TB3124
Real-Time Clock and Calendar Technical Brief
Author: Mary Tamar Tan
Microchip Technology Inc.
INTRODUCTION
Reducing overall component count in any system and
eliminating or reducing the user programming costs for
any application is always a goal in any design.
Microchip offers an easy-to-implement Real-Time
Clock and Calendar hardware feature that helps
achieve both of these goals. The Real-Time Clock and
Calendar (RTCC) module of these devices offers not
just accurate time and date-keeping, but is also
optimized for low-power usage with minimum to no
intervention from the CPU.
The RTCC is a 100-year clock and calendar with
automatic leap year detection. The range of the clock is
from 00:00:00 (midnight) on January 1, 2000 to
23:59:59 on December 31, 2099. The hours use the
24-hour time format (military time) with no hardware
provisions for 12-hour time format (A.M./P.M.).
This technical brief describes briefly the RTCC
module’s features, functionality, calibration, sample
initialization codes, and its low-power and
uninterrupted operation. It also gives an overview on
what devices are suitable for the most common
applications requiring precise timing such as digital
clocks and energy metering devices.
RTCC MODULE KEY FEATURES
PIC® microcontrollers are an excellent choice for
applications involving critical time-keeping operations
because of the following key features of the RTCC
module:
• Hardware Real-Time Clock and Calendar (RTCC)
• Provides hours, minutes and seconds using 24-
hour format
• Visibility of one-half second period
• Provides calendar – weekday, date, month and
year
• Alarm configurable for half a second, one second,
ten seconds, one minute, ten minutes, one hour,
one day, one week or one month
• Alarm repeat with decrementing counter
• Alarm with indefinite repeat–chime
• Year 2000 to 2099 leap year correction
• BCD format for smaller software overhead
• Optimized for long-term battery operation
 2015 Microchip Technology Inc.
• Fractional second synchronization
• Multiple clock sources
- SOSC
- LPRC
- 50 Hz
- 60 Hz
• User calibration with periodic auto-adjust
• Calibration to within ±2.64 seconds error per
month
• Calibrates up to 260 ppm of crystal error
RTCC BLOCK DIAGRAM
Figure 1 shows the block diagram of the RTCC
module. It utilizes a separate clock source coming from
an external crystal oscillating at 32.768 kHz from the
Secondary Oscillator (SOSC) or the T1OSC for some
devices, which enables the module to continue running
even when the CPU clock is disabled during Deep
Sleep mode. The internal RC can also be used,
however, allowing the RTCC accuracy to directly
depend on the RC tolerance.
The 1:16384 clock prescaler provides the half-second
visibility to the user, and in turn allows the RTCC timer
to increment the appropriate second, minute, hour,
weekday, day, month and year values as stored in the
RTCVALx registers. These RTC values are compared
with the user-set alarm values to trigger an alarm inter-
rupt whenever a match occurs. The alarm values are
stored in the ALRMVALx registers. Alarm masks are
used to set the time interval between each alarm event
if ever multiple periodic alarm events are desired.
The RTCC pin can output either the seconds clock or
an alarm pulse operating at half the frequency of the
alarm, depending on the configured settings.
DS90003124A-page 1
TB3124
FIGURE 1: RTCC BLOCK DIAGRAM

RTCC Clock Domain CPU Clock Domain

32.768 kHz Input

RTCCON1
from SOSC Oscillator
RTCC Prescalers
Internal RC ALRMRPT
YEAR
(LF-INTOSC) 0.5s
MTHDY
RTCC Timer RTCVALx
WKDYHR
Alarm
Event MINSEC
Comparator

ALMTHDY
Compare Registers
ALRMVALx ALWDHR
with Masks
ALMINSEC
Repeat Counter

RTCC Interrupt
RTCC Interrupt Logic Alarm Pulse
1s
RTCC Pin
RTSECSEL
RTCOE

BCD TIMER AND ALARM VALUES

To simplify the firmware when using the module, the
register interface for the RTCC and alarm values are
implemented using the Binary Coded Decimal (BCD)
format, as shown in Table 1.

TABLE 1: RTCC VALUES IN BCD

Valid Value Range in BCD
RTCC Value
Tens Digit Ones Digit
Register
bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0
Year 0-9 0-9
Month — — 0-1 0-9
Day — — 0-3 0-9
Weekday — — — — — 0-6
Hour — — 0-2 0-9
Minute — 0-5 0-9
Second — 0-5 0-9
When there is a rollover, the following timer values are • Month: From 12/31 to 01/01 with a carry to the
affected: Year field
• Time of Day: From 23:59:59 to 00:00:00 with a • Day of Week: From 6 (Saturday) to 0 (Sunday)
carry to the Day field with no carry
• Day: From the maximum number of days per • Year Carry: From 99 to 00 (this also surpasses
month (31, 30, 29, or 28) to 1 with carry to the the use of the RTCC)
Month Field The carry to the upper BCD digit occurs at the count of
10, not 16, because the above values are in BCD
format.

DS90003124A-page 2  2015 Microchip Technology Inc.


PERIPHERAL CONFIGURATION
The user configures the time by writing the required
year, month, day, hour, minutes and seconds to the
Timer registers. However, it is important to take note
that the RTCC Enable (RTCEN) bit, the RTCVALH and
RTCVALL registers can only be written to when the
RTCC Value Registers Write Enable (RTCWREN) bit is
set to ‘1’. Else, any write to these registers will be
ignored.
TB3124
For the RTCWREN bit to be set, the code sequence
shown in Example 1 must be executed. In the
sequence, a window of only one instruction cycle time
is allowed between the 0x55 and x00xAA instructions.
The PIC16F97J94 microcontroller is used in the
following examples. For other devices, refer to the data
sheet for device specific information.

EXAMPLE 1: SETTING THE RTCWREN BIT

EECON2 = 0x55;

EECON2 = 0xAA;

RTCCON1bits.RTCWREN = 1; //enable write to the RTCC

The RTCC Timer (RTCVALx) and Alarm Timer
(ALRMVALx) registers can only be accessed through
corresponding register pointers. Every write or read to
the RTCVALH register decrements the RTCC Pointer
value (RTCPTR<1:0>) by ‘1’ until it reaches ‘00’. The
RTCVALH and RTCVALL Register Mapping is shown
in Table 2.
Example 2 shows sample code for writing to the RTCC
Timer registers via register pointers. RTCCON1 is
named RTCCFG on some devices. Also, on some
PIC18 devices, the PADCFGx registers hold the RTCC
Seconds Clock Output Select bits.

TABLE 2: RTCVALH AND RTCVALL

REGISTER MAPPING
RTCC Value Register Window
RTCPTR<1:0>
RTCVALH RTCVALL
00 Minutes Seconds
01 Weekday Hours
10 Month Day
11 — Year

EXAMPLE 2: SETTING THE TIME AND DATE

//Set Date to October 12, 2014 and time to 09:45:30 AM

RTCCON1bits.RTCPTR = 3; //initial RTCC pointer value to prepare write to the YEAR value register

RTCVALL = 0x14; //set YEAR to 2014

RTCVALH = 0; //unimplemented register; this write will decrement pointer value by 1

RTCVALL = 0x12; //set DAY to 12

RTCVALH = 0x10; //set MONTH to October; this write will decrement pointer value by 1

RTCVALL = 0x09; //set HOURS to 9

RTCVALH = 0x00; //set WEEKDAY to Sunday; this write will decrement pointer value by 1

RTCVALL = 0x30; //set SECONDS to 30; RTCPTR reaches 0

RTCVALH = 0x45; //set MINUTES to 45; RTCPTR is already 0 and can no longer be decremented

 2015 Microchip Technology Inc. DS90003124A-page 3

TB3124
When the RTCC output pin is enabled, the user can
choose either to output the seconds clock or an alarm
pulse, operating at half the frequency of the alarm. For
a more accurate timing and to ensure uninterrupted
operation of the RTCC even in Deep Sleep, the SOSC
is recommended as the peripheral’s clock source.
Once the RTCC is enabled, the timer proceeds with the
count from the configured starting point. Also, to avoid
accidental writes to the RTCC Timer register, it is
advised that the RTWREN bit be cleared when not
writing to the register. An example code for this
configuration is shown in Example 3.

EXAMPLE 3: CONFIGURING THE CONTROL REGISTERS

