MX29VW160T/B
20
P/N:PM0567 REV. 0.9.4, JUN. 06, 2001
If a program address falls within a protected block, Q6
toggles for approximately 1us after the program
command sequence is written, then returns to reading
arra y data.
Q6 also toggles during the erase-suspend-program
mode, and stops toggling once the A utomatic Prog r am
algorithm is complete.
Table 5 shows the outputs for Toggle Bit I on Q6.
Q2: Toggle Bit II
The Toggle Bit II on Q2, when used with Q6, indicates
whether a particular bloc k is actively erasing (that is the
Automatic Erase algorithm is in process), or whether
that bloc k is erase-suspended. Toggle Bit II is valid after
the rising edge of the final WE pulse in the command
sequence.
Q2 toggles when the system reads at addresses within
those blocks that have been selected for erasure. (The
system may use either OE or CE to control the read
cycles.) But Q2 cannot distinguish whether the b loc k is
actively erasing or is erase-suspended. Q6, by compari-
son, indicates whether the device is actively erasing or
is erase-suspended, but cannot distinguish which blocks
are selected for erasure. Thus, both status bits are re-
quired f or blocks and mode inf ormation. Refer to table 5
to compare outputs for Q2 and Q6.
Reading Toggle Bits Q6/Q2
Whene ver the system initially begins reading toggle bit
status, it must read Q7~Q0 at least twice in a row to
determine whether a toggle bit is toggling. Typically, the
system would note and store the value of the toggle bit
after the first read. After the second read, the system
would compare the new value of the toggle bit with the
first. If the toggle bit is not toggling, the de vice has com-
pleted the progr am or erase operation. The system can
read arra y data on Q7~Q0 on the f ollo wing read cycle .
However, if after the initial two read cycles, the system
determines that the toggle bit is still toggling, the system
also should note whether the value of Q5 is high (see
the section on Q5). If it is, the system should then deter-
mine again whether the toggle bit is toggling, since the
toggle bit may have stopped toggling just as Q5 went
high. If it is still toggling, the device did not complete the
operation successfully, and the system must write the
reset command to return to reading arra y data.
The remaining scenario is that system initially determines
that the toggle bit is toggling and Q5 has not gone high.
The system may continue to monitor the toggle bit and
Q5 through successive read cycles, determining the sta-
tus as described in the previous paragraph. Alternatively,
it may choose to perform other system tasks. In this case,
the system must start at the beginning of the algorithm
when it returns to determine the status of the operation.
Q5: Exceeded Timing Limits
Q5 will indicate if the program or erase time has
exceeded the specified limits (internal pulse count).
Under these conditions Q5 will produce a "1" This is a
time-out condition which indicates that the program or
erase cycle was not successfully completed. Data
P olling and T oggle Bit are the only operating functions of
the device under this condition.
If this time-out condition occurs during block erase op-
eration, it is specifiesd that a particular block is bad and
it may not be reused. However , other blocks are still func-
tional and may be used f or progr am or erase operation.
The device m ust be reset to use other b locks. Write the
Reset command sequence to the device, and then ex -
ecute program or erase command sequence. This al-
lows the system to continue to use the other active blocks
in the device .
If this time-out condition occurs during the chip erase
operation, it specifies that the entire chip is bad or com-
bination of bloc ks are bad.
The Q5 time-out condition may also appear if a user
tries to program a non b lank location without erasing. In
this case the device locks out and ne v er completes the
Automatic algorithm operation. Hence, the system never
reads a valid data on Q7 bit and Q6 never stops
toggling. Once the device has exceeded timing limits,
the Q5 bit will indicate a logical "1" Please note that this
is not a device failure condition since the device was
incorrectly used.