5AI.1.9 Release Notes

From OMAPpedia

Revision as of 15:41, 3 May 2012 by Bryanwb (Talk | contribs)
Jump to: navigation, search



This software release has been developed and verified in the following software and hardware environment.

OS Kernel: Linux® 3.1
Android: Android IcecreamSandwich 4.0.3 MR1
Audio Back End (ABE): 09.51
Toolchain: CodeSourcery compiler version Sourcery G++ Lite 2010q1-202 for ARM GNU/Linux
Reference hardware platforms: TI OMAP5 5430 SEVM ES1.0 GP
Build Host OS: Ubuntu
Daily Build OMAP5 SEVM Version: OMAP5_master build 122

Tools & Dependency packages

Pre-requisite packages for building the Android Filesystem (Note this is with reference to Ubuntu 10.04 64-bit). Ubuntu 64-bit is required by Ice Cream Sandwich.

If you are behind firewall, you will have to set-up firewall using the instructions in [1]

The following commands will install the correct packages to your server:

sudo apt-get install git-core flex bison gperf libesd0-dev zip libwxgtk2.6-dev zlib1g-dev build-essential tofrodos x-dev 
sudo apt-get install lib32readline5-dev libstdc++6 lib32z1 lib32z1-dev ia32-libs g++-multilib libx11-dev libncurses5-dev 

Add the partner repositories and install the JDK:

sudo add-apt-repository "deb http://archive.canonical.com/ lucid partner"
sudo apt-get update
sudo apt-get install sun-java6-jdk

Install latest repo tool:

mkdir ~/bin -p
sudo apt-get install curl
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo
export PATH=~/bin:$PATH

Command to get repo version:

repo --version
Should be repo version v1.7.8.2 or higer.

If you do not have sudo rights to your machine, contact your System Administrator for assistance.

Tool Chain for building Kernel and Drivers

The Kernel and Driver sources are built using Sourcery G++ Lite 2010q1-202 for ARM GNU/Linux version.

This tool chain can be obtained from


Downloading Release Software

Android Filesystem Sources


1: You should export a variable "https_proxy" when behind a firewall, since file system build downloads repo tree from Google server over https connection. You can use

the format mentioned


export https_proxy=<local_site_proxy_server eg: http://local.proxyserver.com:80>

2: Ensure that you back up .repo folder into another location, otherwise it will take precedence on top of the one you will be creating below. Command below for


mv $HOME/.repo $HOME/.repo_old

You can get the Android source for this release by doing:

cd <your work directory>
mkdir -p 5AI.1.9
cd 5AI.1.9
export YOUR_PATH=`pwd`
mkdir -p mydroid; cd mydroid
export MYDROID=`pwd`
repo init -u git://git.omapzoom.org/platform/omapmanifest.git -b 5AI.x -m RLS_5AI.1.9.xml
repo sync

Kernel & Driver Sources

To clone kernel source from scratch do:

mkdir kernel
git clone git://git.omapzoom.org/kernel/omap.git kernel/android-3.1
cd kernel/android-3.1
git checkout e8eb934642837f461869ad6c9ec5f5068604e7ae

If you already have kernel source cloned then just update it:

cd $YOUR_PATH/kernel/android-3.1
git fetch origin
git checkout e8eb934642837f461869ad6c9ec5f5068604e7ae

U-Boot Sources U-Boot is no longer needed or required for the eMMC boot image, only usbboot is required.

UsbBoot Sources

git clone git://git.omapzoom.org/repo/omapboot.git usbboot
cd usbboot
git checkout fb4303e2f14fa12648900aeb58be17db75098278

Release Content

This release has the below content - Kernel and Drivers tested with OMAP5 5430 SEVM 1.0 GP and verified with Ice Cream Sandwich UI

Build Instructions

Setting up build environment

From your work directory (5AI.1.9 folder):

export YOUR_PATH=`pwd`
export PATH=$PATH:<toolchain_parent_dir>/arm-2010q1/bin
export MYDROID=${YOUR_PATH}/mydroid
mkdir $MYDROID/logs
export CROSS_COMPILE=arm-none-linux-gnueabi-
export PATH=${YOUR_PATH}/u-boot/tools:${PATH}

Building usbboot

This is for creating the emmc boot

cd ${YOUR_PATH}/usbboot
git clean -fdx
export TOOLCHAIN=${MYDROID}/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
make ARCH=omap5 BOARD=omap5evm clean
make ARCH=omap5 BOARD=omap5evm

Building Kernel

To create kernel uImage you need to add "mkimage" directory path to your "PATH" environment variable:

cd ${YOUR_PATH}/kernel/android-3.1
make -j$(cat /proc/cpuinfo |grep ^proc|wc -l) ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- mrproper
make -j$(cat /proc/cpuinfo |grep ^proc|wc -l) ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- android_omap5sevm_defconfig
make -j$(cat /proc/cpuinfo |grep ^proc|wc -l) ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- uImage modules

Patching Android Filesystem (AFS) with TI Codecs enabled

This build requires 1 userspace patches to be applied and is attached to this wiki page. These instructions assume you have downloaded the attached patch into


cd ${MYDROID}/hardware/ti/omap4xxx
git fetch http://review.omapzoom.org/p/platform/hardware/ti/omap4xxx refs/changes/07/19107/1 && git cherry-pick FETCH_HEAD

Building Android Filesystem (AFS)

. build/envsetup.sh
lunch 16
make -j $(egrep '^processor' /proc/cpuinfo | wc -l) clean
make -j $(egrep '^processor' /proc/cpuinfo | wc -l)

Building SGX

The SGX package is based on the following internal repository:

tar zxf <PATH TO>/SGX_5AI.1.9.tgz
cd sgx_2012-04-03_13-07-22
export KERNELDIR=${YOUR_PATH}/kernel/android-3.1
export DISCIMAGE=${PWD}/discimage
if [ -d ${DISCIMAGE} ]; then
  rm -rf ${DISCIMAGE}
mkdir ${DISCIMAGE}
./build_DDK.sh --build omap5 release clobber
./build_DDK.sh --build omap5 release
fakeroot ./build_DDK.sh --install omap5 release

Building TI WLAN Drivers

When building the wifi drivers you will also need to also have the CROSS_COMPILE also set as listed above in Setting up the Build Environment

export KERNEL_DIR=${YOUR_PATH}/kernel/android-3.1
export ARCH=arm
cd ${MYDROID}/hardware/ti/wlan/mac80211/compat/
make -j4 clean  
make -j4

Building Ducati

The Ducati MM package "Ducati_5AI.1.9.tgz" will need to be downloaded from CDDS.

The tools need to be downloaded and installed in a common tools directory that would then be used during the build.
A complete Tools package is available from CDDS at the following link: ICS_Ducati_Tools
A more detailed set of instructions for setting up the tools is available in the OPBU_Linux_5AI_1_9_Release_Notes document that can be downloaded from CDDS.
This package will install the tools together in one specific directory called dsptools.


tar zxf <PATH TO>/Ducati_5AI.1.9.tgz

Build Steps for RPMSG

cd ${YOUR_PATH}/Ducati_2012-04-03_11-54-33/
export DUCATI=`pwd`
git clone git://git.omapzoom.org/repo/sysbios-rpmsg.git rpmsg-
cd rpmsg-
git checkout
chmod +w Makefile
  export BIOSTOOLSROOT=${YOUR_PATH}/dsptools

Edit the Makefile - REPO - else echo - put the path to the dsptools.  Example using sed command below:
sed -i -e "s#/usr/local#${BIOSTOOLSROOT}#g" Makefile 

  export PATH=${PATH}:${BIOSTOOLSROOT}/cgtarm-4.9.0
  export XDCPATH="${DUCATI}/rpmsg-; <BIOSPATH>/bios_6_32_01_38/packages"
  export TMS470CGTOOLPATH=<location of cgtarm-4.9.0>
  export C6000CGTOOLPATH=<location of cgt6x-7.2.0>

  make clean
  make -j4

Build Steps for Ducati

More details on the Ducati build steps are given in the release document: OPBU_Linux_5AI_1_9_Release_Notes.doc available on CDDS.
The paths below need to be defined and for each export commands are one line.

Environment Settings:
    export BIOSTOOLSROOT=${YOUR_PATH}/dsptools  (This assumes all the dsptools are loaded in this directory; so you can modify this if needed)
    export RPMSGSRC=${DUCATI}/rpmsg-
    export DUCATIMMSRC=<base directory of ducatimm>
    export TMS470CGTOOLPATH=${YOUR_PATH}/dsptools/cgtarm-4.9.0 

Specific Build Steps:

cd ${DUCATI}
  make omap5_sevm_config
  make -j4 

The ducati-m3.bin would be generated and then this binary will be copied into the Android File System as instructed below.

Preparing Android binaries

This release officially supports both emmc boot. For the emmc the system image file must have the sgx and ducati binary included.

Rebuild Android Filesystem (AFS) to include the Wifi, Ducati & SGX binaries

Wifi kernel modules:

export BOARD_TYPE="omap5sevm"
cd $MYDROID/out/target/product/$BOARD_TYPE
mkdir -p system/lib/modules; cd system/lib/modules
cp -fp ${MYDROID}/hardware/ti/wlan/mac80211/compat/compat/compat.ko .
cp -fp ${MYDROID}/hardware/ti/wlan/mac80211/compat/net/wireless/cfg80211.ko .
cp -fp ${MYDROID}/hardware/ti/wlan/mac80211/compat/net/mac80211/mac80211.ko .
cp -fp ${MYDROID}/hardware/ti/wlan/mac80211/compat/drivers/net/wireless/ti/wl12xx/wl12xx.ko .
cp -fp ${MYDROID}/hardware/ti/wlan/mac80211/compat/drivers/net/wireless/ti/wl18xx/wl18xx.ko .
cp -fp ${MYDROID}/hardware/ti/wlan/mac80211/compat/drivers/net/wireless/ti/wl1251/wl1251.ko .
cp -fp ${MYDROID}/hardware/ti/wlan/mac80211/compat/drivers/net/wireless/ti/wlcore/wlcore*.ko .
. build/envsetup.sh
lunch 16
cp -v ${YOUR_PATH}/kernel/android-3.1/arch/arm/boot/zImage device/ti/${BOARD_TYPE}/boot/zImage
cp -v ${DUCATI}/ducati-m3.bin out/target/product/${BOARD_TYPE}/system/vendor/firmware/
cp -avf ${YOUR_PATH}/sgx_2012-04-03_13-07-22/discimage/system/vendor/* out/target/product/${BOARD_TYPE}/system/vendor/
cp -v ${YOUR_PATH}/sgx_2012-04-03_13-07-22/discimage/system/etc/* out/target/product/${BOARD_TYPE}/system/etc/
for i in $(ls out/target/product/omap5sevm/*img); do rm -vf $i; done
make -j $(egrep '^processor' /proc/cpuinfo | wc -l)

Preparing eMMC binaries/images

mkdir emmc_files
cp -v ${MYDROID}/out/target/product/omap5sevm/*img emmc_files
cp -v ${MYDROID}/out/target/product/omap5sevm/fastboot.sh emmc_files
cp -v  ${MYDROID}/out/host/linux-x86/bin/{simg2img,make_ext4fs,mkbootimg,fastboot} emmc_files
cp -v ${YOUR_PATH}/kernel/android-3.1/arch/arm/boot/zImage emmc_files
cp -v ${YOUR_PATH}/usbboot/out/omap5evm/MLO emmc_files/omap5evm_GP_ES1.0_MLO
cp -v ${YOUR_PATH}/usbboot/out/omap5evm/usbboot emmc_files
cp -v ${YOUR_PATH}/usbboot/out/omap5evm/iboot.ift emmc_files

It is required to modify the fastboot.sh script for the OMAP5 flashing process so make the following changes as listed below:

Modify the lines:
  export FASTBOOT=${FASTBOOT-"./../../../../out/host/linux-x86/bin/fastboot"} ==>   export FASTBOOT=./fastboot
  export PRODUCT_OUT=${PRODUCT_OUT-"./"} ==>   export PRODUCT_OUT=./
  ./../../../../out/host/linux-x86/bin/make_ext4fs -s -l 256M -a cache ${cacheimg} /tmp/fastboot-cache/
==>   ./make_ext4fs -s -l 256M -a cache ${cacheimg} /tmp/fastboot-cache/

Remove the following lines from the fastboot.sh script related to uboot which is no longer used:

  if [ ! -e "${uboot}" ] ; then
    echo "Missing ${uboot}"
    exit -1;

  ${FASTBOOT} flash bootloader 	${uboot}

Move the 2 lines below so they are above the line: echo "Flashing bootloader....."
  echo "Create GPT partition table"
  ${FASTBOOT} oem format

Remove all of the function that starts with the given line (it is at the end):
  -if [ $resizefail -eq 1 ]; then

Flashing eMMC images

This is done using usbboot to put the OMAP5 board in fastboot mode with the steps given below:

Required dip switch settings on switch S6 to enable eMMC boot. (S6 on the back of the board)
     3    2   1    0

1. Connect your micro usb cable (USB3 cable can also be used) from the
    target to your flashing station, the power supply, & the usb cable using a terminal or screen
    (for screen the command is: screen /dev/ttyUSB0 115200)

2. Make sure the board is powered OFF

3. Start usbbboot in fastboot mode:

      sudo ./usbboot -f
         When running this command you will see: 
         usbboot -f:  starting in fastboot mode
         waiting for device...

     From the terminal you should see something similar to this saying the device is in fastboot mode: 
            r1Texas Instruments Inc Bootloader 1.1.0-jenkins-OMAP5_usbboot-102^0
            Build Info: Apr 20 2012 - 05:01:26
            Entering fastboot mode...

4. Power up your board
   From the command prompt where you ran the usbboot command you should see something similar to this below:
    reading ASIC ID
    CHIP: 5430
    IDEN: cfd7d499ed40beab470795a5cfbc5707807b4b6a
    MPKH: 351edf8f4d739d50f7449a6d3d3d983d6220974836f039c752dae7226bb19955
    CRC0: 06e92275
    CRC1: 3894aaf5
    device is ED/HD (EMU/HS)
    sending 2ndstage to target... f0030002
    waiting for 2ndstage response...
    received 2ndstage response...

5. Run your fastboot.sh script
     sudo ./fastboot.sh
       This will flash the binaries into the emmc on the omap5 board.

6. Now reset the board and let it boot up.

SD Card Boot Information

Personal tools