PIC18F4431-E/ML Microchip Technology, PIC18F4431-E/ML Datasheet - Page 33

• Manufacturer Part Number: PIC18F4431-E/ML
• Description: IC MCU FLASH 8KX16 44QFN
• Manufacturer: Microchip Technology
• Series: PIC® 18Fr

Specifications of PIC18F4431-E/ML

• Core Processor: PIC
• Core Size: 8-Bit
• Speed: 40MHz
• Connectivity: I²C, SPI, UART/USART
• Peripherals: Brown-out Detect/Reset, LVD, Power Control PWM, QEI, POR, PWM, WDT
• Number Of I /o: 36
• Program Memory Size: 16KB (8K x 16)
• Program Memory Type: FLASH
• Eeprom Size: 256 x 8
• Ram Size: 768 x 8
• Voltage - Supply (vcc/vdd): 4.2 V ~ 5.5 V
• Data Converters: A/D 9x10b
• Oscillator Type: Internal
• Operating Temperature: -40°C ~ 125°C
• Package / Case: 44-QFN
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant

5.4
To allow portability of code, a PIC18FXX31 program-
mer 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 mes-
sage 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.
 2010 Microchip Technology Inc.
Embedding Configuration Word
Information in the HEX File
PIC18F2331/2431/4331/4431
5.5
The checksum is calculated by summing the following:
• The contents of all code memory locations
• The configuration word, appropriately masked
• ID locations
The Least Significant 16 bits of this sum are the
checksum.
Table 5-5 (pages 34 through 36) describes how to
calculate the checksum for each device.
Note 1: The checksum calculation differs depend-
Checksum Computation
ing on the code protect setting. Since the
code memory locations read out differ-
ently depending on the code protect set-
ting,
manipulate the actual code memory val-
ues to simulate the values that would be
read from a protected device. When cal-
culating a checksum by reading a device,
the entire code memory can simply be
read and summed. The configuration
word and ID locations can always be
read.
the
table
describes
DS30500B-page 33
how
to