gnupic: Re: [gnupic] pic18f24j10


Previous by date: 1 Jul 2007 13:33:07 +0100 Scope, Tobias Schlottke
Next by date: 1 Jul 2007 13:33:07 +0100 Re: [gnupic] pic18f24j10, Xiaofan Chen
Previous in thread: 1 Jul 2007 13:33:07 +0100 Re: [gnupic] pic18f24j10, David
Next in thread: 1 Jul 2007 13:33:07 +0100 Re: [gnupic] pic18f24j10, Xiaofan Chen

Subject: Re: [gnupic] pic18f24j10
From: "George M. Gallant Jr." ####@####.####
Date: 1 Jul 2007 13:33:07 +0100
Message-Id: <1183293475.11653.18.camel@scuba.home.net>

Dave

The actual hex image is much larger than 64k. It has multiple 
records of setting the base address and then 64k of 0xFF.

The size of the hex file with gputils:  8614212 bytes
                              mpasm:       7948

The address portion of the hex record indicates 49 banks of 64k.

The 18f24j10 has 16K.

George

On Sat, 2007-06-30 at 21:25 -0500, David wrote:
> 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
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
> 
-- 
George M. Gallant, Jr.
(508) 202-2933


Previous by date: 1 Jul 2007 13:33:07 +0100 Scope, Tobias Schlottke
Next by date: 1 Jul 2007 13:33:07 +0100 Re: [gnupic] pic18f24j10, Xiaofan Chen
Previous in thread: 1 Jul 2007 13:33:07 +0100 Re: [gnupic] pic18f24j10, David
Next in thread: 1 Jul 2007 13:33:07 +0100 Re: [gnupic] pic18f24j10, Xiaofan Chen


Powered by ezmlm-browse 0.20.