W25N01GVZEIG
Product Specifications
W25N01GVZEIG - Winbond 1Gb SLC SPI NAND Flash, 104MHz Quad SPI, WSON-8
In Stock - Ready to Ship
The W25N01GVZEIG is a 1Gb (128MB) SLC SPI NAND Flash from Winbond, delivering 8x the density of a 128Mb NOR at approximately 1/3 the cost per bit. Operating at 104MHz Quad SPI (up to 416 Mbps), it combines SPI's low pin count with NAND's cost-efficient high-density storage. The 2KB+64B page architecture with on-die 1-bit ECC simplifies host-side error correction, while continuous read and buffer read modes optimize throughput for sequential data access. With 100,000 P/E cycles, 10-year retention, and industrial -40 to +85C rating, it serves as cost-effective boot media for embedded Linux, firmware storage for IoT gateways, and high-density data logging where NOR Flash capacity is insufficient and eMMC is overkill.
Key Performance Highlights
Technical Specifications
| Manufacturer | Winbond Electronics Corporation |
| Part Number | W25N01GVZEIG |
| Memory Type | SLC NAND Flash (Serial) |
| Density | 1 Gbit (128 MByte) |
| Organization | 128M x 8 bits |
| Page Size | 2,048 bytes + 64 bytes spare area |
| Block Size | 128 KB (64 pages per block) |
| Total Blocks | 1,024 blocks |
| Interface | SPI, Dual SPI, Quad SPI, QPI |
| Max Clock Frequency | 104 MHz (Quad SPI: up to 416 Mbps) |
| Page Read Time | 25 us (page to buffer), then SPI read-out |
| Page Program Time | 250 us typical |
| Block Erase Time | 2 ms typical |
| On-Die ECC | 1-bit ECC per 528-byte sector (with status register) |
| Bad Block Management | Factory-marked bad blocks, runtime BBM required |
| P/E Cycles | 100,000 minimum (SLC, per block) |
| Data Retention | 10 years |
| Supply Voltage | 2.7 V to 3.6 V (3V series) |
| Standby Current | 10 uA (typical) |
| Operating Temperature | -40C to +85C (Industrial) |
| Package | WSON-8 (8 mm x 6 mm, exposed pad) |
| RoHS | RoHS Compliant |
Product Details
SPI NAND vs SPI NOR — When to Choose Which
The W25N01GVZEIG is SPI NAND, fundamentally different from the more common SPI NOR Flash (W25Q128JV). Key architectural differences drive application fit:
NAND advantages: 1Gb at ~1/3 the cost of 1Gb NOR. Sequential read throughput is higher due to page-based internal architecture. Better for bulk data storage, file systems (UBIFS, YAFFS2), and firmware images where the entire contents are loaded into RAM on boot.
NOR advantages: Random byte access with no page read latency. True XIP (eXecute- In-Place) — code runs directly from Flash. No ECC required. Better for boot firmware, real-time code, and applications needing frequent small random reads. NAND is for storage; NOR is for code execution.
Key Applications
Embedded Linux Boot Media - Kernel, device tree, rootfs on UBIFS with UBI wear-leveling
IoT Gateway Firmware Storage - Dual-bank OTA update, factory + update partitions
Data Logging - Sensor data, event logs, configuration databases (SPIFFS, LittleFS)
Audio / Image Storage - Voice prompts, fonts, graphics, UI assets in cost-sensitive products
Automotive Telematics - Event data recorders, navigation map tiles, CAN log storage
Security Camera / DVR - Circular buffer video storage on low-cost SoCs without eMMC
Metering / Industrial - Smart meter data, PLC program storage, recipe databases
NOR vs NAND Technology Comparison
| Feature | W25Q128JV (NOR) | W25N01GVZEIG (SLC NAND) | Typical MLC NAND |
|---|---|---|---|
| Density | 128 Mb (16 MB) | 1 Gb (128 MB) | 4-16 Gb |
| Cost per Bit | Higher (3-5x) | Lower (baseline) | Lowest |
| Random Read | Excellent (byte-addressable) | Page-based (25us latency) | Page-based (slower) |
| XIP (Execute-in-Place) | Yes | No (must copy to RAM) | No |
| P/E Cycles | 100,000 | 100,000 (SLC) | 3,000-10,000 |
| Bad Block Mgmt | Not required | Required (factory + runtime) | Required |
| Filesystem | LittleFS, SPIFFS | UBIFS, YAFFS2, SPIFFS | UBIFS, F2FS, ext4 + FTL |
Why Source W25N01GVZEIG from Superb Automation?
Frequently Asked Questions
What is the difference between W25N01GV (NAND) and W25Q128JV (NOR)?
W25N01GV = SPI NAND: 1Gb, page-based access, requires ECC + bad block management, lower cost/bit, best for data storage. W25Q128JV = SPI NOR: 128Mb, random byte access, no ECC, XIP capable, best for code execution. NAND for capacity; NOR for code.
Does the W25N01GVZEIG need external ECC?
The W25N01GVZEIG has on-die 1-bit ECC per 528-byte sector, automatically correcting single-bit errors. For most consumer/industrial applications, this is sufficient. For automotive or safety-critical use, add software BCH/RS ECC in the host driver for multi-bit error correction.
Can embedded Linux boot from W25N01GV?
Many SoCs with SPI NAND BootROM support can boot directly (Allwinner F1C100s/V3s, Rockchip RV1103, some STM32MP1 configs). For SoCs without SPI NAND boot, use a small SPI NOR for U-Boot SPL and store the kernel/rootfs on W25N01GV. Check your SoC datasheet for SPI NAND boot capability.
What filesystem should I use on W25N01GV?
Linux: UBIFS on top of UBI — provides wear-leveling, bad block management, and power-fail safety. Lightweight MCU: SPIFFS or LittleFS. The Linux MTD spi-nand driver provides direct NAND access. Never use a non-NAND-aware filesystem (FAT, ext4 raw) — bad block and wear-leveling support is mandatory for production use.
How does SLC NAND reliability compare to MLC or TLC?
SLC: 100K P/E, 10yr retention — best reliability. MLC: 3K-10K P/E. TLC: ~1K P/E. SLC is the only NAND type recommended for industrial, automotive, and embedded applications where data integrity and long operating life matter. The W25N01GVZEIG is SLC — the most reliable NAND type.