Cannot flash jetson orin nano with any method

yadu.morakkatte · April 16, 2024, 10:35pm

SDKM_logs_JetPack_6.0_DP_Linux_for_Jetson_Orin_Nano_modules_2024-04-16_18-15-32.zip (123.9 KB)

I’ve tried flashing with the sdkmanager, etcher, and from the command line. Tried the SD card and the NVMe. Nothing works. In the attached logs am using Ubuntu 22.04, trying to flash jetpack 6.0 to the NVMe. This is a native host PC, not a VM. I am putting the device in recovery mode, when I type lsusb I see this: ID 0955:7523 NVIDIA Corp. APX
I have tried leaving the jumper in during flashing, and taking it out before flashing. Neither work.

I am getting the following errors:

18:16:03 INFO: exec_command: true
18:16:03 INFO: command finished successfully
18:16:03 DEBUG: running command < /tmp/device_mode_host_setup.ysunil3.sh >
18:16:03 INFO: exec_command: /tmp/device_mode_host_setup.ysunil3.sh
18:16:03 INFO: Found route default enp0s31f6, setting up device mode
18:16:03 INFO: [host] [sudo] password for ysunil3:
18:16:03 INFO: net.ipv4.ip_forward = 1
18:16:03 INFO: Device mode on host successfully set with DNS 8.8.8.8!
18:16:03 INFO: command finished successfully
18:16:03 DEBUG: running command < true >
18:16:03 INFO: exec_command: true
18:16:03 INFO: Flash Jetson Linux - flash: sudo ./nvsdkmanager_flash.sh --storage nvme0n1p1 --nv-auto-config --username saferobolab
18:20:32 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 270000
18:20:32 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 320000
18:20:33 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 350000
18:20:33 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 360000
18:20:33 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 420000
18:20:33 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 430000
18:20:33 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 440000
18:20:33 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 450000
18:20:33 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 460000
18:20:33 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 470000
18:20:33 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 480000
18:20:33 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 490000
18:20:33 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 500000
18:20:34 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 510000
18:20:34 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 520000
18:20:34 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 530000
18:20:34 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 540000
18:20:34 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 550000
18:20:34 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 560000
18:20:34 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 570000
18:20:34 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 580000
18:20:34 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 590000
18:20:34 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 600000
18:20:35 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 610000
18:20:35 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 620000
18:20:35 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 630000
18:20:35 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 640000
18:20:35 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 650000
18:20:45 ERROR: Flash Jetson Linux - flash: 52057 blocks
18:20:45 ERROR: Flash Jetson Linux - flash: gzip: /home/ysunil3/nvidia/nvidia_sdk/JetPack_6.0_DP_Linux_DP_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/kernel/Image: not in gzip format
18:20:49 ERROR: Flash Jetson Linux - flash: 74756 blocks
18:20:50 ERROR: Flash Jetson Linux - flash: 20 bytes copied, 7.9361e-05 s, 252 kB/s
18:20:50 ERROR: Flash Jetson Linux - flash: 67108864 bytes (67 MB, 64 MiB) copied, 0.1104 s, 608 MB/s
18:20:55 ERROR: Flash Jetson Linux - flash: /home/ysunil3/nvidia/nvidia_sdk/JetPack_6.0_DP_Linux_DP_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/bootloader/L4TConfiguration_updated.dts: Warning (unit_address_vs_reg): Node /fragment@0 has a unit name, but no reg property
18:20:55 ERROR: Flash Jetson Linux - flash: /home/ysunil3/nvidia/nvidia_sdk/JetPack_6.0_DP_Linux_DP_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/bootloader/L4TConfiguration.dtbo: Warning (unit_address_vs_reg): Node /fragment@0 has a unit name, but no reg property
18:20:56 ERROR: Flash Jetson Linux - flash: [ 0.2989 ] ERROR: value 0x31 is out of range
18:20:58 ERROR: Flash Jetson Linux - flash: [ 2.2666 ] ERROR: value 0x31 is out of range
18:20:59 ERROR: Flash Jetson Linux - flash: 74756 blocks
18:21:06 ERROR: Flash Jetson Linux - flash: 128307 blocks
18:29:02 ERROR: Flash Jetson Linux - flash: command terminated with error
18:29:02 SUMMARY: Flash Jetson Linux - flash: First Error: Installation failed.

I tried this in case the rcm error was because of this:
Q: I get a USB timeout error during flash Orin. How to resolve that?
A known issue for ubuntu 20.04 host is the USB autosuspend function is enabled on it by default. This leads to Jetson recovery mode gets suspended before flash. To bypass this error, need to:
Disable autosuspend on host PC with below command:
sudo -s
echo -1 > /sys/module/usbcore/parameters/autosuspend
Plug out the USB cable, put jetson back into recovery mode again and plug the usb cable back.
If USB timeout is still there after above commands, please file a topic to forum and let moderator help check.

Still doesnt work.

DaveYYY · April 17, 2024, 1:53am

Waiting for device to expose ssh ...Run command: flash on fc00:1:1:0::2
SSH ready
mount.nfs: Connection timed out
Flash failure
Cleaning up...

Do you have nfs-common and nfs-kernel-server installed on your host PC?
Or maybe with a different USB cable.

remy415 · April 17, 2024, 3:16am

I don’t know if this will help, but when I am flashing my Orin Nano 8gb (using a Turing Pi 2 board), I get the “waiting for device to boot up…” message. I found an obscure forum post somewhere that actually fixed everything:

https://forum.turingpi.com/t/16218946/turing-pi-v2-orin-nx-v36-2-ubuntu-22-04-kernel-5-15-122-tegr#0f458a94-52cb-4818-9448-febb2ab50a92

