Could not flash my brand new Jetson Orin Nano 8G Devkit

Just bought a new flashing cable (10Gbps USB 3.1 Gen 2 USB A to USB C Data Transfer Cord), then ran the above command again, it still failed with different error below:

###############################################################################

L4T BSP Information:

R36 , REVISION: 2.0

User release: 0.0

###############################################################################

ECID is 0x80012344705DE4422800000010FE81C0

Target Board Information:

Name: jetson-orin-nano-devkit, Board Family: generic, SoC: Tegra 234,

OpMode: production, Boot Authentication: NS,

Disk encryption: disabled ,

###############################################################################

copying emc_fuse_dev_params(/home/vboxuser/nvidia/nvidia_sdk/JetPack_6.0_DP_Linux_DP_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/bootloader/generic/BCT/tegra234-br-bct-diag-boot.dts)… done.

copying device_config(/home/vboxuser/nvidia/nvidia_sdk/JetPack_6.0_DP_Linux_DP_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/bootloader/generic/BCT/tegra234-mb1-bct-device-p3767-0000.dts)… done.

copying misc_config(/home/vboxuser/nvidia/nvidia_sdk/JetPack_6.0_DP_Linux_DP_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/bootloader/generic/BCT/tegra234-mb1-bct-misc-p3767-0000.dts)… done.

./tegraflash.py --chip “0x23” --applet “/home/vboxuser/nvidia/nvidia_sdk/JetPack_6.0_DP_Linux_DP_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/bootloader/mb1_t234_prod.bin” --skipuid --cfg readinfo_t234_min_prod.xml --dev_params tegra234-br-bct-diag-boot.dts --device_config tegra234-mb1-bct-device-p3767-0000.dts --misc_config tegra234-mb1-bct-misc-p3767-0000.dts --bins “mb2_applet applet_t234.bin” --cmd “dump eeprom cvm cvm.bin; dump try_custinfo custinfo_out.bin; reboot recovery”

Welcome to Tegra Flash

version 1.0.0

Type ? or help for help and q or quit to exit

Use ! to execute system commands

[ 0.0614 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet

[ 0.0635 ] File rcm_state open failed

[ 0.0643 ] ERROR: failed to read rcm_state

[ 0.0643 ]

[ 0.0696 ] tegrasign_v3.py --key None --getmode mode.txt

[ 0.0702 ] Assuming zero filled SBK key

[ 0.0656 ] Pre-processing config: tegra234-mb1-bct-device-p3767-0000.dts

[ 0.1033 ] Pre-processing config: tegra234-mb1-bct-misc-p3767-0000.dts

[ 0.2353 ] Parsing partition layout

[ 0.2862 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp

[ 0.2949 ] Kernel DTB used: None

[ 0.2949 ] WARNING: dce base dtb is not provided

[ 0.2949 ] Parsing partition layout

[ 0.2983 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp

[ 0.3016 ] Creating list of images to be signed

[ 0.3060 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --list images_list.xml zerosbk

[ 0.3095 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin

[ 0.3233 ] Header already present for mb1_t234_prod_aligned_sigheader.bin

[ 0.3242 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin

[ 0.3614 ] Header already present for mb1_t234_prod_aligned_sigheader.bin

[ 0.3616 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin

[ 0.3759 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin

[ 0.3779 ] adding BCH for mb2_t234_aligned.bin

[ 0.3865 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin

[ 0.4563 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin

[ 0.4843 ] adding BCH for mb2_t234_aligned.bin

[ 0.5679 ] Filling MB1 storage info

[ 0.5679 ] Parsing dev params for multi chains

[ 0.5975 ] Generating br-bct

[ 0.6012 ] Updating dev and MSS params in BR BCT

[ 0.6013 ] tegrabct_v2 --dev_param tegra234-br-bct-diag-boot_cpp.dtb --brbct br_bct.cfg --chip 0x23 0

[ 0.6253 ] Updating bl info

[ 0.6289 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updateblinfo readinfo_t234_min_prod.xml.bin

[ 0.6318 ] WARNING: boot chain is not completed. set to 0

[ 0.6368 ] Generating signatures

[ 0.6423 ] tegrasign_v3.py --key None --list images_list.xml --pubkeyhash pub_key.key --sha sha512

[ 0.6431 ] Assuming zero filled SBK key

[ 0.8183 ] Warning: pub_key.key is not found

[ 0.8136 ] Parsing dev params for multi chains

[ 0.8138 ] Generating br-bct

[ 0.8152 ] Updating dev and MSS params in BR BCT

[ 0.8154 ] tegrabct_v2 --dev_param tegra234-br-bct-diag-boot_cpp.dtb --brbct br_bct.cfg --chip 0x23 0

[ 0.8204 ] Updating bl info

[ 0.8219 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updateblinfo readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml

[ 0.8235 ] WARNING: boot chain is not completed. set to 0

[ 0.8396 ] Generating SHA2 Hash

[ 0.8660 ] Sha saved in br_bct_BR.sha

[ 0.8613 ] Get Signed section of bct

[ 0.8634 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --listbct bct_list.xml

[ 0.8687 ] Signing BCT

[ 0.8744 ] tegrasign_v3.py --key None --list bct_list.xml --pubkeyhash pub_key.key --sha sha512

[ 0.8751 ] Assuming zero filled SBK key

[ 0.8843 ] Sha saved in br_bct_BR.sha

[ 0.8851 ] Warning: pub_key.key is not found

[ 0.8800 ] Updating BCT with signature

[ 0.8808 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesig bct_list_signed.xml

[ 0.8960 ] Offset :4608 Len :3584

[ 0.8993 ] Generating SHA2 Hash

[ 0.9047 ] tegrasign_v3.py --key None --list bct_list.xml --sha sha512

[ 0.9052 ] Assuming zero filled SBK key

[ 0.9052 ] Assuming zero filled SBK key

[ 0.9681 ] Sha saved in br_bct_BR.sha

[ 0.9744 ] Updating BCT with SHA2 Hash

[ 0.9917 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesha bct_list_signed.xml

[ 1.0243 ] Offset :4608 Len :3584

[ 1.0245 ] Offset :68 Len :8124

[ 1.0512 ] Generating coldboot mb1-bct

[ 1.0534 ] 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

[ 1.0591 ] MB1-BCT version: 0.13

[ 1.0594 ]

[ 1.0594 ] Parsing config file :tegra234-mb1-bct-device-p3767-0000_cpp.dtb

[ 1.0594 ] Added Platform Config 9 data with size :- 100

[ 1.0594 ]

[ 1.0595 ] Updating mb1-bct with firmware information

[ 1.0614 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_cold_boot_bct_MB1.bct --updatefwinfo readinfo_t234_min_prod.xml.bin

[ 1.0697 ] tegrahost_v2 --chip 0x23 0 --align mb1_cold_boot_bct_MB1_aligned.bct

[ 1.0829 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --appendsigheader mb1_cold_boot_bct_MB1_aligned.bct zerosbk

[ 1.0900 ] adding BCH for mb1_cold_boot_bct_MB1_aligned.bct

[ 1.0984 ] tegrasign_v3.py --key None --list mb1_cold_boot_bct_MB1_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key --sha sha512

[ 1.0994 ] Assuming zero filled SBK key

[ 1.1036 ] Warning: pub_key.key is not found

[ 1.1048 ] 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

[ 1.1087 ] Generating recovery mb1-bct

[ 1.1110 ] 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

[ 1.1173 ] MB1-BCT version: 0.13

[ 1.1187 ]

[ 1.1187 ] Parsing config file :tegra234-mb1-bct-device-p3767-0000_cpp.dtb

[ 1.1187 ] Added Platform Config 9 data with size :- 100

[ 1.1187 ]

[ 1.1188 ] Updating mb1-bct with firmware information

[ 1.1212 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_bct_MB1.bct --recov --updatefwinfo readinfo_t234_min_prod.xml.bin

[ 1.1311 ] tegrahost_v2 --chip 0x23 0 --align mb1_bct_MB1_aligned.bct

[ 1.1337 ] Generating SHA2 Hash for mb1bct

[ 1.1427 ] Sha saved in mb1_bct_MB1_aligned.sha

[ 1.1400 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --appendsigheader mb1_bct_MB1_aligned.bct zerosbk

[ 1.1423 ] adding BCH for mb1_bct_MB1_aligned.bct

[ 1.1501 ] tegrasign_v3.py --key None --list mb1_bct_MB1_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key --sha sha512

[ 1.1506 ] Assuming zero filled SBK key

[ 1.1631 ] Warning: pub_key.key is not found

[ 1.1704 ] tegrahost_v2 --chip 0x23 0 --updatesigheader mb1_bct_MB1_aligned_sigheader.bct.encrypt mb1_bct_MB1_aligned_sigheader.bct.hash zerosbk

[ 1.1876 ] Error: Skip generating mem_bct because sdram_config is not defined

[ 1.1957 ] Error: Skip generating mem_bct because sdram_config is not defined

[ 1.1957 ] Copying signatures

[ 1.2317 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml

[ 1.3293 ] mb1_t234_prod_aligned_sigheader.bin.encrypt filename is from images_list

[ 1.3310 ] psc_bl1_t234_prod_aligned_sigheader.bin.encrypt filename is from images_list

[ 1.3310 ] Boot Rom communication

[ 1.3327 ] 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

[ 1.3360 ] BR_CID: 0x80012344705DE4422800000010FE81C0

[ 1.3755 ] Sending bct_br

[ 1.5226 ] ERROR: might be timeout in USB write.

Error: Return value 3

Command 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

Reading board information failed.

Please help.

It has been flashed successfully. Thank you.

[ 533.8132 ] Writing partition APP with system.img [ 6565001436 bytes ]
[ 533.9193 ] […] 100%
[ 1905.7770 ] tegradevflash_v2 --write BCT br_bct_BR.bct
[ 1905.7785 ] Bootloader version 01.00.0000
[ 1905.8560 ] Writing partition BCT with br_bct_BR.bct [ 8192 bytes ]
[ 1905.8564 ] […] 100%
[ 1912.5472 ] tegradevflash_v2 --write BCT-boot-chain_backup bct_backup.img
[ 1912.5485 ] Bootloader version 01.00.0000
[ 1912.6211 ] Writing partition BCT-boot-chain_backup with bct_backup.img [ 32768 bytes ]
[ 1912.6217 ] […] 100%
[ 1913.0840 ] tegradevflash_v2 --write A_MB1_BCT mb1_cold_boot_bct_MB1_sigheader.bct.encrypt
[ 1913.0858 ] Bootloader version 01.00.0000
[ 1913.1723 ] Writing partition A_MB1_BCT with mb1_cold_boot_bct_MB1_sigheader.bct.encrypt [ 17536 bytes ]
[ 1913.1732 ] […] 100%
[ 1913.4531 ] tegradevflash_v2 --write B_MB1_BCT mb1_cold_boot_bct_MB1_sigheader.bct.encrypt
[ 1913.4552 ] Bootloader version 01.00.0000
[ 1913.5333 ] Writing partition B_MB1_BCT with mb1_cold_boot_bct_MB1_sigheader.bct.encrypt [ 17536 bytes ]
[ 1913.5378 ] […] 100%
[ 1913.8180 ] tegradevflash_v2 --write A_MEM_BCT mem_coldboot_sigheader.bct.encrypt
[ 1913.8198 ] Bootloader version 01.00.0000
[ 1913.8920 ] Writing partition A_MEM_BCT with mem_coldboot_sigheader.bct.encrypt [ 243712 bytes ]
[ 1913.8932 ] […] 100%
[ 1916.9871 ] tegradevflash_v2 --write B_MEM_BCT mem_coldboot_sigheader.bct.encrypt
[ 1916.9885 ] Bootloader version 01.00.0000
[ 1917.0628 ] Writing partition B_MEM_BCT with mem_coldboot_sigheader.bct.encrypt [ 243712 bytes ]
[ 1917.0636 ] […] 100%
[ 1920.1725 ] Flashing completed

[ 1920.1728 ] Coldbooting the device
[ 1920.1743 ] tegrarcm_v2 --chip 0x23 0 --ismb2
[ 1920.1757 ] MB2 version 01.00.0000
[ 1920.2588 ] Coldbooting the device
[ 1920.2600 ] tegrarcm_v2 --chip 0x23 0 --reboot coldboot
[ 1920.2612 ] MB2 version 01.00.0000
*** The target generic has been flashed successfully. ***
Reset the board to boot from internal eMMC.

Boot from SD card then hung at:

L4TLauncher: Attempting Direct Boot
EFI stub: Booting Linux Kernel…
EFI stub: Using DTB from configuration table
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Exiting boot services…

What should I do? Please help.

I am confused after looking at the log above. Reset the board to boot from internal eMMC. However, my Jetson Orin Nano board doesn’t have any eMMC. Was the flash process applied to my SD card? How do I reset the board to boot from the recently flashed SD card?

Finally, I solved the problem with help from Dave. So, I document the process here to help the community.

Basically, make sure you have a good SD card with write speed is at least 90MB/s and a good flashing cable for fast a reliable data transfer.

  1. Format your SD card and insert into the SD card slot on the board.
  2. Put the board in “Force Recovery Mode” by connect pin 9(GND) and pin 10(FC REC).
  3. Turn on the device by plugging in the power cable.
  4. On your Ubuntu host, verify that it recognizes your Nvidia Jetson Orin Nano board. You can run the lsusb command to verify that.
vboxuser@Ulab:~$ lsusb
Bus 002 Device 002: ID 0955:7020 NVIDIA Corp. L4T (Linux for Tegra) running on Tegra

Then just run the flash.sh

sudo ./flash.sh jetson-orin-nano-devkit internal

If it failed, check and verify everything to make sure you meet all the requirements described above, then try again.

Enjoy

1 Like

@harryvu can you DM me? I’m having a similar problem here but the Nvidia guys are just ghosting me now and Nvidia support won’t RMA the device, even though it’s within warranty.

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