MEM Module
Application Program Interface
2-205
❏
Stack Size
. The size of the data stack in MADUs. The upper-left
corner of the DSP/BIOS Configuration Tool window shows the
estimated minimum global stack size required for this application (as
a decimal number).
This size is shown as a hex value in Minimum Addressable Data
Units (MADUs). An MADU is the smallest unit of data storage that
can be read or written by the CPU. For the c5000 this is a 16-bit word.
Tconf Name: STACKSIZE
Type: Numeric
Example:
bios.MEM.STACKSIZE = 0x0400;
❏
System Stack Size (MADUs)
. The size of the system stack in
MADUs, applicable only on the C55x device.
Tconf Name: SYSSTACKSIZE
Type: Numeric
Example:
bios.MEM.SYSSTACKSIZE = 0x0100;
❏
No Dynamic Memory Heaps
. Put a checkmark in this box to
completely disable the ability to dynamically allocate memory and the
ability to dynamically create and delete objects. If this property is set
to true, the program may not call the MEM_alloc, MEM_valloc,
MEM_calloc, and malloc or the XXX_create function for any
DSP/BIOS module. If this property is set to true, the Segment For
DSP/BIOS Objects, Segment for malloc()/free(), and Stack segment
for dynamic tasks properties are set to MEM_NULL.
When you set this property to true, heaps already specified in MEM
segments are removed from the configuration. If you later reset this
property to false, recreate heaps by configuring properties for
individual MEM objects as needed.
Tconf Name: NOMEMORYHEAPS
Type: Bool
Example:
bios.MEM.NOMEMORYHEAPS = false;
❏
Segment For DSP/BIOS Objects
. The default memory segment to
contain objects created at run-time with an XXX_create function. The
XXX_Attrs structure passed to the XXX_create function can override
this default. If you select MEM_NULL for this property, creation of
DSP/BIOS objects at run-time via the XXX_create functions is
disabled.
Tconf Name: BIOSOBJSEG
Type: Reference
Example:
bios.MEM.BIOSOBJSEG = prog.get("myMEM");