public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.com>
To: k e <ndgipper@yahoo.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] NEWBIE: Memory Layout on AEB-1 Rev B
Date: Wed, 16 May 2001 10:43:00 -0000	[thread overview]
Message-ID: <3B02BC3A.F56A906E@redhat.com> (raw)
In-Reply-To: <20010516172856.95679.qmail@web14004.mail.yahoo.com>

k e wrote:
> 
> Hi,
> I'm need all the room in RAM that I can get
> on the AEB-1 Rev B.
> Can someone tell me what the following lines
> in the memory layout files are for?
> 
> file: mlt_arm_aeb_ram.ldi
> ...
>     __reserved_vectors = 0; . = __reserved_vectors + 0x1000;

Used for the vectors. You can't avoid this unless you never intend to have
any interrupts or exceptions ever.

>     __reserved_not_mapped = ALIGN (0x1); . = __reserved_not_mapped + 0x7000;

There's no memory in the memory map here.

>     __reserved_for_rom = ALIGN (0x1); . = __reserved_for_rom + 0x4000;

If you don't intend to use the GDB stubs for debugging, you could remove
this. Also note that exception handlers will still have been set up by the
GDB stub in ROM, and those handlers will use RAM in this area. So if you
get any exceptions it will scribble in this area anyway. So obviously
either don't get any exceptions, or supply new exception handlers in your
app.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

  reply	other threads:[~2001-05-16 10:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-16 10:28 k e
2001-05-16 10:43 ` Jonathan Larmour [this message]
2001-05-16 12:08   ` k e
2001-05-16 14:18     ` Jonathan Larmour

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=3B02BC3A.F56A906E@redhat.com \
    --to=jlarmour@redhat.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=ndgipper@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).