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.

CC3100MOD: Can't connect to AP with NWP version 2.12 and 2.13

Part Number: CC3100MOD
Other Parts Discussed in Thread: CC3100, CC3100SDK, UNIFLASH

Hi team,

I have posted a question about CC3100MOD failed to connect to a certain AP with newest service pack. Now the customer has captured the NWP log, would you please help analyze the log? Thanks. 

Issue description: CC3100MOD cannot connect to Huawei AP8150D after updating the service pack to NWP version 2.12 or 2.13. Older service pack has no problem, and testing with another AP model is also normal.

From AP's log, we can find a "Deauth because STA is leaving or has left BSS(3)" error.

Please find the NWP log under NWP 2.12 and 2.5 as below, also there is a log from the AP side for reference.

Log with NWP version 2.13 (cannot connect to AP):

AP8150D-ServicePack2.13.log
Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2021.03.18 09:13:04 =~=~=~=~=~=~=~=~=~=~=~=
71�T··��·(·······Z`8 ··\�··;
v"
w"····
x"··
y"·
�"
�"
�"
c"'
�!bc·�!�····
�!([·�!(�[W·"�A·A·
·d·��·····>·········
····
··'(·#B#72�`···
··-�·-1··{··@ �··� �··
·
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Log with NWP version 2.5 (can connect normally):

AP8150D-ServicePack2.5.log
Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2021.03.18 09:36:16 =~=~=~=~=~=~=~=~=~=~=~=
···
··6·"···) "··) �-T! �··�www.ti.c·6· ···) ·*{··d��··*{··d��···.$DTCC.·····.···(·*{··d��··
· ·
· ·*{··d��··*{··d��··*{··d��··*{··d��··*{··d��··*{··d��· *{··d��·
*{··d��··
· ·
· ·*{··d��··
··-�·-1··{··@ �··� �··
·
·-�·-1··{··@
·····@····Q·
·
·*�··
·
··
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Log from Huawei AP8150D:

session-AP8150D-0317.log

Best regards,

Shuyang

  • Hi Shuyang,

    I am reaching out to our SW team to comment.

  • Hi Shuyang,

    Thank you for the logs. I will review them and provide you an update by the beginning of next week.

    Best regards,

    Sarah

  • Hi Sarah,

    Any update for the review? Thanks!

    BR,

    Shuyang

  • Hi Shuyang,

    Unfortunately not yet. I will be able to review them and respond tomorrow.

    Best regards,

    Sarah

  • Hi Shuyang,

    In the logs, I am seeing association timeouts, but I'm not sure of the cause yet. Can your customer collect sniffer captures?

    I also want to verify which servicepack versions have been tested. In your previous thread, you stated the customer sees this issue on versions 2.11, 2.12, and 2.13. Has 2.10 been tested? I'm asking because there was a major update for the KRACK attack fixes in the 2.10 servicepack.

    Best regards,

    Sarah

  • Hi Sarah,

    Thanks for reply. I will ask the customer to provide the sniffer log, but it may take a few days.

    As for the servicepack versions, they have tested all versions from 2.5 to 2.13, the result is all servicepacks before 2.12 can work, but 2.12 and 2.13 cannot. So I'm afraid the change you mentioned is not the cuase. However we can follow the thoughts: what changes are made since 2.12 could be the possible cause of this?

    Thanks!

    BR,

    Shuyang

  • Hi Shuynag,

    There were many fixes in the 2.12 servicepack, but I do not see anything obvious in the release notes. We will have to check the handshake between the device and the AP in the sniffer log.

    Best regards,

    Sarah

  • Hi Sarah,

    Please find the sniffer log between CC3100MOD and AP as attached. The NWP version is 2.12.

    Please use nodes Huawei:BF:85:C0 (DC:21:E2:BF:85:C0) and TexasInst:49:05:50 (E4:15:F6:49:05:50) as the filter to find the packets between CC3100MOD and AP.

    Thanks!

    Shuyang

    Capture_CC3100MOD_Connection_Fail_Servicepack_2_12.pkt

  • Hi Shuyang,

    Thank you for the capture. I will review and get back to you in 1-2 days.

    Best regards,

    Sarah

  • Hi Shuyang,

    I'm never seeing the Huawei AP send an association response to our device:

    Can you get a sniffer capture of when the CC3100 is able to connect to this AP?

    Best regards,

    Sarah

  • Hi Sarah,

    Please find another sniffer log with the same AP and 20 CC3100MODs, you can find the Assoc Rsp at line 45018, please check out if this is what you need, thanks.

    https://tidrive.itg.ti.com/a/Lt0-CbPdPhY83T4R/3b7e5886-5836-4f25-9a9f-11591e0d9339?l

    BR,

    Shuyang

  • Hi Shuyang,

    Thank for you for log. This does show some successful connections, and I will compare the behavior to the previous log. Please note that this week is shortened due to holidays, so I may respond next on Monday.

    Best regards,

    Sarah

  • Hi Sarah,

    Could you help analyze it as soon as possible? This problem has been delayed for a long time.And this problem is very important to our project schedule.If you still need other data to analyze it, please feel free to contact me,

    thanks. 

    Best regards

    Wuxiang

  • Hi Wuxiang,

    This is a very long log, and I will have to compare the timing and the contents of the connection handshakes to determine how they are different from the first log. All of this information is part of the sniffer logs, so you are welcome to analyze it yourself and let me know your findings. Unfortunately, I am unable to get to this today and Friday is a holiday.

    Best regards,

    Sarah

  • Hi Shuyang, Wuxiang,

    I've looked through the logs and tried to follow 5+ MAC addresses through the connection process, but I only see devices that are already connected at the beginning of the log, or ones that make it partially through the connection process (like completing 1 message out of 4).

    Can you get a sniffer capture of one device that you know is successfully connecting and able to send data? It will also help to see a similar environment to the first capture.

    Best regards,

    Sarah

  • Hi Sarah,

    Thanks for your replys.

    Can you determine a time,I hope I can communicate with you online so much for an hour or more provide anything for you,to help you analysis what i can provide,Thanks.

    Best regard,

    Wuxiang

  • Hi Sarah,

    Please find the log as you requested below. I am uploading this on behalf of Wuxiang because he had some trouble uploding the file.

    CC3100MOD's MAC: 5C:F8:21:CB:B9:D0

    AP's MAC: DC:21:E2:BF:85:C0

    Capture-ServicePack2.11_ConnectAndSendData.pkt

  • Hi,Sarah,

    I found the difference between the 2.11 and 2.13 versions is Assoc Req,but the information in it i can‘t understand.I hope it can be reference to you.

    thanks,

    Wuxiang.

  • Hi Wuxiang, Shuyang,

    The Huawei AP is not sending an association response back to the CC3100. Since the contents of the association request look similar, I am not sure why the AP would be behaving differently. I am reaching out to another member of my team for more help. I will update you as soon as we learn more, but it may be another couple days.

    Best regards,

    Sarah

  • Hi Wuxiang,

    What host driver version are you using (defined in the simplelink.h file)? Are you using sl_WlanSetMode() to change any of the configuration options?

    Best regards,

    Sarah

  • On behalf of Wuxiang:

    --

    1. The following  is the content of file simplelink.h:  (c:\ti\CC3100SDK_1.3.0\cc3100-sdk\simplelink\include\simplelink.h)

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    /*****************************************************************************/
    /* Macro declarations for Host Driver version */
    /*****************************************************************************/
    #define SL_DRIVER_VERSION "1.0.1.11"
    #define SL_MAJOR_VERSION_NUM 1L
    #define SL_MINOR_VERSION_NUM 0L
    #define SL_VERSION_NUM 1L
    #define SL_SUB_VERSION_NUM 11L
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    --

    2. The following is the ONLY place the host promgram call  sl_WlanSetMode() function, just when system is in initialization stage and find the CC3100 device is not in station-mode,

    Fullscreen
    1
    2
    retVal = sl_WlanSetMode(ROLE_STA);
    ASSERT_ON_ERROR(retVal);
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    --

    3. Also these are the functions that the host program calls when doing initialization: 

    Fullscreen
    1
    2
    3
    4
    5
    6
    retVal = sl_WlanPolicySet(SL_POLICY_CONNECTION, SL_CONNECTION_POLICY(1, 0, 0, 0, 1), NULL, 0);
    power = 0;
    retVal = sl_WlanSet(SL_WLAN_CFG_GENERAL_PARAM_ID, WLAN_GENERAL_PARAM_OPT_STA_TX_POWER, 1, (_u8 *)&power);
    retVal = sl_WlanPolicySet(SL_POLICY_PM , SL_LOW_LATENCY_POLICY, NULL, 0); // SL_LOW_LATENCY_POLICY // SL_NORMAL_POLICY // SL_ALWAYS_ON_POLICY
    retVal = sl_WlanSet(SL_WLAN_CFG_GENERAL_PARAM_ID, WLAN_GENERAL_PARAM_OPT_COUNTRY_CODE, 2,(unsigned char *)"EU");
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    --

    BR,

    Shuyang

  • Hi Shuyang,

    My mistake, I meant to ask about sl_WlanSet() instead of sl_WlanSetMode(). Can you double check sl_WlanSet() is not being called anywhere else?

    Best regards,

    Sarah

  • Hi Sarah,

         I found another difference thing of the 2.13 and 2.11 is the Assoc Req packet length(2.13 Packet length is 109,and 2.11 is 118).Form the AP8150D log,we think this may be the reason why AP did not reply to Assoc Rsp.In terms of supported rates, the 2.13 version is a few bytes less than the 2.11 version.I want to know what the reason is, and I hope it will be helpful to you.

    Best regards,

    Wuxiang

  • Hi Wuxiang,

    Yes, that is correct. That is why I am asking about the use of sl_WlanSet(). We are trying to figure out why that is changing between versions.

    Additionally, can you flash a clean image using UniFlash with servicepack 2.13 and capture NWP logs showing the entire first boot and connection attempt?

    Best regards,

    Sarah

  • Hi Sarah,

    As listed in my last repost, the use of sl_WlanSet() is as below:

    retVal = sl_WlanPolicySet(SL_POLICY_CONNECTION, SL_CONNECTION_POLICY(1, 0, 0, 0, 1), NULL, 0);

    power = 0;
    retVal = sl_WlanSet(SL_WLAN_CFG_GENERAL_PARAM_ID, WLAN_GENERAL_PARAM_OPT_STA_TX_POWER, 1, (_u8 *)&power);
    retVal = sl_WlanPolicySet(SL_POLICY_PM , SL_LOW_LATENCY_POLICY, NULL, 0); // SL_LOW_LATENCY_POLICY // SL_NORMAL_POLICY // SL_ALWAYS_ON_POLICY
    retVal = sl_WlanSet(SL_WLAN_CFG_GENERAL_PARAM_ID, WLAN_GENERAL_PARAM_OPT_COUNTRY_CODE, 2,(unsigned char *)"EU");

    BR,

    Shuyang

  • Thanks Shuyang.

    Can you flash a clean image with servicepack 2.13 and capture NWP logs? We want to see the entire first boot and connection attempt.

    Best regards,

    Sarah

  • Hi Sarah,

    The customer has done some more tests with different CC3100MODs, and there is a new finding:

    The modules which cannot connect to the AP do not have the Extended Supported Rates in the association request, and the modules which have the Extended Supported Rates can connect to the AP successfully. It is most likely the root cause for this issue.

    To rule out the impact of hardware and test environment, the customer did the above tests on a same PCB board with 2 different CC3100MODs. It appears that the issue follows the modules. So could you please verify if the supported rates can vary by different batches of CC3100MODs? 

    Best regards,

    Shuyang

  • Hi Shuyang,

    I understand. Can you please flash a clean image with servicepack 2.13 and capture NWP logs that show the entire first boot? This will help us get to the bottom of this issue. We need these logs from the first boot to continue debugging the supported rates.

    Were both of these modules flashed with the same servicepack version?

    Best regards,

    Sarah

  • Hi Sarah,

    Please find the NWP log for the first boot as requested.

    20210415.zip

    The AP manufacturer helped analyze the sniffer log, and found that when connection failed, CC3100MOD claimed the support of HT, but with MCS set = 0. In the normal log, the MCS set is 0xFF:

    And the CC3100 will enter SimpleLinkGeneralEventHandler() when connection failed.

  • Hi Shuyang,

    Sarah is out today, but she will be back soon and will follow-up with you on this issue shortly.

    Best,

    Ben M

  • Hi,Ben M

    What's the progress on this issue?

    Best regards,

    Wuxiang

  • Hi Wuxiang,

    Ben followed up with Shuyang offline. Did he communicate with you? I will check in with him.

    Best regards,

    Sarah

  • Hi Sarah,

    I didn't communicate with him.

    Best regards,

    Wuxiang

  • Hi Wuxiang,

    Based on latest testing, the issue seems to be resolved by formatting the serial flash before loading the image. Please sync with Shuyang offline.

    Best regards,

    Sarah

  • Hi Sarah,

    Thanks for your reply,but I don't know how it was generated, why other modules didn't, and how I should avoid it?

    Best regards,

    Wuxiang

  • Hi Sarah,

    The discussion has switched to offline, thanks for your support!

    BR,

    Shuyang