Hi NXP Support Team,
I would like to report a new issue we encountered during our ongoing testing of the SD8997 Wi-Fi module in 5GHz STA mode.
Under repeated connection failure scenarios, particularly when multiple EAPOL timeouts occur (e.g., 5 consecutive failures), the driver triggers an in-band reset. However, we have observed that the firmware sometimes fails to reload afterward via the SDIO interface, leaving the Wi-Fi interface non-functional until the system is manually rebooted.
This behavior seems to occur only under reconnection stress conditions and may be related to how the SDIO interface or firmware handles recovery following a reset.
SoC: NXP i.MX6ULL (ARMv7)
Kernel: Linux 5.4.24-imx6ull
Wi-Fi Module: NXP SD8997 (SDIO interface)
Driver Stack: moal/mlan
Driver Source: https://github.com/nxp-imx/mwifiex.git -b lf-6.12.20-2.0.0 (lf-6.12.20-2.0.0)
Firmware Source: https://github.com/NXP/imx-firmware.git -b lf-6.12.20-2.0.0 (lf-6.12.20-2.0.0)
Firmware File: nxp/sdiouart8997_combo_v4.bin
Power Table: tx_power_test.bin
cfg80211_wext=0xf
max_vir_bss=1
cal_data_cfg=none
ps_mode=2
auto_ds=2
host_mlme=1
fw_name=nxp/sdiouart8997_combo_v4.bin
drv_mode=3
sta_name=wlan
max_uap_bss=2
txpwrlimit_cfg=nxp/tx_power_test.bin
Topology: SD8997 (STA) ←→ Access Point
Test Scenario: STA reconnection stress test
Failure Point: Firmware fails to reload after in-band reset, triggered by EAPOL timeouts
[87697.429777] WiFi Reset due to EAPOL timeout cnt 5
[87697.499968] ========START IN-BAND RESET===========
[87704.130302] wlan_sdio_poll_card_status failed, tries = 10000, cs = 0xc
[87704.259872] wlan_dnld_fw fail ret=0xffffffff
[87705.481337] woal_request_fw failed
[87705.484769] Firmware Init Failed
We would greatly appreciate your help in confirming the following:
Is this a known issue with SDIO firmware reload after in-band reset?
Are there any suggested workarounds or firmware/driver updates available?
Would this require escalation to the SAE team for deeper investigation?
Please let us know if you need additional logs, debug configurations, or if any specific testing is required from our side. We’re happy to support further troubleshooting.
Thank you very much for your continued assistance.
Best regards,
Yaoguang
Attachment: dmesg.txt – captured during failure event for reference.
Hi, @yangyaoguang
Just for your information, I have created an internal case to escalate this case.
Once have any updates, I will let you know.
Best regards,
Christine.
Hi, @yangyaoguang
Thanks for creating new case to us.
I will check and reply to you ASAP.
For your information, this issue is related to FW reset, it might need our internal SAE team's help for tracking root cause. In other words, it will take longer time for global communications. Please pay more patient about this.
Thanks for your understandings!
Best regards,
Christine.
Hi, @yangyaoguang
Can you please help to remove this driver load parameter: fw_name=nxp/sdiouart8997_combo_v4.bin
Also please copy both (WLAN only and combo FW) in /lib/firmware/nxp path and provide observation.
Thanks,
Christine.
Hi Christine,
Just to update you on two points:
1. Driver Load Parameter
We are not directly passing fw_name=nxp/sdiouart8997_combo_v4.bin in the driver load command.
Instead, we use the following command with a config file:
modprobe moal mod_para=nxp/wifi_mod_para.conf
Both the combo and WLAN-only firmware files have already been placed under /lib/firmware/nxp/.
Directory contents:
README_MLAN
ed_mac_ctrl_V3_8997.conf
mlanutl
sd8997_bt_v4.bin
sd8997_wlan_v4.bin
sdiouart8997_combo_v4.bin
sdsd8997_combo_v4.bin
tx_power_test.bin
txpwrlimit_cfg_8997.conf
wifi_mod_para.conf
2. STA Link Failure After Long Uptime
A new issue was recently reported by our internal testing team.
In a long-term stability test (non-reconnection scenario), the STA interface failed to reconnect after 24 days of continuous operation and required a full reboot to recover.
During this time, the device was only sending a single ping to an external host approximately every 60 seconds.
Key log:
Block woal_cfg80211_del_key in abnormal driver stateThe related log is attached for your reference.
Best regards,
Yaoguang
Regarding the second point, this issue was observed during long-term testing with an older Wi-Fi firmware, and we are now updating to the latest version to rerun the same test.
Hi, @yangyaoguang
Thanks for your updating.
1. Yes, I know you are using following command with a config file:
modprobe moal mod_para=nxp/wifi_mod_para.conf
I mean please modify this config file: /lib/firmware/nxp/wifi_mod_para.conf, remove below parameter.
fw_name=nxp/sdiouart8997_combo_v4.bin
Yes, from your given directory contents, I see both combo and Wi-Fi only FW are put there.
Please remove this parameter in /lib/firmware/nxp/wifi_mod_para.conf, then let me know your test results.
For point 2, please create a new case to us, so that we can track one issue with one case. In this way, we will not be confused and also won't miss any issue.
Best regards,
Christine.
Hi Christine,
Thanks for your instructions.
We removed the fw_name=nxp/sdiouart8997_combo_v4.bin parameter from /lib/firmware/nxp/wifi_mod_para.conf as requested. However, after doing so, the Wi-Fi driver failed to initialize successfully.
[ 31.329658] wlan: Loading MWLAN driver
[ 31.349418] wlan: Register to Bus Driver...
[ 31.353928] vendor=0x02DF device=0x9141 class=0 function=1
[ 31.365740] Attach moal handle ops, card interface type: 0x104
[ 31.371789] rps set to 0 from module param
[ 31.384957] SD8997: init module param from usr cfg
[ 31.393341] card_type: SD8997, config block: 0
[ 31.398090] cfg80211_wext=0xf
[ 31.401682] max_vir_bss=1
[ 31.404360] cal_data_cfg=none
[ 31.407714] ps_mode = 2
[ 31.410394] auto_ds = 2
[ 31.416131] host_mlme=enable
[ 31.420715] drv_mode = 3
[ 31.423957] sta_name=wlan
[ 31.427305] max_uap_bss = 2
[ 31.430680] txpwrlimit_cfg=nxp/tx_power_test.bin
[ 31.435583] Mode PSD file name: nxp/tx_power_test.bin
[ 31.435772] SDIO: sdio_blk_size=256 max_blk_count=65535 max_segs=128 max_seg_size=65535
[ 31.449893] rx_work=1 cpu_num=4
[ 31.453130] Enable moal_recv_amsdu_packet
[ 31.457238] Attach mlan adapter operations.card_type is 0x104.
[ 31.467379] wlan: Enable TX SG mode
[ 31.470961] wlan: mpa_tx.buf_size=65280
[ 31.474870] wlan: Enable RX SG mode
[ 31.541283] Request firmware: nxp/sduart8997_combo_v4.bin
[ 31.547021] wlan_sdio mmc1:0001:1: Direct firmware load for nxp/sduart8997_combo_v4.bin failed with error -2
[ 31.557949] wlan_sdio mmc1:0001:1: Falling back to sysfs fallback for: nxp/sduart8997_combo_v4.bin
[ 31.572463] WLAN: request_firmware() failed, error code = -11
[ 31.578407] woal_request_fw failed
[ 31.582174] Firmware Init Failed
[ 31.589377] Free module params
[ 31.592582] woal_add_card failed
[ 31.596264] wlan_sdio: probe of mmc1:0001:1 failed with error -1
[ 31.604477] usbcore: registered new interface driver usbxxx
[ 31.610456] wlan: Register to Bus Driver Done
[ 31.615067] wlan: Driver loaded successfully
As a result, no interface appears under iw dev.
Regarding the long-term STA issue: we will continue testing using the new firmware/driver version. If the issue can be reproduced again, we’ll proceed to open a separate case.
Best regards,
Yaoguang
Hi, @yangyaoguang
Thanks for your quick response.
Sure, Let me check internally and reply you soon.
Best regards,
Christine.
Hi, @yangyaoguang
Thank you for the driver load logs. From logs we can see below:
[ 31.541283] Request firmware: nxp/sduart8997_combo_v4.bin
Please copy the available combo FW as follows:
cd /lib/firmware/nxp/
cp sdiouart8997_combo_v4.bin sduart8997_combo_v4.bin
Please let us know if you still observe driver load failure after above steps.
Thanks,
Christine.
Hi Christine,
We followed your instruction and copied the firmware file:
cp /lib/firmware/nxp/sdiouart8997_combo_v4.bin /lib/firmware/nxp/sduart8997_combo_v4.bin
After that, the Wi-Fi driver loaded successfully, and the firmware initialized as expected.
Here is part of the log:
[ 31.293027] wlan: Register to Bus Driver...
[ 31.298597] vendor=0x02DF device=0x9141 class=0 function=1
[ 31.304248] Attach moal handle ops, card interface type: 0x104
[ 31.310149] rps set to 0 from module param
[ 31.316040] SD8997: init module param from usr cfg
[ 31.320942] card_type: SD8997, config block: 0
[ 31.325442] cfg80211_wext=0xf
[ 31.328413] max_vir_bss=1
[ 31.332138] cal_data_cfg=none
[ 31.335330] ps_mode = 2
[ 31.338024] auto_ds = 2
[ 31.340495] host_mlme=enable
[ 31.343678] drv_mode = 3
[ 31.346425] sta_name=wlan
[ 31.349052] max_uap_bss = 2
[ 31.352108] txpwrlimit_cfg=nxp/tx_power_test.bin
[ 31.357979] Mode PSD file name: nxp/tx_power_test.bin
[ 31.358168] SDIO: sdio_blk_size=256 max_blk_count=65535 max_segs=128 max_seg_size=65535
[ 31.371521] rx_work=1 cpu_num=4
[ 31.375600] Enable moal_recv_amsdu_packet
[ 31.379863] Attach mlan adapter operations.card_type is 0x104.
[ 31.386878] wlan: Enable TX SG mode
[ 31.390609] wlan: mpa_tx.buf_size=65280
[ 31.394633] wlan: Enable RX SG mode
[ 31.421308] Request firmware: nxp/sduart8997_combo_v4.bin
[ 32.226230] Wlan: FW download over, firmwarelen=635964 downloaded 626844
[ 32.839565] imx-dwmac 30bf0000.ethernet eth1: Link is Up - 100Mbps/Full - flow control rx/tx
[ 32.945532] WLAN FW is active
[ 32.948508] on_time is 32943367625
[ 32.951962] Download txpwrlimit_cfg=nxp/tx_power_test.bin
[ 33.015199] VDLL image: len=9120
[ 33.098103] fw_cap_info=0x587c6fa3, dev_cap_mask=0xffffffff
[ 33.103931] max_p2p_conn = 8, max_sta_conn = 8
[ 33.111331] FW country code WW does not match with US
[ 33.142173] Register NXP 802.11 Adapter wlan0
[ 33.147973] wlan: uap%d set max_mtu 2000
[ 33.160450] Register NXP 802.11 Adapter uap0
[ 33.167250] wlan: uap%d set max_mtu 2000
[ 33.189411] Register NXP 802.11 Adapter uap1
[ 33.195525] wlan: version = SD8997----16.92.21.p149.2-MM6X16537.p9-GPL-(FP92)
[ 33.209366] usbcore: registered new interface driver usbxxx
[ 33.217078] wlan: Register to Bus Driver Done
[ 33.221474] wlan: Driver loaded successfully
[ 33.691546] wlan: wlan0 START SCAN
Best regards,
Yaoguang
Hi, @yangyaoguang
Thanks for your quick reply.
Sounds great!
Then please help to check the original issue(Wi-Fi fails to recover after in-band reset triggered by EAPOL Timeout) whether still exist.
Best regards,
Christine.
Hi, @yangyaoguang
Do you have any updates on this case?
Whether the original issue(Wi-Fi Fails to Recover After In-Band Reset Triggered by EAPOL Timeout) is still exist?
Best regards,
Christine.
Hi Christine,
This issue is still reproducible on our side. We may need some additional time to investigate it further, and we will provide feedback once we have any new findings.
Best regards,
Yangyaoguang
Hi, @yangyaoguang
Thanks for your feedback.
If it still exist, would you please help to provide us dmesg logs for further tracking?
Hope we can resolve it ASAP.
Best regards,
Christine.
Hi, @yangyaoguang
Can you please help get below logs and details?
Best regards,
Christine.
Hi Christine,
It seems that the issue has been resolved. Based on the latest internal testing, the automation has been running for 4 days without encountering any issues. Previously, we could reproduce the problem within 1-3 hours, but with the changes we made (SDIO frequency set to 50MHz and the latest WIFI driver update), the issue no longer occurs.
Thank you for your support !
Best regards,
Yangyaoguang
Hi, @yangyaoguang
Thanks for your feedback.
Then would you please help to accept my answer as a solution so that we can close this current case?
For the SDIO frequency, let's continue to discuss in another thread, OK?
Best regards,
Christine.