You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Seeing the 0.0.0.0 in there gave me the idea to try the following:
(gdp) target remote 0.0.0.0:3333
This results in the output described in the book, and allows me to continue.
Perhaps it would help some if this solution was added as a note in the book.
A further note, the same applies to the gdb script openocd.gdb, changing the first line from target extended-remote :3333 to target extended-remote 0.0.0.0:3333 fixes the later part that hit the same issue.
The text was updated successfully, but these errors were encountered:
In 2.2 Hardware, the following gdb command is listend to connect to openocd:
When I ran this on my machine, it consistently timed out:
The command I'm invoking for the gbd console is:
arm-none-eabi-gdb -q target/thumbv7em-none-eabihf/debug/examples/hello
For some more version info, here's the output of
arm-non-eabi-gdb --version
:And
openocd --version
:Openocd is indeed running and listening on the correct port, as per
netstat -tulpn | grep LISTEN
:Fix/workaround:
Seeing the
0.0.0.0
in there gave me the idea to try the following:This results in the output described in the book, and allows me to continue.
Perhaps it would help some if this solution was added as a note in the book.
A further note, the same applies to the gdb script
openocd.gdb
, changing the first line fromtarget extended-remote :3333
totarget extended-remote 0.0.0.0:3333
fixes the later part that hit the same issue.The text was updated successfully, but these errors were encountered: