1 of 1 people found this helpful
Openocd can communicate with GDB in two ways:
1.A socket(TCP/IP) conncetion is typically started as follows:
target remote localhost:3333
2.A pipe connection is typically started as follows.
target remote | openocd -c "gdb_port pipe; log_output openocd.log".
For more details,please refer to following link"OpenOCD User’s Guide: GDB and OpenOCD ".
Thank you for answer!
Previously I tried to run GDB OpenOCD Debugging (in Debug Configuration menu). For 3333 port it workes, but 3334 hangs.
Now I tried GDB Hardware Debugging with options:
GDB Command: arm-none-eabi-gdb
Use remote target - checked
JTAG Device: GNU ARM OpenOCD
Host name or IP address: localhost
Port number: 3333 (or 3334 for second device)
Force threread list update on suspend - checked
Both port debug works fine!