Board families
Hard Fault supports custom boards and development boards through compatible CMSIS Device Family Packs and built-in pyOCD targets. If your MCU has a compatible device pack, its family does not need to appear in this list.
Example families
Section titled “Example families”These are examples of the broader pack ecosystem. Each can use no setup, lite, or full setup when the exact part meets that level’s requirements:
| Vendor | MCU families |
|---|---|
| STMicroelectronics | STM32 |
| Nordic | nRF51, nRF52, nRF53, nRF54, nRF91 |
| NXP | Kinetis K/L/E/V/W, K32, LPC, i.MX RT, S32K, MCX |
| Infineon / Cypress | PSoC, XMC |
| Analog Devices / Maxim | MAX32, ADuCM |
| Texas Instruments | CC32, MSPM0, TM4C |
| HDSC | HC32 |
| Nuvoton | NuMicro |
| Raspberry Pi | RP2040, RP2350 in Arm mode |
| Ambiq | Apollo |
Pack support extends to many more vendors and MCU families. Setup checks your exact MCU, debug probe, and requested operations.
Setup requirements
Section titled “Setup requirements”| Setup level | What the exact part needs |
|---|---|
no-setup |
Debug support that can connect. Flashing also needs a device-specific flash algorithm. |
setup-lite |
A working connection, local datasheet, and memory regions you confirm. Flashing needs confirmed destinations and erase sectors. |
setup-full |
Verified built-in or pack support, a usable memory layout, a local datasheet, and live identity checks. Flashing and recovery need their own permissions and support. |
Check your board
Section titled “Check your board”Give the agent your board name, exact MCU, datasheet PDF, and preferred safety level. Ask it to check support and report which operations are available.
Start with Easy setup or compare Board safety levels.