L23.i3.3 Release Notes

=Introduction= This release has been developed and tested in the following environment. OS Kernel: Linux® 2.6.32. The perferred Poky Environment is revision 5728; the community may try using latest revisions of Poky against the TI package. Hardware: Zoom3 with TI OMAP3630 IC version: ES1.0 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.

Pre-built binaries from this release can be obtained from PokyL23.i3.3. Please follow the instructions given at the Zoom Flashing Instructions Page.

Other Binary packages

OMX Components & DSP Binaries - DSP binaries The TI OMX components can be found in one package along with another package which has the DSP binaries. In this OMX package there are poky recipes that are delivered and a subset of these recipes specify clear case paths but with this package all the required source files have been included since the OMX packages will all be loaded in your source directory. This will ignore the clear case information in the recipes and build the components as required. Connectivity Package - Wilink project

GIT Comment IDs for this Release
Linux Kernel: "b10ab24e74828809010f7cc6a465c3a73d0fc8f4" X-Loader: "251d92815500143aefdbe3b3558a0ce6daeaebdc" U-Boot: "ab45d2a787a9674bed30542139175d8e090e0749" tidspbridge-lib: "d7ab60790b9be5a0337abfc6d51581c4a1ff056d" tidspbridge-mpusamples: "d7ab60790b9be5a0337abfc6d51581c4a1ff056d" wilink: "69e18d76b8e34eac40e51ca0911cbb29efba495e"

=Build and Installation Instructions=

Building with Poky and the Release Package

The setup of the Poky build environment with the correct tools will be the first task to get setup and this information is available at the Poky Setup Page

Then pull the Pre-built binaries, TI OMX multimedia components, and all the poky recipes for this release. This can be obtained this active link: L23.i3.3 Package then download the L23.i3.3 package. Follow the steps below to setup the build environment:

export POKYROOT=${HOME}/L23_community/ mkdir ${POKYROOT} cd ${POKYROOT} tar zxf ${HOME}/TI_L23i3.3_OMX_DSP_binaries_with_images.tar.gz #This creates the ${POKYROOT}/TI_Community_LO directory

Checkout revision 5728 of Poky using the step given below:

export POKYSRC=${POKYROOT}/pokyomap svn co -r5728 http://svn.o-hand.com/repos/poky/trunk ${POKYSRC}

Follow the steps below to setup the TI code.

