Micro-USB on Tx2 not connecting to devices

Autonomous Machines Jetson & Embedded Systems Jetson TX2
#1

Hello,

I am having a problem with using the micro-usb port on the Tx2.
First whenever I try to connect a peripheral device to the micro-usb port by using a micro-usb to female Usb adapter, then connecting to the device, the device does not connect. When checking dmesg on the tx2 the output is:

[ 130.584829] extcon-gpio-states external-connection:extcon@1: Cable state:1, cable id:2
[ 130.604852] extcon-gpio-states external-connection:extcon@1: Cable state:1, cable id:2
(When the adapter is connected)
[ 140.337386] usb 1-1: new full-speed USB device number 10 using tegra-xusb
[ 140.338099] usb 1-1: Device not responding to setup address.
[ 140.550082] usb 1-1: Device not responding to setup address.
[ 140.761402] usb 1-1: device not accepting address 10, error -71
[ 140.885436] usb 1-1: new full-speed USB device number 11 using tegra-xusb
[ 140.886126] usb 1-1: Device not responding to setup address.
[ 141.097947] usb 1-1: Device not responding to setup address.
[ 141.309508] usb 1-1: device not accepting address 11, error -71
[ 141.315802] usb usb1-port1: attempt power cycle
(When a peripheral device is connected)

I dealt with this temporarily by connecting a usb hub to the usb port. Now I need to enter the Jetson Tx2 into recovery mode, needing to be connected to a host machine using the micro-usb cable included with the Tx2.

I first tried using a virtual machine with ubuntu 16.04 installed. When the Tx2 was connected and in recovery mode it was not available as a USB device for the vm. When checking device manager on windows, the connection using the cable is detected but the Tx2 connected is shown as:
“Unknown USB Device (Device Descriptor Request Failed)”

Finally I attempted to connect the tx2 (in recovery mode) in the same way to a full Ubuntu machine running Ubuntu 20.04. lsusb does not show any connection with the Tx2. Using dmesg the output given when connecting the Tx2 is:

[ 417.564793] usb 1-1: new full-speed USB device number 28 using xhci_hcd
[ 417.692769] usb 1-1: device descriptor read/64, error -71
[ 417.929242] usb 1-1: device descriptor read/64, error -71
[ 418.165064] usb 1-1: new full-speed USB device number 29 using xhci_hcd
[ 418.293161] usb 1-1: device descriptor read/64, error -71
[ 418.529104] usb 1-1: device descriptor read/64, error -71
[ 418.637213] usb usb1-port1: attempt power cycle
[ 419.289055] usb 1-1: new full-speed USB device number 30 using xhci_hcd
[ 419.289278] usb 1-1: Device not responding to setup address.
[ 419.497217] usb 1-1: Device not responding to setup address.
[ 419.705089] usb 1-1: device not accepting address 30, error -71
[ 419.833059] usb 1-1: new full-speed USB device number 31 using xhci_hcd
[ 419.833274] usb 1-1: Device not responding to setup address.
[ 420.041366] usb 1-1: Device not responding to setup address.
[ 420.249190] usb 1-1: device not accepting address 31, error -71
[ 420.249338] usb usb1-port1: unable to enumerate USB device

Could this be a hardware issue on the Tx2 itself? I would appreciate any help that you can offer.

Thank you.

#3

Hi,
The micro USB port on TX2 can run in either host or device mode. Looks like you want to run in host mode. Please try to connect the device to the adapter first, and then connect to the micro port. See if this triggers enumeration. And also try other device such as USB pendrive. See if it is specific to some device.

#4

Hello. Thank you for your reply.

By trying to connect the device first to the adapter, then to the micro port, peripheral devices do not work such as keyboard and mouse, but attempting to do the same with USB Pendrive devices works fine.

It still remains that when I put the Tx2 into recovery mode and connect it to a host Ubuntu 20.04 machine directly through a micro to usb cable without an adapter, it is not recognized. lsusb shows no new device connected while dmesg shows the same error as described before ending with “unable to enumerate USB device”. This happens irrelevant to which device the cable is connected to first.

This is my primary concern as it prevents me from flashing my Tx2.

Thank you.

#5

Hi,
We suggest use 18.04. Please check

System Requirements

  • Host computer running Ubuntu Linux version 16.04 or 18.04 is recommended.
#6

I have tried to do the same using a host pc with Ubuntu 16.04 installed but still the device is unable to be enumerated, giving the same error as usual.

#7

Hi,
Please press Force-Recovery + Rest buttons and check if TX2 can enter recovery mode. The hardware method shall always force TX2 into recovery mode. If this does not work, the hardware may be broken.

#8

I have found that some adapters (with micro at one end, and full sized at the other end…intended for changing a device from full sized to micro) simply do not have good signal quality. I have two such failing adapters here, and one which works (the two adapters which fail are the same model).

As @DaneLLL mentioned, if the Jetson cannot go in recovery mode, then it is a failed device (host should see a recovery mode TX2 with “lsusb -d 0955:7c18”). However, if you use an adapter I would also recommend trying another adapter. I would recommend trying these two variations:

  • Try using an intervening HUB to see if it has better electrical behavior.
  • Try a different adapter cable in case it is just the cable quality.
#10