Hey, So we don't run the FIT verity tests on CI, because veritysetup isn't installed, and should fix that as it's own problem. On one of my test setups, I ran in to this: ----------------------------- Captured stdout call ----------------------------- +/tmp/tmp.xSw29uYDUF/am62x_beagleplay_a53/tools/mkimage -E -D -I dts -O dtb -i /tmp/tmp.xSw29uYDUF/am62x_beagleplay_a53_results/verity-equal -f /tmp/tmp.xSw29uYDUF/am62x_beagleplay_a53_results/verity-equal/image.its /tmp/tmp.xSw29uYDUF/am62x_beagleplay_a53_results/verity-equal/i mage.itb FIT description: dm-verity test Created: Wed Aug 12 11:01:01 2026 Image 0 (rootfs) Description: test filesystem Created: Wed Aug 12 11:01:01 2026 Type: Filesystem Image Compression: uncompressed Data Size: 262144 Bytes = 256.00 KiB = 0.25 MiB Default Configuration: 'conf-1' Configuration 0 (conf-1) Description: test config Kernel: unavailable Loadables: rootfs +fdtget /tmp/tmp.xSw29uYDUF/am62x_beagleplay_a53_results/verity-equal/image.itb /images/rootfs/dm-verity algo sha256 +fdtget /tmp/tmp.xSw29uYDUF/am62x_beagleplay_a53_results/verity-equal/image.itb /images/rootfs/dm-verity data-block-size 4096 +fdtget /tmp/tmp.xSw29uYDUF/am62x_beagleplay_a53_results/verity-equal/image.itb /images/rootfs/dm-verity hash-block-size 4096 +fdtget /tmp/tmp.xSw29uYDUF/am62x_beagleplay_a53_results/verity-equal/image.itb /images/rootfs/dm-verity num-data-blocks Error at 'num-data-blocks': FDT_ERR_NOTFOUND Exit code: 1
-- Tom
signature.asc
Description: PGP signature
