Poky-Tiny - Revision history

Tzanussi: /* Invoking qemu with poky-tiny images */

2016-08-04T19:39:15Z

Invoking qemu with poky-tiny images

← Older revision		Revision as of 19:39, 4 August 2016
Line 99:		Line 99:

	== Invoking qemu with poky-tiny images ==		== Invoking qemu with poky-tiny images ==
	~~Runqemu doesn't understand~~ poky-tiny ~~(or initramfs?)~~. ~~Try~~ executing qemu directly instead. Here's the template:		runqemu can be used to run a poky-tiny image. For instance, for a poky-tiny qemux86 build, try:

			$ runqemu qemux86 ramfs

			If that doesn't work, try executing qemu directly instead. Here's the template:

	$ qemu-system-i386 -kernel path/to/kernel -initrd path/to/image.cpio.gz -nographic -append "console=ttyS0 root=/dev/ram0"		$ qemu-system-i386 -kernel path/to/kernel -initrd path/to/image.cpio.gz -nographic -append "console=ttyS0 root=/dev/ram0"

Maxin B. John: /* Invoking qemu with poky-tiny images */ update path for full command

2016-01-14T16:58:50Z

Invoking qemu with poky-tiny images: update path for full command

← Older revision		Revision as of 16:58, 14 January 2016
Line 105:		Line 105:
	Here the actual full command I used:		Here the actual full command I used:

	$ tmp/sysroots/x86_64-linux/usr/bin/qemu-system-i386 -kernel tmp/deploy/images/bzImage-qemux86.bin -initrd tmp/deploy/images/core-image-minimal-qemux86.cpio.gz -nographic -append "console=ttyS0 root=/dev/ram0"		$ tmp/sysroots/x86_64-linux/usr/bin/qemu-system-i386 -kernel tmp/deploy/images/qemux86/bzImage-qemux86.bin -initrd tmp/deploy/images/qemux86/core-image-minimal-qemux86.cpio.gz -nographic -append "console=ttyS0 root=/dev/ram0"

	=== Some information about the running system ===		=== Some information about the running system ===

Dennis Meier: /* Controlling busybox features */

2013-12-05T08:37:22Z

Controlling busybox features

← Older revision		Revision as of 08:37, 5 December 2013
Line 93:		Line 93:

	In this example you can see how in a new layer, the busybox_<version>.bbappend file modifies the FILESEXTRAPATHS, which enables bitbake to find the corresponding defconfig in meta-new-layer/recipes-core/busybox_1.20.2. In the example defconfig, mdev gets enabled by setting the variables CONFIG_MDEV and CONFIG_FEATURE_MDEV_LOAD_FIRMWARE. The original defconfig that would be used by poky normally is stored in meta/recipes-core/busybox/busybox-<version>/defconfig as of this writing. PACKAGES += just makes sure that busybox-mdev gets packaged because it doesn't do this by default.		In this example you can see how in a new layer, the busybox_<version>.bbappend file modifies the FILESEXTRAPATHS, which enables bitbake to find the corresponding defconfig in meta-new-layer/recipes-core/busybox_1.20.2. In the example defconfig, mdev gets enabled by setting the variables CONFIG_MDEV and CONFIG_FEATURE_MDEV_LOAD_FIRMWARE. The original defconfig that would be used by poky normally is stored in meta/recipes-core/busybox/busybox-<version>/defconfig as of this writing. PACKAGES += just makes sure that busybox-mdev gets packaged because it doesn't do this by default.

			In general: Set the FILESEXTRAPATHS so bitbake finds your defconfig and put whatever you like into your defconfig.

	== Troubleshooting the build ==		== Troubleshooting the build ==

Dennis Meier: /* Controlling busybox features */

2013-12-05T08:34:08Z

Controlling busybox features

← Older revision		Revision as of 08:34, 5 December 2013
Line 74:		Line 74:

	=== Controlling busybox features ===		=== Controlling busybox features ===
	To adjust busybox features, it's necessary to have your own defconfig ~~and~~ the busybox recipe must be appended to tell bitbake where it can find this defconfig. ~~In its most basic form it could look like this~~:		To adjust busybox features, it's necessary to have your own defconfig. Then the busybox recipe must be appended (or you need your own busybox recipe) to tell bitbake where it can find this defconfig. An example:
	~~<nowiki>~~
	$ cd /path/to/poky/directory		'''$ cd /path/to/poky/directory/meta-new-layer'''
	$ tree recipes-core/		'''$ tree recipes-core/'''
	recipes-core/		recipes-core/
	├── busybox_1.20.2		├── busybox_1.20.2
	│ └── defconfig		│ └── defconfig
	└── busybox_1.20.2.bbappend		└── busybox_1.20.2.bbappend
			1 directory, 2 files
			'''$ cat recipes-core/busybox_1.20.2.bbappend'''
			FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
			PACKAGES =+ "${PN}-mdev"
			'''$ diff recipes-core/busybox_1.20.2/defconfig ../meta/recipes-core/busybox/busybox-1.20.2/defconfig'''
			530d529
			< CONFIG_MDEV=y
			536d534
			< CONFIG_FEATURE_MDEV_LOAD_FIRMWARE=y

	~~1 directory~~, 2 ~~files~~		In this example you can see how in a new layer, the busybox_<version>.bbappend file modifies the FILESEXTRAPATHS, which enables bitbake to find the corresponding defconfig in meta-new-layer/recipes-core/busybox_1.20.2. In the example defconfig, mdev gets enabled by setting the variables CONFIG_MDEV and CONFIG_FEATURE_MDEV_LOAD_FIRMWARE. The original defconfig that would be used by poky normally is stored in meta/recipes-core/busybox/busybox-<version>/defconfig as of this writing. PACKAGES += just makes sure that busybox-mdev gets packaged because it doesn't do this by default.
	</~~nowiki>~~

	== Troubleshooting the build ==		== Troubleshooting the build ==

