Difference between revisions of "STM32MP1 Developer Package - SDK"

[quality revision] [unchecked revision]
m
 
imported>Frq08954
m (Undo revision 52237 by Frq08954 (talk))

Template:ArticleMainWriter Template:ReviewersList Template:ArticleApprovedVersion


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

1 STM32MP15-Ecosystem-v1.0.0 release[edit]

  • The STM32MP1 SDK is delivered through a tarball file named : SDK-x86_64-stm32mp1-openstlinux-4.19-thud-mp1-19-02-20.tar.xz

  • Download and install the STM32MP1 SDK.
By downloading this software package, you agree to be bound to the terms of the Limited License Agreement. The detailed content licenses can be found here
STM32MP1 Developer Package SDK - STM32MP15-Ecosystem-v1.0.0 release
Download

Template:STdotcomInfo

Installation
  • Uncompress the tarball file to get the SDK installation script

$ tar xvf SDK-x86_64-stm32mp1-openstlinux-4.19-thud-mp1-19-02-20.tar.xz

  • If needed, change the permissions on the SDK installation script so that it is executable

$ chmod +x stm32mp1-openstlinux-4.19-thud-mp1-19-02-20/sdk/st-image-weston-openstlinux-weston-stm32mp1-x86_64-toolchain-2.4-openstlinux-4.19-thud-mp1-19-02-20.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-4.19-thud-mp1-19-02-20/sdk/st-image-weston-openstlinux-weston-stm32mp1-x86_64-toolchain-2.4-openstlinux-4.19-thud-mp1-19-02-20.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 2.4-openstlinux-4.19-thud-mp1-19-02-20
======================================================================================================================
You are about to install the SDK to "<working directory absolute path>/Developer-Package/SDK". Proceed[Y/n]? Y
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-cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi

Release note

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

If you are interested in former releases, please go through the archives of the ecosystem release note.

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


2 Archives[edit]


2.1 Beta1 release[edit]

  • The STM32MP1 SDK is delivered through a tarball file named : SDK-x86_64-stm32mp1-boards-revc-openstlinux-4.14-rocko-mp1-18-11-26.tar.xz (compatible revision B and revision C)

  • Download and install the STM32MP1 SDK.
By downloading this software package, you agree to be bound to the terms of the Limited License Agreement. The detailed content licenses can be found here
STM32MP1 Developer Package SDK - Beta1 release
Download

Template:STdotcomInfo

Installation
  • Uncompress the tarball file to get the SDK installation script
$ tar xvf SDK-x86_64-stm32mp1-boards-revc-openstlinux-4.14-rocko-mp1-18-11-26.tar.xz
  • If needed, change the permissions on the SDK installation script so that it is executable
$ chmod +x stm32mp1-boards-revc-openstlinux-4.14-rocko-mp1-18-11-26/sdk/st-image-weston-openstlinux-weston-stm32mp1-boards-revc-x86_64-toolchain-2.4-openstlinux-4.14-rocko-mp1-18-11-26.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-boards-revc-openstlinux-4.14-rocko-mp1-18-11-26/sdk/st-image-weston-openstlinux-weston-stm32mp1-boards-revc-x86_64-toolchain-2.4-openstlinux-4.14-rocko-mp1-18-11-26.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 2.4-openstlinux-4.14-rocko-mp1-18-11-26
======================================================================================================================
You are about to install the SDK to "<working directory absolute path>/Developer-Package/SDK". Proceed[Y/n]? Y
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-cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi
Release note

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

If you are interested in former releases, please go through the archives of the ecosystem release note.

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

2

Archives[edit]

2.1 .2 Alpha2 release[edit]

  • The STM32MP1 SDK is delivered through a tarball file named SDK-x86_64-openstlinux-4.14-rocko-mp1-18-07-03.tar.xz.

  • Download and install the STM32MP1 SDK.
By downloading the tarball file, you agree to be bound to the terms of the Limited License Agreement
STM32MP1 Developer Package SDK - Alpha2 release
Download

Template:STdotcomInfo

Installation
  • Uncompress the tarball file to get the SDK installation script
$ tar xvf SDK-x86_64-openstlinux-4.14-rocko-mp1-18-07-03.tar.xz
  • If needed, change the permissions on the SDK installation script so that it is executable
$ chmod +x openstlinux-4.14-rocko-mp1-18-07-03/sdk/st-image-weston-openstlinux-weston-stm32mp1-x86_64-toolchain-2.4+openstlinux-4.14-rocko-mp1-18-07-03.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:
$ ./openstlinux-4.14-rocko-mp1-18-07-03/sdk/st-image-weston-openstlinux-weston-stm32mp1-x86_64-toolchain-2.4+openstlinux-4.14-rocko-mp1-18-07-03.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 2.4+openstlinux-4.14-rocko-mp1-18-07-03
======================================================================================================================
You are about to install the SDK to "<working directory absolute path>/Developer-Package/SDK". Proceed[Y/n]? Y
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-cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi
Release note

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

If you are interested in former releases, please go through the archives of the ecosystem release note.

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

2.23 Alpha1 release[edit]

  • The STM32MP1 SDK is delivered through a tarball file named SDK-x86_64-openstlinux-4.14-rocko-mp1-18-01-23.tar.xz.

  • Download and install the STM32MP1 SDK.
By downloading the tarball file, you agree to be bound to the terms of the Limited License Agreement
STM32MP1 Developer Package SDK - Alpha1 release
Download

Template:STdotcomInfo

Installation
  • Uncompress the tarball file to get the SDK installation script
$ tar xvf SDK-x86_64-openstlinux-4.14-rocko-mp1-18-01-23.tar.xz
  • If needed, change the permissions on the SDK installation script so that it is executable
$ chmod +x openstlinux-4.14-rocko-mp1-18-01-23/sdk/st-image-weston-openstlinux-weston-stm32mp1-x86_64-toolchain-2.4+openstlinux-4.14-rocko-mp1-18-01-23.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:
$ ./openstlinux-4.14-rocko-mp1-18-01-23/sdk/st-image-weston-openstlinux-weston-stm32mp1-x86_64-toolchain-2.4+openstlinux-4.14-rocko-mp1-18-01-23.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 2.4+openstlinux-4.14-rocko-mp1-18-01-23
======================================================================================================================
You are about to install the SDK to "<working directory absolute path>/Developer-Package/SDK". Proceed[Y/n]? Y
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-cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi
Release note

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

If you are interested in former releases, please go through the archives of the ecosystem release note.

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

{{ArticleMainWriter | DenisH}}
{{ReviewersList | NathalieS, BernardP, RomualdJ, Jean-ChristopheT}}
{{ArticleApprovedVersion | SebastienG | Jean-ChristopheT(Passed, 28Nov'18) | Jean-ChristopheT - 17Sep'18 | AlainF | 05Dec'18}}

[[Category:Sub-articles]]
{{UpdateNeededForNewRelease|
* Copy the current release (first chapter) in the "Archives" chapter
* Make the following modifications in this copy:
** Change the "Download" span id to "Download <name of the old release>" (example: "Download Alpha1")
* Make the following modifications in the first chapter
** Change the name of the tarball file
** Change the download URLs
** Change the link to the release note
** Change the path and the description of the installation directory
}}

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]]}}

==Beta1STM32MP15-Ecosystem-v1.0.0 release==</noinclude>

* The STM32MP1 SDK is delivered through a tarball file named : '''SDK-x86_64-stm32mp1-openstlinux-4.19-thud-mp1-19-02-20.tar.xz'''
<span id="Download"></span>

