From: Peter Hoyes
Runtime validation is currently failing on qemu-cortex-a9 for
undiagnosed reasons. Disable testimage on this machine for now until it
has been fixed.
Signed-off-by: Peter Hoyes
---
.gitlab-ci.yml | 1 -
1 file changed, 1 deletion(-)
diff --git a/.gitlab-ci.yml b/.gitlab
From: Peter Hoyes
Signed-off-by: Peter Hoyes
---
ci/base.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ci/base.yml b/ci/base.yml
index 70adac1..4bf59d1 100644
--- a/ci/base.yml
+++ b/ci/base.yml
@@ -7,7 +7,7 @@ distro: zephyr
defaults:
repos:
-refspec
Hi again Armin,
On 03/05/2023 13:38, Peter Hoyes via lists.yoctoproject.org wrote:
Hi Armin,
On 27/04/2023 16:01, Peter Hoyes via lists.yoctoproject.org wrote:
From: Peter Hoyes
Yocto mickledore introduced the addpylib directive for explicitly adding
layer paths to the PYTHONPATH
Hi Armin,
On 27/04/2023 16:01, Peter Hoyes via lists.yoctoproject.org wrote:
From: Peter Hoyes
Yocto mickledore introduced the addpylib directive for explicitly adding
layer paths to the PYTHONPATH.
Standalone OEQA test suite discovery does not require this directive but
it is required
From: Peter Hoyes
Yocto mickledore introduced the addpylib directive for explicitly adding
layer paths to the PYTHONPATH.
Standalone OEQA test suite discovery does not require this directive but
it is required to import test cases from other layers, e.g. to extend
and modify the test cases
From: Peter Hoyes
Armv7 boards are currently failing with binutils 2.40 if certain
statements are combined on the same line without a semicolon. Introduce
a patch to fix this by inserting a semicolon.
Signed-off-by: Peter Hoyes
---
...x-separator-between-directives-on-sa.patch | 44
From: Peter Hoyes
Re-run the generate-version.py script for 3.3.0 to convert the tag for
zcbor to a SHA.
Signed-off-by: Peter Hoyes
---
.../recipes-kernel/zephyr-kernel/zephyr-kernel-src-3.3.0.inc| 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/meta-zephyr-core/recipes
From: Peter Hoyes
The West manifest in Zephyr 3.3 contains a tag (instead of a SHA) for
zcbor [1]. OE standard practice is to always specifiy revisions using
SHAs, so in the Jinja template, use the new resolve_revision filter to
resolve any tags.
[1]
https://github.com/zephyrproject-rtos
From: Peter Hoyes
To simplify the logic to resolve Git tags to SHAs, and so that it works
with non-Github repositories, use git ls-remote instead of the Github
API.
Make the resolve_revision function available as a Jinja filter and move
the version resolution to the template.
Signed-off
From: Peter Hoyes
Signed-off-by: Peter Hoyes
---
.gitlab-ci.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index d5462a4..2ecf132 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -1,4 +1,4 @@
-image: ghcr.io/siemens/kas/kas:3.2
+image
From: Peter Hoyes
The "yocto" toolchain requires a downstream patch to be carried and
maintained. The upstream "cross-compile" toolchain is equivalent so this
is no longer needed.
Remove the toolchain-specific inc file and the downstream patch.
Signed-off-by: Peter Hoye
From: Peter Hoyes
Zephyr upstream contains CMake configuration for a "cross-compile"
toolchain for "other cross compilers" which works with the Yocto-built
toolchain out-of-the-box, so use this instead of the "yocto" toolchain,
which requires a downstream patch t
From: Peter Hoyes
https://github.com/zephyrproject-rtos/sdk-ng/releases/tag/v0.15.2
Signed-off-by: Peter Hoyes
---
.../zephyr-sdk/{zephyr-sdk_0.15.1.bb => zephyr-sdk_0.15.2.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta-zephyr-core/recipes-devtools/zephyr-
From: Peter Hoyes
Now that v3.3.0 is available, drop support for previous versions.
Rename the downstream patches and drop the backport.
Signed-off-by: Peter Hoyes
---
...ix-SMP-local-keys-check-when-startin.patch | 51
... 0001-3.3-cmake-add-yocto-toolchain.patch} | 0
...y
From: Peter Hoyes
https://github.com/zephyrproject-rtos/zephyr/releases/tag/v3.3.0
Signed-off-by: Peter Hoyes
---
.../zephyr-kernel/zephyr-kernel-src-3.3.0.inc | 239 ++
.../zephyr-kernel/zephyr-kernel-src.inc | 2 +-
2 files changed, 240 insertions(+), 1 deletion
From: Peter Hoyes
Certain SRC_URI_* variables may collide with other recipes, e.g.
SRC_URI_TRUSTED_FIRMWARE_A. Namespace these variables under
SRC_URI_ZEPHYR so that the SRC_URIs of Zephyr modules can be
independently tweaked from local.conf or the environment.
Signed-off-by: Peter Hoyes
From: Peter Hoyes
Tag all jobs with the DEFAULT_TAG variable so each instance can control
what tags the jobs have.
Signed-off-by: Ross Burton
Signed-off-by: Jon Mason
Signed-off-by: Peter Hoyes
---
.gitlab-ci.yml | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git
From: Peter Hoyes
The Kas container needs to use the entrypoint as that is where the user
changes from root to a normal user.
Also set the KUBERNETES_CPU_REQUEST to the variable CPU_REQUEST as this
needs to be tuned per-deployment.
CPU_REQUEST has no value outside of Arm Corp. Gitlab CI
From: Peter Hoyes
The packaging step includes post-processing of elf files using objcopy
and strip from the Yocto toolchain. When using the Zephyr SDK, the Yocto
toolchain is explicitly not built so it is not possible to run these
steps. Therefore, inhibit them in zephyr-toolchain-zephyr.inc
From: Peter Hoyes
The inclusion of the Zephyr version-specific .inc file is currently
using a local include. Change to be layer-relative to support including
files in other layers.
Change to use 'require' instead of 'include' so that an earlier error is
printed if the file does not exist
From: Peter Hoyes
Signed-off-by: Peter Hoyes
---
ci/base.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ci/base.yml b/ci/base.yml
index 70adac1..7b2203e 100644
--- a/ci/base.yml
+++ b/ci/base.yml
@@ -7,7 +7,7 @@ distro: zephyr
defaults:
repos:
-refspec
From: Peter Hoyes
Tag all jobs with the DEFAULT_TAG variable so each instance can control
what tags the jobs have.
Signed-off-by: Ross Burton
Signed-off-by: Jon Mason
Signed-off-by: Peter Hoyes
---
.gitlab-ci.yml | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git
From: Peter Hoyes
The Kas container needs to use the entrypoint as that is where the user
changes from root to a normal user.
Also set the KUBERNETES_CPU_REQUEST to the variable CPU_REQUEST as this
needs to be tuned per-deployment.
CPU_REQUEST has no value outside of Arm Corp. Gitlab CI
From: Peter Hoyes
OE-core 4901c9d471cab99d52876842980222ce271b66e4 "base: Switch to use
addpylib directive and BB_GLOBAL_PYMODULES" means that ${LAYERDIR}/lib
is no longer searched by default when loading test controllers.
meta-zephyr-core defines some custom test controllers for te
From: Peter Hoyes
The packaging step includes post-processing of elf files using objcopy
and strip from the Yocto toolchain. When using the Zephyr SDK, the Yocto
toolchain is explicitly not built so it is not possible to run these
steps. Therefore, inhibit them in zephyr-toolchain-zephyr.inc
From: Peter Hoyes
The inclusion of the Zephyr version-specific .inc file is currently
using a local include. Change to be layer-relative to support including
files in other layers.
Change to use 'require' instead of 'include' so that an earlier error is
printed if the file does not exist
From: Peter Hoyes
Tag all jobs with the DEFAULT_TAG variable so each instance can control
what tags the jobs have.
Signed-off-by: Ross Burton
Signed-off-by: Jon Mason
Signed-off-by: Peter Hoyes
---
.gitlab-ci.yml | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git
From: Peter Hoyes
The Kas container needs to use the entrypoint as that is where the user
changes from root to a normal user.
Also set the KUBERNETES_CPU_REQUEST to the variable CPU_REQUEST as this
needs to be tuned per-deployment.
CPU_REQUEST has no value outside of Arm Corp. Gitlab CI
From: Peter Hoyes
Install the Zephyr binaries to ${D}/firmware prior to copying them to
${DEPLOYDIR}.
Implementing do_install has three advantages:
* In use-cases when the Zephyr application is not the final artifact
(e.g. when signing or using additional firmware), other recipes can
From: Peter Hoyes
At the moment:
* zephyr-image.inc depends on zephyr-sample.inc, which doesn't really
make sense.
* zephyr-image.inc inherits testimage, even though it may not be
required.
* Out-of-tree Zephyr apps have to include zephyr-sample.inc in order to
deploy the binaries
Hi,
One minor comment below.
On 23/09/2022 09:27, philippe.coval via lists.yoctoproject.org wrote:
From: Philippe Coval
It was tested with zephyr-openthread-rcp
along Oniro's IoT gateway blueprint
For the record deployment was done manually:
- Click on device button
- uf2conv.py
From: Peter Hoyes
The patch dtc.patch used by 2.7.3 has been accepted upstream, so it is
now a Backport.
Signed-off-by: Peter Hoyes
---
meta-zephyr-core/recipes-kernel/zephyr-kernel/files/dtc.patch | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-zephyr-core/recipes
From: Peter Hoyes
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
From: Peter Hoyes
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
---
...y-generation-issue-in-cross
From: Peter Hoyes
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
From: Peter Hoyes
This patch chain has been developed on top of the 2.7.3 upgrade patch.
Add a script, generate-version.py, which can be used to automatically
generate configuration for new Zephyr versions. Regenerate
configuration for 2.7.3 and 3.1.0 using this script.
This script includes
From: Peter Hoyes
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-sp
From: Peter Hoyes
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
From: Peter Hoyes
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
From: Peter Hoyes
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
From: Peter Hoyes
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
---
m
On 16/08/2022 14:02, Peter Hoyes wrote:
On 16/08/2022 13:42, Bruce Ashfield via lists.yoctoproject.org wrote:
On Tue, Aug 16, 2022 at 8:34 AM Peter Hoyes wrote:
Hi,
We have discovered an issue in yocto-kernel-tools that only arises
with a certain combination of host build paths. Some steps
On 16/08/2022 13:42, Bruce Ashfield via lists.yoctoproject.org wrote:
On Tue, Aug 16, 2022 at 8:34 AM Peter Hoyes wrote:
Hi,
We have discovered an issue in yocto-kernel-tools that only arises with a
certain combination of host build paths. Some steps to reproduce are as follows:
Create
Hi,
We have discovered an issue in yocto-kernel-tools that only arises with
a certain combination of host build paths. Some steps to reproduce are
as follows:
1. Create directories /build and /work at the root of the filesystem
(e.g. in a container or VM)
2. Checkout poky at /work/poky
3.
From: Peter Hoyes
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
From: Peter Hoyes
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
---
meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-blinky.bb | 2 +-
.../recipes-kernel/zephyr-kernel/zep
From: Peter Hoyes
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
---
meta-zephyr-core
From: Peter Hoyes
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
---
.gitignore | 1 +
1 file changed, 1 insertion(+)
create mode
From: Peter Hoyes
Signed-off-by: Peter Hoyes
---
ci/base.yml | 1 +
1 file changed, 1 insertion(+)
diff --git a/ci/base.yml b/ci/base.yml
index f85d780..70adac1 100644
--- a/ci/base.yml
+++ b/ci/base.yml
@@ -36,3 +36,4 @@ target:
- zephyr-helloworld
- zephyr-kernel-test-all
- zephyr
From: Peter Hoyes
Hello World and Philosophers do not have a SUMMARY or DESCRIPTION, so
add these to both recipes.
Signed-off-by: Peter Hoyes
---
.../recipes-kernel/zephyr-kernel/zephyr-helloworld.bb| 4
.../recipes-kernel/zephyr-kernel/zephyr-philosophers.bb | 5 +
2
From: Peter Hoyes
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 recip
From: Peter Hoyes
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
From: Peter Hoyes
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
---
.gitlab-ci.yml | 17
53 matches
Mail list logo
