— 85/88 ns initial access
— 40 MHz with zero wait states, 20 ns clock-to-
data output synchronous-burst read mode
— 25 ns asynchronous-page read mode
— 4-, 8-, 16-, and contin uous-word burst mo de
— Buffered Enhanced Factory Programm ing
(BEFP) at 5 µs/byte (Typ)
— 1.8 V buffered program ming at 7 µs/b yte (Typ)
■ Architecture
— Multi-Level Cell Technology: Highest Density
at Lowest Cost
— Asymmetrically-blocked archit ecture
— Four 32-KByte parameter block s: top or
— 64/128/256/512-Mbit and 1-Gbit densities in
— 16-bit wide data bus
Flash Data Integrator optimized
Set compatible
package
Intel
® Easy BGA package
Intel® QUAD+ SCSP
PP
= V
SS
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 synchronousburst read mode, fast asynchronous access times, low power, flexible security options, and three
industry standard package choices.
The P30 product family is manufactured using Intel
®
130 nm ETOX™ VIII process technology.
Order Number: 306666, Revision: 001
April 2005
INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY
ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN
INTEL'S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHA TSOEVER, AND INTEL DISCLAIMS
ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES
RELATING T O F ITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER
INTELLECTUAL PROPERTY RIGHT. Intel products are not intended for use in medical, life saving, or life sustaining applications.
Intel may make changes to specifications and product descriptions at any time, without notice.
This document contains information on products in the design phase of development. The information here is subject to change without notice. Do not
finalize a design with this information.
StrataFlash® Embedded Memory (P30) Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing
your product order.
Copies of documents which have an ordering number and are referenced in this document, or other Intel literature may be obtained by calling 1-800-
This document provides information about the Intel StrataFlash® Embedded Memory (P30) device
and describes its features, operation, and specifications.
1.1Nomenclature
1.8 V :VCC (core) voltage range of 1.7 V – 2.0 V
1-Gbit P30 Family
3.0 V :V
9.0 V :V
Block :A group of bits, bytes,1-Gbit P30 Family or words within the
Main block :An array block that is usually used to store code and/or data.
Parameter block :An array block that is usually used to store frequently changing
Top parameter device :A device with its parameter blocks located at the highest
Bottom parameter device :A device with its parameter blocks located at the lowest
1.2Acronyms
(I/O) voltage range of 1.7 V – 3.6 V
CCQ
voltage range of 8.5 V – 9.5 V
PP
flash memory array that erase simultaneously when the Erase
command is issued to the device. The 1-Gbit P30 Family has
two block sizes: 32-KByte and 128-KByte.
Main blocks are larger than parameter blocks.
data or small system parameters that traditionally would be
stored in EEPROM.
RFU :Reserved for Future Use
SR :Status Register
WSM :Write State Machine
1.3Conventions
VCC :Signal or voltage connection
:Signal or voltage level
V
CC
0x : Hexadecimal number prefix
0b : Binary number prefix
SR[4] :Denotes an individual register bit.
A[15:0] :Denotes a group of similarly named signals, such as address
A5 :Denotes one element of a signal group membership, such as
or data bus.
an individual address bit.
Bit :Binary unit
Byte : Eight bits
Word : Two bytes, or sixteen bits
Kbit : 1024 bits
KByte : 1024 bytes
KWord : 1024 words
Mbit :1,048,576 bits
MByte : 1,048,576 bytes
MWord : 1,048,576 words
This section provides an overview of the features and capabilities of the 1-Gbit P30 Family device.
The P30 family provides density upgrades from 64-Mbit through 1-Gbit. This family of devices
provides high performance at low voltage on a 16-bit data bus. Individually erasable memory
blocks are sized for optimum code and data storage.
Upon initial power up or return from reset, the device defaults to asynchronous page-mode read.
Configuring the Read Configuration Register enables synchronous burst-mode reads. In
synchronous burst mode, output data is synchronized with a user-supplied clock signal. A WAIT
signal provides an easy CPU-to-flash memory synchronization.
In addition to the enhanced architecture and interface, the device incorporates technology that
enables fast factory program and erase operations. Designed for low-voltage systems, the 1-Gbit
P30 Family supports read operations with V
at 1.8 V or 9.0 V. Buffered Enhanced Factory Programming (BEFP) provides the fastest flash
V
PP
array programming performance with V
at 1.8 V, VCC and VPP can be tied together for a simple, ultra low power design. In addition to
voltage flexibility, a dedicated VPP connection provides complete data protection when V
.
V
PPLK
1-Gbit P30 Family
at 1.8 V, and erase and program operations with
CC
at 9.0 V, which increases factory throughput. With VPP
PP
PP
≤
A Command User Interface (CUI) is the interface between the system processor and all internal
operations of the device. An internal Write State Machine (WSM) automatically executes the
algorithms and timings necessary for block erase and program. A Status Register indicates erase or
program completion and any errors that may have occurred.
An industry-standard command sequence invokes program and erase automation. Each erase
operation erases one block. The Erase Suspend feature allows system software to pause an erase
cycle to read or program data in another block. Program Suspend allows system software to pause
programming to read other locations. Data is programmed in word increments (16 bits).
The 1-Gbit P30 Family’s protection register allows unique flash device identification that can be
used to increase system security. The individual Block Lock feature provides zero-latency block
locking and unlocking. In addition, the P30 device also has four pre-defined spaces in the main
array that can be configured as One-Time Programmable (OTP).
Package HeightA--1.200--0.047
StandoffA
Package Body ThicknessA
Lead Widthb0.1000.1500.2000.0040.0060.008
Lead Thicknessc0.1000.1500.2000.0040.0060.008
Package Body LengthD
Package Body WidthE13.80014.00014.2000.5430.5510.559
Lead Pitche-0.500--0.0197-
Terminal DimensionD19.80020.0020.2000.7800.7870.795
Lead Tip LengthL0.5000.6000.7000.0200.0240.028
Lead CountN-56--56Lead Tip Angle∅0°3°5°0°3°5°
Seating Plane CoplanarityY--0.100--0.004
Lead to Package OffsetZ0.1500.2500.3500. 0060.0100. 014
Top View - Ball side downBottom View - Ball Side Up
A1
87654321
A
B
C
D
E
F
G
H
A
Seating
Plane
Note: Drawi ng not to scale
Corner
S1
S2
b
e
Y
Table 2. Easy BGA Package Dimensions
Product Informa tion
Package Height (64/128/256-Mbit)
Package Height (512-Mbit)
Ball Height (64/128/256-Mbit)
Ball Height (512-Mbit)
Package Body Thickness (64/128/256-Mbit)
Package Body Thickness (512-Mbit)
Ball (Lead) Width
Package Body Width
Package Body Length
Pitch
Ball (Lead) Count
Seating Plane Coplanarity
Corner to Ball A1 Distance Along D
Corner to Ball A1 Distance Along E
Package HeightA--1.200--0.0472
Ball HeightA
Package Body ThicknessA
1
0.200--0.0079--
2
-0.860--0.0339Ball (Lead) Widthb0.3250.3750.4250.01280.01480.0167
Package Body Width D9.90010.00010.1000.38980.39370.3976
Package Body Length E7.9008.0008.1000.31100.31500.3189
Pitch e-0.800--0.0315Ball (L ead) Count N-8 8--88Seating Plane CoplanarityY--0.100--0.0039
Corner to Ball A1 Distance Along E S
Corner to Ball A1 Distance Along D S
Package HeightA--1.0 00--0.039 4
Ball HeightA10.117--0.0046-Package Body ThicknessA2-0.740--0.0291Ball (Lead) Widthb0.3000.3500.4000.01180.01380.0157
Package Body LengthD10.90011.0011.1000.42910.43310.4370
Package Body WidthE7.9008.008.1000.31100.31500.3189
Pitch e-0.80--0.0315Ball (Lead) Count N-88--88Seating Plane CoplanarityY--0.1 00--0.003 9
Corner to Ball A1 Distance Along E S11.1001.2001.3000.04330.047 20.0512
Corner to Ball A1 Distance Along D S21.0001.1001.2000.03940.04330.04 7 2
Package HeightA--1.200--0.0472
Ball HeightA10.200--0.0079-Package Body ThicknessA2-0.860--0.0339Ball (Lead) Widthb0.3250.3750.4250.01280.01480.0167
Package Body Length D10.90011.00011.1000.42910.43310.4370
Package Body Width E7.9008.0008.1000.31100.31500.3189
Pitch e-0.800--0.0315B a ll (Lead) Count N-88--8 8Seating Plane CoplanarityY--0.100--0.0039
C o rner to Ball A1 Distance Along E S11. 1001. 2001.30 00.04330. 04720. 0512
C o rner to Ball A1 Distance Along D S21.0001. 1001.20 00.03940. 04330. 047 2
Package HeightA--1.400--0.0551
Ball HeightA10.200--0.0079-Package Body ThicknessA2-1.070--0.0421Ball (Lead) Widthb0.3250.3750.4250.01280.01480.0167
Package Body Length D10.90011.00011.1000.42910.43310.4370
Package Body Width E10.90011.00011.1000.42910.43310.4370
Pitch e-0.800--0.0315Ball (Lead) Count N-88--88Seating Plane CoplanarityY--0.100--0.0039
Corner to Ball A1 Distance A long E S12.6002.7002.8000.10240.10630.1102
Corner to Ball A1 Distance A long D S21.0001.1001.2000.03940.04330.0472
512-Mbit: A[ 25 :1 ].
See Table 5 on page22 and Figure 10 on p age23 for 512-Mbit addressing.
DATA INPUT/OUTPUTS : Inputs data and commands during write cycles; outputs dat a during
memory, Status Register, Protection Register, and Read Configuration Register reads. Data balls
float when the CE# or OE# are deasserted. Data is in ternally latched during writes.
ADDRESS VALID: Active low input. During synchronous read operations, addresses are latched on
the rising edge of ADV#, or on the next valid CLK edge with ADV# low, whichever occurs first.
In asynchronous mode, the address is latched when ADV# going high or continuously flows through
if ADV# is held low.
WARNING: Designs not using ADV# must tie it to VSS to allow addresses to flow through.
FLASH CHIP ENABLE: Active low input. CE# low selects the associated flash memory die. When
asserted, f lash internal control logic, i nput buffers, decoders, and sen s e amplifiers are active. When
deasserted, the associated flash die is deselected, power is reduced to standby lev els, data and
WAIT outputs are placed in high-Z state.
WARNING: All chip enables must be high when device is not in use.
CLOCK: Synchronizes the device with the syste m’s bus frequency in synchronous-read mode.
During synchronous read operations, addresses ar e 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.
OUTPUT ENABLE: Active low input. OE# low enables the device’s output data buffers during read
cycles. OE# high places the data outputs and W AIT in High-Z.
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: 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 V
when CE# and OE# are VIL. WAIT is high-Z if CE# or OE# is VIH.
V
OH
• In synchronous arr ay or non-array read modes, WAIT indicates invalid data when asserted and
valid data when deasserted.
• In asy n ch ro nous page mo de , an d al l w rite modes, WAIT is de a s se rt e d .
WRITE ENABLE: Active low input. WE# controls writes to the device. Address and data are latc hed
on the rising edge of WE#.
WRITE PROTECT: Active low input. WP# low enables the lock-down mechanism. Blocks in lockdown cannot be unlocked with the Unlock command. WP# high overrides the lock-down function
enabling blocks to be erased or programmed using software commands.
Erase and Progr am Power: A valid voltage on this pin all ows erasing or progr amming. Memory
level of V
IH
PP
≤ V
contents cannot be altered when V
should not be attempted.
= VCC for in-system prog r am and er ase oper at ions. To accommodate resist or o r di ode dr op s
Set V
PP
from the syste m supply, the V
min to perform in-system flash modif ication. VPP may be 0 V during read operations.
can be applied to main blocks for 1000 cy cles maximum and to par ameter blocks for 2500
V
PPH
VPP can be connected to 9 V for a cumulative total not to ex ceed 80 hours. Extended use of
cycles.
this pin at 9 V may reduce block cycling capabili ty.
. Block erase and program at invalid VPP voltages
PPLK
can be as low as V
PP
Device Core Power Supply: Core (logic) source voltage. Writes to the flash array are inhibited when
≤ V
V
CC
. Operations at invalid VCC voltages should not be attempted.
Table 3. TSOP and Easy BGA Signal Descriptions (Sheet 2 of 2)
SymbolTypeName and Function
VCCQPowerOutput Power Supply: Output-driver source voltage.
VSSPowerGround: Con nect to system ground. Do not float any VSS connection.
RFU—
DU—Do Not Use: Do not connect to any other signal, or power supply; must be left floating.
NC—No Connect: No internal connection; can be driven or floated.
Reserved for Fu ture Use: Reserve d by In tel f or fu ture de vice f uncti onali ty and enh ancemen t. T hese
should be treated in the same way as a Do Not Use (DU) signal.
Table 4. QUAD+ SCSP Signal Descriptions (Sheet 1 of 2)
512-Mbit: A[24:0].
See Table 6 on page 22, Figure 11 on page23, and Figure 12 on page 23 for 512-Mbit and 1-Gbit
addressing.
DA TA INPUT/OUTPUTS: Inputs data and command s dur in g w rit e cy c le s ; ou tp uts data dur i n g
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.
ADDRESS VALID: Active low input. During synchronous re ad operations, addresses are latched on
the rising edge of ADV#, or on the next valid CLK edge wit h AD V# low, whichever occurs first.
In asynchronous mode, the address is latched when ADV# going high or continuously flows through
if ADV# is held lo w.
WARNING: Designs not using ADV# must tie it to VSS to allow addresses to flow through.
FLASH CHIP ENABLE: Active low input . CE# low selects the associated flash memory die. When
asserted, flash internal control logic, input buffers, decod ers, 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.
See Table 6 on page 22 for CE# assignment definitions.
WARNING: All chip enables must be high when device is not in use.
CLOCK: Synchronizes the device with the system’s bus frequency in synchronous-read mode.
During synchronous read operations, addresses are latched on the rising edge of ADV#, or on t he
next valid CLK edge with ADV# low, whichever occurs first.
WARNING: Designs not using CLK for synchronous read mode must tie it to VCCQ or VSS.
OUTPUT ENABLE: Active low input. OE# low enables the device’s output data buffers during read
cycles. OE# high places the data outpu ts and WAIT in High-Z.
F1-OE# and F2-OE # should be tied together for all densities.
RESET: Active low input. RS T# resets internal automation and inhibits write operations. This
provides data protection during power transitions. RST# high enables normal operation. Exit from
reset places th e device in asynchronous read array mode.
WAIT: Indicates data valid in synchronous array or non-ar ray burst reads. Read C onfiguration
Register bit 10 (RCR[10], WT) determines its po larity when asserted. WAIT’s active output is V
when CE# and OE# are VIL. WAIT is high-Z if CE # or O E# is VIH.
V
OH
• In synchronous array or non-array read modes, WAIT indicates inva lid data when asserted and
valid data when deasserted.
• In asynchronous page mode, and all w rite modes, WAI T is deasserted.
WRITE ENABLE: Active low in put. WE# controls writes to the device. Address and data are latched
on the rising edg e of WE#.
Table 4. QUAD+ SCSP Signal Descriptions (Sheet 2 of 2)
SymbolTypeName and Func tio n
WP#Input
VPP
Power/
lnput
VCCPower
VCCQPowerOutput Power Supply: Output-driver source voltage.
VSSPower Ground: Connect to system ground. Do not float any VSS connection.
RFU—
DU—Do Not Use: Do not connect to any other signal, or power supply; must be left floating.
NC—No Connect: No internal connection; can be driven or floated.
WRITE PROTECT: Active low input. WP# low enables the lock-down mechanism. Blocks in lockdown cannot be unlocked with the Unlock command. WP# high overrides the lock-down function
enabling blocks to be erased or programmed using software commands.
Erase and Progr am Power: A valid voltage on this pin all ows erasing or progr amming. Memory
level of V
IH
PP
≤ V
contents cannot be altered when V
should not be attempted.
= VCC for in-system prog r am and er ase oper at ions. To accommodate resist or o r di ode dr op s
Set V
PP
from the syste m supply, the V
min to perform in-system flash modif ication. VPP may be 0 V during read operations.
can be applied to main blocks for 1000 cy cles maximum and to par ameter blocks for 2500
V
PPH
VPP can be connected to 9 V for a cumulative total not to ex ceed 80 hours. Extended use of
cycles.
this pin at 9 V may reduce block cycling capabili ty.
. Block erase and program at invalid VPP voltages
PPLK
can be as low as V
PP
min. VPP must remain abov e V
PPL
Device Core Power Supply: Core (logic) source voltage. Writes to the flash array are inhibited when
≤ V
V
CC
. Operations at invalid VCC voltages should not be attempted.
LKO
Reserved for Future Use: Reserved by Intel for fut ure devi ce fun ctional ity a nd enha ncement. These
should be treated in the same way as a Do Not Use (DU) signa l.
PPL
4.3SCSP Configurations
Table 5. Stacked Easy BGA Chip Select Logic
Stack Combination
1-dieF1-CE#2-dieF1-CE# + A25 (V
Table 6. QUAD+ SCSP Chip Select Logic
Stack
Combination
1-dieF1-CE#--2-dieF1-CE# + A24 (V
4-dieF1-CE# + A24 (V
Warning:Stressing the device beyond the “Absolute Maximum Ratings” may cause permanent damage.
These are stress ratings only.
ParameterMaximum RatingNotes
Temperat ur e under bias–40 °C to +85 °C1
Storage temperatur e–65 °C to +125 °C
Voltage on any signal (except VCC, VPP)–0.5 V to +4.1 V2
VPP voltage–0.2 V to +10 V2,3,4
VCC voltage–0.2 V to +2.5 V2
VCCQ voltage–0.2 V to +4.1 V2
Output short circuit current100 mA5
Notes:
1.Temperature for 1-Gbit SCSP is –30 °C to +85 °C.
2.Voltages shown are specifie d with respect to V
signals and –0.2V on V
periods < 20 ns. Maximum DC voltage on V
overshoot to V
+ 0.5V, which, during transitions, may overshoot to V
is V
3.Maximum DC voltage on V
4.Program/erase voltage is typically 1.7 V – 2.0 V. 9.0 V can be applied for 80 hours maximum total, to
5.Output shorted for no mor e than one second. No more than one output shorted at a time.
CCQ
any blocks for 1000 cycles maximum. 9.0 V program/erase voltage may reduce block cycling
capability.
+ 2.0 V for periods < 20 ns. Maximum DC voltage on input/output signals and V
CC
, V
CC
, and VPP. During transitions, this level may undershoot to –2.0 V for
Table 16. AC Read Specifications for 64/128-Mbit Densities (Sheet 1 of 2)
NumSymbolParameterMinMaxUnitNotes
Asynchronous Specificati ons
R1t
R2
R3
R4
R5t
R6t
R7t
R8t
R10t
R11t
R12t
R13t
R15t
R16
R17
AVAV
t
AVQV
t
ELQV
t
GLQV
PHQV
ELQX
GLQX
EHQZ
GHQZ
EHEL
ELTV
EHTZ
GLTV
t
GLTX
t
GHTZ
OH
Latching S pecifications
R101t
R102t
R103t
R104t
R105t
R106t
R108t
R111t
AVVH
ELVH
VLQV
VLVH
VHVL
VHAX
APA
phvh
Clock Specif ica t i on s
R200f
R201t
R202t
R203t
CLK
CLK
CH/CL
FCLK/RCLK
Synchronous Specifications
R301t
R302t
R303t
R304t
CHQV
AVCH/L
VLCH/L
ELCH/L
/ t
Read cycle time85-ns
Address to output valid-85ns
CE# low to output valid-85ns
OE# low to output valid-25ns1,2
RST# high to output valid-150ns1
CE# low to output in low-Z0-ns1,3
OE# low to output in low-Z0-ns1,2, 3
CE# high to output in high-Z-24ns
OE# high to output in high-Z-24ns
Output hold from first occurring address, CE#, or OE# change0-ns
CE# pulse width high20-ns
CE# low to W A IT valid-17ns
CE# high to WAIT high-Z-20ns1,3
OE# low to WAIT vali d-17ns1
OE# low to WAIT in low-Z0-ns
OE# high to WAIT in high-Z-20ns
Address setup to ADV# high10-ns
CE# low to ADV# high10-ns
ADV# low to output valid-85ns
ADV# pulse width low10-ns
ADV# pulse width high10-ns
Address hold from ADV# high9-ns1,4
Page address access-25ns
RST# high to ADV# high30-ns
CLK frequency-40MHz
CLK period25-ns
CLK high/low time5-ns
CLK fall/ri se ti me-3ns
Address setup to CLK9-ns
ADV# low setup to CLK9-ns
CE# low setup to CLK9-ns
CLK to output valid-20ns
Table 16. AC Read Specifications for 64/128-Mbit Densities (Sheet 2 of 2)
NumSymbolParameterMinMaxUnitNotes
R305t
R306t
R307t
R311t
R312t
CHQX
CHAX
CHTV
CHVL
CHTX
Output hold from CLK3-ns1,5
Address hold from CLK10-ns1,4,5
CLK to WAIT valid-20ns1,5
CLK Valid to ADV# Setup3-ns1
WAIT Hold from CLK3-ns1,5
NOTES:
1.See Figure 13, “A C Inpu t/ Out pu t Ref erenc e Waveform” on p age33 for timing measurements and max allowable input
slew rate.
– t
2.OE# may be delayed by up to t
3.Sampled, not 100% tested.
ELQV
4.Address hold in synchr onous burst mode is t
5.Applies only to subsequent synchronou s reads.
after CE#’s falling edge without impact to t
GLQV
CHAX
or t
, whichever timing specification is satisfied first.
VHAX
ELQV
.
6.See your local Intel representative for designs requiring higher than 40 MHz synchronous operation.
Table 17. AC Read Specifications for 256/512-Mbit and 1-Gbit Densities (Sheet 1 of 2)
NumSymbolParameterSpeedMinMaxUnitNotes
Asynchronous Specifications
R1t
R2
R3
R4
R5t
R6t
R7t
R8t
R10t
R11t
R12t
R13t
R15t
R16
R17
AVAV
t
AVQV
t
ELQV
t
GLQV
PHQV
ELQX
GLQX
EHQZ
GHQZ
EHEL
ELTV
EHTZ
GLTV
t
GLTX
t
GHTZ
OH
Read cycle time
Address to output valid
CE# low to output valid
OE# low to output valid-25ns1,2
RST# high to output valid-150ns1
CE# low to output in low-Z0-ns1,3
OE# low to output in low-Z0-ns1,2,3
CE# high to output in high-Z-24ns
OE# high to output in high-Z-24ns
Output hold from first occurring address, CE#, or OE# change0-ns
CE# pulse width high20-ns
CE# low to WAIT val i d-17ns
CE# high to WAIT high-Z-20ns1,3
OE# low to WAIT valid-17ns1
OE# low to WAIT in low-Z0-ns
OE# high to WAIT in high-Z-20ns
Latching Specifications
Vcc = 1.8 V
Vcc = 1.7 V
Vcc = 1.8 V
Vcc = 1.7 V
Vcc = 1.8 V
Vcc = 1.7 V
Figure 19. Synchronous Single-Word Array or Non-array Read Timing
R102
R306R301
R2
R106R101
R3
R4
R8
R9R7
R17R307R15
R312
R305R304
CLK [ C]
ddress [A]
R105R105
ADV# [V]
CE# [ E ]
OE# [G]
WAIT [T]
Data [D/Q]
1.WAIT is dri ven per OE # a ssert io n duri ng sync hron ous ar ray or non- a rra y rea d, a nd can be co nf igu red to
R303
R104
R104
assert either during or one dat a 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 20. Continuous Burst Read, showing an Output Delay Timing
R301
R302
CLK [C]
R2
R101
ddress [A]
R106
R105R105
ADV# [V]
R303
R102
R3
CE# [E]
OE# [G]
R312R307R15
WAIT [T]
R304
R4
R7
Data [D/Q]
R304R304R304R306
R305R305R305R305
Notes:
1.WAIT is dr iven per OE# ass er ti on du r ing sy nch ro no us ar ray o r no n-ar ray read , and ca n b e conf i gure d t o
assert either during or one data cycle before valid data.
2.At the end of Word Line; the delay incur red when a burst access crosses a 16-word boundary and the
starting address is not 4-word boundary aligned.
Note: WAIT shown deasserted and High-Z per OE# deassertion during write operation (RCR[10]=0, Wait asserted low). Clock is
ignored during write operati on.
Figure 26. Write-to-Synchronous Read Timing
R302
R301
CLK
ddress [A]
R104
W19
W20
R11
R11
R104
R303
ADV#
CE# [E}
WE# [W]
OE# [G]
WAIT [T]
Data [D/Q]
RST# [P]
W2
W3W3
W4
W1
W6
W18
W7
DQQ
R306W8W5
R106
Note: WAIT shown deasserted and High-Z per OE# deassertion during write operation (RCR[10]=0, Wait asserted low).
Power supply sequencing is not required if VCC, VCCQ, and VPP are connected together; If
VCCQ and/or VPP are not connected to the VCC supply, then V
applying V
Power supply transitions should only occur when RST# is low. This protects the device from
accidental programming or erasure during power transitions.
8.2Reset 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.
and VPP. Device inputs should not be driven before supply voltage equals V
CCQ
should attain V
CC
CCMIN
before
CCMIN
.
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.
Num SymbolParameterMinMaxUnitNotes
P1 t
PLPH
P2 t
PLRH
P3 t
VCCPHVCC
Notes:
1.These specifications are valid for all device versions (packages and speeds).
2.The device may reset if t
3.Not applicable if RST# is tied to Vcc.
4.Sampled, but not 100% tested.
5.If RST# is tied to the V
6.If RST# is tied to any supply/signal with V
V
7.Reset completes within t
RST# pulse width low 100-ns1,2,3,4
RST# low to device reset during erase-25
RST# low to device reset during program-251,3,4,7
Power valid to RST# de-assertion (high)60-1,4,5,6
until VCC ≥ V
CC
is < t
PLPH
supply, device will not be ready until t
CC
.
CCMIN
if RST# is asserted while no erase or program operatio n is executing.
PLPH
MIN, but this is no t guaranteed.
PLPH
voltage levels, the RST# input voltage must not exceed
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.
P2
IH
IL
P2R5
IH
IL
P3
CC
Abort
Complete
Abort
Complete
R5
®
Because Intel
Multi-Level Cell (MLC) flash memory devices draw their power from VCC, VPP,
and VCCQ, each power connection should have a 0.1 µF ceramic capacitor to ground. Highfrequency, 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.
This section provides an overview of device operations. The system CPU provides control of all insystem read, write, and erase operations of the device via the system bus. The on-chip Write State
Machine (WSM) manages all block-erase and word-program algorithms.
Device commands are written to the Command User Interface (CUI) to control all flash memory
device operations. The CUI does not occupy an addressable memory location; it is the mechanism
through which the flash device is controlled.
9.1Bus 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 V
).
be V
IL
; CE# must
IH
Bus cycles to/from the P30 device conform to standard microprocessor bus operations. Table 19
summarizes the bus operations and the logic levels that must be applied to the device control signal
inputs.
Table 19. Bus Operations Summary
Bus OperationRST#CLKADV#CE#OE#WE#WAITDQ[15:0] Notes
To perform a read operation, RST# and WE# must be deasserted while CE# and OE# are asserted.
CE# is the device-select control. When asserted, it enables the flash memory device. OE# is the
data-output control. When asserted, the addressed flash memory data is driven onto the I/O bus.
See Section 10.0, “Read Operations” on page 53 for details on the available read modes, and see
Section 14.0, “Special Read States” on page 75 for details regarding the available read states.
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 20, “Command Bus Cycles” on page 50 shows the bus cycle
sequence for each of the supported device commands, while Table 21, “Command Codes and
Definitions” on page 51 describes each command. See Section 7.0, “AC Characteristics” on
page 33 for signal-timing details.
1-Gbit P30 Family
Note:Write operations with invalid V
be attempted.
9.1.3Output Disable
When OE# is deasserted, device outputs DQ[15:0] are disabled and placed in a high-impedance
(High-Z) state, WAIT is also placed in High-Z.
9.1.4Standby
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, I
5 µs after CE# is deasserted. During standby, average current is measured over the same time
interval 5 µs after CE# is deasserted.
When the device is deselected (while CE# is deasserted) during a program or erase operation, it
continues to consume active power until the program or erase operation is completed.
9.1.5Reset
As with any automated device, it is important to assert RST# when the system is reset. When the
system comes out of reset, the system processor attempts to read from the flash memory if it is the
system boot device. If a CPU reset occurs with no flash memory reset, improper CPU initialization
may occur because the flash memory may be providing status information rather than array data.
Flash memory devices from Intel allow proper CPU initialization following a system reset through
the use of the RST# input. RST# should be controlled by the same low-true reset signal that resets
the system CPU.
and/or VPP voltages can produce spurious results and should not
CC
, is the average current measured over any 5 ms time interval,
CCS
After initial power-up or reset, the device defaults to asynchronous Read Array, and the Status
Register is set to 0x80. Asserting RST# de-energizes all internal circuits, and places the output
drivers in High-Z. When RST# is asserted, the device shuts down the operation in progress, a
process which takes a minimum amount of time to complete. When RST# has been deasserted, the
device is reset to asynchronous Read Array state.
Note:If RST# is asserted during a program or erase operation, the operation is terminated and the
memory contents at the aborted location (for a program) or block (for an erase) are no longer valid,
because the data may have been only partially written or erased.
When returning from a reset (RST# deasserted), a minimum wait is required before the initial read
access outputs valid data. Also, a minimum delay is required after a reset before a write cycle can
be initiated. After this wake-up interval passes, normal operation is restored. See Section 7.0, “AC
Characteristics” on page 33 for details about signal-timing.
Device operations are initiated by writing specific device commands to the Command User
Interface (CUI). See Table20, “Com mand Bus C yc l e s ” on page50. 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.
1.First command cycle addr ess should be the same as the operation’s target address.
2.ID = Identifier data.
3.The second cycle of the B uf f er ed Pr ogr am Comma nd i s t he word co unt of the data to be loaded i nt o t he w rit e bu ff er. This
4.The confirm command (0xD0) is followed by the buffer data.
Program Protection Register2WritePRA0xC0WritePRAPD
Program Lo c k R e gi ster 2WriteLRA0xC0WriteLRALRD
Program Read Configuration
Register
DBA = Device Base Address (NOTE: needed for 2 or more die stacks)
IA = Identifi c ation code address offset.
QA = CFI Query address offset.
WA = Word address of memory location to be written.
BA = Address within the block.
PRA = Protection Register address.
LRA = Lock Register address.
RCD = Read Configuration Register data on A[15:0].
QD = Query da ta 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.
is followed by up to 32 words of data.Then the confirm command (0xD0) is issued, triggering the array programming
operation.
Bus
Cycles
2WriteRCD0x60WriteRCD0x03
First Bus Cy cl eSecond B us Cyc le
OperAddr
(1)
Data
(2)
OperAddr
(1)
Data
(2)
9.3Command Definitions
Valid device command codes and descriptions are shown in Table 21.
Table 21. Command Codes and Definitions (Sheet 1 of 2)
ModeCodeDevice ModeDescription
0xFF Read ArrayPlaces the device in Read Array mode. Array data is output on DQ[15:0].
0x70 Read Status Register
Read
Write0x40Word Program Setup
Read Device ID
0x90
or Configurat ion
Register
0x98 Read Query
0x50 Clear Status Register
Places the device in Read Status Register mode. The device enters this mode
after a program or erase command is issued. Status Register data is output on
DQ[7:0].
Places device in Read Device Identifier mode. Subsequent reads output
manufacturer/device codes, C onfiguration Register data, Block Lock status, or
Protection Register data on DQ[15:0].
Places the devi ce in Read Query mode. Subsequent reads output Common
Flash Interface information on DQ[7:0].
The WSM can only set Status Register error bits. The Clear Status Register
command is used to clear the SR error bits.
First cycle of a 2- cycle programming command; prepares the CUI for a write
operation. On the next write cycle, the address and data are latched and the
WSM executes the programming algorithm at the addressed location. During
program operations, the device responds only to Read Status Register and
Program Suspend commands. CE# or OE# must be toggled to update the
St atus Reg ister in asynchro nous re ad. CE# or ADV# must be t oggle d to update
the Status Register Dat a for synchronous Non-array reads. The Read Array
command must be issued to read array data after progra mming has finished.
Table 21. Command Codes and Definitions (Sheet 2 of 2)
ModeCodeDevice ModeDescription
Alternate Word
Write
Erase
Suspend
Block Locking/
Unlocking
Protection0xC0
Configuration
0x10
Program Setup
0xE8 Buffered Program
Buffered Program
0xD0
Confirm
0x80BEFP Setup
0xD0 BEFP Confirm
0x20Block Erase Setup
0xD0 Block Erase Confirm
Program or Erase
0xB0
Suspend
0xD0 Suspend Resume
0x60 Lock Block Setup
0x01Lock Block
0xD0 Unlock Block
0x2F Lock-Down Block
Program Protection
Register Setup
Read Configur ation
0x60
Register Setup
Read Configur ation
0x03
Register
Equivalent to the Word Program Setup command, 0x40.
This comm a nd lo ad s a variable num b er of words up to th e bu ffer s iz e of 32
words ont o th e pro g r am bu ffer.
The confirm comman d is Issued after the data streaming for writing into the
buffer is done. This instructs the WSM to perform the Buffered Program
algorithm, wr iting the data from the buffer to the flash memory array.
First cycle of a 2-c ycle command; initiates Buffered Enhanced Factory
Program mode (BEFP). The CUI then waits for the BEFP Confirm command,
0xD0, that initiates the BEFP algorithm. All other commands ar e ignored when
BEFP mode begins.
If the previous c omman d w as BE FP Se tu p (0x8 0), t he CUI latch es t he add ress
and data, and prepares the device for BEFP mode.
First cycle of a 2-cycle command; prep ares the CUI for a blo ck-erase
operation. The W SM 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[4] and SR[5], and
places the device in read status register mode.
If the first c ommand was Block Erase Setup (0x20), the CUI latches the
address and data, and the WSM erases the addressed block. During blockerase opera tions, the device responds only to Read Status Regis ter 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
Sta tus Register Dat a for synchronous Non-array reads
This command issued to any device address initiates a sus pend of the
currently-executing program or block erase operation. The Status Register
indicates successful suspend operation by setting either SR[2] (progr am
suspended) or SR[6] (erase suspended), along with SR[7] (ready). The Write
Sta te Machine re mains in the sus pend mode r egardle ss of contro l signa l state s
(except for RST# asserted).
This command issued t o any devi ce add r ess resu mes the su spen ded progr am
or block-erase operation.
First cycle of a 2-cyc le c omma nd; pre p ares t he CUI f or bl ock lo ck co nfig ur atio n
changes. If the next command is not Block Lock (0x01), Block Unlock (0xD0),
or Block Lock-Do wn (0x2F ), t he C UI se ts Status R egi ster bi ts S R[4] and SR [5] ,
indicating a command sequence error.
If the previous command was Block Lock Setup ( 0x60), the add ressed block is
locked.
If the previous command was Block Lock Setup ( 0x60), the add ressed block is
unlocked. If the addressed block is in a lock-down state, the operation has no
effect.
If the previous command was Block Lock Setup ( 0x60), the add ressed block is
locked down.
First cycle of a 2 -cycl e command; prep a res th e d evi ce f or a P rot ectio n Regi ste r
or Lock Register program operation. The second cycle latches the register
address and dat a, and start s the programming al gorithm
First cycle of a 2-cycle command; prep ares the CUI for devi ce read
configuration. If the Set Read Configuration Register command (0x03) is not
the next command, the CUI sets Status Register bits SR[4] and SR[5],
indicating a command sequence error.
If the previous command was Read Configuration Register Setup (0x60), the
CUI latches t he add ress and wr it es A[15 :0 ] to the R e ad Co nf ig urat io n Reg is te r.
Following a Configure Read Configuration Register command, subsequent
read operations access array data.
The device supports two read modes: asynchronous page mode and synchronous burst mode.
Asynchronous page mode is the default read mode after device power-up or a reset. The Read
Configuration Register must be configured to enable synchronous burst reads of the flash memory
array (see Section 10.3, “Read Configuration Register” on page 54).
The device can be in any of four read states: Read Array, Read Identifier, Read Status or Read
Query. Upon power-up, or after a reset, the device defaults to Read Array. To change the read state,
the appropriate read command must be written to the device (see Section 9.2, “Device Commands”
on page 50). See Section 14.0, “Special Read States” on page 75 for details regarding Read Status,
Read ID, and CFI Query modes.
The following sections describe read-mode operations in detail.
10.1Asynchronous Page-Mode Read
Following a device power-up or reset, asynchronous page mode is the default read mode and the
device is set to Read Array. However, to perform array reads after any other device operation (e.g.
write operation), the Read Array command must be issued in order to read from the flash memory
array.
1-Gbit P30 Family
Note:Asynchronous page-mode reads can only be performed when Read Configuration Register bit
RCR[15] is set (see Section 10.3, “Read Configuration Register” on page 54).
To perform an asynchronous page-mode read, an address is driven onto the Address bus, and CE#
and ADV# are asserted. WE# and RST# must already have been deasserted. WAIT is deasserted
during asynchronous page mode. ADV# can be driven high to latch the address, or it must be held
low throughout the read cycle. CLK is not used for asynchronous page-mode reads, and is ignored.
If only asynchronous reads are to be performed, CLK should be tied to a valid V
signal can be floated and ADV# must be tied to ground. Array data is driven onto DQ[15:0] after
an initial access time t
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.
delay. (see Section 7.0, “AC Characteristics” on page 33).
AVQ V
level, WAIT
IH
10.2Synchronous Burst-Mode Read
To perform a synchronous burst- read, an initial address is driven onto the Address bus, and CE#
and ADV# are asserted. WE# and RST# must already have been deasserted. ADV# is asserted, and
then deasserted to latch the address. Alternately, ADV# can remain asserted throughout the burst
access, in which case the address is latched on the next valid CLK edge while ADV# is asserted.
During synchronous array and non-array read modes, the first word is output from the data buffer
on the next valid CLK edge after the initial access latency delay (see Section 10.3.2, “Latency
Count” on page 55). Subsequent data is output on valid CLK edges following a minimum delay.
However, for a synchronous non-array read, the same word of data will be output on successive
clock edges until the burst length requirements are satisfied. Refer to the following waveforms for
more detailed information:
• Figure 19, “Synchronous Single-Word Array or Non-array Read Timing” on page 39
• Figure 20, “Continuous Burst Read, showing an Output Delay Timing” on page 40
The Read Configuration Register (RCR) is used to select the read mode (synchronous or
asynchronous), and it defines the synchronous burst characteristics of the device. To modify RCR
settings, use the Configure Read Configuration Register command (see Section 9.2, “Device
Commands” on page 50).
RCR contents can be examined using the Read Device Identifier command, and then reading from
offset 0x05 (see Section 14.2, “Read Device Identifier” on page 76).
The RCR is shown in Table 22. The following sections describe each RCR bit.
Table 22. Read Configuration Register Description (Sheet 1 of 2)
Read Configuration Register (RCR)
Data
Read
Mode
13:11Latency Count (LC[2:0])010 =Code 2
RESLatency Count
RMRLC[2:0]WPDHWDBSCERRBWBL[2:0]
1514131211109876543210
BitNameDescription
15Read Mode (RM)0 = Synchronous burst-mode r ead
14Reserved (R)Reserved bits should be cleared (0)
10Wait Polarity (WP)0 =WAIT signal is active low
9Data Hold (DH)0 =Data held for a 1-clock data cycle
8Wait Delay (WD)0 =WAIT deasserted with valid data
7Bu rs t S e qu en c e (BS)0 =Re s erv ed
6Clock Edge (CE)0 = Falling edge
5:4Reserved (R)Reserved bits should be cleared (0)
Table 22. Read Configuration Register Description (Sheet 2 of 2)
3Burst Wrap (BW)0 =Wrap; Burst accesses wrap within burst length set by BL[2:0]
1 =No Wrap; Burst accesses do not wrap w ithin burst length (default)
2:0Burst Length (BL[2:0])001 =4-word bur st
010 =8-word burst
011 =16-word burst
111 =Continuous-word burst (default)
(Other bit settings are reserved)
Note: Latency Code 2, Dat a Hold for a 2-cl ock d ata cycl e (D H = 1) WAIT must be deass er t ed with v al id d at a (W D =
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 supp orted.
10.3.1Read Mode
The Read Mode (RM) bit selects synchronous burst-mode or asynchronous page-mode operation
for the device. When the RM bit is set, asynchronous page mode is selected (default). When RM is
cleared, synchronous burst mode is selected.
10.3.2Latency Count
The Latency Count bits, LC[2:0], tell the device how many clock cycles must elapse from the
rising edge of ADV# (or from the first valid clock edge after ADV# is asserted) until the first data
word is to be driven onto DQ[15:0]. The input clock frequency is used to determine this value.
Figure 28 shows the data output latency for the different settings of LC[2:0].
1-Gbit P30 Family
Synchronous burst with a Latency Count setting of Code 4 will result in zero WAIT state; however,
a Latency Count setting of Code 5 will cause 1 WAIT state (Code 6 will cause 2 WAIT states, and
Code 7 will cause 3 WAIT states) after every four words, regardless of whether a 16-word
boundary is crossed. If RCR[9] (Data Hold) bit is set (data hold of two clocks) this WAIT condition
will not occur because enough clocks elapse during each burst cycle to eliminate subsequent W AIT
states.
Refer to Table 23, “LC and Frequency Support” on page 56 for Latency Code Settings.
Figure 29. Exa m ple Latency Count Setting using Code 3
012
CLK
CE#
ADV#
1-Gbit P30 Family
t
34
Data
A[MAX:0]
D[15:0]
10.3.3WAIT Polarity
The WAIT Polarity bit (WP), RCR[10] determines the asserted level (VOH or VOL) of WAIT.
When WP is set, WAIT is asserted high (default). When WP is cleared, WAIT is asserted low.
WAIT changes state on valid clock edges during active bus cycles (CE# asserted, OE# asserted,
RST# deasserted).
10.3.3.1WAIT Signal Function
The WAIT signal indicates data valid when the device is operating in synchronous mode
(RCR[15]=0). The WAIT signal is only “deasserted” when data is valid on the bus.
When the device is operating in synchronous non-array read mode, such as read status, read ID, or
read query. The WAIT signal is also “deasserted” when data is valid on the bus.
WAIT behavior during synchronous non-array reads at the end of word line works correctly only
on the first data access.
Code 3
High-Z
Address
Data
R103
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
17, “Asynchronous Single-Word Read (ADV# Latch)” on page 38, and Figure 18, “Asynchronous
Page-Mode Read Timing” on page 39.
DatasheetIntel StrataFlash
Order Number: 306666, Revision: 00157
®
Embedded Memory (P30)April 2005
1-Gbit P30 Family
Table 24. WAIT Functionality Table
CE# = ‘1’, OE# = ‘X’ or CE# = ‘0’, OE# = ‘1’High-Z1
CE# =’0’, OE# = ‘0’Active1
Synchronous Array ReadsActive1
Synchronous Non-Ar r ay ReadsActive1
All Asynchronous Rea ds Deasserted1
All WritesHi gh- Z1,2
Notes:
1.
Active: WAIT is asserted until data becomes valid, then deassert s
2.When OE# = V
10.3.4Data 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”. Wh en DH
is set, output data is held for two clocks (default). When DH is cleared, output data is held for one
clock (see Figure 30). The processor’s data setup time and the flash memory’s clock-to-data output
delay should be considered when determining whether to hold output data for one or two clocks. A
method for determining the Data Hold configuration is shown below:
ConditionWAITNotes
during writes, WAIT = High-Z
IH
To set the device at one clock data hold for subsequent reads, the following condition must be
satisfied:
(ns) + t
t
CHQV
= Data set up to Clock (defined by CPU)
t
DATA
For example, with a clock frequency of 40 MHz, the clock period is 25 ns. Assuming
= 20 ns and t
t
CHQV
20 ns + 4 ns
The equation is satisfied and data will be available at every clock period with data hold setting at
one clock. If t
CHQV
must be used.
Figure 30. Data Hold Timing
CLK [C]
1 CLK
Data Ho ld
2 CLK
Data Ho ld
D[15:0] [Q]
D[15:0] [Q]
(ns) ≤ One CLK Period (ns)
DATA
= 4 ns. Applying these values to the formula above:
DATA
≤ 25 ns
(ns) + t
(ns) > One CLK Period (ns), data hold setting of 2 clock periods
The WAIT Delay (WD) bit controls the WAIT assertion-delay behavior during synchronous burst
reads. WAIT can be asserted either during or one data cycle before valid data is output on
DQ[15:0]. When WD is set, WAIT is deasserted one data cycle before valid data (default). When
WD is cleared, WAIT is deasserted during valid data.
10.3.6Burst Sequence
The Burst Sequence (BS) bit selects linear-burst sequence (default). Only linear-burst sequence is
supported. Table 25 shows the synchronous burst sequence for all burst lengths, as well as the
effect of the Burst Wrap (BW) setting.
The Clock Edge (CE) bit selects either a rising (default) or falling clock edge for CLK. This clock
edge is used at the start of a burst cycle, to output synchronous data, and to assert/deassert WAIT.
10.3.8Burst Wrap
The Burst Wrap (BW) bit determines whether 4-word, 8-word, or 16-word burst length accesses
wrap within the selected word-length boundaries or cross word-length boundaries. When BW is
set, burst wrapping does not occur (default). When BW is cleared, burst wrapping occurs.
When performing synchronous burst reads with BW set (no wrap), an output delay may occur
when the burst sequence crosses its first device-row (16-word) boundary. If the burst sequence’s
start address is 4-word aligned, then no delay occurs. If the start address is at the end of a 4-word
DatasheetIntel StrataFlash
Order Number: 306666, Revision: 00159
®
Embedded Memory (P30)April 2005
1-Gbit P30 Family
boundary, the worst case output delay is one clock cycle less than the first access Latency Count.
This delay can take place only once, and doesn’t occur if the burst sequence does not cross a
device-row boundary. WAIT informs the system of this delay when it occurs.
10.3.9Burst Length
The Burst Length bit (BL[2:0]) selects the linear burst length for all synchronous burst reads of the
flash memory array. The burst lengths are 4-word, 8-word, 16-word, and continuous word.
Continuous-burst accesses are linear only, and do not wrap within any word length boundaries (see
Table 25, “Burst Sequence Word Ordering” on page 59). When a burst cycle begins, the device
outputs synchronous burst data until it reaches the end of the “burstable” address space.
The device supports three programming methods: Word Programming (40h/10h), Buffered
Programming (E8h, D0h), and Buffered Enhanced Factory Programming (80h, D0h). See Section
9.0, “Device Operations” on page 48 for details on the various programming commands issued to
the device. The following sections describe device programming in detail.
Successful programming requires the addressed block to be unlocked. If the block is locked down,
WP# must be deasserted and the block must be unlocked before attempting to program the block.
Attempting to program a locked block causes a program error (SR[4] and SR[1] set) and
termination of the operation. See Section 13.0, “Security Modes” on page 69 for details on locking
and unlocking blocks.
The Intel StrataFlash® Embedded Memory (P30) is segmented into multiple Programming
Regions. Programming Regions are made up of 8 or 16 blocks depending on the density. The 64and 128-Mbit devices have 8 blocks per Programming Region, while the 256-Mbit has 16 blocks in
each Programming Region (see Table 26). See Section 4.4, “Memory Maps” on page 24 for
address ranges of each Programming Region per density.
Execute in Place (XIP) is defined as the ability to execute code directly from the flash memory.
XIP applications must partition the memory such that code and data are in separate programming
regions (see Table 26, “Programming Regions per Device” on page 61). Each Programming
Region should contain only code or data, and not both. The following terms define the difference
between code and data. System designs must use these definitions when partitioning their code and
data for the P30 device.
Code :Execution code ran out of the flash device on a continuous basis in the system.
Data :Information periodically programmed into the flash device and read back (e.g.
execution code shadowed and executed in RAM, pictures, log files, etc.).
11.1Word Programming
Number of Progr a mm i ng
Regions per Dev ic e
Word programming operations are initiated by writing the Word Program Setup command to the
device (see Section 9.0, “Device Operations” on page 48). This is followed by a second write to the
device with the address and data to be programmed. The device outputs Status Register data when
read. See Figure 40, “Word Program Flowchart” on page 85. V
the specified V
min/max values (nominally 1.8 V).
PPL
DatasheetIntel StrataFlash
Order Number: 306666, Revision: 00161
must be above V
PP
®
Embedded Memory (P30)April 2005
, and within
PPLK
1-Gbit P30 Family
During programming, the Write State Machine (WSM) executes a sequence of internally-timed
events that program the desired data bits at the addressed location, and verifies that the bits are
sufficiently programmed. Programming the flash memory array changes “ones” to “zeros”.
Memory array bits that are zeros can be changed to ones only by erasing the block (see Section
12.0, “Erase Operations” on page 67).
The Status Register can be examined for programming progress and errors by reading at any
address. The device remains in the Read Status Register state until another command is written to
the device.
Status Register bit SR[7] indicates the programming status while the sequence executes.
Commands that can be issued to the device during programming are Program Suspend, Read Status
Register, Read Device Identifier, CFI Query, and Read Array (this returns unknown data).
When programming has finished, Status Register bit SR[4] (when set) indicates a programming
failure. If SR[3] is set, the WSM could not perform the word programming operation because V
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.
PP
11.1.1Factory 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 V
PP
= V
. This can enable faster programming times during OEM
PPH
manufacturing processes. Factory word programming is not intended for extended use. See Section
5.2, “Operating Conditions” on page 30 for limitations when V
Note:When V
by a logic signal, V
PP
= V
, the device draws programming current from the VCC supply. If VPP is driven
PPL
must remain above V
PPL
the device draws programming current from the V
Connections” on page 66 shows examples of device power supply configurations.
11.2Buffered Programming
The device features a 32-word buffer to enable optimum programming performance. For Buffered
Programming, data is first written to an on-chip write buffer. Then the buffer data is programmed
into the flash memory array in buffer-size increments. This can improve system programming
performance significantly over non-buffered programming.
When the Buffered Programming Setup command is issued (see Section 9.2, “Device Commands”
on page 50), Status Register information is updated and reflects the availability of the buffer. SR[7]
indicates buffer availability: if set, the buffer is available; if cleared, the buffer is not available. To
retry, issue the Buffered Programming Setup command again, and re-check SR[7]. When SR[7] is
set, the buffer is ready for loading. (see Figure 42, “Buffer Program Flowchart” on page 87).
= V
PP
MIN to program the device. When VPP = V
PPL
supply. Figure 31, “Example VPP Supply
PP
PPH
.
PPH
,
On the next write, a word count is written to the device at the buffer address. This tells the device
how many data words will be written to the buffer, up to the maximum size of the buffer.
On the next write, a device start address is given along with the first data to be written to the flash
memory array. Subsequent writes provide additional device addresses and data. All data addresses
must lie within the start address plus the word count. Optimum programming performance and
lower power usage are obtained by aligning the starting address at the beginning of a 32-word
boundary (A[4:0] = 0x00). Crossing a 32-word boundary during programming will double the total
programming time.
After the last data is written to the buffer, the Buffered Programming Confirm command must be
issued to the original block address. The WSM begins to program buffer contents to the flash
memory array. If a command other than the Buffered Programming Confirm command is written to
the device, a command sequence error occurs and Status Register bits SR[7,5,4] are set. If an error
occurs while writing to the array, the device stops programming, and Status Register bits SR[7,4]
are set, indicating a programming failure.
When Buffered Programming has completed, additional buffer writes can be initiated by issuing
another Buffered Programming Setup command and repeating the buffered program sequence.
Buffered programming may be performed with V
PP
= V
Conditions” on page 30 for limitations when operating the device with V
PPL
or V
(see Section 5.2, “Operating
PPH
PP
= V
PPH
).
If an attempt is made to program past an erase-block boundary using the Buffered Program
command, the device aborts the operation. This generates a command sequence error, and Status
Register bits SR[5,4] are set.
If Buffered programming is attempted while V
is below V
PP
, Status Register bits SR[4,3] are
PPLK
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.3Buffered 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 43, “BEFP Flowchart”
on page 88). It uses a write buffer to spread MLC program performance across 32 data words.
Verification occurs in the same phase as programming to accurately program the flash memory cell
to the correct bit state.
A single two-cycle command sequence programs the entire block of data. This enhancement
eliminates three write cycles per buffer: two commands and the word count for each set of 32 data
words. Host programmer bus cycles fill the device’s write buffer followed by a status check. SR[0]
indicates when data from the buffer has been programmed into sequential flash memory array
locations.
Following the buffer-to-flash array programming sequence, the Write State Machine (WSM)
increments internal addressing to automatically select the next 32-word array boundary. This
aspect of BEFP saves host programming equipment the address-bus setup overhead.
With adequate continuity testing, programming equipment can rely on the WSM’s internal
verification to ensure that the device has programmed properly. This eliminates the external postprogram verification and its associated overhead.
DatasheetIntel StrataFlash
Order Number: 306666, Revision: 00163
®
Embedded Memory (P30)April 2005
1-Gbit P30 Family
11.3.1BEFP Requirements and Considerations
BEFP requirements:
• Case temperature: T
• V
within specified operating range
CC
• VPP driven to V
= 25 °C ± 5 °C
C
PPH
• Target block unlocked before issuing the BEFP Setup and Confirm commands
• The first-word address (WA0) for the block to be programmed must be held constant from the
setup phase through all data streaming into the target block, until transition to the exit phase is
desired
• WA0 must align with the start of an array buffer boundary
1
BEFP considerations:
• For optimum performance, cycling must be limited below 100 erase cycles per block
• BEFP programs one block at a time; all buffer data must fall within a single block
2
3
• BEFP cannot be suspended
• Programming to the flash memory array can occur only when the buffer is full
NOTES:
1.Word buffer boun daries in the array are det ermined by A[4:0] (0x00 thr ough 0x1F). The alignm ent start
point is A[4:0] = 0x00.
2.Some degradation in per fo rmance may occur if this limit is exceeded, but the internal algorithm
continues to work pr operly.
3.If the internal address count er increments beyond t he block's maximum addre ss, addressing wraps
around to the begi nning of the block.
4.If the number of words is les s th an 32, remaining locat ions must be filled with 0xFFFF.
4
11.3.2BEFP 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, V
level, etc.). If an error is detected, SR[4] is set and BEFP operation
PP
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 V
PP
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.3BEFP Program/Verify Phase
After the BEFP Setup Phase has completed, the host programming system must check SR[7,0] to
determine the availability of the write buffer for data streaming. SR[7] cleared indicates the device
is busy and the BEFP program/verify phase is activated. SR[0] indicates the write buffer is
available.
Two basic sequences repeat in this phase: loading of the write buffer, followed by buffer data
programming to the array. For BEFP, the count value for buffer loading is always the maximum
buffer size of 32 words. During the buffer-loading sequence, data is stored to sequential buffer
locations starting at address 0x00. Programming of the buffer contents to the flash memory array
starts as soon as the buffer is full. If the number of words is less than 32, the remaining buffer
locations must be filled with 0xFFFF.
Caution:The buffer must be completely filled for pr ogramming 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.4BEFP 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.4Program 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 41, “Program Suspend/Resume
Flowchart” on page 86).
DatasheetIntel StrataFlash
Order Number: 306666, Revision: 00165
®
Embedded Memory (P30)April 2005
1-Gbit P30 Family
When a programming operation is executing, issuing the Program Suspend command requests the
WSM to suspend the programming algorithm at predetermined points. The device continues to
output Status Register data after the Program Suspend command is issued. Programming is
suspended when Status Register bits SR[7,2] are set. Suspend latency is specified in Section 7.5,
“Program and Erase Characteristics” on page 45.
To read data from the device, the Read Array command must be issued. Read Array, Read Status
Register, Read Device Identifier, CFI Query, and Program Resume are valid commands during a
program suspend.
During a program suspend, deasserting CE# places the device in standby, reducing active current.
must remain at its programming level, and WP# must remain unchanged while in program
V
PP
suspend. If RST# is asserted, the device is reset.
11.5Program 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 41, “Program Suspend/Resume Flowchart” on page 86).
11.6Program Protection
When VPP = VIL, absolute hardware write protection is provided for all device blocks. If VPP is at
or below V
lock registers are not affected by the voltage level on V
even if V
Figure 31. Example VPP Supply Connections
• Factory Programming with V
• Complete write/Erase Protection w hen V
VPP=V
• Low Voltage and Factory Programming
, programming operations halt and SR[3] is set indicating a VPP-level error. Block
Flash erasing is performed on a block basis. An entire block is erased each time an erase command
sequence is issued, and only one block is erased at a time. When a block is erased, all bits within
that block read as logical ones. The following sections describe block erase operations in detail.
12.1Block Erase
Block erase operations are initiated by writing the Block Erase Setup command to the address of
the block to be erased (see Section 9.2, “Device Commands” on page 50). Next, the Block Erase
Confirm command is written to the address of the block to be erased. If the device is placed in
standby (CE# deasserted) during an erase operation, the device completes the erase operation
before entering standby.V
“Block Erase Flowchart” on page 89).
During a block erase, the Write State Machine (WSM) executes a sequence of internally-timed
events that conditions, erases, and verifies all bits within the block. Erasing the flash memory array
changes “zeros” to “ones”. Memory array bits that are ones can be changed to zeros only by
programming the block (see Section 11.0, “Programming Operations” on page 61).
must be above V
PP
1-Gbit P30 Family
and the block must be unlocked (see Figure 44,
PPLK
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 V
acceptable limits. SR[1] set indicates that the erase operation attempted to erase a locked block,
causing the operation to abort.
Before issuing a new command, the Status Register contents should be examined and then cleared
using the Clear Status Register command. Any valid command can follow once the block erase
operation has completed.
12.2Erase 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 41, “Program Suspend/Resume Flowchart” on page 86).
When a block erase operation is executing, issuing the Erase Suspend command requests the WSM
to suspend the erase algorithm at predetermined points. The device continues to output Status
Register data after the Erase Suspend command is issued. Block erase is suspended when Status
Register bits SR[7,6] are set. Suspend latency is specified in Section 7.5, “Program and Erase
Characteristics” on page 45.
was outside of its
PP
DatasheetIntel StrataFlash
Order Number: 306666, Revision: 00167
®
Embedded Memory (P30)April 2005
1-Gbit P30 Family
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 comp lete . Read Ar ray, Read Status Register, Read Dev ice Iden tif ier , CFI Que ry, and Er ase
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.
must remain at a valid level, and WP# must remain unchanged while in erase suspend. If
V
PP
RST# is asserted, the device is reset.
12.3Erase Resume
The Erase Resume command instructs the device to continue erasing, and automatically clears
status register bits SR[7,6]. This command can be written to any address. If status register error bits
are set, the Status Register should be cleared before issuing the next instruction. RST# must remain
deasserted (see Figure 41, “Program Suspend/Resume Flowchart” on page 86).
12.4Erase Protection
When VPP = VIL, absolute hardware erase protection is provided for all device blocks. If VPP is
below V
, erase operations halt and SR[3] is set indicating a VPP-level error.
The device features security modes used to protect the information stored in the flash memory
array. The following sections describe each security mode in detail.
13.1Block 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, V
(see Section 11.6, “Program Protection” on page 66 and Section 12.4, “Erase Protection” on
page 68).
The P30 device also offers four pre-defined areas in the main array that can be configured as OneTime 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.
1-Gbit P30 Family
data security can be used to inhibit program and erase operations
PP
13.1.1Lock Block
To lock a block, issue the Lock Block Setup command. The next command must be the Lock Block
command issued to the desired block’s address (see Section 9.2, “Device Commands” on page 50
and Figure 46, “Block Lock Operations Flowchart” on page 91). 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 V
may be modified and/or read even if V
13.1.2Unlock Block
The Unlock Block command is used to unlock blocks (see Section 9.2, “Device Commands” on
page 50). Unlocked blocks can be read, programmed, and erased. Unlocked blocks return to a
locked state when the device is reset or powered down. If a block is in a lock-down state, WP#
must be deasserted before it can be unlocked (see Figure 32, “Block Locking State Diagram” on
page 70).
13.1.3Lock-Down Block
A locked or unlocked block can be locked-down by writing the Lock-Down Block command
sequence (see Section 9.2, “Device Commands” on page 50). Blocks in a lock-down state cannot
be programmed or erased; they can only be read. However, unlike locked blocks, their locked state
cannot be changed by software commands alone. A locked-down block can only be unlocked by
issuing the Unlock Block command with WP# deasserted. To return an unlocked block to locked-
is at or below V
PP
PPLK
. The block lock bits
.
PP
DatasheetIntel StrataFlash
Order Number: 306666, Revision: 00169
®
Embedded Memory (P30)April 2005
1-Gbit P30 Family
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 32, “Block Locking
State Diagram” on page 70).
13.1.4Block Lock Status
The Read Device Identifier command is used to determine a block’s lock status (see Section 14.2,
“Read Device Identifier” on page 76). Data bits DQ[1:0] display the addressed block’s lock status;
DQ0 is the addressed block’s lock bit, while DQ1 is the addressed block’s lock-down bit.
Figure 32. Block Locking State Diagram
Power-Up/Res et
Notes:1. [a, b,c] repr e s ents [ WP# , DQ 1 , 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. DQ 0 = ‘1’, block is
lock e d.
4. Locked-down = Hardware + Software locked.
5. [011] states should be tracked by system software to determine difference between
Hardware Loc ked and Lo cked -D ow n s tates.
Locked
[X01]
Unlocked
[X00 ]
13.1.5Block Locking During Suspend
Locked-
4,5
Down
[011]
WP# Hardware Control
Software
Locked
[111][110]
Software Block Lock (0x60/0x01) or Software Block Unlock (0x60/0xD0)
Software Block Lock-Down (0x60/0x2F)
WP# hardware control
Hardware
Locked
[011]
Unlocked
5
Block lock and unlock changes can be performed during an erase suspend. To change block
locking during an erase operation, first issue the Erase Suspend command. Monitor the Status
Register until SR[7] and SR[6] are set, indicating the device is suspended and ready to accept
another command.
Next, write the desired lock command sequence to a block, which changes the lock state of that
block. After completing block lock or unlock operations, resume the erase operation using the
Erase Resume command.
Note:A Lock Block Setup command followed by any command other than Lock Block, Unlock Block,
or Lock-Down Block produces a command sequence error and set Status Register bits SR[4] and
SR[5]. If a command sequence error occurs during an erase suspend, SR[4] and SR[5] remains set,
even after the erase operation is resumed. Unless the Status Register is cleared using the Clear
Status Register command before resuming the erase operation, possible erase errors may be
masked by the command sequence error.
If a block is locked or locked-down during an erase suspend of the same block, the lock status bits
change immediately. However, the erase operation completes when it is resumed. Block lock
operations cannot occur during a program suspend. See Appendix A, “Write State Machine” on
page 78, which shows valid commands during an erase suspend.
13.2Selectable One-Time Programmable Blocks
Any of four pre-defined areas from the main array (the four 32 KB parameter blocks together as
one and the 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.
Please see your local Intel representative for details about the Selectable OTP implementation.
DatasheetIntel StrataFlash
Order Number: 306666, Revision: 00171
®
Embedded Memory (P30)April 2005
1-Gbit P30 Family
13.3Protection Registers
The device contains 17 Protection Registers (PRs) that can be used to implement system security
measures and/or device identification. Each Protection Register can be individually locked.
The first 128-bit Protection Register is comprised of two 64-bit (8-word) segments. The lower 64bit segment is pre-programmed at the Intel factory with a unique 64-bit number. The other 64-bit
segment, as well as the other sixteen 128-bit Protection Registers, are blank. Users can program
these registers as needed. When programmed, users can then lock the Protection Register(s) to
prevent additional bit programming (see Figure 33, “Protection Register Map” on page 73).
The user-programmable Protection Registers contain one-time programmable (OTP) bits; when
programmed, register bits cannot be erased. Each Protection Register can be accessed multiple
times to program individual bits, as long as the register remains unlocked.
Each Protection Register has an associated Lock Register bit. When a Lock Register bit is
programmed, the associated Protection Register can only be read; it can no longer be programmed.
Additionally, because the Lock Register bits themselves are OTP, when programmed, Lock
Register bits cannot be erased. Therefore, when a Protection Register is locked, it cannot be
unlocked.
The Protection Registers can be read from any address. To read the Protection Register, first issue
the Read Device Identifier command at any address to place the device in the Read Device
Identifier state (see Section 9.2, “Device Commands” on page 50). Next, perform a read operation
using the address offset corresponding to the register to be read. Table 29, “Device Identifier
Information” on page 77 shows the address offsets of the Protection Registers and Lock Registers.
Register data is read 16 bits at a time.
13.3.2Programming the Protection Registers
To program any of the Protection Registers, first issue the Program Protection Register command
at the parameter’s base address plus the offset to the desired Protection Register (see Section 9.2,
“Device Commands” on page 50). Next, write the desired Protection Register data to the same
Protection Register address (see Figure 33, “Protection Register Map” on page 73).
DatasheetIntel StrataFlash
Order Number: 306666, Revision: 00173
®
Embedded Memory (P30)April 2005
1-Gbit P30 Family
The device programs the 64-bit and 128-bit user-programmable Protection Register data 16 bits at
a time (see Figure 47, “Protection Register Programming Flowchart” on page 92). Issuing the
Program Protection Register command outside of the Protection Register’s address space causes a
program error (SR[4] set). Attempting to program a locked Protection Register causes a program
error (SR[4] set) and a lock error (SR[1] set).
13.3.3Locking the Protection Registers
Each Protection Register can be locked by programming its respective lock bit in the Lock
Register. To lock a Protection Register, program the corresponding bit in the Lock Register by
issuing the Program Lock Register command, followed by the desired Lock Register data (see
Section 9.2, “Device Commands” on page 50). The physical addresses of the Lock Registers are
0x80 for register 0 and 0x89 for register 1. These addresses are used when programming the lock
registers (see Table 29, “Device Identifier Information” on page 77).
Bit 0 of Lock Register 0 is already programmed at the factory, locking the lower, pre-programmed
64-bit region of the first 128-bit Protection Register containing the unique identification number of
the device. Bit 1 of Lock Register 0 can be programmed by the user to lock the user-programmable,
64-bit region of the first 128-bit Protection Register. When programming Bit 1 of Lock Register 0,
all other bits need to be left as ‘1’ such that the data programmed is 0xFFFD.
Lock Register 1 controls the locking of the upper sixteen 128-bit Protection Registers. Each of the
16 bits of Lock Register 1 correspond to each of the upper sixteen 128-bit Protection Registers.
Programming a bit in Lock Register 1 locks the corresponding 128-bit Protection Register.
Caution:After being locked, the Protection Registers cannot be unlocked.
The following sections describe non-array read states. Non-array reads can be performed in
asynchronous read or synchronous burst mode. A non-array read operation occurs as asynchronous
single-word mode. When non-array reads are performed in asynchronous page mode only the first
data is valid and all subsequent data are undefined. When a non-array read operation occurs as
synchronous burst mode, the same word of data requested will be output on successive clock edges
until the burst length requirements are satisfied.
Refer to the following waveforms for more detailed information:
• Figure 19, “Synchronous Single-Word Array or Non-array Read Timing” on page 39
14.1Read Status Register
To read the Status Register, issue the Read Status Register command at any address. Status Register
information is available to which the Read Status Register, Word Program, or Block Erase
command was issued. Status Register data is automatically made available following a Word
Program, Block Erase, or Block Lock command sequence. Reads from the device after any of these
command sequences outputs the device’s status until another valid command is written (e.g. Read
Array command).
1-Gbit P30 Family
The Status Register is read using single asynchronous-mode or synchronous burst mode reads.
Status Register data is output on DQ[7:0], while 0x00 is output on DQ[15:8]. In asynchronous
mode the falling edge of OE#, or CE# (whichever occurs first) updates and latches the Status
Register contents. However, reading the Status Register in synchronous burst mode, CE# or ADV#
must be toggled to update status data.
The Device Write Status bit (SR[7]) provides overall status of the device. Status register bits
SR[6:1] present status and error information about the program, erase, suspend, V
locked operations.
Table 28. Status Register Description (Sheet 1 of 2)
Stat us Register (SR)
Device
Write Status
DWSESSESPSVPPSPSSBLSBWS
76543210
BitNameDescription
7
6
Erase
Suspend
Status
Device Write Status
(DWS)
Erase Suspend Status
(ESS)
Erase
Status
Program
Status
0 = Device is busy; program or erase cycle in pr ogress; SR[0] valid.
1 = Device is ready; S R[ 6:1] are valid.
0 = Erase suspend not in effect.
1 = Erase suspend in effect.
V
PP
Status
Program
Suspend
Status
, and block-
PP
Default Value = 0x80
Block-
Locked
Status
BEFP
Status
DatasheetIntel StrataFlash
Order Number: 306666, Revision: 00175
®
Embedded Memory (P30)April 2005
1-Gbit P30 Family
Table 28. Status Register Description (Sheet 2 of 2)
Status Register (SR)
5Erase Status (ES)
4Program Status (PS)
3V
2
1
0BEFP Status (BWS)
Status (VPPS)
PP
Program Suspend Status
(PSS)
Block-Locked Status
(BLS)
0 = Erase successful.
1 = Erase fail or program sequence error when set with SR[4,7].
0 = Program successful.
1 = Program fail or program sequence error when set with SR[5,7]
0 = VPP within acceptable limits dur ing program or erase oper ation.
1 = VPP < VPPLK during pr ogram or erase operat ion.
0 = Program suspend not in effect.
1 = Program suspend in effect.
0 = Block not locked during program or erase.
1 = Block locked during program or erase; operation aborted.
DWS
BWS
0
0
1
1
= WSM is busy and buffer is availab le for loading.
0
= WSM is busy and buffer is not available for loading.
1
= WSM is not busy and buffer is available for loading.
0
= Reserved for Future Use (RFU).
1
Default Value = 0x80
Note:Always clear the Status Register prior to resuming erase operations. It avoids Status Register
ambiguity when issuing commands during Erase Suspend. If a command sequence error occurs
during an erase-suspend state, the Status Register contains the command sequence error status
(SR[7,5,4] set). When the erase operation resumes and finishes, possible errors during the erase
operation cannot be detected via the Status Register because it contains the previous error status.
14.1.1Clear Status Register
The Clear Status Register command clears the status register. It functions independent of VPP. The
Write State Machine (WSM) sets and clears SR[7,6,2], but it sets bits SR[5:3,1] without clearing
them. The Status Register should be cleared before starting a command sequence to avoid any
ambiguity. A device reset also clears the Status Register.
14.2Read Device Identifier
The Read Device Identifier command instructs the device to output manufacturer code, device
identifier code, block-lock status, protection register data, or configuration register data (see
Section 9.2, “Device Commands” on page 50 for details on issuing the Read Device Identifier
command). T able 29, “Device Identifier Information” on page 77 and Table 30, “Device ID codes”
on page 77 show the address offsets and data values for this device.
Manufacturer Co de0x000089h
Device ID Code0x01ID (see Table 30)
Block Lock Configur ation:
• Block Is UnlockedDQ
• Block Is LockedDQ
• Block Is not Locked-DownDQ
• Block Is Locked-DownDQ
Configurat ion Register 0x05Configuration Register Dat a
Lock Register 00x80PR-LK0
64-bit Factory-Programmed Protect ion Register0x81–0x84Factory Protection Register Data
64-bit User-Pr ogr ammable Protectio n R egister0x85–0x88User Protection Register Data
Lock Register 10x89Protection Register Data
128-bit User- Pr ogrammable Protection Registers0x8A–0x109PR-LK1
Notes:
1.BBA = Block Base Address.
(1)
BBA + 0x02
Lock Bit:
1-Gbit P30 Family
Data
= 0b0
0
= 0b1
0
= 0b0
1
= 0b1
1
Table 30. Device ID codes
ID Code TypeDevice Density
Device Code
14.3CFI Query
The CFI Query command instructs the device to output Common Flash Interface (CFI) data when
read. See Section 9.2, “Device Commands” on page 50 for details on issuing the CFI Query
command. Appendix C, “Common Flash Interface” on page 93 shows CFI information and address
offsets within the CFI database.
Device Identifier Codes
–T
(Top Parameter)–B(Bottom Parameter)
64-Mbit8817881A
128-Mbit8818881B
256-Mbit8919891C
DatasheetIntel StrataFlash
Order Number: 306666, Revision: 00177
®
Embedded Memory (P30)April 2005
1-Gbit P30 Family
(2)
Appendix A Write State Machine
Figure 34 through Figure 39 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 34. Write State Machine—Next State Table (Sheet 1 of 6)
Figure 39. Write State Machine—Next State Table (Sheet 6 of 6)
p
A
Output Next State Table
Command Input to Chip and resulting Output Mux Next State
Lock
Current chip state
BEFP Setup,
BEFP Pgm & Verify
Busy,
Erase Setup,
OTP Setup,
BP: Setup, Load 1,
Load 2, Conf i rm,
Word Pgm Setup,
Word Pgm Setup in
Erase Susp ,
BP Setup, Load1,
Load 2, Conf i rm in
Erase Suspend
Lock/CR Setup,
Lock/CR Setup in
Erase Susp
OTP Busy
Ready,
Erase Suspend,
BP Suspend
BP Busy,
Word P rogram
Busy,
Erase Busy,
BP Busy
BP Busy in Erase
Suspend
Word Pgm
Suspend,
Word Pgm Busy in
Erase Suspend,
Pgm Suspend In
Erase Sus
end
OTP
(4)
Setup
Confirm
(C0H)(01H)(2FH)(03H)(FFFFH)(all other codes)
Status Read
Status
Read
Lock-Down
Block
Block
(8)
Confirm
Output does not change.
Write CR
Confirm
(8)
Status Read
rray
Read
Block Address
(8)
(?WA0)
Array Read
Illegal Cmds or
BEFP Data
Status Read
Output does not
change.
(1)
1-Gbit P30 Family
WSM
Operation
Completes
Output does
not change.
Notes:
1."Illegal commands" include comm ands outside o f the allowed command set (allowed commands: 40H [pgm], 20H [erase],
etc.)
2.If a "Read Array" is attem pted from a busy partition, the result w il l be invalid data . The ID and Query data are located at
different locations in the address m ap.
3.1st and 2nd cycles of "2 cycles writ e commands" must be given to the same partition address, or unexpected results will
occur.
4.To protect memory contents against errone ous command sequences, ther e ar e specific instanc es 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 comm and (0x20) is given follo wed by a confirm/resume com mand (0xD0), the second command will be
ignored because it is unclear whether th e user intends to erase the block or resume the program operation.
DatasheetIntel StrataFlash
®
Embedded Memory (P30)April 2005
Order Number: 306666, Revision: 00183
1-Gbit P30 Family
5.The Clear Status command only clears the error bits i n the status r egister 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 allow ed when the status register bit #0 = 0, or else the data is ignored.
7.The "current state" is that of the "chip" and not of the "partition"; Each partition "remembers" which output (Array, ID/CFI or
Sta tus) it was last pointe d to on the last instructi on to the "chip", but the next state of the chip do es not depend on where
the partition's output mux is prese ntly pointing to.
8.Confirm commands (Lock Block, Unlock Block, Lock-Down Block, Configuration Regis ter) perform the oper at ion and then
move to th e R e ady State.
9.WA0 refers to th e block address latched during the first writ e cycle of the current oper ation.
Other partitions of the device can be read by addressing those partitions
and driving OE# low. (Any write commands are not allowed during this
period.)
and Word Address
(Note 5)
Read Status Register
(Note 7)
No
Yes
0 = No
1 = Yes
No
Yes
Buffer Programming Procedure
Use Single Word
Programming
No
Timeout
or Count
Expired?
X = X + 1
Write Buffer Data,
Word Address
No
Abo rt B uffe r
Program?
Yes
Write to another
Block Address
Buffer P rog ra m A b o rted
No
Yes
Issue Read
Status Register
Command
1-Gbit P30 Family
Bus
Operation
(Notes 1, 2)
(Notes 3, 4)
(Note 3)
(Notes 5, 6)
1. Wo rd count value on D[7:0] is loaded into the word co unt
register. Count ranges for this device are N = 0x00 to 0x1F.
2. The device outputs the Status Register when read.
3. Wr ite B u ffer co n ten ts will be prog ramm ed a t the iss ue d word
address.
4. Align the start address on a Write Buffer boundary for
maximum programming performance (i.e., A[4:0] of the Start
Word A dd ress = 0x00).
5. The Buffered Programming Confirm command must be
issued to an address in the same block, for example, the
original Start Word Address, or the last address used during the
loop that loaded the buffer data.
6. The Status Register indicates an improper command
sequence if the Buffer Program c om m an d is aborted; use the
Clear Status Register com m and to c lear error bits.
7. The Status Register can be read from any address within
the programm ing partition.
Full status check can be do ne after all erase and write
sequences complete. Write 0xFF after the last operation to
place the partition in the Read Array state.
Suspend
Program
Loop
Command
Buffer Prog.
Write
ReadNone
IdleNone
Write
Write
Write
Write
Read
Idle
Setup
None
None
None
Buffer Prog.
Conf.
None
None
Comments
Data = 0 xE8
Addr = Word Address
SR[7] = Valid
Addr = Word Address
Che c k S R [7 ]:
1 = Write Buffer available
0 = No Write Buffer available
Data = N-1 = Word Count
N = 0 corresponds to count = 1
Addr = Word Address
Data = Write Bu ffe r D ata
Addr = Start Word Address
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 Stat us Register c h ec k can be done afte r each program, or
after a sequence of program operations.
Write 0xFF after the last operati on to set Read Arra y s tate.
CommandComments
Idle
Program
PR Setup
Protection
Program
Write
Write
ReadNoneStatus Register Data.
Data = 0xC0
Addr = First Location to Program
Data = Data to Program
Addr = Location to Program
Check SR[7]:
1 = WSM Read y
None
0 = WSM Busy
FULL STATUS CHECK PROCEDURE
Bus
Idle
Idle
Command
None
None
Check SR[3]:
1 =V
Check SR[4]:
1 =Programming Error
Operation
Range Error
PP
Comments
SR[4] =
0
SR[1] =
0
Program
Successful
1
1
Program Error
Register Locked;
Program Aborted
IdleNone
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.
The Common Flash Interface (CFI) is part of an overall specification for multiple command-set
and control-interface descriptions. This appendix describes the database structure containing the
data returned by a read operation after issuing the CFI Query command (see Section 9.2, “Device
Commands” on page 50). System software can parse this database structure to obtain information
about the flash device, such as block size, density, bus width, and electrical specifications. The
system software will then know which command set(s) to use to properly perform flash writes,
block erases, reads and otherwise control the flash device.
C.1Query Structure Output
The Query database allows system software to obtain information for controlling the flash device.
This section describes the device’s CFI-compliant interface that allows access to Query data.
1-Gbit P30 Family
Query data are presented on the lowest-order data outputs (DQ
) only. The numerical offset value
7-0
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 (DQ
) and 00h in the high byte (DQ
7-0
At Query addresses containing two or more bytes of information, the least significant data byte is
presented at the lower address, and the most significant data byte is presented at the higher address.
In all of the following tables, addresses and data are represented in hexadecimal notation, so the
“h” suffix has been dropped. In addition, since the upper byte of word-wide devices is always
“00h,” the leading “00” has been dropped from the table notation and only the lower byte value is
shown. Any x16 device outputs can be assumed to have 00h on the upper byte in this mode.
Table 31. Summary of Query Structure Output as a Function of De vice and Mod e
Device
Device Addresses
Hex
Offset
00010:51“Q”
00011:52“R”
00012:59“Y”
Hex
Code
).
15-8
ASCII
Value
Table 32. Example of Query Structure Output of x16- Devices
The Query command causes the flash component to display the Common Flash Interface (CFI)
Query structure or “database.” The structure sub-sections and address locations are summarized
below.
0
P_ID
LO
P_ID
LO
P_ID
HI
D
7
0
PrVendor
ID #
ID #
D
alue
Table 33. Query Structure
OffsetSub-Section Nam
00001-Fh ReservedReserved for vend or-specific information
00010hCFI query identification stringComm a nd set ID and vend or data offset
0001BhSystem interface informationDevice timing & voltage information
00 027 hDe vice geometry de finitionFla s h devic e la yout
(3)
Primary Intel- specific Extended Query Table
Notes:
1.Refer to the Query St ructure O utput sectio n and of fset 28h for the detaile d definit ion of off set addre ss as
a function of device bus width and mode.
2.BA = Block Address beginning locat ion (i.e., 08000h i s block 1’s beginning location w hen the block size
is 16-KWord).
3.Offset 15 defines “P” which points t o the Primary Intel-s pecific Extended Que ry Table.
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 34. CFI Identification
1-Gbit P30 Family
OffsetLengthDescription
10h
13h
3Query-unique ASCII string “QRY“10:
2Primary vendor command set and control interface ID code.13:--01
16-bit ID code for vendor-specified algorithms14:--00
[programming] supply minimum program/erase voltage
PP
bits 0–3 BCD 100 mV
bits 4–7 HEX volts
V
[programming] supply maximum program/erase voltage
PP
bits 0–3 BCD 100 mV
bits 4–7 HEX volts
“n” such that t
“n” such that t
“n” such that t
“n” such that t
“n” such that maxim um word
“n” such that maxim um b uffer write time-out = 2
“n” such that maxim um b loc k e ras e t im e -o ut = 2
“n” such that maxim um c h i
ical single word program time-out = 2n µ-sec
ical max. buffer write time-out = 2n µ-sec
ical block erase time-out = 2n m-sec
ical full chip erase t i me-out = 2nm-sec
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:
76543210
15141312111098
————————29:--00
“n” such that maximum number of bytes in write buffer = 2
2
Number of eras e block regions ( x) wi t hin device:
1. x = 0 mean s no erase block ing; the devic e erases in bulk
2. x specifies the number of device regions with one or
more cont iguous same-s ize eras e blocks .
3. Symmetrically blocked partitions have one blocking region
4Erase Block Region 1 Information
bits 0–15 = y, y+1 = number of identical-size erase blocks
bits 16–31 = z, region erase block(s) size are z x 256 bytes
4Erase Block Region 2 Information
bits 0–15 = y, y+1 = number of identical-size erase blocks
bits 16–31 = z, region erase block(s) size are z x 256 bytes
4Reserved for future erase block region information
P = 10 A h(Optional fl ash features and commands)Add. Code Value
(P+ 0)h3Prim ary extended query table 10A--50"P"
(P+1)hUniqu e ASCII string “PR I“10B: --52"R"
(P+2)h10C:--49"I"
(P+ 3)h1Major version number, ASCII10D:--31"1"
(P+ 4)h1Minor version number, ASCII10E:--34"4"
(P+ 5)h4Optional feature and command support (1=yes, 0=no)10F:--E6
(P+6)hbits 10–31 are reserved; undefined bits are “0.” If bit 31 is 110:--01
(P+7)h“1” then another 31 bit field of Optional features follows at 111:--00
(P+8)hthe end of the bit–30 field.112:--00
(P+ 9)h1113:--01
(P+A)h2Block status register mask 114:--03
(P+B)hbits 2–15 are Reserved; undefined bits are “0”115:--00
(P+ C)h1116:--181.8V
(P+ D)h1117:--909.0V
LengthDescriptionHex
bit 0 Chip erase supportedbit 0 = 0No
bit 1 Suspend erase supportedbit 1 = 1Yes
bit 2 Suspend program supportedbit 2 = 1Yes
bit 3 Legacy lock/unlock supportedbit 3 = 0No
bit 4 Queued erase supportedbit 4 = 0No
bit 5 Instant individual block locking supportedbit 5 = 1Yes
bit 6 Protection bits supportedbit 6 = 1Yes
bit 7 Pagemode read supportedbit 7 = 1Yes
bit 8 Synchronous read supportedbit 8 = 1Yes
bit 9 Simultaneous operations supportedbit 9 = 0No
bit 10 E xtended Flash Array Blocks supportedbit 10 = 0No
bit 30 CFI Link(s) to followbit 30 = 0No
bit 31 Another "Optional Features" field to foll owbit 31 = 0No
Supported functions after suspend: read Array, Status, Query
Other supported operations are:
bits 1–7 reserved; undefined bits are “0”
bit 0 Program supported after erase suspendbit 0 = 1Yes
bit 0 Block Lock-Bit Status register activebit 0 = 1Yes
bit 1 Block Lock-Down Bit Status activebit 1 = 1Yes
bit 4 EFA Block Lock-Bit Status register activebit 4 = 0N o
bit 5 EFA Block Lock-Down Bit Status activebit 5 = 0No
logic supply highest performance program/erase voltage
V
CC
bits 0–3 BCD value in 100 mV
bits 4–7 BCD value in volts
optimum program/erase supply voltage
V
PP
bits 0–3 BCD value in 100 mV
bits 4–7 HEX value in volts
1-Gbit P30 Family
DatasheetIntel StrataFlash
Order Number: 306666, Revision: 00197
®
Embedded Memory (P30)April 2005
1-Gbit P30 Family
p
A
g
(
pg
)
p
A
pag
p
Table 38. Protection Register Information
(1)
Offset
Length
Descri
tion
P = 10Ah(Optional flash features and commands)
(P+E)h1118:--022
Number of Protection register fields in JEDEC ID space.
Hex
dd. CodeValue
“00h,” in dicat e s that 25 6 protec tion fi elds are av ailable
(P+F)h4Protection Field 1: Protection Description119:--8080h
(P+10)hTh i s field describes us er - available One Ti me Pro
(P+11)h
(P+12)h11C:--038 byte
OTP) Protection register bytes. Some are pre-programmed 11B:--038 byte
with device-un ique serial num bers. Others are user
rammable 11A: --0000h
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 add r ess
bits 16–23 = “n” such tha t 2
bits 24–31 = “n” such tha t 2
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 = fact o r y pgm' d groups (l ow byte)
bits 40–47 = “n” ∴ n = fact o r y pgm' d groups (h igh byte)
bits 48–55 = “n” \ 2n = factory prog r ammab l e bytes/ g r oup
bits 56–63 = “n” ∴ n = user pgm'd gr oups (lo w byte)
bits 64–71 = “n” ∴ n = user
m'd groups (high byte
bits 72–79 = “n” ∴ 2n = user programmable bytes/group
Page Mode Read capability
bits 0–7 = “n” such that 2
read-page bytes. See offset 28h for device word width to
determine page-mode data output width. 00h indicates no
read
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 2
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
Table 40. Partition and Erase-block Region Information
(1)
Offset
P= 10AhDescription
BottomTop(O ptional flash features and commands)
(P+23)h (P+23)h12D:--000
Number of device hardw are-partition regions within the device.
x = 0: a single hardware partition device (no fields fol l ow).
x specifies the number of device partition regions containing
one or more contiguous erase block regions.
Flash Memory Design for a St acked Chip Scale Package (SCSP)
®
Flash Memory Chip Scale Package User’s Guide
®
Wireless Communications and Computin g Package User's Guide
®
Small Outline Pac kage Guide
®
Flash Data Integr at or (FDI) User’s Guide
®
Persistent Storage Manager U ser G uide
Document/Tool
300783Using Intel® Flash Memory: Asynchronous Page Mo de and Synchronous Burst Mode
306667
306668
306669
Migration Guide for Intel StrataFlash
Memory (P30) Application Note 812
Migration Guide for Spansion* S29G LxxxN to Intel StrataFlash
(P30) Applicat ion Note 813
Migration Guide for Intel StrataFlash
StrataFlash
®
Embedded Memory (P 30) Application Note 825
®
Memory (J3) to Intel StrataFlash® Embedded
®
Embedded Mem or y
®
Synchronous Me m or y ( K3 /K 18) to Intel
Notes:
1.Please call the I nt el Literature Cent er at (800) 548-4725 to request Intel documentation. Internati onal
customers should contact their local Inte l or di stribution sales offi ce.
2.Visit Intel’s World Wide Web home page at http://www.intel.com for technical documentation and
tools.