[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avr-libc-dev] bug in wdt_disable() for ATmega324P
From: |
jan |
Subject: |
Re: [avr-libc-dev] bug in wdt_disable() for ATmega324P |
Date: |
Sun, 9 Mar 2008 17:18:48 +0100 |
On Sun, 9 Mar 2008 15:52:34 +0100
Joerg Wunsch <address@hidden> wrote:
> As address@hidden wrote:
>
> > First of all, I don't know if this is the appropriate way to report
> > a bug in AVR Libc. If not, please tell me the correct procedure.
>
> Well, for a genuine bug report, the way to submit it would be via
>
> https://savannah.nongnu.org/bugs/?group=avr-libc
>
> However, what you're talking here about is more like a request for
> discussion, and that's fine with that mailing list.
>
> > In ATmega324P you have to make sure the WDRF bit in MCUSR is clear
> > before you try to disable the watchdog.
>
> Well, this is something that needs to be handled at the application
> level. Depending on the application, it has to be handled very early
> at startup (e.g. in situations where the application has much SRAM to
> initialize, or a C++ application that runs expensive global
> constructors), and it only has to be handled once. For the latter
> reason, we decided it's nothing you'd want to perform within each call
> to wdt_disable() but rather documented some example code within the
> prolog of the <avr/wdt.h> documentation about how an application might
> want to handle that.
>
Sorry, I didn't notice that.
In a way it feels good to be wrong about things like this ;^)
/Janne
--
Tomorrow, this will be part of the unchangeable past but fortunately,
it can still be changed today.