Jetson Orin Nano will not flash

Unable to flash Jetson orin nano after a dozen attempts to nvme. Tried both nvme slots with multiple nvme drives which work on my other Jetson developer platforms. Always fails at 98 or 99%. I’ve used the same hp pc to successfully flash multiple jetsons, including another jetson orin nano, jetson orin agx, Jetson nano tx2nx, jetson nano. I’m not using virtualization. Also tried different usb-c data cables.

Thanks for any help you can provide

please let me know which logs will help to troubleshoot this and if there is a way to upload the full SDKM_logs_JetPack_6.0_DP_Linux_for_Jetson_Orin_Nano_modules… .zip file

You didn’t even upload the log.

Thanks, as mentioned I have the zip file full of logs. I don’t see where there is a button that allows me to upload. Where do I upload? The zip file has over a dozen log type files in it, so it seems unreasonable to copy all of them manually in a text box. If there is a particular file in the zip I’d be happy to copy that int the text field, just let me know which one

You just drag the file to the dialog box.
Nothing difficult at all…

SDKM_logs_JetPack_6.0_DP_Linux_for_Jetson_Orin_Nano_modules_2024-03-12_17-55-35.zip (123.7 KB)

Are you sure it’s the full log?
It fails in the very early stage.
Please also do this:

The screen had a giant error message showing a failure, and after that I selected the export and it provided that zip file. I’ll go ahead and follow the article and provide the results. Thanks

Here is the error screen I received on my final attempt last night, I believe I tried again after I opened the ticket. I think switched to the 2230 NVMe with a different nvme drive. I’ll run the process you requested now.


SDKM_logs_JetPack_6.0_DP_Linux_for_Jetson_Orin_Nano_modules_2024-03-12_17-55-35.zip (123.7 KB)

Ok, i have setup the ftdi and oddly enough nothing showed up in minicom when I booted the orin nano. Not sure what you wanted me to do afterwards, so currently running sdk manager to setup and minicom is display the flash process. Ill update with its output once complete and after attempting to connect when the setup completes or errors out, and any error logs if they recur. Is there something else I should try logging with minicom? Thanks

Just dump everything you get from minicom when flashing.

Hey Dave, here is the minicom log. I ran the process twice with the same results. It does prompt about taking longer than expected, but selecting yes just causes it to continue running without logging any new records into minicom. Choosing no displays the installation failure error. Powering off/on afterwords does not have any results showing in minicom
minicom.cap.txt (4.3 KB)

Is it a DevKit?
Try flashing manually under Linux_for_Tegra with the following command:

 sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 \
 -c tools/kernel_flash/flash_l4t_external.xml -p "-c bootloader/generic/cfg/flash_t234_qspi.xml" \
 --showlogs --network usb0 jetson-orin-nano-devkit internal

Then attach log from both host and device.

It appears to have just hung again, must have been over an hour+

minicom.com.txt (4.3 KB)
out.txt (10.2 KB)

You didn’t answer this.
Have you tried other flashing cable/host PC?

yes it is

See if this works:

sudo ./flash.sh --no-systemimg -c bootloader/generic/cfg/flash_t234_qspi.xml jetson-orin-nano-devkit internal

It will flash only the internal QSPI bootloader.

I let it run overnight.

qspi.txt (18.7 KB)

You should follow these steps exactly and in this order. Use an USB hub if possible.

  1. Unplug the USB flashing cable from the USB hub and from the Jetson
  2. Power off the Jetson
  3. Run this command on the host
 sudo -s
 echo -1 > /sys/module/usbcore/parameters/autosuspend
  1. Replug the USB cable into the USB hub and the Jetson
  2. Power on the Jetson and put it into recovery mode
  3. Flash
 sudo ./flash.sh --no-systemimg -c bootloader/generic/cfg/flash_t234_qspi.xml jetson-orin-nano-devkit internal
1 Like

Hi, it’s been running 4 or 5 hours is that to be expected? Here is the current output:

