A/B ROOTFS Redundancy: Bootloader does not boot from backup slot when the working slot is intentionally corrupted

Autonomous Machines Jetson & Embedded Systems Jetson AGX Xavier
,
13

hello sanaurrehman,

please ignore UEFI, that’s necessary only for JP-5.0.1 or later.
and… sorry about the confusion. you know, too many Jetpack release versions we’re supported right now.


let’s focus on RootfsA/B with JP-4.6 release version.
you should refer to this documentation. Root File System Redundancy.

  1. the Cboot will decrease the retry_count of the current rootfs slot.

  2. When the device boot into the rootfs, there will run a background service nv_update_verifier.service, this service will trigger l4t-rootfs-validation-config.service to say the boot is successful.
    however, if the validation script doesn’t exist or returns true, that means the rootfs boot-up successful also.

  3. If the rootfs validation is true, then the “nv_update_verifier.service” will run “/usr/sbin/nv_update_engine --verify”, the nv_update_engine will increase the retry_count and update slot status.

  4. it’s nvbootctrl to switch the rootfs slot. l4t-rootfs-validation-config.service to validate the rootfs.

so,
you should also have a script, l4t-rootfs-validation-config.sh to handle it.
you may found this sample within release image.
i.e. ./rootfs/opt/nvidia/l4t-rootfs-validation-config/l4t-rootfs-validation-config.sh

please have a try, looking forward your test results.
see-also topics, Topic 198703, Topic 197124.