[ECOS] cirrus ep93xx - ecos works, network problems

[ECOS] cirrus ep93xx - ecos works, network problems

[Deak, Ferenc]

Dear sirs,

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.


Thanks in advance,
Ferenc Deak 



-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] cirrus ep93xx - ecos works, network problems

[Andrew Lunn]

On Tue, Oct 11, 2005 at 02:04:25PM +0200, Deak, Ferenc wrote:
> 
> Dear sirs,
> 
> 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.

        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

Re: [ECOS] cirrus ep93xx - ecos works, network problems

[Deak, Ferenc]

> > 
> > 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.

Ferenc


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] cirrus ep93xx - ecos works, network problems

[Andrew Lunn]

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

Re: [ECOS] cirrus ep93xx - ecos works, network problems

[Deak, Ferenc]

 
> What is the license on the code? Can you let us see it or is it closed
> source?

License of our modifications are ok, I will check the cirrus licence tomorrow, but anyway it is
an ecos add-on using the ecos driver API, so it GPL isn't it? (by the way the patch is for ecos 2.0).

Ferenc Deak



-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] cirrus ep93xx - ecos works, network problems

[Deak, Ferenc]

 
> > > 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.
> 

In the meantime I'm implemented the trick found in the cs8900a driver, which can
be configured to use a thread (continously calling { cyg_thread_delay(5); s = splnet();
ep93xx_poll(sc); splx(s); } instead of using interrupts, but it is not help anything.

By the way, is this trick have to work at all, or is this a "dead-end" left in the code?

Ferenc Deak


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] cirrus ep93xx - ecos works, network problems

[Deak, Ferenc]

Just for people who will searching the list, I would like to place mark here, that the 
problems are solved, ecos(not redboot) & network is ok for ep93xx.


On Tue, 11 Oct 2005 14:04:25 +0200
"Deak, Ferenc" <ferenc.deak@stp.hu> wrote:

> 
> Dear sirs,
> 
> 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.
> 
> 
> Thanks in advance,
> Ferenc Deak 
> 
> 
> 
> -- 
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> 


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] cirrus ep93xx - ecos works, network problems

[Gary Thomas]

On Thu, 2005-10-13 at 16:29 +0200, Deak, Ferenc wrote:
> Just for people who will searching the list, I would like to place mark here, that the 
> problems are solved, ecos(not redboot) & network is ok for ep93xx.
> 

What did you end up needing to do to make this work?

> 
> On Tue, 11 Oct 2005 14:04:25 +0200
> "Deak, Ferenc" <ferenc.deak@stp.hu> wrote:
> 
> > 
> > Dear sirs,
> > 
> > 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.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] cirrus ep93xx - ecos works, network problems

[Deak, Ferenc]

On Thu, 13 Oct 2005 08:32:28 -0600
Gary Thomas <gary@mlbassoc.com> wrote:

> On Thu, 2005-10-13 at 16:29 +0200, Deak, Ferenc wrote:
> > Just for people who will searching the list, I would like to place mark here, that the 
> > problems are solved, ecos(not redboot) & network is ok for ep93xx.
> > 
> 
> What did you end up needing to do to make this work?

There were few errors on the driver.

We will check the licence issues of the code from cirrus, and we can, we will create an ecos package for ep93xx.

Best regards,
Ferenc Deak



-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] cirrus ep93xx - ecos works, network problems

[bob.koninckx]

---- Original message ----
>Date: Tue, 11 Oct 2005 18:10:48 +0200
>From: "Deak, Ferenc" <ferenc.deak@stp.hu>  
>Subject: Re: [ECOS] cirrus ep93xx - ecos works, network 
problems  
>To: ecos-discuss@ecos.sourceware.org
>
>On Tue, 11 Oct 2005 11:24:30 -0400
><bob.koninckx@o-3s.com> wrote:
>
>> I am not sure if I understand correctly what you describe. 
I 
>> remember running into problems in the past because of 
calls 
>> to HAL_DELAY_US in the network code. You say something 
about 
>> changing timeouts to the order of magnitude of seconds, so 
>> keep in mind that HAL_DELAY_US implements a busy wait, 
which 
>> could start waiting for a _very_ long period of time if 
you 
>> do that. The behavior you describe indicates that it could 
be 
>> something like that.
>> 
>> Bob
>
>First, am I understand you correctly that you have a working 
network
>stack for ecos (not redboot) with ep93xx?

No

>
>I'm sorry if my english is a little bit confusing, but I did 
not intend to talk about
>timeouts, and I'm not changed any timeouts. The only timeout 
in the
>driver is in the init function, so I think this is not the 
problem...
>
>Thanks for your help,
>Ferenc Deak
>
>
>-- 
>Before posting, please read the FAQ: 
http://ecos.sourceware.org/fom/ecos
>and search the list archive: 
http://ecos.sourceware.org/ml/ecos-discuss
>

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] cirrus ep93xx - ecos works, network problems

[Deak, Ferenc]

On Tue, 11 Oct 2005 11:24:30 -0400
<bob.koninckx@o-3s.com> wrote:

> I am not sure if I understand correctly what you describe. I 
> remember running into problems in the past because of calls 
> to HAL_DELAY_US in the network code. You say something about 
> changing timeouts to the order of magnitude of seconds, so 
> keep in mind that HAL_DELAY_US implements a busy wait, which 
> could start waiting for a _very_ long period of time if you 
> do that. The behavior you describe indicates that it could be 
> something like that.
> 
> Bob

First, am I understand you correctly that you have a working network
stack for ecos (not redboot) with ep93xx?

I'm sorry if my english is a little bit confusing, but I did not intend to talk about
timeouts, and I'm not changed any timeouts. The only timeout in the
driver is in the init function, so I think this is not the problem...

Thanks for your help,
Ferenc Deak


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] cirrus ep93xx - ecos works, network problems

[bob.koninckx]

I am not sure if I understand correctly what you describe. I 
remember running into problems in the past because of calls 
to HAL_DELAY_US in the network code. You say something about 
changing timeouts to the order of magnitude of seconds, so 
keep in mind that HAL_DELAY_US implements a busy wait, which 
could start waiting for a _very_ long period of time if you 
do that. The behavior you describe indicates that it could be 
something like that.

Bob


---- Original message ----
>Date: Tue, 11 Oct 2005 16:09:56 +0200
>From: Andrew Lunn <andrew@lunn.ch>  
>Subject: Re: [ECOS] cirrus ep93xx - ecos works, network 
problems  
>To: "Deak, Ferenc" <ferenc.deak@stp.hu>
>Cc: ecos-discuss@ecos.sourceware.org
>
>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
>

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss