IMX8M Plus with external M.2 PCIe Wi-Fi board not recognised


  • Hello, 

    I have an IMX8M Plus with WiFi and an Ubuntu image ( Ubuntu 20.04 LTS with Wayland 2GB )
    Wi-Fi works fine.

    On the M.2E-ke PCIe, I plug a JODY-W377-00B Wi-Fi board (88W9098-based wireless modules).
    The JODY board is detected; lspci command returns me 2 Eternet controller ( device 2b43 & 2b44)

    root@adlink:/home/imx8mp/Desktop# lspci
    00:00.0 PCI bridge: Synopsys, Inc. DWC_usb3 / PCIe bridge (rev 01)
    01:00.0 PCI bridge: Pericom Semiconductor Device b304 (rev 01)
    02:01.0 PCI bridge: Pericom Semiconductor Device b304 (rev 01)
    02:02.0 PCI bridge: Pericom Semiconductor Device b304 (rev 01)
    03:00.0 Ethernet controller: Marvell Technology Group Ltd. Device 2b43 (rev 03)
    03:00.1 Ethernet controller: Marvell Technology Group Ltd. Device 2b44 (rev 03)

    Then I check the content file : /lib/firmware/nxp/wifi_mod_para.conf

    Content of the configuration file:
    PCIE9098_0 = {
    cfg80211_wext=0xf
    wfd_name=p2p
    max_vir_bss=1
    cal_data_cfg=none
    drv_mode=7
    ps_mode=2
    auto_ds=2
    mac_addr=00:50:43:20:12:34
    fw_name=nxp/pcieuart9098_combo_v1.bin
    }
    PCIE9098_1 = {
    cfg80211_wext=0xf
    wfd_name=p2p
    max_vir_bss=1
    cal_data_cfg=none
    drv_mode=7
    ps_mode=2
    auto_ds=2
    mac_addr=00:50:43:20:52:56
    fw_name=nxp/pcieuart9098_combo_v1.bin
    }

    I use pcieuart9098_combo_v1.bin file which is inside /lib/firmware/nxp directory.

    I load the module in the kernel with the command : modprobe moal mod_para=nxp/wifi_mod_para.conf 

    modprobe command seems successful (no error)

    Here is what I have in the kernel debug message : 

    [   31.964308] woal_request_fw failed
    [   31.967738] Firmware Init Failed
    [   31.978047] Free module params
    [   31.981169] woal_pcie_probe: failed
    [   31.984793] wlan_pcie: probe of 0000:03:00.1 failed with error -14
    [   31.991151] wlan: Driver loaded successfully
    [   32.013669] BT: Loading driver
    [   32.020830] BT FW is active(0)
    [   32.023909] BT: FW already downloaded!
    [   32.052941] BT: Driver loaded successfully

    No new Wi-Fi interfaces appear.

    NXP 88W9098-based wireless modules support Wi-Fi dual radios with dual MACs and dual independent Wi-Fi interfaces created by the driver for each mode of operation. (result expected is to have 2 new interfaces)

    Do you have any idea what I have missed ?
    Thanks.



  • Hi Anthony.

       Could you please share us your business model? I will also check with our engineer for more information.

    I think below info might helpful to take troubleshoot the issue on your end.

       Based on the error message "woal_request_fw failed" and "Firmware Init Failed," it seems that the firmware for the JODY-W377-00B Wi-Fi board is not loaded correctly or is missing. Here are some steps you can take to troubleshoot the issue:

    1. Please check that the firmware file, pcieuart9098_combo_v1.bin, is in the correct location and has the correct permissions. The file should be located in /lib/firmware/nxp/ and should have read permissions for all users.

    2. Please check that the firmware file name is correct and matches the name specified in the wifi_mod_para.conf file.

    3. Verify that the firmware file is compatible with the version of the Wi-Fi board you have. Check the board's documentation or contact the manufacturer to ensure that you have the correct firmware version.

    4. Try loading the firmware file manually with the command: "modprobe woal pcie_ifname=wlan0 firm_path=/lib/firmware/nxp/pcieuart9098_combo_v1.bin". This will load the firmware and create a new interface named "wlan0." If this works, you may need to modify your wifi_mod_para.conf file to include the correct pcie_ifname.

    5. Check the kernel log for any additional error messages that may help diagnose the issue.

    6. Consider contacting the manufacturer of the Wi-Fi board for additional support. They may be able to provide more specific troubleshooting steps or offer a firmware update.

    I hope this helps you resolve the issue!


Please login to reply this topic!