Changes

Linux Kernel 4.9.y

94 bytes added, 10:11, 7 May 2018

no edit summary

=Introduction=

This article is for specific 2.6.37.y Linux kernel branch series. All the steps has been tested with [http://releases.ubuntu.com/12.04/ubuntu-12.04.5-desktop-amd64.iso Ubuntu 12.04 64b] and [http://labs.isee.biz/index.php/How_to_setup_a_cross_compiler#IGEP_OMAP3 IGEP SDK Yocto Toolchain 1.2.2-3].

Depending the Kernel configuration used, 2.6.37.y series support the following IGEP OMAP3 Processor Boards:

==igep00x0_defconfig==

* IGEP v2 '''(WIFI/no WIFI)''' (IGEP0020'''RC''')

* IGEP COM MODULE / ELECTRON '''(WIFI/no WIFI)''' (IGEP0030'''RE''')

* IGEP COM MODULE / ELECTRON '''(no WIFI)'''

=Setup IGEP SDK~~Setup IGEP SDK~~ Yocto Toolchain 1.2.2-3===Install==Download - [http://www.isee.biz/support/downloads/item/igep-sdk-yocto-toolchain-1-2-2-3 isee.biz]

follow the next steps:

* Open a terminal* Located your downloaded file, in my case is inside /home/jdoe/Downloads:

<pre>jdoe@ubuntu ~ $ cd Downloads/</pre>* Extract binaries in root directory with root privileges

<pre>jdoe@ubuntu ~/Downloads $ sudo tar jxf igep-sdk-yocto-toolchain-*.tar.bz2 -C /</pre>* Make sure that binaries are installed correctly.

<pre>jdoe@ubuntu ~/Downloads $ ls /opt/poky/1.2 1.2.1 </pre>==Configure==Open a terminal and type:

<pre> export PATH=/opt/poky/1.2/sysroots/i686-pokysdk-linux/usr/bin/armv7a-vfp-neon-poky-linux-gnueabi:$PATH </pre>=Compiled binaries=

Binaries: latest stable kernel version IGEP OMAP3 devices is: '''2.6.37-12 (20161206)'''

||[http://downloads.isee.biz/pub/releases/linux_kernel/v2.6.37-12/ti-connectivity-wilink8-0.tar.gz ti-connectivity-wilink8-0]([http://downloads.isee.biz/pub/releases/linux_kernel/v2.6.37-12/ti-connectivity-wilink8-0.tar.gz.md5 md5sum)]

|}

=Build kernel from sources='''Download''' the latest stable version sources and follow next steps:

<pre>wget <a class="external free" href="http://downloads.isee.biz/pub/releases/linux_kernel/v2.6.37-12/linux-omap-2.6.37-12.tar.gz" target="_blank" rel="nofollow noreferrer noopener">http://downloads.isee.biz/pub/releases/linux_kernel/v2.6.37-12/linux-omap-2.6.37-12.tar.gz</a>

cd linux-omap-2.6.37-12

</pre>

Also, it could download from GIT Repositories ([http://git.isee.biz/ http://git.isee.biz/]) and test the last unstable version at your own risk (see "''Linux mainline tree (development)''" chapter in [index.php/The_Linux_kernel The Linux kernel])

==Important procedures==

* Remove rootfs modules binaries from any previous Kernel

* If you switch to another configuration, clean kernel sources with command: make mrproper

==~~igep00x0_defconfig~~igep00x0_defconfig=='''Configure''' Linux kernel for IGEP OMAP3 old Marvell WIFI:

<pre>make ARCH=arm igep00x0_defconfig

</pre>

Then '''build''' the kernel and kernel modules. The result will be an ''zImage'' file in arch/arm/boot directory. Execute:

<pre>make ARCH=arm CROSS_COMPILE=[your cross compiler] zImage modules

</pre>

For example, if you are using IGEP SDK Yocto Toolchain then you should execute following cmdline:

<pre>make ARCH=arm CROSS_COMPILE=arm-poky-linux-gnueabi- zImage modules

</pre>

You can '''install''' the kernel image to your target boot

<pre>cp arch/arm/boot/zImage /media/boot/zImage

</pre>

You can '''install''' the kernel modules to your target rootfs

<pre>make ARCH=arm modules_install INSTALL_MOD_PATH=[path to your target rootfs]</pre>

=Kernel Parameters=This chapter describes some [index.php/How_do_I_edit_my_kernel_command_line kernel command line] parameters you can pass to the kernel during system startup. They also depend on the presence of the hardware with which they are associated.

The '''board.ei485''' parameter allows to use UART1 as RS232 port instead of EI485

<pre> board.ei485= [yes, no] Format: ~~<string>~~

no: disable ei485, use UART1 as RS232, supported by igep0020

default: yes

</pre>

The '''buddy''' parameter allows enable or disable expansion boards

<pre> buddy= [igep0022, base0010] Format: ~~<string>~~

igep0022: enable expansion board, supported by igep0020

board

default: none

</pre>

The '''buddy.revision''' parameter allows to pass hardware revision for buddy boards

<pre> buddy.revision= [A, B] Format: ~~<string>~~

A: enable hardware buddy revision A, only available for base0010

B: enable hardware buddy revision B, only available for base0010

default: A

</pre>

The '''buddy.modem''' parameter allows enable or disable modem

<pre> buddy.modem= [yes] Format: ~~<string>~~

yes: enable modem on buddy board, supported by igep0022 expansion board.

default: none

</pre>

==Scenarios==Consider the following situations:

'''Scenario A.''' You have and IGEP0020 board plus IGEP0022 expansion board, then you should add in your [index.php/How_do_I_edit_my_kernel_command_line kernel command line]

<pre>buddy=igep0022

</pre>

Optionally, to enable the IGEP0022 modem which is disabled by default you should add in your [index.php/How_do_I_edit_my_kernel_command_line kernel command line]

<pre>buddy=igep0022 buddy.modem=yes

</pre>

NOTE: UART2 can be used for bluetooth OR modem in expansion board but NOT at same time. They are INCOMPATIBLE.

'''Scenario B.''' You have and IGEP0030 board plus BASE0010 expansion board, then you should add in your [index.php/How_do_I_edit_my_kernel_command_line kernel command line]

<pre>buddy=base0010

</pre>

'''Scenario C.''' You have and IGEP0030 board plus BASE0010 Rev. B expansion board, then you should add in your [index.php/How_do_I_edit_my_kernel_command_line kernel command line]

<pre>buddy=base0010 buddy.revision=B

</pre>

'''Scenario D.''' You have and IGEP0032 board plus BASE0010 Rev. B expansion board, then you should add in your [index.php/How_do_I_edit_my_kernel_command_line kernel command line]

<pre>buddy=base0010 buddy.revision=B

</pre>

'''Scenario E.''' You have and IGEP0030 board plus ILMS0015 expansion board, then you should add in your [index.php/How_do_I_edit_my_kernel_command_line kernel command line]

<pre>buddy=ilms0015

</pre>

=Layout=

Machine specific files are located in '''arch/arm/mach-omap2/''' directory with name '''board-igep*.c''' :

* '''exp-ilms0015.c''': For ILMS0015 expansion board

=Adding New Expansion Boards=

This chapter is meant to be a starting point for people to learn how to add your own expansion board in three steps.

==Step 1: Add new expansion board file==

As you can see in Layout chapter, an expansion board is called exp-~~<your board name>~~.c and should be located in arch/arm/mach-omap2 directory, so the first step will be add a new file for your new expansion board. Following example creates a new expansion board file called exp-dummy.c (arch/arm/mach-omap2/exp-dummy.c)

<pre> #include <linux/kernel.h>

Try to change rootfs owner from root to your username.

<pre> sudo chown ~~<username>~~ -R /media/rootfs</pre>

==wlcore: Unknown symbol==

Probably, you didn't erase old module binaries from rootfs. Open IGEP terminal and type:

Francesc Megias

560

edits

Personal tools

Search

Namespaces

Views

Export pages

Actions

Changes

From IGEP - ISEE Wiki

Linux Kernel 4.9.y

Navigation menu

External Links

Special pages