i.MX 8QuadXPlus and ST60-2230C (NXP 88W8997 based) WiFi module.

[MariusU]

In the L5.15.71_2.2.0_WIFI-Doc fo the Embedded Linux for i.MX Applications Processors, on the page 56 (Chapter 5 - i.MX Platforms on-board chips and external wireless solutions) it is mentioned that for the i.MX8 QXP the WiFi module Murata LBEE5XV1YM based on NXP88W8997 has been used for the tests mentioned in the document.

The question is, if I purchase the ST60-2230C WiFi module (due to availability reasons) will it work as "plug and play"?  (https://www.lairdconnect.com/wireless-modules/wifi-modules-bluetooth/60-2230c-series-bluetooth-and-w...)

Is the needed driver builded in the Embedded Linux for i.MX?

Is there any other WiFi module that is supported by the  Embedded Linux for i.MX and can be used to create WiFi AP?

[Christine_Li]

HI, @[Ungurean Marius-Constantin]​ On the page of 56 in L5.15.71_2.2.0_WIFI-Doc,it just lists the tested modules. It does not mean we only support these module. For other modules(used 88W8997), can also support L5.15.71_2.2.0, but not tested by our engineer. That's why we only list these in the L5.15.71_2.2.0_WIFI-Doc.

If you purchase the ST60-2230C Wi-Fi module (Because it is also use 88W8997 NXP Wi-Fi chip), it should also work well in L5.15.71_2.2.0. Is the needed driver built in the Embedded Linux for i.MX? ==>Yes, if you need this driver (Support L5.15.71_2.2.0), you can download it from our 88W8997 website. After login your account, choose "Design Resources", then click "Secure Files" in "Software" domain. 

Is there any other Wi-Fi module that is supported by the Embedded Linux for i.MX and can be used to create Wi-Fi AP? ==>There are also other Partner Modules which supported by the Embedded Linux for i.MX and can be used to create Wi-Fi AP. We also listed the modules on 88W8997 website. Please visit our website after login.

Not only for all 88W8997 modules but also other NXP Wi-Fi Chipsets(such as 88W9098, 88W8987, IW416, 88W8801 listed in this Doc:L5.15.71_2.2.0_WIFI-Doc), should support L5.15.71_2.2.0 once you download the correct Driver as mentioned above.

Best regards, Christine.

[MariusU]

Hello @Christine_Li , thank you for the help.

I do have some problems understanding your answer, for the question:

Q: "Is the needed driver built in the Embedded Linux for i.MX?"

Your answer is: "Yes, if you need this driver (Support L5.15.71_2.2.0), you can download it from our 88W8997 website."

So, is it build in the image provided in the Getting Started docu Linux 5.15.52_2.1.0? Can we use the wifi module without installing anything extra?

[Christine_Li]

HI, @MariusU 

I am so sorry about the confusion. Let me answer again in details.

Q: "Is the needed driver built in the Embedded Linux for i.MX?"

Answer: "Yes. In common, the related wi-fi driver will be built in the correct Embedded Linux version. If you download the chosen board full pre-built image from out website : Embedded Linux for i.MX Applications Processors, it will include related Linux version wi-fi driver. 

To confirm that, I downloaded  ​i.MX 8M Quad EVK​ prebuilt image (because I only have this board and 88W9098 wi-fi chip on my hand), and verified that can modprobe wi-fi driver successfully without install any extra anything. I believe you can also have a try with  i.MX 8QuadXPlus and ST60-2230C (NXP 88W8997 based) Wi-Fi module.

For your reference, what the command I used is: modprobe moal mod_para=nxp/wifi_mod_para.conf.

If you want to build the separate wi-fi Driver, you can also download the driver source code from our 88W8997 website and build it by yourself.

Hope it makes clear to you.

Best regards,

Christine.

[MariusU]

Hello @Christine_Li, 

We just received the ST60-2230C wifi board and tried it with the iMX8QXPMek board running Linux imx8qxpc0mek 5.15.52+g36363d8623ba. 

It failed to work, my steps exactly are:

1. Boot from emmc.
2. Login as root.
3. # modprobe moal mod_para=nxp/wifi_mod_para.conf
4. connmanctl
5. connmanctl > enable wifi -> This is outputing "wifi is not available"
6. connmanctl> services     -> This is showing only the eth0 interface. There is no mlan0 interface.

A full log can be visible in the attached iMX8QXP_MEK.txt file. 

@Christine_Li When you mentioned it worked with your setup, are you able to scan for WIFI devices using connmanctl > enable wifi and connmanctl > scan wifi ? 

Thank you, 

Marius

[Christine_Li]

HI,@MariusU

Your step looks fine.

But from your log, it looks like there is no Firmware in your board。

Please check below directory:

/lib/firmware/nxp

Theses should be WiFi/Bluetooth Firmware bin like below:

sdiouart8997_combo_v4.bin or pcieuart8997_combo_v4.bin (depends on your Wi-Fi module interface)

and 

wifi_mod_para.conf 

If you don't have, please put them(I attached) to this directory.

When you mentioned it worked with your setup, are you able to scan for WIFI devices using connmanctl > enable wifi and connmanctl > scan wifi ? 

==>Christine:Yes, I can. Please refer to the attached test results for detail logs on my local side with Linux kernel 5.15.52 on i.MX 8MQ and 88W9098 for reference.

Best regards,

Christine.

Best regards,

Christine.

[MariusU]

Hello @Christine_Li, @weidong_sun,

I have had another try with the ST60-2230P this time, the PCIe is detecting the module and I have the following output: 

root@imx8qxpmek:~# modprobe moal mod_para=nxp/wifi_mod_para.conf
[ 90.932459] mlan: loading out-of-tree module taints kernel.
[ 90.981728] wlan: Loading MWLAN driver
[ 90.986229] wlan: Register to Bus Driver...
[ 90.990889] wlan_pcie 0000:01:00.0: enabling device (0000 -> 0002)
[ 90.997338] Attach moal handle ops, card interface type: 0x204
[ 91.004503] PCIE8997: init module param from usr cfg
[ 91.009620] card_type: PCIE8997, config block: 0
[ 91.014293] cfg80211_wext=0xf
[ 91.017294] max_vir_bss=1
[ 91.019978] cal_data_cfg=none
[ 91.022985] ps_mode = 1
[ 91.025435] auto_ds = 1
[ 91.027919] host_mlme=enable
[ 91.030829] fw_name=nxp/pcieuart8997_combo_v4.bin
[ 91.035592] rx_work=1 cpu_num=4
[ 91.038790] Attach mlan adapter operations.card_type is 0x204.
[ 91.046794] Request firmware: nxp/pcieuart8997_combo_v4.bin
[ 91.081142] FW download over, size 0 bytes
[ 93.082353] FW failed to be active in time!
[ 93.086596] wlan_dnld_fw fail ret=0xffffffff
[ 93.090922] WLAN: Fail download FW with nowwait: 0
[ 93.096544] Config Space Registers:
[ 93.100081] reg:0x00 value=0x2b421b4b
[ 93.103774] reg:0x04 value=0x00100406
[ 93.107469] reg:0x10 value=0x7200000c
[ 93.111161] reg:0x18 value=0x7210000c
[ 93.114852] reg:0x2c value=0x00000000
[ 93.118547] reg:0x3c value=0x000001e8
[ 93.122215] reg:0x44 value=0x00000008
[ 93.125902] reg:0x80 value=0x10120040
[ 93.129626] reg:0x98 value=0x00000000
[ 93.133338] reg:0x170 value=0x0001001e
[ 93.137123] FW Scrach Registers:
[ 93.140398] reg:0xcf0 value=0xfedcba00
[ 93.144181] reg:0xcf8 value=0x0
[ 93.147352] reg:0xcfc value=0x0
[ 93.252415] reg:0xcf8 value=0x0
[ 93.255581] reg:0xcfc value=0x0
[ 93.360446] Interface registers dump from offset 0xc00 to 0xcfc
[ 93.366421] 00070621 00000000 c0000000 80000000 bd542000 00000000 00000000 00000000
[ 93.374204] 00000000 00000000 ffffffff 00000000 00000000 00000000 00000000 00000000
[ 93.381994] 00000000 00000000 00000472 000000e5 00000000 00000000 00001040 76543210
[ 93.389802] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 93.397604] a5a00420 040d1be0 01070f1a 5d7c0000 031f9121 00000000 000001e1 00000000
[ 93.405402] 00078120 00058110 00000000 00000000 00000000 00000000 00000000 00000000
[ 93.413214] 00010202 00000000 00000000 ffffffff 00800243 c8701424 00000000 00000000
[ 93.421008] 00000000 00000000 00000000 00000000 fedcba00 00000000 00000000 00000000
[ 93.428859] woal_request_fw failed
[ 93.432297] Firmware Init Failed
[ 93.438932] Free module params
[ 93.442109] woal_pcie_probe: failed
[ 93.445682] wlan_pcie: probe of 0000:01:00.0 failed with error -14
[ 93.452083] wlan: Register to Bus Driver Done
[ 93.456538] wlan: Driver loaded successfully
root@imx8qxpmek:~# lspci
00:00.0 PCI bridge: Freescale Semiconductor Inc Device 0000 (rev 01)
01:00.0 Ethernet controller: Marvell Technology Group Ltd. Device 2b42 (rev 11) 

