I'm using NDK 2.0 on a C6455 application. Our application was based off the "hello world" example included with the NDK. For the most part, the NDK works fine for our application. But occassionally it gets in a state where it does not accept requests to open a TCP socket. In this situation the NDK (acting as the server) responds to the SYN (open request from client) with a RST (reset). Repeated SYNs from the client just get more RSTs from the NDK. After several minutes of retries, or after rebooting our server, the SYN will finally be accepted with a SYN-ACK and the socket will be opened successfully.
It seems like this reset condition occurs if we try to open the socket too soon after powering the server up or too soon after connecting the Ethernet cable. If we wait a few seconds before attempting to open the socket then the open is accepted immediately.
Any suggestions on what causes these resets or how to avoid them would be appreciated.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.