"USB cable is bad" from a certain NX

Hi, we have several NXs and devices and we use the same USB-Ethernet adapter with them.
But we got a certain NX(Model: P3668) which always have the following dmseg output

[  239.579218] usb usb2: usb_suspend_both: status 0 

[  240.577992] usb usb1-port2: Cannot enable. Maybe the USB cable is bad? 

[  241.469935] usb usb1-port2: Cannot enable. Maybe the USB cable is bad? 

[  241.470383] usb usb1-port2: attempt power cycle 

[  243.101651] usb usb1-port2: Cannot enable. Maybe the USB cable is bad? 

[  243.997632] usb usb1-port2: Cannot enable. Maybe the USB cable is bad? 

[  243.997860] usb usb1-port2: unable to enumerate USB device 

[  243.998081] usb usb1: usb_suspend_both: status 0

At the same time, we can get normal output from the others good NXs like this

[   15.213404] usb 1-2: new high-speed USB device number 2 using tegra-xusb 

[   15.236783] usb 1-2: New USB device found, idVendor=05e3, idProduct=0610 

[   15.236805] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 

[   15.236815] usb 1-2: Product: USB2.1 Hub 

[   15.236821] usb 1-2: Manufacturer: GenesysLogic 

[   15.239716] hub 1-2:1.0: USB hub found 

[   15.240016] hub 1-2:1.0: 4 ports detected 

[   15.553398] usb 1-2.2: new high-speed USB device number 3 using tegra-xusb 

[   15.580904] usb 1-2.2: New USB device found, idVendor=0b95, idProduct=1790 

[   15.580970] usb 1-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 

[   15.580982] usb 1-2.2: Product: AX88179 

[   15.580989] usb 1-2.2: Manufacturer: ASIX Elec. Corp. 

[   15.580994] usb 1-2.2: SerialNumber: 0000000001367D 

[   15.976651] ax88179_178a 1-2.2:1.0 eth1: register 'ax88179_178a' at usb-3610000.xhci-2.2, ASIX AX88179 USB 3.0 Gigabit Ethernet, 90:96:f3:4a:44:a9

In addition, we also tested with carrier board, but on carrier board all the NXs work fine with the same USB-Ethernet adapter(Both USB2.0 and 3.0).

To summarise,
issue NX + our device => NG
issue NX + carrier board (dev kit) => OK
other NXs(N=5) + our device => OK
other NXs(N=5) + carrier board (dev kit) => OK

Could this be a HW issue to this certain NX?
(We flashed the same customized image to all NXs)

It looks like a board matching issue…how many your devices have been tested with issue NX? Did yo u follow Design Guide routing guideline well to make your PCB? Or did you check your PCB layout routing to make sure it follows DG well?

Thank you for replying.
We tested with 3 our devices, only the certain NX is NG with all devices and others work fine with all devices

Hi,
Please refer to the document and do compliance test:
https://developer.nvidia.com/jetson-xavier-nx-tuning-and-compliance-guide-application-note

The default setting is for Xavier NX developer kit. For custom board, doing compliance test is required.

sorry we don’t have the environment to do this kind of test now. and this can not explain why other NXs with the same image work fine…

Hi,
The prints show that signal quality is not stable. The default setting is for developer kit. For custom board, it is required to do compliance test. The default setting may not fit custom boards.

The same setting on others NXs(N=5) work fine with our devices. Only one particular NX got the bad msg

Hi,
If the module+ developer kit works fine, it doesn’t look to be something wrong in the module.

We would suggest adjust setting for the custom board. The default setting can pass compliance test on Xavier NX developer kit. May not fit custom boards.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.