Can't boot NX into forced recovery mode

Autonomous Machines Jetson & Embedded Systems Jetson Xavier NX
#1

I installed JP 4.4.1 onto an SD card and can successfully boot to that. When I attempt to jumper pins 9 & 10 into forced recovery mode I am not getting the NX to show up in the output of lsusb from the attached host. I’ve tried two different Linux hosts with the same results. Am I missing something?

chad@us-h6ql182:~$ lsusb
Bus 002 Device 002: ID 8087:8000 Intel Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp. 
Bus 001 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 004: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

jetson-nx-jumpered
jetson-nx-jumpered1280×960 251 KB

#2

That should work. If the micro-B USB cable is a “charger” cable, and not the provided cable, then I would expect failures during flash, but I would still expect the recovery mode to show up correctly at the start.

If the host is a VM, then I would expect a failure due to VM configuration not passing through the USB port.

Just for reference, one would power down the Jetson, jumper the recovery pin, apply power, and remove the jumper. If you’ve done this, and if this is not a VM, then you may have some actual failure.

#3

Your comment regarding the “charger” cable made me take a look around and make sure I was using the proper cable. I believe I am, but I located a second cable which is a charger cable and once I hooked that up it now shows up as expected. So, I guess I had a bad cable. Thanks for the quick response!

#4

Not surprising…charger cables are notorious for being terrible quality. The data wires of a charger cable are about as low quality as you can get and still call them “wires”.