public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Øyvind Harboe" <oyvind.harboe@zylin.com>
To: "Grant Edwards" <grante@visi.com>,
	 	"eCos Disuss" <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Nios eCos repository
Date: Thu, 04 Dec 2008 17:24:00 -0000	[thread overview]
Message-ID: <c09652430812040748n3a4cc0ack39c61423841cd76e@mail.gmail.com> (raw)

>> I'm putting together a Nios eCos repository based on
>> nios2ecos51.exe that Altera published a couple of years back.
>> This version of eCos HAL is under the eCos license.
>
> Is it a real eCos port, or does it require you to install
> Quartus and generate cdl files on the fly using Altera's bogus
> Java programs and XML tempates?

:-)

It still requires Quartus installed and it stll generates cdl files on
the fly, but I've solved some of the nastier problems in that it
can be used with any version of eCos or Quartus.

I don't have a fundamental problem with having the .ptf file as
an input to the build process now that I've rearranged things a bit.

I'd like to be able to commit the tools I use for a product to version
control, so long term I'd like to remove the dependance on Quartus...

Help appreciated!!!

>> This includes a version of OpenCores Ethermac and eCos drivers
>> which works with NEEK. The OpenCores Ethermac is a bit better
>> impeadance match with eCos as it is much smaller than TSE.
>
> Which version of the OC mac?  Is it the recent re-write that
> uses Altera's interconnect bus or the older buggy version with
> the Avalon wrapper around a Wishbone interface?

It is the recent rewrite PLUS the bugfixes that jakobjones added
after I reported various bugs in the last couple of days.

If you can have an FPGA engineer produce .ptf + .sof file
that doesn't have any timing mistakes, I think it will work fine now.

>
>> The OpenCores Ethermac for Altera needed work, but thanks to
>> jakobjones it RX and TX now seems to work fine.
>
> The scary thing about that MAC is that it "seems" to work fine
> until you stress it, then it starts dropping packets,
> overrunning buffers, and doing various other bad things.

It is *MUCH* better now that jakobjons fixed some tx + rx bugs
in the last couple of days. The HDL is committed to ecosforge.net as well.

TCP/IP is nasty in that it will work surprisingly well with busted hardware....


-- 
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 XScale Cortex
JTAG debugger and flash programmer

--
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:[~2008-12-04 15:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-04 17:24 Øyvind Harboe [this message]
2008-12-04 17:39 ` [ECOS] " Grant Edwards
2008-12-04 17:39 ` Grant Edwards
  -- strict thread matches above, loose matches on Subject: below --
2008-12-03 15:04 [ECOS] " Øyvind Harboe

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=c09652430812040748n3a4cc0ack39c61423841cd76e@mail.gmail.com \
    --to=oyvind.harboe@zylin.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=grante@visi.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).