Bootburn flash kernel-dtb failed

Autonomous Vehicles DRIVE AGX Orin DRIVE AGX Orin General
1

Please provide the following info (tick the boxes after creating this topic):
Software Version
DRIVE OS 6.0.6
DRIVE OS 6.0.5
DRIVE OS 6.0.4 (rev. 1)
DRIVE OS 6.0.4 SDK
other

Target Operating System
Linux
QNX
other

Hardware Platform
DRIVE AGX Orin Developer Kit (940-63710-0010-D00)
DRIVE AGX Orin Developer Kit (940-63710-0010-C00)
DRIVE AGX Orin Developer Kit (not sure its number)
other

SDK Manager Version
1.9.2.10884
other

Host Machine Version
native Ubuntu Linux 20.04 Host installed with SDK Manager
native Ubuntu Linux 20.04 Host installed with DRIVE OS Docker Containers
native Ubuntu Linux 18.04 Host installed with DRIVE OS Docker Containers
other

I follow the guider as show below:

./tools/flashtools/bootburn/bootburn.py -b p3710-10-s05 -B qspi -d A_1_kernel-dtb
it report the error info bootburn.py: error: argument -d: expected 2 argument(s)
so try it command: ./tools/flashtools/bootburn/bootburn.py -b p3710-10-s05 -B qspi -d A_1_kernel-dtb /drive/drive-foundation/out/p3710-10-s05/tegra234-p3710-0010-a01-linux-driveav-gos_mods.dtb
it report the error that “s_ERROR_OPTION_VALUE_INVALID – option d invalid name”
so I have to change another command:./tools/flashtools/bootburn/bootburn.py -b p3710-10-s05 -B qspi -u A_1_kernel-dtb
it still also report the error info:
ommand line used was:
[‘./tools/flashtools/bootburn/bootburn.py’, ‘-b’, ‘p3710-10-s05’, ‘-B’, ‘qspi’, ‘-u’, ‘A_1_kernel-dtb’]

s_ERROR_TOOL_NVIMAGEGEN

Exception 46 raised in bootburn_active

can you provide the correct the command to flash the kernel-dtb and A_1_kernel ?

2

Dear @binbin.ding,
Could you share the complete log of both commands?

4

1.the first comand log:
./tools/flashtools/bootburn/bootburn.py -b p3710-10-s05 -B qspi -d A_1_kernel-dtb
****** Starting bootburn/bootburn.py ********
Script directory: /drive/drive-foundation/tools/flashtools/bootburn
Parent directory added to path: /drive/drive-foundation/tools/flashtools/bootburn/…
********* Starting t23x bootburn py ********
Bootburn Starting with arguments [‘./tools/flashtools/bootburn/bootburn.py’, ‘-b’, ‘p3710-10-s05’, ‘-B’, ‘qspi’, ‘-d’, ‘A_1_kernel-dtb’]
usage: bootburn.py [-E] [-D] [–asymmetric] [-C] [-B B] [-M] [-L] [-O]
[–merge-chains MERGE_CHAINS [MERGE_CHAINS …]] [-I I I]
[–user USER] [-U U] [-T] [–find_board_name] [-V] [-P P]
[-R] [-Y Y] [-X] [–chain CHAIN] [-e E] [-d D D] [-g G]
[-f] [–encrypt] [-c] [-b B] [-m] [-l] [-o] [-i I [I …]]
[-h] [-k K] [-j] [-u U [U …]] [-t T] [–fpga]
[–headers HEADERS] [-q] [-p P] [-s] [-r R] [-y] [-x X]
[–clean] [–encryption_key ENCRYPTION_KEY]
[–devicetype DEVICETYPE] [–gpuvbios]
[–microsemi8534_fw MICROSEMI8534_FW]
[–marvell9485_fw MARVELL9485_FW] [–logs LOGS]
[–gpuvbios_fw GPUVBIOS_FW]
[–aquantia07b1_fw AQUANTIA07B1_FW] [–disable_uart]
[–customer-data CUSTOMER_DATA [CUSTOMER_DATA …]] [–vdk]
[–board_config BOARD_CONFIG] [–adbSerial ADBSERIAL]
[–fskp-bct-path FSKP_BCT_PATH [FSKP_BCT_PATH …]]
[–toolsonly] [–pytest] [–platform PLATFORM]
[–no_firmware_update]
[–pl_encryption_key PL_ENCRYPTION_KEY] [–safety] [–dev]
[–init_persistent_partitions] [–hsm HSM]
[–filesystem FILESYSTEM]
bootburn.py: error: argument -d: expected 2 argument(s)
returning to directory /drive/drive-foundation
Cleaning up …

