This article gives details about updating NOR located onto STM32MP157x-EV1 with bootloader objects.
1. Overview[edit source]
First NOR 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.
NOR contains only TF-A BL2 and FIP partitions, Linux partitions are located on SD-Card.
2. Initial configuration[edit source]
Here are the TF-A BL2, U-boot version and the used extlinux.conf file used in Starter Package.
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/mmc0_extlinux/stm32mp157c-ev1_extlinux.conf. This is done thanks to Cortex-A Linux® Deployment shortcut configuration available from Linux® project Run As... .
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, NOR#0 here; TF-A BL2 & FIP image to update.
4. Final configuration[edit source]
After the update, TF-A BL2 and U-Boot versions are modified and Linux® uses the generated Device Tree.
