1. Separate the host, device buffer and array
We use W25N01GVZEIG with BUF=1 as our example. The host holds data before sending and after receiving. The device buffer stages transfers. The nonvolatile array stores the programmed contents. A completed SPI transfer does not prove that data has reached the array.
The command examples follow the Winbond Revision R datasheet dated July 3 2023. They apply to the stated device and mode, not every NAND device.
| Stage | Data location | Remaining check |
|---|---|---|
| Read the target page | Array to device buffer | Internal read completion and applicable ECC status |
| Output read data | Buffer to host | Received contents against expectations |
| Load program data | Host to device buffer | Array update is not yet established |
| Execute page programming | Buffer to target array page | Internal completion and program result |
2. Load the selected page before reading its data
Issue Page Data Read 13h with the page address. Wait for BUSY to clear. With internal ECC enabled, check ECC-1/ECC-0 before accepting the read result.
The status categories are 00 for no correction required, 01 for a correctable 1-bit error event, and 10 for the uncorrectable 2-bit error event defined by this datasheet. They are result categories, not a detailed error count. Do not interpret 01 as correction of any 1–4 errors per page. The manual defines 11 for BUF=0 continuous reads; do not use it as a normal result in this BUF=1 example. These bits do not have the same interpretation with ECC-E=0.
An uncorrectable result is not verified valid data. Follow the project’s error handling and data checks. The status categories also do not guarantee detection of every possible multibit error.
Next, issue Read Data 03h with the column address. This selects a position within the buffer, not another array page. BUSY clearing confirms internal completion, not error-free contents. For stale output after changing pages, use our previous-page troubleshooting guide.
3. Check buffer loading and page programming separately
Before loading data, satisfy write enable with WEL=1. Check the erased-location, protection, and programming requirements for the target.
Load Program Data 02h loads the buffer and sets unloaded buffer bytes to FFh. Random Load Program Data 84h updates only the specified buffer locations. Other buffer bytes remain unchanged. Neither behavior proves that old array contents will be preserved. Loading FFh does not erase a programmed array bit from 0 to 1.
Choose the load method required by the driver and the prepared buffer contents. Then issue Program Execute 10h for the target page. Wait for BUSY to clear, check P-FAIL, and perform the project’s data verification.
Within a block, page programming must follow increasing page addresses. The starting page need not be the first page of that block. A successful readback does not waive this ordering rule.
The maximum number of partial-page program operations, NoP, is four for the entire page, including spare. With internal ECC enabled, sector-based partial programming must handle a complete 512B sector as specified. This describes the array-programming and ECC scope. Check host load length separately against the 02h/84h clauses and programming constraints.
With internal ECC enabled, if the paired spare area’s User Data I is needed, program it with that sector in the same operation. User Data I is optional; the host does not always have to fill the whole 16B spare area paired with that sector.
With internal ECC enabled, the internal calculation overwrites data loaded into ECC parity fields. Put spare metadata only in documented user areas. Avoid ECC parity fields and bad-block markers, and identify which user areas have ECC protection. Short writes do not remove page-order, NoP, or ECC requirements.
4. Check the whole block boundary before a small update
Block Erase D8h starts erasure of the selected whole block. A shorter record does not reduce that scope. Check write enable and protection first, including the applicable TB and BPx definitions in Revision R. A command sent to a protected target is not proof of erasure.
BUSY remains high during erasure, while status-register reads remain available. After completion, check E-FAIL. Command transmission, operation completion, and verified erasure are different results.
Do not verify erasure from previously buffered contents. In this BUF=1 path, issue a fresh 13h for each target page being checked. Wait for completion, then use 03h and compare the result with the expected erased state. Checking one range does not establish that the entire block was checked.
| Check | Record | Effect on the update |
|---|---|---|
| New record | Changed content and target location | Input length does not define erase scope |
| Existing contents | Other valid data in the block | If erasing, plan preservation or migration |
| Programming constraints | Page order, NoP, partial-page and ECC rules | A short write does not allow RAM-style overwriting |
| Buffer loading | 02h or 84h and prepared contents | Their buffer behavior does not establish array-data preservation |
| Verification | Result status and required data checks | Use a fresh 13h and subsequent 03h for this target-page read path |
First decide whether the chosen update method needs an erase. If it does, include the block’s other valid data in the preservation or migration design. This conceptual example does not require erasure for every small change. It is not a board-tested power-loss-safe procedure.
5. Carry the complete sequence into selection and driver review
Record the full part number, read mode, page and block organization, result states, and host management responsibilities. Matching capacity and an SPI interface does not establish compatibility. Use our SPI NAND selection guide when considering another device.
Keep page order, NoP, 02h/84h buffer behavior, and ECC status checks in the review. Record internal results separately from the project’s data validation. This distinguishes buffer loaded, array programmed, and data accepted. We explain the operating layers here; we do not report board-test results.
Keep the complete part number, read mode, and record-update method with the quantity request. Compare candidates against the same buffer flow, erase scope, page-order and NoP limits, load-command behavior, and driver checks. For a SUNTEC quotation, provide the part number, quantity, and unresolved integration requirements.
Prepared by the SUNTEC Technical Team at Suzhou Shengyatai Electronics Co., Ltd.
