I'm using an Olimex ARM-USB-OCD target interface and when I try and connect I get a "Cannot find USB device (vid=0x15BA, pid=0x0003, serial=, channel=0)" error message. What does this mean?
This error applies to all FTDI FT2232 based target devices and indicates that you don't have an appropriate device driver installed.
If you don't have a driver installed then obtain one from the device's vendor and install it.
Another possibility is that you have an incorrect device driver installed - this can happen if you have used OpenOCD as this software now no longer uses the standard FTDI device drivers by default for licensing reasons. If this is the case you will need to uninstall the LibUSB drivers that OpenOCD uses and re-install the FTDI device drivers. If you are using Windows Vista or Windows 7 you should be able to uninstall the driver by right clicking the device in the Windows device manager and selecting Uninstall making sure to select the Delete the driver software for this device option. If you are using a version of Windows prior to Vista you will not have the Delete the driver software for this device option, in which case you will have to do this manually as follows:
- Look in the C:\Windows\inf directory for a .inf file containing the string libusb-win32_ft2232_driver.
- The file will probably be called something like oemn.inf and there should also be a oemn.PNF file with the same value of n, delete both of these files.
Once you have uninstalled and removed the LibUSB driver you should be able to plug the device in again and install the FTDI driver.
Comments
2 comments
I have a similar problem with TI Evalbot and Stellaris ICDI target. Build error: "Cannot find any device with VID 0x1cbe, PID 0x00fd"
The FTDI driver was up-to-date (I re-installed v2.6.00). I do not see OpenOCD/LibUSB. The target builds and loads properly with Keil MDK-ARM.
Is there a debugger configuration in CW?
There is similar case you get USB FTDI error:
cannot find FTDI driver for USB device (vid=0x0403, pid=0xA6D1, serial=, channel=0)
I am using XDS100 v3 for Sitara ( AM3352) processor. I get this error each time I have another FTDI base device connected to my PC ( I do have at least 3 serial port FTDI based devices). It does not matter what driver is being used - even if the same version of driver is used by all devices ( including my XDS100) this problem persists. It does not matter that the device PID is different ( just VID is the same as it supposed to be)
BUT - If you e.g. open these serial ports ( with terminal program), this error disappears, then you can connect without any problems.
I am not sure if this specific to XDS100, but the nature suggest wider problem ( bug?) in handling FT2232 based devices.
Please sign in to leave a comment.