AT45DB021D ATMEL [ATMEL Corporation], AT45DB021D Datasheet - Page 17
![no-image](/images/no-image-200.jpg)
AT45DB021D
Manufacturer Part Number
AT45DB021D
Description
2-megabit 2.7-volt DataFlash
Manufacturer
ATMEL [ATMEL Corporation]
Datasheet
1.AT45DB021D.pdf
(52 pages)
Available stocks
Company
Part Number
Manufacturer
Quantity
Price
Company:
Part Number:
AT45DB021D-MH
Manufacturer:
ATMEL
Quantity:
1 650
Part Number:
AT45DB021D-MH
Manufacturer:
ATMEL/爱特梅尔
Quantity:
20 000
Company:
Part Number:
AT45DB021D-MH-T
Manufacturer:
EPCOS
Quantity:
34 000
Company:
Part Number:
AT45DB021D-SH
Manufacturer:
ATMEL
Quantity:
320
Part Number:
AT45DB021D-SH
Manufacturer:
ATMEL/爱特梅尔
Quantity:
20 000
Part Number:
AT45DB021D-SH-B
Manufacturer:
ATMEL/爱特梅尔
Quantity:
20 000
Part Number:
AT45DB021D-SH-T
Manufacturer:
ATMEL/爱特梅尔
Quantity:
20 000
Company:
Part Number:
AT45DB021D-SSH
Manufacturer:
ATMEL
Quantity:
3 500
Part Number:
AT45DB021D-SSH
Manufacturer:
ATMEL/爱特梅尔
Quantity:
20 000
9.1.3
9.1.4
3638B–DFLASH–02/07
Read Sector Protection Register Command
Various Aspects About the Sector Protection Register
To read the Sector Protection Register, the CS pin must first be asserted. Once the CS pin has
been asserted, an opcode of 32H and 3 dummy bytes must be clocked in via the SI pin. After the
last bit of the opcode and dummy bytes have been clocked in, any additional clock pulses on the
SCK pins will result in data for the content of the Sector Protection Register being output on the
SO pin. The first byte corresponds to sector 0 (0a, 0b), the second byte corresponds to sector 1,
the third byte corresponds to sector 2, and the last byte (byte 4) corresponds to sector 3. Once
the last byte of the Sector Protection Register has been clocked out, any additional clock pulses
will result in undefined data being output on the SO pin. The CS must be deasserted to termi-
nate the Read Sector Protection Register operation and put the output into a high-impedance
state.
Note:
Figure 9-4.
The Sector Protection Register is subject to a limit of 10,000 erase/program cycles. Users are
encouraged to carefully evaluate the number of times the Sector Protection Register will be
modified during the course of the applications’ life cycle. If the application requires that the Sec-
tor Protection Register be modified more than the specified limit of 10,000 cycles because the
application needs to temporarily unprotect individual sectors (sector protection remains enabled
while the Sector Protection Register is reprogrammed), then the application will need to limit this
practice. Instead, a combination of temporarily unprotecting individual sectors along with dis-
abling sector protection completely will need to be implemented by the application to ensure that
the limit of 10,000 cycles is not exceeded.
CS
SO
Command
Read Sector Protection Register
SI
Each transition
represents 8 bits
xx = Dummy Byte
Read Sector Protection Register
Opcode
X
X
Byte 1
AT45DB021D [Preliminary]
32H
X
Data Byte
Byte 2
n
xxH
Data Byte
n + 1
Byte 3
xxH
Data Byte
n + 3
Byte 4
xxH
17