Hi there,
I am in the process of creating a custom machine for the STM32MP257F-DK board following this Wiki guide. After following the necessary steps, I can successfully bitbake st-image-weston with my CubeMX-generated device tree files.
I am hitting an issue where updates to my device tree source (within the mx/ directory in the meta-st-stm32mp-addons layer) are typically not reflected in the output image. As a simple test, I am changing the model name then running bitbake st-image-weston. It looks as if bitbake does carry out some recompile/configure of linux-stm32mp but after updating the board (using the flash-layout-x-.tsv). The model name change is not reflected.
This sounds similar to an issue mentioned in this post. As suggested, I have confirmed the #@NAME: variable reflects my custom machine name and have tried forcing a rebuild with:
bitbake linux-stm32mp -c cleanall
bitbake linux-stm32mp
bitbake st-image-weston
Very occasionally, changes to the kernel dts have been correctly reflected when re-running bitbake. But I cannot seem to find what actually causes the changes to be correctly updated.
For reference, I have attached my machine.conf and my directory structure within the addons layer is as follows:
mx
└── custom
├── CA35
│ ├── DeviceTree
│ │ └── custom
│ │ ├── kernel
│ │ │ ├── Makefile
│ │ │ ├── stm32mp257f-custom-mx.dts
│ │ │ └── stm32mp257f-custom-mx-resmem.dtsi
│ │ ├── optee-os
│ │ │ ├── conf.mk
│ │ │ ├── stm32mp257f-custom-mx.dts
│ │ │ ├── stm32mp257f-custom-mx-rcc.dtsi
│ │ │ ├── stm32mp257f-custom-mx-resmem.dtsi
│ │ │ └── stm32mp257f-custom-mx-rif.dtsi
│ │ ├── tf-a
│ │ │ ├── stm32mp257f-custom-mx.dts
│ │ │ ├── stm32mp257f-custom-mx-fw-config.dts
│ │ │ ├── stm32mp257f-custom-mx-rcc.dtsi
│ │ │ └── stm32mp25-mx.dtsi
│ │ └── u-boot
│ │ ├── Makefile
│ │ ├── stm32mp257f-custom-mx.dtb
│ │ ├── stm32mp257f-custom-mx.dts
│ │ ├── stm32mp257f-custom-mx-resmem.dtsi
│ │ └── stm32mp257f-custom-mx-u-boot.dtsi
│ └── manifest.prop
Any guidance/help would be greatly appreciated!
Thanks.
