2025-11-13 8:46 AM - last edited on 2025-11-13 9:07 AM by Andrew Neil
Hello,
I am working on STM32MP2 using the OpenSTLinux Weston distro and I am modifying the OP-TEE/device-tree files under the external-dt workspace using devtool.
I need to remove a pin definition from the CA35 OP-TEE DTS files, but even after rebuilding the image, the pin still appears in the running system:
This means my change was not applied.
Files I modified and added to git:
stm32mp2/a35-td/optee/stm32mp257f-ev1-ca35tdcid-ostl-m33-examples.dts
stm32mp2/a35-td/optee/stm32mp257f-dk-ca35tdcid-ostl-m33-examples.dts
stm32mp2/a35-td/optee/stm32mp257f-ev1-ca35tdcid-ostl.dts
stm32mp2/a35-td/optee/stm32mp251f-ev1-ca35tdcid-ostl.dts
stm32mp2/a35-td/optee/stm32mp257f-ev1-ca35tdcid-ostl-m33-examples-sram.dts
stm32mp2/a35-td/optee/stm32mp257f-dk-ca35tdcid-ostl.dts
Also committed the corresponding *.orig files
The commit succeeded:
The build completed successfully.
Even after rebuilding:
The pin PI8 still shows up in the system as:
Meaning the DTS change did not make it to the final DTB.
I confirmed the DTS files were edited correctly.
What additional steps are needed to ensure:
The modified DTS files inside external-dt are actually used by U-Boot / Kernel / OP-TEE?
How do I verify which DTS → DTB is consumed during boot?
Do I need to clean the kernel or u-boot sstate for OP-TEE related DTS changes?
Why does devtool show that patches were applied, but the final filesystem still shows the original pin?
Any guidance on how to correctly regenerate the final DTBs for STM32MP2 with OP-TEE device-trees would be helpful.
Thank you!