USB reset repeats.

Hi, I am developing using yocto bsp 5.0.

If I plug anything into the usb, it repeats this message.

[ 1461.705970] usb 3-1.3: reset full-speed USB device number 3 using ci_hdrc
[ 1462.962161] usb 3-1.3: reset full-speed USB device number 3 using ci_hdrc
[ 1464.293917] usb 3-1.3: reset full-speed USB device number 3 using ci_hdrc
[ 1465.565945] usb 3-1.3: reset full-speed USB device number 3 using ci_hdrc

And after 20 minutes, repeats this message.

[ 4442.893408] usb 3-1: new high-speed USB device number 72 using ci_hdrc
[ 4443.037411] usb 3-1: device no response, device descriptor read/64, error -71
[ 4443.289432] usb 3-1: device no response, device descriptor read/64, error -71
[ 4443.529418] usb 3-1: new high-speed USB device number 73 using ci_hdrc
[ 4443.673421] usb 3-1: device no response, device descriptor read/64, error -71
[ 4443.925436] usb 3-1: device no response, device descriptor read/64, error -71

I tried this post because it was similar to the symptoms, but I am using u-boot toradex_imx_v2020.04_5.4.24_2.1.0.

Is there any patch to apply in u-boot toradex_imx_v2020.04_5.4.24_2.1.0?

Note that BSP 5.0 is obsolete by now. Please update to the later BSP 5.2 or wait another week or two for the upcoming BSP 5.3.

Hi @JHLee

could you eventually resolve this issue?

I’ having similar problems on imx7 4.20.17 with an ELP 1080P Webcam.
2 of 150 devices are affected after some days of operation. Soft reboot doesent help. Hard reset does help.

# looping
[   10.691489] usb usb1-port1: attempt power cycle     # could be ignored - usb 5v is hardwired!
[   11.411405] usb 1-1: new high-speed USB device number 12 using ci_hdrc
[   11.571382] usb 1-1: device descriptor read/64, error -71
[   11.861395] usb 1-1: device descriptor read/64, error -71

Hi @m.tellian !

This is a really old topic.

Could you please open a new topic specifically about your issue? You can refer to this topic on your newly created one if you want.

Please don’t forget to share the following information in your new topic:

  • What is the full name of your module together with its version
  • Which OS you are using (TorizonCore / built using Yocto / one of Toradex’s Reference Images)
  • The output of the following commands executed on the Toradex Module
    • cat /etc/os-release
    • cat /etc/issue
    • uname -a
  • Which carrier board are you using (Toradex’s off-the-shelf or custom) and its version

Best regards,

I solved it by upgrading to bsp 5.4.
I think it has something to do with ELB-3228 issue.

1 Like