Using "Select" for non-blocking socket read with select timeout of 10 sec
I have many wireshark captures that show the problem - I'm trying to figure out root cause.
Downloading a 10 meg file from a web site.
50% of the time all goes well.
The other 50% - (based on my debug printf messages and wireshark) that the LWIP stack has stopped processing received packets.
The ESP goes in and out of "TCP Window FULL" and takes 90 to 200 seconds to process a packet.
I know the stack is not locked because I get select timeouts every 10 secs and when I fail to acquire any data from the stack for 200 seconds I issue a close which properly generates a FIN by the ESP LWIP.
Does anyone have an insight to nature of this behavior?
I would normally attempt to trace the LWIP stack but using the RTOS SDK - I don't believe I can enable the LWIP debug messages.
I'm thinking of moving over to the new IDF - since I can have access to the actual LWIP source and debugging options. Is the IDF option viable at this time for the ESP since I see it's primarily designed for ESP32 development?
All comments welcome.
Who is online
Users browsing this forum: APARTMENTrep, Bing [Bot] and 7 guests
Newbies Start Here
Are you new to ESP8266?
Unsure what to do?
Dunno where to start?
Start right here!
We also have a RTOS version and a MESH version too!
Complete listing of the official ESP8266 related documentation release by ESPRESSIF!
Must read here!