11aa02iud 1wire Microchip
11aa02iud 1wire Microchip
11aa02iud 1wire Microchip
Features: Description:
• Preprogrammed 32-Bit Serial Number: The Microchip Technology Inc. 11AA02UID device is a
- Unique across all UID-family EEPROMs 2 Kbit Serial Electrically Erasable PROM with a
- Scalable to 48-bit, 64-bit, 128-bit, 256-bit, preprogrammed, 32-bit unique ID. The device is
and other lengths organized in blocks of x8-bit memory and support the
patented* single I/O UNI/O® serial bus. By using
• Single I/O, UNI/O® Serial Interface Bus
Manchester encoding techniques, the clock and data
• Low-Power CMOS Technology: are combined into a single, serial bit stream (SCIO),
- 1 mA active current, typical where the clock signal is extracted by the receiver to
- 1 µA standby current (max.) correctly decode the timing and value of each bit.
• 256 x 8 Bit Organization Low-voltage design permits operation down to 1.8V,
• Schmitt Trigger Inputs for Noise Suppression with standby and active currents of only 1 uA and 1 mA,
• Output Slope Control to Eliminate Ground Bounce respectively.
• 100 kbps Max. Bit Rate – Equivalent to 100 kHz The 11AA02UID is available in standard 8-lead SOIC
Clock Frequency and 3-lead SOT-23 packages.
• Self-Timed Write Cycle (including Auto-Erase)
• Page-Write Buffer for up to 16 Bytes Package Types (not to scale)
• STATUS Register for Added Control: SOIC
SOT23
- Write enable latch bit (TT) (SN)
- Write-In-Progress bit
2 VCC NC 1 8 VCC
• Block Write Protection: NC 2 7 NC
VSS 3
- Protect none, 1/4, 1/2 or all of array NC 3 6 NC
1 SCIO VSS 4 SCIO
• Built-in Write Protection: 5
- Power-on/off data protection circuitry
- Write enable latch
• High Reliability: Pin Function Table
- Endurance: 1,000,000 erase/write cycles Name Function
- Data retention: > 200 years
SCIO Serial Clock, Data Input/Output
- ESD protection: > 4,000V
VSS Ground
• 3-Lead SOT-23 and 8-Lead SOIC Packages
VCC Supply Voltage
• RoHS Compliant
• Available Temperature Ranges:
- Industrial (I): -40°C to +85°C
* Microchip’s UNI/O® Bus products are covered by the following patents issued in the U.S.A.: 7,376,020 and 7,788,430.
† NOTICE: Stresses above those listed under ‘Absolute Maximum Ratings’ may cause permanent damage to the
device. This is a stress rating only and functional operation of the device at those or any other conditions above those
indicated in the operational listings of this specification is not implied. Exposure to maximum rating conditions for an
extended period of time may affect device reliability.
10 11 2
SCIO
Data ‘0’ Data ‘1’ Data ‘0’ Data ‘1’ Data ‘0’ Data ‘1’ Data ‘0’ Data ‘1’ MAK bit NoSAK bit
12
SCIO
9
SCIO
Standby
Mode
2 2
3 3 6 6 6 6
EEPROM
I/O Control Memory X
Control Array
Logic
Logic Dec
Page Latches
Current-
Limited
Slope
Control
Y Decoder
SCIO
Sense Amp.
VCC R/W Control
VSS
NoSAK
MAK
MAK
SAK
Standby Pulse(1) Start Header Device Address
SCIO
0 1 0 1 0 1 0 1 1 0 1 0 0 0 0 0
NoMAK
NoSAK
SAK
MAK
MAK
SAK
TSS
SCIO
0 1 0 1 0 1 0 1 1 0 1 0 0 0 0 0
Note 1: After a POR/BOR event, a low-to-high transition on SCIO is required to occur before the first
standby pulse.
3.2 Start Data Transfer When a standby pulse is not required (i.e., between
successive commands to the same device), a period of
All operations must be preceded by a start header. The TSS must be observed after the end of the command
start header consists of holding SCIO low for a period and before the beginning of the start header.
of THDR, followed by transmitting an 8-bit ‘01010101’
code. This code is used to synchronize the slave’s Figure 3-2 shows the waveform for the start header,
internal clock period with the master’s clock period, so including the required Acknowledge sequence at the
accurate timing is very important. end of the byte.
SCIO
TSS THDR Data ‘0’ Data ‘1’ Data ‘0’ Data ‘1’ Data ‘0’ Data ‘1’ Data ‘0’ Data ‘1’ MAK NoSAK
MAK SAK
MAK
SAK
Standby Pulse Start Header Device Address
SCIO
0 1 0 1 0 1 0 1 1 0 1 0 0 0 0 0
MAK
SAK
MAK
SAK
MAK
SAK
SCIO 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
0 0 0 0 0 0 1 1
NoMAK
SAK
MAK
SAK
MAK
SAK
SCIO 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0
MAK
SAK
Standby Pulse Start Header Device Address
SCIO
0 1 0 1 0 1 0 1 1 0 1 0 0 0 0 0
MAK
SAK
MAK
SAK
MAK
SAK
Command Data Byte 1 Data Byte 2
SCIO 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0
0 0 0 0 0 1 1 0
NoMAK
SAK
Data Byte n
SCIO 7 6 5 4 3 2 1 0
MAK
SAK
Standby Pulse Start Header Device Address
SCIO
0 1 0 1 0 1 0 1 1 0 1 0 0 0 0 0
MAK
SAK
MAK
SAK
MAK
SAK
SCIO 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
0 1 1 0 1 1 0 0
No MAK
SAK
MAK
SAK
MAK
SAK
SCIO 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0
Twc
NoSAK
MAK
MAK
SAK
Standby Pulse Start Header Device Address
SCIO
0 1 0 1 0 1 0 1 1 0 1 0 0 0 0 0
NoMAK
SAK
Command
SCIO
1 0 0 1 0 1 1 0
MAK
SAK
Standby Pulse Start Header Device Address
SCIO
0 1 0 1 0 1 0 1 1 0 1 0 0 0 0 0
NoMAK
SAK
Command
SCIO
1 0 0 1 0 0 0 1
The Write-In-Process (WIP) bit indicates whether the The WIP and WEL bits will update dynamically (asyn-
11AA02UID is busy with a write operation. When set to chronous to issuing the RDSR instruction). Further-
a ‘1’, a write is in progress, when set to a ‘0’, no write more, after the STATUS register data is received, the
is in progress. This bit is read-only. master can provide a MAK during the Acknowledge
sequence to request that the data be transmitted again.
The Write Enable Latch (WEL) bit indicates the status
This allows the master to continuously monitor the WIP
of the write enable latch. When set to a ‘1’, the latch
and WEL bits without the need to issue another full
allows writes to the array, when set to a ‘0’, the latch
command.
prohibits writes to the array. This bit is set and cleared
using the WREN and WRDI instructions, respectively. Once the master is finished, it provides a NoMAK to
This bit is read-only for any other instruction. end the operation.
Note: The current drawn for a Read Status
Register command during a write cycle is
a combination of the ICC Read and ICC
Write operating currents.
MAK
SAK
Standby Pulse Start Header Device Address
SCIO
0 1 0 1 0 1 0 1 1 0 1 0 0 0 0 0
NoMAK
MAK
SAK
SAK
SCIO 3 2 1 0
0 0 0 0 0 1 0 1 0 0 0 0
Note: The STATUS register data can continuously be read, or polled, by transmitting a MAK in place of the NoMAK.
NoSAK
MAK
MAK
SAK
Standby Pulse Start Header Device Address
SCIO
0 1 0 1 0 1 0 1 1 0 1 0 0 0 0 0
NoMAK
MAK
SAK
SAK
SCIO 7 6 5 4 3 2 1 0
0 1 1 0 1 1 1 0 Twc
NoSAK
MAK
MAK
SAK
Standby Pulse Start Header Device Address
SCIO
0 1 0 1 0 1 0 1 1 0 1 0 0 0 0 0
NoMAK
SAK
Command
SCIO
0 1 1 0 1 1 0 1 Twc
4.8 Set All (SETAL) Instruction The SETAL instruction is ignored if either of the Block
Protect bits (BP0, BP1) are not ‘0’, meaning 1/4, 1/2, or
The SETAL instruction allows the user to write ‘0xFF’ all of the array is protected.
to the entire memory array with one command. Note
that the write enable latch (WEL) must first be set by Note: The SETAL instruction must be termi-
issuing the WREN instruction. nated with a NoMAK following the com-
mand byte. If a NoMAK is not received at
Once the write enable latch is set, the user may pro-
this point, the command will be consid-
ceed with issuing a SETAL instruction (including the
ered invalid, and the device will go into
header and device address bytes). Immediately after
Idle mode without responding with a SAK
the NoMAK bit has been transmitted by the master, the
or executing the command.
internal write cycle is initiated, during which time all
words of the memory array are written to ‘0xFF’.
MAK
SAK
SCIO
0 1 0 1 0 1 0 1 1 0 1 0 0 0 0 0
NoMAK
SAK
Command
SCIO
0 1 1 0 0 1 1 1 Twc
Note: The 32-bit serial number is unique across 7.2 Factory-Programmed Write
all Microchip UID-family serial EEPROM
Protection
devices.
In order to help guard against accidental corruption of
FIGURE 7-1: MEMORY ORGANIZATION the serial number, the BP1 and BP0 bits of the STATUS
register are programmed at the factory to ‘0’ and ‘1’,
00h
respectively, as shown in the following table:
Standard 7 6 5 4 3 2 1 0
EEPROM X X X X BP1 BP0 WEL WIP
— — — — 0 1 — —
C0h This protects the upper 1/4 of the array (0xC0 to 0xFF)
Write-Protected
Serial Number Block from write operations. This array block can be utilized
FFh
for writing by clearing the BP bits with a Write Status
Register (WRSR) instruction. Note that if this is
The 4-byte serial number is stored in array locations
performed, care must be taken to prevent overwriting
0xFC through 0xFF, as shown in Figure 7-2.
the serial number.
Manufacturer Device
Description 32-bit Serial Number
Code Code
Array
Address FAh FBh FCh FDh FEh FFh
7.3 Extending the 32-bit Serial TABLE 7-1: EXTENDED READ EXAMPLES
Number Serial Number
Start Address End Address
For applications that require serial numbers larger than Length
32 bits, additional data bytes can be used to pad the 0xFC 0xFF 32 bits
provided serial number to meet the required length. 0xFA 0xFF 48 bits
Any data byte values can be used for padding as the
32-bit serial number ensures the extended serial 0xF8 0xFF 64 bits
number remains unique. 0xF0 0xFF 128 bits
The padding can be performed in two ways. The first 0xE0 0xFF 256 bits
method is to pad the data in software by combining the
32-bit serial number from the 11AA02UID with fixed
data. The second method is to extend the number of
bytes read from the 11AA02UID to meet the required
length. Table 7-1 shows example address ranges and
their corresponding serial number lengths.
XXXXXXXT 11A2UIDI
XXXXYYWW SN e3 1328
NNN 1L7
XXXNNN AAB1L7
I Temp. I Temp.
11AA02UID AABNNN 11A2UIDT
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.
Note: For the most current package drawings, please see the Microchip Packaging Specification located at
http://www.microchip.com/packaging
Note: For the most current package drawings, please see the Microchip Packaging Specification located at
http://www.microchip.com/packaging
!"#$%
&
!
"# $% &"'""
($)
%
*++&&&!
!+$
'
''"'(%
&
!
"# $% &"'""
($)
%
*++&&&!
!+$
E
E1
1 2
e1
D
c
A A2 φ
A1
L
O K 1O
?%
$"" K
?%L% G H K 7
&
1 !"
"%31%
#%!
%)"
#"
"
%)"
#"
""
6%7!! "%
!"
%
3817
;<* ;"!"
6=#"
&&
#
"
& <1;
Note: For the most current package drawings, please see the Microchip Packaging Specification located at
http://www.microchip.com/packaging
Revision A (05/2013)
Initial release.
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?
• 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.
QUALITY MANAGEMENT SYSTEM Microchip received ISO/TS-16949:2009 certification for its worldwide
headquarters, design and wafer fabrication facilities in Chandler and
CERTIFIED BY DNV Tempe, Arizona; Gresham, Oregon and design centers in California
and India. The Company’s quality system processes and procedures
are for its PIC® MCUs and dsPIC® DSCs, KEELOQ® code hopping
== ISO/TS 16949 == devices, Serial EEPROMs, microperipherals, nonvolatile memory and
analog products. In addition, Microchip’s quality system for the design
and manufacture of development systems is ISO 9001:2000 certified.