Reference Manual AFDX / ARINC 664 Application Interface Library
219
Section 4 – Function Reference: Target Independent Administration Functions
4
4
.
.
5
5
.
.
5
5
F
F
d
d
x
x
P
P
r
r
o
o
c
c
e
e
s
s
s
s
M
M
o
o
n
n
Q
Q
u
u
e
e
u
u
e
e
Prototype:
AiReturn FdxProcessMonQueue (AiUInt32 ul_ReadQualifier, AiUInt32 ul_Entries, void*
pv_MonQueueData)
Driver Command
none
Purpose:
This function processes data, read via
FdxCmdMonQueueRead
in order to use the
TY_FDX_FRAME_BUFFER_HEADER
structure for access to the Frame Header Information.
The processing mainly affects platform dependent variable interpretation / structure access
(Little/Big Endian) of the Frame Header Information. Frame Data remains unchanged. This
function is typically used in conjunction with
FdxCmdMonQueueRead
function.
Note: Data, read via
FdxCmdMonQueueRead
(without processing via this function) can be
directly used for Replay via the
FdxCmdTxQueueWrite
function, if the corresponding Transmit
Port has been configured for Replay. This avoids any data processing when using previously
captured traffic for Replay.
Input:
ul_ReadQualifier
This parameter must match the
ul_ReadQualifier
parameter of previous
FdxCmdMonQueueRead
function calls, in order to tell this function which type of
Queue Data is passed via
pv_MonQueueData
parameter.
Value:
Description:
FDX_MON_READ_FULL
pv_MonQueueData
points to a sequence of one or
more Frame Data information, but only
Frame Headers are processed
FDX_MON_READ_HEADER
pv_MonQueueData
points to a sequence of one or
more Frame Header only information
ul_Entries
This parameter must match the
ul_EntryRead
parameter of previous
FdxCmdMonQueueRead
function calls, in order to tell the function how many
Entries ( Data or Header only) are passed via
pv_MonQueueData
parameter.
O
O
u
u
t
t
p
p
u
u
t
t
:
:
void *pv_MonQueueData
Processed Monitor Queue Data
Return Value
Returns FDX_OK on success or a negative error code on error.
Error Codes: FDX_ERR
