A patch sent upstream has been finally merged so this commit is not
needed anymore.
This reverts commit 6a66656161.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
module-udev-detect blocks the sound interface on boot for about five
seconds while detecting the hardware. This patch removes it so that
module-detect is used instead, which uses static hardware detection and is
faster.
https://jira.digi.com/browse/DEL-2218
Signed-off-by: Jose Diaz de Grenu de Pedro <Jose.DiazdeGrenudePedro@digi.com>
Old versions of u-boot 'v2013.0x' have a bug in the shell's test command
that makes structures like:
if test "${not-existing}" = "0x01"; then ...
if test -z "${not-existing}"; then ...
to fail when the checked variable does not exist.
So implement workarounds in the updater script to overcome this problem.
This is needed because the script may be used in modules with an old
pre-installed u-boot.
https://jira.digi.com/browse/DEL-2231
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The install script allows for an easy deployment of the DEY firmware
artifacts into the eMMC of the ConnectCore 6 by using a micro SD card.
The install script:
- updates U-Boot
- resets the U-Boot environmnet to default values
- formats the User Data partition of the eMMC
- installs the firmware images (linux and rootfs partitions)
- resets/starts the system
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-2192
The canonical symlinks created by poky's U-Boot class in u-boot.inc for
the different U-Boot configs are in the form:
u-boot.imx-<config>
u-boot-<machine>.imx-<config>
These symlinks have the .imx file extension hidden in the middle of the
file name, which looks ugly.
For DEY, remove these unused symlinks and generate new ones in the form:
u-boot-<config>.imx
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-2192
Move this variable to DEY distro conf so that it is available for any
recipe built with the distro.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-2192
There is another OpenGL demo application QT5 Hello Windows for testing
purposes.
https://jira.digi.com/browse/DEL-2184
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
It has been observed that the wireless interface ocassionally fails to resume
from suspend on extensive long run validation testing, so we workaround it by
bringing the interface down before suspend and bring it up again after resume
This reverts commit a77cd1406d.
https://jira.digi.com/browse/DEL-2217
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
This image provides a demo rootfs with QT. It can be built for
framebuffer and also for X11.
https://jira.digi.com/browse/DEL-2196
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
There are different SBC boards IDs each one having a different
device tree file in the form imx6X-ccimx6sbc-idZZZ.dtb, where:
X is the CPU family (q=Quad/Dual, dl=DualLite/Solo).
ZZZ is the board ID number.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-2160
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>
We were masking meta-fsl-arm linux recipes to clean some warnings on
bitbake parsing. This does not happen anymore with new versions of
Yocto, so just remove this BBMASK.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Carrier board version is determined by U-Boot variable $board_id
which will be defined if a board ID has been burned on certain
OTP bits.
Use the value in this variable to create the $fdt_file variable
using the suffix "-id${board_id}" to point to the device tree
file that matches that board ID.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-2160
This install the 'obexd' server which is needed for the QT5 bluetooth
file transfer example applications.
https://jira.digi.com/browse/DEL-2147
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Generalize bluetooth support so it can be used not only with bluez4 but
with bluez5 as well. Use EXTRA_QMAKEVARS_PRE to pass the packageconfig
options to the do_configure task.
https://jira.digi.com/browse/DEL-2147
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This is a user-space workaround for the reboot/poweroff problems we
are having in the ccimx6sbc. Seems that they are not reproducible when
only one core is enabled, so the workaround is to disable the rest of
the cores for rebooting/halting.
https://jira.digi.com/browse/DEL-2133https://jira.digi.com/browse/DEL-2148
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit a9e36a74bb20ab38f220116ba2742dca3d80c293)
Also initialize the video sink to 'glimagesink' in case it has not been
configured from the environment, but only for the X11 application
(gtk-play). This recipe also provides a command line application for
framebuffer (gst-play) that is not affected by this change.
https://jira.digi.com/browse/DEL-2132
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This disables images prelink, which according to the mailing lists it's
broken for ARM and other architectures. It's also reported to make gdb
fail sometimes.
https://jira.digi.com/browse/DEL-2150
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The example applications are not packaged by default, so extend the
recipe to create a package with the example applications.
https://jira.digi.com/browse/DEL-1960
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The script toggles the BT power GPIO regardless of the value being
undefined.
Check that the GPIO is defined before trying to toggle it.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
The BT power GPIOgpio was determined basing on machine name on device tree.
This corresponds to the name of the board, and might be changed by a user
that designs his own carrier board to use the module on.
Besides, the BT power GPIO is a pin that's routed on the module (both on
the ConnectCore 6 and on the ConnectCard for i.MX28) not on the carrier
board.
This commit determines the BT power GPIO basing on the module string inside
the 'compatible' property. This must exactly match the module name and is
a required property for using Digi module's BSP.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-2109
So we can build a 'dey-image-graphical' image for framebuffer with
support for QT5.
https://jira.digi.com/browse/DEL-2017
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
No functional change, as 'package-management' is added via the included
dey-image-minimal recipe, and 'pointercal-xinput' is a dependence of
xinput-calibrator which is added for X11 images.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
By default QT5 applications use 'xcb' platform plugin but this can be
changed using the QT_QPA_PLATFORM environment variable. On non-X11
images the 'xcb' platform plugin obviously does not work, so just
configure 'eglfs' for non-X11 images.
https://jira.digi.com/browse/DEL-2017
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
There are some demo apps that otherwise fail with:
QSqlDatabase: QSQLITE driver not loaded
QSqlDatabase: available drivers:
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This demo app is very generic and does not play well with FSL gstreamer
plugin, so using it just crashes in different ways (doing a camera zoom,
recording a video, etc)
This reverts commit 2776dcd654.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
That's the u-boot configuration used by variants 0x07 and 0x09, which
have been cancelled and are no longer supported by DEY.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Javier Viguera
Jose Diaz de Grenu de Pedro
Hector Palacios
Isaac Hermida