Another 18F Data EEPROM Question

Started by Rick April 30, 2005
Yes, it's me again.

MC makes some cryptic statement about embedding data EEPROM
data in the "hex file" by declaring it with a DE directive
with an ORG of 0xF00000.

Does this mean that bytes declared from 0xF00000 through
0xF003FF get burned into EEPROM at 0x000 through 0x3FF

And if so, why does MPASM insist on having only even ORG

And does this mean that if I want to put something at 0x3FF
in EEPROM, I have to ORG 0xF003FE then waste a byte before
I can declare the data that I actually care about?

TIA, Rick