fm1-nes
This repository shares resources, board-support code and a worked example of how to develop custom firmware for the FM-1, based on the Jieli WL82.
- Custom firmware
- Alpha
- Medium brick risk
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?
- EasyWith Slipway.
- 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?
- The project doesn't say. Assume you can't.
Did it work for you?
Did fm1-nes 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 ("Start with USB serial and a way back to UBOOT"):
Already integrated in this repository: USB CDC serial diagnostics and the guarded two-step UBOOT / UBOOT CONFIRM command are implemented in firmware/usb-diag/ and included in the USB-only, NES and optional USB-audio builds. You do not need to implement this update-entry path from scratch. The V14 composite bench test above successfully entered UBOOT through it. See the implemented command sequence and APPUPDATES.md for programming with the existing Jieli tool. This enters download mode; it is not self-flashing over CDC, and it does not provide those commands to an unmodified stock firmware.
Our recommended first custom firmware is small: USB CDC serial diagnostics, plus a command that returns the device to Jieli UBOOT/download mode. Establish this before working on the LCD, audio engine or a complete application.
- Prepare recovery first. Keep a private, verified backup of your own device and a proven way to enter download mode independently of the application.
- Bring up USB serial. Confirm that the PC can enumerate the device and exchange diagnostic commands and responses reliably.
- Test the included serial UBOOT entry. Confirm that the device leaves CDC mode and re-enumerates in download mode, then verify the appropriate upload and normal-boot procedure for your hardware.
- Add peripherals one at a time. Test the LCD/backlight, audio, keys, knobs and volume independently before integrating an application. …
Risk and recovery
- Brick risk
- Medium
- Requires opening the device
- No
From the project's README ("Start with USB serial and a way back to UBOOT"):
Already integrated in this repository: USB CDC serial diagnostics and the guarded two-step UBOOT / UBOOT CONFIRM command are implemented in firmware/usb-diag/ and included in the USB-only, NES and optional USB-audio builds. You do not need to implement this update-entry path from scratch. The V14 composite bench test above successfully entered UBOOT through it. See the implemented command sequence and APPUPDATES.md for programming with the existing Jieli tool. This enters download mode; it is not self-flashing over CDC, and it does not provide those commands to an unmodified stock firmware.
Our recommended first custom firmware is small: USB CDC serial diagnostics, plus a command that returns the device to Jieli UBOOT/download mode. Establish this before working on the LCD, audio engine or a complete application.
- Prepare recovery first. Keep a private, verified backup of your own device and a proven way to enter download mode independently of the application.
- Bring up USB serial. Confirm that the PC can enumerate the device and exchange diagnostic commands and responses reliably.
- Test the included serial UBOOT entry. Confirm that the device leaves CDC mode and re-enumerates in download mode, then verify the appropriate upload and normal-boot procedure for your hardware.
- Add peripherals one at a time. Test the LCD/backlight, audio, keys, knobs and volume independently before integrating an application. …
Credits, license and support
- License
- Apache-2.0