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

Hi Arpit, I am not sure I need to check. I know that the code uses something called virtual file system for devices that do not have a file system. Maybe you have a point there ... I will check that, thanks. when I commented the call to select and left to code to block on accept it also

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

Hi Noam, Just to clarify another thing, is the environment where you are trying to use lwip_select also uses select for file descriptors ? If yes then there is a possibility of malfunctioning as if I am not wrong lwip_select is not meant to be used with file descriptors as opposed normal BSD

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

Thanks I will check that tomorrow :-) From: lwip-users on behalf of goldsimon Sent: Wednesday, May 31, 2017 5:53 PM To: Mailing list for lwIP users Subject: Re: [lwip-users] LwIP 1.41 select does

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

Noam Weissman: >Were is the semaphore released ? In "event_callback()", if I remember correctly. Simon ___ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users

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

Noam Weissman wrote: >My question was simple ... does anyone have an idea why select > >does not return when a connection to the correct port is initiated. Can't help you much there other than saying: try to check the socket's status: is there an acceptable connection pending in the queue? Has

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

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 Sent: Wednesday,

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,

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

Hi Noam, Just to clarify another thing, is the environment where you are trying to use lwip_select also uses select for file descriptors ? If yes then there is a possibility of malfunctioning as if I am not wrong lwip_select is not meant to be used with file descriptors as opposed normal BSD

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

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

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.

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.

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

Hi Arpit, Thanks for the reply. I am not saying that lwip_select is the problem, I am using the socket API in in another application that I wrote and have no problems. It works as expected. The code I am trying to debug (not my code) is layered and is planed to portable to many systems

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

Hi Noam, I think lwip_select is not the problem. I have used it previously and it used to works with lwip 1.4.1 version. However as per your saying that select gets timeout, I would recommend you to debug event_callback API and verify if the socket descriptor you used in select has received

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

Hi Tim, I am aware of that but that did not answer my question. You can mix API's and I already have systems that use RAW API and Socket API and they coexists when you know the limitations. My question was simple ... does anyone have an idea why select does not return when a connection to

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

Hi All, I am trying to run a CypherBridge uSSH server demo on STM3240-Eval board. The original code was designed for ST discovery board with the same micro. The original code uses FreeRTOS 6.01 and LwIP 1.32 .. I am using a base project that is used for testing. This base project uses