This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Redboot available RAM
- From: Nick Garnett <nickg at ecoscentric dot com>
- To: "Marcin Chrusciel" <Marcin dot chrusciel at cit dot be>
- Cc: <ecos-discuss at ecos dot sourceware dot org>
- Date: 20 Jun 2006 09:50:25 +0100
- Subject: Re: [ECOS] Redboot available RAM
- References: <4833790BBC8C1748ABE1E781F17425F30E572C@citexchange.cit.be>
"Marcin Chrusciel" <Marcin.chrusciel@cit.be> writes:
> Laurie,
>
> Yesterday I tried your tip, but it didn't help in my case. I will
> explain how I do it:
>
> I take i386 Realtek template, choose redboot in packages, then I go to
> eCos HAL -> i386 architecture -> I check Load into higher memory (I
> accept solutions for conflicts) and then I go for Startup type - I
> change it for floppy and I get a conflict that I should use GRUB, but I
> discard a solution so it stays Floppy. It builds fine and image starts
> properly but still the same amount of available RAM appears (about 64k)
>
> Any ideas??? Thanx;)
FLOPPY startup will only load into the bottom 640K and will only use
memory in that area. It is really only intended for use with RedBoot,
although applications that can live in 640K will work too.
To run applications above 1M either load RAM startup applications with
a FLOPPY RedBoot, use a GRUB-loaded RedBoot to load them, or load the
application directly using a GRUB startup type.
--
Nick Garnett eCos Kernel Architect
http://www.ecoscentric.com The eCos and RedBoot experts
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss