SK70720 and SK70721 — Multi-Rate DSL Data Pump Chip Set
24 Datasheet
Both transceivers require a VCXO crystal frequency of:
fxtal = 32 (line_rate).
3.4.4 Data Interface Timing
The MDSL data interface provides for the transfer of binary data to and from the transceiver using
the 272 to 784 kHz clock, BIT_CK, generated by data pump. Figure 9 shows the timing for the data
interface. In the receive direction, the binary data output on RDATA contains the 14-bit frame sync
word (b1-b14), the transparent payload data (b15-b4702) and optional stuff bits (b4703-b4706).
During the activation process, RDATA is held High until ACTIVE goes Low to indicate link
activation has been completed and recovered data is available. The data strobe signal RDATA_ST
is High during the frame sync word and stuff bits and Low during payload data. RDATA_ST can be
used to create a gapped receive payload data clock by suppressing BIT_CK cycles when
RDATA_ST is High. RFP is the receive frame sync output that goes Low during the first bit of
every MDSL frame. In variable data rate applications the original data timing can be recovered
from RFP using a synthesizer PLL.
In the transmit direction, payload data is sampled from TDATA during bits b15-b4702 of each
frame. Frame sync word bits (b1-b14) are internally generated in the MDSP and not sampled from
TDATA, so any data supplied during b1-b14 is ignored. During the activation process, transmit
data is internally generated by the MDSP and TDATA is not sampled until ACTIVE goes Low to
indicate link activation has been completed. For fixed data rate applications an external counter is
used to generate a one BIT_CK cycle long Low pulse for the TFP input. This frame sync pulse
establishes the start of an MDSL frame and is needed to establish a gap in the payload data during
the time the data pump internally generates the frame sync word. In variable rate applications
stuffing control logic adjusts the time between TFP pulses to match the average data rate
transmitted by the data pump to the rate at which it is supplied by the external source. In both cases,
the TFP signal should be valid prior to an activation request for the Master Data Pump. A valid
TFP signal should be generated after power-up, before or immediately after LOS goes Low for the
Slave Data Pump. During initialization and anytime thereafter TFP must not be held low for more
than 2 BIT_CK cycles or the data interface output signals will be disabled. Also, if the TFP signal
is inactive (always High or unconnected) when activation starts, then the Data Pump may activate
but will inject stuff bits in the TDATA stream in every other frame and sync bits in every frame.
Since the Data Pump will not be synchronized to the data source these internally generated bits will
overwrite payload data. If the phase of TFP jumps the Data Pump will immediately reset the
transmit frame alignment, typically causing loss of alignment at the other end.
3.4.5 Loopbacks
The data pump provides data loopbacks toward the line and toward the digital interface. Front End
Loopback (FELB) is the loopback toward the digital interface inside the IAFE and is available only
in Master mode. FELB is initiated by bringing the FELB and ACTREQ signals High in hardware
mode, or by setting the FELB and ACTREQ bits to 1 in the processor control mode. In FELB the
data pump receiver activates with its own transmit data and ignores a signal at the IAFE receiver
analog line interface. Data is transmitted on the line during FELB.
Back End Loopback (BELB) is a data loopback toward the analog line interface inside the MDSP.
BELB is available in both Master and Slave modes after activation is complete. BELB is initiated
by bringing the BELB signal High in hardware mode, or by setting the BELB bit to 1 in the
processor control mode. In BELB the data pump receive data and frame pulse signals are supplied
to the transmitter which ignores the TDATA and TFP inputs. Receive Data is output on RDATA
during BELB.