• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 40 subscribers
  • Views 239 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.

CC3220MOD: CC3220MODSF SSID not scanned in the PC/Mobile

Naveen K1
Intellectual 850 points
Part Number: CC3220MOD

Hi,

We are using CC3220MODSF12MOBR from many years for our different products, all working fine and we never noticed this issue.

But now, we found this issue for two boards. One board is in customer site and second board is with us only, we kept second board for inhouse Testing/Development.

Initially boards are working fine for 1-2month, suddenly this issue was found.

Once power up the board, Device bootup with the default sate as a AP mode and we are expecting SSID (defined by manufacturer) in our PC or mobile scanner, but PC/Mobile scanner not showing the default SSID.

Note* Other boards are working fine with same scenario/Firmware with same PC/Mobile. So no issue with PC/Mobile/Firmware.

Even we replaced the Antenna with connector from working board, but issue not solved. PCB Tracks is fine with continuity test.

Kindly advise, what is the issue and how we can troubleshoot. Kindly help us we are planning for new production and need to fix this issue.

Thanks and regards,

Naveen K

  • 0
    Guru 73215 points

    Hi,

    Is your hardware able connect to WLAN at Client mode? How looks RSSI? If not, it is likely a hardware issue (e.g. soldering joint crack under module). Maybe you can check soldering of your module at x-ray.

    Jan

  • 0 in reply to Jan D
    Intellectual 850 points

    Hi Jan,

    Thank you for the information and appreciate your fast response.

    Yes, We tried with both AP mode and Station mode (to connect router) (We hope Station mode and Client mode are same), but connecting.

    We found the RSSI information from Network Terminal, please find the attachment. 

    1. If Client mode is different than station mode, kindly advice how to connect?

    2. If attached file not right one/not-helpful, kindly advice how to get RSSI.

    3. If soldering issue mean, only RF antenna pin solder got crack or dry soldered ?

    radiotool.txt 
    user:<27>7radiotool<\r>
<\n><\r>
<\n><\r>
<9>------------------------------------------------<\n><\r>
<9>             RadioTool Option Menu        <\n><\r>
<9>------------------------------------------------<\n><\r>
    1. |            Rx task options.            |<\n><\r>
    2. |            Tx task options.            |<\n><\r>
    3. |            Exit radio tool.            |<\n><\r>
