Lpc2000

--- In lpc2000@yahoogroups.com, "jayasooriah" <jayasooriah@...> wrote:
>
> --- In lpc2000@yahoogroups.com, "brendanmurphy37"
> <brendanmurphy37@> wrote:
> 
> > To be fair to Philips, they generally describe the on-board flash 
> > as "program memory", and it's clear that this is very much its 
> > intended purpose.
> 
> The two version EE demo that Philips published must be rubbish then.
>

Well,

as there are different requirements for non-volatile data memory these
examples can be very usefull or if it does not work for your needs
(btw. what are your needs?) then just use an external EE. 

We need to update a few parameters based on environmental conditions
"every now and then" which could be once a day or once a month. The
Flash is big enough to host these additional 32 bytes of NV-data and I
consider it valuable input knowing HOW to do this based on the Flash
implementation. 

If you ask me whether the implementation is optimized for EEPROM,
absolutely not!  But asking myself if I want to spend the extra 50
cent for each board to have an optimized version, even less so!

The risk of overwriting program code caused by a software error as
mentioned by another member is very real though. This could be the
single most important reason why not to "abuse" the the program memory
for data storage.

Calling the detailed information how to store data in the program
memory "rubbish" seems more than just a little out of place. 

Bob