gnupic: [gnupic] Different hex file generated by gpasm and mpasm
Subject:
RE: [gnupic] Different hex file generated by gpasm and mpasm
From:
Peter Onion ####@####.####
Date:
20 Sep 2005 10:02:03 +0100
Message-Id: <1127206892.32327.4.camel@ratbert.alien.bt.co.uk>
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
