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>
P2P disabled is the default in the kernel module, so passing here the
parameter to 'modprobe' does nothing but prevents to set the parameter
in the kernel command line.
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>
These dependencies went missing when we deleted our first .bb file and replaced
it with a .bbappend. Without these dependencies, the build can sometimes fail.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@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>
Removing the flag breaks the build of the freetype package and possibly others.
Leave the flag as it is for now.
This reverts commit e4cbeafa1c.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This option configures gcc to use PIE by default, which is good from a security
standpoint. However, the files necessary to compile applications statically
with PIE support are missing from glibc, causing builds to fail. Said files
were removed on purpose in poky commit 472c86127ab57759588e5ec53c75ebb52667f094
because static PIE binaries apparently don't work very well when using gcc 7.x.
Instead of enabling static PIE support for glibc and risking runtime failures,
revert to our old situation and remove default PIE suport for gcc.
https://jira.digi.com/browse/DEL-6558
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@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>
This variant is exactly the same as variant 0x02, but with a new revision
of the i.MX6UL silicon.
https://jira.digi.com/browse/DEL-6555
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
In the update to thud, the recipe for this package was updated in
meta-freescale with a newer revision that, among other things, breaks
compatibility with the parameters we use to recover closed devices via USB.
Even if we change these parameters to obtain a configuration equivalent to the
one we've always had, closed devices still won't boot because the internal
logic of the tool has changed a lot.
Instead of patching the tool for this very specific use-case, revert to the
version we've been using in DEY 2.2 and 2.4.
https://jira.digi.com/browse/DEL-6520
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Remove the linux-v4.20 recipe and use the linux-fslc kernel recipe in
meta-freescale-3rdparty instead.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
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>
These platforms are not supported on DEY 2.6 yet, and a project created for
either of them will fail during the build.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@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 following firmware binaries to tag r10005.1 from
qca6574au-le-2-2-1_qca_oem repo at meta_build/firmware/sdio/
in order to support fast roaming (802.11r) for the qca6564
wireless chip:
e018e7b629b055dc4616c7e88c615b41 otp30.bin
8b638fdaf21f089940d98db518323767 qwlan30.bin
d6ece5037e595000770fbbb6015c0461 utf30.bin
https://jira.digi.com/browse/DEL-6496
Signed-off-by: Francisco Gil <francisco.gilmartinez@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>
Most of the support has been added to the meta-freescale layer, so
substitute our recipe for a .bbappend and redefine the tasks to build
U-Boot images for our two variants (1GB and 2GB).
https://jira.digi.com/browse/DUB-881
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
Every task in this recipe is already supported in the same way in the
meta-freescale layer, so just keep the .bbappend file to select SRCBRANCH and
SRCREV.
The DDR patch can be removed since that source code is now included into the
SCFW project.
https://jira.digi.com/browse/DUB-881
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
Javier Viguera
Gabriel Valcazar
Hector Palacios
Gonzalo Ruiz
Alex Gonzalez
Francisco Gil