Re: [lwip-users] LwIP 1.41 select does not return ?

[Noam Weissman]

Thanks Tim,

Its not a migration issue..

I am simply trying to run a socket based module that I have not written and I am encountering

issues that I am not finding whats wrong, so far 😊

Thanks,

Noam.

---

From: Tim Cussins <address@hidden>
Sent: Wednesday, May 31, 2017 4:30 PM
To: Noam Weissman; address@hidden
Subject: Re: [lwip-users] LwIP 1.41 select does not return ?

 

Hi Noam,

OK, cool. It sounds like you're on top of the whole raw/netconn thing. I
was really checking to see whether you'd failed to start the tcpip
thread,
or some other setup issue that might come about from migrating from raw
API to netconn for the first time.

So I agree that, in your case, switching off the raw API probably won't
change anything :)

Sorry I couldn't be of more help!

Cheers,
Tim

On Wed, May 31, 2017, at 02:10 PM, Noam Weissman wrote:
> Hi Tim,
>
>
> RAW API is used in multi threaded application with one limitation. All
> RAW API handling must be in the same context as the TCP stack. This
> limitation is kept and works fine.
>
>
> I am running a HTTP server + a TCP server both use the RAW API + a WSS
> client written with the socket API and have ZERO issues.
>
> In my original question I am talking on something else. I have no
> problems turning off the RAW API, comment the use of my TCP server and
> I will be very surprised if that will make any difference. I will test
> that tomorrow :-)
>
>
> Thanks,
>
> Noam.
>
> ________________________________
> From: lwip-users <lwip-users-bounces+address@hidden> on behalf
> of Tim Cussins <address@hidden>
> Sent: Wednesday, May 31, 2017 1:43 PM
> To: address@hidden
> Subject: Re: [lwip-users] LwIP 1.41 select does not return ?
>
> Hi Noam,
>
> On Wed, May 31, 2017, at 11:11 AM, Noam Weissman wrote:
>
> > I am using a base project that is used for testing. This base project
> > uses FreeRTOS 8.01 + LwIP 1.41
> > +  a few modules that work just fine. The base project has a DHCP client
> > and a TCP server (Raw API)
> > that work just fine.
> >
> >
> > I have enabled sockets and netcon in lwipopts.h ... in general it seems
> > to load properly and run.
>
> > My own TCP server that listens on port 23 and the rest of the system
> > works just fine
> >
> >
> > Any ideas what did I miss or what should I check ?
> >
>
> Just a quick check: The raw API is not meant to be used in a
> multi-threaded system. Is your working TCP server using this API? If so,
> I expect your TCP server would work, but your calls to the netconn API
> (or sockets, which uses netconn under the hood) would probably dead-end
> in the way you're seeing.
>
> Have a look at the first couple of paragraphs here:
>
> http://lwip.wikia.com/wiki/Netconn_API

Netconn API | lwIP Wiki | Fandom powered by Wikia

lwip.wikia.com

The netconn API is a sequential API designed to make the stack easier to use (compared to the event-driven raw API) while still preserving zero-copy functionality.

> Netconn API | lwIP Wiki | Fandom powered by
> Wikia<http://lwip.wikia.com/wiki/Netconn_API>

Netconn API | lwIP Wiki | Fandom powered by Wikia

lwip.wikia.com

The netconn API is a sequential API designed to make the stack easier to use (compared to the event-driven raw API) while still preserving zero-copy functionality.

> lwip.wikia.com
> The netconn API is a sequential API designed to make the stack easier to
> use (compared to the event-driven raw API) while still preserving
> zero-copy functionality.
>
>
>
> HTH,
> Tim
>