run takes a board object:
model value your agent passes in board.
uarts is required. It is the list of peripherals to capture.
Only those UARTs are written into the run’s uart artifact.
Requesting a UART the board does not expose is rejected.
See which frameworks have an example for each board on Frameworks.
uarts. Any name in Available UARTs can go in uarts.
What simulation covers
Each board runs on a chip-accurate model of its microcontroller: the CPU, the on-chip peripherals (UART, GPIO, and the rest of the chip’s peripheral registers) and the interrupt controller. Your firmware drives them exactly as it would on the real chip. Each run executes the ELF and captures the UARTs named inboard.uarts. A run lasts up to 5 seconds of virtual time.
Only the chip itself is modelled. External devices wired to it, such as sensors or I2C/SPI parts, are not simulated yet. Your firmware and tests observe the board through UART output.
Don’t see your chip?
Next on the roadmap: NXP S32, Renesas RA, and Infineon AURIX. Please don’t hesitate to ask. Requests really do shape what we add next. Open a request on GitHub with your target MCU and use case, and our team will review it, or come say hi on Discord. Call Chiplab’s discovery/help tool (ask) to confirm the current, authoritative set of boards. It may be ahead of what’s listed here.