Hello,
I’m trying to flash my AGX Orin. The vendor provided the BSP so they validated it and it should be working. However, when launching the process, I get an error saying that it might be timeout in USB write. As suggested by others in this forum, I deactivated usb autosuspend, but still not working. Here is the full log:
Full L4T Image
###############################################################################
# L4T BSP Information:
# R36 , REVISION: 2.0
# User release: 0.0
###############################################################################
ECID is 0x80012344705DD3E31000000016030100
# Target Board Information:
# Name: jetson-agx-orin-devkit, Board Family: generic, SoC: Tegra 234,
# OpMode: production, Boot Authentication: NS,
# Disk encryption: disabled ,
###############################################################################
copying emc_fuse_dev_params(JetPack_6.0_DP_Linux_DP_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra/bootloader/generic/BCT/tegra234-br-bct-diag-boot.dts)... done.
copying device_config(JetPack_6.0_DP_Linux_DP_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra/bootloader/generic/BCT/tegra234-mb1-bct-device-p3701-0000.dts)... done.
copying misc_config(JetPack_6.0_DP_Linux_DP_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra/bootloader/generic/BCT/tegra234-mb1-bct-misc-p3701-0000.dts)... done.
./tegraflash.py --chip "0x23" --applet "JetPack_6.0_DP_Linux_DP_JETSON_AGX_ORIN_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-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 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.0224 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 0.0227 ] File rcm_state open failed
[ 0.0229 ] ERROR: failed to read rcm_state
[ 0.0229 ]
[ 0.0236 ] tegrasign_v3.py --key None --getmode mode.txt
[ 0.0237 ] Assuming zero filled SBK key
[ 0.0232 ] Pre-processing config: tegra234-mb1-bct-device-p3701-0000.dts
[ 0.0287 ] Pre-processing config: tegra234-mb1-bct-misc-p3701-0000.dts
[ 0.0369 ] Parsing partition layout
[ 0.0373 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[ 0.0382 ] Kernel DTB used: None
[ 0.0382 ] WARNING: dce base dtb is not provided
[ 0.0382 ] Parsing partition layout
[ 0.0385 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[ 0.0391 ] Creating list of images to be signed
[ 0.0394 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --list images_list.xml zerosbk
[ 0.0397 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin
[ 0.0408 ] Header already present for mb1_t234_prod_aligned_sigheader.bin
[ 0.0412 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin
[ 0.0457 ] Header already present for mb1_t234_prod_aligned_sigheader.bin
[ 0.0711 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin
[ 0.0764 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin
[ 0.0770 ] adding BCH for mb2_t234_aligned.bin
[ 0.0801 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin
[ 0.0947 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin
[ 0.0953 ] adding BCH for mb2_t234_aligned.bin
[ 0.1095 ] Filling MB1 storage info
[ 0.1095 ] Parsing dev params for multi chains
[ 0.1163 ] Generating br-bct
[ 0.1167 ] Updating dev and MSS params in BR BCT
[ 0.1167 ] tegrabct_v2 --dev_param tegra234-br-bct-diag-boot_cpp.dtb --brbct br_bct.cfg --chip 0x23 0
[ 0.1173 ] Updating bl info
[ 0.1176 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updateblinfo readinfo_t234_min_prod.xml.bin
[ 0.1179 ] WARNING: boot chain is not completed. set to 0
[ 0.1190 ] Generating signatures
[ 0.1196 ] tegrasign_v3.py --key None --list images_list.xml --pubkeyhash pub_key.key --sha sha512
[ 0.1198 ] Assuming zero filled SBK key
[ 0.1280 ] Warning: pub_key.key is not found
[ 0.1276 ] Parsing dev params for multi chains
[ 0.1276 ] Generating br-bct
[ 0.1281 ] Updating dev and MSS params in BR BCT
[ 0.1281 ] tegrabct_v2 --dev_param tegra234-br-bct-diag-boot_cpp.dtb --brbct br_bct.cfg --chip 0x23 0
[ 0.1288 ] Updating bl info
[ 0.1292 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updateblinfo readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
[ 0.1296 ] WARNING: boot chain is not completed. set to 0
[ 0.1312 ] Generating SHA2 Hash
[ 0.1326 ] Sha saved in br_bct_BR.sha
[ 0.1320 ] Get Signed section of bct
[ 0.1323 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --listbct bct_list.xml
[ 0.1329 ] Signing BCT
[ 0.1335 ] tegrasign_v3.py --key None --list bct_list.xml --pubkeyhash pub_key.key --sha sha512
[ 0.1337 ] Assuming zero filled SBK key
[ 0.1353 ] Sha saved in br_bct_BR.sha
[ 0.1355 ] Warning: pub_key.key is not found
[ 0.1349 ] Updating BCT with signature
[ 0.1352 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesig bct_list_signed.xml
[ 0.1355 ] Offset :4608 Len :3584
[ 0.1360 ] Generating SHA2 Hash
[ 0.1367 ] tegrasign_v3.py --key None --list bct_list.xml --sha sha512
[ 0.1368 ] Assuming zero filled SBK key
[ 0.1368 ] Assuming zero filled SBK key
[ 0.1385 ] Sha saved in br_bct_BR.sha
[ 0.1381 ] Updating BCT with SHA2 Hash
[ 0.1384 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesha bct_list_signed.xml
[ 0.1387 ] Offset :4608 Len :3584
[ 0.1390 ] Offset :68 Len :8124
[ 0.1401 ] Generating coldboot mb1-bct
[ 0.1404 ] 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.1407 ] MB1-BCT version: 0.13
[ 0.1422 ] Parsing config file :tegra234-mb1-bct-device-p3701-0000_cpp.dtb
[ 0.1424 ] Added Platform Config 9 data with size :- 100
[ 0.1424 ]
[ 0.1424 ] Updating mb1-bct with firmware information
[ 0.1427 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_cold_boot_bct_MB1.bct --updatefwinfo readinfo_t234_min_prod.xml.bin
[ 0.1440 ] tegrahost_v2 --chip 0x23 0 --align mb1_cold_boot_bct_MB1_aligned.bct
[ 0.1447 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --appendsigheader mb1_cold_boot_bct_MB1_aligned.bct zerosbk
[ 0.1450 ] adding BCH for mb1_cold_boot_bct_MB1_aligned.bct
[ 0.1465 ] tegrasign_v3.py --key None --list mb1_cold_boot_bct_MB1_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[ 0.1467 ] Assuming zero filled SBK key
[ 0.1479 ] Warning: pub_key.key is not found
[ 0.1477 ] 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.1484 ] Generating recovery mb1-bct
[ 0.1488 ] 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.1491 ] MB1-BCT version: 0.13
[ 0.1506 ] Parsing config file :tegra234-mb1-bct-device-p3701-0000_cpp.dtb
[ 0.1509 ] Added Platform Config 9 data with size :- 100
[ 0.1509 ]
[ 0.1509 ] Updating mb1-bct with firmware information
[ 0.1512 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_bct_MB1.bct --recov --updatefwinfo readinfo_t234_min_prod.xml.bin
[ 0.1523 ] tegrahost_v2 --chip 0x23 0 --align mb1_bct_MB1_aligned.bct
[ 0.1526 ] Generating SHA2 Hash for mb1bct
[ 0.1542 ] Sha saved in mb1_bct_MB1_aligned.sha
[ 0.1539 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --appendsigheader mb1_bct_MB1_aligned.bct zerosbk
[ 0.1542 ] adding BCH for mb1_bct_MB1_aligned.bct
[ 0.1555 ] tegrasign_v3.py --key None --list mb1_bct_MB1_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[ 0.1556 ] Assuming zero filled SBK key
[ 0.1568 ] Warning: pub_key.key is not found
[ 0.1565 ] tegrahost_v2 --chip 0x23 0 --updatesigheader mb1_bct_MB1_aligned_sigheader.bct.encrypt mb1_bct_MB1_aligned_sigheader.bct.hash zerosbk
[ 0.1573 ] Error: Skip generating mem_bct because sdram_config is not defined
[ 0.1573 ] Error: Skip generating mem_bct because sdram_config is not defined
[ 0.1573 ] Copying signatures
[ 0.1576 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
[ 0.1627 ] mb1_t234_prod_aligned_sigheader.bin.encrypt filename is from images_list
[ 0.1629 ] psc_bl1_t234_prod_aligned_sigheader.bin.encrypt filename is from images_list
[ 0.1629 ] Boot Rom communication
[ 0.1633 ] 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.1637 ] BR_CID: 0x80012344705DD3E31000000016030100
[ 0.1645 ] Sending bct_br
[ 0.1646 ] 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.
Unfortunately, I saw in this forum that the error is random and no solution was proposed. Maybe someone was able to solve it from that time.
I was able to move on on this. Needed to install binutils first:
sudo apt-get install binutils
After that, I found out that there is two Image files in the folder kernel.
Image (41Mb) and the other one Image.gz (14Mb).
I don’t know if that’s the right thing to do, but since the Image file was not in gzip format as mentionned by the error before, I renamed the Image.gz to Image. So the flash worked and finished. However, the device does not boot anymore. I get into the Nvidia boot screen, but it hangs forever on a black screen after that. So I guess what I did was a mistake as it was the kernel Image.
Thanks @WayneWWW . Indeed, the system was flashed.
However, after booting the device, I get into the Linux configuration sreen (for configuring users). It starts installing but stops and I find myself in an empty desktop.
dmesg says " Please complete system configuration setup on dekstop to proceed".
I tried rebooting, I end up on the same screen like the system is not installed. However, when trying the same computer name, it says that it already exists on the network.