Commit 8cba3aaefb in 'meta-freescale' changed the kernel_localversion
function we are using in our kernel recipe. This leads to a not-properly
configured kernel build, where CONFIG_MODULES is disabled. That
config option is needed to build external kernel modules in other
recipes, so those recipes (kernel-module-qualcomm, cryptodev-module,
etc) fail to build.
The commit makes sure the kernel is properly configured for building by
extending the do_configure function in a "prepend".
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
By default STM layer creates extra partitions, the vendorfs partition is
reserved to save custom STM libraries and binaries, however the ccmp15 platform
does not have this additional partition, and stores all the libraries in the
rootfs.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
gstreamer recipes was updated to v1.20.3 in poky layer, so this commit updates
the recipe version for custom bbappends.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
weston recipe was updated to v10.0.1 in poky layer, so this commit updates the
recipe version and refresh a custom STM patch.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This commit updates the required firmware binaries for bluetooth and wireless
interfaces, based on the release imx-hardknott-drogon_r1.0 (Wireless firmware
v13.10.246.265)
https://onedigi.atlassian.net/browse/DEL-8021
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Building a toolchain/SDK fails for ccmp15-dvk, because the NXP-based
trustfence tools (for example the cst) are not available. Fix the build
by filtering out those tools when the build platform is not NXP based.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
It's just a waste of space as we already have the kernel image in the
'linux' partition and that gets mounted under /mnt/linux.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The recipe fails to build for the target, but that is expected, as this
is a tool you need to run in the host or from the toolchain/SDK, so
rework the recipes to restrict only for native and nativesdk.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Yocto 4.0 only supports OpenSSL 3.0.x while NXP's CST (code signing
tool) is still using OpenSSL 1.1.x. So the build fails when using the
Yocto-build OpenSSL. Instead, build OpenSSL 1.1.1 as part of the build of
the CST and link statically against libcrypto, so the resulting binaries
(cst, srktool) do not depend on any specific OpenSSL version installed
on the development computer.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
In order to perform the standalone signature process, it was required
to rebuild the Toolchain with Trustfence support enabled.
CST source code is now available for downloading in the Digi FTP, so add
Trustfence sign scripts and cst/srktool to the default toolchain for it
to be used for standalone signature without rebuilding.
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
(cherry picked from commit 2c9b721fb9ce38dcd0034e22d95db6e0ee068955)
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The enable p2p patch add support for enabling p2p as module parameter setting
it by default to false.
The cfg80211 netdevice fixes the registration of virtual interfaces for kernels
v5.12+.
https://onedigi.atlassian.net/browse/DEL-7986
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Also, fix the sequence number of the GPIO_SET_DEBOUNCE_IOCTL ioctl. Same
fix has been done in Linux.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit 16eded4f0edcc603de83be7155f7c09718ba5ddd)
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Remove deprecated versions of recipes updated in other general layers
(poky, meta-openembedded). Also remove duplicated IMX specific recipes that
are available in other BSP layers (meta-freescale, meta-fsl-demos, etc).
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
An outdated 'mesa' bbappend on meta-st-stm32mp is making mesa package
fail to build, due to incorrect configure options.
mesa-22.0.0/meson.build:614:2: ERROR: Problem encountered: kmsro requires dri3 for X11 support
Override the build configuration in our layer until the bbappend gets
fixed in ST layer.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Yocto is becoming more strict on not using tags in the SRCREV, as that
may lead to problems in the different tasks of a bitbake recipe.
As of Yocto 4.0, bitbake errors when such condition happens, with:
"Recipe uses a floating tag/branch without a fixed SRCREV"
So convert the SRCREV of all tags to the proper SHA1 revision.
Also, extend the 'fix-build-issues' to delete '-Werror' from the
compilation flags. Newer versions of GCC (as the one used in Yocto 4.0)
throw more (new) warnings, and the '-Werror' flag was making the build
to fail.
cc1: all warnings being treated as errors
lim_api.c:1057:17: error: this 'if' clause does not guard... [-Werror=misleading-indentation]
lim_admit_control.c:169:17: error: this 'if' clause does not guard... [-Werror=misleading-indentation]
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
* fix arch tune files path in machine config
* update imx-digi-base config file (using as a base the imx-base.inc
config file in 'meta-freescale')
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
By default, the STM layer includes several tools in the SDK, one of which is
the gcc-arm-none-eabi toolchain. However, in the build process it throws the
following unexpected error about an unsatisfied runtime dependency:
Error:
Problem: conflicting requests
- nothing provides libpython2.7.so.1.0()(64bit) needed by
nativesdk-gcc-arm-none-eabi-9-r0.1.x86_64_nativesdk
Since this package works with python3, python2 was deprecated and this tool is
only needed to build Cortex-M4 applications, this commit removes this package
from the default SDK.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This commit adds a patch for the qcacld-3.0 wireless driver to read the
wireless MAC addresses from device tree. This patch is based on the original
commit from qcacld-2.0 driver improving and simplifying the code to work with
the new qcacld-3.0 driver.
https://onedigi.atlassian.net/browse/DEL-7916
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This commit updates the wireless firmware in order to work with the new Linux
qcacld-3.0 wireless driver.
Latest release "r10016.1 - Post-CS3 1.0.016.1" updates the following files from
"qca6574au-le-2-2-1_qca_oem" product branch:
PCIe:
- athwlan.bin (b4fd36922625b7303d006581f6c7cd10)
- utf.bin (0d70048214fea05d1c40b3034e8107cd)
SDIO:
- qwlan30.bin (342cb50ce5c6ff930a65f341c0dfbc77)
- utf30.bin (f94810be89cc2f3e979ab4a57243872b)
https://onedigi.atlassian.net/browse/DEL-7916
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This commit updates the Linux wireless driver for Qualcomm's chipset to the
new qcacld-3.0 driver.
This update is based on the release "r10016.1 - Post-CS3 1.0.016.1" from
"qca6574au-le-2-2-1_qca_oem" product branch, which uses for a Linux kernel v5.4
the tag "CHSS.LNX_FSL.5.0-01200-QCA6574AUARMSDIOHZ".
https://onedigi.atlassian.net/browse/DEL-7916
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Commit 8c396281 ("layer: add dynamic-layers for NXP platform") introduced a
typo in the dynamic layer name.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This commit reverts partially the commit 548b8729 ("image_types: add support to
create CCMP15 ubifs images") to fix the boot partition generation.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This platform initializes the Bluetooth interface through the own bluetooth
driver, so the custom Digi init scripts are not needed.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This commit changes the "Image" for the "zImage" as the default kernel image
type for the STM platform.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Javier Viguera
Arturo Buzarra
Isaac Hermida
Gonzalo Ruiz