public
/
meta-st-stm32mp
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Local fork of github.com:STMicroelectronics/meta-st-stm32mp.
222 Commits 1 Branch 0 Tags 7.9 MiB
C++ 27.1%
PHP 26%
BitBake 18.1%
Shell 12.9%
Pascal 10.7%
Other 5.1%
Go to file
Romuald JEANNE af9ec1ddf8 TF-A-STM32MP: add file type for deploying image 
When a compilation a made for TF-a with 'all' target, several binaries are generated
and have the same name on several kind of build but generated with different
compilation switch. In some case (like arm64 bits) the bl2 need to generate a
bl31 binary but without the specific option requested by the generation of official bl31,
which can generate an issue when you deploy the file because it's the binary of
last build which are used but it's not in all case the binary with compilation
option desired.
For solving this king of issue, a flag <file type> which can be : bl31 b32 bl2 fwconfig
are added on the TF_A_CONFIG to specify which kind of binary we need to export.

Change-Id: Ibd484ae2e285bf70e3e0790e020d2ea595506a3c
Signed-off-by: Christophe Priouzeau <christophe.priouzeau@foss.st.com>
 		2021-11-16 17:56:04 +01:00
classes CLASSES: EXTLINUX: add support of several splash screen 2021-11-16 17:56:04 +01:00
conf CLASSES: EXTLINUX: add support of several splash screen 2021-11-16 17:56:04 +01:00
files FILES: default flashlayout files update for dv3.0 2021-03-26 16:55:54 +01:00
recipes-bsp TF-A-STM32MP: add file type for deploying image 2021-11-16 17:56:04 +01:00
recipes-connectivity/bluetooth WIFI-SUSPEND: remove service 2021-03-26 10:37:20 +01:00
recipes-core Revert "DROPBEAR: remove "disable-weak-ciphers" config for CUBE IDE 1.3.0 compatibility" 2020-11-09 10:20:09 +01:00
recipes-devtools STM32WRAPPER4DBG: rework recipes to use only one 2021-11-16 17:56:04 +01:00
recipes-extended M4PROJECTS-STM32MP1: update to V1.4.0 2021-03-26 16:55:54 +01:00
recipes-graphics Remove duplicate patch/config 2021-03-03 09:17:00 +01:00
recipes-kernel CONF: enable kernel config file deploy 2021-11-16 17:56:04 +01:00
recipes-multimedia/pulseaudio AUDIO: update configuration 2019-10-09 11:24:57 +02:00
recipes-security/optee CONF: put DEBUG and trace under flags 2021-11-16 17:56:04 +01:00
recipes-st MACHINE: rework INITRD configuration 2021-11-16 17:56:04 +01:00
recipes-support HIDAPI-STM32MP: Cleanup wrong use of ${SRCPV} in PR recipe var 2020-06-23 17:23:50 +02:00
wic WIC: add uuid for sdcard 2021-11-16 17:56:04 +01:00
.gitignore MACHINE: rework configuration to introduce FIP feature 2021-03-26 16:55:54 +01:00
CONTRIBUTING.md Add CONTRIBUTING file 2020-04-27 11:51:14 +02:00
COPYING.MIT Add License of Layer 2019-02-04 15:26:45 +01:00
License.md openstlinux-4.19-thud-mp1-19-02-20 release 2019-02-05 11:54:23 +01:00
README Add README 2019-02-04 15:26:30 +01:00
README.md README: Correct email address of maintainer 2019-05-03 09:24:57 +02:00

README.md

Summary

meta-st-stm32mp BSP layer is a layer containing the STMicroelectronics bsp metadata for current versions of stm32mp.

This layer relies on OpenEmbedded/Yocto build system that is provided through Bitbake and OpenEmbedded-Core layers or Poky layer all part of the Yocto Project

The Yocto Project has extensive documentation about OE including a reference manual which can be found at:

For information about OpenEmbedded, see the OpenEmbedded website:

This layer depends on:

[OECORE]
URI: https://github.com/openembedded/openembedded-core.git
layers: meta
branch: same dedicated branch as meta-st-stm32mp
revision: HEAD
[BITBAKE]
URI: https://github.com/openembedded/bitbake.git
branch: branch associated to oecore branch
revision: HEAD

or

[OECORE]
URI: git://git.yoctoproject.org/poky
layers: meta
branch: same dedicated branch as meta-st-stm32mp
revision: HEAD

[META-OPENEMBEDDED]
URI: git://github.com/openembedded/meta-openembedded.git
layers: meta-python meta-oe
branch: same dedicated branch as meta-st-stm32mp
revision: HEAD

The dependency (meta-python) are due to the usage of OPTEE which require to use some python packages.

EULA

Some SoC depends on firmware and/or packages that are covered by STMicroelectronics EULA. To have the right to use those binaries in your images you need to read and accept the EULA available as:

conf/eula/$MACHINE, e.g. conf/eula/stm32mp1

In order to accept it, you should add, in your local.conf file:

ACCEPT_EULA_$MACHINE = "1", e.g.: ACCEPT_EULA_stm32mp1 = "1"

If you do not accept the EULA the generated image will be missing some components and features.

Contributing

If you want to contribute changes, you can send Github pull requests at https://github.com/stmicroelectronics/meta-st-stm32mp/pulls.

Maintainers