Unable to flash AGX Orin with NVMe disk

Autonomous Machines Jetson & Embedded Systems Jetson AGX Orin
, ,
1

Trying to flash my Jetson AGX Orin with a 500 gb NVMe disk. I have successfully flashed other AGX Xavier units with SSDs a while back, but it seems like you guys made some progress on making that easier. However, I can’t successfully flash at this time.

$ echo $BOARD
jetson-agx-orin-devkit
$ sudo ./flash.sh $BOARD external
###############################################################################
# L4T BSP Information:
# R35 , REVISION: 1.0
###############################################################################
# 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/per/nvidia/jetson-linux-35-1/linux/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-br-bct-diag-boot.dts)... done.
copying device_config(/home/per/nvidia/jetson-linux-35-1/linux/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-mb1-bct-device-p3701-0000.dts)... done.
copying misc_config(/home/per/nvidia/jetson-linux-35-1/linux/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-mb1-bct-misc-p3701-0000.dts)... done.
./tegraflash.py --chip 0x23 --applet "/home/per/nvidia/jetson-linux-35-1/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.0068 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[   0.0076 ] File rcm_state open failed
[   0.0079 ] ERROR: failed to read rcm_state
[   0.0079 ]
[   0.0086 ] tegrasign_v3.py --key None --getmode mode.txt
[   0.0088 ] Assuming zero filled SBK key
[   0.0082 ] Pre-processing config: tegra234-mb1-bct-device-p3701-0000.dts
[   0.0172 ] Pre-processing config: tegra234-mb1-bct-misc-p3701-0000.dts
[   0.0260 ] Parsing partition layout
[   0.0272 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[   0.0286 ] Parsing partition layout
[   0.0298 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[   0.0308 ] Creating list of images to be signed
[   0.0315 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --list images_list.xml zerosbk
[   0.0319 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin
[   0.0329 ] Header already present for mb1_t234_prod_aligned_sigheader.bin
[   0.0334 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin
[   0.0388 ] Header already present for mb1_t234_prod_aligned_sigheader.bin
[   0.0391 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin
[   0.0427 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin
[   0.0429 ] adding BCH for mb2_t234_aligned.bin
[   0.0455 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin
[   0.0569 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin
[   0.0572 ] adding BCH for mb2_t234_aligned.bin
[   0.0711 ] Generating signatures
[   0.0718 ] tegrasign_v3.py --key None --list images_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.0720 ] Assuming zero filled SBK key
[   0.0844 ] Warning: pub_key.key is not found
[   0.0841 ] Parsing dev params for multi chains
[   0.0897 ] Generating br-bct
[   0.0911 ] Updating dev and MSS params in BR BCT
[   0.0913 ] tegrabct_v2 --dev_param tegra234-br-bct-diag-boot_cpp.dtb --brbct br_bct.cfg --chip 0x23 0
[   0.0922 ] Updating bl info
[   0.0928 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updateblinfo readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
[   0.0936 ] WARNING: boot chain is not completed. set to 0
[   0.0945 ] Get Signed section of bct
[   0.0953 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --listbct bct_list.xml
[   0.0960 ] Signing BCT
[   0.0967 ] tegrasign_v3.py --key None --list bct_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.0968 ] Assuming zero filled SBK key
[   0.0994 ] Sha saved in br_bct_BR.sha
[   0.0997 ] Warning: pub_key.key is not found
[   0.0991 ] Updating BCT with signature
[   0.0999 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesig bct_list_signed.xml
[   0.1004 ] Offset :4608 Len :3584
[   0.1007 ] Generating SHA2 Hash
[   0.1015 ] tegrasign_v3.py --key None --list bct_list.xml --sha sha512
[   0.1017 ] Assuming zero filled SBK key
[   0.1017 ] Assuming zero filled SBK key
[   0.1048 ] Sha saved in br_bct_BR.sha
[   0.1044 ] Updating BCT with SHA2 Hash
[   0.1054 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesha bct_list_signed.xml
[   0.1065 ] Offset :4608 Len :3584
[   0.1067 ] Offset :68 Len :8124
[   0.1069 ] Generating coldboot mb1-bct
[   0.1076 ] 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.1081 ] MB1-BCT version: 0.9

[   0.1090 ] Parsing config file :tegra234-mb1-bct-device-p3701-0000_cpp.dtb
[   0.1093 ] Added Platform Config 9 data with size :- 80
[   0.1093 ]
[   0.1093 ] Updating mb1-bct with firmware information
[   0.1101 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_cold_boot_bct_MB1.bct --updatefwinfo readinfo_t234_min_prod.xml.bin
[   0.1114 ] tegrahost_v2 --chip 0x23 0 --align mb1_cold_boot_bct_MB1_aligned.bct
[   0.1126 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --appendsigheader mb1_cold_boot_bct_MB1_aligned.bct zerosbk
[   0.1135 ] adding BCH for mb1_cold_boot_bct_MB1_aligned.bct
[   0.1150 ] tegrasign_v3.py --key None --list mb1_cold_boot_bct_MB1_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.1151 ] Assuming zero filled SBK key
[   0.1165 ] Warning: pub_key.key is not found
[   0.1167 ] 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.1183 ] Generating recovery mb1-bct
[   0.1191 ] 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.1198 ] MB1-BCT version: 0.9

[   0.1209 ] Parsing config file :tegra234-mb1-bct-device-p3701-0000_cpp.dtb
[   0.1210 ] Added Platform Config 9 data with size :- 80
[   0.1212 ] Updating mb1-bct with firmware information
[   0.1219 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_bct_MB1.bct --recov --updatefwinfo readinfo_t234_min_prod.xml.bin
[   0.1235 ] tegrahost_v2 --chip 0x23 0 --align mb1_bct_MB1_aligned.bct
[   0.1244 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --appendsigheader mb1_bct_MB1_aligned.bct zerosbk
[   0.1253 ] adding BCH for mb1_bct_MB1_aligned.bct
[   0.1266 ] tegrasign_v3.py --key None --list mb1_bct_MB1_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.1268 ] Assuming zero filled SBK key
[   0.1279 ] Warning: pub_key.key is not found
[   0.1278 ] tegrahost_v2 --chip 0x23 0 --updatesigheader mb1_bct_MB1_aligned_sigheader.bct.encrypt mb1_bct_MB1_aligned_sigheader.bct.hash zerosbk
[   0.1291 ] Error: Skip generating mem_bct because sdram_config is not defined
[   0.1291 ] Error: Skip generating mem_bct because sdram_config is not defined
[   0.1291 ] Copying signatures
[   0.1299 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
[   0.1359 ] mb1_t234_prod_aligned_sigheader.bin.encrypt filename is from images_list
[   0.1360 ] psc_bl1_t234_prod_aligned_sigheader.bin.encrypt filename is from images_list
[   0.1360 ] Boot Rom communication
[   0.1373 ] 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.1383 ] BR_CID: 0x80012344705DD3081000000007FF01C0
[   0.1396 ] Sending bct_br
[   0.1530 ] 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.

Tried two different USB-C cables (typically used to transfer image, so I believe they are of high quality), all my different USB-C inputs on my computer. Can’t figure it out. What do I need to do beside the above command, if I want to use a NVMe disk for the root system?

Additional info:

$ uname -a
Linux devper 5.11.12-051112-generic #202104071432 SMP Wed Apr 7 14:50:17 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 20.04.5 LTS
Release:	20.04
Codename:	focal
$ sudo apt update && sudo apt upgrade
[...]
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
3

Hi per.edwardsson,

Do you want to use NVMe for booting or as root file system?

Please refer to following instruction for flashing to an NVMe Drive
Flashing Support — Flashing to an NVMe Drive
You may need to use l4t_initrd_flash.sh instead of flash.sh to flash to NVMe.

4

What I care most about is not running out of space on disk. Do I need to boot from it then? Or is it enough to just use it as a rootfs?

5

For your case, it would be enough for you to use it as rootfs, but you still need to use l4t_inird_flash.sh to flash rootfs to your NVMe.

1 Like
6

Okay. Regardless of script I use I get the same error as listed in the OP. Following the advice of USB Timeout when flashing AGX Orin - #15 by WayneWWW, I updated linux kernel to 5.15.0-57. The problem appears to persist. What else can we try?

7

Do you have other ubuntu host (e.g. ubuntu 18.04) to try?

8

I have another host, but it is running 20.04 with 5.4.0-132-generic. I tried with it just in case, but got the same exact error. Is 18.04 necessary?

9

Sorry for the late response, have you managed to get issue resolved or still need the support? Thanks

10

Issue persists. Should I look for a different version of Ubuntu? Await newer Linux kernels? Can I provide you with any logs that can help you help me?

11

Please try using Ubuntu18.04 to flash the board.
Many users worked on this release.

You could also provide us the steps you did and serial console log for further check.

12

Can confirm it worked fine after Ubuntu 18.04.

14

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