Jetson Orin Dev Kit is not power on

Autonomous Machines Jetson & Embedded Systems Jetson AGX Orin
22

Hello ,

I used Ubuntu 18.04 as per These feedback Jetson AGX Orin Flashing Issues - #30 by david.berger

But still having same error USB TIMEOUT.

Please check lastest log file.

What is the next step to solve the issue ?

###############################################################################

L4T BSP Information:

R35 , REVISION: 6.0

User release: 0.0

###############################################################################
ECID is 0x80012344705DD2E30800000010FE8280

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/troy_user/nvidia/nvidia_sdk/JetPack_5.1.4_Linux_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-br-bct-diag-boot.dts)… done.
copying device_config(/home/troy_user/nvidia/nvidia_sdk/JetPack_5.1.4_Linux_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-mb1-bct-device-p3701-0000.dts)… done.
copying misc_config(/home/troy_user/nvidia/nvidia_sdk/JetPack_5.1.4_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/troy_user/nvidia/nvidia_sdk/JetPack_5.1.4_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.0187 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 0.0194 ] File rcm_state open failed
[ 0.0198 ] ERROR: failed to read rcm_state
[ 0.0198 ]
[ 0.0206 ] tegrasign_v3.py --key None --getmode mode.txt
[ 0.0208 ] Assuming zero filled SBK key
[ 0.0203 ] Pre-processing config: tegra234-mb1-bct-device-p3701-0000.dts
[ 0.0254 ] Pre-processing config: tegra234-mb1-bct-misc-p3701-0000.dts
[ 0.0338 ] Parsing partition layout
[ 0.0347 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[ 0.0362 ] Kernel DTB used: None
[ 0.0362 ] WARNING: dce base dtb is not provided

[ 0.0362 ] Parsing partition layout
[ 0.0370 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[ 0.0382 ] Creating list of images to be signed
[ 0.0390 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --list images_list.xml zerosbk
[ 0.0398 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin
[ 0.0411 ] Header already present for mb1_t234_prod_aligned_sigheader.bin
[ 0.0416 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin
[ 0.0464 ] Header already present for mb1_t234_prod_aligned_sigheader.bin
[ 0.0470 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin
[ 0.0513 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin
[ 0.0520 ] adding BCH for mb2_t234_aligned.bin
[ 0.0540 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin
[ 0.0660 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin
[ 0.0663 ] adding BCH for mb2_t234_aligned.bin
[ 0.0807 ] Filling MB1 storage info
[ 0.0808 ] Parsing dev params for multi chains
[ 0.0862 ] Generating br-bct
[ 0.0870 ] Updating dev and MSS params in BR BCT
[ 0.0871 ] tegrabct_v2 --dev_param tegra234-br-bct-diag-boot_cpp.dtb --brbct br_bct.cfg --chip 0x23 0
[ 0.0882 ] Updating bl info
[ 0.0889 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updateblinfo readinfo_t234_min_prod.xml.bin
[ 0.0897 ] WARNING: boot chain is not completed. set to 0
[ 0.0906 ] Generating signatures
[ 0.0914 ] tegrasign_v3.py --key None --list images_list.xml --pubkeyhash pub_key.key --sha sha512
[ 0.0917 ] Assuming zero filled SBK key
[ 0.1033 ] Warning: pub_key.key is not found
[ 0.1029 ] Parsing dev params for multi chains
[ 0.1029 ] Generating br-bct
[ 0.1037 ] Updating dev and MSS params in BR BCT
[ 0.1038 ] tegrabct_v2 --dev_param tegra234-br-bct-diag-boot_cpp.dtb --brbct br_bct.cfg --chip 0x23 0
[ 0.1048 ] Updating bl info
[ 0.1056 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updateblinfo readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
[ 0.1065 ] WARNING: boot chain is not completed. set to 0
[ 0.1074 ] Get Signed section of bct
[ 0.1084 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --listbct bct_list.xml
[ 0.1094 ] Signing BCT
[ 0.1102 ] tegrasign_v3.py --key None --list bct_list.xml --pubkeyhash pub_key.key --sha sha512
[ 0.1105 ] Assuming zero filled SBK key
[ 0.1131 ] Sha saved in br_bct_BR.sha
[ 0.1135 ] Warning: pub_key.key is not found
[ 0.1129 ] Updating BCT with signature
[ 0.1137 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesig bct_list_signed.xml
[ 0.1145 ] Offset :4608 Len :3584
[ 0.1149 ] Generating SHA2 Hash
[ 0.1157 ] tegrasign_v3.py --key None --list bct_list.xml --sha sha512
[ 0.1159 ] Assuming zero filled SBK key
[ 0.1160 ] Assuming zero filled SBK key
[ 0.1184 ] Sha saved in br_bct_BR.sha
[ 0.1182 ] Updating BCT with SHA2 Hash
[ 0.1189 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesha bct_list_signed.xml
[ 0.1197 ] Offset :4608 Len :3584
[ 0.1200 ] Offset :68 Len :8124
[ 0.1203 ] Generating coldboot mb1-bct
[ 0.1211 ] 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.1218 ] MB1-BCT version: 0.13

[ 0.1235 ] Parsing config file :tegra234-mb1-bct-device-p3701-0000_cpp.dtb
[ 0.1236 ] Added Platform Config 9 data with size :- 100
[ 0.1237 ]
[ 0.1237 ] Updating mb1-bct with firmware information
[ 0.1245 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_cold_boot_bct_MB1.bct --updatefwinfo readinfo_t234_min_prod.xml.bin
[ 0.1265 ] tegrahost_v2 --chip 0x23 0 --align mb1_cold_boot_bct_MB1_aligned.bct
[ 0.1274 ] Generating SHA2 Hash for mb1bct
[ 0.1293 ] Sha saved in mb1_cold_boot_bct_MB1_aligned.sha
[ 0.1305 ] Sha saved in mb1_cold_boot_bct_MB1.sha
[ 0.1306 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --appendsigheader mb1_cold_boot_bct_MB1_aligned.bct zerosbk
[ 0.1314 ] adding BCH for mb1_cold_boot_bct_MB1_aligned.bct
[ 0.1329 ] tegrasign_v3.py --key None --list mb1_cold_boot_bct_MB1_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[ 0.1331 ] Assuming zero filled SBK key
[ 0.1346 ] Warning: pub_key.key is not found
[ 0.1349 ] 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.1362 ] Generating recovery mb1-bct
[ 0.1369 ] 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.1376 ] MB1-BCT version: 0.13

[ 0.1392 ] Parsing config file :tegra234-mb1-bct-device-p3701-0000_cpp.dtb
[ 0.1393 ] Added Platform Config 9 data with size :- 100
[ 0.1393 ]
[ 0.1394 ] Updating mb1-bct with firmware information
[ 0.1403 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_bct_MB1.bct --recov --updatefwinfo readinfo_t234_min_prod.xml.bin
[ 0.1423 ] tegrahost_v2 --chip 0x23 0 --align mb1_bct_MB1_aligned.bct
[ 0.1430 ] Generating SHA2 Hash for mb1bct
[ 0.1449 ] Sha saved in mb1_bct_MB1_aligned.sha
[ 0.1460 ] Sha saved in mb1_bct_MB1.sha
[ 0.1462 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --appendsigheader mb1_bct_MB1_aligned.bct zerosbk
[ 0.1470 ] adding BCH for mb1_bct_MB1_aligned.bct
[ 0.1486 ] tegrasign_v3.py --key None --list mb1_bct_MB1_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[ 0.1488 ] Assuming zero filled SBK key
[ 0.1505 ] Warning: pub_key.key is not found
[ 0.1507 ] tegrahost_v2 --chip 0x23 0 --updatesigheader mb1_bct_MB1_aligned_sigheader.bct.encrypt mb1_bct_MB1_aligned_sigheader.bct.hash zerosbk
[ 0.1520 ] Error: Skip generating mem_bct because sdram_config is not defined
[ 0.1521 ] Error: Skip generating mem_bct because sdram_config is not defined
[ 0.1521 ] Copying signatures
[ 0.1529 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
[ 0.1581 ] Boot Rom communication
[ 0.1591 ] 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.1598 ] BR_CID: 0x80012344705DD2E30800000010FE8280
[ 0.1912 ] Sending bct_br
[ 0.2344 ] Sending mb1
[ 0.2349 ] Sending psc_bl1
[ 0.2468 ] Sending bct_mb1
[ 0.2530 ] Boot Rom communication completed
[ 0.2553 ] tegrahost_v2 --chip 0x23 0 --align applet_t234_aligned.bin
[ 0.2583 ] tegrahost_v2 --chip 0x23 0 --magicid MB2A --appendsigheader applet_t234_aligned.bin zerosbk
[ 0.2599 ] adding BCH for applet_t234_aligned.bin
[ 0.2818 ] tegrasign_v3.py --key None --list applet_t234_aligned_sigheader.bin_list.xml --pubkeyhash pub_key.key --sha sha512
[ 0.2822 ] Assuming zero filled SBK key
[ 0.2869 ] Warning: pub_key.key is not found
[ 0.2882 ] tegrahost_v2 --chip 0x23 0 --updatesigheader applet_t234_aligned_sigheader.bin.encrypt applet_t234_aligned_sigheader.bin.hash zerosbk
[ 0.2921 ] Sending mb2_applet…

[ 0.2941 ] tegrarcm_v2 --chip 0x23 0 --pollbl --download applet applet_t234_sigheader.bin.encrypt
[ 0.2962 ] ERROR: might be timeout in USB read
Error: Return value 8
Command tegrarcm_v2 --chip 0x23 0 --pollbl --download applet applet_t234_sigheader.bin.encrypt
Reading board information failed.

23

Hi @SamSha

Please, check this Quick Start — NVIDIA Jetson Linux Developer Guide 1 documentation just to confirm that you put the board into recovery mode.

For the USB timeout error you could check this Jetson AGX Orin FAQ which points to the Q: I get a USB timeout error during flash Orin. How to resolve that? question.

Hope this helps!
Please, let me know your results!
Regards.

24

Hello Eduardo ,
I tried these commands “sudo -s and echo -1 > /sys/module/usbcore/parameters/autosuspend” on Ubuntu 20.4 and still had USB timout that’s why i used Ubuntu 18.4 and still have the same issue .

The issues are :
1- While Downloading JetPack 5.1.2 from SDK :
12:11:15 INFO: Drivers for Jetson - target_image: start to download Log in | NVIDIA Developer to /home/troy_user/Downloads/nvidia/sdkm_downloads/Jetson_Linux_R35.4.1_aarch64.tbz2

11:05:59 ERROR: Flash Jetson Linux - flash: [ 0.2747 ] ERROR: might be timeout in USB read

11:05:59 ERROR: Flash Jetson Linux - flash: Error: Return value 8

11:05:59 ERROR: Flash Jetson Linux - flash: — Error: Reading board information failed.

11:05:59 ERROR: Flash Jetson Linux - flash: [exec_command]: /bin/bash -c /home/troy_user/.nvsdkm/replays/scripts/JetPack_5.1.4_Linux/NV_L4T_FLASH_JETSON_LINUX_COMP.sh; [error]: — Error: Reading board information failed.

11:05:59 ERROR: command error code: 11

11:05:59 ERROR: Flash Jetson Linux - flash: command terminated with error

11:05:59 SUMMARY: Flash Jetson Linux - flash: First Error: Installation failed.

2- File rcm_state open failed

3- USB timeout

Do you think is a HW issue ?

25

Hi @SamSha

Here are some questions that I would like to ask:

  1. Have you flashed another Jetson device using this Ubuntu host?
  2. Is this a Host Linux PC or a Virtual Machine?
  3. Have you tried flashing by using another USB cable or another Host Linux PC?
26

Please find my response:
1- I tried to flash Nano device through SD card and it worked fine . Didn’t try another Orin Box .
2- Linux PC
3- Yes tried multiple USB-C and got same error.

27

@SamSha

Could please try to get the UART log when flashing?

Also, you could try using a different USB port or different Host Linux PC to check if the issue persists.

28

Hello Eduardo ,

Please find the log captured by UART while flash . I tried different ports and same issue

Screenshot from 2024-10-21 14-09-14
Screenshot from 2024-10-21 14-09-141853×1053 41.4 KB

29

@SamSha

Please, share the logs in a .txt file attached to the meesage

Is that also the log when flashing the board?

30

error_Flashing.zip (779 Bytes)

31

I tested on different laptop and have same failure

33

The error log is more like a hardware problem to me.

Did you ever flash this board successfully before?

34

Yes it was flashed before.

If it HW issue , what will be the next step to define the HW issue and fix it ?

35

Please RMA the device.