Otherwise, systemd will have to guess the PID of the service's main process.
It guesses right most of the time, but sometimes it chooses the PID of the
original pulseaudio process instead of the daemon that gets forked off. This
caused the daemon to stop immediately after starting, breaking other apps that
require the pulseaudio server to be running.
Since the PID file is created in a user-specific runtime directory (and the
service is meant for the whole system), modify the wrapper script to create
a symlink to the PID file in a place where it can be obtained by systemd.
https://jira.digi.com/browse/DEL-6795
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Digi Embedded Yocto 2.6-r2.2
Manually changed recipes to use the master branches instead of the fixed SHA1
from the last release.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Otherwise, systemd will have to guess the PID of the service's main process.
It guesses right most of the time, but sometimes it chooses the PID of the
original pulseaudio process instead of the daemon that gets forked off. This
caused the daemon to stop immediately after starting, breaking other apps that
require the pulseaudio server to be running.
Since the PID file is created in a user-specific runtime directory (and the
service is meant for the whole system), modify the wrapper script to create
a symlink to the PID file in a place where it can be obtained by systemd.
https://jira.digi.com/browse/DEL-6795
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The default service only starts once per non-root user. Add a service that
starts pulseaudio by default along with a wrapper script that sets the
necessary environment variables before launching the daemon.
https://jira.digi.com/browse/DEL-6746
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Use ifupdown variable 'p2p-network-id' to pass a WPA supplicant network
id, to pre-populate some parameters (SSID/passphrase) when creating the
group where this device is the GO.
Also replace go_intent=7 with the auto parameter. According to the
documentation:
"auto" can be used to request wpa_supplicant to automatically
figure out whether the peer device is operating as a GO and if so,
use join-a-group operation rather than GO Negotiation.
https://jira.digi.com/browse/DEL-6741
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This commit fixes the error message when specific network scripts
are launched.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-6728
This was reported by the build:
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:
devtool modify <recipe>
devtool finish --force-patch-refresh <recipe> <layer_path>
This is the result of running the above commands to have
the patches automatically updated on their context lines:
devtool modify weston
devtool finish --force-patch-refresh weston meta-digi-dey
While on it, remove also the initial "From <SHA1>" lines.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
Add support for greengrass 1.9.2 and remove it for 1.9.0.
Support for 1.9.0 was never released and that version is
no longer available.
Signed-off-by: Francisco Gil <francisco.gilmartinez@digi.com>
The most current revision is incompatible with the v4.9 Linux UAPI. Reverting
to the previous commit of the imx-alsa-plugins repo reverts the UAPI changes
while keeping the same functionality, so use this revision for the ccimx6 and
ccimx6qp.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Latest meta-fsl-bsp-release tag 'rel_imx_4.14.98_2.1.0' replaces the
imx-alsa-plugins recipe from the meta-freescale upstream layer to fix
the build with the kernel 4.14. The commit cde60d6 ("asrc_pair: update
according to latest mxc_asrc.h") fixes the build issues.
https://jira.digi.com/browse/DEL-6732
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Trustfence is not yet fully supported for the CC8X.
Retore the warning.
This reverts commit 78534ca779.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
Update SRCREV and SRCBRANCH in most recipes. Update imx-gst1.0-plugin to
v4.4.7.
https://jira.digi.com/browse/DEL-6722
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Change the recipe name to an older version (v6.2.4.p1.8). This is done because
there haven't been any changes in the source code since said version.
https://jira.digi.com/browse/DEL-6722
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Update to v6.2.4.p4.2. Make sure to keep the "wayland" distro feature check
out of the recipe to be able to compile framebuffer images for the ccimx8x.
https://jira.digi.com/browse/DEL-6722
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The correct recipe that need to be used is located at
meta-digi-dey/recipes-qt/demo-extrafiles/
removing all the QT applications that are not included anymore in
rootfs.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-6690
This commit enables gstreamer support when built qtmultimedia. Also
sets the gstreamer plugin video source for QT.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-6691
Otherwise, users that are behind corporate firewalls might not be able to
obtain the package sources.
https://jira.digi.com/browse/DEL-6663
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This way, we assure that the openssl binary is included in the rootfs whenever
the base openssl package is included.
https://jira.digi.com/browse/DEL-6710
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Remove the 'mstructure-size-boundary' flag. This flag is not supported in
ARM64 toolchains, and without it the fbtest application works fine.
https://jira.digi.com/browse/DEL-6498
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
Commit c6e963f9e ("lvm2: Add RDEPEND on lvm2 to lvm2-udevrules")
in meta-oe layer added a package dependency for lvm2. This dependency
includes many unnecessary packages like lvm2, lvm2-scripts, etc.
and their dependencies that increase the size of the initramfs image.
Since lvm2-udevrules is not necessary for our initramfs image,
this commit removes the RRECOMENDS.
https://jira.digi.com/browse/DEL-6701
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Commit 074e3ba3 ("meta-digi-dey: add cryptsetup tool into initramfs") added
the runtime dependency to cryptsetup for all platforms, but it is
required only to encrypt/decrypt block devices.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This commit disables file system check on the root file system when it is encrypted.
This prevents the service from failing on encrypted rootfs with the message:
[FAILED] Failed to mount /run/media/mmcblk0p3.
See 'systemctl status run-media-mmcblk0p3.mount' for details.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-6655
The functionality provided by this bbappend is now available in meta-oe
upstream, commit 7f17da154372b5ec33947766783444961e8aa67c.
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
After some fixes to cloudconnector, all packages compile with the standard
GCC version in Yocto Thud (gcc 8.2).
Some other packages are broken if we do not use the expected GCC version for
Thud. Specifically, this was detected trying to compile docker.
This reverts commit ddd14144c3.
The artifacts that must go inside the installer ZIP image are not anymore
the ones in UBOOT_CONFIG. For CC8X, the artifacts are combinations of
UBOOT_CONFIG and RAM_CONFIGS.
This commit adds a function 'get_bootable_artifacts()' to boot-artifacts class
to generate a new variable BOOTABLE_ARTIFACTS with the list of bootable
artifacts DEY produces.
The installer recipe can then simply iterate on that list, rather than
needing to calculate it by itself.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6641
A variable called IMAGE_BOOTLOADER was being used without distinction for
referring to two different things:
- the recipe that builds the bootable artifacts
- the prefix of those artifacts
The value of this is "u-boot" for most platforms, but "imx-boot" for the
CC8X based platforms.
The name of the variable is misleading, so this commit splits it into two:
- BOOTLOADER_IMAGE_RECIPE, to refer to the recipe
- UBOOT_PREFIX, to refer to the prefix of the bootable artifact
With the separation, the variable UBOOT_SYMLINK becomes a generic formed
one, so it is moved to digi-defaults.inc.
While on it, fix the image_types_digi.bbclass which was not making use of
the original variable to establish all the dependencies.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
This commit exports several internal headers and libraries
to allow link against them in user applications.
https://jira.digi.com/browse/DEL-6649
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
These packages are included in ccimx6/6qp/6ul images because they are a part of
packagegroup-core-x11-sato, which isn't included in ccimx8x images. To assure
that pulseaudio always gets included in non-fb images, add it as a dependency
in packagegroup-dey-audio.
https://jira.digi.com/browse/DEL-6464
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Since the original .bb file is already in the meta-digi layer, bitbake will
look inside of the bluez5-5.41 folder by default, so this line isn't needed.
https://jira.digi.com/browse/DEL-6448
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This commit modifies the weston ini file to support a custom
background and includes a new one with Digi branding.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Modify bluetooth init script to use kernel module to power on/off
the bluetooth chip instead of managing it directly from sysfs.
https://jira.digi.com/browse/DEL-6615
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
These icons have never been included in the filesystem until a recent commit in
poky (522b0d8615cdc6645f6dc37a03ea7584f19c7bfc). In total, they take up over
1 MiB and have been causing filesystem tests to fail on the ccimx6ul due to low
space.
Add a .bbappend to undo the commit's changes in our layer.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This fixes the problem of shell console returning to the login prompt
after a successful login.
Signed-off-by: David Escalona <david.escalona@digi.com>
To avoid possible conflicts with NetworkManager, remove systemd-networkd
entirely.
https://jira.digi.com/browse/DEL-6610
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
-p : Test the standard periodic interrupts (uses timers, doesn't wake from low power)
-u : Test the standard 1 Hz interrupt (uses RTC ALARM)
-v : Test MCA periodic interrupts (uses RTC PERIODIC_IRQ)
-w : Test MCA 1 Hz interrupt (uses RTC 1HZ)
https://jira.digi.com/browse/DEL-6602
Signed-off-by: Hector Bujanda <hector.bujanda@digi.com>
The Replay Protected Memory Block (RPMB) is an special storage
partition that cannot be accessed via standard block layer.
When a user space tool like blkid, tries to read it the kernel
suffers buffer I/O errors and timeouts.
This commit modifies the post installation script to filter the RPMB
partitions from the mmc block devices, to avoid multiple kernel
errors during the script execution.
https://jira.digi.com/browse/DEL-6609
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Removed the platform dependency to apply the resize to all platforms.
https://jira.digi.com/browse/DEL-6609
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
The Replay Protected Memory Block (RPMB) is an special storage
partition that cannot be accessed via standard block layer.
When a user space tool like blkid, tries to read it the kernel
suffers buffer I/O errors and timeouts.
This commit modifies the post installation script to filter the RPMB
partitions from the mmc block devices, to avoid multiple kernel
errors during the script execution.
https://jira.digi.com/browse/DEL-6609
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Removed the platform dependency to apply the resize to all platforms.
https://jira.digi.com/browse/DEL-6609
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This recipe is an example for customer for a system-monitor. Scripts that
verify the system status can be added to /etc/system-monitor.d
The recovery mechanisms can be implemented on those scripts or in the
system-monitor script. The software watchdog systemd support is used to
guarantee that the system-monitor is running.
When using this it is recommended to enable the systemd hardware watchdog
support, refer to the systemd documentation for this.
The systemd service provided by this recipe is not enabled by default as it
is an example that needs customization.
https://jira.digi.com/browse/DEL-6593
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
Also create the folders that contain the scripts attending each
dispatch event type.
https://jira.digi.com/browse/DEL-6575
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Instead of the 20 seconds hardcoded currently in the code, allow to
configure the response timeout in the connectivity section of the main
NetworkManager config file.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Currently in a systemd based init, the httpd server is not launched. A
systemd service is needed, so add it.
Also install a CGI script that allows to use the device for the
NetworkManager connectivity check.
https://jira.digi.com/browse/DEL-6577
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This recipe is an example for customer for a system-monitor. Scripts that
verify the system status can be added to /etc/system-monitor.d
The recovery mechanisms can be implemented on those scripts or in the
system-monitor script. The software watchdog systemd support is used to
guarantee that the system-monitor is running.
When using this it is recommended to enable the systemd hardware watchdog
support, refer to the systemd documentation for this.
The systemd service provided by this recipe is not enabled by default as it
is an example that needs customization.
https://jira.digi.com/browse/DEL-6593
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
Also create the folders that contain the scripts attending each
dispatch event type.
https://jira.digi.com/browse/DEL-6575
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Instead of the 20 seconds hardcoded currently in the code, allow to
configure the response timeout in the connectivity section of the main
NetworkManager config file.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Currently in a systemd based init, the httpd server is not launched. A
systemd service is needed, so add it.
Also install a CGI script that allows to use the device for the
NetworkManager connectivity check.
https://jira.digi.com/browse/DEL-6577
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
There's a recipe in the thud branch of meta-openembedded specifically for the
opencl-headers package, but it's also provided by imx-gpu-viv. This generates
build errors when parsing the recipes and when populating the sysroot for
opencv.
https://jira.digi.com/browse/DEL-6603
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Make our vulkan sub-folder match NXP's by updating recipes, deleting ones that
are no longer needed and adding new ones. Also, stop forcing 1.0.65% as the
preferred vulkan version.
https://jira.digi.com/browse/DEL-6603
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This is the version used in meta-fsl-bsp-release branch sumo-4.14.98-2.0.0_ga.
https://jira.digi.com/browse/DEL-6603
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This is the version used in meta-fsl-bsp-release branch sumo-4.14.98-2.0.0_ga.
Change the .bbappend name so it's compatible with all versions of the package.
https://jira.digi.com/browse/DEL-6603
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This is the version used in meta-fsl-bsp-release branch sumo-4.14.98-2.0.0_ga.
Change the .bbappend name so it's compatible with all versions of the package.
https://jira.digi.com/browse/DEL-6603
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This is the version used in meta-fsl-bsp-release branch sumo-4.14.98-2.0.0_ga.
https://jira.digi.com/browse/DEL-6603
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This is the version used in meta-fsl-bsp-release branch sumo-4.14.98-2.0.0_ga.
The code revision is exactly the same as the one in v6.2.4.p2.3, so simply
rename the recipe and delete files that are not necessary anymore.
https://jira.digi.com/browse/DEL-6603
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This is the version used in meta-fsl-bsp-release branch sumo-4.14.98-2.0.0_ga.
https://jira.digi.com/browse/DEL-6603
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This is the version used in meta-fsl-bsp-release branch sumo-4.14.98-2.0.0_ga.
Instead of having one common .inc file and one .bb file per architecture,
we now have one common .bb file for both architectures.
https://jira.digi.com/browse/DEL-6603
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This is the version used in meta-fsl-bsp-release branch sumo-4.14.98-2.0.0_ga.
https://jira.digi.com/browse/DEL-6603
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This is the version used in meta-fsl-bsp-release branch sumo-4.14.98-2.0.0_ga.
https://jira.digi.com/browse/DEL-6603
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The watchdog and ADC devices were not being modified to belong
to 'digiapix' group, so the examples did not run properly when
ran as a user different than root.
Reported-by: Andreas Burghart <andreas.burghart@digi.com>
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6581
This patch is included in the rocko and sumo branches of poky to avoid errors
when starting an xserver using DRI, but it was removed in the thud branch in
favor of newer input methods other than SIGIO. SIGIO is still supported, but
not explicitly in the xserver configuration.
Since the vivante driver on the i.MX6 is using DRI and, by extension, SIGIO
(even though there is no way to configure xserver to enable SIGIO support), the
only way to make xserver start correctly is by removing the SIGIO support check
in the code.
https://jira.digi.com/browse/DEL-6565
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Even though systemd support is not yet available for these platforms, add the
scripts so bitbake doesn't fail when building the busybox package.
https://jira.digi.com/browse/DEL-6565
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
* Use the same operation order when resuming interfaces
* Remove unnecessary delay in ccimx6sbc standby script
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Otherwise, bitbake will try building the aarch64 version of the package and
fail when building ccimx6 images.
https://jira.digi.com/browse/DEL-6565
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Digi Embedded Yocto 2.6-r1.3
Manually changed recipes to use the master branches instead of the fixed SHA1
from the last release.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
The exported PWM channels now report the channel name under udev
EXPORT parameter.
Add the 'change' udev action type to the udev rules and use that
parameter to change the group ownership of the PWM channels to
digiapix group, so they can be used by non-root user.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
For some reason, even though the general RDEPENDS for this package is correct,
all items are overwritten by the empty class-native version of RDEPENDS, even
when building for the target. Because of this, whenever this python module is
installed and used, it won't work.
Redefine the dependencies needed by the target until the issue is fixed
upstream.
https://jira.digi.com/browse/DEL-6553
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Some modems take a lot of time to initialize and ModemManager won't
see them on its first scan.
This service will force a rescan 40 seconds after boot, to give
enough time for those lazy modems.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6366
This recipe adds a script and a related systemd service that
configures two GPIOs (user defined, or else platform-defaults) as
output and sets them to the appropriate value for initializing the
XBee socket:
- XBEE_SLEEP_RQ: is set low, for running the XBee
- XBEE_RESET_N: is set low and then high, to reset the XBee
The service triggers on the condition that the UART TTY device node
pointed to by variable XBEE_UART exists.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6366
On the default device tree, the MCA UART that's connected to the
XBee socket is enabled. This registers as ttyMCA0.
Add a udev rule for this path so that ModemManager checks for
modems in this serial port.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6366
With the re-organisation of the python3 packaging, some of the
packages have disappeared and are now part of base packages.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Otherwise, packagegroup-dey-core won't get included in ccimx6ulstarter images.
This packagegroup contains fundamental OS elements, such as sysvinit, kernel
modules and so on. Use CORE_IMAGE_BASE_INSTALL instead and make sure to append
to the default value instead of overwriting it.
https://jira.digi.com/browse/DEL-6536
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
For CC6/CC6Plus
- Add USER_LED0 alias (same as default USER_LED)
- Change aliases of the other LEDs to USER_LED1 and
USER_LED2 (without additional underscore and fixed
indexes, to match the board schematics)
For CC8X SBC Pro
- Add USER_LED0 alias (same as default USER_LED)
- Add USER_LED1 which was missing
- Increase indexes (due to removed MCA_IO19 on SOM v3)
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
This modifies the behavior of the sd-resolve libsystemd component to prevent
the system from freezing whenever a service that uses said component is
stopped. Even though this doesn't free the terminated thread's resources
properly, this procedure only gets executed during the final moments of a
service's process before it exits, so resource leaks aren't an issue.
https://jira.digi.com/browse/DEL-6523
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@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
This reduces the number of files that must be modified when changing
branches between development/release modes.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
Organize the common code in the recipe to make easy the
inclusion of new greengrass versions.
Signed-off-by: Francisco Gil <francisco.gilmartinez@digi.com>
This way, the wlan1 interface will only be created whenever a user wants to
bring the interface up with ifupdown. Modify the script to be able to delete
the interface whenever it gets brought down and remove its .sh file extension
so run-parts can run it properly during the ifup process.
https://jira.digi.com/browse/DEL-6353
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Tests have shown that having this interface up hinders wlan0's performance,
so don't bring it up by default.
https://jira.digi.com/browse/DEL-6353
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Update u-boot-fw-utils patches to apply on current upstream version. Remove
recipe for version 2017.09 since both U-Boot v2017.03 and v2018.03 work fine
with the newer version.
https://jira.digi.com/browse/DUB-881
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
This version is only required to build U-Boot 2017.X, so select it as preferred
version only on those platforms that build this U-Boot (CC6 and CC6UL).
https://jira.digi.com/browse/DUB-881
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
The device-tree being used on a system is a very important piece of
information to debug issues. On a host machine, dtc can be used to
reconstruct the DTS used from the /proc/device-tree folder structure.
While on it, remove extra white lines at the beginning and end.
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
This script introduces a minor delay when the own script
launch the wpa_supplicant daemon, however this minor delay
is needed in the boot process when the wireless interface
is loaded, if not the bridge mechanism throws an unexpected
error trying to add the interface to the bridge before the
wireless is ready to use.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Since our initscript contains logic to dynamically generate the path containing
the greengrass daemon (it changes depending on the version), keep it in the
rootfs. Create a symlink to it inside of /etc/init.d for sysvinit images and
create a systemd service wrapper that calls it on systemd images.
https://jira.digi.com/browse/DEL-6510
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Soften the dependencies between the services and start the bluetooth stack
regardless of the existence of a bluetooth chip. Also, update the standby
script to reflect that there is no longer a strong dependency between the
services.
https://jira.digi.com/browse/DEL-6452
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Unlike eudev, which is used on images without systemd, the list of paths
systemd-udev uses to look for rules is very limited. Include an upstream patch
(commit 116b91e8ccfee1d44fc2b140d831d688e3747902 in the systemd repo) that
expands said list.
This fixes an issue with crda's regulatory domain rule file, which was being
excluded due to it being in a path systemd-udev was ignoring (/usr/lib/udev).
Because of this, the regulatory domain was never set properly and hostapd was
failing when configured to use 5GHz channels (which is the default config).
https://jira.digi.com/browse/DEL-6504
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
To avoid bringing up interfaces before they're created by udev scripts
(specifically wlan1), wait until udev settles before starting the service.
https://jira.digi.com/browse/DEL-6504
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
When using systemd, putting the wlan1 interface up wasn't working because it
was relying on initscripts that are no longer in the filesystem.
Add a parametrized version of the upstream hostapd service to be able to use a
configuration that's different from the default one. Also, modify the
generation of the wlan1 entry in /etc/network/interfaces to be able to use
different post-up/pre-down hooks depending on the init manager that's being
used.
https://jira.digi.com/browse/DEL-6504
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This change was added to meta-openembedded layer by commit
0814df2e9179b71b5f5c99b962aca35ede1f242f.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Since the version 1.12, NetworkManager enables the colors in the
terminal output by default. This pretty output is not compatible
with several terminal emulators and makes it difficult to parse
the output of the CLI commands.
This patch uses the standard linux util called 'terminal-colors.d'
to disable the colors by default in the NetworkManager CLI interpeter.
https://jira.digi.com/browse/DEL-6473
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Latest update to version 1.29.3 in upstream breaks the compatibility
of our bbappend, to avoid it in future updates, this commit
generalizes the bbappend to apply all the 1.29 series.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Add pulseaudio audio profile for MAX98089 sound card and
generalize the recipe to support multiple platforms with
the same audio sound card.
https://jira.digi.com/browse/DEL-6461
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
The driver now builds directly from the kernel source and the
fixes are already included in the kernel tree so there is no need
to build the module externally.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6460
(cherry picked from commit a0990a7e1dcd03af239efb620b83b7dee126484e)
This is a user space tool to manage BATMAN advanced network interfaces.
https://jira.digi.com/browse/DEL-6466
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
systemd-tmpfiles throws warnings of /var/run being deprecated in favor of /run.
Even though this is corrected automatically, the warnings appear several times
during runtime, polluting the systemd journal.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Similar to what we did on sysvinit, stop dnsmasq from starting automatically
on boot so NetworkManager can launch it via dbus.
https://jira.digi.com/browse/DEL-6415
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The postinst script tries parsing the wireless MAC address from the sysfs, and
in case of failure, obtains a random string from /dev/urandom. This caused two
problems when booting with systemd:
* The wifi interface's sysfs entry is not available because the interface
hasn't had time to start up yet, forcing the script to always resort to the
/dev/urandom fallback.
* Even though the postinst scripts are run after populating the volatile
filesystems (as can be seen in run-postinsts.service's dependencies), trying
to read either /dev/random or /dev/urandom at this point in the system's
initialization causes it to lock up indefinitely.
To avoid either situation, add the following changes:
* Immediately exit when running on a non-wireless target, as the script isn't
necessary in this use case.
* Parse the wireless mac address from /proc/device-tree/wireless, which is
guaranteed to always be available when the script runs. By doing this, we can
remove the /dev/urandom fallback entirely.
https://jira.digi.com/browse/DEL-6415
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This script behaves the same way as our custom standby script, with a few
modifications, for example:
* instead of using initscripts to stop/start daemons, it uses systemctl calls
* save variables that are needed when resuming in /tmp, because the script is
executed twice instead of once (when suspending and when resuming)
* remove the locking/unlocking of the critical section and the actual state
change, since that is handled by systemd-suspend now
Also, add a different standby script for when systemd is enabled. Said script
acts as a wrapper for systemd's suspend mechanism.
https://jira.digi.com/browse/DEL-6415
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
These changes are needed in order to achieve a behavior similar to our
bluetooth initscripts'.
https://jira.digi.com/browse/DEL-6415
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This service acts as a systemd replacement for our bluetooth-init initscript.
All it does is call the initscript before starting the bluetooth stack.
Since initscripts dissapear from /etc/init.d when disabling sysvinit, move the
script to /etc/. Also, include bluez5-init as a packagegroup-dey-bluetooth
dependency regardles of whether systemd is enabled or not.
https://jira.digi.com/browse/DEL-6415
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
These patches don't apply on the latest version of systemd used in Yocto 2.6.
https://jira.digi.com/browse/DEL-6415
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Without systemd, our KEY_POWER events were handled by the ACPI daemon, which in
turn issued a "poweroff" command. With systemd, the ACPI daemon is no longer
available and the events are handled by systemd-logind instead, which also
powers down the system properly. However, NXP added a patch that prevents
system-logind from handling the events, since they use the sc_powerkey instead.
Remove this patch to be able to power the target off via our power button.
https://jira.digi.com/browse/DEL-6415
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Otherwise, there will be errors due to missing dependencies.
https://jira.digi.com/browse/DEL-6415
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
These have been ported directly from NXP's meta-fsl-bsp-release layer.
https://jira.digi.com/browse/DEL-6415
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Since poky commit b6fbb3f3d4d6367b0fd7921078f67057551c7ede
reboot config was moved to init.cfg to provide this configuration
when busybox is selected as the init manager, however it is needed
for initramfs images where no init manager is set (see poky commit
ef4a417ab04779bd9fc8a6540a20cca7d14e98cf).
https://jira.digi.com/browse/DEL-6451
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Since commit 4b41d9072a304fadbe1cc37c94575f12a2a47fd3 in poky
busybox removes the RRECOMENDS dependency with busybox-syslog,
then we need to explicitly add this dependency in the recipes.
https://jira.digi.com/browse/DEL-6443
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Remove git recipe to use the official 1.8.2 release and update
udev rules file to blacklist the network interfaces that ModemManager
must not manage.
https://jira.digi.com/browse/DEL-6412
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Commit 491082c56ce34f3fd644f8d4457ccd52af951087 in poky layer enables
by default some security enhancements and optimizations for the compiler,
These extra checks added by the flag -D_FORTIFY_SOURCE=2 break the
CloudConnector build. This commit disables the extra validations only
for the CloudConnector recipe.
https://jira.digi.com/browse/DEL-6412
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Removed patches already integrated in the OpenSSL code and
refreshed the necessary ones.
https://jira.digi.com/browse/DEL-6412
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Wireless tools is deprecated in favor of iw because the
wireless extensions have been deprecated in favor of the
new nl80211 interface for wireless devices.
https://jira.digi.com/browse/DEL-6412
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
The defconfig file has been refreshed for the current busybox
version 1.29.2 maintaining the same applets enabled.
https://jira.digi.com/browse/DEL-6412
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This script was added a long time ago and it never gets used anymore, so remove
it from our images.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The point of this recipe is to provide the version of Bluez5 that was
certified. Thes certification does not apply to the ConnectCore 8X, and the
recipe currently fails to build due to missing files. Hence filter out the
ConnectCore 8X from this recipe.
This clears the following warnings:
WARNING: meta-digi/meta-digi-dey/recipes-connectivity/bluez/bluez5_5.41.bb: Unable to get checksum for bluez5 SRC_URI entry bluetooth-init: file could not be found
WARNING: meta-digi/meta-digi-dey/recipes-connectivity/bluez/bluez5_5.41.bb: Unable to get checksum for bluez5 SRC_URI entry main.conf: file could not be found
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
(cherry picked from commit bf9688fd08ac9e8823a5a253bdd1acacd1c0870e)
Trustfence is not supported in the CC8X at the moment. This cleans the
following warning:
WARNING: meta-digi/meta-digi-dey/recipes-core/trustfence/trustfence-initramfs.bb: Unable to get checksum for trustfence-initramfs SRC_URI entry trustfence-initramfs-init: file could not be found
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
(cherry picked from commit 778fc424274fc0983c348f4da6ca09e1a7b5b859)
vpx was wrongly removed when updating the recipe to version 1.14, but it's
required to build x11 images for the ccimx6ulsbc.
https://jira.digi.com/browse/DEL-6078
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
(cherry picked from commit 1e2244afcd)
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
CC8X SBC Pro's LPUART0 port is routed to the Expansion connector.
The UART located in the XBee socket, MCA UART, is not currently supported
so comment the XBee Cellular rule for the moment.
https://jira.digi.com/browse/DEL-6417
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
The defconfig file has been refreshed for the current busybox
version 1.27.x maintaining the same applets enabled.
Signed-off-by: Arturo Buzarra <arturo.buzarra@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>
Digi Embedded Yocto 2.4-r2.2
Manually changed recipes to use the master branches instead of the fixed SHA1
from the last release.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
qt3d sometimes fails to build due to an upstream issue that has yet to be
resolved. Since this interferes with our daily builds from time to time, remove
qt3d from our images completely.
https://jira.digi.com/browse/DEL-6348
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
SOM v1 is not going to be released, so there's no need for a revision check.
Now that hw flow control is available, use it along with the highest baudrate
possible.
This reverts commit e4fbba3dde.
https://jira.digi.com/browse/DEL-6254
Our current OpenSSL libraries are only functional when applications link
against v1.0.2d or higher, making some packages containing pre-compiled
applications that link to older versions (like AWS Greengrass) fail to build
and/or run properly.
This commit includes:
* Changing SHLIB_EXT from so.1.0.2 to so.1.0.0
* Reverting the version-script to an older version with backwards
compatibility plus newer symbols
Specifically, these changes partially revert the patches added in the poky
layer's commits a59bfd05d15085a3dc5669b47fd19867246c846b and
73a43fc15e0463c39baaadecab78fb3ef51b8cd0 respectively.
Please note that this only modifies the cryptographic library's ABI, its code
remains unchanged.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The PWM and ADC values are still to be determined, since their BSP support is
currently unavailable.
https://jira.digi.com/browse/DEL-6205
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Initialize Bluetooth chip in HCI_H4 mode and provide a firmware binary
with the IBS and DEEP_SLEEP mode disabled by default. Also this firmware
enables an internal clock required to maintain the system on low power modes.
https://jira.digi.com/browse/DEL-3711
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
The Digi vendor kernel uses a dedicated HCI UART driver with support for
In-Band Sleep (IBS). This driver, when used with a QCA vendor ROME plugin
for hciattach, is able to upload a new firmware version to the Bluetooth
chipset, as well as set the MAC address directly on the firmware.
Mainline BSP uses the HCI H4 driver instead and the "qualcomm" hciattach
plugin which is not able to upload firmware to the QCA6564 chipset.
As such, when using mainline the chipset uses the ROM firmware and the
bluetooth init script has been adapted accordingly.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The meta-freescale layer assumes that when you define the use-mainline-bsp
the platform is going to use the etnaviv gpu driver. This is not the case
for the CC6UL as the mxsfb.c driver is still not DRM capable.
Probably this will change in v4.19 as there is a DRM capable mxsfb.c
driver that will make it possible to use the armada xf86 driver with the
etnaviv fbdev emulation.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
* Check for file before using it
This just avoids the failure, on mainline access to OTP would need to be
done differently, see:
https://jira.digi.com/browse/ACL-163
* Use compatible node instead of digi,machine,name
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Currently the contents of FILESEXTRAPATHS and the actual paths being used for
the patch files are not aligned. That generates the following WARNINGs:
imx-gst1.0-plugin_4.3.4.bb: Unable to get checksum for imx-gst1.0-plugin SRC_URI entry 0001-gstimxv4l2-map-dev-video1-to-dev-fb0.patch: file could not be found
kernel-module-imx-gpu-viv_5.0.11.p8.6.bb: Unable to get checksum for kernel-module-imx-gpu-viv SRC_URI entry 0001-mxc-gpu-use-recommended-values-for-minimum-GPU-frequ.patch: file could not be found
kernel-module-imx-gpu-viv_5.0.11.p8.6+fslc.bb: Unable to get checksum for kernel-module-imx-gpu-viv SRC_URI entry 0001-mxc-gpu-use-recommended-values-for-minimum-GPU-frequ.patch: file could not be found
Also, those patches are not being applied.
This patch fixes FILESEXTRAPATHS to contain the actual paths being used.
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
(cherry picked from commit 4d35d15fee)
Currently the contents of FILESEXTRAPATHS and the actual paths being used for
the patch files are not aligned. That generates the following WARNINGs:
imx-gst1.0-plugin_4.3.4.bb: Unable to get checksum for imx-gst1.0-plugin SRC_URI entry 0001-gstimxv4l2-map-dev-video1-to-dev-fb0.patch: file could not be found
kernel-module-imx-gpu-viv_5.0.11.p8.6.bb: Unable to get checksum for kernel-module-imx-gpu-viv SRC_URI entry 0001-mxc-gpu-use-recommended-values-for-minimum-GPU-frequ.patch: file could not be found
kernel-module-imx-gpu-viv_5.0.11.p8.6+fslc.bb: Unable to get checksum for kernel-module-imx-gpu-viv SRC_URI entry 0001-mxc-gpu-use-recommended-values-for-minimum-GPU-frequ.patch: file could not be found
Also, those patches are not being applied.
This patch fixes FILESEXTRAPATHS to contain the actual paths being used.
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
On this platform, the SPI device gets registered as /dev/spidev32766.0.
https://jira.digi.com/browse/DEL-6183
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
During the merge of the maintainance branch and the manual revert of
some recipes, these were forgotten.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
On this platform, the SPI device gets registered as /dev/spidev32766.0.
https://jira.digi.com/browse/DEL-6183
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The generate_installer_zip() function had a hardcoded "u-boot" filename when adding
the bootloader to the list of files that are put in the installer .zip.
https://jira.digi.com/browse/DEL-6174
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Set a lower baudrate of 115200bps for bluetooth on SOMv1 since
hardware flow control is not available.
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
These packages create dependency issues when compiling framebuffer images, and
they aren't essential. Include them only in ccimx6 images.
This reverts commit 2edb127d28.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The sources for this package do not exist anymore, causing the build to fail
unless said sources can be obtained via a mirror.
https://jira.digi.com/browse/DEL-6147
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Currently, it isn't possible to wake up the ccimx8x after suspending to RAM.
For now, use the less strict "freeze" low power mode instead.
https://jira.digi.com/browse/DEL-6148
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The recipe's contents are unchanged, but the version number in the recipe name
will now match the rest of the vivante-related recipes.
https://jira.digi.com/browse/DEL-6115
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The package is now available for download on NXP's mirror, so we can fully sync
our recipe with the one in meta-fsl-bsp-release.
https://jira.digi.com/browse/DEL-6115
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Also remove our .bbappend, since it's not needed anymore after updating our
machine overrides.
https://jira.digi.com/browse/DEL-6115
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
These packages are required for videos to play properly on the ccimx8x. Also,
add gstreamer1.0-libav explicitly since the only package that depends on it
(gst-player-bin) was removed from packagegroup-core-x11-sato.
https://jira.digi.com/browse/DEL-6026
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Also add gtk3+ and clutter demos that depend on wayland since they are also
included in NXP's images.
https://jira.digi.com/browse/DEL-6104
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This is done in meta-fsl-bsp-release when building xwayland images, so port it
to our layer.
https://jira.digi.com/browse/DEL-6104
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This updates our Qt5 packagegroup with all of the packages included in NXP's
fsl-image-qt5-validation-imx.bb.
https://jira.digi.com/browse/DEL-6104
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This merges our Qt5 recipes with the ones in meta-fsl-bsp-release.
https://jira.digi.com/browse/DEL-6104
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
These recipes update Qt5, its plugins and adds wayland support.
https://jira.digi.com/browse/DEL-6104
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Some of these recipes might not be strictly necessary for xwayland to work, but
they are related, so I have added them just in case.
https://jira.digi.com/browse/DEL-6104
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
vpx was wrongly removed when updating the recipe to version 1.14, but it's
required to build x11 images for the ccimx6ulsbc.
https://jira.digi.com/browse/DEL-6078
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The newer version used for the ccimx8x has a different license, so its checksum
must be changed.
https://jira.digi.com/browse/DEL-6078
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This package depends on libg2d, and the latest version of this library's
sources for imx6 platforms are currently unavailable. Among other things, the
newer sources add a symbol needed by imx-gst1.0-plugin to compile, so this
patch manually adds the symbol as a macro in the package's source code.
https://jira.digi.com/browse/DEL-6078
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The aarch32 recipe will remain the same for now, since the newer sources aren't
yet available in NXP's mirrors.
https://jira.digi.com/browse/DEL-6078
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This is the version used by NXP in the rocko-4.9.88-2.2.0_8qxp_beta2 branch of
their meta-fsl-bsp-release layer.
https://jira.digi.com/browse/DEL-6078
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The most important change here is the package's revision.
https://jira.digi.com/browse/DEL-6078
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This is the version used by NXP in the rocko-4.9.88-2.2.0_8qxp_beta2 branch of
their meta-fsl-bsp-release layer.
https://jira.digi.com/browse/DEL-6078
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This is the version used by NXP in the rocko-4.9.88-2.2.0_8qxp_beta2 branch of
their meta-fsl-bsp-release layer.
https://jira.digi.com/browse/DEL-6078
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This is the version used by NXP in the rocko-4.9.88-2.2.0_8qxp_beta2 branch of
their meta-fsl-bsp-release layer.
https://jira.digi.com/browse/DEL-6078
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
We now have different tarballs for each CPU architecture we compile for. Also,
add support for the aarch64 tarball.
https://jira.digi.com/browse/DEL-6046
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The PWM and ADC values are still to be determined, since their SOM support is
currently unavailable.
https://jira.digi.com/browse/DEL-6049
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The Display Processing Unit (DPU) on the i.MX8 is what NXP used to call
Image Processing Unit (IPU) on the i.MX6 family.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
Commit 15139a3e97 wrongly removed 'vpx' from plugins-good which
is needed to play WebM files on the CC6UL.
The packagegroup-dey-gstreamer also needed to be updated to use
'pulseaudio' from plugins-good which was apparently renamed from 'pulse'.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6029
(cherry picked from commit 29add13409)
adc_sample:
- extend list of supported devices with MCA_CC8X
adc_cmp_sample:
- Add '-t' argument to specify the type of device.
- Added checking of threshold ranges to avoid confusion between
raw and voltage configurations.
https://jira.digi.com/browse/DEL-6001
Signed-off-by: Hector Bujanda <hector.bujanda@digi.com>
Commit 15139a3e97 wrongly removed 'vpx' from plugins-good which
is needed to play WebM files on the CC6UL.
The packagegroup-dey-gstreamer also needed to be updated to use
'pulseaudio' from plugins-good which was apparently renamed from 'pulse'.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6029
- 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 commit:
- moves the files in platform folders 'ccimx6qsbc' and 'ccimx6ul' to the
recipe's folder (they are the same).
- moves the install instructions for virtual wlan and wlan1 into functions
that can be reused by both platforms.
- moves the bridge example install instruction to the generic do_install()
since it's the same for all.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
Commit 15139a3e97 removed all gstreamer plugins recipes
but NXP meta-fsl-bsp-release still contains .bbappends that
this commit re-adds.
Besides, the imx-gst1.0-plugin recipe contained a patch by Digi
that was also wrongly removed and that this commit re-adds without
the version on the filename.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6029
meta-freescale rocko branch now sources gstreamer and its plugins
from repositories in codeaurora that contain all patches, so these
recipes are no longer required in meta-digi.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6029
(cherry picked from commit 105ab7a89b)
Commit 105ab7a89b removed all gstreamer plugins recipes
but NXP meta-fsl-bsp-release still contains .bbappends that
this commit re-adds.
Besides, the imx-gst1.0-plugin recipe contained a patch by Digi
that was also wrongly removed and that this commit re-adds without
the version on the filename.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6029
This is taken from meta-fsl-bsp-release layer at branch 'rocko-4.9.88-2.0.0_ga'
at SHA1 d65692ecb3a4.
A *.bbappend is required to explicitly set COMPATIBLE_MACHINE.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6029
- These have been taken from meta-fsl-bsp-release layer at branch
'rocko-4.9.88-2.0.0_ga', SHA1 d65692ecb3a4.
- Old recipes have been removed.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6029
meta-freescale rocko branch now sources gstreamer and its plugins
from repositories in codeaurora that contain all patches, so these
recipes are no longer required in meta-digi.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6029
- The variable containing the list of patches has been renamed to a more
generic prefix QCA65XX_.
- The ConnectCore 8X uses GPIO3_10 (394) for BT_EN.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-5936
This is taken from meta-fsl-bsp-release layer at bb80ba5a0104.
The file had a few commented lines for Wayland that have been uncommented
to leave them untouched in the commit.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-5937
The commit 32a6e809f811e8b3920326330d8225b3dd895f70 from the poky layer
breaks the build in the maintenance branch for rocko. This patch updates
the curl base recipe to use the latest version.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
The commit 32a6e809f811e8b3920326330d8225b3dd895f70 from the poky layer
breaks the build in the maintenance branch for rocko. This patch updates
the curl base recipe to use the latest version.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Manually changed recipes to use the master branches instead of the
fixed SHA1 from the last release.
Digi Embedded Yocto 2.4-r1.2
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
Firmware verification has a side effect in cc6ul sbc express platform
that affects to the bluetooth initialization.
https://jira.digi.com/browse/DEL-5802
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Whenever there's a big time jump due to an outaded RTC being updated via NTP,
detect the jump and update the DHCP lease's expiry times accordingly.
https://jira.digi.com/browse/DEL-5233
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
From python 2.x to python 3.x, the '/' operator changed from integer
division to float division.
Hence, when using one core, 'makejobs' was being evaluated to 0.5.
That caused the evaluation below (makejobs == 0) to return False (0),
therefore PARALLEL_MAKE was evaluated to '-j 0' and the compilation
failed because the 'j' parameter must be strictly postive.
Replace the operator by the integer div operator in python 3.x '//'.
https://jira.digi.com/browse/DEL-5769
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
With the migration from dey-2.2 to dey-2.4, now it is mandatory to include
all required applications for compilation. This fixes the next error:
| make: pkg-config: Command not found
| main.c:20:10: fatal error: cryptoauthlib.h: No such file or directory
| #include <cryptoauthlib.h>
https://jira.digi.com/browse/DEL-5710
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Rarely the bluetooth firmware is not loaded properly and causes
errors in the configuration steps. This verification makes sure
the firmware was loaded and is functional, if not we start the
retry mechanism with the default baudrate to avoid the firmware
corruption in the upload process.
https://jira.digi.com/browse/DEL-3711
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
With the switch to using Bash as command line interpreter, the default
/etc/inputrc configuration file for readline doesn't allow the use of
some keys which are common.
This commit enables them to not change the user experience with previous
DEY versions.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-5623
The suspend script has conflicts with the suspend from bash, then
we decided to rename our custom suspend script to standby and create
a symlink called suspend to maintain backward compatibility.
https://jira.digi.com/browse/DEL-5622
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>
Option --reference does not exist for busybox chmod/chown, so you get an ugly
error and file rights are modified.
https://jira.digi.com/browse/DEL-5642
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Sync defconfig to enable command 'chvt' because the xserver-nodm
init script requires this command in the stop process to swicth
the foreground virtual terminal after stopping the xserver.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Xserver prints many debug messages by the console output,
this bbappend modifies the init line to redirect the messages
to a log file.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Sync defconfig to enable command 'command' because /etc/profile
of base-files requires this command to be available. If it is not
available the following message is output during login on a image
using busybox.
-sh: command: not found
(From OE-Core rev: e41c90b852167bbcb434da57b84280e855acae33)
https://jira.digi.com/browse/DEL-5632
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Bash v4.4 or higher warns when discarding NULL bytes in command substitution
output. Remove these bytes to avoid the undesired warnings.
https://jira.digi.com/browse/DEL-5588
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Currently the default bluez5 package installed is bluez-5.46, but we need this
locally for compiling bluez-5.41 (the stack using in the bluetooth
certification process), so we need to locally apply the same fix ("fix python3
core dependency for testtools") for the testtools and its dependency with
python3-code instead of python3.
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Adding the bluetooth testtools does not have a big benefit and increases the
size of the rootfs in 16MB given its dependencies, which is critical in
devices (CC6UL) with a NAND flash.
https://jira.digi.com/browse/DEL-5613
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
There is not need to specify the testing flag for bluez5 compilation. That flag
is new starting at bluez5.44, and in the past it was called experimental. In
the past it made sense to pass that flag to compile specific services, but most
of them has been migrated to standard features, and experimental has been
renamed to testing, but we do not need any of those testing features.
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
In bluez5.41 we needed to specify the "--experimental" flag when starting the
bluetooth service in order to use some specific features (see d434043447).
In bluez5.46 (in fact starting in bluez5.44) code was reorganized and now that
compilation option is called "--testing" but does not exist as flag, because
some of the "experimental" features has been mode to standard features, so
there is not need of indicating any extra flag when starting the service.
https://jira.digi.com/browse/DEL-5624
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
This saves ~4MB of space and is not required for device detection.
https://jira.digi.com/browse/DEL-5613
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
This fixes the following warning:
WARNING: auto-serial-console-0.1-r0 do_populate_lic:
${COREBASE}/LICENSE is not a valid license file, please use
'${COMMON_LICENSE_DIR}/MIT' for a MIT License file in LIC_FILES_CHKSUM.
This will become an error in the future.
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
Rename recipe and fix the path of the progress binary. Also on the
rocko branch of meta-swupdate several signing mechanisms are
supported, and the value is used as a string to determine which one
to use.
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
In previous Yocto versions this recipe throws an warning about
the file dependencies however in Yocto 2.4 this throws a build error.
To avoid the build error we skip the QA check at file-level dependencies.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Some packages are not updated in meta-freescale/rocko, so we do
need to include some of these.
The patches for gstreamer in the original commit are skipped, as
poky/rocko uses a newer version.
This partially reverts commits:
* 52a10ff88d.
* b06c81b277https://jira.digi.com/browse/DEL-5518
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
There is a permissions conflict between qtbase and cmake installing
the environment-setup.d directory. This workaround creates the
directory in the do_install() step to avoid the conflict in the
do_generate_qt_environment_file() step.
https://jira.digi.com/browse/DEL-5583
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Introspection support is currently broken upstream. It is only
used to generate the documentation, so it is safe to remove it.
https://jira.digi.com/browse/DEL-5518
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
Solves:
/bin/bash: line 1: glib-mkenums: command not found
https://jira.digi.com/browse/DEL-5518
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
With Qt 5.8 the Qt Quick 2D renderer is merged into qtdeclarative as
the built-in software rendering backend for the Qt Quick SceneGraph.
https://jira.digi.com/browse/DEL-5518
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
Starting in alsa-lib 1.1.3, the package alsa-lib does not exist,
libasound is the real library package.
https://jira.digi.com/browse/DEL-5518
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
This is the stack covered by the Bluetooth certification. We will keep
it even though the newer bluez 5.46 will be used by default.
https://jira.digi.com/browse/DEL-5518
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
* 'experimental' has been renamed to 'testing' in Bluez 5.44
* Several patches (0004..0011) are now upstream and can be removed
* QCA specific patches have been refreshed
https://jira.digi.com/browse/DEL-5518
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
All these recipes and patches are now available and maintained in the
meta-freescale layer.
https://jira.digi.com/browse/DEL-5518
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
All this recipes only need to be renamed to the new version:
* cherokee
* curl
* imx-codec
* imx-gst1.0-plugin
* imx-parser
https://jira.digi.com/browse/DEL-5518
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
This new version of Qt already has a flag for optimizing for size,
so remove the patch and use this flag instead.
https://jira.digi.com/browse/DEL-5518
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
Pending to update the patch for dynamic environment location in NAND.
https://jira.digi.com/browse/DEL-5518
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
This tool was only needed for old kernels, newer kernels use the hardware
random number generator themselves.
https://jira.digi.com/browse/DEL-5518
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
This variable and all its references were removed in Yocto 2.4
https://jira.digi.com/browse/DEL-5518
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
This class no longer exists, it has been merged with images_types.
https://jira.digi.com/browse/DEL-5518
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
Manually changed recipes to use the master branches instead of the
fixed SHA1 from the last release.
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
NetworkManager was experiencing an unexpected behavior managing
the network interfaces on a supend/resume process, then to avoid
this undesired behavior the suspend script will stop and restart
the NetworkManager service.
https://jira.digi.com/browse/DEL-5351
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
NetworkManager will be restarted on the suspend script so this workaround is not needed
This reverts commit b3ae030fce.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
After exporting a GPIO or PWM, we need to give some time for udev rules
to complete, before actually trying to access the newly created entries
in the sysfs.
This solves a problem, where udev was setting the mode and group of
the newly created files, so they are accessible for users (not root)
belonging to that group.
For traceability and to be sure the patch applies without conflicts,
this commit also sets a fixed revision to use from the libsoc
repository.
https://jira.digi.com/browse/DEL-5389
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
With these changes we tell NM to not manage the wireless interfaces before
unloading the wireless module. This was causing some unexpected behavior that
crashed NetworkManager.
Signed-off-by: Sebastian Pastor <sebastian.pastor@digi.com>
https://jira.digi.com/browse/DEL-5351https://jira.digi.com/browse/DEL-4571
These udev rules allow to use the digiapix API by a normal user that
belongs to the 'digiapix' group.
https://jira.digi.com/browse/DEL-5232
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The recipe modifies the Greengrass Core init script to properly configure the
daemon relative path. This daemon location is different depending on the
Greengrass version being used.
This commits also moves the patch for Greengrass Core 1.0.0 to the
'greengrass-1.0.0' directory in preparation for adding Greengrass Core 1.1.0
recipe in the next commit.
https://jira.digi.com/browse/DEL-5368
Signed-off-by: Tatiana Leon <tatiana.leon@digi.com>
This commit updates dnsmasq to version 2.78 to include the following
vulnerability patches:
* CVE-2017-13704
* CVE-2017-14491
* CVE-2017-14492
* CVE-2017-14493
* CVE-2017-14494
* CVE-2017-14495
* CVE-2017-14496
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-5136
The current recipe copies binaries for different ARM architectures to
the rootfs.
For the CC6UL we need to save some space, so delete the versions of the
binaries that are not being used.
https://jira.digi.com/browse/DEL-4987
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The current recipe copies binaries for different ARM architectures to
the rootfs.
For the CC6UL we need to save some space, so delete the versions of the
binaries that are not being used.
https://jira.digi.com/browse/DEL-4987
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This allows to specify a different set of gstreamer packages to be
installed per machine. It's mainly used for the CC6UL to define a
minimum set of packages that allows to play a WEBM video, and at the
same time save some space as this platform does not have much storage.
The space saved with this change for the CC6UL and the default QT image
is about ~5MB.
https://jira.digi.com/browse/DEL-4987
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
virtwlans script creates an additional interface on startup for QCA6564 chip.
The created interface purpose is for ap mode, so specify its type on creation.
https://jira.digi.com/browse/DEL-5290
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
This creates a new dispatcher action DEVICE_CONNECTIVITY_CHANGE, that
gets triggered whenever one interface fails in the upstream connectivity
check, regardless of the system having connectivity through a different
interface.
https://jira.digi.com/browse/DEL-5210
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Subset of commits to fix the pairing for dual mode devices. Main
commit that fixes is 2d3685252a21cda4b918ad1cc4dd0572bd5c6d3c, but some
previous commits are required as well.
"""
For dual mode devices we need to pass address type used in pairing
events to reply with correct one on agent reply. Otherwise reply for
BR/EDR pairing of dual mode device would use address type (which is
valid only for LE address) resulting in reply being ignored by kernel
and eventually pairing timeout.
"""
https://jira.digi.com/browse/DEL-5226
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
For avoid compilation error due to platform specific patches, first apply
the common patches and later apply platform specific patches.
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Create a multiple patch file with the original qualcomm code that adds
support for the qca6564 chip (hcitattach_rome)
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
This commit re-adds the imx-gpu-g2d recipe that was removed
from the imx-gpu-viv v6 driver.
https://jira.digi.com/browse/DEL-5234
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This commit adds a platform dependency to remove the parts
provided by the new GPU driver and maintain the compatibility
for other platforms using previous versions.
https://jira.digi.com/browse/DEL-5234
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This commit adds the recipe to update the GPU driver
to the latest version.
https://jira.digi.com/browse/DEL-5234
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
The XBee Cellular modem is expected to be at ttymxc1 on CC6UL and
at ttymxc4 on CC6. The changes are needed because in v4.9.11 kernel
the /sys/devices entry for CC6UL and CC6 are the same for the TTYs,
causing that on CC6UL ModemManager was also searching for modems on
ttymxc4.
Signed-off-by: Sebastian Pastor <sebastian.pastor@digi.com>
https://jira.digi.com/browse/DEL-5163
This commit modifies different recipes to support the new platform
ccimx6qpsbc and adapt it to maintain the support to ccimx6sbc.
https://jira.digi.com/browse/DEL-5082
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This commit modifies sysinfo tool to use the kernel symlinks for
the devices instead of using the full node path and maintain
compatibility with different kernel versions.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
The experimental flag is needed to run the GATT server application.
https://jira.digi.com/browse/DEL-5023
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
These examples show how to use the Digi APIX.
https://jira.digi.com/browse/DEL-5097
Signed-off-by: Francisco Gil Martinez <francisco.gilmartinez@digi.com>
This commit adds the some platform board files and removes
the symbolic link to libsoc.conf
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-5096
This commit enables the IPV6 support that is necessary for the
XBee Cellular LTE Cat1 modem.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-4839
(cherry picked from commit a5cfaa921d)
wlan1 is the interface used for SoftAP, so use that one instead. This also
matches with the 'Network bridging' chapter of the documentation.
https://jira.digi.com/browse/DEL-4823
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
(cherry picked from commit e6beba4cb0)
The bridge example uses the wireless interface and it assumes that it is
initialized, so it must be placed after it.
https://jira.digi.com/browse/DEL-4823
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
(cherry picked from commit d7c8fa4b9a)
This only affects the CC6UL, where by default now 'qtsmarthome' is
installed instead of 'qtbase-examples'.
This serves two purposes:
* Remove the 'qtbase-examples' package from the CC6UL to save space.
* Use 'qtsmarthome' as a demo of a QML application running on the CC6UL
using Qt Quick 2D Renderer.
https://jira.digi.com/browse/DEL-3912
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit 4c5a7fd3f8)
Instead of having a recipe to add launchers for a bunch of applications
(most of them are not available anymore) move the qtsmarthome launcher
to the recipe that installs the package.
https://jira.digi.com/browse/DEL-3912
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit 64010754d0)
The demo application uses 'svg' images, so at runtime it depends on
'qtsvg-plugins' package.
Also add a patch to fix a runtime warning:
Both point size and pixel size set. Using pixel size
https://jira.digi.com/browse/DEL-3912
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit 48ff14dc78)
This is an alternative software based renderer for QtQuick2
applications for hardware that doesn't have a GPU.
This is the case of the CC6UL. It does not have a GPU, so the only way
to run QML applications is using this software renderer.
https://jira.digi.com/browse/DEL-3912
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit e623c365ff)
The supplicant support for a bridge was not being managed,
then the bridge was failing when the softap was configured
with an encryption. With this change we launch a supplicant
instance with the bridge support after checking that the
/etc/network/interfaces contains the required parameters.
https://jira.digi.com/browse/DEL-4454
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
(cherry picked from commit 9c5774ed62)
In the past QT package did include some fonts, but not anymore. New
versions of QT do rely on an external font package being installed in
the rootfs.
Without fonts the QT applications just show up in the screen but
obviously with no text at all.
https://jira.digi.com/browse/DEL-4724
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit 02547c6530)
This patch makes smaller libQt libraries saving some space in the CC6UL
rootfs.
Libraries size before the patch:
root@ccimx6ulsbc:~# ls -l /usr/lib/libQt*5.7.1
22448 Aug /usr/lib/libQt5Concurrent.so.5.7.1
5347036 Aug /usr/lib/libQt5Core.so.5.7.1
508464 Aug /usr/lib/libQt5DBus.so.5.7.1
4419712 Aug /usr/lib/libQt5Gui.so.5.7.1
1367776 Aug /usr/lib/libQt5Network.so.5.7.1
275900 Aug /usr/lib/libQt5OpenGL.so.5.7.1
341688 Aug /usr/lib/libQt5PrintSupport.so.5.7.1
88628 Aug /usr/lib/libQt5SerialPort.so.5.7.1
290960 Aug /usr/lib/libQt5Sql.so.5.7.1
212432 Aug /usr/lib/libQt5Test.so.5.7.1
5306588 Aug /usr/lib/libQt5Widgets.so.5.7.1
894928 Aug /usr/lib/libQt5XcbQpa.so.5.7.1
191404 Aug /usr/lib/libQt5Xml.so.5.7.1
Libraries size after the patch:
root@ccimx6ulsbc:~# ls -l /usr/lib/libQt*5.7.1
18352 Aug /usr/lib/libQt5Concurrent.so.5.7.1
4032380 Aug /usr/lib/libQt5Core.so.5.7.1
303684 Aug /usr/lib/libQt5DBus.so.5.7.1
2867436 Aug /usr/lib/libQt5Gui.so.5.7.1
839428 Aug /usr/lib/libQt5Network.so.5.7.1
239044 Aug /usr/lib/libQt5OpenGL.so.5.7.1
267976 Aug /usr/lib/libQt5PrintSupport.so.5.7.1
59960 Aug /usr/lib/libQt5SerialPort.so.5.7.1
172192 Aug /usr/lib/libQt5Sql.so.5.7.1
171500 Aug /usr/lib/libQt5Test.so.5.7.1
4282740 Aug /usr/lib/libQt5Widgets.so.5.7.1
616420 Aug /usr/lib/libQt5XcbQpa.so.5.7.1
154556 Aug /usr/lib/libQt5Xml.so.5.7.1
https://jira.digi.com/browse/DEL-4644
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit c62d5e1e42)
This commit enables the IPV6 support that is necessary for the
XBee Cellular LTE Cat1 modem.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-4839
This commit creates a new file called 'dey-version-${REAL_MULTIMACH_TARGET_SYS}'
(for example, 'dey-version-cortexa7hf-neon-dey-linux-gnueabi') at the same level
as 'version-${REAL_MULTIMACH_TARGET_SYS}',
'site-config-${REAL_MULTIMACH_TARGET_SYS}', and
'environment-setup-${REAL_MULTIMACH_TARGET_SYS}' files.
The file contains the following parameters:
* Machine. The name of the platform the toolchain was built for (ccimx6sbc,
ccimx6ulsbc, ccimx6ulstarter).
* Version: A versioning system for the generated toolchains. Currently is the
distro version followed by the timestamp on which the current build started.
* Image: The name of the image that triggered the population of the SDK
(core-image-base, dey-image-aws, dey-image-qt-${GRAPHICAL_BACKEND})
The purpose of the 'dey-version-*' file is to be parsed by Eclipse so toolchains
can be autodetected.
This file is packaged with the rest of SDK/toolchain resources ('version-*',
'site-config-*', and 'environment-setup-*' files, and 'sysroots' directory)
when creating the SDK tarball and later the installation script.
The 'dey-version-*' file could also be created in a 'meta-environment.bbappend'
appending to the 'create_sdk_files()'. But from this recipe there is no access
to the name of the image that triggers the creation of the SDK (core-image-base,
dey-image-aws, dey-image-qt, etc.).
Currently, we are redefining 'SDK_POSTPROCESS_COMMAND' (from
'poky/meta/classes/populate_sdk_base.bbclass') to insert the generation of the
'dey-version-*' file just before creating the SDK tarball.
https://jira.digi.com/browse/DEL-5074
Signed-off-by: Tatiana Leon <tatiana.leon@digi.com>
NM launches 'dnsmasq' using DBus, so enable DBus support at compile
time. Also remove the symlinks in the different runlevels, so it's not
launched by the included bootscript.
https://jira.digi.com/browse/DEL-4787
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This is needed in the context of network failover, so when one physical
interface is lost, you can still resolve the connectivity-check URL
using the local DNS cache.
https://jira.digi.com/browse/DEL-4787
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The implemented patch fails when NetworkManager uses a local DNS cache
underneath (like 'dnsmasq'). To access the local DNS cache it needs to
use the loopback interface and hardcoding the physical interfaces make
the connectivity check fail.
This reverts commit c9b02d6288.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Use the same interface that it's being checked for the DNS resolution.
This makes connectivity check work in an scenario where the primary
interface has lost connectivity (for example ethernet) but you still
have connectivity through a secondary interface (e.g. wireless).
What happens in that case is that even though you have correct
connectivity in the secondary interface the check fails because it does
not use that secondary interface to resolve the name of the test URL.
The result is that the connectivity check assumes that this secondary
interface is also failing and it penalizes the metrics in the routing
table.
This commit uses libcurl's CURLOPT_DNS_INTERFACE to set the DNS
interface. Notice that this requires 'libcurl' to be compiled with
'--enable-ares'.
https://jira.digi.com/browse/DEL-4787
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This is required to use '--dns-interface' runtime parameter to instruct
'curl' to use a specific interface for DNS resolution.
We need this in the context of the network failover support, where
NetworkManager does the connectivity check, by trying to connect to a
configured URL through the different interfaces available, and for this
check it uses 'libcurl' underneath.
If you try to use this functionality without this build time option
enabled, you get:
curl: (4) A requested feature, protocol or option was not found built-in
in this libcurl due to a build-time decision.
https://jira.digi.com/browse/DEL-4787
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This library will provide a common API to access Digi hardware interfaces and/or
other features.
https://jira.digi.com/browse/DEL-4979
Signed-off-by: Tatiana Leon <tatiana.leon@digi.com>
If two or more targets are in the same environment, all of them will
broadcast the same SSID, which may be a problem when a client wants
to connect to a specific device.
Use the last bytes of the non-virtual wireless MAC for the name of the
SSID, a random value with no hexadecimal characters is used if the MAC
is not available.
Also drop 'wpa2aes' from the SSID.
https://jira.digi.com/browse/DEL-4129
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
Turns out that the busybox' fdisk applet is also able to parse the GPT
partition tables. This saves around 0.5 MiB of space.
https://jira.digi.com/browse/DEL-4565
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
wlan1 is the interface used for SoftAP, so use that one instead. This also
matches with the 'Network bridging' chapter of the documentation.
https://jira.digi.com/browse/DEL-4823
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
The bridge example uses the wireless interface and it assumes that it is
initialized, so it must be placed after it.
https://jira.digi.com/browse/DEL-4823
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
This only affects the CC6UL, where by default now 'qtsmarthome' is
installed instead of 'qtbase-examples'.
This serves two purposes:
* Remove the 'qtbase-examples' package from the CC6UL to save space.
* Use 'qtsmarthome' as a demo of a QML application running on the CC6UL
using Qt Quick 2D Renderer.
https://jira.digi.com/browse/DEL-3912
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Instead of having a recipe to add launchers for a bunch of applications
(most of them are not available anymore) move the qtsmarthome launcher
to the recipe that installs the package.
https://jira.digi.com/browse/DEL-3912
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The demo application uses 'svg' images, so at runtime it depends on
'qtsvg-plugins' package.
Also add a patch to fix a runtime warning:
Both point size and pixel size set. Using pixel size
https://jira.digi.com/browse/DEL-3912
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This is an alternative software based renderer for QtQuick2
applications for hardware that doesn't have a GPU.
This is the case of the CC6UL. It does not have a GPU, so the only way
to run QML applications is using this software renderer.
https://jira.digi.com/browse/DEL-3912
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The supplicant support for a bridge was not being managed,
then the bridge was failing when the softap was configured
with an encryption. With this change we launch a supplicant
instance with the bridge support after checking that the
/etc/network/interfaces contains the required parameters.
https://jira.digi.com/browse/DEL-4454
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
In the past QT package did include some fonts, but not anymore. New
versions of QT do rely on an external font package being installed in
the rootfs.
Without fonts the QT applications just show up in the screen but
obviously with no text at all.
https://jira.digi.com/browse/DEL-4724
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This patch makes smaller libQt libraries saving some space in the CC6UL
rootfs.
Libraries size before the patch:
root@ccimx6ulsbc:~# ls -l /usr/lib/libQt*5.7.1
22448 Aug /usr/lib/libQt5Concurrent.so.5.7.1
5347036 Aug /usr/lib/libQt5Core.so.5.7.1
508464 Aug /usr/lib/libQt5DBus.so.5.7.1
4419712 Aug /usr/lib/libQt5Gui.so.5.7.1
1367776 Aug /usr/lib/libQt5Network.so.5.7.1
275900 Aug /usr/lib/libQt5OpenGL.so.5.7.1
341688 Aug /usr/lib/libQt5PrintSupport.so.5.7.1
88628 Aug /usr/lib/libQt5SerialPort.so.5.7.1
290960 Aug /usr/lib/libQt5Sql.so.5.7.1
212432 Aug /usr/lib/libQt5Test.so.5.7.1
5306588 Aug /usr/lib/libQt5Widgets.so.5.7.1
894928 Aug /usr/lib/libQt5XcbQpa.so.5.7.1
191404 Aug /usr/lib/libQt5Xml.so.5.7.1
Libraries size after the patch:
root@ccimx6ulsbc:~# ls -l /usr/lib/libQt*5.7.1
18352 Aug /usr/lib/libQt5Concurrent.so.5.7.1
4032380 Aug /usr/lib/libQt5Core.so.5.7.1
303684 Aug /usr/lib/libQt5DBus.so.5.7.1
2867436 Aug /usr/lib/libQt5Gui.so.5.7.1
839428 Aug /usr/lib/libQt5Network.so.5.7.1
239044 Aug /usr/lib/libQt5OpenGL.so.5.7.1
267976 Aug /usr/lib/libQt5PrintSupport.so.5.7.1
59960 Aug /usr/lib/libQt5SerialPort.so.5.7.1
172192 Aug /usr/lib/libQt5Sql.so.5.7.1
171500 Aug /usr/lib/libQt5Test.so.5.7.1
4282740 Aug /usr/lib/libQt5Widgets.so.5.7.1
616420 Aug /usr/lib/libQt5XcbQpa.so.5.7.1
154556 Aug /usr/lib/libQt5Xml.so.5.7.1
https://jira.digi.com/browse/DEL-4644
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Tweaked to maintain some recipes' revisions to AUTOREV instead of the
fixed SHA1s from the tag.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
We need to pass different log levels depending on the message, so they
appear in the console, so generalize the 'log' function.
https://jira.digi.com/browse/DEL-4682
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Busybox's init enabled at build time collide with 'sysvinit' package.
This does not seem a problem when using RPM package manager, but using
IPK instead, the build is broken at image creation time:
Collected errors:
* check_data_file_clashes: Package sysvinit wants to install file <...>/rcS
But that file is already provided by package * busybox
https://jira.digi.com/browse/DEL-4573
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
No applet has been enabled or disabled, just the defconfig file has been
refreshed for the current busybox version 1.24.x
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
NetworkManager manages the 'resolv.conf' file globally, so there is no
need for pppd specific scripts for DNS.
These scripts race with NM to set DNS, leading sometimes to a scenario
where you have ethernet as the default gateway, but with DNS only
reachable via cellular.
While on it, also remove not used 'mm_cellular' configuration file.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Some modems (e.g. the XBee Cellular LTE Cat 1) have a long initilization
process and are not available when ModemManager tries to detect them
on boot.
For those modems schedule a rescan a bit later after NetworkManager has
been launched, so they are detected properly.
https://jira.digi.com/browse/DEL-4661
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
These values configure the PPP daemon to check that the connection is
still alive (using an echo) and kill itself otherwise. On that event,
NetworkManager takes over and tries to restore the connection.
This is specially useful for modems with only one serial port, because
they are not able to signal the connectivity loss to the host (the only
data channel is used for the network data itself).
https://jira.digi.com/browse/DEL-4653https://jira.digi.com/browse/DEL-4650
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
Use the 1.8.x stable series, as it has some desired functionality (e.g.
connectivity check) and bug fixes over the default version included in
Yocto.
https://jira.digi.com/browse/DEL-4628
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The name of the repository in Github is fixed, because it is a fork from
the original repository.
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
This commit includes the Python3-Json package that is required now
by QT creator python scripts when debugging an application with GDB
on the target.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
For P2P interfaces, some drivers (CC6UL) create auxiliar interfaces based
on the parent one, like p2p-p2p0-0.
This commit adds a p2p* pattern to the list of unmanaged devices so that
NetworkManager doesn't try to manage P2P devices.
https://jira.digi.com/browse/DEL-4649
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
The removed distro features are mostly corner cases, not widely used,
and sometimes conflict with other packages serving the same purposes.
For example:
* '3g' only adds ofono for cellular support, while we are
using ModemManager.
* 'nfc' adds 'neard' the NFC daemon (which at the moment we don't
support)
* 'zeroconf' adds 'avahi' package, but we are using NetworkManager
instead to manage the network interfaces.
* 'nfs' adds 'rpcbind' server, which is not needed at all to have
an NFS mounted rootfs.
Needless to say that all those packages can be added to any image
without having the distro features enabled, or if preferred, you can add
the distro features back in the project's local.conf.
https://jira.digi.com/browse/DEL-3780
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
As we are using kernel's DEVTMPFS, using udev-cache on top of it does
not add much advantage. Disabling it has the extra advantage of avoiding
writing the udev-cache tarball under '/etc' (which probably won't work
on a read-only system).
https://jira.digi.com/browse/DEL-3780
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
When bringing down the wireless interface used for hostapd, the messages
overlap:
# ifdown wlan1
Stopping HOSTAP Daemon: stopped /usr/sbin/hostapd (pid 569)
hostapd.
Adding the 'quiet' option to start-stop-daemon command fixes the
cosmetic issue.
# ifdown wlan1
Stopping HOSTAP Daemon: hostapd.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
"glibc-gconv" packages are GLIBC library specific, so add the proper
override to fix the build of the package using other C libraries (e.g.
MUSL).
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
If the IOExpander is not programmed but the kernel is running its driver,
the following messages will appear when running sysinfo:
cat: can't open '/sys/devices/platform/soc/2100000.aips-bus/21a0000.i2c/i2c-0/0-006e/hw_version': No such file or directory
cat: can't open '/sys/devices/platform/soc/2100000.aips-bus/21a0000.i2c/i2c-0/0-006e/fw_version': No such file or directory
Signed-off-by: Diaz de Grenu, Jose <Jose.DiazdeGrenu@digi.com>
Now the suspend script brings down all the wireless interfaces that are
managed by ifupdown command (in the '/etc/network/interfaces' file) and
then unloads the wireless driver.
On resume the script triggers an event so udev reloads the wireless
driver and then brings up the interfaces that were brought down on
suspend.
https://jira.digi.com/browse/DEL-4288
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The cellular interface is now managed by NetworkManager, so there is no
need for this custom script.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This commit removes the interfaces that are managed by Networkmanager
from the /etc/network/interfaces entry.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
So the package can be compiled in a non-X11 graphical system.
https://jira.digi.com/browse/DEL-4289
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
* Disabled: dnsmasq and netconfig
* Enabled: cellular related options and connectivity check
https://jira.digi.com/browse/DEL-4289
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
If values are provided in the local.conf, the package will have the
'config.json' file preconfigured.
https://jira.digi.com/browse/DEL-4274
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Rename the class so it's not specific to the C version of the AWS IoT
Device SDK, and can be used for anything related with AWS IOT (for
example Greengrass).
https://jira.digi.com/browse/DEL-4274
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This avoids the following errors:
ERROR: dey-examples-opengles-1.0-r0 do_package_qa: QA Issue: No GNU_HASH in the elf binary
and when cleaning:
ERROR: dey-examples-opengles-1.0-r0 do_configure: oe_runmake failed
| make: *** No rule to make target 'clean'. Stop.
Signed-off-by: Diaz de Grenu, Jose <Jose.DiazdeGrenu@digi.com>
This recipe allows to generate the swu update package to be used with SWUpdate.
The package can be generated using:
bitbake dey-image-aws-swu
https://jira.digi.com/browse/DEL-4304
Signed-off-by: Tatiana Leon <tatiana.leon@digi.com>
In the recovery images we are using a custom init so we are not executing
any post-installation that is required for a correct rootfs setup, so call
all the post installation scripts from our custom init.
The package installation could be ipk, rpm or deb, so call to the
*postint folder.
Given that the recovery rootfs is a ramdisk, there is no need to remove the
post installation scripts.
https://jira.digi.com/browse/DEL-4430
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
The fix in 0ae172613a wrongly printed
a new line after each value, wich resulted in the following output for a
command like this, that reads two 32-bit words:
root@ccimx6ulsbc:~# memwatch -r -l 8 -w -a 0x2008008
0x02008008: 0x0070e501
0x00000100
Instead, it should print a line feed after every 16 bytes.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
This commit updates the spidev_test application from Linux kernel upstream
at /tools/spi/spidev_test.c adding support to new features
commit: 9006a7b3220e7293ef8bc1ac9bba6c54411051c1
https://jira.digi.com/browse/DEL-4358
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
* Create the certificates directory before copying files into it.
* Give the downloaded tarball a meaningful name (otherwise tarballs
downloaded from GitHub don't have a proper name (only the version) and
may collide with other packages with the same version.
* Allow to create certs package if certs are available at build time.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
If the event is already signaled, read the timestamp, log and ack the event,
perform actions and exit. If it is already acknowledged, then do nothing.
Signed-off-by: Sebastian Pastor <sebastian.pastor@digi.com>
Only copy the certificates to the image if they are provided and exists.
https://jira.digi.com/browse/DEL-4339
Signed-off-by: Tatiana Leon <tatiana.leon@digi.com>
This commit moves awsiotsdk-c recipe into 'recipes-aws' and awsiotsdk-demo into
'recipes-digi/dey-examples'.
https://jira.digi.com/browse/DEL-4339
Signed-off-by: Tatiana Leon <tatiana.leon@digi.com>
This argument now is only valid for the behavior of the comparator in
sleep mode, so it no longer makes sense in this application.
Signed-off-by: Sebastian Pastor <sebastian.pastor@digi.com>
GG daemon may die due to misconfigurations, but this takes a bit of
time, so wait a bit to check whether the daemon is still alive.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
That's the default assumed by the GG daemon:
$ daemon --help
-gg-home string
home directory of greengrass (default "/greengrass")
As of this version GG daemon may not work properly otherwise.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This library adds support to use the Atmel CryptoAuth device available
in the ConnectCore 6UL.
https://jira.digi.com/browse/DEL-4284
Signed-off-by: Diaz de Grenu, Jose <Jose.DiazdeGrenu@digi.com>
The readlink command on a real file was expanding to nothing and then
the '/etc/resolv.conf' file was not being updated with the nameservers.
With this change we only run the 'readlink' link command after checking
that the file is actually a symbolic link.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
When not enough arguments are given (this includes using only the '-h'
argument for help), show the complete help.
Signed-off-by: Diaz de Grenu, Jose <Jose.DiazdeGrenu@digi.com>
Avoid splitting the boot script message in two different lines:
Starting bluetooth hardware: [OK]
done.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The new line should be printed after the result, instead of before.
Example:
root@ccimx6sbc:~# memwatch -r -w -a 0x2190034
0x02190034: 0x00000000 root@ccimx6sbc:~#
After this patch:
root@ccimx6sbc:~# memwatch -r -w -a 0x2190034
0x02190034: 0x00000000
Signed-off-by: Diaz de Grenu, Jose <Jose.DiazdeGrenu@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
After 0e7f5d3a47 both platforms probe both ports,
which is problematic (for example, ttymxc4 is the console in the 6UL based
platforms).
Use more concrete rules to avoid that problem.
https://jira.digi.com/browse/DEL-4199
Signed-off-by: Diaz de Grenu, Jose <Jose.DiazdeGrenu@digi.com>off-by: Diaz de Grenu, Jose <Jose.DiazdeGrenu@digi.com>
After the kernel update (v3.14 to v4.1) the sysfs path changed from:
/devices/soc0/soc.0/2100000.aips-bus/21f4000.serial/tty/ttymxc4
to:
/devices/soc0/soc/2100000.aips-bus/21f4000.serial/tty/ttymxc4
which caused the XBee Cellular not to be detected on the new kernel. These more
general rules are compatible with both kernels.
https://jira.digi.com/browse/DEL-4199
Signed-off-by: Diaz de Grenu, Jose <Jose.DiazdeGrenu@digi.com>
This patch modifies the code of some of the provided samples to be able to run
them in our platforms. By default, these applications cannot find the
certificates in the device, and the command line options are not working.
Patched samples:
* shadow_sample
* shadow_sample_console_echo
* subscribe_publish_sample
See https://github.com/aws/aws-iot-device-sdk-embedded-C.
https://jira.digi.com/browse/DEL-4101
Signed-off-by: Tatiana Leon <tatiana.leon@digi.com>
Variable 'AWS_IOT_LOGGING_LEVEL' can be used from the project 'local.conf' to
establish the logging level of the AWS IoT Device SDK.
There are 6 incremental levels: none, error, warn, info, debug, and trace.
Default is 'debug'.
https://jira.digi.com/browse/DEL-4101
Signed-off-by: Tatiana Leon <tatiana.leon@digi.com>
The AWS IoT device SDK for embedded C is a collection of C source files that
can be used in embedded applications to securely connect to the AWS IoT
platform.
The SDK code is available in GitHub and includes the library code and several
sample applications.
A user must provide from its 'local.conf':
* AWS_IOT_CERTS_DIR: Absolute path to the directories where the required
certifies are stored:
* Root CA.
* Device signed certificate.
* Device private key.
And optionally, values for the rest of variables defined in the 'awsiotsdk-c'
bbclass.
This recipe is building the library code and the binaries for the samples:
* shadow_sample
* shadow_sample_console_echo
* subscribe_publish_sample
See https://github.com/aws/aws-iot-device-sdk-embedded-C.
https://jira.digi.com/browse/DEL-4101
Signed-off-by: Tatiana Leon <tatiana.leon@digi.com>
mbedTLS is an open source, portable, easy to use, readable and flexible SSL
library.
https://jira.digi.com/browse/DEL-4101
Signed-off-by: Tatiana Leon <tatiana.leon@digi.com>
QMI modems didn't work with the version of
modemmanager that the dey-2.2-r1 release was
using.
We were using two patches for uBlox plugin to use XBee Cellular 3G
that are now merged in modemmanager master.
This updates modemmanager to use the commit where QMI
problem was fixed and also include uBlox patches.
https://jira.digi.com/browse/DEL-4192
Signed-off-by: Salvador Penalva <salvador.penalva@digi.com>
Add patch to MM, so it detects the U-Blox modem connected to the XBee
socket.
https://jira.digi.com/browse/DEL-4084
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Tweaked to maintain some recipes' revisions to AUTOREV instead of the
fixed SHA1s from the tag.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The XBee Cellular needs more time to settle down before MM is able to
detect it on boot. As this is connected to one of the 'ttymxc' serial
ports, use that port to conditionally delay the launch of MM.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Adding more retries to the port AT probing has an impact in modems not
using serial drivers (for example using qmi, mbim). It takes longer for
MM to detect those modems and then user space gives up waiting for the
modems to be available.
This reverts commit 682d77e414.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Pulseaudio 9.0 relies on the syscall memfd_create, which was introduced
in kernel 3.17, but the version currently supported for the CC6 SBC is
3.14.
There is a corner case where the configure script does not detect the
actual kernel version, thus enabling memfd_create. When Pulseadio tries
to call memfd_create, it shows error messages, so disable memfd
explicitly.
https://jira.digi.com/browse/DEL-3923
Signed-off-by: Alejandro Navarro <alejandro.navarro@digi.com>
Added a post-installation script to disable the wireless interfaces on
module variants without wireless support.
This fixes following messages on boot:
wlan: driver load failure
modprobe: can't load module wlan (extra/wlan.ko): No such device
...
https://jira.digi.com/browse/DEL-3781
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The following changes have been made to the bluetooth-init script:
* Remove "hciconfig hci0 up/down" and this is now deprecated and likely
to fail. We use the AutoEnable feature of bluetoothd for this now.
* Move setting the MAC address to hciattach instead of using hcitool.
* Remove resets performed by hcitool and hciconfig. The hciattach
application already performs a reset and that should suffice.
* Remove hciattach retries.
https://jira.digi.com/browse/DEL-3711https://jira.digi.com/browse/DEL-3436https://jira.digi.com/browse/DEL-3636https://jira.digi.com/browse/DEL-3955
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This commits adds patches to hciattach for the following:
* Strict flow control setting
The hciattach application has a flow | noflow command line argument that is
currently only applied on the first configuration of the uart port. The
hciattach_rome plugin ignores this setting and assumes hardware flow
control is always supported. This commits makes hciattach obey the user flow
control indication.
* Modify hciattach_rome to set MAC address. The MAC address setting
feature in the rome plugin now works with the command line specified
MAC.
* Reduce verbosity. hciattach now accepts a "-v" verbose flag. By
default verbose output it omitted.
https://jira.digi.com/browse/DEL-3711https://jira.digi.com/browse/DEL-3436https://jira.digi.com/browse/DEL-3636https://jira.digi.com/browse/DEL-3955
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This 'sed' command was used in the past, when DHCP or MANUAL was
configured in the '/etc/network/interfaces' (for cellular). This is no
longer true as we always configure the interface with a custom (manual)
script.
This was breaking the rest of interfaces when configured to use 'dhcp':
iface eth0 inet manual
umanualc_opts -S -b >/dev/null &
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Launching the MM on target's boot fails to detect the XBee cellular
because this needs more time to complete the initialization. So add some
more retries for the AT port probing to allow the XBee cellular to be
detected.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Instead of redirecting the MM logging to '/dev/null' use a file, so we
can see what's going on in case of failure.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The flow control patches have been merged to the master branch, so
update the revision to remove those patches from our layer.
This reverts commit a7c51af5b8.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Sysinfo was showing error messages if the working directory contains any file
with .log extension.
Signed-off-by: Diaz de Grenu, Jose <Jose.DiazdeGrenu@digi.com>
The recovery init checks if the configured update package exists and it is valid
before setting a new key and/or formatting the rootfs partition.
This change avoids getting non-booting devices after performing a firmware
update with a non-existing or invalid update package.
https://jira.digi.com/browse/DEL-3959
Signed-off-by: Tatiana Leon <tatiana.leon@digi.com>
We have introduced new default configuration files for wireless that do
not show on sysinfo, so add them if they exist.
https://jira.digi.com/browse/DEL-3974
Signed-off-by: Alejandro Navarro <alejandro.navarro@digi.com>
The XBee cellular support is at the moment only in modemmanager's git
repository (master branch).
Also remove one Telit patch from the bbappend because it's already
included in the git repo.
https://jira.digi.com/browse/DEL-3841
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This version of libqmi is needed for newer versions of ModemManager.
Remove bbappend and patch to previous version as the patch is now
included in the new version.
https://jira.digi.com/browse/DEL-3841
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The current script cannot launch the hostapd twice (for dual HostAP mode)
because start-stop-daemon finds an already existing PID for hostapd after
running the first instance.
The solution is:
- Do not launch the hostapd in background (so that it does not fork the
process, which assigns a different PID)
- Use -b option of start-stop-daemon so that it launches the daemon in
the background.
- Let start-stop-daemon create the PID (since the hostapd will not fork
now this PID will match the hostapd process, allowing to kill it later)
This solution also hides the hostapd log messages that appeared before.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-4045
The original init script hardcodes the configuration file to use so it
cannot be re-utilized for concurrent AP/AP mode where two interfaces can
be used as SoftAP.
This commit uses the variable ${IFACE} to:
- select a specific configuration file per interface:
/etc/hostapd_${IFACE}.conf
- create a specific PID file per interface:
/var/run/hostapd.${IFACE}.pid
With this, the /etc/network/interfaces can use the script for using SoftAP
in different wireless interfaces.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
With the migration to Morty, some of the paths to the artifacts (boot
and rootfs images) need to be updated.
While on it, also remove the temporary README.txt file which is not
needed after it has been packed in the zip installer.
https://jira.digi.com/browse/DEL-4013
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
- The Bluetooth daemon was always executed before setting up the
hardware, generating several problems specifically in the CCIMX6SBC.
This was causing the Bluetooth driver to override the Bluetooth name
and alias, as well as avoiding any host function on Bluetooth profiles.
Only pairing and ping was working, as well as client profile sides.
- This change also fixes some issues in the CCIMX6UL platforms with the
Bluetooth daemon failing to perform several bluetoothctl operations.
https://jira.digi.com/browse/DEL-4000https://jira.digi.com/browse/DEL-4015
Signed-off-by: David Escalona <david.escalona@digi.com>
- Some Python modules are no longer available in DEY-2.2 since
the official supported Python version is now 3. This caused the
HDP application to fail importing some of the old modules. For this
reason the sample application has been updated to use Python3
syntax and modules.
https://jira.digi.com/browse/DEL-3996
Signed-off-by: David Escalona <david.escalona@digi.com>
Print the HW and FW versions for the I/O Expander in the CC6UL SBC platform.
https://jira.digi.com/browse/DEL-3958
Signed-off-by: Sebastian Pastor <sebastian.pastor@digi.com>
If the volume is not found, the partition cannot be wiped since it is attached.
Remove 'update' UBI device in:
* mdev automount script if volume is not found
* recovery init script before formatting 'update' partition
https://jira.digi.com/browse/DEL-3962
Signed-off-by: Tatiana Leon <tatiana.leon@digi.com>
ICU support was not included in the rootfs in previous DEY versions
but it's included now through runtime dependences of 'harfbuzz' and
'libical'.
The support is not strictly needed, as ICU is a library for Unicode
support for applications:
http://site.icu-project.org/home
This commit disables ICU support directly for 'harfbuzz' and adds a
patch for 'libical' that allows to disable it. Notice that it's only
disabled for the CC6UL, as the CC6 has no rootfs space problems.
Only the 'libicudata' library is 25MB:
25M /usr/lib/libicudata.so.57.1
https://jira.digi.com/browse/DEL-3854
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The unlock retries feature from the Telit plugin does not work properly with
old versions of the Telit HE910 firmware. This has been fixed in upstream
commit: fbb607f0c25be3a4bb8692ee48445cf437345b6c
Signed-off-by: Salvador Penalva <salvador.penalva@digi.com>
https://jira.digi.com/browse/DEL-3863
This reverts commit 3123085e72.
we revert this commit because the patch was already applied on mm-1.6.4
Signed-off-by: Salvador Penalva <salvador.penalva@digi.com>
This commit adds mdev support into the recovery ramdisk to
mount/unmount storage devices for the firmware up tool.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-3692
udhcpc's '-n' option means 'Exit if lease is not obtained'.
We want to keep udhcp client alive if lease is not obtained, so when it is
possible, an IP is assigned.
https://jira.digi.com/browse/DEL-3821
Signed-off-by: Tatiana Leon <tatiana.leon@digi.com>
udhcpc options added to 'network/interfaces':
* '-S' to log to syslog too.
* Redirect the output to '/dev/null' not to show messages of the tool running
in background (for example when executing 'ifup').
* '&' to send the udhcp client to background.
https://jira.digi.com/browse/DEL-3821
Signed-off-by: Tatiana Leon <tatiana.leon@digi.com>
This is to avoid the following QA error:
ERROR: fbtest-1.0-r0 do_package_qa: QA Issue: No GNU_HASH in the elf binary: '/usr/local/ssd/dey-2.2/workspace/ccimx6ulstarter/tmp/work/cortexa7hf-neon-dey-linux-gnueabi/fbtest/1.0-r0/packages-split/fbtest/usr/bin/fbtest' [ldflags]
ERROR: fbtest-1.0-r0 do_package_qa: QA run found fatal errors. Please consider fixing them.
ERROR: fbtest-1.0-r0 do_package_qa: Function failed: do_package_qa
ERROR: Logfile of failure stored in: /usr/local/ssd/dey-2.2/workspace/ccimx6ulstarter/tmp/work/cortexa7hf-neon-dey-linux-gnueabi/fbtest/1.0-r0/temp/log.do_package_qa.6755
ERROR: Task (/usr/local/ssd/dey-2.2/sources/meta-digi/meta-digi-dey/recipes-digi/fbtest/fbtest.bb:do_package_qa) failed with exit code '1'
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Reviewing the patches while updating the QCA firmware to a new release,
I encountered this patch. On the original PR it says:
"Do not use hcitattach to reconfigure the baudrate but set it directly in the
Bluetooth FW file; this save us from some syncronism problems if we are not
using HW flow control."
Current spins of the module already use hw flow control. Also, not allowing
hciattach to override the baudrate does not seem right to me. It would be
enough with passing a 3M baudrate to hciattach to match the firmware
default.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This commit fixes an issue with ModemManager to return the correct
error code when an invalid QMI command is send to the modem.
There are two ways to get the UIM/SIM status, one with the "DMS"
service that works on most devices from 2015 and earlier, and a
new way with the "UIM" service that works on many 2015+ devices.
Perhaps the EC21 is new enough that it requires the UIM service,
but ModemManager doesn't recognize the error code that it's returning.
There are two ways to get the UIM/SIM status, one with the "DMS"
service that works on most devices from 2015 and earlier, and a
new way with the "UIM" service that works on many 2015+ devices.
Perhaps the EC21 is new enough that it requires the UIM service,
but ModemManager doesn't recognize the error code that it's returning.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-3748
This commit fixes an issue with the Quectel EC21/EC25 due to a wrong
reported DMS version which will cause ModemManager not to read the
SIM card.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-3748
Implement:
* support to start, stop and restart interface
* states machine and retries system to recover from command failures
* overall simplification and code clean-up
https://jira.digi.com/browse/DEL-3858
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
- Trying to set the complete SWU packages signature key in the
TrustFence class was causing a build error when keys were not
yet generated. To avoid this, set only the key wildcard in the
TrustFence class and expand the variable in the SWU packages
recipes, when keys already exist.
https://jira.digi.com/browse/DEL-3913
Signed-off-by: David Escalona <david.escalona@digi.com>
- Instead of trying to generate the TrustFence keys in this recipe
when they are not present, depend on the 'virtual/kernel' to
ensure they are already generated. This solves a concurrency problem
when two recipes try to generate TrustFence keys at the same time.
https://jira.digi.com/browse/DEL-3913
Signed-off-by: David Escalona <david.escalona@digi.com>
Allowing to boot a non-encrypted rootfs when encryption is enable is a security
hole: if an attacker can somehow write (offline) to the media, he could flash a
custom unencrypted rootfs and break into the system.
If the system is configured to use encryption, only encrypted rootfs will boot.
Trying to boot a non-encrypted rootfs will fail and power off the device.
https://jira.digi.com/browse/DEL-3829
Signed-off-by: Tatiana Leon <tatiana.leon@digi.com>
The recovery ramdisk already contains functionality for encrypted rootfs
installation. The goal is to centralize all this functionality in the recovery
ramdisk.
https://jira.digi.com/browse/DEL-3829
Signed-off-by: Tatiana Leon <tatiana.leon@digi.com>
For CC6UL, when setting a new key, an "enc" flag must be added to the rootfs in
the "mtdparts" U-Boot variable.
After that a reboot is needed, so the recovery command must be modified to
remove the encryption key and proceed with the rest of commands in the next
boot.
When updating the firmware, a format of the rootfs partition is always
performed, independently if a new encryption key has just been configured.
In case only the encryption key is being configured, we also need to reboot to
format the rootfs properly.
https://jira.digi.com/browse/DEL-3685
Signed-off-by: Tatiana Leon <tatiana.leon@digi.com>
For CC6UL, when not using rootfs encryption, the "enc" flag must be removed from
the "mtdparts" U-Boot variable.
https://jira.digi.com/browse/DEL-3685
Signed-off-by: Tatiana Leon <tatiana.leon@digi.com>
Software update recipes ('core-image-base-swu' and 'dey-image-qt-swu') are able
to set default or customized values for:
* In the CC6, the proper path for:
* linux partition (default to '/dev/mmcblk0p1')
* rootfs partition (default to '/dev/mmcblk0p3' if no encrypted, always
'/dev/mapper/cryptroot' otherwise)
* In the CC6UL, the proper volume name for
* linux partition (default to 'linux')
* rootfs partition (default to 'rootfs')
https://jira.digi.com/browse/DEL-3666https://jira.digi.com/browse/DEL-3686
Signed-off-by: Tatiana Leon <tatiana.leon@digi.com>
This commit verifies that the wlan1 interface is not already created
and will skip creating the virtual interface if it already exist.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-3917
With the upgrade to Morty, there is a new bootscript that is provided
by Poky. This bootscript is just launching the generic bluetooth daemon,
but it's not doing any hardware initialization.
The fix is to split the hardware initialization to a different
bootscript 'bluetooth-init' and launch it also on boot.
https://jira.digi.com/browse/DEL-3855
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
If you try to use libmbim (the API is used at least by mbim-network,
mbimcli and ModemManager applications) you get the following error:
ModemManager: Error converting string: Conversion from character
set 'utf-8' to 'utf-16le' is not supported
In order to solve this we need to integrate glibc gconv UTF16le library
in the build (and its dependencies).
Signed-off-by: Mike Engel Mike.Engel@digi.comhttps://jira.digi.com/browse/DEL-3830
This commit changes the concurrent mode script to enable always the
AP interface through the wireless device but will warn the use
if the virtual MAC addresses used are the default once.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-3900
The flash_eraseall busybox utility is not used in the ccimx6 and ccimx6ul
platforms. Its corresponding patch (and the library it depends on) can be
removed from the busybox recipe.
https://jira.digi.com/browse/DEL-1320
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This commit adds the wireless concurrent mode as a default
configuration to the CC6UL machine.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-3818
- Enabled signing support while generating the swupdate
packages for 'core-image-base' and 'dey-image-qt'. The
signing support is only enabled when 'TUSTFENCE_SIGN=1'
and requires the recipe to set the private key that will
be used to generate the signature.
- Enabled hash support while generating the swupdate
packages for 'core-image-base' and 'dey-image-qt'. The
hash support requires the sw-description files to include
a new line for each image and/or file that will be added
to the update package. The hash is automatically calculated
and replaced in the sw-description files.
https://jira.digi.com/browse/DEL-3774
Signed-off-by: David Escalona <david.escalona@digi.com>
- While trying to update the system using signed swupdate packages, the
swupdate binary requires a new parameter (-k) to specify the location
of the public key that will be used to verify the update package. At
the moment there is no way to check if a package is signed or not, so
we asume that the existence of the public key in the recovery initramfs
is enough to determine that we want to update the system using signed
packages.
https://jira.digi.com/browse/DEL-3775
Signed-off-by: David Escalona <david.escalona@digi.com>
- The swupdate binary included in the recovery partition when the
images to build are trustfence enabled performs a verification
of the swupdate package. For this verification to suceed, it is
mandatory to provide to the swupdate binary the public key that
will be used to verify the swupdate package. This public key must be
included in the recovery initramfs only when 'TRUSTFENCE_SIGN=1'.
https://jira.digi.com/browse/DEL-3772
Signed-off-by: David Escalona <david.escalona@digi.com>
- The 'sign/verify' feature of swupdate can only be enabled/disabled at
compile time, it cannot be configured at run time.
- The 'sign/verify' defconfig file is only used when the images to
build are configured with 'TRUSTFENCE_SIGN=1'
- This change implies that all swupdate packages generated will have a
hash for the images to install and will be verified. Sign support is
only enabled for trustfence images.
https://jira.digi.com/browse/DEL-3773
Signed-off-by: David Escalona <david.escalona@digi.com>
- In Jethro, swupdate recipe was using 'swupdate_git.bb' as the main recipe to
build. In morty that recipe has been disabled and the '2017.01' one is used
instead, so we have to append to this new recipe by renaming our existing one.
- Our bbappend will now point to the same SHA1 that is being used, so we can
remove the SRCREV.
- The new code already includes the progress client patch, so it has been removed.
Signed-off-by: David Escalona <david.escalona@digi.com>
There is now a WLAN user guide with configuration examples so there is
no need to pollute the default file with comments.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This recipe is expected to create just an initramfs image, so force the
image FSTYPE with a python anonymous function, so there is no way to
change/append/override it from any other configuration file.
This prevents build failures due to circular dependences if for example
you add:
IMAGE_FSTYPES_append = " recovery.vfat"
to your project's local.conf.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
As of DEY-2.0 "mx6" was an override value for CC6, but not for the
CC6UL, so we used it to restrict the packages to be installed only in
the CC6.
Now in DEY-2.2 "mx6" is also a correct override value for the 6UL
family, so correct the override to prevent those gstreamer packages to
be installed in 6UL machines.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
As of Yocto 2.2, the shipped QT5 version is 5.7.1 which does not include
'qtbase-fonts' anymore, so remove that package and enable 'fontconfig'
package configuration so the system fontconfig support is used.
Also remove PACKAGECONFIG_GL overrides for CC6UL as they have been added
to upstream 'meta-freescale'.
https://jira.digi.com/browse/DEL-3451
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Also, fix gstreamer rtsp package name in dey-gstreamer package group.
https://jira.digi.com/browse/DEL-3459
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Also apply patches from meta-fsl-bsp-release (krogoth_4.1.15-2.0.1)
https://jira.digi.com/browse/DEL-3459
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Also apply patches from meta-fsl-bsp-release (krogoth_4.1.15-2.0.1)
https://jira.digi.com/browse/DEL-3459
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Also apply patches from meta-fsl-bsp-release (krogoth_4.1.15-2.0.1)
https://jira.digi.com/browse/DEL-3459
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Also apply patches from meta-fsl-bsp-release (krogoth_4.1.15-2.0.1)
https://jira.digi.com/browse/DEL-3459
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Let Yocto use their own compilation flags instead of hard-coding the
compile command. This fixes:
ERROR: card-detect-1.0-r0 do_package_qa: QA Issue: No GNU_HASH in the elf binary
https://jira.digi.com/browse/DEL-3451
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
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>
The wireless regulatory database has been moved to its own recipe, so
the update cannot be done bbappending this recipe.
This reverts commit 8e69db8ac5.
https://jira.digi.com/browse/DEL-3451
Signed-off-by: Javier Viguera <javier.viguera@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>
Add critical section in suspend script to avoid that more than
one instance can be executed concurrently. This happens, for
instance, when the power button key is pressed while the system
is resuming, causing issues on the wifi interface.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-3694
Tweaked to maintain the u-boot and linux revisions to AUTOREV instead of
the fixed SHA1s from the tag.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This parameter allows to set the time interval for scheduled scans in
seconds. This is usually managed by the wpa-supplicant dynamically, but
for example with DFS channels and non broadcasting SSIDs re-associations
take too long if the periodic scans time interval is not reduced.
https://jira.digi.com/browse/CC6UL-594
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Ship libgles3-mesa-dev package along with libgles2-mesa-dev because
otherwise GLES3 headers are missing from the toolchain and we have build
failures for example compiling QT applications.
Exactly the same workaround is done for the vivante implementation in
meta-fsl-arm layer.
Original patch (not merged into oe-core):
https://patchwork.openembedded.org/patch/134244/
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
https://jira.digi.com/browse/DEL-3088
According to NXP i.MX Linux Reference Manual:
The full CAAM function is exclusive with the Mega/Fast mix off feature
in DSM. If CAAM is enabled, the Mega/Fast mix off feature needs to be
disabled, and the user should
"echo enabled > /sys/bus/platform/devices/2100000.aips-bus/2100000.caam/2101000.jr0/power/wakeup"
after the kernel boots up, and then Mega/Fast mix will keep the power
on in DSM.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-3636
It's not enabled by default. It's controlled by DEY_IMAGE_INSTALLER
variable in the project's local.conf.
https://jira.digi.com/browse/DEL-3591
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Add critical section in suspend script to avoid that more than
one instance can be executed concurrently. This happens, for
instance, when the power button key is pressed while the system
is resumming, causing issues on the wifi interface.
https://jira.digi.com/browse/DEL-3431
Signed-off-by: Pedro Perez de Heredia <pedro.perez@digi.com>
The profiles created for the sgtl5000 sound card didn't have any priorities
assigned, making pulseaudio map a different profile than before and causing the
sink to remain unloaded.
This commit fixes this by assigning a priority to each profile. The values
were taken directly from the default profile to assure that pulseaudio's
behavior is the same using one profile or the other.
https://jira.digi.com/browse/DEL-3602
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
We have seen corner cases (e.g. when the partition to format has already
some corrupted UBI metadata) where ubiformat stops and ask the user for
confirmation to do the format. We cannot have such interactivity in the
recovery ramdisk so use the '-y' argument to assume yes for all
questions.
Also use the '-q' (quiet) parameter instead of the '/dev/null'
redirections to remove command's output.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This commit adds a wpa supplicant P2P configuration file and configures
the p2p0 interface automatically at pre-up.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
For the moment the cloudconnector is provided only as static library, so
the recipe can be simplified.
https://jira.digi.com/browse/DEL-3523
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
In pulseaudio, module-suspend-on-idle controls how much time a sink spends
in the 'idle' state before going to 'suspended'. This means the ALSA device
associated with the sink stays busy for a few seconds after loading or using
the sink.
This commit adds the timeout=0 parameter when loading module-suspend-on-idle.
Now the sink will go to the 'suspended' state right after being loaded or used.
https://jira.digi.com/browse/DEL-2218
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
On boot, pulseaudio looks for the sound cards' corresponding profile sets, and
uses a default configuration if none is found. This was causing pulseaudio to
take up to 5 seconds trying every possible default profile.
This commit fixes this by creating a specific profile set for each of the sound
cards on the ccimx6sbc so pulseaudio doesn't spend time trying different
profiles that don't apply to our platform. It also adds udev rules so
pulseaudio knows which configuration to load for each card.
https://jira.digi.com/browse/DEL-2218
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The HDMI hotplug script required alsa-utils to be installed in order to work.
This commit avoids this by adding a recipe for a small binary that replaces
aplay in the script.
https://jira.digi.com/browse/DEL-3482
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Instead of using a hardcoded path to the SWU update package, just get
the filename and search the file in the different mounted partitions
(giving priority to the internal 'update' partition over other external
media).
https://jira.digi.com/browse/DEL-3466
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
For block devices we can get the filesystem in the partition using the
'blkid' command.
This cleans up some warnings on mounting:
EXT4-fs (sda2): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (sda2): couldn't mount as ext2 due to feature incompatibilities
EXT4-fs (mmcblk0p4): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (mmcblk0p4): couldn't mount as ext2 due to feature incompatibilities
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
"i" variable in the nested loop is expanded to the absolute path
of the device, so prepending it with the ${device} results in
"/dev/sda/dev/sda1" for a 'sda1' partition.
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>
This avoids the certificate package being generated according to Debian
rules (libcloudconnector-cert).
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The CC6UL has little video capabilities and reduced storage memory so lets
remove gstreamer plugins included in -bad and -ugly to reduce the rootfs
size.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DUB-713
recovery-utils allows to configure recovery commands and reboot into
recovery mode.
Internal recovery-utils.git SHA1: 5555d4c736e3
https://jira.digi.com/browse/DEL-3358
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
When hotplugging the HDMI cable after booting the target, pulseaudio doesn't
load the HDMI sink. This commit fixes this by adding a udev rule and a script
that prompts pulseaudio to detect the HDMI sound card and load its sink, as
well as making it the default one.
If alsa-utils is available, a faulty command is run to load the card without
any audio output. Otherwise, module-udev-detect is unloaded and reloaded.
This is based on commit fca507d316.
https://jira.digi.com/browse/DEL-2327
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This is a clone from the original psplash recipe init script
but with the added fix:
@@ -25,5 +25,7 @@
read rotation < /etc/rotation
fi
-/usr/bin/psplash --angle $rotation &
+if [ -c "${FBDEV:-/dev/fb0}" ]; then
+ /usr/bin/psplash --angle $rotation &
+fi
which avoids running the application when there is no framebuffer
in the system. This prevents the following error message during
boot:
Error opening /dev/fb0: No such file or directory
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-2747
Some platforms, like ccimx6ulsbc, don't support jack detection
out of the box.
PulseAudio will mute the Headphones by default if it believes
there is no headphones jack plugged-in. With this patch we
tell it to preserve ALSA default value for the headphones
controls.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-3435
These recipes allow to generate the .swu update packages to be used with
SWUpdate. The packages can be generated using:
bitbake dey-image-qt-swu
bitbake core-image-base-swu
https://jira.digi.com/browse/DEL-3272
Signed-off-by: Diaz de Grenu, Jose <Jose.DiazdeGrenu@digi.com>
- Include psplash package in the recovery initramfs recipe.
- Start psplash in the recovery init.
- Add new methods to communicate with psplash from the init script.
- Show psplash progress information from the init script.
- Start progress binary to update psplash during a firmware update.
https://jira.digi.com/browse/DEL-3356
Signed-off-by: David Escalona <david.escalona@digi.com>
- This patch comes from the sw-update upstream and adds command line support
to the progress client binary.
a11e6f2b80https://jira.digi.com/browse/DEL-3356
Signed-off-by: David Escalona <david.escalona@digi.com>
- Added a 5 seconds delay before mounting external disks so they have
time to be recognized in the system.
- Check if UBI volume is mounted before formatting it.
- Check if eMMC block device exists before formatting it.
Signed-off-by: David Escalona <david.escalona@digi.com>
- Added the new image type 'recovery.vfat' to the DEY images
generation process. This new image is a clone of the 'boot.vfat'
but including the recovery ramdisk and the recovery boot script.
- Added the new image type 'recovery.ubifs' to the DEY images
generation process. This new image is similar to the 'boot.ubifs'
but including the recovery ramdisk and the recovery boot script.
Signed-off-by: David Escalona <david.escalona@digi.com>
- This recipe generates the recovery ramdisk image with the contents of the
recovery ramdisk tree (recovery-initramfs) and other packages.
Signed-off-by: David Escalona <david.escalona@digi.com>
Bringing the Bluetooth interface down and up during suspend
is not needed and it even showed problems on the Starter Board
where the Bluetooth interface does not come up again after
having been brought down in suspend.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-3416https://jira.digi.com/browse/DEL-3081
Separately add 'dey-gstreamer' to ccimx6ulsbc platform.
This platform does not have 'accel-video' but we want gstreamer
for using it with video/camera.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-2358
There is new functionality in that version that we need for our firmware
update solution, so append the git-based recipe and set the revision to
the 2016.10 version.
Also provide a customized build configuration file. Notice that the
defconfig file is actually a full '.config'. It needs to be a full
config file because otherwise the anonymous python function in the
recipe is not able to gather all the build time dependences.
https://jira.digi.com/browse/DEL-3355
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Remove preventive delays during the removal of Bluetooth and Wireless
interfaces. Tests revealed they are not needed.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
The loading of the wireless module without proper arguments does nothing.
Besides, if the interface was down before going to suspend, there is no
need for the wireless module to be loaded.
The wireless module will be loaded nevertheless (with proper arguments)
when the interface is brought up.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-3241
The suspend script was unloading the wireless module driver *only* if the
interface 'wlan0' was previously up. If the interface is down the module
does not unload and the system fails to suspend.
This patch removes the module always if it appears in the list of loaded
modules.
While on it, move the unloading of wireless after the unloading of
Bluetooth, to be in line with the reversed order in which they are loaded
on the resume_interfaces() call.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-3241
Use the static binary from the tarball, which should be common across
different platforms and operating systems.
https://jira.digi.com/browse/DEL-3261
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The u-boot header is required for U-Boot to boot the image in secure boot.
The cpio.gz.u-boot.tf image gets signed and encrpyted if required.
https://jira.digi.com/browse/DEL-3242
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>
The OTP word read was incorrect. HW_OCOTP_CFG5 corresponds to bank 0 word 6.
https://jira.digi.com/browse/ADK4A-1129
Signed-off-by: Diaz de Grenu, Jose <Jose.DiazdeGrenu@digi.com>
Print the wireless configuration as well as supplicant and hostapd version info
https://jira.digi.com/browse/DEL-3147
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This allows to correctly read the U-Boot version when using encrypted images.
Leave the current implementation as a fallback, in case the system is using an
old U-Boot which does not populate the device tree property.
https://jira.digi.com/browse/DEL-3025
Signed-off-by: Diaz de Grenu, Jose <Jose.DiazdeGrenu@digi.com>
When encryption is enabled, the signed U-Boot image will be used for the uSD.
This allows the uSD image to boot the device and recover it from the U-Boot
console, which is its main purpose. Nevertheless, the uSD image will not be
able to boot Linux.
https://jira.digi.com/browse/DEL-2877
This reverts commit 2e13e194d9.
Optimize the provided config file with default support for 802.11ac.
https://jira.digi.com/browse/DEL-3128
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Also change the image type of dey-image-trustfence-initramfs.
https://jira.digi.com/browse/DUB-615
Signed-off-by: Diaz de Grenu, Jose <Jose.DiazdeGrenu@digi.com>
x11vnc is light in size so we can include it in the final rootfs after
reworking the qtbase and packaga-management stuff.
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Including ICU increases the rootfs too much and is not needed unless we want
to build qtwebkit, so only include it for platforms with enough size.
Additionally, linuxfb support is not needed for ccimx6.
https://jira.digi.com/browse/DEL-3058
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
The ccimx6ul has a small NAND flash rootfs partition, and removing
package-management image feature saves around 10MB.
https://jira.digi.com/browse/DEL-3058
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Do not use hcitattach to reconfigure the baudrate but set it directly in the
Bluetooth FW file; this work arounds some synchronization problems when not
using HW flow control.
https://jira.digi.com/browse/DEL-3052https://jira.digi.com/browse/DEL-3057
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
CCIMX6UL's rootfs partition is not big enough for the default
'dey-image-qt' image. This commit reworks the QT5 and SATO installed
packages for the ccimx6ul, so the image fits in the rootfs partition.
https://jira.digi.com/browse/DEL-2607
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The ccimx6ul does not have a GPU, so opengl based gstreamer sink will
not work. Thus apply the patch only for the CCIMX6.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This plugin uses directly the framebuffer, so it can be used in non
X11-based systems, but it oly supports software rendered content,
no opengl/es.
https://jira.digi.com/browse/DEL-2607
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This allows to build 'qtbase' for the CC6UL.
It only fixes the broken build, as any QT application that uses OpenGL/ES
will fail because there is no support for QT/OpenGL in modules without
a GPU.
Fix:
arm-dey-linux-gnueabi-g++ -march=armv7-a -mfloat-abi=softfp -mfpu=neon
--sysroot=/ssd/dey/jethro/fb/ccimx6ulsbc/tmp/sysroots/ccimx6ulsbc
-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -Wl,-O1 -o opengldesktop
opengldesktop.o -lGL
.../arm-dey-linux-gnueabi/5.2.0/ld: cannot find -lGL
A similar commit was done in meta-fsl-arm.git (branch Krogoth).
https://jira.digi.com/browse/DEL-2607
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Add an empty calibration file to prevent the 'xinput_calibrator' tool
being launched on X11 desktop start.
The file does not have any calibration data because capacitive touch
displays usually do not need calibration.
https://jira.digi.com/browse/DEL-3046
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This file has not been synchronized with the one in Poky since previous
versions of DEY. Not much has changed, but sync it anyway.
Also:
* Get SHOWCURSOR from formfactor config files, but fallback to one
value depending on HAVE_TOUCHSCREEN if it was not configured.
* Rename the bbappend to the version generic '_%.bbappend'
https://jira.digi.com/browse/DEL-3046
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The name "ext-eth" seems to indicate "External Ethernet". Rename that variable
and related ones to a more proper name like second ethernet.
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Copy of the original defconfig in hostapd-2.4 and enabling next options:
- CONFIG_LIBNL32
- CONFIG_EAP_PSK
- CONFIG_EAP_PWD
- CONFIG_WPS
- CONFIG_WPS_NFC
- CONFIG_RADIUS_SERVER
- CONFIG_IEEE80211N
- CONFIG_IEEE80211AC
- CONFIG_DEBUG_FILE
This means that the hostapd binary will have support for that features, but it
does not imply that the wireless chip does support it.
https://jira.digi.com/browse/DEL-2936
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
This reverts commit b8f50680e5.
The support to read and write to an encrypted environment has been added, so
there is no need to exclude the u-boot-fw-utils anymore.
https://jira.digi.com/browse/DEL-2836
Signed-off-by: Diaz de Grenu, Jose <Jose.DiazdeGrenu@digi.com>
Add commented lines as example to configure and run the wlan0 interface in AP
mode using hostapd daemon.
https://jira.digi.com/browse/DEL-2913
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Do not autostart hostapd daemon on boot because because it will conflict with
wpa-supplicant process and add a custom hostapd.conf file with WPA2-AES
encryption.
https://jira.digi.com/browse/DEL-2913
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Currently we don't support booting encrypted images from an SDCARD, so
just disable the generation of such images.
https://jira.digi.com/browse/DEL-2876
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
enabled
There is currently no support on fw_printenv/fw_setenv to access an
encrypted environment.
This commit removes the package if U-Boot environment encryption is
enabled to avoid environment corruption on access.
It also documents the issue as a known issue.
https://jira.digi.com/browse/DEL-2625
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
According to 'grep' manual '\s' is a synonym for [[:space:]] which
matches spaces, TABs, but also newlines, etc. We want to only match
spaces and TABs, so use [[:blank:]] instead.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
* set cellular user and password
* stricter replace to not match set values
* only set cellular interface to auto
Internal merge of Github's PR:
https://github.com/digi-embedded/meta-digi/pull/2
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
By default, on closed devices you cannot revoke any key. To do so, it is
required to compile a U-Boot which instructs the HAB not to set the sticky
bit which write protects that field in the OCOTP controller.
This patch introduces a Yocto macro which allows to configure U-Boot in
that way.
In the ConnectCore 6, the value of this settings is ignored, because HAB never
sets the sticky bit which write protects that field.
https://jira.digi.com/browse/DUB-665
Signed-off-by: Diaz de Grenu, Jose <Jose.DiazdeGrenu@digi.com>
While performing usability testing on the TrustFence documentation, it has
been noted that in order to follow the secure boot instructions the
console needs to be enabled.
We have now moved the secure console section to the end of the
documentation so that disabling the console is the last configuration to
make in a secure system.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Down the bluetooth interface before entering suspend and up it after resuming
if it is present and up.
https://jira.digi.com/browse/DEL-2806
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Start syslog earlier (from 20 to 02) so it is running and other init scripts
can use it to log into the system like the S03networking script.
https://jira.digi.com/browse/DEL-2812
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
This is needed so the encrypted rootfs is properly resized to the
partition size.
https://jira.digi.com/browse/DEL-2765
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
New functionality has been implemented in trustfence-tool application,
so there is no need to call cryptsetup command.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Get filesystem type of rootfs block device and pass it explicitly to the
mount command to clean following warnings on boot:
EXT4-fs (dm-0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (dm-0): couldn't mount as ext2 due to feature incompatibilities
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
We need a different configuration file, because the SoftAP functionality is
supported using the hostapd package instead of the wpa_supplicant.
https://jira.digi.com/browse/DEL-2744
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Extend the report with more details about:
- memory usage
- all network ports (-a) with their related PIDs (-p)
- network link details (to determine if interface is up)
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Using module-detect there are some audio reverb problems. Reverting that commit
will make pulseaudio use module-udev-detect again instead, which takes longer
to initialize but does not have that problem.
This reverts commit e021f738ee.
https://jira.digi.com/browse/DEL-2587
Signed-off-by: Jose Diaz de Grenu de Pedro <Jose.DiazdeGrenudePedro@digi.com>
When module-alsa-sink is used, the audio is sometimes heard with
reverb. We will go back to module-udev-detect, so the functionality
introduced in the commit being reverted won't longer work.
This reverts commit fca507d316.
https://jira.digi.com/browse/DEL-2587
Signed-off-by: Jose Diaz de Grenu de Pedro <Jose.DiazdeGrenudePedro@digi.com>
Add a couple of bluez patches: one for increasing the number of connection
showed with "hcitool con" command and remove "refresh" option in hcitool
help that is not supported.
The qca6564 chip can support more than 10 simultaneous BLE connections.
https://jira.digi.com/browse/DEL-2735
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
qtwebengine does not support armv5 platforms (for example ccardimx28js),
so we need to restrict that package to the ccimx6sbc
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
When Trustfence is enabled, this adds a dependence on the TF initramfs,
so it's built and added to the boot image.
It also modifies the u-boot boot script on the fly, to boot correctly
using the Trustfence initramfs.
https://jira.digi.com/browse/DEL-2278
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This recipe builds the initramfs image that is used to boot from an
encrypted rootfs.
https://jira.digi.com/browse/DEL-2278
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This package adds some files needed by the trustfence initramfs and that
are not included in other packages.
https://jira.digi.com/browse/DEL-2278
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
lvm2 package provides some user-space tools, but also some dynamic
libraries: libdevmapper, libdevmapper-event, etc.
This commit allows to package the LVM2 libraries in a different package
than the LVM2 user-space tools. This way other user-space tools (e.g.
cryptsetup) that runtime depends on the LVM2 libs can only add that libs
package to the rootfs, instead of the whole LVM2 utilities.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The ccimx6ul or ccardimx28 do not have hdmi interface, so do not install the
hdmi hotplug script.
https://jira.digi.com/browse/DEL-2654
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
The TRUSTFENCE_UBOOT_DEK_SIZE Yocto macro maps to the UBOOT_DEK_SIZE U-Boot
Kconfig entry, which is defined as a choice entry. This makes necessary
to explicitly define the choice Kconfig entry for the configuration to
work.
Signed-off-by: Diaz de Grenu, Jose <Jose.DiazdeGrenu@digi.com>
There are several possible values for TRUSTFENCE_UBOOT_ENV_DEK:
* Not defined: if the trustfence support is not included.
Should not include the feature.
* 32 characters: when defining a valid key.
Should include the feature.
* "0": when explicitly disabling the feature.
Should not include the feature
* <other>: Invalid value, should trigger the error.
This commits fixes the logic so that 'None' (no defined) is taken as a valid
value.
Signed-off-by: Diaz de Grenu, Jose <Jose.DiazdeGrenu@digi.com>
The following utilities are supposed to be available on the environment's
PATH:
uptime, uname, cat, zcat, free, ps, mount, netstat, route, ifconfig, gzip
https://jira.digi.com/browse/DEL-2447
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This commit changes the CONFIG_CCIMX6SBC_CONSOLE_ENABLE_GPIO_NR define
into a platform independent setting.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-2641
The power regulator connected to the qca6554 chip is always on, which causes
the Bluetooth part to not work correctly after a software-reset.
This commit asserts momentarily the BT_EN line during the start-up sequence
to reset the Bluetooth controller so that it is in a predictable state after a
reset.
https://jira.digi.com/browse/DEL-2623
Signed-off-by: Isaac Hermida <isaac.hermida@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>
https://jira.digi.com/browse/DEL-2603
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Signed-off-by: Jose Diaz de Grenu de Pedro <Jose.DiazdeGrenudePedro@digi.com>
The steps to set the bluetooth MAC address is send an specific hci command
and an hci reset, so the bluetooth interface need to be up in order to
configure it.
Additionally we have generalized the way to read the MAC address from the
device tree and removed some old code for getting the MAC address in
kernel version 2.
https://jira.digi.com/browse/DUB-595
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Add a software workaround to disable the HW flow control because the SOM
revision 3 (and older) has swapped the bluetooth TX and RX lines so we need
to operate in DTE mode which implies that the HW control lines are swapped.
This also implies reducing the baudrate to avoid the need for HW flow control.
https://jira.digi.com/browse/DEL-2611
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Implement the set of TRUSTFENCE_ macros to configure each secure boot feature
available in U-Boot.
https://jira.digi.com/browse/DUB-570
Signed-off-by: Jose Diaz de Grenu de Pedro <Jose.DiazdeGrenudePedro@digi.com>
sysinfo is a bash script which gathers all the relevant information
from a running system on a timestamped compressed file.
https://jira.digi.com/browse/DEL-2447
Signed-off-by: Victor Rubio Victor.RubioTorroba@digi.com
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This commit adds a trustfence class to encapsulate all trustfence
configurations.
https://jira.digi.com/browse/DEL-2257
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This support comes from meta-linaro @9f899282caa9 and adds the ability
to configure getty dynamically from the console argument in the kernel
command line.
This will make it possible to enable/disable the console dynamically as
signalled by U-Boot.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Port the bluez5 qca6564 support based on 5.19 to the current version 5.33.
The ported version is based on qualcomm tag r110048.3.
https://jira.digi.com/browse/DEL-2581
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
This daemon (rngd) feeds random data from hardware device to kernel
entropy pool.
https://jira.digi.com/browse/DEL-2501
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
As of Yocto 2.0, the cryptodev module used as interface between
user-space and hardware encryption is the version 1.7.
According to that cryptodev's version documentation, the cryptodev
engine in openssh is outdated:
https://github.com/cryptodev-linux/cryptodev-linux/blob/cryptodev-linux-1.7/README
They provide an URL with two patches to update openssl. This commit
forward port those patches to the Openssl version used in this version
of Yocto.
https://jira.digi.com/browse/DEL-2501
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>
That restriction does not make any difference in the final image
contents, because no package depending on X11 is added to the image, and
it prevents the image from being built with the default DEY
configuration (that has X11 distro feature enabled).
This also allows to build the image in the buildserver with the same job
that builds other X11 based images.
https://jira.digi.com/browse/DEL-2106
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>
Otherwise building the demo application fails with:
| DEBUG: Executing shell function do_configure
| Project ERROR: Unknown module(s) in QT: svg
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This patch adds a udev rule and a script to detect HDMI hotplug and create
the HDMI audio pulseaudio sink if needed (that is, if the system was
booted with no HDMI cable plugged).
https://jira.digi.com/browse/DEL-2327
Signed-off-by: Jose Diaz de Grenu de Pedro <Jose.DiazdeGrenudePedro@digi.com>
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>
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>
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>
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>
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
Gabriel Valcazar
Arturo Buzarra
Hector Palacios
Javier Viguera
Mike Engel
Francisco Gil
Jose Diaz de Grenu
David Escalona
Hector Bujanda
Gonzalo Ruiz
Alex Gonzalez
Isaac Hermida
Sebastian Pastor
Tatiana Leon
Salvador Penalva
Alejandro Navarro
Pedro Perez de Heredia
Stephan Klatt
Jose Diaz de Grenu de Pedro
Victor Rubio