![]() Notice that the gpfAppSocketCb DID NOT RECEIVE A MESSAGE that the other side closed the connection. On the Client app, close the socket, then the CLIENT app on the PC. Notice that the gpfAppSocketCb function will give a SOCKET_MSG_ACCEPT message (by the way, the port number is INCORRECT, compared to what the windows "TCPVIEW.EXE" tool shows) 3. Start a CLIENT app on a PC (any client app, doesn't matter), and connect to the device via the IP address and port. Start a hosted MCU app which uses the WINC1500 module, as a TCP server, accepting connections (the programming doc section 6.4.2 would be an adequate example) 2. This occurs when the device is acting as a TCP/IP server. ![]() I opened a "case" with Microchip, and I 'm not convinced the person I was communicating with even understands the issue. ![]() Then I discovered a "leak" which can be used to completely shut down the device. Hello, I have been developing for the WINC1500, hosting on another MCU, and finally got most everything working. WINC1500 Memory leak and DOS vulnerability
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |