openocd libusb errors with win 10

[unseenlaser]

anyone have a reliable fix for libusb errors ?, this has had me fighting for the last week
even used the zadig driver to install winusb(v6.1.7600.16385)
this is with a nucelo f401re

i seem to be going round in circles

using board nucelo_f4.cfg
my output is :

Open On-Chip Debugger 0.9.0-dev-00268-ga9c90a0 (2015-02-08-10:38)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.sourceforge.net/doc/doxygen/bugs.html
Warn : Interface already configured, ignoring
Error: already specified hl_layout stlink
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
adapter speed: 1800 kHz
adapter_nsrst_delay: 100
none separate
srst_only separate srst_nogate srst_open_drain connect_deassert_srst
Info : clock speed 1800 kHz
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Info : STLINK v2 JTAG v24 API v2 SWIM v11 VID 0x0483 PID 0x374B
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Info : STLINK v2 JTAG v24 API v2 SWIM v11 VID 0x0483 PID 0x374B
Info : using stlink api v2
Info : Target voltage: 3.238270
Info : stm32f4x.cpu: hardware has 6 breakpoints, 4 watchpoints

[Jacon]

And your reason for update to Win 10 right now was... ?

[unseenlaser]

what a stupid answer , i'm out of here for good , thats the attitude this forum believes in .

[Giovanni]

Cool, I love broad generalizations...

[avrhack]

what a stupid answer , i'm out of here for good , thats the attitude this forum believes in .

Yes it was an incredibly stupid answer and I can understand why it's so annoying, but it's only one person so as Giovani says, it's a bit daft to generalise like that. Lots of people - unlike that particular poster - are very helpful and especially Giovani who tends to answer very quickly.

Not directly relevant to your issue but I have found libusb-1.0.xx particularly unreliable compared to libusb-0.x which is strange as I tend to run libusb-0.x applications using the compatibility layer on top of..... libusb-1.0.xx! I'm assuming therefore that the issue lies with the way I'm using 1.0.xx.

Best advice I can give as I'm not on a windows platform is to turn on every bit of debugging you can find and then start hunting through the sources for libusb. That's one of the huge benefits of ChibiOS - you can dig through the source to figure out what's going on and 99% of the time it highlights where you're going wrong. On a very odd occasion it highlights a bug in the source which you can fix there and then without waiting for a new release - and of course submit a patch to the maintainers.

---- EDIT ----

Oh and for what it's worth I 'upgraded' my OSX from 10.10 Yosemite to 10.11 El Capitan and it's completely broken the st-link utility whereas everything else USB works fine, so I suspect there's something latent in libusb that worked on previous versions but has surfaced as a result of changes Apple made. The fact W10 seems to have broken your OpenOCD might indicate there's a common update to cover e.g. USB3.1 and libusb needs to be updated. Total guesswork as I haven't yet had time to follow the advice above i.e. get the source code out, turn on the debug and find out why libusb is so flakey

[yoyo-dev]

Hi,

I've moved my my bookpro to El captain, and this has broken my opened for STM32F2x : any idea how to fix this issue ?
GNU ARM Eclipse 64-bit Open On-Chip Debugger 0.9.0-dev-00355-gcb3893d (2015-03-20-20:05)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.sourceforge.net/doc/doxygen/bugs.html
jtag_ntrst_delay
adapter speed: 1000 kHz
adapter_nsrst_delay: 100
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
none separate
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : clock speed 950 kHz
Error: read version failed
in procedure 'init'
in procedure 'ocd_bouncer'
in procedure 'transport'
in procedure 'init'

[avrhack]

Hi,

I've moved my my bookpro to El captain, and this has broken my opened for STM32F2x : any idea how to fix this issue ?
GNU ARM Eclipse 64-bit Open On-Chip Debugger 0.9.0-dev-00355-gcb3893d (2015-03-20-20:05)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.sourceforge.net/doc/doxygen/bugs.html
jtag_ntrst_delay
adapter speed: 1000 kHz
adapter_nsrst_delay: 100
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
none separate
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : clock speed 950 kHz
Error: read version failed
in procedure 'init'
in procedure 'ocd_bouncer'
in procedure 'transport'
in procedure 'init'

Sorry I can't help on Windows 10, but on OSX it's just as broken so I've taken to using a VM running linux which still works perfectly. On the Mac it's pretty seamless but I appreciate on Windows it will be more of a pain to do that......

[Giovanni]

I cannot help with OSX but this reminds me the reason why I stayed with XP until 3 months ago, on the new PC I installed W7. I prefer the rest of the world to beta test for some years them before I make the step.

Thanks rest of the worlds

Giovanni

[avrhack]

I cannot help with OSX but this reminds me the reason why I stayed with XP until 3 months ago, on the new PC I installed W7. I prefer the rest of the world to beta test for some years them before I make the step.

Thanks rest of the worlds

Giovanni

Haha you are SO right. I don't know why the hell I "upgraded" to El Capitan when it all worked fine on Yosemite and there's no other material benefit I can see.