TipsAndTricks/KernelDevelopmentWithEsdk - Revision history

Bavery at 19:50, 4 October 2017

2017-10-04T19:50:43Z

← Older revision		Revision as of 19:50, 4 October 2017
Line 193:		Line 193:
	16 582 656 bytes free		16 582 656 bytes free

			* remove the old kernel from your image:
			$ wic rm /tmp/core-image-base-qemux86-64.wic:1/vmlinuz
			* add in your freshly constructed kernel.
			** if you built the kernel with devtool, the resulting bzImage is in the tmp/work directory as below.
			$ wic cp ~/poky_sdk/tmp/work/qemux86_64-poky-linux/linux-yocto/4.12.12+git999-r0/linux-yocto-4.12.12+git999/arch/x86/boot/bzImage /tmp/core-image-base-qemux86-64.wic:1/vmlinuz
			** if you built it straight with make in the workspace/linux-yocto directory, it is in a more standard place:
			$ cp workspace/sources/linux-yocto/arch/x86/boot/bzImage /tmp/core-image-base-qemux86-64.wic:1/vmlinuz

			* then you can dd your wic image onto a sd card/usb key and you can test your target.
			** note: bmap-copy using the bmap tools is generally ~ 10x-20x faster than a straight dd. Docs -> [http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#flashing-images-using-bmaptool Official bmaptool copy docs]

Bavery at 18:26, 4 October 2017

2017-10-04T18:26:00Z

@@ Line 156: / Line 156: @@
 To build the updated kernel source, in the SDK terminal run make in your kernel source folder. Adjust the -j option to match number of cores on your workstation.
   $ make -C workspace/sources/linux-yocto -j4
-=== Create image with new kernel ===
+=== Create image with new kernel  2.4 Way ===
-Normally you'd make a new image with <tt>devtool build-image</tt> but this can take a minute or so and messes with the kernel source folder. A faster option is to use kpartx to splice the new kernel into the image you have already built. NOTE: If your build system does not have kpartx installed, be sure you install it.
+Note: There are several bugs outstanding to make this process a little easier as of 9/2017.  They mostly deal with unwieldy paths and are easy to work around. I will detail the workarounds here and if it is clear that you don't need them due to the bugs getting fixed and merged, so much the better.
 First make a copy of your wic file in say /tmp

Scottrif at 23:33, 7 September 2017

2017-09-07T23:33:06Z

@@ Line 24: / Line 24: @@
   MACHINE = "genericx86-64"
   MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS += "kernel-modules"
 Now build an extensible SDK installer for the Minnowboard in the bitbake terminal
 <pre>
@@ Line 71: / Line 55: @@
 </pre>
 Take note of the final line, which shows you the environment setup script you must run each time you want to use the eSDK.
 == Setup your ESDK build environment (ESDK terminal) ==
@@ Line 152: / Line 156: @@
 To build the updated kernel source, in the SDK terminal run make in your kernel source folder. Adjust the -j option to match number of cores on your workstation.
   $ make -C workspace/sources/linux-yocto -j4
 === Create image with new kernel ===
 Normally you'd make a new image with <tt>devtool build-image</tt> but this can take a minute or so and messes with the kernel source folder. A faster option is to use kpartx to splice the new kernel into the image you have already built. NOTE: If your build system does not have kpartx installed, be sure you install it.

Scottrif: /* Build Extensible SDK */

2017-08-18T19:26:48Z

Build Extensible SDK

← Older revision		Revision as of 19:26, 18 August 2017
Line 47:		Line 47:
	The eSDK installer can be found in /path_to_build_directory/kernel-dev/tmp/deploy/sdk/		The eSDK installer can be found in /path_to_build_directory/kernel-dev/tmp/deploy/sdk/
	./tmp/deploy/sdk/poky-glibc-x86_64-core-image-minimal-core2-64-toolchain-ext-2.3.1.sh		./tmp/deploy/sdk/poky-glibc-x86_64-core-image-minimal-core2-64-toolchain-ext-2.3.1.sh

	Alternatively, if you are not using a yocto-linux kernel, you can use a prebuilt eSDK installer that includes the toolchain you need. For example, the pyro core-image-minimal esdk release for core2-64 is located [[http://downloads.yoctoproject.org/releases/yocto/yocto-2.3.1/toolchain/x86_64/poky-glibc-x86_64-core-image-minimal-core2-64-toolchain-ext-2.3.1.sh here]]. If you downloaded the installer, make it executable.

	== Install Extensible SDK ==		== Install Extensible SDK ==

Scottrif: /* Build Extensible SDK */

2017-08-17T23:31:32Z

Build Extensible SDK

← Older revision		Revision as of 23:31, 17 August 2017
Line 39:		Line 39:
	<pre>		<pre>
	$ cd ~/poky/build		$ cd ~/poky/build
	$ bitbake-layers add-layer ../meta-my-kernel		$ bitbake-layers add-layer ../../meta-my-kernel
	</pre>		</pre>
	Now build an extensible SDK installer for the Minnowboard in the bitbake terminal		Now build an extensible SDK installer for the Minnowboard in the bitbake terminal

Scottrif: /* Build Extensible SDK */

2017-08-17T23:30:26Z

Build Extensible SDK

← Older revision		Revision as of 23:30, 17 August 2017
Line 31:		Line 31:
	Would you like to have an example recipe created? (y/n) [default: n]		Would you like to have an example recipe created? (y/n) [default: n]
	Would you like to have an example bbappend file created? (y/n) [default: n]		Would you like to have an example bbappend file created? (y/n) [default: n]
	~~Please enter the version number you'd like to use for your bbappend file (this should match the recipe you're appending to): [default: 0.1]~~

	New layer created in ../meta-my-kernel.		New layer created in ../meta-my-kernel.

Scottrif: /* Build Extensible SDK */

2017-08-17T23:28:54Z

Build Extensible SDK

← Older revision		Revision as of 23:28, 17 August 2017
Line 14:		Line 14:
	Open a new terminal window, we'll refer to this terminal as your '''bitbake terminal'''. First we'll checkout poky and configure bitbake environment.		Open a new terminal window, we'll refer to this terminal as your '''bitbake terminal'''. First we'll checkout poky and configure bitbake environment.
	<pre>		<pre>
			$ cd ~
	$ git clone -b pyro git://git.yoctoproject.org/poky		$ git clone -b pyro git://git.yoctoproject.org/poky
	$ source poky/oe-init-build-env		$ source poky/oe-init-build-env
Line 23:		Line 24:
	MACHINE = "genericx86-64"		MACHINE = "genericx86-64"
	MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS += "kernel-modules"		MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS += "kernel-modules"
	We also need to create a layer to take the kernel patches we'll be creating. ~~Be sure to create example recipe and append files when you run you run the "yocto-layer" command.~~		We also need to create a layer to take the kernel patches we'll be creating.
	<pre>		<pre>
			$ cd ~/poky
	$ yocto-layer create my-kernel -o ../meta-my-kernel		$ yocto-layer create my-kernel -o ../meta-my-kernel
	Please enter the layer priority you'd like to use for the layer: [default: 6]		Please enter the layer priority you'd like to use for the layer: [default: 6]
	Would you like to have an example recipe created? (y/n) [default: n~~] y~~		Would you like to have an example recipe created? (y/n) [default: n]
	~~Please enter the name you'd like to use for your example recipe: [default: example~~]		Would you like to have an example bbappend file created? (y/n) [default: n]
	Would you like to have an example bbappend file created? (y/n) [default: n~~] y~~
	~~Please enter the name you'd like to use for your bbappend file: [default: example~~]
	Please enter the version number you'd like to use for your bbappend file (this should match the recipe you're appending to): [default: 0.1]		Please enter the version number you'd like to use for your bbappend file (this should match the recipe you're appending to): [default: 0.1]

Line 39:		Line 39:
	As directed, we need to add our layer to BBLAYERS as follows:		As directed, we need to add our layer to BBLAYERS as follows:
	<pre>		<pre>
			$ cd ~/poky/build
	$ bitbake-layers add-layer ../meta-my-kernel		$ bitbake-layers add-layer ../meta-my-kernel
	</pre>		</pre>

Scottrif: /* Create image with new kernel */

2017-08-09T21:49:25Z

Create image with new kernel

← Older revision		Revision as of 21:49, 9 August 2017
Line 160:		Line 160:
	$ cp tmp/deploy/images/genericx86-64/core-image-minimal-genericx86-64.wic /tmp		$ cp tmp/deploy/images/genericx86-64/core-image-minimal-genericx86-64.wic /tmp
	Then create loopback devices for each partition in wic file.		Then create loopback devices for each partition in wic file.
	NOTE: The first unused loopback device ~~(loopX) will be~~ automatically allocated. ~~This~~ example uses "X". ~~You need to use~~ the actual loopback ~~device~~ (e.g. "~~loop0~~").		NOTE: The first unused loopback device is automatically allocated. The example command output here uses a variable "X" to indicate the loopback device. The actual output you get when you run the command will list the actual loopback devices (e.g. "loop0p1", "loop0p2", and "loop0p3").
	$ sudo kpartx -v -a /tmp/core-image-minimal-genericx86-64.wic		$ sudo kpartx -v -a /tmp/core-image-minimal-genericx86-64.wic
	add map loopXp1 (253:6): 0 47446 linear /dev/loopX 2048		add map loopXp1 (253:6): 0 47446 linear /dev/loopX 2048
Line 166:		Line 166:
	add map loopXp3 (253:8): 0 90112 linear /dev/loopX 170556		add map loopXp3 (253:8): 0 90112 linear /dev/loopX 170556
	Kernel is in the first device, so let's mount /dev/mapper/loopXp1 to take a look		Kernel is in the first device, so let's mount /dev/mapper/loopXp1 to take a look
	NOTE: Replace loopXp1 with the automatically allocated loopback device e.g ~~loop3p1~~.		NOTE: Replace loopXp1 with the automatically allocated loopback device (e.g loop0p1).
	$ sudo mkdir /mnt/wic-p1		$ sudo mkdir /mnt/wic-p1
	$ sudo mount /dev/mapper/loopXp1 /mnt/wic-p1		$ sudo mount /dev/mapper/loopXp1 /mnt/wic-p1
Line 172:		Line 172:
	$ sudo cp workspace/sources/linux-yocto/arch/x86/boot/bzImage /mnt/wic-p1		$ sudo cp workspace/sources/linux-yocto/arch/x86/boot/bzImage /mnt/wic-p1
	Then unmount and unkpartx...		Then unmount and unkpartx...
	NOTE: Replace loopX with the automatically allocated loopback device e.g ~~loop3~~.		NOTE: Replace "loopX" with the automatically allocated loopback device from earlier (e.g "loop0").
	$ sudo umount /mnt/wic-p1		$ sudo umount /mnt/wic-p1
	$ sudo kpartx -d /dev/loopX		$ sudo kpartx -d /dev/loopX

Scottrif: /* Create image with new kernel */

2017-08-09T21:43:58Z

Create image with new kernel

← Older revision		Revision as of 21:43, 9 August 2017
Line 155:		Line 155:
	$ make -C workspace/sources/linux-yocto -j4		$ make -C workspace/sources/linux-yocto -j4
	=== Create image with new kernel ===		=== Create image with new kernel ===
	Normally you'd make a new image with <tt>devtool build-image</tt> but this can take a minute or so and messes with the kernel source folder. A faster option is to use kpartx to splice the new kernel into the image you have already built. If your build system does not have kpartx installed, be sure you install it.		Normally you'd make a new image with <tt>devtool build-image</tt> but this can take a minute or so and messes with the kernel source folder. A faster option is to use kpartx to splice the new kernel into the image you have already built. NOTE: If your build system does not have kpartx installed, be sure you install it.

	First make a copy of your wic file in say /tmp		First make a copy of your wic file in say /tmp
	$ cp tmp/deploy/images/genericx86-64/core-image-minimal-genericx86-64.wic /tmp		$ cp tmp/deploy/images/genericx86-64/core-image-minimal-genericx86-64.wic /tmp
	Then create loopback devices for each partition in wic file.		Then create loopback devices for each partition in wic file.
	NOTE: The first unused loopback device (loopX) will be automatically allocated e.g ~~loop3~~.		NOTE: The first unused loopback device (loopX) will be automatically allocated. This example uses "X". You need to use the actual loopback device (e.g. "loop0").
	$ sudo kpartx -v -a /tmp/core-image-minimal-genericx86-64.wic		$ sudo kpartx -v -a /tmp/core-image-minimal-genericx86-64.wic
	add map loopXp1 (253:6): 0 47446 linear /dev/loopX 2048		add map loopXp1 (253:6): 0 47446 linear /dev/loopX 2048

Todor Minchev: /* Create image with new kernel */

2017-08-09T21:41:01Z

Create image with new kernel

← Older revision		Revision as of 21:41, 9 August 2017
Line 166:		Line 166:
	add map loopXp3 (253:8): 0 90112 linear /dev/loopX 170556		add map loopXp3 (253:8): 0 90112 linear /dev/loopX 170556
	Kernel is in the first device, so let's mount /dev/mapper/loopXp1 to take a look		Kernel is in the first device, so let's mount /dev/mapper/loopXp1 to take a look
			NOTE: Replace loopXp1 with the automatically allocated loopback device e.g loop3p1.
	$ sudo mkdir /mnt/wic-p1		$ sudo mkdir /mnt/wic-p1
	$ sudo mount /dev/mapper/loopXp1 /mnt/wic-p1		$ sudo mount /dev/mapper/loopXp1 /mnt/wic-p1
Line 171:		Line 172:
	$ sudo cp workspace/sources/linux-yocto/arch/x86/boot/bzImage /mnt/wic-p1		$ sudo cp workspace/sources/linux-yocto/arch/x86/boot/bzImage /mnt/wic-p1
	Then unmount and unkpartx...		Then unmount and unkpartx...
			NOTE: Replace loopX with the automatically allocated loopback device e.g loop3.
	$ sudo umount /mnt/wic-p1		$ sudo umount /mnt/wic-p1
	$ sudo kpartx -d /dev/loopX		$ sudo kpartx -d /dev/loopX