SDKv 1.7 and USB on boot up of P1010RDB

[yensid]

Hi,

We have a P1010RDB and our own PCB design which is very similar to the P1010RDB. I am in the process of upgrading to SDKv1.7 to add support for cloud services, specifically AWS (Amazon Web Servcies). After setting up v1.7 for the P1010RDB-PA, since we have an older dev kit, I loaded the new U-Boot, Kernel, and fsl-image-minimal rootfs.  If the RDB is booted with a thumb drive installed, the USB device is detetced continusouly until it is removed. If the thumb drive is connected after the system boots it works normally as expected.  I have also tried multiple thumb drives with different contents from different manufacturers and they all have this issue leading me to belive it is a possible driver or RDB-PA config issue. I have this same issue on our custom PCB board as well.

If you have any ideas please share them, and thanks!

   Here is a sample of the issue.  The full boot up is attached to this post.

Freeing unused kernel memory: 232K (c078c000 - c07c6000)

INIT: version 2.88 booting

usb 1-1: new high-speed USB device number 3 using fsl-ehci

Starting udev

udevd[1403]: starting version 182

usb 1-1: new high-speed USB device number 4 using fsl-ehci

usb 1-1: new high-speed USB device number 5 using fsl-ehci

usb 1-1: new high-speed USB device number 9 using fsl-ehci

usb 1-1: new high-speed USB device number 10 using fsl-ehci

usb 1-1: new high-speed USB device number 11 using fsl-ehci

usb 1-1: new high-speed USB device number 12 using fsl-ehci

usb 1-1: new high-speed USB device number 13 using fsl-ehci

usb 1-1: new high-speed USB device number 16 using fsl-ehci

usb 1-1: new high-speed USB device number 17 using fsl-ehci

Original Attachment has been moved to: Wakeup.txt.zip

[yipingwang · Accepted solution]

Hello yensid,

P1010 rev1.0 is affected by erratum A005275, it cannot be used in USB high-speed mode without problem. The workaround has already been applied in Linux USB driver, which forces high-speed devices to work in full-speed mode. But in SDK 1.7, this erratum workaround is not enabled by default, please refer the following lines in drivers/usb/host/fsl-mph-dr-of.c. So you need to define "fsl,usb-erratum-a005275" in the dts file, or mention it in hwconfig variable in u-boot command line.

/* Activate workaround for USB erratum-A00XXXX if

* fsl,usb-erratum-a00XXXX property is defined for

* affected socs

*/

if (of_get_property(np, "fsl,usb-erratum-a005275", NULL))

pdata->has_fsl_erratum_a005275 = 1;

else

pdata->has_fsl_erratum_a005275 = 0;

Have a great day,
Yiping

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------