> Hmmm that's very odd, these staments (comments removed for clarity):
>
> EE_ROMDATA      CODE    0xF00000        ; data resides in onchip eerom
>         DB
>         0x03,0x01,0x05,0x05,0xDC,0x00,0x00,0x00,0x00,0x00,0x00,0x00 DB
> CALC_LOW_BAUD(9600),0x03,0x00
>
> Generate this in the hex file:
>
>> 1000000003010505DC0000000000000005030000FE
>
> This has worked in previous projects.
> The project above is assembled/linked for an 18F452.
>
> Where did you find the information that only even adresses is accepted ?

Hmm, I don't remember where exactly this came from.  However, if you use
DE instead of DB, you will get data in every other byte in the HEX file.
Since DE is the "official" way to define intial EEPROM data, I assumed
this was the way it was expected in the HEX file and the way I interpret
it in my PIC programmer.  I guess the question is how MPLAB interprets the
HEX file data.  Unfortunately I'm at the wrong machine to test that now.


*****************************************************************
Embed Inc, embedded system specialists in Littleton Massachusetts
(978) 742-9014, http://www.embedinc.com

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@mitvma.mit.edu with SET PICList DIGEST in the body