Watchdog usage on multitask RTOS environment

 Watchdog usage on multitask RTOS environment

Hallo,

I would like to ask if someone has a good methodology to handle a robust watchdog when using an RTOS. If someone has and would not mind discussing it, that would be very appreciated.

I'm basically using an ARM7 and RL-ARM RTOS. After doing some research over the Internet I found Mr. Ganssle's article "Great Watchdogs", but that doesn't address RTOS usage, then I found Mr. Niall Murphy's article from http://www.embedded.com/2000/0011/0011feat4.htm.

My application have tasks that wait for semaphores and they wait with no time-out. Those semaphores are interrupt driven. An external interrupt sends semaphores to those tasks and it won't happen if there's no action on the interrupt line. Mr. Murphy's article doesn't sens to address this situation. My interrupt may not get generated for hours...

Have someone already done a similar watchdog usage? An articles or recommendation, different forums?

Much appreciated.

 RE: Watchdog usage on multitask RTOS environment

Here's one by Jack Ganssle

http://www.rbembedded.com/uci/MiscInfo/Watchdog/WatchdogArticle.html

 RE: Watchdog usage on multitask RTOS environment

Thanks Walter.

That article address profiling and some other cool stuff that will give me enough information to start playing with it all.

I'm redesigning someone else's system that currently has a "WATCHUSER". The device's user's manual states:

"FAQ
Q: I do key press and nothing happens, what is going on?
A: This is a Hardware failure.
Solution: Press the green button located in front panel."

( aka RESET ) ahahaha