PE error 발생시 대처법

주로 PIC24HJ16GP304, PIC24HJ32GP204, dsPIC33FJ16GP304, dsPIC33FJ32GP204, dsPIC33FJ16MC304, dsPIC33FJ32MC204 에서 발생함.

다른 PGC/PGD 묶음에 ICSP를 연결해서 프로그래밍 해본다.

from. MPLAB readme 중에서 PICKIT2 발행 노트


밑은 원문

6.1        General Issues

·          Do not change the selected device (Configure > Select Device…) when PICkit 2 is actively selected as the Debugger. Doing so may cause PICkit 2 to hang at the next debug operation. Deselect PICkit 2 as the debugger (Debugger > Select Tool > None) before changing the device, and then reselect PICkit 2 as the debugger afterwards to ensure proper operation.

·         The Programming Executive (PE) for PIC24H and dsPIC33F parts may fail on certain programming ports of certain 44-Pin devices. Known problems exist with using the PGC3/PGD3 port on the following devices:

PIC24HJ16GP304, PIC24HJ32GP204, dsPIC33FJ16GP304, dsPIC33FJ32GP204, dsPIC33FJ16MC304, dsPIC33FJ32MC204

If a “PE Error” is frequently encountered in the MPLAB IDE Output Window, try using a different PGC/PGD programming port pair on the device.

·         To use the PICkit 2 as a debugger, two 4.7KW pull-down resistors are needed on pins ICSPDAT and ICSPCLK for units with a black pushbutton. Units with a red pushbutton have the pull-down resistors already internal to the unit.

·         Freeze Peripherals for PIC16F devices are not supported at this time.

·         PIC18F2520 MCUs: Table Read Protect (EBTRx) will not work unless Code Protect (CPx) is enabled. Also, once Table Read Protect is enabled, you cannot perform a Verify on the protected block.