Last edited 4 months ago

STM32MP1 Developer Package - OpenSTLinux BSP: Difference between revisions


Latest revision as of 17:00, 13 November 2024

This article aims at giving the following information:

  • How to get the latest OP-TEE, TF-A, U-Boot, Linux® kernel, gcnano-driver and debug symbols for the STM32 microprocessor series
  • Where to find the associated release note
  • Where to find the previous releases (archives)

1. STM32MP1 ecosystem v6.0.0 release[edit | 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 (SLA). The detailed content licenses can be found here.

  • The OpenSTLinux BSP package is delivered through a tarball file named unknown revision for STM32MP157x-EV1 More info green.png, STM32MP157x-DKx More info green.png and STM32MP135x-DK Warning.png boards.

  • Download and install the STM32MP1 OpenSTLinux BSP package.
STM32MP1 Developer Package - STM32MP1 ecosystem v6.0.0 release
Download
  • Go on st.com to download the STM32MP1 Developer Package, unknown revision file.
Installation
cd <working directory path>/Developer-Package
tar xvf unknown revision 
Release note

Details about the content of the OpenSTLinux BSP package are available in the associated STM32 MPU OpenSTLinux release note.

Archive box.png For information on older releases, go to Archives.

  • In the <Developer Package installation directory>/unknown revision , a tarball archive of the OpenSTLinux BSP components can be found.
  • 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
├── 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
  • 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)
├── fiptool-stm32mp					tool for fip generation
├── unknown revision 			U-Boot source code directory
├── 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)
├── fiptool-stm32mp					tool for fip generation
├── unknown revision 		TF-A source code directory
├── 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
└── unknown revision 	Tarball file of the TF-A source code
  • 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)
├── fiptool-stm32mp					tool for fip generation
├── unknown revision 			OP-TEE source code directory
├── 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 FIP artifacts directory is named FIP_artifacts:
FIP_artifacts
├── arm-trusted-firmware
│   ├── fwconfig
│   │   ├── stm32mp13[*]-fw-config-[optee/opteemin]-sdcard.dtb		Device tree for FW config → STM32MP13 boards
│   │   ├── stm32mp13[*]-fw-config-[optee/opteemin]-programmer-[uart/usb].dtb		Device tree for FW config → STM32MP13 boards
│   │   ├── stm32mp15[*]-fw-config-[optee/opteemin]-[storage].dtb		Device tree for FW config → STM32MP15 boards
│   │   └── stm32mp15[*]-fw-config-[optee/opteemin]-programmer-[uart/usb].dtb		Device tree for FW config → STM32MP15 boards
│   ├── metada.bin					Store boot information
│   ├── tf-a-stm32mp13[*].stm32				FSBL binary→ STM32MP13 boards
│   └── tf-a-stm32mp15[*].stm32				FSBL binary → STM32MP15 boards
├── optee
│   ├── tee-header_v2-stm32mp13[*].bin			Binary file for OP-TEE OS → STM32MP13 boards
│   ├── tee-header_v2-stm32mp15[*].bin			Binary file for OP-TEE OS → STM32MP15 kits
│   ├── tee-pageable_v2-stm32mp13[*].bin		Binary file for OP-TEE OS → STM32MP13 boards
│   ├── tee-pageable_v2-stm32mp15[*].bin		Binary file for OP-TEE OS → STM32MP15 boards
│   ├── tee-pager_v2-stm32mp13[*].bin			Binary file for OP-TEE OS → STM32MP13 boards
│   └── tee-pager_v2-stm32mp15[*].bin			Binary file for OP-TEE OS → STM32MP15 boards
└── u-boot
    ├── u-boot-nodtb-stm32mp13-default.bin
    ├── u-boot-nodtb-stm32mp15-default.bin
    ├── u-boot-nodtb-stm32mp13-fastboot-sdcard.bin	Binary file for fastboot on SD-Card for STM32MP13 boards
    ├── u-boot-nodtb-stm32mp15-fastboot-emmc.bin	Binary file for fastboot on eMMC for STM32MP15 boards
    ├── u-boot-nodtb-stm32mp15-fastboot-sdcard.bin	Binary file for fastboot on SD-Card for STM32MP15 boards
    ├── u-boot-stm32mp13[*].dtb				Device tree for U-Boot → STM32MP13 boards
    └── u-boot-stm32mp15[*].dtb				Device tree for U-Boot → STM32MP15 boards
  • The debug symbol files are located under the <Developer Package installation directory>/unknown revision directory:


2. Archives Archive box.png[edit | edit source]

This wiki is for the v4 ecosystem releases. For information about the previous ecosystem releases, go through the Wiki archives.