CM-QS600: Linux: Kernel - Revision history

Ilya: /* Git clone */

2015-11-09T12:42:14Z

‎Git clone

Grinberg: /* WiFi */

2015-07-07T11:03:51Z

‎WiFi

Show changes

Ilya: Undo revision 10602 by Ilya (Talk)

2015-02-25T07:39:02Z

Undo revision 10602 by Ilya (Talk)

Ilya: /* Git clone */

2014-12-24T12:22:23Z

‎Git clone

Igor: /* Overview */

2014-11-04T11:37:38Z

‎Overview

Grinberg: /* Flashing LK-bootable image on storage devices */

2014-09-29T08:40:01Z

‎Flashing LK-bootable image on storage devices

Grinberg: /* Flashing LK-bootable image on storage device */

2014-08-05T15:51:31Z

‎Flashing LK-bootable image on storage device

New page

== Overview ==
Linux kernel for CM-QS600 modules provide support for on-board peripherals and abstracts the functionality provided by the hardware.
Current support coverage is specified at [http://compulab.co.il/operating-systems-and-drivers-for-cm-qs600-and-sbc-qs600/ O/S support coverage map] page.
CompuLab provides ready-to-run binary kernel images, and source code of the modifications and additions made to the Linux kernel to work properly with CM-QS600 modules.

== Building kernel for CM-QS600 ==
=== Cross-Compiler ===
There are several options for cross-compilation toolchain setup. You can either compile your cross-compiler or use an already built cross-compiler. The cross-compiler should support the ARM embedded-application binary interface ("[http://en.wikipedia.org/wiki/Application_binary_interface#EABI EABI]")
* Pre-built toolchain (recommended):
** [http://www.mentor.com/embedded-software/sourcery-tools/sourcery-codebench/editions/lite-edition/ Sourcery CodeBench Lite]
* Tools for creating cross-compilers:
** [http://crosstool-ng.org/ Crosstool-ng]: Builds a cross-compiler from source. Non-distribution specific.
** [http://www.gentoo.org/proj/en/base/embedded/handbook/index.xml?part=1&chap=4 Crossdev]: Gentoo's cross-compiler builder. Needs Gentoo.

=== Getting kernel sources ===
We assume that you have created {{filename|/home/development/cm-qs600/kernel}} directory for CM-QS600 kernel development.

==== Git clone ====
* Install [http://git-scm.com/ git] version control system.
* Create a clone of linux kernel tree
<pre>
cd /home/development/cm-qs600/kernel
git clone git://codeaurora.org/kernel/msm linux-cm-qs600
</pre>
* Create a branch for CM-QS600 development. The CM-QS600 patches are generated vs. LNX.LA.2.7-06310-8960.0 tag (c4f1f8cec1e3c7e3526f6666939f22d23fcd8714 commit) in the Linux tree. It is recommended to use exactly the same baseline to avoid merge conflicts.
<pre>
cd /home/development/cm-qs600/kernel/linux-cm-qs600
git checkout -b cm-qs600-dev LNX.LA.2.7-06310-8960.0
</pre>
* Apply the CM-QS600 patch
<pre>
git apply /path/to/cm-qs600-linux/kernel/linux-3.4.0-06310-cm-qs600-1.patch
</pre>

=== Building the kernel ===
<pre>
export ARCH=arm
export CROSS_COMPILE=arm-none-linux-eabi-
make cm_qs600_defconfig
make menuconfig
make && INSTALL_MOD_PATH=/home/development/cm-qs600/rootfs make modules_install
</pre>

In the example above:

* The Linux kernel image {{filename|zImage}} will be created in {{filename|/home/development/cm-qs600/kernel/linux-cm-qs600/arch/arm/boot}}
* The loadable kernel modules will be installed into the {{filename|/home/development/cm-qs600/rootfs/lib/modules}} directory.

When the CM-QS600 is booted with the kernel image and Device Tree binary created as described above and with networked root filesystem at {{filename|/home/development/cm-qs600/rootfs/}}, the system will be able to load the kernel modules properly, thus avoiding module version problems.

== Running developer kernel ==
CM-QS600 currently uses [https://www.codeaurora.org/blogs/little-kernel-based-android-bootloader Little Kernel] (LK) based application [http://forum.xda-developers.com/wiki/Bootloader bootloader].
The main aim of the application bootloader (LK) is loading and executing boot images from CM-QS600 storage device.
The LK supports USB driver and fastboot protocol that enable obtaining developer images from remote host machine over USB connection.
Images are obtained over USB can be either executed on the device or flashed onto main storage device (e.g. MMC, eMMC).

=== Getting Fastboot ===
CM-QS600 board comes with [http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro fastboot] support, which means that the application bootloader (LK) implements the fastboot protocol.
There are two sides to using fastboot
* a host machine side,
* and a target device side connected to the host via a USB cable.

In general fastboot is provided within the [http://developer.android.com/sdk/index.html Android SDK].
Also some Linux disributions provide fastboot within their package repositories.
For example, on Ubuntu platform, fastboot may be obtained via {{parameter|android-tools-fastboot}} package.

=== Booting a developer kernel ===
Once a custom developer kernel image is built, it can be booted on CM-QS600.
To boot CM-QS600 with a custom kernel image run the following fastboot command on the host machine:
<pre>
fastboot boot -c <cmdline> -b 0x80200000 /home/development/cm-qs600/kernel/linux-cm-qs600/arch/arm/boot/zImage
</pre>

=== Preparing LK-bootable image ===
Usually LK deals with special formatted {{filename|boot.img}} images.
Such image consists of boot header, kernel image, ramdisk and second stage images. Header and kernel sections.
* Boot header describes the {{filename|boot.img}} image layout, can carry other useful data, like board name and kernel command line.
* Kernel is a required part of the {{filename|boot.img}} file.
* Ramdisk and Second stage images are optional.
*: {{Note|CM-QS600 default Linux does not use either Ramdisk or Second stage images.}}

A special utility named {{cmd|mkbootimg}} is used to create {{filename|boot.img}} files.
In general {{cmd|mkbootimg}} is provided within the [http://developer.android.com/sdk/index.html Android SDK].
Alternatively you can use a pre-built binary provided within the [http://compulab.co.il/products/computer-on-modules/cm-qs600/#devres CM-QS600 Linux package].
To create {{filename|boot.img}} using a custom developer kernel image run the following command on the host machine:
<pre>
/path/to/cm-qs600-linux/utilities/mkbootimg/linux-x86/mkbootimg \
--kernel /home/development/cm-qs600/kernel/linux-cm-qs600/arch/arm/boot/zImage \
--ramdisk NONE --cmdline <cmdline> --base 0x80200000 --pagesize 2048 --output /home/development/cm-qs600/output/boot.img
</pre>
In the example above the LK-bootable image {{filename|boot.img}} will be created in the {{filename|/home/development/cm-QS600/output}} directory.
We assume this directory is created to hold custom bootable images.

=== Booting an LK-bootable image ===
Once a custom bootable image is created, it can be booted on CM-QS600.
To boot CM-QS600 with a custom {{filename|boot.img}} run the following fastboot command on the host machine:
<pre>
fastboot boot /home/development/cm-QS600/output/boot.img
</pre>

=== Flashing LK-bootable image on storage devices ===
Once a custom bootable image is created, it can be flashed on the CM-QS600 storage device (e.g. MMC, eMMC).
<pre>
fastboot flash boot /home/development/cm-QS600/output/boot.img
</pre>

: {{Warning|It is strongly recommended to test the {{filename|boot.img}} image priror to flashing it onto the storage device!}}

== See also ==
* [[CM-QS600: Linux: Getting started]]
* [[CM-QS600: Linux: Debian]]

[[Category:Linux]]
[[Category:CM-QS600]]

@@ Line 31: / Line 31: @@
 * Apply the CM-QS600 patch
 <pre>
-git apply /path/to/cm-qs600-linux/kernel/linux-3.4.0-14.10-cm-qs600-3.3.patch
+git apply /path/to/cm-qs600-linux/kernel/linux-3.4.0-14.10-cm-qs600-3.4.patch
 </pre>

@@ Line 24: / Line 24: @@
 git clone git://git.linaro.org/landing-teams/working/qualcomm/kernel.git
 </pre>
-* Create a branch for CM-QS600 development. The CM-QS600 patches are generated vs. ubuntu-ifc6410-14.09 tag (d392f534aee60425fb23868c1164bfbe99e6d52b commit) in the Linux tree. It is recommended to use exactly the same baseline to avoid merge conflicts.
+* Create a branch for CM-QS600 development. The CM-QS600 patches are generated vs. ubuntu-ifc6410-14.10 tag (602a30a57d9d3807df758221c2224e64a29e6fc7 commit) in the Linux tree. It is recommended to use exactly the same baseline to avoid merge conflicts.
 <pre>
 cd /home/development/cm-qs600/kernel/linux-cm-qs600
-git checkout -b cm-qs600-dev ubuntu-ifc6410-14.09
+git checkout -b cm-qs600-dev ubuntu-ifc6410-14.10
 </pre>
 * Apply the CM-QS600 patch
 <pre>
-git apply /path/to/cm-qs600-linux/kernel/linux-3.4.0-14.09-cm-qs600-2.patch
+git apply /path/to/cm-qs600-linux/kernel/linux-3.4.0-14.10-cm-qs600-3.patch
 </pre>

@@ Line 14: / Line 14: @@
 === Getting kernel sources ===
-The CM-QS600 Linux kernel is based on the Snapdragon 600 Linux Platform Ubuntu-based [http://releases.linaro.org/14.09/ubuntu/ifc6410 release] by Linaro.
+The CM-QS600 Linux kernel is based on the Snapdragon 600 Linux Platform Ubuntu-based [http://releases.linaro.org/14.10/ubuntu/ifc6410 release] by Linaro.
 We assume that you have created {{filename|/home/development/cm-qs600/kernel}} directory for CM-QS600 kernel development.
@@ Line 90: / Line 90: @@
       --ramdisk NONE --cmdline <cmdline> --base 0x80200000 --pagesize 2048 --output /home/development/cm-qs600/output/boot.img
 </pre>
-In the example above the LK-bootable image {{filename|boot.img}} will be created in the {{filename|/home/development/cm-QS600/output}} directory.
+In the example above the LK-bootable image {{filename|boot.img}} will be created in the {{filename|/home/development/cm-qs600/output}} directory.
 We assume this directory is created to hold custom bootable images.
@@ Line 97: / Line 97: @@
 To boot CM-QS600 with a custom {{filename|boot.img}} run the following fastboot command on the host machine:
 <pre>
-fastboot boot /home/development/cm-QS600/output/boot.img
+fastboot boot /home/development/cm-qs600/output/boot.img
 </pre>
@@ Line 104: / Line 104: @@
 Once a custom bootable image is created, it can be flashed on the CM-QS600 storage device (e.g. MMC, eMMC).
 <pre>
-fastboot flash boot /home/development/cm-QS600/output/boot.img
+fastboot flash boot /home/development/cm-qs600/output/boot.img
 </pre>

@@ Line 1: / Line 1: @@
 == Overview ==
-Linux kernel for CM-QS600 modules provide support for on-board peripherals and abstracts the functionality provided by the hardware.
+Linux kernel for the CompuLab CM-QS600 System-on-Module / Computer-on-Module provides support for on-board peripherals and abstracts the functionality provided by the hardware.
 Current support coverage is specified at [http://compulab.co.il/operating-systems-and-drivers-for-cm-qs600-and-sbc-qs600/ O/S support coverage map] page.
 CompuLab provides ready-to-run binary kernel images, and source code of the modifications and additions made to the Linux kernel to work properly with CM-QS600 modules.

@@ Line 14: / Line 14: @@
 === Getting kernel sources ===
 We assume that you have created {{filename|/home/development/cm-qs600/kernel}} directory for CM-QS600 kernel development.
@@ Line 21: / Line 22: @@
 <pre>
 cd /home/development/cm-qs600/kernel
-git clone git://codeaurora.org/kernel/msm linux-cm-qs600
+git clone git://git.linaro.org/landing-teams/working/qualcomm/kernel.git
 </pre>
-* Create a branch for CM-QS600 development. The CM-QS600 patches are generated vs. LNX.LA.2.7-06310-8960.0 tag (c4f1f8cec1e3c7e3526f6666939f22d23fcd8714 commit) in the Linux tree. It is recommended to use exactly the same baseline to avoid merge conflicts.
+* Create a branch for CM-QS600 development. The CM-QS600 patches are generated vs. ubuntu-ifc6410-14.09 tag (d392f534aee60425fb23868c1164bfbe99e6d52b commit) in the Linux tree. It is recommended to use exactly the same baseline to avoid merge conflicts.
 <pre>
 cd /home/development/cm-qs600/kernel/linux-cm-qs600
-git checkout -b cm-qs600-dev LNX.LA.2.7-06310-8960.0
+git checkout -b cm-qs600-dev ubuntu-ifc6410-14.09
 </pre>
 * Apply the CM-QS600 patch
 <pre>
-git apply /path/to/cm-qs600-linux/kernel/linux-3.4.0-06310-cm-qs600-1.patch
+git apply /path/to/cm-qs600-linux/kernel/linux-3.4.0-14.09-cm-qs600-2.patch
 </pre>
@@ Line 47: / Line 48: @@
 * The loadable kernel modules will be installed into the {{filename|/home/development/cm-qs600/rootfs/lib/modules}} directory.
-When the CM-QS600 is booted with the kernel image and Device Tree binary created as described above and with networked root filesystem at {{filename|/home/development/cm-qs600/rootfs/}}, the system will be able to load the kernel modules properly, thus avoiding module version problems.
+When the CM-QS600 is booted with the kernel image created as described above and with networked root filesystem at {{filename|/home/development/cm-qs600/rootfs/}}, the system will be able to load the kernel modules properly, thus avoiding module version problems.
 == Running developer kernel ==
@@ Line 100: / Line 101: @@
 === Flashing LK-bootable image on storage devices ===
 Once a custom bootable image is created, it can be flashed on the CM-QS600 storage device (e.g. MMC, eMMC).
 <pre>
 fastboot flash boot /home/development/cm-QS600/output/boot.img
 </pre>
 == See also ==