Unable to flash L4T 35 to AGX Orin (P3730)

Autonomous Machines Jetson & Embedded Systems Jetson AGX Orin
1

I need to reflash the baseline Jetpack R35 to my AGX Orin 64GB Devkit (Model P3730) because something was dorked. I’ve tried to use the sdkmanager and the CLI jetpack tools and both give the same issue. Searching, I saw the possible issue with USB autosuspend and tried that:

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

But it still had no effect. I’m running Ubuntu 22.04 on a Dell laptop in host mode (no Docker). The only other thing I can think of is that the AGX seems to be connecting at USB 2.0 speeds if my reading of lsusb -t is correct:

Bus 003 Device 062: ID 0955:7023 NVIDIA Corp. APX

|__ Port 11: Dev 62, If 0, Class=Vendor Specific Class, Driver=, 480M

I’m also attaching the error logs generated by sdkmanager.

SDKM_logs_JetPack_6.0_DP_Linux_for_Jetson_AGX_Orin_modules_2024-03-06_13-22-24.zip (112.6 KB)

(base) :~/Code/NVidia/Tegra_Linux/Linux_for_Tegra$ sudo ./flash.sh jetson-agx-orin-devkit internal
###############################################################################

L4T BSP Information:

R35 , REVISION: 5.0

User release: 0.0

###############################################################################
ECID is 0x80012344705DD2025C00000001FE8100

Target Board Information:

Name: jetson-agx-orin-devkit, Board Family: t186ref, SoC: Tegra 234,

OpMode: production, Boot Authentication: NS,

Disk encryption: disabled ,

