Jetson AGX xavier is not detecting any device connected to one of its usb3 port

Autonomous Machines Jetson & Embedded Systems Jetson AGX Xavier
1

I am trying to connect Zed camera to the USB3 port of AGX Xavier, it was detecting it before, but recently it has not detected it so I tried connecting some other device to the same port but it’s even not detecting it. I restarted the machine multiple times the issue wasn’t solved. I want to know what else could be the issue any ideas?
following are the commands that i used for analysis
nvidia@nvidia ~> sudo dmesg |grep ZED-2i
[ 6.889917] usb 1-4.1.2: Product: ZED-2i HID INTERFACE
[ 6.894811] hid-generic 0003:2B03:F881.0004: hiddev97,hidraw3: USB HID v1.11 Device [STEREOLABS ZED-2i HID INTERFACE] on usb-3610000.xhci-4.1.2/input0
[ 7.249806] usb 1-4.2.2: Product: ZED-2i HID INTERFACE
[ 7.254180] hid-generic 0003:2B03:F881.0005: hiddev98,hidraw4: USB HID v1.11 Device [STEREOLABS ZED-2i HID INTERFACE] on usb-3610000.xhci-4.2.2/input0
[ 78.220119] hid-generic 0003:2B03:F881.0006: hiddev98,hidraw4: USB HID v1.11 Device [STEREOLABS ZED-2i HID INTERFACE] on usb-3610000.xhci-4.2.2/input0
[ 78.455895] hid-generic 0003:2B03:F881.0007: hiddev97,hidraw3: USB HID v1.11 Device [STEREOLABS ZED-2i HID INTERFACE] on usb-3610000.xhci-4.1.2/input0
[ 4554.962543] usb 1-4.2.2: Product: ZED-2i HID INTERFACE
[ 4554.967779] hid-generic 0003:2B03:F881.0008: hiddev97,hidraw1: USB HID v1.11 Device [STEREOLABS ZED-2i HID INTERFACE] on usb-3610000.xhci-4.2.2/input0
[ 4560.886259] usb 1-4.2.2: Product: ZED-2i HID INTERFACE
[ 4560.891597] hid-generic 0003:2B03:F881.0009: hiddev97,hidraw1: USB HID v1.11 Device [STEREOLABS ZED-2i HID INTERFACE] on usb-3610000.xhci-4.2.2/input0
[ 4565.125849] usb 1-4.2.2: Product: ZED-2i HID INTERFACE
[ 4565.130905] hid-generic 0003:2B03:F881.000A: hiddev97,hidraw1: USB HID v1.11 Device [STEREOLABS ZED-2i HID INTERFACE] on usb-3610000.xhci-4.2.2/input0
[ 4571.825399] usb 1-4.2.2: Product: ZED-2i HID INTERFACE
[ 4571.829986] hid-generic 0003:2B03:F881.000B: hiddev97,hidraw1: USB HID v1.11 Device [STEREOLABS ZED-2i HID INTERFACE] on usb-3610000.xhci-4.2.2/input0
[ 4578.697138] usb 1-4.2.2: Product: ZED-2i HID INTERFACE
[ 4578.701580] hid-generic 0003:2B03:F881.000C: hiddev97,hidraw1: USB HID v1.11 Device [STEREOLABS ZED-2i HID INTERFACE] on usb-3610000.xhci-4.2.2/input0
[ 4586.300346] usb 1-4.2.2: Product: ZED-2i HID INTERFACE
[ 4586.305319] hid-generic 0003:2B03:F881.000D: hiddev97,hidraw1: USB HID v1.11 Device [STEREOLABS ZED-2i HID INTERFACE] on usb-3610000.xhci-4.2.2/input0
[ 4593.907861] usb 1-4.2.2: Product: ZED-2i HID INTERFACE
[ 4593.912711] hid-generic 0003:2B03:F881.000E: hiddev97,hidraw1: USB HID v1.11 Device [STEREOLABS ZED-2i HID INTERFACE] on usb-3610000.xhci-4.2.2/input0
[ 4602.099152] usb 1-4.2.2: Product: ZED-2i HID INTERFACE
[ 4602.104095] hid-generic 0003:2B03:F881.000F: hiddev97,hidraw1: USB HID v1.11 Device [STEREOLABS ZED-2i HID INTERFACE] on usb-3610000.xhci-4.2.2/input0
[ 4609.274692] usb 1-4.2.2: Product: ZED-2i HID INTERFACE
[ 4609.279177] hid-generic 0003:2B03:F881.0010: hiddev97,hidraw1: USB HID v1.11 Device [STEREOLABS ZED-2i HID INTERFACE] on usb-3610000.xhci-4.2.2/input0

nvidia@nvidia ~>lsusb
Bus 002 Device 002: ID 0451:8440 Texas Instruments, Inc.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 010: ID 0451:82ff Texas Instruments, Inc.
Bus 001 Device 032: ID 2b03:f881 USB2.0 HUB
Bus 001 Device 007: ID 0424:2512 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub
Bus 001 Device 003: ID 0451:8442 Texas Instruments, Inc.
Bus 001 Device 006: ID 03e7:2150 Intel Myriad VPU [Movidius Neural Compute Stick]
Bus 001 Device 016: ID 3032:0013
Bus 001 Device 017: ID 04b4:0008 Cypress Semiconductor Corp.
Bus 001 Device 014: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub
Bus 001 Device 018: ID 04e8:4001 Samsung Electronics Co., Ltd USB2.0 HUB
Bus 001 Device 008: ID 0403:6010 Future Technology Devices International, Ltd FT2232C/D/H Dual UART/FIFO IC
Bus 001 Device 004: ID 0409:005a NEC Corp. HighSpeed Hub
Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

3

Hi,
If you can re-flash the system image, we would suggest re-flash the system and try again. The latest releases for Xavier are Jetpack 4.6.4 and 5.1.2. You may try either one.

1 Like
4

Some questions: Is the camera directly connected to a port, or is it going through an external HUB? If through a HUB, is the HUB itself USB3, and is the HUB provided external power or does it use bus power?

You might also add the output in tree view, “lsusb -t”. Finally, if the camera is not connected, and you run “dmesg --follow” to see logs as they occur, what do you see which is specifically a result of plugging in the camera?

I’ll also suggest that updating first is especially important if you use JetPack 5.x (L4T R35.x). There are a lot of significant updates for JetPack 5.x (L4T R35.x), although there are fewer issues with the more mature JetPack 4.x (L4T R32.x).

1 Like
5

Okay I will try reflashing it

6

Somehow the camera is detected without reflashing but I tried connecting a different USB device it did not recognize that. Is there any option of resetting just USB connection drivers in Xavier’s?

7

USB is hot plug, so normally one would just unplug and replug. I’m sure there are ways to echo to a file in “/sys”, but someone from NVIDIA would need to say which file (it’s driver specific).

There are a number of reasons why one USB device might detect, but not another. If there is absolutely no dmesg log from the plugin, then it might be a signal quality issue. With the camera plugged in, what do you see from “lsusb -t”? Then describe the location of the port the other device plugs in (as well as what the device is). Example: The camera and device share a USB HUB, or a different port is used for the other device, or you unplug the camera and plug in the other device.

Note that if it is a signal quality issue, then there won’t be any fix from just resetting. Sometimes a HUB can act as a signal adapter and the signal between HUB and Jetson will work, and the signal between device and HUB will work, but the device directly plugged in to that port on the Jetson won’t work. Power requirements also can make quite strange results.