Please note as of Wednesday, August 15th, 2018 this wiki has been set to read only. If you are a TI Employee and require Edit ability please contact x0211426 from the company directory.

GSG: OMAP35xx WinCE DVSDK Software Setup (new)

From Texas Instruments Wiki
Jump to: navigation, search

^ Up to main OMAP35xx WinCE DVSDK Getting Started Guide Table of Contents

Note: This page describes the software setup for OMAP35xx WinCE DVSDK 1.00.00.05 and later releases.

This topic provides step-by-step instructions for setting up the software you will use to develop applications with the OMAP35xx WinCE DVSDK.

Important Note: The OMAP35x EVM kit comes with a Linux-based DVSDK and software getting started instructions. You should ignore the software setup instructions that come with the OMAP35x EVM from Mistral Solutions. Instead, follow these wiki-based instructions for the WinCE-based version of the DVSDK.

Downloading software

You need to download the following software components before you begin installing:

The WinCE DVSDK package comes with prebuilt binaries. If you plan to compile any of the software packages delivered with WinCE DVSDK, you will need to download the following packages as well (refer the DVSDK release notes in the DVSDK installation package for exact tools versions used):

Installing the software

Installing the Windows Embedded CE software

You must install the following software prior to installing the OMA35xx WinCE BSP. Note that the software must be installed in the order listed. Contact Microsoft for more information about the listed software and known issues with the installation process:

  • Visual Studio 2005 (VS2005)
  • Visual Studio SP1 (Service Pack 1)
  • Windows Embedded CE 6.0 (Plug In for Visual Studio 2005)
  • Windows Embedded CE 6.0 SP1 (Service Pack 1)
  • Windows Embedded CE 6.0 R2 Update
  • Windows Embedded CE 6.0 Platform Builder - Cumulative Product Update Rollup Package (through 12/31/2008)
  • Remaining Windows Embedded CE 6.0 Monthly updates
  • Windows Embedded CE 6.0 R3 Update (if planning to use WinCE 6.0 R3)

If you do not already have this software, you can obtain evaluation versions from Microsoft at http://msdn.microsoft.com/en-us/embedded/aa731407.aspx.

Installing TI Code Generation Tools

Run the ti_cgt_c6000_6.1.xx_setup_win32.exe file that you downloaded and answer the prompts within the installer. CAUTION: Instead of the default installation path, install TI Code Generation tools in a directory that has no spaces in the path else some component builds may fail.

Installing DSP/BIOS

Run the bios_setupwin32_5_33_xx.exe file that you downloaded and answer the prompts within the installer.

Installing XDCtools

Run the xdctools_setupwin32_3_10_xx.exe file that you downloaded and answer the prompts within the installer. CAUTION: Instead of the default installation path, install XDCtools in a directory that has no spaces in the path else some component builds may fail.

Installing ActivePerl

Follow the installation instruction from the downloaded ActivePerl package

Installing the Board Support Package (BSP)

Follow the procedures in Chapter 3 of the EVM3530 BSP User Guide to set up the WinCE build environment.

Installing the DVSDK software

To install the OMAP35xx WinCE DVSDK software, follow these steps:

  1. Run the installer dvsdk_wince_1_xx_yy_xx_setup.exe.
  2. Follow the installer instructions. You should install the software either in the default directory shown by the installer or in a top-level directory such as C:\
  3. The installer will setup a system environment variable DVSDK_INSTALL_DIR with the path to the directory where DVSDK was installed.

 

Integrating the WinCE DVSDK with the WinCE OMAP3530 Board Support Package

  1. Follow the steps outlined in the BSP getting started guide to set up your compilation environment with Visual Studio 2005 and the WinCE 6.0 Platform Builder.
  2. Compile BSP with the instructions given in the BSP getting started guide and verify its functionality.
  3. The BSP comes with prebuilt WinCE DVSDK components that will be overridden by the new WinCE DVSDK
  4. Make a backup copy of the PLATFORM\TI_EVM_3530\FILES directory since some of the files in this directory will be overwritten by the DVSDK release
  5. Modify the BSP as detailed in the following subsections if applicable:

If using BSP version 6.13.00 or later

Edit ti_evm_3530.bat file under PLATFORM\TI_EVM_3530 directory

Change

REM set BSP_TI_DVSDK=1

set BSP_DSPLINK=1
set BSP_CMEM=1
set BSP_DSHOWFILTER=1
set BSP_H264_DECODE_FILTER=1
set BSP_MPEG4_DECODE_FILTER=1
set BSP_MPEG2_DECODE_FILTER=1
set BSP_AAC_DECODE_FILTER=1
set BSP_3GPP_DEMUX=1
set BSP_AAC_PARSER=1

to

set BSP_TI_DVSDK=1

set BSP_DSPLINK=
set BSP_CMEM=
set BSP_DSHOWFILTER=
set BSP_H264_DECODE_FILTER=
set BSP_MPEG4_DECODE_FILTER=
set BSP_MPEG2_DECODE_FILTER=
set BSP_AAC_DECODE_FILTER=
set BSP_3GPP_DEMUX=
set BSP_AAC_PARSER=

There is no need to change the platform.reg or platform.bib files. (The step above though not strictly necessary will avoid warnings related to duplicate file entries.)

If using BSP version 6.12.04 or earlier

Remove the following sections from the PLATFORM\TI_EVM_3530\FILES\platform.reg file:

IF BSP_DSPLINK
...
ENDIF BSP_DSPLINK
 
IF BSP_CMEM
...
ENDIF BSP_CMEM
 
IF BSP_MPEG2_DECODE_FILTER
...
ENDIF
 
IF BSP_MPEG4_DECODE_FILTER
...
ENDIF 
 
IF BSP_H264_DECODE_FILTER
...
ENDIF 
 

Remove the following lines from the PLATFORM\TI_EVM_3530\FILES\platform.bib file (the sections mentioned below may not be contiguous in the file):

IF BSP_DSPLINK
  dsplinkk.dll                    $(_FLATRELEASEDIR)\dsplinkk.dll    NK SHK
  lpmdrv.dll                      $(_FLATRELEASEDIR)\lpmdrv.dll      NK SHK
ENDIF BSP_DSPLINK
 
IF BSP_CMEM
  cmemk.dll                   $(_FLATRELEASEDIR)\cmemk.dll    NK SHK
ENDIF BSP_CMEM
 
IF BSP_DSHOWFILTER
  timm.dll                $(_FLATRELEASEDIR)\timm.dll                 NK SH
ENDIF BSP_DSHOWFILTER
 
IF BSP_H264_DECODE_FILTER
  H264VideoDecoder.dll    $(_FLATRELEASEDIR)\H264VideoDecoder.dll     NK SHM
ENDIF BSP_H264_DECODE_FILTER
 
IF BSP_MPEG4_DECODE_FILTER
  MPEG4VideoDecoder.dll   $(_FLATRELEASEDIR)\MPEG4VideoDecoder.dll    NK SHM
ENDIF BSP_MPEG4_DECODE_FILTER
 
IF BSP_MPEG2_DECODE_FILTER
  MPEG2VideoDecoder.dll   $(_FLATRELEASEDIR)\MPEG2VideoDecoder.dll    NK SHM
ENDIF BSP_MPEG2_DECODE_FILTER
 
IF BSP_DMAI_SAMPLE_APPLICATIONS
  ; DMAI sample applications, requires BSP_DSHOWFILTER
  video_encode_io1_omap3530.exe   $(_FLATRELEASEDIR)\video_encode_io1_omap3530.exe    NK
  audio_decode_io1_omap3530.exe   $(_FLATRELEASEDIR)\audio_decode_io1_omap3530.exe    NK
  image_encode_io1_omap3530.exe   $(_FLATRELEASEDIR)\image_encode_io1_omap3530.exe    NK
  image_decode_io1_omap3530.exe   $(_FLATRELEASEDIR)\image_decode_io1_omap3530.exe    NK
  video_decode_io2_omap3530.exe   $(_FLATRELEASEDIR)\video_decode_io2_omap3530.exe    NK
ENDIF
 
IF BSP_DSHOWFILTER
  cs.x64P                     $(_FLATRELEASEDIR)\cs.x64P                          NK
ENDIF BSP_DSHOWFILTER
 


Integration steps in Visual Studio

  1. Verify that the environment variable DVSDK_INSTALL_DIR exists and  is set to the location where DVSDK has been installed. If the default installation path was selected then this should be set to c:\TI\dvsdk_wince\dvsdk_wince_1_xx_yy_zz (where the xx_yy_zz stand for the actual dvsdk wince version)
  2. Edit setpaths.bat file under %DVSDK_INSTALL_DIR%. The setpaths.bat file is the central place to update tools and WINCE DVSDK component paths. Only the tools section needs to be updated with proper paths.
  3. Open Visual Studio 2005.
  4. Open the OSDesigns EVM_3530 solution (as described in the BSP documentation)
  5. In the Solution Explorer, select the Subprojects node of the EVM_3530 project.
  6. Right-click and select Add Existing Subproject. (If you have changed your system settings for mouse clicks, modify the right-click to meet your needs.)
    Add subproject.png
  7. Navigate to %DVSDK_INSTALL_DIR%\dvsdk_integration_1_xx_yy_zz and select the DVSDK_Integration.pbpxml file. You should have subproject as shown below
    Dvsdk integration subproject.jpg
  8. Make sure that all DVSDK catalog files (not including TI_EVM_3530.pbcxml) from previous installations are deleted or moved from the %_WINCEROOT%/PLATFORM/TI_EVM_3530/CATALOG directory and sub-directories.
  9. Copy the folder  %DVSDK_INSTALL_DIR%\dvsdk_integration_1_xx_yy_zz\dvsdk_catalog (along with all the files inside the folder) to your %_WINCEROOT%\PLATFORM\<bsp_folder>\CATALOG folder. The destination directory is typically %_WINCEROOT%\PLATFORM\TI_EVM_3530\CATALOG
  10. From the Visual Studio menus, choose View > Other Windows > Catalog Items View to enable the catalog items view.
  11. Click on the "Refresh Catalog Tree" button to update the DVSDK catalog items
    Catalog refresh button.jpg
  12. Expand the EVM_3530 tree, and then expand the Third Party\Texas Instruments\Multimedia Framework tree.#Enable the following catalog entries:
    • MMF:TI:CMEM
    • MMF:TI:DSPLINK
    • MMF:TI:CS
    • MMF:TI:H264_DECODE_FILTER
    • MMF:TI:MPEG2_DECODE_FILTER
    • MMF:TI:MPEG4_DECODE_FILTER
    • MMF:TI:TIMM
