Colibri iMX8 v1.0B: core-image-full-cmdline with wifi support

Technical Support
, , , ,
1

I build the fsl-image successfully with this article and were able to connect to a wifi network with connmanctl (link).

Then I tried the same with the ‘core-image-full-cmdline’ (path: \sources\poky\meta\recipes-extended\images). Therefore I modified the recipe like this:

DESCRIPTION = "A console-only image with more full-featured Linux system \
functionality installed."

IMAGE_FEATURES += "splash ssh-server-openssh"

IMAGE_INSTALL = "\
    packagegroup-core-boot \
    packagegroup-core-full-cmdline \
    connman \
    connman-client \
    linux-firmware-pcie8997 \
	openssh-sftp-server \
    ${CORE_IMAGE_EXTRA_INSTALL} \
    "

inherit core-image

I build the image with

MACHINE=colibri-imx8qxp DISTRO=fsl-imx-xwayland source fsl-setup-release.sh -b build
bitbake -k core-image-full-cmdline

The build was successfull and it booted.

But when I tried to connect to a wifi network I got the following error message:

root@colibri-imx8qxp:~# connmanctl enable wifi
Error wifi: Method "SetProperty" with signature "sv" on interface "net.connman.Technology" doesn't exist

What did I miss?

2

hi @Mowlwurf

Could you provide the dmesg log and the output of ‘lsmod’ in a file?

Thanks and best regards,
Jaski

3

Here is the dmesg log file: dmesg log file

The output of ‘lsmod’ is just

Module                  Size  Used by

and nothing more.

Best regards,
Mowlwurf

4

Hi @Mowlwurf

You need to add at least the following to the .bb file.

${@bb.utils.contains("DISTRO_FEATURES", "wifi", "packagegroup-base-wifi", "", d)} \

I tested this with the following additional package added:

packagegroup-base \
packagegroup-distro-base \  	
packagegroup-machine-base \

And the built core-image-full-cmdline had the wifi support.

As alternative, I suggest to check out the Bsp 3.0 branch and build the console image. This image will be one of our regular Bsp Image in the Future and thus you will get better Support for this.

Best regards,
Jaski

5

Thank you for your response,

yes, I got wifi support too. But when I try to connect to a network I got an error scanning for wifi:

root@colibri-imx8qxp:~# connmanctl
connmanctl> enable wifi
Enabled wifi
connmanctl> scan wifi
Scan completed for wifi
connmanctl> [  276.774192] ieee80211 phy0: mwifiex_cfg80211_sched_scan_start : Invalid Sched_scan parameters

Any idea what can be the cause for this?

Best regards,
Mowlwurf

6

You are welcome.

Concerning your issue, this is just a debug message.

Are you able to connect to the Wifi router or access-point.?

7

Sorry for my late reply. It didn’t get a notification of your comment.

I was able to connect to my access-point, thank you again for your help

8

Perfect that it works. Thanks for the feedback.

9

I see this solution and I would like to use it. Do I simply copy and paste this line into my core-image-full-cmdline.bb file? Can you provide the full file used?

10

Well, this was more than two and a half year ago. I don’t remember exactly what I did that made it work but here is the .bb-file that must be the right one:

DESCRIPTION = "A console-only image with more full-featured Linux system \
functionality installed."

inherit core-image

CONMANPKGS ?= "\
	connman \
	connman-plugin-loopback \
	connman-plugin-ethernet \
	connman-plugin-wifi \
	connman-client"

IMAGE_FEATURES += "\
	splash \
	ssh-server-openssh \
	"

IMAGE_INSTALL = "\
    packagegroup-core-boot \
    packagegroup-core-full-cmdline \
    ${CORE_IMAGE_EXTRA_INSTALL} \
	\
    ${CONMANPKGS} \
	nano \
	openssh-sftp-server \
    "
11

Thank you so much! This is very helpful. Adding this to my build has allowed me to run the “connmanctl enable wifi” command.

12

Last question, is there a way to make these changes in the local.conf rather than a remote git controlled repo?

13

Unfortunately, I am not sure about that. Perhaps someone from Toradex can provide information?

14

Hi @MichaelBMiner ,

The code above is meant to be a recipe (for a custom distro / image), so it should be among other recipes inside the layers. So you should not have this on your local.conf.

Although not mandatory, we recommend using a versioning tool like Git to keep track of changes during development as well as for maintenance purposes.

Best Regards
Kevin