RTCCON1bits.RTCOE = 1; //enable the Output Enable pin of the RTCC

RTCCON2bits.RTCCLKSEL = 0; //select SOSC as the RTCC clock source

RTCCON2bits.RTCSECSEL = 1; //output RTCC seconds clock on the RTCC pin

RTCCON1bits.RTCEN = 1; //enable RTCC

RTCCON1bits.RTCWREN = 0; //disable write to the RTCC

ALARM CONFIGURATION
In addition to the capability of the RTCC module to
count the time accurately, it also has an alarm feature
which is configurable from half a second to one year
and can be repeated as desired by the user.
Every write or read to the ALRMVALH register
decrements the Alarm Pointer Value (ALRMPTR<1:0>)
by ’1’. ALRMVALH and ALRMVALL Register Mapping
is shown in Table 3.

TABLE 3: ALRMVALH AND ALRMVALL

REGISTER MAPPING
Alarm Value Register Window
ALRMPTR<1:0>
ALRMVALH ALRMVALL
00 ALRMMIN ALRMSEC
01 ALRMWD ALRMHR
10 ALRMMNTH ALRMDAY
11 — —
Configuring the alarm is very simple as shown in
Example 4.

DS90003124A-page 4  2015 Microchip Technology Inc.

 TB3124
EXAMPLE 4: SAMPLE ALARM CONFIGURATION
//Set Alarm Date to October 12, 2015 and time to 09:45:30 AM

ALRMCFGbits.ALRMEN = 0; //ensure that alarm is disabled

ALRMCFGbits.ALRMPTR = 2;//initial RTCC pointer value to prepare write to the ALRMDAY value register

ALRMVALL = 0x12; //set ALRMDAY to 12

ALRMVALH = 0x10; //set ALRMMONTH to October; this write will decrement pointer value by 1

ALRMVALL = 0x09; //set ALRMHR to 9

ALRMVALH = 0x02; //set ALRMWD to Monday; this write will decrement pointer value by 1

ALRMVALL = 0x30; //set ALRMSEC to 30; ALRMPTR reaches 0

ALRMVALH = 0x45; //set ALRMMIN to 45; ALRMPTR is already 0 and can no longer be decremented

//Set the Alarm to repeat every year indefinitely

ALRMRPT = 0xFF; //repeat alarm 255 more times

ALRMCFGbits.CHIME = 1; //set alarm to repeat indefinitely

ALRMCFGbits.AMASK = 9; //set alarm to repeat every year

ALRMCFGbits.ALRMEN = 1; //enable alarm

REGISTER READ AND WRITES

If the register is enabled while writing to the Timer
registers, the timer still continues to increment.
However, any time the MINUTE or SECOND register is
written to, both of the timer prescalers are reset to ‘0’ to
allow fraction of a second synchronization.
The user should employ a firmware solution to ensure
that the data read did not fall on a roll-over boundary,
resulting in an invalid or partial read. This is done by
reading each register twice and then comparing the two
values. If the two values matched, then a rollover did
not occur. When the read synchronization bit
RTCSYNC is set to ‘1’, the RTCVALH, RTCVALL and
ALRMRPT registers can change when a roll-over ripple
occurs. This process is shown in Figure 2.

 2015 Microchip Technology Inc. DS90003124A-page 5

TB3124
FIGURE 2: SAMPLE FIRMWARE SOLUTION FOR A VALID DATA READ

Peripheral
Initialization

RTCC Synchronization.
RTCVALH, RTCVALL and
ALRMRPT registers change.
RTCPTR = 3

Read RTCVALx values and copy to corresponding temporary variables .

RTCPTR value decrements on every read of the RTCVALH register. Ex.
RTCC_Year = RTCVALL Compare the previously read
: values to their corresponding
: newly read values. Ex. Invalid Data.
RTCC_Min = RTCVALH RTCC_Year = RTCC_YearChk? NO Rollover ripple
: occurred.
:
RTCC_Min = RTCC_MinChk?
RTCPTR = 3

Read RTCVALx values again and copy to corresponding temporary

variables . YES
RTCPTR value decrements on every read of the RTCVALH register. Ex.
RTCC_YearChk = RTCVALL
: Increment corresponding Timer
: Registers
RTCC_MinChk = RTCVALH

