Debugging with OpenOCD and gdb¶
Please use openocd 4.0 or newer.
This example assumes you have a Segger J-Link compatible JTAG adapter between your computer and the device (or dev board) you are debugging. It is possible to use an SWD (ST-Link) adapter instead, for this use openocd 0.7 or newer.
Start the openocd server with configuration files matching your hardware:
openocd -f interface/jlink.cfg -f target/stm32.cfg
Or, if you are using SWD:
openocd -f interface/stlink-v2.cfg -f target/stm32f1x_stlink.cfg
In a second window, start an interactive session with openocd:
telnet localhost 4444
This seems to be necessary to avoid "target is not halted" errors and other trouble later:
Stop the target (the arm processor):
If you have not already flashed the binary, using for instance dfu-util, you can do it over JTAG like this:
1 2 3
reset init flash write_image erase dso-lib.hex 0 ihex reset halt
In a third window, start gdb or gdbtui:
1 2 3 4
arm-none-eabi-gdb (gdb) file dso-lib.elf (gdb) target remote localhost:3333" (gdb) load dso-lib.elf
You should now be able to run and debug:
1 2 3
(gdb) set $pc = Reset_Handler (gdb) display/i $pc (gdb) stepi
Please submit any technical issue into our forum.