2.7 V or 1.65 V I/O Option Reduces
Overall System Power
12 V for Fast Production
Programming
n
High Performance
2.7 V–3.6 V: 90 ns Max Access Time
3.0 V–3.6 V: 80 ns Max Access Time
n
Optimized Architecture for Code Plus
Data Storage
Eight 8-Kbyte Blocks,
Top or Bottom Locations
Up to Sixty-Three 64-KB Blocks
Fast Program Suspend Capability
Fast Erase Suspend Capability
n
Flexible Block Locking
Lock/Unlock Any Block
Full Protection on Power-Up
WP# Pin for Hardware Block
Protection
VPP = GND Option
VCC Lockout Voltage
n
Low Power Consumption
9 mA Typical Read Power
10 µA Typical Standby Power with
Automatic Power Savings Feature
n
Extended Temperature Operation
–40 °C to +85 °C
8-, 16-, 32-MBIT
n
Easy-12 V
Faster Production Programming
No Additional System Logic
n
128-bit Protection Register
64-bit Unique Device Identifier
64-bit User Programmable OTP
Cells
n
Extended Cycling Capability
Minimum 100,000 Block Erase
Cycles
n
Flash Data Integrator Software
Flash Memory Manager
System Interrupt Manager
Supports Parameter Storage,
Streaming Data (e.g., voice)
n
Automated Word/Byte Program and
Block Erase
Command User Interface
Status Registers
n
SRAM-Compatible Write Interface
n
Cross-Compatible Command Support
Intel Basic Command Set
Common Flash Interface
n
x 16 for High Performance
48-Ball µBGA* Package
48-Lead TSOP Package
n
x 8 I/O for Space Savings
48-Ball µBGA* Package
40-Lead TSOP Package
n
0.25 µ ETOX™ VI Flash Technology
PRODUCT PREVIEW
The 0.25 µm 3 Volt Advanced+ Boot Block, manufactured on Int el’s latest 0.25 µ technology , represents a
feature-rich solution at overall lower system cost. Smart 3 flash memory devices incorporate low voltage
capability (2.7 V read, program and erase) with high-speed, low-power operation. Flexible block locking
allows any block to be independently locked or unlocked. Add to this the Intel-developed Flash Data
Integrator (FDI) software and you have a cost-effective, flexible, monolit hi c code plus data storage s ol ution on
the market today. 3 Volt Adv anced+ Boot Block product s will be available in 48-lead TSOP , 40-lead TSOP,
and 48-ball µBGA* packages. Additional information on this product family can be obtained by accessing
Intel’s WWW page: http://www.intel.com/design/flcomp.
May 1998Order Number: 290645-001
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 whatsoever, and Intel disclaims any express or implied warranty, relating to
sale and/or use of Intel products including liability or warranties relating to fitness for a particular purpose, merchantability, or
infringement of any patent, copyright or other intellectual property right. Intel products are not intended for use in medical, life
saving, or life sustaining applications.
Intel may make changes to specifications and product descriptions at any time, without notice.
The 28F008C3, 28F016C3, 28F032C3, 28F800C3, 28F160C3, 28F320C3 may contain design defects or errors known as
errata which may cause the product to deviate from published specifications. Current characterized errata are available on
request.
Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing your product order.
Copies of documents which have an ordering number and are referenced in this document, or other Intel literature, may be
obtained from:
Intel Corporation
P.O. Box 5937
Denver, CO 80217-9808
1.13 Volt Advanced+ Boot Block
Flash Memory Enhancements
This document contains the specifications for the
3 Volt Advanced+ Boot B lock flash memory family .
These flash memories add features which can be
used to enhance the security of systems: instant
block locking and a protection register.
Throughout this document, t he term “2.7 V” refers
to the full voltage range 2.7 V –3.6 V (except where
noted otherwise) and “V
±5%. Sections 1 and 2 provide an overview of the
flash memory family including appli cations, pinouts,
pin descriptions and memory organization. Section
3 describes the operation of these produc ts . Fi nally ,
Section 4 contains the operating specifications.
Feature
VCC Operating Voltage2.7 V – 3.6 VTable 8
VPP VoltageProvides complete write protection with
V
I/O Voltage2.7 V– 3.6 VNote 3
CCQ
Bus Width8-bit16-bitTable 2
Speed (ns)90, 110 @ 2.7 V and 80, 100 @ 3.0 VTable 11
Blocking (top or bottom)8 x 8-Kbyte parameter
Operating TemperatureExtended: –40 °C to +85 °CTable 8
Program/Erase Cycling100,000 cyclesTable 8
Packages40-Lead TSOP
Block LockingFlexible locking of any block with zero latencySection 3.3
Protection Register64-bit unique device number, 64-bit user programmableSection 3.4
NOTES:
1. 32-Mbit density not available in 40-lead TSOP.
2. 8-Mbit density not available in µBGA* CSP.
operation at 1.65 V — 2.5 V available upon request.
3. V
CCQ
=12 V” refers to 12 V
PP
Table 1. 3 Volt Advanced+ Boot Block Feature Summary
(2)
8 M
16 M
(1)
32 M
optional 12V Fast Programming
4-Mb: 7 x 64-Kbyte main
8-Mb: 15 x 64-Kbyte main
16-Mb: 31 x 64-Kbyte main
32-Mb: 63 x 64-Kbyte main
48-Ball µBGA* CSP
The 3 Volt Advanced+ Boot Block flash memory
features:
•Zero-latency, flexible block locking
•128-bit Protection Register
•Simple system implementation for 12 V
production programming with 2.7 V in-field
programming
•Ultra-low power operation at 2.7 V
•Minimum 100,000 block erase cycles
•Common Flash Interface for s oftware query of
device specs and features
(2)
8 M
16 M
32 M
Table 8
8 x 4-Kword parameter
4-Mb: 7 x 32-Kword main 8-
Mb: 15 x 32-Kword main
16-Mb: 31 x 32-Kword main
32-Mb: 63 x 32-Kword main
(1)
(2)
48-Lead TSOP
48-Ball µBGA* CSP
Section 2.2
Appendix E and F
Figures 1, 2, 3,
(2)
and 4
Reference
PRODUCT PREVIEW
5
3 VOLT ADVANCED+ BOOT BLOCK E
1.2Product Overview
Intel provides secure low v oltage memory solutions
with the Advanced Boot B lock fami ly of product s. A
new block locking feature allows instant
locking/unlocking of any block with zero-latency. A
128-bit protection register allows unique flash
device identification.
Discrete supply pins provide single voltage read,
program, and erase capability at 2.7 V while also
allowing 12 V V
programming. Easy-12 V, a new feature designed
to reduce external logic, simplifies board designs
when combining 12 V production programming with
2.7 V in-field programming.
The 3 Volt Advanced+ Boot Block flash memory
products are available in either x8 or x16 pac kages
in the following densities : (see Section 6,
Information
•8-Mbit (8,388,608 bit) flash memories organized
•16-Mbit (16,777,216 bit) flash memories
•32-Mbit (33,554,432 bit) flash memories
Eight 8-KB parameter blocks are located at either
the top (denoted by -T suffix) or the bottom (-B
suffix) of the address map in order t o ac com modate
different microprocessor protocols for kernel code
location. The remaining memory is grouped into 64Kbyte main blocks.
)
as either 512 Kwords of 16 bits each or 1024
Kbytes or 8 bits each.
organized as either 1024 Kwords of 16 bits
each or 2048 Kbytes of 8 bits each.
organized as either 2048 Kwords of 16 bits
each or 4096 Kbytes of 8 bits each.
for faster production
PP
Ordering
The status register indicates the status of the WSM
by signifying block erase or word program
completion and status.
Program and erase automation allows program and
erase operations to be executed using an indust rystandard two-write command sequence t o the CUI.
Program operations are performed in word or byte
increments. Erase operations erase all locations
within a block simultaneously. Both program and
erase operations can be suspended by the system
software in order to read from any other block. In
addition, data can be programmed to anot her block
during an erase suspend.
The 3 Volt Advanced+ Boot Block flash memories
offer two low power savings features: Automatic
Power Savings (APS) and standby mode. The
device automatically enters APS mode following the
completion of a read cycle. Standby mode is
initiated when the system deselects the device by
driving CE# inactive. Combined, these two power
savings features significantly reduce power
consumption.
The device can be reset by lowering RP# to GND.
This provides CPU-memory reset synchronization
and additional protection against bus noise that
may occur during system reset and power-up/down
sequences (see Section 3.5 and 3.6).
Refer to the
complete current and voltage s pecifications. Refer
to the
read and write performance specific ations. Program
and erase times and shown in Section 4.7.
DC Characteristics
AC Characteristic s
Section 4.4 for
Sections 4.5 and 4.6, f or
2.0PRODUCT DESCRIPTION
All blocks can be locked or unlocked instantly to
provide complete protecti on for code or data. (see
Section 3.3 for details).
The Command User Interface (CUI) s erves as the
interface between the microprocessor or
microcontroller and the internal operation of the
flash memory. The internal Write State Machine
(WSM) automatically executes the algorithms and
timings necessary for program and erase
operations, including verification, thereby
unburdening the microprocessor or microcontroller.
6
This section provides device pin descriptions and
package pinouts for the 3 Volt Advanced+ Boot
Block flash memory f amily, which is availabl e in 40Lead TSOP (x8, Figure 1), 48-lead TSOP (x16,
Figure 2) and 48-ball µBGA packages (Figures 3
and 4).
2.1Package Pinouts
In each diagram, upgrade pins from one dens ity to
the next are circled.
Lower densities will have NC on the upper address pins. For example, an 8-Mbit device will have NC on Pins 9 and 15.
16
V
CCQ
GND
DQ
DQ
DQ
DQ
DQ
DQ
DQ
DQ
V
CC
DQ
DQ
DQ
DQ
DQ
DQ
DQ
DQ
OE#
GND
CE#
A
0
15
7
14
6
13
5
12
4
11
3
10
2
9
1
8
0
Figure 2. 48-Lead TSOP Package for x16 Configurations
PRODUCT PREVIEW
7
3 VOLT ADVANCED+ BOOT BLOCK E
12345678
A
13
A
B
14A10
C
A15A
D
A
16D14D5
E
V
CCQ
F
GNDD7D
A
11A8
12A9
D
15D6
VPPWP#A
WE# RP#A
32M
A
20
D
11D2
D
12D3
13D4VCCD10D1
16M
A
19
18A17A5
A
6
D8CE#A
D9D0GND
A
7
4A
A
2
A
A
3
1
0
OE#
NOTES:
1. Shaded connections indicate the upgrade address connections. Lower density devices will not have the upper address
solder balls. Routing is not recommended in this area. A19 is the upgrade address for the 16-Mbit device. A20 is the
upgrade address for the 32-Mbit device.
1. Shaded connections indicate the upgrade address connections. Lower density devices will not have the upper address
solder balls. Routing is not recommended in this area. A
upgrade address for the 32-Mbit device.
Table 2. 3 Volt Advanced+ Boot Block Pin Descriptions
SymbolTypeName and Function
A0–A
21
DQ0–DQ7INPUT/OUTPUT DATA INPUTS/OUTPUTS: Inputs array data on the second CE# and
DQ8–DQ15INPUT/OUTPUT DATA INPUTS/OUTPUTS: Inputs array data on the second CE# and
CE#INPUTCHIP ENABLE: Activates the internal control logic, input buffers,
OE#INPUTOUTPUT ENABLE: Enables the device’s outputs through the data
WE#INPUTWRITE ENABLE: Controls writes to the Command Register and
RP#INPUTRESET/DEEP POWER-DOWN: Uses two voltage levels (VIL, VIH) to
WP#INPUTWRITE PROTECT: Controls the lock-down function of the flexible
V
CC
INPUT
SUPPLYDEVICE POWER SUPPLY: [2.7 V–3.6 V] Supplies power for device
ADDRESS INPUTS for memory addresses. Addresses are internally
latched during a program or erase cycle.
8-Mbit x 8 A[0-19], 16-Mbit x 8 A[0-20], 32-Mbit x 8 A[0-21]
8-Mbit x 16 A[0-18], 16-Mbit x 16 A[0-19], 32-Mbit x 16 A[0-20]
WE# cycle during a Program command. Inputs commands to the
Command User Interface when CE# and WE# are active. Data is
internally latched. Outputs array, configuration and status register data.
The data pins float to tri-state when the chip is de-selected or the outputs
are disabled.
WE# cycle during a Program command. Data is internally latched.
Outputs array and configuration data. The data pins float to tri-state when
the chip is de-selected. Not included on x8 products.
decoders and sense amplifiers. CE# is active low. CE# high de-selects
the memory device and reduces power consumption to standby levels.
buffers during a read operation. OE# is active low.
memory array. WE# is active low. Addresses and data are latched on
the rising edge of the second WE# pulse.
control reset/deep power-down mode.
When RP# is at logic low, the device is in reset/deep power-down
mode, which drives the outputs to High-Z, resets the Write State
Machine, and minimizes current levels (I
When RP# is at logic high, the device is in standard operation.
When RP# transitions from logic-low to logic-high, the device resets all
blocks to locked and defaults to the read array mode.
Locking feature
When WP# is a logic low, the lock-down mechanism is enabled and
blocks marked lock-down cannot be unlocked through software.
When WP# is logic high, the lock-down mechanism is disabled and
blocks previously locked-down are now locked and can be unlocked and
locked through software. After WP# goes low, any blocks previously
marked lock-down revert to that state.
See Section 3.3 for details on block locking.
operations.
CCD
).
PRODUCT PREVIEW
9
3 VOLT ADVANCED+ BOOT BLOCK E
PP
Table 2. 3 Volt Advanced+ Boot Block Pin Descriptions (Continued)
SymbolTypeName and Function
V
CCQ
V
PP
GNDSUPPLYGROUND: For all internal circuitry. All ground inputs must be
NCNO CONNECT: Pin may be driven or left floating.
INPUTI/O POWER SUPPLY: Supplies power for input/output buffers.
[2.7 V–3.6 V] This input should be tied directly to V
CC
.
[1.65 V– 2.5 V] Lower I/O power supply voltage available upon request.
Contact your Intel representative for more information.
INPUT/
SUPPLY
PROGRAM/ERASE POWER SUPPLY: [1.65 V–3.6 V or 11.4 V–12.6 V]
Operates as a input at logic levels to control complete device protection.
Supplies power for accelerated program and erase operations in 12 V ±
5% range. This pin cannot be left floating.
Lower V
PP
≤ V
, to protect all contents against Program and
PPLK
Erase commands.
= VCC for in-system read, program and erase operations. In
Set V
PP
this configuration, V
diode drop from the system supply. Note that if V
signal, V
1.65. That is, V
IH =
can drop as low as 1.65 V to allow for resistor or
is driven by a logic
must remain above 1.65V to perform in-
PP
PP
system flash modifications.
Raise V
environment. Applying 12 V ± 5% to V
to 12 V ± 5% for faster program and erase in a production
PP
can only be done for a
PP
maximum of 1000 cycles on the main blocks and 2500 cycles on the
parameter blocks.
maximum. See Section 3.4 for details on V
VPP may be connected to 12 V for a total of 80 hours
voltage configurations.
PP
connected.
2.2Block Organization
The 3 Volt Advanced+ Boot Block is an
asymmetrically-blocked architecture that enables
system integration of code and data within a single
flash device. Each block can be erased
independently of the others up to 100,000 times.
For the address locations of each block, see the
memory maps in Appendix E and F.
10
2.2.1PARAMETER BLOCKS
The 3 Volt Advanced+ Boot Block flash memory
architecture includes parameter blocks to facilitate
storage of frequently updated small parameters
(i.e., data that would normally be stored in an
EEPROM). Each device contains eight parameter
blocks of 8-Kbytes/4-Kwords (8,192 bytes/4,096
words).
2.2.2MAIN BLOCKS
After the parameter blocks, the remainder of the
array is divided into equal size (64-Kword/32Kword; 65,536 bytes/32,768 words ) main blocks for
data or code storage. Each 8-Mbit, 16-Mbit, or
32-Mbit device contains 15, 31, or 63 main blocks,
respectively.
PRODUCT PREVIEW
E3 VOLT ADVANCED+ BOOT BLOCK
3.0PRINCIPLES OF OPERATION
The 3 Volt Advanced+ Boot Block flash memory
family utilizes a CUI and automated algorithms to
simplify program and erase operations. The CUI
allows for 100% CMOS
fixed power supplies during erasure and
programming.
-
level control inputs and
the V
command must be issued t o the CUI to enter the
corresponding mode. Upon initial dev ice power
or after exit from reset, the device automatically
defaults to read array mode.
CE# and OE# must be driven active to obtain dat a
at the outputs. CE# is the device s election control;
voltage. The appropriate read mode
PP
when active it enables the flash memory device.
The internal WSM completely automates program
and erase operations while the CUI si gnals the s tart
of an operation and the status register reports
status. The CUI handles t he WE# interface to the
OE# is the data output control and it drives the
selected memory data ont o the I/ O bus . For all read
modes, WE# and RP# must be at V
illustrates a read cycle.
data and address latches, as well as system status
requests during WSM operation.
3.1Bus Operation
The 3 Volt Advanced+ Boot Block flash memory
devices read, program and erase in
local CPU or microcontroller. All bus cycles to or
from the flash memory conform to standard
microcontroller bus cycles. Four control pins dictate
the data flow in and out of the flash component:
CE#, OE#, WE# and RP#. These bus operations
are summarized in Table 3.
-
system via the
3.1.2OUTPUT DISABLE
With OE# at a logic
outputs are disabled. Output pins are placed in a
high
-
impedance state.
3.1.3STANDBY
Deselecting the device by bri nging CE# to a logic
high level (VIH) places the device in standby mode,
which substantially reduces device power
consumption without any latency for subsequent
read accesses. In standby, outputs are placed in a
3.1.1READ
The flash memory has four read modes available:
read array, read configuration, read s tatus and read
high-impedance state independent of OE#. If
deselected during program or erase operat ion, the
device continues to c onsume active power unt il the
program or erase operation is complete.
query. These modes are accessi ble independent of
Table 3. Bus Operations
(1)
ModeNoteRP#CE#OE#WE#DQ
Read (Array, Status,
Configuration, or Query)
Output Disable2V
Standby2V
Reset2,7V
Write2,5-7V
NOTES:
1. 8-bit devices use only DQ[0:7], 16-bit devices use DQ[0:15]
2. X must be V
3. See
4. Manufacturer and device codes may also be accessed in read configuration mode (A
5. Refer to Table 5 for valid D
6. To program or erase the lockable blocks, hold WP# at V
7. RP# must be at GND ± 0.2 V to meet the maximum deep power-down current specified.
, VIH for control pins and addresses.
IL
DC Characteristics
for V
2-4V
, V
, V
PP1
PP2
, V
PPLK
during a write operation.
IN
IH
IH
IH
IL
IH
, voltages.
PP3
V
IL
V
IL
V
IH
V
IL
V
IH
XXHigh ZHigh Z
XXXHigh ZHigh Z
V
IL
.
IH
V
IH
1–A20
. Figure 9
IH
-
high level (VIH), the device
DQ
8-15
D
OUT
D
IN
V
IH
V
IH
V
IL
D
High ZHigh Z
D
= 0). See Table 4.
0–7
OUT
IN
-
up
-
PRODUCT PREVIEW
11
3 VOLT ADVANCED+ BOOT BLOCK E
3.1.4RESET
From read mode, RP# at V
for time t
IL
PLPH
deselects the memory, places output drivers in a
high
-
impedance state, and turns off all internal
circuits. After return from reset, a time t
PHQV
is
required until the initial read access outputs are
valid. A delay (t
PHWL
or t
) is required after
PHEL
return from reset before a write can be initiated.
After this wake
-
up interval, normal operation is
restored. The CUI resets t o read array mode, and
the status register i s s et t o 80H. This cas e is shown
in Figure 11A.
If RP# is taken low for time t
during a program
PLPH
or erase operation, the operation will be aborted
and the memory contents at the aborted location
(for a program) or block (for an erase) are no longer
valid, since the data may be partially erased or
written. The abort process goes through the
following sequence: When RP# goes low, the
device shuts down the operation in progress, a
process which takes time t
this time t
, the part will either reset to read
PLRH
array mode (if RP# has gone high during t
to complete. After
PLRH
PLRH
Figure 11B) or enter reset mode (if RP# is still logic
low after t
, Figure 11C). In both cases, after
PLRH
returning from an aborted operation, the relevant
time t
PHQV
or t
PHWL/tPHEL
must be waited bef ore a
read or write operation is initiat ed, as discussed in
the previous paragraph. However, in this case,
these delays are referenced to the end of t
PLRH
rather than when RP# goes high.
As with any automated device, it is important to
assert RP# during system reset. When the system
comes out of reset, proc essor expec ts to read from
the flash memory. Automated flash memories
provide status information when read during
program or block erase operations. If a CPU reset
occurs with no flash memory reset, proper CPU
initialization may not occur because the flash
memory may be providing status information
instead of array data. Int el’s flash memories allow
proper CPU initialization following a system reset
through the use of the RP# input. In this application,
RP# is controlled by the same RESET# signal that
resets the system CPU.
addressable memory location. The address and
data buses are latched on the rising edge of the
second WE# or CE# pulse, whichever occ urs first.
Figure 10 illustrates a program and erase operation.
The available commands are shown in Tabl e 6, and
Appendix A provides detailed information on
moving between the different modes of operation
using CUI commands.
There are two commands that modify array data:
Program (40H) and Erase (20H). Writing either of
these commands to the internal Command User
Interface (CUI) initiates a sequence of internally
timed functions that culminate in the c ompletion of
the requested task (unless that operat ion is aborted
by either RP# being driven to V
for t
IL
appropriate suspend command).
3.2Modes of Operation
The flash memory has four read modes and two
write modes. The read modes are read array, read
configuration, read status, and read query. The
,
write modes are program and block erase. Three
additional modes (erase suspend to program, eras e
suspend to read and program suspend to read) are
available only during suspended operations. These
modes are reached using the commands
summarized in Tables 5 and 6. A comprehensive
chart showing the state transitions is in Appendix A.
3.2.1READ ARRAY
When RP# transitions from V
device defaults to read array mode and will res pond
to the read control inputs (CE #, address i nputs , and
OE#) without any additional CUI commands.
When the device is in read array mode, four control
signals control data output:
•WE# must be logic high (V
•CE# must be logic low (V
•OE# must be logic low (V
•RP# must be logic high (V
(reset) to VIH, the
IL
)
IH
)
IL
)
IL
)
IH
PLRH
or an
-
3.1.5WRITE
A write takes place when bot h CE# and WE# are
low and OE# is high. Commands are written to the
Command User Interface (CUI) using standard
microprocessor write timings to control flash
operations. The CUI does not occupy an
12
In addition, the address of the desired l ocat ion mus t
be applied to the address pins. If the dev ice is not
in read array mode, as would be t he case after a
program or erase operation, the Read Array
command (FFH) must be written to the CUI before
array reads can take place.
PRODUCT PREVIEW
E3 VOLT ADVANCED+ BOOT BLOCK
3.2.2READ CONFIGURATION
The Read Configuration mode outputs the
manufacturer/device identifier. The device is
switched to this mode by writing the Read
Configuration command (90H). Once i n this mode,
read cycles from addresses shown in Table 4
retrieve the specified i nformation. To return to read
array mode, write the Read Array command (FFH).
The Read Configuration mode outputs three types
of information: the manufacturer/device identifier,
the block locking status , and the protec tion regis ter.
The device is switched to this mode by writ ing the
Read Configuration command (90H). Once in this
mode, read cycles from addresses shown in Table
4 retrieve the specified information. To return to
read array mode, write the Read Array command
(FFH).
Table 4. Read Configuration Table
ItemAddressData
Manufacturer Code (x16)000000089
Manufacturer Code (x8)0000089
Device ID (See Appendix G)00001ID
Block Lock Configuration
1. “XX” specifies the block address of lock configuration
being read.
2. See Section 3.3.4 for valid lock status outputs.
3. See Section 3.4 for protection register information.
4. Other locations within the configuration address space
are reserved by Intel for future use.
3.2.3READ STATUS REGISTER
The status register indicates the status of device
operations, and the success/failure of that
operation. The Read Status Register (70H)
2
3
(1)
XX002
80PR-LK
LOCK
command causes subsequent reads to output data
from the status register until another command is
issued. To return to reading from t he array, issue a
Read Array (FFH) command.
The status register bits are output on DQ
The upper byte, DQ
Read Status Register command.
The contents of the st atus register are latched on
the falling edge of OE# or CE#, whichever oc curs
last. This prevents possible bus errors which might
occur if status regi ster content s change while being
read. CE# or OE# must be toggled with each
subsequent status read, or the status register will
not indicate completion of a program or erase
operation.
When the WSM is active, SR.7 will indicate the
status of the WSM; t he remaining bits in the st atus
register indicate whether the WSM was successful
in performing the desired operation (see Table 7).
3.2.3.1Clearing the Status Register
The WSM sets status bits 1 through 7 to “1,” and
clears bits 2, 6 and 7 to “0, ” but cannot clear status
bits 1 or 3 through 5 to “0.” Becaus e bits 1, 3, 4 and
5 indicate various error conditions, these bits can
only be cleared through the use of the Clear Status
Register (50H) command. By allowing the system
software to control the resetting of these bits,
several operations may be performed (such as
cumulatively programming several addresses or
erasing multiple blocks in sequence) before reading
the status register t o determine if an error occurred
during that series. Clear the St atus Register before
beginning another command or sequence. Note
that the Read Array command must be issued
before data can be read from the memory array.
Resetting the device also clears the status register.
3.2.4READ QUERY
The Read Query mode outputs Common Flash
Interface (CFI) data when the devi ce is read. This
can be accessed by writing the Read Query
Command (98H). The CFI data structure contains
information such as bloc k size, density, c ommand
set and electrical specificat ions. Once i n this mode,
read cycles from addresses shown in Appendi x C
retrieve the specified i nformation. To return to read
array mode, write the Read Array command (FFH).
–DQ15, outputs 00H during a
8
–DQ7.
0
PRODUCT PREVIEW
13
3 VOLT ADVANCED+ BOOT BLOCK E
3.2.5PROGRAM MODE
-
Programming is executed using a two
write
sequence. The Program Setup command (40H) is
written to the CUI foll owed by a sec ond write which
specifies the address and data to be programmed.
The WSM will execute a sequence of internally
timed events to program desired bits of the
addressed location, then verify the bits are
sufficiently programmed. Programming the memory
results in specific bits within an address location
being changed to a “0.” If the user attempts to
program “1”s, the memory cell contents do not
change and no error occurs.
The status register indicates programming status:
while the program sequence execut es, status bit 7
is “0.” The status regis ter can be poll ed by toggling
either CE# or OE#. While programming, the only
valid commands are Read Status Register,
Program Suspend, and Program Resume.
When programming is complete, the Program
Status bits shoul d be checked. If the programming
operation was unsuccessf ul, bit SR.4 of the status
register is set to indi cate a program f ailure. If S R.3
is set then V
was not within acceptable l i m i ts, and
PP
the WSM did not execute t he program command. If
SR.1 is set, a program operation was att empted on
a locked block and the operation was aborted.
The status register should be cleared before
attempting the next operat ion. Any CUI instruction
can follow after programming is completed;
however, to prevent inadvertent status register
reads, be sure to reset the CUI to read array mode.
3.2.5.1Suspending and Resuming
Program
The Program Suspend command halts an in
progress program operation so that data can be
read from other locations of memory. Once the
programming process starts, writing the Program
Suspend command to the CUI requests that the
WSM suspend the program sequence (at
predetermined points in the program algorithm).
The device continues to output status register data
after the Program Suspend command is written.
Polling status register bits SR.7 and SR.2 will
determine when the program operation has been
suspended (both will be set to “1”). t
WHRH1/tEHRH1
specify the program suspend latency.
A Read Array command can now be writt en to the
CUI to read data from blocks other than that which
is suspended. The only other valid commands,
while program is suspended, are Read Status
Register, Read Configuration, Read Query, and
Program Resume. After the Program Resume
command is written to t he flash memory, the WSM
will continue with the programming process and
status register bits SR.2 and S R.7 will aut omatic ally
be cleared. The device automatically outputs s tatus
register data when read (see Figure 13 in Appendix
B,
Program Suspend/Resume Flowchart
Program Resume command is written. V
remain at the same V
level used for program
PP
while in program suspend mode. RP# must also
remain at V
.
IH
3.2.6ERASE MODE
To erase a block, write the Erase Set
Confirm commands to the CUI, along with an
address identifying the block to be erased. This
address is latched internally when the Erase
Confirm command is iss ued. Block erasure results
in all bits within the block being s et to “1.” Only one
block can be erased at a time. The WSM will
execute a sequence of internally timed events to
program all bits within the block to “0, ” erase all bit s
within the block to “1,” t hen verify t hat all bits within
the block are sufficiently erased. While the erase
executes, status bit 7 is a “0.”
When the status register indicates that erasure is
complete, check the erase status bit to verify that
the erase operation was successful. If the Erase
operation was unsuccessful, SR.5 of the status
register will be set to a “1,” indicating an erase
failure. If V
the Erase Confirm command was issued, t he WSM
will not execute the erase sequence; instead, SR.5
-
of the status register is set to indicate an erase
was not within acceptable l imits after
PP
error, and SR.3 is set to a “1” t o identify that V
supply voltage was not within acceptable limits.
After an erase operation, clear the status register
(50H) before attempting the next operation. Any
CUI instruction can follow after erasure is
completed; however, to prevent inadvertent status
register reads, it is adv isable to place the flash in
read array mode after the erase is complete.
) after the
must
PP
-
up and Erase
PP
14
PRODUCT PREVIEW
E3 VOLT ADVANCED+ BOOT BLOCK
3.2.6.1Suspending and Resuming Erase
Since an erase operation requires on the order of
seconds to complete, an Erase Suspend c ommand
is provided to allow erase
order to read data from or program data to another
block in memory. Once the erase sequence is
started, writing the Erase Suspend com mand to the
CUI suspends the erase sequence at a
predetermined point in the erase algorithm. The
status register will indicate if/when the erase
operation has been suspended. Erase suspend
latency is specified by t
X = Don’t CarePA = Prog Addr BA = Block AddrIA = Identifier Addr. QA = Query Addr.
SRD = Status Reg. DataPD = Prog DataID = Identifier DataQD = Query Data
NOTES:
1. Bus operations are defined in Table 3.
2. Following the Read Configuration or Read Query commands, read operations output device configuration or CFI query
information, respectively. See Section 3.2.2 and 3.2.4.
3. Either 40H or 10H command is valid, but the Intel standard is 40H.
4. When writing commands, the upper data bus [DQ
-
sequence interruption in
WHRH2/tEHRH2
.
Table 5. Command Bus Definitions
–DQ15] should be either VIL or VIH, to minimize current draw.
8
A Read Array/Program command can now be
written to the CUI to read/program data from/to
blocks other than that which is suspended. This
nested Program command can subsequently be
suspended to read yet another location. The only
valid commands while erase is suspended are
Read Status Register, Read Configuration, Read
Query, Program Setup, Program Resume, Erase
Resume, Lock Bloc k, Unlock Block and Lock -Down
Block. During erase suspend mode, the c hip c an be
placed in a pseudo
V
. This reduces active current consumption.
IH
Erase Resume continues t he eras e s equenc e when
CE# = V
operation, the status register must be read and
cleared before the next instruction is issued.
First Bus CycleSecond Bus Cycle
. As with the end of a standard erase
IL
-
standby mode by taking CE# to
PRODUCT PREVIEW
15
3 VOLT ADVANCED+ BOOT BLOCK E
Table 6. Command Codes and Descriptions
CodeDevice ModeDescription
FFRead ArrayPlaces device in read array mode, such that array data will be output on the
40Program
Set-Up
20Erase
Set-Up
D0Erase Confirm
Program/Erase
Resume
Unlock Block
B0Program
Suspend
Erase
Suspend
70Read Status
Register
50Clear Status
Register
90Read
Configuration
60Configuration
Set-Up
01Lock-BlockIf the previous command was Configuration Set-Up, the CUI will latch the
data pins.
This is a two-cycle command. The first cycle prepares the CUI for a program
operation. The second cycle latches addresses and data information and
initiates the WSM to execute the Program algorithm. The flash outputs status
register data when CE# or OE# is toggled. A Read Array command is required
after programming to read array data. See Section 3.2.5.
Prepares the CUI for the Erase Confirm command. If the next command is not
an Erase Confirm command, then the CUI will (a) set both SR.4 and SR.5 of the
status register to a “1,” (b) place the device into the read status register mode,
and (c) wait for another command. See Section 3.2.6.
If the previous command was an Erase Set-Up command, then the CUI will
close the address and data latches, and begin erasing the block indicated on the
address pins. During program/erase, the device will respond only to the Read
Status Register, Program Suspend and Erase Suspend commands and will
output status register data when CE# or OE# is toggled.
If a program or erase operation was previously suspended, this command will
resume that operation.
If the previous command was Configuration Set-Up, the CUI will latch the
address and unlock the block indicated on the address pins. If the block had
been previously set to Lock-Down, this operation will have no effect. (Sect. 3.3)
Issuing this command will begin to suspend the currently executing
program/erase operation. The status register will indicate when the operation
has been successfully suspended by setting either the program suspend (SR.2)
or erase suspend (SR.6) and the WSM Status bit (SR.7) to a “1” (ready). The
WSM will continue to idle in the SUSPEND state, regardless of the state of all
input control pins except RP#, which will immediately shut down the WSM and
the remainder of the chip if RP# is driven to V
3.2.6.1.
This command places the device into read status register mode. Reading the
device will output the contents of the status register, regardless of the address
presented to the device. The device automatically enters this mode after a
program or erase operation has been initiated. See Section 3.2.3.
The WSM can set the Block Lock Status (SR.1) , VPP Status (SR.3), Program
Status (SR.4), and Erase Status (SR.5) bits in the status register to “1,” but it
cannot clear them to “0.” Issuing this command clears those bits to “0.”
Puts the device into the Read Configuration mode, so that reading the device
will output the manufacturer/device codes or block lock status. Section 3.2.2.
Prepares the CUI for changes to the device configuration, such as block locking
changes. If the next command is not Block Unlock, Block Lock, or Block LockDown, then the CUI will set both the Program and Erase Status register bits to
indicate a command sequence error. See Section 3.3.
address and lock the block indicated on the address pins. (Section 3.3)
. See Sections 3.2.5.1 and
IL
16
PRODUCT PREVIEW
E3 VOLT ADVANCED+ BOOT BLOCK
Table 6. Command Codes and Descriptions (Continued)
CodeDevice ModeDescription
2FLock-DownIf the previous command was a Configuration Set-Up command, the CUI will
98Read
Query
C0Protection
Program
Setup
10Alt. Prog Set-Up Operates the same as Program Set-up command. (See 40H/Program Set-Up)
00Invalid/
Reserved
NOTE:
See Appendix A for mode transition information.
latch the address and lock-down the block indicated on the address pins.
(Section 3.3)
Puts the device into the Read Query mode, so that reading the device will
output Common Flash Interface information. See Section 3.2.4 and Appendix C.
This is a two-cycle command. The first cycle prepares the CUI for an program
operation to the Protection Register. The second cycle latches addresses and
data information and initiates the WSM to execute the Protection Program
algorithm to the Protection Register. The flash outputs status register data when
CE# or OE# is toggled. A Read Array command is required after programming
to read array data. See Section 3.4.
Unassigned commands that should not be used. Intel reserves the right to
redefine these codes for future functions.
PRODUCT PREVIEW
17
3 VOLT ADVANCED+ BOOT BLOCK E
PP
level. The WSM interrogates V
is also checked before the
and V
Table 7. Status Register Bit Definition
WSMSESSESPSVPPSPSSBLSR
76543210
NOTES:
SR.7 WRITE STATE MACHINE STATUS
1 = Ready(WSMS)
0 = Busy
SR.6 = ERASE-SUSPEND STATUS (ESS)
1 = Erase Suspended
0 = Erase In Progress/Completed
SR.5 = ERASE STATUS (ES)
1 = Error In Block Erase
0 = Successful Block Erase
SR.4 = PROGRAM STATUS (PS)
1 = Error in Programming
0 = Successful Programming
SR.3 = VPP STATUS (VPPS)
1 = V
0 = V
Low Detect, Operation Abort
PP
OK
PP
SR.2 = PROGRAM SUSPEND STATUS
(PSS)
1 = Program Suspended
0 = Program in Progress/Completed
SR.1 = BLOCK LOCK STATUS
1 = Prog/Erase attempted on a locked
block; Operation aborted.
0 = No operation to locked blocks
SR.0 = RESERVED FOR FUTURE
ENHANCEMENTS (R)
Check Write State Machine bit first to determine Word
Program or Block Erase completion, before checking
Program or Erase Status bits.
When Erase Suspend is issued, WSM halts execution
and sets both WSMS and ESS bits to “1.” ESS bit
remains set to “1” until an Erase Resume command is
issued.
When this bit is set to “1,” WSM has applied the max.
number of erase pulses to the block and is still unable to
verify successful block erasure.
When this bit is set to “1,” WSM has attempted but failed
to program a word/byte.
The V
of V
status bit does not provide continuous indication
PP
level only after
PP
the Program or Erase command sequences have been
entered, and informs the system if V
switched on. The V
PP
has not been
PP
operation is verified by the WSM. The VPPstatus bit is
not guaranteed to report accurate feedback between
V
PPLK
PP1
Min.
When Program Suspend is issued, WSM halts execution
and sets both WSMS and PSS bits to “1.” PSS bit
remains set to “1” until a Program Resume command is
issued.
If a program or erase operation is attempted to one of the
locked blocks, this bit is set by the WSM. The operation
specified is aborted and the device is returned to read
status mode.
This bit is reserved for future use and should be masked
out when polling the status register.
18
PRODUCT PREVIEW
E3 VOLT ADVANCED+ BOOT BLOCK
3.3Flexible Block Locking
The Intel® 3 Volt Advanced+ Boot Block products
offer an instant, individual block locking scheme
that allows any block t o be locked or unlocked with
no latency, enabling instant code and data
protection.
This locking scheme offers t wo levels of protec tion.
The first level allows software-only control of bloc k
locking (useful for data blocks that change
frequently), while the second level requires
hardware interaction before locki ng can be changed
(useful for code blocks that change infrequently).
The following sections will discuss the operat ion of
the locking system. The term “state [XYZ]” will be
used to specify locking states; e.g., “state [001],”
where X = value of WP#, Y = bit DQ
Lock status regist er, and Z = bit DQ
Lock status register. Table 9 defines all of these
possible locking states.
3.3.1LOCKING OPERATION
The following concisely summarizes the locking
functionality.
•All blocks power-up locked, then can be
unlocked or locked with the Unlock and Lock
commands.
•The Lock-Down command locks a block and
prevents it from being unlocked when WP# = 0.
When WP# = 1, Lock-Down is overridden
and commands can unlock/lock lockeddown blocks.
When WP# returns to 0, locked-down
blocks return to Lock-Down.
Lock-Down is cleared only when t he device
is reset or powered-down.
The locking status of each block can s et t o Loc ked,
Unlocked, and Lock-Down, each of which will be
described in the following sections. A
comprehensive state table f or the locking functions
is shown in Table 9, and a flowchart for locking
operations is shown in Figure 16.
of the Block
1
of the Block
0
3.3.2LOCKED STATE
The default status of all blocks upon power-up or
reset is locked (states [001] or [101]). Locked
blocks are fully protected from alteration. Any
program or erase operations attempted on a l ocked
block will return an error on bit SR.1 of the status
register. The status of a locked block can be
changed to Unlocked or Lock-Down using the
appropriate software commands. An Unlocked
block can be locked by wri ting the Lock command
sequence, 60H followed by 01H.
3.3.3UNLOCKED STATE
Unlocked blocks (states [000], [100], [110]) can be
programmed or erased. All unlocked blocks return
to the Locked state when the device is reset or
powered down. The status of an unlocked block can
be changed to Locked or Locked-Down using the
appropriate software commands. A Locked block
can be unlocked by writing the Unlock command
sequence, 60H followed by D0H.
3.3.4LOCK-DOWN STATE
Blocks that are Locked-Down (state [011]) are
protected from program and erase operations (just
like Locked blocks), but their protection status
cannot be changed using software commands
alone. A Locked or Unlocked bloc k can be Lock eddown by writing the Lock-Down command
sequence, 60H followed by 2FH. Locked-Down
blocks revert to the Locked state when the device is
reset or powered down.
The Lock-Down function is dependent on the WP#
input pin. When WP# = 0, blocks in Lock-Down
[011] are protected from program, erase, and loc k
status changes. When WP# = 1, the Lock-Down
function is disabled ([ 111]) and locked-down blocks
can be individually unlock ed by soft ware command
to the [110] state, where they can be erased and
programmed. These blocks can then be relocked
[111] and unlocked [110] as desired while WP#
remains high. When WP# goes low, blocks that
were previously locked-down return to the
Lock-Down state [011] regardless of any changes
made while WP# was high. Device reset or powerdown resets all blocks, including those in LockDown, to Locked state.
PRODUCT PREVIEW
19
3 VOLT ADVANCED+ BOOT BLOCK E
3.3.5READING A BLOCK’S LOCK STATUS
The lock status of ev ery block can be read in the
Configuration Read mode of the device. To enter
this mode, write 90H to the device. Subsequent
reads at Block Address + 00002 will out put the lock
status of that block . The lock status is represented
by the lowest two output pins , DQ
and DQ1. DQ
0
indicates the Block Lock/Unlock status and is set by
the Lock command and cleared by the Unlock
command. It is also automat ical ly set when entering
Lock-Down. DQ
indicates Lock-Down status and i s
1
set by the Lock-Down command. It cannot be
cleared by software, only by devic e reset or powerdown.
Table 8. Block Lock Status
ItemAddressData
Block Lock ConfigurationXX002LOCK
• Block Is UnlockedDQ0 = 0
• Block Is LockedDQ0 = 1
• Block Is Locked-DownDQ1 = 1
3.3.6LOCKING OPERATIONS DURING
ERASE SUSPEND
Changes to block lock status can be performed
during an erase suspend by using the standard
locking command sequences to unlock, lock, or
lock-down a block. This i s useful in the c ase when
another block needs to be updated while an erase
operation is in progress.
the lock status will be changed. After completing
any desired lock, read, or program operations,
resume the erase operation with the Eras e Resume
command (D0H).
If a block is locked or locked-down during a
suspended erase of the same block, the locking
status bits will be changed immediat ely, but when
0
the erase is resumed, the erase operation will
complete.
Locking operations cannot be performed during a
program suspend. Refer to Appendix A for detailed
information on which commands are valid during
erase suspend.
3.3.7STATUS REGISTER ERROR
CHECKING
Using nested locking or program command
sequences during erase suspend can introduce
ambiguity into status register results.
Since locking changes are perf ormed using a two
cycle command sequence, e.g., 60H followed by
01H to lock a block, following the Configuration
Setup command (60H) with an invalid comm and will
produce a lock command error (SR. 4 and SR.5 wi ll
be set to 1) in the status register. If a lock
command error occurs during an erase suspend,
SR.4 and SR.5 will be set to 1, and will remain at 1
after the erase is resumed. When erase is
complete, any possible error during the erase
cannot be detected via the s tatus register becaus e
of the previous locking command error.
To change block locking during an erase operation,
first write the erase s uspend command (B0H), then
check the status register until it indicates that the
erase operation has been suspended. Next write
the desired lock command sequence t o a block and
20
A similar situation happens if an error occ urs during
a program operation error nested within an erase
suspend.
PRODUCT PREVIEW
E3 VOLT ADVANCED+ BOOT BLOCK
Table 9. Block Locking State Transitions
Current StateErase/ProgLock Command Input Result [Next State]
WP#DQ1DQ
000“Unlocked”YesGoes To [001]No ChangeGoes To [011]
001“Locked” (Default)NoNo ChangeGoes To [000] Goes To [011]
011“Locked-Down”NoNo ChangeNo ChangeNo Change
100“Unlocked”YesGoes To [101]No ChangeGoes To [111]
101“Locked”NoNo ChangeGoes To [100] Goes To [111]
110Lock-Down DisabledYesGoes To [111]No ChangeGoes To [111]
111Lock-Down DisabledNoNo ChangeGoes To [110]No Change
NOTES:
1. In this table, the notation [XYZ] denotes the locking state of a block, where X = WP#, Y = DQ
locking state of a block is defined by the state of WP# and the two bits of the block lock status (DQ
a block is locked (1) or unlocked (0). DQ
2. At power-up or device reset, all blocks default to Locked state [001] (if WP# = 0). Holding WP# = 0 is the recommended
default.
3. The “Erase/Program Allowed?” column shows whether erase and program operations are enabled (Yes) or disabled (No)
in that block’s current locking state.
4. The “Lock Command Input Result [Next State]” column shows the result of writing the three locking commands (Lock,
Unlock, Lock-Down) in the current locking state. For example, “Goes To [001]” would mean that writing the command to a
block in the current locking state would change it to [001].
0
NameAllowed?LockUnlockLock-Down
, and Z = DQ0. The current
1
, DQ1). DQ0 indicates if
indicates if a block has been locked-down (1) or not (0).
1
0
3.4128-Bit Protection Register
The Advanced+ Boot Block arc hitecture includes a
128-bit protection register than can be used to
increase the security of a system design. For
example, the number contained in the protection
register can be used to “mate” the f lash component
with other system com ponents such as the CPU or
ASIC, preventing device substitution. Additional
application information can be found in Intel
application note
Advanced+ Boot Block Flash Memory Architecture
The 128-bits of the protection register are divided
into two 64-bit segments. One of the segments is
programmed at the Intel fact ory wit h a unique 64-bit
number, which is unchangeable. The other segment
is left blank for customer designs to program as
desired. Once the customer segment is
programmed, it can be locked to prevent
reprogramming.
AP-657 Designing with the
PRODUCT PREVIEW
3.4.1READING THE PROTECTION
The protection register is read in the conf iguration
read mode. The device is switc hed to this mode by
writing the Read Configuration command (90H).
Once in this mode, read cycles from addresses
shown in Appendix H retrieve the specified
information. To return to read array mode, write t he
Read Array command (FFH).
.
3.4.2PROGRAMMING THE PROTECTION
The protection register bits are programmed us ing
the two-cycle Protection Program command. The
64-bit number is programmed 16 bits at a time for
word-wide parts and eight bits at a time for bytewide parts. First write t he Prot ect ion Program Set up
command, C0H. The next write to the device will
latch in address and data and program the specified
location. The allowable addresses are shown in
Appendix H. See Figure 17 for the
Register Programming Flowchart
REGISTER
REGISTER
.
Protection
21
3 VOLT ADVANCED+ BOOT BLOCK E
Any attempt to address Protection Program
commands outside the defined protection register
address space will result in a Stat us Register error
(Program Error bit SR.4 will be set to 1). Attempting
to program or to a previously locked protection
register segment will result in a status register error
(program error bit SR.4 and lock error bit SR.1 will
be set to 1).
3.4.3LOCKING THE PROTECTION
REGISTER
The user-programmable segment of the protection
register is lockable by programming Bit 1 of the
PR-LOCK location to 0. Bit 0 of this location is
programmed to 0 at the Intel factory to prot ect the
unique device number. This bit is set using the
Protection Program comm and to program “FFFD” to
the PR-LOCK location. Af ter these bits have been
programmed, no further changes can be made to
the values stored in the protection register.
Protection Program comm ands to a locked section
will result in a status register error (Program Error
bit SR.4 and Lock Error bit SR.1 will be set to 1).
Protection register lockout state is not reversible.
88H
4 Words
User Programmed
85H
84H
4 Words
Factory Programmed
81H
1 Word Lock
80H
0645_05
Figure 5. Protection Register Memory Map
3.5VPP Program and Erase
Voltages
Intel’s 3 Volt Advanced+ Boot Block products
provide in-system writes plus a V
production programming and complete write
protection.
pin for 12 V
PP
3.5.1EASY-12 V OPERATION FOR FAST
MANUFACTURING PROGRAMMING
Intel’s 3 Volt Advanced+ Boot Block products
provide in-system programming and erase in the
2.7 V–3.6 V range. For fast production
programming, 3 Volt Advanced+ Boot Block
includes a low-cost, backward-compatible 12 V
programming feature.
When V
and erase current is drawn through the V
Note that if V
V
IH =
is between 1.65 V and 3.6 V, all program
PP
is driven by a logic signal,
1.65 V. That is, V
PP
must remain above 1.65 V
PP
CC
pin.
to perform in-system flash modifications. When V
is connected to a 12 V power supply, the device
draws program and erase current directl y from the
V
pin. This eliminates the need for an external
PP
switching transistor to control the voltage V
PP
Figure 6 shows examples of how the flash power
supplies can be configured for various usage
models.
The 12 V V
mode enhances programming
PP
performance during the short period of time typically
found in manufacturing processes; however, it is
not intended for extended use. 12 V may be applied
to V
during program and erase operations for a
PP
maximum of 1000 cycles on the main blocks and
2500 cycles on the parameter blocks. V
may be
PP
connected to 12 V for a total of 80 hours max imum.
Stressing the devic e beyond these limits may cause
permanent damage.
3.5.2V
≤ V
PP
PROTECTION
FOR COMPLETE
PPLK
In addition to the flexible block locking, the V
programming voltage can be held low for absolut e
hardware write protection of all blocks in the flash
device. When V
is below V
PP
, any program or
PPLK
erase operation will result in a error, prompt ing the
corresponding status register bit (SR.3) to be set.
3.5.3V
The V
PP
USAGE
PP
pin is used for two funct i ons : Absolute data
protection and fast production programming.
When V
PP
≤ V
, then all program or erase
PPLK
operations to the device are inhibited, providing
absolute data protection.
PP
.
PP
22
PRODUCT PREVIEW
E3 VOLT ADVANCED+ BOOT BLOCK
System Supply
12 V Supply
10 K
Ω
12 V Fast Programming
Complete Write Protection When V
System Supply
(Note 1)
12 V Supply
12 V Fast Programming
Full Array Protection Unavailable
NOTE:
1. A resistor can be used if the VCC supply can sink adequate current based on resistor value. See AP-657
the Advanced+ Boot Block Flash Memory Architecture
Figure 6. Example Power Supply Configurations
When V
manufacturing situations , the devi ce direct ly appli es
the high voltage to achieve faster program and
erase.
Designing for in-system writes to the flash memory
requires special consideration of power supply
traces by the printed circuit board designer.
Adequate power supply traces, and decoupling
capacitors placed adjacent to the component, will
decrease spikes and overshoots.
is raised to 12 V, such as in a
PP
V
CC
V
PP
≠ 12 V
PP
V
CC
V
PP
System Supply
Prot#
(Logic Signal)
Low-Voltage Programming Only
Logic Control of Complete Device Protection
System Supply
Low-Voltage Programming Only
Full Array Protection Unavailable
for details.
3.6.1ACTIVE POWER
(Program/Erase/Read)
With CE# at a logic
high level, the device is in the ac ti ve m ode. Refer t o
the DC Characteristic tables for I
Active power is the largest contributor to overall
system power consumption. Minimizing the active
current could have a profound effect on system
power consumption, especi ally for battery
devices.
V
CC
V
PP
V
CC
V
PP
-
low level and RP# at a logic
CC
0645_06
Designing with
current values.
-
operated
-
3.6Power Consumption
Intel’s flash devices have a tiered approach to
power savings that can significantly reduce ov erall
system power consumption. The Automatic Power
Savings (APS) feature reduces power consumption
when the device is selec ted but idle. If the CE# is
deasserted, the flash enters its standby mode,
where current consumption is even lower. The
combination of these features can minimize
memory power consumption, and therefore, overall
system power consumption.
PRODUCT PREVIEW
3.6.2AUTOMATIC POWER SAVINGS (APS)
-
Automatic Power Savings provides low
operation during read mode. After data is read from
the memory array and the address lines are
quiescent, APS circuitry places the device in a
mode where typical current is comparable to I
The flash stays in t his st atic s tate wi th outputs val id
until a new location is read.
3.6.3STANDBY POWER
-
With CE# at a logic
read mode, the flash memory i s in standby mode,
which disables much of the device’s circuitry and
high level (VIH) and device in
power
CCS
23
.
3 VOLT ADVANCED+ BOOT BLOCK E
substantially reduces power consumption. Outputs
are placed in a high
-
impedance state independent
of the status of the OE# signal. I f CE# t ransiti ons to
a logic
-
high level during erase or program
operations, the device will continue to perform the
operation and consume corresponding act iv e power
until the operation is completed.
System engineers should anal yz e the breakdown of
standby time versus active time and quantify the
respective power consumption in each mode for
their specific application. This will provide a more
accurate measure of applic ation
-
specific power and
energy requirements.
3.6.4DEEP POWER-DOWN MODE
The deep power-down mode is activated when
RP#
(GND ± 0.2 V). During read modes, RP#
= VIL
going low de-selects the memory and places the
outputs in a high impedance s tate. Recovery from
deep power-down requires a minimum time of t
for read operations and t
PHWL/tPHEL
PHQV
for write
operations.
During program or erase modes, RP# transi tioning
low will abort the in-progress operation. The
memory contents of the addres s being program med
or the block being erased are no longer vali d as the
data integrity has been comprom ised by the abort.
During deep power-down, all internal circuits are
switched to a low power savings mode (RP#
transitioning to V
or turning off power to the devic e
IL
clears the status register).
proper CPU/flash initialization following system
reset.
System designers must guard against spurious
writes when V
voltages are above V
CC
LKO
. Since
both WE# and CE# must be low for a command
write, driving either signal to V
will inhibit writ es to
IH
the device. The CUI architecture prov ides additi onal
protection since alterat ion of memory contents c an
only occur after successful completion of the twostep command sequences. The device is also
disabled until RP# is brought to V
, regardless of
IH
the state of its c ontrol inputs. By holding the devic e
in reset (RP# connected to system PowerGood)
during power-up/down, invalid bus conditi ons during
power-up can be masked, providing yet another
level of memory protection.
3.7.2V
, VPP AND RP# TRANSITIONS
CC
The CUI latches commands as issued by system
software and is not altered by V
or CE#
PP
transitions or WSM actions. Its default state upon
power-up, after exit from reset mode or after V
transitions above V
(Lockout voltage), is read
LKO
CC
array mode.
After any program or block erase operation is
complete (even after V
V
), the CUI must be reset t o read array mode
PPLK
transitions down to
PP
via the Read Array command if access to the fl ash
memory array is desired.
3.8Power Supply Decoupling
3.7Power-Up/Down Operation
The device is protected against accidental block
erasure or programming during power transitions.
Power supply sequencing is not required, since the
device is indifferent as to which power supply , V
or VCC, powers-up first.
3.7.1RP# CONNECTED TO SYSTEM
RESET
The use of RP# during system reset is important
with automated program/erase devices since the
system expects to read from the flash memory
when it comes out of res et. If a CPU reset occ urs
without a flash memory reset, proper CPU
initialization will not occur because the flash
memory may be providing status information
instead of array data. Int el recommends c onnecting
RP# to the system CPU RESET# signal to allow
24
PP
Flash memory’s power switching characteristics
require careful device decoupling. System
designers should consider three supply current
issues:
CCR
CCS
)
)
1. Standby current levels (I
2. Read current levels (I
3. Transient peaks produced by falling and rising
edges of CE#.
Transient current magnitudes depend on t he dev ice
outputs’ capacitiv e and inductive loading. Two-line
control and proper decoupling capacitor selection
will suppress these transient voltage peaks. Each
flash device should have a 0.1 µF ceramic
capacitor connected between eac h V
and between its V
and GND. These high-
PP
and GND,
CC
frequency, inherently low-inductance capacitors
should be placed as close as possible to the
package leads.
PRODUCT PREVIEW
E3 VOLT ADVANCED+ BOOT BLOCK
4.0ABSOLUTE MAXIMUM
RATINGS*
Extended Operating Temperature
During Read.......................... –40 °C to +85 °C
During Block Erase
and Program.......................... –40 °C to +85 °C
Temperature Under Bias ....... –40 °C to +85 °C
Storage Temperature................. –65 °C to +125 °C
NOTICE: This datasheet contains preliminary information on
products in the design phase of development. The
specifications are subject to change without notice. Verify
with your local Intel Sales office that you have the latest
datasheet before finalizing a design.
* WARNING: Stressing the device beyond the "Absolute
Maximum Ratings" may cause permanent damage. These
are stress ratings only. Operation beyond the "Operating
Conditions" is not recommended and extended exposure
beyond the "Operating Conditions" may effect device
reliability.
Voltage on Any Pin
(except V
with Respect to GND............. –0.5 V to +5.0 V
VPP Voltage (for Block
Erase and Program)
with Respect to GND.......–0.5 V to +13.5 V
VCC and V
with Respect to GND............. –0.2 V to +5.0 V
Output Short Circuit Current...................... 100 mA
and VPP)
CC
Supply Voltage
CCQ
1,2,4
NOTES:
1
1. Minimum DC voltage is –0.5 V on input/output pins.
During transitions, this level may undershoot to –2.0 V
for periods < 20 ns. Maximum DC voltage on
input/output pins is V
transitions, may overshoot to V
1
3
< 20 ns.
2. Maximum DC voltage on V
for periods < 20 ns.
3. Output shorted for no more than one second. No more
than one output shorted at a time.
voltage is normally 1.65 V–3.6 V. Connection to
4. V
PP
supply of 11.4 V–12.6 V can only be done for 1000
cycles on the main blocks and 2500 cycles on the
parameter blocks during program/erase. V
connected to 12 V for a total of 80 hours maximum.
See Section 3.5 for details.
+ 0.5 V which, during
CC
+ 2.0 V for periods
CC
may overshoot to +14.0 V
PP
may be
PP
4.2Operating Conditions
Table 10. Temperature and Voltage Operating Conditions
11.4 V–12.6 V during a program/erase can only be done for a maximum of 1000 cycles on the main blocks
PP =
.
may be connected to 12 V for a total of 80 hours maximum. See Section
PP
CC1
range.
PRODUCT PREVIEW
25
3 VOLT ADVANCED+ BOOT BLOCK E
Q
4.3Capacitance
T
A =
25 °C, f
1 MHz
=
SymParameterNotesTypMaxUnitsConditions
C
Input Capacitance168pFV
IN
C
Output Capacitance11012pFV
OUT
NOTE:
1. Sampled, not 100% tested.
IN =
OUT =
0 V
0 V
4.4DC Characteristics
V
CC
V
CCQ
2.7 V–3.6 V
2.7 V–3.6 V
SymParameterNoteTypMaxUnitTest Conditions
I
Input Load Current1,7± 1µA
LI
I
Output Leakage Current1,70.2
LO
I
CCSVCC
I
CCDVCC
I
CCRVCC
I
CCWVCC
Standby Current11025µAV
Deep Power-Down
1,7720µA
Current
Read Current1,5,7918mA
Program Current1,41855mA
815mA
VCC Erase Current1,41645mA
I
CCE
815mA
± 10µA
V
CC = VCC
V
CCQ = VCCQ
V
IN
V
CC
V
CCQ = VCCQ
V
IN
CC
CE#
V
CC
V
CCQ =
V
IN
RP#
V
CC
V
CCQ
OE# = V
f = 5 MHz, I
Inputs = V
V
PP
Program in Progress
V
PP = VPP2
Program in Progress
V
PP = VPP1
Erase in Progress
V
PP = VPP2
Max
V
or GND
=
CCQ
VCCMax
=
V
or GND
=
CCQ
VCCMax
=
RP# = V
=
VCCMax
=
V
CC
V
or GND
=
CCQ
GND ± 0.2 V
=
= VCCMax
= V
CCQ
, CE# = V
IH
IL
= V
PP1
(12 V)
(12 V)
Max
Max
Max
Max
OUT
or V
CC
= 0 mA
IH
Erase in Progress
I
CCESVCC
I
CCWSVCC
Erase Suspend
Current
Program Suspend
Current
1,2,41025µACE# = VIH, Erase Suspend in
Progress
1,2,41025µACE# = VIH, Program
Suspend in Progress
IL
26
PRODUCT PREVIEW
E3 VOLT ADVANCED+ BOOT BLOCK
4.4DC Characteristics, Continued
V
CC
V
CCQ
SymParameterNoteTypMaxUnitTest Conditions
I
V
PPD
I
PPSVPP
I
PPRVPP
I
PPWVPP
I
PPEVPP
I
PPESVPP
I
PPWSVPP
Deep Power-Down
Current
Standby Current10.25µAV
Read Current12±15µAV
Program Current1,40.050.1mA
Erase Current1,40.050.1mA
Erase Suspend Current1,40.25µA
Program Suspend Current1,40.25µA
10.25µARP# = GND ± 0.2 V
1,450200µAV
2.7 V–3.6 V
2.7 V–3.6 V
V
Program in Progress
822mA
822mA
50200µA
50200µA
V
Program in Progress
V
Program in Progress
V
Program in Progress
V
Erase Suspend in Progress
V
Erase Suspend in Progress
V
Program Suspend in
Progress
V
Program Suspend in
Progress
≤ V
PP
CC
≤ V
PP
CC
≥ V
PP
CC
=V
PP
PP1
PP = VPP2
= V
PP
PP1
PP = VPP2
= V
PP1
PP
= V
PP2
PP
= V
PP1
PP
= V
PP2
(12 V)
(12 V)
(12 V)
(12 V)
PRODUCT PREVIEW
27
3 VOLT ADVANCED+ BOOT BLOCK E
4.4DC Characteristics, Continued
V
CC
V
CCQ
2.7 V–3.6 V
2.7 V–3.6 V
SymParameterNoteMinMaxUnitTest Conditions
V
Input Low Voltage-0.40.4V
IL
-
V
V
Input High Voltage
IH
V
Output Low Voltage7 -0.100.10VVCC = VCCMin
OL
V
Output High Voltage7V
OH
V
PPLKVPP
V
PP1VPP
V
PP2
V
LKO
V
LKO2
NOTES:
1. All currents are in RMS unless otherwise noted. Typical values at nominal V
2. I
CCES
I
CCES
3. Erase and Program are inhibited when V
4. Sampled, not 100% tested.
5. Automatic Power Savings (APS) reduces I
6. Applying V
and 2500 cycles on the parameter blocks. V
3.4 for details.
7. The test conditions V
listed at the top of each column.
Lock-Out Voltage31.0VComplete Write Protection
during Program / Erase31.653.6V
Operations
V
Prog/Erase Lock Voltage
CC
V
Prog/Erase Lock
CCQ
3,611.412.6
Voltage
and I
and I
are specified with device de-selected. If device is read while in erase suspend, current draw is sum of
CCWS
. If the device is read while in program suspend, current draw is the sum of I
CCR
= 11.4 V–12.6 V during program/erase can only be done for a maximum of 1000 cycles on the main blocks
PP
Max, V
CC
CCQ
< V
PP
PPLK
to approximately standby levels in static operation (CMOS inputs).
CCR
may be connected to 12 V for a total of 80 hours maximum. See Section
PP
Max, VCCMin, and V
CCQ
0.4 V
-
CCQ
0.1 V
1.5V
1.2V
and not guaranteed outside the valid VPP ranges of V
Min refer to the maximum or minimum VCC or V
CCQ
V
V
, TA = +25 °C.
CC
V
= V
CCQ
I
= 100 µA
OL
= VCCMin
V
CC
V
= V
CCQ
I
= –100 µA
OH
CCWS
CCQ
CCQ
and I
CCR
Min
Min
.
PP1
CCQ
and V
voltage
PP2
.
28
PRODUCT PREVIEW
E3 VOLT ADVANCED+ BOOT BLOCK
V
0.0
Device
Under Test
CCQ
INPUTOUTPUT
Figure 7. Input Range and Measurement Points
V
CCQ
R
C
L
R
V
CCQ
1
2
2
Out
TEST POINTS
Test Configuration Component Values Table
Test ConfigurationCL (pF) R1 (Ω)R2 (Ω)
2.7 V–3.6 V Standard
Test
NOTE:
includes jig capacitance.
C
L
V
CCQ
2
5025K25K
0645_07
Figure 8. Test Configuration
PRODUCT PREVIEW
0645_08
29
3 VOLT ADVANCED+ BOOT BLOCK E
4.5AC Characteristics—Read Operations
(1)
—Extended Temperature
Product–90–110
V
CC
3.0 V–3.6 V 2.7 V–3.6 V 3.0 V–3.6 V 2.7 V–3.6 V
#SymParameterNoteMinMaxMinMaxMinMaxMinMax Unit
R1t
R2t
R3t
R4t
R5t
R6t
R7t
R8t
R9t
R10t
Read Cycle Time8090100110ns
AVAV
AVQV
ELQV
GLQV
PHQV
ELQX
GLQX
EHQZ
GHQZ
OH
Address to
Output Delay
CE# to Output
Delay
OE# to Output
Delay
RP# to Output
Delay
CE# to Output in
Low Z
OE# to Output in
Low Z
CE# to Output in
High Z
OE# to Output in
High Z
Output Hold from
Address, CE#, or
28090100110ns
2 30303030ns
30000ns
30000ns
3 20202020ns
3 20202020ns
30000ns
8090100110ns
150150150150ns
OE# Change,
Whichever
Occurs First
NOTES:
AC Waveform: Read Operations
1. See
2. OE# may be delayed up to t
3. Sampled, but not 100% tested.
4. See Test Configuration (Figure 8).
ELQV–tGLQV
.
after the falling edge of CE# without impact on t
ELQV
.
30
PRODUCT PREVIEW
E3 VOLT ADVANCED+ BOOT BLOCK
V
ADDRESSES (A)
CE# (E)
OE# (G)
WE# (W)
DATA (D/Q)
RP#(P)
IH
V
IL
V
IH
V
IL
V
IH
V
IL
V
IH
V
IL
V
OH
V
OL
V
IH
V
IL
Device and
Address Selection
Address Stable
R1
R4
R7
High Z
R6
R2
R5
R3
Valid Output
Figure 9. AC Waveform: Read Operations
Data
ValidStandby
R8
R9
R10
High Z
PRODUCT PREVIEW
31
3 VOLT ADVANCED+ BOOT BLOCK E
Product
(1)
—Extended Temperature
-90-110
4.6AC Characteristics—Write Operations
3.0 V – 3.6 V80100
2.7 V – 3.6 V90110
#SymbolParameterNoteMinMinMinMinUnit
/
t
W1
W2
W3
W4
W5
W6
W7
W8
W9
W10
W11t
PHWL
t
PHEL
t
ELWL
t
WLEL
t
ELEH
t
WLWH
t
DVWH
t
DVEH
t
AVWH
t
AVEH
t
WHEH
t
EHWH
t
WHDX
t
EHDX
t
WHAX
t
EHAX
t
WHWL /
t
EHEL
t
VPWH
t
VPEH
QVVL
RP# High Recovery to WE#
150150150150ns
(CE#) Going Low
/
CE# (WE#) Setup to WE#
0000ns
(CE#) Going Low
/
WE# (CE#) Pulse Width450607070ns
/
Data Setup to WE# (CE#)
2 50506060ns
Going High
/
Address Setup to WE# (CE#)
2 50607070ns
Going High
/
CE# (WE#) Hold Time from
0000ns
WE# (CE#) High
/
Data Hold Time from WE#
20000ns
(CE#) High
/
Address Hold Time from WE#
20000ns
(CE#) High
WE# (CE#) Pulse Width High430303030ns
/
V
Setup to WE# (CE#) Going
3200200200200ns
High
V
Hold from Valid SRD30000ns
PP
NOTES:
1. Write timing characteristics during erase suspend are the same as during write-only operations.
2. Refer to Table 5 for valid A
3. Sampled, but not 100% tested.
4. Write pulse width (t
(whichever goes high first). Hence, t
from CE# or WE# going high (whichever goes high first)
= t
WHWL
= t
EHEL
t
WPH
5. See Test Configuration (Figure 8).
32
or DIN.
IN
) is defined from CE# or WE# going low (whichever goes low last) to CE# or WE# going high
WP
= t
WHEL
= t
EHWL
WP
= t
= t
= t
= t
WLWH
ELEH
WLEH
to CE# or WE# going low (whichever goes low first). Hence,
.
. Similarly, Write pulse width high (t
ELWH
PRODUCT PREVIEW
) is defined
WPH
E3 VOLT ADVANCED+ BOOT BLOCK
4.7Erase and Program Timings
SymbolParameterNoteTyp
t
BWPB
t
BWMB
t
WHQV1
t
WHQV2
t
WHQV3
t
WHRH1
t
WHRH2
/ t
/ t
/ t
/ t
/ t
EHQV1
EHQV2
EHQV3
EHRH1
EHRH2
8-KB Parameter Block
Program Time (Byte)
4-KW Parameter Block
Program Time (Word)
64-KB Main Block
Program Time (Byte)
32-KW Main Block
Program Time(Word)
Byte Program Time2, 3171658185µs
Word Program Time2, 3222008185µs
8-KB Parameter Block
Erase Time (Byte)
4-KW Parameter Block
Erase Time (Word)
64-KB Main Block
Erase Time (Byte)
32-KW Main Block
Erase Time (Word)
Program Suspend Latency3510510µs
Erase Suspend Latency3520520µs
(1)
V
PP
2, 30.160.480.080.24s
2, 30.100.300.030.12s
2, 31.23.70.61.7s
2, 30.82.40.241s
2, 3150.84.8s
2, 30.550.44.8s
2, 31817s
2, 3180.67s
1.65 V–3.6 V11.4 V–12.6 V
(1)
MaxTyp
(1)
MaxUnit
NOTES:
1. Typical values measured at T
2. Excludes external system-level overhead.
3. Sampled, but not 100% tested.
= +25 °C and nominal voltages.
A
PRODUCT PREVIEW
33
3 VOLT ADVANCED+ BOOT BLOCK E
ABC DEF
V
WP#
PP
IH
V
IL
V
IH
V
IL
W2
V
IH
V
IL
V
IH
V
IL
V
IH
High Z
V
IL
V
IH
V
IL
V
IH
V
IL
2
V
PPH
V1
PPH
V
PPLK
V
IL
W1
A
IN
W5
A
IN
W8
(Note 1)
W6
W9
(Note 1)
W3
W4
W7
D
IN
D
IN
W10
Valid
SRD
W11
D
IN
ADDRESSES [A]
CE#(WE#) [E(W)]
OE# [G]
WE#(CE#) [W(E)]
DATA [D/Q]
RP# [P]
V [V]
NOTES:
1. CE# must be toggled low when reading Status Register Data. WE# must be inactive (high) when reading Status Register
Data.
A. V
Power-Up and Standby.
CC
B. Write Program or Erase Setup Command.
C. Write Valid Address and Data (for Program) or Erase Confirm Command.
D. Automated Program or Erase Delay.
E. Read Status Register Data (SRD): reflects completed program/erase operation.
F. Write Read Array Command.
Figure 10. AC Waveform: Program and Erase Operations
34
PRODUCT PREVIEW
E3 VOLT ADVANCED+ BOOT BLOCK
H
4.8Reset Operations
V
IH
RP# (P)
V
IL
(A) Reset during Read Mode
V
IH
RP# (P)
V
IL
(B) Reset during Program or Block Erase, <
V
IH
RP# (P)
V
IL
t
t
PLPH
Abort
Complete
t
PLRH
t
PLPH
t
PLRH
PLPH
Abort
Complete
Deep
Power-
Down
t
PHQV
t
PHWL
t
PHEL
t
PHQV
t
PHWL
t
PHEL
PLPHtPLR
t
PHQV
t
PHWL
t
PHEL
t
(C) Reset Program or Block Erase, >
t
PLPHtPLRH
Figure 11. AC Waveform: Reset Operation
Table 11. Reset Specifications
(1)
VCC 2.7V–3.6V
SymbolParameterNotesMinMaxUnit
t
PLPH
RP# Low to Reset during Read
(If RP# is tied to V
, this specification is not
CC
2,4100ns
applicable)
t
PLRH1
t
PLRH2
NOTES:
1. See Section 3.1.4 for a full description of these conditions.
2. If t
3. If RP# is asserted while a block erase or
4. Sampled, but not 100% tested.
RP# Low to Reset during Block Erase3,422µs
RP# Low to Reset during Program3,412µs
is < 100 ns the device may still reset but this is not guaranteed.
PLPH
word program operation is not executing, the reset will complete within 100 ns.
1. The 48-Ball µBGA package top side mark reads FXX0C3 where XX is the devi ce density. This mark is identical for both
x8 and x16 products. All product shipping boxes or trays provide the correct information regarding bus architecture,
however once the devices are removed from the shipping media, it may be difficult to differentiate based on the top side
mark. The device identifier (accessible through the Device ID command: see Section 3.2.2 for further details) enables x8
and x16 µBGA package product differentiation.
36
PRODUCT PREVIEW
E3 VOLT ADVANCED+ BOOT BLOCK
6.0ADDITIONAL INFORMATION
Order NumberDocument/Tool
210830
292216
292215
Contact your Intel
Representative
297874
NOTES:
1. Please call the Intel Literature Center at (800) 548-4725 to request Intel documentation. International customers should
contact their local Intel or distribution sales office.
2. Visit Intel’s World Wide Web home page at http://www.Intel.com or http://developer.intel.com for technical documentation
and tools.
1998 Flash Memory Databook
AP-658 Designing for Upgrade to the Advanced+ Boot Block Flash Memory
AP-657 Designing with the Advanced+ Boot Block Flash Memory
Architecture
3 Volt Advanced+ Boot Block Algorithms (‘C’ and assembly)
http://developer.intel.com/design/flcomp
Flash Data Integrator (FDI) Software Developer’s Kit
FDI Interactive: Play with Intel’s Flash Data Integrator on Your PC
(1,2)
PRODUCT PREVIEW
37
3 VOLT ADVANCED+ BOOT BLOCK E
APPENDIX A
WSM CURRENT/NEXT STATES
Command Input (and Next State)
Current
State
Read Array“1”Array Read Array Program SetupErase
Read Status“1” Status Read Array Program SetupErase
Check Status Register
80H = no error
30H = Lock Command
Sequence Error
Data = 90H
Addr = X
Block Lock Status Data
Addr = Second addr of block
Confirm Locking Change on
, DQ0. (See Block Locking
DQ
1
State Table for valid
combinations.)
Confirmed?
Locking Change
44
Locking
Change
No
Complete
Figure 16. Locking Operations Flowchart
PRODUCT PREVIEW
E3 VOLT ADVANCED+ BOOT BLOCK
Start
Write C0H
(Protection Reg.
Program Setup)
Write Protect. Register
Address/Data
Read Status Register
SR.7 = 1?
Yes
Full Status
Check if Desired
Program Complete
FULL STATUS CHECK PROCEDURE
Read Status Register
Data (See Above)
SR.3, SR.4 =
SR.1, SR.4 =
SR.1, SR.4 =
Program Successful
No
1, 1
VPP Range Error
0,1
Protection Register
Programming Error
1,1
Attempted Program to
Locked Register -
Aborted
Bus Operation
Write
Write
Read
Standby
Protection Program operations can only be addressed within the protection
register address space. Addresses outside the defined space will return an
error.
Repeat for subsequent programming operations.
SR Full Status Check can be done after each program or after a sequence of
program operations.
Write FFH after the last program operation to reset device to read array mode.
Bus Operation
Standby
Standby
Standby
SR.3 MUST be cleared, if set during a program attempt, before further
attempts are allowed by the Write State Machine.
SR.1, SR.3 and SR.4 are only cleared by the Clear Staus Register Command,
in cases of multiple protection register program operations before full status is
checked.
If an error is detected, clear the status register before attempting retry or other
error recovery.
Command
Protection Program
Setup
Protection Program
CommandComments
Data = C0H
Data = Data to Program
Addr = Location to Program
Status Register Data Toggle
CE# or OE# to Update Status
Register Data
This appendix defines the data s tructure or “database” returned by t he Common Flash I nterface (CFI) Query
command. System s oftware should parse this st ructure to gain critical information such as block s i ze, density,
x8/x16, and electrical specific ations. Once this information has been obtained, the sof tware will know which
command sets to use t o enable flash writes, block erases, and otherwise control t he flash component. The
Query is part of an overall specification for multiple c ommand set and control interface descript ions called
Common Flash Interface, or CFI.
C.1QUERY STRUCTURE OUTPUT
The Query “database” allows system software to gain critical information for controlling the flash component.
This section describes the device’s CFI-compliant interface that allows the host system to access Query data.
Query data are always presented on the lowest -order data out puts (DQ
the address relative to t he maximum bus width s upported by t he device. On this f amily of devic es, t he Query
table device starting address is a 10h, which is a word address for x16 devices or a byte address for x8
devices.
For a word-wide (x16) device, the first two bytes of the Query structure, “Q”, ”R”, and “Y” in ASCII, appear on
the low byte at word addresses 10h, 11h, and 12h. This CFI-compliant device outputs 00H dat a on upper
bytes. Thus, the device outputs ASCII “Q” in the low byte (DQ
At Query addresses cont aining two or more bytes of information, the l east signifi cant data by te is pres ented
at the lower address, and the most significant data byte is presented at the higher address.
In all of the following tabl es, addresses and data are represented in hexadecimal notati on, so the “h” s uffix
has been dropped. In addition, since the upper byt e of word
has been dropped from the table notation and onl y the lower byte value is shown. Any x16 device outputs can
be assumed to have 00h on the upper byte in this mode.
Table C1. Summary of Query Structure Output As a Function of Device and Mode
DeviceLocationQuery Data
8-Mbit x8/8-Mbit x 16, 16-Mbit x 8/16-Mbit x 161051 “Q”
(Word or Byte Addresses)1152 “R”
) and 00h in the high byte (DQ
0-7
wide devices is always “00h,” the leading “00”
-
1259 “Y”
) only. The numerical offs et v alue is
0-7
).
8-15
(Hex, ASCII)
46
PRODUCT PREVIEW
E3 VOLT ADVANCED+ BOOT BLOCK
Address
Byte Addressing:
Table C2. Example of Query Structure Output of x16 and x8 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 in Table D3.
The following sections describe the Query structure sub-sections in detail.
Word Addressing:
Query Data
0051h“Q”
0052h “R”
0059h“Y”
P_ID
P_ID
P
P
A_ID
A_ID
...
PrVendor ID# (Lo byte)
LO
PrVendor ID# (HI byte)
HI
PrVendor TblAddr (Lo)
LO
PrVendor TblAddr (Hi)
HI
AltVendor ID# (Lo)
LO
AltVendor ID# (Hi)
HI
D15–D
Byte
0
A7–A
10h
11h
12h
13h
14h
15h
16h
17h
18h
...
0
51h“Q”
52h“R”
59h“Y”
P_ID
P_ID
P
P
A_ID
A_ID
Query Data
D7–D
PrVendor ID# (Lo)
LO
PrVendor ID# (Hi)
HI
PrVndr TblAdr (Lo)
LO
PrVndr TblAdr (Hi)
HI
AltVndr ID# (Lo)
LO
AltVndr ID# (Hi)
HI
0
Table C3. Query Structure
OffsetSub-Section NameDescription
00hManufacturer Code
01hDevice Code
02-0Fh
10hCFI Query Identification StringCommand set ID and vendor data offset
1BhSystem Interface InformationDevice timing & voltage information
27hDevice Geometry DefinitionFlash device layout
(3)
P
NOTES:
1. Refer to Section D.1 and Table D1 for the detailed definition of offset address as a function of device bus width and mode.
2. BA = The beginning location of a Block Address (e.g., 08000h is the beginning location of block 1 when the block size is
32 Kword).
3. Offset 15 defines “P” which points to the Primary Intel
ReservedReserved for vendor-specific information
Primary Intel-specific Extended Query
table
-
specific Extended Query Table.
(1)
Vendor-defined additional information
specific to the Primary Vendor Algorithm
PRODUCT PREVIEW
47
3 VOLT ADVANCED+ BOOT BLOCK E
C.3BLOCK LOCK STATUS
The Block Lock Status indicates the locking settings of a block.
Table C4. Block Lock Status Register
OffsetLength
(BA+2)h
NOTE:
1. BA = The beginning location of a Block Address (i.e., 008000h is the beginning location of block 1 in word mode.)
C.4CFI QUERY IDENTIFICATION STRING
(bytes)
(1)
01hBlock Lock StatusBA+2:
DescriptionC3
x16 Device/Mode
(see Section 3.3)
The Identification String provides verification that the component supports the Common Flash Interface
specification. A dditionally , it indic ates which v ersion of the spec and which vendor
is (are) supported.
Table C5. CFI Identification
OffsetLength
10h03hQuery-Unique ASCII string “QRY“10: 51
13h02hPrimary Vendor Command Set and Control Interface
15h02hAddress for Primary Algorithm Extended Query
17h02hAlternate Vendor Command Set and Control
19h02hAddress for Secondary Algorithm Extended Query
(Bytes)
ID Code
16
-
bit ID Code for Vendor-Specified Algorithms
Table
Offset value =
Interface ID Code
Second Vendor
Note: 0000h means none exists
Table
Note: 0000h means none exists
Description8-Mbit, 16-Mbit, 32-Mbit
P
= 35h
-
Specified Algorithm Supported
-
specified command set (s)
11: 52
12: 59
13: 03
14: 00
15: 35
16: 00
17: 00
18: 00
19: 00
1A: 00
48
PRODUCT PREVIEW
E3 VOLT ADVANCED+ BOOT BLOCK
C.5SYSTEM INTERFACE INFORMATION
The following device information can be useful in optimizing system interface software
Table C6. System Interface Information
OffsetLength
1Bh01hVCC Logic Supply Minimum Program/Erase Voltage
1Ch01hVCC Logic Supply Maximum Program/Erase Voltage
This field provides critical details of the flash device geometry.
Table C7. Device Geometry Definition
OffsetLength (bytes)Description
27h01hDevice Size = 2N in Number of Bytes
28h02hFlash Device Interface Description
value
28:00, 29:00x8 asynch
28:01,29:00x16 asynch
2Ah02hMaximum Number of Bytes in Write Buffer = 2
2Ch01hNumber of Erase Block Regions within Device:
bits 7–0 = x = # of Erase Block Regions
2Dh04hErase Block Region Information
bits 15–0 = y, Where y+1 = Number of Erase Blocks of Identical
Size within Region
bits 31–16 = z, Where the Erase Block(s) within This Region are
(z) × 256 Bytes
Device Geometry Definition
Offset8 Mbit16 Mbit32 Mbit
-T-B-T-B-T-B
27h27:1427:1427:1527:1527:1627:16
28h28:00 (008)
29:00 (008)
28:01 (800)
29:00 (800)
2Ah2A:00
2B:00
2Ch2C:022C:022C:022C:022C:022C:02
2Dh2D:0E
2E:00
2F:00
30:01
31:07
32:00
33:20
34:00
28:00 (008)
29:00 (008)
28:01 (800)
29:00 (800)
2A:00
2B:00
2D:07
2E:00
2F:20
30:00
31:0E
32:00
33:00
34:01
28:00 (016)
29:00 (016)
28:01 (160)
29:00 (160)
2A:00
2B:00
2D:1E
2E:00
2F:00
30:01
31:07
32:00
33:20
34:00
meaning
28:00 (016)
29:00 (016)
28:01 (160)
29:00 (160)
2A:00
2B:00
2D:07
2E:00
2F:20
30:00
31:1E
32:00
33:00
34:01
N
28:00 (032)
29:00 (032)
28:01 (320)
29:00 (320)
2A:00
2B:00
2D:3E
2E:00
2F:00
30:01
31:07
32:00
33:20
34:00
28:00 (032)
29:00 (032)
28:01 (320)
29:00 (320)
2A:00
2B:00
2D:07
2E:00
2F:20
30:00
31:3E
32:00
33:00
34:01
50
PRODUCT PREVIEW
E3 VOLT ADVANCED+ BOOT BLOCK
C.7INTEL-SPECIFIC EXTENDED QUERY TABLE
-
Certain flash features and c om m ands are optional. The Intel
other similar types of information.
Table C8. Primary-Vendor Specific Extended Query
(1)
Offset
(P)h03hPrimary Extended Query Table
(P+3)h01hMajor Version Number, ASCII38:31
(P+4)h01hMinor Version Number, ASCII39:30
(P+5)h04hOptional Feature & Command Support
(P+9)h01hSupported Functions after Suspend
(P+A)h02hBlock Lock Status
Length
(bytes)
Description8-Mbit, 16-Mbit,
Unique ASCII String “PRI“
bit 0 Chip Erase Supported(1=yes, 0=no)
bit 1 Suspend Erase Supported(1=yes, 0=no)
bit 2 Suspend Program Supported (1=yes, 0=no)
bit 3 Lock/Unlock Supported(1=yes, 0=no)
bit 4 Queued Erase Supported(1=yes, 0=no)
bits 5–31 reserved for future use; undefined bits
are “0”
Read Array, Status, and Query are always supported
during suspended Erase or Program operation. This field
defines other operations supported.
bit 0 Program Supported after Erase Suspend
(1=yes, 0=no)
bits 1-7 reserved for future use; undefined bits are “0”
Defines which bits in the Block Status Register section of
the Query are implemented.
bit 0 Block Lock Status Register Lock/Unlock bit
(bit 0) active
(1=yes, 0=no)
bit 1 Block Lock Status Register Lock-Down bit
(bit 1) active
(1=yes, 0=no)
Bits 2—15 reserved for future use. Undefined bits
are 0.
Specific Ext ended Query t able spec if ies t his and
32-Mbit
35:50
36:52
37:49
3A:06
3B:00
3C:00
3D:00
3E:01
3F: 03
40:00
PRODUCT PREVIEW
51
3 VOLT ADVANCED+ BOOT BLOCK E
Table C8. Primary-Vendor Specific Extended Query (Continued)
(1)
Offset
(P+C)h01hVCC Logic Supply Optimum Program/Erase voltage
x80000089
Device Code
8-Mbit x 16-Tx160000188C0
8-Mbit x 16-Bx160000188C1
16-Mbit x 16-Tx160000188C2
16-Mbit x 16-Bx160000188C3
32-Mbit x 16-Tx160000188C4
32-Mbit x 16-Bx160000188C5
8-Mbit x 8-Tx800001C0
8-Mbit x 8-Bx800001C1
16-Mbit x 8-Tx800001C2
16-Mbit x 8-Bx800001C3
32-Mbit x 8-Tx800001C4
32-Mbit x 8-Bx800001C5
NOTE: Other locations within the configuration address space are reserved by Intel for future use.