WL1807MOD: WL1807MOD

Hi,

Can you pls re-test with the latest WiLink8 firmware version and let us know the results 

https://git.ti.com/cgit/wilink8-wlan/wl18xx_fw/tree/

Saurabh

Hi Saurabh,

We are facing beacon loss issue even after updating WiLink8 firmware to 8.9.0.0.88. Device gets disassociated from router and were keep getting authentication timeout till device reset. Also, we were seeing deauthenticated message with reason code 3 and 6.

We are getting below messages from kernel,

Line 36466: Dec 17 15:50:16 lccd user.info kernel: [106189.595220] wlcore: Beacon loss detected. roles:0x1
Line 36480: Dec 17 15:50:18 lccd user.info kernel: [106191.055189] wlan0: deauthenticated from 7e:d2:94:2b:b4:96 (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
Line 36481: Dec 17 15:50:18 lccd user.info kernel: [106191.153991] cfg80211: Exceeded CRDA call max attempts. Not calling CRDA
Line 36482: Dec 17 15:50:18 lccd user.info kernel: [106191.161911] wlan0: authenticate with 7e:d2:94:2b:b4:96
Line 36483: Dec 17 15:50:18 lccd user.info kernel: [106191.172476] wlan0: send auth to 7e:d2:94:2b:b4:96 (try 1/3)
Line 36484: Dec 17 15:50:18 lccd user.info kernel: [106191.202719] wlan0: authenticated
Line 36485: Dec 17 15:50:18 lccd user.info kernel: [106191.209057] wlan0: associate with 7e:d2:94:2b:b4:96 (try 1/3)
Line 36486: Dec 17 15:50:18 lccd user.info kernel: [106191.239480] wlan0: RX AssocResp from 7e:d2:94:2b:b4:96 (capab=0x1431 status=0 aid=2)
Line 36487: Dec 17 15:50:18 lccd user.info kernel: [106191.257822] wlan0: associated
Line 36488: Dec 17 15:50:18 lccd user.info kernel: [106191.304126] wlcore: Association completed.
Line 37606: Dec 17 15:52:07 lccd user.info kernel: [106300.049586] wlan0: disassociated from 7e:d2:94:2b:b4:96 (Reason: 1)

Line 21112: Dec 17 17:33:53 lccd user.info kernel: [112406.212763] wlan0: authenticate with 7e:d2:94:2b:b4:96
Line 21113: Dec 17 17:33:53 lccd user.info kernel: [112406.222082] wlan0: direct probe to 7e:d2:94:2b:b4:96 (try 1/3)
Line 21115: Dec 17 17:33:53 lccd user.info kernel: [112406.425533] wlan0: direct probe to 7e:d2:94:2b:b4:96 (try 2/3)
Line 21116: Dec 17 17:33:53 lccd user.info kernel: [112406.635528] wlan0: direct probe to 7e:d2:94:2b:b4:96 (try 3/3)
Line 21117: Dec 17 17:33:54 lccd user.info kernel: [112406.845482] wlan0: authentication with 7e:d2:94:2b:b4:96 timed out

Hi,

-  Are all devices under test showing the same behavior - beacon loss ? or is it one specific DUT ?

-  Is beacon loss reported immediately after DUT connects to the AP ?

-  Is this issue seen if DUT connects to a  different AP ?

- What version of linux kernel is running on the product ?

Saurabh

 Hi Saurabh,

Please find the answers below.

-  Are all devices under test showing the same behavior - beacon loss ? or is it one specific DUT ? <Prabha> After upgrading WiLink8 to 8.9.0.0.88, so far we have observed this in one specific DUT.

-  Is beacon loss reported immediately after DUT connects to the AP ? <Prabha> Yes, after ~40 seconds from DUT connect to AP. But the deauth with reason code 3 or 6 happens randomly.

Line 34764: Dec 17 15:48:21 lccd user.info kernel: [106074.257375] wlan0: deauthenticated from 7e:d2:94:2b:b4:96 (Reason: 3=DEAUTH_LEAVING)
Line 34765: Dec 17 15:48:21 lccd user.info kernel: [106074.402119] cfg80211: Exceeded CRDA call max attempts. Not calling CRDA
Line 35612: Dec 17 15:49:19 lccd user.info kernel: [106132.551964] wlan0: authenticate with 7e:d2:94:2b:b4:96
Line 35613: Dec 17 15:49:19 lccd user.info kernel: [106132.561981] wlan0: send auth to 7e:d2:94:2b:b4:96 (try 1/3)
Line 35614: Dec 17 15:49:19 lccd user.info kernel: [106132.633696] wlan0: send auth to 7e:d2:94:2b:b4:96 (try 2/3)
Line 35616: Dec 17 15:49:19 lccd user.info kernel: [106132.713486] wlan0: send auth to 7e:d2:94:2b:b4:96 (try 3/3)
Line 35618: Dec 17 15:49:19 lccd user.info kernel: [106132.764923] wlan0: authentication with 7e:d2:94:2b:b4:96 timed out
Line 35813: Dec 17 15:49:29 lccd user.info kernel: [106141.808474] wlan0: authenticate with 7e:d2:94:2b:b4:96
Line 35814: Dec 17 15:49:29 lccd user.info kernel: [106141.813650] wlan0: send auth to 7e:d2:94:2b:b4:96 (try 1/3)
Line 35815: Dec 17 15:49:29 lccd user.info kernel: [106141.832116] wlan0: authenticated
Line 35816: Dec 17 15:49:29 lccd user.info kernel: [106141.835824] wlan0: associate with 7e:d2:94:2b:b4:96 (try 1/3)
Line 35817: Dec 17 15:49:29 lccd user.info kernel: [106141.855532] wlan0: RX AssocResp from 7e:d2:94:2b:b4:96 (capab=0x1431 status=0 aid=2)
Line 35818: Dec 17 15:49:29 lccd user.info kernel: [106141.873109] wlan0: associated
Line 35819: Dec 17 15:49:29 lccd user.info kernel: [106141.917950] wlcore: Association completed.
Line 36466: Dec 17 15:50:16 lccd user.info kernel: [106189.595220] wlcore: Beacon loss detected. roles:0x1
Line 36480: Dec 17 15:50:18 lccd user.info kernel: [106191.055189] wlan0: deauthenticated from 7e:d2:94:2b:b4:96 (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)

-  Is this issue seen if DUT connects to a  different AP ? <Prabha> I will get back on this.

- What version of linux kernel is running on the product ? <Prabha> Linux version used is 3.14.52.

Hi Prabha,

There could be multiple reasons for beacon loss event , including bad RF reception. In case this issue is seen only on one specific DUT , it might be a good idea to ensure RF is working as expected on that DUT. Typically ,interoperability issues with APs are not specific to DUT.  You may refer to calibrator utility : https://www.ti.com/lit/ug/swru562/swru562.pdf

Saurabh

Hi Saurabh,

As per your request, we have connected DUT to different AP(AT&T). Then, we don't see beacon loss for past ~24 hours. This testing involves two DUT and both of them have reported beacon loss for router(Netgear Orbi(RBR20)). Does WiLink8 driver supports this netgear RBR20 router? Since it is not DUT specific issue, I don't think RF testing is required. Could it be router specific issue?

Thanks,

Prabha.

Hi Prabha,

I will check with the test team if we have this specific AP model in the lab

Kernel 3.14.x is very old. Would you know the version of WiLink8 driver running on DUT i.e.  is it running in-tree WiLink8 kernel driver or backported R8.7_SP3 version   ?

Due to holidays there might be delay in responses

Saurabh

Hi Saurabh,

We are using backported R8.7_SP3 version. With that, we have updated WiLink8 TI binary alone to 8.9.0.0.88. 

We have two issues here,

1. DUT getting disconnected from AP randomly

2. DUT is not able to connect back to AP even if the application is retrying. DUT keep get authentication timeout.

It will be great if you can suggest, how to recover DUT from this state automatically? I am not sure if restarting wlcore driver will help or not. Please let us know if you have any other fix in the driver.

Thanks,

Prabha.

Hi,

You may try to unload and re-load WiLink8 driver kernel modules and check if that helps.

We have a different model of Netgear Orbi in our lab. We will check if we are able to run some tests on it. 

Are you able to share wireless sniffer and firmware logs with us when this issue occurs ?

Saurabh

Hi Saurabh,

Sure we will share the logs. What wireless sniffer would you suggest to use? Would it be better to sniff at the TSTAT end or from laptop?

Regards,

Johncy

Hi,

Can you please provide wireless over the air sniffer logs using wireshark, omnipeek or similar sniffer software. You may run the sniffer tool on a laptop/PC

Also , it would be helpful if you could provide us with WiLink8 firmware logs.

Question -  How much time does it take to reproduce this issue after DUT connects to the AP ?

Saurabh

Thanks Saurabh. Can you guide on how to get the WiLink8 firmware logs?

Hi,

Pls consult gLogger documentation  : https://www.ti.com/lit/ug/swru435a/swru435a.pdf

gLogger needs to be used in UART mode ( section 3 ). This is part of wireless tools package : https://www.ti.com/tool/WILINK-BT_WIFI-WIRELESS_TOOLS

FYI -  WL_UART_DBG is 1.8v IO

Saurabh

Hi,

This is a Chang, I a SW engineer working with Johncy.

I got a Linksys AC1200 adapter today, tried to do an over the air capture. I started with Wireshark first, realized that Wireshark does not support monitor mode on Window. As our issue is that DUT can not connect to AP, I think we really need to run the adapter in monitor mode so that we can capture all the wifi management frames (packets), to possibly figure out why the DUT is not able to connect to the AP.

I also tried Omnipeek. But it crashes every time I started to capture. What do you actually use to do the over the air capture? Can you please provide your setup details so that we can do the same?

Also, the DUT connection issue happens after router reset, or temporary disabled. 

BTW, I am in Dallas, Texas. If you are in US, we might be able to have a short conference call, so we can discuss the issue, and get your suggestions.

Thank you,

Chang

Hi,

We use Omnipeek to capture wireless traces. It's licensed software. You need to start software with admin privileges , and select the adapter under 'capture' tab. You may need special drivers for the adapter : https://mypeek.liveaction.com/driver_downloads.php . You may contact liveaction sales to get more details on this. 

Saurabh

Hi Saurabh, Are you able to reproduce this issue in your lab? Do you have any solution for this issue? We are thinking to restart WiFi module firmware if association timeout continuously for 10minutes. Will it make WiFi module to re-associate with router in next retry? Will there be any side effects if we restart WiFi module at 10 minutes interval during authentication timeout?

Hi Saurabh, Are you able to reproduce this issue in your lab? Do you have any solution for this issue? We are thinking to restart WiFi module firmware if association timeout continuously for 10minutes. Will it make WiFi module to re-associate with router in next retry? Will there be any side effects if we restart WiFi module at 10 minutes interval during authentication timeout?

Hi,

We tested using a different model of Netgear Orbi AP and did not see the issue at our end.

You may try re-starting the WiFi module at your end and check if helps mitigate the issue and meet your product requirements.

Saurabh

Hi Surabh, 

We have tried restarting WiFi module using the following commands during association timeout,

ip link set wlan0 down // link down

stop wpa supplicant
ip link set wlan0 up // link up

iw wlan0 set power_save off
echo 0 > /sys/kernel/debug/ieee80211/phy0/wlcore/sleep_auth

start WPA Supplicant

Even after this WiFi association command was getting authentication timeout. Do we need to add any other commands to the restart sequence?

Will there be any timing related issues during command execution?

Thanks,

Prabha.

Hi,

I don't believe bringing WiFi interface down/up during authentication will mitigate the issue.

You may try to disable ELP and see if it helps

iw wlan0 set power_save off

echo 0 > /sys/kernel/debug/ieee80211/phy0/wlcore/sleep_auth

We will need to review WiFi sniffer and firmware logs to be able to troubleshoot this.

Saurabh

Hi Saurabh,

We would like to confirm, the below sequence s part of our connect.

When we do a connect to the AP selected by the user, a scan was performed to list the AP's.

But when we do a retry when the connect fails, no scan is performed. Same when we do a reconnect to AP when LCC gets powered on there is no scan performed. Will this have any impact or make a difference?

Hi,

You may initiate scan on DUT and re-test.

SN