Also build qemus if a recipe is built for a MACHINE=qemuXXX.
Allow inheriting classes based on recipe context.
Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
Added support for Zephyr qemu-nios2 BOARD.
Nios2 CPU is not supported natively by upstream QEMU,
so a Nios2 specific patch needs to be applied.
[YOCTO#10660]
Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
New class to support commands such as:
$ MACHINE=xxx bitbake yyy -c menuconfig
$ MACHINE=xxx bitbake yyy -c devshell
Kernel options are typically configured via menuconfig.
The file "prj.conf" must be edited manually, hence the need for devshell.
Once in devshell, user can use their favorite editor to edit the file.
For proper operation, these two variables need to be set in
recipes:
ZEPHYR_SRC_DIR : path to the source, typically place with prj.conf
ZEPHYR_BASE: Zephyr kernel tree location
[YOCTO#10657]
Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
Deploy both binary and ELF images in order to make
it easier to flash the image on an actual board, such as Arduino-101.
(Some flashing tools require binary image)
Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
Added support for Zephyr arduino_101_sss board (ARC core).
The support requires ARC toolchain.
Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
Added support for ARC toolchains: binutils, gcc, libgcc.
These are not upstreamed, but taken from Symantec ARC repos.
[YOCTO#10659]
Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
The meaning of BOARD in Zephyr environment is equivalent to MACHINE
in Yocto environment.
Specifying MACHINE will implicitly determine cross-compiler toolchain as well.
There is 1:1 correspondence between Zephyr BOARD and Yocto MACHINE so
a lookup table BOARD:MACHINE may be needed in the future, presently all
that is required is to convert "-" to "_". (Dash to undersocre)
This means that in order to support a new Zephyr board, we simply need to
create a corresponding MACHINE.conf file.
[YOCTO#10894]
Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
Several changes to simplify recipes by refactoring
common code. The code common to all Zephyr builds is
now in the file "zephyr-kernel-common.inc".
Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
Various changes to properly handle QEMU for Cortex M3.
This was solved by creating a new MACHINE qemu-cortex-m3.
Specifying MACHINE=qemu-cortex-m3 will select proper tuning
for the cross-compiler.
Typical usage:
$ MACHINE=qemu-cortex-m3 bitbake zephyr-philosophers
Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
This recipe obtains the Zephyr source code tree.
The idea is to use this tree for out-of-tree Zepyhyr images via
DEPENDS += "zephyr-kernel-src"
Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
Setting ZEPHYR_GCC_VARIANT="yocto" will result in images being
built by our own Makefile: Makefile.toolchain.yocto
The Makefile already contains LIB_INCLUDE_DIR definition, so it
can be removed from this recipe.
Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
Setting ZEPHYR_GCC_VARIANT="yocto" will result in images being
built by our own Makefile: Makefile.toolchain.yocto
The Makefile already contains LIB_INCLUDE_DIR definition, so it
can be removed from this file.
Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
Zephyr RTOS uses the environmental variable ZEPHYR_GCC_VARIANT to
determine which Makefile to use to build images. This allows different
Makefiles for different toolchains, so the toolchains can co-exist.
Rather than patching the included Makefile.toolchain.zephyr, we use
our own file Makefile.toolchain.yocto. This Makefile will be used as
long as Zephyr recipes set:
export ZEPHYR_GCC_VARIANT="yocto"
(Also removed some BOARD definitions)
Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
Removed the need for "poky.conf", as a consequence
some variables previously defined via poky.conf needed to
be re-defined: TARGET_VENDOR, TCLIBCAPPEND
Moved here default BOARD definitions.
Defined DISTRO_VERSION.
Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
Do not prepend 'test' to test programs.
(Don't assume all test programs names begin with 'test_')
Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
Remove tests that fail because QEMU for ARM does not emulate
CortexM3 BASEPRI register functionality.
Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
Cortex-M3 is not supported natively by oe-embedded, so we need to
do it here. With these changes it should be possible to run:
To build all Zephyr tests:
$ MACHINE=qemuarm bitbake zephyr-kernel-test-all
$ MACHINE=qemuarm bitbake zephyr-kernel-test-all -ctestimage
To build "philosophers" sample:
$ MACHINE=qemuarm bitbake zephyr-philosophers
Once built, you can run the created "philosophers" image in qemu
(at this point the various paths have to be entered manually):
$ ./tmp/sysroots/x86_64-linux/usr/bin/qemu-system-arm \
-kernel ./tmp/deploy/images/qemuarm/philosophers.elf \
-cpu cortex-m3 -machine lm3s6965evb -nographic -vga none
Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
Numerous changes to allow building and running various
Zephyr tests using Zephyr release 1.6 and Yocto master distro
(commit 3676601335b4673e3572d5a9987a351f0bb44bcb and later)
Work in progress.
Notable changes:
1. Zephyr 1.6 does not support the concept of nano and micro kernel
anymore.
2. Location of various tests have changed
3. Changes due to subtle python3/python2 differences
4. Zephyr Makefile changes (including renaming)
5. Improved failed test detection
6. Remove patch files no longer needed
With these changes, it is now possible to run Zephyr test suite and
Zephyr sample programs. Currently only x86 CPUs are supported, with
additional CPU support coming in the near future, in particular
support for ARM Cortex-M3 CPUs
Prerequisites:
Modify local conf by adding:
DISTRO="zephyr"
MACHINE?="qemux86"
Modify bblayers.conf by adding "meta-zephyr" to BBLAYERS
To build all Zephyr tests:
$ bitbake zephyr-kernel-test-all
To test all built test images:
$ bitbake zephyr-kernel-test-all -ctestimage
You can also build and test an individual test. This is done by appending
the actual test name to the "zephyr-kernel-test", for example:
$ bitbake zephyr-kernel-test-test_sleep
$ bitbake zephyr-kernel-test-test_sleep -ctestimage
It is also possible to build Zephyr sample programs. Included is a sample recipe
that builds the Zephyr "philosophers" sample:
$ bitbake zephyr-philosophers
Once built, you can run the created "philosophers" image in qemu (at this point
the various paths have to be entered manually):
$ ./tmp/sysroots/x86_64-linux/usr/bin/qemu-system-i386 \
-kernel ./tmp/deploy/images/qemux86/philosophers.elf \
-nographic -machine type=pc-0.14 -display none -clock dynticks \
-no-acpi -balloon none
Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
