OpenOCD st-link v2 just hangs instead of debugging

[MajesticRa]

1. After working for some (short) period of time OpenOCD stops going into the debug mode.
It just hangs in “Waiting for debug method to start” window

Here is the result from VisualGDB diagnostics window

VisualGDB build 5.3.13.1864
Startup initialization took 899 msec
Searching for active configuration for MathLifeSupport.vcxproj...
Trying fast lookup...
Found! Configuration name = Debug
Launching gdbserver...
Launching C:\Users\***\AppData\Local\VisualGDB\EmbeddedDebugPackages\com.sysprogs.arm.openocd\bin\openocd.exe -c "gdb_port 50701" -c "telnet_port 50702" -f interface/stlink-v2.cfg -c "transport select hla_swd" -f target/stm32f7x.cfg -c init -c "reset init" -c "echo VisualGDB_OpenOCD_Ready"...

If I hit “Test” button in OpenOCD project configuration window I get:

Open On-Chip Debugger 0.10.0 (2017-08-05) [https://github.com/sysprogs/openocd]
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
hla_swd
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
adapter speed: 2000 kHz
adapter_nsrst_delay: 100
srst_only separate srst_nogate srst_open_drain connect_deassert_srst
Info : Unable to match requested speed 2000 kHz, using 1800 kHz
Info : Unable to match requested speed 2000 kHz, using 1800 kHz
Info : clock speed 1800 kHz

then it hangs with the sign
“Waiting for the stub to initialize”

The Terminate button doesn’t do anything

2. After this I see openocd.exe in the task manager and cannot kill it.

3. Reboot helps. Closing and opening visual studio – doesn’t.

4. When it hangs I can run ST-Link utility and read/program the device, no problems.

5. I’m using:
– STLink v2 with the latest firmware update
– controller STMF7xxx
– Visual Studio 17 community 15.4.0
– OS Windows 10 home 1709 16299.19

P.S. OpenOCD 2017-08-05 because I tried to downgrade it in the hope it would help.

• This topic was modified 7 years, 2 months ago by MajesticRa.
• This topic was modified 7 years, 2 months ago by MajesticRa.

[support]

Hi,

If killing OpenOCD via task manager doesn’t work, this looks like a USB driver/controller bug. Please try using a different USB port or a different computer. Also if you are using a VM, please try running it on real hardware instead as USB virtualization is sometimes buggy.

[MajesticRa]

Hi!

1. Tried to uninstall the ST-link driver – reboot – reinstall – reboot

2. Tried to switch to USB2.0 port, then USB3.0 port. I connect it directly to motherboard without any additional usb hubs.

Both times it started hanging after several times going to the debug mode.

I have a laptop with approximately the same setup but with Windows 10 pro, it works there fine
(with the same programmer, the programmer usb cable and a controller).

Thank you for the quick reply!
Dmitry

[support]

Hi,

Thanks for checking this. It could be a motherboard bug or a driver bug then. If it works reliably on a laptop, we would simply recommend using the laptop then.

[Author]

Posts