esac
</pre>
== Android Eclair 2.1 Platform ==
=== Pre-built images for impatients ===
<span style="color: rgb(255, 0, 0);">
This software is distributed in the hope that it will be useful, but '''WITHOUT ANY WARRANTY'''; without even the implied warranty of '''MERCHANTABILITY''' or '''FITNESS FOR A PARTICULAR PURPOSE''''.
</span>
{| border=1 class="simple"
!'''Release'''
!'''Kernel'''
!'''Rootfs'''
!'''Platform'''
|-
| Android 2.1 (Eclair)
| [http://downloads.igep.es/android/eclair-2.x/v2.1R1/uImage-2.6.29-igep0020-20100407145010.bin 2.6.29-igep0020]
| [http://downloads.igep.es/android/eclair-2.x/v2.1R1/android-image-eclair-2.1-update1-20100407145010.tar.bz2 2.1 Update 1]
| http://developer.android.com/sdk/android-2.1.html
|}
=== Build Android Eclair from sources ===
Run repo init to bring down the latest version of Repo with all its most recent bug fixes. You must specify a URL for the manifest:
<pre>
$ mkdir android
$ cd android
$ repo init -u git://gitorious.org/rowboat/manifest.git -m < manifest name >
</pre>
where manifest name is:
*rowboat-eclair.xml - for eclair version of rowboat
*rowboat-eclair-dsp.xml - for eclair version of rowboat with DSP support
To pull down files to your working directory from the repositories as specified in the default manifest, run
<pre>
$ repo sync
</pre>
If you want eclair with DSP support you need to download and place codec_engine_2_24_01.tar.gz under the external/ti-dsp folder. Codec Engine is available [http://software-dl.ti.com/dsps/dsps_registered_sw/sdo_sb/targetcontent/CE/ce_2_24/index.html here]. Note you may need to have an account on software-dl.ti.com
Now build for your target product, do
<pre>
$ make TARGET_PRODUCT=igepv2 -j8
</pre>
for rowboat-eclair or
<pre>
$ make TARGET_PRODUCT=igepv2 BUILD_WITH_GST=true dvsdk -j8
</pre>
for rowboat-eclair-dsp
Next step is create a tarball containing the rootfs
<pre>
$ cd out/target/product/igepv2
$ mkdir android-rootfs
$ cp -r root/* android-rootfs
$ cp -r system android-rootfs
$ sudo ../../../../build/tools/mktarball.sh ../../../host/linux-x86/bin/fs_get_stats android-rootfs . rootfs rootfs.tar.bz2
$ cd ../../../../
</pre>
The next step is build the Linux kernel for your board.
<pre>
$ export PATH=${PWD}/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin:$PATH
$ cd kernel/
$ make ARCH=arm igep0020_android_defconfig
$ make ARCH=arm CROSS_COMPILE=arm-eabi- uImage -j8
$ cd ..
</pre>
Now, you're ready to install and run your new android image.
=== Installing and Using the Result on a NFS-mounted root filesystem ===
With factory seetings, the board will attempt to mount its root filesystem from the server as /srv/nfs/<distro>/<project>/<machine>, where
<pre>
***<distro> where distro is <your distro>
***<project> where project is <your project>
***<machine> where machine is <your machine>
</pre>
Create the directory structure and extract the root file system to the NFS server
<pre>
$ sudo mkdir -p /srv/nfs/android/android-image-eclair/igep0020
$ pushd /srv/nfs/android/android-image-eclair/igep0020
$ sudo tar jxf rootfs.tar.bz2
$ popd
</pre>
After this the only configuration that needs to be added is an entry for your target root directory to your /etc/exports file, for instance like this:
<pre>
# Poky image rootfs
/srv/nfs/android/android-image-eclair/igep0020 *(rw,no_root_squash,no_subtree_check,sync)
</pre>
After modifying the /etc/exports file you will make sure the NFS system is notified about the change, for instance by issuing the command:
<pre>
$ sudo exportfs -a
</pre>
The target also can get its kernel image from your tftp server. Similar to the NFS root filesystem, the target system will attempt to get its kernel image from the server as /srv/tftp/<distro>/<project>/<machine>. Follow next steps to configure your board and run the your new image.
Create the directory structure and copy the kernel image to the TFTP server, refer to [[The Linux kernel]] for build your own image.
<pre>
$ mkdir -p /srv/tftp/android/android-image-eclair/igep0020
$ cp kernel/arch/arm/boot/uImage /srv/tftp/android/android-image-eclair/igep0020
</pre>
Then, connect your development board as explained in IGEP v2 Software SDK Manual
Next, power up your board and stop u-boot's autoboot by pressing a key.
Now, it's time to change the U-Boot environment.
<pre>
U-Boot> setenv distro android
U-Boot> setenv project android-image-eclair
U-Boot> setenv bootargs-base mem=512M androidboot.console=ttyS2 console=tty0 console=ttyS2,115200n8 init=/init rootwait omap-dss.def_disp=dvi omapfb.video_mode=720x480MR-16@60
</pre>
If you want to set as default boot option, you can also save your new environment
<pre>
U-Boot> saveenv
</pre>
The last step is run the boot command.
<pre>
U-Boot> run nfs-boot
</pre>
=== Links and resources ===
* [http://atstechlab.wordpress.com/2010/09/05/android-on-your-igepv2-in-14-steps/ Android on your IGEPv2 in 14 steps]
--- That's all folks ---
[[Category:Software distributions|Android]]
