Olimex Support Forum

ARM => JTAG => Topic started by: gsmith246 on September 09, 2020, 05:58:11 pm

Title: WIn10 divers issue
Post by: gsmith246 on September 09, 2020, 05:58:11 pm
Dispite days of dirver installs un-installs and reading I still can't get openOCD to work with my Olimex-ARM-USB-OCD-H.
Done Zadig set drivers to WinUSB (v6.1.7600.16385)
But still get :

Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Title: Re: WIn10 divers issue
Post by: LubOlimex on September 10, 2020, 08:46:09 am
This seems like driver mismatch or error.

It seems that you installed the WinUSB driver for OpenOCD. However, note that ARM-USB-OCD-H has two serial interfaces -> one interface for the COM port near the USB connector, and another one for the JTAG interface. It is possible that you installed the driver only for the COM port, leaving the JTAG interface without a driver. Make sure that both these interfaces have WinUSB driver installed (there is an option in Zadig to show all devices, make sure that both interfaces of ARM-USB-OCD-H have the same driver).

Note that OpenOCD can be compiled with different driver support. Yes, WinUSB drivers are recommended now but you can also compile OpenOCD with the option to work with the older LibUSB drivers. It would depend where you got OpenOCD from. Also which version. Try with these versions:

https://www.olimex.com/Products/ARM/JTAG/_resources/OpenOCD-OLIMEX-WINDOWS.zip


Finally, make sure that you use the configuration file "olimex-arm-usb-ocd-h.cfg" for ARM-USB-OCD-H found in FTDI subfolder ("...openocd-0.9.0\scripts\interface\ftdi").

I've tested ARM-USB-OCD-H with the WinUSB drivers and this release of OpenOCD compiled by Freddie Chopin: http://www.freddiechopin.info/en/download/category/4-openocd?download=118%3Aopenocd-0.9.0 - you can test the setup directly via OpenOCD initially as described in ARM-USB-OCD-H's user's manual.
Title: Re: WIn10 divers issue
Post by: gsmith246 on September 11, 2020, 12:04:27 pm
Thanks for your replay. Just for info :

Open On-Chip Debugger  v0.10.0-esp32-20190708 (2019-07-08-11:04)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
adapter speed: 1000 kHz
Info : Configured 2 cores
esp32 interrupt mask on
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Info : clock speed 1000 kHz
Error: JTAG scan chain interrogation failed: all ones
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: esp32.cpu0: IR capture error; saw 0x1f not 0x01
Warn : Bypassing JTAG setup events due to errors
Info : Listening on port 3333 for gdb connections

USB : Driver Version 6.1.7600.16385 (both ports)
Title: Re: WIn10 divers issue
Post by: LubOlimex on September 11, 2020, 04:51:05 pm
I see you are using some specific OpenOCD made for ESP32 chips. What environment are you using? Most environments have own guides for driver installation for supported tools. For example for PlatformIO and ARM-USB-OCD-H look here:

https://docs.platformio.org/en/latest/plus/debug-tools/olimex-arm-usb-ocd-h.html