314749-05
November 2007
Numonyx™ StrataFlash® Embedded Memory
(P33)
Datasheet
Product Features
High performance:
85 ns initial access
52MHz with zero wait states, 17ns clock-to-
data output synchronous-burst read mode
25 ns asynchronous-page read mode
4-, 8-, 16-, and continuous-word burst
mode
Buffered Enhanced Factory Programming
(BEFP) at 5 µs/byte (Typ)
3.0 V buffered programming at 7 µs/byte
(Typ)
Architecture:
Multi-Level Cell Technology: Highest
Density at Lowest Cost
Asymmetrically-blocked architecture
Four 32-KByte parameter blocks: top or
bottom configuration
128-KByte main blocks
Voltage and Power:
—V
CC (core) voltage: 2.3 V – 3.6 V
—V
CCQ (I/O) voltage: 2.3 V – 3.6 V
Standby current: 35µA (Typ) for 64-Mbit
4-Word synchronous read current:
16 mA (Typ) at 52MHz
Quality and Reliability
Operating temperature: –40 °C to +85 °C
Minimum 100,000 erase cycles per block
ETOX™ VIII process technology
Security:
One-Time Programmable Registers:
64 unique factory device identifier bits
2112 user-programmable OTP bits
Selectable OTP space in Main Array:
Four pre-defined 128-KByte blocks (top or
bottom configuration).
—Up to Full Array OTP Lockout
Absolute write protection: VPP = VSS
Power-transition erase/program lockout
Individual zero-latency block locking
Individual block lock-down capability
Software:
20 µs (Typ) program suspend
20 µs (Typ) erase suspend
Numonyx™ Flash Data Integrator optimized
Basic Command Set and Extended
Command Set compatible
Common Flash Interface capable
Density and Packaging
56-Lead TSOP package (64, 128, 256, 512-
Mbit)
64-Ball Numonyx™ Easy BGA package (64,
128, 256, 512-Mbit)
Numonyx™ QUAD+ SCSP (64, 128, 256,
512-Mbit)
16-bit wide data bus
Datasheet November 2007
2314749-05
Legal L ines and Disclaimers
INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH NUMONYX PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR
OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN NUMONYX'S TERMS AND
CONDITIONS OF SALE FOR SUCH PRODUCTS, NUMONYX ASSUMES NO LIABILITY WHATSOEVER, AND NUMONYX DISCLAIMS ANY EXPRESS OR IMPLIED
WARRANTY, RELATING TO SALE AND/OR USE OF NUMONYX PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A
PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT. Numonyx
products are not intended for use in medical, life saving, life sustaining, critical control or safety systems, or in nuclear facility applications.
Numonyx may make changes to specifications and product descriptions at any time, without notice.
Numonyx, B.V. 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.
Designers must not rely on the absence or characteristics of any features or instructions marked “reserved” or “undefined. Numonyx reserves these for
future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them.
Contact your local Numonyx 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 Numonyx literature may be obtained by visiting
Numonyx's website at http://www.numonyx.com.
Numonyx, the Numonyx logo, and StrataFlash are trademarks or registered trademarks of Numonyx , B.V. or its subsidiaries in other countries.
*Other names and brands may be claimed as the property of others.
Copyright © 2007, Numonyx, B.V., All Rights Reserved.
November 2007 Datasheet
314749-05 3
Numonyx™ StrataFlash® Embedded Memory (P33)
Contents
1.0 Introduction .............................................................................................................. 6
1.1 Nomenclature ..................................................................................................... 6
1.2 Acronyms........................................................................................................... 6
1.3 Conventions ....................................................................................................... 7
2.0 Functional Overview..................................................................................................8
2.1 Virtual Chip Enable Description.............................................................................. 8
3.0 Package Information ............................................................................................... 10
3.1 56-Lead TSOP................................................................................................... 10
3.2 64-Ball Easy BGA Package .................................................................................. 11
3.3 QUAD+ SCSP Packages...................................................................................... 14
4.0 Ballout and Signal Descriptions ............................................................................... 17
4.1 Signal Ballout ................................................................................................... 17
4.2 Signal Descriptions ............................................................................................ 19
4.3 Dual Die SCSP Configurations ............................................................................. 22
4.4 Memory Maps ................................................................................................... 22
5.0 Maximum Ratings and Operating Conditions............................................................ 26
5.1 Absolute Maximum Ratings................................................................................. 26
5.2 Operating Conditions ......................................................................................... 26
6.0 Electrical Specifications ........................................................................................... 27
6.1 DC Current Characteristics.................................................................................. 27
6.2 DC Voltage Characteristics.................................................................................. 28
7.0 AC Characteristics ................................................................................................... 29
7.1 AC Test Conditions ............................................................................................ 29
7.2 Capacitance...................................................................................................... 30
7.3 AC Read Specifications....................................................................................... 30
7.4 AC Write Specifications ...................................................................................... 36
7.5 Program and Erase Characteristics....................................................................... 39
8.0 Power and Reset Specifications ............................................................................... 41
8.1 Power-Up and Power-Down................................................................................. 41
8.2 Reset Specifications........................................................................................... 41
8.3 Power Supply Decoupling ................................................................................... 42
9.0 Bus Operations ........................................................................................................ 43
9.1 Read ............................................................................................................... 43
9.2 Write ............................................................................................................... 43
9.3 Output Disable.................................................................................................. 43
9.4 Standby ........................................................................................................... 44
9.5 Reset............................................................................................................... 44
9.6 Device Command Bus Cycles .............................................................................. 44
10.0 Command Definitions .............................................................................................. 46
11.0 Device Operations ................................................................................................... 48
11.1 Status Register ................................................................................................. 48
11.2 Read Operations ............................................................................................... 55
11.2.1 Asynchronous Page-Mode Read ................................................................ 55
11.2.2 Synchronous Burst-Mode Read................................................................. 56
11.2.3 Read Device Identifier............................................................................. 56
11.2.4 CFI Query ............................................................................................. 57
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
4314749-05
11.3 Programming Operations ....................................................................................57
11.3.1 Word Programming .................................................................................58
11.3.2 Buffered Programming ............................................................................58
11.3.3 Buffered Enhanced Factory Programming ...................................................59
11.3.4 Program Suspend ...................................................................................61
11.3.5 Program Resume ....................................................................................62
11.3.6 Program Protection .................................................................................62
11.4 Erase Operations ...............................................................................................62
11.4.1 Block Erase............................................................................................62
11.4.2 Erase Suspend .......................................................................................63
11.4.3 Erase Resume ........................................................................................63
11.4.4 Erase Protection .....................................................................................63
11.4.5 Security Modes.......................................................................................64
11.4.6 Block Locking .........................................................................................64
11.4.7 Selectable One-Time Programmable Blocks ................................................66
11.4.8 Protection Registers ................................................................................66
12.0 Flowcharts ...............................................................................................................69
13.0 Common Flash Interface ..........................................................................................77
13.1 Query Structure Output ......................................................................................77
13.2 CFI Query Identification String ............................................................................78
13.3 Device Geometry Definition .................................................................................80
13.4 Numonyx-Specific Extended Query Table ..............................................................81
14.0 Write State Machine.................................................................................................87
A Additional Information.............................................................................................94
B Ordering Information for Discrete Products .............................................................95
C Ordering Information for SCSP Products ..................................................................96
November 2007 Datasheet
314749-05 5
Numonyx™ StrataFlash® Embedded Memory (P33)
Revision History
Date Revision Description
April 2006 001 Initial release
August 2006 002 Product release
May 2007 003
Update and provide general document clarifications
Revise ICCR values for Page-Mode Read
Added note for Vccq change on TSOP burst operation
Added TSOP Burst AC Read specification
Updated new revision of CFI
Updated Flowcharts
Updated description of Burst Operation
Document changes regarding burst operation with the TSOP package.
October 2007 004 Updated for 65nm lithography.
Define W602 Erase to Suspend.
November 2007 05 Applied Numonyx template and datasheet organization.
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
6Order Number: 314749-05
1.0 Introduction
This document provides information about the Numonyx™ StrataFlash® Embedded
Memory (P33) device and describes its features, operation, and specifications.
P33 is the latest generation of Numonyx™ StrataFlash® memory devices. Offered in
64-Mbit up through 512-Mbit densities, the P33 flash memory 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.
P33 product family is manufactured using Intel* 130 nm ETOX™ VIII process
technology. The P33 product family is also planned on the Numonyx™ 65nm process
lithography. 65nm AC timing changes are noted in this datasheet, and should be taken
into account for all new designs
1.1 Nomenclature
1.2 Acronyms
3.0 V : VCC (core) and VCCQ (I/O) voltage range of 2.3 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. The Numonyx StrataFlash® Embedded Memory (P33) 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 may be 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.
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
November 2007 Datasheet
Order Number: 314749-05 7
Numonyx™ StrataFlash® Embedded Memory (P33)
1.3 Conventions
VCC : Signal or voltage connection
VCC : Signal or voltage level
0h : Hexadecimal number suffix
0b : Binary number suffix
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 : Single 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
K 1,000
M 1,000,000
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
8Order Number: 314749-05
2.0 Functional Overview
This section provides an overview of the features and capabilities of the Numonyx™
StrataFlash® Embedded Memory (P33) device.
The Kearny Family Flash memory 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 RCR 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 Kearny Family Flash memory supports read operations with VCC at
3.0V, and erase and program operations with VPP at 3.0V or 9.0V. BEFP provides the
fastest flash array programming performance with VPP at 9.0V, which increases factory
throughput. With VPP at 3.0V, 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.
The CUI is the interface between the system processor and all internal operations of
the device. An internal 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 Kearny Family Flash memory 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 Kearny
Family Flash memory may also pre-define main array space as OTP.
2.1 Virtual Chip Enable Description
The 512 Mbit Kearny Family Flash memory employs 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 packages (refer to Figure 10 and Figure 11 for additional details).
Address A24 (QUAD+ package) or A25 (Easy BGA and TSOP package) 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 (Easy BGA A25) is low
(VIL), The lower parameter die is selected; when chip enable is asserted and QUAD+
A24 (Easy BGA A25) is high (VIH), the upper parameter die is selected. Refer to Tab le 1,
“Flash Die Virtual Chip Enable Truth Table for 512 Mbit QUAD+ Package” and Table 2,
“Flash Die Virtual Chip Enable Truth Table for 512 Mbit TSOP / Easy BGA Package” for
additional details.
November 2007 Datasheet
Order Number: 314749-05 9
Numonyx™ StrataFlash® Embedded Memory (P33)
Table 1: Flash Die Virtual Chip Enable Truth Table for 512 Mbit QUAD+ Package
Die Selected F1-CE# A24
Lower Param Die L L
Upper Param Die L H
Table 2: Flash Die Virtual Chip Enable Truth Table for 512 Mbit TSOP / Easy BGA Package
Die Selected CE# A25
Lower Param Die L L
Upper Param Die L H
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
10 Order Number: 314749-05
3.0 Package Information
3.1 56-Lead TSOP
Figure 1: TSOP Mechanical Specifications
Table 3: TSOP Package Dimensions (Sheet 1 of 2)
Product Information Symbol
Millimeters Inches
Notes
Min Nom Max Min Nom Max
Package Height A - - 1.200 - - 0.047
Standoff A10.050 - - 0.002 - -
Package Body Thickness A20.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 D118.200 18.400 18.600 0.717 0.724 0.732
Package Body Width E 13.800 14.000 14.200 0.543 0.551 0.559
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
A
0
L
Detail A
Y
D
C
Z
Pin 1
E
D1
b
Detail B
See Detail A
e
See Detail B
A1
Seating
Plane
A2
See Note 2
[231369-90]
See Notes 1 and 3
November 2007 Datasheet
Order Number: 314749-05 11
Numonyx™ StrataFlash® Embedded Memory (P33)
3.2 64-Ball Easy BGA Package
Lead Count N - 56 - - 56 -
Lead Tip Angle ý
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.
Table 3: TSOP Package Dimensions (Sheet 2 of 2)
Product Information Symbol
Millimeters Inches
Notes
Min Nom Max Min Nom Max
Figure 2: 64-Mbit and 128-Mbit Easy BGA Mechanical Specifications
E
Seating
Plane
S1
S2
e
Top View - Ball side down Bottom View - Ball Side Up
Y
A
A1
D
Ball A1
Corner
A2
Note: Drawing not to scale
A
B
C
D
E
F
G
H
876543 2 1
87654321
A
B
C
D
E
F
G
H
b
Ball A1
Corner
Table 4: 64-Mbit and 128-Mbit Easy BGA Package Dimensions (Sheet 1 of 2)
Product Information Symbol
Millimeters Inches
Notes
Min Nom Max Min Nom Max
Package Height A - - 1.200 - - 0.0472
Ball Height A1 0.250 - - 0.0098 - -
Package Body Thickness A2 - 0.780 - - 0.0307 -
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
12 Order Number: 314749-05
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 7.900 8.000 8.100 0.3110 0.3149 0.3189 1
Pitch [e] - 1.000 - - 0.0394 -
Ball (Lead) Count N - 64 - - 64 -
Seating Plane Coplanarity Y - - 0.100 - - 0.0039
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 0.400 0.500 0.600 0.0157 0.0197 0.0236 1
Notes:
1. Daisy Chain Evaluation Unit information is at Nu;monyx Flash Memory Packaging Technology http://
developer.Numonyx.com/design/flash/packtech.
Figure 3: 256-Mbit and 512-Mbit Easy BGA Mechanical Specifications
Table 4: 64-Mbit and 128-Mbit Easy BGA Package Dimensions (Sheet 2 of 2)
Product Information Symbol
Millimeters Inches
Notes
Min Nom Max Min Nom Max
E
Seating
Plane
S1
S2
e
Top View - Ball side down Bottom View - Ball Side Up
Y
A
A1
D
Ball A1
Corner
A2
Note: Drawing not to scale
A
B
C
D
E
F
G
H
8765432187654321
A
B
C
D
E
F
G
H
b
Ball A1
Corner
November 2007 Datasheet
Order Number: 314749-05 13
Numonyx™ StrataFlash® Embedded Memory (P33)
Table 5: 256-Mbit and 512-Mbit Easy BGA Package Dimensions
Product Information Symbol
Millimeters Inches
Notes
Min Nom Max Min Nom Max
Package Height (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 (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-
Seating Plane Coplanarity Y - - 0.100 - - 0.0039
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 Numonyx™ Flash Memory Packaging Technology http://
developer.numonyx.com/design/flash/packtech.
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
14 Order Number: 314749-05
3.3 QUAD+ SCSP Packages
Figure 4: 64/128-Mbit, 88-ball (80 active) QUAD+ SCSP Specifications (8x10x1.2 mm)
Millimeters Inches
Di me ns i on s S ymbol Mi n No m Max Mi n N om Max
Package Height A - - 1.200 - - 0.0472
Ball Height A
1
0.200 - - 0.0079 - -
Package Body Thickness A
2
- 0.860 - - 0.0339 -
Ball (Lead) W idth 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 Len gth E 7.900 8.000 8.100 0.3110 0.3150 0.3189
Pitch e - 0.800 - - 0.0315 -
Ball (Lead) Count N - 88 - - 88 -
Seating Plane Coplanarity Y - - 0.100 - - 0.0039
Corner to Ball A1 Distance Along E S
1
1.100 1.200 1.300 0.0433 0.0472 0.0512
Corner to Ball A1 Distance Along D S
2
0.500 0.600 0.700 0.0197 0.0236 0.0276
Top View - Ball
Down Bottom View - Ball Up
A
A
2
D
E
Y
A
1
Drawing not to scale.
S
2
S
1
A
C
B
E
D
G
F
J
H
K
L
M
e
12345678
b
A
C
B
E
D
G
F
J
H
K
L
M
12345678
A1 Index
Mark
November 2007 Datasheet
Order Number: 314749-05 15
Numonyx™ StrataFlash® Embedded Memory (P33)
Figure 5: 256-Mbit, 88-ball (80 active) QUAD+ SCSP Specifications (8x11x1.0 mm)
Millimeters Inches
Dimens i ons S ymbol Mi n Nom Max Min Nom Max
Package Height A - - 1.000 - - 0.0394
Ball Height A1 0.117 - - 0.0046 - -
Package Body Thickn es s A2 - 0.740 - - 0.0291 -
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 W idth E 7.900 8.00 8.100 0.3110 0.3150 0.3189
Pitch e - 0.80 - - 0.0315 -
Ball (Lead) Count N - 88 - - 88 -
Seating Plane Coplanarity Y - - 0.100 - - 0.0039
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 1.000 1.100 1.200 0.0394 0.0433 0.0472
Top View - Ball Down Bottom View - Ball Up
A
A2
D
E
Y
A1
Drawing not to scale.
S2
S1
A
C
B
E
D
G
F
J
H
K
L
M
e
12345678
b
A
C
B
E
D
G
F
J
H
K
L
M
A1 Index
Mark
12 3456 78
Note: Dimensions A1, A2, and b are preliminary
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
16 Order Number: 314749-05
Figure 6: 512-Mbit, 88-ball (80 active) QUAD+ SCSP Specifications (8x11x1.2 mm)
Millimeters Inches
Dimens ions 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 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 -
Ball (Lead) Count N - 88 - - 88 -
Seating Plane Coplanarity Y - - 0.100 - - 0.0039
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 1.000 1.100 1.200 0.0394 0.0433 0.0472
Top View - Ball Down Bottom View - Ball Up
A
A2
D
E
Y
A1
Drawing not to scale.
S2
S1
A
C
B
E
D
G
F
J
H
K
L
M
e
12345678
b
A
C
B
E
D
G
F
J
H
K
L
M
A1 Index
Mark
12 34 5678
November 2007 Datasheet
Order Number: 314749-05 17
Numonyx™ StrataFlash® Embedded Memory (P33)
4.0 Ballout and Signal Descriptions
4.1 Signal Ballout
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 and above; otherwise, it is a no connect (NC).
4. A25 is valid for 512-Mbit densities; otherwise, it is a no connect (NC).
5. Please refer to the latest specification update for synchronous read operation on the TSOP package. The synchronous read
input signals (i.e. ADV# and CLK) should be tied off to support asynchronous reads otherwise. See Section 4.2,
“Signal Descriptions” on page 19. for additional information.
Figure 7: 56-Lead TSOP Pinout (64/128/256/512-Mbit)
P33
56- Lead TSOP Pinout
14 mm x 20 mm
Top View
1
3
4
2
5
7
8
6
9
11
12
10
13
15
16
14
17
19
20
18
21
23
24
22
25
27
28
26
56
54
53
55
52
50
49
51
48
46
45
47
44
42
41
43
40
38
37
39
36
34
33
35
32
30
29
31
A14
A13
A12
A10
A9
A11
A23
A21
VSS
A22
VCC
WP#
A20
WE#
A19
A8
A7
A18
A6
A4
A3
A5
A2
A25
VSS
A24
WAIT
DQ15
DQ7
A17
DQ14
DQ13
DQ5
DQ6
DQ12
ADV#
CLK
DQ4
RST#
A16
DQ3
VPP
DQ10
VCCQ
DQ9
DQ2
DQ1
DQ0
VCC
DQ8
OE#
CE#
A1
VSS
A15
DQ11
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
18 Order Number: 314749-05
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.
3. A24 is valid for 256-Mbit densities and above; otherwise, it is a no connect.
4. A25 is valid for 512-Mbit densities; otherwise, it is a no connect.
Figure 8: 64-Ball Easy BGA Ballout (64/128/256/512-Mbit)
18
234567
Easy BGA
Top View- Ball side down
Easy BGA
Bottom View- Ball side up
1
8234
5
67
H
G
F
E
D
C
B
A
H
G
F
E
D
C
A
A2 VSS A9 A14CE# A19 RFUA25
RFU VSS VCC DQ13VSS DQ7 A24VSS
A3 A7 A10 A15A12 A20 A21WP#
A4 A5 A11 VCCQRST# A16 A17VCCQ
RFUDQ8 DQ1 DQ9 DQ4DQ3 DQ15CLK
RFU OE#DQ0 DQ10 DQ12DQ11 WAITADV#
WE#A23 RFU DQ2 DQ5VCCQ DQ14DQ6
A1 A6 A8 A13VPP A18 A22VCC
A23
A4A5A11VCCQ RST#A16A17 VCCQ
A1A6A8A13 VPPA18A22 VCC
A3A7A10A15 A12A20A21 WP#
RFU DQ8DQ1DQ9DQ4 DQ3DQ15 CLK
RFUOE# DQ0DQ10DQ12 DQ11WAIT ADV#
WE# RFUDQ2DQ5 VCCQDQ14 DQ6
A2VSSA9A14 CE#A19RFU A25
RFUVSSVCCDQ13 VSSDQ7A24 VSS
B
November 2007 Datasheet
Order Number: 314749-05 19
Numonyx™ StrataFlash® Embedded Memory (P33)
Notes:
1. A22 is valid for 128-Mbit densities and above; otherwise, it is a no connect.
2. A23 is valid for 256-Mbit densities and above; otherwise, it is a no connect.
3. A24 is valid for 512-Mbit densities and above; otherwise, it is a no connect.
4. F2-CE# and F2-OE# are no connects.
4.2 Signal Descriptions
This section has signal descriptions for the various Numonyx™ StrataFlash® Embedded
Memory (P33) device packages.
Figure 9: 88-Ball (80-Active Ball) QUAD+ SCSP Ballout
Pin 1
12345678
ADU DU Depop Depop Depop Depop DU DU A
BA4 A18 A19 VSS VCC VCC A21 A11 B
CA5 RFU A23 VSS RFU CLK A22 A12 C
DA3 A17 A24 VPP RFU RFU A9 A13 D
EA2 A7 RFU WP# ADV# A20 A10 A15 E
FA1 A6 RFU RST# WE# A8 A14 A16 F
GA0 DQ8 DQ2 DQ10 DQ5 DQ13 WAIT F2-CE# G
HRFU DQ0 DQ1 DQ3 DQ12 DQ14 DQ7 F2-OE# H
JRFU F1-OE# DQ9 DQ11 DQ4 DQ6 DQ15 VCCQ J
KF1-CE# RFU RFU RFU RFU VCC VCCQ RFU K
LVSS VSS VCCQ VCC VSS VSS VSS VSS L
MDU DU Depop Depop Depop Depop DU DU M
12345678
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
20 Order Number: 314749-05
Table 6: TSOP and Easy BGA Signal Descriptions
Symbol Type Name and Function
A[MAX:1] Input
ADDRESS INPUTS: Device address inputs. 64-Mbit: A[22:1]; 128-Mbit: A[23:1]; 256-Mbit:
A[24:1]; 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 A25 high (VIH).
DQ[15:0] Input/
Output
DATA INPUT/OUTPUTS: Inputs data and commands during write cycles; outputs data during
memory, Status Register, Protection Register, and Read Configuration Register reads. Data balls float
when the CE# or OE# are deasserted. Data is internally latched during writes.
ADV# Input
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.
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.
CE# Input
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
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.
CLK Input
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 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.
OE# Input OUTPUT ENABLE: Active low input. OE# low enables the device’s output data buffers during read
cycles. OE# high places the data outputs and WAIT in High-Z.
RST# Input
RESET: Active low input. RST# resets internal automation and inhibits write operations. This
provides data protection during power transitions. RST# high enables normal operation. Exit from
reset places the device in asynchronous read array mode.
WAIT Output
WAIT: Indicates data valid in synchronous array or non-array burst reads. 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.
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.
WE# Input WRITE ENABLE: Active low input. WE# controls writes to the device. Address and data are latched
on the rising edge of WE#.
WP# Input
WRITE PROTECT: Active low input. WP# low enables the lock-down mechanism. Blocks in lock-
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.
VPP Power/
Input
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 drops
from the system supply, the VIH level of VPP can be as low as VPPL min. VPP must remain 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.
VCC Power Device Core Power Supply: Core (logic) source voltage. Writes to the flash array are inhibited
when 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.
RFU Reserved for Future Use: Reserved by Numonyx for future device functionality and enhancement.
These should be treated in the same way as a Don’t Use (DU) signal.
DU Don’t 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.
November 2007 Datasheet
Order Number: 314749-05 21
Numonyx™ StrataFlash® Embedded Memory (P33)
Table 7: QUAD+ SCSP Signal Descriptions
Symbol Type Name and Function
A[MAX:0] Input
ADDRESS INPUTS: Device address inputs. 64-Mbit: A[21:0]; 128-Mbit: A[22:0]; 256-Mbit:
A[23:0]; 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 A24 high (VIH).
DQ[15:0] Input/
Output
DATA INPUT/OUTPUTS: Inputs data and commands during write cycles; outputs data during
memory, Status Register, Protection Register, and Read Configuration Register reads. Data balls float
when the CE# or OE# are deasserted. Data is internally latched during writes.
ADV# Input
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.
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.
F1-CE# Input
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
deasserted, the associated flash die is deselected, power is reduced to standby levels, data and
WAIT outputs are placed in high-Z state. Note: F2-CE# is a NC for this part
WARNING: All chip enables must be high when device is not in use.
CLK Input
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 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.
F1-OE# Input OUTPUT ENABLE: Active low input. OE# low enables the device’s output data buffers during read
cycles. OE# high places the data outputs and WAIT in High-Z. Note: F2-OE# is a NC for this part.
RST# Input
RESET: Active low input. RST# resets internal automation and inhibits write operations. This
provides data protection during power transitions. RST# high enables normal operation. Exit from
reset places the device in asynchronous read array mode.
WAIT Output
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.
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.
WE# Input WRITE ENABLE: Active low input. WE# controls writes to the device. Address and data are latched
on the rising edge of WE#.
WP# Input
WRITE PROTECT: Active low input. WP# low enables the lock-down mechanism. Blocks in lock-
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.
VPP Power/
lnput
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 drops
from the system supply, the VIH level of VPP can be as low as VPPL min. VPP must remain 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.
VCC Power Device Core Power Supply: Core (logic) source voltage. Writes to the flash array are inhibited
when 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.
RFU Reserved for Future Use: Reserved by Numonyx for future device functionality and enhancement.
These should be treated in the same way as a Dont Use (DU) signal.
DU Don’t 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.
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
22 Order Number: 314749-05
4.3 Dual Die SCSP Configurations
Note: Amax=Vih selectes the Top Parameter Die; Amax=Vil selects the Bottom Parameter Die.
4.4 Memory Maps
Ta b l e 8 through Ta b l e 1 0 show the Numonyx StrataFlash® Embedded Memory (P33)
maps. The memory array is divided into multiple 8-Mbit Programming Regions (see
Section 11.3, “Programming Operations” on page 57).
Figure 10: 512-Mbit Easy BGA / TSOP Top or Bottom Parameter Block Diagram
Figure 11: 512-Mbit QUAD+ SCSP Top or Bottom Parameter Block Diagram
Top Param Die
(256-Mbit)
Bottom Param Die
(256-Mbit)
WP#
CLK
CE#
ADV#
OE #
WAIT
WE#
RST#
VCC
VPP
DQ[15:0]
A[MAX:1]
VCCQ
VSS
Easy BGA/TSOP 512-Mbit (2-Die) Top or Bottom Parameter Configuration
Top Param Die
(256-Mbit)
Bottom Param Die
(256-Mbit)
WP#
CLK
F1-CE#
ADV#
OE#
WAIT
WE#
RST#
VCC
VPP
DQ[15:0]
A[MAX:0]
VCCQ
VSS
QUAD+ 512-Mbit (2-Die) Top or Bottom Parameter Configuration
November 2007 Datasheet
Order Number: 314749-05 23
Numonyx™ StrataFlash® Embedded Memory (P33)
Table 8: Discrete Top Parameter Memory Maps (all packages)
Size
(KB) Blk 64-Mbit Size
(KB) Blk 128-Mbit
One
Programming
Region
32 66 3FC000 - 3FFFFF
One
Programming
Region
32 130 7FC000 - 7FFFFF
...
...
...
...
...
...
32 63 3F0000 - 3F3FFF 32 127 7F0000 - 7F3FFF
128 62 3E0000 - 3EFFFF 128 126 7E0000 - 7EFFFF
...
...
...
...
...
...
128 56 380000 - 38FFFF 128 120 780000 - 78FFFF
Seven
Programming
Regions
128 55 370000 - 37FFFF
Fifteen
Programming
Regions
128 119 770000 - 77FFFF
128 54 360000 - 36FFFF 128 118 760000 - 76FFFF
...
...
...
...
...
...
128 1 010000 - 01FFFF 128 1 010000 - 01FFFF
128 0 000000 - 00FFFF 128 0 000000 - 00FFFF
Size
(KB) Blk 256-Mbit
One
Programming
Region
32 258 FFC000 - FFFFFF
...
...
...
32 255 FF0000 - FF3FFF
128 254 FE0000 - FEFFFF
...
...
...
128 248 F80000 - F8FFFF
Thirty-One
Programming
Regions
128 247 F70000 - F7FFFF
128 246 F60000 - F6FFFF
...
...
...
128 1 010000 - 01FFFF
128 0 000000 - 00FFFF
Table 9: Discrete Bottom Parameter Memory Maps (all packages)
Size
(KB) Blk 64-Mbit Size
(KB) Blk 128-Mbit
Seven
Programming
Regions
128 66 3F0000 - 3FFFFF
Fifteen
Programming
Regions
128 130 7F0000 - 7FFFFF
128 65 3E0000 - 3EFFFF 128 129 7E0000 - 7EFFFF
...
...
...
...
...
...
128 12 090000 - 09FFFF 128 12 090000 - 09FFFF
128 11 080000 - 08FFFF 128 11 080000 - 08FFFF
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
24 Order Number: 314749-05
Note: The Dual-Die memory map are the same for both parameter options.
One
Programming
Region
128 10 070000 - 07FFFF
One
Programming
Region
128 10 070000 - 07FFFF
...
...
...
...
...
...
128 4 010000 - 01FFFF 128 4 010000 - 01FFFF
32 3 00C000 - 00FFFF 32 3 00C000 - 00FFFF
...
...
...
...
...
...
32 0 000000 - 003FFF 32 0 000000 - 003FFF
Size
(KB) Blk 256-Mbit
Thirty-One
Programming
Regions
128 258 FF0000 - FFFFFF
128 257 FE0000 - FEFFFF
...
...
...
128 12 090000 - 09FFFF
128 11 080000 - 08FFFF
One
Programming
Region
128 10 070000 - 07FFFF
...
...
...
128 4 010000 - 01FFFF
32 3 00C000 - 00FFFF
...
...
...
32 0 000000 - 003FFF
Block size is referenced in K-Bytes where a byte=8 bits. Block Address range is referenced in K-
Words where a Word is the size of the flash output bus (16 bits).
Table 10: 512-Mbit Top and Bottom Parameter Memory Map (Easy BGA, TSOP, and QUAD+
SCSP) (Sheet 1 of 2)
512-Mbit Flash (2x256-Mbit w/ 1CE)
Die Stack Config Size
(KB) Blk Address Range
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
...
...
...
Table 9: Discrete Bottom Parameter Memory Maps (all packages)
Size
(KB) Blk 64-Mbit Size
(KB) Blk 128-Mbit
November 2007 Datasheet
Order Number: 314749-05 25
Numonyx™ StrataFlash® Embedded Memory (P33)
256-Mbit 128 4 010000 - 01FFFF
Bottom Parameter Die 32 3 00C000 - 00FFFF
...
...
...
32 0 000000 - 003FFF
Note: Refer to the appropriate 256-Mbit Memory Map (Ta b l e 8 or Ta b le 9 ) for Programming Region information. Block size
is referenced in K-Bytes where a byte=8 bits. Block Address range is referenced in K-Words where a Word is the size of
the flash output bus (16 bits).
Table 10: 512-Mbit Top and Bottom Parameter Memory Map (Easy BGA, TSOP, and QUAD+
SCSP) (Sheet 2 of 2)
512-Mbit Flash (2x256-Mbit w/ 1CE)
Die Stack Config Size
(KB) Blk Address Range
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
26 Order Number: 314749-05
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.
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 11: Absolute Maximum Ratings
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 and VCCQ) 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 +4.1 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 2.3 V – 3.6 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.
Table 12: Operating Conditions
Symbol Parameter Min Max Units Notes
TCOperating Temperature –40 +85 °C 1
VCC VCC Supply Voltage 2.3 3.6
V
-
VCCQ I/O Supply Voltage
CMOS inputs 2.3 3.6
3
TTL inputs 2.4 3.6
VPPL VPP Voltage Supply (Logic Level) 1.5 3.6
2
VPPH Factory Word Programming VPP 8.5 9.5
tPPH Maximum VPP Hours VPP = VPPH -80Hours
Block
Erase
Cycles
Main and Parameter Blocks VPP = VPPL 100,000 -
CyclesMain Blocks VPP = VPPH - 1000
Parameter Blocks VPP = VPPH - 2500
Notes:
1. TC = Case Temperature.
2. In typical operation VPP program voltage is VPPL.
3. 40Mhz burst operation on the TSOP package has a max Vccq value of 3.5V. Please refer to the latest Specification Update
regarding synchronous burst operation with the TSOP package.
November 2007 Datasheet
Order Number: 314749-05 27
Numonyx™ StrataFlash® Embedded Memory (P33)
6.0 Electrical Specifications
6.1 DC Current Characteristics
Table 13: DC Current Characteristics (Sheet 1 of 2)
Sym Parameter
CMOS
Inputs
(VCCQ =
2.3 V - 3.6
V)
TTL Inputs
(VCCQ =
2.4 V - 3.6
V) Unit Test Conditions Notes
Typ Max Typ Max
ILI Input Load Current - ±1 - ±2 µA
VCC = VCCMax
VCCQ = VCCQMax
VIN = VCCQ or VSS 1
ILO
Output
Leakage
Current
DQ[15:0], WAIT 1-±10µA
VCC = VCCMax
VCCQ = VCCQMax
VIN = VCCQ or VSS
ICCS,
ICCD
VCC Standby,
Power Down
64-Mbit 35 135 35 200
µA
VCC = VCCMax
VCCQ = VCCQMax
CE# = VCCQ
RST# = VCCQ (for ICCS)
RST# = VSS (for ICCD)
WP# = VIH
1,2
128-Mbit 45 155 45 220
256-Mbit 70 195 70 350
512-Mbit 140 390 140 700
-
ICCR
Average
VCC
Read
Current
Asynchronous Single-
Word f = 5 MHz (1 CLK) 14 16 14 16 mA 1-Word Read
VCC = VCCMax
CE# = VIL
OE# = VIH
Inputs: VIL or
VIH
1
Page-Mode Read
f = 13 MHz (5 CLK) 10 11 10 12 mA 4-Word Read
Synchronous Burst
f = 40MHz
13 17 n/a n/a mA 4-Word
15 19 n/a n/a mA 8-Word
17 21 n/a n/a mA 16-Word
21 26 n/a n/a mA Continuous
Synchronous Burst
f = 52MHz
16 19 n/a n/a mA 4-Word
19 23 n/a n/a mA 8-Word
22 26 n/a n/a mA 16-Word
23 28 n/a n/a mA Continuous
ICCW,
ICCE
VCC Program Current,
VCC Erase Current
36 51 36 51
mA
VPP = VPPL, Pgm/Ers in progress 1,3,5
26 33 26 33 VPP = VPPH, Pgm/Ers in progress 1,3,5
ICCWS,
ICCES
VCC Program Suspend
Current,
VCC Erase
Suspend Current
64-Mbit 35 135 35 200
µA CE# = VCCQ; suspend in
progress 1,3,4
128-Mbit 45 155 45 220
256-Mbit 70 195 70 350
512-Mbit 140 390 140 700
-
IPPS,
IPPWS,
IPPES
VPP Standby Current,
VPP Program Suspend Current,
VPP Erase Suspend Current
0.2 5 0.2 5 µA VPP = VPPL, suspend in progress 1,3
IPPR VPP Read 2 15 2 15 µA VPP = VPPL 1,3
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
28 Order Number: 314749-05
6.2 DC Voltage Characteristics
IPPW VPP Program Current
0.05 0.10 0.05 0.10
mA
VPP = VPPL, program in progress
-
822822 V
PP = VPPH, program in progress
IPPE VPP Erase Current
0.05 0.10 0.05 0.10
mA
VPP = VPPL, erase in progress
-
822822 V
PP = 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 39.
Table 14: DC Voltage Characteristics
Sym Parameter
CMOS Inputs
(VCCQ = 2.3 V – 3.6 V)
TTL Inputs (1)
(VCCQ = 2.4 V – 3.6 V) Unit Test Condition Notes
Min Max Min Max
VIL Input Low Voltage0 0.400.6V 2
VIH Input High Voltage VCCQ – 0.4 V VCCQ 2.0 VCCQ V
VOL Output Low Voltage - 0.1 - 0.1 V
VCC = VCCMin
VCCQ = VCCQMin
IOL = 100 µA
-
VOH Output High Voltage VCCQ – 0.1 - VCCQ – 0.1 - V
VCC = VCCMin
VCCQ = VCCQMin
IOH = –100 µA
-
VPPLK VPP Lock-Out Voltage - 0.4 - 0.4 V 3
VLKO VCC Lock Voltage 1.5 - 1.5 - 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.
Table 13: DC Current Characteristics (Sheet 2 of 2)
Sym Parameter
CMOS
Inputs
(VCCQ =
2.3 V - 3.6
V)
TTL Inputs
(VCCQ =
2.4 V - 3.6
V) Unit Test Conditions Notes
Typ Max Typ Max
November 2007 Datasheet
Order Number: 314749-05 29
Numonyx™ StrataFlash® Embedded Memory (P33)
7.0 AC Characteristics
7.1 AC Test Conditions
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.
Notes:
1. See the following table for component values.
2. Test configuration component value for worst case speed conditions.
3. CL includes jig capacitance
.
Figure 12: AC Input/Output Reference Waveform
Figure 13: Transient Equivalent Testing Load Circuit
Table 15: Test Configuration Component Value for Worst Case Speed Conditions
Test Configuration CL (pF)
VCCQMin Standard Test 30
Figure 14: Clock Input AC Waveform
IO_REF.WMF
Input V
CCQ
/2 V
CCQ
/2 Output
V
CCQ
0V
Test Points
Device
Under Test Out
CL
CLK [C]
V
IH
V
IL
R203R202
R201
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
30 Order Number: 314749-05
7.2 Capacitance
7.3 AC Read Specifications
Table 16: Capacitance
Symbol Parameter Signals Min Typ Max Unit Condition Note
CIN Input Capacitance
Address, Data,
CE#, WE#, OE#,
RST#, CLK,
ADV#, WP#
26 7 pF
Typ temp = 25 °C,
Max temp = 85 °C,
VCC = (0 V - 3.6 V),
VCCQ = (0 V - 3.6 V),
Discrete silicon die
1,2,3
COUT Output Capacitance Data, WAIT 2 4 5 pF
Notes:
1. Capacitance values are for a single die; for dual die, the capacitance values are doubled.
2. Sampled, not 100% tested.
3. Silicon die capacitance only, add 1 pF for discrete packages.
Table 17: AC Read Specifications - 130nm (Sheet 1 of 3)
Num Symbol Parameter Min Max Unit Notes
Asynchronous Specifications
R1 tAVAV Read cycle time
85 -ns-
256/512M
TSOP 95 ns -
R2 tAVQV Address to output valid
-85 ns -
256/512M
TSOP 95 ns -
R3 tELQV CE# low to output valid
-85 ns -
256/512M
TSOP 95 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
1,3
R9 tGHQZ OE# high to output in high-Z - 24 ns
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
Latching Specifications
November 2007 Datasheet
Order Number: 314749-05 31
Numonyx™ StrataFlash® Embedded Memory (P33)
R101 tAVVH Address setup to ADV# high 10 - ns
1
R102 tELVH CE# low to ADV# high 10 - ns
R103 tVLQV ADV# low to output valid
-85 ns
256M/512N
TSOP 95 ns
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
-52MHz
1,3,5,
and 6
TSOP Package - 40 Mhz
R201 tCLK CLK period
19.2 - ns
TSOP Package 25 - ns
R202 tCH/CL CLK high/low time 5 - ns
R203 tFCLK/RCLK CLK fall/rise time - 3 ns
Table 17: AC Read Specifications - 130nm (Sheet 2 of 3)
Num Symbol Parameter Min Max Unit Notes
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
32 Order Number: 314749-05
Synchronous Specifications(5,6)
R301 tAVCH/L Address setup to CLK 9 - ns
1
R302 tVLCH/L ADV# low setup to CLK 9 - ns
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 12, “AC Input/Output Reference Waveform” on page 29 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.
3. Sampled, not 100% tested.
4. Address hold in synchronous burst read mode is tCHAX or tVHAX, whichever timing specification is satisfied first.
5. Please see the latest P33 Spec Update for synchronous busrt operation on TSOP packages.
6. Synchronous burst read mode is not supported with TTL level inputs.
7. Applies only to subsequent synchronous reads.
Table 17: AC Read Specifications - 130nm (Sheet 3 of 3)
Num Symbol Parameter Min Max Unit Notes
Table 18: AC Read Specification differences for 65nm
Num Symbol Parameter Min Max Unit Notes
Asynchronous Specifications
R1 tAVAV Read cycle time 95 -ns2
TSOP 105 ns 2
R2 tAVQV Address to output valid
-95 ns 2
TSOP 105 ns 2
R3 tELQV CE# low to output valid
-95 ns 2
TSOP 105 ns 2
R103 tVLQV
ADV# low to output valid
-95 ns 1,2
TSOP 105 ns 2
Notes:
1. See Figure 12, “AC Input/Output Reference Waveform” on page 29 for timing measurements and
max allowable input slew rate.
2. This is the recommended specification for all new designs supporting both 130nm and 65nm lithos, or for new designs
that will use the 65nm lithography. All other timings not listed here remain the same as referenced by Ta ble 1 7,
AC Read Specifications - 130nm.
November 2007 Datasheet
Order Number: 314749-05 33
Numonyx™ StrataFlash® Embedded Memory (P33)
Note: WAIT shown deasserted during asynchronous read mode (RCR 10=0, WAIT asserted low).
Note: WAIT shown deasserted during asynchronous read mode (RCR 10=0, WAIT asserted low).
Figure 15: Asynchronous Single-Word Read (ADV# Low)
Figure 16: Asynchronous Single-Word Read (ADV# Latch)
R5
R7
R6
R17R15
R9R4
R8R3
R1
R2
R1
A
ddress [A]
ADV#
CE# [E}
OE# [G]
WAIT [T]
Data [D/Q]
RST # [P]
R10
R7
R6
R17R15
R9R4
R8R3
R106
R101
R105R105
R2
R1
A
ddress [A]
A[1:0][A]
ADV#
CE# [E}
OE# [G]
WAIT [T]
Data [D/Q]
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
34 Order Number: 314749-05
Note: WAIT shown deasserted during asynchronous read mode (RCR 10=0, WAIT asserted low).
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 17: Asynchronous Page-Mode Read Timing
Figure 18: Synchronous Single-Word Array or Non-array Read Timing
R108 R9R7
R17R15
R10R4
R8R3
R106
R101
R105R105
R1R1
R2
A
[Max:2] [A]
A[1:0]
ADV#
CE# [E]
OE# [G]
WAIT [T]
DATA [D/Q]
R31 2
R305R304
R4
R17R30 7R15
R9R7
R8
R303
R10 2
R3
R104
R106R10 1
R104
R105R105
R2
R306R301
CLK [C]
A
d dre ss [A]
ADV# [V]
CE# [E]
OE# [G]
WAIT [T]
Data [D/Q]
November 2007 Datasheet
Order Number: 314749-05 35
Numonyx™ StrataFlash® Embedded Memory (P33)
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. See Section 11.1.0.12, “End of Word Line (EOWL) Considerations” on
page 55 for more information
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).
Figure 19: Continuous Burst Read, showing an Output Delay Timing
Figure 20: Synchronous Burst-Mode Four-Word Read Timing
R305R305R305R305
R304
R4
R7
R312R307R15
R303
R102
R3
R106
R105R105
R101
R2
R304R304R304R306
R302
R301
CLK [C]
A
ddress [A]
ADV# [V]
CE# [E]
OE# [G]
WAIT [T ]
Data [D/Q]
y
A
Q0 Q1 Q2 Q3
R307
R10
R304
R305R304
R4
R7
R17R15
R9
R8
R303
R3
R106
R102
R105R105
R101
R2
R306
R302
R301
CLK [C]
A
ddress [A]
ADV# [V]
CE# [E]
OE# [G]
WAIT [T]
Data [D/Q]
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
36 Order Number: 314749-05
7.4 AC Write Specifications
Table 19: AC Write Specifications
Num Symbol Parameter Min Max Unit 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
1,2
W5 tAVWH Address setup to WE# high 50 - ns
W6 tWHEH CE# hold from WE# high 0 - ns
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 V
PP 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#.
3. Sampled, not 100% tested.
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 operations 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.
November 2007 Datasheet
Order Number: 314749-05 37
Numonyx™ StrataFlash® Embedded Memory (P33)
Note: WAIT deasserted during asynchronous read and during write. WAIT High-Z during write per OE# deasserted.
Figure 21: Write-to-Write Timing
Figure 22: Asynchronous Read-to-Write Timing
W1
W7W4W7W4
W3W9 W3W9W3W3
W6W2W6W2
W8W8 W5W5
ddress [A]
CE# [E}
WE# [W]
OE# [G]
Data [D/Q]
RST# [P]
Q D
R5
W7
W4R10
R7
R6
R17R15
W6W3W3W2
R9R4
R8R3
W8W5
R1
R2
R1
A
ddress [A]
CE# [E}
OE# [G]
WE# [W]
WAIT [T ]
Data [D/Q]
RST# [P]
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
38 Order Number: 314749-05
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 23: Write-to-Asynchronous Read Timing
Figure 24: Synchronous Read-to-Write Timing
D Q
W1
R9
R8
R4
R3
R2
W7W4
R17R15
W1 4
W18W3W3
R10W6W2
R1R1W8W5
A
d d re ss [A ]
ADV# [V]
CE# [E}
WE# [W]
OE# [G]
WAIT [T]
Data [D/Q]
RST# [P]
Latency Count
Q D D
W7R305
R304
R7
R312R307R16
W15
W22
W21
W9
W8
W9W3
W22
W21
W3W2
R8
R4
W6
R11
R13
R11
R303
R3
R104R104
R106
R102
R105R105
W18
W5
R101
R2
R306
R302
R301
CLK [C]
A
ddress [ A]
ADV# [V]
CE# [E]
OE# [G]
WE#
WAIT [T]
Data [D/Q]
November 2007 Datasheet
Order Number: 314749-05 39
Numonyx™ StrataFlash® Embedded Memory (P33)
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
Figure 25: Write-to-Synchronous Read Timing
Table 20: Program and Erase Specifications
Num Symbol Parameter
VPPL VPPH
Unit Note
s
Min Typ Max Min Typ Max
Conventional Word Programming
W200 tPROG/W Program
Time
Single word - 130nm - 90 200 - 85 190
µs 1Single word - 65nm - 125 150 - 125 150
Single cell - 30 60 - 30 60
Buffered Programming
W200 tPROG/W Program
Time
Single word - 90 200 - 85 190
µs 1
W251 tBUFF 32-word buffer - 440 880 - 340 680
Buffered Enhanced Factory Programming
W451 tBEFP/W Program
Single word n/a n/a n/a - 10 -
µs
1,2
W452 tBEFP/Setup BEFP Setup n/a n/a n/a 5 - - 1
Erase and Suspend
D Q Q
W1
R304
R305R304
R3
W7
W4
R307R15
R4
W20
W19
W18
W3W3
R11
R303
R11
W6
W2
R104
R106
R104
R306W8W5
R302
R301
R2
CLK
A
ddress [A]
ADV#
CE# [E}
WE# [W]
OE# [G]
WAIT [T]
Data [D/Q]
RST# [P]
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
40 Order Number: 314749-05
W500 tERS/PB Erase Time
32-KByte Parameter - 0.4 2.5 - 0.4 2.5
s
1
W501 tERS/MB 128-KByte Main - 0.85 4.0 - 0.85 4.0
W600 tSUSP/P
Suspend
Latency
Program suspend - 20 25 - 20 25
µsW601 tSUSP/E Erase suspend - 20 25 - 20 25
W602 tERS/SUSP Erase to Suspend - 500 - - 500 - 1,3
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.
3. W602 is the typical time between an initial block erase or erase resume command and the a subsequent erase suspend
command. Violating the specification repeatedly during any particular block erase may cause erase failures.
Table 20: Program and Erase Specifications
Num Symbol Parameter
VPPL VPPH
Unit Note
s
Min Typ Max Min Typ Max
November 2007 Datasheet
Order Number: 314749-05 41
Numonyx™ StrataFlash® Embedded Memory (P33)
8.0 Power and Reset Specifications
8.1 Power-Up and Power-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.
Table 21: Power and Reset
Num Symbol Parameter Min Max Unit Notes
P1 tPLPH RST# pulse width low 100 - ns 1,2,3,4
P2 tPLRH
RST# low to device reset during erase - 25
µs
1,3,4,7
RST# low to device reset during program - 25 1,3,4,7
P3 tVCCPH
VCC Power valid to RST# de-assertion (high)
130nm 90 -
1,4,5,6
VCC Power valid to RST# de-assertion (high)
65nm 300 -
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.
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
42 Order Number: 314749-05
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 Numonyx 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.
Figure 26: Reset Operation Waveforms
(
A) Reset during
read mode
(B) Reset during
program or block erase
P1
P2
(C) Reset during
program or block erase
P1
P2
V
IH
V
IL
V
IH
V
IL
V
IH
V
IL
RST# [P]
RST# [P]
RST# [P]
Abort
Complete
Abort
Complete
V
CC
0V
V
CC
(D) VCC Power-up to
RST# high
P1 R5
P2
P3
P2 R5
R5
November 2007 Datasheet
Order Number: 314749-05 43
Numonyx™ StrataFlash® Embedded Memory (P33)
9.0 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 Numonyx™ StrataFlash® Embedded Memory (P33) device
conform to standard microprocessor bus operations. Ta b l e 2 2 summarizes the bus
operations and the logic levels that must be applied to the device control signal inputs.
9.1 Read
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.
9.2 Write
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 23, “Command Bus Cycles” on page 45
shows the bus cycle sequence for each of the supported device commands, while
Table 24, “Command Codes and Definitions” on page 46 describes each command. See
Section 7.0, “AC Characteristics on page 29 for signal-timing details.
Note: Write operations with invalid VCC and/or VPP voltages can produce spurious results and
should not be attempted.
9.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.
Table 22: Bus Operations Summary
Bus Operation RST# CLK ADV# CE# OE# WE# WAIT DQ[15:0] Notes
Read
Asynchronous VIH XL L L H
Deasserted Output
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 23, “Command Bus Cycles” on page 45 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.
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
44 Order Number: 314749-05
9.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.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
Numonyx 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 mode,
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 29 for details
about signal-timing.
9.6 Device Command Bus Cycles
Device operations are initiated by writing specific device commands to the CUI. See
Table 23, “Command Bus Cycles” on page 45. 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.
November 2007 Datasheet
Order Number: 314749-05 45
Numonyx™ StrataFlash® Embedded Memory (P33)
Table 23: Command Bus Cycles
Mode Command Bus
Cycles
First Bus Cycle Second Bus Cycle
Oper Addr(1) Data(2) Oper Addr(1) Data(2)
Read
Read Array 1 Write DnA 0xFF - - -
Read Device Identifier 2 Write DnA 0x90 Read DBA + IA ID
CFI Query 2 Write DnA 0x98 Read DBA + QA QD
Read Status Register 2 Write DnA 0x70 Read DnA SRD
Clear Status Register 1 Write DnA 0x50 - - -
Program
Word Program 2 Write WA 0x40/
0x10 Write WA WD
Buffered Program(3) > 2WriteWA0xE8Write WA N - 1
Buffered Enhanced Factory
Program (BEFP)(4) > 2 Write WA 0x80 Write WA 0xD0
Erase Block Erase 2 Write BA 0x20 Write BA 0xD0
Suspend
Program/Erase Suspend 1 Write DnA 0xB0 - - -
Program/Erase Resume 1 Write DnA 0xD0 - - -
Block
Locking/
Unlocking
Lock Block 2 Write BA 0x60 Write BA 0x01
Unlock Block 2 Write BA 0x60 Write BA 0xD0
Lock-down Block 2 Write BA 0x60 Write BA 0x2F
Protection
Program Protection Register 2 Write PRA 0xC0 Write PRA PD
Program Lock Register 2 Write LRA 0xC0 Write LRA LRD
Configuration Program Read Configuration
Register 2 Write RCD 0x60 Write RCD 0x03
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 512Mbit device)
DnA = Address within the 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 QUAD+ A[15:0] or EASY BGA / TSOP A[16:1].
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.
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
46 Order Number: 314749-05
10.0 Command Definitions
Ta b l e 2 4 shows valid device command codes and descriptions.
Table 24: Command Codes and Definitions (Sheet 1 of 2)
Mode Code Device Mode Description
Read
0xFF Read Array Places the device in Read Array mode. Array data is output on DQ[15:0].
0x70 Read Status
Register
Places the device in Read Status Register mode. The device enters this mode
after a program or erase command is issued. SR data is output on DQ[7:0].
0x90
Read Device ID
or Configuration
Register
Places device in Read Device Identifier mode. Subsequent reads output
manufacturer/device codes, Configuration Register data, Block Lock status,
or Protection Register data on DQ[15:0].
0x98 Read Query Places the device in Read Query mode. Subsequent reads output Common
Flash Interface information on DQ[7:0].
0x50 Clear Status
Register
The WSM can only set SR error bits. The Clear Status Register command is
used to clear the SR error bits.
Write 0x40 Word Program
Setup
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
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 SR Data for synchronous Non-array reads. The Read Array
command must be issued to read array data after programming has finished.
Write
0x10 Alternate Word
Program Setup Equivalent to the Word Program Setup command, 0x40.
0xE8 Buffered Program This command loads a variable number of words up to the buffer size of 32
words onto the program buffer.
0xD0 Buffered Program
Confirm
The confirm command is Issued after the data streaming for writing into the
buffer is done. This instructs the WSM to perform the Buffered Program
algorithm, writing the data from the buffer to the flash memory array.
0x80 BEFP Setup
First cycle of a 2-cycle command; initiates the BEFP mode. The CUI then
waits for the BEFP Confirm command, 0xD0, that initiates the BEFP
algorithm. All other commands are ignored when BEFP mode begins.
0xD0 BEFP Confirm If the previous command was BEFP Setup (0x80), the CUI latches the
address and data, and prepares the device for BEFP mode.
Erase
0x20 Block Erase Setup
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
the Erase Confirm command. If the next command is not the Erase Confirm
(0xD0) command, the CUI sets Status Register bits SR [5,4], and places the
device in Read Status Register mode.
0xD0 Block Erase Confirm
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
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
SR Data for synchronous Non-array reads.
Suspend
0xB0 Program or Erase
Suspend
This command issued to any device address initiates a suspend of the
currently-executing program or block erase operation. The Status Register
indicates successful suspend operation by setting either SR 2 (program
suspended) or SR 6 (erase suspended), along with SR 7 (ready). The WSM
remains in the suspend mode regardless of control signal states (except for
RST# asserted).
0xD0 Suspend Resume This command issued to any device address resumes the suspended program
or block-erase operation.
November 2007 Datasheet
Order Number: 314749-05 47
Numonyx™ StrataFlash® Embedded Memory (P33)
Block Locking/
Unlocking
0x60 Lock Block Setup
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), or Block Lock-Down (0x2F), the CUI sets SR [5,4], indicating
a command sequence error.
0x01 Lock Block If the previous command was Block Lock Setup (0x60), the addressed block
is locked.
0xD0 Unlock Block
If the previous command was Block Lock Setup (0x60), the addressed block
is unlocked. If the addressed block is in a lock-down state, the operation has
no effect.
0x2F Lock-Down Block If the previous command was Block Lock Setup (0x60), the addressed block
is locked down.
Protection 0xC0 Program Protection
Register Setup
First cycle of a 2-cycle command; prepares the device for a Protection
Register or Lock Register program operation. The second cycle latches the
register address and data, and starts the programming algorithm.
Configuration
0x60 Read Configuration
Register Setup
First cycle of a 2-cycle command; prepares the CUI for device read
configuration. If the Set Read Configuration Register command (0x03) is not
the next command, the CUI sets Status Register bits SR[5,4], indicating a
command sequence error.
0x03 Read Configuration
Register
If the previous command was Read Configuration Register Setup (0x60), the
CUI latches the address and writes A[15:0] (QUAD+) or A[16:1] (EASY BGA/
TSOP) to the Read Configuration Register. Following a Configure RCR
command, subsequent read operations access array data.
Table 24: Command Codes and Definitions (Sheet 2 of 2)
Mode Code Device Mode Description
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
48 Order Number: 314749-05
11.0 Device Operations
This section provides an overview of device operations. The system Central Processing
Unit provides control of all in-system read, write, and erase operations of the device via
the system bus. The on-chip WSM manages all block-erase and word-program
algorithms.
Device commands are written to the 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.
11.1 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. SRD 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. the Read Array command).
The Status Register is read using single asynchronous-mode or synchronous burst
mode reads. SRD 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, when reading the Status Register in
synchronous burst mode, CE# or ADV# must be toggled to update SRD.
The Device Write Status bit (SR[7]) provides overall status of the device. SR[6:1]
present status and error information about the program, erase, suspend, VPP
, and
block-locked operations.
Table 25: Status Register Description (Sheet 1 of 2)
Status Register (SR) Default Value = 0x80
Device Write
Status
Erase
Suspend
Status
Erase Status Program
Status VPP Status
Program
Suspend
Status
Block-Locked
Status
BEFP
Write
Status
DWS ESS ES PS VPPS PSS BLS BWS
76543210
Bit Name Description
7 Device Write Status (DWS) 0 = Device is busy; program or erase cycle in progress; SR[0] valid.
1 = Device is ready; SR[6:1] are valid.
6 Erase Suspend Status (ESS) 0 = Erase suspend not in effect.
1 = Erase suspend in effect.
5 Erase Status (ES) 0 = Erase successful.
1 = Erase fail or program sequence error when set with SR[4,7].
4 Program Status (PS) 0 = Program successful.
1 = Program fail or program sequence error when set with SR[5,7]
3V
PP Status (VPPS) 0 = VPP within acceptable limits during program or erase operation.
1 = VPP < VPPLK during program or erase operation.
November 2007 Datasheet
Order Number: 314749-05 49
Numonyx™ StrataFlash® Embedded Memory (P33)
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.
11.1.0.1 Clear Status Register
The Clear Status Register command clears the status register. It functions independent
of VPP
. The 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.Read Configuration
Register
The 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.6, “Device Command
Bus Cycles” on page 44).
RCR contents can be examined using the Read Device Identifier command, and then
reading from offset 0x05 (see Section 11.2.3, “Read Device Identifier” on page 56).
The RCR is shown in Ta ble 2 6 . The following sections describe each RCR bit.
2 Program Suspend Status (PSS) 0 = Program suspend not in effect.
1 = Program suspend in effect.
1Block-Locked Status (BLS) 0 = Block not locked during program or erase.
1 = Block locked during program or erase; operation aborted.
0BEFP Write Status (BWS)
After Buffered Enhanced Factory Programming (BEFP) data is loaded into the
buffer:
0 = BEFP complete.
1 = BEFP in-progress.
Table 25: Status Register Description (Sheet 2 of 2)
Status Register (SR) Default Value = 0x80
Table 26: Read Configuration Register Description (Sheet 1 of 2)
Read Configuration Register (RCR)
Read
Mode RES Latency Count WAIT
Polarity
Data
Hold
WAIT
Delay
Burst
Seq
CLK
Edge RES RES Burst
Wrap Burst Length
RM RLC[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)
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
50 Order Number: 314749-05
11.1.0.2 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.
11.1.0.3 Latency Count
The Latency Count (LC) bits 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 valid data word is driven onto DQ[15:0]. The input clock frequency is used to
determine this value and Figure 27 shows the data output latency for the different
settings of LC. The maximum Latency Count for P33 would be Code 4 based on the Max
clock frequency specification of 52 Mhz, and there will be zero WAIT States when
bursting within the word line. Please also refer to Section 11.1.0.12, “End of Word Line
(EOWL) Considerations” on page 55 for more information on EOWL.
Refer to Table 27, “LC and Frequency Support” on page 51 for Latency Code Settings.
10 Wait Polarity (WP) 0 =WAIT signal is active low
1 =WAIT signal is active high (default)
9Data 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)
7Burst Sequence (BS) 0 =Reserved
1 =Linear (default)
6Clock Edge (CE) 0 = Falling edge
1 = Rising edge (default)
5:4 Reserved (R) Reserved bits should be cleared (0)
3Burst 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.
Table 26, “Read Configuration Register Description” is shown using the QUAD+ package. For EASY BGA
and TSOP packages, the table reference should be adjusted using address bits A[16:1].
Table 26: Read Configuration Register Description (Sheet 2 of 2)
November 2007 Datasheet
Order Number: 314749-05 51
Numonyx™ StrataFlash® Embedded Memory (P33)
Figure 27: First-Access Latency Count
Table 27: LC and Frequency Support
Latency Count Settings Frequency Support (MHz)
2 27
3 40
4 52
Note: Please refer to the latest specification update for synchronous burst read capability on the TSOP package.
Code 1
(Reserved
Code 6
Code 5
Code 4
Code 3
Code 2
Code 0 (Reserved)
Code 7
Valid
Address
Valid
Output
Valid
Output
Valid
Output
Valid
Output
Valid
Out put
Valid
Output
Valid
Output
Valid
Output
Valid
Output
Valid
Output
Valid
Output
Valid
Out put
Valid
Output
Valid
Output
Valid
Output
Valid
Output
Valid
Output
Valid
Out put
Valid
Output
Valid
Output
Valid
Output
Valid
Output
Valid
Out put
Valid
Output
Valid
Output
Valid
Output
Valid
Out put
Valid
Output
Valid
Output
Valid
Output
Valid
Output
Valid
Output
Valid
Output
Valid
Output
Valid
Output
Valid
Output
Address [A]
ADV# [V]
DQ15-0 [D/Q]
CLK [ C]
DQ15-0 [D/Q]
DQ15-0 [D/Q]
DQ15-0 [D/Q]
DQ15-0 [D/Q]
DQ15-0 [D/Q]
DQ15-0 [D/Q]
DQ15-0 [D/Q]
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
52 Order Number: 314749-05
11.1.0.4 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).
11.1.0.5 WAIT Signal Function
The WAIT signal indicates data valid when the device is operating in synchronous mode
(RCR 15=0). The WAIT signal is onlydeasserted” 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 16, “Asynchronous Single-Word Read (ADV# Latch)” on
page 33, and Figure 17, “Asynchronous Page-Mode Read Timing” on page 34.
Figure 28: Example Latency Count Setting Using Code 3
CLK
CE#
ADV#
A[MAX:0]
D[15:0]
tData
Code 3
Address
Data
012
34
R103
High-Z
Table 28: WAIT Functionality Table (Sheet 1 of 2)
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
November 2007 Datasheet
Order Number: 314749-05 53
Numonyx™ StrataFlash® Embedded Memory (P33)
11.1.0.6 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 29). 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 DH 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.
11.1.0.7 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.
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.
Table 28: WAIT Functionality Table (Sheet 2 of 2)
Condition WAIT Notes
Figure 29: Data Hold Timing
Valid
Output
Valid
Output
Valid
Output
Valid
Output
Valid
Output
CLK [C]
D[15:0] [Q]
D[15:0] [Q]
2 CLK
Data Hold
1 CLK
Data Hold
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
54 Order Number: 314749-05
11.1.0.8 Burst Sequence
The Burst Sequence (BS) bit selects linear-burst sequence (default). Only linear-burst
sequence is supported. Ta b l e 2 9 shows the synchronous burst sequence for all burst
lengths, as well as the effect of the Burst Wrap (BW) setting.
11.1.0.9 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.
11.1.0.10 Burst Wrap
The Burst Wrap (BW) bit determines whether 4, 8, 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.
Table 29: Burst Sequence Word Ordering
Start
Addr.
(DEC)
Burst
Wrap
(RCR 3)
Burst Addressing Sequence (DEC)
4-Word Burst
(BL[2:0] =
0b001)
8-Word Burst
(BL[2:0] = 0b010)
16-Word Burst
(BL[2:0] = 0b011)
Continuous Burst
(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-
40 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…
50 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…
60 6-7-0-1-2-3-4-5 6-7-8-9-10…15-0-1-2-3-4-
56-7-8-9-10-11-12-…
70 7-0-1-2-3-4-5-6 7-8-9-10…15-0-1-2-3-4-5-
67-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-
41 4-5-6-7-8-9-10-11 4-5-6-7-8…18-19 4-5-6-7-8-9-10…
51 5-6-7-8-9-10-11-12 5-6-7-8-9…19-20 5-6-7-8-9-10-11…
61 6-7-8-9-10-11-12-13 6-7-8-9-10…20-21 6-7-8-9-10-11-12-…
71 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-…
November 2007 Datasheet
Order Number: 314749-05 55
Numonyx™ StrataFlash® Embedded Memory (P33)
11.1.0.11 Burst Length
The Burst Length bits (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 29, “Burst Sequence Word Ordering” on page 54). When a burst
cycle begins, the device outputs synchronous burst data until it reaches the end of the
“burstable” address space.
11.1.0.12 End of Word Line (EOWL) Considerations
When performing synchronous burst reads with BW set (no wrap) and DH reset (1-
clock cycle), an output “delay” requiring additional clock Wait States may occur when
the burst sequence crosses its first device-row (16-word) boundary. The delay would
take place only once, and will not occur if the burst sequence does not cross a device-
row boundary. The WAIT signal informs the system of this delay when it occurs. If the
burst sequence’s start address is 4-word aligned (i.e. 0x00h, 0x04h, 0x08, 0x0Ch) then
no delay occurs. If the start address is at the end of a 4-word boundary (i.e. 0x03h,
0x07h, 0x0Bh, 0x0Fh), the worst case delay (number of Wait States required) will be
one clock cycle less than the first access Latency Count (LC-1) when crossing the first
device-row boundary (i.e. 0x0Fh to 0x10h). Other address misalignments may require
wait states depending upon the LC setting and the starting address alignment. For
example, an LC setting of 3 with a starting address of 0xFD requires 0 wait states, but
the same LC setting of 3 with a starting address of 0xFE would require 1 wait state
when crossing the first device row boundary.
11.2 Read Operations
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
mode. To change the read state, the appropriate read command must be written to the
device (see Section 9.6, “Device Command Bus Cycles” on page 44). The following
sections describe read-mode operations in detail.
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 RCR must be configured to enable synchronous burst reads of the flash
memory array (see Section , “The Clear Status Register command clears the status
register. It functions independent of VPP. The 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.Read Configuration Register” on page 49).
11.2.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 mode. 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 RCR 15 is set
The Clear Status Register command clears the status register. It functions independent
of VPP. The 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.
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
56 Order Number: 314749-05
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 29).
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.
11.2.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
11.1.0.3, “Latency Count” on page 50). 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 18, “Synchronous Single-Word Array or Non-array Read Timing” on page 34
Figure 19, “Continuous Burst Read, showing an Output Delay Timing” on page 35
Figure 20, “Synchronous Burst-Mode Four-Word Read Timing” on page 35
11.2.3 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.6, “Device Command Bus Cycles” on page 44 for details on
issuing the Read Device Identifier command). Table 30, “Device Identifier Information”
on page 56 and Table 31, “Device ID codes” on page 57 show the address offsets and
data values for this device.
Table 30: Device Identifier Information (Sheet 1 of 2)
Item Address(1) Data
Manufacturer Code 0x00 0089h
Device ID Code 0x01 ID (see Ta bl e 3 1 )
Block Lock Configuration:
BBA + 0x02
Lock Bit:
Block Is Unlocked DQ0 = 0b0
Block Is Locked 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
November 2007 Datasheet
Order Number: 314749-05 57
Numonyx™ StrataFlash® Embedded Memory (P33)
11.2.4 CFI Query
The CFI Query command instructs the device to output Common Flash Interface (CFI)
data when read. See Section 9.6, “Device Command Bus Cycles on page 44 for details
on issuing the CFI Query command. Appendix , “Common Flash Interface” on page 77
shows CFI information and address offsets within the CFI database.
11.3 Programming Operations
The device supports three programming methods: Word Programming (40h/10h),
Buffered Programming (E8h, D0h), and Buffered Enhanced Factory Programming (80h,
D0h). 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
11.4.5, “Security Modes” on page 64 for details on locking and unlocking blocks.
The Numonyx™ StrataFlash® Embedded Memory (P33) is segmented into multiple 8-
Mbit Programming Regions. See Section 4.4, “Memory Maps” on page 22 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 Numonyx™
StrataFlash® Embedded Memory (P33) device.
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 Lock Data
128-bit User-Programmable Protection Registers 0x8A–0x109 PR-LK1
Notes:
1. BBA = Block Base Address.
Table 31: Device ID codes
ID Code Type Device Density
Device Identifier Codes
–T
(Top Parameter)
–B
(Bottom Parameter)
Device Code
64-Mbit 881D 8820
128-Mbit 881E 8821
256-Mbit 891F 8922
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.
Table 30: Device Identifier Information (Sheet 2 of 2)
Item Address(1) Data
Code : Execution code ran out of the flash device on a continuous basis in the system.
Data : Information periodically programmed into the flash device and read back (e.g. execution code
shadowed and executed in RAM, pictures, log files, etc.).
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
58 Order Number: 314749-05
11.3.1 Word Programming
Word programming operations are initiated by writing the Word Program Setup
command to the device. 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 33, “Word Program Flowchart” on page 69. VPP must be above VPPLK,
and within the specified VPPL min/max values.
During programming, the 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.
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.3.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 26
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 30,
“Example VPP Supply Connections” on page 62 shows examples of device power supply
configurations.
11.3.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.6, “Device
Command Bus Cycles” on page 44), Status Register information is updated and reflects
the availability of the buffer. SR[7] indicates buffer availability: if set, the buffer is
November 2007 Datasheet
Order Number: 314749-05 59
Numonyx™ StrataFlash® Embedded Memory (P33)
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 35, “Buffer Program Flowchart” on page 71).
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 SR[7,5,4] are set. If an error occurs while writing to the array, the device
stops programming, and 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 26 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 SR[5,4] are set.
If Buffered programming is attempted while VPP is below VPPLK, 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.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 36, “BEFP
Flowchart” on page 72). 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.
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
60 Order Number: 314749-05
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.3.1 BEFP Requirements and Considerations
BEFP requirements:
Case temperature: TC = 25 °C ± 5 °C
•V
CC within specified operating range
VPP driven to VPPH
Target block unlocked before issuing the BEFP Setup and Confirm commands
The first-word address 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
The first-word address 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.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.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
November 2007 Datasheet
Order Number: 314749-05 61
Numonyx™ StrataFlash® Embedded Memory (P33)
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.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.3.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 34, “Program Suspend/Resume Flowchart” on
page 70).
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 39.
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.
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
62 Order Number: 314749-05
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.3.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 34, “Program Suspend/
Resume Flowchart” on page 70).
11.3.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.
11.4 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.
11.4.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.6, “Device Command Bus Cycles” on
page 44). 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 37, “Block Erase Flowchart”
on page 73).
Figure 30: Example VPP Supply Connections
Factory Programming with VPP = VPPH
Complete write/Erase Protection when VPP VPPLK
VCC
VPP
VCC
VPP
Low Voltage and Factory Programming
Low-voltage Programming only
Logic Control of Device Protection
VCC
VPP
Low Voltage Programming Only
Full Device Protection Unavailable
VCC
VPP
10K Ω
VPP
VCC VCC
PROT #
VCC
VPP=VPPH
VCC
November 2007 Datasheet
Order Number: 314749-05 63
Numonyx™ StrataFlash® Embedded Memory (P33)
During a block erase, the 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.
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.
11.4.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 34, “Program Suspend/Resume Flowchart” on page 70).
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 39.
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.
11.4.3 Erase Resume
The Erase Resume command instructs the device to continue erasing, and
automatically clears 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.
11.4.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.
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
64 Order Number: 314749-05
11.4.5 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.
11.4.6 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.3.6, “Program Protection” on
page 62 and Section 11.4.4, “Erase Protection” on page 63).
The Numonyx™ StrataFlash® Embedded Memory (P33) 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.
11.4.6.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.6, “Device
Command Bus Cycles” on page 44 and Figure 39, “Block Lock Operations Flowchart” on
page 75). 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.
11.4.6.2 Unlock Block
The Unlock Block command is used to unlock blocks (see Section 9.6, “Device
Command Bus Cycles” on page 44). 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 31, “Block Locking State Diagram” on page 65).
11.4.6.3 Lock-Down Block
A locked or unlocked block can be locked-down by writing the Lock-Down Block
command sequence (see Section 9.6, “Device Command Bus Cycles” on page 44).
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 31, “Block Locking State Diagram” on page 65).
November 2007 Datasheet
Order Number: 314749-05 65
Numonyx™ StrataFlash® Embedded Memory (P33)
11.4.6.4 Block Lock Status
The Read Device Identifier command is used to determine a block’s lock status (see
Section 11.2.3, “Read Device Identifier” on page 56). 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.
11.4.6.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
, “Write State Machine” on page 87, which shows valid commands during an erase
suspend.
Figure 31: Block Locking State Diagram
[X00]
[X01]
Power-Up/Reset
Unlocked
Locked
[011]
[111] [110]
Locked-
Down4,5
Software
Locked
[011]
Hardware
Locked5
Unlocked
WP# 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.
Software Block Lock (0x60/0x01) or Software Block Unlock (0x60/0xD0)
Software Block Lock-Down (0x60/0x2F)
WP# hardware control
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
66 Order Number: 314749-05
11.4.7 Selectable One-Time Programmable Blocks
Blocks from the main array may be optionally configured as OTP. Ask your local
Numonyx representative for details about any of the following selectable OTP
implementations.
11.4.7.1 Permanent Block Locking of up to 512 KB
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.
11.4.7.2 Permanent Block Locking of up to Full Main Array
This option allows all main blocks (plus the four 32-KB parameter blocks together as
one block) to be configured as OTP to prevent further program and erase operations.
This option is available for top or bottom parameter devices.
Ask your local Numonyx representative for details about either of these Selectable OTP
implementations.
11.4.8 Protection Registers
The device contains 17 Protection Registers (PR) that can be used to implement system
security measures and/or device identification. Each Protection Register can be
individually locked.
Table 32: Selectable 512 KB OTP Block Mapping
Density Top Parameter Configuration Bottom Parameter Configuration
256-Mbit
blocks 258:255 (parameters) blocks 3:0 (parameters)
block 254 (main) block 4 (main)
block 253 (main) block 5 (main)
block 252 (main) block 6 (main)
128-Mbit
blocks 130:127 (parameters) blocks 3:0 (parameters)
block 126 (main) block 4 (main)
block 125 (main) block 5 (main)
block 124 (main) block 6 (main)
64-Mbit
blocks 66:63 (parameters) blocks 3:0 (parameters)
block 62 (main) block 4 (main)
block 61 (main) block 5 (main)
block 60 (main) block 6 (main)
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 the protection registers 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.
November 2007 Datasheet
Order Number: 314749-05 67
Numonyx™ StrataFlash® Embedded Memory (P33)
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 Numonyx 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 32, “Protection Register Map” on page 67).
The user-programmable Protection Registers contain one-time programmable (OTP)
bits; when programmed, PR 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.
.
11.4.8.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.6, “Device Command Bus Cycles” on
Figure 32: Protection Register Map
0x89
Lock Register 1
15 14 13 12 11 10 9876543210
0x102
0x109
0x8A
0x91
128-bit Protection Register 16
(User-Programmable)
128-bit Protection Register 1
(User-Programmable)
0x88
0x85
64-bit Segment
(User-Programmable)
0x84
0x81
0x80
Lock Register 0
64-bit Segment
(Factory-Programmed)
15 14 13 12 11 10 9876543210
128-Bit Protection Register 0
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
68 Order Number: 314749-05
page 44). Next, perform a read operation using the address offset corresponding to the
register to be read. Table 30, “Device Identifier Information” on page 56 shows the
address offsets of the Protection Registers and Lock Registers. PR data is read 16 bits
at a time.
11.4.8.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.6, “Device Command Bus Cycles” on page 44). Next, write the
desired Protection Register data to the same Protection Register address (see
Figure 32, “Protection Register Map” on page 67).
The device programs the 64-bit and 128-bit user-programmable Protection Register
data 16 bits at a time (see Figure 40, “Protection Register Programming Flowchart” on
page 76). 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).
Note: When programming the OTP bits in the protection registers 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.
11.4.8.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.6, “Device Command Bus Cycles” on page 44). 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 30, “Device
Identifier Information” on page 56).
Bit 0 of Lock Register 0 is already programmed during the manufacturing process 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.
November 2007 Datasheet
Order Number: 314749-05 69
Numonyx™ StrataFlash® Embedded Memory (P33)
12.0 Flowcharts
Figure 33: Word Program Flowchart
Program
Suspend
Loop
Start
Write 0x40,
Word Address
Write Data,
Word Address
Read Status
Register
SR[7] =
Full Status
Check
(if desired)
Program
Complete
Suspend?
1
0
No
Yes
WORD PROGRAM PROCEDURE
Repeat for subsequent Word Program operations.
Full Status Register check can be done after each program, or
after a sequence of program operations.
Write 0xFF after the last operation to set to the Read Array
state.
Comments
Bus
Operation Command
Data = 0x40
Addr = Location to program
Write Program
Setup
Data = Data to program
Addr = Location to program
Write Data
Status register dataRead None
Check SR[7]
1 = WSM Ready
0 = WSM Busy
Idle None
(Setup)
(Confirm)
FULL STATUS CHECK PROCEDURE
Read Status
Register
Program
Successful
SR[3] =
SR[1] =
0
0
SR[4] =
0
1
1
1VPP Range
Error
Device
Protect Error
Program
Error
If an error is detected, clear the Status Register before
continuing operations - only the Clear Staus Register
command clears the Status Register error bits.
Idle
Idle
Bus
Operation
None
None
Command
Check SR[3]:
1 = VPP Error
Check SR[4]:
1 = Data Program Error
Comments
Idle None Check SR[1]:
1 = Block locked; operation aborted
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
70 Order Number: 314749-05
Figure 34: Program Suspend/Resume Flowchart
Read Status
Register
SR.7 =
SR.2 =
Read Array
Data
Program
Completed
Done
Reading
Program
Resumed
Read Array
Data
0
No
0
Yes
1
1
PROGRAM SUSPEND / RESUME PROCEDURE
Write Program
Resume
Data = D0h
Addr = Suspended block (BA)
Bus
Operation Command Comments
Write Program
Suspend
Data = B0h
Addr = X
Standby
Check SR.7
1 = WSM ready
0 = WSM busy
Standby
Check SR.2
1 = Program suspended
0 = Program completed
Write Read
Array
Data = FFh
Addr = Block address to read (BA)
Read Read array data from block other than
the one being programmed
Read
Status register data
Initiate a read cycle to update Status
register
Addr = Suspended block (BA)
Start
Write B0h
Any Address
Program Suspend
Read Status
Write 70h
Write FFh
Read Array
Write D0h
Any Address
Program Resume
Write FFh
Read Array
Write Read
Status
Data = 70h
Addr = Block to suspend (BA )
November 2007 Datasheet
Order Number: 314749-05 71
Numonyx™ StrataFlash® Embedded Memory (P33)
Figure 35: Buffer Program Flowchart
Start
Get Next
Target Address
Issue Write to Buffer
Command E8h and
Block Address
Read Status Register
(at Block Address)
Is WSM Ready?
SR.7 =
1 = Yes
Device
Supports Buffer
Writes?
Set Timeout or
Loop Counter
Timeout
or Count
Expired?
Write Confirm D0h
and Block Address
Another Buffered
Programming?
Yes
No
No
Write Buffer Data,
Start Address
X = 0
Yes
0 = No
No
Yes
Use Single Word
Programming
Abort Bufferred
Program?
No
X = N?
Write Buffer Data,
Block Address
X = X + 1
Write to another
Block Address
Buffered Program
Aborted
No
YesYes
Write Word Count,
Block Address
1. Word count values on DQ
0
-DQ
7
are loaded into the Count
register. Count ranges for this device are N = 0000h to 0001Fh.
2. The device outputs the status register when read.
3. Write Buffer contents will be programmed at the device start
address or destination flash address.
4. Align the start address on a Write Buffer boundary for
maximum programming performance (i.e., A
4
–A
0
of the start
address = 0).
5. The device aborts the Buffered Program command if the
current address is outside the original block address.
6. The Status register indicates an "improper command
sequence" if the Buffered Program command is aborted. Follow
this with a Clear Status Register command.
Full status check can be done after all erase and write
sequences complete. Write FFh after the last operation to reset
the device to read array mode.
Bus
Operation
Standby
Read
Command
Write Write to
Buffer
Read
Standby
Comments
Check SR.7
1 = WSM Ready
0 = WSM Busy
Status register Data
CE# and OE# low updates SR
Addr = Block Address
Data = E8H
Addr = Block Address
SR.7 = Valid
Addr = Block Address
Check SR.7
1 = Device WSM is Busy
0 = Device WSM is Ready
Write Program
Confirm
Data = D0H
Addr = Block Address
Write
(Notes 1, 2)
Data = N-1 = Word Count
N = 0 corresponds to count = 1
Addr = Block Address
Write
(Notes 3, 4)
Data = Write Buffer Data
Addr = Start Address
Write
(Notes 5, 6)
Data = Write Buffer Data
Addr = Block Address
Suspend
Program
Loop
Read Status Register
SR.7 =?
Full Status
Check if Desired
Program Complete
Suspend
Program
1
0
No
Yes
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
72 Order Number: 314749-05
Figure 36: BEFP Flowchart
NOTES:
1. First-word address to be programmed within the target block must be aligned on a write -buffer boundary.
2. Write-buffer contents are programmed sequentially to the flash array starting at the first word address (WSM internally increments addressing).
BEFP Exit
Repeat for subsequent blocks ;
After BEFP exit, a full Status Register check can
determine if any program error occurred ;
See full Status Register check procedure in the
Word Program flowchart.
Write 0xFF to enter Read Array state .
Standby
Read
Bus
State Operation
Status
Register
Check
Exit
Status
Comments
Data = Status Register Data
Address = 1st Word Addr.
Check SR[7]:
0 = Exit Not Completed
1 = Exit Completed
BEFP Setup
Comments
Bus
State Operation
Write
(Note 1)
BEFP
Setup
Write BEFP
Confirm
Read Status
Register
Standby
BEFP
Setup
Done?
Write Unlock
Block
Data = 0x80 @ 1st Word
Address
Data = 0x80 @ 1st Word
Address1
Data = Status Register Data
Address = 1st Word Addr.
Check SR[7]:
0 = BEFP Ready
1 = BEFP Not Ready
VPPH applied to VPP
Standby
Error
Condition
Check
If SR[7] is set, check:
SR[3] set = VPP Error
SR[1] set = Locked Block
No (SR[0]=1)
Write Data @ 1st
Word Address
Last
Data?
Write 0xFFFF,
Address Not within
Current Block
Program
Done?
Read
Status Reg.
Yes (SR[0]=0)
Y
No (SR[7]=0)
Full Status Check
Procedure
Program
Complete
Read
Status Reg.
BEFP
Exited?
Yes (SR[7]=1)
Start
Write 80h @
1st Word Address
VPP applied
Block Unlocked
Write D0h @
1st Word Address
BEFP Setup
Done?
Read
Status Reg.
No (SR[7]=1)
Exit
N
Program & Verify Phase Exit PhaseSetup Phase
BUFFERED ENHANCED FACTORY PROGRAMMING (BEFP) PROCEDURE
Check
X = 32?
Initialize Count:
X = 0
Increment Count:
X = X+1
Y
N
Check VPP, Lock
errors (SR[3,1])
Yes (SR[7]=0)
BEFP Setup delay
Data Stream
Ready?
Read
Status Reg.
Y es (SR[0]=0)
No (SR[0]=1)
BEFP Program & Verify
Comments
Bus
State
Write
(note 2)
Load
Buffer
Standby Increment
Count
Standby Initialize
Count
Data = Data to Program
Address = 1st Word Addr.
X = X+1
X = 0
Read Status
Register
Standby Program
Done?
Data = Status Reg. Data
Address = 1st Word Addr.
Check SR[0]:
0 = Program Done
1 = Program in Progress
Write Exit Prog &
Verify Phase
Data = 0xFFFF @ address
not in current block
Standby Last
Data?
No = Fill buffer again
Yes = Exit
Standby Buffer
Full?
X = 32?
Yes = Read SR[0]
No = Load Next Data Word
Read
Standby
Status
Register
Data Stream
Ready?
Data = Status Register Data
Address = 1st Word Addr.
Check SR[0]:
0 = Ready for Data
1 = Not Ready for Data
Operation
November 2007 Datasheet
Order Number: 314749-05 73
Numonyx™ StrataFlash® Embedded Memory (P33)
Figure 37: Block Erase Flowchart
Start
FULL ERASE STATUS CHECK PROCEDURE
Repeat for subsequent block erasures.
Full Status register check can be done after each block erase
or after a sequence of block erasures.
Write 0xFF after the last operation to enter read array mode.
Only the Clear Status Register command clears SR[1, 3, 4, 5].
If an error is detected, clear the Status register before
attempting an erase retry or other error recovery.
No
Suspend
Erase
1
0
0
0
1
1,1
1
1
0Yes
Suspend
Erase
Loop
0
Write 0x20,
Block Address
Write 0xD0,
Block Address
Read Status
Register
SR[7] =
Full Erase
Status Check
(if desired)
Block Erase
Complete
Read Status
Register
Block Erase
Successful
SR[1] = Block Locked
Error
BLOCK ERASE PROCEDURE
Bus
Operation Command Comments
Write
Block
Erase
Setup
Data = 0x20
Addr = Block to be erased (BA)
Write Erase
Confirm
Data = 0xD0
Addr = Block to be erased (BA)
Read None Status Register data.
Idle None
Check SR[7]:
1 = WSM ready
0 = WSM busy
Bus
Operation Command Comments
SR[3] = VPP Range
Error
SR[4,5] = Command
Sequence Error
SR[5] = Block Erase
Error
Idle None Check SR[3]:
1 = VPP Range Error
Idle None Check SR[4,5]:
Both 1 = Command Sequence Error
Idle None Check SR[5]:
1 = Block Erase Error
Idle None
Check SR[1]:
1 = Attempted erase of locked block;
erase aborted.
(Block Erase)
(Erase Confirm)
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
74 Order Number: 314749-05
Figure 38: Erase Suspend/Resume Flowchart
Erase
Completed
Read Array
Data
0
0
No
Read
1
Program
Program
Loop
Read Array
Data
1
Yes
Start
Read Status
Register
SR.7 =
SR.6 =
Erase
Resumed
Read or
Program ?
Done?
Write
Write
Standby
Standby
Write
Erase
Suspend
Read Array
or Program
Program
Resume
Data = B0h
Addr = Same partition address as
above
Data = FFh or 40h
Addr = Block to program or read
Check SR.7
1 = WSM ready
0 = WSM busy
Check SR.6
1 = Erase suspended
0 = Erase completed
Data = D0h
Addr = Any address
Bus
Operation Command Comments
Read
Status register data. Toggle CE# or
OE# to update Status register
Addr =X
Read or
Write
Read array or program data from/to
block other than the one being erased
ERASE SUSPEND / RESUME PROCEDURE
ERAS _ SUS . WMF
Write B0h
Any Address
Erase Suspend
Write 70h
Any Address
Read Status
Write D0h
Any Address
Er ase Resume
Write 70h
Any Address
Read Status
Write FFh
Any Addres
Read Arr ay
Write Read
Status
Data = 70h
Addr = Any device address
November 2007 Datasheet
Order Number: 314749-05 75
Numonyx™ StrataFlash® Embedded Memory (P33)
Figure 39: Block Lock Operations Flowchart
No
Optional
Start
Write 60h
Block Address
Write 90h
Read Block Lock
Status
Locking
Change ?
Lock Change
Complete
Write 01 ,D0,2Fh
Block Address
Write FFh
Any Address
Yes
Write
Write
Write
(Optional)
Read
(Optional)
Standby
(Optional)
Write
Lock
Setup
Lock,
Unlock, or
Lockdown
Confirm
Read ID
Plane
Block Lock
Status
Read
Array
Data = 60h
Addr = Block to lock/unlock/lock-down (BA)
Data = 01h (Lock block)
D0h (Unlock block)
2Fh (Lockdown block)
Addr = Block to lock/unlock/lock-down (BA)
Data = 90h
Addr = Block address offset +2 (BA+2)
Block Lock status data
Addr = Block address offset +2 (BA+2)
Confirm locking change on DQ
1
, DQ
0
.
(See Block Locking State Transitions Table
for valid combinations.)
Data = FFh
Addr = Block address (BA)
Bus
Operation Command Comments
LOCKING OPERATIONS PROCEDURE
LOCK_OP.WMF
Lock Confi rm
Lock Setup
Read ID Plane
Read Array
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
76 Order Number: 314749-05
Figure 40: Protection Register Programming Flowchart
FULL STATUS CHECK PROCEDURE
Program Protection Register operation addresses must be
within the Protection Register address space. Addresses
outside this space will return an error.
Repeat for subsequent programming operations.
Full Status Register check can be done after each program, or
after a sequence of program operations.
Write 0xFF after the last operation to set Read Array state.
Only the Clear Staus Register command clears SR[1, 3, 4].
If an error is detected, clear the Status register before
attempting a program retry or other error recovery.
1
0
1
1
1
PROTECTION REGISTER PROGRAMMING PROCEDURE
Start
Write 0xC0,
PR Address
Write PR
Address & Data
Read Status
Register
SR[7] =
Full Status
Check
(if desired)
Program
Complete
Read Status
Register Data
Program
Successful
SR[3] =
SR[4] =
SR[1] =
VPP Range Error
Program Error
Register Locked;
Program Aborted
Idle
Idle
Bus
Operation
None
None
Command
Check SR[3]:
1 =VPP Range Error
Check SR[4]:
1 =Programming Error
Comments
Write
Write
Idle
Program
PR Setup
Protection
Program
None
Data = 0xC0
Addr = First Location to Program
Data = Data to Program
Addr = Location to Program
Check SR[7]:
1 = WSM Ready
0 = WSM Busy
Bus
Operation Command Comments
Read None Status Register Data.
Idle None Check SR[1]:
1 =Block locked; operation aborted
(Program Setup)
(Confirm Data)
0
0
0
November 2007 Datasheet
Order Number: 314749-05 77
Numonyx™ StrataFlash® Embedded Memory (P33)
13.0 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.6, “Device Command Bus Cycles” on page 44). 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.
13.1 Query Structure Output
The Query database allows system software to obtain information for controlling the
flash device. This section describes the devices 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 have 00h on
the upper byte in this mode.
Table 33: Summary of Query Structure Output as a Function of Device and Mode
Device Hex
Offset
Hex
Code
A
SCII
V
alue
00010: 51 "Q"
Device Addresses 00011: 52 "R"
00012: 59 "Y"
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
78 Order Number: 314749-05
Table 34: Example of Query Structure Output of x16- Devices
0.1 Query Structure Overview
The Query command causes the flash component to display the Common Flash
Interface (CFI) Query structure or database. Table 35 summarizes the structure sub-
sections and address locations.
Table 35: Query Structure
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 Numonyx-specific Extended Query Table.
13.2 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 36: CFI Identification
Word Addressin
g
: B
y
te Addressin
g
:
Offset Hex Code Value Offset Hex Code Value
A
X
–A
0 D15
D0
A
X
–A
0 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 PrVendo
r
00014h P_IDHI ID # 00014h P_IDLO ID #
00015h PLO PrVendor 00015h P_IDHI ID #
00016h PHI TblAd
r
00016h ... ...
00017h
A
_IDLO AltVendor 00017h
00018h
A
_IDHI ID # 00018h
... ... ... ...
Offset Sub-Section Name Descri
p
tion(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
P(3) Primary Intel-specific Extended Query Table Vendor-defined additional information specific
to the Primary Vendor Algorithm
Offset Length Description Add.
Hex
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
November 2007 Datasheet
Order Number: 314749-05 79
Numonyx™ StrataFlash® Embedded Memory (P33)
Table 37: System Interface Information
Offset Length Description Add.
Hex
Code Value
1Bh 1 1B: --17 1.7V
1Ch 1 1C: --20 2.0V
1Dh 1 1D: --85 8.5V
1Eh 1 1E: --95 9.5V
1Fh 1 n” such that t
yp
ical sin
g
le word
p
ro
g
ram time-out = 2n
μ
-se
c
1F: --08 256μs
20h 1 “n” such that t
yp
ical full buffer write time-out = 2n
μ
-sec 20: --09 512μs
21h 1 “n” such that t
yp
ical block erase time-out = 2nm-sec 21: --0A 1s
22h 1 “n” such that t
yp
ical full chi
p
erase time-out = 2nm-sec 22: --00 NA
23h 1 “n” such that maximum word
p
ro
g
ram time-out = 2ntimes t
yp
ical 23: --01 512μs
24h 1 “n” such that maximum buffer write time-out = 2ntimes t
yp
ical 24: --01 1024μs
25h 1 n” such that maximum block erase time-out =
2
ntimes t
yp
ical 25: --02 4s
26h 1 “n” such that maximum chi
p
erase time-out = 2ntimes t
yp
ical 26: --00 NA
VPP [programming] supply minimum program/erase voltage
bits 0–3 BCD 100 mV
bits 4–7 HEX volts
VPP [programming] supply maximum program/erase voltage
bits 0–3 BCD 100 mV
bits 4–7 HEX volts
VCC logic supply minimum program/erase voltage
bits 0–3 BCD 100 mV
bits 4–7 BCD volts
VCC logic supply maximum program/erase voltage
bits 0–3 BCD 100 mV
bits 4–7 BCD volts
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
80 Order Number: 314749-05
13.3 Device Geometry Definition
Table 38: Device Geometry Definition
Offset Len
g
th Description Code
27h 1“n” such that device size = 2nin number of bytes 27: See table below
76543210
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 = 2n2A: --06 64
2B: --00
2Ch 1 2C:
2Dh 4 Erase Block Region 1 Information 2D:
bits 0–15 = y, y+1 = number of identical-size erase blocks 2E:
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:
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:
37:
38:
See table below
See table below
See table below
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:
Number of erase block regions (x) within device:
1. x = 0 means no erase blocking; the device erases in bulk
2. x specifies the number of device regions with one or
more contiguous same-size erase blocks.
3. Symmetrically blocked partitions have one blocking region
Address 64-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
128-Mbit 256-Mbit
November 2007 Datasheet
Order Number: 314749-05 81
Numonyx™ StrataFlash® Embedded Memory (P33)
13.4 Numonyx-Specific Extended Query Table
Table 39: Primary Vendor-Specific Extended Query
Discrete
B
T
–- –- die 1 (B) die 2 (T) die 1 (T) die 2 (B)
112: --00 --00 --40 --00 --40 --00
512-Mbit
Address
–B –T
Offset(1) Length Descri
p
tion Hex
P = 10Ah (Optional flash features and commands)
A
dd. Code
V
alue
(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: --35 "5"
(P+5)h 4 Optional feature and command support (1=yes, 0=no) 10F: --E6
(P+6)h bits 10–31 are reserved; undefined bits are “0.” If bit 31 is 110: --09
(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: --40
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 11 Permanent Block Locking of up to Full Main Array supported bit 11 = 1 Yes
bit 12 Permanent Block Locking of up to Partial Main Array supported bit 12 = 0 No
bit 30 CFI Link(s) to follow bit 30 = 1 Yes
bit 31 Another "Optional Features" field to follow bit 31 = 0 No
(P+9)h 1 113: --01
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 116: --18 1.8V
(P+D)h 1 117: --90 9.0V
Supported functions after suspend: read Array, Status, Query
Other supported operations are:
bits 1–7 reserved; undefined bits are “0
VPP optimum program/erase supply voltage
bits 0–3 BCD value in 100 mV
bits 4–7 HEX value in volts
VCC logic supply highest performance program/erase voltage
bits 0–3 BCD value in 100 mV
bits 4–7 BCD value in volts
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
82 Order Number: 314749-05
Table 40: Protection Register Information
Table 41: Burst Read Information
Offset(1) Len
g
th Description Hex
P = 10Ah (Optional flash features and commands)
A
dd. Code
V
alue
(P+E)h 1 118: --02 2
(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 re
g
ister b
y
tes. Some are pre-pro
g
rammed 11B: --03 8 byte
(P+12)h 11C: --03 8 byte
(P+13)h 10 Protection Field 2: Protection Description 11D: --89 89h
(P+14)h 11E: --00 00h
(P+15)h 11F: --00 00h
(P+16)h 120: --00 00h
(P+17)h 121: --00 0
(P+18)h bits 40–47 = “n” n = factory pgm'd groups (high byte) 122: --00 0
(P+19)h 123: --00 0
(P+1A)h 124: --10 16
(P+1B)h 125: --00 0
(P+1C)h 126: --04 16
bits 48–55 = “n” \ 2n = factory programmable bytes/group
bits 56–63 = “n” n = user pgm'd groups (low byte)
bits 64–71 = “n” n = user
pg
m'd
g
rou
p
s
(
hi
g
h b
y
te
)
bits 72–79 = “n” 2n = user programmable bytes/group
with device-unique serial numbers. Others are user
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
Bits 0–31 point to the Protection register physical Lock-word
address in the Jedec-plane.
Following bytes are factory or user-programmable.
bits 32–39 = “n” n = factory pgm'd groups (low byte)
Number of Protection register fields in JEDEC ID space.
“00h,” indicates that 256 protection fields are available
Offset(1) Len
g
th Description Hex
P = 10Ah (Optional flash features and commands)
A
dd. Code
V
alue
(P+1D)h 1 127: --03 8 byte
(P+1E)h 1 128: --04 4
(P+1F)h 1 129: --01 4
(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
Page Mode Read capability
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
p
a
g
e buffer.
Number of synchronous mode read configuration fields that
follow. 00h indicates no burst capability.
Synchronous mode read capability configuration 1
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 out
p
ut width.
November 2007 Datasheet
Order Number: 314749-05 83
Numonyx™ StrataFlash® Embedded Memory (P33)
Table 42: Partition and Erase Block Region Information
Table 43: Partition Region 1 Information (Sheet 1 of 2)
Offset
(1) See table below
P = 10Ah Descri
p
tion
A
ddress
Bottom To
p
(
O
p
tional flash features and commands
)
Len Bot Top
(P+23)h (P+23)h
1 12D: 12D:Number of device hardware-partition regions within the device.
x = 0: a single hardware partition device (no fields follow).
x specifies the number of device partition regions containing
one or more contiguous erase block regions.
Offset
(1) See table below
P = 10Ah Descri
p
tion
A
ddress
Bottom To
p
(
O
p
tional flash features and commands
)
Len Bot Top
(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 1 132: 132:
(P+29)h (P+29)h 1 133: 133:
(P+2A)h (P+2A)h 1 134: 134:
(P+2B)h (P+2B)h 1 135: 135:Types of erase block regions in this Partition Region.
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)
Number of program or erase operations allowed in a partition
bits 0–3 = number of simultaneous Program operations
bits 4–7 = number of simultaneous Erase operations
Simultaneous program or erase operations allowed in other partitions while a
partition in this region is in Program mode
bits 0–3 = number of simultaneous Program operations
bits 4–7 = number of simultaneous Erase operations
Simultaneous program or erase operations allowed in other partitions while a
partition in this region is in Erase mode
bits 0–3 = number of simultaneous Program operations
bits 4–7 = number of simultaneous Erase operations
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
84 Order Number: 314749-05
Table 44: Partition Region 1 Information (Sheet 2 of 2)
Offset
(1) See table below
P = 10Ah Descri
p
tion
A
ddress
Bottom To
p
(
O
p
tional flash features and commands
)
Len Bot Top
(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) 213A:13A:
(P+31)h (P+31)h Block erase cycles x 1000 13B: 13B:
(P+32)h (P+32)h 1 13C: 13C:
(P+33)h (P+33)h 1 13D: 13D:
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 114A:14A:
(P+41)h (P+41)h 114B:14B:
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:
Partition 1 (erase block Type 1) page mode and synchronous mode capabilities
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 1 (erase block Type 1) bits per cell; internal EDAC
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
Partition 1 (erase block Type 2) bits per cell; internal EDAC
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
Partition 1 (erase block Type 2) page mode and synchronous mode capabilities
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
November 2007 Datasheet
Order Number: 314749-05 85
Numonyx™ StrataFlash® Embedded Memory (P33)
Table 45: Partition and Erase Block Region Information
Address 64-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
128-Mbit 256-Mbit
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
86 Order Number: 314749-05
Table 46: CFI Link Information
Offse
t
(1) Len
g
th Descri
p
tion Hex
P = 10Ah (Optional flash features and commands)
A
dd. Code
V
alue
(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:
(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
Bit 5 = Link Field & Table relative location
Bits 6–7 = Reserved
See table below
See table below
Discrete
–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
Address 512-Mbit
–B –T
November 2007 Datasheet
Order Number: 314749-05 87
Numonyx™ StrataFlash® Embedded Memory (P33)
14.0 Write State Machine
Figure 41 through Figure 46 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 41: Write State Machine—Next State Table (Sheet 1 of 6)
Read
Array (2)
Word
Program (3,4)
Buffered
Program
(BP)
Erase
Setup (3,4)
Buffered
Enhanced
Factory Pgm
Setup (3, 4)
BE Confirm,
P/E
Resume,
ULB,
Confirm (8)
BP / Prg /
Erase
Suspend
Read
Status
Clear
Status
Register (5)
Read
ID/Query
Lock, Unlock,
Lock-down,
CR setup (4)
(FFH) (10H/40H) (E8H) (20H) (80H) (D0H) (B0H) (70H) (50H) (90H, 98H) (60H)
Ready Program
Setup BP Setup Erase
Setup BEFP Setup Lock/CR
Setup
Ready
(Unlock
Block)
Setup
Busy
Setup
Busy
Word
Program
Suspend
Suspend
Word
Program
Busy
Setup
BP Load 1
BP Load 2
BP
Confirm BP Busy
BP Busy BP Suspend
BP
Suspend BP Busy
Setup Erase Busy
Busy Erase
Suspend
Suspend Erase
Suspend
Word
Program
Setup in
Erase
Suspend
BP Setup in
Erase
Suspend
Erase Busy
Lock/CR
Setup in
Erase
Suspend
BP Suspend
Erase
BP Busy
Erase Busy
Erase Suspend Erase Suspend
Ready (Error)
Erase Busy
BP Suspend
Ready (Error)
Word
Program
Program Busy
Word Program Suspend
Word Program Busy
OTP
Ready (Lock Error)
Ready Ready
Ready (Lock Error)
OTP Busy
Current Chip
State (7)
Command Input to Chip and resulting Chip Next State
BP
BP Busy
Lock/CR Setup
BP Load 2
Ready (Error)Ready (Error)
Word Program Busy
BP Confirm if Data load into Program Buffer is complete; Else BP Load 2
Word Program Suspend
BP Load 1
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
88 Order Number: 314749-05
Figure 42: Write State Machine—Next State Table (Sheet 2 of 6)
Setup
Busy
Word
Program
Suspend in
Erase
Suspend
Suspend
Word
Program
Busy in
Erase
Suspend
Setup
BP Load 1
BP Load 2
BP
Confirm
BP Busy in
Erase
Suspend
BP Busy
BP Suspend
in Erase
Suspend
BP
Suspend
BP Busy in
Erase
Suspend
Erase
Suspend
(Unlock
Block)
Setup
BEFP
Loading
Data (X=32)
Erase Suspend (Error)
Erase Suspend (Lock Error [Botch])
Ready (Error) Ready (Error)
BP Suspend in Erase Suspend
Ready (Error in Erase Suspend)
BP Busy in Erase Suspend
BP Suspend in Erase Suspend
BP Busy in Erase Suspend
Word Program Busy in Erase Suspend
Word
Program in
Erase
Suspend
Word Program Busy in Erase Suspend
Word Program Suspend in Erase Suspend
Lock/CR Setup in Erase
Suspend Erase Suspend (Lock Error)
BP Confirm if Data load into Program Buffer is complete; Else BP Load 2
BP in Erase
Suspend
BP Load 2
Word Program Busy in Erase Suspend Busy
Word Program Suspend in Erase Suspend
BEFP Program and Verify Busy (if Block Address given matches address given on BEFP Setup command). Commands treated as data. (7)
BEFP
Busy
Buffered
Enhanced
Factory
Program
Mode
BP Load 1
Read
Array
(
2
)
Word
Program (3,4)
Buffered
Program
(BP)
Erase
Setup (3,4)
Buffered
Enhanced
Factory Pgm
Setup (3, 4)
BE Confirm,
P/E
Resume,
ULB,
Confirm (8)
BP / Prg /
Erase
Suspend
Read
Status
Clear
Status
Register (5)
Read
ID/Query
Lock, Unlock,
Lock-down,
CR setup (4)
(FFH) (10H/40H) (E8H) (20H) (80H) (D0H) (B0H) (70H) (50H) (90H, 98H) (60H)
Current Chip
State (7)
Command Input to Chip and resulting Chip Next State
November 2007 Datasheet
Order Number: 314749-05 89
Numonyx™ StrataFlash® Embedded Memory (P33)
Figure 43: Write State Machine—Next State Table (Sheet 3 of 6)
Setup
Busy
Setup
Busy
Suspend
Setup
BP Load 1
BP Load 2
BP
Confirm
BP Busy
BP
Suspend
Setup
Busy
Suspend
Erase
Word
Program
OTP
Ready
Current Chip
State (7)
BP
Lock/CR Setup
OTP
Setup (4)
Lock
Block
Confirm (8)
Lock-Down
Block
Confirm (8)
Write RCR
Confirm (8)
Block Address
(?WA0) 9
Illegal Cmds or
BEFP Data (1)
(C0H) (01H) (2FH) (03H) (XXXXH) (all other codes)
OTP
Setup
Ready
(Lock
Error)
Ready
(Lock
Block)
Ready
(Lock Down
Blk)
Ready
(Set CR)
Ready
N/A
Ready
Ready (BP Load 2 BP Load 2
Ready
BP Confirm if
Data load into
Program Buffer is
complete; ELSE
BP Load 2
Ready (Error)
(Proceed if
unlocked or lock
error)
Ready (Error)
Ready
Ready
N/A
BP Confirm if Data load into Program Buffer is
complete; ELSE BP load 2
Ready (Error)
BP Busy
Erase Busy
Word Program Suspend
BP Load 1
BP Load 2
OTP Busy
Word Program Busy
Word Program Busy
WSM
Operation
Completes
Command Input to Chip and resultin
g
Chip Next State
N/A
Ready (Lock Error)
Ready
BP Suspend
Ready (Error)
Erase Suspend
N/A
N/A
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
90 Order Number: 314749-05
Figure 44: Write State Machine—Next State Table (Sheet 4 of 6)
OTP
Setup (4)
Lock
Block
Confirm (8)
Lock-Down
Block
Confirm (8)
Write RCR
Confirm (8)
Block Address
(?WA0) 9
Illegal Cmds or
BEFP Data (1)
(C0H) (01H) (2FH) (03H) (XXXXH) (all other codes)
WSM
Operation
Completes
Command Input to Chip and resulting Chip Next State
Current Chip
State (7)
NA
Erase Suspend
N/A
Ready (BP Load 2 BP Load 2
Ready
BP Confirm if
Data load into
Program Buffer is
complete; Else
BP Load 2
Ready (Error)
(Proceed if
unlocked or lock
error)
Ready (Error)
Erase Suspend
Erase
Suspend
(Lock
Error)
Erase
Suspend
(Lock
Block)
Erase
Suspend
(Lock Down
Block)
Erase
Suspend
(Set CR)
Ready (BEFP
Loading Data) Ready (Error)
BEFP Program and Verify Busy (if Block Address
given matches address given on BEFP Setup
command). Commands treated as data. (7)
BP Load 1
Ready (Error)
BP Confirm if Data load into Program Buffer is
complete; Else BP Load 2
Ready (Error in Erase Suspend)
Word Program Suspend in Erase Suspend
BP Load 2
Ready
Word Program Busy in Erase Suspend Busy
Word Program Busy in Erase Suspend
BEFP Busy
Ready
Erase Suspend (Lock Error) N/A
BP Busy in Erase Suspend
BP Suspend in Erase Suspend
N/A
Setup
Busy
Suspend
Setup
BP Load 1
BP Load 2
BP
Confirm
BP Busy
BP
Suspend
Setup
BEFP
Busy
Buffered
Enhanced
Factory
Program
Mode
Lock/CR Setup in Erase
Suspend
BP in Erase
Suspend
Word
Program in
Erase
Suspend
November 2007 Datasheet
Order Number: 314749-05 91
Numonyx™ StrataFlash® Embedded Memory (P33)
Figure 45: Write State Machine—Next State Table (Sheet 5 of 6)
Read
Array
(
2
)
Word
Program
Setup (3,4)
BP Setup Erase
Setup (3,4)
Buffered
Enhanced
Factory Pgm
Setup (3, 4)
BE Confirm,
P/E
Resume,
ULB Confirm
(8)
Program/
Erase
Suspend
Read
Status
Clear
Status
Register (5)
Read
ID/Query
Lock, Unlock,
Lock-down,
CR setup (4)
(FFH) (10H/40H) (E8H) (20H) (30H) (D0H) (B0H) (70H) (50H) (90H, 98H) (60H)
Status Read
Command Input to Chip and resulting Output Mux Next State
Output Next State Table
Status Read
Output mux
does not
change.
Status
Read
ID Read
Status Read
Ready,
Erase Suspend,
BP Suspend
Status Read
Lock/CR Setup,
Lock/CR Setup in
Erase Susp
Output does not change. Status Read
BEFP Setup,
BEFP Pgm & Verify
Busy,
Erase Setup,
OTP Setup,
BP: Setup, Load 1,
Load 2, Confirm,
Word Pgm Setup,
Word Pgm Setup in
Erase Susp,
BP Setup, Load1,
Load 2, Confirm in
Erase Suspend
Current chip state
OTP Busy
BP Busy,
Word Program
Busy,
Erase Busy,
BP Busy
BP Busy in Erase
Suspend
Word Pgm
Suspend,
Word Pgm Busy in
Erase Suspend,
Pgm Suspend In
Erase Sus
p
end
Read Array
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
92 Order Number: 314749-05
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.
Figure 46: Write State Machine—Next State Table (Sheet 6 of 6)
OTP Busy
BP Busy,
Word Program
Busy,
Erase Busy,
BP Busy
BP Busy in Erase
Suspend
Word Pgm
Suspend,
Word Pgm Busy in
Erase Suspend,
Pgm Suspend In
Erase Sus
p
end
BEFP Setup,
BEFP Pgm & Verify
Busy,
Erase Setup,
OTP Setup,
BP: Setup, Load 1,
Load 2, Confirm,
Word Pgm Setup,
Word Pgm Setup in
Erase Susp,
BP Setup, Load1,
Load 2, Confirm in
Erase Suspend
Current chip state
Ready,
Erase Suspend,
BP Suspend
Lock/CR Setup,
Lock/CR Setup in
Erase Susp
OTP
Setup (4)
Lock
Block
Confirm (8)
Lock-Down
Block
Confirm (8)
Write CR
Confirm (8)
Block Address
(?WA0)
Illegal Cmds or
BEFP Data (1)
(C0H) (01H) (2FH) (03H) (FFFFH) (all other codes)
WSM
Operation
Completes
Output does
not change.
A
rray
Read Status Read
Array Read Output does not
change.
Output does not change.
Status
Read
Status Read
Status Read
Command Input to Chip and resulting Output Mux Next State
Output Next State Table
November 2007 Datasheet
Order Number: 314749-05 93
Numonyx™ StrataFlash® Embedded Memory (P33)
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 multiplexer (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.
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
94 Order Number: 314749-05
Appendix A Additional Information
Order/Document
Number Document/Tool
317460 Numonyx™ StrataFlash® Embedded Memory (P33) Specification Update
314750 Numonyx™ StrataFlash® Embedded Memory (P30) to Numonyx™ StrataFlash® Embedded Memory
(P33) Conversion Guide Application Note 867
300783 Using Numonyx™® Flash Memory: Asynchronous Page Mode and Synchronous Burst Mode
308551 Numonyx™ StrataFlash® Memory (J3 v. D) Datasheet
306667 Migration Guide for Numonyx™ StrataFlash® Memory (J3) to Numonyx™ StrataFlash® Embedded
Memory (P30/P33) Application Note 812
290737 Numonyx™ StrataFlash® Synchronous Memory (K3/K18) Datasheet
252802 Numonyx™ Flash Memory Design for a Stacked Chip Scale Package (SCSP)
298161 Numonyx™ Flash Memory Chip Scale Package User’s Guide
296514 Numonyx™ Small Outline Package Guide
297833 Numonyx™ Flash Data Integrator (Numonyx™ FDI) User Guide
298136 Numonyx™ Persistent Storage Manager (Numonyx™ PSM) User Guide
306668 Migration Guide for Spansion* S29GLxxxN to Numonyx™ StrataFlash® Embedded Memory (P30/P33)
Application Note 813
Notes:
1. Please call the Numonyx Literature Center at (800) 548-4725 to request Numonyx documentation. International
customers should contact their local Numonyx or distribution sales office.
2. Visit Numonyx’s World Wide Web home page at http://www.Numonyx.com for technical documentation and tools.
3. For the most current information on Numonyx Flash Memory, visit our website at
http://www.Numonyx.com/go/choosesmart.
November 2007 Datasheet
Order Number: 314749-05 95
Numonyx™ StrataFlash® Embedded Memory (P33)
Appendix B Ordering Information for Discrete Products
Figure 47: Decoder
F 6 4 P 3 3 B8E 2T 0
Product Line Designator
28 F = Intel® Flash Memory
Package Designator
TE = 56- Lead TSOP, leaded
JS = 56- Lead TSOP, lead- free
RC = 64- Ball Easy BGA, leaded
PC = 64- Ball Easy BGA, lead- free
Device Density
640 = 64- Mbit
128 = 128- Mbit
256 = 256- Mbit
Product Family
P 33 = Intel StrataFlas Embedded Memory
V
CC
= 2. 3– 3. 6V
V
CCQ
= 2. 3 3. 6 V
Access Speed
85 ns
Parameter Location
B = Bottom Parameter
T = Top Parameter
8 5
Table 47: Valid Combinations for Discrete Products - 130nm
64-Mbit 128-Mbit 256-Mbit
RC28F640P33T85 RC28F128P33T85 RC28F256P33T85
RC28F640P33B85 RC28F128P33B85 RC28F256P33B85
PC28F640P33T85 PC28F128P33T85 PC28F256P33T85
PC28F640P33B85 PC28F128P33B85 PC28F256P33B85
TE28F640P33T85 TE28F128P33T85 TE28F256P33T95
TE28F640P33B85 TE28F128P33B85 TE28F256P33B95
JS28F640P33T85 JS28F128P33T85 JS28F256P33T95
JS28F640P33B85 JS28F128P33B85 JS28F256P33B95
Numonyx™ StrataFlash® Embedded Memory (P33)
Datasheet November 2007
96 Order Number: 314749-05
Appendix C Ordering Information for SCSP Products
Note: * The “B” parameter shown in the table and chart above is used for both “top” and “bottom” options in 512-Mbit densities.
The “T” (Top Boot) configuration is no longer available as it was identical to the Bottom Boot configuration in this density.
§ §
Figure 48: Decoder for SCSP Devices
Table 48: Valid Combinations for Dual- Die Products - 130nm
64-Mbit 128-Mbit 256-Mbit 512-Mbit*
RD48F2000P0XBQ0 RD48F3000P0XBQ0 RD48F4000P0XBQ0 RD48F4400P0TBQ0
RD48F2000P0XTQ0 RD48F3000P0XTQ0 RD48F4000P0XTQ0 PF48F4400P0TBQ0
PF48F2000P0XBQ0 PF48F3000P0XBQ0 PF48F4000P0XBQ0 RC48F4400P0TB00
PF48F2000P0XTQ0 PF48F3000P0XTQ0 PF48F4000P0XTQ0 PC48F4400P0TB00
TE48F4400P0TB00
JS48F4400P0TB00
F 4 0 P 0 X B8D 4R 0 0 Q
Group Designator
48 F = Flas h Memory only
Package Designator
RD = Intel
®
SCSP, leaded
PF = Intel
®
SCSP, lead-free
RC = 64- Ball Easy BGA, leaded
PC = 64- Ball Easy BGA, lead-free
TE = 56- Lead TSOP, leaded
JS = 56- Lead TSOP, lead- free
Flash Density
0 = N o die
2 = 64- Mbit
3 = 128-Mbit
4 = 256-Mbit
Flash #1
Flash #2
Flash #3
Flash #4
Flash Family 1/2
Flash Family 3/4
0
Product Family
P = Intel StrataFlas Embedded Memory
0 = N o die
Device Details
0 = Original version of the product
( refer to the latest version of the
datasheet for details)
Ballout Designator
Q = QUAD+ ballout
0 = Discrete ballout
Parameter, Mux Configuration
B = Bottom Parameter, Non Mux
T = Top Parameter, Non Mux
I/ O Voltage, CE # Configuration
X = Individual Chip Enable(s)
T = Virtual Chip Enable(s)
V
CC
= 2.3V –3.6V
V
CCQ
= 2. 3 V 3. 6 V