SST49LF008A: 15 seconds (typical)
– Single-pulse Program or Erase
– Internal timing generation
• Two Operational Modes
– Firmware Hub Interface (FWH) Mode for
in-system operation
– Parallel Programming (PP) Mode for fast
production programming
• Firmware Hub Hardware Interface Mode
– 5-signal communication interface supporting
byte Read and Write
– 33 MHz clock frequency operation
– WP# and TBL# pins provide hardware write
protect for entire chip and/or top Boot Block
– Block Locking Register for all blocks
– Standard SDP Command Set
– Data# Polling and Toggle Bit for End-of-Write
detection
– 5 GPI pins for system design flexibility
– 4 ID pins for multi-chip selection
• Parallel Programming (PP) Mode
– 11-pin multiplexed address and
8-pin data I/O interface
– Supports fast In-System or PROM programming
for manufacturing
• CMOS and PCI I/O Compatibility
• Packages Available
– 32-lead PLCC
– 32-lead TSOP (8mm x 14mm)
PRODUCT DESCRIPTION
The SST49LF00xA flash memory devices are designed
to be read-compatible with the Intel 82802 Firmware Hub
(FWH) device for PC-BIOS application. It provides protection for the storage and update of code and data in
addition to adding system design flexibility through five
general purpose inputs. Two interface modes are supported by the SST49LF00xA: Firmware Hub (FWH)
Interface Mode for In-System programming and Parallel
Programming (PP) Mode for fast factory programming of
PC-BIOS applications.
The SST49LF00xA flash memory devices are manufactured with SST’s proprietary, high performance SuperFlash Technology. The split-gate cell design and thick
oxide tunneling injector attain better reliability and manufacturability compared with alternate approaches. The
SST49LF00xA devices significantly improve performance
and reliability, while lowering power consumption. The
SST49LF00xA devices write (Program or Erase) with a
single 3.0-3.6V power supply. It uses less energy during
Erase and Program than alternative flash memory technologies. The total energy consumed is a function of the
applied voltage, current and time of application. Since for
The SST logo and SuperFlash are registered trademarks of Silicon Storage Technology, Inc.
Intel is a registered trademark of Intel Corporation.
These specifications are subject to change without notice.
any given voltage range, the SuperFlash technology uses
less current to program and has a shorter Erase time, the
total energy consumed during any Erase or Program operation is less than alternative flash memory technologies.
The SST49LF00xA products provide a maximum ByteProgram time of 20 µsec. The entire memory can be
erased and programmed byte-by-byte typically in 15 seconds for an 8-Mbit device, when using status detection
features such as Toggle Bit or Data# Polling to indicate the
completion of Program operation. The SuperFlash technology provides fixed Erase and Program time, independent of the number of Erase/Program cycles that have
performed. Therefore the system software or hardware
does not have to be calibrated or correlated to the cumulated number of Erase/Program cycles as is necessary
with alternative flash memory technologies, whose Erase
and Program time increase with accumulated Erase/Program cycles.
To protect against inadvertent write, the SST49LF00xA
devices employ hardware and software data (SDP) protection schemes. It is offered with typical endurance of
100,000 cycles. Data retention is rated at greater than 100
years.
To meet high density, surface mount requirements, the
SST49LF00xA device is offered in 32-lead TSOP and 32lead PLCC packages. See Figures 7 and 8 for pin assignments and Table 8 for pin descriptions.
Mode Selection and Description
The SST49LF00xA flash memory devices can operate in
two distinct interface modes: the Firmware Hub Interface
(FWH) mode and the Parallel Programming (PP) mode.
The IC (Interface Configuration pin) is used to set the
interface mode selection. If the IC pin is set to logic High,
the device is in PP mode; while if the IC pin is set Low,
the device is in the FWH mode. The IC selection pin must
be configured prior to device operation. The IC pin is
internally pulled down if the pin is not connected. In FWH
mode, the device is configured to interface with its host
using Intel’s Firmware Hub proprietary protocol. Commu-
nication between Host and the SST49LF00xA occurs via
the 4-bit I/O communication signals, FWH [3:0] and the
FWH4. In PP mode, the device is programmed via an 11bit address and an 8-bit data I/O parallel signals. The
address inputs are multiplexed in row and column
selected by control signal R/C# pin. The column
addresses are mapped to the higher internal addresses,
and the row addresses are mapped to the lower internal
addresses. See the Device Memory Maps in Figures 3
through 6 for address assignments.
FIRMWARE HUB (FWH) MODE
Device Operation
The FWH mode uses a 5-signal communication interface,
FWH[3:0] and FWH4, to control operations of the
SST49LF00xA. Operations such as Memory Read and
Memory Write uses Intel FWH propriety protocol. JEDEC
Standard SDP (Software Data Protection) Byte-Program,
Sector-Erase and Block-Erase command sequences are
incorporated into the FWH memory cycles. Chip-Erase is
only available in PP Mode.
The device enters standby mode when FWH4 is high and
no internal operation is in progress. The device is in ready
mode when FWH4 is low and no activity is on the FWH bus.
Firmware Hub Interface Cycles
Addresses and data are transferred to and from the
SST49LF00xA by a series of “fields,” where each field contains 4 bits of data. ST49LF00xA supports only single-byte
read and writes, and all fields are one clock cycle in length.
Field sequences and contents are strictly defined for Read
and Write operations. Addresses in this section refer to
addresses as seen from the SST49LF00xA’s “point of
view,” some calculation will be required to translate these to
the actual locations in the memory map (and vice versa) if
multiple memory device is used on the bus. Tables 1 and 2
list the field sequences for Read and Write cycles.
If FWH4 is driven low for one or more clock cycles during a
FWH cycle, the cycle will be terminated and the device will
wait for the ABORT command. The host may drive the
FWH[3:0] with ‘1111b’ (ABORT command) to return the
device to Ready mode. If abort occurs during a Write operation, the data may be incorrectly altered.
Response To Invalid Fields
During FWH operations, the FWH will not explicitly indicate
that it has received invalid field sequences. The response
to specific invalid fields or sequences is as follows:
Address out of range: The FWH address sequence is
7 fields long (28 bits), but only the last five address fields
(20 bits) will be decoded by SST49LF00xA.
Address A
writes to the flash core (A
=0).
(A
22
has the special function of directing reads and
22
=1) or to the register space
22
The SST49LF003A features are equivalent to the
SST49LF004A with 128 KByte less memory. For the
SST49LF003A, operations beyond the 3-Mbit boundary
(below 20000H) are not valid (see Device Memory Map).
Invalid IMSIZE field: If the FWH receives an invalid size
field during a Read or Write operation, the device will reset
and no operation will be attempted. The SST49LF00xA will
not generate any kind of response in this situation. Invalidsize fields for a Read/Write cycle are anything but 0000b.
Device Memory Hardware Write Protection
The Top Boot Lock (TBL#) and Write Protect (WP#) pins
are provided for hardware write protection of device
memory in the SST49LF00xA. The TBL# pin is used to
write protect 16 boot sectors (64 KByte) at the highest
flash memory address range for the SST49LF003A/
004A/008A and 4 boot sectors (16 KByte) for
SST49LF002A. WP# pin write protects the remaining
sectors in the flash memory.
WP# pin during a Program or Erase operation could
cause unpredictable results. TBL# and WP# pins cannot
be left unconnected.
TBL# is internally ORed with the top Boot Block Locking
register. When TBL# is low, the top Boot Block is hardware write protected regardless of the state of the WriteLock bit for the Boot Block Locking register. Clearing the
Write-Protect bit in the register when TBL# is low will have
no functional effect, even though the register may indicate
that the block is no longer locked.
WP# is internally ORed with the Block Locking register.
When WP# is low, the blocks are hardware write protected regardless of the state of the Write-Lock bit for the
corresponding Block Locking registers. Clearing the
Write-Protect bit in any register when WP# is low will have
no functional effect, even though the register may indicate
that the block is no longer locked.
Reset
A VIL on INIT# or RST# pin initiates a device reset. INIT#
and RST# pins have the same function internally. It is
required to drive INIT# or RST# pins low during a system
reset to ensure proper CPU initialization.
During a Read operation, driving INIT# or RST# pins low
deselects the device and places the output drivers,
FWH[3:0], in a high-impedance state. The reset signal
must be held low for a minimal duration of time T
reset latency will occur if a reset procedure is performed
during a Program or Erase operation. See Table 18, Reset
Timing Parameters for more information. A device reset
during an active Program or Erase will abort the operation
and memory contents may become invalid due to data
being altered or corrupted from an incomplete Erase or
Program operation.
RSTP.
A
An active low signal at the TBL# pin prevents Program and
Erase operations of the top boot sectors. When TBL# pin is
held high, write protection of the top boot sectors is then
determined by the Boot Block Locking register. The WP#
pin serves the same function for the remaining sectors of
the device memory. The TBL# and WP# pins write protection functions operate independently of one another.
Both TBL# and WP# pins must be set to their required
protection states prior to starting a Program or Erase
operation. A logic level change occurring at the TBL# or
The SST49LF00xA device provides two software means to
detect the completion of a Write (Program or Erase) cycle,
in order to optimize the system Write cycle time. The software detection includes two status bits: Data# Polling
) and Toggle Bit (DQ6). The End-of-Write detection
(DQ
7
mode is incorporated into the FWH Read cycle. The actual
completion of the nonvolatile write is asynchronous with the
system; therefore, either a Data# Polling or Toggle Bit read
may be simultaneous with the completion of the Write
cycle. If this occurs, the system may possibly get an erroneous result, i.e., valid data may appear to conflict with either
or DQ6. In order to prevent spurious rejection, if an
DQ
7
erroneous result occurs, the software routine should
include a loop to read the accessed location an additional
two (2) times. If both reads are valid, then the device has
completed the Write cycle, otherwise the rejection is valid.
Data# Polling (DQ7)
When the SST49LF00xA device is in the internal Program
operation, any attempt to read DQ
will produce the com-
7
plement of the true data. Once the Program operation is
completed, DQ
though DQ
will produce true data. Note that even
7
may have valid data immediately following the
7
completion of an internal Write operation, the remaining
data outputs may still be invalid: valid data on the entire
data bus will appear in subsequent successive Read
cycles after an interval of 1 µs. During internal Erase operation, any attempt to read DQ
internal Erase operation is completed, DQ
will produce a ‘0’. Once the
7
will produce a
7
‘1’. Proper status will not be given using Data# Polling if the
address is in the invalid range.
Toggle Bit (DQ6)
During the internal Program or Erase operation, any consecutive attempts to read DQ
will produce alternating
6
‘0’s and ‘1’s, i.e., toggling between 0 and 1. When the
internal Program or Erase operation is completed, the
toggling will stop.
Multiple Device Selection
The four ID pins, ID[3:0], allow multiple devices to be
attached to the same bus by using different ID strapping in
a system. When the SST49LF00xA is used as a boot
device, ID[3:0] must be strapped as 0000, all subsequent
devices should use a sequential up-count strapping (i.e.
0001, 0010, 0011, etc.). The SST49LF00xA will compare
the strapping values, if there is a mismatch, the device will
ignore the remainder of the cycle and go into standby
mode. For further information regarding FWH device mapping and paging, please refer to the Intel 82801(ICH) I/O
Controller Hub documentation. Since there is no ID support
in PP Mode, to program multiple devices a stand-alone
PROM programmer is recommended.
REGISTERS
There are three types of registers available on the
SST49LF00xA, the General Purpose Inputs Register,
Block Locking Registers, and the JEDEC ID Registers.
These registers appear at their respective address location
in the 4 GByte system memory map. Unused register locations will read as 00H. Any attempt to read or write any register during an internal Write operation will be ignored.
General Purpose Inputs Register
The GPI_REG (General Purpose Inputs Register) passes
the state of FGPI[4:0] pins at power-up on the
SST49LF00xA. It is recommended that the FGPI[4:0] pins
are in the desired state before FWH4 is brought low for the
beginning of the bus cycle, and remain in that state until the
end of the cycle. There is no default value since this is a
pass-through register. The GPI register for the boot device
appears at FFBC0100H in the 4 GByte system memory
map, and will appear elsewhere if the device is not the boot
device. Register is not available for read when the device is
in Erase/Program operation. See Table 3 for the GPI_REG
bits and function.
SST49LF00xA provides software controlled lock protection through a set of Block Locking registers. The Block
Locking Registers are read/write registers and it is accessible through standard addressable memory locations
specified in Table 4 and Table 5. Unused register locations will read as 00H.
Reserved Bit [7..2]Lock-Down Bit [1]Write-Lock Bit [0]Lock Status
Write Lock
The Write-Lock bit, bit 0, controls the lock state described in
Table 6. The default Write status of all blocks after powerup is write locked. When bit 0 of the Block Locking register
is set, Program and Erase operations for the corresponding
block are prevented. Clearing the Write-Lock bit will unprotect the block. The Write-Lock bit must be cleared prior to
starting a Program or Erase operation since it is sampled at
the beginning of the operation.
The Write-Lock bit functions in conjunction with the hardware Write Lock pin TBL# for the top Boot Block. When
TBL# is low, it overrides the software locking scheme. The
top Boot Block Locking register does not indicate the state
of the TBL# pin.
The Write-Lock bit functions in conjunction with the hardware WP# pin for blocks 0 to 6. When WP# is low, it overrides the software locking scheme. The Block Locking
register does not indicate the state of the WP# pin.
LOCK LOCKING REGISTER BITS
00000000Full Access
00000001Write Locked (Default State at Power-Up)
00000010Locked Open (Full Access Locked Down)
00000011Write Locked Down
PARALLEL PROGRAMMING MODE
Device Operation
Commands are used to initiate the memory operation functions of the device. The data portion of the software command sequence is latched on the rising edge of WE#.
During the software command sequence the row address
is latched on the falling edge of R/C# and the column
address is latched on the rising edge of R/C#.
Read
The Read operation of the SST49LF00xA device is controlled by OE#. OE# is the output control and is used to
gate data from the output pins. Refer to the Read cycle
timing diagram, Figure 14, for further details.
Reset
A VIL on RST# pin initiates a device reset.
T6.3 504
Lock Down
The Lock-Down bit, bit 1, controls the Block Locking register as described in Table 6. When in the FWH interface
mode, the default Lock Down status of all blocks upon
power-up is not locked down. Once the Lock-Down bit is
set, any future attempted changes to that Block Locking
register will be ignored. The Lock-Down bit is only cleared
upon a device reset with RST# or INIT# or power down.
Current Lock Down status of a particular block can be
determined by reading the corresponding Lock-Down bit.
Once a block’s Lock-Down bit is set, the Write-Lock bits for
that block can no longer be modified, and the block is
locked down in its current state of write accessibility.
JEDEC ID Registers
The JEDEC ID registers for the boot device appear at
FFBC0000H and FFBC0001H in the 4 GByte system
memory map, and will appear elsewhere if the device is not
the boot device. Register is not available for read when the
device is in Erase/Program operation. Unused register
location will read as 00H. Refer to the relevant application
note for details. See Table 7 for the device ID code.
Byte-Program Operation
The SST49LF00xA device is programmed on a byte-bybyte basis. Before programming, one must ensure that the
sector, in which the byte which is being programmed exists,
is fully erased. The Byte-Program operation is initiated by
executing a four-byte command load sequence for Software Data Protection with address (BA) and data in the last
byte sequence. During the Byte-Program operation, the
row address (A
and the column Address (A
edge of R/C#. The data bus is latched in the rising edge of
WE#. The Program operation, once initiated, will be completed, within 20 µs. See Figure 15 for Program operation
timing diagram, Figure 18 for timing waveforms, and Figure
26 for its flowchart. During the Program operation, the only
valid reads are Data# Polling and Toggle Bit. During the
internal Program operation, the host is free to perform additional tasks. Any commands written during the internal Program operation will be ignored.
The Sector-Erase operation allows the system to erase
the device on a sector-by-sector basis. The sector architecture is based on uniform sector size of 4 KByte. The
Sector-Erase operation is initiated by executing a six-byte
command load sequence for Software Data Protection
with Sector-Erase command (30H) and sector address
(SA) in the last bus cycle. The internal Erase operation
begins after the sixth WE# pulse. The End-of-Erase can
be determined using either Data# Polling or Toggle Bit
methods. See Figure 19 for Sector-Erase timing waveforms. Any commands written during the Sector-Erase
operation will be ignored.
Block-Erase Operation
The Block-Erase Operation allows the system to erase the
device in 64 KByte uniform block size for the
SST49LF003A/SST49LF004A/SST49LF008A and 16
KByte uniform block size for the SST49LF002A. The BlockErase operation is initiated by executing a six-byte command load sequence for Software Data Protection with
Block-Erase command (50H) and block address. The internal Block-Erase operation begins after the sixth WE#
pulse. The End-of-Erase can be determined using either
Data# Polling or Toggle Bit methods. See Figure 20 for timing waveforms. Any commands written during the BlockErase operation will be ignored.
Chip-Erase
The SST49LF00xA device provides a Chip-Erase operation only in PP Mode, which allows the user to erase the
entire memory array to the ‘1’s state. This is useful when
the entire device must be quickly erased.
The Chip-Erase operation is initiated by executing a six- byte
Software Data Protection command sequence with ChipErase command (10H) with address 5555H in the last byte
sequence. The internal Erase operation begins with the rising edge of the sixth WE#. During the internal Erase operation, the only valid read is Toggle Bit or Data# Polling. See
Table 10 for the command sequence, Figure 21 for timing
diagram, and Figure 29 for the flowchart. Any commands
written during the Chip-Erase operation will be ignored.
Write Operation Status Detection
The SST49LF00xA device provides two software means
to detect the completion of a Write (Program or Erase)
cycle, in order to optimize the system Write cycle time. The
software detection includes two status bits: Data# Polling
) and Toggle Bit (DQ6). The End-of-Write detection
(DQ
7
mode is enabled after the rising edge of WE# which initiates the internal Program or Erase operation.
The actual completion of the nonvolatile write is asynchronous with the system; therefore, either a Data# Polling or Toggle Bit read may be simultaneous with the completion of the
Write cycle. If this occurs, the system may possibly get an
erroneous result, i.e., valid data may appear to conflict with
either DQ
or DQ6. In order to prevent spurious rejection, if an
7
erroneous result occurs, the software routine should include a
loop to read the accessed location an additional two (2) times.
If both reads are valid, then the device has completed the
Write cycle, otherwise the rejection is valid.
Data# Polling (DQ7)
When the SST49LF00xA device is in the internal Program
operation, any attempt to read DQ
will produce the com-
7
plement of the true data. Once the Program operation is
completed, DQ
though DQ
will produce true data. Note that even
7
may have valid data immediately following the
7
completion of an internal Write operation, the remaining
data outputs may still be invalid: valid data on the entire data
bus will appear in subsequent successive Read cycles after
an interval of 1 µs. During internal Erase operation, any
attempt to read DQ
Erase operation is completed, DQ
will produce a ‘0’. Once the internal
7
will produce a ‘1’. The
7
Data# Polling is valid after the rising edge of fourth WE#
pulse for Program operation. For Sector- or Chip-Erase, the
Data# Polling is valid after the rising edge of sixth WE#
pulse. See Figure 16 for Data# Polling timing diagram and
Figure 27 for a flowchart. Proper status will not be given
using Data# Polling if the address is in the invalid range.
Toggle Bit (DQ6)
During the internal Program or Erase operation, any consecutive attempts to read DQ
‘0’s and ‘1’s, i.e., toggling between 0 and 1. When the
internal Program or Erase operation is completed, the
toggling will stop. The device is then ready for the next
operation. The Toggle Bit is valid after the rising edge of
fourth WE# pulse for Program operation. For Sector-,
Block- or Chip-Erase, the Toggle Bit is valid after the rising edge of sixth WE# pulse. See Figure 17 for Toggle Bit
timing diagram and Figure 27 for a flowchart.
The SST49LF00xA device provides both hardware and
software features to protect nonvolatile data from inadvertent writes.
Hardware Data Protection
Noise/Glitch Protection: A WE# pulse of less than 5 ns will
not initiate a Write cycle.
Power Up/Down Detection: The Write operation is
V
DD
inhibited when V
Write Inhibit Mode:
is less than 1.5V.
DD
Forcing OE# low, WE# high will inhibit
the Write operation. This prevents inadvertent writes during
power-up or power-down.
Software Data Protection (SDP)
The SST49LF00xA provides the JEDEC approved Software Data Protection scheme for all data alteration operation, i.e., Program and Erase. Any Program operation
requires the inclusion of a series of three-byte sequences.
The three-byte load sequence is used to initiate the Program operation, providing optimal protection from inadvertent Write operations, e.g., during the system power-up or
power-down. Any Erase operation requires the inclusion of
a six-byte load sequence. The SST49LF00xA device is
shipped with the Software Data Protection permanently
enabled. See Table 10 for the specific software command
codes. During SDP command sequence, invalid commands will abort the device to Read mode, within T
RC.
Electrical Specifications
The AC and DC specifications for the FWH Interface signals (FWH[3:0], CLK, FWH4, and RST#) as defined in
Section 4.2.2 of the PCI Local Bus Specification, Rev. 2.1.
Refer to Table 11 for the DC voltage and current specifications. Refer to the tables on pages 19 through 23 for the AC
timing specifications for Clock, Read/Write, and Reset
operations.
Product Identification
The product identification mode identifies the device as the
SST49LF00xA and manufacturer as SST.
TABLE 7: P
Manufacturer’s ID0000HBFHFFBC0000H
Device ID
SST49LF002A0001H57HFFBC0001H
SST49LF003A0001H1BHFFBC0001H
SST49LF004A0001H60HFFBC0001H
SST49LF008A0001H5AHFFBC0001H
RODUCT IDENTIFICATION
ByteData
JEDEC ID
Address
Location
T7.5 504
Design Considerations
SST recommends a high frequency 0.1 µF ceramic capacitor
to be placed as close as possible between V
than 1 cm away from the V
pin of the device. Additionally, a
DD
low frequency 4.7 µF electrolytic capacitor from V
should be placed within 1 cm of the VDD pin. If you use a
socket for programming purposes add an additional 1-10 µF
next to each socket.
The RST# pin must remain stable at V
IH
tion of an Erase operation. WP# must remain stable at V
the entire duration of the Erase and Program operations for
non-Boot Block sectors. To write data to the top Boot Block
sectors, the TBL# pin must also remain stable at V
entire duration of the Erase and Program operations.
AddressIXInputs for low-order addresses during Read and Write operations.
-DQ0DataI/OXTo output data during Read cycles and receive input data during
OE#Output EnableIXTo gate the data output buffers
WE#Write EnableIXTo control the Write operations
ICInterface
Configuration Pin
INIT#InitializeIXThis is the second reset pin for in-system use. This pin is internally
ID[3:0]Identification InputsIXThese four pins are part of the mechanism that allows multiple parts
FGPI[4:0] General Purpose InputsIXThese individual inputs can be used for additional board flexibility.
TBL#Top Block LockIXWhen low, prevents programming to the Boot Block sectors at top of
FWH[3:0] FWH I/OsI/OXI/O Communications
CLKClockIXTo provide a clock input to the control unit
FWH4FWH InputIXInput Communications
RST#ResetIXXTo reset the operation of the device
WP#Write ProtectIXWhen low, prevents programming to all but the highest addressable
R/C#Row/Column SelectIXSelect For the Programming interface, this pin determines whether
RESReservedXThese pins must be left unconnected.
V
DD
V
SS
Power SupplyPWRXXTo provide power supply (3.0-3.6V)
GroundPWRXXCircuit ground (OV reference) All VSS pins must be grounded.
NCNo ConnectionIXXUnconnected pins
1. I = Input, O = Output
1
FunctionsPP FWH
Addresses are internally latched during a Write cycle. For the programming interface, these addresses are latched by R/C# and share
the same pins as the high-order address inputs.
Write cycles. Data is internally latched during a Write cycle. The outputs are in tri-state when OE# is high.
IXXThis pin determines which interface is operational. When held high,
programmer mode is enabled and when held low, FWH mode is
enabled. This pin must be setup at power-up or before return from
reset and not change during device operation. This pin is internally
pulled- down with a resistor between 20-100 KΩ.
combined with the RST# pin; If this pin or RST# pin is driven low,
identical operation is exhibited.
to be attached to the same bus. The strapping of these pins is used
to identify the component.The boot device must have ID[3:0]=0000
and it is recommended that all subsequent devices should use
sequential up-count strapping. These pins are internally pulled-down
with a resistor between 20-100 KΩ.
The state of these pins can be read through GPI_REG register.
These inputs should be at their desired state before the start of the
PCI clock cycle during which the read is attempted, and should
remain in place until the end of the Read cycle. Unused GPI pins
must not be floated.
memory. When TBL# is high it disables hardware write protection for
the top block sectors. This pin cannot be left unconnected.
blocks. When WP# is high it disables hardware write protection for
these blocks. This pin cannot be left unconnected.
the address pins are pointing to the row addresses, or to the column
addresses.
Absolute Maximum Stress Ratings (Applied conditions greater than those listed under “Absolute Maximum
Stress Ratings” may cause permanent damage to the device. This is a stress rating only and functional operation
of the device at these conditions or conditions greater than those defined in the operational sections of this data
sheet is not implied. Exposure to absolute maximum stress rating conditions may affect device reliability.)
1. The input test environment is done with 0.1 VDD of overdrive over VIH and VIL. Timing parameters must be met with no more
overdrive than this. V
may use different voltage values, but must correlate results back to these parameters.
specified the maximum peak-to-peak waveform allowed for measuring input timing. Production testing