StrataFlash P30-T Data Sheet

Intel StrataFlash® Embedded Memory
(P30) Family
Datasheet
Product Features
■ High performance ■ Security
— 85 ns initial access — One-Time Programmable Registers:
— 52 MHz with zero wait states, 17ns clock-to- • 64 unique factory device identifier bits
data output synchronous-burst read mode • 64 user-programmable OTP bits
— 25 ns asynchronous-page read mode • Additional 2048 user-programmable OTP bits
— 4-, 8-, 16-, and continuous-word burst mode — Selectable OTP Space in Main Array:
— Buffered Enhanced Factory Programming • Four pre-defined 128-KByte blocks (top or
(BEFP) at 5 μs/byte (Typ) bottom configuration)
— 1.8 V buffered programming at 7 μs/byte (Typ) • Full Chip (top or bottom configuration)
— Absolute write protection: V PP = VSS
■ Architecture
— Power-transition erase/program lockout
— Multi-Level Cell Technology: Highest Density
at Lowest Cost — Individual zero-latency block locking
— Asymmetrically-blocked architecture — Individual block lock-down
— Four 32-KByte parameter blocks: top or ■ Software
bottom configuration — 20 μs (Typ) program suspend
— 128-KByte main blocks — 20 μs (Typ) erase suspend
■ Voltage and Power — Intel® Flash Data Integrator optimized
— VCC (core) voltage: 1.7 V – 2.0 V — Basic Command Set and Extended Command
— VCCQ (I/O) voltage: 1.7 V – 3.6 V Set compatible
— Standby current: 55 μA (Typ) for 256-Mbit — Common Flash Interface capable
— 4-Word synchronous read current: ■ Density and Packaging
13 mA (Typ) at 40 MHz — 56- Lead TSOP package (64, 128, 256, 512-
■ Quality and Reliability Mbit)
— Operating temperature: –40 °C to +85 °C — 64- Ball Intel® Easy BGA package (64, 128,
— Minimum 100,000 erase cycles per block 256, 512- Mbit)
— ETOX™ VIII process technology (130 nm) — Intel® QUAD+ SCSP (64, 128, 256, 512-
Mbit)
— 16-bit wide data bus
The Intel StrataFlash® Embedded Memory (P30) product is the latest generation of Intel
StrataFlash® memory devices. Offered in 64-Mbit up through 512-Mbit densities, the P30 device
brings reliable, two-bit-per-cell storage technology to the embedded flash market segment.
Benefits include more density in less space, high-speed interface, lowest cost-per-bit NOR
device, and support for code and data storage. Features include high-performance synchronous-
burst read mode, fast asynchronous access times, low power, flexible security options, and three
industry standard package choices. The P30 product family is manufactured using Intel® 130 nm
ETOX™ VIII process technology.
Order Number: 306666, Revision: 007

1-May-2006
INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL® PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY
Le ga l Lin es an d Discla ime rs
ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN
INTEL'S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER, AND INTEL DISCLAIMS
ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES
RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER
INTELLECTUAL PROPERTY RIGHT. Intel products are not intended for use in medical, life saving, life sustaining, critical control or safety systems, or
in nuclear facility applications.
Intel may make changes to specifications and product descriptions at any time, without notice.
Intel Corporation may have patents or pending patent applications, trademarks, copyrights, or other intellectual property rights that relate to the
presented subject matter. The furnishing of documents and other materials and information does not provide any license, express or implied, by
estoppel or otherwise, to any such patents, trademarks, copyrights, or other intellectual property rights.
The Intel StrataFlash® Embedded Memory (P30) Family may contain design defects or errors known as errata which may cause the product to deviate
from published specifications. Current characterized errata are available on request.
Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing your product order.
Copies of documents which have an order number and are referenced in this document, or other Intel literature may be obtained by calling
1-800-548-4725 or by visiting Intel's website at http://www.intel.com.
Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
*Other names and brands may be claimed as the property of others.
Copyright © 2006, Intel Corporation. All Rights Reserved.
1-May-2006 Intel StrataFlash® Embedded Memory (P30) Datasheet

2 Order Number: 306666, Revision: 007
Intel StrataFlash® Embedded Memory (P30) Family
Contents
1.0 Introduction ...............................................................................................................................7
1.1 Nomenclature ....................................................................................................................... 7
1.2 Acronyms.............................................................................................................................. 7
1.3 Conventions.......................................................................................................................... 8
2.0 Functional Overview ..............................................................................................................9
2.1 Virtual Chip Enable Description ............................................................................................ 9
3.0 Package Information ............................................................................................................11
3.1 56-Lead TSOP Package..................................................................................................... 11
3.2 64-Ball Easy BGA Package ................................................................................................ 13
3.3 QUAD+ SCSP Packages.................................................................................................... 15
4.0 Ballout and Signal Descriptions...................................................................................... 18
4.1 Signal Ballout......................................................................................................................18
4.2 Signal Descriptions .............................................................................................................21
4.3 Dual-Die Configurations......................................................................................................24
4.4 Memory Maps ..................................................................................................................... 25
5.0 Maximum Ratings and Operating Conditions ...........................................................28
5.1 Absolute Maximum Ratings ................................................................................................ 28
5.2 Operating Conditions .......................................................................................................... 29
6.0 Electrical Specifications ..................................................................................................... 30
6.1 DC Current Characteristics................................................................................................. 30
6.2 DC Voltage Characteristics................................................................................................. 32
7.0 AC Characteristics ................................................................................................................33
7.1 AC Test Conditions.............................................................................................................33
7.2 Capacitance........................................................................................................................ 34
7.3 AC Read Specifications ......................................................................................................35
7.4 AC Write Specifications ......................................................................................................41
7.5 Program and Erase Characteristics.................................................................................... 45
8.0 Power and Reset Specifications .....................................................................................46
8.1 Power Up and Down...........................................................................................................46
8.2 Reset Specifications ........................................................................................................... 46
8.3 Power Supply Decoupling...................................................................................................47
9.0 Device Operations ................................................................................................................. 48
9.1 Bus Operations ...................................................................................................................48
9.1.1 Reads .................................................................................................................... 48
9.1.2 Writes..................................................................................................................... 49
9.1.3 Output Disable ....................................................................................................... 49
9.1.4 Standby.................................................................................................................. 49
9.1.5 Reset .....................................................................................................................49
9.2 Device Commands .............................................................................................................50
Datasheet Intel StrataFlash® Embedded Memory (P30) 1-May-2006

Order Number: 306666, Revision: 007 3
9.3 Command Definitions ......................................................................................................... 51

10.0 Read Operations .................................................................................................................... 53
10.1 Asynchronous Page-Mode Read........................................................................................ 53
10.2 Synchronous Burst-Mode Read.......................................................................................... 53
10.3 Read Configuration Register .............................................................................................. 54
10.3.1 Read Mode ............................................................................................................ 55
10.3.2 Latency Count........................................................................................................ 55
10.3.3 WAIT Polarity......................................................................................................... 57
10.3.4 Data Hold............................................................................................................... 58
10.3.5 WAIT Delay............................................................................................................ 59
10.3.6 Burst Sequence ..................................................................................................... 59
10.3.7 Clock Edge ............................................................................................................ 59
10.3.8 Burst Wrap............................................................................................................. 59
10.3.9 Burst Length .......................................................................................................... 60
11.0 Programming Operations .................................................................................................. 61
11.1 Word Programming............................................................................................................. 61
11.1.1 Factory Word Programming................................................................................... 62
11.2 Buffered Programming........................................................................................................ 62
11.3 Buffered Enhanced Factory Programming ......................................................................... 63
11.3.1 BEFP Requirements and Considerations .............................................................. 63
11.3.2 BEFP Setup Phase................................................................................................ 64
11.3.3 BEFP Program/Verify Phase ................................................................................. 64
11.3.4 BEFP Exit Phase ................................................................................................... 65
11.4 Program Suspend............................................................................................................... 65
11.5 Program Resume................................................................................................................ 66
11.6 Program Protection............................................................................................................. 66
12.0 Erase Operations ................................................................................................................... 67
12.1 Block Erase......................................................................................................................... 67
12.2 Erase Suspend ................................................................................................................... 67
12.3 Erase Resume .................................................................................................................... 68
12.4 Erase Protection ................................................................................................................. 68
13.0 Security Modes ....................................................................................................................... 69
13.1 Block Locking...................................................................................................................... 69
13.1.1 Lock Block ............................................................................................................. 69
13.1.2 Unlock Block .......................................................................................................... 69
13.1.3 Lock-Down Block ................................................................................................... 69
13.1.4 Block Lock Status .................................................................................................. 70
13.1.5 Block Locking During Suspend.............................................................................. 70
13.2 Selectable One-Time Programmable Blocks...................................................................... 71
13.3 Protection Registers ........................................................................................................... 72
13.3.1 Reading the Protection Registers .......................................................................... 73
13.3.2 Programming the Protection Registers.................................................................. 73
13.3.3 Locking the Protection Registers ........................................................................... 73
14.0 Special Read States ............................................................................................................. 74
14.1 Read Status Register.......................................................................................................... 74
14.1.1 Clear Status Register............................................................................................. 75

14.2 Read Device Identifier ........................................................................................................ 75

14.3 CFI Query ........................................................................................................................... 76
Appendix A Write State Machine .......................................................................................... 77
Appendix B Flowcharts ............................................................................................................84
Appendix C Common Flash Interface ................................................................................ 92
Appendix D Additional Information ...................................................................................102
Appendix E Ordering Information for Discrete Products ........................................103
Appendix F Ordering Information for SCSP Products ..............................................104

Revision History
Revision Date Revision Description
April 2005 -001 Initial Release

Revised discrete memory maps in Section 4.4, “Memory Maps” on page 25
Added memory maps for 512-Mbit top parameter devices in Section 4.4, “Memory
Maps” on page 25
Fixed size of Programming Region for 256-Mbit to be 8-Mbit in Section 4.4,
“Memory Maps” on page 25 and Section 11.0, “Programming Operations” on
August 2005 -002 page 61
Removed power supply sequencing requirement in Section 8.1, “Power Up and
Down” on page 46
Updated conditions for Table 14 “Capacitance” on page 34
Updated CFI table in Appendix C, “Common Flash Interface”
Added note to Table 28 “Device ID codes” on page 76 for stacked Device ID codes
Synchronous burst read operation is currently not supported for the TSOP
September 2005 -003 package
Updated 512-Mbit Easy BGA Ball Height (symbol A1) in Figure 2 “Easy BGA
Mechanical Specifications” on page 13
November 2005 -004 Updated read access speed for 265M TSOP package
February 2006 -005 Removed all references to 1 Gigabit.
• Added 52 MHz capabilities,
• Added TSOP Package information for 512 Mb throughout the document,
• Added Section 2.1, “Virtual Chip Enable Description” on page 9,
• Modified figures in Section 4.3, “Dual-Die Configurations” on page 24,
April 2006 -006 • Modified Table 9 “512-Mbit Top and Bottom Parameter Memory Map (Easy
BGA and QUAD+ SCSP)” on page 27,
• Modified Notes 5 & 6 to Reset Specifications table in Section 8.2, “Reset
Specifications” on page 46,
• Added additional note on 512 Mb capability in Table 25 “Selectable OTP Block
Mapping” on page 71.
• Table 15 “AC Read Specifications for 64/128- Mbit Densities” and Table 16
May 2006 -007
“AC Read Specifications for 256/512-Mbit Densities” were updated for 52 MHz

1.0 Introduction
This document provides information about the Intel StrataFlash® Embedded Memory (P30) device
and describes its features, operation, and specifications.
1.1 Nomenclature
1.8 V: VCC (core) voltage range of 1.7 V – 2.0 V

3.0 V: VCCQ (I/O) voltage range of 1.7 V – 3.6 V
9.0 V: VPP voltage range of 8.5 V – 9.5 V
Block: A group of bits, bytes, or words within the flash memory array that
erase simultaneously when the Erase command is issued to the
device. The Intel StrataFlash® Embedded Memory (P30) Family
has two block sizes: 32-KByte and 128-KByte.
Main block: An array block that is usually used to store code and/or data. Main
blocks are larger than parameter blocks.
Parameter block: An array block that is usually used to store frequently changing
data or small system parameters that traditionally would be stored
in EEPROM.
Top parameter device: A device with its parameter blocks located at the highest physical
address of its memory map.
Bottom parameter device: A device with its parameter blocks located at the lowest physical
address of its memory map.
1.2 Acronyms
BEFP: Buffer Enhanced Factory Programming

CUI: Command User Interface
MLC: Multi-Level Cell
OTP: One-Time Programmable
PLR: Protection Lock Register
PR: Protection Register
RCR: Read Configuration Register
RFU: Reserved for Future Use
SR: Status Register
WSM: Write State Machine

1.3 Conventions
VCC: Signal or voltage connection

VCC: Signal or voltage level
0x: Hexadecimal number prefix
0b: Binary number prefix
SR[4]: Denotes an individual register bit.
A[15:0]: Denotes a group of similarly named signals, such as address or data bus.
A5: Denotes one element of a signal group membership, such as an individual address bit.
Bit: Binary unit
Byte: Eight bits
Word: Two bytes, or sixteen bits
Kbit: 1024 bits
KByte: 1024 bytes
KWord: 1024 words
Mbit: 1,048,576 bits
MByte: 1,048,576 bytes
MWord: 1,048,576 words

2.0 Functional Overview
This section provides an overview of the features and capabilities of the Intel StrataFlash®
Embedded Memory (P30) Family.
The P30 family provides density upgrades from 64-Mbit through 512-Mbit. This family of devices
provides high performance at low voltage on a 16-bit data bus. Individually erasable memory
blocks are sized for optimum code and data storage.
Upon initial power up or return from reset, the device defaults to asynchronous page-mode read.
Configuring the Read Configuration Register enables synchronous burst-mode reads. In
synchronous burst mode, output data is synchronized with a user-supplied clock signal. A WAIT
signal provides an easy CPU-to-flash memory synchronization.
In addition to the enhanced architecture and interface, the device incorporates technology that
enables fast factory program and erase operations. Designed for low-voltage systems, the
Intel StrataFlash® Embedded Memory (P30) Family supports read operations with VCC at 1.8 V,
and erase and program operations with VPP at 1.8 V or 9.0 V. Buffered Enhanced Factory
Programming (BEFP) provides the fastest flash array programming performance with VPP at 9.0 V,
which increases factory throughput. With VPP at 1.8 V, VCC and VPP can be tied together for a
simple, ultra low power design. In addition to voltage flexibility, a dedicated VPP connection
provides complete data protection when VPP ≤ VPPLK.
A Command User Interface (CUI) is the interface between the system processor and all internal
operations of the device. An internal Write State Machine (WSM) automatically executes the
algorithms and timings necessary for block erase and program. A Status Register indicates erase or
program completion and any errors that may have occurred.
An industry-standard command sequence invokes program and erase automation. Each erase
operation erases one block. The Erase Suspend feature allows system software to pause an erase
cycle to read or program data in another block. Program Suspend allows system software to pause
programming to read other locations. Data is programmed in word increments (16 bits).
The Intel StrataFlash® Embedded Memory (P30) Family protection register allows unique flash
device identification that can be used to increase system security. The individual Block Lock
feature provides zero-latency block locking and unlocking. In addition, the P30 device also has
four pre-defined spaces in the main array that can be configured as One-Time Programmable
(OTP).
2.1 Virtual Chip Enable Description

The Intel StrataFlash® Embedded Memory (P30) Family 512Mbit devices employ a Virtual Chip
Enable which combines two 256-Mbit die with a common chip enable, F1-CE# for Quad+
packages or CE# for Easy BGA and TSOP packages. (Refer to Figure 9 on page 24 and Figure 10
on page 24). Address A24 (Quad+ package) or A25 (Easy BGA and TSOP packages) is then used
to select between the die pair with F1-CE# / CE# asserted depending upon the package option used.
When chip enable is asserted and Quad+ A24 (EasyBGA/TSOP A25) is low (VIL), The lower
parameter die is selected; when chip enable is asserted and Quad+ A24 (EasyBGA/TSOP A25) is
high (VIH), the upper parameter die is selected. Refer to Table 1 and Table 2 for additional details.

Table 1. Virtual Chip Enable Truth Table for 512Mb (Quad+ Package)
Die Selected F1-CE# A24
Lower Param Die L L

Upper Param Die L H
Table 2. Virtual Chip Enable Truth Table for 512Mb (EasyBGA & TSOP packages)
Die Selected CE# A25
Lower Param Die L L

Upper Param Die L H

3.0 Package Information
3.1 56-Lead TSOP Package
Figure 1. TSOP Mechanical Specifications
Z
See Note 2 A2
See Notes 1 and 3
Pin 1
e
E See Detail B
D1 A1
D Seating
Plane
See Detail A
Detail A
Detail B
0 b
L
[231369-90]
Table 3. TSOP Package Dimensions (Sheet 1 of 2)

Millimeters Inches
Product Information Symbol Notes
Min Nom Max Min Nom Max
Package Height A - - 1.200 - - 0.047
Standoff A1 0.050 - - 0.002 - -
Package Body Thickness A2 0.965 0.995 1.025 0.038 0.039 0.040
Lead Width b 0.100 0.150 0.200 0.004 0.006 0.008
Lead Thickness c 0.100 0.150 0.200 0.004 0.006 0.008
Package Body Length D1 18.200 18.400 18.600 0.717 0.724 0.732 4
Package Body Width E 13.800 14.000 14.200 0.543 0.551 0.559 4

Table 3. TSOP Package Dimensions (Sheet 2 of 2)

Millimeters Inches
Lead Pitch e - 0.500 - - 0.0197 -
Terminal Dimension D 19.800 20.00 20.200 0.780 0.787 0.795
Lead Tip Length L 0.500 0.600 0.700 0.020 0.024 0.028
Lead Count N - 56 - - 56 -
Lead Tip Angle ∅ 0° 3° 5° 0° 3° 5°
Seating Plane Coplanarity Y - - 0.100 - - 0.004
Lead to Package Offset Z 0.150 0.250 0.350 0.006 0.010 0.014
Notes:
1. One dimple on package denotes Pin 1.
2. If two dimples, then the larger dimple denotes Pin 1.
3. Pin 1 will always be in the upper left corner of the package, in reference to the product mark.
4. Daisy Chain Evaluation Unit information is at Intel® Flash Memory Packaging Technology
http://developer.intel.com/design/flash/packtech.

3.2 64-Ball Easy BGA Package
Figure 2. Easy BGA Mechanical Specifications
Ball A1 Ball A1
Corner Corner
D S1
1 2 3 4 5 6 7 8 8 7 6 5 4 3 2 1 S2
A A
B B
C C
D D b
E
E E
F F
G G
e
H H
Top View - Ball side down Bottom View - Ball Side Up
A1
A2
A
Seating
Plane
Y
Note: Drawing not to scale
Table 4. Easy BGA Package Dimensions (Sheet 1 of 2)

Millimeters Inches
Package Height (64/128/256-Mbit) A - - 1.200 - - 0.0472

Package Height (512-Mbit) A - - 1.300 - - 0.0512
Ball Height A1 0.250 - - 0.0098 - -
Package Body Thickness (64/128/256-Mbit) A2 - 0.780 - - 0.0307 -
Package Body Thickness (512-Mbit) A2 - 0.910 - - 0.0358 -
Ball (Lead) Width b 0.330 0.430 0.530 0.0130 0.0169 0.0209
Package Body Width D 9.900 10.000 10.100 0.3898 0.3937 0.3976 1
Package Body Length E 12.900 13.000 13.100 0.5079 0.5118 0.5157 1
Pitch [e] - 1.000 - - 0.0394 -
Ball (Lead) Count N - 64 - - 64 -

Table 4. Easy BGA Package Dimensions (Sheet 2 of 2)

Millimeters Inches
Corner to Ball A1 Distance Along D S1 1.400 1.500 1.600 0.0551 0.0591 0.0630 1
Corner to Ball A1 Distance Along E S2 2.900 3.000 3.100 0.1142 0.1181 0.1220 1
Notes:
1. Daisy Chain Evaluation Unit information is at Intel® Flash Memory Packaging Technology
http://developer.intel.com/design/flash/packtech.

3.3 QUAD+ SCSP Packages
Figure 3. 64/128-Mbit, 88-ball (80 active) QUAD+ SCSP Specifications (8x10x1.2 mm)
A1 Index S1
Mark
1 2 3 4 5 6 7 8 8 7 6 5 4 3 2 1
S2
A A
B B
C C
D D
E E
F F
D
e
G G
H H
J J
K K
L L
M M
b
E
Top View - Ball

Bottom View - Ball Up
Down
A2
A1 A
D raw ing not to sc ale.
Millimeters Inches
Dimensions Symbol Min Nom Max Min Nom Max
Package Height A - - 1.200 - - 0.0472
Ball Height A1 0.200 - - 0.0079 - -
Package Body Thickness A2 - 0.860 - - 0.0339 -
Ball (Lead) Width b 0.325 0.375 0.425 0.0128 0.0148 0.0167
Package Body Width D 9.900 10.000 10.100 0.3898 0.3937 0.3976
Package Body Length E 7.900 8.000 8.100 0.3110 0.3150 0.3189
Pitch e - 0.800 - - 0.0315 -
Corner to Ball A1 Distance Along E S1 1.100 1.200 1.300 0.0433 0.0472 0.0512
Corner to Ball A1 Distance Along D S2 0.500 0.600 0.700 0.0197 0.0236 0.0276

Figure 4. 256-Mbit, 88-ball (80 active) QUAD+ SCSP Specifications (8x11x1.0 mm)
A 1 Index S1
Mark
1 2 3 4 5 6 7 8 8 7 6 5 4 3 2 1
S2
A A
B B
C C
D D
E E
F F
D e
G G
H H
J J
K K
L L
M M
b
E
Top View - Ball Down Bottom View - Ball Up

A2
A1 A
D raw ing not to scale.
Note: Dimensions A1, A2, and b are preliminary

Millimeters Inches
Package Height A - - 1.000 - - 0.0394
Ball Height A1 0.117 - - 0.0046 - -
Ball (Lead) Width b 0.300 0.350 0.400 0.0118 0.0138 0.0157
Package Body Length D 10.900 11.00 11.100 0.4291 0.4331 0.4370
Package Body Width E 7.900 8.00 8.100 0.3110 0.3150 0.3189
Pitch e - 0.80 - - 0.0315 -

Figure 5. 512-Mbit, 88-ball (80 active) QUAD+ SCSP Specifications (8x11x1.2 mm)
A 1 Index S1
Mark
1 2 3 4 5 6 7 8 8 7 6 5 4 3 2 1
S2
A A
B B
C C
D D
E E
F F
D e
G G
H H
J J
K K
L L
M M
b
E
Top View - Ball Down Bottom View - Ball Up

A2
A1 A
D raw ing not to scale .
Millimeters Inches
Package Height A - - 1.200 - - 0.0472
Ball Height A1 0.200 - - 0.0079 - -
Ball (Lead) Width b 0.325 0.375 0.425 0.0128 0.0148 0.0167
Package Body Length D 10.900 11.000 11.100 0.4291 0.4331 0.4370
Package Body Width E 7.900 8.000 8.100 0.3110 0.3150 0.3189
Pitch e - 0.800 - - 0.0315 -

4.0 Ballout and Signal Descriptions
4.1 Signal Ballout
Figure 6. 56-Lead TSOP Pinout (64/128/256/512- Mbit)
A16 1 56 WAIT
A15 2 55 A17
A14 3 54 DQ15
A13 4 53 DQ7
A12 5 52 DQ14
A11 6 51 DQ6
A10 7 50 DQ13
A9 8 49 DQ5
A23 9 48 DQ12
A22 10 47 DQ4
A21 11 46 ADV#
Intel StrataFlash®
VSS 12 45 CLK
Embedded Memory (P30)
VCC 13 44 RST#
WE# 14 43 VPP
56-Lead TSOP Pinout 42 DQ11
WP# 15
16 14 mm x 20 mm 41 DQ3
A20
A19 17 40 DQ10
18 Top View 39 DQ2
A18
A8 19 38 VCCQ
A7 20 37 DQ9
A6 21 36 DQ1
A5 22 35 DQ8
A4 23 34 DQ0
A3 24 33 VCC
A2 25 32 OE#
A24 26 31 VSS
A25 27 30 CE#
VSS 28 29 A1
Notes:
1. A1 is the least significant address bit.
2. A23 is valid for 128-Mbit densities and above; otherwise, it is a no connect (NC).
3. A24 is valid for 256-Mbit densities; otherwise, it is a no connect (NC).
5. Synchronous burst read operation is currently not supported for the TSOP package. The synchronous
read input signals (i.e. ADV# and CLK) should be tied off to support asynchronous reads. See Section
4.2, “Signal Descriptions” on page 21.

Figure 7. 64-Ball Easy BGA Ballout (64/128/256/512-Mbit)
1 2 3 4 5 6 7 8 8 7 6 5 4 3 2 1
A A
A1 A6 A8 VPP A13 VCC A18 A22 A22 A18 VCC A13 VPP A8 A6 A1
B B
A2 VSS A9 CE# A14 A25 A19 RFU RFU A19 A25 A14 CE# A9 VSS A2
C C
A3 A7 A10 A12 A15 WP# A20 A21 A21 A20 WP# A15 A12 A10 A7 A3
D D
A4 A5 A11 RST# VCCQ VCCQ A16 A17 A17 A16 VCCQ VCCQ RST# A11 A5 A4
E E
DQ8 DQ1 DQ9 DQ3 DQ4 CLK DQ15 RFU RFU DQ15 CLK DQ4 DQ3 DQ9 DQ1 DQ8
F F
RFU DQ0 DQ10 DQ11 DQ12 ADV# WAIT OE# OE# WAIT ADV# DQ12 DQ11 DQ10 DQ0 RFU
G G
A23 RFU DQ2 VCCQ DQ5 DQ6 DQ14 WE# WE# DQ14 DQ6 DQ5 VCCQ DQ2 RFU A23
H H
RFU VSS VCC VSS DQ13 VSS DQ7 A24 A24 DQ7 VSS DQ13 VSS VCC VSS RFU
Easy BGA Easy BGA

Top View- Ball side down Bottom View- Ball side up
Notes:
1. A1 is the least significant address bit.

Figure 8. 88-Ball (80-Active Ball) QUAD+ SCSP Ballout
Pin 1
1 2 3 4 5 6 7 8
A DU DU Depop Depop Depop Depop DU DU A
B A4 A18 A19 VSS VCC VCC A21 A11 B
C A5 RFU A23 VSS RFU CLK A22 A12 C
D A3 A17 A24 VPP RFU RFU A9 A13 D
E A2 A7 RFU WP# ADV# A20 A10 A15 E
F A1 A6 RFU RST# WE# A8 A14 A16 F
G A0 DQ8 DQ2 DQ10 DQ5 DQ13 WAIT F2-CE# G
H RFU DQ0 DQ1 DQ3 DQ12 DQ14 DQ7 F2-OE# H
J RFU F1-OE# DQ9 DQ11 DQ4 DQ6 DQ15 VCCQ J
K F1-CE# RFU RFU RFU RFU VCC VCCQ RFU K
L VSS VSS VCCQ VCC VSS VSS VSS VSS L
M DU DU Depop Depop Depop Depop DU DU M
1 2 3 4 5 6 7 8
Notes:
4. F2-CE# and F2-OE# are no connect (NC) for all densities.

4.2 Signal Descriptions

This section has signal descriptions for the various P30 packages.
Table 5. TSOP and Easy BGA Signal Descriptions (Sheet 1 of 2)

Symbol Type Name and Function
ADDRESS INPUTS: Device address inputs. 64-Mbit: A[22:1]; 128-Mbit: A[23:1]; 256-Mbit: A[24:1];
A[MAX:1] Input 512-Mbit: A[25:1]. Note: The virtual selection of the 256-Mbit “Top parameter” die in the dual-die 512-
Mbit configuration is accomplished by setting A[25] high (VIH).
DATA INPUT/OUTPUTS: Inputs data and commands during write cycles; outputs data during
Input/
DQ[15:0] memory, Status Register, Protection Register, and Read Configuration Register reads. Data balls
Output
float when the CE# or OE# are deasserted. Data is internally latched during writes.
ADDRESS VALID: Active low input. During synchronous read operations, addresses are latched on
the rising edge of ADV#, or on the next valid CLK edge with ADV# low, whichever occurs first.
ADV# Input In asynchronous mode, the address is latched when ADV# going high or continuously flows through
if ADV# is held low.
WARNING: Designs not using ADV# must tie it to VSS to allow addresses to flow through.
FLASH CHIP ENABLE: Active low input. CE# low selects the associated flash memory die. When
asserted, flash internal control logic, input buffers, decoders, and sense amplifiers are active. When
CE# Input deasserted, the associated flash die is deselected, power is reduced to standby levels, data and
WAIT outputs are placed in high-Z state.
WARNING: All chip enables must be high when device is not in use.
CLOCK: Synchronizes the device with the system’s bus frequency in synchronous-read mode.
During synchronous read operations, addresses are latched on the rising edge of ADV#, or on the
CLK Input next valid CLK edge with ADV# low, whichever occurs first.
WARNING: Designs not using CLK for synchronous read mode must tie it to VCCQ or VSS.
OUTPUT ENABLE: Active low input. OE# low enables the device’s output data buffers during read
OE# Input
cycles. OE# high places the data outputs and WAIT in High-Z.
RESET: Active low input. RST# resets internal automation and inhibits write operations. This
RST# Input provides data protection during power transitions. RST# high enables normal operation. Exit from
reset places the device in asynchronous read array mode.
WAIT: Indicates data valid in synchronous array or non-array burst reads. Read Configuration
Register bit 10 (RCR[10], WT) determines its polarity when asserted. WAIT’s active output is VOL or
VOH when CE# and OE# are VIL. WAIT is high-Z if CE# or OE# is VIH.
WAIT Output
• In synchronous array or non-array read modes, WAIT indicates invalid data when asserted and
valid data when deasserted.
• In asynchronous page mode, and all write modes, WAIT is deasserted.
WRITE ENABLE: Active low input. WE# controls writes to the device. Address and data are latched
WE# Input
on the rising edge of WE#.
WRITE PROTECT: Active low input. WP# low enables the lock-down mechanism. Blocks in lock-
WP# Input down cannot be unlocked with the Unlock command. WP# high overrides the lock-down function
enabling blocks to be erased or programmed using software commands.
Erase and Program Power: A valid voltage on this pin allows erasing or programming. Memory
contents cannot be altered when VPP ≤ VPPLK. Block erase and program at invalid VPP voltages
should not be attempted.
Set VPP = VPPL for in-system program and erase operations. To accommodate resistor or diode
Power/
VPP drops from the system supply, the VIH level of VPP can be as low as VPPL min. VPP must remain
Input
above VPPL min to perform in-system flash modification. VPP may be 0 V during read operations.
VPPH can be applied to main blocks for 1000 cycles maximum and to parameter blocks for 2500
cycles. VPP can be connected to 9 V for a cumulative total not to exceed 80 hours. Extended use of
this pin at 9 V may reduce block cycling capability.
Device Core Power Supply: Core (logic) source voltage. Writes to the flash array are inhibited when
VCC Power
VCC ≤ VLKO. Operations at invalid VCC voltages should not be attempted.

Table 5. TSOP and Easy BGA Signal Descriptions (Sheet 2 of 2)

VCCQ Power Output Power Supply: Output-driver source voltage.

VSS Power Ground: Connect to system ground. Do not float any VSS connection.
Reserved for Future Use: Reserved by Intel for future device functionality and enhancement. These
RFU —
should be treated in the same way as a Do Not Use (DU) signal.
DU — Do Not Use: Do not connect to any other signal, or power supply; must be left floating.
NC — No Connect: No internal connection; can be driven or floated.
Table 6. QUAD+ SCSP Signal Descriptions (Sheet 1 of 2)

ADDRESS INPUTS: Device address inputs. 64-Mbit: A[21:0]; 128-Mbit: A[22:0]; 256-Mbit: A[23:0];
A[MAX:0] Input 512-Mbit: A[24:0]. Note: The virtual selection of the 256-Mbit “Top parameter” die in the dual-die 512-
Mbit configuration is accomplished by setting A[25] high (VIH).
DATA INPUT/OUTPUTS: Inputs data and commands during write cycles; outputs data during
Input/
DQ[15:0] memory, Status Register, Protection Register, and Read Configuration Register reads. Data balls
Output
float when the CE# or OE# are deasserted. Data is internally latched during writes.
ADDRESS VALID: Active low input. During synchronous read operations, addresses are latched on
the rising edge of ADV#, or on the next valid CLK edge with ADV# low, whichever occurs first.
ADV# Input In asynchronous mode, the address is latched when ADV# going high or continuously flows through
if ADV# is held low.
WARNING: Designs not using ADV# must tie it to VSS to allow addresses to flow through.
FLASH CHIP ENABLE: Active low input. CE# low selects the associated flash memory die. When
asserted, flash internal control logic, input buffers, decoders, and sense amplifiers are active. When
F1-CE# Input deasserted, the associated flash die is deselected, power is reduced to standby levels, data and
WAIT outputs are placed in high-Z state.
WARNING: All chip enables must be high when device is not in use.
CLOCK: Synchronizes the device with the system’s bus frequency in synchronous-read mode.
During synchronous read operations, addresses are latched on the rising edge of ADV#, or on the
CLK Input next valid CLK edge with ADV# low, whichever occurs first.
WARNING: Designs not using CLK for synchronous read mode must tie it to VCCQ or VSS.
OUTPUT ENABLE: Active low input. OE# low enables the device’s output data buffers during read
F1-OE#
Input cycles. OE# high places the data outputs and WAIT in High-Z.
F2-OE#
F1-OE# and F2-OE# should be tied together for all densities.
RESET: Active low input. RST# resets internal automation and inhibits write operations. This
RST# Input provides data protection during power transitions. RST# high enables normal operation. Exit from
reset places the device in asynchronous read array mode.
WAIT: Indicates data valid in synchronous array or non-array burst reads. Read Configuration
Register bit 10 (RCR[10], WT) determines its polarity when asserted. WAIT’s active output is VOL or
VOH when CE# and OE# are VIL. WAIT is high-Z if CE# or OE# is VIH .
WAIT Output
• In synchronous array or non-array read modes, WAIT indicates invalid data when asserted and
valid data when deasserted.
• In asynchronous page mode, and all write modes, WAIT is deasserted.
WRITE ENABLE: Active low input. WE# controls writes to the device. Address and data are latched
WE# Input
on the rising edge of WE#.
WRITE PROTECT: Active low input. WP# low enables the lock-down mechanism. Blocks in lock-
WP# Input down cannot be unlocked with the Unlock command. WP# high overrides the lock-down function
enabling blocks to be erased or programmed using software commands.

Table 6. QUAD+ SCSP Signal Descriptions (Sheet 2 of 2)

Erase and Program Power: A valid voltage on this pin allows erasing or programming. Memory
contents cannot be altered when VPP ≤ VPPLK. Block erase and program at invalid VPP voltages
should not be attempted.
Set VPP = VPPL for in-system program and erase operations. To accommodate resistor or diode
Power/
VPP drops from the system supply, the VIH level of VPP can be as low as VPPL min. VPP must remain
lnput
above VPPL min to perform in-system flash modification. VPP may be 0 V during read operations.
VPPH can be applied to main blocks for 1000 cycles maximum and to parameter blocks for 2500
cycles. VPP can be connected to 9 V for a cumulative total not to exceed 80 hours. Extended use of
this pin at 9 V may reduce block cycling capability.
Device Core Power Supply: Core (logic) source voltage. Writes to the flash array are inhibited when
VCC Power
VCC ≤ VLKO. Operations at invalid VCC voltages should not be attempted.
VCCQ Power Output Power Supply: Output-driver source voltage.
VSS Power Ground: Connect to system ground. Do not float any VSS connection.
Reserved for Future Use: Reserved by Intel for future device functionality and enhancement. These
RFU —
should be treated in the same way as a Do Not Use (DU) signal.
DU — Do Not Use: Do not connect to any other signal, or power supply; must be left floating.
NC — No Connect: No internal connection; can be driven or floated.

4.3 Dual-Die Configurations
Figure 9. 512-Mbit Easy BGA and TSOP Top or Bottom Parameter Block
Diagram
Easy BGA & TSOP 512-Mbit (Dual-Die) Top or Bottom Parameter

Configuration
CE#
Top Param Die
RST#
WP# (256-Mbit)
VCC
OE#
VPP
WE#
CLK VCCQ
ADV# VSS
Bottom Param Die

(256-Mbit)
DQ[15:0]
A[MAX:1]
WAIT
Figure 10. 512-Mbit QUAD+ SCSP Top or Bottom Parameter Block Diagram
QUAD+ 512-Mbit (Dual-Die) Top or Bottom Parameter

Configuration
F1-CE#
Top Param Die
RST#
WP# (256-Mbit)
VCC
OE#
VPP
WE#
CLK VCCQ
ADV# VSS
Bottom Param Die

(256-Mbit)
DQ[15:0]
A[MAX:0]
WAIT

4.4 Memory Maps

Table 7 through Table 9 show the P30 memory maps. The memory array is divided into multiple 8-
Mbit Programming Regions (see Section 11.0, “Programming Operations” on page 61).
Table 7. Discrete Top Parameter Memory Maps (all packages)

Size Size
Blk 64-Mbit Blk 128-Mbit
(KB) (KB)
32 66 3FC000 - 3FFFFF 32 130 7FC000 - 7FFFFF

Programming
Programming
...
...
...
...
...
...
Region
Region
32 63 3F0000 - 3F3FFF 32 127 7F0000 - 7F3FFF
One
One
128 62 3E0000 - 3EFFFF 128 126 7E0000 - 7EFFFF
...
...
...
...
...
...
128 56 380000 - 38FFFF 128 120 780000 - 78FFFF
128 55 370000 - 37FFFF 128 119 770000 - 77FFFF
Programming
Programming
128 54 360000 - 36FFFF 128 118 760000 - 76FFFF
Regions
Regions
Fifteen
Seven
...
...
...
...
...
...
128 1 010000 - 01FFFF 128 1 010000 - 01FFFF
128 0 000000 - 00FFFF 128 0 000000 - 00FFFF
Size
Blk 256-Mbit
(KB)
32 258 FFC000 - FFFFFF

Programming
...
...
...
Region
32 255 FF0000 - FF3FFF

One
128 254 FE0000 - FEFFFF

...
...
...
128 248 F80000 - F8FFFF

128 247 F70000 - F7FFFF
Programming
Thirty-One
128 246 F60000 - F6FFFF

Regions
...
...
...
128 1 010000 - 01FFFF

128 0 000000 - 00FFFF

Table 8. Discrete Bottom Parameter Memory Maps (all packages)

Size Size
Blk 64-Mbit Blk 128-Mbit
(KB) (KB)
Programming 128 66 3F0000 - 3FFFFF 128 130 7F0000 - 7FFFFF
Programming
128 65 3E0000 - 3EFFFF 128 129 7E0000 - 7EFFFF
Regions
Regions
Fifteen
Seven
...
...
...
...
...
...
128 12 090000 - 09FFFF 128 12 090000 - 09FFFF
128 11 080000 - 08FFFF 128 11 080000 - 08FFFF
128 10 070000 - 07FFFF 128 10 070000 - 07FFFF
Programming
Programming
...
...
...
...
...
...
Region
Region
128 4 010000 - 01FFFF 128 4 010000 - 01FFFF
One
One
32 3 00C000 - 00FFFF 32 3 00C000 - 00FFFF
...
...
...
...
...
...
32 0 000000 - 003FFF 32 0 000000 - 003FFF
Size
Blk 256-Mbit
(KB)
128 258 FF0000 - FFFFFF

Programming
Thirty-One
128 257 FE0000 - FEFFFF

Regions
...
...
...
128 12 090000 - 09FFFF

128 11 080000 - 08FFFF
128 10 070000 - 07FFFF
Programming
...
...
...
Region
128 4 010000 - 01FFFF

One
32 3 00C000 - 00FFFF
...
...
...
32 0 000000 - 003FFF

Note: The Dual- Die P30 memory maps are the same for both parameter options because the devices
employ virtual chip enable (Refer to Section 2.1). The parameter option only defines the placement
of bottom parameter die.
Table 9. 512-Mbit Top and Bottom Parameter Memory Map (Easy BGA and QUAD+ SCSP)
512-Mbit Flash (2x256-Mbit w/ 1CE)
Size
Die Stack Config Blk Address Range
(KB)
32 517 1FFC000 - 1FFFFFF
...
...
...
256-Mbit 32 514 1FF0000 - 1FF3FFF
Top Parameter Die 128 513 1FE0000 - 1FEFFFF
...
...
...
128 259 1000000 - 100FFFF
128 258 FF0000 - FFFFFF

...
...
...
256-Mbit 128 4 010000 - 01FFFF
Bottom Parameter Die 32 3 00C000 - 00FFFF
...
...
...
32 0 000000 - 003FFF
Note: Refer to 256-Mbit Memory Map (Table 7 and Table 8) for Programming Region
information.

5.0 Maximum Ratings and Operating Conditions
5.1 Absolute Maximum Ratings

Warning: Stressing the device beyond the “Absolute Maximum Ratings” may cause permanent damage.
These are stress ratings only.
Parameter Maximum Rating Notes
Temperature under bias –40 °C to +85 °C

Storage temperature –65 °C to +125 °C
Voltage on any signal (except VCC, VPP) –0.5 V to +4.1 V 1
VPP voltage –0.2 V to +10 V 1,2,3
VCC voltage –0.2 V to +2.5 V 1
VCCQ voltage –0.2 V to +4.1 V 1
Output short circuit current 100 mA 4
Notes:
1. Voltages shown are specified with respect to VSS. Minimum DC voltage is –0.5 V on
input/output signals and –0.2 V on VCC, VCCQ, and VPP. During transitions, this level
may undershoot to –2.0 V for periods less than 20 ns. Maximum DC voltage on VCC is
VCC + 0.5 V, which, during transitions, may overshoot to VCC + 2.0 V for periods less
than 20 ns. Maximum DC voltage on input/output signals and VCCQ is VCCQ + 0.5 V,
which, during transitions, may overshoot to VCCQ + 2.0 V for periods less than 20 ns.
2. Maximum DC voltage on VPP may overshoot to +11.5 V for periods less than 20 ns.
3. Program/erase voltage is typically 1.7 V – 2.0 V. 9.0 V can be applied for 80 hours
maximum total, to any blocks for 1000 cycles maximum. 9.0 V program/erase voltage
may reduce block cycling capability.
4. Output shorted for no more than one second. No more than one output shorted at a
time.

5.2 Operating Conditions

Note: Operation beyond the “Operating Conditions” is not recommended and extended exposure beyond
the “Operating Conditions” may affect device reliability.
Table 10. Operating Conditions

Symbol Parameter Min Max Units Notes
TC Operating Temperature –40 +85 °C 1

VCC VCC Supply Voltage 1.7 2.0
CMOS inputs 1.7 3.6
VCCQ I/O Supply Voltage
TTL inputs 2.4 3.6 V
VPPL VPP Voltage Supply (Logic Level) 0.9 3.6
VPPH Factory word programming VPP 8.5 9.5
tPPH Maximum VPP Hours VPP = VPPH - 80 Hours
2
Main and Parameter Blocks VPP = VPPL 100,000 -
Block
Erase Main Blocks VPP = VPPH - 1000 Cycles
Cycles
Parameter Blocks VPP = VPPH - 2500
NOTES:
1. TC = Case Temperature.
2. In typical operation VPP program voltage is VPPL.

6.0 Electrical Specifications
6.1 DC Current Characteristics
Table 11. DC Current Characteristics (Sheet 1 of 2)

CMOS Inputs TTL Inputs
(VCCQ = (VCCQ =
Sym Parameter 1.7 V - 3.6 V) 2.4 V - 3.6 V) Unit Test Conditions Notes
Typ Max Typ Max
VCC = VCCMax
ILI Input Load Current - ±1 - ±2 μA VCCQ = VCCQMax
VIN = VCCQ or VSS
1
Output VCC = VCCMax
ILO Leakage DQ[15:0], WAIT - ±1 - ±10 μA VCCQ = VCCQMax
Current VIN = VCCQ or VSS
64-Mbit 20 35 20 35 VCC = VCCMax
VCCQ = VCCQMax
ICCS , VCC Standby, 128-Mbit 30 75 30 75 CE# = VCCQ
μA 1,2
ICCD Power Down 256-Mbit 55 115 55 200 RST# = VCCQ (for ICCS)
RST# = VSS (for ICCD)
512-Mbit 110 230 110 400 WP# = VIH
Asynchronous Single-
1-Word
Word f = 5 MHz (1 14 16 14 16 mA
Read
CLK)
Page-Mode Read 4-Word
9 10 9 10 mA
f = 13 MHz (5 CLK) Read
13 17 n/a n/a mA BL = 4W
Average VCC = VCC Max
VCC 15 19 n/a n/a mA BL = 8W
ICCR Synchronous Burst CE# = VIL
Read 1
f = 40 MHz 17 21 n/a n/a mA BL = 16W OE# = VIH
Current
21 26 n/a n/a mA BL = Cont. Inputs: VIL or VIH
16 19 n/a n/a mA BL = 4W
Synchronous Burst 19 23 n/a n/a mA BL = 8W

f = 52MHz 22 26 n/a n/a mA BL = 16W
23 28 n/a n/a mA BL = Cont.
VPP = VPPL, pgm/ers in
36 51 36 51 1,3,5
ICCW, VCC Program Current, progress
mA
ICCE VCC Erase Current VPP = VPPH, pgm/ers in
26 33 26 33 1,3,5
progress
64-Mbit 20 35 20 35
VCC Program
ICCWS, Suspend Current, 128-Mbit 30 75 30 75 CE# = VCCQ; suspend in
μA 1,3,4
ICCES VCC Erase 256-Mbit 55 115 55 200 progress
Suspend Current
512-Mbit 110 230 110 400

Table 11. DC Current Characteristics (Sheet 2 of 2)

CMOS Inputs TTL Inputs
(VCCQ = (VCCQ =
Sym Parameter 1.7 V - 3.6 V) 2.4 V - 3.6 V) Unit Test Conditions Notes
Typ Max Typ Max
IPPS, VPP Standby Current,

VPP = VPPL, suspend in
IPPWS, VPP Program Suspend Current, 0.2 5 0.2 5 μA 1,3
progress
IPPES VPP Erase Suspend Current
IPPR VPP Read 2 15 2 15 μA VPP = VPPL 1,3
VPP = VPPL, program in
0.05 0.10 0.05 0.10
progress
IPPW VPP Program Current mA
VPP = VPPH, program in
8 22 8 22
progress
0.05 0.10 0.05 0.10 VPP = VPPL, erase in progress
IPPE VPP Erase Current mA
8 22 8 22 VPP = VPPH, erase in progress
Notes:
1. All currents are RMS unless noted. Typical values at typical VCC, TC = +25 °C.
2. ICCS is the average current measured over any 5 ms time interval 5 μs after CE# is deasserted.
3. Sampled, not 100% tested.
4. ICCES is specified with the device deselected. If device is read while in erase suspend, current is ICCES plus ICCR.
5. ICCW, ICCE measured over typical or max times specified in Section 7.5, “Program and Erase Characteristics” on
page 45.

6.2 DC Voltage Characteristics
Table 12. DC Voltage Characteristics

CMOS Inputs TTL Inputs (1)
(VCCQ = 1.7 V – 3.6 V) (VCCQ = 2.4 V – 3.6 V)
Sym Parameter Unit Test Condition Notes
Min Max Min Max
VIL Input Low Voltage 0 0.4 0 0.6 V

2
VIH Input High Voltage VCCQ – 0.4 V VCCQ 2.0 VCCQ V
VCC = VCCMin
VOL Output Low Voltage - 0.1 - 0.1 V VCCQ = VCCQMin
IOL = 100 μA
VCC = VCCMin
VOH Output High Voltage VCCQ – 0.1 - VCCQ – 0.1 - V VCCQ = VCCQMin
IOH = –100 μA
VPPLK VPP Lock-Out Voltage - 0.4 - 0.4 V 3
VLKO VCC Lock Voltage 1.0 - 1.0 - V
VLKOQ VCCQ Lock Voltage 0.9 - 0.9 - V
NOTES:
1. Synchronous read mode is not supported with TTL inputs.
2. VIL can undershoot to –0.4 V and VIH can overshoot to VCCQ + 0.4 V for durations of 20 ns or less.
3. VPP ≤ VPPLK inhibits erase and program operations. Do not use VPPL and VPPH outside their valid ranges.

7.0 AC Characteristics
7.1 AC Test Conditions
Figure 11. AC Input/Output Reference Waveform
VCCQ
Input VCCQ/2 Test Points VCCQ/2 Output
0V
IO_REF.WMF
Note: AC test inputs are driven at VCCQ for Logic "1" and 0 V for Logic "0." Input/output timing begins/ends at
VCCQ/2. Input rise and fall times (10% to 90%) < 5 ns. Worst case speed occurs at VCC = VCCMin.
Figure 12. Transient Equivalent Testing Load Circuit
Device
Out
Under Test
CL
NOTES:
1. See the following table for component values.
2. Test configuration component value for worst case speed conditions.
3. CL includes jig capacitance
.
Table 13. Test Configuration Component Value For Worst Case Speed Conditions
Test Configuration CL (pF)
VCCQMin Standard Test 30
Figure 13. Clock Input AC Waveform
R201
VIH
CLK [C]
VIL
R202 R203

7.2 Capacitance
Table 14. Capacitance

Parameter Signals Min Typ Max Unit Condition Note
Address, Data, Typ temp = 25 °C,
CE#, WE#, OE#, Max temp = 85 °C,
Input Capacitance 2 6 7 pF
RST#, CLK, VCC = (0 V - 2.0 V), 1,2,3
ADV#, WP# VCCQ = (0 V - 3.6 V),
Output Capacitance Data, WAIT 2 4 5 pF Discrete silicon die

7.3 AC Read Specifications
Table 15. AC Read Specifications for 64/128- Mbit Densities (Sheet 1 of 2)

Num Symbol Parameter Min Max Unit Notes
Asynchronous Specifications
R1 tAVAV Read cycle time 85 - ns
R2 tAVQV Address to output valid - 85 ns
R3 tELQV CE# low to output valid - 85 ns
R4 tGLQV OE# low to output valid - 25 ns 1,2
R5 tPHQV RST# high to output valid - 150 ns 1
R6 tELQX CE# low to output in low-Z 0 - ns 1,3
R7 tGLQX OE# low to output in low-Z 0 - ns 1,2,3
R8 tEHQZ CE# high to output in high-Z - 24 ns
R9 tGHQZ OE# high to output in high-Z - 24 ns 1,3
R10 tOH Output hold from first occurring address, CE#, or OE# change 0 - ns
R11 tEHEL CE# pulse width high 20 - ns

1
R12 tELTV CE# low to WAIT valid - 17 ns
R13 tEHTZ CE# high to WAIT high-Z - 20 ns 1,3
R15 tGLTV OE# low to WAIT valid - 17 ns 1
R16 tGLTX OE# low to WAIT in low-Z 0 - ns

1,3
R17 t GHTZ OE# high to WAIT in high-Z - 20 ns
Latching Specifications
R101 tAVVH Address setup to ADV# high 10 - ns
R102 tELVH CE# low to ADV# high 10 - ns
R103 tVLQV ADV# low to output valid - 85 ns 1
R104 tVLVH ADV# pulse width low 10 - ns
R105 tVHVL ADV# pulse width high 10 - ns
R106 tVHAX Address hold from ADV# high 9 - ns 1,4
R108 tAPA Page address access - 25 ns

1
R111 tphvh RST# high to ADV# high 30 - ns
Clock Specifications
R200 fCLK CLK frequency - 52 MHz
R201 tCLK CLK period 19.2 - ns

1,3,5,6
R202 tCH/CL CLK high/low time 5 - ns
R203 tFCLK/RCLK CLK fall/rise time - 3 ns

(5,6)
Synchronous Specifications
R301 tAVCH/L Address setup to CLK 9 - ns
R302 tVLCH/L ADV# low setup to CLK 9 - ns

1
R303 tELCH/L CE# low setup to CLK 9 - ns
R304 tCHQV / tCLQV CLK to output valid - 17 ns

Table 15. AC Read Specifications for 64/128- Mbit Densities (Sheet 2 of 2)

R305 tCHQX Output hold from CLK 3 - ns 1,7
R306 tCHAX Address hold from CLK 10 - ns 1,4,7
R307 tCHTV CLK to WAIT valid - 17 ns 1,7
R311 tCHVL CLK Valid to ADV# Setup 3 - ns 1
R312 tCHTX WAIT Hold from CLK 3 - ns 1,7
NOTES:
1. See Figure 11, “AC Input/Output Reference Waveform” on page 33 for timing measurements and max allowable input
slew rate.
2. OE# may be delayed by up to tELQV – tGLQV after CE#’s falling edge without impact to tELQV.
4. Address hold in synchronous burst mode is tCHAX or tVHAX , whichever timing specification is satisfied first.
5. Synchronous burst read operation is currently not supported for the TSOP package.
6. Synchronous read mode is not supported with TTL level inputs.
7. Applies only to subsequent synchronous reads.
Table 16. AC Read Specifications for 256/512-Mbit Densities (Sheet 1 of 2)

Num Symbol Parameter Speed Min Max Unit Notes
Asynchronous Specifications
VCC = 1.8 V – 2.0 V 85 -
R1 tAVAV Read cycle time VCC = 1.7 V – 2.0 V 88 - ns

256/512-Mb TSOP 95
packages
VCC = 1.8 V – 2.0 V - 85
VCC = 1.7 V – 2.0 V - 88

R2 tAVQV Address to output valid ns
256/512-Mb TSOP - 95
packages
VCC = 1.8 V – 2.0 V - 85
VCC = 1.7 V – 2.0 V - 88

R3 tELQV CE# low to output valid ns
256/512-Mb TSOP - 95
packages
R4 tGLQV OE# low to output valid - 25 ns 1,2
R5 tPHQV RST# high to output valid - 150 ns 1
R6 tELQX CE# low to output in low-Z 0 - ns 1,3
R7 tGLQX OE# low to output in low-Z 0 - ns 1,2,3
R8 tEHQZ CE# high to output in high-Z - 24 ns
R9 tGHQZ OE# high to output in high-Z - 24 ns 1,3
R10 tOH Output hold from first occurring address, CE#, or OE# change 0 - ns
R11 tEHEL CE# pulse width high 20 - ns

1
R12 tELTV CE# low to WAIT valid - 17 ns
R13 tEHTZ CE# high to WAIT high-Z - 20 ns 1,3
R15 tGLTV OE# low to WAIT valid - 17 ns 1
R16 tGLTX OE# low to WAIT in low-Z 0 - ns

1,3
R17 tGHTZ OE# high to WAIT in high-Z - 20 ns

Table 16. AC Read Specifications for 256/512-Mbit Densities (Sheet 2 of 2)

Num Symbol Parameter Speed Min Max Unit Notes
Latching Specifications
R101 tAVVH Address setup to ADV# high 10 - ns
R102 tELVH CE# low to ADV# high 10 - ns
VCC = 1.8 V – 2.0 V - 85
R103 tVLQV ADV# low to output valid VCC = 1.7 V – 2.0 V - 88 ns 1

256/512-Mb TSOP - 95
packages
R104 tVLVH ADV# pulse width low 10 - ns
R105 tVHVL ADV# pulse width high 10 - ns
R106 tVHAX Address hold from ADV# high 9 - ns 1,4
R108 tAPA Page address access - 25 ns

1
R111 tphvh RST# high to ADV# high 30 - ns
Clock Specifications
R200 fCLK CLK frequency - 52 MHz
R201 tCLK CLK period 19.2 - ns

1,3,5,6
R202 tCH/CL CLK high/low time 5 - ns
R203 tFCLK/RCLK CLK fall/rise time - 3 ns

(5,6)
Synchronous Specifications
R301 tAVCH/L Address setup to CLK 9 - ns
R302 tVLCH/L ADV# low setup to CLK 9 - ns

1
R303 tELCH/L CE# low setup to CLK 9 - ns
R304 tCHQV / tCLQV CLK to output valid - 17 ns
R305 tCHQX Output hold from CLK 3 - ns 1,7
R306 tCHAX Address hold from CLK 10 - ns 1,4,7
R307 tCHTV CLK to WAIT valid - 17 ns 1,7
R311 tCHVL CLK Valid to ADV# Setup 3 - ns 1
R312 tCHTX WAIT Hold from CLK 3 - ns 1,7
NOTES:
1. See Figure 11, “AC Input/Output Reference Waveform” on page 33 for timing measurements and max allowable input
slew rate.
2. OE# may be delayed by up to tELQV – tGLQV after CE#’s falling edge without impact to tELQV.
4. Address hold in synchronous burst mode is tCHAX or tVHAX, whichever timing specification is satisfied first.
5. Synchronous burst read operation is currently not supported for the TSOP package.
6. Synchronous read mode is not supported with TTL level inputs.
7. Applies only to subsequent synchronous reads.

Figure 14. Asynchronous Single-Word Read (ADV# Low)
R1
R2
Address [A]
ADV#
R3 R8
CE# [E}
R4 R9
OE# [G]
R15 R17
WAIT [T]
R7
R6
Data [D/Q]
R5
RST# [P]
Note: WAIT shown deasserted during asynchronous read mode (RCR[10]=0, Wait asserted low).
Figure 15. Asynchronous Single-Word Read (ADV# Latch)
R1
R2
Address [A]
A[1:0][A]
R101
R105 R106
ADV#
R3 R8
CE# [E}
R4 R9
OE# [G]
R15 R17
WAIT [T]
R7
R6 R10
Data [D/Q]

Figure 16. Asynchronous Page-Mode Read Timing
R1
R2
A[Max:2] [A]
A[1:0]
R101
R105 R106
ADV#
R3 R8
CE# [E]
R4 R10
OE# [G]
R15 R17
WAIT [T]
R7 R108 R9
DATA [D/Q]
Figure 17. Synchronous Single-Word Array or Non-array Read Timing
R301 R306
CLK [C]
R2
Address [A]
R101 R106
R105
R104
ADV# [V]
R303
R102
R3 R8
CE# [E]
R7 R9
OE# [G]
R15 R307 R312 R17

WAIT [T]
R4
R304 R305
Data [D/Q]
1. WAIT is driven per OE# assertion during synchronous array or non-array read, and can be configured to
assert either during or one data cycle before valid data.
2. This diagram illustrates the case in which an n-word burst is initiated to the flash memory array and it is
terminated by CE# deassertion after the first word in the burst.

Figure 18. Continuous Burst Read, Showing An Output Delay Timing
R301
R302
R306 R304 R304 R304
CLK [C]
R2
R101
Address [A]
R106
R105
ADV# [V]
R303
R102
R3
CE# [E]
OE# [G]
R15 R307 R312

WAIT [T]
R304
R4
R7 R305 R305 R305 R305
Data [D/Q]
Notes:
1. WAIT is driven per OE# assertion during synchronous array or non-array read, and can be configured to
assert either during or one data cycle before valid data.
2. At the end of Word Line; the delay incurred when a burst access crosses a 16-word boundary and the
starting address is not 4-word boundary aligned.
Figure 19. Synchronous Burst-Mode Four-Word Read Timing

y
R302
R301 R306
CLK [C]
R2
R101
Address [A] A
R105 R106
R102
ADV# [V]
R303
R3 R8
CE# [E]
R9
OE# [G]
R15 R307 R17

WAIT [T]
R4 R304
R7 R304 R305 R10
Data [D/Q] Q0 Q1 Q2 Q3
Note: WAIT is driven per OE# assertion during synchronous array or non-array read. WAIT asserted during
initial latency and deasserted during valid data (RCR[10] = 0, Wait asserted low).

7.4 AC Write Specifications

Table 17. AC Write Specifications
Num Symbol Parameter Min Max Units Notes
W1 tPHWL RST# high recovery to WE# low 150 - ns 1,2,3

W2 tELWL CE# setup to WE# low 0 - ns 1,2,3
W3 tWLWH WE# write pulse width low 50 - ns 1,2,4
W4 tDVWH Data setup to WE# high 50 - ns
W5 tAVWH Address setup to WE# high 50 - ns
W6 tWHEH CE# hold from WE# high 0 - ns 1,2
W7 tWHDX Data hold from WE# high 0 - ns
W8 tWHAX Address hold from WE# high 0 - ns
W9 tWHWL WE# pulse width high 20 - ns 1,2,5
W10 tVPWH VPP setup to WE# high 200 - ns
1,2,3,7
W11 tQVVL VPP hold from Status read 0 - ns
W12 tQVBL WP# hold from Status read 0 - ns
1,2,3,7
W13 tBHWH WP# setup to WE# high 200 - ns
W14 tWHGL WE# high to OE# low 0 - ns 1,2,9
W16 tWHQV WE# high to read valid tAVQV + 35 - ns 1,2,3,6,10
Write to Asynchronous Read Specifications
W18 tWHAV WE# high to Address valid 0 - ns 1,2,3,6,8
Write to Synchronous Read Specifications
W19 tWHCH/L WE# high to Clock valid 19 - ns
1,2,3,6,10
W20 tWHVH WE# high to ADV# high 19 - ns
Write Specifications with Clock Active
W21 tVHWL ADV# high to WE# low - 20 ns
1,2,3,11
W22 tCHWL Clock high to WE# low - 20 ns
Notes:
1. Write timing characteristics during erase suspend are the same as write-only operations.
2. A write operation can be terminated with either CE# or WE#.
4. Write pulse width low (tWLWH or tELEH) is defined from CE# or WE# low (whichever occurs last) to CE#
or WE# high (whichever occurs first). Hence, tWLWH = tELEH = tWLEH = tELWH.
5. Write pulse width high (tWHWL or tEHEL) is defined from CE# or WE# high (whichever occurs first) to
CE# or WE# low (whichever occurs last). Hence, tWHWL = tEHEL = tWHEL = tEHWL).
6. tWHVH or tWHCH/L must be met when transitioning from a write cycle to a synchronous burst read.
7. VPP and WP# should be at a valid level until erase or program success is determined.
8. This specification is only applicable when transitioning from a write cycle to an asynchronous read.
See spec W19 and W20 for synchronous read.
9. When doing a Read Status operation following any command that alters the Status Register, W14 is
20 ns.
10. Add 10 ns if the write operation results in a RCR or block lock status change, for the subsequent read
operation to reflect this change.
11. These specs are required only when the device is in a synchronous mode and clock is active during
address setup phase.

Figure 20. Write-to-Write Timing
W5 W8 W5 W8
Address [A]
W2 W6 W2 W6
CE# [E}
W3 W9 W3
WE# [W]
OE# [G]
W4 W7 W4 W7
Data [D/Q]
W1
RST# [P]
Figure 21. Asynchronous Read-to-Write Timing
R1
R2 W5 W8
Address [A]
R3 R8
CE# [E}
R4 R9
OE# [G]
W2 W3 W6
WE# [W]
R15 R17
WAIT [T]
R7 W7
R6 R10 W4
Data [D/Q] Q D
R5
RST# [P]
Note: WAIT deasserted during asynchronous read and during write. WAIT High-Z during write per OE#
deasserted.

Figure 22. Write-to-Asynchronous Read Timing
W5 W8 R1
Address [A]
ADV# [V]
W2 W6 R10
CE# [E}
W3 W18
WE# [W]
W14
OE# [G]
R15 R17
WAIT [T]
R4
R2 R8
W4 W7 R3 R9
Data [D/Q] D Q
W1
RST# [P]
Figure 23. Synchronous Read-to-Write Timing
Latency Count
R301
R302
R306
CLK [C]
R2 W5
R101 W18
Address [ A]
R105 R106
R102 R104
ADV# [ V]
R303
R11
R3 R13 W6
CE# [E]
R4
R8
OE# [G]
W21
W21 W22
W 22 W8 W15
W2 W3 W9
WE#
R16 R307 R312

WAIT [T]
R304
R7 R305 W7
Dat a [D/Q] Q D D
Note: WAIT shown deasserted and High-Z per OE# deassertion during write operation (RCR[10]=0, Wait asserted low). Clock is
ignored during write operation.

Figure 24. Write-to-Synchronous Read Timing
R302
R301
R2
CLK
W5 W8 R306
Address [A]
R106
R104
ADV#
W6 R303
W2 R11
CE# [E}
W18
W19
W3 W20
WE# [W]
R4
OE# [G]
R15 R307
WAIT [T]
W7 R304 R305
W4 R3 R304
Data [D/Q] D Q Q
W1
RST# [P]
Note: WAIT shown deasserted and High-Z per OE# deassertion during write operation (RCR[10]=0, Wait asserted low).

7.5 Program and Erase Characteristics
VPPL VPPH
Num Symbol Parameter Units Notes
Min Typ Max Min Typ Max
Conventional Word Programming
Program Single word - 90 200 - 85 190
W200 tPROG/W μs 1
Time Single cell - 30 60 - 30 60
Buffered Programming
W200 tPROG/W Program Single word - 90 200 - 85 190
μs 1
W251 tBUFF Time 32-word buffer - 440 880 - 340 680
Buffered Enhanced Factory Programming
W451 tBEFP/W Single word n/a n/a n/a - 10 - 1,2
tBEFP/ Program μs
W452 BEFP Setup n/a n/a n/a 5 - - 1
Setup
Erasing and Suspending
W500 tERS/PB 32-KByte Parameter - 0.4 2.5 - 0.4 2.5
Erase Time s
W501 tERS/MB 128-KByte Main - 1.2 4.0 - 1.0 4.0
1
W600 tSUSP/P Suspend Program suspend - 20 25 - 20 25
μs
W601 tSUSP/E Latency Erase suspend - 20 25 - 20 25
Notes:
1. Typical values measured at TC = +25 °C and nominal voltages. Performance numbers are valid for all
speed versions. Excludes system overhead. Sampled, but not 100% tested.
2. Averaged over entire device.

8.0 Power and Reset Specifications
8.1 Power Up and Down

Power supply sequencing is not required if VPP is connected to VCC or VCCQ. Otherwise VCC
and VCCQ should attain their minimum operating voltage before applying VPP.
Power supply transitions should only occur when RST# is low. This protects the device from
accidental programming or erasure during power transitions.
8.2 Reset Specifications

Asserting RST# during a system reset is important with automated program/erase devices because
systems typically expect to read from flash memory when coming out of reset. If a CPU reset
occurs without a flash memory reset, proper CPU initialization may not occur. This is because the
flash memory may be providing status information, instead of array data as expected. Connect
RST# to the same active low reset signal used for CPU initialization.
Also, because the device is disabled when RST# is asserted, it ignores its control inputs during
power-up/down. Invalid bus conditions are masked, providing a level of memory protection.

P1 tPLPH RST# pulse width low 100 - ns 1,2,3,4
RST# low to device reset during erase - 25 1,3,4,7
P2 tPLRH
RST# low to device reset during program - 25 μs 1,3,4,7
P3 tVCCPH VCC Power valid to RST# de-assertion (high) 60 - 1,4,5,6
Notes:
1. These specifications are valid for all device versions (packages and speeds).
2. The device may reset if tPLPH is < tPLPH MIN, but this is not guaranteed.
3. Not applicable if RST# is tied to Vcc.
4. Sampled, but not 100% tested.
5. When RST# is tied to the VCC supply, device will not be ready until tVCCPH after VCC ≥ VCCMIN.
6. When RST# is tied to the VCCQ supply, device will not be ready until tVCCPH after VCC ≥ VCCMIN .
7. Reset completes within tPLPH if RST# is asserted while no erase or program operation is executing.

Figure 25. Reset Operation Waveforms
P1 R5
(A) Reset during VIH

RST# [P]
read mode VIL
Abort
P2 R5
Complete
(B) Reset during VIH
program or block erase RST# [P]
VIL
P1 ≤ P2
Abort
P2 R5
Complete
(C) Reset during VIH
program or block erase RST# [P]
VIL
P1 ≥ P2
P3
(D) VCC Power-up to VCC

VCC
RST# high 0V
8.3 Power Supply Decoupling

Flash memory devices require careful power supply de-coupling. Three basic power supply current
considerations are 1) standby current levels, 2) active current levels, and 3) transient peaks
produced when CE# and OE# are asserted and deasserted.
When the device is accessed, many internal conditions change. Circuits within the device enable
charge-pumps, and internal logic states change at high speed. All of these internal activities
produce transient signals. Transient current magnitudes depend on the device outputs’ capacitive
and inductive loading. Two-line control and correct de-coupling capacitor selection suppress
transient voltage peaks.
Because Intel® Multi-Level Cell (MLC) flash memory devices draw their power from VCC, VPP,
and VCCQ, each power connection should have a 0.1 μF ceramic capacitor to ground. High-
frequency, inherently low-inductance capacitors should be placed as close as possible to package
leads.
Additionally, for every eight devices used in the system, a 4.7 μF electrolytic capacitor should be
placed between power and ground close to the devices. The bulk capacitor is meant to overcome
voltage droop caused by PCB trace inductance.

