TransitFM1
A tiny firmware for the M-VAVE FM-1 to stop at between two others: every installer takes it for the official V15, and the write that replaces it is guarded until its last sector.
Before you start
For Baud Girl, go through the official V15: install V15 from here, then Baud Girl with its own installer. Its image is larger than TransitFM1 can write; TransitFM1 0.1.2 let Baud Girl's installer try anyway and left an FM-1 dark, so 0.1.2 was withdrawn. 0.1.3 refuses such firmware itself.
Arriving from V15, a cut-off write ends in the chip's USB boot rather than update mode: have MvaveFM1Unbricker (Windows or Linux) or the FM-1 Transporter in mind. Close any app that sends MIDI to the FM-1 while you install. Installing firmware is at your own risk.
Install
Log
If an install is cut off
From TransitFM1, a pulled cable or a flat battery is not the end: switch the FM-1 off and on. Three short flashes of the key lights and a black screen mean update mode. Open this page (or the installer you were using) and press Install again with the same firmware: it finishes the write. Holding OCT- while switching on gives the same update mode at any time.
Leaving TransitFM1
Install the next firmware with its own installer: it sees an FM-1 on the official V15. Whatever
the package, TransitFM1 writes it with its own update loader, the new firmware's first sector last. To go back to
stock, install M-VAVE's FM-1.fwsc. Baud Girl, and any firmware whose image is larger than
the app area: install V15 first, then that firmware from V15.
Install a package file from here
How much of a write is guarded
| hop | cut points with no rescue |
|---|---|
| TransitFM1 → the official V15, or any firmware without ChoralRoot's stub | 16 of 2432: the last sector |
| TransitFM1 ↔ ChoralRoot | none |
| the official V15 → TransitFM1 | 17 of 2432 (the first sector); the other cuts end in the chip's USB boot, not update mode (V15 stages the loader where the boot stub does not look) |