AGX ORIN cant be formatted with SDK manger

Hi, I’m currently using an AGX Orin 32 dev kit (I believe) for object detection with YOLO. I previously used the same program with Xavier NX and got it to work without any issues. However, when I tried to use sudo jtop to identify the existence of CUDA on Orin, I encountered an error.

As a result, I decided to format Orin and reinstall everything using SDK Manager, following the steps outlined in this forum post: AGX Orin doesn't see CUDA - #8 by furkankoc22. Unfortunately, I’m encountering some problems and I’m unable to format AGX Orin using SDK Manager to install Jetpack from scratch.

Attached is the log file from SDK Manager for your reference:
SDKM_logs_JetPack_5.1.1_Linux_for_Jetson_AGX_Orin_modules_2023-04-06_17-28-35.zip (349.3 KB)

Can you please help me with this issue?

May I know you’re using VM or host PC with Ubuntu 20.04 OS?

I’m using a host PC with Ubuntu 20.04

Hi up202102680,

17:37:58.351 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_AGX_ORIN_TARGETS: [   0.0209 ] File rcm_state open failed
17:37:58.351 - error: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_AGX_ORIN_TARGETS: [   0.0209 ] ERROR: failed to read rcm_state

From the SDKM flash log, it seems RCM detected failed.
Could you help to select “Manual Setup” and follow the instruction to set your devkit into force recovery mode before flash?


SDKM_logs_JetPack_5.1.1_Linux_for_Jetson_AGX_Orin_modules_2023-04-06_17-28-35.zip (188.9 KB)
i think im doing it correctly

i tryed for a couple more times and found this error

17:20:35 INFO: Flash Jetson Linux - flash: [ 0.1642 ] BR_CID: 0x80012344705DD3C96C00000010000240
17:20:35 INFO: Flash Jetson Linux - flash: [ 0.1648 ] Sending bct_br
17:20:41 ERROR: Flash Jetson Linux - flash: [ 0.1648 ] ERROR: might be timeout in USB write.
17:20:41 ERROR: Flash Jetson Linux - flash: Error: Return value 3
17:20:41 INFO: Flash Jetson Linux - flash: 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
17:20:41 ERROR: Flash Jetson Linux - flash: --- Error: Reading board information failed.
17:20:41 INFO: Flash Jetson Linux - flash: [ Component Install Finished with Error ]
17:20:41 INFO: Flash Jetson Linux - flash: [host] [ 71.79 MB used. Disk Avail: 167.27 GB ]
17:20:41 INFO: Flash Jetson Linux - flash: [ NV_L4T_FLASH_JETSON_LINUX_COMP Install took 6s ]
17:20:41 ERROR: Flash Jetson Linux - flash: command terminated with error
17:20:41 SUMMARY: Flash Jetson Linux - flash: First Error: Installation failed.

SDKM_logs_JetPack_5.1.1_Linux_for_Jetson_AGX_Orin_modules_2023-04-07_17-20-19.zip (244.9 KB)

This is the error causing flash failed.

We found several user having this flash issue on AGX Orin with Ubuntu 20.04.
Could you refer to the following thread and see if it could work?
Help, I bricked my AGX orin 64G - #17 by 2Fry

I´ve tryed what was refered in

but the command sudo ./nvautoflash.sh jetson-agx-orin-devkit-as-jao-32gb.conf gets me this error

