Release Notes for MPLAB® ICD 2 In-Circuit Debugger
MPLAB® IDE v8.15
MPLAB ICD 2 DLL v8.1.0.23
Operating System (Firmware) Files
|
PIC12F/16F |
v2.07.06 |
(ICD01020706.hex) |
|
PIC12F61X/16F61X |
v1.01.03 |
(ICD15010103.hex) |
|
PIC18F |
v2.07.09 |
(ICD04020709.hex) |
|
PIC18F Extended |
v1.04.05 |
(ICD05010405.hex) |
|
PIC18C601/801 |
v1.02.05 |
(ICD06010205.hex) |
|
PIC10F2XX,PIC16F54/57 |
v1.04.06 |
(ICD07010406.hex) |
|
PIC16F68X |
v1.05.06 |
(ICD08010506.hex) |
|
PIC12F629/675; PIC16F630/676 |
v1.00.03 |
(ICD09010003.hex) |
|
dsPIC30F Rev B1 |
v1.06.04 |
(ICD10010604.hex) |
|
dsPIC30F SMPS Rev 1 |
v1.00.08 |
(ICD18010008.hex) |
|
PIC18F67J/87J |
V2.00.08 |
(ICD11020008.hex) |
|
PIC16F72, PIC16F8X, PIC16F627/628 |
v1.02.03 |
(ICD12010203.hex) |
|
PIC18F45K20/14K50 |
v2.01.09 |
(ICD16020109.hex) |
|
dsPIC33F, PIC24F, PIC24H |
v3.04.01 |
(ICD14030401.hex) |
|
PIC32MX |
v1.00.10 |
(ICD20010010.hex) |
September 26, 2008
|
IMPORTANT: Do not allow Windows® OS to pick a default USB driver. MPLAB ICD 2 will not work with that driver. You must follow the procedure specified during MPLAB IDE software installation for USB driver setup. If you do not set up the port during MPLAB IDE installation, see the section in this readme file on USB Port Setup. |
Table of Contents
5 Repairs and Enhancements Made in v8.15
7 Powering the MPLAB ICD 2 and Target Board
8 Setting Up the MPLAB ICD 2 and Target Board
10 PIC18FXXJ, PIC18FXXK, PIC24F, dsPIC33F Device Programming Considerations
11 Device Programming Considerations
14 Universal Programming Module (AC162049)
Click the link below to see device support for “ICD Debugging” (ICDD) and “ICD Programming” (ICDP).
See section 10 for special device programming considerations to avoid damage these devices:
|
PIC24F/H |
dsPIC33F |
Universal programmer adapter (AC163020) required for the following devices:
PIC10F2XX
For low pin-count devices (8 to 28 pins), a Header board is usually required. See the Header Board Specification (DS51292) or Header help file (hlpHeader.chm) for a list of available headers by device.
For high pin-count devices (40 to 100 pins), a Header board may available, but is not required. See the Header Board Specification (DS51292) or Header help file (hlpHeader.chm) for a list of available headers by device.
This tool has been tested using the following operating systems:
Windows® 2000 SP4, Windows XP SP2, and Windows Vista™ (32-Bit)* OSs
MPLAB ICD 2 P/N 10-00319 does not support 64-bit Vista.
MPLAB ICD 2 P/N 10-00397 supports 64-bit Vista.
IMPORTANT NOTICE: Beginning with MPLAB IDE v7.51, MPLAB IDE and MPLAB ICD 2 will no longer be tested on Windows 98 or Windows ME OSs. MPLAB IDE and MPLAB ICD 2 may continue to work under these operating systems, but their operation will no longer be verified through testing.
The following documents may be found on our website or MPLAB IDE CD-ROM:
· MPLAB ICD 2 Design Advisory (DS51566)
· Using MPLAB ICD 2 Poster (DS51265)
· MPLAB ICD 2 User's Guide (DS51331)
· Header Specification (DS51292)
· Universal Programming Module Instruction Sheet (DS51280)
On-line help (Help>Topics) is also available for this tool:
· Debuggers>MPLAB ICD 2 - hlpMPLABICD2.chm
· New device support and SSR fixes.
|
Key |
Summary |
Device Affected |
|
ICD2-307 |
[Advance breakpoint] With “reset to beginning of the main” enabled, setting advance breakpoint on data memory with a non-zero pass count and then disabling it, causes all PICKit2 options to disable. |
|
|
ICD2-293 |
Read fails when reading a code protected device. |
PIC32MX |
|
ICD2-290 |
Data memory breakpoints are not functional. |
PIC32MX |
|
ICD2-288 |
MPLAB IDE allows execution of only the 1st breakpoint despite setting six breakpoints for the PIC32MX devices. |
PIC32MX |
|
ICD2-286 |
MPLAB ICD 2 is unable to change the value of any bits of the ADCON1 register for the PIC18F85J90 device. |
PIC18F85J90 |
|
ICD2-285 |
[ICD0169] CapID not supported for this device (WREG) is displayed, but should not be. |
PIC18F45J11 / PIC18F46J50/ PIC18F45K20 Families |
|
ICD2-272 |
Breakpoints work intermittently for ICD2 as a debugger using the PIC32MX devices |
PIC32MX |
|
ICD2-271 |
Communications between ICD2 and the target PIC32MX is intermittent. |
PIC32MX |
|
ICD2-249 |
MPLAB IDE reports error ICD027 when accessing the program tab under debugger/programmer settings. |
dsPIC33FJ32MC304, PIC24HJ32GP302 |
|
Key |
Summary |
Device Affected |
|
ECAN variables have incorrect memory names with C1CTRL1.WIN=1 using a debugger. |
dsPIC33FJ256GP710 |
|
|
MPLAB ICD 2 as a Programmer: Both the 'Start' and 'End' Program Memory addresses entered into Program tab page are not validated |
|
|
|
Debugger has trouble connecting and downloading O/S. |
PIC32MX |
|
|
Some PIC18FJxxx devices selected allows 0 breakpoints using same project/workspace. |
PIC18FxxJ devices for certain (possibly many others) |
|
|
dsPIC30F4013 should only have 1 breakpoint. |
dsPIC30F4013 |
|
|
ICD2 does a backwards jump on return from a step over instruction on a function. |
PIC18F4525/4520 |
|
|
Pressing Cancel on the Image-Platform Mismatch warning does not cancel programming |
|
|
|
[Documentation] - The File Register Allocation in Help file & IDE don't match |
PIC16F818 |
|
|
After programming with "Auto run after program" in programmer mode, the Hold in Reset toolbar button does not get enabled |
PIC16F917 |
|
|
Incorrect display of the Dialog box "No More Breakpoints". |
PIC18F family |
|
|
Gives an error after building and attempting to program. |
PIC16F630 |
|
|
MPLAB IDE reports invalid device ID for the PIC32MXxxxx devices. |
PIC32MX |
|
|
Programming settings dialog box shows 'Bootloader' area. It is unclear that this is specifically for the PIC18C601/801 product. |
PIC18C601/801 |
|
|
Request automatic halt and reset target before programming |
|
|
|
User reports not being able to double click on ICDWarn00051 to bring up the help. The help has ICDWarn0051. |
|
|
|
Abort operation fails for the PIC24FJxxxGAxxx devices in MPLAB IDE v7.31.09 using Fw ver 02.00.06.00 |
PIC24FJxxxGAxxx |
|
|
Customer reports getting error message ICD0289 which is not documented in the help. |
|
|
|
MPLAB-1247 |
When the MPLAB ICD 2 is invoked on the rf12F675K, it incorrectly informs you to use a Zener diode on MCLR line. This device is not a 200k product and does not require a clamp on this line. If a clamp were applied, you would not be able to get his application working. |
rfPIC12F675K |
Installation and setup instructions are dependent on your operating system. Open the appropriate file for your OS in a web browser and follow the instructions to install the driver(s).
Note: If you have accidentally installed the Windows OS default driver, these instructions will direct you to how to "clean" your system first before installing the correct driver(s).
Note: If you change USB ports/hubs, you will need to reinstall the drivers.
Win 2000/XP/Vista/Vista 64
Find detailed instructions at:
C:\Program Files\Microchip\MPLAB
IDE\ICD2\Drivers\ddicd2.htm
Basic instructions are as follows:
Win XP 64
Installation instructions are as follows:
IMPORTANT NOTICE: Beginning with MPLAB IDE v7.51, MPLAB IDE and MPLAB ICD 2 will no longer be tested on Windows 98 or Windows ME OSs. MPLAB IDE and MPLAB ICD 2 may continue to work under these operating systems, but their operation will no longer be verified through testing.
Win 98
C:\Program Files\Microchip\MPLAB IDE\ICD2\Drivers\ddicd298.htm
Win ME
C:\Program Files\Microchip\MPLAB IDE\ICD2\Drivers\ddicd2me.htm
NOTE: MPLAB ICD 2 must be powered BEFORE power is applied to the target application.
Serial (RS-232) connection to the PC:
Power supply required.
USB connection to the PC, target not powered from MPLAB ICD 2 or no target connected:
No power supply needed.
USB connection to the PC, target powered from MPLAB ICD 2:
Power supply required. (USB cannot power both.)
Note: Plug in USB first, then power supply.
The MPLAB ICD 2 cannot be powered from the target board.
The MPLAB ICD 2 can provide 5 V and up to 200 mA to a target
if the ICD itself is powered by a power supply. (USB cannot power both.) This
is enabled by checking "Power target circuit from MPLAB ICD 2" (Debugger>Settings,
Power tab).
Note: Plug in USB first, then power supply.
Note: The ICD headers need to be connected to a target board or else they may receive the ICD00083 debug error.
1. Power the MPLAB ICD 2. DO NOT power the target.
2. Start MPLAB IDE.
3. Under the Debugger menu of MPLAB IDE, click "Connect".
4. After establishing communications with the MPLAB ICD 2, select Debugger>Settings.
5. In the Settings dialog, click the Power tab and ensure that the check box for "Power target circuit from MPLAB ICD 2" is checked. Click OK.
6. Now you should be able to erase and program components with the MPLAB ICD 2.
1. Power the MPLAB ICD 2. DO NOT power the target.
2. Start MPLAB IDE.
3. Under the Debugger menu of MPLAB IDE, click "Connect".
4. After establishing communications with the MPLAB ICD 2, select Debugger>Settings.
5. In the Settings dialog, click the Power tab and ensure that the check box for "Power target circuit from MPLAB ICD 2" is NOT checked. Click OK.
6. Power the target system and then select Debugger>Connect.
7. Now you should be able to erase and program components with the MPLAB ICD 2.
If any of the self tests on the Status tab of the Settings dialog do not say pass, you will not be able to erase and program your device. Exception: if Vpp says low, you may still be able to program if the voltage is more than the low value for the device programming range listed in the device programming spec.
Generally, failed self tests will require further troubleshooting.
See on-line help for more information.
There is a folder called \ICD2 that was copied into the MPLAB IDE installation directory. This folder has two files which can be used with the PICDEM™ 18R demo board (DM163006):
SRAM16.HEX - allows program download to the static RAM
29F16016.HEX - allows program download to the flash memory
When using PICDEM 18R, you must use one of the files above in the "Location of WriteProgramWord and EraseProgramMemory" dialog on the MPLAB ICD 2 Advanced Dialog. Also, you must remember to do an erase before programming as this is not done automatically.
For your own design, which probably has different programming algorithms for the memory on your target, you must substitute your own memory read/write routine in order for the MPLAB ICD 2 to download code. See the PICDEM 18R documentation for information on writing your custom routines. These code routines will be used to program your memory and care must be taken to ensure they are relocatable and comply with the format used in the included source files.
The Programming Specifications for PIC18FXXJ MCUs, PIC24F MCUs, and dsPIC33F DSCs indicate that when programming these devices, bulk erase commands should be issued between successive programming operations, i.e., erase, then program, then erase, then program, etc. Therefore, Microchip advises against multiple-stage programming sessions which may damage the device. For example, you should NOT do the following with these parts:
· load and program a particular hex file
· load a second hex file
· disable erase-all-before-programming
· specify an address sub-range
· program the device
The Programming Specifications for PIC18FXXJ MCUs indicate that, this process technology is not 12-volt tolerant. Ensure that external protection for MCLR is in place, for example a zener diode, before proceeding to prevent any damage to your device.
For CodeGuard™ Security Devices
Several 16-bit devices allow customers to define up to 3 programming segments: Boot, Secure and General. The purpose is to allow a customer to place proprietary data (libraries, IP address, etc.) into a protected boot or secure segment. That customer may then transfer these preprogrammed devices to another customer who would use the unprotected general segments.
For more details on CodeGuard Security functionality, please refer to the CodeGuard Security reference manual for 16-bit devices (DS70180) and dsPIC33F/PIC24H and dsPIC30F device programming specifications found on our website.
To program the preprogrammed devices, MPLAB IDE v7.50 and above provides a Secure Segment tab on the Settings dialog, accessed under either the Programmer or Debugger menu. This tab contains the following options:
· Full Chip Erase/Program
· Segment Programming
· Boot, Secure & General Segments
· Secure,General Segments
· General Segment.
The programming function of this tool is now capable of identifying various device segments and their sizes upon connecting the device. Hence, these options allow you to selectively program the program memory segments and thus avoid accidental eraser of preprogrammed proprietary data (Libraries, IP, etc.)
For Non-CodeGuard Security Devices
When programming these devices, bulk erase commands should be issued between successive programming operations, i.e., erase, then program, then erase, then program, etc. Therefore, Microchip advises against multiple-stage programming sessions which may fail to verify. For example, you should NOT do the following sequence with these devices:
The following is a list of known problems. For information on common problems, error messages and limitations, please see Troubleshooting in the online help file for MPLAB ICD 2 (hlpMPLABICD2.chm).
If you are using MPLAB ICD 2 with USB communications AND a power supply, plug in the USB first, then the power supply.
If you have problems with serial communications, see the Troubleshooting section in the help file.
NOTE: You should have the FIFO disabled and hardware handshaking enabled on the PC COM port properties.
· Select Start>Settings>Control Panel
· Double-click on System to open "System Properties"
· Open the Device Manager and find your COM port under Ports
· Open the Communications Port Properties dialog for this port
· Under Port Settings, choose "Flow Control: Hardware" for hardware handshaking
· Open the Advanced Settings dialog and deselect Use FIFO buffers
· When first connecting to MPLAB ICD 2 using serial communications, the default COM port is COM1. If you are using the MPLAB ICD 2 on another COM port, Select Debugger>Settings, Communication tab to set the appropriate COM port. Subsequent connections should be established quickly.
· If you are having problems with ICD operation, please check the revision of your pod, found on the back of the unit. If the part number is 10-00319 R15 through R21 without an “ECO 3013” sticker, please contact your local Microchip FAE or sales office to return the unit for replacement.
· If you do not use the included USB or RS-232 cable, make sure the cable you do use is not longer than 6 feet or communication errors could result. For modular cable lengths, see on-line help.
· Do not plug both the USB cable and RS-232 cable into the MPLAB ICD 2 pod. This will cause errors. Choose one form of ICD-to-PC communication.
For baseline devices, TRISIO and OPTION_REG appear in the watch window drop down list but are not available on the MPLAB ICD 2. No information will be displayed if either is selected.
For dsPIC30F devices, you must provide power on your own board and not to use power from the ICD. The power (Vdd) provided from MPLAB ICD 2 to the target device is not sufficient for all programming operations of the dsPIC30F device family.
Using the USB connection on a laptop PC with suspend mode enabled will lock up the MPLAB ICD 2 if suspend mode is entered. Unplug the USB cable from the MPLAB ICD 2 and then plug the cable back in to resume debugging. You may want to disable suspend mode while using the MPLAB ICD 2. From Control Panel, select Power Options and disable suspend mode.
Care should be taken when programming the PLL. The PLL only changes when power is first applied to the chip. If you are programming the PLL for the first time, remove power from the PIC18Fxxxx part after programming and reapply for the PLL to be enabled. If you are reprogramming the device from PLL mode to another mode, first reprogram with PLL off, then remove power and reapply.
If you have trouble when low voltage programming, add a pull-down 10k ohm resistor to RB5.
Numbers in the start and end address boxes (Debugger>Settings, Program tab) must use the hex numbering convention (0x....).
For PIC18F8720, MEMCON cannot be read if in a microcontroller mode. This is a silicon issue.
If you are not able to enter debug mode when power-up timer is enabled for the following devices, please disable power-up timer during the debugging session. (If the final application firmware requires power-up timer enabled, please enable it after the debugging session is complete and program the part with the final application firmware.)
· PIC18F4620/4610/2620/2610
· PIC18F4680/2680/4681/2681
· PIC18F4520/4420/2520/2420
· PIC18F4550/2550/4455/2455
· PIC18F8490/8410/6490/6410/8390/8310/6390/6310
· PIC18F8722/8627/8622/8527/6722/6627/6622/6527
· PIC18F2525/4525
For dsPIC30F device programming, the Universal Programming Module cannot be used due to the limited number of Vdd and Vss connections.
Code Example CE020 for 16-bit controllers: During the programming sequence, PIC24F devices may be put into a run condition using MPLAB ICD 2. This can result in a verification failure if the code performs self write to either program memory or Data EE.
On PIC16F88X devices it is necessary to pull the RB3/PGM pin low for ICSP programming. This is due to a silicon issue.
When connecting the PIC16F818/819 to the latest MPLAB ICD2's (r3), the device may latch resulting in ICD2Warn0020: Invalid target device id (expected=0x27, read=0x0). A work around is to use a .1 uF capacitator on VPP to GND.
Watch window – It will take 1 cycle for the watch window to update properly for PORTx registers. Use an instruction that reads the port such as ‘MOVFF PORTx, PORTx_copy’ before the breakpoint is reached. This affects the following devices:
PIC18F4620
PIC18F63J90
PIC18F64J90
PIC18F64J95
PIC18F65J95
PIC18F83J90
PIC18F84J90
PIC18F84J95
PIC18F85J90
PIC18F63J11
PIC18F64J11
PIC18F64J16
PIC18F65J11
PIC18F83J11
PIC18F84J11
PIC18F84J16
PIC18F85J11
The low voltage devices, such as PIC18F/LFXXJXX, may result in ICD2Warn0020: Invalid target device id if not powered up correctly.
Work around:
When using 16-bit headers (PIC24H/dsPIC33F/PIC24F) during a debug session with the MPLAB ICD 2 tool, do not disconnect power from the target device else the selected emulated device variant will be lost. If the variant is lost due to disconnecting power during a debug session, just re-program the user code into the device again to re-program and restore the selected variant.
Newer devices with programming ranges of 10-12V may show higher than specified Vpp (13V) on older MPLAB ICD 2 pods (P/N numbers of 10-00319 or less) designed for a 12-14V range. This value is within device tolerance (13.5V) and should not cause an issue when debugging.
MPLAB ICD 2 does not currently support KUSEG.
NOTE: Production programming using the MPLAB ICD 2 is not recommended.
SSR 20230: Programming or reading a code-protected EEPROM memory generates no messages by MPLAB IDE for MPLAB ICD 2 for a PIC12F675 device.
SSR 21163: Programmer function: Cannot program PIC16F87x devices in individual or in combinations of the memory areas without the entire device being automatically erased.
SSR 24354: Freeze peripherals on Halt is checked and grayed, but some peripherals do not freeze. This is a silicon issue.
SSR 26344: Below 4.5 V, MPLAB ICD 2 will not overprogram User ID's on these devices:
PIC12F635 PIC16F684 PIC16F689 PIC16F914
PIC12F683 PIC16F685 PIC16F690 PIC16F916
PIC16F636 PIC16F687 PIC16F785 PIC16F917
PIC16F639 PIC16F688 PIC16F913 PIC16F946
SSR 29399: MPLAB ICD2 fail to program/verify the PIC24FJ128GA010 device when user code does run time flash erase /write operation.It appears the device is executing code before the full programming cycle is complete.
ICD2-18: Freeze peripherals on Halt is checked and grayed, but Timers act as if Freeze if off - 16F684/16F688
ICD2-81: MPLAB ICD 2 fails to program/verify the PIC24FJ128GA010 device when user code does runtime flash erase /write operation. It appears the device is executing code before the full programming cycle is complete.
For PIC24F devices during a programming/verify operation (or subsequent verification operation) of user code that performs self-writes and/or self-erases to program space, a verify sequence may fail if the code execution occurs within the first execution cycles following reset.
Workaround: Place a delay in your code before the code section that performs the self-write and/or self-erase.
The specific delay value may need to be adjusted, but 100 ms would be a conservative value to start
out with. Here is a C language example that illustrates the workaround:
int main (void)
{
// Place 100 ms delay here before any self-write/self-erase code
. . .
. . .
. . .
}
ICD2-109: When connecting the PIC16F818/819 to the latest MPLAB ICD 2’s (r3), the device may latch resulting in ICD2Warn0020: Invalid target device id (expected=0x27, read=0x0). To work around the issue, reduce the cable length to less than 6 inches. Also, if AC162049 is being used, remove the R1 pull-up resistor. Some devices require that a .1uF bypass capacitor be placed from the Vdd pin to the Vss pin of the device to successfully program the device. If programming failures still arise, try increasing this value incrementally to a maximum of 10uF.
ICD2-145: Known limitation: Debugging user code is not possible above 11 MHz when in 'EC' oscillator mode. The following devices are supported by this header: PIC12F609, PIC12F615, PIC16F610, PIC16F616, PIC12HV609, PIC12HV615, PIC16HV610, and PIC16HV616 These devices do not have debug capability by themselves so the header must be used to debug user code.
ICD2-155: USB hub may be interfering with MPLAB ICD 2 tool with regards to debugging.
ICD2-184: PIC32MX Multiple Breakpoints do not function, only the last break point added will stop execution.
ICD2-220: Some family of devices require Power-up timer disabled to enter debug mode. See 12.2, General Issues section.
ICD2-263: MPLAB ICD 2 has issues with PIC32 MCUs when using an array to fill memory
ICD2-287: Older MPLAB ICD 2 pods do not work with PIC32MX MCUs. This issue is being worked on. To identify the older vs. newer pods:
Older pod P/N: 10-00319
Newer pod P/N: 10-00397
ICD2-297: PIC18F67J11 - Verification fails in debugger mode for this device and is dependent on hex file due to device running between program/verify.
ICD2-301: Debugger>Clear Memory>All Memory under device PIC16F819 may cause crash.
If you modify Program Memory, you must reprogram the device.
When running in debug mode, selecting Debugger>Reset resets the program, goes to the zero location, and halts. The program does not automatically re-run.
The following applies to all devices except for Extended PIC18F Devices V2:
- While single stepping, the MPLAB ICD 2 will not respond to interrupts.
- The SLEEP instruction cannot be used when debugging.
- The WDT cannot be used when debugging.
An exception to the single step SLEEP and WDT in the above notes:
Extended PIC18F Devices V2 will allow the user to interrupt while single stepping, use SLEEP, use WDT. Please see MPLAB ICD2 help for details.
USB hubs must be powered.
When working with PIC18XXXX parts, debugging speed is improved (breakpoints, single-step, etc.) if the General Purpose File Register Window is closed. You can put any registers that need to be monitored into a Watch Window, or view Special Function Registers in the SFR Window. MPLAB IDE updates information in visible sections of windows only, unless otherwise specified. Therefore, the smaller the visible area, the faster the updates and debugging speed.
For PIC18Fxx20 devices, you must connect the AVDD and AVSS pins for the devices to program.
Make sure that table reads/writes are not code protected.
In low voltage mode, bulk erase will not erase code protect bits.
MPLAB ICD 2, by design, has limited debug capabilities when compared with an emulator. This is a price/feature trade-off. If you need more complex debugging capabilities, the MPLAB ICE 2000 for PIC MCU device emulation and the MPLAB ICE 4000 for PIC18 MCU and dsPIC DSC device emulation are suggested.
When using a 32 kHz crystal, you may receive the message "Target not in debug mode". Perform a reconnect to enter debug mode.
MPLAB ICD 2 has different OS's for different part families. The ICD will, by default, automatically download the correct OS as necessary.
It is possible to turn off the automatic download feature in Settings>Status. You will then be asked in a dialog if you wish to download the OS. Disabling the automatic download feature is NOT RECOMMENDED. Serious errors may occur if your OS is not correct for your selected device. It is recommended that you download the MPLAB ICD 2 firmware that was packaged with the version of MPLAB IDE being used on your system.
1.
Analog pins:
If MPLAB ICD 2 is selected as a debugger, it initializes all the A/D input pins
- AN0 through AN31 pins - as "digital" pins, by setting all bits in
the ADPCFG register (dsPIC30F) or AD1PCFGL and AD2PCFGL registers
(dsPIC33F/PIC24H).
For example, if EMUD3 and EMUC3 are used as the debug pins on a dsPIC30F2010 device, then bits 0 and 1 of the ADPCFG register must remain set at all times. Similarly, if EMUD and EMUC are used as the debug pins on a dsPIC30F5011 device, then bits 6 and 7 of the ADPCFG register (or AD1PCFGL and AD2PCFGL registers) must remain set at all times. In such cases, you must also take proper precaution to isolate the application circuitry from the corresponding A/D pins during debugging.
For example, if AN4 and AN5 are required as analog input pins, then bits 4 and 5 of the ADPCFG register must be cleared.
2. After programming a device, you must perform a Processor Reset. This can be done either by selecting the Debugger>Reset>Processor Reset command, pressing the <F6> hotkey or clicking on the Processor Reset button. This ensures that the device oscillator is active before the program is run or debugging operations are performed.
3.
User RAM Usage:
You must not use the following memory region while using MPLAB ICD 2; 0x800 -
0x84F (i.e., the first 80 bytes of RAM). If the ICD is to be used for a
particular project, on the Project Manager toolbar select "Debug"
from the Build Configurations drop-down list.
4. File Registers / Special Function Registers / Watch window:
5.
Programming Range:
On enabling MPLAB ICD 2, the Program End Address (Debugger>Settings)
is automatically set as low as possible based on the Program Memory usage of
each MPLAB IDE project. This helps minimize the programming time.
6.
SLEEP, IDLE, WDT, Clock Switching:
For dsPIC devices, debug operations can be executed on programs which use SLEEP
or IDLE mode, Watchdog Timer, and/or Clock Switching.
7.
Debug during SLEEP or IDLE Mode:
When the device is in SLEEP and IDLE mode and a Halt command is issued, MPLAB
ICD 2 will wake up the device and halt execution on the instruction immediately
following the PWRSAV instruction.
8. Interrupts:
9.
Break Point Behavior:
If a break point is set on an instruction that follows a taken branch, the
Breakpoint will be triggered even though the branch went elsewhere.
10.
Break Point Behavior and Skidding:
It is possible that a breakpoint halt will exhibit program memory skidding in
that the execution stops N instructions after reaching the breakpoint. The
following definitions are provided and referred to:
Break Point Behavior:
11. The CAN module, unlike the other peripherals, does not get frozen in the following situations:
For example, if you set a Breakpoint and run to it, the CAN module continues to run in the background, and it may seem that data transmissions and receptions have completed immediately.
12.
DISICNT register:
In five dsPIC30F devices (dsPIC30F6010, dsPIC30F6011, dsPIC30F6012,
dsPIC30F6013 and dsPIC30F6014), since the DISICNT register continues to
decrement even when the device is halted by the debugger, the DISICNT value
will always be seen as 0x0000 in the Watch, SFR and File Registers windows. To
monitor the DISICNT value, add code to copy the DISICNT register contents to a
W register or memory location and monitor the value of the corresponding W
register or memory location in the Watch, SFR or File Registers window.
13.
ADC Module Disable bit in
PMD1 register:
The user application must not set
the ADCMD bit (dsPIC30F) or AD1MD bit (dsPIC33F/PIC24H) in the PMD1 register.
This would lead to incorrect ICD2 operation..
14.
Single-stepping a DO loop:
In five dsPIC30F devices (dsPIC30F6010, dsPIC30F6011, dsPIC30F6012,
dsPIC30F6013 and dsPIC30F6014), single-stepping through a DO loop in dsPIC30F
assembly code results in the loop getting executed one less time than expected.
15.
Number of Breakpoints:
|
Number of Breakpoints Supported |
Devices |
|
1 |
dsPIC30F2010, 2011, 2012, 3010, 3011, 3012, 3013, 3014, 4013 |
|
2 |
dsPIC30F1010, 2020, 2023, 4011, 4012, 5011, 5013, 5015, 5016, 6010, 6010A, 6011, 6011A, 6012, 6012A, 6013, 6013A, 6014, 6014A, 6015 |
|
6 |
All dsPIC33F and PIC24H. |
16.
Pass Counter feature in Advanced Breakpoints:
For a specified Pass count of 'N', the code will break after 'N+1' occurrences
of the breakpoint instead of 'N' occurrences.
17. If you need to use the Fail-Safe Clock Monitor feature on a dsPIC device when using the MPLAB ICD 2 for debugging your application, a Watchdog Timer Device Reset will occur, even if the Watchdog Timer has not been explicitly enabled in the application. This will also occur with any invocation of the LPRC clock source whether by configuration bytes or clock switching to the LPRC at run time will enable the Watchdog Timer. Any action that causes the LPRC clock source to become and/or remain active after the PWRT (Power-up Timer) expires will enable and cause a WDT countdown. To work around this issue, use the "CLRWDT" instruction in the main loop of your application code. This will ensure that the Watchdog Timer gets cleared before it causes the device to reset.
18. The UART module UxRXREG register on dsPIC33F devices and certain dsPIC30F devices (dsPIC30F1010 and dsPIC30F202x) may show incorrect values in debug mode. Investigating the UxRXREG register in debug mode could result in the application reading the wrong value from this register on exiting the debug mode. To avoid this condition, do not set breakpoint or step through code that reads the UxRXREG register. Also avoid setting a watch on the UxRXREG register. Alternatively, set up the application to complete reading the UxRXREG register into user application memory variables. Set a watch on or debug these variables to observe the UxRXREG register.
The Universal Programming Module (UPM) allows the MPLAB ICD 2 to be used as a device programmer for supported product DIP packages.
In-Circuit Serial Programming (ICSP) signals from the MPLAB ICD 2 are routed to seven wires soldered to the UPM at J3.
Vpp - Program Power
Vdd - Power
Vdd - Power
GND - Ground
GND - Ground
PGD - Program Data
PGC - Program Clock
You then jumper these wires to the appropriate pins of the 40-pin header, comprised of pins 1-20 and pins 21-40, which correspond to the pins of the ZIF socket (U1). For information onwhich pins to jumper, please refer to the programming specification for the device you will be programming.
Devices should be aligned to the top of the ZIF socket (pin 1 of all devices should be aligned to pin 1 of the ZIF socket). Refer to the device's data sheet for pinouts.
Both programming specifications and data sheets may be found on our website or on the MPLAB IDE CD-ROM.
Make sure that the programmer options are correct for your target device.
· Make sure the MPLAB ICD 2 is connected (Programmer>Connect).
· Select Programmer>Settings and select the Power tab.
· Check the "Power target circuit from MPLAB ICD 2" box, and press the Apply button. Ensure that Target Vdd is at least 4.5v (press the Update button if necessary)
· Select the Program tab of the ICD Programmer Properties dialog box. Configure your target device as desired. Press OK when done.
Programmer operations are now available. Insert the device to be programmed into the UPM ZIF socket and connect the signals wires per the previous section.
Due to the built-in in-circuit debugging capability of ICD devices, and the ICSP function offered by the Debugger, the MPLAB ICD 2 uses on-chip resources when debugging, i.e., some device resources are reserved for use by MPLAB ICD 2.
Refer to the on-line help for the most up-to-date list of resources used by the MPLAB ICD 2.