gnupic: Re: [gnupic] pic18f24j10
Subject:
Re: [gnupic] pic18f24j10
From:
David ####@####.####
Date:
1 Jul 2007 03:31:28 +0100
Message-Id: <20070630212549.0c59361a@DEEPTHOUGHT.BARNET.net>
On Sat, 30 Jun 2007 22:03:27 -0400
"George M. Gallant Jr." ####@####.#### wrote:
> The resultant hex and cod files are huge. The linker appears to
> be generating a 64Kbyte image when actual image size should be
> less than 3Kbytes.
How are you seeing the size and how do you know what size the image
should be? The actual file size of the HEX file will be much bigger
than the actual data to program because it's ASCII encoded, not raw
bytes, and the HEX format includes addresses, headers, and footers as
well as some other configuration data. The COD file has lots of other
data, too.
There will be a few bytes way up in high addresses for the CONFIG word.
If that's not the issue, you can look in the LST file or use gpdasm or
gpvo to determine what's actually going into memory.
Without any of that information, we have no idea why the files are
bigger than you're expecting.
David Barnett
>
> On Sat, 2007-06-30 at 19:51 -0400, Xiaofan Chen wrote:
> > On 6/30/07, George M. Gallant Jr. ####@####.#### wrote:
> > > I would like to use gputils with the pic18f24j10 chip. gpasm balks
> > > at the unsupported processor. Tried p18f2410 and gpasm dosn't like
> > > all of my MPLAB style CONFIG directives. It finds the
> > > p18f24j10.inc file.
> > >
> > > Program assembles, links, and runs when built with mplab.
> > >
> >
> > Get the latest CVS version and build it. The latest CVS version does
> > support the MPLAB style CONFIG directive and support 18F24J10.
> >
> > I just tested using a template file from MPLAB and it works fine.
> >
> > Regards,
> > Xiaofan
