Tony K|bek wrote:
> 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.
>
> BTW MPLAB IDE 6.30 was used in the above examples.

Now I'm really confused.  Here is a source code snippet:

  .eedata  code    ee_start
  ee_id    de      h'10'       ;transmitter unique ID, low byte
           de      h'32'       ;transmitter unique ID
           de      h'54'       ;transmitter unique ID
           de      h'76'       ;transmitter unique ID, high byte

Which is partially responsible for this HEX file line:

  :100000001000320054007600FF00FC00FF00FF00EB

This is using MPLAB 6.30.00.00 with the processor set to 18F252.  What was
your processor setting?


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