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>
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>
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>
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 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)
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>
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>
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>
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>
- 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
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>
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>
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>
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>
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>
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 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 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>
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>
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>
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 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>
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>
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>
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>
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>
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>
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>
Avoid splitting the boot script message in two different lines:
Starting bluetooth hardware: [OK]
done.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
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>
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>
Gabriel Valcazar
Arturo Buzarra
Jose Diaz de Grenu
Gonzalo Ruiz
Alex Gonzalez
Hector Palacios
Isaac Hermida
Sebastian Pastor
Javier Viguera
Mike Engel
Tatiana Leon
Salvador Penalva