I am about to use the WDT for the first time (ATMega16). I do not have a software problem in my device at the moment but I want to have the WDT active in my production application. From reading the full datasheet for the ATMega16 it seems that, after a WD reset, there is no way to determine what the value of the Program Counter was at the time. So how does one record information to determine where the bug might be in a situation where it is very difficult to reproduce the conditions that caused the software hang? I can have the application leave 'breadcrumbs' at different points but this would either take a lot of time to narrow in on or take a lot of 'breadcrumb' code.
Message
WatchDog Timer
2009-07-21 by Chuck Hackett
Attachments
- No local attachments were found for this message.