fm1-amy
fm1-amy turns the M-VAVE FM-1 into a six-voice polyphonic analog-style synthesizer.
- Custom firmware
- Alpha
- Medium brick risk
- Reversible
This project hasn't been claimed by its maintainer yet, so its details come from the community. Is it yours? Claim it
Before you start
- How hard is it?
- HardUses the command line or developer tools.
- What you need
- A USB or MIDI cable
- Comfort with the command line
- A computer
- Can it break my device?
- Small chance of trouble, with a way to recover.
- Can I undo it?
- Yes. You can go back to the official software.
Did it work for you?
Did fm1-amy work on your M-VAVE FM-1?
No reports yet.
One-tap reports from owners. Bricked reports are checked before they count.
Compatibility
Devices: M-VAVE FM-1.
No compatibility information yet.
Getting started
From the project's README ("Installing"):
There is no ready-made firmware file yet: build it first, which gives build/amyfw/x0x-amy.fwsc. Then, with the FM-1 plugged in by USB and switched on:
pip3 install mido python-rtmidi python3 tools/fm1install.py --info # check the FM-1 is found, and what it runs python3 tools/fm1install.py build/amyfw/x0x-amy.fwsc # install
The installer reads the package and starts the FM-1's update loader, which writes the firmware, restarts the FM-1 and checks what it runs afterwards. It works from M-VAVE's own firmware (it was first installed over M-VAVE's V15, which identifies as FM-1015) and from X0X. Don't unplug the FM-1 or switch it off while it writes. Afterwards the FM-1 reports FM-1900, the identity of a development build, and its USB MIDI port is named "X0X FM-1".
To go back to X0X, install its firmware from X0X's web installer, which can also put M-VAVE's firmware back.
If the install stops with "the update loader did not appear" (the FM-1's screen showed UPDATE / CONFIRM), nothing was written and the FM-1 goes back to what it was running; run the install again. The usual cause is a program doing MIDI thru on the FM-1's port, such as the AMYboard editor in control mode, which sends everything it receives from the board back to it: an echo of the FM-1's own update messages could block the installer's single confirming reply. fm1-amy's firmware ignores those echoes, so this only happens when installing over an older …
Risk and recovery
- Brick risk
- Medium
- Reversible
- Yes
- Requires opening the device
- No
From the project's README ("If something goes wrong"):
These come from X0X and Felucca, and still work in fm1-amy:
- Crash: the screen turns red, shows where the crash happened, and the FM-1 restarts by itself. If you report a crash, include that address and what you were doing.
- Safe mode: if the firmware crashes twice in a row while starting, the FM-1 starts in safe mode instead: no sound, but USB works, so the installer (or X0X's web installer) can reach it.
- Update mode: hold OCT- and OCT+ together for five seconds. fm1-amy doesn't show X0X's countdown on its screen, but the FM-1 still enters update mode, where an install can finish.
- Rescue: if even safe mode fails twice, the chip drops into its own update mode, which only tools/fm1rescue.sh can reach (from a Mac). It puts M-VAVE's V15 firmware back; see "Recovering an FM-1 that won't start" in X0X's manual.
Credits, license and support
- License
- GPL-3.0