The objective of this article is to describe the content of STM32MP15-Ecosystem-v2.0.0 release of STM32MPU Embedded Software distributions and its associated ecosystem.
1. Delivery purpose and scope[edit source]
The new STM32MP15-Ecosystem-v2.0.0 release is dedicated to STM32MP15 microprocessors. It is an evolutive maintenance release based on new communities components version (Yocto LTS Dunfell, Kernel 5.4 LTS, U-BOOT v2020-01, TF-A 2.2, OP-TEE 3.9).
Like previous release, STM32MP15-Ecosystem-v2.0.0 aims at
- providing a full ecosystem for STM32MP15x devices
- working efficiently with STM32MP15 boards, using one of the packages (Starter Package, Developer Package or Distribution Package) developed by STMicroelectronics for STM32 MPUs.
Refer to Which Package better suits your needs for more information on these packages.
This ecosystem release consists of:
- two STM32MPU distributions
- the STM32MPU Embedded Software distribution
- the STM32MPU Embedded Software distribution for Android
- STM32 referenced tools
- STM32CubeIDE
- STM32CubeMX
- STM32CubeProgrammer
- Keygen tool
- Signing tool
- For more details refer to Referenced tools release notes chapter below.
- Documentation
- The present user guide in wiki format
- Documentation package (for more details refer to Reference documents chapter below)
- Supported STM32MP15 boards
- STM32MP15 Evaluation board ( for "STM32MPU Embedded Software distribution" and "STM32MPU Embedded Software distribution for Android")
- STM32MP15 Discovery kit (for STM32MPU Embedded Software distribution)
- More details can be found in Board chapter below.
2. Intended audience[edit source]
The targeted audience is STMicroelectronics customers.
3. Licensing[edit source]
This software package is licensed under a SOFTWARE LICENSE AGREEMENT FOR ST MATERIALS (SLA). The customers may not use this package except in compliance with the software license agreement (SLA).
4. Main features / main highlights[edit source]
4.1. Boards[edit source]
This STM32MP15-Ecosystem-v2.0.0 release supports the same boards as STM32MP15-Ecosystem-v1.0.0 + 1 new board STM32MP157F-EV1.
| Boards | PCBs list | Content | Availability |
|---|---|---|---|
| STM32MP157C-EV1 board (board with Crypto) |
|
|
Jan'19 |
| STM32MP157A-EV1 board (board without Crypto) |
|
|
Jan'19 |
| NEW STM32MP157F-EV1 board (board with Crypto and MP15 at 800MHz) |
|
|
Jun'20 |
| STM32MP157C-DK2 board (board with Crypto) |
|
|
Jan'19 |
| STM32MP157A-DK1 board (board without Crypto) |
|
|
Jan'19 |
4.2. Embedded software[edit source]
4.2.1. OpenSTLinux (Cortex®-A7)[edit source]
Openstlinux-5.4-dunfell-mp1-20-06-24 is the new version delivered with STM32MP15-Ecosystem-v2.0.0 release. This software set consists of the following components:
- Build process
- OpenEmbedded LTS Dunfell (v3.1) - NEW version versus STM32MP15-Ecosystem-v1.2.0 release
- GCC version v8.2 - NEW version versus STM32MP15-Ecosystem-v1.2.0 release
- Software components
- Kernel version LTS v5.4.x - NEW version versus STM32MP15-Ecosystem-v1.2.0 release
- TF-A version v2.2 - NEW version versus STM32MP15-Ecosystem-v1.2.0 release
- U-Boot version v2020.01 - NEW version versus STM32MP15-Ecosystem-v1.2.0 release
- OP-TEE version v3.9.0 - NEW version versus STM32MP15-Ecosystem-v1.2.0 release
- OpenOCD version v0.10.0 - NEW version versus STM32MP15-Ecosystem-v1.2.0 release
- Applicative components
- Weston version v5.0.0 - NEW version versus STM32MP15-Ecosystem-v1.2.0 release
- GStreamer version v1.14.4 - NEW version versus STM32MP15-Ecosystem-v1.2.0 release
- GCnano version v6.4.0 - NEW version versus STM32MP15-Ecosystem-v1.2.0 release
- Main NEW features coming with STM32MP15-Ecosystem-v2.0.0 release
- Added support for new 800 MHz Boards STM32MP157F-EV1
- SCMI - SCMI support for clocks and resets
- The system control and management interface (SCMI) is an OS independent interface proposed by ARM implemented in the secure monitor (TF-A sp_min or OP-TEE) and called by the application (U-Boot, Linux) for clock and reset management. It allows a centralized control of those system resources, with filtering possibilities.
- Support DVFS 800 MHz - 400 MHz
- Operating points DT management wiki article - refer to How_to_change_the_CPU_frequency article
- SNAND - Full SPI Nand support including boot and flash
- SoC and Boards device tree new split
- 1 device tree per board CPN, dtsi device trees splitted between SoC Product lines, SoC extensions (security and Cortex A frequency) and SoC package types - refer to STM32MP15_device_tree article
- OpenSTLinux debug with gdb management
- refer GDB and Wrapper_for_FSBL_images articles
- Basic boot removed except for DDR tuning tool
- ST boot reference is the Trusted with TF-A=>U-BOOT=>Kernel
- UART RS485 support
- Yocto build process
- SSP feature (Secure Secrets Provisonning) delivered with a specific TF-A branch managed with a dedicated Yocto recipe tf-a-stm32mp-ssp_2.2.bb
- A dedicated Yocto recipe is also added to manage the TF-A for serial boot tf-a-stm32mp-serialboot_2.2.bb additionally to tf-a-stm32mp_2.2.bb. The 2 recipes are included in ST yocto images. It allows to use a dedicated TF-A binary for serial boot with STM32CubeProg tool and to save size for the TF-A binary used for the product
- Internal peripheral assignment at boot time
- At boot time, you can select two kernel configurations:
- Configuration 1: all internal peripherals are assigned to Cortex-A7 for Linux drivers. Cortex-M4 coprocessing firmware TTY is executed by default.
- Configuration 2: some internal peripherals are assigned to Cortex-M4 to execute Cortex-M4 delivered examples on the board (EVAL or DISCO) see (How to run Cortex-M4 examples).
- Configuration 1 is activated by default if you do not specify "2" in the U-Boot console.
- More information can be found in How to assign an internal peripheral to a runtime context article.
4.2.2. STM32CubeMP1 (Cortex®-M4)[edit source]
- STM32CubeMP1-v1.2.0 version same as STM32MP15-Ecosystem-v1.2.0 release
4.2.3. STM32MP15 distribution for Android (Cortex®-A7) - NEW[edit source]
STM32MP15 distribution for Android™ v1.1.0 (st-android-10.0.0-2020-02-21 tag) is the version delivered within STM32MP15-Ecosystem-v1.2.0 release.
The objectives of this release are the following:
- Android™ 10.0.0 porting on OpenSTLinux BSP v1.2.0 (TF-A, U-Boot, OP-TEE, Linux kernel), provided as demonstrator
- Android™ certifications are not ensured
See STM32MP15 distribution for Android release note for more details.
4.3. STM32CubeProgrammer, Signing tool, Keygen[edit source]
STM32CubeProgrammer v2.4.0 is the version delivered within STM32MP15-Ecosystem-v1.2.0 release. This is an evolutive maintenance release for STM32CubeProgrammer.
- Main NEW features coming with STM32CubeProgrammer-v2.4.0 version, delivered within STM32MP15-Ecosystem-v1.2.0 release:
- Flashload speed improvement over USB on Windows PC
- Parallel programming on several targets
- Features already available in previous version
- STM32CubeProg installer includes STM32CubeProgrammer, Keygen and Signing tools
- Flashload SDCard, eMMC, NAND, NOR images through USB and UART for STM32MP157C-EV1, STM32MP157A-DK1, STM32MP157C-DK2 boards
- Private and public keys generation
- Images signature
- Flashlayout file format change
- STM32MP1 fuses management (with console interface only)
- PMIC NVM management (with console interface only)
4.4. STM32CubeMX[edit source]
STM32CubeMX-v5.6 is the version delivered within STM32MP15-Ecosystem-v1.2.0 release
- Main NEW features coming with STM32CubeMX-v5.6 version, delivered within STM32MP15-Ecosystem-v1.2.0 release
- Added support for new D and F part numbers
- Device tree (A7)
- Device tree compliance with Openstlinux-20-02-19
- DDR
- Added support for LPDDR on 18x18, 16x16 packages
- DDR tuning parameters saving: see the restriction below in this article
- STM32CubeMP1 (M4)
- Compliance with STM32CubeMP1 V1.2.0
- Added support for Engineering mode
- Added support for SMBus alert bit
- PCC : Power data update
- Added tutorial Videos
- Features already available in previous version
- I/O muxing and clock tree configuration
- STM32MP1 contexts management (A7 non-secure, A7 secure, M4)
- Device tree code generation
- dtsi and header file inclusions
- pinctrl and clock generation
- System-on-chip device node positioning
- multi-core related configurations (ETZPC binding, resources manager binding, peripheral assignment).
- ST32MP1Cube code generation
- Tuning of DDR settings
4.5. STM32CubeIDE[edit source]
STM32CubeIDE V1.3.0 is the version delivered within STM32MP15-Ecosystem-v1.2.0 release.
- Main NEW features coming with STM32CubeIDE V1.3.0 version, delivered within STM32MP15-Ecosystem-v1.2.0 release
- Added support for new D and F part numbers
- Features already available in previous version
- Cortex-M4 STM32CubeMP1 in "Production mode" and "Engineering mode"
- Cortex-M4 Firmware compilation, loading and debugging
- PC Linux with Ethernet (recommended) or serial link
- PC Windows with Ethernet or Ethernet over USB link
- Cortex-M4 Firmware installation directory configurable
4.6. Miscellaneous[edit source]
- Detailed features are available in the release notes of the different components of this delivery.
- See sections STM32MPU Embedded Software distribution detailed release notes, Referenced tools release notes and Reference documents
5. Main restrictions[edit source]
5.1. Embedded software[edit source]
5.1.1. OpenSTLinux (Cortex®-A7)[edit source]
- On STM32MP157C-DK2 boards, BT stack does not work any more after suspend / resume in Standby mode (function with Stop mode). This issue is linked to the Murata Wi-Fi/BT module that expects the 3.3 V supply to be kept, while this supply is switched off in STM32MP1 Standby mode. A similar workaround as for Wi-Fi can be used (GitHub patch). it consists in calling BT unbind and bind drivers before and after resume (modprobe -r hci_uart && modprobe hci_uart).
- For DDR initialization in TF-A, it is recommended to set up and enable all "boot-on" and "always-on" regulators at bootloader stage, after DDR power initialization. This is not yet implemented in V1.2.0 delivery. A patch is being prepared and will be available on GitHub.
5.1.2. STM32CubeMP1 (Cortex®-M4)[edit source]
- To avoid errors in OpenAMP when compiling in MDK-ARM IDE, disable the « Use MicroLIB » in « Target » tab.
- The HAL RTC is delivered within this release. However use it with caution since this driver is also used by Linux. To remove any risk of contention between Linux and the HAL, proceed as follows:
- The write protect (wpr) must be disabled by default and it must never be enabled in any driver (Linux nor HAL).
- The HAL must use only Alarm B, since Linux uses Alarm A.
- The RTC interrupt must be shared between Linux and the HAL to be able to receive alarm notifications on both sides.
5.2. STM32CubeProgrammer, Signing tool and Keygen[edit source]
- Flashload through UART fails
- Key generation is not functional with STM32MP_KeyGen_CLI on Linux under Ubuntu 16.04 (functional with Ubuntu 18.04)
5.3. STM32CubeMX[edit source]
- MR0 register for LPDDR settings is not set by STM32CubeMX in the generated device tree. This register must be set manually at 0.
- DDR tuning parameters saving does not work when DDR Test Suite tool is used. Use U-Boot tag v2018.11-stm32mp-r4.1 on top of the ecosystem release v1.2.0 . This tag contains only one patch required by STM32CubeMX v5.6 ("ram: stm32mp1: display result for software read DQS gating").
- Warning: when opening a previous project built with STM32CubeMX version older than V5.6, the migration does not take into account the user section part. This part needs to be updated manually according the Openstlinux-20-02-19 manifest.
5.4. STM32CubeIDE[edit source]
- Using OpenOCD with ST-LINK does not check and force ST-LINK firmware update at debug launch. It is therefore recommended to manually update to the latest ST-LINK firmware for the best debug experience. Use the Help > ST-LINK Upgrade menu"
5.5. Miscelleanous[edit source]
Restriction lists are available in each subcomponent release note. They are available in the following chapters in the present article:
Moreover, the software workarounds implemented in the ecosystem to provide solutions to the STM32MPU device errata are listed in STM32MP15 ecosystem errata sheet.
6. Minor release updates[edit source]
STMicroelectronics regularly delivers updates through the following github® components: tf-a, u-boot, optee-os, Linux kernel.
You can decide to incorporate them into your Developer Package (refer to STM32MP1 Developer Package or Distribution Package below).
To update the Distribution package, proceed as follows:
- Switch your Distribution package reference source code to github mode.
- Use the devtool modify <recipe name> command to have direct access to the source code git repository used by the build process.
- In the freshly cloned source code, check out the revision you want to start from via git checkout -b WORK <github® TAG>.
STMicroelectronics also delivers dedicated fixes on layers through github®. These changes can be integrated (via git commands) into your local STM32MP1 Distribution Package environment. Below the github® links corresponding to each layers:
6.1. v1.2.1[edit source]
7. Reference documents[edit source]
8. How to download the software and start with this release?[edit source]
The list of embedded software packages available for download depends on the selected package.
The table below provides the available board part numbers as well as information in order to:
- get started with one of the three available Packages (Starter, Developer or Distribution Package)
- get started with the board
- find the associated embedded software distributions
- download source code
- build an embedded software
| Board part number | Jump to |
|---|---|
| STM32MP157C-EV1 Evaluation board |
STM32MP15 Evaluation boards - getting started, including software download |
| STM32MP157X-DKX Discovery kit |
STM32MP15 Discovery kits - getting started, including software download |
9. STM32MPU Embedded Software distribution detailed release notes[edit source]
The table below lists the software packages available in the STM32MPU Embedded Software distributions, and provides the corresponding release notes.
The release notes give more information and details about the features and content of the packages.
They do not explain how to download the software. Refer to How to get the software and start with this release .
| Firmware | Release note | Version |
| OpenSTLinux Distribution | STM32MP15 OpenSTLinux release note - v1.2.0 | openstlinux-20-02-19 |
| STM32Cube MPU Package | STM32CubeMP1 Package release note - v1.2.0 | STM32CubeMP1-v1.2.0 |
| STM32 MPU Distribution for Android | STM32MP15 distribution for Android release note - v1.1.0 | st-android-10.0.0-2020-02-21 |
10. Referenced tools release notes[edit source]
The table below lists the available tools, and provides links to the corresponding release notes.
Each release note gives information on how to install and use the corresponding tool.
The set of tools that can be downloaded depends on the Package that is used (double check Which Package better suits your needs article for more information on each Package).
| Tools | Release notes | Host PC | Which Package may need the tool ? | |||
| Linux version | Windows version | Starter Package | Developer Package | Distribution Package | ||
| STM32CubeIDE | STM32CubeIDE_release_note | 1.3.0 | 1.3.0 | ☐ | ☑ | ☐ |
| STM32CubeMX | STM32CubeMX release note | from 5.6 | from 5.6 | ☐ | ☑ | ☑ |
| STM32CubeProg | STM32CubeProgrammer release note | 2.4.0 | 2.4.0 | ☑ | ☐ | ☑ |
| Keygen | KeyGen release note | 1.0.0 | 1.0.0 | ☑ | ☑ | ☑ |
| Signing tool | Signing tool release note | 1.0.0 | 1.0.0 | ☑ | ☑ | ☑ |
11. References[edit source]