Hello, I powered up my Jetson Orin Nano (super dev kit, Jetpack 6.2.1) after a weekend of being unplugged and now all the USB-A ports are not working. However, the USB-C port does still work. All the ports are supplying 5V power but devices like mice, keyboards or USB drives are not recognized. I have attached the dmesg log:
*** Please note that this reply is generated by LLM automatically ***
Based on the provided information, it appears that the issue is related to the USB ports on the Jetson Orin Nano Super Dev Kit. The dmesg log indicates that the USB ports are not functioning correctly, despite supplying 5V power.
The relevant section of the dmesg log is:
sb0: HOST MAC 22733a3cc38c 16905474
usb0: MAC 22733a3cc38d 16905854
usb1: HOST MAC 22733a3cc38e 16905859
usb1: MAC 22733a3cc38f 16912090
tegraxudc 3550000.usb: EP 0 type ctrl dir out enabled 16920550
l4tbr0: port 1(usb0) entered blocking state 16920570
l4tbr0: port 1(usb0) entered disabled state 16921061
device usb0 entered promiscuous mode 16930410
l4tbr0: port 2(usb1) entered blocking state 16930428
l4tbr0: port 2(usb1) entered disabled state 16930577
device usb1 entered promiscuous mode
This log indicates that the USB ports are entering a disabled state, which is likely causing the issue.
Before reflashing the SD card, you can try the following steps to troubleshoot the issue:
Power cycle the board: Try powering off the board, waiting for a few seconds, and then powering it back on. This can sometimes resolve issues related to USB ports.
Check the USB configuration: Verify that the USB configuration is set correctly in the device tree. You can do this by checking the tegra194-p3668-0000-p3509-0000.dtb file (or the corresponding file for your board) for the USB configuration.
Update the kernel: Ensure that the kernel is up-to-date, as newer kernel versions may have resolved issues related to USB ports.
Check for conflicts with other devices: If you have other devices connected to the USB ports, try disconnecting them and see if the issue persists.
Try a different USB port: If you have multiple USB ports available, try using a different port to see if the issue is specific to one port.
If none of these steps resolve the issue, it may be necessary to reflash the SD card. However, before doing so, you may want to try to gather more information about the issue by:
Checking the kernel logs for any error messages related to USB
Running lsusb to see if the USB devices are being detected
Running usb-devices to see if the USB devices are being enumerated correctly
By gathering more information about the issue, you may be able to identify the root cause and resolve it without needing to reflash the SD card.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
Before reflashing the SD card, you can try the following steps to troubleshoot the issue:
Power cycle the board: Try powering off the board, waiting for a few seconds, and then powering it back on. This can sometimes resolve issues related to USB ports.
Check the USB configuration: Verify that the USB configuration is set correctly in the device tree. You can do this by checking the tegra194-p3668-0000-p3509-0000.dtb file (or the corresponding file for your board) for the USB configuration.
Update the kernel: Ensure that the kernel is up-to-date, as newer kernel versions may have resolved issues related to USB ports.
Check for conflicts with other devices: If you have other devices connected to the USB ports, try disconnecting them and see if the issue persists.
Try a different USB port: If you have multiple USB ports available, try using a different port to see if the issue is specific to one port.
I attempted to power cycle the board, but it did not resolve the issue.
That file is not present in my /boot folder. All the files begin with tegra234. Also, what does a “correct” configuration look like?
I ran sudo apt update && sudo apt upgrade and rebooted the device. Is there anything else here I should try?
The issue persists even when only one device is plugged in.
The problem is ubiquitous for all 4 usb-A ports.
Devices on USB-A ports are not detected when running lsusb nor usb-devices
eric@eric-desktop:~$ lsusb
Bus 002 Device 003: ID 05e3:0626 Genesys Logic, Inc. USB3.1 Hub
Bus 002 Device 002: ID 0bda:0489 Realtek Semiconductor Corp. 4-Port USB 3.0 Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 13d3:3549 IMC Networks Bluetooth Radio
Bus 001 Device 006: ID 16c0:0483 Van Ooijen Technische Informatica Teensyduino Serial
Bus 001 Device 005: ID 343c:0000 xxxxxxxx USB Type-C Digital AV Adapter
Bus 001 Device 004: ID 3554:fc03 2.4G Receiver
Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
note: I have a usb hub attached to the usb-C port and the lsusb did not change after plugging a mouse into the usb-A port
When I plug is some devices, they do show they are powered. For example, an Arduino can be powered from the USB-A port.
If it is the hardware, would it be sufficient to replace just the carrier board? Also, what could have caused the USB port to be damaged? The board was working fine when I left the lab on Saturday. I came back in today and its broken?
Bus 002 Device 003: ID 05e3:0626 Genesys Logic, Inc. USB3.1 Hub
Bus 002 Device 002: ID 0bda:0489 Realtek Semiconductor Corp. 4-Port USB 3.0 Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 13d3:3549 IMC Networks Bluetooth Radio
Bus 001 Device 006: ID 16c0:0483 Van Ooijen Technische Informatica Teensyduino Serial
Bus 001 Device 005: ID 343c:0000 xxxxxxxx USB Type-C Digital AV Adapter
Bus 001 Device 004: ID 3554:fc03 2.4G Receiver
Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Just want to clarify. I don’t really care about any other USB devices running on your board. You could remove them at this moment because they are causing noise in the log file.
Only want to know that. Are you able to see anything detected on the 4 USB type A ports on your devkit in lsusb or not?
Or if anything on that type A ports would trigger any new log in your dmesg?
Also want to point out that. That 4 type A USB ports are actually behind a USB hub too. So please clarify what “hub” you are talking about when you use the word “hub”.
Apologies, the jetson is buried in a robot we are actively working with, so plugging and unplugging the USB ports is a bit cumbersome.
Are you able to see anything detected on the 4 USB type A ports on your devkit in lsusb or not?
Or if anything on that type A ports would trigger any new log in your dmesg?
No, lsusb does not detect anything in the USB-A ports. plugging things into the USB-A port does not generate any new log in the dmesg