> > A robust program always resets or clears every register it uses upon
> > initialization, anyway, so it's a moot point.
>
> This has been stated before on Piclist, but I am not so sure it is true.
>If you cannot trust the chip to initialize itself the way it is supposed
>to why should trust it to, say, get 4 when adding 2+2.

Should you not be treating this as a  case of the chip initialising to a
safe state on reset? I would hate to think what sort of external circuitry
would need to be fitted to make sure that some motor driver was not turned
on while the PIC did its internal reset code, and then enabled the driver if
the PIC was not set to a known state on power up, and then the protection
for the enable circuit to ensure that it was not accidentally fired off by
another init state.....

big problems have little problems upon their backs to try us
and little problems have littler problems
and so ad infinitus

--
http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu