Failed to flash Jetson Orin Nano

Autonomous Machines Jetson & Embedded Systems Jetson Orin Nano
1

Hi,
I was about to flash Jetson Orin Nano Dev Kit board by following this tutorial:
https://docs.nvidia.com/jetson/archives/r35.3.1/DeveloperGuide/text/IN/QuickStart.html#to-flash-the-jetson-developer-kit-operating-software

My condition
Host: Ubuntu 22.04.2 LTS
Jetson: Jetson Orin Nano Dev Kit
Storage for Jetson: NVMe 512GB

These are the processes I’ve gone through:

  1. I downloaded Driver Package (BSP) and Sample Root Filesystem from here:
    Jetson Linux 35.3.1 | NVIDIA Developer

    Screenshot from 2023-08-05 00-20-29
    Screenshot from 2023-08-05 00-20-29942×379 26.6 KB

  2. I entered these commands on host’s terminal, sequentially:

tar xf Jetson_Linux_R35.3.1_aarch64.tbz2
sudo tar xpf Tegra_Linux_Sample-Root-Filesystem_R35.3.1_aarch64.tbz2a -C Linux_for_Tegra/rootfs/
cd Linux_for_Tegra
sudo ./apply_binaries.sh
sudo apt-get install qemu-user-static
sudo ./tools/l4t_flash_prerequisites.sh

  1. I connected the Jetson board to host in Force Recovery Mode. Also I checked whether they are well connected using ‘lsusb’ command. (0955:7523 NVIDIA Corp. APX)

  2. I entered these commands for flashing, sequentially:

sudo apt-get install sshpass
sudo apt-get install abootimg
sudo apt-get install libxml2-utils
sudo ./tools/kernel_flash/l4t_initrd_flash.sh -c --external-device nvme0n1p1 \ -c tools/kernel_flash/flash_l4t_external.xml -p "-c bootloader/t186ref/cfg/flash_t234_qspi.xml" \ --showlogs --network usb0 jetson-orin-nano-devkit internal

Finally I got this log:

/home/soohwanlee/Downloads/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh --no-flash -c --external-device nvme0n1p1  -c tools/kernel_flash/flash_l4t_external.xml -p -c bootloader/t186ref/cfg/flash_t234_qspi.xml  --showlogs --network usb0 jetson-orin-nano-devkit internal
************************************
*                                  *
*  Step 1: Generate flash packages *
*                                  *
************************************
Create folder to store images to flash
Generate image for internal storage devices
Generate images to be flashed
ADDITIONAL_DTB_OVERLAY=""  /home/soohwanlee/Downloads/Linux_for_Tegra/flash.sh --no-flash --sign  jetson-orin-nano-devkit internal