*** Checking ONLINE mode ... OK.
*** Checking target board connection ... 1 connections found.
*** Reading ECID ... FUSELEVEL=fuselevel_production hwchipid=0x23 bootauth=NS
*** Reading EEPROM ... NO_ROOTFS=1 "/home/diogo/Downloads/Linux_for_Tegra/flash.sh" --no-flash jetson-agx-orin-devkit mmcblk0p1
###############################################################################
# L4T BSP Information:
# R35 , REVISION: 1.0
###############################################################################
copying emc_fuse_dev_params(/home/diogo/Downloads/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-br-bct-diag-boot.dts)... done.
copying device_config(/home/diogo/Downloads/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-mb1-bct-device-p3701-0000.dts)... done.
copying misc_config(/home/diogo/Downloads/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-mb1-bct-misc-p3701-0000.dts)... done.
./tegraflash.py --chip 0x23 --applet "/home/diogo/Downloads/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.0036 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[   0.0041 ] File rcm_state open failed
[   0.0041 ] ERROR: failed to read rcm_state
[   0.0041 ] 
[   0.0047 ] tegrasign_v3.py --key None --getmode mode.txt
[   0.0048 ] Assuming zero filled SBK key
[   0.0044 ] Pre-processing config: tegra234-mb1-bct-device-p3701-0000.dts
[   0.0084 ] Pre-processing config: tegra234-mb1-bct-misc-p3701-0000.dts
[   0.0133 ] Parsing partition layout
[   0.0140 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[   0.0148 ] Parsing partition layout
[   0.0153 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[   0.0159 ] Creating list of images to be signed
[   0.0167 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --list images_list.xml zerosbk
[   0.0172 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin
[   0.0177 ] Header already present for mb1_t234_prod_aligned_sigheader.bin
[   0.0178 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin
[   0.0197 ] Header already present for mb1_t234_prod_aligned_sigheader.bin
[   0.0200 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin
[   0.0220 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin
[   0.0221 ] adding BCH for mb2_t234_aligned.bin
[   0.0236 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin
[   0.0296 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin
[   0.0297 ] adding BCH for mb2_t234_aligned.bin
[   0.0370 ] Generating signatures
[   0.0376 ] tegrasign_v3.py --key None --list images_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.0377 ] Assuming zero filled SBK key
[   0.0460 ] Warning: pub_key.key is not found
[   0.0456 ] Parsing dev params for multi chains
[   0.0501 ] Generating br-bct
[   0.0509 ] Updating dev and MSS params in BR BCT
[   0.0509 ] tegrabct_v2 --dev_param tegra234-br-bct-diag-boot_cpp.dtb --brbct br_bct.cfg --chip 0x23 0
[   0.0516 ] Updating bl info
[   0.0523 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updateblinfo readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
[   0.0529 ] WARNING: boot chain is not completed. set to 0
[   0.0534 ] Get Signed section of bct
[   0.0540 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --listbct bct_list.xml
[   0.0545 ] Signing BCT
[   0.0551 ] tegrasign_v3.py --key None --list bct_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.0552 ] Assuming zero filled SBK key
[   0.0567 ] Sha saved in br_bct_BR.sha
[   0.0569 ] Warning: pub_key.key is not found
[   0.0564 ] Updating BCT with signature
[   0.0569 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesig bct_list_signed.xml
[   0.0572 ] Offset :4608 Len :3584
[   0.0575 ] Generating SHA2 Hash
[   0.0580 ] tegrasign_v3.py --key None --list bct_list.xml --sha sha512
[   0.0581 ] Assuming zero filled SBK key
[   0.0581 ] Assuming zero filled SBK key
[   0.0595 ] Sha saved in br_bct_BR.sha
[   0.0592 ] Updating BCT with SHA2 Hash
[   0.0598 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesha bct_list_signed.xml
[   0.0603 ] Offset :4608 Len :3584
[   0.0604 ] Offset :68 Len :8124
[   0.0606 ] Generating coldboot mb1-bct
[   0.0611 ] 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.0616 ] MB1-BCT version: 0.9

[   0.0629 ] Parsing config file :tegra234-mb1-bct-device-p3701-0000_cpp.dtb 
[   0.0630 ] Added Platform Config 9 data with size :- 80
[   0.0630 ] 
[   0.0631 ] Updating mb1-bct with firmware information
[   0.0635 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_cold_boot_bct_MB1.bct --updatefwinfo readinfo_t234_min_prod.xml.bin
[   0.0648 ] tegrahost_v2 --chip 0x23 0 --align mb1_cold_boot_bct_MB1_aligned.bct
[   0.0657 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --appendsigheader mb1_cold_boot_bct_MB1_aligned.bct zerosbk
[   0.0661 ] adding BCH for mb1_cold_boot_bct_MB1_aligned.bct
[   0.0671 ] tegrasign_v3.py --key None --list mb1_cold_boot_bct_MB1_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.0672 ] Assuming zero filled SBK key
[   0.0683 ] Warning: pub_key.key is not found
[   0.0686 ] 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.0694 ] Generating recovery mb1-bct
[   0.0699 ] 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.0704 ] MB1-BCT version: 0.9

[   0.0721 ] Parsing config file :tegra234-mb1-bct-device-p3701-0000_cpp.dtb 
[   0.0722 ] Added Platform Config 9 data with size :- 80
[   0.0723 ] Updating mb1-bct with firmware information
[   0.0728 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_bct_MB1.bct --recov --updatefwinfo readinfo_t234_min_prod.xml.bin
[   0.0741 ] tegrahost_v2 --chip 0x23 0 --align mb1_bct_MB1_aligned.bct
[   0.0750 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --appendsigheader mb1_bct_MB1_aligned.bct zerosbk
[   0.0754 ] adding BCH for mb1_bct_MB1_aligned.bct
[   0.0764 ] tegrasign_v3.py --key None --list mb1_bct_MB1_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.0765 ] Assuming zero filled SBK key
[   0.0775 ] Warning: pub_key.key is not found
[   0.0778 ] tegrahost_v2 --chip 0x23 0 --updatesigheader mb1_bct_MB1_aligned_sigheader.bct.encrypt mb1_bct_MB1_aligned_sigheader.bct.hash zerosbk
[   0.0785 ] Error: Skip generating mem_bct because sdram_config is not defined
[   0.0786 ] Error: Skip generating mem_bct because sdram_config is not defined
[   0.0786 ] Copying signatures
[   0.0791 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
[   0.0821 ] mb1_t234_prod_aligned_sigheader.bin.encrypt filename is from images_list
[   0.0822 ] psc_bl1_t234_prod_aligned_sigheader.bin.encrypt filename is from images_list
[   0.0822 ] Boot Rom communication
[   0.0827 ] 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.0834 ] BR_CID: 0x80012344705DD3C96C00000010000240
[   0.1101 ] Sending bct_br
[   0.1529 ] 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.
--- Error: Reading board information failed.

could there be a problem with the hardware, if so how do i fix it?

I´ve tried to flash the orin in a XAVIER NX but still not possible

@KevinFFF you have refered that there have been several people with this problem, how did they fix it ?
shouldn’t it be possible to just flash the ssd?
also I´m going to try a second computer to see if it works like that

Hi,

It seems to be a unstable usb connection issue between host and jetson Orin. We are still not sure why it would happen.

Another user just resolved same issue with no reason last week. He just plugged a usb-ttl cable on its jetson and it can flash again.

Thus, trying another host computer may help here.

@up202102680

If possible, please also dump the serial console log during flash process from the micro usb as this website guiding.

Please be aware that it should use “micro usb” port but not type C port as the page tells.

hi @WayneWWW i was able to reflash it with a conputer newly formated with ubunto 20.04
thanks for all the help
wish u guys luck finding the error and fixing it!

1 Like

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