
Reference Manual AFDX / ARINC 664 Application Interface Library
71
Section 4 – Function Reference: Transmitter Functions
A
A
i
i
U
U
I
I
n
n
t
t
8
8
u
u
c
c
_
_
P
P
a
a
y
y
l
l
o
o
a
a
d
d
G
G
e
e
n
n
e
e
r
r
a
a
t
t
i
i
o
o
n
n
M
M
o
o
d
d
e
e
The Payload Generation Mode (PGM) defines, which contents of the frame data are
automatically generated by the MAC- Hardware out of the static Tx data registers (see
Command
FdxCmdTxStaticRegsControl
). The payload generation mode is based on
the UDP- protocol within the frame. Therefore, if one of the data reduction modes is
selected, the transmit frame must include an UDP- protocol type.
Value:
Description:
FDX_TX_FRAME_PGM_USER
Default, no payload generation. All AFDX- frame data for
transmission will be provided from this frame entry or partly
from the payload buffer queue. In this mode, all MAC-
frame data, except the FCS- field, has to be fed into the
MAC by the BIU- Processor.
Complete frame data must be provided for this frame.
FDX_TX_FRAME_PGM_IP_PART
The MAC- Destination Address Bytes 2..5, the MAC-
Source Address Bytes 3…5, the MAC- Length Type Field
Byte 0..1, the IP- Version field, the IP- Header Length field,
the IP- protocol field and the UDP- checksum field as well
as the hole UDP- payload will be generated by the MAC-
Hardware by using the Static Transmit Registers.
Only the MAC header and IP Header and UDP Header
needs to be provided as frame data for this frame.
FDX_TX_FRAME_PGM_IP_FULL
The MAC- Destination Address Bytes 2…5, the MAC-
Source Address Bytes 3…5, the MAC- Length Type Field
Byte 0...1, the IP- Version field, the hole IP- Header (20
bytes) and the hole UDP- Header as well as the hole UDP-
payload will be generated by the MAC- Hardware by using
the Static Transmit Registers.
Only the MAC header needs to be provided as frame data
for this frame.
FDX_TX_FRAME_PGM_IP_PART_TT Same
as
FDX_TX_FRAME_PGM_IP_PART, plus UDP-
payload data will be filled with the start Timetag, which is
repeated every eight bytes.
FDX_TX_FRAME_PGM_IP_FULL_TT Same
as
FDX_TX_FRAME_PGM_IP_FULL, plus UDP-
payload data will be filled with the start Timetag, which is
repeated every eight bytes.
Note:
This Static Transmit Registers must be setup properly if any frame uses a Payload Generation
Mode, different from FDX_TX_FRAME_PGM_USER ! Otherwise the frame data may be invalid.
The following Table shows the necessary size of one Queue Entry dependent on the Payload Buffer
and Payload Generation Modes.
Payload Generation Mode
Size of Queue Entry
FDX_TX_FRAME_PGM_USER
sizeof (TY_FDX_TX_FRAME_HEADER) +
uw_FrameSize
FDX_TX_FRAME_PGM_IP_PART
FDX_TX_FRAME_PGM_IP_PART_TT
sizeof (TY_FDX_TX_FRAME_HEADER) +
MAC-Header (14 Bytes) +
IP-Header (20 Bytes) +
UDP-Header (8 Bytes)
FDX_TX_FRAME_PGM_IP_FULL
FDX_TX_FRAME_PGM_IP_FULL_TT
sizeof (TY_FDX_TX_FRAME_HEADER) +
MAC-Header (14 Bytes)
Summary of Contents for AFDX / ARINC 664
Page 2: ......