public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: John Dallaway <john@dallaway.org.uk>
To: Himanshu Patel <himanshup@aftek.com>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Re: Help required for LDI file
Date: Thu, 01 Oct 2009 21:14:00 -0000	[thread overview]
Message-ID: <4AC51BBE.7010005@dallaway.org.uk> (raw)
In-Reply-To: <000001ca428c$6179b020$246d1060$@com>

Hi Himanshu

Himanshu Patel wrote:

> We are using LPC2458, which has scatter (non-continuous) SRAM memory. Now
> we want to assign bss section to this scatter memory. We tried to create
> sections as below but the same is giving linking error.
> SECTION_bss (sram, 0x40000540, LMA_EQ_VMA)  
> SECTION_bss (sram3, 0x7FD00a00, LMA_EQ_VMA)

The above code will attempt to define two linker output sections both
named ".bss". The GNU linker cannot allocate memory for symbols across
multiple memory regions in this way.

In order to split code or data across multiple memory regions, you will
need to define new output section macros (similar to those in arm.ld)
which are then mapped to the various memory regions by extending your
.ldi file. You must then adjust these macros to share the various
compiler-generated objects across the multiple output sections.

In the case of .bss, this is complicated by use of the __bss_start and
__bss_end symbols within eCos code. For example, there is code to zero
the bss at startup which assumes that the bss is contiguous. You will
need to examine how these symbols are used and accommodate any
assumptions that have been made.

I hope this helps

John Dallaway

-- 
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:[~2009-10-01 21:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-21  9:51 [ECOS] What's the process on switching version control system for eCos? Øyvind Harboe
2009-09-21 11:26 ` Alex Schuilenburg
2009-09-22 14:34 ` Bart Veer
2009-09-22 14:40   ` Øyvind Harboe
2009-09-22 15:00     ` [ECOS] " Sergei Organov
2009-09-22 15:42       ` Alex Schuilenburg
2009-09-22 15:57         ` Sergei Organov
2009-09-25  0:28           ` Jonathan Larmour
2009-09-25  7:58             ` Sergei Organov
2009-09-22 16:09   ` [ECOS] " Alex Schuilenburg
2009-09-25  0:33     ` Jonathan Larmour
2009-10-01 11:43 ` [ECOS] Help required for LDI file Himanshu Patel
2009-10-01 21:14   ` John Dallaway [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=4AC51BBE.7010005@dallaway.org.uk \
    --to=john@dallaway.org.uk \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=himanshup@aftek.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).