Naming Conventions; Assembly Language Interface Overview - Texas Instruments TMS320C55 Series Reference Manual

Dsp/bios 5.32 application programming interface api
Table of Contents

Advertisement

1.2

Naming Conventions

1.3

Assembly Language Interface Overview

1.4
DSP/BIOS Tconf Overview
The format for a DSP/BIOS operation name is a 3- or 4-letter prefix for
the module that contains the operation, an underscore, and the action.
The assembly interface that was provided for some of the DSP/BIOS
APIs has been deprecated. They are no longer documented.
Assembly functions can call C functions. Remember that the C compiler
adds an underscore prefix to function names, so when calling a C
function from assembly, add an underscore to the beginning of the C
function name. For example, call _myfunction instead of myfunction. See
the TMS320C55x Optimizing Compiler User's Guide for more details.
When you are using the DSP/BIOS Configuration Tool, use a leading
underscore before the name of any C function you configure. (The
DSP/BIOS Configuration Tool generates assembly code, but does not
add the underscore automatically.) If you are using Tconf, do not add an
underscore before the function name; Tconf internally adds the
underscore needed to call a C function from assembly.
All DSP/BIOS APIs follow standard C calling conventions as documented
in the C programmer's guide for the device you are using.
DSP/BIOS APIs save and restore context for each thread during a
context switch. Your code should simply follow standard C register usage
conventions. Code written in assembly language should be written to
conform to the register usage model specified in the C compiler manual
for your device. When writing assembly language, take special care to
make sure the C context is preserved. For example, if you change the
AMR register on the 'C6000, you should be sure to change it back before
returning from your assembly language routine. See the Register Usage
appendix in this book to see how DSP/BIOS uses specific registers.
The section describing each modules in this manual lists properties that
can be configured in Tconf scripts, along with their types and default
values. The sections on manager properties and instance properties also
provide Tconf examples that set each property.
For details on Tconf scripts, see the DSP/BIOS Tconf User's Guide
(SPRU007). The language used is JavaScript with an object model
specific to the needs of DSP/BIOS configuration.
Naming Conventions
API Functional Overview
1-3

Advertisement

Table of Contents
loading

Table of Contents