LockedICDwarn0020

Author
Guest
Super Member
  • Total Posts : 80499
  • Reward points : 0
  • Joined: 2003/01/01 00:00:00
  • Location: 0
  • Status: online
2004/02/22 17:35:39 (permalink)
0

ICDwarn0020

Hoping someone could help me get rid of an error i keep getting:
"ICDWarn0020: Invalid target device id (expected=0x13, read=0x0)"

I can do the following:
* I can connect to the device fine
* I can download the firmware to the ICD2 fine
* I can poll the ICD2 for the power settings it is currently using (Target Vdd, Vpp and ICD2 Vpp)
* passes a self test
* I have connected an external supply to the ICD2


My configuration settings for the ICD2 are as follows:
* Development environment: MPLAB v 6.40
* USB communication (only - no serial cable connection)
* auto connect at startup
* auto download of firmware if needed
* set the target to be powered by the ICD2

If you could advise on a way to fix this error i would appreciate it
Thankyou!
#1

9 Replies Related Threads

    Guest
    Super Member
    • Total Posts : 80499
    • Reward points : 0
    • Joined: 2003/01/01 00:00:00
    • Location: 0
    • Status: online
    RE: ICDwarn0020 2004/02/23 06:19:27 (permalink)
    0
    This is almost certainly a probalem with the connection to the PIC. Carefully check the PGC and PGD connections, ensuring there are no large resistor values in series (no more than a couple of hundred ohms). Even more important, ensure there are no capacitors connected directly to the MCLR pin, even a 0.1uF cap will prevent programming.
    #2
    Guest
    Super Member
    • Total Posts : 80499
    • Reward points : 0
    • Joined: 2003/01/01 00:00:00
    • Location: 0
    • Status: online
    RE: ICDwarn0020 2004/03/01 01:32:52 (permalink)
    0
    I have the same problem, but i have checked the connections.
    I have tried with both the PICDEM 2 board and my own printboard, but no succes.
    I have also tried wit a new MPLAB ICD2, but no succes. What could be wrong.
    Please help..
    Regards Mogens
    #3
    H H
    Administrator
    • Total Posts : 1197
    • Reward points : 0
    • Joined: 2003/11/07 00:00:00
    • Status: offline
    RE: ICDwarn0020 2004/03/01 07:30:08 (permalink)
    0
    Have you tried more than one device?
    Are you sure the device is operational? What device is it and what MPLAB IDE version are you using?

    hh
    #4
    Guest
    Super Member
    • Total Posts : 80499
    • Reward points : 0
    • Joined: 2003/01/01 00:00:00
    • Location: 0
    • Status: online
    RE: ICDwarn0020 2004/03/01 08:42:43 (permalink)
    0
    I am using the PICDEM 2 PLUS-board with PIC18F452, but have also tried 16F877. And I have tried our own print, but wanted to be sure it worked with the Microchip demo-board first. I have also tried a new MPLAB ICD2 but with no succes. I have measured the connections from the ICD2 to the demo-board and they were ok. I think it is some problem with the software in MPLAB or in the ICD2, but i am not sure.
    Regards Mogens.
    #5
    H H
    Administrator
    • Total Posts : 1197
    • Reward points : 0
    • Joined: 2003/11/07 00:00:00
    • Status: offline
    RE: ICDwarn0020 2004/03/02 08:21:02 (permalink)
    0
    Do you have a long cable between the ICD2 and the target board? Try switching the cable around and see if that makes a difference.

    What MPLAB IDE version are you using?

    hh
    #6
    Guest
    Super Member
    • Total Posts : 80499
    • Reward points : 0
    • Joined: 2003/01/01 00:00:00
    • Location: 0
    • Status: online
    RE: ICDwarn0020 2004/03/03 00:51:34 (permalink)
    0
    No the cable is the one that follows with the evaluations kit, appx. 30cm.
    I have tried with MPLAB 6.30, 6.40 and 6.42.
    Is there enything I can measure to be sure it is the hardware that fails, or something that makes sure that it is the software.
    Regards Mogens.
    #7
    H H
    Administrator
    • Total Posts : 1197
    • Reward points : 0
    • Joined: 2003/11/07 00:00:00
    • Status: offline
    RE: ICDwarn0020 2004/03/03 08:49:32 (permalink)
    0
    You may want to contact your local FAE or Microchip sales for a replacement.

    hh
    #8
    Olin Lathrop
    Super Member
    • Total Posts : 7463
    • Reward points : 0
    • Joined: 2004/02/26 17:59:01
    • Location: Littleton Massachusetts
    • Status: offline
    RE: ICDwarn0020 2004/03/03 13:09:49 (permalink)
    +1 (1)
    I wouldn't dismiss this so easily. There are some serious problems with the target board circuit recommended by Microchip. Many people at Microchip don't seem to be aware of the issue. I've spent quite a bit of time trying to figure out why a simple target circuit wouldn't work with the ICD-2 and my own programmer. Everything was wired according to the Microchip recommendations, but it still didn't work.

    I won't go into all the details here, but when the target chip drives the PGD line, that hard edge can couple onto the PGC line. There is absolutely nothing the programmer, ICD2, or whatever, can do about it at the other end of the standard RJ-12 cable. That's because the entire effect happens in less time than the propagation delay out the cable and back. Matters aren't helped by the fact that the PGD and PGC lines are next to each other in the cable.

    The solution I'm using for all new target boards now is to put 22pF on both lines to ground right at the connector on the target board. In addition, I put a 100 ohms in the PGD line from there to the PIC. This seems to work reliably. The resistor and cap slow down the PGD edges produced by the PIC, and the cap on the PGC line further reduces its susceptibility to coupled transients.
    #9
    Guest
    Super Member
    • Total Posts : 80499
    • Reward points : 0
    • Joined: 2003/01/01 00:00:00
    • Location: 0
    • Status: online
    RE: ICDwarn0020 2004/03/10 02:34:50 (permalink)
    0
    My demoboard is now up and running, my local microchip supplier was here and it was the ICD 2 that didn't work.
    The next step is to make my own target board work and here the problem with the warning is still present. (Read 0x0).
    I am using PIC18F6585 and have measure the following:

    When connecting(in MPLAB) to the target board, there comes no pulse on the MCLR-pin. I have tried the same on the demoboard and here there comes a pulse.

    When the connection to the targetboard is established, the PGC-pin goes from low to high. This is not happening on the demoboard.

    What could the problem be??
    I have checked all the connections for capacitors and resistors according to microchip's adwise.
    #10
    Jump to:
    © 2018 APG vNext Trial Version 4.5