What it solves
A Cortex-M fault can erase the register and reason context needed for diagnosis.
How it works
1Fault→2retained 192-byte commit→3reboot check→4export→5offline decoder
Use it when
Capture Cortex-M fault state
Export a retained dump over a character sink at boot
Decode binary or captured hex on a host
Quick Start
#include "panicdump.h"
if(panicdump_has_valid()){
panicdump_boot_check_and_export(write_char);
panicdump_clear();
}
/* Expected: valid retained evidence is exported once. */Real scenarios
Capture Cortex-M fault state
A retained-RAM library commits a fixed 192-byte CRC-protected dump and exports it for offline decoding.
Export a retained dump over a character sink at boot
A retained-RAM library commits a fixed 192-byte CRC-protected dump and exports it for offline decoding.
Decode binary or captured hex on a host
A retained-RAM library commits a fixed 192-byte CRC-protected dump and exports it for offline decoding.
Engineering evidence
- README records passing host, sanitizer, static-analysis, package, decoder and ARM CI gates
Known limits
- Targets bare-metal Cortex-M plus a host/mock test port
- Retained RAM placement and reset behavior are platform responsibilities
- A dump records evidence; it does not recover the application