Now that this is solved...it points out that using RES and linkers does indeed catch certain problems like this.  But its the old problem of fixing things that are not really broken..ie...it could be made better but works as it is (for the present at least).


--- On Tue, 6/17/08, Alan B. Pearce <A.B.Pearce@rl.ac.uk> wrote:

> From: Alan B. Pearce <A.B.Pearce@rl.ac.uk>
> Subject: Re: [PIC] 16F887 and corrupted RAM/EEPROM
> To: "Microcontroller discussion list - Public." <piclist@mit.edu>
> Date: Tuesday, June 17, 2008, 4:33 AM
> >> It loads from EEPROM, and so the code allows the
> user to check
> >> the value and its wrong
> >
> >How does the data get in the EEPROM in the first place
> ? Sounds
> >more like feral s/w than bad chips
> 
> I was thinking about uninitialized variables - again feral
> software.
> -- 
> http://www.piclist.com PIC/SX FAQ & list archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist


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