On Wed, May 12, 2010 at 3:30 PM, Barry Gershenfeld <gbarry42@gmail.com> wro=
te:
>> So, I guess my question is now...has anyone ever had a chip that
>> accepted a program and ran in debug mode, but refused to debug?
>
> Many times. It seems that the transactions over the ICD connection are
> sensitive to electrical things, and debug seems to make many small
> transactions, which is different than the program/verify kind of behavior.
> The best fix I arrived at over the years was to shorten the ICD cable from
> 19" to about a foot (50 cm to 30 cm). =A0And I'm prepared to go shorter i=
f it
> acts up again.

Interesting. My PK3 is attached with an inch and a half cable to my
circuit. Your post did give me an idea though. I thought perhaps the
debug executive was somehow corrupted. I switched to release mode,
rebuilt, and programmed, which worked fine. Then I switched back to
debug, rebuilt, and tried to download to the chip. This is the error I
got:

Programming...
The following memory regions failed to program correctly:
Debug Executive
Programming failed

I'm going to do a bit more programming with the simulator, then I
guess I'll remove the chip and replace it. I guess I'm also concerned
because I'm so unsure what causes this that I don't want to ruin
another chip when it happens again.

Thanks,

Josh
-- =

A common mistake that people make when trying to design something
completely foolproof is to underestimate the ingenuity of complete
fools.
        -Douglas Adams

-- =

http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist