Problem with the USB ports and overheating - Jetson Xavier NX Developer Kit

[vzammay]

sudo lshw (5.6 KB)
sudo dmesg (61.0 KB)

I am experiencing a number of problems with the Jetson Xavier NX Dev Kit. I set the hotspot to auto start and connected it to another board with an 18V (5.5A) adjustable charger. After a few minutes working properly I noticed that the wifi connection was gone and the Xavier was very hot, especially in the wireless network card area which burned if you touched it. After unplugging it and returning to its normal location, the board is still very hot when it is turned on (now with its charger). In addition, the USB ports do not work if you connect anything (a mouse, a keyboard, an IMU…) and it is no longer able to raise the hotspot again.

I can access by ssh and the display connected by hdmi works correctly. Here is the result of lsusb, lspci and trying to activate the hotspot manually. Attached are the results of dmesg and lshw. Thanks a lot.

:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

:~$ lspci
returns nothing

:~$ nmcli connection up Hotspot
Error: Connection activation failed: No suitable device found for this connection (device eth0 not available because profile is not compatible with device (mismatching interface name)).

[WayneWWW]

Hi,

Some questions here

1. Is the “wifi” here really related to the issue or not? Is this wifi based on PCIe or USB?

2. I don’t really think it is wise to tell whether this device is overheating by “feel” it. You should use tegrastats to show the device status instead of “feel”. 65C and 90C could all be “hot” for human…

3. There is no error log from your dmesg. Did you dump it with usb devices connected in the beginning or you hot plug it later?

[vzammay]

Hi, WayneWWW, thanks for your reply.

1.- On PCIe. It is related only in the sense that the two things stopped working at the same time.

2.- Quite true, tegrastats shows an acceptable temperature range

3.- I tried both ways and in both cases dmesg does not show any change and does not react to the usbs.

The voltage at the USB ports has been measured and in all cases it is 0. Here is the result of lsusb -v, in case it is useful

:~$ lsusb -v

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Couldn’t open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 3.10
bDeviceClass 9 Hub
bDeviceSubClass 0
bDeviceProtocol 3
bMaxPacketSize0 9
idVendor 0x1d6b Linux Foundation
idProduct 0x0003 3.0 root hub
bcdDevice 5.10
iManufacturer 3
iProduct 2
iSerial 1
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x001f
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 12
bMaxBurst 0

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Couldn’t open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0
bDeviceProtocol 1 Single TT
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0002 2.0 root hub
bcdDevice 5.10
iManufacturer 3
iProduct 2
iSerial 1
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0019
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 12

[kayccc]

Overheating only exists on wifi board per your description?
If tegrastats shows an acceptable temperature range, then it looks more like wifi board issue.