88W9098 lf-6.12.34_2.1.0 firmware failure with uap_max_sta=64

[RPontusHedman]

We are using the NXP 88W9098 chipset via a uBlox JODY-W377-00B module on a TI TMDS64EVM evaluation board. The intent is mostly to use it as an access point via Linux.

Specifically, we have been setting uap_max_sta=64 and max_sta_conn=64 in wifi_mod_para.conf to support more stations than the default. This used to work with earlier firmware but now fails. We now get a "woal_request_fw failed" error on bootup and no devices appear.

In short, it worked fine in lf-6.12.20_2.0.0 but no longer works with lf-6.12.34_2.1.0 with a few surprises:

- It does work if I set "uap_max_sta=48" and "max_sta_conn=48" instead of 64 in wifi_mod_para.conf . I basically did a binary search to find a working lower value.

- It also works with the if I use the new lf-6.12.34_2.1.0 mwifiex drivers but the old lf-6.12.20_2.0.0 imx-firmware

That is, the newer drivers seem to work fine, but only with the older firmware when using the higher settings.  With the newer firmware, it has to be lowered from 64 to 48.

I see that mlan/mlan_ioctl.h in branch lf-6.12.34_2.1.0 still has "#define MAX_STA_COUNT 64". So is this no longer correct? Either the newer firmware should reject settings it cannot support, or the firmware should be updated to support it again.

Best,
Pontus Hedman

[RPontusHedman]

Hi Shaun and thanks for the reply,

We are using a Debian12 (VyOS) base system currently using Linux kernel 6.6.114 on a TI TMDS64EVM arm64 board.

The formerly working but now problematic wifi_mod_para.conf is attached (with a .txt suffix). Look for the "PSL:" lines for our changes from the https://github.com/nxp-imx/imx-firmware.git version.  It is very little.

In short "uap_max_sta = 64" in the PCIE9098_0 and PCIE9098_1 sections used to work, but now I have to use the value of "uap_max_sta = 48" or the else the firmware load fails as described in my first message.

Pontus

[shaun_wu]

Hello @RPontusHedman 

Which host OS you are using?

Could you help share wifi_mod_para.conf?

Best Regards

Shaun

[RPontusHedman]

Update... I get the same misbehaviour with the recent lf-6.12.49_2.2.0 imx-firmware and mwifiex as well.

That is, it no longer works with uap_max_sta=64 for PCIE9098_0 and PCIE9098_1 in wifi_mod_para.conf. I have to lower it to uap_max_sta=48 for the firmware to load successfully.

This is on a Debian12 arm64 system based on Linux 6.6.117.

[RPontusHedman]

Hi Shaun; any update on this?

Again, the relevant parts of wifi_mod_para.conf on our Linux Debian12 kernel 6.6.117 is below.

If you increase the value of "uap_max_sta = 48" the devices fail to function as access points. Either the devices do not appear, and/or there are errors like "IOCTL failed: 0000000033d2f3dc id=0x20000, sub_id=0x2000c action=1, status_code=0x1 [FW_NOT_READY]" and hostapd cannot use the device.

It used to work with "uap_max_sta = 64" with the lf-6.12.20_2.0.0 branch but fails with lf-6.12.34_2.1.0. Now anything above 48 fails and it seems related to the firmware as described earlier.

Pontus

wifi_mod_para.conf snippet follows:

PCIE9098_0 = {
cal_data_cfg=none
# PSL: increase connections from the default 8 (client and AP).
uap_max_sta = 48
# PSL: use only ANT1 (J3), "Path A" for 2GHz and 5GHz
antcfg = 0x101
}

PCIE9098_1 = {
cal_data_cfg=none
# PSL: increase connections from the default 8 (client and AP).
uap_max_sta = 48
# PSL: use only ANT1 (J3), "Path A" for 2GHz and 5GHz
antcfg = 0x101
}