[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avr-libc-dev] correction in xmega wdt_enable/ wdt_enable
From: |
S, Pitchumani |
Subject: |
Re: [avr-libc-dev] correction in xmega wdt_enable/ wdt_enable |
Date: |
Mon, 19 May 2014 10:24:34 +0000 |
> -----Original Message-----
> From: Joerg Wunsch [mailto:address@hidden
> Sent: Wednesday, May 14, 2014 6:14 PM
> To: S, Pitchumani
> Cc: address@hidden
> Subject: Re: [avr-libc-dev] correction in xmega wdt_enable/ wdt_enable
>
> As S, Pitchumani wrote:
>
> > Bit 0 - SYNCBUSY
> > When writing to the CTRL or WINCTRL registers, the WDT needs to be
> > synchronized to the other clock domains. During synchronization the
> > SYNCBUSY bit will be read as one. This bit is automatically cleared
> after
> > the synchronization is finished. Synchronization will only take place
> > when the ENABLE bit for the Watchdog Timer is set.
>
> I don't read any requirements out of this to wait until SYNCBUSY is
> cleared before being allowed to execute a WDR instruction (which is
> what your implementation does).
>
> As I read it, SYNCBUSY only has informational value: it turns '1' by
> the time the WEN ("the ENABLE bit") is set, until the watchdog has
> synchronized, when it will go '0' again.
>
> But I agree that the wording is not completely unambiguous. Anyway,
> if one is required to wait until SYNCBUSY is '0' before executing a
> WDR, I think the manual should very clearly state it that way.
Sorry for the delayed response.
I couldn't verify the modified macro with actual device. But, we got
feedback that modified wdt_enable version in atmel's ASF works as
expected.
Ok to commit?
Regards,
Pitchumani