TipsAndTricks/BuildingZephyrImages - Revision history

RzR at 10:51, 25 September 2022

2022-09-25T10:51:19Z

← Older revision		Revision as of 10:51, 25 September 2022
Line 50:		Line 50:

	=== Targeting QEMU ===		=== Targeting QEMU ===
	Here are the steps. We'll use the ~~dunfell~~ branch for stability.		Here are the steps. We'll use the kirkstone (LTS) branch for stability.
	<pre>		<pre>
	$ git clone -b ~~dunfell~~ git://git.yoctoproject.org/~~poky~~		export MACHINE=qemu-x86
	$ git clone -b ~~dunfell~~ git://git.yoctoproject.org/~~meta-zephyr~~		export DISTRO="zephyr"
	$ git clone -b ~~dunfell~~ git://git.openembedded.org/meta-openembedded		branch=kirkstone
	$ source poky/oe-init-build-env
	$ bitbake-layers add-layer ../meta-~~zephyr~~		git clone -b ${branch} --recursive --depth 1 git://git.yoctoproject.org/meta-zephyr/
	$ bitbake-layers add-layer ../meta-openembedded/meta-oe		git clone -b ${branch} --recursive --depth 1 git://git.yoctoproject.org/poky
	$ bitbake-layers add-layer ../meta-~~openembedded~~/meta-~~python~~		git clone -b ${branch} --recursive --depth 1 git://git.openembedded.org/meta-openembedded
			source poky/oe-init-build-env
			bitbake-layers add-layer ../meta-openembedded/meta-oe
			bitbake-layers add-layer ../meta-openembedded/meta-python
			bitbake-layers add-layer ../meta-zephyr/meta-zephyr-core
			bitbake-layers add-layer ../meta-zephyr/meta-zephyr-bsp

	</pre>		</pre>
	~~In local.conf (or set on command line)~~
	~~DISTRO = "zephyr"~~
	~~MACHINE = "qemu-x86"~~
	Now build a Qemu image of the canonical Zephyr sample		Now build a Qemu image of the canonical Zephyr sample

	bitbake zephyr-philosophers		bitbake zephyr-philosophers
	Running zephyr qemu image		Running zephyr qemu image