To other peripherals

CALIBRATION RTCC in Deep Sleep Mode

To provide maximum accuracy, Microchip’s RTCC
module has a calibration register, the RTCCAL, to auto-
adjust the crystal errors every minute. An error to within
±2.64 seconds per month can be achieved when the
module is properly calibrated.
If the oscillator is faster than the ideal frequency, the
module automatically subtracts the error clock pulses
from the timer counter once every minute. On the other
hand, if the oscillator is slower than the ideal frequency,
the number of error clock pulses is added to the timer
counter once every minute.
The user must also consider other factors affecting the
crystal’s behavior such as mechanical vibration, load
capacitance, temperature and aging. For a detailed
explanation on the calibration methods and error
pulses value calculation to be stored to the RTCCAL
register, refer to AN1155 “Run-Time Calibration of
Watch Crystals”.
Deep Sleep mode offers the lowest power consumption
among the instruction-based power-saving modes in
any 8-bit PIC® microcontroller. During this mode, the
power to the microcontroller core is removed to reduce
leakage current and most of the peripherals and other
functions of the microcontroller are disabled, except for
the RTCC and the Deep Sleep Watchdog Timer
(DSWDT). Thus, the RTCC can continue running unin-
terrupted even while the device is in Deep Sleep mode.
When the RTCC is enabled during Deep Sleep, the
current consumption is typically between 650 nA and
850 nA. This mode is entered by setting the DSEN bit
(DSCONH<7>) or by executing the SLEEP instruction.
An RTCC Alarm can wake-up the device from Deep
Sleep, and the system resets to its POR state without
affecting the values stored in the RTCC registers.

DS90003124A-page 6  2015 Microchip Technology Inc.


RTCC IN VBAT MODE
The RTCC operation is considered to be critical due to
the fact that it maintains the current time and date, and
any disruption on its operation (i.e., a VDD power loss,
may affect its timing accuracy.) PIC microcontrollers
offer both MCU power reduction and uninterrupted
operation of the RTCC through a hardware-based
power mode called the VBAT mode. This mode utilizes
a back-up power source connected to the VBAT pin as
shown in Figure 3. An on-chip power switch detects the
power loss from the VDD and connects the VBAT pin to
the retention regulator. This provides power at 1.2V to
maintain the retention regulator, as well as the RTCC,
with its clock source (if enabled) and the Deep Sleep
FIGURE 3: VBAT MODE TOPOLOGY
 2015 Microchip Technology Inc.
TB3124
General Purpose (DSGPRx) registers. The RTCC
continues to operate as if there was no power
interruption.
The device automatically wakes from VBAT mode once
VDD is restored. Wake-up from this mode is identified
by checking the state of the VBAT bit. If this bit is set
when the device is awake and starting to execute the
code from the Reset vector, it indicates that the exit
was from VBAT mode. To identify future VBAT wake-up
events, the bit must be cleared in software. During
wake-up, all SFRs except the Deep Sleep semaphore
and RTCC registers are reset to their POR values.
One example of Microchip’s demo boards that supports
the VBAT operation is the LCD Explorer Demonstration
Board. It is provided with a battery holder for a CR2032
button cell, rated at 3V.
®
8-
DS90003124A-page 7
TB3124
INTEGRATING RTCC WITH OTHER
PERIPHERALS
To fully understand the practicality of using the RTCC
module of PIC microcontrollers and its ease of
integration with other peripherals, two examples are
briefly presented below.

FIGURE 4: DIGITAL ALARM CLOCK IMPLEMENTING THE RTCC MODULE

®
8-Bit

