5AI.1.12 Release Notes

From OMAPpedia

Jump to: navigation, search


[edit] Introduction

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

OS Kernel: Linux® 3.4
Android: Android IcecreamSandwich 4.0.4 MR1
Toolchain: Andriod linux-x86 toolchain arm-eabi-4.4.3
Reference hardware platforms: TI OMAP5 5430 SEVM ES1.0 HD (high secure device)
Build Host OS: Ubuntu
Daily Build OMAP5 SEVM Version: OMAP5_master_3.4kernel build 70

[edit] 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 the Android linux-x86 toolchain for ARM GNU/Linux version.

This tool chain can be obtained when you pull the Android code based on the released manifest that will be given.

[edit] 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.12
cd 5AI.1.12
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.12.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.4
cd kernel/android-3.4
git checkout 3ca022b65d189159693cb9ca41e93255a0d5c370

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

cd $YOUR_PATH/kernel/android-3.4
git fetch origin
git checkout 3ca022b65d189159693cb9ca41e93255a0d5c370

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 40d6dc6d1bf1fd780659af2c2c0bd23b4a57d933

[edit] Release Content

This release has the below content - Kernel and Drivers tested with OMAP5 5430 sEVM 1.0 HD (high security device) and verified with Ice Cream Sandwich UI

[edit] Build Instructions

[edit] Setting up build environment

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

export YOUR_PATH=`pwd`
export MYDROID=${YOUR_PATH}/mydroid
export PATH=$PATH:${MYDROID}/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/
mkdir $MYDROID/logs
export CROSS_COMPILE=${MYDROID}/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-

[edit] 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 MACH=omap5 BOARD=omap5evm clean
make MACH=omap5 BOARD=omap5evm CROSS_COMPILE=${HOME}/.jenkins/workspace/OMAP5_AFS/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-

[edit] Building Kernel

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

cd ${YOUR_PATH}/kernel/android-3.4
make -j$(cat /proc/cpuinfo |grep ^proc|wc -l) ARCH=arm CROSS_COMPILE=arm-eabi- mrproper
make -j$(cat /proc/cpuinfo |grep ^proc|wc -l) ARCH=arm CROSS_COMPILE=arm-eabi- android_omap_defconfig
make -j$(cat /proc/cpuinfo |grep ^proc|wc -l) ARCH=arm CROSS_COMPILE=arm-eabi- uImage modules

[edit] Building Android Filesystem (AFS)

. build/envsetup.sh
lunch 16  #(specific lunch target: full_omap5sevm-userdebug)
make -j $(egrep '^processor' /proc/cpuinfo | wc -l) clean
make -j $(egrep '^processor' /proc/cpuinfo | wc -l)

[edit] Building SGX

It is recommended to open a new command terminal when building the sgx components.
The SGX package is based on an internal repository and so the package needs to be pulled from CDDS: In addition the OMAPLFB package is also needed in this release and is on an internal repository but the package is available on CDDS also:

tar zxf <PATH TO>/SGX_5AI.1.12.tgz
cd sgx_2012-06-26_10-49-15
export KERNELDIR=${YOUR_PATH}/kernel/android-3.4
export CROSS_COMPILE=${MYDROID}/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
export DISCIMAGE=${PWD}/discimage
if [ -d ${DISCIMAGE} ]; then
  rm -rf ${DISCIMAGE}
mkdir ${DISCIMAGE}
. build/envsetup.sh
lunch 16
cd ${YOUR_PATH}/sgx_2012-06-26_10-49-15
./build_DDK.sh -g 544 --build release clobber  #(required for rebuild only)
./build_DDK.sh -g 544 --build release

OMAPLFB kernel module build, (in the same terminal as sgx run):

cd ${YOUR_PATH}/sgx_2012-06-26_10-49-15  #(just to make sure you are in the correct directory)
tar zxf <PATH TO>/OMAPLFB_5AI.1.12.tgz  #(This is inside the sgx directory)
export PVRKMDIR=${YOUR_PATH}/sgx_2012-06-26_10-49-15
export TARGET=omap5430
cd omaplfb_2012-06-26_10-49-15/omaplfb_linux/
cp -fv omaplfb_sgx544_105.ko ${PVRKMDIR}/eurasia_km/eurasiacon/binary2_544_105_omap5430_android_release/target

Final step for Graphics Build:

fakeroot ./build_DDK.sh -g 544 --install release

[edit] Building TI WLAN & Blueti Drivers

When building the wifi drivers and the new blue tooth blueti drivers you will also need to also have the CROSS_COMPILE also set as listed above in Setting up the Build Environment.
For both the WLAN and BTFM components there is licensed firmware that needs to be downloaded from CDDS and the specific details are included in the

OPBU_Linux_5AI.1.12_Release_Notes document and should be used when adding the connectivity components.

Wifi Drivers

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

Blueti Drivers

export KERNEL_DIR=${YOUR_PATH}/kernel/android-3.4
export ARCH=arm
cd ${MYDROID}/hardware/ti/wpan/bluetooth-compat/
make -j4 clean  
make -j4

[edit] Building Ducati

It is recommended for the Ducati & RPMSG builds steps to review the release document: OPBU_Linux_5AI_1_12_Release_Notes.doc available on CDDS.

The Ducati MM package "Ducati_5AI.1.12.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. There where updates in 5AI.1.11.
A complete Tools package is available from CDDS for 5AI.1.11, you will need to review the Release Notes Document for the specific location.
A more detailed set of instructions for setting up the tools is available in the OPBU_Linux_5AI_1_12_Release_Notes document that can be downloaded from CDDS.

[edit] Setup

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

[edit] Build Steps for RPMSG

cd ${YOUR_PATH}/ducati_2012-06-26_14-57-35/
export DUCATI=`pwd`
git clone git://git.omapzoom.org/repo/sysbios-rpmsg.git rpmsg
cd rpmsg
git checkout ecf363f09df5d60ee181f1f0833d03db710753fa
  export BIOSTOOLSROOT=${YOUR_PATH}/dsptools
  export PATH=${PATH}:${BIOSTOOLSROOT}/cgtarm-4.9.0
  export TMS470CGTOOLPATH=<location of cgtarm-4.9.0>
  export C6000CGTOOLPATH=<location of cgt6x-7.2.0>

  make smp_config
  make -j4

[edit] Build Steps for Ducati

More details on the Ducati build steps are given in the release document: OPBU_Linux_5AI_1_12_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_L_smp_config  #This configuration determines the camera module the ducati image will be for - this is the 8 MPix camera that is default.
                                                     # the "make omap5_sevm_smp_config" configures the build for the 14MPix camera.
  export JOBS=4

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

[edit] Preparing Android binaries

Officially this release supports emmc boot. For the emmc the system image file must have the sgx and ducati binary included, the document OPBU_Linux_5AI.1.12_Release_Notes.doc contain details on other components that can also be added to the AFS as done for sgx and ducati. It is recommended to read the document before building your final image.

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

Wifi & BT 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_wl18xx/compat/compat.ko .
cp -fp ${MYDROID}/hardware/ti/wlan/mac80211/compat_wl18xx/net/wireless/cfg80211.ko .
cp -fp ${MYDROID}/hardware/ti/wlan/mac80211/compat_wl18xx/net/mac80211/mac80211.ko .
cp -fp ${MYDROID}/hardware/ti/wlan/mac80211/compat_wl18xx/drivers/net/wireless/ti/wl12xx/wl12xx.ko .
cp -fp ${MYDROID}/hardware/ti/wlan/mac80211/compat_wl18xx/drivers/net/wireless/ti/wl18xx/wl18xx.ko .
cp -fp ${MYDROID}/hardware/ti/wlan/mac80211/compat_wl18xx/drivers/net/wireless/ti/wl1251/wl1251.ko .
cp -fp ${MYDROID}/hardware/ti/wlan/mac80211/compat_wl18xx/drivers/net/wireless/ti/wlcore/wlcore*.ko .
cp -fp ${MYDROID}/hardware/ti/wpan/bluetooth-compat/net/bluetooth/bnep/bnep.ko .
cp -fp ${MYDROID}/hardware/ti/wpan/bluetooth-compat/net/bluetooth/rfcomm/rfcomm.ko .
cp -fp ${MYDROID}/hardware/ti/wpan/bluetooth-compat/net/bluetooth/bluetooth.ko .
cp -fp ${MYDROID}/hardware/ti/wpan/bluetooth-compat/net/bluetooth/hidp/hidp.ko .
cp -fp ${MYDROID}/hardware/ti/wpan/bluetooth-compat/drivers/bluetooth/btwilink.ko .
. build/envsetup.sh
lunch 16
cp -v ${YOUR_PATH}/kernel/android-3.4/arch/arm/boot/zImage device/ti/${BOARD_TYPE}/boot/zImage
cp -v ${DUCATI}/ducati-m3-core0.xem3 out/target/product/${BOARD_TYPE}/system/vendor/firmware/
cp -avf ${YOUR_PATH}/sgx_2012-06-26_10-49-15/discimage/system/vendor/* out/target/product/${BOARD_TYPE}/system/vendor/
cp -avf ${YOUR_PATH}/sgx_2012-06-26_10-49-15/discimage/system/lib/modules/* out/target/product/${BOARD_TYPE}/system/lib/modules/
for i in $(ls out/target/product/omap5sevm/*img); do rm -vf $i; done
make -j $(egrep '^processor' /proc/cpuinfo | wc -l)

[edit] Preparing eMMC binaries/images

mkdir emmc_files
cp -v ${MYDROID}/out/target/product/omap5sevm/*img emmc_files
cp -v ${MYDROID}/device/ti/omap5sevm/boot/fastboot.sh emmc_files
cp -v ${MYDROID}/out/host/linux-x86/bin/{simg2img,make_ext4fs,mkbootimg,fastboot,adb} emmc_files
cp -v ${YOUR_PATH}/kernel/android-3.4/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  # for a GP device

# for HD devices (high security devices) sign the usbboot binaries with m-shield-lite
${YOUR_PATH}/omap-mshield-lite/generate_ULO OMAP5430 ES1.0 ${YOUR_PATH}/usbboot/out/omap5evm/iboot.bin
${YOUR_PATH}/omap-mshield-lite/generate_MLO OMAP5430 ES1.0 ${YOUR_PATH}/usbboot/out/omap5evm/eboot.bin
# for HD devices (high security devices) copy the following after signing with m-shield-lite
cp -v ${YOUR_PATH}/omap-mshield-lite/ULO emmc_files/iboot.ift
cp -v ${YOUR_PATH}/omap-mshield-lite/MLO emmc_files/omap5evm_HS_ES1.0_MLO

[edit] 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...

4. Power up your board

     From the terminal you should see something similar to this saying the device is in fastboot mode (the specific output depends on your board and the release): 
            r1Texas Instruments Inc Bootloader 1.1.0-jenkins-OMAP5_usbboot-102^0
            Build Info: Apr 20 2012 - 05:01:26
            Entering fastboot mode...
   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