Skip to main content
OKN
Associate III
May 14, 2026
Question

[DistributionPackage] Regarding Device Tree Updates

  • May 14, 2026
  • 1 reply
  • 54 views

Hello

I am developing a custom board using the STM32MP255F-AK

Updates to the DeviceTree (DT) of a custom board placed in the `mata` layer are not reflected in the build.

I have already fetched the source using `devtool modify virtual/kernel`

The Device Tree for the custom board is located at .../layers/meta-st/meta-st-stm32mp-addons/mx/ddlskt/..


Edit the kernel's DT (stm32mp255f-ddlskt-mx.dts)
Add a marker to `model = “...”`: `model=“... AAA”`

I tried building it

$ bitbake virtual/kernel

Wrote Image.gz, *.dtb, and modules to the SD card and booted

(brd-ddlskt) # cat /proc/device-tree/model
STMicroelectronics custom STM32CubeMX board - openstlinux-6.6-yocto-scarthgap-mpu-v24.11.06

AAA has not been added to the model

Running `cleansstate` before building will reflect the updated device tree

$ bitbake -c cleansstate virtual/kernel
$ bitbake virtual/kernel

Write Image.gz, *.dtb, and modules to the SD card and boot

(brd-ddlskt) # cat /proc/device-tree/model
STMicroelectronics custom STM32CubeMX board - openstlinux-6.6-yocto-scarthgap-mpu-v24.11.06 AAA

AAA has been added to the model

Is there another way to apply the DT update?

Since running `cleansstate` takes a long time to build, I’d prefer to avoid it if possible

Best Regards,

--

okn

-----------------------

We are proceeding with development by referring to ”https://wiki.st.com/stm32mpu/wiki/How_to_create_your_own_machine#Create_a_customer_machine 

Build Configuration:
BB_VERSION = "2.8.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "aarch64-ostl-linux"
MACHINE = "stm32mp25-ddlskt"
DISTRO = "openstlinux-weston"
DISTRO_VERSION = "5.0.3-snapshot-20260514"
TUNE_FEATURES = "aarch64 crc cortexa35"
TARGET_FPU = ""
DISTRO_CODENAME = "scarthgap"
ACCEPT_EULA_stm32mp25-disco = "1"
GCCVERSION = "13.%"
PREFERRED_PROVIDER_virtual/kernel = "linux-stm32mp"

 

1 reply

OKN
OKNAuthor
Associate III
May 20, 2026

Hello all

 

Until now, I had been placing the updated device tree in

meta-st-stm32mp-addons/mx/.../kernel

I tried placing it in the source directory obtained via `devtool modify linux-stm32mp`

.../workspace/source/linux-stm32mp/arch/arm64/boot/dts/st

 

I found that

the changes in the .dts files are now reflected in the generated .dtb file

without having to run `bitbake virtual/kernel -c cleansstate`

 

Are changes made to the source tree using `devtool modify linux-stm32mp` reflected in the recipe when I run `devtool finish linux-stm32mp`?

Do I need to perform `git add`, `git commit`, or any other procedures?

 

--

OKN