# OpenOCD 0.1.0 with olimex ARM-USB-TINY-H problem **URL:** \ **Category:** MicroMod\ **Tags:** arm-lpc\ **Created:** [November 8, 2010, 11:40am UTC](https://community.sparkfun.com/t/openocd-0-1-0-with-olimex-arm-usb-tiny-h-problem/18096 "2010-11-08T11:40:05Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![blondie](https://avatars.discourse-cdn.com/v4/letter/b/a4c791/32.png) [@blondie](https://community.sparkfun.com/u/blondie)\ **Post date:** [November 8, 2010, 11:40am UTC](https://community.sparkfun.com/t/openocd-0-1-0-with-olimex-arm-usb-tiny-h-problem/18096/1 "2010-11-08T11:40:05Z")
Hi there I am using OpenOCD 0.1.0 with olimex ARM-USB-TINY-H and an STM32F103 device along with the config file from openOCD directories: interface/olimex-jtag-tiny.cfg I get the following errors: * * * Open On-Chip Debugger 0.1.0 (2009-01-21-21:15) Release BUGS? Read [http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS](http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS) $URL: [https://kc8apf@svn.berlios.de/svnroot/r … /openocd.c](https://kc8apf@svn.berlios.de/svnroot/repos/openocd/tags/openocd-0.1.0/src/openocd.c) $ jtag\_speed: 50 500 kHz Error: unable to open ftdi device: 2 Runtime error, file “pp\_Program.cfg”, line 58: #cmd.exe /C program.bat * * * My code works OK with the Olimex parallel port JTAG wiggler or with an Amontec USB JTAG wiggler on a couple of computers. Therefore, I am sure that my problem is either a faulty unit or the wrong drivers for the FTDI chip. I have used the drivers off the supplied Olimex CD, but these don’t work for me. Also, I have used the ‘driver-libftdi-openocd.zip’ - ‘drivers for working with OpenOCD 0.1.0’ from the Olimex website, but these don’t work either. Is there anything else I can try before sending back the ‘faulty’ unit? Thanks ---
**Author:** ![stefmaster](https://avatars.discourse-cdn.com/v4/letter/s/ee7513/32.png) [@stefmaster](https://community.sparkfun.com/u/stefmaster)\ **Post date:** [November 9, 2010, 8:19am UTC](https://community.sparkfun.com/t/openocd-0-1-0-with-olimex-arm-usb-tiny-h-problem/18096/2 "2010-11-09T08:19:40Z")
hi, it might be a driver problem. You could try a newer version of openocd. for example 0.4.0. You can get a compiled version for windows on [http://www.freddiechopin.info](http://www.freddiechopin.info) The versions submitted on that page contains the libftdi drivers. greetings ---
**Author:** ![ernestw](https://avatars.discourse-cdn.com/v4/letter/e/9dc877/32.png) [@ernestw](https://community.sparkfun.com/u/ernestw)\ **Post date:** [November 23, 2010, 3:38am UTC](https://community.sparkfun.com/t/openocd-0-1-0-with-olimex-arm-usb-tiny-h-problem/18096/3 "2010-11-23T03:38:42Z")
Hello All, I am at a similiar stage getting OpenOCD to work with an Olimex ARM-USB-Tiny-H. (I have not used this device before - more of an AVR fan in the past) There are a few things you might find useful 1. Correct device VID & PID (from my .cfg file) # REFERENCE: [ARM-USB-TINY](http://www.olimex.com/dev/arm-usb-tiny.html) interface ft2232 ft2232\_device\_desc “Olimex OpenOCD JTAG TINY” ft2232\_layout “olimex-jtag” ft2232\_vid\_pid 0x15BA 0x002a Note the PIDs could be 0003 0004 as well - you can use USBviewer.exe to get this info. 1. I am using version OpenOCD 0.3.0. The commands and their syntax changes significantly between OpenOCD version releases. Be aware! 2. Speed - try slow ft2232\_latency 10 jtag\_khz 200 jtag\_speed is the command format for older versions of OpenOCD. should be Clk speed/200khz (between 30 and 150??) Note the addition of latency (in ms). Should be between 2 and 10. Not certain if available in version 0.1.0 1. Reset Configuration No idea what your board has. SRST and TRST may be available separately. I use reset\_config trst\_and\_srst separate jtag\_ntrst\_delay 200 jtag\_nsrst\_delay 200 Note delay parameters (ms) - some boards need resets help for a short time to work. 1. Drivers Almost certainly the real problem. Need to know if 32-bit or 64-bit OS. The Olimex drivers are only for 32-bit. If you are using 64-bit OS then Olimex say to use FTDI 64-bit drivers. However the FTDI website drivers are only certified for FTDI chip VID & PIDs. So cannot install on Vista as if wants certified drivers. There are versions of FTDI drivers with correct hardware VID & PIDs (which I have just found/loaded). See [http://www.olimex.com/dev/index.html](http://www.olimex.com/dev/index.html) Software Item 2. (The Crossworks FTD2xx drivers) Having said all of the above and now trying these last FTD2xx drivers… I am still getting “unable to open FTDI device: Device not found” error. I am about to try a Windows XP 64-bit and Windows XP 32-bit OS to see if I can get around the problem. I would appreciate any help I can get. Ernest