欢迎访问ic37.com |
会员登录 免费注册
发布采购

AT45DB321D-SU 参数 Datasheet PDF下载

AT45DB321D-SU图片预览
型号: AT45DB321D-SU
PDF下载: 下载PDF文件 查看货源
内容描述: 32兆位2.7伏的DataFlash [32-megabit 2.7-volt DataFlash]
分类和应用: 闪存存储内存集成电路光电二极管异步传输模式PCATM时钟
文件页数/大小: 55 页 / 1471 K
品牌: ATMEL [ ATMEL ]
 浏览型号AT45DB321D-SU的Datasheet PDF文件第13页浏览型号AT45DB321D-SU的Datasheet PDF文件第14页浏览型号AT45DB321D-SU的Datasheet PDF文件第15页浏览型号AT45DB321D-SU的Datasheet PDF文件第16页浏览型号AT45DB321D-SU的Datasheet PDF文件第18页浏览型号AT45DB321D-SU的Datasheet PDF文件第19页浏览型号AT45DB321D-SU的Datasheet PDF文件第20页浏览型号AT45DB321D-SU的Datasheet PDF文件第21页  
AT45DB321D [Preliminary]  
9.1.3  
Read Sector Protection Register Command  
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  
and the last byte (byte 64) corresponds to sector 63. 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 terminate the Read Sector Protection Reg-  
ister operation and put the output into a high-impedance state.  
Command  
Byte 1  
Byte 2  
Byte 3  
Byte 4  
Read Sector Protection Register  
32H  
xxH  
xxH  
xxH  
Note:  
xx = Dummy Byte  
Figure 9-4. Read Sector Protection Register  
CS  
Opcode  
X
X
X
SI  
Data Byte  
n
Data Byte  
n + 1  
Data Byte  
n + 63  
SO  
Each transition  
represents 8 bits  
9.1.4  
Various Aspects About the Sector Protection Register  
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.  
17  
3597H–DFLASH–02/07