9.0 Device Operations
This section provides an overview of device operations. The system CPU provides control of all in-
system read, write, and erase operations of the device via the system bus. The on-chip Write State
Machine (WSM) manages all block-erase and word-program algorithms.
Device commands are written to the Command User Interface (CUI) to control all flash memory
device operations. The CUI does not occupy an addressable memory location; it is the mechanism
through which the flash device is controlled.
9.1 Bus Operations

CE# low and RST# high enable device read operations. The device internally decodes upper
address inputs to determine the accessed block. ADV# low opens the internal address latches. OE#
low activates the outputs and gates selected data onto the I/O bus.
In asynchronous mode, the address is latched when ADV# goes high or continuously flows through
if ADV# is held low. In synchronous mode, the address is latched by the first of either the rising
ADV# edge or the next valid CLK edge with ADV# low (WE# and RST# must be VIH; CE# must
be VIL).
Bus cycles to/from the P30 device conform to standard microprocessor bus operations. Table 18
summarizes the bus operations and the logic levels that must be applied to the device control signal
inputs.
Table 18. Bus Operations Summary

Bus Operation RST# CLK ADV# CE# OE# WE# WAIT DQ[15:0] Notes
Asynchronous VIH X L L L H Deasserted Output

Read
Synchronous VIH Running L L L H Driven Output
Write VIH X L L H L High-Z Input 1
Output Disable VIH X X L H H High-Z High-Z 2
Standby VIH X X H X X High-Z High-Z 2
Reset VIL X X X X X High-Z High-Z 2,3
Notes:
1. Refer to the Table 19, “Command Bus Cycles” on page 50 for valid DQ[15:0] during a write operation.
2. X = Don’t Care (H or L).
3. RST# must be at VSS ± 0.2 V to meet the maximum specified power-down current.
9.1.1 Reads
To perform a read operation, RST# and WE# must be deasserted while CE# and OE# are asserted.
CE# is the device-select control. When asserted, it enables the flash memory device. OE# is the
data-output control. When asserted, the addressed flash memory data is driven onto the I/O bus.
See Section 10.0, “Read Operations” on page 53 for details on the available read modes, and see
Section 14.0, “Special Read States” on page 74 for details regarding the available read states.

