Bootloader Diagnostic Data
Represents one piece of diagnostic data the bootloader keeps about the device.
Each subtype covers one thing the bootloader records: why the device last reset, the details of a crash, or how recent firmware updates went. Crash reports are split across several parts because one exchange with the device cannot carry them whole, so a full picture needs every part of a set.
Most values are raw register or status codes meant for Efento to interpret rather than to show to users.
Inheritors
Types
The application hit a failed assertion.
First part of an application crash report: the fault status registers.
Second part of an application crash report: the faulting address and the first stacked registers.
Third part of an application crash report: the remaining stacked registers, including where it was executing.
Fourth part of an application crash report.
The bootloader itself hit a failed assertion.
First part of a bootloader crash report: the fault status registers.
Second part of a bootloader crash report: the faulting address and the first stacked registers.
Third part of a bootloader crash report: the remaining stacked registers, including where it was executing.
Fourth part of a bootloader crash report.
A supervised part of the application stopped responding.
Why the device last restarted, and how often it has been restarting.
Piece of diagnostic data to ask the bootloader for.
Firmware the device left the factory with.
Outcome of the last time the device checked for a firmware update.
One of the last four firmware update attempts the device recorded.