MICROCHIP dsPIC33 Dual Watchdog Timer User Guide

MICROCHIP dsPIC33 Dual Watchdog Timer

INTRODUCTION

The dsPIC33/PIC24 Dual Watchdog Timer (WDT) is described in this section. Refer to Figure 1-
1 for a block diagram of the WDT.
The WDT, when enabled, operates from the internal Low-Power RC (LPRC) Oscillator clock source or selectable clock source in Run mode. The WDT can be used to detect system software malfunctions by resetting the device if the WDT is not cleared periodically in software. The WDT can be configured in Window mode or Non-Window mode. Various WDT time-out periods can be selected using the WDT post scaler. The WDT can also be used to wake the device from Sleep or Idle mode (Power Save mode).
The following are some of the key features of the WDT modules:

• Configuration or software controlled
• Separate user-configurable time-out periods for Run and Sleep/Idle modes
• Can wake the device from Sleep or Idle mode
• User-selectable clock source in Run mode
• Operates from LPRC in Sleep/Idle mode

Watchdog Timer Block Diagram

Note

1. WDT Reset behavior following a specific clock switch event is device dependent. Please refer to the “Watchdog Timer” section in the specific device data sheet for a description of clock switch events that clear the WDT.
2. The available clock sources are device-dependent.
   

WATCHDOG TIMER CONTROL REGISTERS

The WDT modules consist of the following Special Function Registers (SFRs):

• WDTCONL: Watchdog Timer Control Register
  This register is used to enable or disable the Watchdog Timer and enables or disables the windowed operation.

• WDTCONH: Watchdog Timer Key Register
  This register is used to clear the WDT to prevent a time-out.

• RCON: Reset Control Register(2)
  This register indicates the cause of a Reset.

Register Map

Table 2-1 provides a brief summary of the related WDT module registers. The corresponding registers appear after the summary, followed by a detailed description of each register.

Table 2-1: Watchdog Timers Register Map

3 )
WDTCONH| 15:0| WDTCLRKEY[15:0]
RCON ( 4 , 5 )| 15:0| TRAPR ( 1 )| IOPUWR ( 1 )| —| —| —| —| CM ( 1 )| VREGS ( 1 )| EXTR ( 1 )| SWR ( 1 )| —| WDTO| SLEEP| IDLE ( 1 )| BOR ( 1 )| POR ( 1 )

Legend: — = unimplemented, read as ‘0’

Note

1. These bits are not associated with the WDT module.
2. These bits are read-only and reflect the value of the Configuration bits.
3. These bits reflect the status for the Configuration bit if set. If the bit is clear, the value is controlled by software.
4. If the WDTEN[1:0] Configuration bits are ‘11’ (unprogrammed), the WDT is always enabled, regardless of the ON (WDTCONL[15]) bit setting.
5. All of the Reset status bits can be set or cleared in software. Setting one of these bits in software does not cause a device Reset.

Register 2-1: WDTCONL: Watchdog Timer Control Register

WDTWINEN ( 1 )
bit 7|  |  | bit 0

• bit 15 ON: Watchdog Timer Enable bit(1,2)
  1 = Enables the Watchdog Timer if it is not enabled by the device configuration
  0 = Disables the Watchdog Timer if it was enabled in software

• bit 14-13 Unimplemented: Read as ‘0’

• bit 12-8 RUNDIV[4:0]: WDT Run Mode Postscaler Status bits(3)

• bit 7-6 CLKSEL[1:0]: WDT Run Mode Clock Select Status bits(3,4)
  11 = LPRC Oscillator
  10 = FRC Oscillator
  01 = Reserved
  00 = SYSCLK

• bit 5-1 SLPDIV[4:0]: Sleep and Idle Mode WDT Postscaler Status bits(3)

• bit 0 WDTWINEN: Watchdog Timer Window Enable bit(1)
  1 = Enables Window mode
  0 = Disables Window mode

Note

1. These bits reflects the status of the Configuration bit if the bit is set. If the bit is cleared, the value is controlled by software.
2. The user’s software should not read or write the peripheral’s SFRs in the SYSCLK cycle immediately following the instruction that clears the module’s ON bit.
3. These bits are read-only and reflect the value of the Configuration bits.
4. The available clock sources are device-dependent. Please refer to the “Watchdog Timer” chapter in the specific device data sheet for availability.

Register 2-2: WDTCONH: Watchdog Timer Key Register

