Searching \ for '[EE] ICD 2 connection problem' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: techref.massmind.org/techref/microchip/devprogs.htm?key=icd
Search entire site for: 'ICD 2 connection problem'.

Exact match. Not showing close matches.
PICList Thread
'[EE] ICD 2 connection problem'
2006\01\24@163558 by Dumitru Stama

flavicon
face

Well, it seems my luck has just ran out.
I have ( maybe it is not broken :-/ ) an Olimex clone of ICD2 and i
was using it to test my programs written in C18 for PIC18F452.
Everything worked like a charm until a certain moment when i tried to
update my latest version of the little program i was developing and
the ICD2 would not connect.
It gets into USB bus because i can see it in Device manager but MPlab
would not connect to it at all. When i am not using an external power
source it just sais :

Connecting to MPLAB ICD 2
ICD0021: Unable to connect with MPLAB ICD 2
MPLAB ICD 2 Ready

When i connect a 9v dc wall adapter to the interface the error changes
to :

Connecting to MPLAB ICD 2
ICD0019: Communications:  Failed to open port:
(Windows::GetLastError() = 0x2, 'The system cannot find the file specified.')
ICD0021: Unable to connect with MPLAB ICD 2
MPLAB ICD 2 Ready

I think it just died on me :-(
Is there someone on this list that had the same problem in the past
and fixed it somehow ? I am just starting to get paranoid about this
because everytime i tried to start with PICs i stopped at some point
but not because of me. I am reallllly close to just go and buy an
official ICD2 from a store near by but it is quite expensive ~250$.
Maybe you guys encountered this before and can guide me into fixing
this unfortunate event.

Thank you in advance for your time
Dumitru Stama

2006\01\24@175715 by John Hansen

picon face
FWIW, I've run into this error a number of times with my genuine
Microchip ICD2.  Sometimes if I close MPLAB and reopen it the problem
goes away.  Other times I have to reboot the computer and then it goes
away (save your work first!).  Anyway,  it always does go away.  Running
XP Pro here.

John Hansen


Dumitru Stama wrote:

>Well, it seems my luck has just ran out.
>
>Connecting to MPLAB ICD 2
>ICD0021: Unable to connect with MPLAB ICD 2
>MPLAB ICD 2 Ready
>
>  
>


2006\01\24@180021 by Shawn Wilton

picon face
Have you tried rebooting your computer?  Sometimes the simplest things work
wonders.  Just a thought.


On 1/24/06, Dumitru Stama <spam_OUTlistTakeThisOuTspammirosat.com> wrote:
{Quote hidden}

> -

2006\01\24@185634 by Bob Axtell

face picon face
I used to have the same problem repeatedly, until I decided to troubleshoot
it and found this out:

There is one inherently BAD problem with the ICD2, real or clone-
It has a very poor GND connection to the device under test. Its because
the ICD2 is referencing its ground with a single, flimsy #26 wire. There
may be more problems, but this one is very obvious.


Using some #22 AWG test probe wire (very flexible with many conductors),
attach the grounds of the ICD2 and the device being tested together.

I haven't had an ICD2 error since.

--Bob

John Hansen wrote:

>FWIW, I've run into this error a number of times with my genuine
>Microchip ICD2.  Sometimes if I close MPLAB and reopen it the problem
>goes away.  Other times I have to reboot the computer and then it goes
>away (save your work first!).  Anyway,  it always does go away.  Running
>XP Pro here.
>
>  
>

--
Note: To protect our network,
attachments must be sent to
.....attachKILLspamspam@spam@engineer.cotse.net .
1-520-850-1673 USA/Canada
http://beam.to/azengineer

More... (looser matching)
- Last day of these posts
- In 2006 , 2007 only
- Today
- New search...