Ever had a device in the field reject a firmware update or roll back to an older image, with no clue why? wolfBoot can now tell you. With the new WOLFBOOT_PERSIST_FAILURE_STATUS option, wolfBoot records the cause of every update, self-update and rollback failure into a dedicated flash region, so your application can read it back after the fact.
Each record captures the phase (update rejected, boot verification failed, rollback, emergency recovery), the cause (bad header, hash mismatch, invalid signature, or an image that never confirmed with wolfBoot_success()), the partition and the firmware version involved. Records are CRC-protected and stored in a circular log across configurable flash sectors, tolerating torn writes and preserving history across power loss. Internal and external flash are both supported, and a simple API (wolfBoot_get_failure_count(), wolfBoot_get_failure(), wolfBoot_clear_failures()) makes the records available to your firmware for logging, telemetry or recovery decisions.
The feature is fully optional and adds no overhead when disabled. For further information, you can read the full documentation in the wolfBoot repository.
If you have questions about wolfBoot or securing your firmware updates, contact us at facts@wolfssl.com or call us at +1 425 245 8247.
Download wolfSSL Now