Personal tools

Log in

Changes

From IGEP - ISEE Wiki

Jump to: navigation, search

Linux Kernel 4.9.y

9,575 bytes removed, 16:34, 12 October 2023
→‎Prepare the environment
[[File:245px-Tux.svg.png|right|167x197px]]&nbsp; =<span id="Introduction" class="mw-headline">Introduction</span>What is Linux?=<span style="color: #808080;">This article Linux is for specific 2.6.37.y the result of merging the computational Kernel made by Linux kernel branch series. All Torval and the steps has been tested with [http://releases.ubuntu.com/12.04/ubuntuscheme present in any Unix operative system, Kernel was written from scratch by Linus and a loosely-12.04knit team of hackers across the Net.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]It aims towards POSIX standard and Single UNIX Specification compliance.</span>
It has all the features you would expect in a modern fully-fledged Unix, including true multitasking, virtual memory, shared libraries, demand loading, shared copy-on-write executables, proper memory management, and multistack networking including IPv4 and IPv6.
<span style="color: #808080;">Although originally developed first for 32-bit x86-based PCs (386 or higher), today Linux also runs on a multitude of other processor architectures, in both 32-and 64- </span>bit variants.
Para dar soporte =<span id="Introduction" class="mw-headline">Introduction</span>=<span style="color: #000000;">In order to build the Linux Kernel for IGEP PROCESSOR BOARDS it is recommended to cross-compile the kernel, that means to build the kernel in your HOST machine for a una nueva board basada en imx en el kernel es necesario tener un fichero de configuracion defconfig (.config) y  una dtbtarget architecture.</span>
Por defecto empezaremos con un defconfig ya creado por igep para procesadores imxTo [[Ubuntu 16.04 LTS Toolchain|Ubuntu_16.04]] there are two fundamental variables that the kernel uses to select the target architecture. Normally these values are guessed based on your build environment, but of course that environment here does not match our target embedded system, so we'll need to override them. The variables in question are:
* <div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code"u>''' ARCH'''<div class="codeContent panelContent pdl"/u><div id="highlighter_162759" class="syntaxhighlighter sh-confluence nogutter java">{| border="0" cellspacing="0" cellpadding="0"|-| class="code"|<div class="container" title="Hint''': double-click ''' The ARCH variable is the architecture you're targeting as the kernel knows it. For IGEP PROCESSOR BOARDS you'll set to select code"><div class=arm"line number1 index0 alt2"><code class="java plain">imx6_igep0046_defconfig</code>architecture.
* </divu>'''CROSS_COMPILE'''</divu>|}</div></div></div>Para que el kernel compile la dtb es necesario tener una dts con la configuración de los periféricos y los drivers que los gestionan,ademas de una anidación al dtsi del procesador correspondiente ''':''' Hopefully the CROSS_COMPILE variable is pretty self-explanatory. Set this to the prefix of your toolchain ( en este caso imx6 ya sea quadincluding the trailing dash "-"). So if your toolchain is invoked as say arm-linux-gnueabihf-gcc, dual, solo ...)just chop off that trailing gcc and that's what you use: '''arm-linux-gnueabihf-'''
En el caso de igep con procesadores imxThere is an additional variable, '''INSTALL_MOD_PATH''', which defines where the /lib directory will be created, and all the modules stored. While you don't have to transfer the kernel sources to your target device, if you build any modules, you'll want this directory.
<div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl"><div id="highlighter_265765" class="syntaxhighlighter sh-confluence nogutter java">{| border="0" cellspacing="0" cellpadding="0"|-| class="code"|<div class="container" title="HintThe general process that it has to be followed in order to compile your Linux Kernel is usually the same: double-click to select code"><div class="line number1 index0 alt2"><code class="java plain">DUAL</code>
# Clone the git from ISEE git with the latest stable version of the corresponding Linux Kernel.
# Select the corresponding branch inside the git repository.
# Select the correct default configuration (defconfig)
# Compile the Kernel Image, Device Tree and Modules of that configuration.
<div class="line number2 index1 alt1"><code class="java plain">imx6dl-igep-base0040ra1.dts</code></div><div classspan id="line number3 index2 alt2How_to_cross_compile_the_linux_kernel"><code class="java plain">imx6dlmw-igep-base0040rc2.dts</code></div><div class="line number4 index3 alt1"><code class="java plain">imx6dl-igep-base0040rd102.dts</code></div><div class="line number5 index4 alt2"> </div><div class="line number6 index5 alt1headline">Prepare the environment<code class="java plain">QUAD<br/code></div><div class="line number7 index6 alt2"span><code class="java plain">imx6q-igep-base0040ra1.dts</code></div><div class="line number8 index7 alt1"><code class="java plain">imx6q-igep-base0040rc2.dts<{{Message/code></div><div class="line number9 index8 alt2"><code classInformation Message|message="java plain">imx6q-igep-base0040rd102The following steps has been tested using '''Ubuntu 16.dts</code></div><div class="line number10 index9 alt1"> </div><div class="line number11 index10 alt2"><code class="java plain">GENERICA</code></div><div class="line number12 index11 alt1"><code class="java plain">imx6qdl-igep-base0040ra04''' and the '''4.dtsi</code></div><div class="line number13 index12 alt2"><code class="java plain">imx6qdl9 version''' of the '''arm-igeplinux-base0040rb.dtsi'''</code></div><div span class="line number14 index13 alt1"><code class="java plain">imx6qdl-igepmw-igep0046ra.dtsi</code></div><div class="line number15 index14 alt2headline"><code class="java plain">imx6qdl-igep-igep0046rc.dtsi'''gnueabihf''' compiler</codespan></div></div></div>|}</div></div></div>Las DTS están anidadas, esto quiere decir que se cogerá la dtb generada a partir de la .dts dependiendo del procesador que monte igep en este caso.}
Para que el kernel compile las First we have to set up the Cross Compiler correctly if it is necessary. In this [[Set Up the Cross Compiler|post]] there are some steps that can be followed in order to do it.dts en dtb se ha de añadir en el Makefile de arch/arm/boot/dts/
<div span class="code panel pdl confmw-macro output-block" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl"><div id="highlighter_599857" class="syntaxhighlighter sh-confluence nogutter javaheadline">{| border="0" cellspacing="0" cellpadding="0"|-| class="code"|<div class="container" title="HintIf it is necessary we can install this extra packages that could be necessaries: double-click to select code"><div class="line number1 index0 alt2"><code class="java plain">(dentro de dtb-$(CONFIG_SOC_IMX6Q) += \)</codespan>
<span class="mw-headline">sudo apt-get install libc6-armel-cross libc6-armhf-cross libc6-dev-armel-cross libncurses5-dev<br><br>sudo apt-get install lzop<br></span>
<span class="mw-headline">The next step is to clone the corresponding git repository. There are different git repositories depending on the model of the processor of the board. The following table shows the steps for each of the <span style="color: #000000;">IGEP PROCESSOR BOARDS</span>:<br data-attributes="%20/"></span>
<div {| class="line number2 index1 alt1contenttable sortable"><code classstyle="java spaceswidth: 890px;">   </code><code class="java plain">imx6dl-igep|-base0040rc2.dtb \</code></div><div class! style="line number3 index2 alt2width: 97px;"><code class|PROCESSOR! style="java spaceswidth: 324.217px;">    </code><code class|GIT REPOSITORY! style="java plainwidth: 275.783px;">imx6dl-igep|BRANCH|-base0040rd102.dtb \</code></div><div class| style="line number4 index3 alt1width: 97px;"><code class|DM3730| style="java spaceswidth: 324.217px;">    <|https://git.isee.biz/cgit/linux-kernel/code><code class="java plain">imx6qlinux-igepomap-base0040rc22.dtb \<6.git/code></div><div class| style="line number5 index4 alt2width: 275.783px;"><code class="java spaces">    </code><code class="java plain">imx6q|isee-igeplinux-base0040rd102v.4.9.dtb \</code></div>y</div></div>|-|}</div></div></div>=<span idstyle="Setup_IGEP_SDK_Yocto_Toolchain_1.2.2-3width: 97px;" class|AM335X| style="mw-headlinewidth: 324.217px;">Setup IGEP SDK<|https:/span><span id="Setup_IGEP_SDK_Yocto_Toolchain_1/git.2isee.2biz/cgit/linux-kernel/linux-3" class="mwomap-headline" 2.6.git/| style="colorwidth: #808080275.783px;"> Yocto Toolchain 1|isee-linux-v.4.29.2y|-3</span>===<span id| style="Installwidth: 97px;" class="mw-headline">Install</span>==|iMX6<span | style="colorwidth: #000000324.217px;">Download - [http|https://wwwgit.isee.biz/supportcgit/downloadslinux-kernel/itemlinux-imx.git/igep| style="width: 275.783px;"|isee-sdk-yocto-toolchain-1-2-2-3 iseeimx_4.9.11_1.0.biz]</span>0_ga
<span style="color: #000000;">follow the next steps:</span>|}
* <span style="colorTo get to desired branch we will use: #000000;">Open a terminal</span>* <span style="color: #000000;">Located your downloaded file, in my case is inside /home/jdoe/Downloads:</span>
<pre><span style="color: #000000;">jdoe@ubuntu ~ $ cd Downloads/</span></pre>* <span style="color: #000000;">Extract binaries in root directory with root privileges</span> git checkout [your_branch]
<pre>=<span styleid="How_to_cross_compile_the_linux_kernel" class="color: #000000;mw-headline">jdoe@ubuntu ~/Downloads $ sudo tar jxf igepCompile the Linux Kernel<br data-sdk-yocto-toolchain-*.tar.bz2 -C attributes="%20/"></span></pre>=* <span style="color: #000000;">Make sure that binaries are installed Once the development environment has been correctlyset up, the following steps can be followed in order to compile the Linux Kernel using a Cross Compiler.<br data-attributes="%20/"></span>
<pre><span style="color: #808080;"><span style="color: #000000;">jdoe@ubuntu ~/Downloads $ ls /opt/poky/1.2 1.2First of all, the default configuration ''(defconfig)'' has to be loaded.1</span> </span></pre>==<span id="Configure" class="mw-headline" style="color: #000000;">Configure</span>==<span style="color: #000000;">Open a terminal and typeIt can be done by writing the following command:</span>
<pre> <span style="color: #000000;"> export PATH<code class="java plain">make ARCH=/opt/poky/1.2/sysroots/i686-pokysdkarm CROSS_COMPILE=arm-linux/usr/bin/armv7a-vfpgnueabihf-neon-poky-linux-gnueabi:$PATH </span>[your_defconfig]</pre>=<span id="Compiled_binaries" class="mw-headline" style="color: #000000;"code>Compiled binaries</span>=<span class="mw-headline" style="color: #808080;">Binaries: latest stable kernel version In the following table it can be found the name of each default configuration associated to each IGEP OMAP3 devices isPROCESSORS BOARDS: '''2.6.37-12 (20161206)'''</span>
{| borderclass="1contenttable sortable" style="width: 888px;"
|-
!|<span style="colorwidth: #808080160px;">'''Platform'''</span>!|<span style="color: #808080;">'''Kernel source'''</span>BOARD!|<span style="colorwidth: #808080163px;">'''zImage binary (igep00x0_defconfig)'''</span>!|<span style="color: #808080;">'''Modules binaries (igep00x0_defconfig)'''</span>DEFCONFIG!|<span style="colorwidth: #808080527px;">'''zImage binary (igep00x0_wilink8_defconfig)'''</span>!|<span style="color: #808080;">'''Modules binaries (igep00x0_wilink8_defconfig)'''</span>!|<span style="color: #808080;">'''Compat Wireless source (only for igep00x0_wilink8_defconfig)'''</span>!|<span style="color: #808080;">'''Firmware binaries (only for igep00x0_wilink8_defconfig)'''</span>EXAMPLE
|-
||<span style="colorwidth: #808080160px;">IGEP00x0</span>|IGEPv5 OMAP5432||<span style="colorwidth: #808080163px;">|[httphttps://downloadsgit.isee.biz/pub/releases/linux_kernel/v2.6.37linux-12kernel/linux-omap-2.6.37/blob/isee-linux-12v.tar4.gz 29.6.37-12]([http:y/arch/downloads.isee.bizarm/pubconfigs/releases/linux_kernel/v2.6.37omap2plus_defconfig omap2plus_defconfig]| style="width: 527px;"|<span style="color: #000000;"><code class="java plain">make ARCH=arm CROSS_COMPILE=arm-12/linux-omap-2.6.37gnueabihf-12.tar.gz.md5 md5sum])omap2plus_defconfig  <br /></code></span>|-| style="width: 160px;"|IGEPv2 DM3730|<span style="colorwidth: #808080163px;">|[httphttps://downloadsgit.isee.biz/publinux-kernel/releases/linux_kernel/v2.6.37linux-12/zImageomap-2.6.37/blob/isee-12.bin zImagelinux-2v.64.37-129.bin] ([http:y/arch/downloads.isee.bizarm/pubconfigs/releases/linux_kernel/v2.6.37omap2plus_defconfig omap2plus_defconfig]| style="width: 527px;"|<span style="color: #000000;"><code class="java plain">make ARCH=arm CROSS_COMPILE=arm-12/zImagelinux-2.6.37gnueabihf-12.bin.md5 md5sum]) omap2plus_defconfig</code></span>|-| style="width: 160px;"|IGEP COM AQUILA AM335x|<span style="colorwidth: #808080163px;">|[httphttps://downloadsgit.isee.biz/publinux-kernel/releases/linux_kernel/v2.6.37linux-12/modulesomap-2.6.37/blob/isee-12.tar.gz moduleslinux-2v.64.37-12]([http://downloads9.isee.bizy/pubarch/releasesarm/linux_kernelconfigs/v2.6.37am335x_igep0034_defconfig am335x_igep0034_defconfig]| style="width: 527px;"|<span style="color: #000000;"><code class="java plain">make ARCH=arm CROSS_COMPILE=arm-12/moduleslinux-2.6.37gnueabihf-12.tar.gz.md5 md5sum)]am335x_igep0034_defconfig</code></span>|-| style="width: 160px;"|IGEP COM MODULE DM3730/AM3703|<span style="colorwidth: #808080163px;">|[httphttps://downloadsgit.isee.biz/pub/releases/linux_kernel/v2.6.37linux-12kernel/zImagelinux-2.6.37-12-wilink8.bin zImageomap-2.6.37/blob/isee-12linux-wilink8v.bin]([http://downloads4.isee9.bizy/pubarch/releasesarm/linux_kernelconfigs/v2.6.37omap2plus_defconfig omap2plus_defconfig]| style="width: 527px;"|<span style="color: #000000;"><code class="java plain">make ARCH=arm CROSS_COMPILE=arm-12/zImage-2.6.37linux-12gnueabihf-wilink8.bin.md5 md5sum])omap2plus_defconfig</code></span>|-| style="width: 160px;"|IGEP SMARC AM335x|<span style="colorwidth: #808080163px;">|[httphttps://downloadsgit.isee.biz/publinux-kernel/releases/linux_kernel/v2.6.37linux-12/modulesomap-2.6.37/blob/isee-12linux-wilink8v.tar4.gz modules-2.69.37-12-wilink8]([http:y/arch/downloads.isee.bizarm/pubconfigs/releases/linux_kernel/v2.6.37am335x_igep0034_defconfig am335x_igep0034_defconfig]| style="width: 527px;"|<span style="color: #000000;"><code class="java plain">make ARCH=arm CROSS_COMPILE=arm-12/modules-2.6.37linux-12gnueabihf-wilink8.tar.gz.md5 md5sum)] am335x_igep0034_defconfig</code></span>|-| style="width: 160px;"|IGEP SMARC iMX6S/DL/Q|<span style="colorwidth: #808080163px;">|[httphttps://downloadsgit.isee.biz/publinux-kernel/releaseslinux-imx/linux_kernelblob/v2isee-imx_4.69.37-12/compat-wireless-wilink8-011_1.tar.gz compat-wireless-wilink8-0]([http://downloads.isee.biz0_ga/pubarch/releasesarm/linux_kernelconfigs/v2.6.37imx6_igep0046_defconfig imx6_igep0046_defconfig]| style="width: 527px;"|<span style="color: #000000;"><code class="java plain">make ARCH=arm CROSS_COMPILE=arm-12/compatlinux-wirelessgnueabihf-wilink8-0.tar.gz.md5 md5sum]) imx6_igep0046_defconfig</code></span>|-|<span style="colorwidth: #808080160px;">|IGEP SMARC iMX6UL/ULL||[httphttps://downloadsgit.isee.biz/publinux-kernel/releaseslinux-imx/linux_kernelblob/v2isee-imx_4.69.37-12/ti-connectivity-wilink8-011_1.tar.gz ti-connectivity-wilink8-0]([http://downloads.isee.biz0_ga/pubarch/releasesarm/linux_kernelconfigs/v2.6.37imx6_igep0146_defconfig imx6_igep0146_defconfig]| style="width: 527px;"|<span style="color: #000000;"><code class="java plain">make ARCH=arm CROSS_COMPILE=arm-12/tilinux-connectivitygnueabihf-wilink8-0.tar.gz.md5 md5sum)] imx6_igep0146_defconfig</code></span>
|}
=<span id="Build_kernel_from_sources" class="mw-headline" style="colorOnce the default configuration has been loaded, it is time to compile the Linux Kernel. There are three important elements to compile: #000000;">Build kernel from sources</span>=<span style="color: #000000;">'''Download''' the latest stable version sources and follow next steps:</span>
<pre><span style="color* '''Image: #808080;">wget <a class="external free" href="http://downloads'''The kernel image.iseeThere are three several formats.biz/pub/releases/linux_kernel/v2.6.37-12/linux-omap-2.6.37-12.tar.gz" target="_blank" rel="nofollow noreferrer noopener">httpGenerally we will use the '''zImage'''://downloads.isee.biz/pub/releases/linux_kernel/v2.6.37-12/linux-omap-2.6.37-12.tar.gz</a>tar xzf linux-omap-2.6.37compressed version of the Linux kernel image that is self-12.tarextracting.gzcd linux-omap-2.6.37-12</span></pre><span style="color* '''DTBs: #000000;">Also'''Device tree binary, it could download from GIT Repositories ([http://gita low level device description, specific to your device.isee.biz/ http* '''Modules://git.isee.biz/]) and test the last unstable version at your own risk (see "''Linux mainline tree (development)''" chapter in [indexKernel Modules, pieces of code that can be loaded and unloaded into the kernel upon demand.php/The_Linux_kernel The Linux They extend the functionality of the kernel])</span>without the need to reboot the system. 
==<span id="Important_procedures" class="mw-headline" style="color: #000000;">Important procedures</span>==* <span style="color: #808080;">Remove rootfs modules binaries from any previous Kernel</span>* <span style="color: #808080;">If you switch In order to compile this three elements we have to another configuration, clean kernel sources with commandtype: make mrproper</span>
<pre><span style="color: #000000;">Para compilar el kernel se ha de seguir los siguientes pasos:<code class="java plain">make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- zImage dtbs modules</spancode></prespan>1- Descargar la rama correspondiente con git
2- Configurar el kernel con la minima configuracion que nos ofreceFinally we will find the resulting compiled Kernel in the '''''arch/arm/boot''''' folder:
<div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl"><div id="highlighter_902183" class="syntaxhighlighter sh-confluence nogutter java">{| border="0" cellspacing="0" cellpadding="0"|-* zImage: located in '''arch/arm/boot/zImage'''| class="code"|<div class="container" title="Hint* DTB: double-click to select code"><div class="line number1 index0 alt2"><code class="java plain">make ARCH=located in arch/arm CROSS_COMPILE=arm-linux-gnueabihf- imx6_igep0046_defconfi/boot/dts/.dtb. Depending of the board the dtb file will be different. In the following table it is detailed the corresponding dtb filename for each b''' <br /code>'''
</div>
</div>
|}</div>
</div>
</div>
3- Ejecutar el menuconfig para optimizar la configuracion a traves del menú.
<div {| class="code panel pdl confcontenttable sortable" style="width: 890px;"|-macro output! style="width: 281.467px;"|BOARD! style="width: 588.533px;"|DTB NAME|-block| style="width: 281.467px;" data-hasbody|IGEPv2 DM3730| style="truewidth: 588.533px;" data|[https://git.isee.biz/linux-kernel/linux-omap-2.6/blob/isee-linux-v.4.9.y/arch/arm/boot/dts/omap3-igep0020-rev-f.dts omap3-igep0020-macrorev-namef.dts]|-| style="codewidth: 281.467px;"><div class|IGEP COM MODULE DM3730/AM3703| style="codeContent panelContent pdlwidth: 588.533px;"><div id|[https://git.isee.biz/linux-kernel/linux-omap-2.6/blob/isee-linux-v.4.9.y/arch/arm/boot/dts/omap3-igep0030-rev-g.dts omap3-igep0030-rev-g.dts]|-| style="highlighter_965738width: 281.467px;" class|IGEP COM AQUILA AM335x| style="syntaxhighlighter shwidth: 588.533px;"|[https://git.isee.biz/linux-kernel/linux-omap-2.6/blob/isee-linux-v.4.9.y/arch/arm/boot/dts/am335x-base0033.dts am335x-base0033.dts]|-confluence nogutter java| style=">width: 281.467px;"|IGEPv5 OMAP5432{| borderstyle="0width: 588.533px;" cellspacing|[https://git.isee.biz/linux-kernel/linux-omap-2.6/blob/isee-linux-v.4.9.y/arch/arm/boot/dts/omap5-igep0050.dts omap5-igep0050.dts]|-| style="0width: 281.467px;" cellpadding|IGEP SMARC AM335x| style="0width: 588.533px;"|[https://git.isee.biz/linux-kernel/linux-omap-2.6/blob/isee-linux-v.4.9.y/arch/arm/boot/dts/am335x-igep-base0040.dts am335x-igep-base0040.dts]
|-
| classstyle="codewidth: 281.467px;"|<div classIGEP SMARC iMX6 Quad| style="containerwidth: 588.533px;" title="Hint|[https: double-click to select code"><div class="line number1 index0 alt2"><code class="java plain">make ARCH=arm CROSS_COMPILE=arm//git.isee.biz/linux-kernel/linux-gnueabihfimx/blob/isee- menuconfig<imx_4.9.11_1.0.0_ga/code> <arch/div><arm/div>|}<boot/div><dts/div></div>Guardar la configuracion del menuconfig en .config 4imx6q- Compilar la imagen los modulos y las dtb <div class="code panel pdl configep-macro outputbase0040rd102.dts imx6q-block" dataigep-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl"><div id="highlighter_56426" class="syntaxhighlighter sh-confluence nogutter java">{| border="0" cellspacing="0" cellpadding="0"base0040rd102.dts]
|-
| classstyle="codewidth: 281.467px;"|<div classIGEP SMARC iMX6 Dual Lite| style="containerwidth: 588.533px;" title="Hint|[https: double-click to select code"><div class="line number1 index0 alt2"><code class="java plain">make ARCH=arm CROSS_COMPILE=arm//git.isee.biz/linux-kernel/linux-gnueabihfimx/blob/isee- zImage modules dtbs<imx_4.9.11_1.0.0_ga/code> <arch/div><arm/div>|}<boot/div><dts/div></div>5imx6dl- Instalar en el rootfs los modulos del kernel que son cargables ( es decir que no estan builtigep-in) <div class="code panel pdl conf-macro output-block" database0040rd102.dts imx6dl-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl"><div id="highlighter_785157" class="syntaxhighlighter shigep-confluence nogutter java">{| border="0" cellspacing="0" cellpadding="0"base0040rd102.dts]
|-
| classstyle="codewidth: 281.467px;"|<div class="container" title="Hint: double-click to select code"><div class="line number1 index0 alt2"><code class="java plain">sudo make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- modules_install INSTALL_MOD_PATH=/opt/nfs-server/rootfs/ubuntu-xenial-armhf-base</code> </div></div>IGEP SMARC iMX6 Ultra Lite|}</div></div></div>'''Nota: Es muy importante que el INSTALL_MOD_PATH sea el correcto y de lugar justo al contenido que se esperaría en un sistema linux (usr, bin, etc, home, opt), este comando ademas se ha de ejecutar con sudo.''' '''Si éste comando falla, es muy probable que instale los modulos en el Host PC pudiendo dejar inservible el actual SO.''' ==<span id="Scenarios" class="mw-headline" style="color|[https: #000000;">Scenarios</span>==<span style="color: #000000;">Consider the following situations:</span> <span style="color: #000000;">'''Scenario Agit.''' You have and IGEP0020 board plus IGEP0022 expansion board, then you should add in your [indexisee.phpbiz/How_do_I_edit_my_kernel_command_line linux-kernel command line]</span> <pre><span style="color: #000000;">buddy=igep0022<linux-imx/span><blob/pre><span style="color: #000000;">Optionally, to enable the IGEP0022 modem which is disabled by default you should add in your [indexisee-imx_4.php/How_do_I_edit_my_kernel_command_line kernel command line]</span> <pre><span style="color: #000000;">buddy=igep0022 buddy9.modem=yes</span></pre><span style="color: #000000;">NOTE: UART2 can be used for bluetooth OR modem in expansion board but NOT at same time11_1. They are INCOMPATIBLE0.<0_ga/span> <span style="color: #000000;">'''Scenario B.''' You have and IGEP0030 board plus BASE0010 expansion board, then you should add in your [index.phparch/How_do_I_edit_my_kernel_command_line kernel command line]<arm/span> <pre><span style="color: #000000;">buddy=base0010<boot/span><dts/pre><span style="color: #000000;">'''Scenario Cimx6ul-igep-base0040rd102.''' You have and IGEP0030 board plus BASE0010 Rev. B expansion board, then you should add in your [indexdts imx6ul-igep-base0040rd102.php/How_do_I_edit_my_kernel_command_line kernel command linedts]</span> <pre><span style="color: #000000;">buddy=base0010 buddy.revision=B</span></pre><span style="color: #000000;">'''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]</span> <pre><span style="colorhttps: #000000;">buddy=base0010 buddy.revision=B</span></pre><span style="color: #000000;">'''Scenario Egit.''' You have and IGEP0030 board plus ILMS0015 expansion board, then you should add in your [indexisee.phpbiz/How_do_I_edit_my_kernel_command_line linux-kernel command line]</span> <pre><span style="color: #000000;">buddy=ilms0015</span></pre>=<span id="Layout" class="mwlinux-headline" style="color: #000000;">Layout</span>=<span style="color: #808080;">Machine specific files are located in '''arch/armimx/mach-omap2blob/''' directory with name '''boardisee-igep*imx_4.c''' :</span> * <span style="color: #808080;">'''board-igep00209.c''': For IGEP0020 machine</span>* <span style="color: #808080;">'''board-igep003011_1.c''': For IGEP0030 machine</span>* <span style="color: #808080;">'''board-igep00320.c''': For IGEP0032 machine<0_ga/span> <span style="color: #808080;">Expansion board files, also are located in '''arch/arm/mach-omap2boot/''' directory with name '''exp-*.c''' :<dts/span> * <span style="color: #808080;">'''expimx6ul-igep0022.c''': For IGEP0022 expansion board</span>* <span style="color: #808080;">'''expigep-base0010.c''': For BASE0010 expansion board</span>* <span style="color: #808080;">'''expbase0040rd102-ilms0015wifi.c''': For ILMS0015 expansion board</span> =<span id="Adding_New_Expansion_Boards" class="mwdts imx6ul-headline" style="color: #000000;">Adding New Expansion Boards</span>=<span style="color: #808080;">This chapter is meant to be a starting point for people to learn how to add your own expansion board in three steps.</span> ==<span id="Step_1:_Add_new_expansion_board_file" class="mw-headline" style="color: #808080;">Step 1: Add new expansion board file</span>==<span style="color: #808080;">As you can see in Layout chapter, an expansion board is called expigep-.c and should be located in arch/arm/machbase0040rd102-omap2 directory, so the first step will be add a new file for your new expansion boardwifi. Following example creates a new expansion board file called exp-dummy.c (arch/arm/mach-omap2/exp-dummy.c)</span>dts]|}
<pre><span style="color: #808080;"> #include <linuxOnce you have to compile the Kernel, you have to copy de Zimage and dtb in /media/user/kernelboot.h> #include '''<linuxbr /init.h>'''
void __init dummy_init(void) { pr_info("Initializing expansion board ... \n"); }</span></pre><span style="colorzImage example: #808080;">next, add the new file to be built</span>
<pre><span style="color: #808080000000;">diff --git a/<code class="java plain">cp arch/arm/mach-omap2boot/Makefile bzimage /archmedia/armuser/mach-omap2/Makefileindex 7505be9..a6572f2 100644--- a/arch/arm/mach-omap2/Makefile+++ b/arch/arm/mach-omap2/Makefile@@ -156,6 +156,7 @@ obj-$(CONFIG_MACH_IGEP0020) += board-igep0020.o \ obj-$(CONFIG_MACH_IGEP0030) += board-igep0030.o \ board-igep00x0.o \ exp-base0010.o \+ exp-dummy.o \ hsmmc.o obj-$(CONFIG_MACH_OMAP3_TOUCHBOOK) += board-omap3touchbook.o \ hsmmc.o</span></pre>==<span id="Step_2:_Register_new_expansion_board" class="mw-headline" style="color: #808080;">Step 2: Register new expansion boardboot</span>==<span style="color: #808080;"code>Now, edit board-igep00x0.h and add an identifier for the new expansion board, for example,</span>
<pre><span style="color: #808080;">diff --git a/arch/arm/mach-omap2/board-igep00x0.h b/arch/arm/mach-omap2/board-igep00x0.h
index 6b9b677..a2325d7 100644
--- a/arch/arm/mach-omap2/board-igep00x0.h
+++ b/arch/arm/mach-omap2/board-igep00x0.h
@@ -15,6 +15,7 @@
#define IGEP00X0_BUDDY_NONE 0x01
#define IGEP00X0_BUDDY_IGEP0022 0x01
#define IGEP00X0_BUDDY_BASE0010 0x02
+#define IGEP00X0_BUDDY_DUMMY 0x03
#define IGEP00X0_BUDDY_HWREV_A (1 << 0) #define IGEP00X0_BUDDY_HWREV_B (1 << 1)</span></pre><span style="color: #808080000000;">also, edit in board<code class="java plain">cp arch/arm/boot/dts/omap3-igep00x0igep0020-rev-f.c the buddy_early_param to add the new expansion board,dtb /media/user/boot</code></span>
<pre><span style="color: #808080;">diff --git a/arch/arm/mach-omap2/board-igep00x0.c b/arch/arm/mach-omap2/board-igep00x0.c
index 2a2d8eb..f2b5b27 100644
--- a/arch/arm/mach-omap2/board-igep00x0.c
+++ b/arch/arm/mach-omap2/board-igep00x0.c
@@ -192,6 +192,9 @@ static int __init buddy_early_param(char *str)
if (!strcmp(name, "base0010")) {
igep00x0_buddy_pdata.model = IGEP00X0_BUDDY_BASE0010;
pr_info("IGEP: IGEP0030 machine + BASE0010 (buddy)\n");
+ } else if (!strcmp(name, "dummy")) {
+ igep00x0_buddy_pdata.model = IGEP00X0_BUDDY_DUMMY;
+ pr_info("IGEP: IGEP0030 machine + DUMMY (buddy)\n");
} else
pr_err("IGEP: Unknown buddy for IGEP0030 machine\n");
}
</span></pre>
==<span id="Step_3:_Run_expansion_board_initialization" class="mw-headline" style="color: #808080;">Step 3: Run expansion board initialization</span>==
<span style="color: #808080;">Finally, modify the machine file and add support for the new expansion board, for example:</span>
<pre><span style="color: #808080;">diff --git '''Before to install the modules, you need to choose a/arch/arm/mach[[IGEP Firmware set-omap2/board-igep0030.c b/arch/armup|rootfs]] and copy in your SDCard or Nand/mach-omap2/board-igep0030MMC rootfs parition.cindex 2b97257..44b319d 100644--- a/arch/arm/mach-omap2/board-igep0030.c+++ b/arch/arm/mach-omap2/board-igep0030.c@@ -204,6 +204,8 @@ static struct omap_board_mux board_mux[] __initdata = {'''
/* Expansion board: BASE0010 */
extern void __init base0010_init(struct twl4030_platform_data *pdata);
+/* Expansion board: DUMMY */
+extern void __init dummy_init(void);
static void __init igep0030_init(void) {@@ -223'''Finally''',6 +225the last step is to''' install the modules inside the desired rootfs'''. For example,10 @@ static void __init igep0030_init(void) /* - BASE0010 (adds twl4030_pdata) */ if (igep00x0_buddy_pdata.model == IGEP00X0_BUDDY_BASE0010) base0010_init(&twl4030_pdata);+ the rootfs is located in a external storage device mounted on the /* - DUMMY */+ if (igep00x0_buddy_pdata.model == IGEP00X0_BUDDY_DUMMY)+ dummy_init();+media folder:
sudo make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- INSTALL_MOD_PATH=/* Add twl4030 common data *media/ omap3_pmic_get_config(&twl4030_pdata, TWL_COMMON_PDATA_USB |<user/span><rootfs/pre>modules_install==<span id="Known_issuesLinux_kernels" class="mw-headline" style="color: #808080;">Known issuesLinux kernels</span>==<span style="color: #808080;">See [http://processors.wiki.ti.com/index.php/AM35x-OMAP35x-PSP_04.02.00.07_Release_Notes#Known_Issues_-_AM.2FDM37x http://processors.wiki.ti.com/index.php/AM35x-OMAP35x-PSP_04.02.00.07_Release_Notes#Known_Issues_-_AM.2FDM37x]</span>To get more information about our Kernel and their compatibilities
==<span id="modules_are_not_installed_correctly" class="mw-headline" style="color: #808080;">modules are not installed correctly</span>==* [[Linux Kernel 4.1.y|Linux Kernel 4.1]]<span style="color: #808080;">Try to change rootfs owner from root to your username* [[Linux Kernel 3.8.y|Linux Kernel 3.</span>8]]
<pre><span style="color: #808080;"> sudo chown -R /media/rootfs</span></pre>
==<span id="wlcore:_Unknown_symbol" class="mw-headline" style="color: #808080;">wlcore: Unknown symbol</span>==
<span style="color: #808080;">Probably, you didn't erase old module binaries from rootfs. Open IGEP terminal and type:</span>
<pre><span style="color[[Category: #808080;">depmod -aLinux]]depmod -A </span></pre><span style="color[[Category: #808080;">Finally reboot the system</span>Linux_Kernel]]
Retrieved from "http://labs.isee.biz/index.php?title=Special:MobileDiff/11640...12229"