Texas Instruments Codec Engine Server, Руководство пользователя

Страница: 25 / 36

Creating a Codec Server
Configuring a Codec Server 2-9
To see documentation for the attributes of the Server module, follow
these steps:
1) Open CE_INSTALL_DIR/xdoc/index.html to see the Configuration
Reference. Depending on your browser, you may need to enable
active content to view the list of nodes on the left.
2) Click the link to the ti.sdo.ce package.
3) Click the link to the Server module.
4) You see the config params that you can set for this module.
Note: To navigate backward in this window, click the " Back " link in
the upper-right corner of the window. The usual Back button in your
browser does not function correctly in this online help system.
For example, you see that the threadAttrs structure has several fields.
The following statements cause the Server module in the ti.sdo.ce
package to be made available to the configuration script. It then sets the
threadAttrs.priority attribute of the Server module to Server.MINPRI. This
indicates that the task threads created by the Codec Server should run at
the minimum priority level.
var Server = xdc.useModule('ti.sdo.ce.Server');
Server.threadAttrs.priority = Server.MINPRI;
To create your own *.cfg file for your server, follow these steps:
1) Rename the *.cfg file in your server directory to match the name of
your server. For example, your file might be called "my_server.cfg".
2) Edit the servername .cfg file with a text editor.
3) In order to allow application developers to use the TraceUtil module
on the GPP side to gather DSP/BIOS log information, you must
enable DSP/BIOS logging in your DSP server image. If the following
line is not already in your server's configuration script, you should
add it to enable DSP/BIOS logging:
var LogServer = xdc.useModule('ti.sdo.ce.bioslog.LogServer');
4) Modify the statements that get codec modules to reference the codec
modules you want to use. Use the package name from your codec
provider. Example codecs are available in the "examples" repository
beginning with the "codecs" namespace (that is, the
examples\codecs directory). Your codecs should be "well named"
beginning with your company name to produce unique package
names.