Re: [OpenOCD-user] FTDI and ST-Link V2 problems with OpenOCD 0.11.0 on Windows

[R. D. <rdi...@ya...>]

> [...]
> Friddie Choppin's OpenOCD 0.10.0 binary works with
> your PC but it is using libusb-1.0.21. You can actually
> replace the libusb-1.0.dll in his binary with libusb-1.0.23
> and 1.0.24 to see if that works. If that works, maybe there
> is an issue with OpenOCD codes. If that does not work,
> the issue is more with libusb-1.0 Windows code on your PC.


I've done a few more tests, for the record, in case it helps in the future.

I got the ST-Link on my NUCLEO-F072RB to work with OpenOCD v0.10.0 on the oldish Windows 7 PC by using "-f interface/stlink-v2-1.cfg", 
because that board actually has an ST-Link V2.1 (instead of V2).

I renamed libusb-1.0.dll from OpenOCD v0.10.0, which is version 1.0.21.11156, and that of course made it fail with "cannot open shared 
object file" (I'm just being paranoid).

I then copied libusb-1.0.dll from libusb-1.0.24\MinGW32\dll , which is version 1.0.24.11584, and it worked.

I replaced it with the version from openocd-v0.11.0-i686-w64-mingw32\bin , which is 1.0.23.11397, and I got "Error: open failed".


So I went to snapshot openocd-20b29b776-i686-w64-mingw32, which should be post v0.11.0 . With the original libusb-1.0.dll, which is version 
1.0.23.11397 too, it did not work, I got the usual "Error: open failed".

I then copied libusb-1.0.dll from libusb-1.0.24\MinGW32\dll , which is version 1.0.24.11584, and it did not work either, same problem (!).

I downgraded libusb-1.0.dll to the same version shipped with OpenOCD v0.10.0, which is version 1.0.21.11156, and it did not work either, 
same problem.


So, either my oldish Windows 7 PC has a Gremlin rummaging inside, or perhaps:

a) libusb-1.0.dll was temporarily broken somewhere between 1.0.21.11156 and 1.0.24.11584 for OpenOCD v0.10.0.

b) OpenOCD v0.11.0 is using some new or different feature/method in libusb-1.0.dll, and that new way reliably fails on my oldish Windows 7 PC.
If you have already seen something like that in the past, that means that this PC is not alone.
Let's hope that this kind of trouble does not happen anymore on newer Windows versions.

Regards,
   rdiez