This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: config file for RedBoot in RAM without RedBoot in ROM
- From: Gary Thomas <gary at mlbassoc dot com>
- To: Nicolas Brouard <nicolas dot brouard at silicomp dot ca>
- Cc: ecos-discuss at sources dot redhat dot com
- Date: Wed, 11 Aug 2004 13:21:38 -0600
- Subject: Re: [ECOS] config file for RedBoot in RAM without RedBoot in ROM
- Organization: MLB Associates
- References: <MFENKKFPNAKOOKBAEHLHMEFLCCAA.nicolas.brouard@silicomp.ca>
On Wed, 2004-08-11 at 13:07, Nicolas Brouard wrote:
> Hi,
> To port redboot for a new platform, I'm following the porting guide which
> says that it is easier to start with a redboot in RAM if a ROM monitor is
> present. It is my case, so I would like to know how I could configure my
> ecos.ecc file for this redboot in RAM?
> I suppose the configuration file is special because virtual vectors and gdb
> stub are ordinary in ROM.
Start with
% ecosconfig new PLATFORM redboot
% ecosconfig tree
% make
RedBoot configured like this will take over the whole machine, virtual
vectors and all. Once this is working, you can transition to a ROM or
ROMRAM version.
This is how I port RedBoot to new hardware :-)
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss