DV164121 Microchip Technology, DV164121 Datasheet - Page 58

• Manufacturer Part Number: DV164121
• Description: KIT PICKIT 2 DEBUG EXPRESS
• Manufacturer: Microchip Technology
• Series: PICkit™ 2r
• Type: Microcontrollerr

Specifications of DV164121

• Contents: Board, PICkit™ 2 Programmer, Cable, CD
• Processor To Be Evaluated: PIC family
• Data Bus Width: 8 bit, 16 bit, 32 bit
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• For Use With/related Products: PIC Micro® MCU
• Lead Free Status / Rohs Status: Lead free / RoHS Compliant

5.3
DS51553E-page 54
PICKIT 2 DEBUG EXPRESS MPLAB IDE ERRORS
Memory Locations are marked ‘RR’
Question
Why does the File Register window or Program Memory show some locations marked
with ‘RR’?
Answer
These are locations that are reserved by ICD debuggers including PICkit 2 Debug
Express during debugging for the debug executive. See Section 4.4.2 “Reserved
Resources”.
Debug Express is Slow
Question
Why is debugging with PICkit 2 so slow?
Answer
Opening the View>File Registers or View>Special Function Registers windows in the
MPLAB IDE can significantly slow down debugging, due to the volume of information
being exchanged though the debugger. Use a Watch window instead as discussed in
Section 4.5.9 “Debugging the PIC16F887 Debug Demo Code”.
The debug interface is also directly affected by the target device oscillator speed. When
debugging with an oscillator less than 1 MHz, a slowdown in debugging performance
may be noticed.
Debug Express Overshoots Breakpoint
Question
Why isn’t PICkit 2 Debug Express stopping on the breakpoint instruction?
Answer
This behavior is referred to as “breakpoint skidding” and is covered in
Section 4.4.6 “Breakpoint Skidding”.
PK2Error0002: Allocation failure (Component)
PK2Error0003: Missing component (Component)
PK2Error0005: Failed to acquire component (Component, HRESULT)
PK2Error0006: Failed external call (Component, Method, HRESULT)
Description: An error occurred initializing a PICkit 2 component, during an internal
operation, or when communicating with the MPLAB IDE environment. The most
probable cause is an incomplete or corrupted installation.
Suggested Actions:
1. Uninstall all versions of MPLAB IDE from the PC.
2. Reinstall the desired MPLAB IDE version.
3. If the problem persists contact Microchip.
PK2Error0008: Read failure (GetLastError)
PK2Error0009: Write failure (GetLastError)
Description: MPLAB IDE was unable to communicate with the PICkit 2. Possible
causes include the PICkit 2 not enumerating properly on USB, a target board causing
a USB overcurrent condition or problems with a USB hub.
© 2008 Microchip Technology Inc.