aboutsummaryrefslogtreecommitdiffstats
path: root/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
AgeCommit message (Collapse)Author
2020-10-21zephyr: use TCLIBC=newlib directlyRoss Burton
Instead of setting TCLIBC=baremetal and then adding newlib in various places, just set TCLIBC=newlib directly. This also means we can use the standard DEPENDS instead of reinventing them. Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
2020-09-23zephyr-kernel: add Zephyr RTOS version 2.3.0 supportMah, Yock Gen
Signed-off-by: Mah, Yock Gen <yock.gen.mah@intel.com> Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
2020-09-22zephyr-kernel: Add python dependenciesJon Mason
Zephyr refuses to compile due to missing python dependencies. Signed-off-by: Jon Mason <jon.mason@arm.com> Signed-off-by: Ross Burton <ross.burton@arm.com>
2019-12-09zephyr-helloworld: code clean upNaveen Saini
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
2019-12-09zephyr-kernel: add Zephyr RTOS version 2.0.0 supportNaveen Saini
Release notes: https://github.com/zephyrproject-rtos/zephyr/releases/tag/zephyr-v2.0.0 Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
2017-03-17zephyr-kernel-common.inc: modify ZEPHYR_MAKE_ARGSJuro Bystricky
Pass ARCH as well. Remove V=1, if needed can be added in a specific recipe. Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
2017-02-05zephyrtest.bbclass: refactorJuro Bystricky
Only keep code/variables related to individual test/package names. Moved ZEPHYR_TEST_SRCDIR into zephyr-kernel.inc as it is zephyr kernel version specific. Moved ZEPHYR_MAKE_OUTPUT into zephyr-kernel-common.inc as it is as it is not zephyr test specific but applicable to all zephyr images. Generate additional files expected by testimage.bbclass: testdata.json and a dummy manifest file Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
2017-01-30zephyr-kernel-common.inc: also build qemus if neededJuro Bystricky
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>
2017-01-19meta-zephyr: newlib supportJuro Bystricky
This patch adds newlib libraries for cortex-m3, x86, IAMCU and ARC toolchains. [YOCTO#10662] Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
2017-01-18zephyr.bbclass: support for image configurationJuro Bystricky
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>
2017-01-10meta-zephyr: Select BOARD via MACHINEJuro Bystricky
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>
2017-01-10zephyr-kernel: refactor common codeJuro Bystricky
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>