Failing to flash single bootchain with a different DRIVEOS

ashwin.nanda · December 3, 2024, 11:37am

Please provide the following info (tick the boxes after creating this topic):
Software Version
[*] DRIVE OS 6.0.10.0
DRIVE OS 6.0.8.1
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-300)
DRIVE AGX Orin Developer Kit (940-63710-0010-200)
DRIVE AGX Orin Developer Kit (940-63710-0010-100)
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
2.1.0
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

Issue Description
Initially both bootchains by default were flashed to 6.0.8.1, however due to CGF display issues, I am trying to flash Bootchain B only (using option --disable-full like flash.py --disable-full /dev/ttyACM1 p3710) so that we can test on latest software.

Bootchain A is kept at DRIVE OS 6.0.8.1, and so Bootchain B is tried to flash to DRIVE OS 6.0.10, however flashing fails for either A and B when trying to flash only one bootchain with DRIVE OS 6.0.10, the following logs are same no matter how I try to flash.

Error String

[2024-12-03 11:32:54,907 root ERROR pdk_bind.py 217 140] Binding of partitions failed ! Check log for more details.
[2024-12-03 11:32:54,908 root DEBUG utilities.py 294 140] ****** Starting bootburn/bootburn.py ********
[2024-12-03 11:32:54,908 root DEBUG utilities.py 294 140] ********* Starting t23x bootburn py ********
[2024-12-03 11:32:54,908 root DEBUG utilities.py 294 140] Bootburn Starting with arguments ['/drive/drive-foundation/tools/flashtools/bootburn/bootburn.py', '--find_board_name', '-x', '/dev/ttyACM1']
[2024-12-03 11:32:54,908 root DEBUG utilities.py 294 140] logfile :: /drive/drive-foundation/tools/flashtools/bootburn_t23x_py/bootburn.txt
[2024-12-03 11:32:54,908 root DEBUG utilities.py 294 140] cwd in setBoardConfigPath :: /drive/drive-foundation/tools/flashtools/bootburn_t23x_py
[2024-12-03 11:32:54,908 root DEBUG utilities.py 294 140]  trying hardware folder:
[2024-12-03 11:32:54,908 root DEBUG utilities.py 294 140] /drive/drive-foundation/platform-config/hardware/nvidia/platform/t23x/automotive/flashing/board_configs
[2024-12-03 11:32:54,908 root DEBUG utilities.py 294 140] 
[2024-12-03 11:32:54,908 root DEBUG utilities.py 294 140] Default Schema:/drive/drive-foundation/tools/flashtools/bootburn_t23x_py/nv-customer-data-schema.json
[2024-12-03 11:32:54,908 root DEBUG utilities.py 294 140] 
[2024-12-03 11:32:54,908 root DEBUG utilities.py 294 140] [bootburn]: [GetInfoRom(620)] : Read skuinfo from InfoRom...
[2024-12-03 11:32:54,908 root DEBUG utilities.py 294 140] [bootburn]: Execute command on Aurix serial port
[2024-12-03 11:32:54,908 root DEBUG utilities.py 294 140] [bootburn]: [CheckFirmwareisAFW(600)] : AFW firmware found
[2024-12-03 11:32:54,908 root DEBUG utilities.py 294 140] [bootburn]: [setTargetConfigt23xInfoRomInfo(720)] : 940-63710-0010-300
[2024-12-03 11:32:54,908 root DEBUG utilities.py 294 140] [bootburn]: [setTargetConfigt23xInfoRomInfo(721)] : None
[2024-12-03 11:32:54,908 root DEBUG utilities.py 294 140] [bootburn]: [setTargetConfigt23xInfoRomInfo(728)] : ******  s_InforomSkuVersion   300
[2024-12-03 11:32:54,908 root DEBUG utilities.py 294 140] [bootburn]: [setTargetConfigt23xInfoRomInfo(729)] : ******  s_InforomProdInfo   940-63710-0010
[2024-12-03 11:32:54,908 root DEBUG utilities.py 294 140] [bootburn]: [findTargetBaseBoardName(767)] : baseBoardName found :: p3710-10-s05
[2024-12-03 11:32:54,909 root DEBUG utilities.py 294 140] [bootburn]: [findBaseBoardName(3907)] : Detected baseboard with default ChipSku  :: p3710-10-s05
[2024-12-03 11:32:54,909 root DEBUG utilities.py 294 140] [bootburn]: [updateFindBoardData(337)] : Connected Board Name details ::  baseBoard name - p3710-10-s05
[2024-12-03 11:32:54,909 root DEBUG utilities.py 294 140] [bootburn]: [GetTegrasAssocWithAurix(507)] : Setting Tegra-A on hold...
[2024-12-03 11:32:54,909 root DEBUG utilities.py 294 140] [bootburn]: [GetTegrasAssocWithAurix(509)] : Done
[2024-12-03 11:32:54,909 root DEBUG utilities.py 294 140] [bootburn]: [getListTargetsInRecovery(3975)] : Bus 003 Device 014: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2024-12-03 11:32:54,909 root DEBUG utilities.py 294 140] [bootburn]: [GetTegrasAssocWithAurix(534)] : Setting Tegra-A in recovery...
[2024-12-03 11:32:54,909 root DEBUG utilities.py 294 140] [bootburn]: [GetTegrasAssocWithAurix(538)] : Done
[2024-12-03 11:32:54,909 root DEBUG utilities.py 294 140] [bootburn]: [getListTargetsInRecovery(3975)] : Bus 003 Device 014: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2024-12-03 11:32:54,909 root DEBUG utilities.py 294 140] [bootburn]: [GetTegrasAssocWithAurix(552)] : retrying board recovery check...
[2024-12-03 11:32:54,909 root DEBUG utilities.py 294 140] [bootburn]: [getListTargetsInRecovery(3975)] : Bus 003 Device 014: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2024-12-03 11:32:54,909 root DEBUG utilities.py 294 140] [bootburn]: [GetTegrasAssocWithAurix(552)] : retrying board recovery check...
[2024-12-03 11:32:54,909 root DEBUG utilities.py 294 140] [bootburn]: [getListTargetsInRecovery(3975)] : Bus 003 Device 014: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2024-12-03 11:32:54,909 root DEBUG utilities.py 294 140] [bootburn]: [GetTegrasAssocWithAurix(552)] : retrying board recovery check...
[2024-12-03 11:32:54,909 root DEBUG utilities.py 294 140] [bootburn]: [getListTargetsInRecovery(3975)] : Bus 003 Device 014: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2024-12-03 11:32:54,909 root DEBUG utilities.py 294 140] [bootburn]: [GetTegrasAssocWithAurix(552)] : retrying board recovery check...
[2024-12-03 11:32:54,909 root DEBUG utilities.py 294 140] [bootburn]: [getListTargetsInRecovery(3975)] : Bus 003 Device 014: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2024-12-03 11:32:54,909 root DEBUG utilities.py 294 140] [bootburn]: [GetTegrasAssocWithAurix(552)] : retrying board recovery check...
[2024-12-03 11:32:54,909 root DEBUG utilities.py 294 140] [bootburn]: [getListTargetsInRecovery(3975)] : Bus 003 Device 014: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2024-12-03 11:32:54,909 root DEBUG utilities.py 294 140] [bootburn]: [GetTegrasAssocWithAurix(552)] : retrying board recovery check...
[2024-12-03 11:32:54,909 root DEBUG utilities.py 294 140] [bootburn]: [getListTargetsInRecovery(3975)] : Bus 003 Device 014: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2024-12-03 11:32:54,909 root DEBUG utilities.py 294 140] [bootburn]: [GetTegrasAssocWithAurix(552)] : retrying board recovery check...
[2024-12-03 11:32:54,909 root DEBUG utilities.py 294 140] [bootburn]: [getListTargetsInRecovery(3975)] : Bus 003 Device 014: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2024-12-03 11:32:54,910 root DEBUG utilities.py 294 140] [bootburn]: [GetTegrasAssocWithAurix(552)] : retrying board recovery check...
[2024-12-03 11:32:54,910 root DEBUG utilities.py 294 140] [bootburn]: [getListTargetsInRecovery(3975)] : Bus 003 Device 014: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2024-12-03 11:32:54,910 root DEBUG utilities.py 294 140] [bootburn]: [GetTegrasAssocWithAurix(552)] : retrying board recovery check...
[2024-12-03 11:32:54,910 root DEBUG utilities.py 294 140] [bootburn]: [getListTargetsInRecovery(3975)] : Bus 003 Device 014: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2024-12-03 11:32:54,910 root DEBUG utilities.py 294 140] command line used was:
[2024-12-03 11:32:54,910 root DEBUG utilities.py 294 140] ['/drive/drive-foundation/tools/flashtools/bootburn/bootburn.py', '--find_board_name', '-x', '/dev/ttyACM1']
[2024-12-03 11:32:54,910 root DEBUG utilities.py 294 140] 
[2024-12-03 11:32:54,910 root DEBUG utilities.py 294 140] 
[2024-12-03 11:32:54,910 root DEBUG utilities.py 294 140] Could not put Tegra-A in recovery
[2024-12-03 11:32:54,910 root DEBUG utilities.py 294 140] 
[2024-12-03 11:32:54,910 root DEBUG utilities.py 294 140] [bootburn]: [__exit__(82)] : Exception in critical section :<class 'OSError'>
[2024-12-03 11:32:54,910 root DEBUG utilities.py 294 140] 
[2024-12-03 11:32:54,910 root DEBUG utilities.py 294 140] Exception caught in bootburn 
[2024-12-03 11:32:54,910 root DEBUG utilities.py 294 140] Traceback (most recent call last):
[2024-12-03 11:32:54,910 root DEBUG utilities.py 294 140] File "/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/bootburn.py", line 271, in bootburn
[2024-12-03 11:32:54,910 root DEBUG utilities.py 294 140] bootburnLib.CheckRecoveryTargets()
[2024-12-03 11:32:54,910 root DEBUG utilities.py 294 140] File "/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/bootburn_lib.py", line 3920, in CheckRecoveryTargets
[2024-12-03 11:32:54,910 root DEBUG utilities.py 294 140] self.aurix.GetTegrasAssocWithAurix(self.targetConfig.s_AurixPort)
[2024-12-03 11:32:54,910 root DEBUG utilities.py 294 140] File "/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/bootburn_aurix.py", line 551, in GetTegrasAssocWithAurix
[2024-12-03 11:32:54,910 root DEBUG utilities.py 294 140] AbnormalTermination("Could not put {} in recovery".format(name), nverror.NvError_ResourceError)
[2024-12-03 11:32:54,910 root DEBUG utilities.py 294 140] File "/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/flashtools_nverror.py", line 251, in AbnormalTermination
[2024-12-03 11:32:54,910 root DEBUG utilities.py 294 140] raise OSError(errorCode)
[2024-12-03 11:32:54,910 root DEBUG utilities.py 294 140] OSError: 15
[2024-12-03 11:32:54,911 root INFO runner.py 37 140] Failed to bind partitions!
[2024-12-03 11:32:54,911 root DEBUG runner.py 39 140] Error on line 972
[2024-12-03 11:32:54,911 root DEBUG runner.py 40 140] Exception info: Exception Type <class 'module.errors.FailedToBindPartitionsError'>, Traceback <traceback object at 0x7fadc601c480>
[2024-12-03 11:32:54,911 root INFO runner.py 42 140] driveinstaller cannot continue! Check the log file for details: /drive/driveinstaller/driveinstaller.log
[2024-12-03 11:32:54,911 root DEBUG runner.py 62 140] Cleaning up...
[2024-12-03 11:32:54,911 root DEBUG utilities.py 137 140] Deleting temporary directories...
[2024-12-03 11:32:54,911 root DEBUG utilities.py 139 140] Deleting /tmp/pdkinstall-tmp-e7w3ljoh-bind
[2024-12-03 11:32:54,911 root DEBUG runner.py 64 140] Closing the log file.
root@6.0.10.0-0009-build-linux-sdk:/drive#

