Am 25.08.2011 21:51, schrieb Peter Bigot: > What you said isn't quite right: a WDT violation does do a PUC, but > not a POR. A PUC doesn't really clear everything that a POR does.
Right, I got that backwards. Sorry, and thanks for putting it right. > Peripheral register configurations are left in place, and I believe > some interrupts may remain pending. Not a good state to be in. The good thing is that you can - given proper code in the bootstrap - figure out what caused the reboot. If you log that somewhere in the field, that is quite valuable information. >> In fact if you want a soft boot, be sure that your bootstrap (reads if >> needed and) clears things a PUC would initialize and poke something you >> can pull from the constant generator into WDTCTL. Of course you don't >> want that in the bootstrap for normal operation... > > If your MCU supports it (the feature is in the 5xx family at least), > this suggestion from > http://tech.groups.yahoo.com/group/msp430/message/48258 is way better > than trying to manually put everything back to POR state. > > PMMCTL0 |= PMMSWPOR; The MSP430F1611 didn't support that, so we had to clear registers manually during boot-up. -- M. Andree ------------------------------------------------------------------------------ EMC VNX: the world's simplest storage, starting under $10K The only unified storage solution that offers unified management Up to 160% more powerful than alternatives and 25% more efficient. Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
