—48-Ball CSP Packages
—40- and 48-Lead TSOP Packages
■ Density and Footprint Upgradeable for
common package
—4-, 8-, 16-, 32- and 64-Mbit Densities
■ ETOX™ VII (0.18 µ) Flash Technology
—28F160/320/640B3xC
—4-, 8-, 16-, and 32-Mbit also exist on
ETOX™ V (0.4µ) and/or ETOX ™ VI
(0.25µ) Flash Technology
■ x8 not recommended for new designs
■ 4-Mbit density not recommended for new
designs
The 3 Volt Advanced Boot Block flash memory, manufactured on Intel’s latest 0.18 µm
technology, represents a feature-rich solution at overall lower system cost. The 3Volt Advanced
Boot Block flash memory products in x16 will be available in 48-lead TSOP and 48-ball CSP
packages. The x8 option of this product family will o nly be available in 40-lead TSOP and 48ball µBGA* packages. Additional information on this product family can be obtained by
accessing Intel’s website at: http://www.intel.com/design/flash.
Notice: This document contains preliminary information on new products in production. 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.
Order Number: 290580-012
October 2000
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.
Designers must not rely on the absence or characteristics of any features or instructions marked "reserved" or "undefined." Intel reserves these for
future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them.
The 28F004/400B3, 28F008/800B3, 28F016/160B3, 28F320B3, 28F640B3 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 by calling 1-800-
Program and Erase Suspend Latency specification change
Updated Appendix A:
Updated Figure, Appendix D:
Minor wording changes
Combined byte-wide specification (previously 290605) with this document
Improved speed specification to 80 ns (3.0 V) and 90 ns (2.7 V)
Improved 1.8 V I/O option to minimum 1.65 V (Section 3.4)
Improved several DC characteristics (Section 4.4)
Improved several AC characteristics (Sections 4.5 and 4.6)
Combined 2.7 V and 1.8 V DC characteristics (Section 4.4)
Added 5 V V
Removed 120 ns and 150 ns speed offerings
Moved
Moved
Updated figure Appendix B,
Updated figure Appendix C,
Moved Program and Erase Flowcharts to Appendix E
Updated
Updated
Minor text edits throughout
Added 32-Mbit density
Added 98H as a reserved command (Table 4)
A
1–A20
Status register clarification for SR3 (Table 7)
and V
V
CC
Combined I
Combined I
Max Parameter Block Erase Time (t
Max Main Block Erase Time (t
Erase suspend time @ 12 V (t
(Section 4.7)
Ordering Information
Write State Machine Current/Next States Table updated (Appendix A)
Program Suspend/Resume Flowchart updated (Appendix F)
Erase Suspend/Resume Flowchart updated (Appendix F)
Text clarifications throughout
µBGA package diagrams corrected (Figures 3 and 4)
I
PPD
32-Mbit ordering information corrected (Section 6)
µBGA package top side mark information added (Section 6)
V
IH
I
CCS
Added Command Sequence Error Note (Table 7)
Datasheet renamed from
Memory Family.
Added device ID information for 4-Mbit x8 device
Removed 32-Mbit x8 to reflect product offerings
Minor text changes
Corrected RP# pin description in Table 2,
Corrected typographical error fixed in
Automated Block Erase Flowchart
, added
Erase Suspend/Resume Flowchart
AC Waveform: Program and Erase Operations
Ordering Information
(included 8 M and 4 M information)
Architecture Block Diagram
read specification (Section 3.4)
from Appendix to Section 6.0; updated information
from Appendix to Section 7.0
Access Time vs. Capacitive Load
Architecture Block Diagram
and I
and I
into one specification (Section 4.4)
CCW
into one specification (Section 4.4)
CCE
updated (Section 6.0)
WHQV2/tEHQV2
WHQV3/tEHQV3
WHRH2/tEHRH2
) reduced to 5 sec (Section 4.7)
) changed to 5 µs typical and 20 µs maximum
This datasheet contains the specifications for the 3 Volt Advanced Boot Block flash memory
family, which is optimized for low power, portable systems. This family of products features
1.65 V–2.5 V or 2.7 V–3.6 V I/Os and a low V
program, and erase operations. In addition this family is capable of fast programming at 12 V.
Throughout this document, the term “2.7 V” refers to the full voltage range 2.7 V–3.6 V (except
where noted otherwise) and “V
overview of the flash memory family including applications, pinouts and pin descriptions. Section
3.0 describes the memory organization and operation for these products. Sections 4.0 and 5.0
contain the operating specifications. Finally, Sections 6.0 and 7.0 provide ordering and other
reference information.
The 3 Volt Advanced Boot Block flash memory features:
• Enhanced blocking for easy segmentation of code and data or additional design flexibility
• Program Suspend to Read command
operating range of 2.7 V–3.6 V for read,
CC/VPP
= 12 V” refers to 12 V ±5%. Section 1.0 and 2.0 provide an
PP
• V
input of 1.65 V–2.5 V on all I/Os. See Figures 1 through 4 for pinout diagrams and
CCQ
V
location
CCQ
• Maximum program and erase time specification for improved data storage.
Table 1. 3 Volt Advanced Boot Block Feature Summary
(2)
(2)
Feature
Read Voltage2.7 V– 3.6 V
V
CC
I/O Voltage1.65 V–2.5 V or 2.7 V– 3.6 VSection 4.2, 4.4
V
CCQ
Program/Erase Voltage2.7 V– 3.6 V or 11.4 V– 12.6 VSection 4.2, 4.4
Intel provides the most flexible voltage soluti on in the flash industry, providing three discrete
voltage supply pins: V
erase operation. All 3 Volt Advanced Boot Block flash memory products provide program/erase
capability at 2.7 V or 12 V (for fast production programming) and read with V
many designs read from the flash memory a larg e percentage of the time, 2.7V V
provide substantial power savings.
The 3 Volt Advanced Boot Block flash memory products ar e available in either x8 or x16 packages
in the following densities: (see Section 6.0, “Ordering Information” on page 34 for availability.)
• 4-Mbit (4,194,304-bit) flash memory organized as 256 Kwords of 16 bits each or 512 Kbytes
of 8-bits each
• 8-Mbit (8,388,608-bit) flash memory organized as 512 Kwo rds of 16 b its each or 1 024 Kbytes
of 8-bits each
• 16-Mbit (16,777,216-bit) flash memory organized as 1024 Kwords of 16 bits each or
2048 Kbytes of 8-bits each
• 32-Mbit (33,554,432-bit) flash memory organized as 2048 Kwords of 16 bits each
for read o peration, V
CC
for output swing, and VPP for program and
CCQ
at 2.7 V. Since
CC
operation can
CC
• 64-Mbit (67,108,864-bit) flash memory organized as 4096 Kwords of 16 bits each
The parameter blocks are located at either the top (denoted by -T suffix) or the bottom (-B suffix)
of the address map in order to accommodate different microprocessor protocols for kernel code
location. The upper two (or lower two) parameter blocks can be locked to provide complete code
security for system initialization code. Locking and unlocking is controlled by WP# (see Section
3.3, “Block Locking” on page 14 for detai ls).
The Command User Interface (CUI) serves 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 un-burdening the microprocessor or microcontroller.
The status register indicates the status of the WSM by signifying block erase or word program
completion and status.
The 3 Volt Advanced Boot Block flash memory is also designed with an Automatic Power Savings
(APS) feature which minimizes system current drain, allowing for very low power designs. This
mode is entered following the completion of a read cycle (approximately 300 ns later).
The RP# pin provides additional protection against unwanted command writes that may occur
during system reset and power-up/down sequences due to invalid system bus conditions (see
Section 3.6, “Power-Up/Down Operation” on page 16).
Section 3.0, “Principles of Operation” on page 7 gives detailed explanation of the different modes
of operation. Complete current and voltage specifications can be found in Section 4.4, “DC
Characteristics” on page 20. Refer to Section 4.5, “AC Characteristics —Read Operations” on
page 23 for read, program and erase performance specifications.
This section explains device pin description and package pinouts.
2.1Package Pinouts
The 3 Volt Advanced Boot Block flash memory is available in 40-lead TSOP (x8, Figure 1),
48-lead TSOP (x16, Fig u r e 2 ) and 48- bal l µBGA(x8 and x16, Figure 3 and Figure 4, respectively)
and 48-ball VF BGA (x16, Figure 4) packages. In all figures, pin changes necessary for density
upgrades have been circled.
Figure 1. 40-Lead TSOP Package for x8 Configurations
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
16-Mbit device.
Figure 4. x16 48-Ball Very Thin Profile Pitch BGA and µBGA* Chip Size Package (Top View,
Ball Down)
13254768
16M
A
A
13
A
11
A
8
V
PP
WP#
A
19
A
7
A
4
B
C
D
E
F
NOTES:
A
14
A
15
A
16
V
CCQ
GNDD
A
10
A
12
D
14
D
15
7
WE#
A
9
D
5
D
6
D
13
64M
RP#
A
21
D
11
D
12
D
A
18
A
17
A
5
A
2
32M
A
20
D
2
D
3
4
V
CC
A
6
D
8
D
9
D
10
A
CE#
D
D
3
0
1
A
A
GND
OE#
1
0
0580_03
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
16-Mbit device. A
device.
is the upgrade address for the 32-Mbit device. A21 is the upgrade address for the 64-Mbit
20
is the upgrade address for the
19
2. 4-Mbit density not available in µBGA CSP.
T able 2, “3 Volt Advanced Boot Block Pin Description s” on page 6 details the usage of each device
DATA INPUTS/OUTPUTS: Inputs array data on the second CE# and 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, i dentifier and status register data. The dat a pins float to tri-state when
the chip is de-selected or the outputs are disabled.
DATA INPUTS/OUTPUTS: Inputs array data on the second CE# and WE# cycle during a Program
command. Data is internally latched. Outputs array and identifier data. The data pins float to tri-state
when the chip is de-selected. Not included on x8 products.
CHIP ENABLE: Activates the internal control logic, input buffers, decoders and sense amplifiers. CE#
is active low. CE# high de-selects the memory device and reduces power consumption to standby
levels.
OUTPUT ENABLE: Enables the device’s outputs through the data buffers during a read operation.
OE# is active low.
WRITE ENABLE: Controls writes to the Command Register and memory array. WE# is active low.
Addresses and data are latched on the rising edge of the second WE# pulse.
RESET/DEEP POWER-DOWN: Uses two voltage levels (V
mode.
, VIH) to control reset/deep power-down
IL
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 logiclow to logic-high, the device defaults to the read array mode.
WRITE PROTECT: Provides a method for locking and unlocking the two lockable parameter blocks.
When WP# is at logic low, the lockable blocks are locked, preventing program and erase
operations to those blocks. If a program or erase operation is attempted on a locked block, SR.1 and
either SR.4 [program] or SR.5 [erase] will be set to indicate the operation failed.
When WP# is at logic high, the lockable blocks are unlocked and can be programmed or erased.
See Section 3.3 for details on write protection.
OUTPUT V
is regulated to 2.7 V–2.85 V, V
V
CC
operation (see Section 4.4
This input may be tied directly to V
: Enables all outputs to be driven to 1.8 V – 2.5 V while the VCC is at 2.7 V–3.3 V. If the
CC
)
.
can be driven at 1.65 V–2.5 V to achieve lowest power
CCQ
(2.7 V–3.6 V).
CC
DEVICE POWER SUPPLY: 2.7 V–3.6 V
PROGRAM/ERASE POWER SUPPLY: Supplies power for program and erase operations. VPP may
be the same as V
manufacturing, 11.4V–12.6 V may be supplied to V
11.4 V–12.6 V to V
cycles on the parameter blocks.
Section 3.4 for details).
< V
V
PP
PPLK
commands.
(2.7 V–3.6 V) for single supply voltage operation. For fast programming at
CC
can only be done for a maximum of 1000 cycles on the main blocks and 2500
PP
may be connected to 12 V for a total of 80 hours maximum (see
VPP
. This pin cannot be left floating. Applying
PP
protects memory contents against inadvertent or unintended program and erase
7
INPUT
INPUT/
OUTPUT
INPUT/
OUTPUT
A
0–A21
DQ
DQ
DQ
–DQ
0
–
8
15
CE#INPUT
OE#INPUT
WE#INPUT
RP#INPUT
WP#INPUT
V
V
V
CCQ
CC
PP
INPUT
GNDGROUND: For all internal circuitry. All ground inputs must be connected.
NCNO CONNECT: Pin may be driven or left floating.
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 add ress locatio ns of each block , see the m emory maps in
Appendix C.
2.2.1Parameter Blocks
The 3 Volt Advanced Boot Block flash memory architecture includes parameter blocks to facilitate
storage of frequently updated small parameters (e.g., data that would normally be stored in an
EEPROM). By using software techniques, the word-rewrite functionality of EEPROMs can be
emulated. Each device contains eight parameter blocks of 8-Kbytes/4-Kwords (8192 bytes/4,096
words) each.
2.2.2Main Blocks
After the parameter blocks, the remainder of the array is divided into equal size main blocks
(65,536 bytes/32,768 words) for data or code storage. The 4-Mbit device contains seven main
blocks; 8-Mbit device contains fifteen main blocks; 16-Mbit flash has thirty-one main blocks;
32-Mbit has sixty-three main blocks; 64-Mbit has one hundred twenty-seven main blocks.
3.0Principles of Operation
Flash memory combines EEPROM functionality with in-circuit electrical program and erase
capability. The 3 Volt Advan ced Boot Block flash memory family utilizes a Command User
Interface (CUI) and automated algorithms to simplify program and erase operations. The CUI
allows for 100% CMOS-level control inputs and fixed power su ppl ie s duri ng erasu re and
programming.
When V
Array, Read Status Register, Clear Status Register and Read Identifier. The device provides
standard EEPROM read, standby and output disable operations. Manufacturer identification and
device identification data can be accessed through the CUI. All functions associated with altering
memory contents, namely program and erase, are accessible via the CUI. The internal Write State
Machine (WSM) completely automates program and erase operations while the CUI signals the
start of an operation and the status register reports status. The CUI handles the WE# interface to the
data and address latches, as well as system status requests during WSM operation.
3.1Bus Operation
3 Volt Advanced Boot Block flash memory devices read, program and erase in-system via the 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.
PP
< V
, the device will only execute the following commands successfully: Read
1. 8-bit devices use only DQ[0:7], 16-bit devices use DQ[0:15].
2. X must be V
DC Characteristics
3. See
4. Manufacturer and device codes may also be accessed in read identifier mode (A
5. Refe r to Table 6 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.
(1)
, VIH for control pins and addresses.
IL
for V
PPLK
during a write operation.
IN
3.1.1Read
The flash memory has four read modes available: read array, read identifier, read status and read
query. These modes are accessible independent of the V
command must be issued to the CUI to enter the co rres ponding mode. Upon initial device powerup or after exit from reset, the device automatically defaults to read array mode.
CE# and OE# must be driven active to obtain data at the outputs. CE# is the device selection
control; when active it enables the flash memory device. OE# is the data output control and it
drives the selected memory data onto the I/O bus. For all read modes, WE# and RP# must be at
V
. Figure 7 illustrates a read cycle.
IH
, V
IH
IH
IH
IL
IH
PP1
, V
0–7
V
IL
V
IL
V
IH
XXXHigh ZHigh Z
V
IL
, V
PP3
, V
PP2
V
IL
V
IH
XXHigh ZHigh Z
V
IH
voltages.
PP4
.
IH
voltage. The appropriate Read Mode
PP
V
IH
V
IH
V
IL
D
OUT
High ZHigh Z
D
IN
= 0). See Table 5.
1–A21
DQ
D
OUT
D
8–15
IN
3.1.2Output Disable
With OE# at a logic-high level (VIH), the device outputs are disabled. Output pins are placed in a
high-impedance state.
3.1.3Standby
Deselecting the device by bringing 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 high-impedance state independent of OE#. If
deselected during program or erase operation, the device continues to consume active power until
the program or erase operation is complete.
3.1.4Deep Power-Down / Reset
From read mode, RP# at VIL for time t
impedance state, and turns off all internal circuits. After r eturn from reset, a time t
until the initial read access outputs are valid. A delay (t
reset before a write can be initiated. After this wake-up interval, normal operation is restored. The
CUI resets to read array mode, and the status register is set to 80H. This case is shown in
Figure 9A.
83UHOLPLQDU\
deselects the memory, places output drivers in a high-
If RP# is taken low for time t
aborted and the memory contents at th e abo rted location (for a program) or block (for an erase) ar e
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
array mode (if RP# h as go ne hi gh dur ing t
low after t
time t
discussed in the previous paragraph. However, in this case, these delays are referenced to the end
of t
PLRH
As with any automated device, it is important to assert RP # during system reset. When the system
comes out of reset, processor expects 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. Intel
proper CPU initialization following a sy stem reset through the use of the RP# input. In this
application, RP# is controlled by the same RESET# signal that resets the system CPU.
3.1.5Write
A write takes place when both 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 addr essable m emor y loca tio n. The ad dress and data buses
are latched on the rising edge of the second WE# or CE# pulse, whichever occurs first. Figure 8
illustrates a program and erase operation. The available commands are shown in Table 6, and
Appendix A provides detailed information on moving between the different modes of op eration
using CUI commands.
during a program or erase operation, the operation will be
PLPH
to complete. After this time t
PLRH
, Figure 9C). In both cases, after returning from an aborted operation, the relevant
PLRH
PHQV
or t
PHWL/tPHEL
must be waited before a read or write operation is initiated, as
rather than when RP# goes high.
, the part will either reset to read
, Figure 9B) or enter reset mode (if RP# is still logic
PLRH
PLRH
®
Flash memories allow
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 internallytimed functions that culminate in the completion of the requested task (unless that operation is
aborted by either RP# being driven to V
3.2Modes of Operation
The flash memory has four read modes and two write modes. The read modes are read array, read
identifier, read status and read query (see Appendix B). The write modes are program and block
erase. Three additional modes (erase suspend to program, erase suspend to read and program
suspend to read) are available only during suspended operations. These modes are reached using
the commands summarized in Table 4. A comprehensive chart showing the state transitions is in
Appendix A.
3.2.1Rea d A rray
When RP# transitions from VIL (reset) to VIH, the device defaults to read array mode and will
respond to the read control inputs (CE#, address inputs, 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
)
IH
)
IL
)
IL
)
IH
In addition, the address of the desired location must be applied to the address pins. If the device is
not in read array mode, as would be the case after a program or erase operation, the Read Array
command (FFH) must be written to the CUI before array reads can take place.
Table 4. Command Codes and Descriptions
CodeDevice ModeDescription
00, 01,
60, 2F,
C0, 98
FFRead ArrayPlaces the device in read array mode, such that array data will be output on the data pins.
40Program Set-Up
10
20Erase Set-Up
D0
B0
70
50
90Read Identifier
Invalid/
Reserved
Alternate
Program Set-Up
Erase Confirm
Program / Erase
Resume
Program / Erase
Suspend
Read Status
Register
Clear Status
Register
Unassigned commands that should not be used. Intel reserves the right to redefine these
codes for future functions.
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.4.
(See 40H/Program Set-Up)
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.5.
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 erase, the
device will only respond to the Read Status Register and Erase Suspend comm ands. The
device 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
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 it is driven to V
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) , V
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 intelligent identifier read mode, so that reading the device will output
the manufacturer and device codes (A
address inputs must be 0). See Section Section 3.2.2.
. See Section 3.2.4.1 and Section 3.2.4.1.
IL
status (SR.3), program status (SR.4), and
PP
= 0 for manufacturer, A0 = 1 for device, all other
0
NOTE: See Appendix A for mode transition information.
103UHOLPLQDU\
3.2.2Rea d Ident if ier
To read the manufacturer and device codes, the device must be in read identifier mode, which can
be reached by writing the Read Identifier command (90H). Once in read identifier mode, A
outputs the manufacturer’s identification code and A
The device status register indicates when a program or erase operation is complete and the success
or failure of that operation. To read the status register issue the Read Status Register (70H)
command to the CUI. This causes all subsequent read operations to output data from the status
register until another command is written to the CUI. To return to reading from the array, issue the
Read Array (FFH) command.
The status register bits are output on DQ
Read Status Register command.
The contents of the status register are latched on the falling edge of OE# or CE#. This prevents
possible bus errors which might occur if status register contents 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.
D4HD5H
D2HD3H
8890H8891H
–DQ7. The upper byte, DQ8–DQ15, outputs 00H during a
0
When the WSM is active, SR.7 will indicate the status of the WSM; the remaining bits in the status
register indicate whether or not the WSM was successful in performing the desired operation (see
Table 7 on page 14).
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.” Because bits 1, 3, 4 and 5 indicate various error conditions, these
bits can only be cleared through 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 to determine if an error occurred during that series. Clear the status
register before beginning another command or sequence. Note, again, that the Read Array
command must be issued before data can be read from the memory array.
3.2.4Program Mode
Programming is executed using a two-write sequence. The Program Setup command (40H) is
written to the CUI followed by a second 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 progr am sequence executes, status bit 7
is “0.” The status register can be polled 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 should be checked. If the programming
operation was unsuccessful, bit SR.4 of the status register is set to indicate a program failure. If
SR.3 is set then V
command. If SR.1 is set, a program operation was attempted on a locked block and the operation
was aborted.
was not within acceptable limits, and the WSM did not execute the program
PP
The status register should be cleared before attempting the next operation. 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.4.1Suspending and Resuming Program
The Program Suspend halts the in-progres s program operation to read data from another location of
memory . Once the programming pr ocess starts, writing the Program Suspend comm and to the CUI
requests that the WSM suspend the program sequence (at predetermined points in the program
algorithm). The device continues t o output status reg ister data after the Program Su spend 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
A Read Array command can now be written to the CUI to read data from bloc ks other than that
which is suspended. The only other valid commands while program is suspended, are Read Status
Register, Read Identifier, and Program Resume. After the Program Resume command is written to
the flash memory, the WSM will continue with the program process and status register bits SR.2
and SR.7 will automatically be cleared. After the Program Resume command is written, the device
automatically outputs status register data when read (see Appendix E for Program Suspend and Resume Flowchart). V
suspend mode. RP# must also remain at V
must remain at the same VPP level used for program while in program
PP
IH.
3.2.5Erase Mode
To erase a block, write the Erase Set-up and Erase 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 issued. Block erasure results in all bits within the block being set 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 bits within the block to “1,” then verify that 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, the WSM will not execute the erase sequence; instead,
SR.5 of the status register is set to indicate an erase error, and SR.3 is set to a “1” to identify that
V
supply voltage was not within acceptable limits.
PP
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 advisable to place the flash in read array mode after the erase is complete.
3.2.5.1Suspending and Resuming Erase
Since an erase operation requires on the o rder of se cond s to complete, an Erase Suspend command
is provided to allow erase-sequence interruption in order to read data from or program data to
another block in memory. Once the erase sequence is started, writing the Erase Suspend command
to the CUI requests that the WSM pause the erase sequence at a predetermined point in the erase
algorithm. The status register will indicate if/when the erase operation has been suspended.
A Read Array/Program command can now be written to the CUI in order to read data from/
program data to blocks other than the one currently suspended. The Program command can
subsequently be suspended to read yet another array location. The only valid commands while
erase is suspended are Erase Resume, Program, Read Array, Read Status Register, or Read
Identifier. During erase suspend mode, the chip can be placed in a pseudo-standby mode by taking
CE# to V
. This reduces active current consumption.
IH
was not within acceptable limits after
PP
Erase Resume continues the erase sequence when CE# = V
operation, the status register must be read and cleared before the next instruction is issued.
Table 6. Command Bus Definitions
CommandNotesOperAddrDataOperAddrData
Read ArrayWriteXFFH
Read Identifier2WriteX90HReadIAID
Read Status RegisterWriteX70HReadXSRD
Clear Status RegisterWr iteX50H
1 = Error in Word Program
0 = Successful Word Program
SR.3 = V
SR.2 = PROGRAM SUSPEND STATUS (PSS)
SR.1 = BLOCK LOCK STATUS
SR.0 = RESERVED FOR FUTURE ENHANCEMENTS (R)This bit is reserved for future use and should be masked out
STATUS (VPPS)
PP
Low Detect, Operation Abort
1 = V
PP
OK
0 = V
PP
1 = Program Suspended
0 = Program in Progress/Completed
1 = Program/Erase attempted on locked block;
Operation aborted
0 = No operation to locked blocks
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 at “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.
The V
V
Program or Erase command sequences have been entered,
and informs the system if V
V
WSM. The V
feedback between V
max and V
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.
when polling the status register.
status bit does not provide continuous indication of
PP
level. The WSM interrogates VPP level only after the
PP
has not been switched on. The
PPLK
PP
max and V
min or between V
PP1
is also checked before the operation is verified by the
PP
status bit is not guaranteed to report accurate
PP
min.
PP4
PP1
NOTE: A Command Sequence Error is indicated when both SR.4, SR.5 and SR.7 are set.
3.3Block Locking
The 3 Volt Advanced Boot Block flash memory architecture features two hardware-lockable
parameter blocks.
3.3.1WP# = VIL for Block Locking
The lockable blocks are locked when WP# = VIL; any program or erase oper ation to a locked b lock
will result in an error, which will be reflected in the status register. For top configuration, the top
two parameter blocks (blocks #133 and #134 for the 64 Mbit, #69 and #70 for the 32 Mbit, blocks
#37 and #38 for the 16 Mbi t, b locks #2 1 and #22 for th e 8 Mbi t, b locks # 13 and #14 f or the 4 Mbi t)
are lockable. For the bottom configuration, the bottom two parameter blocks (blocks #0 and #1 for
4 /8 /16 /32/64 Mbit) are lockable. Unlocked blocks can be programmed or erased no rmally (unless
V
WP# = VIH unlocks all lockable blocks.
These blocks can now be programmed or erased.
Note that RP# does not ov erri d e WP # l o cki ng as i n prev i ous Bo ot B loc k d evi ces . WP# controls all
block locking and V
protection methods.
Table 8. Write Protection Truth Table for the Advanced Boot Block Flash Memory Family
provides protection against spurious writes. Table 8 defines the write
PP
V
PP
XXV
V
IL
≥ V
PPLK
≥ V
PPLK
WP#RP#Write Protection Provided
All Blocks Locked
IL
XVIHAll Blocks Locked
V
IL
V
IH
V
V
Lockable Blocks Locked
IH
All Blocks Unlocked
IH
3.4VPP Program and Erase Voltages
Intel® 3 Volt Advanced Boot Block products provide in-system programming and erase at 2.7 V.
For customers requiring fast programming in their manufacturing environment, 3 Volt Advanced
Boot Block includes an additional low-cost 12V programming feature.
The 12 V V
found in manufacturing processes; however, it is not intended for extended use. 12V may be
applied to V
blocks and 2500 cycles on the parameter blocks. V
hours maximum.
Warning:Stressing the device beyond these limits may cause permanent damage.
During read operations or idle times, V
operations, a 5 V supply is not permitted. The V
11.4 V–12.6 V during program and erase operations.
mode enhances programming performance during the short period of time typically
PP
during program and erase operations for a maximum of 1000 cycles on the main
PP
may be tied to a 5 V supply. For program and erase
PP
may be connected to 12 V for a total of 80
PP
must be supplied with either 2.7 V–3.6 V or
PP
3.4.1VPP = VIL for Complete Protection
The VPP programming voltage can be held low for complete write protectio n of all blocks in the
flash device. When V
is below V
PP
, any program or erase operation will result in a error,
PPLK
prompting the corresponding status register bit (SR.3) to be set.
3.5Power Consumption
Intel Flash devices have a tiered approach to power savings that can significantly reduce overall
system power consumption. The Automatic Power Savings (APS) feature reduces power
consumption when the device is selected 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.
With CE# at a logic-low level and RP# at a logic-high level, the device is in the active mode. Refer
to the DC Characteristic tables for I
overall system power consumption. Minimizing the active current could have a profound ef f ect on
system power consumption, especially for battery-operated devices.
current values. Active power is the largest contributor to
CC
3.5.2Automatic Power Savings (APS)
Automatic Power Savings provides low-power operation during read mode. After d ata is read fr om
the memory array and the address lines are quiescent, APS circuitry places the device in a mode
where typical current is comparable to I
until a new location is read.
. The flash stays in this static state with outputs valid
CCS
3.5.3Standby Power
With CE# at a logic-high level (VIH) and device in read mode, the flash memory is in standby
mode, which disables much of the device’s circuitry and substantially reduces power consumption.
Outputs are placed in a high-impedance state independent of the status of the OE# signal. If CE#
transitions to a logic-high level during erase or program operations, the device will continue to
perform the operation and consume corresponding active power until the operation is completed.
System engineers should analyze 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 application-specific power and energy requirements.
3.5.4Deep Power-Down Mode
The deep power-down mode is activated when RP# = VIL (GND ± 0.2 V). During rea d modes,
RP# going low de-selects the memory and places the outputs in a high impedance state. Recovery
from deep power-down requires a minimum time of t
Operations, Section 4.5).
During program or erase modes, RP# transitioning low will abort the in-progress operation. The
memory contents of the addr ess bei ng prog rammed or the block bei ng erased are no l onger valid as
the data integrity has been compromised by the abort. During deep power-down, all internal
circuits are switched to a low power savings mode (RP# transitioning to V
the device clears the status register).
3.6Power-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
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 reset. If a CPU reset occurs
without a flash memory reset, proper CPU initialization will not occur because the flash memory
may be providing status in formation i nstead of array dat a. Intel re commends conn ecting RP# t o the
system CPU RESET# signal to allow proper CPU/flash initialization following system reset.
System designers must guard against spurious writes when V
both WE# and CE# must be low for a command write, driving either signal to V
writes to the device. The CUI architecture provides additional protection since alteration of
memory contents can only occur after successful completion of the two-step command sequences.
The device is also disabled until RP# is brought to V
By holding the device in reset (RP# connected to system POWERGOOD) during power-up/down,
invalid bus conditions during power-up can be masked, providing yet another level of memory
protection.
3.6.2VCC, VPP and RP# Tr ansitions
The CUI latches commands as issued by system software and is not altered by VPP or CE#
transitions or WSM actions. Its default state upon power-up, after exit from reset mode or after
V
transitions above V
CC
(Lockout voltage), is read array mode.
LKO
After any program or block erase operation is complete (even after V
V
), the CUI must be reset to read array mode via the Read Array command if access to the
PPLK
flash memory array is desired.
3.7Power Supply Decoupling
Flash memory’s power switching characteristics require careful device decoupling. System
designers should consider three supply current issues:
1. Standby current levels (I
2. Read current levels (I
3. Transient peaks produced by falling and rising edges of CE#.
CCR
CCS
)
)
voltages are above V
CC
IH
, regardless of the stat e of it s cont ro l inputs.
IH
transitions down to
PP
. Since
LKO
will inhibit
Transient current magnitudes depend on the dev ice outputs’ capacitive and inductive loadin g.
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 each V
GND, and between its V
and GND. These high-frequency, inherently low-inductance capacitors
PP
CC
and
should be placed as close as possible to the package leads.
Temperature under Bias–40 °C to +85 °C
Storage Temperature–65 °C to +125 °C
Voltage On Any Pin (except V
VPP Voltage (for Block Erase and Program) with Respect to GND–0.5 V to +13.5 V
VCC and V
Supply Voltage with Respect to GND–0.2 V to +3.7 V
CCQ
Output Short Circuit Current100 mA
NOTES:
1. Minimum DC voltage is -0.5 V on input/output pins, with allowable undershoot to -2.0 V for periods <20 ns.
Maximum DC voltage on input/output pins is V
<20 ns
2. Maximum DC voltage on V
Program voltage is normally 2.7 V–3.6 V. Connection to a 11.4 V–12.6 V supply can be done for a
3. V
PP
maximum of 1000 cycles on the main blocks and 2500 cycles on the parameter blocks during program/erase.
may be connected to 12 V for a total of 80 hours maximum. See Section 3.4 for details.
V
PP
4. Minimum DC voltage is -0.5 V on V
Maximum DC voltage on V
of <20 ns.
5. Output shorted for no more than one second. No more than one output shorted at a time.
, V
CC
PP
CC
and VPP) with Respect to GND–0.5 V to +3.7 V
CCQ
+0.5 V, with allowable overshoot to VCC +1.5 for periods of
CC
may overshoot to +14.0 V for periods <20 ns.
and V
CC
CCQ
and V
, with allowable undershoot to -2.0 V for periods <20 ns.
CCQ
pins is VCC +0.5 V, with allowable overshoot to VCC +1.5 for periods
(1)
(1,2,3)
(4)
(5)
NOTICE: This datasheet contains preliminary information on new products in production. 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 affect device reliability.
RP# High Recovery to WE# (CE#) Going Low600600600600ns
/
CE# (WE#) Setup to WE# (CE#) Going Low0000ns
/
WE# (CE#) Pulse Width170707070ns
/
Data Setup to WE# (CE#) Going High250506060ns
/
Address Setup to WE# (CE#) Going High270707070ns
/
CE# (WE#) Hold Time from WE# (CE#) High0000ns
/
Data Hold Time from WE# (CE#) High20000ns
/
Address Hold Time from WE# (CE#) High20000ns
WE# (CE#) Pulse Width High130303030ns
/
VPP Setup to WE# (CE#) Going High3200200200200ns
V
Hold from Valid SRD30000ns
PP
NoteMinMinMinMin
3.0 V –
V
CC
3.6 V
2.7 V –
3.6 V
3.0 V –
3.6 V
2.7 V –
3.6 V
Unit
NOTES:
= t
IN
= t
EHEL
or DIN.
= t
ELEH
= t
WHEL
WLEH
= t
= t
EHWL
. Similarly, Write pulse width
ELWH
.
1. Refer to command definition table (Table 6) for valid A
2. Write pulse width (t
high (whichever goes high first). Hence, t
high (t
(whichever goes low first). Hence, t
) is defined from CE# or WE# going high (whichever goes high first) to CE# or WE# going low
WPH
3. Sampled, but not 100% tested.
) is defined from CE# or WE# going low (whichever goes low last) to CE# or WE# going
WP
WPH
= t
WP
WHWL
= t
WLWH
Read timing characteristics during program suspend and erase suspend are the same as during read-only
operations.
See Figure 5 for timing measurements and maximum allowable input slew rate.
See Figure 8, “AC Waveform: Program and Erase Operations” on page 32.
VPP Setup to WE# (CE#) Going High3200200200200200200ns
VPEH
V
QVVL
Hold from Valid SRD3000000ns
PP
2.7 V –
V
CC
3.6 V
2.7 V –
3.6 V
3.0 V –
3.6 V
NoteMinMinMinMinMinMin
150150600600600600ns
000000ns
2505070707070ns
000000ns
2000000ns
2.7 V –
3.6 V
3.0 V –
3.6 V
2.7 V –
3.6 V
Unit
NOTES:
= t
IN
= t
EHEL
or DIN.
= t
ELEH
= t
WHEL
WLEH
= t
= t
EHWL
. Similarly, Wr ite pulse width
ELWH
.
1. Refer to command definition table (Table 6) for valid A
2. Write pulse width (t
high (whichever goes high first). Hence, t
high (t
(whichever goes low first). Hence, t
) is defined from CE# or WE# going high (whichever goes high first) to CE# or WE# going low
WPH
3. Sampled, but not 100% tested.
) is defined from CE# or WE# going low (whichever goes low last) to CE# or WE# going
WP
WPH
= t
WP
WHWL
= t
WLWH
Read timing characteristics during program suspend and erase suspend are the same as during read-only
operations.
See Figure 5 for timing measurements and maximum allowable input slew rate.
See Figure 8, “AC Waveform: Program and Erase Operations” on page 32.
283UHOLPLQDU\
AC Characteristics—Write Operations, continued
#SymParameter
t
/
RP# High Recovery to WE# (CE#)
PHWL
W1
W2
W3
W4
W5
W6
W7
W8
W9
W10
W11 t
t
t
t
t
t
t
t
t
t
t
t
t
t
t
t
t
t
t
t
Going Low
PHEL
/
CE# (WE#) Setup to WE# (CE#) Going
ELWL
Low
WLEL
/
ELEH
WE# (CE#) Pulse Width1456070707070ns
WLWH
/
DVWH
Data Setup to WE# (CE#) Going High2404050506060ns
DVEH
/
Address Setup to WE# (CE#) Going
AVWH
High
AVEH
/
CE# (WE#) Hold Time from WE#
WHEH
(CE#) High
EHWH
/
WHDX
Data Hold Time from WE# (CE#) High2000000ns
EHDX
/
Address Ho ld Time from WE# (CE#)
WHAX
High
EHAX
WHWL /
WE# (CE#) Pu lse Width High1253030303030ns
EHEL
/
VPWH
VPP Setup to WE# (CE#) Going High3200200200200200200ns
1. Refer to command definition table (Table 6) for valid A
2. Write pulse width (t
high (whichever goes high first). Hence, t
high (t
(whichever goes low first). Hence, t
) is defined from CE# or WE# going high (whichever goes high first) to CE# or WE# going low
WPH
3. Sampled, but not 100% tested.
) is defined from CE# or WE# going low (whichever goes low last) to CE# or WE# going
WP
WPH
= t
WP
WHWL
= t
WLWH
Read timing characteristics during program suspend and erase suspend are the same as during read-only
operations.
See Figure 5 for timing measurements and maximum allowable input slew rate.
See Figure 8, “AC Waveform: Program and Erase Operations” on page 32.
1. Refer to command definition table (Table 6) for valid A
2. Write pulse width (t
high (whichever goes high first). Hence, t
high (t
(whichever goes low first). Hence, t
) is defined from CE# or WE# going high (whichever goes high first) to CE# or WE# going low
WPH
3. Sampled, but not 100% tested.
) is defined from CE# or WE# going low (whichever goes low last) to CE# or WE# going
WP
WPH
= t
WP
WHWL
= t
WLWH
Read timing characteristics during program suspend and erase suspend are the same as during read-only
operations.
See Figure 5 for timing measurements and maximum allowable input slew rate.
See Figure 8, “AC Waveform: Program and Erase Operations” on page 32.
Figure 8. AC Waveform: Program and Erase Operations
ABC D EF
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
V
2
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
ADDRESSES [A]
CE#(WE#) [E(W)]
OE# [G]
WE#(CE#) [W(E)]
DATA [D/Q]
RP# [P]
V [V]
D
IN
NOTES:
1. CE# must be toggled low when reading Status Register Data. WE# must be inactive (high) when reading
Status Register Data.
Power-Up and Standby.
A. V
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.
1. The 48-ball µBGA package top side mark reads F160B3 [or F800B3]. 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 dif ferentiate 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.
2. The second line of the 48-ball µBGA package top side mark specifies assembly codes. For samples only, the
first character signifies either “E” for engineering samples or “S” for silicon daisy chain samples. All other
assembly codes without an “E” or “S” as the first character are production units.
3. Product can be ordered in either 0.25 µm or 0.4 µm material. The “A” before the access speed specifies
0.25 µm material. For new designs, Intel recommends using 0.25 µm Advanced Boot Block devices.
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.
3. For the most current information on Intel Advanced and Advanced+ Boot Block Flash memory, visit our
microsite at http://developer.intel.com/design/flash/abblock.
3 Volt Advanced Boot Block Flash Memory Family Specification Update
AP-641 Achieving Low Power with the 3 Volt Advanced Boot Block Flash Memory
AP-642 Designing for Upgrade to the 3 Volt Advanced Boot Block Flash Memory
3 Volt Advanced Boot Block Algorithms (‘C’ and assembly)
http://developer.intel.com/design/flash/swtools
Intel® Flash Data Integrator (IFDI) Software Developer’s Kit
IFDI Interactive: Play with Intel® Flash Data Integrator on Your PC