###############################################################################
# L4T BSP Information:
# R35 , REVISION: 3.1
# User release: 0.0
###############################################################################
copying emc_fuse_dev_params(/home/soohwanlee/Downloads/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-br-bct-diag-boot.dts)... done.
copying device_config(/home/soohwanlee/Downloads/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-mb1-bct-device-p3767-0000.dts)... done.
copying misc_config(/home/soohwanlee/Downloads/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-mb1-bct-misc-p3767-0000.dts)... done.
./tegraflash.py --chip 0x23 --applet "/home/soohwanlee/Downloads/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 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.0381 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[   0.0385 ] File rcm_state open failed
[   0.0389 ] ERROR: failed to read rcm_state
[   0.0389 ] 
[   0.0548 ] tegrasign_v3.py --key None --getmode mode.txt
[   0.0550 ] Assuming zero filled SBK key
[   0.0393 ] Pre-processing config: tegra234-mb1-bct-device-p3767-0000.dts
[   0.0779 ] Pre-processing config: tegra234-mb1-bct-misc-p3767-0000.dts
[   0.0889 ] Parsing partition layout
[   0.0897 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[   0.0926 ] Kernel DTB used: None
[   0.0926 ] WARNING: dce base dtb is not provided

[   0.0926 ] Parsing partition layout
[   0.0930 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[   0.0938 ] Creating list of images to be signed
[   0.0944 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --list images_list.xml zerosbk
[   0.0948 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin
[   0.0987 ] Header already present for mb1_t234_prod_aligned_sigheader.bin
[   0.0992 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin
[   0.1038 ] Header already present for mb1_t234_prod_aligned_sigheader.bin
[   0.1043 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin
[   0.1096 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin
[   0.1102 ] adding BCH for mb2_t234_aligned.bin
[   0.1138 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin
[   0.1275 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin
[   0.1281 ] adding BCH for mb2_t234_aligned.bin
[   0.1431 ] Filling MB1 storage info
[   0.1431 ] Parsing dev params for multi chains
[   0.1508 ] Generating br-bct
[   0.1515 ] Updating dev and MSS params in BR BCT
[   0.1515 ] tegrabct_v2 --dev_param tegra234-br-bct-diag-boot_cpp.dtb --brbct br_bct.cfg --chip 0x23 0
[   0.1555 ] Updating bl info
[   0.1560 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updateblinfo readinfo_t234_min_prod.xml.bin
[   0.1563 ] WARNING: boot chain is not completed. set to 0
[   0.1573 ] Generating signatures
[   0.1732 ] tegrasign_v3.py --key None --list images_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.1733 ] Assuming zero filled SBK key
[   0.1903 ] Warning: pub_key.key is not found
[   0.1746 ] Parsing dev params for multi chains
[   0.1746 ] Generating br-bct
[   0.1750 ] Updating dev and MSS params in BR BCT
[   0.1751 ] tegrabct_v2 --dev_param tegra234-br-bct-diag-boot_cpp.dtb --brbct br_bct.cfg --chip 0x23 0
[   0.1758 ] Updating bl info
[   0.1762 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updateblinfo readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
[   0.1766 ] WARNING: boot chain is not completed. set to 0
[   0.1778 ] Get Signed section of bct
[   0.1782 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --listbct bct_list.xml
[   0.1788 ] Signing BCT
[   0.1947 ] tegrasign_v3.py --key None --list bct_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.1948 ] Assuming zero filled SBK key
[   0.1973 ] Sha saved in br_bct_BR.sha
[   0.1976 ] Warning: pub_key.key is not found
[   0.1817 ] Updating BCT with signature
[   0.1821 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesig bct_list_signed.xml
[   0.1825 ] Offset :4608 Len :3584
[   0.1829 ] Generating SHA2 Hash
[   0.1988 ] tegrasign_v3.py --key None --list bct_list.xml --sha sha512
[   0.1990 ] Assuming zero filled SBK key
[   0.1990 ] Assuming zero filled SBK key
[   0.2010 ] Sha saved in br_bct_BR.sha
[   0.1854 ] Updating BCT with SHA2 Hash
[   0.1858 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesha bct_list_signed.xml
[   0.1861 ] Offset :4608 Len :3584
[   0.1866 ] Offset :68 Len :8124
[   0.1866 ] 
[   0.1867 ] Generating coldboot mb1-bct
[   0.1870 ] 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.1875 ] MB1-BCT version: 0.10
[   0.1878 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED5/ is not supported
[   0.1885 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED5/ is not supported
[   0.1891 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED5/ is not supported
[   0.1895 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_MCE_COVERAGE/ is not supported
[   0.1895 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_MCE_COVERAGE/ is not supported
[   0.1895 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_MCE_COVERAGE/ is not supported
[   0.1895 ] ERROR: /misc/tsc_controls/tsc_locking_config is not supported
[   0.1895 ] ERROR: /misc/tsc_controls/tsc_locking_diff_configuration is not supported
[   0.1895 ] ERROR: /misc/tsc_controls/tsc_locking_ref_frequency_configuration is not supported
[   0.1895 ] ERROR: /misc/tsc_controls/tsc_locking_control is not supported
[   0.1895 ] ERROR: /misc/tsc_controls/tsc_locking_adjust_configuration is not supported
[   0.1895 ] ERROR: /misc/tsc_controls/tsc_locking_fast_adjust_configuration is not supported
[   0.1895 ] ERROR: /misc/tsc_controls/tsc_locking_adjust_delta_control is not supported
[   0.1895 ] ERROR: /misc/tsc_controls/tsc_capture_control_ptx is not supported
[   0.1895 ] ERROR: /misc/tsc_controls/tsc_capture_config_ptx is not supported
[   0.1895 ] ERROR: /misc/tsc_controls/tsc_stscrsr is not supported
[   0.1895 ] ERROR: /misc/tsc_controls/tsc_locking_adjust_num_control is not supported
[   0.1895 ] 
[   0.1895 ] Parsing config file :tegra234-mb1-bct-device-p3767-0000_cpp.dtb 
[   0.1896 ] Added Platform Config 9 data with size :- 100
[   0.1896 ] 
[   0.1896 ] Updating mb1-bct with firmware information
[   0.1902 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_cold_boot_bct_MB1.bct --updatefwinfo readinfo_t234_min_prod.xml.bin
[   0.1917 ] tegrahost_v2 --chip 0x23 0 --align mb1_cold_boot_bct_MB1_aligned.bct
[   0.1925 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --appendsigheader mb1_cold_boot_bct_MB1_aligned.bct zerosbk
[   0.1929 ] adding BCH for mb1_cold_boot_bct_MB1_aligned.bct
[   0.2095 ] tegrasign_v3.py --key None --list mb1_cold_boot_bct_MB1_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.2097 ] Assuming zero filled SBK key
[   0.2109 ] Warning: pub_key.key is not found
[   0.1955 ] 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.1967 ] Generating recovery mb1-bct
[   0.1972 ] 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.1976 ] MB1-BCT version: 0.10
[   0.1979 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED5/ is not supported
[   0.1987 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED5/ is not supported
[   0.1993 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED5/ is not supported
[   0.1996 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_MCE_COVERAGE/ is not supported
[   0.1997 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_MCE_COVERAGE/ is not supported
[   0.1997 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_MCE_COVERAGE/ is not supported
[   0.1997 ] ERROR: /misc/tsc_controls/tsc_locking_config is not supported
[   0.1997 ] ERROR: /misc/tsc_controls/tsc_locking_diff_configuration is not supported
[   0.1997 ] ERROR: /misc/tsc_controls/tsc_locking_ref_frequency_configuration is not supported
[   0.1997 ] ERROR: /misc/tsc_controls/tsc_locking_control is not supported
[   0.1997 ] ERROR: /misc/tsc_controls/tsc_locking_adjust_configuration is not supported
[   0.1997 ] ERROR: /misc/tsc_controls/tsc_locking_fast_adjust_configuration is not supported
[   0.1997 ] ERROR: /misc/tsc_controls/tsc_locking_adjust_delta_control is not supported
[   0.1997 ] ERROR: /misc/tsc_controls/tsc_capture_control_ptx is not supported
[   0.1997 ] ERROR: /misc/tsc_controls/tsc_capture_config_ptx is not supported
[   0.1997 ] ERROR: /misc/tsc_controls/tsc_stscrsr is not supported
[   0.1997 ] ERROR: /misc/tsc_controls/tsc_locking_adjust_num_control is not supported
[   0.1998 ] 
[   0.1998 ] Parsing config file :tegra234-mb1-bct-device-p3767-0000_cpp.dtb 
[   0.1998 ] Added Platform Config 9 data with size :- 100
[   0.1998 ] 
[   0.1998 ] Updating mb1-bct with firmware information
[   0.2003 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_bct_MB1.bct --recov --updatefwinfo readinfo_t234_min_prod.xml.bin
[   0.2016 ] tegrahost_v2 --chip 0x23 0 --align mb1_bct_MB1_aligned.bct
[   0.2024 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --appendsigheader mb1_bct_MB1_aligned.bct zerosbk
[   0.2028 ] adding BCH for mb1_bct_MB1_aligned.bct
[   0.2194 ] tegrasign_v3.py --key None --list mb1_bct_MB1_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.2196 ] Assuming zero filled SBK key
[   0.2209 ] Warning: pub_key.key is not found
[   0.2055 ] tegrahost_v2 --chip 0x23 0 --updatesigheader mb1_bct_MB1_aligned_sigheader.bct.encrypt mb1_bct_MB1_aligned_sigheader.bct.hash zerosbk
[   0.2063 ] Error: Skip generating mem_bct because sdram_config is not defined
[   0.2063 ] Error: Skip generating mem_bct because sdram_config is not defined
[   0.2063 ] Copying signatures
[   0.2067 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
[   0.2117 ] mb1_t234_prod_aligned_sigheader.bin.encrypt filename is from images_list
[   0.2120 ] psc_bl1_t234_prod_aligned_sigheader.bin.encrypt filename is from images_list
[   0.2120 ] Boot Rom communication
[   0.2126 ] 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.2130 ] BR_CID: 0x80012344705DE64C8000000007FF81C0
[   0.2415 ] Sending bct_br
[   0.2848 ] Sending mb1
[   0.2854 ] Sending psc_bl1
[   0.2970 ] Sending bct_mb1
[   0.3029 ] Boot Rom communication completed
[   0.3049 ] tegrahost_v2 --chip 0x23 0 --align applet_t234_aligned.bin
[   0.3058 ] tegrahost_v2 --chip 0x23 0 --magicid MB2A --appendsigheader applet_t234_aligned.bin zerosbk
[   0.3062 ] adding BCH for applet_t234_aligned.bin
[   0.3335 ] tegrasign_v3.py --key None --list applet_t234_aligned_sigheader.bin_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.3336 ] Assuming zero filled SBK key
[   0.3354 ] Warning: pub_key.key is not found
[   0.3200 ] tegrahost_v2 --chip 0x23 0 --updatesigheader applet_t234_aligned_sigheader.bin.encrypt applet_t234_aligned_sigheader.bin.hash zerosbk
[   0.3218 ] Sending mb2_applet...

[   0.3222 ] tegrarcm_v2 --chip 0x23 0 --pollbl --download applet applet_t234_sigheader.bin.encrypt
[   0.3227 ] BL: version 0.32.0.0-t234-54845784-57325615 last_boot_error: 0
[   0.5135 ] Sending applet
[   0.6310 ] completed
[   0.6330 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[   0.6346 ] MB2 Applet version 01.00.0000
[   0.8503 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[   0.8519 ] MB2 Applet version 01.00.0000
[   0.8865 ] Retrieving board information
[   0.8889 ] tegrarcm_v2 --chip 0x23 0 --oem platformdetails chip chip_info.bin
[   0.8908 ] MB2 Applet version 01.00.0000
[   0.9363 ] Saved platform info in chip_info.bin
[   0.9420 ] Chip minor revision: 1
[   0.9422 ] Bootrom revision: 0x7
[   0.9424 ] Ram code: 0x2
[   0.9425 ] Chip sku: 0xd5
[   0.9427 ] Chip Sample: prod
[   0.9433 ] Retrieving EEPROM data
[   0.9433 ] tegrarcm_v2 --oem platformdetails eeprom cvm /home/soohwanlee/Downloads/Linux_for_Tegra/bootloader/cvm.bin --chip 0x23 0
[   0.9444 ] MB2 Applet version 01.00.0000
[   0.9777 ] Saved platform info in /home/soohwanlee/Downloads/Linux_for_Tegra/bootloader/cvm.bin
[   1.0139 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[   1.0156 ] MB2 Applet version 01.00.0000
[   1.0471 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[   1.0488 ] MB2 Applet version 01.00.0000
[   1.0977 ] Dumping customer Info
[   1.0997 ] tegrarcm_v2 --chip 0x23 0 --oem dump bct tmp.bct
[   1.1015 ] MB2 Applet version 01.00.0000
[   1.1507 ] Saved bct in tmp.bct
[   1.1615 ] tegrabct_v2 --brbct tmp.bct --chip 0x23 0 --custinfo /home/soohwanlee/Downloads/Linux_for_Tegra/bootloader/custinfo_out.bin
[   1.1631 ] Cust[   1.1647 ] omer data saved in /home/soohwanlee/Downloads/Linux_for_Tegra/bootloader/custinfo_out.bin successfully
[   1.1649 ] Rebooting to recovery mode
[   1.1667 ] tegrarcm_v2 --chip 0x23 0 --ismb2
[   1.2047 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[   1.2061 ] MB2 Applet version 01.00.0000
[   1.2578 ] Booting to recovery mode
[   1.2597 ] tegrarcm_v2 --chip 0x23 0 --reboot recovery
[   1.2613 ] MB2 Applet version 01.00.0000
Board ID(3767) version(300) sku(0005) revision(K.2)
Chip SKU(00:00:00:D5) ramcode(00:00:00:02) fuselevel(fuselevel_production) board_FAB(300)
emc_opt_disable_fuse:(0)
Copy /home/soohwanlee/Downloads/Linux_for_Tegra/kernel/dtb/tegra234-p3767-0003-p3768-0000-a0.dtb to /home/soohwanlee/Downloads/Linux_for_Tegra/kernel/dtb/tegra234-p3767-0003-p3768-0000-a0.dtb.rec
Generated UUID 3c4262c7-6f6f-47ee-9887-9c7aa5956a61 for mounting root APP partition.
copying bctfile(/home/soohwanlee/Downloads/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-p3767-0001-sdram-l4t.dts)... done.
copying minratchet_config(/home/soohwanlee/Downloads/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-mb1-bct-ratchet-p3767-0000.dts)... done.
copying device_config(/home/soohwanlee/Downloads/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-mb1-bct-device-p3767-0000.dts)... done.
copying misc_config(/home/soohwanlee/Downloads/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-mb1-bct-misc-p3767-0000.dts)... done.
copying pinmux_config(/home/soohwanlee/Downloads/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-mb1-bct-pinmux-p3767-dp-a03.dtsi)... done.
copying gpioint_config(/home/soohwanlee/Downloads/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-mb1-bct-gpioint-p3767-0000.dts)... done.
copying pmic_config(/home/soohwanlee/Downloads/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-mb1-bct-pmic-p3767-0000-a02.dts)... done.
copying pmc_config(/home/soohwanlee/Downloads/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-mb1-bct-padvoltage-p3767-dp-a03.dtsi)... done.
copying deviceprod_config(/home/soohwanlee/Downloads/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-mb1-bct-cprod-p3767-0000.dts)... done.
copying prod_config(/home/soohwanlee/Downloads/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-mb1-bct-prod-p3767-0000.dts)... done.
copying scr_config(/home/soohwanlee/Downloads/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-mb2-bct-scr-p3767-0000.dts)... done.
copying wb0sdram(/home/soohwanlee/Downloads/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-p3767-0001-wb0sdram-l4t.dts)... done.
copying bootrom_config(/home/soohwanlee/Downloads/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-mb1-bct-reset-p3767-0000.dts)... done.
Existing uphylane_config(/home/soohwanlee/Downloads/Linux_for_Tegra/bootloader/tegra234-mb1-bct-uphylane-si.dtsi) reused.
copying dev_params(/home/soohwanlee/Downloads/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-br-bct-p3767-0000-l4t.dts)... done.
copying dev_params_b(/home/soohwanlee/Downloads/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-br-bct_b-p3767-0000-l4t.dts)... done.
copying mb2bct_cfg(/home/soohwanlee/Downloads/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-mb2-bct-misc-p3767-0000.dts)... done.
Existing pscfwfile(/home/soohwanlee/Downloads/Linux_for_Tegra/bootloader/pscfw_t234_prod.bin) reused.
Existing pscbl1file(/home/soohwanlee/Downloads/Linux_for_Tegra/bootloader/psc_bl1_t234_prod.bin) reused.
Existing mtsmcefile(/home/soohwanlee/Downloads/Linux_for_Tegra/bootloader/mce_flash_o10_cr_prod.bin) reused.
Existing mb2applet(/home/soohwanlee/Downloads/Linux_for_Tegra/bootloader/applet_t234.bin) reused.
Existing bootloader(/home/soohwanlee/Downloads/Linux_for_Tegra/bootloader/mb2_t234.bin) reused.
copying initrd(/home/soohwanlee/Downloads/Linux_for_Tegra/bootloader/l4t_initrd.img)... done.
bl is uefi
Making Boot image... done.
Not signing of boot.img
Making recovery ramdisk for recovery image...
Re-generating recovery ramdisk for recovery image...
/home/soohwanlee/Downloads/Linux_for_Tegra/bootloader/ramdisk_tmp /home/soohwanlee/Downloads/Linux_for_Tegra/bootloader /home/soohwanlee/Downloads/Linux_for_Tegra
39726 blocks

gzip: /home/soohwanlee/Downloads/Linux_for_Tegra/kernel/Image: not in gzip format
/home/soohwanlee/Downloads/Linux_for_Tegra/tools/ota_tools/version_upgrade/ota_make_recovery_img_dtb.sh: line 177: strings: command not found
ERROR: failed to get kernel version from /home/soohwanlee/Downloads/Linux_for_Tegra/kernel/Image
Error: failed to generate images
Cleaning up...

What’s wrong with my procedure??? I couldn’t figure out what the reason of this failure is.
It would be great if you give me any comment or idea.

2

On command line it is possible for an Ubuntu 22 host to work, at least with the regular flash.sh script. None of the Jetsons can use the JetPack GUI front end for flash via an Ubuntu 22 host PC. You’d want Ubuntu 20 for that. I do not know if the other scripts, such as the initrd scripts will work on command line with 22 or not.

Definitely though, VMs cause a lot of problems, and I see the APX in lsusb. VMs are not supported. The reason for failure tends to be that a VM needs to not only see the Jetson at the start of boot, but also needs to see the Jetson every time USB disconnects and reconnects. Unless you have some expertise, or otherwise get lucky, your VM configuration won’t default to this, and flash will fail. The software running from within the VM has no ability to change this, and each VM has different setup, so you’d have to ask the VM support how to do this. Otherwise, a native Ubuntu 20 host PC would be best.

3

Is that the answer for flash orin nano failed? I’m ubuntu22.04 failed on latest line:

sudo ./flash.sh -k A_spe-fw jetson-orin-nano-devkit mmcblk0p1

stuck at :
[ 7.8171 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet

image
image1866×2133 450 KB

4

You should probably start a new thread. It is possible that the error you see is different and related to trying to flash only a particular partition. I would expect an Ubuntu 22 host PC to work for command line flash, although it isn’t technically supported (and in fact a lot of non-Ubuntu Linux host PCs will work on command line if base requirements are met, e.g., correct manual install of the driver package and sample rootfs).

When you post a new thread try to show:

  • What was the original flash (making sure partitions and versions are correct and matching the new flash).
  • Provide a command line log. Example:
    sudo ./flash.sh -k A_spe-fw jetson-orin-nano-devkit mmcblk0p1 2>&1 | tee log_flash_spefw.txt

Technically, it would not hurt to also run a serial console to the Jetson itself during the flash, and save a log of what goes on during flash.

5

log_flash_spefw.txt (68.9 KB)
@linuxdev Please help me to check why I can not flash the orin nao spe fw. first time to get spe to work, Thanks!

6

You should probably start a new thread in the forum, I think the cause of the issue is not the same as the original post. Include the exact model (such as being a dev kit, or if it is a separate eMMC module in combination with a third party carrier board), the L4T release which is currently on the Orin Nano (e.g., via “head -n 1 /etc/nv_tegra_release”), and the exact command (you gave that here, but in a new forum thread you would need to add that back in).

I cannot test anything I might suggest as I do not have an Orin Nano. All I can do is give you some background which might not be particularly useful. Regardless, if this is a dev kit without eMMC, then the content goes to the QSPI memory on the module itself; if this is an eMMC model, then that content goes to an actual eMMC partition. The two will likely differ in how they work during a flash. Additionally, if there is already content there, and the size of the new content is too large, then I would expect it to fail without flashing everything (for an SD card model, I mean QSPI; for an eMMC model, I mean the eMMC). This latter is due to rearranging partitions being a requirement when one of the middle partitions grows too large.

One reason why some of the content might grow is if you’ve compiled some of this yourself, and the binary content has not been stripped of debug symbols. There is also the obvious addition of new content causing an increased size. If you know the size of the original binary file used to flash the partition, and you know the exact size of the new partition, then you can compare sizes. If the target is eMMC, then you’ll be able to also tell what the current partition size is, but I’m not sure if there is a way to do this with the QSPI content.

In the case of eMMC models, you might also try the command with “--no-flash” and “--sign”. For eMMC models (maybe SD card models, but not particular use?) any content must first be signed before going into a partition. So it is the signed size which matters. By not flashing and telling it to sign you can leave the signed version of the binary partition available for examination (generated based on the content you had in place at the time of signing). On eMMC models all partitions (except rootfs/APP) are signed, or they won’t boot. The default is to sign with a NULL key, but if security fuses are burned (which SD card models do not have), then only the exact private key can be used to sign and install (or at least boot would reject the key if not correct, even if it is a NULL key which is correct).

7

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