Texas Instruments TMS320 User Manual page 220

Message Queues
6.5.2 Static Configuration
typedef struct MSGQ_Config {
MSGQ_Obj
MSGQ_TransportObj *transports;
Uint16
Uint16
Uint16
MSGQ_Queue
Uint16
} MSGQ_Config;
Field Type
msgqQueues MSGQ_Obj *
6-18
Wherever possible, the MSGQ APIs have been written to have a
deterministic execution time. This allows application designers to be certain
that messaging will not consume an unknown number of cycles.
In addition, the MSGQ functions support use of message queues from all
types of DSP/BIOS threads: HWIs, SWIs, and TSKs. That is, calls that may
be synchronous (blocking) have an asynchronous (non-blocking) alternative.
In order to use the MSGQ module and the allocators it depends upon, you
must statically configure the following:
❏ MSGQ_config variable in application code (see below)
❏ ENABLEMSGQ property of the MSGQ module in the .tcf file
❏ PROCID property of the GBL module in the .tcf file
❏ ENABLEPOOL property of the POOL module in the .tcf file
❏ POOL_config variable in application code
See the DSP/BIOS Application Programming Interface Guide for your
platform for information about setting the properties mentioned in this list.
An application must provide a filled in MSGQ_config variable in order to use
the MSGQ module.
MSGQ_Config MSGQ_config;
The MSGQ_Config type has the following structure:
*msgqQueues;
numMsgqQueues;
numProcessors;
startUninitialized;
errorQueue;
errorPoolId;
The fields in the MSGQ_Config structure are described in the following table:
Description
Array of message queue objects. The fields of each object do
not need to be initialized.
/* Array of message queue handles */
/* Array of transports */
/* Number of message queue handles*/
/* Number of processors */
/* First msgq to init */
/* Receives async transport errors*/
/* Alloc error msgs from poolId */