Age | Commit message (Collapse) | Author |
|
For some reason the kas 3.2.1 container fails:
No such file or directory: '/builds/engineering/yocto/meta-zephyr/ci/ci/base.yml'
Note the repeated /ci/, which is wrong.
Pin the kas container to 3.2 for now until this is resolved.
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Jon Mason <jon.mason@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
Recent commits have CVE-2022-2741 fixed.
Also backported CVE-2022-2993 fix.
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
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
Signed-off-by: Peter Hoyes <Peter.Hoyes@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
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.
Signed-off-by: Peter Hoyes <Peter.Hoyes@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
Signed-off-by: Peter Hoyes <Peter.Hoyes@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
Tag all jobs with the DEFAULT_TAG variable so each instance can control
what tags the jobs have.
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Jon Mason <jon.mason@arm.com>
Signed-off-by: Peter Hoyes <Peter.Hoyes@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
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 allows for
variables to be overridden by default. So, we can give it a default
value of NULL/empty and have everything work internally and externally
by default.
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Jon Mason <jon.mason@arm.com>
Signed-off-by: Peter Hoyes <Peter.Hoyes@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
Signed-off-by: Jon Mason <jon.mason@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
Signed-off-by: Jon Mason <jon.mason@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
Signed-off-by: Jon Mason <jon.mason@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
Signed-off-by: Jon Mason <jon.mason@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
Signed-off-by: Jon Mason <jon.mason@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
Signed-off-by: Jon Mason <jon.mason@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
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
pick up the Zephyr binary from the sysroot instead of
DEPLOY_DIR_IMAGE.
* It may sometimes make sense to install the binaries in a Linux
filesystem (e.g. to be run by a hypervisor).
* OE-core's QA checks run on the packaged binaries.
There are currently two QA checks that fail, so add these to INSANE_SKIP
for now.
Signed-off-by: Peter Hoyes <Peter.Hoyes@arm.com>
Signed-off-by: Jon Mason <jon.mason@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
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, which is confusingly named if your application
isn't a "sample".
Do some minor refactoring to untangle the above. Now:
* zephyr-sample.inc depends on zephyr-image.inc
* zephyrtest.bbclass inherits testimage.
* Out-of-tree Zephyr apps can include zephyr-image.inc
Additionally, remove QEMU_BIN_PATH, as recent Zephyr versions now pick
up the QEMU binary automatically from PATH.
Signed-off-by: Peter Hoyes <Peter.Hoyes@arm.com>
Signed-off-by: Jon Mason <jon.mason@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
This looks historical and is no longer required for the tested builds.
Signed-off-by: Peter Hoyes <Peter.Hoyes@arm.com>
Signed-off-by: Jon Mason <jon.mason@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
Signed-off-by: Jon Mason <jon.mason@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
zephyr-openthread-rcp support was recently added to
nrf52840-mdk-usb-dongle and nrf52840dk-nrf52840. Add this to the
targets for both machines, which necessitates adding a target entry
for nrf52840-mdk-usb-dongle.
Signed-off-by: Jon Mason <jon.mason@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
This makerdiary board can be a fallback option for Oniro's gateway-blueprint
I've been tested it myself along my single arduino-nano node
Origin: https://gitlab.eclipse.org/eclipse/oniro-core/meta-zephyr/-/merge_requests/22
Relate-to: https://gitlab.eclipse.org/eclipse/oniro-blueprints/transparent-gateway/meta-oniro-blueprints-gateway/-/issues/6
Relate-to: https://gitlab.eclipse.org/pcoval/oniro-presentations/-/wikis/openthread
Forwarded: https://lists.yoctoproject.org/g/yocto/search?q=posterid:6590488
Signed-off-by: Philippe Coval <philippe.coval@astrolabe.coop>
Signed-off-by: Philippe Coval <philippe.coval.ext@huawei.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
It was tested using zephyr-blinky and deployed manually using:
udisksctl mount -b "/dev/disk/by-label'FRDM-KW41ZJ"
Relate-to: https://gitlab.eclipse.org/pcoval/oniro-presentations/-/wikis/openthread
Forwarded: https://lists.yoctoproject.org/g/yocto/search?q=posterid:6590488
Signed-off-by: Philippe Coval <philippe.coval@astrolabe.coop>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
Signed-off-by: Jon Mason <jon.mason@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
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 "zephyr.hex" -c -f 0xADA52840
- and then copy to mounted "/dev/disk/by-label/MDK-DONGLE"
Support of unfree flashing tools might be added later (once double verified)
Forwarded: https://lists.yoctoproject.org/g/yocto/message/58142
Relate-to: https://gitlab.eclipse.org/eclipse/oniro-blueprints/transparent-gateway/meta-oniro-blueprints-gateway/-/issues/6
Relate-to: https://wiki.makerdiary.com/nrf52840-mdk/zephyr/
Relate-to: https://gitlab.eclipse.org/pcoval/oniro-presentations/-/wikis/openthread
Signed-off-by: Philippe Coval <philippe.coval@astrolabe.coop>
Signed-off-by: Philippe Coval <philippe.coval.ext@huawei.com>
Tested-by: Jon Mason <jon.mason@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
This Nordic reference design can be a fallback option for
Oniro's gateway-blueprint
I've been tested it myself along my single arduino-nano node
Origin: https://gitlab.eclipse.org/eclipse/oniro-core/meta-zephyr/-/merge_requests/22
Relate-to: https://gitlab.eclipse.org/eclipse/oniro-blueprints/transparent-gateway/meta-oniro-blueprints-gateway/-/issues/6
Signed-off-by: Philippe Coval <philippe.coval@astrolabe.coop>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
Update the machines using cortex m4s 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 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>
|
|
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>
|
|
The patch dtc.patch used by 2.7.3 has been accepted upstream, so it is
now a Backport.
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>
|
|
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>
|
|
003de78ce0 release: Zephyr 2.7.3
9502d500b6 release: security: Notes for 2.7.3
2a88e08296 release: update v2.7.3 release notes
e1ee34e55c drivers: sensor: sm351lt: Fix global thread triggering bug
2ad1ef651b Bluetooth: host: Fix L2CAP reconfigure response with invalid CID
089675af45 Bluetooth: host: Fix L2CAP reconfigure response with invalid MTU
03ff0d471e net: route: Fix pkt leak if net_send_data() fails
cd96136bcb boards: nucleo_wb55rg: Fix documentation about BLE binary compatibility
567fda57df tests: drivers: can: api: add test for RTR filter matching
b14f356c96 drivers: can: loopback: check frame ID type and RTR bit in filters
874d77bc75 drivers: can: mcux: flexcan: fix handling of RTR frames
ec0befb938 drivers: can: mcan: acknowledge all received frames
273e90a86f scripts: release: list_backports: use older python dict merge method
59dc65a7b4 ci: backports: check if a backport PR has a valid issue
8ff8cafc18 scripts: release: list_backports.py
ba07347b60 scripts: release: use GITHUB_TOKEN and start_date in scripts
e423902617 tests: posix: pthread: test for pthread descriptor leaks
018f836c4d posix: pthread: consider PTHREAD_EXITED state in pthread_create
f4466c4760 tests: cpp: cxx: Add qemu_cortex_a53 as integration platform
9a5cbe3568 tests: cpp: cxx: Test with various types of libc
5b7b15fb2d tests: cpp: cxx: Add dynamic memory availability test for static init
e5a92a1fab tests: cpp: cxx: Add static global constructor invocation test
74f0b6443a lib: libc: newlib: Initialise libc heap during POST_KERNEL phase
6c16b3492b lib: libc: minimal: Initialise libc heap during POST_KERNEL phase
1831431bab lib: posix: semaphore: use consistent timebase in sem_timedwait
765f63c6b9 cmake: remove xtensa workaround in Zephyr toolchain code.
062306fc0b cmake: zephyr toolchain code cleanup
8fcf7f1d78 Revert "cmake: Zephyr sdk backward compatibility with 0.11.1 and 0.11.2"
f06b3d922c Bluetooth: Controller: Fix PHY update for unsupported PHY
b75c012c55 drivers: spi: stm32 spi with dma must enable cs after periph
1efe6de3fe drivers: i2c: Fix infinite recursion in driver unregister function
39270ed4a0 Bluetooth: Mesh: Fix segmentation when sending proxy message
81ffa550ee Bluetooth: Mesh: Check SegN when receiving Transaction Start PDU
8c2965e017 Bluetooth: Mesh: add check for rx buffer overflow in pb adv
7aa38b4ac8 drivers: can: m_can: fix alignmed issues
6dd320f791 release: update v2.7.2 release notes
ecac165d36 logging: shell: fix shell stats null pointer dereference
132d90d1bc tests/bluetooth/tester: Refactor Read UUID callback
58356313ac coredump: adjust mem_region find in gdbstub
99cfd3e4d7 Bluetooth: Controller: Fix per adv scheduling issue
780588bd33 edac: ibecc: Add support for EHL SKU13, SKU14, SKU15
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
Tested-by: Jon Mason <jon.mason@arm.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>
|
|
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>
|
|
Signed-off-by: Jon Mason <jon.mason@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
Signed-off-by: Jon Mason <jon.mason@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
Signed-off-by: Jon Mason <jon.mason@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>
|