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

[Xiaofan C. <xia...@gm...>]

On Thu, Jul 22, 2021 at 2:14 PM R. Diez <rdi...@ya...> wrote:
>
>
> > [...]
> > One quick suggestion that you can give it a shot. I saw this issue
> > last time with my old desktop. Please use Zadig to install WinUSB
> > driver (not using ST's original WinUSB driver). And then try again.
>
> That is the first thing I tried before reinstalling the ST driver, because I was used to Zadig being necessary.
>
> I think that my oldish PC with Windows 7 will remain with OpenOCD v0.10.0
>  for the time being. If no such issues occur with Windows 10
> anymore, then it is not a big deal to worry about.
>
> Thanks again for all the information,

Yes that is a good option since Openocd V0.10 work for you on the
Windows 7 PC.

Since this is not related to Ticket 308,
https://sourceforge.net/p/openocd/tickets/308/
I tend to think this is more related to libusb issues with your
Windows 7 PC, especially none of your devices work with the
OpenOCD 0.11 binary with libusb-1.0.23.

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.

-- 
Xiaofan