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>
When running an up-to-date userspace component, like otbr-agent or
ot-daemon, with Thread 1.2 enabled we need a firmware matching this
capabilities.
Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
These patches are not being applied and not required any more.
Already part of zephyr 2.7.1 and zephyr 3.0.0
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
All the LAYERSERIES_COMPAT versions provide this recipe in oe-core.
Also, west seems to only depend on 0,26 which is provided even in
dunfell.
Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Add CVE_PRODUCT override to fix a lookup problem when performing cve-check,
if not setted it will search for the recipe name, that in this case depends
on the recipe used to build zephyr (eg. zephyr-philosophers)
Signed-off-by: Davide Gardenal <davide.gardenal@huawei.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
v2.7.1 is the LTS release and we'll be adding support fr v3.0.0 in the
subsequent patch. Drop support for v2.6.1.
Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@huawei.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
This builds the sample for the radio co-processor firmware with a specific
set of overlays to work over USB transport.
Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Reuse the same code that generates zephyr samples for building tests.
This allows us to generate .bin files in all cases.
Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@huawei.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Instead of looking in PATH on the host to find bossac we now depend on the
native variant we build and set the path to our yocto build tool.
Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>
Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
This native recipe will be used to streamline the flashing of out
Arduino Nano 33 BLE target. Until now we have pointed to the full
Arduino IDE to get it installed and setting the PATH correctly before
any flashing would work. Having the tool supplied under the hood for
flashing will simplify documentation and support.
Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>
Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Some of these recipes ended up overriding the ZEPHYR_MODULES we set
elsewhere. As well, zephyr-lvgl tries to apply a patch we already apply.
Signed-off-by: Eilís Ní Fhlannagáin <elizabeth.flanagan@huawei.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Trying to handwrite all the machine defintions in zephyr would be an
enormous task. This commit creates a patch to zephy which abuses cmake
to output machine definitions for OE.
Not all machines can be generated this way and meta will need to be in
COREBASE/meta. It's mainly a prototype tool at this point to be able to
add all the machines this patch can figure out to meta-zephyr-bsp.
The hope is at a future date we can use it to autogenerate all the
machines we can from zephyr and use them in meta-zephyr-bsp.
Signed-off-by: Eilís Ní Fhlannagáin <elizabeth.flanagan@huawei.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Currently meta-zephyr only checks out a subset of the kernel source.
With the addition of being able to generate machine configs from
zephyr source, we need to be able to have the complete source if we
don't want things to break badly.
Signed-off-by: Eilís Ní Fhlannagáin <elizabeth.flanagan@huawei.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
