Error when trying to flash Jetson Orin NX. We tried every possible thing and still nothing. Why?

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin NX
, , , , , ,
1

Hey, My boss bought a ES-JNX42 Orin Nano™ or Orin NX™ embedded system from auvidea with JNX42-LM carrier board with Jetson Orin NX 16 GB compute module and it has a M.2 NVME 128 GB SSD built into it.
We followed Auvidea guide on flashing the product here’s the link:

After that when we tried to flash it with the command that they provided we got the error that it can’t find board id: p3509-a02+p3767-0000
Turns out we need Auvidea firmware to use this command which they dont say in the guide. The firmware has a lot of kernel files which i think is necessary. So we downloaded the firmware from the site copied the content to the linux_for_tegra folder now we got the p3509-a02+p3767-0000.conf files etc then we tried again no luck.

This guide is provided in the firmware files from the auvidea site.

  1. prepare the sdk
    ONLY NEEDED IF NO ORIN WAS FLASHED BEFORE
    -start the sdkmanager
    -select the Jetson AGX Orin modules as target Hardware
    -select Jetpack 5.1.3 as target operating system
    -start the installation until the sdk asks you for either use automatic or manual setup
    → at this point you can choose to “skip” the rest of the installation and continue with step 2 of this instructions

  2. copy the contents of the kernel_out folder in the auvidea packet to the nvida_sdk folder
    → cp ~/kernel_out/* /home/USER/nvidia/nvidia_sdk/JetPack_5.1.3_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra

  3. switch in the Orin folder and apply binaries
    → cd /home/USER/nvidia/nvidia_sdk/JetPack_5.1.3_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra
    → sudo ./apply_binaries.sh

  4. enter the Jetpack Linux_for_Tegra folder and flash the Jetson
    → cd /home/USER/nvidia/nvidia_sdk/JetPack_5.1.3_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra/
    for target carrier JNX42
    → sudo ./flash_orin_nx_auvidea_JNX42.sh
    for target carrier JNX45
    → sudo ./flash_orin_nx_auvidea_JNX45.sh
    for target carrier JNX46
    → sudo ./flash_orin_nx_auvidea_JNX46.sh
    for target carrier JNX82
    → sudo ./flash_orin_nx_auvidea_JNX82.sh

We followed everything and then tried to flash. Heres the full log:

epadmin@epadmin-ESPRIMO-P400:~/nvidia/nvidia_sdk/JetPack_5.1.3_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra$ sudo ./flash_orin_nx_auvidea_JNX42.sh
[sudo] password for epadmin: 
Sorry, try again.
[sudo] password for epadmin: 
/home/epadmin/nvidia/nvidia_sdk/JetPack_5.1.3_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh --no-flash --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p -c bootloader/t186ref/cfg/flash_t234_qspi.xml --showlogs --network usb0 orin_nx_JNX42 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/epadmin/nvidia/nvidia_sdk/JetPack_5.1.3_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra/flash.sh --no-flash --sign  -c bootloader/t186ref/cfg/flash_t234_qspi.xml orin_nx_JNX42 internal

###############################################################################
# L4T BSP Information:
# R35 , REVISION: 5.0
# User release: 0.0
###############################################################################
ECID is 0x80012344705DD80B1400000007028080
copying emc_fuse_dev_params(/home/epadmin/nvidia/nvidia_sdk/JetPack_5.1.3_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-br-bct-diag-boot.dts)... done.
copying device_config(/home/epadmin/nvidia/nvidia_sdk/JetPack_5.1.3_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-mb1-bct-device-p3767-0000.dts)... done.
copying misc_config(/home/epadmin/nvidia/nvidia_sdk/JetPack_5.1.3_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-mb1-bct-misc-p3767-0000.dts)... done.
./tegraflash.py --chip 0x23 --applet "/home/epadmin/nvidia/nvidia_sdk/JetPack_5.1.3_Linux_JETSON_ORIN_NX_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 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.0752 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[   0.0768 ] File rcm_state open failed
[   0.0776 ] ERROR: failed to read rcm_state
[   0.0776 ] 
[   0.1016 ] tegrasign_v3.py --key None --getmode mode.txt
[   0.1021 ] Assuming zero filled SBK key
[   0.0787 ] Pre-processing config: tegra234-mb1-bct-device-p3767-0000.dts
[   0.5564 ] Pre-processing config: tegra234-mb1-bct-misc-p3767-0000.dts
[   0.6092 ] Parsing partition layout
[   0.6237 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[   0.6349 ] Kernel DTB used: None
[   0.6349 ] WARNING: dce base dtb is not provided

[   0.6349 ] Parsing partition layout
[   0.6368 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[   0.6391 ] Creating list of images to be signed
[   0.6574 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --list images_list.xml zerosbk
[   0.6592 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin
[   0.6803 ] Header already present for mb1_t234_prod_aligned_sigheader.bin
[   0.6811 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin
[   0.6932 ] Header already present for mb1_t234_prod_aligned_sigheader.bin
[   0.6954 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin
[   0.7061 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin
[   0.7066 ] adding BCH for mb2_t234_aligned.bin
[   0.7410 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin
[   0.7609 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin
[   0.7615 ] adding BCH for mb2_t234_aligned.bin
[   0.7799 ] Filling MB1 storage info
[   0.7799 ] Parsing dev params for multi chains
[   0.7879 ] Generating br-bct
[   0.8189 ] Updating dev and MSS params in BR BCT
[   0.8190 ] tegrabct_v2 --dev_param tegra234-br-bct-diag-boot_cpp.dtb --brbct br_bct.cfg --chip 0x23 0
[   0.8292 ] Updating bl info
[   0.8315 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updateblinfo readinfo_t234_min_prod.xml.bin
[   0.8335 ] WARNING: boot chain is not completed. set to 0
[   0.8351 ] Generating signatures
[   0.8590 ] tegrasign_v3.py --key None --list images_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.8596 ] Assuming zero filled SBK key
[   0.9303 ] Warning: pub_key.key is not found
[   0.9068 ] Parsing dev params for multi chains
[   0.9068 ] Generating br-bct
[   0.9082 ] Updating dev and MSS params in BR BCT
[   0.9083 ] tegrabct_v2 --dev_param tegra234-br-bct-diag-boot_cpp.dtb --brbct br_bct.cfg --chip 0x23 0
[   0.9100 ] Updating bl info
[   0.9113 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updateblinfo readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
[   0.9124 ] WARNING: boot chain is not completed. set to 0
[   0.9147 ] Get Signed section of bct
[   0.9160 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --listbct bct_list.xml
[   0.9175 ] Signing BCT
[   0.9414 ] tegrasign_v3.py --key None --list bct_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.9417 ] Assuming zero filled SBK key
[   0.9467 ] Sha saved in br_bct_BR.sha
[   0.9473 ] Warning: pub_key.key is not found
[   0.9235 ] Updating BCT with signature
[   0.9253 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesig bct_list_signed.xml
[   0.9268 ] Offset :4608 Len :3584
[   0.9274 ] Generating SHA2 Hash
[   0.9513 ] tegrasign_v3.py --key None --list bct_list.xml --sha sha512
[   0.9517 ] Assuming zero filled SBK key
[   0.9517 ] Assuming zero filled SBK key
[   0.9566 ] Sha saved in br_bct_BR.sha
[   0.9332 ] Updating BCT with SHA2 Hash
[   0.9345 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesha bct_list_signed.xml
[   0.9357 ] Offset :4608 Len :3584
[   0.9363 ] Offset :68 Len :8124
[   0.9363 ] 
[   0.9364 ] Generating coldboot mb1-bct
[   0.9376 ] 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.9388 ] MB1-BCT version: 0.12
[   0.9391 ] ERROR: /misc/enable_dram_page_blacklisting is not supported
[   0.9397 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED1/ is not supported
[   0.9404 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED1/ is not supported
[   0.9411 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED1/ is not supported
[   0.9417 ] ERROR: /misc/tsc_controls/tsc_locking_config is not supported
[   0.9422 ] ERROR: /misc/tsc_controls/tsc_locking_diff_configuration is not supported
[   0.9422 ] ERROR: /misc/tsc_controls/tsc_locking_ref_frequency_configuration is not supported
[   0.9422 ] ERROR: /misc/tsc_controls/tsc_locking_control is not supported
[   0.9422 ] ERROR: /misc/tsc_controls/tsc_locking_adjust_configuration is not supported
[   0.9422 ] ERROR: /misc/tsc_controls/tsc_locking_fast_adjust_configuration is not supported
[   0.9422 ] ERROR: /misc/tsc_controls/tsc_locking_adjust_delta_control is not supported
[   0.9422 ] ERROR: /misc/tsc_controls/tsc_capture_control_ptx is not supported
[   0.9422 ] ERROR: /misc/tsc_controls/tsc_capture_config_ptx is not supported
[   0.9422 ] ERROR: /misc/tsc_controls/tsc_stscrsr is not supported
[   0.9422 ] ERROR: /misc/tsc_controls/tsc_locking_adjust_num_control is not supported
[   0.9422 ] 
[   0.9422 ] Parsing config file :tegra234-mb1-bct-device-p3767-0000_cpp.dtb 
[   0.9422 ] Added Platform Config 9 data with size :- 100
[   0.9422 ] 
[   0.9423 ] Updating mb1-bct with firmware information
[   0.9436 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_cold_boot_bct_MB1.bct --updatefwinfo readinfo_t234_min_prod.xml.bin
[   0.9463 ] tegrahost_v2 --chip 0x23 0 --align mb1_cold_boot_bct_MB1_aligned.bct
[   0.9476 ] Generating SHA2 Hash for mb1bct
[   0.9735 ] Sha saved in mb1_cold_boot_bct_MB1_aligned.sha
[   0.9756 ] Sha saved in mb1_cold_boot_bct_MB1.sha
[   0.9530 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --appendsigheader mb1_cold_boot_bct_MB1_aligned.bct zerosbk
[   0.9541 ] adding BCH for mb1_cold_boot_bct_MB1_aligned.bct
[   0.9798 ] tegrasign_v3.py --key None --list mb1_cold_boot_bct_MB1_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.9803 ] Assuming zero filled SBK key
[   0.9832 ] Warning: pub_key.key is not found
[   0.9610 ] 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.9636 ] Generating recovery mb1-bct
[   0.9650 ] 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.9663 ] MB1-BCT version: 0.12
[   0.9666 ] ERROR: /misc/enable_dram_page_blacklisting is not supported
[   0.9672 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED1/ is not supported
[   0.9678 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED1/ is not supported
[   0.9684 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED1/ is not supported
[   0.9690 ] ERROR: /misc/tsc_controls/tsc_locking_config is not supported
[   0.9695 ] ERROR: /misc/tsc_controls/tsc_locking_diff_configuration is not supported
[   0.9701 ] ERROR: /misc/tsc_controls/tsc_locking_ref_frequency_configuration is not supported
[   0.9708 ] ERROR: /misc/tsc_controls/tsc_locking_control is not supported
[   0.9708 ] ERROR: /misc/tsc_controls/tsc_locking_adjust_configuration is not supported
[   0.9708 ] ERROR: /misc/tsc_controls/tsc_locking_fast_adjust_configuration is not supported
[   0.9708 ] ERROR: /misc/tsc_controls/tsc_locking_adjust_delta_control is not supported
[   0.9708 ] ERROR: /misc/tsc_controls/tsc_capture_control_ptx is not supported
[   0.9708 ] ERROR: /misc/tsc_controls/tsc_capture_config_ptx is not supported
[   0.9708 ] ERROR: /misc/tsc_controls/tsc_stscrsr is not supported
[   0.9709 ] ERROR: /misc/tsc_controls/tsc_locking_adjust_num_control is not supported
[   0.9709 ] 
[   0.9709 ] Parsing config file :tegra234-mb1-bct-device-p3767-0000_cpp.dtb 
[   0.9709 ] Added Platform Config 9 data with size :- 100
[   0.9709 ] 
[   0.9709 ] Updating mb1-bct with firmware information
[   0.9724 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_bct_MB1.bct --recov --updatefwinfo readinfo_t234_min_prod.xml.bin
[   0.9764 ] tegrahost_v2 --chip 0x23 0 --align mb1_bct_MB1_aligned.bct
[   0.9778 ] Generating SHA2 Hash for mb1bct
[   1.0039 ] Sha saved in mb1_bct_MB1_aligned.sha
[   1.0063 ] Sha saved in mb1_bct_MB1.sha
[   0.9841 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --appendsigheader mb1_bct_MB1_aligned.bct zerosbk
[   0.9854 ] adding BCH for mb1_bct_MB1_aligned.bct
[   1.0106 ] tegrasign_v3.py --key None --list mb1_bct_MB1_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[   1.0108 ] Assuming zero filled SBK key
[   1.0137 ] Warning: pub_key.key is not found
[   0.9913 ] tegrahost_v2 --chip 0x23 0 --updatesigheader mb1_bct_MB1_aligned_sigheader.bct.encrypt mb1_bct_MB1_aligned_sigheader.bct.hash zerosbk
[   0.9935 ] Error: Skip generating mem_bct because sdram_config is not defined
[   0.9935 ] Error: Skip generating mem_bct because sdram_config is not defined
[   0.9935 ] Copying signatures
[   0.9947 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
[   1.0056 ] Boot Rom communication
[   1.0070 ] 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.0084 ] BR_CID: 0x80012344705DD80B1400000007028080
[   1.0099 ] Sending bct_br
[   1.0101 ] Sending mb1
[   1.0105 ] Sending psc_bl1
[   1.0215 ] Sending bct_mb1
[   1.0274 ] Boot Rom communication completed
[   1.0553 ] tegrahost_v2 --chip 0x23 0 --align applet_t234_aligned.bin
[   1.0591 ] tegrahost_v2 --chip 0x23 0 --magicid MB2A --appendsigheader applet_t234_aligned.bin zerosbk
[   1.0608 ] adding BCH for applet_t234_aligned.bin
[   1.0992 ] tegrasign_v3.py --key None --list applet_t234_aligned_sigheader.bin_list.xml --pubkeyhash pub_key.key --sha sha512
[   1.0996 ] Assuming zero filled SBK key
[   1.1044 ] Warning: pub_key.key is not found
[   1.0823 ] tegrahost_v2 --chip 0x23 0 --updatesigheader applet_t234_aligned_sigheader.bin.encrypt applet_t234_aligned_sigheader.bin.hash zerosbk
[   1.0853 ] Sending mb2_applet...

[   1.0865 ] tegrarcm_v2 --chip 0x23 0 --pollbl --download applet applet_t234_sigheader.bin.encrypt
[   1.0878 ] BL: version 1.4.0.1-t234-54845784-08e631ca last_boot_error: 0
[   1.2328 ] Sending applet
[   1.2331 ] ERROR: might be timeout in USB write.
Error: Return value 3
Command tegrarcm_v2 --chip 0x23 0 --pollbl --download applet applet_t234_sigheader.bin.encrypt
Reading board information failed.
Error: /home/epadmin/nvidia/nvidia_sdk/JetPack_5.1.3_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra/bootloader/signed/flash.idx is not found
Error: failed to relocate images to /home/epadmin/nvidia/nvidia_sdk/JetPack_5.1.3_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra/tools/kernel_flash/images
Cleaning up...

This was tried on Ubuntu 18.04.6 but we tried on 20.4.6 and it did not work. The error i wrote here is on ubuntu 18.04.6 its different then the errors we got on ubuntu 20.4.6 but its kinda similar also its either usb timeout or failed to read rcm_state stuff like that. I can send you the full log on Ubuntu 20.4.6 if you want but i dont think its needed.

Now we try the flashing command from the offical auvidea guide:

epadmin@epadmin-ESPRIMO-P400:~/nvidia/nvidia_sdk/JetPack_5.1.3_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p "-c bootloader/t186ref/cfg/flash_t234_qspi.xml" --showlogs --network usb0 p3509-a02+p3767-0000 internal
/home/epadmin/nvidia/nvidia_sdk/JetPack_5.1.3_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh --no-flash --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p -c bootloader/t186ref/cfg/flash_t234_qspi.xml --showlogs --network usb0 p3509-a02+p3767-0000 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/epadmin/nvidia/nvidia_sdk/JetPack_5.1.3_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra/flash.sh --no-flash --sign  -c bootloader/t186ref/cfg/flash_t234_qspi.xml p3509-a02+p3767-0000 internal

###############################################################################
# L4T BSP Information:
# R35 , REVISION: 5.0
# User release: 0.0
###############################################################################
ECID is 0x80012344705DD80B1400000007028080
copying emc_fuse_dev_params(/home/epadmin/nvidia/nvidia_sdk/JetPack_5.1.3_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-br-bct-diag-boot.dts)... done.
copying device_config(/home/epadmin/nvidia/nvidia_sdk/JetPack_5.1.3_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-mb1-bct-device-p3767-0000.dts)... done.
copying misc_config(/home/epadmin/nvidia/nvidia_sdk/JetPack_5.1.3_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-mb1-bct-misc-p3767-0000.dts)... done.
./tegraflash.py --chip 0x23 --applet "/home/epadmin/nvidia/nvidia_sdk/JetPack_5.1.3_Linux_JETSON_ORIN_NX_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 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.0276 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[   0.0285 ] File rcm_state open failed
[   0.0289 ] ERROR: failed to read rcm_state
[   0.0289 ] 
[   0.0299 ] tegrasign_v3.py --key None --getmode mode.txt
[   0.0301 ] Assuming zero filled SBK key
[   0.0294 ] Pre-processing config: tegra234-mb1-bct-device-p3767-0000.dts
[   0.0375 ] Pre-processing config: tegra234-mb1-bct-misc-p3767-0000.dts
[   0.0528 ] Parsing partition layout
[   0.0543 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[   0.0571 ] Kernel DTB used: None
[   0.0571 ] WARNING: dce base dtb is not provided

[   0.0571 ] Parsing partition layout
[   0.0589 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[   0.0608 ] Creating list of images to be signed
[   0.0625 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --list images_list.xml zerosbk
[   0.0640 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin
[   0.0659 ] Header already present for mb1_t234_prod_aligned_sigheader.bin
[   0.0667 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin
[   0.0752 ] Header already present for mb1_t234_prod_aligned_sigheader.bin
[   0.0760 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin
[   0.0831 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin
[   0.0837 ] adding BCH for mb2_t234_aligned.bin
[   0.0873 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin
[   0.1028 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin
[   0.1034 ] adding BCH for mb2_t234_aligned.bin
[   0.1217 ] Filling MB1 storage info
[   0.1217 ] Parsing dev params for multi chains
[   0.1297 ] Generating br-bct
[   0.1311 ] Updating dev and MSS params in BR BCT
[   0.1312 ] tegrabct_v2 --dev_param tegra234-br-bct-diag-boot_cpp.dtb --brbct br_bct.cfg --chip 0x23 0
[   0.1330 ] Updating bl info
[   0.1345 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updateblinfo readinfo_t234_min_prod.xml.bin
[   0.1356 ] WARNING: boot chain is not completed. set to 0
[   0.1366 ] Generating signatures
[   0.1376 ] tegrasign_v3.py --key None --list images_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.1381 ] Assuming zero filled SBK key
[   0.1601 ] Warning: pub_key.key is not found
[   0.1595 ] Parsing dev params for multi chains
[   0.1595 ] Generating br-bct
[   0.1609 ] Updating dev and MSS params in BR BCT
[   0.1610 ] tegrabct_v2 --dev_param tegra234-br-bct-diag-boot_cpp.dtb --brbct br_bct.cfg --chip 0x23 0
[   0.1636 ] Updating bl info
[   0.1648 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updateblinfo readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
[   0.1662 ] WARNING: boot chain is not completed. set to 0
[   0.1679 ] Get Signed section of bct
[   0.1691 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --listbct bct_list.xml
[   0.1705 ] Signing BCT
[   0.1715 ] tegrasign_v3.py --key None --list bct_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.1717 ] Assuming zero filled SBK key
[   0.1752 ] Sha saved in br_bct_BR.sha
[   0.1757 ] Warning: pub_key.key is not found
[   0.1748 ] Updating BCT with signature
[   0.1759 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesig bct_list_signed.xml
[   0.1771 ] Offset :4608 Len :3584
[   0.1778 ] Generating SHA2 Hash
[   0.1788 ] tegrasign_v3.py --key None --list bct_list.xml --sha sha512
[   0.1791 ] Assuming zero filled SBK key
[   0.1792 ] Assuming zero filled SBK key
[   0.1843 ] Sha saved in br_bct_BR.sha
[   0.1838 ] Updating BCT with SHA2 Hash
[   0.1849 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesha bct_list_signed.xml
[   0.1862 ] Offset :4608 Len :3584
[   0.1867 ] Offset :68 Len :8124
[   0.1870 ] Generating coldboot mb1-bct
[   0.1882 ] 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.1895 ] MB1-BCT version: 0.12
[   0.1897 ] ERROR: /misc/enable_dram_page_blacklisting is not supported
[   0.1901 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED1/ is not supported
[   0.1906 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED1/ is not supported
[   0.1911 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED1/ is not supported
[   0.1916 ] ERROR: /misc/tsc_controls/tsc_locking_config is not supported
[   0.1920 ] ERROR: /misc/tsc_controls/tsc_locking_diff_configuration is not supported
[   0.1924 ] ERROR: /misc/tsc_controls/tsc_locking_ref_frequency_configuration is not supported
[   0.1924 ] ERROR: /misc/tsc_controls/tsc_locking_control is not supported
[   0.1924 ] ERROR: /misc/tsc_controls/tsc_locking_adjust_configuration is not supported
[   0.1925 ] ERROR: /misc/tsc_controls/tsc_locking_fast_adjust_configuration is not supported
[   0.1925 ] ERROR: /misc/tsc_controls/tsc_locking_adjust_delta_control is not supported
[   0.1925 ] ERROR: /misc/tsc_controls/tsc_capture_control_ptx is not supported
[   0.1925 ] ERROR: /misc/tsc_controls/tsc_capture_config_ptx is not supported
[   0.1925 ] ERROR: /misc/tsc_controls/tsc_stscrsr is not supported
[   0.1925 ] ERROR: /misc/tsc_controls/tsc_locking_adjust_num_control is not supported
[   0.1925 ] 
[   0.1925 ] Parsing config file :tegra234-mb1-bct-device-p3767-0000_cpp.dtb 
[   0.1925 ] Added Platform Config 9 data with size :- 100
[   0.1925 ] 
[   0.1925 ] Updating mb1-bct with firmware information
[   0.1938 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_cold_boot_bct_MB1.bct --updatefwinfo readinfo_t234_min_prod.xml.bin
[   0.1969 ] tegrahost_v2 --chip 0x23 0 --align mb1_cold_boot_bct_MB1_aligned.bct
[   0.1980 ] Generating SHA2 Hash for mb1bct
[   0.2007 ] Sha saved in mb1_cold_boot_bct_MB1_aligned.sha
[   0.2022 ] Sha saved in mb1_cold_boot_bct_MB1.sha
[   0.2025 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --appendsigheader mb1_cold_boot_bct_MB1_aligned.bct zerosbk
[   0.2034 ] adding BCH for mb1_cold_boot_bct_MB1_aligned.bct
[   0.2056 ] tegrasign_v3.py --key None --list mb1_cold_boot_bct_MB1_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.2058 ] Assuming zero filled SBK key
[   0.2081 ] Warning: pub_key.key is not found
[   0.2084 ] 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.2110 ] Generating recovery mb1-bct
[   0.2127 ] 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.2140 ] MB1-BCT version: 0.12
[   0.2143 ] ERROR: /misc/enable_dram_page_blacklisting is not supported
[   0.2148 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED1/ is not supported
[   0.2153 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED1/ is not supported
[   0.2158 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED1/ is not supported
[   0.2163 ] ERROR: /misc/tsc_controls/tsc_locking_config is not supported
[   0.2167 ] ERROR: /misc/tsc_controls/tsc_locking_diff_configuration is not supported
[   0.2172 ] ERROR: /misc/tsc_controls/tsc_locking_ref_frequency_configuration is not supported
[   0.2175 ] ERROR: /misc/tsc_controls/tsc_locking_control is not supported
[   0.2175 ] ERROR: /misc/tsc_controls/tsc_locking_adjust_configuration is not supported
[   0.2175 ] ERROR: /misc/tsc_controls/tsc_locking_fast_adjust_configuration is not supported
[   0.2175 ] ERROR: /misc/tsc_controls/tsc_locking_adjust_delta_control is not supported
[   0.2175 ] ERROR: /misc/tsc_controls/tsc_capture_control_ptx is not supported
[   0.2175 ] ERROR: /misc/tsc_controls/tsc_capture_config_ptx is not supported
[   0.2175 ] ERROR: /misc/tsc_controls/tsc_stscrsr is not supported
[   0.2175 ] ERROR: /misc/tsc_controls/tsc_locking_adjust_num_control is not supported
[   0.2175 ] 
[   0.2175 ] Parsing config file :tegra234-mb1-bct-device-p3767-0000_cpp.dtb 
[   0.2175 ] Added Platform Config 9 data with size :- 100
[   0.2175 ] 
[   0.2176 ] Updating mb1-bct with firmware information
[   0.2190 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_bct_MB1.bct --recov --updatefwinfo readinfo_t234_min_prod.xml.bin
[   0.2223 ] tegrahost_v2 --chip 0x23 0 --align mb1_bct_MB1_aligned.bct
[   0.2235 ] Generating SHA2 Hash for mb1bct
[   0.2262 ] Sha saved in mb1_bct_MB1_aligned.sha
[   0.2281 ] Sha saved in mb1_bct_MB1.sha
[   0.2286 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --appendsigheader mb1_bct_MB1_aligned.bct zerosbk
[   0.2297 ] adding BCH for mb1_bct_MB1_aligned.bct
[   0.2319 ] tegrasign_v3.py --key None --list mb1_bct_MB1_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.2322 ] Assuming zero filled SBK key
[   0.2347 ] Warning: pub_key.key is not found
[   0.2352 ] tegrahost_v2 --chip 0x23 0 --updatesigheader mb1_bct_MB1_aligned_sigheader.bct.encrypt mb1_bct_MB1_aligned_sigheader.bct.hash zerosbk
[   0.2372 ] Error: Skip generating mem_bct because sdram_config is not defined
[   0.2372 ] Error: Skip generating mem_bct because sdram_config is not defined
[   0.2372 ] Copying signatures
[   0.2385 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
[   0.2494 ] Boot Rom communication
[   0.2511 ] 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.2525 ] BR_CID: 0x80012344705DD80B1400000007028080
[   0.2540 ] Sending bct_br
[   0.2542 ] Sending mb1
[   0.2561 ] Sending psc_bl1
[   0.2665 ] Sending bct_mb1
[   0.2726 ] Boot Rom communication completed
[   0.2755 ] tegrahost_v2 --chip 0x23 0 --align applet_t234_aligned.bin
[   0.2791 ] tegrahost_v2 --chip 0x23 0 --magicid MB2A --appendsigheader applet_t234_aligned.bin zerosbk
[   0.2807 ] adding BCH for applet_t234_aligned.bin
[   0.2993 ] tegrasign_v3.py --key None --list applet_t234_aligned_sigheader.bin_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.2997 ] Assuming zero filled SBK key
[   0.3036 ] Warning: pub_key.key is not found
[   0.3048 ] tegrahost_v2 --chip 0x23 0 --updatesigheader applet_t234_aligned_sigheader.bin.encrypt applet_t234_aligned_sigheader.bin.hash zerosbk
[   0.3081 ] Sending mb2_applet...

[   0.3097 ] tegrarcm_v2 --chip 0x23 0 --pollbl --download applet applet_t234_sigheader.bin.encrypt
[   0.3111 ] BL: version 1.4.0.1-t234-54845784-08e631ca last_boot_error: 656573201
[   0.4786 ] Sending applet
[   0.4789 ] ERROR: might be timeout in USB write.
Error: Return value 3
Command tegrarcm_v2 --chip 0x23 0 --pollbl --download applet applet_t234_sigheader.bin.encrypt
Reading board information failed.
Error: /home/epadmin/nvidia/nvidia_sdk/JetPack_5.1.3_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra/bootloader/signed/flash.idx is not found
Error: failed to relocate images to /home/epadmin/nvidia/nvidia_sdk/JetPack_5.1.3_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra/tools/kernel_flash/images
Cleaning up...

Still errors and now we get USB timeout error this is a common error. We found this error a lot when trying to flash the jetson. We tried using 35.2.1 jetson we tried to use 36.3.0 still no luck. We figured out that to flash the jetson we need to have the firmware from auvidea and all of its content in the linux for tegra folder to work but no matter what we tried nothing worked it wont flash nothing.
We even tried using SDK Manager but we got this error: “The connected Jetson Device is not ready for flashing” and then it say to reconnect the device make sure its in recovery mode which it is because it shows up when we type lsusb. What could be the problem? We tried a lot of usb ports lot of usb cables but nothing worked.

Screenshot from 2024-11-05 12-29-33
Screenshot from 2024-11-05 12-29-331680×1050 245 KB

But we heard that when flashing auvidea boards sdkmanager can’t help and we should use the official guide.

Should we try with another pc? What can we do?

3

Is your host machine a VM?

4

It is confusing for a newbie. You need a HOST pc (different PC) which has Ubuntu. You need to install nvidia sdkmanager on the host pc and then set the Jetson in recovery mode and connect to your host Ubuntu system. Depending upon Ubuntu OS version of your host PC, you will be able to install older or latest version of Jetpack 6/5/4 sdk components on your Jetson

5

No its not a virtual machine. The pc has only ubuntu installed on it via a fresh usb installer. I deleted every other files on the drive when installing the os.

6

Its in recovery mode…… it shows up in lsusb sdk manager recognize it as recovery jetson orin nx device. Its not a VM its a fresh ubuntu install

7

Moreover, while connecting your Jetson for flashing, generally it is the USB-C port on Jetson which needs to be connected to your host PC via USB-A port (preferably 3.x port)

8

It does not have a usb c port it only has a micro usb for flashing. Its connected via a micro usb cable and the other end is usb 2.0 regular type a. Pc doesjt have usb 3.0 ports only the ones which are black

9

Just some concepts to enhance the communication first.

  1. I just want to clarify that your board is a custom board.
    For any board that is not NV devkit, I cannot guarantee I can fully help here as I don’t know whether Auvidea gave you correct package. Please contact Auvidea in parallel for this issue.

  2. I saw something that is confusing here. Your first flash attempt is using “orin_nx_JNX42” but your second attempt is using "p3509-a02+p3767-0000 ". Which one does Auvidea guide you to use? You should just use that one but not other board config or even sdkmanager. Sdkmanager cannot flash a custom board.

  3. Please try to put your log into a text file and attach them here but not copy and paste. It would be easier for others to check and use search function. If you put all the logs in one comment, then it would be hard for us to check.

1 Like
10

  1. Okay i understand. I will contact Auvidea too.

  2. Both of them are from auvidea the first one is provided in the firmware file that i downloaded from the auvidea site. The second is also from auvidea its provided in there official gitbook guide which is on the website. Its the same command overall because the jnx42.sh has the same command in it.
    The:
    sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p “-c bootloader/t186ref/cfg/flash_t234_qspi.xml” --showlogs --network usb0 p3509-a02+p3767-0000 internal

This command gives the error that i shown in the main comment. We also tried using ./tools/flash.sh or something like that and then board id then rootfs. But that didnt work either

3 I will go to my pc and send you the files in 5 minutes.

11

I am not sure if their board has same layout as NV devkit.

Here is the method to dump device side log from NV devkit. You better checking if their board has same pin to dump the log.

If there is, I need the log during flash failure.

12

Does this work when no kernel or anything are on the board? We couldnt flash it so nothing are on the board other then the ones from the factory. One more issue is that its hard to get the jetson out because its an embedded system with heatsinks etc. Also im not at work today so i wont be able to do that. I will go again on monday. So untill then i cant provide any other info other that the ones i knoe and the ones i saved.

13

The serial console log will start to print since the bootloader so even kernel is not there, it would still have logs.

And if the flash attempt already started the bootrom, it will have log printed in the serial console too.

14

I dont think i will come to work today to test this out because im sick today. But on Monday i will write you a message here if thats fine. I also saw from other posts regarding issue when flashing jetson that this usb timeout error can not be replicated by nvidea and they should try on s different pc. Does trying on a different pc with new ubuntu install worth it. And also should it be ubuntu 18.4.6 or 20.4.6?

15

Also heres the full flashing log in a txt file. It has 3 flash logs the first ones are on ubuntu 20.4.6 the others are 18.04.6. Theres difference between the two. the first log are not relevant because it doesnt have all the firmware files from auvidea site thats why it say cant find board if pxxx…
error nviddea.txt (46.9 KB)

Edit: The first one is the one with the offical guide from auvidea that flashing command the second is sudo ./flash.sh jetson-orin-nano-devkit external the other 2 are the same one in the main message.

16

Hi,

I would like to suggest that you just use one kind of flash command suggested by Auvidea but not keep changing commands.

No idea why there would be 3 different commands to just flash one board. This thing makes not much sense and I don’t think Auvidea really suggested you to do that.

Your first command also had log said “p3509-a02+p3767-0000.conf: No such file or directory”. It is went back again to the first comment you filed in another post. This thing does not even need a discussion. It is just file missing. The flash process didn’t not even start.

Also, you are still not doing things correctly. Don’t put every log in one file. Put them in different files and use file name to tell the difference.
It is still a chaos to put everything in just one file if you ever read those logs by yourself…

17

The logs which i provided for you does have the p3509-a02+p3767-0000.conf in the other post where i sent the log that had the p3509-a02+p3767-0000.conf file missing that because auvidea don’t specify in there guide to download the firmware from their site and paste it to the linux for tegra folder. Then we will get the conf file which are necessary. Yes the flashing didn’t even start and i dont know why is that. When I provide all the files and do everything correctly according to the guide i still get usb time out error and failed to read rcm_state. That is the main problem.
I will write you exectly what i done step by step.

  1. I downloaded the jetson files and the Sample root files. Tried 5.1.3 , 36.3 , 35.2.1
  2. then I extract the files via terminal
  3. now i got the linux for tegra folder
  4. i copied the rootfs files to the rootfs directory in linux for tegra as the guide say
  5. then i typed sudo ./tools/l4t_flash_prerequisites.sh after that sudo ./apply_binaries.sh
  6. Now here comes the tricky part. I tried not downloading the firmware from auvidea site and then flashing it with the command that the provided but then it cant find board with p3509-a02+p3767-0000. Soo i downloaded and pasted all of its content to the linux for tegra folder. Which consist of kernel files mainly dtb files and conf files and sh files. Then tried again. Now the error is the first one on the main message this one:

logs1.txt (13.4 KB)

18

As I already told… do not copy and paste any log again. Just attach them as file.

It is okay to put your steps in list… but please do not copy and paste and log…

19

I fixed it

20

And just to point out some mistakes here.

  1. I downloaded the jetson files and the Sample root files. Tried 5.1.3 , 36.3 , 35.2.1

Just use the version that Auvidea suggest first. Do not use something that they don’t support… Focus on just one version to use here…

  1. Now here comes the tricky part. I tried not downloading the firmware from auvidea site and then flashing it with the command that the provided but then it cant find board with p3509-a02+p3767-0000.

I have no idea about what is this tricky part doing… totally no need to do this. Just follow Auvidea guide to prepare the BSP. You shoud not start to flash a board when the BSP is not yet well-prepared…

  1. Are you sure you really follow Auvidea website? For example, they asked you to do this part. Did you do that?
    image
    image861×652 69.4 KB
21
  1. Yes i tried it with their recommended Jetson version which is the 35.2.1
  2. Yes I adjusted the eprom size to 0x0
  3. The tricky part is when you dont download the files from auvidea site these are from the support tab and on the firmware tab. Then you dont get conf files which i think its needed but if you say they arent then i dont know. Here i will attach it you can take a look at what does it contain.
    Jetpack_5_1_3_Orin_NX_NANO_v1.zip (82.9 KB)