About failure of IEEE802.11az command in SDK demo application

[KKobayashi]

I have Embedded Artists EAR00409 (Murata Type 2EL) Wi-Fi modules equipped with NXP IW612.

I am trying to verify the operation of IEEE802.11az (range measurement function) from the MCUXpresso SDK demo application in combination with NXP MIMXRT1160-EVK (M.2 connection), but it is not working properly and I am having trouble.
​
Environment:
OS: WIndows 11 Pro
MCUXpresso IDE: 24.12.148
SDK: 25_06_00_MIMXRT1160-EVK

According to UM11442 (NXP Wi-Fi and Bluetooth Demo Applications User Guide
for i.MX RT Platforms), a project of "wifi cli demo" was built with the following macros:
WIFI_IW612_BOARD_MURATA_2EL_M2
and
CONFIG_11AZ, CONFIG_11MC, CONFIG_CSI, CONFIG_WLS_CSI_PROC

One board was configured as an access point (AP) ans the other as a station (STA).
The AP started as follows, and the station can connect to the AP correctly.

wlan-add 1 ssid ftmap bssid FE:84:A7:51:E8:F4 ip:192.168.10.1,192.168.10.1,255.255.255.0 role uap channel 36
wlan-start-network 1
wlan-set-uap-bandwidth 1

From the STA, the following commands were input:
wlan-11az-rang-cfg 1 format_bw 0 num_measurements 5 measurement_freq 1 i2r_sts 0 r2i_sts 0 i2r_lmr 0
wlan-ftm-ctrl 1 loop_cnt 1 channel 36 mac FE:84:A7:51:E8:F4

However, the wlan-ftm-ctrl command always reports "FTM Session Failed" even if I have changed the parameters.

Is this the correct way to use these commands? Or are other settings required?

Debug log of the STA is as follows:

wlan-11az-rang-cfg 1 format_bw 0 num_measurements 5 measurement_freq 1 i2r_sts 0 r2i_sts 0 i2r_lmr 0
[wifi] Set Ranging Parameters:
[wifi] ---------------------------------
[wifi] format_bw:0
[wifi] az_measurement_freq:1
[wifi] az_number_of_measurements:5
[wifi] max_i2r_sts_upto80:0
[wifi] max_r2i_sts_upto80:0
[wifi] i2r_lmr_feedback:0

wlan-ftm-ctrl 1 loop_cnt 1 channel 36 mac FE:84:A7:51:E8:F4
[wifi] [INFO] FTM Session Control Started on 36 channel with Peer FE:84:A7:51:E8:F4
[wevt] EVENT - : 0x8d Len : 188 Reason: 45
[wifi] Measured Distance: m; Kalman Distance: m [3255759 ms]
[wifi] EVENT: MLAN_CSI Processing results: -29849 | 30157 (848004), TSF[c20ef15e]
[wevt] EVENT - : 0x8d Len : 188 Reason: 45
[wifi] Measured Distance: m; Kalman Distance: m [3256759 ms]
[wifi] EVENT: MLAN_CSI Processing results: -29747 | 30079 (848004), TSF[c21e351d]
[wevt] EVENT - : 0x8d Len : 188 Reason: 45
[wifi] Measured Distance: m; Kalman Distance: m [3257759 ms]
[wifi] EVENT: MLAN_CSI Processing results: -30105 | 30479 (848004), TSF[c22d78ff]
[wevt] EVENT - : 0x8d Len : 188 Reason: 45
[wifi] EVENT: MLAN_CSI Processing results: -29798 | 30156 (848004), TSF[c23cbcc3]
[wevt] EVENT - : 0x8d Len : 188 Reason: 45
[wifi] Measured Distance: m; Kalman Distance: m [3259760 ms]
[wifi] EVENT: MLAN_CSI Processing results: -30208 | 30556 (848004), TSF[c24c009a]
[wevt] EVENT - : 0x86 Len : 34 Reason: 5
[INFO] EventID: 0x86 SubeventID:5
[wifi] WLS_SUB_EVENT_ANQP_RESP_RECEIVED
FTM Session Failed!

Debug log at the AP when the above commands input is as follows:

[wevt] EVENT - : 0x8d Len : 188 Reason: 45
[wevt] EVENT - : 0x8d Len : 188 Reason: 45
[wevt] EVENT - : 0x8d Len : 188 Reason: 45
[wevt] EVENT - : 0x8d Len : 188 Reason: 45
[wevt] EVENT - : 0x8d Len : 188 Reason: 45

Thank you for your help.

[RomanVR]

Hello @KKobayashi, hope you are doing well.

The features enabled by the macros are meant to work along with the example "wpa_supplicant" as mentioned in the UM11442, so if you are planning to integrate them, it should be done on the wpa_supplicant demo example.

Additionally, the official support for the IW612 chipset is enabled for the MIMXRT1170 EVKB and MIMXRT1060 EVKC as stated on IW611/IW612 release notes.

Please let me know if this information is useful.

[KKobayashi]

Thank you for your reply.

I understand that the features are used along with “wpa_supplicant”.

I would like to try wpa_supplicant, but MIMXRT1170-EVKB is always out of stock... MIMXRT1060-EVK“B” is available for sale, but I cannot find anywhere that sells MIMXRT1060-EVK“C”.

[RomanVR]

Hello @KKobayashi.

To try the wpa_supplicant you can use the MIMXRT1060-EVKB, although please consider that the following rework must be done in order to use the SDIO port (which is used by the 2EL Murata module):

M.2 connector:
- remove resistors: R364, R366, R351, R348, R377, R369 to disconnect the uSD connector (decrease parasitic capacitance).
- populate R345 with 0Ohm resistor

Connect external power supply to J45, set J40: 1-2 and turn on SW6.

This information can be found at the path: "<path-to-sdk-archive>\boards\evkbmimxrt1060\wifi_examples\wifi_wpa_supplicant" in the file named "readme_modules.md".

Please let me know if this information is useful.

[KKobayashi]

Thank you for the valuable information.

I obtained the MIMXRT1060-EVKB and tried the wpa_supplicant demo application.
It recognized the 2EL Murata module connected via M.2, but the command did not succeed.

The AP started as follows, and the station can connect to the AP correctly.
wlan-add 1 ssid ftmap bssid FE:84:A7:51:E8:F4 ip:192.168.10.1,192.168.10.1,255.255.255.0 role uap channel 36
wlan-start-network 1

Debug log of the STA when the wlan-11az-rang-cfg and wlan-ftm-ctrl commands were input is as follows:
(CONFIG_WIFI_EXTRA_DEBUG could not be set to 1 in the wpa_supplicant demo application.)

wlan-11az-rang-cfg 1 format_bw 1 num_measurements 5 measurement_freq 1 i2r_sts 0 r2i_sts 0 i2r_lmr 0
[wcmdr] CMD --- : 0x24d Size: 20 Seq: 0
[wcmdr] CMD_RESP - : 0x824d, result 0, len 20, seqno 0x0

wlan-ftm-ctrl 1 loop_cnt 1 channel 36 mac FE:84:A7:51:E8:F4
[wcmdr] CMD --- : 0x24e Size: 19 Seq: 0
[wcmdr] CMD_RESP - : 0x824e, result 0, len 19, seqno 0x0
[wevt] EVENT - : 0x8d Len : 304 Reason: 74
[wcmdr] CMD --- : 0x8b Size: 64 Seq: 0
[wcmdr] CMD_RESP - : 0x808b, result 0, len 64, seqno 0x0
[wevt] EVENT - : 0x8d Len : 304 Reason: 74
[wcmdr] CMD --- : 0x8b Size: 64 Seq: 0
[wcmdr] CMD_RESP - : 0x808b, result 0, len 64, seqno 0x0
[wevt] EVENT - : 0x8d Len : 304 Reason: 74
[wcmdr] CMD --- : 0x8b Size: 64 Seq: 0
[wcmdr] CMD_RESP - : 0x808b, result 0, len 64, seqno 0x0
[wevt] EVENT - : 0x86 Len : 34 Reason: 5
[INFO] EventID: 0x86 SubeventID:5
FTM Session Failed!

Debug log at the AP when the above commands is as follows:

[wevt] EVENT - : 0x8d Len : 304 Reason: 74
[wevt] EVENT - : 0x74 Len : 11 Reason: 1253
[wevt] EVENT - : 0x8d Len : 304 Reason: 74
[wevt] EVENT - : 0x8d Len : 304 Reason: 74
[wevt] EVENT - : 0x8d Len : 304 Reason: 74
[wevt] EVENT - : 0x8d Len : 304 Reason: 74
[wevt] EVENT - : 0x74 Len : 11 Reason: 1509

The Reason number displayed on the AP side yielded a different result from RT1160, but FTM still does not work.

Thank you for your help.

[RomanVR]

Hi @KKobayashi.

Could you provide more details of the steps that you followed to get the logs that you shared and your setup? Additionally, please confirm that you did the rework and that you are using the proper SDK of the RT1060 EVKB board.

Please let me know in order to try to recreate your issue.