public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: John Carter <john.carter@taitradio.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Cyclone V, Nios II, Ecos, hal-synth on Nios - Repost with clean subject line.
Date: Tue, 01 Mar 2016 22:21:00 -0000	[thread overview]
Message-ID: <CAFD1m3FjyRiYtKzyERpsX08A6QiWNKw27yhKt8cv=DZ4aNsVXQ@mail.gmail.com> (raw)

Sorry subject line in previous post, copy / paste failure. :-(

So we have been running the open source version of Ecos on Cyclone III on Leon2.

We are now considering moving to Cyclone V running Linux on Nios2.

As a porting step, we want to port the Ecos i86 synth HAL to nios, and
run our existing application as a multithreaded Ecos application
residing within a single Linux process.

The obvious way to go about it would be to mash up the nios HAL
available from here...
   http://www.ecoscentric.com/ecospro/nios2.shtml
with the i86 synth hal.

But the fine fine print seems problematic....

> Congratulations, your purchase of the Altera Nios II Development Kit - either the Stratix® II FPGA Edition or the Cyclone® II FPGA Edition, entitles you to a free copy of eCosCentric's eCosPro Starter Kit. The Starter Kit includes all the necessary tools, runtime code and documentation you need to develop royalty and license fee free embedded applications running on Altera's Nios II core.


Alas, we have Cyclone V developer kits and intent to deploy on Cyclone V.

I have a vague memory of reading or hearing that Altera paid for the
Nios port with the aim of selling more chips.

So it would make sense that the actual fine print of that deal didn't
limit it to those older generation chips.

Anybody know for sure?

Alternately, if that fine print says what it says and is immutable..

We could take the open source ecos and rewrite the approximately 800
lines of i386 assembler into Nios.

Or perhaps we could create a CPU agnostic version out of signals and
libc getcontext / swapcontext.

Any ideas? Or suggestions?


-- 
John Carter
Phone : (64)(3) 358 6639
Tait Electronics
PO Box 1645 Christchurch
New Zealand

-- 

------------------------------
This Communication is Confidential. We only send and receive email on the
basis of the terms set out at www.taitradio.com/email_disclaimer
------------------------------

--
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:[~2016-03-01 22:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-01 22:21 John Carter [this message]
2016-03-01 23:30 ` [ECOS] " Grant Edwards
2016-03-02 14:29   ` Edgar Grimberg

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='CAFD1m3FjyRiYtKzyERpsX08A6QiWNKw27yhKt8cv=DZ4aNsVXQ@mail.gmail.com' \
    --to=john.carter@taitradio.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).