Age | Commit message (Collapse) | Author |
|
zephyr can be build for 'acrn' with following configuration:
MACHINE = "intel-x86-64"
ZEPHYR_BOARD = "acrn"
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
User need to specify board value to ZEPHYR_BOARD in local.conf
ZEPHYR_BOARD = "minnowboard"
By default it set to MinnowBoard Max 'minnowboard'
Currently 32-bit supported boards:
* up_squared_32
* minnowboard
Ref:
https://docs.zephyrproject.org/latest/boards/x86/index.html
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
User need to specify board value to ZEPHYR_BOARD in local.conf
ZEPHYR_BOARD = "ehl_crb"
By default it set to Elkhart Lake CRB 'ehl_crb'
Currently 64-bit supported boards:
* up_squared
* ehl_crb_sbl
* ehl_crb
* acrn
* acrn_ehl_crb
Ref:
https://docs.zephyrproject.org/latest/boards/x86/index.html
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
By default, pyocd uses generic target type called "cortex_m" which
should be able to connect and debug but not flash the memory.
Normally pyocd would warn us of using default target instead
of proper one but this message wasn't displayed.
Despite not providing target type, flashing process succeeded
but results were undefined. On Nitrogen, sometimes it worked
(especially for small images) and sometimes the programmed
device crashed miserably.
Fix flashing operation by providing pyocd target type acquired from
the conditional PYOCD_TARGET variable declared for each machine
(chip family).
Signed-off-by: Zbigniew Bodek <zbigniew.bodek@huawei.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: Andrei Gherzan <andrei.gherzan@huawei.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
No longer supported.
https://github.com/zephyrproject-rtos/zephyr/commit/66d60d29411fa34725b450a9e5fa000f1c69b747
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
No longer supported.
https://github.com/zephyrproject-rtos/zephyr/commit/ffaba63b107780562c2c76ca066a7857bc497303
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
No longer supported.
https://github.com/zephyrproject-rtos/zephyr/commit/ffaba63b107780562c2c76ca066a7857bc497303
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
The board is based on STMicro STM32MP157AAC 2xCortex-A7+2xCortex-M4
system-on-chip.
Add STM32MP1 family machine config. STM32MP1 support depends on
STM32 HAL and OpenAMP for inter-core communication.
This change has been verified with zephyr-philosophers
and zephyr-shell sample applications on by loading Zephyr image
to Cortex-M4 core from Linux using remoteproc framework.
Signed-off-by: Wojciech Zmuda <wojciech.zmuda@huawei.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
Implement do_flash_usb for boards supported by pyocd:
MACHINE=xxx bitbake yyy -c flash_usb
Pyocd support abundance of boards, however for now this
meta-layer supports only one board that can be flashed
using pyocd, that is 96Boards Nitrogen.
Describe the feature in README.
Signed-off-by: Wojciech Zmuda <wojciech.zmuda@huawei.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
The board is based on Nordic nRF52832 Cortex-M4 chip.
The support depends on Nordic HAL. It has been verified
with zephyr-philosophers and zephyr-shell sample applications.
Signed-off-by: Wojciech Zmuda <wojciech.zmuda@huawei.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
Add include for Cortex-M4 tunes and nRF52832. The nRF config
appends 'nordic' to MACHINEOVERRIDES, so the kernel recipe
can include Nordic HAL when this override is detected.
Signed-off-by: Wojciech Zmuda <wojciech.zmuda@huawei.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
Qemu system does not passthroth RNG on x86 host.
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
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>
|
|
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
Added CONFIG_X86_64 since ACRN hypervisor supports x86_64 capable
platforms only.
Ref:
https://github.com/zephyrproject-rtos/zephyr/commit/d0126a037d23484feebba00d2c0eac27e6393fef
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
Drop local newlib recipe and use it from oe-core
TODO: enable arc support
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
Due to default -mfloat-abi=softfp facing below error log:
"Compiler generates FPU instructions for a device without an FPU (check __FPU_PRESENT)"
Ref: https://gcc.gnu.org/onlinedocs/gcc/ARM-Options.html
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
Use uninative by default to allow to build multiple distro
and re-use sstate cache
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
Add new acrn machine, which actually is $BOARD
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
Throw below error:
runqemu - ERROR - Failed to run qemu: qemu-system-i386: -clock: invalid option
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
|
|
Move all SITEINFO_EXTRA_DATAFUNCS and PACKAGEQA_EXTRA_MACHDEFFUNCS
from various tune files (tune-arc.inc, tune-iamcu.inc, tune-nios2.inc)
into a a new siteinfo-zephyr.bbclass file. Although the original code did
not result in any obvious errors, in fact it did cause some multiconfig
problems.
[YOCTO#11166]
Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
|
|
Some Makefiles may need to have ARCH set.
Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
|
|
Support for Arduino BLE ARM core.
The core is based on Cortex-M0, so a corresponding tune/toolchain
is required as well.
Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
|
|
Implement a class allowing flashing Arduino-101 using dfu-util.
User needs to have dfu-utils installed on the host machine.
All three cores supported (x86, ARM, ARC).
Sample usage:
$ MACHINE=arduino-101 bitbake xxx
$ MACHINE=arduino-101 bitbake xxx -c flash_usb
Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
|
|
Add support to run qemus using runqemu.
All qemu machines will inherit the bbclass "zephyr-qemuboot",
which is responsible to set up everything that is needed
in order to use "runqemu".
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>
|
|
This patch adds newlib libraries for cortex-m3, x86, IAMCU and ARC toolchains.
[YOCTO#10662]
Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
|
|
MACHINE definition for Zephyr BOARD qemu_x86
Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
|
|
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>
|
|
Support for Arduino-101 board, Intel MCU CPU.
This board needs IAMCU cross-compiler.
[YOCTO#10658]
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>
|
|
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>
|
|
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>
|
|
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>
|
|
Initial commit: original work by Randy Witt and Richard Purdie.
Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
|