4AJ.2.5 OMAP4-Panda Jelly Bean Release Notes

From OMAPpedia

(Difference between revisions)
Jump to: navigation, search
(Created page with " 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 ...")
(4 intermediate revisions not shown)
Line 6: Line 6:
<span style="background:#FFD700"> Document development is still in progress. Please don't use it! </span>
<span style="background:#FFD700"> Document development is still in progress. Please don't use it! </span>
-
=Introduction=
+
= Introduction =
This software has been tested in the following software and hardware environment:
This software has been tested in the following software and hardware environment:
'''OS Kernel:''' Linux® 3.4 <br>
'''OS Kernel:''' Linux® 3.4 <br>
'''Android:'''  Android JellyBean 4.2.2<br>
'''Android:'''  Android JellyBean 4.2.2<br>
-
'''Parent TI release''' Android JB 4AJ2.1<br>
+
'''Parent TI release''' Android JB 4AJ.2.5<br>
'''Toolchain:''' Andriod linux-x86 toolchain arm-eabi-4.6<br>
'''Toolchain:''' Andriod linux-x86 toolchain arm-eabi-4.6<br>
'''Reference hardware platforms:''' TI OMAP4 4460 Pandaboard ES<br>
'''Reference hardware platforms:''' TI OMAP4 4460 Pandaboard ES<br>
'''Build Host OS:''' Ubuntu 12.04 LTS x86_64<br>
'''Build Host OS:''' Ubuntu 12.04 LTS x86_64<br>
-
=Current status=
+
= Current status =
* Device is booting up to UI
* Device is booting up to UI
* HDMI connection: works
* HDMI connection: works
Line 22: Line 22:
* USB Host: works
* USB Host: works
* Mouse connected to USB works
* Mouse connected to USB works
-
* Ethernet: drivers works; UI settings is not working, the issue is fully investigated but not all patches are ready yet
+
* Ethernet: not done yet
-
* Audio/Video playback: is not working
+
* Audio/Video playback: not done yet
-
* WiFi/Bluetooth: is not working
+
* WiFi/Bluetooth: not done yet
-
 
+
= Tools & Dependency packages =
-
 
+
-
=Tools & Dependency packages=
+
'''Pre-requisite packages for building the Android Filesystem (Note: This is with reference to Ubuntu 12.04 64-bit).'''
'''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 Ice Cream Sandwich Filesystem.'''
+
'''Ubuntu 64-bit is required for the cross-compilation of Android JellyBean Filesystem.'''
-
If you are behind a firewall, you will have to set-up firewall using the instructions in [http://omapedia.org/wiki/Host_PC_Setup].
 
The following commands will install the correct packages to your server:
The following commands will install the correct packages to your server:
Line 42: Line 39:
</pre>
</pre>
-
The following commands will install the host compilers needed in your server:
+
Add the partner repositories and install the Oracle/Sun JDK:
-
<pre>
+
''Please find proper guide somewhere in Google''
-
sudo apt-get install gcc-4.4 gcc-4.4-multilib g++-4.4 g++-4.4-multilib
+
-
cd /usr/bin
+
-
sudo ln -sf gcc-4.4 gcc
+
-
sudo ln -sf g++-4.4 g++
+
-
</pre>
+
-
 
+
-
Add the partner repositories and install the JDK:
+
-
 
+
-
<pre>
+
-
sudo add-apt-repository "deb http://archive.canonical.com/ lucid partner"
+
-
sudo apt-get update
+
-
sudo apt-get install sun-java6-jdk
+
-
</pre>
+
Install ''repo'' tool:
Install ''repo'' tool:
Line 69: Line 53:
</pre>
</pre>
-
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 Andriod linux-x86 toolchain arm-eabi-4.6 (This particular version is needed for the AFS to work properly).
-
'''Tool Chain for building Kernel and Drivers'''
+
It is already inside Android source tree.
-
The Kernel and Driver sources are built using Sourcery G++ Lite 2010q1-202 for ARM GNU/Linux version (This particular version is needed for the AFS to work properly).
 
-
This tool chain can be obtained from [http://www.codesourcery.com/sgpp/lite/arm/portal/package6488/public/arm-none-linux-gnueabi/arm-2010q1-202-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2].
+
= Setting up environment =
-
 
+
From your work directory:
-
=Downloading Release Software=
+
-
To obtain '''Android Filesystem Sources''' follow:
+
<pre>
<pre>
cd <your work directory>
cd <your work directory>
-
mkdir -p 4AJ.2.1; cd 4AJ.2.1
+
mkdir -p 4AJ.2.5-panda; cd 4AJ.2.5-panda
export YOUR_PATH=`pwd`
export YOUR_PATH=`pwd`
-
mkdir -p mydroid; cd mydroid
+
mkdir -p mydroid
 +
cd mydroid
export MYDROID=`pwd`
export MYDROID=`pwd`
-
repo init -u git://git.omapzoom.org/platform/omapmanifest.git -b 27.x -m RLS4AJ.2.1_JellyBean.xml
 
-
repo sync
 
</pre>
</pre>
-
To obtain '''Kernel & Driver Sources''' follow:
+
= Downloading Release Software =
 +
To obtain '''Android Filesystem Sources''' follow:
 +
 
<pre>
<pre>
-
cd ${YOUR_PATH}
+
cd ${MYDROID}
-
git clone git://git.omapzoom.org/kernel/omap.git kernel/android-3.0
+
repo init -u git://git.omapzoom.org/platform/omapmanifest.git -b 27.x -m RLS4AJ.2.5_JellyBean.xml
-
cd kernel/android-3.0
+
repo sync
-
git checkout cda0054a3304d5fb744e4ff26f5f72b4fcf1a572
+
</pre>
</pre>
-
To obtain '''U-Boot Sources''' follow:
+
To obtain '''Kernel & Driver Sources''' follow:
<pre>
<pre>
cd ${YOUR_PATH}
cd ${YOUR_PATH}
-
git clone git://git.omapzoom.org/repo/u-boot.git u-boot
+
git clone git://git.omapzoom.org/kernel/omap.git kernel/android-3.4
-
cd u-boot
+
cd kernel/android-3.4
-
git checkout a7a88624fb4d9b39c2a308c89d1d5ffb239072a9
+
git checkout origin/p-android-omap-3.4
</pre>
</pre>
-
To obtain '''X-loader Sources''' follow:
+
To obtain '''OMAPBOOT Sources''' follow:
<pre>
<pre>
cd ${YOUR_PATH}
cd ${YOUR_PATH}
-
git clone git://git.omapzoom.org/repo/x-loader.git x-loader
+
git clone git://git.omapzoom.org/repo/omapboot.git omapboot
-
cd x-loader
+
cd omapboot
-
git checkout 8eb4c159f0eef422dddfa1e0c7954096c107d224
+
git checkout origin/p-master-dev
</pre>
</pre>
-
=Release Content=
+
= Patching for Pandaboard Support =
-
 
+
-
This release has the below content:
+
-
- A9 source code for accelerating Video
+
-
 
+
-
=Patching for Pandaboard Support=
+
-
 
+
-
===Setting up environment===
+
-
From your work directory (where your 4AJ.2.1 folder resides):
+
 +
== Patching KERNEL ==
<pre>
<pre>
-
export YOUR_PATH=`pwd`
+
cd ${YOUR_PATH}/kernel/android-3.4
-
export MYDROID=${YOUR_PATH}/mydroid
+
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
</pre>
</pre>
-
===Patching KERNEL===
+
== Patching OMAPBOOT ==
<pre>
<pre>
-
cd ${YOUR_PATH}/kernel/android-3.0
+
cd ${YOUR_PATH}/omapboot
-
git fetch http://review.omapzoom.org/kernel/omap refs/changes/88/30588/1 && git cherry-pick FETCH_HEAD
+
git fetch http://review.omapzoom.org/repo/omapboot refs/changes/42/32442/3 && git checkout FETCH_HEAD
-
git fetch http://review.omapzoom.org/kernel/omap refs/changes/89/30589/1 && git cherry-pick FETCH_HEAD
+
<patch for recovery is under work, but it is not critical>
-
git fetch http://review.omapzoom.org/kernel/omap refs/changes/90/30590/1 && git cherry-pick FETCH_HEAD
+
-
git fetch http://review.omapzoom.org/kernel/omap refs/changes/91/30591/1 && git cherry-pick FETCH_HEAD
+
-
git fetch http://review.omapzoom.org/kernel/omap refs/changes/92/30592/1 && git cherry-pick FETCH_HEAD
+
-
git fetch http://review.omapzoom.org/kernel/omap refs/changes/93/30593/1 && git cherry-pick FETCH_HEAD
+
-
git fetch http://review.omapzoom.org/kernel/omap refs/changes/94/30594/1 && git cherry-pick FETCH_HEAD
+
-
git fetch http://review.omapzoom.org/kernel/omap refs/changes/95/30595/1 && git cherry-pick FETCH_HEAD
+
-
git fetch http://review.omapzoom.org/kernel/omap refs/changes/96/30596/1 && git cherry-pick FETCH_HEAD
+
-
git fetch http://review.omapzoom.org/kernel/omap refs/changes/97/30597/1 && git cherry-pick FETCH_HEAD
+
</pre>
</pre>
-
===Patching MYDROID===
+
== Patching MYDROID ==
<pre>
<pre>
cd ${MYDROID}/device/ti/panda
cd ${MYDROID}/device/ti/panda
-
git fetch http://review.omapzoom.org/device/ti/panda refs/changes/18/30518/1 && git cherry-pick FETCH_HEAD
+
git fetch http://review.omapzoom.org/device/ti/panda refs/changes/69/32669/1 && git checkout FETCH_HEAD
-
git fetch http://review.omapzoom.org/device/ti/panda refs/changes/19/30519/1 && git cherry-pick FETCH_HEAD
+
git fetch http://review.omapzoom.org/device/ti/panda refs/changes/70/32670/1 && git checkout FETCH_HEAD
-
git fetch http://review.omapzoom.org/device/ti/panda refs/changes/20/30520/1 && git cherry-pick FETCH_HEAD
+
git fetch http://review.omapzoom.org/device/ti/panda refs/changes/71/32671/2 && git checkout FETCH_HEAD
-
git fetch http://review.omapzoom.org/device/ti/panda refs/changes/85/30585/2 && git cherry-pick FETCH_HEAD
+
git fetch http://review.omapzoom.org/device/ti/panda refs/changes/72/32672/2 && git checkout FETCH_HEAD
-
 
+
git fetch http://review.omapzoom.org/device/ti/panda refs/changes/73/32673/2 && git checkout FETCH_HEAD
-
cd ${MYDROID}/device/ti/proprietary-open
+
git fetch http://review.omapzoom.org/device/ti/panda refs/changes/74/32674/2 && git checkout FETCH_HEAD
-
git fetch http://review.omapzoom.org/device/ti/proprietary-open refs/changes/59/30659/1 && git cherry-pick FETCH_HEAD
+
git fetch http://review.omapzoom.org/device/ti/panda refs/changes/75/32675/2 && git checkout FETCH_HEAD
-
 
+
git fetch http://review.omapzoom.org/device/ti/panda refs/changes/76/32676/2 && git checkout FETCH_HEAD
-
cd ${MYDROID}/device/ti/common-open
+
git fetch http://review.omapzoom.org/device/ti/panda refs/changes/77/32677/2 && git checkout FETCH_HEAD
-
git fetch http://review.omapzoom.org/device/ti/common-open refs/changes/60/30660/1 && git cherry-pick FETCH_HEAD
+
-
 
+
-
cd ${MYDROID}/hardware/ti/wlan
+
-
git fetch http://review.omapzoom.org/platform/hardware/ti/wlan refs/changes/61/30661/1 && git cherry-pick FETCH_HEAD
+
</pre>
</pre>
-
=Build Instructions=
+
= Build Instructions =
-
===Setting up build environment===
+
== Setting up build environment ==
-
From your work directory (where your 4AJ.2.1 folder resides):
+
<pre>
<pre>
-
export YOUR_PATH=`pwd`
+
cd ${YOUR_PATH}
-
export PATH=$PATH:<toolchain_parent_dir>/arm-2010q1/bin
+
export PATH=$PATH:${MYDROID}/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6
-
export MYDROID=${YOUR_PATH}/mydroid
+
mkdir $MYDROID/logs
mkdir $MYDROID/logs
-
export CROSS_COMPILE=arm-none-linux-gnueabi-
+
export CROSS_COMPILE=arm-eabi-
-
export PATH=${YOUR_PATH}/u-boot/tools:$PATH
+
-
</pre>
+
-
 
+
-
===Building X-LOADER===
+
-
<pre>
+
-
cd ${YOUR_PATH}/x-loader
+
-
make distclean
+
-
make ARCH=arm omap4430panda_config
+
-
make ift 2>&1 |tee $MYDROID/logs/x-loader_make.out
+
</pre>
</pre>
-
===Building U-BOOT===
+
== Building OMAPBOOT ==
<pre>
<pre>
-
cd ${YOUR_PATH}/u-boot
+
cd ${YOUR_PATH}/omapboot
make distclean
make distclean
-
make ARCH=arm omap4430panda_config
+
make ARCH=arm MACH=omap4 BOARD=panda 2>&1 |tee $MYDROID/logs/omapboot_make.out
-
make 2>&1 |tee $MYDROID/logs/u-boot_make.out
+
</pre>
</pre>
-
===Building Kernel===
+
== Building Kernel ==
To create kernel uImage you need to add "mkimage" directory path to your "PATH" environment variable:
To create kernel uImage you need to add "mkimage" directory path to your "PATH" environment variable:
<pre>
<pre>
-
cd ${YOUR_PATH}/kernel/android-3.0
+
cd ${YOUR_PATH}/kernel/android-3.4
make ARCH=arm distclean
make ARCH=arm distclean
make ARCH=arm panda_defconfig
make ARCH=arm panda_defconfig
Line 201: Line 153:
</pre>
</pre>
-
===Building Kernel modules===
+
== Building Kernel modules ==
<pre>
<pre>
-
cd ${YOUR_PATH}/kernel/android-3.0
+
cd ${YOUR_PATH}/kernel/android-3.4
make ARCH=arm modules 2>&1 |tee $MYDROID/logs/kernel_modules.out
make ARCH=arm modules 2>&1 |tee $MYDROID/logs/kernel_modules.out
</pre>
</pre>
-
===Building WLAN driver===
+
== Building WLAN driver ==
<pre>
<pre>
cd $MYDROID/hardware/ti/wlan/mac80211/compat_wl12xx
cd $MYDROID/hardware/ti/wlan/mac80211/compat_wl12xx
-
export KERNEL_DIR=${YOUR_PATH}/kernel/android-3.0
+
export KERNEL_DIR=${YOUR_PATH}/kernel/android-3.4
export KLIB=${KERNEL_DIR}
export KLIB=${KERNEL_DIR}
export KLIB_BUILD=${KERNEL_DIR}
export KLIB_BUILD=${KERNEL_DIR}
Line 218: Line 170:
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.
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===
+
== 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)
In the make step below use the number of cores you have available; i.e. -j4 (for 4 cores) or -j12 (for 12 cores)
Line 224: Line 176:
cd $MYDROID
cd $MYDROID
source build/envsetup.sh
source build/envsetup.sh
-
lunch full_panda-eng
+
lunch full_panda-userdebug
make clean ;#(required for rebuild only)
make clean ;#(required for rebuild only)
make -j4 2>&1 |tee $MYDROID/logs/android_make.out
make -j4 2>&1 |tee $MYDROID/logs/android_make.out
</pre>
</pre>
-
===Building AFS with Android Codecs===
+
== Building AFS with Android Codecs ==
This release was not verified with Android codecs.
This release was not verified with Android codecs.
-
===Building SGX driver===
+
== Building SGX driver ==
Extract the source code from the tarball if you haven't yet
Extract the source code from the tarball if you haven't yet
Line 243: Line 195:
<pre>
<pre>
cd $MYDROID/device/ti/proprietary-open/omap4/sgx_src/eurasia_km/eurasiacon/build/linux2/omap4430_android
cd $MYDROID/device/ti/proprietary-open/omap4/sgx_src/eurasia_km/eurasiacon/build/linux2/omap4430_android
-
export KERNELDIR=${YOUR_PATH}/kernel/android-3.0
+
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
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- TARGET_PRODUCT="blaze_tablet" BUILD=release TARGET_SGX=540 PLATFORM_VERSION=4.0
</pre>
</pre>
Line 251: Line 203:
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
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===
+
== Preparing Android binaries ==
The following binaries maybe are not required by the Panda board.
The following binaries maybe are not required by the Panda board.
Line 270: Line 222:
</pre>
</pre>
-
===Preparing images===
+
== Preparing images ==
<pre>
<pre>
cd $YOUR_PATH
cd $YOUR_PATH
Line 312: Line 264:
</pre>
</pre>
-
===Flashing the OMAP4 Hardware===
+
== Flashing the OMAP4 Hardware ==
-
====First time flashing on SD====
+
=== 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).  
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).  
Line 337: Line 289:
See [http://omappedia.org/wiki/Android_Build_SD_Configuration Android Build SD Configuration] page
See [http://omappedia.org/wiki/Android_Build_SD_Configuration Android Build SD Configuration] page
-
====Not first time flashing on SD====
+
=== 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.
After the SD files are available you then can use the ''fastboot'' to upload binaries to your Panda or Panda ES.
Line 350: Line 302:
When running the fastboot the command should be issued as super user then run:
When running the fastboot the command should be issued as super user then run:
-
  sudo ./fastboot flash xloader MLO
+
  sudo ./fastboot flash xloader panda_OMAP4460_GP_ES1.1_MLO
-
  sudo ./fastboot flash bootloader u-boot.bin
+
  sudo ./fastboot flash bootloader sboot.bin
  sudo ./fastboot flash boot boot.img
  sudo ./fastboot flash boot boot.img
  sudo ./fastboot flash system system.img
  sudo ./fastboot flash system system.img
Line 361: Line 313:
This will detect your board and flash the images to the board.
This will detect your board and flash the images to the board.
-
='''Resources'''=
+
= Resources =
-
===4AJ.2.1 Release===
+
== 4AJ.2.5 Release ==
-
To get a stable release as base for the porting the 4AJ.2.1 Texas Instrument release for Blaze and Blaze Tablet was considered [[4AJ.2.1 OMAP4 Jelly Bean Release Notes]]
+
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===
+
== 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
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

Revision as of 08:01, 2 May 2013

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 checkout FETCH_HEAD
git fetch http://review.omapzoom.org/device/ti/panda refs/changes/70/32670/1 && git checkout FETCH_HEAD
git fetch http://review.omapzoom.org/device/ti/panda refs/changes/71/32671/2 && git checkout FETCH_HEAD
git fetch http://review.omapzoom.org/device/ti/panda refs/changes/72/32672/2 && git checkout FETCH_HEAD
git fetch http://review.omapzoom.org/device/ti/panda refs/changes/73/32673/2 && git checkout FETCH_HEAD
git fetch http://review.omapzoom.org/device/ti/panda refs/changes/74/32674/2 && git checkout FETCH_HEAD
git fetch http://review.omapzoom.org/device/ti/panda refs/changes/75/32675/2 && git checkout FETCH_HEAD
git fetch http://review.omapzoom.org/device/ti/panda refs/changes/76/32676/2 && git checkout FETCH_HEAD
git fetch http://review.omapzoom.org/device/ti/panda refs/changes/77/32677/2 && git checkout 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