The following document specifie s Spansion me mory prod ucts that are no w offere d by both Adv anced
Micro Devices and Fujitsu. Although the document is marked with the name of the company that originally developed the specification, these products will be offered to customers of both AMD and
Fujitsu.
Continuity of Specifications
There is no change to this datasheet as a result of offering the device as a Spansion product. Any
changes that have been made are the result of normal datasheet improvement and are noted in the
document revision summary, where supported. Futu re routine revisions wi ll occur when appropriate,
and changes will be noted in a revision summary.
Continuity of Ordering Part Numbers
AMD and Fujitsu continue to support exi sting part numbers beg inning with “ Am” an d “MBM”. T o orde r
these products, please use only the Ordering Part Numbers listed in this document.
For More Information
Please contact your local AMD or Fujitsu sales office for additional information about S pansion
memory solutions.
Publication Number 25270 Revision C Amendment +2 Issue Date September 9, 2003
Page 2
THIS PAGE LEFT INTENTIONALLY BLANK.
Page 3
DATASHEET
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
DISTINCTIVE CHARACTERISTICS
™ Control
ARCHITECTURAL ADVANTAGES
■ Single power supply operation
— 3 volt read, erase, and program operations
■ VersatileI/O
— Device generates data output voltages and tolerates
data input voltages on the CE# and DQ
inputs/outputs as determined by the voltage on the
V
■ Manufactured on 0.23 µm MirrorBit process
technology
■ SecSi
— 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
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
time: 16-word/32-byte write buffer reduces overall
programming time for multiple-word updates
■ 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 technical specifications regarding the Products described herein. This Data
Sheet may be revised by subsequent versions or modifications due to changes in technical specifications.
Refer to AMD’s Website (www.amd.com) for the latest information.
Publication# 25270 Rev: C Amendment/2
Issue Date: September 9, 2003
Page 4
DATASHEET
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 the Product Selector Guide and the Ordering Information sections. 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
input, a high-voltage accelerated program
a V
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.
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 com-
mand sequence overhead by requiring only two write
cycles to program data instead of four.
The VersatileI/O™ (V
tem to set the voltage levels that the device generates
) and an I/O voltage range (VIO), as
CC
) control allows the host sys-
IO
and tolerates on the CE# control input and DQ I/Os to
the same voltage level that is asserted on the V
Refer to the Ordering Information section for valid V
IO
pin.
IO
options.
Hardware data protection measures include a low
detector that automatically inhibits write opera-
V
CC
tions during power transitions. The hardware sector
group protection feature disables both program and
erase operations in any combination of sector groups
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 SecSi
™ (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.
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
→MirrorBit→Flash Information→Technical Docu-
tion
→Flash Memory→Product Informa-
mentation. The following is a partial list of documents
closely related to this product:
2Am29LV128MH/LSeptember 9, 2003
MirrorBit™ Flash Memory Write Buffer Programming
and Page Buffer Read
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)
150
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
6Am29LV128MH/LSeptember 9, 2003
Page 9
DATASHEET
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
= 3.0 volt-only single power supply
V
CC
= Output Buffer power
V
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#
September 9, 2003Am29LV128MH/L7
Page 10
DATASHEET
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
I = Industrial (–40
PAC KA G E 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
1101.65–3.6 V
1201.65–3.6 V
Valid Combinations
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
L128MH93N
L128ML93N
L128MH103N
L128ML103N
L128MH113N
L128ML113N
L128MH123N
L128ML123N
I
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 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 SecSi 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 pacakges, 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.
)
8Am29LV128MH/LSeptember 9, 2003
Page 11
DATASHEET
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. Table 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
Addresses
OperationCE#OE# WE# RESET#WP#ACC
ReadLLHH
Write (Program/Erase)LHLH(Note 3)XA
Accelerated ProgramLHLH
±
V
Standby
Output DisableLHHH
ResetXXXL
Sector Group Protect
(Note 2)
Sector Group Unprotect
(Note 2)
Temp orary Sector Grou p
Unprotect
CC
0.3 V
XX
LHL V
LHL V
XXX V
V
CC
0.3 V
±
ID
ID
ID
XX
(Note 3)V
HH
XH
XX
XX
HX
HX
HX A
(Note 2)
SA, A6 =L,
A3=L, A2=L,
A1=H, A0=L
SA, A6=H,
A3=L, A2=L,
A1=H, A0=L
DQ0–
DQ7
A
IN
IN
A
IN
X
X
X
D
(Note 4) (Note 4)
(Note 4) (Note 4)
High-ZHigh-ZHigh-Z
High-ZHigh-ZHigh-Z
High-ZHigh-ZHigh-Z
(Note 4)XX
(Note 4)XX
IN
(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.5 V, VHH = 11.5–12.5 V, 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
SecSi 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#.
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
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
level that is asserted on V
options on this device.
for V
IO
. See Ordering Information
IO
September 9, 2003Am29LV128MH/L9
Page 12
DATASHEET
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. Refer
to the AC Read-Only Operations table for timing specifications and to Figure 14 for the timing diagram. Refer
to the DC Characteristics table 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
and subsequent page read accesses (as long as
t
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/Byte Program Command Sequence” section
has details on programming data to the device using
, and OE# to VIH.
IL
both standard and Unlock Bypass command se-
quences.
An erase operation can erase one sector, multiple sec-
tors, or the entire device. Table 2 indicates the address
space that each sector occupies.
Refer to the DC Characteristics table for the active
current specification for the write mode. The AC Char-
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 prima-
rily 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 re-
duce the time required for program operations. The
system would use a two-cycle program command se-
quence as required by the Unlock Bypass mode. Re-
moving V
to normal operation.
not be at V
from the WP#/ACC pin returns the device
HH
Note that the WP#/ACC pin must
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 se-
quence, the device enters the autoselect mode. The
system can then read autoselect codes from the inter-
nal register (which is separate from the memory array)
on DQ7–DQ0. Standard read cycle timings apply in
this mode. Refer to the Autoselect Mode and Autose-
lect Command Sequence sections for more informa-
tion.
Standby Mode
When the system is not reading or writing to the de-
vice, 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
10Am29LV128MH/LSeptember 9, 2003
Page 13
DATASHEET
VIH.) If CE# and RESET# are held at VIH, but not within
± 0.3 V, the device will be in the standby mode, but
V
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.
Refer to the DC Characteristics table 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.
Refer to the DC Characteristics table 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
but not within VSS±0.3 V, the standby current will
at V
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.
Refer to the AC Characteristics tables 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.
September 9, 2003Am29LV128MH/L11
Page 14
DATASHEET
Table 2. Sector Address Table
8-bit
SectorA22–A15
SA0 0000000064/32000000–00FFFF000000–007FFF
SA1 0000000164/32010000–01FFFF008000–00FFFF
SA2 0000001064/32020000–02FFFF010000–017FFF
SA3 0000001164/32030000–03FFFF018000–01FFFF
SA4 0000010064/32040000–04FFFF020000–027FFF
SA5 0000010164/32050000–05FFFF028000–02FFFF
SA6 0000011064/32060000–06FFFF030000–037FFF
SA7 0000011164/32070000–07FFFF038000–03FFFF
SA8 0000100064/32080000–08FFFF040000–047FFF
SA9 0000100164/32090000–09FFFF048000–04FFFF
SA10 0000101064/320A0000–0AFFFF050000–057FFF
SA11 0000101164/320B0000–0BFFFF058000–05FFFF
SA12 0000110064/320C0000–0CFFFF060000–067FFF
SA13 0000110164/320D0000–0DFFFF 068000–06FFFF
SA14 0000111064/320E0000–0EFFFF070000–077FFF
SA15 0000111164/320F0000–0FFFFF078000–07FFFF
SA16 0001000064/32100000–10FFFF080000–087FFF
SA17 0001000164/32110000–11FFFF088000–08FFFF
SA18 0001001064/32120000–12FFFF090000–097FFF
SA19 0001001164/32130000–13FFFF098000–09FFFF
SA20 0001010064/32140000–14FFFF0A0000–0A7FFF
SA21 0001010164/32150000–15FFFF0A8000–0AFFFF
SA22 0001011064/32160000–16FFFF0B0000–0B7FFF
SA23 0001011164/32170000–17FFFF0B8000–0BFFFF
SA24 0001100064/32180000–18FFFF0C0000–0C7FFF
SA25 0001100164/32190000–19FFFF0C8000–0CFFFF
SA26 0001101064/321A0000–1AFFFF 0D0000–0D7FFF
SA27 0001101164/321B0000–1BFFFF 0D8000–0DFFFF
SA28 0001110064/321C0000–1CFFFF 0E0000–0E7FFF
SA29 0001110164/321D0000–1DFFFF 0E8000–0EFFFF
SA30 0001111064/321E0000–1EFFFF0F0000–0F7FFF
SA31 0001111164/321F0000–1FFFFF0F8000–0FFFFF
SA32 0010000064/32200000–20FFFF100000–107FFF
SA33 0010000164/32210000–21FFFF108000–10FFFF
SA34 0010001064/32220000–22FFFF110000–117FFF
SA35 0010001164/32230000–23FFFF118000–11FFFF
SA36 0010010064/32240000–24FFFF120000–127FFF
SA37 0010010164/32250000–25FFFF128000–12FFFF
SA38 0010011064/32260000–26FFFF130000–137FFF
SA39 0010011164/32270000–27FFFF138000–13FFFF
SA40 0010100064/32280000–28FFFF140000–147FFF
SA41 0010100164/32290000–29FFFF148000–14FFFF
SA42 0010101064/322A0000–2AFFFF150000–157FFF
SA43 0010101164/322B0000–2BFFFF158000–15FFFF
SA44 0010110064/322C0000–2CFFFF160000–167FFF
SA45 0010110164/322D0000–2DFFFF 168000–16FFFF
SA46 0010111064/322E0000–2EFFFF170000–177FFF
Sector Size
(Kbytes/Kwords)
Address Range
(in hexadecimal)
16-bit
Address Range
(in hexadecimal)
12Am29LV128MH/LSeptember 9, 2003
Page 15
DATASHEET
Table 2. Sector Address Table (Continued)
SectorA22–A15
SA47 0010111164/322F0000–2FFFFF178000–17FFFF
SA48 0011000064/32300000–30FFFF180000–187FFF
SA49 0011000164/32310000–31FFFF188000–18FFFF
SA50 0011001064/32320000–32FFFF190000–197FFF
SA51 0011001164/32330000–33FFFF198000–19FFFF
SA52 0011010064/32340000–34FFFF1A0000–1A7FFF
SA53 0011010164/32350000–35FFFF1A8000–1AFFFF
SA54 0011011064/32360000–36FFFF1B0000–1B7FFF
SA55 0011011164/32370000–37FFFF1B8000–1BFFFF
SA56 0011100064/32380000–38FFFF1C0000–1C7FFF
SA57 0011100164/32390000–39FFFF1C8000–1CFFFF
SA58 0011101064/323A0000–3AFFFF 1D0000–1D7FFF
SA59 0011101164/323B0000–3BFFFF 1D8000–1DFFFF
SA60 0011110064/323C0000–3CFFFF 1E0000–1E7FFF
SA61 0011110164/323D0000–3DFFFF 1E8000–1EFFFF
SA62 0011111064/323E0000–3EFFFF1F0000–1F7FFF
SA63 0011111164/323F0000–3FFFFF1F8000–1FFFFF
SA64 0100000064/32400000–40FFFF200000–207FFF
SA65 0100000164/32410000–41FFFF208000–20FFFF
SA66 0100001064/32420000–42FFFF210000–217FFF
SA67 0100001164/32430000–43FFFF218000–21FFFF
SA68 0100010064/32440000–44FFFF220000–227FFF
SA69 0100010164/32450000–45FFFF228000–22FFFF
SA70 0100011064/32460000–46FFFF230000–237FFF
SA71 0100011164/32470000–47FFFF238000–23FFFF
SA72 0100100064/32480000–48FFFF240000–247FFF
SA73 0100100164/32490000–49FFFF248000–24FFFF
SA74 0100101064/324A0000–4AFFFF250000–257FFF
SA75 0100101164/324B0000–4BFFFF258000–25FFFF
SA76 0100110064/324C0000–4CFFFF260000–267FFF
SA77 0100110164/324D0000–4DFFFF 268000–26FFFF
SA78 0100111064/324E0000–4EFFFF270000–277FFF
SA79 0100111164/324F0000–4FFFFF278000–27FFFF
SA80 0101000064/32500000–50FFFF280000–287FFF
SA81 0101000164/32510000–51FFFF288000–28FFFF
SA82 0101001064/32520000–52FFFF290000–297FFF
SA83 0101001164/32530000–53FFFF298000–29FFFF
SA84 0101010064/32540000–54FFFF2A0000–2A7FFF
SA85 0101010164/32550000–55FFFF2A8000–2AFFFF
SA86 0101011064/32560000–56FFFF2B0000–2B7FFF
SA87 0101011164/32570000–57FFFF2B8000–2BFFFF
SA88 0101100064/32580000–58FFFF2C0000–2C7FFF
SA89 0101100164/32590000–59FFFF2C8000–2CFFFF
SA90 0101101064/325A0000–5AFFFF 2D0000–2D7FFF
SA91 0101101164/325B0000–5BFFFF 2D8000–2DFFFF
SA92 0101110064/325C0000–5CFFFF 2E0000–2E7FFF
SA93 0101110164/325D0000–5DFFFF 2E8000–2EFFFF
SA94 0101111064/325E0000–5EFFFF2F0000–2F7FFF
Sector Size
(Kbytes/Kwords)
8-bit
Address Range
(in hexadecimal)
16-bit
Address Range
(in hexadecimal)
September 9, 2003Am29LV128MH/L13
Page 16
DATASHEET
Table 2. Sector Address Table (Continued)
SectorA22–A15
SA95 0101111164/325F0000–5FFFFF2F8000–2FFFFF
SA96 0110000064/32600000–60FFFF300000–307FFF
SA97 0110000164/32610000–61FFFF308000–30FFFF
SA98 0110001064/32620000–62FFFF310000–317FFF
SA99 0110001164/32630000–63FFFF318000–31FFFF
SA100 0110010064/32640000–64FFFF320000–327FFF
SA101 0110010164/32650000–65FFFF328000–32FFFF
SA102 0110011064/32660000–66FFFF330000–337FFF
SA103 0110011164/32670000–67FFFF338000–33FFFF
SA104 0110100064/32680000–68FFFF340000–347FFF
SA105 0110100164/32690000–69FFFF348000–34FFFF
SA106 0110101064/326A0000–6AFFFF350000–357FFF
SA107 0110101164/326B0000–6BFFFF358000–35FFFF
SA108 0110110064/326C0000–6CFFFF360000–367FFF
SA109 0110110164/326D0000–6DFFFF 368000–36FFFF
SA110 0110111064/326E0000–6EFFFF370000–377FFF
SA111 0110111164/326F0000–6FFFFF378000–37FFFF
SA112 0111000064/32700000–70FFFF380000–387FFF
SA113 0111000164/32710000–71FFFF388000–38FFFF
SA114 0111001064/32720000–72FFFF390000–397FFF
SA115 0111001164/32730000–73FFFF398000–39FFFF
SA116 0111010064/32740000–74FFFF3A0000–3A7FFF
SA117 0111010164/32750000–75FFFF3A8000–3AFFFF
SA118 0111011064/32760000–76FFFF3B0000–3B7FFF
SA119 0111011164/32770000–77FFFF3B8000–3BFFFF
SA120 0111100064/32780000–78FFFF3C0000–3C7FFF
SA121 0111100164/32790000–79FFFF3C8000–3CFFFF
SA122 0111101064/327A0000–7AFFFF 3D0000–3D7FFF
SA123 0111101164/327B0000–7BFFFF 3D8000–3DFFFF
SA124 0111110064/327C0000–7CFFFF 3E0000–3E7FFF
SA125 0111110164/327D0000–7DFFFF 3E8000–3EFFFF
SA126 0111111064/327E0000–7EFFFF3F0000–3F7FFF
SA127 0111111164/327F0000–7FFFFF3F8000–3FFFFF
SA128 1000000064/32800000–80FFFF400000–407FFF
SA129 1000000164/32810000–81FFFF408000–40FFFF
SA130 1000001064/32820000–82FFFF410000–417FFF
SA131 1000001164/32830000–83FFFF418000–41FFFF
SA132 1000010064/32840000–84FFFF420000–427FFF
SA133 1000010164/32850000–85FFFF428000–42FFFF
SA134 1000011064/32860000–86FFFF430000–437FFF
SA135 1000011164/32870000–87FFFF438000–43FFFF
SA136 1000100064/32880000–88FFFF440000–447FFF
SA137 1000100164/32890000–89FFFF448000–44FFFF
SA138 1000101064/328A0000–8AFFFF450000–457FFF
SA139 1000101164/328B0000–8BFFFF458000–45FFFF
SA140 1000110064/328C0000–8CFFFF460000–467FFF
SA141 1000110164/328D0000–8DFFFF 468000–46FFFF
SA142 1000111064/328E0000–8EFFFF470000–477FFF
Sector Size
(Kbytes/Kwords)
8-bit
Address Range
(in hexadecimal)
16-bit
Address Range
(in hexadecimal)
14Am29LV128MH/LSeptember 9, 2003
Page 17
DATASHEET
Table 2. Sector Address Table (Continued)
SectorA22–A15
SA143 1000111164/328F0000–8FFFFF478000–47FFFF
SA144 1001000064/32900000–90FFFF480000–487FFF
SA145 1001000164/32910000–91FFFF488000–48FFFF
SA146 1001001064/32920000–92FFFF490000–497FFF
SA147 1001001164/32930000–93FFFF498000–49FFFF
SA148 1001010064/32940000–94FFFF4A0000–4A7FFF
SA149 1001010164/32950000–95FFFF4A8000–4AFFFF
SA150 1001011064/32960000–96FFFF4B0000–4B7FFF
SA151 1001011164/32970000–97FFFF4B8000–4BFFFF
SA152 1001100064/32980000–98FFFF4C0000–4C7FFF
SA153 1001100164/32990000–99FFFF4C8000–4CFFFF
SA154 1001101064/329A0000–9AFFFF 4D0000–4D7FFF
SA155 1001101164/329B0000–9BFFFF 4D8000–4DFFFF
SA156 1001110064/329C0000–9CFFFF 4E0000–4E7FFF
SA157 1001110164/329D0000–9DFFFF 4E8000–4EFFFF
SA158 1001111064/329E0000–9EFFFF4F0000–4F7FFF
SA159 1001111164/329F0000–9FFFFF4F8000–4FFFFF
SA160 1010000064/32A00000–A0FFFF500000–507FFF
SA161 1010000164/32A10000–A1FFFF508000–50FFFF
SA162 1010001064/32A20000–A2FFFF510000–517FFF
SA163 1010001164/32A30000–A3FFFF518000–51FFFF
SA164 1010010064/32A40000–A4FFFF520000–527FFF
SA165 1010010164/32A50000–A5FFFF528000–52FFFF
SA166 1010011064/32A60000–A6FFFF530000–537FFF
SA167 1010011164/32A70000–A7FFFF538000–53FFFF
SA168 1010100064/32A80000–A8FFFF540000–547FFF
SA169 1010100164/32A90000–A9FFFF548000–54FFFF
SA170 1010101064/32AA0000–AAFFFF550000–557FFF
SA171 1010101164/32AB0000–ABFFFF 558000–55FFFF
SA172 1010110064/32AC0000–ACFFFF560000–567FFF
SA173 1010110164/32AD0000–ADFFFF 568000–56FFFF
SA174 1010111064/32AE0000–AEFFFF570000–577FFF
SA175 1010111164/32AF0000–AFFFFF 578000–57FFFF
SA176 1011000064/32B00000–B0FFFF580000–587FFF
SA177 1011000164/32B10000–B1FFFF588000–58FFFF
SA178 1011001064/32B20000–B2FFFF590000–597FFF
SA179 1011001164/32B30000–B3FFFF598000–59FFFF
SA180 1011010064/32B40000–B4FFFF 5A0000–5A7FFF
SA181 1011010164/32B50000–B5FFFF 5A8000–5AFFFF
SA182 1011011064/32B60000–B6FFFF 5B0000–5B7FFF
SA183 1011011164/32B70000–B7FFFF 5B8000–5BFFFF
SA184 1011100064/32B80000–B8FFFF 5C0000–5C7FFF
SA185 1011100164/32B90000–B9FFFF 5C8000–5CFFFF
SA186 1011101064/32BA0000–BAFFFF 5D0000–5D7FFF
SA187 1011101164/32BB0000–BBFFFF 5D8000–5DFFFF
SA188 1011110064/32BC0000–BCFFFF 5E0000–5E7FFF
SA189 1011110164/32BD0000–BDFFFF 5E8000–5EFFFF
SA190 1011111064/32BE0000–BEFFFF 5F0000–5F7FFF
Sector Size
(Kbytes/Kwords)
8-bit
Address Range
(in hexadecimal)
16-bit
Address Range
(in hexadecimal)
September 9, 2003Am29LV128MH/L15
Page 18
DATASHEET
Table 2. Sector Address Table (Continued)
SectorA22–A15
SA191 1011111164/32BF0000–BFFFFF 5F8000–5FFFFF
SA192 1100000064/32C00000–C0FFFF600000–607FFF
SA193 1100000164/32C10000–C1FFFF 608000–60FFFF
SA194 1100001064/32C20000–C2FFFF610000–617FFF
SA195 1100001164/32C30000–C3FFFF 618000–61FFFF
SA196 1100010064/32C40000–C4FFFF620000–627FFF
SA197 1100010164/32C50000–C5FFFF 628000–62FFFF
SA198 1100011064/32C60000–C6FFFF630000–637FFF
SA199 1100011164/32C70000–C7FFFF 638000–63FFFF
SA200 1100100064/32C80000–C8FFFF640000–647FFF
SA201 1100100164/32C90000–C9FFFF 648000–64FFFF
SA202 1100101064/32CA0000–CAFFFF650000–657FFF
SA203 1100101164/32CB0000–CBFFFF 658000–65FFFF
SA204 1100110064/32CC0000–CCFFFF 660000–667FFF
SA205 1100110164/32CD0000–CDFFFF 668000–66FFFF
SA206 1100111064/32CE0000–CEFFFF670000–677FFF
SA207 1100111164/32CF0000–CFFFFF 678000–67FFFF
SA208 1101000064/32D00000–D0FFFF680000–687FFF
SA209 1101000164/32D10000–D1FFFF 688000–68FFFF
SA210 1101001064/32D20000–D2FFFF690000–697FFF
SA211 1101001164/32D30000–D3FFFF 698000–69FFFF
SA212 1101010064/32D40000–D4FFFF 6A0000–6A7FFF
SA213 1101010164/32D50000–D5FFFF 6A8000–6AFFFF
SA214 1101011064/32D60000–D6FFFF 6B0000–6B7FFF
SA215 1101011164/32D70000–D7FFFF 6B8000–6BFFFF
SA216 1101100064/32D80000–D8FFFF 6C0000–6C7FFF
SA217 1101100164/32D90000–D9FFFF 6C8000–6CFFFF
SA218 1101101064/32DA0000–DAFFFF 6D0000–6D7FFF
SA219 1101101164/32DB0000–DBFFFF 6D8000–6DFFFF
SA220 1101110064/32DC0000–DCFFFF6E0000–6E7FFF
SA221 1101110164/32DD0000–DDFFFF6E8000–6EFFFF
SA222 1101111064/32DE0000–DEFFFF 6F0000–6F7FFF
SA223 1101111164/32DF0000–DFFFFF 6F8000–6FFFFF
SA224 1110000064/32E00000–E0FFFF700000–707FFF
SA225 1110000164/32E10000–E1FFFF708000–70FFFF
SA226 1110001064/32E20000–E2FFFF710000–717FFF
SA227 1110001164/32E30000–E3FFFF718000–71FFFF
SA228 1110010064/32E40000–E4FFFF720000–727FFF
SA229 1110010164/32E50000–E5FFFF728000–72FFFF
SA230 1110011064/32E60000–E6FFFF730000–737FFF
SA231 1110011164/32E70000–E7FFFF738000–73FFFF
SA232 1110100064/32E80000–E8FFFF740000–747FFF
SA233 1110100164/32E90000–E9FFFF748000–74FFFF
SA234 1110101064/32EA0000–EAFFFF750000–757FFF
SA235 1110101164/32EB0000–EBFFFF 758000–75FFFF
SA236 1110110064/32EC0000–ECFFFF760000–767FFF
SA237 1110110164/32ED0000–EDFFFF 768000–76FFFF
SA238 1110111064/32EE0000–EEFFFF770000–777FFF
Sector Size
(Kbytes/Kwords)
8-bit
Address Range
(in hexadecimal)
16-bit
Address Range
(in hexadecimal)
16Am29LV128MH/LSeptember 9, 2003
Page 19
DATASHEET
Table 2. Sector Address Table (Continued)
SectorA22–A15
SA239 1110111164/32EF0000–EFFFFF 778000–77FFFF
SA240 1111000064/32F00000–F0FFFF780000–787FFF
SA241 1111000164/32F10000–F1FFFF788000–78FFFF
SA242 1111001064/32F20000–F2FFFF790000–797FFF
SA243 1111001164/32F30000–F3FFFF798000–79FFFF
SA244 1111010064/32F40000–F4FFFF 7A0000–7A7FFF
SA245 1111010164/32F50000–F5FFFF 7A8000–7AFFFF
SA246 1111011064/32F60000–F6FFFF 7B0000–7B7FFF
SA247 1111011164/32F70000–F7FFFF 7B8000–7BFFFF
SA248 1111100064/32F80000–F8FFFF 7C0000–7C7FFF
SA249 1111100164/32F90000–F9FFFF 7C8000–7CFFFF
SA250 1111101064/32FA0000–FAFFFF 7D0000–7D7FFF
SA251 1111101164/32FB0000–FBFFFF 7D8000–7DFFFF
SA252 1111110064/32FC0000–FCFFFF 7E0000–7E7FFF
SA253 1111110164/32FD0000–FDFFFF 7E8000–7EFFFF
SA254 1111111064/32FE0000–FEFFFF 7F0000–7F7FFF
SA255 1111111164/32FF0000–FFFFFF7F8000–7FFFFF
Sector Size
(Kbytes/Kwords)
8-bit
Address Range
(in hexadecimal)
16-bit
Address Range
(in hexadecimal)
September 9, 2003Am29LV128MH/L17
Page 20
DATASHEET
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 VID on address pin A9. Address pins
A6, A3, A2, A1, and A0 must be as shown in Table 3.
In addition, when verifying sector protection, the sector
address must appear on the appropriate highest order
address bits (see Table 2). Table 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 Tables 10 and 11. This
method does not require V
. Refer to the Autoselect
ID
Command Sequence section for more information.
Table 3. Autoselect Codes, (High Voltage Method)
A22
DescriptionCE# OE# WE#
Manufacturer ID: AMDLLHXX
Cycle 1
Cycle 2HHL22X12h
Device ID
Cycle 3HHH22X00h
Sector Group
Protection Verification
SecSi Sector Indicator
Bit (DQ7), WP#
protects highest
address sector
SecSi Sector Indicator
Bit (DQ7), WP#
protects lowest
address sector
LLHXX
LLHSAX
LLHXX
LLHXX
to
A15
A14
to
A9A8toA7A6A5to
A10
V
ID
V
ID
V
ID
V
ID
V
ID
XLXLLL00X01h
XL X
XL X L H L XX
XL X L H H XX
XL X L H H XX
A3
toA2A1A0
A4
LLH 22 X7Eh
DQ8 to DQ15
BYTE#
= V
BYTE#
IH
= V
DQ7 to DQ0
IL
01h (protected),
00h (unprotected)
98h (factory locked),
18h (not factory locked)
88h (factory locked),
08h (not factory locked)
Legend: L = Logic Low = VIL, H = Logic High = VIH, SA = Sector Address, X = Don’t care.
18Am29LV128MH/LSeptember 9, 2003
Page 21
DATASHEET
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 the Autoselect Mode
section 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
September 9, 2003Am29LV128MH/L19
Page 22
DATASHEET
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 Characteristics”.
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”.
when unconnected, WP# is at V
Note that WP# has an internal pullup;
.
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 VID. During this mode, formerly protected sector groups can be programmed or
erased by selecting the sector group addresses. Once
is removed from the RESET# pin, all the previously
V
ID
protected sector groups are protected again. Figure 1
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
20Am29LV128MH/LSeptember 9, 2003
Page 23
DATASHEET
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
September 9, 2003Am29LV128MH/L21
Page 24
DATASHEET
SecSi (Secured Silicon) Sector Flash
Memory Region
The SecSi (Secured Silicon) Sector feature provides a
Flash memory region that enables permanent part
identification through an Electronic Serial Number
(ESN). The SecSi Sector is 256 bytes in length, and
uses a SecSi Sector Indicator Bit (DQ7) to indicate
whether or not the SecSi 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 SecSi 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 SecSi Sector unprotected, allowing
customers to program the sector after receiving the
device. The customer-lockable version also has the
SecSi Sector Indicator Bit permanently set to a “0.”
The factory-locked version is always protected when
shipped from the factory, and has the SecSi (Secured
Silicon) Sector Indicator Bit permanently set to a “1.”
Thus, the SecSi Sector Indicator Bit prevents customer-lockable devices from being used to replace devices that are factory locked.
function and unlock bypass modes are not available
when the SecSi Sector is enabled.
The SecSi sector address space in this device is allocated as follows:
Table 5. SecSi Sector Contents
SecSi Sector
Address Range
000000h–000007h
000008h–00007FhUnavailable
Customer
Lockable
Determined by
customer
The system accesses the SecSi Sector through a
command sequence (see “Enter SecSi Sector/Exit
SecSi Sector Command Sequence”). After the system
has written the Enter SecSi Sector command sequence, it may read the SecSi Sector by using the addresses normally occupied by the first sector (SA0).
This mode of operation continues until the system issues the Exit SecSi Sector command sequence, or
until power is removed from the device. On power-up,
or following a hardware reset, the device reverts to
sending commands to sector SA0.
Note that the ACC
ESN Factory
Locked
ESN
ExpressFlash
Factory Locked
ESN or
determined by
customer
Determined by
customer
Customer Lockable: SecSi 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 SecSi sector.
The system may program the SecSi Sector using the
write-buffer, accelerated and/or unlock bypass methods, in addition to the standard programming command sequence. See Command Definitions.
Programming and protecting the SecSi Sector must be
used with caution since, once protected, there is no
procedure available for unprotecting the SecSi Sector
area and none of the bits in the SecSi Sector memory
space can be modified in any way.
The SecSi Sector area can be protected using one of
the following procedures:
■ Write the three-cycle Enter SecSi 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 VIH or V
. This
ID
allows in-system protection of the SecSi Sector
without raising any device pin to a high voltage.
Note that this method is only applicable to the SecSi
Sector.
■ To verify the protect/unprotect status of the SecSi
Sector, follow the algorithm shown in Figure 3.
Once the SecSi Sector is programmed, locked and
verified, the system must write the Exit SecSi Sector
Region command sequence to return to reading and
writing within the remainder of the array.
Factory Locked: SecSi Sector Programmed and
Protected At the Factory
In devices with an ESN, the SecSi Sector is protected
when the device is shipped from the factory. The SecSi
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 SecSi Sector permanently
locked. Contact an AMD representative for details on
using AMD’s ExpressFlash service.
22Am29LV128MH/LSeptember 9, 2003
Page 25
DATASHEET
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. SecSi 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 Tables 10 and 11
for command definitions). In addition, the following
hardware data protection measures prevent accidental
erasure or programming, which might otherwise be
caused by spurious system level signals during V
CC
power-up and power-down transitions, or 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# =
, CE# = VIH or WE# = VIH. To initiate a write cycle,
V
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 Tables 6–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 Tables 6–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.
September 9, 2003Am29LV128MH/L23
Page 26
DATASHEET
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
1Eh0000hV
1Fh0007hTypical timeout per single byte/word write 2
20h0007hTypical timeout for Min. size buffer write 2
21h000AhTypical timeout per individual block erase 2
22h0000hTypical timeout for full chip erase 2
23h0001hMax. timeout for byte/word write 2
24h0005hMax. timeout for buffer write 2
25h0004hMax. timeout per individual block erase 2
26h0000hMax. timeout for full chip erase 2
CC
D7–D4: volt, D3–D0: 100 millivolt
Max. (write/erase)
V
CC
D7–D4: volt, D3–D0: 100 millivolt
Min. voltage (00h = no VPP pin present)
PP
Max. voltage (00h = no VPP pin present)
PP
N
N
N
times typical
N
times typical (00h = not supported)
N
µs
N
µs (00h = not supported)
N
ms
ms (00h = not supported)
times typical
N
times typical
24Am29LV128MH/LSeptember 9, 2003
Page 27
DATASHEET
Table 8. Device Geometry Definition
Addresses (x16)DataDescription
N
27h0018hDevice Size = 2
byte
28h
29h
2Ah
2Bh
0002h
0000h
0005h
0000h
2Ch0001h
2Dh
2Eh
2Fh
30h
31h
32h
33h
34h
35h
36h
37h
38h
39h
3Ah
3Bh
3Ch
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. Tables 10 and 11 defines the valid register
command sequences.
data values or writing them in the improper sequence
may place the device in an unknown state.
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. Refer to the AC Characteristics section for timing
diagrams.
Writing incorrect address and
A reset
the read mode. If the program command sequence is
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.
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 the Erase Suspend/Erase Resume
Commands section for more information.
must
The system
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.
See also Requirements for Reading Array Data in the
Device Bus Operations section for more information.
The Read-Only Operations table provides the read parameters, and Figure 14 shows the timing diagram.
issue the reset command to return
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
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.
Tables 10 and 11 show the address and data requirements. This method is an alternative to that shown in
Table 3, which is intended for PROM programmers
and requires V
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.
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).
on address pin A9. The autoselect
ID
September 9, 2003Am29LV128MH/L27
Page 30
DATASHEET
Enter SecSi Sector/Exit SecSi Sector
Command Sequence
The SecSi Sector region provides a secured data area
containing an 8-word/16-byte random Electronic Serial
Number (ESN). The system can access the SecSi
Sector region by issuing the three-cycle Enter SecSi
Sector command sequence. The device continues to
access the SecSi Sector region until the system issues the four-cycle Exit SecSi Sector command sequence. The Exit SecSi Sector command sequence
returns the device to normal operation. Tables 10 and
11 show the address and data requirements for both
command sequences. See also “SecSi (Secured Silicon) Sector Flash Memory Region” for further informa-
Note that the ACC function and unlock bypass
tion.
modes are not available when the SecSi Sector is enabled.
Word/Byte 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 al-
not
gorithm. The system is
controls or timings. The device automatically provides
internally generated program pulses and verifies the
programmed cell margin. Tables 10 and 11 show the
address and data requirements for the word program
command sequence.
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. Refer to the Write Operation Status section 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.
Sector, autoselect, and CFI functions are unavailable
when a program operation is in progress.
required to provide further
Note that the SecSi
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. Tables 10 and 11 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.
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.
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
data is still “0.” Only erase operations can convert a “0”
to a “1.”
28Am29LV128MH/LSeptember 9, 2003
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
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
MAX–A4
. All subsequent ad-
Page 31
DATASHEET
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.
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
data is still “0.” Only erase operations can convert a “0”
to a “1.”
Accelerated Program
The device offers accelerated program operations
through the WP#/ACC pin. When the system asserts
on the WP#/ACC pin, the device automatically en-
V
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.
WP#/
the
ACC pin must not be at VHH for operations
Note that
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.
September 9, 2003Am29LV128MH/L29
Page 32
Write “Write to Buffer”
command and
Sector Address
DATASHEET
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 Tables 10 and 11 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
30Am29LV128MH/LSeptember 9, 2003
Page 33
DATASHEET
START
Write Program
Command Sequence
Data Poll
Embedded
Program
algorithm
in progress
Increment Address
Note: See Tables 10 and 11 for program command
sequence.
No
from System
Verify Data?
Yes
Last Address?
Yes
Programming
Completed
Figure 5. Program Operation
No
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 SecSi 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 for more
information.
The system must write the Program Resume command to exit the Program Suspend mode and continue
the programming operation. The address of the program-suspended sector is required when writing this
command. Further writes of the Resume command
are ignored. Another Program Suspend command can
be written after the device has resume programming.
September 9, 2003Am29LV128MH/L31
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
DATASHEET
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.
Refer to the Write Operation Status section 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
SecSi 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 tables 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
not
algorithm. The device does
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. Tables 10 and
11 show the address and data requirements for the
chip erase command sequence.
require the system to
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. Tables 9 & 10 shows the
address and data requirements for the sector erase
command sequence.
not
The device does
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.
autoselect, and CFI functions are unavailable when an
erase operation is in progress.
require the system to preprogram
Note that the SecSi Sector,
32Am29LV128MH/LSeptember 9, 2003
Page 35
DATASHEET
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. Refer to the Write Operation Status section 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 tables in the AC Characteristics section for parameters,
and Figure 20 section for timing diagrams.
START
Write Erase
Command Sequence
(Notes 1, 2)
Data Poll to Erasing
Bank from System
No
Data = FFh?
Embedded
Erase
algorithm
in progress
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.
Refer to the Write Operation Status section 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.
Refer to the Write Operation Status section for more
information.
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.
Yes
To resume the sector erase operation, the system
must write the Erase Resume command. The address
of the erase-suspended sector is required when writ-
Erasure Completed
ing this command. Further writes of the Resume command are ignored. Another Erase Suspend command
Figure 7. Erase Operation
Notes:
1. See Tables 10 and 11 for erase command sequence.
2. See the section on DQ3 for information on the sector
erase timer.
can be written after the chip has resumed erasing.
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 Table 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.
Addr DataAddrDataAddrDataAddrDataAddr Data Addr Data
4AAAAA55555AAA90X06(Note 10)
4AAAAA55555AAA90(SA)X0400/01
Legend:
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.
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 Table 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.
September 9, 2003Am29LV128MH/L35
Page 38
DATASHEET
WRITE OPERATION STATUS
The device provides several bits to determine the status of a
program or erase operation: DQ2, DQ3, DQ5, DQ6, and
DQ7. Table 12 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.
Table 12 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
36Am29LV128MH/LSeptember 9, 2003
Page 39
DATASHEET
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. Table 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 the subsection on
DQ7: Data# Polling).
If a program address falls within a protected sector,
DQ6 toggles for approximately 1
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.
Table 12 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 also the
subsection on DQ2: Toggle Bit II.
µs after the program
September 9, 2003Am29LV128MH/L37
Page 40
No
START
Read DQ7–DQ0
Read DQ7–DQ0
Toggle Bit
= Toggle?
Yes
DQ5 = 1?
Yes
No
DATASHEET
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 Table 12 to compare outputs for DQ2 and DQ6.
Figure 9 shows the toggle bit algorithm in flowchart
form, and the section “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
38Am29LV128MH/LSeptember 9, 2003
Page 41
DATASHEET
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 also the Sector Erase Command
Sequence section.
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.
Table 12 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 section for more details.
September 9, 2003Am29LV128MH/L39
Page 42
DATASHEET
Table 12. Write Operation Status
DQ7
Standard
Mode
Program
Suspend
Mode
Erase
Suspend
Mode
Write-to-
Buffer
Status
Embedded Program AlgorithmDQ7#Toggle0N/ANo toggle00
Embedded Erase Algorithm0Toggle01ToggleN/A0
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.
with Power Applied . . . . . . . . . . . . . . –65
Voltage with Respect to Ground
(Note 1) . . . . . . . . . . . . . . . . .–0.5 V to +4.0 V
V
CC
. . . . . . . . . . . . . . . . . . . . . . . . .–0.5 V to +4.0 V
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
°C to +150°C
°C to +125°C
+0.5 V
CC
+0.5 V.
CC
to –2.0 V for
SS
+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
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
Suspend Program
Erase Suspend
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
52Am29LV128MH/LSeptember 9, 2003
Page 55
AC CHARACTERISTICS
Temporary Sector Group Unprotect
Parameter
DATASHEET
All Speed OptionsJEDECStdDescriptionUnit
t
VID Rise and Fall Time (See Note)Min500ns
VIDR
RESET# Setup Time for Temporary Sector
t
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
September 9, 2003Am29LV128MH/L53
Page 56
AC CHARACTERISTICS
V
ID
V
RESET#
IH
DATASHEET
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
54Am29LV128MH/LSeptember 9, 2003
Page 57
DATASHEET
AC CHARACTERISTICS
Alternate CE# Controlled Erase and Program Operations
Input voltage with respect to V
(including A9, OE#, and RESET#)
Input voltage with respect to V
V
Current–100 mA+100 mA
CC
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
56Am29LV128MH/LSeptember 9, 2003
Page 59
DATASHEET
ERASE AND PROGRAMMING PERFORMANCE
ParameterTyp (Note 1)Max (Note 2)UnitComments
Sector Erase Time0.53.5sec
Chip Erase Time128256sec
Single Byte/Word
Program Time (Note 3)
Accelerated Single Byte/Word
Program Time
(Note 3)
Total Write Buffer Program
Time (Note 4)
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
Byte60600µs
Word60 600µs
Byte54540µs
Word54540µs
2401200µs
Per Byte7.538µs
Per Word1575µs
2001040µs
Per Byte6.2533µs
Per Word12.565µs
Excludes 00h programming
prior to erasure (Note 6)
Excludes system level
overhead (Note 8)
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. Byte/Word programming specification is based upon a single word/byte 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 Table
11 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
September 9, 2003Am29LV128MH/L59
Page 62
DATASHEET
PHYSICAL DIMENSIONS
LAA064—64-Ball Fortified Ball Grid Array
13 x 11 mm Package
60Am29LV128MH/LSeptember 9, 2003
Page 63
REVISION SUMMARY
Revision A (October 3, 2001)
DATASHEET
Distinctive Characteristics
Initial release as abbreviated Advance Information
data sheet.
Revision A+1 (March 20, 2002)
Distinctive Characteristics
Clarified description of Enhanced VersatileIO control.
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.
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.
Changed the typical sector erase time to TBD.
Changed the typical write buffer word programming
time to TBD.
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
Modified Order numbers and package markings to reflect the removal of speed options.
Modified the V
ranges.
IO
Added Notes #1 and #2.
Table 4. SecSi 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).
CMOS Compatible
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: SecSi Sector NOT
Programmed or Protected at the factory.
Added second bullet, SecSi sector-protect verify text
and figure 3.
SecSi Sector Flash Memory Region, and Enter
SecSi Sector/Exit SecSi Sector Command
Sequence
Noted that the ACC function and unlock bypass modes
are not available when the SecSi sector is enabled.
September 9, 2003Am29LV128MH/L61
Page 64
DATASHEET
Byte/Word Program Command Sequence, Sector
Erase Command Sequence, and Chip Erase Command Sequence
Noted that the SecSi Sector, autoselect, and CFI
functions are unavailable when a program or erase
operation is in progress.
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
Removed Notes #1 and 2.
Figure 6. Program Suspend/Program Resume
Change wait time to 15
Operating Ranges
Corrected typos in V
Removed full voltage range.
CMOS Compatible
Changed V
Removed typos in notes.
Read-Only Characteristics
Added a 30 ns option to t
ble.
Added note #3.
s to table and removed Note #2
IO
ranges.
IO
µs.
ranges.
IO
and V
IH1
minimum to 1.9.
IH2
and tOE standard in ta-
PA CC
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
WHWH
1 and t
2 parameters in
WHWH
the Erase and Program Options table that were previously TBD. Also added notes 5 and 6.
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 notes
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 datasheet version.
Modified SecSi 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
Hardware Reset, Erase and Program Operations,
Temporary Sector Unprotect, and Alternate CE#
Controlled Erase and Program Operations