The following document specifies Spansion memory products that are now offered by both Advanced
Micro Devices and Fujitsu. Although the docu ment is ma rked with the name o f the comp any that o riginally 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. Future routine revisions will occur when appropriate,
and changes will be noted in a revision summary.
Continuity of Ordering Part Numbers
AMD and Fujitsu continue to support existing part numbers beginning with “Am” and “MBM”. To order
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 Spansion
memory solutions.
Publication Number 21359 Revision E Amendment +1 Issue Date November 7, 2000
Page 2
Am29LV116D
16 Megabit (2 M x 8-Bit)
CMOS 3.0 Volt-only Boot Sector Flash Memory
DISTINCTIVE CHARACTERISTICS
■ Single power supply operation
— 2.7 to 3.6 volt read and write operations for
battery-powered applications
■ Manufactured on 0.23 µm process technology
— Compatible with and replaces Am29LV116B
device
■ High performance
— Access times as fast as 70 ns
■ 20-year data retention at 125°C
— Reliable operation for the life of the system
■ Package option
— 40-pin TSOP
■ CFI (Common Flash Interface) compliant
— Provides device-specifi c information to the
system, allowing host software to easily
reconfigure for different Flash devices
■ Ultra low power consumption (typical values at
5MHz)
— 200 nA Automatic Sleep mode current
— 200 nA standby mode current
— 9 mA read current
— 15 mA program/erase current
any program or erase operations within that sector
Sectors can be locked in-system or via
programming equipment
Temporary Sector Unprotect f eatur e allows code
changes in previously locked sectors
■ Unlock Bypass Program Command
— Reduces overall programming t ime when issuing
multiple program command sequences
■ Top or bottom boot block configurations
available
■ Compatibility with JEDEC standards
— Pinout and software compatible with single-
power supply Flash
— Superior inadvertent write protection
■ Data# Polling and toggle bits
— Provides a software method of detecti ng program
or erase operation completion
■ Ready/Busy# pin (RY/ BY#)
— Provides a hardware method of detecting
program or erase cycle completion
■ Erase Suspend/Erase Resume
— Suspends an erase operation to read data from,
or program data to, a sector that is not being
erased, then resumes the erase operation
■ Hardware reset pin (RESET#)
— Hardware method to reset the device to reading
array data
■ Embedded Algorithms
— Embedded Erase algorithm automatically
preprograms and erases the entire chip or any
combination of designated sectors
— Embedded Program algorithm automatically
writes and verifies data at specified addresses
■ Minimum 1,000,000 write cy cle guarantee
per sector
This Data Sheet states AMD’s current technical specifications regarding the Product described herein. This Data
Sheet may be revised by subsequent versions or modificat ions due to changes in technical specif ic ations.
Publication# 21359 Rev: E Amendment/+1
Issue Date: November 7, 2000
Page 3
GENERAL DESCRIPTION
The Am29LV116D is a 16 Mbit, 3.0 Volt-only Flash
memory organized as 2,097,152 bytes. The device is
offered in a 40-pin TSOP package. The byte-wide (x8)
data appears on DQ7–DQ0. All read, program, and
erase operations are accomplished using only a single
power supply. The device can also be programmed in
standard EPROM programmers.
The standard device off ers access times of 70, 90, and
120 ns, allowing high speed microprocessors to
operate without wait states. To eliminate bus cont ention
the device has separate chip enable (CE#), write
enable (WE#) and output enable (OE#) controls.
The device requires only a single 3. 0 v o lt po wer sup-ply for both read and write functions. Internally generated and regulated voltages are provided for the
program and erase operations.
The device is entirely command set compatible with the
JEDEC single-power-supply Flash standard. Commands are written to the command register using standard microproc essor write timing s. Register contents
serve as input to an internal sta te-machine that co ntrols the erase and programming circuit ry. Write cycles
also internally latch addresses and data needed f or the
programming and erase operations. Reading data out
of the device is similar to reading from other Flash or
EPROM devices.
Device programming occurs by executing the program
command sequence. This initiates the EmbeddedProgram algorithm—an internal algorithm that automatically times the program pulse widths and verifies
proper cell margin. The Unlock Bypass mode facilitates faster programming times by requir ing only two
write cycles to program data instead of four.
Device erasure occurs by executing the erase command sequence. This initiates the Embedded Erase
algorithm—an in ternal algorithm that autom atically
preprograms the array (if it is not already prog rammed)
before e xecuting the erase operation. During erase, the
device automatically times the erase pulse widths and
verifies proper cell margin.
The host system can detect whether a program or
erase operation is complete by observing the RY/BY#
pin, or by reading the DQ7 (Data# Polling) and DQ6
(toggle) status bits. After a prog ram or erase cycle has
been completed, the device is ready to read array data
or accept another command.
The sector erase archite cture allo ws m emory sect ors
to be erased and reprogrammed without affecting the
data contents of other sectors. The device is fully
erased when shipped from the factory.
Hardware data protection measures include a low
detector that automatically in hibits write opera-
V
CC
tions during power transitions. The hardware sector
protection feature disables both program and erase
operations in any combination of the sectors of memory. This can be achieved in-system or via programming equipment.
The Erase Suspend feature enables the user to put
erase on hold for any period of time to read data from,
or program data to, any sector that is not selected for
erasure. True background erase can thus be achieved.
The hardware RESET# pi n terminates any operation
in progress and resets the internal state machine to
reading array dat a. The RESET# pin ma y be tied to the
system reset circuitry. A system reset would thus also
reset the device, enabling the system microprocessor
to read the boot-up firmware from the Flash memory.
The device off ers two power-sa ving f eatures. When addresses have been stable for a specified amount of
time, the device enters the automatic sleep m ode.
The system can also place the de vice into the standbymode. Power consumption is greatly reduced in both
these modes.
AMD’s 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 bi ts with in
a s e ct or simultaneously via Fowler-Nordheim tunneling. 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 elements below.
Am29LV116DT-70EC
TEMPERATURE RANGE
C=Commercial (0°C to +70°C)
I = Industr ial (–40
PACKAGE TYPE
E=40-Pin Thin Small Outline Package (TSOP)
Standard Pinout (TS 040)
F=40-Pin Thin Small Outline Package (TSOP)
Reverse Pinout (TSR040)
SPEED OPTION
See Product Selector Guide and Valid Combinations
BOOT CODE SECTOR ARCHITECTURE
T= Top Sector
B= Bottom Sector
DEVICE NUMBER/DESCRIPTION
Am29LV116D
16 Megabit (2 M x 8-Bit) CMOS Flash Memory
3.0 Volt-only Read, Program and Erase
°C to +85°C)
Am29LV116DT-70,
Am29LV116DB-70
Am29LV116DT-90,
Am29LV116DB-90
Am29LV116DT-120,
Am29LV116DB-120
Valid Combinations
EC, EI, FC, FI
Valid Combinations
Valid Combinations list configurations planned to be supported in volume f or this device. Consult the local AMD sales
office to confirm av ailability of specific valid combinations and
to check on newly released combinations.
Am29LV116D7
Page 9
DEVICE BUS OPERATIONS
This section describes the requirements and use of the
device bus operations, which are initiated through the
internal c ommand register. The command register itself does not occupy any addressable memory location. The register is composed of l atches that store the
commands, along with the address and data information needed to execute the command. The contents of
Table 1. Am29LV116D Device Bus Operations
OperationCE#OE#WE#RESET#AddressesDQ0–DQ7
ReadLLHHA
WriteLHLHA
±
V
Standby
Output DisableLHHHXHigh-Z
ResetXXXLXHigh-Z
Sector Protect (See Note)LHLV
Sector Unprotect (See Note)LHLV
Temporary Sector UnprotectXXXV
Legend:
L = Logic Low = V
Note: The sector protect and sector unprotect functions may also be implemented via programming equipment. See the “Sector
Protection/Unprotection” section.
, H = Logic High = VIH, VID = 12.0 ± 0.5 V, X = Don’t Care, AIN = Address In, DIN = Data In, D
IL
CC
0.3 V
XX
the 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
inputs and control lev els t he y requ ire , and t he resulting
output. The following subsections describe each of
these operations in further detail.
D
D
, D
D
IN
, D
D
IN
D
= Data Out
OUT
OUT
IN
OUT
OUT
IN
V
CC
0.3 V
ID
ID
ID
±
Sector Addresses,
A6 = L, A1 = H, A0 = L
Sector Addresses
A6 = H, A1 = H, A0 = L
IN
IN
XHigh-Z
A
IN
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 arra y data to the output pins . WE# should
remain at V
.
IH
The internal state machine is set for reading arr ay 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 input s produc e 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 Operations table for timing specifications and to Figure 13 for the timing diagram. I
the DC Characteristics table represents the active current specification for reading array data.
. CE# is the power
IL
CC1
in
Writing Commands/Command Sequences
To wr ite 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 f eatures an Unlock Bypass mode to facili-
tate faster programming. Once the device enters the
Unlock Bypass mode, only two write cycles are required to program a byte, instead of four. The “Byte
Program Command Sequence” section has details on
programming data to the device using both standard
and Unlock Bypass command sequences.
An erase operation can erase one sect or, multiple sectors, or the entire device. Tables 2 and 3 indic ate the
address space that each sector occupies. A “sector address” consists of the address b its requ ired to uni quely
select a sector. The “Command D efinitions” section
has details on erasing a sector or the entire chip, or
suspending/resuming the erase operation.
After the system writes the autoselect command sequence, the device enters the autoselect mode. The
system can then read autoselect codes from the internal register (which is separate from the memory array)
on DQ7–DQ0. Standard read cycle timings apply in this
, and OE# to VIH.
IL
8Am29LV116D
Page 10
mode. Refer to the Autoselect Mode and Autoselect
Command Sequence sections for more information.
in the DC Characteristics table represents the ac-
I
CC2
tive current specification for the write m ode. The “AC
Characteristics” section contains timing specification
tables and timing diagrams for write operations.
Program and Erase Operation Status
During an erase or program operation, the system ma y
check the status of the operation by reading the status
bits on DQ7–DQ0. Standard read cycle timings and I
CC
read specifications apply. Refer to “Write Operation
Status” for more information, and to “AC Characteristics” for timing diagrams.
Standby Mode
When the system is not reading or writing to the device ,
it can place the device in the standby mode. In this
mode, current consumption is great ly 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
0.3 V.
CE# and RESET# pin s are both held at V
CC
±
(Note that this is a more restricted voltage range than
V
.) If CE# and RESET# ar e held a t VIH, but not within
IH
0.3 V, the device will be in the standby mode, b ut
±
V
CC
the standby current will be greater. The device requires
standard access time (t
) for read access when the
CE
device is in either of these standby modes, before it is
ready to read data.
The device also enters the standb y mode when the RESET# pin is driven low. Refer to the next section, “RESET#: Hardware Reset Pin”.
If the device is deselected during erasure or programming, the device draws active current until the
operation is completed.
in the DC Characteristics table represents the
I
CC3
standby current specification.
Automatic Sleep Mode
The automatic sleep mode minimizes Flash device
energy consumption. The de vice automatically enab les
this mode when addresses remain stable for t
ns. The automatic sleep mode is independent of the
CE#, WE#, and OE# control signals. Standard addres s
ACC
+ 30
access timings provide new data when addresses are
changed. While in sleep mode, output data is latched
and always available to the system. I
in the DC
CC5
Characteristics table represents the automatic sleep
mode current specification.
RESET#: Hardware Reset Pin
The RESET# pin provides a hardw are method of resetting the device to reading array data. When the RESET# 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 inter nal 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 c urrent (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.
If RESET# is asserted during a program or erase operation, the RY/BY# pin remains a “0” (busy) until the internal reset operatio n is complete, which requires a
time of t
(during Embedded Algorithms). The
READY
system can thus monitor RY/BY# to determine whether
the reset operation is complete. If RESET# is asserted
when a program or erase operation is not executing
(RY/BY# pin is “1”), the reset operation is completed
within a time of t
rithms). The system can read data t
SET# pin returns to V
(not during Embe dded Algo-
READY
.
IH
RH
after the RE-
Refer to the AC Characteristics tables for RESET# parameters and to Figure 14 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 t he high impedance state.
Am29LV116D9
Page 11
Table 2. Am29LV116DT Top Boot Sector Address Table
The autoselect mode provides manufacturer and device identification, and sector protection verification,
through identifier codes output on DQ7–DQ0. This
mode is primarily intended for progr amming equipment
to automatically match a device to be progr ammed with
its correspondi ng programming al gorithm. However,
the autoselect codes can also be accessed in-system
through the command register.
When using programming equipment, the autoselect
mode requires V
A9. Address pins A6, A1, and A0 must be as shown in
(11.5 V to 12.5 V) on address pin
ID
Ta ble 4. In addition, when verifying sec tor 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 don’t care .
When all necessary bits have been set as required, the
programming equipment may then read the corresponding identifier code on DQ7-DQ0.
To access the autoselect codes in-system, the host
system can issue the autoselect command via the
command register, as shown in Ta ble 9. This method
does not require V
details on using the autoselect mode.
Table 4. Am29LV116D Autoselect Codes (High Voltage Method)
A20
A12
to
to
DescriptionCE#OE#WE#
Manufacturer ID: AMDLLHXXV
Device ID: Am29LV116D
(Top Boot Block)
Device ID: Am29LV116D
(Bottom Boot Block)
LLHXXV
LLHXXV
A13
A10A9
. See “Command Definitions” for
ID
A8
to
A7A6
XLXLL01h
ID
XLXLHC7h
ID
XLXLH4Ch
ID
A5
to
A2A1A0
DQ7
to
DQ0
Sector Protection VerificationLLHSAXV
L = Logic Low = VIL, H = Logic High = VIH, SA = Sector Address, X = Don’t care.
Sector Protection/Unprotection
The hardware sector protection feature disables both
program and erase operations in any sect or. The hardware sector unprotection feature re-enables both program and erase operations in previously protected
sectors. Sector protection/unprotecti on can be implemented via two methods.
The primary method requires V
only, and can be implemented either in-system or via
on the RESET# pin
ID
lication number 21586 contains further details; contact
an AMD representative to request a copy.
The device is shipped with all sectors unprotected.
AMD offers the option of programming and protecting
sectors at its factory prior to shipping the device
through AMD’s ExpressFlash™ Servic e. Contact an
AMD representative for details.
It is possible to determine whether a sector is protected
or unprotected. See “Autoselect Mode” for details.
XLXHL
ID
programming equipment. Figure 1 shows the algorithms and Figure 21 shows the timing diagram. This
method uses standard m icroprocessor bus cycle timing. For sector unprotect, all unprotected sectors must
first be protected prior to the first sector unpro tect write
cycle.
The alternate method intended on ly for programming
equipment requires V
on address pin A9 and OE#.
ID
This method is compatible with programmer routines
written for earlier 3.0 v olt-only AMD flash de vices. Pub-
Temporary Sector Unprotect
This feature allows temporary unprotection of previously protected sectors to change data in-system. The
Sector Unprotect mode is activated by setting the RESET# pin to V
sectors can be programmed or erased b y selecting the
sector addresses. Once V
SET# pin, all the previously protected sectors are
protected again. Figure 2 shows the algorithm, and
Figure 20 shows the timing diagrams, for this feature.
against inadverten t writes (refer to Table 9 for command definitions). In addition, the following hardwar e
data protection mea sures prevent accidental erasure
or programming, which might otherwise be caused by
spurious system level signals during V
power-up and
CC
power-down transitions, or from system noise.
Low V
When V
Write Inhibit
CC
is less than V
CC
, the device does not ac-
LKO
cept any write cycles. This protects data during V
power-up and power-down. The command register and
all internal program/erase circuits are disabled, and the
device resets. Subsequent writes are ignored until V
is greater than V
. The system must provide the
LKO
proper signals to the control pins to prevent unintentional writes when V
is greater than V
CC
LKO
.
Write Pulse “Glitch” Protection
Noise pulses of less than 5 ns (typical) on OE#, CE# or
WE# do not initiate a write cycle.
CC
CC
Notes:
1. All protected sectors unprotected.
2. All previously protected sectors are protected once
again.
Figure 2. Temporary Sector Unprotect Operation
Hardware Data Protection
The command sequence requirement of unlock cycles
for programming or erasing provides data protection
COMMON FLASH MEMORY INTERFACE
(CFI)
The Common Flash Inte rface (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. S oftware support can then be de vice-independent, JEDEC ID-independent, and forward- and backward-compatible for t he specified flash device families.
Flash vendors can standardize t heir existing interf aces
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 de vice is ready to read array
Logical Inhibit
Write cycles are inhibited by holding any one of OE# =
, CE# = VIH or WE# = VIH. To initiate a wr ite 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 , the
IL
device does not accept commands on the rising edge
of WE#. The internal state mac hine is automatically
reset to reading array data on power-up.
data. The system can read CFI information at the
addresses given in Tables 5–8. 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 5–8. The
system must write the reset command to return the
device to the autoselect mode.
For further information, please refer to the CFI Specification and CFI Publication 100, a vailable via the W orld
Wide Web at http://www.amd.com/products/nvd/overview/cfi.html. Alternatively, contact an AMD representative for copies of these documents.
14Am29LV116D
Page 16
Table 5. CFI Query Identification String
AddressesDataDescription
10h
11h
12h
13h
14h
15h
16h
17h
18h
19h
1Ah
51h
52h
59h
02h
00h
40h
00h
00h
00h
00h
00h
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 6. System Interface String
AddressesDataDescription
Min. (write/erase)
V
1Bh27h
1Ch36h
1Dh00hV
1Eh00hV
1Fh04hTypical timeout per single byte/word write 2
20h00hTypical timeout for Min. size buffer write 2
21h0AhTypical timeout per individual block erase 2
22h00hTypical timeout for full chip erase 2
23h05hMax. timeout for byte/word write 2
24h00hMax. timeout for buffer write 2
25h04hMax. timeout per individual block erase 2
26h00hMax. 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
Am29LV116D15
Page 17
Table 7. Device Geometry Definition
AddressesDataDescription
N
27h15hDevice Size = 2
byte
28h
29h
2Ah
2Bh
2Ch04hNumber of Erase Block Regions within device
2Dh
2Eh
2Fh
30h
31h
32h
33h
34h
35h
36h
37h
38h
39h
3Ah
3Bh
3Ch
00h
00h
00h
00h
00h
00h
40h
00h
01h
00h
20h
00h
00h
00h
80h
00h
1Eh
00h
00h
01h
Flash Device Interface description (refer to CFI publication 100)
Max. number of byte in multi-byte write = 2
(00h = not supported)
Erase Block Region 1 Information
(refer to the CFI specification or CFI publication 100)
Erase Block Region 2 Information
Erase Block Region 3 Information
Erase Block Region 4 Information
N
Table 8. Primary Vendor-Specific Extended Query
AddressesDataDescription
40h
41h
42h
43h31hMajor version number, ASCII
44h30hMinor version number, ASCII
45h00h
46h02h
47h01h
48h01hSector Temporary Unprotect: 00 = Not Supported, 01 = Supported
49h04h
4Ah00hSimultaneous Operation: 00 = Not Supported, 01 = Supported
4Bh00hBurst Mode Type: 00 = Not Supported, 01 = Supported
4Ch00h
50h
52h
49h
Query-unique ASCII string “PRI”
Address Sensitive Unlock
0 = Required, 1 = Not Required
Erase Suspend
0 = Not Supported, 1 = To Read Only, 2 = To Read & Write
Sector Protect
0 = Not Supported, X = Number of sectors in per group
Page Mode Type: 00 = Not Supported, 01 = 4 Word Page,
02 = 8 Word Page
16Am29LV116D
Page 18
COMMAND DEFINITIONS
Writing specific addres s and data commands or sequences into the command register initiates device operations. Table 9 defines the valid registe r command
sequences. Writing incorrectaddress and data val-ues or writing them in the improper sequence resets
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 appropriate timing diagrams in the
“AC Characteristics” section.
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 also ready to read array
data after comp leting an Embe dded Program or Embedded Erase algorithm.
After the device accepts an Er ase Suspend command,
the device enters the Erase Suspend mode. The system can read array data using the standard read timings, except that if it reads at an address within erasesuspended sectors, the device outputs status data.
After completing a programming operation in the Erase
Suspend mode, the system may once agai n read arra y
data with the same exception. See “Erase Suspend/Erase Resume Commands” for more information
on this mode.
The reset command may be written between the sequence cycles in an autoselect command sequence.
Once in the autoselect mode, t he reset c ommand
be written to return to reading array data (also applies
to autoselect during Erase Suspend).
If DQ5 goes high during a program or erase operation,
writing the reset command returns the device to reading array data (also applies during Erase Suspend).
must
Autoselect Command Sequence
The autoselect c ommand sequenc e allows the host
system to access the manufacturer and devices codes,
and determine whether or not a sector is protected.
T ab le 9 shows the address and data requirements. This
method is an alternative to that shown in Table 4, which
is intended for PROM programmers and requi res V
on address bit A9.
The autoselect command sequence is initiated by writing two unlock cycles, followed by the autoselect command. The device then enters the autoselect m ode,
and the system may read at any address any number
of times, without initiating another command sequenc e.
A read cycle at address XX00h retrieves the manufacturer code. A read cycle at address XX01h returns the
device code. A read cycle containing a sector address
(SA) and the address 02h returns 01h if that sector is
protected, or 00h if it is unprotected. Refer to Tables 2
and 3 for valid sector addresses.
ID
must
The system
able the dev ice f or reading arra y data if DQ5 goes high,
or while in the autoselect mode. See the “Reset Command” section, next.
See also “Requirements for Reading Arr a y Data” in the
“Device Bus Operations” section for more information.
The Read Operations table provides the read parameters, and Figure 13 shows the timing diagram.
issue the reset command to re-en-
Reset Command
Writing the reset command to the devi ce resets the device to reading array data. Address bits are don’t care
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 reading array
data. 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
reading array data (also applies to programming in
Erase Suspend mode). Once programming begins,
however, the device ignores reset commands until the
operation is complete.
The system must write the reset command to exit the
autoselect mode and return to reading array data.
Byte Program Command Sequence
The device progr ams one byte of data f or each prog ram
operation. The command sequence requires four bus
cycles, and is initiated by wr iting two unlock write cy cles, followed by the program set-up command. The
program address and data are written next, which in
turn initiate the Embedded Program algorithm. The
not
system is
ings. The device automatically generates the program
pulses and verifies the programmed cell margin. Table
9 shows the address and data re quirements for the
byte program command sequence.
When the Embedded Program algorithm is complete,
the device then returns to reading array data and addresses are no longer latched. The system can determine the status of the program operation b y using DQ7,
DQ6, or RY/BY#. See “Write Operation Status” 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 programming operation. The Byte Program command se-
required to provide further controls or tim-
Am29LV116D17
Page 19
quence should be reinitiated once the device has reset
to reading array data, to ensure data integrity.
Programming is allowed in any sequence an d across
sector boundaries. A bit cannot be programmedfrom a “0” back to a “1”. Attempting to do so may halt
the operation and set DQ5 to “1,” or cause the Data#
Polling algorithm to indicate the op eration was successful. However, a succeeding read will show that the
data is still “0”. Only erase operations can convert a “0”
to a “1”.
Unlock Bypass Command Sequence
The unlock bypass feature allows the system to program bytes to t he de vice f aster than using the standard
program command sequence. The unlock b ypass command sequence is initiated by first writin g two unlock
cycles. This is followed b y a third write cycle containing
the unlock bypass command, 20h. The de v ice then enters the unlock bypass mode. A two-cycle unlo ck 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. Table 9 shows t he requirements f or the command sequence.
Increment Address
Embedded
Program
algorithm
in progress
START
Write Program
Command Sequence
Data Poll
from System
Verify Data?
No
Last Address?
Programming
Completed
No
Yes
Yes
During the unlock bypass mode, o nly 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 the data 00h. Add resses are
don’t cares for both cycles. The device then returns to
reading array data.
Figure 3 illustrates the algorithm for the program operation. See the Erase/Program Operations table in “AC
Characteristics” for parameters, and to Figure 15 for
timing diagrams
Note: See Table 9 for program command sequence.
Figure 3. Program Operation
Chip Erase Command Sequence
Chip erase is a six bus cycle opera tion. The chip er ase
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 patter n prior to electr ical
erase. The system is not required to provide any controls or timings during these operations. Table 9 shows
the address and data requirements for the chip erase
command sequence.
Any commands written to the chip during the Embedded Erase algorithm are ignored. Note that a ha rd warereset during the chip erase operation immediately terminates the operation. The Chip Erase command sequence should be reinitiated once the device has
returned to reading array data, to ensure data int eg rity.
require the system to
18Am29LV116D
Page 20
The system can determine the status of the erase operation by using DQ7, DQ6, DQ2, or RY/BY#. See
“Write Operation Status” for information on these status bits. When the Embedded Erase algorithm is complete, the device returns to reading array data and
addresses are no longer latched.
When the Embedded Erase algorithm is complete, the
device returns to reading arra y data and addr esses are
no longer latched. The system can determine the status of the erase operation b y using DQ7, DQ6, DQ2, or
RY/BY#. ( Refer to “Write Ope ration St atus” f or info rmation on these status bits.)
Figure 4 illustrates the algorithm for the erase operation. See the Erase/Program Operations tables in “AC
Characteristics” for parameters, and to Figure 16 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 write cycles are then followed by the
address of the sector to be erased, and the sector
erase command. Table 9 shows the address and data
requirements for the sector eras e command sequence.
not
The device does
the memory prior to erase. The Embedded Erase algorithm automatically programs and verifies the sector f or
an all zero data pattern prior to electrical erase. The
system is not required to provide a ny controls or timings during these operations.
After the command sequence is written, a sector erase
time-out of 50 µs begi ns. During the time-out per iod,
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 secto rs. The time between these additional cycl es must be less than 50 µs,
otherwise the last address and command might not be
accepted, and erasure may begin. It is recommended
that processor interrupts be disab led during this time to
ensure all commands are accepted. The interrupts can
be re-enabled after the last Sector Erase command is
written. If the time between additional sector erase
commands can be assumed to be less than 50 µs, the
system need not monitor DQ3. Any command other
than Sector Erase or Erase Suspend during the
time-out period resets the device to reading array
data. The system must rewrite the command sequence
and any additional sector addresses and commands.
The system can monitor DQ3 to determine if the sector
erase timer has timed out. (See the “DQ3: Sec tor Erase
Timer” section.) The time-out be gins from the rising
edge of the final WE# pulse in the command sequence .
Once the sector erase operation has begun, onl y the
Erase Suspend command is valid. All other commands
are ignored. Note th at a hardware reset during the
sector erase operation immediately terminates the operation. The Sector Erase command sequence should
be reinitiated once the device has returned to reading
array data, to ensure data integrity.
require the system to preprogram
Figure 4 illustrates the algorithm for the erase operation. Refer to the Erase/Program Operations tables in
the “AC Characteristics” section for parameters , and to
Figure 16 for timing diagrams.
Erase Suspend/Erase Resume Commands
The Erase Suspend command allows t he syste m to interrupt a sector erase ope ration 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 time-out period 50 µs
during the sector erase c ommand sequence. The
Erase Suspend command is ignored if written during
the chip erase operation or Embedded Program algorithm. Writing the Erase Suspend command during the
Sector Erase time-out immediately terminates the
time-out period and suspends the er ase oper at ion. Addresses are “don’t-cares” when writing the Erase Suspend command.
When the Erase Suspend command is written during a
sector erase operation, the de vice requires a maximum
of 20 µs to suspend the erase operation. However,
when the Erase Suspend command is written during
the sector erase time-out, the device immediately terminates the time-out period and suspends the erase
operation.
After the erase operation has been suspended, the
system can read array data from or program data to
any sector not selected for erasu re. (The de vice “er ase
suspends” all sectors selected for erasure.) Normal
read and write timings and command definitions apply.
Reading at any address within erase-suspended sectors produces status data on DQ7–DQ0. The system
can use DQ7, or DQ6 and DQ2 together, to determine
if a sector is actively erasing or is erase-suspended.
See “Write Operation Status” for information on these
status bits.
After an erase-suspended program operation is complete, the system c an once again r ead arra y d ata within
non-suspended sectors. The system can determine
the status of the program operation using the DQ7 or
DQ6 status bits, just as in the standard program operation. See “Write Operation Status” for more information.
The system may also write the autoselect command
sequence when the device is in the Erase Suspend
mode. The device allows reading autoselect codes
even at addresses within erasing sectors, since the
codes are not stored in the memory array. When the
Am29LV116D19
Page 21
device exits the autoselect mode, the device reverts to
the Erase Suspend mode, and is ready for another
valid operation. See “Autoselect Command Sequence”
for more information.
The system must write the Erase Resume command
(address bits are “don’t care”) to exit the erase suspend
mode and continue the sector erase operat ion. Further
writes of the Resume command are ignored. Another
Erase Suspend command can be written after the device has resumed erasing.
START
Write Erase
Command Sequence
Data Poll
from System
No
Data = FFh?
Erasure Completed
Embedded
Erase
algorithm
in progress
Yes
Notes:
1. See Table 9 for erase command sequence.
2. See “DQ3: Sector Erase Timer” for more information.
X = Don’t care
RA = Address of the memory location to be read.
RD = Data read from location RA during read operation.
PA = Address of the memory location to be programmed.
Addresses are latched on the falling edge of the WE# or CE#
pulse.
Notes:
1. See Table 1 for descriptions of bus operations.
2. All values are in hexadecimal.
3. Except when reading array or autoselect data, all bus
cycles are write operations.
4. Address bits A20–A11 are don’t care for unlock and
command cycles, except when PA or SA is required.
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 when the device is in the autoselect mode or if DQ5
goes high.
7. The fourth cycle of the autoselect command sequence is
a read cycle.
PD = Data to be programmed at location PA. Data is latched
on the rising edge of WE# or CE# pulse.
SA = Address of the sector to be erased or verified. Address
bits A20–A13 uniquely select any sector.
8. The data is 00h for an unprotected sector and 01h for a
protected sector.
9. Command is valid when device is ready to read array data
or when device is in autoselect mode.
10. The Unlock Bypass command is required prior to the
Unlock Bypass Program command.
11. The Unlock Bypass Reset command is required to return
to reading array data when the device is in the Unlock
Bypass mode.
12. The system may read and program functions in nonerasing sectors, or enter the autoselect mode, when in the
Erase Suspend mode. The Erase Suspend command is
valid only during a sector erase operation.
13. The Erase Resume command is valid only during the
Erase Suspend mode.
Am29LV116D21
Page 23
WRITE OPERATION STATUS
The device provides several bits to determine the status of a write operation: DQ2, DQ3, DQ5, DQ6, DQ7,
and RY/BY#. Table 10 and the following subsections
describe the functions of thes e bits . DQ7, RY/BY#, and
DQ6 each offer a method for determining whether a
program or erase operation is complete or in progress.
These three bits are discussed first.
DQ7: Data# Polling
The Data# Polling bit, DQ7, indicates to the host system whether an Embedded Algorithm is in progress or
completed, or whether the devic e is in Er as e Suspend.
Data# Polling is valid after the rising edge of the final
WE# pulse in the program or erase command sequence.
During the Em bedded Program algor ithm, 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 reading
array data.
Table 10 shows the outputs for Data# Polling on DQ7.
Figure 5 shows the Data# Polling algorithm.
START
Read DQ7–DQ0
Addr = VA
Yes
No
DQ7 = Data?
No
DQ5 = 1?
Yes
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.
This is analogous to the complement/true datum output
described for the Embedded Program algorithm: the
erase function changes all the bits in a sector to “1”;
prior to this, the device outputs the “complement,” o r
“0.” 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 s ectors selected for erasing are protected, Data# Polling
on DQ7 is active f or appro ximately 100 µs , the n the device 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.
When the system detects DQ7 has changed from the
complement to true data, it can read va lid data at DQ7–
DQ0 on the
following
read cycles. This is because DQ7
may change asynchronously with DQ0–DQ6 while
Output Enable (OE#) is as serted low. Figure 17, Data#
Polling Timings (During Embedded Algorithms), in the
“AC Characteristics” section illustrates this.
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 an address within any
sector selected for erasure. 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 5. Data# Polling Algorithm
22Am29LV116D
Page 24
RY/BY#: Ready/Busy#
The RY/BY# is a dedicated, open-drain output pin that
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
on the 44-pin SO package.)
If the output is low (Busy ), the de vice is activ ely er asing
or programming. (T his includes programming in the
Erase Suspend mode.) If th e output is high (Ready) ,
the device is ready to read array data (including during
the Erase Suspend mode), or is in the standby mode.
Table 10 shows the outputs for R Y/BY#. Fig ures 13, 15
and 16 shows RY/BY# for reset, program, and erase
operations, respectively.
. (The RY/BY# pin is not a vailable
CC
DQ6: Toggle Bit I
To ggle Bit I on DQ6 indi cates whether an Embedde d
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 eras e operation), and during the sector erase time-out.
T ab le 10 shows the outputs f or Toggle Bit I on DQ6. Figure 6 shows the toggle bit algorithm in flowchart form,
and the section “Reading Toggle Bits DQ6/DQ2” explains the algorithm. Figure 18 in the “AC Characteristics” section shows the toggle bit timing dia grams.
Figure 19 shows the differences between DQ2 and
DQ6 in graphical form. See also the subsection on
DQ2: Toggle Bit II.
DQ2: Toggle Bit II
The “Toggle Bit II” on DQ2, when used with DQ6, indicates whether a par ticular sect or is actively erasing
(that is, the Embedded Erase algo rithm is in pro gress),
or whether that sector is erase-suspended. Toggle Bit
II is valid after the rising edge of t he final WE# pulse in
the command sequence.
DQ2 toggles w hen the system reads at addresses
within those sector s 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 10 to compare outputs for DQ2 and DQ6.
During an Embedded Program or Erase algorithm operation, successive read cycles to any address cause
DQ6 to toggle (The system may use either OE# o r CE#
to control the read cy cles). When the oper at ion is c omplete, DQ6 stops toggling.
After an erase command sequence is written, if all s ectors selected for eras ing are protected , DQ6 toggles for
approximately 100 µs, then returns to readi ng 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 erasesuspended. When the device is activ ely 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 pro tected 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.
Figure 6 shows the toggle bit algorithm in flowchar t
form, and the section “Reading Toggle Bits DQ6/DQ2”
explains the algorithm. See also the DQ6: Toggle Bit I
subsection. Figure 18 shows the toggle bit timing diagram. Figure 19 shows the differences between DQ2
and DQ6 in graphical form.
Reading Toggle Bits DQ6/DQ2
Refer to Figure 6 for the following discussion. Whe never 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 t oggle 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 eras e 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
Am29LV116D23
Page 25
must write the reset command to return to readin g
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 success ive read cycle s, determining the status as described in the previous paragraph. Alterna tively, it may choose to perform 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 6).
T ab le 10 shows the outputs f or Toggle Bit I on DQ6. Figure 6 shows the toggle bit algorithm. Figure 18 in the
“AC Characteristics” section sho ws the toggle bit timing
diagrams. Figure 19 shows the differences between
DQ2 and DQ6 in graphical form. See also the subsection on DQ2: Toggle Bit II.
START
Read DQ7–DQ0
Read DQ7–DQ0
Toggle Bit
= Toggle?
Yes
(Note 1)
No
DQ5: Exceeded Timing Limits
DQ5 indicates whether the program or erase time has
exceeded a specified internal pulse count limit. Under
these conditions DQ5 produces a “1.” This is a failure
condition that indicates the prog ram or er ase cycle was
not successfully completed.
The DQ5 failure condition may appear if the system
tries to program a “1” to a location that i s previously programmed to “0.” Only an era se operation can change
a “0” back to a “1.” Under this condition, the device
halts the operation, and when the operation has ex-
ceeded the timing limits, DQ5 produces a “1.”
Under both these conditions, t he system must issue the
reset command to return the device to reading array
data.
DQ3: Sector Erase Timer
After writing a sector erase comm and sequence, the
system may read DQ3 to determine whether or not an
erase operation has begun. (The sector erase timer
does not apply to the chip erase command.) If additional sectors are selected for erasure, the entire timeout also applies after each additional sector erase command. When the time-out is com plete, DQ3 switches
from “0” to “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 sequence is written,
the system should read the status on DQ7 (Data# Polling) or DQ6 (Toggle Bit I) to ensure the device has accepted the command sequence, and then read DQ3. If
DQ3 is “1”, the internally controlled erase cycle has begun; all further commands (other than Erase Su spend)
No
Notes:
1. Read toggle bit twice to determine whether or not it is
toggling. See text.
2. Recheck toggle bit because it may stop toggling as DQ5
changes to “1”. See text.
DQ5 = 1?
Yes
Read DQ7–DQ0
Twice
Toggle Bit
= Toggle?
Yes
Program/Erase
Operation Not
Complete, Write
Reset Command
(Notes
1, 2)
No
Program/Erase
Operation Complete
Figure 6. Toggle Bit Algorithm
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 che ck the s tatus
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 10 shows the outputs for DQ3.
24Am29LV116D
Page 26
Table 10. Write Operation Status
DQ7
Standard
Mode
Erase
Suspend
Mode
Operation
Embedded Program AlgorithmDQ7#Toggle0N/ANo toggle0
Embedded Erase Algorithm0Toggle01Toggle0
Reading within Erase
1. DQ5 switches to ‘1’ when an Embedded Program or Embedded Erase operation has exceeded the maximum timing limits.
See “DQ5: Exceeded Timing Limits” for more information.
2. DQ7 and DQ2 require a valid address when reading status information. Refer to the appropriate subsection for further details.
with Power Applied. . . . . . . . . . . . . . –65°C to +125°C
Voltage with Respect to Ground
(Note 1) . . . . . . . . . . . . . . . . .–0.5 V to +4.0 V
V
CC
A9, OE#, 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 o vershoot V
–2.0 V for periods of up to 20 ns. See Figure 7. Maximum
V
DC voltage on input or I/O pins is
voltage transitions, input or I/O pins may overshoot to V
+2.0 V for periods up to 20 ns. See Figure 8.
2. Minimum DC input voltage on pins A9, OE#, and RESET#
is –0.5 V. During voltage transitions, A9, OE#, and
RESET# may overshoot V
20 ns. See Figure 7. Maximum DC input voltage on pin A9
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
SS
+0.5 V. During
CC
CC
+0.5 V
to
SS
CC
20 ns
+0.8 V
–0.5 V
–2.0 V
20 ns
20 ns
Figure 7. Maximum Negative
Overshoot Waveform
20 ns
V
CC
+2.0 V
V
CC
+0.5 V
2.0 V
20 ns
20 ns
Figure 8. Maximum Positive
Overshoot Waveform
OPERATING RANGES
Commercial (C) Devices
Ambient Temperature (T
Industrial (I) Devices
Ambient Temperature (T
Supply Voltages
V
CC
for all devices . . . . . . . . . . . . . . . .+2.7 V to 3.6 V
V
CC
Operating ranges define those limits between which the
functionality of the device is guaranteed.
26Am29LV116D
) . . . . . . . . . . . 0°C to +70°C
A
) . . . . . . . . . –40°C to +85°C
A
Page 28
DC CHARACTERISTICS
CMOS Compatible
ParameterDescriptionTest ConditionsMinTypMaxUnit
V
= VSS to VCC,
I
I
I
CC1
I
LI
LIT
LO
Input Load Current
V
IN
= VCC
CC
A9 Input Load CurrentVCC = V
V
= VSS to VCC,
Output Leakage Current
VCC Active Read Current
(Notes 1, 2)
OUT
= V
V
CC
CE# = V
max
; A9 = 12.5 V35µA
CC max
CC max
5 MHz916
OE#
IL,
= VIH
1 MHz24
1.0µA
±
1.0µA
±
mA
V
V
V
I
CC2
I
CC3
I
CC4
I
CC5
V
V
V
V
IL
IH
ID
OL
OH1
OH2
LKO
VCC Active Write Current
(Notes 2, 3, 4)
CE# = V
VCC Standby Current (Note 2)CE#, RESET# = VCC±
VCC Reset Current (Note 2)RESET# = V
Automatic Sleep Mode
(Notes 2, 5)
VIH = V
V
IL
Input Low Voltage–0.50.8V
Input High Voltage0.7 x V
Voltage for Autoselect and
Temporary Sector Unprotect
V
CC
Output Low VoltageIOL = 4.0 mA, VCC = V
I
Output High Voltage
OH
IOH = –100 µA, VCC = V
Low VCC Lock-Out Voltage
(Note 4)
OE#
IL,
= VIH
0.3 V0.25µA
0.3 V0.25µA
±
SS
± 0.3 V;
CC
SS
±
0.3 V
= V
= 3.3 V11.512.5V
0.45V
CC min
= –2.0 mA, VCC = V
0.85 V
CC min
VCC–0.4
CC min
2.32.5V
Notes:
1. The I
2. Maximum I
3. I
current listed is typically less than 2 mA/MHz, with OE# at VIH. Typical specifications are for VCC = 3.0 V.
CC
specifications are tested with V
CC
active while Embedded Erase or Embedded Program is in progress.
CC
= VCCmax.
CC
4. Not 100% tested.
5. Automatic sleep mode enables the low power mode when addresses remain stable for t
CC
CC
ACC
1530mA
0.25µA
VCC + 0.3V
V
+ 30 ns.
Am29LV116D27
Page 29
DC CHARACTERISTICS (Continued)
Zero Power Flash
25
20
15
10
Supply Current in mA
5
0
05001000150020002500300035004000
Time in ns
Note: Addresses are switching at 1 MHz
Figure 9. I
Current vs. Time (Showing Active and Automatic Sleep Currents)
CC1
10
8
6
4
Supply Current in mA
2
0
12345
3.6 V
2.7 V
Frequency in MHz
Note: T = 25 °C
Figure 10. Typical I
vs. Frequency
CC1
28Am29LV116D
Page 30
TEST CONDITIONS
3.3 V
Table 11. Test Specifications
Test Condition-70-90, -120 Unit
Output Load1 TTL gate
Output Load Capacitance, C
(including jig capacitance)
Input Rise and Fall Times5ns
Input Pulse Levels0.0–3.0V
Input timing measurement
reference levels
Output timing measurement
reference levels
Device
Under
Test
C
L
Note: Diodes are IN3064 or equivalent
6.2 k
2.7 k
Ω
Ω
Figure 11. Test Setup
Key to Switching Waveforms
WAVE FO RMINPUTSOUTPUTS
Steady
Changing from H to L
Changing from L to H
L
30100pF
1.5 V
1.5V
3.0 V
0.0 V
Don’t Care, Any Change PermittedChanging, State Unknown
Does Not ApplyCenter Line is High Impedance State (High Z)
1.5 V1.5 V
Figure 12. Input Waveforms and Measurement Levels
OutputMeasurement LevelInput
Am29LV116D29
Page 31
AC CHARACTERISTICS
Read Operations
Parameter
JEDECStdTest Setup-70-90-12 0U nit
t
AVAV
t
AVQV
t
ELQV
t
GLQV
t
EHQZ
t
GHQZ
t
Description
t
Read Cycle Time (Note 1)Min7090120ns
RC
Address to Output Delay
ACC
t
Chip Enable to Output DelayOE# = V
CE
t
Output Enable to Output DelayMax303550ns
OE
t
Chip Enable to Output High Z (Note 1)Max253030ns
DF
t
Output Enable to Output High Z (Note 1)Max253030ns
DF
CE# = V
OE# = V
IL
Max7090120ns
IL
Max7090120ns
IL
Speed Option
ReadMin0ns
Output Enable
OEH
Hold Time (Note 1)
Toggle and
Data# Polling
Output Hold Time From Addresses, CE# or
t
OH
OE#, Whichever Occurs First (Note 1)
Min10ns
Min0ns
t
AXQX
t
Notes:
1. Not 100% tested.
2. See Figure 11 and Table 11 for test specifications.
RESET# Pin Low (During Embedded Algorithms)
to Read or Write (See Note)
RESET# Pin Low (NOT During Embedded
Algorithms) to Read or Write (See Note)
RESET# Pulse WidthMin500ns
t
RP
RESET# High Time Before Read (See Note)Min50ns
t
RH
RESET# Low to Standby ModeMin20µs
t
RPD
RY/BY# Recovery TimeMin0ns
t
RB
Note: Not 100% test ed.
RY/BY#
CE#, OE#
RESET#
t
RP
t
Ready
Max20µs
Max500ns
t
RH
RY/BY#
CE#, OE#
RESET#
Reset Timings NOT during Embedded Algorithms
Reset Timings during Embedded Algorithms
t
Ready
t
RP
Figure 14. RESET# Timings
t
RB
Am29LV116D31
Page 33
AC CHARACTERISTICS
Erase/Program Operations
ParameterSpeed Options
JEDECStdDescription-70-90-120Unit
t
AVAV
t
AVWL
t
WLAX
t
DVWH
t
WHDX
t
GHWL
t
ELWL
t
WHEH
t
WLWH
t
WHWL
t
WHWH1
t
WHWH2
t
WC
t
AS
t
AH
t
DS
t
DH
t
OES
t
GHWL
t
CS
t
CH
t
WP
t
WPH
t
WHWH1
t
WHWH2
t
VCS
t
RB
t
BUSY
Write Cycle Time (Note 1)Min7090120ns
Address Setup TimeMin0ns
Address Hold TimeMin454550ns
Data Setup TimeMin354550ns
Data Hold TimeMin0ns
Output Enable Setup Time (Note 1)Min0ns
Read Recovery Time Before Write
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 18. Toggle Bit Timings (During Embedded Algorithms)
34Am29LV116D
Page 36
AC CHARACTERISTICS
Enter
Embedded
Erasing
WE#
DQ6
DQ2
Note: The system can use OE# or CE# to toggle DQ2/DQ6. DQ2 toggles only when read at an address within an
erase-suspended sector.
Erase
Erase
Suspend
Erase Suspend
Enter Erase
Suspend Program
Read
Figure 19. DQ2 vs. DQ6
Erase
Suspend
Program
Erase Suspend
Read
Erase
Resume
Erase
Temporary Sector Unprotect
Parameter
All Speed OptionsJEDECStdDescriptionUnit
Erase
Complete
t
VIDR
t
RSP
Note: Not 100% test ed.
12 V
RESET#
0 or 3 V
CE#
WE#
RY/BY#
VID Rise and Fall Time (See Note)Min500ns
RESET# Setup Time for Temporary Sector
AC CHARACTERISTICS
Alternate CE# Controlled Erase/Program Operations
ParameterSpeed Options
JEDECStdDescription-70-90-120Unit
t
AVAV
t
AVEL
t
ELAX
t
DVEH
t
EHDX
t
GHEL
t
WLEL
t
EHWH
t
ELEH
t
EHEL
t
WHWH1
t
WHWH2
t
WC
t
AS
t
AH
t
DS
t
DH
t
OES
t
GHEL
t
WS
t
WH
t
CP
t
CPH
t
WHWH1
t
WHWH2
Write Cycle Time (Note 1)Min7090120ns
Address Setup TimeMin0ns
Address Hold TimeMin454550ns
Data Setup TimeMin354550ns
Data Hold TimeMin0ns
Output Enable Setup TimeMin0ns
Read Recovery Time Before Write
(OE# High to WE# Low)
WE# Setup TimeMin0ns
WE# Hold TimeMin0ns
CE# Pulse WidthMin353550ns
CE# Pulse Width HighMin30ns
Programming Operation (Note 2)Typ9µs
Sector Erase Operation (Note 2)Typ0.7sec
Notes:
1. Not 100% tested.
2. See the “Erase and Programming Performance” section for more information.
Min0ns
Am29LV116D37
Page 39
AC CHARACTERISTICS
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
t
BUSY
Data# Polling
WHWH1 or 2
PA
DQ7#D
OUT
RY/BY#
Note: P A = program address, PD = program data, DQ7# = complement of the data written to the device, D
the device. Figure indicates the last two bus cycles of the command sequence.
Excludes 00h programming
prior to erasure (Note 4)
Excludes system level
overhead (Note 5)
Notes:
°
1. Typical program and erase times assume the following conditions: 25
C, 3.0 V VCC, 1,000,000 cycles. Additionally,
programming typicals assume checkerboard pattern.
2. Under worst case conditions of 90°C, V
= 2.7 V, 1,000,000 cycles.
CC
3. The typical chip programming time is considerably less than the maximum chip programming time listed, since most bytes
program faster than the maximum program times listed.
4. In the pre-programming step of the Embedded Erase algorithm, all bytes are programmed to 00h before erasure.
5. System-level overhead is the time required to execute the four- or two-bus-cycle sequence for the program command. See
Table 9 for further information on command definitions.
6. The device has a guaranteed minimum erase and program cycle endurance of 1,000,000 cycles per sector.
LATCHUP CHARACTERISTICS
DescriptionMinMax
Input voltage with respect to V
(including A9, OE#, and RESE T#)
Input voltage with respect to V
Current–100 mA+100 mA
V
CC
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
TSOP PIN CAPACITANCE
Parameter
SymbolParameter DescriptionTest SetupTypMaxUnit
Input CapacitanceVIN = 067.5pF
Output CapacitanceV
Control Pin CapacitanceVIN = 07.59pF
= 08.512pF
OUT
C
C
C
OUT
IN
IN2
Notes:
1. Sampled, not 100% tested.
2. Test conditions T
= 25°C, f = 1.0 MHz.
A
DATA RETENTION
ParameterTest ConditionsMinUnit
Minimum Pattern Data Retention Time
150°C10Years
125°C20Years
Am29LV116D39
Page 41
PHYSICAL DIMENSIONS*
TS 040—40-Pin Standard TSOP
* For reference only. BSC is an ANSI standard for Basic Space Centering.
40Am29LV116D
Dwg rev AA; 10/99
Page 42
PHYSICAL DIMENSIONS
TSR040—40-Pin Reverse TSOP
* For reference only. BSC is an ANSI standard for Basic Space Centering.
Am29LV116D41
Dwg rev AA; 10/99
Page 43
REVISION SUMMARY
Revision A (October 1997)
First release.
Revision B (October 1997)
Global
Deleted SO package from data sheet.
Revision C (December 1997)
Alternate CE# Controlled Erase/Program
Operations
Changed t
options.
from 45 to 35 ns on 80R and 90 speed
CP
Revision C+1 (January 1998)
Global
Changed data sheet status to Preliminary.
Reset Command
Deleted the last paragraph in this section.
Revision C+2 (March 1998)
Figure 2, In-System Sector Protect/Unprotect
Algorithms (0.35 µm devices)
In the sector protect algorithm, added a “Reset
PLSCNT=1” box in the path from “Protect ano ther sector?” back to setting up the next sec tor address.
AC Characteristics
Erase/Program Operations; Altern ate CE# Controlled
Erase/Program Operations:
ence for t
100% tested. Corrected the note reference for t
This parameter is not 100% tested.
Changed timing specifications in diagram to match
those in the figure of In-System Sector Protect/Unprotect Algorithms.
max test condition for ICC specifications to
CC
Revision D (January 1999)
Distinctive Characteristics
Added “20-year data retention at 125°C” bullet.
Revision E (February 2, 2000)
Global
The process technology has changed to 0.23 µm, and
is indicated in the part number by the “D” suffix. The 70
ns speed option is now offered in the full voltage range
instead of the regulated voltage range. The 70 ns
devices are also now av ailab le in the industrial temperature range. The extended temperature range is no
.
longer available. The 80 ns speed option has been
deleted. All other parameters and functions remain
unchanged.
AC Characteristics—Figure 15. Program
Operations Timing and Figure 16. Chip/Sector
Erase Operations
Deleted t
high.
Physical Dimensions
Replaced figures with more detailed illustrations.
and changed OE# waveform to start at
GHWL
Revision E+1 (November 7, 2000)
Global
Added table of contents. Delete d burn-in option in
ordering information section.