STM32MP1 Developer Package - SDK: Difference between revisions

Latest revision as of 14:39, 19 June 2024↑

Applicable for

This article aims to give the following information:

How to download and install the latest SDK for the STM32 microprocessor series.
Where to find the associated release note.
Where to find the previous releases (archives).

Warning

To use efficiently this SDK, please go through the Developer Package article relative to your STM32 microprocessor series: Category:Developer Package

1. STM32MPU-Ecosystem-v5.1.0 release[edit | edit source]↑

The STM32MP1 SDK is delivered through two tarball file named :

unknown revision for x86_64 host architecture
unknown revision for arm64 host architecture

Download and install the STM32MP1 SDK. 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.

Warning

To download a package, it is recommended to be logged in to your "myst" account [1]. If, trying to download, you encounter a “403 error”, you could try to empty your browser cache to workaround the problem. We are working on the resolution of this problem.
We apologize for this inconvenience

	STM32MP1 Developer Package SDK - STM32MP1-Ecosystem-v5.1.0 release
Download	Go on st.com to download unknown revision file for x86_64 host architecture unknown revision file for arm64 host architecture
Installation	For x86_64 host architecture Uncompress the tarball file to get the SDK installation script. tar xvf unknown revision If needed, change the permissions on the SDK installation script so that it is executable. chmod +x unknown revision /unknown revision Run the SDK installation script. Use the -d <SDK installation directory absolute path> option to specify the absolute path to the directory in which you want to install the SDK (<SDK installation directory>). If you follow the proposition to organize the working directory, it means: ./unknown revision /unknown revision -d <working directory absolute path>/Developer-Package/SDK A successful installation outputs the following log: ST OpenSTLinux - Weston - (A Yocto Project Based Distro) SDK installer version 4.2.4-openstlinux-6.1-yocto-mickledore-mp1-v24.06.26 =================================================================================================================================== You are about to install the SDK to "<working directory absolute path>/Developer-Package/SDK". Proceed [Y/n]? Extracting SDK.........................................................................................................................................................................................................................done Setting it up...done SDK has been successfully set up and is ready to be used. Each time you wish to use the SDK in a new shell session, you need to source the environment setup script e.g. $ . <working directory absolute path>/Developer-Package/SDK/environment-setup-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi
Installation	Expand For arm64 host architecture tar xvf unknown revision If needed, change the permissions on the SDK installation script so that it is executable. chmod +x unknown revision /unknown revision Run the SDK installation script. Use the -d <SDK installation directory absolute path> option to specify the absolute path to the directory in which you want to install the SDK (<SDK installation directory>). If you follow the proposition to organize the working directory, it means: ./unknown revision /unknown revision -d <working directory absolute path>/Developer-Package/SDK A successful installation outputs the following log: ST OpenSTLinux - Weston - (A Yocto Project Based Distro) SDK installer version 4.2.1-openstlinux-6.1-yocto-mickledore-mp1-v23.06.21 =================================================================================================================================== You are about to install the SDK to "<working directory absolute path>/Developer-Package/SDK". Proceed [Y/n]? Extracting SDK.........................................................................................................................................................................................................................done Setting it up...done SDK has been successfully set up and is ready to be used. Each time you wish to use the SDK in a new shell session, you need to source the environment setup script e.g. $ . <working directory absolute path>/Developer-Package/SDK/environment-setup-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi
Release note	Details about the content of the SDK are available in the associated STM32 MPU ecosystem release note. If you are interested in older releases, please have a look into the section Archives.

The SDK is in the <SDK installation directory>:

<SDK installation directory>                                      SDK for OpenSTLinux distribution: details in Standard SDK directory structure article
├── environment-setup-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi  Environment setup script for Developer Package
├── site-config-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi
├── sysroots
│   ├── cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi                Target sysroot (libraries, headers, and symbols)
│   │   └── [...]
│   └── x86_64-ostl_sdk-linux                                     Native sysroot (libraries, headers, and symbols)
│       └── [...]
└── version-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi

Expand

For arm64 host architecture

<SDK installation directory>                                      SDK for OpenSTLinux distribution: details in Standard SDK directory structure article
├── environment-setup-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi  Environment setup script for Developer Package
├── site-config-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi
├── sysroots
│   ├── cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi                Target sysroot (libraries, headers, and symbols)
│   │   └── [...]
│   └── aarch64-ostl_sdk-linux                                     Native sysroot (libraries, headers, and symbols)
│       └── [...]
└── version-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi

2. Archives [edit | edit source]↑

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

Expand

2.1. STM32MPU-Ecosystem-v5.0.0 release[edit | edit source]↑

The STM32MP1 SDK is delivered through two tarball file named :

en.SDK-x86_64-stm32mp1-openstlinux-6.1-yocto-mickledore-mp1-v23.06.21.tar.gz for x86_64 host architecture
en.SDK-aarch64-stm32mp1-openstlinux-6.1-yocto-mickledore-mp1-v23.06.21.tar.gz for arm64 host architecture

Download and install the STM32MP1 SDK. 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.

Warning

To download a package, it is recommended to be logged in to your "myst" account [2]. If, trying to download, you encounter a “403 error”, you could try to empty your browser cache to workaround the problem. We are working on the resolution of this problem.
We apologize for this inconvenience

	STM32MP1 Developer Package SDK - STM32MP1-Ecosystem-v5.0.0 release
Download	Go on st.com to download en.SDK-x86_64-stm32mp1-openstlinux-6.1-yocto-mickledore-mp1-v23.06.21.tar.gz file for x86_64 host architecture en.SDK-aarch64-stm32mp1-openstlinux-6.1-yocto-mickledore-mp1-v23.06.21.tar.gz file for arm64 host architecture
Installation	For x86_64 host architecture Uncompress the tarball file to get the SDK installation script. tar xvf en.SDK-x86_64-stm32mp1-openstlinux-6.1-yocto-mickledore-mp1-v23.06.21.tar.gz If needed, change the permissions on the SDK installation script so that it is executable. chmod +x stm32mp1-openstlinux-6.1-yocto-mickledore-mp1-v23.06.21/sdk/st-image-weston-openstlinux-weston-stm32mp1-x86_64-toolchain-4.2.1-openstlinux-6.1-yocto-mickledore-mp1-v23.06.21.sh Run the SDK installation script. Use the -d <SDK installation directory absolute path> option to specify the absolute path to the directory in which you want to install the SDK (<SDK installation directory>). If you follow the proposition to organize the working directory, it means: ./stm32mp1-openstlinux-6.1-yocto-mickledore-mp1-v23.06.21/sdk/st-image-weston-openstlinux-weston-stm32mp1-x86_64-toolchain-4.2.1-openstlinux-6.1-yocto-mickledore-mp1-v23.06.21.sh -d <working directory absolute path>/Developer-Package/SDK A successful installation outputs the following log: ST OpenSTLinux - Weston - (A Yocto Project Based Distro) SDK installer version 4.2.1-openstlinux-6.1-yocto-mickledore-mp1-v23.06.21 =================================================================================================================================== You are about to install the SDK to "<working directory absolute path>/Developer-Package/SDK". Proceed [Y/n]? Extracting SDK.........................................................................................................................................................................................................................done Setting it up...done SDK has been successfully set up and is ready to be used. Each time you wish to use the SDK in a new shell session, you need to source the environment setup script e.g. $ . <working directory absolute path>/Developer-Package/SDK/environment-setup-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi
Installation	Expand For arm64 host architecture tar xvf en.SDK-aarch64-stm32mp1-openstlinux-6.1-yocto-mickledore-mp1-v23.06.21.tar.gz If needed, change the permissions on the SDK installation script so that it is executable. chmod +x stm32mp1-openstlinux-6.1-yocto-mickledore-mp1-v23.06.21/sdk/st-image-weston-openstlinux-weston-stm32mp1-aarch64-toolchain-4.2.1-openstlinux-6.1-yocto-mickledore-mp1-v23.06.21.sh Run the SDK installation script. Use the -d <SDK installation directory absolute path> option to specify the absolute path to the directory in which you want to install the SDK (<SDK installation directory>). If you follow the proposition to organize the working directory, it means: ./stm32mp1-openstlinux-6.1-yocto-mickledore-mp1-v23.06.21/sdk/st-image-weston-openstlinux-weston-stm32mp1-aarch64-toolchain-4.2.1-openstlinux-6.1-yocto-mickledore-mp1-v23.06.21.sh -d <working directory absolute path>/Developer-Package/SDK A successful installation outputs the following log: ST OpenSTLinux - Weston - (A Yocto Project Based Distro) SDK installer version 4.2.1-openstlinux-6.1-yocto-mickledore-mp1-v23.06.21 =================================================================================================================================== You are about to install the SDK to "<working directory absolute path>/Developer-Package/SDK". Proceed [Y/n]? Extracting SDK.........................................................................................................................................................................................................................done Setting it up...done SDK has been successfully set up and is ready to be used. Each time you wish to use the SDK in a new shell session, you need to source the environment setup script e.g. $ . <working directory absolute path>/Developer-Package/SDK/environment-setup-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi
Release note	Details about the content of the SDK are available in the associated STM32 MPU ecosystem release note. If you are interested in older releases, please have a look into the section Archives.

