4AJ.2.2 OMAP4 Jelly Bean Panda Notes

From OMAPpedia

(Difference between revisions)
Jump to: navigation, search
(Patching MYDROID)
 
(4 intermediate revisions not shown)
Line 2: Line 2:
  Texas Instruments is not responsible for supporting these notes, it is up to the community.
  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
  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
-
 
-
'''/_\ Building in process due to verification'''
 
=Introduction=
=Introduction=
Line 127: Line 125:
===Patching MYDROID===
===Patching MYDROID===
-
Download and apply [https://gforge.ti.com/gf/download/frsrelease/961/6240/proprietaryopenpanda.patch proprietaryopenpanda.patch] [https://gforge.ti.com/gf/download/frsrelease/961/6239/hardwarepanda.patch hardwarepanda.patch]
+
Download and apply [https://gforge.ti.com/gf/download/frsrelease/961/6240/proprietaryopenpanda.patch proprietaryopenpanda.patch] [https://gforge.ti.com/gf/download/frsrelease/961/6239/hardwarepanda.patch hardwarepanda.patch] [https://gforge.ti.com/gf/download/frsrelease/1021/6404/hardwarepanda2.patch hardwarepatch2.patch]
  cd ${MYDROID}/device/ti/panda
  cd ${MYDROID}/device/ti/panda
Line 136: Line 134:
  cd ${MYDROID}/hardware/ti/wlan
  cd ${MYDROID}/hardware/ti/wlan
  git am hardwarepanda.patch
  git am hardwarepanda.patch
 +
git am hardwarepanda2.patch
=Build Instructions=
=Build Instructions=
Line 198: Line 197:
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)
-
<pre>
+
 
-
cd $MYDROID
+
cd $MYDROID
-
source build/envsetup.sh
+
source build/envsetup.sh
-
lunch full_panda-eng
+
lunch full_panda-eng
-
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>
+
===Building AFS with Android Codecs===
===Building AFS with Android Codecs===
Line 213: Line 211:
Extract the source code from the tarball if you haven't yet
Extract the source code from the tarball if you haven't yet
-
<pre>
+
cd $MYDROID/device/ti/proprietary-open/omap4/sgx_src
-
cd $MYDROID/device/ti/proprietary-open/omap4/sgx_src
+
tar xzf eurasia_km.tgz
-
tar xzf eurasia_km.tgz
+
-
</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.0
+
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>
+
The above step will produce the following kernel SGX modules: ''pvrsrvkm_sgx540_112.ko'' and ''omaplfb_sgx540_112.ko''. These modules are pushed into the ''/system/lib/modules'' directory on the system image.
The above step will produce the following kernel SGX modules: ''pvrsrvkm_sgx540_112.ko'' and ''omaplfb_sgx540_112.ko''. These modules are pushed into the ''/system/lib/modules'' directory on the system image.
Line 230: Line 224:
The following binaries maybe are not required by the Panda board.
The following binaries maybe are not required by the Panda board.
-
<pre>
+
export BOARD_TYPE="panda"
-
export BOARD_TYPE="panda"
+
-
cd $MYDROID/out/target/product/$BOARD_TYPE
+
cd $MYDROID/out/target/product/$BOARD_TYPE
-
mkdir -p system/lib/modules
+
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/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/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/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.ko system/lib/modules/
-
cp $MYDROID/hardware/ti/wlan/mac80211/compat_wl12xx/drivers/net/wireless/wl12xx/wl12xx_sdio.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/
-
cp $MYDROID/out/target/product/$BOARD_TYPE/target/kbuild/pvrsrvkm_sgx540_120.ko system/lib/modules/
+
-
</pre>
+
===Updating Ducati===
===Updating Ducati===

Latest revision as of 23:56, 20 February 2013

These Notes are an effort from the community to port the 4AJ.2.2 Release from Texas Instruments to the Panda and Panda ES boards without any 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

[edit] Introduction

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

OS Kernel: Linux® 3.0
Android: Android Jelly Bean 4.1.2
Toolchain: CodeSourcery compiler version Sourcery G++ Lite 2010q1-202 for ARM GNU/Linux
Reference hardware platforms: TI OMAP4 4430/60 Pandaboard and Pandaboard ES
Build Host OS: Ubuntu 12.04

[edit] 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 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 lib32readline6-dev libstdc++6 lib32z1 lib32z1-dev ia32-libs g++-multilib libx11-dev lib32ncurses5-dev uboot-mkimage

The following commands will install the host compilers needed in your server:

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++

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

[edit] Downloading Release Software

To obtain Android Filesystem Sources follow:

cd <your work directory>
mkdir -p 4AJ.2.2; cd 4AJ.2.2
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.2_JellyBean.xml
repo sync

To obtain Kernel & Driver Sources follow:

cd ${YOUR_PATH}
git clone git@github.com:icepeda/omap.git kernel/android-3.0
cd kernel/android-3.0
git fetch origin icepeda-panda-4aj22:master
git checkout master

To obtain U-Boot Sources follow:

cd ${YOUR_PATH}
git clone git://git.omapzoom.org/repo/u-boot.git u-boot
cd u-boot
git checkout 2af35fca236557add6fdd33b836bf5c64455ac8f

To obtain X-loader Sources follow:

cd ${YOUR_PATH}
git clone git://git.omapzoom.org/repo/x-loader.git x-loader
cd x-loader
git checkout 4975b24da3887edff5cd24e44ca7cb4013f04239

[edit] Release Content

This release has the below content: - Kernel and Drivers tested with Pandaboard ES and verified with Jelly Bean UI - A9 source code for accelerating Video

[edit] Patching for Pandaboard Support

[edit] Setting up environment

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

export YOUR_PATH=`pwd`
export MYDROID=${YOUR_PATH}/mydroid

[edit] Patching X-LOADER

Download and apply xloaderpanda.patch

cd ${YOUR_PATH}/x-loader
git am xloaderpanda.patch

[edit] Patching U-BOOT

Download and apply ubootpanda.patch

cd ${YOUR_PATH}/u-boot
git am ubootpanda.patch

[edit] Patching KERNEL

Not needed with icepeda kernel

[edit] Patching MYDROID

Download and apply proprietaryopenpanda.patch hardwarepanda.patch hardwarepatch2.patch

cd ${MYDROID}/device/ti/panda
git fetch git@github.com:icepeda/panda.git icepeda-panda-4aj22:master
git checkout master
cd ${MYDROID}/device/ti/proprietary-open
git am proprietaryopenpanda.patch
cd ${MYDROID}/hardware/ti/wlan
git am hardwarepanda.patch
git am hardwarepanda2.patch

[edit] Build Instructions

[edit] Setting up build environment

From your work directory (where your 4AI.1.7 folder resides):

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

[edit] Building X-LOADER

cd ${YOUR_PATH}/x-loader
make distclean	
make ARCH=arm omap44XXpanda_config
make ift 2>&1 |tee $MYDROID/logs/x-loader_make.out

[edit] Building U-BOOT

cd ${YOUR_PATH}/u-boot
make distclean
make ARCH=arm omap44XXpanda_config
make 2>&1 |tee $MYDROID/logs/u-boot_make.out

[edit] 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.0
make ARCH=arm distclean
make ARCH=arm panda_defconfig
make ARCH=arm uImage 2>&1 |tee $MYDROID/logs/kernel_make.out

[edit] Building Kernel modules

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

[edit] Building WLAN driver

cd $MYDROID/hardware/ti/wlan/mac80211/compat_wl12xx
export KERNEL_DIR=${YOUR_PATH}/kernel/android-3.0
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.

[edit] 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-eng
make clean ;#(required for rebuild only)
make -j4 2>&1 |tee $MYDROID/logs/android_make.out

[edit] Building AFS with Android Codecs

This release was not verified with Android codecs.

[edit] 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.0
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_112.ko and omaplfb_sgx540_112.ko. These modules are pushed into the /system/lib/modules directory on the system image.

[edit] 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/pvrsrvkm_sgx540_120.ko system/lib/modules/

[edit] Updating Ducati

For hardware accelerated video playback and camera usage you have to use proper Ducati binary. Found here ducati-m3.bin

Download the ducati-m3.bin for the 4AJ.2.2 release and place binary in system/vendor/firmware/ :

cp <location-of-downloaded-ducati-bin>/4AJ.2.2_Blaze_ducati-m3.bin ${MYDROID}/out/target/product/panda/system/vendor/firmware/ducati-m3.bin

[edit] 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
./mkbootimg --kernel zImage --ramdisk ramdisk.img --base 0x80000000 --board omap4 -o boot.img

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

[edit] Flashing the OMAP4 Hardware

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

For Formatting the SD Card:

See Android Build SD Configuration page

[edit] Not first time flashing on SD

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

Connect the Pandaboard or Pandaboard 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 MLO
sudo ./fastboot flash bootloader u-boot.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

Pandaboard 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.

[edit] Resources

[edit] 4AJ.2.2 Release

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

[edit] Prebuilt Binaries

Not available yet

[edit] Panda Porting

The porting to Panda progress can be track at isrccepeda blogspot

[edit] Videos

Don't forget to give like, thanks!

First video about Panda Porting: 4AI on Panda ES Multimedia

Second video about Panda Porting: 4AI on Panda ES Connectivity

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

[edit] WLAN Firmware files

Wi-Fi firmware files are now part of repo.

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox