Müsste es dann nicht c!wd heißen?
Michael
2017-05-07 15:42 GMT+02:00 Matthias Trute :
> Hi Tristan,
>
> I've put your code online, revision 2252 contains the new
> file. There is only one change: I renamed the wd! into !wdc.
> It tells "store to watchdog control" and follows the more
> or less in
Hi Tristan,
I've put your code online, revision 2252 contains the new
file. There is only one change: I renamed the wd! into !wdc.
It tells "store to watchdog control" and follows the more
or less informal convention that ! and @ can be preceeded
with size information and followed by location info
Hello Matthias,
> I'll look at them in the next few days. Since we've just discovered
> some interrupt related bugs so maybe I'll ask you to do some
> tests with the code I will checkin. Is this ok for you?
Absolutely fine.
Tristan
Hi Tristan,
> >
> > It would be a great contribution for the cookbook. Esp if it works
> > with
> > Forth code.
> This made me think that writing 4 or 5 assembler words was not the
> best way. Instead, have one assembler word wd! to perform the timed
> write to WDTCSR and then have forth words fo
Hello Matthias,
> IIRC only the "disable watchdog" sequence is timing critical (the
> 4 cpu cycles you mention). All other tasks can be performed at
> lower speed, so a forth implementation should be fine.
My atmega328p seems to require any change to WDTCSR to be completed
within 4 cycles (I have
Am Donnerstag, den 20.04.2017, 09:04 +0100 schrieb Tristan Williams:
> AVR8 watchdog (reset and interrupt) atmega328p
>
> I wanted to use the 128 kHz watchdog oscillator as an additional
> timer.
The watchdog creates a full reset cycle, that means that the full
startup sequence is performed. Your
AVR8 watchdog (reset and interrupt) atmega328p
I wanted to use the 128 kHz watchdog oscillator as an additional
timer. I saw that AVR8 watchdog timer and reset was addressed on the
mailing list in late 2013 using assembler.frt
In the source tree there is an assembler word -wdt (no-wdt.asm), whi