TL;DR: Try the “disable NFSv4 after ./apply_binaries.sh”, and add the “echo on > /sys/bus/usb/devices/usb2/power/control” to line 222 of “tools/kernel_flash/initrd_flash/nv_enable_remote.sh”. Note: I’m using the standard flash methods via usb to NVMe, not using the sdkmanager.

yadu.morakkatte · April 17, 2024, 6:06pm

I will look into this and let you know!

yadu.morakkatte · April 17, 2024, 6:06pm

I will try this!

yadu.morakkatte · April 18, 2024, 6:25pm

So I tried this, but looks like it is still not working

boeroboy · April 18, 2024, 6:52pm

I’m in the same boat. I see plenty of past threads about this but it seems like they are prior generations of the dev board or Nano module.

This is USB-C (not Micro-USB) and I can’t get a USB detected in any case. Latest flash to MicroSD boots to a dead screen as previously reported by numerous users. USB in dmesg is full of “Cannot enable, Maybe the USB cable is bad?” Trying multiple devices and 5 different USB cables shows no difference.

The only way I can make any use of this pricey bit of kit is to switch from Device Tree to ACPI mode and boot Fedora on NVMe which works fine but without the proper GPU drivers. Is this just a problem with newer generation modules/dev boards? What a rocky dev experience. It looks like my model is the latest P3767-0005 module in a P3768-0000 carrier board.

Finally booted in recovery mode via poor-man’s jumper. I wouldn’t recommend this but it was picked up instantly when I plugged it back in. All seems good. Funny they don’t bother to include jumpers in this kit.

yadu.morakkatte · April 18, 2024, 7:16pm

I tried this as well, but no luck
Flashing terminal.pdf (420.6 KB)

This ended in flash failure. My computer does recognize the device, so does sdkmanager. However I do see during the flashing process, it seems to disconnect and reconnect, not sure if that is expected? I have tried multiple USB cables.

I always seem to get these in sdkmanager:
14:18:27 ERROR: Flash Jetson Linux - flash: [ 0.0193 ] ERROR: failed to read rcm_state

14:18:27 ERROR: Flash Jetson Linux - flash: [ 0.1196 ] Error: Skip generating mem_bct because sdram_config is not defined

Not sure why rcm_state seems to never be able to be read. This whole process has been so draining.

remy415 · April 18, 2024, 7:31pm

Are either of you using the official NV Dev board with your Orins, or are you using a “custom” board, such as the Turing Pi 2?

If you’re using a custom board, please see this:

====================================================
EEPROM is an optional component for a customized carrier board. In the case the carrier board
is designed without an EEPROM, below modifications will be needed on the MB2 BCT file:
Linux_for_Tegra/bootloader/tegra234-mb2-bct-common.dtsi
-cvb_eeprom_read_size = <0x100>
+cvb_eeprom_read_size = <0x0>

====================================================

In the case of JP6 on an Orin, the file is bootloader/generic/BCT/tegra234-mb2-bct-misc-p3767-0000.dts

yadu.morakkatte · April 18, 2024, 8:20pm

I am using the official NVIDIA Jetson Orin Nano Developer Kit

DaveYYY · April 19, 2024, 1:47am

Formatting APP parition done
Formatting APP partition /dev/nvme0n1p1 ...
tar -xpf /mnt/external/system.img --checkpoint=10000 --warning=no-timestamp --numeric-owner
--xattrs --xattrs-include=* -C /tmp/ci-qgGjQAXVcJ
tar: Re14:18:27 ERROR: Flash Jetson Linux - flash: [ 0.0193 ] ERROR: failed to read rcm_state
14:18:27 ERROR: Flash Jetson Linux - flash: [ 0.1196 ] Error: Skip generating mem_bct
because sdram_config is not defined
14:18:27 ERROR: Flash Jetson Linux - flash: [ 0.1196 ] Error: Skip generating mem_bct
because sdram_config is not definedad checkpoint 10000
tar: Read checkpoint 20000
tar: Read checkpoint 30000

This means the NFS error seen before has been resolved, but writing to the NVMe drive is somehow disrupted.
You can try using a diffrent USB cable, or prepare the disk by connecting it to the host manually like this:
https://docs.nvidia.com/jetson/archives/r36.2/DeveloperGuide/SD/FlashingSupport.html#flashing-to-an-nvme-drive

system · May 21, 2024, 8:01am

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Erro with Jetson Orin Nano flashing with sdkmanager Jetson Orin Nano reflash	27	2517	June 7, 2023
Issue trying to flash Jetpack 6.2 on SSD Jetson Orin Nano reflash	11	447	January 24, 2025
Jetson Orin Nano does not boot after flashing Jetpack 6 Jetson Orin Nano sdkm , boot	29	3831	January 16, 2024
Unable to flash to NVMe Jetson Orin Nano reflash	19	3165	May 1, 2023
Flashing Orin Nano Failed ("carveout is not supported" and other errors) Jetson Orin Nano	24	3910	April 15, 2023
Unable to Flash R36 on Orin Nano 8GB Dev Kit Using External Storage Jetson Orin Nano reflash	31	3178	January 20, 2024
Jetson Orin Nano Dev Kit 8GB Unable to Flash Through SDK Manager Jetson Orin Nano sdkm	7	1701	June 7, 2023
Jetson Orin Nano devkit flash failing Jetson Orin Nano flash	10	108	July 3, 2024
Jetson Orin Nano Failed to Flash on SDK Jetson Orin Nano reflash	6	822	April 24, 2024
Failure to flash Jetson Orin Nano Devkit, currently bricked Jetson Orin Nano boot , reflash	6	53	March 3, 2025

Cannot flash jetson orin nano with any method

Related topics