• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 40 subscribers
  • Views 288 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

CC3220SF-LAUNCHXL: SL_WLAN_EVENT_DISCONNECT with ReasonCode 110

CC3220SF-LAUNCHXL: SL_WLAN_EVENT_DISCONNECT with ReasonCode 9

user4421125
Intellectual 450 points
Part Number: CC3220SF-LAUNCHXL
Other Parts Discussed in Thread: CC3220SF

Hello
I am trying the provisioning sample on CC3220SF - LAUNCHXL,
SL_WLAN_EVENT_DISCONNECT is raised in SimpleLinkWlanEventHandler.
Reason Code indicates "9".
I assume that this is "SL_WLAN_DISCONNECT_STA_NOT_AUTH" in wlan.h
I found it, but I do not know the meaning of this error and how to deal with it.
Which document describes this workaround?

The timing that occurs is the next step.
1. First Provising --- Success
2. Power ON Reset --- Reset Button
3.Second ...
   SimpleLinkWlanEventHandler SL_WLAN_EVENT_CONNECT
   SimpleLinkNetAppEventHandler IP Acquired
   SimpleLinkWlanEventHandler SL_WLAN_EVENT_DISCONNECT
    ([Event] STA disconnected from AP (Reason Code = 9)

I will reconnect after this, so is there no problem?CCS: Version: 8.1.0.00011

simplelink_cc32xx_sdk_2_10_00_04

Thank you.

H.Wt

  • 0
    TI__Guru 61526 points
    Hi H.Wt,

    After the Reset, do you call sl_WlanConnect (or sl_WlanProvisioning) or it is connecting based on AUTO-Connect?
    After the failure (disconnection), do you need to manually call WlanConnect or it connects automatically.

    This refers to a very basic 802.11 connection issue that shouldn't occur with the SimpleLink device (trying to associate with an Access Point before the device is authenticated).
    This looks like an issue of the specific AP you use but we need to check an air-sniffer log to verify this. Which AP are you trying to connect to?
    If you were able to connect after the first provisioning phase, I guess it is not an issue.

    Br,
    Kobi
  • 0 in reply to Kobi Leibovitch
    Intellectual 450 points
    Hello Kobi

    Thank you for your answer.

    Yes, after resetting, calling sl_WlanConnect.
    I am still using the in-house AP to test.
    I have been able to reconnect, so continue to evaluate as it is.
    I will check for an air-sniffer log.
    Thank you very much.


    H. Wt