This code path was added in the context of single MTD layout support for
ccimx6ul boards, but it was being executed in the default storage layout use
case as well. This could trigger a race condition in which one code path
deletes the mount point while the other one is still setting it up, causing
partitions to not be mounted automatically (specifically, the "update"
partition).
Since both code paths are mutually exclusive in our implementation, reflect
this by making sure that the single MTD layout path is executed only when said
layout is enabled in the U-Boot environment.
https://onedigi.atlassian.net/browse/DEL-7827
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
(cherry picked from commit 9a7ea10a4dfb74651f865f125372604fe6840a10)
The sign mode needed for each platform is invariable, and since the platform
is already a mandatory parameter for the script, we can store this information
implicitly. Reflect this change in every recipe where the script is used, but
keep the variable at the Yocto level since it's still needed in several places.
https://onedigi.atlassian.net/browse/DEL-7862
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The license checksum and the source branch should be on the properly
versioned bitbake recipes. Otherwise, when we include this common file
in a different version linux recipe (for example, the upcoming 5.10) it
will inherit incorrect values.
While on it, fix the incorrect license checksum values for the linux 5.4
recipes.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This commit updates the US Board Data File (BDF) to include the changes
required to pass the EN 300 328 V2.2.2 blocking test.
The new BDF files are:
- ccimx6/bdwlan30_US.bin (eb3d3cdafd30b30e837974177a281648)
- ccimx8m/bdwlan30_US.bin (72531e6e0870673e4ba2b02bd551925b)
- ccimx8x/bdwlan30_US.bin (1cf667271da33f6eb207360eeb3d4d63)
https://onedigi.atlassian.net/browse/DEL-7773
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This makes it so bitbake obtains the SDMA firmware from the firmware-imx recipe
instead.
This also avoids including all of the linux-firmware packages in i.MX6 SDK
builds, preventing errors when building the ccimx6sbc SDK (linux-firmware
provides the community versions of the ath6k and ar3k firmwares, which clash
with our versions).
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This makes it possible to distinguish between two different packages:
* NXP's tensorflow-lite, which contains modifications for i.MX platforms
* Our tensorflow-lite, which is meant to be used with Google Coral
Since tensorflow-lite-coral provides a subset of the files provided by
tensorflow-lite (specifically, the python libraries), make the packages
conflict during runtime.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This package is used by the eIQ recipes, so make sure we have NXP's .bbappend
so it works as expected
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This is a small oversight on NXP's part, because this package is pulled in as a
dependency of imx-vpuwrap, but it's only compatible with their EVK board,
making the build fail on any other i.MX8MP board.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
It seems like the version of mkfs.vfat used in Yocto 3.3 has a label name
length limit of 11 characters. All of the labels for our current platforms
surpassed this limit ("Boot ccimxX" alone already occupies 11 characters), so
replace the machine name with "DEY"
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
These variables were originally set in NXP's recipes, but they moved their
definitions to each platform's configuration file. Set the appropriate values
where needed. While at it, replace every mention of the SOC_TARGET variable
with its new name, IMX_BOOT_SOC_TARGET.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@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>
The common license file GPL-2.0 is now called GPL-2.0-only in poky, so we need
to reflect this name change to avoid errors
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
NXP now uses the meta-freescale version of the imx-boot recipe as a base, and
applies a .bbappend in meta-imx to apply more customizations. Reflect this
in meta-digi-arm and merge said .bbappend with ours. While at it, omit one of
NXP's operations in their do_deploy, since it breaks our build and doesn't look
essential.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This recipe is only compatible with the i.MX8MP EVK, so it might be
platform-specific or board-specific. Add it for now to be safe.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This recipe was missing from our layer, so add it just in case it's needed
by any new package.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Update the recipes to v8.14. NXP changed the mechanism used to load the sdma
and regulatory firmware (they now use firmwared), so remove our ccimx8mm sdma
fw service for now and see if we need a similar workaround with the new
mechanism.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Mike Engel
Gabriel Valcazar
Javier Viguera
Isaac Hermida
Arturo Buzarra