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 page is a candidate for renaming (move).
The requested new name is: How to manage OpenSTLinux projects in STM32CubeIDE/eMMC update with customized trusted image .
The supplied reason is: sub article .
-- Ludovic/Nathalie.
Wiki maintainers: remember to update the pages that link this page before renaming (moving) it.

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

1. Overview[edit source]

First eMMC is intialized with Starter Package image thanks to STM32CubeProgrammer.
The trusted image is built inside STM32CubeIDE with Device Tree configured thanks to embedded STM32CubeMX. Next step is to update MP15 target; this meaning your MP15 target 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. Initial configuration[edit source]

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

eMMC initial setting: TF-A BL2 version

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

eMMC initial setting: extlinux.conf content

3. Update[edit source]

First, after compiling Device Tree from STM32CubeMX we need to update MP15 target bootfs with new .dtb under /boot and adjust /boot/mmc1_extlinux/extlinux.conf. This is done thanks to Cortex-A Linux^® Deployment shortcut configuration available from Linux^® project Run As... .

Linux^® deployment configuration

eMMC Linux^® deployment message

eMMC Linux^® device tree update

Then, select Cortex-A project and right click to get Cortex-A Bootloader Deployment 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 message

4. Final configuration[edit source]

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

eMMC updated TF-A BL2 version

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