This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC3220SF: SL_WLAN_DISCONNECT_ASSOC_TIMEOUT

Part Number: CC3220SF

Hi,

We deployed our battery-operated devices using CC3220SF on the customer site. Our devices connect to their network using WPA2_PSK. We verified the SSID and password are correct.

we are seeing SL_WLAN_DISCONNECT_ASSOC_TIMEOUT just before connecting to an AP. This is observed most of the time while connecting to AP.   

Most of the time our device is in hibernate mode. Every 12 seconds our device comes active and beacon. Each time our device beacons, it will come out of hibernation mode -> connect to AP -> sends its payload -> Disconnects from AP -> and go back to hibernate mode. 

This behavior is not on a single device, it is occurring on multiple devices. 

This association timeout is drastically increasing the time which CC3220SF is in active mode and also affecting the battery life of our devices. 

Note: Our customers are using Meraki MR36 APs.

My questions:

1. What is causing the SL_WLAN_DISCONNECT_ASSOC_TIMEOUT  to happen, then after some time it automatically connects? why can't the device connect the first time.

2. Is there something on CC3220SF that I can do to prevent it?

Thank you,

Kishore.

  • Hi Kishore,

    1. The issue could be due to certificate handling. Have you made sure to follow the steps for a valid certificate chain using our Certificate Handling guide? The other thing that comes to mind is a delay in the AP's response to the CC3220SF. 

    2. Before I recommend a solution, sniffer logs would be very helpful to debug this issue. Can you capture sniffer logs here?

    Thanks,
    Jacob