Logs

driveinstaller.log (28.4 KB)

SivaRamaKrishnaNV · December 4, 2024, 4:13am

Could you check if any serial console session is active?
The error indicate tegra could not be put in recovery mode. Could you check if the board can be set into recovery mode from aurix console manually and confirm additional device is detected in lsusb.

You may manually put the board in recovery from and try bootburn.py and see if it works. After flash keep board in normal mode again.

/drive-foundation/make/bind_partitions -b p3710-10-s05 linux

 
./drive-foundation/tools/flashtools/bootburn/bootburn.py -b p3710-10-s05 -B qspi chain B

ashwin.nanda · December 4, 2024, 10:41am

Hi @SivaRamaKrishnaNV , thank you replying back, please refer the following steps performed after your response on this:

step 1 > switched bootchain to B to flash
step 2 > put manually into recovery
NvShell>
NvShell>tegrarecovery x1 on
Info: Executing cmd: tegrarecovery, argc: 2, args: x1 on
Command Executed
NvShell>
step 3> closed the ACM1 connection
step 4 > found listed on lsub output

pomo@pomodriver:~$ lsusb
Bus 002 Device 002: ID 8087:8000 Intel Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 025: ID 145f:02aa Trust Trust Full HD Webcam
Bus 003 Device 014: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
Bus 003 Device 005: ID 046d:c34a Logitech, Inc. LogiG TKL MKeyboard
Bus 003 Device 008: ID 0000:3825   USB OPTICAL MOUSE
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pomo@pomodriver:~$

