User`s guide

Naming Conventions
1-10
1.3 Naming Conventions
Each DSP/BIOS module has a unique name that is used as a prefix for
operations (functions), header files, and objects for the module. This name is
comprised of 3 or more uppercase alphanumerics.
Throughout this manual, 54 represents the two-digit numeric appropriate to
your specific DSP platform. If your DSP platform is C6200 based, substitute
62 each time you see the designation 54. For example, DSP/BIOS assembly
language API header files for the C6000 platform will have a suffix of .h62.
For a C5000 DSP platform, substitute either 54 or 55 for each occurrence of
54. Also, each reference to Code Composer Studio C5000 can be substituted
with Code Composer Studio C6000.
All identifiers beginning with upper-case letters followed by an underscore
(XXX_*) should be treated as reserved words.
1.3.1 Module Header Names
Each DSP/BIOS module has two header files containing declarations of all
constants, types, and functions made available through that module’s
interface.
❏ xxx.h. DSP/BIOS API header files for C programs. Your C source files
should include std.h and the header files for any modules the C functions
use.
❏ xxx.h54. DSP/BIOS API header files for assembly programs. Assembly
source files should include the xxx.h54 header file for any module the
assembly source uses. This file contains macro definitions specific to this
device.
Your program must include the corresponding header for each module used
in a particular program source file. In addition, C source files must include
std.h before any module header files. (See section 1.3.4, Data Type Names,
page 1-12, for more information.) The std.h file contains definitions for
standard types and constants. After including std.h, you can include the other
header files in any sequence. For example:
#include <std.h>
#include <tsk.h>
#include <sem.h>
#include <prd.h>
#include <swi.h>