EmbeddedRelated.com
Forums
The 2024 Embedded Online Conference

lpc2148 USB driver not working in Linux

Started by Manisha Kalita May 9, 2006
Hi all,

i am designing a USB driver in lpc2148 board. the driver is working fine
with Windows OS in the host. but whenever, we connect the board in a linux
host machine, it is giving the following problem.

May 9 17:29:49 localhost kernel: usb 2-2: new full speed USB device using
address 12
May 9 17:29:54 localhost kernel: usb 2-2: control timeout on ep0in
May 9 17:29:55 localhost kernel: usb 2-2: device descriptor read/all,
error -110
May 9 17:29:55 localhost kernel: usb 2-2: new full speed USB device using
address 13
May 9 17:30:00 localhost kernel: usb 2-2: control timeout on ep0in

the device is enumerated properly in host machine with windows OS. then why
in linux it is not recognizing the device?
Can anyone help me in this regard?

Regards,
Manisha
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s)and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender or a...@tataelxsi.co.in




An Engineer's Guide to the LPC2100 Series

Manisha Kalita wrote:
> Hi all,
>
> i am designing a USB driver in lpc2148 board. the driver is working fine
> with Windows OS in the host. but whenever, we connect the board in a linux
> host machine, it is giving the following problem.
>
> May 9 17:29:49 localhost kernel: usb 2-2: new full speed USB device using
> address 12
> May 9 17:29:54 localhost kernel: usb 2-2: control timeout on ep0in
> May 9 17:29:55 localhost kernel: usb 2-2: device descriptor read/all,
> error -110
> May 9 17:29:55 localhost kernel: usb 2-2: new full speed USB device using
> address 13
> May 9 17:30:00 localhost kernel: usb 2-2: control timeout on ep0in
>
> the device is enumerated properly in host machine with windows OS. then why
> in linux it is not recognizing the device?
> Can anyone help me in this regard?

Probably a bug in the device firmware that is triggered by Linux but
not by Windows.

Have you tried running the USBCV (compliance verifier) tool with your
device? It's at http://www.usb.org/developers/tools
It should at least pass the chapter 9 tests.
The latest version of the tool (1.3beta) even includes some class
specific tests, like HID and mass storage.

To use the tool you also need an EHCI controller and a high-speed hub.

Regards,
Bertrik

The 2024 Embedded Online Conference