W-0                    W-0                  W-0                  W-0 W-0                   W-0                    W-0                  W-0

WDTCLRKEY[15:8]
bit 15 bit 8
W-0                    W-0                  W-0                  W-0 W-0                   W-0                    W-0                  W-0

WDTCLRKEY[7:0]
bit 7 bit 0

Legend

R = Readable bit W = Writable bit U = Unimplemented bit, read as ‘0’
-n = Value at POR ‘1’ = Bit is set ‘0’ = Bit is cleared x = Bit is unknown

• bit 15-0 WDTCLRKEY[15:0]: Watchdog Timer Clear Key bits
  To clear the Watchdog Timer to prevent a time-out, software must write the value, 0x5743, to this location using a single 16-bit write.

Register 2-3: RCON: Reset Control Register(2)

Legend

R = Readable bit W = Writable bit U = Unimplemented bit, read as ‘0’
-n = Value at POR ‘1’ = Bit is set ‘0’ = Bit is cleared x = Bit is unknown

• bit 15 TRAPR: Trap Reset Flag bit(1)
  1 = A Trap Conflict Reset has occurred
  0 = A Trap Conflict Reset has not occurred

• bit 14 IOPUWR: Illegal Opcode or Uninitialized W Register Access Reset Flag bit(1)
  1 = An illegal opcode detection, an illegal address mode or Uninitialized W register used as an Address Pointer caused a Reset
  0 = An illegal opcode or Uninitialized W register Reset has not occurred

• bit 13-12 Unimplemented: Read as ‘0’

• bit 11 VREGSF: Flash Voltage Regulator Standby During Sleep bit(1)
  1 = Flash voltage regulator is active during Sleep
  0 = Flash voltage regulator goes into Standby mode during Sleep

• bit 10 Unimplemented: Read as ‘0’

• bit 9 CM: Configuration Mismatch Flag bit(1)
  1 = A Configuration Mismatch Reset has occurred
  0 = A Configuration Mismatch Reset has not occurred

• bit 8 VREGS: Voltage Regulator Standby During Sleep bit(1)
  1 = Voltage regulator is active during Sleep
  0 = Voltage regulator goes into Standby mode during Sleep

• bit 7 EXTR: External Reset (MCLR) Pin bit(1)
  1 = A Master Clear (pin) Reset has occurred
  0 = A Master Clear (pin) Reset has not occurred

• bit 6 SWR: Software RESET (Instruction) Flag bit(1)
  1 = A RESET instruction has been executed
  0 = A RESET instruction has not been executed

• bit 5 Unimplemented: Read as ‘0’

• bit 4 WDTO: Watchdog Timer Time-out Flag bit
  1 = WDT time-out has occurred
  0 = WDT time-out has not occurred

• bit 3 SLEEP: Wake-up from Sleep Flag bit
  1 = Device has been in Sleep mode
  0 = Device has not been in Sleep mode

Note

1. These bits are not associated with the WDT module.
2. All of the Reset status bits can be set or cleared in software. Setting one of these bits in software does not cause a device Reset.

Register 2-3: RCON: Reset Control Register(2)

• bit 2 IDLE: Wake-up from Idle Flag bit(1)
  1 = Device has been in Idle mode
  0 = Device has not been in Idle mode

• bit 1 BOR: Brown-out Reset Flag bit(1)
  1 = A Brown-out Reset has occurred
  0 = A Brown-out Reset has not occurred

• bit 0 POR: Power-on Reset Flag bit(1)
  1 = A Power-on Reset has occurred
  0 = A Power-on Reset has not occurred

Note

1. These bits are not associated with the WDT module.
2. All of the Reset status bits can be set or cleared in software. Setting one of these bits in software does not cause a device Reset.

WATCHDOG TIMER OPERATION

The primary function of the Watchdog Timer (WDT) is to reset the processor in the event of a software malfunction, or wake-up the processor in the event of a time-out while in Sleep or Idle.
The WDT consists of two independent timers, one for operation in Run mode and the other for operation in Power Save mode. The clock source for the Run mode WDT is user-selectable.
Each timer has an independent, user-programmable postscaler. Both timers are controlled via a single ON bit; they cannot be operated independently.
If the WDT is enabled, the appropriate WDT counter will increment until it overflows or “times out”.
A WDT time-out in Run mode will generate a device Reset. To prevent a WDT Time-out Reset in Run mode, the user application must periodically service the WDT. A time-out in a Power Save mode will wake-up the device.

Note: The LPRC Oscillator is automatically enabled whenever it is being used as a WDT clock source and the WDT is enabled.

Modes of Operation

The WDT has two modes of operation: Non-Window mode and Programmable Window mode. In Non-Window mode, software must periodically clear the WDT at any time less than that of the WDT period to prevent a WDT Reset (Figure 3-1). Non- Window mode is selected by clearing the Watchdog Timer Window Enable (WDTWINEN) bit (WDTCONL[0]).
In Programmable Window mode, software can clear the WDT only when the counter is in its final window before a time-out occurs. Clearing the WDT outside this window will cause a device Reset (Figure 3-2). There are four window size options: 25%, 37.5%, 50% and 75% of the total WDT period. The window size is set in the device configuration. Programmable Window mode is not applicable when in Power Save mode.
Figure 3-1: Non-Window WDT Mode

Figure 3-2: Programmable Window WDT Mode

Watchdog Timer Programmable Window

The window size is determined by the Configuration bits, WDTWIN[1:0] and RWDTPS[4:0]. In the Programmable Window mode (WDTWINEN = 1), the WDT should be cleared based on the setting of the Window Size Configuration bits, WDTWIN[1:0] (see Figure 3-2). These bit settings are:

• 11 = WDT window is 25% of the WDT period
• 10 = WDT window is 37.5% of the WDT period
• 01 = WDT window is 50% of the WDT period
• 00 = WDT window is 75% of the WDT period

If the WDT is cleared before the allowed window, or if the WDT is allowed to time-out, a device Reset occurs. The Window mode is useful for resetting the device during unexpected quick or slow execution of a critical portion of the code. Window operation only applies to the WDT Run mode. The WDT Sleep mode always operates in Non-Window mode.

Enabling and Disabling the WDT

The WDT is enabled or disabled by the device configuration, or controlled through software by writing a ‘1’ to the ON bit (WDTCONL[15]). See Register 2-1 for more details.

DEVICE CONFIGURATION CONTROLLED WDT

If the FWDTEN Configuration bit is set, the WDT is always enabled. The ON control bit (WDTCONL[15]) will reflect this by reading a ‘1’. In this mode, the ON bit cannot be cleared in software. The FWDTEN Configuration bit will not be cleared by any form of Reset. To disable the WDT, the configuration must be rewritten to the device. Window mode is enabled by clearing the WINDIS Configuration bit.

Note: The WDT is enabled by default on an unprogrammed device.

SOFTWARE CONTROLLED WDT

If the FWDTEN Configuration bit is ‘0’, the WDT module can be enabled or disabled (the default condition) by software. In this mode, the ON bit (WDTCONL[15]) reflects the status of the WDT under software control; ‘1’ indicates the WDT module is enabled and ‘0’ indicates it is disabled.

WDT Postscaler

The WDT has two user-programmable postscalers: one for Run mode and the other for Power Save mode. The RWDTPS[4:0] Configuration bits set the Run mode postscaler and the SWDTPS[4:0] Configuration bits set the Power Save mode postscaler.

Note: The Configuration bit names for the postscaler value may vary. Refer to the specific device data sheet for details.

DEVICE CONFIGURATION CONTROLLED WINDOW MODE

Window mode can be enabled by clearing the Configuration bit, WINDIS. When the WDT Window mode is enabled by the device configuration, the WDTWINEN bit (WDTCONL[0]) will be set and cannot be cleared by software.

SOFTWARE CONTROLLED WINDOW MODE

If the WINDIS Configuration bit is ‘1’, the WDT Programmable Window mode can be enabled or disabled by the WDTWINEN bit (WDTCONL[0]). A ‘1’ indicates that Programmable Window mode is enabled and a ‘0’ indicates that Programmable Window mode is disabled.

WDT Postscaler and Period Selection

The WDT has two independent 5-bit postscalers, one for Run mode and the other for Power Save mode, to create a wide variety of time-out periods. The postscalers provide 1:1 through 1:2,147,483,647 divider ratios (see Table 3-1). The postscaler settings are selected using the device configuration. The WDT time-out period is selected by the combination of the WDT clock source and the postscaler. Refer to Equation 3-1 for the WDT period calculation

Equation 3-1: WDT Time-out Period Calculation

WDT Time-out Period = (WDT Clock Period) • 2Postscaler

In Sleep mode, the WDT clock source is LPRC and the time-out period is determined by the SLPDIV[4:0] bits setting. The LPRC, with a nominal frequency of 32 kHz, creates a nominal time-out period for the WDT of 1 millisecond when the postscaler is at the minimum value.
In Run mode, the WDT clock source is selectable. The time-out period is determined by the WDT clock source frequency and the RUNDIV[4:0] bits setting.

Note: The WDT module time-out period is directly related to the frequency of the WDT clock source. The nominal frequency of the clock source is device- dependent. The frequency may vary as a function of the device operating voltage and temperature. Please refer to the specific device data sheet for clock frequency specifications. The available clock sources for Run mode are device-dependent. Please refer to the “Watchdog Timer” chapter in the specific device data sheet for available sources.

WDT Operation in Run Mode

When the WDT expires or is cleared outside the window in Window mode, a device Reset is generated when the NMI counter expires.

WDT Clock Sources

The WDT Run mode clock source is user-selectable. The clock source is selected by the RCLKSEL[1:0] (FWDT[6:5]) device bits. The WDT Power Save mode uses LPRC as the clock source.

Resetting the WDT(1)

The Run mode WDT counter is cleared by any of the following:

• Any Device Reset
• Execution of a DEBUG Command
• Detection of a Correct Write Value (0x5743) to the WDTCLRKEYx bits (WDTCONH[15:0]) (refer to Example 3-1)
• A Clock Switch:(2)
• Firmware initiated clock switch
• Two-Speed Start-up
• Fail-Safe Clock Monitor (FSCM) event
• Clock switch after wake from Sleep when an automatic clock switch occurs due to oscillator configuration and Two-Speed Start-up is enabled by the device configuration
  The Sleep mode WDT counter is reset upon entry into Sleep.

Note

1. The Run mode WDT is not reset when the device enters a Power-Saving mode.
2. WDT Reset behavior following a specific clock switch event is device-dependent. Please refer to the “Watchdog Timer” section in the specific device data sheet for a description of clock switch events that clear the WDT.

Example 3-1: Sample Code to Clear the WDT

Table 3-1: WDT Time-out Period Settings

INTERRUPTS AND RESET GENERATION

WDT Time-out in Run Mode

When the WDT times out in Run mode, a device Reset is generated.
Firmware can determine if the cause of the Reset was the WDT time-out in Run mode by testing the WDTO bit (RCON[4]).

Note: Refer to the “Resets” and “Interrupt Controller” chapters in the specific device data sheet. Also, refer to the “Reset” (DS39712) and “Interrupts” (DS70000600) sections in the “dsPIC33/PIC24 Family Reference Manual” for details.

WDT Time-out in Power Save Mode

When the WDT module times out in Power Save mode, it wakes the device and the WDT Run mode resumes counting.
To detect a WDT wake-up, the WDTO bit (RCON[4]), SLEEP bit (RCON[3]) and IDLE bit (RCON[2]) can be tested. If the WDTO bit is ‘1’, the event was due to a WDT time-out in a Power Save mode. The SLEEP and IDLE bits can then be tested to determine if the WDT event occurred while the device was awake or if it was in Sleep or Idle mode.

Note: Refer to the “Resets” and “Interrupt Controller” chapters in the specific device data sheet. Also, refer to the “Reset” (DS39712) and “Interrupts” (DS70000600) sections in the “dsPIC33/PIC24 Family Reference Manual” for details.

Wake from Power Save Mode by a Non-WDT Event

When the device is awakened from a Power Save mode by a non-WDT NMI interrupt, the Power Save mode WDT is held in Reset and the WDT Run mode continues counting from the pre-power save count value.

RESETS CAUSE AND EFFECT

Determining the Cause of a Reset

To determine if a WDT Reset has occurred, the WDTO bit (RCON[4]) can be tested. If the WDTO bit is ‘1’, the Reset was due to a WDT time-out in Run mode. Software should clear the WDTO bit to allow correct determination of the source of a subsequent Reset.

Effects of Various Resets

Any form of device Reset will clear the WDT. The Reset will return the WDTCONH/L registers to the default value and the WDT will be disabled unless it is enabled by the device configuration.

Note: After a device Reset, the WDT ON bit (WDTCONL[15]) will reflect the state of the FWDTEN bit (FWDT[15]).

OPERATION IN DEBUG AND POWER-SAVING MODES

WDT Operation in Power-Saving Modes

The WDT, if enabled, will continue operation in Sleep mode or Idle mode and can be used to wake-up the device. This allows the device to remain in Sleep or Idle mode until the WDT expires or another interrupt wakes the device. If the device does not re-enter Sleep or Idle mode following a wake-up, the WDT must be disabled or periodically serviced to prevent a WDT Run mode NMI.

WDT OPERATION IN SLEEP MODE

The WDT module may be used to wake the device from Sleep mode. When entering Sleep mode, the WDT Run mode counter stops counting and the Power Save mode WDT begins counting from the Reset state, until it times out, or the device is woken up by an interrupt. When the WDT times out in Sleep mode, the device wakes up and resumes code execution, sets the WDTO bit (RCON[4]) and resumes the Run mode WDT.

WDT OPERATION IN IDLE MODE

The WDT module may be used to wake the device from Idle mode. When entering Idle mode, the WDT Run mode counter stops counting and the Power Save mode WDT begins counting from the Reset state, until it times out, or the device is woken up by an interrupt. The device wakes up and resumes code execution, sets the WDTO bit (RCON[4]) and resumes the Run mode WDT.

Time Delays During Wake-up

There will be a time delay between the WDT event in Sleep and the beginning of code execution. The duration of this delay consists of the start-up time for the oscillator in use. Unlike a wake-up from Sleep mode, there are no time delays associated with wake-up from Idle mode. The system clock is running during Idle mode; therefore, no start-up delays are required at wake-up.

WDT Clock Sources in Power Save Mode

The WDT clock source for Power Save mode is not user-selectable. The clock source is LPRC.

WDT Operation in Debug Mode

The WDT should be disabled in Debug mode to prevent a time-out.

RELATED APPLICATION NOTES

This section lists application notes that are related to this section of the manual. These application notes may not be written specifically for the dsPIC33/PIC24 device family, but the concepts are pertinent and could be used with modification and possible limitations. The current application notes related to the Dual Watchdog Timer module are:

Note: Visit the Microchip website (www.microchip.com) for additional application notes and code examples for the dsPIC33/PIC24 family of devices.

REVISION HISTORY

Revision A (March 2016)
This is the initial version of this document.
Revision B (June 2018)
Changes device family name to dsPIC33/PIC24.
Removes the Advance Information watermark from page footers.
Revision C (February 2022)
Updates Table 2-1 and Table 3-1.
Updates Register 2-1.
Updates Section 3.1 “Modes of Operation”, Section 3.2 “Watchdog Timer Programmable Window”, Section 3.3 “Enabling and Disabling the WDT”, Section 3.4.1 “Device
Configuration Controlled Window Mode”, Section 3.4.2 “Software Controlled Window Mode”, Section 3.7 “WDT Clock Sources” and Section 6.1.2 “WDT Operation in Idle Mode”.
The Watchdog Timer standard uses the terminology “Master” and “Slave.” The equivalent Microchip terminology used in this document is “Main” and “Secondary”, respectively

Note the following details of the code protection feature on Microchip products:

• Microchip products meet the specifications contained in their particular Microchip Data Sheet.
• Microchip believes that its family of products is secure when used in the intended manner, within operating specifications, and under normal conditions.
• Microchip values and aggressively protects its intellectual property rights. Attempts to breach the code protection features of Microchip product is strictly prohibited and may violate the Digital Millennium Copyright Act.
• Neither Microchip nor any other semiconductor manufacturer can guarantee the security of its code. Code protection does not mean that we are guaranteeing the product is “unbreakable”. Code protection is constantly evolving. Microchip is committed to continuously improving the code protection features of our products.

This publication and the information herein may be used only with Microchip products, including to design, test, and integrate Microchip products with your application. Use of this information in any other manner violates these terms. Information regarding device applications 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. Contact your local Microchip sales office for additional support or, obtain additional support at
https://www.microchip.com/en-us/support/design-help/client-supportservices.
THIS INFORMATION IS PROVIDED BY MICROCHIP “AS IS”. 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 ANY IMPLIED WARRANTIES OF NONINFRINGEMENT, MERCHANTABILITY, AND FITNESS FOR A PARTICULAR PURPOSE, OR WARRANTIES RELATED TO ITS CONDITION, QUALITY, OR PERFORMANCE.

IN NO EVENT WILL MICROCHIP BE LIABLE FOR ANY INDIRECT, SPECIAL, PUNITIVE, INCIDENTAL, OR CONSEQUENTIAL LOSS, DAMAGE, COST, OR EXPENSE OF ANY KIND WHATSOEVER RELATED TO THE INFORMATION OR ITS USE, HOWEVER CAUSED, EVEN IF MICROCHIP HAS BEEN ADVISED OF THE POSSIBILITY OR THE DAMAGES ARE FORESEEABLE. TO THE FULLEST EXTENT ALLOWED BY LAW, MICROCHIP’S TOTAL LIABILITY ON ALL CLAIMS IN ANY WAY RELATED TO THE INFORMATION OR ITS USE WILL NOT EXCEED THE AMOUNT OF FEES, IF ANY, THAT YOU HAVE PAID DIRECTLY TO MICROCHIP FOR THE INFORMATION.
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 unless otherwise stated.

Trademarks

The Microchip name and logo, the Microchip logo, Adaptec, AnyRate, AVR, AVR logo, AVR Freaks, BesTime, BitCloud, CryptoMemory, CryptoRF, dsPIC, flexPWR, HELDO, IGLOO, JukeBlox, KeeLoq, Kleer, LANCheck, LinkMD, maXStylus, maXTouch, MediaLB, megaAVR, Microsemi, Microsemi logo, MOST, MOST logo, MPLAB, OptoLyzer, PIC, picoPower, PICSTART, PIC32 logo, PolarFire, Prochip Designer, QTouch, SAM-BA, SenGenuity, SpyNIC, SST, SST Logo, SuperFlash, Symmetricom, SyncServer, Tachyon, TimeSource, tinyAVR, UNI/O, Vectron, and XMEGA are registered trademarks of Microchip Technology Incorporated in the U.S.A. and other countries. AgileSwitch, APT, ClockWorks, The Embedded Control Solutions Company, EtherSynch, Flashtec, Hyper Speed Control, HyperLight Load, IntelliMOS, Libero, motorBench, mTouch, Powermite 3, Precision Edge, ProASIC, ProASIC Plus, ProASIC Plus logo, QuietWire, SmartFusion, SyncWorld, Temux, TimeCesium, TimeHub, TimePictra, TimeProvider, TrueTime, WinPath, and ZL are registered trademarks of Microchip Technology Incorporated in the U.S.A. Adjacent Key Suppression, AKS, Analog-for-the-Digital Age, Any Capacitor, AnyIn, AnyOut, Augmented Switching, BlueSky, BodyCom, CodeGuard, CryptoAuthentication, CryptoAutomotive, CryptoCompanion, CryptoController, dsPICDEM, dsPICDEM.net, Dynamic Average Matching, DAM, ECAN, Espresso T1S, EtherGREEN, GridTime, IdealBridge, In-Circuit Serial Programming, ICSP, INICnet, Intelligent Paralleling, Inter-Chip Connectivity, JitterBlocker, Knob-on-Display, maxCrypto, maxView, memBrain, Mindi, MiWi, MPASM, MPF, MPLAB Certified logo, MPLIB, MPLINK, MultiTRAK, NetDetach, NVM Express, NVMe, Omniscient Code Generation, PICDEM, PICDEM.net, PICkit, PICtail, PowerSmart, PureSilicon, QMatrix, REAL ICE, Ripple Blocker, RTAX, RTG4, SAM-ICE, Serial Quad I/O, simpleMAP, SimpliPHY, SmartBuffer, SmartHLS, SMART-I.S., storClad, SQI, SuperSwitcher, SuperSwitcher II, Switchtec, SynchroPHY, Total Endurance, TSHARC, USBCheck, VariSense, VectorBlox, VeriPHY, ViewSpan, WiperLock, XpressConnect, 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.
The Adaptec logo, Frequency on Demand, Silicon Storage Technology, Symmcom, and Trusted Time are registered trademarks of Microchip Technology Inc. in other countries. GestIC is a registered trademark 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.
© 2016-2022, Microchip Technology Incorporated and its
subsidiaries.
All Rights Reserved.
ISBN: 978-1-5224-9893-3

Worldwide Sales and Service

AMERICAS
Corporate Office
2355 West Chandler Blvd.
Chandler, AZ 85224-6199
Tel: 480-792-7200
Fax: 480-792-7277
Technical Support:
http://www.microchip.com/support
Web Address: www.microchip.com

Read User Manual Online (PDF format)

Download This Manual (PDF format)

Download this manual  >>