From: Andrew Lunn <andrew@lunn.ch>
To: "Deak, Ferenc" <ferenc.deak@stp.hu>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] cirrus ep93xx - ecos works, network problems
Date: Tue, 11 Oct 2005 14:10:00 -0000 [thread overview]
Message-ID: <20051011140956.GD1276@lunn.ch> (raw)
In-Reply-To: <20051011151746.ff95a045.ferenc.deak@stp.hu>
On Tue, Oct 11, 2005 at 03:17:46PM +0200, Deak, Ferenc wrote:
> > >
> > > We have a custom cirrus ep9307 based board. Cirrus has a software package
> > > for their ep93xx-based boards, which contains patches for linux and a
> > > redboot-only ecos. Redboot and linux works fine on our board. I have
> > > managed to work the basic ecos, but I have trouble with the network.
> > >
> > > Is there anybody who made the network work, and can help? We would be very
> > > thankful for any help.
> >
> > The normal problem here is that the network device driver for Redboot
> > is polled io, where as a full eCos device driver is interrupt
> > driven. I suggest you take a look at the device driver and see what it
> > actually implements.
>
> The problem is not so theoretical:-) I'm looking and testing and
> modifying the driver until yesterday. It seems that someone at cirrus have written
> the driver "correctly" because there is a redboot and a real-kernel related
> code in it, there is an IT initialised, a NETDEVTAB_ENTRY etc. (but,
> strange that the real IT related routines usually in hal/<proc>/src/proc_misc.c
> were missing from the patch, but I've added them...) Network ITs are working etc.
>
> The problem where I stopped: There is register in the network related part of the processor,
> which is set to 1 to sign that there is a new data filled and ready to send. But when this register
> is set to 1 second times the whole board stops working at this line, prints before this line are
> appearing but prints after are not. (but these lines are common with the redboot code, so
> perhaps these are algorithmically right)
> On the other hand the board cannot be ping-ed, end receive events are not comming (but these are
> coming under redboot...)
>
> So if somebody has an ideo to try, I would be very grateful.
What is the license on the code? Can you let us see it or is it closed
source?
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2005-10-11 14:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-11 12:01 Deak, Ferenc
2005-10-11 12:06 ` Andrew Lunn
2005-10-11 13:15 ` Deak, Ferenc
2005-10-11 14:10 ` Andrew Lunn [this message]
2005-10-11 15:54 ` Deak, Ferenc
2005-10-11 16:18 ` Deak, Ferenc
2005-10-13 14:27 ` Deak, Ferenc
2005-10-13 14:32 ` Gary Thomas
2005-10-17 13:10 ` Deak, Ferenc
2005-10-11 15:24 bob.koninckx
2005-10-11 16:09 ` Deak, Ferenc
2005-10-12 8:34 bob.koninckx
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=20051011140956.GD1276@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=ferenc.deak@stp.hu \
/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).