Jetson AGX orin not flashing

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Orin
1

When i tried to flash the Jetson AGX orin i got the error

###############################################################################
# L4T BSP Information:
# R36 , REVISION: 4.0
# User release: 0.0
###############################################################################
ECID is 0x80012344705DE6C82C00000002FE00C0
# Target Board Information:
# Name: jetson-agx-orin-devkit, Board Family: generic, SoC: Tegra 234, 
# OpMode: production, Boot Authentication: NS, 
# Disk encryption: disabled ,
###############################################################################
copying device_config(/home/richu/Documents/csli/csli_mseovs/jetson_linux/Linux_for_Tegra/bootloader/generic/BCT/tegra234-mb1-bct-device-p3701-0000.dts)... done.
copying misc_config(/home/richu/Documents/csli/csli_mseovs/jetson_linux/Linux_for_Tegra/bootloader/generic/BCT/tegra234-mb1-bct-misc-p3701-0000.dts)... done.
copying emc_fuse_dev_params(/home/richu/Documents/csli/csli_mseovs/jetson_linux/Linux_for_Tegra/bootloader/generic/BCT/tegra234-br-bct-diag-boot.dts)... done.
Existing emcfuse(/home/richu/Documents/csli/csli_mseovs/jetson_linux/Linux_for_Tegra/bootloader/fuse_t234.xml) reused.
./tegraflash.py --chip "0x23" --applet "/home/richu/Documents/csli/csli_mseovs/jetson_linux/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-p3701-0000.dts --misc_config tegra234-mb1-bct-misc-p3701-0000.dts --bins "mb2_applet applet_t234.bin" --cmd "readfuses fuse_t234.bin fuse_t234.xml; 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.0295 ] Reading fuses
[   0.0305 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[   0.0313 ] File rcm_state open failed
[   0.0321 ] ERROR: failed to read rcm_state
[   0.0321 ] 
[   0.0337 ] tegrasign_v3.py --key None --getmode mode.txt
[   0.0342 ] Assuming zero filled SBK key
[   0.0331 ] Pre-processing config: tegra234-mb1-bct-device-p3701-0000.dts
[   0.0491 ] Pre-processing config: tegra234-mb1-bct-misc-p3701-0000.dts
[   0.0780 ] Parsing partition layout
[   0.0792 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[   0.0824 ] Kernel DTB used: None
[   0.0824 ] WARNING: dce base dtb is not provided

[   0.0824 ] Parsing partition layout
[   0.0838 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[   0.0859 ] Creating list of images to be signed
[   0.0872 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --list images_list.xml zerosbk
[   0.0882 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin
[   0.0912 ] Header already present for mb1_t234_prod_aligned_sigheader.bin
[   0.0920 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin
[   0.1014 ] Header already present for mb1_t234_prod_aligned_sigheader.bin
[   0.1023 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin
[   0.1100 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin
[   0.1104 ] adding BCH for mb2_t234_aligned.bin
[   0.1153 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin
[   0.1384 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin
[   0.1394 ] adding BCH for mb2_t234_aligned.bin
[   0.1653 ] Filling MB1 storage info
[   0.1654 ] Parsing dev params for multi chains
[   0.1824 ] Generating br-bct
[   0.1840 ] Updating dev and MSS params in BR BCT
[   0.1840 ] tegrabct_v2 --dev_param tegra234-br-bct-diag-boot_cpp.dtb --brbct br_bct.cfg --chip 0x23 0
[   0.1862 ] Updating bl info
[   0.1877 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updateblinfo readinfo_t234_min_prod.xml.bin
[   0.1887 ] WARNING: boot chain is not completed. set to 0
[   0.1904 ] Generating signatures
[   0.1920 ] tegrasign_v3.py --key None --list images_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.1925 ] Assuming zero filled SBK key
[   0.2247 ] Warning: pub_key.key is not found
[   0.2238 ] Parsing dev params for multi chains
[   0.2239 ] Generating br-bct
[   0.2253 ] Updating dev and MSS params in BR BCT
[   0.2254 ] tegrabct_v2 --dev_param tegra234-br-bct-diag-boot_cpp.dtb --brbct br_bct.cfg --chip 0x23 0
[   0.2277 ] Updating bl info
[   0.2291 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updateblinfo readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
[   0.2304 ] WARNING: boot chain is not completed. set to 0
[   0.2337 ] Generating SHA2 Hash
[   0.2383 ] Sha saved in br_bct_BR.sha
[   0.2371 ] Get Signed section of bct
[   0.2385 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --listbct bct_list.xml
[   0.2407 ] Signing BCT
[   0.2423 ] tegrasign_v3.py --key None --list bct_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.2428 ] Assuming zero filled SBK key
[   0.2491 ] Sha saved in br_bct_BR.sha
[   0.2499 ] Warning: pub_key.key is not found
[   0.2484 ] Updating BCT with signature
[   0.2495 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesig bct_list_signed.xml
[   0.2506 ] Offset :4608 Len :3584
[   0.2521 ] Generating SHA2 Hash
[   0.2537 ] tegrasign_v3.py --key None --list bct_list.xml --sha sha512
[   0.2542 ] Assuming zero filled SBK key
[   0.2542 ] Assuming zero filled SBK key
[   0.2609 ] Sha saved in br_bct_BR.sha
[   0.2602 ] Updating BCT with SHA2 Hash
[   0.2615 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesha bct_list_signed.xml
[   0.2624 ] Offset :4608 Len :3584
[   0.2636 ] Offset :68 Len :8124
[   0.2641 ] Generating coldboot mb1-bct
[   0.2652 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_cold_boot_bct.cfg --misc tegra234-mb1-bct-misc-p3701-0000_cpp.dtb --device tegra234-mb1-bct-device-p3701-0000_cpp.dtb
[   0.2662 ] MB1-BCT version: 0.13

[   0.2714 ] Parsing config file :tegra234-mb1-bct-device-p3701-0000_cpp.dtb 
[   0.2723 ] Added Platform Config 9 data with size :- 100
[   0.2723 ] 
[   0.2724 ] Updating mb1-bct with firmware information
[   0.2737 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_cold_boot_bct_MB1.bct --updatefwinfo readinfo_t234_min_prod.xml.bin
[   0.2774 ] tegrahost_v2 --chip 0x23 0 --align mb1_cold_boot_bct_MB1_aligned.bct
[   0.2787 ] Generating SHA2 Hash for mb1bct
[   0.2829 ] Sha saved in mb1_cold_boot_bct_MB1_aligned.sha
[   0.2860 ] Sha saved in mb1_cold_boot_bct_MB1.sha
[   0.2859 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --appendsigheader mb1_cold_boot_bct_MB1_aligned.bct zerosbk
[   0.2870 ] adding BCH for mb1_cold_boot_bct_MB1_aligned.bct
[   0.2912 ] tegrasign_v3.py --key None --list mb1_cold_boot_bct_MB1_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.2917 ] Assuming zero filled SBK key
[   0.2962 ] Warning: pub_key.key is not found
[   0.2972 ] 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.3023 ] Generating recovery mb1-bct
[   0.3044 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_bct.cfg --misc tegra234-mb1-bct-misc-p3701-0000_cpp.dtb --device tegra234-mb1-bct-device-p3701-0000_cpp.dtb
[   0.3057 ] MB1-BCT version: 0.13

[   0.3126 ] Parsing config file :tegra234-mb1-bct-device-p3701-0000_cpp.dtb 
[   0.3130 ] Added Platform Config 9 data with size :- 100
[   0.3135 ] Updating mb1-bct with firmware information
[   0.3145 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_bct_MB1.bct --recov --updatefwinfo readinfo_t234_min_prod.xml.bin
[   0.3188 ] tegrahost_v2 --chip 0x23 0 --align mb1_bct_MB1_aligned.bct
[   0.3208 ] Generating SHA2 Hash for mb1bct
[   0.3247 ] Sha saved in mb1_bct_MB1_aligned.sha
[   0.3266 ] Sha saved in mb1_bct_MB1.sha
[   0.3266 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --appendsigheader mb1_bct_MB1_aligned.bct zerosbk
[   0.3273 ] adding BCH for mb1_bct_MB1_aligned.bct
[   0.3324 ] tegrasign_v3.py --key None --list mb1_bct_MB1_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.3331 ] Assuming zero filled SBK key
[   0.3384 ] Warning: pub_key.key is not found
[   0.3396 ] tegrahost_v2 --chip 0x23 0 --updatesigheader mb1_bct_MB1_aligned_sigheader.bct.encrypt mb1_bct_MB1_aligned_sigheader.bct.hash zerosbk
[   0.3429 ] Info: Skip generating mem_bct because sdram_config is not defined
[   0.3432 ] Info: Skip generating mem_bct because sdram_config is not defined
[   0.3434 ] Copying signatures
[   0.3449 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
[   0.3627 ] mb1_t234_prod_aligned_sigheader.bin.encrypt filename is from images_list
[   0.3631 ] psc_bl1_t234_prod_aligned_sigheader.bin.encrypt filename is from images_list
[   0.3631 ] Boot Rom communication
[   0.3642 ] 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.3650 ] BR_CID: 0x80012344705DE6C82C00000002FE00C0
[   0.4295 ] Sending bct_br
[   0.5982 ] 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
[  11.0010 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[  11.0031 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[  11.0054 ] Retrieving board information
[  11.0063 ] tegrarcm_v2 --chip 0x23 0 --oem platformdetails chip chip_info.bin
[  11.0078 ] Retrieving EEPROM data
[  11.0079 ] tegrarcm_v2 --oem platformdetails eeprom cvm /home/richu/Documents/csli/csli_mseovs/jetson_linux/Linux_for_Tegra/bootloader/cvm.bin --chip 0x23 0
[  11.0099 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[  11.0118 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[  11.0130 ] Dumping customer Info
[  11.0137 ] tegrarcm_v2 --chip 0x23 0 --oem dump bct tmp.bct
[  11.0161 ] tegrabct_v2 --brbct tmp.bct --chip 0x23 0 --custinfo /home/richu/Documents/csli/csli_mseovs/jetson_linux/Linux_for_Tegra/bootloader/custinfo_out.bin
[  11.0172 ] File tmp.bct open failed
[  11.0177 ] Error: try getting custinfo fail. Moving on
[  11.0177 ] Rebooting to recovery mode
[  11.0184 ] tegrarcm_v2 --chip 0x23 0 --ismb2
[  11.0195 ] Rebooting to recovery mode
[  11.0202 ] tegrarcm_v2 --chip 0x23 0 --reboot recovery
Parsing board information failed.
2

*** Please note that this reply is generated by LLM automatically ***

The error message you’re encountering during the flashing process of the Jetson AGX Orin suggests several potential issues. To address this comprehensively, let’s break down the key points and possible solutions:

  1. Timeout in USB Write: The error message “ERROR: might be timeout in USB write. Error: Return value 3” indicates a communication issue between your host machine and the Jetson module via USB. This could be due to a faulty USB connection, a problem with the USB port, or issues with the USB cable.

    • Solution: Ensure that the USB connection is stable and try using a different USB port or cable. Also, verify that the Jetson module is properly powered and recognized by your host machine.

  2. Failed to Read rcm_state: The message “File rcm_state open failed” followed by “ERROR: failed to read rcm_state” suggests that there’s an issue with accessing or reading the state of the recovery mode.

    • Solution: This could be related to the permissions or the path to the rcm_state file. Ensure that the file exists and is accessible. If you’re using a script to flash the device, check the script’s permissions and the path specified for rcm_state.

  3. Warning: pub_key.key is not found: This warning indicates that the pub_key.key file, which is necessary for signing the boot loader and other components, is missing.

    • Solution: Locate the pub_key.key file and ensure it’s in the correct directory as specified in your flashing script or commands. If you’re using a default flashing process, this file should be part of the JetPack or SDK you’re using. If it’s missing, you might need to regenerate it or obtain it from NVIDIA’s documentation or support resources.

  4. Parsing board information failed: This error at the end suggests that there was a failure in parsing the board information, which is crucial for the flashing process.

    • Solution: This could be due to a variety of reasons including incorrect configuration files, issues with the tegrarcm_v2 tool, or problems with the board’s EEPROM data. Ensure that your configuration files (like readinfo_t234_min_prod.xml) are correct and not corrupted. Also, verify that the EEPROM data is correctly retrieved and processed.

Given these points, the flashing process seems to encounter multiple issues, ranging from communication timeouts to missing files and parsing errors. To resolve these, ensure that:

  • Your USB connection is stable.
  • All necessary files (like pub_key.key) are present and accessible.
  • Configuration files are correct and not corrupted.
  • You’re using the latest version of the flashing tools and scripts.

If you continue to encounter issues, it might be helpful to consult NVIDIA’s official documentation and support forums for more specific guidance tailored to your Jetson AGX Orin module and the version of the JetPack or SDK you’re using.

4

Hi,

Please try below commands and flash again.

sudo -s
echo -1 > /sys/module/usbcore/parameters/autosuspend

Thanks