PIC12HV615-I/SN Microchip Technology, PIC12HV615-I/SN Datasheet - Page 21

• Manufacturer Part Number: PIC12HV615-I/SN
• Description: IC PIC MCU FLASH 1KX14 8SOIC
• Manufacturer: Microchip Technology
• Series: PIC® 12Fr

Specifications of PIC12HV615-I/SN

• Program Memory Type: FLASH
• Program Memory Size: 1.75KB (1K x 14)
• Package / Case: 8-SOIC (3.9mm Width)
• Core Processor: PIC
• Core Size: 8-Bit
• Speed: 20MHz
• Peripherals: Brown-out Detect/Reset, POR, PWM, WDT
• Number Of I /o: 5
• Ram Size: 64 x 8
• Voltage - Supply (vcc/vdd): 2 V ~ 5 V
• Data Converters: A/D 4x10b
• Oscillator Type: Internal
• Operating Temperature: -40°C ~ 85°C
• Processor Series: PIC12H
• Core: PIC
• Data Bus Width: 8 bit
• Data Ram Size: 64 B
• Interface Type: RS-232/USB
• Maximum Clock Frequency: 20 MHz
• Number Of Programmable I/os: 5
• Number Of Timers: 3
• 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
• Minimum Operating Temperature: - 40 C
• On-chip Adc: 4-ch x 10-bit
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• For Use With: AC162083 - HEADER MPLAB ICD2 PIC16F616 8/14
• Eeprom Size: -
• Connectivity: -
• Lead Free Status / Rohs Status: Lead free / RoHS Compliant

6.0
For PIC12F609/12F615/12F617/16F610/16F616 and
PIC12HV609/12HV615/16HV610/16HV616, once the
CP bit is programmed to ‘0’, all program memory locations
read all ‘0’s. The user ID locations and the Configuration
Word read out in an unprotected fashion. Further
programming is disabled for the entire program memory.
The user ID locations and the Configuration Word can
be programmed regardless of the state of the CP bit.
6.1
It is recommended to use the procedure in Figure 4-15
to disable code protection of the device. This sequence
will erase the program memory, Configuration Word
(0x2007) and user ID locations (0x2000-0x2003). The
Calibration Word (0x2008) will not be erased.
6.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.
Microchip Technology Incorporated feels strongly that
this feature is important for the benefit of the end
customer.
 2009 Microchip Technology Inc.
PIC12F609/12F615/12F617/16F610/16F616 AND PIC12HV609/12HV615/16HV610/16HV616
CODE PROTECTION
Disabling Code Protection
Embedding Configuration Word
and User ID Information in the Hex
File
6.3
6.3.1
Checksum is calculated by reading the contents of the
program memory locations and adding up the opcodes
up to the maximum user addressable location (e.g.,
0x7FF for the PIC16F616). Any carry bits exceeding 16
bits are neglected. Finally, the Configuration Word
(appropriately masked) is added to the checksum. The
checksum computation for the PIC12F609/12F615/
12F617/16F610/16F616 and PIC12HV609/12HV615/
16HV610/16HV616 devices is shown in Table 6-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.
Table 6-1 describes how to calculate the checksum for
each device. Note that the checksum calculation differs
depending on the code-protect setting. Since the
program memory locations read out 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 calculat-
ing 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 code-protect setting.
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.
DS41396A-page 21