i.MX RT WiFi stack won't associate to access point because of mis-detection of WPA version

[TomGibson]

We're using a Murata 1ZM WiFi module with an i.MX RT 1064 MCU, it's mostly working fine, however we've come across an issue where for a particular WiFi network the data passed to the scan results callback function indicates the SSID only supports WPA3. The issue is that the hardware in question that is providing that SSID doesn't support WPA3, it's too old so WPA2 should be used. I've defined CONFIG_WIFI_DEBUG in mlan_api.h and this has provided a wealth of debug information, but little I can see about authentication methods. I'm also unsure if it would be the driver code responsible for interpreting the supported authentication methods passed to the callback, or if it's the firmware downloaded to the card that determines this.

Thanks in advance.

[DanielRuvalcaba]

Hi,

Could you please provide me the following information?

1. I understand that you have been working with the wifi_setup example. Am I correct? Could you also try the wifi_cli example and tell me if you still face the same situation?
2. What is the device (brand and model) you are trying to connect with the RT1064?
3. Are you using the RT1064 EVK? Or is it a custom design?
4. Could you please share with me all the terminal output log from your test? I would like to see all the commands and messages while attempting this connection

Best regards,

Daniel.

[TomGibson]

Hi Daniel,

Thanks for your message.

1) Yes, previous testing used the WiFi Setup example. I now have done some more testing with the wifi_cli sample and have managed to get it to connect to the access point, here is the log:

========================================
wifi cli demo
========================================
Initialize CLI
========================================
Initialize WLAN Driver
========================================
MAC Address: D4:53:83:zz:xx:B2
========================================
app_cb: WLAN: received event 11
========================================
app_cb: WLAN initialized
========================================
WLAN CLIs are initialized
========================================
CLIs Available:
========================================

help
wlan-reset
wlan-version
wlan-mac
wlan-scan
wlan-scan-opt ssid <ssid> bssid ...
wlan-add <profile_name> ssid <ssid> bssid...
wlan-remove <profile_name>
wlan-list
wlan-connect <profile_name>
wlan-start-network <profile_name>
wlan-stop-network
wlan-disconnect
wlan-stat
wlan-info
wlan-address
wlan-get-uap-channel
wlan-get-uap-sta-list
wlan-ieee-ps <0/1>
wlan-deep-sleep-ps <0/1>
wlan-host-sleep <0/1> wowlan_test <0/1>
wlan-send-hostcmd
wlan-set-uap-bandwidth <1/2/3> 1:20 MHz 2:40MHz 3:80MHz
wlan-eu-crypto <EncDec>
ping [-s <packet_size>] [-c <packet_count>] [-W <timeout in sec>] <ipv4/ipv6 address>
iperf [-s|-c <host>|-a|-h] [options]
dhcp-stat
========================================
wlan-scan
Scan scheduled...

# 10 networks found:
A0:40:A0:zz:zz:F3 "REDACTED01" Infra
channel: 11
rssi: -37 dBm
security: WPA2
WMM: YES
EE:63:DA:xx:yy:F3 "REDACTED02" Infra
channel: 11
rssi: -53 dBm
security: OPEN
WMM: YES
EA:63:DA:yy:xx:F3 "REDACTED03" Infra
channel: 44
rssi: -33 dBm
security: OPEN
WMM: YES
E6:63:DA:yy:xx:F3 "REDACTED04" Infra
channel: 44
rssi: -34 dBm
security: WPA2/WPA3 SAE Mixed
WMM: YES
A0:40:A0:zz:yy:F2 "REDACTED01" Infra
channel: 36
rssi: -42 dBm
security: WPA2
WMM: YES
E6:63:DA:xx:yy:F3 "REDACTED04" Infra
channel: 11
rssi: -53 dBm
security: WPA2/WPA3 SAE Mixed
WMM: YES
EA:63:DA:xx:yy:F3 "REDACTED03" Infra
channel: 11
rssi: -52 dBm
security: OPEN
WMM: YES
EE:63:DA:yy:xx:F3 "REDACTED02" Infra
channel: 44
rssi: -33 dBm
security: OPEN
WMM: YES
E0:63:DA:yy:xx:F3 "REDACTED05" Infra
channel: 44
rssi: -33 dBm
security: WPA2
WMM: YES
E0:63:DA:xx:yy:F3 "REDACTED05" Infra
channel: 11
rssi: -52 dBm
security: WPA2
WMM: YES
wlan-add p1 ssid REDACTED04 wpa2 REDACTEDPASSPHRASE
Added "p1"

# wlan-connect p1
Connecting to network...
Use 'wlan-stat' for current connection status.

# ========================================
app_cb: WLAN: received event 1
========================================
app_cb: WLAN: authenticated to network
========================================
app_cb: WLAN: received event 0
========================================
app_cb: WLAN: connected to network
Connected to following BSS:
SSID = [REDACTED04]
IPv4 Address: [172.16.xxx.6]

2) The access points are Ubiquiti UAP-AC-Pros which are WiFi 5 and do not support WPA3. The network I am connecting to is reporting by the wifi_cli application as being WPA2/WPA3 SAE Mixed, which is not correct as the hardware does not support the latter.

3) The testing above was performed using an EVKBIMXRT1050 board, as we do not have any evks for the 1064, we have been using the Embedded Artists 1ZM evaluation card. Our custom design incorporates an RT1064 and 1ZM onto one card, I have repeated the tests with our custom software build and am still having connectivity issues, but I expect I can resolve this now I have got the wifi_cli sample to connect, however the fact the network reports as WPA2/WPA3 incorrectly is still an issue as it will make it harder to identify proper supported security after scans.

4) Output shared above, networks/macs etc redacted.

Regards,

Tom

[nxf77486]

Hello,

Thank you in advance for contacting NXP support.

Can you please help me with the SDK version is currently being used. Also if it is possible to generate the test with a different device for example the PC just to determine if the problem persist.

[TomGibson]

Hello, we are using the MCUXpresso SDK version 2.12.0. We are also using the same Murata 1ZM module on another piece of hardware which couples it with an i.MX 8MM running Linux, and we do not see this issue there - it is able to connect to the network in question fine.

Edit: also on Linux wpa supplicant reports that the network is using WPA2.

[nxf77486]

Hello,

Thank you for the information can you please help me by testing this with the latest version of the SDK 2.13.0 please find the link for the SDK download here.

Also let me know if you have any other question I will be happy to assist you.

[TomGibson]

Hello, I have just been and done some tests using the SDK 2.12 we are using from git, and a newly downloaded SDK 2.13 zip and in both cases I get the same result using the wifi_setup code sample, the network fails to connect.

The 1ZM firmware version in use on the linux platform we tested with that worked is SD8987----16.92.21.p41.4-MM5X16344.p3-GPL-(FP92), which appears to be a newer revision than in either SDK 2.12 or 2.13 (16.92.x rather than 16.91.x), I don't know if that could have any bearing on the issue.