Issues connecting USB 3.0 devices

Hi Toradex-Team,

we are using a Verdin Plus (V1.0B) module together with our own carrier board where we have a USB-C connector for providing a USB3.0 interface. Connecting USB2.0 devices to the USB-C works without any issues. But when we connect USB3.0 devices they are either not connected successfully or they are only connected via the USB2.0 hub and following error is provided:

Cannot enable. Maybe the USB cable is bad?

The full error we get on connecting a USB3.0 data stick is:

[  212.992677] usb usb1-port1: Cannot enable. Maybe the USB cable is bad?
[  213.964653] usb usb1-port1: Cannot enable. Maybe the USB cable is bad?
[  213.971286] usb usb1-port1: attempt power cycle
[  215.016657] usb usb1-port1: Cannot enable. Maybe the USB cable is bad?
[  215.988646] usb usb1-port1: Cannot enable. Maybe the USB cable is bad?
[  215.995264] usb usb1-port1: unable to enumerate USB device

Then the device cannot be seen at all with lsusb:

root@device-builder sys$ lsusb -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M

On connecting another USB3.0 card reader device we get

[  901.796937] usb usb1-port1: Cannot enable. Maybe the USB cable is bad?
[  902.620649] usb 1-1: new high-speed USB device number 20 using xhci-hcd
[  902.822146] usb-storage 1-1:1.0: USB Mass Storage device detected
[  902.834432] scsi host0: usb-storage 1-1:1.0
[  903.875758] scsi 0:0:0:0: Direct-Access              Multi-Reader  -0 1.00 PQ: 0 ANSI: 4
[  903.906153] scsi 0:0:0:1: Direct-Access              Multi-Reader  -1 1.00 PQ: 0 ANSI: 4
[  903.935383] scsi 0:0:0:2: Direct-Access              Multi-Reader  -2 1.00 PQ: 0 ANSI: 4
[  903.956138] sd 0:0:0:0: [sda] Attached SCSI removable disk
[  903.966208] scsi 0:0:0:3: Direct-Access              Multi-Reader  -3 1.00 PQ: 0 ANSI: 4
[  903.986531] sd 0:0:0:1: [sdb] Attached SCSI removable disk
[  904.028392] sd 0:0:0:2: [sdc] Attached SCSI removable disk
[  904.061317] sd 0:0:0:3: [sdd] Attached SCSI removable disk

and lsusb shows a device, but on the 2.0 hub:

root@device-builder sys$ lsusb -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
    |__ Port 1: Dev 20, If 0, Class=Mass Storage, Driver=usb-storage, 480M

The device tree has not been modified in regard to the USB interfaces.
These are kernel outputs during bootup:


root@device-builder sys$ dmesg | grep usb
[    0.316208] usbcore: registered new interface driver usbfs
[    0.321620] usbcore: registered new interface driver hub
[    0.326802] usbcore: registered new device driver usb
[    0.818972] usbcore: registered new interface driver usb-storage
[    0.825047] usbcore: registered new interface driver usbserial_generic
[    0.831598] usbserial: USB Serial support registered for generic
[    0.837629] usbcore: registered new interface driver cp210x
[    0.843221] usbserial: USB Serial support registered for cp210x
[    0.849167] usbcore: registered new interface driver ftdi_sio
[    0.854932] usbserial: USB Serial support registered for FTDI USB Serial Device
[    0.862269] usbcore: registered new interface driver pl2303
[    0.867859] usbserial: USB Serial support registered for pl2303
[    0.873817] usbcore: registered new interface driver usb_serial_simple
[    0.880368] usbserial: USB Serial support registered for carelink
[    0.886477] usbserial: USB Serial support registered for zio
[    0.892159] usbserial: USB Serial support registered for funsoft
[    0.898185] usbserial: USB Serial support registered for flashloader
[    0.904575] usbserial: USB Serial support registered for google
[    0.910518] usbserial: USB Serial support registered for libtransistor
[    0.917067] usbserial: USB Serial support registered for vivopay
[    0.923097] usbserial: USB Serial support registered for moto_modem
[    0.929386] usbserial: USB Serial support registered for motorola_tetra
[    0.936024] usbserial: USB Serial support registered for novatel_gps
[    0.942396] usbserial: USB Serial support registered for hp4x
[    0.948164] usbserial: USB Serial support registered for suunto
[    0.954105] usbserial: USB Serial support registered for siemens_mpi
[    1.102588] usbcore: registered new interface driver usbhid
[    1.108168] usbhid: USB HID core driver
[    1.360763] imx8mq-usb-phy 381f0040.usb-phy: 381f0040.usb-phy supply vbus not found, using dummy regulator
[    1.370657] imx8mq-usb-phy 382f0040.usb-phy: 382f0040.usb-phy supply vbus not found, using dummy regulator
[    1.486268] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.

We based our Yocto build on the Toradex release for BSP 5.6.0-devel-202202.
I can provide schematics of the carrier board via email if required?

Any ideas?
Thx,
BR Ralph

1 Like

Please provide a schematic snippets related to USB.

Hi @alex.tx !
I just sent a mail with the carrier board schematics to ‘support.eu@toradex.com’.
Looking forward to hear from you.
BR Ralph

Schematic looks OK. Please check if your board layout complaints with our layout design guide.

image

Hi @alex.tx,
we checked the layout again for the guidelines and did not find any violations there. If you like, we could also send you the layout for a review.
So when the schematics and the layout are ok, what can we check next?
We also tried with a prebuild Toradex Multimedia Linux image (installed with EasyInstaller) instead of our Yocto image, but we face the same problem when connecting a USB3.0 device.
Do you have any ideas?
Thanks!
Regards Ralph

Hi @alex.tx,
can I sent you a gerber file of the layer where USB3.0 is routed for a review?
BR Ralph

Hello Ralph,

I recived your schematic and I will look at this first.
Can you also send the PCB layout? you can send them as PDF.

Best Regards,

Matthias Gohlke

Hi @matthias.tx ,

I just sent the PCB layout to support@toradex.com (same ticket number).

BR Ralph