BlazeTablet L27.13.1 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 for building the images. OMAP4 SGX hardware Graphics Accelerator libraries are needed to boot AFS with proper colors.

Known issues at present:
 * * Launcher application doesn't handle touchscreen events properly.
 * * Occasionally, display starts blinking after waking up from suspend state.

Environment:
 * OS Kernel: Linux® 2.6.35
 * Android:  Android Gingerbread 2.3.4
 * Toolchain: CodeSourcery compiler version Sourcery G++ Lite 2010q1-202 for ARM GNU/Linux
 * Reference hardware platform: TI OMAP4430 ES2.1 EMU BlazeTablet
 * Build Host OS: Ubuntu
 * Based on Daily Build Version: Gingerbread_DailyBuild_268

= Prebuilt binaries = You can download prebuilt binaries here:

=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: cd mkdir -p mydroid; cd mydroid export MYDROID=`pwd` repo init -u git://gitorious.org/blazetablet/omapmanifest.git -b refs/tags/BT_L27.13.1 repo sync

Kernel & Driver Sources

To clone kernel source from scratch do: cd ; export YOUR_PATH=`pwd` git clone git://gitorious.org/blazetablet/kernel.git kernel cd kernel git checkout BT_L27.13.1 If you already have kernel source cloned then just update it: cd $YOUR_PATH/kernel git remote add blazetablet git://gitorious.org/blazetablet/kernel.git git fetch -t blazetablet git checkout BT_L27.13.1

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

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

=Release Content=

This release has the below content - Kernel and Drivers tested with OMAP4 ES2.1 EMU BlazeTablet 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-P1 folder resides): export YOUR_PATH=`pwd` export PATH=$PATH:/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}

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 omap44XXtablet_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 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 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 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 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/blazetablet/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 BlazeTablet® 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/drivers/staging/ti-st/*.ko $MYDROID/out/target/product/blazetablet/root cp -Rfp ${YOUR_PATH}/kernel/drivers/bluetooth/btwilink.ko $MYDROID/out/target/product/blazetablet/root cp -Rfp ${YOUR_PATH}/kernel/drivers/media/radio/wl128x/fm_v4l2_drv.ko $MYDROID/out/target/product/blazetablet/root cp -Rfp $MYDROID/hardware/ti/wlan/wl1283/platforms/os/linux/tiwlan_drv.ko $MYDROID/out/target/product/blazetablet/system/etc/wifi/ cp -Rfp $MYDROID/hardware/ti/wlan/wl1283_softAP/platforms/os/linux/tiap_drv.ko $MYDROID/out/target/product/blazetablet/system/etc/wifi/softap/ cp -Rfp $MYDROID/out/target/product/blazetablet/root/*. cp -Rfp $MYDROID/out/target/product/blazetablet/system/. cp -Rfp $MYDROID/out/target/product/blazetablet/data/.

For WLAN, you will also need to get firmware.bin and copy it over $MYDROID/out/target/product/blazetablet/system/etc/wifi. Please contact TI customer representative to gain access to corresponding TI proprietary packages.

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

It is recommended to remove the "critical" setting when the syslink_daemon for ducati is booting. To do this you will need to edit init.omap4430.rc for eMMC boot or mmc-init.omap4430.rc for SD boot as indicated: service baseimage /system/bin/syslink_daemon.out -f /data/base_image_sys_m3.xem3 /data/base_image_app_m3.xem3 critical (Remove this line) user media group media
 * 1) Load IVA firmware

So it will be: service baseimage /system/bin/syslink_daemon.out -f /data/base_image_sys_m3.xem3 /data/base_image_app_m3.xem3 user media group media
 * 1) Load IVA firmware

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/blazetablet/gpt.emmc.bin omap4_emmc_files cp -f $MYDROID/out/host/linux-x86/bin/mkbootimg omap4_emmc_files if [ -e ${YOUR_PATH}/27.12.1-P1/u-boot/u-boot.bin ] ; then cp -f ${YOUR_PATH}/27.12.1-P1/u-boot/u-boot.bin omap4_emmc_files cp -f ${YOUR_PATH}/27.12.1-P1/x-loader/MLO omap4_emmc_files cp -f ${YOUR_PATH}/27.12.1-P1/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/arch/arm/boot/zImage omap4_emmc_files fi cp -f $MYDROID/device/ti/blazetablet/env.txt omap4_emmc_files

Creating img files:

cd ${MYDROID} find out/target/product/blazetablet -name *.img -exec rm -f {} \; make cp -f ${MYDROID}/out/target/product/blazetablet/*.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" are defined below (so use in place of bootargs above - in the quotes), bootargs: console=ttyO2,115200n8 rootdelay=2 mem=456M@0x80000000 mem=512M@0xA0000000 init=/init vram=10M omapfb.vram=0:6M 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

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): 

(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): 

(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/ $ mkfs.ext3 -L android_fs /dev/

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 

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/ /tmp/mmc1 $ mount /dev/ /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}/kernel/arch/arm/boot/uImage /tmp/mmc1 $ cp -Rfp $YOUR_PATH/myfs/* /tmp/mmc2 $ chmod -R 777 /tmp/mmc2/* $ umount /tmp/mmc1 $ umount /tmp/mmc2

Booting SD boot is not offically supported Insert your SD card (with u-boot, x-loader and uImage loaded in FAT partition and ) into BlazeTablet SD/MMC card slot, then plug the BlazeTablet 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.

Right after this your BlazeTablet 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 (S1-[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 BlazeTablet 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 (version 00000021) PPA release 1.0.5 -- Device type: EMU, ONLY PUBLIC DEBUG ON                                        Reset reason = 00030181 Texas Instruments X-Loader 1.41 (Apr 4 2011 - 11:20:38) mmc read: Invalid size Starting OS Bootloader from MMC/SD1 ... U-Boot 1.1.4-g09d770e2 (Apr 4 2011 - 11:19:30)

Load address: 0x80e80000 DRAM: 1024 MB                                                                                                                      Flash:  0 kB                                                                                                                        Using default environment In:   serial Out:  serial Err:  serial efi partition table: efi partition table not found Net:  KS8851SNL Hit any key to stop autoboot: 0 OMAP44XX SDP # fastboot Blaze Tablet Board: 0100APPS750-2143 Device Serial Number: 1D62000300000001 Fastboot entered...

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

Now connect the BlazeTablet 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/blazetablet/boot. This is for ES2.2 devices.

cd $YOUR_PATH/omap4_emmc_files cp -f $MYDROID/device/ti/blazetablet/boot/fastboot.sh $YOUR_PATH/omap4_emmc_files sudo ./fastboot.sh --emu  for gp run: sudo ./fastboot.sh --gp

NOTES: Since you are going to execute fastboot.sh from $YOUR_PATH/omap4_emmc_files, you need to make some adjustments to the script before execution.

a) Modify the paths of FASTBOOT and PRODUCT_OUT in the script, like: export FASTBOOT=${FASTBOOT-"./fastboot"} export PRODUCT_OUT=${PRODUCT_OUT-"./"}

b) Make sure the MLO located in $YOUR_PATH/omap4_emmc_files corresponds to your board (being GP or EMU). In the $YOUR_PATH/omap4_emmc_files folder, rename MLO as: %mv MLO MLO_es2.2_emu or %mv MLO MLO_es2.2_gp

c) Modify the paths of MLO and u-boot for "Flashing bootloader.." in the script, like: echo "Flashing bootloader....." $FASTBOOT flash xloader 	./$MLO $FASTBOOT flash bootloader 	./u-boot.bin

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 (version 00000021) PPA release 1.0.5 -- Device type: EMU, ONLY PUBLIC DEBUG ON Reset reason = 00030181

Texas Instruments X-Loader 1.41 (Apr 4 2011 - 11:20:38) Starting OS Bootloader from EMMC ...

U-Boot 1.1.4-g09d770e2 (Apr 4 2011 - 11:19:30)

Load address: 0x80e80000 DRAM: 1024 MB Flash:  0 kB Using default environment

In:   serial Out:  serial Err:  serial

efi partition table: 256    128K xloader 512    256K bootloader 2048      8M recovery 18432      8M boot 34816    512M system 1083392    256M cache 1607680    512M userdata 2656256    463M media Net:  KS8851SNL Hit any key to stop autoboot: 3 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.13.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

Note that parameter mem=456M@0x80000000 mem=512M@0xA0000000 should be used in the bootargs

L27.13.1 Bootargs for SD card boot

setenv bootargs androidboot.console=ttyO2 console=ttyO2,115200n8 mem=456M@0x80000000 mem=512M@0xA0000000 root=/dev/mmcblk1p2 rw rootdelay=2 init=/init vram="10M" omapfb.vram="0:6M" setenv bootcmd 'mmcinit 0;fatload mmc 0 0x80000000 uImage; bootm 0x80000000' saveenv boot

eMMC bootargs given in env.txt

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

Right after this your BlazeTablet should start booting kernel image and loading the Android filesystem both from BlazeTablet 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

WLAN Firmware files
The firmware files needed for Wi-Fi can be taken from here

The Wi-Fi and softAP/HotSpot firmware files go to following locations on file system  Wi-Fi Firmware (firmware.bin) --> /system/etc/wifi/firmware.bin  SoftAP/HotSpot Firmware (firmware_ap.bin) --> /system/etc/wifi/softap/firmware_ap.bin 

L27.INC1.12.1-P1 OMAP4 GingerBread ES2 Release Notes
http://www.omapedia.org/wiki/L27.INC1.12.1-P1_OMAP4_GingerBread_ES2_Release_Notes