Does bootburn require special flags for updated rfs

DRIVE OS Version: 7.0.3

Issue Description: I have been following Rebuilding the Linux SDK File System With Modifications Using the Build-FS Tool — NVIDIA DriveOS 7.0.3 Linux SDK Developer Guide

However upon the step for flashing with bootburn it seems to always default to the below rootfs image.

/drive/drive-foundation/tools/flashtools/bootburn_t264_py/__temp_t264/Tegra-A-3356d19d9c8/flash-images/A_35_gos0-fs_dev_nsr_desktop_ubuntu-24.04_thor_rfs.**img
**
I am unable to determine which flags are required to specify use of a custom image during flashing. As per the linked doc my custom img has been copied over ${NV_WORKSPACE}/drive-linux/filesystem/targetfs.img

as an update to this. I believe I have located a bootburn cfg (boot_chain_storage.cfg) where this may be coming from. Am I to edit this file with the path to where my custom image resides? or is there a more “proper” way to specify which usr-fs image bootburn should use?

Dear @abwaab ,
Does that means provided steps are not working? Could you share the complete command and logs to verify?

bootburn_cmd.txt (11.1 KB)

Nothing tried so far has resulted in my custom image being flashed. Seems the image from the _tmp bootburn working dir created during bootburn run is what gets flashed each time.
Attaching log of command used and bootburn output. In addition to LSOF logs captured during bootburn run.

lsof_bootburn.log (14.0 KB)

Okay I believe this was due to not using an absolute path in LINUX_RFS_IMG_PATH= . It seems ${NV_WORKSPACE} causes issues when used in the value for this flag.

Using the absolute “/drive/../../file.img” seems to ensure bootburn picks up the specified image during flash.

Got it. Thanks for update. I believe the issue was at bind_partition step 9 from Rebuilding the Linux SDK File System With Modifications Using the Build-FS Tool — NVIDIA DriveOS 7.0.3 Linux SDK Developer Guide

9. Pass the absolute path of the updated rootfs image using the bind_partitions command-line argument: LINUX_RFS_IMG_PATH=<absolute path of rootfs image> as seen in the example below.

cd /drive/drive-foundation ./make/bind_partitions -b p3960-10-sw01 drive_av.linux -p dev_nsr LINUX_RFS_IMG_PATH=/drive/drive-linux/filesystem/targetfs-images/driveos-updated-rfs.img