DV164120 Microchip Technology, DV164120 Datasheet - Page 59

• Manufacturer Part Number: DV164120
• Description: KIT STARTER PICKIT 2
• Manufacturer: Microchip Technology
• Series: PICkit™ 2r
• Type: Microcontrollerr

Specifications of DV164120

• Contents: Board, PICkit™ 2 Programmer, Cable, CD
• Processor To Be Evaluated: PIC family
• Data Bus Width: 8 bit, 16 bit, 32 bit
• Core Architecture: PIC
• Ic Product Type: Programmer
• Kit Contents: Hardware, Cables, Literature And Software
• Ic Interface Type: USB
• Supported Families: PICmicro
• Rohs Compliant: Yes
• Development Tool Type: Hardware / Software - Starter Kit
• 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
• For Use With: 8/14/20-pin PICmicros
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant, Lead free / RoHS Compliant

Troubleshooting
Suggested Actions: Ensure the target board does not pull more than 25 mA of current
from the PICkit 2. If it does, use an external power supply with the target board.
A target board may interfere with PICkit 2 enumerating on USB. When connecting
PICkit 2 to a USB port, booting or restarting a connected PC, ensure the PICkit 2 is dis-
connected from the target board.
If the PICkit 2 is connected to a USB hub, try connecting the PICkit 2 directly to a PC
USB port.
When using PICkit 2 as a programmer or debugger in the MPLAB IDE, do not run the
PICkit 2 Programmer application or PK2CMD at the same time.
If the problem persists, try connecting to PICkit 2 using the PICkit 2 Programmer
application.
PK2Error0010: Failed to unload PICkit 2
Description: MPLAB IDE was unable to disconnect from PICkit 2 as a debugger or
programmer when switching to the other tool mode.
Suggested Actions: Disconnect the PICkit 2 from USB, reboot the computer, then
reconnect PICkit 2 to USB (ensure the PICkit 2 is not connected to a target board.) If
the problem persists contact Microchip.
PK2Error0011: PICkit 2 is already busy. Unable to perform requested
task.
Description: PICkit 2 Debug Express has been asked to perform an operation while it
is busy servicing a prior request. For example, a programming operation may still be
process when a debug Step operation is attempted.
Suggested Actions: This situation will not normally happen as the user interface is
disabled while PICkit 2 is servicing requests. Wait for the original operation to
complete.
PK2Error0012: Unable to open file (Filename)
Description: PICkit 2 Debug Express was unable to open the specified file.
Suggested Actions: Ensure the file exists, and file or directory permissions do not pre-
vent access to the file. This may also be caused by an incomplete or corrupted
installation. See
PK2Error0002 Suggested
Actions.
PK2Error0013: Bad hex line (File - Line)
PK2Error0014: Invalid address in hex file (File - Line - Address)
Description: PICkit 2 Debug Express detected an error in a debug executive hex file.
Suggested Actions: Since all debug executive hex files are provided by Microchip, the
issue is most likely a corrupted installation. See
PK2Error0002 Suggested
Actions.
PK2Error0015: Failed Windows call (WinFunc - GetLastError)
Description: A call to a Windows function within PICkit 2 Debug Express has failed.
This internal error is primarily meant for debugging purposes.
Suggested Actions: This may be caused by existed system resources or a corrupted
installation.
1. Try rebooting your system to free up memory.
2. Make sure you have a reasonable amount of free space on your hard drive, and
that it is not overly fragmented.
3. See
PK2Error0002 Suggested Actions
for a corrupted installation.
© 2008 Microchip Technology Inc.
DS51553E-page 55