Hardware Support
Flint’s current development focus is RP2040 and the surrounding MCU toolchain story. Other targets are part of the design, but they are not yet equally mature.
The target matrix and the MCU HAL are separate questions. This page covers chips and boards; the current micro/* peripheral surface is documented in the MCU HAL chapter.
MCU Targets
| Target | Architecture | Status |
|---|---|---|
rp2040 | ARM Cortex-M0+ | Code generation working |
rp2350 | ARM Cortex-M33 / RISC-V | Planned |
samd21 | ARM Cortex-M0+ | Planned |
samd51 | ARM Cortex-M4F | Planned |
stm32f4 | ARM Cortex-M4F | Planned |
esp32c3 | RISC-V | Planned |
nrf52 | ARM Cortex-M4F | Planned |
Board Variants
| Board | Chip | Status |
|---|---|---|
pi-pico | rp2040 | Current reference board |
pi-pico-w | rp2040 | Planned |
pi-pico2 | rp2350 | Planned |
pi-pico2-w | rp2350 | Planned |
Future Native Targets
| Target | Architecture | Status |
|---|---|---|
x86-64 | x86-64 | Planned |
arm64 | AArch64 | Planned |
riscv64 | RISC-V 64-bit | Planned |
wasm32 | WebAssembly | Planned |
Why The Target Model Matters
Flint does not treat cross-compilation as a special trick layered on top later. The target is part of the ordinary build flow from the start.
That matters for embedded work because the language, standard library, and backend all need to agree on:
- memory layout,
- calling conventions,
- startup behavior,
- and which platform APIs exist.