Register | Login | Help | Feedback | SiteMap | Add to favorites | Currency:

Home About US Products Payment Download News Quotation Ebay Forum
2012-9-13 Search Advanced Search
0 Items (US $ 0.00) Checkout Account
News & Events
All>>
News
  Company News
  Other News
  Home >> News & Events >> ICD2/MCD2 summary of frequently asked questions
ICD2/MCD2 summary of frequently asked questions

Author:  From:  Date:2011-2-23

ICD2 debug when "ICD0083: Debug: Unable to enter debug mode. Please double click this message for more information."

  Usually this means that ICD2 or MCD2 can not debug executive communications, which may be made target clock or power supply problem or MCD2 ICD2 debugger can not communicate implementation procedures to ensure that the crystal pins and OSCKI / OSCKO fully close, 4MHz crystal above HS mode is recommended if an external 32K low-frequency oscillator, re "connect" click the executable debug command, there may be internal or external crystal oscillator to the PLL function can not enter the Debug mode, you can turn off the PLL; and then also may be caused by improper configuration bit settings, see Config> Configuration Bits, to ensure that the watchdog is disabled, code protection, brownout detection is turned off

  ICD2 connected to display "ICD0021: Unable to connect with MPLAB ICD 2"?

  Please check ICD2 or MCD2 the communication port connected to the computer is set up correctly (USB or COM).

  ICD2 connected to display "ICD0286: Unable to communicate with ICD

  ICD0082: Failed MPLAB ICD 2 operation "

  This may be the operating system is wrong, then you can manually download the operating system.

  Display when connected ICD2 or MCD2 "ICD0019: Communications: Failed to open port: (Windows:: GetLastError () = 0x2, 'system can not find the file specified.') ICD0021: Unable to connect with MCU."

  ICD2 or MCD2 drive is usually not found to be reinstalled. If MPLAB IDE V7.0 or later, reload the former first run C: \ Program Files \ Microchip \ MPLAB IDE \ Utilities \ MPUsbClean completely removed under the MPUsbClean.exe

  ICD2 or MCD2 self without prompt "... Failed Self Test. See ICD2 Settings (status tab) for details"

  ICD2 or MCD2 self mainly on Target Vdd, Target Vpp, MCLR GND, MCLR Vdd MCLR Vpp voltage detection pin of six, no one will pass, but not normal. The specific circumstances of an error in the status bar in the ICD2 to view, find the wrong item, then check the relevant hardware connection. If PIC18J, PIC24, dsPIC30, dsPIC33 series of devices, is not from the ICD2 or MCD2 power to them, requiring the target board external power supply, and pay attention to their voltage range.

  Note: Some chips may be prompted to Vpp High leading to self-test pass, this is the firmware in the ICD2 Vpp voltage detection upper limit set by the threshold due to small, often negligible, ICD2, or to resume normal programming and debugging

  When using the USB connection MCD2 host PC, to note: at this time MCD2 host can not supply power to the target board, must be included with the product's power supply to the target board or MCD2 host (make sure to enable the target host from the MCD2 access to power), proposed to supply directly to the target.

ICD2 or MCD2 self-test passed, but the tips did not find the target ID, read ID is '0 ', indicating "ICDWarn0020: Invalid target device id (expected = 0x89, read = 0)"

  At this point the primary task is to check the hardware connections, PGC / PGD without a wrong, or PGD / PGC has capacitive load or inductive load. If PIC18J device, make sure vddcore is enabled and connected to the foot of the 0.1-10uF low ESR capacitors. Note: ICD2 cable to the target board header if one end of the crystal, one end of the pin, and pay attention to is the first root of the blue, white is generally not used.

  Microchip factory production of ICD, the order of the line should be: white - VPP, Black - VCC, Red - GND, Green - PGD, yellow - PGC, blue - no, MCD2 also follow this arrangement way. However, white or blue is a VPP VPP, need not be too concerned, as long as six lines do not cross it.

  ICD2 self-test passed, but the tips did not find the target ID, read the ID is not '0 'but does not meet expectations and to show "ICDWarn0020: Invalid target device id (expected = 0x89, read = 0x71)"

  First check the chip type selection is correct; Debug mode, if the prompt appears, confirm whether the selected MCU header before or MCD2 through ICD2 debugger. If the prompt appears with the header, then check the header to set the ADC on the enable / disable the jumper, the jumper will also affect the target device's ID.

  ICD2 programming tips programming was successful but the validation fails

  First check the PGC / PGD without outside interference circuit, and look at 4.5V Vdd has not reached more than (PIC18J/PIC24/dsPIC33F series except), ICD2 or MCD2 on the first full-chip programming rub, for the majority of the implementation of PIC "Bulk Erase" when the minimum voltage Vdd is 4.5V. This requires that even the LF version of the PIC in programming with ICD2 Vdd is at least 4.5V, of course, after the compilation process can still finish in the low voltage (3V) using the ICD2 to debug.

  If the chip has AVdd and AVss feet, respectively, in the ICSP programming received the Vdd and Vss, otherwise this error will appear.

  Some chips use an internal oscillator and internal use reduction, such as the PIC16F630/690, etc. When programming with ICD2 or MCD2 Once the internal oscillator and internal reset can be a warning message:

  ICDWarn0033: You have selected Internal MCLR and Internal Oscillator in your configuration settings. If your code makes use of port pins that correspond to Clock and Data pins in programming mode, you may not be able to reprogram your device. See on-line help for this warning for more information. (OK / Cancel)

  Ignore the information, the initial programming of the chip can be successfully ICD2. However, if the chip configuration word is already in the internal crystal oscillator and internal reset procedure, and the program has on the operation of ICSPCLK and ICSPDAT pins, once again the failure of programming will have parity error. This is because when using the internal oscillator and internal reset, ICD2 and the target board or MCD2 Once connected, the target chip, already working, ICD2 control of ICSPCLK and ICSPDAT feet by the target chip, the operation of this disruption, and therefore can not enter the programming mode. At this time to consider other programming tools, or the beginning of the program plus more than 2ms delay the implementation of procedures to ensure chips before actually entering the programming mode. May also be taking up some resources ICD2 caused.

  MCD2 upcoming programming module (when buying MCD2 gift products) are specifically designed to do to solve this problem.

Debugging or programming with ICD2 PIC16F630/676, PIC12F629/675 devices such as with internal RC connected ICD2 warned "ICDwarn0044: Target has an invalid calibration memory value (Value). Continue?"

  This is the program memory of these devices within the last unit on the RC calibration values (retlw xx) is modified, can be used to re-generate a value PICkit 1; also available on the MPLAB IDE's Programmer - settings - calibration memory card option to Allow ICD2 to program calibration memory hook before reloading a new value marked, programming connected again no problem.

Why in the configuration phase-locked loop (PLL) oscillator problem, ICD2 is suspended?

  PICmicro microcontrollers is required. Oscillator in the PLL configuration bit programming, the power to disconnect and then add to the target board. If you have not done so, the target PICmicro MCU will not clock. No clock, debug mode will not be able to work. Similarly, if switching to PLL mode, the power was not disconnected and then connected the device may run, but did not use the PLL.

ICD2 or MCD2 or PIC16F630/676 PIC12F629/675 in debug, why would Invalid target device id warning?

  Using the MPLAB ICD2 ICD2 or MCD2 header and debugging process of these devices, these devices GP1/RA1 pin can not be pulled, or will warn Invalid target device id. See the MPLAB ICD 2 Header document.

ICD2 or MCD2 step, the timer is why the run is not normal?

  This is the disadvantage of using the one-line debugger. Since the code is actually running the program in the debugger implementation, the implementation of the debug program is running, even if the user's application is suspended, the timer will continue to run.

ICD2 RETFIE command to use by high-priority interrupt, why W, STATUS and BSR registers will change?

  For high-priority interrupt and CALL FAST's shadow register is used MPLAB ICD 2. These are reserved for the MPLAB ICD 2 operation resources. If the breakpoint is set within a subroutine CALL FAST, or instruction through the use of RETURN FAST or the shadow register RETFIE high priority within the interrupt service routine will be a problem.

  dsPIC debugging using ICD2 or MCD2 line interface options

  In some cases, dsPIC programming and debugging the default pin function PGC / EMUC and PGD / EMUD, may be associated with other peripherals (such as I2CTM, SPI or UART modules, etc.) pins. In this case, the application can these pins for programming, but not for online debugging. At this point you should use online backup debug debug channel, EMUC/EMUD1, EMUC2/EMUD2 or EMUC3/EMUD3, please refer to the specific circuit design 152816.pdf document.

ICD2 or MCD2 starting position in the program when setting a breakpoint, why it stops at the address 0x0001, but not the address 0x0000?

  MPLAB ICD 2 in the breakpoint on the instruction after the pause. This means that the breakpoint instruction address 0000 will be executed, then when it finds a breakpoint, the program counter will point to address 0001. If you need to code the first instruction of its suspension, they must be at address 0000 to insert a NOP instruction.

  Not on the ICD2 or MCD2 communication;

  Possible operating system error, this time need to send the original to re-download; also possible to upgrade the module motherboard no contact with the good.

ICD2 debugging or MCD2 when ICDWarn0015: Program memory has changed since last program operation?

Program modifications without re-compilation, programmed into the chip in

When connected ICD2 or MCD2 ICD0152: Failed to read all of requested bytes (0x0 of 0x8)?

  First of all, ICD2 or MCD2 USB or serial port is connected with the computer? If the serial port connection, serial port attributes change it, follow these steps:

  Right-click My Computer - Properties - Hardware - Device Manager - Ports (COM) - COM1 (If you use other COM, then select the appropriate COMx) - properties - port settings, where do the two two settings:

1, Flow Control - Select Hardware

2, click the "Advanced" button - Use FIFO buffers ... in front of the hook removed. After setting may also need to restart the computer. Second, the upgrade version of what IDE.

When finished burning program PICKit2 Warning - No configuration word found in hex file?

That is because the procedures do not include programming Config information required in the MPLAB IDE configbits set of specific steps:
1, open MPLAB IDE;
2, through the file-> import, open the HEX file to be programmed;
3, configbits set;
4, through file-> export, export the HEX file.
5, when the HEX file is the config information contains HEX files, so programming would then PICKIT2 should not prompt the error.

About US
About US
Contact US
Payment
PayPal
China Bank
Shipping
Express Delivery
Post Office
Service
Return Policy
Service

Links:                           
Shen Zhen QLS Elecrtonic TECHNOLOGY CO.,LTD.
ADD:Huiningge 13G,QianLong garden,Longhua,ShenZhen,GuangDong P.R.China.
Postalcode:518131     TEL:+86-0755-28187975-602   FAX:+86-0755-28187976
E-Mail:qls@cxqmcu.com   MSN:qls@cxqmcu.com