Line 71:		Line 76:

	=== Arduino 101 ===		=== Arduino 101 ===
	Let's build the ~~philosphers~~ sample for Arduino 101 x86 core. Set up as for [[TipsAndTricks/BuildingZephyrImages#QEMU\|QEMU]] but set machine as follows		Let's build the philosophers sample for Arduino 101 x86 core. Set up as for [[TipsAndTricks/BuildingZephyrImages#QEMU\|QEMU]] but set machine as follows
	MACHINE = "arduino-101"		MACHINE = "arduino-101"
	Then run		Then run

Naveen Kumar Saini: /* Recipe */

2020-09-22T06:23:53Z

Recipe

← Older revision		Revision as of 06:23, 22 September 2020
Line 30:		Line 30:
	* <tt>inhert deploy</tt> adds a deploy task (it's a standard poky base class)		* <tt>inhert deploy</tt> adds a deploy task (it's a standard poky base class)
	* ZEPHYR_SRC_DIR sets location of application		* ZEPHYR_SRC_DIR sets location of application
	* ~~do_deply~~ puts image in a known location		* do_deploy puts image in a known location

	<pre>		<pre>

Naveen Kumar Saini: /* Targeting QEMU */

2020-09-22T06:23:24Z

Targeting QEMU

← Older revision		Revision as of 06:23, 22 September 2020
Line 50:		Line 50:

	=== Targeting QEMU ===		=== Targeting QEMU ===
	Here are the steps. We'll use the ~~morty~~ branch for stability.		Here are the steps. We'll use the dunfell branch for stability.
	<pre>		<pre>
	$ git clone -b dunfell git://git.yoctoproject.org/poky		$ git clone -b dunfell git://git.yoctoproject.org/poky

Naveen Kumar Saini: /* Zephyr Layer */

2020-09-22T06:22:48Z

Zephyr Layer

← Older revision		Revision as of 06:22, 22 September 2020
Line 18:		Line 18:

	=== Zephyr Layer ===		=== Zephyr Layer ===
	meta-zephyr layer can be found at git://git.yoctoproject.org/meta-zephyr. The layer supports ~~morty~~ and master branches and is dependent on the equivalent poky branch.		meta-zephyr layer can be found at git://git.yoctoproject.org/meta-zephyr. The layer supports dunfell and master branches and is dependent on the equivalent poky branch.

	== Boards and Machines ==		== Boards and Machines ==

Naveen Kumar Saini: /* Targeting QEMU */

2020-09-22T06:20:27Z

Targeting QEMU

← Older revision		Revision as of 06:20, 22 September 2020
Line 52:		Line 52:
	Here are the steps. We'll use the morty branch for stability.		Here are the steps. We'll use the morty branch for stability.
	<pre>		<pre>
	$ git clone -b ~~morty~~ git://git.yoctoproject.org/poky		$ git clone -b dunfell git://git.yoctoproject.org/poky
	$ git clone -b ~~morty~~ git://git.yoctoproject.org/meta-zephyr		$ git clone -b dunfell git://git.yoctoproject.org/meta-zephyr
			$ git clone -b dunfell git://git.openembedded.org/meta-openembedded
	$ source poky/oe-init-build-env		$ source poky/oe-init-build-env
	$ bitbake-layers add-layer ../meta-zephyr		$ bitbake-layers add-layer ../meta-zephyr
			$ bitbake-layers add-layer ../meta-openembedded/meta-oe
			$ bitbake-layers add-layer ../meta-openembedded/meta-python
	</pre>		</pre>
	In local.conf (or set on command line)		In local.conf (or set on command line)

Naveen Kumar Saini: /* Recipe */

2020-09-22T06:14:00Z

Recipe

← Older revision		Revision as of 06:14, 22 September 2020
Line 30:		Line 30:
	* <tt>inhert deploy</tt> adds a deploy task (it's a standard poky base class)		* <tt>inhert deploy</tt> adds a deploy task (it's a standard poky base class)
	* ZEPHYR_SRC_DIR sets location of application		* ZEPHYR_SRC_DIR sets location of application
	* do_compile is straightforward. Could/should be in a base class?
	* do_deply puts image in a known location		* do_deply puts image in a known location

Line 40:		Line 39:
	ZEPHYR_SRC_DIR = "${S}/samples/philosophers"		ZEPHYR_SRC_DIR = "${S}/samples/philosophers"
	ZEPHYR_BASE = "${S}"		ZEPHYR_BASE = "${S}"
			OECMAKE_SOURCEPATH = "${ZEPHYR_SRC_DIR}"
	~~do_compile () {~~
	cd ${ZEPHYR_SRC_DIR}
	~~oe_runmake ${ZEPHYR_MAKE_ARGS}~~
	}

	do_deploy () {		do_deploy () {
	install -D ~~samples/philosophers/outdir/~~${~~BOARD~~}/zephyr~~.elf ${DEPLOYDIR}/${PN}.elf~~		install -D ${B}/zephyr/${ZEPHYR_MAKE_OUTPUT} ${DEPLOYDIR}/${PN}.elf
	~~install -D samples/philosophers/outdir~~/${~~BOARD~~}~~/zephyr.bin~~ ${DEPLOYDIR}/${PN}.~~bin~~
	}		}

	addtask deploy after do_compile		addtask deploy after do_compile
			do_install[noexec] = "1"
	</pre>		</pre>

Henry Bruce: /* Configuration */

2017-03-09T02:43:06Z

Configuration

← Older revision		Revision as of 02:43, 9 March 2017
Line 4:		Line 4:

	== Configuration ==		== Configuration ==
	You'll need to install the following additional package <tt>python3-pexpect</tt>. If you're going to using the Arduino 101 board, you'll also need <tt>dfu-util</tt>.		You'll need to install the following additional package <tt>python3-pexpect</tt>. If you're going to using the Arduino 101 board, you'll also need to configure <tt>dfu-util</tt> as follows:

			=== Using DFU ===
			Device Firmware Update (DFU) allows you to flash A101 images over USB without the need for a JTAG adaptor. First you'll need to install the package <tt>dfu-util</tt> on your Linux distro. By default dfu-util needs root privileges to run. You work around this with the following udev rules
			* If on Fedora, you need to create the system group plugdev
			$ sudo groupadd -r plugdev
			* Add user to plugdev group
			$ sudo usermod -a -G plugdev $USER
			* Create file <tt>etc/udev/rules.d/50-arduino101.rules</tt> and add the following linr
			SUBSYSTEMS=="usb", ATTRS{idVendor}=="8087", ATTRS{idProduct}=="0aba", GROUP="plugdev", MODE="0666"
			* Reload udev rules
			$ sudo udevadm control --reload-rules

			=== Zephyr Layer ===
	meta-zephyr layer can be found at git://git.yoctoproject.org/meta-zephyr. The layer supports morty and master branches and is dependent on the equivalent poky branch.		meta-zephyr layer can be found at git://git.yoctoproject.org/meta-zephyr. The layer supports morty and master branches and is dependent on the equivalent poky branch.

Henry Bruce: /* Building */

2017-03-09T02:39:07Z

Building

← Older revision		Revision as of 02:39, 9 March 2017
Line 94:		Line 94:
	=== Building ===		=== Building ===
	Build both images:		Build both images:
	$ bitbake multiconfig:*:zephyr-ipm		$ bitbake multiconfig:arduino-101:zephyr-ipm multiconfig:arduino-101-sss:zephyr-ipm

	=== Flashing ===		=== Flashing ===

Henry Bruce: /* Configuration */

2017-03-07T22:55:38Z

Configuration

← Older revision		Revision as of 22:55, 7 March 2017
Line 78:		Line 78:
	DISTRO = "zephyr"		DISTRO = "zephyr"
	MACHINE ?= "arduino-101"		MACHINE ?= "arduino-101"
	BBMULTICONFIG ?= "arduino-101-sss"		BBMULTICONFIG ?= "arduino-101 arduino-101-sss"
	Create folder <tt>multiconfig</tt> under <tt>conf</tt> with a file <tt>arduino-101-sss.conf</tt>		Create folder <tt>multiconfig</tt> under <tt>conf</tt> with a file <tt>arduino-101-sss.conf</tt>
	+ conf		+ conf
	+ multiconfig		+ multiconfig
	arduino-101-sss		arduino-101.conf
			arduino-101-sss.conf
			The file <tt>conf/multiconfig/arduino-101.conf</tt> should contain:
			MACHINE="arduino-101"
			TMPDIR="${TOPDIR}/tmp-arduino-101"
	The file <tt>conf/multiconfig/arduino-101-sss.conf</tt> should contain:		The file <tt>conf/multiconfig/arduino-101-sss.conf</tt> should contain:
	MACHINE="arduino-101-sss"		MACHINE="arduino-101-sss"
	TMPDIR="${TOPDIR}/tmp-arduino-101-sss"		TMPDIR="${TOPDIR}/tmp-arduino-101-sss"
			The TMPDIR settings are a workaround a multiconfig bug exposed by the meta-zephyr.

	=== Building ===		=== Building ===

Henry Bruce: /* Arduino 101 */

2017-03-07T22:53:10Z

Arduino 101

@@ Line 67: / Line 67: @@
 Note that there will be significant rebuild, as although both qemu-x86 and arduino-101 are 386 class devices, arduino-101 uses the subtly different IAMCU toolchain.
-After build complete, image will in tmp/deploy/images/arduino-101/zephyr-philosophers.bin. Flash as follows using dfu
+After build complete, use the flash_usb task to flash the target via DFU
-  dfu-util -a x86_app -D tmp/deploy/images/arduino-101/zephyr-philosophers.bin
+ bitbake zephyr-philosophers  -c flash_usb
 Sample text output will appear on serial port.