cd ${POKYSRC} [ -d meta-texasinstruments ] && rm -rf meta-texasinstruments cp -rp ${POKYROOT}/TI_Community_LO/meta-texasinstruments/ ${POKYSRC} mkdir ${POKYSRC}/sources cp ${POKYROOT}/TI_Community_LO/ti_references/sources/* ${POKYSRC}/sources/

Patching the Meta recipes

cd ${POKYSRC} for p in meta-texasinstruments/patches/*; do patch -p0 < $p; done

Setting up the TI site and local config files:

cp meta-texasinstruments/conf/misc/local.conf build/conf cp meta-texasinstruments/conf/misc/site.conf build/conf
 * 1) Edit site.conf, setting SITE_PROXY_HOST and EXTERNAL_CSL_TOOLCHAIN to match your build settings.

The next step is to run the poky build commands:

Initialize the build environment and then build the OMAP image source poky-init-build-env bitbake poky-image-sato

Poky filesystem will be available in /build/tmp/deploy/images folder 

Possible CAVEATS with the build  The kernel package (linux-tiopmap) might have problems cloning the git repository from dev.omapzoom.org via bitbake. The symptom is that the clone command will hang indefinitely. If this occurs, Control-C out of the "bitbake omap-image-sato" command. In the resulting exit output, bitbake will list the command it was running. It will looked something like this:

sh -c export http_proxy=http://proxyserver:80; export GIT_CONFIG=/home/x0124169/L23_community/pokyomap/build/tmp/staging/i686-linux/usr/etc/gitconfig; export GIT_PROXY_PORT=80; export GIT_PROXY_HOST=wwwgate.ti.com; export GIT_PROXY_COMMAND=/home/x0124169/L23_community/pokyomap/scripts/poky-git-proxy-command; export PATH=/home/x0124169/L23_community/pokyomap/build/tmp/staging/i686-linux/usr/bin/zoom3-none-linux-gnueabi:/home/x0124169/L23_community/pokyomap/build/tmp/staging/i686-linux/usr/sbin:/home/x0124169/L23_community/pokyomap/build/tmp/staging/i686-linux/usr/bin:/home/x0124169/L23_community/pokyomap/build/tmp/cross/armv7a/bin:/home/x0124169/L23_community/pokyomap/build/tmp/staging/i686-linux/sbin:/home/x0124169/L23_community/pokyomap/build/tmp/staging/i686-linux/bin::/home/x0124169/build/cross_compile/arm-2008q3//bin:/home/x0124169/L23_community/pokyomap/bitbake//bin/:/home/x0124169/L23_community/pokyomap/scripts:/opt/bison/bin/:/home/x0124169/build/cross_compile/arm-2008q3/bin/:/opt/klocwork/bin/:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games; git clone -n git://dev.omapzoom.org/pub/scm/integration/kernel-omap3.git /home/x0124169/L23_community/pokyomap/sources/git/dev.omapzoom.org.pub.scm.integration.kernel-omap3.git

Your command will look different, based on your environment. Run this full command from the same terminal you were using to generate the imap-image-sato image. The command should properly clone the kernel tree. Once it has completed, reissue the "bitbake omap-image-sato" command. The build will pick up the downloaded tree, and should continue to build normally.

Building commands for one specific component or to rebuild a component
Additional build information has been supplied for information on building specific components and also how to rebuild a component.

To Build a specific component:

Instead of running: $ bitbake poky-image-sato Run: $ bitbake tiopenmax-audiomanager  (Which ever component needs to be built or a specific group of components) Another example: $ bitback tiopenmax-aacdec

Commands to Rebuild a component:

bitbake tiopenmax-audiomanager -cclean (Step that does the clean) bitbake tiopenmax-audiomanager         (Step that does the rebuild) bitbake -c rebuild tiopenmax-audiomanager (One step command to rebuild)

Booting the Zoom3 board with the OMAP images

Instructions for Booting the Zoom36x board with the new images are given in the Zoom Flashing Instructions Page.

Installing the DSP binaries to the File System 

Please follow the below instructions to modify the file system by adding the DSP binaries to the file system to make it work. Select the DSP binaries installation "DSPbinaries-3.09-Linux-x86-Install" located in the ${POKYROOT}/TI_Community_LO directory. Install them by excepting the licence agreement.  Move qosdyn_3430.dll64P to file system location ./dspbinaries The rest of the binary files need to be moved to ./lib/dsp directory in the file system. You will also need to go to ./dspbinaries and run "/etc/init.d/bridge start" or reboot.

WLAN package 

To add WLAN in the build download the WLAN package and install this package into the poky directory WLAN package can be obtained from Wilink project. Untar the package and move the /meta-texasinstruments/packages to your ${POKYSRC}/meta-texasinstruments/packages folder. Then you need to run the wilink-firmware-1.1-Linux-x86-Install and move the wilink-firmware-1.1.tar.gz to ${POKYSRC}/sources. Update the file /meta-texasinstruments/conf/distro/info/distro-features.inc by uncommenting DISTRO_FEATURES += "tiwifi". Then update the recipe /meta-texasinstruments/images/omap-image-sato.bb to uncomment IMAGE_FEATURES += "omap-conn". Run the poky build commands listed above and this will build WLAN and add it to the built image.

SD/MMC Card Bootarg parameters.
In teraterm or minicom insert this bootargs (IP address based on your setup.)

nand unlock nand ecc sw   setenv ipaddr 10.87.224.99 setenv gatewayip 10.87.224.1 setenv serverip 10.87.230.185 setenv ethaddr 08:00:EE:03:7D:C1 setenv video_settings omap_vout_mod.video1_numbuffers=6 omap_vout_mod.vid1_static_vrfb_alloc=y omap_vout_mod.video2_numbuffers=6 omap_vout_mod.vid2_static_vrfb_alloc=y setenv board_settings mem=512M console=ttyS0,115200n8 setenv bootcmd 'mmcinit 0;fatload mmc 0 0x81000000 uImage; bootm 0x81000000' setenv bootcmd=mmcinit 0; fatload mmc 0 80300000 uImage-zoom3.bin; bootm 0x80300000 set bootdelay 2 saveenv boot

= New in this Release =  Kernel based on 2.6.32  BSP  Power Mgmt: OSWR, Smart Reflex Power Mgmt: Support for 1 GHz; VDD1 changed to 1.35 V, S/w Tiering Support for 3630 DSS: Offmode support, HDMI supported with dsi clock (supports all TVs) DSS: Rotation support  Bridge:  <li>Fixed an issue during suspend/resume were dsp was causing a kernel panic due to a suspend timeout. <li>All the patches sent to open source were merged to L25x. </ul> <li>Audio/System  <li>Audio Manager was updated in order to use latest amixer controls <li>Updates for Design Spec and Release Notes documents - new files using OMAP3 naming convention to be more generic across releases. </ul> <li>Image/Video  <li>Migration to 3.9 SN baseline. <li>Klocwork issues fixed. <li>VPP test cases 100% successful. The QBUF_IOCTL error from post proc resolved. <li>LSC patches for fixing dynamic reconfiguration while streaming. </ul> <li>Wi-Fi  <li>Driver Version: WiLink_6.1.0.0.115 <li>Firmware Version: Rev 6.1.0.0.288 <li>Following WLAN features are supported (through UI and WLAN TI CLI Utility)  <li>Scan and list for AP's in the vicinity <li>Connecting to the available AP's      <li>Data transfer using ping and Iperf tool <li>Security <li>Web browsing  Note: Instructions to enable on-demand governor omap_version = 3630 -> will boot @600Mhz (opp 50/100 supported) omap_version = 3630800 -> will boot @800Mhz (opp 50/100/Turbo supported) omap_version = 36301000 -> will boot @ 1GHz. (opp 50/100/Turbo/1GH supported) </ul>To change governor to on-demand following command will help echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor </ul> Note: When using on-demand governor to set at OPP1G the Zoom3 screen will go blank therefore, on-demand governor (pre-release) does not yet support OPP1G, OPP1G should be used with frequency governor, this will be fixed in L23.I3.4. </ul> </ul> </ul>

=Limitations/Known Issues= The release has been validated on Poky version 5728 and the community can try and use the TI content on latest revisions of Poky Random Issues or Limitations seen with 23.i3.3 

When you take a picture using the JPEG encoder the image that is taken can't be viewed if you attempt to load through the JPEG Decoder. If you try to view any other jpeg image this works fine.<BR> Zoom3 boot log shows invalid mux entries due to new mux framework in 2.6.32 kernel.<BR> Subsequent NAND boots are unstable with error to find /dev/fb0, /dev/tty.<BR> Seek on H.263 playback has problems.<BR> Random Kernel panic due to i2c read/write in some application.<BR> When using on-demand governor to set at OPP1G the Zoom3 screen will go blank.<BR> Issues Reported on WLAN being able to find the AP Network if the whole filesystem isn't mounted in the SC card, thus resulting in issues being able to Browse the Web. With filesystem mounted in SD, the list of APs appear and things work OK.<BR>

</ul>

=Use Case Test Results=

Instructions on how to execute the tests can be found in the Test Execution User Guide

=Resources=

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

IRC Chat - #linux-omap Googlegroups - OmapZoom