What it solves
Firmware needs bounded diagnostics without a general logging stack.
How it works
1Event→2log record→3caller sink
Use it when
Record control-loop diagnostics
Route logs to a platform sink
Keep bounded history
Quick Start
#include "mlog.h"
/* Initialize caller-owned logger storage and emit a documented record. */Engineering evidence
- Toolkit integration example uses the inspected public header mlog.h
Known limits
- Sink timing and synchronization are caller concerns