Hi Pete,
The reason to use the HW wathdog is to recover from loops that hang when
you are polling som hardware.
The WDT timeout should be set in the FF configuration file to a longer
time than what is the normal execution time of a HW poll.
I usually configure the watchdog timeout to 0.5 seconds.
PAUSE should get executed at least that often.
The WDT is cleared in PAUSE. If you have a SW loop which is not polling
HW, and it takes a long time to execute, you can clear the watchdog with
PAUSE or CWD in the loop.
For example a I2C device may for some reason never respond. The watchdog
will then restart the CPU.
If do not have any HW that possibly hangs, you can disable the watchdog
in the CPU configuration bits.
BR Mike
On 12.10.2012 5:19, Pete Zawasky wrote:
> Hi Mikael,
>
> Can you elucidate a bit on your philosophy for clearing the WDT in FF3.8?
> Perhaps add some info to the User's Guide concerning the WDT.
>
> Pete
>
> ------------------------------------------------------------------------------
> Don't let slow site performance ruin your business. Deploy New Relic APM
> Deploy New Relic app performance management and know exactly
> what is happening inside your Ruby, Python, PHP, Java, and .NET app
> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
> http://p.sf.net/sfu/newrelic-dev2dev
> _______________________________________________
> Flashforth-devel mailing list
> Fla...@li...
> https://lists.sourceforge.net/lists/listinfo/flashforth-devel
>
|
