Hello:

I'm wondering what thoughts you have about error-handling at the PIC level.
On the hardware side, you've got the WDT, but on the software side I'm
finding the need to check all sorts of things, both to catch and deal with
my own code errors, and also any errors caused by corrupted registers.  I'd
like to report errors serially, but it seems that if one register is corrupt
they all might be so it might be best to immediately reset the whole system.
If I could come up with a way to save the location, in the code, of the
error so that I can transmit it upon restart, that would be best.  And an
approach less drastic than all-or-nothing would be great too, if there is
such a thing.

I have the suspicion this has been a well-worked thread, but turned up
nothing in the archives.  If there's a thread I've missed can you tell me
what it's called?

Bruce Cannon
Style Management Systems
http://siliconcrucible.com
(510) 787-6870
1228 Ceres ST Crockett CA 94525

Remember: electronics is changing your world...for good!

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
use mailto:listserv@mitvma.mit.edu?body=SET%20PICList%20DIGEST