HY29DS162 Datasheet, PDF (21/48 Pages) Hynix Semiconductor – 16 Megabit (2M x 8/1M x 16) Super-Low Voltage, Dual Bank, Simultaneous Read/Write, Flash Memory

HY29DS162/HY29DS163
quires the bank address, causes the erase opera-
tion to be suspended in all sectors designated for
erasure in the specified bank. This command is
valid only during the sector erase operation, in-
cluding during the 50 µs time-out period at the end
of the command sequence, and is ignored if it is
issued during chip erase or programming opera-
tions.
The HY29DS16x requires a maximum of 20 µs to
suspend the erase operation if the erase suspend
command is issued during active sector erasure.
However, if the command is written during the
sector erase time-out, the time-out is terminated
and the erase operation is suspended immediately.
Once the erase operation has been suspended in
the bank, the system can read array data from or
program data into any sector in that bank that is
not designated for erasure. Normal read and write
timings and command definitions apply. Reading
at any address within erase-suspended sectors
produces status data on DQ[7:0]. The host can
use DQ[7], or DQ[6] and DQ[2] together, to deter-
mine if a sector is actively erasing or is erase-sus-
pended. See ‘Write Operation Status’ for infor-
mation on these status bits.
After an erase-suspended program operation is
complete, the bank returns to the erase-suspended
read state and the host can initiate another pro-
gramming operation (or read operation) within non-
suspended sectors. The host can determine the
status of a program operation during the erase-
suspended state just as in the standard program-
ming operation.
The host may also write the Electronic ID com-
mand sequence when the bank is in the Erase
Suspend mode. The device allows reading Elec-
tronic ID codes even at addresses within erasing
sectors, since the codes are not stored in the
memory array. When the device exits the Elec-
tronic ID mode, the bank reverts to the Erase Sus-
pend mode, and is ready for another valid opera-
tion. See the Electronic ID Command section for
more information.
The system must write the Erase Resume com-
mand to the erase-suspended bank to exit the
Erase Suspend mode and continue the sector
erase operation. Further writes of the Resume
command are ignored. Another Erase Suspend
command can be written after the device has re-
sumed erasing.
Table 11 summarizes the erase operations in the
HY29DS16x.
Electronic ID Command
The Electronic ID mode provides manufacturer and
device identification and sector protection verifi-
cation through identifier codes output on DQ[7:0].
This mode is intended primarily for programming
equipment to automatically match a device to be
programmed with its corresponding programming
algorithm.
Table 11. HY29DS16x Erase Operations Summary ⁷
Erase Suspend Programming
Allowed?
Allowed? ¹
Output from Read Operation ³
ES Sector ⁴ Non-ES Sector ⁵
Operation in Progress
Bank 1 Bank 2 Bank 1 Bank 2 Bank 1 Bank 2 Bank 1 Bank 2
No erase
n/a
n/a
Yes
Yes
n/a
n/a
Data Data
Chip Erase
No
No
No
No
n/a
n/a Status Status
Sector Erase in Bank 1 Only
Yes
No
Yes ² Yes ⁶ Status n/a
Data Data
Sector Erase in Bank 2 Only
No
Yes
Yes ⁶ Yes ²
n/a Status Data Data
Sector Erase in Banks 1 and 2 Yes
Yes Yes ² Yes ² Status Status Data Data
Notes:
1. Only one simultaneous programming operation is permitted.
2. Allowed only when the bank is in erase suspend state and only into a sector that is not designated for erasure.
3. Output may differ if program operation is in progress. See Write Operation Status section for additional information.
4. Read from a sector that is designated for erasure while the bank is in erase suspend state.
5. Read from a sector that is not designated for erasure while the bank is in erase suspend state, or read from any sector
in a bank where an erase operation has not been commanded, or any read for the Chip Erase operation.
6. Erase operation in other bank must be suspended.
7. n/a = not applicable. Condition cannot exist.
Data = array data from addressed location.
Status = write operation status (see Write Operation Status section for additional information).
r1.3/Apr 01
21