NOR flash
A non-volatile flash memory architecture with cells connected in parallel, supporting random-address reads and commonly used to store executable code and firmware.
The parallel cell arrangement is not a requirement for a parallel external bus: NOR devices also use serial interfaces. Random-address reads make NOR useful for firmware, but the memory interface and controller determine how code can be fetched. [1] [2]
Byte-addressable reads do not mean arbitrary byte overwrites. Programming changes erased bits from 1 to 0; restoring 0 to 1 requires erasing the containing sector or the chip. Program units can be words or page buffers, and repeated partial programming can violate device-specific ECC rules. Consult the part's programming limits instead of treating NOR as RAM. [2]
A capable controller can expose serial flash for memory-mapped reads and execute-in-place. Program and erase may require separate command sequences or an indirect access mode. Instruction fetches can also conflict with an operation that makes the array busy; supported suspend operations permit access only outside the suspended region under the device's rules. [3] [4]
In Infineon's S29GL-T FAQ example, clearing only data bits is not enough, since new hidden parity can require a 0-to-1 transition and disable automatic ECC on a second program. Do not transfer that example to FL-S/FL-L or other families; the selected part's programming specification applies. [2]
Code executed in place must stay contiguous, uncompressed and unmoved, so its erase units are excluded from wear-leveling and the flash is split into code and data areas. [5] The Linux MTD layer models NOR as bit-writeable with a 1-byte minimum write unit, against one page for NAND. [6]
Relations
- related
- NAND flash, Bad block management, Planar NAND, Solid-state media, Execute-in-place, Byte-addressable storage, Program/erase cycle, EEPROM, EEPROM emulation, Wear leveling, NAND erase block
Limitations
- An interrupted program or erase operation can leave the target region unreliable, so firmware updates need a recovery strategy. [2]
Citations
- KIOXIA. Why Replace Embedded NOR Flash Memory with Serial NAND? March 2021, revision 3.1, pages 1-2. Cell arrangements and external interfaces.
- Infineon. NOR Flash: FAQs. Questions 2, 4, 24-25, 31, 35, 38-39 and 57. Programming units, family-specific ECC and interruption risks.
- STMicroelectronics. AN4760, Introduction to Quad-SPI interface for STM32 MCUs and MPUs, revision 5. Sections 3.3.1-3.3.3 and 6.2.
- Infineon. Program/Erase Suspend and Resume Operations in Serial NOR Flash. S25FL512S example and allowed read regions.
- Gal and Toledo. Algorithms and Data Structures for Flash Memories. Tel-Aviv University survey, 24 July 2004.
- Linux MTD layer: include/uapi/mtd/mtd-abi.h, include/linux/mtd/mtd.h and drivers/mtd/mtdcore.c.
Sources & caveats
- Source review, not a benchmark. The FL-S/FL-L repeated-program rules and S29GL-T parity-transition example are family-specific, not universal NOR behavior.
- Citation c4 uses S25FL512S as its worked suspend/resume example. Supported suspension, readable regions and state transitions remain device-specific.
- Citation c3 documents STM32 QUADSPI. Its separate memory-mapped read and indirect program/erase modes are an example, not a universal controller specification.
- The 2004 survey describes devices of its period; the kernel constants (master branch on the access date) describe software modelling, not physical limits.