The LH28F320S3TD-L10 Dual Work flash memory
with Smart 3 technology is a high-density, low-cost,
nonvolatile, read/write storage solution for a wide
range of applications, having high programming
performance is achieved through highly-optimized
page buffer operations. Its symmetrically-blocked
architecture, flexible voltage and enhanced cycling
capability provide for highly flexible component
suitable for resident flash arrays, SIMMs and
memory cards. Its enhanced suspend capabilities
provide for an ideal solution for code + data storage
applications. For secure code storage applications,
such as networking, where code is either directly
executed out of flash or downloaded to DRAM, the
LH28F320S3TD-L10 offers three levels of
protection : absolute protection with V
selective hardware block locking, or flexible
software block locking. These alternatives give
designers ultimate control of their code security
needs. LH28F320S3TD-L10 is conformed to the
flash Scalable Command Set (SCS) and the
Common Flash Interface (CFI) specification which
enable universal and upgradable interface, enable
the highest system/device data transfer rates and
minimize device and system-level implementation
costs.
FEATURES
• Smart 3 Dual Work technology
– 2.7 V or 3.3 V V
– 2.7 V, 3.3 V or 5 V VPP
– Capable of performing erase, write and read
for each bank independently (Impossible to
perform read from both banks at a time).
• High-speed write performance
– Two 32-byte page buffers/bank
– 2.7 µs/byte write transfer rate
• Common Flash Interface (CFI)
– Universal & upgradable interface
CC
PP at GND,
Smart 3 Dual Work Flash Memory
• Scalable Command Set (SCS)
• High performance read access time
– 100 ns (3.3±0.3 V)/120 ns (2.7 to 3.6 V)
• Enhanced automated suspend options
– Write suspend to read
– Block erase suspend to write
– Block erase suspend to read
• Enhanced data protection features
– Absolute protection with V
– Flexible block locking
– Erase/write lockout during power transitions
• Low power management
– Deep power-down mode
– Automatic power saving mode decreases Icc
in static mode
• Automated write and erase
– Command user interface
– Status register
TM
• ETOX
• Package
∗ ETOX is a trademark of Intel Corporation.
∗
– 56-pin TSOP Type I (TSOP056-P-1420)
LH28F320S3TD-L10
PP = GND
V nonvolatile flash technology
Normal bend
In the absence of confirmation by device specification sheets, SHARP takes no responsibility for any defects that may occur in equipment using any SHARP devices shown in catalogs, data books,
etc. Contact SHARP in order to obtain the latest device specification sheets before using any SHARP device.
ADDRESS INPUTS : Inputs for addresses during read and write operations. Addresses
are internally latched during a write cycle.
A
A
0-A20INPUT
DQ0-DQ15
BE0#,
BE1L#, BE1H#
INPUT/
OUTPUT
INPUT
RP#INPUT
OE#INPUTOUTPUT ENABLE : Gates the device’s outputs during a read cycle.
WE#INPUT
OPEN
STS
DRAIN
OUTPUT
WP#INPUT
BYTE#INPUT
V
PPSUPPLY
VCCSUPPLY
GNDSUPPLYGROUND : Do not float any ground pins.
NCNO CONNECT : Lead is not internal connected; recommend to be floated.
0 : Byte Select Address. Not used in x16 mode (can be floated).
A
1-A4 : Column Address. Selects 1 of 16-bit lines.
A
5-A15 : Row Address. Selects 1 of 2 048-word lines.
A16-A20 : Block Address.
DATA INPUT/OUTPUTS :
DQ
0-DQ7 : Inputs data and commands during CUI write cycles; outputs data during
memory array, status register, query, and identifier code read cycles. Data pins float to
high-impedance when the chip is deselected or outputs are disabled. Data is internally
latched during a write cycle.
DQ
8-DQ15 : Inputs data during CUI write cycles in x16 mode; outputs data during
memory array read cycles in x16 mode; not used for status register, query and identifier
code read mode. Data pins float to high-impedance when the chip is deselected, outputs
are disabled, or in x8 mode (BYTE# = VIL). Data is internally latched during a write cycle.
BANK ENABLE : Activates the device’s control logic, input buffers, decoders, and sense
amplifiers. When BE
0# and BE1L# "low", bank0 is in active. When BE0# and BE1H# are
"low", bank1 is in active. BE0# and BE1L#, BE1H# must not be low at the same time.
RESET/DEEP POWER-DOWN : Puts the device in deep power-down mode and resets
internal automation. RP# V
IH enables normal operation. When driven VIL, RP# inhibits
write operations which provide data protection during power transitions. Exit from deep
power-down sets the device to read array mode.
WRITE ENABLE : Controls writes to the CUI and array blocks. Addresses and data are
latched on the rising edge of the WE# pulse.
STS (RY/BY#) : Indicates the status of the internal WSM. When configured in level
mode (default mode) , it acts as a RY/BY# pin. When low, the WSM is performing an
internal operation (block erase, bank erase, (multi) word/byte write or block lock-bit
configuration). STS High Z indicates that the WSM is ready for new commands, block
ease is suspended, and (multi) word/byte write is inactive, (multi) word/byte write is
suspended or the device is in deep power-down mode. For alternate configurations of
the STATUS pin, see the Configuration command (Table 3 and Section 4.14).
WRITE PROTECT : Master control for block locking. When V
be erased and programmed, and block lock-bits can not be set and reset.
BYTE ENABLE : BYTE# V
on DQ
0-7, and DQ8-15 float. BYTE# VIH places the device in x16 mode, and turns off the
IL places device in x8 mode. All data are then input or output
A0 input buffer.
BLOCK ERASE, BANK ERASE, (MULTI) WORD/BYTE WRITE, BLOCK LOCK-BIT
CONFIGURATION POWER SUPPLY : For erasing array blocks, writing bytes or
configuring block lock-bits. With V
PP ≤ VPPLK, memory contents cannot be altered. Block
erase, bank erase, word/byte write, and block lock-bit configuration with an invalid V
(see Section 6.2.3 "DC CHARACTERISTICS") produce spurious results and should
not be attempted.
DEVICE POWER SUPPLY : Internal detection configures the device for 2.7 V or 3.3 V
operation. To switch from one voltage to another, ramp V
V
CC to the new voltage. Do not float any power pins. With VCC ≤ VLKO, all write attempts
CC down to GND and then ramp
to the flash memory are inhibited. Device operations at invalid V
6.2.3 "DC CHARACTERISTICS") produce spurious results and should not be attempted.
LH28F320S3TD-L10
IL, locked blocks can not
PP
CC voltage (see Section
- 4 -
Page 5
1 INTRODUCTION
This datasheet contains LH28F320S3TD-L10
specifications. Section 1 provides a flash memory
overview. Sections 2, 3, 4, and 5 describe the memory
organization and functionality. Section 6 covers
electrical specifications. The LH28F320S3TD-L10
flash memory documentation also includes ordering
information which is referenced in Section 7.
1.1Product Overview
The LH28F320S3TD-L10 is a high-performance
32 M-bit Smart 3 Dual Work flash memory
organized as 2 MB x8/1 MB x 16 x 2-Bank. The
4 MB of data is arranged in sixty-four 64 k-byte
blocks which are individually erasable, lockable,
and unlockable in-system. The memory map is
shown in Fig. 1.
LH28F320S3TD-L10
A block erase operation erases one of the device’s
64 k-byte blocks typically within 0.41 second (3.3 V
CC, 5 V VPP) independent of other blocks. Each
V
block can be independently erased 100 000 times
(3.2 million block erases per bank). Block erase
suspend mode allows system software to suspend
block erase to read data from, or write data to any
other block.
A word/byte write is performed in byte increments
typically within 12.95 µs (3.3 V V
multi word/byte write has high speed write
performance of 2.7 µs/byte (3.3 V V
(Multi) word/byte write suspend mode enables the
system to read data from, or write data to any other
flash memory array location.
CC, 5 V VPP). A
CC, 5 V VPP).
Smart 3 technology provides a choice of V
PP combinations, as shown in Table 1, to meet
V
system performance and power expectations. V
CC and
PP
at 2.7 V, 3.3 V and 5 V eliminates the need for a
separate 12 V converter. In addition to flexible
erase and program voltages, the dedicated V
gives complete data protection when V
Table 1 VCC and VPP Voltage Combinations
Offered by Smart 3 Technology
VCC VOLTAGEVPP VOLTAGE
2.7 V2.7 V, 3.3 V, 5 V
3.3 V3.3 V, 5 V
PP pin
PP ≤ VPPLK.
Internal VCC and VPP detection circuitry automatically configures the device for optimized read
and write operations.
A Command User Interface (CUI) serves as the
interface between the system processor and internal
operation of the device. A valid command sequence
written to the CUI initiates device automation. An
internal Write State Machine (WSM) automatically
executes the algorithms and timings necessary for
block erase, bank erase, (multi) word/byte write and
block lock-bit configuration operations.
Individual block locking uses a combination of bits
and WP#, sixty-four block lock-bits per bank, to lock
and unlock blocks. Block lock-bits gate block erase,
bank erase and (multi) word/byte write operations.
Block lock-bit configuration operations (Set Block
Lock-Bit and Clear Block Lock-Bits commands) set
and cleared block lock-bits.
The status register indicates when the WSM’s block
erase, bank erase, (multi) word/byte write or block
lock-bit configuration operation is finished.
The STS output gives an additional indicator of
WSM activity by providing both a hardware signal
of status (versus software polling) and status
masking (interrupt masking for background block
erase, for example). Status polling using STS
minimizes both CPU overhead and system power
consumption. STS pin can be configured to
different states using the Configuration command.
The STS pin defaults to RY/BY# operation. When
low, STS indicates that the WSM is performing a
block erase, bank erase, (multi) word/byte write or
block lock-bit configuration. STS High Z indicates
that the WSM is ready for a new command, block
erase is suspended and (multi) word/byte write are
- 5 -
Page 6
LH28F320S3TD-L10
inactive, (multi) word/byte write are suspended, or
the device is in deep power-down mode. The other
3 alternate configurations are all pulse mode for
use as a system interrupt.
The access time is 100 ns (t
AVQV) at the VCC
supply voltage range of 3.0 to 3.6 V over the
temperature range, 0 to +70°C. At 2.7 to 3.6 V
CC, the access time is 120 ns.
V
The Automatic Power Saving (APS) feature
substantially reduces active current when the
device is in static mode (addresses not switching).
In APS mode, the typical I
2.7 V and 3.3 V V
CC.
CCR current is 3 mA at
When either BE
are at V
0# or BE1L#, BE1H# and RP# pins
CC, the ICC CMOS standby mode is
enabled. When the RP# pin is at GND, deep
power-down mode is enabled which minimizes
power consumption and provides write protection
during reset. A reset time (t
PHQV) is required from
RP# switching high until outputs are valid. Likewise,
the device has a wake time (t
PHEL) from RP#-high
until writes to the CUI are recognized. With RP# at
GND, the WSM is reset and the status register is
cleared.
The LH28F320S3TD-L10 Smart 3 Dual Work flash
memory includes an on-chip WSM to manage
block erase, bank erase, (multi) word/byte write and
block lock-bit configuration functions. It allows for :
100% TTL-level control inputs, fixed power supplies
during block erase, bank erase, (multi) word/byte
write and block lock-bit configuration, and minimal
processor overhead with RAM-like interface timings.
After initial device power-up or return from deep
power-down mode (see Table 2.1 and Table 2.2"Bus Operations"), the device defaults to read
array mode. Manipulation of external memory
control pins allow array read, standby, and output
disable operations.
Status register, query structure and identifier codes
can be accessed through the CUI independent of
PP voltage. High voltage on VPP enables
the V
successful block erase, bank erase, (multi)
word/byte write and block lock-bit configuration. All
functions associated with altering memory
contents—lock erase, bank erase, (multi) word/byte
write and block lock-bit configuration, status, query
and identifier codes—are accessed via the CUI and
verified through the status register.
Commands are written using standard microprocessor write timings. The CUI contents serve as
input to the WSM, which controls the block erase,
bank erase, (multi) word/byte write and block lockbit configuration. The internal algorithms are
regulated by the WSM, including pulse repetition,
internal verification, and margining of data.
Addresses and data are internally latched during
write cycles. Writing the appropriate command
outputs array data, accesses the identifier codes,
outputs query structure or outputs status register
data.
LH28F320S3TD-L10
Interface software that initiates and polls progress
of block erase, bank erase, (multi) word/byte write
and block lock-bit configuration can be stored in
any block. This code is copied to and executed
from system RAM during flash memory updates.
After successful completion, reads are again
possible via the Read Array command. Block erase
suspend allows system software to suspend a
block erase to read/write data from/to blocks other
than that which is suspended. Write suspend allows
system software to suspend a (multi) word/byte
write to read data from any other flash memory
array location.
2.1Data Protection
Depending on the application, the system designer
may choose to make the V
switchable (available only when block erase, bank
erase, (multi) word/byte write and block lock-bit
configuration are required) or hardwired to
PPH1/2/3. The device accommodates either design
V
practice and encourages optimization of the
processor-memory interface.
When V
PP ≤ VPPLK, memory contents cannot be
altered. The CUI, with multi-step block erase, bank
erase, (multi) word/byte write and block lock-bit
configuration command sequences, provides
protection from unwanted operations even when
high voltage is applied to V
are disabled when V
voltage V
LKO or when RP# is at V IL. The device’s
CC is below the write lockout
block locking capability provides additional
protection from inadvertent code or data alteration
by gating block erase, bank erase and (multi)
word/byte write operations.
PP power supply
PP. All write functions
- 8 -
Page 9
3 BUS OPERATION
The local CPU reads and writes flash memory insystem. All bus cycles to or from the flash memory
conform to standard microprocessor bus cycles.
3.1Read
Information can be read from any block, identifier
codes, query structure, or status register
independent of the V
IH.
V
PP voltage. RP# must be at
The first task is to write the appropriate read mode
command (Read Array, Read Identifier Codes,
Query or Read Status Register) to the CUI. Upon
initial device power-up or after exit from deep
power-down mode, the device automatically resets
to read array mode. Five control pins dictate the
data flow in and out of the component : BE# (BE
1L#, BE1H#), OE#, WE#, RP# and WP#. BE0#,
BE
1L#, BE1H# and OE# must be driven active to
BE
obtain data at the outputs. BE
0#, BE1L#, BE1H# is
0#,
the device selection control, and when active
enables the selected memory device. OE# is the
data output (DQ
0-DQ15) control and when active
drives the selected memory data onto the I/O bus.
WE# and RP# must be at V
IH. Fig. 15 and Fig. 16
illustrate a read cycle.
3.2Output Disable
With OE# at a logic-high level (VIH), the device
outputs are disabled. Output pins DQ
0-DQ15 are
placed in a high-impedance state.
3.3Standby
Either BE0# or BE1L#, BE1H# at a logic-high level
IH) places the device in standby mode which
(V
substantially reduces device power consumption.
DQ
0-DQ15 outputs are placed in a high-impedance
state independent of OE#. If deselected during
block erase, bank erase, (multi) word/byte write and
block lock-bit configuration, the device continues
functioning, and consuming active power until the
operation completes.
LH28F320S3TD-L10
3.4Deep Power-Down
RP# at VIL initiates the deep power-down mode.
In read modes, RP#-low deselects the memory,
places output drivers in a high-impedance state and
turns off all internal circuits. RP# must be held low
for a minimum of 100 ns. Time t
after return from power-down until initial memory
access outputs are valid. After this wake-up
interval, normal operation is restored. The CUI is
reset to read array mode and status register is set
to 80H.
During block erase, bank erase, (multi) word/byte
write or block lock-bit configuration modes, RP#-low
will abort the operation. STS remains low until the
reset operation is complete. Memory contents being
altered are no longer valid; the data may be
partially erased or written. Time t
after RP# goes to logic-high (V
command can be written.
As with any automated device, it is important to
assert RP# during system reset. When the system
comes out of reset, it expects to read from the flash
memory. Automated flash memories provide status
information when accessed during block erase,
bank erase, (multi) word/byte write and block lockbit configuration. If a CPU reset occurs with no
flash memory reset, proper CPU initialization may
not occur because the flash memory may be
providing status information instead of array data.
SHARP’s flash memories allow proper CPU
initialization following a system reset through the
use of the RP# input. In this application, RP# is
controlled by the same RESET# signal that resets
the system CPU.
PHQV is required
PHWL is required
IH) before another
- 9 -
Page 10
3.5Read Identifier Codes Operation
Block 31 Status Code
Block 0
Block 1 Status Code
Block 0 Status Code
Device Code
Manufacture Code
1FFFFF
1F0006
1F0005
1F0004
1F0003
1F0000
1EFFFF
020000
01FFFF
010006
010005
010004
010003
010000
00FFFF
000006
000005
000004
000003
000002
000001
000000
1FFFFF
1F0006
1F0005
1F0004
1F0003
1F0000
1EFFFF
020000
01FFFF
010006
010005
010004
010003
010000
00FFFF
000006
000005
000004
000003
000002
000001
000000
Bank0
(BE0# = BE1L# = "L")
Bank1
(BE
0# = BE1H# = "L")
Reserved for
Future Implementation
Reserved for
Future Implementation
Block 31
(Blocks 2 through 30)
Reserved for
Future Implementation
Reserved for
Future Implementation
Block 1
Reserved for
Future Implementation
Block 0
Device Code
Manufacture Code
Reserved for
Future Implementation
Reserved for
Future Implementation
Block 31
(Blocks 2 through 30)
Reserved for
Future Implementation
Reserved for
Future Implementation
Block 1
Reserved for
Future Implementation
Block 31 Status Code
Block 1 Status Code
Block 0 Status Code
The read identifier codes operation outputs the
manufacture code, device code, block status codes
for each block (see Fig. 2). Using the manufacture
and device codes, the system CPU can
LH28F320S3TD-L10
automatically match the device with its proper
algorithms. The block status codes identify locked
or unlocked block setting and erase completed or
erase uncompleted condition.
3.6Query Operation
The query operation outputs the query structure.
Query database is stored in the 48-byte ROM per
bank. Query structure allows system software to
gain critical information for controlling the flash
component. Query structures are always presented
on the lowest-order data output (DQ
Fig. 2 Device Identifier Code Memory Map
0-DQ7) only.
3.7Write
Writing commands to the CUI enable reading of
device data and identifier codes. They also control
inspection and clearing of the status register. When
V
CC = VCC1/2 and VPP = VPPH1/2/3, the CUI
additionally controls block erase, bank erase, (multi)
word/byte write and block lock-bit configuration.
- 10 -
Page 11
LH28F320S3TD-L10
The Block Erase command requires appropriate
command data and an address within the block to
be erased. The Word/Byte Write command requires
the command and address of the location to be
BE# (whichever goes high first). Standard
microprocessor write timings are used. Fig. 17 and
Fig. 18 illustrate WE# and BE#-controlled write
operations.
written. Set Block Lock-Bit command requires the
command and block address within the device
(Block Lock) to be locked. The Clear Block LockBits command requires the command and address
within the device.
4 COMMAND DEFINITIONS
When the VPP voltage VPPLK, read operations from
the status register, identifier codes, query, or blocks
are enabled. Placing V
PPH1/2/3 on VPP enables
successful block erase, bank erase, (multi)
The CUI does not occupy an addressable memory
location. It is written when WE# and BE# are
active. The address and data needed to execute a
command are latched on the rising edge of WE# or
Table 2.1 Bus Operations (BYTE# = VIH)
MODENOTERP#BE0#BE1L#BE1H#OE#WE#
Bank0
ReadBank1
DisableVILVILVIL
1, 2, 3,
9, 10
VIHVILVIHVILVILVIHXXDOUTX
Output Disable3VIHVILVILVILVIHVIHXXHigh ZX
Bank0
StandbyBank13V
Bank0, 1
Deep Power-Down4VILXXXXXXXHigh Z High Z
Read
Identifier
Codes
Bank0V
Bank19, 10V
DisableV
Query9, 10VIHVILVILVILVILVIH
Bank0
WriteBank1
Bank0, 1V
3, 7,
8, 9
VIHVILVIHVILVIHVILXXDINX
V
ILVILVIH
V
IH
IHVILVIHVILVILVIH
IHXX
VILVIHVIH
ILVILVIH
ILVILVIL
VILVILVIH
ILVILVIL
word/byte write and block lock-bit configuration
operations. Device operations are selected by
writing specific commands into the CUI. Table 3
defines these commands.
ADDRESS
XXXXHigh ZX
See
Fig. 2
See Table
6 through 10
VPPDQ0-15STS
X
X
(NOTE 5)
(NOTE 6)
High Z
High Z
NOTES :
1. Refer to Section 6.2.3 "DC CHARACTERISTICS".
When V
PP ≤ VPPLK, memory contents can be read, but
not altered.
2. X can be V
PPLK or VPPH1/2/3 for VPP. See Section 6.2.3 "DC
V
CHARACTERISTICS" for V
3. STS is V
WSM is executing internal block erase, bank erase,
(multi) word/byte write or block lock-configuration
algorithms. It is floated during when the WSM is not
busy, in block erase suspend mode with (multi)
word/byte write inactive, (multi) word/byte write suspend
mode, or deep power-down mode.
IL or VIH for control pins and addresses, and
PPLK and VPPH1/2/3 voltages.
OL (if configured to RY/BY# mode) when the
4. RP# at GND±0.2 V ensures the lowest deep powerdown current.
5. See Section 4.2 for read identifier code data.
6. See Section 4.5 for query data.
7. Command writes involving block erase, bank erase,
(multi) word/byte write or block lock-bit configuration are
reliably executed when V
CC1/2.
V
8. Refer to Table 3 for valid D
9. Don’t use the timing both OE# and WE# are V
10. Impossible to perform simultaneous read from both
banks at a time. Both BE
be low at the same time.
PP = VPPH1/2/3 and VCC =
IN during a write operation.
IL.
0# and BE1L#, BE1H# must not
- 11 -
Page 12
LH28F320S3TD-L10
Table 2.2 Bus Operations (BYTE# = VIL)
MODENOTERP#BE0#BE1L#BE1H#OE#WE#
Bank0
ReadBank1
DisableVILVILVIL
1, 2, 3,
9, 10
VIHVILVIHVILVILVIHXXDOUTX
ILVILVIH
V
Output Disable3VIHVILVILVILVIHVIHXXHigh ZX
Bank0
StandbyBank13V
Bank0, 1
IH
IHXX
V
VILVIHVIH
XXXXHigh ZX
Deep Power-Down4VILXXXXX X XHigh Z High Z
Read
Identifier
Codes
Bank0VILVILVIH
Bank19, 10V
DisableV
IHVILVIHVILVILVIH
ILVILVIL
Query9, 10VIHVILVILVILVILVIH
Bank0
WriteBank1
Bank0, 1VILVILVIL
3, 7,
8, 9
VIHVILVIHVILVIHVILXXDINX
VILVILVIH
NOTES :
1. Refer to Section 6.2.3 "DC CHARACTERISTICS".
When V
PP ≤ VPPLK, memory contents can be read, but
not altered.
2. X can be V
V
PPLK or VPPH1/2/3 for VPP. See Section 6.2.3 "DC
CHARACTERISTICS" for V
3. STS is V
WSM is executing internal block erase, bank erase,
(multi) word/byte write or block lock-configuration
algorithms. It is floated during when the WSM is not
busy, in block erase suspend mode with (multi)
word/byte write inactive, (multi) word/byte write suspend
mode, or deep power-down mode.
IL or VIH for control pins and addresses, and
PPLK and VPPH1/2/3 voltages.
OL (if configured to RY/BY# mode) when the
4. RP# at GND±0.2 V ensures the lowest deep powerdown current.
5. See Section 4.2 for read identifier code data.
6. See Section 4.5 for query data.
7. Command writes involving block erase, bank erase,
(multi) word/byte write or block lock-bit configuration are
reliably executed when V
CC1/2.
V
8. Refer to Table 3 for valid D
9. Don’t use the timing both OE# and WE# are V
10. Impossible to perform simultaneous read from both
banks at a time. Both BE
be low at the same time.
ADDRESS
See
Fig. 2
See Table
6 through 10
VPPDQ0-7STS
X
(NOTE 5)
X
(NOTE 6)
PP = VPPH1/2/3 and VCC =
IN during a write operation.
0# and BE1L#, BE1H# must not
High Z
High Z
IL.
- 12 -
Page 13
LH28F320S3TD-L10
COMMAND
Table 3 Command Definitions
BUS CYCLES
REQ’D.
NOTE
Oper
FIRST BUS CYCLESECOND BUS CYCLE
(NOTE 1)
Addr
(NOTE 10)
(NOTE 2)
Data
(NOTE 3)
Oper
(NOTE 1)
Addr
(NOTE 2)
Data
Read Array/Reset1WriteXFFH
Read Identifier Codes≥ 24WriteX90HReadIAID
Query≥ 2WriteX98HReadQAQD
Read Status Register2WriteX70HReadXSRD
Clear Status Register1WriteX50H
Block Erase Setup/Confirm25WriteBA20HWriteBAD0H
Bank Erase Setup/Confirm2WriteX30HWriteXD0H
Word/Byte Write Setup/Write25, 6WriteWA40HWriteWAWD
Alternate Word/Byte Write
Setup/Write
Multi Word/Byte Write
Setup/Confirm
Block Erase and (Multi)
Word/Byte Write Suspend
Confirm and Block Erase and
(Multi) Word/Byte Write Resume
Block Lock-Bit Set
Setup/Confirm
Block Lock-Bit Reset
Setup/Confirm
25, 6WriteWA10HWriteWAWD
≥ 49WriteWAE8HWriteWAN–1
15WriteXB0H
15WriteXD0H
27WriteBA60HWriteBA01H
28WriteX60HWriteXD0H
STS Configuration
Level-Mode for Erase2WriteXB8HWriteX00H
and Write (RY/BY# Mode)
STS Configuration
Pulse-Mode for Erase
STS Configuration
Pulse-Mode for Write
STS Configuration Pulse-Mode
for Erase and Write
2WriteXB8HWriteX01H
2WriteXB8HWriteX02H
2WriteXB8HWriteX03H
NOTES :
1. BUS operations are defined in Table 2.1 and Table 2.2.
2. X = Any valid address within the device.
IA = Identifier code address : see Fig. 2.
QA = Query offset address.
BA = Address within the block being erased or locked.
WA = Address of memory location to be written.
3. SRD = Data read from status register. See Table 13.1
for a description of the status register bits.
WD = Data to be written at location WA. Data is latched
on the rising edge of WE# or BE# (whichever
goes high first).
ID = Data read from identifier codes.
QD = Data read from query database.
4. Following the Read Identifier Codes command, read
operations access manufacture, device and block status
codes. See Section 4.2 for read identifier code data.
5. If the block is locked, WP# must be at V
block erase or (multi) word/byte write operations.
Attempts to issue a block erase or (multi) word/byte write
to a locked block while RP# is V
6. Either 40H or 10H is recognized by the WSM as the
byte write setup.
7. A block lock-bit can be set while WP# is V
8. WP# must be at V
block lock-bits operation simultaneously clears all block
lock-bits.
9. Following the Third Bus Cycle, inputs the write address
and write data of "N" times. Finally, input the confirm
command "D0H".
10. Commands other than those shown above are reserved
by SHARP for future device implementations and should
not be used.
IH to clear block lock-bits. The clear
IH.
IH to enable
IH.
(NOTE 3)
- 13 -
Page 14
LH28F320S3TD-L10
4.1Read Array Command
Upon initial device power-up and after exit from
deep power-down mode, the device defaults to
read array mode. This operation is also initiated by
writing the Read Array command. The device
remains enabled for reads until another command
is written. Once the internal WSM has started a
block erase, bank erase, (multi) word/byte write or
block lock-bit configuration, the device will not
recognize the Read Array command until the WSM
completes its operation unless the WSM is
suspended via an Erase Suspend and (Multi)
Word/Byte Write Suspend command. The Read
Array command functions independently of the V
PP
voltage and RP# must be VIH.
4.2Read Identifier Codes Command
The identifier code operation is initiated by writing
the Read Identifier Codes command. Following the
command write, read cycles from addresses shown
in Fig. 2 retrieve the manufacture, device, block
lock configuration and block erase status (see
Table 4 for identifier code values). To terminate the
operation, write another valid command. Like the
Read Array command, the Read Identifier Codes
DATA
B0
D0
DQ
DQ
PP
1 = 0
1 = 1
2-7
command functions independently of the V
voltage and RP# must be VIH. Following the Read
Identifier Codes command, the following information
can be read :
Table 4 Identifier Codes
CODE
Manufacture Code
Device Code
Block Status Code
•Block is UnlockedDQ0 = 0
•Block is LockedDQ0 = 1
•Last erase operation
completed successfully
•Last erase operation did
not completed successfully
•Reserved for Future UseDQ
ADDRESS
00000H
00001H
00002H
00003H
(NOTE 1)
X0004H
(NOTE 1)
X0005H
NOTE :
1. X selects the specific block status code to be read. See
Fig. 2 for the device identifier code memory map.
4.3Read Status Register Command
The status register may be read to determine when
a block erase, bank erase, (multi) word/byte write
or block lock-bit configuration is complete and
whether the operation completed successfully (see
Table 13.1). It may be read at any time by writing
the Read Status Register command. After writing
this command, all subsequent read operations
output data from the status register until another
valid command is written. The status register
contents are latched on the falling edge of OE# or
0# or BE1# (Either BE1L# or BE1H#), whichever
BE
occurs. OE# or BE
BE
1H#) must toggle to VIH before further reads to
0# or BE1# (Either BE1L# or
update the status register latch. The Read Status
Register command functions independently of the
PP voltage. RP# must be VIH.
V
The extended status register may be read to
determine multi byte write availability (see Table
13.2). The extended status register may be read at
any time by writing the Multi Byte Write command.
After writing this command, all subsequent read
operations output data from the extended status
register, until another valid command is written. The
contents of the extended status register are latched
on the falling edge of OE# or BE
BE
1L# or BE1H#), whichever occurs last in the read
0# or BE1# (Either
cycle. Multi Byte Write command must be re-issued
to update the extended status register latch.
4.4Clear Status Register Command
Status register bits SR.5, SR.4, SR.3 and SR.1 are
set to "1"s by the WSM and can only be reset by
the Clear Status Register command. These bits
indicate various failure conditions (see Table 13.1).
By allowing system software to reset these bits,
several operations (such as cumulatively erasing or
locking multiple blocks or writing several bytes in
- 14 -
Page 15
LH28F320S3TD-L10
sequence) may be performed. The status register
may be polled to determine if an error occurs
during the sequence.
To clear the status register, the Clear Status
Register command (50H) is written. It functions
independently of the applied V
must be V
IH. This command is not functional during
PP voltage. RP#
block erase, bank erase, (multi) word/byte write,
block lock-bit configuration, block erase suspend or
(multi) word/byte write suspend modes.
4.5Query Command
Query database of each bank can be read by
writing Query command (98H). Following the
command write, read cycle from address shown in
Table 6 through Table 10 retrieve the critical
information to write, erase and otherwise control the
flash component. A
ignored when x8 mode (BYTE# = V
Query data of each bank are always presented on
the low-byte data output (DQ
high-byte (DQ
0 of query offset address is
IL).
0-DQ7). In x16 mode,
8-DQ15) outputs 00H. The bytes not
assigned to any information or reserved for future
use are set to "0". This command functions
independently of the V
This field provides lock configuration and erase
status for the specified block. These informations
are only available when device is ready (SR.7 = 1).
If block erase or bank erase operation is finished
irregularly, block erase status bit will be set to "1". If
bit 1 is "1", this block is invalid.
Table 6 Query Block Status Register
OFFSET
(Word Address)
(BA+2)H01HBlock Status Register
LENGTHDESCRIPTION
bit0Block Lock Configuration
0 = Block is unlocked
1 = Block is locked
bit1Block Erase Status
0 = Last erase operation completed successfully
1 = Last erase operation not completed successfully
bit2-7 Reserved for future use
NOTE :
1. BA = The beginning of a Block Address.
- 15 -
Page 16
LH28F320S3TD-L10
4.5.2 CFI QUERY IDENTIFICATION STRING
The identification string provides verification that the
component supports the Common Flash Interface
specification. Additionally, it indicates which version
Table 7 CFI Query Identification String
OFFSET
(Word Address)
10H, 11H, 12H03HQuery Unique ASCII string "QRY"
13H, 14H02HPrimary Vendor Command Set and Control Interface ID Code
15H, 16H02HAddress for Primary Algorithm Extended Query Table
17H, 18H02HAlternate Vendor Command Set and Control Interface ID Code
19H, 1AH02HAddress for Alternate Algorithm Extended Query Table
LENGTHDESCRIPTION
51H, 52H, 59H
01H, 00H (SCS ID Code)
31H, 00H (SCS Extended Query Table Offset)
0000H (0000H means that no alternate exists)
0000H (0000H means that no alternate exists)
of the spec and which vendor-specified command
set(s) is(are) supported.
4.5.3 SYSTEM INTERFACE INFORMATION
The following device information can be useful in optimizing system interface software.
Table 8 System Information String
OFFSET
(Word Address)
1BH01HV
1CH01HV
1DH01HV
1EH01HV
1FH01HTypical Time-Out per Single Byte/Word Write
20H01HTypical Time-Out for Maximum Size Buffer Write (32 Bytes)
21H01HTypical Time-Out per Individual Block Erase
22H01HTypical Time-Out for Bank Erase
23H01HMaximum Time-Out per Single Byte/Word Write, 2
24H01HMaximum Time-Out per Maximum Size Buffer Write, 2
25H01HMaximum Time-Out per Individual Block Erase, 2
26H01HMaximum Time-Out for Bank Erase, 2
LENGTHDESCRIPTION
CC Logic Supply Minimum Write/Erase voltage
27H (2.7 V)
CC Logic Supply Maximum Write/Erase voltage
55H (5.5 V)
PP Programming Supply Minimum Write/Erase voltage
27H (2.7 V)
PP Programming Supply Maximum Write/Erase voltage
55H (5.5 V)
03H (23= 8 µs)
06H (26= 64 µs)
0AH (0AH = 10, 210= 1 024 ms)
0FH (0FH = 15, 215= 32 768 ms)
04H (24= 16, 8 µs x 16 = 128 µs)
04H (24= 16, 64 µs x 16 = 1 024 µs)
04H (24= 16, 1 024 ms x 16 = 16 384 ms)
N
times of typical.
04H (2
4
= 16, 32 768 ms x 16 = 524 288 ms)
N
times of typical.
N
times of typical.
N
times of typical.
- 16 -
Page 17
4.5.4 DEVICE GEOMETRY DEFINITION
This field provides critical details of the flash device geometry.
Table 9 Device Geometry Definition
OFFSET
(Word Address)
27H01HDevice Size
28H, 29H02HFlash Device Interface Description
2AH, 2BH02HMaximum Number of Bytes in Multi Word/Byte Write
2CH01HNumber of Erase Block Regions within Device
2DH, 2EH02HThe Number of Erase Blocks
2FH, 30H02HThe Number of "256 Bytes" Cluster in a Erase Block
LENGTHDESCRIPTION
15H (15H = 21, 221= 2 097 152 = 2 M Bytes)
02H, 00H (x8/x16 supports x8 and x16 via BYTE#)
05H, 00H (25= 32 Bytes )
01H (symmetrically blocked)
1FH, 00H (1FH = 31 ⇒ 31 + 1 = 32 Blocks)
00H, 01H (0100H = 256 ⇒ 256 Bytes x 256 = 64 k Bytes in a Erase Block)
LH28F320S3TD-L10
- 17 -
Page 18
LH28F320S3TD-L10
4.5.5 SCS OEM SPECIFIC EXTENDED QUERY
TABLE
Certain flash features and commands may be
optional in a vendor-specific algorithm specification.
The optional vendor-specific query table(s) may be
Table 10 SCS OEM Specific Extended Query Table
OFFSET
(Word Address)
31H, 32H, 33H03HPRI
34H01H31H (1) Major Version Number , ASCII
35H01H30H (0) Minor Version Number, ASCII
36H, 37H,04H0FH, 00H, 00H, 00H
38H, 39HOptional Command Support
3AH01H01H
3BH, 3CH02H03H, 00H
3DH01HVCC Logic Supply Optimum Write/Erase voltage (highest performance)
3EH01HV
3FHreservedReserved for future versions of the SCS specification
bit0 = 1 : Write Supported after Erase Suspend
bit1-7 = 0 : Reserved for future use
Block Status Register Mask
bit0 = 1 : Block Status Register Lock Bit [BSR.0] active
bit1 = 1 : Block Status Register Valid Bit [BSR.1] active
bit2-15 = 0 : Reserved for future use
50H (5.0 V)
PP Programming Supply Optimum Write/Erase voltage (highest performance)
50H (5.0 V)
used to specify this and other types of information.
These structures are defined solely by the flash
vendor(s).
- 18 -
Page 19
LH28F320S3TD-L10
4.6Block Erase Command
Block erase is executed one block at a time and
initiated by a two-cycle command. A block erase
setup is first written, followed by a block erase
confirm. This command sequence requires
appropriate sequencing and an address within the
block to be erased (erase changes all block data to
FFH). Block preconditioning, erase and verify are
handled internally by the WSM (invisible to the
system). After the two-cycle block erase sequence
is written, the device automatically outputs status
register data when read (see Fig. 3). The CPU can
detect block erase completion by analyzing the
output data of the STS pin or status register bit
SR.7.
When the block erase is complete, status register
bit SR.5 should be checked. If a block erase error
is detected, the status register should be cleared
before system software attempts corrective actions.
The CUI remains in read status register mode until
a new command is issued.
This two-step command sequence of set-up
followed by execution ensures that block contents
are not accidentally erased. An invalid Block Erase
command sequence will result in both status
register bits SR.4 and SR.5 being set to "1". Also,
reliable block erasure can only occur when V
CC1/2 and VPP = VPPH1/2/3. In the absence of this
V
high voltage, block contents are protected against
erasure. If block erase is attempted while V
PPLK, SR.3 and SR.5 will be set to "1". Successful
V
block erase requires that the corresponding block
lock-bit be cleared or if set, that WP# = V
erase is attempted when the corresponding block
lock-bit is set and WP# = V
IL, SR.1 and SR.5 will
be set to "1".
CC =
PP ≤
IH. If block
4.7Bank Erase Command
This command followed by a confirm command
(D0H) erases all of the unlocked blocks. A bank
erase setup is first written, followed by a bank
erase confirm. After a confirm command is written,
device erases the all unlocked blocks from block 0
to block 31 block by block. This command
sequence requires appropriate sequencing. Block
preconditioning, erase and verify are handled
internally by the WSM (invisible to the system).
After the two-cycle bank erase sequence is written,
the device automatically outputs status register data
when read (see Fig. 4). The CPU can detect bank
erase completion by analyzing the output data of
the STS pin or status register bit SR.7.
When the bank erase is complete, status register
bit SR.5 should be checked. If erase error is
detected, the status register should be cleared
before system software attempts corrective actions.
The CUI remains in read status register mode until
a new command is issued. If error is detected on a
block during bank erase operation, WSM stops
erasing. Reading the block valid status by issuing
Read ID Codes command or Query command
informs which blocks failed to its erase.
This two-step command sequence of set-up
followed by execution ensures that block contents
are not accidentally erased. An invalid Bank Erase
command sequence will result in both status
register bits SR.4 and SR.5 being set to "1". Also,
reliable bank erasure can only occur when V
CC1/2 and VPP = VPPH1/2/3. In the absence of this
V
high voltage, block contents are protected against
erasure. If bank erase is attempted while V
V
PPLK, SR.3 and SR.5 will be set to "1". When
WP# = V
IH, all blocks are erased independent of
block lock-bits status. When WP# = V
unlocked blocks are erased. In this case, SR.1 and
SR.4 will not be set to "1". Bank erase can not be
suspended.
CC =
PP ≤
IL, only
- 19 -
Page 20
LH28F320S3TD-L10
4.8Word/Byte Write Command
Word/byte write is executed by a two-cycle
command sequence. Word/Byte Write setup
(standard 40H or alternate 10H) is written, followed
by a second write that specifies the address and
data (latched on the rising edge of WE#). The
WSM then takes over, controlling the word/byte
write and write verify algorithms internally. After the
word/byte write sequence is written, the device
automatically outputs status register data when
read (see Fig. 5). The CPU can detect the
completion of the word/byte write event by
analyzing the STS pin or status register bit SR.7.
When word/byte write is complete, status register
bit SR.4 should be checked. If word/byte write error
is detected, the status register should be cleared.
The internal WSM verify only detects errors for "1"s
that do not successfully write to "0"s. The CUI
remains in read status register mode until it
receives another command.
Reliable word/byte writes can only occur when V
CC
= VCC1/2 and VPP = VPPH1/2/3. In the absence of
this high voltage, memory contents are protected
against word/byte writes. If word/byte write is
attempted while V
PP ≤ VPPLK, status register bits
SR.3 and SR.4 will be set to "1". Successful
word/byte write requires that the corresponding
block lock-bit be cleared or, if set, that WP# = V
IH.
If word/byte write is attempted when the
corresponding block lock-bit is set and WP# = V
IL,
SR.1 and SR.4 will be set to "1". Word/byte write
operations with V
IL < WP# < VIH produce spurious
results and should not be attempted.
4.9Multi Word/Byte Write Command
Multi word/byte write is executed by at least fourcycle or up to 35-cycle command sequence. Up to
32 bytes in x8 mode (16 words in x16 mode) can
be loaded into the buffer and written to the flash
array. First, multi word/byte write setup (E8H) is
written with the write address. At this point, the
device automatically outputs extended status
register data (XSR) when read (see Fig. 6 and
Fig. 7). If extended status register bit XSR.7 is 0,
no Multi Word/Byte Write command is available and
multi word/byte write setup which just has been
written is ignored. To retry, continue monitoring
XSR.7 by writing multi word/byte write setup with
write address until XSR.7 transitions to "1". When
XSR.7 transitions to "1", the device is ready for
loading the data to the buffer. A word/byte count
(N)–1 is written with write address. After writing a
word/byte count (N)–1, the device automatically
turns back to output status register data. The
word/byte count (N)–1 must be less than or equal
to 1FH in x8 mode (0FH in x16 mode). On the next
write, device start address is written with buffer
data. Subsequent writes provide additional device
address and data, depending on the count. All
subsequent address must lie within the start
address plus the count. After the final buffer data is
written, write confirm (D0H) must be written. This
initiates WSM to begin copying the buffer data to
the flash array. An invalid Multi Word/Byte Write
command sequence will result in both status
register bits SR.4 and SR.5 being set to "1". For
additional multi word/byte write, write another multi
word/byte write setup and check XSR.7. The Multi
Word/Byte Write command can be queued while
WSM is busy as long as XSR.7 indicates "1",
because LH28F320S3TD-L10 has two buffers. If an
error occurs while writing, the device will stop
writing and flush next Multi Word/Byte Write
command loaded in Multi Word/Byte Write
command. Status register bit SR.4 will be set to "1".
No Multi Word/Byte Write command is available if
either SR.4 or SR.5 is set to "1". SR.4 and SR.5
should be cleared before issuing Multi Word/Byte
Write command. If a Multi Word/Byte Write
command is attempted past an erase block
boundary, the device will write the data to flash
array up to an erase block boundary and then stop
writing. Status register bits SR.4 and SR.5 will be
set to "1".
- 20 -
Page 21
LH28F320S3TD-L10
Reliable multi byte writes can only occur when VCC
= VCC1/2 and VPP = VPPH1/2/3. In the absence of
this high voltage, memory contents are protected
against multi word/byte writes. If multi word/byte
write is attempted while V
PP ≤ VPPLK, status
register bits SR.3 and SR.4 will be set to "1".
Successful multi word/byte write requires that the
corresponding block lock-bit be cleared or, if set,
that WP# = V
IH. If multi byte write is attempted
when the corresponding block lock-bit is set and
WP# = V
IL, SR.1 and SR.4 will be set to "1".
4.10 Block Erase Suspend Command
The Block Erase Suspend command allows block
erase interruption to read or (multi) word/byte write
data in another block of memory. Once the block
erase process starts, writing the Block Erase
Suspend command requests that the WSM
suspend the block erase sequence at a
predetermined point in the algorithm. The device
outputs status register data when read after the
Block Erase Suspend command is written. Polling
status register bits SR.7 and SR.6 can determine
when the block erase operation has been
suspended (both will be set to "1"). STS will also
transition to High Z. Specification t
the block erase suspend latency.
At this point, a Read Array command can be
written to read data from blocks other than that
which is suspended. A (Multi) Word/Byte Write
command sequence can also be issued during
erase suspend to program data in other blocks.
Using the (Multi) Word/Byte Write Suspend
command (see Section 4.11), a (multi) word/byte
write operation can also be suspended. During a
(multi) word/byte write operation with block erase
suspended, status register bit SR.7 will return to "0"
and the STS (if set to RY/BY#) output will transition
OL. However, SR.6 will remain "1" to indicate
to V
block erase suspend status.
The only other valid commands while block erase is
WHRH2 defines
suspended are Read Status Register and Block
Erase Resume. After a Block Erase Resume
command is written to the flash memory, the WSM
will continue the block erase process. Status
register bits SR.6 and SR.7 will automatically clear
and STS will return to V
OL. After the Erase Resume
command is written, the device automatically
outputs status register data when read (see Fig. 8).
PP must remain at V PPH1/2/3 (the same VPP level
V
used for block erase) while block erase is
suspended. RP# must also remain at V
IH. Block
erase cannot resume until (multi) word/byte write
operations initiated during block erase suspend
have completed.
4.11 (Multi) Word/Byte Write Suspend
Command
The (Multi) Word/Byte Write Suspend command
allows (multi) word/byte write interruption to read
data in other flash memory locations. Once the
(multi) word/byte write process starts, writing the
(Multi) Word/Byte Write Suspend command
requests that the WSM suspend the (multi)
word/byte write sequence at a predetermined point
in the algorithm. The device continues to output
status register data when read after the (Multi)
Word/Byte Write Suspend command is written.
Polling status register bits SR.7 and SR.2 can
determine when the (multi) word/byte write
operation has been suspended (both will be set to
"1"). STS will also transition to High Z. Specification
WHRH1 defines the (multi) word/byte write suspend
t
latency.
At this point, a Read Array command can be
written to read data from locations other than that
which is suspended. The only other valid
commands while (multi) word/byte write is
suspended are Read Status Register and (Multi)
Word/Byte Write Resume. After (Multi) Word/Byte
Write Resume command is written to the flash
memory, the WSM will continue the (multi)
word/byte write process. Status register bits SR.2
- 21 -
Page 22
LH28F320S3TD-L10
and SR.7 will automatically clear and STS will
return to V
OL. After the (Multi) Word/Byte Write
command is written, the device automatically
outputs status register data when read (see Fig. 9).
PP must remain at V PPH1/2/3 (the same VPP level
V
used for (multi) word/byte write) while in (multi)
word/byte write suspend mode. WP# must also
remain at V
IH or VIL.
4.12 Set Block Lock-Bit Command
A flexible block locking and unlocking scheme is
enabled via block lock-bits. The block lock-bits gate
program and erase operations. With WP# = V
individual block lock-bits can be set using the Set
Block Lock-Bit command. See Table 12 for a
summary of hardware and software write protection
options.
Set block lock-bit is executed by a two-cycle
command sequence. The set block lock-bit setup
along with appropriate block or device address is
written followed by either the set block lock-bit
confirm (and an address within the block to be
locked). The WSM then controls the set block lockbit algorithm. After the sequence is written, the
device automatically outputs status register data
when read (see Fig. 10). The CPU can detect the
completion of the set block lock-bit event by
analyzing the STS pin output or status register bit
SR.7.
When the set block lock-bit operation is complete,
status register bit SR.4 should be checked. If an
error is detected, the status register should be
cleared. The CUI will remain in read status register
mode until a new command is issued.
This two-step sequence of set-up followed by
execution ensures that block lock-bits are not
accidentally set. An invalid Set Block Lock-Bit
command will result in status register bits SR.4 and
SR.5 being set to "1". Also, reliable operations
occur only when V
CC = VCC1/2 and VPP = VPPH1/2/3.
IH,
In the absence of this high voltage, block lock-bit
contents are protected against alteration.
A successful set block lock-bit operation requires
WP# = V
IH. If it is attempted with WP# = VIL, SR.1
and SR.4 will be set to "1" and the operation will
fail. Set block lock-bit operations with WP# < V
produce spurious results and should not be
attempted.
4.13 Clear Block Lock-Bits Command
All set block lock-bits are cleared in parallel via the
Clear Block Lock-Bits command. With WP# = V
block lock-bits can be cleared using only the Clear
Block Lock-Bits command. See Table 12 for a
summary of hardware and software write protection
options.
Clear block lock-bits operation is executed by a
two-cycle command sequence. A clear block lockbits setup is first written. After the command is
written, the device automatically outputs status
register data when read (see Fig. 11). The CPU
can detect completion of the clear block lock-bits
event by analyzing the STS pin output or status
register bit SR.7.
When the operation is complete, status register bit
SR.5 should be checked. If a clear block lock-bits
error is detected, the status register should be
cleared. The CUI will remain in read status register
mode until another command is issued.
This two-step sequence of set-up followed by
execution ensures that block lock-bits are not
accidentally cleared. An invalid Clear Block LockBits command sequence will result in status register
bits SR.4 and SR.5 being set to "1". Also, a reliable
clear block lock-bits operation can only occur when
CC = VCC1/2 and VPP = VPPH1/2/3. If a clear block
V
lock-bits operation is attempted while V
PP ≤ VPPLK,
SR.3 and SR.5 will be set to "1". In the absence of
this high voltage, the block lock-bit contents are
IH,
IH
- 22 -
Page 23
LH28F320S3TD-L10
protected against alteration. A successful clear
block lock-bits operation requires WP# = V
attempted with WP# = V
IL, SR.1 and SR.5 will be
IH. If it is
set to "1" and the operation will fail. Clear block
lock-bits operation with V
IH < RP# produce spurious
results and should not be attempted.
If a clear block lock-bits operation is aborted due to
PP or VCC transition out of valid range or RP#
V
active transition, block lock-bit values are left in an
undetermined state. A repeat of clear block lock-bits
is required to initialize block lock-bit contents to
known values.
4.14 STS Configuration Command
The Status (STS) pin can be configured to different
states using the STS Configuration command.
Once the STS pin has been configured, it remains
in that configuration until another configuration
command is issued, the device is powered down or
RP# is set to V
after exit from deep power-down mode, the STS
pin defaults to RY/BY# operation where STS low
indicates that the WSM is busy. STS High Z
indicates that the WSM is ready for a new
operation.
To reconfigure the STS pin to other modes, the
STS Configuration is issued followed by the
appropriate configuration code. The three alternate
IL. Upon initial device power-up and
configurations are all pulse mode for use as a
system interrupt. The STS Configuration command
functions independently of the V
RP# must be V
Table 11 STS Configuration Coding Description
CONFIGURATION
BITS
00H
01H
02H
03H
IH.
Set STS pin to default level mode
(RY/BY#). RY/BY# in the default
level-mode of operation will indicate
WSM status condition.
Set STS pin to pulsed output signal
for specific erase operation. In this
mode, STS provides low pulse at the
completion of Block Erase, Bank
Erase and Clear Block Lock-Bits
operations.
Set STS pin to pulsed output signal
for a specific write operation. In this
mode, STS provides low pulse at the
completion of (Multi) Byte Write and
Set Block Lock-Bit operation.
Set STS pin to pulsed output signal
for specific write and erase operation.
STS provides low pulse at the
completion of Block Erase, Bank
Erase, (Multi) Word/Byte Write and
Block Lock-Bit Configuration operations.
PP voltage and
EFFECTS
Table 12 Write Protection Alternatives
OPERATION
Block Erase or0VIL or VIH Block Erase and (Multi) Word/Byte Write Enabled
(Multi) Word/Byte
WriteVIHBlock Lock-Bit Override. Block Erase and (Multi) Word/Byte Write Enabled
Bank Erase
Set Block Lock-BitX
Clear Block Lock-BitsX
BLOCK
LOCK-BIT
1
0, 1V
XVIHAll blocks are erased
WP#EFFECT
VILBlock is Locked. Block Erase and (Multi) Word/Byte Write Disabled
ILAll unlocked blocks are erased, locked blocks are not erased
(ECBLBS)
1 = Error in Erase or Clear Block Lock-Bits
0 = Successful Erase or Clear Block Lock-Bits
SR.4 =
WRITE AND SET BLOCK LOCK-BIT STATUS
(WSBLBS)
1 = Error in Write or Set Block Lock-Bit
0 = Successful Write or Set Block Lock-Bit
SR.3 = V
PP STATUS (VPPS)
PP Low Detect, Operation Abort
1= V
0= VPP OK
SR.2 = WRITE SUSPEND STATUS (WSS)
1 = Write Suspended
0 = Write in Progress/Completed
SR.1 = DEVICE PROTECT STATUS (DPS)
1 = Block Lock-Bit and/or WP# Lock Detected,
Operation Abort
0 = Unlock
SR.0 =
RESERVED FOR FUTURE ENHANCEMENTS (R)
NOTES :
Check STS or SR.7 to determine block erase, bank erase,
(multi) word/byte write or block lock-bit configuration
completion.
SR.6-0 are invalid while SR.7 = "0".
If both SR.5 and SR.4 are "1"s after a block erase, bank
erase, (multi) word/byte write, block lock-bit configuration or
STS configuration attempt, an improper command sequence
was entered.
SR.3 does not provide a continuous indication of V
The WSM interrogates and indicates the V
block erase, bank erase, (multi) word/byte write or block lockbit configuration command sequences. SR.3 is not guaranteed
to reports accurate feedback only when V
SR.1 does not provide a continuous indication of block lock-bit
values. The WSM interrogates block lock-bit, and WP# only
after block erase, bank erase, (multi) word/byte write or block
lock-bit configuration command sequences. It informs the
system, depending on the attempted operation, if the block
lock-bit is set and/or WP# is not V
configuration codes after writing the Read Identifier Codes
command indicates block lock-bit status.
SR.0 is reserved for future use and should be masked out
when polling the status register.
PP level only after
PP ≠ VPPH1/2/3.
IH. Reading the block lock
PP level.
Table 13.2 Extended Status Register Definition
SMSRRRRRRR
76543210
NOTES :
XSR.7 = STATE MACHINE STATUS (SMS)
1 = Multi Word/Byte Write available
0 = Multi Word/Byte Write not available
XSR.6-0 =
RESERVED FOR FUTURE ENHANCEMENTS (R)
After issue a Multi Word/Byte Write command : XSR.7
indicates that a next Multi Word/Byte Write command is
available.
XSR.6-0 are reserved for future use and should be masked
out when polling the extended status register.
- 24 -
Page 25
LH28F320S3TD-L10
Block Erase
Complete
Start
Write 70H
Read
Status Register
0
0
Yes
No
SR.7 =
1
SR.7 =
1
Write 20H,
Block Address
Write D0H,
Block Address
Suspend Block
Erase Loop
Read
Status Register
Full Status
Check if Desired
SR.3 =
FULL STATUS CHECK PROCEDURE
Read Status Register
Data (See Above)
V
PP Range Error
1
0
SR.1 =
Device Protect Error
1
0
BUS
OPERATION
COMMAND
COMMENTS
Standby
Standby
Check SR.1
1 = Device Protect Detect
WP# = VIL, Block Lock-Bit is Set
Only required for systems implementing block lock-bit configuration
Check SR.5
1 = Block Erase Error
SR.5, SR.4, SR.3 and SR.1 are only cleared by the Clear
Status Register command in cases where multiple blocks
are erased before full status is checked.
If error is detected, clear the status register before attempting
retry or other error recovery.
Block Erase
Successful
Repeat for subsequent block erasures.
Full status check can be done after each block erase or after
a sequence of block erasures.
Write FFH after the last block erase operation to place device
in read array mode.
SR.4, 5 =
Command Sequence
Error
1
0
SR.5 =
Block Erase
Error
1
0
Standby
Check SR.3
1 = V
PP Error Detect
Standby
Check SR.4, 5
Both 1 = Command Sequence Error
BUS
OPERATION
Write
Read
Standby
Standby
COMMAND
Read Status
Register
COMMENTS
Data = 70H
Addr = X
Status Register Data
Status Register Data
Check SR.7
1 = WSM Ready
0 = WSM Busy
Check SR.7
1 = WSM Ready
0 = WSM Busy
Erase
Confirm
Erase Setup
Write
Write
Read
Data = D0H
Addr = Within Block to be Erased
Data = 20H
Addr = Within Block to be Erased
Suspend
Block Erase
Fig. 3 Automated Block Erase Flowchart
- 25 -
Page 26
LH28F320S3TD-L10
Bank Erase
Complete
Start
Write 70H
Read
Status Register
0
0
SR.7 =
1
SR.7 =
1
Write 30H
Write D0H
Read
Status Register
Full Status
Check if Desired
SR.3 =
FULL STATUS CHECK PROCEDURE
Read Status Register
Data (See Above)
V
PP Range Error
1
0
SR.4, 5 =
Command Sequence
Error
1
0
BUS
OPERATION
COMMAND
COMMENTS
Standby
Check SR.5
1 = Bank Erase Error
SR.5, SR.4, SR.3 and SR.1 are only cleared by the Clear
Status Register command in cases where multiple blocks are
erased before full status is checked.
If error is detected, clear the status register before attempting
retry or other error recovery.
Bank Erase
Successful
Full full status check can be done after each bank erase.
Write FFH after the last bank erase operation to place bank
in read array mode.
SR.5 =
Bank Erase Error
1
0
Standby
Check SR.3
1 = V
PP Error Detect
Standby
Check SR.4, 5
Both 1 = Command Sequence Error
BUS
OPERATION
Write
Read
Standby
Standby
COMMAND
Read Status
Register
COMMENTS
Data = 70H
Addr = X
Status Register Data
Status Register Data
Check SR.7
1 = WSM Ready
0 = WSM Busy
Check SR.7
1 = WSM Ready
0 = WSM Busy
Bank Erase
Setup
Bank Erase
Setup
Write
Write
Read
Data = D0H
Addr = X
Data = 30H
Addr = X
Fig. 4 Automated Bank Erase Flowchart
- 26 -
Page 27
LH28F320S3TD-L10
Word/Byte Write
Complete
Start
Write 70H
Read
Status Register
0
0
Yes
No
SR.7 =
1
SR.7 =
1
Write 40H or 10H,
Address
Write Word/Byte
Data and Address
Suspend Word/Byte
Write Loop
Read
Status Register
Full Status
Check if Desired
BUS
OPERATION
COMMAND
COMMENTS
Standby
Check SR.1
1 = Device Protect Detect
WP# = V
IL, Block Lock-Bit is Set
Only required for systems implementing block lock-bit configuration
SR.4, SR.3 and SR.1 are only cleared by the Clear Status
Register command in cases where multiple locations are
written before full status is checked.
If error is detected, clear the status register before attempting
retry or other error recovery.
Repeat for subsequent word/byte writes.
SR full status check can be done after each word/byte write
or after a sequence of word/byte writes.
Write FFH after the last word/byte write operation to place
device in read array mode.
Standby
Check SR.3
1 = V
PP Error Detect
Standby
Check SR.4
1 = Data Write Error
BUS
OPERATION
Write
Read
Standby
Standby
COMMAND
Read Status
Register
COMMENTS
Data = 70H
Addr = X
Status Register Data
Status Register Data
Check SR.7
1 = WSM Ready
0 = WSM Busy
Check SR.7
1 = WSM Ready
0 = WSM Busy
Word/Byte
Write
Setup Word/
Byte Write
Write
Write
Read
Data = Data to be Written
Addr = Location to be Written
Data = 40H or 10H
Addr = Location to be Written
SR.3 =
FULL STATUS CHECK PROCEDURE
Read Status Register
Data (See Above)
V
PP Range Error
1
0
SR.1 =
Device Protect Error
1
0
Word/Byte Write
Successful
SR.4 =
Word/Byte Write
Error
1
0
Suspend
Word/Byte
Write
Fig. 5 Automated Word/Byte Write Flowchart
- 27 -
Page 28
LH28F320S3TD-L10
Start
Write E8H,
Start Address
Read
Status Register
0
XSR.7 =
1
Write Word or Byte Count (N)
_
1,
Start Address
Write Buffer
Start Address
X = 0
Write Buffer Data,
Device Address
NOTES :
1. Byte or word count values on DQ
0-7 are loaded into the
count register.
2. Write buffer contents will be programmed at the start
address.
3. Align the start address on a write buffer boundary for
maximum programming performance.
4. The device aborts the Multi Word/Byte Write command if
the current address is outside of the original block address.
5. The status register indicates an "improper command
sequence" if the Multi Word/Byte Write command is aborted.
Follow this with a Clear Status Register command.
SR full status check can be done after each multi word/byte
write or after a sequence of multi word/byte writes.
Write FFH after the last multi word/byte write operation to
place device in read array mode.
BUS
OPERATION
Write
Read
Standby
Write
(NOTE 1)
COMMAND
Setup Multi
Word/Byte Write
COMMENTS
Data = E8H
Addr = Start Address
Data = Word or Count (N)_1
Addr = Start Address
Write
(NOTE 2, 3)
Data = Buffer Data
Addr = Start Address
Write
(NOTE 4, 5)
Data = Buffer Data
Addr = Start Address
Write
Data = D0H
Addr = X
ReadStatus Register Data
Standby
Extended Status Register Data
Check SR.7
1 = WSM Ready
0 = WSM Busy
Multi Word/Byte
Write Abort
Yes
No
No
X = N
No
Write Buffer
Time-Out
Yes
Full Status
Check if Desired
SR.7 =
Multi Word/Byte
Write Complete
0
1
X = X + 1
Write D0H
Read
Status Register
Yes
No
Yes
No
Suspend Multi Word/Byte
Write Loop
Write Another
Block Address
Check XSR.7
1 = Multi Word/Byte Ready
0 = Multi Word/Byte Busy
Yes
Abort
Buffer Write
Command?
Another
Buffer
Write ?
Suspend
Multi Word/Byte
Write
Fig. 6 Automated Multi Word/Byte Write Flowchart
- 28 -
Page 29
LH28F320S3TD-L10
SR.3 =
FULL STATUS CHECK PROCEDURE FOR
MULTI WORD/BYTE WRITE OPERATION
Read Status Register
V
PP Range Error
1
0
SR.1 =
Device Protect Error
1
0
BUS
OPERATION
COMMAND
Standby
Check SR.1
1 = Device Protect Detect
WP# = VIL, Block Lock-Bit is Set
Only required for systems implementing block lock-bit configuration
SR.5, SR.4, SR.3 and SR.1 are only cleared by the Clear
Status Register command in cases where multiple locations
are written before full status is checked.
If error is detected, clear the status register before attempting
retry or other error recovery.
SR.4, 5 =
Command Sequence
Error
1
0
Multi Word/Byte Write
Successful
SR.4 =
Multi Word/Byte
Write Error
1
0
Standby
Check SR.3
1 = V
PP Error Detect
Standby
Check SR.4, 5
Both 1 = Command Sequence Error
Standby
Check SR.4
1 = Data Write Error
COMMENTS
Fig. 7 Full Status Check Procedure for Automated Multi Word/Byte Write
Repeat for subsequent block set operations.
Full status check can be done after each block lock-bit set
operation or after a sequence of block lock-bit set operations.
Write FFH after the last block lock-bit set operation to place
device in read array mode.
BUS
OPERATION
Write
Write
Read
Standby
COMMAND
Set Block
Lock-Bit Setup
COMMENTS
Data = 60H
Addr = Block Address
Data = 01H
Addr = Block Address
Status Register Data
Check SR.7
1 = WSM Ready
0 = WSM Busy
SR.3 =
FULL STATUS CHECK PROCEDURE
Read Status Register
Data (See Above)
V
PP Range Error
1
0
SR.1 =
Device Protect Error
1
0
BUS
OPERATION
COMMAND
COMMENTS
Standby
Standby
Check SR.1
1 = Device Protect Detect
WP# = V
IL
Check SR.4
1 = Set Block Lock-Bit Error
SR.5, SR.4, SR.3 and SR.1 are only cleared by the Clear
Status Register command in cases where multiple block
lock-bits are set before full status is checked.
If error is detected, clear the status register before attempting
retry or other error recovery.
Set Block
Lock-Bit Confirm
Set Block Lock-Bit
Successful
SR.4, 5 =
Command Sequence
Error
1
0
SR.4 =
Set Block Lock-Bit
Error
1
0
Standby
Check SR.3
1 = V
PP Error Detect
Standby
Check SR.4, 5
Both 1 = Command Sequence Error
Fig. 10 Set Block Lock-Bit Flowchart
- 32 -
Page 33
LH28F320S3TD-L10
Clear Block Lock-Bits
Complete
Start
Write 60H
Write D0H
Read
Status Register
0
SR.7 =
1
Full Status
Check if Desired
Write FFH after the last clear block lock-bits operation to
place device in read array mode.
BUS
OPERATION
Write
Write
Read
Standby
COMMAND
Clear Block
Lock-Bits
Setup
COMMENTS
Data = 60H
Addr = X
Data = D0H
Addr = X
Status Register Data
Check SR.7
1 = WSM Ready
0 = WSM Busy
SR.3 =
FULL STATUS CHECK PROCEDURE
Read Status Register
Data (See Above)
V
PP Range Error
1
0
SR.1 =
Device Protect Error
1
0
BUS
OPERATION
COMMAND
COMMENTS
Standby
Standby
Check SR.1
1 = Device Protect Detect
WP# = V
IL
Check SR.5
1 = Clear Block Lock-Bits Error
SR.5, SR.4, SR.3 and SR.1 are only cleared by the Clear
Status Register command.
If error is detected, clear the status register before attempting
retry or other error recovery.
Clear Block
Lock-Bits
Confirm
Clear Block Lock-Bits
Successful
SR.4, 5 =
Command Sequence
Error
1
0
SR.5 =
Clear Block Lock-Bits
Error
1
0
Standby
Check SR.3
1 = V
PP Error Detect
Standby
Check SR.4, 5
Both 1 = Command Sequence Error
Fig. 11 Clear Block Lock-Bits Flowchart
- 33 -
Page 34
5 DESIGN CONSIDERATIONS
5.1Three-Line Output Control
The device will often be used in large memory
arrays. SHARP provides three control inputs to
accommodate multiple memory connections. Threeline control provides for :
a. Lowest possible memory power consumption.
b. Complete assurance that data bus contention
will not occur.
To use these control inputs efficiently, an address
decoder should enable BE# while OE# should be
connected to all memory devices and the system’s
READ# control line. This assures that only selected
memory devices have active outputs while
deselected memory devices are in standby mode.
RP# should be connected to the system
POWERGOOD signal to prevent unintended writes
during system power transitions. POWERGOOD
should also toggle during system reset.
5.2STS and Block Erase, Bank Erase,
(Multi) Word/Byte Write and Block
Lock-Bit Configuration Polling
STS is an open drain output that should be
connected to V
hardware method of detecting block erase, bank
erase, (multi) word/byte write and block lock-bit
configuration completion. In default mode, it
transitions low after block erase, bank erase, (multi)
word/byte write or block lock-bit configuration
commands and returns to V
finished executing the internal algorithm. For
alternate STS pin configurations, see the Configuration command (Table 3 and Section 4.14 ).
STS can be connected to an interrupt input of the
system CPU or controller. It is active at all times.
STS, in default mode, is also High Z when the
device is in block erase suspend (with (multi)
word/byte write inactive), (multi) word/byte write
suspend or deep power-down modes.
CC by a pullup resistor to provide a
OH when the WSM has
LH28F320S3TD-L10
5.3Power Supply Decoupling
Flash memory power switching characteristics
require careful device decoupling. System
designers are interested in three supply current
issues; standby current levels, active current levels
and transient peaks produced by falling and rising
edges of BE# and OE#. Transient current
magnitudes depend on the device outputs’
capacitive and inductive loading. Two-line control
and proper decoupling capacitor selection will
suppress transient voltage peaks. Each device
should have a 0.1 µF ceramic capacitor connected
between its V
CC and GND and between its VPP
and GND. These high-frequency, low inductance
capacitors should be placed as close as possible to
package leads. Additionally, for every eight devices,
a 4.7 µF electrolytic capacitor should be placed at
the array’s power supply connection between V
CC
and GND. The bulk capacitor will overcome voltage
slumps caused by PC board trace inductance.
5.4VPP Trace on Printed Circuit Boards
Updating flash memories that reside in the target
system requires that the printed circuit board
designers pay attention to the V
trace. The V
PP pin supplies the memory cell current
PP power supply
for block erase, bank erase, (multi) word/byte write
and block lock-bit configuration. Use similar trace
widths and layout considerations given to the V
CC
power bus. Adequate VPP supply traces and
decoupling will decrease V
PP voltage spikes and
overshoots.
5.5VCC, VPP, RP# Transitions
Block erase, bank erase, (multi) word/byte write
and block lock-bit configuration are not guaranteed
if V
PP falls outside of a valid VPPH1/2/3 range, VCC
falls outside of a valid VCC1/2 range, or RP# = VIL.
PP error is detected, status register bit SR.3 is
If V
set to "1" along with SR.4 or SR.5, depending on
the attempted operation. If RP# transitions to V
during block erase, bank erase, (multi) word/byte
write or block lock-bit configuration, STS (if set to
IL
- 34 -
Page 35
LH28F320S3TD-L10
RY/BY# mode) will remain low until the reset
operation is complete. Then, the operation will abort
and the device will enter deep power-down. The
aborted operation may leave data partially altered.
Therefore, the command sequence must be
repeated after normal operation is restored. Device
power-off or RP# transitions to V
IL clear the status
register.
The CUI latches commands issued by system
software and is not altered by V
PP or BE#
transitions or WSM actions. Its state is read array
mode upon power-up, after exit from deep powerdown or after V
CC transitions below VLKO.
After block erase, bank erase, (multi) word/byte
write or block lock-bit configuration, even after V
PP
transitions down to VPPLK, the CUI must be placed
in read array mode via the Read Array command if
subsequent access to the memory array is desired.
5.6Power-Up/Down Protection
The device is designed to offer protection against
accidental block and bank erasure, (multi)
word/byte writing or block lock-bit configuration
during power transitions. Upon power-up, the
device is indifferent as to which power supply (V
or VCC) powers-up first. Internal circuitry resets the
CUI to read array mode at power-up.
PP
5.7Power Consumption
When designing portable systems, designers must
consider battery power consumption not only during
device operation, but also for data retention during
system idle time. Flash memory’s nonvolatility
increases usable battery life because data is
retained when system power is removed.
In addition, deep power-down mode ensures
extremely low power consumption even when
system power is applied. For example, portable
computing products and other power sensitive
applications that use an array of devices for solidstate storage can consume negligible power by
lowering RP# to V
access is again needed, the devices can be read
following the t
required after RP# is first raised to V
6.2.4 through 6.2.6 "AC CHARACTERISTICS READ-ONLY and WRITE OPERATIONS" and
Fig. 15, Fig. 16, Fig. 17 and Fig. 18 for more
information.
IL standby or sleep modes. If
PHQV and tPHWL wake-up cycles
IH. See Section
A system designer must guard against spurious
writes for V
CC voltages above VLKO when VPP is
active. Since both WE# and BE# must be low for a
command write, driving either to V
IH will inhibit
writes. The CUI’s two-step command sequence
architecture provides added level of protection
against data alteration.
In-system block lock and unlock capability prevents
inadvertent data alteration. The device is disabled
while RP# = V
IL regardless of its control inputs
state.
- 35 -
Page 36
LH28F320S3TD-L10
6 ELECTRICAL SPECIFICATIONS
6.1Absolute Maximum Ratings
Operating Temperature
During Read, Erase, Write and
...
Block Lock-Bit Configuration
Temperature under Bias
Storage Temperature
........................
Voltage On Any Pin
(except VCC, VPP)
VCC Supply Voltage
....
– 0.5 V to V
................
VPP Update Voltage during
Erase, Write and
Block Lock-Bit Configuration..– 0.2 to +7.0 V
Output Short Circuit Current
0 to +70°C
.............
– 65 to +125°C
CC+0.5 V
– 0.2 to +7.0 V
................
100 mA
–10 to +80°C
∗
(NOTE 1)
(NOTE 2)
(NOTE 2)
(NOTE 2)
(NOTE 3)
NOTICE : The specifications are subject to
change without notice. Verify with your local
SHARP sales office that you have the latest
datasheet before finalizing a design.
∗
WARNING : Stressing the device beyond the
"
Absolute Maximum Ratings" may cause
permanent damage. These are stress ratings only.
Operation beyond the "Operating Conditions" is not
recommended and extended exposure beyond the
"Operating Conditions" may affect device reliability.
NOTES :
1. Operating temperature is for commercial product defined
by this specification.
2. All specified voltages are with respect to GND. Minimum
DC voltage is – 0.5 V on input/output pins and –0.2 V on
V
CC and VPP pins. During transitions, this level may
undershoot to –2.0 V for periods < 20 ns. Maximum DC
voltage on input/output pins and V
which, during transitions, may overshoot to V
for periods < 20 ns.
3. Output shorted for no more than one second. No more
than one output shorted at a time.
CC is VCC+0.5 V
CC+2.0 V
6.2Operating Conditions
SYMBOL
TAOperating Temperature
VCC1VCC Supply Voltage (2.7 to 3.6 V) 2.73.6V
CC2VCC Supply Voltage (3.3±0.3 V) 3.03.6V
V
6.2.1 CAPACITANCE
SYMBOL
CINInput Capacitance21420pFVIN = 0.0 V
COUTOutput Capacitance1824pFVOUT = 0.0 V
NOTES :
1. Sampled, not 100% tested.
2. BE
0# and BE1L#, BE1H# have half the value of this.
PARAMETERMIN.MAX.UNITTEST CONDITION
0
(NOTE 1)
TA = +25˚C, f = 1 MHz
PARAMETERNOTETYP.MAX.UNITTEST CONDITION
+70
CAmbient Temperature
˚
- 36 -
Page 37
LH28F320S3TD-L10
TEST POINTSINPUTOUTPUT
1.35
1.35
2.7
0.0
1.5
1.5
3.0
0.0
TEST POINTSINPUTOUTPUT
DEVICE
UNDER
TEST
C
L Includes Jig
Capacitance
RL = 3.3 kΩ
C
L
OUT
1.3 V
1N914
6.2.2 AC INPUT/OUTPUT TEST CONDITIONS
AC test inputs are driven at 2.7 V for a Logic "1" and 0.0 V for a Logic "0". Input timing begins, and output
timing ends, at 1.35 V. Input rise and fall times (10% to 90%) < 10 ns.
Fig. 12 Transient Input/Output Reference Waveform for VCC = 2.7 to 3.6 V
AC test inputs are driven at 3.0 V for a Logic "1" and 0.0 V for a Logic "0". Input timing begins, and output
timing ends, at 1.5 V. Input rise and fall times (10% to 90%) < 10 ns.
Fig. 13 Transient Input/Output Reference Waveform for VCC = 3.3±0.3 V
Test Configuration Capacitance Loading Value
TEST CONFIGURATIONCL (pF)
CC = 3.3±0.3 V, 2.7 to 3.6 V50
V
Fig. 14 Transient Equivalent Testing
Load Circuit
- 37 -
Page 38
LH28F320S3TD-L10
6.2.3 DC CHARACTERISTICS
Following is the supply current of one bank. For the supply current of one device total, refer to NOTE 8.
SYMBOL
I
LIInput Load Capacitance1±0.5±0.5µA
LOOutput Leakage Capacitance1±0.5±0.5µA
I
PARAMETERNOTE
VCC= 2.7 to 3.6 V
TYP.MAX.TYP.MAX.
2010020100µAV
ICCSVCC Standby Current
1, 3,BE# = RP# = V
6, 8TTL Inputs
1414mAV
VCC Deep Power-Down
ICCD
CurrentIOUT (STS) = 0 mA
ICCRVCC Read Current
11515µA
1, 5, f = 5 MHz, I
6, 8TTL Inputs
VCC Write Current17——mA VPP = 2.7 to 3.6 V
ICCW((Multi) W/B Write or1, 7, 81717mA VPP = 3.3±0.3 V
Set Block Lock-Bit)1717mA VPP = 5.0±0.5 V
VCC Erase Current17——mA VPP = 2.7 to 3.6 V
ICCE(Block Erase, Bank Erase,1, 7, 81717mA VPP = 3.3±0.3 V
IPPW((Multi) W/B Write or1, 7, 88080mA VPP = 3.3±0.3 V
Set Block Lock-Bit)8080mA VPP = 5.0±0.5 V
VPP Erase Current40——mA VPP = 2.7 to 3.6 V
IPPE(Block Erase, Bank Erase,1, 7, 84040mA VPP = 3.3±0.3 V
Clear Block Lock-Bits)4040mA VPP = 5.0±0.5 V
I
PPWS VPP Write or Block Erase
IPPES Suspend Current
1, 81020010200µAV
VCC = 3.3±0.3 V
UNIT
2525mA
3030mA
TEST
CONDITIONS
CC = VCC Max.
V
VIN = VCC or GND
CC = VCC Max.
V
VOUT = VCC or GND
CMOS Inputs
CC = VCC Max.
CC±0.2 V
CC = VCC Max.
BE# = RP# = VIH
RP# = GND±0.2 V
CMOS Inputs
V
CC = VCC Max.
BE# = GND
OUT = 0 mA
V
CC = VCC Max.
BE# = V
IL
f = 5 MHz, IOUT = 0 mA
IH
PP = VPPH1/2/3
- 38 -
Page 39
6.2.3 DC CHARACTERISTICS (contd.)
SYMBOL
PARAMETERNOTE
VCC= 2.7 to 3.6 V
MIN.MAX.MIN.MAX.
VILInput Low Voltage7– 0.50.8–0.50.8V
V
IHInput High Voltage72.0
V
OLOutput Low Voltage3, 70.40.4V
Output High Voltage
V
OH1
(TTL)
3, 72.42.4V
0.850.85
Output High Voltage
VOH2
(CMOS)V
3, 7
VCCVCCIOH = –2.5 mA
CCVCC
– 0.4–0.4IOH = –100 µA
VPP Lockout Voltage
V
PPLK
during Normal Operations
VPP Voltage during Write
V
PPH1
or Erase Operations
VPP Voltage during Write
V
PPH2
or Erase Operations
VPP Voltage during Write
V
PPH3
or Erase Operations
LKO VCC Lockout Voltage2.02.0V
V
4, 71.51.5V
2.73.6V
3.03.63.03.6V
4.55.54.55.5V
NOTES :
1. All currents are in RMS unless otherwise noted. Typical
values at nominal V
2. I
CCWS and ICCES are specified with the device de-
selected. If reading or (multi) word/byte writing in erase
suspend mode, the device’s current draw is the sum of
CCWS or ICCES and ICCR or ICCW, respectively.
I
3. Includes STS.
4. Block erases, bank erases, (multi) word/byte writes and
block lock-bit configurations are inhibited when V
V
PPLK, and not guaranteed in the range between VPPLK
(max.) and VPPH1 (min.), between VPPH1 (max.) and
PPH2 (min.), between VPPH2 (max.) and VPPH3 (min.)
V
and above V
CC voltage and TA = +25°C.
PP ≤
PPH3 (max.).
VCC = 3.3±0.3 V
CC
V
+0.5+0.5
2.0
5. Automatic Power Saving (APS) reduces typical I
3 mA at 2.7 V and 3.3 V V
6. CMOS inputs are either V
inputs are either V
7. Sampled, not 100% tested.
8. These are the values of the current which is consumed
within one bank area. The value for the bank0 and
bank1 should added in order to calculate the value for
the whole chip. If the bank0 is in write state and bank1
is in read state, the I
in standby mode, the value for the device is 2 times the
value in the above table.
V
CC
IL or VIH.
LH28F320S3TD-L10
UNIT
V
CC = VCC Min.
V
IOL = 2 mA
VCC = VCC Min.
I
OH = –2.5 mA
VCC = VCC Min.
V
CC = VCC Min.
V
V
CC in static operation.
CC±0.2 V or GND±0.2 V. TTL
CC = ICCW + ICCR. If both banks are
TEST
CONDITIONS
CCR to
- 39 -
Page 40
LH28F320S3TD-L10
6.2.4 AC CHARACTERISTICS - READ-ONLY OPERATIONS
• VCC = 2.7 to 3.6 V, TA = 0 to +70˚C
(NOTE 1)
VERSIONLH28F320S3TD-L10
SYMBOL
PARAMETERNOTETYP.MAX.
tAVAVRead Cycle Time120ns
tAVQVAddress to Output Delay120ns
tELQVBE# to Output Delay2120ns
tPHQVRP# High to Output Delay600ns
tGLQVOE# to Output Delay250ns
tELQXBE# to Output in Low Z30ns
tEHQZBE# High to Output in High Z350ns
tGLQXOE# to Output in Low Z30ns
tGHQZOE# High to Output in High Z320ns
OH
t
t
FLQV
tFHQV
Output Hold from Address, BE# or OE# Change,
Whichever Occurs First
30ns
BYTE# to Output Delay3120ns
tFLQZBYTE# to Output in High Z330ns
t
ELFL
t
ELFH
BE# Low to BYTE# High or Low35ns
•VCC = 3.3±0.3 V, TA = 0 to +70˚C
VERSIONLH28F320S3TD-L10
SYMBOL
PARAMETERNOTETYP.MAX.
tAVAVRead Cycle Time100ns
tAVQVAddress to Output Delay100ns
tELQVBE# to Output Delay2100ns
tPHQVRP# High to Output Delay600ns
tGLQVOE# to Output Delay245ns
tELQXBE# to Output in Low Z30ns
tEHQZBE# High to Output in High Z350ns
tGLQXOE# to Output in Low Z30ns
tGHQZOE# High to Output in High Z320ns
t
OH
t
FLQV
tFHQV
Output Hold from Address, BE# or OE# Change,
Whichever Occurs First
30ns
BYTE# to Output Delay3100ns
tFLQZBYTE# to Output in High Z330ns
t
ELFL
ELFH
t
BE# Low to BYTE# High or Low35ns
NOTES :
1. See AC Input/Output Reference Waveform (Fig. 12 and Fig. 13) for maximum allowable input slew rate.
2. OE# may be delayed up to t
3. Sampled, not 100% tested.
ELQV-tGLQV after the falling edge of BE# without impact on tELQV.
UNIT
UNIT
- 40 -
Page 41
LH28F320S3TD-L10
ADDRESSES (A)
BE
X# (E)
OE# (G)
WE# (W)
DATA (D/Q)
RP# (P)
V
CC
VIL
VOH
VOL
VIH
VIH
VIH
VIH
VIH
VIL
VIL
VIL
VIL
Standby
Device
Address SelectionData Valid
Address Stable
High Z
Valid Output
High Z
t
GLQV
tELQV
tGLQX
tELQX
tAVQV
tPHQV
tAVAV
tEHQZ
tGHQZ
tOH
NOTE :
BEX# is defined as the latter of BE0# and BE1L#, BE1H# going Low or the first of BE0# and BE1L#, BE1H# going High.
Fig. 15 AC Waveform for Read Operations
- 41 -
Page 42
LH28F320S3TD-L10
ADDRESSES (A)
BE
X# (E)
OE# (G)
BYTE# (F)
DATA (D/Q)
(DQ
0-DQ7)
Standby
Device
Address SelectionData Valid
Address Stable
V
IL
VOH
VOL
VIH
VIH
VIH
VIH
VIL
VIL
VIL
DATA (D/Q)
(DQ
8-DQ15)
V
OH
VOL
High Z
Data Output
High Z
Valid
Output
High ZHigh Z
Data
Output
t
AVAV
tEHQZ
tGHQZ
tGLQV
tELQV
tGLQX
tELQX
tOH
tAVFL = tELFL
tFLQV = tAVQV
tFLQZ
tELFL
tAVQV
NOTE :
BEX# is defined as the latter of BE0# and BE1L#, BE1H# going Low or the first of BE0# and BE1L#, BE1H# going High.
Fig. 16 BYTE# Timing Waveforms
- 42 -
Page 43
LH28F320S3TD-L10
6.2.5 AC CHARACTERISTICS - WRITE OPERATIONS
• VCC = 2.7 to 3.6 V, TA = 0 to +70˚C
(NOTE 1)
VERSIONLH28F320S3TD-L10
SYMBOL
PARAMETERNOTEMIN.MAX.
tAVAVWrite Cycle Time120ns
tPHWLRP# High Recovery to WE# Going Low21µs
tELWLBE# Setup to WE# Going Low10ns
tWLWHWE# Pulse Width50ns
tSHWHWP# VIH Setup to WE# Going High2100ns
tVPWHVPP Setup to WE# Going High2100ns
tAVWHAddress Setup to WE# Going High350ns
tDVWHData Setup to WE# Going High350ns
tWHDXData Hold from WE# High5ns
tWHAXAddress Hold from WE# High5ns
tWHEHBE# Hold from WE# High10ns
tWHWLWE# Pulse Width High30ns
tWHRLWE# High to STS Going Low100ns
tWHGLWrite Recovery before Read0ns
tQVVLVPP Hold from Valid SRD, STS High Z2, 40ns
t
QVSLWP# VIH Hold from Valid SRD, STS High Z2, 40ns
•VCC = 3.3±0.3 V, TA = 0 to +70˚C
VERSIONLH28F320S3TD-L10
SYMBOL
PARAMETERNOTEMIN.MAX.
tAVAVWrite Cycle Time100ns
tPHWLRP# High Recovery to WE# Going Low21µs
tELWLBE# Setup to WE# Going Low10ns
tWLWHWE# Pulse Width50ns
tSHWHWP# VIH Setup to WE# Going High2100ns
tVPWHVPP Setup to WE# Going High2100ns
tAVWHAddress Setup to WE# Going High350ns
tDVWHData Setup to WE# Going High350ns
tWHDXData Hold from WE# High5ns
tWHAXAddress Hold from WE# High5ns
tWHEHBE# Hold from WE# High10ns
tWHWLWE# Pulse Width High30ns
tWHRLWE# High to STS Going Low100ns
tWHGLWrite Recovery before Read0ns
tQVVLVPP Hold from Valid SRD, STS High Z2, 40ns
t
QVSLWP# VIH Hold from Valid SRD, STS High Z2, 40ns
NOTES :
1. Read timing characteristics during block erase, bank
erase, (multi) word/byte write and block lock-bit
configuration operations are the same as during readonly operations. Refer to Section 6.2.4 "ACCHARACTERISTICS" for read-only operations.
2. Sampled, not 100% tested.
3. Refer to Table 3 for valid A
bank erase, (multi) word/byte write or block lock-bit
configuration.
4. V
PP should be held at VPPH1/2/3 until determination of
block erase, bank erase, (multi) word/byte write or block
lock-bit configuration success (SR.1/3/4/5 = 0).
IN and DIN for block erase,
UNIT
UNIT
- 43 -
Page 44
(NOTE 1) (NOTE 2)(NOTE 3)(NOTE 4)(NOTE 5)(NOTE 6)
VIL
VIH
High Z
V
IH
VIH
VIH
VIL
VIL
VIL
VOL
VIL
VIH
VIL
VPPLK
VPPH1/2/3
VIH
VIL
ADDRESSES (A)
BEX# (E)
OE# (G)
WE# (W)
DATA (D/Q)
RP# (P)
VPP (V)
STS (R)
WP# (S)
VIL
VIH
AINAIN
tAVAVtAVWH
tELWLtWHEH
tWHGL
tWHWL
tWHQV1/2/3/4
tWLWH
tDVWH
tWHDX
Valid
SRD
t
PHWL
tWHRL
tVPWH
tQVVL
DIN
DIN
High Z
DIN
tSHWHtQVSL
tWHAX
NOTES :
1. VCC power-up and standby.
2. Write erase or write setup.
3. Write erase confirm or valid address and data.
4. Automated erase or program delay.
5. Read status register data.
6. Write Read Array command.
7. B E
High.
X# is defined as the latter of BE0# and BE1L#, BE1H# going Low or the first of BE0# and BE1L#, BE1H# going
Fig. 17 AC Waveform for WE#-Controlled Write Operations
LH28F320S3TD-L10
- 44 -
Page 45
LH28F320S3TD-L10
6.2.6 ALTERNATIVE BE#-CONTROLLED WRITES
(NOTE 1)
•VCC = 2.7 to 3.6 V, TA = 0 to +70˚C
VERSIONLH28F320S3TD-L10
SYMBOL
PARAMETERNOTEMIN.MAX.
tAVAVWrite Cycle Time120ns
tPHELRP# High Recovery to BE# Going Low21µs
tWLELWE# Setup to BE# Going Low0ns
tELEHBE# Pulse Width70ns
tSHEHWP# VIH Setup to BE# Going High2100ns
tVPEHVPP Setup to BE# Going High2100ns
tAVEHAddress Setup to BE# Going High350ns
tDVEHData Setup to BE# Going High350ns
tEHDXData Hold from BE# High5ns
tEHAXAddress Hold from BE# High5ns
tEHWHWE# Hold from BE# High0ns
tEHELBE# Pulse Width High25ns
tEHRLBE# High to STS Going Low100ns
tEHGLWrite Recovery before Read0ns
tQVVLVPP Hold from Valid SRD, STS High Z2, 40ns
t
QVSLWP# VIH Hold from Valid SRD, STS High Z2, 40ns
•V
CC = 3.3±0.3 V, TA = 0 to +70˚C
VERSIONLH28F320S3TD-L10
SYMBOL
PARAMETERNOTEMIN.MAX.
tAVAVWrite Cycle Time100ns
tPHELRP# High Recovery to BE# Going Low21µs
tWLELWE# Setup to BE# Going Low0ns
tELEHBE# Pulse Width70ns
tSHEHWP# VIH Setup to BE# Going High2100ns
tVPEHVPP Setup to BE# Going High2100ns
tAVEHAddress Setup to BE# Going High350ns
tDVEHData Setup to BE# Going High350ns
tEHDXData Hold from BE# High5ns
tEHAXAddress Hold from BE# High5ns
tEHWHWE# Hold from BE# High0ns
tEHELBE# Pulse Width High25ns
tEHGLBE# High to STS Going Low100ns
tEHRLWrite Recovery before Read0ns
tQVVLVPP Hold from Valid SRD, STS High Z2, 40ns
t
QVSLWP# VIH Hold from Valid SRD, STS High Z2, 40ns
NOTES :
1. In systems where BE# defines the write pulse width
(within a longer WE# timing waveform), all setup, hold
and inactive WE# times should be measured relative to
the BE# waveform.
2. Sampled, not 100% tested.
3. Refer to Table 3 for valid A
bank erase, (multi) word/byte write or block lock-bit
configuration.
PP should be held at VPPH1/2/3 until determination of
4. V
block erase, bank erase, (multi) word/byte write or block
lock-bit configuration success (SR.1/3/4/5 = 0).
IN and DIN for block erase,
UNIT
UNIT
- 45 -
Page 46
(NOTE 1) (NOTE 2)(NOTE 3)(NOTE 4)(NOTE 5)(NOTE 6)
VIL
VIH
High Z
V
IH
VIH
VIH
VIL
VIL
VIL
VOL
VIL
VIH
VIL
VPPLK
VPPH1/2/3
VIH
VIL
ADDRESSES (A)
WE# (W)
OE# (G)
BEX# (E)
DATA (D/Q)
RP# (P)
VPP (V)
STS (R)
WP# (S)
VIL
VIH
AINAIN
tAVAVtAVEH
tWLELtEHWH
tEHGL
tEHEL
tEHQV1/2/3/4
tELEH
tDVEH
tEHDX
Valid
SRD
t
PHEL
tEHRL
tVPEH
tQVVL
DIN
DIN
High Z
DIN
tSHEHtQVSL
tEHAX
NOTES :
1. VCC power-up and standby.
2. Write erase or write setup.
3. Write erase confirm or valid address and data.
4. Automated erase or program delay.
5. Read status register data.
6. Write Read Array command.
7. B E
High.
X# is defined as the latter of BE0# and BE1L#, BE1H# going Low or the first of BE0# and BE1L#, BE1H# going
LH28F320S3TD-L10
Fig. 18 AC Waveform for BE#-Controlled Write Operations
- 46 -
Page 47
RP# (P)
V
IL
(A) Reset During Read Array Mode
(B) Reset During Block Erase, Bank Erase, (Multi) Word/Byte Write
V
IH
High Z
V
IH
High Z
V
OL
VIL
VOL
STS (R)
STS (R)
RP# (P)
VIL
VIH
RP# (P)
V
IL
VCC
2.7 V/3.3 V
or Block Lock-Bit Configuration
(C) V
CC Power Up Timing
tPLPH
tPLRH
tPLPH
t23VPH
6.2.7 RESET OPERATIONS
LH28F320S3TD-L10
Fig. 19 AC Waveform for Reset Operation
SYMBOL
t
t
RP# Pulse Low Time (If RP# is tied to VCC,
PLPH
this specification is not applicable)
RP# Low to Reset during Block Erase,
1. If RP# is asserted while a block erase, bank erase,
VCC 2.7 V to RP# High
CC 3.0 V to RP# High
V
(multi) word/byte write or block lock-bit configuration
operation is not executing, the reset will complete within
100 ns.
2. A reset time, t
going High Z or RP# going high until outputs are valid.
PHQV, is required from the latter of STS
3100100ns
3. When the device power-up, holding RP#-low minimum
100 ns is required after V
CC has been in predefined
range and also has been in stable there.
- 47 -
UNIT
Page 48
LH28F320S3TD-L10
6.2.8 BLOCK ERASE, BANK ERASE, (MULTI) WORD/BYTE WRITE AND BLOCK LOCK-BIT
CONFIGURATION PERFORMANCE
•VCC = 2.7 to 3.6 V, TA = 0 to +70˚C
SYMBOL
WHQV1
t
EHQV1
t
WHQV1
t
EHQV1
t
tWHQV2
tEHQV2
tWHQV3 Set Block Lock-Bit
tEHQV3 Time
tWHQV4 Clear Block Lock-Bits
tEHQV4 Time
WHRH1 Write Suspend Latency
t
tEHRH1 Time to Read
WHRH2
t
EHRH2Time to Read
t
NOTES :
1. Typical values measured at TA = +25˚C and nominal
voltages. Assumes corresponding block lock-bits are not
set. Subject to change based on device characterization.
PARAMETERNOTE
MIN.
Word/Byte Write Time
(using W/B write, 222.1722.1713.2µs
in word mode)
Word/Byte Write Time
(using W/B write, 219.8919.8913.2µs
in byte mode)
Word/Byte Write Time
(using multi word/byte25.765.762.76µs
write)
Block Write Time
(using W/B write, 20.910.910.44s
in word mode)
Block Write Time
(using W/B write, 21.631.630.87s
in byte mode)
Block Write Time
(using multi word/byte 20.370.370.18s
write)
Block Erase Time20.560.560.42s
Bank Erase Time17.917.913.3s
222.1722.1713.2µs
20.560.560.42s
Erase Suspend Latency
(NOTE 3)
VPP = 2.7 to 3.6 VVPP = 3.3±0.3 VVPP = 5.0±0.5 V
TYP.
(NOTE 1)
MAX. MIN.
TYP.
(NOTE 1)
MAX. MIN.
TYP.
(NOTE 1)
MAX.
7.2410.27.2410.26.739.48µs
15.521.515.521.512.54 17.54µs
2. Excludes system-level overhead.
3. Sampled, not 100% tested.
UNIT
- 48 -
Page 49
LH28F320S3TD-L10
6.2.8 BLOCK ERASE, BANK ERASE, (MULTI) WORD/BYTE WRITE AND BLOCK LOCK-BIT
CONFIGURATION PERFORMANCE (contd.)
•VCC = 3.3±0.3 V, TA = 0 to +70˚C
SYMBOL
t
WHQV1 Word/Byte Write Time
tEHQV1 (using W/B write, in word mode)
WHQV1 Word/Byte Write Time
t
tEHQV1 (using W/B write, in byte mode)
Word/Byte Write Time
(using multi word/byte write)
Block Write Time
(using W/B write, in word mode)
Block Write Time
(using W/B write, in byte mode)
Block Write Time
(using multi word/byte write)
WHQV2
t
tEHQV2
Block Erase Time20.550.41s
Bank Erase Time17.613.1s
WHQV3
t
tEHQV3
tWHQV4
tEHQV4
tWHRH1
tEHRH1
tWHRH2
EHRH2
t
Set Block Lock-Bit Time221.7512.95µs
Clear Block Lock-Bits Time20.550.41s
Write Suspend Latency Time to Read7.1106.69.3µs
Erase Suspend Latency Time to Read15.221.112.317.2µs
NOTES :
1. Typical values measured at TA = +25˚C and nominal
voltages. Assumes corresponding block lock-bits are not
set. Subject to change based on device characterization.