MPLAB ICD 3 In-Circuit Debugger User's Guide

Error MessagesOther Things to Consider1. It is possible the error was a one time glitch. Try the operation again.2. There may be a problem programming in general. As a test, switch to programmermode and program the target with the simplest application possible (e.g., aprogram to blink an LED.) If the program will not run, then you know thatsomething is wrong with the target setup.3. It is possible that the target device has been damaged in some way (e.g., overcurrent.) Development environments are notoriously hostile to components.Consider trying another target device.4. Microchip Technology Inc. offers myriad demonstration boards to support mostof its microcontrollers. Consider using one of these applications, which areknown to work, to verify correct MPLAB ICD 3 in-circuit debugger functionality.Or, use the self-test board to verify the debugger itself (Section 10.7 “ICD 3 TestInterface Board”.)5. Review debugger debug operation to ensure proper application setup (Chapter2. “Theory of Operation”.)6. If the problem persists contact Microchip.7.3.7 Internal Error ActionsInternal errors are unexpected and should not happen. They are primarily used forinternal Microchip development.The most likely cause is a corrupted installation (Section 7.3.4 “CorruptedInstallation Actions”).Another likely cause is exhausted system resources.1. Try rebooting your system to free up memory.2. Make sure you have a reasonable amount of free space on your hard drive (andthat it is not overly fragmented.)If the problem persists contact Microchip.© 2008 Microchip Technology Inc. DS51766A-page 59