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>
Mike Engel
Tatiana Leon
Javier Viguera
David Escalona
Jose Diaz de Grenu
Arturo Buzarra
Isaac Hermida