This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: ram usage by redboot
- From: Gary Thomas <gary at mlbassoc dot com>
- To: Bob dot Brusa at gmail dot com
- Cc: "MailingList:ecos-discuss ;" <ecos-discuss at ecos dot sourceware dot org>
- Date: Tue, 02 Jun 2009 05:27:20 -0600
- Subject: Re: [ECOS] ram usage by redboot
- References: <op.uuu2huh6keg3uf@localhost>
Robert Brusa wrote:
> Hi all
> I have configured a redboot (using ecos-3.0) for my target. Upon power
> up it writes out (among a lot of other stuff):
>
> Platform: AT91ICB (ARM7TDMI)
> RAM: 0x00200000-0x00220000 [0x00204c48-0x0021f300 available]
> FLASH: 0x00100000-0x0013ffff, 1024 x 0x100 blocks
>
> This makes me wunder:
> a) What is the RAM up from 0x0021f300 used for? I can find no hint in
> the map.
It's used as an ad-hoc workspace, mostly for manipulating FLASH. Since
the details of the FLASH device are not necessarily at compile time, this
has to be dynamic (e.g. the size of a FLASH erase page). Carving this
off the end was the simplest way to solve these problems.
> b) It writes out the flash available on this machine. Why not the flash
> actually available for other programs?
This information is too dynamic/complex for a single print. You get that
from 'fis free'
> Thanks for comments on this issue.
> Robert
>
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss