12.0 Special Features of the CPU............................................................................................................................. 119
13.0 Instruction Set Summary................................................................................................................................... 135
14.0 Deve lo pme nt Supp ort........................... ...... ..... ...... .................................. ..... ...... .............................................. 143
Index .......................................................................................................................................................................... 199
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 r egarding t his publication, p lease c ontact the M arket ing Communications Department via
E-mail at docerrors@mail.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)
• The Microchip Corporate Literature Center; U.S. FAX: (480) 792-7277
When contacting a sales office or the literature center, please specify which device, revision of silicon and data sheet (include liter-
ature number) you are using.
Customer Notification System
Register on our web site at www.microchip.com/cn to receive the most current information on all of our products.
DS30292D-page 4 1998-2013 Microchip Technology Inc.
This document contains device specific information.
Additional information may be found in the PIC
Mid-Range Reference Manual (DS33023), which may
be obtained from your local Microchip Sales Representative or downloaded from the Microchip website. The
Reference Manual should be considered a complementary document to this data sheet, and is highly recommended reading for a better understanding of the device
architecture and operation of the peripheral modules.
FIGURE 1-1:PIC16F873 AND PIC16F876 BLOCK DIAGRAM
®
MCU
There are four devices (PIC16F873, PIC16F874,
PIC16F876 and PIC16F877) covered by this data
sheet. The PIC16F876/873 devices come in 28-pin
packages and the PIC16F877/874 devices come in
40-pin packages. The Parallel Slave Port is not
implemented on the 28-pin devic es .
The following device bloc k diagrams are s orted by pin
number; 28-pin for Figure 1-1 and 40-pin for Figure 1-2.
The 28-pin and 40-pin pin outs are listed in Table 1-1
and Table 1-2, respectively.
OSC2/CLKOUT1010O—Oscillator crystal output. Connects to crystal or resonator in
crystal oscillator mode. In RC mode, the OSC2 pin outputs
CLKOUT which has 1/4 the frequency of OSC1, and denotes
the instruction cycle rate.
/VPP11I/PSTMaster Clear (Reset) input or programming voltage input. This
MCLR
pin is an active low RESET to the device.
PORTA is a bi-directional I/O port.
RA0/AN022I/OTTLRA0 can also be analog input0.
RA1/AN133I/OTTLRA1 can also be analog input1.
RA2/AN2/V
REF-44I/OTTLRA2 can also be analog input2 or negative analog
reference voltage.
RA3/AN3/V
REF+55I/OTTLRA3 can also be analog input3 or positive analog
reference voltage.
RA4/T0CKI66I/OSTRA4 can also be the clock input to the Timer0
module. Output is open drain type.
/AN477I/OTTLRA5 can also be analog input4 or the slave select
RA5/SS
for the synchronous serial port.
PORTB is a bi-directional I/O port. PORTB can be software
programmed for internal weak pull-up on all inputs.
RB0/INT2121I/OTTL/ST
(1)
RB0 can also be the external interrupt pin.
RB12222I/OTTL
RB22323I/OTTL
RB3/PGM2424I/OTTLRB3 can also be the low voltage programming input.
RB42525I/OTTLInterrupt-on-change pin.
RB52626I/OTTLInterrupt-on-change pin.
RB6/PGC2727I/OTTL/ST
(2)
Interrupt-on-change pin or In-Circuit Debugger pin. Serial
programming clock.
RB7/PGD2828I/OTTL/ST
(2)
Interrupt-on-change pin or In-Circuit Debugger pin. Serial
programming data.
PORTC is a bi-directional I/O port.
RC0/T1OSO/T1CKI1111I/OSTRC0 can also be the Timer1 oscillator output or Timer1
clock input.
RC1/T1OSI/CCP21212I/OSTRC1 can also be the Timer1 oscillator input or Capture2
input/Compare2 output/PWM2 output.
RC2/CCP11313I/OSTRC2 can also be the Capture1 input/Compare1 output/
PWM1 output.
RC3/SCK/SCL1414I/OSTRC3 can also be the synchronous serial clock input/output
for both SPI and I
RC4/SDI/SDA1515I/OSTRC4 can also be the SPI Data In (SPI mode) or
data I/O (I
2
C mode).
2
C modes.
RC5/SDO1616I/OSTRC5 can also be the SPI Data Out (SPI mode).
RC6/TX/CK1717I/OSTRC6 can also be the USART Asynchronous Transmit or
Synchronous Clock.
RC7/RX/DT1818I/OSTRC7 can also be the USART Asynchronous Receive or
Synchronous Data.
SS8, 198, 19P—Ground reference for logic and I/O pins.
V
DD2020P—Positive supply for logic and I/O pins.
V
Legend: I = inputO = outputI/O = input/outputP = power
Note 1: This buffer is a Schmitt Trigger input when configured as the external interrupt.
2: This buffer is a Schmitt Trigger input when used in Serial Programming mode.
3: This buffer is a Schmitt Trigger input when configured in RC oscillator mode and a CMOS input otherwise.
TABLE 1-2:PIC16F874 AND PIC16F877 PINOUT DESCRIPTION
DIP
Pin Name
OSC1/CLKIN131430IST/CMOS
OSC2/CLKOUT141531O—Oscillator crystal output. Connects to crystal or resonator
/VPP1218I/PSTMaster Clear (Reset) input or programming voltage input.
MCLR
RA0/AN02319I/OTTLRA0 can also be analog input0.
RA1/AN13420I/OTTLRA1 can also be analog input1.
RA2/AN2/V
RA3/AN3/V
RA4/T0CKI6723I/OSTRA4 can also be the clock input to the Timer0 timer/
RA5/SS/
RB0/INT33368I/OTTL/ST
RB134379I/OTTL
RB2353810I /OTTL
RB3/PGM363911I/OTTLRB3 can also be the low voltage programming input.
RB4374114I/OTTLInterrupt-on-change pin.
RB5384215I/OTTLInterrupt-on-change pin.
RB6/PGC394316I/OTTL/ST
RB7/PGD404417I/OTTL/ST
Legend: I = inputO = outputI/O = input/outputP = power
Note 1: This buffer is a Schmitt Trigger input when configured as an external interrupt.
REF-4521I/OTTLRA2 can also be analog input2 or negative
REF+5622I/OTTLRA3 can also be analog input3 or positive
AN47824I/OTTLRA5 can also be analog input4 or the slave select for
2: This buffer is a Schmitt Trigger input when used in Serial Programming mode.
3: This buffer is a Schmitt Trigger input when configured as general purpose I/O and a TTL input when used in the Parallel
Slave Port mode (for interfacing to a microprocessor bus).
4: This buffer is a Schmitt Trigger input when configured in RC oscillator mode and a CMOS input otherwise.
Note 1: This buffer is a Schmitt Trigger input when configured as an external interrupt.
2: This buffer is a Schmitt Trigger input when used in Serial Programming mode.
3: This buffer is a Schmitt Trigger input when configured as general purpose I/O and a TTL input when used in the Parallel
Slave Port mode (for interfacing to a microprocessor bus).
4: This buffer is a Schmitt Trigger input when configured in RC oscillator mode and a CMOS input otherwise.
QFP
Pin#
33,34
I/O/P
Type
Buffer
Type
Description
PORTC is a bi-directional I/O port.
Timer1 clock input.
Capture2 input/Compare2 output/PWM2 output.
output/PWM1 output.
2
output for both SPI and I
2
data I/O (I
C mode).
C modes.
or Synchronous Clock.
or Synchronous Data.
PORTD is a bi-directional I/O port or parallel slave port
when interfacing to a microprocessor bus.
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
PORTE is a bi-directional I/O port.
(3)
RE0 can also be read control for the parallel slave
port, or analog input5.
(3)
RE1 can also be write control for the parallel slave
port, or analog input6.
(3)
RE2 can also be select control for the parallel slave
port, or analog input7.
—These pins are not internally connected. These pins
DS30292D-page 10 1998-2013 Microchip Technology Inc.
PIC16F87X
PC<12:0>
13
0000h
0004h
0005h
Stack Level 1
Stack Level 8
RESET Vector
Interrupt Vector
On-Chip
CALL, RETURN
RETFIE, RETLW
1FFFh
Stack Level 2
Program
Memory
Page 0
Page 1
Page 2
Page 3
07FFh
0800h
0FFFh
1000h
17FFh
1800h
PC<12:0>
13
0000h
0004h
0005h
Stack Level 1
Stack Level 8
RESET Vector
Interrupt Vector
On-Chip
CALL, RETURN
RETFIE, RETLW
1FFFh
Stack Level 2
Program
Memory
Page 0
Page 1
07FFh
0800h
0FFFh
1000h
2.0MEMORY ORGANIZATION
There are three memory blocks in each of the
PIC16F87X MCUs. The Program Memory and Data
Memory have separate buses so that concurrent
access can oc cur and is detailed in this section. The
EEPROM data memory bl ock is detailed in Se ction 4.0.
Additional informa tion on devi ce memory may be found
in the PIC
(DS33023).
FIGURE 2-1:PIC16F877/876 PROGRAM
®
MCU Mid-Range Reference Manual,
MEMORY MAP AND
STACK
2.1Program Memory Organization
The PIC16F87X devic es have a 13-b it program count er
capable of addressing an 8K x 14 program memory
space. The PIC16F877/876 devices have 8K x 14
words of FLASH program memory, and the
PIC16F873/874 devices have 4K x 14. Accessing a
location above the ph ysicall y implem ented addres s will
cause a wraparound.
The RESET vector is at 0000h and the interrupt vector
is at 0004h.
The data memory is partitioned into multiple banks
which contain the General Purpose Registers and the
Special Function Registers. Bits RP1 (STATUS<6>)
and RP0 (STATUS<5>) are the bank select bits.
RP1:RP0Bank
000
011
102
113
Each bank extends up to 7Fh (128 bytes). The lower
locations of each bank are reserved for the Special
Function Registers. Above the Special Function Registers are Gener al Purpose Registers, implemented as
static RAM. All implemented banks contain Special
Function Registers. Some frequently used Special
Function Registers from one bank may be mirrored in
another bank for code reduction and quicker access.
Note:EEPROM Data Memory de scription can b e
found in Section 4.0 of this data sheet.
2.2.1GENERAL PURPOSE REGISTER
FILE
The register file can be acces sed either directly, or indirectly through the File Select Register (FSR).
DS30292D-page 12 1998-2013 Microchip Technology Inc.
Note 1: These registers are not implemented on the PIC16F873.
2: These registers are reserved, maintain these registers clear.
120h
1A0h
File
Address
File
Address
File
Address
File
Address
FIGURE 2-4:PIC16F874/873 REGISTER FILE MAP
DS30292D-page 14 1998-2013 Microchip Technology Inc.
PIC16F87X
2.2.2SPECIAL FUNCTION REGISTERS
The Special Function Registers are registers used by
the CPU and peripheral modules for controlling the
desired operation of the device. These registers are
implemented as static RAM. A list of these registers is
given in Table 2-1.
The Special Function Registers can be classified into
two sets: core (CPU) and peripheral. Those registers
associated with the core functions are described in
detail in this section. Those related to the operation of
the peripheral features are described in detail in the
peripheral features section.
00h
01hTMR0Timer0 Module Registerxxxx xxxx47
02h
03h
04h
05hPORTA
06hPORTBPORTB Data Latch when written: PORTB pins when readxxxx xxxx31
07hPORTCPORTC Data Latch when written: PORTC pins when readxxxx xxxx33
08h
09h
0Ah
0Bh
0ChPIR1PSPIF
0DhPIR2
0EhTMR1LHolding register for the Least Significant Byte of the 16-bit TMR1 Registerxxxx xxxx52
0FhTMR1HHolding register for the Most Significant Byte of the 16-bit TMR1 Registerxxxx xxxx52
10hT1CON
11hTMR2Timer2 Module Register0000 000055
12hT2CON
13hSSPBUFSynchronous Serial Port Rece i ve Buffer/Transmit Regi ste rxxxx xxxx 70, 73
14hSSPCONWCOLSSPOVSSPENCKPSSPM3SSPM2SSPM1SSPM00000 000067
15hCCPR1LCapture/Compare/PWM Register1 (LSB)xxxx xxxx57
16hCCPR1HCapture/Compare/PWM Register1 (MSB)xxxx xxxx57
17hCCP1CON
18hRCSTASPENRX9SRENCRENADDENFERROERRRX9D0000 000x96
19hTXREGUSART Transmit Data Register0000 000099
1AhRCREGUSART Receive Data Register0000 0000101
1BhCCPR2LCapture/Compare/PWM Register2 (LSB)xxxx xxxx57
1ChCCPR2HCapture/Compare/PWM Register2 (MSB)xxxx xxxx57
1DhCCP2CON
1EhADRESHA/D Result Register High Bytexxxx xxxx116
1FhADCON0ADCS1ADCS0CHS2CHS1CHS0GO/DONE
Legend:x = unknown, u = unchanged, q = value depends on condition, - = unimplemented, read as '0', r = reserved.
Note 1: The upper byte of the program counter is not directly accessible. PCLATH is a holding register for the PC<12:8> whose
INDFAddressing this location uses contents of FSR to address data memory (not a physical register)0000 000027
(3)
PCLProgram Counter (PC) Least Significant Byte0000 000026
(3)
STATUSIRPRP1RP0TOPDZDCC0001 1xxx18
(3)
FSRIndirect Data Memory Address Pointerxxxx xxxx27
——PORTA Data Latch when written: PORTA pins when read--0x 000029
(4)
PORTDPORTD Data Latch when written: PORTD pins when readxxxx xxxx35
(4)
PORTE—————RE2RE1RE0---- -xxx36
(1,3)
PCLATH———Write Buffer for the upper 5 bits of the Program Counter---0 000026
(3)
INTCONGIE PEIET0IEINTERBIET0IFINTFRBIF0000 000x20
Shaded locations are unimplemented, read as ‘0’.
contents are transferred to the upper byte of the program counter.
2: Bits PSPIE and PSPIF are reserved on PIC16F873/876 devices; always maintain these bits clear .
3: These registers can be addressed from any bank.
4: PORTD, PORTE, TRISD, and TRISE are not physically implemented on PIC16F873/876 devices; read as ‘0’.
5: PIR2<6> and PIE2<6> are reserved on these devices; always maintain these bits clear.
80h
81hOPTION_REGRBPU
82h
83h
84h
85hTRISA
86hTRISBPORTB Data Direction Register1111 111131
87hTRISCPORTC Data Direction Register1111 111133
88h
89h
8Ah
8Bh
8ChPIE1PSPIE
8DhPIE2
8EhPCON
8Fh—Unimplemented——
90h—Unimplemented——
91hSSPCON2GCENACKSTATACKDTACKENRCENPENRSENSEN0000 000068
92hPR2Timer2 Period Register1111 111155
93hSSPADDSy nchr on ous Se ri a l Port (I
94hSSPSTATSMPCKED/A
95h—Unimplemented——
96h—Unimplemented——
97h—Unimplemented——
98hTXSTACSRCTX9TXENSYNC
99hSPBRGBaud Rate Generator Register0000 000097
9Ah—Unimplemented——
9Bh—Unimplemented——
9Ch—Unimplemented——
9Dh—Unimplemented——
9EhADRESLA/D Result Register Low Bytexxxx xxxx116
9FhADCON1ADFM
Legend:x = unknown, u = unchanged, q = value depends on condition, - = unimplemented, read as '0', r = reserved.
Note 1: The upper byte of the program counter is not directly accessible. PCLATH is a holding register for the PC<12:8> whose
INDFAddressing this location uses contents of FSR to address data memory (not a physical register)0000 000027
(3)
PCLProgram Counter (PC) Least Significant Byte0000 000026
(3)
STATUSIRPRP1RP0TOPDZDCC0001 1xxx18
(3)
FSRIndirect Data Memory Address Pointerxxxx xxxx27
(4)
TRISDPORTD Data Direction Register1111 111135
(4)
TRISEIBFOBFIBOVPSPMODE—PORTE Data Direction Bits0000 -11137
(1,3)
PCLATH———Write Buffer for the upper 5 bits of the Program Counter---0 000026
(3)
INTCONGIEPEIET0IEINTERBIET0IFINTFRBIF0000 000x20
Shaded locations are unimplemented, read as ‘0’.
contents are transferred to the upper byte of the program counter.
2: Bits PSPIE and PSPIF are reserved on PIC16F873/876 devices; always maintain these bits clear .
3: These registers can be addressed from any bank.
4: PORTD, PORTE, TRISD, and TRISE are not physically implemented on PIC16F873/876 devices; read as ‘0’.
5: PIR2<6> and PIE2<6> are reserved on these devices; always maintain these bits clear.
100h
101hTMR0Timer0 Module Registerxxxx xxxx47
102h
103h
104h
105h—Unimplemented——
106hPORTBPORTB Data Latch when written: PORTB pins when readxxxx xxxx31
107h—Unimplemented——
108h—Unimplemented——
109h—Unimplemented——
10Ah
10Bh
10ChEEDATAEEPROM Da ta Register Low Bytexxxx xxxx41
10DhEEADREEPROM Address Register Low Bytexxxx xxxx41
10EhEEDATH
10FhEEADRH
Bank 3
180h
181hOPTION_REGRBPUINTEDGT0CST0SEPSAPS2PS1PS01111 111119
182h
183h
184h
185h—Unimplemented——
186hTRISBPORTB Data Direction Register1111 111131
187h—Unimplemented——
188h—Unimplemented——
189h—Unimplemented——
18Ah
18Bh
18ChEECON1EEPGD
18DhEECON2EEPROM Control Register2 (not a physical register)---- ----41
18Eh—Reserved maintain clear0000 0000—
18Fh—Reserved maintain clear0000 0000—
Legend:x = unknown, u = unchanged, q = value depends on condition, - = unimplemented, read as '0', r = reserved.
Note 1: The upper byte of the program counter is not directly accessible. PCLATH is a holding register for the PC<12:8> whose
INDFAddressing this location uses contents of FSR to address data memory (not a physical register)0000 000027
(3)
PCLProgram Counter's (PC) Least Significant Byte0000 000026
(3)
STATUSIRPRP1RP0TOPDZDCC0001 1xxx18
(3)
FSRIndirect Data Memory Address Pointerxxxx xxxx27
(1,3)
PCLATH———Write Buffer for the upper 5 bits of the Program Counter---0 000026
(3)
INTCONGIE PEIET0IEINTERBIET0IFINTFRBIF0000 000x20
——EEPROM Data Register High Bytexxxx xxxx41
———EEPROM Address Register High Bytexxxx xxxx41
(3)
INDFAddressing this location uses contents of FSR to address data memory (not a physical register)0000 000027
(3)
PCLProgram Counter (PC) Least Significant Byte0000 000026
(3)
STATUSIRPRP1RP0TOPDZDCC0001 1xxx18
(3)
FSRIndirect Data Memory Address Pointerxxxx xxxx27
(1,3)
PCLATH———Write Buffer for the upper 5 bits of the Program Counter---0 000026
(3)
INTCONGIEPEIET0IEINTERBIET0IFINTFRBIF0000 000x20
———WRERRWRENWRRDx--- x000 41, 42
Shaded locations are unimplemented, read as ‘0’.
contents are transferred to the upper byte of the program counter.
2: Bits PSPIE and PSPIF are reserved on PIC16F873/876 devices; always maintain these bits clear .
3: These registers can be addressed from any bank.
4: PORTD, PORTE, TRISD, and TRISE are not physically implemented on PIC16F873/876 devices; read as ‘0’.
5: PIR2<6> and PIE2<6> are reserved on these devices; always maintain these bits clear.
The STATUS register contains the arithmetic status of
the ALU, the RESET statu s and the b ank sele ct bit s for
data memory.
The STATUS register can be the destination for any
instruction, as with any other register. If the STATUS
register is the destination for an instruction that affects
the Z, DC or C bits, then the write to these three bits is
disabled. These bit s are set or cleared ac cording to the
device logic. Furthermore, the TO
writable, therefore, the result of an instruction with the
STATUS register as des tination ma y be different than
intended.
and PD bits are not
For example, CLRF STATUS will clear the upper three
bits and set t he Z bit. T his leaves the STATUS register
as 000u u1uu (where u = unchanged).
It is recommended, therefore, that only BCF, BSF,SWAPF and MOVWF instructions are used to alter the
STATUS register, because these instructions do not
affect the Z, C or D C bits from the ST ATUS register. For
other instructions not affecting any status bits, see the
“Instruction Set Summary."
Note:The C and DC bits operate as a borrow
and digit borrow bit, respectively, in subtraction. See the SUBLW and SUBWF
instructions for examples.
bit 7IRP: Register Bank Select bit (used for indirect addressing)
1 = Bank 2, 3 (100h - 1FFh)
0 = Bank 0, 1 (00h - FFh)
bit 6-5RP1:RP0: Register Bank Select bits (used for direct addressing)
11 = Bank 3 (180h - 1FFh)
10 = Bank 2 (100h - 17Fh)
01 = Bank 1 (80h - FFh)
00 = Bank 0 (00h - 7Fh)
Each bank is 128 bytes
bit 4TO
bit 3PD
bit 2Z: Zero bit
bit 1DC: Digit carry/borrow
bit 0C: Carry/borrow
: Time-out bit
1 = After power-up, CLRWDT instruction, or SLEEP instruction
0 = A WDT time-out occurred
: Power-down bit
1 = After power-up or by the CLRWDT instruction
0 = By execution of the SLEEP instruction
1 = The result of an arithmetic or logic operation is zero
0 = The result of an arithmetic or logic operation is not zero
bit (ADDWF, ADDLW,SUBLW,SUBWF instructions)
(for borrow
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
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:For borrow
, the polarity is reversed)
bit (ADDWF, ADDLW,SUBLW,SUBWF instructions)
, the polarity is reversed. A subtraction is executed by adding the two’s
complement of the second operand. For rotate (RRF, RLF) instructions, this bit is
loaded with either the high, or low order bit of the source register.
PDZDCC
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
DS30292D-page 18 1998-2013 Microchip Technology Inc.
The OPTION_REG Re gister is a re adable and w rit able
register , which cont ains various contr ol bits to conf igure
the TMR0 prescaler/WDT postscaler (single assignable register k nown als o as th e presca ler), t he Externa l
INT Interrupt, TMR0 and the w eak pull-up s on PORTB.
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
in the TRISB register m ust be cleared to disa ble th e pull -up on R B3 and ensu re the p rope r operation of th e device
PIC16F87X
2.2.2.3INTCON Register
The INTCON Register is a readabl e and writ able register, which contains various enable and flag bits for the
TMR0 register overflow, RB Port change and External
RB0/INT pin interrupts.
Note:Interrupt flag bits are set when an in terrupt
condition occurs, re gardless of the st a te of
its corresponding enable bit or the global
enable bit, GIE (INTCON<7>). User software should ensure the appropriate interrupt flag bits are clear prior to enabling an
interrupt.
The PIR1 register contains the individual flag bits for
the periph eral interrupts.
REGISTER 2-5:PIR1 REGISTER (ADDRESS 0Ch)
R/W-0R/W-0R-0R-0R/W-0R/W-0R/W-0R/W-0
(1)
PSPIF
bit 7bit 0
bit 7PSPIF
bit 6ADIF: A/D Converter Interrupt Flag bit
bit 5RCIF: USART Receive Interrupt Flag bit
bit 4TXIF: USART Transmit Interrupt Flag bit
bit 3SSPIF: Synchronous Serial Port (SSP) Interrupt Flag
bit 2CCP1IF: CCP1 Interrupt Flag bit
bit 1TMR2IF: TMR2 to PR2 Match Interrupt Flag bit
bit 0TMR1IF: TMR1 Overflow Interrupt Flag bit
(1)
1 = A read or a write operation has taken place (must be cleared in software)
0 = No read or write has occurred
1 = An A/D conversion completed
0 = The A/D conversion is not complete
1 = The USART receive buffer is full
0 = The USART receive buffer is empty
1 = The USART transmit buffer is empty
0 = The USART transmit buffer is full
1 = The SSP interrupt condition has occurred, and must be cleared in software b efore returning
from the Interrupt Service Routine. The conditions that will set this bit are:
• SPI
• I
2
•I
0 = No SSP interrupt condition has occurred.
Capture mode:
1 = A TMR1 register capture occurred (must be cleared in software)
0 = No TMR1 register capture occurred
Compare mode:
1 = A TMR1 register compare match occ urred (must be cleared in software)
0 = No TMR1 register compare match occurred
PWM mode:
Unused in this mode
1 = TMR2 to PR2 match occurred (must be cleared in software)
0 = No TMR2 to PR2 match occurred
1 = TMR1 register overflowed (must be cleared in software)
0 = TMR1 register did not overflow
Note 1: PSPIF is reserved on PIC16F873/876 devices; always maintain this bit clear.
ADIFRCIFTXIFSSPIFCCP1IFTMR2IFTMR1IF
: Parallel Slave Port Read/Write Interrupt Flag bit
- A transmission/reception has taken place.
2
C Slave
- A transmission/reception has taken place.
C Master
- A transmission/reception has taken place.
- The initiated START condition was completed by the SSP module.
- The initiated STOP condition was completed by the SSP module.
- The initiated Restart condition was completed by the SSP module.
- The initiated Acknowledge condition was completed by the SSP module.
- A START condition occ urred whil e the SSP module was idle (Mul ti-Master sy stem).
- A STOP condition occurred wh ile th e SSP module was idle (Multi-Master system).
Note:Interrupt flag bits are set when an interrupt
condition occurs, regardless of the state of
its corresponding enable bit or the global
enable bit, GIE (INTCON<7>). User software should en sure the approp riate interrup t
bits are cle ar pri or to en ab li ng an interrupt.
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
DS30292D-page 22 1998-2013 Microchip Technology Inc.
2.2.2.6PIE2 Register
The PIE2 register cont ains the ind ividual enab le bits for
the CCP2 peripheral interrupt, the SSP bus collision
interrupt, and the EEPROM write operation interrupt.
REGISTER 2-6:PIE2 REGISTER (ADDRESS 8Dh)
U-0R/W-0U-0R/W-0R/W-0U-0U-0R/W-0
—Reserved—EEIEBCLIE——CCP2IE
bit 7bit 0
bit 7Unimplemented: Read as '0'
bit 6Reserved: Always maintain this bit clear
bit 5Unimplemented: Read as '0'
bit 4EEIE: EEPROM Write Operation Interrupt Enable
1 = Enable EE Write Interrupt
0 = Disable EE Write Interr upt
bit 3BCLIE: Bus Collision Interrupt Enable
1 = Enable Bus Collision Interrupt
0 = Disable Bus Collision Interrupt
bit 2-1Unimplemented: Read as '0'
bit 0CCP2IE: CCP2 Interrupt Enable bit
1 = Enables the CCP2 interrupt
0 = Disables the CCP2 interrupt
PIC16F87X
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
The PIR2 register contains the flag bits for the CCP2
interrupt, the SSP bus collision interrupt and the
EEPROM write operation interrupt.
.
Note:Interrupt flag bits are set when an in terrupt
condition occurs, re gardless of the st a te of
its corresponding enable bit or the global
enable bit, GIE (INTCON<7>). User software should ensure the appropriate interrupt flag bits are clear prior to enabling an
interrupt.
REGISTER 2-7:PIR2 REGISTER (ADDRESS 0Dh)
U-0R/W-0U-0R/W-0R/W-0U-0U-0R/W-0
—Reserved—EEIFBCLIF——CCP2IF
bit 7bit 0
bit 7Unimplemented: Read as '0'
bit 6Reserved: Always maintain this bit clear
bit 5Unimplemented: Read as '0'
bit 4EEIF: EEPROM Write Operation Interrupt Flag bit
1 = The write operation completed (must be cleared in software)
0 = The write operation is not complete or has not been started
bit 3BCLIF: Bus Collision Interrupt Flag bit
1 = A bus collision has occurred in the SSP, when configured for I2C Master mode
0 = No bus collision has occurred
bit 2-1Unimplemented: Read as '0'
bit 0CCP2IF: CCP2 Interrupt Flag bit
Capture mode:
1 = A TMR1 register capture occurred (must be clea red in software)
0 = No TMR1 regi ster capture occurred
Compare mode:
1 = A TMR1 register compare match occurred (must be cleared in software)
0 = No TMR1 register compare match occurred
PWM mode:
Unused
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
DS30292D-page 24 1998-2013 Microchip Technology Inc.
PIC16F87X
2.2.2.8PCON Register
The Power Control (PCON) Register contains flag bits
to allow differentiation between a Power-on Reset
(POR), a Brown-out Reset (BOR), a Watchdog Reset
(WDT), and an external MCLR
Reset.
Note:BOR is unknown on P OR. It mus t be set by
the user and checked on subsequent
RESETS to see if BOR is clear, indicating
a brown-out has occurre d. The BOR st atus
bit is a “don’t care” and is n ot pre dictable if
the brown-out circuit is disabled (by clearing the BODEN bit in the configuration
word).
REGISTER 2-8:PCON REGISTER (ADDRESS 8Eh)
U-0U-0U-0U-0U-0U-0R/W-0R/W-1
——————PORBOR
bit 7bit 0
bit 7-2Unimplemented: Read as '0'
bit 1POR
bit 0BOR
: Power-on Reset Status bit
1 = No Power-on Reset occurred
0 = A Power-on Reset occurred (must be set in software after a Power-on Reset occurs)
: Brown-out Reset Status bit
1 = No Brown-out Reset occurred
0 = A Brown-out Reset occurred (must be set in software after a Brown-out Reset occurs)
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
The program counter (PC) is 13-bits wid e. The low byte
comes from the PCL register, which is a readable and
writable register. The upper bits (PC<12:8>) are not
readable, but are indirectly writable through the
PCLA TH reg is ter. On any RESET, the upper bi t s of the
PC will be cleared. Fig ure2-5 shows the two situations
for the loading o f the PC. The up per ex ample in th e figure shows how the PC is loaded on a write to PCL
(PCLATH<4:0> PCH). The lower exam pl e i n th e fi gure shows how the PC is loaded during a CALL or GOTO
instruction (PCLATH<4:3> PCH).
FIGURE 2-5:LOADING OF PC IN
DIFFERENT SITUATIONS
2.3.1COMP UT ED GOTO
A computed GOTO is accomplish ed by adding an of fs et
to the progr am counter (ADDWF PCL). When doing a
table read using a computed GOTO method, care
should be exercise d i f the t able loca tio n cros ses a PCL
memory boundary (each 256 byte block). Refer to the
application note, “Implementing a Table Read"
(AN556).
Note 1: There are no status bits to indicate stack
overflow or stack underflow conditions.
2: There are no instructions/mnemonics
called PUSH or POP. These are actions
that occur from the execution of the
CALL, RETURN, RETLW and RETFIE
instructions, or the vectoring to an interrupt address.
2.4Program Memory Paging
All PIC16F87X devices are capable of addressing a
continuous 8K word block of program memory. The
CALL and GOTO instructions provide only 11 bits of
address to allow branching within any 2K program
memory page. When doing a CALL or GOTO instruction,
the upper 2 bits of the address are provided by
PCLATH<4:3>. When doing a CALL or GOTO instruction, the user must ensu re tha t the page select bit s are
programmed so that the desired program memory
page is addressed. If a return from a CALL instruction
(or interrupt) is execute d, the entire 13-bit PC is popped
off the stack. Therefore, manipulation of the
PCLA TH<4:3> bits is not required for the return instructions (which POPs the address from the stack).
Note:The contents of the PCLATH register are
unchanged after a RETURN or RETFIE
instruction is executed. The user must
rewrite the contents of the PCLATH register for any subsequent subroutine calls or
GOTO instructions.
Example 2-1 shows the calling of a subroutine in
page 1 of the prog ram memory. This example assumes
that PCLATH is saved and restored by the Interrupt
Service Routine
EXAMPLE 2-1:CALL OF A SUBROUTINE
(if interrupts are used).
IN PAGE 1 FROM PAGE 0
2.3.2STACK
The PIC16F87X family has an 8-level deep x 13-bit wide
hardware stack. The stack space is not part of either program or data space and the stack pointer is not readable
or writable. The PC is PUSHed onto the stack when a
CALL instruction is executed, or an interrupt causes a
branch. The stack is POPed in the event of a
RETURN,RETLW or a RETFIE instruction execution.
PCLA TH is not affected by a PUSH or POP operation.
The stack opera tes as a circular buf fer . This means that
after the st ack h as be en PUSHed eigh t time s, th e nin th
push overwrites the v alue tha t was stored fro m the first
push. The tenth pus h ov erwrites the second p us h (an d
so on).
DS30292D-page 26 1998-2013 Microchip Technology Inc.
PIC16F87X
MOVLW 0x20;initialize pointer
MOVWF FSR;to RAM
NEXTCLRFINDF;clear INDF register
INCFFSR,F;inc pointer
BTFSS FSR,4;all done?
GOTONEXT;no clear next
CONTINUE
:;yes continue
Note 1: For register file map detail, see Figure 2-3.
Data
Memory
(1)
Indirect AddressingDirect Addressing
Bank SelectLocation Select
RP1:RP 06
0
From Opcode
IRPFSR register
7
0
Bank Select
Location Select
00011011
Bank 0Bank 1Bank 2Bank 3
FFh
80h
7Fh
00h
17Fh
100h
1FFh
180h
2.5Indirect Addressing, INDF and
FSR Registers
The INDF register is not a physi cal register. Addressing
the INDF register will cause indirect addressing.
Indirect addressing is possible by using the INDF register. Any instruc tion using the INDF register actual ly
accesses the register pointed to by the File Sele ct Register, FSR. Reading the INDF register itself, indirectly
(FSR = '0') will read 00h. Writing to the INDF register
indirectly result s in a no op era tion (although status bits
may be affected ). An eff ective 9- bit add ress is obt ained
by concatenating the 8 -bit FSR regi ster and the IRP b it
(STAT US<7>), as shown in Figure 2-6.
FIGURE 2-6:DIRECT/INDIRECT ADDRESSING
A simple program to clear RAM locations 20h-2Fh
using indirect addressing is shown in Example 2-2.
DS30292D-page 28 1998-2013 Microchip Technology Inc.
PIC16F87X
BCFSTATUS, RP0;
BCFSTATUS, RP1; Bank0
CLRFPORTA; Initialize PORTA by
; clearing output
; data latches
BSFSTATUS, RP0; Select Bank 1
MOVLW0x06; Configure all pins
MOVWFADCON1; as digital inputs
MOVLW0xCF; Value used to
; initialize data
; direction
MOVWFTRISA; Set RA<3:0> as inputs
; RA<5:4> as outputs
; TRISA<7:6>are always
; read as '0'.
Data
Bus
QD
Q
CK
QD
Q
CK
QD
EN
P
N
WR
Port
WR
TRIS
Data Latch
TRIS Latch
RD
RD Port
V
SS
VDD
I/O pin
(1)
Note 1: I/O pins have protection diodes to VDD and VSS.
Analog
Input
Mode
TTL
Input
Buffer
To A/D Converter
TRIS
Data
Bus
WR
Port
WR
TRIS
RD Port
Data Latch
TRIS Latch
RD
Schmitt
Trigger
Input
Buffer
N
V
SS
I/O pin
(1)
TMR0 Clock Input
QD
Q
CK
QD
Q
CK
EN
QD
EN
Note 1: I/O pin has protection diodes to VSS only.
TRIS
3.0I/O PORTS
Some pins for th ese I/O ports are multiplexed with an
alternate function for the peripheral features on the
device. In general, when a peripheral is enabled, that
pin may not be used as a general purpose I/O pin.
Additional inform atio n o n I/O ports ma y b e f oun d in the
®
MCU Mid-Range Reference Manual, (DS33023).
PIC
3.1PORTA and the TRISA Register
PORTA is a 6-bit wide, bi-directional port. The corresponding data direction register is TRISA. Setting a
TRISA bit (= 1) wi ll make the correspondin g PORTA pin
an input (i.e., put the corresponding output driver in a
Hi-Impedance mode). Clearing a TRISA bit (= 0) will
make the correspondin g POR TA pin an output (i.e., put
the contents of the output latch on the selected pin).
Reading the PORTA register reads the status of the
pins, whereas writing to i t will write to the port latch. All
write operations are read-modify-write operations.
Therefore, a write to a port implies that the port pins are
read, the value is modified and then written to the port
data latch.
Pin RA4 is multiplexed with the Timer0 module clock
input to become the RA4/T0CKI pin. The RA4/T0CKI
pin is a Schmitt Trigger input and an open drain outpu t.
All other PORTA pins have TTL input levels and full
CMOS output drivers.
Other PORTA pins are multiplexed with analog inputs
and analog V
selected by clearing/setting the control bits in the
ADCON1 register (A/D Control Register1).
Note:On a Power-on Reset, these pins are con-
The TRISA register controls the direction of the RA
pins, even when they are be ing us ed as ana log inputs.
The user must ensure the bits in the TRISA regi ster are
maintained se t when using t hem as analog inputs.
RA0/AN0bit0TTLInput/output or analog input.
RA1/AN1bit1TTLInput/output or analog input.
RA2/AN2bit2TTLInput/output or analog input.
RA3/AN3/V
RA4/T0CKIbit4STInput/output or external clock input for Ti mer0. Output is open drain type.
RA5/SS/AN4bit5TTLInput/output or slave select input for synchronous serial port or analog input.
Legend: TTL = TTL input, ST = Schmitt Trigger input
TABLE 3-2:SUMMARY OF REGISTERS ASSOCIATED WITH PORTA
05hPORTA
85hTRISA——PORTA Data Directio n Re gis ter
9FhADCON1 ADFM———PCFG3 PCFG2 PCFG1 PCFG0
Legend: x = unknown, u = unchanged, - = unimplemented locations read as '0'.
Shaded cells are not used by PORTA.
Note:When using the SSP module in SPI Slave mode and SS enabled, the A/D converter must be set to one of
the following modes, where PCFG3:PCFG0 = 0100,0101, 011x, 1101, 1110, 1111.
——RA5RA4RA3RA2RA1RA0
POR,
BOR
--0x 0000--0u 0000
--11 1111--11 1111
--0- 0000--0- 0000
Value on al l
other
RESETS
DS30292D-page 30 1998-2013 Microchip Technology Inc.
PIC16F87X
Data Latch
RBPU
(2)
P
V
DD
QD
CK
QD
CK
QD
EN
Data Bus
WR Port
WR TRIS
RD TRIS
RD Port
Weak
Pull-up
RD Port
RB0/INT
I/O
pin
(1)
TTL
Input
Buffer
Schmitt Trigger
Buffer
TRIS Latch
Note 1: I/O pins have diode protection to V
DD and VSS.
2: To enable weak pull-ups, set the appropriate TRIS
bit(s) and clear the RBPU
bit (OPTION_REG<7>).
RB3/PGM
Data Latch
From other
RBPU
(2)
P
V
DD
I/O
QD
CK
QD
CK
QD
EN
QD
EN
Data Bus
WR Port
WR TRIS
Set RBIF
TRIS Latch
RD TRIS
RD Port
RB7:RB4 pins
Weak
Pull-up
RD Port
Latch
TTL
Input
Buffer
pin
(1)
ST
Buffer
RB7:RB6
Q3
Q1
Note 1: I/O pins have diode protec tion to V
DD and VSS.
2: To enable weak pull-ups, set the app ropriate TRIS
bit(s) and clear the RBPU
bit (OPTION_REG<7>).
In Serial Programming Mode
3.2PORTB and the TRISB Register
PORTB is an 8-bit wide, bi-directional port. The corresponding data direction register is TRISB. Setting a
TRISB bit (= 1) will mak e the corresponding PORTB pin
an input (i.e., put the corresponding output driver in a
Hi-Impedance mode). Clearing a TRISB bit (= 0) will
make the corresponding POR TB pin an output (i.e. , put
the contents of the output latch on the selected pin).
Three pins of PORTB are multiplexed with the Low
Voltage Programming function: RB3/PGM, RB6/PGC
and RB7/PGD. The alternate functions of these pins
are described in the S p ec ial Features Section.
Each of the PORTB pi ns has a w eak i nternal pul l-up. A
single control bit can turn on all the pull-ups. This is performed by clearing bit RBPU
weak pull-up is automatically turned off when the port
pin is configured as an output. The pull-ups are disabled on a Power-on Reset.
FIGURE 3-3:BLOCK DIAGRAM OF
(OPTION_REG<7>). The
RB3:RB0 PINS
This interrupt can wake the device from SLEEP. The
user, in the Interrupt Service Routine, can clear the
interrupt in the following manner:
a)Any read or write of PORTB. This will end the
mismatch condition.
b)Clear flag bit RBIF.
A mismatch c ond it i on wi ll cont i n ue to s et f lag bi t RB IF.
Reading PORTB will end the mismatch condition and
allow flag bit RBIF to be cleared.
The interrupt-on-change feature is recommended for
wake-up on key depression operation and operations
where PORTB is only used for the interrupt-on-change
feature. Polling of PORTB is not recommended while
using the interrupt-on-change feature.
This interrupt-on-mismatch feature, together with software configureable pull-ups on these four pins, allow
easy interface to a keypad and make it possible for
wake-up on key depression. Refer to the Embedded
Control Handbook, “Implementing Wake-up on KeyStrokes” (AN552).
RB0/INT is an ext ernal i nterrupt input pin a nd is confi gured using the INTEDG bit (OPTION_REG<6>).
RB0/INT is discussed in detail in Section 12.10.1.
Four of the PORTB pins, RB7:RB4, have an interrupton-change feature. Only pins configured as inputs can
cause this interrupt to occur (i.e., any RB7:RB4 pin
configured as an output is excluded from the interrupton-change comparison). The input pins (of RB7:RB4)
are compared with the old value latched on the last
read of PORTB. The “mismatch” outputs of RB7:RB4
are OR’ed together to generate the RB Port Change
Interrupt with flag bit RBIF (INTCON<0>).
RB4bit4TTLInput/output pin (with in terrupt-on-c hange). I nternal soft ware progra mmable
RB5bit5TTLInput/output pin (with in terrupt-on-c hange). I nternal soft ware progra mmable
RB6/PGCbit6TTL/ST
RB7/PGDbit7TTL/ST
Legend: TTL = TTL input, ST = Schmitt Trigger input
Note 1: This buffer is a Schmitt Trigger input when configured as the external interrupt.
2: This buffer is a Schmitt Trigger input when used in Serial Programming mode.
3: Low Voltage ICSP Programming (LVP) is enabled by default, which disables the RB3 I/O function. LVP
bit3TTLInput/output pin or programming pin in LVP mode. Internal software
must be disabled to enable RB3 as an I/O pin and allow maximum compatibility to the other 28-pin and
40-pin mid-range devices.
Input/output pin (with interrupt-on-change) or In-Circuit Debugger pin.
Internal software programmable weak pull-up. Serial programming clock.
(2)
Input/output pin (with interrupt-on-change) or In-Circuit Debugger pin.
Internal software programmable weak pull-up. Serial programming data.
TABLE 3-4:SUMMARY OF REGISTERS ASSOCIATED WITH PORTB
AddressNameBit 7Bit 6Bit 5Bit 4Bit 3 Bit 2 Bit 1 Bit 0
06h, 106h PORTBRB7RB6RB5RB4RB3RB2RB1RB0
86h, 186h T RISBPORTB Data Direction Register
81h, 181h OPTION_REG RBPU INTEDGT0CS T0SE PSAPS2PS1PS0
Legend: x = unknown, u = unchanged. Shaded cells are not used by PORTB.
Value on:
POR,
BOR
xxxx xxxx uuuu uuuu
1111 1111 1111 1111
1111 1111 1111 1111
Value on
all other
RESETS
DS30292D-page 32 1998-2013 Microchip Technology Inc.
PIC16F87X
Port/Peripheral Select
(2)
Data Bus
WR
Port
WR
TRIS
RD
Data Latch
TRIS Latch
RD
Schmitt
Trigger
QD
Q
CK
QD
EN
Peripheral Data Out
0
1
QD
Q
CK
P
N
V
DD
VSS
Port
Peripheral
OE
(3)
Peripheral Input
I/O
pin
(1)
Note 1: I/O pins have diode protection to VDD and VSS.
2: Port/Peripheral select signal selects between port
data and peripheral output.
3: Peripheral OE (output enable) is only activated if
peripheral select is active.
TRIS
Port/Peripheral Select
(2)
Data Bus
WR
Port
WR
TRIS
RD
Data Latch
TRIS Latch
RD
Schmitt
Trigger
QD
Q
CK
QD
EN
Peripheral Data Out
0
1
QD
Q
CK
P
N
V
DD
Vss
Port
Peripheral
OE
(3)
SSPl Input
I/O
pin
(1)
Note 1: I/O pins have diode protection to VDD and VSS.
2: Port/Peripheral select signal selects between port data
and peripheral outpu t.
3: Peripheral OE (output enable) is only activated if
peripheral select is active.
0
1
CKE
SSPSTAT<6>
Schmitt
Trigger
with
SMBus
levels
TRIS
3.3PORTC and the TRISC Register
PORTC is an 8-bit wide, bi-directional port. The corresponding data direction register is TRISC. Setting a
TRISC bit (= 1) will make the corresponding PORTC
pin an input (i.e., put the corresponding output driver in
a Hi-Impedance mode). Clearing a TRISC bit (= 0) will
make the correspondi ng PORTC pin an output (i.e., p ut
the contents of the output latch on the selected pin).
PORTC is mul tiplexed with s everal peri pheral function s
(Table 3-5). PORTC pins have Schmitt Trigger input
buffers.
2
When the I
pins can be configured with normal I
SMBus levels by using the CKE bit (SSPSTAT<6>).
When enabling peripheral functions, care should be
taken in defining TRIS bit s fo r each POR TC pin. Some
peripherals override the TRIS bit to make a pin an output, while other peripherals override the TRIS bit to
make a pin an input. Since the TRIS bit override is in
effect while the peripheral is enabled, read-modifywrite instructions (BSF, BCF, XORWF) with TRISC as
destination, should be avoided. The user should refer
to the corresponding peripheral section for the correct
TRIS bit settings.
RC0/T1OSO/T1CKIbit0STInput/output port pin or Ti mer1 oscillator output/Timer1 clock input.
RC1/T1OSI/CCP2bit1STInput/output port pin or Timer1 oscillator input or Capture2 input/
Compare2 output/PWM2 output.
RC2/CCP1bit2STInput/output port pin or Capture1 input/Compare1 output/
PWM1 output.
RC3/SCK/SCLbit3STRC3 can also be the synchronous serial clock for both SPI
RC4/SDI/SDAbit4STRC4 can also be the SPI Data In (SPI mode) or data I/O (I2C mode).
RC5/SDObit5STInput/output port pin or Synchronous Serial Port data output.
RC6/TX/CKbit6STInput/output port pin or USART Asynchronous Transmit or
RC7/RX/DTbit7STInput/output port pin or USART Asynchronous Receive or
Legend: ST = Schmitt Trigger input
TABLE 3-6:SUMMARY OF REGISTERS ASSOCIATED WITH PORTC
07hPORTCRC7RC6RC5RC4RC3RC2RC1RC0
87hTRISCPORTC Data Direction Register
Legend: x = unknown, u = unchanged
Value on:
POR,
BOR
xxxx xxxxuuuu uuuu
1111 11111111 1111
Value on all
other
RESETS
DS30292D-page 34 1998-2013 Microchip Technology Inc.
PIC16F87X
Data
Bus
WR
Port
WR
TRIS
RD Port
Data Latch
TRIS Latch
RD
Schmitt
Trigger
Input
Buffer
I/O pin
(1)
Note 1: I/O pins have protection diodes to VDD and VSS.
QD
CK
QD
CK
EN
QD
EN
TRIS
3.4PORTD and TRISD Registers
PORTD and TRISD are not implemented on the
PIC16F873 or PIC16F876.
PORTD is an 8-bit port with Schmitt Trigger input buffers. Each pin is in dividually co nfigureable as a n input or
output.
PORTD can be configured as an 8-bit wide microprocessor port (parallel slave p ort) by setting c ontrol bit
PSPMODE (TRISE<4>). In this mode, the input buffe rs
are TTL.
Input/output port pin or parallel slave port bit0.
Input/output port pin or parallel slave port bit1.
Input/output port pin or parallel slave port bit2.
Input/output port pin or parallel slave port bit3.
Input/output port pin or parallel slave port bit4.
Input/output port pin or parallel slave port bit5.
Input/output port pin or parallel slave port bit6.
Input/output port pin or parallel slave port bit7.
Legend: ST = Schmitt Trigger input, TTL = TTL input
Note 1: Input buffers are Schmitt Triggers when in I/O mode and TTL buffers when in Parallel Slave Port mode.
T ABLE 3-8:SUMMARY OF REGISTERS ASSOCIATED WITH PORTD
AddressNameBit 7Bit 6 Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
08hPORTDRD7RD6RD5RD4RD3RD2RD1RD0
88hTRISDPORTD Data Direction Register
89hTRISEIBFOBF IBOV PSPMODE—PORTE Data Direc tio n Bit s
Legend: x = unknown, u = unchanged, - = unimplemented, read as '0'. Shaded cells are not used by PORTD.
Note 1: I/O pins have protection diodes to VDD and VSS.
TRIS
3.5PORTE and TRISE Register
PORTE and TRISE are not implemented on the
PIC16F873 or PIC16F876.
PORTE has three pins (RE0/RD
and RE2/CS
/AN7) which are ind iv idu all y co nfi gure able
as inputs or outputs. These pins have Schmitt Trigger
input buffers.
The PORTE pins become the I/O control inputs for the
microprocessor port when bit PSPMODE (TRISE<4>) is
set. In this mode, the user must make certain that the
TRISE<2:0> bits are set, and that the pins are configured
as digital input s. Also ensure that ADCON1 is co nfigured
for digital I/O. In this mo de, th e in put bu ffers are TTL.
Register 3-1 shows the TRISE register, which als o controls the parallel slave port operat ion.
PORTE pins are multiplexed with analog inputs. When
selected for analog input, these pins will read as '0's.
TRISE controls the direction of the RE pins, even when
they are being used as analog inputs. The user must
make sure to keep the pins configured as inputs when
using them as analog inputs.
Note:On a Power-on Reset, these pins are con-
figured as analog inputs, and read as ‘0’.
/AN5, RE1/WR/AN6,
FIGURE 3-8:PORTE BLOCK DIAGRAM
(IN I/O PORT MODE)
TABLE 3-9:PORTE FUNCTIONS
NameBit#Buffer TypeFunction
I/O port pin or read control input in Parallel Slave Port mode or analog input:
RD
RE0/RD
/AN5bit0ST/TTL
(1)
1 =Idle
0 = Read operation. Contents of PORTD register are output to PORTD
I/O pins (if chip selected)
I/O port pin or write control input in Parallel S lave Port mode or analog input:
WR
RE1/WR/AN6bit1ST/TTL
(1)
1 =Idle
0 = Write operation. Value of PORTD I/O pins is latched into PORTD
register (if chip selected)
I/O port pin or ch ip sele ct co ntrol in put in Para llel Sl ave Port m ode or an alog in put:
RE2/CS
/AN7bit2ST/TTL
CS
(1)
1 = Device is not selected
0 = Device is selected
Legend: ST = Schmitt Trigger input, TTL = TTL input
Note 1: Input buffers are Schmitt Triggers when in I/O mode and TTL buffers when in Parallel Slave Port mode.
TABLE 3-10:SUMMARY OF REGISTERS ASSOCIATED WITH PORTE
The Parallel Slave Port (PSP) is not implemented on
the PIC16F873 or PIC16F876.
PORTD operates as an 8 -bit wide Parallel Slav e Port or
microprocessor port, when control bit PSPMODE
(TRISE<4>) is set. I n Sl av e mo de, it is asynchro nou sl y
readable and writa ble by the ex ternal world throu gh RD
control input pin RE0/RD and WR control input pin
RE1/WR
The PSP can directly interfac e to an 8-bit m icroproce ssor data bus. The external microprocessor can read or
write the PORTD latch as an 8-bit latch. Setting bit
PSPMODE enables port pin RE0/RD
input, RE1/WR to be the WR input and RE2/CS to be
the CS
responding data direction bits of the TRISE register
(TRISE<2:0>) must be configured as inputs (set). The
A/D port configuration bits PCFG3:PCFG0
(ADCON1<3:0>) must be set to configure pins
RE2:RE0 as digital I/O.
There are actually two 8-bit latches: one for data output, and one for data input. The user writes 8-bit data
to the PORTD data latch and reads data from the port
pin latch (note that they ha ve the same address). In thi s
mode, the TRISD registe r is ignore d, since the externa l
device is controlling the direction of data flow.
A write to the PSP occurs when both the CS
lines are first detected low. When either the CS or WR
lines become hi gh (level triggered ), the Input Buffe r Full
(IBF) status flag bit (TRISE<7>) is set on the Q4 clock
cycle, following the next Q2 cycle, to signal the write is
complete (Figure 3-10). The interrupt flag bit PSPIF
(PIR1<7>) is also set on the same Q4 clock cycle. IBF
can only be cle are d b y re adi ng the PO R TD i npu t l atc h.
The Input Buffer Overflow (IBOV) status flag bit
(TRISE<5>) is set if a second write to the PSP is
attempted w hen the pre vious byte has not bee n read
out of the buffer.
A read from the PSP occurs when both the CS
lines are first detected low. The Output Buffer Full
(OBF) status flag bit (TRISE<6>) is cleared immediately (Figure 3-11), indicating that the PORTD latch is
waiting to be read by the ext ernal bus . When ei ther the
CS
rupt flag bit PSPIF is set on the Q4 clock cycle, following the next Q2 cycle, indicating that the read is
complete. OBF remains low until data is written to
PORTD by the user firmware.
.
to be the RD
(chip select) input. Fo r this function ality , th e cor-
and WR
and RD
or RD pin becomes high (level triggered), th e in ter-
When not in PSP mode, the IBF and OBF bits are hel d
clear. However, if flag bit IBOV was previously set, it
must be cleared in firmware.
An interrupt is generated and latched into flag bit
PSPIF when a read or write operation is completed.
PSPIF must be cleared by the user in fi rmware an d the
interrupt can be disabled by clearing the interrupt
enable bit PSPIE (PIE1<7>).
FIGURE 3-9:PORTD AND PORTE
BLOCK DIAGRAM
(PARALLEL SLAVE
PORT)
DS30292D-page 38 1998-2013 Microchip Technology Inc.
FIGURE 3-10:PARALLEL SLAVE PORT WRITE WAVEFORMS
Q1Q2Q3Q4
CS
Q1Q2Q3Q4Q1Q2Q3Q4
WR
RD
IBF
OBF
PSPIF
PORTD<7:0>
Q1Q2Q3Q4
CS
Q1Q2Q3Q4Q1Q2Q3Q4
WR
IBF
PSPIF
RD
OBF
PORTD<7:0>
FIGURE 3-11:PARALLEL SLAVE PORT READ WAVEFORMS
PIC16F87X
TABLE 3-11:REGISTERS ASSOCIATED WITH PARALLEL SLAVE PORT
08hPORTDPort Data Latch when written: Port pins when readxxxx xxxx uuuu uuuu
09hPORTE
89hTRISEIBFOBFIBOV PSPMODE
0ChPIR1PSPIF
8ChPIE1PSPIE
9FhADCON1
Legend: x = unknown, u = unchanged, - = unimplemented, read as '0'. Shaded cells are not used by the Parallel Slave Port.
Note 1: Bits PSPIE and PSPIF are reserved on the PIC16F873/876; always maintain these bits clear.
DS30292D-page 40 1998-2013 Microchip Technology Inc.
PIC16F87X
4.0DATA EEPROM AND FLASH
PROGRAM MEMORY
The Data EEPROM and FLASH Program Memory are
readable and writab le during no rmal operati on over the
entire V
gle byte for Data EEPROM memory and a single word
for Program memory. A write operation causes an
erase-then-write operation to take place on the specified byte or word. A bulk erase operation may not be
issued from user code (which includes removing code
protection).
Access to program memory all ows for che cksum calc ulation. The values written to program memory do not
need to be valid instructions. Therefore, up to 14-bit
numbers can be stored in memory for use as calibration parameters, serial numbers, packed 7-bit ASCII,
etc. Executing a program memory location containing
data that form an invalid instruction, results in the execution of a NOP instruction.
The EEPROM Data memory is rated for high erase/
write cycles (specif ica tio n D 120 ). The FLAS H pro gra m
memory is rated much lower (specification D130),
because EEPROM data memory can be used to store
frequently updated values. An on-chip timer controls
the write time and it w ill v ary with v olt age and tempe rature, as well as from chip to chip. Please refer to the
specifications for exact limits (specifications D122 and
D133).
A byte or word write automatically erases the location
and writes the new value (erase before write). Writing
to EEPROM data memory does not impact the operation of the device. Writing to program memory will
cease the execution of instructions until the write is
complete. The program memory cannot be accessed
during the write. During the write operation, the oscillator continues to run, the peripherals continue to function and interrupt events will be detected and
essentially “queued” until the write is complete. When
the write completes, the next instruction in the pipeline
is executed and the branch to the interrupt vector will
take place, i f the i nte rrupt is enabled a nd oc cu rred d uring the write.
Read and write access to both memories take place
indirectly through a set of Special Function Registers
(SFR). The six SFRs used are:
• EEDATA
• EEDATH
• EEADR
• EEADRH
• EECON1
• EECON2
DD range. These opera tions take place on a si n-
The EEPROM data memory allows byte read and write
operations without interfering with the normal operation
of the microcontroller. When interfacing to EEPROM
data memory, the EEADR register holds the address to
be accessed. Depending on the operation, the EEDATA
register holds the data to be written, or the data read, at
the address in EEADR. The PIC16F873/874 devices
have 128 bytes of EEPROM data memory and therefore, require that the MSb of EEADR remain clear. The
EEPROM data memory on these devices do not wrap
around to 0, i.e., 0x80 in the EEADR does not map to
0x00. The PIC16F876/877 devices have 256 bytes of
EEPROM data memory and therefore, uses all 8-bits of
the EEADR.
The FLASH program memory allows non-intrusive
read access, but write operations cause the device to
stop executing instructions, until the write completes.
When interfacing to the program memory, the
EEADRH:EEADR registers form a two-byte word,
which holds the 13-bit address of the memory location
being accessed. The register combination of
EEDATH:EEDATA holds the 14-bit data for writes, or
reflects the val ue of program m emory after a read operation. Just as in EEPROM data memory accesses, the
value of the EEADRH:EEADR registers must be within
the valid range of program memory, depending on the
device: 0000h to 1FFFh for the PIC16F873/874, or
0000h to 3FFFh for the PIC16F876/877. Addresses
outside of this ran ge do no t wrap around t o 0000h (i.e.,
4000h does not map to 0000h on the PIC16F877).
4.1EECON1 and EECON2 Registers
The EECON1 register is the control register for configuring and initiatin g the acces s. The EECON2 reg ister is
not a physically implemented register, but is used
exclusively in the memory write sequence to prevent
inadvertent writes.
There are many bits used to control the read and write
operations to EEPROM data and FLASH program
memory. The EEPGD bit determines if the access will
be a program or data memory access. When clear, any
subsequent operations will work on the EEPROM data
memory. When set, all subsequent operations will
operate in the program memory.
Read operations only us e one additio nal bit, RD, whic h
initiates the read operation from the desired memory
location. Once this bit is set, the value of the desired
memory location will be available in the data registers.
This bit cannot be cleared by firmware. It is automatically cleared at the end of the read operation. For
EEPROM data memory reads, the data will be available in the EEDATA register in the very next i nstructio n
cycle after the RD bit is set. For program memory
reads, the data will be loaded into the
EEDATH:EEDATA registers, following the second
instruction after the RD bit is set.
Write operations have two control bit s, WR and WREN,
and two status bits, WRERR and EEIF. The WREN bit
is used to enable or disable the write operation. When
WREN is clear, the write operation will be disabled.
Therefore, the WREN bit must be set befo re ex ec utin g
a write operation. Th e WR bit is used to in itiate the write
operation. It also is automatically cleared at the end of
the write operation. The interrupt flag EEIF is used to
determine when the mem ory write comp letes . This fla g
must be cleared in software before setting the WR bit.
For EEPROM data memory, once the WREN bit and
the WR bit have been set, the desired memory addres s
in EEADR will be erased, followed by a wri te of the data
in EEDATA. This operation takes place in parallel with
the microcontroller continuing to execute normally.
When the write is c omplete, the EEIF flag bit will be set.
For program memory, once the WREN bit and the WR
bit have been set, the m icrocontr oller will cease to ex e-
cute instructions. T he de sired mem ory l ocatio n poi nted
to by EEADRH:EEADR will be erased. Then, the data
value in EEDATH:EEDATA will be programmed. When
complete, the EEIF flag bi t will be set and the microcontroller will continue to execute code.
The WRERR bit is used to indicate when the
PIC16F87X device has be en re set during a write op eration. WRERR should be cleared after Power-on
Reset. Thereafter, it should be checked on any other
RESET. The WRERR bit is set when a write operation
is interrupted by a MCLR
Reset, during normal o peration. In these situati ons, following a RESET , the user should check the WRERR bit
and rewrite the memory locati on, if set. The c ontents of
the data registers, address registers and EEPGD bit
are not affected by either MCLR
out Reset, during normal operation.
REGISTER 4-1:EECON1 REGISTER (ADDRESS 18Ch)
R/W-xU-0U-0U-0R/W-xR/W-0R/S-0R/S-0
EEPGD———WRERRWRENWRRD
bit 7bit 0
Reset, or a WDT Time-out
Reset, or WDT Time-
bit 7EEPGD: Program/Data EEPROM Select bit
1 = Accesses program memory
0 = Accesses data memory
(This bit cannot be changed while a read or write operati on is in progress)
bit 6-4Unimplemented: Read as '0'
bit 3WRERR: EEPROM Error Flag bit
1 = A write operation is prematurely termina ted
(any MCLR
0 = The write operation completed
bit 2WREN: EEPROM Write Enable bit
1 = Allows write cycles
0 = Inhibits write to the EEPROM
bit 1WR: Write Control bit
1 = Initiates a write cycle. (The bit is cleared by hardware once write is complete. The WR bit
can only be set (not cleared) in software.)
0 = Write cycle to the EEPROM is complete
bit 0RD: Read Control bit
1 = Initiates an EEPROM read. (RD is cleared in hardware. The RD bit can only be set (not
cleared) in software.)
0 = Does not initiate an EEPROM read
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
Reset or any WDT Reset during normal operation)
DS30292D-page 42 1998-2013 Microchip Technology Inc.
BSF STATUS, RP1 ;
BSF STATUS, RP0 ;Bank 3
BTFSC EECON1, WR ;Wait for
GOTO $-1 ;write to finish
BCF STATUS, RP0 ;Bank 2
MOVF ADDR, W ;Address to
MOVWF EEADR ;write to
MOVF VALUE, W ;Data to
MOVWF EEDATA ;write
BSF STATUS, RP0 ;Bank 3
BCF EECON1, EEPGD ;Point to Data memory
BSF EECON1, WREN ;Enable writes
;Only disable interrupts
BCF INTCON, GIE ;if already enabled,
;otherwise discard
MOVLW 0x55 ;Write 55h to
MOVWF EECON2 ;EECON2
MOVLW 0xAA ;Write AAh to
MOVWF EECON2 ;EECON2
BSF EECON1, WR ;Start write operation
;Only enable interrupts
BSF INTCON, GIE ;if using interrupts,
;otherwise discard
BCF EECON1, WREN ;Disable writes
4.2Reading the EEPROM Data
Memory
Reading EEPROM data memory only requires that the
desired address to access be written to the EEADR
register and clear the EEPGD bit. After the RD bit is set,
data will be av ailable in the EEDATA register on the
very next instruction cycle. EEDAT A will hold this value
until another read ope rati on is in iti ated or until it is written by firmware.
The steps to reading the EEPROM data memory are:
1.Write the address to EEDATA. Make sure that
the address is not larger than the memory size
of the PIC16F87X device.
2.Clear the EEPGD bit to point to EEPROM data
memory.
3.Set the RD bit to start the read operation.
4.Read the data from the EEDATA register.
EXAMPLE 4-1: EEPROM DATA READ
The steps to write to EEPROM data memory are:
1.If step 10 is not implemented, check the WR bit
to see if a write is in progress.
2.Write the address to EEADR. Make sure that the
address is not larger than the memory size of
the PIC16F87X device.
3.Write the 8-bit data value to be programmed in
the EEDATA register.
4.Clear the EEPGD bit to point to EEPROM data
memory.
5.Set the WREN bit to enable program operati ons.
6.Disable interrupts (if enabled).
7.Execute the special five instruction sequence:
• Write 55h to EECON2 in two steps (first to W,
then to EECON2)
• Write AAh to EECON2 in two steps (first to
W, then to EECON2)
• Set the WR bit
8.Enable interrupts (if using interrupts).
9.Clear the WREN bit to disable program operations.
10. At the completion of the write cycle, the WR bit
is cleared and the EEIF interrupt flag bit is set.
(EEIF must be cleared by firmware.) If step 1 is
not implemented, then firmware should check
for EEIF to be set, or WR to clear , to indica te the
end of the program cycle.
4.3Writing to the EEPROM Data
Memory
There are many steps in writing to the EEPROM data
memory . Both address and dat a valu es must be writte n
to the SFRs. The EEPGD bit must be cleared, and the
WREN bit must be set, t o enab le w rites. The WREN b it
should be kept clear at all times, ex cept when writi ng to
the EEPROM data. The WR bit can only be set if the
WREN bit wa s set in a previous operation, i.e., they
both cannot be set in the same operation. The WREN
bit should then be cleared by firmware after the write.
Clearing the WREN bit before the write actually completes wil l not terminate the write in progre ss.
Writes to EEPROM data memory must also be prefaced with a special sequence of instructions, that prevent inadvertent wri te operatio ns. This is a s equence of
five instructions that m ust be executed without in terruptions. The firmware should verify that a write is not in
progress, before starting another cycle.
BSF STATUS, RP1 ;
BCF STATUS, RP0 ;Bank 2
MOVF ADDRL, W ;Write the
MOVWF EEADR ;address bytes
MOVF ADDRH,W ;for the desired
MOVWF EEADRH ;address to read
BSF STATUS, RP0 ;Bank 3
BSF EECON1, EEPGD ;Point to Program memory
BSF EECON1, RD ;Start read operation
NOP ;Required two NOPs
NOP ;
BCF STATUS, RP0 ;Bank 2
MOVF EEDATA, W ;DATAL = EEDATA
MOVWF DATAL ;
MOVF EEDATH,W ;DATAH = EEDATH
MOVWF DATAH ;
4.4Reading the FLASH Program
Memory
Reading FLASH program memory is much like that of
EEPROM data memory , only two NOP instructions must
be inserted afte r the RD bit is set. These two i nstruction
cycles that t he NOP instructions execute, will be used
by the micr ocontr olle r to r ead th e data out o f prog ram
memory and insert the value into the
EEDATH:EEDATA registers. Data will be available following the second NOP instruction. EEDATH and
EEDATA will hold their value until another read operation is initiated, or until they are written by firmware.
The steps to rea din g the FLASH program mem ory a re:
1.Write the address to EEADRH:EEADR. Make
sure that the address is not larger than the memory size of the PIC16F87X device.
2.Set the EEPGD bit to point to FLASH program
memory.
3.Set the RD bit to start the read operation.
4.Execute two NOP instructions to allow the micro-
controller to read out of program memory.
5.Read the data from the EEDATH:EEDATA
registers.
EXAMPLE 4-3:FLASH PROGRAM READ
DS30292D-page 44 1998-2013 Microchip Technology Inc.
4.5Writing to the FLASH Program
Memory
Writing to FLASH program memory is unique, in that
the microcontroller does not execute instructions while
programming is taking place. The oscillator continues
to run and all peripherals continue to operate and
queue interrupts, if enabled. Once the write operation
completes (specification D133), the processor begins
executing code from where it left off. The other important difference when writing to FLASH program memory, is that the WRT configuration bit, when clear,
prevents any writes to program memory (see Table 4-1).
Just like EEPROM data memory, there are many steps
in writing to the FLASH program mem ory . Bot h address
and data values must be written to the SFRs. The
EEPGD bit must be set, and the WREN bit must be s et
to enable writes. The WREN bit shou ld b e kept cl ear at
all times, except when writing to the FLASH Program
memory. The WR bit can only be set if the WREN bit
was set in a previous operation, i.e., they both cannot
be set in the same operation. The WREN bit should
then be cleared by firmwa re after the writ e. Clearing the
WREN bit before the write actually completes will not
terminate the write in progress.
Writes to program memory must also be prefaced with
a special sequence of instructions that prevent inadvertent write operations. This is a sequence of five
instructio ns t h at mu st be e xe cu t ed w ith ou t i nte r ru pt i on
for each byt e writ ten. Th ese ins truct ions must then be
followed by two NOP instructions to allow the microcontroller to setup for th e writ e opera tion. Onc e the w rite i s
complete, the execution of instructions starts with the
instruction after the second NOP.
The steps to write to program memory are:
1.Write the address to EEADRH:EEADR. Make
sure that the address i s not larger than the m emory size of the PIC16F87X device.
2.Write the 14-bit data value to be prog ram me d i n
the EEDATH:EEDATA registers.
3.Set the EEPGD bit to point to FLASH program
memory.
4.Set the WREN bit to enable program operati ons.
5.Disable interrupts (if enabled).
6.Execute the special five instruction sequence:
• Write 55h to EECON2 in two step s (first to W ,
then to EECON2)
• Write AAh to EECON2 in two steps (first to W ,
then to EECON2)
• Set the WR bit
7.Execute two NOP instruction s to allow the mic rocontroller to setup for write operation.
8.Enable interrupts (if using interrupts).
9.Clear the WREN bit to disable program
operations.
PIC16F87X
BSF STATUS, RP1 ;
BCF STATUS, RP0 ;Bank 2
MOVF ADDRL, W ;Write address
MOVWF EEADR ;of desired
MOVF ADDRH, W ;program memory
MOVWF EEADRH ;location
MOVF VALUEL, W ;Write value to
MOVWF EEDATA ;program at
MOVF VALUEH, W ;desired memory
MOVWF EEDATH ;location
BSF STATUS, RP0 ;Bank 3
BSF EECON1, EEPGD ;Point to Program memory
BSF EECON1, WREN ;Enable writes
;Only disable interrupts
BCF INTCON, GIE ;if already enabled,
;otherwise discard
MOVLW 0x55 ;Write 55h to
MOVWF EECON2 ;EECON2
MOVLW 0xAA ;Write AAh to
MOVWF EECON2 ;EECON2
BSF EECON1, WR ;Start write operation
NOP ;Two NOPs to allow micro
NOP ;to setup for write
;Only enable interrupts
BSF INTCON, GIE ;if using interrupts,
;otherwise discard
BCF EECON1, WREN ;Disable writes
At the completion of the write cycle, the WR bit is
cleared and the EEIF interrupt flag bit is set. (EEIF
must be cleared by firmware. ) Since the microcont roller
does not execute in structions duri ng the write cy cle, the
firmware does not necessarily have to check either
EEIF, or WR, to determine if the write had finished.
EXAMPLE 4-4:FLASH PROGRAM WRITE
4.6Write Verify
The PIC16F87X device s do not automatic ally verify the
value written during a write operation. Depending on
the application, good programming practice may dictate that the value written to memory b e verified against
the original value. This should be used in applications
where excessive writes can stress bits near the specified endurance limit s.
There are conditions when the device may not want to
write to the EEPROM data memory or FL ASH program
memory. To protect against these spurious write conditions, various mechanisms have been built into the
PIC16F87X devices. On power-up, the WREN bit is
cleared and the Power-up Timer (if enabled) prevents
writes.
The write initiate sequence, and the WREN bit
together, help prevent any accidental writes during
brown-out, power glitches, or firmware malfunction.
4.8Operation While Code Protected
The PIC16F87 X devi ce s ha ve tw o c ode pr o tec t mec ha nisms, one bit for EEPROM dat a memory and two bi ts for
FLASH program memory. Data can be read and written
to the EEPROM data memory, regardless of the state of
the code protection bit, CPD. When code protection is
enabled and CPD cleared, external access via ICSP is
disabled, regardles s of the sta te of the prog ram memory
code protect bits. This prevents the contents of EEPROM
data memory fro m bei ng rea d o ut of the device.
The state of the program memory code protect bits,
CP0 and CP1, do not affect the execution of instructions out of program mem ory. The PIC16F87X devices
can always read the values in program memory,
regardless of the state of the code protect bits. However , the st a te of th e c ode protect bits and the WRT bit
will have diffe rent effects on wr iting to prog ram memory. Table 4-1 shows the effect of the code protect bits
and the WRT bit on program memory.
Once code protection has been enabled for either
EEPROM data memory or FLASH program memory,
only a full erase of the entire device will disable code
protection.
PIC16F87X
4.9FLASH Program Memory Write
Protection
The configuration word contains a bit that write protects
the FLASH program memory, called WRT. This bit can
only be accessed when programming the PIC16F87X
device via ICSP. Once write protection is enable d, only
an erase of the entire device will disable it. When
enabled, write protec tion prevent s any writes to FLASH
program memory. Write protection does not affect program memory reads.
TABLE 4-1:READ/WRITE STATE OF INTERNAL FLASH PROGRAM MEMORY
Configuration Bits
CP1CP0WRT
00x All program memoryYesNo NoNo
010Unprotected areasYesNoYesNo
010Protected areasYesNoNoNo
011Unprotected areasYesYesYesNo
011Protected areasYesNoNoNo
100Unprotected areasYesNoYesNo
100Protected areasYesNoNoNo
101Unprotected areasYesYesYesNo
101Protected areasYesNoNoNo
110 Al l program mem oryYesNoYesYes
111 Al l program mem oryYesYesYesYes
Memory Location
TABLE 4-2:REGISTERS ASSOCIATED WITH DATA EEPROM/PROGRAM FLASH
10DhEEADREEPROM Address Register, Low Byte
10FhEEADRH
10ChEEDATA EEP ROM Data Register, Low Byte
10EhEEDATH
18ChEECON1 EEPGD
18DhEECO N2 EEP ROM Cont rol Register2 (not a physical register)
8DhPIE2
0DhPIR2
Legend: x = unknown, u = unchanged, r = reserved, - = unimplemented, read as '0'.
Note 1: These bits are reserved; always maintain these bits clear.
INTCONGIEPEIE
———EEPROM Address, High Byte
——EEPROM Data Register, High Byte
—(1)—EEIEBCLIE——CCP2IE
—(1)—EEIFBCLIF——CCP2IF
Shaded cells are not used during FLASH/EEPROM access.
T0IEINTERBIET0IFINTFRBIF
———WRERR WRENWRRD
Internal
Read
Internal
Write
ICSP ReadICSP Write
Value on:
POR,
BOR
0000 000x 0000 000u
xxxx xxxx uuuu uuuu
xxxx xxxx uuuu uuuu
xxxx xxxx uuuu uuuu
xxxx xxxx uuuu uuuu
x--- x000 x--- u000
——
-r-0 0--0 -r-0 0--0
-r-0 0--0 -r-0 0--0
Val ue on
all other
RESETS
DS30292D-page 46 1998-2013 Microchip Technology Inc.
PIC16F87X
RA4/T0CKI
T0SE
pin
M
U
X
CLKOUT (= F
OSC/4)
SYNC
2
Cycles
TMR0 Reg
8-bit Prescaler
8 - to - 1MUX
M
U
X
M U X
Watchdog
Timer
PSA
0
1
0
1
WDT
Time-out
PS2:PS0
8
Note: T0CS, T0SE, PSA, PS2:PS0 are (OPTION_REG<5:0>).
PSA
WDT Enable bit
M
U
X
0
1
0
1
Data Bus
Set Flag Bit T0IF
on Overflow
8
PSA
T0CS
PRESCALER
5.0TIMER0 MODULE
Counter mode is selected by setting bit T0CS
(OPTION_REG<5>). In Counter mode, Timer0 will
The Timer0 module timer/co unter has the follow ing features:
• 8-bit timer/counter
• Readable and writable
• 8-bit software programmable prescaler
• Internal or external clock select
• Interrupt on overflow from FFh to 00h
• Edge select for external clock
Figure 5-1 is a bloc k diagram o f the T imer0 mod ule and
increment either o n every rising , or fal ling ed ge of pin
RA4/T0CKI. The incrementing edge is determined by
the Timer0 Source Edge Select bit, T0SE
(OPTION_REG<4>). Clearing bit T0SE selects the rising edge. Restrictions on the external clock input are
discussed in detail in Section5.2.
The prescaler is mutually exclusively shared between
the Timer0 modu le and t he W a tch dog Timer . The prescaler is not readabl e or w rit able. Sectio n 5.3 details the
operation of the prescaler.
the prescaler shared with the WDT.
Additional information on the Timer0 module is avail-
able in the PIC® MCU Mid-Range Family Reference
Manual (DS33023).
Timer mode is selected by clearing bit T0CS
(OPTION_REG<5>). In Timer mode, the Timer0 module will incremen t every ins tru ction cycle (without pre scaler). If the TMR0 register is written, the increment is
inhibited for the following two instruction cycles. The
user can work around this by writing an adjusted value
5.1Timer0 Interrupt
The TMR0 interrupt is generated when the TMR0 register overflows from FFh to 00h. This overflow sets bit
T0IF (INTCON<2>). The interrupt can be masked by
clearing bit T0IE (INTCON<5>). Bit T0IF must be
cleared in soft ware by the T imer0 mo dule Interrupt Service Routine before re-enabling this interrupt. The
TMR0 interrupt cannot awaken the processor from
SLEEP, since the timer is shut-off during SLEEP.
to the TMR0 register.
FIGURE 5-1:BLOCK DIAGRAM OF THE TIMER0/WDT PRESCALER
When no pres caler is us ed, t he ex ternal clock inpu t is
the same as the prescaler outp ut. Th e sy nch ron iz atio n
of T0CKI with the internal phase clocks is accomplished by sampli ng the prescale r output on the Q2 and
Q4 cycles of the internal phase clocks. Therefore, it is
necessary f or T 0 CK I t o be hi g h f or a t le as t 2Tosc (and
a small RC delay of 20 ns) and low for at least 2Tosc
(and a small RC delay of 20 ns). Refer to the electrical
specification of the desired device.
Timer0 module means that there is no prescaler for the
Watchdog Timer, and vice-versa. This prescaler is not
readable or writable (see Figure 5-1).
The PSA and PS2:PS0 bits (OPTION_REG<3:0>)
determine the prescaler assignment and pre scale ratio.
When assigned to the Timer0 module, all instructions
writing to the TMR0 register ( e.g. CLRF
BSF
to WDT, a CLRWDT instr uction will clea r the prescaler
along with the Watchdog Timer. The prescaler is not
readable or writable.
5.3Prescaler
There is only one pres caler a vailable , which i s mutu ally
exclusively sha red between the T imer0 mod ule and the
Watchdog Timer. A prescaler assignment for the
REGISTER 5-1:OPTION_REG REGISTER
R/W-1R/W-1R/W-1R/W-1R/W-1R/W-1R/W-1R/W-1
RBPU
bit 7bit 0
bit 7RBPU
bit 6INTEDG
bit 5T0CS: TMR0 Clock Source Select bit
1 = Increment on high-to-low transition on T0CKI pin
0 = Increment on low-to-high transition on T0CKI pin
bit 3PSA: Prescaler Assignment bit
1 = Prescaler is assigned to the WDT
0 = Prescaler is assigned to the Timer0 module
bit 2-0PS2:PS0: Prescaler Rate Select bits
INTEDGT0CST0SEPSAPS2PS1PS0
1,MOVWF1,
1,x.. ..etc.) will clear the pre scaler . When assigne d
Note:Writing to TMR0, when the prescaler is
assigned to T imer0, will clear the pre scaler
count, but will not change the prescaler
assignment.
Note:To avoid an unintended device RESET, the instruction sequence shown in the PIC® MCU Mid-Range Fam-
DS30292D-page 48 1998-2013 Microchip Technology Inc.
ily Reference Manual (DS33023) must be executed when changing the prescaler assignment from Timer0
to the WDT. This sequence must be followed even if the WDT is disabled.
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
DS30292D-page 50 1998-2013 Microchip Technology Inc.
PIC16F87X
6.0TIMER1 MODULE
The Timer1 mod ule is a 16-bit timer/counter consistin g
of two 8-bit registers (TMR1H and TMR1L), which are
readable and writable. The TMR1 Register pair
(TMR1H:TMR1L) increments from 0000h to FFFFh
and rolls over to 0000 h. The TMR1 Inte rrupt, if enabled,
is generated on overflow, which is latched in interrupt
flag bit TMR1IF (PIR1<0>). This interrupt can be
enabled/disabled by setting/clearing TMR1 interrupt
enable bit TMR1IE (PIE1<0>).
Timer1 can operate in one of two modes:
•As a timer
•As a counter
The operating mode is determined by the clock select
bit, TMR1CS (T1CON<1>).
In Timer mode, Timer1 increments every instruction
cycle. In Counter mode, it increments on every rising
edge of the external clock input.
Timer1 can be enabled/disabled by setting/clearing
control bit TMR1ON (T1CON<0> ) .
Timer1 also has an internal “RESET input”. This
RESET can be generated by either of the two CCP
modules (Section 8.0). Register 6-1 shows the Timer1
control register.
When the Timer1 oscillator is enabled (T1OSCEN is
set), the RC1/T1OSI/CCP2 and RC0/T1OSO/T1CKI
pins become inputs. That is, the TRISC<1:0> value is
ignored, and these pins read as ‘0’.
Additional information on timer modules is available in
the PIC
(DS33023).
®
MCU Mid-Range Family Reference Manual
REGISTER 6-1:T1CON: TIMER1 CONTROL REGISTER (ADDRESS 10h)
U-0U-0R/W-0R/W-0R/W-0R/W-0R/W-0R/W-0
——T1CKPS1 T1CKPS0T1OSCENT1SYNC TMR1CS TMR1ON
bit 7bit 0
bit 7-6Unimplemented: Read as '0'
bit 5-4T1CKPS1:T1CKPS0: Timer1 Input Clock Prescale Select bits
11 = 1:8 Prescale value
10 = 1:4 Prescale value
01 = 1:2 Prescale value
00 = 1:1 Prescale value
bit 3T1OSCEN: Timer1 Oscillator Enable Control bit
1 = Oscillator is enabled
0 = Oscillator is shut-off (t he oscillat or inverter is turned off t o eliminat e power drain)
bit 2T1SYNC
When TMR1CS = 1:
1 = Do not synchronize external clock input
0 = Synchronize external cl ock input
When TMR1CS = 0
This bit is ignored. Timer1 uses the internal clock when TMR1CS = 0.
bit 1TMR1CS: Timer1 Clock Source Select bit
1 = External clock from pin RC0/T1OSO/T1CKI (on the rising edge)
0 = Internal clock (F
bit 0TMR1ON: Timer1 On bit
1 = Enables Timer1
0 = Stops Timer1
: Timer1 External Clock Input Synchronization Control bit
:
OSC/4)
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
Note 1: When the T1OSCEN bit is cleared, the inverter is turned off. This eliminates power drain.
Set Flag bit
TMR1IF on
Overflow
TMR1
6.1Timer1 Operation in Timer Mode
Timer mode is selected by clearing the TMR1CS
(T1CON<1>) bit. In this mode, the input clock to the
timer is F
(T1CON<2>) has no effect, since the internal clock is
always in sync.
FIGURE 6-1:TIMER1 INCREMENTING EDGE
OSC/4. The synchronize control bit T1SYNC
6.2Timer1 Counter Operation
Timer1 may operate in either a Synchronous, or an
Asynchronous mode, depending on the setting of the
TMR1CS bit.
When Timer1 is being incremented via an external
source, increment s occur on a rising edg e. After T imer1
is enabled in Coun ter mode, the module mus t first have
a falling edge before the counter begins to increment.
6.3Timer1 Operation in Synchronized
Counter mode is selected by setting bit TMR1CS. In
this mode, the timer increm ents on every risin g edge of
clock input on pin RC1/T1OSI/CCP2, when bit
T1OSCEN is set, or on pi n RC0/T1 OSO/T 1CKI , when
bit T1OSCEN is cleared.
FIGURE 6-2:TIMER1 BLOCK DIAGRAM
DS30292D-page 52 1998-2013 Microchip Technology Inc.
Counter Mode
If T1SYNC is cleared, the n the externa l clock input is
synchronized with internal phase clocks. The synchronization is done after the prescaler stage. The
prescaler stage is an asynchronous ripple-counter.
In this configuration, during SLEEP mode, Timer1 will
not increment even if the external clock is present,
since the synchronization circuit is shut-off. The
prescaler, however, will continue to increment.
PIC16F87X
6.4Timer1 Operation in
Asynchronous Counter Mode
If control bit T1SYNC (T1CON<2>) is set, the external
clock input is not synchronized. The timer continues to
increment asynchronous to the internal phase clocks.
The timer will continue to run during SLEEP and can
generate an interrupt-on-overflow, which will wake-up
the processor. However, special precautions in software are needed to read/write the time r (Section 6.4.1).
In Asynchronous Counter mode, Timer1 cannot be
used as a time-base for capture or compare operations.
6.4.1READING AND WRITING TIMER1 IN
ASYNCHRONOUS COUNTER
MODE
Reading TMR1H or TMR1L while the timer is running
from an external asynchronous clock, will guarantee a
valid read (taken care of in hardware). However, the
user should keep i n mind that r eadin g the 16-bit time r
in two 8-bit values itself, poses cert a in pro bl em s, s inc e
the timer may overflow between the reads.
For writes, it is recomm ended that the us er simply stop
the timer and write the desired values. A write contention may occur by writing to the timer registers, while
the register is incrementing. This may produce an
unpredictable value i n the timer register.
Reading the 16-bit value requires some care. Examples 12-2 and 12-3 in the PIC
Reference M anual (DS33 023) show how t o read and
write Ti mer1 wh en it i s runni ng in Async hronou s mode.
®
MCU Mid-Range Family
6.5Timer1 Oscillator
A crystal oscillator ci rcuit is built-in betwee n pins T1OSI
(input) and T1OSO (amplifier output). It is enabled by
setting control bit T1OSCEN (T 1CON<3>). The oscill ator is a low power oscillator, rated up to 200 kHz. It will
continue to run during SLEEP. It is primarily intended
for use with a 32 kHz crystal. Table 6-1 shows the
capacitor selection for the Timer1 oscillator.
The Timer1 oscillator is identical to the LP oscillator.
The user must provide a so f t ware time delay to ensure
proper oscillator start-up.
Note 1: Higher capacitance increases the stability
of oscillator , b ut also inc rease s the st art-up
time.
2: Sin ce each resonator/crystal has its own
characteristics, the u ser shoul d consult th e
resonator/crystal manufacturer for appropriate values of external components.
6.6Resetting Timer1 using a CCP
Trigger Output
If the CCP1 or CCP2 module is config ured in C omp are
mode to generate a “special event trigger”
(CCP1M3:CCP1M0 = 1011), this signal will reset
Timer1.
Note:The special event triggers from the CCP1
and CCP2 modules will not set interrupt
flag bit TMR1IF (PIR1<0>).
Timer1 mu st be confi gured fo r either T ime r or Synchr onized Counter mode to take advantage of this feature.
If Timer1 is running in Asynchronous Counter mode,
this RESET operation may not work.
In the event that a write t o T imer1 coinc ides with a sp ecial event trigger from CCP1 or CCP2, the write will
take precedence.
In this mode of ope rati on, the CCPRxH :CCPRx L regis ter pair effectively becomes the period register for
Timer1.
6.7Resetting of Timer1 Register Pair
(TMR1H, TMR1L)
TMR1H and TMR1L registers are not rese t to 00h on a
6.8Timer1 Prescaler
The prescaler counter is cleared on writes to the
TMR1H or TMR1L registers.
POR, or any other RESET, except by the CCP1 and
CCP2 special event triggers.
T1CON register is reset to 00h on a Power-on Reset,
or a Brown-out Reset, which shuts off the timer and
leaves a 1:1 prescale. In all other RESETS, the register
is unaffected.
TABLE 6-2:REGISTERS ASSOCIATED WITH TIMER1 AS A TIMER/COUNTER
0ChPIR1
8ChPIE1
0EhTMR1LHolding Register for the Least Significant Byte of the 16-bit TMR1 Register
0FhTMR1HHolding Register for the Most Significant Byte of the 16-bit TMR1 Register
10hT1CON
Legend:x = unknown, u = unchanged, - = unimplemented, read as '0'. Shaded cells are not used by the Timer1 module.
Note 1: Bits PSPIE and PSPIF are reserved on the PIC16F873/876; always maintain these bits clear.
INTCONGIEPEIE
(1)
PSPIF
PSPIE
——T1CKPS1 T1CKPS0 T1OSCEN T1SYNC TMR1CS TMR1ON
ADIFRCIFTXIFSSPIFCCP1IFTMR2IFTMR1IF
(1)
ADIERCIETXIESSPIECCP1IETMR2IETMR1IE
T0IEINTERBIET0IFINTFRBIF
Value on:
0000 000x0000 000u
0000 00000000 0000
0000 00000000 0000
xxxx xxxxuuuu uuuu
xxxx xxxxuuuu uuuu
--00 0000--uu uuuu
POR,
BOR
Value on
all other
RESETS
DS30292D-page 54 1998-2013 Microchip Technology Inc.
PIC16F87X
Comparator
TMR2
Sets Flag
TMR2 Reg
Output
(1)
RESET
Postscaler
Prescaler
PR2 Reg
2
F
OSC/4
1:11:16
1:1, 1:4, 1:16
EQ
4
bit TMR2IF
Note 1:TMR2 register output can be software selected by the
SSP module as a baud clock.
to
T2OUTPS3:
T2OUTPS0
T2CKPS1:
T2CKPS0
7.0TIMER2 MODULE
Timer2 is an 8-bit timer with a prescaler and a
postscaler. It can be used as the PW M time-base f or
the PWM mode of the CCP mod ule (s). The T MR2 re gister is readable and writable, and is cleared on any
device RESET.
The input clock (F
OSC/4) has a prescale option of 1:1,
Register 7-1 shows the Timer2 control register.
Additional information on timer modules is available in
the PIC
®
MCU Mid-Range Family Reference Manual
(DS33023).
FIGURE 7-1:TIMER2 BLOCK DIAGRAM
1:4, or 1:16, selected by control bits
T2CKPS1:T2CKPS0 (T2CON<1:0>).
The Timer2 module has an 8-bit period register, PR2.
Timer2 increments from 00h until it matches PR2 and
then resets to 00h on the next increment cycle. PR2 is
a readable and writable register. The PR2 register is
initialized to FFh upon RESET.
The match output of TMR2 goes through a 4-bit
postscaler (which gives a 1:1 to 1:16 scaling inclusive)
to generate a TMR2 interrupt (latched in flag bit
TMR2IF, (PIR1<1>)).
Timer2 c an b e s hu t-off by clea ring c ontrol bit TMR2ON
(T2CON<2>) , to minimize power consum ption.
REGISTER 7-1:T2CON: TIMER2 CONTROL REGISTER (ADDRESS 12h)
0ChPIR1
8ChPIE1
11hTMR2Timer2 Module’s Register0000 0000 0000 0000
12hT2CON
92hPR2Timer2 Period Register1111 1111 1111 1111
Legend:x = unknown, u = unchanged, - = unimplemented, read as '0'. Shaded cells are not used by the Timer2 module.
Note 1: Bits PSPIE and PSPIF are reserved on the PIC16F873/876; always maintain these bits clear.
DS30292D-page 56 1998-2013 Microchip Technology Inc.
PIC16F87X
8.0CAPTURE/COMPARE/PWM
MODULES
Each Capture/Compare/PWM (CCP) module contains
a 16-bit register which can operate as a:
• 16-bit Capture register
• 16-bit Compare register
• PWM Master/Slave Duty Cycle register
Both the CCP1 and CCP2 modules are identical in
operation, with the e xception being the operation of the
special event trigg er. Table 8-1 and Table 8-2 show the
resources and interactions of the CCP module(s). In
the following sections, the operation of a CCP module
is described with respect to CCP1. CCP2 operates the
same as CCP1, except where noted.
CCP1 Module:
Capture/Compare/PWM Register1 (CCPR1) is com-
prised of two 8-bit registers: CCPR1L (low byte) and
CCPR1H (high byte). The CCP1CON register controls
the operation of CCP1. The special event trigger is
generated by a compare match and will reset Timer1.
TABLE 8-2:INTERACTION OF TWO CCP MODULES
CCP2 Module:
Capture/Compare/PWM Register2 (CCPR2) is com-
prised of tw o 8-bit registers: CCPR2L (low byte) and
CCPR2H (high byte). The CCP2CON register controls
the operation of CCP2. The special event trigger is
generated by a compare match and will reset Timer1
and start an A/D conversion (if the A/D module is
enabled).
Additional information on CCP modules is available in
the PIC
(DS33023) and in application note AN594, “Using the
CCP Modules” (DS00594).
®
MCU Mid-Range Family Reference Manual
TABLE 8-1:CCP MODE - TIMER
RESOURCES REQUIRED
CCP ModeTimer Resource
Capture
Compare
PWM
Timer1
Timer1
Timer2
CCPx Mode CCPy ModeInteraction
CaptureCaptureSame TMR1 time-base
CaptureCompareThe compare should be configured for the special event trigger, which clears TMR1
CompareCompareThe compare(s) should be configured for the special event trigger, which clears TMR1
PWMPWMThe PWMs will have the same frequency and update rate (TMR2 interrupt)
PWMCaptureNone
PWMCompareNone
bit 7-6Unimplemented: Read as '0'
bit 5-4CCPxX:CCPxY: PWM Least Significant bits
Capture mode
Unused
Compare mode:
Unused
PWM mode:
These bits are the two LSbs of the PWM duty cycle. The eight MSbs are found in CCPRxL.
bit 3-0CCPxM3:CCPxM0: CCPx Mode Select bits
0000 =Capture/Compare/PWM disabled (resets CCPx module)
0100 =Capture mode, every falling edge
0101 =Capture mode, every rising edge
0110 =Capture mode, every 4th rising edge
0111 =Capture mode, every 16th rising edge
1000 =Compare mode, set output on match (CCPxIF bit is set)
1001 =Compare mode, clear output on match (CCPxIF bit is set)
1010 =Compare mode, generate software interrupt on match (CCPxIF bit is set, CCPx pin is
1011 = Compare mode, trigger s pecial event (CCPxIF b it is set, CCPx pin is un affected); CCP1
11xx =PWM mode
:
unaffected)
resets TMR1; CCP2 resets TMR1 and starts an A/D conversion (if A/D module is
enabled)
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
DS30292D-page 58 1998-2013 Microchip Technology Inc.
PIC16F87X
CCPR1HCCPR1L
TMR1HTMR1L
Set Flag bit CCP1IF
(PIR1<2>)
Capture
Enable
Qs
CCP1CON<3:0>
RC2/CCP1
Prescaler
1, 4, 16
and
edge detect
pin
CLRFCCP1CON; Turn CCP module off
MOVLWNEW_CAPT_PS ; Load the W reg with
; the new prescaler
; move value and CCP ON
MOVWFCCP1CON; Load CCP1CON with this
; value
8.1Capture Mode
In Capture mode, CCPR1H:CCPR1L captures the
16-bit value of the TMR1 r egister wh en an eve nt occurs
on pin RC2/CCP1. An ev ent is defined as on e of the following:
• Every falling edge
• Every rising edge
• Every 4th rising edge
• Every 16th rising edge
The type of event is configured by control bits
CCP1M3:CCP1M0 (CCPxCON<3:0>). When a capture is made, the interrupt request flag bit CCP1IF
(PIR1<2>) is set. The interrupt flag must be cleared in
software. If another capture occurs before the value in
register CCPR1 is read, th e old ca ptured v alue is overwritten by the new value.
8.1.1CCP PIN CONFIGURATION
In Capture mode, the R C2/CCP1 pin should b e co nfi gured as an input by setting the TRIS C<2> bit.
Note:If the RC2/CCP1 pin is configured as an
output, a write t o the port c an cau se a capture condition.
8.1.2TIMER1 MODE SELECTION
Timer1 must be running in Timer mode, or Synchronized Counter mode, for the CCP module to use the
capture feature. In Asynchronous Counter mode, the
capture operation may not work.
8.1.3SOFTWARE INTERRUPT
When the Capture mode is changed, a false capture
interrupt may be generated. The user should keep bit
CCP1IE (PIE1<2>) clear to avoid false interrupts and
should clear the flag bit CCP1IF, following any such
change in operating mode.
8.1.4CCP PRESCALER
There are four prescaler settings, specified by bits
CCP1M3:CCP1M0. Whenever the CCP module is
turned off, or the CCP module is not in Capture mode,
the prescaler counter is cleared. Any RESET will clear
the prescaler counter.
Switching from one capture prescaler to another may
generate an interrupt. Also, the prescaler counter will
not be cleared, therefore, the first cap ture may be from
a non-zero prescaler. Example 8-1 shows the recommended method for switching between capture prescalers. This example also clears the prescaler counter
and will not generate the “false” interrupt.
reset Timer1, but not set interrupt flag bit TMR1IF (PIR1<0>),
and set bit GO/DONE (ADCON0<2>).
8.2Compare Mode
In Compare mo de, th e 16- bit CC PR1 re gist er va lue is
constantly compared against the TMR1 register pair
value. When a match occurs, the RC2/CC P1 pin is:
• Driven high
•Driven low
• Remains unchanged
The action on the pin is based on the value of control
bits CCP1M3:CCP1M0 (CCP1CON<3:0>). At the
same time, interrupt flag bit CCP1IF is set.
FIGURE 8-2:COMPARE MODE
OPERATION BLOCK
DIAGRAM
8.2.2TIMER1 MODE SELECTION
Timer1 must be running in Timer mode, or Synchronized Counter mode, if the CCP module is using the
compare feature. In Asynchronous Counter mode, the
compare operation may not work.
8.2.3SOFTWARE INTERRUPT MODE
When Generate Sof tware Interrupt mod e is chosen, the
CCP1 pin is not affecte d. The CCPIF b it is set, c ausing
a CCP interrupt (if enabled).
8.2.4SPECIAL EVENT TRIGGER
In this mode, an internal hardware trigger is generate d,
which may be used to initiate an action.
The special event trigger output of CCP1 resets the
TMR1 regist er pai r. This al lows the CCP R1 r egis ter to
effectively b e a 16-bit progra mmable pe riod registe r for
Timer1.
The special event trigger output of CCP2 resets the
TMR1 register pai r and starts an A/D co nv ersi on (if the
A/D module i s enabled).
Note:The special event trigger from the
CCP1and CCP2 modul es w ill not set int errupt flag bit TMR1IF (PIR1<0>).
8.2.1CCP PIN CONFIGURATION
The user must configure the RC2/CCP1 pin as an output by clearing the TRISC<2> bit.
Note:Clearing the CCP1CON register will force
the RC2/CCP1 compare output latch to the
default low level. This is not the PORT C I/O
data latch.
DS30292D-page 60 1998-2013 Microchip Technology Inc.
PIC16F87X
CCPR1L
CCPR1H (Slave)
Comparator
TMR2
Comparator
PR2
(Note 1)
R
Q
S
Duty Cycle Registers
CCP1CON<5:4>
Clear Timer,
CCP1 pin and
latch D.C.
TRISC<2>
RC2/CCP1
Note 1: The 8-bit timer is concatenated with 2-bit internal Q
clock, or 2 bits of the prescaler, to create 10-bit timebase.
Period
Duty Cycle
TMR2 = PR2
TMR2 = Duty Cycle
TMR2 = PR2
log(
FPWM
log(2)
F
OSC
)
bits
=
Resolution
8.3PWM Mode (PWM)
In Pulse Width Modulation mo de, the CCPx pin produces up to a 10-bit resolution PWM output. Since the
CCP1 pin is multiplexed with the PORTC data latch,
the TRISC<2> bit must be cleared to make the CCP1
pin an output.
Figure 8-3 shows a simplified block diagram of the
CCP module in PWM mode.
For a step-by-step procedure on how to set up the C CP
module for PWM operation, see Section 8.3.3.
FIGURE 8-3:SIMPLIFIED PWM BLOCK
A PWM output (Figure 8-4) has a time-base (period)
and a time that the output stays high (duty cycle). The
frequency of the PWM is the inverse of the period
(1/period).
FIGURE 8-4:PWM OUTPUT
Note:Clearing the CCP1CON register will force
the CCP1 PWM output latch to the default
low level. This is not the PORTC I/O data
latch.
DIAGRAM
8.3.1PWM PERIO D
The PWM period is spec ified by writin g to the PR2 register. The PWM period can be calculated using the following formula:
PWM period = [(PR2) + 1] • 4 • T
OSC •
(TMR2 prescale value)
PWM frequency is defined as 1 / [PWM period].
When TMR2 is eq ual to PR2, t he following three event s
occur on the ne xt increment cycle:
•TMR2 is cleared
• The CCP1 pin is set (exception: if PWM duty
cycle = 0%, the CCP1 pin will not be set)
• The PWM duty cycle is latc hed from CC PR1L into
CCPR1H
Note:The Tim er2 post sc al er (s ee Sec ti on 7.1) is
not used in the determination of the PWM
frequency. The pos tscaler co uld be used
to have a servo update rate at a different
frequency than the PWM output.
8.3.2PWM DUTY CYCLE
The PWM duty cycle is specified by writing to the
CCPR1L register and to the CCP1CON<5:4> bits. Up
to 10-bit re so l uti on is av ai l ab le. T he CC PR 1L c on tai ns
the eight MSbs and the CCP1CON<5:4> contains the
two LSbs. This 10-bit value is represented by
CCPR1L:CCP1CON<5:4>. The following equation is
used to calculate the PWM duty cycle in time:
P WM duty cy cl e = (CCP R1 L: CCP1CON<5:4>) •
OSC • (TMR2 prescale value)
T
CCPR1L and CCP1CON<5:4> can be written to at any
time, but the duty cycle value is not latched into
CCPR1H until after a match between PR2 and TMR2
occurs (i.e., the period is complete). In PWM mode,
CCPR1H is a read-only register.
The CCPR1H register and a 2-bit internal latch are
used to double buf fer the PWM duty cycle. Thi s doubl e
buffering is essential for glitch-free PWM operation.
When the CCP R1H and 2 -bit latch match T MR2, c oncatenated with an internal 2-b it Q clock , or 2 bits of the
TMR2 prescaler, the CCP1 pin is cleared.
The maximum PWM resolution (bits) for a given PWM
frequency is given by the formula:
0ChPIR1
0DhPIR2
8ChPIE1
8DhPIE2
87hTRISCPORTC Data Direction Register1111 1111 1111 1111
0EhTMR1LHolding Register for the Least Significant Byte of the 16-bit TMR1 Registerxxxx xxxx uuuu uuuu
0FhTMR1HHolding Register for the Most Significant Byte of the 16-bit TMR1 Registerxxxx xxxx uuuu uuuu
10hT1CON
15hCCPR1LCapture/Compare/PWM Register1 (LSB)xxxx xxxx uuuu uuuu
16hCCPR1HCapture/Compare/PWM Register1 (MSB)xxxx xxxx uuuu uuuu
17hCCP1CON
1BhCCPR2LCapture/Compare/PWM Register2 (LSB)xxxx xxxx uuuu uuuu
1ChCCPR2HCapture/Compare/PWM Register2 (MSB)xxxx xxxx uuuu uuuu
1DhCCP2CON
Legend: x = unknown, u = unchanged, - = unimplemented, read as '0'. Shaded cells are not used by Capture and Timer1.
Note 1: The PS P is not implemented on the PIC16F873/876; always maintain these bits clear.
0ChPIR1
0DhPIR2
8ChPIE1
8DhPIE2
87hTRISCPORTC Data Di re cti o n Regi s t er1111 1111 1111 1111
11hTMR2T imer2 Module’s Register0000 0000 0000 0000
92hPR2Timer2 Mo dul e’s Period Re gi ste r1111 1111 1111 1111
12hT2CON
15hCCPR1LCapture/Compare/PWM Register1 (LSB)xxxx xxxx uuuu uuuu
16hCCPR1HCapture/Compare/PWM Register1 (MSB)xxxx xxxx uuuu uuuu
17hCCP1CON
1BhCCPR2LCapture/Compare/PWM Register2 (LSB)xxxx xxxx uuuu uuuu
1ChCCPR2HCapture/Compare/PWM Register2 (MSB)xxxx xxxx uuuu uuuu
1DhCCP2CON
Legend: x = unknown, u = unchanged, - = unimplemented, read as '0'. Shaded cells are not used by PWM and Timer2.
Note 1: Bits PSPIE and PS PIF are reserv ed on the PIC16F873/876; always maintain these bits clear.
DS30292D-page 64 1998-2013 Microchip Technology Inc.
9.0MASTER SYNCHRONOUS
SERIAL PORT (MSSP)
MODULE
The Master Synchronous Serial Port (MSSP) module is
a serial interface, useful for communicating with other
peripheral or microc ontroll er dev ices. Th ese p eriphera l
devices may be serial EEPROMs, shift registers, display drivers, A/D converters, etc. The MSSP module
can operate in one of two modes:
• Serial Peripheral Interface (SPI)
• Inter-Integrated Circuit (I
Figure 9-1 shows a block diagram for the SPI mode,
while Figure 9-5 and Figure 9-9 show the block diagrams for the two different I
The Application Note AN734, “Using the PIC
SSP for Slave I
slave operation of the MSSP module on the
PIC16F87X devices. AN735, “Using the PIC® MCU
MSSP Module for I
the master operation of the MSSP module on the
PIC16F87X devices.
REGISTER 9-1:SSPSTAT: SYNC SERIAL PORT STATUS REGISTER (ADDRESS: 94h)
R/W-0R/W-0R-0R-0R-0R-0R-0R-0
SMPCKED/A
bit 7bit 0
bit 7SMP: Sample bit
SPI Master mode:
1 = Input data sampled at end of data output time
0 = Input data sampled at middle of data output time
SPI Slave mode:
SMP must be cleared when SPI is used in slave mode
2
C Master or Slave mode:
In I
1 = Slew rate control disabled for standard speed mode (100 kHz and 1 MHz)
0 = Slew rate control enabled for high speed mode (400 kHz)
bit 6CKE: SPI Clock Edge Select (Figure 9-2, Figure 9-3 and Figure 9-4)
SPI mode:
For CKP = 0
1 = Data transmitted on rising edge of SCK
0 = Data transmitted on falling edge of SCK
For CKP = 1
1 = Data transmitted on falling edge of SCK
0 = Data transmitted on rising edge of SCK
2
C Master or Slave mode:
In I
1 = Input levels conform to SMBus spec
0 = Input levels conform to I
bit 5D/A: Data/Address
1 = Indicates that the last byte received or transmitted was data
0 = Indicates that the last byte received or transmitted was address
bit 4P: STOP bit
(I2C mode only. This bit is cleared when the MSSP module is disabled, SSPEN is cleared.)
1 = Indicates that a STOP bit has been detected last (this bit is '0' on RESET)
0 = STOP bit was not detected last
bit 3S: START bit
bit 2R/W: Read/Write bit Information (I
bit 1UA: Update Address (10-bit I
bit BF: Buffer Full Status bit
2
C mode only. This bit is cleared when the MSSP module is disabled, SSPEN is cleared.)
(I
1 = Indicates that a START bit has been detected last (this bit is '0' on RESET)
0 = START bit was not detected last
This bit holds the R/W bit information following the last address match. This bit is only valid from the
address match to the next START bit, STOP bit or not ACK
2
C Slave mode:
In I
1 = Read
0 = Write
2
In I
C Master mode:
1 = Transmit is in progress
0 = Transmit is not in progress
Logical OR of this bit with SEN, RSEN, PEN, RCEN, or ACKEN will indicate if the MSSP is in IDLE mode.
1 = Indicates that the user needs to update the address in the SSPADD register
0 = Address does not need to be updated
Receive (SPI and I2 C modes):
1 = Receive complete, SSPBUF is full
0 = Receive not complete, SSPBUF is empty
Transmit (I
1 = Data transmit in progress (does not include the ACK and STOP bits), SSPBUF is full
0 = Data transmit complete (does not include the ACK
bit (I2C mode only)
2
C mode only):
2
C specs
2
C mode only)
2
C mode only)
PSR/WUABF
bit.
and STOP bits), SSPBUF is empty
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
DS30292D-page 66 1998-2013 Microchip Technology Inc.
PIC16F87X
REGISTER 9-2:SSPCON: SYNC SERIAL PORT CONTROL REGISTER (ADDRESS 14h)
R/W-0R/W-0R/W-0R/W-0R/W-0R/W-0R/W-0R/W-0
WCOLSSPOVSSPENCKPSSPM3SSPM2SSPM1SSPM0
bit 7bit 0
bit 7WCOL: Write Collision Detect bit
Master mode:
1 = A write to SSPBUF was attempted while the I2C conditions were not valid
0 = No collision
Slave mode:
1 = SSPBUF register is written while still transmitting the previous word (must be cleared in
software)
0 = No collision
bit 6SSPOV: Receive Overflow Indicator bit
In SPI mode:
1 = A new byte is received while SSPBUF holds previous data. Data in SSPSR is lost on overflow. In Slave
mode, the user must read the SSPBUF, even if only transmitting data, to avoid overflows. In Master
mode, the overflow bit is not set, since each operation is initiated by writing to the SSPBUF register.
(Must be cleared in software.)
0 = No overflow
2
C mode:
In I
1 = A byte is received while the SSPBUF is holding the previous byte. SSPOV is a "don’t care" in Transmit
mode. (Must be cleared in software.)
0 = No overflow
bit 5SSPEN: Synchronous Serial Port Enable bit
In SPI mode
When enabled, these pins must be properly configured as input or output
1 = Enables serial port and configures SCK, SDO, SDI, and SS as the source of the serial port pins
0 = Disables serial port and configures these pins as I/O port pins
2
C mode,
In I
When enabled, these pins must be properly configured as input or output
1 = Enables the serial port and configures the SDA and SCL pins as the source of the serial port pins
0 = Disables serial port and configures these pins as I/O port pins
bit 4CKP: Clock Polarity Select bit
In SPI mode:
1 = Idle state for clock is a high level
0 = Idle state for clock is a low level
2
In I
C Slave mode:
SCK release control
1 = Enable clock
0 = Holds clock low (clock stretch). (Used to ensure data setup time.)
2
C Master mode:
In I
Unused in this mode
bit 3-0
SSPM3:SSPM0: Synchronous Serial Port Mode Select bits
0000 = SPI Master mode, clock = F
0001 = SPI Master mode, clock = F
0010 = SPI Master mode, clock = F
0011 = SPI Master mode, clock = TMR2 output/2
0100 = SPI Slave mode, clock = SCK pin. SS
0101 = SPI Slave mode, clock = SCK pin. SS
0110 = I
0111 = I
1000 = I
1011 = I
1110 = I
1111 = I
1001, 1010, 1100, 1101 = Reserved
,
OSC/4
OSC/16
OSC/64
pin control enabled.
2
C Slave mode, 7-bit address
2
C Slave mode, 10-bit address
2
C Master mode, clock = FOSC / (4 * (SSPADD+1))
2
C Firmware Controlled Master mode (slave idle)
2
C Firmware Controlled Master mode, 7-bit address with START and STOP bit interrupts enabled
2
C Firmware Controlled Master mode, 10-bit address with START and STOP bit interrupts enabled
pin control disabled. SS can be used as I/O pin.
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
REGISTER 9-3:SSPCON2: SYNC SERIAL PORT CONTROL REGISTER2 (ADDRESS 91h)
R/W-0R/W-0R/W-0R/W-0R/W-0R/W-0R/W-0R/W-0
GCENACKSTATACKDTACKENRCENPENRSENSEN
bit 7bit 0
2
bit 7GCEN: General Call Enable bit (In I
1 = Enable interrupt when a general call address (0000h) is received in the SSPSR
0 = General call address disabled
bit 6ACKSTAT: Acknowledge Status bit (In I
In Master Transmit mode:
1 = Acknowledge was not received from slave
0 = Acknowledge was received from slave
bit 5ACKDT: Acknowledge Data bit (In I
In Master Receive mode:
Value that will be transmitted when the user initiates an Acknowledg e sequence at the
end of a receive.
1 = Not Acknowledge
0 = Acknowledge
bit 4ACKEN: Acknowledge Sequence Enable bit (In I
In Master Receive mode:
1 = Initiate Acknowledge sequence on SDA and SCL pins and transmit ACKDT data bit.
Automatically cleared by hardware.
0 = Acknowledge sequence idle
bit 3RCEN: Receive Enable bit (In I
1 = Enables Receive mode for I
0 = Receive idle
bit 2PEN: STOP Condition Enable bit (In I
SCK Release Control:
1 = Initiate STOP condition on SDA and SCL pins. Automatically cleared by hardware.
0 = STOP condition idle
bit 1RSEN: Repeated START Condition Enable bit (In I
1 = Initiate Repeated START cond ition on SDA and SCL pins. Automatically cleared by hardware.
0 = Repeated START condition idle
bit 0SEN: START Conditi on Enab le bit (In I2C Master mode only)
1 = Initiate START condition on SDA and SCL pins. Automatically cleared by hardware.
0 = START condition idle
C Slave mode only)
2
C Master mode only)
2
C Master mode only)
2
2
C Master mode only)
2
C
2
C Master mode only)
C Master mode only)
2
C Master mode only)
Note:For bits ACKEN, RCEN, PEN, RSEN, SEN: If the I
2
C module is not in the IDLE
mode, this bit may not be set (no spoo lin g), an d t he SSPBUF may not be writte n (or
writes to the SSPBUF are disabled).
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
DS30292D-page 68 1998-2013 Microchip Technology Inc.
PIC16F87X
ReadWrite
Internal
Data Bus
SSPSR Reg
SSPM3:SSPM0
bit0
Shift
Clock
SS
Control
Enable
Edge
Select
Clock Select
TMR2 Output
T
OSC
Prescaler
4, 16, 64
2
Edge
Select
2
4
Data to TX/RX in SSPSR
Data Direction bit
2
SMP:CKE
SDI
SDO
SS
SCK
SSPBUF Reg
9.1SPI Mode
The SPI mode allo ws 8 bits of data to be sync hronously
transmitted and received simultaneously. All four
modes of SPI are supported. To accomplish communication, typically three pins are used:
• Serial Data Out (SDO)
• Serial Data In (SDI)
• Serial Clock (SCK)
Additionally, a fourth pin may be used when in a Slave
mode of operation:
• Slave Select (SS
When initializing the SPI, several options need to be
specified. This is done by pro gramming th e appropriate
control bits (SSPCON<5:0> and SSPSTAT<7:6>).
These control bits allow the following to be specified:
• Master mode (SCK is the clock output)
• Slave mode (SCK is the clock input)
• Clock Polarity (Idle state of SCK)
• Data input sample phase
(middle or end of data output time)
• Clock edge
(output data on rising/falling edge of SCK)
• Clock Rate (Master mode only)
• Slave Select mode (Slave mode only)
Figure 9-4 shows the block diagram of th e MSSP module when in SPI mode.
To enable the serial port, MSSP Enable bit, SSPEN
(SSPCON<5>) must be set. T o reset or rec onfigure SPI
mode, clear bit SSPEN, re-initialize the SSPCON registers, and then set bit SSPEN. This configures the
SDI, SDO, SCK and SS
pins to behave as the serial port function, some must
have their data direction bits (in the TRIS register)
appropriately programmed. That is:
• SDI is automaticall y c ontrolled by the SPI mo dul e
• SDO must have TRISC<5> cleared
• SCK (Master mode) must have TRISC<3>
cleared
• SCK (Slave mode) must have TRISC<3> set
must have TRISA<5> set and register
•SS
ADCON1 (see Section11.0: A/D Modul e) must be
set in a way that pin RA5 is confi gured a s a dig it al
I/O
)
pins as serial port pins . For the
Any serial port function that is not desired may be
overridden by programming the corresponding data
direction (TRIS) register to the opposite value.
The master can initiate the data transfer at any time
because it controls the SCK. The master determines
when the slave (Processor 2, Figure 9-5) is to broadcast data by the software protoc ol.
In Master mode, the data is transmitted/received as
soon as the SSPBUF register is written to. If the SPI
module is only going to receive, the SDO output could
be disabled (programmed as an input). The SSPSR
register will conti nue to shif t in the signa l present o n the
SDI pin at the programmed clock rate. As each byte is
received, it will be loaded into the SSPBUF register as
if a normal received byte (interrupts and status bits
appropriately set). This could be useful in receiver
applications as a “line activity monitor”.
The clock polarity is selected by appropriately programming bit CKP (SSPCON<4>). This then, would give
waveforms for SPI communication as shown in
FIGURE 9-2:SPI MODE TIMING, MASTER MODE
Figure 9-6, Figure 9-8 and Figure 9-9, where the MSb is
transmitted first. In Master mode, the SPI clock rate (bit
rate) is user programmable to be one of the following:
OSC/4 (or TCY)
•F
•F
OSC/16 (or 4 • TCY)
•FOSC/64 (or 16 • TCY)
• Timer2 output/2
This allows a maximu m bit clock freq uency (at 20 MHz)
of 5.0 MHz.
Figure 9-6 shows the waveforms for Master mode.
When CKE = 1, the SDO data is valid before there is a
clock edge on SCK. The change of the input sample is
shown based on the state of the SMP bit. The time
when the SSPBUF is loaded with the received data is
shown.
DS30292D-page 70 1998-2013 Microchip Technology Inc.
PIC16F87X
SCK (CKP = 0)
SDI (SMP = 0)
SSPIF
bit7
bit6bit5
bit4
bit3
bit2
bit1bit0
SCK (CKP = 1)
SDO
bit7bit0
SS (optional)
SCK (CKP = 0)
SDI (SMP = 0)
SSPIF
bit7
bit6bit5
bit4
bit3
bit2
bit1bit0
SCK (CKP = 1)
SDO
bit7bit0
SS
9.1.2SLAVE MODE
In Slave mode, the data is tra nsmitted and r eceived as
the external clock pulses ap pea r on SCK . When th e last
bit is latched, the interrupt flag bit SSPIF (PIR1<3>) is set.
While in Slave mode, the external clock is supplied by
the external clock source on the SCK pin. This external
clock must meet the minimum high and low times as
specified in the electrical specifications.
While in SLEEP mode, the slave can transmit/receive
data. When a byte is received, the device will wake-up
from SLEEP.
Note 1: When the SPI module is in Slave
mode with SS
(SSPCON<3:0> = 0100), the SPI module
will reset if the SS pin is set to VDD.
2: If the SPI is used in Slave mode with
CKE = '1', then SS
enabled.
FIGURE 9-3:SPI MODE TIMING (SLAVE MODE WITH CKE = 0)
pin control enabled
pin control must be
FIGURE 9-4:SPI MODE TIMING (SLAVE MODE WITH CKE = 1)
DS30292D-page 72 1998-2013 Microchip Technology Inc.
PIC16F87X
ReadWrite
SSPSR Reg
Match Detect
SSPADD Reg
START and
STOP bit Detect
SSPBUF Reg
Internal
Data Bus
Addr Match
Set, Reset
S, P bits
(SSPSTAT Reg)
SCL
Shift
Clock
MSb
LSb
SDA
9.2MSSP I2C Operation
The MSSP module in I2C mode, fully implements all
master and slav e functions (incl uding general call support) and provides interrupts on ST AR T and STO P bits in
hardware, to determine a free bus (multi-master function). The MSSP modul e im plemen ts the s ta ndard m ode
specification s, as wel l as 7-bit and 10-bi t addre ssin g.
Refer to Application Note AN578, "Use of the SSP
Module in the I
A "glitch" filter is on the SCL and SDA pins when the pi n
is an input. This fil ter operates in both the 100 kH z an d
400 kHz modes. In the 10 0 kHz mode, whe n these pin s
are an output, there is a sle w rate control of the pin th at
is independent of device frequency.
FIGURE 9-5:I2C SLAVE MODE BLOCK
Two p ins a re use d for dat a tra nsfer. These are the SCL
pin, which is the clock, and the SDA pin, which is the
data. The SDA and SCL pins are automatically configured when the I
functions are enabled by setting SSP Enable bit
SSPEN (SSPCON<5>).
The MSSP module has six registers for I
They are the:
• SSP Control Register (SSPCON)
• SSP Control Register2 (SSPCON2)
• SSP Status Register (SSPSTAT)
• Serial Receive/Transmit Buffer (SSPBUF)
• SSP Shift Register (SSPSR) - Not directly
accessible
• SSP Address Register (SSPADD)
2
C Multi-Master Environment."
DIAGRAM
2
C mode is enabled. The SSP module
2
C operation.
The SSPCON register allows control of the I
2
C operation. Four mode selection bits (SSPCON<3:0>) allow
one of the following I2C modes to be selected:
2
C Slave mode (7-bit address)
•I
2
•I
C Slave mode (10-bit address)
•I2C Master mode, cl ock = OSC/4 (SSPADD +1)
•I2C firmware modes (provided for compatibility to
other mid-range product s)
2
Before selecting any I
C mode, the SCL and SDA pins
must be programmed to inputs by setting the appropriate TRIS bits. Selecting an I2C mode by setting the
SSPEN bit, enables the SCL and SDA pins to be used
as the clock and data lines in I
2
C mode. Pu ll -u p res i stors must be provided externally to the SCL and SDA
pins for the proper operation of the I2C module.
The CKE bit (SSPSTAT<6:7>) sets the levels of the
SDA and SCL pins in either Master or Slave mode.
When CKE = 1, the levels will conform to the SMBus
specification. W hen C KE = 0 , th e le vels will conform to
2
C specification.
the I
The SSPSTAT register gives the status of the data
transfer. This information includes detection of a
START (S) or STOP (P) bit, specifies if the received
byte was data or address, if the next byte is the completion of 10-bit address, and if this will be a read or
write data transfer.
SSPBUF is the register to which the transfer data is
written to, or read from. The SSPSR register shifts the
data in or ou t of the device. In re ceive oper ations , the
SSPBUF and SSPSR create a doubled buffered
receiver. This allows reception of the next byte to begin
before reading the last by te of receiv ed data. Wh en the
complete byte is received, it is transferred to the
SSPBUF register and flag bit SSPIF is set. If another
complete byte is received before the SSPBUF register
is read, a receiver overflow has occurred and bit
SSPOV (SSPCON<6>) is set and the byte in the
SSPSR is lost.
The SSPADD register holds the slave address. In
10-bit mode, the use r needs to write th e high byte of the
address (1111 0 A9 A8 0). Following the high byte
address match, the l ow byte of the address nee ds to be
loaded (A7:A0).
In Slave mode, the SCL and SDA pins must be confi gured as inputs. The MSSP module will override the
input state with the output data, when required (slavetransmitter).
When an address is matched, or the data transfer af ter
an address m atch is re ceiv ed, the hard ware aut omati cally will generate the Acknowledge (ACK
then load the SSPBUF register with th e re ce ive d valu e
currently in the SSPSR register.
There are certain conditions that will cause the MSSP
module not to give thi s ACK
(or both):
a)The buffer full bit BF (SSPSTAT<0>) was set
before the transfer was received.
b)The overflow bit SS POV (SSPCON<6>) was set
before the transfer was received.
If the BF bit is set, the SSPSR register value is not
loaded into the SSPBUF, but bit SSPIF and SSPOV are
set. Table 9-2 shows what happens when a data transfer byte is received, given the status of bits BF and
SSPOV. The shaded cells show the condition where
user software d id no t prope rly c lear th e ove rflo w cond ition. Flag bit BF is cleared by read ing the SSPBUF register, while bit SSPOV is cleared through software.
The SCL clock input must have a minimum high and
low time for proper operation. The high and low times
2
of the I
the MSSP module, is shown in timing parameter #100
and parameter #101 of the electrical specifications.
C specification, as well as the requirement of
pulse. These are if either
) pulse, and
9.2.1.1Addressing
Once the MSSP module has been enabled, it waits for
a ST AR T co nditio n to occur. Following the STAR T co ndition, the 8-bits are shif ted into the SSPSR register. All
incoming bits are sampled with the rising edge of the
clock (SCL) line. The value of register SSPSR<7:1> is
compared to the value of the SSPADD register. The
address is compared on the falling edge of the eighth
clock (SCL) pulse. If the addresses match, and the BF
and SSPOV bits are clear, the following events occur:
a)The SSPSR register value is loaded into the
SSPBUF register on the falling edge of the 8th
SCL pulse.
b)The buffer full bit, BF, is set on the falling edge
of the 8th SCL pulse.
c)An ACK pulse is generated.
d)SSP interrupt flag bit, SSPIF (PIR1<3>), is set
(interrupt is generated if enabled) on the falling
edge of the 9th SCL pulse.
In 10-bit address mode, two address bytes need to be
received by the slave. The five Most Significant bits
(MSbs) of the first address byte specify if this is a 10-bit
address. Bit R/W
the slave device will receive the second address byte.
(SSPSTA T<2>) must specify a write so
For a 10-bit address, the first byte would equal
‘1111 0 A9 A8 0’, where A9 and A8 are the two MSbs
of the address. The sequence of events for a 10-bit
address is as follows, with steps 7-9 for slave-transmitter:
1.Receive first (high) byte of Address (bits SSPIF,
BF and UA (SSPSTAT<1>) are set).
2.Update the SSPADD register with the second
(low) byte of Address (clears bit UA and
releases the SCL line ).
3.Read the SSPBUF register (clears bit BF) and
clear flag bit SSPIF.
4.Receive second (low) byte of Address (bits
SSPIF, BF and UA are set).
5.Update the SSPADD registe r with the f irst (high)
byte of Address. This will clear bit UA and
release the SCL line.
6.Read the SSPBUF register (clears bit BF) and
clear flag bit SSPIF.
7.Receive Repeated Start condition.
8.Receive first (high) byte of Address (bits SSPIF
and BF are set).
9.Read the SSPBUF register (clears bit BF) and
clear flag bit SSPIF.
Note:Following the Repeated START condition
(step 7) in 10-bit mode, the user only
needs to match the fi rst 7-bit ad dress. Th e
user does not update the SSPADD for the
second half of the address.
9.2.1.2Slave Reception
When the R/W bit of the addres s byte is clear an d an
address match occurs, the R/W
register is cleared. Th e receive d addre ss is loa ded in to
the SSPBUF register.
When the address byte overflow condition exists, then
no Acknowledge (ACK
condition is defined as either bit BF (SSPSTAT<0>) is
set, or bit SSPOV (SSPCON<6>) is set. Thi s is an error
condition due to user firmware.
An SSP interrupt is generated for each data transfer
byte. Flag bit SSPIF (PIR1<3>) must be cleared in sof tware. The SSPSTAT register is used to determine the
status of the received byte.
Note:The SSPBUF will be loaded if the SSPOV
bit is set and the BF flag is cleared. If a
read of the SSPBUF was performed, but
the user did not clear the state of the
SSPOV bit before the next receive
occurred, the ACK
SSPBUF is updated.
) pulse is given. An overflow
bit of the SSPSTAT
is not sent and the
DS30292D-page 74 1998-2013 Microchip Technology Inc.
TABLE 9-2:DATA TRANSFER RECEIVED BYTE ACTIONS
P
9
8
7
6
5
D0
D1
D2
D3D4
D5
D6D7
S
A7 A6 A5 A4
A3 A2 A1SDA
SCL
1234
5
6
7
8
9
1234
56
7
89
123
4
Bus Master
Terminates
Transfer
Bit SSPOV is set because the SSPBUF register is still full.
Cleared in software
SSPBUF register is read
ACK
Receiving Data
Receiving Data
D0
D1
D2
D3D4
D5
D6D7
ACK
R/W=0
Receiving Address
SSPIF
BF (SSPSTAT<0>)
SSPOV (SSPCON<6>)
ACK
ACK is not sent.
Not
PIC16F87X
Status Bits as Data
Transfer is Received
BFSSPOV
SSPSR
SSPBUF
Generate ACK
Pulse
Set bit SSPIF
(SSP Interrupt occurs
if enabled)
00YesYesYes
10NoNoYes
11NoNoYes
01YesNoYes
Note:Shaded cells show the conditions where the user software did not properly clear the overflow condition.
9.2.1.3 Slave Transmission
When the R/W bit of the incoming address byte is set
and an address match occurs, the R/W
SSPSTAT register is set. The received address is
loaded into the SSPBUF register. The ACK
be sent on the ninth bit, and the SCL pin is held low.
The transmit data must be loaded into the SSPBUF
register, which also loads the SSPSR register. Then,
the SCL pin should be enabled by setting bit CKP
(SSPCON<4>). The master must monitor the SCL pin
prior to asserting another clock pulse. The slave
devices may be holding off the master by stretching the
clock. The eight data bits are shifted out on the falling
edge of the SCL input. This ensures that the SDA signal is vali d during the SCL high time (Figure 9-7).
bit of the
pulse will
An SSP interrupt is generated for each data transfer
byte. The SSPIF flag bit must be cleared in software
and the SSPST AT register is used to determine the status of the byte tran sf er. The SSPIF flag bit is set on the
falling edge of the ninth clock pulse.
As a slave-transmitter, the ACK
pulse from the master
receiver is latched on the rising edge of the ninth SCL
input pulse. If the SDA line is high (not ACK), then the
data transfer is comple te. Whe n the n ot ACK
is latched
by the slave, the slave logic is r ese t a nd t he s lave then
monitors for another occurrence of th e ST AR T bit. If the
SDA line was low (ACK
), the transmit data must be
loaded into the SSPBUF register, which also loads the
SSPSR register. Then the SCL pin should be enabled
by setting the CKP bit.
FIGURE 9-6:I2C WAVEFORMS FOR RECEPTION (7-BIT ADDRESS)
(the SSPBUF must be written to,
before the CKP bit can be set)
R/W
= 0
SDA
SCL
S
SSPIF
BF
SSPOV
Cleared in software
SSPBUF is read
R/W
= 0
ACK
General Call Address
Address is compared to General Call Address
GCEN
Receiving data
ACK
123456789123456789
D7 D6D5 D4D3 D2D1D0
after ACK, set interrupt flag
'0'
'1'
(SSPSTAT<0>)
(SSPCON<6>)
(SSPCON2<7>)
FIGURE 9-7:I2C WAVEFORMS FOR TRANSMISSION (7-BIT ADDRESS)
9.2.2GENERAL CALL ADDRESS
SUPPORT
The addressing procedure for the I2C bus is such that
the first byte after the START condition usually determines which device will be the slave addressed by the
master. The exception is the gene ral call address , which
can address all devices. When this address is used, all
devices should, in theory , respond with an acknowledge.
The general call address is one of eight addresses
reserved for specific purposes by the I
consists of all 0’s with R/W
= 0.
The general call address is recognized when the General Call Enable bit (GCEN) is enabled (SSPCON2<7>
is set). Following a START bit detect, 8 bits are shifted
into SSPSR and the address is compared against
2
C protocol. It
If the general call address matches, the SSPSR is
transferred to the SSPBUF, the BF flag is set (eighth
bit), and on the falling edge of the ninth bit (ACK
bit),
the SSPIF flag is set.
When the interrupt is serv ic ed, the s ou r ce f or the int er-
rupt can be checked by reading the contents of the
SSPBUF to determine if the address was device specific, or a general call address.
In 10-bit mode, the SSPADD is required to be updated
for the second half of the address to match , and the UA
bit is set (SSPSTAT<1>). If the general call address is
sampled when GCEN is set, while the slave is configured in 10-bit address mode, then the second half of
the address is not ne cessary, the UA bit w il l n ot be set,
and the slave will begin receiving data after the
Acknowledge (Figure9-8).
SSPADD. It is also compared to the general call
address and fixed in hardware.
FIGURE 9-8:SLAVE MODE GENERAL CALL ADDRESS SEQUENCE (7 OR 10-BIT MODE)
DS30292D-page 76 1998-2013 Microchip Technology Inc.
PIC16F87X
9.2.3SLEEP OPERATION
While in SLEEP mode, the I2C module can receive
addresses or data. When an address match or com-
9.2.4EFFECTS OF A RESET
A RESET disables the SSP module and terminates the
current tran sfer.
plete byte transfer occurs, wake the processor from
SLEEP (if the SSP interrupt is enabled).
Legend: x = unknown, u = unchanged, - = unimplemented, read as '0'. Shaded cells are not used by the SSP in I
Note 1: These bits are reserved on PIC16F873/876 devices; always maintain these bits clear.
Master mode of operation is supported by interrupt
generation on the detection of the START and STOP
conditions. The STOP (P) and START (S) bits are
cleared from a RESET, or when the MSSP module is
disabled. Control of the I
P bit is set, or the bus is idle, with bo th the S and P bit s
clear.
2
C bus may be t aken when th e
The following events will cause the SSP Interrupt Flag
bit, SSPIF, to be set (an SSP interrupt will occur if
enabled):
• START condition
• STOP condition
• Data transfer byte transmitted/received
• Acknowledge transmit
• Repeated START
In Master mode, the SCL and SDA lines are manipulated by the MSSP hardware.
FIGURE 9-9:SSP BLOCK DIAGRAM (I2C MASTER MODE)
9.2.6MULTI-MASTER MODE
In Multi-Master mode, the interrupt generation on the
detection o f the START and STOP conditions al lows
the determination of when the bus is free. The STOP
(P) and START (S) bits are cleared from a RESET or
when the MSSP module is disabled . Control of the I
bus may be taken when bit P (SSPSTAT<4>) is set, or
the bus is idle with both the S and P bits clear. When
the bus is busy, enabling the SSP Interrupt will gener-
2
C
ate the interrupt when the STOP condition occurs.
DS30292D-page 78 1998-2013 Microchip Technology Inc.
In Multi-Master operation, the SDA line must be monitored for arbitration to see if the signal level is the
expected output leve l. This chec k is perfor med in hardware, with the result placed in the BCLIF bit.
The states where arbitration can be lost are:
• Address Trans fer
• Data Transfer
• A START Condition
• A Repeated START Condition
• An Acknowledge Condition
PIC16F87X
SSPM3:SSPM0
BRG Down Counter
CLKOUT
F
OSC/4
SSPADD<6:0>
SSPM3:SSPM0
SCL
Reload
Control
Reload
9.2.7I2C MASTER MODE SUPPORT
Master mode is enabled by setting and clearing the
appropriate SSPM bits in SSPCON and by setting the
SSPEN bit. Once Master mode is enabled, the user
has six options:
• Assert a START condition on SDA and SCL.
• Assert a Repeated START condition on SDA and
SCL.
• Write to the SSPBUF register initiating transmis-
sion of data/address.
• Generate a STOP condition on SDA and SCL.
• Configure the I
• Generate an Acknowled ge cond ition at the end of
a received byte of data.
Note:The MSSP Module, when confi gured in I2C
2
C port to receive data.
Master mode, does not allow queueing of
events. For instance, the user is not
allowed to initiate a START condition and
immediately write the SSPBUF register to
initiate transmission before the START
condition is complete. In this case, the
SSPBUF will not be written to and the
WCOL bit will be set, indicating that a write
to the SSPBUF did not occur.
SSPBUF. Once the given operation is complete (i.e.,
transmission of the last d ata bit is followed b y ACK), the
internal clock will automatically stop counting and the
SCL pin will remain in its last state.
A typical transmit sequence would go as follows:
a)User generates a START condition by setting
the START enable bit (SEN) in SSPCON2.
b)SSPIF is set. The module will wait the required
start time before any other operation takes place.
c)User loads SSPBUF with address to transmit.
d)Address is s hi f ted o ut the SDA pin until al l 8 bits
are transmitted.
e)MSSP module shifts in the ACK bit from the
slave device and writes its value into the
SSPCON2 register (SSPCON2<6>).
f)MSSP module generates an interrupt at the end
of the ninth clock cycle by setting SSPIF.
g)User loads SSPBUF with eight bits of data.
h)DA T A is shifted out the SDA pin unti l all 8 bit s are
transmitted.
i)MSSP module shifts in the ACK bit from the
slave device, and writes its value into the
SSPCON2 register (SSPCON2<6>).
j)MSSP module genera tes an interru pt at the end
of the ninth clock cycle by setting the SSPIF bit.
9.2.7.1I2C Master Mode Operation
The master device generates all of the serial clock
pulses and the START and STOP conditions. A tran sfer is ended with a STOP condition or with a Repeated
k)User generates a STOP conditi on by setting the
STOP enable bit, PEN, in SSPCON2.
l)Interrupt is generated once the STOP condition
is complete.
START condition. Since the Re peated START condition is also the beginning of the nex t s eri al tran sfe r, the
2
C bus will not be released.
I
In Master Transmitter mode, serial data is output through
SDA, while SCL outputs the serial cl ock. The first by te
transmitted con tains the slave addres s of the receiving
device (7 bit s) and t he Re ad/W rite (R/W
the R/W
bit will be logic '0'. Serial data is transmitted 8 bits
) bit. In this case ,
at a time. After each byte is transmitted, an Acknowledge
bit is received. START and STOP conditions are output
to indicate the beginning and the end of a serial transfer.
9.2.8BAUD RATE GENERATOR
In I2C Master mode, the reload value for the BRG is
located in the lower 7 bits of the SSPADD register
(Figure 9-10). When the BRG is loaded with this value,
the BRG counts down to 0 and stops until another reload
has taken place. The BRG count is decremented twice
per instruction cycle (T
2
C Master mode, the BRG is reloaded automatically. If
In I
clock arbitration is taking place, the BRG will be reloaded
when the SCL pin is sampled high (Figure 9-11).
CY), on the Q2 and Q4 clock.
In Master Receive mode, the firs t byte transmitt ed contains the slave address of the transmitting device
(7 bits) and the R/W
bit. In this case, the R/W bit will be
Note:Baud Rate = FOSC / (4 * (SSPADD + 1) )
logic '1'. Thus, the first byte transmitted is a 7-bit slave
address foll owed by a '1' t o indi cate re ceive bit. Se rial
data is receiv ed vi a SDA , whi le SC L outp uts th e ser ial
clock. Serial dat a is rec eived 8 bits at a tim e. Aft er each
FIGURE 9-10:BAUD RATE GENERATOR
BLOCK DIAGRAM
byte is received, an Acknowledge bit is transmitted.
START and STOP conditions indicate the beginning
and end of transmission.
The baud rate generator used for SPI mode operation
is now used to set the SCL clock frequency for either
100 kHz, 400 kHz, or 1 MHz I
rate generator reload value is contained in the lower 7
bits of the SSPADD register. The baud rate generator
2
C operation. The baud
will automatically begin counting on a write to the
SCL is sampled high, reload takes
place, and BRG starts its count
03h02h01h00h (hold off)03h02h
Reload
BRG
Value
SCL low (clock arbitration)
SCL allowed to transition high
BRG decrements
(on Q2 and Q4 cycles)
SDA
SCL
S
TBRG
1st Bit
2nd Bit
TBRG
SDA = 1,
At completion of START bit,
SCL = 1
Write to SSPBUF occurs here
TBRG
Hardware clears SEN bit
TBRG
Write to SEN bit occurs here
Set S bit (SSPSTAT<3>)
and sets SSPIF bit
FIGURE 9-11:BAUD RATE GENERATOR TIMING WITH CLOCK ARBITRATION
9.2.9I
2
C MASTER MODE START
CONDITION TIMING
To initiate a START condi tion, the user sets the START
condition enable bit, SEN (SSPCON2<0>). If the SDA
and SCL pins are samp led hig h, th e ba ud ra te generator is reloaded with the contents of SSPADD<6:0> and
starts it s c oun t. If SCL and SDA are bot h s ampl ed high
when the baud rate generator times out (T
BRG), the
SDA pin is driven low. The action of the SDA being
driven low while SCL is high is the START condition,
and causes the S bit (SSPSTAT<3>) to be set. Following this, the baud rate generator is reloaded with the
contents of SSPADD<6:0> and resumes its count.
When the baud rate generator times out (T
BRG), the
SEN bit (SSPCON2<0>) will be automatically cleared
by hardware. The baud rate generator is suspended,
leaving the SDA li ne held low, and the STAR T conditio n
is complete .
FIGURE 9-12:FIRST START BIT TIMING
Note:If, at the beginning of START condition, the
SDA and SCL pins are already sampled
low, or if during t he START condition the
SCL line is sampled low before the SDA
line is driven low, a bus collision occurs,
the Bus Collision Interrupt Flag (BCLIF) is
set, the START condition is aborted, and
2
C module is reset into its IDLE state.
the I
9.2.9.1WCOL Status Flag
If the user writes the SSPBUF when a START
sequence is in progress, then WCOL is set and the
contents of the bu ffe r are un chang ed (the w rite doe sn’t
occur).
Note:Because queueing of events is not
allowed, writing to the lower 5 bits of
SSPCON2 is disabled until the START
condition is complete .
DS30292D-page 80 1998-2013 Microchip Technology Inc.
PIC16F87X
SDA
SCL
Sr = Repeated START
Write to SSPCON2
Write to SSPBUF occurs here
Falling edge of ninth clock
End of Xmit
At completion of START bit,
hardware clears RSEN bit
A Repeated START condition occurs when the RSEN
bit (SSPCON2<1>) is programmed high and the I
module is in the IDLE state. When the RSEN bit is set,
the SCL pin is asserted low. When the SCL pin is sampled low, the baud rate generator is loaded with the
contents of SSPADD<6:0> and begins counting. The
SDA pin is released (brought high) for one baud rate
generator count (T
BRG). When the baud rate genera tor
times out, if SD A is sampl ed hi gh, th e SCL pin w ill be
de-asserted (brought high). When SCL is sampled high
the baud rate genera tor is reloaded w ith the conten ts of
SSPADD<6:0> and begins counting. SDA and SCL
must be sampled high for one T
BRG. This action is then
followed by assertion of the SDA pin (SDA is low) for
BRG, while SCL is high. Follo wing thi s, t he RSEN
one T
bit in the SSPCON2 register will be automatically
cleared and the baud rate generator will not be
reloaded, leaving the SDA pin held low. As soon as a
ST ART cond ition is det ected on the SDA and SCL p ins,
the S bit (SSPSTAT<3>) will be set. The SSPIF bit will
not be set until the ba ud rate generator has timed out.
Note 1: If RSEN is programmed while any other
event is in progress, it will not take effect.
2: A bus collision during the Repeated
START condition occurs if:
• SDA is sampled low wh en SCL
goes from low to high.
•SCL goes low before SDA is
asserted low . This may indicate that
another master is attempting to
transmit a data "1".
2
Immediately following the SSPIF bit getting set, the
user may write the SSPBUF with the 7-bit address in
7-bit mode, or the default first address in 10-bit mode.
After the first eight bits are transmitted and an ACK is
C
received, the use r may then transmi t an additional e ight
bits of address (1 0-bit mod e), or ei ght bi t s of dat a (7-b it
mode).
9.2.10.1WCOL Status Flag
If the user writes the SSPBUF when a Repeated
START sequence is in progress, then WCOL is set and
the contents of the buffer are unchanged (the write
doesn’t occur).
Note:Because queueing of events is not
allowed, writing of the lower 5 bits of
SSPCON2 is disabled until the Repeated
START condition is complete.
Transmission of a data byte, a 7-bit address, or either
half of a 10-bit address, is accomplished by simply writing a value to SSPBUF register. This action will set the
Buffer Full flag (BF) and allow the baud rate generator
to begin counting a nd star t the next trans mission. Eac h
bit of address/data will be shifted out onto the SDA pin
after the falling edg e of SCL is ass erte d (se e data hold
time spec). SCL i s held low for o ne baud rate gen erator
rollover count (T
is released high (see data setup time spec). When the
SCL pin is r eleased high, i t is hel d that w ay for T
The data on the SDA pin must remain stable for that
duration and some hold ti me after the next fallin g edg e
of SCL. After the eighth bit is shifted out (the falling
edge of the eighth c lock), the BF f lag is cl eared and th e
master releases SDA allowing the slave device being
addressed t o res p on d w ith an ACK
bit time, if an address match occurs or if data was
received properly. The status of ACK is read into the
ACKDT on the falling edge of the ninth clock. If the
master receives an Acknowledge, the Acknowledge
Status bit (ACKSTAT) is cleared. If not, the bit is set.
After the ninth clock, the SSPIF is set and the master
clock (baud rate gene rator ) is suspended until the next
data byte is loaded into the SSPBUF, leaving SCL low
and SDA unchanged (Figure 9-14).
After the write to the SSPBUF, each bit of address will
be shifted out on the fal ling edge of SC L, until all seve n
address bits and the R/W
ing edge of the eighth clock, the master will de-assert
the SDA pin, allowing the slave to respond with an
Acknowledge. On th e falling edge o f the ninth clock , the
master will sample the SDA pin to see if the address
was recognized by a slave. The status of the ACK bit is
loaded into the ACKSTAT status bit (SSPCON2<6>).
Following t he falli ng edge o f the ni nth clock transmis sion of the address, the SSPIF is set, the BF flag is
cleared, and the baud rate generator is turned off until
another write to the SSPBUF takes place, holdi ng SCL
low and allowing SDA to float.
BRG). Data should be valid before SCL
BRG.
bit during the ninth
bit are complet ed. On the fall-
9.2.11.1BF Status Flag
In Transmit mode, the BF bit (SSPSTAT<0>) is set
when the CPU writes to SSPBUF and is cleared when
all 8 bits are shifted out.
9.2.11.2WCOL Status Flag
If the user writes the SSPBUF when a transmit is
already in progress (i.e., SSPSR is still shifting out a
data byte), then WCOL is set and the contents of the
buffer are unchanged (the write doesn’t occur).
WCOL must be cleared in software.
9.2.11.3ACKSTAT Status Flag
In Transmit mod e, the ACKSTAT bit (SSPCON2<6>) is
cleared when the slave has sent an Acknowledge
(ACK = 0), and is set when the sl ave does not Acknow ledge (ACK
it has recognized its address (including a general call),
or when the slave has properly received its data.
= 1). A slave sends an Acknowledg e when
DS30292D-page 82 1998-2013 Microchip Technology Inc.
PIC16F87X
SDA
SCL
SSPIF
BF (SSPST AT<0>)
SEN
A7A6 A5A4 A3 A2 A1ACK = 0D7D6D5D4D3D2D1D0
ACK
Transmitting Data or Second Half
R/W
= 0Transmit Address to Slave
123456789123456789
P
Cleared in software service routine
SSPBUF is written in software
From SSP interrupt
After START condition SEN, cleared by hardware.
S
SSPBUF written with 7-bit address and R/W
start transmit
SCL held low
while CPU
responds to SSPIF
SEN = 0
of 10-bit address
Write SSPCON2<0> SEN = 1
START condition begins
From slave clear ACKSTAT bit SSPCON2<6>
ACKSTAT in
SSPCON2 = 1
Cleared in software
SSPBUF written
PEN
Cleared in software
R/W
FIGURE 9-14:I2C MASTER MODE TIMING (TRANSMISSION, 7 OR 10-BIT ADDRESS)
Master mode recepti on is enab led by pr ogrammin g the
Receive Enable bit, RCEN (SSPCON2<3>).
Note:The SSP module must be in a n IDL E st a te
before the RCEN bit is set, or the RCEN bit
will be disregarded.
The baud rate genera tor b egi ns cou nti ng, and on each
rollover, the state of the SCL pin changes (high to low/
low to high), and data is shifted into the SSPSR. After
the falling edge of the eighth clock, the receive enable
flag is automatically cleared, the contents of the
SSPSR are loaded into the SSPBUF, the BF flag is set,
the SSPIF is set, and the baud rate generator is suspended from counting, holding SCL low. The SSP is
now in IDLE state, awaiting the next command. When
the buffer is read by the CPU, the BF flag is automatically cleared. The us er can then s end an Acknowl edge
bit at the end of reception, by setting the Acknowledge
Sequence Enable bit, ACKEN (SSPCON2<4>).
9.2.12.1BF Status Flag
In receive operation, BF is set when an address or data
byte is loaded into SSPBUF from SSPSR. It is cleared
when SSPBUF is read.
9.2.12.2SSPOV Status Flag
In receive operation, SSPOV is set when 8 bits are
received into the SSPSR, and the BF flag i s already set
from a previous reception.
9.2.12.3WCOL Status Flag
If the user writes the SSPBUF when a receive is
already in progress (i.e., SSPSR i s still shifting in a dat a
byte), then WCOL is set and the contents of the buffer
are unchanged (the write doesn’t occur).
DS30292D-page 84 1998-2013 Microchip Technology Inc.
rate generator cou nts for T
pulled low. Following this, t he ACKEN bi t is au to mat ically cleared, the baud rate generator is turned off,
An Acknowledge sequence is enabled by setting the
Acknowledge Sequence Enable bit, ACKEN
(SSPCON2<4>). When this bit is set, the SCL pin is
pulled low and the content s of the Acknowledge dat a bit
is presented on the SD A pin . If t he user wishes to ge nerate an Acknowledge, the ACKDT bit should be
cleared. If not, the user should set the ACKDT bit
before starting an Acknowledge sequence. The baud
rate generator then counts for one rollover period
BRG), and the SCL pin is de-asserted high. When the
(T
and the SSP module then goes into IDLE mode
(Figure 9-16).
9.2.13.1WCOL Status Flag
If the user writes the SSPBUF when an Acknowledge
sequence is in progress , the WCOL is set and the contents of the buffer are unchanged (the write doesn’t
occur).
SCL pin is sampled high (clock arbitration), the baud
FIGURE 9-16:ACKNOWLEDGE SEQUENCE WAVEFORM
BRG. The SCL pin is t hen
DS30292D-page 86 1998-2013 Microchip Technology Inc.
PIC16F87X
SCL
SDA
SDA asserted low before rising edge of clock
Write to SSPCON2
Set PEN
Falling edge of
SCL = 1 for T
BRG, followed by SDA = 1 for TBRG
9th clock
SCL brought high after T
BRG
Note: TBRG = one baud rate generator period.
T
BRG
TBRG
after SDA sampled high. P bit (SSPSTAT<4>) is set.
T
BRG
to setup STOP condition
ACK
P
T
BRG
PEN bit (SSPCON2<2>) is cleared by
hardware and the SSPIF bit is set
9.2.14STOP CONDITION TIMING
A STOP bit is asserted on the SDA pin at the end of a
receive/t ransmi t by s etti ng th e Stop Sequen ce E nable
bit, PEN (SSPCON2<2>). At the end of a receive/
transmit, the SCL line is held low after the falling edge
of the ninth clock. When the PEN bit is set, the master
will assert the SDA line lo w . Whe n the SDA line is sampled low, the baud rate generator is reloaded and
counts down to 0. Wh en th e ba ud rat e ge nerator times
out, the SCL pin will be brought high, and one T
(baud rate generator rollover count) later, the SDA pin
will be de-asserted. Wh en the SDA pin is sam pled high
BRG
while SCL is high, the P bit (SSPSTAT<4>) is set. A
BRG later, the PEN bit is cleared and the SSPIF bit is
T
set (Figure 9-17).
Whenever the firmware decides to take control of the
bus, it will firs t dete rm ine if the bus is bu sy b y ch eck in g
the S and P bits in the SSPSTAT register. If the bus is
busy, then the CPU can be interrupted (notified) when
a STOP bit is detected (i.e., bus is free).
9.2.14.1WCOL Status Flag
If the user writes the SS PBUF when a ST OP se quence
is in progress, then WCOL is set and th e contents o f the
buffer are unchanged (the write doesn’t occur).
FIGURE 9-17:STOP CONDITION RECEIVE OR TRANSMIT MODE
Clock arbitration occurs when the master, during any
receive, transmit, or Repeated START/STOP condition, de-asserts th e SCL pin (SCL allowed to float high).
When the SCL pin is allowed to floa t high, the baud rate
9.2.16SLEEP OPERATIO N
While in SLEEP mode, the I2C module can receive
addresses or data, and when an address match or
complete byte transfer occurs, wake the processor
from SLEEP (if the SSP interrupt is enabled).
generator (BRG) is suspended from counting until the
SCL pin is actually sam ple d hi gh. W hen the SC L p in i s
sampled high, the baud rate gen erator is reloaded with
the contents of SSPADD<6:0> and begins counting.
This ensures that the SCL high time will always be at
9.2.17EFFECTS OF A RESET
A RESET disables the SSP module and terminates the
current tran sfer.
least one BRG rollover c ount in the e vent that the clock
is held low by an external device (Figure 9-18).
FIGURE 9-18:CLOCK ARBITRATION TIMING IN MASTER TRANSMIT MODE
DS30292D-page 88 1998-2013 Microchip Technology Inc.
PIC16F87X
SDA
SCL
BCLIF
SDA released
SDA line pulled low
by another source
Sample SDA. While SCL is high,
data doesn’t match what is driven
Bus collision has occurred.
Set bus collision
interrupt
by the master.
by master
Data changes
while SCL = 0
9.2.18MULTI -MASTER
COMMUNICATION,
BUS COLLISION, AND
BUS ARBITRATION
Multi-Master mode support is achieved by bus arbitration. When the master outputs address/data bits onto
the SDA pin, arbitration takes place when the master
outputs a '1' on SDA, by letting SDA float high and
another master asserts a ' 0'. Whe n th e SC L pi n fl oats
high, data should be stable. If the expected data on
SDA is a '1' and the data s ampl ed on the SD A pin = '0' ,
a bus collision has t ak en place. The master will set the
Bus Collision Interrupt Flag, BCLIF and reset the I
port to its IDLE state (Figure 9-19).
If a transmit was in progress when the bus collision
occurred, the transmission is halted, the BF flag is
cleared, the SDA and SCL lines are de-asserted, and
the SSPBUF can be w ritten t o. When the u ser se rvice s
the bus collision Interrupt Service Routine, and if the
2
C bus is free, the user can res ume commu nication b y
I
2
C
If a START, Repeated START, STOP, or Acknowledge
condition was in progress when the bus collision
occurred, t he condition is aborted, t he SDA and SCL
lines are de-assert ed, and t he respe ctiv e contro l bit s in
the SSPCON2 register are cleared. When the user services the bus collision Interrupt Service Routine, and if
2
C bus is free, the use r can resume communicatio n
the I
by asserting a START condition.
The master will continue to monitor the SDA and SCL
pins and if a STOP condition occurs, the SSPIF bit will
be set.
A write to the SSPBUF will start the transmission of
data at the first data bit, regardless of where the transmitter left off when the bus collision occurred.
In Multi-Master mode, the interrupt generation on the
detection of START and STOP conditions allows the
determination of whe n the bus is free. Con trol of the I
bus can be taken when the P bit is set in the SSPSTAT
register, or the bus is idle and the S and P bits are
cleared.
asserting a START conditio n.
FIGURE 9-19:BUS COLLISION TIMING FOR TRANSMIT AND ACKNOWLEDGE
SEN cleared automatically because of bus collision.
S bit and SSPIF set because
Set SEN, enable START
condition if SDA = 1, SCL = 1
SDA = 0, SCL = 1.
BCLIF
S
SSPIF
SDA = 0, SCL = 1.
SSPIF and BCLIF are
cleared in software
SSPIF and BCLIF are
cleared in software
Set BCLIF,
Set BCLIF.
START condition.
9.2.18.1Bus Collision During a START
Condition
During a START condition, a bus collision occurs if:
a)SDA or SCL are s ampled low a t the beginning of
the START condition (Figure 9-20).
b)SCL is sampl ed l ow be fore SD A is as se rted low
(Figure 9-21).
During a START condition, both the SDA and the SCL
pins are monitored. If e ither the SDA pi n or
is already low, then these events all occur:
• the START condition is aborted,
•and
the BCLIF flag is set,
•and the SSP module is reset to its IDLE state
(Figure 9-20).
The START condition begins with the SDA and SCL
pins de-asserted. When the SDA pin is sampled high,
the baud rate generator is loaded from SSPADD<6:0>
and counts down to 0. If the SCL pin is sampled low
while SDA is high, a bus collision occurs, because it is
assumed that another master is attempting to drive a
the SCL pin
If the SDA pin is sampled low during this count, the
BRG is reset and the SDA line is asserted early
(Figure 9-22). If, however, a '1' is sampled on the SDA
pin, the SDA pin is assert ed low at the end of the BRG
count. The baud rate generator is then reloaded and
counts down to 0. During this time, if the SCL pins are
sampled as '0', a bus collision does not occur. At the
end of the BRG count, the SCL pin is asserted low.
Note:The reason that bus coll ision is no t a fact or
during a START condition is that no two
bus masters can assert a START condition
at the exact same time. Therefore, one
master will always assert SDA before the
other . T his con dition does not cause a bus
collision, becau se the two master s must be
allowed to arbitrate t he first add ress following the START condition. If the address is
the same, arbitration must be allowed to
continue into the data portion, Repeated
START, or STOP conditions.
data '1' during the START condition.
FIGURE 9-20:BUS COLLISION DURING START CONDITION (SDA ONLY)
DS30292D-page 90 1998-2013 Microchip Technology Inc.
PIC16F87X
SDA
SCL
SEN
Bus collision occurs, Set BCLIF
SCL = 0 before SDA = 0,
Set SEN, enable START
sequence if SDA = 1, SCL = 1
TBRG
TBRG
SDA = 0, SCL = 1
BCLIF
S
SSPIF
Interrupts cleared
in software
Bus collision occurs, Set BCLIF
SCL = 0 before BRG time-out,
'0'
'0'
'0'
'0'
SDA
SCL
SEN
Set S
Set SEN, enable START
sequence if SDA = 1, SCL = 1
Less than T
BRG
TBRG
SDA = 0, SCL = 1
BCLIF
S
SSPIF
s
Interrupts cleared
in software
Set SSPIF
SDA = 0, SCL = 1
SDA pulled low by other master.
Reset BRG and assert SDA.
SCL pulled low after BRG
Time-out
Set SSPIF
'0'
FIGURE 9-21:BUS COLLISION DURING START CONDITION (SCL = 0)
FIGURE 9-22:BRG RESET DUE TO SDA COLLISION DURING START CONDITION
Sample SDA when SCL goes high.
If SDA = 0, set BCLIF and release SDA and SCL.
Cleared in software
'0'
'0'
'0'
'0'
SDA
SCL
BCLIF
RSEN
S
SSPIF
Interrupt cleared
in software
SCL goes low before SDA,
Set BCLIF. Release SDA and SCL.
TBRGTBRG
'0'
'0'
'0'
'0'
9.2.18.2Bus Collision During a Repeated
ST ART Condition
During a Repeated START condition, a bus collision
occurs if:
a)A low level is sampled on SDA when SCL goes
from low level to high level.
b)SCL goes low before SDA is asserted low, indi-
cating that anoth er master is attem pting to transmit a data ’1’.
When the user de-asserts SDA and the pin is allowed
to float high, the BRG is loaded with SSPADD<6:0>
and counts down to 0. The SCL pin is then de-asserted,
and when sampled high, the SDA pin is sampled. If
SDA is low, a bus collision has occurred (i.e., another
SDA is sampled high, the BRG is reloaded and begins
counting. If SDA goes from high to low befo re the BRG
times out, no bus collision occurs, because no two
masters can assert SDA at exactly the same time.
If, however , SCL goes from hig h to low before the BRG
times out and SDA has not already been asserted, a
bus collision occurs. In this case, another master is
attempting to transmit a data’1’ during the Repeated
START condition.
If at the end of the BRG time-out, both SCL and SDA
are still high, the SDA pin is driven low, the BRG is
reloaded and begins counting. At the end of the count,
regardless of the status of the SCL pin, the SCL pin is
driven low and the Repeated START condition is
complete (Figure 9-23).
master is attempting to transmit a data’0’). If, however,
FIGURE 9-23:BUS COLLISION DURING A REPEATED START CONDITION (CASE 1)
FIGURE 9-24:BUS COLLISION DURING REPEATED START CONDITION (CASE 2)
DS30292D-page 92 1998-2013 Microchip Technology Inc.
PIC16F87X
SDA
SCL
BCLIF
PEN
P
SSPIF
TBRGTBRGTBRG
SDA asserted low
SDA sampled
low after T
BRG,
Set BCLIF
'0'
'0'
'0'
'0'
SDA
SCL
BCLIF
PEN
P
SSPIF
TBRGTBRGTBRG
Assert SDA
SCL goes low before SDA goes high,
Set BCLIF
'0'
'0'
9.2.18.3Bus Collision During a STOP
Condition
Bus collision occurs during a STOP condition if:
a)After the SDA pin has been de-asserted and
allowed to float high, SDA is sampled low after
the BRG has timed out.
b)After the SCL pin is de-asserted, SCL is sam-
pled low before SDA goes high.
The STOP condition begins with SDA asserted low.
When SDA is sampled low, the SCL pin is allowed to
float. When th e pin i s sa mple d hi gh (c loc k ar bit rati on) ,
the baud rate generator is loaded with SSPADD<6:0>
and counts down to 0. After the BRG times o ut, SDA i s
sampled. If SDA is sampled low, a bus collision has
occurred. This is due to another master attempting to
drive a data ' 0'. If the SCL pin is sample d low before
SDA is allowed to float hi gh, a bus collis ion occurs. Thi s
is a case of another master attempting to drive a data
'0' (Figure 9-25).
FIGURE 9-25:BUS COLLISION DURING A STOP CONDITION (CASE 1)
FIGURE 9-26: BUS COLLISION DURING A STOP CONDITION (CASE 2)
Note: I2C devices with input levels related to VDD must have one com mon supply line to which the pull-up resistor is also
connected.
9.3Connection Considerations for
2
I
C Bus
For standard-mode I2C bus devices, the values of
resistors R
lowing parameters:
• Supply voltage
• Bus capacitance
• Number of connected devices
(input current + leakage current)
The supply voltage limits the minimum value of resistor
due to the specified minimum sink current of 3 mA at
R
p,
OL max = 0.4V, for the specified output stages.
V
and Rs in Figure 9-27 depend on the fol-
p
For
example, with a supply voltage of V
OL max = 0.4V at 3 mA, R
V
V
DD as a function of R
desired noise margin of 0.1V
the maximum value of R
and used to improve ESD susceptibility.
The bus capacitance is the total capacitance of wire,
connections, an d pins. This capaci tance lim its the m aximum value of R
due to the specified rise time
p
(Figure 9-27).
The SMP bit is the slew rate control enabled bit. This bit
is in the SSPSTAT register, and controls the slew rate
of the I/O pins when in I
FIGURE 9-27:SAMPL E DEVICE CONFIGURATION FOR I2C BUS
DD = 5V±10% and
min = (5.5-0.4)/0.003 = 1.7 k
p
is shown i n Figure 9-27. The
p
DD for the low level limits
. Series resistors are optional
s
2
C mode (master or slave).
DS30292D-page 94 1998-2013 Microchip Technology Inc.
PIC16F87X
10.0ADDRESSABLE UNIVERSAL
SYNCHRONOUS
ASYNCHRONOUS RECEIVER
T RANSMITTER (USART)
The Universal Synchronous Asynchronous Receiver
Transmitter (USART) module is one of the two serial
I/O modules . (USA RT is als o know n as a S erial Communications Interface or SCI.) The USART can be configured as a full duplex asynchronous system that can
communicate with pe ripheral devi ces s uch as CR T terminals and perso nal comp uters, or it can be configure d
as a half duplex s yn chronous system th at c an co mm unicate with periphera l de vi ces su ch as A/ D or D /A in tegrated circuits, serial EEPROMs etc.
The USART can be configured in the following modes:
• Asynchronous (full duplex)
• Synchronous - Master (half duplex)
• Synchronous - Slave (half duplex)
Bit SPEN (RCSTA<7>) and bits TRISC<7:6> have to
be set in order to configure pins RC6/TX/CK and
RC7/RX/DT as the Universal Synchronous Asynchronous Receiver Transmitter.
The USART module also has a multi-processor communication capability using 9-bit address detection.
REGISTER 10-1:TXSTA: T RANSMIT STATUS AND CONTROL REGISTER (ADDRESS 98h)
1 = Enables continuous receive until enable bit CREN is cleared (CREN overrides SREN)
0 = Disables co ntinuous receive
bit 3ADDEN: Address Detect Enable bit
Asynchronous mode 9-bit (RX9 = 1):
1 = Enables address detection, enables interrupt and load of the receive buffer when
RSR<8> is set
0 = Disables address detection, all bytes are received, and ninth bit can be used as parity bit
bit 2FERR: Framing Error bit
1 = Framing error (can be updated by reading RCREG register and receive next valid byte)
0 = No framing error
bit 1OERR: Overrun Error bit
1 = Overrun error (can be cleared by clearing bit CREN)
0 = No overrun error
bit 0RX9D: 9th bit of Received Data (can be parity bit, but must be calculated by user firmware)
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
DS30292D-page 96 1998-2013 Microchip Technology Inc.
PIC16F87X
10.1USART Baud Rate Generator
(BRG)
The BRG supports both the Asynchronous and Synchronous modes of the USART. It is a dedicated 8-bit
baud rate generator. The SPBRG register controls the
period of a free running 8-bit timer. In Asynchronous
mode, bit BRGH (TXSTA<2>) also controls the baud
rate. In Synchronous mode, bit BRGH is ignored.
Table 10-1 shows the formula for computation of the
baud rate for differen t US ART modes which only a ppl y
in Master mode (internal clock).
Given the desired baud rate and F
integer value for the SPBRG register can be calculated
OSC, the nearest
It may be advantageous to use the high baud rate
(BRGH = 1), even for slower baud clocks. This is
because the FOSC/(16(X + 1)) equation c an red uce the
baud rate error in some cases.
Writing a new value to the SPBRG register causes the
BRG timer to be reset (or cleared). This ensures the
BRG does not wait for a timer overflow before outputting the new baud rate.
10.1.1SAMPLING
The data on the RC7/RX/D T pin is sampled three times
by a majority detect circuit to determine if a high or a
low level is present at the RX pin.
using the formula in Table 10-1. From this, the error in
baud rate can be determined.
TABLE 10-1:BAUD RATE FORMULA
SYNCBRGH = 0 (Low Speed)BRGH = 1 (High Speed)
0
1
X = value in SPBRG (0 to 255)
(Asynchronous) Baud R ate = F
(Synchronous) Baud Rate = F
OSC/(64(X+1))
OSC/(4(X+1))
Baud Rate = F
N/A
OSC/(16(X+1))
TABLE 10-2:REGISTERS ASSOCIATED WITH BAUD RATE GENERATOR
98hTXSTA
18hRCSTASPEN
99hSPBRGBaud Rate Generator Register0000 00000000 0000
Legend: x = unknown, - = unimplemented, read as '0'. Shaded cells are not used by the BRG.
TABLE 10-3:BAUD RATES FOR ASYNCHRONOUS MODE (BRGH = 0)
OSC = 20 MHzFOSC = 16 MHzFOSC = 10 MHz
BAUD
RATE
(K)
0.3------- --
1.21.2211.752551.2020.172071.2020.17129
2.42.4040.171292.4040.171032.4040.1764
9.6 9.7661.73319.6150.16259.7661.7315
19.219.531 1.721519.2310.161219.5311.727
28.831.2508.51927.7783.55831.2508.514
33.634.7223.34835.7146.29631.2506.994
57.662.5008.51462.5008.51352.0839.582
HIGH1.221-2550.977-2550.610-255
LOW 312.500-0250.000-0156.250-0
BAUD
RATE
(K)
0.30.30002070.30191
1.21.2020.17511.2047
2.42.4040.17252.4023
9.6 8.9296.9969.605
19.220.8338.51219.202
28.831.2508.51128.801
33.6------
57.662.5008.51057.600
HIGH0.244-2550.225-255
LOW 62.500-057.6-0
F
KBAUD%ERROR
OSC = 4 MHzFOSC = 3.6864 MHz
F
%
KBAUD
ERROR
SPBRG
value
(decimal)
SPBRG
value
(decimal)KBAUD
KBAUD%ERROR
%
ERROR
SPBRG
value
(decimal)
SPBRG
value
(decimal)
KBAUD%ERROR
SPBRG
value
(decimal)
TABLE 10-4:BAUD RATES FOR ASYNCHRONOUS MODE (BRGH = 1)
OSC = 20 MHzFOSC = 16 MHzFOSC = 10 MHz
BAUD
RATE
(K)
0.3---------
1.2---------
2.4------2.4411.71255
9.6 9.6150.161299.6150.161039.6150.1664
19.219.2310.166419.2310.165119.5311.7231
28.829.0700.944229.4122.133328.4091.3621
33.633.7840.553633.3330.792932.8952.1018
57.659.5243.342058.8242.131656.8181.3610
HIGH4.883-2553.906-2552.441-255
LOW 1250.000-01000.0000625.000-0
BAUD
RATE
(K)
0.3------
1.21.2020.172071.20191
2.42.4040.171032.4095
9.6 9.6150.16259.6023
19.219.2310.161219.2011
28.827.7983.55828.807
33.635.7146.29632.92.046
57.662.5008.51357.603
HIGH0.977-2550.9-255
LOW 250.000-0230.4-0
F
KBAUD%ERROR
OSC = 4 MHzFOSC = 3.6864 MHz
F
%
KBAUD
ERROR
SPBRG
value
(decimal)
SPBRG
value
(decimal)KBAUD
KBAUD%ERROR
%
ERROR
SPBRG
value
(decimal)
SPBRG
value
(decimal)
KBAUD%ERROR
SPBRG
value
(decimal)
DS30292D-page 98 1998-2013 Microchip Technology Inc.
PIC16F87X
TXIF
TXIE
Interrupt
TXEN
Baud Rate CLK
SPBRG
Baud Rate Generator
TX9D
MSb
LSb
Data Bus
TXREG Register
TSR Register
(8)
0
TX9
TRMT
SPEN
RC6/TX/CK pin
Pin Buffer
and Control
8
10.2USART Asynchronous Mode
In this mode, the USART uses standard non-return-tozero (NRZ) format (one START bit, eight or nine data
bits, and one STOP bit). The most common data format
is 8-bits. An on-chip, dedicated, 8-bit baud rate generator can be used to derive standard baud rate fre quencies from the oscillator. The USART transmits and
receives the LSb fi rst. The t r ans mitte r and receiver are
functionally indep endent, b ut use th e same data f ormat
and baud rate. The baud rate generator produces a
clock, either x16 or x64 of the bit shift rate, depending
on bit BRGH (TXSTA<2>). Parity is not supported by
the hardware, but can b e implemented i n softwa re (and
stored as the ninth data bit). Asynchronous mode is
stopped during SLEEP.
Asynchronous mode is selected by clearing bit SYNC
(TXSTA<4>).
The USART Asynchronous module consists of the following important elements:
• Baud Rate Generator
• Sampling Circuit
• Asynchronous Transmitter
• Asynchronous Receiver
10.2.1USART ASYNCHRONOUS
TRANSMITTER
The USART transmitter block diagram is shown in
Figure 10-1. The heart of t he trans mitte r is the t ransm it
(serial) shift register (TSR). The shif t register obt ains its
data from the read/write transmit buffer, TXREG. The
TXREG register is loaded with data in software. The
TSR register is not loaded until the STOP bit has been
transmitted from the previous load. As soon as the
STOP bit is transmitted, the TSR is loaded with new
data from the TXREG register (if available). Once the
TXREG register transfers the data to the TSR register
(occurs in one T
flag bit TXIF (PIR1<4>) is set. This interrupt can be
CY), the TXR EG re gist er i s em pty and
enabled/disabled by setting/clearing enable bit TXIE
( PIE1<4>). Flag bit TXIF will be set, regardless of the
state of enabl e bit TX IE an d cann ot be cl ear ed in software. It will reset only wh en ne w dat a is loa ded i nto th e
TXREG register . While flag bi t TXIF indicates the status
of the TXREG register, another bit TRMT (TXSTA<1>)
shows the status of the TSR register. Status bit TRMT
is a read only bi t, wh ic h i s se t w he n the TSR r egister is
empty. No interrupt logic is tied to this bit, so the user
has to poll this bit in order to determine if the TSR register is empty.
Note 1: The TSR register is not mapped in data
memory, so it is not available to the user.
2: Flag bit TXIF is set when enabl e bit TXEN
is set. TXIF is cleared by loadi ng TXRE G.
Transmission is enabled by setting enable bit TXEN
(TXSTA<5>). The actual transmission will not occur
until the TXREG register has been loaded with data
and the baud rate generator (BRG) has produced a
shift clock (Figure 10-2). The transmission can also be
started by first loading the TXREG register and then
setting enable bit TXEN. Normally, when transmission
is first started, the TSR register is empty. At that point,
transfer to the TXREG register will result in an immediate transfe r to TSR, result ing in an empty TXR EG. A
back-to-back transfer is thus possible (Figure 10-3).
Clearing enable bit TXEN during a transmission will
cause the transmis s ion to be ab orte d a nd will reset the
transmitter. As a result, the RC6/TX/CK pin will revert
to hi-impedance.
In order to select 9-bit transmission, transmit bit TX9
(TXSTA<6>) should be set and the ninth bit should be
written to TX9D (TXSTA<0>). The ninth bit must be
written before writing the 8-bit data to the TXREG register. This is because a data write to the TXREG register can result in an immediate tra nsfer of the dat a to the
TSR register (if the TSR is empty). In such a case, an
incorrect ninth data bit may be loaded in the TSR
register.