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.

CC3235SF: AP disconnected on Error: 109, 202 and 203 is received quite frequently while connected to an AP.

Part Number: CC3235SF

Hi,

I have a client's device which is frequently disconnecting from the AP it was provisioned with. The device frequently disconnects from the AP it is connected to with the error 109, 202 and 203.

It does manage to make a connection in one out of 10 tries but then disconnects immediately with the error 109. And after this the Disconnect Callback is called periodically with the Error 202 or 203. I am not able to understand what exactly is causing this issue. 

Could you also explain what the above mentioned errors mean? and how I can tackle this situation.

Regards,

Darpan.

  • Hi Darpan,

    You can find the WLAN disconnect reason codes in source/ti/drivers/net/wifi/wlan.h. 109 is ROAMING_TRIGGER_BSS_LOSS, 202 is AUTH_TIMEOUT, and 203 is ASSOC_TIMEOUT.

    What is servicepack version? Is the environment very noisy? Is the issue only occurring with one AP?

    Best regards,

    Sarah

  • Hi Sarah,

    Thank you for the definitions, could you also let me know what they mean and in what situations they arise in?

    The service pack running is sp_4.8.0.8_3.7.0.1_3.1.0.26.bin.

    I am not sure about the environment, I will find out more from my client and revert back. 

    As of now, this is the only device that is behaving in this particular way. Hence I guess it is only with this router. 

    Can a noisy environment cause this frequent disconnection? Reason being if the device has already managed to secure a connection with the AP can it get disconnected because of the noise in the band?

    Regards,

    Darpan.

  • Hi Darpan,

    ROAMING_TRIGGER_BSS_LOSS typically means that the device is out of range or has otherwise lost signal strength. AUTH_TIMEOUT and ASSOC_TIMEOUT refer to timeouts for the authentication and association requests during reconnection attempts.

    If the environment is noisy, the AP may not be responding to our device in a timely manner. I suggest getting a sniffer capture, plus the MAC addresses of the CC3235 device and the AP.

    Best regards,

    Sarah

  • Hi Sarah,

    This device is with one of my clients who is overseas and is not able to capture sniffer logs between the device and AP. Is there another way we can investigate this situation? 

    I was able to get a reply to my clients environment in which this device is setup, it is as follows:

    Connected to TP-Link Deco X60 Mesh system 

    2.4Ghz & 5Ghz both active but device is connected to the 2.4Ghz freq.

    There are no BLE devices in the approximate vicinity.  The Harmony Hub (20 ft. away) operates on BLE and of course our cell phones.  

    I don’t have another router in use nor do I have another one to try.

    Regards,

    Darpan.

  • Hi Darpan,

    You can use the scan policy and sl_WlanGetExtNetworkList to log the BSSIDs and RSSI of APs in range and see if the BSS loss error makes sense. Is roaming enabled?

    How far away is the device from the nearest TP-Link AP?

    Best regards,

    Sarah