The SDK is in the <SDK installation directory>:

<SDK installation directory>                                      SDK for OpenSTLinux distribution: details in Standard SDK directory structure article
├── environment-setup-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi  Environment setup script for Developer Package
├── site-config-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi
├── sysroots
│   ├── cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi                Target sysroot (libraries, headers, and symbols)
│   │   └── [...]
│   └── x86_64-ostl_sdk-linux                                     Native sysroot (libraries, headers, and symbols)
│       └── [...]
└── version-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi

Expand

For arm64 host architecture

<SDK installation directory>                                      SDK for OpenSTLinux distribution: details in Standard SDK directory structure article
├── environment-setup-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi  Environment setup script for Developer Package
├── site-config-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi
├── sysroots
│   ├── cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi                Target sysroot (libraries, headers, and symbols)
│   │   └── [...]
│   └── aarch64-ostl_sdk-linux                                     Native sysroot (libraries, headers, and symbols)
│       └── [...]
└── version-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi

@@ Line 11: / Line 11: @@
 {{Warning|To use efficiently this SDK, please go through the Developer Package article relative to your STM32 microprocessor series: [[:Category:Developer Package]]}}
-==STM32MPU-Ecosystem-v5.0.0 release ==
+==STM32MPU-Ecosystem-v5.1.0 release ==
 </noinclude>
