i.MX ProcessorsのトピックUSB on START-R Board

USB on START-R Board

Filippo — Fri, 04 May 2012 13:38:35 GMT

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

Re: USB on START-R Board

RobertBrown — Mon, 07 May 2012 09:49:58 GMT

The Ubuntu 12.04 release has the same problem; see https://bugs.launchpad.net/ubuntu/+source/linux-linaro-lt-mx5/+bug/943058

I do hope it gets fixed soon: my iMX53QSB is gathering dust until it does.

Re: USB on START-R Board

Filippo — Mon, 07 May 2012 11:13:25 GMT

Somehow SOLVED

I've rebuilt ltib from start, I've applied all the patches and I've created a new mmc : usb runs, maybe I had some environment problems.

Then I've used a stock 2.6.35.3 kernel patched with all the patches from Freescale, built from a crosstool generated compiler and a buildroot created file system. Apart from some junk on the serial port until the login appears, everything runs fine too.

The junk appears after the dmesg line
mxcintuart.0: ttymxc0 at MMIO 0x53fbc000 (irq = 31) is a Freescale i.MX
until the prompt, but the prompt is correct.I will investigate further.

Anyway I still have that note that complains about USB_OTG and others, I will investigate this too.

So, Robert, I thank you very much for the info, is exactly what I was seeing in my wrong ltib.

Re: USB on START-R Board

Filippo — Mon, 07 May 2012 15:38:09 GMT

SOLVED

After removing the OTG stuff from the kernel .config, everything is ok, and the serial port too. I guess my problems on the serial port were from the board, after a powerup they are gone, and I'm pretty sure there are no relationship with OTG.

Re: USB on START-R Board

Satya1z — Thu, 02 Aug 2012 11:31:45 GMT

Hi Fillipo,

I am facing a similar problem with Freescale iMX21 eval board. I am trying to boot with linux kernel 3.2 we observed that USB-HCD and storage driver is registered properly. However USB UDC driver is not properly initializaed. During platform specific code initialization, during probe, UDC driver returns ENODEV. Due to no device is detected in the system. The same is the case with rtc driver.

Could you please help me out.

boot logs attached:

cs89x0:cs89x0_probe(0x0)
cs89x0.c: v2.4.3-pre1 Russell Nelson <nelson@crynwr.com>, Andrew Morton
eth0: cs8900 rev K found at 0xf5000000 [Cirrus EEPROM]
cs89x0 media RJ-45, IRQ 203, programmed I/O, MAC 00:04:9f:00:5c:07
cs89x0_probe1() successful
cs89x0:cs89x0_probe(0x0)
cs89x0: request_region(0xf5000000, 0x10) failed
cs89x0: no cs8900 or cs8920 detected. Be sure to disable PnP with SETUP
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
IMX21 USB Host Controller
*** imx21_probe: res_start = 0xc192a0e4, res->start
imx21-hcd imx21-hcd.0: Hardware HC revision: 0x20
imx21-hcd imx21-hcd.0: IMX21 USB Host Controller
imx21-hcd imx21-hcd.0: new USB bus registered, assigned bus number 1
imx21-hcd imx21-hcd.0: irq 55, io base 0x10024000
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
Satyajeeeeeeeet: enterred in udc_init
imx_udc: Return value is 0
imx_udc: Return value is -19
mxc_rtc: Return value is 0
mxc_rtc: Return value is -19
i2c /dev entries driver
Software Watchdog Timer: 0.07 initialized. soft_noboot=0 soft_margin=60 sec soft_panic=0 (nowayout= 0)
TCP cubic registered
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
imx21-hcd imx21-hcd.0: Hub status changed
usb 1-2: new full speed USB device number 2 using imx21-hcd
usb 1-2: device not accepting address 2, error -110
In udev->wusb logic
imx21-hcd imx21-hcd.0: Hub status changed
usb 1-2: new full speed USB device number 3 using imx21-hcd
eth0: using half-duplex 10Base-T (RJ-45)
IP-Config: Complete:

Filippo said:

SOLVED
After removing the OTG stuff from the kernel .config, everything is ok, and the serial port too. I guess my problems on the serial port were from the board, after a powerup they are gone, and I'm pretty sure there are no relationship with OTG.