openrisc toolchains

[Jose Ignacio Villar]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Hello,
Currently I can see three efforts to provide a robust toolchain to openrisc developers:The new toolchain from orsoc and meansofreedom, The toolchain that you can build from embecosm EAN2 and the one called DRP by Mark Jarvin.

After many months without an unified effort to provide a common set of tools, I'm happy to see the "new toolchain" page on opencores  but I see that it contains old versions of Or1kSim and Linux, that and GDB is missing. So, my questions is wether GDB 6.8 and or1KSim 0.3.0 from Jeremy Bennet will be included or not in the manline Opencores toolchain script. I think this way all Openrisc community may have a common and well tested set of tools with the latest versions of every package being used and tested by everyone.

Currently I was successful to generate the complete toolchain with the automated script under ubuntu 8.10 32bits with binutils 2.18 and gcc 4.3.2, but a pair of patches were needed...

Here is a table with versions of every package of the three toolchains.

	DRP	Orsoc	Embecosm
Binutils	2.17	2.18.50	2.16.1
GCC	4.2.1	4.2.2	3.4.4
GDB	5.3	NA	6.8
ucLibC	0.9.28	0.9.29	0.9.28
Newlib	1.15.0	NA	NA
Linux	2.6.19	2.6.19	2.6.23
BusyBox	NA	1.7.5	NA
ucLinux	2.0.38	NA	NA
Or1KSim	0.2.0	0.2.0	0.3.0

Jose.

--
José Ignacio Villar <jose@...>
Departamento de Tecnología Electrónica
Escuela Técnica Superior de Ingeniería Informática
Universidad de Sevilla
Avda. Reina Mercedes, s/n
41012 - Sevilla (Spain)

Tlf: 954 55 61 60
Fax: [phone]


_______________________________________________
http://www.opencores.org/mailman/listinfo/openrisc

[Jeremy Bennett-4]

On Thu, 2009-03-05 at 00:10 +0100, Jose Ignacio Villar wrote:

> Hello,
> Currently I can see three efforts to provide a robust toolchain to
> openrisc developers:The new toolchain from orsoc and meansofreedom,
> The toolchain that you can build from embecosm EAN2 and the one called
> DRP by Mark Jarvin.
>
> After many months without an unified effort to provide a common set of
> tools, I'm happy to see the "new toolchain" page on opencores  but I
> see that it contains old versions of Or1kSim and Linux, that and GDB
> is missing. So, my questions is wether GDB 6.8 and or1KSim 0.3.0 from
> Jeremy Bennet will be included or not in the manline Opencores
> toolchain script. I think this way all Openrisc community may have a
> common and well tested set of tools with the latest versions of every
> package being used and tested by everyone.

Hi Jose,

Thanks for your contributions to this mailing list in recent days. They
will help to improve the tool chain in the future. I look forward to
seeing your future contributions.

The differences you see reflect the dynamics of open source development
and the priorities of individual, independent contributors.
- Mark Jarvin's tool chain dates from August 2007
- OpenCores script and vmware image pre-date GDB 6.8 and Or1ksim 0.3.0.
- EAN2 pre-dates GCC 4.2.2 and binutils 2.18.50

These latest versions are the cumulative work of (amongst many others) a
Canadian academic, a US telecoms engineer, a Swedish fabless design
house and a British embedded tools company. There are others as well,
for example the guide to the software tool chain from the De Nayer
Instituut in the Netherlands.

The upside is that the latest work on each component is always available
as the group specializing in it completes the work. The downside is that
there is not one rigidly enforced script, as you would get with a
commercial closed-source product.

> Currently I was successful to generate the complete toolchain with the
> automated script under ubuntu 8.10 32bits with binutils 2.18 and gcc
> 4.3.2, but a pair of patches were needed...

All new contributions are much appreciated. If you'd post a link to
where your script can be downloaded, I'll add it to the tool chain page
alongside the link to EAN2 and the De Nayer Instituut.

Best wishes, and I look forward to hearing more from you.


Jeremy

--
Tel:      [phone]
Cell:     [phone]
SkypeID: jeremybennett
Email:   jeremy.bennett@...
Web:     www.embecosm.com


_______________________________________________
http://www.opencores.org/mailman/listinfo/openrisc

[rich_daddio]

Hi Jose,
Just to follow on to Jeremy's point. The work on the toolchain is not
quite as disparate as it might seem. The releases are usually "patched
forward" from each other's work. So, for example, the 2.18.50 binutils
patch is derived from the 2.17 patch. The same holds true with gcc,
linux, and uclibc. Since we have been quite small over the past few
years this has not been too hard to manage.

In the case of efforts like MOF and Freecores
(http://www.freecores.org/wiki/Main_Page) these derivative projects
were reflective of some of the changes happening at Opencores at the
time. For the most part these grew out of concern for the project and
its goals rather than vectors for vector's sake.

Now that ORSoC has stablized the project our plan with the toolchain
and linux at least is to migrate back into the Openrisc project, and
then and then push to get our stuff into public repositories so that
non-scalable herculean individual efforts are not required to support
and chase after the constantly moving upgrade targets.


HTH & BR,

Rich d


----- Original Message -----
From: Jeremy Bennett<jeremy.bennett@e...>
To:
Date: Thu Mar  5 10:41:46 CET 2009
Subject: [openrisc] openrisc toolchains

> On Thu, 2009-03-05 at 00:10 +0100, Jose Ignacio Villar wrote:
> > Hello,
> > Currently I can see three efforts to provide a robust
> toolchain to
> > openrisc developers:The new toolchain from orsoc and
> meansofreedom,
> > The toolchain that you can build from embecosm EAN2 and the
> one called
> > DRP by Mark Jarvin.
> >
> > After many months without an unified effort to provide a
> common set of
> > tools, I'm happy to see the "new toolchain" page on
> opencores but I
> > see that it contains old versions of Or1kSim and Linux, that
> and GDB
> > is missing. So, my questions is wether GDB 6.8 and or1KSim
> 0.3.0 from
> > Jeremy Bennet will be included or not in the manline Opencores
> > toolchain script. I think this way all Openrisc community may
> have a
> > common and well tested set of tools with the latest versions
> of every
> > package being used and tested by everyone.
> Hi Jose,
> Thanks for your contributions to this mailing list in recent days.
> They
> will help to improve the tool chain in the future. I look forward
> to
> seeing your future contributions.
> The differences you see reflect the dynamics of open source
> development
> and the priorities of individual, independent contributors.
> - Mark Jarvin's tool chain dates from August 2007
> - OpenCores script and vmware image pre-date GDB 6.8 and Or1ksim
> 0.3.0.
> - EAN2 pre-dates GCC 4.2.2 and binutils 2.18.50
> These latest versions are the cumulative work of (amongst many
> others) a
> Canadian academic, a US telecoms engineer, a Swedish fabless design
> house and a British embedded tools company. There are others as
> well,
> for example the guide to the software tool chain from the De Nayer
> Instituut in the Netherlands.
> The upside is that the latest work on each component is always
> available
> as the group specializing in it completes the work. The downside is
> that
> there is not one rigidly enforced script, as you would get with a
> commercial closed-source product.
> > Currently I was successful to generate the complete toolchain
> with the
> > automated script under ubuntu 8.10 32bits with binutils 2.18
> and gcc
> > 4.3.2, but a pair of patches were needed...
> All new contributions are much appreciated. If you'd post a link to
> where your script can be downloaded, I'll add it to the tool chain
> page
> alongside the link to EAN2 and the De Nayer Instituut.
> Best wishes, and I look forward to hearing more from you.
> Jeremy
> --
> Tel: [phone]
> Cell: [phone]
> SkypeID: jeremybennett
> Email: jeremy.bennett at embecosm.com
> Web: www.embecosm.com
>
>

_______________________________________________
http://www.opencores.org/mailman/listinfo/openrisc