Did you say your Vdd was 3.3V?  Does the ICD2 support programming that
part with that Vdd?

On Mon, 21 Aug 2006, Harold Hallikainen wrote:

> OK, MPLAB 7.41 did not fix the problem. I guess use of another programmer
> (like PM3) would be ok, but how am I supposed to debug stuff without the
> ICD-2? This used to work fine! I really count on the use of the ICD-2 for
> debug. It's a whole lot easier than just staring at the code trying to see
> what's wrong (or even running it through the simulator, which doesn't
> simulate all our hardware). This is really bad if we can't get the ICD
> running! Again, until last week, it worked great! I dunno what changed. I
> had not done an MPLAB upgrade in a while (I was running 7.31), so the ICD
> firmware should not have changed. Now I'm running 7.41 in the hopes that
> would fix the problem, but it did not. Here's the output when I try to
> program the chip for debug:
>
> MPLAB ICD 2 Ready
> Resetting Target
> MPLAB ICD 2 Ready
> Programming Target...
> ...Validating configuration fields
> ...Erasing Part
> ...Programming Program Memory (0x0 - 0x6AFF)
> ...Loading DebugExecutive
> ...Programming DebugExecutive
> ...Programming Debug Vector
> ...Programming RSBUG
> Verifying...
> ...Program Memory
> ICD0161: Verify failed (MemType = Program, Address = 0x0, Expected Val =
> 0xD00C, Val Read = 0x0)
> ICD0275:  Programming failed.
> MPLAB ICD 2 Ready
>
>
> Any ideas as to what to do for debug? We can get another programmer for
> production, but we need to debug!
>
> Thanks!
>
> Harold
>
>
> -- 
> FCC Rules Updated Daily at http://www.hallikainen.com - Advertising
> opportunities available!
> -- 
> http://www.piclist.com PIC/SX FAQ & list archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist
>

--
John W. Temples, III
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist