Board-level Linux integration, U-Boot, device trees, kernel drivers and peripheral bring-up. Separate power and hardware checks from software adaptation, and define a recoverable boot path.
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…
When UBIFS stops accepting writes, establish which layer became read-only and capture the first causal error. A read-only filesystem mount, a UBIFS error latch, and a read-only UBI device are related observations, but they are not interchangeable diagnoses. Repeated later EROFS results often describe the consequence rather than the initiating fault. This diagnostic method is…
Use UBIFS’s reported available space as an admission signal, then qualify the real operation and handle its actual result. A display based on physical flash capacity, an old sample, or total free blocks can show headroom that the application cannot use. Reserved space, concurrent writers, metadata growth, and the shape of a replacement operation all…
When UBI attachment fails after a flash change, compare the target’s physical geometry and expected header offsets with the image’s recorded layout before rebuilding anything. A valid image for the old geometry can be incompatible with the new attachment configuration. Reformatting first destroys the evidence needed to distinguish that mismatch from damaged data. This diagnostic…
An increasing corrected-bit counter is a reason to inspect the read workload and correction margin, not a direct estimate of remaining NAND life. Separate successful correction, a threshold-triggered warning, uncorrectable reads, and block retirement. Those observations lead to different actions. This guide is pinned to Linux v6.12 MTD and UBI. It concerns host-visible NAND correction…
Approve a NAND substitution only when its addressing geometry, correction requirement, spare-area layout, and error-reporting behavior fit every reader and writer in the product. Matching capacity and package is insufficient. A clean read on a new device can conceal an unsupported correction configuration. This procedure covers host-managed NAND integration, including the different ownership model of…
Preserve factory bad-block information before any NAND programming or erase operation. Manufacturing tools, bootloaders, operating-system drivers, and update software must agree on where that information lives and how it remains excluded from ordinary image writes. A successful firmware verify does not prove that the device’s bad-block evidence survived. This checklist concerns host-managed NAND, including SPI…
Translate a green sandbox job into a ledger of collected nodes, reached branches and checked assertions before claiming verifier coverage. A selected algorithm label does not identify every path exercised, and a skipped case contributes no successful execution evidence. This guide pins U-Boot v2024.10’s FIT verification tests. It provides an original CI review method based…
Do not assume that adding a second digest preserves compatibility with a verifier that understands only the first. Inspect how the exact format combines checks. In the U-Boot v2024.10 FIT path examined here, every enforced hash node must pass; a supported hash does not rescue an additional unsupported one. This guide builds an algorithm-capability decision…
Authenticate the representation consumed by the decoder when the selected boot format supports it, and still bound decoding resources. An authorized compressed stream can be malformed or too large for the approved memory layout. Authentication and decoder safety answer different questions. This guide pins U-Boot v2024.10’s simple-SPL FIT gzip path, with the intended required-signature policy…