
PEB 20321
PEF 20321
Host Memory Organization
Data Sheet
314
2001-02-14
FF FF
H
for TMA, FA = 0) are sent before the following frame (non shared
flags).
FNUM = 2 means that after the current frame 3 characters (7E
H
7E
H
7E
H
(IFTF =
‘
0
’
) or 7E
H
FF
H
7E
H
(IFTF =
‘
1
’
) for HDLC and 00
H
00
H
00
H
for TMB
and TMR, TFLAG, TFLAG, TFLAG for TMA (FA =
‘
1
’
); FF FF FF
H
for TMA,
(FA = 0)) are sent.
FNUM = k means that after the current frame k + 1 characters are sent
(k + 1) times 7E
H
for ITFT =
‘
0
’
and HDLC
7E
H
, (k
–
1) times FF
H
, 7E
H
for ITFT =
‘
1
’
and HDLC
(k + 1) times 00
H
for TMB, TMR
(k + 1) times TFLAG
for TMA, FA =
‘
1
’
(k + 1) times FF
H
for TMA, FA =
‘
0
’
.
For HDLC mode, FNUM is reduced by one eighth of the number of zero
insertions, if FA is set. If the reduction would result in a negative number of
interframe time-fill characters it is programmed to
‘
0
’
.
Tx Data Pointer:
This 32-bit pointer contains the start address of the Tx data
section. Although MUNICH32X works only DWORD oriented, it
is possible to begin a Tx data section at an odd address. The two
least significant bits (ADD) of the Tx data pointer determine the
beginning of the data section and the number of data bytes in the
first DWORD of the data section, respectively.
ADD:
00 = 4 bytes
01 = 3 bytes
10 = 2 bytes
11 = 1 byte
MUNICH32X reads the first DWORD and discards the unused
least significant bytes. The NO establishes (determines) the end
of the data section, whereas the remainder of I (NO ADD)
/
4 I defines the number of bytes in the last DWORD of the data
section.
MUNICH32X reads the last DWORD and discards the unused
most significant bytes of the last DWORD.
If the first access is the same as the last access, ADD specifies
the beginning of the data section and NO the number of data
bytes in the DWORD. All unused bytes are discarded.