|
Safe Data API
CRC-protected (optionally redundant) data containers for Zephyr
|
|
v0.0-dev+gbb519af | |
CRC-protected (optionally redundant) data containers with integrity guaranteed by construction. More...
Topics | |
| Type-Erased Core | |
| Type-erased core operations; all integrity logic in one audited place. | |
| Diagnostics and Fault Handling | |
| Integrity-event reporting: fault handler, statistics, self-test. | |
| Containers and Typed Access | |
| Typed container definition and access macros - the primary API. | |
CRC-protected (optionally redundant) data containers with integrity guaranteed by construction.
A safe container bundles a user payload with an integrity tag (CRC), an optional inverted shadow copy, and a per-container mutex. All access goes through operations that hold the lock across the whole read-modify-write and reseal the tag automatically, so a stale tag or a torn update cannot happen by construction.