RE: Different hex file generated by gpasm and mpasm

Peter Onion <[email protected]> Tue, 20 Sep 2005 10:01:31 +0100
Newsgroups gmane.comp.hardware.microcontrollers.gnupic
Message-ID <[email protected]>
On Tue, 2005-09-20 at 08:11 +0800, Chen Xiao Fan wrote:
> For now yes I am looking at the hex file quite often since
> I am involved in the pickit-devel project. ;)-

I still fail to see why this is important unless you are reinventing the
wheel by writing your own hex file parser ?

> What I want to know is exactlly gpasm generates the hex
> file. The file in question is a single relocatable assembly
> file and I do not expect too much difference in the 
> generated assmebly. 

Ok, but gpasm does not produce a hex file in the case you give above.
gpasm produces the ".o" file which is read by gplink and that produces
the hex file.

Peter