Compiling the kernel
(→Preparations) |
|||
| Line 181: | Line 181: | ||
[[Category:HowTos]] | [[Category:HowTos]] | ||
| + | [[Category:MidgardWiki]] | ||
Revision as of 10:49, 6 June 2008
Introduction
This document describes how a 3rd party developer can compile, modify and deploy the linux kernel if (s)he really wants to. First thing to consider is whether your own kernel is really needed. Most additional functionality can be provided with modules dynamically loaded into original kernel provided by Nokia. This may be easier for you and also easier for other users to install on their devices. Only if your change conflicts with original Nokia configuration or new feature cannot be compiled as a module, new kernel is needed.
If you choose to compile only additional modules then use the original n770_defconfig configuration as a base and enable new functionality as modules. Make sure you use compatible compiler with the one used for original kernel (currently gcc 3.4) otherwise your modules may produce errors when inserting into the kernel. The best may be to use exactly the same one - see /proc/version on device or use the one suggested in Section 2.
If you choose to make a new kernel Section 2 describes the compilation procedure, Section 3 the modification procedure, and Section 4 the deployment procedure. The document finishes off by a section listing issues that should be taken into account when working with the kernel and Maemo.
Compiling the Kernel
The compilation procedure can be split into two phases; the preparation phase that needs to be done only once, and the actual compilation phase.
Preparations
A Scratchbox target with a compatible toolchain must be created in order to compile kernel images that can be used on the actual device. The following instructions assume that Scratchbox 0.9.8.5 has already been succesfully installed. In order to set up a target for kernel compilation, perform the following four steps:
1. Install a gcc 3.4 toolchain, for example this one
2. Start sbox and create a new target for kernel compilation
$ sbox-config -ct MAEMO_KERNEL
- select newly installed gcc 3.4 toolchain
- select qemu-arm as CPU transparency mode
- select debian devkit
3. Select the newly created target, install ARM rootstrap, and finish toolchain setup
$ sbox-config -st MAEMO_KERNEL $ sbox-config -er /scratchbox/packages/Maemo_Dev_Platform_RS_v1.1_arm.tgz $ sbox-config -cc $ sbox-config -cf
4. Edit /etc/apt/sources.list to contains the following lines
deb maemo1.1 free non-free deb-src maemo1.1 free non-free
The above lines should be adjusted as appropriate for newer versions of maemo, e.g. 2.0 or 2.1
5. Create a directory to work in
$ mkdir ~/kernel-build
Compilation
Now, after the target is properly set up, we are ready to compile the kernel. This is done by following these seven steps:
1. Select the Scrathbox target configured earlier, if not yet selected.
$ sbox-config -st MAEMO_KERNEL
2. Update package database
$ apt-get update
3. Go to the compilation directory
$ cd ~/kernel-build
4. Install kernel sources and debian tools for building the kernel image
$ fakeroot apt-get install kernel-source-2.6.12.3 kernel-package
The above command not work for me in maemo 2.1. I worked around this by installing only kernel source $ fakeroot apt-get install kernel-source-2.6.16 kernel-package should be in scratchbox toolbox
5. Get sources for su-18-kernel package
$ apt-get source su-18-kernel
6. Rebuild su-18-kernel package
$ cd su-18-kernel-2.6.12.3 $ dpkg-buildpackage -rfakeroot -uc -us -sa -d
7. Install the kernel image in Scratchbox target
$ fakeroot dpkg -i ../su-18-kernel_*.deb
Modifying Default Kernel Configuration
In order to modify the default kernel configuration, a few things needs to be done. Assuming that the kernel has been built at least once as described in Section 2, perform the following procedure to build a modified kernel for Maemo:
1. Edit ~/kernel-build/su-18-kernel-2.6.12.3/debian/rules so that modifications may be done
Make sure the following two lines are commented or removed completely:
- build-stamp section: tar jxf /usr/src/kernel-source-$(SOURCE_VERSION).tar.bz2
- clean section: rm -rf kernel-source-$(SOURCE_VERSION)
2. Change file permissions for default config file
$ chmod a+w ~/kernel-build/su-18-kernel-2.6.12.3/kernel-source-2.6.12.3/arch/arm/configs/n770_defconfig
3. Make your modifications to /kernel-build/su-18-kernel-2.6.12.3/kernel-source-2.6.12.3/arch/arm/configs/n770_defconfig
To make myself more comfortable with this step, I added a couple more steps:
- ) I copied n770_defconfig to .config and ran make oldconfig.
- ) then I copied .config back to n770_defconfig.
This made me more confident that the changes I made in n770_defconfig were correct.
4. Recompile the kernel image
$ cd su-18-kernel-2.6.12.3 $ dpkg-buildpackage -rfakeroot -uc -us -sa -d
5. Install the kernel image in Scratchbox target
$ fakeroot dpkg -i ../su-18-kernel_*.deb
Deploying the Kernel Onto the Device
The kernel kernel image is deployed onto the device by issuing the following command:
# flasher -f -k /scratchbox/users/<username>/targets/MAEMO_KERNEL/usr/share/osso/kernels/zImage-su-18-<yyyyww>
This command is executed outside Scratchbox, assuming that the flasher utility is in $PATH.
Or if you want to be safe, you can test boot it with: (without actually permanently modifying the kernel)
# flasher -l -b -k /scratchbox/users/<username>/targets/MAEMO_KERNEL/usr/share/osso/kernels/zImage-su-18-<yyyyww>
instead.
If that doesn't work (hangs indefinitely while trying to find device), try:
mount -t usbfs none /proc/bus/usb/
Things to Remember When Working with Linux Kernel and Maemo
Below is a list of things that should be taken into consideration when working with the Linux kernel and Maemo.
Modules and initfs
Your kernel image have to be compatible with modules in initfs image on the device. If you flash custom kernel image incompatible with modules in this initfs you may see constants reboots. This can be fixed either by making the kernel compatible (use same or very similar gcc compiler and kernel configuration) or by rebuilding initfs image with your version of modules. For a list of those essential modules see: /lib/modules/current in the initfs image or /mnt/initfs/lib/modules/current directly on the device. Also if you enabled some additional functionality as modules you may need to copy them manually to the initfs on the device (if there is free space) or better put them somewhere in the root filesystem.
Kernel Partition Size
The size of the kernel partition on the device is limited. When enabling additional features to be compiled directly into kernel the image may quite easily exceed the size of the partition and thus flashing an oversized image to the kernel partition may render the device useless. It is advised to use modules as much as possible to keep kernel size down and prevent this from happening. If this happens, see next item.
What To Do When Flashing Breaks the Device
For example, flashing an oversized kernel image renders the device useless. In order to get the device working again, select one of the following two options.
Flash Kernel Image from Maemo.org
You can install a fully working kernel image by installing the su-18-kernel image available on maemo.org. Issue the following command in Scratchbox:
$ apt-get install su-18-kernel
After this, flash the kernel image as instructed in Section 4.
Flash from Fiasco Image
The other way around the problem is to install the latest Fiasco image available from Nokia Support or maemo.org downloads. Please see this How To Flash from Linux How To for more information how to do this. You can use flasher to unpack firmware *.bin image and flash only kernel or initfs or both.
Serial Console
When hacking the kernel, you may need the serial console. You may have noticed an 11 pins conector (pad) in the battery compartment of the device:
1-2-3-4-5-6 -7-8-9-A-B-
Pin 9 is RxD (Nokia receive input) and pin A is TxD (Nokia transmit output). Pin 8 and 3 are the ground. The outputs are evidently 3.3v - Some used a USB-mobile phone cable as described in and to connect to the device.
On the N800 this connector contains only 7 pins and it located near the battery. Pin 7 is RxD (Nokia receive input) and pin 6 is TxD (Nokia transmit output). Pin 3 and 4 are the ground. It looks like pin 5 is connected to the battery over current indicator.
1 5 2 6 3 7 4
There is an other 4 Pin connector near on booth th n800 and n810. those are related to usb.(we did get some bus reset signals when playing with them)
1 2 3-4
Once your done with your cable, enable the R&D mode and set the serial console flag and connect via 8N1,115200.
$sudo ./flasher <del>enable-rd-mode </del>set-rd-flags=serial-console Password: Suitable USB device not found, waiting USB device found found at bus 002, device address 011 Found board Nokia 770 (F5) NOLO version 0.9.0 The device is now in R&D mode Set R&D flags: 0010