public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS]  Re: Preliminary questions on eCOS
Date: Tue, 20 Mar 2007 14:54:00 -0000	[thread overview]
Message-ID: <etosig$2km$1@sea.gmane.org> (raw)
In-Reply-To: <A46C7A571BBD3541902BE34330F0312C2C3ECB@mb01e201.malca.ds.magellanaerospace.com>

On 2007-03-20, JS Stoezel <js.stoezel@magellan.aero> wrote:

> I see there is no tool chain for this type of processor (this
> is stated here: http://ecos.sourceware.org/ecos/getstart.html). 
> However I can read: "Developers targeting one of the other
> architectures must build a toolchain themselves at present.
> Full instructions for downloading source code and building a
> toolchain are available.". Doesn't this mean I can port eCOS
> to the tool chain I am using?

It means that if you want to target an architecture for which
there aren't a pre-built gcc/binutils tool-chains, you have to
download the gcc/binutils sources and build a tool-chain.

eCos uses a number of gcc C and C++ extensions as well as some
rather unique binutils features. In theory you could port eCos
to another tool-chain, but it's going to be tough. People on
the mailing list have talked about attempting to do such a
port, but I don't think anybody has reported success.

I'd probably look at other RTOSes (FreeRTOS, XMK, uC/OS-II)
before I'd start thinking about porting eCos to a 16-bit
processor using a non-gcc tool-chain.  Though if you succeed
you'll be the first to do so with either a 16-bit target or a
non-gcc tool-chain, and you'll indeed be rolling in geek-points.

-- 
Grant Edwards                   grante             Yow!  People humiliating
                                  at               a salami!
                               visi.com            


-- 
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:[~2007-03-20 14:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-20 14:17 [ECOS] " JS Stoezel
2007-03-20 14:41 ` [ECOS] " Grant Edwards
2007-03-20 14:43   ` JS Stoezel
2007-03-20 14:54     ` Grant Edwards [this message]
2007-03-20 15:00       ` JS Stoezel
2007-03-20 15:07         ` Grant Edwards
2007-03-20 18:00     ` Paul D. DeRocco

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='etosig$2km$1@sea.gmane.org' \
    --to=grante@visi.com \
    --cc=ecos-discuss@sources.redhat.com \
    /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).