10
P/N:PM0604 REV. 0.9.1, NOV. 21, 2002
MX29L1611G
SECTOR ERASE
Sector erase is a six-bus cycle operation. There are two
"unlock" write cycles. These are followed b y writing the
set-up command-80H. Two more "unloc k" write cycles
are then followed by the sector erase command-30H.
The sector address is latched on the falling edge of CE,
while the command (data) is latched on the rising edge
of CE.
Sector erase does not require the user to program the
device prior to erase. The system is not required to
provide any controls or timings during these operations.
The automatic sector erase begins on the rising edge of
the last CE pulse in the command sequence and termi-
nates when the status on Q7 is "1" at which time the
device stays at read status register mode. The device
remains enabled for read status register mode until the
CIR contents are altered by a valid command
sequence.(Refer to table 3,6 and Figure 3,4,6,8)
A19 A18 A17 A 16 A15 Address Range
[A19, -1]
SA0 0 0 0 0 0 000000H--00FFFFH
SA1 0 0 0 0 1 010000H--01FFFFH
SA2 0 0 0 1 0 020000H--02FFFFH
SA3 0 0 0 1 1 030000H--03FFFFH
SA4 0 0 1 0 0 040000H--04FFFFH
... ... ... ... ... ................................
SA31 1 1 1 1 1 1F0000H--1FFFFFH
Table 5. MX29L1611G Sector Address Table
(Byte-Wide Mode)
READ STATUS REGISTER
The MXIC's 16 Mbit flash family contains a status reg-
ister which may be read to determine when a program or
erase operation is complete, and whether that operation
completed successfully. The status register may be read
at any time by writing the Read Status command to the
CIR. After writing this command, all subsequent read
operations output data from the status register until an-
other valid command sequence is written to the CIR. A
Read Array command must be written to the CIR to re-
turn to the Read Array mode.
The status register bits are output on Q3 - Q7 (table 6)
whether the device is in the byte-wide (x8) or word-wide
(x16) mode for the MX29L1611G. In the word-wide mode
the upper byte, Q(8:15) is set to 00H during a Read Sta-
tus command. In the byte-wide mode, Q(8:14) are tri-
stated and Q15/A-1 retains the low order address func-
tion.
It should be noted that the contents of the status regis-
ter are latched on the falling edge of OE or CE which-
ever occurs last in the read cycle. This prevents pos-
sible bus errors which might occur if the contents of the
status register change while reading the status register .
CE or OE must be toggled with each subsequent status
read, or the completion of a program or erase operation
will not be evident.
The Status Register is the interface between the micro-
processor and the Write State Machine (WSM). When
the WSM is active, this register will indicate the status
of the WSM, and will also hold the bits indicating whether
or not the WSM was successful in perfor ming the de-
sired operation. The WSM sets status bits f our through
seven and clears bits six and seven, but cannot clear
status bits four and five. If Erase fail or Program fail
status bit is detected, the Status Register is not cleared
until the Clear Status Register command is written. The
MX29L1611G automatically outputs Status Register data
when read after Chip Erase, Sector Erase, Page Pro-
gram or Read Status Command write cycle. The default
state of the Status Register after power-up and return
from deep power-down mode is (Q7, Q6, Q5, Q4) =
1000B. Q3 = 0 or 1 depends on sector-protect status,
can not be changed by Clear Status Register Command
or Write State Machine.
"unlock" write cycles. These are follo wed b y writing the
"set-up" command-80H. Two more "unlock" write cycles
are then followed by the chip erase command-10H.
Chip erase does not require the user to program the de-
vice prior to erase.
The automatic erase begins on the rising edge of the
last CE pulse in the command sequence and terminates
when the status on Q7 is "1" at which time the device
sta ys at read status register mode. The device remains
enabled for read status register mode until the CIR con-
tents are altered by a valid command sequence. (Refer
to table 3,6 and Figure 2,6,8)