DRIVE OS Version: 6.0.10
Issue Description: Understanding the hierarchy to rebuild the targetfs and binding the filesystem with yocto project
Dear NVIDIA Team, please consider this thread in regard to understand the build process and flashing the filesystem back to the target device
So far so, from the manual : DRIVE OS Linux Yocto Components | NVIDIA Docs
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?