Hi @Merlin ,
Can you check if you have any layer activated that has in the kernel recipes something like you can see here:
/path/layers$ rg nxp89xx
meta-toradex-nxp/recipes-kernel/linux-firmware/linux-firmware_%.bbappend
PACKAGES =+ " ${PN}-nxp89xx"
FILES_${PN}-nxp89xx = " \
This seems to be the recipe that adds the nxp89xx as a possible target. If you have a document with this, you should check if the layer is activated in the bblayers.conf of your Yocto Build.
Best regards,
Guilherme
Hi @gclaudino.tx !
rg nxp89xx
did not provide any result.
Is it possible to create a .bbappend recipes in my meta adding nxp89xx as possible target?
How is it possible that I can’t find nxp89xx in my /layer folder?
Merlin
Hi @Merlin ,
Can you please check the recipes-kernel on our meta-toradex-nxp repository recipes-kernel - meta-toradex-nxp.git - Toradex BSP layer, recipes for NXP based modules ? There you can find how we made it and so that you can adapt it to your recipe.
This repository is usually downloaded when you do the first repo sync following this article: Build a Reference Image with Yocto Project/OpenEmbedded | Toradex Developer Center .
Please tell me if this helps you.
Best regards,
Guilherme
Hi @gclaudino.tx !
As you can see in the attached image I don’t have linux-firmware in the folder.
I followed the instruction in the article you sent me but it’s been a long time i did it.
Do you think I have to update my meta?
I’m a bit afraid of lose my job XD.
Maybe I can back-up my environment and the I can try to update my meta.
Merlin
Hi @Merlin ,
You can download the new files from the link I just sent and add them to your recipes-kernel folder. Adding the linux-firmware folder shall be enough. Please do it and try again 
.
Remember to check on your bblayers.conf that meta-toradex-nxp is listed.
Best regards,
Guilherme
Hi @gclaudino.tx ,
I thought it was bettere to sync on your HEAD revision, in this way my environment and yours are identical.
I did the bitbake of my image but I still can’t see Wifi (and bluetooth) when I run
connmanctl technologies
Running
ls /sys/bus/pci/drivers
now I can see mwifiex_pcie .
Is it possible for you to send me the chelt.bb file you used and let you use the wifi interface please?
I think everything is ok in kernel .config so the problem should be in the .bb file
The error I get is always the same:
root@localhost:~# dmesg | grep wifi
[ 1.289681] mwifiex_pcie 0000:01:00.0: enabling device (0000 -> 0002)
[ 1.289797] mwifiex_pcie: PCI memory map Virt0: 000000001b02f1b5 PCI memory map Virt2: 0000000022b9d5b0
[ 1.290314] mwifiex_pcie 0000:01:00.0: Direct firmware load for mrvl/pcieusb8997_combo_v4.bin failed with error -2
[ 1.290323] mwifiex_pcie 0000:01:00.0: Failed to get firmware mrvl/pcieusb8997_combo_v4.bin
[ 1.290328] mwifiex_pcie 0000:01:00.0: info: _mwifiex_fw_dpc: unregister device
[ 1.290408] mwifiex_pcie 0000:01:00.0: performing cancel_work_sync()...
[ 1.290417] mwifiex_pcie 0000:01:00.0: cancel_work_sync() done
Merlin
Hi guys,
I compared the .config got from Toradex Multimedia Image with mine.
In my configuration I moved some option from ‘y’ to ‘m’ as your .config (I swear this is the only change I did), I compiled the kernel and flash it to my system.
Now the wifi works!
I am a bit confused honestly, but it seems we reached the target XD
Thank for your support.
Merlin
Hi @Merlin ,
I’m glad the wifi works for you now. Can you please mark the post as solved then? I’ll just add a few comments about the things you said.
Indeed it would be better to sync it using git commands such as clone to get the most updated version from our branch and check it time by time using git status.
Do you think you’d still need it? I didn’t sent it to you as I had just added those few lines and had to remove the ones from your application.
Indeed this could be giving additional problems.
If there is anything else that we can do for you don’t hesitate in contacting us.
Best regards,
Guilherme