i.MX ProcessorsのトピックRe: IMX8QXP-MEK laird WiFi module integration issues.

IMX8QXP-MEK laird WiFi module integration issues.

jakos — Thu, 19 Nov 2020 10:39:16 GMT

Hi,

As a proof of concept of our project we are using IMX8QXP-MEK board. We are using Yocto as build system and managed to launch core-image-base onto the target with no issues (DISTRO=fsl-imx-wayland and imx8qxp-mek-root.dtb). Now, what we are struggling to launch is st60-2230c wi-fi module (i know that NXP supports Murata, but my supervisors chose this module, so I have to make it work :)). I would like to point out that i am not an expert in integrating of such modules with Linux.

From what I've seen there are no drivers for laird modules in kernel 5.4, only generic Marvel 88W8997 driver. Loading it from menuconfig did not do the trick. I've also loaded kernel-module-pcie8997 present in meta-img/meta-bsp/recipes-kernel/kernel-modules. Upon loading them from within linux system there was no wlan present.

Integration with the use of this guide:

https://www.mouser.com/pdfDocs/CS-AN-ST60-BackportsIntegrationv1_0.pdf

Has lead me to an error:

make: *** [Makefile:41: defconfig-sterling60] Error 1
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.
| ERROR: Execution of '/mnt/Yocto/imx-yocto-bsp/build/tmp/work/imx8qxpmek-poky-linux/sterling-backports-laird/8.2.0.17-r0/temp/run.do_compile.2253815' failed with exit code 1:
| /--------------
| | Your kernel headers are incomplete/not installed.
| | Please install kernel headers, including a .config
| | file or use the KLIB/KLIB_BUILD make variables to
| | set the kernel to build against, e.g.
| | make KLIB=/lib/modules/3.1.7/
| | to compile/install for the installed kernel 3.1.7
| | (that isn't currently running.)
| \--
| make: *** [Makefile:41: defconfig-sterling60] Error 1
| WARNING: exit code 1 from a shell command.

Then I've tried to simply integrate laird's layer to my build system:

https://github.com/LairdCP/meta-laird-cp

This lead me to another error:

he recipe sterling-backports-laird is trying to install files into a shared area when those files already exist. Those files and their manifest location are:
/mnt/Yocto/imx-yocto-bsp/build/tmp/pkgdata/imx8qxpmek/runtime/kernel-module-btusb-5.4.47-2.2.0+g5ec03d06f54e.packaged
(matched in manifest-imx8qxpmek-linux-imx.packagedata)
/mnt/Yocto/imx-yocto-bsp/build/tmp/pkgdata/imx8qxpmek/runtime/kernel-module-btusb-5.4.47-2.2.0+g5ec03d06f54e
(matched in manifest-imx8qxpmek-linux-imx.packagedata)
Please verify which recipe should provide the above files.

I've tried to remove "wifi bluetooth" options from configuration files as well as kernel modules that come with meta-imx to hopefully exlude kernel-module-btusb.

README section of meta-laird-cp states:

   1. Remove cfg80211 and mac80211 from the kernel config
   2. Explicitly add the cfg80211 and mac80211 dependencies to the kernel config

I am however not sure what it means, how does one "explicitly add kernel config ?" -> for now it is chosen with make menuconfig.

Could any option chosen in kernel config interfere with this build ?

Does anyone have any experience with integration of such modules and could point me in the right direction?

Re: IMX8QXP-MEK laird WiFi module integration issues.

igorpadykov — Mon, 23 Nov 2020 08:44:36 GMT

Hi jakub_kostiw

one can look at below links describing how add additional drivers to image :

https://community.nxp.com/t5/i-MX-Processors-Knowledge-Base/i-MX-Yocto-Project-How-can-I-quickly-modify-the-kernel-and-test/ta-p/1129551

https://community.nxp.com/t5/i-MX-Processors-Knowledge-Base/Task-10-How-to-create-a-custom-layer/ta-p/1121982

In general wifi porting guidelines should be provided by wifi vendor, so recommended to apply to laird

for additional support.

Best regards
igor

Re: IMX8QXP-MEK laird WiFi module integration issues.

johnnosky — Thu, 07 Jan 2021 17:16:31 GMT

Hi jakub_kostiw,

John from Laird Connectivity here. Looks like you need to reconfigure your kernel and then recompile/redeploy. To do this, simply run bitbake -c menuconfig virtual/kernel and perform the following:

Go to Device Drivers ---> Network device support --->
Deselect [ ] Wireless LAN ----
Go back to the main menu
Go to Networking support --->
Deselect < > Bluetooth subsystem support ----
Deselect [ ] Wireless ----
Go back to the main menu
Use search (forward slash '/' key) and select the following (if the other systems were selected, these are most likely still selected):
CRYPTO_SHA256
CRYPTO_ARC4
CRYPTO_AES
CRYPTO_CCM
CRYPTO_GCM
CRYPTO_CMAC
CRC32
CRYPTO_ECDH
CRYPTO_ECB
CRC16
CRYPTO_BLKCIPHER

After this, save and exit menuconfig then:

bitbake -c compile virtual/kernel -f

bitbake -c deploy virtual/kernel

At this point you can build backports. Apologies for that document, it is out of date and I am working on updating it. If you need further support, please reach out to us through our support portal (use the "Open a Support Ticket" button at the bottom):

https://www.lairdconnect.com/resources/support