How to Create DSP Algorithm Package with RidgeRun SDK

From RidgeRun Developer Connection

(Difference between revisions)
Jump to:navigation, search
(Running the wizard)
Line 12: Line 12:
|-
|-
|}
|}
 +
 +
=Requirements for the GencodecPkg Wizard=
 +
*Engine 2.25 or later
 +
**CE 2.25.02 improves the GUI interface
 +
*XDAIS 6.25 or later
 +
*XDAIS 6.25.02 improves the code templates
 +
*XDCtools 3.16 or later
=Additional Background Info=
=Additional Background Info=
Line 35: Line 42:
Make sure you use a tab in that second line as it is required by make for all the command
Make sure you use a tab in that second line as it is required by make for all the command
-
 
-
=Requirements for the GencodecPkg Wizard=
 
-
*Engine 2.25 or later
 
-
**CE 2.25.02 improves the GUI interface
 
-
*XDAIS 6.25 or later
 
-
*XDAIS 6.25.02 improves the code templates
 
-
*XDCtools 3.16 or later
 
=Running the wizard=
=Running the wizard=

Revision as of 15:25, 5 June 2010

Contents

Abstract

This document will be an easy way to create a new DSP algorithm based on TMS320 DSP processor. It will target these algorithms and assists the reader with making the algorithms compliant with the TMS320 DSP algorithm standard which is part of TI's eXpressDSP technology initiative. The document proposes a simple approach to running xDAIS (iUniversal) algorithms with a Codec Engine (CE) application based on TI's technology and RidgeRun SDK. The wizard selected is responsible for creating an xDAIS algorithm (iUniversal), and providing the necessary packaging to enable these algorithms to be consumed and configured by Codec Engine.


We assume readers have a basic understanding of the elements in a Codec Engine application, including VISA APIs, xDM, servers, and codecs.

Requirements for the GencodecPkg Wizard

Additional Background Info

Invoking the wizard from a DVSDK makefile

The GenCodecPkg wizard generates the files and packaging required for integrating an algorithm into Codec Engine. Assuming your using a RR SDK you have a complete integration with a TI DVSDK release, then you likely have already defined paths to all your tools in the Rules.make .

These generated Codec Packages can be integrated into a Server and the document will explain the way to append the new codec into TI's Codec Server

Inside the Makefile from the DVSDK:

 
$ cd $(DEVDIR)/propietary/dvsdk*
$ gedit Makefile

You should append the following rule:

gencodecpkg: 
    $(XDC)/xs --xdcpath="$(CE_INSTALL_DIR)/packages; \
    $(XDAIS_INSTALL_DIR)/packages" ti.sdo.ce.wizards.gencodecpkg

Make sure you use a tab in that second line as it is required by make for all the command

Running the wizard

From your DVSDK directory you can invoke gencodecpkg with the following command:

 
 $ cd $(DEVDIR)/proprietary/dvsdk_* 
 $ make gencodecpkg

At the first Screen

Procedure

  1. Choose the 3rd option, I want to create an algorithm from scratch
  2. Point to the xDAIS directory
  3. Point to the root of the compiler installation: CGTOOLS
Navigation
Toolbox