RTCC in Digital Alarm Clocks Several demo boards by Microchip support RTCC
hardware and have a built-in LCD glass, which could
Figure 4 shows a sample implementation of the RTCC be good resources in developing applications using the
with the LCD Driver and the Capture/Compare/PWM RTCC with the LCD. These include the LCD Explorer
(CCP) modules for a digital alarm clock application. Demo Board (DM240314) and the PICDEMTM PIC18
The secondary oscillator (SOSC) provides the clock for Explorer Demo Board (DM183032). Several PIC
the RTCC module. Suppose that the RTCC pin is microcontrollers with RTCC also have an internal LCD
configured to output the seconds clock. This allows Driver module which could directly drive the LCD glass,
LED D1 to blink once every second. The values in the while others can use the MSSP module to
RTCVALx registers are manipulated by firmware to be communicate with the LCD while displaying the time
displayed on LCD1 through the LCD Driver module. and date.
The alarm interrupt triggers the CCP module to
generate a pulse-width modulated output which
activates the piezo buzzer (P1) on every alarm event.
The alarm duration is controlled through firmware. The
push-button switches (S1, S2, S3) are used to set the
initial RTCC time and date, as well as the alarm
settings, and one of the buttons can also be used to
trigger the start of the RTCC count.

DS90003124A-page 8  2015 Microchip Technology Inc.

 TB3124
RTCC in Metering Devices CONCLUSION
Another sample implementation of the RTCC module is The RTCC module of PIC microcontrollers provides all
in energy metering devices, in which it could be the necessary features to maintain accurate time and
integrated with other peripherals such as the Analog- date-keeping. It is easy to configure, provides
to-Digital Converter (A/D) module and the LCD Driver automatic error calibration, and has very low power
module. consumption.
MCUs for metering applications should have a high Since the RTCC is usually not implemented by itself, its
resolution A/D converter for voltage and current usefulness is better appreciated when integrated with
measurement, must consume low power, must be able other peripherals. PIC microcontrollers offer versatile
to operate from a battery source to enable choices of peripherals which could be implemented
uninterrupted operation of the RTCC and should have with the RTCC module for various applications.
an EEPROM for data logging and storage for
calibration data.
Microchip’s PIC18F97J94, PIC18F87J90, and
PIC18F87K90, are only a few of the 8-bit
microcontrollers that meet the above-mentioned
design requirements. The periodic auto-adjust feature
in the RTCC module of these devices can be used with
the Analog-to-Digital Converter (A/D) module to
perform software temperature compensation for a
more accurate time. Moreover, these microcontrollers
have a built-in LCD module which could directly drive
an LCD to display the real time energy consumption.
Last but not the least, PIC microcontrollers have an
external interface for a battery source through the VBAT
pin, which enables the RTCC module to run
continuously in case a VDD power loss occurs.
The discussion on the actual implementation of the
RTCC for energy metering applications, however, is
beyond the scope of this technical brief.

 2015 Microchip Technology Inc. DS90003124A-page 9

TB3124
APPENDIX A: 8-BIT PIC® MICROCONTROLLERS WITH RTCC MODULE

TABLE A-1: WEB LINKS FOR 8-BIT PIC MCUs WITH RTCC MODULE
PIC18 Product Family Web Links
PIC18F46J11 http://www.microchip.com/wwwproducts/Devices.aspx?product=PIC18F46J11
PIC18F47J13 http://www.microchip.com/wwwproducts/Devices.aspx?product=PIC18F47J13
PIC18F47J53 http://www.microchip.com/wwwproducts/Devices.aspx?dDocName=en548693
PIC18F87K22 http://www.microchip.com/wwwproducts/Devices.aspx?dDocName=en546891
PIC18F87K90 http://www.microchip.com/wwwproducts/Devices.aspx?dDocName=en547324
PIC18F87J50 http://www.microchip.com/wwwproducts/Devices.aspx?dDocName=en027172
PIC18F87J72 http://www.microchip.com/wwwproducts/Devices.aspx?dDocName=en550260
PIC18F87J90 http://www.microchip.com/wwwproducts/Devices.aspx?product=PIC18F87J90
PIC18F87J93 http://www.microchip.com/wwwproducts/Devices.aspx?product=PIC18F87J93
PIC18F97J94 http://www.microchip.com/wwwproducts/Devices.aspx?product=PIC18F97J94

DS90003124A-page 10  2015 Microchip Technology Inc.

Note the following details of the code protection feature on Microchip devices:
• Microchip products meet the specification contained in their particular Microchip Data Sheet.

• 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.

Information contained in this publication regarding device Trademarks

applications and the like is provided only for your convenience
and may be superseded by updates. It is your responsibility to
ensure that your application meets with your specifications.
MICROCHIP MAKES NO REPRESENTATIONS OR
WARRANTIES OF ANY KIND WHETHER EXPRESS OR
IMPLIED, WRITTEN OR ORAL, STATUTORY OR
OTHERWISE, RELATED TO THE INFORMATION,
INCLUDING BUT NOT LIMITED TO ITS CONDITION,
QUALITY, PERFORMANCE, MERCHANTABILITY OR
FITNESS FOR PURPOSE. Microchip disclaims all liability
arising from this information and its use. Use of Microchip
devices in life support and/or safety applications is entirely at
the buyer’s risk, and the buyer agrees to defend, indemnify and
hold harmless Microchip from any and all damages, claims,
suits, or expenses resulting from such use. No licenses are
conveyed, implicitly or otherwise, under any Microchip
intellectual property rights.
The Microchip name and logo, the Microchip logo, dsPIC,
FlashFlex, flexPWR, JukeBlox, KEELOQ, KEELOQ logo, Kleer,
LANCheck, MediaLB, MOST, MOST logo, MPLAB,
OptoLyzer, PIC, PICSTART, PIC32 logo, RightTouch, SpyNIC,
SST, SST Logo, SuperFlash and UNI/O are registered
trademarks of Microchip Technology Incorporated in the
U.S.A. and other countries.
The Embedded Control Solutions Company and mTouch are
registered trademarks of Microchip Technology Incorporated
in the U.S.A.
Analog-for-the-Digital Age, BodyCom, chipKIT, chipKIT logo,
CodeGuard, dsPICDEM, dsPICDEM.net, ECAN, In-Circuit
Serial Programming, ICSP, Inter-Chip Connectivity, KleerNet,
KleerNet logo, MiWi, MPASM, MPF, MPLAB Certified logo,
MPLIB, MPLINK, MultiTRAK, NetDetach, Omniscient Code
Generation, PICDEM, PICDEM.net, PICkit, PICtail,
RightTouch logo, REAL ICE, SQI, Serial Quad I/O, Total
Endurance, TSHARC, USBCheck, VariSense, ViewSpan,
WiperLock, Wireless DNA, and ZENA are trademarks of
Microchip Technology Incorporated in the U.S.A. and other
countries.
SQTP is a service mark of Microchip Technology Incorporated
in the U.S.A.
Silicon Storage Technology is a registered trademark of
Microchip Technology Inc. in other countries.
GestIC is a registered trademarks of Microchip Technology
Germany II GmbH & Co. KG, a subsidiary of Microchip
Technology Inc., in other countries.
All other trademarks mentioned herein are property of their
respective companies.
© 2015, Microchip Technology Incorporated, Printed in the
U.S.A., All Rights Reserved.
ISBN: 978-1-63276-998-5

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

== ISO/TS 16949 ==
are for its PIC® MCUs and dsPIC® DSCs, KEELOQ® code hopping
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.

 2015 Microchip Technology Inc. DS90003124A-page 11

 Worldwide Sales and Service
