Submit your firmware

Made a firmware for the FM-1 or the SMK-37? Put it on the hub. It goes here with your name and your links, and the hub follows every release you make. Open source gets the most: one-click install from the hub itself.

What the hub lists

Open source under the GPL-3.0, the MPL-2.0 or another open licence, with its complete source public. Then the hub serves the package itself, installs it in one click and keeps a copy of the source.
A release on GitHub with the .fwsc attached. The hub takes every new release by itself, within three hours.
Its own identity, an FM-1_ number no other firmware uses: how to pick one.
The update loader in the package, so players can leave it again: what that is.

Closed source? Welcome too, as a link card: like M-VAVE's FM1 Open or Baud Girl, it installs from your own page. The hub shows it and links to it, but does not host or mirror it.

New to it? Start from a template: Dinghy, the plumbing done and documented, a sine wave on top, yours to replace; or foma by konsumer, Dinghy made smaller: one C file, a Docker toolchain, a browser emulator that reloads as you save, CI builds and a web preview.

Test it before you send it. Really.

The hub runs no tests: you are the only one who does. Players press Install trusting that it works, and a firmware that does not let go leaves them with a stuck FM-1. Untested firmwares are not listed.

Install the release's .fwsc on a real FM-1, from V15 and from another firmware.
Leave it again: from your firmware, install another one. It must start the next update, or players get stuck.
USB: it shows up as MIDI and answers the identity request with its own FM-1_ number.
Say what it keeps: if it cannot read other firmwares' projects or samples, the README says so.

What to send

Names: the firmware's, and yours as it should appear on the card and the Wall of Creators.
The repository with the release (closed source: your page), its FM-1_ identity and its licence.
What it does in two or three sentences. The card may say it a little shorter.
A picture: a capture of its screen (240 × 240) or a photo, square or wide. A link to it is enough.
If you have them: a version that plays in the browser, an editor, a video, a cheat sheet.

Links instead of attachments, please: big mails do not always arrive.

What happens then

I look at it and write back if something is missing.
It goes on the test site first, then live: your card on the hub, your name on the Wall of Creators.
Every release from then on is checked (identity, update loader, checksum) and listed by itself, and a copy of its source is kept next to the package.
Players rate it, keep it as a favourite, and reach you through your repository.

Optional, and worth it: let GitHub build and sign your release. Five minutes, once, and your card shows Built from source on GitHub.

Send it

All of the above in one mail. The button opens a mail with the questions already in it.

✉ Mail me your firmware

zven@thefirmwarehub.com

The hub is free and stays free. If it saved you an evening: ☕ buy me a coffee.