Can not connect to Wifi 5G but 2.4G is OK

[Alex888]

Hi NXP experts,

We are using MTK 6890 with the wifi chip AzureWave module(the model is AW-XM458) to implement our AP product.
We found that sometimes the STA cannot connect to AP Wifi 5G, but 2.4G is OK.

Test procedure as below:

1. The AP turn on 2.4G on muap0 and 5G on uap0 , and do not connect to any clients.

2. Plug in the charger (the purpose is to avoid the system enter suspend and keep Wifi active all the time,)

3. Wait for 24 hours or longer, and then a STA try to connect to 5G, but shows fail to connect. But connect to 2.4G is OK.

From the sniffer logs we found that  2.4G can be  connected is because the STA (IntelCor_0c:44:b4) sent a probe Request, and AP has returned a Probe Response. But in the 5G fail case, STA (IntelCor_0c:44:b4) sent probe Request, but the AP did not return a Probe Response.

- 2G_OK.pcapng:

5552          35.094860        IntelCor_0c:44:b4    Broadcast         802.11          169  Probe Request, SN=2228, FN=0, Flags=........C, SSID=D52M-22NT-2.4GHz7187   25.304694        AzureWav_c0:cf:c1          IntelCor_07:2c:c2    802.11      372  Probe Response, SN=1532, FN=0, Flags=........C, BI=100, SSID=D52M-22NT-2.4GHz

5555          35.098792        AzureWav_c0:cf:c1 IntelCor_0c:44:b4          802.11      372  Probe Response, SN=2942, FN=0, Flags=........C, BI=100, SSID=D52M-22NT-2.4GHz

 - 5G_Fail.pcapng:

454643     114.457805      IntelCor_0c:44:b4    Broadcast         802.11          175  Probe Request, SN=113, FN=0, Flags=........C, SSID=D52M-22NT-5GHz

…

460419     115.690655      IntelCor_0c:44:b4    Broadcast         802.11          175  Probe Request, SN=156, FN=0, Flags=........C, SSID=D52M-22NT-5GHz

Sniffer logs and kernel log are attached. Could you please help to check what could caused this problem?

Thank you.

[Alex888]

Hi NXP experts,

We have met this problem on different devices.

Can someone please help to check this issue?

Thank you.

[Alex888]

Hi AllenHsu2,

Sorry for the late reply. The reproduce rate is 100%. After put the device in idle (with no clients connected), the issue occurs sometimes after one day, sometimes after 2 days. But I can still reproduce this issue even with different devices.

Thanks.

[AllenHsu2]

@Alex888 

I also use the 88w9098 chip, can i know this issue reproduce rate?

I'm not sure whether the FW issue or not, but from your sniffer log, it seems that FW or driver didn't reply the probe request. Hope NXP can fix this issue