When implementing a bootloader with "A/B partitioning" for OTA updates, what critical step ensures a device doesn't get permanently bricked by a bad update?
Correct! Well done.
Incorrect.
The correct answer is A) The bootloader verifies the new firmware's integrity and attempts to boot it; if it fails to confirm a successful boot within a timeout (e.g., via a watchdog), the bootloader reverts to the previous known-good partition
Correct Answer
The bootloader verifies the new firmware's integrity and attempts to boot it; if it fails to confirm a successful boot within a timeout (e.g., via a watchdog), the bootloader reverts to the previous known-good partition
A robust OTA scheme keeps the previous working firmware intact in the inactive partition; if the new firmware fails to mark itself as successfully booted (e.g., crashes repeatedly), the bootloader falls back to the known-good partition, preventing a "bricked" device.