L25.14M3 Release Notes

=Introduction= This release has been developed and tested in the following environment. OS Kernel: Linux® 2.6.29. AndroidTM Donut public project. Toolchain: CodeSourcery compiler version 2008q3-72.

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

Source code Release Manifest for open code source. Release Tag - RLS25.14M.3_RC1

Other Binary packages

DSP Binary Package - DSP binaries Connectivity Package - Wilink project

=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 RLS25.14M3 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:  libOMX.TI.AMR.decode.so  libOMX.TI.AMR.encode.so    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.14M3 Package.

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

mount -o remount rw /system 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

= New in this Release =  This release was validated using "donut" public branch This release is on 2.6.29 Kernel. PV open Core 2.03 and patches BSP  SRF: Fix latency resource target value computations. UART: SDP3430: Enabling the OMAP serial Driver in defconfig Unlock filesystem nand partitions after core off USB HOST Disable SAR for RET remove TWL4030 A2S script before reboot introduce remove_script function <li>sil9022: Fix for sil9022_probe when sil9022 is not present <li>omap: resource: use resource_lookup since it is a safe <li>omap: resource: Make update_resource_level thread safe <li>McSPI: fix for rx error due to channel noise <li>Refer to BSP release notes </ul> <li>Bridge:  <li>Avoid inserting wrong elements to STRM list. <li>Adding protection Resource cleanup linked lists. <li>Refer to Bridge release notes </ul>

<li>Image/Video  <li>memory leak ti omx interface and libopencorehw. <li>Fix a memory leak during error condition in DSPNode.c  <li>Fixed first stss(sync. sample entry) incorrect value of H.264 recorded file. <li>Removed work around to get MPEG4 working. It forced port reconfiguration. <li>AdHoc: While doing random FF and RW of H264 AAC LC clip, board crashed and gives InitMMCodec failed <li>Fixed pixelation (bad quality) during A/V Encode. <li>Refer to OMX release notes </ul>

<li>Bluetooth  <li>AVRCP profile is enabled. <li>BT and FM features now supported with 2.6.29 kernel and donut file system with OMAP Serial driver with UART2 DMA enabled. <li>Audio streaming over A2DP (Media Service) to BT Stereo headset is supported. <li>Audio Streaming over HFP (Phone Audio Servive) to BT mono/stereo headset is supported. It is verified through the command line media player [alsa_aplay]. </ul>

<li>Wi-Fi  <li>Timeout added after driver_wext init. <li>Changing nvs_map.bin file creation path. <li>Following WLAN features are supported (through UI and WLAN TI CLI Utility)  <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;  <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.  Note: SmartReflex&#0153; does tuning around the recommended OPP voltage and never changes the OPP To enable/disable SmartReflex&#1053; for VDD1 & VDD2, use the following commands, respectively: # echo –n > /sys/power/sr_vdd1_autocomp The value can be 	0 – To disable 1 – To enable

# echo –n > /sys/power/sr_vdd2_autocomp The value can be 	0 – To disable 1 – To enable </ul> </ul>

=Limitations/Known Issues=

IMPORTANT:   <li> Currently we support only MPEG4 video encoding. To test it open the camera (or camcorder) app. Once it is open, press <F1>. Select "Settings" from the menu. Once this menu loads, choose "Select Video Quality" and "Select Video Encoder" and set them to DVD-Video NTSC and MPEG4 respectively. See Test Execution Instructions </ul>

Camera  <li>In camera preview when the picture appears, it looks dark (in PC appears fine, also in camera app thumbnail), same behavior that on burst mode setting. <li>“Sorry! Activity Camera (in application Camera) is not responding” error message may appear rarely random when camera is manipulated after several snapshots in a row. <li>“vdd_opp_store: invalid value” message line appear on terminal when trying to display an image thumbnail but has no impact on functionality. <li>Frames may be repeated on preview camera viewfinder after taking several pictures with HP format, this does not affect functionality. </ul>

Camcorder  <li>If you see ‘Activity Camcorder is not responding’, press ‘Wait’ and everything will continue to work fine. </ul>

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=

=Resources=

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

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