Any Idea why do we get this error?

Thank you, 

Marius

[weidong_sun]

Dear @MariusU ,

Would you please check these 2 points?

1. If 8997 firmware is in /lib/firmare/nxp

pcieuart8997_combo_v4.bin , check it, please!

2. i.mx8qxp device tree.

See i.MX_Linux_Release_Notes.pdf ( linux bsp doc), please!

It mean that imx8qxp-mek-rpmsg.dtb should be used for 8997 PCIe WiFi.

Try it, please!

Thanks!

Regards,

weidong

[MariusU]

Hello @weidong_sun,

1) I have the 8997 firmware in /lib/firmware/nxp folder as you mentioned. I have tried using the one in place, replace it with the one from github link you send in the message earlier and even replacing with the one from @Christine_Li but the behaviour is the same: FW failed to be active in time!

2) Using the imx8qxp-mek-rpmsg.dtb seems to be even worse, the PCIe interface does not list any device anymore. I leave here a print of my Env from U-Boot:

U-Boot SPL 2022.04-lf_v2022.04+g1c881f4da8 (Jun 07 2022 - 05:16:02 +0000)
Normal Boot
Trying to boot from MMC2_2
Primary set selected
Load image from MMC/SD 0x63800

U-Boot 2022.04-lf_v2022.04+g1c881f4da8 (Jun 07 2022 - 05:16:02 +0000)

