![]() ![]() ![]() I've tested ARM-USB-OCD-H with the WinUSB drivers and this release of OpenOCD compiled by Freddie Chopin: - you can test the setup directly via OpenOCD initially as described in ARM-USB-OCD-H's user's manual. Try with these versions:įinally, 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"). It would depend where you got OpenOCD from. Yes, WinUSB drivers are recommended now but you can also compile OpenOCD with the option to work with the older LibUSB drivers. Note that OpenOCD can be compiled with different driver support. 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). Heres a rundown of what took place immediately before it stopped working: Installed Zadig Using Zadig, selected Intel Wireless Bluetooth (R) Replaced driver to 'libusbK (v3.0.7.0)' Things were working fine and as intended but when i restarted my computer the device was missing and i couldnt pair anything. It is possible that you installed the driver only for the COM port, leaving the JTAG interface without a driver. 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 seems that you installed the WinUSB driver for OpenOCD. This seems like driver mismatch or error. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |