AM29LV001BB-90EC Spansion Inc., AM29LV001BB-90EC Datasheet - Page 21

• Manufacturer Part Number: AM29LV001BB-90EC
• Manufacturer: Spansion Inc.

Specifications of AM29LV001BB-90EC

• Cell Type: NOR
• Density: 1Mb
• Access Time (max): 90ns
• Interface Type: Parallel
• Boot Type: Bottom
• Address Bus: 17b
• Operating Supply Voltage (typ): 3/3.3V
• Operating Temp Range: 0C to 70C
• Package Type: TSOP
• Program/erase Volt (typ): 2.7 to 3.6V
• Sync/async: Asynchronous
• Operating Temperature Classification: Commercial
• Operating Supply Voltage (min): 2.7V
• Operating Supply Voltage (max): 3.6V
• Word Size: 8b
• Number Of Words: 128K
• Supply Current: 12mA
• Mounting: Surface Mount
• Pin Count: 32
• Lead Free Status / Rohs Status: Not Compliant

command sequence (prior to the program or erase
operation), and during the sector erase time-out.
During an Embedded Program or Erase algorithm
operation, successive read cycles to any address
cause DQ6 to toggle (The system may use either OE#
or CE# to control the read cycles). When the operation
is complete, DQ6 stops toggling.
After an erase command sequence is written, if all
sectors selected for erasing are protected, DQ6 toggles
for approximately 100 µs, then returns to reading array
data. If not all selected sectors are protected, the
Embedded Erase algorithm erases the unprotected
sectors, and ignores the selected sectors that are
protected.
The system can use DQ6 and DQ2 together to deter-
mine whether a sector is actively erasing or is erase-
suspended. When the device is actively erasing (that is,
the Embedded Erase algorithm is in progress), DQ6
toggles. When the device enters the Erase Suspend
mode, DQ6 stops toggling. However, the system must
also use DQ2 to determine which sectors are erasing
or erase-suspended. Alternatively, the system can use
DQ7 (see the subsection on DQ7: Data# Polling).
If a program address falls within a protected sector,
DQ6 toggles for approximately 1 µs after the program
command sequence is written, then returns to reading
array data.
DQ6 also toggles during the erase-suspend-program
mode, and stops toggling once the Embedded
Program algorithm is complete.
Table 6 on page 21
on DQ6.
algorithm in flowchart form, and the section
Toggle Bits DQ6/DQ2” on page 19
rithm.
diagrams.
between DQ2 and DQ6 in graphical form. See also the
subsection on
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 whether that sector is erase-suspended. Toggle 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 were selected for erasure.
(The system may use either OE# or CE# to control the
read cycles.) But DQ2 cannot distinguish whether the
sector is actively erasing or is erase-suspended. DQ6,
by comparison, indicates whether the device is actively
erasing, or is in Erase Suspend, but cannot distinguish
which sectors are selected for erasure. Thus, both
May 5, 2006 21557F4
Figure 18, on page 31
Figure 6, on page 20
Figure 19, on page 32
“DQ2: Toggle Bit
shows the outputs for Toggle Bit I
shows the toggle bit timing
II”, next.
shows the differences
shows the toggle bit
explains the algo-
“Reading
D A T A S H E E T
Am29LV001B
status bits are required for sector and mode informa-
tion. Refer to
for DQ2 and DQ6.
Figure 6, on page 20
flowchart form, and the section
DQ6/DQ2”
Toggle Bit I subsection.
the toggle bit timing diagram.
shows the differences between DQ2 and DQ6 in graph-
ical form.
Reading Toggle Bits DQ6/DQ2
Refer to
sion. Whenever the system initially begins reading
toggle bit status, it must read DQ7–DQ0 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
device has completed the program or erase operation.
The system can read array data on DQ7–DQ0 on the
following 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 DQ5 is
high (see the section on
Limits” on page
determine again whether the toggle bit is toggling,
since the toggle bit may have stopped toggling just as
DQ5 went high. If the toggle bit is no longer toggling,
the device has successfully completed the program or
erase operation. If it is still toggling, the device did not
completed the operation successfully, and the system
must write the reset command to return to reading
array data.
The remaining scenario is that the system initially
determines that the toggle bit is toggling and DQ5 has
not gone high. The system may continue to monitor the
toggle bit and DQ5 through successive read cycles,
determining the status 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 (top of
on page
Table 6 on page 21
on DQ6.
algorithm.
timing diagrams.
ferences between DQ2 and DQ6 in graphical form. See
also the subsection on
DQ5: Exceeded Timing Limits
DQ5 indicates whether the program or erase time has
exceeded a specified internal pulse count limit. Under
Figure 6, on page 20
20).
Figure 6, on page 20
Figure 18, on page 31
explains the algorithm. See also the DQ6:
Table 6 on page 21
19). If it is, the system should then
Figure 19, on page 32
shows the outputs for Toggle Bit I
shows the toggle bit algorithm in
“DQ2: Toggle Bit II” on page
Figure 18, on page 31
“DQ5: Exceeded Timing
for the following discus-
Figure 19, on page 32
“Reading Toggle Bits
shows the toggle bit
shows the toggle bit
to compare outputs
shows the dif-
Figure 6,
shows
19.
19