From KiCad netlist to firmware simulation
Prev. Stitch Fix · Amazon · Bain Capital Ventures. Built ML systems in production at scale; runs how we turn datasheets into models.
KiCad already exports connectivity. The missing piece for embedded teams is a path from that export to a runnable board under real firmware — without waiting on gerbers.
What to export
Netlist (.net / XML), BOM (CSV/Excel), firmware image. Schematic PDF helps when straps and addresses are not in the BOM. Keep the KiCad project as source of truth; HardLabs consumes exports.
What you get back
A platform description, coverage gaps for unmodeled parts, and a path into CI. Open-source ECAD does not mean unserious bring-up.
HardLabs
Send us your design. We'll send you a simulator.
We build a board simulator from your netlist, schematic, and BOM, run your real firmware against it, and fail CI when pinmux, buses, or timing contracts break.
- A working simulator of your board, built from netlist, schematic, and BOM.
- Peripheral models attached so your firmware can talk to the board.
- A setup that runs your real firmware binary — no rewrite required.
Related
- Altium → simulation
Simulate firmware against Altium-designed connectivity before fab. Use design-of-record exports — not a hand-maintained virtual shield.
- Firmware-in-the-loop
Firmware-in-the-loop against your netlist — not stubs. Run unmodified .elf images on MCU simulation with board-aware I²C/SPI models and CI assertions.
- TCA9555 model
HardLabsAll topics