<div dir="ltr">I forgot to say: I also think of a side effect of 4.10.2 patch for Mini2440. But where, do you think I may search for the side effect with this experimentals? I mean where can be effected by the side effect that this happens? The implementation of TCP/IP stack or I dunno somewhere else?<br>
<br><div class="gmail_quote">On Tue, Aug 28, 2012 at 2:02 AM, SAeeD <span dir="ltr"><<a href="mailto:salpha.2004@gmail.com" target="_blank">salpha.2004@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">As I traced the execution of RTEMS 4.10.2 with a simple TCP client application on QEMU, I got this experimental:<br>After setting up a TCP server in PC, I executed the TCP client on Mini2440 and traced the execution. A socket is created with socket descriptor #3. Every thing seems fine but when calling function "connect", after a long time hanging on the line 161 of the following context (rtems_syscall.c where function "connect" if implemented.), an error numbered #116 happens and I got out of the loop and return -1 as the return value of function "connect". This is the context:<br>
<br>160 while ((so->so_state & SS_ISCONNECTING) && so->so_error == 0) {<br>161 error = soconnsleep (so);<br>162 if (error)<br>163 break;<br>164 }<br>165 if (error == 0) {<br>
166 error = so->so_error;<br>167 so->so_error = 0;<br>168 }<br>169 bad:<br>170 so->so_state &= ~SS_ISCONNECTING;<br>171 m_freem (nam);<br>172 if (error)<br>173 errno = error;<br>
174 else<br>175 ret = 0;<br>176 rtems_bsdnet_semaphore_release ();<br>177 return ret;<br><br>What could be the possible problem? What is the meaning of error #116?<br><br>I think I should also mention that when sniffing packets on telnetd application, Mini2440 (which was running RTEMS 4.10.2) did not respond to ARP requests from my PC. After I manipulated my PC's ARP table manually, then Mini2440 didn't respond to my PC's TCP Syn packets so telnetd didn't work too.<br>
<br>Thanks for any hint<span class="HOEnZb"><font color="#888888"><br>SAeeD</font></span><div><div class="h5"><br><br><div class="gmail_quote">On Sun, Aug 26, 2012 at 6:37 PM, Joel Sherrill <span dir="ltr"><<a href="mailto:Joel.Sherrill@oarcorp.com" target="_blank">Joel.Sherrill@oarcorp.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<pre style="font-size:10pt;font-family:Tahoma;word-wrap:break-word">How do they fail? As far as I can remember, there are no network related changes between those versions. This may be a side effect of something else.
SAeeD <<a href="mailto:salpha.2004@gmail.com" target="_blank">salpha.2004@gmail.com</a>> wrote:
</pre><div><div>
<div>
<div dir="ltr">I must mention that I configured and compiled both version using --enable-networking and --enable-posix options.<br>
<br>
<div class="gmail_quote">On Sun, Aug 26, 2012 at 1:55 PM, SAeeD <span dir="ltr"><<a href="mailto:salpha.2004@gmail.com" target="_blank">salpha.2004@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">Dear all,<br>
<br>
I'm currently running network-demos on Mini2440 BSP.<br>
What makes me wonder is that various network-demos samples (like telnetd, http, netdemo) works on RTEMS 4.9.5 but not on RTEMS 4.10.2.<br>
The point is that both versions have the same network device driver. (As their c/src/lib/libbsp/arm/mini2440/network/network.c files are the same.)<br>
Also, I was able to send UDP packets in both versions so I think the problem is not related to device drivers. One more evidence: The demos for 4.10.2 doesn't work on QEMU for Mini2440 too. I also checked rtems_gluc.c for both versions to make sure that definition
of rtems_bsdnet_initialize_network() wasn't changed.<br>
Does anyone have any hint, suggestion, advice, etc.? I do really appreciate any comment.<br>
<br>
Thanks<span><font color="#888888"><br>
SAeeD<br>
</font></span></div>
</blockquote>
</div>
<br>
</div>
</div>
</div></div></div>
</blockquote></div><br></div></div></div>
</blockquote></div><br></div>