HY29LV160 Hynix Semiconductor, HY29LV160 Datasheet - Page 16

• Manufacturer Part Number: HY29LV160
• Description: 16 Mbit (2M x 8/1M x 16) Low Voltage Flash Memory
• Manufacturer: Hynix Semiconductor

HY29LV160
even if specified for erasure, is not affected by the
sector erase operation.
The Sector Erase command sequence starts the
Automatic Erase algorithm, which preprograms
and verifies the specified unprotected sectors for
an all zero data pattern prior to electrical erase.
The device then provides the required number of
internally generated erase pulses and verifies cell
erasure within the proper cell margins. The host
system is not required to provide any controls or
timings during these operations.
After the sector erase data cycle (the sixth bus
cycle) of the command sequence is issued, a sec-
tor erase time-out of 50 µs, measured from the
rising edge of the final WE# pulse in that bus cycle,
begins. During this time-out window, an additional
sector erase data cycle, specifying the sector ad-
dress of another sector to be erased, may be writ-
ten into an internal sector erase buffer. This buffer
may be loaded in any sequence, and the number
of sectors specified may be from one sector to all
sectors. The only restriction is that the time be-
tween these additional data cycles must be less
than 50 µs, otherwise erasure may begin before
the last data cycle is accepted. To ensure that all
data cycles are accepted, it is recommended that
host processor interrupts be disabled during the
16
Address for Erase Operation
Setup First (or Next) Sector
Write Last Cycle (SA/0x30)
Write First Five Cycles of
Command Sequence
Command Sequence
of SECTOR ERASE
Additional Sector?
SECTOR ERASE
Erase An
START
N O
YES
Time-out (DQ[3])
Sector Erase
Expired?
Figure 6. Sector Erase Procedure
N O
YES
time that the additional cycles are being issued
and then be re-enabled afterwards.
If all sectors specified for erasing are protected,
the device returns to reading array data after ap-
proximately 100 µs. If at least one specified sec-
tor is not protected, the erase operation erases
the unprotected sectors, and ignores the command
for the sectors that are protected.
The system can monitor DQ[3] to determine if the
50 µs sector erase time-out has expired, as de-
scribed in the Write Operation Status section. If
the time between additional sector erase data
cycles can be insured to be less than the time-
out, the system need not monitor DQ[3].
Any command other than Sector Erase or Erase
Suspend during the time-out period resets the
device to reading array data. The system must
then rewrite the command sequence, including any
additional sector erase data cycles. Once the sec-
tor erase operation itself has begun, only the Erase
Suspend command is valid. All other commands
are ignored.
As for the Chip Erase command, note that a hard-
ware reset immediately terminates the sector
erase operation. To ensure data integrity, the
(See Write Operation Status
ERASE COMPLETE
Check Erase Status
this erase cycle must be erased
but which were not specified in
Sectors which require erasure
Section)
later using a new command
Normal Exit
sequence
DQ[5] Error Exit
ERROR RECOVERY
GO TO
Rev. 1.2/May 01