T7115AMCDT LSI, T7115AMCDT Datasheet - Page 63
![no-image](/images/manufacturer_photos/0/4/400/lsi_sml.jpg)
T7115AMCDT
Manufacturer Part Number
T7115AMCDT
Description
Manufacturer
LSI
Datasheet
1.T7115AMCDT.pdf
(68 pages)
Specifications of T7115AMCDT
Package Type
PLCC
Lead Free Status / Rohs Status
Not Compliant
Data Sheet
April 1997
Appendix
This Appendix is intended to answer questions that
may arise when using the T7121 HDLC Interface for
ISDN. These questions have been compiled from cus-
tomer inquiries.
The questions and answers are divided into four
operational categories: transparent mode, HDLC
mode, general features, and power and ground.
Transparent Mode
Q1: Since there is no interrupt due to a MATCH, how
A1: Initially, the receive threshold should be set to 1.
Q2: In transparent mode, the transmit idle character
A2: Yes, this is normal operation. Although end-of-
Q3: In the transparent mode, what does a TDONE
A3: It means the transmit FIFO is empty. If the FIFO
Lucent Technologies Inc.
can a MATCH be detected as soon as one
occurs?
An interrupt will then occur on the first data byte
after the MATCH. Next, the MATCH status should
be read and a determination made as to whether
the application requires a threshold other than 1;
if it does, the threshold should be changed
accordingly.
(TIC0—TIC7, AR13) and the receiver match
character (RMC0—RMC7, AR12) are set to the
same value and local loopback is enabled
(LLOOP, R6, b1 = 1). After enabling the transmit-
ter and receiver, the interrupt for receiver over-
runs occurs, and the receive FIFO is full of match
characters (as expected). The end-of-frame bit
(EOF, R4, b7) is also set. Is this normal?
frame has no meaning in transparent mode, the
EOF bit acts as another indication that the
receiver has been overrun.
(R15, bit 0) of 1 mean?
is empty in the transparent mode configuration, a
TDONE interrupt will immediately occur, along
with a TE interrupt, even before enabling the
transmitter.
HDLC Mode
Q4: If the transmit FIFO is loaded and then enabled,
A4: As soon as the FIFO is loaded, the data is
Q5: When using the first solution described for Q4,
A5: One-byte frames may not be sent properly
Q6: Can the T7121 recognize the shared flag
A6: Yes, this is considered normal operation.
Q7: Regarding the EOF status byte, when the bad
A7: CRC bits are checked on a bit-per-bit basis.
T7121 HDLC Interface for ISDN (HIFI-64)
There are two solutions. The first one is to enable
The second solution is to set the idle character to
information is sometimes lost (in the HDLC
mode), is there an explanation for this?
prepared for HDLC transmission. If the micropro-
cessor (which is asynchronous with the highway)
turns on the transmitter at the wrong time relative
to the frame sync, then the first byte is missed.
The first byte is the open flag, so the first frame of
HDLC data is lost.
the transmitter and then load the FIFO. As long
as the FIFO is loaded faster than data can be
sent out, the system will operate without any
abort interrupts.
look like an open flag, then load the FIFO, and
then enable the transmitter; this means there is
always going to be an open flag. If the idle char-
acter is then changed to all 1s before the FIFO is
empty, all subsequent frames will have the open
flag, as expected, and all 1s will be sent as idle.
1-byte frames cannot always be sent; why?
because data may be sent before the close infor-
mation register can be written—if the transmitter
is enabled when the FIFO is written, data may be
sent as soon as the FIFO is written—resulting in
a transmit abort. However, in a real HDLC
environment, address information plus data usu-
ally prevents the problem from occurring.
between consecutive frames? In other words,
can the closing flag of the first frame be the open-
ing flag of the second frame, i.e., Flag Data1
CRC CRC Flag Data2 . . . .
byte count bit (bit 4) is activated (high), does the
bad CRC bit (bit 7) also activate?
Therefore, it is possible, but very unlikely, that a
bad byte count could occur without a bad CRC
indication.
63