MC9S12NE64

Hi, I'm using the MC9S12NE64 with the Freescale version of OpenTCP and
I'm having some problems the the tcp/ip-stack. It sometimes doesn't
ACK received data packets, which results in retransmissions. The
problem doesen't seem to be related to high volume traffic all, tough
the problem becomes more acute when a lot of data is being received
and transmitted. Is someone using this tcp/ip-stack and having the
same problems as me? I would also be interested in other peoples
experiences with OpenTCP.

Best Wishes

Johnny Karlsson

If you cannot resolve your problem, you may want to check out CMX at
www.cmx.com.  CMX offers a small TCP/IP stack called CMX-MicroNet that
works quite well on the MC9S12NE64 and is fully supported, etc.  A free
evaluation version of the software for this chip can be downloaded from
the CMX website, as well.

<embeddedsys999@hotmail.com> wrote in message 
news:1118237285.864533.108910@f14g2000cwb.googlegroups.com...
> If you cannot resolve your problem, you may want to check out CMX at
> www.cmx.com.  CMX offers a small TCP/IP stack called CMX-MicroNet that
> works quite well on the MC9S12NE64 and is fully supported, etc.  A free
> evaluation version of the software for this chip can be downloaded from
> the CMX website, as well.


Mine is running in Uip....

but only 7Kb/S from MMC card for each conenction :(

but it kan handle 10 connections a 7Kb/s.....
(caused by windowze is quite slow to ack)

Kasper

"Repzak" <repzakGED@hotmail.com> wrote in message news:<42a877c0$0$18650$14726298@news.sunsite.dk>...
> <embeddedsys999@hotmail.com> wrote in message 
> news:1118237285.864533.108910@f14g2000cwb.googlegroups.com...
> > If you cannot resolve your problem, you may want to check out CMX at
> > www.cmx.com.  CMX offers a small TCP/IP stack called CMX-MicroNet that
> > works quite well on the MC9S12NE64 and is fully supported, etc.  A free
> > evaluation version of the software for this chip can be downloaded from
> > the CMX website, as well.
> 
> 
> Mine is running in Uip....
> 
> but only 7Kb/S from MMC card for each conenction :(
> 
> but it kan handle 10 connections a 7Kb/s.....
> (caused by windowze is quite slow to ack)
> 
> Kasper

I found the the problem now, it was a bug in OpenTCP, i sent a patch
to the maintainer of Freescale OpenTCP so hopefully the fix will be
integrated in the next release. 7Kb/S seems really slow if your using
the MC9212NE64, i can't give you a speed mesurement for OpenTCP but it
seems faster then that.

johnny.karlsson@gmail.com (Johnny Karlsson) writes:
> I found the the problem now, it was a bug in OpenTCP, i sent a patch
> to the maintainer of Freescale OpenTCP so hopefully the fix will be
> integrated in the next release.

If it's a reasonably small patch, could you just post it here for the
rest of us?

Thanks!
Eric

Could you please explain what was the problem and how to fix it? that
would be very helpful for us that are working with OpenTCP on NE64.


Thanks

"ReneT" <Rene.Trenado@Embeddia.com> wrote in message news:<1118426888.066207.318380@g43g2000cwa.googlegroups.com>...
> Could you please explain what was the problem and how to fix it? that
> would be very helpful for us that are working with OpenTCP on NE64.
> 
> 
> Thanks

Ok, i'll try and exlain it here, i could make a patch if you want me
to. This applies to the latest Freescale OpenTCP(FSOTCP_1-0.tgz)
release.

In  the tcp.c, function process_tcp_in(), line 1335 we have this
return statement. "return(0); //jpw added per steve testing". This
return statement is
used when a ack is received when we are in Connected mode. The problem
with that is if the received package contains both data and ack then
the data gets discarded. So removing the line "return(0); //jpw added
per steve testing" solves the problem.

This does cause the possibility that a DATA event in the event handler
function may happen even when there is no data. But i guess that it
should be possible to recieve empty data packages. If not then it easy
to check before issuing the data event if the len variable is bigger
than zero. 

//Johnny

>Hi, I'm using the MC9S12NE64 with the Freescale version of OpenTCP and
>I'm having some problems the the tcp/ip-stack. It sometimes doesn't
>ACK received data packets, which results in retransmissions. The
>problem doesen't seem to be related to high volume traffic all, tough
>the problem becomes more acute when a lot of data is being received
>and transmitted. Is someone using this tcp/ip-stack and having the
>same problems as me? I would also be interested in other peoples
>experiences with OpenTCP.
>
>Best Wishes
>
>Johnny Karlsson
>

Hi, I'm also using the MC9S12NE64 with the OpenTCP from Freescale and I'
haveing some Problems with the ACK. It sometimes ACK received data with a
old sequence number and therefore there are a lot of retransmissions. Th
problem is independent from traffic. It seems that soc->receive_next wil
not be incremented correctly. 

Does someone know about the problem?

Best Regards,

Florian Eibensteiner




		
This message was sent using the comp.arch.embedded web interface o
www.EmbeddedRelated.com

florian skrev:

> >Hi, I'm using the MC9S12NE64 with the Freescale version of OpenTCP and
> >I'm having some problems the the tcp/ip-stack. It sometimes doesn't
> >ACK received data packets, which results in retransmissions. The
> >problem doesen't seem to be related to high volume traffic all, tough
> >the problem becomes more acute when a lot of data is being received
> >and transmitted. Is someone using this tcp/ip-stack and having the
> >same problems as me? I would also be interested in other peoples
> >experiences with OpenTCP.
> >
> >Best Wishes
> >
> >Johnny Karlsson
> >
>
> Hi, I'm also using the MC9S12NE64 with the OpenTCP from Freescale and I'm
> haveing some Problems with the ACK. It sometimes ACK received data with an
> old sequence number and therefore there are a lot of retransmissions. The
> problem is independent from traffic. It seems that soc->receive_next will
> not be incremented correctly.
>
> Does someone know about the problem?
>
> Best Regards,
>
> Florian Eibensteiner
>
>
>
>
>
> This message was sent using the comp.arch.embedded web interface on
> www.EmbeddedRelated.com

Hi, this could be related the the bug i reported. Please try the
recommended solution i posted. If that doesn't work the perhaps your
could post some more detailed information about the problem.

Best Regards 

Johnny Karlsson

>
>florian skrev:
>
>> >Hi, I'm using the MC9S12NE64 with the Freescale version of OpenTC
and
>> >I'm having some problems the the tcp/ip-stack. It sometimes doesn't
>> >ACK received data packets, which results in retransmissions. The
>> >problem doesen't seem to be related to high volume traffic all, tough
>> >the problem becomes more acute when a lot of data is being received
>> >and transmitted. Is someone using this tcp/ip-stack and having the
>> >same problems as me? I would also be interested in other peoples
>> >experiences with OpenTCP.
>> >
>> >Best Wishes
>> >
>> >Johnny Karlsson
>> >
>>
>> Hi, I'm also using the MC9S12NE64 with the OpenTCP from Freescale an
I'm
>> haveing some Problems with the ACK. It sometimes ACK received data wit
an
>> old sequence number and therefore there are a lot of retransmissions
The
>> problem is independent from traffic. It seems that soc->receive_nex
will
>> not be incremented correctly.
>>
>> Does someone know about the problem?
>>
>> Best Regards,
>>
>> Florian Eibensteiner
>>
>>
>>
>>
>>
>> This message was sent using the comp.arch.embedded web interface on
>> www.EmbeddedRelated.com
>
>Hi, this could be related the the bug i reported. Please try the
>recommended solution i posted. If that doesn't work the perhaps your
>could post some more detailed information about the problem.
>
>Best Regards 
>
>Johnny Karlsson
>
>

Hi,

i have removed that statement but it doesn't help. Your patch enable
receiving data packets without the PSH flag, but the software on the p
always sets this flag.

As i mentioned before, soc->receive_next seems to be false. Every secon
or third packet is retransmitted because sequence number check (in tcp.
line 1340) fails.

I used the original FSOTCP_1.0, therefore the problem must be in ever
application where MC9S12NE64 is used as client.

Best Regards

Florian Eibensteiner
		
This message was sent using the comp.arch.embedded web interface o
www.EmbeddedRelated.com