CCS/CC3220SF-LAUNCHXL: CC3220SF TCP SOCKET SL_SO_KEEPALIVETIME Fails

Hi,

You need to enable option by SL_SO_KEEPALIVE first. See: swru455 chapter 6.5.1.3.

Btw ... it is a good practice to read return code from sl_ API.

Jan

Hi Jan,

Thanks for the quick response.

TCP SOCKET SL_SO_KEEPALIVETIME Fails 

I am having an issue setting the keep alive time out for the TCP socket. The default timeout of  5mins works fine. But when I try to alter this timeout I do get return value as 0 but timeout does not occur as per the timeout value.  I am opening the socket first to obtain the socket handle and then setting the socket options by calling sl_SetSockOpt. Later I am calling sl_connect. The timeout still occurs at the default timeout setting that is 5mins.  Please find attached the source.

Hi,

I have done my own test with server socket at CC3220 and I am not able reproduce a issue. Keep Alive timeout settings worked for me fine. I set socket options to new socket after calling accept(). I tested TCP TLS server with single client socket capability because it was easier for me. I think there should not be difference between server and client socket.

See results in Wireshark:

192.168.236.8 - PC client

192.168.236.15 - CC3220SF server

Btw ... can you test settings of socket options after successful connect?

I tested with latest SDK (3_10_00_04) and ServicePack (3.11.0.6).

Jan

Hello Jan, 

I am facing this issue in CC3220SF in TCP Client Mode.

My SDK version is simplelink_cc32xx_sdk_2_30_00_05. and my service pack version is  3.9.0.6. Is this issue arising because of the Old versions?

Can you please share your steps for socket creation on the client side. My complete Socket creation function is attached below. Can you please share your views.

Thanks :)  

int32_t WS_Open_Socket(void)
{
    _u32 DestinationIP;
    if (Read_ServerDetails() < 0)
    {
        while (1)
            ;

    }
    _i16 Status = -1;
    SockID = -1;
    SockID = sl_Socket(SL_AF_INET, SL_SOCK_STREAM, 0);
    if (SockID < 0)
    {
        UART_PRINT("Could Not Open Socket %d \r\n", SockID);
        return -1;
    }
    else
        UART_PRINT("\n Opened Socket with ID : %d \r\n", SockID);

    SlSockKeepalive_t enableOption;
    enableOption.KeepaliveEnabled = 1;
    Status = sl_SetSockOpt(SockID, SL_SOL_SOCKET, SL_SO_KEEPALIVE,
                           (_u8 *) &enableOption, sizeof(enableOption));
    if (Status < 0)
    {
        UART_PRINT("\r\n Socket Issue %d", Status);
    }
    else
        UART_PRINT("\r\n Socket SL_SO_KEEPALIVE RETURN %d", Status);

    _u32 TimeOut = 30;
    Status = sl_SetSockOpt(SockID, SL_SOL_SOCKET, SL_SO_KEEPALIVETIME, ( _u8*)&TimeOut, sizeof(TimeOut));
    if (Status < 0)
    {
        UART_PRINT("\r\n Socket Issue %d", Status);
    }
    else
        UART_PRINT("\r\n Socket SL_SO_KEEPALIVETIME RETURN %d", Status);


    SlSockAddrIn_t Addr;
    Addr.sin_family = SL_AF_INET;
    Addr.sin_port = sl_Htons((uint16_t)server_Info_R.PORT);


    if (strstr(server_Info_R.DNS, "IP") == 0
            && strstr(server_Info_R.DNS, "ip") == 0)
    {
        char* loc = strstr(server_Info_R.DNS, ":");
        loc++;
        sl_NetAppDnsGetHostByName(loc, strlen(loc), &DestinationIP, SL_AF_INET);
        Addr.sin_addr.s_addr = sl_Htonl(DestinationIP);
 
    }
    else
    {
        convChrIPToInt(&server_Info_R.DNS[0] + 3);
   Addr.sin_addr.s_addr = sl_Htonl(SL_IPV4_VAL(server_Info_R.IP[0],server_Info_R.IP[1],server_Info_R.IP[2],server_Info_R.IP[3])); //TP:168,62,174,42
    }

    Status = sl_Connect(SockID, (SlSockAddr_t *) &Addr, sizeof(SlSockAddrIn_t));
    if (Status < 0)
    {
        UART_PRINT("\nCould Not connect to socket %d,status: %d\r\n", SockID,
                   Status);

        return -1;
    }
    else
        UART_PRINT("\n Connected to Socket Successfully. ");
    return 1;

}

Hi,

I am not aware about any bug related to settings of keep-alive interval settings at older SDK or servicepack versions. But I am not a TI employee and from this reason I haven't access internal bug-tracking.

I did not tested setup of keep-alive interval at client mode. For testing I used CC3220 TCP server because it was easier to set test. But I did not expect any difference. Unfortunately I can't share my code. But at first look I don't see anything fundamentally wrong inside your code. You can try following change inside your code - move sl_SetSockOpt() APIs after sl_Connect().

Can you confirm by network sniffer (e.g. Wireshart) that settings of keep-alive internal is not functional?

Jan

Hi,

Apologies for the late response.

I tried the following changes.  'You can try following change inside your code - move sl_SetSockOpt() APIs after sl_Connect().' 

But the same issue was observed in this case as well.

I also observed something new when I tried this:

'can you test settings of socket options after successful connect?'

When I try to get the settings of socket connection alive timeout, after a successful connection to the server I observed the error code -2002. Which states:

Hi,

Unfortunately I am not able do tests at client mode. I haven't enough time to create code for this test case. Maybe someone from TI support should be able do that. For this moment I haven't additional idea. Please provide Wireshark log for confirmation of issue. Do not forget set proper filter to remove unrelated packets.

Jan

Parth,

Please provide wireshark captures of the issue. I haven't had a issue on the client side with this. Can you also check what your server keep alive is?

BR,

Vince