Yocto - Revision history

Kai: /* NFS */

2025-04-12T15:30:12Z

NFS

← Older revision		Revision as of 2025-04-12T15:30:12
Line 190:		Line 190:
	<br />		<br />

			==== Server Configuration on Build Machine ====
	On your Debian-based Yocto build machine, follow the instruction for [[Ubuntu#Setting_up_an_NFS_Server\|'''setting up an NFS server''']], where the served directory in ''/etc/exports'' must be		On your Debian-based Yocto build machine, follow the instruction for [[Ubuntu#Setting_up_an_NFS_Server\|'''setting up an NFS server''']], where the served directory in ''/etc/exports'' must be
	<br />		<br />
Line 195:		Line 196:
	For example,		For example,
	: ''build-robofish-lt0/tmp/work/raspberrypi4_64-poky-linux/robofish-lt0-image-dev/1.0-r0/rootfs''		: ''build-robofish-lt0/tmp/work/raspberrypi4_64-poky-linux/robofish-lt0-image-dev/1.0-r0/rootfs''
	~~<br />~~

			==== Client Configuration on Build Machine ====
	To add NFS client capabilities to the target device, edit ''conf/local.conf'' in the Yocto build directory, adding the line		To add NFS client capabilities to the target device, edit ''conf/local.conf'' in the Yocto build directory, adding the line
	<pre class="code">		<pre class="code">
Line 209:		Line 210:
	ENABLE_UART = "1"		ENABLE_UART = "1"
	</pre>		</pre>
			Build the image and deploy on the target device by flashing an SD-Card or eMMC, as usual.
	<br />		<br />
	~~Build the image and deploy~~ on ~~the target device by flashing an SD-Card or eMMC, as usual.~~ Connected to the target device over UART, reboot the target device to enter the U-Boot command prompt. ~~Follow [https://developer.technexion.com/docs/using-an-nfs-root-filesystem#uboot-configuration these instructions for configuring U-Boot].~~
			==== Client Configuration on Target Device ====
			Connected to the target device over UART, reboot the target device to enter into the U-Boot command prompt before the timeout expires.

	<br />		<br />
			Similar instructions can be found [https://developer.technexion.com/docs/using-an-nfs-root-filesystem#uboot-configuration in this external article].

	<br />		<br />

Kai: /* NFS */

2025-04-12T14:04:17Z

NFS

← Older revision		Revision as of 2025-04-12T14:04:17
Line 188:		Line 188:
	=== NFS ===		=== NFS ===
	In Embedded Linux projects, NFS is often included in development images to enable faster code-deploy turnaround times. With NFS included, the target device can be configured to access the Yocto build machine over the network while booting. Once the target device is connected to the build machine, it uses the generated root filesystem on the build machine to continue with system initialization. As long as no change to the boot partition of the target device is required, the generated root filesystem does not need be packaged into a flashable image file (.wic.bz2 format, for example) and then flashed to the target storage medium (eMMC or SD-Card) anymore. The build step for generating the image file can thus be disabled, shortening the build time.		In Embedded Linux projects, NFS is often included in development images to enable faster code-deploy turnaround times. With NFS included, the target device can be configured to access the Yocto build machine over the network while booting. Once the target device is connected to the build machine, it uses the generated root filesystem on the build machine to continue with system initialization. As long as no change to the boot partition of the target device is required, the generated root filesystem does not need be packaged into a flashable image file (.wic.bz2 format, for example) and then flashed to the target storage medium (eMMC or SD-Card) anymore. The build step for generating the image file can thus be disabled, shortening the build time.
			<br />

			On your Debian-based Yocto build machine, follow the instruction for [[Ubuntu#Setting_up_an_NFS_Server\|'''setting up an NFS server''']], where the served directory in ''/etc/exports'' must be
	<br />		<br />
	To ~~include~~ NFS client ~~capability on~~ the target device, edit ''conf/local.conf'' in the Yocto build directory ~~(or ''conf/layer.conf'' file of your layer) to add~~ the line		: ${YOCTO_BUILD_DIR}'''/tmp/work/'''${TARGET}'''-poky-linux/'''${IMAGE}'''/1.0-r0/rootfs'''
			For example,
			: ''build-robofish-lt0/tmp/work/raspberrypi4_64-poky-linux/robofish-lt0-image-dev/1.0-r0/rootfs''
			<br />

			To add NFS client capabilities to the target device, edit ''conf/local.conf'' in the Yocto build directory, adding the line
	<pre class="code">		<pre class="code">
	DISTRO_FEATURES:append = " nfs"		DISTRO_FEATURES:append = " nfs"
	</pre>		</pre>
	Since the Raspberry Pi bootloader does not support mounting a file system from the network, we ~~also add the following line for using~~ U-Boot instead:		Since the Raspberry Pi bootloader does not support mounting a file system from the network, we use U-Boot instead:
	<pre class="code">		<pre class="code">
	RPI_USE_U_BOOT = "1"		RPI_USE_U_BOOT = "1"
Line 203:		Line 210:
	</pre>		</pre>
	<br />		<br />
			Build the image and deploy on the target device by flashing an SD-Card or eMMC, as usual. Connected to the target device over UART, reboot the target device to enter the U-Boot command prompt. Follow [https://developer.technexion.com/docs/using-an-nfs-root-filesystem#uboot-configuration these instructions for configuring U-Boot].
	<br />		<br />
	~~On your Debian-based Yocto build machine, follow the instruction for [[Ubuntu#Setting_up_an_NFS_Server\|'''setting up an NFS server''']], where the served directory in ''/etc/exports'' must be~~
	~~<br />~~
	~~: ${YOCTO_BUILD_DIR}'''/tmp/work/'''${TARGET}'''-poky-linux/'''${IMAGE}'''/1.0-r0/rootfs'''~~
	~~For example,~~
	~~: ''build-robofish-lt0/tmp/work/raspberrypi4_64-poky-linux/robofish-lt0-image-dev/1.0-r0/rootfs''~~
	~~<br />~~
	<br />		<br />

Kai: /* NFS */

2025-04-12T11:05:58Z

NFS

← Older revision		Revision as of 2025-04-12T11:05:58
Line 197:		Line 197:
	<pre class="code">		<pre class="code">
	RPI_USE_U_BOOT = "1"		RPI_USE_U_BOOT = "1"
			</pre>
			According to the [https://meta-raspberrypi.readthedocs.io/en/latest/extra-build-config.html#boot-to-u-boot meta-raspberrypi documentation], U-Boot only works if we also have
			<pre class="code">
			ENABLE_UART = "1"
	</pre>		</pre>
	<br />		<br />

Kai: Adds text about how to use U-Boot instead of the Raspberry Pi bootloader.

2025-04-12T10:50:58Z

Adds text about how to use U-Boot instead of the Raspberry Pi bootloader.

← Older revision		Revision as of 2025-04-12T10:50:58
Line 194:		Line 194:
	DISTRO_FEATURES:append = " nfs"		DISTRO_FEATURES:append = " nfs"
	</pre>		</pre>
			Since the Raspberry Pi bootloader does not support mounting a file system from the network, we also add the following line for using U-Boot instead:
			<pre class="code">
			RPI_USE_U_BOOT = "1"
			</pre>
			<br />
	<br />		<br />
	On your Debian-based Yocto build machine, follow the instruction for [[Ubuntu#Setting_up_an_NFS_Server\|'''setting up an NFS server''']], where the served directory in ''/etc/exports'' must be		On your Debian-based Yocto build machine, follow the instruction for [[Ubuntu#Setting_up_an_NFS_Server\|'''setting up an NFS server''']], where the served directory in ''/etc/exports'' must be

Kai: /* NFS */

2025-04-11T10:16:29Z

NFS

← Older revision		Revision as of 2025-04-11T10:16:29
Line 195:		Line 195:
	</pre>		</pre>
	<br />		<br />
	On your Debian-based Yocto build machine, [[Ubuntu#Setting_up_an_NFS_Server\|~~set~~ up an NFS server]] where the served directory in ''/etc/exports'' must be		On your Debian-based Yocto build machine, follow the instruction for [[Ubuntu#Setting_up_an_NFS_Server\|'''setting up an NFS server''']], where the served directory in ''/etc/exports'' must be
	<br />		<br />
	: ${YOCTO_BUILD_DIR}'''/tmp/work/'''${TARGET}'''-poky-linux/'''${IMAGE}'''/1.0-r0/rootfs'''		: ${YOCTO_BUILD_DIR}'''/tmp/work/'''${TARGET}'''-poky-linux/'''${IMAGE}'''/1.0-r0/rootfs'''

Kai: expanding the instructions on use of NFS to shorten development time

2025-04-11T10:13:50Z

expanding the instructions on use of NFS to shorten development time

← Older revision		Revision as of 2025-04-11T10:13:50
Line 187:		Line 187:

	=== NFS ===		=== NFS ===
	In Embedded Linux projects, NFS is often included in development images to enable faster code-deploy turnaround times.		In Embedded Linux projects, NFS is often included in development images to enable faster code-deploy turnaround times. With NFS included, the target device can be configured to access the Yocto build machine over the network while booting. Once the target device is connected to the build machine, it uses the generated root filesystem on the build machine to continue with system initialization. As long as no change to the boot partition of the target device is required, the generated root filesystem does not need be packaged into a flashable image file (.wic.bz2 format, for example) and then flashed to the target storage medium (eMMC or SD-Card) anymore. The build step for generating the image file can thus be disabled, shortening the build time.

	<br />		<br />
	In the ''conf/local.conf'' ~~file of your~~ Yocto build directory (or ''conf/layer.conf'' file of your layer) add		To include NFS client capability on the target device, edit ''conf/local.conf'' in the Yocto build directory (or ''conf/layer.conf'' file of your layer) to add the line
	<pre class="code">		<pre class="code">
	DISTRO_FEATURES:append = " nfs"		DISTRO_FEATURES:append = " nfs"
	</pre>		</pre>
	<br />		<br />
	On your Debian-based Yocto machine, [[Ubuntu#Setting_up_an_NFS_Server\|set up an NFS server]] where the served directory in ''/etc/exports'' must be		On your Debian-based Yocto build machine, [[Ubuntu#Setting_up_an_NFS_Server\|set up an NFS server]] where the served directory in ''/etc/exports'' must be
	<br />		<br />
	: ${YOCTO_BUILD_DIR}'''/tmp/work/'''${TARGET}'''-poky-linux/'''${IMAGE}'''/1.0-r0/rootfs'''		: ${YOCTO_BUILD_DIR}'''/tmp/work/'''${TARGET}'''-poky-linux/'''${IMAGE}'''/1.0-r0/rootfs'''

Kai: Adding reference to section that explains mounting a Raspberry Pi eMMC with rpiboot

2025-04-07T16:39:37Z

Adding reference to section that explains mounting a Raspberry Pi eMMC with rpiboot

← Older revision		Revision as of 2025-04-07T16:39:37
Line 135:		Line 135:

	== Installing the Rootfs Image ==		== Installing the Rootfs Image ==
	Using [https://github.com/intel/bmap-tools bmaptool] we can copy the generated ''wic'' image (with matching bmap file) to ~~a mounted~~ SD card or eMMC storage.		Using [https://github.com/intel/bmap-tools bmaptool] we can copy the generated ''wic'' image (with matching bmap file) to an SD card or eMMC storage ([https://robo.fish/wiki/index.php?title=Raspberry_Pi#Installing_the_System_Image_on_eMMC_using_rpiboot mounted using rpiboot]).
	<pre class="terminal">		<pre class="terminal">
	sudo bmaptool copy tmp/deploy/images/raspberrypi4-64/<wic.bz2 file> <drive>		sudo bmaptool copy tmp/deploy/images/raspberrypi4-64/<wic.bz2 file> <drive>

Kai: /* Layers */

2024-11-10T18:24:58Z

Layers

← Older revision		Revision as of 2024-11-10T18:24:58
Line 36:		Line 36:
	A layer is a purposeful collection of metadata that adds some feature or capability to your custom system image. For example, if you want to create a custom system for the Raspberry Pi 4, you will need the drivers and configurations for that device. These are available packaged as a layer. Just download the sources for the Raspberry Pi layer and add it to the stack of layers used in your build:		A layer is a purposeful collection of metadata that adds some feature or capability to your custom system image. For example, if you want to create a custom system for the Raspberry Pi 4, you will need the drivers and configurations for that device. These are available packaged as a layer. Just download the sources for the Raspberry Pi layer and add it to the stack of layers used in your build:
	<pre class="terminal">		<pre class="terminal">
			cd $HOME
			mkdir yocto
			cd yocto
	git clone git://git.yoctoproject.org/poky -b scarthgap		git clone git://git.yoctoproject.org/poky -b scarthgap
	~~cd poky~~
	~~source oe-init-build-env~~
	~~cd ..~~
	mkdir layers		mkdir layers
	cd layers		cd layers
	git clone git://git.yoctoproject.org/meta-raspberrypi -b scarthgap		git clone git://git.yoctoproject.org/meta-raspberrypi -b scarthgap
	cd ../poky		cd ../poky
	bitbake-layers add-layer ../layers/meta-raspberrypi		source oe-init-build-env
	cat build/conf/bblayers.conf \| grep raspberrypi		bitbake-layers add-layer $HOME/yocto/layers/meta-raspberrypi
			cat $HOME/yocto/poky/build/conf/bblayers.conf \| grep raspberrypi
	TARGET=core-image-full-cmdline		TARGET=core-image-full-cmdline
	bitbake --dry-run $TARGET		bitbake --dry-run $TARGET

Kai: /* Layers */

2024-11-10T18:11:48Z

Layers

← Older revision		Revision as of 2024-11-10T18:11:48
Line 44:		Line 44:
	git clone git://git.yoctoproject.org/meta-raspberrypi -b scarthgap		git clone git://git.yoctoproject.org/meta-raspberrypi -b scarthgap
	cd ../poky		cd ../poky
	bitbake-layers add-layer ~~../~~../layers/meta-raspberrypi		bitbake-layers add-layer ../layers/meta-raspberrypi
	cat build/conf/bblayers.conf \| grep raspberrypi		cat build/conf/bblayers.conf \| grep raspberrypi
	TARGET=core-image-full-cmdline		TARGET=core-image-full-cmdline

Kai: /* Layers */

2024-11-10T18:09:16Z

Layers

← Older revision		Revision as of 2024-11-10T18:09:16
Line 39:		Line 39:
	cd poky		cd poky
	source oe-init-build-env		source oe-init-build-env
			cd ..
	mkdir layers		mkdir layers
	cd layers		cd layers