Can not flash Orin AGX "Reading board information failed"

I can not flash the AGX Orin at all. I tried the sdkmanager but it failed the same way as shown here: Cannot flash Jetson AGX orin: "Reading board information failed".

After that I tried to run

$~/nvidia/nvidia_sdk/JetPack_5.0.2_Linux_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra$ sudo ./flash.sh jetson-agx-orin-devkit mmcblk0p1

which let to the following output:

###############################################################################
# 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/marco/nvidia/nvidia_sdk/JetPack_5.0.2_Linux_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-br-bct-diag-boot.dts)... done.
copying device_config(/home/marco/nvidia/nvidia_sdk/JetPack_5.0.2_Linux_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-mb1-bct-device-p3701-0000.dts)... done.
copying misc_config(/home/marco/nvidia/nvidia_sdk/JetPack_5.0.2_Linux_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-mb1-bct-misc-p3701-0000.dts)... done.
./tegraflash.py --chip 0x23 --applet "/home/marco/nvidia/nvidia_sdk/JetPack_5.0.2_Linux_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 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.0072 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[   0.0082 ] File rcm_state open failed
[   0.0085 ] ERROR: failed to read rcm_state
[   0.0085 ] 
[   0.0093 ] tegrasign_v3.py --key None --getmode mode.txt
[   0.0096 ] Assuming zero filled SBK key
[   0.0090 ] Pre-processing config: tegra234-mb1-bct-device-p3701-0000.dts
[   0.0164 ] Pre-processing config: tegra234-mb1-bct-misc-p3701-0000.dts
[   0.0281 ] Parsing partition layout
[   0.0295 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[   0.0313 ] Parsing partition layout
[   0.0324 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[   0.0337 ] Creating list of images to be signed
[   0.0348 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --list images_list.xml zerosbk
[   0.0358 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin
[   0.0372 ] Header already present for mb1_t234_prod_aligned_sigheader.bin
[   0.0379 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin
[   0.0441 ] Header already present for mb1_t234_prod_aligned_sigheader.bin
[   0.0446 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin
[   0.0500 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin
[   0.0505 ] adding BCH for mb2_t234_aligned.bin
[   0.0538 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin
[   0.0709 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin
[   0.0714 ] adding BCH for mb2_t234_aligned.bin
[   0.0911 ] Generating signatures
[   0.0919 ] tegrasign_v3.py --key None --list images_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.0922 ] Assuming zero filled SBK key
[   0.1074 ] Warning: pub_key.key is not found
[   0.1074 ] Parsing dev params for multi chains
[   0.1169 ] Generating br-bct
[   0.1184 ] Updating dev and MSS params in BR BCT
[   0.1186 ] tegrabct_v2 --dev_param tegra234-br-bct-diag-boot_cpp.dtb --brbct br_bct.cfg --chip 0x23 0
[   0.1202 ] Updating bl info
[   0.1216 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updateblinfo readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
[   0.1229 ] WARNING: boot chain is not completed. set to 0
[   0.1246 ] Get Signed section of bct
[   0.1262 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --listbct bct_list.xml
[   0.1281 ] Signing BCT
[   0.1290 ] tegrasign_v3.py --key None --list bct_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.1295 ] Assuming zero filled SBK key
[   0.1346 ] Sha saved in br_bct_BR.sha
[   0.1352 ] Warning: pub_key.key is not found
[   0.1345 ] Updating BCT with signature
[   0.1366 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesig bct_list_signed.xml
[   0.1384 ] Offset :4608 Len :3584
[   0.1390 ] Generating SHA2 Hash
[   0.1399 ] tegrasign_v3.py --key None --list bct_list.xml --sha sha512
[   0.1402 ] Assuming zero filled SBK key
[   0.1403 ] Assuming zero filled SBK key
[   0.1450 ] Sha saved in br_bct_BR.sha
[   0.1455 ] Updating BCT with SHA2 Hash
[   0.1469 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesha bct_list_signed.xml
[   0.1483 ] Offset :4608 Len :3584
[   0.1488 ] Offset :68 Len :8124
[   0.1490 ] Generating coldboot mb1-bct
[   0.1504 ] 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.1519 ] MB1-BCT version: 0.9

[   0.1545 ] Parsing config file :tegra234-mb1-bct-device-p3701-0000_cpp.dtb 
[   0.1548 ] Added Platform Config 9 data with size :- 80
[   0.1548 ] 
[   0.1548 ] Updating mb1-bct with firmware information
[   0.1557 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_cold_boot_bct_MB1.bct --updatefwinfo readinfo_t234_min_prod.xml.bin
[   0.1582 ] tegrahost_v2 --chip 0x23 0 --align mb1_cold_boot_bct_MB1_aligned.bct
[   0.1608 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --appendsigheader mb1_cold_boot_bct_MB1_aligned.bct zerosbk
[   0.1620 ] adding BCH for mb1_cold_boot_bct_MB1_aligned.bct
[   0.1635 ] tegrasign_v3.py --key None --list mb1_cold_boot_bct_MB1_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.1637 ] Assuming zero filled SBK key
[   0.1655 ] Warning: pub_key.key is not found
[   0.1672 ] 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.1701 ] Generating recovery mb1-bct
[   0.1714 ] 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.1729 ] MB1-BCT version: 0.9

[   0.1753 ] Parsing config file :tegra234-mb1-bct-device-p3701-0000_cpp.dtb 
[   0.1756 ] Added Platform Config 9 data with size :- 80
[   0.1756 ] 
[   0.1757 ] Updating mb1-bct with firmware information
[   0.1773 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_bct_MB1.bct --recov --updatefwinfo readinfo_t234_min_prod.xml.bin
[   0.1813 ] tegrahost_v2 --chip 0x23 0 --align mb1_bct_MB1_aligned.bct
[   0.1843 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --appendsigheader mb1_bct_MB1_aligned.bct zerosbk
[   0.1857 ] adding BCH for mb1_bct_MB1_aligned.bct
[   0.1876 ] tegrasign_v3.py --key None --list mb1_bct_MB1_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.1879 ] Assuming zero filled SBK key
[   0.1912 ] Warning: pub_key.key is not found
[   0.1920 ] tegrahost_v2 --chip 0x23 0 --updatesigheader mb1_bct_MB1_aligned_sigheader.bct.encrypt mb1_bct_MB1_aligned_sigheader.bct.hash zerosbk
[   0.1941 ] Error: Skip generating mem_bct because sdram_config is not defined
[   0.1941 ] Error: Skip generating mem_bct because sdram_config is not defined
[   0.1941 ] Copying signatures
[   0.1953 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
[   0.2036 ] mb1_t234_prod_aligned_sigheader.bin.encrypt filename is from images_list
[   0.2040 ] psc_bl1_t234_prod_aligned_sigheader.bin.encrypt filename is from images_list
[   0.2040 ] Boot Rom communication
[   0.2060 ] 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.2076 ] BR_CID: 0x80012344705DD45F500000000D0082C0
[   0.2344 ] Sending bct_br
[   0.2774 ] 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.

I know there are a bunch of similar issues here but they are all lengthy discussion and none really had a direct simple solution.

I tried this with two different Orin AGX, two different cables, two different USB-A to USB-C converters, allways the same result. I don’t have random computers laying around so I can’t test with a different host.

Any help would be welcome.

Edit: Here the logs from the sdk. I just tried to completely reinstall the sdk and still same issue.
SDKM_logs_JetPack_5.0.2_Runtime_(rev._1)_Linux_for_Jetson_AGX_Orin_modules_2022-12-12_14-32-59.zip (45.5 KB)

Hi,

1.Please also check if you can dump the serial console log.

  1. I guess you are using ubuntu 20.04 and it seems a specific kernel version of ubuntu 20.04 would hit this issue.
    https://forums.developer.nvidia.com/t/usb-timeout-when-flashing-agx-orin/235600/14?u=waynewww

I just checked with another host, also with Ubuntu20.04, set up from scratch with all updates installed. Same error, so I think this might be affecting every system on that version?

I updated to Ubuntu22.04 hoping the kernel would be fixed, but I guess Ubuntu22.04 is not supported with the SDKmanager, and the flash.sh script failed the same way.

I tried to play around with minicom earlier, but I couldn’t figure out how to get any logs. I am connected with USB-C and the /dev/ttyACM0 only shows up when the Orin boots to it’s normal install. I think some more extensive explanations would be useful, if you guys request logs from everybody, just that article is not telling me anything about how to get the logs.

I could try the docker images, but I suspect I will still hit the same issue, as the kernel is shared. Any suggestions?

yeah same issue as mentioned in the other post:

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04.5 LTS
Release: 20.04
Codename: focal
$ uname -a
Linux marco-XPS-13 5.14.0-1054-oem #61-Ubuntu SMP Fri Oct 14 13:05:50 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

I guess we can close this if you guys prefer, but I definitely would like to see a way of making this work in the other thread then. Only thing I can think of is downgrading the kernel, but not even sure how far and honestly that is a pretty bad solution.

I tried to play around with minicom earlier, but I couldn’t figure out how to get any logs. I am connected with USB-C and the /dev/ttyACM0 only shows up when the Orin boots to it’s normal install. I think some more extensive explanations would be useful, if you guys request logs from everybody, just that article is not telling me anything about how to get the logs.

Hi, sorry that I forgot to clarify that. Actually only the micro usb port has the capability to dump log prior to kernel. For example, bootloader side log.

Flash log is also only available to this port. Not type C.

Also, another kernel version of ubuntu20.04 that we have validated is 5.15.0-53-generic.

Thanks for these information. I just tried with that kernel version and I got the same issue:

$ uname -a
Linux marco-XPS-13 5.15.0-53-generic #59~20.04.1-Ubuntu SMP Thu Oct 20 15:10:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
$ sudo ./flash.sh jetson-agx-orin-devkit mmcblk0p1
###############################################################################
# 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/marco/nvidia/nvidia_sdk/JetPack_5.0.2_Runtime_Linux_Runtime_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-br-bct-diag-boot.dts)... done.
copying device_config(/home/marco/nvidia/nvidia_sdk/JetPack_5.0.2_Runtime_Linux_Runtime_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-mb1-bct-device-p3701-0000.dts)... done.
copying misc_config(/home/marco/nvidia/nvidia_sdk/JetPack_5.0.2_Runtime_Linux_Runtime_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-mb1-bct-misc-p3701-0000.dts)... done.
./tegraflash.py --chip 0x23 --applet "/home/marco/nvidia/nvidia_sdk/JetPack_5.0.2_Runtime_Linux_Runtime_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 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.0106 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[   0.0121 ] File rcm_state open failed
[   0.0126 ] ERROR: failed to read rcm_state
[   0.0126 ] 
[   0.0138 ] tegrasign_v3.py --key None --getmode mode.txt
[   0.0142 ] Assuming zero filled SBK key
[   0.0134 ] Pre-processing config: tegra234-mb1-bct-device-p3701-0000.dts
[   0.0236 ] Pre-processing config: tegra234-mb1-bct-misc-p3701-0000.dts
[   0.0380 ] Parsing partition layout
[   0.0400 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[   0.0433 ] Parsing partition layout
[   0.0451 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[   0.0474 ] Creating list of images to be signed
[   0.0493 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --list images_list.xml zerosbk
[   0.0613 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin
[   0.0619 ] Header already present for mb1_t234_prod_aligned_sigheader.bin
[   0.0623 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin
[   0.0667 ] Header already present for mb1_t234_prod_aligned_sigheader.bin
[   0.0673 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin
[   0.0742 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin
[   0.0748 ] adding BCH for mb2_t234_aligned.bin
[   0.0797 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin
[   0.1076 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin
[   0.1081 ] adding BCH for mb2_t234_aligned.bin
[   0.1387 ] Generating signatures
[   0.1399 ] tegrasign_v3.py --key None --list images_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.1403 ] Assuming zero filled SBK key
[   0.1716 ] Warning: pub_key.key is not found
[   0.1711 ] Parsing dev params for multi chains
[   0.1848 ] Generating br-bct
[   0.1933 ] Updating dev and MSS params in BR BCT
[   0.1935 ] tegrabct_v2 --dev_param tegra234-br-bct-diag-boot_cpp.dtb --brbct br_bct.cfg --chip 0x23 0
[   0.1957 ] Updating bl info
[   0.1977 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updateblinfo readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
[   0.1993 ] WARNING: boot chain is not completed. set to 0
[   0.2011 ] Get Signed section of bct
[   0.2029 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --listbct bct_list.xml
[   0.2048 ] Signing BCT
[   0.2060 ] tegrasign_v3.py --key None --list bct_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.2064 ] Assuming zero filled SBK key
[   0.2115 ] Sha saved in br_bct_BR.sha
[   0.2121 ] Warning: pub_key.key is not found
[   0.2111 ] Updating BCT with signature
[   0.2127 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesig bct_list_signed.xml
[   0.2140 ] Offset :4608 Len :3584
[   0.2146 ] Generating SHA2 Hash
[   0.2158 ] tegrasign_v3.py --key None --list bct_list.xml --sha sha512
[   0.2161 ] Assuming zero filled SBK key
[   0.2161 ] Assuming zero filled SBK key
[   0.2223 ] Sha saved in br_bct_BR.sha
[   0.2222 ] Updating BCT with SHA2 Hash
[   0.2251 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesha bct_list_signed.xml
[   0.2286 ] Offset :4608 Len :3584
[   0.2296 ] Offset :68 Len :8124
[   0.2304 ] Generating coldboot mb1-bct
[   0.2323 ] 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.2344 ] MB1-BCT version: 0.9

[   0.2375 ] Parsing config file :tegra234-mb1-bct-device-p3701-0000_cpp.dtb 
[   0.2379 ] Added Platform Config 9 data with size :- 80
[   0.2379 ] 
[   0.2380 ] Updating mb1-bct with firmware information
[   0.2397 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_cold_boot_bct_MB1.bct --updatefwinfo readinfo_t234_min_prod.xml.bin
[   0.2442 ] tegrahost_v2 --chip 0x23 0 --align mb1_cold_boot_bct_MB1_aligned.bct
[   0.2578 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --appendsigheader mb1_cold_boot_bct_MB1_aligned.bct zerosbk
[   0.2598 ] adding BCH for mb1_cold_boot_bct_MB1_aligned.bct
[   0.2631 ] tegrasign_v3.py --key None --list mb1_cold_boot_bct_MB1_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.2635 ] Assuming zero filled SBK key
[   0.2665 ] Warning: pub_key.key is not found
[   0.2677 ] 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.2706 ] Generating recovery mb1-bct
[   0.2723 ] 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.2740 ] MB1-BCT version: 0.9

[   0.2766 ] Parsing config file :tegra234-mb1-bct-device-p3701-0000_cpp.dtb 
[   0.2770 ] Added Platform Config 9 data with size :- 80
[   0.2770 ] 
[   0.2771 ] Updating mb1-bct with firmware information
[   0.2786 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_bct_MB1.bct --recov --updatefwinfo readinfo_t234_min_prod.xml.bin
[   0.2829 ] tegrahost_v2 --chip 0x23 0 --align mb1_bct_MB1_aligned.bct
[   0.2963 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --appendsigheader mb1_bct_MB1_aligned.bct zerosbk
[   0.2986 ] adding BCH for mb1_bct_MB1_aligned.bct
[   0.3018 ] tegrasign_v3.py --key None --list mb1_bct_MB1_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.3022 ] Assuming zero filled SBK key
[   0.3056 ] Warning: pub_key.key is not found
[   0.3067 ] tegrahost_v2 --chip 0x23 0 --updatesigheader mb1_bct_MB1_aligned_sigheader.bct.encrypt mb1_bct_MB1_aligned_sigheader.bct.hash zerosbk
[   0.3096 ] Error: Skip generating mem_bct because sdram_config is not defined
[   0.3097 ] Error: Skip generating mem_bct because sdram_config is not defined
[   0.3097 ] Copying signatures
[   0.3114 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
[   0.3258 ] mb1_t234_prod_aligned_sigheader.bin.encrypt filename is from images_list
[   0.3263 ] psc_bl1_t234_prod_aligned_sigheader.bin.encrypt filename is from images_list
[   0.3264 ] Boot Rom communication
[   0.3290 ] 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.3308 ] BR_CID: 0x80012344705DD45F500000000D0082C0
[   0.3598 ] Sending bct_br
[   0.4011 ] 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.

So maybe it is not a kernel issue after all, but an issue with the XPS13 laptops. Both of the hosts I tested are from that brand. I can try to get the logs tomorrow, I don’t have a micro USB here.

Here the log during normal startup and during flashing. Hope that helps figuring out what is going on here. Would be really great if I could flash the Orin.

By the way I just remembered I used the same computer in the past to flash other Jetson devices, although through the micro usb port. So in theory it should work.

minicom_flash.cap (25.1 KB)
minicom_startup.cap (81.1 KB)

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

Not really. The current status of this issue is, according to my understanding, that the flashing script is hitting a kernel issue that prevents anybody from flashing a Orin over USB-C with any of the dell laptops, as they require a custom kernel, with that particular issue present. I tried:

  • Using a different kernel, which didn’t work, I assume, because the standard kernel can not properly communicate with the dell USB-C module.
  • Using Ubuntu 22.04 (I need to check if there is an updated kernel available), with the flash script, same issue.

I don’t have a none dell laptop available, so I won’t be able to flash any of the Orin we have, I can work with the off the shelf installation on these, but it is not great to not being able to check if I can deploy our software stack from scratch.

I am experiencing what looks to be the same problem, unable to flash our Orin modules on kernel 5.15.0-56-generic, we are looking into downgrading; however, it’s clear the time involved is going to cause us to miss our project deadlines.

@manbehindthemadness This seems to be the kernel version that comes with ubuntu 22.04 and as mentioned earlier, it seems to have the same issue, at least on a XPS13, probably all Dell laptops.

Weird, I’m using an olllllllllld-ass MacBook Pro 17in as it is the only non production system I have

Interesting, so far I assumed that this problem is restricted to dell computers, as the above mentioned issue was on a Precision and I have XPS’s, but that might indicate that it is a bigger issue.

I suspect it’s the usb bus hardware itself, I have had some inconsistent behavior with various USB 3 devices running on usb 2 that could easily qualify as an x-file