I use an old ICD2 (4 year) with MPlab 8.14 and it's working fine. However every version of mplab is worse than the previous... Luis Moreira wrote: > Hi Bob, > I use the ICD2 dally with MPlab 8.10 and it works fine, it never locked > up on me. > Best Regards > Luis > > > > -----Original Message----- > From: piclist-bounces@mit.edu [mailto:piclist-bounces@mit.edu] On Behalf > Of bob.axtell@gmail.com > Sent: 08 January 2009 22:47 > To: Microcontroller discussion list - Public. > Subject: Re: [PIC] MPLAB ICD2 burial > > You will experience problems with the ICD2 if you are using WinXP with > MPLAB later than version 7.6. MPLAB7.4 and 7.6 are the only versions > of MPLAB that reliably handle the ICD2. > > I operate for days without the slightest problems with MPLAB7.4; but > MPLAB v8 will choke at least once an hour. > > I have no idea why. > > --Bob > > > > On 1/5/09, Tony Vandiver wrote: > >> Hi Dwayne, >> >> Thanks for the tip - turns out the ICD2 is o.k. - I had another >> > bad > >> cable in the system supplying power to the target. What's wierd is >> > that > >> first, it came up reading the chip signature as zero - that's typical >> when the system isn't communicating with the target, but next it >> > started > >> saying that it failed the self test, and after a couple more tries, it >> stopped communicating at all saying that it had lost the USB >> connection. I rebooted everything and tried again and got the same >> > self > >> test failure (this test probably needs a powered target - I'm not >> > sure, > >> but I didn't think so since one of the things it's checking is the >> > MCLR > >> programming voltage - in this case it was reporting it low, and surely >> that's not supplied by the target?). That's when I gave up and tried >> the PICKIT2 and everything was rosy (after I figured out that I had a >> bad power supply cable to the target). It finally dawned on me that >> > the > >> ICD2 might be o.k. so I tried it and version 8.15a downloaded a new OS >> for me and now I'm programming again. So now I've got another ICD2 on >> the way and a working PICKIT2 and ICD2 on the bench - life is good. I >> suppose the moral of the story is not to call an ICD2 dead until it's >> actually been buried for a few days, and it always helps to have >> > another > >> programmer on hand to verify the target. >> >> Thanks, >> >> Tony >> >> >> Dwayne Reid wrote: >> >>> At 05:44 PM 1/5/2009, Tony Vandiver wrote: >>> >>> >>> >>>> (I'm sure that eventually it will even be worth the money it'll cost >>>> to replace the ICD2). >>>> >>>> >>> Here's the nice thing about the ICD2: it won't cost you a penny to >>> have it fixed. Head on over to support.microchip.com and register if >>> you have not already done so. Then request support. >>> >>> It will take a day or so for someone to get back to you but they will >>> wind up sending you a refurbished ICD2 along with return packaging >>> and instructions for your dead unit. >>> >>> Quick and painless! >>> >>> dwayne >>> >>> >>> >>> >> -- >> http://www.piclist.com PIC/SX FAQ & list archive >> View/change your membership options at >> http://mailman.mit.edu/mailman/listinfo/piclist >> >> -- http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist