Am29LV004 17
PRELIMINARY
RY/BY#: Ready/Busy#
The RY/BY# is a dedicated, open-drain output pin that
indicates whether an Embedded Algorithm is in
progress or complete. The RY/BY# status is valid after
the rising edge of the final WE# pu lse in the command
sequence. Since RY/BY# is an open-drain output, sev-
eral RY/BY# pins can be tied together in parallel with a
pull-up resistor to VCC.
If the output is low (Busy), the device is actively erasing
or programming. (This includes programming in the
Erase Suspend mode.) If the output is high (Ready),
the device is ready to read array data (including during
the Erase Suspend mode), or is in the standby mode.
Table 6 shows the outputs for RY/BY#. Figures 12, 13,
14 and 15 shows R Y/BY# for read, reset, program, and
er ase operations, respectively.
DQ6: Toggle Bit I
Toggle Bit I on DQ6 indicates whether an Embedded
Pr ogra m o r Eras e a lgor ith m is in pr ogre ss or com ple te,
or whether the device has entered the Erase Suspend
mod e. Tog gl e Bit I may be rea d at an y addres s, an d is
va lid after the ri sin g edge of the fin al WE # pu ls e in th e
command sequence (prior to the program or erase op-
er ation), and during the secto r erase time-out.
Du ring an Embe dded Pr ogra m or E rase al gor ithm op -
erat ion, succe ssive read cy cles to any add ress c aus e
DQ6 to toggle. (The system may use either OE# or
CE # to contro l the read cycles.) When the operation is
comple te, DQ6 stops toggling.
After an erase command sequence is written, if all sec-
tors selected for erasing are protected, DQ6 toggles for
approximately 100 µs, then returns to reading array
data . If not al l s el ec ted se cto rs ar e pro te cted , the E m -
bedded Erase algorithm erases the unprotected sec-
tors, and ignores the selected sectors that are
prot ected.
The sys tem can use DQ6 and DQ2 toge ther to deter-
mine whether a sector is actively erasing or is erase-
suspended. When the device is actively erasing (that
is , the E m be dd e d Er as e al g or it hm i s i n pr og re ss ), DQ6
toggles. When the device enters the Erase Suspend
mod e, D Q6 stop s to ggling . Ho wever, the syste m mu st
also use DQ2 to determine which sector s are erasing
or erase- susp ende d. Alter native ly, the syste m can use
DQ7 (see the subsection on “DQ7: Data# Polling”).
If a program address falls within a protected sector,
DQ 6 togg les f or ap proxi mat ely 2 µs afte r the prog ram
co mm an d s eq uence is w r itten, th en re tur ns to r ea di n g
array data.
DQ6 also toggles during the erase-suspend-program
mode, and stops toggling once the Embedded Pro-
gram algorithm is complete.
Table 6 shows the outputs for Toggle Bit I on DQ6.
Refer to Figure 5 for the toggle bit al gorithm, and to Fig-
ur e 17 i n th e “ A C C h arac t er is t ics ” sec t io n f o r th e t og gl e
bit timing diagrams. Figure 18 shows the differences
between DQ2 and DQ6 in graphical form. See also the
subsection on “DQ2: Toggle Bit II”.
DQ2: Toggle Bit II
The “Toggle Bit II” on DQ2, when used with DQ6, indi-
cates whether a particular sector is actively erasing
(that is, the Embedded Erase algorithm is in progress),
or w het her t hat s ecto r is eras e-susp ende d. Tog gle Bit
II is valid after the rising edge of the final WE# pulse in
the command sequence.
DQ2 toggles when the system reads at addresses
within those sectors that have been selected for era-
sure . (The syste m may use eith er OE # or CE# to con -
trol the read cycles.) But DQ2 cannot distinguish
whether the sector is actively erasing or is erase-sus-
pended. DQ6, by comparison, indicates whether the
device is actively erasing, or is in Erase Suspend, but
cannot distinguish which sectors are selected for era-
sure. Thus, both status bits are required for sector and
mode information. Refer to Table 6 to compare outputs
for DQ2 and DQ6.
Figure 5 shows the toggle bit algorithm in flowchart
form , a nd th e section “ DQ2 : To gg le B it II” explains th e
algorithm. See also the “DQ6: Toggle Bit I” subsection.
Fi gure 17 sh ows the toggle bit timi ng d iagram . Fi gur e
18 shows the differences between DQ2 and DQ6 in
graphical form.
Reading Toggle Bits DQ6/DQ2
Refer to Fi gure 5 for the following di scuss ion. Whenever
the system initially begins reading toggle bit status, it
must read DQ7–DQ0 at least twic e 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. A fter the second read, the system woul d com-
pare the new value of the toggle bit with the first. If the
toggle bit is not togglin g, the device has com pleted the
program or erase operation. The system can read array
data on DQ7–DQ0 on the followi ng read cycle.
Howeve r, if after the initial two read cycles, the syste m
determine s that t he toggle bit is still toggling, t he sys-
tem also should note whether the value of DQ5 is high
(see the section on DQ5). If it is, the system should
then determine again whether the toggle bit is toggling,
sin ce the togg l e bit may h ave s t op pe d t og gl ing just a s
DQ5 went high. If the toggle bit is no longer toggling,
the d evic e has su cce ssfu lly comp let ed the prog ram o r
erase o peration . If it is still t oggling, t he de vice did not
completed the operation successfully, and the system
must write the reset command to return to reading
array data.