This will allow to get advantage of TF-A-STM32MP code update on fiptool
and certtool.
Signed-off-by: Romuald JEANNE <romuald.jeanne@st.com>
Change-Id: Ibc215ac0d78d678633a5f8bc25636da2c99c21a0
Rework the way we set the default settings to avoid missalignment between
FIP_CONFIG and both FIP_BL32_CONF and FIP_DEVICETREE on SDK side.
Avoid also var expansion issue since Kirkstone update as the python
anonymous function schedule has changed. Now var expansion is run for all
available configs.
Signed-off-by: Romuald JEANNE <romuald.jeanne@st.com>
Change-Id: I0f86bc724c458f56cb48fb1be97bb608b2ac740b
When gcnano-userland libs are installed on /vendor/lib folder, we are not
able to link them under SDK.
Add additional symlinks to these shared libs into /usr/lib to fix linking
issue under SDK.
Signed-off-by: Romuald JEANNE <romuald.jeanne@st.com>
Change-Id: Ibac80cd9924487d917cd4bab44c98edd3db3f7ed
When provided device tree is not one of the embedded one in official source
code, we need to set the right configuration switch:
CFG_STM32MP13=1 or CFG_STM32MP15=y
And also we need to manage the DRAM size to configure.
Change-Id: I7d3dc67b89ce2ff1c6330d3ce1b07a5e4344eb61
Signed-off-by: Romuald JEANNE <romuald.jeanne@st.com>
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>
FIP: adapt signature to key by socname
Implement BL32_CONF and DT_CONFIG management from FIP_CONFIG
Change-Id: I8f86cf40b2db480c5c0d2be5c3cf9fcc0ad4c964
Signed-off-by: Romuald JEANNE <romuald.jeanne@st.com>
New class is introduce 'fip-utils-stm32mp.bbclass'
New flashlayout file configuration
New features enable on machine side
Signed-off-by: Romuald JEANNE <romuald.jeanne@st.com>
Change-Id: Ifb5af81b5341ef924b8c22992df20a21bd729e3f
jimtcl repository on repo.or.cz has been abandoned
Signed-off-by: Antonio Borneo <antonio.borneo@st.com>
Change-Id: I077efd18c17618608884a63b561f98b5b300beb5
To manage overlay device tree on U-Boot via boot.scr script:
- add an overlay entry on extlinux.conf without FDT or FDTDIR
- create a directory named 'overlays' on boot directory
- populate 'overlays' with the device tree overlay
- create a file named overlays.txt on overlays directory
- syntax of overlays.txt:
overlay=aa bb cc dd
- aa, bb, cc, dd correspond to a device tree name file (without extension)
present on /overlays/ directory
/overlays/aa.dtbo
/overlays/bb.dtbo
/overlays/cc.dtbo
/overlays/dd.dtbo
Tree of bootfs addons for overlay
/overlays/aa.dtbo
/overlays/bb.dtbo
/overlays/cc.dtbo
/overlays/dd.dtbo
/overlays/overlays.txt
warning: think to add an entry on extlinux.conf without FTDIR or FDTFILE
entry
Signed-off-by: Christophe Priouzeau <christophe.priouzeau@st.com>
Change-Id: I3615d6f03cf874cf3f3c12ea1dd5882bb054542d
On Ubuntu 20.04, devtool cannot be used in recipe inheriting
python3native. Unexport _PYTHON_SYSCONFIGDATA_NAME as a workaround.
To check if it can be revert with next bitbake releases.
Signed-off-by: Lionel VITTE <lionel.vitte@st.com>
Change-Id: I7d73d05e1a5d58dedf69b3aefb3e07c35b92800d
Due to internal override mechanism, we should make sure to add explicitly
all var with their potential override name in 'vardeps' flags.
Signed-off-by: Romuald JEANNE <romuald.jeanne@st.com>
Change-Id: I3fcdbf1bf3856c043987569922c5c60fc0fc7bf9
With new kernel 5.10, the service are no more needed.
Signed-off-by: Christophe Priouzeau <christophe.priouzeau@st.com>
Change-Id: I3d169c2c62a4de61681fa7e437629085f341bb28
Allow to export build info file to DEPLOYDIR.
Signed-off-by: Romuald JEANNE <romuald.jeanne@st.com>
Change-Id: I13801e67837f08faff3691dccdc6856905ac3b49
- Split properly between tf-a-stm32mp and tf-a-stm32mp-ssp.
- Remove use of PV_class-devupstream: no more needed since we avoid using
SRCPV inside default PV (this avoid also misalignment with PV when updated).
- Fix missing fragment files for linux-stm32mp when devupstream in use.
Signed-off-by: Romuald JEANNE <romuald.jeanne@st.com>
Change-Id: I57ed371c9eefce6dc31d816508e99c576a7db91a
Several updates integrated:
- removal of no more supported basic boot scheme
- removal of no more supported boot device (nor-nand and nor-emmc)
- rework of providers and machine features
- introduction of new board versions (a, c, d, f)
- update of extlinuxconf-stm32mp class to manage multiple board versions
- configure 'extlinux.conf' file to manage PARTUUID to select rootfs
partition
- new partition images management (easy to add or remove partition through
new PARTITIONS_CONFIG var
- specific configuration on machine side for all storage device supported
Change-Id: I7e4d3d16535a5654c7fd80f9b56296a61050def3
Setting ${SRCPV} in PR leads to expansion error when using externalsrc with
devtool. The ${SRCPV} expansion is only done when used in PV.
Change-Id: I7e30095b52e6e8f866a58c5beed838fdb96539c0
With Thud 2.6.2, some packages are not installed on sdk due to conflict
between provider. The package target-sdk-provides-dummy should not include
all the list: bash-dev and perl-dev generate the issue.
Note that these packages need to be present on SDK due to dependencies.
Change-Id: I5250fb8607d0cb6206b24290955b91d3f4fb74c0
Signed-off-by: Romuald JEANNE <romuald.jeanne@st.com>
- manage empty UBI volume for multivolume UBI
Add new parameter to allow to add empty UBI volume when creating the
multivolume UBI.
User just need to provide new volume name and size.
- clean temporary file to avoid issue while deploying to image
If we keep the temporary cfg file for empty UBI volume, we have an issue
when bitbake deploy artifacts to DEPLOYDIR_IMAGE when a different image
has been already built as files have the same name.
As we're using this cfg file as a temporary step for multi-volume cfg, we
can remove them instead of deploying them.
- manage extra_space on UBI volume for bad blocks management
Change-Id: If7ef9a66fb058cdaf0d77a22ca0be70fa05fca6f
Signed-off-by: Romuald JEANNE <romuald.jeanne@st.com>
Romuald JEANNE