Jetson Nano Development Kit not recognized via USB when in recovery mode

Autonomous Machines Jetson & Embedded Systems Jetson Nano
1

I have the problem that the Jetson Nano B01 Development kit is not recognized over usb.
I’m running Ubuntu 18.04 on my host. I connect the Jetson with the MicroUsb to USB cable. I connect the USB port on my host.I run Jetson into recovery mode

lsusb is not listing the device. If I run dmesg --follow and replug the usb cable, I get

[ 8895.018055] usb 1-1.5: new full-speed USB device number 69 using ehci-pci
[ 8895.098053] usb 1-1.5: device descriptor read/64, error -32
[ 8895.286049] usb 1-1.5: device descriptor read/64, error -32
[ 8895.474016] usb 1-1.5: new full-speed USB device number 70 using ehci-pci
[ 8895.554055] usb 1-1.5: device descriptor read/64, error -32
[ 8895.742037] usb 1-1.5: device descriptor read/64, error -32
[ 8895.850159] usb 1-1-port5: attempt power cycle
[ 8896.454025] usb 1-1.5: new full-speed USB device number 71 using ehci-pci
[ 8896.870039] usb 1-1.5: device not accepting address 71, error -32
[ 8896.950016] usb 1-1.5: new full-speed USB device number 72 using ehci-pci
[ 8897.366006] usb 1-1.5: device not accepting address 72, error -32
[ 8897.366136] usb 1-1-port5: unable to enumerate USB device
[ 9008.171817] usb 1-1.5: new full-speed USB device number 73 using ehci-pci
[ 9008.251835] usb 1-1.5: device descriptor read/64, error -32
[ 9008.439811] usb 1-1.5: device descriptor read/64, error -32
[ 9008.627807] usb 1-1.5: new full-speed USB device number 74 using ehci-pci
[ 9008.707816] usb 1-1.5: device descriptor read/64, error -32
[ 9008.895804] usb 1-1.5: device descriptor read/64, error -32
[ 9009.004024] usb 1-1-port5: attempt power cycle
[ 9009.607788] usb 1-1.5: new full-speed USB device number 75 using ehci-pci
[ 9010.023750] usb 1-1.5: device not accepting address 75, error -32
[ 9010.103750] usb 1-1.5: new full-speed USB device number 76 using ehci-pci
[ 9010.519768] usb 1-1.5: device not accepting address 76, error -32

ubuntu@ubuntu:~$ lsusb

Bus 002 Device 004: ID 8564:1000 Transcend Information, Inc. JetFlash
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 089: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Any hints to what I could do?

2

This looks like an actual USB error, perhaps due to signal quality. Are you using a HUB? If so, try without the HUB; if not, try with a HUB. Regardless, make sure the Jetson is the only thing on that port.

As a test you could see if lsusb shows as working from another computer. Signal quality issues depend on both ends, plus the cable and everything in between, and even if the port is otherwise working, then some combinations may not work due to minor differences.

Another cause of something like this is not using the supplied micro-B USB cable. Charger cables have notoriously low quality when it comes to signals.

3

My kit was without a micro usb cable, I tried different cables, connect via a hub and without, no result. Can i sing (encrypt) dtb, without jetson connecting to host machine?

4

You can do this, and then use dd to put a partition in place if the Jetson is running. I’ve not personally done this, and the notes I have are for signing with a private key known by the user since that key would have been used to burn the fuses. I am not sure how this works if you use the “--no-flash” option without naming a key, but it goes something like this for a known key (this is a bit contrived, and perhaps not a real command for your particular hardware):
sudo ./flash.sh --no-flash -u <rsa_priv>.pem -v <sbk>.key jetson-nano-qspi-sd mmcblk0p1

Someone else may have more advice on device tree signing.