Hello world custom kernel module error

Hello all,

I am trying tu add a custom kernel module to my Boot2Qt image and so I am following these instructions to add an hello-world module

But when I am running

bitbake b2qt-embedded-qt5-image
bitbake hello-mod

I am getting this following error

ERROR: hello-mod-1.0-r0 do_package: QA Issue: hello-mod: Files/directories were installed but not shipped in any package:
Please set FILES such that these items are packaged. Alternatively if they are unneeded, avoid installing them or delete them within do_install.
hello-mod: 4 installed and not shipped files. [installed-vs-shipped]
ERROR: hello-mod-1.0-r0 do_package: Fatal QA errors found, failing task.
ERROR: Logfile of failure stored in: /home/inno-dev/BuildDir/VOH_OS/build-apalis-imx8/tmp/work/apalis_imx8-poky-linux/hello-mod/1.0-r0/temp/log.do_package.260735
ERROR: Task (/home/inno-dev/BuildDir/VOH_OS/sources/meta-voh/recipes-kernel/hello-mod/hello-mod_1.0.bb:do_package) failed with exit code ‘1’

What am I missing here?

Thanks for your help.


When running

export MACHINE=apalis-imx8
source ./setup-environment.sh
bitbake hello-mod

I’ve got the error. But when running

export MACHINE=raspberrypi4
source ./setup-environment.sh
bitbake hello-mod

Everything works fine. So could it be that there is a configuration error with the imx-8 ?


Dear @Romain.Donze,

Can you please give us more information?

From where did you get the setup-environment.sh? Here on toradex we use . export as shown here: Build a Reference Image with Yocto Project/OpenEmbedded | Toradex Developer Center. You could also have a look on this page: Qt for Device Creation (Boot to Qt) | Toradex Developer Center

Also, I’d guess that for Raspberry the QA is not enabled. You could have a look here to understand more what that means: 9 QA Error and Warning Messages — The Yocto Project ® 4.0.1 documentation

Have you made any custom recipe? If yes, could you please share with us?

Best regards,


Thank you for your quick reply.

After some thinking and testing and with the rapsberry build working flawlessly, I went and did a complete clean and rebuild the complete image overnight and it worked.

I think I might had some corrupted files in my old build.

Everything seems fine now

1 Like