Agentic firmware development
Give coding agents real hardware through MCP: observe by default, actuate under a grant a person approved. The loop of write, flash, test and judge runs without a human in the timing path.
Use cases
Agents, CI farms, production lines, precision rigs and the desk next to you all run the same tests against the same bench.
Use cases
Give coding agents real hardware through MCP: observe by default, actuate under a grant a person approved. The loop of write, flash, test and judge runs without a human in the timing path.
Start with GPIO and UART, add CAN-FD or a power module when the product needs it. Pay for the slots you use, not a rack you'll grow into.
The tests that ran on the desk run on the line. A fixture becomes a set of modules, and every unit leaves a manifest with firmware version, bench ID and calibration.
A shared 10 MHz clock puts every module on one timeline. Edges, bytes and frames carry hardware timestamps, and reactions stay on the module, well under a microsecond.
A fleet of benches as runners for GitHub Actions or GitLab. One lease per job, safe state between jobs, JUnit results, and a labgrid exporter for farms that already exist.
The same pytest suite with --hil-bench. No bench attached? Hardware tests skip and say which module is missing. No hardware yet? Point it at the virtual bench.
Cut power the moment the DUT's current rises during a flash write. Sag the supply, drop the BLE link, corrupt UART framing, all timed on the module.
Swap modules per client instead of building a new interface board for every project. Hand the client the tests and the records with the firmware.
The EU Cyber Resilience Act means more updates, and each one needs regression on hardware. Requirement → test → run, with records an auditor can follow.
Developer experience
Signals are attributes. Plans are built in Python and run on the module clocks. The same file runs on your desk, in CI and for an agent.
The missing middle
| Industrial HIL | Compact fixed-I/O tools | DIY rigs | Lupemm | |
|---|---|---|---|---|
| Modular I/O | ||||
| µs timing on the device | ||||
| Fault injection per module | ||||
| pytest & Git CI native | ||||
| Agent access with approvals | ||||
| Open module spec | ||||
| Price | quote only, often five to six figures | ~$500, fixed I/O | cheap parts, costly time | $3–8k target |
yespartlyno
Design partner program
We're looking for 5–10 firmware teams who ship at least monthly and test on hardware by hand or with a DIY rig today. Paid pilots, early hardware and a direct line to the people building it.
Talk to us →