16 Bit MCU 40MIPS 64KB FLASH 100 TQFP 14x14x1mm TRAY

PIC24HJ64GP510A-E/PF

Manufacturer Part NumberPIC24HJ64GP510A-E/PF
Description16 Bit MCU 40MIPS 64KB FLASH 100 TQFP 14x14x1mm TRAY
ManufacturerMicrochip Technology
SeriesPIC® 24H
PIC24HJ64GP510A-E/PF datasheets
 


Specifications of PIC24HJ64GP510A-E/PF

Core ProcessorPICCore Size16-Bit
Speed40 MIPsConnectivityCAN, I²C, IrDA, LIN, SPI, UART/USART
PeripheralsBrown-out Detect/Reset, DMA, POR, PWM, WDTNumber Of I /o85
Program Memory Size64KB (22K x 24)Program Memory TypeFLASH
Ram Size8K x 8Voltage - Supply (vcc/vdd)3 V ~ 3.6 V
Data ConvertersA/D 32x10b/12bOscillator TypeInternal
Operating Temperature-40°C ~ 125°CPackage / Case100-TQFP, 100-VQFP
Lead Free Status / RoHS StatusLead free / RoHS CompliantEeprom Size-
1
Page 1
2
Page 2
3
Page 3
4
Page 4
5
Page 5
6
Page 6
7
Page 7
8
Page 8
9
Page 9
10
Page 10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
Page 10/84

Download datasheet (2Mb)Embed
PrevNext
FIGURE 3-3:
ENTERING ENHANCED ICSP™ MODE
P6
P14
MCLR
V
DD
PGDx
PGCx
P18
3.4
Blank Check
The term “Blank Check” implies verifying that the
device has been successfully erased and has no
programmed memory locations. A blank or erased
memory location is always read as ‘1’.
The Device ID registers (0xFF0000:0xFF0002) can be
ignored by the Blank Check since this region stores
device information that cannot be erased. The device
Configuration registers are also ignored by the Blank
Check. Additionally, all unimplemented memory space
should be ignored from the Blank Check.
The QBLANK command is used for the Blank Check. It
determines if the code memory is erased by testing
these memory regions. A ‘BLANK’ or ‘NOT BLANK’
response is returned. If it is determined that the device
is not blank, it must be erased before attempting to
program the chip.
DS70152H-page 10
V
IH
Program/Verify Entry Code = 0x4D434850
0
1
0
0
1
0
...
b31
b30
b29
b28
b27
b3
P1A
P1B
3.5
Code Memory Programming
3.5.1
PROGRAMMING METHODOLOGY
Code memory is programmed with the PROGP
command. PROGP programs one row of code memory
starting from the memory address specified in the
command. The number of PROGP commands required
to program a device depends on the number of write
blocks that must be programmed in the device.
A flowchart for programming code memory is illustrated
in
Figure
3-4. In this example, all 88K instruction words
of a dsPIC33F/PIC24H device are programmed. First,
the
number
‘RemainingCmds’ in the flowchart) is set to 1368 and
the destination address (called ‘BaseAddress’) is set to
‘0’. Next, one write block in the device is programmed
with a PROGP command. Each PROGP command
contains data for one row of code memory of the
dsPIC33F/PIC24H.
processed
decremented by ‘1’ and compared with ‘0’. Since there
are more PROGP commands to send, ‘BaseAddress’ is
incremented by 0x80 to point to the next row of
memory.
On the second PROGP command, the second row is
programmed. This process is repeated until the entire
device is programmed.
Note:
If a bootloader needs to be programmed,
the
programmed into the first page of code
memory. For example, if a bootloader
located at address 0x200 attempts to
erase the first page, it would inadvertently
erase
bootloader into the second page (e.g.,
0x400).
P19
P7
V
IH
0
0
0
b2
b1
b0
of
commands
to
send
(called
After
the
first
command
successfully,
‘RemainingCmds’
bootloader
code
must
not
be
itself.
Instead,
program
the
© 2010 Microchip Technology Inc.
is
is