Even I did a text search in the whole SDK for 36352; but not a single hit. My suggestion would be to have the debug macros enabled and check when you receive the error, is there any additional debug prints?
Also, when the socket is reopened, do you receive that packet or the packet is lost and the image transfer gets stopped?
Upon further investigation i see the errors over a larger population of our devices and in other TCP sockets/connections Many of these devices are running production code or at customer sites where serial logging is impossible so I will see what I can do to log additional information.
I also see other invalid values returned from wiced_tcp_receive
I am periodically polling the socket for received data through wiced_tcp_receive. I currently treat these unknown return values as a general error that triggers the connection to be closed. I wonder what would happen if i ignore it.
I did not see anything reported when i encountered the strange return values, in this case it was 36480.