How to compile the device tree with the Developer Package

Applicable for

STM32MP15x lines

---

1 Purpose

This article explains how to update the boot chain (trusted modeOP-TEE with FIP) for a "custom" device tree.
In particular, STM32CubeMX can generate a "custom" device tree.

This article describes how to update the device tree compiled (DTB) part of the boot binaries.

2 Rationale

There are various rationale for using a custom device tree, such as:

• the description of a new and private board
• the swapping of some internal peripherals from Cortex^®-M side to Cortex-A side (or the opposite)

3 Prerequisites

Information

Even if STMicroelectronics strongly recommends to use a Linux® environment, the steps described in this article can be executed in a WSL2 (Windows Sub-system Linux 2) environment.

Compiling a new device tree means updating three software components belonging to the complete boot chain (trusted mode), Trusted Firmware A (TF-A), uU-bootBoot, and Linux kernel.

The material required to update the above software components is the following:

• Starter package:
  • the flashlayout as well as the images to flash, provided within the en.FLASH-stm32mp1-openstlinux<YY>openstlinux-<MM>-<DD>.5.15-yocto-kirkstone-mp1-v22.06.15.tar.xz file (download it from st.com)
• Developer package:
  • the component sources and patches, provided within the en.SOURCES-stm32mp1-openstlinux-<YY>5.15-<MM>-<DD>.yocto-kirkstone-mp1-v22.06.15.tar.xz file (download it from st.com)
  • the SDK toolchain, provided within the en.SDK-x86_64-stm32mp1-openstlinux-<YY>5.15-<MM>-<DD>.yocto-kirkstone-mp1-v22.06.15.tar.xz file (download it from st.com)
• the STM32CubeProgrammer, which is the tool used to flash the images and binaries into the target.

• Custom device tree sources:
  • In the rest of this document, we assume that the custom device tree is generated by STM32CubeMX and stored in a MyDeviceTree_fromCubeMX.tar.xz tarball with following file tree:

MyDeviceTree_fromCubeMX
|-- kernel
|   |-- stm32mp157cstm32mp157f-mydevicetree-mx.dts
|-- tf-a
|  |-- stm32mp157cstm32mp157f-mydevicetree-mx.dts
|  |-- stm32mp157cstm32mp157f-mydevicetree-mx-fw-config.dts
|  |-- stm32mp15-mx.dtsi
|-- u-boot
|  |-- stm32mp157cstm32mp157f-mydevicetree-mx.dts
|  |-- stm32mp157cstm32mp157f-mydevicetree-mx-u-boot.dtsi
|  |-- stm32mp15-mx.dtsi

• Make sure the hardware configuration described in PC_prerequisites#Linux PC has been executed (even with a WSL2 setup)

4 Preparing your environment

It is recommended to organize the numerous inputs described in #Prerequisites in your environment.
First create a dedicated WORKDIR under your HOME folder and copy there all the inputs listed in #Prerequisites:

cd $HOME

mkdir WORKDIR

cd WORKDIR

export WORKDIR="$PWD"

tar --strip-components=1 -xf <FLASH-st-image-weston-openstlinux-weston-stm32mp1.tar.xz> -C $WORKDIR/

tar --strip-components=1 -xf <SOURCES-st-image-weston-openstlinux-weston-stm32mp1.tar.xz> -C $WORKDIR/

tar --strip-components=1 -xf <SDK-st-image-weston-openstlinux-weston-stm32mp1.tar.xz> -C $WORKDIR/

tar xf <MyDeviceTree_fromCubeMX.tar.xz> -C $WORKDIR/

Then proceed with the SDK installation.

The commands described in the rest of the document must be run in an SDK environment context: (Starting_up_the_SDK).

5 Updating the kernel device tree

Since 'extlinux.conf' explicitly points to the DTB, just update the kernel device tree by replacing the DTB file of the '/boot' partition. The path used must be something like '/boot/<devicetree>.dtb'.

The following chapters describe the procedure to generate and copy the new DTB into the target.

5.1 Kernel : unpack and patch sources

Information

The procedure below is an extract of the README.HOW_TO.txt file which is available in $WORKDIR/sources/arm-ostl-linux-gnueabi/linux-stm32mp-*. Please notice a grep "$>" README.HOW_TO.txt describes the few commands needed to build the artifact of kernel

Run the following command into a shell:

pushd $WORKDIR

mkdir -p kernel

tar xf sources/arm-ostl-linux-gnueabi/linux-stm32mp-*/linux-*.tar.xz -C kernel

mv kernel/linux-* kernel/kernel-sources/

pushd kernel/kernel-sources/

