L27.INC1.12.1 OMAP4 GingerBread ES2 Release Notes

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

Please note Toolchain required is 2010q1-202.

OS Kernel: Linux® 2.6.35 Android:  Android Gingerbread 2.3.3 Toolchain: CodeSourcery compiler version Sourcery G++ Lite 2010q1-202 for ARM GNU/Linux Reference hardware platform: TI OMAP4 ES2.2 EMU Blaze Build Host OS: Ubuntu Daily Build Version: Gingerbread_DailyBuild_144

=Tools & Dependency packages=

Pre-requisite packages for build Android Filesystem (Note this is with reference to Ubuntu 10.04 64-bit). Ubuntu 64-bit is required by Gingerbread.

If you are behind firewall, you will have to set-up firewall using the instructions in

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 repo tool:

mkdir ~/bin -p sudo apt-get install curl curl http://android.git.kernel.org/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 tool chain can be obtained from

=Downloading Release Software= Android Filesystem Sources

you can get the Android source for this release by doing: git clone git://git.omapzoom.org/platform/omapmanifest.git cd omapmanifest git reset --hard RLS27.12.1_Gingerbread export MANIFEST=`pwd` cd export YOUR_PATH=`pwd` mkdir -p 27.12.1/mydroid; cd 27.12.1/mydroid export MYDROID=`pwd` repo init -u $MANIFEST repo sync

Kernel & Driver Sources

To clone kernel source from scratch do: cd ${YOUR_PATH} mkdir kernel git clone git://git.omapzoom.org/kernel/omap.git kernel/android-2.6.35 cd kernel/android-2.6.35 git checkout a8b0d4f2f873bec3c0c47ae37896234f1f632750 If you already have kernel source cloned then just update it: cd $YOUR_PATH/kernel/android-2.6.35 git fetch origin git checkout a8b0d4f2f873bec3c0c47ae37896234f1f632750

U-Boot Sources cd ${YOUR_PATH} git clone git://git.omapzoom.org/repo/u-boot.git u-boot cd u-boot git checkout 98fa4e1b51c9a09bfea1a09be73976d78405cd3e

X-loader Sources cd ${YOUR_PATH} git clone git://git.omapzoom.org/repo/x-loader.git x-loader cd x-loader git checkout 51cf822e76be8bde9e0b86966db745faba655763

=Release Content=

This release has the below content - Kernel and Drivers tested with OMAP4 ES2.2 EMU Blaze platform and verified with Gingerbread UI - A9 source code for accelerating Video

The release has been verified with OMAP4 SGX hardware Graphics Accelerator libraries and accelerated Video codecs. Please contact TI customer representative to gain access TI proprietary packages.

=Build Instructions=

Setting up build environment
From your work directory (where your 27.12.1 folder resides): export YOUR_PATH=`pwd` export PATH=$PATH:/arm-2010q1/bin export MYDROID=${YOUR_PATH}/27.12.1/mydroid mkdir $MYDROID/logs export CROSS_COMPILE=arm-none-linux-gnueabi- export PATH=${YOUR_PATH}/u-boot/tools:${PATH}

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

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

Signing X-LOADER for EMU devices

The tool for signing x-loader is provided on TI's package. 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 ES2.x x-load.bin

ES2.x parameter changes according the SOM HS vresion you have, if you have ES HS 2.2 then use ES2.2

Building Kernel
To create kernel uImage you need to add "mkimage" directory path to your "PATH" environment variable: cd ${YOUR_PATH}/kernel/android-2.6.35 make ARCH=arm distclean make ARCH=arm android_4430_defconfig make ARCH=arm uImage 2>&1 |tee $MYDROID/logs/kernel_make.out

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

Building WLAN driver
cd $MYDROID/hardware/ti/wlan/wl1283/platforms/os/linux export KERNEL_DIR=${YOUR_PATH}/kernel/android-2.6.35 make ARCH=arm TNETW=1283

Building SoftAP/HotSpot driver
cd $MYDROID/hardware/ti/wlan/wl1283_softAP/platforms/os/linux export KERNEL_DIR=${YOUR_PATH}/kernel/android-2.6.35 make ARCH=arm TNETW=1283

