L27.INC1.8.2 OMAP4 Froyo ES2 Community Release Notes

From OMAPpedia

(Difference between revisions)
Jump to: navigation, search
m (Build and Installation Instructions)
m (Build and Installation Instructions)
 
(7 intermediate revisions not shown)
Line 42: Line 42:
Please note the tool chain has changed for this release. Details are present in the above link
Please note the tool chain has changed for this release. Details are present in the above link
-
Pre-built binaries from this release can be obtained from [https://gforge.ti.com/gf/project/omapandroid/frs/?action=FrsReleaseBrowse&frs_package_id=172 Package].
+
Pre-built binaries from this release can be obtained from [https://gforge.ti.com/gf/project/omapandroid/frs/?action=FrsReleaseBrowse&frs_package_id=178 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 (<span style="color:#ff0000">GP</span>) device. Please rename gp_MLO to MLO before using it.'''
'''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 (<span style="color:#ff0000">GP</span>) device. Please rename gp_MLO to MLO before using it.'''
Line 51: Line 51:
'''Building WLAN driver(1271)'''<br>
'''Building WLAN driver(1271)'''<br>
-
Download the [https://gforge.ti.com/gf/project/wilink_drivers/frs/?action=FrsReleaseBrowse&frs_package_id=173 WLAN 1271 Connectivity Package]. <br>
+
Download the [https://gforge.ti.com/gf/project/wilink_drivers/frs/?action=FrsReleaseBrowse&frs_package_id=179 WLAN 1271 Connectivity Package]. <br>
It has the patch, firmware binary and BT/FM init scripts.
It has the patch, firmware binary and BT/FM init scripts.
-
<li>0001-WL1271-Support-for-WL1271-on-blaze-for-L27.8.patch must be applied to WiLink6 driver in order to load the driver on Blaze + COM6 setup.<br>
+
<li>0001-Patch-for-WL1271-driver-for-Blaze-COM6-and-Pandroid.patch / 0001-omap_pm_set_min_mpu_freq-is-not-defined-in-p-android.patch must be applied to WiLink6 driver in order to load the driver on Blaze + COM6 setup.<br>
Apply the patch:<br>
Apply the patch:<br>
Line 60: Line 60:
To check whether the WiLink6 driver is latest, check the git log for following commit ID:
To check whether the WiLink6 driver is latest, check the git log for following commit ID:
-
bdce65c9998b69a6b4f0682865515f72faec5266.<br>
+
c7e399e2804729c5d271ce58a9f299a2fa2a0631.<br>
 +
 
 +
$git apply --stat --check -v <Path to patch 0001-Patch-for-WL1271-driver-for-Blaze-COM6-and-Pandroid.patch > //to check whether old patch can be applied or not<br>
 +
$git apply -v <Path to patch 0001-Patch-for-WL1271-driver-for-Blaze-COM6-and-Pandroid.patch > //to actually apply patch<br>
 +
$git apply --stat --check -v <Path to patch 0001-omap_pm_set_min_mpu_freq-is-not-defined-in-p-android.patch > //to check whether old patch can be applied or not<br>
 +
$git apply -v <Path to patch 0001-omap_pm_set_min_mpu_freq-is-not-defined-in-p-android.patch > //to actually apply patch<br>
-
$git apply --stat --check -v <Path to patch 0001-WL1271-Support-for-WL1271-on-blaze-for-L27.8.patch > //to check whether old patch can be applied or not<br>
 
-
$git apply -v <Path to patch 0001-WL1271-Support-for-WL1271-on-blaze-for-L27.8.patch > //to actually apply patch<br>
 
<li>Building WLAN Driver<br>
<li>Building WLAN Driver<br>
Line 98: Line 101:
Another file, firmware.bin is also required but this must be obtained from the package  from the below link. <br>
Another file, firmware.bin is also required but this must be obtained from the package  from the below link. <br>
Please download one of the package - depending on what WLAN hardware chip you are using<br>
Please download one of the package - depending on what WLAN hardware chip you are using<br>
-
[https://gforge.ti.com/gf/project/wilink_drivers/frs/?action=FrsReleaseBrowse&frs_package_id=174 WLAN 1283 Connectivity Package]<br>
+
[https://gforge.ti.com/gf/project/wilink_drivers/frs/?action=FrsReleaseBrowse&frs_package_id=180 WLAN 1283 Connectivity Package]<br>
-
[https://gforge.ti.com/gf/project/wilink_drivers/frs/?action=FrsReleaseBrowse&frs_package_id=173 WLAN 1271 Connectivity Package]<br>
+
[https://gforge.ti.com/gf/project/wilink_drivers/frs/?action=FrsReleaseBrowse&frs_package_id=179 WLAN 1271 Connectivity Package]<br>
$ chmod 777 Froyo_L27.8.2_Connectivity_1283-1.0-Linux-x86-Install<br>
$ chmod 777 Froyo_L27.8.2_Connectivity_1283-1.0-Linux-x86-Install<br>
Line 109: Line 112:
'''Installing GFX binaries from the package'''<br>
'''Installing GFX binaries from the package'''<br>
-
Package can be obtained from the [https://gforge.ti.com/gf/project/omapgraphics/frs/?action=FrsReleaseBrowse&frs_package_id=175 GFX link]<br>
+
Package can be obtained from the [https://gforge.ti.com/gf/project/omapgraphics/frs/?action=FrsReleaseBrowse&frs_package_id=181 GFX link]<br>
$ chmod 777 Froyo_L27.8.2_Graphics-1.0-Linux-x86-Install<br>
$ chmod 777 Froyo_L27.8.2_Graphics-1.0-Linux-x86-Install<br>
$ ./Froyo_L27.8.2_Graphics-1.0-Linux-x86-Install<br>
$ ./Froyo_L27.8.2_Graphics-1.0-Linux-x86-Install<br>
Line 116: Line 119:
'''Installing Ducati binaries from the package'''<br>
'''Installing Ducati binaries from the package'''<br>
-
Package can be obtained from the [https://gforge.ti.com/gf/project/openmax/frs/?action=FrsReleaseBrowse&frs_package_id=170 Ducati Link]<br>
+
Package can be obtained from the [https://gforge.ti.com/gf/project/openmax/frs/?action=FrsReleaseBrowse&frs_package_id=182 Ducati Link]<br>
$ chmod 777 Froyo_L27.8.2_Ducati_Binaries-1.0-Linux-x86-Install<br>
$ chmod 777 Froyo_L27.8.2_Ducati_Binaries-1.0-Linux-x86-Install<br>
$ ./Froyo_L27.8.2_Ducati_Binaries-1.0-Linux-x86-Install<br>
$ ./Froyo_L27.8.2_Ducati_Binaries-1.0-Linux-x86-Install<br>
Line 145: Line 148:
<span style="color:#ff0000">'''IMPORTANT: '''</span>  
<span style="color:#ff0000">'''IMPORTANT: '''</span>  
   <ul>
   <ul>
 +
  <li><span style="color:#ff0000">'''GFX package MUST be installed in order to load GUI in this release. '''Package can be obtained from the [https://gforge.ti.com/gf/project/omapgraphics/frs/?action=FrsReleaseBrowse&frs_package_id=181 GFX link]<br></span>
   <li> When Froyo image boots up For first time there will be a window asking,  
   <li> When Froyo image boots up For first time there will be a window asking,  

Latest revision as of 18:13, 20 December 2010

Contents

[edit] Introduction

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

OS Kernel: Linux® 2.6.35.
Android™ Froyo public project.
Toolchain: CodeSourcery compiler version 2010q1.
Manifest: 27.8.2_Manifest.
U-boot version: 025fefdbfb6234fe986ac59e7cde5e838981d00a.
X-loader version: 7e658a49642dde495318d4bf8a43da2c9fa47718.
kernel version: e4d2c285d4943b744359dfcf3ad494e9f2f0c35b.

[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.8.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.8.2_OMAP4_Froyo_ES2_Release_Notes#Build_Instructions Please note the tool chain has changed for this release. Details are present in the above link

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.

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-Patch-for-WL1271-driver-for-Blaze-COM6-and-Pandroid.patch / 0001-omap_pm_set_min_mpu_freq-is-not-defined-in-p-android.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: c7e399e2804729c5d271ce58a9f299a2fa2a0631.
    $git apply --stat --check -v <Path to patch 0001-Patch-for-WL1271-driver-for-Blaze-COM6-and-Pandroid.patch > //to check whether old patch can be applied or not
    $git apply -v <Path to patch 0001-Patch-for-WL1271-driver-for-Blaze-COM6-and-Pandroid.patch > //to actually apply patch
    $git apply --stat --check -v <Path to patch 0001-omap_pm_set_min_mpu_freq-is-not-defined-in-p-android.patch > //to check whether old patch can be applied or not
    $git apply -v <Path to patch 0001-omap_pm_set_min_mpu_freq-is-not-defined-in-p-android.patch > //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=<path to the kernel folder which was built above>
    $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 Froyo_L27.8.2_Connectivity_1283-1.0-Linux-x86-Install
    $./Froyo_L27.8.2_Connectivity_1283-1.0-Linux-x86-Install
    $ 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 Froyo_L27.8.2_Graphics-1.0-Linux-x86-Install
    $ ./Froyo_L27.8.2_Graphics-1.0-Linux-x86-Install
    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.8.2_Ducati_Binaries-1.0-Linux-x86-Install
    $ ./Froyo_L27.8.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.35 Kernel.
    • Dynamically switching from speakers/headphones is now working.
    • Audio files can be played using the default configuration on Android Filesystem
    • New WLAN packages are created for this release.
    • New Graphic binary package is part of this release.
    • Toolchain has changed for this release. Please refer build instructions to get the details.

      [edit] Limitations/Known Issues

      IMPORTANT:

      • GFX package MUST be installed in order to load GUI in this release. Package can be obtained from the GFX link
      • 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.
      • 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 google.com 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 - OMAPDiscuss

        Mailing List - OMAPAndroid Discussion list
  • Personal tools
    Namespaces
    Variants
    Actions
    Navigation
    Toolbox