Update the qemu-cortex-m3 machine to use the OE tune file, and remove
the duplicate one locally.
Signed-off-by: Jon Mason <jon.mason@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Update the parameters being run in qemu to get more stable results.
Values taken from zephyr qemu. Also, use QB_GRAPHICS instead of
QB_OPT_APPEND for the relevant places.
Signed-off-by: Jon Mason <jon.mason@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Make the changes necessary to get testimage working and run it as part
of CI
Signed-off-by: Jon Mason <jon.mason@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
For a given release tag, ZEPHYR_MODULES is constant. It is therefore now
populated by the generate-version.py script, the output of which is
stored in the repository, so the build-time logic to populate
ZEPHYR_MODULES is no longer needed.
Remove the do_get_zmods task, but retain the Python dependencies which
are still required by Python scripts in the Zephyr repository that are
trigerred by CMake.
The above means that West is now only required as a host dependency to
run generate-version.py, so remove the West Yocto recipe.
Signed-off-by: Peter Hoyes <Peter.Hoyes@arm.com>
Tested-by: Jon Mason <jon.mason@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
This commit uses the output of
meta-zephyr-core/scripts/generate-version.py for both the 2.7.3 and
3.1.0 versions.
Rename a patch for for v2.7.3 to match the filename expected by the
generated configuration.
Signed-off-by: Peter Hoyes <Peter.Hoyes@arm.com>
Tested-by: Jon Mason <jon.mason@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Add a Python script which can be used to automatically generate
configuration for new Zephyr versions. This script:
* Takes the Zephyr version as a single argument
* Uses the Github API to find the version tag's SHA1
* Uses West as a library to parse the version's manifest file
* Uses a Jinja template to generate a .inc file for the version
* Outputs the .inc file directly into the zephyr-kernel directory
The generated .inc file includes:
* SRCREVs for all modules
* Separate SRC_URI_x variables for each module, to make it easier to
swap out a specific URL for a fork or mirror
* A version-specific SRC_URI, containing only the modules defined in
the release
* A list of the ZEPHYR_MODULES
Signed-off-by: Peter Hoyes <Peter.Hoyes@arm.com>
Tested-by: Jon Mason <jon.mason@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Add an option to build applications using the Zephyr SDK by specifying
ZEPHYR_TOOLCHAIN_VARIANT="zephyr". This mode works with the zephyr or
poky distros (TCMODE is ignored), allowing Zephyr applications to be
built alongside a Linux stack.
Provide a toolchain-specific inc file for the Zephyr SDK, which
configures the dependencies and CMake appropriately.
Add Zephyr toolchain variant to CI configuration for qemu-cortex-a53,
qemu-cortex-m3 and qemu-x86. Update README.txt
Signed-off-by: Peter Hoyes <Peter.Hoyes@arm.com>
Tested-by: Jon Mason <jon.mason@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
The Zephyr SDK (https://github.com/zephyrproject-rtos/sdk-ng) provides
pre-built toolchains for all of Zephyr's supported architectures.
Add a recipe to download SDK v0.14.2, in preparation for adding an
option to build Zephyr applications using this toolchain instead of the
Yocto-built one.
Signed-off-by: Peter Hoyes <Peter.Hoyes@arm.com>
Tested-by: Jon Mason <jon.mason@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Create ZEPHYR_TOOLCHAIN_VARIANT variable with an unchanged default value
of 'yocto'.
To support providing different configuration for different toolchain
variants, require a toolchain-specific inc file.
Create zephyr-toolchain-yocto.inc, and factor out all variables that are
specific to building using the Yocto toolchain.
Signed-off-by: Peter Hoyes <Peter.Hoyes@arm.com>
Tested-by: Jon Mason <jon.mason@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Adopt the jobs-to-kas helper script from meta-arm, which uses Gitlab's
parellel matrix to overlay additional Kas files on top of the base Kas
file (based on $CI_JOB_NAME).
This allows multiple combinations of Kas file overlays to be easily
tested with minimal boilerplate.
Signed-off-by: Peter Hoyes <Peter.Hoyes@arm.com>
Tested-by: Jon Mason <jon.mason@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
The README.txt files at the root and in meta-zephyr-core are identical,
so replace the copy inside meta-zephyr-core with "See ../README.txt" to
remove the need to keep two files in sync.
Add a similar README.txt to meta-zephyr-bsp.
Signed-off-by: Peter Hoyes <Peter.Hoyes@arm.com>
Tested-by: Jon Mason <jon.mason@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
When using West, Zephyr is checked out in a "zephyr" subdirectory of the
working directory. At the moment Zephyr is checked out at the root,
meaning a workaround is required to extract the module information.
In order to remove the workaround, change the Zephyr destsuffix in
SRC_URI and ZEPHYR_BASE. As a result of this change, modify patchdir for
the patches and the path to the LICENSE file.
Signed-off-by: Peter Hoyes <Peter.Hoyes@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Change ${S} -> ${ZEPHYR_BASE} in all application recipes, as Zephyr
might not always be found at the root of the source directory.
Signed-off-by: Peter Hoyes <Peter.Hoyes@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
zephyr-image.inc and zephyr-sample.inc both include
zephyr-kernel-common.inc, which already defines ZEPHYR_BASE. Remove the
redundant definitions.
Also, pass -DZEPHYR_BASE=${ZEPHYR_BASE} instead of ${S} in
EXTRA_OECMAKE.
Signed-off-by: Peter Hoyes <Peter.Hoyes@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
The oeqa code in meta-zephyr-core/lib/ generates __pycache__ files which
pollute the development environment. Add a .gitignore file to
automatically exclude these files from commits.
Signed-off-by: Peter Hoyes <Peter.Hoyes@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Hello World and Philosophers do not have a SUMMARY or DESCRIPTION, so
add these to both recipes.
Signed-off-by: Peter Hoyes <Peter.Hoyes@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
The Zephyr documentation [1] lists 3 "classic samples" that "can be run
on any of the supported platforms": Hello World, Synchronization and
Dining Philosophers. meta-zephyr already includes the first two but not
synchronization so add a recipe for it.
[1] https://docs.zephyrproject.org/3.1.0/samples/classic.html
Signed-off-by: Peter Hoyes <Peter.Hoyes@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
The autotest change allows for the list of targets to be built to be
larger. Add more targets to increase the build coverage of CI.
Unfortunately, there are some platforms that do not build everything.
So, clip those down to those that work for all. Also, there are a few
targets unique to certain platforms. So, expand those to have coverage.
Signed-off-by: Jon Mason <jon.mason@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Trivial change to move stm32mp157c-dk2 to its alphabetical location.
This is relevant because it aligns the file to match the order on the
gilab pipeline entry.
Signed-off-by: Jon Mason <jon.mason@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Warnings are being seen in gitlab of
WARNING - Falling back to file-relative addressing of local include "base.yml"
WARNING - Update your layer to repo-relative addressing to avoid this warning
WARNING - Falling back to file-relative addressing of local include "meta-openembedded.yml"
WARNING - Update your layer to repo-relative addressing to avoid this warning
Make the relevant changes to resolve this issue
Signed-off-by: Jon Mason <jon.mason@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
The fix for the gcc issue has been upstreamed and the workaround is no
longer needed.
Signed-off-by: Jon Mason <jon.mason@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Now that TESTIMAGE_AUTO is available for Zephyr builds, enable it in
ci/testimage.yml and remove the redundant build_and_test base
configuration.
Remove testimage from Nios2 build as it is currently failing.
Signed-off-by: Peter Hoyes <Peter.Hoyes@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
When TESTIMAGE_AUTO is enabled, the do_testimage task is inserted after
do_image_complete and before do_build so that the test suites
automatically run as part of the image build.
However, do_testdata_write is currently constrained to run only before
do_build, so it likely won't execute prior to do_testimage. Change the
"before" constraint to do_testimage do that the testdata is always
generated prior to running the testimage task.
Signed-off-by: Peter Hoyes <Peter.Hoyes@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
newlib fails to compile for nios2 architecture. Work around this by
using glibc instead.
Signed-off-by: Jon Mason <jon.mason@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Nothing in meta-zephyr uses python3-cbor, and as it hasn't had a release
since 2016 everyone using it should move to cbor2.
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
This recipe wasn't actually named *.bb, so it wasn't parsed at all, so
it can't have been used.
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