###############################################################################
copying emc_fuse_dev_params(/home/user/Code/NVidia/Tegra_Linux/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-br-bct-diag-boot.dts)… done.
copying device_config(/home/user/Code/NVidia/Tegra_Linux/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-mb1-bct-device-p3701-0000.dts)… done.
copying misc_config(/home/user/Code/NVidia/Tegra_Linux/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-mb1-bct-misc-p3701-0000.dts)… done.
./tegraflash.py --chip 0x23 --applet “/home/user/Code/NVidia/Tegra_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 “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.0110 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 0.0113 ] File rcm_state open failed
[ 0.0114 ] ERROR: failed to read rcm_state
[ 0.0114 ]
[ 0.0131 ] tegrasign_v3.py --key None --getmode mode.txt
[ 0.0132 ] Assuming zero filled SBK key
[ 0.0115 ] Pre-processing config: tegra234-mb1-bct-device-p3701-0000.dts
[ 0.0156 ] Pre-processing config: tegra234-mb1-bct-misc-p3701-0000.dts
[ 0.0211 ] Parsing partition layout
[ 0.0215 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[ 0.0222 ] Kernel DTB used: None
[ 0.0222 ] WARNING: dce base dtb is not provided

[ 0.0222 ] Parsing partition layout
[ 0.0226 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[ 0.0235 ] Creating list of images to be signed
[ 0.0237 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --list images_list.xml zerosbk
[ 0.0240 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin
[ 0.0246 ] Header already present for mb1_t234_prod_aligned_sigheader.bin
[ 0.0248 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin
[ 0.0279 ] Header already present for mb1_t234_prod_aligned_sigheader.bin
[ 0.0285 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin
[ 0.0320 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin
[ 0.0324 ] adding BCH for mb2_t234_aligned.bin
[ 0.0335 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin
[ 0.0425 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin
[ 0.0427 ] adding BCH for mb2_t234_aligned.bin
[ 0.0526 ] Filling MB1 storage info
[ 0.0526 ] Parsing dev params for multi chains
[ 0.0568 ] Generating br-bct
[ 0.0570 ] Updating dev and MSS params in BR BCT
[ 0.0570 ] tegrabct_v2 --dev_param tegra234-br-bct-diag-boot_cpp.dtb --brbct br_bct.cfg --chip 0x23 0
[ 0.0574 ] Updating bl info
[ 0.0577 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updateblinfo readinfo_t234_min_prod.xml.bin
[ 0.0578 ] WARNING: boot chain is not completed. set to 0
[ 0.0582 ] Generating signatures
[ 0.0600 ] tegrasign_v3.py --key None --list images_list.xml --pubkeyhash pub_key.key --sha sha512
[ 0.0601 ] Assuming zero filled SBK key
[ 0.0655 ] Warning: pub_key.key is not found
[ 0.0639 ] Parsing dev params for multi chains
[ 0.0639 ] Generating br-bct
[ 0.0640 ] Updating dev and MSS params in BR BCT
[ 0.0640 ] tegrabct_v2 --dev_param tegra234-br-bct-diag-boot_cpp.dtb --brbct br_bct.cfg --chip 0x23 0
[ 0.0643 ] Updating bl info
[ 0.0645 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updateblinfo readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
[ 0.0646 ] WARNING: boot chain is not completed. set to 0
[ 0.0651 ] Get Signed section of bct
[ 0.0653 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --listbct bct_list.xml
[ 0.0656 ] Signing BCT
[ 0.0673 ] tegrasign_v3.py --key None --list bct_list.xml --pubkeyhash pub_key.key --sha sha512
[ 0.0674 ] Assuming zero filled SBK key
[ 0.0689 ] Sha saved in br_bct_BR.sha
[ 0.0690 ] Warning: pub_key.key is not found
[ 0.0673 ] Updating BCT with signature
[ 0.0674 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesig bct_list_signed.xml
[ 0.0675 ] Offset :4608 Len :3584
[ 0.0678 ] Generating SHA2 Hash
[ 0.0695 ] tegrasign_v3.py --key None --list bct_list.xml --sha sha512
[ 0.0696 ] Assuming zero filled SBK key
[ 0.0696 ] Assuming zero filled SBK key
[ 0.0704 ] Sha saved in br_bct_BR.sha
[ 0.0688 ] Updating BCT with SHA2 Hash
[ 0.0690 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesha bct_list_signed.xml
[ 0.0691 ] Offset :4608 Len :3584
[ 0.0693 ] Offset :68 Len :8124
[ 0.0694 ] Generating coldboot mb1-bct
[ 0.0695 ] 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.0697 ] MB1-BCT version: 0.12
[ 0.0698 ] ERROR: /misc/enable_dram_page_blacklisting is not supported
[ 0.0699 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED1/ is not supported
[ 0.0701 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED1/ is not supported
[ 0.0703 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED1/ is not supported
[ 0.0704 ] ERROR: /misc/tsc_controls/tsc_locking_config is not supported
[ 0.0706 ] ERROR: /misc/tsc_controls/tsc_locking_diff_configuration is not supported
[ 0.0707 ] ERROR: /misc/tsc_controls/tsc_locking_ref_frequency_configuration is not supported
[ 0.0709 ] ERROR: /misc/tsc_controls/tsc_locking_control is not supported
[ 0.0711 ] ERROR: /misc/tsc_controls/tsc_locking_adjust_configuration is not supported
[ 0.0712 ] ERROR: /misc/tsc_controls/tsc_locking_fast_adjust_configuration is not supported
[ 0.0714 ] ERROR: /misc/tsc_controls/tsc_locking_adjust_delta_control is not supported
[ 0.0715 ] ERROR: /misc/tsc_controls/tsc_capture_control_ptx is not supported
[ 0.0715 ] ERROR: /misc/tsc_controls/tsc_capture_config_ptx is not supported
[ 0.0715 ] ERROR: /misc/tsc_controls/tsc_stscrsr is not supported
[ 0.0715 ] ERROR: /misc/tsc_controls/tsc_locking_adjust_num_control is not supported
[ 0.0715 ]
[ 0.0715 ] Parsing config file :tegra234-mb1-bct-device-p3701-0000_cpp.dtb
[ 0.0715 ] Added Platform Config 9 data with size :- 100
[ 0.0715 ]
[ 0.0715 ] Updating mb1-bct with firmware information
[ 0.0717 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_cold_boot_bct_MB1.bct --updatefwinfo readinfo_t234_min_prod.xml.bin
[ 0.0722 ] tegrahost_v2 --chip 0x23 0 --align mb1_cold_boot_bct_MB1_aligned.bct
[ 0.0724 ] Generating SHA2 Hash for mb1bct
[ 0.0745 ] Sha saved in mb1_cold_boot_bct_MB1_aligned.sha
[ 0.0748 ] Sha saved in mb1_cold_boot_bct_MB1.sha
[ 0.0732 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --appendsigheader mb1_cold_boot_bct_MB1_aligned.bct zerosbk
[ 0.0734 ] adding BCH for mb1_cold_boot_bct_MB1_aligned.bct
[ 0.0756 ] tegrasign_v3.py --key None --list mb1_cold_boot_bct_MB1_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[ 0.0756 ] Assuming zero filled SBK key
[ 0.0762 ] Warning: pub_key.key is not found
[ 0.0747 ] 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.0752 ] Generating recovery mb1-bct
[ 0.0753 ] 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.0755 ] MB1-BCT version: 0.12
[ 0.0756 ] ERROR: /misc/enable_dram_page_blacklisting is not supported
[ 0.0757 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED1/ is not supported
[ 0.0758 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED1/ is not supported
[ 0.0759 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED1/ is not supported
[ 0.0761 ] ERROR: /misc/tsc_controls/tsc_locking_config is not supported
[ 0.0763 ] ERROR: /misc/tsc_controls/tsc_locking_diff_configuration is not supported
[ 0.0764 ] ERROR: /misc/tsc_controls/tsc_locking_ref_frequency_configuration is not supported
[ 0.0766 ] ERROR: /misc/tsc_controls/tsc_locking_control is not supported
[ 0.0767 ] ERROR: /misc/tsc_controls/tsc_locking_adjust_configuration is not supported
[ 0.0768 ] ERROR: /misc/tsc_controls/tsc_locking_fast_adjust_configuration is not supported
[ 0.0769 ] ERROR: /misc/tsc_controls/tsc_locking_adjust_delta_control is not supported
[ 0.0769 ] ERROR: /misc/tsc_controls/tsc_capture_control_ptx is not supported
[ 0.0769 ] ERROR: /misc/tsc_controls/tsc_capture_config_ptx is not supported
[ 0.0769 ] ERROR: /misc/tsc_controls/tsc_stscrsr is not supported
[ 0.0769 ] ERROR: /misc/tsc_controls/tsc_locking_adjust_num_control is not supported
[ 0.0769 ]
[ 0.0769 ] Parsing config file :tegra234-mb1-bct-device-p3701-0000_cpp.dtb
[ 0.0769 ] Added Platform Config 9 data with size :- 100
[ 0.0769 ]
[ 0.0769 ] Updating mb1-bct with firmware information
[ 0.0770 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_bct_MB1.bct --recov --updatefwinfo readinfo_t234_min_prod.xml.bin
[ 0.0777 ] tegrahost_v2 --chip 0x23 0 --align mb1_bct_MB1_aligned.bct
[ 0.0779 ] Generating SHA2 Hash for mb1bct
[ 0.0799 ] Sha saved in mb1_bct_MB1_aligned.sha
[ 0.0804 ] Sha saved in mb1_bct_MB1.sha
[ 0.0788 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --appendsigheader mb1_bct_MB1_aligned.bct zerosbk
[ 0.0790 ] adding BCH for mb1_bct_MB1_aligned.bct
[ 0.0811 ] tegrasign_v3.py --key None --list mb1_bct_MB1_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[ 0.0812 ] Assuming zero filled SBK key
[ 0.0817 ] Warning: pub_key.key is not found
[ 0.0802 ] tegrahost_v2 --chip 0x23 0 --updatesigheader mb1_bct_MB1_aligned_sigheader.bct.encrypt mb1_bct_MB1_aligned_sigheader.bct.hash zerosbk
[ 0.0806 ] Error: Skip generating mem_bct because sdram_config is not defined
[ 0.0806 ] Error: Skip generating mem_bct because sdram_config is not defined
[ 0.0806 ] Copying signatures
[ 0.0808 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
[ 0.0833 ] Boot Rom communication
[ 0.0836 ] 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.0838 ] BR_CID: 0x80012344705DD2025C00000001FE8100
[ 0.1108 ] Sending bct_br
[ 0.1541 ] 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.

2

Just to rule out the obvious, I’ve tried with a number of different USB cables (A->C, C-C) on the same USB ports on the laptop, which I know work as they are able to connect my NVME external drives at full speed, so I’m not sure why I’m getting USB 2.0 connection speeds:

(base) ~/Code/NVidia/Tegra_Linux/Linux_for_Tegra$ sdkmanager --list-connected
Jetson:
Device Name | USB Port | USB Bus/Device | USB Specification | Network Interface | MAC Address | Status

        | 3-11     | 003/062        | 2.002.00          | null              | null        | Recovery
4

Force recovery mode on Orin platforms by default works at USB 2.0, unless it’s otherwise fuse burnt, so nothing to panic here.

Manually put the device into force recovery mode again, use a different USB cable/port, reboot the host PC…
Find a different host PC if all of the above fails.

5

Trying from an Ubuntu 20.04 Tensorbook seemed to work. I’m not sure why Jammy 22.04 would have heartburn even trying to run the CLI script, but unless there’s something weird about Dell (because Dell) I’m at a loss to understand why. Either way, I was lucky to find the 20.04 laptop.

6

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

  4. Replug the USB cable into the USB hub and the Jetson

  5. Power on the Jetson and put it into recovery mode

  6. Flash

8

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