Welcome, Guest

Author Topic: Yet another ARM-USB-OCD-H Windows driver question  (Read 1391 times)

resCat

  • Newbie
  • *
  • Posts: 2
  • Karma: +1/-0
Yet another ARM-USB-OCD-H Windows driver question
« on: September 20, 2017, 04:26:36 AM »

I've just spent several hours beating my head against windows driver installation for my Olimex ARM-USB-OCD-H and searching this forum for tips.
I'm using the debugger on a proprietary board that has an STM32F412. And I have the debugger working successfully on linux (ubuntu 14.04) so I'm confident that the board and debugger are working.

But attempts to find working drivers on Windows have eluded me. Below are details on versions and driver variants I've found and tried.

Any suggestions will be more than welcome at this point!


Versions:
Windows 8.1
OpenOCD 0.10.0-201610281609-dev  // I've tried both 32 and 64 bit versions
   
Drivers tried for both Olimex interfaces that enumerate(note that Windows automatic driver update is disabled per the recommendations elsewhere):
- WinUSB installed by Zadig-2.3 as recommended in the debugger manual https://www.olimex.com/Products/ARM/JTAG/_resources/ARM-USB-OCD_and_OCD_H_manual.pdf
- Olimex Drivers from this forum post: https://www.olimex.com/Products/ARM/JTAG/_resources/DRIVERS-(libusb-1.2.2.0-CDM20808).zip
- Olimex Drivers from this forum post: https://www.olimex.com/forum/index.php?topic=1465.0
- Tried cleaning all drivers using the FTClean utility mentioned in the manual and then repeating all of the above.
- After all that I tried the drivers that windows automatically finds.

I've tried with the old-style olimex-arm-usb-ocd-h.cfg (included in OpenOCD), which gives me the following error:

Code: [Select]
>C:\OpenOCD\0.10.0-201610281609-dev\bin\openocd.exe -f .\interface\olimex-arm-usb-ocd-h.cfg -f .\target\stm32f4x.cfg
GNU ARM Eclipse 64-bits Open On-Chip Debugger 0.10.0-dev-00498-gbbfb673 (2016-10-28-16:31)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
adapter speed: 2000 kHz
adapter_nsrst_delay: 100
jtag_ntrst_delay: 100
none separate
cortex_m reset_config sysresetreq
Warn : Using DEPRECATED interface driver 'ft2232'
Info : Consider using the 'ftdi' interface driver, with configuration files in interface/ftdi/...
Error: unable to open ftdi device: usb_open() failed

And with the ftdi/olimex-arm-usb-ocd-h.cfg (included in OpenOCD).

Code: [Select]
>C:\OpenOCD\0.10.0-201610281609-dev\bin\openocd.exe -f .\interface\ftdi\olimex-arm-usb-ocd-h.cfg -f .\target\stm32f4x.cfg
GNU ARM Eclipse 64-bits Open On-Chip Debugger 0.10.0-dev-00498-gbbfb673 (2016-10-28-16:31)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
adapter speed: 2000 kHz
adapter_nsrst_delay: 100
jtag_ntrst_delay: 100
none separate
cortex_m reset_config sysresetreq
Error: libusb_open() failed with LIBUSB_ERROR_NOT_FOUND
Error: no device found
Error: unable to open ftdi device with vid 15ba, pid 002b, description 'Olimex OpenOCD JTAG ARM-USB-OCD-H', serial '*' at bus location '*'

resCat

  • Newbie
  • *
  • Posts: 2
  • Karma: +1/-0
Re: Yet another ARM-USB-OCD-H Windows driver question
« Reply #1 on: September 20, 2017, 04:57:58 AM »
Ok, so 9th time is the charm.

I just carefully redid the Zadig WinUSB driver install from clean state and that worked (for both *.cfg files).

Specifically
1) Disable windows automatic driver updates (On Windows 8.1 you must be sure device installation settings has "No, let me choose"  AND "Never install..."  AND uncheck the box for replacing generic icons)
2) Uninstall (and delete) the existing Olimex drivers via the DeviceManager
3) Run FTClean
4) Run Zadag-2.3.exe and choose WinUSB.
« Last Edit: September 20, 2017, 05:02:16 AM by resCat »