Some of our example recipes that are meant to be used on specific platform
subsets are available to be built/installed for all platforms. Even though it's
possible to build/install these recipes for platforms they aren't meant for,
we should restrict them to their intended platforms:
* dey-examples-btconfig: this is only meant for ccimx6 platforms that use
the Atheros wifi/bt chip, so reflect this in the recipe and in the
examples packagegroup.
* dey-examples-tamper: this is only meant for platforms with MCA (ccimx6ul,
ccimx8x and ccimx8m). This requirement was already set in the examples
packagegroup, but the recipe was available to any platform.
https://onedigi.atlassian.net/browse/DEL-9612
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Commit 15f9aeba0e removed the dey-examples-v4l2
recipe, yet we still kept it as a dependency for ccimx6 platforms. Remove this
impossible dependency to be able to build the examples packagegroup for ccimx6
platforms.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
connectcore-demo-example multimedia content is only meant for webkit images,
and all this package does in its regular non-webkit version is add a few static
resources. Remove said resources and install only the demo's server + basic
assets.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This commits adds the CCMX91 platform to the DEY
build system. Furthermore, it creates generic ccimx9
support to be used for the CCiMX91 and CCiMX93
platform.
https://onedigi.atlassian.net/browse/DEL-9106
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
Add also 'e2fsprogs-tune2fs' to the image, as busybox's version of
tune2fs command does not support setting the "encrypt" feature of the
EXT4 filesystem.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
ConnectCore Cloud Services examples are included in 'dey-examples' repository
so they can be built from here and also imported in Eclipse/Digi Application
Development Environment for Linux with the samples wizard.
The example 'upload_file' has been removed since currently there is no support
for binary data points in the CCCS daemon/client model.
https://onedigi.atlassian.net/browse/DEL-8628
Signed-off-by: Tatiana Leon <Tatiana.Leon@digi.com>
This commit separates the original 'connectcore-demo-example' package in 3
packages:
1. 'server' package. It contains the 'demoserver.py' script and its
corresponding systemd service and init script.
This script is required for the local demo and to be used with the
Bluetooth application (during the get started process)
2. 'example' package. It contains the html and required resources (images,
javascript, etc.) to use the demo locally, except for the multimedia
resources.
This package depends (in runtime) on the 'server' package.
3. 'multimedia' package. It contains the multimedia html and required
resources (images, javascript, videos, etc.) to use the multimedia demo
features locally.
This package depends (in runtime) on the 'example' package and also on
'video-examples' and 'webglsamples' packages.
This split allows to select the required demo packages per platform and image
type.
By default, the 'multimedia' package is the one included in the webkit images,
but the 'example' package is the one included in the rest of images.
Signed-off-by: Tatiana Leon <Tatiana.Leon@digi.com>
The ConnectCore Demo is launched on startup and starts the web server. Demo can be accessed
by any computer in the LAN by just typing the IP address of the device in the web browser.
Signed-off-by: David Escalona <david.escalona@digi.com>
This commit removes the v4l2 example because they are superseded
by gstreamer examples.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-7211
This allows to generalize the code instead of needing to replicate
overrides for each platform that contains the MCA.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
This commit removes the following examples that were accessing
hardware interfaces:
- dey-examples-adc
- dey-examples-can
- dey-examples-gpio-sysfs
- dey-examples-spidev
- dey-examples-watchdog
The recipe 'dey-examples-digiapix' builds similar examples that make
use of Digi's APIX for accessing the hardware. Add this recipe to images
- dey-image-qt
- core-image-base
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-5169
- For most examples, since they apply to all platforms, remove
COMPATIBLE_MACHINE.
- For recipes related to specific hardware, add support to the new platform
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
While on it:
- add dey-examples-rtc unconditionally (rtc is never in MACHINE_FEATURES)
- add missing recipes: digiapix, cryptochip
- re-order them alphabetically.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
This application tests the MCA comparator feature by configuring
the thresholds, sample rate and other parameters.
Signed-off-by: Sebastian Pastor <sebastian.pastor@digi.com>
https://jira.digi.com/browse/CC6UL-600
The LICENSE is added through the packagegroup bbclass and the checksums
were outdated making the build fail with:
The LIC_FILES_CHKSUM does not match for poky/LICENSE;md5=3f40d7994397109285ec7b81fdeb3b58
https://jira.digi.com/browse/DEL-3451
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
These examples can be used to test Device Cloud functionality. There are three
test applications available:
* device_request_listener: Listen for requests from the Device Cloud
* upload_data_points: Upload test data points to the Device Cloud
* upload_file: Uploads the contents of a file as binary data points
https://jira.digi.com/browse/DEL-3305https://jira.digi.com/browse/DEL-3309https://jira.digi.com/browse/DEL-3397
Signed-off-by: Diaz de Grenu, Jose <Jose.DiazdeGrenu@digi.com>
https://jira.digi.com/browse/DEL-3195
Signed-off-by: Pedro Perez de Heredia <pedro.perez@digi.com>
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This function is deprecated in favor of bb.utils.contains. The same
change has been done in other layers.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
COMPATIBLE_MACHINE is a regular expression, so we need to update the current
pattern for ccimx6 due to it will also match with ccimx6ul.
Signed-off-by: Isaac Hermida <isaac.hermida@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>
dependences for consistency
The GPIO and ADC examples are not meant for the mx6 familiy, so make their
dependences platform dependent
Signed-off-by: Jose Diaz de Grenu de Pedro <Jose.DiazdeGrenudePedro@digi.com>
This is now needed in yocto 1.7. Otherwise it fails with:
ERROR: Please ensure recipe packagegroup-dey-gstreamer.bb sets PACKAGE_ARCH before inherit packagegroup
ERROR: Please ensure recipe packagegroup-dey-examples.bb sets PACKAGE_ARCH before inherit packagegroup
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The availability of some examples depends on the kernel version, so we
need to add the dependence to the packagegroup as well.
This allows to build two ccardimx28 projects one for kernel 2.x and the
other for 3.x sharing the state-cache. Otherwise the first project
builds correctly but the second one fails.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>