Dennis Meier: /* Controlling busybox features */

2013-12-05T08:07:37Z

Controlling busybox features

← Older revision		Revision as of 08:07, 5 December 2013
Line 74:		Line 74:

	=== Controlling busybox features ===		=== Controlling busybox features ===
			To adjust busybox features, it's necessary to have your own defconfig and the busybox recipe must be appended to tell bitbake where it can find this defconfig. In its most basic form it could look like this:
			<nowiki>
			$ cd /path/to/poky/directory
			$ tree recipes-core/
			recipes-core/
			├── busybox_1.20.2
			│ └── defconfig
			└── busybox_1.20.2.bbappend

			1 directory, 2 files
			</nowiki>

	== Troubleshooting the build ==		== Troubleshooting the build ==

Tbird20d: /* exiting the system */

2012-11-14T22:51:43Z

exiting the system

← Older revision		Revision as of 22:51, 14 November 2012
Line 213:		Line 213:
	=== exiting the system ===		=== exiting the system ===
	There is no 'shutdown' command, but you can use 'ctrl-a to execute a command to the qemu monitor, and 'ctrl-a b' to issue a sysrq to the Linux kernel.		There is no 'shutdown' command, but you can use 'ctrl-a to execute a command to the qemu monitor, and 'ctrl-a b' to issue a sysrq to the Linux kernel.
	You can do a sysrq-B to do a reboot. Do: ctrl-a h to see available commands, and ctrl-a x to exit ~~the~~ qemu.		You can do a sysrq-B to do a reboot. Do: ctrl-a h to see available commands, and ctrl-a x to exit qemu.

	== Resources ==		== Resources ==
	* Presentation: [http://elinux.org/images/2/2b/Elce11_hart.pdf Tuning Linux For Embedded Systems: When Less Is More] by Darren Hart, ELC Europe 2011, October 2011, Prague, Czech Republic		* Presentation: [http://elinux.org/images/2/2b/Elce11_hart.pdf Tuning Linux For Embedded Systems: When Less Is More] by Darren Hart, ELC Europe 2011, October 2011, Prague, Czech Republic

Tbird20d: /* Some information about the running system */

2012-11-14T22:50:46Z

Some information about the running system

← Older revision		Revision as of 22:50, 14 November 2012
Line 208:		Line 208:
	busybox, ldconfig and libc (and other libc-related libs) make up about 95% of the system.		busybox, ldconfig and libc (and other libc-related libs) make up about 95% of the system.

	If busybox were statically linked, and ldconfig and libc were omitted, I'm believe it would		If busybox were statically linked, and ldconfig and libc were omitted, I believe it would
	reduce the size of the system substantially.		reduce the size of the system substantially.

Tbird20d: /* Basic use */

2012-11-14T22:40:35Z

Basic use

← Older revision		Revision as of 22:40, 14 November 2012
Line 21:		Line 21:
	$ bitbake core-image-minimal		$ bitbake core-image-minimal

	Resulting images should appear in your <build-dir>/deploy/images directory.		Resulting images should appear in your <build-dir>/tmp/deploy/images directory.

	== FAQ ==		== FAQ ==

Dvhart: moved Projects/Poky-Tiny to Poky-Tiny: Be consistent with other project pages.

2012-11-14T22:27:08Z

moved Projects/Poky-Tiny to Poky-Tiny: Be consistent with other project pages.

← Older revision	Revision as of 22:27, 14 November 2012
(No difference)

Tbird20d: /* Some information about the running system */

2012-11-14T22:26:47Z

Some information about the running system

← Older revision		Revision as of 22:26, 14 November 2012
Line 113:		Line 113:
	Here's a sample of what the filesystem looks like (as of yocto-danny-8.0), with results sorted by size		Here's a sample of what the filesystem looks like (as of yocto-danny-8.0), with results sorted by size
	and /sys, /proc and /dev omitted:		and /sys, /proc and /dev omitted:
	/ # find / -type f -xdev \| xargs ls -laSr		# find / -type f -xdev \| xargs ls -laSr
	-rw-r--r-- 1 root root 0 Nov 14 21:24 /lib/modules/3.4.11-yocto-tiny/modules.dep		-rw-r--r-- 1 root root 0 Nov 14 21:24 /lib/modules/3.4.11-yocto-tiny/modules.dep
	-rw-r--r-- 1 root root 0 Nov 14 21:24 /lib/modules/3.4.11-yocto-tiny/modules.builtin.bin		-rw-r--r-- 1 root root 0 Nov 14 21:24 /lib/modules/3.4.11-yocto-tiny/modules.builtin.bin