AVR-Chat

Chuck -

My experience is that a watchdog timer is simply a reset of last  
resort, after the horses are out of the barn, but hopefully before  
they have wandered to some place dangerous. I know of no way to read  
the watchdog timer. You only know when it has timed out.

I personally don't try to keep a bread crumb trail. I'm just thankful  
that it got reset. I have not had a known watchdog reset in recent  
history or ever with an AVR so I don't know what I would do. Of  
course, that does not mean that my next project will be so fortunate!  
Or, the one after that.

Jim Wagner
Oregon Research Electronics.

On Jul 20, 2009, at 7:52 PM, Chuck Hackett wrote:

> 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.
>
>
> 



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