Overrun = overrun;
> hexRecord(addr, rtvalIndex);
> return;
> }
>
> I've tried to compress the app even further, to get something small
> enough to submit as a how-to-reproduce sample. However the problem goes
> away if I get it any smaller
er. So, I'm stuck with 8 compilation units and
makefile. I can send you this off-list if you need it.
Regards,
Andy
>
> Date: Wed, 28 Jan 2009 20:40:22 +0100
> From: "Maarten Brock"
> Subject: Re: [Sdcc-user] Help with code-banking
>
> Andy,
>
> If you s
> Thanks in advance,
> Andy
>
>
>
>
> >
> > Message: 4
> > Date: Fri, 23 Jan 2009 20:28:49 +0100
> > From: "Maarten Brock"
> > Subject: Re: [Sdcc-user] Help with code-banking
> > To: sdcc-user@lists.sourceforge.net
> > Message-
Andy,
The records you posted are extended linear address records. Each one
specifies the upper 16 bits of the address, creating a full 32 bit address.
Each address prefix will last until a new prefix is declared.
:0204FA
:02 - Bytes in record
- address field - always 0 for this t
> Date: Fri, 23 Jan 2009 20:28:49 +0100
> From: "Maarten Brock"
> Subject: Re: [Sdcc-user] Help with code-banking
> To: sdcc-user@lists.sourceforge.net
> Message-ID: <497a2881.5191.28cf6...@sourceforge.brock.dse.nl>
> Content-Type: text/plain; charset=US-ASCII
>
Andy,
SDCC generates a so-called extended intel-hex file. This
also contains records to indicate the start of a new
segment/bank. If your bootloader or whatever you use to
program the chip(s) does not understand extended hex-
files you can use srecord to split the file into several
hex-files f
I'm evaluating SDCC for a project, which needs code-banking (we estimate
code size >64k). Are there any examples of how to do code-banking? I
have seen and followed the instructions (see below), but I think there
is one thing I still need to know.
On our hardware, the common area is 0x4000-0x7fff,
