BSP Layers and Reference Images for Yocto Project Issue Tracker

Description: IW416 Wi-Fi firmware is not part of the OE image unless explicitly added. Tdxref image is not affected.

Workaround: Manually add `linux-firmware-iw416` to the image composition.

Description: A maximum of one client is supported when Wi-Fi is in AP mode.

Description: Update Wi-Fi SDIO-UART W8997 Firmware from version 16.92.10.p219.5 (`mxm5x17283.p2`) to 16.92.21.p55.3 (`mxm5x17344.p3`)

Description: Wi-Fi connection is not stable, it stops working after less than a minute of stress testing.

Description: Add missing uap0 Wi-Fi device, to be used for AP mode

Description: Disabled Wi-Fi background scanning

Description: As concurrent use of SDIO Wi-Fi and Bluetooth is causing issues an alternative would be to use the UART for Bluetooth.

Description: We got confirmation from NXP and AzureWave that 3.3V@50MHz is not recommended due to noise affecting the wireless throughput. Limit the SDIO Clock to 25MHz for 3.3V I/O signaling on Colibri iMX6ULL.

Description: Until now the setting for `pinctrl_usdhc2` was mostly 0x17059. This means we get 87Ohms of impedance. Our hardware is matched for 50Ohms impedance. This ticket changes the pad-controls to 0x17069 which results in 52Ohms at 3.3V.

Description: When using the on-module Wi-Fi "Invalid Sched_scan" message appears. This error message has no meaning in our use-case so we removed it.

Description: The mwifiex_sdio driver goes into an unrecoverable state after the firmware of the SDIO Wi-Fi module has crashed. Note: this only covers the Wi-Fi only use case while NXP is still working on the concurrent Wi-Fi Bluetooth use case (see ELB-3039).

Workaround: Use the mwifiex_sdio driver from backports-5.4 for robust Wi-Fi functionality. Note: this only covers the Wi-Fi only use case while NXP is still working on the concurrent Wi-Fi Bluetooth use case (see ELB-3039).

Description: Support on-module WiFi is added.

Description: Support the USB WiFi products available in the Toradex webshop

Description: The on-module Wi-Fi might not resuming after suspend.

Workaround: Re-loading all Wi-Fi related kernel modules may help.

Description: We switched from CRDA to direct loading of the Wi-Fi regulatory domain database in-kernel.

Description: Update Wi-Fi Backports to 4.18

Description: Include hostapd in demo builds. Note that this is only about the naked daemon without any configuration which depends on resp. requirements. So nothing of the hostapd will be automatically started by default.

Description: Add support for on-module Wi-Fi.

Description: Include multiple Bluetooth and Wi-Fi kernel modules in our BSP demo image release packages.

Workaround: You may find our backports based on Linux kernel 4.11 here: http://git.toradex.com/cgit/backports-toradex.git/log/?h=toradex-4.11

Description: Add support for the LM Technologies LM006 Wi-Fi USB dongle to our standard images.

Description: The Wi-Fi module's firmware fails right after resuming the system and goes into an unrecoverable state.

Description: Simultaneous use of Wi-Fi and Bluetooth interfaces can lead to crashes of the firmware and/or the Linux kernel driver of the SDIO Wi-Fi/BT solution.

Workaround: Unload (rmmod) the entire Wi-Fi and Bluetooth stack and reload (insmod) it again. Worst case an entire system reboot may be required. Note: NXP is still working on the concurrent Wi-Fi Bluetooth use case.

Description: Support the USB WiFi products available in the Toradex webshop

Description: Support on-module Wi-Fi

Description: For single antenna set single_rf=0x01

Description: Currently access point aka ap mode is not supported on the LM816 Wi-Fi USB dongle.

Description: LM816 Wi-Fi speed is limited to 1 Mbit/s rx/tx.

Workaround: Updating to a later Wi-Fi backports may help but only marginally.

Description: Connecting to a Wi-Fi network, especially on 2.4GHz channels) might fail with the following errors: ``` [ 38.057353] mwifiex_sdio mmc2:0001:1: info: trying to associate to bssid b6:fb:e4:be:d8:d6 [ 39.578757] mwifiex_sdio mmc2:0001:1: ASSOC_RESP: failed, status code=1 err=0xfffc a_id=0x3fff [ 39.587549] mwifiex_sdio mmc2:0001:1: assoc failure: reason CONNECT_ERR_ASSOC_ERR_TIMEOUT [ 39.595870] mwifiex_sdio mmc2:0001:1: ASSOC_RESP: UNSPECIFIED failure [ 39.602679] mwifiex_sdio mmc2:0001:1: info: association to bssid b6:fb:e4:be:d8:d6 failed ``` or ``` [ 456.297556] mwifiex_sdio mmc2:0001:1: info: trying to associate to bssid 3c:52:a1:e4:61:50 [ 457.805023] mwifiex_sdio mmc2:0001:1: ASSOC_RESP: failed, status code=2 err=0xfffa a_id=0x3fff [ 457.805149] mwifiex_sdio mmc2:0001:1: assoc failure: reason Unknown connect failure [ 457.805453] mwifiex_sdio mmc2:0001:1: info: association to bssid 3c:52:a1:e4:61:50 failed ```

Description: Wi-Fi connection might fail, more likely after long (>4 hours) stress test. Example kernel errors logs: ``` [ 75.162225] mwifiex_sdio mmc2:0001:1: mwifiex_cmd_timeout_func: Timeout cmd id = 0x107, act = 0x0 [ 75.171155] mwifiex_sdio mmc2:0001:1: num_data_h2c_failure = 0 [ 75.177007] mwifiex_sdio mmc2:0001:1: num_cmd_h2c_failure = 0 [ 75.182793] mwifiex_sdio mmc2:0001:1: is_cmd_timedout = 1 [ 75.188199] mwifiex_sdio mmc2:0001:1: num_tx_timeout = 0 [ 75.193525] mwifiex_sdio mmc2:0001:1: last_cmd_index = 4 [ 75.198841] mwifiex_sdio mmc2:0001:1: last_cmd_id: 20 00 20 00 10 00 28 00 07 01 [ 75.206248] mwifiex_sdio mmc2:0001:1: last_cmd_act: 0c 00 0c 00 01 00 13 00 00 00 [ 75.213731] mwifiex_sdio mmc2:0001:1: last_cmd_resp_index = 3 [ 75.219489] mwifiex_sdio mmc2:0001:1: last_cmd_resp_id: 20 80 20 80 10 80 28 80 1e 80 [ 75.227318] mwifiex_sdio mmc2:0001:1: last_event_index = 0 [ 75.232821] mwifiex_sdio mmc2:0001:1: last_event: 0a 00 0b 00 0b 00 0b 00 0b 00 [ 75.240136] mwifiex_sdio mmc2:0001:1: data_sent=0 cmd_sent=0 [ 75.245816] mwifiex_sdio mmc2:0001:1: ps_mode=1 ps_state=0... ```

Description: Kernel stuck at enumerating PCIe on Colibri iMX8X non-Wi-Fi modules.

Workaround: In U-Boot enter 'setenv tdxargs initcall_blacklist=imx6_pcie_init && saveenv'.