Please provide the following info (tick the boxes after creating this topic):
Software Version
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
(using 6.0.9)
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
1.9.3.10904
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 am trying to do just driveos kernel dtb updates with driveupdate (all nvidia provided samples and plugins are used)
The board is flashed with a different image before following these steps
Steps followed:
./make/bind_partitions -s 2 -b p3710-10-s05 linux
python3 ./tools/flashtools/bootburn/create_bsp_images.py -u A_1_kernel-dtb -b p3710-10-s05 -B qspi -r 1 -g $NV_WORKSPACE/bsp_image
python3 ./dupkg/dupkg.py gen --template dupkg_single_tegra_template --in TEGRA_A_SRC=$NV_WORKSPACE/bsp_image/642-63710-0010-000_TS5/flash-images/ --out $NV_WORKSPACE/dupkg
The output of create_bsp_images.py works and boots properly when we flash it with flash_bsp_images.py.
The dupkg from the same bsp_image when deployed however breaks the boot process to the other bootchain in MB2 with error:
I> Task: Load PVIT
I> Partition name: B_pvit
I> Size of partition: 262144
I> Binary@ device:8/0 block-13636928 (partition size: 0x40000), name: B_pvit
E> HeaderMagic Invalid
E> data NVDA, header magic kernel-dtb
C> Task 0x0 failed (err: 0x22220002)
E> Top caller module: LOADER, error module: LOADER, reason: 0x02, aux_info: 0x00
I> Busy Spin
It looks like the PVIT is not valid after the driveupdate, but the USB flash method handles this case properly by doing some sort of partial PVIT update.
Please advise on how to fix this?
I am looking to use driveupdate to just deploy devicetree modifications without touching anything else in the image.
Thank you in advance.