Hi,
Wouter van Ooijen wrote:
>Because it is not a property of the chip, just a convention. The eeprom
>has no physical address, it is a different addressable region
(different
>from code and file registers), with different ways to read/write that
>region.

Well in a way I understand that from an technical standpoint but however
from
an practical standpoint I don't. The specification states that eeprom
data
is to be included in the hex file then also that means that the
'feature'
"fill the eeprom with initial data" is pretty useful and available. Now
the datasheet covers how to read/write from the eeprom, but does not
mention
this 'feature' at all. For me this is unfortunate as it really is a
*good* microchip
pic feature. When using external eeproms as I normally do, one always
have to have
bulks of code dealing with 'fresh' uninitilised eeproms ( filling them
with valid data etc. ).

But thanks to the old project I did a long time ago I recalled that one
could include
the data in the hex file. If it wasn't for that project i would have had
to add the code to
initialise it. Well one can say that I need to read all related
documents inlcuding
the programming speification, which i have btw, but for this particular
issue I didn't
see the correlation and didn't recall the information about it in the
programing spec.

So I don't se any harm in include this little tidbit of information in
the datasheet,
but I'm worng and I know it, just beeing stubborn :)

BTW the configuration fuses are pretty well documented at adress :
0x300000 and upwards
but they are 'half' program mem and half 'special' things :)

/Tony

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