Cannot flash 7.0.1.0 on drive agx thor u devkit

Autonomous Vehicles DRIVE AGX Thor DRIVE AGX Thor General
, , , ,
1

Please provide the following info (tick the boxes after creating this topic):

Software Version
[*] DRIVE OS 7.0.3
other

Target Operating System
[*] Linux
QNX
other

Hardware Platform
DRIVE AGX Thor Developer Kit (940-63960-0010-000)
DRIVE AGX Thor Developer Kit (940-63960-0012-000)
[*] other

Host Machine Version
[*] native Ubuntu Linux 24.04 Host installed with DRIVE OS Docker Containers
other

Issue Description
<Please provide details about your query/application pipeline/usecase/pictures here>

I want to flash the drive agx thor toolkit use the command:
./bootburn.py -b p3960-10-sw01 --init_persistent_partitions --board_config /drive/drive-foundation/platform-config/hardware/nvidia/platform/t264/automotive/automotive-platform-configs/p3960/p3960-10/p3960-10-sw01/board_configs/p3960-10-sw01_thor_u.json
which is mentioned in NVIDIA DriveOS 7.0 Linux Installation Guide
And I got python os error 43, due to TEGRARCM – Unable to execute command.
I am using the Docker image:
edge.urm.nvidia.com/sw-driveos-linux-docker-local/drive-agx-linux-nsr-aarch64-sdk-build-x86:7.0.1.0-0003

Error String

TEGRARCM – Unable to execute command

Exception 43 raised in bootburn_active
Traceback (most recent call last):
File “/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t264_py/bootburn.py”, line 143, in bootburn_active
bootburnThor.Boot_Create_Flash_Coldboot()
File “/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t264_py/bootburn_thor.py”, line 1243, in Boot_Create_Flash_Coldboot
self.runPlatformDetection(“rcm-flash”, self.targetConfig.p_OutDirPath, l_findBoardOnly=False)
File “/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t264_py/bootburn_thor.py”, line 1151, in runPlatformDetection
self.BootMb2Applet(l_Operation, binaryLocation)
File “/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t264_py/bootburn_thor.py”, line 933, in BootMb2Applet
self.sendRcmCommand(" --chip 0x26 --pollbl --download applet applet/applet_blob.bin")
File “/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t264_py/bootburn_lib.py”, line 760, in sendRcmCommand
AbnormalTermination(“TEGRARCM – Unable to execute command”, nverror.NvError_TegraRcmError)
File “/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t264_py/flashtools_nverror.py”, line 249, in AbnormalTermination
raise OSError(errorCode)
OSError: 43

Logs
Provide logs in text box instead of image.
Please paste the complete application log here. If there are multiple logs, please use multiple text box.

[bootburndie0]: [GenerateImage(1946)] : Generating Flashing-RCM Images
[bootburndie0]: [Boot_Create_Flash_Coldboot(1237)] : Generating cold boot flash-images
[bootburndie0]: [GenerateImage(1972)] : Generating Flash Images for chain A, this may take a few minutes
[bootburndie0]: [GenerateImage(1972)] : Generating Flash Images for chain B, this may take a few minutes
[bootburndie0]: [GenerateImage(1972)] : Generating Flash Images for chain C, this may take a few minutes
[bootburndie0]: [Boot_Create_Flash_Coldboot(1241)] : Booting Flashing Kernel
[bootburndie0]: [runPlatformDetection(1124)] : runPlatformDetection - rcm-flash
[bootburndie0]: [executeShellCommand(169)] : shell command – /drive/drive-foundation/tools/flashtools/flash/tegrarcm_v2 --instance /dev/bus/usb/003/029 --chip 0x26 --pollbl --download applet applet/applet_blob.bin failed
[bootburndie0]: [executeShellCommand(171)] : Output: ERROR: might be timeout in USB read

[bootburndie0]: [executeShellCommand(173)] : Return code: 8
[bootburndie0]: [executeShellCommand(175)] : stdout: b’ERROR: might be timeout in USB read \n’
[bootburndie0]: [executeShellCommand(177)] : stderr: None
[bootburndie0]: [sendRcmCommand(759)] : Unable to execute tegrarcm command – /drive/drive-foundation/tools/flashtools/flash/tegrarcm_v2 --instance /dev/bus/usb/003/029 --chip 0x26 --pollbl --download applet applet/applet_blob.bin
command line used was:
[‘./bootburn.py’, ‘-b’, ‘p3960-10-sw01’, ‘–init_persistent_partitions’, ‘–board_config’, ‘/drive/drive-foundation/platform-config/hardware/nvidia/platform/t264/automotive/automotive-platform-configs/p3960/p3960-10/p3960-10-sw01/board_configs/p3960-10-sw01_thor_u.json’]

TEGRARCM – Unable to execute command

Exception 43 raised in bootburn_active
Traceback (most recent call last):
File “/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t264_py/bootburn.py”, line 143, in bootburn_active
bootburnThor.Boot_Create_Flash_Coldboot()
File “/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t264_py/bootburn_thor.py”, line 1243, in Boot_Create_Flash_Coldboot
self.runPlatformDetection(“rcm-flash”, self.targetConfig.p_OutDirPath, l_findBoardOnly=False)
File “/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t264_py/bootburn_thor.py”, line 1151, in runPlatformDetection
self.BootMb2Applet(l_Operation, binaryLocation)
File “/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t264_py/bootburn_thor.py”, line 933, in BootMb2Applet
self.sendRcmCommand(" --chip 0x26 --pollbl --download applet applet/applet_blob.bin")
File “/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t264_py/bootburn_lib.py”, line 760, in sendRcmCommand
AbnormalTermination(“TEGRARCM – Unable to execute command”, nverror.NvError_TegraRcmError)
File “/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t264_py/flashtools_nverror.py”, line 249, in AbnormalTermination
raise OSError(errorCode)
OSError: 43

4

There is no update from you for a period, assuming this is not an issue anymore.
Hence, we are closing this topic. If need further support, please open a new one.
Thanks ~0826

Dear @xuyj7 ,
Could you please check with your NV Representative if forum is right support channel for you as there were no Thor releases on devzone yet.

General suggestions for the issue

  1. Double check if the board config with bootburn command matches with NVPN of target.
  2. Did you put the target in recovery mode before trying to flash.
  3. Double check the connections between host and target as shared in quick start guide.
6

Dear @xuyj7 ,
We have published DRIVE OS 7.0.3 to Devzone.