Table of Contents | ||
---|---|---|
|
1. Overview
This page describes how to build the Torizon OS for the STM32MPx development boards, including:
STM32MP257x-EV1
...
STM32MP257x-DKx
...
STM32MP157x-DKx.
2. Understanding Build Structure
The base principles for building the Torizon OS for the STM32MP architecture are the same as for the other targets described in the official Torizon OS documentation: https://developer.toradex.com/torizon/in-depth/build-torizoncore-from-source-with-yocto-projectopenembedded/.
...
meta-st-stm32mp
- BSP Layer for the STM32MP targets developed by STMicroelectonics for the OpenSTLinux project: https://wiki.st.com/stm32mpu/wiki/Category:Yocto-based_OpenSTLinux_embedded_softwaremeta-emcraft-torizon-st
- adaptation of the STM32MP BSP for Torizon OS developed by EmCraftEmcraft.
What follows is the instructions on how to integrate these two layers in to the general Torizon OS Yocto project and then build Torizon OS for the STM32MP targets.
3. Preparing BSP for Build
Perform the following steps:
Set up the default
git
user and e-mail:Code Block $ git config --global user.email "you@example.com" $ git config --global user.name "Your Name"
Install the
repo
utility to the development host:Code Block $ mkdir ~/bin $ PATH=~/bin:$PATH $ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo $ chmod a+x ~/bin/repo
Create a working directory for the Yocto build and go to it, go into that directory:
Code Block $ cd ~ $ mkdir ~/yocto-workdir $ cd ~/yocto-workdir
Initialize the Torizon OS Reporeposiotiy:
Code Block $ repo init -u git://git.toradex.com/toradex-manifest.git -b kirkstone-6.x.y -m torizoncore/default.xml
Sync the repositories:
Code Block $ repo sync
Download the ST32MP2 ST32MP BSP layer:
Code Block $ git -C layers clone -b mickledore https://github.com/STMicroelectronics/meta-st-stm32mp
Download the ST32MP2 ST32MP Torizon compatibility layer:
Code Block $ git -C layers clone -b kirkstone git@github.com:EmcraftSystems/meta-emcraft-torizon-st.git
Replace the setup environment link and the Docker build link:
Code Block $ ln -sf layers/meta-emcraft-torizon-st/scripts/setup-environment setup-environment
4. Building BSP Images
Perform the following steps:
Use the Docker container provided by Toradex to setup the build environment in the work directory
~/yocto-workdir
prepared in previous steps:Code Block $ docker run --rm -it --name=crops6-minimal -v ~/yocto-workdir:/workdir --workdir=/workdir torizon/crops:kirkstone-6.x.y /bin/bash
In the docker Docker console setup set up the environment for the certain a specific STM32MP board:
MACHINE=<MACHINE> source setup-environment [BUILDDIR]
. Where , whereMACHINE
is one of the supported STM32MP targets:stm32mp25-eval
for the STM32MP2 Evaluation kit,stm32mp25-evaldisco
for the STM32MP2 Discovery kit or stm32mp25stm32mp15-evaldisco
for STM32MP1 STM32MP157 Discovery kit,BUILDDIR
in is the directory where you would like to to store the build files. For example:Code Block $$ MACHINE=stm32mp25-eval DISTRO=torizon source setup-environment build-stm32mp25-eval
Repeat the step of configuring the Git user name and email (this is only needed on the first build from scratch):
Code Block $$ git config --global user.email "you@example.com" $$ git config --global user.name "Your Name"
Build the Torizon OS images:
Code Block $$ bitbake torizon-core-docker
5. Understanding Build Outcome
When the build has successfully completed, the following artifacts build artefacts located in the $BUILDDIR/deploy/images/$MACHINE
can be used to install Torizon OS to the STM32MP target board (refer to Installing Torizon OS to STM32MP Target Boards Using the STM32 Programmer ToolTargets):
arm-trusted-firmware/
- the directory with FSBL (= Trusted Firmware-A) images:fip/
- the directory with FIP (= U-Boot) images to be installed to eMMC or SD card:flashlayout_torizon-core-docker/optee/
- the directory with eMMC or SD card layout to be used with the STM32_Programmertorizon-core-docker-<MACHINE>.ota-ext4
- main TorizonOS OSTree based image, including the Linux kernel images and the root file system.
For example, the following images will be deployed for the STM32MP2 Evaluation kit:
arm-trusted-firmware/
:tf-a-stm32mp257f-ev1-usb.stm32
- FSBL to boot the STM32MP2 targets over USB for the initial installationtf-a-stm32mp257f-ev1-optee-emmc.stm32
- FSBL to be installed and boot the STM32MP2 targets from eMMCtf-a-stm32mp257f-ev1-optee-sdcard.stm32
- FSBL to be installed and boot the STM32MP2 targets from SD cardmetadata.bin
- FSBL metadata.
fip/
:fip-stm32mp257f-ev1-ddr-optee-emmc.bin
- required to initialize DDRfip-stm32mp257f-ev1-ddr-optee-sdcard.bin
- required to initialize DDRfip-stm32mp257f-ev1-optee-emmc.bin
- main bootloader image for eMMCfip-stm32mp257f-ev1-optee-sdcard.bin
- main bootloader image for SD card
flashlayout_torizon-core-docker/optee/:
FlashLayout_emmc_stm32mp257f-ev1-optee.tsv
- eMMC layout to be used with the STM32_ProgrammerFlashLayout_sdcard_stm32mp257f-ev1-optee.tsv
- SD card layout to be used with the STM32_Programmer
torizon-core-docker-stm32mp25-eval.ota-ext4
- main Torizon OS OSTree based image, including the Linux kernel images and the root file system.
...