??? 12/20/09 01:34 Read: times Msg Score: -1 -1 Off-Topic |
#171785 - the problem with watchdogs Responding to: ???'s previous message |
Watchdogs only tell you that there's been a problem. They can't tell you what it is, and they can't tell you much else, either. They're like that "idiot light" on your car's dashboard, that tells you the oil pressure is low, or the temperature is too high, or that you should have your engine "serviced," but not much else. They, simply put, tell you nothing other than that trouble has arrived. Some supervisor chips can be connected in a way that tells you trouble may be imminent, but most are used simply to say it has arrived and to reset the MCU. Some of the internal watchdogs tell you that they were what caused the reset, but little more. I suppose it's possible to devise a way of providing more information, but I don't believe anyone has done that yet, and it's highly unlikely that they will. After all, it points up a flaw, and nobody wants credit for having, or even finding, them in an established product.
RE |
Topic | Author | Date |
Micro D.I.I. Reset question | 01/01/70 00:00 | |
if the wind blows from the west | 01/01/70 00:00 | |
Monostable multivibrator or watchdog | 01/01/70 00:00 | |
the problem with watchdogs | 01/01/70 00:00 | |
Watchdogs are useful even if they don't help with debugging | 01/01/70 00:00 | |
it's not just for debugging ... | 01/01/70 00:00 | |
Oh yes it can! | 01/01/70 00:00 | |
It's not as widespread as I'd hoped | 01/01/70 00:00 | |
the best I have seen | 01/01/70 00:00 | |
watchdog interrupt | 01/01/70 00:00 | |
That would help, but not in production![]() | 01/01/70 00:00 |