Datasheet Am29LV116D Datasheet (SPANSION)

Page 1
查询AM29LV116DB-120供应商
Am29LV116D
Data Sheet
July 2003
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 rig­inally 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
Flexible sector arc hitecture
— One 16 Kbyte, two 8 Kbyte, one 32 Kbyte, and
thirty-one 64 Kbyte sectors — Supports full chip erase — Sector Protection features:
A hardware method of locking a sector to prevent
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 gener­ated 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. Com­mands are written to the command register using stan­dard microproc essor write timing s. Register contents serve as input to an internal sta te-machine that co n­trols 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 Embedded Program algorithm—an internal algorithm that auto­matically times the program pulse widths and verifies proper cell margin. The Unlock Bypass mode facili­tates faster programming times by requir ing only two write cycles to program data instead of four.
Device erasure occurs by executing the erase com­mand 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 mem­ory. This can be achieved in-system or via program­ming 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 ad­dresses 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 standby mode. 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 effective­ness. The device electrically erases all bi ts with in a s e ct or simultaneously via Fowler-Nordheim tun­neling. The data is programmed using hot electron injec­tion.
2 Am29LV116D
Page 4
TABLE OF CONTENTS
Product Selector Guide . . . . . . . . . . . . . . . . . . . . .4
Connection Diagrams . . . . . . . . . . . . . . . . . . . . . . .5
Pin Configuration . . . . . . . . . . . . . . . . . . . . . . . . . .6
Logic Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Ordering Information . . . . . . . . . . . . . . . . . . . . . . .7
Standard Products ....................................................................7
Device Bus Operations . . . . . . . . . . . . . . . . . . . . . .8
Table 1. Am29LV116D Device Bus Operations ................................8
Requirements for Reading Array Data .......... ...........................8
Writing Commands/Command Sequences ..................... .........8
Program and Erase Operation Status ......................................9
Standby Mode ............................ ..............................................9
Automatic Sleep Mode ........................................ ................. .. ..9
RESET#: Hardware Reset Pin .................................................9
Output Disable Mode ................................................................9
Table 2. Am29LV116DT Top Boot Sector Address Table ..............10
Table 3. Am29LV116DB Bottom Boot Sector Address Table .........11
Autoselect Mode ........................... .. ................. ................. ......12
Table 4. Am29LV116D Autoselect Codes (High Voltage Method) ..12
Sector Protection/Unprotection ............................................... 12
Temporary Sector Unprotect ..................................................12
Figure 1. In-System Sector Protect/Unprotect Algorithms.............. 13
Figure 2. Temporary Sector Unprotect Operation........................... 14
Hardware Data Protection ......................................................14
Low V
Write Pulse “Glitch” Protection ...............................................14
Logical Inhibit ..........................................................................14
Power-Up Write Inhibit ............................................................ 14
Common Flash Memory Interface (CFI). . . . . . . 14
Command Definitions . . . . . . . . . . . . . . . . . . . . . .17
Reading Array Data ................................................................17
Reset Command .....................................................................17
Autoselect Command Sequence ............................................17
Byte Program Command Sequence ...... .................................17
Unlock Bypass Command Sequence ............................... ......18
Chip Erase Command Sequence ...........................................18
Sector Erase Command Sequence ........................................19
Erase Suspend/Erase Resume Commands ......... ..................19
Command Definitions .............................................................21
Write Operation Status . . . . . . . . . . . . . . . . . . . . .22
DQ7: Dat a# Po ll i n g ....... ... .. ................... ................... ... ............ 22
RY/BY#: Ready/Busy# ...........................................................23
DQ6: Toggle Bit I ....................................................................23
DQ2: Toggle Bit II ...................................................................23
Write Inhibit .............................................................. 14
CC
Table 5. CFI Query Identification String ..........................................15
Table 6. System Interface String .....................................................15
Table 7. Device Geometry Definition ..............................................16
Table 8. Primary Vendor-Specific Extended Query ........................16
Figure 3. Program Operation.......................................................... 18
Figure 4. Erase Operation............................................................... 20
Table 9. Am29LV116D Command Definitions ...............................21
Figure 5. Data# Polling Algorithm ................................................... 22
Reading Toggle Bits DQ6/DQ2 ...............................................23
DQ5: Exceeded Timing Limits ................................................24
DQ3: Sector Erase Timer .......................................................24
Figure 6. Toggle Bit Algorithm........................................................ 24
Table 10. Write Operation Status ................................................... 25
Absolute Maximum Ratings . . . . . . . . . . . . . . . . 26
Figure 7. Maximum Negative Overshoot Waveform...................... 26
Figure 8. Maximum Positive Overshoot Waveform........................ 26
Operating Ranges. . . . . . . . . . . . . . . . . . . . . . . . . 26
DC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . 27
CMOS Compa tible .. .. ................... ................... ................... .....27
Zero Power Flash ...................................................................28
Figure 9. I
Automatic Sleep Currents)............................ ............ ........... .......... 28
Figure 10. Typical I
Current vs. Time (Showing Active and
CC1
vs. Frequency........................................... 28
CC1
Test Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Figure 11. Test Setup..................................................................... 29
Table 11. Test Specifications ......................................................... 29
Key to Switching Waveforms ..................................................29
Figure 12. Input Waveforms and Measurement Levels ................. 29
AC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . 30
Read Operations ....................................................................30
Figure 13. Read Operations Timings ............................................. 30
Hardware Reset (RESET#) ....................................... .. ...........31
Figure 14. RESET# Timings.......................................................... 31
Erase/Program Operations .....................................................32
Figure 15. Program Operation Timings.......................................... 33
Figure 16. Chip/Sector Erase Operation Timings .......................... 33
Figure 17. Data# Polling Timings (During Embedded Algorithms). 34
Figure 18. Toggle Bit Timings (During Embedded Algorithms)...... 34
Figure 19. DQ2 vs. DQ6................................................................. 35
Temporary Sector Unprotect ..................................................35
Figure 20. Temporary Sector Unprotect Timing Diagram .............. 35
Figure 21. Sector Protect/Unprotect Timing Diagram.................... 36
Figure 22. Alternate CE# Controlled Write Operation Timings ...... 38
Erase and Programming Performance . . . . . . . 39
Latchup Characteristics. . . . . . . . . . . . . . . . . . . . 39
TSOP Pin Capacitance. . . . . . . . . . . . . . . . . . . . . 39
Data Retention. . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Physical Dimensions . . . . . . . . . . . . . . . . . . . . . . 40
TS 040—40-Pin Standard TSOP ............................................40
TSR040—40-Pin Reverse TSOP ...........................................41
Revision Summary . . . . . . . . . . . . . . . . . . . . . . . . 42
Revision A (October 1997) .....................................................42
Revision B (October 1997) .....................................................42
Revision C (December 1997) ......... ............. ...........................42
Revision C+1 (January 1998) ............ ............................ .........42
Revision C+2 (March 1998) ................................................ .. ..42
Revision C+3 (August 1998) ...................................................42
Revision D (January 1999) .................. ........................... ........42
Revision E (February 2, 2000) ................................................ 42
Revision E+1 (November 7, 2000) .........................................42
Am29LV116D 3
Page 5
PRODUCT SELECTOR GUIDE
Family Part Number Am29LV116D
Speed Options V
Max access time, ns (t
ACC
Max CE# access time, ns (t Max OE# access time, ns (t
= 2.7–3.6 V -70 -90 -120
CC
)7090120
)7090120
CE
) 303550
OE
Note: See “AC Characteristics” for full specifications.
BLOCK DIAGRAM
RY/BY#
V
CC
V
SS
RESET#
WE#
CE#
OE#
State
Control
Command
Register
PGM Voltage
Generator
Sector Switches
Erase Voltage
Generator
Chip Enable
Output Enable
Logic
STB
DQ0
DQ7
Input/Output
Buffers
Data
Latch
A0–A20
VCC Detector
Timer
STB
Address Latch
Y-Decoder
X-Decoder
Y-Gating
Cell Matrix
4 Am29LV116D
Page 6
CONNECTION DIAGRAMS
A16 A15 A14 A13 A12 A11
A9 A8
WE#
RESET#
NC
RY/BY#
A18
A7 A6 A5 A4 A3 A2 A1
A17 V
SS
A20 A19
A10 DQ7 DQ6 DQ5 DQ4
V
CC
V
CC
NC DQ3 DQ2 DQ1 DQ0
OE#
V
SS
CE#
A0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
40-Pin Standard TSOP
40-Pin Reverse TSOP
40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21
40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21
A17 V
SS
A20 A19 A10 DQ7 DQ6 DQ5 DQ4 V
CC
V
CC
NC DQ3 DQ2 DQ1 DQ0 OE#
V
SS
CE# A0
A16 A15 A14 A13 A12 A11 A9 A8 WE# RESET# NC RY/BY# A18 A7 A6 A5 A4 A3 A2 A1
Am29LV116D 5
Page 7
PIN CONFIGURATION
A0–A20 = 21 addresses DQ0–DQ7 = 8 data inputs/outputs CE# = Chip enable OE# = Output enable WE# = Write enable RESET# = Hardware reset pin, active low RY/BY# = Ready/Busy output
= 3.0 volt-only single power supply
V
CC
V
SS
NC = Pin not connected internally
(see Product Selector Guide for speed
options and voltage supply toleranc es)
= Device ground
LOGIC SYMBOL
21
A0–A20
CE# OE#
WE# RESET#
8
DQ0–DQ7
RY/BY#
6 Am29LV116D
Page 8
ORDERING INFORMATION Standard Pr od ucts
AMD standard products are available in several packages and operating ranges. The order number (Valid Combi­nation) is formed by a combination of the elements below.
Am29LV116D T -70 E C
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 sup­ported 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.
Am29LV116D 7
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 it­self does not occupy any addressable memory loca­tion. The register is composed of l atches that store the commands, along with the address and data informa­tion needed to execute the command. The contents of
Table 1. Am29LV116D Device Bus Operations
Operation CE# OE# WE# RESET# Addresses DQ0–DQ7
Read L L H H A Write L H L H A
±
V
Standby Output Disable L H H H X High-Z
Reset X X X L X High-Z Sector Protect (See Note) L H L V
Sector Unprotect (See Note) L H L V Temporary Sector Unprotect X X X V
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 ma­chine. 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
X High-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 con­trol 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 con­tent 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 specifica­tions and to Figure 13 for the timing diagram. I
the DC Characteristics table represents the active cur­rent 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 in­cludes 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 re­quired 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 sec­tors, or the entire device. Tables 2 and 3 indic ate the address space that each sector occupies. A “sector ad­dress” 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 se­quence, the device enters the autoselect mode. The system can then read autoselect codes from the inter­nal register (which is separate from the memory array) on DQ7–DQ0. Standard read cycle timings apply in this
, and OE# to VIH.
IL
8 Am29LV116D
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 Characteris­tics” 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, inde­pendent 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 RE­SET# pin is driven low. Refer to the next section, “RE­SET#: Hardware Reset Pin”.
If the device is deselected during erasure or program­ming, 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 reset­ting the device to reading array data. When the RE­SET# pin is driven low for at least a period of t
RP
, the device immediately terminates any operation in progress, tristates all output pins, and ignores all read/write commands for the duration of the RESET# pulse. The device also resets the inter nal state ma­chine to reading array data. The operation that was in­terrupted 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 firm­ware from the Flash memory.
If RESET# is asserted during a program or erase oper­ation, the RY/BY# pin remains a “0” (busy) until the in­ternal 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# pa­rameters 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 imped­ance state.
Am29LV116D 9
Page 11
Table 2. Am29LV116DT Top Boot Sector Address Table
Sector Size
Sector A20 A19 A18 A17 A16 A1 5 A14 A13
SA000000XXX 64 000000–00FFFF SA100001XXX 64 01000001FFFF SA200010XXX 64 02000002FFFF SA300011XXX 64 03000003FFFF SA400100XXX 64 04000004FFFF SA500101XXX 64 05000005FFFF SA600110XXX 64 06000006FFFF SA700111XXX 64 07000007FFFF SA801000XXX 64 08000008FFFF
SA901001XXX 64 09000009FFFF SA1001010XXX 64 0A00000AFFFF SA1101011XXX 64 0B00000BFFFF SA1201100XXX 64 0C00000CFFFF SA1301101XXX 64 0D00000DFFFF SA1401110XXX 64 0E00000EFFFF SA1501111XXX 64 0F00000FFFFF SA1610000XXX 64 10000010FFFF SA1710001XXX 64 11000011FFFF SA1810010XXX 64 12000012FFFF SA1910011XXX 64 13000013FFFF SA2010100XXX 64 14000014FFFF SA2110101XXX 64 15000015FFFF SA2210110XXX 64 16000016FFFF SA2310111XXX 64 17000017FFFF SA2411000XXX 64 18000018FFFF SA2511001XXX 64 19000019FFFF SA2611010XXX 64 1A00001AFFFF SA2711011XXX 64 1B00001BFFFF SA2811100XXX 64 1C00001CFFFF SA2911101XXX 64 1D00001DFFFF SA3011110XXX 64 1E00001EFFFF SA31111110XX 32 1F00001F7FFF SA3211111100 8 1F80001F9FFF SA3311111101 8 1FA0001FBFFF SA341111111X 16 1FC0001FFFFF
(Kbytes)
Address Range
(in hexadecimal)
10 Am29LV116D
Page 12
Table 3. Am29LV116DB Bottom Boot Sector Address Tab le
Sector Size
Sector A20 A19 A18 A17 A16 A15 A14 A13
SA0 0000000X 16 000000–003FFF SA1 00000010 8 004000005FFF SA2 00000011 8 006000007FFF SA3 0 0 0 0 0 1 X X 32 008000–00FFFF SA4 0 0 0 0 1 X X X 64 010000–01FFFF SA5 0 0 0 1 0 X X X 64 020000–02FFFF SA6 0 0 0 1 1 X X X 64 030000–03FFFF SA7 0 0 1 0 0 X X X 64 040000–04FFFF SA8 0 0 1 0 1 X X X 64 050000–05FFFF
SA9 0 0 1 1 0 X X X 64 060000–06FFFF SA10 0 0 1 1 1 X X X 64 070000–07FFFF SA11 0 1 0 0 0 X X X 64 080000–08FFFF SA12 0 1 0 0 1 X X X 64 090000–09FFFF SA13 0 1 0 1 0 X X X 64 0A0000–0AFFFF SA14 0 1 0 1 1 X X X 64 0B0000–0BFFFF SA15 0 1 1 0 0 X X X 64 0C0000–0CFFFF SA16 0 1 1 0 1 X X X 64 0D0000–0DFFFF SA17 0 1 1 1 0 X X X 64 0E0000–0EFFFF SA18 0 1 1 1 1 X X X 64 0F0000–0FFFFF SA19 1 0 0 0 0 X X X 64 100000–10FFFF SA20 1 0 0 0 1 X X X 64 110000–11FFFF SA21 1 0 0 1 0 X X X 64 120000–12FFFF SA22 1 0 0 1 1 X X X 64 130000–13FFFF SA23 1 0 1 0 0 X X X 64 140000–14FFFF SA24 1 0 1 0 1 X X X 64 150000–15FFFF SA25 1 0 1 1 0 X X X 64 160000–16FFFF SA26 1 0 1 1 1 X X X 64 170000–17FFFF SA27 1 1 0 0 0 X X X 64 180000–18FFFF SA28 1 1 0 0 1 X X X 64 190000–19FFFF SA29 1 1 0 1 0 X X X 64 1A0000–1AFFFF SA30 1 1 0 1 1 X X X 64 1B0000–1BFFFF SA31 1 1 1 0 0 X X X 64 1C0000–1CFFFF SA32 1 1 1 0 1 X X X 64 1D0000–1DFFFF SA33 1 1 1 1 0 X X X 64 1E0000–1EFFFF SA34 1 1 1 1 1 X X X 64 1F0000–1FFFFF
(Kbytes)
Address Range
(in hexadecimal)
Am29LV116D 11
Page 13
Autoselect Mode
The autoselect mode provides manufacturer and de­vice 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 corre­sponding 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
Description CE# OE# WE#
Manufacturer ID: AMD L L H X X V Device ID: Am29LV116D
(Top Boot Block) Device ID: Am29LV116D
(Bottom Boot Block)
LLHXXV
LLHXXV
A13
A10 A9
. See “Command Definitions” for
ID
A8
to
A7 A6
XLXLL 01h
ID
XLXLH C7h
ID
XLXLH 4Ch
ID
A5
to
A2 A1 A0
DQ7
to
DQ0
Sector Protection Verification L L H SA X V
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 hard­ware sector unprotection feature re-enables both pro­gram and erase operations in previously protected sectors. Sector protection/unprotecti on can be imple­mented 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 algo­rithms and Figure 21 shows the timing diagram. This method uses standard m icroprocessor bus cycle tim­ing. 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 previ­ously protected sectors to change data in-system. The Sector Unprotect mode is activated by setting the RE­SET# 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.
01h
(protected)
00h
(unprotected)
. During this mode, formerly protected
ID
is removed from the RE-
ID
12 Am29LV116D
Page 14
Temporary Sector
Unprotect Mode
No
START
PLSCNT = 1
RESET# = V
Wait 1 µs
First Write
Cycle = 60h?
START
Protect all sectors:
The indicated portion
of the sector protect
ID
algorithm must be
performed for all
unprotected sectors
prior to issuing the
first sector
unprotect address
PLSCNT = 1
RESET# = V
Wait 1 µs
First Write
Cycle = 60h?
ID
No
Temporary Sector
Unprotect Mode
Increment
PLSCNT
No
PLSCNT
= 25?
Yes
Device failed
Sector Protect
Algorithm
Yes
Set up sector
address
Sector Protect:
Write 60h to sector
address with
A6 = 0, A1 = 1,
A0 = 0
Wait 150 µs
Verify Sector
Protect: Write 40h
to sector address
with A6 = 0,
A1 = 1, A0 = 0
Read from
sector address
with A6 = 0,
A1 = 1, A0 = 0
No
Data = 01h?
Yes
Protect another
sector?
No
Remove V
from RESET#
Write reset
command
Sector Protect
complete
Yes
No
All sectors protected?
Yes
Set up first sector
address
Sector Unprotect:
Write 60h to sector
address with
A6 = 1, A1 = 1,
A0 = 0
Reset
PLSCNT = 1
Increment
PLSCNT
No
Yes
ID
PLSCNT = 1000?
Yes
Device failed
Sector Unprotect
Wait 15 ms
Verify Sector
Unprotect: Write
40h to sector
address with
A6 = 1, A1 = 1,
A0 = 0
Read from
sector address
with A6 = 1,
A1 = 1, A0 = 0
No
Data = 00h?
Last sector
verified?
Remove V
from RESET#
Yes
Yes
Set up
next sector
address
No
ID
Algorithm
Write reset
command
Sector Unprotect
complete
Figure 1. In-System Sector Protect/Unprotect Algorithms
Am29LV116D 13
Page 15
START
RESET# = V
(Note 1)
Perform Erase or
Program Operations
RESET# = V
Temporary Sector
Unprotect Completed
(Note 2)
ID
IH
against inadverten t writes (refer to Table 9 for com­mand 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 uninten­tional 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 out­lines 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-indepen­dent, JEDEC ID-independent, and forward- and back­ward-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 Specifi­cation and CFI Publication 100, a vailable via the W orld Wide Web at http://www.amd.com/products/nvd/over­view/cfi.html. Alternatively, contact an AMD represen­tative for copies of these documents.
14 Am29LV116D
Page 16
Table 5. CFI Query Identification String
Addresses Data Description
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
Addresses Data Description
Min. (write/erase)
V
1Bh 27h
1Ch 36h
1Dh 00h V 1Eh 00h V
1Fh 04h Typical timeout per single byte/word write 2 20h 00h Typical timeout for Min. size buffer write 2 21h 0Ah Typical timeout per individual block erase 2 22h 00h Typical timeout for full chip erase 2 23h 05h Max. timeout for byte/word write 2 24h 00h Max. timeout for buffer write 2 25h 04h Max. timeout per individual block erase 2 26h 00h Max. 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
Am29LV116D 15
Page 17
Table 7. Device Geometry Definition
Addresses Data Description
N
27h 15h Device Size = 2
byte
28h 29h
2Ah 2Bh
2Ch 04h Number 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
Addresses Data Description
40h
41h
42h
43h 31h Major version number, ASCII
44h 30h Minor version number, ASCII
45h 00h
46h 02h
47h 01h
48h 01h Sector Temporary Unprotect: 00 = Not Supported, 01 = Supported
49h 04h
4Ah 00h Simultaneous Operation: 00 = Not Supported, 01 = Supported 4Bh 00h Burst Mode Type: 00 = Not Supported, 01 = Supported
4Ch 00h
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
Sector Protect/Unprotect scheme 01 = 29F040 mode, 02 = 29F016 mode, 03 = 29F400 mode, 04 = 29LV800A mode
Page Mode Type: 00 = Not Supported, 01 = 4 Word Page, 02 = 8 Word Page
16 Am29LV116D
Page 18
COMMAND DEFINITIONS
Writing specific addres s and data commands or se­quences into the command register initiates device op­erations. Table 9 defines the valid registe r command sequences. Writing incorrect address 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 Em­bedded Erase algorithm.
After the device accepts an Er ase Suspend command, the device enters the Erase Suspend mode. The sys­tem can read array data using the standard read tim­ings, except that if it reads at an address within erase­suspended 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 Sus­pend/Erase Resume Commands” for more information on this mode.
The reset command may be written between the se­quence 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 read­ing 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 writ­ing two unlock cycles, followed by the autoselect com­mand. 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 manufac­turer 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 Com­mand” 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 parame­ters, 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 de­vice to reading array data. Address bits are don’t care for this command.
The reset command may be written between the se­quence cycles in an erase command sequence before erasing begins. This resets the device to reading array data. Once erasure begins, however, the device ig­nores reset commands until the operation is complete.
The reset command may be written between the se­quence cycles in a program command sequence be­fore 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 ad­dresses are no longer latched. The system can deter­mine the status of the program operation b y using DQ7, DQ6, or RY/BY#. See “Write Operation Status” for in­formation on these status bits.
Any commands written to the device during the Em­bedded Program Algorithm are ignored. Note that a hardware reset immediately terminates the program­ming operation. The Byte Program command se-
required to provide further controls or tim-
Am29LV116D 17
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 programmed from 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 suc­cessful. 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 pro­gram bytes to t he de vice f aster than using the standard program command sequence. The unlock b ypass com­mand 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 en­ters the unlock bypass mode. A two-cycle unlo ck by­pass program command sequence is all that is required to program in this mode. The first cycle in this se­quence contains the unlock bypass program com­mand, 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 program­ming time. Table 9 shows t he requirements f or the com­mand 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 By­pass Program and Unlock Bypass Reset commands are valid. To exit the unlock bypass mode, the system must issue the two-cycle unlock bypass reset com­mand 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 oper­ation. 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 algo­rithm 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 con­trols 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 Embed­ded Erase algorithm are ignored. Note that a ha rd ware reset during the chip erase operation immediately ter­minates the operation. The Chip Erase command se­quence should be reinitiated once the device has returned to reading array data, to ensure data int eg rity.
require the system to
18 Am29LV116D
Page 20
The system can determine the status of the erase op­eration by using DQ7, DQ6, DQ2, or RY/BY#. See
“Write Operation Status” for information on these sta­tus bits. When the Embedded Erase algorithm is com­plete, 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 sta­tus of the erase operation b y using DQ7, DQ6, DQ2, or RY/BY#. ( Refer to “Write Ope ration St atus” f or info rma­tion on these status bits.)
Figure 4 illustrates the algorithm for the erase opera­tion. 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 un­lock cycles, followed by a set-up command. Two addi­tional 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 algo­rithm 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 tim­ings 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 com­mands may be written. Loading the sector erase buffer may be done in any sequence, and the number of sec­tors may be from one sector to all secto rs. The time be­tween 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 op­eration. 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 opera­tion. 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 in­terrupt 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 algo­rithm. 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. Ad­dresses are “don’t-cares” when writing the Erase Sus­pend 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 ter­minates 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 sec­tors 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 com­plete, 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 oper­ation. See “Write Operation Status” for more informa­tion.
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
Am29LV116D 19
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 de­vice 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.
Figure 4. Erase Operation
20 Am29LV116D
Page 22
Command Definitions
Table 9. Am29LV116D Command Definitions
Command Sequence
(Note 1)
Read (Note 5) 1 RA RD Reset (Note 6) 1 XXX F0
Manufacturer ID 4 555 AA 2A A 55 555 90 X00 01 Device ID,
Top Boot Block Device ID,
Bottom Boot Block Sector Protect
Autoselect (Note 7)
Verify (Note 8)
CFI Query (Note 9) 1 55 98 Byte Program 4 555 AA 2AA 55 555 A0 PA PD Unlock Bypass 3 555 AA 2AA 55 555 20 Unlock Bypass Program
(Note 10) Unlock Bypass Reset
(Note 11) Chip Erase 6 555 AA 2AA 55 555 80 555 AA 2AA 55 555 10 Sector Erase 6 555 AA 2A A 55 555 80 555 AA 2AA 55 SA 30 Erase Suspend (Note 12) 1 XXX B0 Erase Resume (Note 13) 1 XXX 30
4 555 AA 2AA 55 555 90 X01
4 555 AA 2AA 55 555 90
2 XXX A0 PA PD
2 XXX 90 XXX 00
First Second Third Fourth Fifth Sixth
Cycles
Addr Data Addr Data Addr Data Addr Data Addr Data Addr Data
Bus Cycles (Notes 2–4)
SA
X02
C7
4C 00
01
Legend:
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 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.
13. The Erase Resume command is valid only during the Erase Suspend mode.
Am29LV116D 21
Page 23
WRITE OPERATION STATUS
The device provides several bits to determine the sta­tus 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 sys­tem 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 se­quence.
During the Em bedded Program algor ithm, the device outputs on DQ7 the complement of the datum pro­grammed to DQ7. This DQ7 status also applies to pro­gramming 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 al­gorithm 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 in­formation on DQ7.
After an erase command sequence is written, if all s ec­tors selected for erasing are protected, Data# Polling on DQ7 is active f or appro ximately 100 µs , the n the de­vice returns to reading array data. If not all selected sectors are protected, the Embedded Erase algorithm erases the unprotected sectors, and ignores the se­lected 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
22 Am29LV116D
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, sev­eral 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 op­eration), and during the sector erase time-out.
T ab le 10 shows the outputs f or Toggle Bit I on DQ6. Fig­ure 6 shows the toggle bit algorithm in flowchart form, and the section “Reading Toggle Bits DQ6/DQ2” ex­plains the algorithm. Figure 18 in the “AC Characteris­tics” 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, indi­cates 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 era­sure. (The system may use either OE# or CE# to con­trol the read cycles.) But DQ2 cannot distinguish whether the sector is actively erasing or is erase-sus­pended. DQ6, by comparison, indicates whether the device is actively erasing, or is in Erase Suspend, but cannot distinguish which sectors are selected for era­sure. Thus, both status bits are required for sector and mode information. Refer to Table 10 to compare out­puts for DQ2 and DQ6.
During an Embedded Program or Erase algorithm op­eration, 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 om­plete, DQ6 stops toggling.
After an erase command sequence is written, if all s ec­tors 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 Em­bedded Erase algorithm erases the unprotected sec­tors, and ignores the selected sectors that are protected.
The system can use DQ6 and DQ2 together to deter­mine whether a sector is actively erasing or is erase­suspended. 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 Pro­gram 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 dia­gram. 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 n­ever the system initially begins reading toggle bit sta­tus, 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 com­pleted the program or eras e operation. The system can read array data on DQ7–DQ0 on the following read cy­cle.
However, if after the initial two read cycles, the system determines that the toggle bit is still toggling, the sys­tem 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
Am29LV116D 23
Page 25
must write the reset command to return to readin g array data.
The remaining scenario is that the system initially de­termines 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, de­termining the status as described in the previous para­graph. 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. Fig­ure 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 subsec­tion 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 pro­grammed 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 addi­tional sectors are selected for erasure, the entire time­out also applies after each additional sector erase com­mand. 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” sec­tion.
After the sector erase command sequence is written, the system should read the status on DQ7 (Data# Poll­ing) or DQ6 (Toggle Bit I) to ensure the device has ac­cepted the command sequence, and then read DQ3. If DQ3 is “1”, the internally controlled erase cycle has be­gun; 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 ac­cepted. Table 10 shows the outputs for DQ3.
24 Am29LV116D
Page 26
Table 10. Write Operation Status
DQ7
Standard Mode
Erase Suspend Mode
Operation
Embedded Program Algorithm DQ7# Toggle 0 N/A No toggle 0 Embedded Erase Algorithm 0 Toggle 0 1 Toggle 0 Reading within Erase
Suspended Sector Reading within Non-Erase
Suspended Sector Erase-Suspend-Program DQ7# Toggle 0 N/A N/A 0
(Note 2) DQ6
1 No toggle 0 N/A Toggle 1
Data Data Data Data Data 1
Notes:
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.
DQ5
(Note 1) DQ3
DQ2
(Note 2) RY/BY#
Am29LV116D 25
Page 27
ABSOLUTE MAXIMUM RATINGS
Storage Temperature
Plastic Packages . . . . . . . . . . . . . . . –65°C to +150°C
Ambient Temperature
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.
26 Am29LV116D
) . . . . . . . . . . . 0°C to +70°C
A
) . . . . . . . . . –40°C to +85°C
A
Page 28
DC CHARACTERISTICS CMOS Compatible
Parameter Description Test Conditions Min Typ Max Unit
V
= VSS to VCC,
I
I
I
CC1
I
LI
LIT
LO
Input Load Current
V
IN
= VCC
CC
A9 Input Load Current VCC = 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 V 35 µA
CC max
CC max
5 MHz 9 16
OE#
IL,
= VIH
1 MHz 2 4
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.5 0.8 V Input High Voltage 0.7 x V Voltage for Autoselect and
Temporary Sector Unprotect
V
CC
Output Low Voltage IOL = 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 V 0.2 5 µA
0.3 V 0.2 5 µA
±
SS
± 0.3 V;
CC
SS
±
0.3 V
= V
= 3.3 V 11.5 12.5 V
0.45 V
CC min
= –2.0 mA, VCC = V
0.85 V
CC min
VCC–0.4
CC min
2.3 2.5 V
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
15 30 mA
0.2 5 µA
VCC + 0.3 V
V
+ 30 ns.
Am29LV116D 27
Page 29
DC CHARACTERISTICS (Continued) Zero Power Flash
25
20
15
10
Supply Current in mA
5
0
0 500 1000 1500 2000 2500 3000 3500 4000
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
28 Am29LV116D
Page 30
TEST CONDITIONS
3.3 V
Table 11. Test Specifications
Test Condition -70 -90, -120 Unit
Output Load 1 TTL gate Output Load Capacitance, C
(including jig capacitance) Input Rise and Fall Times 5 ns Input Pulse Levels 0.0–3.0 V
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 RM INPUTS OUTPUTS
Steady
Changing from H to L
Changing from L to H
L
30 100 pF
1.5 V
1.5 V
3.0 V
0.0 V
Don’t Care, Any Change Permitted Changing, State Unknown
Does Not Apply Center Line is High Impedance State (High Z)
1.5 V 1.5 V
Figure 12. Input Waveforms and Measurement Levels
OutputMeasurement LevelInput
Am29LV116D 29
Page 31
AC CHARACTERISTICS Read Operations
Parameter
JEDEC Std Test Setup -70 -90 -12 0 U nit
t
AVAV
t
AVQV
t
ELQV
t
GLQV
t
EHQZ
t
GHQZ
t
Description
t
Read Cycle Time (Note 1) Min 70 90 120 ns
RC
Address to Output Delay
ACC
t
Chip Enable to Output Delay OE# = V
CE
t
Output Enable to Output Delay Max 30 35 50 ns
OE
t
Chip Enable to Output High Z (Note 1) Max 25 30 30 ns
DF
t
Output Enable to Output High Z (Note 1) Max 25 30 30 ns
DF
CE# = V OE# = V
IL
Max 70 90 120 ns
IL
Max 70 90 120 ns
IL
Speed Option
Read Min 0 ns
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)
Min 10 ns
Min 0 ns
t
AXQX
t
Notes:
1. Not 100% tested.
2. See Figure 11 and Table 11 for test specifications.
t
RC
Addresses
CE#
OE#
WE#
Outputs
RESET#
RY/BY#
0 V
Addresses Stable
t
ACC
t
OE
t
OEH
t
CE
HIGH Z
Output Valid
Figure 13. Read Operations Timings
t
OH
t
DF
HIGH Z
30 Am29LV116D
Page 32
AC CHARACTERISTICS Hardware Reset (RESET#)
Parameter
Description All Speed OptionsJEDEC Std Test Setup Unit
t
READY
t
READY
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 Width Min 500 ns
t
RP
RESET# High Time Before Read (See Note) Min 50 ns
t
RH
RESET# Low to Standby Mode Min 20 µs
t
RPD
RY/BY# Recovery Time Min 0 ns
t
RB
Note: Not 100% test ed.
RY/BY#
CE#, OE#
RESET#
t
RP
t
Ready
Max 20 µs
Max 500 ns
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
Am29LV116D 31
Page 33
AC CHARACTERISTICS Erase/Program Operations
Parameter Speed Options
JEDEC Std Description -70 -90 -120 Unit
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) Min 70 90 120 ns Address Setup Time Min 0 ns Address Hold Time Min 45 45 50 ns Data Setup Time Min 35 45 50 ns Data Hold Time Min 0 ns Output Enable Setup Time (Note 1) Min 0 ns Read Recovery Time Before Write
(OE# High to WE# Low)
Min 0 ns
CE# Setup Time Min 0 ns CE# Hold Time Min 0 ns Write Pulse Width Min 35 35 50 ns Write Pulse Width High Min 30 ns Programming Operation (Note 2) Typ 9 µs
Sector Erase Operation (Note 2) Typ 0.7 sec VCC Setup Time (Note 1) Min 50 µs Recovery Time from RY/BY# Min 0 ns Program/Erase Valid to RY/BY# Delay Min 90 ns
Notes:
1. Not 100% tested.
2. See the “Erase and Programming Performance” section for more information.
32 Am29LV116D
Page 34
AC CHARACTERISTICS
Program Command Sequence (last two cycles)
t
WC
Addresses
CE#
555h
t
CH
OE#
t
WP
WE#
t
CS
t
DS
t
DH
Data
A0h
RY/BY#
t
VCS
V
CC
Note: PA = program address, PD = program data, D
Figure 15. Program Operation Timings
Read Status Data (last two cycles)
t
AS
PA PA
t
AH
t
WPH
PD
t
BUSY
is the true data at the program address.
OUT
t
WHWH1
PA
Status
D
OUT
t
RB
Erase Command Sequence (last two cycles) Read Status Data
t
AS
555h for chip erase
VA
t
AH
VA
Addresses
t
WC
2AAh SA
CE#
t
OE#
WE#
Data
t
CS
CH
t
WP
t
WPH
t
DS
t
DH
55h
30h
10 for Chip Erase
t
BUSY
t
WHWH2
In
Progress
Complete
t
RB
RY/BY#
t
VCS
V
CC
Note: SA = sector address (for Sector Erase), VA = Valid Address for reading status data (see “Write Operation Status”).
Figure 16. Chip/Sector Erase Operation Timings
Am29LV116D 33
Page 35
AC CHARACTERISTICS
Addresses
CE#
t
CH
OE#
t
WE#
DQ7
OEH
t
ACC
t
CE
t VA
t
RC
OE
t
t
OH
Complement
DF
VA VA
Complement
True
Valid Data
High Z
DQ0–DQ6
t
BUSY
Status Data
Status Data
True
Valid Data
High Z
RY/BY#
Note: VA = Valid address. Illustration shows first status cycle after command sequence, last status read cycle, and array data read cycle.
Figure 17. Data# Polling Timings (During Embedded Algorithms)
t
RC
Addresses
CE#
OE#
WE#
DQ6/DQ2
RY/BY#
t
CH
t
BUSY
t
OEH
High Z
t
ACC
VA
t
CE
t
OE
t
DF
t
OH
(first read) (second read) (stops toggling)
VA VA
Valid Status
VA
Valid DataValid StatusValid Status
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)
34 Am29LV116D
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 OptionsJEDEC Std Description Unit
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) Min 500 ns RESET# Setup Time for Temporary Sector
Unprotect
t
VIDR
Min 4 µs
t
VIDR
Program or Erase Command Sequence
t
RSP
Figure 20. Temporary Sector Unprotect Timing Diagram
Am29LV116D 35
Page 37
AC CHARACTERISTICS
V
ID
V
RESET#
IH
SA, A6,
A1, A0
Valid* Valid* Valid*
Sector Protect/Unprotect Verify
Data
60h 60h 40h
1 µs
Sector Protect: 150 µs
Sector Unprotect: 15 ms
CE#
WE#
OE#
Note: For sector protect, A6 = 0, A1 = 1, A0 = 0. For sector unprotect, A6 = 1, A1 = 1, A0 = 0.
Figure 21. Sector Protect/Unprotect Timing Diagram
Status
36 Am29LV116D
Page 38
AC CHARACTERISTICS Alternate CE# Controlled Erase/Program Operations
Parameter Speed Options
JEDEC Std Description -70 -90 -120 Unit
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) Min 70 90 120 ns Address Setup Time Min 0 ns Address Hold Time Min 45 45 50 ns Data Setup Time Min 35 45 50 ns Data Hold Time Min 0 ns Output Enable Setup Time Min 0 ns Read Recovery Time Before Write
(OE# High to WE# Low) WE# Setup Time Min 0 ns WE# Hold Time Min 0 ns CE# Pulse Width Min 35 35 50 ns CE# Pulse Width High Min 30 ns Programming Operation (Note 2) Typ 9 µs
Sector Erase Operation (Note 2) Typ 0.7 sec
Notes:
1. Not 100% tested.
2. See the “Erase and Programming Performance” section for more information.
Min 0 ns
Am29LV116D 37
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.
Figure 22. Alternate CE# Controlled Write Operation Timings
= data written to
OUT
38 Am29LV116D
Page 40
ERASE AND PROGRAMMING PERFORMANCE
Parameter Typ (Note 1) Max (Note 2) Unit Comments
Sector Erase Time 0.7 15 s Chip Erase Time 25 s Byte Programming Time 9 300 µs
Chip Programming Time (Note 3) 18 54 s
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
Description Min Max
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 V VCC + 1.0 V
SS
–1.0 V 12.5 V
TSOP PIN CAPACITANCE
Parameter
Symbol Parameter Description Test Setup Typ Max Unit
Input Capacitance VIN = 0 6 7.5 pF
Output Capacitance V
Control Pin Capacitance VIN = 0 7.5 9 pF
= 0 8.5 12 pF
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
Parameter Test Conditions Min Unit
Minimum Pattern Data Retention Time
150°C 10 Years 125°C 20 Years
Am29LV116D 39
Page 41
PHYSICAL DIMENSIONS*
TS 040—40-Pin Standard TSOP
* For reference only. BSC is an ANSI standard for Basic Space Centering.
40 Am29LV116D
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.
Am29LV116D 41
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 sec­tor?” 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.
Temporary Sector Unprotect Table
Added note reference for t 100% tested.
Figure 21, Sector Protect/Unprotect Timing Diagram
A valid address is not required for the first write cycle; only the data 60h.
Erase and Programming Performance
In Note 2, the worst case endurance is now 1 million cycles.
WHWH1
and t
Corrected the notes refer-
WHWH2
. These parameters are
. This parameter is not
VIDR
VCS
Revision C+3 (August 1998)
Global
Added 70R speed option, changed 80R speed option to 80.
Distinctive Characteristics
Changed process technology to 0.32 µm.
Table 9, Command Definitions
The CFI Query command is now included in the table.
DC Characteristics
Moved V notes.
Figure 21, Sector Protect/Unprotect Timing Diagram
Changed timing specifications in diagram to match those in the figure of In-System Sector Protect/Unpro­tect 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 temper­ature 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.
42 Am29LV116D
Page 44
Trademarks
Copyright © 2000 Advanced Micro Devices, Inc. All rights reserved. AMD, the AMD logo, and combinations thereof are registered trademarks of Advanced Micro Devices, Inc. ExpressFlash is a trademark of Advanced Micro Devices, Inc. Product names used in this publication are for identification purposes only and may be trademarks of their respective companies.
Am29LV116D 43
Loading...