PIC18F13K50-I/P Microchip Technology, PIC18F13K50-I/P Datasheet - Page 32
![IC PIC MCU FLASH 4KX16 20-PDIP](/photos/12/13/121303/150-20-dip_sml.jpg)
PIC18F13K50-I/P
Manufacturer Part Number
PIC18F13K50-I/P
Description
IC PIC MCU FLASH 4KX16 20-PDIP
Manufacturer
Microchip Technology
Series
PIC® XLP™ 18Fr
Datasheets
1.PIC18F13K50-ISS.pdf
(420 pages)
2.PIC18F13K50-ISS.pdf
(40 pages)
3.PIC18F13K50-ISS.pdf
(10 pages)
4.PIC18F13K50-ISS.pdf
(2 pages)
5.PIC18F14K50-IP.pdf
(422 pages)
Specifications of PIC18F13K50-I/P
Program Memory Type
FLASH
Program Memory Size
8KB (4K x 16)
Package / Case
20-DIP (0.300", 7.62mm)
Core Processor
PIC
Core Size
8-Bit
Speed
48MHz
Connectivity
I²C, SPI, UART/USART, USB
Peripherals
Brown-out Detect/Reset, POR, PWM, WDT
Number Of I /o
14
Eeprom Size
256 x 8
Ram Size
512 x 8
Voltage - Supply (vcc/vdd)
1.8 V ~ 5.5 V
Data Converters
A/D 11x10b
Oscillator Type
Internal
Operating Temperature
-40°C ~ 85°C
Processor Series
PIC18F
Core
PIC
Data Bus Width
8 bit
Data Ram Size
512 B
Interface Type
EUSART/I2C/MSSP/SPI/USB
Maximum Clock Frequency
48 MHz
Number Of Programmable I/os
15
Number Of Timers
4
Maximum Operating Temperature
+ 85 C
Mounting Style
Through Hole
3rd Party Development Tools
52715-96, 52716-328, 52717-734, 52712-325, EWPIC18
Development Tools By Supplier
PG164130, DV164035, DV244005, DV164005, DM164127, DV164126
Minimum Operating Temperature
- 40 C
On-chip Adc
11-ch x 10-bit
Package
20PDIP
Device Core
PIC
Family Name
PIC18
Maximum Speed
48 MHz
Operating Supply Voltage
3.3|5 V
Lead Free Status / RoHS Status
Lead free / RoHS Compliant
For Use With
DV164126 - KIT DEVELOPMENT USB W/PICKIT 2DM164127 - KIT DEVELOPMENT USB 18F14/13K50AC164112 - VOLTAGE LIMITER MPLAB ICD2 VPP
Lead Free Status / Rohs Status
Lead free / RoHS Compliant
Available stocks
Company
Part Number
Manufacturer
Quantity
Price
Company:
Part Number:
PIC18F13K50-I/P
Manufacturer:
MICROCHIP
Quantity:
201
Part Number:
PIC18F13K50-I/P
Manufacturer:
MICROCHIP/微芯
Quantity:
20 000
PIC18F1XK50/PIC18LF1XK50
7.0
To allow portability of code, a PIC18F1XK50/
PIC18LF1XK50 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.
7.1
To allow portability of code, a PIC18F1XK50/
PIC18LF1XK50 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.
7.2
The checksum is calculated by summing the following:
• The contents of all program Flash locations
• The Configuration Word, appropriately masked
• ID locations (only if any portion of program
The Least Significant 16 bits of this sum are the
checksum.
Code protection limits access to program memory by
both external programmer (code-protect) and code
execution (table read protect). The ID locations, when
included in a code protected checksum, contain the
checksum of an unprotected part. The unprotected
checksum is distributed: one nibble per ID location.
Each nibble is right justified.
DS41342E-page 32
memory is code-protected)
EMBEDDING CONFIGURATION
WORD INFORMATION IN THE
HEX FILE
Embedding Data EEPROM
Information In the HEX File
Checksum Computation
Advance Information
Table 7-1 describes how to calculate the checksum for
each device.
Note:
The
depending on the code-protect setting.
Since the program Flash locations read
out differently, depending on the code-
protect setting, the table describes how to
manipulate the actual program Flash
values to simulate the values that would
be read from a protected device. When
calculating a checksum by reading a
device, the entire program Flash can
simply be read and summed. The
Configuration Word and ID locations can
always be read.
checksum
2010 Microchip Technology Inc.
calculation
differs