Supported Hardware
MCU families, debug probes, and compatibility information.
Rake supports ARM Cortex-M firmware workflows through its managed ARM GNU toolchain, OpenOCD scripts, built-in MCU catalog, SVD register metadata, and debug probe detection; ESP32 projects through managed ESP-IDF; and Tuya T5 devices through the managed tyutool. The first action that needs a toolchain asks for download approval; see Toolchain Setup.
MCU Catalog
Rake can configure known MCUs from its built-in catalog, which covers ten chip vendors and 51 families. Automatic target detection depends on probe access, target power, SWD/JTAG wiring, and whether the device exposes a recognizable ID.
| Vendor | Families In The Built-In Catalog | Example Parts |
|---|---|---|
| STMicroelectronics | STM32C0, STM32F0, STM32F1, STM32F2, STM32F3, STM32F4, STM32F7, STM32G0, STM32G4, STM32H7, STM32L0, STM32L1, STM32L4, STM32L5, STM32U0, STM32U3, STM32U5, STM32WB, STM32WBA, STM32WL | STM32F103, STM32F407, STM32H743, STM32U575, STM32WB55 |
| Nordic Semiconductor | nRF51, nRF52, nRF53, nRF91 | nRF51822, nRF52840, nRF5340, nRF9160 |
| Raspberry Pi | RP2040, RP2350 | Raspberry Pi Pico, Raspberry Pi Pico 2 |
| Microchip / Atmel | SAMD21, SAMD51, SAME54, SAML, SAM3, SAM3X, SAM4 | ATSAMD21G18A, ATSAMD51J20A, ATSAME54P20A, ATSAML21 |
| NXP / Freescale | Kinetis K, Kinetis KL, Kinetis KE, LPC8xx, LPC84x, LPC11xx, LPC13xx, LPC17xx, LPC43xx | MK64FN1M0, MKL25Z4, LPC845, LPC1768, LPC4337 |
| Silicon Labs | EFM32, EFR32 Series 2 | EFM32GG, EFM32TG, EFR32BG22 |
| Texas Instruments | Stellaris / TM4C, MSPM0 | TM4C123GH6PM, TM4C129ENCPDT, MSPM0G3507 |
| Infineon | XMC4000 | XMC4100, XMC4500, XMC4700, XMC4800 |
| Espressif | ESP32, ESP32-S3, ESP32-C3, ESP32-C6, through managed ESP-IDF | ESP32-WROOM-32, ESP32-S3, ESP32-C6 |
| Tuya | T5, device tools only (see below) | T5-E1 |
The catalog means Rake has built-in metadata for configuration. It does not guarantee that every board variant, boot mode, flash layout, or protection state can be handled without manual adjustment.
Supported Debug Probes
Rake can automatically identify 18 common probes by USB vendor/product IDs and choose an OpenOCD interface script. ESP32 probes are driven through ESP-IDF's OpenOCD instead.
ST-Link
| Probe | Interface | Notes |
|---|---|---|
| ST-Link V2 | SWD/JTAG | Standalone programmer |
| ST-Link V2-1 | SWD/JTAG | Built into many Nucleo boards |
| ST-Link V3 | SWD/JTAG | High-speed standalone probe |
| ST-Link V3E | SWD/JTAG | Built into newer Discovery boards |
| ST-Link V3 MINIE | SWD/JTAG | Compact standalone probe |
SEGGER J-Link
| Probe | Interface | Notes |
|---|---|---|
| J-Link | SWD/JTAG | Professional debugger |
| J-Link EDU | SWD/JTAG | Educational license |
CMSIS-DAP
| Probe | Interface | Notes |
|---|---|---|
| CMSIS-DAP | SWD/JTAG | Generic CMSIS-DAP devices |
| Microchip EDBG CMSIS-DAP | SWD/JTAG | Common on Microchip evaluation boards |
| Raspberry Pi Debug Probe | SWD | Official Raspberry Pi debug probe |
| Picoprobe | SWD | Raspberry Pi Pico used as a probe |
Texas Instruments
| Probe | Interface | Notes |
|---|---|---|
| XDS110 | SWD/JTAG | On-board debugger of TI LaunchPads and the standalone XDS110 |
| TI ICDI | JTAG | In-Circuit Debug Interface on Tiva C and Stellaris LaunchPads |
Espressif
| Probe | Interface | Notes |
|---|---|---|
| Espressif USB-JTAG | JTAG | Built into ESP32-S3, ESP32-C3 and ESP32-C6; used through ESP-IDF |
| FTDI FT2232H (ESP-Prog compatible) | JTAG | ESP-Prog and compatible adapters; used through ESP-IDF |
Other Probes
| Probe | Interface | Notes |
|---|---|---|
| Black Magic Probe | SWD/JTAG | Open-source probe |
| FTDI FT2232H | SWD/JTAG | Dual-channel USB adapter |
| FTDI FT232H | SWD/JTAG | Single-channel USB adapter |
SVD Register Support
Rake loads bundled SVD files when one is available for the selected MCU. SVD data enables named peripheral registers, bit fields, reset values, and access metadata in the register view.
If your MCU is not covered by a bundled SVD file, add a custom svdFile path in .rake/launch.json. See Project Configuration.
Hardware Detection
Ask @Debugger detect my hardware to run automatic detection.
Rake will try to:
- Identify connected debug probes.
- Query the target through the probe.
- Match the MCU or family to the built-in catalog.
- Select OpenOCD interface and target scripts.
- Generate or update the debug configuration.
Detection Requirements
- Debug probe connected by USB
- Target board powered
- SWD/JTAG connected between probe and target
- Target not locked in a protection mode that blocks detection
- Correct boot or reset state for the target family
Manual Configuration
Use manual configuration when:
- The board uses a custom flash layout.
- The target is not in the built-in catalog.
- Automatic detection cannot read the target ID.
- You need custom OpenOCD scripts.
- You need a custom SVD file.
Create or edit .rake/launch.json for those cases. See Project Configuration.
ESP-IDF Targets
Managed ESP-IDF builds cover ESP32, ESP32-S3, ESP32-C3, and ESP32-C6 projects. Rake prepares the required toolchain after approval; installing idf.py separately does not replace it. See Toolchain Setup.
Build support does not guarantee that every board's wiring, boot mode, or debug probe has been tested. Check the target and connection before approving a hardware operation.
Tuya T5
Rake flashes, monitors, and licenses Tuya T5 (T5AI) boards built with TuyaOpen through the managed tyutool. Build the firmware with tos.py build; Rake records the image that build produces and flashes only that image. On a board with separate flash and log UARTs, you pick the port. T5 has no SWD or JTAG path, so debugging is not supported.
Currently Unsupported
- RISC-V outside supported ESP-IDF targets - No general-purpose managed RISC-V profile.
- Cargo-only firmware projects - The built-in build actions support Make and CMake, not Cargo.
- STM8 - 8-bit architecture is outside Rake's Cortex-M workflow.
- AVR - Not an ARM Cortex-M target.