Examples - Analog Devices VisualDSP++ 5.0 Service Manual

functions may modify the
manipulation functions. Regardless of how the
IMASK
changed, the interrupt manager API provides a uniform and consistent
mechanism for this.
Two operating environment implementation-dependent functions are
provided to set and clear bits in the
and
adi_int_ClearIMASKBits
that corresponds to the
adi_int_SetIMASKBits()
bits in the
IMASK
the value passed in. When the
called, the function clears those bits (to 0) in the
1 in the corresponding bit position of the value passed in.
Consider the following example code. Assume that
and contains
0x00000000
...
...
ReturnCode = adi_int_SetIMASKBits(0x00000003);
...
ReturnCode = adi_int_ClearIMASKBits(0x00000001);
...
ReturnCode = adi_int_ClearIMASKBits(0x00000002);
...
While it is very unlikely that the application will ever need to control
individual
IMASK
control the CEC.

Examples

Examples demonstrating use of the interrupt manager can be found in the
Blackfin/EZ-Kits
VisualDSP++ 5.0 Device Drivers and System
Services Manual for Blackfin Processors
value directly, or use the RTOS-provided
IMASK
. These functions take as a parameter a value
register of the targeted processor. When the
IMASK
function is called, the function sets to 1 those
register that have a 1 in the corresponding bit position of
adi_int_ClearIMASKBits()
upon entry into the code:
// IMASK = 0x00000000
// IMASK now equals 0x00000003
// IMASK now equals 0x00000002
// IMASK now equals 0x00000000
bit values, the interrupt manager uses these functions to
subdirectories.
Interrupt Manager
register:
IMASK adi_int_SetIMASKBits
IMASK
IMASK
value is
IMASK
function is
register that have a
is a 32-bit value
2-15