2.second command:
./tools/flashtools/bootburn/bootburn.py -b p3710-10-s05 -B qspi -d A_1_kernel-dtb /drive/drive-foundation/out/p3710-10-s05/tegra234-p3710-0010-a01-linux-driveav-gos_mods.dtb
****** Starting bootburn/bootburn.py ********
Script directory: /drive/drive-foundation/tools/flashtools/bootburn
Parent directory added to path: /drive/drive-foundation/tools/flashtools/bootburn/…
********* Starting t23x bootburn py ********
Bootburn Starting with arguments [‘./tools/flashtools/bootburn/bootburn.py’, ‘-b’, ‘p3710-10-s05’, ‘-B’, ‘qspi’, ‘-d’, ‘A_1_kernel-dtb’, ‘/drive/drive-foundation/out/p3710-10-s05/tegra234-p3710-0010-a01-linux-driveav-gos_mods.dtb’]
cwd in setBoardConfigPath :: /drive/drive-foundation/tools/flashtools/bootburn_t23x_py
trying hardware folder:
/drive/drive-foundation/platform-config/hardware/nvidia/platform/t23x/automotive/flashing/board_configs

cwd in loadBoardGoldenRegsFile :: /drive/drive-foundation/tools/flashtools/bootburn_t23x_py
Default Schema:/drive/drive-foundation/tools/flashtools/bootburn_t23x_py/nv-customer-data-schema-orin.json

command line used was:
[‘./tools/flashtools/bootburn/bootburn.py’, ‘-b’, ‘p3710-10-s05’, ‘-B’, ‘qspi’, ‘-d’, ‘A_1_kernel-dtb’, ‘/drive/drive-foundation/out/p3710-10-s05/tegra234-p3710-0010-a01-linux-driveav-gos_mods.dtb’]

s_ERROR_OPTION_VALUE_INVALID – option d invalid name

command line used was:
[‘./tools/flashtools/bootburn/bootburn.py’, ‘-b’, ‘p3710-10-s05’, ‘-B’, ‘qspi’, ‘-d’, ‘A_1_kernel-dtb’, ‘/drive/drive-foundation/out/p3710-10-s05/tegra234-p3710-0010-a01-linux-driveav-gos_mods.dtb’]

Failed to initialize target config

Exception caught in bootburn
Traceback (most recent call last):
File “/drive/drive-foundation/tools/flashtools/bootburn/…/bootburn_t23x_py/bootburn.py”, line 255, in bootburn
cmdParser.initializeTargetConfig(targetConfig, GenericOptions, False)
File “/drive/drive-foundation/tools/flashtools/bootburn/…/bootburn_t23x_py/bootburn_parser.py”, line 203, in initializeTargetConfig
AbnormalTermination(“Failed to initialize target config”, nverror.NvError_ConfigVarNotFound)
File “/drive/drive-foundation/tools/flashtools/bootburn/…/bootburn_t23x_py/flashtools_nverror.py”, line 249, in AbnormalTermination
raise OSError(errorCode)
OSError: 67
returning to directory /drive/drive-foundation
Cleaning up …

  1. third command:
    ./tools/flashtools/bootburn/bootburn.py -b p3710-10-s05 -B qspi -u A_1_kernel-dtb
    log is
    bootburnTegra-A.txt (203.5 KB)
    I see the error said the : nvimagegen Update partition name A_1_kernel-dtb not found and return Error Code 4.
5

Dear @binbin.ding,
Please confirm if the used platform is p3710 or p3663?

6

I confirm that p3710-10-s05, not p3663. u can see the log info description about p3710 . not include any p3663

7

Sorry for the late response, have you managed to get issue resolved or still need the support? Thanks

8

switch to sdk6060 ,not yet supported on the 6040, thanks!

9

So with DRIVE OS 6.0.6, it’s OK now?

11

we modify the script bootborn to achieve flash kernel-dtb partitions.

13

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