After using the Orin AGX [CLB] to flash into JetPack 6.x, all USB ports cannot be used normally

[921537903]

The device is an Orin AGX CLB 64GB (loborobot). It works normally under JETPACK 5.1.5, but after I flashed the 6.x version using SDK Manager, although the device boots and runs properly, all USB ports are non-functional. Plugging in and unplugging the mouse, keyboard, and external hard drive does not produce any output in lsusb.

The output during boot compilation is as follows:

[ 5.756860] ucsi_ccg 1-0008: i2c_transfer failed -121

[ 5.756863] ucsi_ccg 1-0008: ucsi_ccg_init failed - -121

[ 5.756867] ucsi_ccg: probe of 1-0008 failed with error -121

sudo dmesg | grep -i usb produces the following:

jetson@ubuntu:~$ sudo dmesg | grep -i usb

[sudo] password for jetson:

[ 0.121105] usbcore: registered new interface driver usbfs

[ 0.121133] usbcore: registered new interface driver hub

[ 0.121158] usbcore: registered new device driver usb

[ 0.254562] ehci_hcd: USB 2.0 ‘Enhanced’ Host Controller (EHCI) Driver

[ 0.254810] ohci_hcd: USB 1.1 ‘Open’ Host Controller (OHCI) Driver

[ 0.255378] usbcore: registered new interface driver usb-storage

[ 3.646584] usbcore: registered new interface driver usbhid

[ 3.646589] usbhid: USB HID core driver

[ 3.715427] usbcore: registered new interface driver snd-usb-audio

And

jetson@ubuntu:~$ lspci | grep -i usb

jetson@ubuntu:~$ ls /sys/class/usb_host

ls: cannot access ‘/sys/class/usb_host’: No such file or directory

jetson@ubuntu:~$ ls /lib/modules/$(uname -r)/kernel/drivers/usb/host | grep xusb jetson@ubuntu:~$ ls /lib/modules/$(uname -r)/kernel/drivers/usb/host | grep xusb

Are there any other details I should provide to help solve this issue? AGX is still running on 5.1.5, where everything works fine, but I would still like to upgrade to Jetpack 6 for more support. :)

[WayneWWW]

Just to clarify.

This kind of questions have been asked and answered multiple times.

If you are using a custom board, then sdkmanager does not guarantee to fully support it.

If it works in some old release, then you have some good luck.
But it does not mean it will always work in later release…

You should check with board vendor for custom BSP to flash the board.

[921537903]

So, is this issue caused by incompatibility between the system and hardware due to third-party hardware design? Since the device was purchased through a central procurement process in the lab, I attempted to contact the hardware vendor, but they refused to provide after-sales support, citing the lack of an order number. Therefore, I am trying my luck here to see if there are any developers who have encountered the same issue.

Since my main research focuses on Model Inference, and I have limited knowledge about such low-level issues, I would greatly appreciate it if you could provide some relevant topic links or resources in case I need to reference similar questions. Thank you so much in advance!

[WayneWWW]

Hi,

In this case, I don’t think you are possible to do that with these reasons:

1. You don’t know the hardware design of you 3rdparty carrier board (and we won’t know either). Without this info, it is not possible to write a correct device tree file for this board.

2. We have documentation but, to understand it, you need to have knowledge like USB hardware design and device tree. This document is for vendor to read, not for end users.