From mboxrd@z Thu Jan  1 00:00:00 1970
From: fche@redhat.com
To: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Hardware Watchdog
Date: Thu, 26 Jul 2001 04:58:00 -0000
Message-id: <200107261156.f6QBusX14487@touchme.toronto.redhat.com>
References: <20010726125313.A14929@frequentis.com>
X-SW-Source: 2001-07/msg00818.html

Content-Type: text/plain; charset=US-ASCII
From: fche@redhat.com (Frank Ch. Eigler)
Date: 26 Jul 2001 07:56:53 -0400
In-Reply-To: < 20010726125313.A14929@frequentis.com >
Message-ID: <o5ofq7ucmy.fsf@touchme.toronto.redhat.com>
Lines: 23
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley)
MIME-Version: 1.0

Christoph Csebits <christoph.csebits@frequentis.com> writes:

: [...]
: im having a MPC860T based board with
: an hardware watchdog on it.
: [...]
: In eCos applications i am having a
: separate thread triggering the watchdog.
: No problem.
: [...]
: What do you think about using some
: of the timer interrupts for generating
: the watchdog triggers.

Is it typical to put watchdog reset calls into separate dedicated
threads, or low-level automatically-invoked code like interrupt
handlers?  I was under the impression that watchdog resets are most
appropriately placed within the activity loops of the application code
itself -- it is their demise that the watchdog mechanism is meant to
detect.


- FChE