sectors before an erase operat ion is com ple ted
— Data# polling & toggle bits provide status
— Unlock Bypass Program command reduces overall
multiple-word programming time
— CFI (Com mon F lash Inte rfac e) com plia nt: a llow s hos t
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 Unprotect: V
changing code in locked sectors
— WP#/ACC input:
Write Protect input (WP#) protects top or bottom two
sectors regardless of sector protection settings
ACC (high voltage) accelerates programming time for
higher throughput during system production
— Hardware reset input (RESET#) resets device
— Ready/Busy# output (RY/BY#) indicates program or
erase cycle completion
-level method of
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# 26518 Rev: B Amendment/0
Issue Date: May 16, 2003
DATASHEET
GENERAL DESCRIPTION
The Am29LV320M/TB is a 32 Mbit, 3.0 volt single
power supply flash memory device organized as
2,097,152 words or 4,194,304 bytes. The device has
an 8-bit/16-bit bus and 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 a ccess time has a spec ific operat ing
voltage range (V
specified in the Product Selector Guide and the Order-
ing Information sections. The devic e is offered in a
48-pin TSOP, 48-ball Fine-pitch BGA or 64-ball Fortified BGA package. Each device has separate chip enable (CE#), write enable (WE#) and output enable
(OE#) controls.
Each device requires on ly a single 3.0 volt powersupply for both read and write functions. In addition to
input, a high-voltage accelerated program
a V
CC
(ACC) function provides shorter programming times
through increased current on the WP#/ACC input. 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-pow er-supply Flash standard.
Commands are written to the device using standard
microprocessor write timing. Write cycles also internally latch address es and data nee ded for the programming and erase operations.
The sector erase architec ture allow s memory sectors to be erased and reprogrammed without affecting
the data conten ts of oth er se ctors. T he devi ce is f ully
erased when shipped from the factory.
Device programming and erasure are initiated through
command sequences. Once a program or erase operation has begun, the host system need only poll the
DQ7 (Data# Polling) or DQ6 (toggle) status bits or
monitor the Ready/Busy# (RY/BY#) output to determine whether the operation is complete. To facilitate
programming, an Unlock Bypass mode reduces command sequence overhead by requiring only two write
cycles to program data instead of four.
) and an I/O voltage range (VIO), as
CC
Hardware data protection measures include a low
detector that automatically inhibits write opera-
V
CC
tions during power transitions. The hardware sector
protection feature disables both program and erase
operations in any combination of sectors 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 operati on. The ProgramSuspend/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# p in terminates any opera tion
in progress and resets the device, after which it is then
ready for a new operation. T he 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 redu ces 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 Write Protect (WP#) feature protects the top or
bottom two sectors by asserting a logic low on the
WP#/ACC pin. The protected sector will still be protected even during accelerated programming.
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.
AMD MirrorBit flash technology combines years of
Flash memory manufacturing experienc e 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.
AMD standard products are available in several packages and operating ranges. The order number (Valid Combination) is
formed by a combination of the following:
Am29LV320MT120RPCI
TEMPERATURE RANGE
I = Industrial (–40
PACKAGE TYPE
E= 48-Pin Thin Small Outline Package (TSOP) Standard Pinout (TS 048)
PC = 64-Ball Fortified Ball Grid Array (
1.0 mm pitch, 13 x 11 mm package (LAA064)
WC = 48-Ball Fine Pitch Ball Grid Array (FBGA),
0.80 mm pitch, 9 x 8 mm package (FBC048)
SPEED OPTION
See Product Selector Guide a nd Valid Combinations
°C to +85°C)
FBGA),
SECTOR ARCHITECTURE AND WP# PROTECTION (WP# = V
T= Top boot sector device, top two address secto rs protected
B= Bottom boot sector device, bottom two address sectors protected
DEVICE NUMBER/DESCRIPTION
Am29LV320MT/B
32 Megabit (2 M x 16-Bit/4 M x 8-Bit) MirrorBit Boot Sector Flash Memory
3.0 Volt-only Read, Program, and Erase
Valid Combinations for
TSOP Package
Am29LV320MT90R,
Am29LV320MB90R
Am29LV320MT100,
Am29LV320MB100
Am29LV320MT110,
Am29LV320MB110
Am29LV320MT120,
Am29LV320MB120
Am29LV320MT100R,
Am29LV320MB100R
Am29LV320MT110R,
Am29LV320MB110R
Am29LV320MT120R,
Am29LV320MB120R
Speed
(ns)
903.0–3.6 V
100
110
EI
120
100
110
120
V
CC
Range
2.7–3.6 V
3.0–3.6 V
Valid Combinations
Valid Com binations l ist c onfi gurations pl anned 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.
Valid Combinations for
BGA Packages
Order NumberPackage Markin g
Am29LV320MT90R
Am29LV320MB90R
Am29LV320MT100
Am29LV320MB100
Am29LV320MT110
Am29LV320MB110
Am29LV320MT120
Am29LV320MB120
Am29LV320MT100R
Am29LV320MB100R
Am29LV320MT110R
Am29LV320MB110R
Am29LV320MT120R
Am29LV320MB120R
WCI L320MT90QI
PCI L320MT90NI
WCI L320MB90QI
PCI L320MB10NI
WCI L320MT10UI
PCI L320MT10PI
WCI L320MB10UI
PCI L320MB10PI
WCI L320MT11UI
PCI L320MT11PI
WCI L320MB11UI
PCI L320MB11PI
WCI L320MT12UI
PCI L320MT12PI
WCI L320MB12UI
PCI L320MB12PI
WCI L320MT10QI
PCI L320MT10NI
WCI L320MB10QI
PCI L320MB10NI
WCI L320MT11QI
PCI L320MT11NI
WCI L320MB11QI
PCI L320MB11NI
WCI L320MT12QI
PCI L320MT12NI
WCI L320MB12QI
PCI L320MB12NI
IL
)
Speed
(ns)
90
100
110
120
100
110
120
V
CC
Range
3.0–
3.6 V
2.7–
3.6 V
3.0–
3.6 V
3.0–
3.6 V
May 16, 2003Am29LV320MT/B9
DATASHEET
DEVICE BUS OPERATIONS
This section describes the requirements and use of
the device bus operations, which are in itiated through
the internal command register. The command register
itself does not occupy any addressabl e memory l ocation. The register is a latch used to store the commands, along with the ad dress and da ta information
needed to execute the command. The contents of the
Table 1. Device Bus Operations
register serve as inputs to the intern al state machine.
The state machine outputs dictate the function of the
device. Table 1 lists the device bus operations, the in-
puts and control l evels they requir e, and the resultin g
output. The following subsections de scribe each of
these operations in further detail.
Legend: L = Logic Low = VIL, H = Logic Hi gh = VIH, VID = 11.5–12.5V, VHH = 11.5–12. 5 V , X = Do n’t Care , SA = Sect or Addr ess ,
= Address In, DIN = Data In, D
A
IN
= Data Out
OUT
Notes:
1. Addresses are A20:A0 in word mode; A20:A-1 in byte mode. Sector addresses are A20:A12 in both modes.
2. The sector protect and sector unprotect functions may al so be i mplemente d via programmi ng equipmen t. See the “Sector Group
Protection and Unprotection” sectio n.
3. If WP# = V
, the first or last sector remains protect ed. I f WP# = VIH, the top two or bottom two sectors wi ll be prot ected or
IL
unprotected as determined by the method d escribe d in “Sector Group Pr otecti on and Unprotect ion ”. All sector s are unprote cted
when shipped from the factory (The SecSi Secto r may be facto ry pr otected depending on ver sion or dered.)
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 de vice data I/O
pins operate in the b yte or word confi guration. If the
BYTE# pin is set at logic ‘1’, the device is in word configuration, DQ0–DQ15 are active and co ntrolled 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.
Requirements for Reading Array Data
To read array data from the outputs, the system must
drive the CE# and OE# pins to V
control and selects the device. OE# is the output control and gates array data to the output pins. WE#
should remain at V
.
IH
. CE# is the power
IL
10Am29LV320MT/BMay 16, 2003
DATASHEET
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 durin g 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 spec-
ifications 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 wi thin a page. T he page s ize of
the device is 4 words/8 bytes. The appropriate page is
selected by th e higher addres s bits A(ma x)–A2. A ddress bits A1–A0 in word mode (A1–A-1 in byte mode)
determine the specif ic wor d withi n a page. This is an
asynchronous operation; the m icroprocesso r 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 equival ent to t
. When CE# is
PACC
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 cha nging the “i ntra-read p age”
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 mo de, only two write cycles are required to program a word or byte, instead of four. The
“Word/Byte Program Co mmand Sequenc e” section
has details on programming data to the device using
both standard and Unlock Bypass command sequences.
An erase operation can erase one sector, multiple sectors, or the entire device. Tables 3 and 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 to write a
maximum of 16 words/32 bytes in one programming
operation. This results in faster effective programming
time than the standard programming algorithms. See
“Write Buffer” for more information.
Accelerated Program Operation
The device offers accelerated program operations
through the ACC function. This is one of two functions
provided by the WP#/ACC pin. This function is primarily intended to allow faster manu facturing throu ghput
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 protec ted sectors,
and uses the higher voltage on the pin to reduce the
time required for program operations. The system
would use a two-cycle progra m command sequence
as required by the Unlock Bypass mode. Removing
from the WP#/ACC p in returns th e device to nor-
V
HH
mal operation. N ote that the WP# /ACC pin must not
be at V
for operations oth er than acceler ated pro-
HH
gramming, or device damage may result. In addition,
no external pullup is necessary since the WP#/ACC
pin has internal pullup to V
CC
.
Autoselect Functions
If the system writes the autoselect command s equence, the device enters the autoselect mo de. The
system can then read autoselect codes from the internal register (which is separate from the memory array)
on DQ7–DQ0. Standard read cycle timings apply in
this mode. Refer to the Autoselect M ode and Au tose-
lect Command Sequence sections for m ore informa-
tion.
Standby Mode
When the system is n ot reading or wri ting to the device, it can place the device in the standby mode. In
this mode, current consum ption is greatly reduc ed,
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 tha n
.) If CE# and RESET# are held at VIH, but not within
V
IH
± 0.3 V, the device will be in the s tandby mode,
V
CC
but the standby current will be greater. The device requires standard ac cess time (t
) for read access
CE
when the device is in either of these standby modes,
before it is ready to read data.
± 0.3 V.
CC
May 16, 2003Am29LV320MT/B11
DATASHEET
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 me thod of resetting the device to reading array data. When the RESET# pin is driven low for at least a period of t
device immediately term inates any operation in
progress, tristates all output pins, and ignores all
RP
, the
read/write command s for the dur ation 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 cir-
cuitry. 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.
Note: The address range is A20:A-1 in byte mode (BYTE# = VIL) or A20:A0 in word mode (BYTE# = VIH)
Sector Size
(Kbytes/Kwords)
(x8)
Address Range
Address Range
(x16)
May 16, 2003Am29LV320MT/B15
DATASHEET
Autoselect Mode
The autoselect mode provides manufacturer and device identification, and sector protection verification,
through identifier codes output on DQ7–DQ0. This
mode is prim arily intend ed for progr amming equi pment to automatically match a device to be programmed with its corresponding programming
algorithm. However, the autoselect codes can also be
accessed in-system through the command register .
When using programming equipment, the autoselect
mode requires V
A6, A3, A2, A1, and A0 must be as shown in Table 4.
on address pin A9. Address pins
ID
In addition, when verifying sector protection, the sector
address must appear on the appropriate highest order
address bits (see Tables 2 and 3). Table 4 shows the
remaining address bits that are do n’t care. W hen 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 12 and 13. This
method does not require V
. Refer to t he Aut os ele ct
ID
Command Sequence section for more information.
Tabl e 4. Autoselect Codes, (High Voltage Method)
A21
DescriptionCE# OE# WE#
Manufacturer ID: AMDLLHXX
Cycle 1
Cycle 2HHL22X1Ah
Device ID
Cycle 3HHH22X
Sector Protection
Verification
SecSi Sector In d i cator
Bit (DQ7), WP#
protects top two
address sector
SecSi Sector Indicator
Bit (DQ7), WP#
protects bottom two
address sector
LLHXX
LLHSAX
LLHXX
LLHXX
to
A15
A14
to
A9A8toA7A6A5to
A10
V
ID
V
ID
V
ID
V
ID
V
ID
XLX L L L 00X01h
XLX
XLX L H L X X
XLX L HH XX
XLX L HH XX
A3
toA2A1A0
A4
LLH 22 X7Eh
DQ8 to DQ15
BYTE#
= V
BYTE#
IH
= V
DQ7 to DQ0
IL
00 (bottom boot)
01h (top boot)
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.
16Am29LV320MT/BMay 16, 2003
DATASHEET
Sector Group Protection and
Unprotection
The hardware sector group protection feature disables
both program and erase operations in any sector
group. In this device, a sector group consists of fou r
adjacent sectors that are protected or unprotected at
the same time (see Tables 5 and 6). 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 protection/unprotection requires V
SET# pin only, and can be implemented either in-system or via progr amming eq uipment. Figure 2 sh ows
the algorithms and Figure 24 shows the timing diagram. This method uses standard microprocessor bus
cycle timing. For sector group unprotect, all unprotected sector groups must first be protected prior to
the first sector group unprotect write cycle.
The device is shipped with all se ctor 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 determin e whether a se ctor group is
protected or unprotected. See the Autoselect Mode
section for details.
The Write Protect function provides a hardware
method of protecting the top two or bottom two sectors
without using V
vided by the WP#/ACC input.
If the system asserts V
vice disables pro gram a nd er ase func tions in th e first
or last sector independently of whether those sectors
were protected or unprotected usin g the method described in “Sector Group Protecti on and Unprotec ti on”.
Note that if WP#/ACC is at V
the standby mode, the m aximum input lo ad current is
increased. See the table in “DC Characteristics”.
. WP# is one of two functions pro-
ID
on the WP#/ACC pin, the de-
IL
when the device is in
IL
May 16, 2003Am29LV320MT/B17
DATASHEET
If the system asserts V
on the WP#/ACC pin, the de-
IH
vice reverts to whether the top or bottom two sectors
were previously set to be protected or unprotected
using the method described in “Sector Group Protection and Unprotection”. Note: No external pullup is
necessary since the WP#/ACC pin has internal pullup
to V
CC
Temporary Sector Group Unprotect
(Note: In this device, a sector group consists of four adjacent
sectors that are prote cted or unprotected at the same ti me
(see Table 6).
This feature allo ws tempora ry unprotecti on of previously protected sector groups to change data in-system. The Sector Group Unprotect mode is act ivated by
setting the RESET# p in to V
merly protected sector groups can be programmed o r
erased by selecting the sector group addresses. Once
is removed from the RESET# pi n, all the prev i-
V
ID
ously protected sector groups are protected again.
Figure 1 shows the algorithm, and Figure 23 shows
the timing diagrams, for this feature.
. During this m ode, for-
ID
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 protect ed sec tor gro ups are prote cte d
once again.
ID
IH
,
IL
Figure 1. T emporary Sector Group
Unprotect Operation
18Am29LV320MT/BMay 16, 2003
DATASHEET
Temporary Sector
Group Unprotect
Mode
Increment
PLSCNT
START
PLSCNT = 1
RESET# = V
Wait 1 µs
No
First Write
Cycle = 60h?
Set up sector
group address
Sector Group Protect:
Write 60h to sector
group address with
A6–A0 = 0xx0010
Wait 150 µs
Verify Sector Group
Protect: Write 40h
to sector group
address with
A6–A0 = 0xx0010
Yes
START
Protect all sector
groups: The indicated
ID
Reset
PLSCNT = 1
portion of the sector
group protect algorithm
must be performed for all
unprotected sector
groups prior to issuing
the first sector group
unprotect address
PLSCNT = 1
RESET# = V
Wait 1 µs
First Write
Cycle = 60h?
All sector
No
protected?
Set up first sector
group address
Sector Group
Unprotect:
Write 60h to sector
group address with
A6–A0 = 1xx0010
Wait 15 ms
groups
Yes
Yes
ID
Temporary Sector
No
Group Unprotect
Mode
No
PLSCNT
= 25?
Yes
Device failed
Sector Group
Protect
Algorithm
Read from
sector group address
with A6–A0
= 0xx0010
No
Data = 01h?
Protect
another
sector group?
Remove V
from RESET#
Write reset
command
Sector Group
Protect complete
Yes
No
Verify Sector Group
Unprotect: Write
40h to sector group
Increment
PLSCNT
No
Yes
ID
PLSCNT
= 1000?
Yes
Device failed
Sector Group
address with
A6–A0 = 1xx0010
Read from
sector group
address with
A6–A0 = 1xx0010
No
Data = 00h?
Last sector
Remove V
from RESET#
group
verified?
Yes
Yes
ID
Set up
next sector group
address
No
Unprotect
Algorithm
Write reset
command
Sector Group
Unprotect complete
Figure 2. In-System Sector Group Protect/Unprotect Algorithms
May 16, 2003Am29LV320MT/B19
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 leng th, 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 fie ld.
AMD offers the device with the SecSi Sector either
customer lockable (standa rd shipping option) or fac tory 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. Note that the ACC
function and unlock b ypass modes ar e not availabl e
when the SecSi Sector is enabled.
The SecSi sector address space in this device is allocated as follows:
Table 7. SecSi Sector Contents
SecSi Sector
Address Range
000000h–000007h
000008h–00007FhUnavailable
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 sequ ence, 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.
Customer
Lockable
Determine d by
customer
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 prog ram 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 S ector 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 prote cted 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 V
or VID. This
IH
allows in-system protection of the SecSi Sector
without raising any device pin to a high voltage.
Note that this method is only applicabl e to the SecSi
Sector.
■ To v erify the protect/unprotect status of the SecSi
Sector, follow the algorithm shown in Figure 3.
Once the SecSi Secto r is programmed, loc ked 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 f a ct o ry. The SecSi
Sector cannot be modified in any way. An ESN F actory
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 pro grammed by
AMD through the AMD ExpressFlash service (Express
Flash Factory Locked ). The devic es are then shi pped
from AMD’s factory with the SecSi Sector permanent ly
locked. Contact an AMD repr esentative fo r details o n
using AMD’s ExpressFlash service.
20Am29LV320MT/BMay 16, 2003
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 pro tection
against inadvertent writes (refer to Tables 12 and 13
for command definitions) . In addition, the fol lowing
hardware data protection measures prevent accidental
erasure or programming, which might otherwise be
caused by spurious system level signals during V
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 igno red 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 Wri t e 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 s tate 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-comp atible for the spe cified flash dev ice
families. Flash vendors can sta ndardiz e 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
May 16, 2003Am29LV320MT/B21
given in Tables 8–11. 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 qu ery mod e, and th e syste m can r ead
CFI data at the addresses given in Tables 8–11. 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.
DATASHEET
Table 8. CFI Query Identification String
Addresses
(x16)
10h
11h
12h
13h
14h
15h
16h
17h
18h
19h
1Ah
Addresses
(x8)DataDescription
20h
22h
24h
26h
28h
2Ah
2Ch
2Eh
30h
32h
34h
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 9. System Interface String
Addresses
(x16)
1Bh36h0027h
1Ch38h0036h
1Dh3Ah0000hV
1Eh3Ch0000hV
1Fh3Eh0007hTypical timeout per single byte/word write 2
20h40h0007hTypical timeout for Min. size buffer write 2
21h42h000AhTypical timeout per individual block erase 2
22h44h0000hTypical timeout for full chip erase 2
23h46h0001hMax. timeout for byte/word write 2
24h48h0005hMax. timeout for buffer write 2
25h4Ah0004hMax. timeout per individual block erase 2
26h4Ch0000hMax. timeout for full chip erase 2
Addresses
(x8)DataDescription
Min. (write/erase)
V
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
times typical
N
N
µs
N
µs (00h = not supported)
N
ms
N
ms (00h = not supported)
N
times typical
N
times typical
times typical (00h = not supported)
22Am29LV320MT/BMay 16, 2003
DATASHEET
Table 10. Device Geometry Definition
Addresses
(x16)
Addresses
(x8)DataDescription
27h4Eh0016hDevice Size = 2
28h
29h
2Ah
2Bh
2Ch58h0002h
2Dh
2Eh
2Fh
30h
31h
32h
33h
34h
35h
36h
37h
38h
39h
3Ah
3Bh
3Ch
50h
52h
54h
56h
5Ah
5Ch
5Eh
60h
62h
64h
66h
68h
6Ah
6Ch
6Eh
70h
72h
74h
76h
78h
0002h
0000h
0005h
0000h
007Fh
0000h
0020h
0000h
003Eh
0000h
0000h
0001h
0000h
0000h
0000h
0000h
0000h
0000h
0000h
0000h
Flash Device Interface description (refer to CFI publication 100)
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)
N
byte
N
May 16, 2003Am29LV320MT/B23
DATASHEET
Table 11. Primary Vendor-Specific Extended Query
Addresses
(x16)
40h
41h
42h
43h86h0031hMajor version number, ASCII
44h88h0033hMinor version number, ASCII
Program Suspend
00h = Not Supported, 01h = Supported
COMMAND DEFINITIONS
Writing specific address and data commands or sequences into the command register initiates device operations. Tables 12 and 13 define the valid register
command sequences. Writing incorrect address and
data values or writing them in the improper sequence may place the device in an unknown state. A
reset command is then required to return the device to
reading array data.
All addresses are latched on the falling edge of WE#
or CE#, whichever happens later. All dat a is latched on
the rising edge of WE# or CE#, whichever happens
first. Refer to the AC Characteristics section for timing
diagrams.
Reading Array Data
The device is automatically set to reading array data
after device power-up. No commands are required to
retrieve data. The device is ready to read array data
after completing an Embedded Program or Embedded
Erase algorithm.
After the device accepts an Erase Suspend command,
the device enters the erase-suspend-read mode, after
24Am29LV320MT/BMay 16, 2003
DATASHEET
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.
The system must issue the reset command to return
the device to the read (or erase-suspend-read) mode
if DQ5 goes high during an active program or erase
operation, or if the device i s in the autoselect mod e.
See the next section, Reset Command, for more information.
See also Requirements for Reading Array Data in th e
Device Bus Operation s section for more information.
The Read-Only Operations t able pr ovides the read pa-
rameters, and Figure 14 shows the timing diagram.
Reset Command
Writing the reset command resets the device to the
read or erase-sus pend-read mod e. Address bi ts 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 w ritten between the
sequence cycles in a program command sequence
before programming begins. This resets the devic e to
the read mode. If the pr ogram com mand sequ ence is
written while the device is in the Erase Suspend mode,
writing the reset comma nd returns the device to th e
erase-suspend-re ad mode. Once pr ogramming b egins, 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 autosele ct mode whi le in the Erase
Suspend mode, writing the reset command returns the
device to the erase-suspend-read mode.
If DQ5 goes high during a program or erase operat ion,
writing the reset comma nd returns the device to th e
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 com mand sequenc e to
reset the device for the next operation.
Autoselect Command Sequence
The autoselect command sequence allows the host
system to read several identifier codes at specific addresses:
Note: The device ID i s read over three cycles . SA = Sec tor
Address
A7:A0
(x16)
A6:A-1
(x8)
Tables 12 and 13 show the address and data requirements. This m ethod is an altern ative to that sh own in
Ta bl e 4 , which is intended for PROM pr ogrammers
and requires V
on address pin A9. The autoselect
ID
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 wr itten 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.
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).
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 12 and
13 show the address and data requirements for both
command s equen ces. Se e als o “Sec Si (S ecured Silicon) Sector Flash Memory Region” for further information. Note that the ACC function and unlock bypass
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 addr ess and data are wr itten
May 16, 2003Am29LV320MT/B25
DATASHEET
next, which in tur n initiate the Embedd ed Program algorithm. The system is not required to pro vide furthe r
controls or timings. The device automatically provides
internally generated program pulses and verifies th e
programmed cell margin. Tables 12 and 13 show the
address and data requiremen ts for the word pr ogram
command sequence.
When the Emb edded P rogram algori thm is c omple te,
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 wr itten to the dev ice during the Embedded Program Algorithm are ignored. Note that ahardware reset immediately terminates the program
operation. Note that the SecSi Sector, autoselect, and
CFI functions are unavailable whe n a program oper ation is in progress. The program command sequence
should be reinitiated once the device has returned to
the read mode, to ensure data integrity.
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 t hat the
data is still “0.” On ly erase ope rations can c onvert a
“0” to a “1.”
Unlock Bypass Command Sequence
The unlock bypass feature allows the system to program words to the device faster than using the standard program command s equence. The unlock
bypass command se quence is in itiated by firs t 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 mo de. 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 12 and 13 show the requirements for the command sequence.
During the unlock bypass mode, only the Unlock Bypass Program and Unlock Bypas s Reset comma nds
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 syst em 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 S ector A ddress 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 add ress location s, then 05h shou ld be
written to the device. This tells the device how many
write buffer addresses will be loaded with data an d
therefore when to expect the Progra m Buffer to Flash
command. The number of locations to program c annot
exceed the size of the write buffer or the operation will
abort.
The fifth cycle writes the first address location and
data to be programmed. The write-buffer-page is selected by address bits A
MAX–A4
. All subsequent address/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
means that Write Bu ffer Program ming 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 ti mes, the addre ss/data pa ir counte r will b e
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 monitori ng the la st addr ess loc ation lo aded in to
the write buffer. DQ7, DQ6, DQ5, and DQ1 should be
monitored to determine the device status during Write
Buffer Programming.
26Am29LV320MT/BMay 16, 2003
DATASHEET
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. N ote that the full 3-c ycle
Write-to-Buffer-Abort Reset command sequence is required when using Write-Buffer-Programming features
in Unlock Bypass mode.
Accelerated Program
The device offers accelerated program operations
through the WP#/ACC pin. When the system asserts
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 de vice us es the hig her voltag e on the
WP#/ACC pin to acc elerate the ope ration. Note that
the WP#/ACC pin must not be at V
for operations
HH
other than accelerated programming, or device damage may resu lt. In addi tion, no e xternal pu llup is necessary since the WP#/ACC pin has internal pullup to
.
V
CC
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 17 for timing diagrams.
May 16, 2003Am29LV320MT/B27
Write “Write to Buffer”
command and
Sector Address
DATASHEET
No
Yes
Yes
(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?
Yes
Yes
Yes
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-Buffe r add re s s loc ati ons with data, all
addresses must fall with in 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 ca se, the proper r e se t
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 12 and 13 for command sequences
required for write buffer programming.
Read DQ7 - DQ0 with
address = Last Loaded
Address
(Note 2)
DQ7 = Data?
Yes
No
(Note 3)
FAIL or ABORTPASS
Figure 4. Write Buffer Programming Operation
28Am29LV320MT/BMay 16, 2003
DATASHEET
START
Write Program
Command Sequence
Data Poll
Embedded
Program
algorithm
in progress
Increment Address
Note: See Tables 12 and 13 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-suspende d sector. When the Progra m 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 r ead array data from any
non-suspended sector. The Program Suspend command may also be issued during a programming operation while an eras e is suspend ed. In this cas e, data
may be read from any addresses not in Erase Suspend or Program Suspend. If a read is ne eded from
the SecSi Sector area (One-time Program area), then
user must use the proper comman d sequences to
enter and exit this region.
The system may also write th e autoselect comman d
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 pr ogram ope ration using th e
DQ7 or DQ6 status bits, just as in the sta ndard program operation. See Write Operation Status for more
information.
The system must write the Program Resume command (address bits are don’t care) to exit the Program
Suspend mode and continue the programming operation. Further writes of the Resume command are ignored. Another Program Suspend command can be
written after the device has resume programming.
May 16, 2003Am29LV320MT/B29
DATASHEET
d
Program Operation
or Write-to-Buffer
Sequence in Progress
Write address/data
No
Write address/data
Device reverts to
operation prior to
Program Suspend
XXXh/B0h
Wait 15 µs
Read data as
required
Done
reading?
Yes
XXXh/30h
Write Program Suspend
Command Sequence
Command is also valid for
Erase-suspended-program
operations
Autoselect operations are also allowe
Data cannot be read from erase- or
program-suspended sectors
Write Program Resume
Command Sequence
Figure 6. Program Suspend/Program Resume
Chip Erase Command Sequence
Chip erase is a six bus cycle operat ion. The chip erase
command sequence is initiated by writing two unlock
cycles, followed by a set-up command. Two additional
unlock write cycles are then followed by the chip erase
command, which in turn invokes the Embedded Erase
algorithm. The device does not require the system to
preprogram prior to erase. The Embedded Erase algorithm automatically preprograms and verifies the entire
memory for an all zero data pattern prior to electrical
erase. The system is not required to provide any controls or timings during these operations. Tables 12 and
13 shows the address and data requirements for the
chip erase command sequence. Note that the SecS i
Sector, autoselect, and CFI functions are unavailable
when a program operation is in progress.
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 immediately termina tes the erase operation. If tha t occurs, the chip erase command sequence should be
reinitiated once the device ha s returned to re ading
array data, to ensure data integrity.
Figure 7 illustrates the algorithm for the erase operation. Refer to the Erase and Program Operations tables in the AC Characteristics sectio n for parameters,
and Figure 19 section for timing diagrams.
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 wri tten, and are the n followed by the address of the sector to be erased, and
the sector erase command. Tables 12 and 13 shows
the address and data requirements for the sector
erase command sequence. Note that the SecSi Sec-
tor, autoselect, and CFI function s are unavailabl e
when a program operation is in progress.
The device does not require the system to preprogram
prior to erase. The Embedded Erase algorithm automatically programs an d verifies the entire me mory 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 s ector erase
time-out of 50 µs occurs. During the time-out period,
additional sector addresses and sector erase com mands may be written. Loading the sector er ase buf fer
may be done in any sequence, and the number of sectors may be from on e 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 comm and 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 comm ands are accepted. Th e
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 rewrite the command se-
quence and any additional addresses and commands.
The system can monitor DQ3 to determine if the sec-
tor erase timer has timed out (See the section on DQ3:
Sector Erase Timer.). The time-out begins fr om the ris-
30Am29LV320MT/BMay 16, 2003
DATASHEET
ing 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 Opera-
tion 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 er ase operation. If
that occurs, the sector e rase command sequen ce
should be reinitiated once the device has returned to
reading array data, to ensure data integrity.
Figure 7 illustrates the algorithm for the erase operation. Refer to the Erase and Program Operation s tables in the AC Characteristics sectio n for parameters,
and Figure 19 section for timing diagrams.
START
Write Erase
Command Sequence
(Notes 1, 2)
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 with in erase-suspende d 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-sus pended.
Refer to the Write Operation Status section for information on these status bits.
Data Poll to Erasing
Bank from System
No
Notes:
1. See Tables 12 and 13 for erase command sequence.
2. See the section on DQ3 for information on the sector
erase timer.
Data = FFh?
Yes
Erasure Completed
Embedded
Erase
algorithm
in progress
Figure 7. Erase Operation
After an eras e-sus pende d prog ram o pera tion 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.
To resume the sector erase operation, the system
must write the Erase Resume command. The address
of the erase-suspended sector is required when writing this command. Further writes of the Resume command are ignored. Another Erase Suspend com mand
can be written after the chip has resumed erasing.
(Note 10)
Enter SecSi Sector Region3555AA2AA5555588
Exit SecSi Sector Region4555AA2AA5555590XXX00
Program4555AA2AA55555A0PAPD
Write to Buffer (Note 11)6555AA2AA55SA25SAWCPAPDWBLPD
Program Buffer to Flash1SA29
Write to Buffer Abort Reset (Note 12) 3555AA2AA55555F0
Unlock Bypass3555AA2AA5555520
Unlock Bypass Program (Note 13)2XXXA0PAPD
Unlock Bypass Reset (Note 14)2XXX90XXX00
Chip Erase6555AA2AA5555580555AA2AA5555510
Sector Erase6555AA2AA5555580555AA2AA55SA30
Program/Erase Suspend (Note 15)1BAB0
Program/Erase Resume (Note 16)1BA30
CFI Query (Note 17)15598
Legend:
X = Don’t care
RA = Read Address of the memory location to be read .
RD = Read Da t a read from location RA d uring 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 o f
WE# or CE# pulse, whichever happens first.
First Second Third Fourth Fifth Sixth
Cycles
Addr DataAddrDataAddrDataAddrDataAddr Data Addr Data
4555AA2AA5555590X03(Note 9)
4555AA2AA5555590(SA)X0200/01
SA = Sector Address of sector to be verified (in autoselect m ode) or
erased. Address bits A20–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 mi nus 1 .
2200/
2201
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. During unlock cycles, when lower address bits are 555 or 2AAh
as shown in table, address bits higher than A11 (except where BA
is required) and data bits higher than DQ7 are don’t cares.
5. No unlock or command cycles required when device is in read
mode.
6. 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.
7. 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.
8. The device ID must be read in three cycles. The data is 2201h for
top boot and 2200h for bottom boot.
9. If WP# protects the top two address sectors, the data is 98h for
factory locked and 18h for not factory locked. If WP# protects the
bottom two address sectors, the data is 88h for factory locked and
08h for not factor locked.
10. The data is 00h for an unprotected sector group and 01h for a
protected sector group.
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. Command sequence resets device for next command after
aborted write-to-buffer operation.
13. The Unlock Bypass command is required prior to the Unlock
Bypass Program command.
14. The Unlock Bypass Reset command is required to return to the
read mode when the device is in the unlock bypass mode.
15. 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.
16. The Erase Resume command is valid only during the Erase
Suspend mode.
17. Command is valid when device is ready to read array data or when
device is in autoselect mode.
Enter SecSi Sector Region3AAAAA55555AAA88
Exit SecSi Sector Region4AAAAA55555AAA90XXX00
Program4AAAAA55555AAAA0PAPD
Write to Buffer (Note 11)6AAAAA55555SA25SABCPAPDWBLPD
Program Buffer to Flash1SA29
Write to Buffer Abort Reset (Note 12) 3AAAAA55555AAAF0
Unlock Bypass3AAAAA55555AAA20
Unlock Bypass Program (Note 13)2XXXA0PAPD
Unlock Bypass Reset (Note 14)2XXX90XXX00
Chip Erase6AAAAA55555AAA80AAAAA55555AAA10
Sector Erase6AAAAA55555AAA80AAAAA55555SA30
Program/Erase Suspend (Note 15)1BAB0
Program/Erase Resume (Note 16)1BA30
CFI Query (Note 17)1AA98
Legend:
X = Don’t care
RA = Read Address of the memory location to be read .
RD = Read Da t a read from location RA d uring 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 o f
WE# or CE# pulse, whichever happens first.
First Second Third Fourth Fifth Sixth
Cycles
Addr DataAddrDataAddrDataAddrDataAddr Data Addr Data
4AAAAA55555AAA90X06(Note 9)
4AAAAA55555AAA90(SA)X0400/01
SA = Sector Address of sector to be verified (in autoselect m ode) or
erased. Address bits A20–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 mi nus 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. During unlock cycles, when lower address bits are 555 or AAAh
as shown in table, address bits higher than A11 (except where BA
is required) and data bits higher than DQ7 are don’t cares.
5. No unlock or command cycles required when device is in read
mode.
6. 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.
7. 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.
8. The device ID must be read in three cycles. The data is 01h for
top boot and 00h for bottom boot
9. If WP# protects the top two address sectors, the data is 98h for
factory locked and 18h for not factory locked. If WP# protects the
bottom two address sectors, the data is 88h for factory locked and
08h for not factor locked.
10. The data is 00h for an unprotected sector group and 01h for a
protected sector group.
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. Command sequence resets device for next command after
aborted write-to-buffer operation.
13. The Unlock Bypass command is required prior to the Unlock
Bypass Program command.
14. The Unlock Bypass Reset command is required to return to the
read mode when the device is in the unlock bypass mode.
15. 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.
16. The Erase Resume command is valid only during the Erase
Suspend mode.
17. Command is valid when device is ready to read array data or when
device is in autoselect mode.
May 16, 2003Am29LV320MT/B33
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 14 and the following subsections d es cribe 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 comma nd sequence .
During the Embedded Prog ram algorithm, the devi ce outputs on DQ7 the complement of t he datum pr ogr ammed to
DQ7. This DQ7 status also applies to programming during
Erase Suspend. When t he Embedded Pr ogram algorit hm is
complete, the device outputs the datum programmed to
DQ7. The system must provide the program address to
read valid status in formation 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 14 shows the outputs for Data# Pollin g on DQ7.
Figure 8 shows the Data# Polling algorithm. Figure 20
in the AC Characteristics section sh ows the Data#
Polling timing diagram.
START
Read DQ7–DQ0
Addr = VA
Yes
No
DQ7 = Data?
No
DQ5 = 1?
During the Embedd ed Erase algorith m, Data# Pollin g
produces a “0” on DQ7. W hen the Embedde d 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 r ead valid statu s information on DQ7.
After an erase com mand sequen ce 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 unpr otected secto rs, and i gnores the selected sectors that are protected. However, if the system reads DQ7 at an address withi n 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 er ase operation and D Q7 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” beca use
DQ7 may change simultaneously with DQ5.
Yes
PASS
Figure 8. Data# Polling Algorithm
34Am29LV320MT/BMay 16, 2003
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 active ly 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 m ode. Table 14
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 pro gress or complete, or whether the device has entered the Erase
Suspend mo de. Toggle Bit I m ay be read at any a ddress, and is valid after the rising edge of the final
WE# pulse in the command sequence (prior to the
program or erase operation), and d uring 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 erasi ng are protec ted, DQ6 t oggle s for a pproximately 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 a re protect ed.
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 togg les. Whe n the d evice 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 µs after the program
command sequence is written, then returns to reading
array data.
DQ6 also toggles during the erase-suspend-program
mode, and stops toggling once the Embedded Program algorithm is complete.
Table 14 shows the outputs for Toggle Bit I on DQ6.
Figure 9 shows the toggle bit algorithm. Figure 21 in
the “AC Characteristics” section shows the toggle bit
timing diagrams. F igure 22 shows th e differences b etween DQ2 and DQ6 in graphical form. See also the
subsection on DQ2: Toggle Bit II.
May 16, 2003Am29LV320MT/B35
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 i s 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 era sing or is e rase-suspended. DQ6, by compa rison, indicates whe ther the
device is actively erasing, or is in Erase Suspend, but
cannot distinguish whic h sectors ar e selected for erasure. Thus, both status bits are required for sector and
mode inform ation. R efer to Table 14 to compare out-
puts 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#: Read y/Busy# subsection. Figure 21 shows the toggle bit timing diagram.
Figure 22 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 whe ther 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 comple ted the pr ogram or erase op eration. T he
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 toggl e 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 a gain 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 scena rio is that th e system i nitially determines that the toggle bit i s toggling a nd DQ5 h as
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
36Am29LV320MT/BMay 16, 2003
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
wri te -to -b uf fe r ti me has exceeded a specified internal
pulse count limit. Under these conditio ns 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 sys tem 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 lim it
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 determ ine whether or not
erasure has begun. (The sector erase timer does not
apply to the chip erase c ommand.) If additional
sectors are selected for erasure, the entire time-out
also applies afte r each ad ditional se ctor eras e com-
mand. When the time-out period is complete, DQ3
switches from a “0” to a “1.” If the time betwe en 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 acce pt additional sector eras e com mands.
To ensure the command has been a ccepted, the system software should check the status of DQ3 prior to
and following each subsequent sector erase command. If DQ3 is high on the sec ond status ch eck, the
last command might not have been accepted.
Table 14 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-Res et command sequence to return the device to reading array data. See W rite Buf fer
Table 14. Write Operation Status
DQ7
Status
Standard
Mode
Program
Suspend
Mode
Erase
Suspend
Mode
Write-to-
Buffer
Notes:
1. DQ5 switches to ‘1’ when an Embedded Program, Embedded Erase, or Write-to-Buffer operation has exceeded the
maximum timing limits. Refer to the section on DQ5 for more information.
2. DQ7 and DQ2 require a valid address when reading status infor mation. Refer to t he appro priate subsect ion f or fur ther detail s.
3. The Data# Polling algorithm should be used to monit or the last loaded write -buffer addre ss loc ation.
4. DQ1 switches to ‘1’ when the device has aborted the write-to-buffer operation.
Embedded Program AlgorithmDQ7#Toggle0N/ANo toggle00
Embedded Erase Algorithm0Toggle01ToggleN/A0
with Power Applied . . . . . . . . . . . . . –55°C to +125°C
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
ns. 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 oversho ot 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 outpu t may be shor ted to ground at a
time. Duration of the short c ircuit should n ot 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 co nditions above those i ndicated in the
operational sections of this data sheet is not implied.
Exposure of the device to absolute maximum rating
conditions for extended per iod s may affe ct dev ice relia bili ty.
to –2.0 V for periods of up to 20 ns.
SS
+2.0 V for periods up to 20
CC
SS
+0.5 V
CC
+0.5 V.
CC
to –2.0 V for
+0.8 V
–0.5 V
–2.0 V
V
+2.0 V
V
+0.5 V
2.0 V
20 ns
20 ns
Figure 10. Maximum Negative
Overshoot Waveform
20 ns
CC
CC
20 ns
Figure 11. Maximum Positive
Overshoot Waveform
20 ns
20 ns
OPERATING RANGES
Industrial (I) Devices
Ambient Temperature (T
Supply Voltages
V
for full voltage range . . . . . . . . . . . . . . . 2.7–3.6 V
CC
for regulated voltage range. . . . . . . . . . 3.0–3.6 V
V
CC
Note: Operating ranges define those limits between which
the functionality of the device is guaranteed.
38Am29LV320MT/BMay 16, 2003
) . . . . . . . . . –40°C to +85°C
A
DC CHARACTERISTICS
CMOS Compatible
DATASHEET
Parameter
Symbol
I
LI
I
LIT
I
LR
I
LO
I
CC1
Parameter Description
(Notes)Test Conditions MinTypMaxUnit
= VSS to VCC,
V
Input Load Current (1)
V
IN
= VCC
CC
A9, ACC Input Load CurrentVCC = V
Reset Leakage CurrentVCC = V
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 21. Toggle Bit Timings (During Embedded Algorithms)
Enter
Embedded
Erasing
WE#
Erase
Erase
Suspend
Erase Suspend
Suspend Program
Read
Enter Erase
Erase
Suspend
Program
Erase Suspend
Read
Erase
Resume
Erase
Erase
Complete
DQ6
DQ2
Note: DQ2 toggles only when read at an address within an erase-suspended sector. The system may use OE# or CE# to toggle
DQ2 and DQ6.
Figure 22. DQ2 vs. DQ6
48Am29LV320MT/BMay 16, 2003
AC CHARACTERISTICS
Temporary Sector Unprotect
Parameter
t
VID Rise and Fall Time (See Note)Min500ns
VIDR
RESET# Setup Time for Temporary Sector
t
RSP
Unprotect
Note: Not 100% tested.
DATASHEET
All Speed OptionsJEDECStdDescriptionUnit
Min4µs
RESET#
CE#
WE#
RY/BY#
V
ID
VSS, VIL,
or V
IH
t
VIDR
t
VIDR
Program or Erase Command Sequence
t
RSP
t
RRB
Figure 23. Temporary Sector Group Unprotect Timing Diagram
V
VSS, VIL,
or V
ID
IH
May 16, 2003Am29LV320MT/B49
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–A0 = 0xx0010. For sector group unprotect, A6–A0 = 1xx0010.
Figure 24. Sector Group Protect and Unprotect Timing Diagram
Status
50Am29LV320MT/BMay 16, 2003
DATASHEET
AC CHARACTERISTICS
Alternate CE# Controlled Erase and Program Operations
ParameterSpeed Options
JEDECStd.Description90R
t
AVAV
t
AVWL
t
ELAX
t
DVEH
t
EHDX
t
GHEL
t
WLEL
t
EHWH
t
ELEH
t
EHEL
t
t
GHEL
t
t
t
Write Cycle Time (Note 1)Min90100110120ns
WC
t
Address Setup TimeMin0ns
AS
t
Address Hold TimeMin45ns
AH
t
Data Setup TimeMin45ns
DS
t
Data Hold TimeMin0ns
DH
Read Recovery Time Before Write
(OE# High to WE# Low)
WE# Setup T i m eMin0ns
WS
WE# Hold T i meMin0ns
WH
t
CE# Pulse Widt hMin45ns
CP
CE# Pulse Width HighMin30ns
CPH
Min0ns
Write Buffer Program Operation (Notes 2, 3)Typ240µs
Per ByteTyp7.5µs
Per WordTyp15µs
Per ByteTyp6.25µs
Per WordTyp12.5µs
Byte
Typ
Word60µs
t
WHWH1
t
WHWH1
Effective Write Buffer Program
Operation (Notes 2, 4)
Accelerated Effective Write Buffer
Program Operation (Notes 2, 4)
Single Word/Byte Program Operation
(Note 2, 5)
100,
100R
110,
110R
60µs
120,
120RUnit
t
WHWH2
t
WHWH2
t
RH
Accelerated Single Word/Byte
Programming Operation (Note 2, 5)
Byte
Typ
Word54µs
Sector Erase Operation (Note 2)Typ0.5sec
RESET# High Time Before Write (Note 1)Min50ns
54µs
Notes:
1. Not 100% tested.
2. See the “Erase And Programming Performance” section for more i nformati on.
3. For 1–16 words (or 1–32 bytes in byte mode) programmed.
4. Effective write buffer specification is based upon a 16-wor d (or 32-byt e) wri te buf fer operati on.
5. Word/Byte programming specification is based upon a single word/byte programming operation not utilizing the write buffer.
May 16, 2003Am29LV320MT/B51
AC CHARACTERISTICS
DATASHEET
Addresses
WE#
OE#
CE#
Data
RESET#
555 for program
2AA for erase
t
WC
t
WH
t
WS
t
RH
PA for program
SA for sector erase
555 for chip erase
t
AS
t
GHEL
t
CP
t
CPH
t
DS
t
DH
A0 for program
55 for erase
t
AH
t
PD for program
30 for sector erase
10 for chip erase
BUSY
Data# Polling
t
WHWH1 or 2
PA
DQ7#D
OUT
Notes:
1. Figure indicates last two bus cycles of a program or erase operation.
RY/BY#
2. PA = program address, SA = sect or addr ess, PD = prog ram data .
3. DQ7# is the complement of the data written to the device. D
Accelerated Single Word/Byte Program Time
(Note 3)
Total Write Buffer Program Time (Note 4)2401200µs
Effective Write Buffer Program Time (Note 5)
Total Accelerated Write Buffer Program Time (Note 4)2001040µs
Effective Accelerated Write Buffer Program Time
(Note 5)
Chip Program Time 31.573sec
Byte60600µs
Word60600µs
Byte54540µs
Word54540µs
Per Byte7.538µs
Per Word1575µs
Per Byte6.2533µs
Per Word12.565µs
Notes:
1. Typical program and erase times assume the following conditions: 25°C, 3.0 V V
, Programming specification assume that
CC
all bits are programmed to 00h.
2. Maximum values are measured at V
= 3.0, worst case temperature. Maximum val ues ar e vali d up t o and i ncludi ng 100,0 00
CC
program/erase cycles.
3. Word/Byte programming specification is based upon a s ingle word/byt e progr amming ope ration not ut ili zing the wri te buf fer.
4. For 1-16 words or 1-32 bytes programmed in a single writ e buff er prog ramming op erati on.
5. Effective write buffer specification is calcul ated on a per-word/per-byte basis for a 16- word/32- byte wr ite buffer operation.
6. In the pre-programming step of the Embedded Erase algor ithm, all bits are pr ogrammed to 00h bef ore er asure.
7. System-level overhead is the time required to execute t he command sequence (s) for the progra m command. See Tables 12 and
13 for further information on command defin ition s.
8. The device has a minimum erase and program cycle endurance of 100,000 cycles.
Excludes 00h programming
prior to erasure (Note 6)
Excludes system level
overhead (Note 7)
LATCHUP CHARACTERISTICS
DescriptionMinMax
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.
Alternate CE# Controlled Erase and Program
Operations
Added t
Erase and Program Operations
Added t
CMOS Compatable
Deleted the I
tics table.
Figure 16. Program Operation Timings
Added RY/BY# to waveform.
TSOP and BGA PIN Capacitance
Added the FBGA package.
Program Suspend/Program Resume Command
Sequence
Changed 15 µs typical to maximum and added 5 µs
typical.
Erase Suspend/Erase Resume Commands
Changed typical from 20 µs to 5 µs and added a maximum of 20 µs.
Mirrorbit 32 Mbit Device Family
Changed 48-pin TSOP to 40-pin TSOP.
parameter to table.
RH
parameter to table.
BUSY
specification row in DC Characteris-
ACC
Revision A+2 (September 19, 2002)
Distinctive Characteristics
Changed the flexible sector architecture from
Sixty-four 32 Kword/64-Kbyte sectors to Sixty-thr ee 32
Kword/64-Kbyte sectors.
Revision A+3 (November 19, 2002)
Product Selector Guide and Read Only Operations
Changed the page access times and T
Moved the reverse speed options up into correct row.
Changed V
range for full speed option to 2.7-3.6.
CC
Ordering Information and Physical Dimensions
Removed FBD048 package.
Added FBC048 package.
Added TS048 package.
Changed order numbers and package markings to re-
flect new package.
Table 7. SecSi Sector Contents
Changed the x8 Secsi Sector Address range to
000010h–0000FFh.
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 unloc k byp ass m odes
are not available when the SecSi sector is enabled.
OE
Product Selector Guide, V alid Combinations T able,
Read-Only Operations, Erase and Program
Operations and Alternate CE# Controlled Erase
and Program Operations
Added regulated OPN to table.
Common Flash Memory Inter face
Changed the text in the third paragraph to end with ”...
reading array data.”
Command Definitions
Modified the last sentences in the first paragraph.
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.
May 16, 2003Am29LV320MT/B59
DATASHEET
Erase and Programming Performance
Changed the typicals and/or maximums of the Chip
Erase Time, Effective Write Buffer Program Time,
Byte/Word Program Time, and Accelerated Effective
Program Time to TBD.
Revision A+4 (February 16, 2003)
Erase and Programming Performance
Input values into table that were previously TBD.
Added note 3 and 4
Revision B (May 16, 2003)
Distinctive Characteristics
Added typical active read current
Distinctive Characteristics
Corrected performance characteristics.
Product Selector Guide
Added note 2.
Ordering Information
Corrected Valid Combinations table.
Added Note.
AC Characteristics
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 note 5.
Input values in the t
WHWH
1 and t
2 parameters in
WHWH
the Alternate CE# Controlled Erase and Program Options table that were previously TBD. Also, added note
5.
Global
Converted to full datasheet version.
Modified SecSi Sector Flash Memory Region section
to include ESN references.
CMOS Compatible
Corrected Typ and Max values for the I
CC 1, 2, and 3
.
Erase and Program Operations and Alternate CE#
Controlled Erase and Program Operations
Changed Accelerated Effective Write Buffer Program
Operation value.
Erase and Programming Performance
Input values into table that were previously TBD.
Modified notes.
Removed Word references.
Advanced Micro Devices reserves the right to make changes in its product without notice
in order to impr
characteristics listed in this document are guaranteed by specific tests, guard banding,
design and other practices common to the industry. For specific testing details, contact
your local AMD sales representativ
any circuits described herein.