Imx8mp failed to connect to WiFi metwork

hanqish · February 27, 2026, 12:45am

I’m using imx8mp + Dahlia V1.1, failed to connect to WiFi network.
I’m using the latest Torizon OS
ID=torizon
NAME=“Torizon OS”
VERSION=“7.5.0+build.30 (scarthgap)”
VERSION_ID=7.5.0-build.30
VERSION_CODENAME=“scarthgap”
PRETTY_NAME=“Torizon OS 7.5.0+build.30 (scarthgap)”
CPE_NAME=“cpe:/o:openembedded:torizon:7.5.0+build.30”
BUILD_ID=“30”
ANSI_COLOR=“1;34”
VARIANT=“Docker”

I’ve tried to reload the mwifiex_sdio driver, power cycle the board, and re-flash the image, but it still failed authentication.
Below is the system log to help debug:

[ 2009.324133] mwifiex_sdio mmc0:0001:1: info: shutdown mwifiex…
[ 2009.324248] mwifiex_sdio mmc0:0001:1: PREP_CMD: card is removed
[ 2009.326094] mwifiex_sdio mmc0:0001:1: PREP_CMD: card is removed
[ 2009.395593] mwifiex_sdio mmc0:0001:1: PREP_CMD: card is removed
[ 2021.884883] mwifiex_sdio mmc0:0001:1: WLAN FW already running! Skip FW dnld
[ 2021.884905] mwifiex_sdio mmc0:0001:1: WLAN FW is active
[ 2021.928558] mwifiex_sdio mmc0:0001:1: event: unknown event id: 0x81
[ 2021.928705] mwifiex_sdio mmc0:0001:1: Unknown GET_HW_SPEC TLV type: 0x23e
[ 2021.928714] mwifiex_sdio mmc0:0001:1: host_mlme: enable, key_api: 2
[ 2021.965058] mwifiex_sdio mmc0:0001:1: info: MWIFIEX VERSION: mwifiex 1.0 (16.92.21.p137)
[ 2021.965077] mwifiex_sdio mmc0:0001:1: driver_version = mwifiex 1.0 (16.92.21.p137)
[ 2269.070164] mwifiex_sdio mmc0:0001:1: auth: send authentication to 28:70:4e:62:85:e3
[ 2269.083454] mwifiex_sdio mmc0:0001:1: auth: receive authentication from 28:70:4e:62:85:e3
[ 2271.663420] mwifiex_sdio mmc0:0001:1: CMD_RESP: cmd 0x10d error, result=0x1
[ 2271.663451] mwifiex_sdio mmc0:0001:1: failed to remain on channel
[ 2272.565115] mwifiex_sdio mmc0:0001:1: auth: send authentication to 28:70:4e:62:8c:4b
[ 2278.859700] mwifiex_sdio mmc0:0001:1: Pending auth on going
[ 2280.591051] mwifiex_sdio mmc0:0001:1: Pending auth on going
[ 2290.321574] mwifiex_sdio mmc0:0001:1: Pending auth on going
[ 2294.425268] mwifiex_sdio mmc0:0001:1: Pending auth on going
[ 2305.234027] mwifiex_sdio mmc0:0001:1: Pending auth on going
[ 2323.375313] mwifiex_sdio mmc0:0001:1: Pending auth on going
[ 2334.179037] mwifiex_sdio mmc0:0001:1: Pending auth on going
[ 2352.378457] mwifiex_sdio mmc0:0001:1: Pending auth on going
[ 2363.181644] mwifiex_sdio mmc0:0001:1: Pending auth on going
[ 2501.009781] mwifiex_sdio mmc0:0001:1: info: shutdown mwifiex…
[ 2501.009897] mwifiex_sdio mmc0:0001:1: PREP_CMD: card is removed
[ 2501.011716] mwifiex_sdio mmc0:0001:1: PREP_CMD: card is removed
[ 2501.085790] mwifiex_sdio mmc0:0001:1: PREP_CMD: card is removed
[ 2512.104211] mwifiex_sdio mmc0:0001:1: info: FW download over, size 624880 bytes
[ 2512.935494] mwifiex_sdio mmc0:0001:1: WLAN FW is active
[ 2512.978990] mwifiex_sdio mmc0:0001:1: event: unknown event id: 0x81
[ 2512.979110] mwifiex_sdio mmc0:0001:1: Unknown GET_HW_SPEC TLV type: 0x23e
[ 2512.979117] mwifiex_sdio mmc0:0001:1: host_mlme: enable, key_api: 2
[ 2513.012364] mwifiex_sdio mmc0:0001:1: info: MWIFIEX VERSION: mwifiex 1.0 (16.92.21.p137)
[ 2513.012383] mwifiex_sdio mmc0:0001:1: driver_version = mwifiex 1.0 (16.92.21.p137)
[ 2596.215244] mwifiex_sdio mmc0:0001:1: auth: send authentication to 28:70:4e:62:85:e3
[ 2596.253444] mwifiex_sdio mmc0:0001:1: auth: receive authentication from 28:70:4e:62:85:e3
[ 2598.808253] mwifiex_sdio mmc0:0001:1: CMD_RESP: cmd 0x10d error, result=0x1
[ 2598.808282] mwifiex_sdio mmc0:0001:1: failed to remain on channel
[ 2599.635200] mwifiex_sdio mmc0:0001:1: auth: send authentication to 28:70:4e:61:8a:6e
[ 2605.938905] mwifiex_sdio mmc0:0001:1: Pending auth on going
[ 2607.745731] mwifiex_sdio mmc0:0001:1: Pending auth on going
[ 2617.438644] mwifiex_sdio mmc0:0001:1: Pending auth on going
[ 2624.361952] mwifiex_sdio mmc0:0001:1: Pending auth on going
[ 2635.159313] mwifiex_sdio mmc0:0001:1: Pending auth on going
[ 2653.372264] mwifiex_sdio mmc0:0001:1: Pending auth on going
[ 2686.017553] mwifiex_sdio mmc0:0001:1: Pending auth on going
[ 2696.822678] mwifiex_sdio mmc0:0001:1: Pending auth on going
[ 2710.203487] mwifiex_sdio mmc0:0001:1: Pending auth on going
[ 2720.937541] mwifiex_sdio mmc0:0001:1: Pending auth on going
[ 2738.379232] mwifiex_sdio mmc0:0001:1: Pending auth on going
[ 2749.116156] mwifiex_sdio mmc0:0001:1: Pending auth on going
[ 2767.385296] mwifiex_sdio mmc0:0001:1: Pending auth on going
[ 2778.244235] mwifiex_sdio mmc0:0001:1: Pending auth on going
[ 2796.368195] mwifiex_sdio mmc0:0001:1: Pending auth on going
[ 2807.161960] mwifiex_sdio mmc0:0001:1: Pending auth on going
[ 2825.375302] mwifiex_sdio mmc0:0001:1: Pending auth on going
[ 2836.223855] mwifiex_sdio mmc0:0001:1: Pending auth on going

