I never expected him to use RAM copies.  There is some odd checksumming
thing but when that is merely XOR all bytes together.  Getting all
zeroed be a real or from chip failures would pass despite the misread.

> -----Original Message-----
> From: piclist-bounces@mit.edu [mailto:piclist-bounces@mit.edu] On
Behalf
> Of David VanHorn
> Sent: Friday, February 10, 2006 2:08 PM
> To: Microcontroller discussion list - Public.
> Subject: Re: [PIC] question from someone new to the list
> 
> >
> >
> > I am learning more as I read the source.  Looks like it isn't EEPROM
> > after all.  The program reads the EEPROM values only at boot and
writes
> > it only when commanded.  Otherwise it uses a RAM copy of the home
> > positions.
> 
> 
> Hmm.. I'd wonder if there was a reason to do it that way. If not,
pulling
> them from EE would be more reliable.
> --
> 
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist


-------------------------------------  Notice of Confidentiality ----------------------------------------------------------
This email and any files transmitted with it are confidential and intended solely for the use of the 
individual or entity to whom they are addressed. If you have received this email in error please notify 
postmaster@vgt.net. This message contains confidential information and is intended only for the 
individual named. If you are not the named addressee you should not disseminate, distribute or 
copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by 
mistake and delete this e-mail from your system. If you are not the intended recipient you are notified 
that disclosing, copying, distributing or taking any action in reliance on the contents of this information 
is strictly prohibited.

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