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>
Hector Palacios
Gonzalo Ruiz
Gabriel Valcazar
Alex Gonzalez
Francisco Gil
Jose Diaz de Grenu
Arturo Buzarra