[   0.0317 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[   0.0322 ] File rcm_state open failed
[   0.0326 ] ERROR: failed to read rcm_state
[   0.0338 ] tegrasign_v3.py --key None --getmode mode.txt
[   0.0340 ] Assuming zero filled SBK key
[   0.0331 ] Pre-processing config: tegra234-mb1-bct-device-p3767-0000.dts
[   0.0510 ] Pre-processing config: tegra234-mb1-bct-misc-p3767-0000.dts
[   0.0834 ] Parsing partition layout
[   0.0841 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[   0.0859 ] Kernel DTB used: None
[   0.0860 ] WARNING: dce base dtb is not provided

[   0.0860 ] Parsing partition layout
[   0.0866 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[   0.0879 ] Creating list of images to be signed
[   0.0884 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --list images_list.xml zerosbk
[   0.0889 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin
[   0.0921 ] Header already present for mb1_t234_prod_aligned_sigheader.bin
[   0.0936 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin
[   0.1127 ] Header already present for mb1_t234_prod_aligned_sigheader.bin
[   0.1143 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin
[   0.1327 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin
[   0.1334 ] adding BCH for mb2_t234_aligned.bin
[   0.1405 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin
[   0.1578 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin
[   0.1584 ] adding BCH for mb2_t234_aligned.bin
[   0.1782 ] Filling MB1 storage info
[   0.1783 ] Parsing dev params for multi chains
[   0.1901 ] Generating br-bct
[   0.1908 ] Updating dev and MSS params in BR BCT
[   0.1909 ] tegrabct_v2 --dev_param tegra234-br-bct-diag-boot_cpp.dtb --brbct br_bct.cfg --chip 0x23 0
[   0.1924 ] Updating bl info
[   0.1932 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updateblinfo readinfo_t234_min_prod.xml.bin
[   0.1939 ] WARNING: boot chain is not completed. set to 0
[   0.1961 ] Generating signatures
[   0.1972 ] tegrasign_v3.py --key None --list images_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.1974 ] Assuming zero filled SBK key
[   0.2256 ] Warning: pub_key.key is not found
[   0.2250 ] Parsing dev params for multi chains
[   0.2250 ] Generating br-bct
[   0.2256 ] Updating dev and MSS params in BR BCT
[   0.2257 ] tegrabct_v2 --dev_param tegra234-br-bct-diag-boot_cpp.dtb --brbct br_bct.cfg --chip 0x23 0
[   0.2275 ] Updating bl info
[   0.2281 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updateblinfo readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
[   0.2287 ] WARNING: boot chain is not completed. set to 0
[   0.2308 ] Generating SHA2 Hash
[   0.2334 ] Sha saved in br_bct_BR.sha
[   0.2325 ] Get Signed section of bct
[   0.2332 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --listbct bct_list.xml
[   0.2346 ] Signing BCT
[   0.2358 ] tegrasign_v3.py --key None --list bct_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.2360 ] Assuming zero filled SBK key
[   0.2407 ] Sha saved in br_bct_BR.sha
[   0.2412 ] Warning: pub_key.key is not found
[   0.2401 ] Updating BCT with signature
[   0.2407 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesig bct_list_signed.xml
[   0.2413 ] Offset :4608 Len :3584
[   0.2426 ] Generating SHA2 Hash
[   0.2437 ] tegrasign_v3.py --key None --list bct_list.xml --sha sha512
[   0.2439 ] Assuming zero filled SBK key
[   0.2440 ] Assuming zero filled SBK key
[   0.2489 ] Sha saved in br_bct_BR.sha
[   0.2483 ] Updating BCT with SHA2 Hash
[   0.2489 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesha bct_list_signed.xml
[   0.2496 ] Offset :4608 Len :3584
[   0.2506 ] Offset :68 Len :8124
[   0.2513 ] Generating coldboot mb1-bct
[   0.2521 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_cold_boot_bct.cfg --misc tegra234-mb1-bct-misc-p3767-0000_cpp.dtb --device tegra234-mb1-bct-device-p3767-0000_cpp.dtb
[   0.2528 ] MB1-BCT version: 0.13

[   0.2563 ] Parsing config file :tegra234-mb1-bct-device-p3767-0000_cpp.dtb 
[   0.2570 ] Added Platform Config 9 data with size :- 100
[   0.2570 ] 
[   0.2570 ] Updating mb1-bct with firmware information
[   0.2578 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_cold_boot_bct_MB1.bct --updatefwinfo readinfo_t234_min_prod.xml.bin
[   0.2601 ] tegrahost_v2 --chip 0x23 0 --align mb1_cold_boot_bct_MB1_aligned.bct
[   0.2616 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --appendsigheader mb1_cold_boot_bct_MB1_aligned.bct zerosbk
[   0.2621 ] adding BCH for mb1_cold_boot_bct_MB1_aligned.bct
[   0.2648 ] tegrasign_v3.py --key None --list mb1_cold_boot_bct_MB1_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.2649 ] Assuming zero filled SBK key
[   0.2676 ] Warning: pub_key.key is not found
[   0.2671 ] tegrahost_v2 --chip 0x23 0 --updatesigheader mb1_cold_boot_bct_MB1_aligned_sigheader.bct.encrypt mb1_cold_boot_bct_MB1_aligned_sigheader.bct.hash zerosbk
[   0.2689 ] Generating recovery mb1-bct
[   0.2694 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_bct.cfg --misc tegra234-mb1-bct-misc-p3767-0000_cpp.dtb --device tegra234-mb1-bct-device-p3767-0000_cpp.dtb
[   0.2698 ] MB1-BCT version: 0.13

[   0.2733 ] Parsing config file :tegra234-mb1-bct-device-p3767-0000_cpp.dtb 
[   0.2736 ] Added Platform Config 9 data with size :- 100
[   0.2738 ] Updating mb1-bct with firmware information
[   0.2743 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_bct_MB1.bct --recov --updatefwinfo readinfo_t234_min_prod.xml.bin
[   0.2762 ] tegrahost_v2 --chip 0x23 0 --align mb1_bct_MB1_aligned.bct
[   0.2770 ] Generating SHA2 Hash for mb1bct
[   0.2803 ] Sha saved in mb1_bct_MB1_aligned.sha
[   0.2798 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --appendsigheader mb1_bct_MB1_aligned.bct zerosbk
[   0.2803 ] adding BCH for mb1_bct_MB1_aligned.bct
[   0.2837 ] tegrasign_v3.py --key None --list mb1_bct_MB1_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.2839 ] Assuming zero filled SBK key
[   0.2867 ] Warning: pub_key.key is not found
[   0.2864 ] tegrahost_v2 --chip 0x23 0 --updatesigheader mb1_bct_MB1_aligned_sigheader.bct.encrypt mb1_bct_MB1_aligned_sigheader.bct.hash zerosbk
[   0.2884 ] Error: Skip generating mem_bct because sdram_config is not defined
[   0.2884 ] Error: Skip generating mem_bct because sdram_config is not defined
[   0.2884 ] Copying signatures
[   0.2889 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
[   0.3045 ] mb1_t234_prod_aligned_sigheader.bin.encrypt filename is from images_list
[   0.3047 ] psc_bl1_t234_prod_aligned_sigheader.bin.encrypt filename is from images_list
[   0.3047 ] Boot Rom communication
[   0.3054 ] tegrarcm_v2 --new_session --chip 0x23 0 --uid --download bct_br br_bct_BR.bct --download mb1 mb1_t234_prod_aligned_sigheader.bin.encrypt --download psc_bl1 psc_bl1_t234_prod_aligned_sigheader.bin.encrypt --download bct_mb1 mb1_bct_MB1_sigheader.bct.encrypt
[   0.3060 ] BR_CID: 0x80012344705DE64C7800000002FE8240
[   0.3985 ] Sending bct_br
[   0.4825 ] Sending mb1
[   0.4833 ] Sending psc_bl1
[   0.4944 ] Sending bct_mb1
[   0.5006 ] Boot Rom communication completed
[   0.5025 ] tegrahost_v2 --chip 0x23 0 --align applet_t234_aligned.bin
[   0.5042 ] tegrahost_v2 --chip 0x23 0 --magicid MB2A --appendsigheader applet_t234_aligned.bin zerosbk
[   0.5047 ] adding BCH for applet_t234_aligned.bin
[   0.5319 ] tegrasign_v3.py --key None --list applet_t234_aligned_sigheader.bin_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.5322 ] Assuming zero filled SBK key
[   0.5373 ] Warning: pub_key.key is not found
[   0.5371 ] tegrahost_v2 --chip 0x23 0 --updatesigheader applet_t234_aligned_sigheader.bin.encrypt applet_t234_aligned_sigheader.bin.hash zerosbk
[   0.5414 ] Sending mb2_applet...

[   0.5423 ] tegrarcm_v2 --chip 0x23 0 --pollbl --download applet applet_t234_sigheader.bin.encrypt
[   0.5432 ] BL: version 1.4.0.1-t234-54845784-08e631ca last_boot_error: 0
[   0.7250 ] Sending applet
[   0.8431 ] completed
[   0.8440 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[   2.0321 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 1007.0458 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 2022.8537 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 3038.6614 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 4054.4699 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 5070.2775 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 6086.0860 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 7101.8933 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 8117.7031 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 9133.5091 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 10149.3177 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 11165.1257 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 12180.9337 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 13196.7416 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 14212.5497 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 15228.3577 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 16244.1652 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 17259.9740 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 18275.7820 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 19291.5897 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet

Dump the log as indicated here.