Last edited 9 months ago

STM32MP1 Developer Package - SDK: Difference between revisions

Visual
Registered User
mNo edit summary
Registered User
mNo edit summary
Tag: 2017 source edit
 
(20 intermediate revisions by 4 users not shown)
Line 5: Line 5:
<noinclude>
<noinclude>
This article aims to give the following information:
This article aims to give the following information:
* How to download and install the '''latest''' SDK for the STM32 microprocessor Series
* How to download and install the '''latest''' SDK for the STM32 microprocessor series.
* Where to find the associated release note
* Where to find the associated release note.
* Where to find the previous releases (archives)
* 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]]}}
{{Warning|To use efficiently this SDK, please go through the Developer Package article relative to your STM32 microprocessor series: [[:Category:Developer Package]]}}


==STM32MPU-Ecosystem-v4.0.0 release ==
==STM32MPU-Ecosystem-v5.1.0 release ==
</noinclude>
</noinclude>
* The STM32MP1 SDK is delivered through a tarball file named : '''{{EcosystemRelease/Package | revision=4.0.0 | package=SDK package | request=name}}'''
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>
<span id="Download"></span>
* Download and install the STM32MP1 SDK.
Download and install the STM32MP1 SDK.
{{SoftwareLicenseAgreement | distribution=OpenSTLinux}}
{{SoftwareLicenseAgreement | distribution=OpenSTLinux}}
{| class="st-table"
{| class="st-table"
|-
|-
!  !!style="text-align:center;"|STM32MP1 Developer Package SDK - STM32MP1-Ecosystem-v4.0.0 release
!  !!style="text-align:center;"|STM32MP1 Developer Package SDK - STM32MP1-Ecosystem-v5.1.0 release
|-
|-
| Download ||  
| Download ||  
You need to be logged on ''my.st.com'' before accessing the following link: <br />
* Go on [https://www.st.com/en/embedded-software/stm32mp1dev.html#get-software st.com] to download
[{{EcosystemRelease/Package | revision=4.0.0 | package=SDK package | request=url}}/{{EcosystemRelease/Package | revision=4.0.0 | package=SDK package | request=name}} {{EcosystemRelease/Package | revision=4.0.0 | package=SDK package | request=name}}]
** '''{{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
|-
|-
| Installation ||
| rowspan="2" | Installation
* Uncompress the tarball file to get the SDK installation script
| For '''x86_64''' host architecture


{{PC$}} tar xvf {{EcosystemRelease/Package | revision=4.0.0 | package=SDK package | request=name}}
* Uncompress the tarball file to get the SDK installation script.


* If needed, change the permissions on the SDK installation script so that it is executable
{{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;">  
<div style="max-width:60em;">  
  {{PC$}} chmod +x {{EcosystemRelease/Package | revision=4.0.0 | package=SDK installation script | request=path}}/{{EcosystemRelease/Package | revision=4.0.0 | package=SDK installation script | request=name}}
  {{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>
</div>


* Run the SDK installation script
* 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>'')
** 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:
** If you follow the [[Example of directory structure for Packages|proposition to organize the working directory]], it means:
<div style="max-width:60em;">
<div style="max-width:60em;">
  {{PC$}} ./{{EcosystemRelease/Package | revision=4.0.0 | package=SDK installation script | request=path}}/{{EcosystemRelease/Package | revision=4.0.0 | package=SDK installation script | request=name}} -d <working directory absolute path>/Developer-Package/SDK
  {{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>
</div>
:* A successful installation outputs the following log:  
:* A successful installation outputs the following log:  
<pre style="max-width:60em;">
<pre style="max-width:60em;">
ST OpenSTLinux - Weston - (A Yocto Project Based Distro) SDK installer version 4.0.1-openstlinux-5.15-yocto-kirkstone-mp1-v22.06.15
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]?  
You are about to install the SDK to "<working directory absolute path>/Developer-Package/SDK". Proceed [Y/n]?  
Extracting SDK............................................................................................................................................................................................................................done
Extracting SDK.........................................................................................................................................................................................................................done
Setting it up...done
Setting it up...done
SDK has been successfully set up and is ready to be used.
SDK has been successfully set up and is ready to be used.
Line 53: Line 59:
  $ . <working directory absolute path>/Developer-Package/SDK/environment-setup-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi
  $ . <working directory absolute path>/Developer-Package/SDK/environment-setup-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi
</pre>
</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 ||
| Release note ||
Details about the content of the SDK are available in the '''associated''' [[STM32 MPU ecosystem release note - v4.0.0|STM32 MPU ecosystem 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]].
[[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]].
Line 71: Line 107:
  │      └── [...]
  │      └── [...]
  └── version-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi
  └── 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>
<noinclude>


==Archives [[File:Archive_box.png|25px|link=]]==
==Archives [[File:Archive_box.png|25px|link=]]==
{{EcosystemFlow/Archives}}
{{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}}
* '''{{EcosystemRelease/Package | revision=5.0.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.0.0 release
|-
| Download ||
* Go on [https://www.st.com/en/embedded-software/stm32mp1dev.html#get-software st.com] to download
** '''{{EcosystemRelease/Package | revision=5.0.0 | package=SDK package | request=name}}''' file for x86_64 host architecture
** '''{{EcosystemRelease/Package | revision=5.0.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.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}}
</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.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>
 
:* 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 class="mw-collapsible mw-collapsed">
For '''arm64''' host architecture
<div class="mw-collapsible-content">
{{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}}
</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.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>
 
:* 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.0.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>
</div></div>
{{NoIndex}}
{{NoIndex}}
[[Category:Sub-articles]]
[[Category:Sub-articles]]
Line 89: Line 249:
** Change the path and the description of the installation directory
** Change the path and the description of the installation directory
}}
}}
{{PublicationRequestId | 24660| 2022-09-26 |}}
</noinclude>
</noinclude>

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

Applicable for STM32MP13x lines, STM32MP15x lines

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 white.png 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↑

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.

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

For arm64 host architecture

Release note

Details about the content of the SDK are available in the associated STM32 MPU ecosystem release note.

Archive box.png 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

For arm64 host architecture


2. Archives Archive box.png↑

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

2.1. STM32MPU-Ecosystem-v5.0.0 release↑


Retrieved from "https://wiki.stmicroelectronics.cn/stm32mpu-ecosystem-v5/index.php?title=STM32MP1_Developer_Package_-_SDK&oldid=104266"