| Summary: | Zephyr BOARD value in local.conf is ignored | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Other YP Layers | Reporter: | Henry Bruce <henry.bruce> |
| Component: | meta-zephyr | Assignee: | Juro Bystricky <juro.bystricky> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | ||
| Version: | 2.3 | ||
| Target Milestone: | 2.3 M2 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Henry Bruce
2017-01-07 00:24:32 UTC
After pondering this somewhat, I believe the best way to fix this is deprecate the variable BOARD altogether and replace it with MACHINE. The meaning of BOARD in Zephyr environment is pretty much equivalent to MACHINE in yocto environment. So the envisioned solution would look something like: $ MACHINE=arduino_101 bitbake zephyr-philosophers or $ MACHINE=qemu_cortex_m3 bitbake zephyr-philosophers etc. where, of course, MACHINE can be set in local.conf as well. I created support for these new MACHINES: MACHINE=arduino-101 MACHINE=arduino-101-sss MACHINE=qemu-cortx-m3 (with more to follow) These correspond to Zephyr boards: BOARD=arduino_101 BOARD=arduino_101_sss BOARD=qemu_cortx_m3 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 "_") |