Onestone wrote:
:
> never consider releasing a long deployement design without it. By that I
> mean anything expected to run for more than a couple of hours without
> power cycling MUSAT be protected in my view, and even these designs
> should be protected if at all possible. (some desigs simply MUST run a
:

I agree!

> the simplest protection, after good basic design and layout is to refrsh
> all register bits that are used by the system, but which are not
> normally updated by the code, ie setting a data direction register at
> power on then assuming it will still be set 4 months later is not a good
> idea. rather periodically refresh it along with all other bits only set
> once. Alternatively if you have the code space, and the slight impact on
> execution speed is not a problem you can make sure that all such
> critical bits (anything used by the program is a critical bit) is
> specifically configured immediately prior to use.

Refreshing the SFRs is currently my approach. But the other problem for
me is: what to do with unreachable internal registers of the MSP430,
e.g. JTAG configuration.
One idea is to do a periodic reset. But I'm not sure, if this really
has the same effect to internal registers as power-cycling has!? The
MSP430 has a broad range of resets and which registers are affected, so
one cannot be sure...

Anyway thanks for your suggestions!

Regards

Hardy

------------------------------------



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