Searching \ for '[PIC] PicKit 3 damaged?' 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/devices.htm?key=pic
Search entire site for: 'PicKit 3 damaged?'.

Exact match. Not showing close matches.
PICList Thread
'[PIC] PicKit 3 damaged?'
2010\07\19@201616 by David Duffy (AVD)

flavicon
face
I bought a PicKit 3 recently so I can start using ICSP with my
products.  All was going well for my first ICSP project (using a 16F88)
and the programmer worked well.

The target PCB (5V, powered from the programmer) was connected to a DMX
lighting desk, as well as a DMX LED light.

I then took the PicKit 3, target board and the LED light home to
continue working on the firmware. I connected the DMX LED light to the
target board first, then the PicKit 3.

MPLAB gave the usual "PicKit 3 connected" message, but then said it
needed to do an AP & RS upgrade, which I let it do.  This seemed a
little odd, as it did the same thing at work the first time is was
connected and I had the same project and version of MPLAB in both places.

Now, I'm fairly sure I saw a small spark as the programmer pins touched
the ICSP pads on the target board. This may have been leakage from the
DMX LED light, but I can't be sure.

Anyway, MPLAB then complained "Target ID (0000000) does not match the
device ID (00000760)" and now will not program my board.  Re-testing the
original setup back at work, and with the demo board that came with the
programmer gives the same result, so I'm reasonable sure the target
board is OK. (it still works)

I checked the components around the PicKit's PGC & PGD lines, but all
seems OK.  I even replaced the SMD I/O chips for these lines with no change.

Have I fried my PicKit 3?  Is it a dog of a programmer and should I just
buy a PicKit 2 instead?
David...

--
___________________________________________
David Duffy        Audio Visual Devices P/L
Unit 8, 10 Hook St, Capalaba 4157 Australia
Ph: +61 7 38235717      Fax: +61 7 38234717
Our Web Site: http://www.audiovisualdevices.com.au
___________________________________________

2010\07\19@211006 by Bob Axtell

face picon face
I was not able to get my brand-new PICKIT3 to work either...

--Bob A

David Duffy (AVD) wrote:
{Quote hidden}

2010\07\19@215520 by David Duffy (AVD)

flavicon
face
What error do you get?

On 20/07/2010 11:10 AM, Bob Axtell wrote:
> I was not able to get my brand-new PICKIT3 to work either...
>
> --Bob A
>
> David Duffy (AVD) wrote:
>> Anyway, MPLAB then complained "Target ID (0000000) does not match the
>> device ID (00000760)" and now will not program my board.  Re-testing the
>> original setup back at work, and with the demo board that came with the
>> programmer gives the same result, so I'm reasonable sure the target
>> board is OK. (it still works)
>>
>> I checked the components around the PicKit's PGC&  PGD lines, but all
>> seems OK.  I even replaced the SMD I/O chips for these lines with no change.
>>
>> Have I fried my PicKit 3?  Is it a dog of a programmer and should I just
>> buy a PicKit 2 instead?
>> David...
>>      

--
___________________________________________
David Duffy        Audio Visual Devices P/L
Unit 8, 10 Hook St, Capalaba 4157 Australia
Ph: +61 7 38235717      Fax: +61 7 38234717
Our Web Site: http://www.audiovisualdevices.com.au
___________________________________________

2010\07\19@222904 by Xiaofan Chen

face picon face
On Tue, Jul 20, 2010 at 9:55 AM, David Duffy (AVD)
<spam_OUTdavidTakeThisOuTspamaudiovisualdevices.com.au> wrote:
> What error do you get?

For me I got the following connection problem with PICkit 3.
http://www.microchip.com/forums/tm.aspx?m=467684

Many more people got one of the following two problems with PICkit 3.
1) Update firmware for the PICkit 3 and you get a light-weight brick
www.microchip.com/forums/tm.aspx?m=468826
2) PK3Err0038 Failed to initialize PICkit 3 problem
http://www.microchip.com/forums/tm.aspx?m=474136

I think they have since improved the situation but still the
problems are still there.

--
Xiaofan

2010\07\19@223741 by David Duffy (AVD)

flavicon
face
On 20/07/2010 12:28 PM, Xiaofan Chen wrote:
> For me I got the following connection problem with PICkit 3.
> http://www.microchip.com/forums/tm.aspx?m=467684
>
> Many more people got one of the following two problems with PICkit 3.
> 1) Update firmware for the PICkit 3 and you get a light-weight brick
> www.microchip.com/forums/tm.aspx?m=468826
> 2) PK3Err0038 Failed to initialize PICkit 3 problem
> http://www.microchip.com/forums/tm.aspx?m=474136
>
> I think they have since improved the situation but still the
> problems are still there.

Hmmm... mine seems to have a different fault than any of those links.

Because it did the update just before I connected it to my target board,
I can't be sure if it's a hardware or firmware failure.

Would it be worth buying a PicKit 2 anyway?  I assume they're still a
useful device?
David...

--
___________________________________________
David Duffy        Audio Visual Devices P/L
Unit 8, 10 Hook St, Capalaba 4157 Australia
Ph: +61 7 38235717      Fax: +61 7 38234717
Our Web Site: http://www.audiovisualdevices.com.au
___________________________________________

2010\07\19@232515 by Funny NYPD

picon face
There are lot of ICD2 "gene" in PK3 hardware and software architecture, so don't
be surprise when the PK3 gets the same issue as ICD2 had, or it can get even
worse when some of the ICD2 hardware are cost-reduced in PK3.


Now, there isn't much choice for most of the PIC users:
1. If you don't care about money, go to ICD3, it is faster, and it also has a
free replacement support when it malfunctions.
2. Or, you can get a PK2, which is stable and reliable after these many years
accumulation of developments (by Microchip PK2 team, PK2 communities, and third
parties.). Overall, the PK2 is a nicely designed product from Microchip.


Funny N.
Au Group Electronics, http://www.AuElectronics.com
http://www.AuElectronics.com/products
http://augroups.blogspot.com/




________________________________
From: David Duffy (AVD) <.....davidKILLspamspam@spam@audiovisualdevices.com.au>
To: Microcontroller discussion list - Public. <piclistspamKILLspammit.edu>
Sent: Mon, July 19, 2010 8:16:12 PM
Subject: [PIC] PicKit 3 damaged?

I bought a PicKit 3 recently so I can start using ICSP with my
products.  All was going well for my first ICSP project (using a 16F88)
and the programmer worked well.

The target PCB (5V, powered from the programmer) was connected to a DMX
lighting desk, as well as a DMX LED light.

I then took the PicKit 3, target board and the LED light home to
continue working on the firmware. I connected the DMX LED light to the
target board first, then the PicKit 3.

MPLAB gave the usual "PicKit 3 connected" message, but then said it
needed to do an AP & RS upgrade, which I let it do.  This seemed a
little odd, as it did the same thing at work the first time is was
connected and I had the same project and version of MPLAB in both places.

Now, I'm fairly sure I saw a small spark as the programmer pins touched
the ICSP pads on the target board. This may have been leakage from the
DMX LED light, but I can't be sure.

Anyway, MPLAB then complained "Target ID (0000000) does not match the
device ID (00000760)" and now will not program my board.  Re-testing the
original setup back at work, and with the demo board that came with the
programmer gives the same result, so I'm reasonable sure the target
board is OK. (it still works)

I checked the components around the PicKit's PGC & PGD lines, but all
seems OK.  I even replaced the SMD I/O chips for these lines with no change.

Have I fried my PicKit 3?  Is it a dog of a programmer and should I just
buy a PicKit 2 instead?
David...

--
___________________________________________
David Duffy        Audio Visual Devices P/L
Unit 8, 10 Hook St, Capalaba 4157 Australia
Ph: +61 7 38235717      Fax: +61 7 38234717
Our Web Site: http://www.audiovisualdevices.com.au
___________________________________________

2010\07\19@233103 by Funny NYPD

picon face
>Many more people got one of the following two problems with PICkit 3.
>1)  Update firmware for the PICkit 3 and you get a light-weight brick
>www.microchip.com/forums/tm.aspx?m=468826
>2)  PK3Err0038 Failed to initialize PICkit 3 problem
>http://www.microchip.com/forums/tm.aspx?m=474136

>I  think they have since improved the situation but still the
>problems  are still there.

Some of  those issue happened on ICD2 too (released decades ago, now the ICD2 is
in the end of its life. If you only use one type of PIC chip, ICD2 is a good bet
too.), and Microchip's ICD2 team (Now, part of PK3 team) is still scratching
their head, and cannot figure out what is wrong. So much for "Downloading new os
for each PIC chip, ......".

Funny N.
Au Group Electronics, http://www.AuElectronics.com
http://www.AuElectronics.com/products
http://augroups.blogspot.com/




________________________________
From: Xiaofan Chen <.....xiaofancKILLspamspam.....gmail.com>
To: Microcontroller discussion list - Public. <EraseMEpiclistspam_OUTspamTakeThisOuTmit.edu>
Sent: Mon, July 19, 2010 10:28:57 PM
Subject: Re: [PIC] PicKit 3 damaged?

On Tue, Jul 20, 2010 at 9:55 AM, David Duffy (AVD)
<davidspamspam_OUTaudiovisualdevices.com.au> wrote:
> What error do you get?

For me I got the following connection problem with PICkit 3.
http://www.microchip.com/forums/tm.aspx?m=467684

Many more people got one of the following two problems with PICkit 3.
1) Update firmware for the PICkit 3 and you get a light-weight brick
www.microchip.com/forums/tm.aspx?m=468826
2) PK3Err0038 Failed to initialize PICkit 3 problem
http://www.microchip.com/forums/tm.aspx?m=474136

I think they have since improved the situation but still the
problems are still there.

--
Xiaofan

2010\07\19@233749 by Xiaofan Chen

face picon face
On Tue, Jul 20, 2010 at 10:37 AM, David Duffy (AVD)
<@spam@davidKILLspamspamaudiovisualdevices.com.au> wrote:
> Would it be worth buying a PicKit 2 anyway?  I assume they're still a
> useful device?

I would go for an ICD 3. It is way faster than PICKit 2, PICkit 3 or ICD 2.
And it seems to me that you are doing real work and not a hobbyist.
In that case, then the investment into ICD 3 is well worth the money.

Despite being labeled as a PICkit 2 apologist by Olin, I no longer
really use PICkit 2. Rather I use an ICD 3 for my PIC 32 experiment
(not work related). PICkit 2 can not really be used for PIC32 since
it does not support debugging for PIC 32.

--
Xiaofan http://sourceforge.net/projects/libusb-win32/

2010\07\20@003011 by David Duffy (AVD)

flavicon
face
Hmmm... that reminds me.  We actually bought an ICD2 some time back, but
never used it IIRC.

Maybe I should dig it out and see it it works!
David...

On 20/07/2010 1:37 PM, Xiaofan Chen wrote:
> I would go for an ICD 3. It is way faster than PICKit 2, PICkit 3 or
> ICD 2.
> And it seems to me that you are doing real work and not a hobbyist.
> In that case, then the investment into ICD 3 is well worth the money.
>    
--

___________________________________________
David Duffy        Audio Visual Devices P/L
Unit 8, 10 Hook St, Capalaba 4157 Australia
Ph: +61 7 38235717      Fax: +61 7 38234717
Our Web Site: http://www.audiovisualdevices.com.au
___________________________________________

2010\07\20@004755 by Funny NYPD

picon face
If you got more than one ICD2, Only use each ICD2 for one type of PIC (you can
put a mark of the chip type on the case), it will work.

No new OS will need to be downloaded on this case.

Funny N.
Au Group Electronics, http://www.AuElectronics.com
http://www.AuElectronics.com/products
http://augroups.blogspot.com/




________________________________
From: David Duffy (AVD) <KILLspamdavidKILLspamspamaudiovisualdevices.com.au>
To: Microcontroller discussion list - Public. <RemoveMEpiclistTakeThisOuTspammit.edu>
Sent: Tue, July 20, 2010 12:29:57 AM
Subject: Re: [PIC] PicKit 3 damaged?

Hmmm... that reminds me.  We actually bought an ICD2 some time back, but
never used it IIRC.

Maybe I should dig it out and see it it works!
David...

On 20/07/2010 1:37 PM, Xiaofan Chen wrote:
> I would go for an ICD 3. It is way faster than PICKit 2, PICkit 3 or
> ICD 2.
> And it seems to me that you are doing real work and not a hobbyist.
> In that case, then the investment into ICD 3 is well worth the money.
>    
--

___________________________________________
David Duffy        Audio Visual Devices P/L
Unit 8, 10 Hook St, Capalaba 4157 Australia
Ph: +61 7 38235717      Fax: +61 7 38234717
Our Web Site: http://www.audiovisualdevices.com.au
___________________________________________

2010\07\20@140834 by Bob Axtell

face picon face
The PICKIT3 failed to enumerate, I guess. Windows never recognized it.
It was almost a year ago, at home.

--Bob A

David Duffy (AVD) wrote:
{Quote hidden}

2010\07\20@213801 by Xiaofan Chen

face picon face
On Wed, Jul 21, 2010 at 2:08 AM, Bob Axtell <spamBeGoneengineerspamBeGonespamcotse.net> wrote:
> The PICKIT3 failed to enumerate, I guess. Windows never recognized it.
> It was almost a year ago, at home.
>

Often adding a USB hub (especially powered) will help such issues.

--
Xiaofan http://sourceforge.net/projects/libusb-win32/

2010\07\20@220114 by Funny NYPD

picon face
Yes. USB hub does help a lot.


Funny N.
Au Group Electronics, http://www.AuElectronics.com
http://www.AuElectronics.com/products
http://augroups.blogspot.com/




________________________________
From: Xiaofan Chen <TakeThisOuTxiaofancEraseMEspamspam_OUTgmail.com>
To: Microcontroller discussion list - Public. <RemoveMEpiclistspamTakeThisOuTmit.edu>
Sent: Tue, July 20, 2010 9:37:59 PM
Subject: Re: [PIC] PicKit 3 damaged?

On Wed, Jul 21, 2010 at 2:08 AM, Bob Axtell <engineerEraseMEspam.....cotse.net> wrote:
> The PICKIT3 failed to enumerate, I guess. Windows never recognized it.
> It was almost a year ago, at home.
>

Often adding a USB hub (especially powered) will help such issues.

--
Xiaofan http://sourceforge.net/projects/libusb-win32/

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