To flash Yocto built Images via bootburn

These steps update the Yocto built images back to the release so that bootburn picks them up:
  1. Change to the Yocto deploy directory:
    cd <top>/drive-linux_src/yocto/build/tmp/deploy/images/${MACHINE}
  2. Copy the linux-DTBs to the release:
    cp *.dtb <top>/drive-linux/kernel/preempt_rt/
  3. Copy the kernel images and modules to the release:
    cp Image <top>/drive-linux/kernel/preempt_rt/images/
    cp vmlinux <top>/drive-linux/kernel/preempt_rt/images/
    cp System.map <top>/drive-linux/kernel/preempt_rt/images/
    
    
    For K5.15:
    cd <top>/drive-linux/kernel/preempt_rt/modules 
    tar xf <top>/drive-linux_src/yocto/build/tmp/deploy/images/${MACHINE}/modules-${MACHINE}.tgz 
    find ./ -name '*rt-tegra*' -exec mv -t ./ {} +
    For K5.15 with production config :
    cd <top>/drive-linux/kernel/preempt_rt_prod/modules
    tar xf <top>/drive-linux_src/yocto/build/tmp/deploy/images/${MACHINE}/modules-${MACHINE}.tgz 
    find ./ -name '*rt-tegra*' -exec mv -t ./ {} +
  4. Copy the initramfs to the release:
    For K5.10 :
    cp tegra-initramfs-boot-*.cpio <top>/drive-linux/filesystem/initramfs.cpio
    For K5.15 :
    cp tegra-knext-initramfs-boot-*.cpio <top>/drive-linux/filesystem/initramfs.cpio
    For K5.15 with production config :
    cp tegra-prod-knext-initramfs-boot-*.cpio <top>/drive-linux/filesystem/prod-initramfs.cpio
  5. Copy the recovery initramfs to the release:
    cp tegra-initramfs-recovery-*.cpio <top>/drive-linux/filesystem/recovery-initramfs.cpio
  6. Place the drive-os-av rootFS image at the location specified by the bootburn configurations:
    cd <top>/drive-linux/filesystem/targetfs-images
    cp tegra-drive-os-av-image-${MACHINE}.img <top>/drive-linux/filesystem/targetfs-images
    ln -sf <top>/drive-linux/filesystem/targetfs-images/tegra-drive-os-av-image${MACHINE}.img <top>/drive-linux/filesystem/targetfs.img

After following the steps above, all binaries are replaced by the Yocto built versions. Executing bootburn now automatically picks up these updated binaries. This applies to both native, as well as hypervisor flashing. For information on flashing steps, see the Flashing Customization topic in the NVIDIA DRIVE OS 6.0 Linux SDK Developer Guide.