Last edited 3 years ago

STM32MP1 Developer Package - SDK: Difference between revisions

This message will disappear after all relevant tasks have been resolved.
Semantic MediaWiki
There are 1 incomplete or pending task to finish installation of Semantic MediaWiki. An administrator or user with sufficient rights can complete it. This should be done before adding new data to avoid inconsistencies.
VisualWikitext
Registered User
mNo edit summary
Registered User
 
(6 intermediate revisions by 2 users not shown)
Line 7: Line 7:
{{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]]}}


==STM32MP15-Ecosystem-v2.1.0 release==
==STM32MP15-Ecosystem-v3.1.0 release==
</noinclude>
</noinclude>
* The STM32MP1 SDK is delivered through a tarball file named : '''{{EcosystemRelease/Package | revision=2.1.0 | package=SDK package | request=name}}'''
* The STM32MP1 SDK is delivered through a tarball file named : '''{{EcosystemRelease/Package | revision=3.1.0 | package=SDK package | request=name}}'''


<span id="Download"></span>
<span id="Download"></span>
Line 16: Line 16:
{| class="st-table"
{| class="st-table"
|-
|-
!  !!style="text-align:center;"|STM32MP1 Developer Package SDK - STM32MP15-Ecosystem-v2.1.0 release
!  !!style="text-align:center;"|STM32MP1 Developer Package SDK - STM32MP15-Ecosystem-v3.1.0 release
|-
|-
| Download ||  
| Download ||  
You need to be logged on ''my.st.com'' before accessing the following link: <br />
You need to be logged on ''my.st.com'' before accessing the following link: <br />
[{{EcosystemRelease/Package | revision=2.1.0 | package=SDK package | request=url}}/{{EcosystemRelease/Package | revision=2.1.0 | package=SDK package | request=name}} {{EcosystemRelease/Package | revision=2.1.0 | package=SDK package | request=name}}]
[{{EcosystemRelease/Package | revision=3.1.0 | package=SDK package | request=url}}/{{EcosystemRelease/Package | revision=3.1.0 | package=SDK package | request=name}} {{EcosystemRelease/Package | revision=3.1.0 | package=SDK package | request=name}}]
|-
|-
| Installation ||
| Installation ||
* Uncompress the tarball file to get the SDK installation script
* Uncompress the tarball file to get the SDK installation script


  tar xvf {{EcosystemRelease/Package | revision=2.1.0 | package=SDK package | request=name}}
  {{PC$}} tar xvf {{EcosystemRelease/Package | revision=3.1.0 | package=SDK package | request=name}}


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


Line 36: Line 36:
** 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;">
  $ ./{{EcosystemRelease/Package | revision=2.1.0 | package=SDK installation script | request=path}}/{{EcosystemRelease/Package | revision=2.1.0 | package=SDK installation script | request=name}} -d <working directory absolute path>/Developer-Package/SDK
  {{PC$}} ./{{EcosystemRelease/Package | revision=3.1.0 | package=SDK installation script | request=path}}/{{EcosystemRelease/Package | revision=3.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 3.1-openstlinux-5-4-dunfell-mp1-20-11-12
ST OpenSTLinux - Weston - (A Yocto Project Based Distro) SDK installer version 3.1.11-openstlinux-5.10-dunfell-mp1-21-11-17
===========================================================================================
===========================================================================================
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]?  
Line 47: Line 47:
SDK has been successfully set up and is ready to be used.
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.
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
  $> . <working directory absolute path>/Developer-Package/SDK/environment-setup-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi
</pre>
</pre>
|-
|-
| Release note ||
| Release note ||
Details about the content of the SDK are available in the '''associated''' [[STM32MP15 ecosystem release note - v2.1.0|STM32MP15 ecosystem release note]].
Details about the content of the SDK are available in the '''associated''' [[STM32MP15 ecosystem release note - v3.1.0|STM32MP15 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 58: Line 58:
* The SDK is in the ''<SDK installation directory>'':
* The SDK is in the ''<SDK installation directory>'':


  {{Green|<SDK installation directory>}}                                                   {{Highlight|'''SDK for OpenSTLinux distribution''': details in [[Standard SDK directory structure]] article}}
  {{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}}
  ├── environment-setup-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi  {{Highlight|'''Environment setup script''' for Developer Package}}
  ├── site-config-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi
  ├── site-config-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi
Line 71: Line 71:
==Archives [[File:Archive_box.png|25px|link=]]==
==Archives [[File:Archive_box.png|25px|link=]]==
{{EcosystemFlow/Archives}}
{{EcosystemFlow/Archives}}
<div class="mw-collapsible mw-collapsed">
<div class="mw-collapsible mw-collapsed">
===STM32MP15-Ecosystem-v2.0.0 release===
===STM32MP15-Ecosystem-v3.0.0 release===
<div class="mw-collapsible-content">
<div class="mw-collapsible-content">
* The STM32MP1 SDK is delivered through a tarball file named : '''{{EcosystemRelease/Package | revision=2.0.0 | package=SDK package | request=name}}'''


<span id="Download"></span>
* The STM32MP1 SDK is delivered through a tarball file named : '''{{EcosystemRelease/Package | revision=3.0.0 | package=SDK package | request=name}}'''
 
* 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 - STM32MP15-Ecosystem-v2.0.0 release
!  !!style="text-align:center;"|STM32MP1 Developer Package SDK - STM32MP15-Ecosystem-v3.0.0 release
|-
|-
| Download ||  
| Download ||  
You need to be logged on ''my.st.com'' before accessing the following link: <br />
You need to be logged on ''my.st.com'' before accessing the following link: <br />
[{{EcosystemRelease/Package | revision=2.0.0 | package=SDK package | request=url}}/{{EcosystemRelease/Package | revision=2.0.0 | package=SDK package | request=name}} {{EcosystemRelease/Package | revision=2.0.0 | package=SDK package | request=name}}]
[{{EcosystemRelease/Package | revision=3.0.0 | package=SDK package | request=url}}/{{EcosystemRelease/Package | revision=3.0.0 | package=SDK package | request=name}} {{EcosystemRelease/Package | revision=3.0.0 | package=SDK package | request=name}}]
|-
|-
| Installation ||
| Installation ||
* Uncompress the tarball file to get the SDK installation script
* Uncompress the tarball file to get the SDK installation script


  tar xvf {{EcosystemRelease/Package | revision=2.0.0 | package=SDK package | request=name}}
  {{PC$}} tar xvf {{EcosystemRelease/Package | revision=3.0.0 | package=SDK package | request=name}}


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


Line 101: Line 102:
** 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;">
  $ ./{{EcosystemRelease/Package | revision=2.0.0 | package=SDK installation script | request=path}}/{{EcosystemRelease/Package | revision=2.0.0 | package=SDK installation script | request=name}} -d <working directory absolute path>/Developer-Package/SDK
  {{PC$}} ./{{EcosystemRelease/Package | revision=3.0.0 | package=SDK installation script | request=path}}/{{EcosystemRelease/Package | revision=3.0.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 3.1-snapshot
ST OpenSTLinux - Weston - (A Yocto Project Based Distro) SDK installer version 3.1-openstlinux-5.10-dunfell-mp1-21-03-31
===========================================================================================
===========================================================================================
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]?  
Line 112: Line 113:
SDK has been successfully set up and is ready to be used.
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.
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
  $> . <working directory absolute path>/Developer-Package/SDK/environment-setup-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi
</pre>
</pre>
|-
|-
| Release note ||
| Release note ||
Details about the content of the SDK are available in the '''associated''' [[STM32MP15 ecosystem release note - v2.0.0|STM32MP15 ecosystem release note]].
Details about the content of the SDK are available in the '''associated''' [[STM32MP15 ecosystem release note - v3.0.0|STM32MP15 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 123: Line 124:
* The SDK is in the ''<SDK installation directory>'':
* The SDK is in the ''<SDK installation directory>'':


  {{Green|<SDK installation directory>}}                                                   {{Highlight|'''SDK for OpenSTLinux distribution''': details in [[Standard SDK directory structure]] article}}
  {{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}}
  ├── environment-setup-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi  {{Highlight|'''Environment setup script''' for Developer Package}}
  ├── site-config-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi
  ├── site-config-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi
Line 132: Line 133:
  │      └── [...]
  │      └── [...]
  └── version-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi
  └── version-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi
 
</div></div>
{{NoIndex}}
{{NoIndex}}
[[Category:Sub-articles]]
[[Category:Sub-articles]]

Latest revision as of 12:01, 15 November 2021↑

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.png To use efficiently this SDK, please go through the Developer Package article relative to your STM32 microprocessor Series: Category:Developer Package

1. STM32MP15-Ecosystem-v3.1.0 release↑

  • The STM32MP1 SDK is delivered through a tarball file named : unknown revision

  • 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.png 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 - STM32MP15-Ecosystem-v3.1.0 release
Download

You need to be logged on my.st.com before accessing the following link:
[unknown revision/unknown revision unknown revision]

Installation
  • 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 3.1.11-openstlinux-5.10-dunfell-mp1-21-11-17
===========================================================================================
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 STM32MP15 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


2. Archives Archive box.png↑

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

2.1. STM32MP15-Ecosystem-v3.0.0 release↑

  • The STM32MP1 SDK is delivered through a tarball file named : unknown revision
  • 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.png 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 - STM32MP15-Ecosystem-v3.0.0 release
Download

You need to be logged on my.st.com before accessing the following link:
[unknown revision/unknown revision unknown revision]

Installation
  • 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 3.1-openstlinux-5.10-dunfell-mp1-21-03-31
===========================================================================================
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 STM32MP15 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


Retrieved from "https://wiki.st.com/stm32mpu-ecosystem-v3/index.php?title=STM32MP1_Developer_Package_-_SDK&oldid=80040"