Add initial support for Digi's ConnectCore 6 QuadPlus SBC.
The ccimx6qp platform has the QCA6564 chip instead of the
other Atheros chips and included the Atmel ECC508A cryptographic
chip.
https://jira.digi.com/browse/DEL-5082
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
As the platform data is only separated by spaces, the data is assigned
to the incorrect variable:
ccardimx28js variants: -
ccardimx28js targets: e w wb web web1 dey-image-qt
After this commit:
ccardimx28js variants: - e w wb web web1
ccardimx28js targets: dey-image-qt
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This is the manufacturing test harness used for the CC6UL module during
manufacturing RF test.
Signed-off-by: Sebastian Pastor <sebastian.pastor@digi.com>
We have seen lately random build failures in the buildserver due to
missing QT5 base libraries that are needed when building some other
QT5 packages.
Examples:
Compiling qtdeclarative:
error: cannot open .../tmp/work/cortexa9hf-vfp-neon-mx6qdl-dey-linux-gnueabi/qtbase/5.5.1+gitAUTOINC+5afc431323-r0/build/lib/libQt5Core.so: No such file or directory
error: cannot open .../tmp/work/cortexa9hf-vfp-neon-mx6qdl-dey-linux-gnueabi/qtbase/5.5.1+gitAUTOINC+5afc431323-r0/build/lib/libQt5Network.so: No such file or directory
error: cannot open .../tmp/work/cortexa9hf-vfp-neon-mx6qdl-dey-linux-gnueabi/qtbase/5.5.1+gitAUTOINC+5afc431323-r0/build/lib/libQt5Widgets.so: No such file or directory
The problem here is that 'qtdeclarative' is trying to get the needed
libraries from the 'qtbase' temporary work directory. But because in the
buildserver we have 'rm_work' enabled to save space, sometimes the
rm-work class has removed the 'qtbase' work directory before
'qtdeclarative' has been built, leading to the compilation error.
This is probably a bug in 'meta-qt5', because the different packages
needing QT5 base libraries should take them at compile time from the
sysroot and not from the qtbase work directory.
At the moment just workaround this adding an exception to the rm-work
class to not remove the 'qtbase' temporary work directory.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The build script was filtering out toolchain builds for all image
recipes not starting with 'dey-image-', but for the CC6UL we are
building by default 'core-image-base', so update the regular expression
to allow building the toolchain for 'core-image-*' image recipes.
https://jira.digi.com/browse/DEL-2837
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
- Added a checker with the job name to declare the manufacturing var
- Changed the name of the repo manifest file for the manufacturing job
- Added a checker to updated the bblayers.conf file with the mfg layer
Signed-off-by: Diego Escalona <diego.escalona@digi.com>
Instead of having one default image target for all platforms allow to
define this per platform.
This is needed because for example for the 'ccimx6ulstarter' we want to
define a default command line image instead of a QT-based one.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Adding sdk support by copying the files from ccimx6sbc and replacing the
machine.
https://jira.digi.com/browse/DEL-2529
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
'build-linux.digi.com' is the old DEL buildserver that sooner than later
will be decommisioned (hopefully) so just don't depend on it for DEY
builds.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
In order to build tiny or tiny-initramfs images, the script adds
the line:
DISTRO_FEATURES_remove = "x11"
to 'conf/local.conf' file.
https://jira.digi.com/browse/DEL-2106
Signed-off-by: Urko Nalda <Urko.Nalda@digi.com>
This is needed when you use a PREMIRROR (as we usually do in buildserver
builds). Otherwise there is a strange corner case where the do_fetch
task fails when the upstream git repo has been rebased and the old mirror
tarball does not have the new SHA1 revision.
ERROR: Function failed: Fetcher failure for URL: 'git://git.yoctoproject.org/matchbox-window-manager'. Unable to fetch URL from any source.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
ccimx51js and ccimx53js are not supported in this version of DEY.
Support for those platforms is in previous versions of DEY.
https://jira.digi.com/browse/DEL-1890
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
There is only one kernel supported for each platform, so there is no
need to explicitly set the kernel preferred version.
Also:
* Remove IS_KERNEL_2X variable which is no longer needed.
* Simplify jenkins build script, now that we do not need to build two
kernel versions for ccardimx28.
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)
This was used just for SARES testing and according to the SA team it is
not needed anymore, so just remove it.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Remove the current DEY variants support and framework for CC6 because in
following commits we will add support for all *hardware* variants in
just one set of DEY images for CC6.
https://jira.digi.com/browse/DEL-1569
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Remove 'dey-test' image feature and create a SARES bbclass with the
same functionality. This makes easier the creation of images suitable
for SARES testing just adding:
INHERIT += "sares-image"
to your project's local.conf
https://jira.digi.com/browse/DEL-1558
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This completes the support for ccimx6sbc variants:
* support device tree variants
* split variants '0x01,0x02,0x04' group in two different groups (with or
without kinetis)
https://jira.digi.com/browse/DEL-1359
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit 3f20015411f4e270b2e2c8faf292678c75ff2aff)
Depending on DY_BUILD_VARIANTS variable (set by Jenkins):
'false': don't build variants (only the default)
<empty>: build all the variants supported by the platform
'var1 var2': build the ones specified in the variable
https://jira.digi.com/browse/DEL-1360
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit de58d3fac52448ee7b1828c6ac71c6c10a3442ff)
These are key packages that we may need to debug in the buildserver, so
do not remove the object files.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Adapt the jenkins build script to build for ccardimx28js by default
linux 3.10 and u-boot 2013.01 and as alternative configuration linux
2.6.35.14 and u-boot 2009.08
https://jira.digi.com/browse/DEL-1168
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Packagegroups define sets of packages to be installed in the rootfs
*depending* on the hardware variant (~MACHINE_FEATURES). For example
installing or not the bluetooth firmware depending on machine variant
having bluetooth.
It may happen that we build sequentially machines with different
features using the same sstate and thus it may happen we end with a
rootfs lacking bluetooth firmware for a bluetooth variant.
So add all packagegroups to the list of packages to purge state-cache
between platform builds.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This is needed so jenkins jobs not using 'meta-digi-dey' (the layer
containing the cleaned recipe) can complete. Otherwise they fail with:
ERROR: Nothing PROVIDES 'packagegroup-dey-examples'
(for example using just the BSP layer 'meta-digi-arm' with standard
image recipes, e.g. core-image-minimal)
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
In the buildserver we share the state-cache for all the different
platforms we build in a jenkins job. This may cause problems with
some packages that have different runtime dependencies depending on
the platform or variant.
Purge then the state-cache of those problematic packages between
platform builds.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
For daily builds just copy the firmware images to avoid running out of
space in the buildserver.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This allows to build 'core-image-minimal' or 'core-image-sato' standard
images using only the BSP layer meta-digi-arm.
https://jira.digi.com/browse/DEL-547
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Arturo Buzarra
Javier Viguera
Alex Gonzalez
Sebastian Pastor
Diego Escalona
Isaac Hermida
Urko Nalda