<9>------------------------------------------------<\n><\r>
radiotool@CC32xx:<27>71<\r>
<27>[2J<\r>
<\n><\r>
<9>------------------------------------------------<\n><\r>
<9>             RX Task Option Menu        <\n><\r>
<9>------------------------------------------------<\n><\r>
<\n><\r>
<9>Choose Rx channel: 2.4Ghz-[1,13] 5Ghz-[36,165]<\n><\r>
<\n><\r>
radiotool@CC32xx:<27>75<\r>
<\n><\r>
<9>Enter Rx duration (in mSec units): [1,UINT32_MAX]<\n><\r>
<\n><\r>
radiotool@CC32xx:<27>75<\r>
<\n><\r>
<9>Show Rx statistics?: <\n><\r>
<\n><\r>
<9>1. Yes <\n><\r>
<\n><\r>
<9>2. No <\n><\r>
<\n><\r>
radiotool@CC32xx:<27>71<\r>
<\n><\r>
[Transceiver Mode] : Ready to start RX, press any key to start...<\n><\r>
<\n><\r>
<\n><\r>
[Transceiver Mode] : Open Receiver on channel 5, for ~ 5 mSec period...<\n><\r>
<\n><\r>
[Transceiver Mode] : Rx complete.<\n><\r>
<\r>
<\n>*********************************Rx Statistics**********************************<\r>
<\n>Received Packets: 8 <\r>
<\n>Average RSSI for management: -69 Average RSSI for other packets: -69<\r>
<\n><\r>
<\n>    -----------------------   RSSI Histogram   -----------------------<\r>
<\n><\r>
<\n>-40dBm to -87dBm (below and above RSSI will appear in the first and last cells]<\r>
<\n><\r>
<\n>           10   20   30   40   50   60   70   80   90   100<\r>
<\n>         |----+----+----+----+----+----+----+----+----+----|<\r>
<\n>>-40dBm                                                    (0.0%)<\r>
<\n>         |----+----+----+----+----+----+----+----+----+----|<\r>
<\n>  -49dBm                                                  (0.0%)<\r>
<\n>         |----+----+----+----+----+----+----+----+----+----|<\r>
<\n>  -58dBm                                                  (0.0%)<\r>
<\n>         |----+----+----+----+----+----+----+----+----+----|<\r>
<\n>  -68dBm**************************************************(100.0%)<\r>
<\n>         |----+----+----+----+----+----+----+----+----+----|<\r>
<\n>  -77dBm                                                  (0.0%)<\r>
<\n>         |----+----+----+----+----+----+----+----+----+----|<\r>
<\n><-87dBm                                                  (0.0%)<\r>
<\n>         |----+----+----+----+----+----+----+----+----+----|<\r>
<\n>              10   20   30   40   50   60   70   80   90   100<\r>
<\n><\r>
<\n>    -----------------------   Rate Histogram   -----------------------<\r>
<\n><\r>
<\n>           10   20   30   40   50   60   70   80   90   100<\r>
<\n>         |----+----+----+----+----+----+----+----+----+----|<\r>
<\n>0          **************************************************(100.0%)<\r>
<\n>         |----+----+----+----+----+----+----+----+----+----|<\r>
<\n>1                                                            (0.0%)<\r>
<\n>         |----+----+----+----+----+----+----+----+----+----|<\r>
<\n>2                                                            (0.0%)<\r>
<\n>         |----+----+----+----+----+----+----+----+----+----|<\r>
<\n>3                                                            (0.0%)<\r>
<\n>         |----+----+----+----+----+----+----+----+----+----|<\r>
<\n>4                                                            (0.0%)<\r>
<\n>         |----+----+----+----+----+----+----+----+----+----|<\r>
<\n>5                                                            (0.0%)<\r>
<\n>         |----+----+----+----+----+----+----+----+----+----|<\r>
<\n>6                                                            (0.0%)<\r>
<\n>         |----+----+----+----+----+----+----+----+----+----|<\r>
<\n>7                                                            (0.0%)<\r>
<\n>         |----+----+----+----+----+----+----+----+----+----|<\r>
<\n>8                                                            (0.0%)<\r>
<\n>         |----+----+----+----+----+----+----+----+----+----|<\r>
<\n>9                                                            (0.0%)<\r>
<\n>         |----+----+----+----+----+----+----+----+----+----|<\r>
<\n>10                                                           (0.0%)<\r>
<\n>         |----+----+----+----+----+----+----+----+----+----|<\r>
<\n>11                                                           (0.0%)<\r>
<\n>         |----+----+----+----+----+----+----+----+----+----|<\r>
<\n>12                                                           (0.0%)<\r>
<\n>         |----+----+----+----+----+----+----+----+----+----|<\r>
<\n>13                                                           (0.0%)<\r>
<\n>         |----+----+----+----+----+----+----+----+----+----|<\r>
<\n>14                                                           (0.0%)<\r>
<\n>         |----+----+----+----+----+----+----+----+----+----|<\r>
<\n>15                                                           (0.0%)<\r>
<\n>         |----+----+----+----+----+----+----+----+----+----|<\r>
<\n>16                                                           (0.0%)<\r>
<\n>         |----+----+----+----+----+----+----+----+----+----|<\r>
<\n>17                                                           (0.0%)<\r>
<\n>         |----+----+----+----+----+----+----+----+----+----|<\r>
<\n>18                                                           (0.0%)<\r>
<\n>         |----+----+----+----+----+----+----+----+----+----|<\r>
<\n>19                                                           (0.0%)<\r>
<\n>         |----+----+----+----+----+----+----+----+----+----|<\r>
<\n>              10   20   30   40   50   60   70   80   90   100<\r>
<\n><\r>
<\n>                     The data was sampled during 17mSec<\r>
<\n>*******************************End Rx Statistics********************************<\n><\r>
[Transceiver Mode] : Press any key to continue...<\n><\r>
<\n><\r>
<\n><\r>
<9>------------------------------------------------<\n><\r>
<9>             RadioTool Option Menu        <\n><\r>
<9>------------------------------------------------<\n><\r>
    1. |            Rx task options.            |<\n><\r>
    2. |            Tx task options.            |<\n><\r>
    3. |            Exit radio tool.            |<\n><\r>
<9>------------------------------------------------<\n><\r>
radiotool@CC32xx:<27>7

    Thanks and regards,

    Naveen K

  • 0 in reply to Naveen K1
    Guru 73215 points

    Hi Naveen,

    By client mode I mean station mode. Easy way how to read RSSI when you are connected into WLAN at station mode is usage of API. You can call this API at interval let say 10sec to capture RSSI. RSSI from access point side (your infrastructure access point) may to be useful as well.

    int rssi;
SlWlanGetRxStatResponse_t rssiRxStat;

// read RSSI by sl_ API
if (sl_WlanRxStatGet(&rssiRxStat, 0) == 0) {
  if (rssiRxStat.AvarageMgMntRssi != 0) {
    // save RSSI
    rssi = rssiRxStat.AvarageMgMntRssi;
  }
} else {
  // error
  rssi = -99;
}

    Wrong solder joint at antenna pin may to explain poor RF performance. But I think some issue at power and GND pins may to cause RF performance issue as well. If you have spectrum analyser, you can try to measure RF output power by conductive measurement.

    Jan

  • 0 in reply to Jan D
    Intellectual 850 points

    Hi Jan,

    Thank you for your support.

    As suggested by you, Please find the attached RSSI file in AP mode. Kindly advice on this.

    We unable to enter into station mode from AP mode, because we unable to configure the wi-fi right.

    We don't have spectrum analyser, we are thinking how to find the source of issue. We are doing machine assembly with our repetitive assembly partner. We don't know, how this soldering issue happens.

    Could you please advice is there any other possibilities which causing this issue? 

    output_2021-12-27_16-49-41.log 
    GEN:Log UART Initialize successfully 
GEN:reset cause reason is 		 = PRCM_POWER_ON 0
GEN:Timer 1 initialization done successfully
GEN:GPIO Core driver initialization done
GEN:watch dog timer initialization done
GEN:SPI driver initialization done successfully
GEN:Initializing the network socket layer task
GEN:network socket layer task initialization done with priority 9
GEN:main application task initialization done with priority 	8
GEN:Initializing the main application thread
GEN:network thread has been initialized with priority   = 6
GEN:PMS thread has been initialized with priority     = 5
GEN:MODBUS thread has been initialized with priority     = 4
GEN:OTA TASK Thread task initialization done with priority 	1
GEN:initAppVariables() Initialization Done
GEN:-----------------------------
GEN:COMPANY NAME              = WIMERA SYSTEMS PVT LTD BENGALURU
GEN:PROJECT NAME              = ReMon-WIFI On-Premises 
GEN:framework installed date  = 16:45:14 Dec 27 2021 
GEN:current framework version = 01.01.00 
GEN:current framework build v = 01.01.00.00.00 
GEN:-----------------------------
GEN:waiting for the PMS thread sync up
GEN:waiting for the MODBUS thread sync up
GEN:waiting for the OTA thread sync up
GEN:[NETAPP EVENT] IP set to: IPv4 = 10.123.45.1 , Gateway = 10.123.45.1
GEN:Device started as STATION
GEN:CHIP 822083609
 MAC  31.2.0.0.0
 PHY  2.2.0.7
 NWP  3.16.0.1
 ROM  0
 HOST 3.0.1.65
GEN:MSD DEVICE MAC address:         4C:24:98:43:93:E2
GEN:Connection Policy is already set to AUTO + FAST
GEN:Index:0, No Profile Stored
GEN:Index:1, No Profile Stored
GEN:Index:2, No Profile Stored
GEN:Index:3, No Profile Stored
GEN:Index:4, No Profile Stored
GEN:Index:5, No Profile Stored
GEN:Index:6, No Profile Stored
GEN:starting Provisioning since there are No Profiles stored
GEN:[NETAPP EVENT] IP set to: IPv4 = 10.123.45.1 , Gateway = 10.123.45.1
GEN:CHIP 822083609
 MAC  31.2.0.0.0
 PHY  2.2.0.7
 NWP  3.16.0.1
 ROM  0
 HOST 3.0.1.65
GEN:MSD DEVICE MAC address:         4C:24:98:43:93:E2
GEN:[NETAPP EVENT] IP set to: IPv4 = 10.123.45.1 , Gateway = 10.123.45.1
GEN:WIFI device has been started in the default state
GEN:RSSI strength value -99
GEN:please send connection profiles from browser!!
GEN:RSSI strength value -93
GEN:please send connection profiles from browser!!
GEN:RSSI strength value -88
GEN:please send connection profiles from browser!!
GEN:RSSI strength value -82
GEN:please send connection profiles from browser!!
GEN:RSSI strength value -88
GEN:please send connection profiles from browser!!
GEN:RSSI strength value -99
GEN:please send connection profiles from browser!!
GEN:RSSI strength value -99
GEN:please send connection profiles from browser!!
GEN:RSSI strength value -99
GEN:please send connection profiles from browser!!
GEN:RSSI strength value -72
GEN:please send connection profiles from browser!!
GEN:RSSI strength value -90
GEN:please send connection profiles from browser!!
GEN:RSSI strength value -99
GEN:please send connection profiles from browser!!
GEN:RSSI strength value -99
GEN:please send connection profiles from browser!!
GEN:RSSI strength value -92
GEN:please send connection profiles from browser!!
GEN:RSSI strength value -69
GEN:please send connection profiles from browser!!
GEN:RSSI strength value -99
GEN:please send connection profiles from browser!!
GEN:RSSI strength value -66
GEN:please send connection profiles from browser!!
GEN:RSSI strength value -99
GEN:please send connection profiles from browser!!
GEN:RSSI strength value -99
GEN:please send connection profiles from browser!!

    Thanks an regards,

    Naveen k

  • 0 in reply to Naveen K1
    Guru 73215 points

    Hi Naveen,

    Reading RSSI at AP mode by sl_WlanRxStatGet() is not helpful. Why you not save connection profile manually from code by sl_ APIs? This should be relatively easy change at code.

    According description at your first post it looks like hardware issue. Most likely manufacturing issue of your hardware. But if you want, you can check following software things:

    • how is set TX power
    • how is set country code and AP mode channel (e.g. you cannot have set channel 13 for US country code)
    • it seems you are using slightly outdated ServicePack, you may to update to latest version
    • check if error code is not returned from sl_Start() API
    • you may to capture NWP log (SWRU455 chapter 20) and log by WLAN sniffer

    But I think crucial first step is determine is your hardware is able generate proper output RF power. Easy way is to use conductive measurement using spectrum analyser. There are some other ways how quantify RF power but it will require deep knowledge of RF measurement. If you found issue with RF TX power, you should check assembly of your board at 3d x-ray.

    I think it will be hard to move forward without knowledge whether RF output works. Maybe you can check your power rail at oscilloscope for unexpected power outages and carefully visually inspect antenna path under microscope.

    Jan

  • 0 in reply to Jan D
    Intellectual 850 points

    Hi Jan,

    Thank you for your advice.

    We tried with "save connection profile manually from code by sl_ APIs in issue board", but not connecting with issue board. But we also tried this code with other working board, it's working and it's connected.

    • how is set TX power: Maximum.
    • how is set country code and AP mode channel (e.g. you cannot have set channel 13 for US country code):  AP Mode Channel: 1; Country code: EU.
    • it seems you are using slightly outdated ServicePack, you may to update to latest version; New Version updated.
    • check if error code is not returned from sl_Start() API; No errors coming from SI_Start() API.
    • you may to capture NWP log (SWRU455 chapter 20) and log by WLAN sniffer; Can we use Module pin no. 46-GPIO1-TX1?

    1. You are correct, issues with Hardware side only, because same firmware code working with other boards. but not working in issue boards. So, no need to do root cause testing in Software right? We need to concentrate only on hardware, right?

    2. Only way is to test the RF output power and do X-Ray right?

        We need to find the exact source of issue, we will do spectrum analyser measurement and X-Ray.

    3. What will be the acceptable RF Output power range?

    4. X-ray will also tells poor soldering joint? We thought, it will only helps to find the short.

    Thanks and regards,

    Naveen K

  • +1 in reply to Naveen K1
    Guru 73215 points

    Hi,

    Alternate pins for NWP log at CC3220 are following. But I think capturing NWP log will not be much helpful because it looks like a hardware issue definitely.

    MAP_PinTypeUART(PIN_53, PIN_MODE_5);//GPIO30
MAP_PinTypeUART(PIN_18, PIN_MODE_3);//GPIO28
MAP_PinTypeUART(PIN_60, PIN_MODE_3);//GPIO5
MAP_PinTypeUART(PIN_62, PIN_MODE_1);//GPIO7

    At hardware side may to be wrong two things:

    • your board or assembling of module at your board
    • module itself (e.g. module can be damaged by wrong temperature profile during re-flow or just somehow damaged)

    There is many ways how to test RF output of WiFi device but simplest and cheapest way is to use conductive measurement by spectrum analyser. Other ways will require much more expensive measurement equipment or knowledge of RF testing. Best way regardless is used conductive or radiated measurement is to use radio tools application and compare your good with bad board. Other way may to be implementation of radio testing code into your own firmware.

    Using X-Ray at modules like CC3220MOD may to be slightly tricky. With good 3d x-ray machine you can focus beams to different layers and this allow to identify shorts or poor joints. Soldering of module can be partially checked by the BGA inspection cam as well.

    Usage of X-Ray is a non destructive way. Other way may to be destructive like removing shielding of module and investigating if something wrong is inside module (e.g. RF output filter). But with destructive way it may happen that you lost trace or damage your module...

    Jan

  • 0 in reply to Jan D
    Intellectual 850 points

    Hi Jan,

    Thank you for your support.

    Once we done with X-Ray and RF measure by Spectrum Analyzer, we will update on this post.

    Thanks and regards,

    Naveen K

  • 0 in reply to Naveen K1
    Guru 73215 points

    Hi Naveen,

    OK. Just I want to note, there is opened very similar issue at this thread. Please check there thread. If you think that is exact same issue it may to signalise some problem with module itself.

    Jan