Jetson Orin NX OS Flash Issue - Board Connection Getting Lost

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin NX
1

I have been trying to flash my Jetson Orin NX-based Avermedia D131L Carrier Board without any success. So far flashing has been tried with SDK manager version 2.0.0 on Ubuntu 18.04, 20.04, and 22.04 respectively. Furthermore, docker image versions of the SDK manager didn’t provide help either. The corresponding SSD for flashing is formatted and clear. The device can only be set to recovery mode from the boot menu. For possible USB connection errors, I have tried 2 different cables. Also, I have tried jetpack 6.0 and 5.1.3.

You can find the log outputs in the attachment. When all processes are complete, the device loses connection during the OS flashing part, and the host machine cannot read the board information, as observed.

10:34:09.432 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: [   0.1960 ] Warning: pub_key.key is not found
10:34:09.433 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: [   0.1896 ] tegrahost_v2 --chip 0x23 0 --updatesigheader mb1_bct_MB1_aligned_sigheader.bct.encrypt mb1_bct_MB1_aligned_sigheader.bct.hash zerosbk
10:34:09.433 - error: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: [   0.1911 ] Error: Skip generating mem_bct because sdram_config is not defined
10:34:09.433 - info: Event: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS - error is: [   0.1911 ] Error: Skip generating mem_bct because sdram_config is not defined
10:34:09.433 - error: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: [   0.1911 ] Error: Skip generating mem_bct because sdram_config is not defined
10:34:09.434 - info: Event: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS - error is: [   0.1911 ] Error: Skip generating mem_bct because sdram_config is not defined
10:34:09.434 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: [   0.1911 ] Copying signatures
10:34:09.434 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: [   0.1920 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
10:34:09.434 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: [   0.1977 ] Boot Rom communication
10:34:09.434 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: [   0.1985 ] 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
10:34:09.435 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: [   0.1996 ] BR_CID: 0x80012344705DE44D780000000DFF0200
10:34:09.476 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: [   0.2287 ] Sending bct_br
10:34:14.608 - error: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: [   0.2721 ] ERROR: might be timeout in USB write.
10:34:14.608 - info: Event: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS - error is: [   0.2721 ] ERROR: might be timeout in USB write.
10:34:14.621 - error: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: Error: Return value 3
10:34:14.621 - info: Event: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS - error is: Error: Return value 3
10:34:14.622 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: 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
10:34:14.630 - error: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: --- Error: Reading board information failed.
10:34:14.631 - info: Event: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS - error is: --- Error: Reading board information failed.
10:34:14.633 - error: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: *** ERROR: Parsing boardid failed
10:34:14.633 - info: Event: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS - error is: *** ERROR: Parsing boardid failed
10:34:14.633 - error: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: [exec_command]: /bin/bash -c /tmp/tmp_NV_L4T_FLASH_JETSON_LINUX_COMP.msb.sh; [error]: *** ERROR: Parsing boardid failed
10:34:14.634 - info: Event: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS - error is: [exec_command]: /bin/bash -c /tmp/tmp_NV_L4T_FLASH_JETSON_LINUX_COMP.msb.sh; [error]: *** ERROR: Parsing boardid

SDKM_logs_JetPack_5_1_3_Linux_for_Jetson_Orin_NX_modules_2024_02.zip (130.6 KB)

1 Like
2

Custom board is not able to get flashed with sdkmanager. Need to use the BSP provided by the vendor.

Sdkmanager is only for NV developer kit.

3

You are correct but the provider also redirect to nvidia website for BSP. Please check the below image and the link;

image
image3040×796 132 KB

4

One weird situation is your flash log said you are trying to flash Orin AGX. But sounds like your board is Orin NX?

5

How did you assume as AGX? the log also shows as NX version.

7

I just retried to flash with SDK Manager 1.9.3 and same output. Here is the latest SDK Manager logs.
SDKM_logs_JetPack_5_1_2_Linux_for_Jetson_Orin_NX_modules_2024_02.zip (120.7 KB)

8

Because I know the meaning in the flash log.

Your log has this line. But p3701 is Orin AGX id.

[ 0.1527 ] 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

If this is Orin NX/Nano, you shall see something like below as p3767 is the id for Orin NX/Nano…

[ 1.0534 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_cold_boot_bct.cfg --misc tegra234-mb1-bct-misc-p3767-0000_cpp.dtb --device tegra234-mb1-bct-device-p3767-0000_cpp.dtb

9

One question here, did you ever flash this module before or not? I mean is this device a fresh one or you/someone else has flashed it before?

10

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