24AA52/24LCS52: 2K 2.2V I C Serial EEPROM With Software Write-Protect
24AA52/24LCS52: 2K 2.2V I C Serial EEPROM With Software Write-Protect
24AA52/24LCS52: 2K 2.2V I C Serial EEPROM With Software Write-Protect
A1 2 7 WP
A2 3 6 SCL
VSS 4 5 SDA
*24XX52 is used in this document as a generic part number for the 24AA52/24LCS52 devices.
† NOTICE: Stresses above those listed under "Absolute Maximum Ratings" may cause permanent damage to the
device. These are stress ratings only and functional operation of the device at these or any other conditions above
those indicated in the operation sections of the specifications is not implied. Exposure to Absolute Maximum Rating
conditions for extended periods may affect device reliability.
5 4
2
3
SCL
7
8 9 10
6
SDA
IN 14
11 12
SDA
OUT
D4
SCL
6
7 10
SDA
START STOP
SDA
SDA LINE S P
A A A
BUS ACTIVITY C C C
K K K
Send
Write Command Note: Once the software write-protect register
has been written, the write protection is
enabled and cannot be reversed, even if
Send Stop the device is powered down.
Condition to
Initiate Write Cycle 6.2 Hardware Write-Protect
The WP pin can be tied to VCC, VSS or can be left float-
ing. If tied to VCC, the entire array will be write-protected,
Send Start regardless of whether the software write-protect register
has been written or not. If the WP pin is set to VCC, it will
prevent the software write-protect register from being
written. If the WP is tied to VSS or left floating, then write
Send Control Byte protection is determined by the status of the software
with R/W = 0 write-protect register.
Did Device
No
Acknowledge
(ACK = 0)?
Yes
Next
Operation
SDA LINE S P
A A A
BUS ACTIVITY C C C
K K K
SDA LINE S P
A N
BUS ACTIVITY C O
K
A
C
K
S S
BUS ACTIVITY T CONTROL WORD T CONTROL S
MASTER A BYTE ADDRESS (n) A BYTE T
R R DATA (n) O
T T P
S S P
SDA LINE
A A A N
C C C O
K K K
BUS ACTIVITY A
C
K
SDA LINE P
A A A A N
BUS ACTIVITY C C C C O
K K K K
A
C
K
XXXXXXXX 24AA52
XXXXXNNN I/PNNN
YYWW YYWW
XXXXXXXX 24LCS52
XXXXYYWW I/SNYYWW
NNN NNN
XXXX S52
XYWW IYWW
NNN NNN
XXXXXX 4S52I
YWWNNN YWWNNN
Note: In the event the full Microchip part number cannot be marked on one line, it will
be carried over to the next line thus limiting the number of available characters
for customer specific information.
*Standard OTP marking consists of Microchip part number, year code, week code and traceability code.
E1
n 1
A A2
L
c
A1
β B1
p
eB B
E1
D
2
B n 1
h α
45°
c
A A2
φ
β L A1
E1
D
2
1
n
B
α
A
φ A1 A2
β
L
E1
D
2
B
n 1
A A2
c
φ
A1
(F) L
β
From: Name
Company
Address
City / State / ZIP / Country
Telephone: (_______) _________ - _________ FAX: (______) _________ - _________
Application (optional):
Would you like a reply? Y N
Questions:
2. How does this document meet your hardware and software development needs?
3. Do you find the organization of this document easy to follow? If not, why?
4. What additions to the document do you think would enhance the structure and subject?
5. What deletions from the document could be made without affecting the overall usefulness?
Please specify which device, revision of silicon and Data Sheet (include Literature #) you are using.
• Microchip believes that its family of products is one of the most secure families of its kind on the market today, when used in the
intended manner and under normal conditions.
• There are dishonest and possibly illegal methods used to breach the code protection feature. All of these methods, to our
knowledge, require using the Microchip products in a manner outside the operating specifications contained in Microchip's Data
Sheets. Most likely, the person doing so is engaged in theft of intellectual property.
• Microchip is willing to work with the customer who is concerned about the integrity of their code.
• Neither Microchip nor any other semiconductor manufacturer can guarantee the security of their code. Code protection does not
mean that we are guaranteeing the product as “unbreakable.”
Code protection is constantly evolving. We at Microchip are committed to continuously improving the code protection features of our
products. Attempts to break microchip’s code protection feature may be a violation of the Digital Millennium Copyright Act. If such acts
allow unauthorized access to your software or other copyrighted work, you may have a right to sue for relief under that Act.