CC3220SF: TCP Retransmission Interval, TX_Failed (-107), Driver Aborted (-2005)

Hi,

Are you using the latest servicepack on the CC3220? You can find it as part of the SDK, at <sdk path>/tools/cc32xx_tools/servicepack-cc3x20. You can flash the servicepack following the instructions here:

https://dev.ti.com/tirex/explore/node?node=ABEoqU9o3snoxDcmIpW0EA__fc2e6sr__LATEST

Please flash the latest servicepack and try your test again if you haven't done so yet.

From where are you capturing the wireshark logs? Are you using an air sniffer or are you capturing directly from a local interface on your server? If you could provide me those logs so I can investigate further that will be appreciated.

Also, if you could provide me the NWP logs that would be appreciated. The instructions to capture the NWP logs from teh CC3220 can be found here: https://processors.wiki.ti.com/index.php/CC3120_%26_CC3220_Capture_NWP_Logs

Do note while the captured logs will be a raw binary format, there are a few steps you can do to ensure that the logs are formatted correctly:

1. The logs are collected from device startup, as in you release reset/power on the device once the logging software is already collecting data
2. Open the logs with a raw hex editor and see if within the raw binary logs you find the string “/sys/servicepack.ucf” in plaintext at some point (this signals that the device startup sequence is captured correctly)
3. Check to ensure that immediately before the string “/sys/servicepack.ucf” in the raw log from step 2, you see the bytes 0x0D 0x27 0xCA (this indicates that all raw binary is captured, and not just printable characters).

Regards,
Michael

Hi, Michael

Thanks for your reply.

I have attached the picture you requested.

This is when the server was turned off while TCP connection. 

192.168.10.1 : AP

192.168.10.2 : Station ( = CC3220SF )

TCP retransmission interval is 10ms under. and retransmission interval sent by the other party is similar.

Hi,

Thanks for showing the wireshark screenshot.

Unfortunately, I still need more information to determine what the cause of this behavior might be.

Please collect the NWP logs while performing your test as described in my previous post. Attaching the the wireshark log captures might be useful as well. I would appreciate it if you could provide me that debug data.

Regards,

Michael