Jetson Thor Flashing finished Unsuccessfully

Robotics & Edge Computing Jetson & Embedded Systems Jetson Thor
1

When Thor uses scripts to flash an external NVMe on a custom carrier board, the following error occurs:

ERROR: might be timeout in USB write.

[flash_bsp_jetson-t264_die0]: [executeShellCommand(175)] : Return code: 3
[flash_bsp_jetson-t264_die0]: [executeShellCommand(177)] : stdout: b’Sending blob\nERROR: might be timeout in USB write.\n’
[flash_bsp_jetson-t264_die0]: [executeShellCommand(179)] : stderr: None
[flash_bsp_jetson-t264_die0]: [sendRcmCommand(774)] : Unable to execute tegrarcm command – /home/hxl/work/nvidia/R38.2/Linux_for_Tegra/unified_flash/out/bsp_images/tools/flashtools/flash/tegrarcm_v2 --instance /dev/bus/usb/001/031 --download blob ./rcm_blob.bin
Traceback (most recent call last):
File “/home/hxl/work/nvidia/R38.2/Linux_for_Tegra/unified_flash/out/bsp_images/tools/flashtools/bootburn/../bootburn_t264_py/flash_bsp_images.py”, line 114, in flash_bsp_active
bootburnThor.BootRCM(“rcm-flash”, binaryLocationPath)
File “/home/hxl/work/nvidia/R38.2/Linux_for_Tegra/unified_flash/out/bsp_images/tools/flashtools/bootburn_t264_py/bootburn_thor.py”, line 1281, in BootRCM
self.sendRcmCommand("–download blob " + blob)
File “/home/hxl/work/nvidia/R38.2/Linux_for_Tegra/unified_flash/out/bsp_images/tools/flashtools/bootburn/../bootburn_t264_py/bootburn_lib.py”, line 775, in sendRcmCommand
AbnormalTermination(“TEGRARCM – Unable to execute command”, nverror.NvError_TegraRcmError)
File “/home/hxl/work/nvidia/R38.2/Linux_for_Tegra/unified_flash/out/bsp_images/tools/flashtools/bootburn/../bootburn_t264_py/flashtools_nverror.py”, line 260, in AbnormalTermination
raise OSError(errorCode)
OSError: 43
command line used was:
[‘/home/hxl/work/nvidia/R38.2/Linux_for_Tegra/unified_flash/out/bsp_images/tools/flashtools/bootburn/flash_bsp_images.py’, ‘-b’, ‘jetson-t264’, ‘–l4t’, ‘-D’, ‘-P’, ‘/home/hxl/work/nvidia/R38.2/Linux_for_Tegra/unified_flash/out/bsp_images/flash_workspace’, ‘–usb-instance’, ‘1-7.2’]

TEGRARCM – Unable to execute command

Exception raised in flash BSP ACTIVE
43
[flash_bsp_jetson-t264]: start time = 1764220707.5253398
[flash_bsp_jetson-t264]: end time = 1764220709.7124677
[flash_bsp_jetson-t264]: Total Time = 2.1871278285980225
[flash_bsp_jetson-t264]: Image Flashing took 2.1871278285980225
[flash_bsp_jetson-t264]: Flashing finished Unsuccessfully!!
Cleaning up…

For the complete log and serial port output, please see the attachment.

thor flash uart print.log (41.3 KB)

thor flash.log (342.7 KB)

Execute lsusb**, the result is as follows:**

Bus 002 Device 003: ID 05e3:0612 Genesys Logic, Inc. Hub
Bus 002 Device 002: ID 05e3:0612 Genesys Logic, Inc. Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 046d:c09d Logitech, Inc. G102 LIGHTSYNC Gaming Mouse
Bus 001 Device 026: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Bus 001 Device 012: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 028: ID 0955:7026 NVIDIA Corp. APX
Bus 001 Device 008: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 003: ID 1a2c:600f China Resource Semico Co., Ltd USB Gaming Keyboard
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Execute the flash script with the following command:

sudo ./l4t_initrd_flash.sh jetson-agx-thor-devkit external

3

HI,

Please refer to README_initrd_flash.txt workflow3 thor example.

sudo ADDITIONAL_DTB_OVERLAY_OPT="BootOrderNvme.dtbo" ./l4t_initrd_flash.sh --external-device nvme0n1p1 -c ./tools/kernel_flash/flash_l4t_t264_nvme.xml  --showlogs  jetson-agx-thor-devkit external

Thanks

4

Using this command will produce the same error. likely failed to burn UEFI and NVMe.

Note: The power indicator turns off when the error occurs,

5

Hi,
Did you make any changes to the BRBCT configuration?
Do you have the developer kit to install the SOM and check if the issue occurs?
Thanks.

6

No change.

Install this SOM on the development kit, and it can be normally programmed and booted.

7

The same module and NVMe SSD were placed on the development kit and the custom carrier board, respectively, and burned using the same script command line on the same PC. The burning was successful on the development kit but failed on the custom carrier board.

A comparison of the burning logs revealed several differences, in addition to the error points, as shown in the following figure, with the left side being the custom carrier board and the right side being the development kit carrier board :

1、

image
image1920×471 320 KB

2、

./tegraflash.py --bl uefi_t26x_general.bin --overlay_dtb L4TConfiguration.dtbo,tegra264-p4071-0000+p3834-xxxx-dynamic.dtbo, --bldtb tegra264-p4071-0000+p3834-0008-nv.dtb --applet applet_t264.bin --cmd " sign" --coldboot_pt_layout flash.xml --chip “0x26” --concat_cpubl_bldtb --cpubl uefi_t26x_general.bin –cust_info custinfo_out.bin --coldboot_bct_cfg bct_cfg.xml --rcmboot_bct_cfg rcmboot_bct_cfg.xml --minratchet_config tegra264-mb1-bct-ratchet-p3834-xxxx-p4071-0000.dts --bct_flags_file platform_config_profile.yaml --bins “mb2_bootloader mb2_t264.bin; xusb_fw xusb_t264_prod.bin; pva_fw nvpva_030.fw; dce_fw display-t264-dce.bin; bpmp_fw bpmp_t264-TA1090SA-A1_prod.bin; bpmp_fw_dtb tegra264-bpmp-3834-0008-4071-xxxx.dtb; rce_fw camera-rtcpu-t264-rce.img; eks eks_t264.img; bootloader_dtb tegra264-p4071-0000+p3834-0008-nv.dtb” --bct_backup --boot_chain A --no_pva 0 --ramcode 12

3、

image
image3260×357 90.2 KB

4、

image
image3321×258 65 KB

error point:

[flash_bsp_jetson-t264_die0]: [executeShellCommand(156)] : command = /home/hxl/work/nvidia/R38.2/Linux_for_Tegra/unified_flash/out/bsp_images/tools/flashtools/flash/tegrarcm_v2 --instance /dev/bus/usb/001/013 --download blob ./rcm_blob.bin
cwd = /home/hxl/work/nvidia/R38.2/Linux_for_Tegra/unified_flash/out/bsp_images/flash_workspace/rcm-flash
[flash_bsp_jetson-t264_die0]: [executeShellCommand(171)] : shell command – /home/hxl/work/nvidia/R38.2/Linux_for_Tegra/unified_flash/out/bsp_images/tools/flashtools/flash/tegrarcm_v2 --instance /dev/bus/usb/001/013 --download blob ./rcm_blob.bin failed
[flash_bsp_jetson-t264_die0]: [executeShellCommand(173)] : Output: Sending blob
ERROR: might be timeout in USB write.

[flash_bsp_jetson-t264_die0]: [executeShellCommand(175)] : Return code: 3
[flash_bsp_jetson-t264_die0]: [executeShellCommand(177)] : stdout: b’Sending blob\nERROR: might be timeout in USB write.\n’
[flash_bsp_jetson-t264_die0]: [executeShellCommand(179)] : stderr: None
[flash_bsp_jetson-t264_die0]: [sendRcmCommand(774)] : Unable to execute tegrarcm command – /home/hxl/work/nvidia/R38.2/Linux_for_Tegra/unified_flash/out/bsp_images/tools/flashtools/flash/tegrarcm_v2 --instance /dev/bus/usb/001/013 --download blob ./rcm_blob.bin
Traceback (most recent call last):
File “/home/hxl/work/nvidia/R38.2/Linux_for_Tegra/unified_flash/out/bsp_images/tools/flashtools/bootburn/../bootburn_t264_py/flash_bsp_images.py”, line 114, in flash_bsp_active
bootburnThor.BootRCM(“rcm-flash”, binaryLocationPath)
File “/home/hxl/work/nvidia/R38.2/Linux_for_Tegra/unified_flash/out/bsp_images/tools/flashtools/bootburn_t264_py/bootburn_thor.py”, line 1281, in BootRCM
self.sendRcmCommand("–download blob " + blob)
File “/home/hxl/work/nvidia/R38.2/Linux_for_Tegra/unified_flash/out/bsp_images/tools/flashtools/bootburn/../bootburn_t264_py/bootburn_lib.py”, line 775, in sendRcmCommand
AbnormalTermination(“TEGRARCM – Unable to execute command”, nverror.NvError_TegraRcmError)
File “/home/hxl/work/nvidia/R38.2/Linux_for_Tegra/unified_flash/out/bsp_images/tools/flashtools/bootburn/../bootburn_t264_py/flashtools_nverror.py”, line 260, in AbnormalTermination
raise OSError(errorCode)
OSError: 43
command line used was:
[‘/home/hxl/work/nvidia/R38.2/Linux_for_Tegra/unified_flash/out/bsp_images/tools/flashtools/bootburn/flash_bsp_images.py’, ‘-b’, ‘jetson-t264’, ‘–l4t’, ‘-D’, ‘-P’, ‘/home/hxl/work/nvidia/R38.2/Linux_for_Tegra/unified_flash/out/bsp_images/flash_workspace’, ‘–usb-instance’, ‘1-7.2’]

TEGRARCM – Unable to execute command

Exception raised in flash BSP ACTIVE
43
[flash_bsp_jetson-t264]: start time = 1764293914.8178132
[flash_bsp_jetson-t264]: end time = 1764293918.3234222
[flash_bsp_jetson-t264]: Total Time = 3.5056090354919434
[flash_bsp_jetson-t264]: Image Flashing took 3.5056090354919434
[flash_bsp_jetson-t264]: Flashing finished Unsuccessfully!!
Cleaning up…

8

The same error occurs when flashing the boot firmware using ：sudo ./l4t_initrd_flash.sh --qspi-only jetson-agx-thor-devkit internal