public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: ANILA SOOMRO <dranne27@hotmail.com>
Cc: eCos Mailing List <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] eCos for MPC565 - new user
Date: Thu, 31 Jan 2008 11:56:00 -0000	[thread overview]
Message-ID: <20080131113415.GH26434@lunn.ch> (raw)
In-Reply-To: <BLU111-W13411CA9D1F106B42157EED8370@phx.gbl>

On Thu, Jan 31, 2008 at 10:41:30AM +0000, ANILA SOOMRO wrote:
> 
> 
> Hello
>  
> I am a new user of eCos and ultimately want to run eCos on a Phytec's MPC565 board.
> I have downloaded eCos and the the hal package does have a mpc5xx folder.
> I have read the instructions for rebuilding RedBoot which talks about the Redboot configuration file for that platform, redboot_RAM.ecm or redboot_ROM.ecm but these files are not available in the mpc5xx folder.
> Can anyone tell me from where to get these files or how to build RedBoot for MPC565 from the scratch?
> What steps do I need to follow to run RedBoot on MPC565?
> Any help would be highly appreciated.

The mpc5xx package provides generic code for the mpc5xx processor
family. In addition to that you need code specific to your board. eg
look at the cme555 and ec555 packages. These contain the
redboot_RAM.ecm files for that specific board.

You need to first port eCos to your specific board. I don't know the
PPC families, but maybe you can use either the ec555 or the cme555 as
a starting point.

  Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2008-01-31 11:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-31 11:00 ANILA SOOMRO
2008-01-31 11:56 ` Andrew Lunn [this message]
2008-01-31 16:11   ` Ilija Koco

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=20080131113415.GH26434@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=dranne27@hotmail.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    /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).