PIC16F913-I/SO Microchip Technology, PIC16F913-I/SO Datasheet - Page 29

• Manufacturer Part Number: PIC16F913-I/SO
• Description: IC PIC MCU FLASH 4KX14 28SOIC
• Manufacturer: Microchip Technology
• Series: PIC® 16Fr

Specifications of PIC16F913-I/SO

• Program Memory Type: FLASH
• Program Memory Size: 7KB (4K x 14)
• Package / Case: 28-SOIC (7.5mm Width)
• Core Processor: PIC
• Core Size: 8-Bit
• Speed: 20MHz
• Connectivity: I²C, SPI, UART/USART
• Peripherals: Brown-out Detect/Reset, LCD, POR, PWM, WDT
• Number Of I /o: 24
• Eeprom Size: 256 x 8
• Ram Size: 256 x 8
• Voltage - Supply (vcc/vdd): 2 V ~ 5.5 V
• Data Converters: A/D 5x10b
• Oscillator Type: Internal
• Operating Temperature: -40°C ~ 85°C
• Processor Series: PIC16F
• Core: PIC
• Data Bus Width: 8 bit
• Data Ram Size: 256 B
• Interface Type: SSP/I2C/AUSART/SPI
• Maximum Clock Frequency: 20 MHz
• Number Of Programmable I/os: 24
• Number Of Timers: 3
• Operating Supply Voltage: 2 V to 5.5 V
• Maximum Operating Temperature: + 85 C
• Mounting Style: SMD/SMT
• 3rd Party Development Tools: 52715-96, 52716-328, 52717-734
• Development Tools By Supplier: PG164130, DV164035, DV244005, DV164005, PG164120, ICE2000, DV164120
• Minimum Operating Temperature: - 40 C
• On-chip Adc: 5-ch x 10-bit
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• For Use With: XLT28SO-1 - SOCKET TRANSITION 28SOIC 300MIL
• Lead Free Status / Rohs Status: Lead free / RoHS Compliant

5.0
For PIC16F91X/946, once the CP bit is programmed to
‘0’, all program memory locations read all ‘0’s. Further
programming is disabled for the entire program memory.
Data memory is protected with its own Code-Protect bit
(CPD). When enabled, the data memory can still be
programmed and read using the EECON1 register
(See the applicable data sheet for more information).
The user ID locations and the Configuration Word can
be programmed and read out regardless of the state of
the CP and CPD bits.
5.1
It is recommended to use the procedure in Figure 3-21
to disable code protection of the device. This sequence
will erase the program memory, data memory, Configu-
ration Word (0x2007) and user ID locations (0x2000-
0x2003). The Calibration Words (0x2008-0x2009) will
not be erased.
5.2
To allow portability of code, the programmer is required
to read the Configuration Word and user ID locations
from the hex file when loading the hex file. If Configura-
tion Word information was not present in the hex file, a
simple warning message may be issued. Similarly,
while saving a hex file, Configuration Word and user ID
information must be included. An option to not include
this information may be provided.
Specifically for the PIC16F91X/946, the data memory
should also be embedded in the hex file (see
Section 5.3.2 “Embedding Data Memory Contents
In Hex File”).
Microchip Technology Incorporated feels strongly that
this feature is important for the benefit of the end
customer.
© 2009 Microchip Technology Inc.
Note:
CODE PROTECTION
Disabling Code Protection
Embedding Configuration Word
and User ID Information in the Hex
File
To ensure system security, if CPD bit = 0,
Bulk Erase Program Memory command
will also erase data memory.
5.3
5.3.1
Checksum is calculated by reading the contents of the
PIC16F91X/946 memory locations and adding up the
opcodes up to the maximum user addressable location,
(e.g., 0x1FFF for PIC16F917). Any carry bits exceed-
ing 16 bits are neglected. Finally, the Configuration
Word (appropriately masked) is added to the check-
sum. Checksum computation for the PIC16F91X/946
devices is shown in Table 5-1.
The checksum is calculated by summing the following:
• The contents of all program memory locations
• The Configuration Word, appropriately masked
• Masked user ID locations (when applicable)
The Least Significant 16 bits of this sum is the
checksum.
The following table describes how to calculate the
checksum for each device. Note that the checksum
zeroes when code-protected, the table describes how
to manipulate the actual program memory values to
simulate values that would be read from a protected
device. When calculating a checksum by reading a
device, the entire program memory can simply be
read and summed. The Configuration Word and user
ID locations can always be read regardless of the
code-protect setting.
calculation differs depending on the code-protect
setting. Since the program memory locations read out
Note:
Checksum Computation
CHECKSUM
Some older devices have an additional
value added in the checksum. This is to
maintain compatibility with older device
programmer checksums.
PIC16F91X/946
DS41244F-page 29