—2.7 V– 3.6 V Read/Program/Erase
—12 V for Fast Production Programming
■ 1.65 V–2.5 V or 2.7 V–3.6 V I/O Option
—Reduces Overall System Power
■ High Performance
—2.7 V– 3.6 V: 70 ns Max Access Time
■ Optimized Architecture for Code Plus
Data Storage
—Eight 4 Kword Blocks, Top or Bottom
Parameter Boot
—Up to One Hundred-Twenty-Seven 32
Kword Blocks
—Fast Program Suspend Capability
—Fast Erase Suspend Capability
■ Flexible Block Locking
—Lock/Unlock Any Block
—Full Protection on Power-Up
—WP# Pin for Hardware Block Protection
■ Low Power Consumption
—9 mA Typical Read
—7 A Typical Standby with Automatic
Power Savings Feature (APS)
■ Extended Temperature Operation
—–40°C to+85 °C
■ 128-bit Protection Register
—64 bit Unique Device Identifier
—64 bit User Programmable OTP Cells
■ Extended Cycling Capability
—Minimum 100,000 Block Erase Cycles
■ Software
—Intel
®
Flash Data Integrator (FDI)
—Supports Top or Bottom Boot Storage,
Streaming Data (e.g., voice)
—Intel Basic Command Set
—Common Flash Interface (CFI)
■ Standard Surface Mount Packaging
—48-Ball µBGA*/VFBGA
—64-Ball Easy BGA Packages
—48-Lead TSOP Package
■ ETOX™ VIII (0.13 µm) Flash
Technology
—16, 32 Mbit
■ ETOX™ VII (0.18 µm)Flash Technology
—16, 32, 64 Mbit
■ ETOX™ VI (0.25 µm) Flash Technology
—8, 16 and 32 Mbit
The Intel®Advanced+ Book Block Flash Memory (C3) device, manufactured on Intel’s latest
0.13 µm and 0.18 µm technologies, represents a feature-rich solution for low-power applications.
The C3 device incorporates low-voltage capability (3 V read, program, and erase) with highspeed, low-power operation. Flexible block locking allows any block to be independently locked
or unlocked. Add to this the Intel
effective, flexible, monolithic code plus data storage solution. Intel
Memory (C3) products will be available in 48-lead TSOP, 48-ball CSP, and 64-ball Easy BGA
packages. Additional information on this product family can be obtained by accessing the Intel
®
Flash Data Integrator (FDI) software and you have a cost-
®
Advanced+ Boot Block Flash
®
Flash website: http://www.intel.com/design/flash.
Notice: This specification is subject to change without notice. Verify with your local Intel sales
office that you have the latest datasheet before finalizing a design.
Order Number: 290645-017
October 2003
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 28F800C3, 28F160C3, 28F320C3, 28F640C3 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-800548-4725 or by visiting Intel's website at http://www.intel.com.
10/03-017Corrected information in the Device Geometry Details table, address 0x34.
VersionDescription
Updated 64Mb product offerings.
Updated 16Mb product offerings.
Revised and corrected DC Characteristics Table.
Added mechanicals for Easy BGA.
Minor text edits throughout document.
6Datasheet
1.0Introduction
1.1Document Purpose
This datasheet contains the specifications for the Intel®Advanced+ Boot Block Flash Memory
(C3) device family. These flash memories add features such as instant block locking and protection
registers that can be used to enhance the security of systems.
1.2Nomenclature
0xHexadecimal prefix
0bBinary prefix
Byte8 bits
Word16 bits
Kword1024 words
Mword1,048,576 words
Kb1024 bits
KB1024 bytes
Mb1,048,576 bits
MB1,048,576 bytes
APSAutomatic Power Savings
CUICommand User Interface
OTPOne Time Programmable
PRProtection Register
PRDProtection Register Data
PLRProtection Lock Register
RFUReserved for Future Use
SRStatus Register
SRDStatus Register Data
WSMWrite State Machine
Intel£Advanced+ Boot Block Flash Memory (C3)
1.3Conventions
The terms pin and signal are often used interchangeably to refer to the external signal connections
on the package. (ball is the term used for CSP).
Group Membership Brackets: Square brackets will be used to designate group membership or to
define a group of signals with similar function (i.e. A[21:1], SR[4:1])
Set: When referring to registers, the term set means the bit is a logical 1.
Clear: When referring to registers, the term clear means the bit is a logical 0.
Block: A group of bits (or words) that erase simultaneously with one block erase instruction.
Main Block: A block that contains 32 Kwords.
Parameter Block: A block that contains 4 Kwords.
Datasheet7
Intel£Advanced+ Boot Block Flash Memory (C3)
2.0Device Description
This section provides an overview of the Intel®Advanced+ Boot Block Flash Memory (C3) device
features, packaging, signal naming, and device architecture.
2.1Product Overview
The C3 device provides high-performance asynchronous reads in package-compatible densities
with a 16 bit data bus. Individually-erasable memory blocks are optimally sized for code and data
storage. Eight 4 Kword parameter blocks are located in the boot block at either the top or bottom of
the device’s memory map. The rest of the memory array is grouped into 32 Kword main blocks.
The device supports read-array mode operations at various I/O voltages (1.8 V and 3 V) and erase
and program operations at 3 V or 12 V VPP. With the 3 V I/O option, VCC and VPP can be tied
together for a simple, ultra-low-power design. In addition to I/O voltage flexibility, the dedicated
VPP input provides complete data protection when V
The device features a 128-bit protection register enabling security techniques and data protection
schemes through a combination of factory-programmed and user-programmable OTP data
registers. Zero-latency locking/unlocking on any memory block provides instant and complete
protection for critical system code and data. Additional block lock-down capability provides
hardware protection where software commands alone cannot change the block’s protection status.
PP
≤ V
PPLK
.
A command User Interface(CUI) serves as the interface between the system processor and internal
operation of the device. A valid command sequence issued to the CUI initiates device automation.
An internal Write State Machine (WSM) automatically executes the algorithms and timings
necessary for block erase, program, and lock-bit configuration operations.
The device offers three low-power saving features: Automatic Power Savings (APS), standby
mode, and deep power-down mode. The device automatically enters APS mode following read
cycle completion. Standby mode begins when the system deselects the flash memory by
deasserting CE#. The deep power-down mode begins when RP# is asserted, which deselects the
memory and places the outputs in a high-impedance state, producing ultra-low power savings.
Combined, these three power-savings features significantly enhanced power consumption
flexibility.
2.2Ballout Diagram
The C3 device is available in 48-lead TSOP, 48-ball VF BGA, 48-ball µBGA, and Easy BGA
packages. (Refer to Figure1onpage9, Figure 3 on page 11,andFigure 4 on page 12,
respectively.)
1. For lower densities, upper address should be treated as NC. For example, a 16-Mbit device will have NC on
Pins 9 and 10.
Datasheet9
Intel£Advanced+ Boot Block Flash Memory (C3)
Figure 2. Mark for Pin-1 indicator on 48-Lead 8Mb, 16Mb and 32Mb TSOP
Current Mark:
New Mark:
Note:The topside marking on 8 Mb, 16 Mb, and 32 Mb Intel
£
Advanced and Advanced + Boot Block
48L TSOP products will convert to a white ink triangle as a Pin 1 indicator. Products without the
white triangle will continue to use a dimple as a Pin 1 indicator. There are no other changes in
package size, materials, functionality, customer handling, or manufacturability. Product will
continue to meet Intel stringent quality requirements. Products affected are Intel Ordering Codes
shown in Table 1 .
Tabl e 2 lists the active signals used and provides a brief description of each.
Table 2. Signal Descriptions
SymbolTypeName and Function
ADDRESS INPUTS for memory addresses. Address are internally latched during a program or erase
cycle.
A[MAX:0]INPUT
DQ[15:0]
CE#INPUT
OE#INPUT
RP#INPUT
WE#INPUT
WP#INPUT
VPP
VCCPOWER
VCCQPOWER
GNDPOWER
DU-
NC-
INPUT/
OUTPUT
INPUT/
POWER
8 Mbit: AMAX= A18
16 Mbit: AMAX = A19
32 Mbit: AMAX = A20
64 Mbit: AMAX = A21
DATA INPUTS/OUTPUTS: Inputs data and commands during a write cycle; outputs data during read
cycles. Inputs commands to the Command User Interface when CE# and WE# are active. Data is
internally latched. The data pins float to tri-state when the chip is de-selected or the outputs are
disabled.
CHIP ENABLE: Active-low input. 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: Active-low input. Enables the device’s outputs through the data buffers during a
Read operation.
RESET/DEEP POWER-DOWN: Active-low input.
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.
WRITE ENABLE: Active-low input. WE# controls writes to the device. Address and data are latched on
therisingedgeoftheWE#pulse.
WRITE PROTECT: Active-low input.
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 the lock-down state.
See Section 5.0, “Security Modes” on page 27 for details on block locking.
PROGRAM/ERASE POWER SUPPLY: Operates as an input at logic levels to control complete device
protection. Supplies power for accelerated Program and Erase operations in 12 V
cannot be left floating.
Lower VPP
Set VPP = VCC for in-system Read, Program and Erase operations. In this configuration, VPP can
drop as low as 1.65 V to allow for resistor or diode drop from the system supply.
Apply VPP to 12 V
to VPP can only be done for a maximum of 1000 cycles on the main blocks and 2500 cycles on the
boot blocks. VPP may be connected to 12 V for a total of 80 hours maximum. See Section 5.6 for
details on VPP voltage configurations.
DEVICE CORE POWER SUPPLY: Supplies power for device operations.
OUTPUT POWER SUPPLY: Output-driven source voltage. This ball can be tied directly to V
operating within V
GROUND: For all internal circuitry. All ground inputs must be connected.
DON’T USE: Do not use this ball. This ball should not be connected to any power supplies, signals or
other balls, and must be left floating.
NO CONNECT: Pin must be left floating.
≤ VPPLK to protect all contents against Program and Erase commands.
± 5% for faster program and erase in a production environment. Applying 12 V ± 5%
range.
CC
CCD
).
± 5% range. This pin
CC
if
Datasheet13
Intel£Advanced+ Boot Block Flash Memory (C3)
2.4Block Diagram
V
CCQ
Power
Reduction
Control
A[MAX:MIN]
Input B uff er
Address
Latch
Address
Counter
Y-Decoder
X-Decoder
Output Buffer
Output
Multiplexer
Y-G ating/ Sensing
4-KWord
Paramet er B lock
DQ0-DQ
Comparat or
4-KWord
Paramet er B lock
Identifier
Register
Stat us
Register
Dat a
32- KWor d
Main Block
15
Input Buffer
Data
Re gist er
Command
User
Interface
Write State
Machine
32- KWor d
Main Block
I/O Logic
Program /Eras e
Voltage Switch
CE#
WE#
OE#
RP#
WP#
V
GND
V
PP
CC
14Datasheet
2.5Memory Map
The C3 device is asymmetrically blocked, which enables system code and data integration within a
single flash device. The bulk of the array is divided into 32 Kword main blocks that can store code
or data, and 4 Kword boot blocks to facilitate storage of boot code or for frequently changing small
parameters. See Table 3, “Top Boot Memory Map” on page 15 and Table 4, “Bottom Boot Memory
The C3 device uses a CUI and automated algorithms to simplify Program and Erase operations.
The CUI allows for 100% CMOS
programming.
The internal WSM completely automates Program and Erase operations while the CUI signals the
start of an operation and the status register reports device status. The CUI handles the WE#
interface to the data and address latches, as well as system status requests during WSM operation.
3.1Bus Operations
The C3 device performs read, program, and erase operations in-system via the local CPU or
microcontroller. Four control pins (CE#, OE#, WE#, and RP#) manage the data flow in and out of
the flash device. Table 5 on page 17 summarizes these bus operations.
Table 5. Bus Operations
Intel£Advanced+ Boot Block Flash Memory (C3)
-level control inputs and fixed power supplies during erasure and
3.1.1Read
When performing a read cycle, CE# and OE# must be asserted; WE# and RP# must be deasserted.
CE# is the device selection control; when active low, it enables the flash memory device. OE# is
the data output control; when low, data is output on DQ[15:0]. See Figure 8, “Read Operation
Wav ef orm” on page 42.
3.1.2Write
A write cycle occurs when both CE# and WE# are low; RP# and OE# are high. Commands are
issued to the Command User Interface (CUI). The CUI does not occupy an addressable memory
location. Address and data are latched on the rising edge of the WE# or CE# pulse, whichever
occurs first. See Figure 9, “Write Operations Waveform” on page 47.
ModeRP#CE#OE#WE#DQ[15:0]
ReadV
WriteV
Output DisableV
StandbyV
ResetV
NOTE: X = Don’t Care (V
IL
or VIH)
IH
IH
IH
IH
IL
V
IL
V
IL
V
IL
V
IH
XXXHigh-Z
V
IL
V
IH
V
IH
XXHigh-Z
V
IH
V
IL
V
IH
D
OUT
D
High-Z
IN
3.1.3Output Disable
With OE# at a logic-high level (VIH), the device outputs are disabled. DQ[15:0] are placed in a
-impedance state.
high
Datasheet17
Intel£Advanced+ Boot Block Flash Memory (C3)
3.1.4Standby
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 a Program or Erase operation, the device continues to consume active power
until the Program or Erase operation is complete.
3.1.5Reset
From read mode, RP# at VILfor time t
impedance state, and turns off all internal circuits. After return from reset, a time t
until the initial read-access outputs are valid. A delay (t
reset before a write cycle can be initiated. After this wake
deselects the memory, places output drivers in a high-
PLPH
PHQV
PHWL
or t
) is required after return from
PHEL
-up interval, normal operation is restored.
is required
The CUI resets to read-array mode, the status register is set to 0x80, and all blocks are locked. See
Figure 10, “Reset Operations Waveforms” on page 48.
If RP# is taken low for time t
during a Program or Erase operation, the operation will be
PLPH
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:
1. When RP# goes low, the device shuts down the operation in progress, a process which takes time
to complete.
t
PLRH
2. After time t
enter reset mode (if RP# is deasserted after t
, the part will either reset to read-array mode (if RP# is asserted during t
PLRH
). See Figure 10, “Reset Operations Waveforms”
PLRH
PLRH
)or
on page 48.
In both cases, after returning from an aborted operation, the relevant time t
PHQV
or t
PHWL/tPHEL
must be observed before a Read or Write operation is initiated, as discussed in the previous
paragraph. However, in this case, these delays are referenced to the end of t
rather than when
PLRH
RP# goes high.
As with any automated device, it is important to assert RP# during a system reset. When the system
comes out of reset, the 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
®
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.
18Datasheet
4.0Modes of Operation
4.1Read Mode
The flash memory has four read modes (read array, read identifier, read status, and CFI query), and
two write modes (program and erase). Three additional modes (erase suspend to program, erase
suspend to read, and program suspend to read) are available only during suspended operations.
Table 7, “Command Bus Operations” on page 24 and Table 8, “Command Codes and
Descriptions”onpage25summarize the commands used to reach these modes. Appendix A,
“Write State Machine States” on page 50 is a comprehensive chart showing the state transitions.
4.1.1Read Array
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#mustbelogichigh(V
)
IH
)
IL
)
IL
)
IH
Intel£Advanced+ Boot Block Flash Memory (C3)
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 (0xFF) must be issued to the CUI before array reads can occur.
4.1.2Read Identifier
The read-identifier mode outputs three types of information: the manufacturer/device identifier, the
block locking status, and the protection register. The device is switched to this mode by issuing the
Read Identifier command (0x90). Once in this mode, read cycles from addresses shown in Table 6
retrieve the specified information. To return to read-array mode, issue the Read Array command
(0xFF).
Datasheet19
Intel£Advanced+ Boot Block Flash Memory (C3)
Table 6.Device Identification Codes
Item
Manufacturer IDBlock0x000x0089
Device IDBlock0x01
Block Lock Status
Block Lock-Down Status
Protection Register Lock StatusBlock0x80Lock Data
Protection RegisterBlock
NOTES:
1. The address is constructed from a base address plus an offset. For example, to read the Block Lock Status
for block number 38 in a bottom boot device, set the address to 0x0F8000 plus the
0x0F8002. Then examine DQ0 of the data to determine if the block is locked.
2. See Section 5.2, “Reading Block-Lock Status” on page 28 for valid lock status.
2
2
Address
BaseOffset
Block0x02
Block0x02
1
0x81 -
0x88
DataDescription
0x88C08-Mbit Top Boot Device
0x88C18-Mbit Bottom Boot Device
0x88C216-Mbit Top Boot Device
0x88C316-Mbit Bottom Boot Device
0x88C432-Mbit Top Boot Device
0x88C532-Mbit Bottom Boot Device
0x88CC64-Mbit Top Boot Device
0x88CD64-Mbit Bottom Boot Device
DQ0 = 0b0Block is unlocked
DQ0 = 0b1Block is locked
DQ1 = 0b0Block is not locked-down
DQ1 = 0b1Block is locked down
Register Data
Multiple reads required to read
the entire 128-bit Protection
Register.
offset (0x02), i.e.
4.1.3CFI Query
The CFI query mode outputs Common Flash Interface (CFI) data after issuing the Read Query
Command (0x98). The CFI data structure contains information such as block size, density,
command set, and electrical specifications. Once in this mode, read cycles from addresses shown in
Appendix C, “Common Flash Interface,” retrieve the specified information. To return to read-array
mode, issue the Read Array command (0xFF).
4.1.4Read Status Register
The status register indicates the status of device operations, and the success/failure of that
operation. The Read Status Register (0x70) command causes subsequent reads to output data from
the status register until another command is issued. To return to reading from the array, issue a
Read Array (0xFF) command.
The status-register bits are output on DQ[7:0]. The upper byte, DQ[15:8], outputs 0x00 when a
Read Status Register command is issued.
20Datasheet
The contents of the status register are latched on the falling edge of OE# or CE# (whichever occurs
last) which prevents possible bus errors that 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.
When the WSM is active, SR[7] will indicate the status of the WSM; the remaining bits in the
status register indicate whether the WSM was successful in performing the preferred operation (see
Table 9, “Status Register Bit Definition” on page 26).
4.1.4.1Clear Status Register
The WSM can set Status Register bits 1 through 7 and can clear bits 2, 6, and 7; but, the WSM
cannot clear Status Register bits 1, 3, 4 or 5. Because bits 1, 3, 4, and 5 indicate various error
conditions, these bits can be cleared only through the Clear Status Register (0x50) 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. The Read Array
command must be issued before data can be read from the memory array. Resetting the device also
clears the Status Register.
Intel£Advanced+ Boot Block Flash Memory (C3)
4.2Program Mode
Programming is executed using a two-write cycle sequence. The Program Setup command (0x40)
is issued 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 preferred
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 users attempt
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 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.
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.
4.2.112-Volt Production Programming
When VPPis between 1.65 V and 3.6 V, all program and erase current is drawn through the VCC
pin. Note that if V
1.65 V to perform in-system flash modifications. When V
the device draws program and erase current directly from the VPP pin. This eliminates the need for
an external switching transistor to control V
flash power supplies can be configured for various usage models.
was not within acceptable limits, and the WSM did not execute the program
PP
is driven by a logic signal, VIHmin = 1.65 V. That is, VPPmust remain above
PP
PP
is connected to a 12 V power supply,
PP
. Figure 7 on page 31 shows examples of how the
Datasheet21
Intel£Advanced+ Boot Block Flash Memory (C3)
The 12 V VPPmode enhances programming 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 VPP during Program and Erase operations for a maximum of 1000 cycles on the main
blocks and 2500 cycles on the parameter blocks. VPP may be connected to 12 V for a total of 80
hours maximum. Stressing the device beyond these limits may cause permanent damage.
4.2.2Suspending 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, issuing 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 issued. 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
t
A Read-Array command can now be issued 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 Identifier, CFI Query, and Program Resume.
After the Program Resume command is issued to the flash memory, the WSM will continue with
the programming process and status register bits SR[2] and SR[7] will automatically be cleared.
The device automatically outputs status register data when read (see Figure 14, “Program Suspend
/ResumeFlowchart”onpage53) after the Program Resume command is issued. V
atthesameV
V
specify the program-suspend latency.
EHRH1
level used for program while in program-suspend mode. RP# must also remain at
PP
IH
.
WHRH1
must remain
PP
/
4.3Erase Mode
To erase a block, issue 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
supply voltage was not within acceptable limits.
V
PP
After an Erase operation, clear the status register (0x50) before attempting the next operation. Any
CUI instruction can follow after erasure is completed; however, to prevent inadvertent statusregister reads, it is advisable to place the flash in read-array mode after the erase is complete.
was not within acceptable limits after
PP
22Datasheet
Intel£Advanced+ Boot Block Flash Memory (C3)
4.3.1Suspending and Resuming Erase
Since an Erase operation requires on the order of seconds to complete, an Erase Suspend command
is provided to allow erase
another block in memory. Once the erase sequence is started, issuing the Erase Suspend command
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
WHRH2/tEHRH2
A Read Array or Program command can now be issued 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 Identifier, CFI Query, Program Setup, Program Resume, Erase
Resume, Lock Block, Unlock Block, and Lock-Down Block. During erase-suspend mode, the chip
can be placed in a pseudo
consumption.
-sequence interruption in order to read data from—or program data to—
.
-standbymodebytakingCE#toV
, which reduces active current
IH
Erase Resume continues the erase sequence when CE# = V
. Similar to the end of a standard
IL
Erase operation, the status register should be read and cleared before the next instruction is issued.
1. Following the Read Identifier or CFI Query commands, read operations output device identification data or
CFI query information, respectively. See Section 4.1.2 and Section 4.1.3.
2. Either 0x40 or 0x10 command is valid, but the Intel standard is 0x40.
3. When writing commands, the upper data bus [DQ8-DQ15] should be either V
draw.
PD = Prog DataID = Identifier DataQD = Query Data
First Bus CycleSecond Bus Cycle
OperAddrDataOperAddrData
0x40/
0x10
WritePAPD
or VIH, to minimize current
IL
Bus operations are defined in Table 5, “Bus Operations” on page 17.
24Datasheet
Table 8. Command Codes and Descriptions
Intel£Advanced+ Boot Block Flash Memory (C3)
Code
(HEX)
FFRead Array
40Program Set-Up
20Erase Set-Up
D0
B0
70
50
90
60
01Lock-Block
2FLock-Down
98
C0
Device ModeCommand Description
Erase Confirm
Program/Erase
Resume
Unlock Block
Program Suspend
Erase Suspend
Read Status
Register
Clear Status
Register
Read
Identifier
Block Lock, Block
Unlock, Block
Lock-Down Set-
Up
CFI
Query
Protection
Program
Set-Up
This command places the device in read-array mode, which outputs array data on the data
pins.
This is a two
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 4.2, “Program
Mode” on page 21.
This is a two
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 4.3, “Erase Mode” on page 22.
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 Block Unlock 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. (See Section 5.1)
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
remainderofthechipifRP#isdriventoV
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 4.1.4, “Read Status Register” on page 20.
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 read-identifier mode so that reading the device will output the
manufacturer/device codes or block-lock status. See Section 4.1.2, “Read Identifier” on
page 19.
Prepares the CUI for block-locking changes. If the next command is not Block Unlock, Block
Lock, or Block Lock-Down, then the CUI will set both the program and erase-status-register
bits to indicate a command-sequence error. See Section 5.0, “Security Modes” on page 27.
If the previous command was Lock Set-Up, the CUI will latch the address and lock the block
indicated on the address pins. (See Section 5.1)
If the previous command was a Lock-Down Set-Up command, the CUI will latch the address
and lock-down the block indicated on the address pins. (See Section 5.1)
Puts the device into the CFI-Query mode so that reading the device will output Common Flash
Interface information. See Section 4.1.3 and Appendix C, “Common Flash Interface”.
This is a two-cycle command. The first cycle prepares the CUI for a 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 5.5.
-cycle command. The first cycle prepares the CUI for a program operation. The
-cycle command. Prepares the CUI for the Erase Confirm command. If the next
. See Sections 3.2.5.1 and 3.2.6.1.
IL
Status SR[3], program status SR[4], and
PP
Datasheet25
Intel£Advanced+ Boot Block Flash Memory (C3)
Table 8.Command Codes and Descriptions
Code
(HEX)
Device ModeCommand Description
10Alt. Prog Set-UpOperates the same as Program Set-up command. (See 0x40/Program Set-Up)
00
NOTE: See Appendix A, “Write State Machine States” for mode transition information.
Invalid/
Reserved
Unassigned commands should not be used. Intel reserves the right to redefine these codes for
future functions.
Table 9.Status Register Bit Definition
WSMSESSESPSVPPSPSSBLSR
76543210
NOTES:
SR[7] WRITE STATE MACHINE STATUS (WSMS)
1 = Ready
0=Busy
SR[6] = ERASE
-SUSPEND STATUS (ESS)
1 = Erase Suspended
0=EraseInProgress/Completed
SR[5] = ERASE STATUS (ES)
1=ErrorInBlockErase
0 = Successful Block Erase
SR[4] = PROGRAM STATUS (PS)
1 = Error in Programming
0 = Successful Programming
SR[3] = V
1=V
0=V
STATUS (VPPS)
PP
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/Eraseattemptedonalockedblock;Operation
aborted.
0=Nooperationtolockedblocks
SR[0] = RESERVED FOR FUTURE ENHANCEMENTS (R)
NOTE: A Command-Sequence Error is indicated when SR[4], SR[5], and SR[7] are set.
Check Write State Machine bit first to determine Word Program
or Block Erase completion, before checking program or erasestatus 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
V
Program or Erase command sequences have been entered,
and informs the system if V
V
WSM. The V
feedback between V
status bit does not provide continuous indication of
PP
level. The WSM interrogates VPPlevel only after the
PP
has not been switched on. The
PPLK
PP
and V
PP1
Min.
is also checked before the operation is verified by the
PP
status bit is not guaranteed to report accurate
PP
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
specifiedisabortedandthedeviceisreturnedtoreadstatus
mode.
This bit is reserved for future use and should be masked out
when polling the status register.
26Datasheet
5.0Security Modes
5.1Flexible Block Locking
The C3 device offers an instant, individual block-locking scheme that allows any block to be
locked or unlocked with no latency, enabling instant code and data protection.
This locking scheme offers two levels of protection. The first level allows software-only control of
block locking (useful for data blocks that change frequently), while the second level requires
hardware interaction before locking can be changed (useful for code blocks that change
infrequently).
The following sections will discuss the operation of the locking system. The term “state [abc]” will
be used to specify locking states; e.g., “state [001],” where a = value of WP#, b = bit D1 of the
Block Lock status register, and c = bit D0 of the Block Lock status register. Figure 5, “Block
Locking State Diagram” on page 27 displays all of the possible locking states.
Figure 5. Block Locking State Diagram
Intel£Advanced+ Boot Block Flash Memory (C3)
Power-U p/Reset
Not es:1. [ a,b,c ] represents [WP#, D 1, D0]. X = Don’t Care.
2. D 1 indic ates block Lock-down s tatus . D 1 = ‘0’, Lock-dow n has not been issued t o
this bloc k. D1 = ‘1’, Lock-down has been is sued t o this block .
3. D 0 indic ates block lock s tatus. D 0 = ‘0’, block is unloc ked. D0 = ‘1’, bloc k is loc k ed.
4. Loc ked-down = Hardware + Sof tware lock ed.
5. [ 011] st at es s hould be t rac ked by sys tem s oftware to determ ine difference
betw een H ardware Locked and Loc ked-Down s tates .
Lo cked
[X01]
Unlo cked
[X00]
Software Block Lock (0x60/0x01) or Software Block Unlock (0x60/0xD0)
Software Block Lock-Down (0x60/0x2F)
WP# hardware control
Lo cked-
Down
Software
4,5
[011]
WP#HardwareControl
Lo cked
[111][ 110]
Hardware
Lo cked
[011]
Unlo cked
5
Datasheet27
Intel£Advanced+ Boot Block Flash Memory (C3)
5.1.1Locking Operation
The locking status of each block can be set to Locked, Unlocked, or Lock-Down, each of which
will be described in the following sections. See Figure 5, “Block Locking State Diagram” on
page 27 and Figure 17, “Locking Operations Flowchart” on page 56.
The following concisely summarizes the locking functionality.
5.1.1.1Locked State
The default state 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 locked
block will return an error on bit SR[1] of the Status Register. The state of a locked block can be
changed to Unlocked or Lock Down using the appropriate software commands. An Unlocked
block can be locked by writing the Lock command sequence, 0x60 followed by 0x01.
5.1.1.2Unlocked 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, 0x60 followed by 0xD0.
5.1.1.3Lock-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 block can be Locked Down by writing the Lock-Down command sequence,
0x60 followed by 0x2F. Locked-Down blocks revert to the Locked state when the device is reset or
powered down.
The Lock-Down function depends on the WP# input pin. When WP# = 0, blocks in Lock Down
[011] are protected from program, erase, and lock status changes. When WP# = 1, the Lock-Down
function is disabled ([111]) and Locked-Down blocks can be individually unlocked by software
command to the [110] state, where they can be erased and programmed. These blocks can then be
relocked [111] and unlocked [110] as required 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 power-down resets all blocks, including those
in Lock-Down, to Locked state.
5.2Reading Block-Lock Status
The Lock status of each block can be read in read-identifier mode of the device by issuing the readidentifier command (0x90). Subsequent reads at Block Address + 0x00002 will output the Lock
status of that block. The Lock status is represented by DQ0 and DQ1. DQ0 indicates the Block
Lock/Unlock status and is set by the Lock command and cleared by the Unlock command. It is also
automatically set when entering Lock Down. DQ1 indicates Lock-Down status, and is set by the
Lock-Down command. It cannot be cleared by software—only by device reset or power-down. See
Table 6, “Device Identification Codes” on page 20 for block-status information.
28Datasheet
Intel£Advanced+ Boot Block Flash Memory (C3)
5.3Locking 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 is useful in the case
when another block needs to be updated while an Erase operation is in progress.
To change block locking during an Erase operation, first issue the Erase Suspend command (0xB0),
then check the status register until it indicates that the Erase operation has been suspended. Next,
write the preferred Lock command sequence to a block and the Lock status will be changed. After
completing any preferred Lock, Read, or Program operations, resume the Erase operation with the
Erase Resume command (0xD0).
If a block is Locked or Locked Down during a Suspended Erase of the same block, the locking
status bits will be changed immediately. But when the Erase is resumed, the Erase operation will
complete.
Locking operations cannot be performed during a Program Suspend. Refer to Appendix A, “Write
State Machine States” on page 50 for detailed information on which commands are valid during
Erase Suspend.
5.4Status Register Error Checking
Using nested-locking or program-command sequences during Erase Suspend can introduce
ambiguity into status register results.
Since locking changes are performed using a two-cycle command sequence, e.g., 0x60 followed by
0x01 to lock a block, following the Block Lock, Block Unlock, or Block Lock-Down Setup
command (0x60) with an invalid command will produce a Lock-Command error (SR[4] and SR[5]
will 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 status register because of
the previous Lock-Command error.
A similar situation happens if an error occurs during a Program-Operation error nested within an
Erase Suspend.
5.5128-Bit Protection Register
The C3 device architecture 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 “match” the flash component with other system components, such as the CPU or ASIC,
preventing device substitution. The Intel application note,
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 factory with a unique 64-bit number, which is unchangeable. The other
segment is left blank for customer designs to program, as preferred. Once the customer segment is
programmed, it can be locked to prevent further programming.
contains additional application information.
AP-657 Designing with the Advanced+
Datasheet29
Intel£Advanced+ Boot Block Flash Memory (C3)
5.5.1Reading the Protection Register
The protection register is read in the read-identifier mode. The device is switched to this mode by
issuing the Read Identifier command (0x90). Once in this mode, read cycles from addresses shown
in Figure 6, “Protection Register Mapping” retrieve the specified information. To return to readarray mode, issue the Read Array command (0xFF).
5.5.2Programming the Protection Register
The protection register bits are programmed using the two-cycle Protection Program command.
The 64-bit number is programmed 16 bits at a time. First, issue the Protection Program Setup
command, 0xC0. The next write to the device will latch in address and data, and program the
specified location. The allowable addresses are shown in Table 6, “Device Identification Codes” on
page 20.SeeFigure 18, “Protection Register Programming Flowchart” on page 57. Attempts to
address Protection Program commands outside the defined protection register address space should
not be attempted. Attempting to program 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).
5.5.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. See Figure 6, “Protection Register Mapping” on page 30.Bit0ofthis
location is programmed to 0 at the Intel factory to protect the unique device number. This bit is set
using the Protection Program command to program 0xFFFD to the PR-LOCK location. After these
bits have been programmed, no further changes can be made to the values stored in the protection
register. Protection Program commands 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.
Figure 6. Protection Register Mapping
0x88
0x85
0x84
0x81
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
0x80
64-bit Segment
(User-Programmable)
128-Bit Prot ec tion R egis ter 0
64-bit Segment
(Intel Factory-Programmed)
PR Lock R egister 0
5.6VPPProgram and Erase Voltages
The C3 device provides in-system programming and erase in the 1.65 V–3.6 V range. For fast
production programming, 12 V programming can be used. Refer to Figure 7, “Example Power
Supply Configurations” on page 31.
30Datasheet
5.6.1Program Protection
In addition to the flexible block locking, the VPPprogramming voltage can be held low for absolute
hardware write protection of all blocks in the flash device. When V
any Program or Erase operation will result in an error, prompting the corresponding status-register
bit (SR[3]) to be set.
Figure 7. Example Power Supply Configurations
Intel£Advanced+ Boot Block Flash Memory (C3)
is below or equal to V
PP
PPLK
,
System Supply
12 V Supply
≤KΩ
10
12 V Fast Programming
Absolute Write Protection With V
System Supply
(Note 1)
12 V Supply
Low Voltage and 12 V Fast Programming
NOTE:
1. A resistor can be used if the VCCsupply can sink adequate current based on resistor value. See AP-657
Designing with the Advanced+ Boot Block Flash Memory Architecture
V
CC
V
PP
≤
V
PP
PPLK
V
CC
V
PP
System Supply
Prot#
(Logic Signal)
Low-Voltage Programming
Absolute Write Protection via Logic Signal
System Supply
Low-Voltage Programming
V
V
V
V
for details.
CC
PP
CC
PP
0645_06
Datasheet31
Intel£Advanced+ Boot Block Flash Memory (C3)
6.0Power 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 CE# is deasserted, the flash enters its standby
mode, where current consumption is even lower. If RP# is deasserted, the flash enter deep powerdown mode for ultra-low current consumption. The combination of these features can minimize
memory power consumption, and therefore, overall system power consumption.
6.1Active Power (Program/Erase/Read)
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 effect on
system power consumption, especially for battery
6.2Automatic Power Savings (APS)
current values. Active power is the largest contributor to
CC
-operated devices.
Automatic Power Savings provides low-power operation during read mode. After data is read from
the memory array and the address lines are idle, APS circuitry places the device in a mode where
typical current is comparable to I
new location is read.
. The flash stays in this static state with outputs valid until a
CCS
6.3Standby Power
When CE# is at a logic-high level (VIH), the flash memory is in standby mode, which disables
much of the device’s circuitry and substantially reduces power consumption. Outputs are placed in
-impedance state independent of the status of the OE# signal. If CE# transitions to a logic-
ahigh
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 approach will
provide a more accurate measure of application
6.4Deep Power-Down Mode
The deep power-down mode is activated when RP# = VIL. During read modes, RP# going low deselects the memory and places the outputs in a high-impedance state. Recovery from deep powerdown requires a minimum time of t
operations.
PHQV
-specific power and energy requirements.
for Read operations, and t
PHWL/tPHEL
for Write
32Datasheet
Intel£Advanced+ Boot Block Flash Memory (C3)
During program or erase modes, RP# transitioning low will abort the in-progress operation. The
memory contents of the address being programmed or the block being erased are no longer 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
to the device clears the status register).
6.5Power and Reset Considerations
6.5.1Power-Up/Down Characteristics
In order to prevent any condition that may result in a spurious write or erase operation, it is
recommended to power-up VCC and VCCQ together. Conversely, VCC and VCCQ must powerdown together.
or turning off power
IL
It is also recommended to power-up VPP with or after VCC has reached VCC
must powerdown with or slightly before VCC.
If VCCQ and/or VPP are not connected to the VCC supply, then VCC should attain VCC
applying VCCQ and VPP. Device inputs should not be driven before supply voltage reaches
min
.
VCC
Power supply transitions should only occur when RP# is low.
6.5.2RP# 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 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 information instead of array data. Intel recommends connecting RP# to 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 during power-up/down, invalid bus conditions during power-up can
be masked, providing yet another level of memory protection.
6.5.3VCC,VPPand RP# Transitions
. Conversely, VPP
min
before
min
voltages are above V
CC
IH
, regardless of the state of its control inputs.
IH
. Because
LKO
will inhibit
The CUI latches commands as issued by system software and is not altered by VPPor CE#
transitions or WSM actions. Its default state upon power-up, after exit from reset mode or after
transitions above V
V
CC
After any program or Block-Erase operation is complete (even after V
), the CUI must be reset to read-array mode via the Read Array command if access to the
V
PPLK
(Lockout voltage), is read-array mode.
LKO
transitions down to
PP
flash-memory array is desired.
Datasheet33
Intel£Advanced+ Boot Block Flash Memory (C3)
6.6Power Supply Decoupling
Flash memory power-switching characteristics require careful device decoupling. System
designers should consider the following three supply current issues:
• Standby current levels (I
• Read current levels (I
CCR
CCS
)
)
• Transient peaks produced by falling and rising edges of CE#.
Transient current magnitudes depend on the device outputs’ capacitive and inductive loading. Twoline 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
and between its V
and VSS. These high- frequency, inherently low-inductance capacitors should
PP
be placed as close as possible to the package leads.
7.0Thermal and DC Characteristics
7.1Absolute Maximum Ratings
War n ing: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.
NOTICE: Specifications are subject to change without notice. Verify with your local Intel Sales office that you have
the latest datasheet before finalizing a design
.
and GND,
CC
ParameterMaximum RatingNotes
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
Voltage On Any Pin (except V
V
Voltage (for Block Erase and Program) with Respect to GND–0.5 V to +13.5 V1,2,3
PP
V
and V
CC
Output Short Circuit Current100 mA4
NOTES:
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
+0.5 V which, during transitions, may overshoot to VCC+2.0 V for periods <20 ns.
2. Maximum DC voltage on V
3. V
PP
done for a maximum of 1000 cycles on the main blocks and 2500 cycles on the parameter
blocks during program/erase. V
4. Output shorted for no more than one second. No more than one output shorted at a time.
Supply Voltage with Respect to GND–0.2 V to +3.6 V
CCQ
Program voltage is normally 1.65 V–3.6 V. Connection to a 11.4 V–12.6 V supply can be
and VPP) with Respect to GND–0.5 V to +3.7 V1
CC
CC
may overshoot to +14.0 V for periods <20 ns.
PP
may be connected to 12 V for a total of 80 hours maximum.
PP
34Datasheet
Intel£Advanced+ Boot Block Flash Memory (C3)
7.2Operating Conditions
Table 10. Temperature and Voltage Operating Conditions
SymbolParameterNotesMinMaxUnits
T
V
V
V
V
V
V
A
CC1
CC2
CCQ1
CCQ2
CCQ3
PP1
PP2
Operating Temperature–40+85°C
VCCSupply Voltage1, 22.73.6Volts
I/O Supply Voltage
Supply Voltage11.653.6Volts
CyclingBlock Erase Cycling3100,000Cycles
NOTES:
1. VCCand V
2. V
Max = 3.3 V for 0.25µm 32-Mbit devices.
CC
3. Applying V
the main blocks and 2500 cycles on the parameter blocks. V
must share the same supply when they are in the V
CCQ
= 11.4 V–12.6 V during a program/erase can only be done for a maximum of 1000 cycles on
PP
80 hours maximum.
7.3DC Current Characteristics
Table 11. DC Current Characteristics (Sheet 1 of 3)
V
2.7 V–3.6 V 2.7 V–2.85 V2.7 V–3.3 V
CC
SymParameter
V
NoteTypMaxTypMaxTypMax
2.7 V–3.6 V1.65 V–2.5 V1.8 V–2.5 V
CCQ
1, 23.03.6
12.73.6
1.652.5
VoltsV
1.82.5
1, 311.412.6Volts
range.
CC1
may be connected to 12 V for a total of
PP
Unit
Test
Conditions
=
V
CC
V
Max
CC
V
=
I
I
Input Load Current1,2± 1± 1± 1µA
LI
LO
Output Leakage
Current
1,2
± 10± 10± 10µA
CCQ
V
Max
CCQ
V
IN=VCCQ
or GND
=
V
CC
V
Max
CC
V
=
CCQ
V
Max
CCQ
V
IN=VCCQ
or GND
Datasheet35
Intel£Advanced+ Boot Block Flash Memory (C3)
Table 11. DC Current Characteristics (Sheet 2 of 3)
V
CC
SymParameter
VCCStandby Current
for 0.13 and 0.18
Micron Product
I
CCS
V
Standby Current
CC
for 0.25 Micron
Product
VCCPower-Down
Current for 0.13 and
0.18 Micron Product
I
CCD
V
Power-Down
CC
Current for 0.25
Product
VCCRead Current for
0.13 and 0.18 Micron
Product
I
CCR
VCCRead Current for
0.25 Micron Product
I
PPD
I
CCW
I
CCE
VPPDeep PowerDown Current
VCCProgram Current1,4
VCCErase Current1,4
VCCErase Suspend
Current for 0.13 and
I
CCES
I
CCWS
0.18 Micron Product
/
V
Erase Suspend
CC
Current for 0.25
Micron Product
V
CCQ
NoteTypMaxTypMaxTypMax
17152050150250µA
110252050150250µA
1,2715720720µA
1,2725725725µA
1,2,3918815915mA
1,2,31018815915mA
10.250.250.25µA
1,4,5
2.7 V–3.6 V2.7 V–2.85 V2.7 V–3.3 V
2.7V–3.6V 1.65V–2.5V1.8V–2.5V
Unit
185518551855mA
82210301030mA
164521452145mA
81516451645mA
7155020050200µA
10255020050200µA
Tes t
Conditions
VCC=
V
Max
CC
CE# = RP#
=V
CCQ
or during
Program/
Erase
Suspend
WP# =
V
or
CCQ
GND
VCC=
V
Max
CC
V
=
CCQ
V
Max
CCQ
V
IN=VCCQ
or GND
RP# = GND
±0.2V
VCC=
V
Max
CC
V
=
CCQ
V
Max
CCQ
OE# = V
CE# =V
f=5MHz,
I
Inputs = V
or V
OUT
IH
IL
=0 mA
IH
RP# = GND
±0.2V
V
≤ V
PP
CC
V
PP=VPP1,
Program in
Progress
V
PP=VPP2
(12v)
Program in
Progress
V
PP=VPP1,
Erase in
Progress
V
PP=VPP2
(12v) ,
Erase in
Progress
CE# = V
Erase
IH,
Suspend in
Progress
,
IL
36Datasheet
Intel£Advanced+ Boot Block Flash Memory (C3)
Table 11. DC Current Characteristics (Sheet 3 of 3)
V
2.7 V–3.6 V 2.7 V–2.85 V2.7 V–3.3 V
CC
SymParameter
V
NoteTypMaxTypMaxTypMax
I
I
I
I
I
VPPRead Current1,4
PPR
VPPProgram Current1,4
PPW
VPPErase Current1,4
PPE
/
VCCErase Suspend
PPES
Current
PPWS
NOTES:
1. All currents are in RMS unless otherwise noted. Typical values at nominal VCC,TA=+25°C.
2. The test conditions V
V
voltage listed at the top of each column. V
CCQ
3. Automatic Power Savings (APS) reduces I
CC
Max, V
CCQ
inputs).
4. Sampled, not 100% tested.
5. I
or I
CCES
is sum of I
and I
CCR
is specified with device de-selected. If device is read while in erase suspend, current draw
CCWS
.
CCES
and I
. If the device is read while in program suspend, current draw is the sum of I
CCR
2.7 V–3.6 V1.65 V–2.5 V1.8 V–2.5 V
CCQ
2
502005020050200µAVPP>V
0.050.10.050.10.050.1mA
822 8 22 8 22mA
0.050.10.050.10.050.1mA
82216 451645mA
0.250.250.25µA
1,4
502005020050200µA
Max, VCCMin, and V
to approximately standby levels in static operation (CMOS
CCR
Unit
Test
Conditions
±152±152±15µAVPP≤ V
V
PP=VPP1,
Program in
Progress
V
PP=VPP2
(12v)
Program in
Progress
V
PP=VPP1,
Erase in
Progress
V
PP=VPP2
(12v) ,
Erase in
Progress
V
PP=VPP1,
Program or
Erase
Suspend in
Progress
V
PP=VPP2
(12v) ,
Program or
Erase
Suspend in
Progress
Min refer to the maximum or minimum VCCor
CCQ
Max = 3.3 V for 0.25µm 32-Mbit devices.
CC
CC
CC
CCWS
Datasheet37
Intel£Advanced+ Boot Block Flash Memory (C3)
7.4DC Voltage Characteristics
Table 12. DC Voltage Characteristics
SymParameter
V
CCQ
CC
2.7 V–3.6 V2.7 V–2.85 V2.7 V–3.3 V
2.7 V–3.6 V1.65 V–2.5 V1.8 V–2.5 V
NoteMinMaxMinMaxMinMax
V
V
V
V
V
V
V
IL
IH
OL
OH
PPLK
PP1
PP2
Input Low
Voltage
Input High
Voltage
Output Low
Voltage
Output High
Voltage
VPPLockOut Voltage
VPPduring
Program /
Erase
Operations
–0.4
2.0
–0.10.1-0.10.1-0.10.1V
V
CCQ
–0.1V
11.01.01.0V
11.653.61.653.61.653.6V
1,211.412.611.412.611.412.6V
V
CC
0.22 V
V
CCQ
+0.3V
VCCProg/
V
LKO
Erase
Lock
1.51.51.5V
Voltage
V
Prog/
CCQ
V
LKO2
Erase
Lock
1.21.21.2V
Voltage
NOTES:
1. Erase and Program are inhibited when VPP<V
2. Applying V
2500 cycles on the parameter blocks. V
= 11.4 V–12.6 V during program/erase can only be done for a maximum of 1000 cycles on the main blocks and
PP
may be connected to 12 V for a total of 80 hours maximum.
PP
*
–0.40.4–0.40.4V
–
V
CCQ
0.4V
V
CCQ
0.1V
and not guaranteed outside the valid VPPranges of V
PPLK
V
CCQ
+0.3V
–
V
V
CCQ
0.4V
CCQ
0.1V
–
V
+0.3V
–
CCQ
UnitTest ConditionsV
V
V
V
CC=VCC
V
CCQ=VCCQ
I
OL
V
CC=VCC
V
CCQ=VCCQ
I
OH
Min
=100µA
Min
= –100 µA
Complete Write
Protection
and V
PP1
PP2
Min
Min
.
38Datasheet
8.0AC Characteristics
8.1AC Read Characteristics
Table 13. Read Operations—8 Mbit Density
Density8 Mbit
Intel£Advanced+ Boot Block Flash Memory (C3)
#Sym Parameter
R1t
R2t
R3t
R4t
R5t
R6t
R7t
R8t
R9t
Read Cycle Time3,48090100110ns
AVAV
Address to Output Delay3,48090100110ns
AVQV
CE# to Output Delay1,3,48090100110ns
ELQV
OE# to Output Delay1,3,430303030ns
GLQV
RP# to Output Delay3,4150150150150ns
PHQV
CE# to Output in Low Z2,3,40000ns
ELQX
OE# to Output in Low Z2,3,40000ns
GLQX
CE#toOutputinHighZ2,3,420202020ns
EHQZ
OE#toOutputinHighZ2,3,420202020ns
GHQZ
Product90 ns110 ns
V
CC
NoteMinMaxMinMaxMinMaxMinMax
3.0V–3.6V2.7V–3.6V3.0V–3.6V2.7V–3.6V
Output Hold from
R10t
Address, CE#, or OE#
OH
Change, Whichever
2,3,40000ns
Occurs First
NOTES:
1. OE#maybedelayeduptot
2. Sampled, but not 100% tested.
ELQV–tGLQV
after the falling edge of CE# without impact on t
ELQV
.
3. See Figure 8, “Read Operation Waveform” on page 42.
4. See Figure 11, “AC Input/Output Reference Waveform” on page 49 for timing measurements and maximum allowable input
slew rate.
Unit
Datasheet39
Intel£Advanced+ Boot Block Flash Memory (C3)
Table 14. Read Operations—16 Mbit Density
Density16 Mbit
#Sym
Paramete
r
Product
V
CC
70 ns80 ns90 ns110 ns
Unit Notes
2.7 V–3.6 V 2.7 V–3.6 V 3.0 V–3.6 V 2.7 V–3.6 V 3.0 V–3.6V 2.7 V–3.6V
MinMaxMinMaxMinMaxMinMaxMin Max Min Max
R1t
R2
R3
R4
R5
R6
R7
R8
R9
R10t
AVAV
t
AVQ
t
ELQ
t
GLQ
t
PHQ
t
ELQ
t
GLQ
t
EHQ
t
GHQ
V
V
V
V
X
X
Z
Z
OH
Read Cycle Time
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
OE# Change,
Whichever
Occurs First
70808090100110
70808090100110
70808090100110
202030303030
150150150150150150
000000
000000
202020202020
202020202020
000000
ns3,4
ns3,4
ns1,3,4
ns1,3,4
ns3,4
ns2,3,4
ns2,3,4
ns2,3,4
ns2,3,4
ns2,3,4
NOTES:
1.OE#maybedelayeduptot
2. Sampled, but not 100% tested.
ELQV–tGLQV
after the falling edge of CE# without impact on t
ELQV
.
3. See Figure 8, “Read Operation Waveform” on page 42.
4. See Figure 11, “AC Input/Output Reference Waveform” on page 49 for timing measurements and maximum allowable input
slew rate.
40Datasheet
Table 15. Read Operations—32 Mbit Density
Density32 Mbit
Intel£Advanced+ Boot Block Flash Memory (C3)
#Sym
Para-
meter
Product
V
CC
70 ns90 ns100 ns110 ns
2.7 V–3.6 V 2.7 V–3.6 V 3.0 V–3.3 V 2.7 V–3.3 V 3.0 V–3.3 V 2.7 V–3.3 V
Min MaxMinMaxMinMaxMinMaxMin MaxMinMax
R1t
R2
R3
R4
R5
R6
R7
R8
R9
R10t
AVAV
t
AVQ
t
ELQ
t
GLQ
t
PHQ
t
ELQ
t
GLQ
t
EHQ
t
GHQ
V
V
V
V
X
X
Z
Z
OH
Read Cycle Time
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
OE# Change,
Whichever
Occurs First
709090100100110
709090100100110
709090100100110
202030303030
150150150150150150
000000
000000
202020202020
202020202020
000000
NOTES:
1. OE#maybedelayeduptot
2. Sampled, but not 100% tested.
ELQV–tGLQV
after the falling edge of CE# without impact on t
ELQV
.
3. See Figure 8, “Read Operation Waveform” on page 42.
4. See Figure 11, “AC Input/Output Reference Waveform” on page 49 for timing measurements and maximum allowable
input slew rate.
Unit Notes
ns3,4
ns3,4
ns1,3,4
ns1,3,4
ns3,4
ns2,3,4
ns2,3,4
ns2,3,4
ns2,3,4
ns2,3,4
Datasheet41
Intel£Advanced+ Boot Block Flash Memory (C3)
A
Table 16. Read Operations — 64 Mbit Density
Density64 Mbit
#SymParameter
R1t
R2t
R3t
R4t
R5t
R6t
R7t
R8t
R9t
R10t
Read Cycle Time3,47080ns
AVAV
Address to Output Delay3,47080ns
AVQV
CE# to Output Delay1,3,47080ns
ELQV
OE# to Output Delay1,3,42020ns
GLQV
RP# to Output Delay3,4150150ns
PHQV
CE#toOutputinLowZ2,3,400ns
ELQX
OE# to Output in Low Z2,3,400ns
GLQX
CE#toOutputinHighZ2,3,42020ns
EHQZ
OE# to Output in High Z2,3,42020ns
GHQZ
Output Hold from Address, CE#, or OE#
OH
Change, Whichever Occurs First
NOTES:
1.OE#maybedelayeduptot
2. Sampled, but not 100% tested.
ELQV–tGLQV
3. See Figure 8, “Read Operation Waveform” on page 42.
4. See Figure 11, “AC Input/Output Reference Waveform” on page 49 for timing measurements and
maximum allowable input slew rate.
Figure 8. Read Operation Waveform
Product70 ns80 ns
V
CC
2.7 V–3.6 V2.7 V–3.6 V
NoteMinMaxMinMax
2,3,400ns
after the falling edge of CE# without impact on t
ELQV
Unit
.
R1R2R1
ddress [A]
R8R3
CE# [E]
R9R4
OE# [G]
WE# [W]
R7
R6
R10
Data [D/Q]
R5
RST # [P ]
42Datasheet
8.2AC Write Characteristics
Table17. WriteOperations—8MbitDensity
Intel£Advanced+ Boot Block Flash Memory (C3)
Density8 Mbit
Product90 ns110 ns
#Sym Parameter
V
3.0V–3.6V80100
CC
2.7V–3.6V90110
Unit
NoteMinMinMinMin
t
/
W1
W2
W3
W4
W5
W6
W7
W8
W9
W10
W11t
W12
W13t
W14t
PHWL
t
PHEL
t
ELWL
t
WLEL
t
WLWH
t
ELEH
t
DVWH
t
DVEH
t
AVW H
t
AVE H
t
WHEH
t
EHWH
t
WHDX
t
EHDX
t
WHAX
t
EHAX
t
WHWL /
t
EHEL
t
VPWH
t
VPEH
QVVL
t
BHWH
t
BHEH
QVBL
WHGL
RP# High Recovery to WE# (CE#) Going Low4,5150150150150ns
/
CE# (WE#) Setup to WE# (CE#) Going Low4,50000ns
/
WE#(CE#)PulseWidth4,550607070ns
/
Data Setup to WE# (CE#) Going High2,4,550506060ns
/
Address Setup to WE# (CE#) Going High2,4,550607070ns
/
CE# (WE#) Hold Time from WE# (CE#) High4,50000ns
/
Data Hold Time from WE# (CE#) High2,4,50000ns
/
Address Hold Time from WE# (CE#) High2,4,50000ns
WE# (CE#) Pulse Width High2,4,530303030ns
/
VPPSetup to WE# (CE#) Going High3,4,5200200200200ns
VPPHold from Valid SRD3,40000ns
/
WP# Setup to WE# (CE#) Going High3,40000ns
WP# Hold from Valid SRD3,40000ns
WE#HightoOE#GoingLow3,430303030ns
NOTES:
1. Write pulse width (tWP) is defined from CE# or WE# going low (whichever goes low last) to CE# or WE# going high (whichever
goes high first). Hence, t
WE# going high (whichever goes high first) to CE# or WE# going low (whichever goes low last). Hence,
t
WPH=tWHWL=tEHEL=tWHEL=tEHWL
2. Refer to Table 7, “Command Bus Operations” on page 24 for valid A
WP=tWLWH=tELEH=tWLEH=tELWH
.
3. Sampled, but not 100% tested.
. Similarly, write pulse width high (t
or DIN.
IN
) is defined from CE# or
WPH
4. See Figure 11, “AC Input/Output Reference Waveform” on page 49 for timing measurements and maximum allowable input
slew rate.
5. See
Figure 9, “Write Operations Waveform” on page 47.
Datasheet43
Intel£Advanced+ Boot Block Flash Memory (C3)
Table 18. Write Operations—16 Mbit Density
Density16 Mbit
Product70ns 80ns90ns110ns
#SymParameter
V
3.0 V – 3.6 V80100
CC
2.7V–3.6V708090110
Unit
NoteMinMinMinMinMinMin
t
/
W1
W2
W3
W4
W5
W6
W7
W8
W9
W10
W11t
W12
W13t
W14t
PHWL
t
PHEL
t
ELWL
t
WLEL
t
WLWH
t
ELEH
t
DVWH
t
DVEH
t
AVW H
t
AVE H
t
WHEH
t
EHWH
t
WHDX
t
EHDX
t
WHAX
t
EHAX
t
WHWL /
t
EHEL
t
VPWH
t
VPEH
QVVL
t
BHWH
t
BHEH
QVBL
WHGL
RP# High Recovery to WE# (CE#) Going
Low
/
CE# (WE#) Setup to WE# (CE#) Going Low4,5000000ns
/
WE#(CE#)PulseWidth1,4,5455050607070ns
/
Data Setup to WE# (CE#) Going High2,4,5404050506060ns
/
Address Setup to WE# (CE#) Going High2,4,5505050607070ns
/
CE# (WE#) Hold Time from WE# (CE#)
High
/
Data Hold Time from WE# (CE#) High2,4,5000000ns
/
Address Hold Time from WE# (CE#) High2,4,5000000ns
4,5150150150150150150ns
4,5000000ns
WE# (CE#) Pulse Width High1,4,5253030303030ns
/
VPPSetup to WE# (CE#) Going High3,4,5200200200200200200ns
VPPHold from Valid SRD3,4000000ns
/
WP# Setup to WE# (CE#) Going High3,4000000ns
WP# Hold from Valid SRD3,4000000ns
WE#HightoOE#GoingLow3,4303030303030ns
NOTES:
1. Write pulse width (tWP) is defined from CE# or WE# going low (whichever goes low last) to CE# or WE# going high
(whichever goes high first). Hence, t
from CE# or WE# going high (whichever goes high first) to CE# or WE# going low (whichever goes low last). Hence,
t
WPH=tWHWL=tEHEL=tWHEL=tEHWL
2. Refer to Table 7, “Command Bus Operations” on page 24 for valid A
WP=tWLWH=tELEH=tWLEH=tELWH
.
3. Sampled, but not 100% tested.
. Similarly, write pulse width high (t
or DIN.
IN
) is defined
WPH
4. See Figure 11, “AC Input/Output Reference Waveform” on page 49 for timing measurements and maximum allowable input
slew rate.
5. See
Figure 9, “Write Operations Waveform” on page 47.
44Datasheet
Intel£Advanced+ Boot Block Flash Memory (C3)
Table 19. Write Operations—32 Mbit Density
Density32 Mbit
Product70ns90ns100ns110ns
#SymParameter
t
/
W1
W2
W3
W4
W5
W6
W7
W8
W9
W10
W11 t
W12
W13 t
W14 t
PHWL
t
PHEL
t
ELWL
t
WLEL
t
WLWH
/
t
ELEH
t
DVWH
t
DVEH
t
AVWH
t
AVE H
t
WHEH
t
EHWH
t
WHDX
t
EHDX
t
WHAX
t
EHAX
t
WHWL /
t
EHEL
t
VPWH
t
VPEH
QVVLVPP
t
BHWH
t
BHEH
QVBL
WHGL
RP#HighRecoverytoWE#(CE#)
Going Low
/
CE#(WE#)SetuptoWE#(CE#)
Going Low
WE# (CE#) Pulse Width1,4,5456060707070ns
/
Data Setup to WE# (CE#) Going High2,4,5404050606060ns
/
Address Setup to WE# (CE#) Going
High
/
CE# (WE#) Hold Time from WE#
(CE#) High
/
Data Hold Time from WE# (CE#)
High
/
Address Hold Time from WE# (CE#)
High
WE# (CE#) Pulse Width High1,4,5253030303030ns
/
VPPSetup to WE# (CE#) Going High3,4,5200200200200200200ns
Hold from Valid SRD3,4000000ns
/
WP# Setup to WE# (CE#) Going
High
WP# Hold from Valid SRD3,4000000ns
WE#HightoOE#GoingLow3,4303030303030ns
3.0V–3.6V
V
CC
2.7 V – 3.6 V7090100110
NOTES:
1. Write pulse width (tWP) is defined from CE# or WE# going low (whichever goes low last) to CE# or WE# going high (whichever
goes high first). Hence, t
WE# going high (whichever goes high first) to CE# or WE# going low (whichever goes low last). Hence,
t
WPH=tWHWL=tEHEL=tWHEL=tEHWL
2. Refer to Table 7, “Command Bus Operations” on page 24 for valid A
WP=tWLWH=tELEH=tWLEH=tELWH
.
3. Sampled, but not 100% tested.
4. See Figure 11, “AC Input/Output Reference Waveform” on page 49 for timing measurements and maximum allowable input
slew rate.
5. See
Figure 9, “Write Operations Waveform” on page 47.
6. VCCMax = 3.3 V for 32-Mbit 0.25 Micron product.
6
90100
Unit
NoteMinMinMinMinMinMin
4,5150150150150150150ns
4,5000000ns
2,4,5506060707070ns
4,5000000ns
2,4,5000000ns
2,4,5000000ns
3,4000000ns
. Similarly, write pulse width high (t
or DIN.
IN
) is defined from CE# or
WPH
Datasheet45
Intel£Advanced+ Boot Block Flash Memory (C3)
Table 20. Write Operations—64Mbit Density
Density64 Mbit
#SymParameter
t
/
PHWL
W1
W2
W3
W4
W5
W6
W7
W8
W9
W10
W11 t
W12
W13 t
W14 t
t
PHEL
t
ELWL
t
WLEL
t
WLWH
t
ELEH
t
DVWH
t
DVEH
t
AVWH
t
AVE H
t
WHEH
t
EHWH
t
WHDX
t
EHDX
t
WHAX
t
EHAX
t
WHWL /
t
EHEL
t
VPWH
t
VPEH
QVVL
t
BHWH
t
BHEH
QVBL
WHGL
RP# High Recovery to WE# (CE#) Going Low4,5150ns
/
CE# (WE#) Setup to WE# (CE#) Going Low4,50ns
/
WE#(CE#)PulseWidth1,4,560ns
/
Data Setup to WE# (CE#) Going High2,4,540ns
/
Address Setup to WE# (CE#) Going High2,4,560ns
/
CE# (WE#) Hold Time from WE# (CE#) High4,50ns
/
Data Hold Time from WE# (CE#) High2,4,50ns
/
Address Hold Time from WE# (CE#) High2,4,50ns
WE#(CE#)PulseWidthHigh1,4,530ns
/
VPPSetup to WE# (CE#) Going High3,4,5200ns
VPPHold from Valid SRD3,40ns
/
WP#SetuptoWE#(CE#)GoingHigh3,40ns
WP# Hold from Valid SRD3,40ns
WE#HightoOE#GoingLow3,430ns
2.7V–3.6V NoteMin
V
CC
UnitProduct80 ns
NOTES:
1. Write pulse width (tWP) is defined from CE# or WE# going low (whichever goes low last) to CE# or
WE# going high (whichever goes high first). Hence, t
Similarly, write pulse width high (t
high first) to CE# or WE# going low (whichever goes low last). Hence,
t
WPH=tWHWL=tEHEL=tWHEL=tEHWL
2. Refer to Table 7, “Command Bus Operations” on page 24 for valid A
) is defined from CE# or WE# going high (whichever goes
WPH
.
WP=tWLWH=tELEH=tWLEH=tELWH
3. Sampled, but not 100% tested.
IN
or DIN.
.
4. See Figure 11, “AC Input/Output Reference Waveform” on page 49 for timing measurements and
maximum allowable input slew rate.
5. See
Figure 9, “Write Operations Waveform” on page 47.
46Datasheet
Figure 9. Write Operations Waveform
A
ddress [A]
CE# [E]
Intel£Advanced+ Boot Block Flash Memory (C3)
W8W5
W6
W2
W3W3
WE# [ W]
OE# [G]
W7W4
Data [D/Q]
W1
RP# [P]
W10
Vpp [V]
W9W9
8.3Erase and Program Timings
Table 21. Erase and Program Timings
V
SymbolParameter
t
BWPB
t
BWMB
4-KW Parameter Block
Word Program Time
32-KW Main Block
Word Program Time
Word Program Time for 0.13
t
WHQV1/tEHQV1
and0.18MicronProduct
Word Program Time for 0.25
Micron Product
t
WHQV2/tEHQV2
t
WHQV3/tEHQV3
t
WHRH1/tEHRH1
t
WHRH2/tEHRH2
NOTES:
4-KW Parameter Block
Erase Time
32-KW Main Block
Erase Time
Program Suspend Latency1,3510510µs
Erase Suspend Latency1,3520520µs
PP
NoteTypMaxTypMax
1, 2, 30.100.300.030.12s
1, 2, 30.82.40.241s
1, 2, 3122008185µs
1, 2, 3222008185µs
1, 2, 30.540.44s
1, 2, 3150.65s
1. Typical values measured at TA= +25 °C and nominal voltages.
2. Excludes external system-level overhead.
3. Sampled, but not 100% tested.
1.65 V–3.6 V11.4 V–12.6 V
Unit
Datasheet47
Intel£Advanced+ Boot Block Flash Memory (C3)
H
8.4Reset Specifications
Table 22. Reset Specifications
SymbolParameterNotes
RP# Low to Reset during Read
t
PLPH
t
PLRH1
t
PLRH2
NOTES:
1. If t
2. If RP# is asserted while a Block Erase or Word Program operation is not executing, the reset will complete
within 100 ns.
3. Sampled, but not 100% tested.
Figure 10. Reset Operations Waveforms
(If RP# is tied to V
applicable)
, this specification is not
CC
RP# Low to Reset during Block Erase322µs
RP# Low to Reset during Program312µs
is < 100 ns the device may still reset but this is not guaranteed.
PLPH
V
2.7V–3.6V
CC
Unit
MinMax
1, 2100ns
V
RP# (P)
IH
V
IL
t
PLPH
t
PHQV
t
PHWL
t
PHEL
(A) Reset during Read Mode
Abort
t
Complete
t
t
PLRH
PLPH
RP# (P)
V
IH
V
IL
(B) Reset during Program or Block Erase,<
Abort
t
PLPH
Deep
Power-
Down
RP# (P)
Complete
t
V
IH
V
IL
PLRH
(C) Res et Program or Block Erase,>
PHQV
t
PHWL
t
PHEL
PLPHtPLR
t
PHQV
t
PHWL
t
PHEL
t
PLPHtPLRH
t
48Datasheet
8.5AC I/O Test Conditions
Figure 11. AC Input/Output Reference Waveform
V
CCQ
V
InputOutput
0V
/2V
CCQ
Intel£Advanced+ Boot Block Flash Memory (C3)
e
s
T
s
t
P
t
n
o
i
CCQ
/2
NOTE: Input timing begins, and output timing ends, at V
Worst case speed conditions are when V
CC=VCC
/2. Input rise and fall times (10% to 90%) < 5 ns.
Repeat f or subsequent Wor d Progr am oper ations.
Ful l Status Regi ster c heck can be done after each pr ogram , or
after a sequence of program oper ations.
Wri te 0xFF after the l ast operat ion to set t o the Read Ar ray
state.
Command
Progr am
Wr ite
Wr iteData
ReadN one
Setup
IdleNone
Data = 0x40
Addr = Location t o program
Data = Data to pr ogram
Addr = Location t o program
Status regi ster dat a: Toggle C E# or
OE# to update Status Regi ster
Chec k SR[7]
1 = WSM Ready
0= WSM Busy
Comments
Progr am
Complete
Read St atus
Regi ster
SR[3] =
0
SR[4] =
0
SR[1] =
0
Progr am
Successful
1V
1
1
FULL STATUS CHECK PROCEDURE
Bus
Operation
Range
PP
Err or
Progr am
Err or
SR[3] MU ST be clear ed before the Wri te State Machi ne wil l
Device
Protect Err or
all ow fur ther pr ogram at tempts.
If an er ror is detected, c lear t he Status R egister befor e
conti nuing operations - onl y the C lear St aus Regi ster
com mand cl ears t he Status Regi ster er ror bits.
Command
Idle
None
Idle
None
IdleNone
Comments
Chec k SR[3]:
1= V
Err or
PP
Chec k SR[4]:
1= DataProgramError
Chec k SR[1]:
1 = Bl ock loc ked; operati on aborted
52Datasheet
Intel£Advanced+ Boot Block Flash Memory (C3)
Figure 14. Program Suspend / Resume Flowchart
PROGRAM SUSPEND / RESUME PROCEDURE
Start
Wr ite 0xB0
Any Address
Wr ite 0x70
Any Address
Read Status
Regi ster
SR[7] =
SR[2] =
Wr ite 0xF F
Read Array
Data
Done
Reading
Wr ite 0xD 0
Any Address
1
1
Yes
(Program Suspend)
(Read Status)
0
0
(Read Array)
No
(Program Resume)
Completed
Wr ite 0xF F
Read Ar ray
Progr am
Data
(Re ad
Array)
Bus
Operat ion
CommandComments
Wr ite
Wr ite
ReadNone
IdleNone
IdleNone
Wr ite
ReadNone
Wr ite
Read
Status
Pr ogram
Suspend
Read
Arr ay
Pr ogram
Resume
Data = 0x70
Addr = Any address
Data = 0xB0
Addr = Any address
Status regi ster data
Toggle CE# or OE# to update Status
regi ster
Addr = Any address
Check SR [7]:
1 = WSM r eady
0= WSM busy
Check SR [2]:
1 = Pr ogram s uspended
0 = Pr ogram c ompl eted
Data = 0xFF
Addr = Any address
Read ar ray data fr om bl ock other than
the one being progr ammed
Data = 0xD0
Addr = Any address
Progr am
Resumed
Datasheet53
Intel£Advanced+ Boot Block Flash Memory (C3)
Figure 15. Erase Suspend / Resume Flowchart
ERASE SUSPEND / RESUME PROCEDURE
(Rea d A rray)
(E ra se R esu m e)
Star t
Write 0x B0,
Any A ddr ess
Write 0x 70,
Any A ddr ess
Read Status
Regis ter
SR[7] =
1
SR[6] =
1
Wr it e 0x FF
Read Array
Data
Done
Reading
1
Write 0x D0,
Any A ddr ess
(Erase Suspend)
(Read Status)
0
0
0
Erase
Completed
Wri te 0x FF
Bus
Operation
Wri te
Wri te
ReadNone
Idle
Idle
Wri te
Read or
Wri te
Wri te
(Rea d A rray)
CommandComment s
Read
Data= 0x70
Status
Addr = Any address
Erase
Suspend
Read Array
or Pr ogram
Program
Resume
Data= 0xB0
Addr = Any address
Status R egister data. Toggl e CE# or
OE# to update Status register;
Addr = Any Addr ess
Check SR [7]:
1 = WSM ready
None
0 = WSM busy
Check SR [6]:
None
1 = Erase suspended
0 = Erase com pleted
Data = 0xFF or 0x40
Addr = Any address
Read ar ray or progr am data fr om/ to
None
block other than the one being eras ed
Data= 0xD0
Addr = Any address
Erase
Resumed
Read Array
Data
54Datasheet
Figure 16. Block Erase Flowchart
Intel£Advanced+ Boot Block Flash Memory (C3)
BLOCK ERASE P ROCEDURE
Start
Wri te 0x20,
Block Addr ess
Wri te 0xD0,
Block Addr ess
Read Status
Regist er
SR[7] =
1
Full Erase
Status Chec k
(if des ir ed)
Block Er ase
Complete
Read Status
Regist er
SR[3] =
0
SR[4,5] =
0
SR[5] =
0
SR[1] =
0
Block Er ase
Successful
(Bl ock Era se)
(Erase Confirm)
No
Suspend
0Yes
Eras e
FULL E RASE STATUS CHECK PROCE DURE
1
1,1
1
1
VPPRange
Error
Command
Sequenc e Error
Block Er ase
Error
Block Lock ed
Error
Suspend
Eras e
Loop
Bus
Operat ion
CommandComments
Bloc k
Wr ite
Wr ite
Confi rm
ReadNone
Data= 0x20
Eras e
Addr = Bloc k to be er ased ( BA)
Setup
Eras e
Data= 0xD0
Addr = Bloc k to be er ased ( BA)
Status Regi ster data. Toggl e C E# or
OE# t o update Status r egister data
Check SR [7]:
IdleNone
1 = WSM ready
0= WSM busy
Repeat f or s ubsequent block er asur es.
Full Status r egister chec k can be done aft er each block er ase
or after a s equence of bl ock er asur es.
Wr ite 0x FF after t he las t oper ation to enter r ead ar ray m ode.
Bus
Operat ion
CommandComments
IdleNone
IdleNone
IdleNone
Check SR [3]:
1= V
PP
Check SR[4,5]:
Both 1 = Com mand Sequence Err or
Check SR [5]:
1 = Bl ock Erase Error
Range Error
Check SR [1]:
IdleNone
1 = Attem pted er ase of l ocked bl ock;
erase abor ted.
SR[1,3] must be cleared before the Wri te State Machine w il l
allow further erase attempts.
Onl y the Cl ear Status Regi ster com mand cl ears SR [1, 3, 4, 5].
If an error i s detected, cl ear the Status r egis ter before
attempting an er ase r etry or other err or rec overy.
Program Pr otection R egister oper ation addr esses m ust be
wi thin the Pr otecti on Register address s pace. Addr esses
outsi de this s pace wi ll r eturn an er ror .
Repeat f or subsequent pr ogram ming oper ations.
Ful l Status Regi ster c heck can be done after each pr ogram , or
after a sequence of progr am operations.
Wri te 0xFF after the l ast operati on to set R ead Arr ay state.
Operation
SR[ 3] m ust be cl eared befor e the Wri te State M achine w ill
all ow fur ther pr ogram attem pts.
Only the C lear St aus R egister com mand cl ears SR [1, 3, 4].
If an er ror is detected, c lear the Status r egister befor e
attem pting a pr ogram r etry or other error r ecovery .
CommandComments
Progr am
Wr ite
PR Setup
Protecti on
Wr ite
ReadNone
Idle
Bus
Command
Idle
Idle
IdleNone
Data = 0xC0
Addr = F ir st Loc ati on to P rogr am
Data = D ata to Program
Progr am
Addr = Location to Pr ogram
Status Regi ster Data. T oggle C E# or
OE# to U pdate Status R egister D ata
Chec k SR[7]:
None
1 = WSM R eady
0=WSM Busy
Chec k SR[1], SR [3], SR[4]:
None
0,1,1 = V
Chec k SR[1], SR [3], SR[4]:
None
0,0,1 = Pr ogram mi ng Er ror
Chec k SR[1], SR [3], SR[4]:
1,0,1 = Bloc k locked; oper ation abor ted
Comments
Range Er ror
PP
Datasheet57
Intel£Advanced+ Boot Block Flash Memory (C3)
Appendix C Common Flash Interface
This appendix defines the data structure or “database” returned by the Common Flash Interface
(CFI) Query command. System software should parse this structure to gain critical information
such as block size, density, x8/x16, and electrical specifications. Once this information has been
obtained, the software will know which command sets to use to enable flash writes, block erases,
and otherwise control the flash component. The Query is part of an overall specification for
multiple command set and control interface descriptions called Common Flash Interface, or CFI.
C.1Query Structure Output
The Query database allows system software to obtain information for controlling the flash device.
This section describes the device’s CFI-compliant interface that allows access to Query data.
Query data are presented on the lowest-order data outputs (DQ0-DQ7) only. The numerical offset
value is the address relative to the maximum bus width supported by the device. On this family of
devices, the Query table device starting address is a 0x10, which is a word address for x16 devices.
For a word-wide (x16) device, the first two Query-structure bytes, ASCII “Q” and “R,” appear on
the low byte at word addresses 0x10 and 0x11. This CFI-compliant device outputs 0x00 data on
upper bytes. The device outputs ASCII “Q” in the low byte (DQ0-DQ7) and 0x00 in the high byte
(DQ8-DQ15).
At Query addresses containing two or more bytes of information, the least significant data byte is
presented at the lower address, and the most significant data byte is presented at the higher address.
In all of the following tables, addresses and data are represented in hexadecimal notation, so the
“h” suffix has been dropped. In addition, since the upper byte of word-wide devices is always
“0x00,” the leading “00” has been dropped from the table notation and only the lower byte value is
shown. Any x16 device outputs can be assumed to have 0x00 on the upper byte in this mode.
Table 24. Summary of Query Structure Output as a Function of Device and Mode
DeviceHex OffsetHex CodeASCII Value
00010:51"Q"
Device Addresses
00011:52"R"
00012:59"Y"
Table 25. Example of Query Structure Output of x16 Devices (Sheet 1 of 2)
Word Addressing:
OffsetHex CodeValue
A[X-0]DQ[16:0]
0x000100051"Q"
0x000110052"R"
0x000120059"Y"
0x00013P_IDLOPrVendor
58Datasheet
Intel£Advanced+ Boot Block Flash Memory (C3)
Table 25. Example of Query Structure Output of x16 Devices (Sheet 2 of 2)
0x00014P_IDHIID #
0x00015PLOPrVendor
0x00016PHITblAdr
0x00017A_IDLOAltVendor
0x00018A_IDHIID #
.........
C.2Query Structure Overview
The Query command causes the flash component to display the Common Flash Interface (CFI)
Query structure or “database.” The structure sub-sections and address locations are summarized
below.
Table 26. Query Structure
OffsetSub-Section Name
0x00000Manufacturer Code
0x00001Device Code
0x(BA+2)
0x00004-0xFReservedReserved for vendor-specific information
1. Refer to the Query Structure Output section and offset 0x28 for the detailed definition of offset address as a
2. BA = Block Address beginning location (i.e., 0x08000 is block 1’s beginning location when the block size is
3. Offset 15 defines “P” which points to the Primary Intel-specific Extended Query Table.
2
3
function of device bus width and mode.
32K-word).
Block Status registerBlock-specific information
CFI query identification
string
System interface
information
Primary Intel-specific
Extended Query Table
Command set ID and vendor data offset
Device timing & voltage information
Vendor-defined additional information specific to the Primary
Vendor Algorithm
Description
1
C.3Block Status Register
The Block Status Register indicates whether an erase operation completed successfully or whether
a given block is locked or can be accessed for flash program/erase operations.
Block Erase Status (BSR[1]) allows system software to determine the success of the last block
erase operation. BSR[1] can be used just after power-up to verify that the VCC supply was not
accidentally removed during an erase operation.
Datasheet59
Intel£Advanced+ Boot Block Flash Memory (C3)
Table27. BlockStatusRegister
OffsetLengthDescriptionAdd.Value
Block Lock Status RegisterBA+2--00 or --01
BSR[0] Block lock status
0 = Unlocked
0x(BA+2)
NOTES:
1. BA = Block Address beginning location (i.e., 0x08000 is block 1’s beginning location when the block size is
1
32K-word).
1
1 = Locked
BSR[1] Block lock-down status
0 = Not locked down
1=Lockeddown
BSR[7:2]:
Reserved for future useBA+2(bit 2-7): 0
C.4CFI Query Identification String
The Identification String provides verification that the component supports the Common Flash
Interface specification. It also indicates the specification version and supported vendor-specified
command set(s).
Optional feature and command support (1=yes,
0=no)
bits 9–31 are reserved; undefined bits are “0.” If bit
31 is “1” then another 31 bit field of optional
features follows at the end of the bit-30 field.
bit 0 Chip erase supported
bit 1 Suspend erase supported
bit 2 Suspend program supported
bit 3 Legacy lock/unlock supported
bit 4 Queued erase supported
bit 5 Instant individual block locking supported
bit 6 Protection bits supported
bit 7 Page mode read supported
bit 8 Synchronous read supported
Description
AddressHex CodeValue
35:
36:
37:
3A:
3B:
3C:
3D:
--50
--52
--49
--66
--00
--00
--00
bit 0 = 0
bit 1 = 1
bit 2 = 1
bit 3 = 0
bit 4 = 0
bit 5 = 1
bit 6 = 1
bit 7 = 0
bit 8 = 0
“P”
“R”
“I”
No
Yes
Yes
No
No
Yes
Yes
No
No
62Datasheet
Intel£Advanced+ Boot Block Flash Memory (C3)
Table 32. Primary-Vendor Specific Extended Query (Sheet 2 of 2)
1
Offset
P = 0x15
Length
(Optional Flash Features and Commands)
Supported functions after suspend: Read Array,
Status, Query
0x(P+9)1
Other supported operations are:
bits 1–7 reserved; undefined bits are “0”
bit 0 Program supported after erase suspendbit 0 = 1Yes
Block status register mask
0x(P+A)
0x(P+B)
2
bits 2–15 are Reserved; undefined bits are “0”
bit 0 Block Lock-Bit Status Register active
bit 1 Block Lock-Down Bit Status active
V
logic supply highest performance program/
CC
0x(P+C)1
erase voltage
bits 0–3 BCD value in 100 mV
bits 4–7 BCD value in volts
V
optimum program/erase supply voltage
0x(P+D)1
PP
bits 0–3 BCD value in 100 mV
bits 4–7 HEX value in volts
NOTES:
1. The variable P is a pointer which is defined at CFI offset 0x15.
Description
AddressHex CodeValue
3E:--01
3F:--03
40:--00
bit 0 = 1Yes
bit 1 = 1Yes
41:--333.3 V
42:--C012.0 V
Table 33. Protection Register Information
1
Offset
P = 0x35
0x(P+E)1
Length
(Optional Flash Features and Commands)
Number of Protection register fields in JEDEC ID space.
“00h,” indicates that 256 protection bytes are available
0x(P+F)
0x(P+10)
(0xP+11)
Protection Field 1: Protection Description
This field describes user-available One Time Programmable (OTP)
Protection register bytes. Some are pre-programmed with deviceunique serial numbers. Others are user programmable. Bits 0–15
4
point to the Protection register Lock byte, the section’s first byte.
0x(P+12)
The following bytes are factory pre-programmed and userprogrammable.
bits 0–7 = Lock/bytes JEDEC-plane physical low address
bits 8–15 = Lock/bytes JEDEC -plane physical high address
bits 16–23 = “n” such that 2
bits 24–31 = “n” such that 2
0x(P+13)Reserved for future use48:
NOTES:
1. The variable P is a pointer which is defined at CFI offset 0x15.
Description
n
= factory pre-programmed bytes
n
= user programmable bytes
Address
Hex
Code
Val ue
43:--0101
44:
45:
46:
--80
--00
--03
80h
00h
8byte
47:--038 byte
Datasheet63
Intel£Advanced+ Boot Block Flash Memory (C3)
R0
Appendix D Mechanical Specifications
Figure 19. µBGA* and VF BGA Package Drawing & Dimensions
Ball A1
Corner
E
D
12345678
A
B
C
D
E
F
Top View - Bump Side down
4
5678
A
B
C
D
E
F
b
Bottom View -Bump side up
123
S1
Ball A1
Corner
S2
e
A
1
A2
A
Seating
Plan
Y
Side View
Note: Drawing not to scale
Dimens ionsSymbolMinNomMaxMinNomMax
Pac kage Heig htA1.0000.0394
Ball Heigh tA10.1500.0059
Pac kage Bod y Th icknes sA20.6650.0262
Ball (Lea d) W idt hb0.3250.3750.4250.01280.01480.0167
Pac kage Bod y Lengt h 8M (.25)D7.8107.9108.010
Pac kage Bod y Lengt h 16M (.25/.18/.13) 32M (.25/ .18/.13)D7.1867.2867.3860.28290.28680.2908
Pac kage Bod y Lengt h 64M (.18)D7.6007.7007.8000.29920.30310.3071
Pac kage Bod y Widt h 8M (.25)E6.4006. 5006.6000.25200.25590.2598
Pac kage Bod y Widt h 16M (.25/ .18/.13) 32M (.18/.13)E6.8646.9647.0640.27020.27420.2781
Pac kage Bod y Widt h 32M (.25)E10.75010.85010. 8600.42320.42720.4276
Pac kage Bod y Widt h 64M (.18)E8.9009.0009.1000.35040.35430.3583
Pitc he0.7500.0295
Ball (Lea d) Cou nt 8M, 16MN4646
Ball (Lead) Count 32MN4747
Ball (Lead) Count 64MN4848
Sea ting Plan e Cop lanarityY0.1000.0039
Corn er to Ball A 1 Dist anc e Alo ng D 8M (.25)S11.2301.3301.4300.04840.05240.0563
Corn er to Ball A 1 Dist anc e Alo ng D 16M (.25/ .18/.13) 32M (.18/ .13)S10.9181.0181.1180.03610.04010.0440
Corn er to Ball A 1 Dist anc e Alo ng D 64M (.18)S11.1251.2251.3250.04430.04820.0522
Corn er to Ball A 1 Dist anc e Alo ng E 8M (. 25)S21.2751.3751.4750.05020. 05410.0581
Corn er to Ball A 1 Dist anc e Alo ng E 16M (.25/.18/.13) 32M (.18/.13)S21.5071.6071.7070.05930. 06330.0672
Corn er to Ball A 1 Dist anc e Alo ng E 32M (.25)S23.4503.5503.6500.13580.13980.1437
Corn er to Ball A 1 Dist anc e Alo ng E 64M (.18)S22.5252.6252.7250.09940.10330.1073
MillimetersInches
64Datasheet
Intel£Advanced+ Boot Block Flash Memory (C3)
Figure 20. TSOP Package Drawing & Dimensions
Dimensions
Pin 1
Z
See Not es 1, 2, 3 and 4
D
1
D
A
2
E
A
Seating
Plane
See Det ail A
A
Detail A
Detail B
C
b
Fami ly: Th in Smal l Out-Line Package
Symbol
Package H eightA1.2000.047
StandoffA10.0500.002
Package Body Thick nessA20. 950 1.000 1.0500.037 0.039 0.041
Lead Widthb0.150 0.200 0.3000.006 0.008 0.012
Lead Thick nessc0.100 0.150 0.2000.004 0.006 0. 008
Plastic Body LengthD118.200 18.400 18.6000.717 0.724 0.732
Pack age Body W idt hE11.800 12. 000 12. 2000. 465 0. 472 0.480
Lead Pitche0.5000.0197
Term inal Dim ensionD19. 800 20.0 00 20.2000. 780 0.787 0. 795
Lead Tip LengthL0.500 0.600 0.7000. 020 0.024 0.028
Lead CountN4848
Lead T ip AngleØ0°3°5°0°3°5°
Seating Plane CoplanarityY0.1000.004
Lead to Pack age Off setZ0.150 0.250 0.3500.006 0.010 0. 014
MillimetersInches
Min
NomMax Notes MinNomMax Notes
0
L
e
SeeD etailB
Y
1
A5568-02
1. One dimple on package denotes Pin 1.
2. If two dimples, then the larger dimple denotes Pin 1.
3. Pin 1 will always be in the upper left corner of the package, in reference to the product mark.
4. Pin 1 will always supersede above pin one notes.
Datasheet65
Intel£Advanced+ Boot Block Flash Memory (C3)
j
Figure 21. Easy BGA Package Drawing & Dimension
Ball A1
Corner
E
D
8765432187654321
A
B
C
D
E
F
G
H
Top View - Ball side downBottom View - Ball Side Up
A1
A2
Side View
A
B
C
D
E
F
G
H
A
Seating
Plane
Note: Drawing not to scale
S1
Y
b
e
Ball A1
Corner
S2
Dimensions Table
Millimet ersIn ch es
SymbolMinNomMax NotesMinNomMax
Packa ge Heig htA1.2000.0472
Ball Heigh tA
Package Body ThicknessA
Ball (Lead ) Wid thb0.3300.4300.5300.01300.01690.0209
Packa ge Bod y W idthD9.90010.00010.10010.38980.39370.3976
Packa ge Bod y Len gthE12.90013.00013.10010.50790.51180.5157
Pitch[e]1.0000.0394
Ball (Lead) CountN6464
Seat ing Plan e Copla narityY0.1000.0039
Corner to BallA1 Dis tance Along DS
Corner to BallA1 Dis tance Along ES
Note: (1) Package dimensions are for reference only. These dimensions are estimates based
on die size, and are sub
ect to change.
1
0.2500.0098
2
1
1.4001.5001.60010.05510.05910.0630
2
2.9003.0003.10010.11420.11810.1220
0.7800.0307
66Datasheet
Intel£Advanced+ Boot Block Flash Memory (C3)
Appendix E Additional Information
Order NumberDocument/Tool
2979383 Volt Advanced+ Boot Block Flash Memory Specification Update
292216AP-658 Designing for Upgrade to the Advanced+ Boot Block Flash Memory
292215
Contact your Intel
Representative
297874IFDI Interactive: Play with Intel
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/design/flash’ for technical
documentation and tools.
AP-657 Designing with the Advanced+ Boot Block Flash Memory
Architecture
Intel®Flash Data Integrator (FDI) Software Developer’s Kit
®
Flash Data Integrator on Your PC
Datasheet67
Intel£Advanced+ Boot Block Flash Memory (C3)
k
Appendix F Ordering Information
Figure 22. Component Ordering Information
T E 2 8 F 3 2 0 C 3 T C 7 0
Package
TE = 48-Lead TSOP
GT = 48-Ball µ BGA* CSP
GE = VF BGA CSP
RC = Easy BGA
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.
68Datasheet
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.