From: Lars Poeschel <larsi@wh2.tu-dresden.de>
To: Martin Laabs <martin.laabs@mailbox.tu-dresden.de>
Cc: "ecos-devel@ecos.sourceware.org" <ecos-devel@ecos.sourceware.org>
Subject: Re: packages to different memory sections
Date: Wed, 26 Nov 2008 15:48:00 -0000 [thread overview]
Message-ID: <8F1E3E9A-182D-44C7-96BB-E257473ABE52@wh2.tu-dresden.de> (raw)
In-Reply-To: <op.uk3e1xru724k7f@localhost>
[-- Attachment #1: Type: text/plain, Size: 1528 bytes --]
Am 23.11.2008 um 23:21 schrieb Martin Laabs:
> Hi,
>
> I have a board with a lpc2294. This processor has about 256kB of
> fast internal flash. However - this is not enough. At least while
> developement. I have plenty of flash at the external memory bus but
> it has many waitstates.
> Now I'd like to split ecos in two parts and say "HAL, Kernel and
> Math"-Package in the fast internal flash, "ISO-C, Fat, zLib etc."-
> Packages
> into the slow external flash.
>
> Is this possible without too much handwork on the linker script?
> (So not add every symbol per hand to the coresponding section.)
I don't know a way that could do it without much handwork.
> And if not - does the gnu-ld linker support two sections of the
> same name or assignment of (i.e. the .text) segment to two differ-
> ent memory regions? (So that I could use as well the internal as
> the external flash for the .text segment.) The info page of ld
> was not very informative about that.
Yes, this should be possible although I never did that. Please read
http://sourceware.org/binutils/docs/ld/Scripts.html#Scripts
I think I would solve that by mapping the same input sections to two
different output sections seperating them by filename. - not very nice
but should work.
Derived from the example I would write something like:
SECTIONS {
.text : { *(.text) }
.text1: {library.o(.text)}
.data : { *(.data) }
.bss : { *(.bss) } }
}
Also see:
http://sourceware.org/binutils/docs/ld/Input-Section-Example.html#Input-Section-Example
Lars
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 194 bytes --]
prev parent reply other threads:[~2008-11-26 15:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-23 22:22 Martin Laabs
2008-11-26 15:48 ` Lars Poeschel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8F1E3E9A-182D-44C7-96BB-E257473ABE52@wh2.tu-dresden.de \
--to=larsi@wh2.tu-dresden.de \
--cc=ecos-devel@ecos.sourceware.org \
--cc=martin.laabs@mailbox.tu-dresden.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).