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>