JMGross schrieb: > I you require a WDT for environment stability (and not just to > circumvent code deadlocks due to poorly written code) then the WDT > may not be disabled EVER. It is on at startup and it has to stay on. > period. If you don't need it, well, maybe a faster startup that > disables WDT is nice. And if you KNOW that htis happens wihtout > digging into linker listings or library source code, it is even > nicer. But in case you NEED the WDT to ensure device crash recovery, > there must be a way to never disable it at all.
the correct way would be when the startup code resets the WDT periodically. which has the small disadvantage that it's making the startup code hardware dependent and a bit larger (code size) there are other points no one so far brought up (for good reasons), like increasing the CPU frequency to speed up the init etc. and as most people realize this would be a very bad idea. not only the the max speed dependent on the VCC voltage, the increased current consumption could also lead to a problem. but for some projects this could be a good solution, as by default the startup does the initialization at a relatively slow speed. in that case the developer needs to do that manually. > As a normal programmer you don't expect that you have to mess with > the C startup code. (okay, I must admit, a normal C programmer > wouldn't care for the WDT at all and and disabled WDT saves him a lot > of wondering about reboots) :) i'm fine with enabled WDT at startup. all the examples from TI start by disabling the WDT anyway. so a msp430 developer should learn that quickly ;-) chris
