AVR-Chat

>
>
> As a general rule its always bad to write loops with only one possible
> exit. At the least you should provide a time out exit. Or enable the
> watchdog timer and kick the dog once prior to entering the above loop.


I've tried really hard to write my apps so that there is only one WDR, in
the main loop, behind some sanity-checking code like looking at the stack
pointer and critical data.

A convenient thing also, is a "halt and DONT catch fire" routine.
One that puts everything in a safe state and waits for a reset.
Some projects don't need it, but if you have hardware that could be damaged
by hanging in a random state, it's a good idea.


[Non-text portions of this message have been removed]