It seems like to rebuild the flash-able image, we would need the `tegra-drive-os-av-image` to be used with bitbake recipies in a certain variant (full; minimal; samples; and debug-utils).
What our intention is to be get a upgraded version of the `tegra-drive-os-av-image`, and then proceed with flashing this image with the bootburn without disturbing other partitions, and this is done by the `NVIDIA Build-Fs` ?
Upon reading the manual again, the `NVIDIA Build-Fs` seeks a base ubuntu image in deb format and the other resources as optional ? (like getting the deb files for CuDNN, CUDA, TensorRT) :
The NVIDIA Build-Fs needs a config manifest in json format to gather the mirrors and the base filesystem to build it altogether? and thus results in targetfs.img? this is then a linker to `tegra-drive-os-av-image`?
If the above reasoning is correct;
Can the base Ubuntu image (nv-driveos-linux-ubuntu-20.04-base-*_amd64.deb) be replaced with a different base image and then following with `NVIDIA Build-Fs` with an updated manifest?
Dear @SivaRamaKrishnaNV can I please get some guidance here? I believe I cant access any other version of nv-driveos-linux-ubuntu-20.04-base-*_amd64.deb package because DriveOS 6.0.10 was primarily made for Ubuntu20.04, however for a minimal build can the base image be repacked with Ubuntu22.04?
dear @SivaRamaKrishnaNV, thanks for reaching back, I still need confirmation on the build process, I intend to repack the base image from my side, please confirm the reasoning on the build-process, and I shall close this topic.
I intend to open the deb package and repack it, even it leads to a failure of build; all I want is to please confirm on the reasoning of the build process, much appreciated, thanks.
dear @SivaRamaKrishnaNV please let me know if ive got his wrongly understood, you may close this topic if this seems logically correct you, awaiting.. :