2025-03-06 9:38 AM
Hello,
If I put my new machine conf and device tree in meta-st-stm32mp-addons I can compile device tree and my image without any error.
But if I use my own layer meta-my-layer (in meta-st), machine config is used but I have this message : | make[2]: *** No rule to make target 'arch/arm/boot/dts/st/stm32mp153c-linux-platform-mx.dtb'. Stop.
I read the forum and documentation but, I don't find a way to have a working project.
Could you explain me how to create my own layer to be outside meta-st-stm32mp-addons (to use my own git) and compile my new machine with associated device tree ?
Thank you so much for your help
Solved! Go to Solution.
2025-03-07 9:54 AM - edited 2025-03-07 9:55 AM
Hello,
My bad, I read lot of time these documentation but I forgot to add meta-st-stm32mp-addons into NEEDED_BSPLAYERS
#@NEEDED_BSPLAYERS: layers/meta-openembedded/meta-oe layers/meta-openembedded/meta-python layers/meta-st/meta-st-stm32mp-addons
It works fine now.
Thank you and sorry for inconvenience.
Best regards,
2025-03-07 1:24 AM
Hello @JMD ,
Is it possible for you to provide a kind of tree of your Yocto layer here (with folders, subfolders) to check the architecture of your Yocto layer ?
If sensitive information are inside, maybe you can filter or replace by a tag the sensitive file names / information.
I guess you are already aware about this article:
Did you take the same architecture than the addons layer ? Are you able to source your own MACHINE ? Do you well have your Yocto layer inside the Yocto BUILD path ?
Kind regards,
Erwan.
2025-03-07 9:54 AM - edited 2025-03-07 9:55 AM
Hello,
My bad, I read lot of time these documentation but I forgot to add meta-st-stm32mp-addons into NEEDED_BSPLAYERS
#@NEEDED_BSPLAYERS: layers/meta-openembedded/meta-oe layers/meta-openembedded/meta-python layers/meta-st/meta-st-stm32mp-addons
It works fine now.
Thank you and sorry for inconvenience.
Best regards,