JMGross wrote:
:
I you require a WDT for environment stability (and not just to circumvent code
deadlocks due to poorly written code) then the WDT may not be disabled EVER. It
is on at startup and it has to stay on. period.
If you don't need it, well, maybe a faster startup that disables WDT is nice. And if you KNOW that htis happens wihtout digging into linker listings or library source code, it is even nicer. But in case you NEED the
WDT to ensure device crash recovery, there must be a way to never disable it at all.
:
Good point. But what should one do in low power applications where the
µC is _most_ of the time in LPM3? Eg my application allows LPM3
durations of 16s. How does that fit with a WDT with 1s timeout?
Hardy
