Hi,

Olin Lathrop wrote:

>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.

Yes it's a bit odd, beacuse when I replaced the DB directives with DE =
as:

EE_ROMDATA      CODE    0xF00000        ; data resides in onchip eerom
        DE      0x03,0x01,0x05,0x05,0xDC,0x00,0x00,0x00,0x00,0x00,0x00,0x00
        DE      CALC_LOW_BAUD(9600),0x03,0x00

I got this:
:1000000003010505DC0000000000000005030000FE

In the hex file which is exactly the same as the previous one:

:1000000003010505DC0000000000000005030000FE

Intriguing as there is not zero padding in either one,
I remember I *had* problems with zero padding in previous MPLAB versions
and when I started using DB they went away.=20

BTW MPLAB IDE 6.30 was used in the above examples.


/Tony

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