USB problem by working with AGX Xavier evaluation board

Autonomous Machines Jetson & Embedded Systems Jetson AGX Xavier
#1

Dear support,
We have USB problem by working with AGX Xavier evaluation board.
Everything is running fine but at some point the USB completely stops working. all USBs don’t answer. Pls see attached dmseg log line [ 657.320325]
[ 657.320325] tegra-xusb 3610000.xhci: xHCI host not responding to stop endpoint command.

dmesgLog_17-11-2020.txt (81.9 KB)
We face this issue suddenly after successfully working - our application perform captures by using ximea camera (connection via USB-C) with external PS, another one USB-A is connected to FPGA with external PS also, and T7 touch SSD device connected to USB-C (we save on SSD device our captures). SSD device doesn’t have external PS.
After Jetson reboot all continue work without problem…

Could you pls help us to resolve this problem?
we work with the following version:
NVIDIA Jetson AGX Xavier [16GB]
L4T 32.3.1 [ JetPack 4.3 ]
Ubuntu 18.04.5 LTS
Kernel Version: 4.9.140-rt93-tegra
CUDA 10.2.89
CUDA Architecture: 7.2
OpenCV version: 4.1.1
OpenCV Cuda: NO
CUDNN: 8.0.0.180
TensorRT: 7.1.3.0
Vision Works: 1.6.0.501
VPI: 0.3.7

#3

Hi,
We have two type-C posts J512 and J513 on the evaluation board. At which port do you hit the issue? And are you able to try JP4.4.1(r32.4.4)?

#4

How about check USB bandwidth;

#5

The following ports do not work:
USB_A ( J507) - connect to FPGA, USB-C (J513) - connect to Camera, USB C ( J512) - connect to SSD. We didn’t try JP4.4.1(r32.4.4). Does it include changes in USB drivers?

#6

Dear support. I get the same USB problem by working with another AGX Jetson board.dmesg_25_11_2020_error.txt (78.3 KB)
I added the patch from Stream 4 Cameras with GStreamer (xhci->quirks |= XHCI_TRUST_TX_LENGTH;). but it didn’t help.
could you pls help us to resolve this problem It is very critical for us.

Thanks, Sabina

#7

Hi,
Please refer to power mode table:
https://docs.nvidia.com/jetson/l4t/index.html#page/Tegra%20Linux%20Driver%20Package%20Development%20Guide%2Fpower_management_jetson_xavier.html%23wwpID0E0NO0HA
You can run in MAXN mode and execute sudo jetson_clocks. Check if running in max performance mode helps.

If the issue still exists, please try to eliminate certain devices and see if which device triggers the issue. Looks like you have three devices. One in J507, one in J513 and the other in J512.

1 Like