AVR-Chat

On Tue, Jul 21, 2009 at 4:01 AM,
s.holder123@btinternet.com<s.holder123@btinternet.com> wrote:
>
>
> Just a minor point, the newer range of AVR devices , (atmega168, xmega etc)
> have the capability of mapping the watchdog timeout to an interrupt rather
> than a reset,

Check the errata, that doesn't work in some parts.

A bad recovery can actually be more dangerous  that crashed code
if done wrong.

> 1) The dark art of assertion Macros, these can prove inavluable in
> determining a porblem area of code.

http://directory.fsf.org/project/nana/
may be better.

>
> 2) Just before you "Tickle/Kick" the watchdog include a routine for writing
> a value to an eeprom area a bytye should do it,

That could wear out a EEPROM block fast.  Even if just used in debugging mode.
You should always debug the code you ship.  Having debug mode and a ship mode
is not wise.


> 1) Build a watchdog task which is the only part of the software that is
> allowed to tickle the watchdog.

http://www.ganssle.com/watchdogs.pdf

-- 
http://www.softwaresafety.net/
http://www.wearablesmartsensors.com/
http://www.designer-iii.com/
http://www.unusualresearch.com/