> I think you didn't explain my problem correctly.

Forgive me for saying so, but I get the impression that you don't know
what you are doing.

> I am trying 
> to locate in my .hex file (I have used gpasm) the code that 
> corresponds to directives, macros, include file and definitions.

there is none, the essense of an assembler is that it processes all
those and gets rid of them. the .hex file contains only data (in the
broad sense) to be put at specific locations in the PIC. There are fixed
locations for code, eeprom, fuses and (seldom used) ID locations.

> since I will flash my hex file to my (future) pic programmer 
> into its program and data memory.
> I can't figure out how to deal with this issue. I know that 
> the program memory starts always by OXO.
> "starts at 0x2100 IIRC" what do you mean by this?

Eaxtly what I said: by convention (defined by Microchip) the eeprom data
is located in the .hex file at that address (IIRC, please verify the
address). Fuses info is at 0x2007 and sometimes 2x2008 (for 18F's many
more locations are used), ID at (IIRC) 0x2006.

> I think that data memory are 8 bits (not 14 bits) and program 
> memory are 14 bits (correct me if i am wrong).

true, but that does not mean much, except that the relation between code
addresses and hex file addresses is HA = 2 * CA (for 12 and 14 bit
cores, for 18Fs the code is addressed byte-wise so it is simple).

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: www.voti.nl
consultancy, development, PICmicro products
docent Hogeschool van Utrecht: www.voti.nl/hvu
 

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist