We are going to remove this repo, so the sources will always be fetched from
the official Microchip repo from now on.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Install crypto libraries in the rootfs so external applications can made use
of them.
Reworked first patch with all the needed port changes.
https://jira.digi.com/browse/DEL-5710
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Make SRC_URI point to Microchip's standalone repo of the cryptoauth library,
add our customization patches and modify the license variables to point to the
new Microchip license file.
https://jira.digi.com/browse/DEL-5591
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Under certain circumstances I was able to create a microSD card with
the FAT file system but corrupt partition table like this one:
Device Boot Start End Sectors Size Id Type
/dev/sdf1p1 778135908 1919645538 1141509631 544,3G 72 unknown
/dev/sdf1p2 168689522 2104717761 1936028240 923,2G 65 Novell Netware 386
/dev/sdf1p3 1869881465 3805909656 1936028192 923,2G 79 unknown
/dev/sdf1p4 2885681152 2885736650 55499 27,1M d unknown
Specifying the partition index made the install script to fail, but
not specifying it makes it work, although it also falls back to use
the first partition in the table.
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
util-linux is needed as the scripts use 'hexdump'. In previous versions
of Yocto the tool from the host was used, but this has been fixed in
Yocto 2.3
Also fix the other dependencies: the -native suffix is not needed nor
correct, as the native and nativesdk classes already map packages in
the DEPENDS variable to the corresponding packages.
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
The MACHINE_EXTRA_RRECOMMENDS for the ccimx6ul in meta-digi-arm contains
cryptoauthlib. If we want to use meta-digi-arm as a standalone BSP layer
we need to move the cryptoauthlib recipe to meta-digi-arm, that or not make it
a machine dependency.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
In the old u-boot-fw-utils 2016.x the function 'fw_env_close' wrote
the environment to the media. That is no longer the case, now that
function only frees the memory used, and 'fw_env_flush' is used
to write the environment.
This was causing that userspace application using this library were not
able to write changes to the environment.
https://jira.digi.com/browse/DEL-5644
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
Generate and include the host tools in the SDK when Trustfence is enabled.
This makes it easier to use the standalone signing and encrypting scripts.
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
Bash v4.4 or higher warns when discarding NULL bytes in command substitution
output. Remove these bytes to avoid the undesired warnings.
https://jira.digi.com/browse/DEL-5588
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This allows us to save around 4MiB of space in the rootfs image.
(see commit in poky/meta 71ca295786e35b7be84bfd4bc04e0c3ec0f97cd8)
https://jira.digi.com/browse/DEL-5613
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Support for dynamic location of U-Boot environment was added in
commit 2b5017956b. This forward ports
the patch to Yocto 2.4.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-5574
As a side effect, remove U-Boot entry point variable and LOADADDR
extra parameter from the kernel recipe.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-5554
Some packages are not updated in meta-freescale/rocko, so we do
need to include some of these.
The patches for gstreamer in the original commit are skipped, as
poky/rocko uses a newer version.
This partially reverts commits:
* 52a10ff88d.
* b06c81b277https://jira.digi.com/browse/DEL-5518
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
All these recipes and patches are now available and maintained in the
meta-freescale layer.
https://jira.digi.com/browse/DEL-5518
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
Pending to update the patch for dynamic environment location in NAND.
https://jira.digi.com/browse/DEL-5518
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
Cryptodev has been updated to version 1.9 and the patch is no longer
needed.
https://jira.digi.com/browse/DEL-5518
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
This tool was only needed for old kernels, newer kernels use the hardware
random number generator themselves.
https://jira.digi.com/browse/DEL-5518
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
ConnectCore 6 and ConnectCore 6 UL are now supported in kernel v4.9.
https://jira.digi.com/browse/DEL-5518
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
This functionality is automatically enabled for any recipe that inherits
the kernel class.
https://jira.digi.com/browse/DEL-5518
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
As per Yocto 2.4, do_image_<type>[depends] has replaced IMAGE_DEPENDS_<type>.
The previous trick to propagate *boot* dependencies from *boot.[vfat|ubifs]*
is no longer needed.
https://jira.digi.com/browse/DEL-5518
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
When parsing the recipe, a warning is shown because the tarball is only found
in the downloads folder. However this is expected as it cannot be distributed.
As a workaround, add the tarball to the SRC_URI variable only when Trustfence
is active. That way the warning is not shown in all other cases.
This was incorrectly removed in commit 14fc51147f.
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
U-Boot has been able to boot kernel zImage for a long time so make this
the default kernel image.
For the CC6 we still want to use uImage for compatibility reasons.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-5237
Prevents loading the spidev module at boot time to avoid
the undesired warning message from driver.
https://jira.digi.com/browse/DEL-4748
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This commit re-adds the imx-gpu-g2d recipe that was removed
from the imx-gpu-viv v6 driver.
https://jira.digi.com/browse/DEL-5234
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This commit adds the recipe to update the GPU driver
to the latest version.
https://jira.digi.com/browse/DEL-5234
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This commit adds the recipe to update the Vivante GPU
driver to the latest version and refresh patches.
https://jira.digi.com/browse/DEL-5082
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This commit adds the defconfig for the platform ccimx6qpsbc
to the kernel v4.9 and modifies the recipe.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This commit modifies different recipes to support the new platform
ccimx6qpsbc and adapt it to maintain the support to ccimx6sbc.
https://jira.digi.com/browse/DEL-5082
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This commit includes ccimx6qpsbc platform in the recipe and adds
U-Boot scripts for deploying and booting the system.
https://jira.digi.com/browse/DEL-5082
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Add initial support for Digi's ConnectCore 6 QuadPlus SBC.
The ccimx6qp platform has the QCA6564 chip instead of the
other Atheros chips and included the Atmel ECC508A cryptographic
chip.
https://jira.digi.com/browse/DEL-5082
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
The patch is needed to match the API kernel changes. This fixes:
zc.c:68:44: error: passing argument 7 of 'get_user_pages_remote' from incompatible pointer type [-Werror=incompatible-pointer-types]
(unsigned long)addr, pgcount, write, 0, pg, NULL);
^~
In file included from zc.c:28:0:
kernel-source/include/linux/mm.h:1276:6: note: expected 'struct vm_area_struct **' but argument is of type 'struct page **'
long get_user_pages_remote(struct task_struct *tsk, struct mm_struct *mm,
^~~~~~~~~~~~~~~~~~~~~
zc.c:63:8: error: too many arguments to function 'get_user_pages_remote'
ret = get_user_pages_remote(
^~~~~~~~~~~~~~~~~~~~~
In file included from zc.c:28:0:
kernel-source/include/linux/mm.h:1276:6: note: declared here
long get_user_pages_remote(struct task_struct *tsk, struct mm_struct *mm,
^~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
https://jira.digi.com/browse/DEL-5081
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
CC6 PS_ASIC_class_1.pst MD5SUM be8766069eed652449682d9006dd6ecd
https://jira.digi.com/browse/DEL-5057
Signed-off-by: Francisco Gil <francisco.gilmartinez@digi.com>
The current value only allows partitions of up to 8 MiB, which is not
enough for the 0x04 variant (which uses a linux partition of 24 MiB by
default).
This new value allows for up to 32 MiB (assuming 128 KiB erase block size).
Also add comments explaining the -c value and maximum partition sizes
supported.
https://jira.digi.com/browse/DEL-4971
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
After the 'ccardimx28js' platform removal, these variables and machine
features are not used anymore, so remove them.
https://jira.digi.com/browse/DEL-4771
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Tweaked to maintain some recipes' revisions to AUTOREV instead of the
fixed SHA1s from the tag.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
We need to pass different log levels depending on the message, so they
appear in the console, so generalize the 'log' function.
https://jira.digi.com/browse/DEL-4682
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
At the point this script is running from udev (the system log is not yet
available), so to avoid debug messages from qualcomm wireless module
reduce the console log level.
https://jira.digi.com/browse/DEL-4570
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This is required to be able to use the whole RootFS partition which is
512 MiB in the 0x04 CC6UL SOM variant.
The old value only allowed to manage partitions of up to 256 MiB, this new
value allows for up to 1 GiB (assuming 128 KiB erase block size).
https://jira.digi.com/browse/DEL-4567
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
At the point this script is run (from udev) the system log is not yet
available, so use the kernel log buffer instead.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Use the same udev script that loads the qualcomm wireless module to
create the 'wlan1' virtual interface.
https://jira.digi.com/browse/DEL-4453
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Udev comes with a bunch of generic rules for the hardware. One of them:
/lib/udev/rules.d/80-drivers.rules
is able to load the qualcomm wireless module.
At the same time our new rule is needed, so it prepares the firmware
before the module is loaded.
Both rules running collide with following error message:
udevd[181]: '/etc/udev/scripts/qualcomm.sh' [184] terminated by signal 1 (Hangup)
So to fix this, we rename the specific rule so it's parsed later, and
then we use the hard assignation '=' instead of '+=' to override the
values that come from the previous parsed rule.
Also clean-up a bit the 'qualcomm.sh' script and the modprobe file,
given that now we know the standard drivers rule won't run for this
interface.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
NetworkManager is not able to detect and manage the wireless interface
until is actually created, so let udev load the kernel module and create
the interface on boot.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
The new fw-4.bin (v3.4.0.236) with md5sum e2fc33daba2c35fe2c4f62492a44f8b6
was used to pass RED (Radio Equipment Directive) certification on the CC6
module.
https://jira.digi.com/browse/DEL-4512
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
A mechanism was introduced in U-Boot to dynamically locate the environment
copies within a NAND partition, skipping bad blocks and making full use of
the partition blocks.
To trigger this mechanism in Linux tools (fw_printenv/fw_setenv) the
configuration file /etc/fw_env.config must have both copies entries
pointing to the same offset.
This commit substitutes the hardcoded configuration file for CC6UL with a
stub and generates one on an RPM post-script basing on:
- Supplied DEY variables (with default values per platform):
- UBOOT_ENV_OFFSET: starting offset of the environment within the
partition.
- UBOOT_ENV_SIZE: size of each copy of the environment.
- UBOOT_ENV_RANGE: size in the partition that the environment copies may
occupy, starting from UBOOT_ENV_OFFSET. If undefined, the whole
partition is used.
- Calculated values:
- NAND Erase block size
- Number of blocks available for the environment copies
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-4256
Gabriel Valcazar
Arturo Buzarra
Isaac Hermida
Gonzalo Ruiz
Javier Viguera
Jose Diaz de Grenu
Alex Gonzalez
Hector Palacios
David Escalona
Sebastian Pastor
Francisco Gil
Mike Engel