Dvsdk catalog tree.jpg
  1. From the menus, choose Build > Advanced Build Commands > Build Current BSP and Subprojects to compile the subproject along with the BSP. If you have already compiled the BSP, you can use subproject menu to build the subproject only.
  2. If there are build errors check the build.log under dvsdk_integration_1_xx_yy_zz directory (detailed error information does not show up on the platform builder window).
  3. This should copy all the necessary DLLs/DMAI applications to the FLATRELEASE folder, update the DVSDK specific .bib/.reg entries and update the WinCE binary to run the demos as explained in GSG: OMAP35xx WinCE DVSDK Running the Demos.
  4. This concludes the steps for integrating DVSDK WINCE prebuilt binaries into the BSP. It is highly recommended that the above steps are followed to make sure that the baseline is okay before recompiling or changing any DVSDK components.

 

Changing/upgrading DVSDK software packages

The OMAP35xx WinCE DVSDK is made up of the following software packages:

  • Codec Engine
  • Framework Components
  • DSP Link
  • DSP codec server
  • DMAI
  • TI Direct Show Filters
  • XDAIS
  • Utility components such as WinCE Utils, Local power manager, BIOS utils, edma3_lld etc

Please refer to the Release Notes in the OMAP35xx WinCE DVSDK installation for exact component version information as well as tools versions.

The DVSDK for WinCE is delivered in precompiled form, but you can upgrade or change the software packages used.

CAUTION: Before you upgrade any of the packages, please ensure that the package versions you want to use support WinCE and that they are compatible with the other DVSDK components used.

The following packages can be recompiled using platform builder projects that are provided as part of the software package (these platform builder projects are dummy projects that invoke command line to build the components):

  • DSP Link
  • DSP codec server
  • DMAI
  • Direct Show Filters

NOTE: All other components cannot be recompiled but any update will contain binaries.

In order to recompile the software packages, you will need Texas Instruments C6000 Code Generation Tools, DSP/BIOS, and XDCtools as well as active perl as described in an earlier section. Refer the DVSDK release notes for exact versions of these tools.

The DVSDK WINCE installation would have taken care of setting an environment variable called DVSDK_INSTALL_DIR to the installation path. If this system environment variable is not set then either this can be done manually in system environment setting or this variable can be edited in setpaths.bat file under the DVSDK_INSTALL_DIR directory. The following is an example of the DVSDK_INSTALL_DIR variable setting (the version you have maybe different):

DVSDK_INSTALL_DIR
C:\TI\dvsdk_wince\dvsdk_wince_1_00_00_05

Building DVSDK packages in Visual Studio

  • Verify that the environment variable DVSDK_INSTALL_DIR exists and is set to the location where DVSDK has been installed.
  • Edit setpaths.bat file under %DVSDK_INSTALL_DIR%. The setpaths.bat file is the central place to update tools and WINCE DVSDK component paths. Make sure that the tools path are correct and the DVSDK component paths are updated to reflect the packages that are being changed.
  • Open Visual Studio 2005.
  • Open the OSDesigns EVM_3530 solution (as described in the BSP documentation)
  • In the Solution Explorer, select the Subprojects node of the EVM_3530 project tree.
  • Right-click and select Add Existing Subproject.
Add subproject.png
  • Add DVSDK Integration subproject - Navigate to %DVSDK_INSTALL_DIR%\dvsdk_integration_1_xx_yy_zz and select the DVSDK_Integration.pbpxml file.
  • Add DSPLink subproject - Navigate to %DVSDK_INSTALL_DIR%\dsplink_1_xx_yy\dsplink\etc\host\projects\WinCE\DSPLink and select the DSPLink.pbpxml file.
  • Add DSP Coder Server subproject - Navigate to %DVSDK_INSTALL_DIR%\dvsdk_integration_1_xx_yy_zz\CodecServer and select the CodecServer.pbpxml file.
  • Add DMAI subproject - Navigate to %DVSDK_INSTALL_DIR%\dmai_1_xx_yy_zz\wince_pb\wince600 and select the dmai.pbpxml file.
  • Add TI Direct Show Filters subproject - Navigate to %DVSDK_INSTALL_DIR%\dshow_1_xx_yy_zz\project and select the dshow.pbpxml file.
  • The Subprojects tree should look like this (please note that the subprojects are displayed in alphabetical order and not in the build order)
    Dvsdk all subprojects.jpg

  • Specify Subproject Build Order - In the Solution Explorer view, right click on the Subprojects node of the EVM_3530 project tree and select Set Subproject Build Order...
SubprojectBuildOrderMenu.jpg

  • This will bring up a floating window where you can specify the order in which subprojects are built. Ensure that the build order is as shown below and then select OK.
SubprojectBuildOrderEditor.jpg

  • Make sure that all DVSDK catalog files (not including TI_EVM_3530.pbcxml) from previous installations are deleted or moved from the %_WINCEROOT%/PLATFORM/TI_EVM_3530/CATALOG directory and sub-directories.
  • Copy the folder  %DVSDK_INSTALL_DIR%\dvsdk_integration_1_xx_yy_zz\dvsdk_catalog (along with all the files inside the folder) %_WINCEROOT%\PLATFORM\<bsp_folder>\CATALOG folder.
  • From the Visual Studio menus, choose View > Other Windows > Catalog Items View to enable the catalog items view.
  • Click on the "Refresh Catalog Tree" button to update the DVSDK catalog items.
    Catalog refresh button.jpg

  • Expand the EVM_3530 tree, and then expand the Third Party\Texas Instruments\Multimedia Framework tree.
  • Enable the following catalog entries:
  MMF:TI:CMEM
  MMF:TI:DSPLINK
  MMF:TI:CS
  MMF:TI:H264_DECODE_FILTER
  MMF:TI:MPEG2_DECODE_FILTER
  MMF:TI:MPEG4_DECODE_FILTER
  MMF:TI:TIMM
Dvsdk catalog tree.jpg

  • From the menus, choose Build > Advanced Build Commands > Build Current BSP and Subprojects to compile all the DVSDK subprojects along with the BSP.
  • If there are build errors check the build.log (located in the same dir as the corresponding .pbpxml file)for each of the subprojects (detailed error information does not show up on the platform builder window).
  • This should update the DVSDK packages and generate all the necessary DLLs, DMAI application, .bib files, .reg files and the WinCE binary to run the demos as explained in GSG: OMAP35xx WinCE DVSDK Running the Demos.
  • This concludes the section on building DVSDK components in Visual Studio



Building DVSDK Packages Using The Command Line

The following sections have pointers to documents that explain how to upgrade the various DVSDK packages by building them using command line utilities.

Compiling DSP Link

Follow the procedure outlined in the DSP Link install guide, which is located at %DVSDK_INSTALL_DIR%\dsplink_1_xx_yy\dsplink\doc\InstallGuide_WinCE_OMAP3530.pdf, to compile the DSP Link package.

Compiling DSP codec server

Follow the procedure outlined in the DSP Codec Server release notes located under %DVSDK_INSTALL_DIR%\cs1omap3530_1_xx_yy.

Compiling DMAI

Follow the procedure outlined in the DMAI user guide under %DVSDK_INSTALL_DIR%\dmai_1_xx_yy_zz directory to compile the DMAI package.

Compiling Direct Show Filters

Follow the procedure outlined in the release notes under DVSDK_INSTALL_DIR\dshow_1_xx_yy_zz to compile the dshow filters.

Package Dependencies

As shown in the DVSDK WinCE software architecture diagram, various software layers are dependent on each other. You need to recompile dependent packages if you change or upgrade one of the DVSDK software packages. The following table outlines the packages you need to recompile if a change is made to one of the packages.

Package Changed Packages to Recompile
Codec Engine DSP Codec Server, DMAI, Direct Show Filters
DSP Link DSP Link, DSP Codec Server, DMAI, Direct Show Filters
DSP codec server DSP codec server, DMAI, Direct Show Filters
DMAI DMAI, Direct Show Filters
Direct Show Filters Direct Show Filters

 

What next?

To begin running demo applications, go to the GSG: OMAP35xx WinCE DVSDK Running the Demos topic.

For links to wiki topics about modifying the Codec Engine memory configuration, go to the GSG: OMAP35xx WinCE DVSDK Overview topic.