When using fitImage as kernel image type the fitImage already contains the
device tree blob files. So, it's not necessary to add them to the image
boot files.
Signed-off-by: Weisser, Pascal <pascal.weisser.ext@karlstorz.com>
Add the relevant configuration for an i.MX 95 SoC so that the
mali-imx recipe is selected for userspace GPU support (EGL, GLES...).
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Using the UUU-tagged bootloader image directly with UUU can cause UUU
to hang. The bootloader image is split on a certain transmit size, and
the hang occurs if the tag does not fit with the final bytes of the
bootloader image and must be split into a new transmit package.
The UUU tag is needed by UUU only in the SD Card image file itself so
that UUU can find the end of the boot partition.
Rework the design so the default bootloader and the default imx-boot
binaries are not tagged.
Also, extend the UUU tagging to fslc so it can gain the same benefit.
Fixes: https://github.com/Freescale/meta-freescale/pull/1762
Fixes: https://github.com/nxp-imx/mfgtools/issues/416
Co-authored-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
Add the full set of 1.22.5 compatible recipes with the following
exceptions due to build breaks for obsolete components:
- gstreamer1.0-omx: Drop the recipe
- gstreamer1.0-plugins-ugly: Drop liba52 and mpeg2dec support
These exceptions mirror changes in the upstream support:
9c21815339 gstreamer1.0: update 1.22.11 -> 1.24.3
90fbfe9fe1 liba52: remove the recipe
d46660e6c0 mpeg2dec: remove the recipe
(From OE-Core rev: ae9c64cd2291f4b24ac442816a4e354e47c70933)
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
Commit 9a522207 ("firmware-imx: Use vpu-amphion and vpu-wave suffix.")
renamed the vpu firmware package name from firmware-vpu-imx8 to
firmware-imx-vpu-amphion.
Follow that in the setting of MACHINE_FIRMWARE setting.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Update the recipe to be aligned with the NXP BSP LF6.6.3-1.0.0.
Add installing of a second part of ELE to rootfs.
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@foundries.io>
Upgrade the optee-client to 4.0 to be aligned with NXP BSP LF6.1.55_2.2.0.
Relevant changes:
- acb0885 teec: use multiple of page size for page aligned buffers
- 6178477 cmake: pkgconfig file: install the file
- 46831ac pkgconfig file: remove extra comments
- 3ac968e Makefile, cmake: move teec related headers
- 2dd250b cmake: remove whitespace before parenthesis
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@foundries.io>
Since [1] the firmware-sentinel is renamed to firmware-ele-imx.
It also align the recipe to be aligned with the NXP BSP LF6.1.55_2.2.0.
[1] 6412faf7e4
Signed-off-by: Daiane Angolini <daiane.angolini@foundries.io>
Using 'aarch64', as if the WKS_FILE_DEPENDS was conditioned to the
userspace's architecture, will not include imx-boot in a multilib context
(e.g., for a 32-bit userspace). This happens because 'aarch64' will not
be listed in OVERRIDES, and the error below will come up during do_image_wic
task:
wic.filemap.Error: cannot open image file
'.../build/tmp-glibc/deploy/images/microej-imx93/imx-boot':
[Errno 2] No such file or directory
Replace 'aarch64' by mx*-generic-bsp, for both imx8 and imx9, as these
two are aarch64 platforms.
Signed-off-by: Joao Marcos Costa <joaomarcos.costa@bootlin.com>
Using 'aarch64', as if the OPTEE_BOOT_IMAGE was conditioned to the
userspace's architecture, will include uTee-${OPTEE_BIN_EXT} in a multilib
context (e.g., for a 32-bit userspace). This happens because 'aarch64' will not
be listed in OVERRIDES, and the error below will come up during do_image_wic
task:
output: install:
cannot stat '...build/tmp-glibc/deploy/images/microej-imx93/uTee-':
No such file or directory
Replace 'aarch64' by mx*-generic-bsp, for both imx8 and imx9, as these
two are aarch64 platforms.
Signed-off-by: Joao Marcos Costa <joaomarcos.costa@bootlin.com>
Using 'aarch64', as if the KERNEL_IMAGETYPE was conditioned to the
userspace's architecture, will cause the wrong image type to be built in
a multilib context (e.g., for a 32-bit userspace). This happens because
'aarch64' will not be listed in OVERRIDES, and the error below will come
up during do_image_wic task:
output: install:
cannot stat '...build/tmp-glibc/deploy/images/microej-imx93/zImage':
No such file or directory
Replace 'aarch64' by mx*-generic-bsp, for both imx8 and imx9, as these
two are aarch64 platforms.
Signed-off-by: Joao Marcos Costa <joaomarcos.costa@bootlin.com>
The A1 SECO firmware run on a B0 board can brick the board unless it can be
switched to USB serial download to force an update. Because of this, drop
the ambiguous machine config file and make the rev explicit in the machine
config name.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
Rework imx-boot and use-imx-security-controller-firmware.bbclass with a
generic SOC revision design implemented in imx-base.inc. This does
replace the machine feature design using `soc-rev*`, but maintains
backwards compatibility by incorporating that design into the default
settings.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
There is a general jailhouse recipe in other layers which causes a
version conflict. Introduce jailhouse-imx recipe to avoid conflict.
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@foundries.io>
Upgrade optee-test to be aligned with NXP BSP LF6.1.22_2.0.0.
Relevant changes:
- c2c9f92 ta: crypto_perf: update TEE_Param according to GP131
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@foundries.io>
