AM29LV116DT-90FF [SPANSION]

Flash, 2MX8, 90ns, PDSO40, REVERSE, MO-142BCD, TSOP-40;
AM29LV116DT-90FF
型号: AM29LV116DT-90FF
厂家: SPANSION    SPANSION
描述:

Flash, 2MX8, 90ns, PDSO40, REVERSE, MO-142BCD, TSOP-40

CD 光电二极管
文件: 总45页 (文件大小:1522K)
中文:  中文翻译
下载:  下载PDF数据表文档文件
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 document is marked with the name of the company that orig-  
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 2 Issue Date May 27, 2004  
THIS PAGE LEFT INTENTIONALLY BLANK.  
Am29LV116D  
16 Megabit (2 M x 8-Bit)  
CMOS 3.0 Volt-only Boot Sector Flash Memory  
DISTINCTIVE CHARACTERISTICS  
Single power supply operation  
20-year data retention at 125°C  
— 2.7 to 3.6 volt read and write operations for  
battery-powered applications  
— Reliable operation for the life of the system  
Package option  
Manufactured on 0.23 µm process technology  
— 40-pin TSOP  
— Compatible with and replaces Am29LV116B  
device  
CFI (Common Flash Interface) compliant  
— Provides device-specific information to the  
system, allowing host software to easily  
reconfigure for different Flash devices  
High performance  
— Access times as fast as 70 ns  
Ultra low power consumption (typical values at  
Compatibility with JEDEC standards  
5 MHz)  
— Pinout and software compatible with single-  
power supply Flash  
— 200 nA Automatic Sleep mode current  
— 200 nA standby mode current  
— 9 mA read current  
— Superior inadvertent write protection  
Data# Polling and toggle bits  
— 15 mA program/erase current  
— Provides a software method of detecting program  
or erase operation completion  
Flexible sector architecture  
— One 16 Kbyte, two 8 Kbyte, one 32 Kbyte, and  
thirty-one 64 Kbyte sectors  
Ready/Busy# pin (RY/BY#)  
— Provides a hardware method of detecting  
program or erase cycle completion  
— Supports full chip erase  
— Sector Protection features:  
Erase Suspend/Erase Resume  
A hardware method of locking a sector to prevent  
any program or erase operations within that sector  
— Suspends an erase operation to read data from,  
or program data to, a sector that is not being  
erased, then resumes the erase operation  
Sectors can be locked in-system or via  
programming equipment  
Hardware reset pin (RESET#)  
Temporary Sector Unprotect feature allows code  
changes in previously locked sectors  
— Hardware method to reset the device to reading  
array data  
Unlock Bypass Program Command  
— Reduces overall programming time when issuing  
multiple program command sequences  
Top or bottom boot block configurations  
available  
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 cycle 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 modifications due to changes in technical specifications.  
Publication# 21359 Rev: E Amendment/+2  
Issue Date: May 27, 2004  
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 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 program or erase cycle has  
been completed, the device is ready to read array data  
or accept another command.  
The sector erase architecture allows memory sectors  
to be erased and reprogrammed without affecting the  
data contents of other sectors. The device is fully  
erased when shipped from the factory.  
The standard device offers access times of 70, 90, and  
120 ns, allowing high speed microprocessors to  
operate without wait states. To eliminate bus contention  
the device has separate chip enable (CE#), write  
enable (WE#) and output enable (OE#) controls.  
Hardware data protection measures include a low  
VCC detector that automatically inhibits write opera-  
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 device requires only a single 3.0 volt power 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 microprocessor write timings. Register contents  
serve as input to an internal state-machine that con-  
trols the erase and programming circuitry. Write cycles  
also internally latch addresses and data needed for the  
programming and erase operations. Reading data out  
of the device is similar to reading from other Flash or  
EPROM devices.  
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# pin terminates any operation  
in progress and resets the internal state machine to  
reading array data. The RESET# pin may 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.  
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 requiring only two  
write cycles to program data instead of four.  
The device offers two power-saving features. When ad-  
dresses have been stable for a specified amount of  
time, the device enters the automatic sleep mode.  
The system can also place the device into the standby  
mode. Power consumption is greatly reduced in both  
these modes.  
Device erasure occurs by executing the erase com-  
mand sequence. This initiates the Embedded Erase  
algorithm—an internal algorithm that automatically  
preprograms the array (if it is not already programmed)  
before executing the erase operation. During erase, the  
device automatically times the erase pulse widths and  
verifies proper cell margin.  
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 bits within  
a sector simultaneously via Fowler-Nordheim tun-  
neling. The data is programmed using hot electron injec-  
tion.  
4
Am29LV116D  
TABLE OF CONTENTS  
Product Selector Guide . . . . . . . . . . . . . . . . . . . . .6  
Connection Diagrams . . . . . . . . . . . . . . . . . . . . . . .7  
Pin Configuration . . . . . . . . . . . . . . . . . . . . . . . . . .8  
Logic Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8  
Ordering Information . . . . . . . . . . . . . . . . . . . . . . .9  
Standard Products .................................................................... 9  
Device Bus Operations . . . . . . . . . . . . . . . . . . . . .10  
Table 1. Am29LV116D Device Bus Operations ..............................10  
Requirements for Reading Array Data ................................... 10  
Writing Commands/Command Sequences ............................ 10  
Program and Erase Operation Status .................................... 11  
Standby Mode ........................................................................ 11  
Automatic Sleep Mode ........................................................... 11  
RESET#: Hardware Reset Pin ............................................... 11  
Output Disable Mode .............................................................. 11  
Table 2. Am29LV116DT Top Boot Sector Address Table ..............12  
Table 3. Am29LV116DB Bottom Boot Sector Address Table .........13  
Autoselect Mode ..................................................................... 14  
Table 4. Am29LV116D Autoselect Codes (High Voltage Method) ..14  
Sector Protection/Unprotection ............................................... 14  
Temporary Sector Unprotect .................................................. 14  
Figure 1. In-System Sector Protect/Unprotect Algorithms .............. 15  
Figure 2. Temporary Sector Unprotect Operation........................... 16  
Hardware Data Protection ...................................................... 16  
Low VCC Write Inhibit .............................................................. 16  
Write Pulse “Glitch” Protection ............................................... 16  
Logical Inhibit .......................................................................... 16  
Power-Up Write Inhibit ............................................................ 16  
Common Flash Memory Interface (CFI). . . . . . . 16  
Table 5. CFI Query Identification String ..........................................17  
Table 6. System Interface String .....................................................17  
Table 7. Device Geometry Definition ..............................................18  
Table 8. Primary Vendor-Specific Extended Query ........................18  
Command Definitions . . . . . . . . . . . . . . . . . . . . . .19  
Reading Array Data ................................................................ 19  
Reset Command ..................................................................... 19  
Autoselect Command Sequence ............................................ 19  
Byte Program Command Sequence ....................................... 19  
Unlock Bypass Command Sequence ..................................... 20  
Figure 3. Program Operation .......................................................... 20  
Chip Erase Command Sequence ........................................... 20  
Sector Erase Command Sequence ........................................ 21  
Erase Suspend/Erase Resume Commands ........................... 21  
Figure 4. Erase Operation............................................................... 22  
Command Definitions ............................................................. 23  
Table 9. Am29LV116D Command Definitions ...............................23  
Write Operation Status . . . . . . . . . . . . . . . . . . . . .24  
DQ7: Data# Polling ................................................................. 24  
Figure 5. Data# Polling Algorithm ................................................... 24  
RY/BY#: Ready/Busy# ........................................................... 25  
DQ6: Toggle Bit I .................................................................... 25  
DQ2: Toggle Bit II ................................................................... 25  
Reading Toggle Bits DQ6/DQ2 .............................................. 25  
DQ5: Exceeded Timing Limits ................................................ 26  
DQ3: Sector Erase Timer ....................................................... 26  
Figure 6. Toggle Bit Algorithm........................................................ 26  
Table 10. Write Operation Status ................................................... 27  
Absolute Maximum Ratings . . . . . . . . . . . . . . . . 28  
Figure 7. Maximum Negative Overshoot Waveform ...................... 28  
Figure 8. Maximum Positive Overshoot Waveform........................ 28  
Operating Ranges. . . . . . . . . . . . . . . . . . . . . . . . . 28  
DC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . 29  
CMOS Compatible .................................................................. 29  
Zero Power Flash ................................................................... 30  
Figure 9. I  
Current vs. Time (Showing Active and  
CC1  
Automatic Sleep Currents)............................................................. 30  
Figure 10. Typical I vs. Frequency ........................................... 30  
CC1  
Test Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . 31  
Figure 11. Test Setup..................................................................... 31  
Table 11. Test Specifications ......................................................... 31  
Key to Switching Waveforms .................................................. 31  
Figure 12. Input Waveforms and Measurement Levels ................. 31  
AC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . 32  
Read Operations .................................................................... 32  
Figure 13. Read Operations Timings ............................................. 32  
Hardware Reset (RESET#) .................................................... 33  
Figure 14. RESET# Timings .......................................................... 33  
Erase/Program Operations ..................................................... 34  
Figure 15. Program Operation Timings.......................................... 35  
Figure 16. Chip/Sector Erase Operation Timings .......................... 35  
Figure 17. Data# Polling Timings (During Embedded Algorithms). 36  
Figure 18. Toggle Bit Timings (During Embedded Algorithms)...... 36  
Figure 19. DQ2 vs. DQ6................................................................. 37  
Temporary Sector Unprotect .................................................. 37  
Figure 20. Temporary Sector Unprotect Timing Diagram .............. 37  
Figure 21. Sector Protect/Unprotect Timing Diagram .................... 38  
Figure 22. Alternate CE# Controlled Write Operation Timings ...... 40  
Erase and Programming Performance . . . . . . . 41  
Latchup Characteristics. . . . . . . . . . . . . . . . . . . . 41  
TSOP Pin Capacitance . . . . . . . . . . . . . . . . . . . . . 41  
Data Retention. . . . . . . . . . . . . . . . . . . . . . . . . . . . 41  
Physical Dimensions . . . . . . . . . . . . . . . . . . . . . . 42  
TS 040—40-Pin Standard TSOP ............................................ 42  
TSR040—40-Pin Reverse TSOP ........................................... 43  
Revision Summary . . . . . . . . . . . . . . . . . . . . . . . . 44  
Revision A (October 1997) ..................................................... 44  
Revision B (October 1997) ..................................................... 44  
Revision C (December 1997) ................................................. 44  
Revision C+1 (January 1998) ................................................. 44  
Revision C+2 (March 1998) .................................................... 44  
Revision C+3 (August 1998) ................................................... 44  
Revision D (January 1999) ..................................................... 44  
Revision E (February 2, 2000) ................................................ 44  
Revision E+1 (November 7, 2000) ......................................... 44  
Added table of contents. Deleted burn-in option in ordering infor-  
mation section. ....................................................................... 44  
Revision E+2 (May 27, 2004) ................................................. 44  
Am29LV116D  
5
PRODUCT SELECTOR GUIDE  
Family Part Number  
Am29LV116D  
Speed Options  
V
= 2.7–3.6 V  
-70  
70  
70  
30  
-90  
90  
90  
35  
-120  
120  
120  
50  
CC  
Max access time, ns (t  
)
ACC  
Max CE# access time, ns (t  
)
CE  
Max OE# access time, ns (t  
)
OE  
Note: See “AC Characteristics” for full specifications.  
BLOCK DIAGRAM  
DQ0DQ7  
RY/BY#  
V
CC  
Sector Switches  
V
SS  
Erase Voltage  
Generator  
Input/Output  
Buffers  
RESET#  
WE#  
State  
Control  
Command  
Register  
PGM Voltage  
Generator  
Data  
Latch  
Chip Enable  
Output Enable  
Logic  
STB  
CE#  
OE#  
Y-Decoder  
Y-Gating  
STB  
V
Detector  
Timer  
CC  
Cell Matrix  
X-Decoder  
A0–A20  
6
Am29LV116D  
CONNECTION DIAGRAMS  
A17  
VSS  
A16  
A15  
A14  
A13  
A12  
A11  
A9  
1
2
3
4
40  
39  
38  
37  
36  
35  
34  
33  
32  
31  
30  
29  
28  
27  
26  
25  
24  
23  
22  
21  
A20  
A19  
A10  
DQ7  
DQ6  
DQ5  
DQ4  
VCC  
VCC  
5
6
7
A8  
8
WE#  
RESET#  
NC  
RY/BY#  
A18  
A7  
9
10  
11  
12  
13  
14  
15  
16  
17  
18  
19  
20  
40-Pin Standard TSOP  
NC  
DQ3  
DQ2  
DQ1  
DQ0  
OE#  
VSS  
A6  
A5  
A4  
A3  
A2  
A1  
CE#  
A0  
A17  
VSS  
1
2
3
4
5
6
7
8
40  
39  
38  
37  
36  
35  
34  
33  
32  
31  
30  
29  
28  
27  
26  
25  
24  
23  
22  
21  
A16  
A15  
A14  
A13  
A12  
A11  
A9  
A20  
A19  
A10  
DQ7  
DQ6  
DQ5  
DQ4  
VCC  
VCC  
NC  
DQ3  
DQ2  
DQ1  
DQ0  
A8  
9
WE#  
RESET#  
NC  
RY/BY#  
A18  
A7  
A6  
A5  
A4  
A3  
10  
11  
12  
13  
14  
15  
16  
17  
18  
19  
20  
40-Pin Reverse TSOP  
OE#  
VSS  
A2  
A1  
CE#  
A0  
Am29LV116D  
7
PIN CONFIGURATION  
LOGIC SYMBOL  
A0–A20  
= 21 addresses  
21  
DQ0–DQ7 = 8 data inputs/outputs  
A0–A20  
8
CE#  
=
=
=
=
=
=
Chip enable  
DQ0–DQ7  
OE#  
Output enable  
WE#  
Write enable  
CE#  
OE#  
RESET#  
RY/BY#  
VCC  
Hardware reset pin, active low  
Ready/Busy output  
WE#  
RESET#  
3.0 volt-only single power supply  
(see Product Selector Guide for speed  
options and voltage supply tolerances)  
RY/BY#  
VSS  
NC  
=
=
Device ground  
Pin not connected internally  
8
Am29LV116D  
ORDERING INFORMATION  
Standard Products  
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
I
=
=
=
=
Commercial (0°C to +70°C)  
Industrial (–40°C to +85°C)  
Commercial (0°C to +70°C) with Pb-free package  
D
F
Industrial (–40°C to +85°C) with Pb-free package  
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
B
=
=
Top Sector  
Bottom Sector  
DEVICE NUMBER/DESCRIPTION  
Am29LV116D  
16 Megabit (2 M x 8-Bit) CMOS Flash Memory  
3.0 Volt-only Read, Program and Erase  
Valid Combinations  
Valid Combinations  
Valid Combinations list configurations planned to be sup-  
ported in volume for this device. Consult the local AMD sales  
office to confirm availability of specific valid combinations and  
to check on newly released combinations.  
Am29LV116DT-70,  
Am29LV116DB-70  
Am29LV116DT-90,  
Am29LV116DB-90  
EC, EI, FC, FI, ED, EF  
Am29LV116DT-120,  
Am29LV116DB-120  
Am29LV116D  
9
DEVICE BUS OPERATIONS  
This section describes the requirements and use of the  
device bus operations, which are initiated through the  
internal command register. The command register it-  
self does not occupy any addressable memory loca-  
tion. The register is composed of latches that store the  
commands, along with the address and data informa-  
tion needed to execute the command. The contents of  
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 levels they require, and the resulting  
output. The following subsections describe each of  
these operations in further detail.  
Table 1. Am29LV116D Device Bus Operations  
Operation  
CE#  
L
OE#  
L
WE#  
H
RESET#  
Addresses  
DQ0–DQ7  
Read  
Write  
H
H
A
A
D
OUT  
IN  
IN  
L
H
L
D
IN  
V
0.3 V  
V
CC  
0.3 V  
CC  
Standby  
X
X
X
High-Z  
Output Disable  
Reset  
L
H
X
H
X
H
L
X
X
High-Z  
High-Z  
X
Sector Addresses,  
A6 = L, A1 = H, A0 = L  
Sector Protect (See Note)  
L
H
L
V
D
D
, D  
, D  
ID  
IN  
IN  
OUT  
OUT  
Sector Addresses  
A6 = H, A1 = H, A0 = L  
Sector Unprotect (See Note)  
L
H
X
L
V
V
ID  
Temporary Sector Unprotect  
X
X
A
D
IN  
ID  
IN  
Legend:  
L = Logic Low = V , H = Logic High = V , V = 12.0 0.5 V, X = Don’t Care, A = Address In, D = Data In, D  
= Data Out  
IL  
IH  
ID  
IN  
IN  
OUT  
Note: The sector protect and sector unprotect functions may also be implemented via programming equipment. See the “Sector  
Protection/Unprotection” section.  
Requirements for Reading Array Data  
Writing Commands/Command Sequences  
To read array data from the outputs, the system must  
drive the CE# and OE# pins to VIL. CE# is the power  
control and selects the device. OE# is the output con-  
trol and gates array data to the output pins. WE# should  
remain at VIH.  
To write 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 VIL, and OE# to VIH.  
The device features 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.  
The internal state machine is set for reading array data  
upon device power-up, or after a hardware reset. This  
ensures that no spurious alteration of the memory 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 inputs produce valid data on the  
device data outputs. The device remains enabled for  
read access until the command register contents are  
altered.  
An erase operation can erase one sector, multiple sec-  
tors, or the entire device. Tables 2 and 3 indicate the  
address space that each sector occupies. A “sector ad-  
dress” consists of the address bits required to uniquely  
select a sector. The “Command Definitions” section  
has details on erasing a sector or the entire chip, or  
suspending/resuming the erase operation.  
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. ICC1 in  
the DC Characteristics table represents the active cur-  
rent specification for reading array data.  
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  
10  
Am29LV116D  
mode. Refer to the Autoselect Mode and Autoselect  
Command Sequence sections for more information.  
access timings provide new data when addresses are  
changed. While in sleep mode, output data is latched  
and always available to the system. ICC5 in the DC  
Characteristics table represents the automatic sleep  
mode current specification.  
ICC2 in the DC Characteristics table represents the ac-  
tive current specification for the write mode. The “AC  
Characteristics” section contains timing specification  
tables and timing diagrams for write operations.  
RESET#: Hardware Reset Pin  
The RESET# pin provides a hardware method of reset-  
ting the device to reading array data. When the RE-  
SET# pin is driven low for at least a period of tRP, the  
device immediately terminates any operation in  
progress, tristates all output pins, and ignores all  
read/write commands for the duration of the RESET#  
pulse. The device also resets the internal state 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.  
Program and Erase Operation Status  
During an erase or program operation, the system may  
check the status of the operation by reading the status  
bits on DQ7–DQ0. Standard read cycle timings and ICC  
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 greatly reduced, and the  
outputs are placed in the high impedance state, inde-  
pendent of the OE# input.  
Current is reduced for the duration of the RESET#  
pulse. When RESET# is held at VSS 0.3 V, the device  
draws CMOS standby current (ICC4). If RESET# is held  
at VIL but not within VSS 0.3 V, the standby current will  
be greater.  
The device enters the CMOS standby mode when the  
CE# and RESET# pins are both held at VCC 0.3 V.  
(Note that this is a more restricted voltage range than  
VIH.) If CE# and RESET# are held at VIH, but not within  
VCC 0.3 V, the device will be in the standby mode, but  
the standby current will be greater. The device requires  
standard access time (tCE) for read access when the  
device is in either of these standby modes, before it is  
ready to read data.  
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 operation is complete, which requires a  
time of tREADY (during Embedded Algorithms). The  
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 tREADY (not during Embedded Algo-  
rithms). The system can read data tRH after the RE-  
SET# pin returns to VIH.  
The device also enters the standby 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.  
ICC3 in the DC Characteristics table represents the  
standby current specification.  
Refer to the AC Characteristics tables for RESET# pa-  
rameters and to Figure 14 for the timing diagram.  
Automatic Sleep Mode  
Output Disable Mode  
When the OE# input is at VIH, output from the device is  
disabled. The output pins are placed in the high imped-  
ance state.  
The automatic sleep mode minimizes Flash device  
energy consumption. The device automatically enables  
this mode when addresses remain stable for tACC + 30  
ns. The automatic sleep mode is independent of the  
CE#, WE#, and OE# control signals. Standard address  
Am29LV116D  
11  
Table 2. Am29LV116DT Top Boot Sector Address Table  
Sector Size  
Address Range  
(in hexadecimal)  
Sector  
SA0  
A20  
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
A19  
0
0
0
0
0
0
0
0
1
1
1
1
1
1
1
1
0
0
0
0
0
0
0
0
1
1
1
1
1
1
1
1
1
1
1
A18  
0
0
0
0
1
1
1
1
0
0
0
0
1
1
1
1
0
0
0
0
1
1
1
1
0
0
0
0
1
1
1
1
1
1
1
A17  
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
1
1
1
A16  
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
1
1
1
A15  
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
0
A14  
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
0
A13  
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
0
(Kbytes)  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
32  
8
000000–00FFFF  
010000–01FFFF  
020000–02FFFF  
030000–03FFFF  
040000–04FFFF  
050000–05FFFF  
060000–06FFFF  
070000–07FFFF  
080000–08FFFF  
090000–09FFFF  
0A0000–0AFFFF  
0B0000–0BFFFF  
0C0000–0CFFFF  
0D0000–0DFFFF  
0E0000–0EFFFF  
0F0000–0FFFFF  
100000–10FFFF  
110000–11FFFF  
120000–12FFFF  
130000–13FFFF  
140000–14FFFF  
150000–15FFFF  
160000–16FFFF  
170000–17FFFF  
180000–18FFFF  
190000–19FFFF  
1A0000–1AFFFF  
1B0000–1BFFFF  
1C0000–1CFFFF  
1D0000–1DFFFF  
1E0000–1EFFFF  
1F0000–1F7FFF  
1F8000–1F9FFF  
1FA000–1FBFFF  
1FC000–1FFFFF  
SA1  
SA2  
SA3  
SA4  
SA5  
SA6  
SA7  
SA8  
SA9  
SA10  
SA11  
SA12  
SA13  
SA14  
SA15  
SA16  
SA17  
SA18  
SA19  
SA20  
SA21  
SA22  
SA23  
SA24  
SA25  
SA26  
SA27  
SA28  
SA29  
SA30  
SA31  
SA32  
SA33  
SA34  
1
1
0
1
8
1
1
X
16  
12  
Am29LV116D  
Table 3. Am29LV116DB Bottom Boot Sector Address Table  
Sector Size  
Address Range  
(in hexadecimal)  
Sector  
SA0  
A20  
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
A19  
0
0
0
0
0
0
0
0
0
0
0
1
1
1
1
1
1
1
1
0
0
0
0
0
0
0
0
1
1
1
1
1
1
1
1
A18  
0
0
0
0
0
0
0
1
1
1
1
0
0
0
0
1
1
1
1
0
0
0
0
1
1
1
1
0
0
0
0
1
1
1
1
A17  
0
0
0
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
A16  
0
0
0
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
A15  
A14  
A13  
X
0
(Kbytes)  
16  
8
0
0
000000–003FFF  
004000–005FFF  
006000–007FFF  
008000–00FFFF  
010000–01FFFF  
020000–02FFFF  
030000–03FFFF  
040000–04FFFF  
050000–05FFFF  
060000–06FFFF  
070000–07FFFF  
080000–08FFFF  
090000–09FFFF  
0A0000–0AFFFF  
0B0000–0BFFFF  
0C0000–0CFFFF  
0D0000–0DFFFF  
0E0000–0EFFFF  
0F0000–0FFFFF  
100000–10FFFF  
110000–11FFFF  
120000–12FFFF  
130000–13FFFF  
140000–14FFFF  
150000–15FFFF  
160000–16FFFF  
170000–17FFFF  
180000–18FFFF  
190000–19FFFF  
1A0000–1AFFFF  
1B0000–1BFFFF  
1C0000–1CFFFF  
1D0000–1DFFFF  
1E0000–1EFFFF  
1F0000–1FFFFF  
SA1  
0
1
SA2  
0
1
1
8
SA3  
1
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
32  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
64  
SA4  
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
SA5  
SA6  
SA7  
SA8  
SA9  
SA10  
SA11  
SA12  
SA13  
SA14  
SA15  
SA16  
SA17  
SA18  
SA19  
SA20  
SA21  
SA22  
SA23  
SA24  
SA25  
SA26  
SA27  
SA28  
SA29  
SA30  
SA31  
SA32  
SA33  
SA34  
Am29LV116D  
13  
Table 4. In addition, when verifying sector protection,  
the sector address must appear on the appropriate  
highest order address bits (see Tables 2 and 3). Table  
4 shows the remaining address bits that are 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.  
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 programming equipment  
to automatically match a device to be programmed with  
its corresponding programming algorithm. However,  
the autoselect codes can also be accessed in-system  
through the command register.  
To access the autoselect codes in-system, the host  
system can issue the autoselect command via the  
command register, as shown in Table 9. This method  
does not require VID. See “Command Definitions” for  
details on using the autoselect mode.  
When using programming equipment, the autoselect  
mode requires VID (11.5 V to 12.5 V) on address pin  
A9. Address pins A6, A1, and A0 must be as shown in  
Table 4. Am29LV116D Autoselect Codes (High Voltage Method)  
A20 A12  
to to  
OE# WE# A13 A10  
A8  
to  
A7  
A5  
to  
A2  
DQ7  
to  
DQ0  
Description  
CE#  
A9  
A6  
A1  
A0  
Manufacturer ID: AMD  
L
L
L
H
H
X
X
X
X
V
X
X
L
X
X
L
L
01h  
C7h  
ID  
ID  
Device ID: Am29LV116D  
(Top Boot Block)  
L
L
V
L
L
L
L
H
H
Device ID: Am29LV116D  
(Bottom Boot Block)  
L
L
H
H
X
X
X
V
X
X
X
X
4Ch  
ID  
ID  
01h  
(protected)  
Sector Protection Verification  
L
SA  
V
L
H
L
00h  
(unprotected)  
L = Logic Low = V , H = Logic High = V , SA = Sector Address, X = Don’t care.  
IL  
IH  
lication number 21586 contains further details; contact  
an AMD representative to request a copy.  
Sector Protection/Unprotection  
The hardware sector protection feature disables both  
program and erase operations in any sector. The hard-  
ware sector unprotection feature re-enables both pro-  
gram and erase operations in previously protected  
sectors. Sector protection/unprotection can be imple-  
mented via two methods.  
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™ Service. Contact an  
AMD representative for details.  
The primary method requires VID on the RESET# pin  
only, and can be implemented either in-system or via  
programming equipment. Figure 1 shows the algo-  
rithms and Figure 21 shows the timing diagram. This  
method uses standard microprocessor bus cycle tim-  
ing. For sector unprotect, all unprotected sectors must  
first be protected prior to the first sector unprotect write  
cycle.  
It is possible to determine whether a sector is protected  
or unprotected. See “Autoselect Mode” for details.  
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 VID. During this mode, formerly protected  
sectors can be programmed or erased by selecting the  
sector addresses. Once VID is removed from the RE-  
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.  
The alternate method intended only for programming  
equipment requires VID on address pin A9 and OE#.  
This method is compatible with programmer routines  
written for earlier 3.0 volt-only AMD flash devices. Pub-  
14  
Am29LV116D  
START  
START  
Protect all sectors:  
The indicated portion  
of the sector protect  
algorithm must be  
performed for all  
PLSCNT = 1  
PLSCNT = 1  
RESET# = VID  
RESET# = VID  
unprotected sectors  
prior to issuing the  
first sector  
Wait 1 µs  
Wait 1 µs  
unprotect address  
No  
First Write  
Cycle = 60h?  
No  
First Write  
Cycle = 60h?  
Temporary Sector  
Unprotect Mode  
Temporary Sector  
Unprotect Mode  
Yes  
Yes  
Set up sector  
address  
No  
All sectors  
protected?  
Sector Protect:  
Write 60h to sector  
address with  
A6 = 0, A1 = 1,  
A0 = 0  
Yes  
Set up first sector  
address  
Sector Unprotect:  
Wait 150 µs  
Write 60h to sector  
address with  
A6 = 1, A1 = 1,  
A0 = 0  
Verify Sector  
Protect: Write 40h  
to sector address  
with A6 = 0,  
Reset  
PLSCNT = 1  
Increment  
PLSCNT  
Wait 15 ms  
A1 = 1, A0 = 0  
Verify Sector  
Unprotect: Write  
40h to sector  
address with  
A6 = 1, A1 = 1,  
A0 = 0  
Read from  
sector address  
with A6 = 0,  
A1 = 1, A0 = 0  
Increment  
PLSCNT  
No  
No  
PLSCNT  
= 25?  
Read from  
sector address  
with A6 = 1,  
Data = 01h?  
Yes  
A1 = 1, A0 = 0  
No  
Yes  
Set up  
next sector  
address  
Yes  
No  
PLSCNT  
= 1000?  
Protect another  
sector?  
Data = 00h?  
Yes  
Device failed  
No  
Yes  
Remove VID  
from RESET#  
No  
Last sector  
verified?  
Device failed  
Write reset  
command  
Yes  
Remove VID  
Sector Unprotect  
Algorithm  
from RESET#  
Sector Protect  
Algorithm  
Sector Protect  
complete  
Write reset  
command  
Sector Unprotect  
complete  
Figure 1. In-System Sector Protect/Unprotect Algorithms  
Am29LV116D  
15  
against inadvertent writes (refer to Table 9 for com-  
mand definitions). In addition, the following hardware  
data protection measures prevent accidental erasure  
or programming, which might otherwise be caused by  
spurious system level signals during VCC power-up and  
power-down transitions, or from system noise.  
START  
RESET# = V  
(Note 1)  
ID  
Low V  
Write Inhibit  
CC  
When VCC is less than VLKO, the device does not ac-  
cept any write cycles. This protects data during VCC  
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 VCC  
is greater than VLKO. The system must provide the  
proper signals to the control pins to prevent uninten-  
Perform Erase or  
Program Operations  
RESET# = V  
IH  
tional writes when VCC is greater than VLKO  
.
Temporary Sector  
Unprotect Completed  
(Note 2)  
Write Pulse “Glitch” Protection  
Noise pulses of less than 5 ns (typical) on OE#, CE# or  
WE# do not initiate a write cycle.  
Logical Inhibit  
Notes:  
Write cycles are inhibited by holding any one of OE# =  
VIL, CE# = VIH or WE# = VIH. To initiate a write cycle,  
CE# and WE# must be a logical zero while OE# is a  
logical one.  
1. All protected sectors unprotected.  
2. All previously protected sectors are protected once  
again.  
Power-Up Write Inhibit  
Figure 2. Temporary Sector Unprotect Operation  
If WE# = CE# = VIL and OE# = VIH during power up, the  
device does not accept commands on the rising edge  
of WE#. The internal state machine is automatically  
reset to reading array data on power-up.  
Hardware Data Protection  
The command sequence requirement of unlock cycles  
for programming or erasing provides data protection  
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.  
COMMON FLASH MEMORY INTERFACE  
(CFI)  
The Common Flash Interface (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. Software support can then be device-indepen-  
dent, JEDEC ID-independent, and forward- and back-  
ward-compatible for the specified flash device families.  
Flash vendors can standardize their existing interfaces  
for long-term compatibility.  
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, available via the World  
Wide Web at http://www.amd.com/products/nvd/over-  
view/cfi.html. Alternatively, contact an AMD represen-  
tative for copies of these documents.  
This device enters the CFI Query mode when the  
system writes the CFI Query command, 98h, to  
address 55h, any time the device is ready to read array  
16  
Am29LV116D  
Table 5. CFI Query Identification String  
Description  
Addresses  
Data  
10h  
11h  
12h  
51h  
52h  
59h  
Query Unique ASCII string “QRY”  
13h  
14h  
02h  
00h  
Primary OEM Command Set  
15h  
16h  
40h  
00h  
Address for Primary Extended Table  
17h  
18h  
00h  
00h  
Alternate OEM Command Set (00h = none exists)  
Address for Alternate OEM Extended Table (00h = none exists)  
19h  
1Ah  
00h  
00h  
Table 6. System Interface String  
Description  
Addresses  
Data  
V
Min. (write/erase)  
CC  
1Bh  
27h  
D7–D4: volt, D3–D0: 100 millivolt  
V
Max. (write/erase)  
CC  
1Ch  
36h  
D7–D4: volt, D3–D0: 100 millivolt  
1Dh  
1Eh  
1Fh  
20h  
21h  
22h  
23h  
24h  
25h  
26h  
00h  
00h  
04h  
00h  
0Ah  
00h  
05h  
00h  
04h  
00h  
V
V
Min. voltage (00h = no V pin present)  
PP  
PP  
PP  
Max. voltage (00h = no V pin present)  
PP  
N
Typical timeout per single byte/word write 2 µs  
N
Typical timeout for Min. size buffer write 2 µs (00h = not supported)  
N
Typical timeout per individual block erase 2 ms  
N
Typical timeout for full chip erase 2 ms (00h = not supported)  
N
Max. timeout for byte/word write 2 times typical  
N
Max. timeout for buffer write 2 times typical  
N
Max. timeout per individual block erase 2 times typical  
N
Max. timeout for full chip erase 2 times typical (00h = not supported)  
Am29LV116D  
17  
Table 7. Device Geometry Definition  
Description  
Addresses  
Data  
N
27h  
15h  
Device Size = 2 byte  
28h  
29h  
00h  
00h  
Flash Device Interface description (refer to CFI publication 100)  
N
2Ah  
2Bh  
00h  
00h  
Max. number of byte in multi-byte write = 2  
(00h = not supported)  
2Ch  
04h  
Number of Erase Block Regions within device  
2Dh  
2Eh  
2Fh  
30h  
00h  
00h  
40h  
00h  
Erase Block Region 1 Information  
(refer to the CFI specification or CFI publication 100)  
31h  
32h  
33h  
34h  
01h  
00h  
20h  
00h  
Erase Block Region 2 Information  
Erase Block Region 3 Information  
Erase Block Region 4 Information  
35h  
36h  
37h  
38h  
00h  
00h  
80h  
00h  
39h  
3Ah  
3Bh  
3Ch  
1Eh  
00h  
00h  
01h  
Table 8. Primary Vendor-Specific Extended Query  
Data Description  
Addresses  
40h  
41h  
42h  
50h  
52h  
49h  
Query-unique ASCII string “PRI”  
43h  
44h  
31h  
30h  
Major version number, ASCII  
Minor version number, ASCII  
Address Sensitive Unlock  
0 = Required, 1 = Not Required  
45h  
46h  
00h  
02h  
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  
47h  
48h  
01h  
01h  
Sector Temporary Unprotect: 00 = Not Supported, 01 = Supported  
Sector Protect/Unprotect scheme  
49h  
04h  
01 = 29F040 mode, 02 = 29F016 mode,  
03 = 29F400 mode, 04 = 29LV800A mode  
4Ah  
4Bh  
00h  
00h  
Simultaneous Operation: 00 = Not Supported, 01 = Supported  
Burst Mode Type: 00 = Not Supported, 01 = Supported  
Page Mode Type: 00 = Not Supported, 01 = 4 Word Page,  
02 = 8 Word Page  
4Ch  
00h  
18  
Am29LV116D  
COMMAND DEFINITIONS  
Writing specific address and data commands or se-  
quences into the command register initiates device op-  
erations. Table 9 defines the valid register command  
sequences. Writing incorrect address and data val-  
ues or writing them in the improper sequence resets  
the device to reading array data.  
The reset command may be written between the se-  
quence cycles in an autoselect command sequence.  
Once in the autoselect mode, the reset command must  
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).  
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.  
Autoselect Command Sequence  
The autoselect command sequence allows the host  
system to access the manufacturer and devices codes,  
and determine whether or not a sector is protected.  
Table 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 requires VID  
on address bit A9.  
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 completing an Embedded Program or Em-  
bedded Erase algorithm.  
The autoselect command sequence is initiated by writ-  
ing two unlock cycles, followed by the autoselect com-  
mand. The device then enters the autoselect mode,  
and the system may read at any address any number  
of times, without initiating another command sequence.  
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.  
After the device accepts an Erase 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 again read array  
data with the same exception. See “Erase Sus-  
pend/Erase Resume Commands” for more information  
on this mode.  
The system must issue the reset command to re-en-  
able the device for reading array data if DQ5 goes high,  
or while in the autoselect mode. See the “Reset Com-  
mand” section, next.  
The system must write the reset command to exit the  
autoselect mode and return to reading array data.  
Byte Program Command Sequence  
The device programs one byte of data for each program  
operation. The command sequence requires four bus  
cycles, and is initiated by writing 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  
system is not required to provide further controls or tim-  
ings. The device automatically generates the program  
pulses and verifies the programmed cell margin. Table  
9 shows the address and data requirements for the  
byte program command sequence.  
See also “Requirements for Reading Array 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.  
Reset Command  
Writing the reset command to the device 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.  
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 by using DQ7,  
DQ6, or RY/BY#. See “Write Operation Status” for in-  
formation on these status bits.  
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.  
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-  
Am29LV116D  
19  
quence should be reinitiated once the device has reset  
to reading array data, to ensure data integrity.  
START  
Programming is allowed in any sequence and 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 operation 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”.  
Write Program  
Command Sequence  
Data Poll  
from System  
Unlock Bypass Command Sequence  
Embedded  
Program  
algorithm  
in progress  
The unlock bypass feature allows the system to pro-  
gram bytes to the device faster than using the standard  
program command sequence. The unlock bypass com-  
mand sequence is initiated by first writing two unlock  
cycles. This is followed by a third write cycle containing  
the unlock bypass command, 20h. The device then en-  
ters the unlock bypass mode. A two-cycle unlock 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 the requirements for the com-  
mand sequence.  
Verify Data?  
Yes  
No  
No  
Increment Address  
Last Address?  
Yes  
Programming  
Completed  
During the unlock bypass mode, only 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. Addresses are  
don’t cares for both cycles. The device then returns to  
reading array data.  
Note: See Table 9 for program command sequence.  
Figure 3. Program Operation  
Chip Erase Command Sequence  
Chip erase is a six bus cycle operation. The chip erase  
command sequence is initiated by writing two unlock  
cycles, followed by a set-up command. Two additional  
unlock write cycles are then followed by the chip erase  
command, which in turn invokes the Embedded Erase  
algorithm. The device does not require the system to  
preprogram prior to erase. The Embedded Erase algo-  
rithm automatically preprograms and verifies the entire  
memory for an all zero data pattern prior to electrical  
erase. The system is not required to provide any con-  
trols or timings during these operations. Table 9 shows  
the address and data requirements for the chip erase  
command sequence.  
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  
Any commands written to the chip during the Embed-  
ded Erase algorithm are ignored. Note that a hardware  
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 integrity.  
20  
Am29LV116D  
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 array data and addresses are  
no longer latched. The system can determine the sta-  
tus of the erase operation by using DQ7, DQ6, DQ2, or  
RY/BY#. (Refer to “Write Operation Status” for informa-  
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.  
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.  
Sector Erase Command Sequence  
Erase Suspend/Erase Resume Commands  
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 erase command sequence.  
The Erase Suspend command allows the system to in-  
terrupt a sector erase operation and then read data  
from, or program data to, any sector not selected for  
erasure. This command is valid only during the sector  
erase operation, including the time-out period 50 µs  
during the sector erase command 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 erase operation. Ad-  
dresses are “don’t-cares” when writing the Erase Sus-  
pend command.  
The device does not require the system to preprogram  
the memory prior to erase. The Embedded Erase algo-  
rithm automatically programs and verifies the sector for  
an all zero data pattern prior to electrical erase. The  
system is not required to provide any controls or tim-  
ings during these operations.  
When the Erase Suspend command is written during a  
sector erase operation, the device 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 command sequence is written, a sector erase  
time-out of 50 µs begins. During the time-out period,  
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 sectors. The time be-  
tween these additional cycles 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 disabled 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.  
After the erase operation has been suspended, the  
system can read array data from or program data to  
any sector not selected for erasure. (The device “erase  
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 can once again read array data 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 can monitor DQ3 to determine if the sector  
erase timer has timed out. (See the “DQ3: Sector Erase  
Timer” section.) The time-out begins from the rising  
edge of the final WE# pulse in the command sequence.  
Once the sector erase operation has begun, only the  
Erase Suspend command is valid. All other commands  
are ignored. Note that 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.  
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  
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.  
START  
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 operation. Further  
writes of the Resume command are ignored. Another  
Erase Suspend command can be written after the de-  
vice has resumed erasing.  
Write Erase  
Command Sequence  
Data Poll  
from System  
Embedded  
Erase  
algorithm  
in progress  
No  
Data = FFh?  
Yes  
Erasure Completed  
Notes:  
1. See Table 9 for erase command sequence.  
2. See “DQ3: Sector Erase Timer” for more information.  
Figure 4. Erase Operation  
22  
Am29LV116D  
Command Definitions  
Table 9. Am29LV116D Command Definitions  
Bus Cycles (Notes 2–4)  
Command Sequence  
(Note 1)  
First  
Second  
Third  
Fourth  
Fifth  
Sixth  
Addr Data Addr Data Addr Data Addr Data Addr Data Addr Data  
Read (Note 5)  
Reset (Note 6)  
1
1
4
RA  
XXX  
555  
RD  
F0  
Manufacturer ID  
AA  
2AA  
2AA  
55  
55  
555  
555  
90  
90  
X00  
X01  
01  
Device ID,  
Top Boot Block  
C7  
4
555  
555  
AA  
Device ID,  
Bottom Boot Block  
4C  
00  
01  
Sector Protect  
Verify (Note 8)  
SA  
X02  
4
AA  
2AA  
55  
555  
90  
CFI Query (Note 9)  
1
4
3
55  
98  
AA  
AA  
Byte Program  
Unlock Bypass  
555  
555  
2AA  
2AA  
55  
55  
555  
555  
A0  
20  
PA  
PD  
Unlock Bypass Program  
(Note 10)  
2
2
XXX  
XXX  
A0  
90  
PA  
PD  
00  
Unlock Bypass Reset  
(Note 11)  
XXX  
Chip Erase  
6
6
1
1
555  
555  
AA  
AA  
B0  
30  
2AA  
2AA  
55  
55  
555  
555  
80  
80  
555  
555  
AA  
AA  
2AA  
2AA  
55  
55  
555  
SA  
10  
30  
Sector Erase  
Erase Suspend (Note 12)  
Erase Resume (Note 13)  
XXX  
XXX  
Legend:  
X = Don’t care  
PD = Data to be programmed at location PA. Data is latched  
on the rising edge of WE# or CE# pulse.  
RA = Address of the memory location to be read.  
SA = Address of the sector to be erased or verified. Address  
bits A20–A13 uniquely select any sector.  
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.  
8. The data is 00h for an unprotected sector and 01h for a  
protected sector.  
2. All values are in hexadecimal.  
9. Command is valid when device is ready to read array data  
or when device is in autoselect mode.  
3. Except when reading array or autoselect data, all bus  
cycles are write operations.  
10. The Unlock Bypass command is required prior to the  
Unlock Bypass Program command.  
4. Address bits A20–A11 are don’t care for unlock and  
command cycles, except when PA or SA is required.  
11. The Unlock Bypass Reset command is required to return  
to reading array data when the device is in the Unlock  
Bypass mode.  
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.  
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.  
7. The fourth cycle of the autoselect command sequence is  
a read cycle.  
13. The Erase Resume command is valid only during the  
Erase Suspend mode.  
Am29LV116D  
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 these 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.  
Table 10 shows the outputs for Data# Polling on DQ7.  
Figure 5 shows the Data# Polling algorithm.  
START  
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 device is in Erase Suspend.  
Data# Polling is valid after the rising edge of the final  
WE# pulse in the program or erase command se-  
quence.  
Read DQ7–DQ0  
Addr = VA  
Yes  
DQ7 = Data?  
During the Embedded Program algorithm, 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.  
No  
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,or  
“0.The system must provide an address within any of  
the sectors selected for erasure to read valid status in-  
formation on DQ7.  
Read DQ7–DQ0  
Addr = VA  
Yes  
DQ7 = Data?  
No  
PASS  
FAIL  
After an erase command sequence is written, if all sec-  
tors selected for erasing are protected, Data# Polling  
on DQ7 is active for approximately 100 µs, then 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.  
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.  
When the system detects DQ7 has changed from the  
complement to true data, it can read valid data at DQ7–  
DQ0 on the following read cycles. This is because DQ7  
may change asynchronously with DQ0–DQ6 while  
Output Enable (OE#) is asserted low. Figure 17, Data#  
Polling Timings (During Embedded Algorithms), in the  
“AC Characteristics” section illustrates this.  
Figure 5. Data# Polling Algorithm  
24  
Am29LV116D  
Table 10 shows the outputs for 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 diagrams.  
Figure 19 shows the differences between DQ2 and  
DQ6 in graphical form. See also the subsection on  
DQ2: Toggle Bit II.  
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 VCC. (The RY/BY# pin is not available  
on the 44-pin SO package.)  
DQ2: Toggle Bit II  
If the output is low (Busy), the device is actively erasing  
or programming. (This includes programming in the  
Erase Suspend mode.) If the output is high (Ready),  
the device is ready to read array data (including during  
the Erase Suspend mode), or is in the standby mode.  
The “Toggle Bit II” on DQ2, when used with DQ6, indi-  
cates whether a particular sector is actively erasing  
(that is, the Embedded Erase algorithm is in progress),  
or whether that sector is erase-suspended. Toggle Bit  
II is valid after the rising edge of the final WE# pulse in  
the command sequence.  
Table 10 shows the outputs for RY/BY#. Figures 13, 15  
and 16 shows RY/BY# for reset, program, and erase  
operations, respectively.  
DQ2 toggles when the system reads at addresses  
within those sectors 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.  
DQ6: Toggle Bit I  
Toggle Bit I on DQ6 indicates whether an Embedded  
Program or Erase algorithm is in progress or complete,  
or whether the device has entered the Erase Suspend  
mode. Toggle Bit I may be read at any address, and is  
valid after the rising edge of the final WE# pulse in the  
command sequence (prior to the program or erase op-  
eration), and during the sector erase time-out.  
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# or CE#  
to control the read cycles). When the operation is com-  
plete, DQ6 stops toggling.  
Figure 6 shows the toggle bit algorithm in flowchart  
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.  
After an erase command sequence is written, if all sec-  
tors selected for erasing are protected, DQ6 toggles for  
approximately 100 µs, then returns to reading array  
data. If not all selected sectors are protected, the Em-  
bedded Erase algorithm erases the unprotected sec-  
tors, and ignores the selected sectors that are  
protected.  
Reading Toggle Bits DQ6/DQ2  
Refer to Figure 6 for the following discussion. When-  
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 toggle bit  
after the first read. After the second read, the system  
would compare the new value of the toggle bit with the  
first. If the toggle bit is not toggling, the device has com-  
pleted the program or erase operation. The system can  
read array data on DQ7–DQ0 on the following read cy-  
cle.  
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 actively erasing (that is,  
the Embedded Erase algorithm is in progress), DQ6  
toggles. When the device enters the Erase Suspend  
mode, DQ6 stops toggling. However, the system must  
also use DQ2 to determine which sectors are erasing  
or erase-suspended. Alternatively, the system can use  
DQ7 (see the subsection on DQ7: Data# Polling).  
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  
If a program address falls within a protected sector,  
DQ6 toggles for approximately 1 µs after the program  
command sequence is written, then returns to reading  
array data.  
DQ6 also toggles during the erase-suspend-program  
mode, and stops toggling once the Embedded Pro-  
gram algorithm is complete.  
Am29LV116D  
25  
must write the reset command to return to reading  
array data.  
START  
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 successive read cycles, de-  
termining the status as described in the previous para-  
graph. Alternatively, 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).  
Read DQ7–DQ0  
(Note 1)  
Read DQ7–DQ0  
Table 10 shows the outputs for Toggle Bit I on DQ6. Fig-  
ure 6 shows the toggle bit algorithm. Figure 18 in the  
“AC Characteristics” section shows 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.  
No  
Toggle Bit  
= Toggle?  
Yes  
DQ5: Exceeded Timing Limits  
No  
DQ5 = 1?  
Yes  
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 program or erase cycle was  
not successfully completed.  
(Notes  
1, 2)  
Read DQ7–DQ0  
Twice  
The DQ5 failure condition may appear if the system  
tries to program a “1” to a location that is previously pro-  
grammed to “0.Only an erase 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.”  
Toggle Bit  
= Toggle?  
No  
Under both these conditions, the system must issue the  
reset command to return the device to reading array  
data.  
Yes  
Program/Erase  
Operation Not  
Complete, Write  
Reset Command  
Program/Erase  
Operation Complete  
DQ3: Sector Erase Timer  
After writing a sector erase command 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 complete, 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.  
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.  
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 check the status  
of DQ3 prior to and following each subsequent sector  
erase command. If DQ3 is high on the second status  
check, the last command might not have been ac-  
cepted. Table 10 shows the outputs for DQ3.  
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 Suspend)  
26  
Am29LV116D  
Table 10. Write Operation Status  
DQ7  
DQ5  
DQ2  
Operation  
(Note 2)  
DQ6  
(Note 1)  
DQ3  
N/A  
1
(Note 2)  
RY/BY#  
Embedded Program Algorithm  
Embedded Erase Algorithm  
DQ7#  
0
Toggle  
Toggle  
0
0
No toggle  
Toggle  
0
0
Standard  
Mode  
Reading within Erase  
Suspended Sector  
1
No toggle  
0
N/A  
Toggle  
1
Erase  
Suspend Reading within Non-Erase  
Data  
Data  
Data  
0
Data  
N/A  
Data  
N/A  
1
0
Mode  
Suspended Sector  
Erase-Suspend-Program  
DQ7#  
Toggle  
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.  
Am29LV116D  
27  
ABSOLUTE MAXIMUM RATINGS  
Storage Temperature  
Plastic Packages . . . . . . . . . . . . . . . –65°C to +150°C  
20 ns  
20 ns  
Ambient Temperature  
with Power Applied. . . . . . . . . . . . . . –65°C to +125°C  
+0.8 V  
Voltage with Respect to Ground  
–0.5 V  
–2.0 V  
VCC (Note 1) . . . . . . . . . . . . . . . . .0.5 V to +4.0 V  
A9, OE#, and  
RESET# (Note 2) . . . . . . . . . . . .–0.5 V to +12.5 V  
20 ns  
All other pins (Note 1) . . . . . . –0.5 V to VCC+0.5 V  
Output Short Circuit Current (Note 3) . . . . . . 200 mA  
Figure 7. Maximum Negative  
Overshoot Waveform  
Notes:  
1. Minimum DC voltage on input or I/O pins is –0.5 V. During  
voltage transitions, input or I/O pins may overshoot V to  
SS  
–2.0 V for periods of up to 20 ns. See Figure 7. Maximum  
DC voltage on input or I/O pins is VCC +0.5 V. During  
20 ns  
voltage transitions, input or I/O pins may overshoot to V  
+2.0 V for periods up to 20 ns. See Figure 8.  
V
CC  
CC  
+2.0 V  
V
2. Minimum DC input voltage on pins A9, OE#, and RESET#  
is –0.5 V. During voltage transitions, A9, OE#, and  
CC  
+0.5 V  
RESET# may overshoot V to –2.0 V for periods of up to  
SS  
2.0 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.  
20 ns  
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.  
Figure 8. Maximum Positive  
Overshoot Waveform  
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.  
OPERATING RANGES  
Commercial (C) Devices  
Ambient Temperature (TA) . . . . . . . . . . . 0°C to +70°C  
Industrial (I) Devices  
Ambient Temperature (TA) . . . . . . . . . –40°C to +85°C  
VCC Supply Voltages  
VCC for all devices . . . . . . . . . . . . . . . .+2.7 V to 3.6 V  
Operating ranges define those limits between which the  
functionality of the device is guaranteed.  
28  
Am29LV116D  
DC CHARACTERISTICS  
CMOS Compatible  
Parameter  
Description  
Test Conditions  
= V to V  
Min  
Typ  
Max  
1.0  
35  
Unit  
µA  
V
V
,
CC  
IN  
SS  
I
Input Load Current  
LI  
= V  
CC  
CC max  
I
A9 Input Load Current  
Output Leakage Current  
V
= V  
; A9 = 12.5 V  
µA  
LIT  
CC  
CC max  
V
V
= V to V  
,
CC  
OUT  
SS  
I
1.0  
µA  
LO  
= V  
CC  
CC max  
5 MHz  
1 MHz  
9
2
16  
4
V
Active Read Current  
CC  
I
I
CE# = V OE#  
V
V
mA  
mA  
CC1  
CC2  
IL,  
=
=
IH  
(Notes 1, 2)  
V
Active Write Current  
CC  
CE# = V OE#  
15  
30  
IL,  
IH  
(Notes 2, 3, 4)  
I
I
V
V
Standby Current (Note 2)  
Reset Current (Note 2)  
CE#, RESET# = V  
0.3 V  
0.2  
0.2  
5
5
µA  
µA  
CC3  
CC  
CC  
CC  
RESET# = V  
0.3 V  
CC4  
SS  
Automatic Sleep Mode  
(Notes 2, 5)  
V
V
= V  
= V  
0.3 V;  
0.3 V  
IH  
IL  
CC  
SS  
I
0.2  
5
µA  
CC5  
V
Input Low Voltage  
Input High Voltage  
–0.5  
0.8  
V
V
IL  
V
0.7 x V  
V
+ 0.3  
IH  
CC  
CC  
Voltage for Autoselect and  
Temporary Sector Unprotect  
V
V
= 3.3 V  
11.5  
12.5  
0.45  
V
ID  
CC  
V
Output Low Voltage  
I
I
I
= 4.0 mA, V = V  
CC min  
V
V
OL  
OL  
OH  
OH  
CC  
V
= –2.0 mA, V = V  
CC min  
0.85 V  
OH1  
OH2  
CC  
CC  
Output High Voltage  
V
= –100 µA, V = V  
V
–0.4  
CC  
CC min  
CC  
Low V Lock-Out Voltage  
(Note 4)  
CC  
V
2.3  
2.5  
V
LKO  
Notes:  
1. The I current listed is typically less than 2 mA/MHz, with OE# at V . Typical specifications are for V = 3.0 V.  
CC  
IH  
CC  
2. Maximum I specifications are tested with V = V max.  
CC  
CC  
CC  
3. I active while Embedded Erase or Embedded Program is in progress.  
CC  
4. Not 100% tested.  
5. Automatic sleep mode enables the low power mode when addresses remain stable for t  
+ 30 ns.  
ACC  
Am29LV116D  
29  
DC CHARACTERISTICS (Continued)  
Zero Power Flash  
25  
20  
15  
10  
5
0
0
500  
1000  
1500  
2000  
2500  
3000  
3500  
4000  
Time in ns  
Note: Addresses are switching at 1 MHz  
Figure 9. ICC1 Current vs. Time (Showing Active and Automatic Sleep Currents)  
10  
8
3.6 V  
2.7 V  
6
4
2
0
1
2
3
4
5
Frequency in MHz  
Note: T = 25 °C  
Figure 10. Typical ICC1 vs. Frequency  
30  
Am29LV116D  
TEST CONDITIONS  
Table 11. Test Specifications  
3.3 V  
Test Condition  
-70  
-90, -120 Unit  
Output Load  
1 TTL gate  
100  
2.7 kΩ  
Device  
Under  
Test  
Output Load Capacitance, C  
(including jig capacitance)  
L
30  
pF  
C
L
Input Rise and Fall Times  
Input Pulse Levels  
5
ns  
V
6.2 kΩ  
0.0–3.0  
Input timing measurement  
reference levels  
1.5  
1.5  
V
V
Output timing measurement  
reference levels  
Note: Diodes are IN3064 or equivalent  
Figure 11. Test Setup  
Key to Switching Waveforms  
WAVEFORM  
INPUTS  
OUTPUTS  
Steady  
Changing from H to L  
Changing from L to H  
Don’t Care, Any Change Permitted  
Does Not Apply  
Changing, State Unknown  
Center Line is High Impedance State (High Z)  
3.0 V  
0.0 V  
1.5 V  
1.5 V  
Input  
Measurement Level  
Output  
Figure 12. Input Waveforms and Measurement Levels  
Am29LV116D  
31  
AC CHARACTERISTICS  
Read Operations  
Parameter  
Speed Option  
JEDEC  
Std  
Description  
Test Setup  
-70  
-90  
-120 Unit  
t
t
Read Cycle Time (Note 1)  
Min  
70  
70  
90  
120  
120  
ns  
ns  
AVAV  
RC  
CE# = V  
OE# = V  
IL  
IL  
t
t
Address to Output Delay  
Max  
90  
AVQV  
ACC  
t
t
t
Chip Enable to Output Delay  
OE# = V  
Max  
Max  
Max  
Max  
Min  
70  
30  
25  
25  
90  
35  
30  
30  
0
120  
50  
ns  
ns  
ns  
ns  
ns  
ELQV  
GLQV  
EHQZ  
GHQZ  
CE  
IL  
t
t
Output Enable to Output Delay  
OE  
t
Chip Enable to Output High Z (Note 1)  
Output Enable to Output High Z (Note 1)  
30  
DF  
DF  
t
t
30  
Read  
Output Enable  
Hold Time (Note 1)  
t
OEH  
Toggle and  
Data# Polling  
Min  
Min  
10  
0
ns  
ns  
Output Hold Time From Addresses, CE# or  
OE#, Whichever Occurs First (Note 1)  
t
t
OH  
AXQX  
Notes:  
1. Not 100% tested.  
2. See Figure 11 and Table 11 for test specifications.  
tRC  
Addresses Stable  
tACC  
Addresses  
CE#  
tDF  
tOE  
OE#  
tOEH  
WE#  
tCE  
tOH  
HIGH Z  
HIGH Z  
Output Valid  
Outputs  
RESET#  
RY/BY#  
0 V  
Figure 13. Read Operations Timings  
32  
Am29LV116D  
AC CHARACTERISTICS  
Hardware Reset (RESET#)  
Parameter  
JEDEC  
Std  
Description  
Test Setup  
Max  
All Speed Options  
Unit  
RESET# Pin Low (During Embedded Algorithms)  
to Read or Write (See Note)  
t
t
20  
µs  
READY  
RESET# Pin Low (NOT During Embedded  
Algorithms) to Read or Write (See Note)  
Max  
500  
ns  
READY  
t
t
RESET# Pulse Width  
Min  
Min  
Min  
Min  
500  
50  
20  
0
ns  
ns  
µs  
ns  
RP  
RESET# High Time Before Read (See Note)  
RESET# Low to Standby Mode  
RY/BY# Recovery Time  
RH  
t
RPD  
t
RB  
Note: Not 100% tested.  
RY/BY#  
CE#, OE#  
RESET#  
tRH  
tRP  
tReady  
Reset Timings NOT during Embedded Algorithms  
Reset Timings during Embedded Algorithms  
tReady  
RY/BY#  
tRB  
CE#, OE#  
RESET#  
tRP  
Figure 14. RESET# Timings  
Am29LV116D  
33  
AC CHARACTERISTICS  
Erase/Program Operations  
Parameter  
Speed Options  
JEDEC  
Std  
Description  
-70  
-90  
90  
0
-120  
Unit  
ns  
t
t
Write Cycle Time (Note 1)  
Address Setup Time  
Address Hold Time  
Data Setup Time  
Min  
Min  
Min  
Min  
Min  
Min  
70  
120  
AVAV  
WC  
t
t
ns  
AVWL  
WLAX  
DVWH  
WHDX  
AS  
AH  
DS  
DH  
t
t
45  
35  
45  
45  
0
50  
50  
ns  
t
t
ns  
t
t
t
t
Data Hold Time  
ns  
t
Output Enable Setup Time (Note 1)  
0
ns  
OES  
Read Recovery Time Before Write  
(OE# High to WE# Low)  
t
Min  
0
ns  
GHWL  
GHWL  
t
t
CE# Setup Time  
Min  
Min  
Min  
Min  
Typ  
Typ  
Min  
Min  
Min  
0
0
ns  
ns  
ns  
ns  
µs  
sec  
µs  
ns  
ns  
ELWL  
WHEH  
WLWH  
WHWL  
CS  
CH  
WP  
t
CE# Hold Time  
t
t
Write Pulse Width  
35  
35  
30  
9
50  
t
t
Write Pulse Width High  
Programming Operation (Note 2)  
Sector Erase Operation (Note 2)  
WPH  
t
t
t
t
WHWH1  
WHWH2  
WHWH1  
WHWH2  
0.7  
50  
0
t
V
Setup Time (Note 1)  
VCS  
CC  
t
Recovery Time from RY/BY#  
RB  
t
Program/Erase Valid to RY/BY# Delay  
90  
BUSY  
Notes:  
1. Not 100% tested.  
2. See the “Erase and Programming Performance” section for more information.  
34  
Am29LV116D  
AC CHARACTERISTICS  
Program Command Sequence (last two cycles)  
Read Status Data (last two cycles)  
tAS  
tWC  
Addresses  
555h  
PA  
PA  
PA  
tAH  
CE#  
OE#  
tCH  
tWHWH1  
tWP  
WE#  
Data  
tWPH  
tCS  
tDS  
tDH  
PD  
DOUT  
A0h  
Status  
tBUSY  
tRB  
RY/BY#  
VCC  
tVCS  
Note: PA = program address, PD = program data, D  
is the true data at the program address.  
OUT  
Figure 15. Program Operation Timings  
Erase Command Sequence (last two cycles)  
Read Status Data  
tAS  
SA  
tWC  
VA  
VA  
Addresses  
CE#  
2AAh  
555h for chip erase  
tAH  
tCH  
OE#  
tWP  
WE#  
tWPH  
tWHWH2  
tCS  
tDS  
tDH  
In  
Data  
Complete  
55h  
30h  
Progress  
10 for Chip Erase  
tBUSY  
tRB  
RY/BY#  
VCC  
tVCS  
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  
35  
AC CHARACTERISTICS  
tRC  
VA  
Addresses  
VA  
VA  
tACC  
tCE  
CE#  
tCH  
tOE  
OE#  
tOEH  
WE#  
tDF  
tOH  
High Z  
High Z  
DQ7  
Valid Data  
Complement  
Complement  
True  
DQ0–DQ6  
Status Data  
True  
Valid Data  
Status Data  
tBUSY  
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)  
tRC  
Addresses  
CE#  
VA  
tACC  
tCE  
VA  
VA  
VA  
tCH  
tOE  
OE#  
WE#  
tOEH  
tDF  
tOH  
High Z  
DQ6/DQ2  
RY/BY#  
Valid Status  
(first read)  
Valid Status  
Valid Status  
Valid Data  
(second read)  
(stops toggling)  
tBUSY  
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)  
36  
Am29LV116D  
AC CHARACTERISTICS  
Enter  
Embedded  
Erasing  
Erase  
Suspend  
Enter Erase  
Suspend Program  
Erase  
Resume  
Erase  
Erase Suspend  
Read  
Erase  
Suspend  
Program  
Erase  
Complete  
WE#  
Erase  
Erase Suspend  
Read  
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.  
Figure 19. DQ2 vs. DQ6  
Temporary Sector Unprotect  
Parameter  
JEDEC  
Std  
Description  
Rise and Fall Time (See Note)  
All Speed Options  
Unit  
t
V
Min  
Min  
500  
ns  
VIDR  
ID  
RESET# Setup Time for Temporary Sector  
Unprotect  
t
4
µs  
RSP  
Note: Not 100% tested.  
12 V  
RESET#  
0 or 3 V  
tVIDR  
tVIDR  
Program or Erase Command Sequence  
CE#  
WE#  
tRSP  
RY/BY#  
Figure 20. Temporary Sector Unprotect Timing Diagram  
Am29LV116D  
37  
AC CHARACTERISTICS  
VID  
VIH  
RESET#  
SA, A6,  
A1, A0  
Valid*  
Sector Protect/Unprotect  
60h 60h  
Valid*  
Valid*  
Status  
Verify  
40h  
Data  
Sector Protect: 150 µs  
Sector Unprotect: 15 ms  
1 µs  
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  
38  
Am29LV116D  
AC CHARACTERISTICS  
Alternate CE# Controlled Erase/Program Operations  
Parameter  
Speed Options  
JEDEC  
Std  
Description  
-70  
-90  
90  
0
-120  
Unit  
ns  
t
t
Write Cycle Time (Note 1)  
Address Setup Time  
Address Hold Time  
Data Setup Time  
Min  
Min  
Min  
Min  
Min  
Min  
70  
120  
AVAV  
AVEL  
ELAX  
DVEH  
EHDX  
WC  
t
t
ns  
AS  
AH  
DS  
DH  
t
t
45  
35  
45  
45  
0
50  
50  
ns  
t
t
t
ns  
t
Data Hold Time  
ns  
t
Output Enable Setup Time  
0
ns  
OES  
Read Recovery Time Before Write  
(OE# High to WE# Low)  
t
t
t
Min  
0
ns  
GHEL  
WLEL  
GHEL  
t
t
WE# Setup Time  
Min  
Min  
Min  
Min  
Typ  
Typ  
0
0
ns  
ns  
WS  
t
WE# Hold Time  
EHWH  
WH  
t
t
CE# Pulse Width  
35  
35  
30  
9
50  
ns  
ELEH  
EHEL  
CP  
t
t
CE# Pulse Width High  
Programming Operation (Note 2)  
Sector Erase Operation (Note 2)  
ns  
CPH  
t
t
t
t
µs  
WHWH1  
WHWH2  
WHWH1  
WHWH2  
0.7  
sec  
Notes:  
1. Not 100% tested.  
2. See the “Erase and Programming Performance” section for more information.  
Am29LV116D  
39  
AC CHARACTERISTICS  
555 for program  
PA for program  
2AA for erase  
SA for sector erase  
555 for chip erase  
Data# Polling  
Addresses  
PA  
tWC  
tWH  
tAS  
tAH  
WE#  
OE#  
tGHEL  
tWHWH1 or 2  
tCP  
CE#  
Data  
tWS  
tCPH  
tDS  
tBUSY  
tDH  
DQ7#  
DOUT  
tRH  
A0 for program  
55 for erase  
PD for program  
30 for sector erase  
10 for chip erase  
RESET#  
RY/BY#  
Note: PA = program address, PD = program data, DQ7# = complement of the data written to the device, D  
= data written to  
OUT  
the device. Figure indicates the last two bus cycles of the command sequence.  
Figure 22. Alternate CE# Controlled Write Operation Timings  
40  
Am29LV116D  
ERASE AND PROGRAMMING PERFORMANCE  
Parameter  
Typ (Note 1)  
Max (Note 2)  
Unit  
s
Comments  
Sector Erase Time  
0.7  
25  
9
15  
Excludes 00h programming  
prior to erasure (Note 4)  
Chip Erase Time  
s
Byte Programming Time  
Chip Programming Time (Note 3)  
300  
54  
µs  
s
Excludes system level  
overhead (Note 5)  
18  
Notes:  
1. Typical program and erase times assume the following conditions: 25°C, 3.0 V V , 1,000,000 cycles. Additionally,  
CC  
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 on all pins except I/O pins  
(including A9, OE#, and RESET#)  
SS  
–1.0 V  
12.5 V  
Input voltage with respect to V on all I/O pins  
–1.0 V  
V
+ 1.0 V  
CC  
SS  
V
Current  
–100 mA  
+100 mA  
CC  
Includes all pins except V . Test conditions: V = 3.0 V, one pin at a time.  
CC  
CC  
TSOP PIN CAPACITANCE  
Parameter  
Symbol  
Parameter Description  
Input Capacitance  
Test Setup  
Typ  
6
Max  
7.5  
12  
Unit  
pF  
C
V
= 0  
IN  
IN  
C
Output Capacitance  
Control Pin Capacitance  
V
= 0  
8.5  
7.5  
pF  
OUT  
OUT  
C
V
= 0  
IN  
9
pF  
IN2  
Notes:  
1. Sampled, not 100% tested.  
2. Test conditions T = 25°C, f = 1.0 MHz.  
A
DATA RETENTION  
Parameter  
Test Conditions  
150°C  
Min  
10  
Unit  
Years  
Years  
Minimum Pattern Data Retention Time  
125°C  
20  
Am29LV116D  
41  
PHYSICAL DIMENSIONS*  
TS 040—40-Pin Standard TSOP  
Dwg rev AA; 10/99  
* For reference only. BSC is an ANSI standard for Basic Space Centering.  
42  
Am29LV116D  
PHYSICAL DIMENSIONS  
TSR040—40-Pin Reverse TSOP  
Dwg rev AA; 10/99  
* For reference only. BSC is an ANSI standard for Basic Space Centering.  
Am29LV116D  
43  
REVISION SUMMARY  
Distinctive Characteristics  
Revision A (October 1997)  
Changed process technology to 0.32 µm.  
First release.  
Table 9, Command Definitions  
Revision B (October 1997)  
Global  
The CFI Query command is now included in the table.  
DC Characteristics  
Deleted SO package from data sheet.  
Moved VCCmax test condition for ICC specifications to  
notes.  
Revision C (December 1997)  
Alternate CE# Controlled Erase/Program  
Operations  
Figure 21, Sector Protect/Unprotect Timing  
Diagram  
Changed tCP from 45 to 35 ns on 80R and 90 speed  
options.  
Changed timing specifications in diagram to match  
those in the figure of In-System Sector Protect/Unpro-  
tect Algorithms.  
Revision C+1 (January 1998)  
Global  
Revision D (January 1999)  
Distinctive Characteristics  
Changed data sheet status to Preliminary.  
Added “20-year data retention at 125°C” bullet.  
Reset Command  
Deleted the last paragraph in this section.  
Revision E (February 2, 2000)  
Global  
Revision C+2 (March 1998)  
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 available 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.  
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 another sec-  
tor?” back to setting up the next sector address.  
AC Characteristics  
Erase/Program Operations; Alternate CE# Controlled  
Erase/Program Operations: Corrected the notes refer-  
ence for tWHWH1 and tWHWH2. These parameters are  
100% tested. Corrected the note reference for tVCS  
This parameter is not 100% tested.  
AC Characteristics—Figure 15. Program  
Operations Timing and Figure 16. Chip/Sector  
Erase Operations  
.
Deleted tGHWL and changed OE# waveform to start at  
high.  
Temporary Sector Unprotect Table  
Added note reference for tVIDR. This parameter is not  
100% tested.  
Physical Dimensions  
Replaced figures with more detailed illustrations.  
Figure 21, Sector Protect/Unprotect Timing  
Diagram  
Revision E+1 (November 7, 2000)  
Global  
A valid address is not required for the first write cycle;  
only the data 60h.  
Added table of contents. Deleted burn-in option in or-  
dering information section.  
Erase and Programming Performance  
In Note 2, the worst case endurance is now 1 million  
cycles.  
Revision E+2 (May 27, 2004)  
Revision C+3 (August 1998)  
Ordering Information  
Global  
Added Lead-free (Pb-free) options to the Temperature  
Range breakout of the OPN table and the Valid Combi-  
nations table.  
Added 70R speed option, changed 80R speed option  
to 80.  
44  
Am29LV116D  
Trademarks  
Copyright © 2004 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  
45  

相关型号:

SI9130DB

5- and 3.3-V Step-Down Synchronous Converters

Warning: Undefined variable $rtag in /www/wwwroot/website_ic37/www.icpdf.com/pdf/pdf/index.php on line 217
-
VISHAY

SI9135LG-T1

SMBus Multi-Output Power-Supply Controller

Warning: Undefined variable $rtag in /www/wwwroot/website_ic37/www.icpdf.com/pdf/pdf/index.php on line 217
-
VISHAY

SI9135LG-T1-E3

SMBus Multi-Output Power-Supply Controller

Warning: Undefined variable $rtag in /www/wwwroot/website_ic37/www.icpdf.com/pdf/pdf/index.php on line 217
-
VISHAY

SI9135_11

SMBus Multi-Output Power-Supply Controller

Warning: Undefined variable $rtag in /www/wwwroot/website_ic37/www.icpdf.com/pdf/pdf/index.php on line 217
-
VISHAY

SI9136_11

Multi-Output Power-Supply Controller

Warning: Undefined variable $rtag in /www/wwwroot/website_ic37/www.icpdf.com/pdf/pdf/index.php on line 217
-
VISHAY

SI9130CG-T1-E3

Pin-Programmable Dual Controller - Portable PCs

Warning: Undefined variable $rtag in /www/wwwroot/website_ic37/www.icpdf.com/pdf/pdf/index.php on line 217
-
VISHAY

SI9130LG-T1-E3

Pin-Programmable Dual Controller - Portable PCs

Warning: Undefined variable $rtag in /www/wwwroot/website_ic37/www.icpdf.com/pdf/pdf/index.php on line 217
-
VISHAY

SI9130_11

Pin-Programmable Dual Controller - Portable PCs

Warning: Undefined variable $rtag in /www/wwwroot/website_ic37/www.icpdf.com/pdf/pdf/index.php on line 217
-
VISHAY

SI9137

Multi-Output, Sequence Selectable Power-Supply Controller for Mobile Applications

Warning: Undefined variable $rtag in /www/wwwroot/website_ic37/www.icpdf.com/pdf/pdf/index.php on line 217
-
VISHAY

SI9137DB

Multi-Output, Sequence Selectable Power-Supply Controller for Mobile Applications

Warning: Undefined variable $rtag in /www/wwwroot/website_ic37/www.icpdf.com/pdf/pdf/index.php on line 217
-
VISHAY

SI9137LG

Multi-Output, Sequence Selectable Power-Supply Controller for Mobile Applications

Warning: Undefined variable $rtag in /www/wwwroot/website_ic37/www.icpdf.com/pdf/pdf/index.php on line 217
-
VISHAY

SI9122E

500-kHz Half-Bridge DC/DC Controller with Integrated Secondary Synchronous Rectification Drivers

Warning: Undefined variable $rtag in /www/wwwroot/website_ic37/www.icpdf.com/pdf/pdf/index.php on line 217
-
VISHAY