
PEB 20321
PEF 20321
Host Memory Organization
Data Sheet
306
2001-02-14
For a description of the complete polling process of the MUNICH32X refer to
the descriptions of MODE2 and TXPOLL registers.
Host initiated interrupt; if the HI bit is set, MUNICH32X generates an interrupt
with set HI bit after receiving all data bytes.
This defines the byte size of the receive data section allocated by the host.
Because MUNICH32X always writes DWORDs the number of bytes (data
section size) must be a multiple of 4 and greater or equal to 4. The maximum
data section size is 8188 bytes.
After reception of an HDLC frame with a data byte number not divisible by 4
the MUNICH32X first transfers the greatest entire (number of data bytes/4) in
DWORDs. Then the remainder of the data bytes is transferred in another
DWORD, where the non-significant bytes are filled with random values. They
should not be interpreted.
For example a HDLC frame with one data byte is received:
HI:
NO:
Rx Descriptor
The data bytes are stored in the Rx data section in little endian format .
Frame End: The frame end bit is set to
‘
1
’
only in HDLC, TMB, TMR mode and
indicates that a receive frame has ended in this Rx descriptor. For TMA and
V.110/X.30 the bit is always
‘
0
’
.
FE =
‘
0
’
in HDLC, TMB, TMR mode means that frame continues in the next
Rx descriptor or that it filled the current receive data section exactly
(BNO = NO). In this case, the next Rx descriptor will have FE =
‘
1
’
, C =
‘
1
’
,
BNO =
‘
0
’
, and no data bytes are stored in the corresponding data section.
Note: For LBI FE is set to
‘
1
’
in general, since only HDLC is supported.
FE:
00000000.00001000.00000000.00000
Next Rx Descriptor Pointer
Rx Data Pointer
11000000.00000001.Status.00000000
XX.XX.XX.data
Rx Data Section