Last edited one month ago

Which STM32MPU Embedded Software Package for Android better suits your needs

Applicable for STM32MP25x lines

Warning DB.png Important
OpenSTDroid is validated against the ecosystem release v5.1.0 . It has not been ported yet on ecosystem release v6.0.0 More info.png .

The STM32MPU Embedded Software distribution for Android™ for STM32 microprocessor platforms supports two software Packages:

  • The Starter Package to quickly and easily start with any STM32MP microprocessor device. The Starter Package is generated from the Distribution Package.
  • The Distribution Package to create your own Android™ distribution, your own Starter Package and your own Developer Package.

Compared to the STM32MPU Embedded Software distribution (based on the OpenSTLinux distribution), no Developer Package is delivered, for this STM32MPU Embedded Software distribution for Android™, in the current release (even if shown in below generic figure).

STM32MPU Embedded Software distribution Packages


This article describes in details the above Packages ("ways of working") and helps finding the one that best fits your use case. Packages are standalone, but they are not isolated one from the others: there are gateways between them.

This article starts by an overview of the STM32MPU Embedded Software distribution for Android components.

1. Overview of STM32MPU Embedded Software distribution for Android components[edit | edit source]

The STM32MPU Embedded Software distribution for Android includes the following components:

  • Binaries: software images
  • Source code for:
    • The OpenSTDroid distribution application frameworks (including when required source code for TF-A, OP-TEE, U-Boot and Linux® kernel) running on Arm® Cortex®-A processor(s)
    • The STM32Cube MPU Package running on Arm® Cortex®-M processor(s)
  • Android build framework
  • Documentation and tools such as:
    • The present wiki
    • The STM32CubeProgrammer
    • Integrated development environments (IDE)

Each of the two Packages described below is made of some of the above components.

2. Starter Package[edit | edit source]

This Package allows to quickly and easily get any STM32 microprocessor development platform up and running.
An STM32 microprocessor development platform (such as STM32MP257x-EV1 Evaluation board) is all what is required to discover the platform capabilities. No integrated development environment (IDE), no software development kit (SDK) are needed: just use the development platform as an Android™ device.

What are the main use cases that can be covered with this Package?

  • Evaluation of the STM32 microprocessor device and development platform (such as internal peripherals and performance)


For more information on the Starter Package depending on your development platform, refer to the corresponding Starter Package article named Your_development_platform - Starter Package for Android.
Example: STM32MP25 Evaluation boards - Starter Package for Android for the STM32MP25 Evaluation boards.
All Starter Package articles belong to the Category:Starter Package.


Switch to the next Package if you need to:

  • modify or tune the BSP (TF-A, U-Boot, OP-TEE and Linux®) or/and the application frameworks of the STM32MPU distribution for Android
  • create your own distribution (e.g. to integrate and share pieces of software from open source communities or third parties)
  • generate your own images

3. Distribution Package[edit | edit source]

This Package allows the creation of a new distribution with a final objective of productization.
It includes the source code for all the pieces of software present in the STM32MPU Embedded Software distribution for Android, plus a build framework. A host PC is required to operate this Package (a Linux® host PC is even strongly recommended).

What are the main use cases that can be covered with this Package?

  • Creation of your own distribution for Android
    • to tune the system configuration options (such as memory sizes, resource allocation, debug options...)
    • to share all the developments within your team (software baseline)
    • to prepare the final software for productization
  • Integration of the following software in this distribution:
    • your developments made thanks to the Developer Package
    • pieces of software coming from open source communities or third parties
    • Integrate your Cube M4 firmware projects in your own distribution (binary)
  • Generation of your own Starter Package images


For more information on the Distribution Package for a given STM32 microprocessor Series, refer to the corresponding Distribution Package article named STM32MP_microprocessors_series Distribution Package for Android.
Example: STM32MPU Distribution Package for Android for the STM32MP2 microprocessors Series. All Distribution Package articles belong to the Category:Distribution Package.