AISLINGby CÚ_STE

support · back up, switch, rescue

tried on one FM-1, from a Mac, with M-Flasher 0.12.1

Support

For an FM-1 running AISLING, FX-1 or anything else.

Keep a copy of your FM-1, change what it runs, and bring it back if it won't start.

The tool

What is M-Flasher?

A free program for Windows, macOS and Linux that reads and writes the FM-1's whole memory over USB, even when the firmware on it does not run.

It is by Julius Vitkauskas, not by AISLING, and it works with any firmware: M-VAVE's own, AISLING, FX-1 and the rest. AISLING's installer in the browser is still the short way to put AISLING on. M-Flasher is for what the installer cannot do: a backup of everything, going from one custom firmware to another, and an FM-1 the installer can no longer see.

Before it writes anything it reads the whole memory, checks that the package is for this model and this unit, saves a backup, and shows what would change. After writing, it checks what it wrote.

Get M-Flasher Its own guide

Both open Julius Vitkauskas's pages. His guide is the full one, and the one to trust where it and this page differ.

The everyday use

Back up, then switch firmware

Six steps. The backup comes first, every time: it is the only thing that brings back the sounds and saves a firmware kept.

  1. Install itOn a Mac, drag M-Flasher to Applications. It is not signed by Apple, so the first time: System Settings → Privacy & Security → Open Anyway.
  2. Plug the FM-1 inStraight into the computer with a USB data cable, not through a hub, and switched on. Close anything else that uses MIDI.
  3. Download modePress DOWNLOAD MODE in M-Flasher. The FM-1's screen stays as it was. A Mac asks for your password, then whether M-Flasher may use a removable volume: Allow.
  4. Back upBACKUP FULL FLASH. It saves a 1 MiB .bin and a .json beside it in Documents/M-Flasher/backups. Keep both.
  5. Choose the firmwareFLASH FIRMWARE, then the .fwsc package: AISLING's, FX-1's or M-VAVE's, as downloaded. Then REVIEW & FLASH, and read what it says it will change.
  6. RestartWhen it has written and checked, unplug the FM-1, switch it off and on. It starts the new firmware.

AISLING's package FX-1's package M-VAVE's firmware

Tried here · An FM-1 running FX-1 1.1 was sent to download mode by the button, backed up, and given AISLING 1.4.1, from a Mac. It started AISLING. One FM-1, with the older memory chip (M-Flasher shows 0x856014 (old)).

Not tried here · Windows and Linux; the newer memory chip (0xB36014); restoring a backup; whether AISLING's saves are still there after a spell on FX-1.

Once per FM-1

Install m-bootloader

The bootloader is the first small program the FM-1 runs. Julius Vitkauskas's replaces M-VAVE's and adds a way into download mode from the FM-1's own keys.

With M-VAVE's bootloader, an FM-1 whose firmware does not start can only be reached with extra hardware (a Raspberry Pi Pico made into a USB_KEY dongle). With m-bootloader it is two fingers:

Held while switching onWhat happens
RECDownload mode, ready for M-Flasher.
PLAYA recovery menu: the firmware's state, Boot app, Download mode, Boot anyway, and a MIDI mode that a browser installer can write through.
nothingIt checks the firmware, then starts it. Damaged firmware opens the menu instead of being started.
  1. Back up firstSteps 1 to 4 above. The backup holds M-VAVE's bootloader too, so it is also the way back.
  2. Look at Flash chipUnder device info. 0x856014 (old): go on. 0xB36014 (new), in FM-1s sold from late 2026: m-bootloader is little tested there, its author says at your own risk, and M-Flasher warns.
  3. Flash bootloaderOn an FM-1 with M-VAVE's bootloader, M-Flasher offers this by itself once it has read the memory. Otherwise press FLASH BOOTLOADER. It has the build for the FM-1 inside it.
  4. Review and flashIt writes the first 16 KiB only, and keeps the chip key that firmware installers need. The firmware, settings and sounds are not touched.
  5. Try the keysUnplug, switch off, then on holding REC: M-Flasher should find the FM-1 again. Switch off and on with nothing held, and the firmware starts as before.

Tried here · AISLING 1.4.1 and FX-1 1.1 both start and play on an FM-1 with m-bootloader 2.4 (2.4-395e6cc, as M-Flasher reads it).

Not tried here · The install itself: that FM-1 already had m-bootloader, so the five steps above are from M-Flasher's guide, not from doing it. Nor the two keys, the menu, or MIDI mode with AISLING's installer.

When it goes wrong

The FM-1 won't start

A dark screen is nearly always the chip waiting in download mode, not a dead FM-1. In order:

  1. Off and onIf you sent it to download mode yourself, that is all it needs: the firmware starts again.
  2. Open M-FlasherPlug the FM-1 in and switch it on. An FM-1 whose firmware is damaged often goes to download mode by itself, and M-Flasher finds it.
  3. Hold RECWith m-bootloader: switch on holding REC. M-Flasher finds it.
  4. Put it backRESTORE FULL FLASH with your backup, or FLASH FIRMWARE with any package for the FM-1.

With M-VAVE's bootloader, no backup, and a Mac: AISLING's own rescue script puts M-VAVE's firmware back from the command line. It is in the manual, under Recovering an FM-1 that won't start.

If none of that reaches it, the USB_KEY dongle does: it forces the chip into download mode whatever is on it. It is described in m-bootloader's own pages.

What each button writes and what it leaves alone
ButtonWhat it writes
Download modeNothing. It sends the FM-1 one MIDI message, and the FM-1 restarts into the chip's download mode.
Backup full flashNothing on the FM-1. A copy of its 1 MiB memory on the computer.
Restore full flashThe parts that differ from the backup. This unit's factory data is kept. With Keep this unit's bootloader, not the first 16 KiB.
Flash firmwareThe firmware in the package. The bootloader is kept; nothing outside the package is erased.
Flash bootloaderThe first 16 KiB only: m-bootloader, or M-VAVE's from an official package.

From M-Flasher's guide, in its words shortened.

The Mac calls my FM-1 something else a name left over from another device

M-Flasher's first line may show another instrument's name beside "running": here, an FM-1 was listed as an SMK-37 Elite. macOS remembers a MIDI device's name by its USB number and the socket it was in, and several custom firmwares share a number. It does no harm: once the FM-1 is in download mode, M-Flasher reads the model from the memory itself.

To clear the old name: Audio MIDI Setup → Window → Show MIDI Studio, unplug the FM-1, and delete the greyed-out device.

Messages on the FM-1's screen BAD CONFIG, FAILED −5, APP BAD CRC

These are m-bootloader's and M-VAVE's updater's, not AISLING's, and what they mean depends on the versions involved. M-Flasher's guide and m-bootloader's status notes list them. In short: BAD CONFIG is an older m-bootloader, and installing the current one from M-Flasher fixes it; APP BAD CRC, APP INCOMPLETE and APP NOT FOUND mean the firmware is damaged or missing, so install it again.

Windows says it is a threat Defender and unsigned programs

M-Flasher is not signed, so Windows may say it protected your PC (More info → Run anyway), and Microsoft Defender sometimes removes a new release as a guess. Its author reports each one to Microsoft, and his guide says what to do meanwhile. Download it only from his page or his releases on GitHub.

M-Flasher and m-bootloader are by Julius Vitkauskas: github.com/jvitkauskas/m-flasher, github.com/jvitkauskas/m-bootloader. Questions about them go to him there. This page is AISLING's account of using them, and is not his.
Changing an FM-1's firmware or bootloader is at your own risk. M-VAVE and FM-1 are trademarks of their respective owners.