It appears that there has been a disassociation between STA and AP. WICED_NOTUP means that netif_is_up() does not have NETIF_FLAG_UP flag. Do you have wireshark logs to share? We can check if there is any disassociation or roaming.
Thats just the thing though, UDP transmits were working in the background (NTP, DNS hostname lookup, UDP debug broadcasts) but the TCP socket was returning NOTUP.
We have never seen this or able to reproduce this issue. Perhaps if you could share a portion of your code where you could see the issue. What happens if you run wiced_wifi_up() after seeing the WICED_NOTUP error?
Has anyone seen this? I am guessing something has happened to the socket variable being passed into wiced_tcp_receive, which provides an invalid interface to WICED_LINK_CHECK_TCP_SOCKET, but is odd that it cannot recover on following connect attempts.
LWIP + FreeRTOS
The same error code 9 for unknown reason and not able to connect anymore.
Not sure calling wiced_wifi_up will do anything...
Other network connections are good: DNS/DHCP/SNTP/other UDP sockets and also 1 other TCP/TLS connection. This occurs on a single TCP/TLS socket. The said TCP socket is working correctly until it disconnects and following connects fail with socket error code 9.
I was thinking it could be variable states being overwritten for the socket data structre but if AxLi_1746341 has seen it too, then that removes out application code as a culprit.
My only work around at this time is to perform a SW reset when i encounter the error 9.