WL1837MOD: WIFI Joining Issues

Hello,

When you say "When we changed the  Predefined SSID to a Router", what do you mean? do you mean connecting to another non-WiLink router? or do you still use WiLink device as AP?

Also:

• do you get the same when trying less stations?
• is the connection secured or OPEN? if it is secured, can you try in OPEN?
• how often does it happen?
• what devices are you using as stations?
• Do you have the option to fetch logger from the device?

Regards,

Shlomi

Hi Shlomi,

"When we changed the Predefined SSID to a Router", meant that we changed the STA to connect to a TP link Router (5 Ghz) instead of the WiLink AP SSID.

1. We also observed the issue when we had 6 Stations.

2. Connection is secured WPA2 . Not tried the  OPEN network. Will give a try.

3. In the 10 attempts of pairing trials , 2 times we see the issue.

4. We are using our custom designed STA based on Cypress chip-set CYW43907.

5. We don't have any serial interface available to take log's from Wilink. Wilink Module is interfaced with AM33x running on Linux. Kernel debug log's we can collect.

Thanks for the info.

Please give the OPEN security a try and let me know.

The logger i mentioned is described here https://www.ti.com/lit/ug/swru435a/swru435a.pdf?ts=1599466015739&ref_url=https%253A%252F%252Fwww.google.com%252F. Don't you have the relevant pin available?

it would be hard to debug without a logger.

Regards,

Shlomi

Hi Shlomi,

Tried with OPEN security , we still see the joining issue.

Regards

venkatesh

Hi Shlomi,

To add more details, We are using Wilink Module WL1837MOD in Dual Band.

1. Wilink module acts as STA using 2.4 Ghz  to Join the Another AP (Router) for internet access

2. Wilink module uses 5 Ghz  to act as AP to  allow the STA's to connect to it.

So Wilink Module used in both STA & AP modes, having 2 antenna's on the board. STA's connected to Wilink module (over 5Ghz) do not access the internet., Upon successful pairing they establish TCP , UDP connections  for the custom data exchange.

Do you see any issues having the module in both roles ??

The debug pin (WLUARTDBG) to collect the log's is available as  Mounting Hole, we need to rework on it to get the Log's which might take some time to get it ready.

Regards,

Venkatesh

Thanks for the info.

So you are working in multi-role which should be OK.

Did i understand correctly that the stations are communicating between them without going through the AP to the internet?

Logger debug is valuable here to understand more.

BTW, what firmware version are you using?

Shlomi

Also, a Wi-Fi air sniffer can shed more light if you have one.

and lastly, a good test would also be to test AP role only without the STA role and check if you still see issues (assuming as you mentioned that the stations do not go out via the STA role connected to the router).

Hi Shlomi,

Below are the Wlcore version Info:

wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
 wlcore: PHY firmware version: Rev 8.2.0.0.242
wlcore: firmware booted (Rev 8.9.0.0.79)

Yes, did tried with by disabling 2.4Ghz and only 5Ghz Enabled. In this case wilink module is acting in single role as AP , with this we are not seeing the issue.

We are capturing the Wifi Log's and WL18xx Debug and Troubleshoot as mentioned in the link https://processors.wiki.ti.com/index.php/WL18xx_Debug_and_Troubleshoot

Thanks,

So it seems that the extra AP role is interfering with connection of the other stations.

Have you succeeded in fetching the logs?

Shlomi

And another idea to try out, since you mentioned that the stations are not communicating out anyway, how about connecting all stations to WiLink AP first (which should pass as you mentioned) and only then start the WiLink station role and connect to the router?

do you see a problem with it?

do you expect anything from WiLink station role that should be connected prior to other station connecting to it locally?

Shlomi

Hi Shlomi,

Yet to get the HW rework done to  Looger log's. Hopefully we can share them on Monday.

We could collect the the sniffer logs(attached) in monitor mode. Murata devices in the log are the STA devices we are using. "ACT" is the SSID that AP visible for Registration. STA's would be trying to join the SSID "ACT". Post the Registration process SSID will be switched to "DP2_74:E1:82:8C:47:1F". Sniffer_Log.zip

Hi Shlomi,

We did try to collect the log's using glogger tool via UART. We have used USB to FTDI  cable to where Rx pin of the cable is connected to WL_UART_DBG pin Wilink module through a 3v3 level shifter and  GND to GND.

We are not clear what shall be the 'bin 2' file, how ever did try selecting wl18xx-con.bin. We are not seeing any log's from the modules. Can you please share the  more details on how to capture the log's

Below is the Settings & bin files we selected.

Hi Shlomi,

Another question is, Our application needs a  minimum 15 mins  uninterrupted data transmission over UDP  with minimum delay's with out data loss. So having Wilink module in dual role can cause in any delay's in the data transmission over UDP .

Hi,

Bin File 2 is not necessary. only Bin File and it should match the binary that is stored on your device.

At this point you should see stream of data going through the hardware pin.

If not, something is broken.

Shlomi

Generally speaking, there could be cases where the device goes into station mode and leave the AP role for various tasks but at this point it should send a CTS packet to announce its absence. In any case, it is always best to work on a reliable protocol in higher levels that is based on TCP so you get re-transmissions in case packets get dropped.

Shlomi 

Hi Shlomi,

 We are using the same bin file as used for the module in glogger but we don't see full log's.

we are getting only few messages as below once after the Device powerup.

the attachment didn't go well.

can you reattach?

Uploaded Attachment Again.glog_2020_09_14_142028.csv

Hi Shlomi,

any suggestion to get the logs using glogger  ??

Mean while we could collect the Sniffer log's  again. Attached the Log's .

Hi,

The gLogger is corrupted and cannot be extracted. Not sure what is the problem.

Regarding the sniffer logs, it seems like all stations are keep on connecting, sometimes simultaneously and sometimes consecutively (do you expect it?).

When they connect consecutively, they connect securely (EAPOL frames goes in and out) and then some data exchange and eventually the station seems to disassociate from the AP. It is similar to every station and lasts about 3 seconds.

Looking some more I have noticed that the AP does not transmit any beacon out so I suspect that the stations are disassociating on a beacon loss event.

In this sense, there is nothing particular different with station  00:9d:6b:c2:28:48. 

In this case and in order to debug I must get the firmware log of the AP to understand why there are no beacons sent out.

I hope that there are no filters on the sniffer itself.

Also, do you see the expected SSID on your mobile phone?

Regards,

Shlomi

Hi Shlomi,

Yes ,filter is not applied for capturing the Log's and SSID was visible to other STA's. Not checked on Phone.

To add more details on the sequence of operation with respect to product behavior in sniffer log. 

1. STA having the MAC ( 00:9d:6b:c2:28:48 ) was in the 3rd  position during the registration process. Hence the STA would be trying to Join the Real SSID = "DP2_74:E1:82:8C:47:1F" till it receive the Registration pulse.Once STA Detects the pulse it starts to join the Default SSID = "ACT". Worst case scenario it takes 1 min to receive the Registration pulse to 3 rd STA. 

Hi,

The following is the summary of what I see from the sniffer.

1. simultaneously  connecting to SSID DP2_... in non-secured manner and disconnects immediately.Stations are:
   
   1. c2:28:48
   2. c2:27:b2
   3. c2:2a:46
   4. c2:23:26
   5. c2:27:b6
   6. c2:25:b4
   7. c2:2a:b6
2. consecutively  connecting to SSID ACT in secured manner and disconnects after ~3seconds. Stations are:
   1. c2:2a:30
   2. c2:2a:46
   3. c2:25:b4
   4. c2:23:26
   5. c2:27:b2
   6. c2:2a:b6
   7. c2:27:b6
3. WiLink turns into SSID DP2_... again. This time, the stations are connecting simultaneously   again but this time in secured manner. Stations are:
   1. c2:27:b6
   2. c2:27:b2
   3. c2:25:b4
   4. c2:2a:30
   5. c2:2a:46
   6. c2:23:26
   7. c2:28:48

Seems like c2:28:48 disconnects and c2:2a:b6 connects instead.

Does it make sense?

I can see only up to 7 station at any time.

gLogger is really mandatory to understand more.

Still, it is not clear why I cannot see the beacons in the sniffer. Even with a hidden SSID, I expect to see a beacon.

Regards,

Shlomi