public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Harish Kulkarni <wasinapple@yahoo.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Help on .ldi & h file
Date: Wed, 27 Jul 2005 19:54:00 -0000	[thread overview]
Message-ID: <20050727195354.GC10656@lunn.ch> (raw)
In-Reply-To: <20050727164658.74998.qmail@web30410.mail.mud.yahoo.com>

On Wed, Jul 27, 2005 at 05:46:58PM +0100, Harish Kulkarni wrote:
> Hello Group,
> 
> We are porting eCos onto board with leon processor.
> 
> The board has multiple chunks of ram (SRAM, scrachpad
> ram etc) spread across 32-bit address space.
> 
> How do we represent the same in .ldi and in .h (in
> pkgconf dir)?
> 
> In most of the ports, we can see ONLY one "ram"
> section used.
> 
> Could any one please refer us to .ldi/.h memory layout
> were multiple chunks of ram are mapped while porting
> eCos.

I don't think the linker can automatically spread the image over
multiple memory sections. The user has to control this. 

See for example 
packages/hal/arm/gps4020/current/include/pkgconf/mlt_arm_gps4020_rom.ldi

This has both sram and ram, and rom. It puts the fixed vectors in
sram, the data and bss in ram and the rest in rom. 

You could do something similar with your setup. Or you could for
example put the heap in a different memory bank than the rest of the
code.

If you need finer control you then need to make individial
functions/variables with attributes to tell the linker where to put a
symbol. The flash code has examples that does this. 

        Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

      reply	other threads:[~2005-07-27 19:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-27 16:47 Harish Kulkarni
2005-07-27 19:54 ` Andrew Lunn [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=20050727195354.GC10656@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=wasinapple@yahoo.com \
    /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).