From OMAPpedia

Contents 1 Introduction 2 Release Content 3 Build and Installation Instructions 4 Booting Kernel and Android® File System from SD card 5 New in this Release 6 Limitations/Known Issues 7 Use Case Test Results 8 Resources

[edit] Introduction

This release has been developed and tested in the following environment.

OS Kernel: Linux® 2.6.32.
Android™ Froyo public project.
Toolchain: CodeSourcery compiler version 2009q1.
Manifest: 27.6.2_Manifest.
U-boot version: 255e28d6ac361b7c3c14ee48b49581db911ceca4.
X-loader version: e29f59769182e8602f0bfc38ff0d872a2d665dd9.
kernel version: c012c72d887f720609d341a03661da10c87d6445.

[edit] Release Content

The release refers to the source code in git trees and the binary packages are distributed in different projects. The next section on how to build will help pull them into the correct directories to integrate the software system. This release also contains WLAN (1271/1283) and Graphics packages. Details are given below in "Build and Installation Instructions"

Supported MM Use Cases(ARM side) in the Community Release
JPEG Dec
MP3 Dec
AAC Dec

Documentation
OMAPpedia is an excellent source for details on the various components. There is a project listing in the main page on the various components. You may also go and check the following: Refer to BSP release notes at

   https://gforge.ti.com/gf/project/omapandroid/docman/?subdir=11

Power Management materials PM is enabled by default in the kernel, but for enabling any of the features we need to use some sysfs entries from user space:

   http://omappedia.org/wiki/Linux_OMAP_Kernel_Main
   http://elinux.org/OMAP_Power_Management

Source code
Release Manifest for open code source. Release Tag - RLS27.6.2_Froyo.

IMPORTANT: kernel source, u-boot and x-loader has been removed from the manifest so it is not included in this manifest and thus you have to clone it separately.

Please note: for U-Boot and X-Loader "omap4_dev" branch was used.

[edit] Build and Installation Instructions

Building the Bootloader, Kernel, WLAN driver(1283) and Android File System
The details are given at: http://www.omapedia.org/wiki/L27.INC1.6.2_OMAP4_Froyo_ES2_Release_Notes#Build_Instructions

Pre-built binaries from this release can be obtained from Package.

Please note there are two pre-built MLO - one for EMU board and other for GP board. Default MLO is for EMU devices. gp_MLO is for (GP) device. Please rename gp_MLO to MLO before using it.

Please note this release is tested with Android codecs and have followed instructions to enable them while building.

If you have a COM6 chip (127x WLAN), please follow the steps mentioned below for following build the WLAN driver. Please note it requires a patch to be applied on the Android File System. Hence, it will be required to build the AFS after applying the patch.

Building WLAN driver(1271)
Download the WLAN 1271 Connectivity Package.
It has the patch, firmware binary and BT/FM init scripts.

• 0001-WL1271-Support-for-WL1271-on-blaze-for-L27.6.patch must be applied to WiLink6 driver in order to load the driver on Blaze + COM6 setup.
  Apply the patch:
  $cd $MYDROID
  $cd hardware/ti/wlan/
  To check whether the WiLink6 driver is latest, check the git log for following commit ID: c7155066d87dab9844d239ab00f82c3df26b2c75
  $git apply --stat --check -v //to check whether old patch can be applied or not
  $git apply -v //to actually apply patch
  
• Building WLAN Driver
  Update following environment variables in wl_env.bash file located at
  $MYDROID/hardware/ti/wlan/wl1271/platforms/os/linux/ .
  export CROSS_COMPILE=arm-none-linux-gnueabi-
  export ARCH=arm
  export HOST_PLATFORM=blaze
  export KERNEL_DIR=
  $cd $MYDROID/hardware/ti/wlan/wl1271/platforms/os/linux/
  $make
  We will get tiwlan_drv.ko in $MYDROID/hardware/ti/wlan/wl1271/platforms/os/linux/
  
• Configuration for WLAN
  Make sure the file vendor device $MYDROID/ti/blaze/BoardConfig.mk has all wifi related definitions:
  
  1. Wifi
     
  BOARD_WPA_SUPPLICANT_DRIVER := CUSTOM
  BOARD_WLAN_DEVICE  := wl1271
  WPA_SUPPLICANT_VERSION  := VER_0_6_X
  WIFI_DRIVER_MODULE_PATH  := "/system/etc/wifi/tiwlan_drv.ko"
  WIFI_DRIVER_MODULE_NAME  := "tiwlan_drv"
  WIFI_FIRMWARE_LOADER  := "wlan_loader"
  Make sure the system property file $MYDROID/device/ti/blaze/system.prop has definition for wifi interface
  wifi.interface=tiwlan0
  
  Installing 1271/1283 WLAN firmware from the package
  Place the file tiwlan_drv.ko build from previous step to system/etc/wifi. Go to platform/os/linux folder and copy the required files to file system:
  $ cd $MYDROID/hardware/ti/wlan/(wl1283 or wl1271)/platforms/os/linux
  $ cp tiwlan_drv.ko $MYDROID/out/target/product/blaze/system/etc/wifi
  Another file, firmware.bin is also required but this must be obtained from the package from the below link.
  Please download one of the package - depending on what WLAN hardware chip you are using
  WLAN 1283 Connectivity Package
  WLAN 1271 Connectivity Package
  $ chmod 777 [WLAN Package name]
  $./[WLAN Package Name]
  $ cd $MYDROID/out/target/product/blaze/system/etc/wifi
  $ cp $YOUR_PATH/WLAN_firmware/firmware.bin .
  $ chmod 777 $MYDROID/out/target/product/blaze/system/etc/wifi/firmware.bin
  
  Installing GFX binaries from the package
  Package can be obtained from the GFX link
  $ chmod 777 GFX package name
  $ ./GFX package name
  Accept the terms and install it at your filesystem location e.g. YOUR_PATH/myfs
  
  Installing Ducati binaries from the package
  Package can be obtained from the Ducati Link
  $ chmod 777 Froyo_L27.6.2_Ducati_Binaries-1.0-Linux-x86-Install
  $ ./Froyo_L27.6.2_Ducati_Binaries-1.0-Linux-x86-Install
  Accept the terms and install it at your filesystem location e.g. YOUR_PATH/myfs (Please notice that files go to myfs/data folder).
  

  [edit] Booting Kernel and Android® File System from SD card

  The instruction on formatting the SD card and copying the environment can be found at http://omappedia.org/wiki/Android_SD_Configuration http://omappedia.org/wiki/Flashing_Android#Flashing_to_SD

  Please note this release has been tested on OMAP4430 ES2 EMU device on Blaze platform and will requires a signed x-loader. Please contact TI customer representative to get access to the signing tool.

  [edit] New in this Release

  • This release was validated using "Froyo" public branch.
  • This release uses Android codecs.
  • This release is on 2.6.32 Kernel.
  • Dynamically switching from speakers/headphones is now working.
  • Audio files can be played using the default configuration on Android Filesystem
  • WLAN packages are part of this release.
  • Graphic binary package is part of this release.
  • Ducati binary package (which enables video codec[MPEG4 decode/H264 decode]) is part of this release.

    [edit] Limitations/Known Issues

    IMPORTANT:

    • When Froyo image boots up For first time there will be a window asking, Complete action using: Com.android.provision.DeFault.Activity Com.android.sdksetup.DeFault.Activity . Choose the first one - Com.android.provision.DeFault.Activity
    • UI experience is faster as compared to eclair
    • You will have to press F1 key everytime before unlocking the UI
    • The board overheats while it is connected to the power supply.
    • To play video codecs, ducati binary is required in the filesystem.
    • Camera preview/functionality is not supported on this release due to licensing restrictions. Whenever the OMAP4 Camera app is opened the system prompts:Sorry! The application OMAP4 Camera (process com.ti.omap4.android.camera) has stopped unexpectedly. Please try again Force close

      [edit] Use Case Test Results

      Test Case ID	Test Case Name	Validation Criteria	Sample file	Test Result	Comments
      1	Boot from SD	Android boots from SD card	N/A	Pass	Android boots up and the Home screen is displayed on the LCD
      2	WLAN	Scan wireless network and connect	NA	Pass	Could found wireless network and connect to it. *** This test cases should be run using WLAN Binaries.
      3	WLAN - Browse webpage	Open browser and connect to and other webpages	NA	Pass	Could browse web pages on internet. *** This test cases should be run using WLAN Binaries.
      4	Audio Playback - AAC	Play - Audio shall play without audible glitches.	A_000385_AAC_48kHz_256kbps_stereo.mp4 or A_000341_eAacplus_48khz_STEREO_32kbps_track1.m4a	Pass	Audio plays without audible glitches.
      5	Audio Playback - MP3	Play - Audio shall play without audible glitches.	A_000209_DaftPunk_Discovery_02_Aerodynamic.mp3	Pass	Audio plays without audible glitches.
      6	A/V Playback - MPEG4	Audio can be mute; video can be distorted until play is resumed.	AV_000427_MPEG4_Visual_Simple_Profile_at_level_6_WVGA_ Landscape_854_480_30_fps_8_Mbps_eAACplus_48_kHz_48_kbps_stereo.mp4	Pass	Video is heard and rendered without distortion. *** This test cases should be run using Ducati Binaries.
      7	A/V Playback - H264	Play - Shall play synchronized audio/video without audible/visible distortion.	AV_000257_H264_4M_D1NTSC_30fp_PROFILE_3_AAC_48khz_128kbps.mp4	Pass	Video is heard and rendered without distortion. *** This test cases should be run using Ducati Binaries.
      8	Bluetooth	Pass if pairing is succesful.	NA	Pass	BT device is paired without issues. *** This test cases should be run using WLAN Binaries.
      9	Bluetooth File Transfer	Sent and received file should be uncurrupted.	N/A.	Pass.	Files sent and received OK. *** This test cases should be run using WLAN Binaries.
      10	GFX DDK OGLES1Test1	GFX should be displayed properly.	NA	Pass.	GFX displayed OK. *** This test cases should be run using GFX Binaries.
      11	GFX DDK OGLES2Test1	GFX should be displayed properly.	NA	Pass.	GFX displayed OK. *** This test cases should be run using GFX Binaries.

      ---

      [edit] Resources

      OMAPWorld.com and OMAPpedia.org may be good starting places.

      IRC Chat - #linux-omap
      Googlegroups -
      

      Mailing List - OMAPAndroid Discussion list
  Retrieved from "https://omappedia.com/wiki/L27.INC1.6.2_OMAP4_Froyo_ES2_Community_Release_Notes"