I guess it pays to assume anything could have an micro controller now days.
The other day my truck's radio went blank (after some self induced frequency changes). Ironically, I was on the way to the car dealer and less than a mile away. ;-)
Turning the truck off and then back on didn't change anything. Because I was just taking the truck in for a unscheduled oil change, I made a quick check under the hood to make sure there were no obvious melted wires or smoke. Seeing nothing wrong, I warned the service people and said I'd look at the radio myself later after they changed the oil.
At home I found the fuse was good and it had full voltage on. It also had about 2 volts on the radio side of the fuse while the fuse was removed.
I looked and didn't see an easy way to get to the radio in the dashboard so I was planning to take it in to get it fixed.
Luckily I didn't get the dealership called the next day and I decided I really should make sure I had done everything I could. I hadn't done a "power down clear" on the radio to reset any micro controller that might be in the radio. That 2 volts on the wire going to the radio made me suspect that there could be another power line leading to the radio.
Not having a schematic of the truck's wiring, I used the brute force method and disconnected the battery for 30 seconds. Thats all it took to fix it (so far). It was raining the day it failed and there was some lightning in the area. So hopefully it was a one time problem.
I'm new to embedded design idea's (at home projects so far) so I'm thinking a watchdog timer would have been one way to have this problem fix itself easier than disconnecting the battery. I have read some of the previous discussions and agree with the idea that if a watchdog timer is actually tripping, it means you messed up somewhere. But it also seems like the user should have a reliable device. So if in the field, a watchdog timer covers up a once in four year glitch. Thats not all bad from my user's point of view.
Am I all wet thinking that way? ;-)
Gerald Bonnstetter Bonnsoft