In message [off-list ref] you wrote:
quoted
Do you really mean RTC here???
Yes - the 866 and derivatives (859 etc) do NOT have a Real Time Clock
block. This means that hooking the RTC interrupt to 'kick the dog' is
rather difficult :-))
That may be the case. But the watchdog code does not use any RTC at
all.
"It is based on the code of Florian Schirmer but using kernel timers (as
used by the DENX driver) rather than the RTC."
Have you ever seen a MPC8xx watchdog driver that used RTC for
triggering?
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
A wise person makes his own decisions, a weak one obeys public
opinion. -- Chinese proverb
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Wolfgang Denk wrote:
In message [off-list ref] you wrote:
quoted
quoted
Do you really mean RTC here???
Yes - the 866 and derivatives (859 etc) do NOT have a Real Time Clock
block. This means that hooking the RTC interrupt to 'kick the dog' is
rather difficult :-))
That may be the case. But the watchdog code does not use any RTC at
all.
quoted
"It is based on the code of Florian Schirmer but using kernel timers (as
used by the DENX driver) rather than the RTC."
Have you ever seen a MPC8xx watchdog driver that used RTC for
triggering?
Gosh - egg on face. Got mixed up with the PIT which usually uses a 32KHz
crystal as does the RTC on the mpc860. Well, we don't have a crystal on
the PIT so that (as well as the non-existant RTC) is not available!!
This is what comes from trying to rely on memory alone with 1358 pages
of mpc866 manual :-))
--
Robin Gilks
Senior Design Engineer Phone: (+64)(3) 357 1569
Tait Electronics Fax : (+64)(3) 359 4632
PO Box 1645 Christchurch Email : robin.gilks@tait.co.nz
New Zealand
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
In message [off-list ref] you wrote:
quoted
quoted
Do you really mean RTC here???
Yes - the 866 and derivatives (859 etc) do NOT have a Real Time Clock
block. This means that hooking the RTC interrupt to 'kick the dog' is
rather difficult :-))
Why would you want to do that? Not a very effective watchdog
timer. Even in the most hopelessly crashed system the RTC or other
timer interrupts usually continue to operate. An effective watchdog
needs to be managed throughout the whole boot process and handed off
along the way to some application, such that any system error will
cause the application to fail to kick the timer.
Good luck :-)
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/