openocd failed to connect to target

Post here first, or if you can't find a relevant section!
Post Reply
STM32_Newbbe
Posts: 50
Joined: Thu Nov 05, 2020 10:26 am

openocd failed to connect to target

Post by STM32_Newbbe »

I am trying to debug a Nucleo-L4R5 in sloeber/eclipse
I had it working a while ago, but now I get the following error output
xPack OpenOCD x86_64 Open On-Chip Debugger 0.11.0+dev (2022-03-25-17:32)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : auto-selecting first available session transport "hla_swd". To override use 'transport select <transport>'.
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
Info : DEPRECATED target event trace-config; use TPIU events {pre,post}-{enable,disable}
Started by GNU MCU Eclipse
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : clock speed 500 kHz
Info : STLINK V2J40M27 (API v2) VID:PID 0483:374B
Info : Target voltage: 3.241253
Error: init mode failed (unable to connect to the target)
And some additional info in a dialog:
Error in final launch sequence
Failed to execute MI command:
-target-select remote localhost:3333
Error message from debugger back end:
localhost:3333: Connection timed out.
Failed to execute MI command:
-target-select remote localhost:3333
Error message from debugger back end:
localhost:3333: Connection timed out.
localhost:3333: Connection timed out.
I followed the instructions here:
https://github.com/stm32duino/wiki/wiki/How-to-debug

I can normally program the Nucleo via STM32CubeProgrammer / Arduino IDE / sloeber-eclipse

The error is independent of the eclipse perspective I use

Is this hardware related or is something wrong with the GDB/openOCD part?
I am just starting to get into the subject...
Post Reply

Return to “General discussion”