Fault Forensics

Read the shared embedded contract and keep source/build, device and physical evidence separate.

Read capture and architecture. Preserve the original log/register dump, reset reason, exact ELF/map, revision, build options and architecture before rebooting or rebuilding. Never symbolize against a newer binary merely because its filename matches.

For ARMv7-M Cortex-M3/M4/M7, run the offline uv run scripts/decode_cortex_fault.py CAPTURE.json on the documented schema. It reports set bits, valid fault addresses and unresolved cause. It does not read hardware or establish that a stacked PC identifies the initiating instruction. Cortex-M0/M0+ and ARMv8-M have different fault facilities; ESP32 Xtensa/RISC-V panic formats use the matching vendor decoder instead.