Supported boards
Board support is defined by a hardware-focused YAML file under boards/. Bring-up,
Stage 0 validation, and the benchmark suite are proven on the boards below.
Official scoped pair
Section titled “Official scoped pair”These two targets are the real bench path for the current phases.
| Board | MCU | Probe | Board id |
|---|---|---|---|
| Nordic nRF52833-DK | nRF52833 (Cortex-M4F) | On-board J-Link / CMSIS-DAP | nrf52833dk |
| ST Nucleo-L476RG | STM32L476 (Cortex-M4F) | On-board ST-LINK | nucleo_l476rg |
Alternate profile
Section titled “Alternate profile”Retained for future support work; no longer blocks the current gates.
| Board | MCU | Probe | Board id |
|---|---|---|---|
| Nordic nRF52840-DK | nRF52840 (Cortex-M4F) | On-board J-Link | nrf52840dk |
How a board is defined
Section titled “How a board is defined”Tracked board YAML is hardware-only. It may include board identity and display
name, MCU family, probe family, pyocd_target, baudrate, probe/serial hint
terms, recover policy (for example requires_recover_validation and
recover_mode), and UART expectation metadata.
It must not include project paths, build commands, artifact output paths, or any user- or session-scoped path — those are part of the repo tree and naming standard, not board config. User firmware is always supplied later as runtime input and never lives in the repo.
Board ids are lowercase stable identifiers and key every per-board path.