L27.INC1.4 OMAP4 Eclair ES1 Release Notes

From OMAPpedia

Jump to: navigation, search

Contents

[edit] Introduction

This release has been developed and tested in the following environment.

OS Kernel: Linux® 2.6.32.
AndroidTM Éclair 2.1 public project.
Toolchain: CodeSourcery compiler version 2009q1.
Manifest: 27.4_Manifest.
U-boot version: 626aee14ccf5b5e49189ab2a4e256c58d5a4572f
X-loader version: 132029560a1f00cd0d43253d00ff92f00e13780b
kernel version: c7b50d07193abbfd25daca0377fec800dc45536d

[edit] Release Content

The release refers to the source code in git trees and the binary packages are distributed in different projects. The next section on how to build will help pull them into the correct directories to integrate the software system.

Supported MM Use Cases(ARM side) in the Community Release
JPEG Dec

eAAC Dec

eAAC plus Dec

PCM Dec

Wide Band AMR Dec

Narrow Band AMR Dec

Video Playback - MPEG4/AAC

Video Playback - H264/AAC


Documentation
OMAPpedia is an excellent source for details on the various components. There is a project listing in the main page on the various components. You may also go and check the following: Refer to BSP release notes at

   https://gforge.ti.com/gf/project/omapandroid/docman/?subdir=11

Power Management materials PM is enabled by default in the kernel, but for enabling any of the features we need to use some sysfs entries from user space:

   http://omappedia.org/wiki/Linux_OMAP_Kernel_Main
   http://elinux.org/OMAP_Power_Management

Source code
Release Manifest for open code source. Release Tag - RLS27.4rc0

IMPORTANT: kernel source has been removed from the manifest so it is not included in this manifest and thus you have to clone it separately. Instructions for cloning kernel and android source tree are here.

Please note: for U-Boot and X-Loader "omap4_dev" branch was used; and at presently in the manifest.

[edit] Build and Installation Instructions

Building the Bootloader, Kernel and Android File System

The final Release RC tag from L27x manifest for the source should be used. Perform a clean build of u-boot, x-loader, kernel and the android file system.

Pre-built binaries from this release can be obtained from Package.

Software and Tools requirements

IMPORTANT: This release has been builded using Ubuntu Linux 10.0.4; we strongly recommend to upgrade to version 10.0.4.

sudo apt-get install git-core flex bison gperf libesd0-dev x-dev
sudo apt-get install libwxgtk2.6-dev zlib1g-dev build-essential libstdc++5 
sudo apt-get install tofrodos x-dev libx11-dev libncurses5-dev tofrodos
sudo apt-get install sun-java5-jdk
sudo apt-get install cramfsprogs fakeroot

LIBICONV

wget http://ftp.gnu.org/pub/gnu/libiconv/libiconv-1.13.1.tar.gz
tar xzvf libiconv-1.13.1.tar.gz 
cd libiconv-1.13.1/
./configure
make
sudo make install
rm -rf libiconv-1.13.1.tar.gz 

Setting your environment

Please refer to http://omappedia.org/wiki/Android_source_code_versions for getting the source.

From your working directory (where your mydroid folder resides):

export TOP=`pwd`
export MYDROID=$TOP/mydroid
mkdir $MYDROID/logs
export myrelease=27.4_rc1
export JAVA_HOME=/usr/lib/jvm/java-1.5.0-sun
export CROSS_COMPILE=${TOOL_CHAIN_HOME}/bin/arm-none-linux-gnueabi-
export PATH=${MYDROID}/bootable/bootloader/u-boot/tools:${PATH}

set the path to your toolchain (version arm-2009q1):

export TOOL_CHAIN_HOME=<some_path_here>/arm-2009q1

Building UBOOT

cd $MYDROID/bootable/bootloader/u-boot
make distclean
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- omap4430sdp_config
make
export PATH=$PATH:$MYDROID/bootable/bootloader/u-boot/tools

Building XLOADER

cd $MYDROID/bootable/bootloader/x-loader
make distclean	
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- omap4430sdp_config
make ift

Building Kernel

cd $MYDROID/kernel/android-2.6.32
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- distclean
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- android_4430_defconfig
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- uImage

Building Kernel modules

cd $MYDROID/kernel/android-2.6.32
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- modules

Setting Arm Only Build Option

This would disable use of TI's HW Accelerated codecs and would enable to perform only an ARM build, please follow the below instructions

After repo sync perform the following steps:

Edit: “vendor/ti/zoom2/BoardConfig.mk”:

Uncomment  “USE_CAMERA_STUB := true” 
Comment “BOARD_USES_TI_CAMERA_HAL := true” 
Comment "HARDWARE_OMX := true”  

Doing so will not build the TI OMX components and instead Android codecs will be choosen.

Building AFS

on step below use the number of cores you have available; i.e. -j4 or -j12:

cd $MYDROID
cp -Rfp vendor/ti/nextgen/buildspec.mk.default buildspec.mk
make -j4

Please follow the below instructions to modify the file system to make it work.

The Android File System to use on the board

The following elements are required by the Blaze® board. This step will prepare a directory, called myfs, containing all necessary Android files that you must include within your SD card.

cd $YOUR_PATH
mkdir myfs
cd myfs
cp -Rfp $MYDROID/kernel/android-2.6.32/drivers/misc/ti-st/*.ko $MYDROID/out/target/product/nextgen/root
cp -Rfp $MYDROID/out/target/product/nextgen/root/* .
cp -Rfp $MYDROID/out/target/product/nextgen/system/ .
cp -Rfp $MYDROID/out/target/product/nextgen/data/ .
cp -Rfp $MYDROID/vendor/ti/nextgen/init.omap4sdp.rc init.rc

To change default display resolution value to 240 do:

echo “ro.sf.lcd_density=240” >> system/build.prop

[edit] Booting Kernel and Android® File System from SD card

IMPORTANT: This release has been tested using Ubuntu Linux 10.0.4, previous versions might have problems while recognizing the device. We strongly recommend to upgrade to version 10.0.4.


Before continuing, ensure you have installed in your FAT32 partition the following components:

In your ext3 partition, you must install the all content of myfs folder mentioned on previous section. Ensure the content of this partition has full permissions (recursively).

Now insert your SD card into Blaze® SD/MMC card slot, then plug the Blaze® mini USB port to your PC and open a serial terminal (baudrate:115200, no parity, 8 bits). In your Terminal window connected to your mini USB/Serial Port you should be able to see the ‘New’ u-boot prompt: “OMAP44XX SDP #”

Make sure that you can see the Blaze® prompt so that you know it’s the correct u-boot.

Make sure that you copied your myfs folder on the ext3 file system (2nd partition) on your SD card.

In your Terminal Window connected to your Serial Port copy and paste the following:

setenv bootargs console=ttyO2,115200n8 root=/dev/mmcblk0p2 rw rootdelay=2 mem 463M init=/init
setenv bootcmd 'mmcinit 0; fatload mmc 0 0x80000000 uImage; bootm 0x80000000'
boot

[edit] New in this Release

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox