Filippo Visocchi

USB on START-R Board

Discussion created by Filippo Visocchi on May 4, 2012
Latest reply on Aug 2, 2012 by Satya Satya

Hi all,

I'm currently using ltib with the patch linux-2.6.35.3-imx_11.09.01_201112 applied, as per MX53_LINUX_BSP_201112_Patch_release.pdf document. Maybe I'm doing something really wrong, but I can't have usb running, and dmesg tells me:

[    2.765806] Warning: unable to open an initial console.
[    2.766228] RAMDISK: ext2 filesystem found at block 0
[    2.766291] RAMDISK: Loading 5703KiB [1 disk] into ram disk... \
[    2.873475] mmc0: new high speed SD card at address 0007
[    2.874120] mmcblk0: mmc0:0007 SD01G 972 MiB
[    2.874538]  mmcblk0: p1 p2
[    2.878777] /
[    2.943605] usb 1-1: device descriptor read/64, error -71
[    2.944282] done.
[    3.128608] VFS: Mounted root (ext2 filesystem) on device 1:0.
[    3.128885] devtmpfs: mounted
[    3.129006] Freeing init memory: 180K
[    3.263448] usb 1-1: device descriptor read/64, error -71
[    3.493424] usb 1-1: new low speed USB device using fsl-ehci and address 3
[    3.546226] eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=0:00, irq=-1)
[    3.803314] usb 1-1: device descriptor read/64, error -71
[    4.223299] usb 1-1: device descriptor read/64, error -71
[    4.453318] usb 1-1: new low speed USB device using fsl-ehci and address 4
[    4.993266] usb 1-1: device not accepting address 4, error -71
[    5.113349] usb 1-1: new low speed USB device using fsl-ehci and address 5
[    5.543518] PHY: 0:00 - Link is Up - 100/Full
[    5.653288] usb 1-1: device not accepting address 5, error -71
[    5.653379] hub 1-0:1.0: unable to enumerate USB device on port 1
[    8.093355] ehci_fsl_bus_suspend, Host 1
[    8.094262] there is a device on the port

After that, I have the prompt but the usb keyboard is not running.
I'm seeing that the first usb error is printed before the initrd is loaded, too.
The board runs fine with the original mmc ( the one with Ubuntu factory loaded ).
Additionally, on the START Board ( the Dialog based one ) the same kernel runs fine, and usb is ok.

I have the same results using a kernel built outside ltib, with all the patches applied.
I'm stuck on this from yesterday, any guy has some hints, or a running .config file if this is the case?
Thank you in advance
Filippo

Outcomes