All timer events are executed in the same thread. This means that the next timer event is raised after the last one has finished.
Event that triggering the watchdog does not need to be very exact, and the call is quite short, it might lower the exactness of other timer events.
I would have thought that the watchdog is there to ensure your app is still healthy, so I don’t see the point of the thread solution, on the other hand using the timer then you know that something hasn’t brought down the main scheduler, and if it does then the watchdog would fire
have to agree to disagree, im afraid, but totally dependant on what you would want a watchdog to do, normally its another piece of logic/code that needs to reset it ie application layer vs driver layer
maybe slightly off topic, but doesn’t micro framework have a ConstrainedExecution or something, I remember using it somewhere to trap something taking longer than expected, seemed useful at the time
@ Architect - I meant the application scheduler not the mf scheduler, but yeh both work if something catastrophic happens
Watchdog is a hardware layer control. If your code is still running, and still “touching” the watchdog counter, the hardware WD won’t jump in. If something goes astray in your code (which could be as simple as blocked execution, or as bad as a unhandled exception halts all execution) then the WD counts down and is reset. It is really only the “I’ve failed, reset the hardware” error catch, and for a robust application you would still want other logic controls that handles the softer, “my app is still running but I don’t know what state I’m in” errors (although in a microcontroller sense, resetting may still be the most logical approach to recover that too)