The .elf output files are for debugging purposes, so put them into the
-dbg package to make this clear.
Change-Id: I5d70b2421b06eed0483f8ef508cf535ec70abc63
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Jon Mason <jon.mason@arm.com>
Update TF-M to version 1.3.0, mbed TLS to 2.26, TF-M tests to 1.3.0
(previously untagged), and MCU Boot now has a new git repo location and
updated to 1.7.2.
Change-Id: I7ff2756cacff02abd31bb54048f8846b6a58cd01
Signed-off-by: Jon Mason <jon.mason@arm.com>
Signed-off-by: Ross Burton <ross.burton@arm.com>
As the SRCREV is pinned to a specific SHA we should also set LINUX_VERSION, as future kernel
upgrades in oe-core master will change both SRCREV and LINUX_VERSION.
Change-Id: Iafababe83ff54625112d2fae859d8a3938001cd5
Signed-off-by: Ross Burton <ross.burton@arm.com>
Mark the build jobs as interruptible, as they don't write to shared
resources (unlike update-repos or get-binary-toolchains). This means
that if the same branch is pushed again GitLab is likely to be able to
abort the obsolete pipeline to start the new build sooner.
Change-Id: I9284273e9b3118b616d3cb062cb957d98fc5e37e
Signed-off-by: Ross Burton <ross.burton@arm.com>
There is only one provider for the armcompiler, so remove the virtual
provider.
Change-Id: I3492c49f5cf6eb6f3d3156adb3d87e315ed8183d
Signed-off-by: Ross Burton <ross.burton@arm.com>
These recipes don't build anything, so there's no need to depend on a
toolchain.
Change-Id: I49b641fb54839c30255a11a7c9d5798c8e4afd2a
Signed-off-by: Ross Burton <ross.burton@arm.com>
Add kernel configuration necessary to build an image with preempt-rt support
for fvp-baser-aemv8r64, together with a build configuration file to build it via
kas.
Update BSP documentation for RT linux support on the machine.
Issue-Id: SCM-2343
Signed-off-by: Richard Neill <richard.neill@arm.com>
Change-Id: I11e3ba3ad7da00db1810c70fa4f98bfffd4b8254
Signed-off-by: Ross Burton <ross.burton@arm.com>
In meta-virtualization master branch the sysvinit-inittab_virtualization.inc
was introduced to handle the installation of the getty-wrapper for spawing the
console login for /dev/hvc0.
Since we don't make usage of the virtualization DISTRO_FEATURES we have to
manually include the mentioned file when building with arm-autonomy-host and
arm-autonomy-guest DISTRO_FEATURES.
Also, since arm-autonomy-guest doesn't include the xen DISTRO_FEATURES we have
to manually include sysvinit-inittab_xen.inc to append the getty-wrapper entry
to /etc/inittab.
Issue-Id: SCM-2329
Signed-off-by: Diego Sueiro <diego.sueiro@arm.com>
Change-Id: I0f92565de8a9053c0541928c30b8f979757bfbca
Signed-off-by: Jon Mason <jon.mason@arm.com>
In meta-arm-bsp fvp-base switched to wic images. Hence, make the appropriate
changes to also use wic images in meta-arm-autonomy.
Change-Id: I34d68fee11ea339fb52a97d7593e373aa69faa1c
Issue-Id: SCM-2329
Signed-off-by: Diego Sueiro <diego.sueiro@arm.com>
Signed-off-by: Jon Mason <jon.mason@arm.com>
Add wks script, modify documentation and kernel command line.
Remove 'image_types_disk_img.bbclass' as it is no longer used.
Change-Id: I2a95349adc038e8484d7b9f578ad3ce698b1f528
Signed-off-by: Anders Dellien <anders.dellien@arm.com>
Signed-off-by: Jon Mason <jon.mason@arm.com>
Add new recipe for SCP version 2.8.0 and remove the old 2.7.0 recipe.
Change TC0 and N1SDP to use the latest tag, and not their previous
intermediate SHA (which are in the 2.8.0 release).
Change-Id: Id3f0af549790969ce6fd3b315f94177726f24d73
Signed-off-by: Jon Mason <jon.mason@arm.com>
The previous patch broke for qemuarm64-sbsa, ebcause they share the same
defconfig patch but now the upstream kernel SHAs are different. Change
them to have the same SHAs.
Also, the previous patch lost the patch header. So re-add that.
Signed-off-by: Jon Mason <jon.mason@arm.com>
Upstream kernel is now being patched, which prevents the patch being
fixed here from applying cleanly. Rebase it on top of the existing one
to resolve the issue.
Signed-off-by: Jon Mason <jon.mason@arm.com>
Abstract away all of the things preventing the current setup from
working on only internal, arm64 build hardware.
Change-Id: Ib8d0e8e76602d4553e044520a91349015b1aa19b
Signed-off-by: Jon Mason <jon.mason@arm.com>
Use the KAS docker image provided by the KAs project for Gitlab CI.
This allows for the external (non-Arm Corp) users/developers to run
Gitlab CI.
Change-Id: I9fee9a0d571e3fd60862d4ccd36176f9e583fc91
Signed-off-by: Jon Mason <jon.mason@arm.com>
Because of how the kernel class searches for files any changes to
FILESEXTRAPATHS should be done in an override so it doesn't potentially
impact unrelated builds.
Issue spotted by running yocto-check-layer.
Change-Id: I3e915a0cafc850d4b2594b655a849977d389465a
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Jon Mason <jon.mason@arm.com>
Because of how the kernel class searches for files any changes to
FILESEXTRAPATHS should be done in an override so it doesn't potentially
impact unrelated builds.
Issue spotted by running yocto-check-layer.
Change-Id: Id3b741d184a024d0cc6d2d5031e150a8f0ae4b0d
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Jon Mason <jon.mason@arm.com>
This recipe is for TC0, so set COMPATIBLE_MACHINE appropriately.
This is both logically correct, and fixes a Yocto Compatible test failure
where tc0-artifacts-image isn't buildable for arbitrary machines.
Change-Id: I6381fc08076d4ddea254f7efc84f90c4a7f65d26
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Jon Mason <jon.mason@arm.com>
The following patch has been backported to kernel 5.10.30:
0001-xen-evtchn-Change-irq_info-lock-to-raw_spinlock_t.patch
Issue-Id: SCM-2307
Signed-off-by: Peter Hoyes <Peter.Hoyes@arm.com>
Change-Id: I9cef017b60891780176dff944e3eca5986746d8a
Signed-off-by: Jon Mason <jon.mason@arm.com>
This patch enables coresight to work with n1sdp c2c profile.
Change-Id: Id3a5f92cc1f99cd907111ea858aad4efe561179e
Signed-off-by: Khasim Syed Mohammed <khasim.mohammed@arm.com>
Signed-off-by: Jon Mason <jon.mason@arm.com>
meta-atp layer provides support for building AMBA Adaptive Traffic
Profiles (ATP) Engine. It provides the following recipes:
- ATP Engine native standalone build.
- ATP Engine with gem5 as host platform.
- ATP Linux kernel modules.
- ATP Linux user API.
- ATP Linux tests.
The layer provides a "gem5-atp-arm64" machine with ATP device and
adapter support.
Change-Id: Ib86c7502d62d5707d0d4bbdd7d179f231cf96f57
Signed-off-by: Adrian Herrera <adrian.herrera@arm.com>
Signed-off-by: Jon Mason <jon.mason@arm.com>
We don't test this, and don't expect it to work, so don't claim it does.
Change-Id: I045930e690edba5a5b0b8cb810130c8c6733623f
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Jon Mason <jon.mason@arm.com>
Add the newly added repo dir to the disk usage calculation and add the
ability to remove each of the persistent directories.
Change-Id: Ib922ad42c62efdeccf01851ac751742ed67748ae
Signed-off-by: Jon Mason <jon.mason@arm.com>
Added quickstart instructions on how to build a BSP evaluation image using kas.
Updated FVP naming convention as well as information about where to download
and how to run the FVP.
Signed-off-by: Diego Sueiro <diego.sueiro@arm.com>
Change-Id: Ia6056194ed23d6e38769a3e300eadf77fc41beb2
Signed-off-by: Jon Mason <jon.mason@arm.com>
The kas/fvp-baser-aemv8r64-bsp.yml is intended to be used as an evaluation
build for the BSP components.
Signed-off-by: Diego Sueiro <diego.sueiro@arm.com>
Change-Id: Idce501224f4c8fbd6c53dc318db73dcd3100b57b
Signed-off-by: Jon Mason <jon.mason@arm.com>
Since meta-virtualization master branch bumped to 4.15+stable we need to force
the 4.14+stable until we validate the new version.
Issue-Id: SSCM-2307
Signed-off-by: Diego Sueiro <diego.sueiro@arm.com>
Change-Id: Id204314af9c87615d88dfc60702867380225b491
Signed-off-by: Jon Mason <jon.mason@arm.com>
Integration of OP-TEE in the u-boot image is done with `TEE=tee.elf`,
so this build artifact must be exported.
U-boot integration can now be done in a BSP layer with something like
this in `u-boot_%.bbappend`:
# OP-TEE, dependent on "optee" DISTRO_FEATURES
OPTEE_OEMAKE ?= " TEE=${DEPLOY_DIR_IMAGE}/optee/tee.elf"
EXTRA_OEMAKE_append = " ${PACKAGECONFIG_CONFARGS}"
PACKAGECONFIG[optee] = "${OPTEE_OEMAKE},,optee-os"
PACKAGECONFIG_append = " ${@bb.utils.filter('DISTRO_FEATURES', 'optee', d)}"
Signed-off-by: Yann Dirson <yann@blade-group.com>
Signed-off-by: Jon Mason <jon.mason@arm.com>
Hardknott has released and upstream oe-core master has diverged. We will
also be releasing shortly so track hardknott not master for the CI.
Change-Id: I68f8b1c4cc5ac0686c3db9259b44d16f367d82d6
Signed-off-by: Ross Burton <ross.burton@arm.com>
The files in kas/ are not generic Kas files, but instead designed
specifically and solely around the CI system.
Change-Id: I30082392ad2231a4c1c41e54a292595adf81715b
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Jon Mason <jon.mason@arm.com>
We previously disabled uninative[1] because it broke builds in the
Docker containers. This has now been fixed in oe-core with uninative 3.0
so this workaround can be removed.
[1] e5523d626f
Change-Id: I40975eb46737e66dab9f9b8cc63a9283d79918fb
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Jon Mason <jon.mason@arm.com>
Aside from diverging from upstream, appending such a change it at the end of
oe_runmake makes it hard to override it in a bbappend.
This value does not seem to be inherited in TA builds, and
eg. optee-examples do use the the values set in their individual
Makefiles. Setting this to 0 however seems to cause the TA traces not
to be relayed to the console, so the examples end up less
self-illustrative than they should.
This patch restores the upstream choice, while allowing downstream layers to
choose to set it to zero if they wish to do so.
Signed-off-by: Yann Dirson <yann@blade-group.com>
Signed-off-by: Jon Mason <jon.mason@arm.com>
This is more FHS-conformant, and allows tee-supplicant to work on a
readonly rootfs setup (although then it uses volatile storage by
default, and it is still a matter of distro policy how to arrange for
that storage to be persistent in a readonly setup).
Signed-off-by: Yann Dirson <yann@blade-group.com>
Suggested-by: Ricardo Salveti <ricardo@foundries.io>
Signed-off-by: Jon Mason <jon.mason@arm.com>
Integration of OP-TEE in the u-boot image is done with `TEE=tee.elf`,
so this build artifact must be exported.
U-boot integration can now be done in a BSP layer with something like
this in `u-boot_%.bbappend`:
# OP-TEE, dependent on "optee" DISTRO_FEATURES
OPTEE_OEMAKE ?= " TEE=${DEPLOY_DIR_IMAGE}/optee/tee.elf"
EXTRA_OEMAKE_append = " ${PACKAGECONFIG_CONFARGS}"
PACKAGECONFIG[optee] = "${OPTEE_OEMAKE},,optee-os"
PACKAGECONFIG_append = " ${@bb.utils.filter('DISTRO_FEATURES', 'optee', d)}"
Signed-off-by: Yann Dirson <yann@blade-group.com>
Signed-off-by: Jon Mason <jon.mason@arm.com>
Recent versions of OP-TEE perfectly build with pycryptodome, no need for
the pycryptodomex transition package any more.
Signed-off-by: Yann Dirson <yann@blade-group.com>
Reviewed-by: Denys Dmytriyenko <denis@denix.org>
Signed-off-by: Jon Mason <jon.mason@arm.com>
Ross Burton
Jon Mason
Ross Burton
Richard Neill
Diego Sueiro
Anders Dellien
Peter Hoyes
Khasim Mohammed
Adrian Herrera
Yann Dirson