Hi all,

Can anyone shed some light on how the correct method of creating HEX
files from ASM code.

Here is some ASM code to load the EEPROM into the 18F series.

          org 0xF00000

         DE 0x20, 0x20, 0x58, 0x20, 0x52, 0x45, 0x41, 0x44
         DE 0x20, 0x20, 0x45, 0x56, 0x45, 0x4e, 0x54, 0x20

This is the HEX code that is produced by MPLAB.

 :10000000202058205245414420204556454E54203A

The result is consecutive data in the EEPROM memory.

This is the HEX code that is the problem. I think it was produced by a
Basic Compiler. As you can see, there are 0x00 spaces inserted into the
EEPROM data

 :10000000200020005800200052004500410044001C
 :10001000200020004500560045004E0054002000FE


Is this a 'norm' as far as HEX files go.

regards

Tony

--
http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu