imx6qdlsabresd: USB OTG issue with u-boot-imx 2022.04

SebastienFabre · ‎12-02-2022

I am working on imx6qdlsabresd on yocto kirstone.

When using u-boot-imx (2022.04), I have some issues with usb otg. If I connect a mouse to the USB OTG port, after moving it several seconds (less than 1 minute), no more event is sent (can be seen with evtest tool) and the port is reset (after several seconds).

[ 44.546052] usb 2-1: new low-speed USB device number 3 using ci_hdrc
[ 44.752376] usb 2-1: New USB device found, idVendor=093a, idProduct=2510, bcdDevice= 1.00
[ 44.760745] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 44.768014] usb 2-1: Product: USB Optical Mouse
[ 44.772580] usb 2-1: Manufacturer: PixArt
[ 44.783470] input: PixArt USB Optical Mouse as /devices/platform/soc/2100000.bus/2184000.usb/ci_hdrc.0/usb2/2-1/2-1:1.0/0003:093A:2510.0002/input/input8
[ 44.797440] hid-generic 0003:093A:2510.0002: input: USB HID v1.11 Mouse [PixArt USB Optical Mouse] on usb-ci_hdrc.0-1/input0
[ 107.516305] random: crng init done
[ 107.519743] random: 2 urandom warning(s) missed due to ratelimiting
[ 124.468579] usb 2-1: USB disconnect, device number 3
[ 126.006006] usb 2-1: new low-speed USB device number 4 using ci_hdrc
[ 126.212860] usb 2-1: New USB device found, idVendor=093a, idProduct=2510, bcdDevice= 1.00
[ 126.221146] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 126.228384] usb 2-1: Product: USB Optical Mouse
[ 126.232946] usb 2-1: Manufacturer: PixArt
[ 126.243987] input: PixArt USB Optical Mouse as /devices/platform/soc/2100000.bus/2184000.usb/ci_hdrc.0/usb2/2-1/2-1:1.0/0003:093A:2510.0003/input/input9
[ 126.257914] hid-generic 0003:093A:2510.0003: input: USB HID v1.11 Mouse [PixArt USB Optical Mouse] on usb-ci_hdrc.0-1/input0

Moreover, sometimes, several seconds (less than 1 minute) after connecting usb stick (no mount performed), the port is reset.

[ 170.476078] usb 2-1: new high-speed USB device number 5 using ci_hdrc
[ 170.678240] usb 2-1: New USB device found, idVendor=21c4, idProduct=0cd1, bcdDevice=11.00
[ 170.686520] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 170.693721] usb 2-1: Product: USB Flash Drive
[ 170.698150] usb 2-1: Manufacturer: Lexar
[ 170.702098] usb 2-1: SerialNumber: 04PAH98A4QFYZNI9
[ 170.709168] usb-storage 2-1:1.0: USB Mass Storage device detected
[ 170.715847] scsi host1: usb-storage 2-1:1.0
[ 171.931658] scsi 1:0:0:0: Direct-Access Lexar USB Flash Drive 1100 PQ: 0 ANSI: 6
[ 171.943602] sd 1:0:0:0: [sda] 60620800 512-byte logical blocks: (31.0 GB/28.9 GiB)
[ 171.953197] sd 1:0:0:0: [sda] Write Protect is off
[ 171.958051] sd 1:0:0:0: [sda] Mode Sense: 43 00 00 00
[ 171.959240] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 171.976420] sda: sda1
[ 171.983504] sd 1:0:0:0: [sda] Attached SCSI removable disk
[ 202.246029] usb 2-1: reset high-speed USB device number 5 using ci_hdrc
[ 202.447734] sd 1:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=30s
[ 202.457408] sd 1:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 03 9c ff fe 00 00 01 00
[ 202.464743] blk_update_request: I/O error, dev sda, sector 60620798 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0

[ 232.966052] usb 2-1: reset high-speed USB device number 5 using ci_hdrc
[ 233.167575] sd 1:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=30s
[ 233.177366] sd 1:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 00 00 28 00 00 10 00
[ 233.184743] blk_update_request: I/O error, dev sda, sector 40 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0
[ 233.943246] udevd[172]: worker [412] /devices/platform/soc/2100000.bus/2184000.usb/ci_hdrc.0/usb2/2-1/2-1:1.0/host1/target1:0:0/1:0:0:0/block/sda is taking a long time

...

I have these issues with linux-imx or linux-fslc-imx.

It seems that I do not have these issues with u-boot-fslc (2022.10).

I have also additional issues:

u-boot-fslc (2022.10): I must revert https://github.com/Freescale/u-boot-fslc/commit/d0399a46e7cda63c07e3eb8558bef84cfb068028 to be able to detect sdcard (same thing for wandboard) used to boot the board
linux-fslc-imx (5.15-2.1.x-imx) : there are issues on device trees: https://github.com/Freescale/linux-fslc/blob/5.15-2.1.x-imx/arch/arm/boot/dts/imx6q.dtsi#L194 + https://github.com/Freescale/linux-fslc/blob/5.15-2.1.x-imx/arch/arm/boot/dts/imx6dl.dtsi#L122 (wrong reg values). Without updated these dtsi, a warning is printed in kernel logs

Sanket_Parekh · ‎12-07-2022

Hi @SebastienFabre

I hope you are doing well.

One of the possible cause of USB reset is power fluctuation of USB. Can you please check the USB VBUS power rails while you see the reset logs?

Thanks & Regards

Sanket Parekh

SebastienFabre · ‎12-08-2022

Hello,

Even when I see reset log, USB VBUS stays equal to 5V.

Moreover, about issue on u-boot-fslc 2022.10 to detect sdcard, we can update:

- arch/arm/dts/imx6qdl-sabresd.dtsi with

aliases {
mmc1 = &usdhc3;
};

- arch/arm/dts/imx6qdl-wandboard.dtsi with

aliases {
mmc0 = &usdhc3;
};

Best regards

Sanket_Parekh · ‎12-09-2022

Hi @SebastienFabre

Can you please share your board DTS files?

Thanks & Regards

Sanket Parekh

SebastienFabre · ‎12-12-2022

Hello,

As said before I am using yocto kirkstone. You can reproduce this issue with yocto kirkstone imx manifest (repo init -u https://source.codeaurora.org/external/imx/imx-manifest -b imx-linux-kirkstone -m imx-5.15.32-2.0.0.xml), MACHINE equals to imx6qdlsabresd, DISTRO equal to fsl-imx-xwayland (I think that we have the same issue with other distros) and with core-image-weston image (I think that we have the same issue with other images).

As said before, the issue seems to not be reproduced with u-boot-fslc (IMX_DEFAULT_BOOTLOADER:imx-nxp-bsp = "u-boot-fslc" in local.conf + PREFERRED_PROVIDER_virtual/bootloader:imx-nxp-bsp = "u-boot-fslc" in fsl-imx-preferred-env.inc)

Best regards

Sanket_Parekh · ‎12-15-2022

Hi @SebastienFabre

I hope you are doing well

Thanks for your patience.

We tried to reproduce the issue on yocto kirkstone imx manifest with BSP version 5.15.32 on the IMX8MQ and IMX8MP board as we have no imx6qdlsabresd board setup. But the USB device works fine on our end. We kindly recommend you please cross-varify your hardware. It seems that the issue is not from the BSP side.

Thanks & Regards

Sanket Parekh

SebastienFabre · ‎12-15-2022

Hello,

On the same board, there is the issue in case of u-boot-imx whereas it is OK in case of u-boot-fslc. I have the same behavior with another imx6qdlsabresd board. So it should not be an hardware issue.

I think there is an issue in u-boot-imx (code or device tree) at least for imx6qdlsabresd board. I have not tested with other imx6 boards.

Best regards

Sébastien

Sanket_Parekh · ‎12-20-2022

Hi @SebastienFabre

We confirmed that there is no issue on iMX8 with the same version of u-boot-imx (2022.04) and we are trying for the same setup of imx6qdlsabresd.

We are working on that. We will get back to you soon.

Thanks & Regards

Sanket Parekh

Sanket_Parekh · ‎12-21-2022

Hi @SebastienFabre

I really appreciate your patience.

We tried the same setup as you have with the imx6qdlsabresd board with the same BSP you mentioned.

But we failed to reproduce the issue on our end and the mouse connected with OTG is being detected, also port is not getting reset.

We observed this scenario for more than half an hour but the result is the same.

Thanks & Regards

Sanket Parekh

SebastienFabre · ‎01-03-2023

Hello,

So, when you use u-boot-imx (2022.04) with kirkstone on imx6qdlsabresd, if you connect your mouse on USB OTG port, it is always detected even if you move it several seconds or minutes (less than 5) ?

If so, I don't understand why I can reproduce the issue on 2 boards with u-boot-imx (2022.04) and not with u-boot-fslc (2022.10)

Best regards

Sanket_Parekh · ‎01-06-2023

Hi @SebastienFabre

So, when you use u-boot-imx (2022.04) with kirkstone on imx6qdlsabresd, if you connect your mouse on USB OTG port, it is always detected even if you move it several seconds or minutes (less than 5) ?

=> Yes

If so, I don't understand why I can reproduce the issue on 2 boards with u-boot-imx (2022.04) and not with u-boot-fslc (2022.10)

=> I have sent this issue to our engineering team. We will get back to you as soon as we get any clue.

Thanks & Regards

Sanket Parekh