Personal tools

Log in

Changes

From IGEP - ISEE Wiki

Jump to: navigation, search

How to get the Android distribution

2,165 bytes removed, 10:07, 31 December 2013
m
Pre-built images for impatients
__TOC__
{{Message/Information Message|message= New [http://labs.isee.biz/index.php/How_to_get_the_Android_4.0_%28Ice_Cream_Sandwich%29_distribution Android 4 (ICS)] is available}}
= How to get the Android distribution =
*Android website ( http://www.android.com/ )
*Android developer website ( http://developer.android.com )
*Android NDK, for native development ( http://developer.android.com/sdk/ndk/index.html )
*Rowboat project website ( http://code.google.com/p/rowboat )
== Android Froyo 2.2 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>
 
 
{{Message/Broken Links}}
 
{| border="1" class="simple"
|-
| &nbsp;Android 2.2 (Froyo) for <span style="color: rgb(255, 0, 0);">DM3730&nbsp;</span>
| &nbsp;[http://downloads.igepisee.esbiz/pub/SW_Releases/binaries/x-loader/v1.4.4-1/x-load-1.4.4-1.igep0020-sdcard.bin.ift x-load-1.4.4-1]&nbsp; | &nbsp;[http://downloadslabs.igepisee.es/binaries/u-boot-armbiz/v2010index.06-1php/uU-boot-arm-2010Boot_2010.06-1.igep0020.bin y_series u-boot-2010.06-1]&nbsp; | &nbsp;[http://downloads.igepisee.esbiz/pub/SW_Releases/android/froyo-2.2/uImage-android-2.6.32.bin uImage-2.6.32.bin]&nbsp; | &nbsp;[http://downloads.igepisee.esbiz/pub/SW_Releases/android/froyo-2.2/android-dm3730-froyo-2.2-20110223161010.tar.bz2 dm3730-2.2]&nbsp;
| http://developer.android.com/sdk/android-2.2.html
| <br>
|-
| &nbsp;Android 2.2 (Froyo) for <span style="color: rgb(255, 0, 0);">OMAP3530&nbsp;</span>
| &nbsp;[http://downloads.igepisee.esbiz/pub/SW_Releases/binaries/x-loader/v1.4.4-1/x-load-1.4.4-1.igep0020-sdcard.bin.ift x-load-1.4.4-1]&nbsp; | &nbsp;[http://downloadslabs.igepisee.es/binaries/u-boot-armbiz/v2010index.06-1php/u-bootU-arm-2010Boot_2010.06-1.igep0020.bin y_series u-boot-2010.06-1]&nbsp; | &nbsp;[http://downloads.igepisee.esbiz/pub/SW_Releases/android/froyo-2.2/uImage-android-2.6.32.bin uImage-2.6.32.bin]&nbsp; | &nbsp;N[http://downloads.isee.biz/pub/SW_Releases/android/froyo-2.2/A android-om3530-froyo-2.2-20110224115610.tar.bz2 om3530-2.2]&nbsp;
| http://developer.android.com/sdk/android-2.2.html
|}
boot.scr files:
*dvi: [http://downloads.igepisee.esbiz/pub/SW_Releases/android/froyo-2.2/boot-dvi.scr 1280x720] *lcd: [http://downloads.igepisee.esbiz/pub/SW_Releases/android/froyo-2.2/boot-lcd-70.scr Seiko 7.0 inch WVGA (800 x RGB x 480) TFT with Touch-Panel] *lcd: [http://downloads.igepisee.esbiz/pub/SW_Releases/android/froyo-2.2/boot-lcd-43.scr Powertip 4.3 inch (480 x RGB x 272) TFT with Touch-Panel] If you want to hook up a HDMI TFT monitor (tv for example), modify the parameter&nbsp;omapfb.mode in the *.scr file to&nbsp;omapfb.mode=dvi:hd720-32@50, with the parameter 32 is the colo mode (16, 24 or 32 bits) and the parameter 50 is the frequency (50 or 60 Hz), both for the monitor used.
'''Quick steps: create a bootable sdcard'''
$ wget http://downloads.igepisee.esbiz/pub/SW_Releases/binaries/x-loader/v1.4.4-1/x-load-1.4.4-1.igep0020-sdcard.bin.ift $ wget http://downloads.igepisee.esbiz/pub/SW_Releases/binaries/u-boot-arm/v2010.06-1/u-boot-arm-2010.06-1.igep0020.bin $ wget http://downloads.igepisee.esbiz/pub/SW_Releases/android/froyo-2.2/uImage-android-2.6.32.bin $ wget http://downloads.igepisee.esbiz/pub/SW_Releases/android/froyo-2.2/android-dm3730-froyo-2.2-20110223161010.tar.bz2 $ wget http://downloads.igepisee.esbiz/pub/SW_Releases/files/media-samples.tar.gz
$ tar xzf media-samples.tar.gz
Download one of
$ wget http://downloads.igepisee.esbiz/pub/SW_Releases/android/froyo-2.2/boot-dvi.scr $ wget http://downloads.igepisee.esbiz/pub/SW_Releases/android/froyo-2.2/boot-lcd-70.scr $ wget http://downloads.igepisee.esbiz/pub/SW_Releases/android/froyo-2.2/boot-lcd-43.scr
and rename to boot.scr
$ mv &lt;boot.scr file&gt; boot.scr
Make the sd card :
$ wget http://downloads.igepisee.esbiz/pub/SW_Releases/android/froyo-2.2/mkmmc-android.sh
$ chmod a+x mkmmc-android.sh
$ sudo ./mkmmc-android.sh &lt;device&gt; x-load-1.4.4-1.igep0020-sdcard.bin.ift u-boot-arm-2010.06-1.igep0020.bin uImage-android-2.6.32.bin boot.scr android-dm3730-froyo-2.2-20110223161010.tar.bz2 media-samples
 
The device name here (&lt;device&gt;) is actually the SDCard in your /dev/ folder. Try removing and inserting the card, and then type command ''dmesg'' in terminal in order to figure out which device name to use (/dev/sdb in this example).
 
Sample output of ''dmesg'' command:
<pre>[ 111.583965] sd 3:0:0:0: [sdb] 990976 512-byte hardware sectors (507 MB)
 
[ 111.587140] sd 3:0:0:0: [sdb] Write Protect is off
 
[ 111.587144] sd 3:0:0:0: [sdb] Mode Sense: 03 00 00 00
 
[ 111.587146] sd 3:0:0:0: [sdb] Assuming drive cache: write through
 
[ 111.591499] sd 3:0:0:0: [sdb] 990976 512-byte hardware sectors (507 MB)
 
[ 111.595692] sd 3:0:0:0: [sdb] Write Protect is off
 
[ 111.595697] sd 3:0:0:0: [sdb] Mode Sense: 03 00 00 00
 
[ 111.595699] sd 3:0:0:0: [sdb] Assuming drive cache: write through
 
[ 111.595721] sdb: sdb1</pre>
 
<div>Note that the numbers are just a timestamp, and that this is the last few lines of the ''dmesg'' command output (you will more likely be in the same situation, given that the last peripheral hooked up to your machine wille be the SD Card).&nbsp;</div>
=== Enhancements ===
==== Apply IGEP v2 patches ====
<span style="color: rgb(255, 0, 0);">
Attention '''BEFORE''' continue you must apply all patches described [[#Annex:_patches |here]] '''Also''' copy the the [[#Annex:_libertas.rc |libertas init script]] and move it to device/ti/igepv2/libertas/rc.libertas.rc
</span>
$ mkdir device/ti/igepv2/libertas/
$ wget http://downloads.igepisee.esbiz/pub/SW_Releases/android/froyo-2.2/libertas.ko $ wget http://downloads.igepisee.esbiz/pub/SW_Releases/android/froyo-2.2/libertas_sdio.ko
$ mv libertas.ko device/ti/igepv2/libertas/
$ mv libertas_sdio.ko device/ti/igepv2/libertas/
$ mkdir device/ti/igepv2/firmware/
$ wget http://downloads.igepisee.esbiz/pub/SW_Releases/android/froyo-2.2/sd8686.bin $ wget http://downloads.igepisee.esbiz/pub/SW_Releases/android/froyo-2.2/sd8686_helper.bin
$ mv sd8686*bin device/ti/igepv2/firmware/
$ cp <dvsdk package> external/ti-dsp
and The next step is running the TI DVSDK installation script. Since the script relies on English application output you need to set the language to English (only on non-english development hosts):  $ export LANG=C Now run the get-tidsp.sh script
$ external/ti-dsp/./get_tidsp.sh
Create a SD card
$ wget http://downloads.igepisee.esbiz/pub/SW_Releases/binaries/x-loader/v1.4.4-1/x-load-1.4.4-1.igep0020-sdcard.bin.ift $ wget http://downloads.igepisee.esbiz/pub/SW_Releases/binaries/u-boot-arm/v2010.06-1/u-boot-arm-2010.06-1.igep0020.bin
Create ONE of these scripts (boot.source)
download some media samples
$ wget http://downloads.igepisee.esbiz/pub/SW_Releases/files/media-samples.tar.gz
$ tar xzf media-samples.tar.gz
finally create the sdcard with the mkmmc-android.sh script(See pre built images for impatients to learn how to create the SD card).
$ wget http://downloads.igepisee.esbiz/pub/SW_Releases/android/froyo-2.2/mkmmc-android.sh
$ chmod a+x mkmmc-android.sh
$ sudo ./mkmmc-android.sh <device> x-load-1.4.4-1.igep0020-sdcard.bin.ift u-boot-arm-2010.06-1.igep0020.bin kernel/arch/arm/boot/uImage boot.scr froyo-rootfs.tar.bz2 media-samples
'''Warning:''' Provide the right device name after the script name when you invoke the script. If you get this wrong it can wipe your HDD. (See pre built images for impatients to learn how to figure out the device name).
=== Annex: patches ===
</pre>
=== Annex: rc.libertas.rc ===
Save the following block to device/ti/igepv2/libertas/rc.libertas.rc
<pre>
</pre>
== Android Eclair 2.1 Platform ==--- That's all folks ---
=== 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> {| borderSee also =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 How to bring down get 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: Ubuntu distribution]]*rowboat-eclair.xml - for eclair version of rowboat*rowboat-eclair-dsp.xml - for eclair version of rowboat with DSP support  To pull down files [[How to your working directory from get 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 hereLinaro distribution]]. 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 [[How to install and run your new android image. === Installing and Using get 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>Angstrom distribution]]***<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 [[How to get 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 rootfsMeego distribution]]/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 [[How 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 Poky Linux kernel]distribution] 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 androidU-Boot> setenv project android-image-eclairU-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]]
4,199
edits