User`s guide

Naming Conventions
About DSP/BIOS 1-13
In addition, the standard constant NULL (0) is used by DSP/BIOS to signify
an empty pointer value. The constants TRUE (1) and FALSE (0) are used for
values of type Bool.
Object structures used by the DSP/BIOS API modules use a naming
convention of MOD_Obj, where MOD is the letter code for the object’s
module. If your program code uses any such objects created by the
Configuration Tool, it should make an extern declaration for the object. For
example:
extern LOG_Obj trace;
The Configuration Tool automatically generates a C header to file that
contains the appropriate declarations for all DSP/BIOS objects created by the
Configuration Tool (<program>.cfg.h. This file can be included by the
application’s source files to accomplish the DSP/BIOS object declarations.
DSP/BIOS for the C54x platform was originally developed for the 16-bit
addressing model of the early C54x devices. Newer C54x devices
incorporate far extended addressing modes, and DSP/BIOS has been
modified to work in this environment. See the Application Report, DSP/BIOS
and TMS320C54x Extended Addressing, SPRA599, for more information.
1.3.5 Memory Segment Names
The memory segment names used by DSP/BIOS are described in Table 1-3.
You can change the origin, size, and name of most default memory segments
using the Configuration Tool.
Table 1-3. Memory Segment Names
a. C54x Platform
Segment Description
IDATA Internal (on-device) data memory
EDATA
Primary block of external data memory
EDATA1
Secondary block of external data memory (not contigu-
ous with EDATA)
IPROG Internal (on-device) program memory
EPROG Primary block of external program memory
EPROG1
Secondary block of external program memory (not con-
tiguous with EPROG)
USERREGS Page 0 user memory (28 words)
BIOSREGS Page 0 reserved registers (4 words)
VECT Interrupt vector segment