Supported hardware

USB

Coming soon

The pod becomes a USB host for your board: it tests the board's own USB port and flashes boards that only have a USB bootloader. This page describes what is coming, and details may change. Decoding USB on the logic analyzer works today.

Decode USB on today's pods

The logic analyzer decodes a board's USB traffic now, on every pod: tap the lines and see the enumeration as a list.

  • Wiring. D+ and D- to two LA channels, GND to GND, wires short. Set the I/O voltage to 3.3 V.
  • Rate. Full speed (12 Mbit/s): capture at 48 MS/s. Low speed (1.5 Mbit/s): 6 MS/s or more.
  • Where. The Capture tab (Decode, USB), decode_la in the MCP server, bp.decode(la, "usb", dp=7, dm=8) in pytest, or POST /analyzer/decode.
  • Output. Control transfers (the request and the descriptor read back: VID and PID, interfaces, endpoints, strings), transactions (token, data, ACK, NAK or STALL) and packets with their CRC checked. A bad packet is flagged, the rest still decode.
  • Limits. High speed (480 Mbit/s) is not visible: a high-speed board on a high-speed host shows a reset and then nothing. A full-speed hub between them keeps it at full speed. Heavy bulk traffic can end a 48 MS/s capture early; the capture says so.

How it works

  • Plug the board into the pod's USB-A port. The pod powers it from its internal 5 V, so power cycling and current measurement work on the USB port too.
  • Host mode is on demand. A test, a flash or a CLI command switches the pod's USB to the board for as long as it needs, then back. A timeout always switches it back, even when the client is gone.
  • Use the network or the cloud. While the pod hosts your board it is off your computer's USB, so connect to it over Ethernet, Wi-Fi or the cloud.
  • Full speed (12 Mbit/s), one board at a time. A high-speed board falls back to full speed, so functional tests and flashing work.

USB tests

From pytest, the CLI, the MCP server and the web workspace, like every other pod feature.

TestWhat the pod checks
EnumerationVendor and product ID, strings, USB version, speed, classes and interfaces, and how long the board takes to enumerate after power-on or reset.
USB powerThe current on the USB port during enumeration, in use and in suspend, against what the board declares it needs.
Plug and unplugData-only, power-only or full unplug and replug from a test, with timing. Thousands of cycles unattended for a soak test.
USB serial consoleA board's USB serial port read and written like a UART: wait for a line, assert on the boot log, send commands. Also over the cloud.
Class trafficHID reports (what a keyboard or controller sends), files on a USB drive the board presents, and vendor requests for a custom protocol.

Flashing over USB

The same benchpod flash command, SDK call and MCP tool as for SWD and ESP32, with a new target for each board. The tools read the file formats (.uf2, .hex, .bin, .dfu, .zip), so nothing else is needed on your computer or in CI. A boot or reset pin wired to the pod puts the board in its bootloader without anyone pressing a button.

In development means the pod's development firmware has the flasher and it passes tests against simulated bootloaders. It is not in a firmware release yet and has not been tested on a board. Planned means it is not built yet.

Chip familyStatusHowNotes
Raspberry Pi Pico, Pico 2 (RP2040, RP2350)
In development
USB bootloader (BOOTSEL), .uf2BOOTSEL on a pod pin puts the board in its bootloader without a button.
Teensy 3.x, 4.0, 4.1
In development
Teensy USB bootloader, .hexFlash and USB serial console. No debugging.
Arduino Uno, Nano, Mega 2560 (clones included)
Planned
Arduino bootloader over the board's USB serial, .hexThe board's own USB serial chip, so 5 V logic does not matter.
Arduino Leonardo, Micro, Pro Micro
Planned
Arduino bootloader over native USB, .hexThe pod enters the bootloader with the 1200 baud touch, as the Arduino IDE does.
Arduino Zero, MKR, Due, UNO R4
Planned
Arduino bootloader or USB DFU, .bin
ESP32-S3, C3, C6 (native USB), ESP32 dev kits with a USB serial chip
Planned
ESP32 ROM bootloader over USB serialThe same flasher as over UART, through the board's USB port instead of pod pins.
STM32 in its ROM USB bootloader (Black Pill and others)
In development
USB DFU, .bin, .hex, .dfuBOOT0 on a pod pin starts the bootloader. The pod erases only the sectors the image covers.
NUCLEO and Discovery boards, nRF DK, micro:bit (drag-and-drop drive)
In development
Copy the file onto the board's USB drive, .bin, .hexThe board's on-board debugger takes the file, as when you drag it there yourself.
nRF52840 dongle, Adafruit and Seeed nRF52 boards
Planned
Nordic serial DFU (.zip) or UF2
Adafruit Feather, ItsyBitsy, Seeed XIAO (SAMD, nRF52, RP2040)
In development
UF2 bootloader, .uf2

On today's pods: flashing over UART

Some of the same bootloaders also listen on a UART, which works from the pod's pins on every pod. ESP32 chips already flash this way: see ESP32 chips. The Arduino bootloader of the Uno, Nano and Mega over their serial pins is planned next. Those pins are 5 V: see 5 V logic.

Not planned

  • High-speed (480 Mbit/s) signal quality, USB compliance testing, USB Power Delivery and USB 3.
  • Flashing Linux modules (Raspberry Pi compute modules, i.MX and similar): their images are too large for a full-speed port.
  • Passing the board's USB through to your computer.