hello initrd.img,
the logic is… if the retry_count reaches 0, then the cboot will select another rootfs slot.
it’s cboot to decrease retry count of the current slot.
when the device boot into the rootfs, there will run a background service, nv_update_verifier.service.
in this update verifier service, it will trigger the l4t-rootfs-validation-config.service, this validation service provides an interface to users to customize when to say the boot is successful.
for example, /usr/sbin/user_rootfs_validation.sh, this script does not exist by default.
if the validation script doesn’t exist, or, returns true, that means the rootfs boot-up successful.
so,
in your case, you should not use nvbootctrl to mark the rootfs slot as unbootable, you should use the l4t-rootfs-validation-config.sh to handle it instead.
unfortunately, it seems we missed this info in the public user guide. we will review the documentation to update it.
thanks