- 8 -
LH28F800SG-L/SGH-L (FOR TSOP, CSP)
RP# and WP#. CE# and OE# must be driven
active to obtain data at the outputs. CE# is the
device selection control, and when active enables
the selected memory device. OE# is the data
output (DQ
0
-DQ
15
) control and when active drives
the selected memory data onto the I/O bus. WE#
must be at V
IH
and RP# must be at V
IH
or V
HH
.
Fig. 13
illustrates read cycle.
3.2
With OE# at a logic-high level (V
IH
), the device
outputs are disabled. Output pins DQ
0
-DQ
15
are
placed in a high-impedance state.
Output Disable
3.3
CE# at a logic-high level (V
IH
) places the device in
standby mode which substantially reduces device
power consumption. DQ
0
-DQ
15
outputs are placed
in a high-impedance state independent of OE#. If
deselected during block erase, word write, or lock-
bit configuration, the device continues functioning,
and consuming active power until the operation
completes.
Standby
3.4
RP# at V
IL
initiates the deep power-down mode.
Deep Power-Down
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
PHQV
is required
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, word write, or lock-bit
configuration modes, RP#-low will abort the
operation. RY/BY# 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
PHWL
is required
after RP# goes to logic-high (V
IH
) before another
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,
word write, or lock-bit configuration modes. 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.