Not able to get into recovery mode

Hi,

I got the product and first try to setup the device. It goes well in the first run, However, at the second time, it goes to blue screen. Then I found people suggest to flash to R27.1 release. However, I’m not able to put the device into recovery mode.

I followed the instruction, first turned power off, then connect the USB to host PC, then turn the power on, and press and hold the REC, while press RES, then release RES, after two seconds, release REC.

I tried several times and it doesn’t work. There is also no power supply from USB, the screen connected to the device (HDMI port) shows nothing. When I type lsusb in the host PC, there is no NVIDIA device shown.

I was wondering how I can solve this …

Thanks,

The recovery mode makes the device available from a Host OS.

To check if the device got to the recovery mode successfully - run lsusb from Host Ubuntu 64 OS to which the device is connected via the special usb cable while being in the recovery mode.
You should see something like Nvidia device listed.

There is no Nvidia device listed when I run this commend in the host OS.

You must have the recovery button held down while power is brought up or cycled. Pressing recovery button on a system which is already powered has no effect. Recovery pressed, tap/click power on (or power reset if already on), let go of recovery.

I tried to power it off, and then press and hold the REC first, then press power, then release the REC. After that, I type lsusb in the host OS, there is still no nvidia device shown …

Are you using the provided micro-B USB cable? The full-sized connector can’t be used for recovery mode. If using the micro-B, can you try a different port on the host PC? Also, is there anything special about the host, e.g., being a VM?

the modus operandi is to press power on button, than press Force recovery mode button and held it than press reset and after that in few seconds release Force recovery mode button

Hi fh985,

Have you managed to resolve the problem?
Any result can be shared?

Thanks

It turns out to be a USB line problem. When I changed another USB line, it seems that the device is recognized from host.

Dears,

I have the same problem on my TX2.

When I power On the Dev Kit, I press buttons as asked but see nvidia Corp prompted when y do the command lsusb.

I changed cables, tried every USB port on my computer. I run on Ubuntu 16.04 straight (No VM, Dual boot etc…). Other USB peripherals are correctly discovered.

Does any LED should blink or whatsoever to indicate that we entered in USB FORCE RECOVERY MODE ?

Is the recovery button held down before and during power up or power reset? Pressing and releasing the recovery button followed by power or power reset buttons in sequence won’t work. If recovery is held down while power or reset buttons are tapped, and if the Jetson still does not show up on lsusb, then this is indeed a likely hardware failure. Just to verify, a Jetson TX2 in recovery mode would be visible via:

lsusb -d 0955:7c18

Hi,
Is there a way to put the TX2 into force recovery mode though the debug port. On the TX1 ‘enterrcm’ command performed this operation, however it seems to be missing on the TX2?

Even with a working JTAG debugger I do not believe you could get into recovery mode. I’d really like to know if there is a way which I don’t know about, but I suspect it isn’t worth the trouble. Are you using a carrier board with JTAG but no USB?

We are using our custom board. With the TX1, we were able to put it into bootloader mode for the flash.sh script by issuing the command ‘enterrcm’ on the serial debug port when the TX1 booted. This was very convenient for in in application programming of the TX1s. However the enterrcm command is missing on the TX2 tegra console.

TX2 has a different boot flow. I think this is a big reason why the DTB ended up in a partition instead of as a regular file. It would be interesting if this could be done, but I don’t know of a way.

Solved by using 4.1.1

[s]I have a similar issue.

This should be a fresh Jetson AGX Xavier. (corporate environment, so not sure, maybe others messed up with the device)

After entering USB recovery mode, the device appears as:

Bus 001 Device 030: ID 0403:6011 Future Technology Devices International, Ltd FT4232H Quad HS USB-UART/FIFO IC

instead of 0955:7c18, as above.

As such, Jetpack won’t install anything on the device.

Where can I go from here ?

Edit:
I realize this is not the correct way, but as a debugging step, if I use the USB-C port instead of the
micro-USB port, lsusb shows:
Bus 001 Device 035: ID 0955:7019 NVidia Corp.
Adding this just in case it provide useful information. I’m actually trying with the micro-USB port.[/s]

If you see FTDI and R31.1 works, then it means you have an Xavier, not a TX2. The original thread is for TX2, so that would explain it (and Xavier doesn’t work with releases prior to R31.x).

Hi,
Sry for reactivating that thread.

I have a similar issue with the Xavier NX DevKit. The Force Recovery pin does not seem to be able to set the device into force recovery mode. It starts as if the pin is not set. This is only a recent phenomenon though as it worked until a few days ago. I am not running a VM or anything and I tried all USB ports on my Host PC ( USB2.0, USB3.0 … ).

When looking at the dmesg output there are some error Messages ( WARN Cannot submit Set TR Deq Ptr ) that are not present when the system is started without the FC pin beeing set.

The lsusb output seems to be identical in both cases.

dmesg Output when FC is set:

[21412.583036] usb 1-6: USB disconnect, device number 61
[21412.583168] rndis_host 1-6:1.0 enp0s20f0u6: unregister 'rndis_host' usb-0000:00:14.0-6, RNDIS device
[21412.583396] xhci_hcd 0000:00:14.0: WARN Cannot submit Set TR Deq Ptr**
[21412.583398] xhci_hcd 0000:00:14.0: A Set TR Deq Ptr command is pending.**
[21412.583479] xhci_hcd 0000:00:14.0: WARN Cannot submit Set TR Deq Ptr**
[21412.583482] xhci_hcd 0000:00:14.0: A Set TR Deq Ptr command is pending.**
[21412.583493] xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.**
[21412.680388] cdc_ncm 1-6:1.5 enp0s20f0u6i5: unregister 'cdc_ncm' usb-0000:00:14.0-6, CDC NCM
[21444.464333] usb 1-6: new high-speed USB device number 62 using xhci_hcd
[21444.613250] usb 1-6: New USB device found, idVendor=0955, idProduct=7020, bcdDevice= 0.02
[21444.613255] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[21444.613259] usb 1-6: Product: Linux for Tegra
[21444.613261] usb 1-6: Manufacturer: NVIDIA
[21444.613264] usb 1-6: SerialNumber: 1421520056767
[21444.621483] rndis_host 1-6:1.0 usb0: register 'rndis_host' at usb-0000:00:14.0-6, RNDIS device, 96:3d:04:45:8f:63
[21444.622626] cdc_acm 1-6:1.2: ttyACM0: USB ACM device
[21444.623332] usb-storage 1-6:1.4: USB Mass Storage device detected
[21444.623767] scsi host6: usb-storage 1-6:1.4
[21444.646882] cdc_ncm 1-6:1.5: MAC-Address: be:76:ca:df:00:42
[21444.647039] cdc_ncm 1-6:1.5 usb1: register 'cdc_ncm' at usb-0000:00:14.0-6, CDC NCM, be:76:ca:df:00:42
[21444.666725] rndis_host 1-6:1.0 enp0s20f0u6: renamed from usb0
[21444.689213] cdc_ncm 1-6:1.5 enp0s20f0u6i5: renamed from usb1
[21444.771329] cdc_ncm 1-6:1.5 enp0s20f0u6i5: 425 mbit/s downlink 425 mbit/s uplink
[21444.803274] cdc_ncm 1-6:1.5 enp0s20f0u6i5: 425 mbit/s downlink 425 mbit/s uplink
[21444.835290] cdc_ncm 1-6:1.5 enp0s20f0u6i5: network connection: connected
[21444.835336] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s20f0u6i5: link becomes ready
[21445.653181] scsi 6:0:0:0: Direct-Access     Linux    File-Stor Gadget 0409 PQ: 0 ANSI: 2
[21445.654093] sd 6:0:0:0: Attached scsi generic sg3 type 0
[21445.654190] sd 6:0:0:0: Power-on or device reset occurred
[21445.654554] sd 6:0:0:0: [sdc] 32768 512-byte logical blocks: (16.8 MB/16.0 MiB)
[21445.654720] sd 6:0:0:0: [sdc] Write Protect is on
[21445.654724] sd 6:0:0:0: [sdc] Mode Sense: 0f 00 80 00
[21445.654862] sd 6:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[21445.673810]  sdc:
[21445.675025] sd 6:0:0:0: [sdc] Attached SCSI removable disk

