Squirmware

Components and intentions in, working firmware out.

Tell Squirmware what a circuit board should do, in plain words, and give it the board. It writes the firmware, checks its own work at every step, and asks you to approve each step before the next one starts.

How it works

  1. Intent. Your words become a precise description of behaviour, checked against what the board can do.
  2. Binding. The board's wiring is read and every pin gets its job. No guessing: it comes from the netlist.
  3. Plan. The firmware is laid out as modules, tasks and tests you can read before any code exists.
  4. Build. The code is written, compiled and tested in a sealed container; problems go back to be fixed.
  5. Target. The firmware is loaded onto the board, watched while it runs, and released with its notes.

You approve at each of the five gates. Nothing reaches you that the machine checks have not already passed.

Part of a family

RADCAD designs the mechanical parts. pcbyay designs the circuit board. The Library of Everything keeps every part, board and file they make. Squirmware makes the board do what you wanted.

Status: early. This is the framework release; the service is open to invited users with an access token.

For developers: the API is described at /api/docs and answers at /api/health.