Re: [lwip-users] Re opening LWIP for new HTTP message

[Simon Goldschmidt]

"H.A." <address@hidden> wrote:
> Connection didn't open and no tcp output, nothing visible in Wireshark.
> OK,
> the open is a non-blocking command so it might take a "certain" amount of
> time for it to open. But it doesn't feel right to sit and wait for the
> connection to open inside an interrrupt routine.

Cretainly not! The raw API is an event-based API: you call tcp_connect() and 
return instead of watiting. Either your connected-callback (on successful 
connect) or your err-callback will be called later.

However, you should at least see a SYN packet going out when calling 
tcp_connect().

But as I mentioned before, the Stellaris port for lwIP I once had a look at was 
using lwIP in a strange way, so this *might* be a race condition of using lwIP 
from different interrupt-levels (or interrupt and main loop).

Simon