MSGQ Module
2-234
❏
❏
❏
❏
A writer calls the following APIs:
❏
MSGQ_locate or MSGQ_locateAsync
❏
❏
❏
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.
Static Configuration
In order to use the MSGQ module and the allocators it depends upon,
you must statically configure the following:
❏
ENABLEMSGQ property of the MSGQ module using Tconf (see
“MSGQ Manager Properties” on page 2-238)
❏
MSGQ_config variable in application code (see below)
❏
PROCID property of the GBL module using Tconf (see “GBL Module
Properties” on page 2-109)
❏
ENABLEPOOL property of the POOL module using Tconf (see
“POOL Manager Properties” on page 2-289)
❏
POOL_config variable in application code (see “Static Configuration”
on page 2-286)
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: