L27.INC1.11.1 OMAP4 GingerBread ES2 Release Notes

From OMAPpedia

Revision as of 17:30, 7 March 2011 by X0088926 (Talk | contribs)
Jump to: navigation, search

Contents

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: Gingerbread public project
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

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 Support Tools


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 libx11-dev libncurses5-dev 
sudo apt-get install lib32readline5-dev libstdc++6 lib32z1 lib32z1-dev ia32-libs g++-multilib
sudo apt-get install sun-java6-jdk

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

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.11.1_Gingerbread
export MANIFEST=`pwd`
cd <your work directory>
export YOUR_PATH=`pwd`
mkdir -p 27.11.1/mydroid; cd 27.11.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 d4a101815d4957438915193785cefcaf5ea8cd33

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

cd $YOUR_PATH/kernel/android-2.6.35
git fetch origin
git checkout d4a101815d4957438915193785cefcaf5ea8cd33

U-Boot Sources

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


X-loader Sources

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

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.11.1 folder resides):

export YOUR_PATH=`pwd`
export PATH=$PATH:<toolchain_parent_dir>/arm-2010q1/bin
export MYDROID=${YOUR_PATH}/27.11.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 x-load.bin

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
cd $MYDROID/hardware/ti/wlan/wl1283/platforms/os/linux
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
cd $MYDROID/hardware/ti/wlan/wl1283/platforms/os/linux
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 $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

#ro.sf.lcd_density=240

Preparing eMMC images

If you wish to boot entirely from eMMC, you will need to modify init.omap4430.rc file to mount eMMC partitions on your system and create the eMMC partition images:

cd $YOUR_PATH
mkdir omap4_emmc_files
cp -f $MYDROID/out/host/linux-x86/bin/fastboot omap4_emmc_files
cp -f $MYDROID/device/ti/blaze/gpt.emmc.bin omap4_emmc_files
cp -f $MYDROID/out/host/linux-x86/bin/mkbootimg omap4_emmc_files
if [ -e ${YOUR_PATH}/27.11.1/u-boot/u-boot.bin ] ; then 
  cp -f ${YOUR_PATH}/27.11.1/u-boot/u-boot.bin omap4_emmc_files
  cp -f ${YOUR_PATH}/27.11.1/x-loader/MLO omap4_emmc_files
  cp -f ${YOUR_PATH}/27.11.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
cp -f $MYDROID/device/ti/blaze/env.txt omap4_emmc_files

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 aaaaaa --board omap4 -o boot.img

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

You will need to format your SD for the Linux file system. Connect your SD memory card reader with memory card inserted to a USB port on your Linux Ubuntu PC. You must login as Super User.

$ su
$ fdisk -l