ToradexAI · February 27, 2026, 12:46am

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.

Based on your logs and the known issues with the mwifiex_sdio driver, here are several troubleshooting steps to resolve the WiFi authentication failures:

Driver Stability Issues

The mwifiex_sdio driver is known to have stability issues, particularly with authentication and connectivity (1). Your logs show the classic symptoms of the driver getting stuck in a “Pending auth on going” state, which is a documented issue with this driver.

Blacklisted WiFi Drivers

The mwifiex drivers are blacklisted by default in Torizon OS to optimize boot time and prevent timing-related connectivity issues (2). The drivers are loaded later in the boot process using a systemd service to ensure more reliable operation.

Troubleshooting Steps

1. Check Driver Status

First, verify which WiFi interfaces are available:

iw dev

(3)

You should see both mlan0 (station mode) and uap0 (access point mode) interfaces.

2. Reset the WiFi Module

Try a complete reset of the WiFi subsystem:

sudo modprobe -r mwifiex_sdio
sudo modprobe mwifiex_sdio

3. Check Network Configuration

Verify your network configuration using NetworkManager:

nmcli device status
nmcli connection show

4. Alternative Driver Consideration

The documentation indicates that some use cases don’t work well with the mainline mwifiex driver (1). If your connectivity issues persist, NXP’s downstream drivers may provide better stability for certain scenarios, though this would require custom kernel development.

5. Hardware Verification

Since you’re using a Verdin iMX8M Plus with the AW-CM276NF WiFi module, ensure:

The antenna is properly connected
No physical damage to the module
The WiFi network you’re connecting to is compatible with the module’s capabilities

Known Limitations

The AW-CM276NF module has some documented limitations where certain use cases (like simultaneous Wi-Fi client mode + Bluetooth) may not work reliably with the mainline driver (1).

If these steps don’t resolve the issue, the problem may require investigation into alternative driver solutions or hardware-specific configurations.

Best regards, Toradex AI Assistant.

Did you like my answer?

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

hai.tx · March 2, 2026, 6:09am

Hi Shao，

Please refer to below article for wifi usage on verdin imx8mp with TorizonOS.
https://developer.toradex.com/quickstart/bringup/wifi-usage/

Hai Qin
Toradex

hanqish · March 3, 2026, 4:40am

It won’t work for the first time trying nmcli, but after the connection has been recorded, it will succeed after reset the Dahlia board.
My ultimate goal is to enable the WiFi feature in my customized buildroot image, but kept getting the logs above. I’m checked the mrvl firmware version and it’s the same one used for TorizonOS, is there any clue why I’m seeing the logs above?

hai.tx · March 3, 2026, 7:04am

Hi Shao,

Which SW is used to manage network in your buildroot image? For Toradex, we use Network manager for TorizonOS and Connman for Yocto based Linux BSP. I have tested with Verdin iMX8MP+Dahlia on my site with TorizonOS BSP 7.x and Yocto Linux BSP 7.x, both work fine to connect my office wifi AP, and please find detailed log as below. BTW, please do connect 2pcs antennas accordingly to use Wifi on Verdin iMX8MP.
./ TorizonOS
torizon@verdin-imx8mp-06849028:~$ nmcli device wifi list
IN-USE BSSID SSID MODE CHAN RATE SIGNAL BARS SECURITY
C2:12:3B:27:89:72 Thingget Infra 1 130 Mbit/s 92 **** WPA2
EC:26:CA:EE:9D:BC Lotus_WIFI Infra 6 405 Mbit/s 79 *** WPA1 WPA2
9A:00:74:EC:48:54 ChinaNet-PCEV Infra 1 130 Mbit/s 75 *** WPA1 WPA2
5C:02:14:A9:BD:0E sunborne Infra 8 270 Mbit/s 69 *** WPA2
B4:FB:E4:C1:90:14 MONTASTAR Infra 6 405 Mbit/s 67 * WPA2
…
torizon@verdin-imx8mp-06849028:~$ nmcli -a device wifi connect MONTASTAR
Password:
Device ‘mlan0’ successfully activated with ‘48b56ded-5618-4908-8337-69794f6bc810’.

./ Yocto Linux BSP
root@verdin-imx8mp-06849028:~# connmanctl
connmanctl> enable wifi
Enabled wifi
connmanctl> scan wifi
Scan completed for wifi
connmanctl> agent on[1299.737463] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start : Invals

Agent registered
connmanctl> services
Thingget wifi_00e93a9b0a7d_5468696e67676574_managed_psk
MONTASTAR wifi_00e93a9b0a7d_4d4f4e544153544152_managed_psk
wifi_00e93a9b0a7d_hidden_managed_psk
…
connmanctl> connect wifi_00e93a9b0a7d_4d4f4e544153544152_managed_psk
Agent RequestInput wifi_00e93a9b0a7d_4d4f4e544153544152_managed_psk
Passphrase = [Type=psk, Requirement=mandatory]
Passphrase? …
connmanctl> [1425.070015] mwifiex_sdio mmc0:0001:1: auth: send authentication to b4:fb:e4:c4
[1425.081026] mwifiex_sdio mmc0:0001:1: auth: receive authentication from b4:fb:e4:c2:90:14
[1425.094101] mwifiex_sdio mmc0:0001:1: assoc: send association to b4:fb:e4:c2:90:14
[1425.111829] mwifiex_sdio mmc0:0001:1: assoc: associated with b4:fb:e4:c2:90:14
[1425.123102] mwifiex_sdio mmc0:0001:1: key: send EAPOL to b4:fb:e4:c2:90:14
[1425.144951] mwifiex_sdio mmc0:0001:1: key: send EAPOL to b4:fb:e4:c2:90:14
Connected wifi_00e93a9b0a7d_4d4f4e544153544152_managed_psk
connmanctl>

Hai Qin
Toradex