General purpose logger enabling applications to log data that
can be read by an instrumentation host over JTAG, when the
target is halted
Each LoggerStopMode instance has its own buffer for events logged to that
instance. By including the header file, ti/uia/runtime/LogUC.h, you
can specify the LoggerStopMode instance that you want the event logged
to.
When the buffer is filled, LoggerStopMode will update the QueueDescriptor
data structure (which provides the interface needed by the host's JTAG
transport handler to read the logged event data) and wrap around the buffer's
write pointer.
LoggerStopMode was designed to have as minimal impact as possible on an
application when calling a Log function. There are several configuration
parameters that allow an application to get the optimal performance in
exchange for certain restrictions.
Interrupts are disabled during the duration of the log call.
The following XDC configuration statements
create a logger module, and assign it as the default logger for all
modules.
The following XDC configuration statements show how to use LoggingSetup
with LoggerStopMode. Note that the second line is unnecessary, since
LoggerStopMode is the default logger for LoggingSetup.
enum LoggerStopMode_TransferType |
|
typedef enum LoggerStopMode_TransferType {
LoggerStopMode_TransferType_RELIABLE,
LoggerStopMode_TransferType_LOSSY
} LoggerStopMode_TransferType;
config LoggerStopMode_filterByLevel // module-wide |
|
Support filtering of events by event level
extern const Bool LoggerStopMode_filterByLevel;
DETAILS
To improve logging performance, this feature can be disabled by setting
filterByLevel to false.
See '
setFilterLevel' for an explanation of level filtering.
config LoggerStopMode_isTimestampEnabled // module-wide |
|
Enable or disable logging the 64-bit local CPU timestamp
at the start of each event
extern const Bool LoggerStopMode_isTimestampEnabled;
DETAILS
Having a timestamp allows an instrumentation host (e.g.
System Analyzer) to display events with the correct system time.
config LoggerStopMode_level1Mask // module-wide |
|
Mask of diags categories whose initial filtering level is Diags.LEVEL1
extern const Diags_Mask LoggerStopMode_level1Mask;
DETAILS
See '
level4Mask' for details.
config LoggerStopMode_level2Mask // module-wide |
|
Mask of diags categories whose initial filtering level is Diags.LEVEL2
extern const Diags_Mask LoggerStopMode_level2Mask;
DETAILS
See '
level4Mask' for details.
config LoggerStopMode_level3Mask // module-wide |
|
Mask of diags categories whose initial filtering level is Diags.LEVEL3
extern const Diags_Mask LoggerStopMode_level3Mask;
DETAILS
See '
level4Mask' for details.
config LoggerStopMode_level4Mask // module-wide |
|
Mask of diags categories whose initial filtering level is Diags.LEVEL4
extern const Diags_Mask LoggerStopMode_level4Mask;
DETAILS
If 'filterByLevel' is true, then all LoggerBuf instances will filter
incoming events based on their event level.
The LoggerStopMode module allows for specifying a different filter level
for every Diags bit. These filtering levels are module wide; LoggerBuf
does not support specifying the levels on a per-instance basis.
The setFilterLevel API can be used to change the filtering levels at
runtime.
The default filtering levels are assigned using the 'level1Mask' -
'level4Mask' config parameters. These are used to specify, for each of
the four event levels, the set of bits which should filter at that
level by default.
The default filtering configuration sets the filter level to
Diags.LEVEL4 for all logging-related diags bits so that all events are
logged by default.
config LoggerStopMode_numCores // module-wide |
|
Number of C6X cores running the same image with an instance in shared memory
extern const Int LoggerStopMode_numCores;
DETAILS
A common use case is to have the same binary image (e.g. .out file)
run on multiple cores of multi-core device. This causes a problem if the
logger's buffer is in shared memory (e.g. DDR). Since the image is the
same for all the cores, each core will attempt to write to the same
buffer in the shared memory. To avoid this, either place the logger's
buffers in non-shared memory, or set the numCores parameter to
the number of cores on the device.
Note: Use the
bufSection along with the Program.sectMap to
place a logger instance's buffer into specific memory.
Setting numCores to a value greater than 1 signals LoggerStopMode to
statically set aside additional memory ((x numCores) to allow each
core to have
bufSize amount of memory.
Warning: Setting this parameter to a value greater than one should only
be done when there is a single image used on multiple cores of a
multi-core device AND the logger instance's buffer is in shared memory.
While functionally it will still work, memory will be wasted if both
these conditions are not met.
The default is 1, which means do not reserve any additional memory
for the logger.
config LoggerStopMode_supportLoggerDisable // module-wide |
|
Allow LoggerStopMode instances to be enabled/disabled during runtime
extern const Bool LoggerStopMode_supportLoggerDisable;
DETAILS
Setting supportLoggerDisable to true will increase the
LoggerStopMode footprint.
Module-Wide Built-Ins |
|
// Get this module's unique id
Bool LoggerStopMode_Module_startupDone();
// Test if this module has completed startup
// The heap from which this module allocates memory
Bool LoggerStopMode_Module_hasMask();
// Test whether this module has a diagnostics mask
Bits16 LoggerStopMode_Module_getMask();
// Returns the diagnostics mask for this module
Void LoggerStopMode_Module_setMask(Bits16 mask);
// Set the diagnostics mask for this module
Instance Object Types |
|
typedef struct LoggerStopMode_Object LoggerStopMode_Object;
// Opaque internal representation of an instance object
// Client reference to an instance object
typedef struct LoggerStopMode_Struct LoggerStopMode_Struct;
// Opaque client structure large enough to hold an instance object
// Convert this instance structure pointer into an instance handle
// Convert this instance handle into an instance structure pointer
Instance Config Parameters |
|
typedef struct LoggerStopMode_Params {
// Instance config-params structure
// Common per-instance configs
SizeT bufSize;
// LoggerStopMode instance's buffer size in MAUs (Minimum Addressable
Units e.g. Bytes)
Int16 instanceId;
// Unique id of the LoggerStopMode instance
SizeT maxEventSize;
// The maximum event size (in Maus) that can be written with a single
event. Must be less than or equal to bufSize - 64
//
} LoggerStopMode_Params;
// Initialize this config-params structure with supplier-specified defaults before instance creation
config LoggerStopMode_Params.bufSize // instance |
|
LoggerStopMode instance's buffer size in MAUs (Minimum Addressable
Units e.g. Bytes)
DETAILS
NOTE: the buffer size must contain an integer number of 32-bit words
(e.g. if a MAU = 1 byte, then the buffer size must be a multiple of 4).
The buffer size must also be at least maxEventSize + 64.
config LoggerStopMode_Params.instanceId // instance |
|
Unique id of the LoggerStopMode instance
config LoggerStopMode_Params.maxEventSize // instance |
|
The maximum event size (in Maus) that can be written with a single
event. Must be less than or equal to bufSize - 64
DETAILS
The writeMemoryRange API checks to see if the event size required to
write the block of memory is larger than maxEventSize. If so, it will
split the memory range up into a number of smaller blocks and log the
blocks using separate events with a common snapshot ID in order to
allow the events to be collated and the original memory block to be
reconstructed on the host.
config LoggerStopMode_Params.transferType // instance |
|
Runtime Instance Creation |
|
// Allocate and initialize a new instance object and return its handle
// Initialize a new instance object inside the provided structure
ARGUMENTS
params
per-instance config params, or NULL to select default values (target-domain only)
eb
active error-handling block, or NULL to select default policy (target-domain only)
Instance Deletion |
|
// Finalize and free this previously allocated instance object, setting the referenced handle to NULL
// Finalize the instance object inside the provided structure
LoggerStopMode_disable() // instance |
|
Disable a log
ARGUMENTS
handle
handle of a previously-created LoggerStopMode instance object
DETAILS
Events written to a disabled log are silently discarded.
RETURNS
The function returns the state of the log (TRUE if enabled,
FALSE if disabled) before the call. This return value allows
clients to restore the previous state.
Note: not thread safe.
LoggerStopMode_enable() // instance |
|
Enable a log
ARGUMENTS
handle
handle of a previously-created LoggerStopMode instance object
RETURNS
The function returns the state of the log (TRUE if enabled,
FALSE if disabled) before the call. This return value allows
clients to restore the previous state.
Note: not thread safe.
LoggerStopMode_flush() // instance |
|
Reset the logger's write pointer back to the beginning of the buffer
ARGUMENTS
handle
handle of a previously-created LoggerStopMode instance object
LoggerStopMode_getBufSize() // instance |
|
Returns the Log's configured buffer size
ARGUMENTS
handle
handle of a previously-created LoggerStopMode instance object
RETURNS
Log's configured buffer size.
LoggerStopMode_getContents() // instance |
|
Fills buffer that is passed in with unread data, up to size bytes
in length
ARGUMENTS
handle
handle of a previously-created LoggerStopMode instance object
hdrBuf
Ptr to a buffer that is at least <size> bytes in length
size
The max number of bytes to be read into the buffer
cpSize
The number of bytes actually copied
DETAILS
The logger is responsible for ensuring that no partial event records
are stored in the buffer. Bytes are in target endianness.
RETURN
returns false if logger has no more records to read
LoggerStopMode_getFilterLevel() // instance |
|
Returns the mask of diags categories currently set to the specified
level
ARGUMENTS
handle
handle of a previously-created LoggerStopMode instance object
DETAILS
See '
setFilterLevel' for an explanation of level filtering.
See '
setFilterLevel' for an explanation of level filtering.
LoggerStopMode_getInstanceId() // instance |
|
Returns an ID value that uniquely identifies this instance of the logger
ARGUMENTS
handle
handle of a previously-created LoggerStopMode instance object
DETAILS
Note that a value of 0 is reserved to indicate that the instance ID has
not been initialized yet and a unique value needs to be generated.
LoggerStopMode_getMaxLength() // instance |
|
ARGUMENTS
handle
handle of a previously-created LoggerStopMode instance object
LoggerStopMode_getTransferType() // instance |
|
ARGUMENTS
handle
handle of a previously-created LoggerStopMode instance object
LoggerStopMode_isEmpty() // instance |
|
Returns true if the transfer buffer has no unread data
ARGUMENTS
handle
handle of a previously-created LoggerStopMode instance object
RETURN
true if no unread data
LoggerStopMode_reset() // instance |
|
Reset a log to empty state and enable it
ARGUMENTS
handle
handle of a previously-created LoggerStopMode instance object
WARNING
This method is not synchronized with other instance
methods and, as a result, it must never be called when there is a
chance that another instance method is currently in operation or
when another method on this instance may preempt this call.
LoggerStopMode_setFilterLevel() // instance |
|
Sets the level of detail that instances will log
ARGUMENTS
handle
handle of a previously-created LoggerStopMode instance object
mask
The diags categories to set the level for
The diags categories to set the level for
filterLevel
The new filtering level for the specified
categories
The new filtering level for the specified
categories
DETAILS
Events with the specified level or higher will be logged, events
below the specified level will be dropped.
Events are filtered first by diags category, then by level. If an
event's diags category is disabled in the module's diags mask, then it
will be filtered out regardless of level. The event will not even be
passed to the logger.
This API allows for setting the filtering level for more than one
diags category at a time. The mask parameter can be a single category
or multiple categories combined, and the level will be set for all of
those categories.
Events with the specified level or higher will be logged, events
below the specified level will be dropped.
Events are filtered first by diags category, then by level. If an
event's diags category is disabled in the module's diags mask, then it
will be filtered out regardless of level. The event will not even be
passed to the logger.
This API allows for setting the filtering level for more than one
diags category at a time. The mask parameter can be a single category
or multiple categories combined, and the level will be set for all of
those categories.
LoggerStopMode_write0() // instance |
|
Process a log event with 0 arguments
ARGUMENTS
handle
handle of a previously-created LoggerStopMode instance object
DETAILS
Same as write4 except with 0 arguments rather than 4.
SEE
LoggerStopMode_write1() // instance |
|
Process a log event with 1 argument
ARGUMENTS
handle
handle of a previously-created LoggerStopMode instance object
DETAILS
Same as write4 except with 1 arguments rather than 4.
SEE
LoggerStopMode_write2() // instance |
|
Process a log event with 2 arguments
ARGUMENTS
handle
handle of a previously-created LoggerStopMode instance object
DETAILS
Same as write4 except with 2 arguments rather than 4.
SEE
LoggerStopMode_write4() // instance |
|
Process a log event with 4 arguments
ARGUMENTS
handle
handle of a previously-created LoggerStopMode instance object
evt
event to be logged
mid
module ID of the module which logged the event
a1
arbitrary argument passed by caller
DETAILS
The
evt argument is of type Log.Event, which encodes the
Log.EventId, the
Diags.Mask, and the
Diags.EventLevel of the event. The event ID can be obtained
via
Types.getEventId(evt), the Diags mask can be obtained via
Diags.getMask(evt), and the event level can be obtained via
Diags.getLevel(evt).
The modId argument is the module ID of the module that logged the
event.
The event information can be used by the logger to handle different
events specially. For example, the event ID can be used to compare
against other known Log.Events.
if (Log_getEventId(MY_EVENT) == Log_getEventId(evt)) {
:
}
The Diags mask and event level can be used for filtering of events
based on event level (see
IFilterLogger), or even routing
events to separate loggers based on diags category (see, for example,
LoggerBuf.statusLogger).
The Diags mask and event level are useful for handling the event, but
are generally not recorded by the logger because they are not needed in
decoding and displaying the event. A more suitable value to record is a
Types.Event, which encodes the event ID and module ID. For
example, the
Log.EventRec type stores a
Types.Event
in its record definition. A
Types.Event can be created using
the
Types.makeEvent API given the event ID and module ID.
The event ID value of
0 is used to indicate an event triggered by a
call to one of the
Log_print[0-6] methods. These
methods take a format string rather than a
Log_Event argument and,
as a result, the event ID encoded in
evt is
0 and the parameter
a1 is the format string.
Non-zero event IDs can also be used to access the
msg string
associated with the
Log.EventDesc that originally
defined the
Log event.
Log_EventId id = Log_getEventId(evt));
if (id != 0) {
String msg = Text_ropeText(id);
System_aprintf(msg, a1, a2, a3, a4);
}
This works because an event's ID is simply an offset into a table
of characters (maintained by the
Text module)
containing the event's msg string.
The arguments a1, a2, etc. are parameters that are to be interpreted
according to the message format string associated with evt.
SEE
LoggerStopMode_write8() // instance |
|
Process a log event with 8 arguments
Void LoggerStopMode_write8(
LoggerStopMode_Handle handle,
Log_Event evt,
Types_ModuleId mid,
IArg a1,
IArg a2,
IArg a3,
IArg a4,
IArg a5,
IArg a6,
IArg a7,
IArg a8);
ARGUMENTS
handle
handle of a previously-created LoggerStopMode instance object
DETAILS
Same as write4 except with 8 arguments rather than 4.
SEE
LoggerStopMode_writeMemoryRange() // instance |
|
Log an event along with values from a range of memory addresses
ARGUMENTS
handle
handle of a previously-created LoggerStopMode instance object
evt
event to be logged
snapshotId
0 = no other snapshot groups, Use value from
LogSnapshot.getSnapshotId() for all snapshots to be grouped.
fileName
__FILE__ result
lineNum
__LINE__ result
fmt
a printf style format string
startAdrs
value for first format conversion character
lengthInMAUs
value for second format conversion character
DETAILS
If the mask in the specified LogSnapshot event has any bit set which is
also set in the current module's diagnostics mask, then this call to
write will "raise" the given LogSnapshot event.
Note that this API supports null terminated strings, arrays of characters and
memory mapped registgers as well as blocks of memory. The LogSnapshot module provides macros that
map the appropriate values to the writeMemoryRange API's arguments
SEE
Instance Convertors |
|
// unconditionally move one level up the inheritance hierarchy
// conditionally move one level down the inheritance hierarchy; NULL upon failure
// unconditionally move 2 levels up the inheritance hierarchy
// conditionally move 2 levels down the inheritance hierarchy; NULL upon failure
// unconditionally move 3 levels up the inheritance hierarchy
// conditionally move 3 levels down the inheritance hierarchy; NULL upon failure
// unconditionally move 4 levels up the inheritance hierarchy
// conditionally move 4 levels down the inheritance hierarchy; NULL upon failure
Instance Built-Ins |
|
Int LoggerStopMode_Object_count();
// The number of statically-created instance objects
// The handle of the i-th statically-created instance object (array == NULL)
// The handle of the first dynamically-created instance object, or NULL
// The handle of the next dynamically-created instance object, or NULL
// The heap used to allocate dynamically-created instance objects
// The label associated with this instance object
// The name of this instance object
enum LoggerStopMode.TransferType |
|
values of type LoggerStopMode.TransferType
const LoggerStopMode.TransferType_RELIABLE;
const LoggerStopMode.TransferType_LOSSY;
C SYNOPSIS
metaonly struct LoggerStopMode.MetaData |
|
This data is added to the RTA MetaData file to support stop mode RTA
var obj = new LoggerStopMode.MetaData;
obj.instanceId = Int ...
obj.priority = Int ...
metaonly struct LoggerStopMode.RecordView |
|
var obj = new LoggerStopMode.RecordView;
obj.sequence = Int ...
obj.timestampRaw = Long ...
obj.modName = String ...
obj.text = String ...
obj.eventId = Int ...
obj.eventName = String ...
obj.arg0 = IArg ...
obj.arg1 = IArg ...
obj.arg2 = IArg ...
obj.arg3 = IArg ...
obj.arg4 = IArg ...
obj.arg5 = IArg ...
obj.arg6 = IArg ...
obj.arg7 = IArg ...
metaonly struct LoggerStopMode.RtaData |
|
Data added to the RTA MetaData file to support System Analyzer
var obj = new LoggerStopMode.RtaData;
obj.instanceId = Int ...
config LoggerStopMode.filterByLevel // module-wide |
|
Support filtering of events by event level
LoggerStopMode.filterByLevel = Bool false;
DETAILS
To improve logging performance, this feature can be disabled by setting
filterByLevel to false.
See '
setFilterLevel' for an explanation of level filtering.
C SYNOPSIS
config LoggerStopMode.isTimestampEnabled // module-wide |
|
Enable or disable logging the 64-bit local CPU timestamp
at the start of each event
LoggerStopMode.isTimestampEnabled = Bool true;
DETAILS
Having a timestamp allows an instrumentation host (e.g.
System Analyzer) to display events with the correct system time.
C SYNOPSIS
config LoggerStopMode.level1Mask // module-wide |
|
Mask of diags categories whose initial filtering level is Diags.LEVEL1
LoggerStopMode.level1Mask = Bits16 0;
DETAILS
See '
level4Mask' for details.
C SYNOPSIS
config LoggerStopMode.level2Mask // module-wide |
|
Mask of diags categories whose initial filtering level is Diags.LEVEL2
LoggerStopMode.level2Mask = Bits16 0;
DETAILS
See '
level4Mask' for details.
C SYNOPSIS
config LoggerStopMode.level3Mask // module-wide |
|
Mask of diags categories whose initial filtering level is Diags.LEVEL3
LoggerStopMode.level3Mask = Bits16 0;
DETAILS
See '
level4Mask' for details.
C SYNOPSIS
config LoggerStopMode.level4Mask // module-wide |
|
Mask of diags categories whose initial filtering level is Diags.LEVEL4
DETAILS
If 'filterByLevel' is true, then all LoggerBuf instances will filter
incoming events based on their event level.
The LoggerStopMode module allows for specifying a different filter level
for every Diags bit. These filtering levels are module wide; LoggerBuf
does not support specifying the levels on a per-instance basis.
The setFilterLevel API can be used to change the filtering levels at
runtime.
The default filtering levels are assigned using the 'level1Mask' -
'level4Mask' config parameters. These are used to specify, for each of
the four event levels, the set of bits which should filter at that
level by default.
The default filtering configuration sets the filter level to
Diags.LEVEL4 for all logging-related diags bits so that all events are
logged by default.
C SYNOPSIS
config LoggerStopMode.numCores // module-wide |
|
Number of C6X cores running the same image with an instance in shared memory
LoggerStopMode.numCores = Int 1;
DETAILS
A common use case is to have the same binary image (e.g. .out file)
run on multiple cores of multi-core device. This causes a problem if the
logger's buffer is in shared memory (e.g. DDR). Since the image is the
same for all the cores, each core will attempt to write to the same
buffer in the shared memory. To avoid this, either place the logger's
buffers in non-shared memory, or set the numCores parameter to
the number of cores on the device.
Note: Use the
bufSection along with the Program.sectMap to
place a logger instance's buffer into specific memory.
Setting numCores to a value greater than 1 signals LoggerStopMode to
statically set aside additional memory ((x numCores) to allow each
core to have
bufSize amount of memory.
Warning: Setting this parameter to a value greater than one should only
be done when there is a single image used on multiple cores of a
multi-core device AND the logger instance's buffer is in shared memory.
While functionally it will still work, memory will be wasted if both
these conditions are not met.
The default is 1, which means do not reserve any additional memory
for the logger.
C SYNOPSIS
config LoggerStopMode.supportLoggerDisable // module-wide |
|
Allow LoggerStopMode instances to be enabled/disabled during runtime
LoggerStopMode.supportLoggerDisable = Bool false;
DETAILS
Setting supportLoggerDisable to true will increase the
LoggerStopMode footprint.
C SYNOPSIS
metaonly config LoggerStopMode.cacheLineSizeInMAUs // module-wide |
|
LoggerStopMode.cacheLineSizeInMAUs = Int 128;
metaonly config LoggerStopMode.common$ // module-wide |
|
Common module configuration parameters
DETAILS
All modules have this configuration parameter. Its name
contains the '$' character to ensure it does not conflict with
configuration parameters declared by the module. This allows
new configuration parameters to be added in the future without
any chance of breaking existing modules.
metaonly LoggerStopMode.getLoggerInstanceId() // module-wide |
|
returns the id of this logger instance
LoggerStopMode.getLoggerInstanceId(Any inst) returns Any
metaonly LoggerStopMode.getMetaArgs() // module-wide |
|
Returns any meta data needed to support RTA
LoggerStopMode.getMetaArgs(Any inst, Any instNum) returns Any
DETAILS
This meta data should be returned in the form of a structure which
can be converted into XML. This data is added to the RTA XML file
during the application's configuration, and can be accessed later
through the xdc.rta.MetaData module.
The MetaData is returned per instance of the ILogger module. The
instance object is passed to the function as the first argument.
The second argument is the index of the instance in the list of
the ILogger's static instances.
metaonly LoggerStopMode.getNumInstances() // module-wide |
|
LoggerStopMode.getNumInstances() returns Int
metaonly LoggerStopMode.getPtrToQueueDescriptorMeta() // module-wide |
|
Each logger instance has a unique queue descriptor address that is
stored in the Event Record header to identify itself to the host.
This metaonly configuration parameter allows the UIA Metadata to
determine what the address is for each statically created logger instance
in order to emit XML code to allow the host to look up information about
the logger instance (such as its name) based on the queue descriptor
address that is stored in the event record header
LoggerStopMode.getPtrToQueueDescriptorMeta(Any inst) returns Any
DETAILS
The pointer is returned per instance of the logger module. The
instance object is passed to the function as the first argument.
metaonly LoggerStopMode.setPtrToQueueDescriptorMeta() // module-wide |
|
Sets the queue descriptor address in the logger's object instance data
LoggerStopMode.setPtrToQueueDescriptorMeta(Any inst, Any queueDescriptorAdrs) returns Any
Instance Config Parameters |
|
var params = new LoggerStopMode.Params;
// Instance config-params object
params.bufSection = String null;
// Section name for the buffer managed by the static instance
params.bufSize = SizeT 1400;
// LoggerStopMode instance's buffer size in MAUs (Minimum Addressable
Units e.g. Bytes)
params.instanceId = Int16 1;
// Unique id of the LoggerStopMode instance
params.maxEventSize = SizeT 512;
// The maximum event size (in Maus) that can be written with a single
event. Must be less than or equal to bufSize - 64
params.ptrToQueueDescriptorMeta = Ptr null;
//
//
config LoggerStopMode.Params.bufSize // instance |
|
LoggerStopMode instance's buffer size in MAUs (Minimum Addressable
Units e.g. Bytes)
var params = new LoggerStopMode.Params;
...
params.bufSize = SizeT 1400;
DETAILS
NOTE: the buffer size must contain an integer number of 32-bit words
(e.g. if a MAU = 1 byte, then the buffer size must be a multiple of 4).
The buffer size must also be at least maxEventSize + 64.
C SYNOPSIS
config LoggerStopMode.Params.instanceId // instance |
|
Unique id of the LoggerStopMode instance
var params = new LoggerStopMode.Params;
...
params.instanceId = Int16 1;
C SYNOPSIS
config LoggerStopMode.Params.maxEventSize // instance |
|
The maximum event size (in Maus) that can be written with a single
event. Must be less than or equal to bufSize - 64
var params = new LoggerStopMode.Params;
...
params.maxEventSize = SizeT 512;
DETAILS
The writeMemoryRange API checks to see if the event size required to
write the block of memory is larger than maxEventSize. If so, it will
split the memory range up into a number of smaller blocks and log the
blocks using separate events with a common snapshot ID in order to
allow the events to be collated and the original memory block to be
reconstructed on the host.
C SYNOPSIS
config LoggerStopMode.Params.transferType // instance |
|
var params = new LoggerStopMode.Params;
...
C SYNOPSIS
metaonly config LoggerStopMode.Params.bufSection // instance |
|
Section name for the buffer managed by the static instance
var params = new LoggerStopMode.Params;
...
params.bufSection = String null;
DETAILS
The default section is the 'dataMemory' in the platform.
metaonly config LoggerStopMode.Params.ptrToQueueDescriptorMeta // instance |
|
var params = new LoggerStopMode.Params;
...
params.ptrToQueueDescriptorMeta = Ptr null;
Static Instance Creation |
|
var params =
new LoggerStopMode.
Params;
// Allocate instance config-params
params.config = ...
// Assign individual configs
var inst = LoggerStopMode.create(params);
// Create an instance-object
ARGUMENTS
params
per-instance config params, or NULL to select default values (target-domain only)
eb
active error-handling block, or NULL to select default policy (target-domain only)