OpenOCD Open Failed

[mpm165]

Hello all,

 

I am trying to get started with the STM32F7 Discovery board and have been following this tutorial: https://visualgdb.com/tutorials/arm/stm32/stm32f7/. I was following along and everything was fine until I went to “Test OpenOCD Settings” in step 7. I get the error message that the ‘Open failed’ with the following log:

C:\Users\MICHAE~1\AppData\Local\VisualGDB\EmbeddedDebugPackages\com.sysprogs.arm.openocd\bin\openocd.exe -c “gdb_port 51240” -c “telnet_port 51241” -f interface/stlink-v2-1.cfg -f target/stm32f7x.cfg -c init -c “reset init” -c “echo VisualGDB_OpenOCD_Ready”
Open On-Chip Debugger 0.10.0 (2018-05-24) [https://github.com/sysprogs/openocd]
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
WARNING: interface/stlink-v2-1.cfg is deprecated, please switch to interface/stlink.cfg
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
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
Error: libusb_open() failed with LIBUSB_ERROR_NOT_FOUND
Error: open failed
in procedure ‘init’
in procedure ‘ocd_bouncer’

I have found similar issues but as this is the first time I am working on an embedded system outside of a classroom setting I am having trouble following solutions. I am using the most recent versions of VisualGDB and OpenOCD on Windows10 Pro-64. If anyone has any assistance I would greatly appreciate it.

Thank you,

Michael M.

[support]

Hi,

Please refer to the following page for instructions on troubleshooting this: https://visualgdb.com/support/nodevice

[mpm165]

Got it working, thank you very much.

[Reza1757]

I have similar problem, my code build correctly but in debug phase i have this problem.

C:\Users\REZA\AppData\Local\VisualGDB\EmbeddedDebugPackages\com.sysprogs.arm.openocd\bin\openocd.exe -c “gdb_port 49501” -c “telnet_port 49500” -f interface/stlink-v2.cfg -f target/stm32f1x.cfg -c “tcl_port 2048″-f” interface/stlink-v2.cfg -f target/stm32f1x.cfg -c init -c “reset” init” -c init -c “reset init” -c “echo VisualGDB_OpenOCD_Ready”
Open On-Chip Debugger 0.10.0 (2020-12-28) [https://github.com/sysprogs/openocd]
Licensed under GNU GPL v2
libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
WARNING: interface/stlink-v2.cfg is deprecated, please switch to interface/stlink.cfg
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
tcl_port [port_num]

 

how can i fixed it?

 

[support]

Unfortunately, it is hard to suggest anything specific based on the description you provided.
In order for us to provide any help with this, we need to be able to reproduce the problem on our side.
Please provide complete and detailed steps to reproduce the issue as described below:

1. The steps should begin with launching Visual Studio. They should include every step necessary to create the project from scratch and reproduce the issue.
2. Please make sure the steps do not involve any 3rd-party code as we will not be able to review it. If the problem only happens with a specific project, please make sure you can reproduce it on a clean project created from scratch.
3. The steps should include uncropped screenshots of all wizard pages, VisualGDB Project Properties pages and any other GUI involved in reproducing the problem. This is critical for us to be able to reproduce the problem on our side.

You can read more about the best way to report VisualGDB issues in our problem reporting guidelines, If you do not wish to document the repro steps and save the screenshots, please consider recording a screen video instead and sending us a link to it.

Please note that many VisualGDB issues are caused by selecting an incompatible combination of settings at some point. We are generally not able to review specific projects and find the specific settings that were set incorrectly. We recommend checking the projects into source control and keeping a track of all changed settings to avoid breaking the projects.

[Author]

Posts