ES29LV160F Datasheet, PDF (38/71 Pages) Excel Semiconductor Inc. – 16 Megabit (2 M x 8-Bit/1 M x 16-Bit) CMOS 3.0 Volt-only Boot Sector Flash Memory

ES29LV160F
Excel Semiconductor Inc.
11.6 DQ5: Exceeded Timing Limits
DQ5 indicates whether the program or erase time has exceeded a specified internal pulse count
limit. Under these conditions DQ5 produces a 1. This is a failure condition that indicates the
program or erase cycle was not successfully completed.
The DQ5 failure condition may appear if the system tries to program a 1 to a location that is
previously programmed to 0. Only an erase operation can change a 0 back to a 1. Under this
condition, the device halts the operation, and when the operation has exceeded the timing limits,
DQ5 produces a 1.
Under both these conditions, the system must issue the reset command to return the device to
reading array data.
11.7 DQ3: Sector Erase Timer
After writing a sector erase command sequence, the system may read DQ3 to determine whether
or not an erase operation has begun. (The sector erase timer does not apply to the chip erase
command.) If additional sectors are selected for erasure, the entire time-out also applies after each
additional sector erase command. When the time-out is complete, DQ3 switches from 0 to 1. The
system may ignore DQ3 if the system can guarantee that the time between additional sector erase
commands will always be less than 50 μs. See also Sector Erase Command Sequence on page 29.
After the sector erase command sequence is written, the system should read the status on DQ7
(Data# Polling) or DQ6 (Toggle Bit I) to ensure the device has accepted the command sequence,
and then read DQ3. If DQ3 is 1, the internally controlled erase cycle has begun; all further
commands (other than Erase Suspend) are ignored until the erase operation is complete. If DQ3 is
0, the device will accept additional sector erase commands. To ensure the command has been
accepted, the system software should check the status of DQ3 prior to and following each
subsequent sector erase command. If DQ3 is high on the second status check, the last command
might not have been accepted. Table 11.1 shows the outputs for DQ3.
Table 11.1 Write Operation Status
Standard
Mode
Erase
Suspend
Mode
Operation
Embedded Program
Algorithm
Embedded Erase
Algorithm
Reading within Erase
Suspended Sector
DQ7
(Note 2)
DQ7#
0
1
Reading within Non-Erase
Suspended Sector
Data
Erase-Suspend-Program
DQ7#
DQ6
Toggle
DQ5
(Note 1)
0
Toggle
0
No
toggle
0
Data
Data
Toggle
0
DQ3
N/A
1
N/A
Data
N/A
DQ2
(Note 2)
No toggle
RY/BY#
0
Toggle
0
Toggle
1
Data
1
N/A
0
Rev.0A (Dec 12, 2007) 38