Repository navigation
The menu's Wipe user data item is gone. Firmwares keep their settings, projects and samples in different places, often outside the areas they declare or next to data you want, so erasing the declared areas could leave the problem in place or make things worse. Everything else works as in 2.3.
- Removed: Wipe user data. To reset a firmware's settings, use that firmware's own reset, or restore a backup with M-Flasher. The menu now offers SD card (with a card fitted), Boot app or Boot anyway, Download mode and MIDI mode.
- Built with pi32v2 LLVM 23.1.5-5, where 2.3 used 23.1.5-2. So every file below differs from 2.3's, including the helper and the flash loader, whose code hasn't changed apart from the shared flash-format code the wipe item used.
Before you install
- Use M-Flasher 0.9.1 or newer, as for 2.2 and 2.3. M-UPGRADE has no such limit.
- Some browser installers don't accept MIDI mode yet. It answers as
ota-FM-1_900orota-SMK-37 Pro_900, as firmware update loaders do. Optimist's web installer refuses that and points to M-UPGRADE, but Optimist's command-line installer works. - Official M-VAVE updates and Baud Girl's installer put the stock bootloader back, with its full configuration. Reinstall m-bootloader afterwards.
| File | For |
|---|---|
fm1-uboot.fwsc |
FM-1, with M-UPGRADE |
smk37-pro-uboot.fwsc |
SMK-37 Pro, with M-UPGRADE |
smk37-elite-uboot.fwsc |
SMK-37 Elite, with M-UPGRADE |
fm1-uboot.boot |
FM-1, with M-Flasher |
smk37-uboot.boot |
SMK-37 Pro / Elite, with M-Flasher |
fm1-stage.fwsc, smk37-pro-stage.fwsc, smk37-elite-stage.fwsc |
The helper, through M-VAVE's firmware or Baud Girl |
fm1-stage-listed.fwsc, smk37-pro-stage-listed.fwsc, smk37-elite-stage-listed.fwsc |
The helper, through Felucca-family firmware |
fm1-stage-ram.bin, smk37-stage-ram.bin |
The helper, with M-Flasher's run-ram at 0x01C28000 |
mflr-loader-a.bin, mflr-loader-b.bin |
M-Flasher's flash loader, the same code as 1.3, built with the newer compiler |
SHA256SUMS |
checksums |
Back up your unit with M-Flasher first. The menu and M-Flasher show the version as 2.4-395e6cc.
Tested on this exact build, on an FM-1 (0x856014, firmware FM-1 901) and an SMK-37 Pro (Snoop37, with a card). CI's build of it is byte-identical to the one tested.
- Installing with M-Flasher (over its test build, which went on over 2.3), and the firmware starting under it.
- With the firmware damaged, only in its app area: a flipped bit showing
APP BAD CRC, an erased sectorAPP INCOMPLETE, and the whole app erasedAPP NOT FOUND, each time with MIDI mode opening by itself and the firmware not started. - From there, a key opening the menu, with no wipe item, and Boot anyway starting the firmware with a bad CRC once: the next start caught it again.
- Download mode asked for over MIDI from MIDI mode.
- Each unit's flash restored afterwards, and read back identical to its backup, the SMK-37's calibration and its copy included.
On its test build, 2.4-395e6cc-test, on both units: MIDI mode by request, and the SD card item by request. On the SMK-37 that ran m-apps' launcher from its card; the FM-1 has no card, so it went to download mode, as it should without the item.
Not tested:
- The M-UPGRADE packages, official updates, the helper and RAM apps with this build. Their code is as in 2.3, where they were tested, but they're built with the newer compiler.
- This release's own
mflr-loader-*.bin. M-Flasher, which carries its own copy of the 1.3 loader, was used for the tests. - The SD card item with a card on the FM-1.
- 1.2 and 1.3 installed over it. The configuration code hasn't changed since 2.1.
- A real SMK-37 Elite, the MiniFM, and the UC25HQ80.