-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi David,
> I'm part of the way there. Just re-initialising my watchdog timer
> in my turnkey word before I call applturnkey seems to have stopped
> the repeated resets. I'll battle on...
I think its plausible that initializing the WDR refreshing
rou
I'm part of the way there. Just re-initialising my watchdog timer in my
turnkey word before I call applturnkey seems to have stopped the repeated
resets. I'll battle on...
--
Android is increasing in popularity, but the ope
I think my initial guess that the watchdog condition remains active after
reset is true, but only on newer devices.
http://www.nongnu.org/avr-libc/user-manual/FAQ.html#faq_softreset
Also from page 55 of the 324P datasheet:
'Note: If the Watchdog is accidentally enabled, for example by a runaway
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi David,
> problem comes when I simulate my application hanging - i.e when
> wdr doesn't get called. Obviously to be a useful watchdog, what
> needs to happen is that the device resets and starts running the
> application from the start again, but wh
Hi Matthius,
Thanks for your help again,
>Close, but still missing the point. You'll
>need to *regularly* clear the watchdog reset
>condition (depends on your settings every
>) with the WDR instruction. A forth word wi
>few milliseconds to at most 2 seconds IIR
>Cth that name is provided via core
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi David,
> I'm trying to use the watchdog on an ATMega644P chip. I have the
> problem that if the watchdog actually triggers it just keeps
> resetting, repeatedly writing out the 'amforth 5.1' message.
Your watchdog works perfectly well :)
> My g
Hi All,
I'm trying to use the watchdog on an ATMega644P chip. I have the problem
that if the watchdog actually triggers it just keeps resetting, repeatedly
writing out the 'amforth 5.1' message. My guess is that the watchdog
interrupt condition needs clearing at startup. Could this be right? Has
a
