4AJ.2.3 OMAP4 Jelly Bean Release Notes

From OMAPpedia

Revision as of 17:41, 28 December 2012 by Roman.shaposhnikov (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search



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

OS Kernel: Linux® 3.4
Android: Android JellyBean 4.2
Toolchain: Andriod linux-x86 toolchain arm-eabi-4.6
Reference hardware platforms: TI OMAP4 4470 ES1.0 HS Blaze Tablet 2
Build Host OS: Ubuntu 10.04 64-bit
Daily Build Blaze_Tablet Version: JB DEV Daily Build 26

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 for the cross-compilation of Android Jelly Bean Filesystem.

If you are behind a 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 gawk ant libwxgtk2.6-dev zlib1g-dev build-essential tofrodos
sudo apt-get install lib32readline5-dev libstdc++6 lib32z1 lib32z1-dev ia32-libs g++-multilib libx11-dev libncurses5-dev uboot-mkimage

Install Java SE 6 JDK from Oracle.


Install 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

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.

Downloading Release Software

To obtain Android Filesystem Sources follow:

cd <your work directory>
mkdir -p 4AJ.2.3; cd 4AJ.2.3
export YOUR_PATH=`pwd`
mkdir -p mydroid; cd mydroid
export MYDROID=`pwd`
repo init -u git://git.omapzoom.org/platform/omapmanifest.git -b 27.x -m RLS4AJ.2.3_JellyBean.xml
repo sync

To obtain Kernel & Driver Sources follow:

To clone kernel source from scratch do:

git clone git://git.omapzoom.org/kernel/omap.git kernel/android-3.4
cd kernel/android-3.4
git checkout f46bf5dee480b615454d7435ea4b5202d562eedb

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

cd ${YOUR_PATH}/kernel/android-3.4
git fetch origin
git checkout f46bf5dee480b615454d7435ea4b5202d562eedb

To obtain U-Boot Sources follow:

git clone git://git.omapzoom.org/repo/u-boot.git u-boot
cd u-boot
git checkout 2af35fca236557add6fdd33b836bf5c64455ac8f

To obtain X-loader Sources follow:

git clone git://git.omapzoom.org/repo/x-loader.git x-loader
cd x-loader
git checkout dd88047040dce4a926a6ab80e207bc757f44d648

Release Content

This release has the below content - Kernel and Drivers tested with OMAP4 4470 ES1.0 HS Blaze_Tablet @1.5GHz and verified with Jelly Bean UI - A9 source code for accelerating Video

Build Instructions

Setting up build environment

From your work directory (where your 4AJ.2.3 directory resides):

export YOUR_PATH=`pwd`
export MYDROID=${YOUR_PATH}/mydroid
export PATH=$PATH:${MYDROID}/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/bin/
mkdir ${MYDROID}/logs
export CROSS_COMPILE=${MYDROID}/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/bin/arm-eabi-
export PATH=${YOUR_PATH}/u-boot/tools:$PATH

Building U-BOOT

cd ${YOUR_PATH}/u-boot
make distclean
make ARCH=arm omap44XXtablet_config #(for Blaze_Tablet)
make ARCH=arm omap4430sdp_config #(for Blaze)
make 2>&1 |tee ${MYDROID}/logs/u-boot_make.out

Building X-LOADER for OMAP4470

cd ${YOUR_PATH}/x-loader
make distclean	
make ARCH=arm omap44XXtablet_config #(for Blaze_Tablet)
make ARCH=arm omap44XXsdp_config #(for Blaze)
make ift 2>&1 |tee ${MYDROID}/logs/x-loader_make.out
### For fastboot.sh flashing script needs to rename MLO: ####
mv MLO Blaze_Tablet_OMAP4470_GP_ES1.0_MLO #(for Tablet)

Signing X-LOADER for HS devices

The tool for signing x-loader is provided on TI's package, (MShield). Please contact TI customer representative to get access to this tool.

cd ${YOUR_PATH}/mshield-dk
cp -f ${YOUR_PATH}/x-loader/x-load.bin .
./generate_MLO OMAP4470 ES1.0 x-load.bin

### For fastboot.sh flashing script needs to rename MLO: ####
cp MLO Blaze_Tablet_OMAP4470_HS_ES1.0_MLO  #(For Blaze_Tablet)

Building Kernel

Note: If you are building for a GP device it is recommended not to build the SMC kernel driver.
To create kernel uImage you need to add "mkimage" directory path to your "PATH" environment variable:

cd ${YOUR_PATH}/kernel/android-3.4
make ARCH=arm distclean
make ARCH=arm android_omap_defconfig
make -j$(egrep '^processor' /proc/cpuinfo | wc -l) ARCH=arm uImage 2>&1 |tee ${MYDROID}/logs/kernel_make.out

Building Kernel modules

cd ${YOUR_PATH}/kernel/android-3.4
make ARCH=arm modules 2>&1 |tee ${MYDROID}/logs/kernel_modules.out

Building WLAN driver

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

The above step will produce the following kernel WLAN modules: compat.ko, cfg80211.ko, mac80211.ko, wl18xx.ko, wlcore.ko, wl12xx.ko and wl18xx_sdio.ko. These modules are pushed into the /system/lib/modules directory on the flashed image.

Building Android Filesystem (AFS) with TI Codecs enabled

In the make step below use the number of cores you have available; i.e. -j4 (for 4 cores) or -j12 (for 12 cores)

source build/envsetup.sh

Now depending on your platform use either:

lunch blaze_tablet-userdebug  # (for Blaze Tablet)
lunch full_blaze-userdebug    # (for Blaze)
make clean ;#(required for clean rebuild only)
make -j$(egrep '^processor' /proc/cpuinfo | wc -l) 2>&1 |tee ${MYDROID}/logs/android_make.out

Building AFS with Android Codecs

This release was not verified with Android codecs. Camera based applications need TI proprietary drivers. Please contact TI customer representative to get access to proprietary sources

Building Ducati

Appropriate Ducati binary can be found on Android: Working with pre-built binaries page.

Preparing Android binaries

The following binaries are required by the Blaze Tablet® board. This step will prepare a directory, called myfs, containing all necessary Android files that you

must include within your SD card.

export BOARD_TYPE="blaze_tablet" #or "blaze" depending on your board type

cd ${MYDROID}/out/target/product/${BOARD_TYPE}
mkdir -p system/lib/modules
  cp -fv ${MYDROID}/hardware/ti/wlan/mac80211/compat_wl18xx/compat/compat.ko system/lib/modules/
  cp -fv ${MYDROID}/hardware/ti/wlan/mac80211/compat_wl18xx/net/wireless/cfg80211.ko system/lib/modules/
  cp -fv ${MYDROID}/hardware/ti/wlan/mac80211/compat_wl18xx/net/mac80211/mac80211.ko system/lib/modules/
  cp -fv ${MYDROID}/hardware/ti/wlan/mac80211/compat_wl18xx/drivers/net/wireless/ti/wlcore/wlcore.ko system/lib/modules/
  cp -fv ${MYDROID}/hardware/ti/wlan/mac80211/compat_wl18xx/drivers/net/wireless/ti/wl18xx/wl18xx.ko system/lib/modules/
  cp -fv ${MYDROID}/hardware/ti/wlan/mac80211/compat_wl18xx/drivers/net/wireless/ti/wl12xx/wl12xx.ko system/lib/modules/
  cp -fv ${MYDROID}/hardware/ti/wlan/mac80211/compat_wl18xx/drivers/net/wireless/ti/wlcore/wlcore_sdio.ko system/lib/modules/

mkdir myfs_${BOARD_TYPE}
cd myfs_${BOARD_TYPE}
cp -Rfp ${MYDROID}/out/target/product/${BOARD_TYPE}/root/* .
cp -Rfp ${MYDROID}/out/target/product/${BOARD_TYPE}/system/ .
cp -Rfp ${MYDROID}/out/target/product/${BOARD_TYPE}/data/ .

Preparing eMMC images

mkdir omap4_emmc_files_${BOARD_TYPE}
cd omap4_emmc_files_${BOARD_TYPE}
cp -f ${MYDROID}/out/host/linux-x86/bin/fastboot .
cp -f ${MYDROID}/out/host/linux-x86/bin/mkbootimg .
cp -f ${MYDROID}/out/host/linux-x86/bin/simg2img .
cp -f ${MYDROID}/out/host/linux-x86/bin/make_ext4fs .

cp -f ${YOUR_PATH}/u-boot/u-boot.bin .
cp -f ${YOUR_PATH}/x-loader/Blaze_Tablet_OMAP4470_GP_ES1.0_MLO .  #(or Blaze_GP_ES1.1_MLO)
cp -f ${YOUR_PATH}/kernel/android-3.4/arch/arm/boot/zImage .

cp -f ${YOUR_PATH}/mshield-dk/Blaze_Tablet_OMAP4470_HS_ES1.0_MLO . #(or Blaze_HS_ES1.1_MLO)

Creating img files:

find out/target/product/${BOARD_TYPE} -name *.img -exec rm -f {} \;  
cp -f ${MYDROID}/out/target/product/${BOARD_TYPE}/*.img ${YOUR_PATH}/omap4_emmc_files_${BOARD_TYPE}

This build should not take too much time and will re-generate a new *.img files with the modified init.rc file in it

Now from this new directory we will create the eMMC images which will be flashed using fastboot protocol (described later). First create boot.img image

using kernel image we copied previously:

cd ${YOUR_PATH}/omap4_emmc_files_${BOARD_TYPE}
./mkbootimg --kernel zImage --ramdisk ramdisk.img --base 0x80000000 --board omap4 -o boot.img 

Or for HSIC-modified Tablet2 ONLY use:

./mkbootimg --kernel zImage --ramdisk ramdisk.img --base 0x80000000 --cmdline "omap4_tablet_uses_hsic" --board omap4 -o boot.img

Now create cache partition:

cd ${YOUR_PATH}/omap4_emmc_files_${BOARD_TYPE}
dd if=/dev/zero of=./cache.img bs=1048510 count=128
mkfs.ext4 -F cache.img -L cache

Flashing the OMAP4 Hardware

After the emmc files are available you then can use the fastboot.sh script to upload binaries to your Blaze or Blaze_Tablet. You will need to copy the fastboot.sh script to the location of the eMMC files.

cd ${YOUR_PATH}/omap4_emmc_files_${BOARD_TYPE}
cp ${MYDROID}/device/ti/${BOARD_TYPE}/boot/fastboot.sh .

Connect the Blaze or Blaze_Tablet micro USB port to your Linux box and go to where the eMMC files are. Previous partitions created will be deleted and eMMC will be flashed with new u-boot and MLO. You need to boot the board and start fastboot server on the target (OMAP4 board).

   # fastboot

You should see a message such as:

    "Fastboot started..." or "Fastboot entered..."

When running the fastboot script the command should be issued as super user then run:

  ./fastboot.sh --pwd

Blaze Tablet will boot up on its own with the new image in a few minutes. Until the user interface is ready for use, please avoid interrupting it by pressing any keys etc. This will detect your board and flash the images to the board.

First time flashing on eMMC

If there is no u-boot on your board's eMMC, you will have to boot using SD card. Copy u-boot.bin and MLO files to an SD card (boot partition) and then boot the target board from this external SD card using the following SYSBOOT switch settings to boot from external SD card: 01011101

   For Blaze & Blaze_Tablet board: Switch S2-(1:8): OFF ON OFF ON ON ON OFF ON

Note: S8-(6:1) corresponds to SYSBOOT[5:0] in TRM. (ON=0, OFF=1)

Once you boot the board, start fastboot server on the target (OMAP4 board).

   # fastboot

You should see a message such as:

    "Fastboot started..." or "Fastboot entered..."

Now from the PC execute following commands to flash MLO and u-boot to eMMC

   ./fastboot oem format
   ./fastboot flash xloader ./MLO
   ./fastboot flash bootloader ./u-boot.bin

Now change the following SYSBOOT switch settings to boot out of EMMC: 11111101 whenever the board is restarted.

   For Blaze & Blaze_Tablet board: Switch S2-(1:8): ON ON ON ON ON ON OFF ON

For Formatting the SD Card:

See Android Build SD Configuration page


WLAN Calibration

For optimal Wi-Fi performance calibration of Wi-Fi hardware is mandatory, follow the procedure from http://omappedia.org/wiki/Android_Mac80211#WLAN_Calibration_Instruction

WLAN Firmware files

Wi-Fi firmware files are now part of repo.

Personal tools