This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Running from Redboot
- From: Gary Thomas <gary at mlbassoc dot com>
- To: Unni Nair <manjunni at yahoo dot com>
- Cc: eCos Discussion <ecos-discuss at sources dot redhat dot com>
- Date: 15 Aug 2003 12:53:34 -0600
- Subject: Re: [ECOS] Running from Redboot
- Organization: MLB Associates
- References: <20030815181540.62251.qmail@web14606.mail.yahoo.com>
On Fri, 2003-08-15 at 12:15, Unni Nair wrote:
> I have redboot compiled for RAM for a proprietary
> MPC860 target and
> running using a Vision Probe emulator. The CLI prompt
> is given below
>
> RedBoot(tm) bootstrap and debug environment [RAM]
> Non-certified release, version UNKNOWN - built
> 16:28:54, Aug 14 2003
> Platform: Proprietary (Motorola PowerPC 8xx Family)
> Copyright (C) 2000, 2001, 2002, Red Hat, Inc.
> RAM: 0x00000000-0x00400000, 0x00085938-0x00400000
> available
> RedBoot>
>
> Unfortunately when I compile a sample application with
> ECOS (default
> selected in the template), the code is build for RAM
> starting at address
> 0x70000 (which is the end of the section
> reserved_for_rom in the header
> file located in the "pkgconf" directory). When I try
> to load this into
> the target using redboot, the memory location where
> the data is sent to
> (0x70000) is less that the current available start
> location (0x85938).
> I have a RAM only system, where the redboot and ecos
> are going into the
> same memory.
>
> Could anyone please let me know what my problem is and
> how to coorect
> this situation.
The easiest way is to modify your RAM 'MLT' files to match
this new memory layout and then rebuild your application.
What have you put into RedBoot to make it be so huge?
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss