Interesting stuff, Jinx, but:

On Sat, 22 Apr 2006 19:05:50 +1200, Jinx wrote:

> One useful way to avoid the refresh issue is to store your configuration/
> calibration data in program memory on those PICs that support self writing.
> This will work if you can live within the endurance constraint of program
> memory (parameter D130 for our example PICS, Min=10K, Typ=100K), and
> can afford to have your PIC 'freeze' while writing the parameters

But doesn't this mean you're using something which has 1/10th of the endurance (10k/100k vs. 100k/1M)?  And 
does program memory suffer the same "rewrite of something degrades the rest" problem of data EEPROM?  Surely 
if it does, you're better using EEPROM since it has ten times the endurance to start with?  (OK, I'll stop 
calling you Shirley! :-)

Cheers,


Howard Winter
St.Albans, England


-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist