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: SP 3.17.0.4 - any change related network scan?

Guru 79985 points
Part Number: CC3220SF

Hi Team,

Please ask R&D whether at new ServicePack (3.17.0.4) for CC3220 are any changes related to WiFi scan. At release notes for SDK 4.30.0.6 are stated "Bug Fixes" and I am not sure if there is hidden something related WiFi scan as well.

btw ... at SDK version 4.30.0.6 are missing html files with release notes for CC3x20 and CC3x35 ServicePack.

Thanks

Jan

  • Hi Jan,

    I'm not aware of specific scan-related bug fixes. I'll check and let you know if I find anything.

    Why are you asking? do you see any new issue with the latest SP?

    Thanks for notifying on the missing html file (I saw the README.md is there and it can be used until this is fixed).

    Br,

    Kobi 

  • Hi Kobi,

    We have seen during tests of our devices issue with network scan API (code with SP 3.16.0.1). Now he have updated to latest SP 3.17.0.4 but I haven't seen issue yet. But maybe I don't wait enough time. Who knows...

    When issue occurs API sl_WlanGetNetworkList() is returning SL_ERROR_WLAN_GET_NETWORK_LIST_EAGAIN and stay at this state forever. All other features of NWP works well. For recovery from the issue is NWP restart mandatory. Occurrence of issue is rare and from this reason we was not able determine what is triggering issue. But we saw very interesting thing. When device have such a issue, and you place another device next to, it dramatically increase probability of issue at the 2nd device. And this is pretty interesting.

    My algorithm around network scanning is pretty simple:

    • it is set scan interval by scan policy to 20 sec
    • my task read results by API sl_WlanGetNetworkList() at interval 20sec
    • when API sl_WlanGetNetworkList() returns SL_ERROR_WLAN_GET_NETWORK_LIST_EAGAIN I call API after 10sec instead 20sec

    Regards,

    Jan

  • There was one related fix (it was about the interface between the NWP and MAC processor: sometimes when the scan failed in the MAC level, the NWP didn't handle the event correctly and the scan failure became permanent).

    Br,

    Kobi

  • Hi Kobi,

    Thank you for a information. It looks that is could be this one.

    Jan