Thanks for the interest Dale, You're right, I download and update the data table
from time to time, This 'will' be a end user operation via a laptop and rs232.
When the application is running the lookup needs to be VERY fast, or rather a low
overhead from receiving an interrupt, the EEDATA read is just too slow.





dale@BOTKIN.ORG on 12/02/2002 15:02:58
Please respond to PICLIST@MITVMA.MIT.EDU@INTERNET@wtgw

To:     PICLIST@MITVMA.MIT.EDU@INTERNET@wtgw
cc:
Paper Mail:
Subject:        Re: [PIC]:Program memory tables - Advice please

                   *** WARNING ***

This mail has originated outside your organization,
either from an external partner or the Global Internet.
     Keep this in mind if you answer this message.


On Tue, 12 Feb 2002, Mike Blakey wrote:

> Thanks Tony, What I think I'm after is a hybrid of both !!  i.e. store the table
in
> EEDATA, and write it into program memory as the Micro boots up.

I gotta ask...  why would you do this?  If you ned to change the table
without reprogramming the PIC, I would assume you're downloading the data
from somewhere or altering it from time to time as you go.  Why not just
store it in FLASH program space instead of EEPROM to start with?

Dale

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics








********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.