# Unable to open ftdi device **URL:** \ **Category:** MicroMod\ **Tags:** arm-lpc\ **Created:** [December 2, 2008, 11:11am UTC](https://community.sparkfun.com/t/unable-to-open-ftdi-device/9244 "2008-12-02T11:11:14Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Gaurang](https://avatars.discourse-cdn.com/v4/letter/g/cdc98d/32.png) [@Gaurang](https://community.sparkfun.com/u/Gaurang)\ **Post date:** [December 2, 2008, 11:11am UTC](https://community.sparkfun.com/t/unable-to-open-ftdi-device/9244/1 "2008-12-02T11:11:14Z")
Dear All, I am using ARM-USB-OCD JTEG tool and Eclipse 3.3 platform, When i run a sample program to stm32f103\_stk using OpenOCD i got the following error Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 CEST) Error: ft2232.c:1341 ft2232\_init\_ftd2xx(): unable to open ftdi device: 2 Error: ft2232.c:1356 ft2232\_init\_ftd2xx(): ListDevices: 2 Error: ft2232.c:1358 ft2232\_init\_ftd2xx(): 0: Olimex OpenOCD JTAG B Error: ft2232.c:1358 ft2232\_init\_ftd2xx(): 1: V\> Can anyone help me Thanks in advance. Gaurang ---
**Author:** ![carrejans](https://avatars.discourse-cdn.com/v4/letter/c/9e8a1a/32.png) [@carrejans](https://community.sparkfun.com/u/carrejans)\ **Post date:** [December 8, 2008, 11:26pm UTC](https://community.sparkfun.com/t/unable-to-open-ftdi-device/9244/2 "2008-12-08T23:26:58Z")
I have the same error. ```auto Error: ft2232.c:1065 ft2232_init(): unable to open ftdi device: 2 Error: ft2232.c:1080 ft2232_init(): ListDevices: 2 Error: ft2232.c:1082 ft2232_init(): 0: Symphony SoundBite A Error: ft2232.c:1082 ft2232_init(): 1: Symphony SoundBite B ``` I tried solving the problem all day and night. Searched the entire net too. šŸ™‚ But no solution. ā˜¹ - I tried to reinstall driver - I tried to change the pid number in the cfg file - I tried to change the name in the cfg file - ā€¦ Nothing worked. My configuration file: ```auto #daemon configuration telnet_port 23 gdb_port 9998 #interface interface ft2232 ft2232_device_desc "Symphony Soundbite A" ft2232_layout "soundbite" ft2232_vid_pid 0x0403 0x6010 jtag_speed 2 # was 2 #use combined on interfaces or targets that can't set TRST/SRST separately reset_config trst_and_srst #jtag scan chain #format L IRC IRCM IDCODE (Length, IR Capture, IR Capture Mask, IDCODE) jtag_device 4 0x1 0x3 0x2 #target configuration daemon_startup reset #target target dsp56374 big run_and_halt 0 ``` Please, someone help us! ---
**Author:** ![ntfreak](https://avatars.discourse-cdn.com/v4/letter/n/ee7513/32.png) [@ntfreak](https://community.sparkfun.com/u/ntfreak)\ **Post date:** [December 9, 2008, 8:30pm UTC](https://community.sparkfun.com/t/unable-to-open-ftdi-device/9244/3 "2008-12-09T20:30:02Z")
carrejans, openocd supports various ftdi based dongles, but i am not aware of any support for a ft2232\_layout ā€œsoundbiteā€ you will have to speak to freescale and ask where the src is, or look at the schematic and try and add the interface. Cheers Spen ---
**Author:** ![KiZZo](https://avatars.discourse-cdn.com/v4/letter/k/7bcc69/32.png) [@KiZZo](https://community.sparkfun.com/u/KiZZo)\ **Post date:** [December 17, 2008, 9:03am UTC](https://community.sparkfun.com/t/unable-to-open-ftdi-device/9244/4 "2008-12-17T09:03:38Z")
Hello, sorry if Iā€™m asking some stupid question, but Iā€™m a total newb to ARM and OCD and Iā€™m trying to run my ā€œHello Worldā€. I have the same problem. Iā€™m using ARM-USB-TINY and STM32-103STK and the message I get when I run external tool is: ```auto Open On-Chip Debugger 1.0 (2008-10-15-13:12) svn:exported $URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $ Info: options.c:50 configuration_output_handler(): jtag_speed: 10, 10 Info: options.c:50 configuration_output_handler(): Open On-Chip Debugger 1.0 (2008-10-15-13:12) svn:exported Error: ft2232.c:1375 ft2232_init_ftd2xx(): unable to open ftdi device: 2 Error: ft2232.c:1390 ft2232_init_ftd2xx(): ListDevices: 2 Error: ft2232.c:1392 ft2232_init_ftd2xx(): 0: Olimex OpenOCD JTAG TINY A Error: ft2232.c:1392 ft2232_init_ftd2xx(): 1: Olimex OpenOCD JTAG TINY B ``` I tried using the other external tool (openocd-ftd2xx.exe) and then it seems to start but I get error when I try to debug. ---
**Author:** ![csabi911](https://avatars.discourse-cdn.com/v4/letter/c/85f322/32.png) [@csabi911](https://community.sparkfun.com/u/csabi911)\ **Post date:** [March 1, 2009, 10:49pm UTC](https://community.sparkfun.com/t/unable-to-open-ftdi-device/9244/5 "2009-03-01T22:49:48Z")
Hi Kizzo, The configuration file that you are trying to use is for the Freescale Soundbite board. I donā€™t think thatā€™s gonna work with your ARM JTAG debugger. Csaba ---
**Author:** ![jaripetteri](https://avatars.discourse-cdn.com/v4/letter/j/73ab20/32.png) [@jaripetteri](https://community.sparkfun.com/u/jaripetteri)\ **Post date:** [May 18, 2009, 6:15pm UTC](https://community.sparkfun.com/t/unable-to-open-ftdi-device/9244/6 "2009-05-18T18:15:34Z")
I have exact same problem here, have you find out how to use ARM-USB-OCD? ---
**Author:** ![mlu](https://avatars.discourse-cdn.com/v4/letter/m/f07891/32.png) [@mlu](https://community.sparkfun.com/u/mlu)\ **Post date:** [May 20, 2009, 11:56pm UTC](https://community.sparkfun.com/t/unable-to-open-ftdi-device/9244/7 "2009-05-20T23:56:21Z")
Under windows it is usually a driver installation problem If you are using Linux it is often a problem of setting access rights to the usb device, usually using a udev rule, this has been discussed in the lists (or google). ---
**Author:** ![fpaolo63](https://avatars.discourse-cdn.com/v4/letter/f/5daacb/32.png) [@fpaolo63](https://community.sparkfun.com/u/fpaolo63)\ **Post date:** [March 5, 2010, 8:27pm UTC](https://community.sparkfun.com/t/unable-to-open-ftdi-device/9244/8 "2010-03-05T20:27:20Z")
Hi guys this work for me: on /etc/fstab I add # amontec jtag none /proc/bus/usb usbfs **auto,users,** mode=0666 0 0 instead of none /proc/bus/usb usbfs **default,** mode=0666 0 0 **auto** and **users** (group my uid belongs) make the diff šŸ˜‰ pf