AM29BDD160G AMD [Advanced Micro Devices], AM29BDD160G Datasheet - Page 56
![no-image](/images/no-image-200.jpg)
AM29BDD160G
Manufacturer Part Number
AM29BDD160G
Description
16 Megabit (1 M x 16-bit/512 K x 32-Bit), CMOS 2.5 Volt-only Burst Mode, Dual Boot, Simultaneous Read/Write Flash Memory
Manufacturer
AMD [Advanced Micro Devices]
Datasheet
1.AM29BDD160G.pdf
(80 pages)
Available stocks
Company
Part Number
Manufacturer
Quantity
Price
Company:
Part Number:
AM29BDD160GB-54DKE
Manufacturer:
NA
Quantity:
6 222
Company:
Part Number:
AM29BDD160GB-64CKE
Manufacturer:
SPANSION
Quantity:
4 155
Company:
Part Number:
AM29BDD160GB-64CKE
Manufacturer:
AMD
Quantity:
6 234
Company:
Part Number:
AM29BDD160GB-64CKET
Manufacturer:
SPANSION
Quantity:
3 000
Company:
Part Number:
AM29BDD160GB54SKE
Manufacturer:
SPANSION
Quantity:
532
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 ig-
nore DQ3 if the system can guarantee that the time
between additional sector erase commands will al-
ways be less than 50 µs. See also the
Command
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
Notes:
1. DQ5 switches to ‘1’ when an Embedded Program or Embedded Erase operation has exceeded the maximum timing limits.
2. DQ7 and DQ2 require a valid address when reading status information. Refer to the appropriate subsection for further
54
Standard
Suspend
Mode
Erase
Mode
See
details.
DQ5: Exceeded Timing Limits
section.
Reading within Erase Suspended
Embedded Program Algorithm
Embedded Erase Algorithm
Reading within Non-Erase
Erase-Suspend-Program
Suspended Sector
Operation
Sector
for more information.
Table 23. Write Operation Status
Sector Erase
(Note 2)
DQ7#
DQ7#
DQ7
Data
0
1
Am29BDD160G
No toggle
Toggle
Toggle
Toggle
DQ6
Data
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 ad-
ditional 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 23 shows the
outputs for DQ3.
DQ5 (Note
Data
1)
0
0
0
0
DQ3
Data
N/A
N/A
N/A
1
DQ2 (Note
No toggle
Toggle
Toggle
Data
N/A
2)
RY/BY#
0
0
1
1
0