What it solves
Storage drivers expose inconsistent absolute addressing and erase rules.
How it works
1Partition request→2bounds/alignment checks→3driver
Use it when
Partition a shared flash device
Validate NOR erase/write alignment
Track successful operations per partition
Quick Start
#include "mflash.h"
/* Initialize driver callbacks and caller-owned partition storage. */
/* Use partition-relative read, write and erase operations. */Engineering evidence
- Host build/test, installed consumer and ARM compile-only commands are documented
Known limits
- No global adapter state
- Partial NOR updates through erase_write are rejected
- RAM erase fills with zero rather than erased-flash bytes