* meta-ml was renamed to meta-imx-ml, and its BBFILE_COLLECTIONS was renamed to
imx-machine-learning
* meta-st-stm32mpu-ai was renamed to meta-st-x-linux-ai
https://onedigi.atlassian.net/browse/DEL-9011
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This includes also an update and rename of the Edgelock Enclave firmware
package (firmware-ele-imx).
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
An anonymous function in linux-stm32mp.inc produces a bbfatal error when
KERNEL_DEVICETREE variable contains more than one device tree. This is our
case since we build the main DT plus a number of DT overlays.
This commit removes the dependency to this include file since we have our
own recipe to build the kernel and it is not needed at all.
It also removes the build of a uImage and the need to provide a
LOADADDR.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
The name of the variable was not very intuitive of what
it contains. This variable expands to the SoC vendor
(NXP or STM).
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
This dependency is only required if you wish to build ST's reference images,
which isn't our case. Add said reference images' recipes to the BBMASK to
avoid build errors.
https://onedigi.atlassian.net/browse/DEL-8308
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
For now, we're only interested in generating the SBOM, which we can upload and
have Vigiles scan later on if needed. The report generation process adds some
overhead and can cause unwanted errors if the Vigiles server takes too long.
Enable report generation for our automated builds.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
As that's an old VM with limited specs, there is no much gain on using
it over the canonical Stash repositories that justifies the code
overhead and the possible errors due to synchronization problems.
Signed-off-by: Javier Viguera <javier.viguera@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 removes some STM recipes that are not
needed in our layer because they apply changes that
are not required in our DEY layer.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
The recipe we ported from meta-imx has the same version number (v2.4) and
bitbake chooses the meta-freescale version because said layer comes before
meta-digi-arm in the BBLAYERS. Since the meta-freescale version uses different
platform overrides, the build fails, so filter it out to use our version
instead.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Required for the release rel_imx_5.4.70_2.3.0 based on zeus
https://jira.digi.com/browse/DEL-7397
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Update the README as well to reflect this change, since the ftp protocol might
be blocked in some corporate networks.
https://jira.digi.com/browse/DEL-6880
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
In 92c49b9b1a16dfd35444db8143bd4cae4cda70cc was introduced the LAYERSERIES_CORENAMES
and LAYERSERIES_COMPAT_<layername> with the intention of allowing layers
to indicate which versions of the core project they're compatible with.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
The MACHINE_EXTRA_RRECOMMENDS for the ccimx6ul in meta-digi-arm contains
cryptoauthlib. If we want to use meta-digi-arm as a standalone BSP layer
we need to move the cryptoauthlib recipe to meta-digi-arm, that or not make it
a machine dependency.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
meta-fsl-arm is no longer used for Morty release. Now the community
support is implemented in 'meta-freescale' layer.
https://jira.digi.com/browse/DEL-3451
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Use LAYERDEPENDS to configure the layer dependences for meta-digi-arm
and meta-digi-dey.
https://jira.digi.com/browse/DEL-1129
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
As the plan is to use the same git objects (SHA1) in the internal and
github repos, also remove that internal/external SRCREV infrastructure.
https://jira.digi.com/browse/DEL-2205
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
https://jira.digi.com/browse/DEL-1734
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit 35a78b13f72963205dc1ae1e05ee851ca6cc4f28)
It has never been a mirror of upstream packages.
It's the URL of packages needed for the BSP. These packages are mostly
Digi specific and not provided in any other location.
https://jira.digi.com/browse/DEL-1493
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit d4cf9a88c9db39c6ecfd0099437d82af81c96e85)
Most SRC_URI defaults to DIGI_LOG_GIT. This patch sets a more generic
name (DIGI_GIT) that defaults to DIGI_LOG_GIT, but is configurable by
someone who might want to tune it (DIGI_MTK_GIT, etc.).
Signed-off-by: Seth Bollinger <sethb@digi.com>
This is the FTP site where the release artifacts will be placed. It's
structure will be something like:
x.y.z/
source
images
toolchains
adt-installer
https://jira.digi.com/browse/DEL-473
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
If you don't want to use meta-digi-del and use only the BSP layer
(meta-digi-arm) to build a generic image (like core-image-minimal) you
need the DIGI_MIRROR variable in this layer because some of the BSP
recipes (kernel, u-boot) use it to get the source.
So this allows to build core-image-minimal for Digi platforms without
using meta-digi-del.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Gabriel Valcazar
Javier Viguera
Hector Palacios
Arturo Buzarra
Mike Engel
Hector Bujanda
Alex Gonzalez
Seth Bollinger