dmesg Output when FC is not set:

[21550.370048] usb 1-6: USB disconnect, device number 62
[21550.370232] rndis_host 1-6:1.0 enp0s20f0u6: unregister 'rndis_host' usb-0000:00:14.0-6, RNDIS device
[21550.453061] cdc_ncm 1-6:1.5 enp0s20f0u6i5: unregister 'cdc_ncm' usb-0000:00:14.0-6, CDC NCM
[21580.380709] usb 1-6: new high-speed USB device number 63 using xhci_hcd
[21580.530297] usb 1-6: New USB device found, idVendor=0955, idProduct=7020, bcdDevice= 0.02
[21580.530302] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[21580.530305] usb 1-6: Product: Linux for Tegra
[21580.530307] usb 1-6: Manufacturer: NVIDIA
[21580.530310] usb 1-6: SerialNumber: 1421520056767
[21580.535949] rndis_host 1-6:1.0 usb0: register 'rndis_host' at usb-0000:00:14.0-6, RNDIS device, ea:7d:0b:74:24:ec
[21580.537526] cdc_acm 1-6:1.2: ttyACM0: USB ACM device
[21580.538642] usb-storage 1-6:1.4: USB Mass Storage device detected
[21580.539159] scsi host6: usb-storage 1-6:1.4
[21580.562961] cdc_ncm 1-6:1.5: MAC-Address: be:76:ca:df:00:42
[21580.563119] cdc_ncm 1-6:1.5 usb1: register 'cdc_ncm' at usb-0000:00:14.0-6, CDC NCM, be:76:ca:df:00:42
[21580.582484] rndis_host 1-6:1.0 enp0s20f0u6: renamed from usb0
[21580.605555] cdc_ncm 1-6:1.5 enp0s20f0u6i5: renamed from usb1
[21580.675572] cdc_ncm 1-6:1.5 enp0s20f0u6i5: 425 mbit/s downlink 425 mbit/s uplink
[21580.707580] cdc_ncm 1-6:1.5 enp0s20f0u6i5: 425 mbit/s downlink 425 mbit/s uplink
[21580.739579] cdc_ncm 1-6:1.5 enp0s20f0u6i5: network connection: connected
[21580.739638] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s20f0u6i5: link becomes ready
[21581.557630] scsi 6:0:0:0: Direct-Access     Linux    File-Stor Gadget 0409 PQ: 0 ANSI: 2
[21581.558167] sd 6:0:0:0: Attached scsi generic sg3 type 0
[21581.558510] sd 6:0:0:0: Power-on or device reset occurred
[21581.559026] sd 6:0:0:0: [sdc] 32768 512-byte logical blocks: (16.8 MB/16.0 MiB)
[21581.559217] sd 6:0:0:0: [sdc] Write Protect is on
[21581.559221] sd 6:0:0:0: [sdc] Mode Sense: 0f 00 80 00
[21581.559393] sd 6:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[21581.578076]  sdc:
[21581.579015] sd 6:0:0:0: [sdc] Attached SCSI removable disk

I don’t know about the specific dmesg differences, but assuming this is on the host PC, then this is definitely a booted Jetson and not a recovery mode Jetson. However…and this is a big however…the original thread is for the TX2, not the Xavier, and while the TX2 uses the micro-USB connector for this, the Xavier uses the USB-C for recovery mode flashing. I am guessing you are just using the wrong USB port.

Thanks for your quick reply but flashing the Xavier NX Dev Kit over this port worked in the past ( with the same Host PC ).