dangernoodle-io / breadboard / 25123197578

100%

push

github

feat(bb_log): RTC panic capture + GET/DELETE /api/diag/panic (#152)

Mirrors bb_log_stream's ringbuffer into a magic+CRC-validated
buffer in RTC slow memory (RTC_NOINIT_ATTR), so the last KB of
log lines survives a software reboot. On the next boot, if the
record is valid AND esp_reset_reason() reports an abnormal
reset (panic, task/int/regular WDT, brownout), the data is
exposed via:

  GET    /api/diag/panic  → {"available": <bool>, "reset_reason": "...",
                              "log_tail": "..."}
  DELETE /api/diag/panic  → 204, clears the record

Generic — any BB consumer running on a device without serial
console access can diagnose post-rollback panics remotely. Cost:
2 KB RTC slow RAM (configurable 512–8192 via Kconfig).

New public API in components/bb_log/include/bb_log.h:
  bool     bb_log_panic_available(void);
  bb_err_t bb_log_panic_get(char *out, size_t *len_inout);
  void     bb_log_panic_clear(void);

Kconfig:
  CONFIG_BB_LOG_PANIC_CAPTURE     (default y)
  CONFIG_BB_LOG_PANIC_BUF_SIZE    (default 2048, range 512..8192)

Host stub returns NOT_FOUND for the entire surface; tests
exercise the host path.

Disabled at compile time by clearing CONFIG_BB_LOG_PANIC_CAPTURE
— the routes don't register, the RTC buffer isn't allocated,
and the mirror-write hook compiles to nothing.

Closes B1-120 follow-up (panic visibility was a frequent gap
during the TM↔BB sync and bitaxe-403 diagnosis).

336 of 336 branches covered (100.0%)

Branch coverage included in aggregate %.

527 of 527 relevant lines covered (100.0%)

487.36 hits per line