Versions: Generally speaking, customers should be running the latest available SupMCU firmware (fw). Some functionality may change from one version to the next.

Tools for re-flashing: (Re-)flash new SupMCU firmware onto SupMCU-based modules via Pumpkin's ds30 Loader GUI software in conjunction with the SupMCU's built-in bootloader.

Non-volatile memory (NVM) settings: Some firmware updates may automatically return the NVM settings to their defaults when applied to a SupMCU. Therefore, make a note of any custom NVM settings prior to reflashing SupMCU firmware. Erase NVM settings immediately after loading new firmware, restart the module, and then re-write custom NVM settings to avoid configuration problems.

Matching firmware updates to hardware: Some SupMCU modules have 512KB of flash memory, others have 256KB; firmware files contain the flash memory size in their names for easy identification. Customers must identify and use the firmware update that matches their SupMCU hardware. Should the user (re-)flash the SupMCU with firmware that does not match the module type and hardware revision code of the target module, i) the bootloader will refuse to run the mismatched firmware (and will reflect this via a message that is sent out of the CLI terminal), ii) the SupMCU will not run the target application and iii) the module will continuously restart with a slowly blinking status LED. Should this occur, re-flash via the ds30 Loader GUI using the correct SupMCU firmware.

Downloading .hex files: Because the default MIME type for .hex files is text/plain, most browsers will open .hex files instead of downloading them to your computer when you click on them. If/when this happens, employ a two-step process by i) clicking on the .hex file, and ii) by then choosing "Save Link As ..." (FireFox) or equivalent, to save the .hex file to your computer using the original filename. Then, from within the ds30 Loader GUI, select the downloaded file for reflashing the SupMCU.

Version	Date Added	Notes
BM2_256MC206_RevF3_0x5C_fw-1.5.9r2-1.6.2r0.hex BM2_256MC206_RevF3_0x5D_fw-1.5.9r2-1.6.2r0.hex BM2_256MC206_RevF3_0x5E_fw-1.5.9r2-1.6.2r0.hex	20230411	BM2 firmware flight releases for three separate default I2C addresses; i.e., this will be the module's I2C address after a clearing of the NVM. Review the module's post-splash screen text: "Rx SCPI commands on I2C address 0x5C (400kHz max SCL) ..." for its current I2C address, and re-flash it with the corresponding hex file. Includes updates to SupMCU core code streamlining various issues surrounding telemetry gathering over I2C.
BM2_256MC206_RevF3_0x5C_fw-1.5.9r2-1.6.0r4.hex BM2_256MC206_RevF3_0x5D_fw-1.5.9r2-1.6.0r4.hex BM2_256MC206_RevF3_0x5E_fw-1.5.9r2-1.6.0r4.hex	20220518	BM2 firmware flight releases for three separate default I2C addresses; i.e., this will be the module's I2C address after a clearing of the NVM.
BM2_256MC206_RevF3_on_QSM_fw-1.5.9r2-1.6.0r4.hex	20220518	BM2 on QSM (simulated BM2) firmware flight release. Customers must change the I2C address (as needed) using the NVM facility in order to generate instances of alternate I2C addresses.