Re: [lwip-users] PolarSSL and mbedTLS

Hi Simon, with SSL there is a read for 5 bytes record header and then reading the data itself as a whole or in parts (inside lwip_recvfrom). My module is a single task that has a state machine. When the state is in OPEN state it blocks for 1 second on select, if select is returning with a

Re: [lwip-users] PolarSSL and mbedTLS

Noam, that sounds a bit too complicatied... My first thought is: you call select and it returns that there is data to read, but that does not mean there is enough data to read for TLS, so EWOULDBLOCK is not an error at all in this case. Simon ___

Re: [lwip-users] PolarSSL and mbedTLS

Hi Simon, In my first mail regarding this situation I wrote the errno but hear it is again. It is EWOULDBLOCK >From checking again the net_socket.c file from mbedTLS I see that they have >two function: mbedtls_net_recv

Re: [lwip-users] PolarSSL and mbedTLS

Noam Weissman wrote: I am not ignoring the fact that it may be the driver or definitions but I am simply asking for leads... That's what I thought I gave in the last mail. OTOH, for getting the errno set by recvfrom, you don't have to be an lwIP developer... Simon