Hi all, I've got a system running a connection-less tcp client which
periodically opens/sends/closes some telemetry to a backend.
On occasion, when a connection failure occurs (link/server is down), the
following open connection that succeeds (server/link is back online) will
result in its tcb lis
On 28 Jan 2012, at 19:15, Sylvain Bernard wrote:
> I've seen a couple old posts on a similar issue but no mentions on a possible
> cause/resolution. Any idea?
>
> note: the lwip stack is running in a single-threaded environment (no OS)
The normal reason for this is that there are two threads
I checked but no interrupts are used.
I have reshuffled the client code to follow the lwip callback sequence and
the issue seems to have dissapeared. Previously, lwip callbacks were used
to set flags that were acted upon in a highler level application
state-machine. It seemed some race condition
