config Settings.debug // module-wide |
 |
Enable the debug profile of the osal BIOS module
XDCscript usage |
meta-domain |
Settings.debug = Bool false;
config Settings.defaultMemSegId // module-wide |
 |
Default ID of the memory segment from which to allocate space
(for Memory_alloc/free() calls, as opposed to Memory_segAlloc/Free()).
Typically it's the segment where all other code and data go
XDCscript usage |
meta-domain |
Settings.defaultMemSegId = String null;
DETAILS
If left as "null", the system will try to find a BIOS segment named
"DDR" or "DDR2" and assign its name to this field. In the future
this auto-find feature may be removed, so it's best that user .cfg
script set this value directly to what they know is appropriate
segment.
config Settings.enableLogging // module-wide |
 |
If set to true, enable data generation necessary for CE benchmarking
analysis
XDCscript usage |
meta-domain |
Settings.enableLogging = Bool true;
config Settings.logName // module-wide |
 |
Name of buffer used for capturing benchmarking data
XDCscript usage |
meta-domain |
Settings.logName = String "ti_sdo_ce_osal_LOG_Buffer";
DETAILS
In BIOS environments, this is the name of the BIOS LOG.
config Settings.logSeg // module-wide |
 |
Memory segment for the buffer used for capturing benchmarking data
XDCscript usage |
meta-domain |
Settings.logSeg = String null;
config Settings.logSize // module-wide |
 |
Size of buffer used for capturing benchmarking data
XDCscript usage |
meta-domain |
Settings.logSize = Int 256;
config Settings.logType // module-wide |
 |
Type of buffer used for capturing benchmarking data
XDCscript usage |
meta-domain |
Settings.logType = String "circular";
DETAILS
This can be either "fixed" or "circular".
config Settings.traceBufferSize // module-wide |
 |
Size of the server trace buffer, in MAUs
XDCscript usage |
meta-domain |
Settings.traceBufferSize = Int 32768;
DETAILS
The server trace buffer is a circular buffer of characters written
to by clients of ti.sdo.ce.osal.Trace (and ti.sdo.utils.trace.GT) and
read by the Engine_*Trace() methods.
All the trace data in the target memory is stored into a globally
visible character buffer
Char Global_traceBuffer[ <traceBufferSize> ];