Winbond Serial Flash Series Guide: W25X, W25Q, W25R, W25N and the Suffixes That Break Substitution

Where Winbond sourcing actually goes wrong #

Almost nobody struggles to find a Winbond serial flash datasheet. What causes rework is narrower and more expensive: a buyer is handed `W25Q128JV`, finds a dozen orderable codes that all read "128 Mbit, SPI, SOIC-8", picks whichever one has stock, and discovers three weeks later that the boot loader does not come up on the new lot.

Winbond's ordering scheme is disciplined — every letter means something specific, and the meanings are published in section 11 of each datasheet. The problem is that two of the letters change behaviour you cannot see on the board, and one of them changes the device ID that firmware reads back. Those are the letters that get dropped when a part number is retyped into an RFQ.

The LimChip catalogue currently carries 50 published Winbond codes — 33 serial NOR (27 in the W25Q line, five W25X, one W25R), five serial NAND, two parallel NAND and ten specialty DRAM. This guide covers how those families divide up, how to read a code field by field, and which suffix differences genuinely block a substitution.

The four flash families and what each one is for #

Winbond splits code-storage flash by interface and die type rather than by end market, so the family prefix tells you most of what you need.

Two boundaries in that table matter more than the rest.

The first is W25X versus W25Q. W25X predates the Quad interface, so a device such as W25X40CLSNIG runs Standard and Dual SPI up to 104 MHz on a 2.3–3.6 V rail. If a design was drawn around W25X and someone substitutes a W25Q part of the same density, the footprint usually matches and the board usually works — but the reverse is not true. A controller configured for Quad I/O has nowhere to go on a W25X die.

The second is W25Q versus W25N, which is the NOR-to-NAND boundary. Serial NAND arrives with page-based access, a 2048 + 64 byte page structure and mandatory bad-block handling. Winbond puts ECC and a bad-block lookup table on the die, which removes most of that burden from the host, but it is still not a NOR replacement: you cannot execute in place from it the way you can from a W25Q. Choosing between them is an architecture decision, not a sourcing one. If the underlying NOR/NAND distinction is the open question, our memory technology glossary covers it before you get to ordering codes.

Reading a W25Q code field by field #

Taking `W25Q128JVSIQ` apart against the W25Q128JV datasheet's ordering table:

Two practical warnings about that table.

The package letter is defined per datasheet, not across the family. On W25Q128JV the package field is a single letter — `S` for SOIC-8 208-mil, `F` for SOIC-16 300-mil, `E` for WSON 8×6 mm, `P` for WSON 6×5 mm. On the 32 Mbit part the same field is two letters, because there are more options to distinguish: `SS` and `SN` separate 208-mil from 150-mil SOIC, `ZP` and `ZE` separate the two WSON sizes, `UU` is USON 4×3 mm. And the letters are not even stable in meaning between densities — `UU` is USON 4×3 mm on W25Q32JV, while the USON option on the 16 Mbit part in our catalogue (W25Q16JVUXIQ) is `UX` and measures 2×3 mm. Read the ordering table for the density you are actually buying.

The part marking is not the part number. Winbond's own note is explicit: the `W` prefix is not marked on the device, and for WSON parts the `ZP`/`ZE` package codes are not marked either. An incoming-inspection process that compares the laser mark character-for-character against the purchase order will raise false failures on perfectly good material.

Four suffix changes that are not drop-in #

The option letter changes the device ID #

This is the one that costs the most time. On W25Q128JV, option `Q` ships with the Quad Enable bit fixed to 1 in Status Register-2 and is backward compatible with the older FV family. Option `M` ships with QE programmable and defaulted to 0, and — per the datasheet note — uses a new device ID to identify the JV family.

So `W25Q128JVSIQ` and `W25Q128JVSIM` are the same density, same 2.7–3.6 V rail, same SOIC-8 footprint, same temperature grade. They are not the same device to software. A driver that reads the JEDEC ID and matches it against a table will see something it does not recognise, and a controller that assumes Quad mode is already enabled will fall over on the `M` part. Our catalogue lists both suffixes on 128 Mbit and 64 Mbit, and they are stocked and quoted as separate items for exactly this reason. There is also an `N` option on some densities, which fixes QE to 1 like `Q` but also sets output drive strength to 75%.

1.8 V and 3 V share a footprint but not a rail #

`W25Q128JVSIQ` wants 2.7–3.6 V. `W25Q128JWSIQ` wants 1.7–1.95 V. One letter apart, physically interchangeable, electrically incompatible. This is the failure that survives visual inspection and dies at power-up, and it is easy to introduce when someone shortens a part number in an email. The 1.8 V variants are common on newer SoC platforms where the flash sits on the same rail as the low-voltage I/O bank, so both classes legitimately appear in the same BOM library.

The hardware /RESET pin only exists on two packages #

On the JV generation, a dedicated hardware `/RESET` pin is available only on the SOIC-16 and TFBGA packages. On the 8-pin and 8-pad packages, pin 7 is a shared `/HOLD` or `/RESET` function, and it is available for Standard and Dual SPI only — in Quad mode that pin is IO3.

That is why W25Q256JVFIQ exists as a distinct item from the 8-pin 256 Mbit codes: `F` is the 16-pin SOIC 300-mil body with the dedicated reset. If a design relies on asserting reset to recover a hung flash device, moving to an 8-pin package to save board area removes the mechanism. Package substitution here is a functional change, not a footprint change. The broader package vocabulary is covered in our IC package identification guide.

W25R is pin-compatible with W25Q — in one direction #

The `R` in W25R marks a Replay-Protected Monotonic Counter. Winbond introduced the family to meet Intel's RPMC specification and Microsoft's UEFI secure boot requirements, adding a SHA-256 accelerator, a 32-bit monotonic counter, a 256-bit root key that becomes inaccessible once provisioned, and a volatile HMAC key. Winbond's October 2018 announcement is clear that the parts use standard flash packages, so a PC maker can move from a standard W25Q to an RPMC-enabled W25R without redesigning the motherboard.

Read that carefully, because it only runs one way. Going W25Q → W25R adds a capability the platform can ignore. Going W25R → W25Q removes the counter a secure-boot platform is checking for, and the board will refuse to come up. There is a second trap for anyone using flash tooling: the W25R256JW carries the same JEDEC device ID as the W25Q256JW, so ID-based identification cannot tell them apart, yet the two do not support the same set of block-erase instructions. Programming infrastructure that treats device ID as sufficient identification will mis-handle one of them.

The same "invisible letter" pattern shows up on the NAND side. On the serial NAND line, the trailing option letter sets the default read mode — Winbond's own parameter tables show 1 Gbit codes shipping with Buffer Read as the default and others shipping with Continuous or Sequential Read as the default, with the other mode available as an option. Pin-compatible, same die family, different behaviour on the first read after power-up.

The trailing G that is not a different part #

One suffix worth knowing about specifically because it looks alarming: a `G` in the 13th character of a Winbond part number identifies material manufactured using renewable energy — Winbond's example is W25H02JVTBIMG against W25H02JVTBIM. All specifications and features are identical; only the electricity source used in manufacturing differs.

If a supplier offers the `…G` version against a BOM line that does not have it, that is not a substitution in any engineering sense. It is worth confirming rather than assuming, but it should not trigger a requalification.

Check lifecycle at the ordering-code level #

Winbond publishes per-code lifecycle data on its own product pages, which is more useful to a buyer than a generic family-level "active" claim. Two fields are worth pulling before you commit to a design or a large buy:

• Industrial / Automotive Status — `P` mass production, `S` samples, `UD`

under development, `N` not recommended for new design, `EOL` end of life. An `N` on the exact code you are about to design in is a decision point, even though material is still available.

• Longevity — `Y` means the code is covered by Winbond's product longevity

programme; `N` means no longevity commitment. For industrial equipment with a ten-year build life, this distinction matters more than current stock depth.

Automotive grades are listed separately and are worth checking against the real ambient requirement rather than assumed: `AG1` covers −40 to 125 °C, `AG2` −40 to 105 °C, `AG2+` −40 to 115 °C, `AG3` −40 to 85 °C. Note also that Industrial Plus (105 °C) parts are functionally tested at 105 °C while endurance testing is conducted at 85 °C — if the application genuinely cycles at the top of the range, the reliability report rather than the grade letter is the right document to read.

What a Winbond flash RFQ should contain #

Because so much of the risk here lives in the last two characters, quoting from a truncated part number is the single most common way to receive the wrong material. A usable request specifies:

• the complete orderable code, including voltage, package, temperature and

option letters — `W25Q128JVSIQ`, not "W25Q128 SOIC-8";

• whether the option letter is fixed by firmware, so an alternative suffix

can be ruled in or out immediately rather than after receipt;

• packing, because Winbond's standard bulk shipment for these SOIC parts is

tube, with tape and reel or tray specified at order time — WSON parts default to tray. Assuming reel and receiving tube stalls an SMT line;

• the acceptable date-code window, quantity and any lot-consistency

requirement, if the build is a single production run.

Conclusion #

The four Winbond families answer different questions: W25X for legacy low-density parameter storage, W25Q for mainstream boot and XIP, W25R where a platform demands rollback protection, W25N where density outgrows NOR. Within W25Q, the fields that decide whether two codes are interchangeable are not the ones that look important. Density and package are obvious and get checked. The voltage letter, the temperature grade and the option letter are single characters that get dropped in transcription — and the option letter can change the device ID that firmware matches against, which makes it a functional difference wearing the costume of a packaging code.

The practical rule is short: treat the full ordering code as the part, verify the package table in the datasheet for the specific density, and confirm the option letter against firmware expectations before approving any alternative. Our published Winbond serial flash codes are listed individually by full suffix rather than grouped by family, so the code you quote is the code you receive.

Sources #

• Winbond W25Q32JV datasheet — ordering information, package codes, /RESET pin availability and Industrial Plus test conditions.
• Winbond W25Q32JV-DTR datasheet (Rev H) — package code assignments SN/SS, ZP, XG, UU and SF.
• Winbond announcement: 1.8 V RPMC flash for PC UEFI and BIOS data, 11 October 2018 — W25R RPMC feature set, densities and package compatibility with W25Q.
• Winbond W25N-KV QSPI NAND product data — default read mode, on-chip ECC, lifecycle status, automotive grade and longevity field definitions, and the renewable-energy `G` character note.
• flashrom change 90298: add Winbond W25R256JW, December 2025 — shared device ID with W25Q256JW and the differing block-erase instruction support.