Specifications

iv
Notational Conventions
Notational Conventions
This document uses the following conventions:
❏
The TMS320C6000 core is also referred to as ’C6000.
❏
Code Composer Studio generates files with extensions of .s62 and .h62.
These files can also be used with both the TMS320C6201 and the
TMS320C6701. DSP/BIOS does not use the floating-point instructions
that are supported by the TMS320C6701.
❏
Program listings, program examples, and interactive displays are shown
in a
special typeface
. Examples use a
bold version
of the special
typeface for emphasis; interactive displays use a
bold version
of the
special typeface to distinguish commands that you enter from items that
the system displays (such as prompts, command output, error messages,
etc.).
Here is a sample program listing:
Void copy(HST_Obj *input, HST_Obj *output)
{
PIP_Obj *in, *out;
Uns *src, *dst;
Uns size;
❏
In syntax descriptions, the instruction, command, or directive is in a
bold
typeface
and parameters are in an
italic typeface . Portions of a syntax
that are in bold should be entered as shown; portions of a syntax that are
in italics
describe the type of information that should be entered. Syntax
that is entered on a command line is centered. Syntax that is used in a
text file is left-justified.
❏
Square brackets ( [ ] ) identify an optional parameter. If you use an
optional parameter, you specify the information within the brackets.
Unless the square brackets are in a
bold
typeface, do not enter the
brackets themselves.