Includes:
imx-vpu: Fix selected version for 6Q and 6DL [LF-1816]
An older version of imx-vpu, from upstream, is being selected
for the image instead of the current one. The problem is
the override imxvpucnm used for the COMPATIBLE_MACHINE
is no longer being used. Update the recipe to use SOC
overrides instead.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
Signed-off-by: Hector Bujanda <Hector.Bujanda@digi.com>
Includes:
imx-seco-libs: Switch branch to imx_5.4.47_2.2.0
multilib: imx-seco-libs: Fix LIBDIR
imx-seco.inc: use c0 for 8dxl phantom with new c0 boards
Signed-off-by: Hector Bujanda <Hector.Bujanda@digi.com>
Includes:
imx-boot_1.0.bb: Update M4 binary name for i.MX 8QM [YOCIMX-4866]
8QM M4 demos unified the binary name.
Change name make it more easy for understanding.
imx-boot: Update the build option for iMX 8DXL Phantom C0 new boards [YOCIMX-4663]
Signed-off-by: Hector Bujanda <Hector.Bujanda@digi.com>
Build the U-Boot for variants with 1GB of memory and make the installation and
boot scripts recognize all of the current variants.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Since this overlay is only used in the SBC Pro bootscript, have a separate
bootscript for the SBC Express.
https://jira.digi.com/browse/DEL-7276
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Update file:
- bdwlan30_US.bin (8c8b575fb9a65714df0b7c6cb3399ed6)
This file was generated by calibrating several CC8MN SOMs from spin 3
and merging their resulting BDF files into a Golden file.
It also encodes the Target output powers.
Reference calibration file is obtained from 'qca6574au-le-2-2-2_qca_oem' repo
at tag 'r00005.1' under path
'wlanfw/cnss_proc/wlan/fw/target/sdio_dst/qc6174/bdwlan30.bin':
- bdwlan30.bin (8a40d95698825e1718bee640b1f7982a)
Target output powers respect the maximum EVM for every data rate.
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
Add the ccimx6/6qp and update the ccimx8x supported U-Boot version. Even though
older versions of U-Boot can be built for the 8X, the dependencies with the
SCFW only make it possible to use the latest version of U-Boot to avoid
unexpected behaviour.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The boot script appends values to certain variables such as
$extra_bootargs and $overlays.
If the final instruction of the boot script (dboot command)
fails, these variables contain the new values, plus the original
one. Since the user recovers the prompt, he may do a 'saveenv'
to save the environment, and the modified variables will be
saved, only to be enlarged again on the next boot.
This can lead to repeated strings on such variables.
Save the original value and restore it in case of failure on
the dboot command.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
Follow the syntax:
_ov_<som|board>_<functionality>[_<hardware>].dts
where:
_ov_ identifies the file as an overlay.
som|board identifies whether the overlay applies to the SOM
or to the carrier board.
functionality identifies the function of the overlay.
hardware identifies the hardware to which the overlay
applies.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
Wrapping unterminated lines doesn't work for scripts (even
if they contain the backslash).
Substitute with full non-wrapped if/elif sentences.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-7252
In the ccimx6sbc, since each SOC has a separate set of device trees, we can use
the soc_family environment variable when generating the name of the final
device tree in the bootscript. However, for the ccimx6qpsbc, there is only one
set of device trees with the "imx6qp" prefix, even though there are SOC
variants such as the imx6dp. Running the bootscript on a ccimx6qpsbc with an
imx6dp SOC assembled will result in a failure, since it will look for a
non-existing device tree starting with a "imx6dp" prefix.
Stop using the soc_family variable and hardcode "imx6qp" instead.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
With the latest version of imx-mkimage, the original dtb file is being
removed at the end of the build.
Add a patch to preserve it and be able to run several builds during the
same compile run, like we do for imx-boot signing.
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
With this change, the ccimx6sbc and ccimx6qpsbc default images will now use the
xwayland backend instead of x11.
https://jira.digi.com/browse/DEL-7221
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
Remove all v4.9 recipes and build Linux using the same branch on all platforms.
The .inc files were only needed because of the existence of multiple Linux
versions, but that's not the case anymore, so remove them.
https://jira.digi.com/browse/DEL-7221
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The CST package requires byacc to compile, and even though this dependency is
met when building images for the target, said dependency needs to be made
explicit when the package is built for the SDK in order to avoid build errors.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
With the previous solution we would need to generate
multiple overlays for each soc_type, so if we have a
new soc type (for example the solo), we would need
to generate 3 different overlays.
Signed-off-by: Francisco Gil Martinez <francisco.gilmartinez@digi.com>
This commit fixed the sdcard generation when encryption is enabled.
In the sdcard image always is included the signed image instead of the
encrypted.
https://jira.digi.com/browse/DEL-7200
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This version supports encryption for devices with Advanced High Assurance Boot
(AHAB) capabilities. This commit also updates and simplifies Digi custom
patches.
https://jira.digi.com/browse/DEL-7175
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Add running 'mmc partconf 0 1 1 1' command to the uuu scripts after
writing the new U-Boot into the internal eMMC.
This is required for blank eMMCs on CC8MN and CC8X SOMs where the
'update' command has never been run to be able to boot from eMMC.
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
The encryption of the U-Boot environment uses the HWID as key
modifier. The HWID was being read using the fsl_otp driver sysfs
entries and over two words. The driver is now deprecated and also
the cc8x and cc8m platforms have different number of HWID words.
This patch modifies the function that reads the HWID words by
using new entries on the device tree 'digi,hwid_X' where X is the
index of the HWID word.
It also removes the need to select CONFIG_MD5 which is already
auto-selected on sandbox_defconfig by other config switches.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-7185
(cherry picked from commit 8ced362766)
The encryption of the U-Boot environment uses the HWID as key
modifier. The HWID was being read using the fsl_otp driver sysfs
entries and over two words. The driver is now deprecated and also
the cc8x and cc8m platforms have different number of HWID words.
This patch modifies the function that reads the HWID words by
using new entries on the device tree 'digi,hwid_X' where X is the
index of the HWID word.
It also removes the need to select CONFIG_MD5 which is already
auto-selected on sandbox_defconfig by other config switches.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-7185
The Cortex-M7 uses the UART4 as debug console, and it is
shared with the Cortex-A53. This commit disables it for the
ConnectCore 8M Nano DVK board to avoid conflicts.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
Store mkimage log for every built target so it can be later used by the
signing script to create the correct CSF file for every target.
https://jira.digi.com/browse/DEL-7158
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
The mkimage.log file is required by the signing script to create the CSF file.
Since there is one mkimage log file per target, update the mkimage.log symlink
right before signing the imx-boot file to ensure creating the CSF with the
corresponding mkimage log for every target.
https://jira.digi.com/browse/DEL-7158
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
This commit updates the M7 demos to new package version v2.8.0
of the new NXP release imx-5.4.24-2.1.0.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
This commit updates the M4 demos to new package version v2.8.0
of the new NXP release imx-5.4.24-2.1.0.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
This commit updates to the NXP imx-5.4.24-2.1.0 BSP.
Including following changes
In M4 MCUX SDK 2.8.0, it added PMS demo for CM40 to support Partition
reboot feature besides rpmsg pingpong. So change the m40 default image
to imx8qm_m4_0_TCM_power_mode_switch_m40.bin
Build i.MX 8DXL flash_linux_m4 with V2X off
Use option V2X=NO to switch V2X off.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
imx-boot files for target flash_regression_linux_m4 fail the signature
process, so skip them while signing the rest of the targets.
https://jira.digi.com/browse/DEL-7158
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
The cryptoauthlib package is being added in digi-defaults.inc, which is parsed
before this file. Setting the variable here overwrites its previous value,
causing the cryptoauthlib package to be left out of the rootfs. Append to the
variable instead of overwriting it to avoid this.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Aside from adding the wireless-regdb-static support, this NXP package needs to
be included in the rootfs so the regulatory fw gets loaded in userspace.
https://jira.digi.com/browse/DEL-7133
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Starting with Linux v4.15, regulatory domains are no longer handled via CRDA,
but via the kernel and a flexible database instead. Said database is included
in the wireless-regdb-static package, which conflicts with the old
wireless-regdb package.
To accomodate for this new package, add CRDA as a dependency for ccimx6
platforms only, and incorporate wireless-regdb-static for the rest of the
platforms. Additionally, the ccimx6 kernel should inherit the
kernel_wireless_regdb .bbclass so the plaintext database is copied to the
kernel sources, but since we use the same recipe for all kernel versions and
ccimx6 platforms are not yet supported in zeus, omit this change for now.
Remove the package-base .bbappend, since only ccimx6ulstarter images include
that packagegroup and they require wireless-regdb-static, anyway.
By adding the regulatory database, we avoid delays when going to suspend,
caused by the kernel waiting for the database to appear.
https://jira.digi.com/browse/DEL-7133
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
When loading the wireless driver in test mode, the UTF firmware file
is loaded.
On pcie chips, the UTF file is expected to be named 'utf.bin'.
On sdio chips, the UTF file is expected to be named 'utf30.bin'.
Rename the pcie UTF file to match this requirement.
md5sum
----------------------------------------------------------
qca65X4_pcie: utf.bin -> 41cfb4e50613cd0eeb0fa99a005131bd
qca65X4_sdio: utf30.bin -> 4743dee015047752e433e69f4db89974
https://jira.digi.com/browse/DEL-7086
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
Add Compliance Test Limits (CTL) information for FCC, CE and TELEC
certifications to the CC8X US Board Data File.
The rest of the file (calibration, target power levels, etc.) remains
intact.
Updated file:
- bdwlan30_US.bin (MD5SUM: 100a982b33b4a2cfeb34cdea794dc6d6)
https://jira.digi.com/browse/DEL-6995
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
Perform AHAB signing process without altering the original file.
https://jira.digi.com/browse/DEL-7024
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
When the Bootloader is an 'u-boot' select the correct u-boot
signed image to compose the sdcard artifact.
Signed u-boot artifacts start with 'u-boot-dtb-signed-'.
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
When the Bootloader is an 'imx-boot', select the correct imx-boot
signed image to compose the sdcard artifact.
https://jira.digi.com/browse/DEL-7024
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
Signed imx-boot files had the '-signed' appended at the end of the file.
Add it after the file prefix instead, so it is easier to replace using an
unsigned file for a signed one just by changing the file prefix.
https://jira.digi.com/browse/DEL-7024
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
The '-fmacro-prefix' option is a new GCC option introduced in gcc version 8.
To keep compatibility with previous GCC versions, remove this option from
the DEBUG_PREFIX_MAP list so nativesdk builds are able to compile this recipe.
Following is the compilation issue avoided by this patch:
| gcc: error: unrecognized command line option ‘-fmacro-prefix-map=<yocto-workspace>/tmp/work/x86_64-nativesdk-deysdk-linux/nativesdk-imx-mkimage/git-r0=/usr/src/debug/nativesdk-imx-mkimage/git-r0’
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
This recipe is now built as native and nativesdk by means of the
BBCLASSEXTEND configuration.
Remove every remaining legacy native configuration since all will be covered
by the class extension.
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
This service is the same as the one provided by NXP, but with altered
dependencies. Start it before the kernel modules are loaded so the firmware is
ready by the time the mcp25xxfd module is loaded.
https://jira.digi.com/browse/DEL-7114
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Disable all encryption support by default on CC8X and CC8MN platforms so
the default built images can be directly built.
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
LINUX_ARM64 images include the padding length in the size property of
their header, so for these images read the header size property instead
of calculating it with 'stat'.
https://jira.digi.com/browse/DEL-7024
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
If CONFIG_SIGN_MODE is unset, we were assuming the sign mode to be AHAB
whereas it is preferable to abort the signing process and notify with an
error message.
https://jira.digi.com/browse/DEL-7024
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
The signing script is used for signing multiple artifacts, not just the
kernel, so rename it for a broader use.
https://jira.digi.com/browse/DEL-7047
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
Signing with AHAB mode only requires an additional prior step, so
reuse as much code as possible.
Also, for Image.gz images, sign the uncompressed Image and later
compress the result.
https://jira.digi.com/browse/DEL-7047
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
Signing with AHAB mode only requires an additional prior step, so
reuse as much code as possible.
https://jira.digi.com/browse/DEL-7047
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
TRUSTFENCE_SIGN_MODE for ccimx8mn is "HAB", although the
BOOTLOADER_IMAGE_RECIPE is "imx-boot".
https://jira.digi.com/browse/DEL-7024
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
Includes:
- add io reset support including edge detection.
https://jira.digi.com/browse/CC6UL-1132
Signed-off-by: Pedro Perez de Heredia <pedro.perez@digi.com>
imx-mkimage is a host recipe to provide the mkimage_imx8 binaries, required
for the trustfence support with platform based on AHAB (ccimx8x). Since
these binaries are required to the sign process we need to export it in the
SDK to allow the standalone sign mode, and with that we can simplify the
mechanism to share these binaries with another recipes (u-boot, linux).
Also the do_deploy() from imx-mkimage recipe was removed to avoid overriding
the implementation from the native class and allow populating the mkimage
binaries.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Commit 3fbd38ca ("imx-boot: build ccimx8x images for B0 and C0 silicon
revisions") added support to build images for B0 and C0 revisions,
forgetting include this support on trustfence builds.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This recipe takes several binaries demo for the Cortex M7 CPU,
and are provided in the deploy directory.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This update is a cosmetic one and removes the RAM frequency from the SCFW
filenames. Reflect this change in the RAM_CONFIGS variable and in the uSD/UUU
installation scripts.
As a result, the imx-boot filenames will no longer have the RAM frequency
either.
https://jira.digi.com/browse/DEL-7096
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The scripts need to know the SOC's revision to be able to select the correct
imx-boot image. Modify the boot-artifacts bbclass so the renamed imx-boot files
are included in the installation .zip.
Also, bypass the SECO fw check in the uSD script so it can install future
versions that aren't recognized by U-Boot's SECO fw checking logic. The UUU
script doesn't require this bypass, since it doesn't use the Digi update
command to flash the bootloader.
https://jira.digi.com/browse/DEL-7069
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Modify the imx-seco recipe so it deploys the B0 and C0 versions of the SECO
firmware, Then, modify the imx-boot recipe so it builds every possible
combination of:
* RAM configuration
* imx-boot target (with and without M4 demos)
* Silicon revision
https://jira.digi.com/browse/DEL-7069
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
With the device tree overlays mechanism in place, the bootscript
doesn't need to set the fdt_file variable. Instead, it will use
the value it has (which can be changed by the user) and it will
simply update the 'overlays' variable with the device tree
overlays that apply basing on the hardware capabilities found
on the HWID, SOM version, and carrier board version.
This allows a user to override the default fdt_file to point
to his custom device tree, but still make use of the boot script
for hardware-detected overlays.
Without the need to set the base filename, the boot script is the
same for any carrier board of the ccimx8x SOM, so this commit
moves it to a common folder.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
Each platform now has only one base device tree, meant for the i.MX8DX variants
of the ccimx8x boards. Apply the QXP overlay in the bootscript if the SOC is
identified as an i.MX8QXP.
Since we want to give this overlay a higher priority than the SOM overlays
(wifi and bluetooth), prepend it to the overlay list after appending the SOM
overlays.
https://jira.digi.com/browse/DEL-7100
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
These overlays aren't handled in our bootscript, but we make them available for
users in case they wish to use alternative interface configurations.
https://jira.digi.com/browse/DEL-7100
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Remove the old wb device trees from the ccimx8x-sbc-express and ccimx8x-sbc-pro
configuration files and add the ccimx8x wifi and bt overlays. Modify both
platforms' bootscripts to apply the overlays depending on board_id, hardware
capabilities or module variants.
https://jira.digi.com/browse/DEL-7100
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The function that parsed the output for a U-Boot variable value
was receiving a multi-line output, with blank lines that were
not being properly processed.
Simplify the parsing by using 'sed' command.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DUB-951
The if condition expanded to nothing so the install command was
never called. Apart from that the install command was wrong and
missing the '-m' option for modifier.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
This allows to generalize the code instead of needing to replicate
overrides for each platform that contains the MCA.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
The variable BT_DEVICE_NAME is used to name the Bluetooth device name on
the BlueZ configuration file. Re-use the contents of DIGI_FAMILY (except
for ccimx6qp which re-writes it) to simplify platform definitions.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
- WLAN_P2P_INTERFACE is the same for all platforms: "p2p0".
- WLAN_P2P_DEVICE_NAME can be built out of ${DIGI_FAMILY} except for
the ccimx6qp, that's why it has a weak default assignment.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
Platform-based variable STORAGE_MEDIA, allows us to select the
correct configuration file without needing to replicate it per
platform.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
This overlay is not handled in our bootscript, but we add it to the Linux
partition in case users want to apply it manually.
https://jira.digi.com/browse/DEL-2609
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Parse the hardware version from the HWID and load the overlay if and only if
the revision is "1". Also, update the board's device tree list accordingly.
https://jira.digi.com/browse/DEL-7070
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Instead of having two separate device trees for the non-wireless and wireless
variants of the ccimx8mn, use the non-wireless .dtb as a base and apply the
overlays in the bootscript depending on the variant's capabilities.
Also, update the board's device tree list accordingly.
https://jira.digi.com/browse/DEL-2609
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This reverts commit 03d40edfd0.
The build of U-Boot without the flags field, incorporated changes
that made the Cortex M4 acquired certain resources (like GPIOs)
that were later not available for the Cortex A35 cores.
Revert this patch so that such changes only take place on images
that contain the M4 applications.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-7073
(cherry picked from commit 28ce9340f55a35199dacf1bcbf83dc016b6a2fc7)
Update to NXP's v1.4.0 porting kit, fix an issue with resource allocation
making some GPIOs unusable from the Cortex A35s and update the DCDs using NXP's
RPA v14.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@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 gpio.h file that is used to generate the SDK (which comes
from kernel 5.4) with Digi debounce additions.
https://jira.digi.com/browse/DEL-7027
Signed-off-by: Hector Bujanda hector.bujanda@digi.com
Added rsync to the native dependencies, since it is used during
header install to prevent a build issue.
https://jira.digi.com/browse/DEL-7013
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Default version is defined in poky layer, this commit also modifies
the preferred version to match with the new one.
https://jira.digi.com/browse/DEL-7013
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Remove support to kernel v4.14 and move platforms to use the new
kernel v5.4
https://jira.digi.com/browse/DEL-7013
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
packagegroup-base includes wireless-regdb-static package unconditionally,
however it conflicts with wireless-regdb that it is required by crda,
which is included as a dependency to packagagroup-dey-wireless.
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>
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)
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>
Digi Embedded Yocto 2.6-r3.1
Manually changed recipes to use the master branches instead of the fixed SHA1
from the last release.
Signed-off-by: Mike Engel <mike.engel@digi.com>
There is no need to generate PV-PR revision of this file
since it's the same for any version.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
The recipe needs to create a copy of the sign.sh script to be used by
other recipes, but the file is the same whether you use it for HAB or AHAB
images. This is determined through the use of an exported variable with
the mode. There is no need to have the script duplicated.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
The only script that needs to generate the SRK_efuses is the sign.sh
script in the U-Boot code. For the rest of signed non-bootable artifacts
this is not required and it was creating the SRK_efuses file on every
recipe where the script was called, like linux-dey and others, which
eventually resulted in a conflict when copying the artifacts to the shared
deploy-image-dir.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
This binary is required for signing the U-Boot scripts generated
by the U-Boot recipe but it wasn't available because this recipe
was not installing it anywhere.
At the same time, remove the installation from imx-boot, to avoid a
conflict between the two (imx-mkimage is a dependency from imx-boot
anyway).
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
Environment encryption is not yet supported in U-Boot.
Unset TRUSTFENCE_ENCRYPT_ENVIRONMENT on the machine configuration
and remove the platform conditional on the class.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
This commit changes the u-boot sources needed to create standalone
signing tools to 2019.04. This u-boot supports all Trustfence
platforms.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
This commit adds some dependencies to include the imx-mkimage package
that is needed to use the mkimage_imx8 tool.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
* prefix TRUSTFENCE_ to variable SIGN_MODE for DEY
* prefix CONFIG_ to variable SIGN_MODE for script
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
The bootable artifacts that must go inside the installer ZIP image, are defined
in the variable BOOTABLE_ARTIFACTS. For platforms without RAM_CONFIGS, these
artifacts are obtained from the UBOOT_CONFIG variable.
This commit fixes the final artifact name added to the BOOTABLE_ARTIFACTS that
for some platform is not strictly the same that the UBOOT_CONFIG name.
For example for the U-Boot configuration "ccimx8mn_dvk", corresponds the
bootable artifact "ccimx8mn-dvk"
https://jira.digi.com/browse/DEL-6974
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This commit fixes the copy of the initramfs final image with the extension
*.tf when Trustfence is disabled. This was introduced by commit
5beec04b ("trustfence: Add Trustfence support for CCMX8X")
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
Commit 5beec04b ("trustfence: Add Trustfence support for CCMX8X") introduces
a dependency when the imx-mkimage recipe and the SIGN_MODE is equal to AHAB.
However this dependency should be added only when the TRUSTFENCE_SIGN is equal
to 1 and when the SIGN_MODE is equal to AHAB, not only when the SIGN_MODE is
equal to AHAB. This commit introduces this double check.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Commit 31d8ff94 ("meta-digi-arm: u-boot: Update recipes with new u-boot version")
updates the license checksum for the new u-boot_2019.04 recipe, however this
license file is different for the other u-boot versions.
This commit reverts this change and includes the updated checksum only for the
new u-boot_2019.04 recipe.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Wrapped lines must have a back-slash symbol so that U-Boot
doesn't interpret them as finished.
The missing symbol resulted in the script not being able to
determine the U-Boot image to program in some cases.
Reported-by: Leonid Makhnovskiy <leonid.makhnovskiy@digi.com>
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6953
Regulatory domain support will be added completely with the 'regulatory-addon'.
Also simplify symlink management now that BDF file has the same name for
every platform.
https://jira.digi.com/browse/DEL-6841
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
The ccimx8mn console is on ttymxc0 (uart1 thanks to aliases).
https://jira.digi.com/browse/DEL-6876
Signed-off-by: Hector Bujanda <hector.bujanda@digi.com>
This file does not longer exist. It has been replaced by bdwlan30_US.bin,
which is already included to the community driver option.
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
Now that xbee-init supports multiple interfaces, add the XBee Cellular
GPIOs to the already existing XBee User ones to it so it can handle both
of them on the ccimx8mn DVK.
https://jira.digi.com/browse/DEL-6887
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Update US Board Data File to fix a wrong calibration of channel 7 (2442 MHz).
The rest of the file remains the same.
The new BDF is:
- bdwlan30_US.bin (f6ec3328309aaa3e187295446966ab27)
https://jira.digi.com/browse/DEL-6922
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
Update file:
- bdwlan30_US.bin (d5221377de1dde9ff442740e56fea647)
This file was generated by calibrating several CC8MN DVKs and
merging their resulting BDF files into a Golden file.
Reference calibration file is:
- bdwlan30_US.bin (a5635e39aaaa220094e0d07f7a4f4567)
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
The new driver uses the same files for both platforms (6564,
6574). The specific platform binaries have been removed.
Now the modifications of the nvm_tlv_3.2 to disable the IBS
is done by the recipe.
The disable of the deep sleep and the enable of the internal
clock is done in the recipe only for the CC6UL.
We have used the files from the following repo:
qca6574au-le-2-2-2_qca_oem -> 4d29c6886f2Commit label r00005.1
- CS2.2 0.0.005.1
md5sum
------------------------------------------------------------
nvm_tlv_3.2.bin -> a97cdfe80e8109cf3574f74cd3c73fc7
rampatch_tlv_3.2.tlv -> 72d28614afd0abe5846c1758099282e3
https://jira.digi.com/browse/DEL-6766
Signed-off-by: Francisco Gil <francisco.gilmartinez@digi.com>
Update the wireless driver to a newer version that supports both
chips (qca6574 and qca6564).
We keep the same bdwlan30_US.bin files as the previous version
of the driver (or fakeboard_US for the qca6474).
Rename directories to qca65X4_driver_interface.
We have used the files from the following repo:
qca6574au-le-2-2-2_qca_oem -> 4d29c6886f2Commit label r00005.1
- CS2.2 0.0.005.1
md5sum
----------------------------------------------------------
qca65X4_pcie: otp30.bin -> 9d1cf03473904bd8b97fa30bc92b4a16
qwlan30.bin -> 794f7a6f12ef3e6f8db6257b3a6f896f
utf30.bin -> 41cfb4e50613cd0eeb0fa99a005131bd
qca65X4_sdio: otp30.bin -> e018e7b629b055dc4616c7e88c615b41
qwlan30.bin -> fe37bc043132ecf21e504eb33f46b846
utf30.bin -> 4743dee015047752e433e69f4db89974
https://jira.digi.com/browse/DEL-6766
Signed-off-by: Francisco Gil <francisco.gilmartinez@digi.com>
Although the recipe was updated with the modifications in meta-fsl-bsp-release,
the revision was still pointing to the sumo-4.14.98-2.2.0 version of
imx-mkimage, which is incompatible with our recently updated patch.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Update to NXP's v1.3.0 porting kit and add power optimizations for suspend
mode.
https://jira.digi.com/browse/DEL-6932
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Update to v2.5.4 and add new recipe imx-seco-libs. For the time being, use the
B0 firmware for all i.MX8QXP platforms and leave C0 support in a comment.
https://jira.digi.com/browse/DEL-6932
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Update SRCREV and SRCBRANCH, change the names of the m4 demos that are
installed into imx-boot, change the name of the SECO firmware (ahab container)
and update our patch so it applies over the newest revision of imx-mkimage.
For the time being, use the B0 SECO firmware for all i.MX8QXP platforms and add
the changes needed for C0 support in comments.
https://jira.digi.com/browse/DEL-6932
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Update the values of the MACHINE_SOCARCH_FILTER variable with the ones in
meta-fsl-bsp-release's imx-base.inc.
https://jira.digi.com/browse/DEL-6932
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The LPDDR4 retention code is executed as part of the suspend/resume process.
When resuming, this code writes to a register that doesn't exist on the
i.MX8MN, causing the system to freeze before control is returned to Linux.
Add a patch that introduces a compile-time check for the SoC type to avoid
performing the write operation on the i.MX8MN.
https://jira.digi.com/browse/DEL-6914
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The Cortex-M7 uses the UART4 as debug console, and it is
shared with the Cortex-A53. This commit disables it for the
ConnectCore 8M Nano DVK board to avoid conflicts.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
For the i.MX8M processors, the do_deploy support is provided by
the upstream recipe firmware-imx-8m.
https://jira.digi.com/browse/DEL-6911
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
WPA and P2P configuration files are basically the same between all
platforms, so we remove all duplicated files to use a common file
and modify it in the recipe logic.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Update the README as well to reflect this change, since the ftp protocol might
be blocked in some corporate networks.
https://jira.digi.com/browse/DEL-6880
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Also remount the root filesystem as 'rw' when the symlinks need to be
updated.
https://jira.digi.com/browse/DEL-6760
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
Obtain the mount point of the filesystem to remount as 'read-write' from
/proc/mounts to avoid issues related to df output wrapping on a second line
when the device filesystem name is too long.
When the script finishes, remount the filesystem as 'read-only' if that was
the original access permission.
https://jira.digi.com/browse/DEL-6760https://jira.digi.com/browse/DEL-5854
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
Update file:
- fakeboar_US.bin (f74a835871d9c12f116312ff54927b39)
This file was generated by calibrating 10 CC8X SOMs (version 0x4) and merging
their resulting BDF files into a Golden file. Target powers table is also
updated to improve performance on 2.4GHz band.
Reference calibration file is:
- bdwlan30.bin (8a558fa38dacee7038f04c1b10ec69a5)
located at 'cnss_proc/wlan/fw/target/pcie_dst/qc6174/' from tag r10007.1 on
qca6574au-le-2-2-1_qca_oem repo.
https://jira.digi.com/browse/DEL-6852
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
(cherry picked from commit a332ff445f)
Update file:
- fakeboar_US.bin (f74a835871d9c12f116312ff54927b39)
This file was generated by calibrating 10 CC8X SOMs (version 0x4) and merging
their resulting BDF files into a Golden file. Target powers table is also
updated to improve performance on 2.4GHz band.
Reference calibration file is:
- bdwlan30.bin (8a558fa38dacee7038f04c1b10ec69a5)
located at 'cnss_proc/wlan/fw/target/pcie_dst/qc6174/' from tag r10007.1 on
qca6574au-le-2-2-1_qca_oem repo.
https://jira.digi.com/browse/DEL-6852
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
This adds the same example application that was used for the old version of the
library, but it has been separated into a proper package this time.
Recommend said package when installing the library.
https://jira.digi.com/browse/DEL-6826
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This version is based on the 20190517 master release, with the addition of
pkcs11 provisioning support.
The source code now has cmake files, so we don't need as many code
customizations as we used to. Revamp the recipe and its patches.
https://jira.digi.com/browse/DEL-6826https://jira.digi.com/browse/DEL-6835
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This imx-seco recipe manages now the NXP IMX SECO firmware, it was removed
from the firmware-imx recipe.
https://jira.digi.com/browse/DEL-6823
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Rename board data file loaded on qca6574 wireless chips to 'fakeboar_US.bin'.
A symlink named 'fakeboar.bin' will be created by 'qualcomm.sh' selecting
either this file or the WorlWide variant: 'fakeboar_World.bin'.
- fakeboard_US.bin (e1db4a300b58776f8abd8588beadc09e)
https://jira.digi.com/browse/DEL-6773
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
Generalize script to select the correct board data file to load into the
wireless chip depending on the Regulatory Domain configuration whether it
is a variation of 'bdwlan30.bin' or 'fakeboar.bin'.
If 'bdwlan30_US.bin' or 'bdwlan30_World.bin' files are found in the firmware
directory, the script will create two symlinks, 'bdwlan30.bin and 'utfbd30.bin',
pointing to either one of those files.
If no 'bdwlan30_*.bin' files are found, but 'fakeboar_US.bin' or
'fakeboar_World.bin' is, it will create a single symlink, 'fakeboar.bin',
pointing to either one of those files. In the case a QCA6574 community driver
is loaded, 'board.bin' symlink will be updated.
If no 'fakeboard_*.bin' files are found either, the script will exit.
https://jira.digi.com/browse/DEL-6773
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
Digi Embedded Yocto 2.6-r2.2
Manually changed recipes to use the master branches instead of the fixed SHA1
from the last release.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Rename board data file loaded on qca6574 wireless chips to 'fakeboar_US.bin'.
A symlink named 'fakeboar.bin' will be created by 'qualcomm.sh' selecting
either this file or the WorlWide variant: 'fakeboar_World.bin'.
- fakeboard_US.bin (e1db4a300b58776f8abd8588beadc09e)
https://jira.digi.com/browse/DEL-6773
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
Generalize script to select the correct board data file to load into the
wireless chip depending on the Regulatory Domain configuration whether it
is a variation of 'bdwlan30.bin' or 'fakeboar.bin'.
If 'bdwlan30_US.bin' or 'bdwlan30_World.bin' files are found in the firmware
directory, the script will create two symlinks, 'bdwlan30.bin and 'utfbd30.bin',
pointing to either one of those files.
If no 'bdwlan30_*.bin' files are found, but 'fakeboar_US.bin' or
'fakeboar_World.bin' is, it will create a single symlink, 'fakeboar.bin',
pointing to either one of those files. In the case a QCA6574 community driver
is loaded, 'board.bin' symlink will be updated.
If no 'fakeboard_*.bin' files are found either, the script will exit.
https://jira.digi.com/browse/DEL-6773
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
Update file:
- fakeboar.bin (e1db4a300b58776f8abd8588beadc09e)
This file was generated by calibrating several CC8X SOMs and SBCs and
merging their resulting BDF files into a Golden file.
Reference calibration file is:
- bdwlan30.bin (8a558fa38dacee7038f04c1b10ec69a5)
located at 'cnss_proc/wlan/fw/target/pcie_dst/qc6174/' from tag r10007.1 on
qca6574au-le-2-2-1_qca_oem repo.
https://jira.digi.com/browse/DEL-6736
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
Default poky's version of the 'mount.sh' script doesn't account
for the possibility of udev calling twice the script for the 'add'
action. This has been observed on USB sticks connected to a USB hub
and, although the script eventually fails, for already mounted
partitions, in that case the script tries to remove the created
mountpoint, when it shouldn't.
This patch checks for already mounted partitions earlier (before
creating the mount point) and returns with no actions.
The patch that it adds (with respect to poky's thud default) is
the following:
diff --git a/meta/recipes-core/udev/udev-extraconf/mount.sh b/meta/recipes-core/udev/udev-extraconf/mount.sh
index 3ee67b13183a..e6882a69c223 100644
--- a/meta/recipes-core/udev/udev-extraconf/mount.sh
+++ b/meta/recipes-core/udev/udev-extraconf/mount.sh
@@ -38,6 +38,12 @@ done
automount_systemd() {
name="`basename "$DEVNAME"`"
+ # Skip already mounted partitions
+ if [ -f /run/systemd/transient/run-media-$name.mount ]; then
+ logger "mount.sh/automount" "/run/media/$name already mounted"
+ return
+ fi
+
# Skip the partition which are already in /etc/fstab
grep "^[[:space:]]*$DEVNAME" /etc/fstab && return
for n in LABEL PARTLABEL UUID PARTUUID; do
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6759
Update file:
- fakeboar.bin (3e558869e3943da08899abd881455bc6)
This file was generated by calibrating several CC8X SOMs and merging
their resulting BDF files.
Reference calibration file is:
- bdwlan30.bin (8a558fa38dacee7038f04c1b10ec69a5)
located at 'cnss_proc/wlan/fw/target/pcie_dst/qc6174/' from tag r10007.1 on
qca6574au-le-2-2-1_qca_oem repo.
https://jira.digi.com/browse/DEL-6736
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
The current scripts used the standard mount binary at /bin/mount
for mounting the partitions. Systemd however seems to have a monitor
that eventually umounts such partitions if not mounted by systemd's
specific command 'systemd-mount`.
For platforms using systemd, we need to use this binary together with
parameter --no-block so that partitions are mounted correctly during
the boot process.
This commit merges the two scripts for Digi-handled partitions into
just one:
mount_bootparts.sh
\
+--> mount_digiparts.sh
/
mount_partition.sh
The merged script:
- checks if running with systemd, to use its binary.
- checks if running with busybox, to not use the unsupported '-o'
attribute.
- checks if mounting the 'linux' partition, to mount it read-only.
- checks for already-attached UBI devices, to avoid re-attaching.
This commit also combines the Digi-handled partitions (linux, update)
into the same udev rule, to simplify it, and breaks the rules lines
for readability.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6744
Error message was being printed upon successful copy of the
MAC addresses file, instead of upon failure.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
Latest release r10007.1 updates the following files from qca6574au-le-2-2-1_qca_oem
repo at meta_build/firmware/pcie/:
- qwlan30.bin -> qwlan30.bin (60ac4486fba393294b590f86117f5539)
- utf30.bin -> utf.bin (c15794509d8a8435d4244fea699d99b3)
and the following files from meta_build/firmware/sdio/:
- qwlan30.bin -> qwlan30.bin (4421b30ca259ab73bbfa79df807e0b47)
- utf30.bin -> utf30.bin (b2651762aa1d620349593905efab326b)
Update Bluetooth firmware from qca6574au-le-2-2-1_qca_oem repo at
cnss_proc_1/btfm_proc/bt/wcss/bsp/rom/build/SCAQBAF/Test_Files/Linux/
- rampatch_tlv_3.2.tlv -> rampatch_tlv_3.2.tlv (72d28614afd0abe5846c1758099282e3)
- nvm_tlv_3.2.bin -> nvm_tlv_3.2.bin (3de46ea023570b86cabb9502b92a1fed)
Note: nvm_tlv_3.2.bin based on original md5sum
a97cdfe80e8109cf3574f74cd3c73fc7 but changed byte at
offset 0x36 from 0x82 to 0x02 (IBS).
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6725
Remove our .bbappend, which was wrongly making this recipe compatible with the
imx8. Directly port NXP's recipe (v5.4.39), which is newer than the one in
meta-freescale (v5.4.38).
https://jira.digi.com/browse/DEL-6722
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Change the license type from "MIT" to "Proprietary". This change was taken
from the imx-sc-firmware recipe.
https://jira.digi.com/browse/DEL-6722
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Otherwise, users that are behind corporate firewalls might not be able to
obtain the package sources.
https://jira.digi.com/browse/DEL-6663
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The 'soc_type' variable was already set by fastboot to "imx8qxp"
so the U-Boot board code that was setting this to just "8qxp" has
been changed to set it to "imx8qxp".
Update the scripts accordingly.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DUB-901
On some scenarios, like when booting from NFS, the root filesystem is not
writteable. When this happens the qualcomm.sh is not able to write the MAC
file which so the wireless driver fails to load.
The arguments that U-Boot uses when booting from NFS using dboot result in
the root filesystem being mounted as read-only, but at some point it is
remounted as read/write. This happens after trying to load the wireless
driver, though.
Currently this is the only scenario in which we can reproduce the problem,
and there are several other processes in DEY that require a writeable root
filesystem (wireless SSID editing, Dropbear SSH key-gen and u-boot-fw-utils)
so remount the rootfs as writteable as a workaround.
While on it improve the script a bit to notify on error trying to create
this file, just in case this happens in other scenarios.
https://jira.digi.com/browse/DEL-5854
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
All the dependencies of the required symbols are also added.
These are easier to mantain and enable the minimum support. If extra
features are required they shuold be explicitly added.
https://jira.digi.com/browse/DEL-6681
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
This commit fixes two issues:
- Comparison clause uses only one equal sign
- Fix soc_type for Dual variants because the supported soc types
for the imx8 processor are: 8qm, 8qxp, and 8dx
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
These images were broken in many ways, including ethernet not working and Linux
not booting. For now, revert back to the build command that was used in
DEY-2.6-r1.
https://jira.digi.com/browse/DEL-6677
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
When using virtualization, ammend the kernel configuration so that docker
is supported.
https://jira.digi.com/browse/DEL-6681
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
The meta-freescale-3rdparty layer used for the mainline bsp support does
not support the WiFi interface on thud. WiFi is currently merged on master
so it will probably be available on Zeus (2.8).
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
After the recent changes to generate the bootable artifacts, these are
now formed using the ${MACHINE} variable rather than the string in
${UBOOT_CONFIG} array, so the underscores must be changed with dashes.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
The artifacts that must go inside the installer ZIP image are not anymore
the ones in UBOOT_CONFIG. For CC8X, the artifacts are combinations of
UBOOT_CONFIG and RAM_CONFIGS.
This commit adds a function 'get_bootable_artifacts()' to boot-artifacts class
to generate a new variable BOOTABLE_ARTIFACTS with the list of bootable
artifacts DEY produces.
The installer recipe can then simply iterate on that list, rather than
needing to calculate it by itself.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6641
The existing loops were iterating through all RAM_CONFIGS, but
they must only iterate over those that match the RAM size on the
platform's UBOOT_CONFIG.
This commit adds a Python class 'boot-artifacts' to get the list of matching
combinations of RAM_CONFIGS and UBOOT_CONFIG so that the iteration
is easier to do than nesting loops inside one another.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6641
The recipe was creating a variable with the value of another one from
the main recipe, just to refer to the bootable artifact prefix.
We can now use instead the new UBOOT_PREFIX variable.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
A variable called IMAGE_BOOTLOADER was being used without distinction for
referring to two different things:
- the recipe that builds the bootable artifacts
- the prefix of those artifacts
The value of this is "u-boot" for most platforms, but "imx-boot" for the
CC8X based platforms.
The name of the variable is misleading, so this commit splits it into two:
- BOOTLOADER_IMAGE_RECIPE, to refer to the recipe
- UBOOT_PREFIX, to refer to the prefix of the bootable artifact
With the separation, the variable UBOOT_SYMLINK becomes a generic formed
one, so it is moved to digi-defaults.inc.
While on it, fix the image_types_digi.bbclass which was not making use of
the original variable to establish all the dependencies.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
Similar to the way the u-boot recipe does, create a symlink to the default
bootable artifact.
Since they are overwritten on every loop, this requires that the default
RAM configuration is set the last on the list of RAM_CONFIGS (same
convention than the one used on UBOOT_CONFIGS).
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6641
With the rework to support variants, the machine name (actually the
UBOOT_CONFIG) was removed from the filename. Re-add it using
${MACHINE_NAME} which is more appropriate than the ${UBOOT_CONFIG} which
contains the RAM size (now present in ${ramc}).
While on it, remove one of the two symlinks on DEPLOYDIR. Only one makes
sense.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6641
Now the U-Boot binaries contain the RAM frequency and bus width, not just
only the RAM size.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6641
There are several U-Boot binaries, depending on RAM size, at the moment:
- u-boot.bin-ccimx8x_sbc_pro512MB
- u-boot.bin-ccimx8x_sbc_pro1GB
- u-boot.bin-ccimx8x_sbc_pro2GB
and several SCFW files, depending on frequency, size, bus width, at the
moment:
- scfw_tcm.bin-1.2GHz_512B_16bit
- scfw_tcm.bin-1.2GHz_1GB_16bit
- scfw_tcm.bin-1.2GHz_1GB_32bit
- scfw_tcm.bin-1.2GHz_2GB_32bit
From these, we need to combine those that match the RAM size, to produce
bootable images for the different variants.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6641
With the arrival of DualX variants, the device tree files have been renamed
to contain the SOC type (8qxp, or 8dx). This is determined by a new U-Boot
variable 'soc_type'.
Default to "8qxp" if the variable is not defined (old U-Boots).
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6641
With the arrival of DualX variants, the devicetree files have changed
their names to include the soc type (qxp, dx).
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6641
Even though our ccimx6 and ccimx6qp images were using Linux v4.9 sources
correctly, they were using the same recipe as our images with Linux v4.14.
Technically, both recipes are identical (save for the branch name), but each
Linux version should have its own recipe.
Also, make sure that ccimx6/ccimx6qp images are built with our version of the
linux-imx-headers recipe instead of the one in meta-freescale.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
We want to run the script if the 'wireless' node exits on the device tree.
This is to facilitate disabling of the wireless by removing that node.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6616
This recipe was updated in NXP's 4.14.98-2.0.1 patch release.
https://jira.digi.com/browse/DEL-6618
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The 'do_install()' call was doing a 'cd' command to later do symlinks
more straight forward.
This 'cd' however may affect further 'do_install' appends, that expect to
be working on the ${WORKDIR}.
Remove the 'cd' command and instead supply the correct paths to the 'ln'
commands.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
(cherry picked from commit 54bd1e47ad024515b737aea106dc4fca374c0fb8)
The new HWID fields make U-Boot create new variable 'module_ram'.
If it exists use it to select the U-Boot file to use during
firmware update. If not, fall back to old method of using the
variant code and the hard-coded table of variants.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6598
The new HWID fields make U-Boot create new variable 'module_ram'.
If it exists calculate new HWID fields to check if the SOM has
Wi-Fi, Bluetooth, etc. in order to select the device tree file.
If not, fall back to old method of using the variant code and
the hard-coded table of variants.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6598
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>
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>
The new development branch is based on NXP's v4.14.98 BSP.
https://jira.digi.com/browse/DEL-6603
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This is the version used in meta-fsl-bsp-release branch sumo-4.14.98-2.0.0_ga
for the imx8qxp.
https://jira.digi.com/browse/DEL-6603
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This recipe's package is meant for packages that require NXP-specific linux
headers.
https://jira.digi.com/browse/DEL-6603
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This is the version used in meta-fsl-bsp-release branch sumo-4.14.98-2.0.0_ga.
https://jira.digi.com/browse/DEL-6603
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This is the version used in meta-fsl-bsp-release branch sumo-4.14.98-2.0.0_ga.
When using v1.5, we used a .bbappend to change the revision of the v1.5 recipe
in meta-freescale. Since we're upgrading to a version that isn't supported in
the other layers yet, remove the .bbappend and add the entire v2.0 recipe.
https://jira.digi.com/browse/DEL-6603
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This is the version used in meta-fsl-bsp-release branch sumo-4.14.98-2.0.0_ga.
https://jira.digi.com/browse/DEL-6603
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Update NXP's .bbclass files with the ones in meta-fsl-bsp-release branch
sumo-4.14.98-2.0.0_ga.
https://jira.digi.com/browse/DEL-6603
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Digi Embedded Yocto 2.6-r1.3
Manually changed recipes to use the master branches instead of the fixed SHA1
from the last release.
Signed-off-by: Arturo Buzarra <arturo.buzarra@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>
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>
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>
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
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>
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>
This adds support for U-Boot v2018.03 for CC8X platforms only.
Create 'digi-u-boot.inc' with the common definitions for both v2017.03
and v2018.03.
https://jira.digi.com/browse/DUB-881
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
Collects following changes:
- fix compatible string parsing: Only first compatible string
was being parsed from "/proc/device-tree/compatible"
while looking the device the application is running on.
https://jira.digi.com/browse/DEL-6436
Signed-off-by: Hector Bujanda <hector.bujanda@digi.com>
Add kernel module parameter to enable/disable the p2p interface.
By default p2p interface is disabled.
https://jira.digi.com/browse/DEL-6503
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
The naming of branches in the qcacld repository is now in the qca65x4
namespace.
Also, the qca6564/master branch now does not hardcode the TX MCS to 0 as
this change should only apply to the CC6UL and not other platforms like
the CC6+.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Update file:
- fakeboar.bin (f9f8dc905be5732525e0c9e8db7822f3)
This file was generated by calibrating several CC8X SBC Pro boards and merging
their resulting BDF files.
Reference calibration file is:
- bdwlan30.bin (8a558fa38dacee7038f04c1b10ec69a5)
located at 'cnss_proc/wlan/fw/target/pcie_dst/qc6174/' from tag r10005.1 on
qca6574au-le-2-2-1_qca_oem repo.
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
Device tree files no longer have the kernel type prefixed to their name, so the
trustfence_sign() function must be updated to reflect this change or else
errors will occur.
https://jira.digi.com/browse/DEL-6476
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This version supports OpenSSL v1.1.0 by default, which is used in DEY 2.6.
Trying to build older versions of the package will result in failures, so
remove support for said versions entirely.
Our patches apply cleanly except for the hab4_pki_tree.sh automation patch,
which needs a small tweak so it can get applied over the latest version of the
script.
https://jira.digi.com/browse/DEL-6476
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@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)
In Yocto 2.6, this variable is null whenever systemd is enabled. Explicitly set
this variable to keep some necessary scripts in /etc/init.d.
https://jira.digi.com/browse/DEL-6415
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Also, remove sysvinit and add pam, which is needed by weston+systemd.
https://jira.digi.com/browse/DEL-6415
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Fix write operation by moving the re-lock of the mmc partition
after performing the system synchronization, if not the mmc
driver throws read-only errors. Also, improved the code
to avoid compilation warnings because the return values were
not managed in write operations.
https://jira.digi.com/browse/DEL-6449
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Hector Bujanda
Hector Palacios
Gabriel Valcazar
Arturo Buzarra
Gonzalo Ruiz
Francisco Gil Martinez
Mike Engel
Javier Viguera
Jose Diaz de Grenu
Alex Gonzalez