FREE AMBIENT FIRMWARE / FM-1

Make room
for a world.

Install Bunker Evolved. Keep a way back.

RELEASE 1.0 · FM-1_7100002 · ORIGINAL ↔ BUNKER TEST PASSED

01 / Prepare and connect

Charge and power on your FM-1. Connect it directly with a USB data cable. Open this HTTPS page in desktop Chrome or Edge. Close other MIDI apps and installer tabs, and connect only one FM-1.

No device identity requested yet.

Coming from original firmware? Use this installer directly. AMB-1 is not required first. Original V15 is the documented baseline; if an older stock version will not enter update mode, update to V15 with the manufacturer's tool first.

On 17 October 2026, the project owner completed Bunker → original → Bunker → original on an FM-1 and confirmed working audio and controls. Release 1.0 uses that exact tested firmware. Read the release record.

02 / Back up your music

Already on Bunker Evolved? Stop playback and recording, then save a complete music archive to your computer. This reads current music, project slots, user sounds, samples and settings. Keep the downloaded file.

Detect your device first. This does not flash firmware.

Original / AMB / other firmware: use its own backup tools before switching. The Bunker backup button does not export those formats. Old music is not converted and can be replaced by saving or autosave. A firmware rollback is not a music backup.

Restore a Bunker music archive

First install Bunker Evolved and stop playback. Select an archive made by this page. All archive checksums are checked before writing. Restoration replaces music, samples and settings; a disconnect can leave a partial restore.

03 / Choose your firmware

Other firmware / archive

Optional previous and alternative builds. The current release and the original firmware are listed above.

Previous Bunker source · AMB-1 source

Checking packages…

04 / Install

The installer checks the file size, SHA-256 and product identity. It prepares the update loader, writes the application, then checks the device's returned identity. Detection alone never starts an update.

Already running FM-1_7100002? You have this exact release. Its internal startup label still contains RC2 because the hardware-tested binary has not changed. No reflash is needed.

Prepare above. Nothing is flashed automatically.

Keep power and USB connected. Leave this tab open until completion. If an error occurs, save the log before taking recovery steps.

Installation log & diagnostics


05 / If something interrupts the update
  1. The application starts: choose a rollback target and install normally.
  2. The MIDI update loader answers: keep powered, select the same target and start again. The writing phase restarts; completion requires the expected final identity.
  3. The application hangs: the watchdog can reboot it. Repeated failed starts may enter UBOOT, a chip mode that can require separate tools.
  4. No compatible MIDI reply: Chrome cannot recover every chip mode. Save the log and follow the full recovery guide.
Both OCT buttons held for five seconds while running enter UBOOT. Both held at power-on open panel calibration. Neither is the normal install procedure.


06 / Your first few minutes
Start quietly. Press PLAY. HOME / SELECT changes the six pages; ALGORITHM selects the track. On GROW: KNOB 1 root, KNOB 2 scale, KNOB 3 style, KNOB 4 ONE / ALL. OCT+ applies, OCT− undoes. The result stays locked until you re-enable EVOLVE.
On SOUND, PRESETS loads a new sound immediately. EDIT, ENV, LFO and FX open detailed sound design. Save a composition on SAVE → PROJECT before turning off. Full guide →
After an update, check the firmware identity, audio, note edits, GROW/undo and save/restart. Do not test recovery by deliberately interrupting power.