Hello Team,
We use a custom carrier board based on Jetson AGX Orin and have encountered an issue with USB 3.2 drives.
The board provides 4x USB 2.0 ports, which are also expected to support USB 3.0 and 3.2 devices. However, when connecting only a USB 3.2 device (e.g., a USB 3.2 pen drive), it often fails to enumerate or get recognized. The following kernel message is seen:
[ 67.372631] usb 1-3: reset high-speed USB device number 2 using tegra-xusb
Interestingly, if a USB 2.0 or USB 3.0 device is already connected to any of the ports, then the USB 3.2 device is recognized correctly.
Additional Info:
We are using the USB2514BT-I/M2 USB hub IC in our custom board design. This exact same design works well on Jetson TX2i with JetPack 4.4 without any issues detecting USB 3.2 drives.
Could you please help us understand why this behavior is occurring? Is there a known driver limitation on the Jetson AGX Orin USB controller regarding USB 3.2 device detection? Are there any workarounds or recommended configurations to make USB 3.2 devices work reliably without needing to plug in a USB 2.0/3.0 device?
Regards,
Parashuram
What’s the JetPack SW you’re using now?
Hi Kayccc,
Currently using Jetpack 5.1.4
Hi,
It looks to be an issue in signal quality. Please do compliance test to the custom board. You can find tuning guide at download center.
Hi,
Thank you for the suggestion regarding signal quality and compliance testing.
However, I have a question regarding the observed behavior:
When I connect a USB 2.0 or USB 3.0 device to the port, it works fine. But if I connect only a USB 3.2 device, it is not detected unless a USB 2.0 or USB 3.0 device is also connected. If this is due to a signal integrity issue, could you please explain why it starts working after connecting USB 2.0/3.0 devices?
Is there a known dependency or initialization sequence that enables proper detection when USB 2.0/3.0 devices are present, but not when only USB 3.2 devices are connected?
Looking forward to your guidance.
Regards,
Parashuram
Hi,
There is no such limitation. Single USB device should be well enumerated. From the description, it may be the signal is not good when only the USB3.2 device is connected.
Hello DeneLLL,
We’ll recheck the signal integrity and routing on our board as suggested and let you know.