Supported hardware

Which chips the BenchPod can flash, and which add-on boards and adapters work with it: which ones we test, which ones we expect to work, and what is not supported. Everything else the pod does (power, UART, GPIO, I2C, SPI, CAN, the logic analyzer and analog) works with any board at 1.8 or 3.3 V, whatever chip it has.

Overview

Each family has its own page with the wiring and the notes for its parts. Tested means we run it on our own bench; Should work means it uses the same path and is supported by the tools, but we have not run it ourselves yet.

HardwareWhatStatus
Arm chips over SWDSTM32, nRF51/52, RP2040/RP2350, SAM D/E, LPC, Kinetis, EFM32, Renesas RA: flashed through the pod's SWD probe
Tested
Should work
ESP32 chipsESP32, S2, S3, C2, C3, C6, H2: flashed through the chip's UART ROM bootloader
Tested
Should work
GPIO expander boardsI2C and SPI expander breakouts the SDK and MCP drive as extra pins EXT1, EXT2, ...
Should work
5 V logic and RS-485Adapters for what the pod has no I/O for: a level shifter for 5 V serial, an RS-485 transceiver for Modbus RTU
Should work

External SPI flash (25-series chips) can be programmed directly from four pod pins, whatever the MCU: benchpod spi-flash write in theCLI reference.

What does my target device need as a minimum?

Four things, each on a header or a test point you can reach without soldering to a fine-pitch pin:

  • SWD and reset: SWDIO, SWCLK and the reset line. Reset lets the pod connect even when your firmware turns SWD off. An ESP32 has no SWD: it needs the UART TX and RX of its ROM bootloader, the boot pin and the enable pin instead.
  • UART: the board's TX and RX, for the boot log and a console.
  • GND: at least two ground pins. One is not enough for a clean capture.
  • I/O at 1.8 or 3.3 V: every signal wired to the pod swings between 0 V and one of those two voltages. A 5 V part needs a level shifter, and a signal above the voltage you set can damage the pod.

Also worth having: a defined level (a pull-up or pull-down on the board) on boot and strapping pins, so the board boots the same way when the pod lets go of them, and no second debugger on the SWD pins at the same time. To measure the board's current, power it from the pod's DUT 5V or DUT EXT output.

Not supported

What the pod cannot flash, and what to do instead. For 5 V parts, see5 V logic and RS-485 for the adapters that let the pod talk to them.

Chip familyStatusHowNotes
Boards whose SWD pins are not reachable (Teensy 4.x, many finished modules)
Not supported
USB bootloader onlyThe pod does not flash over USB. Flash from your computer (for a Teensy, teensy_loader_cli) and use the pod for power, UART, GPIO, the logic analyzer and analog.
USB-only bootloaders (UF2 drag and drop, USB DFU)
Not supported
USBUse the SWD pins when the board has them. Otherwise flash from your computer.
AVR and other 5 V parts (ATmega328P, classic Arduino)
Not supported
No SWD, 5 V logicThe pod pins run at 1.8 or 3.3 V. Not planned.
JTAG-only targets (no SWD)
Not supported
JTAGThe pod speaks SWD, not JTAG. Most Arm Cortex-M parts have both: use SWD.