If device is a SMARC, use SMARC properties to log in sysinfo (serial
number, variant, hardware version). If not, use SOM properties.
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
Replace current MOV video file not supported by Chromium with a MP4
video file with the same video content.
https://onedigi.atlassian.net/browse/DEL-10156
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
Add an mp4 example video, with the same contents as the mov file:
1280x720, MPEG-4 format.
Also, for ccimx95, due to Chromium limitations, install the mp4 file
instead of the mov file.
https://onedigi.atlassian.net/browse/DEL-10156
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
ConnectCore 95 integrates the Murata 2EC Wi-Fi module and requires applying the
vendor custom patch set across the supported releases.
https://onedigi.atlassian.net/browse/DEL-10142
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Update nl80211 definitions to match Linux v6.6.116, preventing extended feature
mismatches and fixing parsing of driver-reported capabilities.
https://onedigi.atlassian.net/browse/DEL-10142
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Adjust the ccimx95-specific networking pieces so they no longer inherit
the IW612-specific behavior from ccimx9:
- use wlan1/p2p0 instead of uap0/wfd0 where appropriate
- install hostapd_wlan1.conf instead of hostapd_uap0.conf
- restore virtual WLAN handling for ccimx95
- avoid IW612-specific suspend/resume actions such as moal reload and
load_iw612.sh
Signed-off-by: Francisco Gil <francisco.gilmartinez@digi.com>
Some Bluetooth controllers may expose hci0 even when the firmware
initialization has not completed correctly. In that state, the init
script may report success but bluetoothd cannot use the controller.
Validate the controller through the kernel management interface before
accepting the initialization as successful. This matches the interface
used by bluetoothd and catches controllers that are visible through HCI
but not registered in MGMT yet.
Use a timeout for the MGMT query so a broken controller state cannot
block the init script instead of falling back to the retry loop.
https://onedigi.atlassian.net/browse/DEL-9512
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Add full support to face-recognition demo so it can be integrated in the
webkit demo.
Improvements are:
* support for USB camera
* use 640x480 resolution so it fits in our COG demo
https://onedigi.atlassian.net/browse/DEL-10133
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Expand the BT_GPIO placeholder after installing the init script, so
optional scripts such as bluetooth-init_atheros are handled the same way.
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Make the minimal changes needed to adapt the original X-LINUX-AI example and
integrate it into the Digi custom launcher.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Restore the V4L2SRC based pipeline for USB webcams that was dropped in newer
X-LINUX-AI releases, fixing USB camera support on the v6.2.0 baseline.
https://onedigi.atlassian.net/browse/DEL-10040
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Read the QR serial number from /proc/device-tree/serial-number and the
MAC address from the U-Boot ethaddr environment variable.
Include digi,drm-ic in the QR payload only when present, and update the
console output and provisioning message accordingly.
Signed-off-by: Francisco Gil <francisco.gilmartinez@digi.com>
After refactoring these scripts in a8c6dcb56e, some platforms are
not setting the enable line correctly.
Regarding the affected platforms, on the 6UL it works because that GPIO
comes enabled by default, but not on the other ones.
For the other platforms refactored, such as the CC91/93 or CCMP25,
it is not needed, as the variable is used directly in the gpioset command.
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
CCCS service starts before the network is fully ready and fail the first
connection attempt. When that happens, the daemon waits for the
configured reconnect interval before trying again, which delays DRM
availability for dependent services.
https://onedigi.atlassian.net/browse/DEL-10083
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
This commit generalizes the BT GPIO value used in the bluetooth-init
script for different platforms.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://onedigi.atlassian.net/browse/DEL-9668
The bbappend hardcoded an old libsocketcan revision. Remove the override
so the recipe uses the revision from meta-openembedded. Also refresh our
patch, so it applies cleanly on top of the new revision.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Module ccimx95 enables the mca machine feature, but it does not support
dey-examples-adc-cmp or dey-examples-tamper. Move the MCA example list
to DEY_EXAMPLES_MCA and clear it for ccimx95.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This commit replaces systemd-udev-settle from bluetooth-init and
ifupdown service. Systemd recommends not to use that service and
wait for specifc event or service to sync interfaces.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://onedigi.atlassian.net/browse/DEL-9338
Add QR code generation to sysinfo using U-Boot serial and
MAC address information, with support for both standard
and legacy payload formats.
When requested with --qr_display, show the QR code using the
most suitable backend for the running system
https://onedigi.atlassian.net/browse/DEL-9281
Signed-off-by: Francisco Gil <francisco.gilmartinez@digi.com>
Restrict nxp-wlan-utils to ccimx91 and ccimx93. The ccimx95 uses the
Murata wireless chip.
https://onedigi.atlassian.net/browse/DEL-9990
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
(cherry picked from commit cd9a79152866ed2fcc91a2316d6a4f9eb3e72266)
(cherry picked from commit eb3d6e0355)
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>
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>
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>
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>
Synchronize the dcmipp-isp-ctrl recipe with the meta-OpenSTLinux layer from the
openstlinux-6.6-yocto-scarthgap-mpu-v26.02.18 tag. Although the version string
appears to be a downgrade, the recipe points to a newer commit (SHA1),
following ST’s versioning.
https://onedigi.atlassian.net/browse/DEL-10021
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This fixes the build failure caused by the OpenSSL update in Poky.
Import the OpenSSL patch set from NXP's whinlatter release. Since NXP's
whinlatter release is based on OpenSSL 3.5.4, rebase the patches on top
of OpenSSL 3.5.5 to match the current version.
https://onedigi.atlassian.net/browse/DEL-10019
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Use placeholders and machine-configurable variables to determine systemd
behavior when receiving power key events.
By default, these are:
- short press: suspend
- long press: graceful poweroff
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
Arturo Buzarra
Gonzalo Ruiz
Francisco Gil
Isaac Hermida
Hector Bujanda
Mike Engel
Javier Viguera
Gabriel Valcazar
Hector Palacios