step 5 > binding partitions manually (added a snippet (Question - this snippet shows boot blob image for CHAIN C is completed, does this mean only C is made or I am just seeing the end chain, and rest two are made before this?))

[MAKE] pct.json
# Below symlink is for compatibility w/ System Profiler
7887 blocks
[MAKE] TOS image
make -f /drive/drive-foundation/security/trusted-os/Makefile.cpio \
	TOS_BASE=/drive/drive-foundation/security/trusted-os \
	HV_PCT_BIN_PATH=/drive/drive-foundation/virtualization/hypervisor/t23x/configs/t234ref-release/pct/p3710-10-s05/linux/pct.bin \
	ARCH=t23x \
	TOS_BIN_SUFFIX= \
	TOS_OUTDIR=/drive/drive-foundation/security/trusted-os/out/t23x/tos \
	MAKE_DIR=/drive/drive-foundation/security/trusted-os \
	TOOLCHAIN_DIR=""
Creating TOS USER BIN: /drive/drive-foundation/security/trusted-os/out/t23x/tos/user-tct.bin with Apps pscfw-service crypto-asym-service crypto-sym-service pkcs11-keystore gp-se nvmacsec
# __USER__ is intentionally 8-byte long
# _CUSTOM_ is intentionally 8-byte long
Creating TOS CPIO: /drive/drive-foundation/security/trusted-os/out/t23x/tos/blob.cpio with Apps pscfw-service crypto-asym-service crypto-sym-service pkcs11-keystore gp-se nvmacsec and Servers tz-se_server secure-sysmgr
Creating TOS image
Generated TOS image @ /drive/drive-foundation/security/trusted-os/out/t23x/tos/tos.img
'/drive/drive-foundation/security/trusted-os/out/t23x/tos/tos.img' -> '/drive/drive-foundation/firmware/bin/t23x/tzvault/p3710-10-s05/tos.img'

 ********** boot blob image created ********** 

target SOC is t234
Applying DTB Cleanup
BPMP_SERVER_ELF is /drive/drive-foundation/virtualization/hypervisor/t23x/safety/bpmp_server_native_dev
BPMP_SERVER_BIN is /drive/drive-foundation/virtualization/hypervisor/t23x/safety/bpmp_server_native
SE_SERVER_NATIVE is /drive/drive-foundation/virtualization/hypervisor/t23x/safety/se_server_native
SE_SERVER_ELF is /drive/drive-foundation/virtualization/hypervisor/t23x/safety/se_server_native_prod_debug
VSC_SERVER_UFS_ELF is /drive/drive-foundation/virtualization/hypervisor/t23x/safety/vsc_server_native_ufs_standard
VSC_SERVER_QSPI_ELF is /drive/drive-foundation/virtualization/hypervisor/t23x/safety/vsc_server_native_qspi_standard
VSC_SERVER_SDMMC_ELF is /drive/drive-foundation/virtualization/hypervisor/t23x/safety/vsc_server_native_sdmmc_standard
NVHOST_SERVER_NATIVE is /drive/drive-foundation/virtualization/hypervisor/t23x/safety/nvhost_server_native
rm -rf /drive/drive-foundation/virtualization/hypervisor/t23x/configs/t234ref-release/pct/p3710-10-s05_chain_c/linux_chain_c
rm -rf /drive/drive-foundation/out/p3710-10-s05_chain_c
mkdir -p /drive/drive-foundation/out/p3710-10-s05_chain_c
[MAKE] pct.bin
mkdir -p /drive/drive-foundation/virtualization/hypervisor/t23x/configs/t234ref-release/pct/p3710-10-s05_chain_c/linux_chain_c
[platform_pct_metadata.h] copy from /drive/drive-foundation/out/p3710-10-s05/platform_pct_metadata.h to /drive/drive-foundation/virtualization/hypervisor/t23x/configs/t234ref-release/pct/p3710-10-s05_chain_c/linux_chain_c
[CC] pct.o
[GCC] pct.elf
[OBJCPY] pct.bin
[CPP] t23x-debug-server.dts0
[DTC] t23x-debug-server.dtb
<stdout>: Warning (clocks_property): Missing property '#clock-cells' in node /bpmp or bad phandle (referred from /tegra_safety_audio:clocks[0])
[CPP] t23x-ethernet-server.dts0
[DTC] t23x-ethernet-server.dtb
<stdout>: Warning (clocks_property): Missing property '#clock-cells' in node /bpmp or bad phandle (referred from /tegra_safety_audio:clocks[0])
[CPP] t23x-vsc-server.dts0
[DTC] t23x-vsc-server.dtb
<stdout>: Warning (clocks_property): Missing property '#clock-cells' in node /bpmp or bad phandle (referred from /tegra_safety_audio:clocks[0])
[CPP] gpu-server.dts0
[DTC] gpu-server.dtb
<stdout>: Warning (clocks_property): Missing property '#clock-cells' in node /bpmp or bad phandle (referred from /tegra_safety_audio:clocks[0])
[CPP] t23x-bpmp-server.dts0
[DTC] t23x-bpmp-server.dtb
<stdout>: Warning (clocks_property): Missing property '#clock-cells' in node /bpmp or bad phandle (referred from /tegra_safety_audio:clocks[0])
[CPP] t23x-se-server.dts0
[DTC] t23x-se-server.dtb
<stdout>: Warning (clocks_property): Missing property '#clock-cells' in node /bpmp or bad phandle (referred from /tegra_safety_audio:clocks[0])
[CPP] t23x-update-service.dts0
[DTC] t23x-update-service.dtb
<stdout>: Warning (clocks_property): Missing property '#clock-cells' in node /bpmp or bad phandle (referred from /tegra_safety_audio:clocks[0])
[CPP] t23x-vm-server.dts0
[DTC] t23x-vm-server.dtb
<stdout>: Warning (clocks_property): Missing property '#clock-cells' in node /bpmp or bad phandle (referred from /tegra_safety_audio:clocks[0])
delnode.sh version     : 1.0
delnode.sh version     : 1.0
delnode.sh trim dtb    : t23x-debug-server.dtb
removed '/drive/drive-foundation/out/p3710-10-s05_chain_c/t23x-debug-server.dtb_temp1.dts'
removed '/drive/drive-foundation/out/p3710-10-s05_chain_c/t23x-debug-server.dtb_temp2.dts'
removed '/drive/drive-foundation/out/p3710-10-s05_chain_c/t23x-debug-server.dtb_temp3.dts'
removed '/drive/drive-foundation/out/p3710-10-s05_chain_c/t23x-debug-server.dtb_temp4.dts'
removed '/drive/drive-foundation/out/p3710-10-s05_chain_c/t23x-debug-server.dtb_temp3.dtb'
delnode.sh version     : 1.0
delnode.sh trim dtb    : t23x-vsc-server.dtb
removed '/drive/drive-foundation/out/p3710-10-s05_chain_c/t23x-vsc-server.dtb_temp1.dts'
removed '/drive/drive-foundation/out/p3710-10-s05_chain_c/t23x-vsc-server.dtb_temp2.dts'
removed '/drive/drive-foundation/out/p3710-10-s05_chain_c/t23x-vsc-server.dtb_temp3.dts'
removed '/drive/drive-foundation/out/p3710-10-s05_chain_c/t23x-vsc-server.dtb_temp4.dts'
removed '/drive/drive-foundation/out/p3710-10-s05_chain_c/t23x-vsc-server.dtb_temp3.dtb'
delnode.sh version     : 1.0
delnode.sh version     : 1.0
delnode.sh whitelist   : t23x-bpmp-server.dtb
delnode.sh version     : 1.0
delnode.sh trim dtb    : t23x-update-service.dtb
removed '/drive/drive-foundation/out/p3710-10-s05_chain_c/t23x-update-service.dtb_temp1.dts'
removed '/drive/drive-foundation/out/p3710-10-s05_chain_c/t23x-update-service.dtb_temp2.dts'
removed '/drive/drive-foundation/out/p3710-10-s05_chain_c/t23x-update-service.dtb_temp3.dts'
removed '/drive/drive-foundation/out/p3710-10-s05_chain_c/t23x-update-service.dtb_temp4.dts'
removed '/drive/drive-foundation/out/p3710-10-s05_chain_c/t23x-update-service.dtb_temp3.dtb'
delnode.sh version     : 1.0
delnode.sh trim dtb    : t23x-se-server.dtb
removed '/drive/drive-foundation/out/p3710-10-s05_chain_c/t23x-se-server.dtb_temp1.dts'
removed '/drive/drive-foundation/out/p3710-10-s05_chain_c/t23x-se-server.dtb_temp2.dts'
removed '/drive/drive-foundation/out/p3710-10-s05_chain_c/t23x-se-server.dtb_temp3.dts'
removed '/drive/drive-foundation/out/p3710-10-s05_chain_c/t23x-se-server.dtb_temp4.dts'
removed '/drive/drive-foundation/out/p3710-10-s05_chain_c/t23x-se-server.dtb_temp3.dtb'
delnode.sh version     : 1.0
delnode.sh whitelist   : t23x-vm-server.dtb
[MAKE] pct.json
# Below symlink is for compatibility w/ System Profiler
6960 blocks
[MAKE] TOS image
make -f /drive/drive-foundation/security/trusted-os/Makefile.cpio \
	TOS_BASE=/drive/drive-foundation/security/trusted-os \
	HV_PCT_BIN_PATH=/drive/drive-foundation/virtualization/hypervisor/t23x/configs/t234ref-release/pct/p3710-10-s05_chain_c/linux_chain_c/pct.bin \
	ARCH=t23x \
	TOS_BIN_SUFFIX= \
	TOS_OUTDIR=/drive/drive-foundation/security/trusted-os/out/t23x/tos \
	MAKE_DIR=/drive/drive-foundation/security/trusted-os \
	TOOLCHAIN_DIR=""
Creating TOS USER BIN: /drive/drive-foundation/security/trusted-os/out/t23x/tos/user-tct.bin with Apps pscfw-service crypto-asym-service crypto-sym-service pkcs11-keystore gp-se nvmacsec
# __USER__ is intentionally 8-byte long
# _CUSTOM_ is intentionally 8-byte long
Creating TOS CPIO: /drive/drive-foundation/security/trusted-os/out/t23x/tos/blob.cpio with Apps pscfw-service crypto-asym-service crypto-sym-service pkcs11-keystore gp-se nvmacsec and Servers tz-se_server secure-sysmgr
Creating TOS image
Generated TOS image @ /drive/drive-foundation/security/trusted-os/out/t23x/tos/tos.img
'/drive/drive-foundation/security/trusted-os/out/t23x/tos/tos.img' -> '/drive/drive-foundation/firmware/bin/t23x/tzvault/p3710-10-s05_chain_c/tos.img'

 ********** boot blob image CHAIN C ended **********

step 6> manually running bootburn.py with --chain B as option

root@6.0.10.0-0009-build-linux-sdk:/drive# ./drive-foundation/tools/flashtools/bootburn/bootburn.py -b p3710-10-s05 -B qspi --chain B
****** Starting bootburn/bootburn.py ********
********* Starting t23x bootburn py ********
Bootburn Starting with arguments ['./drive-foundation/tools/flashtools/bootburn/bootburn.py', '-b', 'p3710-10-s05', '-B', 'qspi', '--chain', 'B']
logfile :: /drive/drive-foundation/tools/flashtools/bootburn_t23x_py/bootburn.txt
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.json

