gnupic@linuxhacker.org

Folks,

While I'm writing Pista, the PICSTART Plus handler program
(http://gatling.ikk.sztaki.hu/~kissg/pd/pista/pista.html) I found a problem.

According to Microchip data sheets internal data storage EEPROM
is addressing starts from 0x0. At least PIC programs and PICSTART Plus
programmer use this base address.
This may cause a confusion when handling program code and EEPROM data.
(It is hard to figure out that address 0x22 belongs code or EEPROM area.)

However I found that MPLAB exports EEPROM content into HEX files
with 0x2100 or 0xf00000 base address (depending on 14/16 bit processor
architecture).
I guess the same convention is used when it imports HEX files.

I would like this way of distinguishing program and data address range
because it would solve a lot of problem but I want to be sure that
this method is portable.
So I have some questions, please help!

1. Does MPLAB use other than above two base addresses for EEPROM data
in HEX files?
2. Can Microchip assemblers and compilers produce EEPROM content HEX files?
Is the base address same as above?
3. Do gputils follow this convention?

Thanks.

Gabor
-- 
No smoke, no drugs, no vindoze.