L25.INC3.4P3 Community Release Notes

From OMAPpedia

(Difference between revisions)
Jump to: navigation, search
m (Booting with zoom2 (OMAP 3430):)
m (New in this Release)
Line 123: Line 123:
----
----
===<span style="color:#ff0000">'''NO Zoom2 (OMAP 3430) for this L25.INC3.4P3 Release'''</span> ===
===<span style="color:#ff0000">'''NO Zoom2 (OMAP 3430) for this L25.INC3.4P3 Release'''</span> ===
-
 
-
= New in this Release =
 
-
<ul>
 
-
<li>This release was validated using "Éclair" public branch
 
-
<li>This release is on 2.6.29 Kernel.
 
-
<li>PV OpenCore® 2.02 and patches
 
-
<li>BSP
 
-
  <ul>
 
-
  <li>MUSB DMA optimizations.
 
-
  <li>MUSB and MMC PM Constraints update.
 
-
  <li>EHCI PHY mode support.
 
-
  <li>Support for pre-multiplied alpha blending.
 
-
  <li>OFF mode fixed.
 
-
  <li>TV out support.
 
-
  <li>Remove the console dbg msgs from DISPC.
 
-
  <li>Fix c-state constraint for HDMI GFX_FIFO_UNDERFLOW.
 
-
  <li>Improving throughput using the constraints framework.
 
-
  <li>Disable OTG AUTOIDLE feature to allow OMAP3630 to hit OFF mode.
 
-
  <li>Update DMA buffer address between DMA/PIO transfers.
 
-
  </ul>
 
-
 
-
<li>Image/Video
 
-
  <ul>
 
-
  <li>Support for Audio “crackle” sounds are heard in addition to the recorded sound for first 2-3 seconds of the recorded clip. During this time video is somewhat jumpy.
 
-
  <li>Fixed: AV sync fails (delay of close to 1 sec is there, first audio is played followed by video).
 
-
  <li>Fixed: Recorded fps is less than the set value (eg: records at 27fps for 30fps setting, 13 for 15fps).
 
-
  <li>Robustness and Clean ups in Camera subsystem components.
 
-
  <li>DSP Socket Nodes migration 3.11.
 
-
  <li>Review comments defect fixes in OMX JPEG and CameraHAL.
 
-
  <li>128 Byte alignment.
 
-
  <li>CameraHAL component test app, Added 43 new test cases as part of Unit test suite on for CameraHAL. "pal" and "ntsc" that can be used to tv out.
 
-
  <li>omapfb.vram=<fbnum>:<size>[@<physaddr>][,...]
 
-
VRAM allocated for a framebuffer. Normally omapfb allocates vram depending on the display size. With this you can manually allocate more or define the physical address of each framebuffer. For example, "1:4M" to allocate 4M for fb1.
 
-
  <li>omapfb.debug=<y|n>
 
-
Enable debug printing. You have to have OMAPFB debug support enabled in kernel config.
 
-
  <li>omapfb.test=<y|n>
 
-
Draw test pattern to framebuffer whenever framebuffer settings change. You need to have OMAPFB debug support enabled in kernel config.
 
-
  <li>omapfb.vrfb=<y|n>
 
-
Use VRFB rotation for all framebuffer.
 
-
  <li>omapfb.rotate=<angle>
 
-
Default rotation applied to all framebuffer:
 
-
0 - 0 degree rotation.
 
-
1 - 90 degree rotation.
 
-
2 - 180 degree rotation.
 
-
3 - 270 degree rotation.
 
-
  <li>Refer to [https://gforge.ti.com/gf/project/omapandroid/docman/?subdir=22 OMX release notes]
 
-
  </ul>
 
-
 
-
<li>Bluetooth
 
-
  <ul>
 
-
  <li>FM driver ST interface support added and FM works without Bluetooth being enabled from UI.
 
-
  <li>Enabled OPP support from Android and now file transfer is possible from Android UI (From Gallery)/BlueFTP.
 
-
  <li>FM stack version M5.03.
 
-
  <li>UART2 DMA enabled.
 
-
  <li>BT-FM service pack version 2.27.
 
-
  <li>Supported Features:
 
-
      <ul>
 
-
  <li>BT Scan, pair, connects.
 
-
      <li>A2DP streaming to BT Stereo headset
 
-
      <li>Audio streaming over HFP to BT mono/stereo headset
 
-
      <li>AVRCP control of Music player
 
-
      <li>FM Transmit
 
-
      <li>FM Radio
 
-
      <li>BT PM with OMAP PM
 
-
      <li>File tranfer using BlueFTP application.
 
-
  </ul>
 
-
  </ul>
 
-
 
-
<li>Wi-Fi
 
-
  <ul>
 
-
  <li>Upgraded wilink_6_1 version to M5.04 (WiLink_Driver_6.1.0.0.130)
 
-
  <li>Random MAC address for wifi interface.
 
-
  <li>Following WLAN features are supported (through UI and WLAN TI CLI Utility)
 
-
      <ul>
 
-
      <li>Scanning for AP's and listing the devices with SSID
 
-
      <li>Connecting to the available AP's
 
-
      <li>Web browsing
 
-
      <li>WLAN security (WEP40, WEP128, WPA, WPA2)
 
-
      <li>Roaming
 
-
      <li>Ad-hoc networking
 
-
      <li>QoS
 
-
      <li>Host power management
 
-
      <li>BT & WLAN Coexistence
 
-
      </ul>
 
-
  </ul>
 
-
 
-
<li>PPM SmartReflex&#0153;
 
-
      <ul>
 
-
      <li>SmartReflex&#0153; is an adaptive voltage scaling technology, in which the supply voltage can be adapted to the silicon performance either from the static sense (e.g. adapted to the manufacturing process of a given device) or the dynamic sense (e.g. adapted to the temperature induced current performance of the device). This allows dynamically adapting the VDD1 & VDD2 voltages to the silicon characteristics and temperature to minimize active power consumption. It can operate under manual or automatic mode to suit PM SW needs. Though it is recommended to run the system at specified voltage & frequency as per selected OPP, the optimal voltage for a given frequency varies with the manufacturing process of the device and temperature. Thus, the optimal voltage for a given frequency is different for every silicon chip based on its silicon characteristics (hot vs. cold samples) and current temperature.
 
-
      <ul>
 
-
      <br>
 
-
<u>Note:</u> SmartReflex&#0153; does tuning around the recommended OPP voltage and never changes the OPP
 
-
      <br><br>
 
-
To enable/disable SmartReflex&#1053; for VDD1 & VDD2, use the following commands, respectively:
 
-
      <br>
 
-
'''# echo –n <value> > /sys/power/sr_vdd1_autocomp'''
 
-
      <br>
 
-
The value <value> can be <br>
 
-
0 – To disable <br>
 
-
1 – To enable <br>&nbsp;<br>
 
-
 
-
'''# echo –n <value> > /sys/power/sr_vdd2_autocomp'''
 
-
      <br>
 
-
The value <value> can be <br>
 
-
0 – To disable <br>
 
-
1 – To enable <br>
 
-
      </ul>
 
-
      </ul>
 
-
 
-
<hr>
 
='''Limitations/Known Issues'''=
='''Limitations/Known Issues'''=

Revision as of 19:33, 14 December 2010

Contents

Introduction

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

OS Kernel: Linux® 2.6.32.
AndroidTM Froyo 2.2.1 public project.
Toolchain: Android Froyo Toolchain : arm-eabi-4.4.0 (Using GCC4.4.0).
Manifest: 25.INC3.4P3_Manifest.
U-boot Version: fbe4cef852de5a39412234b4acd47a830d0282a2.
X-loader version: eb8b047c29a2027fbdd841cd1289fa27ddb22d72.
Kernel version: 0d27f8409fd277b66d46e16ffadb0ec9bf26eb8a.

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.

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

Refer to Bridge release notes at

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

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

Refer to OMX release notes at https://gforge.ti.com/gf/project/omapandroid/docman/?subdir=22

Source code
Release Manifest for open code source. Release Tag - RLS25.INC3.4P3DB237rc0

Follow these instructions in order to download RLS25.INC3.4P3DB237rc0 manifest:

mkdir RLS25.INC3.4P3DB237rc0
cd RLS25.INC3.4P3DB237rc0
repo init -u git://git.omapzoom.org/platform/omapmanifest.git -b eclair
cd .repo/manifests
git reset --hard RLS25.INC3.4P3DB237rc0
cd ../..
repo sync

Kernel cloning/building

git clone git://git.omapzoom.org/kernel/omap.git
cd omap/
git checkout --track -b p-android-omap-2.6.32 origin/p-android-omap-2.6.32
git checkout -b L25.I3.4P3 android-2.6.32-2.2-Inc3-4P3
make ARCH=arm CROSS_COMPILE=arm-eabi- android_zoom3_defconfig
make ARCH=arm CROSS_COMPILE=arm-eabi- uImage

U-Boot cloning/building

git clone  git://git.omapzoom.org/repo/u-boot.git
cd u-boot/
git checkout -b L25.I3.4P3 fbe4cef852de5a39412234b4acd47a830d0282a2
make ARCH=arm CROSS_COMPILE=arm-eabi- omap3630zoom3_config
make ARCH=arm CROSS_COMPILE=arm-eabi-

X-Loader cloning/building

git clone git://git.omapzoom.org/repo/x-loader.git
cd x-loader/
git checkout -b L25.I3.4P3 eb8b047c29a2027fbdd841cd1289fa27ddb22d72
make ARCH=arm CROSS_COMPILE=arm-eabi- omap3630zoom3_config
make ARCH=arm CROSS_COMPILE=arm-eabi- ift

Other Binary packages
DSP Binary Package - binaries Connectivity Package - project Graphics Package - Please refer to Build/Install instructions on details

Build and Installation Instructions

Building the Bootloader, Kernel and Android File System

The final Release RC tag from L25x manifest for the source should be used. Perform a clean build of u-boot, x-loader, kernel and the android file system. Instructions on how to build can also be obtained from Android Wiki

Pre-built binaries from this release can be obtained from Package. Please follow the below instructions to modify the file system to make it work.

DSP binaries package

Pull in the DSP binaries and install them following the instructions in the readme.txt in the package. Features supported can be referred at OpenMAX page

IMPORTANT: First you need to rename/move a couple of libraries to make them work. The libraries are in /system/lib:

Rename them to something else (e.g. libOMX.TI.AMR.decode.so.bak and libOMX.TI.AMR.encode.so.bak). By default, AMR libraries have been already renamed in available pre-compiled binaries RLS25.INC2.5 Package.

If you are booting from NAND then once you have booted your filesystem, on your terminal type the following:

cd /system/lib
mv libOMX.TI.AMR.decode.so libOMX.TI.AMR.decode.so.bak
mv libOMX.TI.AMR.encode.so libOMX.TI.AMR.encode.so.bak

then reboot.

Connectivity package

Connectivity package can be obtained from Wilink package. For instructions to build and test, refer to Wilink wiki

Graphics package

To access the graphics package - following steps are required



NO Zoom2 (OMAP 3430) for this L25.INC3.4P3 Release

Limitations/Known Issues

IMPORTANT:

Random white screen issue

This is a known issue which happens due to change in GPIO pin muxing in beta and production boards. Reading the gpio_94 to determine production vs pilot units has shown not to be a reliable method. Now we will check the silicon version of the zoom2 unit based on the following:

If Silicon rev is ES3.1 or greater => Zoom2 Production Units. If Silicon rev is ES3.0 or lesser => Zoom2 Pilot Units

With this information we can determine the gpio value required for the lcd reset:

Zoom2 Production Unit => LCD panel reset gpio = 96
Zoom2 Pilot Unit => LCD panel reset gpio = 55

Refer to the commit ID 571770a16d95a0eaae9740ee0c58246700b345c7 for a fix.

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 (no need of any DSP binary)
2 Audio Playback - AAC Play - Audio shall play without audible glitches. A_000433_eAACplus_stereo_48000Hz_48kbps.m4a Pass Audio plays without audible glitches.
3 A/V Playback - MPEG4 Play - Shall play synchronized audio/video without audible/visible distortion. MPEG4_QVGA_320x240_ASP_L3_30fps_1_5Mbps_AAC_48kHz_128kbps_stereo.MP4 Pass Video is heard and rendered without distortion.
4 A/V Playback - H264 Play - Shall play synchronized audio/video without audible/visible distortion. AV_000343_h264_Baseline_Profile_level_1_3_CIF_30fps_768Kbps_AAC_48khz_128kbps_stereo.mp4 Pass Video is heard and rendered without distortion.
5 A/V Record - MPEG4 Shall record synchronized audio/video without audible/visible distortion. Digital zoom applies to viewfinder and capture. NA Pass Need to rename libOMX.TI.AMR.encode.so and libOMX.TI.AMR.decode.so in /system/lib to make Camcorder use Android's audio encoder since there is no TI AMR encoder.
6 Image Capture - JPEG Image should be capture without any distortion. NA Pass Image is displayed without distortion. You can switch to Camcorder and then go back to Camera to keep taking pictures.
7 Bluetooth Pass if pairing is succesful. NA Pass BT device is paired without issues.
8 FM FM station should be listened properly. N/A. Pass. FM station listened correctly.
9 Bluetooth File Transfer Sent and received file should be uncurrupted. N/A. Pass. Files sent and received OK.
10 WLAN File shall be downloaded and rendered successfully by the browser. NA Pass. URL is downloaded and displayed correctly on browser.
11 GFX SDK OGLES2HelloTriangle GFX should be displayed properly. NA Pass. GFX displayed OK.

Resources

OMAPZoom.org and OMAPpedia.org may be good starting places.

IRC Chat - #linux-omap
Googlegroups - OmapZoom
Mailing List - OMAPAndroid Discussion list

Related Links

[lcd tv]

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox