Bootburn on the SoC is failing

DRIVE OS Version: Provide DRIVE OS version. Example: 7.0.3

Issue Description:
Hello,

We are using Nvidia thor hardware, and trying to perform bootburn on the SoC.

for bootburn process we are following steps mentioned by nvidia in the link below

In the Minicom shell we enter into Recovery Mode
tegrarecovery x1 on
tegrareset x1

And then from the Docker terminal we are executing below commands
cd /drive/drive-foundation/tools/flashtools/bootburn
python3 bootburn.py -b p3960-10-sw01 -l -u pct-bin kernel-dtb

but we are facing issue
*ERROR: Failed to create hpse_t264 pkg due to /drive/drive-foundation/security/spvault/out/nvidia/spvault/conf-blob/t26x/spvault-hpse-oem-conf.bin is not found.
*
We need to know why is this failing and is there any additional things we need perform.?

Complete Logs:

root@7.0.3.0-0010-linux-nsr:/drive/drive-foundation/tools/flashtools/bootburn# python3 bootburn.py -b p3960-10-sw01 -l -u pct-bin kernel-dtb
********* Starting bootburn/bootburn.py *********
Command Line Arguments :: [‘bootburn.py’, ‘-b’, ‘p3960-10-sw01’, ‘-l’, ‘-u’, ‘pct-bin’, ‘kernel-dtb’]
2026-01-20 15:33:02,461 - INFO - Initializing SOC group selector
2026-01-20 15:33:02,462 - INFO - Found SOC group for board p3960-10-sw01
********* Starting t264 bootburn py ********
Bootburn Starting with arguments [‘bootburn.py’, ‘-b’, ‘p3960-10-sw01’, ‘-l’, ‘-u’, ‘pct-bin’, ‘kernel-dtb’]
Default Schema:/drive/drive-foundation/tools/flashtools/bootburn_t264_py/nv-customer-data-schema.json

cwd in setBoardConfigPath :: /drive/drive-foundation/tools/flashtools/bootburn_t264_py
cwd in loadBoardGoldenRegsFile :: /drive/drive-foundation/tools/flashtools/bootburn_t264_py
Check finished successfully
Done parsing command line

[bootburn]: [executeShellCommand(155)] : command = whoami
cwd = /drive/drive-foundation/tools/flashtools/bootburn_t264_py
[bootburn]: [executeShellCommand(162)] : root

[bootburn]: [getListTargetsInRecovery(3570)] : Bus 001 Device 012: ID 0955:7026 NVIDIA Corp. APX
[bootburn]: [getListTargetsInRecovery(3570)] : Bus 001 Device 002: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
p3960-10-sw01
Default Schema:/drive/drive-foundation/tools/flashtools/bootburn_t264_py/nv-customer-data-schema.json

cwd in setBoardConfigPath :: /drive/drive-foundation/tools/flashtools/bootburn_t264_py
cwd in loadBoardGoldenRegsFile :: /drive/drive-foundation/tools/flashtools/bootburn_t264_py
Check finished successfully
Done parsing command line

[bootburndie0]: [executeShellCommand(155)] : command = whoami
cwd = /drive/drive-foundation/tools/flashtools/bootburn_t264_py
[bootburndie0]: [executeShellCommand(162)] : root

[bootburndie0]: [GetTargetECID(784)] : Target BR_CID: 0x80012641783DC0C908000000170301C0

[bootburndie0]: [GetTargetECID(785)] : Target ECID: 0x1783DC0C908000000170301C0

[bootburndie0]: [GenAdbSerialNum(551)] : ADB serial number is 2U1TO34GG00000BG60E0
[bootburndie0]: [CheckForDeviceType(882)] : Detected ES production device type

In BoardSetFilePathsAndDefaultValues in targetConfig

n_FlashFirmware is set to True

In BoardSetFilePathsAndDefaultValues in targetConfig

n_FlashFirmware is set to True
[bootburndie0]: creating and flashing coldboot images
[bootburndie0]: [Boot_Create_Flash_Coldboot(1439)] : Creating & Flashing images
[bootburndie0]: Creating rcm-flash images
[bootburndie0]: [Boot_Create_Flash_Coldboot(1442)] : flashingCFG :: /drive/drive-foundation/tools/flashtools/flashing_kernel/flashing_configs/t264/quickboot_flashing.cfgself.targetConfig.p_OutDirPath :: /drive/drive-foundation/tools/flashtools/bootburn_t264_py/__temp_t264/die0-13c15cd36cc
/drive/drive-foundation/tools/flashtools/bootburn_t264_py/__temp_t264/die0-13c15cd36cc/rcm-flash/tegrasign_v3_internal.py:1339: SyntaxWarning: invalid escape sequence ‘\d’
m = re.search(‘Key size is (\d+)’, ret_str)
/drive/drive-foundation/tools/flashtools/bootburn_t264_py/__temp_t264/die0-13c15cd36cc/rcm-flash/tegrasign_v3_internal.py:1385: SyntaxWarning: invalid escape sequence ‘\d’
m = re.search(‘Key size is (\d+)’, ret_str)
/drive/drive-foundation/tools/flashtools/bootburn_t264_py/_temp_t264/die0-13c15cd36cc/rcm-flash/tegrasign_v3_internal.py:1752: SyntaxWarning: invalid escape sequence ‘\d’
re_string = 'kdf_args
’ + temp_stem + ‘(\d).yaml’
/drive/drive-foundation/tools/flashtools/bootburn_t264_py/__temp_t264/die0-13c15cd36cc/rcm-flash/tegrasign_v3_util.py:158: SyntaxWarning: invalid escape sequence ‘\d’
m = re.search(‘[1]+’, arg)
command line used was:
[‘bootburn.py’, ‘-b’, ‘p3960-10-sw01’, ‘-l’, ‘-u’, ‘pct-bin’, ‘kernel-dtb’]

ERROR: Failed to create hpse_t264 pkg due to /drive/drive-foundation/security/spvault/out/nvidia/spvault/conf-blob/t26x/spvault-hpse-oem-conf.bin is not found

Exception 8 raised in bootburn_active
Traceback (most recent call last):
File “/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t264_py/bootburn.py”, line 144, in bootburn_active
bootburnThor.Boot_Create_Flash_Coldboot()
File “/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t264_py/bootburn_thor.py”, line 1445, in Boot_Create_Flash_Coldboot
self.CreateVDKImages(flashingCFG, self.targetConfig.p_OutDirPath, “rcm-flash”)
File “/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t264_py/bootburn_thor.py”, line 878, in CreateVDKImages
self.GenerateImage(self.storageCfgParser.cfgFileList, l_Operation, operationPath)
File “/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t264_py/bootburn_lib.py”, line 1919, in GenerateImage
self.GenerateHpseSbPkg(l_Image, p_TempDumpPath, chain)
File “/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t264_py/bootburn_thor.py”, line 631, in GenerateHpseSbPkg
raise AbnormalTermination(“ERROR: Failed to create %s pkg due to %s is not found” %(pkg, f_OespBinAbs),
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t264_py/flashtools_nverror.py”, line 261, in AbnormalTermination
raise OSError(errorCode)
OSError: 8
root@7.0.3.0-0010-linux-nsr:/drive/drive-foundation/tools/flashtools/bootburn#


  1. \d ↩︎

Dear @swapnil.langarkande ,
Is it like you want to flash DRIVE OS 7.0.3 to target or you wants to flash any customizations ?
Is the board variant p3960-10-sw01?
Could you verify board variant from part number Requirements for Development Environments — NVIDIA DriveOS 7.0 Linux Installation Guide

Hi @SivaRamaKrishnaNV ,

We have started with flashing DRIVE OS 7.0.3 to the target. The board variant we are using is p3960-10-sw03 and the part number is 940-63960-0010-000.

Best Regards,

Shashidhar

Dear @shashidhar.kasoju.pb1 , @swapnil.langarkande ,
May I know if both are working together on same issue?
Is the issue resolved?

Hello @SivaRamaKrishnaNV
Yes myself and @shashidhar.kasoju.pb1 we both work together in a same team and on same issue.
Issue is not yet resolved.

Regards
Swapnil

Dear @swapnil.langarkande @shashidhar.kasoju.pb1 ,
Does normal flashing command work(./bootburn.py -b <board_variant> -x /dev/ttyACM2 when board is in normal mode) ?

Could you please share the used bind and flash commands and logs for p3960-10-sw03?
Is the board in recovery mode or normal mode before running your commands?

@swapnil.langarkande could you please check my private message?

Hello @SivaRamaKrishnaNV

Based on your suggestion in previous message I tried flashing command in normal mode (BOard is in normal mode) Still we are facing issue. I am adding logs below

Logs:
********* Starting bootburn/bootburn.py *********
Command Line Arguments :: [‘./bootburn.py’, ‘-b’, ‘p3960-10-sw03’, ‘-x’, ‘/dev/ttyACM2’]
********* Starting t264 bootburn py ********
Bootburn Starting with arguments [‘./bootburn.py’, ‘-b’, ‘p3960-10-sw03’, ‘-x’, ‘/dev/ttyACM2’]
Default Schema:/drive/drive-foundation/tools/flashtools/bootburn_t264_py/nv-customer-data-schema.json

cwd in setBoardConfigPath :: /drive/drive-foundation/tools/flashtools/bootburn_t264_py
cwd in loadBoardGoldenRegsFile :: /drive/drive-foundation/tools/flashtools/bootburn_t264_py
Check finished successfully
Done parsing command line

[bootburn]: [executeShellCommand(155)] : command = whoami
cwd = /drive/drive-foundation/tools/flashtools/bootburn_t264_py
[bootburn]: [executeShellCommand(162)] : root

[bootburn]: [GetInfoRom(599)] : Read skuinfo from InfoRom…
[bootburn]: Execute command on Aurix serial port
[bootburn]: [ParseInfoRom_Print(673)] : Product Part Number: 670-63960-0010-000
[bootburn]: [getListTargetsInRecovery(3570)] : Bus 001 Device 008: ID 0955:7026 NVIDIA Corp. APX
[bootburn]: [getListTargetsInRecovery(3570)] : Bus 001 Device 002: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[bootburn]: [GetTegrasAssocWithAurix(514)] : Setting Tegra-A in recovery…
[bootburn]: [GetTegrasAssocWithAurix(518)] : Done
[bootburn]: [getListTargetsInRecovery(3570)] : Bus 001 Device 002: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[bootburn]: [GetTegrasAssocWithAurix(532)] : retrying board recovery check…
[bootburn]: [getListTargetsInRecovery(3570)] : Bus 001 Device 009: ID 0955:7026 NVIDIA Corp. APX
[bootburn]: [getListTargetsInRecovery(3570)] : Bus 001 Device 002: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
p3960-10-sw03
Default Schema:/drive/drive-foundation/tools/flashtools/bootburn_t264_py/nv-customer-data-schema.json

cwd in setBoardConfigPath :: /drive/drive-foundation/tools/flashtools/bootburn_t264_py
cwd in loadBoardGoldenRegsFile :: /drive/drive-foundation/tools/flashtools/bootburn_t264_py
Platform config path - /drive/drive-foundation/out/p3960-10-sw03/platform_config.json - does not exist

Platform config file not found – not overiding values
Check finished successfully
Done parsing command line

[bootburnTegra-A]: [executeShellCommand(155)] : command = whoami
cwd = /drive/drive-foundation/tools/flashtools/bootburn_t264_py
[bootburnTegra-A]: [executeShellCommand(162)] : root

Platform config path - /drive/drive-foundation/out/p3960-10-sw03/platform_config.json - does not exist

Platform config file not found – not overiding values
[bootburnTegra-A]: [GetTargetECID(784)] : Target BR_CID: 0x80012641783DE205240000000A028100

[bootburnTegra-A]: [GetTargetECID(785)] : Target ECID: 0x1783DE205240000000A028100

[bootburnTegra-A]: [GenAdbSerialNum(551)] : ADB serial number is 2U1TS82I800000505080
[bootburnTegra-A]: [CheckForDeviceType(882)] : Detected ES production device type

In BoardSetFilePathsAndDefaultValues in targetConfig

n_FlashFirmware is set to True
command line used was:
[‘./bootburn.py’, ‘-b’, ‘p3960-10-sw03’, ‘-x’, ‘/dev/ttyACM2’]

e[01;31mBind partitions does not look to have been run for board p3960-10-sw03
please make bind partitions before running bootburne[0m

e[01;31mException 4 raised in bootburn_active e[0m

This indicates the bind_partitions command did not use p3960-10-sw03 before running bootburn

Could you please provide any update for this topic?

Dear @swapnil.langarkande @shashidhar.kasoju.pb1 ,
Is the issue resolved? Can we close the topic?

Could you please provide any update for this topic?

I’m closing this topic due to there is no update from you for a period, assuming this issue was resolved.
If still need the support, please open a new topic. Thanks