4AJ.2.5 OMAP4-Panda Jelly Bean Release Notes

From OMAPpedia

Revision as of 10:13, 27 May 2013 by Andrii (Talk | contribs)
Jump to: navigation, search
This is not official release notes, just community work. So there is not warranty of any kind.
Texas Instruments is not responsible for supporting these notes, it is up to the community.
Feel free to use this instructions under your own risk being aware that if you face any issue you have to fix it by yourself

Contents

Warning!

Document development is still in progress. Please don't use it!

Introduction

This software has been tested in the following software and hardware environment:

OS Kernel: Linux® 3.4
Android: Android JellyBean 4.2.2
Parent TI release Android JB 4AJ.2.5
Toolchain: Andriod linux-x86 toolchain arm-eabi-4.6
Reference hardware platforms: TI OMAP4 4460 Pandaboard ES
Build Host OS: Ubuntu 12.04 LTS x86_64

Current status

Tools & Dependency packages

Pre-requisite packages for building the Android Filesystem (Note: This is with reference to Ubuntu 12.04 64-bit). Ubuntu 64-bit is required for the cross-compilation of Android JellyBean Filesystem.


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
sudo apt-get install lib32readline6-dev libstdc++6 lib32z1 lib32z1-dev ia32-libs g++-multilib libx11-dev lib32ncurses5-dev

Add the partner repositories and install the Oracle/Sun JDK:

Please find proper guide somewhere in Google

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

Tool Chain for building Kernel and Drivers

The Kernel and Driver sources are built using Andriod linux-x86 toolchain arm-eabi-4.6 (This particular version is needed for the AFS to work properly).

It is already inside Android source tree.


Setting up environment

From your work directory:

cd <your work directory>
mkdir -p 4AJ.2.5-panda; cd 4AJ.2.5-panda
export YOUR_PATH=`pwd`
mkdir -p mydroid
cd mydroid
export MYDROID=`pwd`

Downloading Release Software

To obtain Android Filesystem Sources follow:

cd ${MYDROID}
repo init -u git://git.omapzoom.org/platform/omapmanifest.git -b 27.x -m RLS4AJ.2.5_JellyBean.xml
repo sync

To obtain Kernel & Driver Sources follow:

cd ${YOUR_PATH}
git clone git://git.omapzoom.org/kernel/omap.git kernel/android-3.4
cd kernel/android-3.4
git checkout origin/p-android-omap-3.4

To obtain OMAPBOOT Sources follow:

cd ${YOUR_PATH}
git clone git://git.omapzoom.org/repo/omapboot.git omapboot
cd omapboot
git checkout origin/p-master-dev

Patching for Pandaboard Support

Patching KERNEL

cd ${YOUR_PATH}/kernel/android-3.4
git fetch http://review.omapzoom.org/kernel/omap refs/changes/85/31985/3 && git checkout FETCH_HEAD
git fetch http://review.omapzoom.org/kernel/omap refs/changes/24/32424/1 && git checkout FETCH_HEAD

Patching OMAPBOOT

cd ${YOUR_PATH}/omapboot
git fetch http://review.omapzoom.org/repo/omapboot refs/changes/42/32442/3 && git checkout FETCH_HEAD
<patch for recovery is under work, but it is not critical>

Patching MYDROID

cd ${MYDROID}/device/ti/panda
git fetch http://review.omapzoom.org/device/ti/panda refs/changes/69/32669/1 && git cherry-pick FETCH_HEAD
git fetch http://review.omapzoom.org/device/ti/panda refs/changes/70/32670/1 && git cherry-pick FETCH_HEAD
git fetch http://review.omapzoom.org/device/ti/panda refs/changes/71/32671/2 && git cherry-pick FETCH_HEAD
git fetch http://review.omapzoom.org/device/ti/panda refs/changes/72/32672/2 && git cherry-pick FETCH_HEAD
git fetch http://review.omapzoom.org/device/ti/panda refs/changes/73/32673/2 && git cherry-pick FETCH_HEAD
git fetch http://review.omapzoom.org/device/ti/panda refs/changes/74/32674/2 && git cherry-pick FETCH_HEAD
git fetch http://review.omapzoom.org/device/ti/panda refs/changes/75/32675/2 && git cherry-pick FETCH_HEAD
git fetch http://review.omapzoom.org/device/ti/panda refs/changes/76/32676/2 && git cherry-pick FETCH_HEAD
git fetch http://review.omapzoom.org/device/ti/panda refs/changes/77/32677/2 && git cherry-pick FETCH_HEAD

Build Instructions

Setting up build environment

cd ${YOUR_PATH}
export PATH=$PATH:${MYDROID}/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6
mkdir $MYDROID/logs
export CROSS_COMPILE=arm-eabi-

Building OMAPBOOT

cd ${YOUR_PATH}/omapboot
make distclean
make ARCH=arm MACH=omap4 BOARD=panda 2>&1 |tee $MYDROID/logs/omapboot_make.out

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 ARCH=arm distclean
make ARCH=arm panda_defconfig
make 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_wl12xx
export KERNEL_DIR=${YOUR_PATH}/kernel/android-3.4
export KLIB=${KERNEL_DIR}
export KLIB_BUILD=${KERNEL_DIR}
make ARCH=arm

The above step will produce the following kernel WLAN modules: compat.ko, cfg80211.ko, mac80211.ko, wl12xx.ko and wl12xx_sdio.ko. These modules are pushed into the /system/lib/modules directory on the system 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)

cd $MYDROID
source build/envsetup.sh
lunch full_panda-userdebug
make clean ;#(required for rebuild only)
make -j4 2>&1 |tee $MYDROID/logs/android_make.out

Building AFS with Android Codecs

This release was not verified with Android codecs.

Building SGX driver

Extract the source code from the tarball if you haven't yet

cd $MYDROID/device/ti/proprietary-open/omap4/sgx_src
tar xzf eurasia_km.tgz
cd $MYDROID/device/ti/proprietary-open/omap4/sgx_src/eurasia_km/eurasiacon/build/linux2/omap4430_android
export KERNELDIR=${YOUR_PATH}/kernel/android-3.4
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- TARGET_PRODUCT="blaze_tablet" BUILD=release TARGET_SGX=540 PLATFORM_VERSION=4.0

The above step will produce the following kernel SGX modules: pvrsrvkm_sgx540_120.ko and omaplfb_sgx540_120.ko. These modules are pushed into the /system/lib/modules directory on the system image.

Note that you need to add DISPLAY_CONTROLLER_COMPONENT := dc_omapfb3_linux in eurasia_km/eurasiacon/build/linux2/omap4430_android/Makefile to generate omaplfb_sgx540_120.ko

Preparing Android binaries

The following binaries maybe are not required by the Panda board.

export BOARD_TYPE="panda"

cd $MYDROID/out/target/product/$BOARD_TYPE
mkdir -p system/lib/modules
cp $MYDROID/hardware/ti/wlan/mac80211/compat_wl12xx/compat/compat.ko system/lib/modules/
cp $MYDROID/hardware/ti/wlan/mac80211/compat_wl12xx/net/wireless/cfg80211.ko system/lib/modules/
cp $MYDROID/hardware/ti/wlan/mac80211/compat_wl12xx/net/mac80211/mac80211.ko system/lib/modules/
cp $MYDROID/hardware/ti/wlan/mac80211/compat_wl12xx/drivers/net/wireless/wl12xx/wl12xx.ko system/lib/modules/
cp $MYDROID/hardware/ti/wlan/mac80211/compat_wl12xx/drivers/net/wireless/wl12xx/wl12xx_sdio.ko system/lib/modules/

cp $MYDROID/out/target/product/$BOARD_TYPE/target/kbuild/omaplfb_sgx540_120.ko system/lib/modules/
cp $MYDROID/out/target/product/$BOARD_TYPE/target/kbuild/pvrsrvkm_sgx540_120.ko system/lib/modules/

Preparing images

cd $YOUR_PATH
mkdir omap4_sd_files_$BOARD_TYPE
cd omap4_sd_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}/x-loader/MLO .
cp -f ${YOUR_PATH}/u-boot/u-boot.bin .
cp -f ${YOUR_PATH}/kernel/android-3.0/arch/arm/boot/zImage .


Creating img files:

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

This build should not take too much time and will re-generate a new *.img files.

Now from this new directory we will create the SD 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_sd_files_$BOARD_TYPE
$MYDROID/device/ti/support-tools/boot/omap4/umulti2.sh 

Now create cache partition:

cd $YOUR_PATH/omap4_sd_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

First time flashing on SD

If there is no u-boot on your board, 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. Once you boot the board, start fastboot server on the target (Pandaboard).

# fastboot

You should see a message such as:

"Fastboot entered..."

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

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

This will create several partitions on your SD card that has specific proposes for the Panda board

For Formatting the SD Card:

See Android Build SD Configuration page

Not first time flashing on SD

After the SD files are available you then can use the fastboot to upload binaries to your Panda or Panda ES.

Connect the Panda or Panda ES mini USB port to your Linux machine and go to where the SD files are. Previous partitions created will be deleted and SD will be flashed with new u-boot and MLO. You need to boot the board and start fastboot server on the target (Pandaboard) by keeping the USER button press.

You should see a message such as:

"Fastboot entered..."

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

sudo ./fastboot flash xloader panda_OMAP4460_GP_ES1.1_MLO
sudo ./fastboot flash bootloader sboot.bin
sudo ./fastboot flash boot boot.img
sudo ./fastboot flash system system.img
sudo ./fastboot flash cache cache.img
sudo ./fastboot flash userdata userdata.img
sudo ./fastboot reboot

Panda board 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.

Resources

4AJ.2.5 Release

To get a stable release as base for the porting the 4AJ.2.5 Texas Instrument release for Blaze and Blaze Tablet was considered 4AJ.2.5 OMAP4 Jelly Bean Release Notes

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

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox