PicKit 2 WARNING
in [Design]
|
From: E on 14 Sep 2009 09:47 "Robert Baer" <robertbaer(a)localnet.com> kirjoitti viestiss�:V7ednUh1WdnzXDDXnZ2dnUVZ_qSdnZ2d(a)posted.localnet... > You can permanently destroy a PicKit 2 programming pod in an easy > un-documented manner. > 1) Tie one or more pins of a PIC MCU to ground; it does not help to have > MCU program use the pin(s) as inputs. > 2) Program then power up the MCU with the PicKit 2; you may need to do > power down and power up a few times. > ZZZZzzzzzaaaaaa:P:! No Poof, No Frap, No Zap; it just gets killed. > As far as i can tell the USP port is not damaged; my 1Gbyte stick still > reads OK. > > And the damn pods are not cheap. Have you tried updating it (tools ->Download Pickit2 Operating System) I have noticed it tends to lose its operating system if mishandled.
From: Jamie on 14 Sep 2009 12:23 Robert Baer wrote: > You can permanently destroy a PicKit 2 programming pod in an easy > un-documented manner. > 1) Tie one or more pins of a PIC MCU to ground; it does not help to have > MCU program use the pin(s) as inputs. > 2) Program then power up the MCU with the PicKit 2; you may need to do > power down and power up a few times. > ZZZZzzzzzaaaaaa:P:! No Poof, No Frap, No Zap; it just gets killed. > As far as i can tell the USP port is not damaged; my 1Gbyte stick still > reads OK. > > And the damn pods are not cheap. And are you talking about ? the USB-Serial adapter?
From: Robert Baer on 15 Sep 2009 01:16 David L. Jones wrote: > Robert Baer wrote: >> You can permanently destroy a PicKit 2 programming pod in an easy >> un-documented manner. >> 1) Tie one or more pins of a PIC MCU to ground; it does not help to >> have MCU program use the pin(s) as inputs. >> 2) Program then power up the MCU with the PicKit 2; you may need to do >> power down and power up a few times. >> ZZZZzzzzzaaaaaa:P:! No Poof, No Frap, No Zap; it just gets killed. >> As far as i can tell the USP port is not damaged; my 1Gbyte stick >> still reads OK. > > Do you know what exactly got fried? > From your description it appears as though the only overload path could be > if the programmed micro sets one of those grounded pins to a positive output > after it's programmed. That doesn't seem like it would be enough to destroy > the PICkit2 to me. You sure something else funny isn't going on? > >> And the damn pods are not cheap. > > Err, yes they are, at $35 it's one of the cheapest official programmers on > the market for any micro. > > Dave. > The program definitely sets the (offending?) pins to input - the state of most pins of MCUs are unknown and random until the MCU program sets their state. The pod is definitely ruined as the CPU program bitterly complains that the pod is not connected (when it is connected) even after clicking on (retry) communications; even if the pod is NOT connected to the (offending?) MCU. ** You must be *rich*; i am so poor that i cannot afford to pay attention...i am Socially Insecure - $35 is a week's of groceries so the dead pod means i go hungry.
From: Robert Baer on 15 Sep 2009 01:33 Frank Buss wrote: > David L. Jones wrote: > >> Robert Baer wrote: >>> You can permanently destroy a PicKit 2 programming pod in an easy >>> un-documented manner. >>> 1) Tie one or more pins of a PIC MCU to ground; it does not help to >>> have MCU program use the pin(s) as inputs. >>> 2) Program then power up the MCU with the PicKit 2; you may need to do >>> power down and power up a few times. >>> ZZZZzzzzzaaaaaa:P:! No Poof, No Frap, No Zap; it just gets killed. >>> As far as i can tell the USP port is not damaged; my 1Gbyte stick >>> still reads OK. > > I have no such problems with this test setup: > > http://www.frank-buss.de/pic18f2550/index.html > > The PIC is always powered from external power in my test setup. But I > noticed that the PicKit pulls VDD to low, if disabled, which was not much > of a problem, because of my current limited power supply, but I think this > could destroy the prorgammer. How does your schematic looks like? > >> Err, yes they are, at $35 it's one of the cheapest official programmers on >> the market for any micro. > > There are some other programmers within the same price range: > > http://search.digikey.com/scripts/DkSearch/dksus.dll?keywords=428-2021-ND > http://search.digikey.com/scripts/DkSearch/dksus.dll?keywords=336-1182-ND > > But you are right, there are more expensive ones, but then usually with > in-circuit debugging support etc. > I use the same programming scheme; the +5V was not activated and i tried running the MCU using the PicKit 2 as the power source. That Cypress programmer is only slightly less expensive and i think i am better off using a "known" where all software and hardware are from the same company.
From: Robert Baer on 15 Sep 2009 01:37
David L. Jones wrote: > Frank Buss wrote: >> David L. Jones wrote: >> >>> Robert Baer wrote: >>>> You can permanently destroy a PicKit 2 programming pod in an easy >>>> un-documented manner. >>>> 1) Tie one or more pins of a PIC MCU to ground; it does not help to >>>> have MCU program use the pin(s) as inputs. >>>> 2) Program then power up the MCU with the PicKit 2; you may need to >>>> do power down and power up a few times. >>>> ZZZZzzzzzaaaaaa:P:! No Poof, No Frap, No Zap; it just gets killed. >>>> As far as i can tell the USP port is not damaged; my 1Gbyte stick >>>> still reads OK. >> I have no such problems with this test setup: >> >> http://www.frank-buss.de/pic18f2550/index.html >> >> The PIC is always powered from external power in my test setup. But I >> noticed that the PicKit pulls VDD to low, if disabled, which was not >> much of a problem, because of my current limited power supply, but I >> think this could destroy the prorgammer. > > It can only pull VDD low with a 1K in series, so that isn't going to destroy > the programmer. > www.modtronix.com/products/prog/pickit2/pickit2%20datasheet.pdf > >>> Err, yes they are, at $35 it's one of the cheapest official >>> programmers on the market for any micro. >> There are some other programmers within the same price range: >> >> http://search.digikey.com/scripts/DkSearch/dksus.dll?keywords=428-2021-ND >> http://search.digikey.com/scripts/DkSearch/dksus.dll?keywords=336-1182-ND >> >> But you are right, there are more expensive ones, but then usually >> with in-circuit debugging support etc. > > The PICkit2 has in-circuit debugging capability, stand-alone field > programming support, and can power your circuit under test with any voltage > from 2.8V to 5V. And as a bonus can be used as a 4 logic analyser and serial > protocol analyser too. Pretty good value for money! > > Dave. > There was NO (1K) "protection" resistor (8 lines) from MCU to ground; at worst 2 pins were shorted. |