Searching \ for '[PIC] ICD2 Failure' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: www.piclist.com/techref/microchip/devprogs.htm?key=icd
Search entire site for: 'ICD2 Failure'.

Exact match. Not showing close matches.
PICList Thread
'[PIC] ICD2 Failure'
2005\11\11@151331 by Josť M™ Vara

flavicon
face
Hi!

I have two ICD2 and both have the same problem: when connecting to the
device warning "Invalid target device id" is up. I have test all connections
and power lines and it is all rigth.

I think both ICD2 are broken, but I have no schemes to repair it, and I
don't know where to send them to repair...

Any idea?

Thanks in advance

José Mª Vara
NOVENTIA INGENIEROS, S.L.
Avda. Monelos 125-127, entlo. izq.
15009  A Coruña
Tlf: 981-139823
Fax: 981-060914
Correo: spam_OUTjvaraTakeThisOuTspamnoventiaingenieros.com

2005\11\11@153047 by Mario Mendes Jr.

flavicon
face
> Hi!
>
> I have two ICD2 and both have the same problem: when connecting to the
> device warning "Invalid target device id" is up. I have test all
> connections
> and power lines and it is all rigth.
>
> I think both ICD2 are broken, but I have no schemes to repair it, and I
> don't know where to send them to repair...
Hi Jose,

I have only experienced this once.  I was completely sure that I had
purchased a 16F877A when in reality what had been shipped to me had been a
16F877.

I spent hours and hours hitting my head against the wall until I finally
decided to check the print on the chip itself, that's when I saw that I
had been sent the wrong chip.

While it is possible that your ICD2's may be broken, double and tripple
check to make sure that you have the ICD2 configured for the correct chip
(check the print on it =).

Good luck.


-Mario

{Quote hidden}

>

2005\11\11@154753 by Thomas C. Sefranek

face picon face
Be SURE you don't have capacitors on the ICD CLOCK, DATA, or MCLR/PGM lines
on the PIC.  Classic error is to have a .1 uFd cap on the MCLR pin.
Also any resistors to low impedances on those lines have to be greater than
10K ohms. Classic error is to have reset driver on the MCLR pin which can
not take a 12 volt programming signal from the ICD.

Illegal loads will give you this message, as the ICD can not read the
device.

 *
 |  __O    Thomas C. Sefranek  tcsspamKILLspamcmcorp.com
 |_-\<,_   Amateur Radio Operator: WA1RHP
 (*)/ (*)  Bicycle mobile on 145.41MHz PL74.4
ARRL Instructor, Technical Specialist, VE Contact.
hamradio.cmcorp.com/inventory/Inventory.html
http://www.harvardrepeater.org
{Original Message removed}

2005\11\11@155447 by Andre Abelian

flavicon
face
jose,

you need to upload new operating system and program the target board.
microchip's product are very reliable hard to break them.

Andre


José Mª Vara wrote:

{Quote hidden}

>

2005\11\11@155708 by Wouter van Ooijen

face picon face
> I think both ICD2 are broken, but I have no schemes to repair
> it, and I
> don't know where to send them to repair...

the schematic is in the manual, you can download it from uChips's site

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: http://www.voti.nl
consultancy, development, PICmicro products
docent Hogeschool van Utrecht: http://www.voti.nl/hvu


2005\11\11@160747 by John Nall

picon face
José Mª Vara wrote:
> > I have two ICD2 and both have the same problem: when connecting to the
> device warning "Invalid target device id" is up. I have test all connections
> and power lines and it is all rigth.
>   I had the same problem with my ICD2 and it was a matter of the little cable (RJ11?  RJ12?  Whatever) that runs from the ICD2 to the target board having a poor connection.  Switching to another cable solved  the whole problem.
Joh

2005\11\11@171345 by James Humes
picon face
This may be too obvious but have you selected the proper device in MPLAB?
James

2005\11\11@172323 by olin piclist

face picon face
José Mª Vara wrote:
> I have two ICD2 and both have the same problem: when connecting to the
> device warning "Invalid target device id" is up. I have test all
> connections and power lines and it is all rigth.
>
> I think both ICD2 are broken, but I have no schemes to repair it, and
> I don't know where to send them to repair...

This may be a crosstalk problem.  See
http://www.embedinc.com/picprg/icsp.htm.


******************************************************************
Embed Inc, Littleton Massachusetts, (978) 742-9014.  #1 PIC
consultant in 2004 program year.  http://www.embedinc.com/product

2005\11\11@175250 by regen / Mailinglists

flavicon
face
And checked for own power-supply or supply by ICD2?

Jens

> -----Original Message-----
> From: EraseMEpiclist-bouncesspam_OUTspamTakeThisOuTmit.edu
> [piclist-bouncesspamspam_OUTmit.edu] On Behalf Of James Humes
> Sent: Friday, November 11, 2005 11:14 PM
> To: Microcontroller discussion list - Public.
> Subject: Re: [PIC] ICD2 Failure
>
> This may be too obvious but have you selected the proper
> device in MPLAB?
>  James
> -

2005\11\11@184749 by Peter van Hoof

face picon face
--- Wouter van Ooijen <@spam@wouterKILLspamspamvoti.nl> wrote:

> > I think both ICD2 are broken, but I have no schemes to repair
> > it, and I
> > don't know where to send them to repair...
>
> the schematic is in the manual, you can download it from uChips's
> site
>

It's not in the manual or on the microchip site, I have been looking
for it for a while.

I would guess Microchip learned from the original ICD which did have
diagrams and code on the rom and the microchip site. Copy's of it
showed up everywhere.


Peter van Hoof

2005\11\11@190019 by Bob Axtell

face picon face
John Nall wrote:

> José Mª Vara wrote:
>
>> > I have two ICD2 and both have the same problem: when connecting to the
>> device warning "Invalid target device id" is up. I have test all
>> connections
>> and power lines and it is all rigth.
>>  
>
> I had the same problem with my ICD2 and it was a matter of the little
> cable (RJ11?  RJ12?  Whatever) that runs from the ICD2 to the target
> board having a poor connection.  Switching to another cable solved  
> the whole problem.
> John

I have had the same problem. Solder a decent ground wire onto the USB Cable Shield Ground (exposed metal) and connect it to the PCB
you are working on.  It makes the ground much more reliable.

Think about it. You are depending on ONE tiny #24AWG wire as a ground for that sensitive application. Why they didn't go ahead and connect a second GND pin to that unused pin is beyond me...

--Bob
-- Note: To protect our network,
attachments must be sent to
KILLspamattachKILLspamspamengineer.cotse.net .
1-520-777-7606 USA/Canada
http://beam.to/azengineer

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