This article explains, using STM32CubeIDE, how to update the NOR memory, located on an ST board (e.g. here the STM32MP157x-EV1 Evaluation board 
) with
- a new device tree generated by STM32CubeMX
- the bootloader objects
 Information
|
| In this article, explanations are applicable to any version of Yocto-based OpenSTLinux embedded software. |
1. Prerequisites[edit | edit source]
You should have read instructions given in this article How to import and build STM32MPU OpenSTLinux projects in STM32CubeIDE before continuing with the current article.
2. Overview[edit | edit source]
The different steps to update a NOR memory with a customized trusted image are the following ones:
- Initialize the NOR memory with the Starter Package image by means of the STM32CubeProgrammer,
- Within STM32CubeIDE:
- customize the trusted image, using the device trees generated by the embedded STM32CubeMX
- compile the corresponding Linux® device tree and bootloader images
- update them on the running STM32MP157x-EV1 Evaluation board
- Check that the new customization is correctly set up
The NOR memory contains only the TF-A BL2 and FIP partitions. The Linux® partitions are located in the SD™ card.
All those steps are explained in the chapters below.
3. Initialize the NOR memory with the Starter Package[edit | edit source]
Initialize the NOR memory with the Starter Package image with STM32CubeProgrammer.
For that, select the Starter package corresponding to the OpenSTLinux projects imported in STM32CubeIDE and to the targeted board STM32MP157x-EV1 Evaluation board and jump to chapter Downloading the image and flashing it on the board.
Before executing the next step, check the bootloader version, which is visible in boot messages:
- TF-A BL2 version, booting from the NOR memory
- U-boot version and extlinux.conf file used, booting from the NOR memory
- extlinux.conf content before update
4. Build the trusted image inside STM32CubeIDE with the new expected device trees[edit | edit source]
After the customization of hardware resources within the STM32CubeMX (visit this page), the new device trees for Linux® and for the bootloader are generated.
The next step is to build a new trusted image; this is covered also within STM32CubeIDE with:
- bootloader images generation, as explained in How_to_import_and_build_STM32MPU_OpenSTLinux_projects_in_STM32CubeIDE#Bootloader_projects
- and Linux® device tree compilation How_to_import_and_build_STM32MPU_OpenSTLinux_projects_in_STM32CubeIDE#Linux_project
Note that for Linux®, only the device tree needs to be updated as described hereafter.
5. Update the board with new Linux® device tree[edit | edit source]
In this step, the STM32MP157x-EV1 Evaluation board is up and running with network access: target status is green.
After having compiled the OpenSTLinux project with the device tree generated by STM32CubeMX, you must:
- update the STM32MP15x target bootfs with the new .dtb under /boot
- and adjust /boot/mmc0_extlinux/extlinux.conf to declare the new device tree and set it as default. Note that this setup is done in the SD™ card memory since the Linux® partitions are located there.
For that, follow the steps explained below:
- select the Cortex-A Linux® Deployment shortcut configuration available from Linux® project Run As... menu.
- Validate your choice and use the Run button. You get in a dedicated Linux® Deployment console a message like this one:
- Check extlinux.conf content after the NOR Linux® device tree update (DEFAULT and LABEL have changed)
5.1. Update the board with new bootloader images[edit | edit source]
In this step, the STM32MP157x-EV1 Evaluation board is up and running with network access: target status is green.
After having built customized bootloader images, you must update the STM32MP157x-EV1 Evaluation board .
- Select the Cortex-A project in STM32CubeIDE and right-click to get the Cortex-A Bootloader Deployment shortcut.
The connection is automatically set and you need to scan the STM32MP15x target storage, using the Scan... button.
This storage list depends on the board and on the boot storage used.
Then, select the storage to update (NOR #0 here), and the TF-A BL2 and FIP image to update from FIP_artifacts/.
Here is the corresponding STM32 Cortex-A Bootloader Deployment configuration:
- Click on Run. You get in a dedicated Bootloader Deployment console the following message:
6. Check the new bootloader version after the customization with STM32CubeIDE[edit | edit source]
After the update, the new bootloader version can be checked by comparing the versions appearing in boot messages: the TF-A BL2 and U-Boot versions are modified and Linux® uses the generated device tree.
Here are the new boot messages:
- TF-A BL2 updated version, booting from the NOR memory
- U-Boot updated version and Linux® device tree, booting from the NOR memory
Arm® is a registered trademark of Arm Limited (or its subsidiaries) in the US and/or elsewhere. 