I posted this question a while back but with an incorrect tag,
so some people might not have seen it.

I am infrequently seeing corruption of the Flash memory on an
16F877A device. I first suspected my "bootloader" routine (which
actually doesn't program on boot-up), but I can't find a reason
why it would jump into the programming routine at just the right
point to corrupt the memory, bypassing the normal checks on
the data to be programmed (comparing length and checksum). I'm
running at 5V +/-2% with brown-out detect enabled and triggering
at very close to the nominal 4.0 V. Any ideas what, besides a
code bug, could be corrupting the program memory?

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