+The STM32MP1 SDK is delivered through two tarball file named :
+* '''{{EcosystemRelease/Package | revision=5.1.0 | package=SDK package | request=name}}''' for {{highlight|x86_64 host architecture}}
+* '''{{EcosystemRelease/Package | revision=5.1.0 | package=SDK-arm64 package | request=name}}''' for {{highlight|arm64 host architecture}}
+<span id="Download"></span>
+Download and install the STM32MP1 SDK.
+{{SoftwareLicenseAgreement | distribution=OpenSTLinux}}
+{| class="st-table"
+|-
+!  !!style="text-align:center;"|STM32MP1 Developer Package SDK - STM32MP1-Ecosystem-v5.1.0 release
+|-
+| Download ||
+* Go on [https://www.st.com/en/embedded-software/stm32mp1dev.html#get-software st.com] to download
+** '''{{EcosystemRelease/Package | revision=5.1.0 | package=SDK package | request=name}}''' file for x86_64 host architecture
+** '''{{EcosystemRelease/Package | revision=5.1.0 | package=SDK-arm64 package | request=name}}''' file for arm64 host architecture
+|-
+| rowspan="2" | Installation
+| For '''x86_64''' host architecture
+* Uncompress the tarball file to get the SDK installation script.
+ {{PC$}}tar xvf {{EcosystemRelease/Package | revision=5.1.0 | package=SDK package | request=name}}
+* If needed, change the permissions on the SDK installation script so that it is executable.
+<div style="max-width:60em;">
+ {{PC$}}chmod +x {{EcosystemRelease/Package | revision=5.1.0 | package=SDK installation script | request=path}}/{{EcosystemRelease/Package | revision=5.1.0 | package=SDK installation script | request=name}}
+</div>
+* Run the SDK installation script.
+** Use the ''-d <SDK installation directory absolute path>'' option to specify the absolute path to the directory in which you want to install the SDK (''<SDK installation directory>'').
+** If you follow the [[Example of directory structure for Packages|proposition to organize the working directory]], it means:
+<div style="max-width:60em;">
+ {{PC$}}./{{EcosystemRelease/Package | revision=5.1.0 | package=SDK installation script | request=path}}/{{EcosystemRelease/Package | revision=5.1.0 | package=SDK installation script | request=name}} -d <working directory absolute path>/Developer-Package/SDK
+</div>
+:* A successful installation outputs the following log:
+<pre style="max-width:60em;">
+ST OpenSTLinux - Weston - (A Yocto Project Based Distro) SDK installer version 4.2.4-openstlinux-6.1-yocto-mickledore-mp1-v24.06.26
+===================================================================================================================================
+You are about to install the SDK to "<working directory absolute path>/Developer-Package/SDK". Proceed [Y/n]?
+Extracting SDK.........................................................................................................................................................................................................................done
+Setting it up...done
+SDK has been successfully set up and is ready to be used.
+Each time you wish to use the SDK in a new shell session, you need to source the environment setup script e.g.
+ $ . <working directory absolute path>/Developer-Package/SDK/environment-setup-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi
+</pre>
+|-
+| <div class="mw-collapsible mw-collapsed">
+For '''arm64''' host architecture
+<div class="mw-collapsible-content">
+ {{PC$}}tar xvf {{EcosystemRelease/Package | revision=5.1.0 | package=SDK-arm64 package | request=name}}
+* If needed, change the permissions on the SDK installation script so that it is executable.
+<div style="max-width:60em;">
+ {{PC$}}chmod +x {{EcosystemRelease/Package | revision=5.1.0 | package=SDK-arm64 installation script | request=path}}/{{EcosystemRelease/Package | revision=5.1.0 | package=SDK-arm64 installation script | request=name}}
+</div>
+* Run the SDK installation script.
+** Use the ''-d <SDK installation directory absolute path>'' option to specify the absolute path to the directory in which you want to install the SDK (''<SDK installation directory>'').
+** If you follow the [[Example of directory structure for Packages|proposition to organize the working directory]], it means:
+<div style="max-width:60em;">
+ {{PC$}}./{{EcosystemRelease/Package | revision=5.1.0 | package=SDK-arm64 installation script | request=path}}/{{EcosystemRelease/Package | revision=5.1.0 | package=SDK-arm64 installation script | request=name}} -d <working directory absolute path>/Developer-Package/SDK
+</div>
+:* A successful installation outputs the following log:
+<pre style="max-width:60em;">
+ST OpenSTLinux - Weston - (A Yocto Project Based Distro) SDK installer version 4.2.1-openstlinux-6.1-yocto-mickledore-mp1-v23.06.21
+===================================================================================================================================
+You are about to install the SDK to "<working directory absolute path>/Developer-Package/SDK". Proceed [Y/n]?
+Extracting SDK.........................................................................................................................................................................................................................done
+Setting it up...done
+SDK has been successfully set up and is ready to be used.
+Each time you wish to use the SDK in a new shell session, you need to source the environment setup script e.g.
+ $ . <working directory absolute path>/Developer-Package/SDK/environment-setup-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi
+</pre>
+</div></div>
+|-
+| Release note ||
+Details about the content of the SDK are available in the '''associated''' [[STM32 MPU ecosystem release note - v5.1.0|STM32 MPU ecosystem release note]].
+[[File:Archive_box.png|25px|link=]] If you are interested in older releases, please have a look into the section [[STM32MP1_Developer_Package_-_SDK#Archives|Archives]].
+|}
+* The SDK is in the ''<SDK installation directory>'':
+ {{HighlightParam|<SDK installation directory>}}                                      {{Highlight|'''SDK for OpenSTLinux distribution''': details in [[Standard SDK directory structure]] article}}
+ ├── environment-setup-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi  {{Highlight|'''Environment setup script''' for Developer Package}}
+ ├── site-config-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi
+ ├── {{Green|sysroots}}
+ │   ├── {{Green|cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi}}                {{Highlight|Target sysroot (libraries, headers, and symbols)}}
+ │   │   └── [...]
+ │   └── {{Green|x86_64-ostl_sdk-linux}}                                     {{Highlight|Native sysroot (libraries, headers, and symbols)}}
+ │       └── [...]
+ └── version-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi
+<div class="mw-collapsible mw-collapsed">
+For '''arm64''' host architecture
+<div class="mw-collapsible-content">
+ {{HighlightParam|<SDK installation directory>}}                                      {{Highlight|'''SDK for OpenSTLinux distribution''': details in [[Standard SDK directory structure]] article}}
+ ├── environment-setup-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi  {{Highlight|'''Environment setup script''' for Developer Package}}
+ ├── site-config-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi
+ ├── {{Green|sysroots}}
+ │   ├── {{Green|cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi}}                {{Highlight|Target sysroot (libraries, headers, and symbols)}}
+ │   │   └── [...]
+ │   └── {{Green|aarch64-ostl_sdk-linux}}                                     {{Highlight|Native sysroot (libraries, headers, and symbols)}}
+ │       └── [...]
+ └── version-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi
+</div></div>
+<noinclude>
+==Archives [[File:Archive_box.png|25px|link=]]==
+{{EcosystemFlow/Archives}}
+<div class="mw-collapsible mw-collapsed">
+===STM32MPU-Ecosystem-v5.0.0 release ===
+<div class="mw-collapsible-content">
 The STM32MP1 SDK is delivered through two tarball file named :
 * '''{{EcosystemRelease/Package | revision=5.0.0 | package=SDK package | request=name}}''' for {{highlight|x86_64 host architecture}}
@@ Line 34: / Line 149: @@
 * Uncompress the tarball file to get the SDK installation script.
-  {{PC$}} tar xvf {{EcosystemRelease/Package | revision=5.0.0 | package=SDK package | request=name}}
+  {{PC$}}tar xvf {{EcosystemRelease/Package | revision=5.0.0 | package=SDK package | request=name}}
 * If needed, change the permissions on the SDK installation script so that it is executable.
 <div style="max-width:60em;">
-  {{PC$}} chmod +x {{EcosystemRelease/Package | revision=5.0.0 | package=SDK installation script | request=path}}/{{EcosystemRelease/Package | revision=5.0.0 | package=SDK installation script | request=name}}
+  {{PC$}}chmod +x {{EcosystemRelease/Package | revision=5.0.0 | package=SDK installation script | request=path}}/{{EcosystemRelease/Package | revision=5.0.0 | package=SDK installation script | request=name}}
 </div>
@@ Line 45: / Line 160: @@
 ** If you follow the [[Example of directory structure for Packages|proposition to organize the working directory]], it means:
 <div style="max-width:60em;">
-  {{PC$}} ./{{EcosystemRelease/Package | revision=5.0.0 | package=SDK installation script | request=path}}/{{EcosystemRelease/Package | revision=5.0.0 | package=SDK installation script | request=name}} -d <working directory absolute path>/Developer-Package/SDK
+  {{PC$}}./{{EcosystemRelease/Package | revision=5.0.0 | package=SDK installation script | request=path}}/{{EcosystemRelease/Package | revision=5.0.0 | package=SDK installation script | request=name}} -d <working directory absolute path>/Developer-Package/SDK
 </div>
@@ Line 63: / Line 178: @@
 For '''arm64''' host architecture
 <div class="mw-collapsible-content">
-  {{PC$}} tar xvf {{EcosystemRelease/Package | revision=5.0.0 | package=SDK-arm64 package | request=name}}
+  {{PC$}}tar xvf {{EcosystemRelease/Package | revision=5.0.0 | package=SDK-arm64 package | request=name}}
 * If needed, change the permissions on the SDK installation script so that it is executable.
 <div style="max-width:60em;">
-  {{PC$}} chmod +x {{EcosystemRelease/Package | revision=5.0.0 | package=SDK-arm64 installation script | request=path}}/{{EcosystemRelease/Package | revision=5.0.0 | package=SDK-arm64 installation script | request=name}}
+  {{PC$}}chmod +x {{EcosystemRelease/Package | revision=5.0.0 | package=SDK-arm64 installation script | request=path}}/{{EcosystemRelease/Package | revision=5.0.0 | package=SDK-arm64 installation script | request=name}}
 </div>
@@ Line 74: / Line 189: @@
 ** If you follow the [[Example of directory structure for Packages|proposition to organize the working directory]], it means:
 <div style="max-width:60em;">
-  {{PC$}} ./{{EcosystemRelease/Package | revision=5.0.0 | package=SDK-arm64 installation script | request=path}}/{{EcosystemRelease/Package | revision=5.0.0 | package=SDK-arm64 installation script | request=name}} -d <working directory absolute path>/Developer-Package/SDK
+  {{PC$}}./{{EcosystemRelease/Package | revision=5.0.0 | package=SDK-arm64 installation script | request=path}}/{{EcosystemRelease/Package | revision=5.0.0 | package=SDK-arm64 installation script | request=name}} -d <working directory absolute path>/Developer-Package/SDK
 </div>
@@ Line 121: / Line 236: @@
   └── version-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi
 </div></div>
-<noinclude>
+</div></div>
-==Archives [[File:Archive_box.png|25px|link=]]==
-{{EcosystemFlow/Archives}}
 {{NoIndex}}
 [[Category:Sub-articles]]