Bootloader does not fall-back to slot A when Slot B can't boot (rootfs A/B)

Autonomous Machines Jetson & Embedded Systems Jetson AGX Xavier
6

Hello JerryChang,

thanks for this on-point summary. We already read a lot about the nv_update_verifier.service before, but this whole mechanism will only run after a kernel was booted succesfully. We plan to use it to verify that our deployed application(s) are fine, but its not useful to guarantee changes to e.g. Bootloader, Kernel, Devicetree, Rootfs are fine.

So what is described in Topic 197124 means that the current bootloader in 32.6 is not capable for what we are testing currently, right?

Only in 32.7 it will be fixed and the bootloader will count-down the retries on a failed boot, is that right?