Battery-powered devices have a way of turning memory specs into battery specs. Every rail in a wearable or a portable instrument is chosen at 1.8 V partly for power and partly because the SoC's memory controller lives there — which pushes flash selection into the 1.8 V class, where the PY25Q128LA from PUYA (Puya) is a natural fit: 128 Mbit of SPI NOR on a 1.8 V rail, in the industry-standard command set.
The short answer
The PY25Q128LA is the code-storage pick for 1.8 V-host designs that need 16 MB of firmware and asset space with the W/IR-suffix build options for extended temperature or industrial requirements — wearables, portable medical accessories, IoT hubs and battery instruments.
Verified device identity
From the PUYA PY25Q128LA datasheet V1.5:
| Attribute | Value |
|---|---|
| Density | 128 Mbit (16 MB) |
| Interface | SPI / QSPI NOR |
| Supply class | 1.8 V |
| Ordering suffixes | WXH-IR style build options (package/temperature/grade) |
| Family | PY25Q128H (3.3 V) / PY25Q128L·LA (1.8 V) siblings |
The LA variant carries PUYA's extended-grade build options in the WXH-IR ordering scheme — the suffix system that maps package, temperature range and grade for industrial and instrument builds.
Why the 1.8 V rail changes the flash decision
One rail for the memory bank. Modern low-power SoCs run their QSPI memory interface at 1.8 V. A 3.3 V flash on that bus means level shifters or a separate flash rail; a 1.8 V flash like the PY25Q128LA means the memory bank joins the host's rail directly — fewer parts, fewer failure points, and no level-shifter propagation delay in the QSPI timing budget.
The power maths. Flash idle current and rail voltage both feed the always-on budget of a wearable. At 1.8 V, the same leakage and standby behaviour costs roughly 45% less power than at 3.3 V — small numbers individually, but a wearable's sleep budget is audited in microamps.
Density enables the OTA pattern. 16 MB supports dual full images on wearable-class firmware — the base application plus assets, staged and validated — without a recovery-mode circus. For products that ship OTA updates as a core feature (watches, medical patches, asset trackers), the density is the enabler.
Where it lands in a battery design
Typical platform around the PY25Q128LA:
- Host — low-power SoC with 1.8 V QSPI XIP (wearable-class, BLE/Wi-Fi SoC, or MCU + radio)
- Code + assets — PY25Q128LA, 16 MB
- Working memory — PSRAM (APS/CSS 1.8 V class) or on-chip SRAM
- Calibration + counters — EEPROM (P24C-class)
The pattern covers smartwatch-class wearables, portable medical accessories, industrial hand-helds and connected-sensor hubs.
The WXH-IR suffix system, briefly
PUYA's ordering suffix encodes package, voltage, temperature and grade — the WXH-IR-style builds target extended temperature and industrial-grade expectations. For a product heading into regulated or harsh-service territory, the suffix decides whether the part's qualification story matches your document package. Send us your environmental requirements and we will map them to the exact ordering code — this is the step that prevents requalification surprises.
Frequently asked questions
PY25Q128LA versus P25Q128L — both 1.8 V, both 128 Mbit. Which one?
Same rail and density point, different families and build-option ladders. The LA's suffix system carries the extended-grade build options; the P25Q128L is the volume mainstream part. Selection comes down to the grade your programme needs and second-source policy — we supply both datasheet sets for a direct comparison.
Can my SoC execute in place from it?
If the SoC has a QSPI XIP memory-mapped controller, yes — the standard command set supports it. This is the dominant architecture on wearable-class SoCs.
What retention can I expect across the battery's life?
Code-storage flash in a battery device sees a handful of write cycles (OTA updates) across years of powered read service. SPI NOR retention under that duty is decades-class; the practical variables are legitimate sourcing and power-ramp discipline, both of which our traceability and documentation package cover.
Is 16 MB overkill for a wearable?
Under-spec it once and the OTA scheme gets complicated forever. Base firmware, graphics assets, language packs, model updates and dual-image OTA land most wearables at 8–16 MB. The 128 Mb class is the honest sizing, not the padded one.
Sourcing note
The PY25Q128LA ships through Mandu with the PUYA V1.5 datasheet and ordering-code guide. Send your platform, environmental requirements and annual volume for the exact grade mapping, samples and pricing.