PIC18F2XXX/4XXX FAMILY
DS30009622M-page 46 2010-2015 Microchip Technology Inc.
EBTR0 CONFIG7L Table Read Protection bit (Block 0 code memory area)
1 = Block 0 is not protected from Table Reads executed in other blocks
0 = Block 0 is protected from Table Reads executed in other blocks
EBTRB CONFIG7H Table Read Protection bit (Boot Block memory area)
1 = Boot Block is not protected from Table Reads executed in other blocks
0 = Boot Block is protected from Table Reads executed in other blocks
DEV<10:3> DEVID2 Device ID bits
These bits are used with the DEV<2:0> bits in the DEVID1 register to identify
part number.
DEV<2:0> DEVID1 Device ID bits
These bits are used with the DEV<10:3> bits in the DEVID2 register to identify
part number.
REV<4:0> DEVID1 Revision ID bits
These bits are used to indicate the revision of the device. The REV4 bit is
sometimes used to fully specify the device type.
TABLE 5-3: PIC18F2XXX/4XXX FAMILY BIT DESCRIPTIONS (CONTINUED)
Bit Name
Configuration
Words
Description
Note 1: The BBSIZ bits, BBSIZ<1:0> and BBSIZ<2:1> bits, cannot be changed once any of the following
code-protect bits are enabled: CPB or CP0, WRTB or WRT0, EBTRB or EBTR0.
2: Not available in PIC18FXX8X and PIC18F2450/4450 devices.
2010-2015 Microchip Technology Inc. DS30009622M-page 47
PIC18F2XXX/4XXX FAMILY
5.3 Single-Supply ICSP Programming
The LVP bit in Configuration register, CONFIG4L, enables Single-Supply (Low-Voltage) ICSP Programming. The LVP
bit defaults to a ‘1’ (enabled) from the factory.
If Single-Supply Programming mode is not used, the LVP bit can be programmed to a ‘0’ and RB5/PGM becomes a digital
I/O pin. However, the LVP bit may only be programmed by entering the High-Voltage ICSP mode, where MCLR
/VPP/RE3
is raised to V
IHH. Once the LVP bit is programmed to a ‘0’, only the High-Voltage ICSP mode is available and only the
High-Voltage ICSP mode can be used to program the device.
5.4 Embedding Configuration Word Information in the HEX File
To allow portability of code, a PIC18F2XXX/4XXX Family programmer is required to read the Configuration Word
locations from the hex file. If Configuration Word information is not present in the hex file, then a simple warning
message should be issued. Similarly, while saving a hex file, all Configuration Word information must be included. An
option to not include the Configuration Word information may be provided. When embedding Configuration Word
information in the hex file, it should start at address, 300000h.
Microchip Technology Inc. feels strongly that this feature is important for the benefit of the end customer.
5.5 Embedding Data EEPROM Information In the HEX File
To allow portability of code, a PIC18F2XXX/4XXX Family programmer is required to read the data EEPROM
information from the hex file. If data EEPROM information is not present, a simple warning message should be issued.
Similarly, when saving a hex file, all data EEPROM information must be included. An option to not include the data
EEPROM information may be provided. When embedding data EEPROM information in the hex file, it should start at
address, F00000h.
Microchip Technology Inc. believes that this feature is important for the benefit of the end customer.
5.6 Checksum Computation
The checksum is calculated by summing the following:
The contents of all code memory locations
The Configuration Words, appropriately masked
ID locations (if any block is code-protected)
The Least Significant 16 bits of this sum is the checksum. The contents of the data EEPROM are not used.
5.6.1 PROGRAM MEMORY
When program memory contents are summed, each 16-bit word is added to the checksum. The contents of program
memory, from 000000h to the end of the last program memory block, are used for this calculation. Overflows from bit
15 may be ignored.
5.6.2 CONFIGURATION WORDS
For checksum calculations, unimplemented bits in Configuration Words should be ignored as such bits always read
back as ‘1’s. Each 8-bit Configuration Word is ANDed with a corresponding mask to prevent unused bits from affecting
checksum calculations.
The mask contains a ‘0’ in unimplemented bit positions, or a 1’ where a choice can be made. When ANDed with the
value read out of a Configuration Word, only implemented bits remain. A list of suitable masks is provided in Table 5-5.
Note 1: The High-Voltage ICSP mode is always available, regardless of the state of the LVP bit, by applying
V
IHH to the MCLR/VPP/RE3 pin.
2: While in Low-Voltage ICSP mode, the RB5 pin can no longer be used as a general purpose I/O.
PIC18F2XXX/4XXX FAMILY
DS30009622M-page 48 2010-2015 Microchip Technology Inc.
5.6.3 ID LOCATIONS
Normally, the contents of these locations are defined by the user, but MPLAB
®
IDE provides the option of writing the
device’s unprotected 16-bit checksum in the 16 Most Significant bits of the ID locations (see MPLAB IDE Configure/ID
Memory” menu). The lower 16 bits are not used and remain clear. This is the sum of all program memory contents and
Configuration Words (appropriately masked) before any code protection is enabled.
If the user elects to define the contents of the ID locations, nothing about protected blocks can be known. If the user
uses the preprotected checksum, provided by MPLAB IDE, an indirect characteristic of the programmed code is
provided.
5.6.4 CODE PROTECTION
Blocks that are code-protected read back as all ‘0’s and have no effect on checksum calculations. If any block is
code-protected, then the contents of the ID locations are included in the checksum calculation.
All Configuration Words and the ID locations can always be read out normally, even when the device is fully
code-protected. Checking the code protection settings in Configuration Words can direct which, if any, of the program
memory blocks can be read, and if the ID locations should be used for checksum calculations.

PIC18F2510T-I/SO

Mfr. #:
Manufacturer:
Microchip Technology
Description:
8-bit Microcontrollers - MCU 32KB 1536 RAM 25I/O
Lifecycle:
New from this manufacturer.
Delivery:
DHL FedEx Ups TNT EMS
Payment:
T/T Paypal Visa MoneyGram Western Union