2021-06-02 02:39 AM
I'm trying to edit the device tree of the distribution but there is no .dts or .dtsi files in all the distribution package directories. The only way I found to experiment modifying the device tree is doing it with developper package (I modified stm32mp157c-dk2.dts) but I now must add it to the distribution and I'm still not able to force bitbake to generate any dts file.
How can I do it.
Thank you in advance.
Solved! Go to Solution.
2021-06-03 01:27 AM
Hi @BJola.1 , @Jean-Marc B
I agree not obvious but the most pertinent link to integrate CubeMX generated DT in distribution package is this one
https://wiki.st.com/stm32mpu/wiki/How_to_create_your_own_machine
Hope it help
Olivier
2021-06-02 03:28 AM
Hello @BJola.1
Could this wiki page may help you https://wiki.st.com/stm32mpu/wiki/How_to_compile_the_device_tree_with_the_Developer_Package ?
Best regards,
--JM
2021-06-02 04:34 AM
Hello !
Sorry but no, because as I said I've already been able to do it in developer package. Now what I need is to integrate my modifications in the distribution by patching the dts file source of the kernel recipe. To patch the sources I need it to be be generated somewhere in the distribution directories. In other pages of the stm32mpu wiki it is said that thoose files should be in the directories after running bitbake st-image-weston, but it wasn't.
But I just found out that it's possible to do it with devtool so I'm trying to do it. ( https://wiki.st.com/stm32mpu/wiki/How_to_cross-compile_with_the_Distribution_Package#Modifying_the_Linux_kernel_device_tree )
After that I'll need to create a patch and apply it somehow when building the distribution. So if you have other advices I'm still trying to find out.
Thank you for your help.
2021-06-02 05:16 AM
Hi @BJola.1
I am sorry for the wrong piece of advices.
I have a project with a patched dts file. As I am not an expert about this topic, I don't know if this is the right way to do it. Maybe another contributor may better advise you.
So after creating a patch of your dts file, let's say 00<num>-this-is-my-patch.patch, copy it into the sub-directory recipes-kernel/linux/linux-stm32mp/5.4/5.4.56 in the layer meta-st/meta-st-stm32mp1. Then still in this layer, create the recipe recipes-kernel/linux/linux-stm32mp_5.4.bbappend with a similar code:
SRC_URI += "file://${LINUX_VERSION}/${LINUX_VERSION}.${LINUX_SUBVERSION}/00<num>-this-is-my-patch.patch"
As said, take it as a work-around before confirmed by an expert.
Best regards,
--JM
2021-06-02 05:51 AM
No problem.
Thank you, I'll try that.
Best regards
2021-06-03 01:27 AM
Hi @BJola.1 , @Jean-Marc B
I agree not obvious but the most pertinent link to integrate CubeMX generated DT in distribution package is this one
https://wiki.st.com/stm32mpu/wiki/How_to_create_your_own_machine
Hope it help
Olivier
2021-06-03 01:59 AM
Thanks,
I'm not modifying the DT with CubeMX but still it gave informations about how to make it correctly.
For now I used that bbappend in my layer with the patch in a directory next to the bbappend.
in linux-stm32mp_5.10.bbappend with the patch in linux-stm32mp directory
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
SRC_URI += "file://0001-ajout-de-la-PWM-sur-PE9-au-device-tree.patch"
But that's temporary, I'll use your informations to make it in a proper way.
Thank you and have a nice day.