Sign in

username:

password:



Not a member?

Search m68hc11



Search tips

Subscribe to m68hc11



m68hc11 by Keywords

27c256 | 4K81H | 68HC11A1 | 68HC11P1 | 68hc24 | 68HC711E9 | 68HC811 | 8255 | A2D | ADC | ADC12138 | Am85C30 | BRCLR | Buffalo | CMOS | EEPROM | EPROM | Ethernet | EVB | EVBU | HC11E1 | HC11E9 | HC711E9 | Horray | ImageCraft | IRQ | Keypad | LCD | MC68HC11D0FN | MC68HC11E1CFU3 | MC68HC11F1 | MC68HC711E9 | MC68HC711E9CFN2 | Microcore11 | Microstamp11 | Minikit | NVRAM | PSD | PSD8xx | PSD9xx | PT1000 | RS232 | RTS | RXD | SPI | SRAM | TXD | Watchdogs | XIRQ


Ads

Discussion Groups

See Also

DSPFPGAElectronics

Discussion Groups | | Re: External watchdog (was: Thinking...)

Re: External watchdog (was: Thinking...) - Kerry Berland - Jun 5 15:11:00 2002

Have seen external watchdogs used fairly frequently
on automotive and industrial circuits where you
want to be sure that power devices are shut down
if the MCU is out of control.

The external watchdog is typically routed to two
places-- the RESET# input of the MCU, to try
to get it started again; and to the RESET# inputs
(or equivalent) of peripheral devices that control outputs.

If the MCU recovers, good. But if not, at least
the motors are shut off, or the switching power supply
is shut off, or whatever, so as to do the least
amount of harm, absent intelligent control.

Use of an external watchdog is a valid practice
IMHO if you are dealing with a system where
failure of the MCU clock could lead to a hazardous
situation.

Outright failures of the 68HC11 clock oscillator are not
very common, but the high impedance oscillator
is actually one of the most susceptible parts of
a typical circuit. Quartz crystals can fracture if
an ECU is shocked mechanically. Crud can build
up on a board in the oscillator area and stop
the clock. Electrical noise events can cause
pseudo-resets that put the internal state machine into
a lock-up condition.

The need for an external watchdog is strong enough
that they make voltage regulators with built-in watchdog
timers, which are sold into the automotive market.

Best regards,

Kerry Berland

Silicon Engines
2101 Oxford Road
Des Plaines, IL 60018 USA
847-803-6860
Fax 847-803-6870

----- Original Message -----
From: "Tony Papadimitriou" <>
To: <>
Sent: Wednesday, June 05, 2002 7:25 AM
Subject: Re: [m68HC11] Thinking... > ----- Original Message -----
> From: Roberto G Berner <>
> To: <>
> Sent: Tuesday, June 04, 2002 10:44 PM
> Subject: Re: [m68HC11] Thinking... > > I don't think that the internal watch-dog timer has
> > any kind of functional bug, but if the final product spec is very
> tight, I
> > would never trust the internal watch-dog by itself, just because it
> depends
> > on the MPU oscillator clock.
>
> The way I understand the internal watchdog circuitry makes me think
> that the only possibility for the internal watchdog to not work is
> that the MCU stops 'clocking'. An external watchdog using a different
> clock reference would timeout even then but since the MCU is not
> executing any code, it would be practically useless! Where would one
> route the timeout signal from the external watchdog? Wouldn't you
> need a second MCU to run the code for the external watchdog's trigger.
> And then, the same problem repeats...
>
> > Roberto Guillermo Berner >
> To unsubscribe from this group, send an email to:


______________________________
Stellaris® MCU Family: New Parts, New Package, New Price.


(You need to be a member of m68hc11 -- send a blank email to m68hc11-subscribe@yahoogroups.com )