Справочник Пользователя для Microchip Technology ICD 3 In-Circuit Debugger DV164035 DV164035
Модели
DV164035
MPLAB
®
ICD 3 In-Circuit Debugger User’s Guide
DS51766A-page 58
© 2008 Microchip Technology Inc.
7.3.5
USB Port Communication Error Actions
The problem is most likely caused by a faulty or non-existent communications port.
1.
Reconnect to the MPLAB ICD 3 in-circuit debugger
2.
Make sure the debugger is physically connected to the PC on the appropriate
USB port.
USB port.
3.
Make sure the appropriate USB port has been selected in the debugger Settings.
4.
Make sure the USB port is not in use by another device.
5.
If using a USB hub, make sure it is powered.
6.
Make sure the USB drivers are loaded.
7.3.6
Debug Failure Actions
The MPLAB ICD 3 in-circuit debugger was unable to perform a debugging operation.
There are numerous reasons why this might occur.
There are numerous reasons why this might occur.
Top Reasons Why You Can’t Debug
1.
The oscillator is not working. Check your Configuration bits setting for the
oscillator.
oscillator.
2.
The target board is not powered. Check the power cable connection.
3.
The MPLAB ICD 3 in-circuit debugger has somehow become physically
disconnected from the PC. Check the USB communication cable connection.
disconnected from the PC. Check the USB communication cable connection.
4.
The debugger has somehow become physically disconnected from the target
board. Check the communications cable connection.
board. Check the communications cable connection.
5.
The device is code-protected. Check your Configuration bits setting for code
protection.
protection.
6.
You are trying to rebuild the project while in Release mode. Select Debug in the
Build Configuration drop-down list on the project toolbar, then rebuild the project.
Build Configuration drop-down list on the project toolbar, then rebuild the project.
7.
The debugger is selected as a programmer, and not as a debugger, in MPLAB
IDE.
IDE.
8.
Debugger to PC communications has somehow been interrupted. Reconnect to
the debugger in MPLAB IDE.
the debugger in MPLAB IDE.
9.
The target application has somehow become corrupted or contains errors. For
example, the regular linker script was used in the project instead of the debugger
version of the linker script (e.g., 18F8722.lkr was used instead of 18F8722i.lkr).
Try rebuilding and reprogramming the target application. Then initiate a
Power-on Reset of the target.
example, the regular linker script was used in the project instead of the debugger
version of the linker script (e.g., 18F8722.lkr was used instead of 18F8722i.lkr).
Try rebuilding and reprogramming the target application. Then initiate a
Power-on Reset of the target.
10. Other configuration settings are interfering with debugging. Any configuration
setting that would prevent the target from executing code will also prevent the
debugger from putting the code into debug mode.
debugger from putting the code into debug mode.
11. The debugger cannot always perform the action requested. For example, the
debugger cannot set a breakpoint if the target application is currently running.