CPU: NXP i.MX8QXP RevB A35 at 1200 MHz at 21C

Model: NXP i.MX8QXP MEK
Board: iMX8QXP MEK
Boot: SD1
DRAM: 3 GiB
TCPC: Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C1 0x50]
Core: 257 devices, 28 uclasses, devicetree: separate
MMC: FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from MMC... OK
[*]-Video Link 0it6263_i2c_reg_read, read err 3
faill to read from it6263 revision, ret 3
(1280 x 720)
[0] dpu@56180000, video
[1] lvds-channel@0, display
[2] lvds-to-hdmi-bridge@4c, video_bridge
In: serial
Out: serial
Err: serial

BuildInfo:
- SCFW 8172eaea, SECO-FW c9de51c0, IMX-MKIMAGE a8bb8edb, ATF c6a19b1
- U-Boot 2022.04-lf_v2022.04+g1c881f4da8

switch to partitions #0, OK
mmc1 is current device
flash target is MMC:1
Net: eth0: ethernet@5b040000 [PRIME], eth1: ethernet@5b050000
Fastboot: Normal
Normal Boot
Hit any key to stop autoboot: 0
=> printenv
auth_os=auth_cntr ${cntr_addr}
baudrate=115200
board_name=MEK
board_rev=iMX8QXP
boot_fdt=try
boot_os=booti ${loadaddr} - ${fdt_addr};
bootcmd=mmc dev ${mmcdev}; if mmc rescan; then if run loadbootscript; then run bootscript; else if test ${sec_boot} = yes; then if run loadcntr; then run mmcboot; else run netboot; fi; else if run loadimage; then run mmcboot; else run netboot; fi; fi; fi; else booti ${loadaddr} - ${fdt_addr}; fi
bootcmd_mfg=run mfgtool_args;if iminfo ${initrd_addr}; then if test ${tee} = yes; then bootm ${tee_addr} ${initrd_addr} ${fdt_addr}; else booti ${loadaddr} ${initrd_addr} ${fdt_addr}; fi; else echo "Run fastboot ..."; fastboot auto; fi;
bootdelay=3
bootscript=echo Running bootscript from mmc ...; source
cntr_addr=0x98000000
cntr_file=os_cntr_signed.bin
commit_atf=c6a19b1
commit_mkimage=a8bb8edb
commit_scfw=8172eaea
commit_secofw=c9de51c0
console=ttyLP0
dom0fdt_file=imx8qxp-mek-dom0.dtb
emmc_dev=0
eth1addr=fe:13:4c:d0:a9:4e
ethact=ethernet@5b040000
ethaddr=00:04:9f:05:c8:82
ethprime=eth0
fastboot_dev=mmc1
fdt_addr=0x83000000
fdt_file=imx8qxp-mek-rpmsg.dtb
fdt_high=0xffffffffffffffff
fdtcontroladdr=fb203a10
image=Image
initrd_addr=0x83100000
initrd_high=0xffffffffffffffff
jh_mmcboot=setenv fdt_file imx8qxp-mek-root.dtb;setenv boot_os 'scu_rm dtb ${fdt_addr}; booti ${loadaddr} - ${fdt_addr};'; run mmcboot;
jh_netboot=setenv fdt_file imx8qxp-mek-root.dtb;setenv boot_os 'scu_rm dtb ${fdt_addr}; booti ${loadaddr} - ${fdt_addr};'; run netboot;
kboot=booti
loadaddr=0x80200000
loadbootscript=fatload mmc ${mmcdev}:${mmcpart} ${loadaddr} ${script};
loadcntr=fatload mmc ${mmcdev}:${mmcpart} ${cntr_addr} ${cntr_file}
loadfdt=fatload mmc ${mmcdev}:${mmcpart} ${fdt_addr} ${fdt_file}
loadimage=fatload mmc ${mmcdev}:${mmcpart} ${loadaddr} ${image}
loadm4image_0=fatload mmc ${mmcdev}:${mmcpart} ${loadaddr} ${m4_0_image}
m4_0_image=m4_0.bin
m4boot_0=run loadm4image_0; dcache flush; bootaux ${loadaddr} 0
mfgtool_args=setenv bootargs console=${console},${baudrate} rdinit=/linuxrc clk_ignore_unused
mmcargs=setenv bootargs console=${console},${baudrate} earlycon root=${mmcroot}
mmcautodetect=yes
mmcboot=echo Booting from mmc ...; run mmcargs; if test ${sec_boot} = yes; then if run auth_os; then run boot_os; else echo ERR: failed to authenticate; fi; else if test ${boot_fdt} = yes || test ${boot_fdt} = try; then if run loadfdt; then run boot_os; else echo WARN: Cannot load the DT; fi; else echo wait for boot; fi;fi;
mmcdev=1
mmcpart=1
mmcroot=/dev/mmcblk1p2 rootwait rw
nandfit_part=yes
netargs=setenv bootargs console=${console},${baudrate} earlycon root=/dev/nfs ip=dhcp nfsroot=${serverip}:${nfsroot},v3,tcp
netboot=echo Booting from net ...; run netargs; if test ${ip_dyn} = yes; then setenv get_cmd dhcp; else setenv get_cmd tftp; fi; if test ${sec_boot} = yes; then ${get_cmd} ${cntr_addr} ${cntr_file}; if run auth_os; then run boot_os; else echo ERR: failed to authenticate; fi; else ${get_cmd} ${loadaddr} ${image}; if test ${boot_fdt} = yes || test ${boot_fdt} = try; then if ${get_cmd} ${fdt_addr} ${fdt_file}; then run boot_os; else echo WARN: Cannot load the DT; fi; else booti; fi;fi;
script=boot.scr
sd_dev=1
sec_boot=no
serial#=1c18680e82963f70
soc_rev=revb
soc_type=imx8qxp
splashimage=0x9e000000
xenboot_common=${get_cmd} ${loadaddr} xen;${get_cmd} ${fdt_addr} ${dom0fdt_file};${get_cmd} ${xenlinux_addr} ${image};fdt addr ${fdt_addr};fdt resize 256;fdt set /chosen/module@0 reg <0x00000000 ${xenlinux_addr} 0x00000000 0x${filesize}>; fdt set /chosen/module@0 bootargs "${bootargs} ${xenlinux_bootargs}"; setenv bootargs ${xenhyper_bootargs};booti ${loadaddr} - ${fdt_addr};
xenhyper_bootargs=console=dtuart dtuart=/serial@5a060000 dom0_mem=1024M dom0_max_vcpus=2 dom0_vcpus_pin=true
xenlinux_addr=0x9e000000
xenlinux_bootargs=
xenlinux_console=hvc0 earlycon=xen
xenmmcboot=setenv get_cmd "fatload mmc ${mmcdev}:${mmcpart}";setenv console ${xenlinux_console};run mmcargs;run xenboot_common;
xennetboot=setenv get_cmd dhcp;setenv console ${xenlinux_console};run netargs;run xenboot_common;