Building Android Filesystem (AFS) with TI Codecs enabled
on step below use the number of cores you have available; i.e. -j4 or -j12: cd $MYDROID cp -Rfp device/ti/blaze/buildspec.mk.default buildspec.mk 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. Camera based applications need TI proprietary drivers. Please contact TI customer representative to get access to proprietary sources

Preparing Android binaries
The following binaries are required by the Blaze® board. This step will prepare a directory, called myfs, containing all necessary Android files that you must include within your SD card. cd $YOUR_PATH mkdir myfs cd myfs cp -Rfp ${YOUR_PATH}/kernel/android-2.6.35/drivers/staging/ti-st/*.ko $MYDROID/out/target/product/blaze/root cp -Rfp ${YOUR_PATH}/kernel/android-2.6.35/drivers/misc/ti-st/st_drv.ko $MYDROID/out/target/product/blaze/root cp -Rfp ${YOUR_PATH}/kernel/android-2.6.35/drivers/bluetooth/btwilink.ko $MYDROID/out/target/product/blaze/root cp -Rfp $MYDROID/out/target/product/blaze/root/*. cp -Rfp $MYDROID/out/target/product/blaze/system/. cp -Rfp $MYDROID/out/target/product/blaze/data/.

Changing default display resolution on Android

Default LCD density is now set to 240 (was 160 previously by default). If you want to come back to the previous setting to make Android UI look smaller (smaller icons, etc...), comment the following line in system/build.prop
 * 1) ro.sf.lcd_density=240

Preparing eMMC images
cd $YOUR_PATH mkdir omap4_emmc_files cp -f $MYDROID/out/host/linux-x86/bin/fastboot omap4_emmc_files cp -f $MYDROID/out/host/linux-x86/bin/mkbootimg omap4_emmc_files if [ -e ${YOUR_PATH}/27.12.1/u-boot/u-boot.bin ] ; then cp -f ${YOUR_PATH}/27.12.1/u-boot/u-boot.bin omap4_emmc_files cp -f ${YOUR_PATH}/27.12.1/x-loader/MLO omap4_emmc_files cp -f ${YOUR_PATH}/27.12.1/kernel/android-2.6.35/arch/arm/boot/zImage omap4_emmc_files else cp -f ${YOUR_PATH}/u-boot/u-boot.bin omap4_emmc_files cp -f ${YOUR_PATH}/x-loader/MLO omap4_emmc_files cp -f ${YOUR_PATH}/kernel/android-2.6.35/arch/arm/boot/zImage omap4_emmc_files fi

Creating img files:

cd ${MYDROID} find out/target/product/blaze -name *.img -exec rm -f {} \; make cp -f ${MYDROID}/out/target/product/blaze/*.img $YOUR_PATH/omap4_emmc_files This build should not take too much time and will re-generate a new *.img files with the modified init.rc file in it (If you built and installed GFX after compiling AFS, system.img and data.img will also be updated with the GFX files).

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 ./mkbootimg --kernel zImage --ramdisk ramdisk.img --base 0x80000000 --cmdline "bootargs" --board omap4 -o boot.img Please note: "bootargs" is defined below: bootargs: console=ttyO2,115200n8 rootdelay=2 mem=456M@0x80000000 mem=512M@0xA0000000 init=/init vram="10M" omapfb.vram="0:4M" androidboot.console=ttyO2

Now create cache partition: cd $YOUR_PATH/omap4_emmc_files dd if=/dev/zero of=./cache.img bs=1048510 count=128 mkfs.ext4 -F cache.img -L cache

And finally the environment file with the bootargs and bootcmd information (see bootargs section)

= Booting Kernel and Android File System from SD card = Formatting SD Card

=SD partitioning and Formatting=

Refer to  SD configuration for information regarding paritioning and formatting an SD card.

= Booting Kernel and Android File System from eMMC = Formatting eMMC

If your are going to use eMMC for the first time, you need to create the appropriate partition table and create a filesystem (format) for each partition. For this you need to load u-boot from your SD card; for this you need to change your SYS_BOOT configuration (S2-[1:3] OFF, ON, OFF). Use the u-boot.bin and the x-loader you built for this release; copy them to your "boot" partition of your SD card, turn your Blaze on and press any key on your serial terminal to stop the auto-boot process.

Now type from you serial terminal (on the u-boot prompt) 'fastboot' and board should be waiting for any fastboot command. You should see something like this: [Please note this is an older snapshot (so rev numbers you see might be different as compared to below)]

-- OMAP 4 PPA release 1.0.0 -- Reset reason = 00030181

Texas Instruments X-Loader 1.41 (Feb 25 2011 - 22:30:29) Starting OS Bootloader from EMMC ...

U-Boot 1.1.4-gbf5e493e (Feb 25 2011 - 22:30:11)

Load address: 0x80e80000 DRAM: 1024 MB Flash:  0 kB In:    serial Out:  serial Err:  serial Net:  KS8851SNL Hit any key to stop autoboot: 0 OMAP44XX SDP # fastboot Fastboot entered...

If you had SD card S2 Dip swtich cnfiguration, you can change it now to eMMC conf: SYS_BOOT configuration to boot from eMMC (S2-[1:3] ON, ON, ON)

Now connect the Blaze 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. Make sure the commands are issued as super user. You can use ./fastboot.sh which is located at $MYDROID/device/ti/blaze/boot.

cd $YOUR_PATH/omap4_emmc_files $ cp -f $MYDROID/device/ti/support-tools/boot/omap4/fastboot.sh. $ ./fastboot.sh

For your information the script does the following: cd $YOUR_PATH/omap4_emmc_files ./fastboot flash xloader ./MLO ./fastboot flash bootloader ./u-boot.bin ./fastboot reboot-bootloader sleep 5 ./fastboot oem format ./fastboot flash boot ./boot.img ./fastboot flash system ./system.img ./fastboot flash userdata ./userdata.img ./fastboot flash cache ./cache.img

Booting

Power your board up and in your terminal window you should be able to see the auto-boot process start in 3 seconds:

-- OMAP 4 PPA release 1.0.0 -- Reset reason = 00030181

Texas Instruments X-Loader 1.41 (Feb 25 2011 - 22:30:29) Starting OS Bootloader from EMMC ...

U-Boot 1.1.4-gbf5e493e (Feb 25 2011 - 22:30:11)

Load address: 0x80e80000 DRAM: 1024 MB Flash:  0 kB In:    serial Out:  serial Err:  serial Net:  KS8851SNL Hit any key to stop autoboot: 5

Boot Arguments:

setenv bootargs console=ttyO2,115200n8 rootdelay=2 mem=456M@0x80000000 mem=512M@0xA0000000 init=/init vram="10M" omapfb.vram="0:4M" androidboot.console=ttyO2

Environment size: 223/131068 bytes

To continue booting just type 'boot' and the boot process will start.

=Bootargs=

'''L27.12.1 SD card booting is not offically supported, init.rc and init.omap4430.rc need to be modified as follows:

init.rc  on post-fs # once everything is setup, no need to modify / # mount rootfs rootfs / rw remount

init.omap4430.rc on fs   #mount ext4 /dev/block/platform/mmci-omap-hs.1/by-name/system /system wait ro    #mount ext4 /dev/block/platform/mmci-omap-hs.1/by-name/userdata /data wait noatime nosuid nodev #mount ext4 /dev/block/platform/mmci-omap-hs.1/by-name/cache /cache wait noatime nosuid nodev

The sd card bootargs are present in device/ti/blaze/sd_card_env.txt file '''

eMMC bootargs given in env.txt

The eMMC bootargs are present in device/ti/blaze/env.txt file

Right after this your Blaze should start booting kernel image and loading the Android filesystem both from Blaze eMMC In order to issue commands, it is necessary to type “su -“ on the console.

=Resources=

WLAN Calibration
For optimal Wi-Fi performance calibration of Wi-Fi hardware is mandatory, follow the procedure from WLAN_Calibration