This page is a candidate for renaming (move). The requested new name is: STM32MP2_Developer_Package_-_OpenSTLinux_BSP . The supplied reason is: Previous idea was to have only 1 developer package. But some tests showed it's more complex. So developer package : one STM32MP2_Developer_Package_-_OpenSTLinux_BSP for MP1 and one STM32MP2_Developer_Package_-_OpenSTLinux_BSP for MP2. -- Registered User (-) 14:16, 5 June 2024 (CEST). Wiki maintainers: remember to update the pages that link this page before renaming (moving) it. |
This article aims at giving the following information:
- How to get the latest OP-TEE, TF-A, U-Boot, Linux® kernel, gcnano-driver, external device tree and debug symbols for the STM32 microprocessor series
- Where to find the associated release note
- Where to find the previous releases (archives)
1. STM32MPU ecosystem v5.1.0 release[edit source]
The software package is provided AS IS, and by downloading it, you agree to be bound to the terms of the software license agreement (SLA0048). The detailed content licenses can be found here.
- The OpenSTLinux BSP package is delivered through a tarball file named en.sources-stm32mp1-openstlinux-6.1-yocto-mickledore-mpu-v24.06.26.tar.gz for STM32MP257F-EV1 boards.
- Download and install the STM32MPU OpenSTLinux BSP package.
STM32MPU Developer Package - STM32MPU ecosystem v5.1.0 release | |
---|---|
Download |
|
Installation |
cd <working directory path>/Developer-Package
tar xvf en.sources-stm32mp1-openstlinux-6.1-yocto-mickledore-mpu-v24.06.26.tar.gz |
Release note |
Details about the content of the OpenSTLinux BSP package are available in the associated STM32 MPU OpenSTLinux release note. For information on older releases, go to Archives. |
- In sub-directories from <Developer Package installation directory>/stm32mp1-openstlinux-6.1-yocto-mickledore-mpu-v24.06.26/sources/arm-ostl-linux-gnueabi, several tarball archive of the OpenSTLinux BSP components can be found.
- The external device tree directory is named external-dt-<ext-dt version>:
external-dt-v5.0-stm32mp-r1-r0 external device tree installation directory ├── external-dt-v5.0-stm32mp-r1-r0.tar.xz Tarball file of the external device tree source code └── README.HOW_TO.txt Helper file for external device tree management: reference for external device tree usage
- The Linux kernel installation directory is named linux-stm32mp-<kernel version>:
linux-stm32mp-6.1.82-stm32mp-r2-r0 Linux kernel installation directory ├── [*].patch ST patches to apply during the Linux kernel preparation (see next chapter) ├── fragment-[*].config ST configuration fragments to apply during the Linux kernel configuration (see next chapter) ├── optional-fragment-[*].config Optional ST configuration fragments to apply during the Linux kernel configuration depending on your needs (SMP or not, signature or not, ...) ├── linux-6.1.82.tar.xz Tarball file of the Linux kernel source code ├── README.HOW_TO.txt Helper file for Linux kernel management: reference for Linux kernel build └── series List of all ST patches to apply
- The gcnano driver installation directory is named gcnano-driver-stm32mp-<gcnano driver version>:
gcnano-driver-stm32mp-6.4.15-stm32mp1-r1-r0/ gcnano-driver installation directory ├── [*].patch ST patches to apply during the gcnano driver preparation (see next chapter) ├── gcnano-driver-stm32mp-6.4.15-stm32mp1-r1-r0.tar.xz Tarball file of the gcnano-driver source code ├── README.HOW_TO.txt Helper file for gcnano-driver management: reference for gcnano-driver build └── series List of all ST patches to apply
- The ddr phy installation directory is named stm32mp-ddr-phy-<ddr phy version>:
unknown package ddr-phy installation directory ├── unknown package Tarball file of the ddr-phy binaries └── README.HOW_TO.txt Helper file for ddr phy management: reference for ddr-phy use
- The OP-TEE installation directory is named optee-os-stm32mp-<OP-TEE version>:
optee-os-stm32mp-3.19.0-stm32mp-r2-r0/ OP-TEE installation directory ├── [*].patch ST patches to apply during the OP-TEE preparation (see next chapter) ├── fiptool-stm32mp tool for fip generation ├── fonts.tar.gz fonts for OPTEE-OS ├── Makefile.sdk Makefile for the OP-TEE compilation ├── optee-os-stm32mp-3.19.0-stm32mp-r2-r0.tar.xz Tarball file of the OP-TEE source code ├── README.HOW_TO.txt Helper file for OP-TEE management: reference for OP-TEE build └── series List of all ST patches to apply
- The U-Boot installation directory is named u-boot-stm32mp-<U-Boot version>:
u-boot-stm32mp-v2022.10-stm32mp-r2-r0 U-Boot installation directory ├── [*].patch ST patches to apply during the U-Boot preparation (see next chapter) ├── fiptool-stm32mp tool for fip generation ├── fragment-[*].fb_cfg ST configuration fragments to apply during the U-Boot configuration to support fastboot ├── Makefile.sdk Makefile for the U-Boot compilation ├── README.HOW_TO.txt Helper file for U-Boot management: reference for U-Boot build ├── series List of all ST patches to apply └── u-boot-stm32mp-v2022.10-stm32mp-r2-r0.tar.xz Tarball file of the U-Boot source code
- The TF-A installation directory is named tf-a-stm32mp-<TF-A version>:
tf-a-stm32mp-v2.8.15-stm32mp-r2-r0 TF-A installation directory ├── [*].patch ST patches to apply during the TF-A preparation (see next chapter) ├── fiptool-stm32mp tool for fip generation ├── Makefile.sdk Makefile for the TF-A compilation ├── README.HOW_TO.txt Helper file for TF-A management: reference for TF-A build ├── series List of all ST patches to apply ├── tf-a-st-ddr.tar.gz Tarball file of the DDR firmware └── tf-a-stm32mp-v2.8.15-stm32mp-r2-r0.tar.xz Tarball file of the TF-A source code
- The FIP artifacts directory is named FIP_artifacts:
FIP_artifacts ├── arm-trusted-firmware │ ├── bl31 │ │ ├── stm32mp257f-dk-bl31-optee.dtb │ │ ├── stm32mp257f-ev1-bl31-optee.dtb │ │ ├── stm32mp257f-ev1-ca35tdcid-ostl-bl31-optee.dtb │ │ ├── stm32mp257f-ev1-ca35tdcid-ostl-m33-examples-bl31-optee.dtb │ │ └── tf-a-bl31-stm32mp25-optee.bin │ ├── ddr │ │ └── ddr_pmu-stm32mp25[*].bin DDR firmware → STM32MP25 boards │ ├── fwconfig │ │ └── stm32mp25[*]-optee.dtb Device tree for FW config → STM32MP25 boards │ ├── metadata.bin Store boot information │ └── tf-a-stm32mp257[*].stm32 FSBL binary → STM32MP25 boards ├── fip │ ├── fip-stm32mp257f-dk-ddr.bin │ ├── fip-stm32mp257f-dk-optee.bin │ ├── fip-stm32mp257f-ev1-ca35tdcid-ostl-ddr.bin │ ├── fip-stm32mp257f-ev1-ca35tdcid-ostl-m33-examples-ddr.bin │ ├── fip-stm32mp257f-ev1-ca35tdcid-ostl-m33-examples-optee.bin │ ├── fip-stm32mp257f-ev1-ca35tdcid-ostl-optee.bin │ ├── fip-stm32mp257f-ev1-ddr.bin │ └── fip-stm32mp257f-ev1-optee.bin ├── optee │ ├── tee-header_v2-stm32mp25[*].bin Binary file for OP-TEE OS → STM32MP25 boards │ ├── tee-pageable_v2-stm32mp25[*].bin Binary file for OP-TEE OS → STM32MP25 boards │ └── tee-pager_v2-stm32mp25[*].bin Binary file for OP-TEE OS → STM32MP25 boards └── u-boot ├── u-boot-nodtb-stm32mp25.bin └── u-boot-stm32mp25[*].dtb Device tree for U-Boot → STM32MP5 boards
- The debug symbol files are located under the <Developer Package installation directory>/stm32mp1-openstlinux-6.1-yocto-mickledore-mpu-v24.06.26/images/stm32mp1 directory:
2. Archives [edit source]
This wiki is for the v5 ecosystem releases. For information about the previous ecosystem releases, go through the Wiki archives.
2.1. STM32MPU ecosystem v5.0.2.BETA release[edit source]
The software package is provided AS IS, and by downloading it, you agree to be bound to the terms of the software license agreement (SLA0048). The detailed content licenses can be found here.
- The OpenSTLinux BSP package is delivered through a tarball file named unknown revision for STM32MP257F-EV1 boards.
- Download and install the STM32MPU OpenSTLinux BSP package.
STM32MPU Developer Package - STM32MPU ecosystem v5.0.2.BETA release | |
---|---|
Download |
|
Installation |
cd <working directory path>/Developer-Package
tar xvf en.sources-stm32mp1-openstlinux-6.1-yocto-mickledore-mpu-v24.06.26.tar.gz |
Release note |
Details about the content of the OpenSTLinux BSP package are available in the associated STM32 MPU OpenSTLinux release note. For information on older releases, go to Archives. |
- In sub-directories from <Developer Package installation directory>/unknown revision, several tarball archive of the OpenSTLinux BSP components can be found.
- The external device tree directory is named external-dt-<ext-dt version>:
unknown revision external device tree installation directory ├── unknown revision Tarball file of the external device tree source code └── README.HOW_TO.txt Helper file for external device tree management: reference for external device tree usage
- The Linux kernel installation directory is named linux-stm32mp-<kernel version>:
unknown revision Linux kernel installation directory ├── [*].patch ST patches to apply during the Linux kernel preparation (see next chapter) ├── fragment-[*].config ST configuration fragments to apply during the Linux kernel configuration (see next chapter) ├── optional-fragment-[*].config Optional ST configuration fragments to apply during the Linux kernel configuration depending on your needs (SMP or not, signature or not, ...) ├── unknown revision Tarball file of the Linux kernel source code ├── README.HOW_TO.txt Helper file for Linux kernel management: reference for Linux kernel build └── series List of all ST patches to apply
- The gcnano driver installation directory is named gcnano-driver-stm32mp-<gcnano driver version>:
unknown revision gcnano-driver installation directory ├── [*].patch ST patches to apply during the gcnano driver preparation (see next chapter) ├── unknown revision Tarball file of the gcnano-driver source code ├── README.HOW_TO.txt Helper file for gcnano-driver management: reference for gcnano-driver build └── series List of all ST patches to apply
- The SCP firmware installation directory is named scp-firmware-<SCP firmware version>:
unknown revision SCP-FW installation directory ├── [*].patch ST patches to apply during the SCP firmware preparation (see next chapter) ├── unknown revision Tarball file of the SCP firmware source └── README.HOW_TO.txt Helper file for SCP firmware management: reference for SCP firmware build
- The OP-TEE installation directory is named optee-os-stm32mp-<OP-TEE version>:
unknown revision OP-TEE installation directory ├── [*].patch ST patches to apply during the OP-TEE preparation (see next chapter) ├── fonts.tar.gz fonts for OPTEE-OS ├── Makefile.sdk Makefile for the OP-TEE compilation ├── unknown revision Tarball file of the OP-TEE source code ├── README.HOW_TO.txt Helper file for OP-TEE management: reference for OP-TEE build └── series List of all ST patches to apply
- The U-Boot installation directory is named u-boot-stm32mp-<U-Boot version>:
unknown revision U-Boot installation directory ├── [*].patch ST patches to apply during the U-Boot preparation (see next chapter) ├── Makefile.sdk Makefile for the U-Boot compilation ├── README.HOW_TO.txt Helper file for U-Boot management: reference for U-Boot build ├── series List of all ST patches to apply └── unknown revision Tarball file of the U-Boot source code
- The TF-A installation directory is named tf-a-stm32mp-<TF-A version>:
unknown revision TF-A installation directory ├── [*].patch ST patches to apply during the TF-A preparation (see next chapter) ├── Makefile.sdk Makefile for the TF-A compilation ├── README.HOW_TO.txt Helper file for TF-A management: reference for TF-A build ├── series List of all ST patches to apply ├── tf-a-st-ddr.tar.gz Tarball file of the DDR firmware └── unknown revision Tarball file of the TF-A source code
- The FIP artifacts directory is named FIP_artifacts:
FIP_artifacts ├── arm-trusted-firmware │ ├── bl31 │ │ ├── stm32mp257f-dk-bl31-optee.dtb │ │ ├── stm32mp257f-ev1-bl31-optee.dtb │ │ ├── stm32mp257f-ev1-ca35tdcid-ostl-bl31-optee.dtb │ │ ├── stm32mp257f-ev1-ca35tdcid-ostl-m33-examples-bl31-optee.dtb │ │ └── tf-a-bl31-stm32mp25-optee.bin │ ├── ddr │ │ └── ddr_pmu-stm32mp25[*].bin DDR firmware → STM32MP25 boards │ ├── fwconfig │ │ └── stm32mp25[*]-optee.dtb Device tree for FW config → STM32MP25 boards │ ├── metadata.bin Store boot information │ └── tf-a-stm32mp257[*].stm32 FSBL binary → STM32MP25 boards ├── fip │ ├── fip-stm32mp257f-dk-ddr.bin │ ├── fip-stm32mp257f-dk-optee.bin │ ├── fip-stm32mp257f-ev1-ca35tdcid-ostl-ddr.bin │ ├── fip-stm32mp257f-ev1-ca35tdcid-ostl-m33-examples-ddr.bin │ ├── fip-stm32mp257f-ev1-ca35tdcid-ostl-m33-examples-optee.bin │ ├── fip-stm32mp257f-ev1-ca35tdcid-ostl-optee.bin │ ├── fip-stm32mp257f-ev1-ddr.bin │ └── fip-stm32mp257f-ev1-optee.bin ├── optee │ ├── tee-header_v2-stm32mp25[*].bin Binary file for OP-TEE OS → STM32MP25 boards │ ├── tee-pageable_v2-stm32mp25[*].bin Binary file for OP-TEE OS → STM32MP25 boards │ └── tee-pager_v2-stm32mp25[*].bin Binary file for OP-TEE OS → STM32MP25 boards └── u-boot ├── u-boot-nodtb-stm32mp25.bin └── u-boot-stm32mp25[*].dtb Device tree for U-Boot → STM32MP5 boards
- The debug symbol files are located under the <Developer Package installation directory>/unknown revision directory: