I am trying to create a full chain of trust boot. the secure boot was successful but i am having problems with dm-verity on the rootfs. i added configuration to the conf/locol.conf
IMAGE_INSTALL_append = " lvm2 cryptsetup "
IMAGE_FEATURES_append = " read-only-rootfs "
DM_VERITY_IMAGE = "fsl-image-qt5"
DM_VERITY_IMAGE_TYPE = "ext4"
IMAGE_CLASSES += " dm-verity-img "
IMAGE_BOOT_FILES_append = " fitImage-${INITRAMFS_IMAGE}-${MACHINE}-${MACHINE}"
INITRAMFS_IMAGE = "dm-verity-image-initramfs"
INITRAMFS_FSTYPES = "cpio.gz"
INITRAMFS_IMAGE_BUNDLE = "1"
in the deploy images i see the
dm-verity-initramfs cpio, Image.initramfs bin, rootfs.ext4.verity file
but when i deploy the fsl-image-qt5-imx8mm-var-dart.tar.gz file to the SD card i do not see that the initramfs or the dm-verity is working.
i thought the BUNDLE option binds the initfamfs to the oginal Image and the verity rootfs is bundled to the tar.gz that is deployed to the the SDCard
Hi @greeran
As this feature is supported by Yocto layer, you can post this issue in yocto community.
Reference link: https://lists.yoctoproject.org/g/yocto/message/49112