Automating Firmware Generation from Schematics for Microcontroller based Designs

Christopher Besch, Janis S. Häseker, Hassan Nassar, Norbert Toth, Jörg Henkel • 16th August 2026

Automating Firmware Generation from Schematics for Microcontroller based Designs

PLUTO's PCDU (Power Conditioning and Distribution Unit)

A Snippet

A Group Netlist

To tackle this problem we got together with the Chair for Embedded Systems at the Karlsruhe Institute for Technology and together introduce the Group Netlist. The Group Netlist is an abstract and tool agnostic representation of the hardware.
We group multiple components fulfilling a well defined function into Groups. The schematics on the left, for example, shows one such Group. You can find this ADC in the simplified Group Netlist on the right. As you can see, the Group Netlist represents what Groups there are and how they interconnect. Therefore, the Group Netlist contains exactly the information needed to write firmware.

kicad_firmware_generation

github.com/DLR-RY/kicad_firmware_generation

To validate our approach, we implemented kicad_firmware_generation, a reference implementation for KiCad. It starts by generating an XML Group Netlist out of the hardware's KiCad netlist. To understand what Groups there are, each snippet's external pin needs a simple annotation. Afterwards our tooling generates firmware from the Group Netlist and Jinja2 templates.
The workflow is entirely deterministic and thus fit for continuous integration. Where previously a cumbersome process bridged hardware and firmware development, our approach continuously runs and ensures that hardware and software are consistent.
Once we introduced our tooling into the PCDU development it found a fault in the PCDU's electrical design! Two control pins for a power switch were swapped. No one spotted this fault before because the power switch and the microcontroller are actually on different boards, bridged through a large connector. One has to trace the circuit through five pages of schematics split across two projects to find the fault. Our tooling caught the fault as a by-product of firmware generation.

Systematic Fault Injection

Inject faults into PCDU schematics:
swap labels, delete cables
8885 unique faults
Result: detected up to 75% of otherwise not found Group Pin swaps

Synthetic Benchmark

Group Netlist

kicad_firmware_generation

github.com/DLR-RY/kicad_firmware_generation