Environment size: 4057/8188 bytes

[weidong_sun]

Dear @MariusU ,

checked the datasheet of your module. Let me paste it here.

ST60-2230C is SDIO for wifi, and UART for BT. Very strange, they don't have PCIe for WIFI module.

sorry! my mistake!, it is not PCIE ,for ST60-2230C, 88W8997 SDIO wifi firmware can be downloaded here:

https://github.com/nxp-imx/imx-firmware/tree/lf-5.15.71_2.2.0/nxp

Then please check if sdiouart8997_combo_v4.bin is in /lib/firmware/nxp

if not, download it and copy it to the path.

Last step. I don't know if you are using i.MX8QXP-EVK board, if yes, SDIO interface is not supported on M.2 KEY E connector. See below, please!

[Note]

If your board is customized based on i.MX8QXP, you also need to check if SDIO signals are wired to M.2 connector.

Regards,

weidong

[MariusU]

Hello @weidong_sun,

I'm not using the ST60-2230C-U anylonger, I have bought the ST60-2230C-P, this last trieouts were performed on this last one which, according to datashet, is based on PCIe and UART.

I am using the iMX8QXP B0 Mek (https://www.nxp.com/design/development-boards/i-mx-evaluation-and-development-boards/i-mx-8quadxplus...)

[weidong_sun]

Dear @MariusU ,

1. Are you sure that ST60-2230C-P is based 88W8997 PCIe & UART?

2. Do you have these 2 doc ?

--i.MX_Linux_Release_Notes.pdf

--i.MX_Linux_Users_Guide.pdf

If you have these 2 docs, check above , please!

It means that default linux bsp you are using supports 88W8997 . you only need to run:

# modprobe moal mod_para=nxp/wifi_mod_para.conf

wifi driver will be loaded successfully. don't need to other steps.

Regards,

weidong

[MariusU]

Hello @weidong_sun,

1) Yes, as you can see in the picture below, from https://ro.mouser.com/datasheet/2/986/CS_DS_ST60_2230C_P_ST60_2230C_PU_v1_14-1894142.pdf:

2) With the *_rpmsg.dtb the device is not even recognized:

I have read the two documents, I don't know if I'm missing something but the command

modprobe moal mod_para=nxp/wifi_mod_para.conf

seem to load the driver only when using the default imx8qxp-mek.dtb and then it give the firmware problem FW failed to be active in time!

What could be the reason for this problem? Since the /lib/firmware/nxp has the specified driver:

Is there any posibility for a Support meeting on Teams/Zoom/Other for a live ?

Thank you, 

Marius

[weidong_sun]

Hello @MariusU ,

Could you run lspci command to check if pcie wifi can be found by linux?

Regards,

weidong

[MariusU]

Hello @weidong_sun ,

1) Using the *_rpmsg.dtb there is nothing shown when lspci.

2) Using the imx8qxp-mek.dtb:

This imx8qxp-mek.dtb is also the only *.dtb that manages to reach the firmware load phase and generates the: 

[ 91.038790] Attach mlan adapter operations.card_type is 0x204.
[ 91.046794] Request firmware: nxp/pcieuart8997_combo_v4.bin
[ 91.081142] FW download over, size 0 bytes
[ 93.082353] FW failed to be active in time!
[ 93.086596] wlan_dnld_fw fail ret=0xffffffff
[ 93.090922] WLAN: Fail download FW with nowwait: 0

Regards,

Marius

[weidong_sun]

Hello @MariusU ,

Do you have any other i.MX platform? if yes, could you test the wifi module on other platform?

Regards,

weidong

[MariusU]

Hello @weidong_sun,

Unfortunately, I do not have other iMX platform at this time, the availability to buy is limited at this moment in EMEA. 

When I run the pci command in U-boot there is a message related to "disable-gpio", coud this affect the loading of the WiFi firmware?

Regards,

Marius

[weidong_sun · Accepted solution]

Hello @MariusU ,

your i.mx8qxp-evk board is B0 version,  but 5.15.71 bsp is only C0 version.

please use 5.15.52 or 5.10.72 linux bsp!

B0 version is supported in these 2 versions of bsp.

Regards,

weidong

[MariusU]

Hello @weidong_sun,

You are absolutely right, our board version is B0 and 5.10.72-lts-5.10.y+g06213bb0115f seems to solve the strange behavior.

The driver is now able to load the WiFi module firmware and I can connect to a wifi network.

Thank you for the time spent to help us!

Marius

[Christine_Li]

Hi, @MariusU 

Thanks for your feedback.

Sounds great!

Then let's close this case and not make other updates here any more.

If you have any other questions, please feel free to create new case to us.

Have a good day!

Best regards,

Christine.

[MariusU]

Hello @Christine_Li,

First of all I want to thank you for the time spent to help us, you have been really helpfull.

The firmwares are in place, in the /lib/firmware/nxp. I even comared the with the ones you sent and are the same, including the .conf file.

The problem seems to be at the PCIE side:

root@imx8qxpc0mek:~# dmesg | grep pcie
[ 3.089637] imx6q-pcie 5f010000.pcie: supply epdev_on not found, using dummy regulator
[ 3.097966] imx6q-pcie 5f010000.pcie: No cache used with register defaults set!
[ 3.147992] imx6q-pcie 5f010000.pcie: PCIe PLL is locked.
[ 3.153838] imx6q-pcie 5f010000.pcie: iATU unroll: disabled
[ 3.167595] imx6q-pcie 5f010000.pcie: Detected iATU regions: 6 outbound, 6 inbound
[ 3.167611] imx6q-pcie 5f010000.pcie: host bridge /bus@5f000000/pcie@0x5f010000 ranges:
[ 3.183675] imx6q-pcie 5f010000.pcie: IO 0x007ff80000..0x007ff8ffff -> 0x0000000000
[ 3.202725] imx6q-pcie 5f010000.pcie: MEM 0x0070000000..0x007fefffff -> 0x0070000000
[ 3.219357] imx6q-pcie 5f010000.pcie: iATU unroll: disabled
[ 3.240867] imx6q-pcie 5f010000.pcie: Detected iATU regions: 6 outbound, 6 inbound
[ 4.244073] imx6q-pcie 5f010000.pcie: Phy link never came up
[ 4.250937] imx6q-pcie: probe of 5f010000.pcie failed with error -110
root@imx8qxpc0mek:~# mx6q-pcie 5f010000.pcie: Detected iATU regions: 6 outbound, 6 inbound

Could it be because of this?

## Flattened Device Tree blob at 83000000
Booting using the fdt blob at 0x83000000
ERROR: reserving fdt memory region failed (addr=90400000 size=100000 flags=4)
Using Device Tree in place at 0000000083000000, end 000000008301b707
Disable clock-controller@585a0000 rsrc 411 not owned
Disable clock-controller@5a4d0000 rsrc 62 not owned
Disable clock-controller@5ac90000 rsrc 102 not owned

Is there another way to force the PCIe interface up?

Your help is much appreciated!

Marius