On Sun, 17 Nov 2002, Rob Robson wrote:

> "When my program blows up randomly, the first thing I look for is..."

...my most recent known working backup doing the same thing?

Without an in circuit emulator, it is risky to make a drastic change to
your code (and expect it to work). So typically I break development into
(at least) two strategies:

1) Make low risk, incremental changes and verify the change does what is
expected.

2) For changes that are in their nature "major", simulate before burning
chips. This can be a challenge with MPLAB, but something like gpsim or
UMPS makes the job "possible".  ICD may be a suitable alternative... Once
you've verified that the simulated works, debug the real thing. (The only
reason I say ICD "might" be a suitable alternative is that in many cases
it's just too intrusive.)

Scott

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads