Olin Lathrop wrote:

> It's unlikely that random buggy code would write to the EEPROM.  A
> special write "unlock" sequence has to be performed before each
> write.  Of course that doesn't prevent a bug from erroneously calling
> or jumping into the routine that performs the unlock and write (which
> is why I think such interlocks are silly).

I wonder if the OP forgot to disable interrupts when performing the
"unlock" sequence.

michael brown

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@mitvma.mit.edu with SET PICList DIGEST in the body