GCnano userland 6.4.3: symbol not exported by eglGetProcAddress()
Change-Id: I739306248076f018ccba52638830350c47c54032
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>
By default U-Boot reserve overlay sizee with 4KB padding, sometime it is
not enought and it is normal.
The caller NEED to reserved enought memory before to apply overlay
by usisng the <extrasize> parameter.
fdt resize [<extrasize>]
- Resize fdt to size + padding to 4k addr + some optional <extrasize> if needed
A correct value cannot be proposed (it is depending of the overlay size)
but at least you must reserved the size of the loaded overlay dtbo file
=> ${filesize} (this variable automatically updated after a load command)
Change-Id: Ib37f2778bd843436b0baddb67a7a4fd5c799b749
Signed-off-by: Patrick Delaunay <patrick.delaunay@foss.st.com>
The splashscreen name are defined compared to socname
UBOOT_EXTLINUX_SPLASH_<socname> = "<path and name of splash>"
Change-Id: I8b3e3efe79fa436bbb2d35bceade7f6edd51844e
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>
- Allow specific partition image configuration between 'ext4' and 'ubifs'.
- In case ubifs created is larger than max-leb-cnt allocated, mkfs.ubi raise
an error that make bitbake exit on error: add test to avoid this unexpected exit.
Change-Id: Ib386e703cfb1d0434ea17c279abb31f705514019
Signed-off-by: Romuald JEANNE <romuald.jeanne@st.com>
Global flags: ST_DEBUG_TRACE
if ST_DEBUG_TRACE = 1, the debug and trace are activated on all
boot stage
Specific boot stage debug and trace flags:
ST_CMD_LINE_DEBUG_TRACE: addons for remove trace on kernel
ST_UBOOT_DEBUG_TRACE: activate/deactivate silent mode on u-boot
ST_TF_A_DEBUG_TRACE: activate/deactivate trace and debug on TF-A
ST_OPTEE_DEBUG_TRACE: activate/deactivate trace and debug on optee
Change-Id: I09a0c528fcef18f466f0e2b7b46715e2e43c8cf8
Signed-off-by: Christophe Priouzeau <christophe.priouzeau@foss.st.com>
Partitions like vendorfs can be in many cases empty due to not deploying
package targeting that specific partition - see
gcnano-userland-multi-binary-stm32mp as an example. Having a warning for
use-cases that are both common but also valid, would just result in
build noise. This change switches to build notes for flagging an empty
partition.
Change-Id: Iade087b9171dabfaebd498aa13672d2e2f497349
Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>
With Yocto 3.1.9,
Syntax have changed for fit management,
usage of '-' instead of '@'
Signed-off-by: Christophe Priouzeau <christophe.priouzeau@foss.st.com>
Use fip as part-name for fip otherwise tf-a is unable to find the fip
partition:
ERROR: Could NOT find the fip partition!
ERROR: BL2: Failure in pre image load handling (-2)
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
When trying to build with a more recent OE-master version, bitbake ended
up having an issue parsing the rdepends for the target and native build
targets due lack of space when appending bash to rdepends.
Fix by just adding the extra space required when appending values to a
variable.
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
In order to manage multiple defconfig definition for same UBOOT_CONFIG
label, to address subset of devicetree files form UBOOT_DEVICETREE list, we
implement new functionality to provide UBOOT_CONFIG labels with format:
UBOOT_CONFIG += "<uboot_config_label>_<uboot_devicetree_filter_pattern>"
As soon as UBOOT_CONFIG label contains '_' chars, we split it into two
separate parts:
- first one for UBOOT_CONFIG label (used as suffix on binary name)
- second one for pattern (used as filter on devicetree name)
Signed-off-by: Romuald JEANNE <romuald.jeanne@st.com>
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
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
Cedric VINCENT
Lionel VITTE
Romuald JEANNE
Patrick Delaunay
Christophe Priouzeau
Andrei Gherzan
Ricardo Salveti
Pierre-Yves MORDRET