Debugger won't start

I’m tying to debug on the STM32F469IDiscovery but without any success, i thought that as long as a board is supported this should just work - clearly i am missing something.

I get the following message after a successful compile.


And the following message in the debug-console.

Reading symbols from c:/…/.pioenvs/disco_f469ni/firmware.elf…
PlatformIO Unified Debugger > Redirecting...
PlatformIO: Initializing remote target…
GNU MCU Eclipse 64-bits Open On-Chip Debugger 0.10.0+dev-00392-gbe9ef0b0 (2018-01-12-15:03)
Licensed under GNU GPL v2
For bug reports, read
OpenOCD: Bug Reporting
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
none separate
srst_only separate srst_nogate srst_open_drain connect_deassert_srst
Info : tcl server disabled
Info : telnet server disabled
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_SUPPORTED
Error: libusb_open() failed with LIBUSB_ERROR_NOT_FOUND
Error: open failed
in procedure ‘init’
in procedure ‘ocd_bouncer’
.pioinit:12: Error in sourced command file:
Remote communication error. Target disconnected.: Success.

Any ideas what might be wrong?

Did you install ST-Link drivers? See ST-LINK — PlatformIO latest documentation

1 Like

I sorted this - problem was indeed driver related - but not st-link - it was libusb - in case anyone else runs into this problem.

I should just point out that platformio is too slow to use. It takes 30-40 seconds to fire up the debugger, builds are slow, it hangs my VI extension all the time, the intellisense is barely functional. It’s a pity because it shows real promise as an IDE - i’ll come back and look in 6 months maybe.

It is really the driver problem. I encountered the problem (LIBUSB_ERROR_NOT_FOUND) when uploading the mbed program to a st nucleo-f412 board today, then I get the software STSW-LINK009 from, after installing it, the problem fixed.
Thank you, ivankravets.

1 Like