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>
This commit adds support to read the GPU reserved memory
from the DT.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-3868
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>
These new US and world board data files contain new settings updated
with the latest certification results including the 2 dB power reduction
from DVT.
md5sums:
a5635e39aaaa220094e0d07f7a4f4567 bdwlan30_US.bin
cabebad84a6afc1c2a7d795d31dda480 bdwlan30_World.bin
https://jira.digi.com/browse/CC6UL-740
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Variant 0x04 has wireless and must select the '-wb' device tree.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-4100
Tatiana Leon
Salvador Penalva
Javier Viguera
Mike Engel
Alejandro Navarro
Diaz de Grenu, Jose
Alex Gonzalez
Sebastian Pastor
Hector Palacios