Check finished successfully
Done parsing command line

[bootburn]: [getListTargetsInRecovery(3975)] : Bus 003 Device 014: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[bootburn]: [CheckRecoveryTargets(3933)] : No recovery-target found; Make sure the target device is connected to the
[bootburn]: [CheckRecoveryTargets(3934)] : host and is in recovery mode. Exiting
command line used was:
['./drive-foundation/tools/flashtools/bootburn/bootburn.py', '-b', 'p3710-10-s05', '-B', 'qspi', '--chain', 'B']


ERROR_TARGET_RECOVERY


Exception caught in bootburn 
Traceback (most recent call last):
  File "/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/bootburn.py", line 271, in bootburn
    bootburnLib.CheckRecoveryTargets()
  File "/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/bootburn_lib.py", line 3935, in CheckRecoveryTargets
    AbnormalTermination("ERROR_TARGET_RECOVERY", nverror.NvError_ResourceError)
  File "/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/flashtools_nverror.py", line 251, in AbnormalTermination
    raise OSError(errorCode)
OSError: 15
root@6.0.10.0-0009-build-linux-sdk:/drive#

ashwin.nanda · December 4, 2024, 1:34pm

@SivaRamaKrishnaNV Its my one of the long days I imagine, I had the type-c cable connected to the right port. (my fault)

