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
applications and t he lik e is provided only for your convenience
and may be su perseded by upda t es . It is y our 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 supp ort and/or safety ap plications is entir ely at
the buyer’s risk, and the buyer agrees to defend, indemnify and
hold harmless M icrochip from any and all dama ges, claims,
suits, or expenses re sulting from such use. No licens es are
conveyed, implicitly or otherwise, under any Microchip
intellectual property rights.
Trademarks
The Microchip name and logo, the Microchip logo, Accuron,
dsPIC, K
EELOQ, KEELOQ logo, MPLAB, PIC, PICmicro,
PICSTART, rfPIC, SmartShunt and UNI/O are registered
trademarks of Microchip Technology Incorporated in the
U.S.A. and other countries.
FilterLab, Linear Active Thermistor, MXDEV, MXLAB,
SEEVAL, SmartSensor and The Embedded Control Solutions
Company are registered trademarks of Microchip Technology
Incorporated in the U.S.A.
Analog-for-the-Digital Age, Application Maestro, CodeGuard,
dsPICDEM, dsPICDEM.net, dsPICworks, dsSPEAK, ECAN,
ECONOMONITOR, FanSense, In-Circuit Serial
Programmin g , IC SP, ICEPIC, Mindi, MiW i , MPASM, MPLAB
Certified logo, MPLIB, MPLINK, mTouch, PICkit, PICDEM,
PICDEM.net, PICtail, PIC
32
logo, PowerCal, PowerInfo,
PowerMate, PowerT ool, REAL ICE, rfLAB, Select Mode, Total
Endurance, WiperLock 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.
All other trademarks mentioned herein are property of their
respective companies.
Microchip received ISO/TS-16949:2002 certification for its worldwide
headquarters, design and wafer fabrication facilities in Chandler and
Tempe, Arizona; Gresham, Oregon and design centers in California
and India. The Company’s quality system processes and procedures
are for its PIC
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.
6.0Flash Pro g ram Memory.............................................................. ................................................................................................87
8.0Data EEPR OM Mem o ry................ .................................................................. ......................................................................... 111
9.08 x 8 Hardware Multip lier.............................. ........................... ........................................ ......................................................... 117
19.0 Master Synchronous Serial Port (MSSP) Module ....................................................................................................................205
25.0 Special Features of the CPU.................................................................. ..................................................................................297
26.0 Instruction Set Summary..........................................................................................................................................................321
27.0 Development Support. .............................................................................................................................................................. 371
Appendix D: Migration From Baseline to Enhanced Devices............................................................................................................. 426
Appendix E: Migration From Mid-Range to Enhanced Devices......................................................................................................... 427
Appendix F: Migration From High-End to Enhanced Devices.................................................................. .. ........................................ 427
Index .................................................................................................................................................................................................. 429
The Microchip Web Site.................. ................................................................................................................................................... 441
Customer Change Notification Service .............................................................................................................................................. 441
PIC18F8722 Family Product Identification System............................................................................................................................443
It is our intention to provide our valued customers with the best documentation possible to ensure successful use of your Microchip
products. To this end, we will continue to improve our publications to better suit your needs. Our publications will be refined and
enhanced as new volumes and updates are introduced.
If you have any questions or c omm ents regarding t his publication, please contact the Marketing Communications Department via
E-mail at docerrors@.microchip.com or fax the Reader Response Form in the back of this data sheet to (480) 792-4150. We
welcome your feedback.
Most Current Data Sheet
To obtain the most up-to-date version of this data sheet, please register at our Worldwide Web site at:
http://www.microchip.com
You can determine the version of a data sheet by examining its literature number found on the bottom outside corner of any page.
The last character of the literature number is the version number, (e.g., DS30000A is version A of document DS30000).
Errata
An errata sheet, describing minor operational differences from the data sheet and recommended workarounds, may exist for current
devices. As device/documentation issues become known to us, we will publish an errata sheet. The errata will specify the revision
of silicon and revision of document to which it applies.
To determine if an errata sheet exists for a particular device, please check with one of the following:
• Microchip’s Worldwide Web site; http://www.microchip.com
• Your local Microchip sales office (see last page)
When contacting a sales office, please specify which device, revision of silicon and data sheet (include literature number) you are
using.
Customer Notification System
Register on our web site at www.microchip.com to receive the most current information on all of our products.
This document co nta i ns dev ic e spec if i c in for m at ion fo r
the following devices:
• PIC18F6527• PIC18LF6527
• PIC18F6622• PIC18LF6622
• PIC18F6627• PIC18LF6627
• PIC18F6722• PIC18LF6722
• PIC18F8527• PIC18LF8527
• PIC18F8622• PIC18LF8622
• PIC18F8627• PIC18LF8627
• PIC18F8722• PIC18LF8722
This family offers the advantages of all PIC18 microcontrollers – namely, high computa tional performance at
an economical price – with the addition of highendurance, Enhanced Flash program memory . On top of
these features, the PIC18F8722 family introduces
design enhancements that make these microcontrollers
a logical choice for many high-performance, power
sensitive applications.
1.1New Core Features
1.1.1nanoWatt TECHNOLOGY
All of the devices in the PIC18 F8722 fami ly incorp orate
a range of features that can significantly reduce power
consumption during operation. Key items include:
• Alternate Run Modes: By clocking the controller
from the Timer1 source or the internal oscillator
block, power consumption during code execution
can be significantly redu ce d.
• Multiple Idle Modes: The controller can also run
with its CPU core disabled but the peripherals still
active. In these st ates, powe r consumpt ion can be
reduced even further.
• On-the-fly Mode Switching: The powermanaged modes a re invo ked b y user code durin g
operation, allowing the user to incorporate powersaving ideas into their application’s software
design.
• Low Consumption in Key Modules: The
power requirements for both Timer1 and the
Watchdog Timer are minimized. See
Section 28.0 “Electrical Characteristics”
for values.
1.1.2EXPANDED MEMORY
The PIC18F8722 family provides ample room for
application code and includes members with 48, 64,
96 or 128 Kbytes of code space.
• Data RAM and Data EEPROM: The PIC18F872 2
family also p rov ide s ple nty o f room for applicati on
data. The devices have 3936bytes of data RAM,
as well as 1024 bytes of data EEPROM, for long
term retention of nonvolatile data.
• Memory Endurance: The Enhanced Flash cells
for both program memory and data EEPROM are
rated to last for many thousands of erase/write
cycles, up to 100,000 for program memory and
1,000,000 for EEPROM. Data retention without
refresh is conservatively estimated to be greater
than 40 years.
1.1.3MULTIPLE OSCILLATOR OPTIONS
AND FEATURES
All of the devices in the PIC18F8722 family offer ten
different osci llator option s, all owin g users a w ide range
of choices in developing application hardware. These
include:
• Four Crystal modes, using crystals or ceramic
resonators
• Two External Clock modes, offering the option of
using two pins (oscillator input and a divide-by-4
clock output) or one pin (oscillator input, with the
second pin reassigned as general I/O)
• Two External RC Oscillator modes with the same
pin options as the External Clock modes
• An internal oscillator block which provides an
8 MHz clock and an INTRC source (approximately 31 kHz), as well as a range of 6 user
selectable cl ock fre quenc ies, be tween 125 kHz to
4 MHz, for a total of 8 clock frequencies. This
option frees the two oscillator pins for use as
additional general purpose I/O.
• A Phase Lock Loop (PLL) frequency multiplier,
available to both the high-speed crystal and internal oscillator m odes, which a llows clo ck speeds o f
up to 40 MHz. Used with the internal oscillator, the
PLL gives users a complete selection of clock
speeds, from 31 kHz to 32 MHz – all without us ing
an external crystal or clock circuit.
Besides its availability as a clock source, the internal
oscillator block provides a stable reference source that
gives the family additional features for robust operation:
• Fail-Safe Clock Monitor: This option co nst ant ly
monitors the m ai n c l oc k source against a reference
signal provide d by th e internal osci ll at or. If a cl oc k
failure occu rs , t he co nt rol le r i s s witc h ed to th e
internal oscillator block, allowing for continued
low-speed operation or a safe application shutdown.
• Two-Speed Start-up: This option allows the
internal oscillator to serve as the clock source
from Power-on Reset, or wake-up from Sleep
mode, until the primary clock source is available.
1.1.4EXTERNAL MEMORY INTERFACE
In the unlikely event that 128 Kbytes of program
memory is inadequate for an application, the
PIC18F8527/8622/8627/8722 members of the family
also implement an external memory interface. This
allows the controller’s internal program counter to
address a memory space of up to 2 Mbytes,
permitting a level of data access that few 8-bit devices
can claim.
With the addition of new operat ing mod es, the ext erna l
memory interface offers many new options, including:
• Operating the microcontrol le r entirel y from
external memory
• Using combinations of on-chip and external
memory, up to the 2-Mbyte limit
• Using external Flash memory for reprogrammable
application code or large data tables
• Using external RAM devices for storing large
amounts of variable data
1.1.5EASY MIGRATION
Regardless of the memory size, all devices share the
same rich set of peripherals, allowing for a smooth
migration path as applications grow and evolve.
The consistent pinout scheme used throughout the
entire family also aids in migrating to the next larger
device. Thi s is true when mo ving between the 64-pin
members, between the 80-pin members, or even
jumping from 64-pin to 80-pin devices.
1.2Other Special Features
• Communications: The PIC18F8722 family
incorporates a range of serial communication
peripherals, including 2 independent Enhanced
USARTs and 2 Master SSP modules capable of
both SPI and I
operation. Also, one of the general purpose I/O
ports can be reconfigured as an 8-bit Parallel
Slave Port for direct processor-to-processor
communications.
• CCP Modules: All devices in the family
incorporate two Capture/Compare/PWM (CCP)
modules and three Enhanced CCP (ECCP)
modules to maximize flexibility in control
applications. Up to four different time bases may
be used to perform severa l di f fe rent operations at
once. Each of the three ECCP modul es offer up to
four PWM outputs, allowing for a total of
12 PWMs. The ECCPs also offer many beneficial
features, including polarity selection,
Programmable Dead-Time, Auto-Shutdown and
Restart and Half-Bridge and Full-Bridge
Output modes.
• Self-Programmability: These devices can write
to their own program memory spaces under
internal software control. By using a bootloader
routine located in the protected boot block at the
top of program memory, it becomes possible to
create an application that can update itself in the
field.
• Extended Instruction Set: The PIC18F8722
family introduces an optional extension to the
PIC18 instruction set, which adds 8 new instructions and an Indexed Addressing mode. This
extension, enabled as a device configuration
option, has been specifi cally des igned to opti mize
re-entrant applica tion code original ly deve loped in
high-level language s, su ch as C.
• 10-bit A/D Converter: This module incorporates
programmable acquisition time, allowing for a
channel to be selected and a conversion to be
initiated without w ait ing for a sampling period and
thus, reduce code overhead.
• Extended Watchdog Timer (WDT): This
enhanced version in corpora tes a 16 -bit pre scale r,
allowing an exte nded time-o ut rang e that is s ta ble
across operating voltage and temperature. See
Section 28.0 “Electrical Characteristics” for
time-out periods.
Devices in the PIC18F8722 family are available in
64-pin and 80-pin packages. Block diagrams for the
two groups are shown in Figure 1-1 and Figure 1-2.
The devices are differentiated from each other in five
ways:
1.Flash program memory (48 Kbytes for
PIC18F6527/8527 devices, 64 Kbytes for
PIC18F6622/8622 devices, 96 Kbytes for
PIC18F6627/8627 devices and 128 Kbytes for
All other features fo r device s in this family are identi cal.
These are summarized in Table1-2 and Table 1-2.
The pinouts for all devices are listed in Table 1-3 and
Table 1-4.
Like all Microchip PIC18 devices, members of the
PIC18F8722 family are available as both standard and
low-voltage devices. Standard devices with Enhanced
Flash memory, designated with an “F” in the part
number (such as PIC18F6627), accommodate an
operating V
DD range of 4.2V to 5.5V. Low-voltage
parts, designated by “LF” (such as PIC18LF6627),
function over an extended VDD range of 2.0V to 5.5V.
PIC18F6722/8722).
2. A/D channels (12 for 64-pin devices, 16 for
80-pin devices).
3. I/O ports (7 bidirectional por ts on 64-pin de vices,
9 bidirectional ports on 80-pin devices).
4. External Memory Bus, configurable for 8 and
16-bit operation, is available on PIC18F8527/
8622/8627/8722 devices.
T ABLE 1-1:DEVICE FEATURES (PIC18F6527/6622/6627/6722)
FeaturesPIC18F6527PIC18F6622PIC18F6627PIC18F6722
Operating FrequencyDC – 40 MHzDC – 40 MHzDC – 40 MHzDC – 40 MHz
Program Memory (Bytes)48K64K96K128K
Program Memory (Instructions)24576327684915265536
Data Memory (Bytes)3936393639363936
Data EEPROM Memory (Bytes)1024102410241024
Interrupt Sources28282828
I/O PortsPorts A, B, C, D, E, F, G Ports A, B, C, D, E, F, G Ports A, B, C, D, E, F, G Ports A, B, C, D, E, F, G
Timers5555
Capture/Co mp a re/PWM
Modules
Enhanced Capture/Compare/
PWM Modules
Enhanced USART2222
Serial CommunicationsMSSP,
Parallel Communications (PSP)Y esY esYe sYes
10-bit Analog-to-Digit al Modul e12 Input Channels12 Input Channels12 In put Cha nnel s12 Input Chann els
Resets (and Delays)POR, BOR,
Operating FrequencyDC – 40 MHzDC – 40 MHzDC – 40 MHzDC – 40 MHz
Program Memory (Bytes)48K64K96K128K
Program Memory (Instructions)24576327684915265536
Data Memory (Bytes)3936393639363936
Data EEPROM Memo ry (Byte s)1024102410241024
Interrup t Sou r ce s29292929
I/O PortsPorts A, B, C, D, E,
F, G, H, J
Timers5555
Capture/Compare/PWM
Modules
Enhanced Capture/Comp are/
PWM Modules
Enhanced USART2222
Serial CommunicationsMSSP,
Parallel Communications
(PSP)
10-bit Analog-to-Digit al Modul e16 Input Channels16 Input Chann els16 Input Channels16 Input Channels
Resets (and Delays)POR, BOR,
Note 1: Default assignment for ECCP2 when Conf iguration bit, CCP2MX, is set.
/VPP
ST = Schmitt Trigger input with CMOS levels Analog= Analog input
I= Input O= Output
P= Power I
2: Alternate assignment for ECCP2 when Configuration bit, CCP2MX, is cleared.
39
40
7
I
I
P
I
I
CMOS
I/O
O
O
I/O
2
C™= I2C/SMBus input buffer
Master Clear (input) or programming voltage (input).
ST
ST
ST
TTL
—
—
TTL
Digital input.
Master Clear (Reset) input. This pin is an active-low
Reset to the device.
Programming voltage input.
Oscillator crystal or external clock input.
Oscillator crystal input or external clock source input.
ST buffer when configured in RC mode, CMOS
otherwise.
External clock source input. Always associated
with pin function OSC1. (See related OSC1/CLKI,
OSC2/CLKO pins.)
General purpose I/O pin.
Oscillator crystal or clock output.
Oscillator crystal output. Connects to crystal or
resonator in Crystal Oscillator mode.
In RC mode, OSC2 pin outputs CLKO, which has
1/4 the frequency of OSC1 and denotes the
instruction cycle rate.
General purpose I/O pin.
Note 1: Alternate assignment for ECCP2 when Configuration bit, CCP2MX, is cleared (all operating modes except
/VPP
ST = Schmitt Trigger input with CMOS levels Analog= Analog input
I= Input O= Output
P= Power I
Microcontroller mode).
2: Default assignment fo r ECCP2 in all operating modes (CCP2MX is set).
3: Alternate assignment for ECCP2 when CCP2MX is cleared (Microcontroller mode only).
4: Default assignment for P1B/P1C/P3B/P3C (ECCPMX is set).
5: Alternate assignment for P1B/P1C/P3B/P3C (ECCPMX is clear).
49
50
9
I
I
P
I
I
CMOS
I/O
O
O
I/O
2
C™/SMB= I2C/SMBus input buffer
Master Clear (input) or programming voltage (input).
ST
ST
ST
TTL
—
—
TTL
Digital input.
Master Clear (Reset) input. This pin is an active-low
Reset to the device.
Programming voltage input.
Oscillator crystal or external clock input.
Oscillator crystal input or external clock source input.
ST buffer when configured in RC mode, CMOS
otherwise.
External clock source input. Always associated with
pin function OSC1. (See related OSC1/CLKI,
OSC2/CLKO pins.)
General purpose I/O pin.
Oscillator crysta l or clock output.
Oscillator crystal output. Connects to crystal or
resonator in Crystal Oscillator mode.
In RC mode, OSC2 pin out put s CLKO, whi ch has 1/4 the
frequency of OSC1 and denotes the
instruction cycle rate.
General purpose I/O pin.
Note 1: Alternate assignment for ECCP2 when Configuration bit, CCP2MX, is cleared (all operating modes except
REF-
REF-
REF+
REF+
ST = Schmitt Trigger input with CMOS levels Analog= Analog input
I= Input O= Output
P= Power I
Microcontroller mode).
2: Default assignment fo r ECCP2 in all operating modes (CCP2MX is set).
3: Alternate assignment for ECCP2 when CCP2MX is cleared (Microcontroller mode only).
4: Default assignment for P1B/P1C/P3B/P3C (ECCPMX is set).
5: Alternate assignment for P1B/P1C/P3B/P3C (ECCPMX is clear).
30
29
28
27
34
33
I/O
I/O
I/O
I/O
I/OIST/ODSTDigital I/O. Open-drain when configured as output.
I/O
TTL
I
Analog
TTL
I
Analog
TTL
I
Analog
I
Analog
TTL
I
Analog
I
Analog
TTL
I
Analog
I
Analog
2
C™/SMB= I2C/SMBus input buffer
Digital I/O.
Analog input 0.
Digital I/O.
Analog input 1.
Digital I/O.
Analog input 2.
A/D reference voltage (low) input.
Digital I/O.
Analog input 3.
A/D reference voltage (high) input.
Timer0 external clock input.
Digital I/O.
Analog input 4.
High/Low-Voltage Detect inpu t.
ST = Schmitt Trigger input with CMOS levels Analog= Analog input
I= Input O= Output
P= Power I
Note 1: Alternate assignment for ECCP2 when Configuration bit, CCP2MX, is cleared (all operating modes except
Microcontroller mode).
2: Default assignment fo r ECCP2 in all operating modes (CCP2MX is set).
3: Alternate assignment for ECCP2 when CCP2MX is cleared (Microcontroller mode only).
4: Default assignment for P1B/P1C/P3B/P3C (ECCPMX is set).
5: Alternate assignment for P1B/P1C/P3B/P3C (ECCPMX is clear).
57
56
55
54
53
52
47
I/O
I/O
I/O
O
O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
TTL
I
I
I
I
I
I
I
2
ST
TTL
ST
TTL
ST
—
—
TTL
TTL
TTL
TTL
ST
TTL
TTL
ST
TTL
TTL
ST
C™/SMB= I2C/SMBus input buffer
Digital I/O.
External interrupt 1.
Digital I/O.
External interrupt 2.
Digital I/O.
External interrupt 3.
Enhanced Capture 2 input/Compare 2 output/
PWM 2 output .
ECCP2 PWM output A.
Digital I/O.
Interrupt-on-change pin.
Digital I/O.
Interrupt-on-change pin.
Low-V o lt ag e ICSP™ Prog rammi ng ena ble pin.
Digital I/O.
Interrupt-on-change pin.
In-Circuit Debugger and ICSP™ programming clock pin.
Digital I/O.
Interrupt-on-change pin.
In-Circuit Debugger and ICSP programming data pin.
ST = Schmitt Trigger input with CMOS levels Analog= Analog input
I= Input O= Output
P= Power I
Note 1: Alternate assignment for ECCP2 when Configuration bit, CCP2MX, is cleared (all operating modes except
Microcontroller mode).
2: Default assignment fo r ECCP2 in all operating modes (CCP2MX is set).
3: Alternate assignment for ECCP2 when CCP2MX is cleared (Microcontroller mode only).
4: Default assignment for P1B/P1C/P3B/P3C (ECCPMX is set).
5: Alternate assignment for P1B/P1C/P3B/P3C (ECCPMX is clear).
Digital I/O.
EUSART1 asynchronous receive.
EUSART1 synchronous data (see related TX1/CK1).
PIC18F8722 FAMILY
T ABLE 1-4:PIC18F8527/8622/8627/8722 PINOUT I/O DESCRIPTIONS (CONTINUED)
Pin Name
Pin Number
TQFP
Pin
Type
Buffer
Type
Description
PORTD is a bidirectional I/O port.
RD0/AD0/PSP0
RD0
AD0
PSP0
RD1/AD1/PSP1
RD1
AD1
PSP1
RD2/AD2/PSP2
RD2
AD2
PSP2
RD3/AD3/PSP3
RD3
AD3
PSP3
RD4/AD4/PSP4/SDO2
RD4
AD4
PSP4
SDO2
RD5/AD5/PSP5/
SDI2/SDA2
RD5
AD5
PSP5
SDI2
SDA2
RD6/AD6/PSP6/
SCK2/SCL2
RD6
AD6
PSP6
SCK2
SCL2
72
69
68
67
66
65
64
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
ST
TTL
TTL
ST
TTL
TTL
ST
TTL
TTL
ST
TTL
TTL
ST
TTL
TTL
—
ST
TTL
TTL
I
ST
2
C/SMB
I
ST
TTL
TTL
ST
2
C/SMB
I
Digital I/O.
External memory address/data 0.
Parallel Slave Port data.
Digital I/O.
External memory address/data 1.
Parallel Slave Port data.
Digital I/O.
External memory address/data 2.
Parallel Slave Port data.
Digital I/O.
External memory address/data 3.
Parallel Slave Port data.
Digital I/O.
External memory address/data 4.
Parallel Slave Port data.
SPI data out.
Digital I/O.
External memory address/data 5.
Parallel Slave Port data.
SPI data in.
2
C™ data I/O.
I
Digital I/O.
External memory address/data 6.
Parallel Slave Port data.
Synchronous serial clock input/output for SPI mode.
Synchronous serial clock input/output for I2C mode.
ST = Schmitt Trigger input with CMOS levels Analog= Analog input
I= Input O= Output
P= Power I
Note 1: Alternate assignment for ECCP2 when Configuration bit, CCP2MX, is cleared (all operating modes except
Microcontroller mode).
2: Default assignment fo r ECCP2 in all operating modes (CCP2MX is set).
3: Alternate assignment for ECCP2 when CCP2MX is cleared (Microcontroller mode only).
4: Default assignment for P1B/P1C/P3B/P3C (ECCPMX is set).
5: Alternate assignment for P1B/P1C/P3B/P3C (ECCPMX is clear).
ST = Schmitt Trigger input with CMOS levels Analog= Analog input
I= Input O= Output
P= Power I
Note 1: Alternate assignment for ECCP2 when Configuration bit, CCP2MX, is cleared (all operating modes except
Microcontroller mode).
2: Default assignment fo r ECCP2 in all operating modes (CCP2MX is set).
3: Alternate assignment for ECCP2 when CCP2MX is cleared (Microcontroller mode only).
4: Default assignment for P1B/P1C/P3B/P3C (ECCPMX is set).
5: Alternate assignment for P1B/P1C/P3B/P3C (ECCPMX is clear).
ST = Schmitt Trigger input with CMOS levels Analog= Analog input
I= Input O= Output
P= Power I
Note 1: Alternate assignment for ECCP2 when Configuration bit, CCP2MX, is cleared (all operating modes except
Microcontroller mode).
2: Default assignment fo r ECCP2 in all operating modes (CCP2MX is set).
3: Alternate assignment for ECCP2 when CCP2MX is cleared (Microcontroller mode only).
4: Default assignment for P1B/P1C/P3B/P3C (ECCPMX is set).
5: Alternate assignment for P1B/P1C/P3B/P3C (ECCPMX is clear).
RG5See RG5/ MC LR
Legend: TTL = TTL compatible input CMOS= CMOS compatible input or output
ST = Schmitt Trigger input with CMOS levels Analog= Analog input
I= Input O= Output
P= Power I
Note 1: Alternate assignment for ECCP2 when Configuration bit, CCP2MX, is cleared (all operating modes except
Microcontroller mode).
2: Default assignment fo r ECCP2 in all operating modes (CCP2MX is set).
3: Alternate assignment for ECCP2 when CCP2MX is cleared (Microcontroller mode only).
4: Default assignment for P1B/P1C/P3B/P3C (ECCPMX is set).
5: Alternate assignment for P1B/P1C/P3B/P3C (ECCPMX is clear).
10
5
I/O
I/O
O
6
I/O
O
I/O
7
I/O
I
I/O
8
I/O
I/O
O
I/O
I/O
O
2
ST
ST
—
ST
—
ST
ST
ST
ST
ST
ST
—
ST
ST
—
C™/SMB= I2C/SMBus input buffer
Digital I/O.
Enhanced Capture 3 input/Compare 3 output/
PWM 3 output .
ECCP3 PWM output A.
Digital I/O.
EUSART2 asynchronous transmit.
EUSART2 synchronous clock (see related RX2/DT2).
Digital I/O.
EUSART2 asynchronous receive.
EUSART2 synchronous data (see related TX2/CK2).
Digital I/O.
Capture 4 input/Compare 4 output/PWM 4 output.
ECCP3 PWM output D.
Digital I/O.
Capture 5 input/Compare 5 output/PWM 5 output.
ECCP1 PWM output D.
ST = Schmitt Trigger input with CMOS levels Analog= Analog input
I= Input O= Output
P= Power I
Note 1: Alternate assignment for ECCP2 when Configuration bit, CCP2MX, is cleared (all operating modes except
Microcontroller mode).
2: Default assignment fo r ECCP2 in all operating modes (CCP2MX is set).
3: Alternate assignment for ECCP2 when CCP2MX is cleared (Microcontroller mode only).
4: Default assignment for P1B/P1C/P3B/P3C (ECCPMX is set).
5: Alternate assignment for P1B/P1C/P3B/P3C (ECCPMX is clear).
VSS11, 31, 51, 70P—Groun d reference for logic an d I/O pins.
DD12, 32, 48, 71P—Positive supply for logic and I/O pins.
V
AVSS26P—Ground reference for analog modules.
AVDD25P—Positive supply for analog modules.
Legend: TTL = TTL compatible input CMOS= CMOS compatible input or output
ST = Schmitt Trigger input with CMOS levels Analog= Analog input
I= Input O= Output
P= Power I
Note 1: Alternate assignment for ECCP2 when Configuration bit, CCP2MX, is cleared (all operating modes except
Microcontroller mode).
2: Default assignment fo r ECCP2 in all operating modes (CCP2MX is set).
3: Alternate assignment for ECCP2 when CCP2MX is cleared (Microcontroller mode only).
4: Default assignment for P1B/P1C/P3B/P3C (ECCPMX is set).
5: Alternate assignment for P1B/P1C/P3B/P3C (ECCPMX is clear).
62
61
60
59
39
40
41
42
I/O
O
I/O
O
I/O
O
I/O
O
I/O
O
I/O
O
I/O
O
I/O
O
2
ST
—
ST
—
ST
—
ST
—
ST
—
ST
—
ST
—
ST
—
C™/SMB= I2C/SMBus input buffer
Digital I/O.
External memory address latch enable.
Digital I/O.
External memory output enable.
Digital I/O.
External memory write low control.
Digital I/O.
External memory write high control.
Digital I/O.
External memory byte address 0 control.
Note 1: See Table 2-1 and Table2-2 for initial values of
C1 and C2.
2: A series resistor (R
S) may be required for AT
strip cut crystals.
3: R
F varies with the oscillator mode chosen.
C1
(1)
C2
(1)
XTAL
OSC2
OSC1
RF
(3)
Sleep
To
Logic
PIC18FXXXX
RS
(2)
Internal
2.0OSCILLATOR
CONFIGURATIONS
2.1Oscillator Types
The PIC18F8722 family of devices can be operated in
ten different oscillator modes. The user can program the
Configuration bits, FOSC<3:0>, in Configuration
Register 1H to select one of these ten modes:
1.LPLow-Power Crystal
2. XTCrystal/Resonator
3. HSHigh-Speed Crystal/Resonator
4.HSPLL High-Speed Crystal/Resonator
with PLL enabled
5.RCExternal Resistor/Capacitor with
F
OSC/4 output on RA6
6.RCIOExternal Resistor/Capacitor with I/O
on RA6
7. INTIO1 Internal Oscillator with F
on RA6 and I/O on RA7
8. INTIO2 Internal Oscillator with I/O on RA6
and RA7
9. ECExternal Clock with F
10. ECIOExternal Clock with I/O on RA6
OSC/4 output
OSC/4 output
FIGURE 2-1:CRYSTAL/CERAMIC
RESONATOR OPERATION
(XT, LP, HS OR HSPLL
CONFIGURATION)
T ABLE 2-1:CAPACITOR SELECTION FOR
CERAMIC RESONATORS
Typical Capacitor Values Used:
ModeFreqOSC1OSC2
2.2Crystal Oscilla tor/Ceramic
Resonators
In XT, LP, HS or HSPLL Oscillator modes, a crystal or
ceramic resonator is connected to the OSC1 and
OSC2 pins to establish oscillation. Figure 2-1 shows
the pin connections.
The oscillator design requires the use of a parallel cut
crystal.
Note:Use of a series cut crystal may give a
frequency out of the crystal ma nufacturer’s
specifications.
XT3.58 MHz22 pF22 pF
Capacitor values are for design guidance only.
Different cap acitor values may be required to prod uce
acceptable oscillator operation. The user should test
the performance of the oscillator over the expected
DD and temperature range for the application. Refer
V
to the following applicat ion notes for oscil lator specific
information:
®
• AN588 – PI C
Microcontroller Oscillator Design
Guide
• AN826 – Crystal Oscillator Basics and Crystal
Selection for rfPIC
• AN849 – Basic PIC
• AN943 – Practical PIC
®
and PIC® Devices
®
Oscillator Design
®
Oscillator Analysis and
Design
• AN949 – Making Your Oscillator Work
See the notes following Table 2-2 for additional
information.
Note:When using resonators with frequencies
above 3.5 MHz, the use of HS mode,
rather than XT mode, is recommended.
HS mode may be used at any V
which the controller is rated. If HS is
selected, it is possible that the gain of the
oscillator will overdrive the resonator.
Therefore, a series resistor may be placed
between the OSC2 pin and the resonator.
As a good starting point, the
recommended value of R
25 MHz
Capacitor values are for design guidance only.
Different capa citor values may be required to produc e
acceptable oscillator operation. The user should test
the performance of the oscillator over the expected
VDD and temperature range for the application. Refer
to the following a pplicati on not es for os cillator specifi c
information:
®
• AN588 – PIC
Microcontroller Oscillator Design
Guide
• AN826 – Crystal Oscillator Basics and Crystal
Selection for rfPIC
• AN849 – Basic P IC
• AN943 – Practical PIC
Design
• AN949 – Making Your Oscillator Work
See the notes following this table for additional
information.
T ypical Cap acitor V alues
C1C2
22 pF
22 pF
22 pF
22 pF
22 pF
22 pF
®
and PIC® Devices
®
Oscillator Design
®
Oscillator Analysis and
Tested:
22 pF
22 pF
22 pF
22 pF
22 pF
22 pF
An external clock source may also be connected to the
OSC1 pin in the HS mode, as shown in Figure 2-2.
When operated in this mode, parameters D033 and
D043 apply.
FIGURE 2-2:EXTERNAL CLOCK INPUT
OPERATION (HS OSC
CONFIGURATION)
2.3External Clock Input
The EC and ECIO Oscillator mode s require an externa l
clock source to be conn ected to the OSC1 pi n. There is
no oscillator start-up time required after a Power-on
Reset or after an exit from Sleep mode.
In the EC Oscillator mode, the oscillator frequency
divided by 4 is available on the OSC2 pin. This signal
may be used f or t est pu r pos es or t o sy nc hr o niz e o t he r
logic. Figure 2-3 shows the pin connections for the EC
Oscillator mode.
FIGURE 2-3:EXTERNAL CLOCK
INPUT OPERATION
(EC CONFIGURATION)
Note 1: Hi gher capac itance inc reases the st abilit y
of the oscillator but also increases the
start-up time.
2: When operating below 3V V
DD, or when
using certain ceramic resonators at any
voltage, it may be necessary to use the
HS mode or switch to a crystal oscillator.
3: Since each resonator/crystal has its own
characteristics, the user should consult
the resonator/crystal manufacturer for
appropriate values of external
components.
4: Rs may be required to avoid overd riving
crystals with low driv e lev e l spe ci fic ati on.
5: Alw ays verify os ci lla tor pe rform an ce ov er
DD and temperature range that is
the V
expected for the application.
The ECIO Oscillator mo de func tio ns lik e t he EC mod e,
except that the OSC2 pin becomes an additional
general purpose I/O pin. The I/O pin becomes bit 6 of
PORTA (RA6). Figure 2-4 shows the pin connections
for the ECIO Oscillator mode. When operated in this
mode, parameters D033A and D043A apply.
For timing insensitive applications, the RC and RCIO
Oscillator modes offer additional cost savings. The
actual oscillator frequency is a function of several
factors:
• supply voltage
• values of the external resistor (R
capacitor (C
EXT)
• operating temperature
Given the same device, operating voltage and temperature and component values, there will also be unit-to-unit
frequency variations. These are due to factors such as:
• normal manufacturing variation
• difference in lead frame capacitance between
package types (especially for low C
• variati ons within th e tolerance of limits of R
EXT
and C
In the RC Oscillator mode, the oscillator frequency
divided by 4 is available on the OSC2 pin. This signal
may be used f or t est pu r pos es or t o sy nc hr o niz e o t he r
logic. Figure 2-5 shows how the R/C combination is
connected.
FIGURE 2-5:RC OSCILLATOR MODE
EXT) and
EXT values)
EXT
2.5PLL Frequency Multiplier
A Phase Locked Loop (PLL) circuit is provided as an
option for users who wish to use a lower frequency
oscillator circuit or to clock the device up to its highest
rated frequency from a crystal oscillator. This may be
useful for customers who are concerned with EMI due
to high-frequency crystals or users who require higher
clock speeds from an internal oscillator.
2.5.1HSPLL OSCILLATOR MODE
The HSPLL mode make s use of the HS mode osc illator
for frequencies up t o 10 MHz. A PLL then multipl ies the
oscillator output frequency by 4 to produce an internal
clock frequency up to 40 MHz. The PLLEN bit is not
available when this mode is configured as the primary
clock source.
The PLL is only available to the crystal oscillator when
the FOSC<3:0> Configurati on bits are progra mmed for
HSPLL mode (= 0110).
FIGURE 2-7:HSPLL BLOCK DIAGRAM
The RCIO Oscillator mode (Figure 2-6) functions like
the RC mode, except that the OSC2 pin becomes an
additional general purpose I/O pin. The I/O pin
becomes bit 6 of PORTA (RA6).
The PLL is also ava ilabl e to th e inte rnal os cill ator bl ock
when the internal oscillator block is configured as the
primary clock source. In this configuration, the PLL is
enabled in sof tware and g enerate s a c lock output of u p
to 32 MHz. The operation of INTOSC with the PLL is
described in Section 2.6.4 “PLL in INTOSC Modes”.
PIC18F8722 FAMILY
PIC18FXXXX
OSC2
F
OSC/4
I/O (OSC1)
RA7
PIC18FXXXX
I/O (OSC2)
RA6
I/O (OSC1)
RA7
MUX
VCO
Loop
Filter
OSC2
PLLEN
F
IN
FOUT
SYSCLK
Phase
Comparator
8 or 4 MHz
÷4
(OSCTUNE<6>)
MUX
RA6
CLKO
INTOSC
2.6Internal Oscillator Block
The PIC18F8722 family of devices includes an int erna l
oscillator block which generates two different clock
signals; either can be used as the microcontroller’s
clock source. This may eliminate the need for external
oscillator circuits on the OSC1 and/or OSC 2 pins.
The main output (INTOSC) is an 8MHz clock source,
which can be used to directly drive the device clock. It
also drives a postscaler, which can provide a range of
clock frequencies from 31 kHz to 4 MHz. The INTOSC
output is enabled when a clock fre quency from 12 5 kHz
to 8 MHz is selected. The INTOSC output can also be
enabled when 31 kHz is selected, depending on the
INTSRC bit (OSCTUNE<7>).
The other clock source is the internal RC oscillator
(INTRC), which provides a nominal 31 kHz output.
INTRC is enabled if it is selected as the device clock
source; it is also ena bled autom atically when an y of the
following are enabled:
• Power-up Timer
• Fail-Safe Clock Monitor
• Watchdog Timer
• Two-Speed Start-up
These features are discussed in greater detail in
Section 25.0 “Special Features of the CPU”.
The clock source frequency (INTOSC direct, INTRC
direct or INTOSC postscaler) is selected by configuring
the IRCF bits of the OSCCON register (page 39).
2.6.1INTIO MODES
Using the internal oscillator as the clock source eliminates the need for up to two external oscillator pins,
which can then be used for digital I/O. Two distinct
configurations are available:
• In INTIO1 mode, the OSC2 pin outputs F
while OSC1 functions as RA7 (s ee Fig ure 2-8) for
digital input and output.
• In INTIO2 mode, OSC1 functions as RA7 and
OSC2 functions as RA6 (see Figure2-9), both for
digital input and output.
OSC/4,
2.6.2INTOSC OUTPUT FREQUENCY
The internal oscillator block is calibrated at the factory
to produce an INTOSC output frequency of 8 MHz.
The INTRC oscillator operates independently of the
INTOSC source. Any changes in INTOSC across
voltage and temperature are not necessarily reflected
by changes in INTRC or vice versa.
2.6.3OSCTUNE REGISTER
The INTOSC output has been calibrated at the
factory but can be adjusted in the user’s application.
This is done by writing to TUN<4:0>
(OSCTUNE<4:0>) in the OSCTUNE register
(Register ).
When the OSCTUNE regis ter is mo di fied , the IN T O SC
frequency will begin shifting to the new frequency. The
INTOSC clock will stabilize within 1 ms. Code execution continues during this shift. There is no indication
that the shift has occurred. The INTRC is not affected
by OSCTUNE.
The OSCTUNE register also implements the INTSRC
(OSCTUNE<7>) and PLLEN (OSCTUNE<6>) bits,
which control certain features of the internal oscillator
block. The INTSRC bit allows users to select which
internal oscillator provides the clock source when the
31 kHz frequenc y o ptio n is selected. This is co vered in
greater detail in Section 2.7.1 “Oscillator ControlRegister”.
The PLLEN bit controls the operation of the Phase
Locked Loop (PLL) in internal oscillator modes (see
Figure 2-10).
The 4x Phase Locked Loop (PLL) ca n be used with the
internal oscillator block to produce faster device clock
speeds than are normally possible with the internal
oscillator sources. When enabled, the PLL produces a
clock speed of 16 MHz or 32 MHz.
Unlike HSPLL mode, the PLL is controlled through
software. The control bit, PLLEN (OSCTUNE<6>), is
used to enable or disable its operation.
The PLL is available when the device is configured to
use the internal oscillator block as its primary clock
source (FOSC<3:0> = 1001 or 1000). Additionally, the
PLL will only function when the selected output frequency is either 4 MHz or 8 MHz (OSCCON<6:4> = 111
or 110). If both of these conditions are not met, the PLL
is disabled and the PLLEN bit remains clear (writes are
ignored).
2.6.5INTOSC FREQUENCY DRIFT
The factory calibrates the internal oscillator block
output (INTOSC) for 8 MHz. However, this frequency
may drift as V
affect the controller operation in a variety of ways. It is
possible to adjust the INTOSC frequency by modifying
the value in the OSCTUNE register. Depending on the
device, this may have no effect on the INTRC clock
source frequency.
Tuning the INTOSC source requires knowing when to
make the adjustment, in which direction it should be
made and in some cases, how large a change is
needed. Three compensation techniques are discus sed
in Section 2.6.5.1 “Compensating with the
EUSART”, Section 2.6.5.2 “Compensating with the
Timers” and Section 2.6.5.3 “Compe nsa tin g w it h th e
CCP Module in Capture Mode” but other techniques
may be used.
DD or temperature changes and can
REGISTER 2-1:OSCTUNE: OSCILLATOR TUNING REGISTER
R/W-0 R/W-0U-0R/W-0 R/W-0 R/W-0 R/W-0 R/W-0
INTSRCPLLEN
bit 7bit 0
(1)
—TUN4TUN3TUN2TUN1TUN0
Legend:
R = Readable bitW = Writable bitU = Unimplemented bit, read as ‘0’
-n = Value at POR‘1’ = Bit is set‘0’ = Bit is clearedx = Bit is unknown
bit 7INTSRC: Internal Oscillator Low-Frequency Source Select bit
An adjustment may be required when the EUSART
begins to generate frami ng errors or rec eive s dat a with
errors while in Asynchronous mode. Framing errors
indicate that the device clock frequency is too high. To
adjust for this, decrement the value in OSCTUNE to
reduce the clock frequency. On the other hand, errors
in data may sugge st that the clock speed is to o low. To
compensate, increment OSCTUNE to increase the
clock frequency.
2.6.5.2Compensating with the Timers
This technique compares device clock speed to some
reference clock. Two timers may be used; one timer is
clocked by the peripheral clock, while the other is
clocked by a fixed reference source, such as the
Timer1 oscillat or.
Both timers are cleared, but the timer clocked by the
reference generates interrupts. When an interrupt
occurs, the internally clocked timer is read and both
timers are cleared. If the internally clocked timer value
is much greater than expected, then the internal
oscillator block is running too fast. To adjust for this,
decrement the OSCTUNE register.
2.6.5.3Compensating with the CCP Module
in Capture Mode
A CCP module can use free running Timer1 (or
Timer3), cl oc ked by the internal oscillator block and an
external event with a known period (i.e., AC power
frequency). The ti me of the first ev ent is capt ured in the
CCPRxH:CCPRxL registers and is recorded for use
later. When the second event causes a capture, the
time of the first event is su btra cte d fro m the tim e of th e
second event. Since the period of the external event is
known, the time difference between events can be
calculated.
If the measured time is much greater than the
calculated time, the inte rnal oscillator block is running
too fast. To compensate, decrement the OSCTUNE
register. If the measured time is much less than the
calculated time, the inte rnal oscillator block is running
too slow. To compensate, increment the OSCTUNE
register.
The PIC18F8722 family of devices includes a feature
that allows the devic e clock so urce to be sw itched fro m
the main oscillator to an alternate clock source. These
devices also offer two alternate clock sources. When
an alternate clock source is enabled, the various
power-managed operating modes are available.
Essentially, there are three clock sources for these
devices:
• Primary oscillators
• Secondary oscillators
• Internal oscillator block
The primary oscillators include the Ex ternal Crystal
and Resonator modes, the External RC modes, the
External Clock modes and the internal oscillator block.
The particular mode is defined by the FOSC<3:0>
Configuration bits. The details of these modes are
covered earlier in this chapter.
The se condary oscillators are those external sources
not connected to the OSC1 or OSC2 pins. These
sources may continue to operate even after the
controller is placed in a power-managed mode.
The PIC18F8722 family of devices offers the Timer1
oscillator as a secon dary oscilla tor . This osc illator , in all
power-managed modes, is often the time base for
functions such as a real-time cloc k.
Most often, a 32.768 kHz watch crystal is connected
between the RC0/T1OSO/T13CKI and RC1/T1OSI
pins. Like the LP mode oscillator circuit, loading
capacitors are also connected from each pin to ground.
The Timer1 oscillator is discussed in greater detail in
Section 13.3 “Timer1 Oscillator”.
In addition to being a prim ary clock source, the internaloscillator block is available as a power-managed
mode clock source. T he IN TR C s ource is also used as
the clock source for several special features, such as
the WDT and Fail-Safe Clock Monitor.
The clock sources for the PIC18F8722 famil y of devic es
are shown in Figure 2-11. See Section 25.0 “Special
Features of the CPU” for Configuration register details.
The OSCCON register (Register 2-2) controls several
aspects of the device clock’s operation, both in full
power operation and in power-managed modes.
The System Clock Select bits, SCS<1:0>, select the
clock source. The available clock sources are the
primary clock (defined by the FOSC<3:0> Configuration bits), the secondary clock (Timer1 oscillator) and
the internal oscillator block. The clock source changes
immediately after either of the SCS<1:0> bits are
changed, following a brief clock transition interval. The
SCS bits are reset on all forms of Reset.
The Internal Oscillator Frequency Select bits
(IRCF<2:0>) select the fr equenc y output of th e interna l
oscillator block to drive the device clock. The choices
are the INTRC source (31 kHz), the INTOSC source
(8 MHz) or one of the frequencies derived from the
INTOSC postscaler (31.25 kHz to 4 MHz). If the
internal oscillator block is supplying the device clock,
changing the states of these bits will have an immediate change on the internal oscillator’s output. On
device Resets, the default output frequency of the
internal oscillator block is set at 1 MHz.
When a nominal ou tput frequenc y of 31 kHz is selected
(IRCF<2: 0> = 000), users may choose which internal
oscillator acts as the source. This is done with the
INTSRC bit in the OSCTUNE register (OSCTUNE<7>).
Setting this bit selects INTOSC as a 31.25 kHz clock
source derived from the INTOSC postscaler. Clearing
INTSRC selects INTRC (nominally 31 kHz) as the
clock source and disables the INTOSC to reduce
current consumption.
This option allows users to select the tunable and more
precise INTOSC as a clock source, while maintaining
power savings wit h a very low clock speed . Additionally , the IN T OSC so urce w ill alread y be sta ble s hould a
switch to a higher frequency be needed quickly.
Regardless of the setting of INTSRC, INTRC always
remains the clock source for features such as the
Watchdog Timer and the Fail-Safe Clock Monitor.
The OSTS, IOFS and T1RUN bits indicate which cl ock
source is currently providing the device clock. The
OSTS bit indicates that the Oscillator Start-up Timer
and PLL St art-up T im er (if enable d) have timed o ut and
the primary clock is providing the device clock in
primary clock modes. The IOFS bit indicates when the
internal oscillator block has stabilized and is providing
the device clock in RC Clock modes. The T1RUN bit
(T1CON<6>) indicates when the Timer1 oscillator is
providing the device clock in secondary clock modes.
In power-managed modes, only one of the se thre e bits
will be set at any time. If none of these bits are set, the
INTRC is providing the clock or the internal oscillator
block has just started and is not yet stable.
The IDLEN bit controls whether the device goes into
Sleep mode or one of the Idle modes when the SLEEP
instruction is executed.
The use of the flag and control bits in the OSCCON
register is discussed in more detail in Section 3.0
“Power-Managed Modes”.
Note 1: The Timer1 oscillator must be enabled to
select the secondary clock source. The
Timer1 osc illator is enabled by s etting the
T1OSCEN bit in the Timer1 Control re gister (T1CON<3>). If the Timer1 oscillator
is not enabled, then any at tem pt to se lec t
a secondary clock source will be ignore d.
2: It is recommended that the Timer1
oscillator be operating and stable before
selecting the secondary clock source or a
very long delay may occur while the
Timer1 oscillator starts.
2.7.2OSCILLATOR TRANSITIONS
The PIC18F8722 family of d ev ic es c on t ai ns circuitry to
prevent clock “glitches” when switching between clock
sources. A short pause in the device clock occurs during the clock switch. The length o f this p ause is th e sum
of two cycles of the old clock source and three to four
cycles of the new clock source. This formula assumes
that the new clock source is stable.
Clock transitions are discussed in greater detail in
Section 3.1.2 “Entering Power-Managed Modes”.
Note 1: Reset state depends on state of the IESO Configuration bit.
2: Source selected by the INTSRC bit (OSCTUNE<7>), see text.
3: Default output frequency of INTOSC on Reset.
4: Modifying the SCS<1:0> bits will cause an immediate clock source switch.
5: Modifying the IRCF<3:0> bits will cause an immediate clock frequency switch if the internal oscillator is
2.8Effects of Power-Managed Modes
on the Various Clock Sources
When PRI_IDLE mode is selected, the configured
oscillator continues to run without interruption. For all
other power-managed modes, the oscillator using the
OSC1 pin is disa bled. The OSC1 pin (a nd OSC2 pin in
crystal oscillator modes) will stop oscillating.
In secondary clock modes (SEC_RUN and
SEC_IDLE), the Timer1 oscillator is operating and
providing the device clock. The Timer1 oscillator may
also run in all power-managed modes if required to
clock Timer1 or Timer3.
In internal oscillator modes (RC_RUN and RC_IDLE),
the internal oscillator block provides the device clock
source. The 31kHz INTRC output can be used dire ctly
to provide the clock and may be enabled to support
various special features, regardless of the powermanaged mode (see Section 25.2 “Watchdog Timer(WDT)” and Section 25.4 “Fail-Safe Clock Monitor”
for more information). The INTOSC output at 8 MHz
may be used directly to clock the device or may be
divided down by the postscaler. The INTOSC output is
disabled if the clock is provi ded directly from the INTRC
output. The I NTOSC output is also enab led for TwoSpeed Start-up at 1 MHz after Resets and when
configured for wake from Sleep mode.
If the Sleep mode is selected, all clock sources are
stopped. Since all the transistor switching currents
have been stopped, Sleep mode achieves the lowest
current consumption of the device (only leakage
currents).
Enabling any on-chip feature that will operate during
Sleep will increas e the current cons umed during S leep.
The INTRC is required to support WDT operation. The
Timer1 oscillator may be operating to support a realtime clock. Other features m ay be op erating th at do not
require a device clock source (i.e., SSP slave, PSP,
INTx pins and others). Peripherals that may add
significant current consumption are listed in
Section 28.2 “DC Charac teristics”.
2.9Power-up Delays
Power-up delays are controlled by two or three timers,
so that no external Reset circuitry is required for most
applications. The delays ensure that the device is kept
in Reset until the device power supply is stable under
normal circumstances and the primary clock is operating and stable. For additional information on power-up
delays, see Section 4.5 “Device Reset Timers”.
The first timer is the Power-up Timer (PWRT) which
provides a fixed delay on power-up (parameter 33,
Table 28-12). It is enabled by clearing (= 0) the
PWRTEN
2.9.1DELAYS FOR POWER-UP AND
The second timer is the Oscillator Start-up Timer
(OST), intended to delay execution until the crystal
oscillator is stable (LP, XT and HS modes). The OST
does this by counting 1024 oscillator cycles before
allowing the oscillator to clock the device.
When the HSPL L Oscillator m ode is selected, a third
timer delays execution for an additional 2 ms following
the HS mode OST delay, so the PLL can lock to the
incoming clock frequency. At the end of these delays,
the OSTS bit (OSCCON<3>) is set.
There is a delay of interval T
Table 28-12), once execution is allowed to start, when
the controller becomes ready to execute instructions.
This delay runs concurrently with any other delays.
This may be the only delay that occurs when any of the
EC, RC or INTIO modes are us ed as the primary clock
source.
Configuration bit (CONFIG2L<0>).
RETURN TO PRIMARY CLOCK
CSD (parameter 38,
TABLE 2-3:OSC1 AND OSC2 PIN STATES IN SLEEP MODE
OSC ModeOSC1 PinOSC2 Pin
RC, INTIO1Floating, external resistor pulls highAt logic low (clock/4 output)
RCIOFloating, external resistor pulls highConfigured as PORTA, bit 6
INTIO2Configured as PORTA, bit 7Configured as PORTA, bit 6
ECIOFloating, driven by external clockConfigured as PORTA, bit 6
ECFloating, driven by external clockAt logic low (clock/4 output)
LP, XT and HSFeedback inverter disabled at quiescent
voltage level
Note:See Table 4-2 in Section 4.0 “Reset” for time-outs due to Sleep and MCLR
Feedback inverter disabled at quiescent
voltage level
Reset.
PIC18F8722 FAMILY
3.0POWER-MANAGED MODE S
The PIC18F8722 family of devices offers a total of
seven operating modes for more efficient power management. These modes prov ide a vari ety of options for
selective power conservation in applications where
resources may be limited (i.e., battery-powered
devices).
There are three categories of power-managed modes:
• Run modes
• Idle modes
• Sleep mode
These categories define which portions of the device
are clocked and some times , what sp eed. The R un and
Idle modes may use any of the three available clock
sources (primary, secondary or internal oscillator
block); the Sleep mode does not use a clock source.
The power-managed modes include several powersaving features of fe red on previ ous P IC
is the clock switching feature, offered in other PIC18
devices, allowing the controller to use the Timer1 oscillator in place of the primary oscillator. Also included is
the Sleep mode, offered by all PIC devices, where all
device clocks are stopped.
3.1Selecting Power-Managed Modes
Selecting a power-managed mode requires two
decisions: if the CPU is to be clocked or not and the
selection of a clock source. The IDLEN bit
(OSCCON<7>) controls CPU clocking, while the
SCS<1:0> bits (OSCCON<1:0>) select the clock
source. The individual modes, bit settings, clock sources
and affected modules are summarized in Table 3-1.
®
devices. One
3.1.1CLOCK SOURCES
The SCS1:SCS0 bits allow the sele ction of one o f three
clock sources for power-managed modes. They are:
• the primary clock, as defined by the FOSC<3:0>
Configuration bits
• the secondary clock (the Timer1 oscillator)
• the internal oscillator block (for INTOSC modes)
3.1.2ENTERING POWER-MANAGED
MODES
Switching from one power-managed mode to another
begins by loading the OSCCON register. The
SCS<1:0> bits select the clock source and determine
which Run or Idle mode is to be used. Changing these
bits causes an immediate switch to the new clock
source, assuming that it is running. The switch may
also be sub ject to clock tr ansition delays. T hese are
discussed in Section 3.1.3 “Clock Transitions andStatus Indicators” and subsequent sections.
Entry to the power-managed Idle or Sleep modes is
triggered by the execution of a SLEE P instruction. The
actual mode that results depends on the status of the
IDLEN bit.
Depending on the current mode and the mode being
switched to, a change to a power-managed mode does
not always require setting all of these bits. Many
transitions may be done by changing the oscillator s elect
bits, or changing the IDLEN bit, prior to issuing a SLEEP
instruction. If the IDLEN bit is already configured
correctly, it may only be necessary to perform a SLEEP
instruction to switch to the desired mode.
TABLE 3-1:POWER-MANAGED MODES
Mode
Sleep0N/AOffOffNone – All clocks are disabled
PRI_RUNN/A00ClockedClockedPrimary – LP, XT, HS, HSPLL, RC, EC and
Internal Oscillator Block
This is the normal full power execution mode.
.
(2)
(2)
PIC18F8722 FAMILY
3.1.3CLOCK TRANSITI ONS AND S TATUS
INDICATORS
The length of the transition between clock sources is
the sum of two cycles o f the old clo ck so urce an d three
to four cycles of the ne w clock source. Thi s formula
assumes that the new clock source is stable.
Three bits indicate the current clock source and its
status. They are:
• OSTS (OSCCON<3>)
• IOFS (OSCCON<2>)
• T1RUN (T1CON<6>)
In general, only one of these bits will be set while in a
given power-managed mode. When the OSTS bit is
set, the primary clock is providing the device clock.
When the IOFS bit is set, the INTOSC output is
providing a stable 8 MHz clock source to a divider that
actually drives the device clock. When the T1RUN bit is
set, the Timer1 oscillator is providing the clock. If none
of these bits are set, then either the INTRC clock
source is cloc ki ng t he dev ic e, o r th e INTOSC source is
not yet stable.
If the internal oscillator block is configured as the primary clock source by the FOSC<3:0> Configuration
bits, then both the OSTS and IOFS bits may be set
when in PRI_RUN or PRI_IDLE modes. This indicates
that the primary clock (INTOSC output) is genera tin g a
stable 8 MHz output. Entering another INTOSC po wermanaged mode at the sam e fre quency would clear the
OSTS bit.
Note 1: Caution should be us ed when modifyi ng a
single IRCF bit. I f V
possible to select a higher clock speed
than is supported by the low VDD.
Improper device operation may result if
DD/FOSC specifications are violated.
the V
2: Executing a SLEEP instruction does not
necessarily place the device into Sleep
mode. It acts as the trigger to place the
controller into either the Sleep mode or
one of the Idle modes, depending on the
setting of the IDLEN bit.
DD is less than 3V, it is
3.1.4MULTIPLE SLEEP COMMANDS
The power-managed mode that is invoked with the
SLEEP instruction is determined by the setting of the
IDLEN bit at the time the instruction is executed. If
another SLEEP instruction is executed, the device will
enter the power-ma nag ed mo de s pe ci fie d by ID L EN at
that time. If IDLEN has changed, the device will enter
the new power-managed mode specified by the new
setting.
3.2Run Modes
In the Run modes, clocks to both the core and
peripherals are active. The difference between these
modes is the clock source.
3.2.1PRI_RUN MODE
The PRI_RUN mode is the normal, full power execution
mode of the microcontroller. This is also the default
mode upon a devi ce Reset, u nless T wo- Sp eed S tart-u p
is enabled (see Section 25.3 “Two-Speed Start-up”
for details). In this m ode, the OSTS bi t is set. Th e IOFS
bit may be set if the internal oscillator block is the
primary clock source (see Section 2.7.1 “OscillatorControl Register”).
3.2.2SEC_RUN MODE
The SEC_RUN mode is the compatible mode to the
“clock switching” feature offered in other PIC18
devices. In this mode, the CPU and peripherals are
clocked from the T imer1 os cillator. This gives users the
option of lower power consumption w hile still u sing a
high accuracy clock source.
SEC_RUN mode is entered by setting the SCS<1:0>
bits to ‘01’. The device clock source is switched to the
Timer1 oscillator (see Figure 3-1), the primary oscillator is shut down, the T1RUN bit (T1CON<6>) is set and
the OSTS bit is cleared.
Note:The Timer1 oscillator should already be
running prior to entering SEC_RU N mode.
If the T1OSCEN bit is not set when the
SCS<1:0> bits are set to ‘01’, entry to
SEC_RUN mode will not occur. If the
Timer1 oscillator is enabled, but not yet
running, devic e cloc ks will be de layed u ntil
the oscillator has started; in such situations, initial oscillator operation is far from
stable and unpredictable operation may
result.
On transitions from SEC_RUN mode to PRI_RUN, the
peripherals and CPU continue to be clocked from the
Timer1 oscillator while the primary clock is started.
When the primary clo ck bec omes r eady, a clock switch
back to the primary clock occurs (see Figure 3-2).
When the clock switch is complete, the T1RUN bit is
cleared, the OSTS bit is set and the primary clock is
providing the clock. The IDLEN and SCS bits are not
affected by the wake-up; the Timer1 oscillator
continues to run.
Note 1: Clock transition typically occurs within 2-4 T
OSC.
Q1Q3 Q4
OSC1
Peripheral
Program
PC
T1OSI
PLL Clock
Q1
PC + 4
Q2
Output
Q3Q4Q1
CPU Clock
PC + 2
Clock
Counter
Q2Q2Q3
Note 1:TOST = 1024 TOSC; TPLL = 2 ms (approx). These intervals are not shown to scale.
2: Clock transition typically occurs within 2-4 T
OSC.
SCS1:SCS0 bits Changed
TPLL
(1)
12 n-1n
Clock
OSTS bit Set
Transition
(2)
TOST
(1)
FIGURE 3-1:TRANSITION TIMING FOR ENTRY TO SEC_RUN MODE
FIGURE 3-2:TRANSITION TIMING FROM SEC_RUN MODE TO PRI_RUN MODE (HSPLL)
3.2.3RC_RUN MODE
In RC_RUN mode, the CPU and peripherals are
clocked from the internal oscillator block using the
INTOSC multiplexer. In this mode, the primary clock is
shut down. When using the INTRC source, this mode
provides the best power conservation of all the Run
modes, while still executing code. It works well for user
applications whi ch are n ot h igh ly tim in g-s ens it ive or d o
not require high-speed clocks at all times.
If the primary clock source is the internal oscillator
block (either INTRC or INTOSC), there are no distinguishable differences between PRI_RUN and
RC_RUN modes during execution. Howe ver, a clock
switch delay will occur during entry to and exit from
RC_RUN mode. Therefore, if the primary clock source
is the internal oscillator block, the use of RC_RUN
mode is not recommended.
This mode is entered by setting the SCS1 bit to ‘1’.
Although it is ignored, it is rec ommended that the SCS0
bit also be cleared; this is to maintain software compatibility with future devices. When the clock source is
switched to the INTOSC multiplexer (see Figure 3-3),
the primary oscillator is shut down and the OSTS bit is
cleared. The IRCF bits may be modified at any time to
immediately change the clock speed.
Note:Caution should be used when modifying a
single IRCF bit. If V
DD is less than 3V, it is
possible to select a higher clock speed
than is supported by the low V
Improper device operation may result if
DD/FOSC specifications are violated.
the V
DD.
PIC18F8722 FAMILY
Q4Q3Q2
OSC1
Peripheral
Program
Q1
INTRC
Q1
Counter
Clock
CPU
Clock
PC + 2PC
123n-1n
Clock Transition
(1)
Q4Q3Q2Q1Q3Q2
PC + 4
Note 1: Clock transition typically occurs within 2-4 T
OSC.
Q1
Q3 Q4
OSC1
Peripheral
Program
PC
INTOSC
PLL Clock
Q1
PC + 4
Q2
Output
Q3
Q4
Q1
CPU Clock
PC + 2
Clock
Counter
Q2
Q2
Q3
Note 1: TOST = 1024 TOSC; TPLL = 2 ms (approx). These intervals are not shown to scal e.
2: Clock transition typically occurs within 2-4 T
OSC.
SCS1:SCS0 bits Changed
TPLL
(1)
12 n-1n
Clock
OSTS bit Set
Transition
(2)
Multiplexer
TOST
(1)
If the IRCF bits and the INTSRC bit are all clear, the
INTOSC output is not enabled and the IOFS bit will
remain clear; there will be no indication of the current
clock source. The INTRC source is providing the
device clocks.
If the IRCF bits are changed from all clear (thus,
enabling the INTOSC output) or if INTSRC is set, the
IOFS bit becomes set after the INTOSC output
becomes stable. Clocks to the device continue while
the INTOSC source stabilizes after an interval of
IOBST (parameter 39, Table 28-12).
T
On transitions from RC_RUN mode to PRI_RUN mode,
the device continues to be clocked from the INTOSC
multiplexer whil e the prim ary clock is st arted. W hen the
primary clock becomes ready, a clock switch to the
primary clock occurs (see Figure 3-4). When the clock
switch is complete, the IOFS bit is cleared, the OSTS
bit is set and the primary clock is providing the device
clock. The IDLEN and SCS bits are not af fe cte d by the
switch. The INTRC source will continue to run if either
the WDT or the Fail-Safe Clock Monitor is enabled.
If the IRCF bits w ere prev io us ly at a no n-z ero val ue, or
if INTSRC was set before setting SCS1 and the
INTOSC source was already stable, the IOFS bi t will
remain set.
FIGURE 3-3:TRANSITION TIMING TO RC_RUN MODE
FIGURE 3-4:TRANSITION TIMING FROM RC_RUN MODE TO PRI_RUN MODE
OST = 1024 TOSC; TPLL = 2 ms (approx). These intervals are not shown to scale.
TOST
(1)
TPLL
(1)
OSTS bit Set
PC + 2
3.3Sleep Mode
The power-managed Sleep mode in the PIC18F8722
family of devices is identical to the legacy Sleep mode
offered in all other PIC de vices. It is enter ed by clearing
the IDLEN bit (the default state on device Reset) and
executing the SLEEP instruction. This shuts down the
selected oscillator (Figure 3-5). All clock source status
bits are cleared.
Entering the Sleep m ode from any other mo de does not
require a clock switch. This is because no clocks are
needed once the controller has entered Sleep. If the
WDT is selected, the INTRC source will continue to
operate. If the Timer1 oscillator is enabled, it will also
continue to run.
When a wake ev ent occurs i n Sleep mo de (by int errupt,
Reset or WDT time-out), the device will not be clocked
until the clock source selected by the SCS<1:0> bits
becomes ready (see Figure 3-6), or it will be clocked
from the internal osc illator block if e ither the T wo-S peed
Start-up or the Fail-Safe Clock Monitor are enabled
(see Sectio n 25.0 “Spe cial Features o f the CPU”). In
either case, the OS TS bit i s set wh en the p rimary cloc k
is providing the device cl ocks. The IDLEN and SCS bit s
are not affected by the w ake-up.
3.4Idle Modes
The Idle modes allow the controller’s CPU to be
selectively shut down while the peripherals continue to
operate. Selecting a particular Idle mode allows users
to further manage power consumption.
If the IDLEN bit i s set to a ‘1’ when a SLEEP inst ruction is
executed, the periph erals will be cloc ked fro m the cloc k
source selecte d using the SCS< 1:0> bits; howev er, the
CPU will not be clocked. The clock source status bits are
not affected. Setting IDLEN and executing a SLEEP
instruction pr ovides a quick method of switchi ng from a
given Run mo de to its correspon ding Idle mode.
If the WDT is selected, the INTRC source will continue
to operate. If the T imer1 oscill ator is enable d, it will also
continue to run.
Since the CPU is not executing instructions, the only
exits from any of the Idle modes are by interrupt, WDT
time-out or a Reset. When a wa ke even t occur s, CPU
execution is delayed by an interval of T
(parameter 38, Table 28-12) while it becomes ready to
execute code. When the CPU begins executing code,
it resumes with the same clock source for the current
Idle mode. For example, when waking from RC_IDLE
mode, the internal oscillator block will clock the CPU
and peripherals (in other words, RC_RUN mode). The
IDLEN and SCS bits are not affected by the wake-up.
While in any Idle mode or the S leep mode, a WDT
time-out will result in a WDT wake-up to the Run mode
currently specified by the SCS<1:0> bits.
CSD
FIGURE 3-5:TRANSITION TIMING FOR ENTRY TO SLEEP MODE
FIGURE 3-6:TRANSITION TIMING FOR WAKE FROM SLEEP (HSPLL)
This mode is uni que among the thre e low-power Idle
modes, in that it does not disable the primary device
clock. For timing sensitive applications, this allows for
the fastest resump tion of devic e operation w ith its mo re
accurate pri mary clock source, si nce the cl ock source
does not have to “warm-up” or transition from another
oscillator.
PRI_IDLE mode is entered from PRI_RUN mode by
setting the IDLEN bit and executing a SLEEP instruction. If the device is in another Run mode, set IDLEN
first, then clear the SCS bits and execute SLEEP.
Although the CPU i s disab led, th e peri pherals cont inue
to be clocked from the primary clock source specified
by the FOSC< 3:0> Configuration bi ts. The OSTS bit
remains set (see Figure3-7).
When a wake event occurs, the CPU is clocked from the
primary clock source. A delay of interval T
(parameter 39, Table 28-12) is required between the
wake event and when code execution starts. This is
required to allow the CPU to become ready to ex ecute
instructions. After the wake-up, the OSTS bit remains
set. The IDLEN and SCS b its are not affected by the
wake-up (see Figure 3-8).
CSD
3.4.2SEC_IDLE MODE
In SEC_IDLE mode, the CPU is disabled but the
peripherals continue to be clocked from the Timer1
oscillator. This mode is entered from SEC_RUN by setting the IDLEN bit and executi ng a SLEEP instruction. If
the device is in another Run mode, set the IDLEN bit
first, then set the SCS<1:0> bits to ‘01’ and execute
SLEEP . When the clock source is switched to the
Timer1 oscillato r, the primary osci llator is shut down,
the OSTS bit is cleared and the T1RUN bit is set.
When a wake event occurs, the peripherals continue to
be clocked from the Timer1 oscillator. After an interval
CSD following the wake event, the CPU b egins exe-
of T
cuting code being cloc ked by the T im er1 oscil lator . Th e
IDLEN and SCS bits are not affected by the wake-up;
the Timer1 oscillator continues to run (see Figure3-8).
Note:The Timer1 oscillator should already be
running prior to entering SEC_IDLE mod e.
If the T1OSCEN bit is not set when the
SLEEP instruction is executed, the SLEEP
instruction will be ignored and entry to
SEC_IDLE mode will not occur. If the
Timer1 oscillator is enabled but not yet
running, peripheral clocks will be delayed
until the oscillator has started. In such
situations, initial oscillator operation is far
from stable and unpredictable operation
may result.
FIGURE 3-7:TRANSITION TIMING FOR ENTRY TO IDLE MODE
FIGURE 3-8:TRANSITION TIMING FOR WAKE FROM IDLE TO RUN MODE
In RC_IDLE mode, t he C PU is d is abl ed but th e p erip herals continue to b e c loc ke d fro m the internal oscilla t or
block using the INTOSC multiplexer. This mode allows
for controllable power cons ervation during Idl e periods .
From RC_RUN, this mode is entered by setting the
IDLEN bit and executing a SLEEP instruction. If the
device is in a nother Run mode, first s et IDLEN, th en set
the SCS1 bit and execute SLEEP. Although its value is
ignored, it is reco mmended that SCS0 also be cle ared;
this is to maintain software compatibility with future
devices. The INTOSC multiplexer may be used to
select a higher clock frequency by modifying the IRCF
bits before exec uti ng th e SLEEP instruction. When the
clock source is switched to the INTOSC mult iplexer , the
primary oscillator is shut down and the OSTS bit is
cleared.
If the IRCF bits are set to any non-zero value, or the
INTSRC bit is set, the INTOSC output is enabled. The
IOFS bit becomes set, after the INTOSC output
becomes stable, after an interval of T
(parameter 39, Table 28-12). Clocks to the peripherals
continue while the INTOSC source stabilizes. If the
IRCF bits were previously at a non-zero value, or
INTSRC was set before the SLEEP instruction was ex ecuted and the INTOSC source was already stable, the
IOFS bit will remain set. If the IRCF bits and INTSRC
are all clear , the INT OSC output will n ot be enabled, the
IOFS bit will remain c lear and there will be no ind ication
of the current clock source .
When a wake event o ccurs, the pe ripherals co ntinue to
be clocked from the INTOSC multiplexer. After a delay
CSD (parameter 38, Table 28-12) following the wake
of T
event, the CPU begins executing code being clocked
by the INTOSC multiplexer. The IDLEN and SCS bits
are not affec ted by the wake-up. T he INTRC sou rce will
continue to run if eith er the WDT or th e Fail-Sa fe Cloc k
Monitor is enabled.
IOBST
3.5Exiting Idle and Sleep Modes
An exit from Sleep mode or any of the Idle modes is
triggered b y an interrupt , a Reset or a WDT time-out.
This section discusses the triggers that cause exits
from power-managed modes. The clocking subsystem
actions are discussed in each of the power-managed
modes (see Section 3.2 “Run Modes”, Section 3.3“Sleep Mode” and Section 3.4 “Idle Modes”).
3.5.1EXIT BY INTERRUPT
Any of the available interrupt sources can cause the
device to exit from an Idle mode or the Sleep mode to
a Run mode. To enable this functionality, an interrupt
source must be enab led by s etti ng i t s en able bit in one
of the INTCON or PIE registers. The exit sequence is
initiated when the c orresponding interrupt flag bit is set.
On all exits from Idle or Sl eep modes by interrupt, code
execution branches to the interrupt vector if the GIE/
GIEH bit (INTCON<7>) is set. Otherwise, code execution continues or resumes without branching (see
Section 10.0 “Interrupts”).
A fixed delay of inter val T
is required when leaving Sleep and Idle modes. This
delay is required for the CPU to prepare for execution.
Instructio n execution r esumes on th e first clock c ycle
following this delay.
CSD following th e wake event
3.5.2EXIT BY WDT TIME-OUT
A WDT time-out will cause different actions depending
on which power-managed mode the device is in when
the time-out occurs.
If the device i s not exec uti ng code (al l Idle mode s and
Sleep mode), the time-out will res ul t in a n ex it fro m th e
power-managed mode (see Section 3.2 “RunModes” and Section 3.3 “Sleep Mode”). If the device
is executing code (all Run modes), the time-out will
result in a WDT Reset (see Section 25.2 “WatchdogTimer (WDT)”).
The WDT timer and postscaler are cleared by
executing a SL EE P or CLRWDT instruction, the loss of a
currently selected clock source (if the Fail-Safe Clock
Monitor is enabled) and modifying the IRCF bits in the
OSCCON register if the internal oscillator block is the
device clock source.
3.5.3EXIT BY RESET
Normally, the device is held in Reset by the Oscillator
Start-up Timer (OST) until the primary clock becomes
ready. At that time, the OSTS bit is set and the device
begins executing code. If the internal osc il lat or bl oc k i s
the new clock source, the IOFS bit is set instead.
The exit delay time from Reset to the start of code
execution depends on both the clock sources before
and after the wake-up and the type of oscillator if the
new clock source is the primary clock. Exit delays are
summarized in Table 3-2.
Code execution can begin before the primary clock
becomes ready. If either the Two-Speed Start-up (see
Section 25.3 “Two-Speed Start-up”) or Fail-Safe
Clock Monitor (see Section 25.4 “Fail-Safe ClockMonitor”) is enabled, the device may begin execution
as soon as the Reset source ha s cle are d. Execution is
clocked by the INTO SC mu lti ple xe r driv en b y th e internal oscillator bloc k. Executi on is clo cked by the interna l
oscillator block until either the primary clock becomes
ready or a power-mana ged mo de is e ntered b efore th e
primary clock beco mes re ady; the pri mary clo ck is then
shut down.
Certain exits from power-managed modes do not
invoke the OST at all. There are two cases:
• PRI_IDLE mode, where the primary clock source
is not stopped and
• the primary clock source is not any of the LP, XT,
HS or HSPLL modes.
In these instances, the primary clock source either
does not require an oscillator start-up delay since it is
already running (PRI_IDLE), or normally does not
require an oscillator start-up delay (RC, EC and INTIO
Oscillator modes). However, a fixed delay of interval
CSD following the wake event is still required when
T
leaving Sleep and Idle modes to allow the CPU to
prepare for execution. Instruction execution resumes
on the first clock cycle following this delay.
TABLE 3-2:EXIT DELAY ON WAKE-UP BY RESET FROM SLEEP MODE OR ANY IDLE MODE
(BY CLOCK SOURCES)
Clock Source
before Wake-up
Primary Device Clo ck
(PRI_IDLE mode)
T1OSC or IN TRC
INTOSC
(Sleep mode)
Note 1: TCSD (parameter 38, Table 28-12) is a required delay when w aking from Sle ep and all Idle modes and run s
concurrently with any other required delays (see Section 3.4 “Idle Modes”).
2: Includes both the INTOSC 8MHz source and postscaler deriv ed frequ encie s. On Res et, INT OSC defau lt s
to 1 MHz.
3: T
(parameter F12, Table 28-7); it is also designated as T
4: Execution continues during T
(2)
None
OST is the Oscillator Start-up Timer (parameter 32, Table 28-12). t
Clock Source
after Wake-up
Exit Delay
Clock Ready Status
Bit (OSCCON)
LP, XT, HS
HSPLL
EC, RC
INTOSC
(2)
LP, XT, HSTOST
EC, RCTCSD
INTOSC
(2)
LP, XT, HSTOST
EC, RCTCSD
INTOSC
(2)
LP, XT, HSTOST
EC, RCTCSD
INTOSC
IOBST (parameter 39, Table 28-12), the INTOSC stabilization period.
This section discusses Resets generated by MCLR
POR and BOR and covers the ope rati on o f the various
start-up timers. Stack Reset events are covered in
Section 5.1.3.4 “Stack Full and Underflow Resets”.
WDT Resets are co v ere d i n Section 25.2 “Watchdog
,
4.1RCON Register
Device Reset events are tracked through the RCON
register (Register 4-1). The lower five bits of the register indicate that a specif ic Reset eve nt has occu rred. In
most cases, thes e bits c an only be cl eared by the e vent
and must be set by the ap pli ca tio n af ter the event. The
state of these flag bits, taken together, can be read to
indicate the type of Reset that just occurred. This is
described in more detail in Section 4. 6 “Reset Stateof Registers”.
The RCON register also has control bits for setting
interrupt priority (IPEN) and software control of the
BOR (SBOREN). Interrupt priority is discussed in
Section 10.0 “Interrupts”. BOR is covered in
Section 4.4 “Brown-out Reset (BOR)”.
Timer (WDT)”.
FIGURE 4-1:SIMPLIFIED BLOCK DIAGRAM OF ON-CHIP RESET CIRCUIT
is determined by the type of device Reset. See the notes following this
is ‘0’ and POR is ‘1’ (assuming that POR was set to
PIC18F8722 FAMILY
Note 1: External Power- on Reset circuit is required
only if the V
DD power-up slope is too slow.
The diode D helps discharge the capacitor
quickly when V
DD powers down.
2: R < 40 kΩ is recommended to make sure that
the voltage drop across R does not violate
the device’s electrical specification.
3: R1 ≥ 1 kΩ will limit any current flowing into
MCLR
from external capacitor C, in the event
of MCLR
/VPP pin breakdown, due to
Electrostatic Discharge (ESD) or Electrical
Overstress (EOS).
C
R1
(3)
R
(2)
D
V
DD
MCLR
PIC18FXXXX
VDD
4.2Master Clear (MCLR)
The MCLR pin provides a method for triggering an
external Reset of the device. A Reset is generated by
holding the pin low. Thes e device s have a no ise filter i n
the MCLR
Reset path which detects and ignores small
pulses.
The MCLR
pin is not drive n low by any inter nal Reset s,
including the WDT.
In the PIC18F8722 family of devices, the MCLR
input
can be disabled with the MCLRE Configuration bit.
When MCLR is disabled, the pin becomes a digital
input. See Section 11.5 “PORTE, TRISE and LATE
Registers” for more information.
4.3Power-on Reset (POR)
A Power-on Reset pulse is generated on-chip
whenever V
allows the device to start in the initialized state when
VDD is adequate for operation.
T o t ake advantage o f the POR circuitry , tie the MCLR
through a resistor (1 kΩ to 10 kΩ) to V
eliminate external RC components usually needed to
create a Power-on Reset delay . A minimum ri se rate for
DD is specified (parameter D004, “Section 28.2 “DC
V
Characteristics: Power-Down and Supply Current”).
For a slow rise time, see Figure 4-2.
When the device st arts normal operati on (i.e ., ex its the
Reset condition), device operating parameters (voltage, frequency, temperature, etc.) must be met to
ensure operation. If these conditions are not met, the
device must be held in Reset until the operating
conditions are met.
POR events are captured by the POR
The state of th e bit is set to ‘0’ wh enever a POR occurs;
it does not change for any other Reset event. POR is
not reset to ‘1’ by any hardware event. To capture
multiple events, the user manually resets the bit to ‘1’
in software following any POR.
The PIC18F 87 22 f am il y of de vi ces im p lem en ts a BO R
circuit that provides the user with a number of configuration and power-saving options. The BOR is
controlled by the BORV<1:0> and BOREN<1:0>
Configuration bits. There are a total of four BOR
configurations which are summarized in Table 4-1.
The BOR threshold is set by the BORV<1:0> bits. If
BOR is enabled (any values of BOREN<1:0>, except
‘00’), any drop of V
Section 28. 1 “DC Characteris tics”) for greater than
TBOR (parameter 35, Table 28-12) will reset the device.
A Reset may or may not occur if V
for less tha n TBOR. The chip will remain in Br own-o ut
Reset until V
If the Power-up T imer is enab led, it will be inv oked after
DD rises above VBOR; it then will keep the chip in
V
Reset for an additional time delay, T
(parameter 33, Table 28-12). If VDD drops below VBOR
while the Power-up Timer is running, the chip will go
back into a Brown-out Reset and the Power-up Timer
will be initialized. Once VDD rises above VBOR, the
Power-up Timer will execute the additional time delay.
BOR and the Power-on Timer (PWRT) are
independently configured. Enabling BOR Reset does
not automat ically enable the PWRT.
4.4.1SOF TWARE ENABLED BOR
When BOREN<1:0> = 01, the BOR can be enabled or
disabled by the user in software. This is done with the
control bit, SBOREN (RCON<6>). Setting SBOREN
enables the BOR to function as previously described.
Clearing SBOREN disables the BOR entirely. The
SBOREN bit operates only in this mode; otherwise it i s
read as ‘0’.
DD below VBOR (parameter D005,
DD falls below VBOR
DD rises abov e VBOR.
PWRT
Placing the BOR under software control gives the user
the additional flexibility of tailoring the application to its
environment withou t ha vi ng to reprogram the devi ce to
change the BOR configuration. It also allows the user
to tailor device power consumption in software by
eliminating the incremental current that the BOR consumes. While the BOR current is typically very small, it
may have some impact in low-power applications.
Note:Even when BOR is under software control,
the BOR Reset voltage level is still set by
the BORV<1:0> Configuration bits. It
cannot be changed in software.
4.4.2DETECTING BOR
When BOR is enabl ed, the BOR bit always resets to ‘0’
on any BOR or P OR event. This makes it d ifficult to
determine if a BOR event has occurre d jus t by reading
the state of BOR
simultaneously check the state of both POR
This assumes that the POR
immediately after any POR event. If BOR
POR
is ‘1’, it can be reliably assum ed that a BOR event
has occurred.
alone. A more reliable method is to
and BOR.
bit is reset to ‘1’ in software
is ‘0’ while
4.4.3DISABLING BOR IN SLEEP MODE
When BOREN<1:0> = 10 , the BOR remains under
hardware control and operates as previously
described. Whenever the device enters Sleep mode,
however , the BOR is au tom ati ca lly dis abl ed . When the
device returns to any other operating mode, BOR is
automatically re-enabled.
This mode allows for applications to recover from
brown-out situations, while actively executing code,
when the device requires BOR protection the most. At
the same time, it save s additional po wer in Sleep mod e
by eliminating the small incremental BOR current.
TABLE 4-1:BOR CONFIGURATIONS
BOR Configuration Status of
BOREN1BOREN0
00Unavailable BOR disabled; must be enabled by reprogramming the Configuration bits.
01AvailableBOR enabled in software; operation controlled by SBOREN.
10Unavailable BOR enabled in hardware in Run and Idle modes, disabled during
11Unavailable BOR enabled in hardware; must be disabled by reprogramming the
The PIC18F8722 family of devices incorporates three
separate on-chip timers that help regulate the Power-on
Reset process. Their main function is to ensure that the
device clock is stable before code is executed. These
timers are:
• Power-up Timer (PWRT)
• Oscillator Start-up Timer (OST)
• PLL Lock Time-out
4.5.1POWER-UP TIMER (PWRT)
The Power-up Timer (PWRT) of the PIC18F8722
family of devices is an 11-bit counter which uses the
INTRC source as the clock input. While the PWRT is
counting, the device is held in Reset.
The power-up time delay depe nd s on the INTRC cl oc k
and will vary from chip-to-chip due to temperature and
process variation. See DC parameter 33 in Table 28-12
for details.
The PWRT is enabled by clearing the PWRTEN
Configuration bit.
4.5.2OSCILLATOR START-UP TIMER
(OST)
The Oscillator Start-up Timer (OST) provides a 1024
oscillator cycle (from OSC1 input) delay after the
PWRT delay is over (parameter 33, Table 28-12). This
ensures that the crystal oscillator or resonator has
started and stabilized.
The OST time-out is invoked only for XT, LP, HS and
HSPLL modes and only on Power-on Reset, or on exit
from most power-manag ed modes.
4.5.3PLL LOCK TIME-OUT
With the PLL enabled in its PLL mode, the time-out
sequence following a Power-on Reset is slightly different from other oscillator modes. A separate timer is
used to provide a fixed time-out tha t i s su f f i cient for the
PLL to lock to the main oscillator frequency. This PLL
lock time-o ut (T
PLL) is typically 2 ms and follows the
oscillator start-up time-out.
4.5.4TIME-OUT SEQUENCE
On power-up, the time-out sequence is as follows:
1.After the POR pulse has cleared, PWR T time-out
is invoked (if enabled).
2. Then, the OST is activated.
The total time-out will vary based on oscillator configuration and the status of the PWRT. Figure 4-3,
Figure 4-4, Figure 4-5, Figure 4-6 and Figure 4-7 all
depict time-out sequences on power-up, with the
Power-up Timer enabled and the device operating in
HS Oscillator mode. Figure s 4-3 through 4-6 also apply
to devices operating in XT or LP m odes. F or devi ces i n
RC mode and with the PWRT disabled, on the other
hand, there will be no time-out at all.
Since the time-outs occur from the POR pulse, if MC LR
is kept low long e nough, all ti me -out s will e xpire. Brin ging MCLR
(Figure 4-5). This is useful for testing purposes or to
synchronize more than one PIC18F8722 family device
operating in parallel.
Most registers are unaffected by a Reset. Their status
is unknown on POR and unchanged by all other
Table 4-4 describes the Reset states for all of the
Special Function Registers. These are categorized by
Power-on and Brown-out Resets, Master Clear and
WDT Resets and WDT wake-ups.
Resets. All othe r reg is ters are forced to a “Reset state”
depending on the type of Reset that occurred.
Most registers are not affected by a WDT wake-up,
since this is viewed as the resumption of normal operation. Status bits from the RCON register, RI
POR
and BOR, are set or cleare d dif ferently i n dif ferent
, TO, PD,
Reset situations, as indicated in Table4-3. These bits
are used in software to determine the nature of the
Reset.
TABLE 4-3:STATUS BITS, THEIR SIGNIFICANCE AND THE INITIALIZATION CONDITION
Shaded cells indicate conditions do not apply for the designated device.
Note 1:One or more bits in the INTCONx or PIRx registers will be affected (to cause wake-up).
2:When the wake-up is due to an interrupt and the GIEL or GIEH bit is set, the PC is loaded with the interrupt vector
(0008h or 0018h).
3:When the wake-up is due to an interrupt and the GIEL or GIEH bit is set, the TOSU, TOSH and TOSL are updated with
the current value of the PC. The STKPTR is modified to point to the next location in the hardware stack.
4:See Table4-3 for Reset value for specific condition.
5:Bits 6 and 7 of PORTA, LATA and TRISA are enabled, depending on the oscillator mode selected. When not enabled
Legend:u = unchanged, x = unknown, - = unimplemented bit, read as ‘0’, q = value depends on condition.
Note 1:One or more bits in the INTCONx or PIRx registers will be affected (to cause wake-up).
Shaded cells indicate conditions do not apply for the designated device.
2:When the wake-up is due to an interrupt and the GIEL or GIEH bit is set, the PC is loaded with the interrupt vector
(0008h or 0018h).
3:When the wake-up is due to an interrupt and the GIEL or GIEH bit is set, the TOSU, TOSH and TOSL are updated with
the current value of the PC. The STKPTR is modified to point to the next location in the hardware stack.
4:See Table4-3 for Reset value for specific condition.
5:Bits 6 and 7 of PORTA, LATA and TRISA are enabled, depending on the oscillator mode selected. When not enabled
Shaded cells indicate conditions do not apply for the designated device.
Note 1:One or more bits in the INTCONx or PIRx registers will be affected (to cause wake-up).
2:When the wake-up is due to an interrupt and the GIEL or GIEH bit is set, the PC is loaded with the interrupt vector
(0008h or 0018h).
3:When the wake-up is due to an interrupt and the GIEL or GIEH bit is set, the TOSU, TOSH and TOSL are updated with
the current value of the PC. The STKPTR is modified to point to the next location in the hardware stack.
4:See Table4-3 for Reset value for specific condition.
5:Bits 6 and 7 of PORTA, LATA and TRISA are enabled, depending on the oscillator mode selected. When not enabled
Shaded cells indicate conditions do not apply for the designated device.
Note 1:One or more bits in the INTCONx or PIRx registers will be affected (to cause wake-up).
2:When the wake-up is due to an interrupt and the GIEL or GIEH bit is set, the PC is loaded with the interrupt vector
(0008h or 0018h).
3:When the wake-up is due to an interrupt and the GIEL or GIEH bit is set, the TOSU, TOSH and TOSL are updated with
the current value of the PC. The STKPTR is modified to point to the next location in the hardware stack.
4:See Table4-3 for Reset value for specific condition.
5:Bits 6 and 7 of PORTA, LATA and TRISA are enabled, depending on the oscillator mode selected. When not enabled
TABLE 4-4:INITIALIZATION CONDITIONS FOR ALL REGISTERS (CONTINUED)
MCLR
RegisterApplicable Devices
(5)
PORTA
SPBRGH16X276X228X278X220000 00000000 0000uuuu u uuu
BAUDCON16X276X228X278X2201-0 0-0001-0 0-00uu-u u-uu
SPBRGH26X276X228X278X220000 00000000 0000uuuu u uuu
BAUDCON26X276X228X278X2201-0 0-0001-0 0-00uu-u u-uu
ECCP1DEL6X276X228X278X220000 00000000 0000uuuu uuuu
TMR46X276X228X278X220000 00000000 0000uuuu uuuu
PR46X276X228X278X221111 1111uuuu uuuuuuuu uuuu
T4CON6X276X228X278X22-000 0000-000 0000-uuu uuuu
CCPR4H6X276X228X278X22xxxx xxxxuuuu uuuuuuuu uuuu
CCPR4L6X276X228X278X22xxxx xxxxuuuu uuuuuuuu uuuu
CCP4CON6X276X228X278X22--00 0000--00 0000--uu uuuu
CCPR5H6X276X228X278X22xxxx xxxxuuuu uuuuuuuu uuuu
CCPR5L6X276X228X278X22xxxx xxxxuuuu uuuuuuuu uuuu
CCP5CON6X276X228X278X22--00 0000--00 0000--uu uuuu
SPBRG26X276 X228X278X220000 00000000 0000uuuu uuuu
RCREG26X276X228X278X220000 00000000 0000uuu u u uuu
TXREG26X276X228X278X220000 00000000 0000uuuu u uuu
TXSTA26X276X228X278X220000 00100000 0010uuuu u uuu
RCSTA26X276X228X278X220000 000x0000 000xuuuu uuuu
ECCP3AS6X276X228X278X220000 00000000 0000uuu u uuuu
ECCP3DEL6X276X228X278X220000 00000000 0000uuuu uuuu
ECCP2AS6X276X228X278X220000 00000000 0000uuu u uuuu
ECCP2DEL6X276X228X278X220000 00000000 0000uuuu uuuu
SSP2BUF6X276X228X278X22xxxx xxxxuuuu uuuuuuuu uuuu
SSP2ADD6X276X228X278X220000 00000000 0000uuu u uuuu
SSP2STAT6X276X228X278X220000 00000000 0000uuuu uuuu
SSP2CON16X276X228X278X220000 00000000 0000uuu u uuuu
SSP2CON26X276X228X278X220000 00000000 0000uuu u uuuuLegend:u = unchanged, x = unknown, - = unimplemented bit, read as ‘0’, q = value depends on condition.
Shaded cells indicate conditions do not apply for the designated device.
Note 1:One or more bits in the INTCONx or PIRx registers will be affected (to cause wake-up).
2:When the wake-up is due to an interrupt and the GIEL or GIEH bit is set, the PC is loaded with the interrupt vector
(0008h or 0018h).
3:When the wake-up is due to an interrupt and the GIEL or GIEH bit is set, the TOSU, TOSH and TOSL are updated with
the current value of the PC. The STKPTR is modified to point to the next location in the hardware stack.
4:See Table4-3 for Reset value for specific condition.
5:Bits 6 and 7 of PORTA, LATA and TRISA are enabled, depending on the oscillator mode selected. When not enabled
There are three types of memory in PIC18 Enhanced
microcontroller devices:
• Program Memory
• Data RAM
• Data EEPROM
As Harvard architecture dev ices, the dat a and progra m
memories use separate busses; this allows for concurrent access of the two memory spaces. The data
EEPROM, for practical purposes, can be regarded as
a peripheral device, since it is addresse d and accessed
through a set of control registers.
Additional detailed information on the operation of the
Flash program memory is provided in Section 6.0“Flash Program Memory”. Data EEPROM is
discussed s eparately in Section 8.0 “Data EEPROM
Memory”.
5.1Program Memory Organization
PIC18 microcontrollers implement a 21-bit program
counter, which is capable of addressing a 2-Mbyte
program memory space. Accessing a location between
the upper boundary of the physically implemented
memory and the 2-Mbyte address will return all ‘0’s (a
NOP instruction).
The PIC18F6527 and PIC18F8527 each have 48 Kbytes
of Flash memory an d can sto re up to 24, 576 sing le-wor d
instructions.
The PIC18F6622 and PIC18F8622 each have 64 Kbytes
of Flash memory an d can sto re up to 32, 768 sing le-wor d
instructions.
The PIC18F6627 a nd PIC18F86 27 each hav e 96 Kbytes
of Flash memory an d can sto re up to 49, 152 sing le-wor d
instructions.
The PIC18F6722 and PIC18F8722 each have
128 Kbytes of Flash memory and can store up to
65,536 single-word instructions.
PIC18 devices have two interrupt vectors. The Reset
vector address is at 0000h and the interrupt vector
addresses are at 0008h and 0018h.
The program memory map for the PIC18F8722 family
of devices is shown in Figure 5-1.
5.1.1PIC18F8527/8622/8627/8722
PROGRAM MEMORY MODES
PIC18F8527/8622/8627/8722 devices differ significantly from their PIC18 pred ecesso rs in their util izatio n
of program memory. In addition to available on-chip
Flash program memory, these controllers can also
address up to 2 Mbytes of external program memory
through the external memory interface. There are four
distinct operating modes available to the controllers:
• Microprocessor (MP)
• Microprocessor with Boot Block (MPBB)
• Extended Microcontroller (EMC)
• Microcontroller (MC)
The program memory mode is determined by setting
the two Least Significant bits of the Configuration
Register 3L (CONFIG3L) as shown in Register 25-4
(see Section 25.1 “Configuration Bits” for additional
details on the device Configuration bits).
The program memory modes operate as follows:
•The Microprocessor Mode permits access only
to external program memory; the contents of the
on-chip Flash memory are ignored. The 21-bit
program counter permits access to a 2-Mbyte
linear program memory space.
• The Microprocessor with Boot Block Mode
accesses on-chip Flash memory from the boot
block. Above this, external program memory is
accessed all the way up to the 2-Mbyte limit.
Program execution automatically switches
between the two memories as required. The boot
block is configurable to 1, 2 or 4 Kbytes.
• The Microcontroller Mode accesses only
on-chip Flash memory. Attempts to read above the
physical limit of the on-chip Flash (0BFFFh for the
PIC18F8527, 0FFFFh for the PIC18F8622,
17FFFh for the PIC18F8627, 1FFFFh for the
PIC18F8722) causes a read of all ‘0’s (a NOP
instruction).
The Microcontroller mode is also the only operating
mode available to PIC18F6527/6622/6627/6722
devices.
•The Extended Microcontroller Mode allows
access to both internal and external program
memories as a single block. The device can
access its entire on-chip Flash memory; above
this, the device accesses external program
memory up to the 2-Mbyte program space limit.
As with Boot Block mode, ex ecution a utomatica lly
switches between the two memories as required.
In all modes, the microcontroller has complete access
to data RAM and EEPROM.
Figure 5-2 comp are s t he me mo ry m aps of the dif fere nt
program memory modes. The differences between
on-chip and external memory access limitations are
more fully explained in Table 5-1.
2:PIC18F6622 and PIC18F8622.
3:PIC18F6627 and PIC18F8627.
4:PIC18F6722 and PIC18F8722.
5:This is the only mode available on PIC18F6527/6622/6627/6722 devices.
6:Boot block size is determined by the BBSIZ<1:0> bits in CONFIG4L.
000FFFh
(6)
or
001FFFh
(6)
001000h
(6)
or
002000h
(6)
010000h
(2)
0C000h
(1)
020000h
(4)
018000h
(3)
0FFFFh
(2)
0BFFFh
(1)
01FFFFh
(4)
017FFFh
(3)
010000h
(2)
0C000h
(1)
020000h
(4)
018000h
(3)
FIGURE 5-2:MEMORY MAPS FOR PIC18F8722 FAMILY PROGRAM MEMORY MODES
The Program Counter (PC ) specifies the address of th e
instruction to fetch for execu tion. The PC is 21 bits wide
and is contained in three separate 8-bit registers. The
low byte, known as the PCL register, is both readable
and writable. The high byt e, or PCH re gister, contains
the PC<15:8> bits; i t is not directly re adable or writ able.
Updates to the PCH register are perfo rmed through the
PCLATH register. The upper byte is called PCU. This
register contains the PC<20:16> bits; it is also not
directly readable or writable. Updates to the PCU
register are performed through the PCLATU register.
The contents of PCLATH and PCLATU are transferred
to the program counter by any operation that writes
PCL. Similarly, the upper two bytes of the program
counter are transferred to P CLATH and PCLATU by an
operation that reads PCL. This is useful for computed
offsets to the PC (see Section 5.1.5.1 “ComputedGOTO”).
The PC addresses bytes in the program memory. To
prevent the PC from becoming misaligned with word
instructions, the Least Significant bit of PCL is fixed to
a value of ‘0’. The PC increments by 2 to address
sequential instructions in the program memory.
The CALL, RCALL, GOTO and program branch
instructions write to the program counter directly. For
these instructions, the contents of PCLATH and
PCLATU are not transferred to the program counter.
5.1.3RETURN ADDRESS STACK
The return address s tack allows any co mb ination of up
to 31 program calls and interrupts to occur. The PC is
pushed onto th e stac k when a CALL or RCALL instruction is executed or an interrupt is Acknowledged. The
PC value is pulled off the stack on a RETURN, RETLW
or a RETFIE instruction. PCLATU and PCLATH are not
affected by any of the RETURN or CALL instructions.
The stack operates as a 31-word by 21-bit RAM and a
5-bit Stack Pointer, STKPTR. The stac k space is not
part of either program or da ta sp ace. The Stack Point er
is readable and writable and the address on the top of
the stack is readable and writable through the top-ofstack Special File Registers. Data can also be pushed
to, or popped from the stack, using these registers.
A CALL type instru ctio n cau ses a pu sh ont o the stack;
the Stack Pointer is first incremented and the location
pointed to by the Stack Pointer is written with the
contents of the PC (already pointing to the instruction
following the CALL). A RETURN type instruction causes
a POP from the stack; the contents of the location
pointed to by the STKPTR are transferred to the PC
and then the Stack Pointer is decremented.
The Stack Pointer is initialized to ‘00000’ after all
Resets. There is no RAM associated with the location
corresponding to a Stack Pointer value of ‘00000’; this
is only a Reset value. Stat us bit s in dic ate if the stack is
full or has overflowed or has underflowed.
5.1.3.1Top-of-Stack Access
Only the top of the return address stack (TOS) is
readable and writable. A set of three registers,
TOSU:TOSH:TOSL, hold the content s of the stack location pointed to by the STKPTR register (Figure5-3). This
allows users to implement a software stack if nec essary.
After a CALL, RCALL or interrupt, the software can read
the pushed value by reading the TOSU:TOSH:TOSL
registers. These values can be placed on a use r defined
software stack. At return time, the software can return
these values to TOSU:TOSH:TOSL and do a return.
The user must disable the global interrupt enable bits
while accessing the stack to prevent inadvertent stack
corruption.
FIGURE 5-3:RETURN ADDRESS STACK AND ASSOCIATED REGISTERS
The STKPTR register (Register5-1) contains the St ack
Pointer value, the STKFUL (Stack Full) status bit and
the STKUNF (Stack Underflow) status bits. The value
of the Stack Pointer can be 0 through 31. The Stack
Pointer increments before values are pushed onto the
stack and decrements after values are popped off the
stack. On Reset, the Stack Pointer value will be zero.
The user may read and write the Stack Pointer value.
This feature can be used by a Real-Time Operating
System (RTOS) for return stack maintenance.
After the PC is pu sh ed ont o the s ta ck 31 time s (witho ut
popping any values off the stack), the STKFUL bit is
set. The STKFUL bit is cleared by software or by a
POR.
The action that takes place when the stack becomes
full depends on the state of the STVREN (Stack Overflow Reset Enable) Configuration bit. (Refer to
Section 25.1 “Configuration Bit s” for a descrip tion of
the device Configuration bits.) If STVREN is set
(default) , the 31st PUSH will push the (PC + 2) value
onto the stack, set the STKFUL bit and reset the
device. The STKFUL bit will remain set and the Stack
Pointer will be set to zero.
If STVREN is cleared, the STKFUL bi t will be set on the
31st PUSH and the Stack Pointer will increment to 31.
Any additional pushes will not overwrite the 31st PUSH
and STKPTR will remain at 31.
When the stack has been popped enough times to
unload the stack, the next POP will return a value of
zero to the PC and set the STKUNF bit, wh ile the S t ack
Pointer remains at zero. The STKUNF bit will remain
set until cleared by software or until a POR occurs.
Note:Returning a value of zero to the PC on an
underflow has the effect of vectoring the
program to the Reset vector, where the
stack conditions can be verified and
appropriate actions can be taken. This is
not the same as a Reset, as the contents
of the SFRs are not affected.
5.1.3.3PUSH and POP Instructions
Since the Top-of-Stack is readable and writable, the
ability to push value s on to the st ac k an d pul l values off
the stack without disturbing normal program execution
is a desirable feature. The PIC18 instruction set
includes two instructions, PUSH and POP, that permit
the TOS to be manipulated under software control.
TOSU, TOSH and T OS L can be m odifie d to plac e dat a
or a return address on the stack.
The PUSH instruction places the current PC value onto
the stack. This increments the Stack Pointer and loads
the current PC value onto the stack.
The POP instruction discards the current TOS by decrementing the Stack Pointer. The previous value pushed
onto the stack then becomes the TOS value.
REGISTER 5-1:STKPTR: STACK POINTER REGISTER
R/C-0R/C-0U-0R/W-0R/W-0R/W-0R/W-0R/W-0
STKFUL
bit 7bit 0
Legend:
R = Readable bitW = Writable bitU = Unimplemented bit, read as ‘0’
-n = Value at POR‘1’ = Bit is set‘0’ = Bit is clearedx = Bit is unknown
bit 7STKFUL: Stack Full Flag bit
bit 6STKUNF: Stack Underflo w Flag bit
bit 5Unimplemented: Read as ‘0’
bit 4-0SP<4:0>: Stack Pointer Location bits
Note 1: Bit 7 and bit 6 are cleared by user software or by a POR.
(1)
STKUNF
1 = Stack became full or overflowed
0 = Stack has not become full or overflowed
1 = Stack underflow occurred
0 = Stack underflow did not occur
TABLE MOVFPCL, F; A simple read of PCL will update PCLATH, PCLATU
RLNCFW, W; Multiply by 2 to get correct offset in table
ADDWFPCL; Add the modified offset to force jump into table
RETLW‘A’
RETLW‘B’
RETLW‘C’
RETLW‘D’
RETLW‘E’
END
5.1.3.4Stack Full and Underflow Resets
Device Resets on stack overflow and stack underflow
conditions are enabled by setting the STVREN bit in
Configuration Register 4L. When STVREN is set, a ful l
or underflow will set the appropriate STKFUL or
STKUNF bit and then cause a device Reset. When
STVREN is cleared, a full or underflow condi tion will set
the appropriate STKFUL or STKUNF bit, but not caus e
a device Reset. The STKFUL or STKUNF bits are
cleared by the user software or a Power-on Reset.
5.1.4FAST REGISTER STACK
A fast register stack is provided for the STATUS,
WREG and BSR registers, to provide a “fast return”
option for interrupts. The stack for each register is onl y
one level deep and is neith er readable no r writable. It is
loaded with the curre nt val ue of the corres pondi ng register when the processor vectors for an interrupt. All
interrupt sources will push values into the Stack registers. The values in the registers are then loaded back
into their associated registers if the RETFIE, FAST
instruction is used to return from the interrupt.
If both low and high-priority interrupts are enabled, the
stack registers cannot be used reliably to return from
low-priority interrupts. If a high-priority interrupt occurs
while servicing a low-priority interrupt, the Stack register values stored by the low-priority interrupt will be
overwritten. In these cases, users must save the key
registers in software during a low-priority interrupt.
If interrupt priority is not used, all interrupts ma y use the
fast register stack for returns from interrupt. If no interrupts are used, the fast register stack can be used to
restore the STATUS, WREG and BSR registers at the
end of a subroutine call. To use the fast register stack
for a subroutine call, a CALL label, FAST instruction
must be executed to save the STATUS, WREG and
BSR registers to the fast register stack. A
RETURN, FAST instruction is then executed to restore
these registers from the fast register stack.
Example 5-1 shows a source code example that uses
the fast register stack during a subroutine call and return.
EXAMPLE 5-1:FAST REGISTER STACK
CODE EXAMPLE
5.1.5LOOK-UP TABLES IN PROGRAM
MEMORY
There may be programming situations that require the
creation of data structures, or look-up tables, in
program memory. For PIC18 devices, look-up tables
can be implemented in two ways:
• Computed GOTO
• Table Reads
5.1.5.1Computed GOTO
A computed GOTO is accompli shed by adding an offset
to the program counter. An example is shown in
Example 5-2.
A look-up table can be formed with an ADDWF PCL
instruction and a group of RETLW nn instructions. The W
register is load ed with an of fset in to the t able bef ore executing a call to that table. The first instruction of the called
routine is the ADDWF PCL instruction. The next instruction
executed will be one of th e RETLW nn instru ctions that
returns the valu e ‘nn’ to t he calling func tio n.
The offset value (in WREG) specifies the number of
bytes that the program counter should advance and
should be multiples of 2 (LSb = 0).
In this method, only one data byte may be stored in
each instruction location and room on the return
address stack is required.
Note:The “ADDWF PCL” instruction does not
update the PCLATH and PCLATU registers.
A read operation on PCL must be performed
to update PCLATH and PCLA TU.
All instructions are single cycle, except for any program branche s. These tak e two cycles since the fetch instruct ion
is “flushed” from the pipeline while the new instruction is being fetched and then executed.
TCY0TCY1TCY2TCY3TCY4TCY5
1. MOVLW 55h
Fetch 1Execute 1
2. MOVWF PORTB
Fetch 2Execute 2
3. BRA SUB_1
Fetch 3Execute 3
4. BSF PORTA, BIT3 (Forced NOP)
Fetch 4Flush (NOP)
5. Instruction @ address SUB_1
Fetch SUB_1 Execute SUB_1
5.1.5.2Table Reads and Table Writes
A better method of storing data in program memory
allows two bytes of dat a to be stored in each instruction
location.
Look-up table data may be stored two bytes per program word by using table reads and writes. The Table
Pointer (TBLPTR) register specifies the byte address
and the Table Latch (TABLAT) register contains the
data that is read from or wr itten to progr am memory.
Data is transferred to or from program memory one
byte at a time.
Table read and table write operations are discussed
further in Section 6.1 “Table Reads and Table
Writes”.
5.2PIC18 Instruction Cycle
5.2.1CLOCKING SCHEME
The microcontroller clock input, whether from an internal
or external source, is internally divided by four to generate four non-overlapping quadrature clocks (Q1, Q2, Q3
and Q4). Internally, the program counter is incremented
on every Q1; the instruction is fetched from the program
FIGURE 5-4:CLOCK/INSTRUCTION CYCLE
memory and latched into the instruction register during
Q4. The instruction is decoded and executed during the
following Q1 through Q4. The clocks and instruction
execution flow are shown in Figure 5-4.
5.2.2INSTRUCTION FLOW/PIPELINING
An “Instruction Cycle” consists of four Q cycles: Q1
through Q4. The instruction fetch and execute are
pipelined in such a manner that a fetch takes one
instruction cycle, while the decode and execute take
another instruction cycle. However, due to the pipelining, each instruction effectively executes in one
cycle. If a n instruc tion caus es the pro gram coun ter to
change (e.g., GOTO), then two cycles are required to
complete the instruction (Example 5-3).
A fetch cycle begins with the program counter
incrementing in Q1.
In the execution cy cle, the fetch ed instruction i s latched
into the Instruction Register (IR) in cycle Q1. This
instruction is then decoded and executed during the
Q2, Q3 and Q4 c ycles. Dat a m emory is read during Q2
(operand read) and written during Q4 (destination
write).
The program memory is addressed in bytes. Instructions are stored as two bytes or four bytes in program
memory. The Least Significant Byte of an instruction
word is always stored in a program memory location
with an even address (LSb = 0). To maintain alignment
with instruction bo undaries , the PC incr ements in step s
of 2 and the LSb wi ll always read ‘0’ (see Section 5.1.2“Program Counter”).
Figure 5-5 shows an ex am ple of h ow in st ruc tion w ord s
are stored in the program memory.
The CALL and GOTO instructions have the absolute program memory address embedded into the instruction.
Since instructions are always stored on word boundaries, the data contained in the instruction is a word
address. The word address is written to PC<20:1>,
which accesses the desired byte address in program
memory. Instruction #2 in Figure 5-5 shows how the
instruction GOTO 0006h is encoded in the program
memory. Program branch instructions, which encode a
relative address offset, operate in the same ma nner. The
offset value stored in a branch instruction represents the
number of single-word instructions that the PC will be
offset by. Section 26.0 “Instruction Set Summary”
provides further details of the instruction set.
The standard PIC18 instruction set has 8 two-word
instructions: CALL, MOVFF, GOTO, LSFR, ADDULNK,CALLW, MOVSS and SUBULNK. In all cases, the
second word of th e instructi ons always ha s ‘1111’ as
its four Most Signi fican t bit s; the oth er 12 bit s are li teral
data, usually a data memory address.
The use of ‘1111’ in the 4 MSbs of an instruction specifies a special form of NOP. If the instruction is executed
in proper sequence – immed iate ly af ter the first word –
the data in the s econd w ord is ac cessed an d used by
the instruction seq ue nce . If the first word is skipped for
some reason and the se cond word is ex ecuted by itsel f,
a NOP is executed instead. This is necessary for cases
when the two-word instruction is preceded by a conditional instruction that changes the PC. Example 5-4
shows how this works.
Note:See Section 5.6 “PIC18 Instruction
Execution and the Extended Instruction Set” for information on two-word
instructions in the extended instruction set.
EXAMPLE 5-4:TWO-WORD INSTRUCTIONS
CASE 1:
Object CodeSource Code
0110 0110 0000 0000TSTFSZREG1; is RAM location 0?
1100 0001 0010 0011MOVFFREG1, REG2 ; No, skip this word
1111 0100 0101 0110; Execute this word as a NOP
0010 0100 0000 0000ADDWFREG3; continue code
CASE 2:
Object CodeSource Code
0110 0110 0000 0000TSTFSZREG1; is RAM location 0?
1100 0001 0010 0011MOVFFREG1, REG2 ; Yes, execute this word
1111 0100 0101 0110; 2nd word of instruction
0010 0100 0000 0000ADDWFREG3; continue code
memory are changed when the PIC18
extended instruction set is enabled. See
Section 5.5 “Data Memory and the
Extended Instruction Set” for more
information.
The data memory in PIC18 devices is implemented as
static RAM. Each register in the data memory has a
12-bit address, allowing up to 4096 bytes of data
memory . The m emory sp ace is div ided into as many as
16 banks that con tain 256 by tes each; the PIC18F 8722
family of devices implements all 16 banks. Figure 5-6
shows the data memory organization for the
PIC18F8722 family of devices.
The data memory contains Special Function Registers
(SFRs) and General Purpose Registers (GPRs). The
SFRs are used for control and status of the controller
and peripheral functio ns, while GPRs are us ed for data
storage and scratchpad operations in the user’s
application. Any re ad of an unimpl emented location will
read as ‘0’s.
The instruction set and architecture allow operations
across all banks. The entire data memory may be
accessed by Direct, Indirect or Indexed Addressing
modes. Addressing modes are discussed later in this
subsection.
To ensure that commonly used registers (SFRs and
select GPRs) c an b e ac ce ssed in a si ngle cyc le, PI C18
devices impl em ent an Ac ce ss Ba nk . Th is i s a 256-byte
memory space that pr ovid es fa st acc ess to SFRs a nd
the lower portion of GPR Bank 0 without using the
BSR. Section 5.3.2 “Access Bank” provides a
detailed description of the Access RAM.
5.3.1BANK SELECT REGISTER (BSR)
Large areas of data memory require an efficient
addressing scheme to make rapid access to any
address possible. Ideally, this means that an entire
address does not need to be provided for each read or
write operation. For PIC18 devices, this is accomplished with a RAM banking scheme. This divides the
memory space into 16 contiguous banks of 256 bytes.
Depending on the instruction, each location can be
addressed directly by its full 12-bit address, or an 8-bit
low-order address and a 4-bit Bank Pointer.
Most instruct ions in th e PIC18 in struct ion set ma ke use
of the Bank Pointer , known as the Ba nk Select Reg ister
(BSR). This SFR holds the 4 Most Significant bits of a
location’s address; the instruction itself includes the
8 Least Significant bits. Only the four lower bits of the
BSR are implemented (BSR<3:0>). Th e upper four bit s
are unused; they will always read ‘0’ and cannot be
written to. The BSR can be l oaded direc tly b y using the
MOVLB instruction.
The value of the BSR indicates the bank in data
memory; the 8 bits in the instruction show the location
in the bank and can be thought of as an o f fs et from th e
bank’s lower boundary. The relationship between the
BSR’s value and the bank division in data memory is
shown in Figure 5-7.
Since up to 16 reg isters m ay sh are the same l ow-ord er
address, the user must alway s be careful to ensure that
the proper bank is selected before performing a data
read or write. For example, writing what should be
program data to an 8 -bi t ad dres s of F 9h w h il e th e BSR
is 0Fh will end up resetting the program counter.
While any bank can be s el ec ted, only those banks th at
are actually implemented can be read or written to.
Writes to unimplemented banks are ignored, while
reads from unimplemented banks will return ‘0’s. Even
so, the STATUS register will still be affected as if the
operation was successful. The data memory map in
Figure 5-6 indicates which banks are implemented.
In the core PIC18 instruction set, only the MOVFF
instruction fully specifies the 12-bit address of the
source and target registers. This i nstruction ig nores the
BSR completely when it ex ecutes. All o ther instructi ons
include only the low-order address as an operand and
must use either the BSR or the Access Bank to locate
their target registers.
Note 1:The Access RAM bit of the instruction can be used to force an override of the selected bank (BSR<3:0>) to
the registers of the Access Bank.
2:The
MOVFFinstruction embeds the entire 12-bit address in the instruction.
Data
Memory
Bank Select
(2)
7
0
From Opcode
(2)
0000
000h
100h
200h
300h
F00h
E00h
FFFh
Bank 0
Bank 1
Bank 2
Bank 14
Bank 15
00h
FFh
00h
FFh
00h
FFh
00h
FFh
00h
FFh
00h
FFh
Bank 3
through
Bank 13
0011
11111111
7
0
BSR
(1)
FIGURE 5-7:USE OF THE BANK SELECT REGISTER (DIRECT ADDRESSING)
5.3.2ACCESS BANK
While the use of the BSR with an embedded 8-bit
address allows users to address the entire range of
data memory, it also means th at the user must a lways
ensure that the correct bank is selected. Otherwise,
data may be read from or written to the wrong location.
This can be disastrous if a GPR is the intended target
of an operation, but an SFR is written to instead.
Verifying and/or changing the BSR for each read or
write to data memory can become very inefficient.
memory locations, the data memory is configured with
an Access Bank, which allows users to access a
mapped block of memory without specifying a BSR.
The Access Bank consists of the first 96 bytes of
T o stre amline acces s for the most commonl y used data
memory (00h-5Fh) in Bank 0 and the last 160 bytes of
memory (60h-FFh) in Block 15 . The lower half is known
as the “Access RAM” and is composed of GPRs. This
upper half is also where the device’s SFRs are
mapped. These two areas are mapped contiguously in
the Access Bank and can be addressed in a linear
fashion by an 8-bit address (Figure 5-6).
The Access Bank is used by core PIC18 instructions
that inclu de the Acce ss RAM bit ( the ‘a’ parame ter in
the instruction). When ‘a’ is equal to ‘1’, the instru ct ion
uses the BSR and the 8-bit address included in the
opcode for the data memory address. When ‘a’ is ‘0’,
however, the instruction is forced to use the Access
Bank address map; the current value of the BSR is
ignored entirely.
Using this “forced” addressing allows the instruction to
operate on a data address in a single cycle, without
updating the BSR first. For 8-bit addresses of 60h and
above, this mean s that use rs can ev aluate an d operate
on SFRs more efficiently. The Access RAM below 60h
is a good place for da ta values that the user might need
to access rapidly, such as immediate computational
results or common program variables. Access RAM
also allows for faster and more code efficient context
saving and switching of variables.
The mapping of the Access Bank is slightly different
when the extended instruction set is enabled (XINST
Configuration bit = 1). This is discussed in more deta il
in Section 5.5.3 “Mapping the Access Bank inIndexed Literal Offset Mode”.
5.3.3GENER AL PURPOSE REGISTER
FILE
PIC18 devices may have banked memory in the GPR
area. This is data RAM, which is available for use by all
instructions. GPRs start at the bottom of Bank 0
(address 000h) and grow upwards towards the bottom of
the SFR area. GPRs are not initialized by a Power-on
Reset and are unchanged on all other Resets.
The Special Function Registers (SFRs) are registers
used by the CPU and p eripheral modul es for controllin g
the desired operation of the device. These reg isters are
implemented as static RAM. SFRs start at the top of
data memory (FF Fh) an d extend downw ard to oc cupy
the top half of Bank 15 (F60h to FFFh). A list of these
registers is given in Table 5-2 and Table 5-3.
The SFRs can be classified into two sets: those
associated with the “core” device functionality (ALU,
Resets and interrupts) and those related to the
peripheral functions. The Reset and interrupt registers
are described in their respective chapters, while the
ALU’s STATUS register is described later in this section. Registers related to the operation of a peripheral
feature are described in the chapter for that pe riphera l.
The SFRs are typically distributed among the
peripherals whose fun cti ons th ey c ontr ol. U nus ed SFR
locations are unimplemented and read as ‘0’s.
TABLE 5-2:SPECIAL FUNCTION REGISTER MAP FOR THE PIC18F8722 FAMILY OF DEVICES
TOSU
TOSHTop-of-Stack High Byte (TOS<15:8>)0000 0000 57, 66
TOSLTop-of-Stack Low Byte (TOS<7:0>)0000 0000 57, 66
STKPTRSTKFUL
PCLATU
PCLATHHol d ing R egist er for PC< 15: 8>0000 0000 57, 66
PCLPC Low Byte (PC<7:0>)0000 0000 57, 66
TBLPTRU
TBLPTRHProgram Memory Table Pointer High Byte (TBLPTR<15:8>)0000 0000 57, 90
TBLPTRLProgram Memory Table Pointer Low Byte (TBLPTR<7:0>)0000 0000 57, 90
TABLATProgram Memory Table Latch0000 0000 57, 90
PRODHProduct Register High Bytexxxx xxxx 57, 117
PRODLProduct Register Low Bytexxxx xxxx 57, 117
INTCONGIE/GIEHPEIE/GIELTMR0IEINT0IERBIETMR0IFINT0IFRBIF0000 000x 57, 121
INTCON2RBPU
INTCON3INT2IPINT1IPINT3IEINT2IEINT1IEINT3IFINT2IFINT1IF1100 0000 57, 123
INDF0Uses contents of FSR0 to address data memory – value of FSR0 not changed (not a physical register)N/A57, 82
POSTINC0Uses contents of FSR0 to address data memory – value of FSR0 post-incremented (not a physical register)N/A57, 82
POSTDEC0 Uses contents of FSR0 to address data memory – value of FSR0 post-decremented (not a physical register)N/A57, 82
PREINC0Uses contents of FSR0 to address data memory – value of FSR0 pre-incremented (not a physical register)N/A57, 82
PLUSW0Uses contents of FSR0 to address data memory – value of FSR0 pre-incremented (not a physical register) –
FSR0H
FSR0LIndirect Data Memory Address Pointer 0 Low Bytexxxx xxxx 57, 82
WREGWorking Regi st erxxxx xxxx57
INDF1Uses contents of FSR1 to address data memory – value of FSR1 not changed (not a physical register)N/A57, 82
POSTINC1Uses contents of FSR1 to address data memory – value of FSR1 post-incremented (not a physical register)N/A57, 82
POSTDEC1 Uses contents of FSR1 to address data memory – value of FSR1 post-decremented (not a physical register)N/A57, 82
PREINC1Uses contents of FSR1 to address data memory – value of FSR1 pre-incremented (not a physical register)N/A57, 82
PLUSW1Uses contents of FSR1 to address data memory – value of FSR1 pre-incremented (not a physical register) –
FSR1H
FSR1LIndirect Data Memory Address Pointer 1 Low Bytexxxx xxxx 58, 82
BSR
INDF2Uses contents of FSR2 to address data memory – value of FSR2 not changed (not a physical register)N/A58, 82
POSTINC2Uses contents of FSR2 to address data memory – value of FSR2 post-incremented (not a physical register)N/A58, 82
POSTDEC2 Uses contents of FSR2 to address data memory – value of FSR2 post-decremented (not a physical register)N/A58, 82
PREINC2Uses contents of FSR2 to address data memory – value of FSR2 pre-incremented (not a physical register)N/A58, 82
PLUSW2Uses contents of FSR2 to address data memory – value of FSR2 pre-incremented (not a physical register) –
Legend:x = unknown , u = unchanged, - = unimplemented, q = value depends on condition
Note 1:The SBOREN bit is only available when the BOREN<1:0> Configuration bits = 01; otherwise, this bit reads as ‘0’.
2:These registers and/or bits are not implemented on 64-pin devices and are read as
3:The PLLEN bit is only available in specific oscillator configuration; otherwise, it is disabled and reads as
4:RA6/RA7 and their associated latch and direction bits are individually configured as port pins based on various primary oscillator modes.
5:RG5 and LATG5 are only available when Master Clear is disabled (MCLRE Configuration bit = 0); otherwise, RG5 and LATG5 read as
6:Bit 7 and Bit 6 are cleared by user software or by a POR.
7:Bit 21 of TBLPTRU allows access to the device Configuration bits.
Legend:x = unknown , u = unchanged, - = unimplemented, q = value depends on condition
Note 1:The SBOREN bit is only available when the BOREN<1:0> Configuration bits = 01; otherwise, this bit reads as ‘0’.
2:These registers and/or bits are not implemented on 64-pin devices and are read as
3:The PLLEN bit is only available in specific oscillator configuration; otherwise, it is disabled and reads as
4:RA6/RA7 and their associated latch and direction bits are individually configured as port pins based on various primary oscillator modes.
5:RG5 and LATG5 are only available when Master Clear is disabled (MCLRE Configuration bit = 0); otherwise, RG5 and LATG5 read as
6:Bit 7 and Bit 6 are cleared by user software or by a POR.
7:Bit 21 of TBLPTRU allows access to the device Configuration bits.
Legend:x = unknown , u = unchanged, - = unimplemented, q = value depends on condition
Note 1:The SBOREN bit is only available when the BOREN<1:0> Configuration bits = 01; otherwise, this bit reads as ‘0’.
(2)
(2)
(2)
(2)
(2)
2:These registers and/or bits are not implemented on 64-pin devices and are read as
3:The PLLEN bit is only available in specific oscillator configuration; otherwise, it is disabled and reads as
4:RA6/RA7 and their associated latch and direction bits are individually configured as port pins based on various primary oscillator modes.
5:RG5 and LATG5 are only available when Master Clear is disabled (MCLRE Configuration bit = 0); otherwise, RG5 and LATG5 read as
6:Bit 7 and Bit 6 are cleared by user software or by a POR.
7:Bit 21 of TBLPTRU allows access to the device Configuration bits.
Legend:x = unknown , u = unchanged, - = unimplemented, q = value depends on condition
Note 1:The SBOREN bit is only available when the BOREN<1:0> Configuration bits = 01; otherwise, this bit reads as ‘0’.
2:These registers and/or bits are not implemented on 64-pin devices and are read as
3:The PLLEN bit is only available in specific oscillator configuration; otherwise, it is disabled and reads as
4:RA6/RA7 and their associated latch and direction bits are individually configured as port pins based on various primary oscillator modes.
5:RG5 and LATG5 are only available when Master Clear is disabled (MCLRE Configuration bit = 0); otherwise, RG5 and LATG5 read as
6:Bit 7 and Bit 6 are cleared by user software or by a POR.
7:Bit 21 of TBLPTRU allows access to the device Configuration bits.
The STATUS register, shown in Register 5-2, contains
the arithmetic status of the ALU. As wi th any other SFR,
it can be the operand for any instruction.
If the STA TUS register is the destination for an instruction
that affects the Z, DC, C, OV or N bits, the results of the
instruction are not written; instead, the STATUS register
is updated a ccording to the i nstructio n perfor med. There fore, the result of an inst ruction with th e STATUS registe r
as its destinat ion may b e differe nt than inten ded. As an
example, CLRF STATUS will set the Z bit and leave the
remaining Status bits unchanged (‘000u u1uu’).
It is recommended that only BCF, BSF, SWAPF , MOVFF
and MOVWF instructions are used to alter the STATUS
register , b ecaus e thes e ins tructi ons d o not af fect t he Z,
C, DC, OV or N bits in the STATUS register.
For other instructions that do not aff ect Status bi t s , se e
the instruction set summaries in Table 26-2 and
Table 26-3.
Note:The C and DC bits operate as the borrow
and digit borrow bits, respectively, in
subtraction.
REGISTER 5-2:STATUS: ARITHMETIC STATUS REGISTER
U-0U-0U-0R/W-xR/W-xR/W-xR/W-xR/W-x
———NOVZDC
bit 7bit 0
Legend:
R = Readable bitW = Writable bitU = Unimplemented bit, read as ‘0’
-n = Value at POR‘1’ = Bit is set‘0’ = Bit is clearedx = Bit is unknown
(1)
(2)
C
bit 7-5Unimplemented: Read as ‘0’
bit 4N: Negative bit
This bit is used for signed arithmetic (2’s complement). It indicates whether the result was
negative (ALU MSB = 1).
1 = Result was negative
0 = Result was positive
bit 3OV: Overflow bit
This bit is used for signed arithmetic (2’s complement). It indicates an overflow of the 7-bit
magnitude which causes the sign bit (bit 7 of the result) to change state.
1 = Overflow occurred for signed arithmetic (in this arithmetic operation)
0 = No overflow occurred
bit 2Z: Zero bit
1 = The result of an arithmetic or logic operation is zero
0 = The result of an arithmetic or logic operation is not zero
(1)
bit
(2)
bit
bit 1DC: Digit Carry/borrow
For ADDWF, ADDLW, SUBLW and SUBWF instructions:
1 = A carry-out from the 4th low-order bit of the result occurred
0 = No carry-out from the 4th low-order bit of the result
bit 0C: Carry/borrow
For ADDWF, ADDLW, SUBLW and SUBWF instructions:
1 = A carry-out from the Most Significant bit of the result occurred
0 = No carry-out from the Most Significant bit of the result occurred
Note 1: For borrow,
operand. For rotate (RRF, RLF) instructions, this bit is lo ade d with either bit 4 or bit 3 of the sourc e re gis ter.
2: For borrow,
operand. For rotate (RRF, RLF) instructions, this bit is loaded with either the high or low-order bit of the
source register.
the polarity is reversed. A subtractio n is execu ted by adding th e 2’scomplement of the second
the polarity is reversed. A subtractio n is execu ted by adding th e 2’scomplement of the second
core PIC18 instruction set are changed
when the PIC18 extended instruction set is
enabled. See Section 5.5 “Data Memoryand the Extended Instruction Set” for
more information.
The data memory space can be addr essed in se veral
ways. For most instructions, the addressing mode is
fixed. Other instructions may use up to three modes,
depending on whic h operands are used and whe ther or
not the extended instruction set is enabled.
The addressing modes are:
• Inherent
• Literal
•Direct
•Indirect
An additional addressing mode, Indexed Literal Offset,
is available when the extended instruction set is
enabled (XINST Configuration bit = 1). Its operation is
discussed in greater detail in Section 5.5.1 “IndexedAddressing with Literal Offset”.
5.4.1INHERENT AND LITERAL
ADDRESSING
Many PIC18 control instructions do not need any argument at all; they either perform an operation that globally
affects the device or they operate implicitly on one
register. This addressing mode is known as Inherent
Addressing. Examples include SLEEP, RESET and DAW.
Other instructions work in a similar way but require an
additional explicit argument in the opcode. This is
known as Literal Addressing mode because they
require some literal value as an argument. Examples
include ADDLW and MOVLW, which respectively, add or
move a literal value to the W register. Other examples
include CALL and GOTO, which include a 20-bit
program memory address.
5.4.2DIRECT ADDRESSING
Direct Addressing specifies all or part of the source
and/or destination address of the operation within the
opcode itself. The options are specified by the
arguments accompanying the instruction.
In the core PIC18 inst ruct ion se t, bit-ori ented and by teoriented instructions use some version of Direct
Addressing by default. All of these instructions include
some 8-bit literal address as their Least Significant
Byte. This address spec ifies either a re gister address in
one of the banks of d ata RAM ( Section 5.3.3 “GeneralPurpose Register File”) or a location in the Access
Bank (Section 5.3.2 “Access Bank”) as the data
source for the instruction.
The Access RAM bit ‘a’ determines how the a ddre ss i s
interpreted. When ‘a’ is ‘1’, the contents of the BSR
(Section 5.3.1 “Bank Select Register (BSR)”) are
used with the address t o determin e the comple te 12-bit
address of the reg ister. When ‘a’ is ‘0’, the address is
interpreted as being a register in the Access Bank.
Addressing that uses the Access RAM is sometimes
also known as Direct Forced Addressing mode.
A few instructions, such as MOVFF, include the entire
12-bit address (either source or destination) in their
opcodes. In these cases, the BSR is ignored entirely.
The destination of the operati on’s results is determined
by the destination bit ‘d ’. Wh en ‘d’ is ‘1’, the results are
stored back in th e s o ur c e re g is ter, overw rit i n g i ts or i ginal contents. When ‘d’ is ‘0’, the results are stored in
the W register. Instructions without the ‘d’ argument
have a destin ation tha t is i mplicit in the inst ruction; their
destination is either the target register being operated
on or the W register.
5.4.3INDIRECT ADDRESSING
Indirect Addressin g allows the u ser to access a l ocation
in data memory without giving a fixed address in the
instruction. This is done by using File Select Registers
(FSRs) as pointers to the location s to be read or written
to. Since the FSRs are themselves located in RAM as
Specia l File Regi sters, the y can als o be di rectly mani pulated under program control. This makes FSRs very
useful in imp lem ent ing data str uct ures , s uch as tabl es
and arrays in data memory.
The registers for Indirect Addressing are also
implemented with Indirect File Operands (INDFs) that
permit automatic mani pulati on of the poi nter value with
auto-incrementing, auto-decrementing or offsetting
with another va lue . Th is al lo ws f or e fficient code, us ing
loops, such as the example of clearing an entire RAM
bank in Example5-5.
EXAMPLE 5-5:HOW TO CLEAR RAM
(BANK 1) USING
INDIRECT ADDRESSING
PIC18F8722 FAMILY
FSR1H:FSR1L
0
7
Data Memory
000h
100h
200h
300h
F00h
E00h
FFFh
Bank 0
Bank 1
Bank 2
Bank 14
Bank 15
Bank 3
through
Bank 13
ADDWF, INDF1, 1
07
Using an instruction with one of the
Indirect Addressing registers as the
operand....
...uses the 12-bit address stored in
the FSR pair associated with that
register....
...to determine the data memory
location to be used in that operation.
In this case, the FSR1 pair contains
ECCh. This means the contents of
location ECCh will be added to that
of the W register and stored back in
ECCh.
xxxx1110 11001100
5.4.3.1FSR Registers and the
INDF Operand
At the core of Indirect Addressing are three sets of
registers: FSR0, FSR1 and FSR2. Each represents a
pair of 8-bit registers, FSRnH and FSRnL. The four
upper bits of the FSRnH register are not used so each
FSR pair holds a 12-bi t va lue. T his repre sen ts a val ue
that can address the entire range of the data memory
in a linear fashion. The FSR register pairs, then, serve
as pointers to data memory locations.
Indirect Addressing is accomplished with a set of
Indirect File Operands, INDF0 through INDF2. These
can be thought of as “virtual” registers: they are
mapped in the SFR space but are not physically implemented. Reading or writin g to a particular INDF reg ister
actually accesses its corresponding FSR register pair.
A read from INDF1, for example, reads the data at the
address indi cated by FSR 1H:FSR1L. Instructi ons that
use the IND F registers a s operands actu ally use the
contents of th eir co rrespon ding FS R as a poin ter to th e
instruction’s target. The INDF operand is just a
convenient way of using the pointer.
Because Indirect Ad dressing uses a fu ll 12-bit addr ess,
data RAM banking is not necessary. Thus, the current
contents of the BSR and the Access RAM bit have no
effect on determining the target address.
5.4.3.2FSR Registers and POSTI NC,
POSTDEC, PREINC and PLUSW
In addition to the IND F operand, eac h FSR register pair
also has four additional indirect operands. Like INDF,
these are “virtual” registers that cannot be indirectly
read or written to. Accessing these registers actually
accesses the associated FSR register pair, but also
performs a specifi c action on it s stored v alue. They ar e:
• POSTDEC: accesses the FSR value, then
automatically decrements it by 1 afterwards
• POSTINC: accesses the FSR value, then
automatically increments it by 1 afterwards
• PREINC: increments the FSR value by 1, then
uses it in the operation
• PLUSW: adds the signed value of the W register
(range of -127 to 128) t o that of th e FSR and uses
the new value in the operation.
In this context, accessing an INDF register uses the
value in the FSR registers without changing them.
Similarly, accessing a PLUSW register gives the FSR
value offset by the valu e in the W register; neithe r value
is actually changed in the operation. Accessing the
other virtual registers changes the value of the FSR
registers.
Operations on the FSRs with POSTDEC, POSTINC
and PREINC affect the entire register pair; that is, rollovers of the FSRnL register from FFh to 00h ca rry over
to the FSRnH register. On the other hand, results of
these operations do not change the value of any flags
in the STATUS register (e.g., Z, N, OV, etc.).
The PLUSW register can be used to implement a form
of Indexed Addressing in the data memory space. By
manipulating the value in the W register, users can
reach addresses that are fixed offsets from pointer
addresses. In some applications, this can be used to
implement some powerful program control structure,
such as software stacks, inside of data memory.
5.4.3.3Operations by FSRs on FSRs
Indirect Addressing operations that target other FSRs
or virtual registers represent special cases. For example, using an FSR to point to on e of the virtual regis ters
will not result in successful operations. As a specific
case, assume that FSR0H:FSR0L contains FE7h, the
address of INDF1. Attempts to read the value of the
INDF1 using INDF0 as an operand will return 00h.
Attempts to write to INDF1 using I NDF0 as the operan d
will result in a NOP.
On the other ha nd, u sing the v irtual reg isters to w rite to
an FSR pair may n ot oc cur as plan ned. I n t hese cases ,
the value will be written to the FSR p air bu t withou t an y
incrementing or decrementing. Thus, writing to INDF2
or POSTDEC2 will write the same value to the
FSR2H:FSR2L.
Since the FSRs are physical registers mapped in the
SFR space, they can be manipulated through all direct
operations. Users should proceed cautiously when
working on these registers, particularly if their code
uses Indirect Addressing.
Similarly, operations by Indirect Addressing are generally permitted on all other SFRs. U sers shoul d exercise
the appropriate caution that they do not inadvertently
change settings that might affect the operation of the
device.
5.5Data Memory and the Extended
Instruction Set
Enabling the PIC18 extended instruction set (XINST
Configuration bit = 1) significantly changes certain
aspects of data memory and its addressing. Specifically, the use of the Access Bank for many of the core
PIC18 instructions is different; this is due to the
introduction of a new addressing mode for the data
memory space.
What does not change is just as im po rtant. The size of
the data memory space is unchanged, as well as its
linear addressing. The SFR map remains the same.
Core PIC18 instructions can still operate in both Direct
and Indirect Addressing mode; inherent and literal
instructions do not change at all. Indirect Addressing
with FSR0 and FSR1 also remain unchanged.
5.5.1INDEXED ADDRESSING WITH
LITERAL OFFSET
Enabling the PIC18 extended instruction set changes
the behavior of Indirect Addressing using the FSR2
register pair within Access RAM. Under the proper
conditions, instruc tions that us e the Access Ban k – that
is, most bit-oriented and byte-oriented instructions –
can invoke a form of Indexed Addressing using an
offset specified in the in structi on. Thi s spe cial a ddress ing mode is known as Indexed Addressing with Literal
Offset, or Indexed Literal Offset mode.
When using the extended instruction set, this
addressing mode requires the following:
• The use of the Access Ban k i s forced (‘a’ = 0) and
• The file address arg um ent is less than or e qua l to
5Fh.
Under these conditions, the file address of the instruction is not interpreted as the lower byte of an address
(used with the BSR in Direct Addres sing), or as an 8-bit
address in the Access Bank. Instead, the value is
interpreted as an offset value to an address pointer,
specified by FSR2. The offset and the contents of
FSR2 are added to obtain the target address of the
operation.
5.5.2INSTRUCTIONS AFFECTED BY
INDEXED LITERAL OFFSET MODE
Any of the core PIC18 instructions that can use Direct
Addressing are potentially affected by the Indexed
Literal Offset Addressing mode. This includes all
byte-oriented and bit-oriented instructions, or almost
one-half of the standard PIC18 instruction set.
Instructions that onl y use Inherent or Literal Addr essing
modes are unaffecte d.
Additionally, byte-oriented and bit-oriented instructions
are not affected if they do not use the Access Bank
(Access RAM bit is ‘1’), or include a fi le ad dres s of 60 h
or above. Instructions meeting these criteria will
continue to execute as be fore. A comp aris on of the di fferent possible addressing modes when the extended
instruction set is enabled in shown in Figure 5-9.
Those who desire to use byte-oriented or bit-oriented
instructions in the Indexed Literal Offset mode should
note the changes to assembler syntax for this mode.
This is described in more detail in Section 26.2.1“Extended Instruction Syntax”.
EXAMPLE INSTRUCTION: ADDWF, f, d, a (Opcode: 0010 01da ffff ffff)
When ‘a’ = 0 and f ≥ 60h:
The instruction executes in
Direct Forced mode. ‘f’ is interpreted as a location in the
Access RAM between 060h
and 0FFh. This is the sam e as
locations 060h to 07Fh
(Bank 0) and F80h to FFFh
(Bank 15) of data memory.
Locations below 60h are not
available in this addressing
mode.
When ‘a’ = 0 and f ≤ 5Fh:
The instruction executes in
Indexed Literal Offset mode. ‘f’
is interpreted as an offset to the
address value in FSR2. The
two are added together to
obtain the address of the target
register for the instruction. The
address can be anywhere in
the data memory space.
Note that in this mode, the
correct syntax is now:
ADDWF [k], d
where ‘k’ is the same as ‘f’.
When ‘a’ = 1 (all values of f):
The instruction executes in
Direct mode (also known as
Direct Long mode). ‘f’ is interpreted as a location in one of
the 16 banks of the data
memory space. The bank is
designated by the Bank Sel ect
Register (BSR). The address
can be in any implemented
bank in the data memory
space.
000h
060h
100h
F00h
F80h
FFFh
Valid range
00h
60h
80h
FFh
Data Memory
Access RAM
Bank 0
Bank 1
through
Bank 14
Bank 15
SFRs
000h
080h
100h
F00h
F80h
FFFh
Data Memory
Bank 0
Bank 1
through
Bank 14
Bank 15
SFRs
FSR2HFSR2L
ffffffff001001da
ffffffff001001da
000h
080h
100h
F00h
F80h
FFFh
Data Memory
Bank 0
Bank 1
through
Bank 14
Bank 15
SFRs
for ‘f’
BSR
00000000
080h
FIGURE 5-9:COMPARING ADDRESSING OPTIONS FOR BIT-ORIENTED AND
BYTE-ORIENTED INSTRUCTIONS (EXTENDED INSTRUCTION SET ENABLED)
Locations in the region
from the FSR2 Pointer
(120h) to the pointer plus
05Fh (17Fh) are mapped
to the bottom of the
Access RAM (000h-05Fh).
Locations in Bank 0 from
060h to 07Fh are mapped,
as usual, to the middle half
of the Access Bank.
Special File Registers at
F80h through FFFh are
mapped to 80h through
FFh, as usual.
Bank 0 addresses below
5Fh can still be addressed
by using the BSR.
Access Bank
00h
80h
FFh
7Fh
Bank 0
SFRs
Bank 1 “Window”
Bank 0
Bank 0
Window
Example Situation:
07Fh
120h
17Fh
5Fh
Bank 1
5.5.3MAPPING THE ACCESS BANK IN
INDEXED LITERAL OFFSET MODE
The use of Indexed Literal Offset Addressing mode
effectively chan ges how the first 96 locati ons of Access
RAM (00h to 5Fh) are m ap ped . R at her tha n c on taining
just the contents of the bottom half of Bank 0, this mode
maps the contents from Bank 0 and a user defined
“window” that can be located anywhere in the data
memory space. The value of FSR2 establishes the
lower boundary of the addresses mapped into the
window, while the upper boundary is defined by FSR2
plus 95 (5Fh). Addresses in the Access RAM above
Remapping of the Access Bank applies only to operations using the I ndexed Lite ral Offs et mode. Ope rations
that use the BSR (Access RAM bit is ‘1’) will continue
to use Direct Addressing as before.
5.6PIC18 Instruction Execution and
the Extended Instruction Set
Enabling the extended instruction set adds eight
additional commands to the existing PIC18 instruction
set. These instructions are executed as described in
Section 26.2 “Extended Instruction Set”.
5Fh are mapped as previously described (see
Section 5.3.2 “Access Ban k”). An example of Access
Bank remapping in this addressing mode is shown in
Figure 5-10.
FIGURE 5-10:REMAPPING THE ACCESS BANK WITH INDEXED LITERAL
Note 1:Table Pointer register points to a byte in program memory.
Program Memory
(TBLPTR)
6.0FLASH PROGRAM MEMORY
The Flash program memory is readable, writable and
erasable during normal operation over the entire V
range.
A read from program memory is executed on one byte
at a time. A write to program memory is executed on
blocks of 64 bytes at a time. Program memory is
erased in blocks of 64 bytes at a time. A bulk erase
operation may not be issued from user code.
Writing or erasing program memory will cease
instruction fetches until the operation is complete. The
program memory cannot be accessed during the write
or erase, therefore, code cannot execute. An internal
programming timer terminates program memory writes
and erases.
A value written to progra m memory does not nee d to be
a valid instruction. Executing a program memory
location that forms an invalid instruction results in a
NOP.
DD
6.1Table Reads and Table Writes
In order to read and write program memory, there are
two operations that allow the processor to move bytes
between the program memory sp ace and the dat a RAM:
• Table Read (TBLRD)
• Table Write (TBLWT)
The program memory space is 16 bits wide, while the
data RAM space is 8 bits wide. Table reads and table
writes move data between these two memory spaces
through an 8-bit register (TABLAT).
Table read operations retrieve data from program
memory and place it into the data RAM space.
Figure 6-1 shows the operation of a table read with
program memory and data RAM.
Table write opera tions s tor e data from t he da ta memo ry
space into holding registers in program memory. The
procedure to write the contents of the holding registers
into program memory is detailed in Section 6.5 “Writin gto Flash Program Memory”. Figure6-2 shows the
operation of a table write with program memory and data
RAM.
Table operations work with byte entities. A table block
containing data, rather than program instructions, is not
required to be word aligned. Therefore, a table block can
start and end at any byte address. If a t able write is being
used to write executable code into program memory,
program instructions will need to be word aligned.
Note1:Table Pointer actually points to one of 64 holding registers, the address of which is determined by
TBLPTRL<5:0>. The process for physically writing data to the program memor y array is discusse d in
Section 6.5 “Writing to Flash Program Memor y ”.
Holding Registers
Program Memory
FIGURE 6-2:TABLE WRITE OPERATION
6.2Control Registers
Several control registers are used in conjunction with
the TBLRD and TBLWT instructions. These include the:
• EECON1 register
• EECON2 register
• TABLAT register
• TBLPTR registers
6.2.1EECON1 AND EECON2 REGISTERS
The EECON1 register (Register 6-1) is the control
register for memory acce sses. The EECO N2 register is
not a physical register; it is used exclusively in the
memory write and erase sequences. Reading
EECON2 will read all ‘0’s.
The EEPGD control bit determines if th e access will be
a program or data EEPROM memory access. When
clear, any subsequent operations will operate on the
data EEPROM memory. When set, any subsequent
operations will operate on the program memory.
The CFGS control bit determines if the access will be
to the Configuration/C alib ration re giste rs or to pro gram
memory/data EEPROM memory. When set,
subsequent operations will operate on Configuration
registers regardless of EEPGD (see Section 25.0“Special Featur es of the CPU”). When clear , memor y
selection access is determined by EEPGD.
The FREE bit, when set, will allow a program memory
erase operation. When FREE is set, the erase
operation is initiated on the next WR command. When
FREE is clear , only wr ite s are enab led .
The WREN bit, when set, will allow a write operation.
On power-up, the WREN bit is c lear . The WRERR bit is
set in hardware when the WR bit is set and cleared
when the internal programming timer expires and the
write operation is complete.
Note:During normal operation, the WRERR is
read as ‘1’. This can indicate that a write
operation was prematurely terminated by
a Reset, or a write operation was
attempted improperly.
The WR control bit initiates write operations. The bit
cannot be cleared, only set, in software; it is cleared in
hardware at the completion of the write operation.
Note:The EEIF interrupt flag bit (PIR2<4>) is set
when the write is complete. It must be
cleared in software.
The Table Latch (TABLAT) is an 8-bit register mapped
into the SFR space. The Table Latch register is used to
hold 8-bit data during data transfers between program
memory and data RAM.
6.2.3TBLPTR – TABLE POINTER
REGISTER
The Table Poin ter (T BLPTR ) re gis ter add res se s a byte
within the program memory. The TBLPTR is comprised
of three SFR registers : Table Pointer Upper Byte, Table
Pointer High Byte and Table Pointer Low Byte
(TBLPTRU:TBLPTRH:TBLPTRL). These three registers join to form a 22-bit wide po inter. The low-o rder
21 bits allow the device to address up to 2 Mbytes of
program memory sp ace. Th e 22nd b it allow s acce ss to
the device ID, the user ID and the Configuration bits.
The Table Pointer register, TBLPTR, is used by the
TBLRD and TBLWT instructi ons . T hes e i ns truc tio ns ca n
update the TBLPTR in one of four ways based on the
table operation. These operations are shown in
T abl e 6-1. These op erations on the TBLPT R only af fect
the low-order 21 bits.
6.2.4TABLE POINTER BOUNDARIES
TBLPTR is used in reads, writes and erases of the
Flash program memory.
When a TBLRD is executed, al l 22 bits of th e T BLPT R
determine which byte is read from program memory
into TABL AT.
When a TBLWT is executed, the six LSbs of the Table
Pointer register (TBLPTR<5:0>) determine which of
the 64 program memory holding registers is written to.
When the timed write to program memory begins (via
the WR bit), the 16 MSbs of the TBLPTR
(TBLPTR<21:6>) determine which program memory
block of 64 bytes is written to. For more detail, see
Section 6.5 “Writing to Flash Program Memory”.
When an erase of program memory is executed, the
16 MSbs of the Table Pointer register (TBLPTR<21:6>)
point to the 64-byte block that will be erased. The Least
Significant bits (TBLPTR<5:0>) are ignored.
Figure 6-3 describes the relevant boundaries of
TBLPTR based on Flash program memory operations.
TABLE 6-1:TABLE POINTER OPERATIONS WITH TBLRD AND TBLWT INSTRUCTIONS
ExampleOperation on Table Pointer
TBLRD*
TBLWT*
TBLRD*+
TBLWT*+
TBLRD*TBLWT*-
TBLRD+*
TBLWT+*
TBLPTR is incremented after the read/write
TBLPTR is decremented after the read/write
TBLPTR is incremented before the read/write
TBLPTR is not modified
FIGURE 6-3:TABLE POINTER BOUNDARIES BASED ON OPERATION
MOVLWCODE_ADDR_UPPER; Load TBLPTR with the base
MOVWFTBLPTRU; address of the word
MOVLWCODE_ADDR_HIGH
MOVWFTBLPTRH
MOVLWCODE_ADDR_LOW
MOVWFTBLPTRL
READ_WORD
TBLRD*+; read into TABLAT and increment
MOVFTABLAT, W ; get data
MOVWFWORD_EVEN
TBLRD*+; read into TABLAT and increment
MOVFTABLAT, W ; get data
MOVFWORD_ODD
6.3Reading the Flash Program
Memory
The TBLRD instruction is used to retrieve data from
program memory and places it into data RAM. Table
reads from program memory are pe rformed one by te at
a time.
TBLPTR poi nts to a byte address in pro gram space.
Executing TBLRD places the byte pointed to into
TABLAT. In addition, TBLPTR can be modified
automatically for the next table read operation.
The internal program memory is typically organize d by
words. The Least Sig nificant b it of th e address selects
between the high and low bytes of the word. Figure 6-4
shows the interface between the internal program
memory and the TABLAT.
MOVLWCODE_ADDR_UPPER; load TBLPTR with the base
MOVWFTBLPTRU ; address of the memory block
MOVLWCODE_ADDR_HIGH
MOVWFTBLPTRH
MOVLWCODE_ADDR_LOW
MOVWFTBLPTRL
ERASE_ROW
BSF EECON1, EEPGD; point to Flash program memory
BCFEECON1, CFGS; access Flash program memory
BSFEECON1, WREN; enable write to memory
BSF EECON1, FREE; enable Row Erase operation
BCFINTCON, GIE; disable interrupts
The minimum eras e block is 32 wo rds or 64 b ytes. Only
through the use of an external programmer, or through
ICSP control, can larger blocks of program memory be
bulk erased. Word erase in the Flash array is not
supported.
When initiating an erase sequence from the microcontroller itself, a blo ck of 64 bytes of program memo ry
is erased. The Most Significant 16 bits of the
TBLPTR<21:6> point to the block being erased.
TBLPTR<5:0> are ignored.
The EECON1 register comma nds the erase operation.
The EEPGD bit must be set to point to the Flash
program memory. The WREN bit must be set to enable
write operations. The F REE bit is set to select an erase
operation.
For protection, the wri te i ni tiat e s equ enc e f or EECO N2
must be used.
A long write is nec essa ry for erasin g the i nternal Flash.
Instruction execution is halted while in a long write
6.4.1FLASH PROGRAM MEMORY
ERASE SEQUENCE
The sequence of events for erasing a block of internal
program memory location is:
1. Load Table Pointer register with address of row
being erased.
2.Set the EECON1 register for the erase operation:
• set EEPGD bit to point to program memory;
• clear the CFGS bit to access program memory;
• set WREN bit to enable writes;
• set FREE bit to enable the erase.
3. Disable interrupts.
4. Write 55h to EECON2.
5. Write 0AAh to EECON2.
6. Set the WR bit. This will begin the row erase
cycle.
7. The CPU will stall for duration of the erase for
TIW (see parameter D1 33 A).
8. Re-enable interrupts.
cycle. The long write will be terminated by the internal
programming timer.
The minimum programming block is 32 words or
64 bytes. Word or byte programming is not supported.
Table writes are used internally to load the holding
registers needed to program the Flash memory. There
are 64 holding registers used by the table writes for
programming.
Since the Table Latch (TABLAT) is only a single byte, the
TBLWT instruction may need to be executed 64 times for
each programming operation. All of the t able w rite ope rations will essentially be short writes because only the
holding registers are written. At the end of updating the
64 holding registers, the EECON1 register must be
written to in order to start the programming operation
with a long write.
The long write is necessary for programming the internal Flash. Instruc tion exe cution is halted wh ile in a long
write cycle. The long write will be terminated by the
internal programming timer.
The EEPROM on-chip timer controls the write time.
The write/erase voltages are generated by an on-chip
charge pump, rated to operate over the voltage range
of the device.
Note:The default value of the holding registers on
device Resets and aft er write op eratio ns is
FFh. A write of FFh to a holding register
does not modify that byte. T his mea ns th at
individual bytes of program memory may be
modified, provided that the change does not
attempt to change any bi t from a ‘0’ to a ‘1’.
When modifying individual bytes, it is not
necessary to load all 64 holding registers
before executing a write ope ration.
FIGURE 6-5:TABLE WRITES TO FLASH PROGRAM MEMORY
6.5.1FLASH PROGRAM MEMORY WRITE
SEQUENCE
The sequence of events for programming an internal
program memory location should be:
1.Read 64 bytes into RAM.
2. Update data values in RAM as necessary.
3. Load Table Pointer register with address being
erased.
4. Execute the row erase procedure.
5. Load Table Pointer register with address of first
byte being written.
6. Write the 64 bytes into the ho lding regis ters wi th
auto-increment.
7. Set the EECON1 register for the write operatio n:
10. Write 0AAh to EECON2.
1 1. Set the WR bit. This will begin the write cycl e.
12. The CPU will stall for duration of the write for T
(see parameter D133A).
13. Re-enable interrupts.
14. Verify the memory (table read).
An example of the required code is shown in
Example 6- 3 on the following page.
Note:Before setting the WR bit, the Table
Pointer address needs to be within the
intended address range of the 64 bytes in
the holding register.
IW
PIC18F8722 FAMILY
MOVLWD'64'; number of bytes in erase block
MOVWFCOUNTER
MOVLWBUFFER_ADDR_HIGH; point to buffer
MOVWFFSR0H
MOVLWBUFFER_ADDR_LOW
MOVWFFSR0L
MOVLWCODE_ADDR_UPPER; Load TBLPTR with the base
MOVWFTBLPTRU; address of the memory block
MOVLWCODE_ADDR_HIGH
MOVWFTBLPTRH
MOVLWCODE_ADDR_LOW
MOVWFTBLPTRL
READ_BLOCK
TBLRD*+; read into TABLAT, and inc
MOVFTABLAT, W ; get data
MOVWFPOSTINC0; store data
DECFSZ COUNTER ; done?
BRAREAD_BLOCK; repeat
MODIFY_WORD
MOVLWD ATA_ADDR_HIGH; point to buffer
MOVWFFSR0H
MOVLWDATA_ADDR_LOW
MOVWFFSR0L
MOVLWNEW_DATA_LOW; update buffer word
MOVWFPOSTINC0
MOVLWNEW_DATA_HIGH
MOVWFINDF0
ERASE_BLOCK
MOVLWCODE_ADDR_UPPER; load TBLPTR with the base
MOVWFTBLPTRU ; address of the memory block
MOVLWCODE_ADDR_HIGH
MOVWFTBLPTRH
MOVLWCODE_ADDR_LOW
MOVWFTBLPTRL
BSFEECON1, EEPGD; point to Flash program memory
BCFEECON1, CFGS; access Flash program memory
BSFEECON1, WREN; enable write to memory
BSFEECON1, FREE; enable Row Erase operation
BCFINTCON, GIE; disable interrupts
MOVLW55h
BSFEECON1, EEPGD ; point to Flash program memory
BCFEECON1, CFGS; access Flash program memory
BSFEECON1, WREN; enable write to memory
BCFINTCON, GIE; disable interrupts
MOVLW55h
RequiredMOVWFEECON2; write 55h
SequenceMOVLW0AAh
MOVWFEECON2 ; write 0AAh
BSFEECON1, WR; start program (CPU stall)
BSFINTCON, GIE; re-enable interrupts
BCFEECON1, WREN; disable write to memory
EXAMPLE 6-3:WRITING TO FLASH PROGRAM MEMORY (CONTINUED)
6.5.2WRITE VERIFY
Depending on the application, good programming
practice may dictate that the value written to the
memory should be verified against the original value.
This should be used in applications where excessive
writes can stress bits near the specification limit.
6.5.3UNEXPECTED TERMINATION OF
WRITE OPERATION
If a write is termin ate d b y a n u npl anned event, such as
loss of power or an unexpected Reset, the memory
location just pr ogrammed shou ld be verifi ed and repr ogrammed if needed. If the wr ite operatio n is interrupte d
by a MCLR
normal operation, the user can check the WRERR bit
and rewrite the location(s) as needed.
Reset or a WDT Time-out Reset during
TABLE 6-2:REGISTERS ASSOCIATED WITH PROGRAM FLASH MEMORY
NameBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
TBLPTRU
TBPLTRH Program Memory Table Pointer High Byte (TBLPTR<15:8>)57
TBLPTRL Program Memory Table Pointer Low Byte (TBLPTR<7:0>)57
TABLATProgram Memory Table Latch57
INTCONGIE/GIEH PEIE/GIEL TMR0IEINT0IERBIETMR0IFINT0IFRBIF57
EECON2EEPROM Control Register 2 (not a physical register)59
EECON1EEPGDCFGS
IPR2
PIR2
PIE2
Legend: — = unimplemented, read as ‘0’. Shaded cells are not used during Flash/EEPROM access.
Note 1: Bit 21 of TBLPTRU allows access to the device Configuration bits.
To protect against spurious writes to Flash program
memory, the write initiate sequence must also be
followed. See Section 25.0 “Special Features of the
CPU” for more detail.
6.6Flash Program Operation During
Code Protection
See Section 25.5 “Program Verification and Code
Protection” for details on code protection of Flash
program memory.
Reset
Values on
page
(1)
Program Memory T able Pointer Upper Byte (TBLPTR<20:16>)57
mented on PIC18F6527/6622/6627/6722
(64-pin) devices.
The External Memory Bus (EMB) allows the device to
access external memory devices (such as Flash,
EPROM, SRAM , etc.) as pro gram or data mem ory. It
supports both 8-bit and 16-bit Data Width modes and
four address widths from 8 to 20 bits.
The bus is implemented with 28 pins, multiplexed
across four I/O ports. Three ports (PORTD, PORTE
and PORTH) are m ultiplexed with th e address/dat a bus
for a total of 20 available lines, while PORTJ is
multiplexed with the bus cont rol sig nal s.
A list of the pins and their functions is provided in
Table 7-1.
T ABLE 7-1:PIC18F8527/8622/8627/8722 EXTERNAL BUS – I/O PORT FUNCTIONS
NamePortBitExternal Memory Bus Function
RD0/AD0PORTD0Address bit 0 or Data bit 0
RD1/AD1PORTD1Address bit 1 or Data bit 1
RD2/AD2PORTD2Address bit 2 or Data bit 2
RD3/AD3PORTD3Address bit 3 or Data bit 3
RD4/AD4PORTD4Address bit 4 or Data bit 4
RD5/AD5PORTD5Address bit 5 or Data bit 5
RD6/AD6PORTD6Address bit 6 or Data bit 6
RD7/AD7PORTD7Address bit 7 or Data bit 7
RE0/AD8PORTE0Address bit 8 or Data bit 8
RE1/AD9PORTE1Address bit 9 or Data bit 9
RE2/AD10PORTE2Address bit 10 or Data b it 10
RE3/AD11PORTE3Address bit 11 or Data bit 11
RE4/AD12PORTE4Address bit 12 or Data b it 12
RE5/AD13PORTE5Address bit 13 or Data b it 13
RE6/AD14PORTE6Address bit 14 or Data b it 14
RE7/AD15PORTE7Address bit 15 or Data b it 15
RH0/A16PORTH0Address bi t 16
RH1/A17PORTH1Address bi t 17
RH2/A18PORTH2Address bi t 18
RH3/A19PORTH3Address bi t 19
RJ0/ALEPORTJ0Address Latch Enable (ALE) Control pin
RJ1/OE
RJ2/WRL
RJ3/WRH
RJ4/BA0POR TJ4Byte Address bit 0 (BA0)
RJ5/CE
RJ6/LB
RJ7/UB
Note:For the sake of clarity, only I/O port and external bus assign ment s a re show n he re. One or more additi onal
multiplexed features may be available on some pins.
PORTJ1Output Enable (OE) Control pin
PORTJ2Write Low (WRL) Control pin
PORTJ3Write High (WRH) Control pin
PORTJ5Chip Enable (CE) Control pin
PORTJ6Lower Byte Enable (LB) Control pin
PORTJ7Upper Byte Enable (UB) Control pin
The operation of the interface is controlled by the
MEMCON register (Register 7-1). This register is
available in all program memory operating modes
except Microcontrol le r mode. In this mode, the reg is ter
is disabled and cannot be written to.
The EBDIS bit (MEMCON<7>) controls the operation
of the bus and related port functions. Clearing EBDIS
enables the interface and disables the I/O functions of
the ports, as well as any other functions multiplexed to
those pins. Setting the bit enables the I/O ports and
other functions but allows the interface to override
everything else on the pins when an external memory
operation i s required. By def ault, the external bus is
always enabled and disables all other I/O.
The operation of the EBDIS bit is also influenc ed by the
program memory mode being used. This is discussed
in more detail in Section 7.4 “Program MemoryModes and the External Memory Bus”.
The WAIT bits allow for the addition of wait states to
external memory operations. The use of these bits is
discussed in Section 7.3 “Wait States”.
The WM bits select th e p artic ular ope rating m ode use d
when the bu s is o peratin g in 16 -bit D ata Width mode.
These are discussed in more detail in Section 7.5“16-Bit Data Width Modes”. Thes e bits have no ef fect
when an 8-bit Data Width mode is selected.
WM<1:0>:TBLWT Operation with 16-Bit Data Bus
Width Select bits
1x = Word Write mode: TABLA T0 and TABLAT1 word
output, WRH
01 = Byte Select mode: TABLAT data copied on both
MSB and LSB; WRH and (UB or LB) will activate
active when TABLAT1 written
REGISTER 7-1:MEMCON: EXTERNAL MEMORY BUS CONTROL REGISTER
R/W-0U-0R/W-0R/W-0U-0U-0R/W-0R/W-0
EBDIS—WAIT1WAIT0——WM1WM0
bit 7bit 0
Legend:
R = Readable bitW = Writable bitU = Unimplemented bit, read as ‘0’
-n = Value at POR‘1’ = Bit is set‘0’ = Bit is clearedx = Bit is unknown
bit 7EBDIS: External Bus Disable bit
1 = External bus enabled when microcontroller accesses external memory;
otherwise, all external bus drivers are mapped as I/O ports
0 = External bus always enabled, I/O ports are disabled
bit 6Unimplemented: Read as ‘0’
bit 5-4WAIT<1:0>: Table Reads and Writes Bus Cycle Wait Count bits
11 = Table reads and writes will wait 0 T
10 = Table reads and writes will wait 1 TCY
01 = Table reads and writes will wait 2 TCY
00 = Table reads and writes will wait 3 TCY
bit 3-2Unimplemented: Read as ‘0’
bit 1-0WM<1:0>: TBLWT Operation with 16-Bit Data Bus Width Select bits