* Download and install the STM32MP1 SDK.
:''By downloading this software package, you agree to be bound to the terms of the [[OpenSTLinux licenses#Limited_License_Agreement|Limited License Agreement]]''. ''The detailed content licenses can be found [[OpenSTLinux licenses|here]]''
{| class="wikitable"
|-
!  !! STM32MP1 Developer Package SDK - STM32MP15-Ecosystem-v1.0.0 release
|-
| Download || 
{{InternalInfo|
[https://citools.st.com/artifacts/artifactory/MPUPUBDV-codex-st-com/openstlinux-4.19-thud-mp1-19-02-20/SDK-x86_64-stm32mp1-openstlinux-4.19-thud-mp1-19-02-20.tar.xz SDK-x86_64-stm32mp1-openstlinux-4.19-thud-mp1-19-02-20.tar.xz]
* Download the tarball file in a temporary directory of your host PC
}}
{{STdotcomInfo|
* '''A ''my.st.com'' account is required, with specific access rights: please request these rights to your ST support contact'''
* You need to be logged on ''my.st.com'' before accessing the following links
[https://my.st.com/collab/g1/stm32mp1/openstlinux_library/REF%20code/SDK-x86_64-stm32mp1-openstlinux-4.19-thud-mp1-19-02-20.tar.xz.z01 SDK-x86_64-stm32mp1-openstlinux-4.19-thud-mp1-19-02-20.tar.xz.z01]<br />

[https://my.st.com/collab/g1/stm32mp1/openstlinux_library/REF%20code/SDK-x86_64-stm32mp1-openstlinux-4.19-thud-mp1-19-02-20.tar.xz.z02 SDK-x86_64-stm32mp1-openstlinux-4.19-thud-mp1-19-02-20.tar.xz.z02]<br />

[https://my.st.com/collab/g1/stm32mp1/openstlinux_library/REF%20code/SDK-x86_64-stm32mp1-openstlinux-4.19-thud-mp1-19-02-20.tar.xz.z03 SDK-x86_64-stm32mp1-openstlinux-4.19-thud-mp1-19-02-20.tar.xz.z03]<br />

[https://my.st.com/collab/g1/stm32mp1/openstlinux_library/REF%20code/SDK-x86_64-stm32mp1-openstlinux-4.19-thud-mp1-19-02-20.tar.xz.z04 SDK-x86_64-stm32mp1-openstlinux-4.19-thud-mp1-19-02-20.tar.xz.z04]<br />

[https://my.st.com/collab/g1/stm32mp1/openstlinux_library/REF%20code/SDK-x86_64-stm32mp1-openstlinux-4.19-thud-mp1-19-02-20.tar.xz.zip SDK-x86_64-stm32mp1-openstlinux-4.19-thud-mp1-19-02-20.tar.xz.zip]
* Download these tarball files in a temporary directory of your host PC
* Merge the 5 tarball files into a single one (SDK-x86_64-stm32mp1-openstlinux-4.19-thud-mp1-19-02-20.tar.xz)<pre>

$ cat SDK-x86_64-stm32mp1-openstlinux-4.19-thud-mp1-19-02-20.tar.xz.* > single.zip
$ unzip -FF single.zip</pre>

}}
|-
| Installation ||
* Uncompress the tarball file to get the SDK installation script<pre>

$ tar xvf SDK-x86_64-stm32mp1-openstlinux-4.19-thud-mp1-19-02-20.tar.xz</pre>

* If needed, change the permissions on the SDK installation script so that it is executable<pre style="white-space: pre-wrap">

$ chmod +x stm32mp1-openstlinux-4.19-thud-mp1-19-02-20/sdk/st-image-weston-openstlinux-weston-stm32mp1-x86_64-toolchain-2.4-openstlinux-4.19-thud-mp1-19-02-20.sh</pre>

* 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:<pre style="white-space: pre-wrap">

$ ./stm32mp1-openstlinux-4.19-thud-mp1-19-02-20/sdk/st-image-weston-openstlinux-weston-stm32mp1-x86_64-toolchain-2.4-openstlinux-4.19-thud-mp1-19-02-20.sh -d <working directory absolute path>/Developer-Package/SDK</pre>

:* A successful installation outputs the following log: <pre>

ST OpenSTLinux - Weston - (A Yocto Project Based Distro) SDK installer version 2.4-openstlinux-4.19-thud-mp1-19-02-20
======================================================================================================================
You are about to install the SDK to "<working directory absolute path>/Developer-Package/SDK". Proceed[Y/n]? Y
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-cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi</pre>

|-
| Release note ||
Details about the content of the SDK are available in the '''associated''' [[STM32MP15 ecosystem release note - v1.0.0|STM32MP15 ecosystem release note]].

If you are interested in former releases, please go through the [[STM32MP15 ecosystem release note#Archives| archives]] of the ecosystem release note.
|}

* The SDK is in the ''<SDK installation directory>'':

 {{Green|<SDK installation directory>}}                                                  {{Highlight|'''SDK for OpenSTLinux distribution''': details in [[Standard SDK directory structure]] article}}
 ├── environment-setup-cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi  {{Highlight|'''Environment setup script''' for Developer Package}}
 ├── site-config-cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi
 ├── {{Green|sysroots}}
 │   ├── {{Green|cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi}}                {{Highlight|Target sysroot (libraries, headers, and symbols)}}
 │   │   └── [...]
 │   └── {{Green|x86_64-openstlinux_weston_sdk-linux}}                                   {{Highlight|Native sysroot (libraries, headers, and symbols)}}
 │       └── [...]
 └── version-cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi<noinclude>


==Archives==
{{InternalInfo|Please copy the content of the older release here when delivering a new release<pre>

===XXX release===<div class="NavFrame collapsed">
<div class="NavHead">Details</div>
<div class="NavContent">

  ...</div>
</div>
</pre>

}}

===Beta1 release===
* The STM32MP1 SDK is delivered through a tarball file named : '''SDK-x86_64-stm32mp1-boards-revc-openstlinux-4.14-rocko-mp1-18-11-26.tar.xz''' (compatible {{Highlight|'''revision B'''}} and {{Highlight|'''revision C'''}})
<span id="Download Beta1"></span>

* Download and install the STM32MP1 SDK.
:''By downloading this software package, you agree to be bound to the terms of the [[OpenSTLinux licenses#Limited_License_Agreement|Limited License Agreement]]''. ''The detailed content licenses can be found [[OpenSTLinux licenses|here]]''
{| class="wikitable"
|-
!  !! STM32MP1 Developer Package SDK - Beta1 release
|-
| Download || 
{{InternalInfo|
[https://citools.st.com/artifacts/artifactory/MPUPUBDV-codex-st-com/openstlinux-4.14-rocko-mp1-18-11-26/SDK-x86_64-stm32mp1-boards-revc-openstlinux-4.14-rocko-mp1-18-11-26.tar.xz SDK-x86_64-stm32mp1-boards-revc-openstlinux-4.14-rocko-mp1-18-11-26.tar.xz]
* Download the tarball file in a temporary directory of your host PC
}}
{{STdotcomInfo|
* '''A ''my.st.com'' account is required, with specific access rights: please request these rights to your ST support contact'''
* You need to be logged on ''my.st.com'' before accessing the following links
[https://my.st.com/collab/g1/stm32mp1/openstlinux_library/REF%20code/SDK-x86_64-stm32mp1-boards-revc-openstlinux-4.14-rocko-mp1-18-11-26.tar.xz.z01 SDK-x86_64-stm32mp1-boards-revc-openstlinux-4.14-rocko-mp1-18-11-26.tar.xz.z01]<br />

[https://my.st.com/collab/g1/stm32mp1/openstlinux_library/REF%20code/SDK-x86_64-stm32mp1-boards-revc-openstlinux-4.14-rocko-mp1-18-11-26.tar.xz.z02 SDK-x86_64-stm32mp1-boards-revc-openstlinux-4.14-rocko-mp1-18-11-26.tar.xz.z02]<br />

[https://my.st.com/collab/g1/stm32mp1/openstlinux_library/REF%20code/SDK-x86_64-stm32mp1-boards-revc-openstlinux-4.14-rocko-mp1-18-11-26.tar.xz.z03 SDK-x86_64-stm32mp1-boards-revc-openstlinux-4.14-rocko-mp1-18-11-26.tar.xz.z03]<br />

[https://my.st.com/collab/g1/stm32mp1/openstlinux_library/REF%20code/SDK-x86_64-stm32mp1-boards-revc-openstlinux-4.14-rocko-mp1-18-11-26.tar.xz.z04 SDK-x86_64-stm32mp1-boards-revc-openstlinux-4.14-rocko-mp1-18-11-26.tar.xz.z04]<br />

[https://my.st.com/collab/g1/stm32mp1/openstlinux_library/REF%20code/SDK-x86_64-stm32mp1-boards-revc-openstlinux-4.14-rocko-mp1-18-11-26.tar.xz.zip SDK-x86_64-stm32mp1-boards-revc-openstlinux-4.14-rocko-mp1-18-11-26.tar.xz.zip]
* Download these tarball files in a temporary directory of your host PC
* Merge the 5 tarball files into a single one (SDK-x86_64-stm32mp1-boards-revc-openstlinux-4.14-rocko-mp1-18-11-26.tar.xz)<pre>

$ cat SDK-x86_64-stm32mp1-boards-revc-openstlinux-4.14-rocko-mp1-18-11-26.tar.xz.* > single.zip
$ unzip -FF single.zip</pre>

}}
|-
| Installation ||
* Uncompress the tarball file to get the SDK installation script<pre>

$ tar xvf SDK-x86_64-stm32mp1-boards-revc-openstlinux-4.14-rocko-mp1-18-11-26.tar.xz</pre>

* If needed, change the permissions on the SDK installation script so that it is executable<pre style="white-space: pre-wrap">

$ chmod +x stm32mp1-boards-revc-openstlinux-4.14-rocko-mp1-18-11-26/sdk/st-image-weston-openstlinux-weston-stm32mp1-boards-revc-x86_64-toolchain-2.4-openstlinux-4.14-rocko-mp1-18-11-26.sh</pre>

* 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:<pre style="white-space: pre-wrap">

$ ./stm32mp1-boards-revc-openstlinux-4.14-rocko-mp1-18-11-26/sdk/st-image-weston-openstlinux-weston-stm32mp1-boards-revc-x86_64-toolchain-2.4-openstlinux-4.14-rocko-mp1-18-11-26.sh -d <working directory absolute path>/Developer-Package/SDK</pre>

:* A successful installation outputs the following log: <pre>

ST OpenSTLinux - Weston - (A Yocto Project Based Distro) SDK installer version 2.4-openstlinux-4.14-rocko-mp1-18-11-26
======================================================================================================================
You are about to install the SDK to "<working directory absolute path>/Developer-Package/SDK". Proceed[Y/n]? Y
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-cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi</pre>

|-
| Release note ||
Details about the content of the SDK are available in the '''associated''' [[STM32MP15 ecosystem release note - Beta1|STM32MP15 ecosystem release note]].

If you are interested in former releases, please go through the [[STM32MP15 ecosystem release note#Archives| archives]] of the ecosystem release note.
|}

* The SDK is in the ''<SDK installation directory>'':

 {{Green|<SDK installation directory>}}                                                  {{Highlight|'''SDK for OpenSTLinux distribution''': details in [[Standard SDK directory structure]] article}}
 ├── environment-setup-cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi  {{Highlight|'''Environment setup script''' for Developer Package}}
 ├── site-config-cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi
 ├── {{Green|sysroots}}
 │   ├── {{Green|cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi}}                {{Highlight|Target sysroot (libraries, headers, and symbols)}}
 │   │   └── [...]
 │   └── {{Green|x86_64-openstlinux_weston_sdk-linux}}                                   {{Highlight|Native sysroot (libraries, headers, and symbols)}}
 │       └── [...]
 └── version-cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi<noinclude>


==Archives==
{{InternalInfo|Please copy the content of the older release here when delivering a new release<pre>

===XXX release===<div class="NavFrame collapsed">
<div class="NavHead">Details</div>
<div class="NavContent">

  ...</div>
</div>
</pre>

}}

===

===Alpha2 release===
* The STM32MP1 SDK is delivered through a tarball file named '''SDK-x86_64-openstlinux-4.14-rocko-mp1-18-07-03.tar.xz'''.
<span id="Download Alpha2"></span>

* Download and install the STM32MP1 SDK.
:''By downloading the tarball file, you agree to be bound to the terms of the [[media:LLA_evaluation_for_STM32MPU.pdf|Limited License Agreement]]''
{| class="wikitable"
|-
!  !! STM32MP1 Developer Package SDK - Alpha2 release
|-
| Download || 
{{InternalInfo|
[https://citools.st.com/artifacts/artifactory/MPUPUBDV-codex-st-com/openstlinux-4.14-rocko-mp1-18-07-03/SDK-x86_64-openstlinux-4.14-rocko-mp1-18-07-03.tar.xz SDK-x86_64-openstlinux-4.14-rocko-mp1-18-07-03.tar.xz]
* Download the tarball file in a temporary directory of your host PC
}}
{{STdotcomInfo|
* '''A ''my.st.com'' account is required, with specific access rights: please request these rights to your ST support contact'''
* You need to be logged on ''my.st.com'' before accessing the following links
[https://my.st.com/collab/g1/stm32mp1/openstlinux_library/REF%20code/SDK-x86_64-openstlinux-4.14-rocko-mp1-18-07-03.tar.xz.z01 SDK-x86_64-openstlinux-4.14-rocko-mp1-18-07-03.tar.xz.z01]

[https://my.st.com/collab/g1/stm32mp1/openstlinux_library/REF%20code/SDK-x86_64-openstlinux-4.14-rocko-mp1-18-07-03.tar.xz.zip SDK-x86_64-openstlinux-4.14-rocko-mp1-18-07-03.tar.xz.zip]
* Download these tarball files in a temporary directory of your host PC
* Merge the 2 tarball files into a single one (SDK-x86_64-openstlinux-4.14-rocko-mp1-18-07-03.tar.xz)<pre>

$ zip -s 0 SDK-x86_64-openstlinux-4.14-rocko-mp1-18-07-03.tar.xz.zip --out single.zip
$ unzip single.zip</pre>

}}
|-
| Installation ||
* Uncompress the tarball file to get the SDK installation script<pre>

$ tar xvf SDK-x86_64-openstlinux-4.14-rocko-mp1-18-07-03.tar.xz</pre>

* If needed, change the permissions on the SDK installation script so that it is executable<pre style="white-space: pre-wrap">

$ chmod +x openstlinux-4.14-rocko-mp1-18-07-03/sdk/st-image-weston-openstlinux-weston-stm32mp1-x86_64-toolchain-2.4+openstlinux-4.14-rocko-mp1-18-07-03.sh</pre>

* 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:<pre style="white-space: pre-wrap">

$ ./openstlinux-4.14-rocko-mp1-18-07-03/sdk/st-image-weston-openstlinux-weston-stm32mp1-x86_64-toolchain-2.4+openstlinux-4.14-rocko-mp1-18-07-03.sh -d <working directory absolute path>/Developer-Package/SDK</pre>

:* A successful installation outputs the following log: <pre>

ST OpenSTLinux - Weston - (A Yocto Project Based Distro) SDK installer version 2.4+openstlinux-4.14-rocko-mp1-18-07-03
======================================================================================================================
You are about to install the SDK to "<working directory absolute path>/Developer-Package/SDK". Proceed[Y/n]? Y
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-cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi</pre>

|-
| Release note ||
Details about the content of the SDK are available in the '''associated''' [[STM32MP15 ecosystem release note - Alpha2|STM32MP15 ecosystem release note]].

If you are interested in former releases, please go through the [[STM32MP15 ecosystem release note#Archives| archives]] of the ecosystem release note.
|}

* The SDK is in the ''<SDK installation directory>'':

 {{Green|<SDK installation directory>}}                                                  {{Highlight|'''SDK for OpenSTLinux distribution''': details in [[Standard SDK directory structure]] article}}
 ├── environment-setup-cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi  {{Highlight|'''Environment setup script''' for Developer Package}}
 ├── site-config-cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi
 ├── {{Green|sysroots}}
 │   ├── {{Green|cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi}}                {{Highlight|Target sysroot (libraries, headers, and symbols)}}
 │   │   └── [...]
 │   └── {{Green|x86_64-openstlinux_weston_sdk-linux}}                                   {{Highlight|Native sysroot (libraries, headers, and symbols)}}
 │       └── [...]
 └── version-cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi

===Alpha1 release===
* The STM32MP1 SDK is delivered through a tarball file named '''SDK-x86_64-openstlinux-4.14-rocko-mp1-18-01-23.tar.xz'''.
<span id="Download Alpha1"></span>

* Download and install the STM32MP1 SDK.
:''By downloading the tarball file, you agree to be bound to the terms of the [[media:LLA_evaluation_for_STM32MPU.pdf|Limited License Agreement]]''
{| class="wikitable"
|-
!  !! STM32MP1 Developer Package SDK - Alpha1 release
|-
| Download ||
{{InternalInfo|
[https://citools.st.com/artifacts/artifactory/MPUPUBDV-codex-st-com/openstlinux-4.14-rocko-mp1-18-01-23/SDK-x86_64-openstlinux-4.14-rocko-mp1-18-01-23.tar.xz SDK-x86_64-openstlinux-4.14-rocko-mp1-18-01-23.tar.xz]
* Download the tarball file in a temporary directory of your host PC
}}
{{STdotcomInfo|
* '''A ''my.st.com'' account is required, with specific access rights: please request these rights to your ST support contact'''
* You need to be logged on ''my.st.com'' before accessing the following links
[https://my.st.com/collab/g1/stm32mp1/openstlinux_library/REF%20code/SDK-x86_64-openstlinux-4.14-rocko-mp1-18-01-23.tar.xz.z01 SDK-x86_64-openstlinux-4.14-rocko-mp1-18-01-23.tar.xz.z01]

[https://my.st.com/collab/g1/stm32mp1/openstlinux_library/REF%20code/SDK-x86_64-openstlinux-4.14-rocko-mp1-18-01-23.tar.xz.zip SDK-x86_64-openstlinux-4.14-rocko-mp1-18-01-23.tar.xz.zip]
* Download these tarball files in a temporary directory of your host PC
* Merge the 2 tarball files into a single one (SDK-x86_64-openstlinux-4.14-rocko-mp1-18-01-23.tar.xz)<pre>

$ zip -s 0 SDK-x86_64-openstlinux-4.14-rocko-mp1-18-01-23.tar.xz.zip --out single.zip
$ unzip single.zip</pre>

}}
|-
| Installation ||
* Uncompress the tarball file to get the SDK installation script<pre>

$ tar xvf SDK-x86_64-openstlinux-4.14-rocko-mp1-18-01-23.tar.xz</pre>

* If needed, change the permissions on the SDK installation script so that it is executable<pre style="white-space: pre-wrap">

$ chmod +x openstlinux-4.14-rocko-mp1-18-01-23/sdk/st-image-weston-openstlinux-weston-stm32mp1-x86_64-toolchain-2.4+openstlinux-4.14-rocko-mp1-18-01-23.sh</pre>

* 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:<pre style="white-space: pre-wrap">

$ ./openstlinux-4.14-rocko-mp1-18-01-23/sdk/st-image-weston-openstlinux-weston-stm32mp1-x86_64-toolchain-2.4+openstlinux-4.14-rocko-mp1-18-01-23.sh -d <working directory absolute path>/Developer-Package/SDK</pre>

:* A successful installation outputs the following log: <pre>

ST OpenSTLinux - Weston - (A Yocto Project Based Distro) SDK installer version 2.4+openstlinux-4.14-rocko-mp1-18-01-23
======================================================================================================================
You are about to install the SDK to "<working directory absolute path>/Developer-Package/SDK". Proceed[Y/n]? Y
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-cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi</pre>

|-
| Release note ||
Details about the content of the SDK are available in the '''associated''' [[STM32MP15 ecosystem release note - Alpha1|STM32MP15 ecosystem release note]].

If you are interested in former releases, please go through the [[STM32MP15 ecosystem release note#Archives| archives]] of the ecosystem release note.
|}

* The SDK is in the ''<SDK installation directory>'':

 {{Green|<SDK installation directory>}}                                                  {{Highlight|'''SDK for OpenSTLinux distribution''': details in [[Standard SDK directory structure]] article}}
 ├── environment-setup-cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi  {{Highlight|'''Environment setup script''' for Developer Package}}
 ├── site-config-cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi
 ├── {{Green|sysroots}}
 │   ├── {{Green|cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi}}                {{Highlight|Target sysroot (libraries, headers, and symbols)}}
 │   │   └── [...]
 │   └── {{Green|x86_64-openstlinux_weston_sdk-linux}}                                   {{Highlight|Native sysroot (libraries, headers, and symbols)}}
 │       └── [...]
 └── version-cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi</noinclude>
Line 23: Line 23:
 
{{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]]}}
   
==Beta1 release==
+
==STM32MP15-Ecosystem-v1.0.0 release==
 
</noinclude>
 
</noinclude>
  +
* The STM32MP1 SDK is delivered through a tarball file named : '''SDK-x86_64-stm32mp1-openstlinux-4.19-thud-mp1-19-02-20.tar.xz'''
  +
  +
<span id="Download"></span>
  +
* Download and install the STM32MP1 SDK.
  +
:''By downloading this software package, you agree to be bound to the terms of the [[OpenSTLinux licenses#Limited_License_Agreement|Limited License Agreement]]''. ''The detailed content licenses can be found [[OpenSTLinux licenses|here]]''
  +
{| class="wikitable"
  +
|-
  +
!  !! STM32MP1 Developer Package SDK - STM32MP15-Ecosystem-v1.0.0 release
  +
|-
  +
| Download ||
  +
{{InternalInfo|
  +
[https://citools.st.com/artifacts/artifactory/MPUPUBDV-codex-st-com/openstlinux-4.19-thud-mp1-19-02-20/SDK-x86_64-stm32mp1-openstlinux-4.19-thud-mp1-19-02-20.tar.xz SDK-x86_64-stm32mp1-openstlinux-4.19-thud-mp1-19-02-20.tar.xz]
  +
* Download the tarball file in a temporary directory of your host PC
  +
}}
  +
{{STdotcomInfo|
  +
* '''A ''my.st.com'' account is required, with specific access rights: please request these rights to your ST support contact'''
  +
* You need to be logged on ''my.st.com'' before accessing the following links
  +
[https://my.st.com/collab/g1/stm32mp1/openstlinux_library/REF%20code/SDK-x86_64-stm32mp1-openstlinux-4.19-thud-mp1-19-02-20.tar.xz.z01 SDK-x86_64-stm32mp1-openstlinux-4.19-thud-mp1-19-02-20.tar.xz.z01]<br />
  +
[https://my.st.com/collab/g1/stm32mp1/openstlinux_library/REF%20code/SDK-x86_64-stm32mp1-openstlinux-4.19-thud-mp1-19-02-20.tar.xz.z02 SDK-x86_64-stm32mp1-openstlinux-4.19-thud-mp1-19-02-20.tar.xz.z02]<br />
  +
[https://my.st.com/collab/g1/stm32mp1/openstlinux_library/REF%20code/SDK-x86_64-stm32mp1-openstlinux-4.19-thud-mp1-19-02-20.tar.xz.z03 SDK-x86_64-stm32mp1-openstlinux-4.19-thud-mp1-19-02-20.tar.xz.z03]<br />
  +
[https://my.st.com/collab/g1/stm32mp1/openstlinux_library/REF%20code/SDK-x86_64-stm32mp1-openstlinux-4.19-thud-mp1-19-02-20.tar.xz.z04 SDK-x86_64-stm32mp1-openstlinux-4.19-thud-mp1-19-02-20.tar.xz.z04]<br />
  +
[https://my.st.com/collab/g1/stm32mp1/openstlinux_library/REF%20code/SDK-x86_64-stm32mp1-openstlinux-4.19-thud-mp1-19-02-20.tar.xz.zip SDK-x86_64-stm32mp1-openstlinux-4.19-thud-mp1-19-02-20.tar.xz.zip]
  +
* Download these tarball files in a temporary directory of your host PC
  +
* Merge the 5 tarball files into a single one (SDK-x86_64-stm32mp1-openstlinux-4.19-thud-mp1-19-02-20.tar.xz)
  +
<pre>
  +
$ cat SDK-x86_64-stm32mp1-openstlinux-4.19-thud-mp1-19-02-20.tar.xz.* > single.zip
  +
$ unzip -FF single.zip
  +
</pre>
  +
}}
  +
|-
  +
| Installation ||
  +
* Uncompress the tarball file to get the SDK installation script
  +
<pre>
  +
$ tar xvf SDK-x86_64-stm32mp1-openstlinux-4.19-thud-mp1-19-02-20.tar.xz
  +
</pre>
  +
* If needed, change the permissions on the SDK installation script so that it is executable
  +
<pre style="white-space: pre-wrap">
  +
$ chmod +x stm32mp1-openstlinux-4.19-thud-mp1-19-02-20/sdk/st-image-weston-openstlinux-weston-stm32mp1-x86_64-toolchain-2.4-openstlinux-4.19-thud-mp1-19-02-20.sh
  +
</pre>
  +
* 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:
  +
<pre style="white-space: pre-wrap">
  +
$ ./stm32mp1-openstlinux-4.19-thud-mp1-19-02-20/sdk/st-image-weston-openstlinux-weston-stm32mp1-x86_64-toolchain-2.4-openstlinux-4.19-thud-mp1-19-02-20.sh -d <working directory absolute path>/Developer-Package/SDK
  +
</pre>
  +
:* A successful installation outputs the following log:
  +
<pre>
  +
ST OpenSTLinux - Weston - (A Yocto Project Based Distro) SDK installer version 2.4-openstlinux-4.19-thud-mp1-19-02-20
  +
======================================================================================================================
  +
You are about to install the SDK to "<working directory absolute path>/Developer-Package/SDK". Proceed[Y/n]? Y
  +
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-cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi
  +
</pre>
  +
|-
  +
| Release note ||
  +
Details about the content of the SDK are available in the '''associated''' [[STM32MP15 ecosystem release note - v1.0.0|STM32MP15 ecosystem release note]].
  +
  +
If you are interested in former releases, please go through the [[STM32MP15 ecosystem release note#Archives| archives]] of the ecosystem release note.
  +
|}
  +
  +
* The SDK is in the ''<SDK installation directory>'':
  +
  +
{{Green|<SDK installation directory>}}                                                  {{Highlight|'''SDK for OpenSTLinux distribution''': details in [[Standard SDK directory structure]] article}}
  +
├── environment-setup-cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi  {{Highlight|'''Environment setup script''' for Developer Package}}
  +
├── site-config-cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi
  +
├── {{Green|sysroots}}
  +
│  ├── {{Green|cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi}}                {{Highlight|Target sysroot (libraries, headers, and symbols)}}
  +
│  │  └── [...]
  +
│  └── {{Green|x86_64-openstlinux_weston_sdk-linux}}                                  {{Highlight|Native sysroot (libraries, headers, and symbols)}}
  +
│      └── [...]
  +
└── version-cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi
  +
<noinclude>
  +
  +
==Archives==
  +
{{InternalInfo|Please copy the content of the older release here when delivering a new release
  +
<pre>
  +
===XXX release===
  +
<div class="NavFrame collapsed">
  +
  <div class="NavHead">Details</div>
  +
  <div class="NavContent">
  +
  ...
  +
  </div>
  +
</div>
  +
</pre>
  +
}}
  +
  +
===Beta1 release===
 
* The STM32MP1 SDK is delivered through a tarball file named : '''SDK-x86_64-stm32mp1-boards-revc-openstlinux-4.14-rocko-mp1-18-11-26.tar.xz''' (compatible {{Highlight|'''revision B'''}} and {{Highlight|'''revision C'''}})
 
* The STM32MP1 SDK is delivered through a tarball file named : '''SDK-x86_64-stm32mp1-boards-revc-openstlinux-4.14-rocko-mp1-18-11-26.tar.xz''' (compatible {{Highlight|'''revision B'''}} and {{Highlight|'''revision C'''}})
   
<span id="Download"></span>
+
<span id="Download Beta1"></span>
 
* Download and install the STM32MP1 SDK.
 
* Download and install the STM32MP1 SDK.
 
:''By downloading this software package, you agree to be bound to the terms of the [[OpenSTLinux licenses#Limited_License_Agreement|Limited License Agreement]]''. ''The detailed content licenses can be found [[OpenSTLinux licenses|here]]''
 
:''By downloading this software package, you agree to be bound to the terms of the [[OpenSTLinux licenses#Limited_License_Agreement|Limited License Agreement]]''. ''The detailed content licenses can be found [[OpenSTLinux licenses|here]]''
Line 99: Line 189:
 
  │      └── [...]
 
  │      └── [...]
 
  └── version-cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi
 
  └── version-cortexa7hf-neon-vfpv4-openstlinux_weston-linux-gnueabi
<noinclude>
 
 
==Archives==
 
{{InternalInfo|Please copy the content of the older release here when delivering a new release
 
<pre>
 
===XXX release===
 
<div class="NavFrame collapsed">
 
  <div class="NavHead">Details</div>
 
  <div class="NavContent">
 
  ...
 
  </div>
 
</div>
 
</pre>
 
}}
 
   
 
===Alpha2 release===
 
===Alpha2 release===