for p in $(ls -1 ../../sources/arm-ostl-linux-gnueabi/linux-stm32mp-*/*.patch); do patch -p1 < $p; done

popd

popd

5.2 Kernel : copy the DTS into the source code

pushd $WORKDIR

cp -r MyDeviceTree_fromCubeMX/kernel/* kernel/kernel-sources/arch/arm/boot/dts/

popd

5.3 Kernel : regenerate the kernel DTB

Information

The procedure below is an extract of the README.HOW_TO.txt file which is available in $WORKDIR/sources/arm-ostl-linux-gnueabi/linux-stm32mp-*. Please notice a grep "$>" README.HOW_TO.txt describes the few commands needed to build the artifact of kernel

pushd $WORKDIR/kernel/kernel-sources

make ARCH=arm O="$PWD/../build" multi_v7_defconfig fragment*.config

for f in `ls -1 ../../sources/arm-ostl-linux-gnueabi/linux-stm32mp-*/fragment*.config`; do scripts/kconfig/merge_config.sh -m -r -O $PWD/../build $PWD/../build/.config $f; done

yes "" | make ARCH=arm oldconfig O="$PWD/../build"

make stm32mp157cstm32mp157f-mydevicetree-mx.dtb LOADADDR=0xC2000040 O="$PWD/../build"

popd

ls -l $WORKDIR/kernel/build/arch/arm/boot/dts/stm32mp157cstm32mp157f-mydevicetree-mx.dtb

5.4 Kernel : copy the DTB into bootfs

First of all #Updating bootfs with the new DTB so that it is taken it into account at the next boot of the target.

Then, if needed, #Updating extlinux for the target according to this new DTB filename. This is only required if the filename of the generated DTB is different from the one used by extlinux to boot.

6 Updating BOOT firmwares

BOOT firmwares are TF-A and U-Boot and should be updated together (CubeMX provides devicetree for TF-A and U-Boot).

6.1 Updating the TF-A device tree

To update the TF-A device tree, replace the DTB part of the TF-A binary.
The TF-A binary allocates a 'fixed' area for the DTB, just after the 'mkimage" headers. If the DTB is smaller than the reserved area, the remaining memory is padded with zero.

Below the procedure to generate TF-A with a new DTB and then flash it on the target:

6.1.1 TF-A : unpack and patch sources

Information

The procedure below is an extract of the README.HOW_TO.txt file which is available in $WORKDIR/sources/arm-ostl-linux-gnueabi/tf-a-stm32mp-*. Please notice a grep "$>" README.HOW_TO.txt describes the few commands needed to build the artifact of tf-a

pushd $WORKDIR

pushd sources/arm-ostl-linux-gnueabi/tf-a-stm32mp-v[0-9]*

mkdir -p tf-a-sources

tar xf tf-a-stm32mp-v[0-9]*.tar.* --one-top-level=tf-a-sources --strip-components=1

pushd tf-a-sources

for p in `ls -1 ../*.patch`; do patch -p1 < $p; done

popd

popd

6.1.2 TF-A : copy the DTS into the source code

pushd $WORKDIR

cp -r MyDeviceTree_fromCubeMX/tf-a/* sources/arm-ostl-linux-gnueabi/tf-a-stm32mp-v[0-9]*/tf-a-sources/fdts/

popd

6.1.3 TF-A : regenerate TF-A

Information

The procedure below is an extract of the README.HOW_TO.txt file which is available in $WORKDIR/sources/arm-ostl-linux-gnueabi/tf-a-stm32mp-*. Please notice a grep "$>" README.HOW_TO.txt describes the few commands needed to build the artifact of tf-a

First only the TF-A "intermediates" artifacts are generated, the FIP image will be generated at final step (U-Boot compilation).

pushd $WORKDIR/sources/arm-ostl-linux-gnueabi/tf-a-stm32mp-v[0-9]*/tf-a-sources

export FIP_DEPLOYDIR_ROOT=$PWD/../../FIP_artifacts

make -f ../Makefile.sdk TF_A_DEVICETREE=<devicetree_name> FIP_CONFIG=" trusted" FIP_BL32_CONF="tfa," TF_A_CONFIG="trusted optee emmc nand nor sdcard uart usb" DEPLOYDIR=$FIP_DEPLOYDIR_ROOT/arm-trusted-firmware stm32

<device tree><devicetree_name> : is the device tree just copied, i.e.: stm32mp157cstm32mp157f-mydevicetree-mx

DEPLOYDIR is the path where intermediate binaries of tf-a should be deployed (requiered by fip-tools to generate fip image)

popd

7

6.2 Updating the

u

OP-

boot

TEE device tree

To update the uOP-boot TEE device tree, replace the DTB part of the uOP-boot TEE binary.
Adding a new device tree to the uOP-boot TEE source code forces the Makefile to regenerate a new uOP-boot.stm32 containing the new DTS. TEE binaries.
The following chapters describe the procedure to update the OP-TEE device tree.

6.2.1 OP-TEE: unpack and patch sources

Information

The procedure below is an extract of the README.HOW_TO.txt file which is available in $WORKDIR/sources/arm-ostl-linux-gnueabi/optee-os-stm32mp-*. Please notice a grep "$>" README.HOW_TO.txt describes the few commands needed to build the artifact of OP-TEE

pushd $WORKDIR

pushd sources/arm-ostl-linux-gnueabi/optee-os-stm32mp-[0-9]*

tar xf optee-os-stm32mp-[0-9]*.tar.* --one-top-level=optee-os-sources --strip-components=1

pushd optee-os-sources

tar xfz ../fonts.tar.gz

for p in `ls -1 ../*.patch`; do patch -p1 < $p; done

popd

popd

6.2.2 OP-TEE: copy the DTS in the source code

pushd $WORKDIR

cp MyDeviceTree_fromCubeMX/u-boot/* sources/arm-ostl-linux-gnueabi/optee-os-stm32mp-*/optee-os-sources/core/arch/arm/dts/

popd

6.2.3 OP-TEE: regenerate fip image within new OP-TEE

Information

The procedure below is an extract of the README.HOW_TO.txt file which is available in $WORKDIR/sources/arm-ostl-linux-gnueabi/u-boot-stm32mp-*. Please notice a grep "$>" README.HOW_TO.txt describes the few commands needed to build the artifact of OP-TEE

pushd $WORKDIR/sources/arm-ostl-linux-gnueabi/optee-os-stm32mp-[0-9]*/optee-os-sources

make -f ../Makefile.sdk CFG_EMBED_DTB_SOURCE_FILE=<device tree> OPTEE_DRAMSIZE=<RAM size> DEPLOYDIR=~/views/temp/CubeIde/WORKDIR/sources/arm-ostl-linux-gnueabi/FIP_artifacts/optee optee

<device tree> : is the device tree just copied, i.

7.1 U-boot 

e.: stm32mp157f-mydevicetree-mx

<RAM size>  : is the RAM size of the board selected by the device treee, i.e.: 0x20000000

popd

6.3 Updating the U-Boot device tree

To update the U-Boot device tree, need to replace the U-Boot DTB in FIP image.

6.3.1 U-Boot : unpack and patch sources

Information

The procedure below is an extract of the README.HOW_TO.txt file which is available in $WORKDIR/sources/arm-ostl-linux-gnueabi/u-boot-stm32mp-*. Please notice a grep "$>" README.HOW_TO.txt describes the few commands needed to build the artifact of uU-boot Boot

pushd $WORKDIR

pushd sources/arm-ostl-linux-gnueabi/u-boot-stm32mp-v[0-9]*

tar xf u-boot-stm32mp-v[0-9]*.tar.* --one-top-level=u-boot-sources --strip-components=1

pushd u-boot-sources

for p in `ls -1 ../*.patch`; do patch -p1 < $p; done

popd

popd

7

6.3.2 U-

boot 

Boot : copy the DTS in the

u

U-

boot

Boot source code

pushd $WORKDIR

cp MyDeviceTree_fromCubeMX/u-boot/* sources/arm-ostl-linux-gnueabi/u-boot-stm32mp-v[0-9]*/u-boot-sources/arch/arm/dts/

popd

7

6.3.3 U-

boot 

Boot : regenerate fip image within new

u

U-

boot

Boot binary

Information

The procedure below is an extract of the README.HOW_TO.txt file which is available in $WORKDIR/sources/arm-ostl-linux-gnueabi/u-boot-stm32mp-*. Please notice a grep "$>" README.HOW_TO.txt describes the few commands needed to build the artifact of uU-boot Boot

pushd $WORKDIR/sources/arm-ostl-linux-gnueabi/u-boot-stm32mp-v[0-9]*/u-boot-sources

make stm32mp15_<config>_defconfig

<config> : could be trusted or basic according the boot type

stm32mp1[35]_defconfig

make -f ../Makefile.sdk DEVICEUBOOT_TREE=<device tree> DEPLOYDIR=$FIP_DEPLOYDIR_ROOT/CONFIG=trusted UBOOT_DEFCONFIG=stm32mp1[35]_defconfig UBOOT_BINARY=u-boot.dtb FIP_CONFIG=" trusted" FIP_BL32_CONF="tfa," optee" DEVICETREE=<device tree> all

<device tree> : is the device tree just copied, i.e.: stm32mp157cstm32mp157f-mydevicetree-mx

popd

7

6.3.4 U-

boot 

Boot : copy

the u

U-

boot

Boot binary into the target

• Because of 'extlinux' and before flashing the new fip image, make sure #Updating extlinux is compliant with the 'compatible' value in the DTS file.
  
• Then, using STM32CubeProgrammer, flash the utf-boota-xxxx.stm32 file (generated at tf-a step) into the 'ssblfsbl1' and 'fsbl2' partition of the target using STM32CubeProgrammer.

8

• and the 'fip-a' partition with fip-stm32mpxxxx.bin file (generated just above).

7 Update methods

87.1 Updating extlinux

87.1.1 extlinux basics

extlinux describes how uU-boot Boot boots. Updating extlinux consists in updating the extlinux.conf:

• In case of an DK-2 board booting from the sdcard. A stm32mp157cstm32mp157f-dk2_extlinux.conf file is located in /boot/mmc0_extlinux/,
• otherwise if there is no specific extlinux.conf for your board then the extlinux.conf is taking into account.

extlinux.conf is the description of a boot menu with one or several entries; 'DEFAULT' selects the default entry.
Below an example of extlinux.conf:

menu title Select the boot mode
MENU BACKGROUND ../splash.bmp
TIMEOUT 5
DEFAULT stm32mp157cstm32mp157f-mydevicetree-mx
LABEL stm32mp157cstm32mp157f-dk2-sdcard
        KERNEL /uImage
        FDTDIR /
        APPEND root=PARTUUID=e91c4e10-16e6-4c0e-bd0e-77becf4a3582 rootwait rw console=ttySTM0,115200
LABEL stm32mp157cstm32mp157f-dk2-a7-examples-sdcard
        KERNEL /uImage
        FDT /stm32mp157cstm32mp157f-dk2-a7-examples.dtb
        APPEND root=PARTUUID=e91c4e10-16e6-4c0e-bd0e-77becf4a3582 rootwait rw console=ttySTM0,115200
LABEL stm32mp157cstm32mp157f-dk2-m4-examples-sdcard
        KERNEL /uImage
        FDT /stm32mp157cstm32mp157f-dk2-m4-examples.dtb
        APPEND root=PARTUUID=e91c4e10-16e6-4c0e-bd0e-77becf4a3582 rootwait rw console=ttySTM0,115200
LABEL stm32mp157cstm32mp157f-mydevicetree-mx
       KERNEL /uImage
       FDT /stm32mp157cstm32mp157f-mydevicetree-mx.dtb
       APPEND root=PARTUUID=e91c4e10-16e6-4c0e-bd0e-77becf4a3582 rootwait rw console=ttySTM0,115200

Please update/add the highlighted lines according to what have been compiled in chapter 5, 6 and/or 7:

• DEFAULT: This is the default 'LABEL' to boot
• LABEL : The entry 'LABEL' is the value of 'compatible' of the DTS file compiled with u-bootused by U-Boot.

  The 'compatible' value is at head of the DTS file and looks like : "st,stm32mp157cstm32mp157f-mydevicetree-mx"

• FDT : The path from /boot of the kernel DTB to use

87.2 Updating bootfs

There are two methods to update bootfs

• On an up and running target

scp stm32mp157cstm32mp157f-mydevicetree-mx.dtb root@<Target_IP>:/boot/

• Directly into 'bootfs' image

You do not need to have a target up and running. Only the "st-image-bootfs-openstlinux-weston-stm32mp1.ext4" file is required. To modify an 'ext4' file, a loopback mount, avaible within any Linux Distribution (even through WSL2), is required:

mkdir -p $WORKING$WORKDIR/bootfs

mount -o loop <st-image-bootfs-openstlinux-weston-stm32mp1.ext4> $WORKING $WORKDIR/bootfs

##Then copy the new dtb file at the root of $WORKING$WORKDIR/bootfs

umount $WORKING$WORKDIR/bootfs

sync

Then use STM32CubeProgrammer to update the bootfs partiton

87.2.1 Updating extlinux

Updating 'extlinux' consists in modifying the extlinux.conf. There are two ways to do this:

• On an up and running target

Open an ssh connection to the target or use a direct connection with a tty terminal. Then use an vi editor to modify the extlinux.conf file.

Do not forget to synchronize the file system before rebooting the target:

sync

• Into 'bootfs' image directly

You do not need to have a target up and running. Only the "st-image-bootfs-openstlinux-weston-stm32mp1.ext4" file is required. To modify an 'ext4' file, a loopback mount tool, avaible in any Linux Distribution (even through WSL2), is needed:

mkdir -p $WORKING$WORKDIR/bootfs

sudo mount -o loop <st-image-bootfs-openstlinux-weston-stm32mp1.ext4> $WORKING $WORKDIR/bootfs

##Then edit the extlinux.conf file (for WSL2 use a 'Linux' type editor; vi, ...)

##Once extlinux.conf up-to-date, umount loopback and flash the bootfs into sdcard with STM32CubeProgrammer