In case of storage not present on specific devicetree we encounter
some issue at flashlayout generation.
Signed-off-by: Christophe Priouzeau <christophe.priouzeau@foss.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
To manage different kind of boot sequence, add a variable which
define the boot sequence to used.
When the parition teeh are flashed only 300 bits are writed and
it's not enought to overwrite the filesystem header of bootfs in
case of trusted boot.
Change-Id: I8b9e307689aff56e30b65e3d47626e3bf2e4e36f
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
Due to a dependency with libb64, sysdig move on bsp layer
Change-Id: I379dcc2e77d18bd2f735145f86bbb99bff6065c4
Signed-off-by: Christophe Priouzeau <christophe.priouzeau@st.com>