[ECOS] porting ecos to a "new" hardavre.

[ECOS] porting ecos to a "new" hardavre.

[Ferenc Cserepkei]

Welcome.
I am maintaining some embedded hardvare, the board has some custom
brew bios. We should add tcp/ip (preferably V6) functionlity soon. The
existing BIOS the board has rather  dumb, its main functionalty is
BASIC configuration of the FPGAs and ASICs the board has, give  a
9600/8N1 serial, and upgrade sw parts in motorola s-record format (can
be streamed over serial). I already built a GCC 4.6.2 sporting
newlib1.20 for the main processor what is freescale MPC8548.
My question is, how can i tell ecos 3.0, to use that compiler (it has
GDB 7.3, psim and python support) and how can i design a template
"build>templates" for our systems?
Any help are much elcome.
BR:
Ferenc

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

Re: [ECOS] porting ecos to a "new" hardavre.

[Ilija Kocho]

On 04.03.2012 20:02, Ferenc Cserepkei wrote:
> Welcome.
> I am maintaining some embedded hardvare, the board has some custom
> brew bios. We should add tcp/ip (preferably V6) functionlity soon. The
> existing BIOS the board has rather  dumb, its main functionalty is
> BASIC configuration of the FPGAs and ASICs the board has, give  a
> 9600/8N1 serial, and upgrade sw parts in motorola s-record format (can
> be streamed over serial). I already built a GCC 4.6.2 sporting
> newlib1.20 for the main processor what is freescale MPC8548.
> My question is, how can i tell ecos 3.0, to use that compiler (it has
> GDB 7.3, psim and python support) and how can i design a template
> "build>templates" for our systems?

You actually need to introduce the path to your new compiler to your
environment. How to do it depends on your host system (OS, shell, etc).
What host do you use?

Ilija


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

Re: [ECOS] porting ecos to a "new" hardavre.

[Ilija Kocho]

On 05.03.2012 18:14, Ferenc Cserepkei wrote:
>  Ilija,
> thats all? so if i set it in the ecosenv.sh its okay? I'm using ubuntu
> 11.04/10.04 desktop edition.

If you are calling ecosenv.sh to set environment yes.
The alternative would be to add PATH entry in .bashrc
For instance, provided that your new gcc is under /opt/ecos/gnutools/bin
PATH="${PATH}":/opt/ecos/gnutools/arm-eabi/bin:/opt/ecos/gnutools/bin:/opt/ecos/ecos-3.0/tools/bin
shall first look for new and if it fails it will use the old gcc.

> What futher cdls shall i write, I mean flash, DDR(2) sdram, ethernet,
> etc? Have Ecos got some support for MPC8548? What shall I add, which
> CDL shall I write? As I discovered ecos has some gcc 3.4.x by default
> and only MPC 860. What should I do to have the MPC8548 fully
> supported?

eCos 3.0 is relatively old code so I would recommend you to get the
latest code from CVS. Look here for instructions:
http://ecos.sourceware.org/anoncvs.html

However I'm afraid MPC8548 is not supported by eCos and there's a lot to
do. AFAIK eCos doesn't have architectural port for e500 core so get
prepared for serious work.

On the bright side. the eCos porting process is well documented:
http://ecos.sourceware.org/docs-latest/ref/ecos-ref.html
http://ecos.sourceware.org/docs-latest/cdl-guide/cdl-guide.html
Also I would recommend you the book
http://www.informit.com/store/product.aspx?isbn=0130354732 by Anthony J.
Massa

I hope this helps you to start.

Ilija


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

RE: [ECOS] porting ecos to a "new" hardavre.

[Christophe Coutand]

For porting to the MPC8548, you can have a look at the port for the MPC8572 I committed some years ago, search eCos bugzilla for it. You can find a restructure  version of the patch here https://bitbucket.org/openetech/ecos. The patch is missing support for PCIe and SEC engine. For this device Freescale has removed the FPU and replaced it with the SPE which is not supported in the patch.

Christophe


-----Original Message-----
From: ecos-discuss-owner@ecos.sourceware.org [mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of Ilija Kocho
Sent: 6. mars 2012 19:04
To: Ferenc Cserepkei; ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] porting ecos to a "new" hardavre.

On 05.03.2012 18:14, Ferenc Cserepkei wrote:
>  Ilija,
> thats all? so if i set it in the ecosenv.sh its okay? I'm using ubuntu
> 11.04/10.04 desktop edition.

If you are calling ecosenv.sh to set environment yes.
The alternative would be to add PATH entry in .bashrc
For instance, provided that your new gcc is under /opt/ecos/gnutools/bin
PATH="${PATH}":/opt/ecos/gnutools/arm-eabi/bin:/opt/ecos/gnutools/bin:/opt/ecos/ecos-3.0/tools/bin
shall first look for new and if it fails it will use the old gcc.

> What futher cdls shall i write, I mean flash, DDR(2) sdram, ethernet,
> etc? Have Ecos got some support for MPC8548? What shall I add, which
> CDL shall I write? As I discovered ecos has some gcc 3.4.x by default
> and only MPC 860. What should I do to have the MPC8548 fully
> supported?

eCos 3.0 is relatively old code so I would recommend you to get the
latest code from CVS. Look here for instructions:
http://ecos.sourceware.org/anoncvs.html

However I'm afraid MPC8548 is not supported by eCos and there's a lot to
do. AFAIK eCos doesn't have architectural port for e500 core so get
prepared for serious work.

On the bright side. the eCos porting process is well documented:
http://ecos.sourceware.org/docs-latest/ref/ecos-ref.html
http://ecos.sourceware.org/docs-latest/cdl-guide/cdl-guide.html
Also I would recommend you the book
http://www.informit.com/store/product.aspx?isbn=0130354732 by Anthony J.
Massa

I hope this helps you to start.

Ilija


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