There is a mismatch between the new upstream recipe that uses a cache folder
to share the header files and the imx recipe that requires a specific folder.
https://jira.digi.com/browse/DEL-7013
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Bluetooth class to support the bluez4/bluez5 distro features,
was removed due to bluez4 was removed from meta-oe some time ago.
This commit simplifies the requeriments adding directly the bluez5,
instead of the intermediate bluetooth class.
https://jira.digi.com/browse/DEL-7013
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
In meta-freescale was renamed the linux-imx-headers recipe with the
full linux kernel version "4.14.98". With that change our custom
recipe from meta-digi is not selected. This commit reuses the recipe
from meta-freescale layer and modifies it.
https://jira.digi.com/browse/DEL-7001
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Update u-boot-fw-utils patches to apply on upstream version 2019.07.
https://jira.digi.com/browse/DEL-7013
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Digi customized linux kernel gpio.h file to allow debounce functionality by the
user space through the character device.
This commit patches the default gpio.h file that is used to generate the SDK
(which comes from kernel 4.18) with Digi debounce additions.
https://jira.digi.com/browse/DEL-7027
Signed-off-by: Hector Bujanda <hector.bujanda@digi.com>
Commit 07d4a6ba ("xserver-xorg: Backport to fix X server 1.20.1 crash")
integrates this patch in meta-freescale layer, then it is no longer
necessary to have it in our meta-digi layer.
This reverts commit 995212a213.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This configuration is required to sign and encrypt U-Boot images during
build time, as it is done for ccimx6ul platform.
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
Add Trustfence support for signing imx-boot images:
- Install a different U-Boot signing script for images with U-Boot SPL.
- Store mkimage log for later use in the signing script
- make 'print_hab_log' and store its log for later use in the signing script
https://jira.digi.com/browse/DEL-7023
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
Do not evaluate TRUSTFENCE_SIGN_MODE on conditions where the sign mode
is not relevant:
1) U-Boot binary file should be signed directly after building it when simple
U-Boot images are used, but it should not be signed when imx-boot bundled
images are used.
For those, the signing process is performed later over the whole imx-boot
bundled binary file on a different recipe.
We use BOOTLOADER_IMAGE_RECIPE variable to evaluate this distinction.
BOOTLOADER_IMAGE_RECIPE is set to "u-boot" by default and is set to "imx-boot"
on ccimx8x and ccimx8mn machine configuration files.
2) For signing imx-boot images we should treat differently those images that
include the RAM configuration in their name and those that don't, as we do
for the rest of the tasks in the same recipe. We can ignore the sign mode
method in this case.
https://jira.digi.com/browse/DEL-7023
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
Some CC6Plus units fail to communicate with the Bluetooth chip at a certain
temperature range, as happened on some CC6UL units.
Apply the following customizations to the NVM file so the communication is
maintained regardless of the temperature.
- Disable DEEP_SLEEP
- Enable Internal Clock
These customizations were already performed on the NVM file for the CC6UL.
https://jira.digi.com/browse/DEL-3711
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
(cherry picked from commit 400b31f652fb98bb1620e03f85a33c231bf6f244)
Generalize 'Disable Deep Sleep' and 'Enable Internal clock' customizations
so they can be applied on every platform by defining
BT_INTCLOCK_WORKAROUND to '1'.
Disable the customizations by default and enable them for ccimx6ul only.
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
(cherry picked from commit 78ef498178abe587d6e2cb4b1ed8ba5f8979fb4e)
We are currently applying customizations to the base NVM file on install.
There was an error that introduced the '"\' characters into the NVM file
instead of the intended hex data.
This commit fixes the implementation of this customization.
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
(cherry picked from commit a204a7bfc54fc15aca0d87530c838fb427710a8e)
Generalize wireless concurrent mode and DFS-capable channels limitations
which apply for every platform.
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
This commit adds a installation script that uses fastboot support to
update the target firmware.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-6845
Additionally:
- The handling of gpios has been swapped so 'Set low XBEE_SLEEP_RQ' is done
before 'Power cycle XBEE_RESET_N' to assure the device doesn't enter sleep mode.
- Removed ExecStop entry from systemd service since it's doing nothing.
https://jira.digi.com/browse/DEL-6424https://jira.digi.com/browse/DEL-6423
Signed-off-by: Hector Bujanda <hector.bujanda@digi.com>
Arturo Buzarra
Hector Bujanda
Gonzalo Ruiz
Francisco Gil Martinez
Hector Palacios
Mike Engel