public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "james chen" <james_ch1@sina.com>
To: "Gary Thomas" <gthomas@cambridge.redhat.com>
Cc: <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] Memory Layout
Date: Wed, 18 Apr 2001 18:05:00 -0000	[thread overview]
Message-ID: <000701c0c86c$ed2f5820$c408aa0a@inc.inventec> (raw)
In-Reply-To: <XFMail.20010418062421.gthomas@cambridge.redhat.com>

>
> On 18-Apr-2001 james chen wrote:
> > Hello,
> >
> >        From memory layout, I find that Redboot( startup in ROM) and
> > Applications( startup in RAM ) both share the same memory address and
size.
> > When I use GDB debugging applications through redboot's gdb stub. Will
> > redboot's memory  be cracked by Applications? Thanks in advance!
>
> Memory used by RedBoot and "normal" applications do not overlap.  The MLT
> files imply that they do, but this is because RedBoot is just a ROM
> application and the MLT setup is to allow for any application to use all
> available resources.
>
> In general, RedBoot uses a chunk of low memory (128k is typical) and
> RAM based applications are set up to load just above that and use the
> remaining memory.
>
       After looking many ARM based platform in eCos. RAM based applications
leave different size memory( from 0x8000--0x20000), I think these memory is
used by RedBoot except vectors( sure?:-) ). Which size will I leave memory
for RedBoot, I am using my custom board based on ARM7TDMI.
       Another quesiton, when I release my applications and RedBoot will not
ship in. Will the memory used by redboot be lost( can't used by normal
applicationss). If then, how can I re-use it?

      Thanks in advance!

james chen


  reply	other threads:[~2001-04-18 18:05 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-18  2:01 james chen
2001-04-18  5:24 ` Gary Thomas
2001-04-18 18:05   ` james chen [this message]
2001-04-19  5:12     ` Gary Thomas
2001-04-19 17:37       ` james chen
2001-04-19 17:48         ` Gary Thomas
2001-04-19 17:53         ` [ECOS] Bootloaders (was Re: [ECOS] Memory Layout) Lewin A.R.W. Edwards
  -- strict thread matches above, loose matches on Subject: below --
2008-04-10 21:35 [ECOS] Memory layout Syed Ismail
2007-10-29 14:13 [ECOS] memory layout Syed Ismail
2007-10-29 14:18 ` Andrew Lunn
2003-10-08 14:29 [ECOS] Memory Layout James Yates
2003-09-18  7:31 [ECOS] Memory layout Matthieu.GIRARDIN
2002-11-18 19:44 [ECOS] memory layout AL Chane
2002-10-30  9:55 Schumacher, Gordon
2002-11-04 20:37 ` Jonathan Larmour
2002-10-30  1:09 AL Chane
2002-10-30  4:52 ` Chris Garry
2002-04-10 18:23 [ECOS] Memory layout Agarwal, Lomesh
2002-04-10 18:18 Agarwal, Lomesh
2002-04-11 18:03 ` Jonathan Larmour
2002-04-10 15:31 Agarwal, Lomesh
2002-04-10 17:39 ` Jonathan Larmour
2002-04-10 14:01 Agarwal, Lomesh
2002-04-10 15:22 ` Jonathan Larmour
2002-04-07 16:14 Agarwal, Lomesh
2002-04-10 13:51 ` Jonathan Larmour
2001-01-23 22:51 [ECOS] memory layout Natarajan, Mekala (CTS)
2001-01-23 23:46 ` Jesper Skov

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='000701c0c86c$ed2f5820$c408aa0a@inc.inventec' \
    --to=james_ch1@sina.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=gthomas@cambridge.redhat.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).