npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

@iotize/mcu-flasher.js

v2.1.0

Published

IoTize library for ARM-Cortex MCU programming

Downloads

85

Readme

MCU Flasher

This library is still in alpha stage. Breaking changes may occurs in future releases.

See CHANGELOG.

Installation

npm

npm install @iotize/mcu-flasher.js

Usage

MCU Flasher needs these informations to configure itself :

  • Simfile : A configuration file provided by IoTize declaring every MCU Reference-specific informations (such as memory addresses).
  • PluginFile : an Intel HEX file, provided by IoTize, that contains the plugin to load in the MCU's memory to perform programming actions. The plugin to load is specified in the MCU's Simfile.

Both files can be retrieved from this repository: https://github.com/iotize-sas/simfiles

It also needs an IoTizeDevice to connect to, and profile credentials with sufficient rights, (e.g. tap admin's credentials)

Create and use a Developer instance

import { MicroControllerDeveloper } from '@iotize/mcu-flasher.js';

let mcuDeveloper = MicroControllerDeveloper.create(
    device,
    simFileString,
    pluginString
);

// now you may call the programming methods:

await mcuDeveloper.dump();
await mcuDeveloper.erase();
await mcuDeveloper.blankCheck();
await mcuDeveloper.programFile(programString);
await mcuDeveloper.run();

programString is the Hex file or Srec file (to be validated) that you want to program in your MCU memory.