openocd

Start with config file

$ openocd -f [interface/stlink.cfg] -f [target/stm32f4x.cfg]

$ openocd -f [interface.cfg] -f [target.cfg] -c "program [firmware.elf] verify reset exit"

$ openocd -f [interface/jlink.cfg] -f [board/stm32f4discovery.cfg]

$ openocd -f [config.cfg] -c "init"

$ openocd -f [config.cfg] -c "init" -c "dump_image [output.bin] 0x08000000 0x10000"

$ openocd -d3 -f [interface.cfg] -f [target.cfg]

openocd [-f config] [-c command] [-d level] [options]

openocd (Open On-Chip Debugger) provides debugging and programming for embedded systems. It interfaces with JTAG and SWD debug adapters to access microcontrollers.
Configuration files define the debug adapter (interface) and target device. Many boards and adapters have predefined configurations in the installation.
Programming mode flashes firmware to microcontrollers. Verify confirms the write succeeded. Reset starts the new firmware.
When running as a server, OpenOCD provides GDB server (port 3333) and telnet interface (port 4444). GDB connects for source-level debugging.
The telnet interface allows direct commands: halt, resume, step, memory read/write, register access, and breakpoint management.
Multiple targets can be debugged simultaneously. JTAG chains with several devices are supported.

-f FILE

Configuration file.

Run command.

Search directory.

Debug level (0-3).

Log to file.

Show version.

Show help.

Requires appropriate adapter hardware. Target configuration must match device. Some features are adapter-specific. Debug permissions may need udev rules.

OpenOCD was started by Dominic Rath as a university project in 2005. It became the standard open-source on-chip debugger, supporting hundreds of target devices and debug adapters. Development continues under community governance.

gdb(1), arm-none-eabi-gdb(1), stlink(1), avrdude(1)