This product has been retired and is not recommended for designs. For new and current designs,
S29GL256N supersedes Am29LV128MH/L and is the factory-recommended migration path. Please
refer to the S29GL256N datasheet for specifications and ordering information. Availability of this
document is retained for reference and historical purposes only.
The following document contains information on Spansion memory products.
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.
For More Information
Please contact your local sales office for additional information about Spansion memory solutions.
Publication Number 25270 Revision C Amendment 7 Issue Date January 31, 2007
Page 2
THIS PAGE LEFT INTENTIONALLY BLANK.
Page 3
DATA SHEET
Am29LV128MH/L
128 Megabit (8 M x 16-Bit/16 M x 8-Bit) MirrorBit™ 3.0 Volt-only
Uniform Sector Flash Memory with VersatileI/O™ Control
This product has been retired and is not recommended for designs. For new and current designs, S29GL256N supersedes Am29LV128MH/L and is the factory-recommended migration path. Please refer to the S29GL256N datasheet for specifications and ordering information. Availability of this document is retained for reference and historical purposes only
DISTINCTIVE CHARACTERISTICS
..
ARCHITECTURAL ADVANTAGES
Single power supply operation
— 3 volt read, erase, and program operations
VersatileI/O™ control
— Device generates data output voltages and tolerates
data input voltages on the CE# and DQ
inputs/outputs as determined by the voltage on the
pin; operates from 1.65 to 3.6 V
V
IO
Manufactured on 0.23 µm MirrorBit process
technology
Secured Silicon Sector region
— 128-word/256-byte sector for permanent, secure
identification through an 8-word/16-byte random
Electronic Serial Number, accessible through a
command sequence
— May be programmed and locked at the factory or by
the customer
Flexible sector architecture
— Two hundred fifty-six 32 Kword (64 Kbyte) sectors
Compatibility with JEDEC standards
— Provides pinout and software compatibility for
single-power supply flash, and superior inadvertent
write protection
Minimum 100,000 erase cycle guarantee per sector
20-year data retention at 125°C
PERFORMANCE CHARACTERISTICS
High performance
— 90 ns access time
— 25 ns page read times
— 0.5 s typical sector erase time
— 15 s typical effective write buffer word programming
programming time for multiple-word updates
— 4-word/8-byte page read buffer
— 16-word/32-byte write buffer
Low power consumption (typical values at 3.0 V, 5
MHz)
— 13 mA typical active read current
— 50 mA typical erase/program current
— 1 µA typical standby mode current
Package options
— 56-pin TSOP
— 64-ball Fortified BGA
SOFTWARE & HARDWARE FEATURES
Software features
— Program Suspend & Resume: read other sectors
before programming operation is completed
— Erase Suspend & Resume: read/program other
sectors before an erase operation is completed
— Data# polling & toggle bits provide status
— Unlock Bypass Program command reduces overall
multiple-word or byte programming time
— CFI (Common Flash Interface) compliant: allows host
system to identify and accommodate multiple flash
devices
Hardware features
— Sector Group Protection: hardware-level method of
preventing write operations within a sector group
— Temporary Sector Group Unprotect: V
of changing code in locked sector groups
— WP#/ACC input accelerates programming time
(when high voltage is applied) for greater throughput
during system production. Protects first or last sector
regardless of sector protection settings
— Hardware reset input (RESET#) resets device
— Ready/Busy# output (RY/BY#) detects program or
erase cycle completion
-level method
ID
This Data Sheet states AMD’s current specifications regarding the Products described herein. This Data Sheet may
be revised by subsequent versions or modifications due to changes in technical specifications.
Publication# 25270 Rev: C Amendment: 7
Issue Date: January 31, 2007
Page 4
DATA SHEET
GENERAL DESCRIPTION
The Am29LV128MH/L is a 128 Mbit, 3.0 volt single
power supply flash memory devices organized as
8,388,608 words or 16,777,216 bytes. The device has
a 16-bit wide data bus that can also function as an
8-bit wide data bus by using the BYTE# input. The device can be programmed either in the host system or
in standard EPROM programmers.
An access time of 90, 100, 110, or 120 ns is available.
Note that each access time has a specific operating
voltage range (V
specified in “Product Selector Guide” on page 6 and
the “Ordering Information” on page 10. The device is
offered in a 56-pin TSOP, 64-ball Fortified BGA. Each
device has separate chip enable (CE#), write enable
(WE#) and output enable (OE#) controls.
Each device requires only a single 3.0 volt powersupply for both read and write functions. In addition to
a V
input, a high-voltage accelerated program
CC
(WP#/ACC) input provides shorter programming times
through increased current. This feature is intended to
facilitate factory throughput during system production,
but may also be used in the field if desired.
The device is entirely command set compatible with
the JEDEC single-power-supply Flash standard.
Commands are written to the device using standard
microprocessor write timing. Write cycles also internally latch addresses and data needed for the programming and erase operations.
) and an I/O voltage range (VIO), as
CC
of memory. This can be achieved in-system or via programming equipment.
The Erase Suspend/Erase Resume feature allows
the host system to pause an erase operation in a given
sector to read or program any other sector and then
complete the erase operation. The Program Sus-pend/Program Resume feature enables the host system to pause a program operation in a given sector to
read any other sector and then complete the program
operation.
The hardware RESET# pin terminates any operation
in progress and resets the device, after which it is then
ready for a new operation. The RESET# pin may be
tied to the system reset circuitry. A system reset would
thus also reset the device, enabling the host system to
read boot-up firmware from the Flash memory device.
The device reduces power consumption in the
standby mode when it detects specific voltage levels
on CE# and RESET#, or when addresses have been
stable for a specified period of time.
The Secured Silicon Sector provides a
128-word/256-byte area for code or data that can be
permanently protected. Once this sector is protected,
no further changes within the sector can occur.
The Write Protect (WP#/ACC) feature protects the
first or last sector by asserting a logic low on the WP#
pin.
The sector erase architecture allows memory sectors to be erased and reprogrammed without affecting
the data contents of other sectors. The device is fully
erased when shipped from the factory.
Device programming and erasure are initiated through
command sequences. Once a program or erase operation has begun, the host system need only poll the
DQ7 (Data# Polling) or DQ6 (toggle) status bits or
monitor the Ready/Busy# (RY/BY#) output to determine whether the operation is complete. To facilitate
programming, an Unlock Bypass mode reduces command sequence overhead by requiring only two write
cycles to program data instead of four.
The VersatileI/O™ (V
) control allows the host sys-
IO
tem to set the voltage levels that the device generates
and tolerates on the CE# control input and DQ I/Os to
the same voltage level that is asserted on the V
IO
pin.
Refer to the Ordering Information section for valid V
options.
Hardware data protection measures include a low
V
detector that automatically inhibits write opera-
CC
tions during power transitions. The hardware sector
group protection feature disables both program and
erase operations in any combination of sector groups
AMD MirrorBit flash technology combines years of
Flash memory manufacturing experience to produce
the highest levels of quality, reliability and cost effectiveness. The device electrically erases all bits within a
sector simultaneously via hot-hole assisted erase. The
data is programmed using hot electron injection.
RELATED DOCUMENTS
For a comprehensive information on MirrorBit products, including migration information, data sheets, application notes, and software drivers, please see
www.amd.com
tion
→MirrorBit→Flash Information→Technical Docu-
mentation. The following is a partial list of documents
closely related to this product:
MirrorBit™ Flash Memory Write Buffer Programming
and Page Buffer Read
IO
Implementing a Common Layout for AMD MirrorBit
and Intel StrataFlash Memory Devices
Migrating from Single-byte to Three-byte Device IDs
Am29LV256M, 256 Mbit MirrorBit Flash device
(in 64-ball, 18 x 12 mm Fortified BGA package)
→Flash Memory→Product Informa-
4Am29LV128MH/L25270C7 January 31, 2007
Page 5
DATA SHEET
TABLE OF CONTENTS
Continuity of Specifications ............................................................. i
For More Information ....................................................................... i
150°C for prolonged periods of time.
Special handling is required for Flash Memory products
in molded packages (TSOP and BGA). The package
and/or data integrity may be compromised if the
8Am29LV128MH/L25270C7 January 31, 2007
Page 9
DATA SHEET
PIN DESCRIPTION
A22–A0= 23 Address inputs
DQ14–DQ0 = 15 Data inputs/outputs
DQ15/A-1= DQ15 (Data input/output, word mode),
A-1 (LSB Address input, byte mode)
CE#= Chip Enable input
OE#= Output Enable input
WE#= Write Enable input
WP#/ACC= Hardware Write Protect input;
Acceleration input
RESET#= Hardware Reset Pin input
BYTE#= Selects 8-bit or 16-bit mode
RY/BY#= Ready/Busy output
V
= 3.0 volt-only single power supply
CC
V
= Output Buffer power
IO
V
SS
NC= Pin Not Connected Internally
(see Product Selector Guide for
speed options and voltage
supply tolerances)
= Device Ground
LOGIC SYMBOL
23
A22–A0
CE#
OE#
WE#
WP#/ACC
RESET#
V
IO
BYTE#
16 or 8
DQ15–DQ0
(A-1)
RY/BY#
January 31, 2007 25270C7Am29LV128MH/L9
Page 10
DATA SHEET
ORDERING INFORMATION
Standard Products
AMD standard products are available in several packages and operating ranges. The order number (Valid Combination) is
formed by a combination of the following:
Am29LV128MH/LH123RPCI
TEMPERATURE RANGE
F= Industrial (-40C to 85C) with Pb-free Package
I = Industrial (–40
PACKAGE TYPE
E= 56-Pin Thin Small Outline Package (TSOP) Standard Pinout (TS 056)
F= 56-Pin Thin Small Outline Package (TSOP) Reverse Pinout (TSR056)
PC = 64-Ball Fortified Ball Grid Array (
1.0 mm pitch, 13 x 11 mm package (LAA064)
SPEED OPTION
See Product Selector Guide and Valid Combinations
°C to +85°C)
FBGA),
SECTOR ARCHITECTURE AND SECTOR WRITE PROTECTION (WP# = V
Am29LV128MH/L
128 Megabit (8 M x 16-Bit/16 M x 8-Bit) MirrorBit Uniform Sector Flash Memory with VersatileIO™ Control,
3.0 Volt-only Read, Program, and Erase
Valid Combinations for
TSOP Package
Am29LV128MH93R
Am29LV128ML93R
Am29LV128MH103R
Am29LV128ML103R
Am29LV128MH113R
Am29LV128ML113R
Am29LV128MH123R
Am29LV128ML123R
Speed
(ns)
903.0–3.6 V
1002.7–3.6 V
EI,
FI
EF
1101.65–3.6 V
1201.65–3.6 V
V
IO
Range
V
CC
Range
3.0–3.6 V
Valid Combinations for
Fortified BGA Package
Order NumberPackage Marking
Am29LV128MH93R
Am29LV128ML93R
Am29LV128MH103R
Am29LV128ML103R
Am29LV128MH113R
Am29LV128ML113R
Am29LV128MH123R
Am29LV128ML123R
PCI,
PCF
L128MH93N
L128ML93N
L128MH103N
L128ML103N
L128MH113N
L128ML113N
L128MH123N
L128ML123N
I,
F
Speed
(ns)
90
100
110
120
V
IO
Range
3.0–
3.6V
2.7–
3.6 V
1.65–
3.6 V
1.65–
3.6 V
V
CC
Range
3.0–
3.6 V
Valid Combinations
Valid Combinations list configurations planned to be supported in volume for this device. Consult the local AMD sales office to confirm
availability of specific valid combinations and to check on newly released combinations.
Notes:
1. For 100, 110, and 120 speed option shown in product selector guide, contact AMD for availability and ordering information.
2. To select product with ESN factory-locked into the Secured Silicon Sector: 1) select order number from the valid combinations given above, 2) add designator
“N” at the end of the order number, and 3) modify the speed option indicator as follows [103R = 10R, 113R = 11R, 123R = 12R, 93R, 103, 113, 123 = no
change]. Example: Am29LV128MH12RPCIN. For Fortified BGA packages, modify the speed option indicator as follows: [103N = 10N, 113N = 11N, 123N =
12N, 93N = no change]. The designator “N” will also appear at the end of the package marking. Example: L128MH12NIN.
)
10Am29LV128MH/L25270C7 January 31, 2007
Page 11
DATA SHEET
DEVICE BUS OPERATIONS
This section describes the requirements and use of
the device bus operations, which are initiated through
the internal command register. The command register
itself does not occupy any addressable memory location. The register is a latch used to store the commands, along with the address and data information
needed to execute the command. The contents of the
Table 1. Device Bus Operations
register serve as inputs to the internal state machine.
The state machine outputs dictate the function of the
device. Ta bl e 1 lists the device bus operations, the in-
puts and control levels they require, and the resulting
output. The following subsections describe each of
these operations in further detail.
DQ8–DQ15
OperationCE#OE# WE# RESET#WP#ACC
ReadLLHH
Write (Program/Erase)LHLH
Accelerated ProgramLHLH
±
V
Standby
Output DisableLHHH
ResetXXXL
Sector Group Protect
(Note 2)
Sector Group Unprotect
(Note 2)
Temporary Sector Group
Unprotect
CC
0.3 V
XX
LHL V
LHL V
XXX V
VCC ±
0.3 V
(Note 3)L/H
(Note 3)V
ID
ID
ID
DQ0–
DQ7
D
(Note 4) (Note 4)
(Note 4) (Note 4)
XL/H
HH
Addresses
(Note 2)
A
IN
A
IN
A
IN
XHXHigh-ZHigh-ZHigh-Z
XL/HXHigh-ZHigh-ZHigh-Z
XL/HXHigh-ZHigh-ZHigh-Z
SA, A6 =L,
HL/H
HL/H
HL/H
A3=L, A2=L,
A1=H, A0=L
SA, A6=H,
A3=L, A2=L,
A1=H, A0=L
A
IN
(Note 4)XX
(Note 4)XX
(Note 4) (Note 4)High-Z
OUT
BYTE#
= V
IH
D
OUT
BYTE#
= V
IL
DQ8–DQ14
= High-Z,
DQ15 = A-1
Legend: L = Logic Low = VIL, H = Logic High = VIH, VID = 11.5–12.5V, VHH = 11.5–12.5V, X = Don’t Care, SA = Sector Address,
= Address In, DIN = Data In, D
A
IN
= Data Out
OUT
Notes:
1. Addresses are A22:A0 in word mode; A22:A-1 in byte mode. Sector addresses are A22:A15 in both modes.
2. The sector group protect and sector group unprotect functions may also be implemented via programming equipment. See the
“Sector Group Protection and Unprotection” section.
3. If WP# = V
, the first or last sector remains protected. If WP# = VIH, the first or last sector will be protected or unprotected as
IL
determined by the method described in “Write Protect (WP#)”. All sectors are unprotected when shipped from the factory (The
Secured Silicon Sector may be factory protected depending on version ordered.)
4. D
IN
or D
as required by command sequence, data polling, or sector protect algorithm (see Figure 2).
OUT
Word/Byte Configuration
The BYTE# pin controls whether the device data I/O
pins operate in the byte or word configuration. If the
BYTE# pin is set at logic ‘1’, the device is in word configuration, DQ0–DQ15 are active and controlled by
CE# and OE#.
pins DQ8–DQ14 are tri-stated, and the DQ15 pin is
used as an input for the LSB (A-1) address function.
VersatileIO™ (VIO) Control
The VersatileIO™ (VIO) control allows the host system
to set the voltage levels that the device generates and
tolerates on CE# and DQ I/Os to the same voltage
If the BYTE# pin is set at logic ‘0’, the device is in byte
configuration, and only data I/O pins DQ0–DQ7 are
active and controlled by CE# and OE#. The data I/O
level that is asserted on V
tion” for V
options on this device.
IO
. See “Ordering Informa-
IO
January 31, 2007 25270C7Am29LV128MH/L11
Page 12
DATA SHEET
Requirements for Reading Array Data
To read array data from the outputs, the system must
drive the CE# and OE# pins to V
. CE# is the power
IL
control and selects the device. OE# is the output control and gates array data to the output pins. WE#
should remain at V
.
IH
The internal state machine is set for reading array data
upon device power-up, or after a hardware reset. This
ensures that no spurious alteration of the memory
content occurs during the power transition. No command is necessary in this mode to obtain array data.
Standard microprocessor read cycles that assert valid
addresses on the device address inputs produce valid
data on the device data outputs. The device remains
enabled for read access until the command register
contents are altered.
See “Reading Array Data” for more information. See
the table, See “Read-Only Operations” on page 47 for
timing specifications and Figure 14 for the timing diagram. See the table in “DC Characteristics” on
page 45 for the active current specification on reading
array data.
Page Mode Read
The device is capable of fast page mode read and is
compatible with the page mode Mask ROM read operation. This mode provides faster read access speed
for random locations within a page. The page size of
the device is 4 words/8 bytes. The appropriate page is
selected by the higher address bits A(max)–A2. Address bits A1–A0 in word mode (A1–A-1 in byte mode)
determine the specific word within a page. This is an
asynchronous operation; the microprocessor supplies
the specific word location.
The random or initial page access is equal to t
t
and subsequent page read accesses (as long as
CE
ACC
or
the locations specified by the microprocessor falls
within that page) is equivalent to t
. When CE# is
PAC C
deasserted and reasserted for a subsequent access,
the access time is t
or tCE. Fast page mode ac-
ACC
cesses are obtained by keeping the “read-page addresses” constant and changing the “intra-read page”
addresses.
Writing Commands/Command Sequences
To write a command or command sequence (which includes programming data to the device and erasing
sectors of memory), the system must drive WE# and
CE# to V
The device features an Unlock Bypass mode to facilitate faster programming. Once the device enters the
Unlock Bypass mode, only two write cycles are required to program a word or byte, instead of four. The
“Word Program Command Sequence” section has de-
, and OE# to VIH.
IL
tails on programming data to the device using both
standard and Unlock Bypass command sequences.
An erase operation can erase one sector, multiple sectors, or the entire device. Ta bl e 2 indicates the address
space that each sector occupies.
See the table in “DC Characteristics” on page 45 for
the active current specification for the write mode. “AC
Characteristics” on page 47 contains timing specifica-
tion tables and timing diagrams for write operations.
Write Buffer
Write Buffer Programming allows the system write to a
maximum of 16 words/32 bytes in one programming
operation. This results in faster effective programming
time than the standard programming algorithms. See
“Write Buffer” for more information.
Accelerated Program Operation
The device offers accelerated program operations
through the ACC function. This is one of two functions
provided by the WP#/ACC pin. This function is primarily intended to allow faster manufacturing throughput
at the factory.
If the system asserts V
on this pin, the device auto-
HH
matically enters the aforementioned Unlock Bypass
mode, temporarily unprotects any protected sector
groups, and uses the higher voltage on the pin to reduce the time required for program operations. The
system would use a two-cycle program command sequence as required by the Unlock Bypass mode. Removing V
from the WP#/ACC pin returns the device
HH
to normal operation. Note that the WP#/ACC pin must
not be at V
for operations other than accelerated
HH
programming, or device damage may result. WP# has
an internal pullup; when unconnected, WP# is at V
.
IH
Autoselect Functions
If the system writes the autoselect command sequence, the device enters the autoselect mode. The
system can then read autoselect codes from the internal register (which is separate from the memory array)
on DQ7–DQ0. Standard read cycle timings apply in
this mode. See “Autoselect Mode” on page 20 and
“Autoselect Command Sequence” on page 29 for
more information.
Standby Mode
When the system is not reading or writing to the device, it can place the device in the standby mode. In
this mode, current consumption is greatly reduced,
and the outputs are placed in the high impedance
state, independent of the OE# input.
The device enters the CMOS standby mode when the
CE# and RESET# pins are both held at V
(Note that this is a more restricted voltage range than
± 0.3 V.
IO
12Am29LV128MH/L25270C7 January 31, 2007
Page 13
DATA SHEET
VIH.) If CE# and RESET# are held at VIH, but not within
V
± 0.3 V, the device will be in the standby mode, but
IO
the standby current will be greater. The device requires standard access time (t
) for read access
CE
when the device is in either of these standby modes,
before it is ready to read data.
If the device is deselected during erasure or programming, the device draws active current until the
operation is completed.
See the table in “DC Characteristics” on page 45 for
the standby current specification.
Automatic Sleep Mode
The automatic sleep mode minimizes Flash device energy consumption. The device automatically enables
this mode when addresses remain stable for t
ACC
+
30 ns. The automatic sleep mode is independent of
the CE#, WE#, and OE# control signals. Standard address access timings provide new data when addresses are changed. While in sleep mode, output
data is latched and always available to the system.
See the table in “DC Characteristics” on page 45 for
the automatic sleep mode current specification.
RESET#: Hardware Reset Pin
The RESET# pin provides a hardware method of resetting the device to reading array data. When the RE-
SET# pin is driven low for at least a period of t
RP
, the
device immediately terminates any operation in
progress, tristates all output pins, and ignores all
read/write commands for the duration of the RESET#
pulse. The device also resets the internal state machine to reading array data. The operation that was interrupted should be reinitiated once the device is
ready to accept another command sequence, to ensure data integrity.
Current is reduced for the duration of the RESET#
pulse. When RESET# is held at V
draws CMOS standby current (I
at V
but not within VSS±0.3 V, the standby current will
IL
±0.3 V, the device
SS
). If RESET# is held
CC4
be greater.
The RESET# pin may be tied to the system reset circuitry. A system reset would thus also reset the Flash
memory, enabling the system to read the boot-up firmware from the Flash memory.
See the tables in “AC Characteristics” on page 47 for
RESET# parameters and to Figure 16 for the timing diagram.
Output Disable Mode
When the OE# input is at VIH, output from the device is
disabled. The output pins are placed in the high
impedance state.
January 31, 2007 25270C7Am29LV128MH/L13
Page 14
DATA SHEET
Table 2. Sector Address Table (Sheet 1 of 6)
SectorA22–A15
SA00000000064/32000000–00FFFF000000–007FFF
SA10000000164/32010000–01FFFF008000–00FFFF
SA20000001064/32020000–02FFFF010000–017FFF
SA30000001164/32030000–03FFFF018000–01FFFF
SA40000010064/32040000–04FFFF020000–027FFF
SA50000010164/32050000–05FFFF028000–02FFFF
SA60000011064/32060000–06FFFF030000–037FFF
SA70000011164/32070000–07FFFF038000–03FFFF
SA80000100064/32080000–08FFFF040000–047FFF
SA90000100164/32090000–09FFFF048000–04FFFF
SA100000101064/320A0000–0AFFFF050000–057FFF
SA110000101164/320B0000–0BFFFF058000–05FFFF
SA120000110064/320C0000–0CFFFF060000–067FFF
SA130000110164/320D0000–0DFFFF068000–06FFFF
SA140000111064/320E0000–0EFFFF070000–077FFF
SA150000111164/320F0000–0FFFFF078000–07FFFF
SA160001000064/32100000–10FFFF080000–087FFF
SA170001000164/32110000–11FFFF088000–08FFFF
SA180001001064/32120000–12FFFF090000–097FFF
SA190001001164/32130000–13FFFF098000–09FFFF
SA200001010064/32140000–14FFFF0A0000–0A7FFF
SA210001010164/32150000–15FFFF0A8000–0AFFFF
SA220001011064/32160000–16FFFF0B0000–0B7FFF
SA230001011164/32170000–17FFFF0B8000–0BFFFF
SA240001100064/32180000–18FFFF0C0000–0C7FFF
SA250001100164/32190000–19FFFF0C8000–0CFFFF
SA260001101064/321A0000–1AFFFF0D0000–0D7FFF
SA270001101164/321B0000–1BFFFF0D8000–0DFFFF
SA280001110064/321C0000–1CFFFF0E0000–0E7FFF
SA290001110164/321D0000–1DFFFF0E8000–0EFFFF
SA300001111064/321E0000–1EFFFF0F0000–0F7FFF
SA310001111164/321F0000–1FFFFF0F8000–0FFFFF
SA320010000064/32200000–20FFFF100000–107FFF
SA330010000164/32210000–21FFFF108000–10FFFF
SA340010001064/32220000–22FFFF110000–117FFF
SA350010001164/32230000–23FFFF118000–11FFFF
SA360010010064/32240000–24FFFF120000–127FFF
SA370010010164/32250000–25FFFF128000–12FFFF
SA380010011064/32260000–26FFFF130000–137FFF
SA390010011164/32270000–27FFFF138000–13FFFF
SA400010100064/32280000–28FFFF140000–147FFF
SA410010100164/32290000–29FFFF148000–14FFFF
SA420010101064/322A0000–2AFFFF150000–157FFF
SA430010101164/322B0000–2BFFFF158000–15FFFF
SA440010110064/322C0000–2CFFFF160000–167FFF
SA450010110164/322D0000–2DFFFF168000–16FFFF
SA460010111064/322E0000–2EFFFF170000–177FFF
Sector Size
(Kbytes/Kwords)
8-bit
Address Range
(in hexadecimal)
16-bit
Address Range
(in hexadecimal)
14Am29LV128MH/L25270C7 January 31, 2007
Page 15
DATA SHEET
Table 2. Sector Address Table (Sheet 2 of 6)
SectorA22–A15
SA470010111164/322F0000–2FFFFF178000–17FFFF
SA480011000064/32300000–30FFFF180000–187FFF
SA490011000164/32310000–31FFFF188000–18FFFF
SA500011001064/32320000–32FFFF190000–197FFF
SA510011001164/32330000–33FFFF198000–19FFFF
SA520011010064/32340000–34FFFF1A0000–1A7FFF
SA530011010164/32350000–35FFFF1A8000–1AFFFF
SA540011011064/32360000–36FFFF1B0000–1B7FFF
SA550011011164/32370000–37FFFF1B8000–1BFFFF
SA560011100064/32380000–38FFFF1C0000–1C7FFF
SA570011100164/32390000–39FFFF1C8000–1CFFFF
SA580011101064/323A0000–3AFFFF1D0000–1D7FFF
SA590011101164/323B0000–3BFFFF1D8000–1DFFFF
SA600011110064/323C0000–3CFFFF1E0000–1E7FFF
SA610011110164/323D0000–3DFFFF1E8000–1EFFFF
SA620011111064/323E0000–3EFFFF1F0000–1F7FFF
SA630011111164/323F0000–3FFFFF1F8000–1FFFFF
SA640100000064/32400000–40FFFF200000–207FFF
SA650100000164/32410000–41FFFF208000–20FFFF
SA660100001064/32420000–42FFFF210000–217FFF
SA670100001164/32430000–43FFFF218000–21FFFF
SA680100010064/32440000–44FFFF220000–227FFF
SA690100010164/32450000–45FFFF228000–22FFFF
SA700100011064/32460000–46FFFF230000–237FFF
SA710100011164/32470000–47FFFF238000–23FFFF
SA720100100064/32480000–48FFFF240000–247FFF
SA730100100164/32490000–49FFFF248000–24FFFF
SA740100101064/324A0000–4AFFFF250000–257FFF
SA750100101164/324B0000–4BFFFF258000–25FFFF
SA760100110064/324C0000–4CFFFF260000–267FFF
SA770100110164/324D0000–4DFFFF268000–26FFFF
SA780100111064/324E0000–4EFFFF270000–277FFF
SA790100111164/324F0000–4FFFFF278000–27FFFF
SA800101000064/32500000–50FFFF280000–287FFF
SA810101000164/32510000–51FFFF288000–28FFFF
SA820101001064/32520000–52FFFF290000–297FFF
SA830101001164/32530000–53FFFF298000–29FFFF
SA840101010064/32540000–54FFFF2A0000–2A7FFF
SA850101010164/32550000–55FFFF2A8000–2AFFFF
SA860101011064/32560000–56FFFF2B0000–2B7FFF
SA870101011164/32570000–57FFFF2B8000–2BFFFF
SA880101100064/32580000–58FFFF2C0000–2C7FFF
SA890101100164/32590000–59FFFF2C8000–2CFFFF
SA900101101064/325A0000–5AFFFF2D0000–2D7FFF
SA910101101164/325B0000–5BFFFF2D8000–2DFFFF
SA920101110064/325C0000–5CFFFF2E0000–2E7FFF
SA930101110164/325D0000–5DFFFF2E8000–2EFFFF
SA940101111064/325E0000–5EFFFF2F0000–2F7FFF
Sector Size
(Kbytes/Kwords)
8-bit
Address Range
(in hexadecimal)
16-bit
Address Range
(in hexadecimal)
January 31, 2007 25270C7Am29LV128MH/L15
Page 16
DATA SHEET
Table 2. Sector Address Table (Sheet 3 of 6)
SectorA22–A15
SA950101111164/325F0000–5FFFFF2F8000–2FFFFF
SA960110000064/32600000–60FFFF300000–307FFF
SA970110000164/32610000–61FFFF308000–30FFFF
SA980110001064/32620000–62FFFF310000–317FFF
SA990110001164/32630000–63FFFF318000–31FFFF
SA1000110010064/32640000–64FFFF320000–327FFF
SA1010110010164/32650000–65FFFF328000–32FFFF
SA1020110011064/32660000–66FFFF330000–337FFF
SA1030110011164/32670000–67FFFF338000–33FFFF
SA1040110100064/32680000–68FFFF340000–347FFF
SA1050110100164/32690000–69FFFF348000–34FFFF
SA1060110101064/326A0000–6AFFFF350000–357FFF
SA1070110101164/326B0000–6BFFFF358000–35FFFF
SA1080110110064/326C0000–6CFFFF360000–367FFF
SA1090110110164/326D0000–6DFFFF368000–36FFFF
SA1100110111064/326E0000–6EFFFF370000–377FFF
SA1110110111164/326F0000–6FFFFF378000–37FFFF
SA1120111000064/32700000–70FFFF380000–387FFF
SA1130111000164/32710000–71FFFF388000–38FFFF
SA1140111001064/32720000–72FFFF390000–397FFF
SA1150111001164/32730000–73FFFF398000–39FFFF
SA1160111010064/32740000–74FFFF3A0000–3A7FFF
SA1170111010164/32750000–75FFFF3A8000–3AFFFF
SA1180111011064/32760000–76FFFF3B0000–3B7FFF
SA1190111011164/32770000–77FFFF3B8000–3BFFFF
SA1200111100064/32780000–78FFFF3C0000–3C7FFF
SA1210111100164/32790000–79FFFF3C8000–3CFFFF
SA1220111101064/327A0000–7AFFFF3D0000–3D7FFF
SA1230111101164/327B0000–7BFFFF3D8000–3DFFFF
SA1240111110064/327C0000–7CFFFF3E0000–3E7FFF
SA1250111110164/327D0000–7DFFFF3E8000–3EFFFF
SA1260111111064/327E0000–7EFFFF3F0000–3F7FFF
SA1270111111164/327F0000–7FFFFF3F8000–3FFFFF
SA1281000000064/32800000–80FFFF400000–407FFF
SA1291000000164/32810000–81FFFF408000–40FFFF
SA1301000001064/32820000–82FFFF410000–417FFF
SA1311000001164/32830000–83FFFF418000–41FFFF
SA1321000010064/32840000–84FFFF420000–427FFF
SA1331000010164/32850000–85FFFF428000–42FFFF
SA1341000011064/32860000–86FFFF430000–437FFF
SA1351000011164/32870000–87FFFF438000–43FFFF
SA1361000100064/32880000–88FFFF440000–447FFF
SA1371000100164/32890000–89FFFF448000–44FFFF
SA1381000101064/328A0000–8AFFFF450000–457FFF
SA1391000101164/328B0000–8BFFFF458000–45FFFF
SA1401000110064/328C0000–8CFFFF460000–467FFF
SA1411000110164/328D0000–8DFFFF468000–46FFFF
SA1421000111064/328E0000–8EFFFF470000–477FFF
Sector Size
(Kbytes/Kwords)
8-bit
Address Range
(in hexadecimal)
16-bit
Address Range
(in hexadecimal)
16Am29LV128MH/L25270C7 January 31, 2007
Page 17
DATA SHEET
Table 2. Sector Address Table (Sheet 4 of 6)
SectorA22–A15
SA1431000111164/328F0000–8FFFFF478000–47FFFF
SA1441001000064/32900000–90FFFF480000–487FFF
SA1451001000164/32910000–91FFFF488000–48FFFF
SA1461001001064/32920000–92FFFF490000–497FFF
SA1471001001164/32930000–93FFFF498000–49FFFF
SA1481001010064/32940000–94FFFF4A0000–4A7FFF
SA1491001010164/32950000–95FFFF4A8000–4AFFFF
SA1501001011064/32960000–96FFFF4B0000–4B7FFF
SA1511001011164/32970000–97FFFF4B8000–4BFFFF
SA1521001100064/32980000–98FFFF4C0000–4C7FFF
SA1531001100164/32990000–99FFFF4C8000–4CFFFF
SA1541001101064/329A0000–9AFFFF4D0000–4D7FFF
SA1551001101164/329B0000–9BFFFF4D8000–4DFFFF
SA1561001110064/329C0000–9CFFFF4E0000–4E7FFF
SA1571001110164/329D0000–9DFFFF4E8000–4EFFFF
SA1581001111064/329E0000–9EFFFF4F0000–4F7FFF
SA1591001111164/329F0000–9FFFFF4F8000–4FFFFF
SA1601010000064/32A00000–A0FFFF500000–507FFF
SA1611010000164/32A10000–A1FFFF508000–50FFFF
SA1621010001064/32A20000–A2FFFF510000–517FFF
SA1631010001164/32A30000–A3FFFF518000–51FFFF
SA1641010010064/32A40000–A4FFFF520000–527FFF
SA1651010010164/32A50000–A5FFFF528000–52FFFF
SA1661010011064/32A60000–A6FFFF530000–537FFF
SA1671010011164/32A70000–A7FFFF538000–53FFFF
SA1681010100064/32A80000–A8FFFF540000–547FFF
SA1691010100164/32A90000–A9FFFF548000–54FFFF
SA1701010101064/32AA0000–AAFFFF550000–557FFF
SA1711010101164/32AB0000–ABFFFF558000–55FFFF
SA1721010110064/32AC0000–ACFFFF560000–567FFF
SA1731010110164/32AD0000–ADFFFF568000–56FFFF
SA1741010111064/32AE0000–AEFFFF570000–577FFF
SA1751010111164/32AF0000–AFFFFF578000–57FFFF
SA1761011000064/32B00000–B0FFFF580000–587FFF
SA1771011000164/32B10000–B1FFFF588000–58FFFF
SA1781011001064/32B20000–B2FFFF590000–597FFF
SA1791011001164/32B30000–B3FFFF598000–59FFFF
SA1801011010064/32B40000–B4FFFF5A0000–5A7FFF
SA1811011010164/32B50000–B5FFFF5A8000–5AFFFF
SA1821011011064/32B60000–B6FFFF5B0000–5B7FFF
SA1831011011164/32B70000–B7FFFF5B8000–5BFFFF
SA1841011100064/32B80000–B8FFFF5C0000–5C7FFF
SA1851011100164/32B90000–B9FFFF5C8000–5CFFFF
SA1861011101064/32BA0000–BAFFFF5D0000–5D7FFF
SA1871011101164/32BB0000–BBFFFF5D8000–5DFFFF
SA1881011110064/32BC0000–BCFFFF5E0000–5E7FFF
SA1891011110164/32BD0000–BDFFFF5E8000–5EFFFF
SA1901011111064/32BE0000–BEFFFF5F0000–5F7FFF
Sector Size
(Kbytes/Kwords)
8-bit
Address Range
(in hexadecimal)
16-bit
Address Range
(in hexadecimal)
January 31, 2007 25270C7Am29LV128MH/L17
Page 18
DATA SHEET
Table 2. Sector Address Table (Sheet 5 of 6)
SectorA22–A15
SA1911011111164/32BF0000–BFFFFF5F8000–5FFFFF
SA1921100000064/32C00000–C0FFFF600000–607FFF
SA1931100000164/32C10000–C1FFFF608000–60FFFF
SA1941100001064/32C20000–C2FFFF610000–617FFF
SA1951100001164/32C30000–C3FFFF618000–61FFFF
SA1961100010064/32C40000–C4FFFF620000–627FFF
SA1971100010164/32C50000–C5FFFF628000–62FFFF
SA1981100011064/32C60000–C6FFFF630000–637FFF
SA1991100011164/32C70000–C7FFFF638000–63FFFF
SA2001100100064/32C80000–C8FFFF640000–647FFF
SA2011100100164/32C90000–C9FFFF648000–64FFFF
SA2021100101064/32CA0000–CAFFFF650000–657FFF
SA2031100101164/32CB0000–CBFFFF658000–65FFFF
SA2041100110064/32CC0000–CCFFFF660000–667FFF
SA2051100110164/32CD0000–CDFFFF668000–66FFFF
SA2061100111064/32CE0000–CEFFFF670000–677FFF
SA2071100111164/32CF0000–CFFFFF678000–67FFFF
SA2081101000064/32D00000–D0FFFF680000–687FFF
SA2091101000164/32D10000–D1FFFF688000–68FFFF
SA2101101001064/32D20000–D2FFFF690000–697FFF
SA2111101001164/32D30000–D3FFFF698000–69FFFF
SA2121101010064/32D40000–D4FFFF6A0000–6A7FFF
SA2131101010164/32D50000–D5FFFF6A8000–6AFFFF
SA2141101011064/32D60000–D6FFFF6B0000–6B7FFF
SA2151101011164/32D70000–D7FFFF6B8000–6BFFFF
SA2161101100064/32D80000–D8FFFF6C0000–6C7FFF
SA2171101100164/32D90000–D9FFFF6C8000–6CFFFF
SA2181101101064/32DA0000–DAFFFF6D0000–6D7FFF
SA2191101101164/32DB0000–DBFFFF6D8000–6DFFFF
SA2201101110064/32DC0000–DCFFFF6E0000–6E7FFF
SA2211101110164/32DD0000–DDFFFF6E8000–6EFFFF
SA2221101111064/32DE0000–DEFFFF6F0000–6F7FFF
SA2231101111164/32DF0000–DFFFFF6F8000–6FFFFF
SA2241110000064/32E00000–E0FFFF700000–707FFF
SA2251110000164/32E10000–E1FFFF708000–70FFFF
SA2261110001064/32E20000–E2FFFF710000–717FFF
SA2271110001164/32E30000–E3FFFF718000–71FFFF
SA2281110010064/32E40000–E4FFFF720000–727FFF
SA2291110010164/32E50000–E5FFFF728000–72FFFF
SA2301110011064/32E60000–E6FFFF730000–737FFF
SA2311110011164/32E70000–E7FFFF738000–73FFFF
SA2321110100064/32E80000–E8FFFF740000–747FFF
SA2331110100164/32E90000–E9FFFF748000–74FFFF
SA2341110101064/32EA0000–EAFFFF750000–757FFF
SA2351110101164/32EB0000–EBFFFF758000–75FFFF
SA2361110110064/32EC0000–ECFFFF760000–767FFF
SA2371110110164/32ED0000–EDFFFF768000–76FFFF
SA2381110111064/32EE0000–EEFFFF770000–777FFF
Sector Size
(Kbytes/Kwords)
8-bit
Address Range
(in hexadecimal)
16-bit
Address Range
(in hexadecimal)
18Am29LV128MH/L25270C7 January 31, 2007
Page 19
DATA SHEET
Table 2. Sector Address Table (Sheet 6 of 6)
SectorA22–A15
SA2391110111164/32EF0000–EFFFFF778000–77FFFF
SA2401111000064/32F00000–F0FFFF780000–787FFF
SA2411111000164/32F10000–F1FFFF788000–78FFFF
SA2421111001064/32F20000–F2FFFF790000–797FFF
SA2431111001164/32F30000–F3FFFF798000–79FFFF
SA2441111010064/32F40000–F4FFFF7A0000–7A7FFF
SA2451111010164/32F50000–F5FFFF7A8000–7AFFFF
SA2461111011064/32F60000–F6FFFF7B0000–7B7FFF
SA2471111011164/32F70000–F7FFFF7B8000–7BFFFF
SA2481111100064/32F80000–F8FFFF7C0000–7C7FFF
SA2491111100164/32F90000–F9FFFF7C8000–7CFFFF
SA2501111101064/32FA0000–FAFFFF7D0000–7D7FFF
SA2511111101164/32FB0000–FBFFFF7D8000–7DFFFF
SA2521111110064/32FC0000–FCFFFF7E0000–7E7FFF
SA2531111110164/32FD0000–FDFFFF7E8000–7EFFFF
SA2541111111064/32FE0000–FEFFFF7F0000–7F7FFF
SA2551111111164/32FF0000–FFFFFF7F8000–7FFFFF
Sector Size
(Kbytes/Kwords)
8-bit
Address Range
(in hexadecimal)
16-bit
Address Range
(in hexadecimal)
January 31, 2007 25270C7Am29LV128MH/L19
Page 20
DATA SHEET
Autoselect Mode
The autoselect mode provides manufacturer and device identification, and sector group protection verification, through identifier codes output on DQ7–DQ0.
This mode is primarily intended for programming
equipment to automatically match a device to be programmed with its corresponding programming algorithm. However, the autoselect codes can also be
accessed in-system through the command register.
When using programming equipment, the autoselect
mode requires V
A6, A3, A2, A1, and A0 must be as shown in Tab l e 3 In
addition, when verifying sector protection, the sector
address must appear on the appropriate highest order
address bits (see Ta bl e 2 ). Tab le 3 shows the remaining address bits that are don’t care. When all necessary bits have been set as required, the programming
equipment may then read the corresponding identifier
code on DQ7–DQ0.
To access the autoselect codes in-system, the host
system can issue the autoselect command via the
command register, as shown in Ta bl e 1 0 and Tab le 1 1.
This method does not require V
. See “Autoselect
ID
Command Sequence” on page 29 for more informa-
tion.
A3
toA2A1A0
A4
LLH 22 X7Eh
DQ8 to DQ15
BYTE#
= V
BYTE#
IH
= V
IL
00h (unprotected)
98h (factory locked),
18h (not factory locked)
88h (factory locked),
08h (not factory locked)
DQ7 to DQ0
01h (protected),
Legend: L = Logic Low = VIL, H = Logic High = VIH, SA = Sector Address, X = Don’t care.
20Am29LV128MH/L25270C7 January 31, 2007
Page 21
DATA SHEET
Sector Group Protection and Unprotection
The hardware sector group protection feature disables
both program and erase operations in any sector
group. The hardware sector group unprotection feature re-enables both program and erase operations in
previously protected sector groups. Sector group protection/unprotection can be implemented via two
methods.
Sector group protection/unprotection requires V
the RESET# pin only, and can be implemented either
in-system or via programming equipment. Figure 2
shows the algorithms and Figure 25 shows the timing
diagram. This method uses standard microprocessor
bus cycle timing. For sector group unprotect, all unprotected sector group must first be protected prior to the
first sector group unprotect write cycle.
The device is shipped with all sector groups unprotected. AMD offers the option of programming and protecting sector groups at its factory prior to shipping the
device through AMD’s ExpressFlash™ Service. Contact an AMD representative for details.
It is possible to determine whether a sector group is
protected or unprotected. See “Autoselect Mode” on
page 20 for details.
Table 4. Sector Group Protection/Unprotection
Address Table
Sector GroupA22–A15
SA000000000
SA100000001
SA200000010
SA300000011
SA4–SA7000001xx
SA8–SA11000010xx
SA12–SA15000011xx
SA16–SA19000100xx
SA20–SA23000101xx
SA24–SA27000110xx
SA28–SA31000111xx
SA32–SA35001000xx
SA36–SA39001001xx
SA40–SA43001010xx
SA44–SA47001011xx
SA48–SA51001100xx
SA52–SA55001101xx
SA56–SA59001110xx
SA60–SA63001111xx
SA64–SA67010000xx
SA68–SA71010001xx
SA72–SA75010010xx
SA76–SA79010011xx
SA80–SA83010100xx
on
ID
Sector GroupA22–A15
SA84–SA87010101xx
SA88–SA91010110xx
SA92–SA95010111xx
SA96–SA99011000xx
SA100–SA103011001xx
SA104–SA107011010xx
SA108–SA111011011xx
SA112–SA115011100xx
SA116–SA119011101xx
SA120–SA123011110xx
SA124–SA127011111xx
SA128–SA131100000xx
SA132–SA135100001xx
SA136–SA139100010xx
SA140–SA143100011xx
SA144–SA147100100xx
SA148–SA151100101xx
SA152–SA155100110xx
SA156–SA159100111xx
SA160–SA163101000xx
SA164–SA167101001xx
SA168–SA171101010xx
SA172–SA175101011xx
SA176–SA179101100xx
SA180–SA183101101xx
SA184–SA187101110xx
SA188–SA191101111xx
SA192–SA195110000xx
SA196–SA199110001xx
SA200–SA203110010xx
SA204–SA207110011xx
SA208–SA211110100xx
SA212–SA215110101xx
SA216–SA219110110xx
SA220–SA223110111xx
SA224–SA227111000xx
SA228–SA231111001xx
SA232–SA235111010xx
SA236–SA239111011xx
SA240–SA243111100xx
SA244–SA247111101xx
SA248–SA251111110xx
SA25211111100
SA25311111101
SA25411111110
SA25511111111
January 31, 2007 25270C7Am29LV128MH/L21
Page 22
DATA SHEET
Write Protect (WP#)
The Write Protect function provides a hardware
method of protecting the first or last sector group without using V
. Write Protect is one of two functions pro-
ID
vided by the WP#/ACC input.
If the system asserts V
on the WP#/ACC pin, the de-
IL
vice disables program and erase functions in the first
or last sector group independently of whether those
sector groups were protected or unprotected using the
method described in “Sector Group Protection and
Unprotection”. Note that if WP#/ACC is at V
when the
IL
device is in the standby mode, the maximum input
load current is increased. See the table in “DC Char-
acteristics” on page 45
If the system asserts V
on the WP#/ACC pin, the de-
IH
vice reverts to whether the first or last sector was previously set to be protected or unprotected using the
method described in “Sector Group Protection and
Unprotection”. Note that WP# has an internal pullup;
when unconnected, WP# is at V
.
IH
Temporary Sector Group Unprotect
This feature allows temporary unprotection of previously protected sector groups to change data in-system. The Sector Group Unprotect mode is activated by
setting the RESET# pin to V
merly protected sector groups can be programmed or
erased by selecting the sector group addresses. Once
V
is removed from the RESET# pin, all the previously
ID
protected sector groups are protected again. Figure 1
. During this mode, for-
ID
shows the algorithm, and Figure 24 shows the timing
diagrams, for this feature.
START
RESET# = V
(Note 1)
Perform Erase or
Program Operations
RESET# = V
Temporary Sector Group
Unprotect Completed
(Note 2)
Notes:
1. All protected sector groups unprotected (If WP# = V
the first or last sector will remain protected).
2. All previously protected sector groups are protected
once again.
ID
IH
,
IL
Figure 1. Temporary Sector Group
Unprotect Operation
22Am29LV128MH/L25270C7 January 31, 2007
Page 23
DATA SHEET
Temporary Sector
Unprotect Mode
Increment
PLSCNT
No
PLSCNT
= 25?
Yes
Device failed
Sector Group
Protect
Algorithm
START
PLSCNT = 1
RESET# = V
Wait 1 μs
No
First Write
Cycle = 60h?
Set up sector
address
Sector Protect:
Write 60h to sector
address with
A6 = 0, A1 = 1,
A0 = 0
Wait 150 µs
Verify Sector
Protect: Write 40h
to sector address
with A6 = 0,
A1 = 1, A0 = 0
Read from
sector address
with A6 = 0,
A1 = 1, A0 = 0
No
Data = 01h?
Protect another
sector?
Remove V
from RESET#
Write reset
command
Sector Protect
complete
Yes
Yes
No
START
Protect all sectors:
The indicated portion
of the sector protect
ID
Reset
PLSCNT = 1
Yes
ID
algorithm must be
performed for all
unprotected sectors
prior to issuing the
first sector
unprotect address
Increment
PLSCNT
No
PLSCNT
= 1000?
Yes
Device failed
Sector Group
PLSCNT = 1
RESET# = V
Wait 1 μs
First Write
Cycle = 60h?
No
All sectors
protected?
Set up first sector
address
Sector Unprotect:
Write 60h to sector
address with
A6 = 1, A1 = 1,
A0 = 0
Wait 15 ms
Verify Sector
Unprotect: Write
40h to sector
address with
A6 = 1, A1 = 1,
A0 = 0
Read from
sector address
with A6 = 1,
A1 = 1, A0 = 0
No
Data = 00h?
Last sector
verified?
Remove V
from RESET#
Yes
Yes
Yes
Yes
ID
No
Temporary Sector
Unprotect Mode
Set up
next sector
address
No
ID
Unprotect
Algorithm
Write reset
command
Sector Unprotect
complete
Figure 2. In-System Sector Group Protect/Unprotect Algorithms
January 31, 2007 25270C7Am29LV128MH/L23
Page 24
DATA SHEET
Secured Silicon Sector Flash
Memory Region
The Secured Silicon Sector feature provides a Flash
memory region that enables permanent part identification through an Electronic Serial Number (ESN). The
Secured Silicon Sector is 256 bytes in length, and
uses a Secured Silicon Sector Indicator Bit (DQ7) to
indicate whether or not the Secured Silicon Sector is
locked when shipped from the factory. This bit is permanently set at the factory and cannot be changed,
which prevents cloning of a factory locked part. This
ensures the security of the ESN once the product is
shipped to the field.
AMD offers the device with the Secured Silicon Sector
either customer lockable (standard shipping option) or
factory locked (contact an AMD sales representative
for ordering information). The customer-lockable version is shipped with the Secured Silicon Sector unprotected, allowing customers to program the sector after
receiving the device. The customer-lockable version
also has the Secured Silicon Sector Indicator Bit permanently set to a “0.” The factory-locked version is always protected when shipped from the factory, and
has the Secured Silicon Sector Indicator Bit permanently set to a “1.” Thus, the Secured Silicon Sector Indicator Bit prevents customer-lockable devices from
being used to replace devices that are factory locked.
Note that the ACC function and unlock bypass modes
are not available when the Secured Silicon Sector is
enabled.
The Secured Silicon sector address space in this device is allocated as follows:
Table 5. Secured Silicon Sector Contents
Secured Silicon
Sector Address
Range
000000h–000007h
000008h–00007FhUnavailable
The system accesses the Secured Silicon Sector
through a command sequence (see “Enter Secured
Silicon Sector/Exit Secured Silicon Sector
Command Sequence” on page 30). After the system
has written the Enter Secured Silicon Sector command sequence, it may read the Secured Silicon Sector by using the addresses normally occupied by the
first sector (SA0). This mode of operation continues
until the system issues the Exit Secured Silicon Sector
command sequence, or until power is removed from
Customer
Lockable
Determined by
customer
ESN Factory
Locked
ESN
ExpressFlash
Factory Locked
ESN or
determined by
customer
Determined by
customer
the device. On power-up, or following a hardware reset, the device reverts to sending commands to sector
SA0.
Customer Lockable: Secured Silicon Sector NOT
Programmed or Protected At the Factory
Unless otherwise specified, the device is shipped such
that the customer may program and protect the
256-byte Secured Silicon sector.
Programming and protecting the Secured Silicon Sector must be used with caution since, once protected,
there is no procedure available for unprotecting the
Secured Silicon Sector area and none of the bits in the
Secured Silicon Sector memory space can be modified in any way.
The Secured Silicon Sector area can be protected
using one of the following procedures:
Write the three-cycle Enter Secured Silicon Sector
Region command sequence, and then follow the
in-system sector protect algorithm as shown in
Figure 2, except that RESET# may be at either V
or VID. This allows in-system protection of the Se-
cured Silicon Sector without raising any device pin
to a high voltage. Note that this method is only applicable to the Secured Silicon Sector.
To verify the protect/unprotect status of the Secured
Silicon Sector, follow the algorithm shown in
Figure 3.
Once the Secured Silicon Sector is programmed,
locked and verified, the system must write the Exit Secured Silicon Sector Region command sequence to
return to reading and writing within the remainder of
the array.
Factory Locked: Secured Silicon Sector
Programmed and Protected At the Factory
In devices with an ESN, the Secured Silicon Sector is
protected when the device is shipped from the factory.
The Secured Silicon Sector cannot be modified in any
way. An ESN Factory Locked device has an 16-byte
random ESN at addresses 000000h–000007h. Please
contact your local AMD sales representative for details
on ordering ESN Factory Locked devices.
Customers may opt to have their code programmed by
AMD through the AMD ExpressFlash service (Express
Flash Factory Locked). The devices are then shipped
from AMD’s factory with the Secured Silicon Sector
permanently locked. Contact an AMD representative
for details on using AMD’s ExpressFlash service.
IH
24Am29LV128MH/L25270C7 January 31, 2007
Page 25
DATA SHEET
START
RESET# =
or V
V
IH
ID
Wait 1 μs
Write 60h to
any address
Write 40h to SecSi
Sector address
with A6 = 0,
A1 = 1, A0 = 0
Read from SecSi
Sector address
with A6 = 0,
A1 = 1, A0 = 0
If data = 00h,
SecSi Sector is
unprotected.
If data = 01h,
SecSi Sector is
protected.
Remove VIH or VID
from RESET#
Write reset
command
SecSi Sector
Protect Verify
complete
Figure 3. Secured Silicon Sector Protect Verify
Hardware Data Protection
The command sequence requirement of unlock cycles
for programming or erasing provides data protection
against inadvertent writes (refer to Tab l e 1 0 and
Ta bl e 1 1 for command definitions). In addition, the fol-
lowing hardware data protection measures prevent accidental erasure or programming, which might
otherwise be caused by spurious system level signals
during V
power-up and power-down transitions, or
CC
from system noise.
Low V
When V
cept any write cycles. This protects data during V
Write Inhibit
CC
is less than V
CC
, the device does not ac-
LKO
CC
power-up and power-down. The command register
and all internal program/erase circuits are disabled,
and the device resets to the read mode. Subsequent
writes are ignored until V
is greater than V
CC
LKO
. The
system must provide the proper signals to the control
pins to prevent unintentional writes when V
greater than V
LKO
.
CC
is
Write Pulse “Glitch” Protection
Noise pulses of less than 5 ns (typical) on OE#, CE#
or WE# do not initiate a write cycle.
Logical Inhibit
Write cycles are inhibited by holding any one of OE# =
V
, CE# = VIH or WE# = VIH. To initiate a write cycle,
IL
CE# and WE# must be a logical zero while OE# is a
logical one.
Power-Up Write Inhibit
If WE# = CE# = V
and OE# = VIH during power up,
IL
the device does not accept commands on the rising
edge of WE#. The internal state machine is automatically reset to the read mode on power-up.
COMMON FLASH MEMORY INTERFACE (CFI)
The Common Flash Interface (CFI) specification outlines device and host system software interrogation
handshake, which allows specific vendor-specified
software algorithms to be used for entire families of
devices. Software support can then be device-independent, JEDEC ID-independent, and forward- and
backward-compatible for the specified flash device
families. Flash vendors can standardize their existing
interfaces for long-term compatibility.
This device enters the CFI Query mode when the system writes the CFI Query command, 98h, to address
55h, any time the device is ready to read array data.
The system can read CFI information at the addresses
given in Ta bl e 6 , Ta bl e 7 , Ta bl e 8 , and Ta bl e 9 . To terminate reading CFI data, the system must write the
reset command.
The system can also write the CFI query command
when the device is in the autoselect mode. The device
enters the CFI query mode, and the system can read
CFI data at the addresses given in Tab le 6 , Tab le 7 ,
Ta bl e 8 , and Ta bl e 9 . The system must write the reset
command to return the device to reading array data.
For further information, please refer to the CFI Specification and CFI Publication 100, available via the World
Wide Web at http://www.amd.com/flash/cfi. Alternatively, contact an AMD representative for copies of
these documents.
January 31, 2007 25270C7Am29LV128MH/L25
Page 26
DATA SHEET
Table 6. CFI Query Identification String
Addresses (x16)DataDescription
10h
11h
12h
13h
14h
15h
16h
17h
18h
19h
1Ah
0051h
0052h
0059h
0002h
0000h
0040h
0000h
0000h
0000h
0000h
0000h
Query Unique ASCII string “QRY”
Primary OEM Command Set
Address for Primary Extended Table
Alternate OEM Command Set (00h = none exists)
Address for Alternate OEM Extended Table (00h = none exists)
Table 7. System Interface String
Addresses (x16)DataDescription
Min. (write/erase)
V
1Bh0027h
1Ch0036h
1Dh0000hV
1Eh0000hVPP Max. voltage (00h = no VPP pin present)
CC
D7–D4: volt, D3–D0: 100 millivolt
VCC Max. (write/erase)
D7–D4: volt, D3–D0: 100 millivolt
Min. voltage (00h = no VPP pin present)
PP
1Fh0007hTypical timeout per single byte/word write 2N µs
20h0007hTypical timeout for Min. size buffer write 2N µs (00h = not supported)
21h000AhTypical timeout per individual block erase 2N ms
22h0000hTypical timeout for full chip erase 2N ms (00h = not supported)
23h0001hMax. timeout for byte/word write 2N times typical
24h0005hMax. timeout for buffer write 2N times typical
N
25h0004hMax. timeout per individual block erase 2
times typical
26h0000hMax. timeout for full chip erase 2N times typical (00h = not supported)
26Am29LV128MH/L25270C7 January 31, 2007
Page 27
DATA SHEET
Table 8. Device Geometry Definition
Addresses (x16)DataDescription
27h0018hDevice Size = 2N byte
28h
29h
2Ah
2Bh
2Ch0001h
2Dh
2Eh
2Fh
30h
31h
32h
33h
34h
35h
36h
37h
38h
39h
3Ah
3Bh
3Ch
0002h
0000h
0005h
0000h
00FFh
0000h
0000h
0001h
0000h
0000h
0000h
0000h
0000h
0000h
0000h
0000h
0000h
0000h
0000h
0000h
Flash Device Interface description (refer to CFI publication 100)
N
Max. number of byte in multi-byte write = 2
(00h = not supported)
Number of Erase Block Regions within device (01h = uniform device, 02h = boot
device)
Erase Block Region 1 Information
(refer to the CFI specification or CFI publication 100)
Erase Block Region 2 Information (refer to CFI publication 100)
Erase Block Region 3 Information (refer to CFI publication 100)
Erase Block Region 4 Information (refer to CFI publication 100)
Writing specific address and data commands or sequences into the command register initiates device operations. Ta b le 10 and Tabl e 11 defines the valid
register command sequences. Writing incorrect ad-
dress and data values or writing them in the improper
sequence may place the device in an unknown state.
A reset command is then required to return the device
to reading array data.
All addresses are latched on the falling edge of WE#
or CE#, whichever happens later. All data is latched on
the rising edge of WE# or CE#, whichever happens
first. See “AC Characteristics” on page 47 for timing diagrams.
Reading Array Data
The device is “automatically set to reading array data
after device power-up. No commands are required to
retrieve data. The device is ready to read array data
after completing an Embedded Program or Embedded
Erase algorithm.
After the device accepts an Erase Suspend command,
the device enters the erase-suspend-read mode, after
which the system can read data from any
non-erase-suspended sector. After completing a programming operation in the Erase Suspend mode, the
system may once again read array data with the same
exception. See “Erase Suspend/Erase Resume Com-
mands” on page 35 for more information.
The system must issue the reset command to return
the device to the read (or erase-suspend-read) mode if
DQ5 goes high during an active program or erase operation, or if the device is in the autoselect mode. See
the next section, “Reset Command,” for more information.
written while the device is in the Erase Suspend mode,
writing the reset command returns the device to the
erase-suspend-read mode. Once programming begins, however, the device ignores reset commands
until the operation is complete.
The reset command may be written between the sequence cycles in an autoselect command sequence.
Once in the autoselect mode, the reset command
must be written to return to the read mode. If the device entered the autoselect mode while in the Erase
Suspend mode, writing the reset command returns the
device to the erase-suspend-read mode.
If DQ5 goes high during a program or erase operation,
writing the reset command returns the device to the
read mode (or erase-suspend-read mode if the device
was in Erase Suspend).
Note that if DQ1 goes high during a Write Buffer Programming operation, the system must write the
Write-to-Buffer-Abort Reset command sequence to
reset the device for the next operation.
Autoselect Command Sequence
The autoselect command sequence allows the host
system to access the manufacturer and device codes,
and determine whether or not a sector is protected.
Ta bl e 1 0 and Tab le 1 1 show the address and data re-
quirements. This method is an alternative to that
shown in Tab le 3 , which is intended for PROM programmers and requires V
autoselect command sequence may be written to an
address that is either in the read or
erase-suspend-read mode. The autoselect command
may not be written while the device is actively programming or erasing.
on address pin A9. The
ID
See “Reading Array Data” on page 29 in the Device
Bus Operations section for more information. “See the
table, “Read-Only Operations” on page 47 for the read
parameters, and Figure 14 shows the timing diagram.
Reset Command
Writing the reset command resets the device to the
read or erase-suspend-read mode. Address bits are
don’t cares for this command.
The reset command may be written between the sequence cycles in an erase command sequence before
erasing begins. This resets the device to the read
mode. Once erasure begins, however, the device ignores reset commands until the operation is complete.
The reset command may be written between the
sequence cycles in a program command sequence
before programming begins. This resets the device to
the read mode. If the program command sequence is
January 31, 2007 25270C7Am29LV128MH/L29
The autoselect command sequence is initiated by first
writing two unlock cycles. This is followed by a third
write cycle that contains the autoselect command. The
device then enters the autoselect mode. The system
may read at any address any number of times without
initiating another autoselect command sequence:
A read cycle at address XX00h returns the manu-
facturer code.
Three read cycles at addresses 01h, 0Eh, and 0Fh
return the device code.
A read cycle to an address containing a sector ad-
dress (SA), and the address 02h on A7–A0 in word
mode returns 01h if the sector is protected, or 00h if
it is unprotected.
The system must write the reset command to return to
the read mode (or erase-suspend-read mode if the device was previously in Erase Suspend).
Page 30
DATA SHEET
Enter Secured Silicon Sector/Exit Secured
Silicon Sector Command Sequence
The Secured Silicon Sector region provides a secured
data area containing an 8-word/16-byte random Electronic Serial Number (ESN). The system can access
the Secured Silicon Sector region by issuing the
three-cycle Enter Secured Silicon Sector command
sequence. The device continues to access the Secured Silicon Sector region until the system issues the
four-cycle Exit Secured Silicon Sector command sequence. The Exit Secured Silicon Sector command
sequence returns the device to normal operation.
Ta bl e 1 0 and Ta bl e 1 1 show the address and data re-
quirements for both command sequences. See also
“Secured Silicon Sector Flash Memory Region” on
page 24 for further information. Note: The write buffer,
ACC function, and unlock bypass modes are not available when the Secured Silicon Sector is enabled.
Word Program Command Sequence
Programming is a four-bus-cycle operation. The program command sequence is initiated by writing two
unlock write cycles, followed by the program set-up
command. The program address and data are written
next, which in turn initiate the Embedded Program algorithm. The system is not required to provide further
controls or timings. The device automatically provides
internally generated program pulses and verifies the
programmed cell margin. Ta bl e 1 0 and Tab le 1 1 show
the address and data requirements for the word program command sequence.
data is still “0.” Only erase operations can convert a “0”
to a “1.”
Note: Single byte programming is not supported in x8-mode.
Write buffer programming must be used during x8-mode
operation.
Unlock Bypass Command Sequence
The unlock bypass feature allows the system to program words to the device faster than using the standard program command sequence. The unlock bypass
command sequence is initiated by first writing two unlock cycles. This is followed by a third write cycle containing the unlock bypass command, 20h. The device
then enters the unlock bypass mode. A two-cycle unlock bypass program command sequence is all that is
required to program in this mode. The first cycle in this
sequence contains the unlock bypass program command, A0h; the second cycle contains the program
address and data. Additional data is programmed in
the same manner. This mode dispenses with the initial
two unlock cycles required in the standard program
command sequence, resulting in faster total programming time. Tabl e 1 0 and Ta bl e 1 1 show the requirements for the command sequence.
During the unlock bypass mode, only the Unlock Bypass Program and Unlock Bypass Reset commands
are valid. To exit the unlock bypass mode, the system
must issue the two-cycle unlock bypass reset command sequence. The first cycle must contain the data
90h. The second cycle must contain the data 00h. The
device then returns to the read mode.
When the Embedded Program algorithm is complete,
the device then returns to the read mode and addresses are no longer latched. The system can determine the status of the program operation by using
DQ7 or DQ6. See “Write Operation Status” on
page 39 for information on these status bits.
Any commands written to the device during the Embedded Program Algorithm are ignored. Note that a
hardware reset immediately terminates the program
operation. The program command sequence should
be reinitiated once the device has returned to the read
mode, to ensure data integrity. Note that the Secured
Silicon Sector, autoselect, and CFI functions are unavailable when a program operation is in progress.
Programming is allowed in any sequence and across
sector boundaries. A bit cannot be programmedfrom “0” back to a “1.” Attempting to do so may
cause the device to set DQ5 = 1, or cause the DQ7
and DQ6 status bits to indicate the operation was successful. However, a succeeding read will show that the
Write Buffer Programming
Write Buffer Programming allows the system write to a
maximum of 16 words/32 bytes in one programming
operation. This results in faster effective programming
time than the standard programming algorithms. The
Write Buffer Programming command sequence is initiated by first writing two unlock cycles. This is followed
by a third write cycle containing the Write Buffer Load
command written at the Sector Address in which programming will occur. The fourth cycle writes the sector
address and the number of word locations, minus one,
to be programmed. For example, if the system will program 6 unique address locations, then 05h should be
written to the device. This tells the device how many
write buffer addresses will be loaded with data and
therefore when to expect the Program Buffer to Flash
command. The number of locations to program cannot
exceed the size of the write buffer or the operation will
abort.
The fifth cycle writes the first address location and
data to be programmed. The write-buffer-page is selected by address bits A
dress/data pairs must fall within the
selected-write-buffer-page. The system then writes the
MAX–A4
. All subsequent ad-
30Am29LV128MH/L25270C7 January 31, 2007
Page 31
DATA SHEET
remaining address/data pairs into the write buffer.
Write buffer locations may be loaded in any order.
The write-buffer-page address must be the same for
all address/data pairs loaded into the write buffer.
(This means Write Buffer Programming cannot be performed across multiple write-buffer pages. This also
means that Write Buffer Programming cannot be performed across multiple sectors. If the system attempts
to load programming data outside of the selected
write-buffer page, the operation will abort.
Note that if a Write Buffer address location is loaded
multiple times, the address/data pair counter will be
decremented for every data load operation. The host
system must therefore account for loading a
write-buffer location more than once. The counter decrements for each data load operation, not for each
unique write-buffer-address location. Note also that if
an address location is loaded more than once into the
buffer, the final data loaded for that address will be
programmed.
Once the specified number of write buffer locations
have been loaded, the system must then write the Program Buffer to Flash command at the sector address.
Any other address and data combination aborts the
Write Buffer Programming operation. The device then
begins programming. Data polling should be used
while monitoring the last address location loaded into
the write buffer. DQ7, DQ6, DQ5, and DQ1 should be
monitored to determine the device status during Write
Buffer Programming.
The write-buffer programming operation can be suspended using the standard program suspend/resume
commands. Upon successful completion of the Write
Buffer Programming operation, the device is ready to
execute the next command.
The Write Buffer Programming Sequence can be
aborted in the following ways:
Load a value that is greater than the page buffer
size during the Number of Locations to Program
step.
Write to an address in a sector different than the
one specified during the Write-Buffer-Load command.
Write an Address/Data pair to a different
write-buffer-page than the one selected by the
Starting Address during the write buffer data loading stage of the operation.
Write data other than the Confirm Command after
the specified number of data load cycles.
The abort condition is indicated by DQ1 = 1, DQ7 =
DATA# (for the last address location loaded), DQ6 =
toggle, and DQ5=0. A Write-to-Buffer-Abort Reset
command sequence must be written to reset the device for the next operation. Note that the full 3-cycle
Write-to-Buffer-Abort Reset command sequence is required when using Write-Buffer-Programming features
in Unlock Bypass mode.
Accelerated Program
The device offers accelerated program operations
through the WP#/ACC pin. When the system asserts
V
on the WP#/ACC pin, the device automatically en-
HH
ters the Unlock Bypass mode. The system may then
write the two-cycle Unlock Bypass program command
sequence. The device uses the higher voltage on the
WP#/ACC pin to accelerate the operation. Note that
the WP#/ACC pin must not be at V
for operations
HH
other than accelerated programming, or device damage may result. WP# has an internal pullup; when unconnected, WP# is at V
.
IH
Figure 5 illustrates the algorithm for the program operation. Refer to the Erase and Program Operations
table in the AC Characteristics section for parameters,
and Figure 18 for timing diagrams.
January 31, 2007 25270C7Am29LV128MH/L31
Page 32
Write “Write to Buffer”
command and
Sector Address
DATA SHEET
No
Ye s
Ye s
(Note 1)
Write number of addresses
to program minus 1(WC)
and Sector Address
Write first address/data
WC = 0 ?
No
Abort Write to
Buffer Operation?
No
Write next address/data pair
WC = WC - 1
Write program buffer to
flash sector address
Read DQ7 - DQ0 at
Last Loaded Address
DQ7 = Data?
No
No
DQ5 = 1?DQ1 = 1?
Ye s
Ye s
Ye s
Part of “Write to Buffer”
Command Sequence
Write to a different
sector address
Write to buffer ABORTED.
Must write “Write-to-buffer
Abort Reset” command
sequence to return
to read mode.
Notes:
1. When Sector Address is specified, any address in
the selected sector is acceptable. However, when
loading Write-Buffer address locations with data, all
addresses must fall within the selected Write-Buffer
Page.
2. DQ7 may change simultaneously with DQ5.
Therefore, DQ7 should be verified.
3. If this flowchart location was reached because
DQ5= “1”, then the device FAILED. If this flowchart
location was reached because DQ1= “1”, then the
Write to Buffer operation was ABORTED. In either
case, the proper reset command must be written
before the device can begin another operation. If
DQ1=1, write the
Write-Buffer-Programming-Abort-Reset
command. if DQ5=1, write the Reset command.
4. See Ta bl e 1 0 and Ta b le 1 1 for command sequences
required for write buffer programming.
Read DQ7 - DQ0 with
address = Last Loaded
Address
(Note 2)
(Note 3)
DQ7 = Data?
No
FAIL or ABORTPASS
Ye s
Figure 4. Write Buffer Programming Operation
32Am29LV128MH/L25270C7 January 31, 2007
Page 33
DATA SHEET
START
Write Program
Command Sequence
Data Poll
Embedded
Program
algorithm
in progress
Increment Address
Note: See Ta bl e 1 0 and Tab l e 1 1 for program command
sequence.
No
from System
Verify Data?
Yes
Last Address?
Yes
Programming
Completed
No
Figure 5. Program Operation
Program Suspend/Program Resume
Command Sequence
The Program Suspend command allows the system to
interrupt a programming operation or a Write to Buffer
programming operation so that data can be read from
any non-suspended sector. When the Program Suspend command is written during a programming process, the device halts the program operation within 15
μs maximum (5 μs typical) and updates the status bits.
Addresses are not required when writing the Program
Suspend command.
After the programming operation has been suspended, the system can read array data from any
non-suspended sector. The Program Suspend command may also be issued during a programming operation while an erase is suspended. In this case, data
may be read from any addresses not in Erase Suspend or Program Suspend. If a read is needed from
the Secured Silicon Sector area (One-time Program
area), then user must use the proper command sequences to enter and exit this region.
The system may also write the autoselect command
sequence when the device is in the Program Suspend
mode. The system can read as many autoselect codes
as required. When the device exits the autoselect
mode, the device reverts to the Program Suspend
mode, and is ready for another valid operation. See
Autoselect Command Sequence for more information.
After the Program Resume command is written, the
device reverts to programming. The system can determine the status of the program operation using the
DQ7 or DQ6 status bits, just as in the standard program operation. See “Write Operation Status” on
page 39 for more information.
The system must write the Program Resume command to exit the Program Suspend mode and continue
the programming operation. Further writes of the Resume command are ignored. Another Program Suspend command can be written after the device has
resume programming.
January 31, 2007 25270C7Am29LV128MH/L33
Page 34
Program Operation
r
or Write-to-Buffer
Sequence in Progress
Write address/data
XXXh/B0h
Wait 15 μs
Read data as
required
No
reading?
Done
DATA SHEET
Write Program Suspend
Command Sequence
Command is also valid for
Erase-suspended-program
operations
Autoselect and SecSi Sector
read operations are also allowed
Data cannot be read from erase- o
program-suspended sectors
When the Embedded Erase algorithm is complete, the
device returns to the read mode and addresses are no
longer latched. The system can determine the status
of the erase operation by using DQ7, DQ6, or DQ2.
See “Write Operation Status” on page 39 for information on these status bits.
Any commands written during the chip erase operation
are ignored.However, note that a hardware reset im-
mediately terminates the erase operation. If that occurs, the chip erase command sequence should be
reinitiated once the device has returned to reading
array data, to ensure data integrity. Note that the Se-
cured Silicon Sector, autoselect, and CFI functions are
unavailable when an program operation is in progress.
Figure 6 illustrates the algorithm for the erase operation. Refer to the Erase and Program Operations ta-
bles in the AC Characteristics section for parameters,
and Figure 20 section for timing diagrams.
Yes
Write address/data
XXXh/30h
Device reverts to
operation prior to
Program Suspend
Write Program Resume
Command Sequence
Figure 6. Program Suspend/Program Resume
Chip Erase Command Sequence
Chip erase is a six bus cycle operation. The chip erase
command sequence is initiated by writing two unlock
cycles, followed by a set-up command. Two additional
unlock write cycles are then followed by the chip erase
command, which in turn invokes the Embedded Erase
algorithm. The device does not require the system to
preprogram prior to erase. The Embedded Erase algorithm automatically preprograms and verifies the entire
memory for an all zero data pattern prior to electrical
erase. The system is not required to provide any controls or timings during these operations. Ta bl e 1 0 and
Ta bl e 1 1 show the address and data requirements for
the chip erase command sequence.
Sector Erase Command Sequence
Sector erase is a six bus cycle operation. The sector
erase command sequence is initiated by writing two
unlock cycles, followed by a set-up command. Two additional unlock cycles are written, and are then followed by the address of the sector to be erased, and
the sector erase command. Ta bl e 9 and Ta bl e 1 0 show
the address and data requirements for the sector
erase command sequence.
The device does not require the system to preprogram
prior to erase. The Embedded Erase algorithm automatically programs and verifies the entire memory for
an all zero data pattern prior to electrical erase. The
system is not required to provide any controls or timings during these operations.
After the command sequence is written, a sector erase
time-out of 50 µs occurs. During the time-out period,
additional sector addresses and sector erase commands 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 erasure may begin. Any sector erase address and command following the exceeded time-out
may or may not be accepted. It is recommended that
processor interrupts be disabled during this time to ensure all commands are accepted. The interrupts can
be re-enabled after the last Sector Erase command is
written. Any command other than Sector Erase or
Erase Suspend during the time-out period resets
the device to the read mode. The system must re-
write the command sequence and any additional addresses and commands. Note that the Secured Silicon
Sector, autoselect, and CFI functions are unavailable
when an erase operation is in progress.
34Am29LV128MH/L25270C7 January 31, 2007
Page 35
DATA SHEET
The system can monitor DQ3 to determine if the sector erase timer has timed out (See the section on DQ3:
Sector Erase Timer.). The time-out begins from the rising edge of the final WE# pulse in the command
sequence.
When the Embedded Erase algorithm is complete, the
device returns to reading array data and addresses
are no longer latched. The system can determine the
status of the erase operation by reading DQ7, DQ6, or
DQ2 in the erasing sector. See “Write Operation Sta-
tus” on page 39 for information on these status bits.
Once the sector erase operation has begun, only the
Erase Suspend command is valid. All other commands are ignored. However, note that a hardwarereset immediately terminates the erase operation. If
that occurs, the sector erase command sequence
should be reinitiated once the device has returned to
reading array data, to ensure data integrity.
Figure 6 illustrates the algorithm for the erase operation. Refer to the Erase and Program Operations ta-
bles in the AC Characteristics section for parameters,
and Figure 20 section for timing diagrams.
Erase Suspend/Erase Resume
Commands
The Erase Suspend command, B0h, allows the system to interrupt a sector erase operation and then read
data from, or program data to, any sector not selected
for erasure. This command is valid only during the sector erase operation, including the 50 µs time-out period during the sector erase command sequence. The
Erase Suspend command is ignored if written during
the chip erase operation or Embedded Program
algorithm.
When the Erase Suspend command is written during
the sector erase operation, the device requires a typical of 5 µs (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 terminates the time-out period and
suspends the erase operation.
After the erase operation has been suspended, the
device enters the erase-suspend-read mode. The system can read data from or program data to any sector
not selected for erasure. (The device “erase suspends” all sectors selected for erasure.) Reading at
any address within erase-suspended sectors produces status information on DQ7–DQ0. The system
can use DQ7, or DQ6 and DQ2 together, to determine
if a sector is actively erasing or is erase-suspended.
See “Write Operation Status” on page 39 for information on these status bits.
After an erase-suspended program operation is complete, the device returns to the erase-suspend-read
mode. The system can determine the status of the
program operation using the DQ7 or DQ6 status bits,
just as in the standard word program operation. See
“Write Operation Status” on page 39 for more informa-
tion.
In the erase-suspend-read mode, the system can also
issue the autoselect command sequence. Refer to the
Autoselect Mode and Autoselect Command Sequence
sections for details.
To resume the sector erase operation, the system
must write the Erase Resume command. Further
writes of the Resume command are ignored. Another
Erase Suspend command can be written after the chip
has resumed erasing.
Note: During an erase operation, this flash device performs multiple internal operations which are invisible
to the system. When an erase operation is suspended,
any of the internal operations that were not fully completed must be restarted. As such, if this flash device
is continually issued suspend/resume commands in
rapid succession, erase progress will be impeded as a
function of the number of suspends. The result will be
a longer cumulative erase time than without suspends.
Note that the additional suspends do not affect device
reliability or future performance. In most systems rapid
erase/suspend activity occurs only briefly. In such
cases, erase performance will not be significantly impacted.
January 31, 2007 25270C7Am29LV128MH/L35
Page 36
START
Write Erase
Command Sequence
(Notes 1, 2)
Data Poll to Erasing
Bank from System
No
Data = FFh?
Erasure Completed
DATA SHEET
Embedded
Erase
algorithm
in progress
Yes
Figure 7. Erase Operation
Notes:
1. See Ta b le 1 0 and Tab l e 1 1 for erase command
sequence.
2. See the section on DQ3 for information on the sector
erase timer.
X = Don’t care
RA = Read Address of the memory location to be read.
RD = Read Data read from location RA during read operation.
PA = Program Address. Addresses latch on the falling edge of the WE#
or CE# pulse, whichever happens later.
PD = Program Data for location PA. Data latches on the rising edge of
WE# or CE# pulse, whichever happens first.
FirstSecond Third Fourth Fifth Sixth
Cycles
Addr DataAddrDataAddrDataAddrDataAddr Data Addr Data
4555AA2AA5555590X03(Note 10)
4555AA2AA5555590(SA)X0200/01
Bus Cycles (Notes 2–5)
SA = Sector Address of sector to be verified (in autoselect mode) or
erased. Address bits A22–A15 uniquely select any sector.
WBL = Write Buffer Location. Address must be within the same write
buffer page as PA.
WC = Word Count. Number of write buffer locations to load minus 1.
Notes:
1. See Ta b l e 1 for description of bus operations.
2. All values are in hexadecimal.
3. Except for the read cycle and the fourth cycle of the autoselect
command sequence, all bus cycles are write cycles.
4. Data bits DQ15–DQ8 are don’t care in command sequences,
except for RD, PD, and WC.
5. Unless otherwise noted, address bits A22–A11 are don’t cares.
6. No unlock or command cycles required when device is in read
mode.
7. The Reset command is required to return to the read mode (or to
the erase-suspend-read mode if previously in Erase Suspend)
when the device is in the autoselect mode, or if DQ5 goes high
while the device is providing status information.
8. The fourth cycle of the autoselect command sequence is a read
cycle. Data bits DQ15–DQ8 are don’t care. See the Autoselect
Command Sequence section for more information.
9. The device ID must be read in three cycles.
10. If WP# protects the highest address sector, the data is 98h for
factory locked and 18h for not factory locked. If WP# protects the
lowest address sector, the data is 88h for factory locked and 08h
for not factor locked.
11. The total number of cycles in the command sequence is
determined by the number of words written to the write buffer. The
maximum number of cycles in the command sequence is 21.
12. The data is 00h for an unprotected sector and 01h for a protected
sector.
13. Command sequence resets device for next command after
aborted write-to-buffer operation.
14. The Unlock Bypass command is required prior to the Unlock
Bypass Program command.
15. The Unlock Bypass Reset command is required to return to the
read mode when the device is in the unlock bypass mode.
16. The system may read and program in non-erasing sectors, or
enter the autoselect mode, when in the Erase Suspend mode.
The Erase Suspend command is valid only during a sector erase
operation.
17. The Erase Resume command is valid only during the Erase
Suspend mode.
18. Command is valid when device is ready to read array data or when
device is in autoselect mode.
X = Don’t care
RA = Read Address of the memory location to be read.
RD = Read Data read from location RA during read operation.
PA = Program Address. Addresses latch on the falling edge of the WE#
or CE# pulse, whichever happens later.
PD = Program Data for location PA. Data latches on the rising edge of
WE# or CE# pulse, whichever happens first.
FirstSecond Third Fourth Fifth Sixth
Cycles
Addr DataAddrDataAddrDataAddrDataAddr Data Addr Data
4AAAAA55555AAA90X06(Note 10)
4AAAAA55555AAA90(SA)X0400/01
Bus Cycles (Notes 2–5)
SA = Sector Address of sector to be verified (in autoselect mode) or
erased. Address bits A22–A15 uniquely select any sector.
WBL = Write Buffer Location. Address must be within the same write
buffer page as PA.
BC = Byte Count. Number of write buffer locations to load minus 1.
Notes:
1. See Ta b l e 1 for description of bus operations.
2. All values are in hexadecimal.
3. Except for the read cycle and the fourth cycle of the autoselect
command sequence, all bus cycles are write cycles.
4. Data bits DQ15–DQ8 are don’t care in command sequences,
except for RD and PD.
5. Unless otherwise noted, address bits A22–A11 are don’t cares.
6. No unlock or command cycles required when device is in read
mode.
7. The Reset command is required to return to the read mode (or to
the erase-suspend-read mode if previously in Erase Suspend)
when the device is in the autoselect mode, or if DQ5 goes high
while the device is providing status information.
8. The fourth cycle of the autoselect command sequence is a read
cycle. Data bits DQ15–DQ8 are don’t care. See the Autoselect
Command Sequence section for more information.
9. The device ID must be read in three cycles.
10. If WP# protects the highest address sector, the data is 98h for
factory locked and 18h for not factory locked. If WP# protects the
lowest address sector, the data is 88h for factory locked and 08h
for not factor locked.
11. The total number of cycles in the command sequence is
determined by the number of words written to the write buffer. The
maximum number of cycles in the command sequence is 37.
12. The data is 00h for an unprotected sector group and 01h for a
protected sector group.
13. Command sequence resets device for next command after
aborted write-to-buffer operation.
14. The Unlock Bypass command is required prior to the Unlock
Bypass Program command.
15. The Unlock Bypass Reset command is required to return to the
read mode when the device is in the unlock bypass mode.
16. The system may read and program in non-erasing sectors, or
enter the autoselect mode, when in the Erase Suspend mode.
The Erase Suspend command is valid only during a sector erase
operation.
17. The Erase Resume command is valid only during the Erase
Suspend mode.
18. Command is valid when device is ready to read array data or when
device is in autoselect mode.
38Am29LV128MH/L25270C7 January 31, 2007
Page 39
DATA SHEET
WRITE OPERATION STATUS
The device provides several bits to determine the status of a
program or erase operation: DQ2, DQ3, DQ5, DQ6, and
DQ7. Ta b le 1 2 and the following subsections describe the
function of these bits. DQ7 and DQ6 each offer a method for
determining whether a program or erase operation is complete or in progress. The device also provides a hardware-based output signal, RY/BY#, to determine
whether an Embedded Program or Erase operation is
in progress or has been completed.
DQ7: Data# Polling
The Data# Polling bit, DQ7, indicates to the host system
whether an Embedded Program or Erase algorithm is in
progress or completed, or whether the device is in Erase
Suspend. Data# Polling is valid after the rising edge of the
final WE# pulse in the command sequence.
During the Embedded Program algorithm, the device outputs on DQ7 the complement of the datum programmed to
DQ7. This DQ7 status also applies to programming during
Erase Suspend. When the Embedded Program algorithm is
complete, the device outputs the datum programmed to
DQ7. The system must provide the program address to
read valid status information on DQ7. If a program address
falls within a protected sector, Data# Polling on DQ7 is active for approximately 1 µs, then the device returns to the
read mode.
valid data, the data outputs on DQ0–DQ6 may be still
invalid. Valid data on DQ0–DQ7 will appear on successive read cycles.
Ta bl e 1 2 shows the outputs for Data# Polling on DQ7.
Figure 8 shows the Data# Polling algorithm. Figure 21
in the AC Characteristics section shows the Data#
Polling timing diagram.
START
Read DQ7–DQ0
Addr = VA
Yes
No
DQ7 = Data?
No
DQ5 = 1?
During the Embedded Erase algorithm, Data# Polling
produces a “0” on DQ7. When the Embedded Erase
algorithm is complete, or if the device enters the Erase
Suspend mode, Data# Polling produces a “1” on DQ7.
The system must provide an address within any of the
sectors selected for erasure to read valid status information on DQ7.
After an erase command sequence is written, if all
sectors selected for erasing are protected, Data# Polling on DQ7 is active for approximately 100 µs, then the
device returns to the read mode. If not all selected
sectors are protected, the Embedded Erase algorithm
erases the unprotected sectors, and ignores the selected sectors that are protected. However, if the system reads DQ7 at an address within a protected
sector, the status may not be valid.
Just prior to the completion of an Embedded Program
or Erase operation, DQ7 may change asynchronously
with DQ0–DQ6 while Output Enable (OE#) is asserted
low. That is, the device may change from providing
status information to valid data on DQ7. Depending on
when the system samples the DQ7 output, it may read
the status or valid data. Even if the device has completed the program or erase operation and DQ7 has
Yes
Read DQ7–DQ0
Addr = VA
DQ7 = Data?
No
FAIL
Notes:
1. VA = Valid address for programming. During a sector
erase operation, a valid address is any sector address
within the sector being erased. During chip erase, a
valid address is any non-protected sector address.
2. DQ7 should be rechecked even if DQ5 = “1” because
DQ7 may change simultaneously with DQ5.
Yes
PASS
Figure 8. Data# Polling Algorithm
January 31, 2007 25270C7Am29LV128MH/L39
Page 40
DATA SHEET
RY/BY#: Ready/Busy#
The RY/BY# is a dedicated, open-drain output pin
which indicates whether an Embedded Algorithm is in
progress or complete. The RY/BY# status is valid after
the rising edge of the final WE# pulse in the command
sequence. Since RY/BY# is an open-drain output, several RY/BY# pins can be tied together in parallel with a
pull-up resistor to V
If the output is low (Busy), the device is actively erasing or programming. (This includes programming in
the Erase Suspend mode.) If the output is high
(Ready), the device is in the read mode, the standby
mode, or in the erase-suspend-read mode. Tab le 12
shows the outputs for RY/BY#.
CC
.
DQ6: Toggle Bit I
Toggle Bit I on DQ6 indicates whether an Embedded
Program or Erase algorithm is in progress or complete, or whether the device has entered the Erase
Suspend mode. Toggle Bit I may be read at any address, and is valid after the rising edge of the final
WE# pulse in the command sequence (prior to the
program or erase operation), and during the sector
erase time-out.
During an Embedded Program or Erase algorithm operation, successive read cycles to any address cause
DQ6 to toggle. The system may use either OE# or
CE# to control the read cycles. When the operation is
complete, DQ6 stops toggling.
After an erase command sequence is written, if all sectors
selected for erasing are protected, DQ6 toggles for approximately 100 µs, then returns to reading array data. If not all
selected sectors are protected, the Embedded Erase algorithm erases the unprotected sectors, and ignores the selected sectors that are protected.
The system can use DQ6 and DQ2 together to determine
whether a sector is actively erasing or is erase-suspended.
When the device is actively erasing (that is, the Embedded
Erase algorithm is in progress), DQ6 toggles. When the device enters the Erase Suspend mode, DQ6 stops toggling.
However, the system must also use DQ2 to determine
which sectors are erasing or erase-suspended. Alternatively, the system can use DQ7. See “DQ7: Data# Polling”
on page 39.
If a program address falls within a protected sector,
DQ6 toggles for approximately 1 μs after the program
command sequence is written, then returns to reading
array data.
DQ6 also toggles during the erase-suspend-program
mode, and stops toggling once the Embedded Program algorithm is complete.
Ta bl e 1 2 shows the outputs for Toggle Bit I on DQ6.
Figure 9 shows the toggle bit algorithm. Figure 22 in
the “AC Characteristics” section shows the toggle bit
timing diagrams. Figure 23 shows the differences between DQ2 and DQ6 in graphical form. See “DQ2:
Toggle Bit II” on page 41.
40Am29LV128MH/L25270C7 January 31, 2007
Page 41
No
START
Read DQ7–DQ0
Read DQ7–DQ0
Toggle Bit
= Toggle?
Yes
DQ5 = 1?
Yes
No
DATA SHEET
DQ2: Toggle Bit II
The “Toggle Bit II” on DQ2, when used with DQ6, indicates whether a particular sector is actively erasing
(that is, the Embedded Erase algorithm is in progress),
or whether that sector is erase-suspended. Toggle Bit
II is valid after the rising edge of the final WE# pulse in
the command sequence.
DQ2 toggles when the system reads at addresses
within those sectors that have been selected for erasure. (The system may use either OE# or CE# to control the read cycles.) But DQ2 cannot distinguish
whether the sector is actively erasing or is erase-suspended. DQ6, by comparison, indicates whether the
device is actively erasing, or is in Erase Suspend, but
cannot distinguish which sectors are selected for erasure. Thus, both status bits are required for sector and
mode information. Refer to Tab le 1 2 to compare outputs for DQ2 and DQ6.
Figure 9 shows the toggle bit algorithm in flowchart
form, and “DQ2: Toggle Bit II” explains the algorithm.
See also the “RY/BY#: Ready/Busy#” subsection.
Figure 22 shows the toggle bit timing diagram.
Figure 23 shows the differences between DQ2 and
DQ6 in graphical form.
Read DQ7–DQ0
Twice
Toggle Bit
= Toggle?
Yes
Program/Erase
Operation Not
Complete, Write
Reset Command
Note: The system should recheck the toggle bit even if
DQ5 = “1” because the toggle bit may stop toggling as DQ5
changes to “1.” See the subsections on DQ6 and DQ2 for
more information.
No
Program/Erase
Operation Complete
Figure 9. Toggle Bit Algorithm
Reading Toggle Bits DQ6/DQ2
Refer to Figure 9 for the following discussion. Whenever the system initially begins reading toggle bit status, it must read DQ7–DQ0 at least twice in a row to
determine whether a toggle bit is toggling. Typically,
the system would note and store the value of the toggle bit after the first read. After the second read, the
system would compare the new value of the toggle bit
with the first. If the toggle bit is not toggling, the device
has completed the program or erase operation. The
system can read array data on DQ7–DQ0 on the following read cycle.
However, if after the initial two read cycles, the system
determines that the toggle bit is still toggling, the system also should note whether the value of DQ5 is high
(see the section on DQ5). If it is, the system should
then determine again whether the toggle bit is toggling, since the toggle bit may have stopped toggling
just as DQ5 went high. If the toggle bit is no longer
toggling, the device has successfully completed the
program or erase operation. If it is still toggling, the device did not completed the operation successfully, and
the system must write the reset command to return to
reading array data.
The remaining scenario is that the system initially determines that the toggle bit is toggling and DQ5 has
not gone high. The system may continue to monitor
the toggle bit and DQ5 through successive read cycles, determining the status as described in the previous paragraph. Alternatively, it may choose to perform
January 31, 2007 25270C7Am29LV128MH/L41
Page 42
DATA SHEET
other system tasks. In this case, the system must start
at the beginning of the algorithm when it returns to determine the status of the operation (top of Figure 9).
DQ5: Exceeded Timing Limits
DQ5 indicates whether the program, erase, or
write-to-buffer time has exceeded a specified internal
pulse count limit. Under these conditions DQ5 produces a
“1,” indicating that the program or erase cycle was not successfully completed.
The device may output a “1” on DQ5 if the system tries
to program a “1” to a location that was previously programmed to “0.” Only an erase operation canchange a “0” back to a “1.” Under this condition, the
device halts the operation, and when the timing limit
has been exceeded, DQ5 produces a “1.”
In all these cases, the system must write the reset
command to return the device to the reading the array
(or to erase-suspend-read if the device was previously
in the erase-suspend-program mode).
DQ3: Sector Erase Timer
After writing a sector erase command sequence, the
system may read DQ3 to determine whether or not
erasure has begun. (The sector erase timer does not
apply to the chip erase command.) If additional
sectors are selected for erasure, the entire time-out
also applies after each additional sector erase com-
mand. When the time-out period is complete, DQ3
switches from a “0” to a “1.” If the time between additional sector erase commands from the system can be
assumed to be less than 50 µs, the system need not
monitor DQ3. See “Sector Erase Command Se-
quence” on page 34.
After the sector erase command is written, the system
should read the status of DQ7 (Data# Polling) or DQ6
(Toggle Bit I) to ensure that the device has accepted
the command sequence, and then read DQ3. If DQ3 is
“1,” the Embedded Erase algorithm has begun; all further commands (except Erase Suspend) are ignored
until the erase operation is complete. If DQ3 is “0,” the
device will accept additional sector erase commands.
To ensure the command has been accepted, the system software should check the status of DQ3 prior to
and following each subsequent sector erase command. If DQ3 is high on the second status check, the
last command might not have been accepted.
Ta bl e 1 2 shows the status of DQ3 relative to the other
status bits.
DQ1: Write-to-Buffer Abort
DQ1 indicates whether a Write-to-Buffer operation
was aborted. Under these conditions DQ1 produces a
“1”. The system must issue the
Write-to-Buffer-Abort-Reset command sequence to return the device to reading array data. See “Write Buffer
Programming” on page 30 for more details.
42Am29LV128MH/L25270C7 January 31, 2007
Page 43
DATA SHEET
Table 12. Write Operation Status
DQ7
Status
Standard
Mode
Program
Suspend
Mode
Erase
Suspend
Mode
Write-to-
Buffer
Notes:
1. DQ5 switches to ‘1’ when an Embedded Program, Embedded Erase, or Write-to-Buffer operation has exceeded the
maximum timing limits. Refer to the section on DQ5 for more information.
2. DQ7 and DQ2 require a valid address when reading status information. Refer to the appropriate subsection for further details.
3. The Data# Polling algorithm should be used to monitor the last loaded write-buffer address location.
4. DQ1 switches to ‘1’ when the device has aborted the write-to-buffer operation.
Embedded Program AlgorithmDQ7#Toggle0N/ANo toggle00
Embedded Erase Algorithm0Toggle01ToggleN/A0
with Power Applied. . . . . . . . . . . . . . –65°C to +125°C
Voltage with Respect to Ground
V
(Note 1) . . . . . . . . . . . . . . . . . –0.5 V to +4.0 V
CC
V
. . . . . . . . . . . . . . . . . . . . . . . . . –0.5 V to +4.0 V
IO
A9, OE#, ACC, and RESET#
(Note 2) . . . . . . . . . . . . . . . . . . . . –0.5 V to +12.5 V
All other pins (Note 1) . . . . . . –0.5 V to V
Output Short Circuit Current (Note 3) . . . . . . 200 mA
Notes:
1. Minimum DC voltage on input or I/O pins is –0.5 V.
During voltage transitions, input or I/O pins may
overshoot V
Maximum DC voltage on input or I/O pins is V
See Figure 10. During voltage transitions, input or I/O
pins may overshoot to V
See Figure 11.
2. Minimum DC input voltage on pins A9, OE#, ACC, and
RESET# is –0.5 V. During voltage transitions, A9, OE#,
ACC, and RESET# may overshoot V
periods of up to 20 ns. See Figure 10. Maximum DC
input voltage on pin A9, OE#, ACC, and RESET# is
+12.5 V which may overshoot to +14.0 V for periods up
to 20 ns.
3. No more than one output may be shorted to ground at a
time. Duration of the short circuit should not be greater
than one second.
Stresses above those listed under “Absolute Maximum
Ratings” may cause permanent damage to the device. This
is a stress rating only; functional operation of the device at
these or any other conditions above those indicated in the
operational sections of this data sheet is not implied.
Exposure of the device to absolute maximum rating
conditions for extended periods may affect device reliability.
to –2.0 V for periods of up to 20 ns.
SS
+2.0 V for periods up to 20 ns.
CC
SS
+0.5 V
CC
+0.5 V.
CC
to –2.0 V for
+0.8 V
–0.5 V
–2.0 V
V
+2.0 V
V
+0.5 V
2.0 V
20 ns
20 ns
Figure 10. Maximum Negative
Overshoot Waveform
20 ns
CC
CC
20 ns
Figure 11. Maximum Positive
Overshoot Waveform
20 ns
20 ns
OPERATING RANGES
Industrial (I) Devices
Ambient Temperature (TA) . . . . . . . . . . . . . . –40°C to +85°C
1. Operating ranges define those limits between which the
functionality of the device is guaranteed.
2. See “Ordering Information” on page 10 for valid VCC/VIO
range combinations. The I/Os will not operate at 3V when
= 1.8V.
V
IO
3. 100R parts have a V
44Am29LV128MH/L25270C7 January 31, 2007
range from 2.7–3.6 V.
IO
Page 45
DC CHARACTERISTICS
CMOS Compatible
DATA SHEET
Parameter
Symbol
I
LI
I
LIT
I
LO
I
LR
I
CC1
I
CC2
I
CC3
I
CC4
I
CC5
I
CC6
I
CC7
V
IL1
V
IH1
V
IL2
V
IH2
V
HH
V
ID
V
OL
V
OH1
V
OH2
V
LKO
Parameter Description
(Notes)
= VSS to VCC,
V
Input Load Current (1)
V
IN
= VCC
CC
A9, ACC Input Load CurrentVCC = V
V
Output Leakage Current
OUT
= V
V
CC
Reset Leakage CurrentVCC = V
VCC Active Read Current
(2, 3)
CE# = V
Test Conditions MinTypMaxUnit
max
; A9 = 12.5 V35µA
CC max
= VSS to VCC,
CC max
; RESET# = 12.5 V35µA
CC max
5 MHz334
OE# = VIH,
IL,
1 MHz1343
±1.0µA
±1.0µA
mA
1 MHz450
V
Initial Page Read Current (2, 3) CE# = V
CC
OE# = V
IL,
IH
mA10 MHz4080
10 MHz320
V
Intra-Page Read Current (2, 3)CE# = V
CC
VCC Active Write Current (3, 4)CE# = V
VCC Standby Current (3)CE#, RESET# = VCC ± 0.3 V, WP# = V
VCC Reset Current (3)RESET# = V
V
= V
Automatic Sleep Mode (3, 5)
IH
WP# = V
OE# = V
IL,
OE# = V
IL,
± 0.3 V; V
CC
IH
IH
IH
± 0.3 V, WP# = V
SS
= V
IL
SS
33 MHz640mA
5060mA
IH
IH
± 0.3 V,
15µA
15µA
15µA
Input Low Voltage 1(6, 7)–0.50.8V
+
V
Input High Voltage 1 (6, 7)1.9
CC
0.5
Input Low Voltage 2 (6, 8)–0.50.3 x VIOV
Input High Voltage 2 (6, 8)1.9VIO + 0.5V
Voltage for ACC Program
Acceleration
Voltage for Autoselect and
Temporary Sector Unprotect
Output Low Voltage (10)IOL = 4.0 mA, VCC = V
Output High Voltage
= 2.7–3.6 V11.512.5V
V
CC
V
= 2.7–3.6 V11.512.5V
CC
0.15 x
V
= –2.0 mA, VCC = V
I
OH
IOH = –100 µA, VCC = V
CC min
CC min
CC min
= V
= V
= V
IO
IO
IO
0.85 V
IO
VIO–0.4V
IO
Low VCC Lock-Out Voltage (9)2.32.5V
V
V
V
Notes:
1. On the WP#/ACC pin only, the maximum input load current when
WP# = V
2. The ICC current listed is typically less than 2 mA/MHz, with OE# at
V
3. Maximum I
4. I
CC
progress.
is ± 5.0 µA.
IL
.
IH
specifications are tested with VCC = VCCmax.
CC
active while Embedded Erase or Embedded Program is in
5. Automatic sleep mode enables the low power mode when
addresses remain stable for t
6. If V
7. V
8. V
9. Not 100% tested.
10. Includes RY/BY#
< VCC, maximum VIL for CE# and DQ I/Os is 0.3 VIO.
IO
Maximum V
voltage requirements.
CC
voltage requirements.
IO
for these connections is VIO + 0.3 V
IH
+ 30 ns.
ACC
January 31, 2007 25270C7Am29LV128MH/L45
Page 46
TEST CONDITIONS
DATA SHEET
3.3 V
Table 13. Test Specifications
Test ConditionAll SpeedsUnit
Device
Under
Te s t
C
L
Note:Diodes are IN3064 or equivalent
6.2 kΩ
Figure 12. Test Setup
KEY TO SWITCHING WAVEFORMS
WAVEFORMINPUTSOUTPUTS
2.7 kΩ
Output Load1 TTL gate
Output Load Capacitance, C
(including jig capacitance)
Input Rise and Fall Times5ns
Input Pulse Levels0.0–3.0V
Input timing measurement
reference levels (See Note)
Output timing measurement
reference levels
Note: If VIO < VCC, the reference level is 0.5 VIO.
Steady
Changing from H to L
L
30pF
1.5 V
0.5 V
IO
V
Don’t Care, Any Change PermittedChanging, State Unknown
Does Not ApplyCenter Line is High Impedance State (High Z)
3.0 V
0.0 V
Note: If VIO < VCC, the input measurement reference level is 0.5 VIO.
1.5 V0.5 V
Figure 13. Input Waveforms and Measurement Levels
Changing from L to H
V
IO
OutputMeasurement LevelInput
46Am29LV128MH/L25270C7 January 31, 2007
Page 47
AC CHARACTERISTICS
Read-Only Operations
DATA SHEET
Param ete r
JEDEC Std.93R
t
AVAVtRC
t
AVQVtACC
t
ELQVtCE
t
GLQVtOE
t
EHQZtDF
t
GHQZtDF
t
AXQXtOH
DescriptionTest Setup
Read Cycle Time (Note 1)Min90100110120ns
Address to Output DelayCE#, OE# = VILMax90100110120ns
Chip Enable to Output Delay OE# = V
t
Page Access TimeMax253030403040ns
PAC C
Output Enable to Output Delay Max253030403040ns
Chip Enable to Output High Z (Note 1) Max16ns
Output Enable to Output High Z (Note 1) Max16ns
Output Hold Time From Addresses, CE# or OE#,
Whichever Occurs First
Output Enable Hold Time
t
OEH
(Note 1)
ReadMin0ns
Toggle and
Data# Polling
Max90100110120ns
IL
Min0ns
Min10ns
Notes:
1. Not 100% tested.
2. See Figure 12 and Ta b l e 1 3 for test specifications.
3. AC Specifications listed are tested with V
= VCC. Contact AMD for information on AC operation with VIO ≠ VCC.
IO
Speed Options
103,
103R113113R123123RUnit
Addresses
CE#
OE#
WE#
Outputs
RESET#
RY/BY#
0 V
t
RC
Addresses Stable
t
ACC
t
RH
t
RH
t
OEH
t
OE
t
CE
HIGH Z
Figure 14. Read Operation Timings
t
OH
Output Valid
t
DF
HIGH Z
January 31, 2007 25270C7Am29LV128MH/L47
Page 48
AC CHARACTERISTICS
DATA SHEET
A22-A2
A1
-
A0*
t
ACC
Aa
Data Bus
CE#
OE#
* Figure shows word mode. Addresses are A1–A-1 for byte mode.
Figure 15. Page Read Timings
Same Page
t
PAC C
Ad
AbAc
t
PAC C
t
PAC C
QaQbQcQd
48Am29LV128MH/L25270C7 January 31, 2007
Page 49
AC CHARACTERISTICS
Hardware Reset (RESET#)
Parameter
DATA SHEET
DescriptionAll Speed OptionsUnitJEDECStd.
t
Ready
t
Ready
t
RESET# Pin Low (During Embedded Algorithms)
to Read Mode (See Note)
RESET# Pin Low (NOT During Embedded
Algorithms) to Read Mode (See Note)
t
RESET# Pulse WidthMin500ns
RP
t
Reset High Time Before Read (See Note)Min50ns
RH
RESET# Low to Standby ModeMin20μs
RPD
t
RY/BY# Recovery TimeMin0ns
RB
Max20μs
Max500ns
Note:
1. Not 100% tested.
2. AC Specifications listed are tested with VIO = VCC. Contact AMD for information on AC operation with VIO ≠ VCC.
RY/BY#
CE#, OE#
t
RH
RESET#
t
RP
t
Ready
Reset Timings NOT during Embedded Algorithms
Reset Timings during Embedded Algorithms
t
Ready
RY/BY#
t
RB
CE#, OE#
RESET#
t
RP
Figure 16. Reset Timings
January 31, 2007 25270C7Am29LV128MH/L49
Page 50
DATA SHEET
AC CHARACTERISTICS
Erase and Program Operations
ParameterSpeed Options
JEDECStd.Description93R103, 103R 113, 113R 123, 123R Unit
t
AVAV
t
AVW L
t
WLAX
t
DVW H
t
WHDX
t
GHWL
t
ELWL
t
WHEH
t
WLWH
t
WHDL
t
WHWH1tWHWH1
t
WHWH2tWHWH2
Notes:
1. Not 100% tested.
2. See the “Erase And Programming Performance” on page 60 for more information.
3. For 1–16 words/1–32 bytes programmed.
4. Effective write buffer specification is based upon a 16-word/32-byte write buffer operation
5. Byte/Word programming specification is based upon a single word/byte programming operation not utilizing the write buffer.
6. AC Specifications listed are tested with V
7. When using the program suspend/resume feature, if the suspend command is issued within t
re-applied upon resuming the programming operation. If the suspend command is issued after t
again prior to reading the status bits upon resuming.
t
Write Cycle Time (Note 1)Min90100110120ns
WC
t
Address Setup TimeMin0ns
AS
t
Address Setup Time to OE# low during toggle bit polling Min15ns
ASO
t
Address Hold TimeMin45ns
AH
Address Hold Time From CE# or OE# high
t
AHT
during toggle bit polling
t
Data Setup TimeMin45ns
DS
t
Data Hold TimeMin0ns
DH
t
Output Enable High during toggle bit pollingMin20ns
OEPH
Read Recovery Time Before Write
t
GHWL
(OE# High to WE# Low)
t
CE# Setup TimeMin0ns
CS
t
CE# Hold TimeMin0ns
CH
t
Write Pulse WidthMin35ns
WP
t
Write Pulse Width HighMin30ns
WPH
Min0ns
Min0ns
Write Buffer Program Operation (Notes 2, 3)Typ240µs
Effective Write Buffer Program Operation
(Notes 2, 4)
Accelerated Effective Write Buffer Program
Operation (Notes 2, 4)
Single Byte/Word
Program Operation (Note 2, 5)
Accelerated Single Byte/Word Programming
Operation (Note 2, 5)
Per ByteTyp7.5
Per WordTyp15
Per ByteTyp6.25µs
Per WordTyp12.5µs
ByteTyp60
WordTyp60
ByteTyp54µs
WordTyp54µs
Sector Erase Operation (Note 2)Typ0.5sec
t
VHHVHH
t
VCSVCC
t
BUSY
t
POLL
Rise and Fall Time (Note 1)Min250ns
Setup Time (Note 1)Min50µs
Erase/Program Valid to RY/BY# DelayMax90ns
Program Valid Before Status Polling (Note 7)Max4µs
= VCC. Contact AMD for information on AC operation with VIO ≠ VCC.
IO
, t
POLL
POLL
must be fully
POLL
, t
is not required
POLL
µs
µs
50Am29LV128MH/L25270C7 January 31, 2007
Page 51
RY/BY#
CE#, OE#
RESET#
RY/BY#
DATA SHEET
t
RH
t
RP
t
Ready
Reset Timings NOT during Embedded Algorithms
Reset Timings during Embedded Algorithms
t
Ready
t
RB
CE#, OE#
RESET#
t
RP
Figure 17. Reset Timings
January 31, 2007 25270C7Am29LV128MH/L51
Page 52
AC CHARACTERISTICS
DATA SHEET
Addresses
CE#
OE#
WE#
Data
RY/BY#
V
CC
Program Command Sequence (last two cycles)
DH
t
AS
PAPA
t
CH
t
WPH
t
WC
555h
t
CS
t
WP
t
DS
t
A0h
t
VCS
Read Status Data (last two cycles)
PA
t
AH
t
POLL
t
WHWH1
PD
t
BUSY
Status
D
OUT
t
RB
otes:
. PA = program address, PD = program data, D
. Illustration shows device in word mode.
Figure 18. Program Operation Timings
V
HH
V
or V
IL
ACC
IHV
t
VHH
Figure 19. Accelerated Program Timing Diagram
is the true data at the program address.
OUT
t
VHH
IL
or V
IH
52Am29LV128MH/L25270C7 January 31, 2007
Page 53
AC CHARACTERISTICS
Erase Command Sequence (last two cycles)Read Status Data
DATA SHEET
t
AS
555h for chip erase
VA
t
AH
VA
Addresses
t
WC
2AAhSA
CE#
t
t
CH
WP
OE#
WE#
Data
t
DH
WPH
30h
10 for Chip Erase
t
BUSY
t
CS
t
DS
t
55h
t
WHWH2
In
Progress
Complete
t
RB
RY/BY#
t
VCS
V
CC
Notes:
1. SA = sector address (for Sector Erase), VA = Valid Address for reading status data. See “Write Operation Status” on page 39.
2. These waveforms are for the word mode.
Figure 20. Chip/Sector Erase Operation Timings
January 31, 2007 25270C7Am29LV128MH/L53
Page 54
AC CHARACTERISTICS
Addresses
t
POLL
CE#
t
CH
OE#
t
WE#
DQ15 and DQ7
OEH
t
ACC
t
t
RC
VA
CE
t
OE
DATA SHEET
VAVA
t
DF
t
OH
Complement
Complement
Tru e
Valid Data
High Z
DQ14–DQ8, DQ6–DQ0
t
BUSY
Status Data
Status Data
Tru e
Valid Data
High Z
RY/BY#
Note: VA = Valid address. Illustration shows first status cycle after command sequence, last status read cycle, and array data
read cycle.
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 22. Toggle Bit Timings (During Embedded Algorithms)
Enter
Embedded
Erasing
WE#
Erase
Erase
Suspend
Erase Suspend
Suspend Program
Read
Enter Erase
Erase
Suspend
Program
Erase Suspend
Read
Erase
Resume
Erase
Erase
Complete
DQ6
DQ2
Note: DQ2 toggles only when read at an address within an erase-suspended sector. The system may use OE# or CE# to toggle
DQ2 and DQ6.
Figure 23. DQ2 vs. DQ6
January 31, 2007 25270C7Am29LV128MH/L55
Page 56
AC CHARACTERISTICS
Temporary Sector Group Unprotect
Parameter
DATA SHEET
All Speed OptionsJEDECStdDescriptionUnit
t
t
VID Rise and Fall Time (See Note)Min500ns
VIDR
RESET# Setup Time for Temporary Sector
RSP
Unprotect
Note:
1. Not 100% tested.
2. AC Specifications listed are tested with V
V
ID
RESET#
VSS, VIL,
or V
IH
t
VIDR
CE#
WE#
t
RSP
Min4µs
= VCC. Contact AMD for information on AC operation with VIO ≠ VCC.
IO
VSS, VIL,
or V
t
VIDR
Program or Erase Command Sequence
t
RRB
V
ID
IH
RY/BY#
Figure 24. Temporary Sector Group Unprotect Timing Diagram
56Am29LV128MH/L25270C7 January 31, 2007
Page 57
AC CHARACTERISTICS
V
ID
V
RESET#
IH
DATA SHEET
SA, A6,
A1, A0
Valid*Valid*Valid*
Sector Group Protect or UnprotectVerify
Data
60h60h40h
Sector Group Protect: 150 µs,
Sector Group Unprotect: 15 ms
1 µs
CE#
WE#
OE#
* For sector group protect, A6 = 0, A1 = 1, A0 = 0. For sector group unprotect, A6 = 1, A1 = 1, A0 = 0.
Figure 25. Sector Group Protect and Unprotect Timing Diagram
Status
January 31, 2007 25270C7Am29LV128MH/L57
Page 58
DATA SHEET
AC CHARACTERISTICS
Alternate CE# Controlled Erase and Program Operations
Write Buffer Program Operation (Notes 2, 3)Typ240µs
Per ByteTyp7.5µs
Per WordTyp15µs
Per ByteTyp6.25µs
Per WordTyp12.5µs
t
WHWH1tWHWH1
Effective Write Buffer Program Operation
(Notes 2, 4)
Accelerated Effective Write Buffer Program
Operation (Notes 2, 4)
Single Word Program Operation (Note 2, 5)Typ60µs
t
WHWH2tWHWH2
t
POLL
Accelerated Single Word Programming Operation
(Note 2, 5)
Sector Erase Operation (Note 2)Typ0.5sec
Program Valid before Status Polling (Note 7)Max4µs
Ty p5 4µ s
Notes:
1. Not 100% tested.
2. See “Erase And Programming Performance” on page 60 for more information.
3. For 1–16 words/1–32 bytes programmed.
4. Effective write buffer specification is based upon a 16-word/32-byte write buffer operation.
5. Word programming specification is based upon a single word programming operation not utilizing the write buffer.
6. AC Specifications listed are tested with V
7. When using the program suspend/resume feature, if the suspend command is issued within t
re-applied upon resuming the programming operation. If the suspend command is issued after t
= VCC. Contact AMD for information on AC operation with VIO ≠ VCC.
IO
, t
POLL
POLL
must be fully
POLL
, t
is not required
POLL
again prior to reading the status bits upon resuming.
58Am29LV128MH/L25270C7 January 31, 2007
Page 59
AC CHARACTERISTICS
DATA SHEET
Addresses
WE#
OE#
CE#
Data
RESET#
555 for program
2AA for erase
t
WC
t
WH
t
WS
t
RH
PA for program
SA for sector erase
555 for chip erase
t
AS
t
t
GHEL
t
CP
t
CPH
t
DS
t
DH
A0A0 for program
5555 for erase
AH
t
POLL
t
WHWH1 or 2
t
BUSY
PD for program
3030 for sector erase
1010 for chip erase
Data# Polling
PA
DQ7#,
DQ15
D
OUT
RY/BY#
Notes:
1. Figure indicates last two bus cycles of a program or erase operation.
2. PA = program address, SA = sector address, PD = program data.
3. DQ7# is the complement of the data written to the device. D
Input voltage with respect to V
(including A9, OE#, and RESET#)
Input voltage with respect to V
VCC Current–100 mA+100 mA
Note: Includes all pins except VCC. Test conditions: VCC = 3.0 V, one pin at a time.
on all pins except I/O pins
SS
on all I/O pins–1.0 VVCC + 1.0 V
SS
–1.0 V12.5 V
January 31, 2007 25270C7Am29LV128MH/L59
Page 60
DATA SHEET
ERASE AND PROGRAMMING PERFORMANCE
ParameterTyp (Note 1)Max (Note 2)UnitComments
Sector Erase Time0.53.5sec
Chip Erase Time128256sec
Single Word Program Time (Note 3)60600µs
Accelerated Single Word Program Time
(Note 3)
Total Write Buffer Program Time (Note 4)2401200µs
Effective Write Buffer Program
Time (Note 5)
Total Accelerated Write Buffer Program Time
(Note 4)
Effective Accelerated Write
Buffer Program Time
(Note 5)
Chip Program Time126292sec
Notes:
1. Typical program and erase times assume the following conditions: 25°C, 3.0 V VCC. Programming specifications assume that
all bits are programmed to 00h.
2. Maximum values are measured at VCC = 3.0, worst case temperature. Maximum values are valid up to and including 100,000
program/erase cycles.
3. Word programming specification is based upon a single word programming operation not utilizing the write buffer.
4. For 1-16 words or 1-32 bytes programmed in a single write buffer programming operation.
5. Effective write buffer specification is based upon a 16-word/32-byte write buffer operation.
6. The typical chip programming time is considerably less than the maximum chip programming time listed, since most words
program faster than the maximum program times listed.
7. In the pre-programming step of the Embedded Erase algorithm, all bits are programmed to 00h before erasure.
8. System-level overhead is the time required to execute the two- or four-bus-cycle sequence for the program command. See
Ta b l e 1 1 for further information on command definitions.
9. The device has a minimum erase and program cycle endurance of 100,000 cycles.
TS056/TSR056—56-Pin Standard/Reverse Thin Small Outline Package (TSOP)
PACKAGE
JEDEC
SYMBOL
A
A1
A2
b1
b
c1
c
D
D1
E
e
L
O
R
N
TS/TSR 56
MO-142 (B) EC
MIN.
---
0.05
0.95
0.50 BASIC
NOM.
---
---
1.00
0.200.230.17
0.220.270.17
---0.160.10
---0.210.10
20.0020.2019.90
18.4018.5018.30
14.0014.1013.90
0.600.700.50
3˚5˚0˚
---0.200.08
56
MAX.
1.20
0.15
1.05
NOTES:
1 CONTROLLING DIMENSIONS ARE IN MILLIMETERS (mm).
(DIMENSIONING AND TOLERANCING CONFORMS TO ANSI Y14.5M-1982.)
2 PIN 1 IDENTIFIER FOR STANDARD PIN OUT (DIE UP).
3 PIN 1 IDENTIFIER FOR REVERSE PIN OUT (DIE DOWN), INK OR LASER MARK.
4 TO BE DETERMINED AT THE SEATING PLANE -C- . THE SEATING PLANE IS
DEFINED AS THE PLANE OF CONTACT THAT IS MADE WHEN THE PACKAGE
LEADS ARE ALLOWED TO REST FREELY ON A FLAT HORIZONTAL SURFACE.
5 DIMENSIONS D1 AND E DO NOT INCLUDE MOLD PROTRUSION. ALLOWABLE
MOLD PROTUSION IS 0.15 mm PER SIDE.
6 DIMENSION b DOES NOT INCLUDE DAMBAR PROTUSION. ALLOWABLE
DAMBAR PROTUSION SHALL BE 0.08 mm TOTAL IN EXCESS OF b
DIMENSION AT MAX MATERIAL CONDITION. MINIMUM SPACE BETWEEN
PROTRUSION AND AN ADJACENT LEAD TO BE 0.07 mm.
7 THESE DIMESIONS APPLY TO THE FLAT SECTION OF THE LEAD BETWEEN
0.10 mm AND 0.25 mm FROM THE LEAD TIP.
8. LEAD COPLANARITY SHALL BE WITHIN 0.10 mm AS MEASURED FROM THE
SEATING PLANE.
9 DIMENSION "e" IS MEASURED AT THE CENTERLINE OF THE LEADS.
3160\38.10A
62Am29LV128MH/L25270C7 January 31, 2007
Page 63
DATA SHEET
PHYSICAL DIMENSIONS
LAA064—64-Ball Fortified Ball Grid Array
13 x 11 mm Package
January 31, 2007 25270C7Am29LV128MH/L63
Page 64
DATA SHEET
REVISION SUMMARY
Revision A (October 3, 2001)
Initial release as abbreviated Advance Information
data sheet.
Revision A+1 (March 20, 2002)
Distinctive Characteristics
Clarified description of Enhanced VersatileIO control.
Product Selector Guide
Removed the 98R, 108, 108R, 118, 118R, 128, and
128R Speed Options.
Replaced Note #2.
Product Selector Guide and Read Only Operations
Added a 30 ns Page Access time and Output Enable
Access time to the 113R and 123R Speed Options.
Ordering Information
Corrected device density in device number/description.
Physical Dimensions
Added drawing that shows both TS056 and TSR056
specifications.
Revision B (July 1, 2002)
Expanded data sheet to full specification version.
Revision B+1 (September 16, 2002)
Distinctive Characteristics, Physical Dimensions
Added 80-Ball Fine-Pitch BGA.
Product Selector Guide
Added 80-Ball Fine-Pitch BGA. Added Note #1. Added
103, 108, 113, 118, 123, 128 regulated OPNs.
Changed all OPNs that end with 4 or 9 to 3 or 8.
Program Suspend/Program Resume Command
Sequence
Changed 1ms to 15μs maximum, with a typical of 5 μs.
Erase Suspend/Erase Resume Commands
Added that the device requires a typical of 5 μs.
Read-Only Operations, Erase Program Operations,
and Alternate CE# Controlled Erase and Program
Operations
Added regulated OPNs. Changed all OPNs that end
with 4 or 9 to 3 or 8.
Revision B+2 (November 11, 2002)
Global
Removed the Enhanced VI/O option and changed it to
VI/O only.
Ordering Information
Modified Order numbers and package markings to reflect the removal of speed options. Modified the V
ranges. Added Notes #1 and #2.
Table 4. Secured Silicon Sector Contents
Added x8 and x16
Operating Ranges
Changed the V
Added V
IO
supply range to 1.65–3.6 V.
IO
(regulated voltage range) and VIO (full volt-
age range).
DC Characteristics
Removed V
, V
V
IL1
, VIH, VOL, and VOH from table and added
IL
, V
, V
IH1
IL2
, VOL, V
IH2
OH1
, and V
from the
OH2
CMOS table in the Am29LV640MH/L datasheet.
Erase and Programming Performance
Changed the typicals and/or maximums of Chip Erase
Time, Sector Erase Time, Effective Write Buffer Program Time, Program Time, and Accelerated Program
Time to TBD.
Customer Lockable: Secured Silicon Sector NOT
Programmed or Protected at the factory.
Added second bullet, Secured Silicon sector-protect
verify text and figure 3.
Secured Silicon Sector Flash Memory Region, and
Enter Secured Silicon Sector/Exit Secured Silicon
Sector Command Sequence
Noted that the ACC function and unlock bypass modes
are not available when the Secured Silicon sector is enabled.
Byte/Word Program Command Sequence, Sector
Erase Command Sequence, and Chip Erase Command Sequence
IO
Distinctive Characteristics
Changed the typical sector erase time to TBD.
Changed the typical write buffer word programming
Noted that the Secured Silicon Sector, autoselect, and
CFI functions are unavailable when a program or
erase operation is in progress.
time to TBD.
64Am29LV128MH/L25270C7 January 31, 2007
Page 65
DATA SHEET
Common Flash Memory Interface (CFI)
Changed wording in last sentence of third paragraph
from, “...the autoselect mode.” to “...reading array
data.” Changed CFI website address
Revision B+3 (December 2, 2002)
Global
Added sector group protection throughout datasheet
and added Table 4.
Product Selector Guide
Added V
Ordering Information
Corrected typos in V
2.
Figure 6. Program Suspend/Program Resume
Change wait time to 15
Operating Ranges
Corrected typos in V
range.
s to table and removed Note #2
IO
ranges. Removed Notes #1 and
IO
μs.
ranges. Removed full voltage
IO
Input values in the t
WHWH
1 and t
2 parameters in
WHWH
the Alternate CE# Controlled Erase and Program Options table that were previously TBD. Also added Note
5.
Erase and Programming Performance
Input values into table that were previously TBD.
Added note 4.
Revision C (May 16, 2003)
Global
Converted to full data sheet version. Modified Secured
Silicon Sector Flash Memory Region section to include ESN references. Changed data sheet title to
Am29LV128MH/L.
Erase and Programming Performance
Input values into table that were previously TBD. Modified notes.
Revision C+1 (June 11, 2003)
Product Selector Guide
Added Note 2 to 113 and 123 speed grades
DC Characteristics
Changed V
IH1
and V
minimum to 1.9. Removed
IH2
typos in notes.
Read-Only Characteristics
Added a 30 ns option to t
and tOE standard in ta-
PAC C
ble. Added note #3.
Hardware Reset, Erase and Program Operations,
Temporary Sector Unprotect, and Alternate CE#
Controlled Erase and Program Operations
Added Note.
Revision B+4 (February 14, 2003)
Distinctive Characteristics
Corrected performance characteristics.
Product Selector Guide
Removed 93R speed option. Added Note 2.
Ordering Information
Corrected Valid Combination to reflect speed option
changes. Added Note.
AC Characteristics
Removed 93, 93R speed option. Added Note.
Input values in the t
the Erase and Program Options table that were previously TBD. Also added notes 5 and 6.
This product has been retired and is not recommended for designs. For new and current designs,
S29GL256N supersedes Am29LV128MH/L and is the
factory-recommended migration path. Please refer to
the S29GL256N datasheet for specifications and ordering information. Availability of this document is retained for reference and historical purposes only.
Revision C7 (January 31, 2007)
Global
Removed Preliminary designation from document.
Changed SecSi Sector to Secured Silicon Sector.
Erase and Program Operations table
Changed t
to a maximum specification.
BUSY
Colophon
The products described in this document are designed, developed and manufactured as contemplated for general use, including without limitation, ordinary industrial use, general office use, personal use, and household use, but are not designed, developed and manufactured as contemplated (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 LLC 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 authorization by the respective government entity will be required for export of those products.