Anilrgowda

Hi, I have a problem. Here are my OS details:

OS: Redhat Linux version 9
Kernel: 2.4.20-8

Problem:

I am currently a student and was tasked a "JTAG PROGRAMMING ACCELERATOR FOR USB LINK" project. The language of choice was C.

I was given a FTDI device using the FT245BM chip. I went to "www.intra2net.com/de/produkte/opensource/ftdi/" to download the libftdi driver and "libusb.sourceforge.net/ " to download the libusb driver. After the usual ./configure, make, make install. I was able to compile all programs that used the 'ftdi.h' or 'usb.h' header files. Everything seemed to be fine, until I plugged in the FTDI device via a USB cable.

Somehow, the particular device could not be found/detected. After the command 'dmesg' was typed, this was what was printed on the screen:

=====================================================================================
hub.c: new USB device 00:1d.1-1, assigned address 4
usb-uhci.c: interrupt, status 2, frame# 1208
usb.c: USB device not accepting new address=4 (error=-110)
hub.c: new USB device 00:1d.1-1, assigned address 5
usb.c: USB device not accepting new address=5 (error=-110)
=====================================================================================

I tried all the USB ports on my computer and still this was the message that I received.

My professor suggested that I check /etc/hotplug/usb.handmap or /etc/hotplug/usb.usermap.

Can you guys please help me? I am a novice Linux user and just learned using it about 3 weeks back. I really need to get this device detected as soon as possible for me to get this project going.

If there is any information that you guys need pls let me know and probably tell me where I can get this information that you need (remember, I am a beginner linux user).

------------------

Anilrgowda

soln
As far as I know, the -110 error can be caused by a faulty USB device. On some cases, disconnection, on some others, controller or driver. I would recommend you'd try to connect the device to some other USB enabled system, or try using live CD for the task (such as KNOPPIX, for example) - just for the test.

My bet, since you have changed the ports, is that the device itself is faulty.

------------------