The ccmp25 WebKit container needs a small set of extra device nodes
to run the embedded AI demos reliably.
Bind only the device nodes validated on target for the browser demos:
galcore, DRM, framebuffer, input, and the camera video/media/subdevice
nodes used by the AI examples.
https://onedigi.atlassian.net/browse/DEL-10038https://onedigi.atlassian.net/browse/DEL-10039
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
The WebKit container profile was missing runtime pieces that are
present in the native WebKit image and required by the embedded
ConnectCore demos.
Add the font and icon packages needed by the fish tank WebGL demo,
include the Weston and GStreamer runtime packages used by the browser
demo stack, and switch the ccmp25 profile to the GCNano userspace
packages used by the native image.
Keep the machine learning packagegroup scoped to ccmp25, since the
ST X-LINUX-AI subset and its demo integration are specific to that
platform.
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Standalone GPU and video tests perform as expected in the WebKit
container, but rendering degrades once Cog runs on top of Weston.
Align the container Weston startup with the native setup by
loading the default Weston options, enabling the systemd-notify
module and exporting WL_EGL_GBM_FENCE=0 before starting the compositor.
https://onedigi.atlassian.net/browse/DEL-10038https://onedigi.atlassian.net/browse/DEL-10039
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Package recommendations are disable, so some recommended packages might
be missed.
For HW detecting add the next explicit packages, which solves the
microSD card detection.
https://onedigi.atlassian.net/browse/DEL-10042
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
(cherry picked from commit cd9a79152866ed2fcc91a2316d6a4f9eb3e72266)
(cherry picked from commit eb3d6e0355)
This commit adds support for environment encryption/decryption of the
u-boot environment on the CCMP2 platform in Linux.
https://onedigi.atlassian.net/browse/DEL-10029
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
(cherry picked from commit 9b99c0b073)
Remove the ccmp1x machine restriction from the sample recipes, since they
support both CPU and NPU variants.
https://onedigi.atlassian.net/browse/DEL-10045
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This commit adds support for environment encryption/decryption of the
u-boot environment on the CCMP2 platform in Linux.
https://onedigi.atlassian.net/browse/DEL-10029
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Add a bootscript for the ConnectCore 95 platform, including the default device
tree overlay names.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
We initially created this patch when adding XWayland support for the ccimx6 and
ccimx6qp back in dey-3.0-r2.1 (commit eda2f4177e), but we ended up removing
it in dey-4.0-r1.beta1 (commit 526cb3cae0). Even though the blank screen
issue isn't nearly as reproducible as it was back when it was initially
discovered (it used to have a 66% chance of happening), it can still occur
every now and then, especially on the ccimx6 when using an LVDS display.
Adapt the patch to weston 10.0.5.imx and apply it to fix the issue.
https://onedigi.atlassian.net/browse/DEL-7236
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This partially reverts commit f6d91b9022. The new
mca-tool v1.26 already installs its binaries to /usr/sbin (instead of /sbin),
so the workaround is no longer needed.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
ST updated the AI layer from v6.1.1 to v6.2.0, which means our v6.1.% bbappend
is no longer applied. Update the recipe version to match the new X-LINUX-AI
release.
https://onedigi.atlassian.net/browse/DEL-10027
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
The latest ST release (openstlinux-6.6-yocto-scarthgap-mpu-v26.02.18) checks for
the presence of several TF-M-related variables at parse time, even when they are
not used. This triggers build failures with the new M33-TD flavor variables
required by the TF-M recipe.
Set default (dummy) values for these variables to avoid the parse-time failures.
This is a workaround until full support for building secure TF-M binaries is
integrated.
https://onedigi.atlassian.net/browse/DEL-10022
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
The original do_install() preserves file ownership, which can contaminate the
SDK build and cause "getpwuid(): uid not found: 1000". Adjust the copy command
to not preserve owner/group.
https://onedigi.atlassian.net/browse/DEL-10022
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This commit imports the Digi custom version of sign-stm32mp bbclass to ensure
that the search_path() function does not raise a build exception if the signing
tool or keys are not present in the PATH before starting the build process.
In our case, we do not need to manually install the tools or generate the keys
beforehand, as this is automatically handled by Yocto in our DEY distribution.
https://onedigi.atlassian.net/browse/DEL-10022
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Commit 3fdb245765 ("trustfence: add encrypted
boot artifact support for CCMP13 platform") broke PKI tree generation when
encryption is disabled. Fix it for ccmp15.
https://onedigi.atlassian.net/browse/DEL-10022
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Commit 52a1111da6d72446530da26e135b65a34b48e279 ("OPTEE: MANAGE signature,
M33TD") in the ST layer incorrectly enables CFG_REMOTEPROC_PUB_KEY_VERIFY=y for
all platforms when SIGN_ENABLE is set.
However, co-processor public key verification against OTP fuses is not
supported on stm32mp1x platforms and causes the build to fail.
Remove CFG_REMOTEPROC_PUB_KEY_VERIFY for ccmp15.
https://onedigi.atlassian.net/browse/DEL-10022
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Remove the TF-A specific toolchain from SDK generation to avoid build issues
caused by unresolved runtime library dependencies in nativesdk-gcc-aarch64-none-elf,
including libcrypt.so.1, libncursesw.so.6, libpython3.8.so.1.0, and
libtinfo.so.6.
https://onedigi.atlassian.net/browse/DEL-10022
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Update secure boot support for Cortex-M processors by refreshing the patch set
and dropping patches already integrated, aligning the implementation with ST
release openstlinux-6.6-yocto-scarthgap-mpu-v26.02.18.
https://onedigi.atlassian.net/browse/DEL-10022
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Since commit d29b92ed9935 ("CLASS: SIGN: manage signature for coprocessor")
in meta-st-stm32mp from tag openstlinux-6.6-yocto-scarthgap-mpu-v26.02.18, the
SIGN_HEADER_VERSION variable is required.
Set the appropriate SIGN_HEADER_VERSION value for each platform.
https://onedigi.atlassian.net/browse/DEL-10022
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Set KillMode=process in the systemd unit so 'systemctl stop
cc-containerd' only terminates the daemon itself.
Without this, systemd uses the default control-group kill mode and
can terminate container processes that share the service cgroup,
which changes container runtime state when the service is stopped.
https://onedigi.atlassian.net/browse/DEL-9963https://onedigi.atlassian.net/browse/DEL-10005
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Document dey-image-container-manager in meta-digi-containers and
update the ccmp25-dvk and ccimx95-dvk build template notes so the
image is listed during environment setup together with its
virtualization requirement.
https://onedigi.atlassian.net/browse/DEL-9996
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Add the dey-image-container-manager image recipe to provide a
dedicated DEY image for container management using the trimmed LXC
and Podman runtimes from meta-digi-containers.
https://onedigi.atlassian.net/browse/DEL-9996
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Add dedicated trimmed runtime wrappers for LXC and Podman in
meta-digi-containers so dey-image-container-manager can install
reduced container runtimes without affecting other DEY images.
https://onedigi.atlassian.net/browse/DEL-9996
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Add the artifact packaging stage that assembles deployable LXC/Podman
bundles with a normalized layout (manifest, payload, checksums, metadata).
The task also computes digests/metadata and removes intermediate build
outputs once final artifacts are produced.
https://onedigi.atlassian.net/browse/DEL-10004
Signed-off-by: Francisco Gil <francisco.gilmartinez@digi.com>
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Introduce the base dey-image-container recipe and split core logic into
dedicated include files for rootfs overlays, LXC bundle generation and
Podman archive conversion.
This commit defines the profile-driven variables/overrides and the
native build tasks required to produce runtime-specific container outputs.
Also allow the recipe to overwrite WAYLAND_DISPLAY on init scripts to match
with different platforms.
https://onedigi.atlassian.net/browse/DEL-10004
Signed-off-by: Francisco Gil <francisco.gilmartinez@digi.com>
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Add the new meta-digi-containers layer skeleton for Yocto 5.0 and wire it into bitbake layer discovery.
This initial layer commit provides:
- layer metadata and compatibility/dependency declarations
- recipe/bbappend file discovery for container-related content
- base structure used by subsequent commits for container images and runtime integration
https://onedigi.atlassian.net/browse/DEL-10004
Signed-off-by: Francisco Gil <francisco.gilmartinez@digi.com>
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Until now the key modifier was being read from 'hwid_n' device tree
entries, but now those entries reflect the environment HWID, which
could be temporarily overriding the fuse HWID.
Ensure the key modifier is generated from the new 'hwid_fuse_n'
device tree entries created by U-Boot with the contents of the
fuse HWID, just as U-Boot does to encrypt/decrypt the environment.
https://onedigi.atlassian.net/browse/DEL-9123
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
Remove options that aren't supported in v9.3.0 (LV_MEM_CUSTOM and
LV_TICK_CUSTOM_*) and move the lvgl-demo's default values to lv-conf.inc so
they can be changed via local.conf
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
LVGL v9.3.0 added support for multi-touch gestures via the
USE_GESTURE_RECOGNITION option, but in doing so, they made all touchscreen
support depend on said symbol, at least for the wayland backend. Since the
option is disabled by default, touchscreen support wasn't working in the
wayland version of the demo.
Enable gesture recognition/touchscreen support by default when using the
wayland backend. This depends on LVGL's floating number support, so make sure
this is reflected in the recipe as well.
https://onedigi.atlassian.net/browse/DEL-9925
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Now that we support the LVGL wayland backend, include the weston desktop in
dey-image-lvgl images, like we used to in older DEY versions.
This reverts commit db3e526b31.
https://onedigi.atlassian.net/browse/DEL-9925
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
We only want to recover the libinput patch that fixes the cursor issue in the
LVGL demo, don't recover the wl_shell patch.
This partially reverts commit 7afc4a67de.
https://onedigi.atlassian.net/browse/DEL-9925
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Rework our customizations and apply them as full files instead of patches to
make it easier for users to inspect.
Instead of having one cmake file for all backends, provide a separate file for
each backend and select it dynamically based on the selected backend. To do
this, create a new LVGL_BACKEND variable in lv-conf.inc.
While at it, increase the demo's memory from 256 KiB to 2 MiB to ensure that
the wayland flavor of the demo works properly.
https://onedigi.atlassian.net/browse/DEL-9925
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This backend depends on libsdl2, a library we don't include in our default
images. Even when this library is included, the LVGL demo doesn't work properly
when using the SDL backend on any of our platforms, so remove it.
https://onedigi.atlassian.net/browse/DEL-9925
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
We're going to be adding support for LVGL's wayland backend in the following
commits, so recover the initscript logic that ties in with said backend
This reverts commit 21d9c4f17b.
https://onedigi.atlassian.net/browse/DEL-9925
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This is mostly logic to convert the backend configured in the PACKAGECONFIG to
the lv_conf.h file, based on the DEY 4.0 version of the recipe. Add weston as
a runtime dependency to make sure the final image has a wayland compositor and
recover DEY 4.0's mechanism to fall back to a minimal backend if wayland is
missing from DISTRO_FEATURES
Use the wayland backend by default in all platforms except the ccimx6ul
https://onedigi.atlassian.net/browse/DEL-9925
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Isaac Hermida
Mike Engel
Arturo Buzarra
Gabriel Valcazar
Hector Bujanda
Hector Palacios
Francisco Gil
Gonzalo Ruiz