Reconnected to left port, and flashed again. Now we have both DRIVE OS on the SoC. Thank you for looking into this.

SivaRamaKrishnaNV · December 4, 2024, 1:40pm

Glad to hear you could flash. Thank you for update.

system · December 18, 2024, 1:41pm

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

Topic		Replies	Views
Flash failed. Orin no more recoverable or flashable DRIVE AGX Orin General drive-platform-setup	14	636	February 12, 2024
First attempt to use bootburn, Yocto build, python errors DRIVE AGX Orin General drive-platform-setup	14	75	August 21, 2024
Driver orin Dev kit flashing failed:- Encounter Errors while flashing using bootburn.py script DRIVE AGX Orin General drive-platform-setup	14	1196	June 2, 2023
DriveOS 6.0.4 Flashing Failures DRIVE AGX Orin General drive-platform-setup	36	3027	March 14, 2023
Drive OS Migration from 6.0.6 to 6.0.10 DRIVE AGX Orin General drive-platform-setup	13	45	March 24, 2025
Drive AGX instaltion failed with SDK Manager DRIVE AGX Orin General drive-platform-setup	41	1983	August 30, 2023
Drive AGX flash error DRIVE AGX Orin General drive-platform-setup	17	513	August 8, 2024
DRIVE ORIN flash fail DRIVE AGX Orin General drive-platform-setup	4	238	May 15, 2024
Drive OS 6.0.8.1 flashing error DRIVE AGX Orin General drive-platform-setup	17	735	May 9, 2024
Drive AGX flashing failed DRIVE AGX Xavier General	21	1137	October 12, 2021

Failing to flash single bootchain with a different DRIVEOS

Related topics