Match the device to the size of your memory card. Look for the /dev/*** device which matches the memory card in the card reader. Use the matching device’s letter prefix in the next command. For example if the device for memory card reader card example was: /dev/sdb1, then use only /dev/sdb in the fdisk command.

Take note of the size in bytes of your SD Card. You will need this to calculate the number of cylinders in a future step.

$ fdisk /dev/sdb  (replace sdb with the letter prefix for your device)

(Delete all partitions on the card if they exist)
Command (m for help): d
Partition number (1-4): 1
Command (m for help): d
Selected partition 2

Command (m for help): x

(Change the number of heads, sectors and cylinders on the device)
Expert command (m for help): h
Number of heads (1-256, default 255): 255
Expert command (m for help): s
Number of sectors (1-63, default 63): 63
Expert command (m for help): c
Number of cylinders (1-1048576, default 248): <You must calculate the number of cylinders for your SD card.  To do this, use the following formula:  

new_cylinders = (Size in bytes from your fdisk –l command)/8225280
Drop any fractional values and enter the whole number in this command.
Use this number all the steps that refer to the number of cylinders>

(Now return to the main menu)
Expert command (m for help): r

(Create the first partition)
Command (m for help): n
Command action
   e   extended
   p   primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-248, default 1): 1
Last cylinder or +size or +sizeM or +sizeK (1-248, default 248): +64M

If you plan to use this SD card partition for storing media your can use +1024M assuming a 2+ GB SD card.

(Create the second partition)
Command (m for help): n
Command action
   e   extended
   p   primary partition (1-4)
p
Partition number (1-4): 2
First cylinder (10-248, default 10): 10
Last cylinder or +size or +sizeM or +sizeK (124-248, default 248): <use the cylinder value you calculated earlier>  

(Change the first partition to at FAT32 partition)
Command (m for help): t
Partition number (1-4): 1
Hex code (type L to list codes): c
Changed system type of partition 1 to c (W95 FAT32 (LBA))

(Toggle the bootable flag for partition 1)
Command (m for help): a
Partition number (1-4): 1

(Print the partition table to confirm your settings)
Command (m for help): p

(Sample Output – your output may differ depending on your SD card’s size and brand)
Disk /dev/sdb: 2041 MB, 2041577472 bytes
255 heads, 63 sectors/track, 248 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1         9        72261     c  W95 FAT32 (LBA)
/dev/sdb2              10       248     1919767+    83  Linux

(Write your changes to the SD Card)	
Command (m for help): w

(You will see the following output)
The partition table has been altered!

Calling ioctl() to re-read partition table.


WARNING: If you have created or modified any DOS 6.x partitions, please see the fdisk manual page for additional information.
Syncing disks.

Format your partitions typing the following commands (logged as root@ubuntu-box):
$ mkfs.vfat -F 32 -n boot /dev/<your device’s first partition’s name – see the print output from the previous step> 
$ mkfs.ext3 -L android_fs /dev/<your device’s second partition’s name – see the print output from the previous step> 

There is a shell script that all calculations above automatically; to get it do:
$ wget http://cgit.openembedded.org/cgit.cgi/openembedded/plain/contrib/angstrom/omap3-mkcard.sh

Add execution permission:
$ chmod +x omap3-mkcard.sh

And you are ready to use it by just typing:
$sudo ./omap3-mkcard.sh <your_device (e.g. /dev/sdb)>

Copying Binaries onto SD Card

Now type the following to mount your SD Card on your Linux box (logged as root@ubuntu-box):

$ mkdir /tmp/mmc1
$ mkdir /tmp/mmc2
$ mount /dev/<your device’s first partition’s name> /tmp/mmc1
$ mount /dev/<your device’s second partition’s name> /tmp/mmc2

Load the appropriate software to the SD Card (logged as root@ubuntu-box):

$ cp $YOUR_PATH/x-loader/MLO /tmp/mmc1   (if you are using EMU or HS device, plese copy signed MLO instead)
$ cp $YOUR_PATH/u-boot/u-boot.bin /tmp/mmc1
$ cp ${YOUR_PATH}/27-GB-ENG-1/kernel/android-2.6.35/arch/arm/boot/uImage /tmp/mmc1
$ cp -Rfp $YOUR_PATH/27.10.1/myfs/* /tmp/mmc2
$ chmod –R 777 /tmp/mmc2/*
$ umount /tmp/mmc1
$ umount /tmp/mmc2

Booting
SD boot is not offically supported hence SD boot was not validated
Insert your SD card (with u-boot, x-loader and uImage loaded in FAT partition and ) into Blaze SD/MMC card slot, then plug the Blaze mini USB port to your PC and open a serial terminal (baudrate:115200, no parity, 8 bits). Power your board up and in your terminal window you should be able to see the ‘New’ u-boot prompt:

“OMAP44XX SDP #”

In your serial terminal define the bootargs and boot as mentioned in the bootarg section.</br>

Right after this your Blaze should start booting using the kernel image and loading the Android filesystem from your SD

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

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.

cd $YOUR_PATH/omap4_emmc_files
./fastboot flash xloader ./MLO
./fastboot flash bootloader ./u-boot.bin

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)
Power Cycle the Board now and restart fastboot client on board

./fastboot oem format
./fastboot flash xloader ./MLO
./fastboot flash bootloader ./u-boot.bin
./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

If you want to verify that your bootargs and bootcmd were flashed correctly as described in env.txt file, then press any key to stop the auto-boot process and type 'print':

OMAP44XX SDP # print
bootdelay=5
bootargs=console=ttyO2,115200n8 rootdelay=2 mem=456M@0x80000000 mem=512M@0xA0000000 init=/init vram="10M" omapfb.vram="0:4M"
bootcmd=mmcinit 1;mmc 1 read 0x500 0x81000000 0x500000;bootm 81000000
loadaddr=81000000
stdin=serial
stdout=serial
stderr=serial
ethact=KS8851SNL

Environment size: 223/131068 bytes

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

Bootargs

L27.11.1 SD card boot has not being validated

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

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox