Difference between revisions of "Building the Linux Kernel"

From wiki.emacinc.com
Jump to: navigation, search
m (Noted omissions and marked Buggy.)
Line 1: Line 1:
−
{{todo|Review (11.26.13-22:10->MD+)(12.10.13-14:45->MG+);(12.17.13-12:10->KY+);(03.04.14-16:30->BS-);(03.26.14-17:10->BS+);(11.06.15-16:30->MG+)|Mike Dean|project=md,oe 4,oe 5,Review,mg,ky,bs}}
+
{{todo|Buggy (11.26.13-22:10->MD+)(12.10.13-14:45->MG+);(12.17.13-12:10->KY+);(03.04.14-16:30->BS-);(03.26.14-17:10->BS+);(11.06.15-16:30->MG+);(11.06.15-17:15->MD-)|Mike Dean|project=md,oe 4,oe 5,Buggy,mg,ky,bs}}
  
 
{{#seo:
 
{{#seo:
Line 33: Line 33:
 
1. Copy the default configuration file to the same directory as the kernel source tree and kernel-build-cross.sh and rename it defconfig.  
 
1. Copy the default configuration file to the same directory as the kernel source tree and kernel-build-cross.sh and rename it defconfig.  
  
−
* The kernel-build-cross script accepts the SOURCE_TREE as the first argument and either config or build as the second argument. Optionally, a third argument, BUILD_SUFFIX may be supplied as a suffix to add to the build directory.BUILD_SUFFIX is commonly used to add a date tag or machine name to a build.
+
* The kernel-build-cross script accepts the SOURCE_TREE as the first argument and either config or build as the second argument. Optionally, a third argument, BUILD_SUFFIX may be supplied as a suffix to add to the build directory. BUILD_SUFFIX is commonly used to add a date tag or machine name to a build.
  
−
<syntaxhighlight lang="bash">
+
{{cli | username=developer | hostname=ldc |./kernel-build-cross.sh linux-at91 config som9x25}}
−
developer@ldc:~$ ./kernel-build-cross.sh linux-at91 config som9x25
 
−
</syntaxhighlight>
 
  
 
* The kernel menu-driven configuration utility will be displayed. Features can be selected/deselected to be built into the kernel. Some features can be built as a loadable module, denoted by < >, and not built directly into the kernel.  
 
* The kernel menu-driven configuration utility will be displayed. Features can be selected/deselected to be built into the kernel. Some features can be built as a loadable module, denoted by < >, and not built directly into the kernel.  
−
 
+
{{ warning | Disabling  or modularizing some kernel features may prevent the kernel from starting correctly or at all. }}
−
{{ imbox | type = speedy | style = margin-bottom: 0.5em; | text = Disabling  or modularizing some kernel features may prevent the kernel from starting correctly or at all. }}
 
  
 
Use the space bar to select an option or the 'm' key to configure the selected option as a module. Select <code>Exit</code> to close the kernel configuration menu and save the configuration to the newly created build directory. When the same build-suffix is used for subsequent builds, this configuration will be used.  
 
Use the space bar to select an option or the 'm' key to configure the selected option as a module. Select <code>Exit</code> to close the kernel configuration menu and save the configuration to the newly created build directory. When the same build-suffix is used for subsequent builds, this configuration will be used.  
Line 49: Line 46:
  
 
<cl>
 
<cl>
−
1. Run the kernel-build-cross script again with the build option this time using the same build-suffix used in the configuration step.  
+
1. Run the kernel-build-cross script again with the build option, this time using the same build-suffix used in the configuration step.  
  
−
<syntaxhighlight lang="bash">
+
{{cli | username=developer | hostname=ldc |./kernel-build-cross.sh linux-at91 build som9x25}}
−
developer@ldc:~$ ./kernel-build-cross.sh linux-at91 build som9x25
 
−
</syntaxhighlight>
 
  
 
* The kernel will begin compiling now. This will take several minutes to complete depending on the kernel configuration and the speed of the development machine. Only move on to the next step if the build completes with no errors.
 
* The kernel will begin compiling now. This will take several minutes to complete depending on the kernel configuration and the speed of the development machine. Only move on to the next step if the build completes with no errors.
Line 59: Line 54:
 
* The new kernel image will be in the <code>build-3.10.0-som9x25/Install/boot</code> directory called zImage. For the 3.10 and later device tree enabled kernels, the desired device tree blob needs to be appended to the kernel.  
 
* The new kernel image will be in the <code>build-3.10.0-som9x25/Install/boot</code> directory called zImage. For the 3.10 and later device tree enabled kernels, the desired device tree blob needs to be appended to the kernel.  
  
−
<syntaxhighlight lang="bash">
+
{{clo}}
−
developer@ldc:~$ cd build-3.10.0-som9x25/Install/boot
+
{{clio | username=developer | hostname=ldc |cd build-3.10.0-som9x25/Install/boot}}
−
developer@ldc:~$ cat zImage-3.10.0 som-9x25-150es.dtb > zImage-boot
+
{{clio | username=developer | hostname=ldc |cat zImage-3.10.0 som-9x25-150es.dtb > zImage-boot}}
−
</syntaxhighlight>
+
{{clos}}
  
 
This is the image that will get loaded onto the board and executed by the bootloader. To load the new kernel onto the target machine, see the [[Loading Linux Kernels Onto a Board]] page.
 
This is the image that will get loaded onto the board and executed by the bootloader. To load the new kernel onto the target machine, see the [[Loading Linux Kernels Onto a Board]] page.
Line 76: Line 71:
 
1. Copy the archive to the root of the filesystem of the target machine
 
1. Copy the archive to the root of the filesystem of the target machine
  
−
<syntaxhighlight lang="bash">
+
{{cli | username=developer | hostname=ldc |scp build-3.10.0-som9x25/Install/modules.tar.gz root@1IP_ADDRESS:/ }}
−
developer@ldc:~$ scp build-3.10.0-som9x25/Install/modules.tar.gz root@1IP_ADDRESS:/  
 
−
</syntaxhighlight>
 
  
 
* Log onto the target machine
 
* Log onto the target machine
  
−
<syntaxhighlight lang="bash">
+
{{cli | username=developer | hostname=ldc |ssh root@IP_ADDRESS}}
−
developer@ldc:~$ ssh root@IP_ADDRESS</syntaxhighlight>
 
  
 
* Extract the kernel modules archive and force the kernel to reload the modules. Make sure that the root flash is mounted read/write before extracting.
 
* Extract the kernel modules archive and force the kernel to reload the modules. Make sure that the root flash is mounted read/write before extracting.
  
−
<syntaxhighlight lang="bash">
+
{{clo}}
−
root@som9x25:~# cd /
+
{{clio |cd /}}
−
root@som9x25:~# tar xzvf modules.tar.gz
+
{{clio |tar xzvf modules.tar.gz}}
−
root@som9x25:~# depmod -a
+
{{clio |depmod -a}}
−
root@som9x25:~# reboot
+
{{clio |reboot}}
−
</syntaxhighlight>
+
{{clos}}
 
</cl>
 
</cl>
 +
 +
{{warning| Needs a conclusion}}
 +
 +
{{warning | Needs a Where to go Next}}
 +
 +
{{warning | Needs a Related Content}}
 +
 
<!--
 
<!--
 
[[Category:Custom Development]]
 
[[Category:Custom Development]]
 
-->
 
-->

Revision as of 17:16, 6 November 2015

TODO: {{#todo:Buggy (11.26.13-22:10->MD+)(12.10.13-14:45->MG+);(12.17.13-12:10->KY+);(03.04.14-16:30->BS-);(03.26.14-17:10->BS+);(11.06.15-16:30->MG+);(11.06.15-17:15->MD-)|Mike Dean|md,oe 4,oe 5,Buggy,mg,ky,bs}}

This page covers the process of configuring and compiling the Linux kernel using the EMAC kernel build script. This process assumes that you have already acquired the following software:

  1. EMAC Software Development Kit OE 4 or OE 5
  2. Linux kernel source for target hardware (provided via EMAC public GIT server )
  3. Kernel build script

The example below will assume that a kernel image for the SoM-9x25 module will be created, although the instructions apply to other hardware as well assuming that the correct SDK, kernel tree, and build script is used.


Setup

The steps below assume that the kernel-build-cross.sh script is located in the same directory as the kernel tree. Be sure to modify the environment.cfg.sh script for the correct architecture and EMAC OE version.

Configuring the Kernel

The first step for building the kernel is to configure it as desired. It is recommended to start with the kernel configuration file used by EMAC to build the kernel for the target device. Starting with EMAC OE 5, the kernel configuration can be obtained on a running board from /proc/config.gz. Please contact EMAC support for earlier EMAC OE versions.
The following are steps to configure the kernel:

  1. Copy the default configuration file to the same directory as the kernel source tree and kernel-build-cross.sh and rename it defconfig.

  2. The kernel-build-cross script accepts the SOURCE_TREE as the first argument and either config or build as the second argument. Optionally, a third argument, BUILD_SUFFIX may be supplied as a suffix to add to the build directory. BUILD_SUFFIX is commonly used to add a date tag or machine name to a build.

    developer@ldc:~# ./kernel-build-cross.sh linux-at91 config som9x25

  3. The kernel menu-driven configuration utility will be displayed. Features can be selected/deselected to be built into the kernel. Some features can be built as a loadable module, denoted by < >, and not built directly into the kernel.


    WARNING!
    Disabling or modularizing some kernel features may prevent the kernel from starting correctly or at all.


    Use the space bar to select an option or the 'm' key to configure the selected option as a module. Select Exit to close the kernel configuration menu and save the configuration to the newly created build directory. When the same build-suffix is used for subsequent builds, this configuration will be used.

Building the Kernel

  1. Run the kernel-build-cross script again with the build option, this time using the same build-suffix used in the configuration step.

    developer@ldc:~# ./kernel-build-cross.sh linux-at91 build som9x25

  2. The kernel will begin compiling now. This will take several minutes to complete depending on the kernel configuration and the speed of the development machine. Only move on to the next step if the build completes with no errors.

  3. The new kernel image will be in the build-3.10.0-som9x25/Install/boot directory called zImage. For the 3.10 and later device tree enabled kernels, the desired device tree blob needs to be appended to the kernel.

    developer@ldc:~# cd build-3.10.0-som9x25/Install/boot
    developer@ldc:~# cat zImage-3.10.0 som-9x25-150es.dtb > zImage-boot

    This is the image that will get loaded onto the board and executed by the bootloader. To load the new kernel onto the target machine, see the Loading Linux Kernels Onto a Board page.

    The build script will also create an archive of all of the modules created during the build process and place it in the build-3.10.0-som9x25/Install/ directory. The archive will be called modules.tar.gz.

Loading Kernel Modules

If the kernel is recompiled without changing the configuration or source code for any modules, it is not necessary to reload the modules archive. Alternatively, if a module was modified or added, it is only necessary to reload the modules archive. To reload the modules:

  1. Copy the archive to the root of the filesystem of the target machine

    developer@ldc:~# scp build-3.10.0-som9x25/Install/modules.tar.gz root@1IP_ADDRESS:/

  2. Log onto the target machine

    developer@ldc:~# ssh root@IP_ADDRESS

  3. Extract the kernel modules archive and force the kernel to reload the modules. Make sure that the root flash is mounted read/write before extracting.

    root@som9x25:~# cd /
    root@som9x25:~# tar xzvf modules.tar.gz
    root@som9x25:~# depmod -a
    root@som9x25:~# reboot



WARNING!
Needs a conclusion




WARNING!
Needs a Where to go Next




WARNING!
Needs a Related Content



Retrieved from "https://wiki.emacinc.com/index.php?title=Building_the_Linux_Kernel&oldid=5004"