Am29F400B: Data Sheet
Am29F400B: Data Sheet
Am29F400B: Data Sheet
Data Sheet
Continuity of Specifications
There is no change to this data sheet as a result of offering the device as a Spansion product. Any
changes that have been made are the result of normal data sheet improvement and are noted in the
document revision summary.
Am29F400B
4 Megabit (512 K x 8-Bit/256 K x 16-Bit)
CMOS 5.0 Volt-only Boot Sector Flash Memory
DISTINCTIVE CHARACTERISTICS
■ Single power supply operation ■ Embedded Algorithms
— 5.0 volt-only operation for read, erase, and — Embedded Erase algorithm automatically
program operations preprograms and erases the entire chip or any
— Minimizes system level requirements combination of designated sectors
— Embedded Program algorithm automatically
■ Manufactured on 0.32 µm process technology
writes and verifies data at specified addresses
— Compatible with 0.5 µm Am29F400 device
■ Minimum 1,000,000 program/erase cycles per
■ High performance sector guaranteed
— Access times as fast as 45 ns ■ 20-year data retention at 125°C
■ Low power consumption (typical values at — Reliable operation for the life of the system
5 MHz) ■ Package option
— 1 µA standby mode current — 48-pin TSOP
— 20 mA read current (byte mode) — 44-pin SO
— 28 mA read current (word mode) — Known Good Die (KGD)
— 30 mA program/erase current (see publication number 21258)
■ Flexible sector architecture ■ Compatibility with JEDEC standards
— One 16 Kbyte, two 8 Kbyte, one 32 Kbyte, and — Pinout and software compatible with single-
seven 64 Kbyte sectors (byte mode) power-supply Flash
— One 8 Kword, two 4 Kword, one 16 Kword, and — Superior inadvertent write protection
seven 32 Kword sectors (word mode)
■ Data# Polling and toggle bits
— Supports full chip erase
— Provides a software method of detecting
— Sector Protection features: program or erase operation completion
A hardware method of locking a sector to
■ Ready/Busy# pin (RY/BY#)
prevent any program or erase operations within
that sector — Provides a hardware method of detecting
program or erase cycle completion
Sectors can be locked via programming
equipment ■ Erase Suspend/Erase Resume
Temporary Sector Unprotect feature allows code — Suspends an erase operation to read data from,
changes in previously locked sectors or program data to, a sector that is not being
erased, then resumes the erase operation
■ Top or bottom boot block configurations available
■ Hardware reset pin (RESET#)
— Hardware method to reset the device to reading
array data
This Data Sheet states AMD’s current technical specifications regarding the Products described herein. This Data Publication# 21505 Rev: E Amendment: 5
Sheet may be revised by subsequent versions or modifications due to changes in technical specifications. Issue Date: November 1, 2006
D A T A S H E E T
GENERAL DESCRIPTION
The Am29F400B is a 4 Mbit, 5.0 volt-only Flash Device erasure occurs by executing the erase
memory organized as 524,288 bytes or 262,144 words. command sequence. This initiates the Embedded
The device is offered in 44-pin SO and 48-pin TSOP Erase algorithm—an internal algorithm that automatically
packages. The device is also available in Known Good preprograms the array (if it is not already programmed)
Die (KGD) form. For more information, refer to publica- before executing the erase operation. During erase, the
tion number 21258. The word-wide data (x16) appears device automatically times the erase pulse widths and
on DQ15–DQ0; the byte-wide (x8) data appears on verifies proper cell margin.
DQ7–DQ0. This device is designed to be programmed in-
The host system can detect whether a program or
system with the standard system 5.0 volt VCC supply. A 12.0
erase operation is complete by observing the RY/BY#
V VPP is not required for write or erase operations. The
pin, or by reading the DQ7 (Data# Polling) and DQ6/
device can also be programmed in standard EPROM
DQ2 (toggle) status bits. After a program or erase
programmers.
cycle has been completed, the device is ready to read
This device is manufactured using AMD’s 0.32 µm array data or accept another command.
process technology, and offers all the features and ben-
The sector erase architecture allows memory sectors
efits of the Am29F400, which was manufactured using
to be erased and reprogrammed without affecting the
0.5 µm process technology.
data contents of other sectors. The device is fully
The standard device offers access times of 45, 50, 55, erased when shipped from the factory.
70, 90, and 120 ns, allowing high speed microproces-
Hardware data protection measures include a low
sors to operate without wait states. To eliminate bus
VCC detector that automatically inhibits write opera-
contention the device has separate chip enable (CE#),
tions during power transitions. The hardware sector
write enable (WE#) and output enable (OE#) controls.
protection feature disables both program and erase
The device requires only a single 5.0 volt power operations in any combination of the sectors of memory.
supply for both read and write functions. Internally This can be achieved via programming equipment.
generated and regulated voltages are provided for the
The Erase Suspend feature enables the user to put
program and erase operations.
erase on hold for any period of time to read data from,
The device is entirely command set compatible with the or program data to, any sector that is not selected for
JEDEC single-power-supply Flash standard. Com- erasure. True background erase can thus be achieved.
mands are written to the command register using
The hardware RESET# pin terminates any operation
standard microprocessor write timings. Register con-
in progress and resets the internal state machine to
tents serve as input to an internal state-machine that
reading array data. The RESET# pin may be tied to the
controls the erase and programming circuitry. Write
system reset circuitry. A system reset would thus also
cycles also internally latch addresses and data needed
reset the device, enabling the system microprocessor
for the programming and erase operations. Reading
to read the boot-up firmware from the Flash memory.
data out of the device is similar to reading from other
Flash or EPROM devices. The system can place the device into the standby
mode. Power consumption is greatly reduced in this mode.
Device programming occurs by executing the program
command sequence. This initiates the Embedded AMD’s Flash technology combines years of Flash
Program algorithm—an internal algorithm that auto- memory manufacturing experience to produce the
matically times the program pulse widths and verifies highest levels of quality, reliability and cost effective-
proper cell margin. ness. The device electrically erases all bits within a sector
simultaneously via Fowler-Nordheim tunneling. The data is
programmed using hot electron injection.
TABLE OF CONTENTS
Product Selector Guide . . . . . . . . . . . . . . . . . . . . . 4 Figure 7. Maximum Positive Overshoot Waveform........................ 22
Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Operating Ranges . . . . . . . . . . . . . . . . . . . . . . . . . 22
Connection Diagrams . . . . . . . . . . . . . . . . . . . . . . 5 DC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . 23
Pin Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 6 TTL/NMOS Compatible .......................................................... 23
Logic Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 CMOS Compatible .................................................................. 24
Ordering Information . . . . . . . . . . . . . . . . . . . . . . . 7 Test Conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Device Bus Operations . . . . . . . . . . . . . . . . . . . . . 8 Figure 8. Test Setup....................................................................... 25
Table 1. Am29F400B Device Bus Operations .................................. 8 Table 7. Test Specifications ........................................................... 25
Word/Byte Configuration .......................................................... 8 Key to Switching Waveforms. . . . . . . . . . . . . . . . 25
Requirements for Reading Array Data ..................................... 8 AC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . 26
Writing Commands/Command Sequences .............................. 8 Read Operations .................................................................... 26
Program and Erase Operation Status ...................................... 9 Figure 9. Read Operations Timings ............................................... 26
Standby Mode .......................................................................... 9 Hardware Reset (RESET#) .................................................... 27
RESET#: Hardware Reset Pin ................................................. 9 Figure 10. RESET# Timings .......................................................... 27
Output Disable Mode ................................................................ 9 Word/Byte Configuration (BYTE#) ...................................... 28
Table 2. Am29F400BT Top Boot Block Sector Address Table ....... 10 Figure 11. BYTE# Timings for Read Operations............................ 28
Table 3. Am29F400BB Bottom Boot Block Sector Address Table.. 10 Figure 12. BYTE# Timings for Write Operations............................ 28
Autoselect Mode ..................................................................... 10 Erase/Program Operations ..................................................... 29
Table 4. Am29F400B Autoselect Codes (High Voltage Method) .... 11 Figure 13. Program Operation Timings.......................................... 30
Figure 14. Chip/Sector Erase Operation Timings .......................... 31
Sector Protection/Unprotection ............................................... 11
Figure 15. Data# Polling Timings (During Embedded Algorithms). 32
Temporary Sector Unprotect .................................................. 11
Figure 16. Toggle Bit Timings (During Embedded Algorithms)...... 32
Figure 1. Temporary Sector Unprotect Operation........................... 11
Figure 17. DQ2 vs. DQ6................................................................. 33
Hardware Data Protection ...................................................... 12 Temporary Sector Unprotect .................................................. 33
Low VCC Write Inhibit ...................................................................... 12
Figure 18. Temporary Sector Unprotect Timing Diagram .............. 33
Write Pulse “Glitch” Protection........................................................ 12
Alternate CE# Controlled Erase/Program Operations ............ 34
Logical Inhibit .................................................................................. 12
Figure 19. Alternate CE# Controlled Write Operation Timings ...... 35
Power-Up Write Inhibit .................................................................... 12
Command Definitions . . . . . . . . . . . . . . . . . . . . . 13 Erase and Programming Performance . . . . . . . . 36
Reading Array Data ................................................................ 13 Latchup Characteristics . . . . . . . . . . . . . . . . . . . . 36
Reset Command ..................................................................... 13 TSOP and SO Pin Capacitance . . . . . . . . . . . . . . 36
Data Retention. . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Autoselect Command Sequence ............................................ 13
Word/Byte Program Command Sequence ............................. 13 Physical Dimensions . . . . . . . . . . . . . . . . . . . . . . 37
Figure 2. Program Operation .......................................................... 14 TS 048—48-Pin Standard Thin Small Outline Package ......... 37
Chip Erase Command Sequence ........................................... 14 SO 044—44-Pin Small Outline Package ................................ 38
Sector Erase Command Sequence ........................................ 14 Revision Summary . . . . . . . . . . . . . . . . . . . . . . . . 39
Erase Suspend/Erase Resume Commands ........................... 16 Revision A (August 1997) ....................................................... 39
Figure 3. Erase Operation............................................................... 16 Revision B (October 1997) ..................................................... 39
Table 5. Am29F400B Command Definitions................................... 17 Revision C (January 1998) ..................................................... 39
Write Operation Status . . . . . . . . . . . . . . . . . . . . 18 Revision C+1 (February 1998) ............................................... 39
DQ7: Data# Polling ................................................................. 18 Revision C+2 (April 1998) ....................................................... 39
Figure 4. Data# Polling Algorithm ................................................... 18 Revision C+3 (June 1998) ...................................................... 39
RY/BY#: Ready/Busy# ........................................................... 19 Revision C+4 (August 1998) ................................................... 40
DQ6: Toggle Bit I .................................................................... 19 Revision D (January 1999) ..................................................... 40
DQ2: Toggle Bit II ................................................................... 19 Revision D+1 (July 2, 1999) ................................................... 40
Reading Toggle Bits DQ6/DQ2 .............................................. 19 Revision E (November 15, 1999) ............................................ 40
DQ5: Exceeded Timing Limits ................................................ 20 Revision E+1 (November 30, 2000) ....................................... 40
DQ3: Sector Erase Timer ....................................................... 20 Revision E+2 (June 4, 2004) .................................................. 40
Figure 5. Toggle Bit Algorithm......................................................... 20 Revision E+3 (December 22, 2005) ....................................... 40
Table 6. Write Operation Status...................................................... 21 Revision E4 (May 18, 2006) ................................................... 40
Absolute Maximum Ratings . . . . . . . . . . . . . . . . 22
Figure 6. Maximum Negative Overshoot Waveform ....................... 22
BLOCK DIAGRAM
RY/BY# DQ0–DQ15 (A-1)
VCC
Sector Switches
VSS
Erase Voltage Input/Output
RESET# Generator Buffers
WE# State
Control
BYTE#
Command
Register
PGM Voltage
Generator
Chip Enable Data
Output Enable STB Latch
CE#
Logic
OE#
Y-Decoder Y-Gating
STB
Address Latch
A0–A17
CONNECTION DIAGRAMS
This device is also available in Known Good Die (KGD) form. Refer to publication number 21258 for
more information.
A15 1 48 A16
A14 2 47 BYTE#
A13 3 46 VSS
A12 4 45 DQ15/A-1
A11 5 44 DQ7
A10 6 43 DQ14
A9 7 42 DQ6
A8 8 41 DQ13
NC 9 40 DQ5
NC 10 39 DQ12
WE# 11 48-Pin TSOP—Standard Pinout 38 DQ4
RESET# 12 37 VCC
NC 13 36 DQ11
NC 14 35 DQ3
RY/BY# 15 34 DQ10
NC 16 33 DQ2
A17 17 32 DQ9
A7 18 31 DQ1
A6 19 30 DQ8
A5 20 29 DQ0
A4 21 28 OE#
A3 22 27 VSS
A2 23 26 CE#
A1 24 25 A0
NC 1 44 RESET#
RY/BY# 2 43 WE#
A17 3 42 A8
A7 4 41 A9
A6 5 40 A10
A5 6 39 A11
A4 7 38 A12
A3 8 37 A13
A2 9 36 A14
A1 10 35 A15
A0 11 SO 34 A16
CE# 12 33 BYTE#
VSS 13 32 VSS
OE# 14 31 DQ15/A-1
DQ0 15 30 DQ7
DQ8 16 29 DQ14
DQ1 17 28 DQ6
DQ9 18 27 DQ13
DQ2 19 26 DQ5
DQ10 20 25 DQ12
DQ3 21 24 DQ4
DQ11 22 23 VCC
ORDERING INFORMATION
Standard Products
AMD standard products are available in several packages and operating ranges. The order number (Valid Combi-
nation) is formed by a combination of the elements below.
Am29F400B T -45 E C
OPTIONAL PROCESSING
Blank = Standard Processing
0 = VCC = 5.0 V ± 10%, 55 ns device only
(Contact an AMD representative for more information)
TEMPERATURE RANGE
C = Commercial (0°C to +70°C)
D = Commercial (0°C to +70°C) with Pb-Free Package
I = Industrial (–40°C to +85°C)
F = Industrial (–40°C to +85°C) with Pb-Free Package
E = Extended (–55°C to +125°C)
K = Extended (–55°C to +125°C) with Pb-free Package
PACKAGE TYPE
E = 48-Pin Thin Small Outline Package (TSOP)
Standard Pinout (TS 048)
S = 44-Pin Small Outline Package (SO 044)
This device is also available in Known Good Die (KGD) form. See publication number
21258 for more information.
SPEED OPTION
See Product Selector Guide and Valid Combinations
DEVICE NUMBER/DESCRIPTION
Am29F400B
4 Megabit (512 K x 8-Bit/256 K x 16-Bit) CMOS Flash Memory
5.0 Volt-only Read, Program and Erase
Valid Combinations
Voltage
Valid Combinations list configurations planned to be sup-
Valid Combinations Range
ported in volume for this device. Consult the local AMD sales
AM29F400BT-45, EC, ED, EI, EF, office to confirm availability of specific valid combinations and
AM29F400BB-45, SC, SD, SI, SF to check on newly released combinations.
AM29F400BT-50,
5.0 V ± 5%
AM29F400BB-50 EC, ED, EI, EF, EE, EK
AM29F400BT-55, SC, SD, SI, SF, SE, SK
AM29F400BB-55
AM29F400BT-70,
AM29F400BB-70 5.0 V ± 10%
EC, ED, EI,
AM29F400BT-90, EF, EE, EK
AM29F400BB-90 SC, SD, SI,
SF, SE, SK
AM29F400BT-120,
AM29F400BB-120
After the system writes the autoselect command In the CMOS and TTL/NMOS-compatible DC Charac-
sequence, the device enters the autoselect mode. The teristics tables, ICC3 represents the standby current
system can then read autoselect codes from the specification.
internal register (which is separate from the memory
array) on DQ7–DQ0. Standard read cycle timings apply RESET#: Hardware Reset Pin
in this mode. Refer to the “Autoselect Mode” and The RESET# pin provides a hardware method of reset-
“Autoselect Command Sequence” sections for more ting the device to reading array data. When the
information. RESET# pin is driven low for at least a period of tRP, the
ICC2 in the DC Characteristics table represents the device immediately terminates any operation in
active current specification for the write mode. The “AC progress, tristates all output pins, and ignores all read/
Characteristics” section contains timing specification write commands for the duration of the RESET# pulse.
tables and timing diagrams for write operations. The device also resets the internal state machine to
reading array data. The operation that was interrupted
Program and Erase Operation Status should be reinitiated once the device is ready to accept
another command sequence, to ensure data integrity.
During an erase or program operation, the system may
check the status of the operation by reading the status Current is reduced for the duration of the RESET#
bits on DQ7–DQ0. Standard read cycle timings and ICC pulse. When RESET# is held at VIL, the device enters
read specifications apply. Refer to “The Erase Resume the TTL standby mode; if RESET# is held at VSS±0.5
command is valid only during the Erase Suspend V, the device enters the CMOS standby mode.
mode.” for more information, and to “AC Characteris-
The RESET# pin may be tied to the system reset cir-
tics” for timing diagrams.
cuitry. A system reset would thus also reset the Flash
memory, enabling the system to read the boot-up firm-
Standby Mode
ware from the Flash memory.
When the system is not reading or writing to the device,
it can place the device in the standby mode. In this If RESET# is asserted during a program or erase oper-
mode, current consumption is greatly reduced, and the ation, the RY/BY# pin remains a “0” (busy) until the
outputs are placed in the high impedance state, inde- internal reset operation is complete, which requires a
pendent of the OE# input. time of tREADY (during Embedded Algorithms). The
system can thus monitor RY/BY# to determine whether
The device enters the CMOS standby mode when the the reset operation is complete. If RESET# is asserted
CE# and RESET# pins are both held at VCC ± 0.5 V. when a program or erase operation is not executing
(Note that this is a more restricted voltage range than (RY/BY# pin is “1”), the reset operation is completed
VIH.) The device enters the TTL standby mode when within a time of tREADY (not during Embedded Algo-
CE# and RESET# pins are both held at VIH. The device rithms). The system can read data t RH after the
requires standard access time (tCE) for read access RESET# pin returns to VIH.
when the device is in either of these standby modes,
before it is ready to read data. Refer to the AC Characteristics tables for RESET#
parameters and to Figure 10 for the timing diagram.
The device also enters the standby mode when the
RESET# pin is driven low. Refer to the next section, Output Disable Mode
“RESET#: Hardware Reset Pin”.
When the OE# input is at VIH, output from the device is
If the device is deselected during erasure or program- disabled. The output pins are placed in the high imped-
ming, the device draws active current until the ance state.
operation is completed.
Autoselect Mode
The autoselect mode provides manufacturer and the sector address must appear on the appropriate
device identification, and sector protection verification, highest order address bits (see Tables 2 and 3). Table
through identifier codes output on DQ7–DQ0. This 4 shows the remaining address bits that are don’t care.
mode is primarily intended for programming equipment When all necessary bits have been set as required, the
to automatically match a device to be programmed with programming equipment may then read the corre-
its corresponding programming algorithm. However, sponding identifier code on DQ7–DQ0.
the autoselect codes can also be accessed in-system
To access the autoselect codes in-system, the host
through the command register.
system can issue the autoselect command via the
When using programming equipment, the autoselect command register, as shown in Table 5. This method
mode requires VID (11.5 V to 12.5 V) on address pin does not require VID. See “Command Definitions” for
A9. Address pins A6, A1, and A0 must be as shown in details on using the autoselect mode.
Table 4. In addition, when verifying sector protection,
01h
X
(protected)
Sector Protection Verification L L H SA X VID X L X H L
00h
X
(unprotected)
L = Logic Low = VIL, H = Logic High = VIH, SA = Sector Address, X = Don’t care.
Sector Protection/Unprotection rithm, and Figure 18 shows the timing diagrams, for this
feature.
The hardware sector protection feature disables both
program and erase operations in any sector. The hard-
ware sector unprotection feature re-enables both
program and erase operations in previously protected START
sectors.
Sector protection/unprotection must be implemented RESET# = VID
using programming equipment. The procedure (Note 1)
requires a high voltage (VID) on address pin A9 and
OE#. Details on this method are provided in a supple-
Perform Erase or
ment, publication number 20185. Contact an AMD Program Operations
representative to obtain a copy of this document.
The device is shipped with all sectors unprotected.
AMD offers the option of programming and protecting RESET# = VIH
sectors at its factory prior to shipping the device
through AMD’s ExpressFlash™ Service. Contact an
AMD representative for details. Temporary Sector
Unprotect Completed
It is possible to determine whether a sector is protected (Note 2)
or unprotected. See “Autoselect Mode” for details.
Hardware Data Protection proper signals to the control pins to prevent uninten-
tional writes when VCC is greater than VLKO.
The command sequence requirement of unlock cycles
for programming or erasing provides data protection Write Pulse “Glitch” Protection
against inadver tent writes (refer to Table 5 for Noise pulses of less than 5 ns (typical) on OE#, CE# or
command definitions). In addition, the following hard- WE# do not initiate a write cycle.
ware data protection measures prevent accidental
erasure or programming, which might otherwise be Logical Inhibit
caused by spurious system level signals during VCC Write cycles are inhibited by holding any one of OE# =
power-up and power-down transitions, or from system VIL, CE# = VIH or WE# = VIH. To initiate a write cycle,
noise. CE# and WE# must be a logical zero while OE# is a
Low VCC Write Inhibit logical one.
When V CC is less than V LKO, the device does not Power-Up Write Inhibit
accept any write cycles. This protects data during VCC If WE# = CE# = VIL and OE# = VIH during power up, the
power-up and power-down. The command register and device does not accept commands on the rising edge
all internal program/erase circuits are disabled, and the of WE#. The internal state machine is automatically
device resets. Subsequent writes are ignored until VCC reset to reading array data on power-up.
is greater than V LKO. The system must provide the
COMMAND DEFINITIONS
Writing specific address and data commands or however, the device ignores reset commands until the
sequences into the command register initiates device operation is complete.
operations. Table 5 defines the valid register command
The reset command may be written between the
sequences. Writing incorrect address and data
sequence cycles in an autoselect command sequence.
values or writing them in the improper sequence
Once in the autoselect mode, the reset command must
resets the device to reading array data.
be written to return to reading array data (also applies
All addresses are latched on the falling edge of WE# or to autoselect during Erase Suspend).
CE#, whichever happens later. All data is latched on
If DQ5 goes high during a program or erase operation,
the rising edge of WE# or CE#, whichever happens
writing the reset command returns the device to
first. Refer to the appropriate timing diagrams in the
reading array data (also applies dur ing Erase
“AC Characteristics” section.
Suspend).
Reading Array Data Autoselect Command Sequence
The device is automatically set to reading array data
The autoselect command sequence allows the host
after device power-up. No commands are required to
system to access the manufacturer and devices codes,
retrieve data. The device is also ready to read array
and determine whether or not a sector is protected.
data after completing an Embedded Program or
Table 5 shows the address and data requirements. This
Embedded Erase algorithm.
method is an alternative to that shown in Table 4, which
After the device accepts an Erase Suspend command, is intended for PROM programmers and requires VID
the device enters the Erase Suspend mode. The on address bit A9.
system can read array data using the standard read
The autoselect command sequence is initiated by
timings, except that if it reads at an address within
writing two unlock cycles, followed by the autoselect
erase-suspended sectors, the device outputs status
command. The device then enters the autoselect
data. After completing a programming operation in the
mode, and the system may read at any address any
Erase Suspend mode, the system may once again
number of times, without initiating another command
read array data with the same exception. See “Erase
sequence.
Suspend/Erase Resume Commands” for more infor-
mation on this mode. A read cycle at address XX00h or retrieves the manu-
facturer code. A read cycle at address XX01h in word
The system must issue the reset command to re-
mode (or 02h in byte mode) returns the device code. A
enable the device for reading array data if DQ5 goes
read cycle containing a sector address (SA) and the
high, or while in the autoselect mode. See the “Reset
address 02h in word mode (or 04h in byte mode)
Command” section, next.
returns 01h if that sector is protected, or 00h if it is
See also “Requirements for Reading Array Data” in the unprotected. Refer to Tables 2 and 3 for valid sector
“Device Bus Operations” section for more information. addresses.
The Read Operations table provides the read parame-
The system must write the reset command to exit the
ters, and Figure 9 shows the timing diagram.
autoselect mode and return to reading array data.
Reset Command Word/Byte Program Command Sequence
Writing the reset command to the device resets the
The system may program the device by word or byte,
device to reading array data. Address bits are don’t
depending on the state of the BYTE# pin. Program-
care for this command.
ming is a four-bus-cycle operation. The program
The reset command may be written between the command sequence is initiated by writing two unlock
sequence cycles in an erase command sequence write cycles, followed by the program set-up command.
before erasing begins. This resets the device to reading The program address and data are written next, which
array data. Once erasure begins, however, the device in turn initiate the Embedded Program algorithm. The
ignores reset commands until the operation is system is not required to provide further controls or tim-
complete. ings. The device automatically provides internally
generated program pulses and verify the programmed
The reset command may be written between the
cell margin. Table 5 shows the address and data
sequence cycles in a program command sequence
r e q u i r e m e n t s fo r t h e byt e p r o gra m c o m m a n d
before programming begins. This resets the device to
sequence.
reading array data (also applies to programming in
Erase Suspend mode). Once programming begins, When the Embedded Program algorithm is complete,
the device then returns to reading array data and
addresses are no longer latched. The system can Chip Erase Command Sequence
determine the status of the program operation by using
Chip erase is a six-bus-cycle operation. The chip erase
DQ7, DQ6, or RY/BY#. See “The Erase Resume
command sequence is initiated by writing two unlock
command is valid only during the Erase Suspend
cycles, followed by a set-up command. Two additional
mode.” for information on these status bits.
unlock write cycles are then followed by the chip erase
Any commands written to the device during the command, which in turn invokes the Embedded Erase
Embedded Program Algorithm are ignored. Note that a algorithm. The device does not require the system to
hardware reset immediately terminates the program- preprogram prior to erase. The Embedded Erase algo-
min g o pe ra ti on . T he B y te P ro gra m c om ma nd rithm automatically preprograms and verifies the entire
sequence should be reinitiated once the device has memory for an all zero data pattern prior to electrical
reset to reading array data, to ensure data integrity. erase. The system is not required to provide any con-
trols or timings during these operations. Table 5 shows
Programming is allowed in any sequence and across
the address and data requirements for the chip erase
sector boundaries. A bit cannot be programmed
command sequence.
from a “0” back to a “1”. Attempting to do so may halt
the operation and set DQ5 to “1”, or cause the Data# Any commands wr itten to the chip dur ing the
Polling algorithm to indicate the operation was suc- Embedded Erase algorithm are ignored. Note that a
cessful. However, a succeeding read will show that the hardware reset during the chip erase operation imme-
data is still “0”. Only erase operations can convert a “0” diately terminates the operation. The Chip Erase
to a “1”. command sequence should be reinitiated once the
device has returned to reading array data, to ensure
data integrity.
START
The system can determine the status of the erase oper-
ation by using DQ7, DQ6, DQ2, or RY/BY#. See “The
Erase Resume command is valid only during the Erase
Suspend mode.” for information on these status bits.
Write Program When the Embedded Erase algorithm is complete, the
Command Sequence device returns to reading array data and addresses are
no longer latched.
Figure 3 illustrates the algorithm for the erase opera-
Data Poll tion. See the “Erase/Program Operations” tables in “AC
from System Characteristics” for parameters, and to Figure 14 for
Embedded
Program timing diagrams.
algorithm
in progress Sector Erase Command Sequence
Verify Data? Sector erase is a six bus cycle operation. The sector
No
erase command sequence is initiated by writing two
unlock cycles, followed by a set-up command. Two
Yes additional unlock write cycles are then followed by the
address of the sector to be erased, and the sector
No erase command. Table 5 shows the address and data
Increment Address Last Address? requirements for the sector erase command sequence.
The device does not require the system to preprogram
Yes the memory prior to erase. The Embedded Erase algo-
rithm automatically programs and verifies the sector for
Programming an all zero data pattern prior to electrical erase. The
Completed system is not required to provide any controls or
timings during these operations.
After the command sequence is written, a sector erase
Note:
See Table 5 for program command sequence. time-out of 50 µs begins. During the time-out period,
additional sector addresses and sector erase com-
Figure 2. Program Operation mands may be written. Loading the sector erase buffer
may be done in any sequence, and the number of
sectors may be from one sector to all sectors. The time
between these additional cycles must be less than 50
µs, otherwise the last address and command might not Once the sector erase operation has begun, only the
be accepted, and erasure may begin. It is recom- Erase Suspend command is valid. All other commands
mended that processor interrupts be disabled during are ignored. Note that a hardware reset during the
this time to ensure all commands are accepted. The sector erase operation immediately terminates the
interrupts can be re-enabled after the last Sector Erase operation. The Sector Erase command sequence
command is written. If the time between additional should be reinitiated once the device has returned to
sector erase commands can be assumed to be less reading array data, to ensure data integrity.
than 50 µs, the system need not monitor DQ3. Any
When the Embedded Erase algorithm is complete, the
command other than Sector Erase or Erase
device returns to reading array data and addresses are
Suspend during the time-out period resets the
no longer latched. The system can determine the
device to reading array data. The system must
status of the erase operation by using DQ7, DQ6, DQ2,
rewrite the command sequence and any additional
or RY/BY#. (Refer to “The Erase Resume command is
sector addresses and commands.
valid only during the Erase Suspend mode.” for infor-
The system can monitor DQ3 to determine if the sector mation on these status bits.)
erase timer has timed out. (See the “DQ3: Sector Erase
Figure 3 illustrates the algorithm for the erase opera-
Timer” section.) The time-out begins from the rising
tion. Refer to the “Erase/Program Operations” tables in
edge of the final WE# pulse in the command sequence.
the “AC Characteristics” section for parameters, and to
Figure 14 for timing diagrams.
Erase Suspend/Erase Resume Commands even at addresses within erasing sectors, since the
codes are not stored in the memory array. When the
The Erase Suspend command allows the system to
device exits the autoselect mode, the device reverts to
interrupt a sector erase operation and then read data
the Erase Suspend mode, and is ready for another
from, or program data to, any sector not selected for
valid operation. See “Autoselect Command Sequence”
erasure. This command is valid only during the sector
for more information.
erase operation, including the 50 µs time-out period
during the sector erase command sequence. The The system must write the Erase Resume command
Erase Suspend command is ignored if written during (address bits are “don’t care”) to exit the erase suspend
the chip erase operation or Embedded Program algo- mode and continue the sector erase operation. Further
rithm. Writing the Erase Suspend command during the writes of the Resume command are ignored. Another
Sector Erase time-out immediately terminates the Erase Suspend command can be written after the
time-out period and suspends the erase operation. device has resumed erasing.
Addresses are “don’t-cares” when writing the Erase
Suspend command.
When the Erase Suspend command is written during a START
sector erase operation, the device requires a maximum
of 20 µs to suspend the erase operation. However,
when the Erase Suspend command is written during
the sector erase time-out, the device immediately ter- Write Erase
minates the time-out period and suspends the erase Command Sequence
operation.
After the erase operation has been suspended, the
system can read array data from or program data to Data Poll
any sector not selected for erasure. (The device “erase from System
suspends” all sectors selected for erasure.) Normal Embedded
read and write timings and command definitions apply. Erase
Reading at any address within erase-suspended algorithm
sectors produces status data on DQ7–DQ0. The in progress
No
system can use DQ7, or DQ6 and DQ2 together, to Data = FFh?
determine if a sector is actively erasing or is erase-sus-
pended. See “The Erase Resume command is valid
only during the Erase Suspend mode.” for information Yes
on these status bits.
After an erase-suspended program operation is com- Erasure Completed
plete, the system can once again read array data within
non-suspended sectors. The system can determine
the status of the program operation using the DQ7 or
DQ6 status bits, just as in the standard program oper-
Notes:
ation. See “The Erase Resume command is valid only
1. See Table 5 for erase command sequence.
during the Erase Suspend mode.” for more information.
2. See “DQ3: Sector Erase Timer” for more information.
The system may also write the autoselect command
sequence when the device is in the Erase Suspend Figure 3. Erase Operation
mode. The device allows reading autoselect codes
Cycles
Command
Sequence First Second Third Fourth Fifth Sixth
(Note 1) Addr Data Addr Data Addr Data Addr Data Addr Data Addr Data
Read (Note 6) 1 RA RD
Reset (Note 7) 1 XXX F0
Word 555 2AA 555
Manufacturer ID 4 AA 55 90 X00 01
Byte AAA 555 AAA
Autoselect (Note 8)
Legend:
X = Don’t care PD = Data to be programmed at location PA. Data latches on the
RA = Address of the memory location to be read. rising edge of WE# or CE# pulse, whichever happens first.
RD = Data read from location RA during read operation. SA = Address of the sector to be verified (in autoselect mode) or
erased. Address bits A17–A12 uniquely select any sector.
PA = Address of the memory location to be programmed.
Addresses latch on the falling edge of the WE# or CE# pulse,
whichever happens later.
Notes:
1. See Table 1 for description of bus operations. 8. The fourth cycle of the autoselect command sequence is a
2. All values are in hexadecimal. read cycle.
3. Except when reading array or autoselect data, all bus cycles 9. The data is 00h for an unprotected sector and 01h for a
are write operations. protected sector. See“Autoselect Command Sequence” for
more information.
4. Data bits DQ15–DQ8 are don’t cares for unlock and
command cycles. 10. The system may read and program in non-erasing sectors, or
enter the autoselect mode, when in the Erase Suspend
5. Address bits A17–A11 are don’t cares for unlock and mode. The Erase Suspend command is valid only during a
command cycles, unless PA or SA required. sector erase operation.
6. No unlock or command cycles required when reading array 11. The Erase Resume command is valid only during the Erase
data. Suspend mode.
7. The Reset command is required to return to reading array
data when device is in the autoselect mode, or if DQ5 goes
high (while the device is providing status data).
RY/BY#: Ready/Busy# Table 6 shows the outputs for Toggle Bit I on DQ6.
Figure 5 shows the toggle bit algorithm. Figure 16 in the
The RY/BY# is a dedicated, open-drain output pin that
“AC Characteristics” section shows the toggle bit timing
indicates whether an Embedded Algorithm is in
diagrams. Figure 17 shows the differences between
progress or complete. The RY/BY# status is valid after
DQ2 and DQ6 in graphical form. See also the subsec-
the rising edge of the final WE# pulse in the command
tion on “DQ2: Toggle Bit II”.
sequence. Since RY/BY# is an open-drain output,
several RY/BY# pins can be tied together in parallel
DQ2: Toggle Bit II
with a pull-up resistor to VCC.
The “Toggle Bit II” on DQ2, when used with DQ6, indi-
If the output is low (Busy), the device is actively erasing cates whether a particular sector is actively erasing
or programming. (This includes programming in the (that is, the Embedded Erase algorithm is in progress),
Erase Suspend mode.) If the output is high (Ready), or whether that sector is erase-suspended. Toggle Bit
the device is ready to read array data (including during II is valid after the rising edge of the final WE# pulse in
the Erase Suspend mode), or is in the standby mode. the command sequence.
Table 6 shows the outputs for RY/BY#. Figures 10, DQ2 toggles when the system reads at addresses
Figure 13 and Figure 14 shows RY/BY# for reset, pro- within those sectors that have been selected for era-
gram, and erase operations, respectively. sure. (The system may use either OE# or CE# to
control the read cycles.) But DQ2 cannot distinguish
DQ6: Toggle Bit I whether the sector is actively erasing or is erase-sus-
Toggle Bit I on DQ6 indicates whether an Embedded pended. DQ6, by comparison, indicates whether the
Program or Erase algorithm is in progress or complete, device is actively erasing, or is in Erase Suspend, but
or whether the device has entered the Erase Suspend cannot distinguish which sectors are selected for era-
mode. Toggle Bit I may be read at any address, and is sure. Thus, both status bits are required for sector and
valid after the rising edge of the final WE# pulse in the mode information. Refer to Table 6 to compare outputs
command sequence (prior to the program or erase for DQ2 and DQ6.
operation), and during the sector erase time-out.
Figure 5 shows the toggle bit algorithm in flowchart
During an Embedded Program or Erase algorithm form, and the section “DQ2: Toggle Bit II” explains the
operation, successive read cycles to any address algorithm. See also the “DQ6: Toggle Bit I” subsection.
cause DQ6 to toggle. The system may use either OE# Figure 16 shows the toggle bit timing diagram. Figure
or CE# to control the read cycles. When the operation 17 shows the differences between DQ2 and DQ6 in
is complete, DQ6 stops toggling. graphical form.
After an erase command sequence is written, if all
Reading Toggle Bits DQ6/DQ2
sectors selected for erasing are protected, DQ6 toggles
for approximately 100 µs, then returns to reading array Refer to Figure 5 for the following discussion. When-
data. If not all selected sectors are protected, the ever the system initially begins reading toggle bit
Embedded Erase algorithm erases the unprotected status, it must read DQ7–DQ0 at least twice in a row to
sectors, and ignores the selected sectors that are determine whether a toggle bit is toggling. Typically, the
protected. system would note and store the value of the toggle bit
after the first read. After the second read, the system
The system can use DQ6 and DQ2 together to deter- would compare the new value of the toggle bit with the
mine whether a sector is actively erasing or is erase- first. If the toggle bit is not toggling, the device has com-
suspended. When the device is actively erasing (that is, pleted the program or erase operation. The system can
the Embedded Erase algorithm is in progress), DQ6 read array data on DQ7–DQ0 on the following read
toggles. When the device enters the Erase Suspend cycle.
mode, DQ6 stops toggling. However, the system must
also use DQ2 to determine which sectors are erasing However, if after the initial two read cycles, the system
or erase-suspended. Alternatively, the system can use determines that the toggle bit is still toggling, the
DQ7 (see the subsection on “DQ7: Data# Polling”). system also should note whether the value of DQ5 is
high (see the section on DQ5). If it is, the system
If a program address falls within a protected sector, should then determine again whether the toggle bit is
DQ6 toggles for approximately 2 µs after the program toggling, since the toggle bit may have stopped tog-
command sequence is written, then returns to reading gling just as DQ5 went high. If the toggle bit is no longer
array data. toggling, the device has successfully completed the
DQ6 also toggles during the erase-suspend-program program or erase operation. If it is still toggling, the
mode, and stops toggling once the Embedded device did not complete the operation successfully, and
Program algorithm is complete. the system must write the reset command to return to
reading array data.
OPERATING RANGES
Commercial (C) Devices
Ambient Temperature (TA) . . . . . . . . . . . 0°C to +70°C
Industrial (I) Devices
Ambient Temperature (TA) . . . . . . . . . –40°C to +85°C
Extended (E) Devices
Ambient Temperature (TA) . . . . . . . . –55°C to +125°C
VCC Supply Voltages
VCC for ± 5% devices . . . . . . . . . . .+4.75 V to +5.25 V
VCC for ± 10% devices . . . . . . . . . . . .+4.5 V to +5.5 V
Note:Operating ranges define those limits between which the
functionality of the device is guaranteed.
DC CHARACTERISTICS
TTL/NMOS Compatible
Parameter Description Test Conditions Min Typ Max Unit
ILI Input Load Current VIN = VSS to VCC, VCC = VCC max ±1.0 µA
A9, OE#, RESET# Input Load VCC = VCC max;
ILIT 50 µA
Current A9, OE#, RESET# = 12.5 V
ILO Output Leakage Current VOUT = VSS to VCC, VCC = VCC max ±1.0 µA
VCC
VIH Input High Voltage 2.0 V
+0.5
VOH Output High Voltage IOH = –2.5 mA, VCC = VCC min 2.4 V
Notes:
1. The ICC current listed is typically less than 2 mA/MHz, with OE# at VIH..
2. Maximum ICC specifications are tested with VCC = VCCmax.
3. ICC active while Embedded Erase or Embedded Program is in progress.
4. Not 100% tested.
DC CHARACTERISTICS
CMOS Compatible
Parameter Description Test Conditions Min Typ Max Unit
0.7 x VCC+
VIH Input High Voltage V
VCC 0.3
Notes:
1. The ICC current listed is typically less than 2 mA/MHz, with OE# at VIH.
2. Maximum ICC specifications are tested with VCC = VCCmax.
3. ICC active while Embedded Erase or Embedded Program is in progress.
4. Not 100% tested.
5. ICC3 = 20 µA max at extended temperature (>+85° C).
TEST CONDITIONS
Table 7. Test Specifications
5.0 V
-45, All
Test Condition -50, -55 others Unit
2.7 kΩ
Device Output Load 1 TTL gate
Under
Test Output Load Capacitance, CL
30 100 pF
(including jig capacitance)
CL 6.2 kΩ
Input Rise and Fall Times 5 20 ns
Steady
Changing from H to L
Changing from L to H
AC CHARACTERISTICS
Read Operations
Parameter Speed Options
JEDEC Std Description Test Setup -45 -50 -55 -70 -90 -120 Unit
CE# = VIL
tAVQV tACC Address to Output Delay Max 45 50 55 70 90 120 ns
OE# = VIL
tELQV tCE Chip Enable to Output Delay OE# = VIL Max 45 50 55 70 90 120 ns
Notes:
1. Not 100% tested.
2. See Figure 8 and Table 7 for test specifications.
tRC
tDF
tOE
OE#
tOEH
WE# tCE
tOH
HIGH Z HIGH Z
Outputs Output Valid
RESET#
RY/BY#
0V
AC CHARACTERISTICS
Hardware Reset (RESET#)
Parameter
Note:
Not 100% tested.
RY/BY#
CE#, OE#
tRH
RESET#
tRP
tReady
tReady
RY/BY#
tRB
CE#, OE#
RESET#
tRP
AC CHARACTERISTICS
Word/Byte Configuration (BYTE#)
Parameter Speed Options
JEDEC Std Description -45 -50 -55 -70 -90 -120 Unit
CE#
OE#
BYTE#
tELFL
BYTE# DQ0–DQ14 Data Output Data Output
Switching (DQ0–DQ14) (DQ0–DQ7)
from word
to byte
mode DQ15/A-1 DQ15 Address
Output Input
tFLQZ
tELFH
BYTE#
BYTE#
Switching
from byte DQ0–DQ14 Data Output Data Output
to word (DQ0–DQ7) (DQ0–DQ14)
mode
DQ15/A-1 Address DQ15
Input Output
tFHQV
CE#
BYTE#
tSET
(tAS)
tHOLD (tAH)
Note:
Refer to the Erase/Program Operations table for tAS and tAH specifications.
Figure 12. BYTE# Timings for Write Operations
AC CHARACTERISTICS
Erase/Program Operations
Parameter Speed Options
JEDEC Std Description -45 -50 -55 -70 -90 -120 Unit
Notes:
1. Not 100% tested.
2. See the “Erase and Programming Performance” section for more information.
AC CHARACTERISTICS
Program Command Sequence (last two cycles) Read Status Data (last two cycles)
tWC tAS
Addresses 555h PA PA PA
tAH
CE#
tCH
OE#
tWP tWHWH1
WE#
tWPH
tCS
tDS
tDH
tBUSY tRB
RY/BY#
tVCS
VCC
Notes:
1. PA = program address, PD = program data, DOUT is the true data at the program address.
2. Illustration shows device in word mode.
Figure 13. Program Operation Timings
AC CHARACTERISTICS
OE# tCH
tWP
WE#
tWPH tWHWH2
tCS
tDS
tDH
In
Data 55h 30h Progress Complete
tBUSY tRB
RY/BY#
tVCS
VCC
Notes:
1. SA = sector address (for Sector Erase), VA = Valid Address for reading status data (see “Write Operation Status”).
2. Illustration shows device in word mode.
AC CHARACTERISTICS
tRC
Addresses VA VA VA
tACC
tCE
CE#
tCH
tOE
OE#
tOEH tDF
WE#
tOH
High Z
DQ7 Complement Complement True Valid Data
High Z
DQ0–DQ6 Status Data Status Data True Valid Data
tBUSY
RY/BY#
Note:
VA = Valid address. Illustration shows first status cycle after command sequence, last status read cycle, and array data read cycle.
tRC
Addresses VA VA VA VA
tACC
tCE
CE#
tCH
tOE
OE#
tOEH tDF
WE#
tOH
High Z
DQ6/DQ2 Valid Status Valid Status Valid Status Valid Data
(first read) (second read) (stops toggling)
tBUSY
RY/BY#
Note:
VA = Valid address; not required for DQ6. Illustration shows first two status cycle after command sequence, last status read cycle,
and array data read cycle.
Figure 16. Toggle Bit Timings (During Embedded Algorithms)
AC CHARACTERISTICS
Enter
Embedded Erase Enter Erase Erase
Erasing Suspend Suspend Program Resume
WE# Erase Erase Suspend Erase Erase Suspend Erase Erase
Read Suspend Read Complete
Program
DQ6
DQ2
Note:
The system may use either CE# or OE# to toggle DQ2 and DQ6. DQ2 toggles only when read at an address within an
erase-suspended sector.
Figure 17. DQ2 vs. DQ6
tVIDR VID Rise and Fall Time (See Note) Min 500 ns
12 V
RESET#
0 or 5 V 0 or 5 V
tVIDR tVIDR
Program or Erase Command Sequence
CE#
WE#
tRSP
RY/BY#
AC CHARACTERISTICS
Alternate CE# Controlled Erase/Program Operations
Parameter Speed Options
JEDEC Std Description -45 -50 -55 -70 -90 -120 Unit
Notes:
1. Not 100% tested.
2. See the “Erase and Programming Performance” section for more information.
AC CHARACTERISTICS
555 for program PA for program
2AA for erase SA for sector erase
555 for chip erase
Data# Polling
Addresses PA
tWC tAS
tAH
tWH
WE#
tGHEL
OE#
tCP tWHWH1 or 2
CE#
tWS tCPH
tBUSY
tDS
tDH
DQ7# DOUT
Data
tRH A0 for program PD for program
55 for erase 30 for sector erase
10 for chip erase
RESET#
RY/BY#
Notes:
1. PA = Program Address, PD = Program Data, SA = Sector Address, DQ7# = Complement of Data Input, DOUT = Array Data.
2. Figure indicates the last two bus cycles of the command sequence, with the device in word mode.
Figure 19. Alternate CE# Controlled Write Operation Timings
Notes:
1. Typical program and erase times assume the following conditions: 25°C, 5.0 V VCC, 1,000,000 cycles. Additionally,
programming typicals assume checkerboard pattern.
2. Under worst case conditions of 90°C, VCC = 4.5 V, 1,000,000 cycles.
3. The typical chip programming time is considerably less than the maximum chip programming time listed, since most bytes
program faster than the maximum program times listed.
4. In the pre-programming step of the Embedded Erase algorithm, all bytes are programmed to 00h before erasure.
5. System-level overhead is the time required to execute the four-bus-cycle sequence for the program command. See Table 5
for further information on command definitions.
6. The device has a guaranteed minimum erase and program cycle endurance of 1,000,000 cycles.
LATCHUP CHARACTERISTICS
Description Min Max
Input voltage with respect to VSS on all pins except I/O pins
–1.0 V 12.5 V
(including A9, OE#, and RESET#)
Input voltage with respect to VSS on all I/O pins –1.0 V VCC + 1.0 V
Includes all pins except VCC. Test conditions: VCC = 5.0 V, one pin at a time.
Notes:
1. Sampled, not 100% tested.
2. Test conditions TA = 25°C, f = 1.0 MHz.
DATA RETENTION
Parameter Test Conditions Min Unit
150°C 10 Years
Minimum Pattern Data Retention Time
125°C 20 Years
PHYSICAL DIMENSIONS
TS 048—48-Pin Standard Thin Small Outline Package
PHYSICAL DIMENSIONS
SO 044—44-Pin Small Outline Package
REVISION SUMMARY
Colophon
The products described in this document are designed, developed and manufactured as contemplated for general use, including without limita-
tion, ordinary industrial use, general office use, personal use, and household use, but are not designed, developed and manufactured as con-
templated (1) for any use that includes fatal risks or dangers that, unless extremely high safety is secured, could have a serious effect to the
public, and could lead directly to death, personal injury, severe physical damage or other loss (i.e., nuclear reaction control in nuclear facility,
aircraft flight control, air traffic control, mass transport control, medical life support system, missile launch control in weapon system), or (2) for
any use where chance of failure is intolerable (i.e., submersible repeater and artificial satellite). Please note that Spansion Inc. will not be liable
to you and/or any third party for any claims or damages arising in connection with above-mentioned uses of the products. Any semiconductor
devices have an inherent chance of failure. You must protect against injury, damage or loss from such failures by incorporating safety design
measures into your facility and equipment such as redundancy, fire protection, and prevention of over-current levels and other abnormal operating
conditions. If any products described in this document represent goods or technologies subject to certain restrictions on export under the Foreign
Exchange and Foreign Trade Law of Japan, the US Export Administration Regulations or the applicable laws of any other country, the prior au-
thorization by the respective government entity will be required for export of those products.
Trademarks
Copyright © 2006 Spansion Inc. All Rights Reserved. Spansion, the Spansion logo, MirrorBit, ORNAND, HD-SIM, and combinations thereof are
trademarks of Spansion Inc. Other names are for informational purposes only and may be trademarks of their respective owners.
Copyright © 2004–2006 Advanced Micro Devices, Inc. All rights reserved. AMD, the AMD logo, and combinations thereof are registered trade-
marks of Advanced Micro Devices, Inc. ExpressFlash™ is a trademark of Advanced Micro Devices, Inc. Product names used in this publication
are for identification purposes only and may be trademarks of their respective companies.