Supported hardware

ESP32 chips

ESP32 chips have no SWD. The pod flashes them through the chip's own ROM bootloader over its UART, the way esptool does, so no esptool is needed on your computer.

Chips

Chip familyStatusHowNotes
Espressif ESP32 (the original ESP32, for example an ESP32-WROOM-32 board)
Tested
UART ROM bootloader: TXD0 and RXD0 on two pod pins, IO0 on a third, EN on the reset pinbenchpod flash --target esp32, or flash(target="esp32", ...) in the SDK; no esptool needed. Tested on an ESP32-WROOM-32 board. Needs pod firmware 3.10.7, CLI 0.8.11 or SDK 2.13.19.
Espressif ESP32-S2, S3, C2, C3, C6, H2
Should work
The same UART ROM bootloader; the boot pin is IO9 on the C3 and C6Same command with --target esp32s3, esp32c3 and so on. ESP8266 not supported.

Wiring

PodESP32Note
An LA pin (rx, default the profile's uart_rx)TXD0The pod listens to the bootloader here
An LA pin (tx, default uart_tx)RXD0The pod sends the image here
An LA pin (boot, default a profile signal named BOOT, IO0 or IO9)IO0 (IO9 on the C3 and C6)Driven open-drain, low through reset to enter the bootloader
Reset pin (NRST_CONTROL, J1 pin 22)ENWith --nreset the pod pulses it to restart the chip
GNDGNDAt least one, two is better

Flash

# an ESP-IDF build: flasher_args.json names every image and its offset
benchpod flash --target esp32s3 --file build/flasher_args.json --boot 6 --nreset
# one image at an address
benchpod flash --target esp32 --file build/app.bin --load-address 0x10000 --rx 3 --tx 4 --boot 6 --nreset
  • In the SDK: flash(target="esp32", file=..., rx=..., tx=..., boot=...); the MCP server's flash tool takes the same. Omitted pins come from the wiring profile stored on the pod; a pin it does not set either must be passed, and the call says which.
  • Use the target name of your chip: esp32, esp32s3, esp32c3 and so on.
  • The board's own USB-to-serial chip and auto-reset circuit can fight the pod on TXD0, RXD0, IO0 and EN. Leave the board's USB unplugged while the pod flashes it.
  • Needs pod firmware 3.10.7, CLI 0.8.11 or SDK 2.13.19 or later.