Personal tools

Log in

Changes

From IGEP - ISEE Wiki

Jump to: navigation, search

The IGEP X-loader

3,663 bytes added, 14:04, 3 March 2011
no edit summary
'''kernel build command example''':
<pre>$make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- zImage modules
</pre> 
=== Second Partition ===
Copy all your rootfs in this second partition.
Also you can use the [http://releases.linaro.org/platform/linaro-m/headless/final/linaro-m-headless-tar-20101108-2.tar.gz linaro 10.11 minimal image]&nbsp;download the image and untar (as root) in your microsd card second partition.
Remember install the kernel modules in this partition.
Example:
<pre>sudo make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- modules_install INSTALL_MOD_PATH=[path to your target rootfs]
</pre>
== OneNand Boot ==
 
=== OneNand Partitions<br> ===
 
We suggest use minimum 3 partitions on the OneNand.
<pre>MTD partitions on "omap2-onenand":
(a) 0x000000000000-0x000000080000 : "X-Loader"
(b) 0x000000080000-0x000000c80000 : "Boot"
(c) 0x000000c80000-0x000020000000 : "File System"
</pre>
==== X-Loader Partition ====
 
*Not fs formated (onenand raw)
*Suggested size: 0x80000 (512 KiB)
*The xloader must be signed before copy it in the flash memory.
****You should copy the x-loader in the firsts 4 blocks (first 512 KiB), this is not a&nbsp;
*
 
 
*<span style="display: none; " id="1299156417262E">&nbsp;</span>formated partition due the ROM not permits boot from there, you should use tools:<br>flash_eraseall and nandwrite for copy x-loader in the first blocks.<br>Suggested procedure:<br>nand_eraseall /dev/mtd0<br>nandwrite -p /dev/mtd0 &lt;x-loader&gt;<br>Sign x-loader<br>You should execute contrib/signGP for sign the xloader that resides inside the flash memory.<br>contrib/signGP x-load.bin <br>The signed x-loader it's named: x-load.bin.ift<br>Due the Onenand 512 MiB has two dies it's necessary split the x-loader and convert it to a 1 die binary.<br>This is a know OMAP/DM/AM OneNand/Nand boot limitation.<br>This is the procedure for create the x-loader OneNand binary:<br>You should execute: (You can use copy paste in your console)<br>split -b 2K x-load.bin.ift split-<br>for file in `ls split-a?`; do cat $file &gt;&gt; x-load-ddp.bin.ift; cat $file &gt;&gt; x-load-ddp.bin.ift; done<br>This last command generate a file named x-load-ddp.bin.ift this is the x-loader for copy it in the OneNand.
 
-------------------------------<br>4.4.1) Xloader partition<br>* Not fs formated (raw)<br>* Suggested size: 0x80000 (512 KiB)<br>* The xloader must be signed before copy it in the flash memory.<br>You should copy the x-loader in the firsts 4 blocks (first 512 KiB), this is not a <br>formated partition due the ROM not permits boot from there, you should use tools:<br>flash_eraseall and nandwrite for copy x-loader in the first blocks.<br>Suggested procedure:<br>nand_eraseall /dev/mtd0<br>nandwrite -p /dev/mtd0 &lt;x-loader&gt;<br>Sign x-loader<br>You should execute contrib/signGP for sign the xloader that resides inside the flash memory.<br>contrib/signGP x-load.bin <br>The signed x-loader it's named: x-load.bin.ift<br>Due the Onenand 512 MiB has two dies it's necessary split the x-loader and convert it to a 1 die binary.<br>This is a know OMAP/DM/AM OneNand/Nand boot limitation.<br>This is the procedure for create the x-loader OneNand binary:<br>You should execute: (You can use copy paste in your console)<br>split -b 2K x-load.bin.ift split-<br>for file in `ls split-a?`; do cat $file &gt;&gt; x-load-ddp.bin.ift; cat $file &gt;&gt; x-load-ddp.bin.ift; done<br>This last command generate a file named x-load-ddp.bin.ift this is the x-loader for copy it in the OneNand.<br>4.4.2 Boot Partition<br>--------------------<br>* fs used jffs2 zlib compressed filesystem.<br>* Suggested size: 0xC00000 (12 MiB)<br>First time creation:<br>a) Use the same procedure described in point 4.2.1. Copy your jffs2 compressed image in the<br>partition, it can be a empty file.<br>b) Erase the partition and mount it as jffs2 filesystem then you can copy with cp command.<br>Next Times:<br>Copy the files using cp command, or edit directly.<br>when kernel boots you can enable mount this partition over /boot directory for access all boot content.<br>4.4.3 Rootfs <br>------------<br>* fs (your prefered fs supported by linux, maybe a good choice it should be ubifs)<br>* Size, all or you can create more partitions if you wish ... :)<br>
 
=== ===
=== <br> 4 Settings &amp; Configuration: ===