When programming the PIC18LF452 with MPLAB 5.62 and PICSTART Plus firmware
revision 3.0, I occasionally experience a strange error.  Regardless of code
protect configuration, it automatically programs most code protect bits as
0.  All CP & table read protect bits are cleared, and table write 200-7fff
is also cleared (protected).  Then, when verifying the program write, the
error is detected, and it displays the code protect discrepancy.

I am now left with a code protected chip.  Attempts to erase the chip fail.
No error message is displayed, but the bits are not reset.  Thus, the chip
seems to be rendered unusable.

This error seems to occur sporadically; it occurred on two of the five chips
I tested.  It has never occurred on the 50+ F442s that have been through
this programmer in the past month, nor on any other chip I've programmed
here.  (I think that would rule out communication errors, although I don't
feel like stripping the cable and testing each line) :)

It may be a die problem (these *were* early adopter samples); it may be an
ESD problem; it may be an operator stupidity problem.  At this point, I have
no problem throwing these two chips away.  But I would really like to know
the cause.  Any ideas?

Jen

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics