From: John Newlin <jnewlin@gmail.com>
To: Balasaravanan P <pbalasaravanan@gmail.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Ecos port for Xtensa processor core.
Date: Wed, 15 Jun 2005 17:46:00 -0000 [thread overview]
Message-ID: <3f4bf60c050615104618393779@mail.gmail.com> (raw)
In-Reply-To: <122f8500050614232347cee878@mail.gmail.com>
> Hi,
>
> Is there a port for Xtensa processor core available already.
> Is anybody using Ecos for Xtensa processor.
>
> Thanks,
> Bala.
Tensilica supplies a working version of Redboot, based on the old 1.1
code. At my previous company (www.stretchinc.com) I ported their code
to the latest ECOS CVS. I finished most of the port (and fixed a ton
of bugs :P) but never had time to get ECOS running. I suspect it
would not be terribly difficult, assuming you don't run into serious
tool issues with C++. Neither Tensilica nor Stretch submitted their
changes back, but if you are Tensilica Licensee, you probably have
their code anyhow.
The latest compiler from Tensilica is no longer gcc based, instead
they have a compiler based on the Open64 compiler from MIPS, so there
may be some issues with C++ if you do not have the gcc compiler for
Xtensa.
(Shameless plug for Stretch...)
If you are embedding an Xtensa, you might want to look at Stretch.
They have a part and development board that lets you create the
equivalent of TIE instructions and run them at speed (300Mhz). ;)
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2005-06-15 17:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-15 6:23 Balasaravanan P
2005-06-15 17:46 ` John Newlin [this message]
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=3f4bf60c050615104618393779@mail.gmail.com \
--to=jnewlin@gmail.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=pbalasaravanan@gmail.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).