eMMC update with customized trusted image

This message will disappear after all relevant tasks have been resolved.

Semantic MediaWiki

There are 1 incomplete or pending task to finish installation of Semantic MediaWiki. An administrator or user with sufficient rights can complete it. This should be done before adding new data to avoid inconsistencies.

This article gives details about updating the bootloader objects of eMMC memory, located onto STM32MP157x-EV1 (e.g.), using STM32CubeIDE.

1. Overview[edit source]

Here is the process used:

eMMC is first initialized with Starter Package image thanks to STM32CubeProgrammer.
The trusted image is built inside STM32CubeIDE with device tree configured using embedded STM32CubeMX.
Next step is to update STM32MP15 board; this means the STM32MP15 board is up and running with network access: target status is green.
The way to check this customization is to compare version appearing in boot message.

2. Bootloader version after update with Starter Package[edit source]

Here are the TF-A BL2, U-boot version and the used extlinux.conf file used in Starter Package.
They all appear in boot messages.

TF-A BL2 version, booting from eMMC memory

eMMC initial setting: TF-A BL2 version

U-boot version & extlinux.conf file used, booting from eMMC memory

eMMC initial setting: U-boot version & extlinux.conf

extlinux.conf content before update.

eMMC initial setting: extlinux.conf content

3. Customizing bootloader with STM32CubeIDE[edit source]

After compiling device tree generated by STM32CubeMX we need to :

update MP15 target bootfs with new .dtb under /boot
and adjust /boot/mmc1_extlinux/extlinux.conf in order to declare new device tree and set it as default.

This is done thanks to Cortex-A Linux^® Deployment shortcut configuration available from Linux^® project Run As... menu.

Linux^® deployment configuration

Linux^® deployment configuration

eMMC Linux^® deployment message

eMMC Linux^® deployment message

eMMC Linux^® device tree update

eMMC Linux^® device tree update

Then, select Cortex-A project and right click to get Cortex-A Bootloader Deployment shortcut.

Bootloader update shortcut

Connection is automatically set and you need to scan MP15 target storage. This storage list depends on the board and on boot storage used. Then, select:

the storage to update, eMMC #0 here;
TF-A BL2 & FIP image to update from FIP_artifacts/ .

eMMC bootloader deployment configuration

eMMC Bootloader deployment configuration

eMMC bootloader deployment message

eMMC Bootloader deployment message

4. Bootloader version after customization wit STM32CubeIDE[edit source]

After the update, TF-A BL2 and U-Boot versions are modified and Linux^® uses the generated Device Tree. Here are the boot messages now:

TF-A BL2 updated version, booting from eMMC memory

eMMC updated TF-A BL2 version

U-Boot updated version & Linux^® device tree, booting from eMMC memory

eMMC updated U-Boot version & Linux^® Device Tree