Apply a default only when the setting’s documented policy permits it. A missing record, a malformed or integrity-failing record, and an explicitly cleared value carry different information. If firmware maps all three to the same fallback, it can silently undo an operator’s choice or conceal a storage fault. This article defines an original six-byte application…
Programming internal flash can block execution that still needs the affected flash bank. Moving one programming function to RAM is not enough if an interrupt vector, handler, helper function or constant remains in that bank. Qualify the complete access dependency path and the exact device’s concurrent-operation rules. The concrete example is a 2-Mbyte STM32F429 dual-bank…
Use a layout parser when factory data has a defined structure but cell offsets vary with preceding records. The parser locates the fields and creates named NVMEM cells; consumers request those names rather than copying a byte offset from one sample EEPROM image. This article uses the Linux 6.12 NVMEM interface and the stable v6.12.100…
Copying an existing filesystem image to a larger device preserves the image’s logical layout. Extra physical bytes become usable only when every intervening boundary permits them: driver addressing, region ownership, filesystem geometry, and application policy. Diagnose the first unchanged boundary before attempting a resize. The concrete filesystem example is littlefs v2.11.2 with unchanged logical block…
Gate the first storage read on the external flash’s actual exit-from-power-down sequence, not merely on the MCU’s wake event or the SPI controller becoming available. The device may still ignore ordinary commands while the software considers the system awake. The concrete example here is Microchip SST25PF040C, datasheet DS20005397E, with a separate Zephyr v4.2.0 SPI-NOR driver…
Measure raw-flash amplification with separate ledgers for useful application payload, filesystem program requests, and erase operations by block. A single “bytes written” counter cannot explain whether a settings workload creates extra programming, repeatedly erases a small region, or merely repeats unchanged application requests. This method uses littlefs v2.11.2 callbacks as one observation boundary. It targets…
A flash ring log needs an explicit erase-eligibility rule before it wraps: a sector may be reclaimed only when every record it contains is eligible for removal. If an incident pins even one record in that sector, ordinary rotation must stop or use a separately qualified retention path. Finite storage cannot guarantee unlimited recording and…
Recover an append-only log by accepting a contiguous prefix of fully validated records and stopping at the first incomplete or invalid frame. Return both the accepted records and the exact stop offset. Do not search for the next familiar marker and silently join data across an unexplained gap. This article defines an original, synthetic framing…
A UBI volume with an unfinished whole-volume update can be deliberately unavailable before UBIFS gets a chance to interpret its contents. Check the per-volume update marker and the updater’s completion evidence first. The marker identifies an incomplete replacement state; it does not provide an automatic rollback copy of the previous image. This guide targets the…
Treat an NVMEM cell as bytes with a documented consumer format. Validate the returned length and version, decode each field with explicit byte order and signedness, then check its meaning before use. Casting the buffer to a native C structure can accidentally depend on CPU byte order, alignment, and compiler layout. This guide is pinned…