AMERICAS ASIA/PACIFIC ASIA/PACIFIC EUROPE
Corporate Office Asia Pacific Office India - Bangalore Austria - Wels
2355 West Chandler Blvd. Suites 3707-14, 37th Floor Tel: 91-80-3090-4444 Tel: 43-7242-2244-39
Chandler, AZ 85224-6199 Tower 6, The Gateway Fax: 91-80-3090-4123 Fax: 43-7242-2244-393
Tel: 480-792-7200 Harbour City, Kowloon Denmark - Copenhagen
India - New Delhi
Fax: 480-792-7277 Hong Kong Tel: 45-4450-2828
Tel: 91-11-4160-8631
Technical Support: Tel: 852-2943-5100 Fax: 45-4485-2829
Fax: 91-11-4160-8632
http://www.microchip.com/ Fax: 852-2401-3431
India - Pune France - Paris
support
Australia - Sydney Tel: 91-20-3019-1500 Tel: 33-1-69-53-63-20
Web Address:
Tel: 61-2-9868-6733 Fax: 33-1-69-30-90-79
www.microchip.com Japan - Osaka
Fax: 61-2-9868-6755 Germany - Dusseldorf
Atlanta Tel: 81-6-6152-7160
China - Beijing Tel: 49-2129-3766400
Duluth, GA Fax: 81-6-6152-9310
Tel: 86-10-8569-7000 Germany - Munich
Tel: 678-957-9614 Japan - Tokyo
Fax: 86-10-8528-2104 Tel: 49-89-627-144-0
Fax: 678-957-1455 Tel: 81-3-6880- 3770
China - Chengdu Fax: 49-89-627-144-44
Austin, TX Fax: 81-3-6880-3771
Tel: 86-28-8665-5511 Germany - Pforzheim
Tel: 512-257-3370 Korea - Daegu
Fax: 86-28-8665-7889 Tel: 49-7231-424750
Boston Tel: 82-53-744-4301
Westborough, MA China - Chongqing Fax: 82-53-744-4302 Italy - Milan
Tel: 774-760-0087 Tel: 86-23-8980-9588 Tel: 39-0331-742611
Korea - Seoul
Fax: 774-760-0088 Fax: 86-23-8980-9500 Fax: 39-0331-466781
Tel: 82-2-554-7200
Chicago China - Hangzhou Fax: 82-2-558-5932 or Italy - Venice
Itasca, IL Tel: 86-571-8792-8115 82-2-558-5934 Tel: 39-049-7625286
Tel: 630-285-0071 Fax: 86-571-8792-8116 Netherlands - Drunen
Malaysia - Kuala Lumpur
Fax: 630-285-0075 China - Hong Kong SAR Tel: 60-3-6201-9857 Tel: 31-416-690399
Cleveland Tel: 852-2943-5100 Fax: 60-3-6201-9859 Fax: 31-416-690340
Independence, OH Fax: 852-2401-3431 Poland - Warsaw
Malaysia - Penang
Tel: 216-447-0464 China - Nanjing Tel: 48-22-3325737
Tel: 60-4-227-8870
Fax: 216-447-0643 Tel: 86-25-8473-2460 Fax: 60-4-227-4068 Spain - Madrid
Dallas Fax: 86-25-8473-2470 Tel: 34-91-708-08-90
Philippines - Manila
Addison, TX China - Qingdao Fax: 34-91-708-08-91
Tel: 63-2-634-9065
Tel: 972-818-7423 Tel: 86-532-8502-7355 Fax: 63-2-634-9069 Sweden - Stockholm
Fax: 972-818-2924
Fax: 86-532-8502-7205 Tel: 46-8-5090-4654
Singapore
Detroit China - Shanghai Tel: 65-6334-8870 UK - Wokingham
Novi, MI Tel: 86-21-5407-5533 Fax: 65-6334-8850 Tel: 44-118-921-5800
Tel: 248-848-4000 Fax: 86-21-5407-5066
Taiwan - Hsin Chu Fax: 44-118-921-5820
Houston, TX
China - Shenyang Tel: 886-3-5778-366
Tel: 281-894-5983
Tel: 86-24-2334-2829 Fax: 886-3-5770-955
Indianapolis Fax: 86-24-2334-2393
Noblesville, IN Taiwan - Kaohsiung
China - Shenzhen Tel: 886-7-213-7830
Tel: 317-773-8323
Tel: 86-755-8864-2200
Fax: 317-773-5453 Taiwan - Taipei
Fax: 86-755-8203-1760 Tel: 886-2-2508-8600
Los Angeles
China - Wuhan Fax: 886-2-2508-0102
Mission Viejo, CA
Tel: 86-27-5980-5300 Thailand - Bangkok
Tel: 949-462-9523
Fax: 86-27-5980-5118 Tel: 66-2-694-1351
Fax: 949-462-9608
China - Xian Fax: 66-2-694-1350
New York, NY
Tel: 631-435-6000 Tel: 86-29-8833-7252
Fax: 86-29-8833-7256
San Jose, CA
Tel: 408-735-9110 China - Xiamen
Tel: 86-592-2388138
Canada - Toronto
Fax: 86-592-2388130
Tel: 905-673-0699
Fax: 905-673-6509 China - Zhuhai
Tel: 86-756-3210040
03/25/14
Fax: 86-756-3210049

DS90003124A-page 12  2015 Microchip Technology Inc.