AeonDave jtag-swd
Use when firmware extraction is needed but direct SPI flash reading is physically impossible (BGA chips, eMMC), or live debugging/execution flow control is required.
1. Interface identification
- Standard JTAG:
TCK,TMS,TDI,TDO,nTRST,nSRST,GND,VCC. - ARM SWD: Compact 2-wire alternative (
SWDIO,SWDCLK,GND,VCC). - Use tools like JTAGulator or JTAGenum on unknown pin headers to automatically scan for TDO responses without manual probing.
2. OpenOCD connection
Map the physical interface (e.g., FTDI-based programmer like Olimex or TIAO) and the target MCU architecture.
# Example: Connect to an STM32F4 via an Olimex ARM-USB-OCD-H programmer
openocd -f interface/ftdi/olimex-arm-usb-ocd-h.cfg -f target/stm32f4x.cfg
3. Execution control & dumping
Connect to OpenOCD's telnet control interface (localhost:4444).
> telnet localhost 4444
# Halt the CPU execution cleanly
> halt
# Inspect CPU state and registers
> reg
# Dump specific memory region (e.g., 1MB starting from flash base 0x08000000)
> dump_image firmware.bin 0x08000000 0x100000
# Resume normal execution
> resume
4. Risks & Considerations
- Watchdog Timers: Halting via JTAG may trigger hardware watchdogs, causing abrupt resets.
- Read-out Protection (RDP): Microcontrollers (especially STM32/NRF) often set internal fuses disabling JTAG debug access or flash reads. Bypassing requires chip-specific glitching workflows.
References
- references/stm32-rdp-bypass.md — Load when an STM32 Read-Out Protection (RDP) prevents memory extraction in OpenOCD.