9.1.2 Writes
To perform a write operation, both CE# and WE# are asserted while RST# and OE# are deasserted.
During a write operation, address and data are latched on the rising edge of WE# or CE#,
whichever occurs first. Table 19, “Command Bus Cycles” on page 50 shows the bus cycle
sequence for each of the supported device commands, while Table 20, “Command Codes and
Definitions” on page 51 describes each command. See Section 7.0, “AC Characteristics” on
page 33 for signal-timing details.
Note: Write operations with invalid VCC and/or VPP voltages can produce spurious results and should not
be attempted.
9.1.3 Output Disable

When OE# is deasserted, device outputs DQ[15:0] are disabled and placed in a high-impedance
(High-Z) state, WAIT is also placed in High-Z.
9.1.4 Standby
When CE# is deasserted the device is deselected and placed in standby, substantially reducing
power consumption. In standby, the data outputs are placed in High-Z, independent of the level
placed on OE#. Standby current, ICCS, is the average current measured over any 5 ms time interval,
5 μs after CE# is deasserted. During standby, average current is measured over the same time
interval 5 μs after CE# is deasserted.
When the device is deselected (while CE# is deasserted) during a program or erase operation, it
continues to consume active power until the program or erase operation is completed.
9.1.5 Reset
As with any automated device, it is important to assert RST# when the system is reset. When the
system comes out of reset, the system processor attempts to read from the flash memory if it is the
system boot device. If a CPU reset occurs with no flash memory reset, improper CPU initialization
may occur because the flash memory may be providing status information rather than array data.
Flash memory devices from Intel allow proper CPU initialization following a system reset through
the use of the RST# input. RST# should be controlled by the same low-true reset signal that resets
the system CPU.
After initial power-up or reset, the device defaults to asynchronous Read Array, and the Status
Register is set to 0x80. Asserting RST# de-energizes all internal circuits, and places the output
drivers in High-Z. When RST# is asserted, the device shuts down the operation in progress, a
process which takes a minimum amount of time to complete. When RST# has been deasserted, the
device is reset to asynchronous Read Array state.
Note: If RST# is asserted during a program or erase operation, the operation is terminated and the
memory contents at the aborted location (for a program) or block (for an erase) are no longer valid,
because the data may have been only partially written or erased.
When returning from a reset (RST# deasserted), a minimum wait is required before the initial read
access outputs valid data. Also, a minimum delay is required after a reset before a write cycle can
be initiated. After this wake-up interval passes, normal operation is restored. See Section 7.0, “AC
Characteristics” on page 33 for details about signal-timing.

9.2 Device Commands

Device operations are initiated by writing specific device commands to the Command User
Interface (CUI). See Table 19, “Command Bus Cycles” on page 50. Several commands are used to
modify array data including Word Program and Block Erase commands. Writing either command
to the CUI initiates a sequence of internally-timed functions that culminate in the completion of the
requested task. However, the operation can be aborted by either asserting RST# or by issuing an
appropriate suspend command.
Table 19. Command Bus Cycles (Sheet 1 of 2)

First Bus Cycle Second Bus Cycle
Bus
Mode Command
Cycles
Oper Addr(1) Data(2) Oper Addr(1) Data(2)
Read Array 1 Write DBA 0xFF - - -

Read Device Identifier ≥2 Write DBA 0x90 Read DBA + IA ID
Read CFI Query ≥2 Write DBA 0x98 Read DBA + QA QD
Read Status Register 2 Write DBA 0x70 Read DBA SRD
Clear Status Register 1 Write DBA 0x50 - - -
0x40/
Word Program 2 Write WA Write WA WD
0x10
Program Buffered Program(3) >2 Write WA 0xE8 Write WA N-1
Buffered Enhanced Factory
>2 Write WA 0x80 Write WA 0xD0
Program (BEFP)(4)
Erase Block Erase 2 Write BA 0x20 Write BA 0xD0
Program/Erase Suspend 1 Write DBA 0xB0 - - -

Suspend
Program/Erase Resume 1 Write DBA 0xD0 - - -
Lock Block 2 Write BA 0x60 Write BA 0x01
Block
Locking/ Unlock Block 2 Write BA 0x60 Write BA 0xD0
Unlocking
Lock-down Block 2 Write BA 0x60 Write BA 0x2F

Table 19. Command Bus Cycles (Sheet 2 of 2)

First Bus Cycle Second Bus Cycle
Bus
Mode Command
Cycles
Oper Addr(1) Data(2) Oper Addr(1) Data(2)
Program Protection Register 2 Write PRA 0xC0 Write PRA PD

Protection
Program Lock Register 2 Write LRA 0xC0 Write LRA LRD
Program Read Configuration
Configuration 2 Write RCD 0x60 Write RCD 0x03
Register
Notes:
1. First command cycle address should be the same as the operation’s target address.
DBA = Device Base Address (NOTE: needed for dual-die 512 Mb device)
IA = Identification code address offset.
QA = CFI Query address offset.
WA = Word address of memory location to be written.
BA = Address within the block.
PRA = Protection Register address.
LRA = Lock Register address.
RCD = Read Configuration Register data on A[15:0].
2. ID = Identifier data.
QD = Query data on DQ[15:0].
SRD = Status Register data.
WD = Word data.
N = Word count of data to be loaded into the write buffer.
PD = Protection Register data.
LRD = Lock Register data.
3. The second cycle of the Buffered Program Command is the word count of the data to be loaded into the write buffer. This
is followed by up to 32 words of data.Then the confirm command (0xD0) is issued, triggering the array programming
operation.
4. The confirm command (0xD0) is followed by the buffer data.
9.3 Command Definitions

Valid device command codes and descriptions are shown in Table 20.
Table 20. Command Codes and Definitions (Sheet 1 of 2)

Mode Code Device Mode Description
0xFF Read Array Places the device in Read Array mode. Array data is output on DQ[15:0].
Places the device in Read Status Register mode. The device enters this mode
0x70 Read Status Register after a program or erase command is issued. Status Register data is output on
DQ[7:0].
Read Device ID Places device in Read Device Identifier mode. Subsequent reads output
Read 0x90 or Configuration manufacturer/device codes, Configuration Register data, Block Lock status, or
Register Protection Register data on DQ[15:0].
Places the device in Read Query mode. Subsequent reads output Common
0x98 Read Query
Flash Interface information on DQ[7:0].
The WSM can only set Status Register error bits. The Clear Status Register
0x50 Clear Status Register
command is used to clear the SR error bits.
First cycle of a 2-cycle programming command; prepares the CUI for a write
operation. On the next write cycle, the address and data are latched and the
WSM executes the programming algorithm at the addressed location. During
program operations, the device responds only to Read Status Register and
Write 0x40 Word Program Setup
Program Suspend commands. CE# or OE# must be toggled to update the
Status Register in asynchronous read. CE# or ADV# must be toggled to update
the Status Register Data for synchronous Non-array reads. The Read Array
command must be issued to read array data after programming has finished.

Table 20. Command Codes and Definitions (Sheet 2 of 2)

Mode Code Device Mode Description
Alternate Word
0x10 Equivalent to the Word Program Setup command, 0x40.
Program Setup
This command loads a variable number of words up to the buffer size of 32
0xE8 Buffered Program
words onto the program buffer.
The confirm command is Issued after the data streaming for writing into the
Buffered Program
0xD0 buffer is done. This instructs the WSM to perform the Buffered Program
Confirm
Write algorithm, writing the data from the buffer to the flash memory array.
First cycle of a 2-cycle command; initiates Buffered Enhanced Factory
Program mode (BEFP). The CUI then waits for the BEFP Confirm command,
0x80 BEFP Setup
0xD0, that initiates the BEFP algorithm. All other commands are ignored when
BEFP mode begins.
If the previous command was BEFP Setup (0x80), the CUI latches the address
0xD0 BEFP Confirm
and data, and prepares the device for BEFP mode.
First cycle of a 2-cycle command; prepares the CUI for a block-erase
operation. The WSM performs the erase algorithm on the block addressed by
0x20 Block Erase Setup the Erase Confirm command. If the next command is not the Erase Confirm
(0xD0) command, the CUI sets Status Register bits SR[4] and SR[5], and
places the device in read status register mode.
Erase If the first command was Block Erase Setup (0x20), the CUI latches the
address and data, and the WSM erases the addressed block. During block-
erase operations, the device responds only to Read Status Register and Erase
0xD0 Block Erase Confirm
Suspend commands. CE# or OE# must be toggled to update the Status
Register in asynchronous read. CE# or ADV# must be toggled to update the
Status Register Data for synchronous Non-array reads
This command issued to any device address initiates a suspend of the
currently-executing program or block erase operation. The Status Register
Program or Erase indicates successful suspend operation by setting either SR[2] (program
0xB0
Suspend suspended) or SR[6] (erase suspended), along with SR[7] (ready). The Write
Suspend State Machine remains in the suspend mode regardless of control signal states
(except for RST# asserted).
This command issued to any device address resumes the suspended program
0xD0 Suspend Resume
or block-erase operation.
First cycle of a 2-cycle command; prepares the CUI for block lock configuration
changes. If the next command is not Block Lock (0x01), Block Unlock (0xD0),
0x60 Lock Block Setup
or Block Lock-Down (0x2F), the CUI sets Status Register bits SR[4] and SR[5],
indicating a command sequence error.
If the previous command was Block Lock Setup (0x60), the addressed block is
Block Locking/ 0x01 Lock Block
locked.
Unlocking
0xD0 Unlock Block unlocked. If the addressed block is in a lock-down state, the operation has no
effect.
0x2F Lock-Down Block
locked down.
First cycle of a 2-cycle command; prepares the device for a Protection Register
Program Protection
Protection 0xC0 or Lock Register program operation. The second cycle latches the register
Register Setup
address and data, and starts the programming algorithm
First cycle of a 2-cycle command; prepares the CUI for device read
Read Configuration configuration. If the Set Read Configuration Register command (0x03) is not
0x60
Register Setup the next command, the CUI sets Status Register bits SR[4] and SR[5],
indicating a command sequence error.
Configuration
If the previous command was Read Configuration Register Setup (0x60), the
Read Configuration CUI latches the address and writes A[15:0] to the Read Configuration Register.
0x03
Register Following a Configure Read Configuration Register command, subsequent
read operations access array data.

10.0 Read Operations
The device supports two read modes: asynchronous page mode and synchronous burst mode.
Asynchronous page mode is the default read mode after device power-up or a reset. The Read
Configuration Register must be configured to enable synchronous burst reads of the flash memory
array (see Section 10.3, “Read Configuration Register” on page 54).
The device can be in any of four read states: Read Array, Read Identifier, Read Status or Read
Query. Upon power-up, or after a reset, the device defaults to Read Array. To change the read state,
the appropriate read command must be written to the device (see Section 9.2, “Device Commands”
on page 50). See Section 14.0, “Special Read States” on page 74 for details regarding Read Status,
Read ID, and CFI Query modes.
The following sections describe read-mode operations in detail.
10.1 Asynchronous Page-Mode Read

Following a device power-up or reset, asynchronous page mode is the default read mode and the
device is set to Read Array. However, to perform array reads after any other device operation (e.g.
write operation), the Read Array command must be issued in order to read from the flash memory
array.
Note: Asynchronous page-mode reads can only be performed when Read Configuration Register bit
RCR[15] is set (see Section 10.3, “Read Configuration Register” on page 54).
To perform an asynchronous page-mode read, an address is driven onto the Address bus, and CE#
and ADV# are asserted. WE# and RST# must already have been deasserted. WAIT is deasserted
during asynchronous page mode. ADV# can be driven high to latch the address, or it must be held
low throughout the read cycle. CLK is not used for asynchronous page-mode reads, and is ignored.
If only asynchronous reads are to be performed, CLK should be tied to a valid VIH level, WAIT
signal can be floated and ADV# must be tied to ground. Array data is driven onto DQ[15:0] after
an initial access time tAVQV delay. (see Section 7.0, “AC Characteristics” on page 33).
In asynchronous page mode, four data words are “sensed” simultaneously from the flash memory
array and loaded into an internal page buffer. The buffer word corresponding to the initial address
on the Address bus is driven onto DQ[15:0] after the initial access delay. The lowest two address
bits determine which word of the 4-word page is output from the data buffer at any given time.
10.2 Synchronous Burst-Mode Read

To perform a synchronous burst- read, an initial address is driven onto the Address bus, and CE#
and ADV# are asserted. WE# and RST# must already have been deasserted. ADV# is asserted, and
then deasserted to latch the address. Alternately, ADV# can remain asserted throughout the burst
access, in which case the address is latched on the next valid CLK edge while ADV# is asserted.
During synchronous array and non-array read modes, the first word is output from the data buffer
on the next valid CLK edge after the initial access latency delay (see Section 10.3.2, “Latency
Count” on page 55). Subsequent data is output on valid CLK edges following a minimum delay.

However, for a synchronous non-array read, the same word of data will be output on successive
clock edges until the burst length requirements are satisfied. Refer to the following waveforms for
more detailed information:
• Figure 17, “Synchronous Single-Word Array or Non-array Read Timing” on page 39
• Figure 18, “Continuous Burst Read, Showing An Output Delay Timing” on page 40
• Figure 19, “Synchronous Burst-Mode Four-Word Read Timing” on page 40
10.3 Read Configuration Register

The Read Configuration Register (RCR) is used to select the read mode (synchronous or
asynchronous), and it defines the synchronous burst characteristics of the device. To modify RCR
settings, use the Configure Read Configuration Register command (see Section 9.2, “Device
Commands” on page 50).
RCR contents can be examined using the Read Device Identifier command, and then reading from
offset 0x05 (see Section 14.2, “Read Device Identifier” on page 75).
The RCR is shown in Table 21. The following sections describe each RCR bit.
Table 21. Read Configuration Register Description (Sheet 1 of 2)
Read Configuration Register (RCR)

Read WAIT Data WAIT Burst CLK Burst
Mode RES Latency Count Polarity Seq Edge RES RES Burst Length
Hold Delay Wrap
RM R LC[2:0] WP DH WD BS CE R R BW BL[2:0]
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Bit Name Description
15 Read Mode (RM) 0 = Synchronous burst-mode read
1 = Asynchronous page-mode read (default)
14 Reserved (R) Reserved bits should be cleared (0)
13:11 Latency Count (LC[2:0]) 010 =Code 2
011 =Code 3
100 =Code 4
101 =Code 5
110 =Code 6
111 =Code 7 (default)
(Other bit settings are reserved)
10 Wait Polarity (WP) 0 =WAIT signal is active low
1 =WAIT signal is active high (default)
9 Data Hold (DH) 0 =Data held for a 1-clock data cycle
1 =Data held for a 2-clock data cycle (default)
8 Wait Delay (WD) 0 =WAIT deasserted with valid data
1 =WAIT deasserted one data cycle before valid data (default)
7 Burst Sequence (BS) 0 =Reserved
1 =Linear (default)
6 Clock Edge (CE) 0 = Falling edge
1 = Rising edge (default)
5:4 Reserved (R) Reserved bits should be cleared (0)

Table 21. Read Configuration Register Description (Sheet 2 of 2)

3 Burst Wrap (BW) 0 =Wrap; Burst accesses wrap within burst length set by BL[2:0]
1 =No Wrap; Burst accesses do not wrap within burst length (default)
2:0 Burst Length (BL[2:0]) 001 =4-word burst
010 =8-word burst
011 =16-word burst
111 =Continuous-word burst (default)
(Other bit settings are reserved)
Note: Latency Code 2, Data Hold for a 2-clock data cycle (DH = 1) WAIT must be deasserted with valid data (WD =
0). Latency Code 2, Data Hold for a 2-cock data cycle (DH=1) WAIT deasserted one data cycle before valid
data (WD = 1) combination is not supported.
10.3.1 Read Mode

The Read Mode (RM) bit selects synchronous burst-mode or asynchronous page-mode operation
for the device. When the RM bit is set, asynchronous page mode is selected (default). When RM is
cleared, synchronous burst mode is selected.
10.3.2 Latency Count

The Latency Count bits, LC[2:0], tell the device how many clock cycles must elapse from the
rising edge of ADV# (or from the first valid clock edge after ADV# is asserted) until the first data
word is to be driven onto DQ[15:0]. The input clock frequency is used to determine this value.
Figure 26 shows the data output latency for the different settings of LC[2:0].
Synchronous burst at 40 MHz with a Latency Count setting of Code 3 will result in zero WAIT
states; however, a Latency Count setting of Code 4 will cause 1 WAIT state (Code 5 will cause 2
WAIT states, and so on) after every four words, regardless of whether a 16-word boundary is
crossed. If RCR[9] (Data Hold) bit is set (data hold of two clocks) this WAIT condition will not
occur because enough clocks elapse during each burst cycle to eliminate subsequent WAIT states.
Refer to Table 22, “Latency Count (LC) and Frequency Support” on page 56 for Latency Code
Settings.

Figure 26. First-Access Latency Count
CLK [C]
Address [A] Valid

Address
ADV# [V]
Code 0 (Reserved)
Valid Valid Valid Valid Valid Valid Valid Valid
DQ15-0 [D/Q] Output Output Output Output Output Output Output Output
Code 1
DQ15-0 [D/Q] (Reserved Valid Valid Valid Valid Valid Valid Valid
Output Output Output Output Output Output Output
Code 2 Valid Valid Valid Valid Valid Valid

DQ15-0 [D/Q] Output Output Output Output Output Output
Code 3 Valid Valid Valid Valid Valid

DQ15-0 [D/Q] Output Output Output Output Output
Code 4 Valid Valid Valid Valid

DQ15-0 [D/Q] Output Output Output Output
Code 5 Valid Valid Valid

DQ15-0 [D/Q] Output Output Output
Code 6
DQ15-0 [D/Q] Valid
Output
Valid
Output
Code 7 Valid
DQ15-0 [D/Q] Output
Table 22. Latency Count (LC) and Frequency Support

Latency Count Settings Frequency Support (MHz)
2 ≤ 27
3 ≤ 40
4 ≤ 52
Note: Synchronous burst read operation is currently not supported for the TSOP
package.

Figure 27. Example Latency Count Setting using Code 3
tData
0 1 2 3 4
CLK
CE#
ADV#
A[MAX:0] Address
Code 3
High-Z
D[15:0] Data
R103
10.3.3 WAIT Polarity

The WAIT Polarity bit (WP), RCR[10] determines the asserted level (VOH or VOL) of WAIT.
When WP is set, WAIT is asserted high (default). When WP is cleared, WAIT is asserted low.
WAIT changes state on valid clock edges during active bus cycles (CE# asserted, OE# asserted,
RST# deasserted).
10.3.3.1 WAIT Signal Function

The WAIT signal indicates data valid when the device is operating in synchronous mode
(RCR[15]=0). The WAIT signal is only “deasserted” when data is valid on the bus.
When the device is operating in synchronous non-array read mode, such as read status, read ID, or
read query. The WAIT signal is also “deasserted” when data is valid on the bus.
WAIT behavior during synchronous non-array reads at the end of word line works correctly only
on the first data access.
When the device is operating in asynchronous page mode, asynchronous single word read mode,
and all write operations, WAIT is set to a deasserted state as determined by RCR[10]. See Figure
15, “Asynchronous Single-Word Read (ADV# Latch)” on page 38, and Figure 16, “Asynchronous
Page-Mode Read Timing” on page 39.

Table 23. WAIT Functionality Table

Condition WAIT Notes
CE# = ‘1’, OE# = ‘X’ or CE# = ‘0’, OE# = ‘1’ High-Z 1

CE# =’0’, OE# = ‘0’ Active 1
Synchronous Array Reads Active 1
Synchronous Non-Array Reads Active 1
All Asynchronous Reads Deasserted 1
All Writes High-Z 1,2
Notes:
1. Active: WAIT is asserted until data becomes valid, then deasserts
2. When OE# = VIH during writes, WAIT = High-Z
10.3.4 Data Hold

For burst read operations, the Data Hold (DH) bit determines whether the data output remains valid
on DQ[15:0] for one or two clock cycles. This period of time is called the “data cycle”. When DH
is set, output data is held for two clocks (default). When DH is cleared, output data is held for one
clock (see Figure 28). The processor’s data setup time and the flash memory’s clock-to-data output
delay should be considered when determining whether to hold output data for one or two clocks. A
method for determining the Data Hold configuration is shown below:
To set the device at one clock data hold for subsequent reads, the following condition must be
satisfied:
tCHQV (ns) + tDATA (ns) ≤ One CLK Period (ns)
tDATA = Data set up to Clock (defined by CPU)
For example, with a clock frequency of 40 MHz, the clock period is 25 ns. Assuming
tCHQV = 20 ns and tDATA = 4 ns. Applying these values to the formula above:
20 ns + 4 ns ≤ 25 ns
The equation is satisfied and data will be available at every clock period with data hold setting at
one clock. If tCHQV (ns) + tDATA (ns) > One CLK Period (ns), data hold setting of 2 clock periods
must be used.
Figure 28. Data Hold Timing
CLK [C]
1 CLK Valid Valid Valid

Data Hold
D[15:0] [Q] Output Output Output
2 CLK Valid Valid

Data Hold
D[15:0] [Q] Output Output

10.3.5 WAIT Delay

The WAIT Delay (WD) bit controls the WAIT assertion-delay behavior during synchronous burst
reads. WAIT can be asserted either during or one data cycle before valid data is output on
DQ[15:0]. When WD is set, WAIT is deasserted one data cycle before valid data (default). When
WD is cleared, WAIT is deasserted during valid data.
10.3.6 Burst Sequence

The Burst Sequence (BS) bit selects linear-burst sequence (default). Only linear-burst sequence is
supported. Table 24 shows the synchronous burst sequence for all burst lengths, as well as the
effect of the Burst Wrap (BW) setting.
Table 24. Burst Sequence Word Ordering
Start Burst Addressing Sequence (DEC)
Addr. Burst Wrap
(DEC) (RCR[3]) 4-Word Burst 8-Word Burst 16-Word Burst Continuous Burst
(BL[2:0] = 0b001) (BL[2:0] = 0b010) (BL[2:0] = 0b011) (BL[2:0] = 0b111)
0 0 0-1-2-3 0-1-2-3-4-5-6-7 0-1-2-3-4…14-15 0-1-2-3-4-5-6-…
1 0 1-2-3-0 1-2-3-4-5-6-7-0 1-2-3-4-5…15-0 1-2-3-4-5-6-7-…
2 0 2-3-0-1 2-3-4-5-6-7-0-1 2-3-4-5-6…15-0-1 2-3-4-5-6-7-8-…
3 0 3-0-1-2 3-4-5-6-7-0-1-2 3-4-5-6-7…15-0-1-2 3-4-5-6-7-8-9-…
4 0 4-5-6-7-0-1-2-3 4-5-6-7-8…15-0-1-2-3 4-5-6-7-8-9-10…
5 0 5-6-7-0-1-2-3-4 5-6-7-8-9…15-0-1-2-3-4 5-6-7-8-9-10-11…
6 0 6-7-0-1-2-3-4-5 6-7-8-9-10…15-0-1-2-3-4-5 6-7-8-9-10-11-12-…
7 0 7-0-1-2-3-4-5-6 7-8-9-10…15-0-1-2-3-4-5-6 7-8-9-10-11-12-13…
…
…
14 0 14-15-0-1-2…12-13 14-15-16-17-18-19-20-…
15 0 15-0-1-2-3…13-14 15-16-17-18-19-20-21-…
…
…
0 1 0-1-2-3 0-1-2-3-4-5-6-7 0-1-2-3-4…14-15 0-1-2-3-4-5-6-…
1 1 1-2-3-4 1-2-3-4-5-6-7-8 1-2-3-4-5…15-16 1-2-3-4-5-6-7-…
2 1 2-3-4-5 2-3-4-5-6-7-8-9 2-3-4-5-6…16-17 2-3-4-5-6-7-8-…
3 1 3-4-5-6 3-4-5-6-7-8-9-10 3-4-5-6-7…17-18 3-4-5-6-7-8-9-…
4 1 4-5-6-7-8-9-10-11 4-5-6-7-8…18-19 4-5-6-7-8-9-10…
5 1 5-6-7-8-9-10-11-12 5-6-7-8-9…19-20 5-6-7-8-9-10-11…
6 1 6-7-8-9-10-11-12-13 6-7-8-9-10…20-21 6-7-8-9-10-11-12-…
7 1 7-8-9-10-11-12-13-14 7-8-9-10-11…21-22 7-8-9-10-11-12-13…
…
14 1 14-15-16-17-18…28-29 14-15-16-17-18-19-20-…
15 1 15-16-17-18-19…29-30 15-16-17-18-19-20-21-…
10.3.7 Clock Edge

The Clock Edge (CE) bit selects either a rising (default) or falling clock edge for CLK. This clock
edge is used at the start of a burst cycle, to output synchronous data, and to assert/deassert WAIT.
10.3.8 Burst Wrap

The Burst Wrap (BW) bit determines whether 4-word, 8-word, or 16-word burst length accesses
wrap within the selected word-length boundaries or cross word-length boundaries. When BW is
set, burst wrapping does not occur (default). When BW is cleared, burst wrapping occurs.
When performing synchronous burst reads with BW set (no wrap), an output delay may occur
when the burst sequence crosses its first device-row (16-word) boundary. If the burst sequence’s
start address is 4-word aligned, then no delay occurs. If the start address is at the end of a 4-word

boundary, the worst case output delay is one clock cycle less than the first access Latency Count.
This delay can take place only once, and doesn’t occur if the burst sequence does not cross a
device-row boundary. WAIT informs the system of this delay when it occurs.
10.3.9 Burst Length

The Burst Length bit (BL[2:0]) selects the linear burst length for all synchronous burst reads of the
flash memory array. The burst lengths are 4-word, 8-word, 16-word, and continuous word.
Continuous-burst accesses are linear only, and do not wrap within any word length boundaries (see
Table 24, “Burst Sequence Word Ordering” on page 59). When a burst cycle begins, the device
outputs synchronous burst data until it reaches the end of the “burstable” address space.

11.0 Programming Operations
The device supports three programming methods: Word Programming (40h/10h), Buffered
Programming (E8h, D0h), and Buffered Enhanced Factory Programming (80h, D0h). See
Section 9.0, “Device Operations” on page 48 for details on the various programming commands
issued to the device. The following sections describe device programming in detail.
Successful programming requires the addressed block to be unlocked. If the block is locked down,
WP# must be deasserted and the block must be unlocked before attempting to program the block.
Attempting to program a locked block causes a program error (SR[4] and SR[1] set) and
termination of the operation. See Section 13.0, “Security Modes” on page 69 for details on locking
and unlocking blocks.
The Intel StrataFlash® Embedded Memory (P30) is segmented into multiple 8-Mbit Programming
Regions. See Section 4.4, “Memory Maps” on page 25 for complete addressing. Execute in Place
(XIP) applications must partition the memory such that code and data are in separate programming
regions. XIP is executing code directly from flash memory. Each Programming Region should
contain only code or data but not both. The following terms define the difference between code and
data. System designs must use these definitions when partitioning their code and data for the P30
device.
Code: Execution code ran out of the flash device on a continuous basis in the system.
Information periodically programmed into the flash device and read back (e.g.
Data:
execution code shadowed and executed in RAM, pictures, log files, etc.).
11.1 Word Programming

Word programming operations are initiated by writing the Word Program Setup command to the
device (see Section 9.0, “Device Operations” on page 48). This is followed by a second write to the
device with the address and data to be programmed. The device outputs Status Register data when
read. See Figure 38, “Word Program Flowchart” on page 84. VPP must be above VPPLK, and within
the specified VPPL min/max values.
During programming, the Write State Machine (WSM) executes a sequence of internally-timed
events that program the desired data bits at the addressed location, and verifies that the bits are
sufficiently programmed. Programming the flash memory array changes “ones” to “zeros”.
Memory array bits that are zeros can be changed to ones only by erasing the block (see Section
12.0, “Erase Operations” on page 67).
The Status Register can be examined for programming progress and errors by reading at any
address. The device remains in the Read Status Register state until another command is written to
the device.
Status Register bit SR[7] indicates the programming status while the sequence executes.
Commands that can be issued to the device during programming are Program Suspend, Read Status
Register, Read Device Identifier, CFI Query, and Read Array (this returns unknown data).
When programming has finished, Status Register bit SR[4] (when set) indicates a programming
failure. If SR[3] is set, the WSM could not perform the word programming operation because VPP
was outside of its acceptable limits. If SR[1] is set, the word programming operation attempted to
program a locked block, causing the operation to abort.

Before issuing a new command, the Status Register contents should be examined and then cleared
using the Clear Status Register command. Any valid command can follow, when word
programming has completed.
11.1.1 Factory Word Programming

Factory word programming is similar to word programming in that it uses the same commands and
programming algorithms. However, factory word programming enhances the programming
performance with VPP = VPPH. This can enable faster programming times during OEM
manufacturing processes. Factory word programming is not intended for extended use. See Section
5.2, “Operating Conditions” on page 29 for limitations when VPP = VPPH.
Note: When VPP = VPPL, the device draws programming current from the VCC supply. If VPP is driven
by a logic signal, VPPL must remain above VPPL MIN to program the device. When VPP = VPPH,
the device draws programming current from the VPP supply. Figure 29, “Example VPP Supply
Connections” on page 66 shows examples of device power supply configurations.
11.2 Buffered Programming

The device features a 32-word buffer to enable optimum programming performance. For Buffered
Programming, data is first written to an on-chip write buffer. Then the buffer data is programmed
into the flash memory array in buffer-size increments. This can improve system programming
performance significantly over non-buffered programming.
When the Buffered Programming Setup command is issued (see Section 9.2, “Device Commands”
on page 50), Status Register information is updated and reflects the availability of the buffer. SR[7]
indicates buffer availability: if set, the buffer is available; if cleared, the buffer is not available. To
retry, issue the Buffered Programming Setup command again, and re-check SR[7]. When SR[7] is
set, the buffer is ready for loading. (see Figure 40, “Buffer Program Flowchart” on page 86).
On the next write, a word count is written to the device at the buffer address. This tells the device
how many data words will be written to the buffer, up to the maximum size of the buffer.
On the next write, a device start address is given along with the first data to be written to the flash
memory array. Subsequent writes provide additional device addresses and data. All data addresses
must lie within the start address plus the word count. Optimum programming performance and
lower power usage are obtained by aligning the starting address at the beginning of a 32-word
boundary (A[4:0] = 0x00). Crossing a 32-word boundary during programming will double the total
programming time.
After the last data is written to the buffer, the Buffered Programming Confirm command must be
issued to the original block address. The WSM begins to program buffer contents to the flash
memory array. If a command other than the Buffered Programming Confirm command is written to
the device, a command sequence error occurs and Status Register bits SR[7,5,4] are set. If an error
occurs while writing to the array, the device stops programming, and Status Register bits SR[7,4]
are set, indicating a programming failure.
When Buffered Programming has completed, additional buffer writes can be initiated by issuing
another Buffered Programming Setup command and repeating the buffered program sequence.
Buffered programming may be performed with VPP = VPPL or VPPH (see Section 5.2, “Operating
Conditions” on page 29 for limitations when operating the device with VPP = VPPH).

If an attempt is made to program past an erase-block boundary using the Buffered Program
command, the device aborts the operation. This generates a command sequence error, and Status
Register bits SR[5,4] are set.
If Buffered programming is attempted while VPP is below VPPLK, Status Register bits SR[4,3] are
set. If any errors are detected that have set Status Register bits, the Status Register should be
cleared using the Clear Status Register command.
11.3 Buffered Enhanced Factory Programming

Buffered Enhanced Factory Programing (BEFP) speeds up Multi-Level Cell (MLC) flash
programming. The enhanced programming algorithm used in BEFP eliminates traditional
programming elements that drive up overhead in device programmer systems.
BEFP consists of three phases: Setup, Program/Verify, and Exit (see Figure 41, “BEFP Flowchart”
on page 87). It uses a write buffer to spread MLC program performance across 32 data words.
Verification occurs in the same phase as programming to accurately program the flash memory cell
to the correct bit state.
A single two-cycle command sequence programs the entire block of data. This enhancement
eliminates three write cycles per buffer: two commands and the word count for each set of 32 data
words. Host programmer bus cycles fill the device’s write buffer followed by a status check. SR[0]
indicates when data from the buffer has been programmed into sequential flash memory array
locations.
Following the buffer-to-flash array programming sequence, the Write State Machine (WSM)
increments internal addressing to automatically select the next 32-word array boundary. This
aspect of BEFP saves host programming equipment the address-bus setup overhead.
With adequate continuity testing, programming equipment can rely on the WSM’s internal
verification to ensure that the device has programmed properly. This eliminates the external post-
program verification and its associated overhead.
11.3.1 BEFP Requirements and Considerations

BEFP requirements:
• Case temperature: TC = 25 °C ± 5 °C
• VCC within specified operating range
• VPP driven to VPPH
• Target block unlocked before issuing the BEFP Setup and Confirm commands
• The first-word address (WA0) for the block to be programmed must be held constant from the
setup phase through all data streaming into the target block, until transition to the exit phase is
desired
• WA0 must align with the start of an array buffer boundary1
BEFP considerations:
• For optimum performance, cycling must be limited below 100 erase cycles per block2
• BEFP programs one block at a time; all buffer data must fall within a single block3

• BEFP cannot be suspended

• Programming to the flash memory array can occur only when the buffer is full4
Note:
1. Word buffer boundaries in the array are determined by A[4:0] (0x00 through 0x1F). The alignment start
point is A[4:0] = 0x00.
2. Some degradation in performance may occur if this limit is exceeded, but the internal algorithm
continues to work properly.
3. If the internal address counter increments beyond the block's maximum address, addressing wraps
around to the beginning of the block.
4. If the number of words is less than 32, remaining locations must be filled with 0xFFFF.
11.3.2 BEFP Setup Phase

After receiving the BEFP Setup and Confirm command sequence, Status Register bit SR[7]
(Ready) is cleared, indicating that the WSM is busy with BEFP algorithm startup. A delay before
checking SR[7] is required to allow the WSM enough time to perform all of its setups and checks
(Block-Lock status, VPP level, etc.). If an error is detected, SR[4] is set and BEFP operation
terminates. If the block was found to be locked, SR[1] is also set. SR[3] is set if the error occurred
due to an incorrect VPP level.
Note: Reading from the device after the BEFP Setup and Confirm command sequence outputs Status
Register data. Do not issue the Read Status Register command; it will be interpreted as data to be
loaded into the buffer.
11.3.3 BEFP Program/Verify Phase

After the BEFP Setup Phase has completed, the host programming system must check SR[7,0] to
determine the availability of the write buffer for data streaming. SR[7] cleared indicates the device
is busy and the BEFP program/verify phase is activated. SR[0] indicates the write buffer is
available.
Two basic sequences repeat in this phase: loading of the write buffer, followed by buffer data
programming to the array. For BEFP, the count value for buffer loading is always the maximum
buffer size of 32 words. During the buffer-loading sequence, data is stored to sequential buffer
locations starting at address 0x00. Programming of the buffer contents to the flash memory array
starts as soon as the buffer is full. If the number of words is less than 32, the remaining buffer
locations must be filled with 0xFFFF.
Caution: The buffer must be completely filled for programming to occur. Supplying an address outside of the
current block's range during a buffer-fill sequence causes the algorithm to exit immediately. Any
data previously loaded into the buffer during the fill cycle is not programmed into the array.
The starting address for data entry must be buffer size aligned, if not the BEFP algorithm will be
aborted and the program fails and (SR[4]) flag will be set.
Data words from the write buffer are directed to sequential memory locations in the flash memory
array; programming continues from where the previous buffer sequence ended. The host
programming system must poll SR[0] to determine when the buffer program sequence completes.
SR[0] cleared indicates that all buffer data has been transferred to the flash array; SR[0] set
indicates that the buffer is not available yet for the next fill cycle. The host system may check full

status for errors at any time, but it is only necessary on a block basis after BEFP exit. After the
buffer fill cycle, no write cycles should be issued to the device until SR[0] = 0 and the device is
ready for the next buffer fill.
Note: Any spurious writes are ignored after a buffer fill operation and when internal program is
proceeding.
The host programming system continues the BEFP algorithm by providing the next group of data
words to be written to the buffer. Alternatively, it can terminate this phase by changing the block
address to one outside of the current block’s range.
The Program/Verify phase concludes when the programmer writes to a different block address;
data supplied must be 0xFFFF. Upon Program/Verify phase completion, the device enters the
BEFP Exit phase.
11.3.4 BEFP Exit Phase

When SR[7] is set, the device has returned to normal operating conditions. A full status check
should be performed at this time to ensure the entire block programmed successfully. When exiting
the BEFP algorithm with a block address change, the read mode will not change. After BEFP exit,
any valid command can be issued to the device.
11.4 Program Suspend

Issuing the Program Suspend command while programming suspends the programming operation.
This allows data to be accessed from the device other than the one being programmed. The
Program Suspend command can be issued to any device address. A program operation can be
suspended to perform reads only. Additionally, a program operation that is running during an erase
suspend can be suspended to perform a read operation (see Figure 39, “Program Suspend/Resume
Flowchart” on page 85).
When a programming operation is executing, issuing the Program Suspend command requests the
WSM to suspend the programming algorithm at predetermined points. The device continues to
output Status Register data after the Program Suspend command is issued. Programming is
suspended when Status Register bits SR[7,2] are set. Suspend latency is specified in Section 7.5,
“Program and Erase Characteristics” on page 45.
To read data from the device, the Read Array command must be issued. Read Array, Read Status
Register, Read Device Identifier, CFI Query, and Program Resume are valid commands during a
program suspend.
During a program suspend, deasserting CE# places the device in standby, reducing active current.
VPP must remain at its programming level, and WP# must remain unchanged while in program
suspend. If RST# is asserted, the device is reset.

11.5 Program Resume

The Resume command instructs the device to continue programming, and automatically clears
Status Register bits SR[7,2]. This command can be written to any address. If error bits are set, the
Status Register should be cleared before issuing the next instruction. RST# must remain deasserted
(see Figure 39, “Program Suspend/Resume Flowchart” on page 85).
11.6 Program Protection

When VPP = VIL, absolute hardware write protection is provided for all device blocks. If VPP is at
or below VPPLK, programming operations halt and SR[3] is set indicating a VPP-level error. Block
lock registers are not affected by the voltage level on VPP; they may still be programmed and read,
even if VPP is less than VPPLK.
Figure 29. Example VPP Supply Connections
VCC VCC VCC VCC
VPP VPP PROT # VPP

≤ 10K Ω
• Low-voltage Programming only

• Factory Programming with VPP = VPPH • Logic Control of Device Protection
• Complete write/Erase Protection when VPP ≤ VPPLK
VCC VCC VCC VCC
VPP=VPPH VPP VPP
• Low Voltage Programming Only

• Low Voltage and Factory Programming • Full Device Protection Unavailable

12.0 Erase Operations
Flash erasing is performed on a block basis. An entire block is erased each time an erase command
sequence is issued, and only one block is erased at a time. When a block is erased, all bits within
that block read as logical ones. The following sections describe block erase operations in detail.
12.1 Block Erase

Block erase operations are initiated by writing the Block Erase Setup command to the address of
the block to be erased (see Section 9.2, “Device Commands” on page 50). Next, the Block Erase
Confirm command is written to the address of the block to be erased. If the device is placed in
standby (CE# deasserted) during an erase operation, the device completes the erase operation
before entering standby.VPP must be above VPPLK and the block must be unlocked (see Figure 42,
“Block Erase Flowchart” on page 88).
During a block erase, the Write State Machine (WSM) executes a sequence of internally-timed
events that conditions, erases, and verifies all bits within the block. Erasing the flash memory array
changes “zeros” to “ones”. Memory array bits that are ones can be changed to zeros only by
programming the block (see Section 11.0, “Programming Operations” on page 61).
The Status Register can be examined for block erase progress and errors by reading any address.
The device remains in the Read Status Register state until another command is written. SR[0]
indicates whether the addressed block is erasing. Status Register bit SR[7] is set upon erase
completion.
Status Register bit SR[7] indicates block erase status while the sequence executes. When the erase
operation has finished, Status Register bit SR[5] indicates an erase failure if set. SR[3] set would
indicate that the WSM could not perform the erase operation because VPP was outside of its
acceptable limits. SR[1] set indicates that the erase operation attempted to erase a locked block,
causing the operation to abort.
Before issuing a new command, the Status Register contents should be examined and then cleared
using the Clear Status Register command. Any valid command can follow once the block erase
operation has completed.
12.2 Erase Suspend

Issuing the Erase Suspend command while erasing suspends the block erase operation. This allows
data to be accessed from memory locations other than the one being erased. The Erase Suspend
command can be issued to any device address. A block erase operation can be suspended to
perform a word or buffer program operation, or a read operation within any block except the block
that is erase suspended (see Figure 39, “Program Suspend/Resume Flowchart” on page 85).
When a block erase operation is executing, issuing the Erase Suspend command requests the WSM
to suspend the erase algorithm at predetermined points. The device continues to output Status
Register data after the Erase Suspend command is issued. Block erase is suspended when Status
Register bits SR[7,6] are set. Suspend latency is specified in Section 7.5, “Program and Erase
Characteristics” on page 45.

To read data from the device (other than an erase-suspended block), the Read Array command must
be issued. During Erase Suspend, a Program command can be issued to any block other than the
erase-suspended block. Block erase cannot resume until program operations initiated during erase
suspend complete. Read Array, Read Status Register, Read Device Identifier, CFI Query, and Erase
Resume are valid commands during Erase Suspend. Additionally, Clear Status Register, Program,
Program Suspend, Block Lock, Block Unlock, and Block Lock-Down are valid commands during
Erase Suspend.
During an erase suspend, deasserting CE# places the device in standby, reducing active current.
VPP must remain at a valid level, and WP# must remain unchanged while in erase suspend. If
RST# is asserted, the device is reset.
12.3 Erase Resume

The Erase Resume command instructs the device to continue erasing, and automatically clears
status register bits SR[7,6]. This command can be written to any address. If status register error bits
are set, the Status Register should be cleared before issuing the next instruction. RST# must remain
deasserted (see Figure 39, “Program Suspend/Resume Flowchart” on page 85).
12.4 Erase Protection

When VPP = VIL, absolute hardware erase protection is provided for all device blocks. If VPP is
below VPPLK, erase operations halt and SR[3] is set indicating a VPP-level error.

13.0 Security Modes
The device features security modes used to protect the information stored in the flash memory
array. The following sections describe each security mode in detail.
13.1 Block Locking

Individual instant block locking is used to protect user code and/or data within the flash memory
array. All blocks power up in a locked state to protect array data from being altered during power
transitions. Any block can be locked or unlocked with no latency. Locked blocks cannot be
programmed or erased; they can only be read.
Software-controlled security is implemented using the Block Lock and Block Unlock commands.
Hardware-controlled security can be implemented using the Block Lock-Down command along
with asserting WP#. Also, VPP data security can be used to inhibit program and erase operations
(see Section 11.6, “Program Protection” on page 66 and Section 12.4, “Erase Protection” on
page 68).
The P30 device also offers four pre-defined areas in the main array that can be configured as One-
Time Programmable (OTP) for the highest level of security. These include the four 32 KB
parameter blocks together as one and the three adjacent 128 KB main blocks. This is available for
top or bottom parameter devices.
13.1.1 Lock Block

To lock a block, issue the Lock Block Setup command. The next command must be the Lock Block
command issued to the desired block’s address (see Section 9.2, “Device Commands” on page 50
and Figure 44, “Block Lock Operations Flowchart” on page 90). If the Set Read Configuration
Register command is issued after the Block Lock Setup command, the device configures the RCR
instead.
Block lock and unlock operations are not affected by the voltage level on VPP. The block lock bits
may be modified and/or read even if VPP is at or below VPPLK.
13.1.2 Unlock Block

The Unlock Block command is used to unlock blocks (see Section 9.2, “Device Commands” on
page 50). Unlocked blocks can be read, programmed, and erased. Unlocked blocks return to a
locked state when the device is reset or powered down. If a block is in a lock-down state, WP#
must be deasserted before it can be unlocked (see Figure 30, “Block Locking State Diagram” on
page 70).
13.1.3 Lock-Down Block

A locked or unlocked block can be locked-down by writing the Lock-Down Block command
sequence (see Section 9.2, “Device Commands” on page 50). Blocks in a lock-down state cannot
be programmed or erased; they can only be read. However, unlike locked blocks, their locked state
cannot be changed by software commands alone. A locked-down block can only be unlocked by
issuing the Unlock Block command with WP# deasserted. To return an unlocked block to locked-

down state, a Lock-Down command must be issued prior to changing WP# to VIL. Locked-down
blocks revert to the locked state upon reset or power up the device (see Figure 30, “Block Locking
State Diagram” on page 70).
13.1.4 Block Lock Status

The Read Device Identifier command is used to determine a block’s lock status (see Section 14.2,
“Read Device Identifier” on page 75). Data bits DQ[1:0] display the addressed block’s lock status;
DQ0 is the addressed block’s lock bit, while DQ1 is the addressed block’s lock-down bit.
Figure 30. Block Locking State Diagram
Locked- Hardware
Power-Up/Reset Locked Down 4,5 Locked 5
[X01] [011] [011]
WP# Hardware Control
Software
Unlocked Locked Unlocked
[X00] [111] [110]
Software Block Lock (0x60/0x01) or Software Block Unlock (0x60/0xD0)
Software Block Lock-Down (0x60/0x2F)
W P# hardware control
Notes: 1. [a,b,c] represents [WP#, DQ1, DQ0]. X = Don’t Care.

2. DQ1 indicates Block Lock-Down status. DQ1 = ‘0’, Lock-Down has not been issued
to this block. DQ1 = ‘1’, Lock-Down has been issued to this block.
3. DQ0 indicates block lock status. DQ0 = ‘0’, block is unlocked. DQ0 = ‘1’, block is
locked.
4. Locked-down = Hardware + Software locked.
5. [011] states should be tracked by system software to determine difference between
Hardware Locked and Locked-Down states.
13.1.5 Block Locking During Suspend

Block lock and unlock changes can be performed during an erase suspend. To change block
locking during an erase operation, first issue the Erase Suspend command. Monitor the Status
Register until SR[7] and SR[6] are set, indicating the device is suspended and ready to accept
another command.
Next, write the desired lock command sequence to a block, which changes the lock state of that
block. After completing block lock or unlock operations, resume the erase operation using the
Erase Resume command.
Note: A Lock Block Setup command followed by any command other than Lock Block, Unlock Block,
or Lock-Down Block produces a command sequence error and set Status Register bits SR[4] and
SR[5]. If a command sequence error occurs during an erase suspend, SR[4] and SR[5] remains set,
even after the erase operation is resumed. Unless the Status Register is cleared using the Clear

Status Register command before resuming the erase operation, possible erase errors may be
masked by the command sequence error.
If a block is locked or locked-down during an erase suspend of the same block, the lock status bits
change immediately. However, the erase operation completes when it is resumed. Block lock
operations cannot occur during a program suspend. See Appendix A, “Write State Machine” on
page 77, which shows valid commands during an erase suspend.
13.2 Selectable One-Time Programmable Blocks

Any of four pre-defined areas from the main array (the four 32 KB parameter blocks together as
one and three adjacent 128 KB main blocks) can be configured as One-Time Programmable (OTP)
so further program and erase operations are not allowed. This option is available for top or bottom
parameter devices.
Table 25. Selectable OTP Block Mapping

Density Top Parameter Configuration Bottom Parameter Configuration
blocks 258:255 (parameters) blocks 3:0 (parameters)

block 254 (main) block 4 (main)
256-Mbit

128-Mbit

64-Mbit
Notes:
1. The 512-Mbit devices will have multiple die and selectable OTP Areas depending on the
placement of the parameter blocks.
2. When programming the OTP bits in PR-LR0 for a Top Parameter Device, the following
upper address bits must also be driven properly: A[Max:17] driven high (VIH) for TSOP
and Easy BGA packages, and A[Max:16] driven high (VIH) for QUAD+ SCSP.
Please see your local Intel representative for details about the Selectable OTP implementation.

13.3 Protection Registers

The device contains 17 Protection Registers (PRs) that can be used to implement system security
measures and/or device identification. Each Protection Register can be individually locked.
The first 128-bit Protection Register is comprised of two 64-bit (8-word) segments. The lower 64-
bit segment is pre-programmed at the Intel factory with a unique 64-bit number. The other 64-bit
segment, as well as the other sixteen 128-bit Protection Registers, are blank. Users can program
these registers as needed. When programmed, users can then lock the Protection Register(s) to
prevent additional bit programming (see Figure 31, “Protection Register Map” on page 72).
The user-programmable Protection Registers contain one-time programmable (OTP) bits; when
programmed, register bits cannot be erased. Each Protection Register can be accessed multiple
times to program individual bits, as long as the register remains unlocked.
Each Protection Register has an associated Lock Register bit. When a Lock Register bit is
programmed, the associated Protection Register can only be read; it can no longer be programmed.
Additionally, because the Lock Register bits themselves are OTP, when programmed, Lock
Register bits cannot be erased. Therefore, when a Protection Register is locked, it cannot be
unlocked.
.
Figure 31. Protection Register Map
0x109
128-bit Protection Register 16

(User-Programmable)
0x102
0x91
128-bit Protection Register 1

(User-Programmable)
0x8A
Lock Register 1
0x89 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
0x88
64-bit Segment
(User-Programmable)
0x85
128-Bit Protection Register 0
0x84
64-bit Segment
(Factory-Programmed)
0x81
Lock Register 0
0x80 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

13.3.1 Reading the Protection Registers

The Protection Registers can be read from any address. To read the Protection Register, first issue
the Read Device Identifier command at any address to place the device in the Read Device
Identifier state (see Section 9.2, “Device Commands” on page 50). Next, perform a read operation
using the address offset corresponding to the register to be read. Table 27, “Device Identifier
Information” on page 76 shows the address offsets of the Protection Registers and Lock Registers.
Register data is read 16 bits at a time.
13.3.2 Programming the Protection Registers

To program any of the Protection Registers, first issue the Program Protection Register command
at the parameter’s base address plus the offset to the desired Protection Register (see Section 9.2,
“Device Commands” on page 50). Next, write the desired Protection Register data to the same
Protection Register address (see Figure 31, “Protection Register Map” on page 72).
The device programs the 64-bit and 128-bit user-programmable Protection Register data 16 bits at
a time (see Figure 45, “Protection Register Programming Flowchart” on page 91). Issuing the
Program Protection Register command outside of the Protection Register’s address space causes a
program error (SR[4] set). Attempting to program a locked Protection Register causes a program
error (SR[4] set) and a lock error (SR[1] set).
13.3.3 Locking the Protection Registers

Each Protection Register can be locked by programming its respective lock bit in the Lock
Register. To lock a Protection Register, program the corresponding bit in the Lock Register by
issuing the Program Lock Register command, followed by the desired Lock Register data (see
Section 9.2, “Device Commands” on page 50). The physical addresses of the Lock Registers are
0x80 for register 0 and 0x89 for register 1. These addresses are used when programming the lock
registers (see Table 27, “Device Identifier Information” on page 76).
Bit 0 of Lock Register 0 is already programmed at the factory, locking the lower, pre-programmed
64-bit region of the first 128-bit Protection Register containing the unique identification number of
the device. Bit 1 of Lock Register 0 can be programmed by the user to lock the user-programmable,
64-bit region of the first 128-bit Protection Register. When programming Bit 1 of Lock Register 0,
all other bits need to be left as ‘1’ such that the data programmed is 0xFFFD.
Lock Register 1 controls the locking of the upper sixteen 128-bit Protection Registers. Each of the
16 bits of Lock Register 1 correspond to each of the upper sixteen 128-bit Protection Registers.
Programming a bit in Lock Register 1 locks the corresponding 128-bit Protection Register.
Caution: After being locked, the Protection Registers cannot be unlocked.

14.0 Special Read States
The following sections describe non-array read states. Non-array reads can be performed in
asynchronous read or synchronous burst mode. A non-array read operation occurs as asynchronous
single-word mode. When non-array reads are performed in asynchronous page mode only the first
data is valid and all subsequent data are undefined. When a non-array read operation occurs as
synchronous burst mode, the same word of data requested will be output on successive clock edges
until the burst length requirements are satisfied.
Refer to the following waveforms for more detailed information:

• Figure 14, “Asynchronous Single-Word Read (ADV# Low)” on page 38
• Figure 15, “Asynchronous Single-Word Read (ADV# Latch)” on page 38
• Figure 17, “Synchronous Single-Word Array or Non-array Read Timing” on page 39
14.1 Read Status Register

To read the Status Register, issue the Read Status Register command at any address. Status Register
information is available to which the Read Status Register, Word Program, or Block Erase
command was issued. Status Register data is automatically made available following a Word
Program, Block Erase, or Block Lock command sequence. Reads from the device after any of these
command sequences outputs the device’s status until another valid command is written (e.g. Read
Array command).
The Status Register is read using single asynchronous-mode or synchronous burst mode reads.
Status Register data is output on DQ[7:0], while 0x00 is output on DQ[15:8]. In asynchronous
mode the falling edge of OE#, or CE# (whichever occurs first) updates and latches the Status
Register contents. However, reading the Status Register in synchronous burst mode, CE# or ADV#
must be toggled to update status data.
The Device Write Status bit (SR[7]) provides overall status of the device. Status register bits
SR[6:1] present status and error information about the program, erase, suspend, VPP, and block-
locked operations.
Table 26. Status Register Description (Sheet 1 of 2)
Status Register (SR) Default Value = 0x80
Erase Program Block-

Device Erase Program BEFP
Suspend VPP Status Suspend Locked
Write Status Status Status Status
Status Status Status
DWS ESS ES PS VPPS PSS BLS BWS
7 6 5 4 3 2 1 0
Bit Name Description

Device Write Status 0 = Device is busy; program or erase cycle in progress; SR[0] valid.
7
(DWS) 1 = Device is ready; SR[6:1] are valid.
Erase Suspend Status 0 = Erase suspend not in effect.
6
(ESS) 1 = Erase suspend in effect.

Table 26. Status Register Description (Sheet 2 of 2)
Status Register (SR) Default Value = 0x80
0 = Erase successful.
5 Erase Status (ES)
1 = Erase fail or program sequence error when set with SR[4,7].
0 = Program successful.
4 Program Status (PS)
1 = Program fail or program sequence error when set with SR[5,7]
0 = VPP within acceptable limits during program or erase operation.
3 VPP Status (VPPS)
1 = VPP < VPPLK during program or erase operation.
Program Suspend Status 0 = Program suspend not in effect.
2
(PSS) 1 = Program suspend in effect.
Block-Locked Status 0 = Block not locked during program or erase.
1
(BLS) 1 = Block locked during program or erase; operation aborted.
After Buffered Enhanced Factory Programming (BEFP) data is
loaded into the buffer:
0 BEFP Status (BWS)
0 = BEFP complete.
1 = BEFP in-progress.
Note: Always clear the Status Register prior to resuming erase operations. It avoids Status Register
ambiguity when issuing commands during Erase Suspend. If a command sequence error occurs
during an erase-suspend state, the Status Register contains the command sequence error status
(SR[7,5,4] set). When the erase operation resumes and finishes, possible errors during the erase
operation cannot be detected via the Status Register because it contains the previous error status.
14.1.1 Clear Status Register

The Clear Status Register command clears the status register. It functions independent of VPP. The
Write State Machine (WSM) sets and clears SR[7,6,2], but it sets bits SR[5:3,1] without clearing
them. The Status Register should be cleared before starting a command sequence to avoid any
ambiguity. A device reset also clears the Status Register.
14.2 Read Device Identifier

The Read Device Identifier command instructs the device to output manufacturer code, device
identifier code, block-lock status, protection register data, or configuration register data (see
Section 9.2, “Device Commands” on page 50 for details on issuing the Read Device Identifier
command). Table 27, “Device Identifier Information” on page 76 and Table 28, “Device ID codes”
on page 76 show the address offsets and data values for this device.

Table 27. Device Identifier Information

Item Address(1) Data
Manufacturer Code 0x00 0089h

Device ID Code 0x01 ID (see Table 28)
Block Lock Configuration: Lock Bit:
• Block Is Unlocked DQ0 = 0b0
• Block Is Locked BBA + 0x02 DQ0 = 0b1
• Block Is not Locked-Down DQ1 = 0b0
• Block Is Locked-Down DQ1 = 0b1
Read Configuration Register 0x05 RCR Contents
Lock Register 0 0x80 PR-LK0
64-bit Factory-Programmed Protection Register 0x81–0x84 Factory Protection Register Data
64-bit User-Programmable Protection Register 0x85–0x88 User Protection Register Data
Lock Register 1 0x89 Protection Register Data
128-bit User-Programmable Protection Registers 0x8A–0x109 PR-LK1
Notes:
1. BBA = Block Base Address.
Table 28. Device ID codes

Device Identifier Codes
ID Code Type Device Density –T –B
(Top Parameter) (Bottom Parameter)
64-Mbit 8817 881A
Device Code 128-Mbit 8818 881B
256-Mbit 8919 891C
Note: The 512-Mbit devices do not have a Device ID associated with them. Each die within the stack can be
identified by either of the 256-Mbit Device ID codes depending on its parameter option.
14.3 CFI Query

The CFI Query command instructs the device to output Common Flash Interface (CFI) data when
read. See Section 9.2, “Device Commands” on page 50 for details on issuing the CFI Query
command. Appendix C, “Common Flash Interface” on page 92 shows CFI information and address
offsets within the CFI database.

Appendix A Write State Machine

Figure 32 through Figure 37 show the command state transitions (Next State Table) based on
incoming commands. Only one partition can be actively programming or erasing at a time. Each
partition stays in its last read state (Read Array, Read Device ID, CFI Query or Read Status
Register) until a new command changes it. The next WSM state does not depend on the partition’s
output state.
Figure 32. Write State Machine—Next State Table (Sheet 1 of 6)
Command Input to Chip and resulting Chip Next State

BE Confirm,
Buffered
Buffered P/E BP / Prg / Clear Lock, Unlock,
Read Word Erase Enhanced Read Read
Program Resume, Erase Status Lock-down,
Current Chip Array
(2)
Program
(3,4)
Setup
(3,4) Factory Pgm Status ID/Query
(BP) ULB, Suspend Register (5) CR setup (4)
(7) Setup (3, 4)
State Confirm
(8)
(FFH) (10H/40H) (E8H) (20H) (80H) (D0H) (B0H) (70H) (50H) (90H, 98H) (60H)
Program Erase Lock/CR

Ready Ready BP Setup BEFP Setup Ready
Setup Setup Setup
Ready
Lock/CR Setup Ready (Lock Error) (Unlock Ready (Lock Error)
Block)
Setup
OTP OTP Busy
Busy
Setup Word Program Busy
Word
Busy Program Busy Program Word Program Busy
Word
Suspend
Program
Word
Suspend Word Program Suspend Program Word Program Suspend
Busy
Setup BP Load 1
BP Load 1 BP Load 2
BP Load 2 BP Confirm if Data load into Program Buffer is complete; Else BP Load 2
BP
BP
Ready (Error) BP Busy Ready (Error)
Confirm
BP Busy BP Busy BP Suspend BP Busy
BP
BP Suspend BP Busy BP Suspend
Suspend
Setup Ready (Error) Erase Busy Ready (Error)
Erase
Busy Erase Busy Erase Busy
Suspend
Erase Word
Lock/CR
Program BP Setup in
Erase Setup in
Suspend Setup in Erase Erase Suspend Erase Busy Erase Suspend
Suspend Erase
Erase Suspend
Suspend
Suspend


BE Confirm,
Buffered
Buffered P/E BP / Prg / Clear Lock, Unlock,
Read Word Erase Enhanced Read Read
Program Resume, Erase Status Lock-down,
Current Chip Array (2) Program (3,4) Setup (3,4) Factory Pgm
Status ID/Query
(BP) ULB, Suspend Register (5)
CR setup (4)
(7) Setup (3, 4)
State Confirm (8)
Setup Word Program Busy in Erase Suspend

Word
Program
Busy Word Program Busy in Erase Suspend Suspend in Word Program Busy in Erase Suspend Busy
Word
Erase
Program in
Suspend
Erase
Suspend Word
Program
Suspend Word Program Suspend in Erase Suspend Busy in Word Program Suspend in Erase Suspend
Erase
Suspend
Setup BP Load 1
BP Load 1 BP Load 2
BP Load 2 BP Confirm if Data load into Program Buffer is complete; Else BP Load 2
BP in Erase BP Busy in
BP
Suspend Erase Suspend (Error) Erase Ready (Error in Erase Suspend)
Confirm
Suspend
BP Suspend
BP Busy BP Busy in Erase Suspend in Erase BP Busy in Erase Suspend
Suspend
BP Busy in
BP
BP Suspend in Erase Suspend Erase BP Suspend in Erase Suspend
Suspend
Suspend
Erase
Lock/CR Setup in Erase Suspend
Erase Suspend (Lock Error) Erase Suspend (Lock Error [Botch])
Suspend (Unlock
Block)
BEFP
Buffered Setup Ready (Error) Loading Ready (Error)
Enhanced Data (X=32)
Factory
Program
BEFP
Mode BEFP Program and Verify Busy (if Block Address given matches address given on BEFP Setup command). Commands treated as data. (7)
Busy

Lock Lock-Down
OTP Write RCR Block Address Illegal Cmds or
Current Chip Block Block WSM
Setup (4) Confirm (8)
(?WA0) 9
BEFP Data (1)
(7) Confirm (8) Confirm (8) Operation
State Completes
(C0H) (01H) (2FH) (03H) (XXXXH) (all other codes)
Ready OTP
Ready
Setup
Ready Ready Ready
Ready N/A
Lock/CR Setup (Lock (Lock (Lock Down Ready (Lock Error)
(Set CR)
Error) Block) Blk)
Setup
OTP OTP Busy
Busy Ready
Setup Word Program Busy N/A
Busy Word Program Busy Ready

Word
Program
Suspend Word Program Suspend
Setup BP Load 1
BP Load 1 BP Load 2 Ready (BP Load 2 BP Load 2
BP Confirm if
N/A
Data load into
BP Load 2 BP Confirm if Data load into Program Buffer is
Ready Program Buffer is
complete; ELSE BP load 2
complete; ELSE
BP BP Load 2
BP Ready (Error)
Confirm (Proceed if
Ready (Error) Ready (Error)
unlocked or lock
error)
BP Busy
BP Busy Ready
BP
Suspend BP Suspend
N/A
Setup
Ready (Error)
Busy
Erase Busy Ready
Erase
Suspend
Erase Suspend N/A

Lock Lock-Down
OTP Write RCR Block Address Illegal Cmds or
Block Block WSM
Current Chip Setup (4) (8) (8) Confirm (8)
(?WA0) 9
BEFP Data (1)
(7) Confirm Confirm Operation
State Completes
(C0H) (01H) (2FH) (03H) (XXXXH) (all other codes)
Setup Word Program Busy in Erase Suspend NA
Busy Word Program Busy in Erase Suspend Busy Erase Suspend

Word
Program in
Erase
Suspend
Suspend Word Program Suspend in Erase Suspend N/A
Setup BP Load 1
BP Load 1 BP Load 2 Ready (BP Load 2 BP Load 2
BP Confirm if
Data load into
BP Confirm if Data load into Program Buffer is
BP Load 2 Ready Program Buffer is N/A
complete; Else BP Load 2
complete; Else
BP Load 2
BP in Erase Ready (Error)
Suspend BP (Proceed if
Ready (Error in Erase Suspend) Ready (Error)
Confirm unlocked or lock
error)
BP Busy BP Busy in Erase Suspend Erase Suspend
BP
BP Suspend in Erase Suspend
Suspend
Erase Erase Erase

Erase
Lock/CR Setup in Erase Suspend Suspend Suspend
Suspend Erase Suspend (Lock Error)
Suspend (Lock (Lock (Lock Down N/A
(Set CR)
Error) Block) Block)
Ready (BEFP
Buffered Setup Ready (Error) Ready (Error)
Loading Data)
Enhanced
Factory
Program BEFP Program and Verify Busy (if Block Address
BEFP
Mode given matches address given on BEFP Setup Ready BEFP Busy Ready
Busy
command). Commands treated as data. (7)

Output Next State Table

Command Input to Chip and resulting Output Mux Next State
BE Confirm,
Buffered
Word P/E Program/ Clear Lock, Unlock,
Read Erase Enhanced Read Read
Program BP Setup Resume, Erase Status Lock-down,
Array (2) Setup (3,4) Factory Pgm ULB Confirm Status (5) ID/Query
Current chip state Setup (3,4) Suspend Register CR setup (4)
Setup (3, 4) (8)
BEFP Setup,
BEFP Pgm & Verify
Busy,
Erase Setup,
OTP Setup,
BP: Setup, Load 1,
Load 2, Confirm, Status Read
Word Pgm Setup,
Word Pgm Setup in
Erase Susp,
BP Setup, Load1,
Load 2, Confirm in
Erase Suspend
Lock/CR Setup,
Lock/CR Setup in Status Read
Erase Susp
Status
OTP Busy Read
Ready,
Erase Suspend,
BP Suspend
BP Busy,
Word Program
Busy,
Output mux
Erase Busy, Read Array Status Read Output does not change. Status Read does not Status Read
BP Busy change. ID Read
BP Busy in Erase
Suspend
Word Pgm
Suspend,
Word Pgm Busy in
Erase Suspend,
Pgm Suspend In
Erase Suspend

Output Next State Table

Command Input to Chip and resulting Output Mux Next State
Lock Lock-Down
OTP Write CR Block Address Illegal Cmds or
Block Block WSM
Setup (4) (8) (8) Confirm (8)
(?WA0) BEFP Data (1)
Current chip state Confirm Confirm Operation
Completes
(C0H) (01H) (2FH) (03H) (FFFFH) (all other codes)
BEFP Setup,
BEFP Pgm & Verify
Busy,
Erase Setup,
OTP Setup,
BP: Setup, Load 1,
Load 2, Confirm, Status Read
Word Pgm Setup,
Word Pgm Setup in
Erase Susp,
BP Setup, Load1,
Load 2, Confirm in
Erase Suspend
Lock/CR Setup,
Array
Lock/CR Setup in Status Read
Read
Status Read
Erase Susp
Output does
OTP Busy not change.
Ready,
Erase Suspend,
BP Suspend
BP Busy,
Word Program
Busy,
Erase Busy, Status Output does not
Output does not change. Array Read
BP Busy Read change.
BP Busy in Erase
Suspend
Word Pgm
Suspend,
Word Pgm Busy in
Erase Suspend,
Pgm Suspend In
Erase Suspend
Notes:
1. "Illegal commands" include commands outside of the allowed command set (allowed commands: 40H [pgm], 20H [erase],
etc.)
2. If a "Read Array" is attempted from a busy partition, the result will be invalid data. The ID and Query data are located at
different locations in the address map.
3. 1st and 2nd cycles of "2 cycles write commands" must be given to the same partition address, or unexpected results will
occur.
4. To protect memory contents against erroneous command sequences, there are specific instances in a multi-cycle
command sequence in which the second cycle will be ignored. For example, when the device is program suspended and
an erase setup command (0x20) is given followed by a confirm/resume command (0xD0), the second command will be
ignored because it is unclear whether the user intends to erase the block or resume the program operation.

5. The Clear Status command only clears the error bits in the status register if the device is not in the following modes: WSM
running (Pgm Busy, Erase Busy, Pgm Busy In Erase Suspend, OTP Busy, BEFP modes).
6. BEFP writes are only allowed when the status register bit #0 = 0, or else the data is ignored.
7. The "current state" is that of the "chip" and not of the "partition"; Each partition "remembers" which output (Array, ID/CFI or
Status) it was last pointed to on the last instruction to the "chip", but the next state of the chip does not depend on where
the partition's output mux is presently pointing to.
8. Confirm commands (Lock Block, Unlock Block, Lock-Down Block, Configuration Register) perform the operation and then
move to the Ready State.
9. WA0 refers to the block address latched during the first write cycle of the current operation.

Appendix B Flowcharts
Figure 38. Word Program Flowchart
WORD PROGRAM PROCEDURE
Bus
Start Operation Command Comments
Program Data = 0x40

Write
Write 0x40, Setup Addr = Location to program
(Setup)
Word Address
Data = Data to program
Write Data
Addr = Location to program
Write Data, (Confirm)
Word Address
Read None Status register data
Program
Read Status Suspend
Register Check SR[7]
Loop
Idle None 1 = WSM Ready
No 0 = WSM Busy
0 Yes
SR[7] = Suspend? Repeat for subsequent Word Program operations.
1 Full Status Register check can be done after each program, or

after a sequence of program operations.
Full Status Write 0xFF after the last operation to set to the Read Array
Check
state.
(if desired)
Program
Complete
FULL STATUS CHECK PROCEDURE

Read Status Bus
Command Comments
Register Operation
Check SR[3]:
Idle None
1 = VPP Error
1 VPP Range
SR[3] = Error
Check SR[4]:
0 Idle None
1 = Data Program Error
1 Program Check SR[1]:

SR[4] = Idle None
Error 1 = Block locked; operation aborted
0
If an error is detected, clear the Status Register before
1 Device continuing operations - only the Clear Staus Register
SR[1] = command clears the Status Register error bits.
Protect Error
0
Program
Successful

Figure 39. Program Suspend/Resume Flowchart
PROGRAM SUSPEND / RESUME PROCEDURE
Start
Program Suspend Bus

Operation Command Comments
Write B0h
Any Address Program Data = B0h
Write
Read Status Suspend Addr = Block to suspend (BA)
Write 70h
Same Partition Write Read Data = 70h
Status Addr = Same partition
Read Status Status register data

Register Read
Addr = Suspended block (BA)
Check SR.7
0 Standby 1 = WSM ready
SR.7 =
0 = WSM busy
1
Check SR.2
Standby 1 = Program suspended
0 Program 0 = Program completed
SR.2 =
Completed
1 Data = FFh
Read
Read Array Write Addr = Any address within the
Array
Write FFh suspended partition
Susp Partition
Read array data from block other than
Read the one being programmed
Read Array
Data Program Data = D0h
Write
Resume Addr = Suspended block (BA)
If the suspended partition was placed in Read Array mode:
Done No
Reading Return partition to Status mode:
Read
Yes
Write Data = 70h
Status Addr = Same partition
Program Resume Read Array
Write D0h Write FFh
Any Address Pgm'd Partition
Program Read Array

Resumed Data
Read Status
Write 70h
Same Partition PGM_SUS.WMF

Figure 40. Buffer Program Flowchart
Buffer Programming Procedure
Start
Bus
Command Comments
Operation
Device
Use Single Word Buffer Prog. Data = 0xE8
Supports Buffer Write
No Programming Setup Addr = Word Address
Writes?
SR[7] = Valid
Yes Read None
Addr = Word Address
Set Timeout or
Loop Counter Check SR[7]:
Idle None 1 = Write Buffer available
0 = No Write Buffer available
Get Next
Target Address Data = N-1 = Word Count
Write
None N = 0 corresponds to count = 1
(Notes 1, 2)
Addr = Word Address
Issue Buffer Prog. Cmd.
0xE8, Write Data = Write Buffer Data
None
Word Address (Notes 3, 4) Addr = Start Word Address
Other partitions of the device can be read by addressing those partitions
Write Data = Write Buffer Data

None
and driving OE# low. (Any write commands are not allowed during this
Read Status Register (Note 3) Addr = Word Address

at Word Address
Write Buffer Prog. Data = 0xD0
(Notes 5, 6) Conf. Addr = Original Word Address
No
Status register Data
Write Buffer Timeout Read None
0 = No Addr = Note 7
Available? or Count
Yes
SR[7] = Expired? Check SR[7]:
Idle None 1 = WSM Ready
1 = Yes 0 = WSM Busy
Write Word Count, 1. Word count value on D[7:0] is loaded into the word count
Word Address register. Count ranges for this device are N = 0x00 to 0x1F.
2. The device outputs the Status Register when read.
Buffer Program Data, 3. Write Buffer contents will be programmed at the issued word
X=X+1 address.
Start Word Address
4. Align the start address on a Write Buffer boundary for
maximum programming performance (i.e., A[4:0] of the Start
Write Buffer Data, Word Address = 0x00).
X=0 5. The Buffered Programming Confirm command must be
Word Address
issued to an address in the same block, for example, the
No original Start Word Address, or the last address used during the
loop that loaded the buffer data.
No Abort Buffer 6. The Status Register indicates an improper command
X = N?
Program? sequence if the Buffer Program command is aborted; use the
Clear Status Register command to clear error bits.
Yes 7. The Status Register can be read from any address within
the programming partition.
Yes Write to another
period.)
Write Confirm 0xD0 Block Address

Full status check can be done after all erase and write
and Word Address sequences complete. Write 0xFF after the last operation to
(Note 5) place the partition in the Read Array state.
Buffer Program Aborted Issue Read
0xFF commands can be issued to read from
Status Register
Command
Read Status Register Suspend

(Note 7) Program
Loop
No
any blocks in other partitions
0=No Suspend Yes

Is BP finished?
SR[7] = Program?
1=Yes
Full Status
Check if Desired
Program Complete

Figure 41. BEFP Flowchart
BUFFERED ENHANCED FACTORY PROGRAMMING (BEFP) PROCEDURE

Setup Phase Program & Verify Phase Exit Phase
Read Read
Start
Status Reg . Status Reg .
V P P applied
No (SR[0]=1) Data Stream No (SR[7]=0) BEFP
Block Unlocked
Ready? Exited ?
Yes (SR[0]=0) Yes (SR[7]=1)

W rite 80h @
1 st W ord Address Initialize Count: Full Status Check
X=0 Procedure
Write D0h @
1 st W ord Address Write Data @ 1st Program
Word Address Complete
BEFP Setup delay

Increment Count:
X = X+1
Read
Status Reg .
N Check
X = 32?
BEFP Setup Yes (SR[7]=0) Y

Done?
Read
No (SR[7]=1) Status Reg .
Check V PP, Lock No (SR[0]=1)

errors (SR[3,1])
Program
Done?
Exit Yes (SR[0]=0)
N Last
Data?
W rite 0xFFFF,
Address Not within
Current Block
BEFP Setup BEFP Program & Verify BEFP Exit

Bus Bus Bus
Operation Comments O peration Comments Operation Com ments
State State State
Unlock Status Data = Status Register Data Status Data = Status Register Data
Write V P PH applied to VPP Read Read
Block Register Address = 1 st W ord Addr. Register Address = 1 st W ord Addr.
Write BEFP Data = 0x80 @ 1 st W ord Check SR[0]: Check Check SR[7]:
(Note 1) Setup Address Data Stream
Standby 0 = Ready for Data Standby Exit 0 = Exit Not Completed
Ready?
BEFP Data = 0x80 @ 1 st W ord 1 = Not Ready for Data Status 1 = Exit Completed
Write 1
Confirm Address Initialize
Standby X=0 Repeat for subsequent blocks ;
Status Data = Status Register Data Count
Read
Register Address = 1 st Word Addr. W rite Load Data = Data to Program After BEFP exit, a full Status Register check can
(note 2) Buffer Address = 1 st W ord Addr. determine if any program error occurred ;
BEFP Check SR [7]:
Standby Setup 0 = BEFP Ready Increment See full Status Register check procedure in the
Done? 1 = BEFP Not Ready Standby X = X+1
Count W ord Program flowchart.
Error If SR[7] is set, check: X = 32?

Buffer W rite 0xFF to enter Read Array state .
Standby Condition SR[3] set = V PP Error Standby Yes = Read SR [0]
Full?
Check SR[1] set = Locked Block No = Load Next Data W ord
Status Data = Status Reg. Data
Read
Register Address = 1 st W ord Addr.
Check SR[0]:
Program
Standby 0 = Program Done
Done?
1 = Program in Progress
Last No = Fill buffer again

Standby
Data? Yes = Exit
Exit Prog & Data = 0xFFFF @ address

W rite
Verify Phase not in current block
NOTES:
1. First-word address to be programmed within the target block must be aligned on a write -buffer boundary.
2. W rite-buffer contents are programmed sequentially to the flash array starting at the first word address (W SM internally increments addressing ).

Figure 42. Block Erase Flowchart
BLOCK ERASE PROCEDURE
Bus
Start Operation Command Comments
Block
Data = 0x20
Write Erase
Write 0x20, Addr = Block to be erased (BA)
(Block Erase) Setup
Block Address
Erase Data = 0xD0
Write Confirm Addr = Block to be erased (BA)
Write 0xD0,
(Erase Confirm)
Block Address
Read None Status Register data.
Suspend
Read Status Erase
Register Check SR[7]:
Loop
Idle None 1 = WSM ready
No
0 = WSM busy
0 Suspend Yes
SR[7] =
Erase Repeat for subsequent block erasures.
1 Full Status register check can be done after each block erase
or after a sequence of block erasures.
Full Erase
Status Check Write 0xFF after the last operation to enter read array mode.
(if desired)
Block Erase
Complete
FULL ERASE STATUS CHECK PROCEDURE
Read Status Bus

Command Comments
Register Operation
Check SR[3]:
Idle None
1 VPP Range 1 = VPP Range Error
SR[3] =
Error Check SR[4,5]:
0 Idle None
Both 1 = Command Sequence Error
SR[4,5] = 1,1 Command Check SR[5]:

Sequence Error Idle None
1 = Block Erase Error
0
Check SR[1]:
1 Block Erase Idle None 1 = Attempted erase of locked block;
SR[5] =
Error erase aborted.
0 Only the Clear Status Register command clears SR[1, 3, 4, 5].
1 Block Locked If an error is detected, clear the Status register before
SR[1] =
Error attempting an erase retry or other error recovery.
0
Block Erase
Successful

Figure 43. Erase Suspend/Resume Flowchart
ERASE SUSPEND / RESUME PROCEDURE
Start
Bus
Command Comments
Operation
Write 0x70, (Read Status) Write Read Data = 0x70

Same Partition Status Addr = Any partition address
Data = 0xB0
Erase
Write 0xB0, Write Addr = Same partition address as
(Erase Suspend) Suspend
Any Address above
Read None Status Register data.

Read Status Addr = Same partition
Register
Check SR[7]:
Idle None 1 = WSM ready
0 0 = WSM busy
SR[7] =
1 Check SR[6]:
Idle None 1 = Erase suspended
0 = Erase completed
0 Erase
SR[6] =
Completed
Read Array Data = 0xFF or 0x40
Write Addr = Any address within the
1 or Program
suspended partition
Read Program
Read or Read array or program data from/to
Read or None
Write block other than the one being erased
Program?
Read Array Program Program Data = 0xD0
No Write
Data Loop Resume Addr = Any address
Done If the suspended partition was placed in

Read Array mode or a Program Loop:
Write 0xD0, Read Return partition to Status mode:

(Erase Resume) Write Status Data = 0x70
Any Address
Register Addr = Same partition
Erase Write 0xFF, (Read Array)

Resumed Erased Partition
Write 0x70, Read Array

(Read Status)
Same Partition Data

Figure 44. Block Lock Operations Flowchart
LOCKING OPERATIONS PROCEDURE

Start
Bus
Command Comments
Operation
Write 0x60, Lock Data = 0x60

(Lock Setup) Write
Block Address Setup Addr = Block to lock/unlock/lock-down
Lock, Data = 0x01 (Block Lock)

Write either
Unlock, or 0xD0 (Block Unlock)
0x01/0xD0/0x2F, (Lock Confirm) Write
Lock-Down 0x2F (Lock-Down Block)
Block Address
Confirm Addr = Block to lock/unlock/lock-down
Write Read Data = 0x90

Write 0x90 (Read Device ID)
(Optional) Device ID Addr = Block address + offset 2
Read Block Lock Block Lock status data

Optional
Read Block
(Optional) Status Addr = Block address + offset 2
Lock Status
Idle None Confirm locking change on D[1,0].

Locking No
Change?
Yes Read Data = 0xFF
Write
Array Addr = Block address
Write 0xFF
(Read Array)
Partition Address
Lock Change
Complete

Figure 45. Protection Register Programming Flowchart
PROTECTION REGISTER PROGRAMMING PROCEDURE
Bus
Start Command Comments
Operation
Program Data = 0xC0
Write
Write 0xC0, PR Setup Addr = First Location to Program
(Program Setup)
PR Address
Protection Data = Data to Program
Write Program Addr = Location to Program
Write PR
(Confirm Data)
Address & Data
Read None Status Register Data.
Read Status Check SR[7]:

Register Idle None 1 = WSM Ready
0 = WSM Busy
0 Program Protection Register operation addresses must be

SR[7] = within the Protection Register address space. Addresses
outside this space will return an error.
1
Repeat for subsequent programming operations.
Full Status
Check Full Status Register check can be done after each program, or
(if desired) after a sequence of program operations.
Write 0xFF after the last operation to set Read Array state.
Program
Complete
FULL STATUS CHECK PROCEDURE
Read Status Bus Command Comments

Register Data Operation
Check SR[3]:
Idle None
1 =VPP Range Error
1
SR[3] = VPP Range Error
Check SR[4]:
Idle None
0 1 =Programming Error
1 Check SR[1]:
SR[4] = Program Error Idle None
1 =Block locked; operation aborted
0 Only the Clear Staus Register command clears SR[1, 3, 4].
If an error is detected, clear the Status register before
SR[1] = 1 Register Locked;
Program Aborted attempting a program retry or other error recovery.
Program
Successful

Appendix C Common Flash Interface

The Common Flash Interface (CFI) is part of an overall specification for multiple command-set
and control-interface descriptions. This appendix describes the database structure containing the
data returned by a read operation after issuing the CFI Query command (see Section 9.2, “Device
Commands” on page 50). System software can parse this database structure to obtain information
about the flash device, such as block size, density, bus width, and electrical specifications. The
system software will then know which command set(s) to use to properly perform flash writes,
block erases, reads and otherwise control the flash device.
C.1 Query Structure Output

The Query database allows system software to obtain information for controlling the flash device.
This section describes the device’s CFI-compliant interface that allows access to Query data.
Query data are presented on the lowest-order data outputs (DQ7-0) only. The numerical offset value
is the address relative to the maximum bus width supported by the device. On this family of
devices, the Query table device starting address is a 10h, which is a word address for x16 devices.
For a word-wide (x16) device, the first two Query-structure bytes, ASCII “Q” and “R,” appear on
the low byte at word addresses 10h and 11h. This CFI-compliant device outputs 00h data on upper
bytes. The device outputs ASCII “Q” in the low byte (DQ7-0) and 00h in the high byte (DQ15-8).
At Query addresses containing two or more bytes of information, the least significant data byte is
presented at the lower address, and the most significant data byte is presented at the higher address.
In all of the following tables, addresses and data are represented in hexadecimal notation, so the
“h” suffix has been dropped. In addition, since the upper byte of word-wide devices is always
“00h,” the leading “00” has been dropped from the table notation and only the lower byte value is
shown. Any x16 device outputs can be assumed to have 00h on the upper byte in this mode.
Table 29. Summary of Query Structure Output as a Function of Device and Mode
Hex Hex ASCII

Device
Offset Code Value
00010: 51 "Q"
Device Addresses 00011: 52 "R"
00012: 59 "Y"

Table 30. Example of Query Structure Output of x16- Devices

Word Addressing: Byte Addressing:
Offset Hex Code Value Offset Hex Code Value
AX–A0 D15–D0 AX–A0 D7–D0
00010h 0051 "Q" 00010h 51 "Q"
00011h 0052 "R" 00011h 52 "R"
00012h 0059 "Y" 00012h 59 "Y"
00013h P_IDLO PrVendor 00013h P_IDLO PrVendor
00014h P_IDHI ID # 00014h P_IDLO ID #
00015h PLO PrVendor 00015h P_IDHI ID #
00016h PHI TblAdr 00016h ... ...
00017h A_IDLO AltVendor 00017h
00018h A_IDHI ID # 00018h
... ... ... ...
C.2 Query Structure Overview

The Query command causes the flash component to display the Common Flash Interface (CFI)
Query structure or “database.” The structure sub-sections and address locations are summarized
below.
Table 31. Query Structure
Offset Sub-Section Name Description(1)

00001-Fh Reserved Reserved for vendor-specific information
00010h CFI query identification string Command set ID and vendor data offset
0001Bh System interface information Device timing & voltage information
00027h Device geometry definition Flash device layout
Vendor-defined additional information specific
P(3) Primary Intel-specific Extended Query Table
to the Primary Vendor Algorithm
Notes:
1. Refer to the Query Structure Output section and offset 28h for the detailed definition of offset address as
a function of device bus width and mode.
2. BA = Block Address beginning location (i.e., 08000h is block 1’s beginning location when the block size
is 32-KWord).
3. Offset 15 defines “P” which points to the Primary Intel-specific Extended Query Table.

C.3 CFI Query Identification String

The Identification String provides verification that the component supports the Common Flash
Interface specification. It also indicates the specification version and supported vendor-specified
command set(s).
Table 32. CFI Identification

Hex
Offset Length Description
Add. Code Value
10h 3 Query-unique ASCII string “QRY“ 10: --51 "Q"
11: --52 "R"
12: --59 "Y"
13h 2 Primary vendor command set and control interface ID code. 13: --01
16-bit ID code for vendor-specified algorithms 14: --00
15h 2 Extended Query Table primary algorithm address 15: --0A
16: --01
17h 2 Alternate vendor command set and control interface ID code. 17: --00
0000h means no second vendor-specified algorithm exists 18: --00
19h 2 Secondary algorithm Extended Query Table address. 19: --00
0000h means none exists 1A: --00
Table 33. System Interface Information
Hex
Offset Length Description
Add. Code Value
1Bh 1 VCC logic supply minimum program/erase voltage 1B: --17 1.7V
bits 0–3 BCD 100 mV
bits 4–7 BCD volts
1Ch 1 VCC logic supply maximum program/erase voltage 1C: --20 2.0V
bits 4–7 BCD volts
1Dh 1 VPP [programming] supply minimum program/erase voltage 1D: --85 8.5V
bits 4–7 HEX volts
1Eh 1 VPP [programming] supply maximum program/erase voltage 1E: --95 9.5V
bits 4–7 HEX volts
1Fh 1 “n” such that typical single word program time-out = 2n μ-sec 1F: --08 256μs
20h 1 “n” such that typical max. buffer write time-out = 2n μ-sec 20: --09 512μs
21h 1 “n” such that typical block erase time-out = 2n m-sec 21: --0A 1s
22h 1 “n” such that typical full chip erase time-out = 2n m-sec 22: --00 NA
23h 1 “n” such that maximum word program time-out = 2n times typical 23: --01 512μs
24h 1 “n” such that maximum buffer write time-out = 2n times typical 24: --01 1024μs
25h 1 “n” such that maximum block erase time-out = 2n times typical 25: --02 4s
26h 1 “n” such that maximum chip erase time-out = 2n times typical 26: --00 NA

C.4 Device Geometry Definition

Table 34. Device Geometry Definition
Offset Length Description Code

27h 1 “n” such that device size = 2n in number of bytes 27: See table below
Flash device interface code assignment:
"n" such that n+1 specifies the bit field that represents the flash
device width capabilities as described in the table:
7 6 5 4 3 2 1 0
28h 2 — — — — x64 x32 x16 x8 28: --01 x16
15 14 13 12 11 10 9 8
— — — — — — — — 29: --00
2Ah 2 “n” such that maximum number of bytes in write buffer = 2n 2A: --06 64
2B: --00
2Ch 1 Number of erase block regions (x) within device: 2C:
1. x = 0 means no erase blocking; the device erases in bulk
2. x specifies the number of device regions with one or See table below
more contiguous same-size erase blocks.
3. Symmetrically blocked partitions have one blocking region
2Dh 4 Erase Block Region 1 Information 2D:
bits 0–15 = y, y+1 = number of identical-size erase blocks 2E:
See table below
bits 16–31 = z, region erase block(s) size are z x 256 bytes 2F:
30:
31h 4 Erase Block Region 2 Information 31:
bits 0–15 = y, y+1 = number of identical-size erase blocks 32:
See table below
bits 16–31 = z, region erase block(s) size are z x 256 bytes 33:
34:
35h 4 Reserved for future erase block region information 35:
36:
See table below
37:
38:
A ddress 64-Mbit 128-Mbit 256-Mbit

–B –T –B –T –B –T
27: --17 --17 --18 --18 --19 --19
28: --01 --01 --01 --01 --01 --01
29: --00 --00 --00 --00 --00 --00
2A : --06 --06 --06 --06 --06 --06
2B: --00 --00 --00 --00 --00 --00
2C: --02 --02 --02 --02 --02 --02
2D: --03 --3E --03 --7E --03 --FE
2E: --00 --00 --00 --00 --00 --00
2F: --80 --00 --80 --00 --80 --00
30: --00 --02 --00 --02 --00 --02
31: --3E --03 --7E --03 --FE --03
32: --00 --00 --00 --00 --00 --00
33: --00 --80 --00 --80 --00 --80
34: --02 --00 --02 --00 --02 --00
35: --00 --00 --00 --00 --00 --00
36: --00 --00 --00 --00 --00 --00
37: --00 --00 --00 --00 --00 --00
38: --00 --00 --00 --00 --00 --00

C.5 Intel-Specific Extended Query Table

Table 35. Primary Vendor-Specific Extended Query
Offset(1) Length Description Hex

P = 10Ah (Optional flash features and commands) Add. Code Value
(P+0)h 3 Primary extended query table 10A --50 "P"
(P+1)h Unique ASCII string “PRI“ 10B: --52 "R"
(P+2)h 10C: --49 "I"
(P+3)h 1 Major version number, ASCII 10D: --31 "1"
(P+4)h 1 Minor version number, ASCII 10E: --34 "4"
(P+5)h 4 Optional feature and command support (1=yes, 0=no) 10F: --E6
(P+6)h bits 11–29 are reserved; undefined bits are “0.” If bit 31 is 110: --01
(P+7)h “1” then another 31 bit field of Optional features follows at 111: --00
(P+8)h the end of the bit–30 field. 112: See table below
bit 0 Chip erase supported bit 0 = 0 No
bit 1 Suspend erase supported bit 1 = 1 Yes
bit 2 Suspend program supported bit 2 = 1 Yes
bit 3 Legacy lock/unlock supported bit 3 = 0 No
bit 4 Queued erase supported bit 4 = 0 No
bit 5 Instant individual block locking supported bit 5 = 1 Yes
bit 6 Protection bits supported bit 6 = 1 Yes
bit 7 Pagemode read supported bit 7 = 1 Yes
bit 8 Synchronous read supported bit 8 = 1 Yes
bit 9 Simultaneous operations supported bit 9 = 0 No
bit 10 Extended Flash Array Blocks supported bit 10 = 0 No
bit 30 CFI Link(s) to follow bit 30 See
table
bit 31 Another "Optional Features" field to follow bit 31 below
(P+9)h 1 Supported functions after suspend: read Array, Status, Query 113: --01
Other supported operations are:
bits 1–7 reserved; undefined bits are “0”
bit 0 Program supported after erase suspend bit 0 =1 Yes
(P+A)h 2 Block status register mask 114: --03
(P+B)h bits 2–15 are Reserved; undefined bits are “0” 115: --00
bit 0 Block Lock-Bit Status register active bit 0 =1 Yes
bit 1 Block Lock-Down Bit Status active bit 1 =1 Yes
bit 4 EFA Block Lock-Bit Status register active bit 4 =0 No
bit 5 EFA Block Lock-Down Bit Status active bit 5 =0 No
(P+C)h 1 VCC logic supply highest performance program/erase voltage 116: --18 1.8V
bits 0–3 BCD value in 100 mV
bits 4–7 BCD value in volts
(P+D)h 1 VPP optimum program/erase supply voltage 117: --90 9.0V
bits 0–3 BCD value in 100 mV
bits 4–7 HEX value in volts
Address Discrete 512-Mbit

–B –T –B –T
–- –- die 1 (B) die 2 (T) die 1 (T) die 2 (B)
112: --00 --00 --40 --00 --40 --00

Table 36. Protection Register Information
(1)
Offset Length Description Hex
(P+E)h 1 Number of Protection register fields in JEDEC ID space. 118: --02 2
“00h,” indicates that 256 protection fields are available
(P+F)h 4 Protection Field 1: Protection Description 119: --80 80h
(P+10)h This field describes user-available One Time Programmable 11A: --00 00h
(P+11)h (OTP) Protection register bytes. Some are pre-programmed 11B: --03 8 byte
(P+12)h with device-unique serial numbers. Others are user 11C: --03 8 byte
programmable. Bits 0–15 point to the Protection register Lock
byte, the section’s first byte. The following bytes are factory
pre-programmed and user-programmable.
bits 0–7 = Lock/bytes Jedec-plane physical low address

bits 8–15 = Lock/bytes Jedec-plane physical high address
bits 16–23 = “n” such that 2n = factory pre-programmed bytes
bits 24–31 = “n” such that 2n = user programmable bytes
(P+13)h 10 Protection Field 2: Protection Description 11D: --89 89h

(P+14)h Bits 0–31 point to the Protection register physical Lock-word 11E: --00 00h
(P+15)h address in the Jedec-plane. 11F: --00 00h
(P+16)h Following bytes are factory or user-programmable. 120: --00 00h
(P+17)h bits 32–39 = “n” ∴ n = factory pgm'd groups (low byte) 121: --00 0
(P+18)h bits 40–47 = “n” ∴ n = factory pgm'd groups (high byte) 122: --00 0
(P+19)h bits 48–55 = “n” \ 2n = factory programmable bytes/group 123: --00 0
(P+1A)h bits 56–63 = “n” ∴ n = user pgm'd groups (low byte) 124: --10 16
(P+1B)h bits 64–71 = “n” ∴ n = user pgm'd groups (high byte) 125: --00 0
(P+1C)h bits 72–79 = “n” ∴ 2n = user programmable bytes/group 126: --04 16
Table 37. Burst Read Information

(1)
(P+1D)h 1 Page Mode Read capability 127: --03 8 byte
bits 0–7 = “n” such that 2n HEX value represents the number of
read-page bytes. See offset 28h for device word width to
determine page-mode data output width. 00h indicates no
read page buffer.
(P+1E)h 1 Number of synchronous mode read configuration fields that 128: --04 4
follow. 00h indicates no burst capability.
(P+1F)h 1 Synchronous mode read capability configuration 1 129: --01 4
Bits 3–7 = Reserved
bits 0–2 “n” such that 2n+1 HEX value represents the
maximum number of continuous synchronous reads when
the device is configured for its maximum word width. A value
of 07h indicates that the device is capable of continuous
linear bursts that will output data until the internal burst
counter reaches the end of the device’s burstable address
space. This field’s 3-bit value can be written directly to the
Read Configuration Register bits 0–2 if the device is
configured for its maximum word width. See offset 28h for
word width to determine the burst data output width.
(P+20)h 1 Synchronous mode read capability configuration 2 12A: --02 8
(P+21)h 1 Synchronous mode read capability configuration 3 12B: --03 16
(P+22)h 1 Synchronous mode read capability configuration 4 12C: --07 Cont

Table 38. Partition and Erase Block Region Information
(1) See table below

Offset
P = 10Ah Description Address
Bottom Top (Optional flash features and commands) Len Bot Top
Number of device hardware-partition regions within the device. 1 12D: 12D:
x = 0: a single hardware partition device (no fields follow).
x specifies the number of device partition regions containing
(P+23)h (P+23)h one or more contiguous erase block regions.
Table 39. Partition Region 1 Information
Offset(1) See table below

(P+24)h (P+24)h Data size of this Parition Region Information field 2 12E: 12E
(P+25)h (P+25)h (# addressable locations, including this field) 12F 12F
(P+26)h (P+26)h Number of identical partitions within the partition region 2 130: 130:
(P+27)h (P+27)h 131: 131:
(P+28)h (P+28)h Number of program or erase operations allowed in a partition 1 132: 132:
bits 0–3 = number of simultaneous Program operations
bits 4–7 = number of simultaneous Erase operations
(P+29)h (P+29)h Simultaneous program or erase operations allowed in other partitions while a 1 133: 133:
partition in this region is in Program mode
(P+2A)h (P+2A)h Simultaneous program or erase operations allowed in other partitions while a 1 134: 134:
partition in this region is in Erase mode
(P+2B)h (P+2B)h Types of erase block regions in this Partition Region. 1 135: 135:
x = 0 = no erase blocking; the Partition Region erases in bulk
x = number of erase block regions w/ contiguous same-size
erase blocks. Symmetrically blocked partitions have one
blocking region. Partition size = (Type 1 blocks)x(Type 1
block sizes) + (Type 2 blocks)x(Type 2 block sizes) +…+
(Type n blocks)x(Type n block sizes)

Table 40. Partition Region 1 Information (continued)
Offset(1) See table below

(P+2C)h (P+2C)h Partition Region 1 Erase Block Type 1 Information 4 136: 136:
(P+2D)h (P+2D)h bits 0–15 = y, y+1 = # identical-size erase blks in a partition 137: 137:
(P+2E)h (P+2E)h bits 16–31 = z, region erase block(s) size are z x 256 bytes 138: 138:
(P+2F)h (P+2F)h 139: 139:
(P+30)h (P+30)h Partition 1 (Erase Block Type 1) 2 13A: 13A:
(P+31)h (P+31)h Block erase cycles x 1000 13B: 13B:
(P+32)h (P+32)h Partition 1 (erase block Type 1) bits per cell; internal EDAC 1 13C: 13C:
bits 0–3 = bits per cell in erase region
bit 4 = internal EDAC used (1=yes, 0=no)
bits 5–7 = reserve for future use
(P+33)h (P+33)h Partition 1 (erase block Type 1) page mode and synchronous mode capabilities 1 13D: 13D:
defined in Table 10.
bit 0 = page-mode host reads permitted (1=yes, 0=no)
bit 1 = synchronous host reads permitted (1=yes, 0=no)
bit 2 = synchronous host writes permitted (1=yes, 0=no)
bits 3–7 = reserved for future use
Partition Region 1 (Erase Block Type 1) Programming Region Information 6
(P+34)h (P+34)h bits 0–7 = x, 2^x = Programming Region aligned size (bytes) 13E: 13E:
(P+35)h (P+35)h bits 8–14 = Reserved; bit 15 = Legacy flash operation (ignore 0:7) 13F: 13F:
(P+36)h (P+36)h bits 16–23 = y = Control Mode valid size in bytes 140: 140:
(P+37)h (P+37)h bits 24-31 = Reserved 141: 141:
(P+38)h (P+38)h bits 32-39 = z = Control Mode invalid size in bytes 142: 142:
(P+39)h (P+39)h bits 40-46 = Reserved; bit 47 = Legacy flash operation (ignore 23:16 & 39:32) 143: 143:
(P+3A)h (P+3A)h Partition Region 1 Erase Block Type 2 Information 4 144: 144:
(P+3B)h (P+3B)h bits 0–15 = y, y+1 = # identical-size erase blks in a partition 145: 145:
(P+3C)h (P+3C)h bits 16–31 = z, region erase block(s) size are z x 256 bytes 146: 146:
(P+3D)h (P+3D)h 147: 147:
(P+3E)h (P+3E)h Partition 1 (Erase Block Type 2) 2 148: 148:
(P+3F)h (P+3F)h Block erase cycles x 1000 149: 149:
(P+40)h (P+40)h Partition 1 (erase block Type 2) bits per cell; internal EDAC 1 14A: 14A:
bits 0–3 = bits per cell in erase region
bit 4 = internal EDAC used (1=yes, 0=no)
bits 5–7 = reserve for future use
(P+41)h (P+41)h Partition 1 (erase block Type 2) page mode and synchronous mode capabilities 1 14B: 14B:
defined in Table 10.
bit 0 = page-mode host reads permitted (1=yes, 0=no)
bit 1 = synchronous host reads permitted (1=yes, 0=no)
bit 2 = synchronous host writes permitted (1=yes, 0=no)
bits 3–7 = reserved for future use
Partition Region 1 (Erase Block Type 2) Programming Region Information 6
(P+42)h (P+42)h bits 0–7 = x, 2^x = Programming Region aligned size (bytes) 14C: 14C:
(P+43)h (P+43)h bits 8–14 = Reserved; bit 15 = Legacy flash operation (ignore 0:7) 14D: 14D:
(P+44)h (P+44)h bits 16–23 = y = Control Mode valid size in bytes 14E: 14E:
(P+45)h (P+45)h bits 24-31 = Reserved 14F: 14F:
(P+46)h (P+46)h bits 32-39 = z = Control Mode invalid size in bytes 150: 150:
(P+47)h (P+47)h bits 40-46 = Reserved; bit 47 = Legacy flash operation (ignore 23:16 & 39:32) 151: 151:

Table 41. Partition and Erase Block Region Information
Address 64-Mbit 128-Mbit 256-Mbit

–B –T –B –T –B –T
12D: --01 --01 --01 --01 --01 --01
12E: --24 --24 --24 --24 --24 --24
12F: --00 --00 --00 --00 --00 --00
130: --01 --01 --01 --01 --01 --01
131: --00 --00 --00 --00 --00 --00
132: --11 --11 --11 --11 --11 --11
133: --00 --00 --00 --00 --00 --00
134: --00 --00 --00 --00 --00 --00
135: --02 --02 --02 --02 --02 --02
136: --03 --3E --03 --7E --03 --FE
137: --00 --00 --00 --00 --00 --00
138: --80 --00 --80 --00 --80 --00
139: --00 --02 --00 --02 --00 --02
13A: --64 --64 --64 --64 --64 --64
13B: --00 --00 --00 --00 --00 --00
13C: --02 --02 --02 --02 --02 --02
13D: --03 --03 --03 --03 --03 --03
13E: --00 --00 --00 --00 --00 --00
13F: --80 --80 --80 --80 --80 --80
140: --00 --00 --00 --00 --00 --00
141: --00 --00 --00 --00 --00 --00
142: --00 --00 --00 --00 --00 --00
143: --80 --80 --80 --80 --80 --80
144: --3E --03 --7E --03 --FE --03
145: --00 --00 --00 --00 --00 --00
146: --00 --80 --00 --80 --00 --80
147: --02 --00 --02 --00 --02 --00
148: --64 --64 --64 --64 --64 --64
149: --00 --00 --00 --00 --00 --00
14A: --02 --02 --02 --02 --02 --02
14B: --03 --03 --03 --03 --03 --03
14C: --00 --00 --00 --00 --00 --00
14D: --80 --80 --80 --80 --80 --80
14E: --00 --00 --00 --00 --00 --00
14F: --00 --00 --00 --00 --00 --00
150: --00 --00 --00 --00 --00 --00
151: --80 --80 --80 --80 --80 --80

Table 42. CFI Link Information

(1)
(P+48)h 4 CFI Link Field bit definitions 152:
(P+49)h Bits 0–9 = Address offset (within 32Mbit segment) of referenced CFI table 153:
(P+4A)h Bits 10–27 = nth 32Mbit segment of referenced CFI table 154: See table below
(P+4B)h Bits 28–30 = Memory Type 155:
Bit 31 = Another CFI Link field immediately follows
(P+4C)h 1 CFI Link Field Quantity Subfield definitions 156:
Bits 0–3 = Quantity field (n such that n+1 equals quantity)
Bit 4 = Table & Die relative location See table below
Bit 5 = Link Field & Table relative location
Bits 6–7 = Reserved
Address Discrete 512-Mbit

–B –T –B –T
–- –- die 1 (B) die 2 (T) die 1 (T) die 2 (B)
152: --FF --FF --10 --FF --10 --FF
153: --FF --FF --20 --FF --20 --FF
154: --FF --FF --00 --FF --00 --FF
155: --FF --FF --00 --FF --00 --FF
156: --FF --FF --10 --FF --10 --FF

Appendix D Additional Information
Order/Document
Document/Tool
Number
309045 P30 Family Specification Update

308291 Schematic Review Checklist for Intel StrataFlash ® Embedded Memory (P30)
300783 Using Intel® Flash Memory: Asynchronous Page Mode and Synchronous Burst Mode
290667 Intel StrataFlash® Memory (J3) Datasheet
Migration Guide for Intel StrataFlash® Memory (J3) to Intel StrataFlash® Embedded
306667 Memory (P30) Application Note 812
290737 Intel StrataFlash® Synchronous Memory (K3/K18) Datasheet
Migration Guide for Intel StrataFlash® Synchronous Memory (K3/K18) to Intel
306669
StrataFlash® Embedded Memory (P30) Application Note 825
290701 Intel® Wireless Flash Memory (W18) Datasheet
290702 Intel® Wireless Flash Memory (W30) Datasheet
252802 Intel® Flash Memory Design for a Stacked Chip Scale Package (SCSP)
298161 Intel® Flash Memory Chip Scale Package User’s Guide
253418 Intel® Wireless Communications and Computing Package User's Guide
296514 Intel® Small Outline Package Guide
297833 Intel® Flash Data Integrator (Intel® FDI) User Guide
298136 Intel® Persistent Storage Manager (Intel® PSM) User Guide
Migration Guide for Spansion* S29GLxxxN to Intel StrataFlash® Embedded Memory
306668
(P30) Application Note 813
Notes:
1. Please call the Intel Literature Center at (800) 548-4725 to request Intel documentation. International
customers should contact their local Intel or distribution sales office.
2. Visit Intel’s World Wide Web home page at http://www.intel.com for technical documentation and
tools.
3. For the most current information on Intel ® Flash Memory, visit our website at
http://www.intel.com/go/choosesmart.

Appendix E Ordering Information for Discrete Products

Figure 46. Decoder for Discrete Intel StrataFlash® Embedded Memory (P30)
T E 2 8 F 6 4 0 P 3 0 B 8 5
Package Designator Access Speed

TE = 56-Lead TSOP, leaded 85 ns
JS = 56-Lead TSOP, lead-free
RC = 64-Ball Easy BGA, leaded Param eter Location
PC = 64-Ball Easy BGA, lead-free B = Bottom Parameter
T = Top Parameter
Product Line Designator
28F = Intel® Flash Memory Product Fam ily
P30 = Intel StrataFlash® Embedded Memory
Device Density V CC = 1.7 – 2.0 V
640 = 64-Mbit V CCQ = 1.7 – 3.6 V
128 = 128-Mbit
256 = 256-Mbit
Table 43. Valid Combinations for Discrete Products

64-Mbit 128-Mbit 256-Mbit
TE28F640P30B85 TE28F128P30B85 TE28F256P30B95

TE28F640P30T85 TE28F128P30T85 TE28F256P30T95
JS28F640P30B85 JS28F128P30B85 JS28F256P30B95
JS28F640P30T85 JS28F128P30T85 JS28F256P30T95
RC28F640P30B85 RC28F128P30B85 RC28F256P30B85
RC28F640P30T85 RC28F128P30T85 RC28F256P30T85
PC28F640P30B85 PC28F128P30B85 PC28F256P30B85
PC28F640P30T85 PC28F128P30T85 PC28F256P30T85

Appendix F Ordering Information for SCSP Products
Figure 47. Decoder for SCSP Intel StrataFlash® Embedded Memory (P30)
Flash Family 1/2
Flash Family 3/4

Flash #1
Flash #2
Flash #3
Flash #4
R D 4 8 F 4 0 0 0 P 0 Z B Q 0
Package Designator
RD = Intel ® SCSP, leaded Device Details
P F = Intel® SCSP, lead-free 0 = O riginal version of the product
RC = 64-Ball Easy BG A, leaded (refer to the latest version of the
P C = 64-Ball Easy BG A, lead-free datasheet for details)
T E = 56-Lead TSO P , leaded
JS = 56-Lead T SO P, lead-free
Ballout Designator
Group Designator Q = Q UAD+ ballout
48F = Flash Memory only 0 = Discrete ballout
Flash Density Param eter, M ux Configuration

0 = No die B = Bottom Param eter, Non Mux
2 = 64-Mbit T = Top Param eter, Non M ux
3 = 128-M bit
4 = 256-M bit I/O Voltage, CE# Configuration
Z = Individual Chip Enable(s)
Product Fam ily
V = Virtual Chip E nable(s)
P = Intel StrataF lash® Em bedded M em ory
V C C = 1.7 V – 2.0 V
0 = No die
V C C Q = 1.7 V – 3.6 V
Table 44. Valid Combinations for Dual- Die Products

64-Mbit 128-Mbit 256-Mbit 512-Mbit
RD48F2000P0ZBQ0 RD48F3000P0ZBQ0 RD48F4000P0ZBQ0 RD48F4400P0VBQ0

RD48F2000P0ZTQ0 RD48F3000P0ZTQ0 RD48F4000P0ZTQ0 RD48F4400P0VTQ0
PF48F2000P0ZBQ0 PF48F3000P0ZBQ0 PF48F4000P0ZBQ0 PF48F4400P0VBQ0
PF48F2000P0ZTQ0 PF48F3000P0ZTQ0 PF48F4000P0ZTQ0 PF48F4400P0VTQ0
RC48F4400P0VB00
RC48F4400P0VT00
PC48F4400P0VB00
PC48F4400P0VT00
TE48F4400P0VB00
TE48F4400P0VT00
JS48F4400P0VB00
JS48F4400P0VT00


StrataFlash P30-T Data Sheet

Uploaded by

Copyright:

Available Formats

StrataFlash P30-T Data Sheet

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

StrataFlash P30-T Data Sheet

Uploaded by

Copyright:

Available Formats

Intel StrataFlash® Embedded Memory

Order Number: 306666, Revision: 007

1-May-2006 Intel StrataFlash® Embedded Memory (P30) Datasheet

Datasheet Intel StrataFlash® Embedded Memory (P30) 1-May-2006

9.3 Command Definitions ......................................................................................................... 51

1-May-2006 Intel StrataFlash® Embedded Memory (P30) Datasheet

14.2 Read Device Identifier ........................................................................................................ 75

Datasheet Intel StrataFlash® Embedded Memory (P30) 1-May-2006

April 2005 -001 Initial Release

1-May-2006 Intel StrataFlash® Embedded Memory (P30) Datasheet

1.8 V: VCC (core) voltage range of 1.7 V – 2.0 V

BEFP: Buffer Enhanced Factory Programming

Datasheet Intel StrataFlash® Embedded Memory (P30) 1-May-2006

VCC: Signal or voltage connection

1-May-2006 Intel StrataFlash® Embedded Memory (P30) Datasheet

2.0 Functional Overview

2.1 Virtual Chip Enable Description

Datasheet Intel StrataFlash® Embedded Memory (P30) 1-May-2006

Lower Param Die L L

Lower Param Die L L

1-May-2006 Intel StrataFlash® Embedded Memory (P30) Datasheet

3.0 Package Information

3.1 56-Lead TSOP Package

Figure 1. TSOP Mechanical Specifications

Table 3. TSOP Package Dimensions (Sheet 1 of 2)

Package Height A - - 1.200 - - 0.047

Standoff A1 0.050 - - 0.002 - -

Package Body Thickness A2 0.965 0.995 1.025 0.038 0.039 0.040

Lead Width b 0.100 0.150 0.200 0.004 0.006 0.008

Lead Thickness c 0.100 0.150 0.200 0.004 0.006 0.008

Package Body Length D1 18.200 18.400 18.600 0.717 0.724 0.732 4

Package Body Width E 13.800 14.000 14.200 0.543 0.551 0.559 4

Datasheet Intel StrataFlash® Embedded Memory (P30) 1-May-2006

Table 3. TSOP Package Dimensions (Sheet 2 of 2)

Lead Pitch e - 0.500 - - 0.0197 -

Terminal Dimension D 19.800 20.00 20.200 0.780 0.787 0.795

Lead Tip Length L 0.500 0.600 0.700 0.020 0.024 0.028

Lead Tip Angle ∅ 0° 3° 5° 0° 3° 5°

Seating Plane Coplanarity Y - - 0.100 - - 0.004

Lead to Package Offset Z 0.150 0.250 0.350 0.006 0.010 0.014

1-May-2006 Intel StrataFlash® Embedded Memory (P30) Datasheet

3.2 64-Ball Easy BGA Package

Figure 2. Easy BGA Mechanical Specifications

Top View - Ball side down Bottom View - Ball Side Up

Table 4. Easy BGA Package Dimensions (Sheet 1 of 2)

Package Height (64/128/256-Mbit) A - - 1.200 - - 0.0472

Datasheet Intel StrataFlash® Embedded Memory (P30) 1-May-2006

Table 4. Easy BGA Package Dimensions (Sheet 2 of 2)

1-May-2006 Intel StrataFlash® Embedded Memory (P30) Datasheet

3.3 QUAD+ SCSP Packages

Top View - Ball

D raw ing not to sc ale.

Datasheet Intel StrataFlash® Embedded Memory (P30) 1-May-2006

Top View - Ball Down Bottom View - Ball Up

D raw ing not to scale.

Note: Dimensions A1, A2, and b are preliminary

1-May-2006 Intel StrataFlash® Embedded Memory (P30) Datasheet

Top View - Ball Down Bottom View - Ball Up

D raw ing not to scale .

Datasheet Intel StrataFlash® Embedded Memory (P30) 1-May-2006