XRT84L38IB [EXAR]
OCTAL T1/E1/J1 FRAMER; 八路T1 / E1 / J1成帧器型号: | XRT84L38IB |
厂家: | EXAR CORPORATION |
描述: | OCTAL T1/E1/J1 FRAMER |
文件: | 总451页 (文件大小:4397K) |
中文: | 中文翻译 | 下载: | 下载PDF数据表文档文件 |
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
FEBRUARY 2004
REV.1.0.0
and Overhead Data Input port, which permits Data
Link Terminal Equipment direct access to the out-
bound T1/E1/J1 frames Likewise, a Receive Over-
head output data port permits Data Link Terminal
Equipment direct access to the Data Link bits of the
inbound T1/E1/J1 frames.
GENERAL DESCRIPTION
The XRT84L38 is an eight-channel 1.544 Mbit/s or
2.048 Mbit/s DS1/E1/J1 framing controller. The
XRT84L38 contains an integrated DS1/E1/J1 framer
which provides DS1/E1/J1 framing and error accumu-
lation in accordance with ANSI/ITU_T specifications.
Each framer has its own framing synchronizer and
The XRT84L38 fully meets all of the latest T1/E1/J1
transmit-receive slip buffers, and can be independent- specifications: ANSI T1/E1.107-1988, ANSI T1/
ly enabled or disabled as required and can be config-
ured to frame to the common DS1/E1/J1 signal for-
mats
E1.403-1995, ANSI T1/E1.231-1993, ANSI T1/
E1.408-1990, AT&T TR 62411 (12-90) TR54016, and
ITU G-703, G.704, G706 and G.733, AT&T Pub.
43801, and ETS 300 011, 300 233, JT G.703, JT
G.704, JT G706, I.431. Extensive test and diagnostic
functions include Loop-backs, Boundary scan, Pseu-
do Random bit sequence (PRBS) test pattern gener-
ation, Performance Monitor, Bit Error Rate (BER)
meter, forced error insertion, and LAPD unchannel-
ized data payload processing according to ITU-T
standard Q.921.
Each Framer block contains its own Transmit and Re-
ceive T1/E1/J1 Framing function including 3 HDLC
controllers to support V5.2. Each Transmit HDLC
controller encapsulates contents of the Transmit
HDLC buffers into LAPD Message frames. Each Re-
ceive HDLC controller extracts payload content of Re-
ceive LAPD Message frames from the incoming T1/
E1/J1 data stream and writes it into the Receive
HDLC buffer. Each framer also contains a Transmit
Applications and Features (next page)
FIGURE 1. XRT84L38 8-CHANNEL DS1 (T1/E1/J1) FRAMER
External Data
Link Controller
8 DS1/E1
Channels
Local PCM
Tx Overhead In
Rx Overhead Out
XRT84L38
Highway
1.544/2.048 MHz
XRT83L38
1 of 8-channels
TxPOS
TxNEG
TxLineCLK 8
8
8
2-Frame
Slip Buffer
Elastic Store
Tx Encoder
LIU
Interface
TPOS
TNEG
TCLK1
8
Twisted
Pair
Tx Serial
Data In
Tx1
Rx1
Tx Framer
Rx Framer
Tx Serial
Clock
Twisted
Pair
LLB
LB
RxPOS
RxNEG
RxLineCLK 8
8
8
2-Frame
Slip Buffer
Elastic Store
Rx Encoder
LIU
Interface
RPOS
RNEG
RCLK1
8
Rx Serial
Data Out
Rx Serial
Clock
µP
Interface
HDLC (LAPD)
Controller &
96-byte Buffer
LIU &
Loopback
Control
PRBS
Generator &
Analyser
Performance
Monitor
Tx8
8kHz sync
OSC
Rx8
DMA
Interface
Microprocessor
Interface
Signaling &
Alarms
JTAG
8-CH T1/E1/LIU
Host Mode
Back Plane
1.544-16.384 Mbit/s
WR
ALE_AS
RD
4
3
Channel
Select
Interrupt
D[7:0]
A[6:0]
RDY_DTACK
Intel/Motorola µP
Configuration, Control &
Status Monitor
System (Terminal) Side
Line Side
Memory
Exar Corporation 48720 Kato Road, Fremont CA, 94538 • (510) 668-7000 • FAX (510) 668-7017 • www.exar.com
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
APPLICATIONS
• Extracts and inserts robbed bit signaling (RBS)
• High-Density T1/E1/J1 interfaces for Multiplexers,
• 3 independent HDLC Controllers for Receive and
Switches, LAN Routers and Digital Modems
Transmit on a per channel basis
• SONET/SDH terminal or Add/Drop multiplexers
• Each HDLC controller contains two 96-BYTE buff-
(ADMs)
ers
• T1/E1/J1 add/drop multiplexers (MUX)
• Timeslot assignable HDLC
• V5.1 and V5.2 Interface
• Channel Service Units (CSUs): T1/E1/J1 and Frac-
tional T1/E1/J1
•
µ
8-bit Intel/Motorola P and MIPS Power PC inter-
• Digital Access Cross-connect System (DACs)
• Digital Cross-connect Systems (DCS)
faces for configuration, control and status monitor-
ing
• Parallel search algorithm for fast frame synchroni-
zation
• Frame Relay Switches and Access Devices
(FRADS)
• Wide choice of T1 framing structures: D4, ESF,
SLC®96, TIDM and N-Frame (non-framing)
• ISDN Primary Rate Interfaces (PRA)
• PBXs and PCM channel bank
• Direct access to D and E channels for fast transmis-
sion of data link information
• T3 channelized access concentrators and M13
MUX
• PRBS and QRSS generation and detection
• Programmable Interrupt output pin
• Wireless base stations
• ATM equipment with integrated DS1 interfaces
• Multichannel DS1 Test Equipment
• T1/E1/J1 Performance Monitoring
• Voice over packet gateways
• Routers
• Supports programmed I/O, Burst and DMA modes
of Read-Write access
• Each framer block encodes and decodes the T1/
E1/J1 Frame serial data into and from the Single-
rail or Dual-rail (B8ZS) format
• Dual or single rail line side digital PCM inputs
FEATURES
• Detects and forces Red (SAI), Yellow (RAI) and
• Eight independent, full duplex DS1 Tx and Rx
Blue (AIS) Alarms
Framers
• Detects OOF, LOF, LOS errors and COFA condi-
tions
• Two 512-bit (two-frame) elastic store, PCM frame
slip buffers (FIFO) on TX and Rx provide up to
8.192 MHz asynchronous back plane connections
with jitter and wander attenuation
• Loopbacks: Local (LLB) and Line remote (LB)
• Facilitates Inverse Multiplexing for ATM
• Supports input PCM and signaling data at 1.544,
2.048, 4.096 and 8.192 Mbits. Also supports 4-
channel multiplexed 12.352/16.384 (HMVIP/H.100)
Mbit/s on the back plane bus
• Performance monitor with one second polling
• Boundary scan (IEEE 1149.1) JTAG test port
• Accepts external 8kHz Sync reference
• 3.3V CMOS operation with 5V tolerant inputs
• Programmable output clocks for Fractional T1/E1/
J1
•
°
°
388-pin BGA package with –40 C to +85 C opera-
tion
• Supports Channel Associated Signaling (CAS)
• Supports Common Channel Signalling (CCS)
• Direct Interface to Exar’s XRT83L38 (Octal) LIU
• Supports ISDN Primary Rate Interface (ISDN PRI)
signaling
ORDERING INFORMATION
PART NUMBER
PACKAGE
OPERATING TEMPERATURE RANGE
XRT84L38IB
388 Pin Plastic Ball Grid Array
-40°C to +85°C
2
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
FIGURE 2. PIN OUT OF THE XRT84L38 TOP VIEW (SEE PIN LIST FOR NAMES AND FUNCTION)
(See pin list for pin names and function)
Top View
A
26
A1
B1
AF
AE
AD
AC
AB
AA
Y
C1
D
23
D
26
D4
E1
F1
G1
H1
J1
D4
W
V
K1
L1
U
L
23
L
24
L
25
L
26
L2
L3
L4
V3
V1
V1
V1
V1
G
V3
V1
V1
V1
V1
G
V3
G
G
G
G
G
V3
G
G
G
G
G
V3
V2
V2
V2
V2
G
V3
V2
V2
V2
V2
G
T
M1
N1
P1
R1
T1
U1
V1
W1
Y1
R
P
N
M
L
T
23
T
24
T
25
T
26
T2
T3
T4
K
XRT84L38
J
H
G
F
AA
1
AB
1
E
AC
1
AC
4
AC
23
AC
26
D
AD
1
C
AE
1
B
AF
1
AF
26
A
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
3
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
TABLE OF CONTENTS
GENERAL DESCRIPTION ................................................................................................. 1
Figure 1. XRT84L38 8-channel DS1 (T1/E1/J1) Framer ................................................................... 1
APPLICATIONS .............................................................................................................................................. 2
FEATURES .................................................................................................................................................... 2
ORDERING INFORMATION ............................................................................................................... 2
Figure 2. Pin Out of the XRT84L38 Top View (see pin list for names and function) .................... 3
TABLE OF CONTENTS ....................................................................................................... I
TABLE 1: LIST BY PIN NUMBER ............................................................................................................ 16
PIN DESCRIPTIONS ........................................................................................................ 21
TRANSMIT SERIAL DATA INPUT .................................................................................................................... 21
OVERHEAD INTERFACE ............................................................................................................................... 30
RECEIVE SERIAL DATA OUTPUT .................................................................................................................. 32
RECEIVE DECODER LIU INTERFACE ............................................................................................................. 39
TRANSMIT ENCODER LIU INTERFACE ........................................................................................................... 39
TIMING ....................................................................................................................................................... 40
LIU CONTROL ............................................................................................................................................. 41
JTAG ........................................................................................................................................................ 42
MICROPROCESSOR INTERFACE .................................................................................................................... 43
GROUND PINS ............................................................................................................................................ 46
POWER SUPPLY PINS ................................................................................................................................. 46
NO CONNECT PINS ..................................................................................................................................... 47
ELECTRICAL CHARACTERISTICS ................................................................................................................... 48
ABSOLUTE MAXIMUMS ................................................................................................................................ 48
DC ELECTRICAL CHARACTERISTICS ............................................................................................................ 48
TABLE 2: XRT84L38 POWER CONSUMPTION ...................................................................................... 48
1.0 Microprocessor Interface Block ............................................................................................................ 49
TABLE 3: µC/µP SELECTION TABLE ..................................................................................................... 49
1.1 CHANNEL SELECTION WITHIN THE FRAMER ............................................................................................ 50
1.2 THE MICROPROCESSOR INTERFACE BLOCK SIGNAL ............................................................................... 50
TABLE 4: CHANNEL SELECTION ........................................................................................................... 50
Figure 3. Simplified Block Diagram of the Microprocessor Interface Block .............................. 50
TABLE 5: XRT84L38 MICROPROCESSOR INTERFACE SIGNALS THAT EXHIBIT CONSTANT ROLES IN BOTH THE
INTEL AND MOTOROLA MODES ................................................................................................ 51
1.3 INTERFACING THE XRT84L38 TO THE LOCAL µC/µP VIA THE MICROPROCESSOR INTERFACE BLOCK ....... 52
1.3.1 Interfacing the Framer to the Microprocessor over an 8 bit wide bi-directional Data Bus ......... 52
TABLE 6: INTEL MODE: MICROPROCESSOR INTERFACE SIGNALS ........................................................... 52
TABLE 7: MOTOROLA MODE: MICROPROCESSOR INTERFACE SIGNALS .................................................. 52
1.3.2 Data Access Modes .................................................................................................................. 53
Figure 4. Intel µP Interface signals during Programmed I/O Read Operation ............................ 54
Figure 5. Intel µP Interface Signals during Programmed I/O Write Operation ........................... 55
Figure 6. Motorola µP Interface signals during a Programmed I/O Read Operation ................. 56
Figure 7. Motorola µP Interface signal during Programmed I/O Write Operation ...................... 57
Figure 8. Intel µP Interface Signals, during the Initial Read Operation of a Burst Cycle .......... 58
Figure 9. Intel µP Interface Signals, during subsequent Read Operations of a Burst I/O Cycle ...
60
Figure 10. Intel µP Interface signals, during the Initial Write Operation of a Burst Cycle ........ 62
Figure 11. µP Interface Signals, during subsequent Write Operations of a Burst I/O Cycle .... 63
Figure 12. Motorola µP Interface Signals during the Initial Read Operation of a Burst Cycle . 64
Figure 13. Motorola µP Interface Signals, during subsequent Read Operations of a Burst I/O Cy-
cle ......................................................................................................................................... 65
Figure 14. Motorola µP Interface signals, during the Initial Write Operation of a Burst Cycle . 67
1.4 DMA READ/WRITE OPERATIONS ........................................................................................................... 68
I
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
Figure 15. Motorola µP Interface Signals during subsequent Write Operations of a Burst I/O Cy-
cle ......................................................................................................................................... 68
DMA-0 Write DMA Interface ............................................................................................................................. 69
1.5 MEMORY AND REGISTER MAP .............................................................................................................. 69
1.5.1 Memory Mapped I/O Indirect Addressing ................................................................................. 69
Figure 16. DMA Mode for the XRT84L38 and a Microprocessor ................................................. 69
TABLE 8: ADDRESS MAP ..................................................................................................................... 70
1.6 DESCRIPTION OF THE CONTROL REGISTERS ......................................................................................... 71
RECEIVE SUBSTITUTION SIGNALING REGISTER (RSSR) (INDIRECT ADDRESS = 0XN02H, 0XC0H - 0XD7H) 150
TABLE 9: PMON T1/E1 RECEIVE LINE CODE (BIPOLAR) VIOLATION COUNTER ................................... 175
TABLE 10: PMON T1/E1 RECEIVE LINE CODE (BIPOLAR) VIOLATION COUNTER ................................. 175
TABLE 11: PMON T1/E1 RECEIVE FRAMING ALIGNMENT BIT ERROR COUNTER ................................. 175
TABLE 12: PMON T1/E1 RECEIVE FRAMING ALIGNMENT BIT ERROR COUNTER ................................. 175
TABLE 13: PMON T1/E1 RECEIVE SEVERELY ERRORED FRAME COUNTER ........................................ 176
TABLE 14: PMON T1/E1 RECEIVE CRC-4 BLOCK ERROR COUNTER - MSB ..................................... 176
TABLE 15: PMON T1/E1 RECEIVE CRC-4 BLOCK ERROR COUNTER - LSB ...................................... 176
TABLE 16: PMON T1/E1 RECEIVE FAR-END BLOCK ERROR COUNTER - MSB .................................. 176
TABLE 17: PMON T1/E1 RECEIVE FAR END BLOCK ERROR COUNTER .............................................. 177
TABLE 18: PMON T1/E1 RECEIVE SLIP COUNTER ............................................................................ 177
TABLE 19: PMON T1/E1 RECEIVE LOSS OF FRAME COUNTER .......................................................... 177
TABLE 20: PMON T1/E1 RECEIVE CHANGE OF FRAME ALIGNMENT COUNTER ................................... 178
TABLE 21: PMON LAPD T1/E1 FRAME CHECK SEQUENCE ERROR COUNTER ................................... 178
TABLE 22: T1/E1 PRBS BIT ERROR COUNTER MSB ........................................................................ 178
TABLE 23: T1/E1 PRBS BIT ERROR COUNTER LSB ......................................................................... 179
TABLE 24: T1/E1 TRANSMIT SLIP COUNTER ...................................................................................... 179
1.7 THE INTERRUPT STRUCTURE WITHIN THE FRAMER .............................................................................. 180
TABLE 25: LIST OF THE POSSIBLE CONDITIONS THAT CAN GENERATE INTERRUPTS, IN EACH FRAMER . 180
TABLE 26: ADDRESS OF THE BLOCK INTERRUPT STATUS REGISTERS ................................................. 181
TABLE 27: BLOCK INTERRUPT STATUS REGISTER .............................................................................. 182
TABLE 28: BLOCK INTERRUPT ENABLE REGISTER ............................................................................. 183
1.7.1 Configuring the Interrupt System, at the Framer Level ........................................................... 184
TABLE 29: INTERRUPT CONTROL REGISTER ....................................................................................... 184
2.0 The E1 Framing Structure .................................................................................................................... 186
2.1 THE SINGLE E1 FRAME ...................................................................................................................... 186
Timeslot 0 ....................................................................................................................................................... 186
Timeslot 0 octets within FAS frames .............................................................................................................. 186
Figure 17. Single E1 Frame Diagram ........................................................................................... 186
TABLE 30: BIT FORMAT OF TIMESLOT 0 OCTET WITHIN A FAS E1 FRAME .......................................... 186
Bit 0—Si (International Bit) ............................................................................................................................. 187
Bit 0—Si (International Bit) ............................................................................................................................. 187
Bit 1—Fixed at “1” .......................................................................................................................................... 187
Bit 2—A (FAS Frame Yellow Alarm Bit) ......................................................................................................... 187
Bit 3 through 7—Sa4–Sa8 (National Bits) ...................................................................................................... 187
2.2 THE E1 MULTI-FRAME STRUCTURES ................................................................................................... 187
2.2.1 The CRC Multi-frame Structure .............................................................................................. 187
TABLE 31: BIT FORMAT OF TIMESLOT 0 OCTET WITHIN A NON-FAS E1 FRAME .................................. 187
2.2.2 CAS Multi-Frames and Channel Associated Signaling .......................................................... 188
TABLE 32: BIT FORMAT OF ALL TIMESLOT 0 OCTETS WITHIN A CRC MULTI-FRAME ............................ 188
Figure 18. Frame/Byte Format of the CAS Multi-Frame Structure ............................................ 189
Figure 19. E1 Frame Format ......................................................................................................... 190
3.0 The DS1 Framing Structure ................................................................................................................. 191
3.1 T1 SUPER FRAME FORMAT (SF) ........................................................................................................ 191
Figure 20. T1 Frame Format ......................................................................................................... 191
Figure 21. T1 Superframe PCM Format ....................................................................................... 192
TABLE 33: SUPERFRAME FORMAT ..................................................................................................... 192
II
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
3.2 T1 EXTENDED SUPERFRAME FORMAT ................................................................................................. 193
Figure 22. T1 Extended Superframe Format ................................................................................ 193
TABLE 34: EXTENDED SUPERFRAME FORMAT .................................................................................... 194
3.3 SLC 96 FORMAT (SLC) ...................................................................................................................... 195
TABLE 35: SLC®96 FS BIT CONTENTS ............................................................................................. 195
4.0 The DS1 Transmit Section ................................................................................................................... 196
4.1 THE DS1 TRANSMIT PAYLOAD DATA INPUT INTERFACE BLOCK ............................................................ 196
4.1.1 Description of the Transmit Payload Data Input Interface Block ............................................. 196
TRANSMIT INTERFACE CONTROL REGISTER (TICR) (INDIRECT ADDRESS = 0XN0H, 0X20H) ........................ 196
4.1.2 Brief Discussion of the Transmit Payload Data Input Interface Block Operating at 1.544Mbit/s
mode ................................................................................................................................................ 197
CLOCK SELECT REGISTER (CSR) (INDIRECT ADDRESS = 0XN0H, 0X00H) ................................................ 197
TABLE 36: SIGNALS FOR DIFFERENT TRANSMIT TIMING SOURCES ........................................................ 198
TRANSMIT INTERFACE CONTROL REGISTER (TICR) (INDIRECT ADDRESS = 0XN0H, 0X20H) ....................... 198
TABLE 37: THE TXTSB[3:0] BITS WHEN THE TRANSMIT FRACTIONAL T1 INPUT BIT IS SET TO DIFFERENT VAL-
UES ...................................................................................................................................... 199
Figure 23. Interfacing XRT84L38 to local Terminal Equipment with TxSerClk_n as Transmit Tim-
ing Source .......................................................................................................................... 200
Figure 24. Waveforms of the signals that connect the Transmit Payload Data Input Interface
block to the local Terminal Equipment with the Transmit Serial clock being the Timing
Source of the Transmit Section ....................................................................................... 201
CLOCK SELECT REGISTER (CSR) (INDIRECT ADDRESS = 0XN0H, 0X00H) ................................................ 202
Figure 25. Interfacing XRT84L38 to the local Terminal Equipment with the OSCCLK Driven Divid-
ed Clock as Transmit Timing Source .............................................................................. 203
Figure 26. Waveforms of the signals connecting the Transmit Payload Data Input Interface block
to the local Terminal Equipment with the OSCCLK Driven Divided clock as the timing
source of the Transmit Section ....................................................................................... 204
CLOCK SELECT REGISTER (CSR) (INDIRECT ADDRESS = 0XN0H, 0X00H) ................................................. 205
Figure 27. Interfacing XRT84L38 to local Terminal Equipment with Recovered Receive Line
Clock as Transmit Timing Source ................................................................................... 206
4.1.3 Brief Discussion of the Transmit High-Speed Back-Plane Interface ....................................... 207
Figure 28. Waveforms of the signals connecting the Transmit Payload Data Input Interface block
to the local Terminal Equipment with the Recovered Receive Line Clock being the timing
source of the Transmit Section ....................................................................................... 207
TRANSMIT INTERFACE CONTROL REGISTER (TICR) (INDIRECT ADDRESS = 0XN0H, 0X20H) ....................... 207
TABLE 38: TRANSMIT MULTIPLEX ENABLE BIT AND TRANSMIT INTERFACE MODE SELECT [1:0] BITS WITH THE
RESULTING TRANSMIT BACK-PLANE INTERFACE DATA RATES ................................................. 208
TRANSMIT MULTIPLEX ENABLE BIT = 0 ...................................................................................................... 208
TRANSMIT MULTIPLEX ENABLE BIT = 1 ...................................................................................................... 209
TRANSMIT INTERFACE CONTROL REGISTER (TICR) (INDIRECT ADDRESS = 0XN0H, 0X20H) ........................ 209
TABLE 39: THE MAPPING OF T1 FRAME INTO E1 FRAMING FORMAT ..................................................... 210
Figure 29. Interfacing XRT84L38 to the local Terminal Equipment using MVIP 2.048Mbit/s Data
Bus ..................................................................................................................................... 211
Figure 30. Timing Diagram of the Input Signals to the Framer when running at MVIP 2.048Mbit/s
Mode ................................................................................................................................... 211
TABLE 40: THE MAPPING OF T1 FRAME INTO E1 FRAMING FORMAT ..................................................... 212
Figure 31. Interfacing XRT84L38 to the local Terminal Equipment using 4.096Mbit/s Data Bus ..
213
Figure 32. Timing Diagram of the Input Signals to the Framer when running at 4.096Mbit/s Mode
213
TABLE 41: THE MAPPING OF T1 FRAME INTO E1 FRAMING FORMAT ..................................................... 214
Figure 33. Interfacing XRT84L38 to the Local Terminal Equipment using 8.192Mbit/s Data Bus .
215
Figure 34. Timing Diagram of the Input Signals to the Framer when running at 8.192Mbit/s Mode
III
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
215
FIRST OCTET OF 12.352MBIT/S DATA STREAM ......................................................................................... 216
SECOND OCTET OF 12.352MBIT/S DATA STREAM ..................................................................................... 216
THIRD OCTET OF 12.352MBIT/S DATA STREAM ......................................................................................... 216
SIXTH OCTET OF 12.352MBIT/S DATA STREAM ......................................................................................... 217
SEVENTH OCTET OF 12.352MBIT/S DATA STREAM .................................................................................... 217
EIGHTH OCTET OF 12.352MBIT/S DATA STREAM ...................................................................................... 217
NINETH OCTET OF 12.352MBIT/S DATA STREAM ....................................................................................... 217
Figure 35. Interfacing XRT84L38 to the Local Terminal Equipment using Bit-Multiplexed
12.352Mbit/s Data Bus ...................................................................................................... 218
Figure 36. Timing Diagram of the Input Signals to the Framer when running at 12.352Mbit/s Mode
218
FIRST OCTET OF 16.384MBIT/S DATA STREAM ......................................................................................... 219
NINETH OCTET OF 16.384MBIT/S DATA STREAM ....................................................................................... 219
TENTH OCTET OF 16.384MBIT/S DATA STREAM ........................................................................................ 219
THIRTEENTH OCTET OF 16.384MBIT/S DATA STREAM ............................................................................... 220
FOURTEENTH OCTET OF 16.384MBIT/S DATA STREAM .............................................................................. 220
FIFTEENTH OCTET OF 16.384MBIT/S DATA STREAM ................................................................................. 220
SIXTEENTH OCTET OF 16.384MBIT/S DATA STREAM ................................................................................. 220
Figure 37. Interfacing XRT84L38 to the Local Terminal Equipment using 16.384Mbit/s Data Bus
221
Figure 38. Timing Diagram of the Input Signals to the Framer when running at Bit-Multiplexed
16.384Mbit/s Mode ............................................................................................................ 221
FIRST OCTET OF 16.384MBIT/S DATA STREAM ......................................................................................... 222
NINTH OCTET OF 16.384MBIT/S DATA STREAM ........................................................................................ 222
ELEVENTH OCTET OF 16.384MBIT/S DATA STREAM .................................................................................. 223
THIRTEENTH OCTET OF 16.384MBIT/S DATA STREAM ............................................................................... 223
FIFTEENTH OCTET OF 16.384MBIT/S DATA STREAM ................................................................................. 223
TENTH OCTET OF 16.384MBIT/S DATA STREAM ........................................................................................ 223
TWELFTH OCTET OF 16.384MBIT/S DATA STREAM .................................................................................... 223
FOURTEENTH OCTET OF 16.384MBIT/S DATA STREAM .............................................................................. 223
SIXTEENTH OCTET OF 16.384MBIT/S DATA STREAM ................................................................................. 224
Figure 39. Interfacing XRT84L38 to the Local Terminal Equipment using HMVIP 16.384Mbit/s
Data Bus ............................................................................................................................ 225
Figure 40. Timing Diagram of the Input Signals to the Framer when running at HMVIP 16.384Mbit/
s Mode ............................................................................................................................... 225
FIRST OCTET OF 16.384MBIT/S DATA STREAM ......................................................................................... 226
NINTH OCTET OF 16.384MBIT/S DATA STREAM ........................................................................................ 226
ELEVENTH OCTET OF 16.384MBIT/S DATA STREAM .................................................................................. 227
THIRTEENTH OCTET OF 16.384MBIT/S DATA STREAM ............................................................................... 227
FIFTEENTH OCTET OF 16.384MBIT/S DATA STREAM ................................................................................. 227
TENTH OCTET OF 16.384MBIT/S DATA STREAM ........................................................................................ 227
TWELFTH OCTET OF 16.384MBIT/S DATA STREAM .................................................................................... 227
FOURTEENTH OCTET OF 16.384MBIT/S DATA STREAM .............................................................................. 227
SIXTEENTH OCTET OF 16.384MBIT/S DATA STREAM ................................................................................. 228
Figure 41. Interfacing XRT84L38 to the Local Terminal Equipment using H.100 16.384Mbit/s Data
Bus ..................................................................................................................................... 229
Figure 42. Timing Diagram of the Input Signals to the Framer when running at H.100 16.384Mbit/
s Mode ............................................................................................................................... 229
5.0 The DS1 Receive Section ..................................................................................................................... 230
5.1 THE DS1 RECEIVE PAYLOAD DATA OUTPUT INTERFACE BLOCK .......................................................... 230
5.1.1 Description of the Receive Payload Data Output Interface Block .......................................... 230
5.1.2 The Receive Payload Data Output Interface Block Operating at 1.544Mbit/s mode .............. 230
RECEIVE INTERFACE CONTROL REGISTER (RICR) (INDIRECT ADDRESS = 0XN0H, 0X22H) ........................ 230
IV
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
SLIP BUFFER CONTROL REGISTER (SBCR) (INDIRECT ADDRESS = 0XN0H, 0X16H) .................................. 231
SLIP BUFFER CONTROL REGISTER (SBCR) (INDIRECT ADDRESS = 0XN0H, 0X16H) .................................. 231
TABLE 42: THE RECEIVE SERIAL CLOCK AND RECEIVE SINGLE-FRAME SYNCHRONIZATION SIGNALS FOR DIF-
FERENT SLIP BUFFER SETTINGS ............................................................................................ 232
RECEIVE INTERFACE CONTROL REGISTER (RICR) (INDIRECT ADDRESS = 0XN0H, 0X22H) ........................ 232
TABLE 43: THE RXTSB[2:0] BITS WHEN THE RECEIVE FRACTIONAL T1 OUTPUT BIT IS SET TO DIFFERENT
VALUES ................................................................................................................................ 233
Figure 43. Interfacing XRT84L38 local Terminal Equipment with Slip Buffer Bypassed and Re-
covered Receive Line Clock as Receive Timing Source ............................................... 234
Figure 44. Waveforms of the Signals Connecting the Receive Payload Data Output Interface
block to the local Terminal Equipment when the Slip Buffer is Bypassed and the Recov-
ered Line Clock is the Timing Source of the Receive Section ...................................... 235
SLIP BUFFER STATUS REGISTER (SBSR) (INDIRECT ADDRESS = 0XNAH, 0X08H) .................................... 236
Figure 45. Interfacing XRT84L38 to local Terminal Equipment with Slip Buffer Enabled or Acts
as FIFO ............................................................................................................................... 237
Figure 46. Waveforms of the Signals that Connect the Receive Payload Data Output Interface
block to the local Terminal Equipment when the Slip Buffer is Enabled .................... 238
FIFO LATENCY REGISTER (FIFOLR) (INDIRECT ADDRESS = 0XN0H, 0X17H) ............................................ 238
Figure 47. Interfacing XRT84L38 to local Terminal Equipment with Slip Buffer Enabled or Acts
as FIFO ............................................................................................................................... 239
5.1.3 High Speed Receive Back-plane Interface ............................................................................. 240
Figure 48. Waveforms of the Signals that Connect the Receive Payload Data Output Interface
block to the local Terminal Equipment when the Slip Buffer is acted as FIFO ........... 240
RECEIVE INTERFACE CONTROL REGISTER (RICR) (INDIRECT ADDRESS = 0XN0H, 0X22H) ........................ 240
TABLE 44: RECEIVE MULTIPLEX ENABLE BIT AND RECEIVE INTERFACE MODE SELECT [1:0] BITS WITH THE
RESULTING RECEIVE BACK-PLANE INTERFACE DATA RATES ................................................... 241
RECEIVE MULTIPLEX ENABLE BIT = 0 ........................................................................................................ 241
RECEIVE MULTIPLEX ENABLE BIT = 1 ........................................................................................................ 242
RECEIVE INTERFACE CONTROL REGISTER (RICR) (INDIRECT ADDRESS = 0XN0H, 0X22H) ........................ 242
TABLE 45: THE MAPPING OF T1 FRAME INTO E1 FRAMING FORMAT ..................................................... 243
Figure 49. Interfacing XRT84L38 to local Terminal Equipment using MVIP 2.048Mbit/s Data Bus
244
Figure 50. Timing Diagram of Input signals to the Framer when running at MVIP 2.048Mbit/s ....
244
TABLE 46: THE MAPPING OF T1 FRAME INTO E1 FRAMING FORMAT ..................................................... 245
Figure 51. Interfacing XRT84L38 to local Terminal Equipment using 4.096Mbit/s Data Bus .. 246
Figure 52. Timing Diagram of Input signals to the Framer when running at 4.096Mbit/s ....... 246
TABLE 47: THE MAPPING OF T1 FRAME INTO E1 FRAMING FORMAT ..................................................... 247
Figure 53. Interfacing XRT84L38 to local Terminal Equipment using 8.192Mbit/s Data Bus .. 248
Figure 54. Timing Diagram of Input signals to the Framer when running at 8.192Mbit/s ....... 248
FIRST OCTET OF 12.352MBIT/S DATA STREAM ......................................................................................... 249
SECOND OCTET OF 12.352MBIT/S DATA STREAM ..................................................................................... 249
THIRD OCTET OF 12.352MBIT/S DATA STREAM ......................................................................................... 249
SIXTH OCTET OF 12.352MBIT/S DATA STREAM ......................................................................................... 250
SEVENTH OCTET OF 12.352MBIT/S DATA STREAM .................................................................................... 250
EIGHTH OCTET OF 12.352MBIT/S DATA STREAM ....................................................................................... 250
NINETH OCTET OF 12.352MBIT/S DATA STREAM ....................................................................................... 250
Figure 55. Interfacing XRT84L38 to local Terminal Equipment using 12.352Mbit/s Data Bus 251
Figure 56. Timing Diagram of Input signals to the Framer when running at 12.352Mbit/s ..... 251
FIRST OCTET OF 16.384MBIT/S DATA STREAM ......................................................................................... 252
NINTH OCTET OF 16.384MBIT/S DATA STREAM ......................................................................................... 252
TENTH OCTET OF 16.384MBIT/S DATA STREAM ........................................................................................ 252
THIRTEENTH OCTET OF 16.384MBIT/S DATA STREAM ................................................................................ 253
FOURTEENTH OCTET OF 16.384MBIT/S DATA STREAM .............................................................................. 253
V
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
FIFTEENTH OCTET OF 16.384MBIT/S DATA STREAM ................................................................................. 253
SIXTEENTH OCTET OF 16.384MBIT/S DATA STREAM ................................................................................. 253
Figure 57. Interfacing XRT84L38 to local Terminal Equipment using 16.384Mbit/s Data Bus 254
Figure 58. Timing Diagram of Input signals to the Framer when running at Bit-multiplexed
16.384Mbit/s ...................................................................................................................... 254
FIRST OCTET OF 16.384MBIT/S DATA STREAM ......................................................................................... 255
NINTH OCTET OF 16.384MBIT/S DATA STREAM ........................................................................................ 255
ELEVENTH OCTET OF 16.384MBIT/S DATA STREAM .................................................................................. 255
THIRTEENTH OCTET OF 16.384MBIT/S DATA STREAM ............................................................................... 255
FIFTEENTH OCTET OF 16.384MBIT/S DATA STREAM ................................................................................. 256
TENTH OCTET OF 16.384MBIT/S DATA STREAM ........................................................................................ 256
TWELFTH OCTET OF 16.384MBIT/S DATA STREAM .................................................................................... 256
FOURTEENTH OCTET OF 16.384MBIT/S DATA STREAM .............................................................................. 256
SIXTEENTH OCTET OF 16.384MBIT/S DATA STREAM ................................................................................. 256
Figure 59. Interfacing XRT84L38 to local Terminal Equipment using 16.384Mbit/s Data Bus 257
Figure 60. Timing Diagram of Input signals to the Framer when running at HMVIP 16.384Mbit/s
257
FIRST OCTET OF 16.384MBIT/S DATA STREAM ......................................................................................... 258
NINTH OCTET OF 16.384MBIT/S DATA STREAM ........................................................................................ 259
ELEVENTH OCTET OF 16.384MBIT/S DATA STREAM .................................................................................. 259
THIRTEENTH OCTET OF 16.384MBIT/S DATA STREAM ............................................................................... 259
FIFTEENTH OCTET OF 16.384MBIT/S DATA STREAM ................................................................................. 259
TENTH OCTET OF 16.384MBIT/S DATA STREAM ........................................................................................ 259
TWELFTH OCTET OF 16.384MBIT/S DATA STREAM .................................................................................... 260
FOURTEENTH OCTET OF 16.384MBIT/S DATA STREAM .............................................................................. 260
SIXTEENTH OCTET OF 16.384MBIT/S DATA STREAM ................................................................................. 260
Figure 61. Interfacing XRT84L38 to local Terminal Equipment using H.100 16.384Mbit/s Data Bus
261
Figure 62. Timing Diagram of Input signals to the Framer when running at H.100 16.384Mbit/s .
261
6.0 The E1 Transmit Section ...................................................................................................................... 262
6.1 THE E1 TRANSMIT PAYLOAD DATA INPUT INTERFACE BLOCK ............................................................... 262
6.1.1 Description of the Transmit Payload Data Input Interface Block ............................................ 262
6.1.2 Brief Discussion of the Transmit Payload Data Input Interface Block Operating at XRT84V24 Com-
patible 2.048Mbit/s mode ................................................................................................................ 262
TRANSMIT INTERFACE CONTROL REGISTER (TICR) (INDIRECT ADDRESS = 0XN0H, 0X20H) ....................... 262
CLOCK SELECT REGISTER (CSR) (INDIRECT ADDRESS = 0XN0H, 0X00H) ................................................ 263
TRANSMIT INTERFACE CONTROL REGISTER (TICR) (INDIRECT ADDRESS = 0XN0H, 0X20H) ....................... 264
Figure 63. Interfacing XRT84L38 to local terminal equipment with TxSerClk_n as Transmit Tim-
ing Source ......................................................................................................................... 266
Figure 64. Waveforms of the signals that connect the Transmit Payload Data Input Interface
Block to the local Terminal Equipment with the Transmit Serial clock being the timing
source of the Transmit Section ....................................................................................... 267
CLOCK SELECT REGISTER (CSR) (INDIRECT ADDRESS = 0XN0H, 0X00H) ................................................ 268
Figure 65. Interfacing XRT84L38 to local terminal equipment with OSCCLK driven divided clock
as transmit timing source ................................................................................................ 269
Figure 66. Waverforms of the signals connecting the Transmit Payload Data Input Interface
block to the local Terminal Equipment with the OSCCLK driven divided clock as the tim-
ing source of the Transmit Section ................................................................................. 270
CLOCK SELECT REGISTER (CSR) (INDIRECT ADDRESS = 0XN0H, 0X00H) ................................................ 271
Figure 67. Interfacing XRT84L38 to local terminal equipment with recovered receive line clock
as transmit timing source ................................................................................................ 272
6.1.3 Brief Discussion of the Transmit High-Speed Back-Plane Interface ...................................... 273
Figure 68. Waverforms of the signals connecting the Transmit Payload Data input interface
VI
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
block to the local Terminal Equipment with the Recovered Receive Line Clock being the
timing source of transmit section ................................................................................... 273
TRANSMIT INTERFACE CONTROL REGISTER (TICR) (INDIRECT ADDRESS = 0XN0H, 0X20H) ....................... 273
TRANSMIT MULTIPLEX ENABLE BIT = 0 ...................................................................................................... 274
TRANSMIT MULTIPLEX ENABLE BIT = 1 ...................................................................................................... 275
TRANSMIT INTERFACE CONTROL REGISTER (TICR) ........................ (INDIRECT ADDRESS = 0XN0H, 0X20H) 275
Figure 69. Interfacing XRT84L38 to local terminal equipment using MVIP 2.048Mbit/s data bus .
276
Figure 70. Timing diagram of input signals to the framer when running at MVIP 2.048Mbit/s ......
277
Figure 71. Interfacing XRT84L38 to local terminal equipment using 4.096Mbit/s data bus .... 278
Figure 72. Timing diagram of input signals to the framer when running at 4.096Mbit/s mode .....
278
Figure 73. Interfacing XRT84L38 to local terminal equipment using 8.192Mbit/s data bus .... 279
Figure 74. Timing diagram of input signals to the framer when running at 8.192Mbit/s mode .....
280
FIRST OCTET OF 16.384MBIT/S DATA STREAM ......................................................................................... 281
SECOND OCTET OF 16.384MBIT/S DATA STREAM ..................................................................................... 281
FIFTH OCTET OF 16.384MBIT/S DATA STREAM .......................................................................................... 281
SIXTH OCTET OF 16.384MBIT/S DATA STREAM ......................................................................................... 281
SEVENTH OCTET OF 16.384MBIT/S DATA STREAM .................................................................................... 281
EIGHTH OCTET OF 16.384MBIT/S DATA STREAM ....................................................................................... 282
Figure 75. Interfacing XRT84L38 to local terminal equipment using 16.384Mbit/s data bus .. 283
Figure 76. iming signal when the framer is running at Bit-Multiplexed 16.384Mbit/s mode ... 283
FIRST OCTET OF 16.384MBIT/S DATA STREAM ......................................................................................... 284
THIRD OCTET OF 16.384MBIT/S DATA STREAM ......................................................................................... 284
FIFTH OCTET OF 16.384MBIT/S DATA STREAM .......................................................................................... 284
SEVENTH OCTET OF 16.384MBIT/S DATA STREAM .................................................................................... 284
SECOND OCTET OF 16.384MBIT/S DATA STREAM ..................................................................................... 285
FOURTH OCTET OF 16.384MBIT/S DATA STREAM ...................................................................................... 285
SIXTH OCTET OF 16.384MBIT/S DATA STREAM ......................................................................................... 285
EIGHTH OCTET OF 16.384MBIT/S DATA STREAM ....................................................................................... 285
Figure 77. Interfacing XRT84L38 to local terminal equipment using 16.384Mbit/s data bus .. 286
Figure 78. Timing Signal when the framer is running at HMVIP 16.384Mbit/s mode ............... 286
FIRST OCTET OF 16.384MBIT/S DATA STREAM ......................................................................................... 287
THIRD OCTET OF 16.384MBIT/S DATA STREAM ......................................................................................... 287
FIFTH OCTET OF 16.384MBIT/S DATA STREAM .......................................................................................... 287
SEVENTH OCTET OF 16.384MBIT/S DATA STREAM .................................................................................... 288
SECOND OCTET OF 16.384MBIT/S DATA STREAM ..................................................................................... 288
FOURTH OCTET OF 16.384MBIT/S DATA STREAM ...................................................................................... 288
SIXTH OCTET OF 16.384MBIT/S DATA STREAM ......................................................................................... 288
EIGHTH OCTET OF 16.384MBIT/S DATA STREAM ....................................................................................... 288
Figure 79. Interfacing XRT84L38 to local terminal equipment using 16.384Mbit/s data bus .. 289
6.2 THE RECEIVE PAYLOAD DATA OUTPUT INTERFACE BLOCK ................................................................... 290
6.2.1 Description of the Receive Payload Data Output Interface Block ........................................... 290
Figure 80. Timing signal when the framer is running at H.100 16.384Mbit/s mode ................. 290
6.2.2 Brief Discussion of the Receive Payload Data Output Interface Block Operating at XRT84V24
Compatible 2.048Mbit/s mode ......................................................................................................... 291
RECEIVE INTERFACE CONTROL REGISTER (RICR) (INDIRECT ADDRESS = 0XN0H, 0X22H) ........................ 291
SLIP BUFFER CONTROL REGISTER (SBCR).................................... (INDIRECT ADDRESS = 0XN0H, 0X16H) 291
SLIP BUFFER CONTROL REGISTER (SBCR).................................... (INDIRECT ADDRESS = 0XN0H, 0X16H) 292
RECEIVE INTERFACE CONTROL REGISTER (RICR) (INDIRECT ADDRESS = 0XN0H, 0X22H) ........................ 293
Figure 81. Interfacing XRT84L38 to local terminal equipment with slip buffer bypassed and re-
covered receive line clock as receive timing source ..................................................... 295
VII
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
Figure 82. Waveforms of the Signals Connecting the Receive Payload Data Output Interface
block to the local Terminal Equipment when the Slip Buffer is Bypassed and the Recov-
ered Line Clock is the Timing Source of the Receive Section ..................................... 296
SLIP BUFFER STATUS REGISTER (SBSR) ...................................... (INDIRECT ADDRESS = 0XNAH, 0X08H) 297
Figure 83. Interfacing XRT84L38 to local terminal equipment with slip buffer enabled or acts as
fifo ...................................................................................................................................... 298
Figure 84. Waveforms of the Signals that Connect the Receive Payload Data Output Interface
block to the local Terminal Equipment when the Slip Buffer is Enabled .................... 299
FIFO LATENCY REGISTER (FIFOL) (INDIRECT ADDRESS = 0XN0H, 0X17H) .............................................. 299
Figure 85. Interfacing XRT84L38 to local terminal equipment with slip buffer enabled or acts as
fifo ...................................................................................................................................... 300
6.2.3 High Speed Receive Back-plane Interface ............................................................................. 301
Figure 86. Waveforms of the Signals that Connect the Receive Payload Data Output Interface
block to the local Terminal Equipment when the Slip Buffer is acted as FIFO .......... 301
RECEIVE INTERFACE CONTROL REGISTER (RICR) (INDIRECT ADDRESS = 0XN0H, 0X22H) ........................ 301
RECEIVE MULTIPLEX ENABLE BIT = 0 ....................................................................................................... 302
RECEIVE MULTIPLEX ENABLE BIT = 1 ....................................................................................................... 303
RECEIVE INTERFACE CONTROL REGISTER (RICR) ..........................(INDIRECT ADDRESS = 0XN0H, 0X22H) 303
Figure 87. Interfacing XRT84L38 to local terminal equipment using MVIP 2.048Mbit/s data bus .
304
Figure 88. Timing Diagram of Input signals to the Framer when running at MVIP 2.048Mbit/s ....
304
Figure 89. Interfacing XRT84L38 to local terminal equipment using 4.096Mbit/s data bus ... 305
Figure 90. Timing Diagram of input signals to the framer when running at 4.096Mbit/s mode ....
306
Figure 91. Interfacing XRT84L38 to local terminal equipment using 8.192Mbit/s data bus ... 307
Figure 92. Timing diagram of input signals to the framer when running at 8.192Mbit/s mode .....
307
FIRST OCTET OF 16.384MBIT/S DATA STREAM ......................................................................................... 308
SECOND OCTET OF 16.384MBIT/S DATA STREAM ..................................................................................... 308
FIFTH OCTET OF 16.384MBIT/S DATA STREAM ......................................................................................... 308
SIXTH OCTET OF 16.384MBIT/S DATA STREAM ......................................................................................... 309
SEVENTH OCTET OF 16.384MBIT/S DATA STREAM .................................................................................... 309
EIGHTH OCTET OF 16.384MBIT/S DATA STREAM ...................................................................................... 309
Figure 93. Interfacing XRT84L38 to local terminal equipment using 16.384 Mbit/s data bus 310
Figure 94. Timing signal when the framer is running at Bit-Multiplexed 16.384Mbit/s mode 310
FIRST OCTET OF 16.384MBIT/S DATA STREAM ......................................................................................... 311
THIRD OCTET OF 16.384MBIT/S DATA STREAM ......................................................................................... 311
FIFTH OCTET OF 16.384MBIT/S DATA STREAM ......................................................................................... 311
SEVENTH OCTET OF 16.384MBIT/S DATA STREAM .................................................................................... 311
SECOND OCTET OF 16.384MBIT/S DATA STREAM ..................................................................................... 312
FOURTH OCTET OF 16.384MBIT/S DATA STREAM ..................................................................................... 312
SIXTH OCTET OF 16.384MBIT/S DATA STREAM ......................................................................................... 312
EIGHTH OCTET OF 16.384MBIT/S DATA STREAM ...................................................................................... 312
Figure 95. Interfacing XRT84L38 to local terminal equipment using 16.384Mbit/s data bus . 313
Figure 96. Timing Signal when the framer is running at HMVIP 16.384Mbit/s mode .............. 313
FIRST OCTET OF 16.384MBIT/S DATA STREAM ......................................................................................... 314
THIRD OCTET OF 16.384MBIT/S DATA STREAM ......................................................................................... 314
FIFTH OCTET OF 16.384MBIT/S DATA STREAM ......................................................................................... 314
SEVENTH OCTET OF 16.384MBIT/S DATA STREAM .................................................................................... 314
SECOND OCTET OF 16.384MBIT/S DATA STREAM ..................................................................................... 315
FOURTH OCTET OF 16.384MBIT/S DATA STREAM ..................................................................................... 315
SIXTH OCTET OF 16.384MBIT/S DATA STREAM ......................................................................................... 315
EIGHTH OCTET OF 16.384MBIT/S DATA STREAM ...................................................................................... 315
VIII
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
Figure 97. Interfacing XRT84L38 to local terminal equipment using 16.384Mbit/s data bus .. 316
Figure 98. Timing Signal when the framer is running at H.100 16.384Mbit/s mode ................. 316
7.0 DS1 Overhead Interface Block ............................................................................................................. 317
7.1 DS1 TRANSMIT OVERHEAD INPUT INTERFACE BLOCK .......................................................................... 317
7.1.1 Description of the DS1 Transmit Overhead Input Interface Block ........................................... 317
7.1.2 Configure the DS1 Transmit Overhead Input Interface module as source of the Facility Data Link
(FDL) bits in ESF framing format mode ........................................................................................... 317
Figure 99. Block Diagram of the DS1 Transmit Overhead Input Interface of the XRT84L38 .. 317
TRANSMIT DATA LINK SELECT REGISTER (TDLSR) (INDIRECT ADDRESS = 0XN0H, 0X0AH) ....................... 318
TRANSMIT DATA LINK SELECT REGISTER (TDLSR) (INDIRECT ADDRESS = 0XN0H, 0X0AH) ....................... 318
7.1.3 Configure the DS1 Transmit Overhead Input Interface module as source of the Signaling Framing
(Fs) bits in N or SLC®96 framing format mode ................................................................................ 319
Figure 100. DS1 Transmit Overhead Input Interface Timing in ESF Framing Format mode ... 319
TRANSMIT DATA LINK SELECT REGISTER (TDLSR) (INDIRECT ADDRESS = 0XN0H, 0X0AH) ....................... 319
7.1.4 Configure the DS1 Transmit Overhead Input Interface module as source of the Remote Signaling
(R) bits in T1DM framing format mode ............................................................................................. 320
Figure 101. DS1 Transmit Overhead Input Timing in N or SLC®96 Framing Format Mode .... 320
TRANSMIT DATA LINK SELECT REGISTER (TDLSR) (INDIRECT ADDRESS = 0XN0H, 0X0AH) .......................... 320
Figure 102. DS1 Transmit Overhead Input Interface module in T1DM Framing Format mode ......
320
7.2 DS1 RECEIVE OVERHEAD OUTPUT INTERFACE BLOCK ......................................................................... 321
7.2.1 Description of the DS1 Receive Overhead Output Interface Block ......................................... 321
7.2.2 Configure the DS1 Receive Overhead Output Interface module as destination of the Facility Data
Link (FDL) bits in ESF framing format mode .................................................................................... 321
Figure 103. Block Diagram of the DS1 Receive Overhead Output Interface of XRT84L38 ..... 321
RECEIVE DATA LINK SELECT REGISTER (TDLSR) (INDIRECT ADDRESS = 0XN0H, 0X0AH) ......................... 322
RECEIVE DATA LINK SELECT REGISTER (TDLSR) (INDIRECT ADDRESS = 0XN0H, 0X0AH) ......................... 322
7.2.3 Configure the DS1 Receive Overhead Output Interface module as destination of the Signaling
Framing (Fs) bits in N or SLC®96 framing format mode .................................................................. 323
Figure 104. DS1 Receive Overhead Output Interface module in ESF framing format mode .. 323
RECEIVE DATA LINK SELECT REGISTER (TDLSR) (INDIRECT ADDRESS = 0XN0H, 0X0AH) ........................ 323
7.2.4 Configure the DS1 Receive Overhead Output Interface module as destination of the Remote Sig-
naling (R) bits in T1DM framing format mode .................................................................................. 324
Figure 105. DS1 Receive Overhead Output Interface Timing in N or SLC®96 Framing Format
mode ................................................................................................................................... 324
RECEIVE DATA LINK SELECT REGISTER (RDLSR) (INDIRECT ADDRESS = 0XN0H, 0X0AH) ........................ 324
Figure 106. DS1 Receive Overhead Output Interface Timing in T1DM Framing Format mode .....
325
8.0 E1 Overhead Interface Block ............................................................................................................... 326
8.1 E1 TRANSMIT OVERHEAD INPUT INTERFACE BLOCK ............................................................................. 326
8.1.1 Description of the E1 Transmit Overhead Input Interface Block ............................................. 326
8.1.2 Configure the E1 Transmit Overhead Input Interface module as source of the National Bit Se-
quence in E1 framing format mode .................................................................................................. 326
Figure 107. Block Diagram of the E1 Transmit Overhead Input Interface of XRT84L38 ......... 326
SYNCHRONIZATION MUX REGISTER (SMR) (INDIRECT ADDRESS = 0XN0H, 0X09H) .................................. 327
TRANSMIT SIGNALING AND DATA LINK SELECT REGISTER (TSDLSR) (INDIRECT ADDRESS = 0XN0H, 0X0AH) ....
327
8.2 E1 RECEIVE OVERHEAD INTERFACE .................................................................................................... 328
8.2.1 Description of the E1 Receive Overhead Output Interface Block ........................................... 328
Figure 108. E1 Transmit Overhead Input Interface Timing ........................................................ 328
8.2.2 Configure the E1 Receive Overhead Output Interface module as source of the National Bit Se-
quence in E1 framing format mode .................................................................................................. 329
Figure 109. Block Diagram of the E1 Receive Overhead Output Interface of XRT84L38 ........ 329
RECEIVE SIGNALING AND DATA LINK SELECT REGISTER (RSDLSR) (INDIRECT ADDRESS = 0XN0H, 0X0CH) ....
IX
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
329
Figure 110. E1 Receive Overhead Output Interface Timing ...................................................... 330
9.0 DS1 Transmit Framer Block ................................................................................................................ 331
9.1 HOW TO CONFIGURE XRT84L38 TO OPERATE IN DS1 MODE ............................................................. 331
CLOCK SELECT REGISTER (CSR) (INDIRECT ADDRESS = 0XN0H, 0X00H) ................................................ 331
FRAMING SELECT REGISTER (FSR) (INDIRECT ADDRESS = 0XN0H, 0X07H) ............................................. 331
9.2 HOW TO CONFIGURE THE FRAMER TO TRANSMIT DATA IN VARIOUS DS1 FRAMING FORMATS ............... 332
9.2.1 How to configure the framer to input framing alignment bits from different sources .............. 332
FRAMING SELECT REGISTER (FSR) (I..............................................NDIRECT ADDRESS = 0XN0H, 0X07H) 332
9.2.2 How to configure the framer to input CRC-6 bits from different sources ................................ 333
SYNCHRONIZATION MUX REGISTER (SMR) (INDIRECT ADDRESS = 0XN0H, 0X09H) .................................. 333
SYNCHRONIZATION MUX REGISTER (SMR) (INDIRECT ADDRESS = 0XN0H, 0X09H) .................................. 333
9.3 HOW TO CONFIGURE THE FRAMER TO APPLY DATA AND SIGNALING CONDITIONING TO DS1 PAYLOAD DATA
ON A PER-CHANNEL BASIS .............................................................................................................................. 334
9.3.1 How to apply User IDLE Code to the DS1 payload data ........................................................ 335
TRANSMIT CHANNEL CONTROL REGISTER (TCCR) (INDIRECT ADDRESS = 0XN2H, 0X00H - 0X1FH) .......... 335
USER IDLE CODE REGISTER (UCR) (INDIRECT ADDRESS = 0XN02H, 0X20H - 0X37H) ............................ 335
9.4 HOW TO CONFIGURE THE XRT84L38 FRAMER TO APPLY ZERO CODE SUPPRESSION TO DS1 PAYLOAD DATA
ON A PER-CHANNEL BASIS .............................................................................................................................. 336
9.5 HOW TO CONFIGURE THE XRT84L38 FRAMER TO TRANSMIT ROBBED-BIT SIGNALING INFORMATION .... 336
9.5.1 Brief Discussion of Robbed-bit Signaling in DS1 Framing Format ......................................... 336
TRANSMIT CHANNEL CONTROL REGISTER (TCCR) (INDIRECT ADDRESS = 0XN2H, 0X00H - 0X1FH) ......... 336
9.5.2 Configure the framer to transmit Robbed-bit Signaling .......................................................... 337
TRANSMIT SIGNALING CONTROL REGISTER (TSCR) (INDIRECT ADDRESS = 0XN2H, 0X40H - 0X57H) ....... 338
Figure 111. Timing Diagram of the TxSig_n Input ...................................................................... 339
TRANSMIT INTERFACE CONTROL REGISTER (TICR).........................(INDIRECT ADDRESS = 0XN0H, 0X20H) 339
9.6 HOW TO CONFIGURE THE XRT84L38 FRAMER TO GENERATE AND TRANSMIT ALARMS AND ERROR INDICA-
TIONS TO REMOTE TERMINAL .......................................................................................................................... 340
9.6.1 Brief discussion of alarms and error conditions ...................................................................... 340
TRANSMIT SIGNALING CONTROL REGISTER (TSCR) (INDIRECT ADDRESS = 0XN2H, 0X40H - 0X57H) ....... 340
TRANSMIT SIGNALING CONTROL REGISTER (TSCR) (INDIRECT ADDRESS = 0XN2H, 0X40H - 0X57H) ....... 340
Figure 112. Simple Diagram of DS1 System Model .................................................................... 341
Figure 113. Generation of Yellow Alarm by the CPE upon detection of line failure ................ 342
Figure 114. Generation of AIS by the Repeater upon detection of Yellow Alarm originated by the
CPE .................................................................................................................................... 343
9.6.2 How to configure the framer to transmit AIS ........................................................................... 344
Figure 115. Generation of Yellow Alarm by the CPE upon detection of AIS originated by the Re-
peater ................................................................................................................................. 344
9.6.3 How to configure the framer to generate Red Alarm .............................................................. 345
9.6.4 How to configure the framer to transmit Yellow Alarm ........................................................... 345
ALARM GENERATION REGISTER (AGR)...........................................(INDIRECT ADDRESS = 0XN0H, 0X08H) 345
ALARM GENERATION REGISTER (AGR)...........................................(INDIRECT ADDRESS = 0XN0H, 0X08H) 345
ALARM GENERATION REGISTER (AGR)...........................................(INDIRECT ADDRESS = 0XN0H, 0X08H) 347
10.0 DS1 Receive Framer Block ................................................................................................................ 348
10.1 HOW TO CONFIGURE XRT84L38 TO OPERATE IN DS1 MODE ........................................................... 348
CLOCK SELECT REGISTER (CSR) (INDIRECT ADDRESS = 0XN0H, 0X00H) ................................................ 348
FRAMING SELECT REGISTER (FSR) (INDIRECT ADDRESS = 0XN0H, 0X07H) ............................................. 348
10.2 HOW TO CONFIGURE THE FRAMER TO RECEIVE DATA IN VARIOUS DS1 FRAMING FORMATS ............... 349
10.3 HOW TO CONFIGURE THE FRAMER TO APPLY DATA AND SIGNALING CONDITIONING TO RECEIVED DS1 PAY-
LOAD DATA ON A PER-CHANNEL BASIS ............................................................................................................ 349
FRAMING SELECT REGISTER (FSR) (INDIRECT ADDRESS = 0XN0H, 0X07H) .............................................. 349
RECEIVE CHANNEL CONTROL REGISTER (RCCR) (INDIRECT ADDRESS = 0XN2H, 0X60H - 0X7FH) ........... 351
RECEIVE USER IDLE CODE REGISTER (UCR) (INDIRECT ADDRESS = 0XN02H, 0X80H - 0X97H) ............... 351
10.4 HOW TO CONFIGURE THE XRT84L38 FRAMER TO APPLY ZERO CODE SUPPRESSION TO RECEIVED DS1
X
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
PAYLOAD DATA ON A PER-CHANNEL BASIS ...................................................................................................... 352
10.5 HOW TO CONFIGURE THE XRT84L38 FRAMER TO EXTRACT ROBBED-BIT SIGNALING INFORMATION .... 352
10.5.1 Configure the framer to receive and extract Robbed-bit Signaling ....................................... 352
RECEIVE CHANNEL CONTROL REGISTER (RCCR) (INDIRECT ADDRESS = 0XN2H, 0X60H - 0X7FH) ............ 352
RECEIVE SIGNALING CONTROL REGISTER (RSCR) (INDIRECT ADDRESS = 0XN2H, 0XA0H - 0XB7H) ......... 353
FRAMER INTERRUPT ENABLE REGISTER (FIER) (INDIRECT ADDRESS = 0XNAH, 0X05H) ........................... 353
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X00H) ............................... 354
FRAMER INTERRUPT STATUS REGISTER (FISR) (INDIRECT ADDRESS = 0XNAH, 0X04H) ........................... 354
SIGNALING CHANGE REGISTERS (SCR) (INDIRECT ADDRESS = 0XN0H, 0X0DH - 0X0FH) ......................... 354
RECEIVE SIGNALING REGISTER ARRAY (RSRA) (INDIRECT ADDRESS = 0XN4H, 0X00H - 0X17H) .............. 355
RECEIVE INTERFACE CONTROL REGISTER (TICR) (INDIRECT ADDRESS = 0XN0H, 0X20H) ......................... 355
Figure 116. Timing Diagram of the RxSig_n Output pin ............................................................. 356
RECEIVE SIGNALING CONTROL REGISTER (RSCR) (INDIRECT ADDRESS = 0XN2H, 0XA0H - 0XB7H) ......... 356
RECEIVE SIGNALING CONTROL REGISTER (RSCR) (INDIRECT ADDRESS = 0XN2H, 0XA0H - 0XB7H) ......... 357
RECEIVE SUBSTITUTION SIGNALING REGISTER (RSSR) (INDIRECT ADDRESS = 0XN02H, 0X80H - 0X97H) . 357
10.6 HOW TO CONFIGURE THE FRAMER TO DETECT ALARMS AND ERROR CONDITIONS .............................. 358
10.6.1 How to configure the framer to detect AIS Alarm .................................................................. 358
RECEIVE SIGNALING CONTROL REGISTER (RSCR) (INDIRECT ADDRESS = 0XN2H, 0X40H - 0X57H) ......... 358
ALARM GENERATION REGISTER (AGR) (INDIRECT ADDRESS = 0XN0H, 0X08H) ........................................ 359
ALARM AND ERROR INTERRUPT ENABLE REGISTER (AEIER) (INDIRECT ADDRESS = 0XNAH, 0X03H) ........ 359
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X01H) .............................. 359
10.6.2 How to configure the framer to detect Red Alarm ................................................................. 360
ALARM AND ERROR STATUS REGISTER (AESR) (INDIRECT ADDRESS = 0XNAH, 0X02H) ............................ 360
ALARM AND ERROR STATUS REGISTER (AESR) (INDIRECT ADDRESS = 0XNAH, 0X02H) ........................... 360
ALARM AND ERROR INTERRUPT ENABLE REGISTER (AEIER) (INDIRECT ADDRESS = 0XNAH, 0X03H) ........ 361
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X01H) ............................... 361
ALARM AND ERROR STATUS REGISTER (AESR) (INDIRECT ADDRESS = 0XNAH, 0X02H) ............................ 361
10.6.3 How to configure the framer to detect Yellow Alarm ............................................................. 362
ALARM AND ERROR STATUS REGISTER (AESR) (INDIRECT ADDRESS = 0XNAH, 0X02H) ............................ 362
ALARM AND ERROR INTERRUPT ENABLE REGISTER (AEIER) (INDIRECT ADDRESS = 0XNAH, 0X03H) ......... 362
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X01H) ............................... 362
10.6.4 How to configure the framer to detect Bipolar Violation ........................................................ 363
ALARM AND ERROR STATUS REGISTER (AESR).............................(INDIRECT ADDRESS = 0XNAH, 0X02H) 363
ALARM AND ERROR STATUS REGISTER (AESR) (INDIRECT ADDRESS = 0XNAH, 0X02H) ........................... 363
10.6.5 How to configure the framer to detect Loss of Signal ........................................................... 364
ALARM AND ERROR INTERRUPT ENABLE REGISTER (AEIER) (INDIRECT ADDRESS = 0XNAH, 0X03H) ........ 364
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X01H) ............................... 364
ALARM AND ERROR STATUS REGISTER (AESR) (INDIRECT ADDRESS = 0XNAH, 0X02H) ........................... 364
ALARM AND ERROR INTERRUPT ENABLE REGISTER (AEIER) (INDIRECT ADDRESS = 0XNAH, 0X03H) ......... 365
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X01H) ............................... 365
ALARM AND ERROR STATUS REGISTER (AESR) (INDIRECT ADDRESS = 0XNAH, 0X02H) ........................... 365
11.0 E1 Transmit Framer Block ................................................................................................................. 366
11.1 HOW TO CONFIGURE XRT84L38 TO OPERATE IN E1 MODE .............................................................. 366
11.2 HOW TO CONFIGURE THE FRAMER TO TRANSMIT AND RECEIVE DATA IN E1 FRAMING FORMAT ........... 366
11.2.1 How to configure the framer to choose FAS searching algorithm ......................................... 366
CLOCK SELECT REGISTER (CSR) (INDIRECT ADDRESS = 0XN0H, 0X00H) ................................................. 366
11.2.2 How to configure the framer to enable CRC-4 Multi-frame alignment and select the locking crite-
ria ..................................................................................................................................................... 367
11.2.3 How to configure the framer to enable CAS Multi-frame alignment ...................................... 367
FRAMING SELECT REGISTER (FSR) (INDIRECT ADDRESS = 0XN0H, 0X07H) .............................................. 367
FRAMING SELECT REGISTER (FSR) (INDIRECT ADDRESS = 0XN0H, 0X07H) .............................................. 367
11.2.4 How to configure the framer to input the framing alignment bits from different sources ....... 368
FRAMING SELECT REGISTER (FSR) (INDIRECT ADDRESS = 0XN0H, 0X07H) .............................................. 368
11.2.5 How to configure the framer to input CRC-4 bits from different sources ............................... 369
XI
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
11.2.6 How to configure the framer to input E bits from different sources ....................................... 369
SYNCHRONIZATION MUX REGISTER (SMR) (INDIRECT ADDRESS = 0XN0H, 0X09H) .................................. 369
SYNCHRONIZATION MUX REGISTER (SMR) (INDIRECT ADDRESS = 0XN0H, 0X09H) ................................. 369
11.3 HOW TO CONFIGURE THE FRAMER TO APPLY DATA AND SIGNALING CONDITIONING TO E1 PAYLOAD DATA
ON A PER-CHANNEL BASIS .............................................................................................................................. 370
SYNCHRONIZATION MUX REGISTER (SMR) (INDIRECT ADDRESS = 0XN0H, 0X09H) ................................. 370
TRANSMIT CHANNEL CONTROL REGISTER (TCCR) (INDIRECT ADDRESS = 0XN2H, 0X00H - 0X1FH) .......... 371
11.4 HOW TO CONFIGURE THE XRT84L38 FRAMER TO TRANSMIT SIGNALING INFORMATION ...................... 372
11.4.1 Brief Discussion of Common Channel Signaling in E1 Framing Format .............................. 372
11.4.2 Brief Discussion of Channel Associated Signaling in E1 Framing Format ........................... 372
USER IDLE CODE REGISTER (UCR) (INDIRECT ADDRESS = 0XN02H, 0X20H - 0X3FH) ............................. 372
11.4.3 Configure the framer to transmit Channel Associated Signaling .......................................... 373
TRANSMIT SIGNALING CONTROL REGISTER (TSCR) (INDIRECT ADDRESS = 0XN2H, 0X40H - 0X5FH) ....... 374
Figure 117. Timing Diagram of the TxSig_n Input ...................................................................... 375
TRANSMIT INTERFACE CONTROL REGISTER (TICR) (INDIRECT ADDRESS = 0XN0H, 0X20H) ...................... 375
Figure 118. Timing Diagram of the TxOH_n Input ...................................................................... 375
11.5 HOW TO CONFIGURE THE XRT84L38 FRAMER TO GENERATE AND TRANSMIT ALARMS AND ERROR INDICA-
TIONS TO REMOTE TERMINAL .......................................................................................................................... 376
11.5.1 Brief discussion of alarms and error conditions .................................................................... 376
TRANSMIT SIGNALING CONTROL REGISTER (TSCR) (INDIRECT ADDRESS = 0XN2H, 0X40H - 0X57H) ....... 376
Figure 119. Simple Diagram of E1 system model ....................................................................... 377
Figure 120. Generation of Yellow Alarm by the Repeater upon detection of line failure ........ 378
Figure 121. Generation of AIS by the Repeater upon detection of line failure ........................ 379
Figure 122. Generation of Yellow Alarm by the CPE upon detection of AIS originated by the Re-
peater ................................................................................................................................. 380
Figure 123. Generation of CAS Multi-frame Yellow Alarm and AIS16 by the Repeater .......... 381
11.5.2 How to configure the framer to transmit AIS ......................................................................... 382
Figure 124. Generation of CAS Multi-fram Yellow Alarm by the CPE upon detection of “AIS16”
pattern sent by the Repeater ........................................................................................... 382
11.5.3 How to configure the framer to generate Red Alarm ............................................................ 383
11.5.4 How to configure the framer to transmit Yellow Alarm ......................................................... 383
ALARM GENERATION REGISTER (AGR) (INDIRECT ADDRESS = 0XN0H, 0X08H) ........................................ 383
ALARM GENERATION REGISTER (AGR) (INDIRECT ADDRESS = 0XN0H, 0X08H) ........................................ 383
ALARM GENERATION REGISTER (AGR) (INDIRECT ADDRESS = 0XN0H, 0X08H) ........................................ 385
12.0 E1 Receive Framer Block ................................................................................................................... 386
12.1 HOW TO CONFIGURE XRT84L38 TO OPERATE IN E1 MODE .............................................................. 386
12.2 HOW TO CONFIGURE THE FRAMER TO RECEIVE DATA IN VARIOUS E1 FRAMING FORMATS ................. 386
12.2.1 How to configure the framer to choose FAS searching algorithm ........................................ 386
CLOCK SELECT REGISTER (CSR)...................................................(INDIRECT ADDRESS = 0XN0H, 0X00H) 386
12.2.2 How to configure the framer to enable CRC-4 Multi-frame alignment and select the locking crite-
ria ..................................................................................................................................................... 387
12.2.3 How to configure the framer to enable CAS Multi-frame alignment ..................................... 387
FRAMING SELECT REGISTER (FSR) (INDIRECT ADDRESS = 0XN0H, 0X07H) ............................................. 387
FRAMING SELECT REGISTER (FSR) (INDIRECT ADDRESS = 0XN0H, 0X07H) ............................................. 387
12.3 HOW TO CONFIGURE THE FRAMER TO APPLY DATA AND SIGNALING CONDITIONING TO RECEIVED E1 PAY-
LOAD DATA ON A PER-CHANNEL BASIS ............................................................................................................ 388
FRAMING SELECT REGISTER (FSR) (INDIRECT ADDRESS = 0XN0H, 0X07H) ............................................. 388
RECEIVE CHANNEL CONTROL REGISTER (RCCR) (INDIRECT ADDRESS = 0XN2H, 0X60H - 0X7FH) .......... 389
12.4 HOW TO CONFIGURE THE XRT84L38 FRAMER TO EXTRACT ROBBED-BIT SIGNALING INFORMATION ... 390
12.4.1 Configure the framer to receive and extract Robbed-bit Signaling ....................................... 390
RECEIVE USER IDLE CODE REGISTER (UCR) (INDIRECT ADDRESS = 0XN02H, 0X80H - 0X97H) .............. 390
RECEIVE SIGNALING CONTROL REGISTER (RSCR) (INDIRECT ADDRESS = 0XN2H, 0XA0H - 0XB7H) ........ 390
FRAMER INTERRUPT ENABLE REGISTER (FIER) (INDIRECT ADDRESS = 0XNAH, 0X05H) ............................ 391
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X00H) ............................. 391
XII
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
FRAMER INTERRUPT STATUS REGISTER (FISR) (INDIRECT ADDRESS = 0XNAH, 0X04H) ........................... 391
SIGNALING CHANGE REGISTERS (SCR) (INDIRECT ADDRESS = 0XN0H, 0X0DH - 0X10H) ......................... 392
RECEIVE SIGNALING REGISTER ARRAY (RSRA) (INDIRECT ADDRESS = 0XN4H, 0X00H - 0X1FH) .............. 392
RECEIVE INTERFACE CONTROL REGISTER (RICR) (INDIRECT ADDRESS = 0XN0H, 0X20H) ........................ 393
Figure 125. Timing diagram of RxSig_n Output pin ................................................................... 393
Figure 126. Timing diagram of the RxOH_n Output pin ............................................................. 393
RECEIVE SIGNALING CONTROL REGISTER (RSCR) (INDIRECT ADDRESS = 0XN2H, 0XA0H - 0XBFH) ......... 394
RECEIVE SIGNALING CONTROL REGISTER (RSCR) (INDIRECT ADDRESS = 0XN2H, 0XA0H - 0XBFH) ........ 394
RECEIVE SUBSTITUTION SIGNALING REGISTER (RSSR) (INDIRECT ADDRESS = 0XN02H, 0X80H - 0X9FH) 394
12.5 HOW TO CONFIGURE THE FRAMER TO DETECT ALARMS AND ERROR CONDITIONS .............................. 395
RECEIVE SIGNALING CONTROL REGISTER (RSCR) (INDIRECT ADDRESS = 0XN2H, 0X40H - 0X5FH) ......... 395
12.5.1 How to configure the framer to detect AIS Alarm .................................................................. 396
ALARM GENERATION REGISTER (AGR) (INDIRECT ADDRESS = 0XN0H, 0X08H) ........................................ 397
ALARM AND ERROR INTERRUPT ENABLE REGISTER (AEIER) (INDIRECT ADDRESS = 0XNAH, 0X03H) ........ 397
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X01H) .............................. 397
12.5.2 How to configure the framer to detect Red Alarm ................................................................. 398
ALARM AND ERROR STATUS REGISTER (AESR) (INDIRECT ADDRESS = 0XNAH, 0X02H) ............................ 398
ALARM AND ERROR STATUS REGISTER (AESR) (INDIRECT ADDRESS = 0XNAH, 0X02H) ............................ 398
ALARM AND ERROR INTERRUPT ENABLE REGISTER (AEIER) (INDIRECT ADDRESS = 0XNAH, 0X03H) ........ 399
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X01H) .............................. 399
ALARM AND ERROR STATUS REGISTER (AESR) (INDIRECT ADDRESS = 0XNAH, 0X02H) ........................... 399
12.5.3 How to configure the framer to detect Yellow Alarm ............................................................. 400
ALARM AND ERROR STATUS REGISTER (AESR) (INDIRECT ADDRESS = 0XNAH, 0X02H) ........................... 400
ALARM AND ERROR INTERRUPT ENABLE REGISTER (AEIER) (INDIRECT ADDRESS = 0XNAH, 0X03H) ......... 400
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X01H) .............................. 400
12.5.4 How to configure the framer to detect CAS Multi-frame Yellow Alarm .................................. 401
ALARM AND ERROR STATUS REGISTER (AESR) (INDIRECT ADDRESS = 0XNAH, 0X02H) ........................... 401
ALARM AND ERROR INTERRUPT ENABLE REGISTER (AEIER) (INDIRECT ADDRESS = 0XNAH, 0X03H) ........ 401
12.5.5 How to configure the framer to detect Bipolar Violation ........................................................ 402
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X01H) .............................. 402
ALARM AND ERROR STATUS REGISTER (AESR) (INDIRECT ADDRESS = 0XNAH, 0X02H) ........................... 402
12.5.6 How to configure the framer to detect Loss of Signal ........................................................... 403
ALARM AND ERROR INTERRUPT ENABLE REGISTER (AEIER) (INDIRECT ADDRESS = 0XNAH, 0X03H) ........ 403
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X01H) ............................... 403
ALARM AND ERROR STATUS REGISTER (AESR) (INDIRECT ADDRESS = 0XNAH, 0X02H) ............................ 403
13.0 DS1 HDLC Controller Block ............................................................................................................... 404
13.1 DS1 TRANSMIT HDLC CONTROLLER BLOCK ..................................................................................... 404
ALARM AND ERROR INTERRUPT ENABLE REGISTER (AEIER) (INDIRECT ADDRESS = 0XNAH, 0X03H) ......... 404
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X01H) ............................... 404
ALARM AND ERROR STATUS REGISTER (AESR) (INDIRECT ADDRESS = 0XNAH, 0X02H) ............................ 404
13.1.1 Description of the DS1 Transmit HDLC Controller Block ...................................................... 405
TRANSMIT DATA LINK SELECT REGISTER (TSDLSR) (INDIRECT ADDRESS = 0XN0H, 0X0AH) .................... 405
13.1.2 How to configure XRT84L38 to transmit data link information through D or E Channels ..... 406
DATA LINK CONTROL REGISTER (DLCR) INDIRECT ADDRESS = 0XN0H, 0X13H) ........................................ 406
DATA LINK CONTROL REGISTER (DLCR) (INDIRECT ADDRESS = 0XN0H, 0X13H) ....................................... 406
TRANSMIT CHANNEL CONTROL REGISTER (TCCR) (INDIRECT ADDRESS = 0XN2H, 0X00H - 0X1FH) .......... 406
13.1.3 Transmit BOS (Bit Oriented Signaling) Processor ................................................................ 407
TRANSMIT DATA LINK SELECT REGISTER (TSDLSR) (INDIRECT ADDRESS = 0XN0H, 0X0AH) .................... 407
TRANSMIT DATA LINK BYTE COUNT REGISTER (TDLBCR) (INDIRECT ADDRESS = 0XN0H, 0X14H) ............ 408
TRANSMIT DATA LINK BYTE COUNT REGISTER (TDLBCR) (INDIRECT ADDRESS = 0XN0H, 0X14H) ............ 408
DATA LINK CONTROL REGISTER (DLCR) (INDIRECT ADDRESS = 0XN0H, 0X13H) ....................................... 409
DATA LINK CONTROL REGISTER (DLCR) (INDIRECT ADDRESS = 0XN0H, 0X13H) ...................................... 409
DATA LINK CONTROL REGISTER (DLCR) (INDIRECT ADDRESS = 0XN0H, 0X13H) ....................................... 409
DATA LINK INTERRUPT ENABLE REGISTER (DLIER) (INDIRECT ADDRESS = 0XNAH, 0X07H) ....................... 410
XIII
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X00H) ............................. 410
DATA LINK STATUS REGISTER (DLSR) (INDIRECT ADDRESS = 0XNAH, 0X06H) ........................................ 410
13.1.4 Transmit MOS (Message Oriented Signaling) or LAPD Controller ....................................... 411
DATA LINK CONTROL REGISTER (DLCR) (INDIRECT ADDRESS = 0XN0H, 0X13H) ..................................... 411
Figure 127. LAPD Controller ......................................................................................................... 411
Figure 128. LAPD Frame Structure .............................................................................................. 412
TRANSMIT DATA LINK BYTE COUNT REGISTER (TDLBCR) (INDIRECT ADDRESS = 0XN0H, 0X14H) ............ 415
TRANSMIT DATA LINK BYTE COUNT REGISTER (TDLBCR) (INDIRECT ADDRESS = 0XN0H, 0X14H) ........... 416
DATA LINK CONTROL REGISTER (DLCR) (INDIRECT ADDRESS = 0XN0H, 0X13H) ...................................... 416
DATA LINK CONTROL REGISTER (DLCR) (INDIRECT ADDRESS = 0XN0H, 0X13H) ...................................... 416
DATA LINK CONTROL REGISTER (DLCR) (INDIRECT ADDRESS = 0XN0H, 0X13H) ..................................... 417
DATA LINK CONTROL REGISTER (DLCR) (INDIRECT ADDRESS = 0XN0H, 0X13H) ..................................... 417
DATA LINK INTERRUPT ENABLE REGISTER (DLIER) (INDIRECT ADDRESS = 0XNAH, 0X07H) ..................... 417
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X00H) ............................. 418
DATA LINK STATUS REGISTER (DLSR) (INDIRECT ADDRESS = 0XNAH, 0X06H) ........................................ 418
13.1.5 Transmit SLCâ96 Data link Controller .................................................................................. 419
DATA LINK CONTROL REGISTER (DLCR) (INDIRECT ADDRESS = 0XN0H, 0X13H) ..................................... 419
FRAMING SELECT REGISTER (FSR) (INDIRECT ADDRESS = 0XN0H, 0X07H) ............................................. 420
TRANSMIT SLC®96 MESSAGE REGISTERS ............................................................................................... 420
TRANSMIT DATA LINK BYTE COUNT REGISTER (TDLBCR) (INDIRECT ADDRESS = 0XN0H, 0X14H) ........... 421
DATA LINK INTERRUPT ENABLE REGISTER (DLIER) (INDIRECT ADDRESS = 0XNAH, 0X07H) ...................... 421
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X00H) .............................. 422
DATA LINK STATUS REGISTER (DLSR) (INDIRECT ADDRESS = 0XNAH, 0X06H) ........................................ 422
DATA LINK CONTROL REGISTER (DLCR) (INDIRECT ADDRESS = 0XN0H, 0X13H) ..................................... 422
13.2 DS1 RECEIVE HDLC CONTROLLER BLOCK ....................................................................................... 423
13.2.1 Description of the DS1 Receive HDLC Controller Block ...................................................... 423
DATA LINK CONTROL REGISTER (DLCR) (INDIRECT ADDRESS = 0XN0H, 0X13H) ..................................... 423
DATA LINK CONTROL REGISTER (DLCR) (INDIRECT ADDRESS = 0XN0H, 0X13H) ..................................... 423
RECEIVE DATA LINK SELECT REGISTER (RSDLSR) (INDIRECT ADDRESS = 0XN0H, 0X0CH) ..................... 424
13.2.2 How to configure XRT84L38 to Receive data link information through D or E Channels ..... 425
DATA LINK CONTROL REGISTER (DLCR) (INDIRECT ADDRESS = 0XN0H, 0X13H) ..................................... 425
DATA LINK STATUS REGISTER (DLSR) (INDIRECT ADDRESS = 0XNAH, 0X06H) ........................................ 425
RECEIVE CHANNEL CONTROL REGISTER (RCCR) (INDIRECT ADDRESS = 0XN2H, 0X60H - 0X7FH) .......... 425
13.2.3 Receive BOS (Bit Oriented Signaling) Processor ................................................................. 426
RECEIVE DATA LINK SELECT REGISTER (RSDLSR) (INDIRECT ADDRESS = 0XN0H, 0X0CH) ..................... 426
DATA LINK INTERRUPT ENABLE REGISTER (DLIER) (INDIRECT ADDRESS = 0XNAH, 0X07H) ..................... 426
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X00H) ............................. 427
DATA LINK STATUS REGISTER (DLSR) (INDIRECT ADDRESS = 0XNAH, 0X06H) ........................................ 427
DATA LINK INTERRUPT ENABLE REGISTER (DLIER) (INDIRECT ADDRESS = 0XNAH, 0X07H) ..................... 427
DATA LINK STATUS REGISTER (DLSR) (INDIRECT ADDRESS = 0XNAH, 0X06H) ........................................ 428
RECEIVE DATA LINK BYTE COUNT REGISTER (RDLBCR) (INDIRECT ADDRESS = 0XN0H, 0X15H) .............. 428
13.2.4 Receive LAPD Controller ...................................................................................................... 429
RECEIVE DATA LINK BYTE COUNT REGISTER (RDLBCR) (INDIRECT ADDRESS = 0XN0H, 0X15H) ............. 429
DATA LINK STATUS REGISTER (DLSR) (INDIRECT ADDRESS = 0XNAH, 0X06H) ......................................... 429
DATA LINK INTERRUPT ENABLE REGISTER (DLIER) (INDIRECT ADDRESS = 0XNAH, 0X07H) ..................... 430
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X00H) ............................. 430
DATA LINK STATUS REGISTER (DLSR) (INDIRECT ADDRESS = 0XNAH, 0X06H) ........................................ 431
DATA LINK INTERRUPT ENABLE REGISTER (DLIER) (INDIRECT ADDRESS = 0XNAH, 0X07H) ..................... 431
DATA LINK STATUS REGISTER (DLSR) (INDIRECT ADDRESS = 0XNAH, 0X06H) ........................................ 432
DATA LINK INTERRUPT ENABLE REGISTER (DLIER) (INDIRECT ADDRESS = 0XNAH, 0X07H) ..................... 432
DATA LINK STATUS REGISTER (DLSR) (INDIRECT ADDRESS = 0XNAH, 0X06H) ........................................ 432
RECEIVE DATA LINK BYTE COUNT REGISTER (RDLBCR) (INDIRECT ADDRESS = 0XN0H, 0X15H) ............. 433
RECEIVE DATA LINK BYTE COUNT REGISTER (RDLBCR) (INDIRECT ADDRESS = 0XN0H, 0X15H) ............. 433
DATA LINK STATUS REGISTER (DLSR) (INDIRECT ADDRESS = 0XNAH, 0X06H) ........................................ 433
XIV
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
13.2.5 Receive SLCâ96 Data link Controller .................................................................................... 434
RECEIVE SLC®96 MESSAGE REGISTERS .................................................................................................. 434
DATA LINK INTERRUPT ENABLE REGISTER (DLIER) (INDIRECT ADDRESS = 0XNAH, 0X07H) ...................... 435
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X00H) .............................. 435
DATA LINK STATUS REGISTER (DLSR) (INDIRECT ADDRESS = 0XNAH, 0X06H) ......................................... 435
DATA LINK INTERRUPT ENABLE REGISTER (DLIER) (INDIRECT ADDRESS = 0XNAH, 0X07H) ...................... 436
DATA LINK STATUS REGISTER (DLSR) (INDIRECT ADDRESS = 0XNAH, 0X06H) ........................................ 436
RECEIVE DATA LINK BYTE COUNT REGISTER (RDLBCR) (INDIRECT ADDRESS = 0XN0H, 0X15H) ............. 436
14.0 E1 HDLC Controller Block .................................................................................................................. 438
14.1 E1 TRANSMIT HDLC CONTROLLER BLOCK ........................................................................................ 438
14.1.1 Description of the E1 Transmit HDLC Controller Block ......................................................... 438
SYNCHRONIZATION MUX REGISTER (SMR) (INDIRECT ADDRESS = 0XN0H, 0X09H) .................................. 438
14.1.2 How to configure XRT84L38 to transmit data link information through the National bits (Sa4
through Sa8) .................................................................................................................................... 439
DATA LINK CONTROL REGISTER (DLCR) (INDIRECT ADDRESS = 0XN0H, 0X13H) ...................................... 439
TRANSMIT SIGNALING AND DATA LINK SELECT REGISTER (TSDLSR) (INDIRECT ADDRESS = 0XN0H, 0X0AH) ...
439
14.1.3 How to configure XRT84L38 to transmit data link information through Timeslot 16 octet .... 440
14.1.4 How to configure XRT84L38 to transmit data link information through D or E Channels ..... 440
TRANSMIT SIGNALING AND DATA LINK SELECT REGISTER (TSDLSR) (INDIRECT ADDRESS = 0XN0H, 0X0AH) ...
440
TRANSMIT SIGNALING AND DATA LINK SELECT REGISTER (TSDLSR) (INDIRECT ADDRESS = 0XN0H, 0X0AH) ...
440
14.1.5 Transmit BOS (Bit Oriented Signaling) Processor ................................................................ 441
14.1.6 Transmit MOS (Message Oriented Signaling) or LAPD Controller ....................................... 441
14.2 E1 RECEIVE HDLC CONTROLLER BLOCK .......................................................................................... 441
14.2.1 Description of the E1 Receive HDLC Controller Block .......................................................... 441
TRANSMIT CHANNEL CONTROL REGISTER (TCCR) (INDIRECT ADDRESS = 0XN2H, 0X00H - 0X1FH) ......... 441
14.2.2 How to configure XRT84L38 to receive data link information through the National bits (Sa4
through Sa8) .................................................................................................................................... 442
DATA LINK STATUS REGISTER (DLSR) (INDIRECT ADDRESS = 0XNAH, 0X06H) ........................................ 442
RECEIVE SIGNALING AND DATA LINK SELECT REGISTER (RSDLSR) (INDIRECT ADDRESS = 0XN0H, 0X0CH) ....
442
14.2.3 How to configure XRT84L38 to receive data link information through Timeslot 16 octet ...... 443
RECEIVE SIGNALING AND DATA LINK SELECT REGISTER (RSDLSR) (INDIRECT ADDRESS = 0XN0H, 0X0CH) ....
443
14.2.4 How to configure XRT84L38 to receive data link information through D or E Channels ....... 444
14.2.5 Receive BOS (Bit Oriented Signaling) Processor ................................................................. 444
14.2.6 Receive LAPD Controller ...................................................................................................... 444
RECEIVE SIGNALING AND DATA LINK SELECT REGISTER (RSDLSR) (INDIRECT ADDRESS = 0XN0H, 0X0CH) ....
444
RECEIVE CHANNEL CONTROL REGISTER (RCCR) (INDIRECT ADDRESS = 0XN2H, 0X60H - 0X7FH) ........... 444
15.0 Transmit LIU Interface ........................................................................................................................ 446
16.0 Receive LIU Interface .......................................................................................................................... 446
ORDERING INFORMATION ........................................................................................................... 447
PACKAGE DIMENSIONS ............................................................................................................................. 447
REVISIONS ............................................................................................................................................... 448
XV
áç
XRT84L38
OCTAL T1E1/J1 FRAMER
REV.1.0.0
TABLE 1: LIST BY PIN NUMBER
PIN
PIN NAME
PIN
PIN NAME
PIN
PIN NAME
PIN
PIN NAME
A1
TCK
B1
TDI
C1
RxNEG_0
D1
RxLineClk_0
A2
A3
A4
A5
A6
RxTSb0_0
RxSig_0
B2
B3
B4
B5
B6
RxSerClk_0
C2
C3
C4
C5
C6
TMS
D2
D3
D4
D5
D6
RxLOS_0
TDO
RxSync_0
RxCASMSync_0
TxOHClk_0
NC
RxMSync_0
RxCRCMSync_0
TRST
RxTSb2_0
RxTSChn_0
RxTSClk_0
RxOHClk_0
RxSer_0
RxTSb3_0
Rx8kHz_0
RxTSb1_0
RxFrTD_0
TxSer_0
TxMSync_0
TxInClk_0
TxSync_0
A7
A8
TxOH_0
B7
B8
NC
C7
C8
RxOH_0
D7
D8
RxTSb4_0
TxTSb2_0
Tx12.352MHz_0
TxTSb3_0
TxOHSync_0
TxTSb0_0
TxSig_0
TxSerClk_0
A9
RxSer_1
B9
RxSerClk_1
C9
RxMSync_1
RxCRCMSync_1
D9
TxTSb1_0
TxFrTD_0
A10
A11
A12
A13
RxTSb1_1
RxFrTD_1
B10
B11
B12
B13
RxOH_1
C10
C11
C12
C13
TxTSb4_0
D10
D11
D12
D13
TxTSClk_0
RxCASMSync_1
RxSync_1
RxOHClk_1
RxTSb2_1
RxTSChn_1
RxTSClk_1
TxSync_1
NC
RxTSb0_1
RxSig_1
RxTSb4_1
TxSer_1
TxMSync_1
TxInClk_1
NC
RxTSb3_1
Rx8kHz_1
A14
A15
B14
B15
TxTSClk_1
C14
C15
TxOH_1
D14
D15
NC
TxTSb2_1
Tx12.352MHz_1
TxTSb1_1
TxFrTD_1
TxOHClk_1
TxTSb0_1
TxSig_1
A16
TxSerClk_1
B16
RxSync_2
C16
NC
D16
TxTSb3_1
TxOHSync_1
A17
A18
RxSerClk_2
B17
B18
NC
C17
C18
TxTSb4_1
RxSer_2
D17
D18
NC
RxTSb0_2
RxSig_2
RxCASMSync_2
RxTSClk_2
A19
A20
RxMSync_2
RxCRCMSync_2
B19
B20
RxTSb1_2
RxFrTD_2
C19
C20
RxOH_2
D19
D20
RxOHClk_2
TxSerClk_2
NC
RxTSb2_2
RxTSChn_2
RxTSb3_2
Rx8kHz_2
A21
A22
TxSync_2
B21
B22
RxTSb4_2
C21
C22
TxTSClk_2
D21
D22
TxOHClk_2
TxTSb4_2
TxMSync_2
TxInClk_2
TxSer_2
TxTSb1_2
TxFrTD_2
A23
A24
A25
A26
TxTSb0_2
TxSig_2
B23
B24
B25
B26
TxTSb2_2
Tx12.352MHz_2
C23
C24
C25
C26
NC
D23
D24
D25
D26
TxOH_2
RxCASMSync_3
TxTSClk_3
TxTSb3_2
TxOHSync_2
RxSer_3
RxOHClk_3
RxOH_3
RxSync_3
RxTSClk_3
RxTSb0_3
RxSig_3
RxMSync_3
RxCRCMSync_3
RxTSb1_3
RxFrTD_3
RxTSb3_3
Rx8kHz_3
16
XRT84L38
OCTAL T1E1/J1 FRAMER
REV. 1.0.0
áç
PIN
PIN NAME
PIN
PIN NAME
PIN
PIN NAME
PIN
PIN NAME
E1
NC
F1
RxNEG_1
G1
RxLineClk_1
H1
RxPOS_2
E2
E3
NC
F2
F3
TxLineClk_0
G2
G3
TxLineClk_1
RxPOS_1
H2
H3
TxNEG_1
TxMX_1
TxPOS_0
TxNRZ_0
TxNEG_0
TxMX_0
TxPOS_1
TxNRZ_1
E4
RxPOS_0
F4
NC
G4
LOS_0
H4
RxLOS_1
E23
RxSerClk_3
F23
TxOH_3
G23
TxSerClk_3
H23
TxTSb1_3
TxFrTD_3
E24
RxTSb2_3
RxTSChn_3
F24
TxOHClk_3
TxSer_3
G24
TxTSb0_3
TxSig_3
H24
TxTSb3_3
TxOHSync_3
E25
E26
TxSync_3
F25
F26
G25
G26
CS
H25
H26
NC
RxTSb4_3
TxMSync_3
TxInClk_3
WR
NC
PIN
PIN NAME
PIN
PIN NAME
PIN
PIN NAME
PIN
PIN NAME
J1
RxLOS_2
K1
LOS_2
L1
TxPOS_3
TxNRZ_3
M1
GPO3
CS0
J2
J3
J4
TxLineClk_2
RxNEG_2
LOS_1
K2
K3
K4
TxNEG_2
TxMX_2
L2
L3
RxPOS_3
M2
M3
LOS_3
TxPOS_2
TxNRZ_2
RxNEG_3
TxNEG_3
TxMX_3
RxLineClk_2
L4
RxLOS_3
VDD
VDD
VDD
VDD
VDD
VDD
A4
M4
RxLineClk_3
L11
L12
L13
L14
L15
L16
L23
M11
M12
M13
M14
M15
M16
M23
VDD
VDD
VSS
VSS
VDD
VDD
J23
TxTSb2_3
K23
A6
NC
Tx12.352MHz_3
J24
J25
J26
Data7
TxTSb4_3
A5
K24
K25
K26
Data6
Data5
NC
L24
L25
L26
Data4
Blast
A3
M24
M25
M26
INT
µPType2
A2
17
áç
XRT84L38
OCTAL T1E1/J1 FRAMER
REV.1.0.0
PIN
PIN NAME
PIN
PIN NAME
PIN
PIN NAME
PIN
PIN NAME
N1
GPO0
SDO0
P1
GPO7
CS1
R1
GPO4
SDO1
T1
OSCClk
N2
N3
N4
GPO2
SClk0
P2
P3
P4
GPO6
SClk1
R2
R3
R4
RxPOS_4
T2
T3
T4
RxNEG_4
GPO1
SDI0
Test Mode
Reset
RxLineClk_4
TxLineClk_3
GPO5
SDI1
LOP
TxPOS_4
TxNRZ_4
N11
N12
N13
N14
N15
N16
N23
N24
N25
N26
VDD
VDD
R11
R12
R13
R14
R15
R16
R23
R24
R25
R26
VDD
VDD
VSS
T11
T12
T13
T14
T15
T16
T23
T24
T25
T26
VSS
VSS
VSS
P13
P14
VSS
VSS
VSS
VSS
VSS
VSS
VDD
VDD
VDD
µPClk
Data0
Data1
RD
VSS
VDD
VSS
A1
P23
P24
P25
P26
RDY_DTACK
µPType1
DBEn
ACK1
Indirect
µPType0
Req0
ALE_AS
Data3
Data2
A0
PIN
PIN NAME
PIN
PIN NAME
PIN
PIN NAME
PIN
PIN NAME
U1
RxLOS_4
V1
TxNEG_4
TxMX_4
W1
RxNEG_5
Y1
RxLOS_5
U2
U3
8kHzRef
NC
V2
V3
LOS_4
W2
W3
RxPOS_5
Y2
Y3
TxNEG_5
TxMX_5
NC
TxPOS_5
TxNRZ_5
TxLineClk_5
U4
NC
V4
TxLineClk_4
RxOHClk_4
W4
RxLineClk_5
Y4
NC
U23
Req1
V23
W23
RxTSb3_4
Rx8kHz_4
Y23
TxSerClk_4
U24
U25
U26
RxSerClk_4
NC
V24
V25
V26
RxTSClk_4
W24
W25
W26
RxTSb0_4
RxSig_4
Y24
Y25
Y26
RxCASMSync_4
RxMSync_4
RxCRCMSync_4
RxOH_4
RxTSb2_4
RxTSChn_4
ACK0
RxSync_4
RxSer_4
RxTSb1_4
RxFrTD_4
18
XRT84L38
OCTAL T1E1/J1 FRAMER
REV. 1.0.0
áç
PIN
PIN NAME
PIN
PIN NAME
PIN
PIN NAME
PIN
PIN NAME
AA1
LOS_5
AB1
RxNEG_6
AC1
TxNEG_6
TxMX_6
AD1
RxNEG_7
AA2
RxPOS_6
AB2
TxPOS_6
TxNRZ_6
AC2
RxPOS_7
AD2
TxPOS_7
TxNRZ_7
AA3
AA4
RxLOS_6
AB3
AB4
LOS_6
AC3
AC4
AC5
AC6
TxLineClk_6
TxLineClk_7
TxTSClk_7
TxSerClk_7
RxLineClk_6
RxLOS_7
AD5
AD6
TxOH_7
TxTSb1_7
TxFrTD_7
AC7
AC8
TxTSb0_7
TxSig_7
AD7
AD8
RxSerClk_7
RxMSync_7
RxSer_7
RxCRCMSync_7
AC9
AC10
AC11
AC12
RxTSClk_7
RxCASMSync_7
RxOH_7
AD9
AD10
AD11
AD12
TxSerClk_6
RxOHClk_7
TxTSb4_6
TxTSb3_6
RxCASMSync_6
TxOHSync_6
AC13
TxTSb0_6
TxSig_6
AD13
TxOHClk_6
AC14
AC15
AC16
TxOH_6
AD14
AD15
AD16
RxSync_6
RxTSb4_6
RxSerClk_6
RxTSb0_6
RxSig_6
RxTSb2_6
RxTSChn_6
AC17
AC18
TxOH_5
AD17
AD18
RxOHClk_6
TxSerClk_5
TxTSb3_5
TxOHSync_5
AC19
AC20
AC21
TxSync_5
RxOH_5
AD19
AD20
AD21
TxSer_5
TxOHClk_5
RxTSb4_5
RxTSb1_5
RxFrTD_5
AC22
RxSync_5
AD22
RxTSb0_5
RxSig_5
AA23
AA24
TxSync_4
TxOH_4
AC23
AC24
NC
AD23
AD24
RxCASMSync_5
AB24
TxTSB0_4
TxSig_4
TxTSb1_4
TxFrTD_4
RxMSync_5
RxCRCMSync_5
AA25
AA26
NC
AB25
AB26
TxTSClk_4
AC25
AC26
TxOHClk_4
AD25
AD26
RxTSClk_5
RxTSb4_4
TxSer_4
TxMSync_4
TxInClk_4
NC
19
áç
XRT84L38
OCTAL T1E1/J1 FRAMER
REV.1.0.0
PIN
PIN NAME
PIN
PIN NAME
AE1
TxNEG_7
TxMX_7
AF1
LOS_7
AE2
AE3
AE4
RxLineClk_7
AF2
AF3
AF4
NC
NC
TxOHClk_7
TxTSb4_7
TxTSb3_7
TxOHSync_7
AE5
AE6
TxTSb2_7
Tx12.352MHz_7
AF5
AF6
TxSer_7
TxSync_7
RxTSb4_7
TxMSync_7
TxInClk_7
AE7
AE8
RxSync_7
AF7
AF8
RxTSb3_7
Rx8kHz_7
RxTSb2_7
RxTSChn_7
AE9
RxTSb1_7
RxFrTD_7
AF9
RxTSb0_7
RxSig_7
AE10
TxSync_6
AF10
TxMSync_6
TxInClk_6
AE11
AE12
TxSer_6
AF11
AF12
NC
TxTSb2_6
Tx12.352MHz_6
TxTSb1_6
TxFrTD_6
AE13
TxTSClk_6
AF13
RxMSync_6
RxCRCMSync_6
AE14
AE15
AE16
NC
NC
AF14
AF15
AF16
NC
RxTSClk_6
RxSer_6
RxTSb3_6
Rx8kHz_6
AE17
NC
AF17
RxTSb1_6
RxFrTD_6
AE18
AE19
TxTSb4_5
AF18
AF19
RxOH_6
TxTSb2_5
Tx12.352MHz_5
TxTSb1_5
TxFrTD_5
AE20
AE21
AE22
AE23
TxTSClk_5
AF20
AF21
AF22
AF23
TxTSb0_5
TxSig_5
RxOHClk_5
TxMSync_5
TxInClk_5
RxTSb3_5
Rx8kHz_5
NC
RxSer_5
RxTSb2_5
RxTSChn_5
AE24
AE25
AE26
TxTSb4_4
NC
AF24
AF25
AF26
NC
RxSerClk_5
TxTSb2_4
TxTSb3_4
Tx12.352MHz_4
TxOHSync_4
20
XRT84L38
OCTAL T1/E1/J1 FRAMER
áç
1.0.0
PIN DESCRIPTIONS
TRANSMIT SERIAL DATA INPUT
(Framer Channel Number indicated by _n)
SIGNAL NAME
PIN #
TYPE
DESCRIPTION
TxSer_0
TxSer_1
TxSer_2
TxSer_3
TxSer_4
TxSer_5
TxSer_6
TxSer_7
B6
A14
B22
I
Transmit Serial Data Input—Transmit Framer_n:
This input pin along with TxSerClk_n functions as the Transmit Serial input port
for Framer_n.
F25
DS1 Mode:
AB26
AD19
AE11
AF5
Any payload data applied to this pin would be inserted into a DS1 frame and
output onto the T1 line via the TxPOS_n and TxNEG_n output pins. If
Framer_n is configured accordingly, the framing alignment bits, the facility data
link bits and the CRC-6 bits can also be inserted to input pin.The signal applied
to this input pin can be latched to the Transmit Payload Data Input Interface on
either the rising edge or the falling edge of TxSerClk_n according to configura-
tions of Framer_n.
E1 Mode:
Any payload data applied to this pin would be inserted into an E1 frame and
output onto the E1 line via the TxPOS_n and TxNEG_n output pins. All data
intended to be transported via Time Slots 1 through 15 and Time slots 17
through 31, within each E1 frame, must be applied to this input pin. If Framer_n
is configured accordingly, data intended for Time Slots 0 and 16 can also be
applied to this input pin.
21
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
TRANSMIT SERIAL DATA INPUT
(Framer Channel Number indicated by _n)
SIGNAL NAME
PIN #
TYPE
DESCRIPTION
TxSerClk_0
TxSerClk_1
TxSerClk_2
TxSerClk_3
TxSerClk_4
TxSerClk_5
TxSerClk_6
TxSerClk_7
D8
A16
D20
G23
Y23
AC18
AD9
AC6
I or O Transmit Serial Clock Signal --Transmit Framer_n:
This clock signal is used by the Transmit payload data Input Interface, to latch
the contents of the TxSer_n signal into the Octal T1/E1/J1 Framer IC. Data that
is applied at the TxSer_n input is latched into the Transmit payload data Input
Interface (for Framer_n) on either the rising edge or the falling edge of
TxSerClk_n depending on configurations of Framer_n. TxSerClk_n can either
be an input or an output.
DS1 Mode:
Transmit Back-plane Interface-1.544 MHz Clock Mode
If TxMUXEN = 0 and TxIMODE[1:0] = 00 in Transmit interface control register,
Transmit back-plane interface of Framer_n is taking data at a rate of 1.544
Mbit/s. If the Transmit Section of Framer_n has been configured to use the
TxSerClk_n signal as the timing source, then this signal will be an Input. If the
Transmit Section of Framer_n has been configured to use either the
RxLineClk_n signal or the OSCClk signal as the timing source, then
TxSerClk_n will be an Output.
Transmit Back-plane Interface-High Speed Clock Mode
If TxMUXEN ≠ 0 and TxIMODE[1:0] ≠ 00 in Transmit interface control register,
Transmit back-plane interface of Framer_n is operating at a high-speed mode
and is taking data at rates of 2.048 Mbit/s, 4.096 Mbit/s, 8.192 Mbit/s, 12.352
Mbit/s or 16.384 Mbit/s. The TxSerClk_n signal will be an Input clock signal
running at 1.544 MHz.
E1 Mode:
Transmit Back-plane Interface-2.048 MHz Clock Mode
If TxMUXEN = 0 and TxIMODE[1:0] = 00 in Transmit interface control register,
Transmit back-plane interface of Framer_n is taking data at a rate of 2.048
Mbit/s. If the Transmit Section of Framer_n has been configured to use the
TxSerClk_n signal as the timing source, then this signal will be an Input. If the
Transmit Section of Framer_n has been configured to use either the
RxLineClk_n signal or the OSCClk signal as the timing source, then
TxSerClk_n will be an Output.
Transmit Back-plane Interface-High Speed Clock Mode
If TxMUXEN ≠ 0 or TxIMODE[1:0] ≠ 00 in Transmit interface control register,
Transmit back-plane interface of Framer_n is operating at a high-speed mode.
The TxSerClk_n signal will be an Input clock signal running at 2.048 MHz.
22
XRT84L38
OCTAL T1/E1/J1 FRAMER
áç
1.0.0
TRANSMIT SERIAL DATA INPUT
(Framer Channel Number indicated by _n)
SIGNAL NAME
PIN #
TYPE
DESCRIPTION
TxSync_0
TxSync_1
TxSync_2
TxSync_3
TxSync_4
TxSync_5
TxSync_6
TxSync_7
D6
A12
A21
I or O Single Frame Sync Pulse Input/Output—Transmit Framer_n:
This pin is configured to be an input if the TxSerClk_n input pin is configured
to be the timing reference for the Transmit Portion of Framer_n. This pin is con-
figured as an output if the RxLineClk_n input pin or the OSCClk input pins are
configured to be the timing reference for the Transmit portion of Framer_n.
DS1 Mode:
E25
AA23
AC19
AE10
AF6
When pin is configured to be an Input
If this pin is configured to be an input, then the user must pulse this pin "High"
for one period of TxSerClk_n, when the Transmit payload data Input Interface
(of Framer_n) is processing the first bit (F-bit) of an outbound DS1 frame.
NOTE: It is imperative that the TxSync_n input signal be synchronized with the
TxSerClk_n input signal.
When pin is configured to be an Output
If this pin is configured to be an output, then it will pulse "High", for one period
of TxSerClk_n, when the Transmit payload data Input Interface (of Framer_n)
is processing the last payload bit within an outbound DS1 frame.
E1 Mode:
When pin is configured to be an Input
If this pin is configured to be an input, then the user must pulse this pin "High"
for one period of TxSerClk_n, when the Transmit payload data Input Interface
(of Framer_n) is processing the International Bit (Si) of an outbound E1 frame.
NOTE: It is imperative that the TxSync_n input signal be synchronized with the
TxSerClk_n input signal.
When pin is configured to be an Output
If this pin is configured to be an output, then it will pulse "High", for one period
of TxSerClk_n, when the Transmit payload data Input Interface (of Framer_n)
is processing the last bit within a given outbound E1 frame.
23
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
TRANSMIT SERIAL DATA INPUT
(Framer Channel Number indicated by _n)
SIGNAL NAME
PIN #
TYPE
DESCRIPTION
TxMSync_0
TxMSync_1
TxMSync_2
TxMSync_3
TxMSync_4
TxMSync_5
TxMSync_6
TxMSync_7
C6
B13
A22
I or O Multiframe Sync Pulse Input/Output—Framer_n:
This signal indicates the boundary of an outbound multi-frame.
DS1 Mode:
F26
Transmit Back-plane Interface-1.544 MHz Clock Mode
If TxMUXEN = 0 and TxIMODE[1:0] = 00 in Transmit interface control register,
Transmit back-plane interface of Framer_n is taking data at a rate of 1.544
Mbit/s. This pin is configured to be an Input if the TxSerClk_n input pin is con-
figured to be the timing reference for the Transmit section of Framer_n. Con-
versely, this pin will be configured as an Output if the RxLineClk input pin or
the OSCClk input pins are configured to be the timing reference for the Trans-
mit section of Framer_n.The roles of these pins when configured as input or
output, is described below.
AC26
AF21
AF10
AE6
When pin is configured to be an Input
If this pin is configured to be an input, this pin must be pulsed "High" for one
period of TxSerClk_n, the instant that the Transmit payload data Interface (of
Framer_n) is processing the first bit of a DS1 Multi-frame.
NOTE: It is imperative that the TxMSync_n input signal be synchronized with
the TxSerClk_n input signal.
When pin is configured to be an Output
If this pin is configured to be an output, then it will pulse "High", for one period
of TxSerClk_n, when the Transmit payload data Input Interface (of Framer_n)
is processing the last bit of a DS1 Multi-frame.
E1 Mode:
Transmit Back-plane Interface-2.048 MHz Clock Mode
If TxMUXEN = 0 and TxIMODE[1:0] = 00 in Transmit interface control register,
Transmit back-plane interface of Framer_n is taking data at a rate of 2.048
Mbit/s. This pin is configured to be an Input if the TxSerClk_n input pin is con-
figured to be the timing reference for the Transmit section of Framer_n. Con-
versely, this pin will be configured as an Output if the RxLineClk input pin or
the OSCClk input pins are configured to be the timing reference for the Trans-
mit section of Framer_n.
When pin is configured to be an Input
If this pin is configured to be an input, this pin must be pulsed "High" for one
period of TxSerClk_n, the instant that the Transmit payload data Interface (of
Framer_n) is processing the first International Bit (Si) of an "outbound" CRC
payload data Multiframe.
NOTES:
1. This pin is ignored if CRC Multiframe Alignment has been disabled.
2. It is imperative that the TxMSync_n input signal be synchronized with
the TxSerClk_n input signal.
When pin is configured to be an Output
If this pin is configured to be an output, then it will pulse "High", for one period
of TxSerClk_n, when the Transmit payload data Input Interface (of Framer_n)
is processing the last bit, within an "outbound" CRC Multi-frame.
NOTES:
1. This pin is inactive if CRC Multi-frame Alignment has been disabled.
2. The purpose of this output pin is to permit the Terminal Equipment to
maintain alignment with the "outbound" CRC-Multi-frame structure.
24
XRT84L38
OCTAL T1/E1/J1 FRAMER
áç
1.0.0
TRANSMIT SERIAL DATA INPUT
(Framer Channel Number indicated by _n)
SIGNAL NAME
PIN #
TYPE
DESCRIPTION
TxInClk_0
TxInClk_1
TxInClk_2
TxInClk_3
TxInClk_4
TxInClk_5
TxInClk_6
TxInClk_7
C6
B13
A22
I
Transmit Input Clock Signal -- Transmit Framer _n
If TxMUXEN ≠ 0 or TxIMODE[1:0] ≠ 00 in Transmit interface control register,
Transmit back-plane interface of Framer_n is operating at a high-speed mode.
This pin will function as an input clock signal for the high-speed Transmit back-
plane interface.
F26
AC26
AF21
AF10
AE6
DS1 Mode:
Transmit Back-plane Interface-MVIP, 2.048 MHz Clock Mode
If TxMUXEN = 0 and TxIMODE[1:0] = 01 in Transmit interface control register,
Transmit back-plane interface of Framer_n is taking data at a rate of 2.048
Mbit/s. The TxInClk_n signal will be an Input clock signal running at 2.048
MHz.
Transmit Back-plane Interface-4.096 MHz Clock Mode
If TxMUXEN = 0 and TxIMODE[1:0] = 10 in Transmit interface control register,
Transmit back-plane interface of Framer_n is taking data at a rate of 4.096
Mbit/s. The TxInClk_n signal will be an Input clock signal running at 4.096
MHz.
Transmit Back-plane Interface-8.192 MHz Clock Mode
If TxMUXEN = 0 and TxIMODE[1:0] = 11 in Transmit interface control register,
Transmit back-plane interface of Framer_n is taking data at a rate of 8.192
Mbit/s. The TxInClk_n signal will be an Input clock signal running at 8.192
MHz.
Transmit Back-plane Interface-Multiplexed at 12.352 MHz Clock Mode
If TxMUXEN = 1 and TxIMODE[1:0] = 00 in Transmit interface control register,
Transmit back-plane interface of Framer_n is taking multiplexed data at a rate
of 12.352 Mbit/s. TxInClk_0 and TxInClk_4 signals will be Input clock signals
running at 12.352 MHz. TxInClk_1, 2, 3 and TxInClk_5, 6, 7 signals are not
required. Transmit Payload data of Channel 0, 1, 2 and 3 are multiplexed and
latched into Transmit back-plane interface using clock edge of TxInClk_0 via
TxSer_0 input pin. Transmit Payload data of Channel 4, 5, 6 and 7 are multi-
plexed and latched into Transmit back-plane interface using clock edge of
TxInClk_4 via TxSer_4 input pin. Inside the Octal Framer, data will be de-multi-
plexed into 8 channels from the serial inputs of Channel 0 and 4.
Transmit Back-plane Interface-Multiplexed at 16.384 MHz Clock Mode
If TxMUXEN = 1 and TxIMODE[1:0] = 01 in Transmit interface control register,
Transmit back-plane interface of Framer_n is taking multiplexed data at a rate
of 16.384 Mbit/s. TxInClk_0 and TxInClk_4 signals will be Input clock signals
running at 16.384 MHz. TxInClk_1, 2, 3 and TxInClk_5, 6, 7 signals are not
required. Transmit Payload data of Channel 0, 1, 2 and 3 are multiplexed and
latched into Transmit back-plane interface using clock edge of TxInClk_0 via
TxSer_0 input pin. Transmit Payload data of Channel 4, 5, 6 and 7 are multi-
plexed and latched into Transmit back-plane interface using clock edge of
TxInClk_4 via TxSer_4 input pin. Inside the Octal Framer, data will be de-multi-
plexed into 8 channels from the serial inputs of Channel 0 and 4.
Transmit Back-plane Interface-HMVIP, 16.384 MHz Clock Mode
If TxMUXEN = 1 and TxIMODE[1:0] = 10 in Transmit interface control register,
Transmit back-plane interface of Framer_n is taking multiplexed data at a rate
of 16.384 Mbit/s. TxInClk_0 and TxInClk_4 signals will be Input clock signals
running at 16.384 MHz. TxInClk_1, 2, 3 and TxInClk_5, 6, 7 signals are not
required. Transmit Payload data of Channel 0, 1, 2 and 3 are multiplexed and
latched into Transmit back-plane interface using clock edge of TxInClk_0 via
TxSer_0 input pin. Transmit Payload data of Channel 4, 5, 6 and 7 are multi-
plexed and latched into Transmit back-plane interface using clock edge of
TxInClk_4 via TxSer_4 input pin. Inside the Octal Framer, data will be de-multi-
plexed into 8 channels from the serial inputs of Channel 0 and 4.
25
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
TRANSMIT SERIAL DATA INPUT
(Framer Channel Number indicated by _n)
SIGNAL NAME
PIN #
TYPE
DESCRIPTION
TxInClk_0
TxInClk_1
TxInClk_2
TxInClk_3
TxInClk_4
TxInClk_5
TxInClk_6
TxInClk_7
C6
B13
A22
I
Transmit Input Clock Signal -- Transmit Framer _n (continued)
Transmit Back-plane Interface-H.100, 16.384 MHz Clock Mode
If TxMUXEN = 1 and TxIMODE[1:0] = 11 in Transmit interface control register,
Transmit back-plane interface of Framer_n is taking multiplexed data at a rate
of 16.384 Mbit/s. TxInClk_0 and TxInClk_4 signals will be Input clock signals
running at 16.384 MHz. TxInClk_1, 2, 3 and TxInClk_5, 6, 7 signals are not
required. Transmit Payload data of Channel 0, 1, 2 and 3 are multiplexed and
latched into Transmit back-plane interface using clock edge of TxInClk_0 via
TxSer_0 input pin. Transmit Payload data of Channel 4, 5, 6 and 7 are multi-
plexed and latched into Transmit back-plane interface using clock edge of
TxInClk_4 via TxSer_4 input pin. Inside the Octal Framer, data will be de-multi-
plexed into 8 channels from the serial inputs of Channel 0 and 4.
E1 Mode:
F26
AC26
AF21
AF10
AE6
Transmit Back-plane Interface-2.048 MHz Clock Mode
If TxMUXEN = 0 and TxIMODE[1:0] = 01 in Transmit interface control register,
Transmit back-plane interface of Framer_n is taking data at a rate of 2.048
Mbit/s. The TxInClk_n signal will be an Input clock signal running at 2.048
MHz.
Transmit Back-plane Interface-4.096 MHz Clock Mode
If TxMUXEN = 0 and TxIMODE[1:0] = 10 in Transmit interface control register,
Transmit back-plane interface of Framer_n is taking data at a rate of 4.096
Mbit/s. The TxInClk_n signal will be an Input clock signal running at 4.096
MHz.
Transmit Back-plane Interface-8.192 MHz Clock Mode
If TxMUXEN = 0 and TxIMODE[1:0] = 11 in Transmit interface control register,
Transmit back-plane interface of Framer_n is taking data at a rate of 8.192
Mbit/s. The TxInClk_n signal will be an Input clock signal running at 8.192
MHz.
Transmit Back-plane Interface-Multiplexed at 16.384 MHz Clock Mode
If TxMUXEN = 1 and TxIMODE[1:0] = 01 in Transmit interface control register,
Transmit back-plane interface of Framer_n is taking multiplexed data at a rate
of 16.384 Mbit/s. TxInClk_0 and TxInClk_4 signals will be Input clock signals
running at 16.384 MHz. TxInClk_1, 2, 3 and TxInClk_5, 6, 7 signals are not
required. Transmit Payload data of Channel 0, 1, 2 and 3 are multiplexed and
latched into Transmit back-plane interface using clock edge of TxInClk_0 via
TxSer_0 input pin. Transmit Payload data of Channel 4, 5, 6 and 7 are multi-
plexed and latched into Transmit back-plane interface using clock edge of
TxInClk_4 via TxSer_4 input pin. Inside the Octal Framer, data will be de-multi-
plexed into 8 channels from the serial inputs of Channel 0 and 4.
Transmit Back-plane Interface-HMVIP, 16.384 MHz Clock Mode
If TxMUXEN = 1 and TxIMODE[1:0] = 10 in Transmit interface control register,
Transmit back-plane interface of Framer_n is taking multiplexed data at a rate
of 16.384 Mbit/s. TxInClk_0 and TxInClk_4 signals will be Input clock signals
running at 16.384 MHz. TxInClk_1, 2, 3 and TxInClk_5, 6, 7 signals are not
required. Transmit Payload data of Channel 0, 1, 2 and 3 are multiplexed and
latched into Transmit back-plane interface using clock edge of TxInClk_0 via
TxSer_0 input pin. Transmit Payload data of Channel 4, 5, 6 and 7 are multi-
plexed and latched into Transmit back-plane interface using clock edge of
TxInClk_4 via TxSer_4 input pin. Inside the Octal Framer, data will be de-multi-
plexed into 8 channels from the serial inputs of Channel 0 and 4.
26
XRT84L38
OCTAL T1/E1/J1 FRAMER
áç
1.0.0
TRANSMIT SERIAL DATA INPUT
(Framer Channel Number indicated by _n)
SIGNAL NAME
PIN #
TYPE
DESCRIPTION
TxInClk_0
TxInClk_1
TxInClk_2
TxInClk_3
TxInClk_4
TxInClk_5
TxInClk_6
TxInClk_7
C6
B13
A22
I
Transmit Input Clock Signal -- Transmit Framer _n (continued)
Transmit Back-plane Interface-H.100, 16.384 MHz Clock Mode
If TxMUXEN = 1 and TxIMODE[1:0] = 11 in Transmit interface control register,
Transmit back-plane interface of Framer_n is taking multiplexed data at a rate
of 16.384 Mbit/s. TxInClk_0 and TxInClk_4 signals will be Input clock signals
running at 16.384 MHz. TxInClk_1, 2, 3 and TxInClk_5, 6, 7 signals are not
required. Transmit Payload data of Channel 0, 1, 2 and 3 are multiplexed and
latched into Transmit back-plane interface using clock edge of TxInClk_0 via
TxSer_0 input pin. Transmit Payload data of Channel 4, 5, 6 and 7 are multi-
plexed and latched into Transmit back-plane interface using clock edge of
TxInClk_4 via TxSer_4 input pin. Inside the Octal Framer, data will be de-multi-
plexed into 8 channels from the serial inputs of Channel 0 and 4.
F26
AC26
AF21
AF10
AE6
TxTSb0_0
TxTSb0_1
TxTSb0_2
TxTSb0_3
TxTSb0_4
TxTSb0_5
TxTSb0_6
TxTSb0_7
C8
D15
A23
G24
AB24
AF20
AC13
AC7
O
Transmit Framer_n--Time Slot Octet Identifier Output-Bit [0:4]:
These output signals (TxTSb4_n through TxTSb0_n) reflects the five-bit binary
value of the number of Time Slot (in the incoming DS1 frame), being accepted
and processed by the Transmit Payload Data Input Interface block associated
with Framer_n.
Terminal Equipment should use the TxTSClk_n clock signal to sample the five
output pins of each channel in order to identify the time-slot being processed
by the Transmit Payload Data Input Interface block of Framer_n.
TxSig_0
TxSig_1
TxSig_2
TxSig_3
TxSig_4
TxSig_5
TxSig_6
TxSig_7
C8
D15
A23
G24
AB24
AF20
AC13
AC7
I
Transmit Serial Signaling Input--Transmit Framer_n
These pins can be used to input robbed-bit signaling data within an outbound
DS1 frame or to input Channel Associated Signaling (CAS) bits within an out-
bound E1 frame, if Framer_n is configured accordingly.
TxTSb1_0
TxTSb1_1
TxTSb1_2
TxTSb1_3
TxTSb1_4
TxTSb1_5
TxTSb1_6
TxTSb1_7
D9
B15
C22
O
Transmit Framer_n--Time Slot Octet Identifier Output-Bit 1:
These output signals (TxTSb4_n through TxTSb0_n) reflects the five-bit binary
value of the number of Time Slot (in the incoming DS1 frame), being accepted
and processed by the Transmit Payload Data Input Interface block associated
with Framer_n.
Terminal Equipment should use the TxTSClk_n clock signal to sample the five
output pins of each channel in order to identify the time-slot being processed
by the Transmit Payload Data Input Interface block of Framer_n.
H23
AC24
AF19
AF12
AD6
TxFrTD_0
TxFrTD_1
TxFrTD_2
TxFrTD_3
TxFrTD_4
TxFrTD_5
TxFrTD_6
TxFrTD_7
D9
B15
C22
I
Transmit Serial Fractional T1/E1 Input--Transmit Framer_n
These pins can be used to input fractional DS1/E1 payload data within an out-
bound DS1/E1 frame, if Framer_n is configured accordingly. In this mode, ter-
minal equipment will use either TxTSClk_n or TxSerClk_n output pins to clock
out fractional DS1/E1 payload data. Framer_n will then use TxTSClk_n or
TxSerClk_n to clock in fractional DS1/E1 payload data. Please see pin
description of TxTSClk_n for details.
H23
AC24
AF19
AF12
AD6
27
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
TRANSMIT SERIAL DATA INPUT
(Framer Channel Number indicated by _n)
SIGNAL NAME
PIN #
TYPE
DESCRIPTION
TxTSb2_0
TxTSb2_1
TxTSb2_2
TxTSb2_3
TxTSb2_4
TxTSb2_5
TxTSb2_6
TxTSb2_7
A8
A15
B23
J23
AE26
AE19
AE12
AE5
O
Transmit Framer_n--Time Slot Octet Identifier Output-Bit 2:
These output signals (TxTSb4_n through TxTSb0_n) reflects the five-bit binary
value of the number of Time Slot (in the incoming DS1 frame) being accepted
and processed by the Transmit Payload Data Input Interface block associated
with Framer_n.
Terminal Equipment should use the TxTSClk_n clock signal to sample the five
output pins of each channel in order to identify the time-slot being processed
by the Transmit Payload Data Input Interface block of Framer_n.
If TxTSb1_n pin is configured as TxFrTD_n to input fractional DS1 payload
data into Framer_n, the TxTSb2_n pin will serially output the five-bit binary
value of the number of the Time Slot being accepted and processed by the
Transmit Payload Data Input Interface block associated with Framer_n.
Tx12.352MHz_0
Tx12.352MHz_1
Tx12.352MHz_2
Tx12.352MHz_3
Tx12.352MHz_4
Tx12.352MHz_5
Tx12.352MHz_6
Tx12.352MHz_7
A8
A15
B23
J23
AE26
AE19
AE12
AE5
O
Transmit 12.352MHz Clock Output-Transmit Framer_n:
These pins can be used to output 12.352MHz clock derived from OSCClk, if
Framer_n is configured accordingly.
TxTSb3_0
TxTSb3_1
TxTSb3_2
TxTSb3_3
TxTSb3_4
TxTSb3_5
TxTSb3_6
TxTSb3_7
B8
D16
A24
H24
AF26
AD18
AC12
AF4
O
Transmit Framer_n-Time Slot Octet Identifier Output-Bit 3:
These output signals (TxTSb4_n through TxTSb0_n) reflects the five-bit binary
value of the number of Time Slot (in the incoming DS1 frame) being accepted
and processed by the Transmit Payload Data Input Interface block associated
with Framer_n.
Terminal Equipment should use the TxTSClk_n clock signal to sample the five
output pins of each channel in order to identify the time-slot being processed
by the Transmit Payload Data Input Interface block of Framer_n.
TxOHSync_0
TxOHSync_1
TxOHSync_2
TxOHSync_3
TxOHSync_4
TxOHSync_5
TxOHSync_6
TxOHSync_7
B8
D16
A24
H24
AF26
AD18
AC12
AF4
O
Transmit Overhead Synchronization Pulse--Transmit Framer_n:
These pins can be used to output Overhead Synchronization Pulse that indi-
cate the first bit of each multi-frame, if Framer_n is configured accordingly.
TxTSb4_0
TxTSb4_1
TxTSb4_2
TxTSb4_3
TxTSb4_4
TxTSb4_5
TxTSb4_6
TxTSb4_7
C10
C17
D22
O
Transmit Framer_n--Time Slot Octet Identifier Output-Bit 4:
These output signals (TxTSb4_n through TxTSb0_n) reflects the five-bit binary
value of the number of Time Slot (in the incoming DS1 frame) being accepted
and processed by the Transmit Payload Data Input Interface block associated
with Framer_n.
Terminal Equipment should use the TxTSClk_n clock signal to sample the five
output pins of each channel in order to identify the time-slot being processed
by the Transmit Payload Data Input Interface block of Framer_n.
J25
AE24
AE18
AD11
AE4
28
XRT84L38
OCTAL T1/E1/J1 FRAMER
áç
1.0.0
TRANSMIT SERIAL DATA INPUT
(Framer Channel Number indicated by _n)
SIGNAL NAME
PIN #
TYPE
DESCRIPTION
TxTSClk_0
TxTSClk_1
TxTSClk_2
TxTSClk_3
TxTSClk_4
TxTSClk_5
TxTSClk_6
TxTSClk_7
D10
B14
C21
O
Transmit Channel Clock Output Signal—Framer_n:
This pin indicates the boundary of each time slot of an outbound DS1/E1
frame.
D25
DS1 Mode:
AB25
AE20
AE13
AC5
Each of these output pins are a 192kHz clock output which pulses "High"
whenever the Transmit Payload Data Input Interface block accepts the LSB of
each of the 24 time slots, within the DS1 data stream, being processed via
Framer _n. The Terminal Equipment should use this clock signal to sample the
TxTSb0_n through TxTSb4_n output signals and identify the time-slot being
processed via the "Transmit Section" of each Framer_n.
If TxTSb1_n pin is configured as TxFrTD_n to input fractional DS1 payload
data into Framer_n, the TxTSClk_n pin can be configured to function as one of
the following:
The pin will output gaped fractional DS1 clock that can be used by terminal
equipment to clock out fractional DS1 payload data at rising edge of the clock.
Framer_n will then input fractional DS1 payload data using falling edge of the
clock.Otherwise, this pin will be a clock enable signal to Transmit fractional
DS1 Input (TxFrTD_n) if Framer_n is configured accordingly. In this mode, frac-
tional DS1 payload data is clocked into the chip using un-gaped TxSerClk_n.
E1 Mode:
Each of these output pins are a 256kHz clock output which pulses "High"
whenever the Transmit Payload Data Input Interface block accepts the LSB of
each of the 32 time slots, within the E1 data stream, being processed via
Framer _n. The Terminal Equipment should use this clock signal to sample the
TxTSb0_n through TxTSb4_n output signals, and identify the time-slot being
processed via the "Transmit Section" of each Framer_n.
If TxTSb1_n pin is configured as TxFrTD_n to input fractional E1 payload data
into Framer_n, the TxTSClk_n pin can be configured to function as one of the
following: The pin will output gaped fractional E1 clock that can be used by ter-
minal equipment to clock out fractional E1 payload data at rising edge of the
clock. Framer_n will then input fractional E1 payload data using falling edge of
the clock.Otherwise, this pin will be a clock enable signal to Transmit fractional
E1 Input (TxFrTD_n) if Framer_n is configured accordingly. In this mode, frac-
tional E1 payload data is clocked into the chip using un-gaped TxSerClk_n.
29
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
OVERHEAD INTERFACE
(Framer Channel Number indicated by _n)
SIGNAL NAME
PIN #
TYPE
DESCRIPTION
TxOH_0
TxOH_1
TxOH_2
TxOH_3
TxOH_4
TxOH_5
TxOH_6
TxOH_7
A7
C14
D23
F23
AA24
AC17
AC14
AD5
I
Transmit Overhead Input—Framer_n:
This input pin, along with TxOHClk_n functions as the Transmit Overhead input
port for Framer_n.
DS1 Mode:
This input pin will become active if the Transmit Section of Framer_n has been
configured to use this input as the source of Facility Data Link bits in ESF fram-
ing mode, Fs bits in the SLC96 and N framing mode, and R bit in T1DM mode.
The data that is input into this pin will be inserted into the Data Link Bits within
the outbound DS1 frames at the falling edge of TxOHClk_n.
NOTE: This input pin will be disabled if Framer_n is using the Transmit HDLC
Controller, or the TxSer_n input as the source for the Data Link Bits.
E1 Mode:
This input pin will become active if the Transmit Section of Framer_n has been
configured to use this input as the source of Data Link bits. The data that is input
into this pin will be inserted into the Sa4 through Sa8 bits (the National Bits)
within the outbound non-FAS E1 frames.
NOTE: This input pin will be disabled if Framer_n is using the Transmit HDLC
Controller, or the TxSer_n input as the source for the Data Link Bits.
TxOHClk_0
TxOHClk_1
TxOHClk_2
TxOHClk_3
TxOHClk_4
TxOHClk_5
TxOHClk_6
TxOHClk_7
A5
C15
D21
F24
AC25
AD20
AD13
AF3
O
Transmit OH Serial Clock Output Signal—Framer_n:
This output clock signal functions as a demand clock signal for the "Transmit
Overhead Data Input Interface" block associated with Framer_n.
DS1 Mode:
If the "Transmit Overhead Data Input Interface" has been configured to be the
source of Facility Data Link bits in ESF framing mode, Fs bits in the SLC96 and
N framing mode, and R bit in T1DM framing mode, then the Transmit Overhead
data Input Interface block will provide a clock edge for each Data Link Bit.
Data Link Equipment, which is interfaced to this pin, should update its data (on
the TxOH_n line) on the rising edge of this clock signal. The Transmit Overhead
Data Input Interface will latch the data (on the TxOH_n line) on the falling edge
of this clock signal.
NOTES:
1. If the "Transmit Overhead Data Input Interface” has not been configured
to be the source of the Data Link information, then this output signal will
be inactive.
2. Depending on the configurations of Framer_n, the clock frequency in
ESF framing mode can be 2KHz or 4KHz in ESF.
E1 mode:
If the "Transmit Overhead data Input Interface" has been configured to be the
source of Data Link information, then the Transmit Overhead data Input Inter-
face block will provide a clock edge for each "Sa" bit that is carrying data link
information.
Data Link Equipment, which is interfaced to this pin, should update its data (on
the TxOH_n line) on the rising edge of this clock signal. The Transmit Overhead
Data Input Interface will latch the data (on the TxOH_n line) on the falling edge
of this clock signal.
NOTE: If the "Transmit Overhead Data Input Interface” has not been configured
to be the source of the Data Link information, then this output signal will be inac-
tive.
30
XRT84L38
OCTAL T1/E1/J1 FRAMER
áç
1.0.0
OVERHEAD INTERFACE
(Framer Channel Number indicated by _n)
SIGNAL NAME
PIN #
TYPE
DESCRIPTION
RxOH_0
RxOH_1
RxOH_2
RxOH_3
RxOH_4
RxOH_5
RxOH_6
RxOH_7
C7
B10
C19
B26
W25
AC20
AF18
AC11
O
Receive Overhead Output—Framer_n:
This pin, along with RxOHClk_n functions as the Receive Overhead Output
Interface for Framer_n.
DS1 Mode:
This pin unconditionally outputs the contents of the Facility Data Link Bit in ESF
framing mode, Fs bit in the SLC96 and N framing mode, and R bit in T1DM
framing mode.
NOTE: This output pin is active even if the Receive HDLC Controller (within
Framer_n) is active.
E1 mode:
This pin unconditionally outputs the contents of the National Bits (the "Sa4"
through the "Sa8" bits). If Framer_n has been configured to interpret the
National bits of the incoming E1 frames as carrying "Data Link" information;
then the Receive Overhead Output Interface will provide a clock pulse (via the
RxOHClk_n output pin) for each "Sa" bit carrying Data Link information.
NOTE: This output pin is active even if the Receive HDLC Controller (within
Framer_n) is active.
RxOHClk_0
RxOHClk_1
RxOHClk_2
RxOHClk_3
RxOHClk_4
RxOHClk_5
RxOHClk_6
RxOHClk_7
C5
B12
D19
B25
V23
AE21
AD17
AD10
O
Receive OH Serial Clock Output Signal—Framer_n:
This pin, along with RxOH_n functions as the Receive Overhead Output Inter-
face for Framer_n.
DS1 Mode:
This pin outputs a clock edge corresponding to each Facility Data Link Bit in
ESF framing mode, Fs bit in the SLC96 and N framing mode, and R bit in T1DM
framing mode, which carries Data Link information.
NOTES:
1. Depending on the configurations of Framer_n, the clock frequency in
ESF framing mode can be 2KHz or 4KHz.
2. This output pin is inactive if the Receive HDLC Controller (within
Framer_n) has been enabled.
E1 mode:
This pin outputs a clock edge corresponding to each National Bit that is carrying
"Data Link" information.
NOTE: This output pin is inactive if the Receive HDLC Controller (within
Framer_n) has been enabled.
31
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
RECEIVE SERIAL DATA OUTPUT
(Framer Channel Number indicated by _n)
SIGNAL NAME
PIN #
TYPE
DESCRIPTION
RxSync_0
RxSync_1
RxSync_2
RxSync_3
RxSync_4
RxSync_5
RxSync_6
RxSync_7
A3
B11
B16
C24
V26
AC22
AD14
AE7
I or O Single Frame Sync Pulse Input/Output pin—Receive Framer_n:
This pin is configured to be an Input if the Slip Buffer associated with Framer_n is
enabled. Conversely, this pin will be configured to be an Output if the Slip-Buffer
is by-passed.
DS1 Mode:
When pin is configured to be an Input
If this pin is configured to be an input, then the user must pulse this pin "High"
for one period of RxSerClk_n, when the Receive payload data output Interface
(of Framer_n) is processing the first bit (F-bit) of an inbound DS1 frame.
NOTE: It is imperative that the RxSync_n input signal be synchronized with the
RxSerClk_n input signal.
When pin is configured to be an Output
If this pin is configured to be an output, then it will pulse "High", for one period of
RxSerClk_n, when the Receive payload data output Interface (of Framer_n) is
processing the first bit (F-bit) of an inbound DS1 frame.
E1 Mode:
When pin is configured to be an Input
If this pin is configured to be an input, then this pin must be pulsed "High" for
one period of RxSerClk_n, when the Receive E1 Serial (or Overhead) Output
Interface, outputs the International bit (Si) of an inbound E1 frame.
NOTE: It is imperative that the RxSync_n input signal be synchronized with the
RxSerClk_n input signal.
When pin is configured to be an Output
If this pin is configured to be an output, then it will pulse "High" for one period of
RxSerClk_n, when the Receive E1 Serial (or Overhead) output Interface outputs
the last bit, in an inbound E1 frame.
RxMSync_0
RxMSync_1
RxMSync_2
RxMSync_3
RxMSync_4
RxMSync_5
RxMSync_6
RxMSync_7
B3
C9
O
Multiframe Sync Pulse Output--Receive Framer_n:
This DS1-only signal will pulse "High" for one period of RxSerClk_n, the instant
that the Receive payload data Interface (of Framer_n) is processing the first bit
of a DS1 Multi-frame.
A19
A26
V25
AD24
AF13
AC8
RxCRCMSync_0
RxCRCMSync_1
RxCRCMSync_2
RxCRCMSync_3
RxCRCMSync_4
RxCRCMSync_5
RxCRCMSync_6
RxCRCMSync_7
B3
C9
O
Receive "CRC Multiframe" Sync Output signal-Framer_n:
This E1-only signal pulses "High" for one period of RxSerClk_n whenever the
Receive E1 Output Interface of Framer_n outputs the first bit, within a given
"CRC Multiframe".
A19
A26
V25
AD24
AF13
AC8
NOTE: This output pin is inactive if CRC Multiframe Alignment is disabled.
32
XRT84L38
OCTAL T1/E1/J1 FRAMER
áç
1.0.0
RECEIVE SERIAL DATA OUTPUT
(Framer Channel Number indicated by _n)
SIGNAL NAME
PIN #
TYPE
DESCRIPTION
RxSerClk_0
RxSerClk_1
RxSerClk_2
RxSerClk_3
RxSerClk_4
RxSerClk_5
RxSerClk_6
RxSerClk_7
B2
B9
I or O Receive Serial Clock Signal—Receive Framer_n:
This signal is used by the Receive payload data output Interface, to latch the
contents of the RxSer_n signal out from the Octal T1/E1/J1 Framer IC.
Framer_n can use either the rising edge or the falling edge of RxSerClk_n signal
to latch the received DS1 payload data out. Depending on configurations of
Framer_n. RxSerClk_n can either be an input or an output.
A17
E23
U24
AF25
AD15
AD7
DS1 Mode:
Receive Back-plane Interface-1.544 MHz Clock Mode
If RxMUXEN = 0 and RxIMODE[1:0] = 00 in Receive interface control register,
Receive back-plane interface of Framer_n is presenting data at a rate of 1.544
Mbit/s. This pin is configured to be an Input if the Slip Buffer associated with
Framer_n is enabled. Conversely, this pin will be configured to be an Output if
the "Slip-Buffer" is "by-passed".
Receive Back-plane Interface-MVIP, 2.048 MHz Clock Mode
If RxMUXEN = 0 and RxIMODE[1:0] = 01 in Receive interface control register,
Receive back-plane interface of Framer_n is presenting data at a rate of 2.048
Mbit/s. The RxSerClk_n signal will be an Input clock signal running at 2.048
MHz.
Receive Back-plane Interface-4.096 MHz Clock Mode
If RxMUXEN = 0 and RxIMODE[1:0] = 10 in Receive interface control register,
Receive back-plane interface of Framer_n is presenting data at a rate of 4.096
Mbit/s. The RxSerClk_n signal will be an Input clock signal running at 4.096
MHz.
Receive Back-plane Interface-8.192 MHz Clock Mode
If RxMUXEN = 0 and RxIMODE[1:0] = 11 in Receive interface control register,
Receive back-plane interface of Framer_n is presenting data at a rate of 8.192
Mbit/s. The RxSerClk_n signal will be an Input clock signal running at 8.192
MHz.
Receive Back-plane Interface-Multiplexed at 12.352 MHz Clock Mode
If RxMUXEN = 1 and RxIMODE[1:0] = 00 in Receive interface control register,
Receive back-plane interface of Framer_n is presenting multiplexed data at a
rate of 12.352 Mbit/s. RxSerClk_0 and RxSerClk_4 signals will be Input clock
signals running at 12.352 MHz. RxSerClk_1, 2, 3 and RxSerClk_5, 6, 7 signals
are not required. Received DS1 Payload data of Channel 0, 1, 2 and 3 are multi-
plexed and latched out from Receive back-plane interface using clock edge of
RxSerClk_0 via RxSer_0 output pin. Receive DS1 Payload data of Channel 4, 5,
6 and 7 are multiplexed and latched out from Receive back-plane interface using
clock edge of RxSerClk_4 via RxSer_4 output pin.
33
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
RECEIVE SERIAL DATA OUTPUT
(Framer Channel Number indicated by _n)
SIGNAL NAME
PIN #
TYPE
DESCRIPTION
RxSerClk_0
RxSerClk_1
RxSerClk_2
RxSerClk_3
RxSerClk_4
RxSerClk_5
RxSerClk_6
RxSerClk_7
B2
B9
I or O Receive Serial Clock Signal—Receive Framer_n: (Continued)
A17
E23
U24
AF25
AD15
AD7
Receive Back-plane Interface-Multiplexed at 16.384 MHz Clock Mode
If RxMUXEN = 1 and RxIMODE[1:0] = 01 in Receive interface control register,
Receive back-plane interface of Framer_n is presenting multiplexed data at a
rate of 16.384 Mbit/s. RxSerClk_0 and RxSerClk_4 signals will be Input clock
signals running at 16.384 MHz. RxSerClk_1, 2, 3 and RxSerClk_5, 6, 7 signals
are not required. Received DS1 Payload data of Channel 0, 1, 2 and 3 are multi-
plexed and latched out from Receive back-plane interface using clock edge of
RxSerClk_0 via RxSer_0 output pin. Receive DS1 Payload data of Channel 4, 5,
6 and 7 are multiplexed and latched out from Receive back-plane interface using
clock edge of RxSerClk_4 via RxSer_4 output pin.
Receive Back-plane Interface-HMVIP, 16.384 MHz Clock Mode
If RxMUXEN = 1 and RxIMODE[1:0] = 10 in Receive interface control register,
Receive back-plane interface of Framer_n is presenting multiplexed data at a
rate of 16.384 Mbit/s. RxSerClk_0 and RxSerClk_4 signals will be Input clock
signals running at 16.384 MHz. RxSerClk_1, 2, 3 and RxSerClk_5, 6, 7 signals
are not required. Received DS1 Payload data of Channel 0, 1, 2 and 3 are multi-
plexed and latched out from Receive back-plane interface using clock edge of
RxSerClk_0 via RxSer_0 output pin. Receive DS1 Payload data of Channel 4, 5,
6 and 7 are multiplexed and latched out from Receive back-plane interface using
clock edge of RxSerClk_4 via RxSer_4 output pin.
Receive Back-plane Interface-H.100, 16.384 MHz Clock Mode
If RxMUXEN = 1 and RxIMODE[1:0] = 11 in Receive interface control register,
Receive back-plane interface of Framer_n is presenting multiplexed data at a
rate of 16.384 Mbit/s. RxSerClk_0 and RxSerClk_4 signals will be Input clock
signals running at 16.384 MHz. RxSerClk_1, 2, 3 and RxSerClk_5, 6, 7 signals
are not required. Received DS1 Payload data of Channel 0, 1, 2 and 3 are multi-
plexed and latched out from Receive back-plane interface using clock edge of
RxSerClk_0 via RxSer_0 output pin. Receive DS1 Payload data of Channel 4, 5,
6 and 7 are multiplexed and latched out from Receive back-plane interface using
clock edge of RxSerClk_4 via RxSer_4 output pin.
E1 Mode:
Receive Back-plane Interface-2.048 MHz (XRT84V24 Compatible) Clock
Mode
If RxMUXEN = 0 and RxIMODE[1:0] = 00 in Receive interface control register,
Receive back-plane interface of Framer_n is presenting data at a XRT84V24
compatible rate of 2.048 Mbit/s. This pin is configured to be an Input if the Slip
Buffer associated with Framer_n is enabled. Conversely, this pin will be config-
ured to be an Output if the "Slip-Buffer" is "by-passed".
Receive Back-plane Interface-2.048 MHz Clock Mode
If RxMUXEN = 0 and RxIMODE[1:0] = 01 in Receive interface control register,
Receive back-plane interface of Framer_n is presenting data at a rate of 2.048
Mbit/s. The RxSerClk_n signal will be an Input clock signal running at 2.048
MHz.
Receive Back-plane Interface-4.096 MHz Clock Mode
If RxMUXEN = 0 and RxIMODE[1:0] = 10 in Receive interface control register,
Receive back-plane interface of Framer_n is presenting data at a rate of 4.096
Mbit/s. The RxSerClk_n signal will be an Input clock signal running at 4.096
MHz.
Receive Back-plane Interface-8.192 MHz Clock Mode
If RxMUXEN = 0 and RxIMODE[1:0] = 11 in Receive interface control register,
Receive back-plane interface of Framer_n is presenting data at a rate of 8.192
Mbit/s. The RxSerClk_n signal will be an Input clock signal running at 8.192
MHz.
34
XRT84L38
OCTAL T1/E1/J1 FRAMER
áç
1.0.0
RECEIVE SERIAL DATA OUTPUT
(Framer Channel Number indicated by _n)
SIGNAL NAME
PIN #
TYPE
DESCRIPTION
RxSerClk_0
RxSerClk_1
RxSerClk_2
RxSerClk_3
RxSerClk_4
RxSerClk_5
RxSerClk_6
RxSerClk_7
B2
B9
I or O Receive Serial Clock Signal—Receive Framer_n: (Continued)
A17
E23
U24
AF25
AD15
AD7
Receive Back-plane Interface-Multiplexed at 16.384 MHz Clock Mode
If RxMUXEN = 1 and RxIMODE[1:0] = 01 in Receive interface control register,
Receive back-plane interface of Framer_n is presenting bit-multiplexed data at a
rate of 16.384 Mbit/s. RxSerClk_0 and RxSerClk_4 signals will be Input clock
signals running at 16.384 MHz. RxSerClk_1, 2, 3 and RxSerClk_5, 6, 7 signals
are not required. Received DS1 Payload data of Channel 0, 1, 2 and 3 are multi-
plexed and latched out from Receive back-plane interface using clock edge of
RxSerClk_0 via RxSer_0 output pin. Receive DS1 Payload data of Channel 4, 5,
6 and 7 are multiplexed and latched out from Receive back-plane interface using
clock edge of RxSerClk_4 via RxSer_4 output pin.
Receive Back-plane Interface-HMVIP, 16.384 MHz Clock Mode
If RxMUXEN = 1 and RxIMODE[1:0] = 10 in Receive interface control register,
Receive back-plane interface of Framer_n is presenting multiplexed data at a
rate of 16.384 Mbit/s. RxSerClk_0 and RxSerClk_4 signals will be Input clock
signals running at 16.384 MHz. RxSerClk_1, 2, 3 and RxSerClk_5, 6, 7 signals
are not required. Received DS1 Payload data of Channel 0, 1, 2 and 3 are multi-
plexed and latched out from Receive back-plane interface using clock edge of
RxSerClk_0 via RxSer_0 output pin. Receive DS1 Payload data of Channel 4, 5,
6 and 7 are multiplexed and latched out from Receive back-plane interface using
clock edge of RxSerClk_4 via RxSer_4 output pin.
Receive Back-plane Interface-H.100, 16.384 MHz Clock Mode
If RxMUXEN = 1 and RxIMODE[1:0] = 11 in Receive interface control register,
Receive back-plane interface of Framer_n is presenting multiplexed data at a
rate of 16.384 Mbit/s. RxSerClk_0 and RxSerClk_4 signals will be Input clock
signals running at 16.384 MHz. RxSerClk_1, 2, 3 and RxSerClk_5, 6, 7 signals
are not required. Received DS1 Payload data of Channel 0, 1, 2 and 3 are multi-
plexed and latched out from Receive back-plane interface using clock edge of
RxSerClk_0 via RxSer_0 output pin. Receive DS1 Payload data of Channel 4, 5,
6 and 7 are multiplexed and latched out from Receive back-plane interface using
clock edge of RxSerClk_4 via RxSer_4 output pin.
RxSer_0
RxSer_1
RxSer_2
RxSer_3
RxSer_4
RxSer_5
RxSer_6
RxSer_7
D4
A9
O
Receive Serial Data Output—Receive Framer_n:
This output pin along with RxSerClk_n functions as the Receive Serial Output
port for Framer_n.
C18
B24
W26
AE23
AE16
AD8
T1 mode:
Any incoming T1 line data that is received from the RxPOS_n and RxNEG_n
input pins, will be decoded and output via this pin.Framer_n can use either the
rising edge or the falling edge of RxSerClk_n input pin to latch the received T1
payload data out according to configurations of Framer_n.
E1 mode:
Much of the data that is received from the line via the RxPOS_n and RxNEG_n
input pins, will be decoded and output via this pin, in a binary format.All data that
is transported via Time Slots 1 through 15 and Time Slots 17 through 31, within
each incoming E1 frame, will be output via this pin. If Framer_n is configured
accordingly, the data for Time Slots 0 and 16 will also be output via this pin.
Framer_n can use either the rising edge or the falling edge of RxSerClk_n input
pin to latch the received DS1/E1 payload data out according to configurations of
Framer_n.
35
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
RECEIVE SERIAL DATA OUTPUT
(Framer Channel Number indicated by _n)
SIGNAL NAME
PIN #
TYPE
DESCRIPTION
RxTSb0_0
RxTSb0_1
RxTSb0_2
RxTSb0_3
RxTSb0_4
RxTSb0_5
RxTSb0_6
RxTSb0_7
A2
D12
A18
O
Receive Framer_n--Time Slot Octet Identifier Output-Bit 0:
These output signals (RxTSb4_n through RxTSb0_n) reflect the five-bit binary
value of the number of Time Slot (in the incoming DS1 frame) being received
and output to the Terminal Equipment via the Receive Payload Data Output
Interface block associated with Framer_n. The Terminal Equipment should use
the RxTSClk_n clock to sample these five output pins in order to identify the
time-slot being processed by the Receive Section of Framer_n.
C25
W24
AD22
AC16
AF9
RxSig_0
RxSig_1
RxSig_2
RxSig_3
RxSig_4
RxSig_5
RxSig_6
RxSig_7
A2
D12
A18
O
Receive Serial Signaling Output--Receive Framer_n:
These pins can be used to output robbed-bit signaling data extracted from an
incoming DS1 frame, if Framer_n is configured accordingly.
C25
W24
AD22
AC16
AF9
RxTSb1_0
RxTSb1_1
RxTSb1_2
RxTSb1_3
RxTSb1_4
RxTSb1_5
RxTSb1_6
RxTSb1_7
D5
A10
B19
C26
Y26
AC21
AF17
AE9
O
Receive Framer_n--Time Slot Octet Identifier Output-Bit 1:
These output signals (RxTSb4_n through RxTSb0_n) reflect the five-bit binary
value of the number of Time Slot (in the incoming DS1 frame) being received
and output to the Terminal Equipment via the Receive Payload Data Output
Interface block associated with Framer_n. The Terminal Equipment should use
the RxTSClk_n clock to sample these five output pins in order to identify the
time-slot being processed by the Receive Section of Framer_n.
RxFrTD_0
RxFrTD_1
RxFrTD_2
RxFrTD_3
RxFrTD_4
RxFrTD_5
RxFrTD_6
RxFrTD_7
D5
A10
B19
C26
Y26
AC21
AF17
AE9
O
Receive Serial Fractional T1/E1 Input--Receive Framer_n:
These pins can be used to output fractional DS1/E1 payload data extracted from
an inbound DS1/E1 frame, if Framer_n is configured accordingly. In this mode,
terminal equipment will use either rising edge of RxTSClk_n or RxSerClk_n to
clock in fractional DS1/E1 payload data. Please see pin description of
RxTSClk_n for details.
RxTSb2_0
RxTSb2_1
RxTSb2_2
RxTSb2_3
RxTSb2_4
RxTSb2_5
RxTSb2_6
RxTSb2_7
B4
C11
B20
E24
Y25
AF23
AD16
AF8
O
Receive Framer_n--Time Slot Octet Identifier Output-Bit 2:
These output signals (RxTSb4_n through RxTSb0_n) reflect the five-bit binary
value of the number of Time Slot (in the incoming DS1 frame) being received
and output to the Terminal Equipment via the Receive Payload Data Output
Interface block associated with Framer_n. The Terminal Equipment should use
the RxTSClk_n clock to sample these five output pins in order to identify the
time-slot being processed by the Receive Section of Framer_n.
RxTSChn_0
RxTSChn_1
RxTSChn_2
RxTSChn_3
RxTSChn_4
RxTSChn_5
RxTSChn_6
RxTSChn_7
B4
C11
B20
E24
Y25
AF23
AD16
AF8
O
Receive Framer_n -- Time Slot Identifier Serial Output
If RxTSb1_n pin is configured as RxFrTD_n to output fractional DS1 payload
data from Framer_n, then these pins serially output the five-bit binary value of
the number of the Time Slot being accepted and processed by the Transmit Pay-
load Data Input Interface block associated with Framer_n.
36
XRT84L38
OCTAL T1/E1/J1 FRAMER
áç
1.0.0
RECEIVE SERIAL DATA OUTPUT
(Framer Channel Number indicated by _n)
SIGNAL NAME
PIN #
TYPE
DESCRIPTION
RxTSb3_0
RxTSb3_1
RxTSb3_2
RxTSb3_3
RxTSb3_4
RxTSb3_5
RxTSb3_6
RxTSb3_7
B5
D13
C20
D26
W23
AE22
AF16
AE8
O
Receive Framer_n-Time Slot Octet Identifier Output-Bit 3:
These output signals (RxTSb4_n through RxTSb0_n) reflect the five-bit binary
value of the number of Time Slot (in the incoming DS1 frame) being received
and output to the Terminal Equipment via the Receive Payload Data Output
Interface block associated with Framer_n. The Terminal Equipment should use
the RxTSClk_n clock to sample these five output pins in order to identify the
time-slot being processed by the Receive Section of Framer_n.
Rx8kHz_0
Rx8kHz_1
Rx8kHz_2
Rx8kHz_3
Rx8kHz_4
Rx8kHz_5
Rx8kHz_6
Rx8kHz_7
B5
D13
C20
D26
W23
AE22
AF16
AE8
O
Receive 8KHz Clock-Receive Framer_n:
These pins output a reference 8KHz signal clock as if Framer_n is configured
accordingly.
RxTSb4_0
RxTSb4_1
RxTSb4_2
RxTSb4_3
RxTSb4_4
RxTSb4_5
RxTSb4_6
RxTSb4_7
D7
A13
B21
O
Receive Framer_n--Time Slot Octet Identifier Output-Bit 4:
These output signals (RxTSb4_n through RxTSb0_n) reflect the five-bit binary
value of the number of Time Slot (in the incoming DS1 frame) being received
and output to the Terminal Equipment via the Receive Payload Data Output
Interface block associated with Framer_n. The Terminal Equipment should use
the RxTSClk_n clock to sample these five output pins in order to identify the
time-slot being processed by the Receive Section of Framer_n.
E26
AA26
AD21
AC15
AF7
37
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
RECEIVE SERIAL DATA OUTPUT
(Framer Channel Number indicated by _n)
SIGNAL NAME
PIN #
TYPE
DESCRIPTION
RxTSClk_0
RxTSClk_1
RxTSClk_2
RxTSClk_3
RxTSClk_4
RxTSClk_5
RxTSClk_6
RxTSClk_7
C4
D11
D18
A25
O
Receive Channel Clock Output Signal—Framer_n:
This pin indicates the boundary of each time slot of an inbound DS1/E1 frame.
DS1 Mode:
Each of these output pins are a 192kHz clock output which pulses "High" when-
ever the Receive Payload Data Output Interface block outputs the LSB of each
of the 24 time slots (within the inbound DS1 data stream) on the RxSer_n pin.
The Terminal Equipment should use this clock signal to sample the RxTSb0_n
through RxTSb4_n output signals, and identify the time-slot being processed via
the "Receive Section" of each Framer_n.
V24
AD25
AF15
AC9
If RxTSb1_n pin is configured as RxFrTD_n to output fractional DS1 payload
data from Framer_n, the RxTSClk_n pin can be configured to function as one of
the following:
The pin will output gaped fractional DS1 clock that can be used by terminal
equipment to clock out fractional DS1 payload data at rising edge of the clock.
Otherwise, this pin will be a clock enable signal to Receive fractional DS1 Out-
put (RxFrTD_n) if Framer_n is configured accordingly. In this mode, fractional
DS1 payload data is clocked into the terminal equipment using un-gapped
RxSerClk_n.
E1 Mode:
Each of these output pins are a 256kHz clock output which pulses "High" when-
ever the Receive Payload Data Output Interface block outputs the LSB of each
of the 32 time slots (within the inbound E1 data stream) on the RxSer_n pin. The
Terminal Equipment should use this clock signal to sample the RxTSb0_n
through RxTSb4_n output signals, and identify the time-slot being processed via
the "Receive Section" of each Framer_n.
If RxTSb1_n pin is configured as RxFrTD_n to output fractional E1 payload data
from Framer_n, the RxTSClk_n pin can be configured to function as one of the
following: The pin will output gaped fractional E1 clock that can be used by ter-
minal equipment to clock out fractional E1 payload data at rising edge of the
clock.
Otherwise, this pin will be a clock enable signal to Receive fractional E1 Output
(RxFrTD_n) if Framer_n is configured accordingly. In this mode, fractional E1
payload data is clocked into the terminal equipment using un-gaped
RxSerClk_n.
RxLOS_0
RxLOS_1
RxLOS_2
RxLOS_3
RxLOS_4
RxLOS_5
RxLOS_6
RxLOS_7
D2
H4
J1
L4
U1
Y1
AA3
AB4
O
Receive Loss of Signal Output Indicator—Framer_n:
This output pin will toggle “High” (declare LOS) if the Receive block associated
with Framer_n determines that neither the RxPOS_n or the RxNEG_n inputs
have received a High level pulse in the last 32 bit periods.
This output pin will toggle “Low” if the Receive block, associated with Framer_n,
detects a string of 32 consecutive bits, that does not contain a string of 4 con-
secutive “0’s”.
NOTE: This output pin will also toggle "High" if the LOS_0 input pin is asserted
(e.g., toggled “High” by the LIU LOS output pin).
RxCASMSync_0
RxCASMSync_1
RxCASMSync_2
RxCASMSync_3
RxCASMSync_4
RxCASMSync_5
RxCASMSync_6
RxCASMSync_7
A4
A11
B18
D24
O
Receive “CAS Multiframe” Sync Output Signal--Framer_n:
This E1-only signal pulses "High" for one period of RxSerClk_n whenever the
Receive E1 Output Interface of Framer_n outputs the first bit, within a given
"CAS Multiframe".
Y24
NOTE: This output pin is inactive if Common Channel Signaling is enabled.
AD23
AD12
AC10
38
XRT84L38
OCTAL T1/E1/J1 FRAMER
áç
1.0.0
RECEIVE DECODER LIU INTERFACE
(Framer Channel Number indicated by _n)
SIGNAL NAME
PIN #
TYPE
DESCRIPTION
RxPOS_0
RxPOS_1
RxPOS_2
RxPOS_3
RxPOS_4
RxPOS_5
RxPOS_6
RxPOS_7
E4
G3
H1
L2
R2
W2
AA2
AC2
I
Receive Positive Polarity Pulse—Framer_n:
This input pin is intended to be connected to the RxPOS or RPDATA output of
the LIU (Line Interface Unit) IC associated with Framer_n.
The LIU will assert this input signal (pulse it "High"), when it is receiving a posi-
tive-polarity pulse from the line. This input signal is sampled and latched into the
Framer, on the user-selectable edge (rising or falling) of the RxLineClk_n signal.
RxNEG_0
RxNEG_1
RxNEG_2
RxNEG_3
RxNEG_4
RxNEG_5
RxNEG_6
RxNEG_7
C1
F1
J3
L3
T2
W1
AB1
AD1
I
Receive Negative Polarity Pulse—Framer_n:
This input pin is intended to be connected to the RxNEG or RNDATA output of the
LIU (Line Interface Unit) associated with Framer_n.
The LIU will assert this input signal (pulse it "High"), when it is receiving a nega-
tive-polarity pulse from the line. This input signal is sampled and latched into the
Framer, on the user-selectable edge (rising or falling) of the RxLineClk_n signal.
RxLineCLK_0
RxLineCLK_1
RxLineCLK_2
RxLineCLK_3
RxLineCLK_4
RxLineCLK_5
RxLineCLK_6
RxLineCLK_7
D1
G1
K4
M4
T3
W4
AA4
AE2
I
Receive Line Clock Input—Framer_n:
This input pin is intended to be connected to the RxClk output of the LIU (Line
Interface Unit) associated with Framer_n.
Framer_n uses the user-selectable edge of this signal to sample and latch the
signals at the RxPOS_n and RxNEG_n input pins.
TRANSMIT ENCODER LIU INTERFACE
(Framer Channel Number indicated by _n)
SIGNAL NAME
PIN #
TYPE
DESCRIPTION
TxPOS_0
TxPOS_1
TxPOS_2
TxPOS_3
TxPOS_4
TxPOS_5
TxPOS_6
TxPOS_7
E3
H3
K3
L1
T4
W3
AB2
AD2
O
Transmit Positive Polarity Pulse—Framer_n:
This output pin is intended to be connected to the TxPOS or TPDATA input of
the LIU (Line Interface Unit) associated with Framer_n.
Framer_n will assert this signal when it wishes for the Line Interface Unit (LIU)
associated with Framer_n, to transmit a positive polarity pulse on the line.
O
TxNRZ_0
TxNRZ_1
TxNRZ_2
TxNRZ_3
TxNRZ_4
TxNRZ_5
TxNRZ_6
TxNRZ_7
E3
H3
K3
L1
T4
W3
AB2
AD2
Transmit Non Return to Zero:
Unipolar output for transmitted data. TxNRZ_n includes the results of bit 7 stuff-
ing, but does not include HDB3 encoding.
39
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
TRANSMIT ENCODER LIU INTERFACE
(Framer Channel Number indicated by _n)
SIGNAL NAME
PIN #
TYPE
DESCRIPTION
TxNEG_0
TxNEG_1
TxNEG_2
TxNEG_3
TxNEG_4
TxNEG_5
TxNEG_6
TxNEG_7
F3
H2
K2
M3
V1
Y2
O
Transmit Negative Polarity Pulse—Framer_n:
This output pin is intended to be connected to the TxNEG or TNDATA input of
the LIU (Line Interface Unit) associated with Framer_n.
Framer_n will assert this signal when it wishes for the Line Interface Unit (LIU)
associated with Framer_n, to transmit a negative polarity pulse on the line.
AC1
AE1
Transmit Max
O
TxMX_0
TxMX_1
TxMX_2
TxMX_3
TxMX_4
TxMX_5
TxMX_6
TxMX_7
F3
H2
K2
M3
V1
Y2
Output pulses “High” for one bit time and is coincident with the sampling of the
least serial bit of a multiframe.
AC1
AE1
TxLineCLK_0
TxLineCLK_1
TxLineCLK_2
TxLineCLK_3
TxLineCLK_4
TxLineCLK_5
TxLineCLK_6
TxLineCLK_7
F2
G2
J2
N4
V4
Y3
AC3
AC4
O
Transmit Line Clock Output—Framer_n:
This output pin is intended to be connected to the TxClk input of the LIU (Line
Interface Unit) associated with Framer_n.
The LIU uses this pin to sample and latch the signals at its TPDATA and
TNDATA input pins.
TIMING
(Framer Channel Number indicated by _n)
SIGNAL NAME
PIN #
TYPE
DESCRIPTION
OSCClk
T1
I
Oscillator Clock:
This is a programmable operation clock input. This clock input can be one of six
frequencies:
E1 Mode: 16.384, 32.768 or 65.536 MHz
T1 Mode: 12.352, 24.704 or 49.408 MHz
8kHz_Ref
LOP
U2
R4
I
I
8 kHz External Reference Clock Input:
Loss of Power / Input Pin for Messaging
40
XRT84L38
OCTAL T1/E1/J1 FRAMER
áç
1.0.0
LIU CONTROL
(Framer Channel Number indicated by _n)
SIGNAL NAME
PIN #
TYPE
DESCRIPTION
LOS_0
LOS_1
LOS_2
LOS_3
LOS_4
LOS_5
LOS_6
LOS_7
G4
J4
K1
M2
V2
AA1
AB3
AF1
I
Loss of Signal Input—LIU Interface-Framer_n:
This input pin is intended to be connected to the RxLOS output pin of the LIU
associated with Framer_n. If the LIU IC detects an LOS condition and asserts
(toggles "High") this input pin, then the Receive Framer associated with
Channel_n will declare a LOS condition.
Asserting this input pin "High" will result in Framer_n asserting the RxLOS_n
output pin.
GPO7
P1
O
General Purpose Output pin/Chip Select Output pin:
The exact role of this output pin depends upon whether the LIU Controller block
is operating in the Hardware or HOST Mode.
Hardware Mode: GPO7
This pin is a general purpose output pin that is controlled by the contents of bit-
field 7, within the Line Control Register (Address = 00h, 02h).
HOST Mode:CS1
CS1
This pin is a chip select output pin that is asserted (toggles “Low”) following a
write operation to the LIU Access Register 1, associated with framer 4, 5, 6 and
7. This output pin is intended to be tied to the chip select input of an LIU (or
other peripheral device) that is configurable via a Microprocessor Serial Inter-
face. Once the HOST Mode serial port has completed its read or write opera-
tion, then it will negate (toggle "High") this output pin.
GPO6
P2
P4
R1
O
O
O
General Purpose Output pin/Serial Clock Output:
The exact role of this output pin depends upon whether the LIU Controller block
is operating in the Hardware or HOST Mode.
Hardware Mode: GPO6
This pin is a general purpose output pin that is controlled by the contents of bit-
field 6, within the Line Control Register (Address = 00h, 02h).
HOST Mode:SClk1
This pin functions as the Serial Clock output signal (SCLK), when the LIU Con-
troller Block is configured to operate in the HOST Mode
SClk1
GPO5
General Purpose Output pin/Serial Data Input bit 1:
The exact role of this output pin depends upon whether the LIU Controller block
is operating in the Hardware or HOST Mode.
Hardware Mode: GPO5
This pin is a general purpose output pin that is controlled by the contents of bit-
field 5, within the Line Control Register (Address = 00h, 02h).
HOST Mode:SDI1
This pin functions as the Serial Data Input (SDI) output pin (to the Microproces-
sor Serial Interface).
SDI1
GPO4
General Purpose Output pin/Serial Data Output bit 0:
The exact role of this output pin depends upon whether the LIU Controller block
is operating in the Hardware or HOST Mode.
Hardware Mode: GPO4
This pin is a general purpose output pin that is controlled by the contents of bit-
field 4, within the Line Control Register (Address = 00h, 02h).
HOST Mode:SDO1
SDO1
This pin functions as the Serial Data Output (SDO) input pin (into the LIU Con-
troller Block).
41
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
LIU CONTROL
(Framer Channel Number indicated by _n)
SIGNAL NAME
PIN #
TYPE
DESCRIPTION
GPO3
M1
O
General Purpose Output pin/Chip Select Output pin:
The exact role of this output pin depends upon whether the LIU Controller block
is operating in the Hardware or HOST Mode.
Hardware Mode: GPO3
This pin is a general purpose output pin that is controlled by the contents of bit-
field 3, within the Line Control Register (Address = 0x00, 0x02).
HOST Mode: CS0
CS0
This pin is a chip select output pin that is asserted (toggles “Low”) following a
write operation to the LIU Access Register 1, associated with framer 0,1, 2 and
3. This output pin is intended to be tied to the chip select input of an LIU (or
other peripheral device) that is configurable via a Microprocessor Serial Inter-
face. Once the HOST Mode serial port has completed its read or write opera-
tion, then it will negate (toggle "High") this output pin.
GPO2
N2
N3
N1
O
General Purpose Output/Serial Clock Output:
The exact role of this output pin depends upon whether the LIU Controller block
is operating in the Hardware or HOST Mode.
Hardware Mode: GPO2
This pin is a general purpose output pin that is controlled by the contents of bit-
field 2, within the Line Control Register (Address = 00h, 02h).
HOST Mode: SClk0
This pin functions as the Serial Clock output signal (SCLK), when the LIU Con-
troller Block is configured to operate in the HOST Mode.
SClk0
GPO1
O
General Purpose Output pin/Serial Data In Output pin:
The exact role of this output pin depends upon whether the LIU Controller block
is operating in the Hardware or HOST Mode.
Hardware Mode: GPO1
This pin is a general purpose output pin that is controlled by the contents of bit
field 1, within the Line Control Register (Address = 00h, 02h)
HOST Mode: SDI
This pin functions as the Serial Data Input (SDI) output pin (to the Microproces-
sor Serial Interface).
SDI0
GPO0
I or O General Purpose Output pin/Serial Data Out Input pin:
The exact role of this pin depends upon whether the LIU Controller block is
operating in the Hardware or HOST Mode.
Hardware Mode: GPO0
This pin is a general purpose output pin that is controlled by the contents of bit-
field 0, within the Line Control Register (Address = 00h, 02h).
HOST Mode: SDO0
SDO0
This Input pin functions as the Serial Data Output (SDO) input pin (into the LIU
Controller Block).
JTAG
(Framer Channel Number indicated by _n)
SIGNAL NAME
PIN #
TYPE
DESCRIPTION
Test clock: Boundary Scan clock input.
Note: This input pin should be pulled “Low” for normal operation
TCK
A1
I
Test Mode Select: Boundary Scan Mode Select input.
Note: This input pin should be pulled “Low” for normal operation
TMS
C2
I
42
XRT84L38
OCTAL T1/E1/J1 FRAMER
áç
1.0.0
JTAG
(Framer Channel Number indicated by _n)
SIGNAL NAME
PIN #
TYPE
DESCRIPTION
Test Data In: Boundary Scan Test data input
Note: This input pin should be pulled “Low” for normal operation
TDI
B1
I
TDO
TRST
D3
C3
P3
O
I
Test Data Out: Boundary Scan Test data output
JTAG Test Reset Input
Factory Test Mode Pin
Note: User should tie this pin to ground
Test Mode
I
MICROPROCESSOR INTERFACE
(Framer Channel Number indicated by _n)
SIGNAL NAME
PIN #
TYPE
DESCRIPTION
Data0
Data1
Data2
Data3
Data4
Data5
Data6
Data7
R24
R25
N26
N25
L24
K25
K24
J24
I/O
Bidirectional Microprocessor Data Bus Bit 0--LSB
Bidirectional Microprocessor Data Bus Bit 1
Bidirectional Microprocessor Data Bus Bit 2
Bidirectional Microprocessor Data Bus Bit 3
Bidirectional Microprocessor Data Bus Bit 4
Bidirectional Microprocessor Data Bus Bit 5
Bidirectional Microprocessor Data Bus Bit 6
Bidirectional Microprocessor Data Bus Bit 7--MSB
Req0
T26
O
DMA Cycle Request Output—DMA Controller 0 (Write):
The Framer asserts this output pin (toggles it "Low") when at least one of the
Transmit HDLC buffers are empty and can receive one more HDLC message.
The Framer negates this output pin (toggles it “High”) when the HDLC buffer can
no longer receive another HDLC message.
Req1
U23
DMA Cycle Request Output—DMA Controller 1 (Read):
The Framer asserts this output pin (toggles it "Low") when one of the Receive
HDLC buffer contains a complete HDLC message that needs to be read by the
µC/µP.
The Framer negates this output pin (toggles it High) when the Receive HDLC
buffers are depleted.
INT
M24
R23
O
I
Interrupt Request Output:
The Framer will assert this active "Low" output (toggles it "Low"), to the local µP,
anytime it requires interrupt service.
µPClk
Microprocessor Clock Input:
This clock signal is the Microprocessor Interface System clock. This clock signal
is used for synchronous/burst/DMA data transfer. The maximum frequency of
this clock signal is 33MHz.
43
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
MICROPROCESSOR INTERFACE
(Framer Channel Number indicated by _n)
SIGNAL NAME
PIN #
TYPE
DESCRIPTION
µPType0
T25
I
Microprocessor Type Input: Bit 0 (LSB):
This input pin, along with µPTYPE1 and µPTYPE2 permit the user to specify
which type of Microprocessor/Microcontroller to be interfaced the Framer.
µPType1
µPType2
P24
M25
Microprocessor Type Input: Bit 1
Microprocessor Type Input: Bit 2
MICROPROCESSOR
TYPE
0
0
0
0
1
1
0
0
1
1
0
0
0
1
0
1
0
1
68HC11, 8051, 80C188
MOTOROLA 68K
INTEL X86
INTEL I960
IDT3051/52
IBM POWER PC 403
RDY_DTACK
P23
O
Ready/Data Transfer Acknowledge Output:
The exact behavior of this pin depends upon which Microprocessor the Framer
is configured to interface to:
Intel Type Microprocessors
This output pin toggles "Low" when the Framer is ready to respond to the current
PIO (Programmed I/O) or Burst Transaction.
Motorola Type Microprocessors
This output pin toggles "Low" when the Framer has completed the current bus
cycle.
A0
A1
A2
A3
A4
A5
A6
P26
N23
M26
L26
L23
J26
K23
I
Microprocessor Interface Address Bus Input Bit 0 -- (LSB)
Microprocessor Interface Address Bus Input Bit 1
Microprocessor Interface Address Bus Input Bit 2
Microprocessor Interface Address Bus Input Bit 3
Microprocessor Interface Address Bus Input Bit 4
Microprocessor Interface Address Bus Input Bit 5
Microprocessor Interface Address Bus Input Bit 6 -- (MSB)
DBEn
ALE_AS
CS
P25
N24
G25
I
I
I
Data Bus Enable Input pin.
Address Latch Enable Input_Address Strobe
Microprocessor Interface—Chip Select Input:
The Microprocessor/Microcontroller must assert this input pin (toggle it "Low") in
order to exchange data with the Framer.
Note: For the 68K MPU, this signal is generated by address decode and address
strobe.
RD
R26
I
Microprocessor Interface—Read Strobe Input:
The exact behavior of this pin depends upon the type of Microprocessor/Micro-
controller the Framer has been configured to interface to, as defined by the
µPTYPE[2:0] pins.
Note: See pin T25 (µPType0) for the µP selection table.
44
XRT84L38
OCTAL T1/E1/J1 FRAMER
áç
1.0.0
MICROPROCESSOR INTERFACE
(Framer Channel Number indicated by _n)
SIGNAL NAME
PIN #
TYPE
DESCRIPTION
WR
G26
I
Microprocessor Interface—Write Strobe Input
"Low" : Indicates current bus cycle is a write cycle: Intel 51, 188, MIPS350x
"High" : Indicates present bus cycle is a write cycle: Intel x86, i960
"Low" : Indicates current bus cycle is a read cycle: Intel x86, i960
"High" : Indicates present bus cycle is a read cycle: Motorola, Power PC 403
"Low" : Also used as write strobe in DMA transfer
ACK0
U26
I
DMA Cycle Acknowledge Input—DMA Controller 0 (Write):
The external DMA Controller will assert this input pin “Low” when the following
two conditions are met:
a. After the DMA Controller, within the Framer has asserted (toggled “Low”), the
Req_0 output signal.
b. When the external DMA Controller is ready to transfer data from external
memory to the selected Transmit HDLC buffer.
At this point, the DMA transfer between the external memory and the selected
Transmit HDLC buffer may begin.
After completion of the DMA cycle, the external DMA Controller will negate this
input pin after the DMA Controller within the Framer has negated the Req_0 out-
put pin. The external DMA Controller must do this in order to acknowledge the
end of the DMA cycle.
ACK1
T23
I
DMA Cycle Acknowledge Input—DMA Controller 1 (Read):
The external DMA Controller asserts this input pin “Low” when the following two
conditions are met:
a. After the DMA Controller, within the Framer has asserted (toggled "Low"), the
Req_1 output signal.
b. When the external DMA Controller is ready to transfer data from the selected
Receive HDLC buffer to external memory.
At this point, the DMA transfer between the selected Receive HDLC buffer and
the external memory may begin.
After completion of the DMA cycle, the external DMA Controller will negate this
input pin after the DMA Controller within the Framer has negated the Req_1 out-
put pin. The external DMA Controller will do this in order to acknowledge the
end of the DMA cycle.
Blast
L25
R3
I
I
Last Cycle of Burst Indicator Input:
The Microprocessor asserts this pin “Low”when it is performing its last read or
write cycle, within a burst operation.
Reset
Reset Input: Active "Low"
45
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
GROUND PINS
SIGNAL NAME
PIN #
TYPE
DESCRIPTION
VDD
L11
L12
L13
L14
L15
L16
M11
M12
M15
M16
N11
N12
N15
N16
R11
R12
R15
R16
****
Power Supply Pins
POWER SUPPLY PINS
SIGNAL NAME
PIN #
TYPE
DESCRIPTION
GND
M13
M14
N13
N14
P13
P14
R13
R14
T11
T12
T13
T14
T15
T16
****
Ground Pins
46
XRT84L38
OCTAL T1/E1/J1 FRAMER
áç
1.0.0
NO CONNECT PINS
SIGNAL NAME
PIN #
TYPE
DESCRIPTION
NC
A6
A20
B7
Not Connected
B17
C12
C13
C16
C23
D14
D17
E1
E2
F4
H25
H26
K26
M23
U3
U4
U25
V3
Y4
AA25
AC23
AD26
AE3
AE14
AE15
AE17
AE25
AF2
AF11
AF14
AF22
AF24
47
áç
XRT84L38
OCTAL E1/T1/J1 FRAMER
REV.1.0.0
ELECTRICAL CHARACTERISTICS
ABSOLUTE MAXIMUMS
Power Supply......................................... -0.5V to +3.465V
Storage Temperature ...............................-65°C to 150°C
Operating Temperature Range.................-40°C to 85°C
Supply Voltage ...................... GND-0.5V to +VDD + 0.5V
Power Dissipation PBGA Package........................... 2W
Input Logic Signal Voltage (Any Pin) .........-0.5V to + 5.5V
ESD Protection...................................................>2000V
Input Current (Any Pin) ...................................... + 100mA
DC ELECTRICAL CHARACTERISTICS
Test Conditions: TA = 25°C, VDD = 3.3V + 5% unless otherwise specified
SYMBOL
PARAMETER
MIN.
TYP.
MAX.
UNITS
mA
µA
V
CONDITIONS
IDD
Power Supply Current
450
All Channels on
ILL
Data Bus Tri-State Bus Leakage Current
Input Low voltage
-10
+10
0.6
VIL
PDATA[0:7]
All Others
PDATA[0:7]
All Others
IOL = 2mA
0.8
V
VIH
Input High Voltage
2.7
2.0
0.0
VDD
VDD
0.4
V
V
VOL
VOH
Output Low Voltage
Output High Voltage
V
2.4
VDD
V
IOH = 2mA
IOC
IIH
Open Drain Output Leakage Current
Input High Voltage Current
-10
-10
10
10
µA
µA
VIH = VDD
VIL = GND
Input High Voltage Current (with pull-down resistor)
Input Low Voltage Current
100
-10
400
10
IIL
µA
Input Low Voltage Current (with pull-up resistor)
-150
-30
TABLE 2: XRT84L38 POWER CONSUMPTION
(Vdd=3.3V±5%, TA=25°C unless otherwise specified)
MODE
T1
SUPPLYVOLTAGE
3.3V
MIN
TYP
1.8
1.5
MAX
2.0
UNIT
W
-
-
E1
3.3V
1.8
W
48
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
1.0 MICROPROCESSOR INTERFACE BLOCK
The Microprocessor Interface section supports communication between the local microprocessor (µP) and the
Framer. The Microprocessor Interface supports the following features:
• Communicates through a 7 bit address bus (4 bit for one framer) and an 8 bit data bus.
• Supports DMA read/write data interface
• Supports burst transfers
• Supports Programmed I/O read and write, wait cycle extended with READY/DTACK
The Microprocessor Interface section supports the following operations:
• Channel Selection
• Writing configuration data into the Framer on-chip (addressable) registers
• Writing outbound PMDL (Path Maintenance Data Link) messages into the Transmit LAPD Message buffer of
the Framer
• Generation of Interrupt Requests to the µP
• Servicing Interrupt Requests from the Framer
• Monitoring the system's health by periodically reading the on-chip Performance Monitor registers
• Reading inbound PMDL Messages from the Receive LAPD Message Buffer of the Framer
Each of these operations (between the local microprocessor and the Framer IC) is discussed in detail, through-
out this data sheet.
The Framer supports the following microprocessors/microcontrollers with a minimum amount of glue logic.
• Intel 8051, 80C188, x86, i960
• Motorola 68HC11, 68K
• MIPS 3051/52
• PowerPC 403
The type of microprocessor/microcontroller to interface to the Framer is specified by tying the µPTYPE[2:0]
pins to the appropriate level. Table 1, lists the values for µPTYPE[2:0] and the corresponding µP/µC types.
TABLE 3: µC/µP SELECTION TABLE
µPTYPE[2:0] INPUT LEVELS
CORRESPONDING µC/µP
68HC11, 8051, 80C188
Motorola 68000 Family
Intel x86 Family
000
001
010
011
100
101
Intel I960
IDT3051/52 (MIPS)
IBM PowerPC 403
The behavior of some of the pins, associated with the Microprocessor Interface, depends upon the value that
the user has applied to the PType[2:0] input pins. The next sections present a detailed discussion on the role of
each of these pins, and how to configure the Framer to interface to each of these types of Microprocessors.
The Framer connects to the Microcontroller as if it were external memory. The microcontroller can read or write
to two different storage elements in the Framer:
• Flip-flop types of registers
• RAMs
The configuration of the Framer, including the enabling/disabling of interrupts, is selected by setting values in
various control registers. The registers can be read as well as written. The Framer can be designed into both
49
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
polled and interrupt-driven systems. All detection of change of state of alarm conditions, data link events, error
events, or counter overflows can be programmed to cause interrupts.
The Microcontroller Interface Block within the Framer supports three types of data transfer schemes:
• Programmable Input/Output (PIO)
• Burst Transfer
• DMA (Direct Memory Access)
Each of these data transfer methods are also discussed in the next sections.
1.1 CHANNEL SELECTION WITHIN THE FRAMER
The XRT84L38 Framer consists of eight independent banks of configuration registers. Each of these banks are
identical and correspond to each of the eight channels within the XRT84L38. The XRT84L38 permits selection
of and access to, any one of these Configuration Register Banks, via the Three (3) Most Significant Address
Pins, A4, A5 and A6. The relationship between the states of A4, A5 and A6, and the corresponding Configura-
tion Register bank, is shown below.
TABLE 4: CHANNEL SELECTION
A6
0
A5
0
A4
0
CONFIGURATION REGISTER BANK
Channel 0
0
0
1
Channel 1
0
1
0
Channel 2
0
1
1
Channel 3
1
0
0
Channel 4
1
0
1
Channel 5
1
1
0
Channel 6
1
1
1
Channel 7
FIGURE 3. SIMPLIFIED BLOCK DIAGRAM OF THE MICROPROCESSOR INTERFACE BLOCK
WR
RD
ALE_AS
Blast
µPType [2:0]
Microprocessor
Interface
Rdy/DTACK
&
Reset
DBEn
Programmable
Registers
Clk
CS
INT
A[6:0]
DMA
Data[7:0]
ACK[1:0]
Req[1:0]
Interface
1.2 THE MICROPROCESSOR INTERFACE BLOCK SIGNAL
50
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The Framer may be configured into different operating modes and have its performance monitored by software
through a standard microprocessor, using data, address and control signals.
The local µP configures the Framer (into a desired operating mode) by writing data into specific addressable,
on-chip Read/Write registers, or on-chip RAM. The microprocessor interface provides the signals which are re-
quired for a general purpose microprocessor to read or write data into these registers. The Microprocessor In-
terface also supports polled and interrupt driven environments. These interface signals are described below in
Table 5, Table 6, and Table 7. The microprocessor interface can be configured to operate in the Motorola
Mode, the Intel mode, as well as other modes. When the Microprocessor Interface is operating in the Motorola
mode, some of the control signals function in a manner required by the Motorola 68000 family of microproces-
sors. Likewise, when the Microprocessor Interface is operating in the Intel Mode, then these Control Signals
function in a manner as required by the Intel 80xx family of microprocessors.
Table 5 lists and describes those Microprocessor Interface signals whose role is constant across the two
modes. Table 6 describes the role of some of these signals when the Microprocessor Interface is operating in
the Intel Mode. Likewise, Table 7 describes the role of these signals when the Microprocessor Interface is op-
erating in the Motorola Mode.
TABLE 5: XRT84L38 MICROPROCESSOR INTERFACE SIGNALS THAT EXHIBIT CONSTANT ROLES IN BOTH THE INTEL
AND MOTOROLA MODES
PIN NAME
TYPE
DESCRIPTION
I
Microprocessor Interface Mode Select Input pins
µPTYPE[2:0]
These three pins are used to specify the Microprocessor Mode that the Microprocessor Inter-
face will operate in. The relationship between the state of these three input pins, and the corre-
sponding Microprocessor Mode is presented in Table 1.
D[7:0]
A[6:0]
I/O
I
Bi-Directional Data Bus for register Read or Write Operations.
Seven-Bit Address Bus Inputs
The XRT84L38 Framer Microprocessor Interface uses a Multiplexed Address bus. This
address bus is provided to permit the user to select an on-chip register or buffer location for
Read/Write access.
CS
I
Chip Select Input
This active-low signal selects the Microprocessor Interface of the XRT84L38 Framer and
enables Read/Write operations with the on-chip registers/buffer locations.
51
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
TABLE 6: INTEL MODE: MICROPROCESSOR INTERFACE SIGNALS
XRT84L38
PIN NAME
INTEL
EQUIVALENTPIN
TYPE
DESCRIPTION
ALE_AS
ALE
I
Address-Latch Enable: This active-high signal is used to latch the contents on
the address bus, A[6:0]. The contents of the Address Bus are latched into the
A[6:0] inputs on the falling edge of ALE_AS. Additionally, this signal can be used
to indicate the start of a burst cycle.
RD
RD*
I
Read Signal: This active-low input functions as the read signal from the local µP.
When this signal goes "Low", the Framer Microprocessor Interface places the
contents of the addressed register on the Data Bus pins, D[7:0]. The Data Bus is
tri-stated once this input signal returns "High".
WR
WR*
I
Write Signal: This active-low input functions as the write signal from the local
µP. The contents of the Data Bus (D[7:0]) is written into the addressed register
via A[6:0], on the rising edge of this signal.
READY*
O
Ready Output: This active-low signal is provided by the Framer and indicates
that the current read or write cycle is to be extended until this signal is asserted.
The local µP typically inserts WAIT states until this signal is asserted. This output
toggles "Low" when the device is ready for the next Read or Write cycle.
RDY_DTACK
TABLE 7: MOTOROLA MODE: MICROPROCESSOR INTERFACE SIGNALS
XRT84L38
PIN NAME
MOTOROLA
EQUIVALENTPIN
TYPE
DESCRIPTION
ALE_AS
AS*
I
Address Strobe: This active-low signal is used to latch the contents on the
address bus input pins, A[6:0], into the Microprocessor Interface circuitry. The
contents of the Address Bus are latched into the Framer on the rising edge of the
ALE_AS signal. This signal can also be used to indicate the start of a burst cycle.
RD
WR
DS*
R/W*
I
I
Data Strobe: This signal latches the contents of the bi-directional data bus pins
into the Addressed Register within the Framer during a Write Cycle.
Read/Write Input: When this pin is "High", it indicates a Read Cycle. When this
pin is "Low", it indicates a Write cycle.
DTACK*
O
Data Transfer Acknowledge: The Framer asserts DTACK in order to inform the
CPU that the present READ or WRITE cycle is nearly complete. The 68000 fam-
ily of CPUs requires this signal from its peripheral devices in order to quickly and
properly complete a READ or WRITE cycle.
RDY_DTACK
1.3 INTERFACING THE XRT84L38 TO THE LOCAL µC/µP VIA THE MICROPROCESSOR INTERFACE BLOCK
The Microprocessor Interface block within the Framer is very flexible and provides the following options:
• Interface the Framer to a µC/µP over an 8-bit wide bi-directional data bus.
• Interface the Framer to an Intel-type or Motorola-type µC/µP.
• Transfer data (between the Framer IC and the µC/µP) via the Programmed I/O or Burst Mode
1.3.1 Interfacing the Framer to the Microprocessor over an 8 bit wide bi-directional Data Bus
The Framer Microprocessor Interface permits the user to interface it to a µC/µP over an 8-bit wide bi-directional
data bus. In general, interfacing the Framer to an 8-bit µC/µP is quite straight-forward. This is because most of
the registers, within the Framer, are 8-bits wide. In this mode, the µC/µP can read or write data into both even
and odd numbered addresses within the Framer address space.
Example:
52
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
Consider that an 8-bit µC/µP needs to read in the PMON LCV Event Count Register. In order to accomplish
this task, the 8-bit µC/µP needs to read in the contents of PMON LCV Event Count Register - MSB (located at
Address = 0x50) and the contents of the PMON LCV Event Count Register - LSB (located at Address = 0x51).
These two eight-bit registers when concatenated together make up the PMON LCV Event Count Register.
If the 8-bit µC/µP reads in the PMON LCV Event Count-LSB register first, then the entire PMON LCV Event
Count register will be reset to 0x0000. As a consequence, if the 8-bit µC/µP attempts to read in the PMON LCV
Event Count-MSB register in the very next read cycle, it will read in the value 0x00.
1.3.2 Data Access Modes
The Microprocessor Interface block supports data transfer between the Framer and the µC/µP (e.g., Read and
Write operations) via the Programmed I/O and the Burst Modes.
1.3.2.1 Programmed I/O
Programmed I/O is basically a handshaking type of asynchronous bus access, which provides relatively slow
single read and write data transfers. The Microprocessor must supply an address value to the Address Bus in-
put pins A[6:0] with each read and write cycle. Because of the Indirect Addressing scheme each PIO reads and
write access requires two accesses, as illustrated below.
In the first access, the Microprocessor is specifying two things:
1. Which of the four framer register sets it intends to access.
2. Which group of registers within the selected framer’s register sets, the Microprocessor wants to access.
As a slave, the E1 is the target of access generated by a bus master, the CPU. Slave accesses are accepted by
the slave control state machine, then passed to related functional logic. Address is buffered and decoded to ad-
dress relevant destination. Data is also latch in both write and read directions. PIO operations are enabled by
the Chip Select (CS) input signal. Framer PIO interface supports pipelined (buffered) writes to increase bus
throughput. All internal registers and accessible memory are addressable through 6 bits of address bus.
1.3.2.2 Data Access using Programmed I/O
Programmed I/O is the conventional manner in which a microprocessor exchanges data with a peripheral de-
vice. However, it is also the slowest method of data exchange between the Framer and the µC/µP.
1.3.2.2.1 Intel Mode Programmed I/O Access
If the Framer is interfaced to an Intel-type µC/µP (e.g., the 80x86 family, etc.), then it should be configured to
operate in the Intel mode.
1.3.2.2.1.1 Intel Mode Read Cycle
Whenever an Intel-type µC/µP wishes to read the contents of a register or some location within the Receive
LAPD Message buffer or the Receive OAM Cell Buffer, within the Framer, it should do the following.
1. Place the address of the target register or buffer location, within the Framer, on the Address Bus input pins
A[6:0].
2. While the µC/µP is placing this address value on the Address Bus, the Address Decoding circuitry within
the user's system should assert the CS (Chip Select) pin of the Framer, by toggling it "Low". This action
enables further communication between the µC/µP and the Framer Microprocessor Interface block.
3. Toggle the ALE_AS (Address Latch Enable) input pin "High". This step enables the Address Bus input driv-
ers, within the Microprocessor Interface block of the Framer.
4. After allowing the data on the Address Bus pins to settle, by waiting the appropriate Address Data Setup
time, the µC/µP should toggle the ALE_AS pin "Low". This step causes the Framer to latch the contents of
the Address Bus into its internal circuitry. At this point, the address of the register or buffer locations, within
the Framer, has been selected.
5. Next, the µC/µP should indicate that this current bus cycle is a Read Operation by toggling the RD_DS
(Read Strobe) input pin "Low". This action also enables the bi-directional data bus output drivers of the
Framer. At this point, the bi-directional data bus output drivers proceeds to drive the contents of the latched
addressed register, or buffer location, onto the bi-directional data bus, D[7:0].
6. Immediately after the µC/µP toggles the Read Strobe signal "Low", the Framer toggles the RDY_DTACK
output pin "Low". The Framer does this in order to inform the µC/µP that the data to be read from the data
bus is NOT READY to be latched into the µC/µP.
53
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
7. After some settling time, the data on the bi-directional data bus stabilizes and can be read by the µC/µP.
The Framer indicates that this data can be read by toggling the RDY_DTACK (READY) signal "High".
8. After the µC/µP detects the RDY_DTACK signal, from the Framer, it can terminate the Read Cycle by tog-
gling the RD_DS (Read Strobe) input pin "High".
Figure 4 presents a timing diagram which illustrates the behavior of the Microprocessor Interface signals during
an Intel-type Programmed I/O Read Operation.
FIGURE 4. INTEL µP INTERFACE SIGNALS DURING PROGRAMMED I/O READ OPERATION
ALE_AS
A[6:0]
CS
Address of target Register
D[7:0]
Not Valid
Valid
RD
WR_R/W
RDY_DTACK
1.3.2.2.1.2 The Intel Mode Write Cycle
Whenever an Intel-type µC/µP wishes to write a byte or word of data into a register or buffer location, within the
Framer, it should do the following.
1. Assert the ALE_AS (Address Latch Enable) input pin by toggling it "High". When the µC/µP asserts the
ALE_AS input pin, it enables the Address Bus Input Drivers within the Framer chip.
2. Place the address of the target register or buffer location, within the Framer, on the Address Bus input pins,
A[6:0].
3. While the µC/µP is placing this address value onto the Address Bus, the Address Decoding circuitry within
the user's system should assert the CS input pin of the Framer by toggling it "Low". This step enables fur-
ther communication between the µC/µP and the Framer Microprocessor Interface block.
4. After allowing the data on the Address Bus pins to settle, by waiting the appropriate Address Setup time,
the µC/µP should toggle the ALE_AS input pin "Low". This step causes the Framer to latch the contents of
the Address Bus into its internal circuitry. At this point, the address of the register or buffer location within
the Framer, has been selected.
5. Next, the µC/µP should indicate that this current bus cycle is a Write Operation by toggling the WR_R/W
(Write Strobe) input pin "Low". This action also enables the bi-directional data bus input drivers of the
Framer.
6. The µC/µP should then place the byte or word that it intends to write into the target register on the bi-direc-
tional data bus, D[7:0].
7. After waiting the appropriate amount of time for the data on the bi-directional data bus to settle, the µC/µP
should toggle the WR_R/W (Write Strobe) input pin "High". This action accomplishes two things:
a. It latches the contents of the bi-directional data bus into the Framer Microprocessor Interface block.
b. It terminates the write cycle.
54
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
Figure 5 presents a timing diagram which illustrates the behavior of the Microprocessor Interface signals, dur-
ing an Intel-type Programmed I/O Write Operation.
FIGURE 5. INTEL µP INTERFACE SIGNALS DURING PROGRAMMED I/O WRITE OPERATION
ALE_AS
A[6:0]
CS
Address of Target Register
D[7:0]
Data to be Written
RD
WR_R/W
RDY_DTACK
1.3.2.2.2 Motorola Mode Programmed I/O Access
If the Framer is interfaced to a Motorola-type µC/µP (e.g., the MC680X0 family, etc.), it should be configured to
operate in the Motorola mode.
1.3.2.2.2.1 Motorola Mode Read Cycle
Whenever a Motorola-type µC/µP wishes to read the contents of a register or some location within the Receive
LAPD Message or Receive OAM Cell Buffer, within the Framer, it should do the following.
1. Assert the ALE_AS (Address-Strobe) input pin by toggling it “Low”. This step enables the Address Bus
input drivers within the Microprocessor Interface Block of the Framer.
2. Place the address of the target register or buffer location within the Framer, on the Address Bus input pins,
A[6:0].
3. At the same time, the Address Decoding circuitry within the user's system should assert the CS (Chip
Select) input pin of the Framer, by toggling it "Low". This action enables further communication between
the µC/µP and the Framer Microprocessor Interface block.
4. After allowing the data on the Address Bus pins to settle, by waiting the appropriate Address Setup time,
the µC/µP should toggle the ALE_AS input pin "High". This step causes the Framer to latch the contents of
the Address Bus into its internal circuitry. At this point, the address of the register or buffer location within
the Framer has been selected.
5. Further, the µC/µP should indicate that this cycle is a Read cycle by setting the WR_R/W (R/W*) input pin
"High".
6. Next the µC/µP should initiate the current bus cycle by toggling the RD_DS (Data Strobe) input pin "Low".
This step enables the bi-directional data bus output drivers, within the Framer. At this point, the bi-direc-
tional data bus output drivers will proceed to drive the contents of the Address register onto the bi-direc-
tional data bus, D[7:0].
7. After some settling time, the data on the bi-directional data bus will stabilize and can be read by the µC/µP.
The Framer will indicate that this data can be read by asserting the RDY_DTACK (DTACK) signal “Low”.
8. After the µC/µP detects the RDY_DTACK signal (from the Framer) it will terminate the Read Cycle by tog-
gling the RD_DS (Data Strobe) input pin "High".
Figure 6 presents a timing diagram which illustrates the behavior of the Microprocessor Interface signals during
a Motorola-type Programmed I/O Read Operation.
55
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
FIGURE 6. MOTOROLA µP INTERFACE SIGNALS DURING A PROGRAMMED I/O READ OPERATION
ALE_AS
A[6:0]
CS
Address of target Register
D[7:0]
Not Valid
Valid Data
RD_DS
WR_R/W
RDY_DTACK
1.3.2.2.2.2 Motorola Mode Write Cycle
Whenever a Motorola-type µC/µP wishes to write a byte or word of data into a register or buffer location, within
the Framer, it should do the following.
1. Assert the ALE_AS (Address Select) input pin by toggling it "Low". This step enables the Address Bus
input drivers (within the Framer chip).
2. Place the address of the target register or buffer location (within the Framer), on the Address Bus input
pins, A[6:0].
3. While the µC/µP is placing this address value onto the Address Bus, the Address-Decoding circuitry (within
the user's system) should assert the CS (Chip Select) input pins of the Framer by toggling it "Low". This
step enables further communication between the µC/µP and the Framer Microprocessor Interface block.
4. After allowing the data on the Address Bus pins to settle (by waiting the appropriate Address Setup time),
the µC/µP should toggle the ALE_AS input pin "High". This step causes the Framer to latch the contents of
the Address Bus into its own circuitry. At this point, the Address of the register or buffer location (within the
Framer), has now been selected.
5. Further, the µC/µP should indicate that this current bus cycle is a Write operation by toggling the WR_R/W
(R/W*) input pin "Low".
6. The µC/µP should then place the byte or word that it intends to write into the target register, on the bi-direc-
tional data bus, D[7:0].
7. Next, the µC/µP should initiate the bus cycle by toggling the RD_DS (Data Strobe) input pin "Low". When
the Framer senses that the WR_R/W (R/W*) input pin is "High" and that the RD_DS (Data Strobe) input pin
has toggled "Low", it will enable the input drivers of the bi-directional data bus, D[7:0].
8. After waiting the appropriate time, for this newly placed data to settle on the bi-directional data bus (e.g.,
the Data Setup time) the Framer will assert the RDY_DTACK output signal “Low”.
9. After the µC/µP detects the RDY_DTACK signal (from the Framer), the µC/µP should toggle the RD_DS
input pin "High". This action accomplishes two things.
a. It latches the contents of the bi-directional data bus into the Microprocessor Interface block.
b. It terminates the Write cycle.
Figure 7 presents a timing diagram which illustrates the behavior of the Microprocessor Interface signals, dur-
ing a Motorola-type Programmed I/O Write Operation.
56
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
FIGURE 7. MOTOROLA µP INTERFACE SIGNAL DURING PROGRAMMED I/O WRITE OPERATION
ALE_AS
A[6:0]
CS
Address of target Register
D[7:0]
Data to be Written
RD
WR
RDY_DTACK
1.3.2.3 Burst Mode I/O for Data Access
Burst Mode I/O access is a much faster way to transfer data between the µC/µP and the Microprocessor Inter-
face (of the Framer), than Programmed I/O. The reason why Burst Mode I/O is faster is explained below.
Data is placed upon the Address Bus input pins A[6:0] only for the very first access, within a given burst ac-
cess. The remaining read or write operations (within this burst access) do not require the placement of the Ad-
dress Data on the Address Data Bus. As a consequence, the user does not have to wait through the Address
Setup and Hold times for each of these Read/Write operation, within the Burst Access.
It is important to note that there are some limitations associated with Burst Mode I/O Operations.
1. All cycles within the Burst Access, must be either all Read or all Write cycles. No mixing of Read and Write
cycles is permitted.
2. A Burst Access can only be used when Read or Write operations are to be employed over a contiguous
range of address locations, within the Framer.
3. The very first Read or Write cycle, within a burst access, must start at the lowest address value, of the
range of addresses to be accessed. Subsequent operations will automatically be incremented to the very
next higher address value.
Examples of Burst Mode I/O operations are presented below for read and write operations, with both Intel-type
and Motorola-type µC/µP.
1.3.2.3.1 Burst I/O Access: Intel Mode
If the XRT84L38 Framer is interfaced to an Intel-type µC/µP (e.g., the 80x86 family, etc.), then it should be con-
figured to operate in the Intel mode (by tying the MOTO pin to ground). Intel-type Read and Write Burst I/O Ac-
cess operations are described below.
1.3.2.3.1.1 Intel-Mode Read Burst Access
When an Intel-type µC/µP wants to read the contents of numerous registers or buffer locations over a contigu-
ous range of addresses, then it should do the following.
a. Perform the initial read operation of the burst access.
b. Perform the remaining read operations of the burst access.
c. Terminate the burst access operation.
Each of these operations within the burst access are described below.
1.3.2.3.1.1.1 Initial Read Operation: Intel mode
57
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The initial read operation of an Intel-type read burst access is accomplished by executing a Programmed I/O
Read Cycle as summarized below.
A.0 Execute a Single Ordinary (Programmed I/O) Read Cycle, as described in steps A.1 through A.7 below.
A.1 Place the address of the initial-target register or buffer location (within the Framer) on the Address Bus
input pins A[6:0].
A.2 While the µC/µP is placing this address value onto the Address Bus, the Address Decoding circuitry
(within the user's system) should assert the CS input pin of the Framer, by toggling it "Low". This step
enables further communication between the µC/µP and the Framer Microprocessor Interface block.
A.3 Assert the ALE_AS (Address Latch Enable) pin by toggling it "High". This step enables the Address Bus
input drivers, within the Microprocessor Interface block of the Framer.
A.4 After allowing the data on the Address Bus pins to settle (by waiting the appropriate Address Data Setup
time), the µC/µP should then toggle the ALE_AS pin "Low". This step latches the contents, on the
Address Bus pins, A[6:0], into the Framer Microprocessor Interface block. At this point, the initial address
of the burst access has now been selected.
NOTE: The ALE_AS input pin should remain "Low" for the remainder of this Burst Access operation.
A.5 Next, the µC/µP should indicate that this current bus cycle is a Read Operation by toggling the RD_DS
(Read Strobe) input pin "Low". This action also enables the bi-directional data bus output drivers of the
Framer. At this point, the bi-directional data bus output drivers will proceed to drive the contents of the
addressed register onto the bi-directional data bus, D[7:0].
A.6 Immediately after the µC/µP toggles the Read Strobe signal "Low", the Framer will toggle the
RDY_DTACK (READY) output pin "Low". The Framer does this in order to inform the µC/µP that the data
(to be read from the data bus) is NOT READY to be latched into the µC/µP.
A.7 After some settling time, the data on the bi-directional data bus will stabilize and can be read by the µC/
µP. The Framer will indicate that this data is ready to be read, by toggling the RDY_DTACK (Ready) sig-
nal "High".
A.8 After the µC/µP detects the RDY_DTACK signal (from the Framer), it can then will terminate the Read
cycle by toggling the RD_DS (Read Strobe) input pin "High".
Figure 8 presents an illustration of the behavior of the Microprocessor Interface Signals, during the initial Read
Operation, within a Burst I/O Cycle for an Intel-type µC/µP.
FIGURE 8. INTEL µP INTERFACE SIGNALS, DURING THE INITIAL READ OPERATION OF A BURST CYCLE
ALE_AS
A[6:0]
CS
Address of Initial Target Register (Offset = 0x00)
Valid Data of
Offset = 0x00
D[7:0]
Not Valid
RD
WR
RDY_DTACK
At the completion of this initial read cycle, the µC/µP has read in the contents of the first register or buffer loca-
tion (within the Framer) for this particular burst I/O access operation. In order to illustrate how this burst access
58
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
operation works, the byte (or word) of data, that is being read in Figure 8, has been labeled Valid Data at Offset
= 0x00. This label indicates that the µC/µP is reading the very first register (or buffer location) in this burst ac-
cess operation.
59
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
1.3.2.3.1.1.2 Subsequent Read Operations
The procedure that the µC/µP must use to perform the remaining read cycles, within this Burst Access opera-
tion, is presented below.
B.0 Execute each subsequent Read Cycles, as described in steps 1 through 3 below.
B.1 Without toggling the ALE_AS input pin (e.g., keeping it "Low"), toggle the RD_DS input pin "Low". This
step accomplishes the following.
a. The Framer will internally increments the latched address value (within the Microprocessor Interface circuitry).
b. The output drivers of the bi-directional data bus, D[7:0] are enabled. At some time later, the register or buffer location
corresponding to the incremented latched address value will be driven onto the bi-directional data bus.
B.2 Immediately after the Read Strobe pin toggles "Low" the Framer will toggle the RDY_DTACK (READY)
output pin "Low" to indicate its NOT READY status.
B.3 After some settling time, the data on the bi-directional data bus will stabilize and can be read by the µC/
µP. The Framer will indicate that this data is ready to be read by toggling the RDY_DTACK (READY) sig-
nal "High".
B.4 After the µC/µP detects the RDY_DTACK signal (from the Framer), it can terminate the Read cycle by
toggling the RD_DS (Read Strobe) input pin "High".
For subsequent read operations, within this burst cycle, the µC/µP simply repeats steps 1 through 3, as illus-
trated in Figure 9.
FIGURE 9. INTEL µP INTERFACE SIGNALS, DURING SUBSEQUENT READ OPERATIONS OF A BURST I/O CYCLE
ALE_AS
A[6:0]
CS
Address of Initial Target Register (Offset = 0x00)
Not
Valid
Valid Data at
Offset = 0x01
Not
Valid
Valid Data at
Offset = 0x02
D[7:0]
RD
WR
RDY_DTACK
In addition to the behavior of the Microprocessor Interface signals, Figure 9 also illustrates other points regard-
ing the Burst Access Operation.
a. The Framer internally increments the address value, from the original latched value shown in Figure 8.
This is illustrated by the data, appearing on the data bus, (for the first read access) being labeled Valid
Data at Offset = 0x01 and that for the second read access being labeled Valid Data at Offset = 0x02.
b. The Framer performs this address incrementing process even though there are no changes in the Address
Bus Data, A[6:0].
60
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
1.3.2.3.1.1.3 Terminating the Burst Access Operation
The Burst Access Operation will be terminated upon the rising edge of the ALE_AS input signal. At this point
the Framer will cease to internally increment the latched address value. Further, the µC/µP is now free to exe-
cute either a Programmed I/O access or to start another Burst Access Operation with the Framer.
1.3.2.3.1.2 Write Burst Access: Intel-Mode
When an Intel-type µC/µP wishes to write data into a contiguous range of addresses, then it should do the fol-
lowing.
a. Perform the initial write operation of the burst access.
b. Perform the remaining write operations, of the burst access.
c. Terminate the burst access operation.
Each of these operations within the burst access are described below.
1.3.2.3.1.2.1 Initial Write Operation
The initial write operation of an Intel-type Write Burst Access is accomplished by executing a Programmed I/O
write cycle as summarized below.
A.0 Execute a Single Ordinary (Programmed I/O) Write cycle, as described in Steps A.1 through A.7 below.
A.1 Place the address of the initial target register (or buffer location) within the Framer, on the Address Bus
pins, A[6:0].
A.2 At the same time, the Address-Decoding circuitry (within the user's system) should assert the CS (Chip
Select) input pin of the Framer, by toggling it "Low". This step enables further communication between
the µC/µP and the Framer Microprocessor Interface block.
A.3 Assert the ALE_AS (Address Latch Enable) input pin "High". This step enables the Address Bus input
drivers, within the Microprocessor Interface Block of the Framer.
A.4 After allowing the data on the Address Bus pins to settle (by waiting the appropriate Address Setup
time), the µC/µP should then toggle the ALE_AS input pin "Low". This step latches the contents, on the
Address Bus pins, A[6:0], into the XRT84L38 Framer Microprocessor Interface block. At this point, the
initial address of the burst access has now been selected.
NOTE: The ALE_AS input pin should remain "Low" for the remainder of this Burst I/O Access operation.
A.5 Next, the µC/µP should indicate that this current bus cycle is a Write operation by keeping the RD_DS
pin "High" and toggling the WR_R/W (Write Strobe) pin "Low". This action also enables the bi-directional
data bus input drivers of the Framer.
A.6 The µC/µP places the byte (or word) that it intends to write into the target register on the bi-directional
data bus, D[7:0].
A.7 After waiting the appropriate amount of time, for the data (on the bi-directional data bus) to settle, the µC/
µP should toggle the WR_R/W (Write Strobe) input pin "High". This action accomplishes two things.
a. It latches the contents of the bi-directional data bus into the Framer Microprocessor Interface Block.
b. It terminates the write cycle.
61
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
Figure 10 presents a timing diagram which illustrates the behavior of the Microprocessor Interface signals, dur-
ing the initial write operation within a Burst Access, for an Intel-type µC/µP.
FIGURE 10. INTEL µP INTERFACE SIGNALS, DURING THE INITIAL WRITE OPERATION OF A BURST CYCLE
ALE_AS
A[6:0]
CS
Address of Initial Target Register (Offset = 0x00)
Data to be Written
(Offset = 0x00)
D[7:0]
RD
WR
RDY_DTACK
At the completion of this initial write cycle, the µC/µP has written a byte or word into the first register or buffer
location (within the Framer) for this particular burst access operation. In order to illustrate this point, the byte (or
word) of data, that is being written in Figure 10 has been labeled Data to be Written (Offset = 0x00).
62
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
1.3.2.3.1.2.2 The Subsequent Write Operations
The procedure that the µC/µP must use to perform the remaining write cycles, within this burst access opera-
tion, is presented below.
B.0 Execute each subsequent write cycle, as described in steps B.1 through B.3.
B.1 Without toggling the ALE_AS input pin (e.g., keeping it "Low"), apply the value of the next byte or word
(to be written into the Framer) to the bi-directional data bus pins, D[7:0].
B.2 Toggle the WR_R/W (Write Strobe) input pin "Low". This step accomplishes two things.
a. It enables the input drivers of the bi-directional data bus.
b. It causes the Framer to internally increment the value of the latched address.
B.3 After waiting the appropriate amount of settling time the data, in the internal data bus, will stabilize and is
ready to be latched into the Framer Microprocessor Interface block. At this point, the µC/µP should latch
the data into the Framer by toggling the WR_R/W input pin "High".
For subsequent write operations, within this burst I/O access, the µC/µP simply repeats steps B.1 through B.3,
as illustrated in Figure 11.
FIGURE 11. µP INTERFACE SIGNALS, DURING SUBSEQUENT WRITE OPERATIONS OF A BURST I/O CYCLE
ALE_AS
A[6:0]
CS
Address of Initial Target Register (Offset = 0x00)
D[7:0]
Data Written at Offset = 0x01
Data Written at Offset = 0x02
RD
WR
RDY_DTACK
1.3.2.3.1.2.3 Terminating the Burst I/O Access
Burst Access Operation will be terminated upon the rising edge of the ALE_AS input signal. At this point the
Framer will cease to internally increment the latched address value. Further, the µC/µP is now free to execute
either a Programmed I/O access or to start another Burst Access Operation with the XRT84L38 Framer.
1.3.2.3.2 Burst I/O Access: Motorola Mode
If the XRT84L38 Framer is interfaced to a Motorola-type µC/µP (e.g., the MC680x0 family, etc.), then it should
be configured to operate in the Motorola mode (by tying the MOTO pin to VCC). Motorola-type Read and Write
Burst I/O Access operations are described below.
1.3.2.3.2.1 Read Burst I/O Access Operation: Motorola-Mode
Whenever a Motorola-type µC/µP wishes to read the contents of numerous registers or buffer locations over a
contiguous range of addresses, then it should do the following.
a. Perform the initial Read operation of the burst access.
b. Perform the remaining read operations in the burst access.
c. Terminate the burst access operation.
Each of these operations, within the Burst Access are discussed below.
63
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
1.3.2.3.2.1.1 Initial Read Operation: Motorola Mode
The initial read operation of a Motorola-type read burst access is accomplished by executing a Programmed I/
O Read cycle, as summarized below.
A.0 Execute a Single Ordinary (Programmed I/O) Read Cycle, as described in steps A.1 through A.8 below.
A.1 Assert the ALE_AS (AS) input pin by toggling it "Low". This step enables the Address Bus input drivers
(within the Framer) within the Framer Microprocessor Interface Block.
A.2 Place the address of the initial target register or buffer location (within the Framer), on the Address Bus
input pins, A[6:0].
A.3 At the same time, the Address-Decoding circuitry (within the user's system) should assert the CS (Chip
Select) input pins of the Framer by toggling it "Low". This action enables further communication between
the µC/µP and the Framer Microprocessor Interface block.
A.4 After allowing the data on the Address Bus pins to settle (by waiting the appropriate Address Setup
time), the µC/µP should toggle the ALE_AS input pin "High". This step causes the Framer to latch the
contents of the Address Bus into its internal circuitry. At this point, the initial address of the burst access
has now been selected.
A.5 Further, the µC/µP should indicate that this cycle is a Read cycle by setting the WR_R/W (R/W) input pin
"High".
A.6 Next the µC/µP should initiate the current bus cycle by toggling the RD_DS (Data Strobe) input pin
"Low". This step will enable the bi-directional data bus output drivers, within the Framer. At this point, the
bi-directional data bus output drivers will proceed to driver the contents of the Address register onto the
bi-directional data bus.
A.7 After some settling time, the data on the bi-directional data bus will stabilize and can be read by the µC/
µP. The Framer will indicate that this data can be read by asserting the RDY_DTACK (DTACK) signal
“Low”.
A.8 After the µC/µP detects the RDY_DTACK signal (from the Framer) it will terminate the Read Cycle by tog-
gling the RD_DS (Data Strobe) input pin "High".
Figure 12 presents an illustration of the behavior of the Microprocessor Interface Signals during the initial Read
Operation, within a Burst I/O Cycle, for a Motorola-type µC/µP.
FIGURE 12. MOTOROLA µP INTERFACE SIGNALS DURING THE INITIAL READ OPERATION OF A BURST CYCLE
ALE_AS
A[6:0]
CS
Address of Initial Target Register (Offset = 0x00)
Valid Data at
Offset = 0x00
D[7:0]
Not Valid
RD
WR
RDY_DTACK
At the completion of this initial read cycle, the µC/µP has read in the contents of the first register or buffer loca-
tion (within the Framer) for this particular burst access operation. In order to illustrate how this burst I/O cycle
64
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
works, the byte (or word) of data, that is being read in Figure 12 has been labeled Valid Data at Offset = 0x00.
This indicates that the µC/µP is reading the very first register (or buffer location) in this burst access.
1.3.2.3.2.1.2 Subsequent Read Operations
The procedure that the µC/µP must use to perform the remaining read cycles, within this Burst Access opera-
tion, is presented below.
B.0 Execute each subsequent Read Cycle, as described in steps B.1 through B.3, below.
B.1 Without toggling the ALE_AS input pin (e.g., keeping it "High"), toggle the RD_DS (Data Strobe) input pin
"Low". This step accomplishes the following.
a. The Framer internally increments the latched address value (within the Microprocessor Interface circuitry).
b. The output drivers of the bi-directional data bus (D[7:0]) are enabled. At some time later, the register or
buffer location corresponding to the incremented latched address value will be driven onto the bi-direc-
tional data bus.
NOTE: In order to insure that the Framer will interpret this signal as being a Read signal, the µC/µP should keep the
WR_R/W input pin "High".
B.2 After some settling time, the data on the bi-directional data bus will stabilize and can be read by the µC/
µP. The Framer will indicate that this data is ready to be read by asserting the RDY_DTACK (DTACK) sig-
nal “Low”.
B.3 After the µC/µP detects the RDY_DTACK signal (from the Framer), it terminates the Read cycle by tog-
gling the RD_DS (Data Strobe) input pin "High".
For subsequent read operations, within this burst cycle, the µC/µP simply repeats steps B.1 through B.3, as il-
lustrated in Figure 13.
FIGURE 13. MOTOROLA µP INTERFACE SIGNALS, DURING SUBSEQUENT READ OPERATIONS OF A BURST I/O CYCLE
ALE_AS
A[6:0]
CS
Address of Initial Target Register (Offset = 0x00)
Valid Data at
Offset = 0x01
Valid Data at
Offset = 0x02
D[7:0]
Not Valid
Not Valid
RD
WR
RDY_DTACK
1.3.2.3.2.1.3 Terminating Burst Access Operation
The Burst I/O Access will be terminated upon the falling edge of the ALE_AS input signal. At this point the
Framer will cease to internally increment the latched address value. Further, the µC/µP is now free to execute
either a Programmed I/O access or to start another Burst Access Operation with the Framer.
1.3.2.3.2.2 Write Burst Access: Motorola-Mode
Whenever a Motorola-type µC/µP wishes to write the contents of numerous registers or buffer locations over a
contiguous range of addresses, then it should do the following.
a. Perform the initial write operation of the burst access.
b. Perform the remaining write operations, of the burst access.
65
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
c. Terminate the burst access operation.
1.3.2.3.2.2.1 Initial Write Operation
The initial write operation of a Motorola-type Write Burst Access is accomplished by executing a Programmed
I/O Write Cycle as summarized below.
A.0 Execute a Single Ordinary (Programmed I/O) Write cycle, as described in Steps A.1 through A.7 below.
A.1 Assert the ALE_AS (Address Strobe) input pin by toggling it "Low". This step enables the Address Bus
input drivers (within the Framer).
A.2 Place the address of the initial target register or buffer location (within the Framer), on the Address Bus
input pins, A[6:0].
A.3 At the same time, the Address-Decoding circuitry (within the user's system) should assert the CS input
pin of the Framer by toggling it "Low". This step enables further communication between the µC/µP and
the Framer Microprocessor Interface block.
A.4 After allowing the data on the Address Bus pins to settle (by waiting the appropriate Address Setup
time), the µC/µP should toggle the ALE_AS input pin "High". This step causes the Framer to latch the
contents of the Address Bus into its own circuitry. At this point, the initial address of the burst access has
now been selected.
A.5 Further, the µC/µP should indicate that this current bus cycle is a Write operation by toggling the WR_R/
W (R/W) input pin "Low".
A.6 The µC/µP should then place the byte or word that it intends to write into the target register, on the bi-
directional data bus, D[7:0].
A.7 Next, the µC/µP should initiate the bus cycle by toggling the RD_DS (Data Strobe) input pin "Low". When
the XRT84L38 Framer senses that the WR_R/W input pin is "Low", and that the RD_DS input pin has tog-
gled "Low" it will enable the input drivers of the bi-directional data bus, D[7:0].
A.8 After waiting the appropriate amount of time, for this newly placed data to settle on the bi-directional data
bus (e.g., the Data Setup time) the Framer will assert the RDY_DTACK (DTACK) output signal.
A.9 After the µP/µC detects the RDY_DTACK signal (from the Framer) it should toggle the RD_DS input pin
"High". This action accomplishes two things:
a. It latches the contents of the bi-directional data bus into the Framer Microprocessor Interface block.
b. It terminates the Write cycle.
66
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
Figure 14 presents a timing diagram which illustrates the behavior of the Microprocessor Interface signals, dur-
ing the Initial write operation within a Burst Access, for a Motorola-type µC/µP.
FIGURE 14. MOTOROLA µP INTERFACE SIGNALS, DURING THE INITIAL WRITE OPERATION OF A BURST CYCLE
ALE_AS
A[6:0]
CS
Address of Initial Target Register (Offset = 0x00)
Data to be Written
(Offset = 0x00)
D[7:0]
RD
WR
RDY_DTACK
At the completion of this initial write cycle, the µC/µP has written a byte or word into the first register or buffer
location (within the Framer) for this particular burst I/O access. In order to illustrate how this burst I/O cycle
works, the byte (or word) of data, that is being written in Figure 14 has been labeled Data to be Written (Offset
= 0x00).
1.3.2.3.2.2.2 The Subsequent Write Operations
The procedure that the µC/µP must use to perform the remaining write cycles, within this burst access opera-
tion, is presented below.
B.0 Execute each subsequent write cycle, as described in steps B.1 through B.3.
B.1 Without toggling the ALE_AS input pin (e.g., keeping it "Low"), apply the value of the next byte or word
(to be written into the Framer) to the bi-directional data bus pins, D[7:0].
B.2 Toggle the WR_R/W (Write Strobe) input pin "Low". This step accomplishes two things.
a. It enables the input drivers of the bi-directional data bus.
b. It causes the Framer to internally increment the value of the latched address.
B.3 After waiting the appropriate amount of settling time the data, in the internal data bus, will stabilize and is
ready to be latched into the Framer Microprocessor Interface block. At this point, the µC/µP should latch
the data into the Framer by toggling the WR_R/W input pin "High".
67
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
For subsequent write operations, within this burst I/O access, the µC/µP simply repeats steps B.1 through B.3,
as illustrated in Figure 15.
FIGURE 15. MOTOROLA µP INTERFACE SIGNALS DURING SUBSEQUENT WRITE OPERATIONS OF A BURST I/O CYCLE
ALE_AS
A[6:0]
CS
Address of Initial Target Register (Offset = 0x00)
D[7:0]
Data Written at Offset = 0x01
Data Written at Offset = 0x02
RD
WR
RDY_DTACK
1.3.2.3.2.2.3 Terminating the Burst I/O Access
The Burst I/O Access will be terminated upon the falling edge of the ALE_AS input signal. At this point the
Framer will cease to internally increment the latched address value. Further, the µC/µP is now free to execute
either a Programmed I/O access or to start another Burst I/O Access with the Framer.
1.4 DMA READ/WRITE OPERATIONS
The XRT84L38 Framer contains two DMA Controller Interfaces which provide support for all eight framers within
the chip. The purpose of the two DMA Controllers is to facilitate the rapid block transfer of data between an ex-
ternal memory location and the on-chip HDLC buffers via the Microprocessor Interface.
68
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
DMA-0 WRITE DMA INTERFACE
DMA 0 Controller Interface handles data transfer between external memory and the selected Transmit HDLC
Buffer.
The DMA cycle starts when the XRT84L38 asserts the REQ0 output pin. The external DMA Controller then re-
sponds by asserting the ACK0 input pin. The contents of the Microprocessor Interface bi-directional data bus
are latched into the XRT84L38 each time the pWRL (Write Strobe) input pin is strobed “Low”.
The XRT84L38 ends the DMA cycle by negating the DMA request input (REQ0) while WR is still active. The ex-
ternal DMA Controller acknowledges the end of DMA Transfer by driving the ACK0 input pin “High”.
FIGURE 16. DMA MODE FOR THE XRT84L38 AND A MICROPROCESSOR
REQ[1:0]
ACK[1:0]
WR
RD
µ
PCLK
DATA[7:0]
XRT84L38
Microprocessor
1.5 MEMORY AND REGISTER MAP
This section presents a complete list of the Framer external memory address map and the internal memory
map. In addition, the allocations of the three internal storage spaces is depicted.
1.5.1 Memory Mapped I/O Indirect Addressing
The XRT84L38 employs a complete indirect addressing approach for the Microprocessor Interface; in order to
support multiple channel implementations, maintaining rich user-controlled features, minimizing the total pin
count and providing future scalability without sacrificing performance for microcontroller access. Eight address
bits are used with the 4 MSB (most significant bits) identifying each of the eight framers channels and the 4
LSBs to address the indirect mapping registers.
The XRT84L38 framer has approximately 5,800 addressable spaces internally. If each of these addresses has
to be accessed directly, it would require a 13-bit address bus. In order to control total pin count as well as to
provide future scalability, the XRT84L38 employs an Indirect Addressing Scheme. Using this technique, only 7
address input pins on the XRT84L38 are needed.
The addressable spaces within the XRT84L38 are divided into groups of registers. Each register group con-
sists of a specific number of indirect address registers and a same number of indirect data registers with the
exception of LAPD Buffer 0 and 1. Of the 7 total address input bits, the 3 MSB pins are used to identify each of
eight T1/E1 framer channels. The remaining 4 LSB bits are used to address the register groups. Table 8 indi-
cates the address mapping of all the register groups within the XRT84L38. Please note that the indirect ad-
dress registers are with even addresses and the corresponding indirect data registers are with odd addresses
with the exception of, again, the LAPD Buffer 0 and 1. The n corresponds to the channel number.
69
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
TABLE 8: ADDRESS MAP
ADDRESS
n_0H
CONTENTS
Channel_n - Control Register Indirect Address Register
Channel_n - Control Register Indirect Data Register
Channel_n - Channel Control Indirect Address Register
Channel_n - Channel Control Indirect Data Register
n_1H
n_2H
n_3H
n_4H
Channel_n - Receive Signaling Array Indirect Address Register
Channel_n - Receive Signaling Array Indirect Data Register
Channel_n - LAPD Buffer 0 Indirect Data Register
Channel_n - LAPD Buffer 1 Indirect Data Register
Channel_n - Performance Monitor Indirect Address register
Channel_n - Performance Monitor Indirect Data register
Channel_n - Interrupt Indirect Address register
Channel_n - Interrupt Indirect Data register
n_5H
n_6H
n_7H
n_8H
n_9H
n_AH
n_BH
n_CH - n_FH
Reserved
To access each individual register inside each group, a two-step access by the micro-controller to the
XRT84L38 is required. In the first step, a micro-controller WRITE access specifying the indirect address for that
register within the register group should be done to the indirect address register of that group. In the second
step, a micro-controller READ or WRITE should access the indirect data register of that group. For example, in
order to write 0DH into the Framing Select Register of Channel 5 (address 0x50H>07H), one needs to do the
following:
WR
0x50 0x07
Write 0x07Hex into the indirect address register (0x50Hex) to specify address of the Framing Select Register
within the Control Register group.
WR
0x51 0x0D
Actually WRITE value 0x0DHex into the indirect data register (0x51Hex) of the Control Register group.
The value of the indirect address register will increment after each access of the corresponding indirect data
register. Using the above example for illustration, after WRITE to the indirect data register (0x51Hex), the value
stored inside the indirect address register (0x50Hex) would become 0x08Hex. This feature can greatly en-
hance the users' ability to access consecutive locations within a certain register group.
For LAPD Buffer 0 and 1 with addresses 0x06Hex and 0x07Hex respectively, there is no indirect address regis-
ter. A micro-controller WRITE access to these data registers will access the LAPD Transmit Buffers and a mi-
cro-controller READ will access the LAPD Receive Buffers. The very first access of the LAPD buffers will al-
ways to location 0. After each access, the pointer within the LAPD buffer will automatically increment by one,
making further access to the next location within the buffer. User should keep track of the current location in-
side the buffer the READ or WRITE is associated with.
70
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
1.6 DESCRIPTION OF THE CONTROL REGISTERS
Clock Select Register (CSR) - T1 Mode(Indirect Address = 0xn0H, 0x00H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Bipolar
Violation
Insertion
T1, E1 Select
8KHz
Synchroniza-
tion
Clock Loss
Detection
Enable
OSCCLK
Frequency
Select Bit 1
OSCCLK
Frequency
Transmit
Timing
Transmit
Timing
Select Bit 0 SourceSelect SourceSelect
Enable
Bit 1
R/W
0
Bit 0
R/W
1
R/W
0
R/W
0
R/W
0
R/W
1
R/W
0
R/W
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Bipolar Violation Insertion
R/W
Bipolar Violation Insertion:
This READ/WRITE bit-field permits the user to insert Bipolar
Violation to the transmit encoder.
The line coding for the DS1 signal should be bipolar. This signal-
ing technique consists of transmitting a binary "0" as zero volts,
while a binary "1" is transmitted as either a positive or negative
pulse, opposite in polarity to the previous pulse. A Bipolar Viola-
tion occurs when the alternate polarity rule is violated.
A zero-to-one transition of the bit will cause one Bipolar Violation
to be inserted into the outgoing data stream.
6
T1/E1 Select
R/W
T1/E1 Select:
This READ/WRITE bit-field permits the user to select which
mode the framer will be operating.
When this bit is set to one:
The framer is in T1 mode.
When this bit is set to zero:
The framer is in E1 mode.
5
8KHz Synchronization
Enable
R/W
8KHz Synchronization Enable:
This READ/WRITE bit-field permits the user to activate and de-
activate the 8KHz synchronization of the framer.
An 8KHz external reference clock can be provided to the framer.
When this bit is set to one:
If the Transmit Clock Source Select bits are set to two, the trans-
mit clocks of all eight channels will be synchronized to the exter-
nal applied 8KHz reference clock and thus have the same
frequency and the same phase.
71
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
4
Clock Loss Detection
Enable
R/W
Clock Loss Detection Enable:
This READ/WRITE bit-field permits the user to enable the Clock
Loss Detection logic for the framer when the Recovered Receive
Line Clock is used as transmit timing source of the framer.
When this bit is set to zero:
The framer disables the Clock Loss Detection logic.
When this bit is set to one:
The framer enables the Clock Loss Detection logic. If the Recov-
ered Receive Line Clock is used as transmit timing source of the
framer, and if clock recovered from the LIU is lost, the framer can
detect loss of the Recovered Receive Line Clock. Upon detecting
of this occurrence, the framer will automatically begin to use the
OSCCLK Driven Divided clock as transmit timing source until the
LIU is able to regain clock recovery.
NOTE: This bit-field is ignored if the TxSerClk or the OSCCLK
Driven Divided clock is chosen to be the timing source of Trans-
mit Section of the framer.
3-2
OSCCLK Frequency
Select
R/W
OSCCLK Frequency Select:
These two READ/WRITE bit-fields permit the user to select inter-
nal clock dividing logic of the framer depending on the frequency
of incoming oscillator clock (OSCCLK). The frequency of internal
clock used by the framer should be 12.352MHz.
When these bits are set to 00:
The framer will internally divide the incoming OSCCLK by one.
Therefore, the external oscillator clock applied to the OSCCLK
pin should be 12.352MHz.
When these bits are set to 01:
The framer will internally divide the incoming OSCCLK by two.
Therefore, the external oscillator clock applied to the OSCCLK
pin should be 24.704MHz.
When these bits are set to 10:
The framer will internally divide the incoming OSCCLK by four.
Therefore, the external oscillator clock applied to the OSCCLK
pin should be 49.408MHz.
72
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1-0
Transmit Timing Source
Select
R/W
Transmit Timing Source Select:
These two READ/WRITE bit-fields permit the user to select the
timing source of Transmit section of the framer.
When the framer is operating at non-multiplexed mode, that is,
the Transmit Back-plane interface is operating at a clock rate of
1.544MHz for T1, these two READ/WRITE bit-fields also deter-
mine the direction of Single Frame Synchronization Pulse
(TxSync), Multi-frame Synchronization Pulse (TxMSync) and
Transmit Serial Clock Input (TxSerClk). When the framer is oper-
ating at other Back-plane mode, the Single Frame Synchroniza-
tion Pulse (TxSync), Multi-frame Synchronization Pulse
(TxMSync) and Transmit Serial Clock Input (TxSerClk) are all
inputs.
When these bits are set to 00:
The Recovered Receive Line Clock is the timing source of Trans-
mit section of the framer. When operating at the non-multiplexed
1.544MHz Back-plane Interface mode, the Single Frame Syn-
chronization Pulse (TxSync), Multi-frame Synchronization Pulse
(TxMSync) and Transmit Serial Clock Input (TxSerClk) are all
outputs. Upon losing of the Recovered Receiver Line Clock, the
OSCCLK Driven Divided clock is automatically chosen to be the
timing source of the Transmit section of the framer.
When these bits are set to 01:
The Transmit Serial Clock is the timing source of Transmit sec-
tion of the framer. When operating at the non-multiplexed
1.544MHz Back-plane Interface mode, the Single Frame Syn-
chronization Pulse (TxSync), Multi-frame Synchronization Pulse
(TxMSync) and Transmit Serial Clock Input (TxSerClk) are all
inputs.
When these bits are set to 10:
The OSCCLK Driven Divided clock is the timing source of Trans-
mit section of the framer. When operating at the non-multiplexed
1.544MHz Back-plane Interface mode, the Single Frame Syn-
chronization Pulse (TxSync), Multi-frame Synchronization Pulse
(TxMSync) and Transmit Serial Clock Input (TxSerClk) are all
outputs. Upon losing of the Recovered Receiver Line Clock, the
OSCCLK Driven Divided clock is automatically chosen to be the
timing source of the Transmit section of the framer.
When these bits are set to 11:
The Recovered Receive Line Clock is the timing source of Trans-
mit section of the framer. When operating at the non-multiplexed
1.544MHz Back-plane Interface mode, the Single Frame Syn-
chronization Pulse (TxSync), Multi-frame Synchronization Pulse
(TxMSync) and Transmit Serial Clock Input (TxSerClk) are all
outputs. Upon losing of the Recovered Receiver Line Clock, the
OSCCLK Driven Divided clock is automatically chosen to be the
timing source of the Transmit section of the framer.
73
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
Clock Select Register (CSR) - E1 Mode (Indirect Address = 0xn0H, 0x00H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Bipolar
Violation
Insertion
T1, E1 Select
8KHz
Synchroniza-
tion
Clock Loss
Detection
Enable
OSCCLK
Frequency
Select Bit 1
OSCCLK
Frequency
Transmit
Timing
Transmit
Timing
Select Bit 0 SourceSelect SourceSelect
Enable
Bit1
R/W
0
Bit0
R/W
1
R/W
0
R/W
0
R/W
0
R/W
1
R/W
0
R/W
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Bipolar Violation Insertion
R/W
Bipolar Violation Insertion:
This READ/WRITE bit-field permits the user to insert Bipolar
Violation to the transmit encoder.
The line coding for the DS1 signal should be bipolar. This signal-
ing technique consists of transmitting a binary "0" as zero volts,
while a binary "1" is transmitted as either a positive or negative
pulse, opposite in polarity to the previous pulse. A Bipolar Viola-
tion occurs when the alternate polarity rule is violated.
A zero-to-one transition of the bit will cause one Bipolar Violation
to be inserted into the outgoing data stream.
6
T1/E1 Select
R/W
T1/E1 Select:
This READ/WRITE bit-field permits the user to select which
mode the framer will be operating.
When this bit is set to one:
The framer is in T1 mode.
When this bit is set to zero:
The framer is in E1 mode.
5
8KHz Synchronization
Enable
R/W
8KHz Synchronization Enable:
This READ/WRITE bit-field permits the user to activate and de-
activate the 8KHz synchronization of the framer.
An 8KHz external reference clock can be provided to the framer.
When this bit is set to one:
If the Transmit Clock Source Select bits are set to two, the trans-
mit clocks of all eight channels will be synchronized to the exter-
nal applied 8KHz reference clock and thus have the same
frequency and the same phase.
74
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
4
Clock Loss Detection
Enable
R/W
Clock Loss Detection Enable:
This READ/WRITE bit-field permits the user to enable the Clock
Loss Detection logic for the framer when the Recovered Receive
Line Clock is used as transmit timing source of the framer.
When this bit is set to zero:
The framer disables the Clock Loss Detection logic.
When this bit is set to one:
The framer enables the Clock Loss Detection logic. If the Recov-
ered Receive Line Clock is used as transmit timing source of the
framer, and if clock recovered from the LIU is lost, the framer can
detect loss of the Recovered Receive Line Clock. Upon detecting
of this occurrence, the framer will automatically begin to use the
OSCCLK Driven Divided clock as transmit timing source until the
LIU is able to regain clock recovery.
NOTE: This bit-field is ignored if the TxSerClk or the OSCCLK
Driven Divided clock is chosen to be the timing source of Trans-
mit Section of the framer.
3-2
OSCCLK Frequency
Select
R/W
OSCCLK Frequency Select:
These two READ/WRITE bit-fields permit the user to select inter-
nal clock dividing logic of the framer depending on the frequency
of incoming oscillator clock (OSCCLK). The frequency of internal
clock used by the framer should be 16.384MHz.
When these bits are set to 00:
The framer will internally divide the incoming OSCCLK by one.
Therefore, the external oscillator clock applied to the OSCCLK
pin should be 16.384MHz.
When these bits are set to 01:
The framer will internally divide the incoming OSCCLK by two.
Therefore, the external oscillator clock applied to the OSCCLK
pin should be 32.768MHz.
When these bits are set to 10:
The framer will internally divide the incoming OSCCLK by four.
Therefore, the external oscillator clock applied to the OSCCLK
pin should be 65.536MHz.
75
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1-0
Transmit Timing Source
Select
R/W
Transmit Timing Source Select:
These two READ/WRITE bit-fields permit the user to select the
timing source of Transmit section of the framer.
When the framer is operating at non-multiplexed mode, that is,
the Transmit Back-plane interface is operating at a clock rate of
2.048MHz for T1, these two READ/WRITE bit-fields also deter-
mine the direction of Single Frame Synchronization Pulse
(TxSync), Multi-frame Synchronization Pulse (TxMSync) and
Transmit Serial Clock Input (TxSerClk). When the framer is oper-
ating at other Back-plane mode, the Single Frame Synchroniza-
tion Pulse (TxSync), Multi-frame Synchronization Pulse
(TxMSync) and Transmit Serial Clock Input (TxSerClk) are all
inputs.
When these bits are set to 00:
The Recovered Receive Line Clock is the timing source of Trans-
mit section of the framer. When operating at the non-multiplexed
2.048MHz Back-plane Interface mode, the Single Frame Syn-
chronization Pulse (TxSync), Multi-frame Synchronization Pulse
(TxMSync) and Transmit Serial Clock Input (TxSerClk) are all
outputs. Upon losing of the Recovered Receiver Line Clock, the
OSCCLK Driven Divided clock is automatically chosen to be the
timing source of the Transmit section of the framer.
When these bits are set to 01:
The Transmit Serial Clock is the timing source of Transmit sec-
tion of the framer. When operating at the non-multiplexed
2.048MHz Back-plane Interface mode, the Single Frame Syn-
chronization Pulse (TxSync), Multi-frame Synchronization Pulse
(TxMSync) and Transmit Serial Clock Input (TxSerClk) are all
inputs.
When these bits are set to 10:
The OSCCLK Driven Divided clock is the timing source of Trans-
mit section of the framer. When operating at the non-multiplexed
2.048MHz Back-plane Interface mode, the Single Frame Syn-
chronization Pulse (TxSync), Multi-frame Synchronization Pulse
(TxMSync) and Transmit Serial Clock Input (TxSerClk) are all
outputs. Upon losing of the Recovered Receiver Line Clock, the
OSCCLK Driven Divided clock is automatically chosen to be the
timing source of the Transmit section of the framer.
When these bits are set to 11:
The Recovered Receive Line Clock is the timing source of Trans-
mit section of the framer. When operating at the non-multiplexed
2.048MHz Back-plane Interface mode, the Single Frame Syn-
chronization Pulse (TxSync), Multi-frame Synchronization Pulse
(TxMSync) and Transmit Serial Clock Input (TxSerClk) are all
outputs. Upon losing of the Recovered Receiver Line Clock, the
OSCCLK Driven Divided clock is automatically chosen to be the
timing source of the Transmit section of the framer.
76
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
Line Interface Control Register (LICR) - T1 Mode (Indirect Address = 0xn0H, 0x01H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Force
Transmit LOS
NRZ Rail
Select
Loop-back
Select Bit 1
Loop-back Transmit Line Receive Line
Transmit
B8ZS Enable B8ZS Enable
Receive
Select Bit 0
Clock
Clock
Inversion
Inversion
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Force Transmit LOS
R/W
Force Transmit LOS:
This READ/WRITE bit-field forces the framer to transmit Loss of
Signal (LOS) onto the LIU interface.
When this bit is set to one:
The framer is forced to transmit an LOS signal onto the LIU inter-
face outputs.
6
NRZ Rail Select
R/W
NRZ Rail Select:
This READ/WRITE bit-field permits the user to select how data
are transmitted to and received from the LIU.
When this bit is set to zero:
The framer is operating in dual-rail mode. The TxPOS pin is car-
rying the positive data and the TxNEG pin is carrying the nega-
tive data. The positive and the negative data combined represent
the entire data stream going to the LIU.
The received data from the LIU will also be bipolar, that is, the
positive data received from RxPOS and the negative data
received from RxNEG combined represent the entire data
stream.
When this bit is set to one:
The framer is operating in single-rail mode. The TxPOS pin is
carrying the entire data stream. The TxNEG pin is carrying the
Multi-frame Synchronization Pulse.
The received data from the LIU will also be single-railed. The
RxPOS pin is carrying the entire data stream going into the
framer from LIU.
77
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
5-4
Loop-back Select
R/W
Loop-back Select:
These READ/WRITE bit-fields permit the user to configure any
channel of the framer to operate in different loop-back modes.
Each channel of the framer can operate in three loop-back
modes:
Local Loop-back (LL), Far-End Line Loop-back (FELL) and Pay-
load Loop-back (PL).Local Loop-back connects the transmitter
output of the framer back to the receiver input. All payload data
as well as data link bits and Frame Alignment bits are directed
back into the framer. The Local-Loop-back allows the perfor-
mance of diagnostic tests on the transmitter and receiver to ver-
ify operation of the framer and equipment-side circuitry.
Payload Loop-back also connects the transmitter output of the
framer back to the receiver input. However, only payload data
and Frame Alignment bits are directed back into the framer. The
framer can still transmit data link information to the remote termi-
nal. The Payload Loop-back allows the performance of diagnos-
tic tests on the transmitter and receiver to verify operation of the
framer and equipment-side circuitry. At the same time, the Pay-
load Loop-back allows performance report and test signal identi-
fication message to be sent to remote side.
Far-End Line Loop-back connects the receiver input to the trans-
mit output. Only the LIU interface logic inside the framer can be
examined using this loop-back mode. During the Far-End Line
Loop-back, the Recovered Receive Line Clock will automatically
be the source of the Transmit Line Clock.
When these bits are set to 00:
The framer is operating in normal mode; no loop-back mode is
selected.
When these bits are set to 01:
The framer is operating in Local Loop-back mode.
When these bits are set to 10:
The framer is operating in Far-End Line Loop-back mode.
When these bits are set to 11:
The framer is operating in Payload Loop-back mode.
3
Transmit Line Clock
Inversion
R/W
Transmit Line Clock Inversion:
This READ/WRITE bit-field permits the user to select which
edge of the Transmit Line Clock will data transition occur.
When this bit is set to zero:
The transmit data transition occurs at rising edge of the Transmit
Line Clock. The user should program the LIU device to sample
data at falling edge of the Transmit Line Clock.
When this bit is set to one:
The transmit data transition occurs at falling edge of the Transmit
Line Clock. The user should program the LIU device to sample
data at rising edge of the Transmit Line Clock.
78
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
2
Receive Line Clock Inver-
sion
R/W
Receive Line Clock Inversion:
This READ/WRITE bit-field permits the user to select which
edge of the Receive Line Clock will be used by the framer to
sample incoming data from LIU.
When this bit is set to zero:
The receive data transition occurs at rising edge of the Receive
Line Clock. The framer will sample data at falling edge of the
Receive Line Clock.
When this bit is set to one:
The receive data transition occurs at falling edge of the Receive
Line Clock. The frame will sample data at rising edge of the
Receive Line Clock.
1
Transmit B8ZS Enable
R/W
Transmit B8ZS Enable:
This READ/WRITE bit-field permits the user to enable transmit
B8ZS encoding.
When this bit is set to zero:
The framer will send out transmit data encoded by B8ZS. The
user should turn off the B8ZS encoding of the LIU device.
When this bit is set to one:
The framer will send out transmit data in AMI line code without
B8ZS encoding. The user should turn on or off B8ZS encoding of
the LIU device depending on system requirement.
0
Receive B8ZS Enable
R/W
Receive B8ZS Enable:
This READ/WRITE bit-field permits the user to enable receive
B8ZS decoding.
When this bit is set to zero:The framer will decode the incoming
data assuming that they are B8ZS encoded.When this bit is set
to one:The framer disables B8ZS decoding of the incoming data.
79
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
Line Control Register (LCR) (Indirect Address = 0xn0H, 0x02H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
GPIO
GPIO
GPIO
GPIO
GPIO Bit 3
GPIO Bit 2
GPIO Bit 1
GPIO Bit 0
Direction
Direction
Direction
Direction
Control Bit 3 Control Bit 2 Control Bit 1 Control Bit 0
R/W
1
R/W
1
R/W
1
R/W
1
R/W
0
R/W
0
R/W
0
R/W
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-4
GPIO Direction Control
R/W
GPIO Direction Control:
These READ/WRITE bit-fields control directions of the four on-
chip General Purpose Input/Output pins.
When these bits are set to zero:
The corresponding GPIO pins are configured as inputs. The user
can now apply signals to the GPIO pins by writing to the corre-
sponding GPIO bit-fields.
When these bits are set to one:
The corresponding GPIO pins are configured as outputs. The
user can read the output values by reading the corresponding
GPIO bit-fields.
3-0
GPIO
R/W
GPIO:
These READ/WRITE bit-fields contain values of the four on-chip
General Purpose Input/Output pins.
When the corresponding GPIO Direction Control bit-fields are
set to zero, the GPIO pins are configured as inputs. The GPIO
bit-fields contain values to be present on the GPIO pins. For
example, if the user wants to pull the pin GPIO_0 HIGH, he/she
can write zero into the GPIO Direction Control Bit 0; then write
one into the GPIO Bit 0.
When the corresponding GPIO Direction Control bit-fields are
set to one, the GPIO pins are configured as outputs. The GPIO
bit-fields contain values currently present on the GPIO pins.
LIU Access Register 1 (LAR1) (Indirect Address = 0xn0H, 0x03H)
BIT 7
LAR1 Bit 7
R/W
BIT 6
LAR1 Bit 6
R/W
BIT 5
LAR1 Bit 5
R/W
BIT 4
LAR1 Bit 4
R/W
BIT3
LAR1 Bit 3
R/W
BIT 2
LAR1 Bit 2
R/W
BIT 1
LAR1 Bit 1
R/W
BIT 0
LAR1 Bit 0
R/W
0
0
0
0
0
0
0
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-0
LAR1
R/W
80
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
LIU Access Register 2 (LAR2) (Indirect Address = 0xn0H, 0x04H)
BIT 7
LAR2 Bit 7
R/W
BIT 6
LAR2 Bit 6
R/W
BIT 5
LAR2 Bit 5
R/W
BIT 4
LAR2 Bit 4
R/W
BIT3
LAR2 Bit 3
R/W
BIT 2
LAR2 Bit 2
R/W
BIT 1
BIT 0
LAR2 Bit 1
LAR2 Bit 0
R/W
0
R/W
0
0
0
0
0
0
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-0
LAR2
R/W
LIU Poll Register 1 (LPR1) (Indirect Address = 0xn0H, 0x05H)
BIT 7
LPR1 Bit 7
R/W
BIT 6
LPR1 Bit 6
R/W
BIT 5
LPR1 Bit 5
R/W
BIT 4
LPR1 Bit 4
R/W
BIT3
LPR1 Bit 3
R/W
BIT 2
LPR1 Bit 2
R/W
BIT 1
BIT 0
LPR1 Bit 0
R/W
LPR1 Bit 1
R/W
0
0
0
0
0
0
0
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-0
LPR1
R/W
LIU Poll Register 2 (LPR2) (Indirect Address = 0xn0H, 0x06H)
BIT 7
LPR2 Bit 7
R/W
BIT 6
LPR2 Bit 6
R/W
BIT 5
LPR2 Bit 5
R/W
BIT 4
LPR2 Bit 4
R/W
BIT3
LPR2 Bit 3
R/W
BIT 2
LPR2 Bit 2
R/W
BIT 1
BIT 0
LPR2 Bit 0
R/W
LPR2 Bit 1
R/W
0
0
0
0
0
0
0
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-0
LPR2
R/W
81
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
Framing Select Register (FSR) - T1 Mode (Indirect Address = 0xn0H, 0x07H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Signaling
Update on
Super-frame
Boundary
CRC
Diagnostics
Select
J1 CRC
One
Fast
T1 Framing
T1 Framing
Select Bit 1
T1 Framing
Select Bit 0
Calculation Synchroniza- Synchroniza- Select Bit 2
tion
Candidate
Only
tion
R/W
0
R/W
0
R/W
0
R/W
0
R/W
1
R/W
0
R/W
0
R/W
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Signaling Update on
R/W
Signaling Update on Super-frame Boundary:
Super-frame Boundary
This READ/WRITE bit-field controls the framer to update signal-
ing data only on Super-frame boundaries.
The user can insert signaling data to the framer through the
TxSIG_n input pins or by writing into the Transmit Signaling Con-
trol Registers (TSCR).
When this bit is set to zero:
The framer will update signaling data once it is received. That is,
any value presents on the TxSIG_n pins or any value pro-
grammed to the TSCR will be inserted into the outgoing data
stream right away. Also, any changes on the TxSIG_n pins or the
TSCR will be instantaneously reflected on the outgoing data
stream.
When this bit is set to one:
The framer will only update signaling data on super-frame
boundaries. Any changes on the TxSIG_n pins or the TSCR will
be ignored until the next super-frame boundary is reached.
6
CRC Diagnostics Select
R/W
CRC Diagnostics Select:
This READ/WRITE bit-field allows the user to insert CRC errors
into outgoing data stream. A transition from zero to one of this bit
will prompt the framer to invert the value of one CRC bit.
When this bit is set to zero:
The framer will operate normally and there is no insertion of
erroneous CRC bit.
When this bit is set to one:
One CRC error will be inserted into the outgoing data stream
when this bit is transitioned from zero to one.
NOTE: To send another CRC error, the framer has to reset this
bit to zero and set it to one again.
82
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
5
J1 CRC Calculation
R/W
J1 CRC Calculation:
This READ/WRITE bit-field forces the framer to calculate CRC-6
bits in J1 format.In J1 format, CRC-6 calculation is done based
on the actual values of all payload bits as well as the framing
bits. In DS1 format, CRC-6 calculation is done based on the pay-
load bits only while assuming all the framing bits are one.
When this bit is set to zero:
The framer will perform CRC-6 calculation in DS1 format.
When this bit is set to one:
The framer will perform CRC-6 calculation in J1 format. This fea-
ture permits the driver to comply with J1 standard.
4
One Synchronization
Candidate Only
R/W
One Synchronization Candidate Only:
This READ/WRITE bit-field forces the framing search engine of
the framer to declare synchronization while there is one and only
one candidate left.
3
Fast Synchronization
T1 Framing Select
R/W
R/W
Fast Synchronization:
This READ/WRITE bit-field permits the framing search engine of
the framer to declare synchronization earlier.
2-0
T1 Framing Select:
These READ/WRITE bit-fields allow the user to select one of the
five T1 framing formats supported by the framer. These framing
formats include ESF, SLC 96, SF, N and T1DM mode.
Framing
Format
Bit 2
Bit 1
Bit 0
ESF
0
1
1
1
1
X
0
0
1
1
X
0
1
0
1
SLC®96
SF
N
T1DM
NOTE: Changing of framing format will automatically force the
framer to RESYNC.
83
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
Framing Select Register (FSR) - E1 Mode (Indirect Address = 0xn0H, 0x07H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Annex B
Enable
CRC
CAS
CAS
CRC-4
CRC-4
FAS
FAS
Selection bit
Diagnostics Selection bit 1 Selection bit 0 Selection bit 1 Selection bit 0 Alignment
Select
Frame Check
Sequence
Enable
R/W
0
R/W
0
R/W
0
R/W
0
R/W
1
R/W
0
R/W
0
R/W
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Annex B Enable
R/W
Signaling Update on Super-frame Boundary:
This READ/WRITE bit-field controls the framer to be compliant
with ITU-T Recommendation G.706 Annex B for CRC-to-non-
CRC internetworking detection.
When this bit is set to zero:
The framer will operate in normal condition. That is, ITU-T G.706
Annex B is disabled.
When this bit is set to one:
The framer will enable support of ITU-T G.706 Annex B.
6
CRC Diagnostics Select
R/W
CRC Diagnostics Select:
This READ/WRITE bit-field allows the user to insert CRC errors
into outgoing data stream. A transition from zero to one of this bit
will prompt the framer to invert the value of one CRC bit.
When this bit is set to zero:
The framer will operate normally and there is no insertion of
erroneous CRC bit.
When this bit is set to one:
One CRC error will be inserted into the outgoing data stream
when this bit is transitioned from zero to one.NOTE:To send
another CRC error, the framer has to reset this bit to zero and set
it to one again.
84
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
5-4
CAS Selection bit
R/W
CAS Selection:
These Read/Write bit fields allow the user to enable searching of
CAS Multi-frame alignment and determine which algorithm of the
two are used for locking the CAS Multi-frame alignment pattern.
When these bits are set to 00:
Searching of CAS Multi-frame alignment is disabled. The
XRT84L38 framer will not search for CAS Multi-frame alignment
and thus will not declare CAS Multi-frame synchronization. No
Receive CAS Multi-frame Synchronization (RxCRCMsync_n)
pulse will be generated by the framer.
When these bits are set to 01:
Searching of CAS Multi-frame alignment is enabled. The
XRT84L38 will search for and declare CAS Multi-frame synchro-
nization using Algorithm 1.
When these bits are set to 10:
Searching of CAS Multi-frame alignment is enabled. The
XRT84L38 will search for and declare CAS Multi-frame synchro-
nization using Algorithm 2 (G.732).
When these bits are set to 11:
Searching of CAS Multi-frame alignment is disabled. The
XRT84L38 framer will not search for CAS Multi-frame alignment
and thus will not declare CAS Multi-frame synchronization. No
Receive CAS Multi-frame Synchronization (RxCRCMsync_n)
pulse will be generated by the framer.
85
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3-2
CRC-4 Selection bit
R/W
CRC-4 Selection:
These Read/Write bit fields allow the user to enable searching of
CRC-4 Multi-frame alignment and determine what criteria are
used for locking the CRC-4 Multi-frame alignment pattern.
When these bit s are set to 00:
Searching of CRC-4 Multi-frame alignment is disabled. The
XRT84L38 framer will not search for CRC-4 Multi-frame align-
ment and thus will not declare CRC-4 Multi-frame synchroniza-
tion. No Receive CRC-4 Multi-frame Synchronization
(RxCRCMsync_n) pulse will be generated by the framer.
When these bit s are set to 01:
Searching of CRC-4 Multi-frame alignment is enabled. The
XRT84L38 will search for and declare CRC-4 Multi-frame syn-
chronization if:
At least one valid CRC-4 Multi-frame alignment signal is
observed within 8 ms.
When these bit s are set to 10:
Searching of CRC-4 Multi-frame alignment is enabled. The
XRT84L38 will search for and declare CRC-4 Multi-frame syn-
chronization if:
At least two valid CRC-4 Multi-frame alignment signals are
observed within 8 ms.
The time separating two CRC-4 Multi-frame alignment signals is
multiple of 2 ms.
When these bit s are set to 11:
Searching of CRC-4 Multi-frame alignment is enabled. The
XRT84L38 will search for and declare CRC-4 Multi-frame syn-
chronization if:
At least three valid CRC-4 Multi-frame alignment signals are
observed within 8 ms.
The time separating two CRC-4 Multi-frame alignment signals is
multiple of 2 ms.
1
FAS Alignment Frame
R/W
FAS Alignment Frame Check Sequence Enable:
Check Sequence Enable
This READ/WRITE bit-field enables frame check sequence in
FAS alignment process. The frame check sequence consists of
verifying correct frame alignment for an additional two frames.
When this bit is set to 0:
The frame check sequence is disabled in FAS alignment pro-
cess.
When this bit is set to 1:
The frame check sequence is enabled in FAS alignment process.
86
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
0
FAS Selection bit
R/W
FAS Selection:
This Read/Write bit field allows the user to determine which
algorithm is used for searching FAS frame alignment pattern.
When an FAS alignment pattern is found and locked, the
XRT84L38 will generate Receive Synchronization (RxSync_n)
pulse.
When this bit is set to 0:
Algorithm 1 is selected for searching FAS frame alignment pat-
tern.
When this bit is set to 1:
Algorithm 2 is selected for searching FAS frame alignment pat-
tern.
Alarm Generation Register (AGR) - T1 Mode (Indirect Address = 0xn0H, 0x08H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Reserved LossofFrame Yellow Alarm Yellow Alarm
Alarm
Indication
Signal
Alarm
Indication
Signal
Alarm
Indication
Signal
Alarm
Indication
Signal
Declaration
Enable
Generation
Select Bit 1
Generation
Select Bit 0
Generation
Select Bit 1
Generation
Select Bit 0
Detection
Select Bit 1
Detection
Select Bit 0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
6
Reserved
X
Loss of Frame
R/W
Loss of Frame Declaration Enable:
Declaration Enable
This READ/WRITE bit-field permits the framer to declare Red
Alarm in case of Loss of Frame Alignment (LOF).
When receiver module of the framer detects Loss of Frame
Alignment in the incoming data stream, it will generate a Red
Alarm. The framer will also generate an RxLOFs interrupt to
notify the microprocessor that an LOF condition is occurred. A
Yellow Alarm is then returned to the remote transmitter to report
that the local receiver detects LOF.
When this bit is set to zero:
Red Alarm declaration is disabled.
When this bit is set to one:
Red Alarm declaration is enabled.
87
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
5-4
Yellow Alarm Generation
Select
R/W
Yellow Alarm Generation Select:
These READ/WRITE bit-fields activate and de-activate transmis-
sion of Yellow Alarm by the framer. In various framing formats,
the pattern and duration of Yellow Alarm various. The following
text describes how the framer transmits Yellow Alarm by setting
these bit-fields to different values.
SF Mode:
When these bits are set to 00:
Transmission of Yellow Alarm is disabled.
When these bits are set to 01:
The framer transmits Yellow Alarm by converting the second
MSB of all outgoing twenty-four DS0 channel into zero.
When these bits are set to 10:
The framer transmits Yellow Alarm by sending the Super-frame
Alignment Bit (Fs) of Frame 12 as one.
When these bits are set to 11:
The framer transmits Yellow Alarm by converting the second
MSB of all outgoing twenty-four DS0 channel into zero.N Mode:
When these bits are set to 00:
Transmission of Yellow Alarm is disabled.
When these bits are set to 01, 10 or 11:
The framer transmits Yellow Alarm by converting the second
MSB of all outgoing twenty-four DS0 channel into zero.
ESF Mode:
When the framer is in ESF mode, it transmits Yellow Alarm pat-
tern of eight ones followed by eight zeros
(1111_1111_0000_0000) through the 4Kbit/s data link bits.
When the Yellow Alarm Generation Select bits are set to 00:
Transmission of Yellow Alarm is disabled.
When these bits are set to 01:
The following scenario will happen:
1. If Bit 0 of Yellow Alarm Generation Select forms a pulse
width shorter or equal to the time required to transmit 255
patterns on the 4Kbit/s data link, the alarm is transmitted for
255 patterns.
2. If Bit 0 of Yellow Alarm Generation Select forms a pulse
width longer than the time required to transmit 255 patterns
on the 4Kbit/s data link, the alarm continues until Bit 0 goes
LOW.
3. A second pulse on Bit 0 of Yellow Alarm Generation Select
during an alarm transmission resets the pattern counter.
The framer will send another 255 patterns of the Yellow
Alarm.
88
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
When these bits are set to 10:
Bit 1 of the Yellow Alarm Generation Select forms a pulse that
controls the duration of Yellow Alarm transmission. The alarm
continues until Bit 1 goes LOW.
When these bits are set to 11:
The following scenario will happen:
1. If Bit 0 of Yellow Alarm Generation Select forms a pulse
width shorter or equal to the time required to transmit 255
patterns on the 4Kbit/s data link, the alarm is transmitted for
255 patterns.
2. If Bit 0 of Yellow Alarm Generation Select forms a pulse
width longer than the time required to transmit 255 patterns
on the 4Kbit/s data link, the alarm continues until Bit 0 goes
LOW.
3. A second pulse on Bit 0 of Yellow Alarm Generation Select
during an alarm transmission resets the pattern counter.
The framer will send another 255 patterns of the Yellow
Alarm.
T1DM Mode:
When these bits are set to 00:
Transmission of Yellow Alarm is disabled.
When these bits are set to 01, 10 or 11:
The framer transmits Yellow Alarm by setting the Yellow Alarm bit
(Y-bit) to zero.
3-2
Alarm Indication Signal
Generation Select
R/W
Alarm Indication Signal Generation Select:
These READ/WRITE bit-fields activate and de-activate transmis-
sion of Alarm Indication Signal (AIS). There are two types of
Alarm Indication Signals - framed and unframed. A unframed
AIS signal is all-ones including all the framing bits. A framed AIS
signal is all-ones except the framing bits.
When these bits are set to 00:
The framer will disable AIS alarm generation.
When these bits are set to 01:
The framer will transmit unframed AIS alarm.
When these bits are set to 10:
The framer will disable AIS alarm generation.
When these bits are set to 11:
The framer will transmit framed AIS Alarm.
1-0
Alarm Indication Signal
Detection Select
R/W
Alarm Indication Signal Detection Select:
These READ/WRITE bit-fields activate and de-activate Alarm
Indication Signal Detection of the framer.
When these bits are set to 00:
The framer disables detection of AIS Alarm.
When these bits are set to 01:
The framer enables detection of unframed AIS Alarm.
When these bits are set to 10:
The framer disables detection of AIS Alarm.
When these bits are set to 11:
The framer enables detection of framed AIS Alarm.
89
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
Alarm Generation Register (AGR) - E1 Mode (Indirect Address = 0xn0H, 0x08H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
AUXP Enable LossofFrame Yellow Alarm Yellow Alarm
Alarm
Indication
Signal
Alarm
Indication
Signal
Alarm
Indication
Signal
Alarm
Indication
Signal
Declaration
Enable
Generation
Select Bit 1
Generation
Select Bit 0
Generation
Select Bit 1
Generation
Select Bit 0
Detection
Select Bit 1
Detection
Select Bit 0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
AUXP Enable
R/W
AUXP Enable:
AUXP is an unframed 1010 pattern.
When this bit is set to zero:
AUXP generation is disabled.
When this bit is set to one:
AUXP generation is enabled.
6
Loss of Frame
Declaration Enable
R/W
Loss of Frame Declaration Enable:
This READ/WRITE bit-field permits the framer to declare Red
Alarm in case of Loss of Frame Alignment (LOF).
When receiver module of the framer detects Loss of Frame
Alignment in the incoming data stream, it will generate a Red
Alarm. The framer will also generate an RxLOFs interrupt to
notify the microprocessor that an LOF condition is occurred. A
Yellow Alarm is then returned to the remote transmitter to report
that the local receiver detects LOF.
When this bit is set to zero:
Red Alarm declaration is disabled.
When this bit is set to one:
Red Alarm declaration is enabled.
90
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
5-4
Yellow Alarm Generation
Select
R/W
Yellow Alarm Generation Select:
These READ/WRITE bit-fields allows the user to choose how the
XRT84L38 would generate Yellow Alarm and CAS Multi-frame
Yellow Alarm.
When these bits are set to 00:
Transmission of Yellow Alarm and CAS Multi-frame Yellow Alarm
is disabled.
When these bits are set to 01:
The Yellow Alarm bit is transmitted by echoing the received FAS
alignment pattern. If the correct FAS alignment is received, the
Yellow Alarm bit is set to zero. If the FAS alignment pattern is
missing or corrupted, the Yellow Alarm bit is set to one.
The CAS Multi-frame Yellow Alarm bit is transmitted by echoing
the received CAS Multi-frame alignment pattern (the four zeros
pattern). If the correct CAS Multi-frame alignment is received,
the CAS Multi-frame Yellow Alarm bit is set to zero. If the CAS
Multi-frame alignment pattern is missing or corrupted, the CAS
Multi-frame Yellow Alarm bit is set to one.
When these bits are set to 10:
The Yellow Alarm and CAS Multi-frame Yellow Alarms are trans-
mitted as zero.
When these bits are set to 11:
The Yellow Alarm and CAS Multi-frame Yellow Alarms are trans-
mitted as one.
3-2
Alarm Indication Signal
Generation Select
R/W
Alarm Indication Signal Generation Select:
These READ/WRITE bit-fields activate and de-activate transmis-
sion of Alarm Indication Signal (AIS). There are two types of
Alarm Indication Signals - framed and unframed. A unframed
AIS signal is all-ones including all the framing bits. A framed AIS
signal is all-ones except the framing bits.
When these bits are set to 00:
The framer will disable AIS alarm generation.
When these bits are set to 01:
The framer will transmit unframed AIS alarm.
When these bits are set to 10:
The framer will generate AIS16. Only time slot 16 is carrying the
all ones pattern. The other time slots still carry framing and PCM
data.
When these bits are set to 11:
The framer will transmit framed AIS Alarm.
91
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1-0
Alarm Indication Signal
Detection Select
R/W
Alarm Indication Signal Detection Select:
These READ/WRITE bit-fields activate and de-activate Alarm
Indication Signal Detection of the framer.
When these bits are set to 00:
The framer disables detection of AIS Alarm.
When these bits are set to 01:
The framer enables detection of unframed AIS Alarm.
When these bits are set to 10:
The framer enables detection of AIS16 Alarm.
When these bits are set to 11:
The framer enables detection of framed AIS Alarm.
Synchronization Mux Register (SMR) - T1 Mode (Indirect Address = 0xn0H, 0x09H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Reserved
Transmit
Multi-frame Super-frame
Alignment
Transmit
Synchroniza-
tion Signal
Direction
Reserved
Reserved
CRC-6
Source
Framing Bit
Source
Synchroniza-
tion
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
6
Reserved
R/W
Transmit Multi-frame
Alignment
R/W
Transmit Multi-frame Alignment:
This READ/WRITE bit-field forces the framer to align the Trans-
mit Multi-frame boundary with the back-plane Multi-frame Syn-
chronization Pulse.
When this bit is set to zero:
The Transmit Multi-frame boundary is not aligned with the back-
plane Multi-frame Synchronization Pulse.
When this bit is set to one:
The Transmit Multi-frame boundary is forced to align with the
back-plane Multi-frame Synchronization Pulse.
92
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
5
Transmit Super-frame
Synchronization
R/W
Transmit Super-frame Synchronization:
This READ/WRITE bit-field determines the transmit synchroni-
zation input signal (TxSync) being either the Frame Synchroniza-
tion signal or the Multi-frame Synchronization signal.
When this bit is set to zero:
The transmit synchronization input signal (TxSync) is the Frame
Synchronization signal that indicates the frame boundary. In
1.544Mbit/s basic mode, the Transmit Multi-frame Synchroniza-
tion input signal (TxMSync) indicates the Multi-frame boundary.
In other back-plane modes, the TxMSync input is an input trans-
mit clock.
When this bit is set to one:
The transmit synchronization input signal (TxSync) is the Trans-
mit Multi-frame Synchronization signal indicating the multi-frame
boundary.
4
Synchronization Signal
Direction
R/W
Synchronization Signal Direction:
This READ/WRITE bit-field determines the direction of transmit
synchronization signal (TxSync_n) and the Transmit Multi-frame
Synchronization signal (TxMSync_n). In H.100 interface mode,
this READ/WRITE bit-field determines the location of the trans-
mit synchronization pulse.
When this bit is set to zero:
The transmit synchronization signal is input if the Transmit Line
Clock Source Select bits of Clock Select Register (CSR) equal to
one. If the Transmit Line Clock Source Select bits of Clock Select
Register (CSR) is not equal to one, the transmit synchronization
signal is output.
In H.100 interface mode, the transmit synchronization pulse
occurs at the last and the first clock cycles of each frame.
When this bit is set to one:
The transmit synchronization signal is output if the Transmit Line
Clock Source Select bits of Clock Select Register (CSR) equal to
one. If the Transmit Line Clock Source Select bits of Clock Select
Register (CSR) is not equal to one, the transmit synchronization
signal is input.
In H.100 interface mode, the transmit synchronization pulse
occurs at the first two clock cycles of each frame.
3-2
1
Reserved
R/W
R/W
CRC-6 Source
CRC-6 Source:
This READ/WRITE bit-field permits the user to determine where
the CRC-6 bits should be inserted.
When this bit is zero:
The CRC-6 bits are generated and inserted by the framer inter-
nally.
When this bit is one:
If the framer is operating in normal 1.544Mbit/s mode, the CRC-6
bits are passed through from the Transmit Serial Data input
(TxSer_n).
93
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
0
Framing Bit Source
R/W
Framing Bit Source:
This READ/WRITE bit-field permits the user to determine where
the framing alignment bits should be inserted.
When this bit is zero:
The framing alignment bits are generated and inserted by the
framer internally.
When this bit is one:
If the framer is operating in normal 1.544Mbit/s mode, the fram-
ing alignment bits are passed through from the Transmit Serial
Data input (TxSer_n).
Synchronization Mux Register (SMR) - E1 Mode (Indirect Address = 0xn0H, 0x09H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
E bit Source E bit Source
Reserved
Synchroniza- Transmit Data Transmit Data
CRC-4
Source
Framing Bit
Source
Select bit 1
Select bit 0
tion Signal
Direction
Link Source Link Source
Select bit 1
Select bit 0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-6
E bit Source Select
R/W
E Source Select:
These READ/WRITE bit-fields permits the user to determine
where the E bits should be inserted and what the E bits should
be.
When these bits are 00:
The E bits are generated and inserted by the framer internally.
When these bits are 01:
The E bits are forced to be "0" and are inserted by the framer
internally. When these bits are 10:The E bits are forced to be "1"
and are inserted by the framer internally.
When these bits are 11:
Source of the E bits is HDLC controller of the framer. The E bits
are used to carry data link messages.
5
Reserved
94
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
4
Synchronization Signal
Direction
R/W
Synchronization Signal Direction:
This READ/WRITE bit-field determines the direction of transmit
synchronization signal (TxSync_n) and the Transmit Multi-frame
Synchronization signal (TxMSync_n). In H.100 interface mode,
this READ/WRITE bit-field determines the location of the trans-
mit synchronization pulse.
When this bit is set to zero:
The transmit synchronization signal is input if the Transmit Line
Clock Source Select bits of Clock Select Register (CSR) equal to
one. That is, if the Transmit Serial Input Clock (TxSerClk_n) is
configured as the source of the Transmit Line Clock.
If the Transmit Line Clock Source Select bits of Clock Select
Register (CSR) is not equal to one, the transmit synchronization
signal is output.
In H.100 interface mode, the transmit synchronization pulse
occurs at the last and the first clock cycles of each frame.
When this bit is set to one:
The transmit synchronization signal is output if the Transmit Line
Clock Source Select bits of Clock Select Register (CSR) equal to
one. That is, if the Transmit Serial Input Clock (TxSerClk_n) is
configured as the source of the Transmit Line Clock.
If the Transmit Line Clock Source Select bits of Clock Select
Register (CSR) is not equal to one, the transmit synchronization
signal is input.
In H.100 interface mode, the transmit synchronization pulse
occurs at the first two clock cycles of each frame.
3-2
Transmit Data Link
Source Select [1:0]
R/W
Transmit Data Link Source Select [1:0]:
These READ/WRITE bit-fields permits the user to determine
where the data link bits should be inserted from.
When these bits are set to 00:
The data link bits are inserted into the framer through the Trans-
mit Serial Data input Interface via the TxSer_n pins.
When these bits are set to 01:
The data link bits are inserted into the framer through the Trans-
mit HDLC Controller.
When these bits are set to 10:
The data link bits are inserted into the framer through the Trans-
mit Overhead Input Interface via the TxOH_n pins.
When these bits are set to 11:
The data link bits are inserted into the framer through the Trans-
mit Serial Data input Interface via the TxSer_n pins.
95
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1
CRC-4 Source Select
R/W
CRC-4 Source Select:
This READ/WRITE bit-field permits the user to determine where
the CRC-4 bits should be inserted.
When this bit is set to 0:
The CRC-4 bits are generated and inserted by the framer inter-
nally.
When this bit is set to 1:
If the framer is operating in normal 2.048Mbit/s mode, the CRC-4
bits are generated by external equipment and passed through
from the Transmit Serial Data Input Interface block via the
TxSer_n pin.
0
Framing Bit Source
R/W
Framing Bit Source:
This READ/WRITE bit-field permits the user to determine where
the framing alignment bits should be inserted.
When this bit is set to 0:
The framing alignment bits are generated and inserted by the
framer internally.
When this bit is set to 1:
If the framer is operating in normal 2.048Mbit/s mode, the fram-
ing alignment bits are passed through from the Transmit Serial
Data Input Interface block via the TxSer_n pin.
Transmit Signaling And Data Link Select Register (TSDLSR)- T1 Mode (Indirect Address = 0xn0H,
0x0AH)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Reserved
Reserved
Transmit Data Transmit Data D/E Timeslot D/E Timeslot
Data Link
Data Link
Link
Link
SourceSelect SourceSelect SourceSelect SourceSelect
Bandwidth
Select Bit 1
Bandwidth
Select Bit 0
Bit 1
Bit 0
Bit 1
Bit 0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-6
Reserved
R/W
96
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
5-4
Transmit Data Link Band-
width Select
R/W
Transmit Data Link Bandwidth Select:
These READ/WRITE bit-fields determined the bandwidth of
Facility Data Link channel of the framer when operating in ESF
mode.
When these bits are set to 00:
The Facility Data Link is a 4KHz channel. All available FDL bits
(first bit of every other frame) are used as data link bits.
When these bits are set to 01:
The Facility Data Link is a 2KHz channel. Only the odd FDL bits
(first bit of frame 1, 5, 9…) are used as data link bits.
When these bits are set to 10:
The Facility Data Link is a 2KHz channel. Only the even FDL bits
(first bit of frame 3, 7, 11…) are used as data link bits.
3-2
D/E Timeslot Source
Select
R/W
D/E Timeslot Source Select:
These READ/WRITE bit-fields permit the user to select data
source of D or E channel (D/E Timeslot) for the ISDN Primary
Rate Interface, if LAPDSEL[1:0] bits in TCCR is 10.
NOTE: The LAPD Select (LAPDSEL) bits of the Transmit Chan-
nel Control Register (TCCR) determine which one of the three
LAPD channel are used for D/E timeslot. If LAPDSEL[1:0] = 10,
the D/E Timeslot Source Select bits will determine the data
source for D/E time slot.
The ISDN Primary Rate Interface (ISDN I.431) can carry B chan-
nel, D channel, E channel and H channel. B channel has a bit
rate of 64Kbit/s and is equivalent to a DS0 channel in T1 used for
payload transmission. D channel has a bit rate of 64Kbit/s and is
used primarily for signaling transmission. E channel has a bit
rate of 64Kbit/s and is used for signaling for circuit switching. It is
used only with multiple-access configuration. H channel has bit
rates of 384Kbit/s, 1536Kbit/s for T1 primary rate, and 1920Kbit/
s for E1 primary rate.
The signaling information presented on D or E channels are pro-
vided by several sources. The user can provide the signaling
information through the Transmit Serial Data via the TxSer_n
pins. The user can also supply the signaling data by writing to
the LAPD controller using microprocessor access. Finally, the
user can provide the data through Fraction T1 input via the
TxFrT1_n pins.
When these bits are set to 00:
The D or E channel data are inserted from the Transmit Serial
Data input.
When these bits are set to 01:
The D or E channel data are inserted from the LAPD controllers.
The user can read or write to the LAPD controller using micro-
processor access.
When these bits are set to 10:
The D or E channel data are inserted from the Transmit Serial
Data input.
When these bits are set to 11:
The D or E channel data are inserted from the Fractional T1
input.
97
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1-0
Data Link Source Select
R/W
Data Link Source Select:
These READ/WRITE bit-fields permit the user to select data
source of the Facility Data Link bits.
The user can insert Facility Data Link bits into the framer through
the LAPD controller or SLCâ96 buffer. Both LAPD controller and
SLCâ96 buffer can be programmed through microprocessor
access. The user can also insert Facility Data Link bits through
Transmit Serial Data directly via TxSer_n pins. Overhead inter-
face of the framer can also be used to input Facility Data Link
bits. Finally, the user can force these data link bits to one.
When these bits are set to 00:
The Facility Data Link bits are inserted into the framer through
either the LAPD controller or the SLCâ96 buffer.
When these bits are set to 01:
The Facility Data Link bits are inserted into the framer through
the Transmit Serial Data input.
When these bits are set to 10:
The Facility Data Link bits are inserted into the framer through
the Overhead Interface via the TxOH_n pins.
When these bits are set to 11:
The Facility Data Link bits are forced to one by the framer.
Transmit Signaling And Data Link Select Register (TSDLSR)- E1 Mode (Indirect Address = 0xn0H,
0x0AH)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Transmit Sa8 Transmit Sa7 Transmit Sa6 Transmit Sa5 Transmit Sa4
Data Link
Data Link
Data Link
Data Link
Select
Data Link
Select
Data Link
Select
Data Link
Select
Data Link
Select
SourceSelect SourceSelect SourceSelect
Bit 2
R/W
0
Bit 1
R/W
0
Bit 0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Transmit Sa8 Data Link
Select
R/W
R/W
Transmit Sa8 Data Link Select:
When this bit is set to 0:
Source of the Sa8 Nation bit is not from the data link interface.
When this bit is set to 1:
Source the Sa8 National bit from the data link interface.
6
Transmit Sa7 Data Link
Select
Transmit Sa7 Data Link Select:
When this bit is set to 0:
Source of the Sa7 Nation bit is not from the data link interface.
When this bit is set to 1:
Source the Sa7 National bit from the data link interface.
98
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
5
Transmit Sa6 Data Link
Select
R/W
Transmit Sa6 Data Link Select:
When this bit is set to 0:
Source of the Sa6 Nation bit is not from the data link interface.
When this bit is set to 1:
Source the Sa6 National bit from the data link interface.
4
3
Transmit Sa5 Data Link
Select
R/W
R/W
R/W
Transmit Sa5 Data Link Select:
When this bit is set to 0:
Source of the Sa5 Nation bit is not from the data link interface.
When this bit is set to 1:
Source the Sa5 National bit from the data link interface.
Transmit Sa4 Data Link
Select
Transmit Sa4 Data Link Select:
When this bit is set to 0:
Source of the Sa4 Nation bit is not from the data link interface.
When this bit is set to 1:
Source the Sa4 National bit from the data link interface.
2-0
Transmit Signaling and
Data Link Select
Transmit Signaling and Data Link Select:
These READ/WRITE bit-fields permit the user to select data
source of the D or E channels, the National bits and the time slot
16 octets.
National Bits
When these bits are set to 000:
The data link interface is source of the Sa4 through Sa8 Nation
bits, if the corresponding Transmit Sa Data Link Select bit(s) (Bit
3 to Bit 7 of the Transmit Signaling and Data Link Select Regis-
ter) are set to 1.
When these bits are set to 001:
The data link interface is source of the Sa4 through Sa8 Nation
bits, if the corresponding Transmit Sa Data Link Select bit(s) (Bit
3 to Bit 7 of the Transmit Signaling and Data Link Select Regis-
ter) are set to 1.
When these bits are set to 010:
The Sa4 through Sa8 Nation bits are forced to 1.
When these bits are set to 011:
The Sa4 through Sa8 Nation bits are forced to 1.
When these bits are set to 100:
The data link interface is source of the Sa4 through Sa8 Nation
bits, if the corresponding Transmit Sa Data Link Select bit(s) (Bit
3 to Bit 7 of the Transmit Signaling and Data Link Select Regis-
ter) are set to 1.
When these bits are set to 101:
Reserved.
When these bits are set to 110:
Reserved.
When these bits are set to 111:
Reserved.
99
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
Timeslot 16 Octet
When these bits are set to 000:
Timeslot 16 octet is taken directly from the Transmit Signaling
Control Register (TSCR).
When these bits are set to 001:
Timeslot 16 octet is taken directly from the Transmit Overhead
Input Interface through the TxOH_n pin or per-channel signaling
registers determined by Transmit Signaling Source bit of the
Transmit Signaling Control Register (TSCR)of Timeslot 16.
When these bits are set to 010:
Timeslot 16 octet is taken directly from the Transmit Signaling
Input Interface through the TxSig_n pin.
When these bits are set to 011:
Timeslot 16 octet is taken directly from the Transmit Overhead
Input Interface through the TxOH_n pin or per-channel signaling
registers determined by Transmit Signaling Source bit of the
Transmit Signaling Control Register (TSCR) of Timeslot 16.
When these bits are set to 100:
Timeslot 16 octet is taken directly from the Transmit Signaling
Control Register (TSCR).
When these bits are set to 101:
Reserved.
When these bits are set to 110:
Reserved.
When these bits are set to 111:
Reserved.
D/E Time Slot
When these bits are set to 000:
D or E time slot data are taken through the Transmit Fractional
Data Input Interface (TxFrTD_n pin).
When these bits are set to 001:
D or E time slot data are taken through the Transmit Fractional
Data Input Interface (TxFrTD_n pin).
When these bits are set to 010:
D or E time slot data are taken through the Transmit Fractional
Data Input Interface (TxFrTD_n pin).
When these bits are set to 011:
D or E time slot data are taken through the Transmit Fractional
Data Input Interface (TxFrTD_n pin).
When these bits are set to 100:
D or E time slot data are taken through the Transmit Serial Sig-
naling Input Interface (TxSig_n pin).
When these bits are set to 101:
Reserved.
When these bits are set to 110:
Reserved.
When these bits are set to 111:
Reserved.
The following table summaries sources of National bits, Timeslot
16 octet and D or E time slots.T
100
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
National Bits
(Sa4-Sa8)
Timeslot 16
Octet
D or E
Timeslot
TxSIGDL [2:0]
000
001
Data Link
TSCR
TxFrTD_n
TxFrTD_n
TxSig_n or
TxOH
Data Link
TxSig_n or
TxOH
TxSig_n or
010
011
None
None
TxFrTD_n
TxFrTD_n
TxOH
100
101
110
111
Data Link
Reserved
Reserved
Reserved
TSCR
TxSig_n
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Framing Control Register (FCR) - T1 Mode (Indirect Address = 0xn0H, 0x0BH)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Force
Synchroniza- Framing Error Framing Error Framing Error Framing Bit
Framing Bit
Range
Framing Bit
Range
Re-synchroni- tion with CRC
Tolerance
Bit 2
Tolerance
Bit 1
Tolerance
Bit 0
Range
Bit 2
zation
R/W
0
Verification
Bit 1
Bit 0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Force Re-synchronization
R/W
Force Re-synchronization:
This READ/WRITE bit-field forces the re-synchronization pro-
cess of the framer.
When this bit is set to one:
The framer started the re-synchronization process. After syn-
chronization is achieved, the bit is automatically cleared.
6
Synchronization with
CRC Verification
R/W
Synchronization with CRC Verification:
This READ/WRITE bit-field forces the framer to obtain synchro-
nization with CRC verification.
When this bit is set to zero:
The framer obtains synchronization without CRC match test.
When this bit is set to one:
CRC match test is included as part of the synchronization pro-
cess.
101
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
5-3
Framing Error Tolerance
R/W
Framing Error Tolerance:
These READ/WRITE bit-fields together with the Range bits form
the criteria for Loss of Frame Alignment.
In SF mode, a Loss of Frame Alignment is typically declared if
two out of four Terminal Framing bits (Ft) or Signaling Framing
bits (Fs) are incorrect. Therefore, the Tolerance bits are normally
set to two and the Range bits are normally set to four.
In ESF mode, a Loss of Frame Alignment is typically declared if
two out of four Framing Pattern Sequence bits (FPS) are incor-
rect. Therefore, the Tolerance bits are normally set to two and
the Range bits are normally set to four.
In N mode, a Loss of Frame Alignment is typically declared if two
out of four Terminal Framing bits (Ft) are incorrect. Therefore, the
Tolerance bits are normally set to two and the Range bits are
normally set to four.
In SLC 96 mode, a Loss of Frame Alignment is typically
declared if two out of four Terminal Framing bits (Ft) are incor-
rect. Therefore, the Tolerance bits are normally set to two and
the Range bits are normally set to four.
In T1DM mode, a Loss of Frame Alignment is typically declared
if TOLR out of RANG bits are incorrect. Therefore, the Tolerance
bits are normally set to two and the Range bits are normally set
to four.
2-0
Framing Bit Range
R/W
Framing Bit Range:
These READ/WRITE bit-fields together with the Tolerance bits
form the criteria for Loss of Frame Alignment.
In SF mode, a Loss of Frame Alignment is typically declared if
two out of four Terminal Framing bits (Ft) or Signaling Framing
bits (Fs) are incorrect. Therefore, the Tolerance bits are normally
set to two and the Range bits are normally set to four.
In ESF mode, a Loss of Frame Alignment is typically declared if
two out of four Framing Pattern Sequence bits (FPS) are incor-
rect. Therefore, the Tolerance bits are normally set to two and
the Range bits are normally set to four.
In N mode, a Loss of Frame Alignment is typically declared if two
out of four Terminal Framing bits (Ft) are incorrect. Therefore, the
Tolerance bits are normally set to two and the Range bits are
normally set to four.
In SLC 96 mode, a Loss of Frame Alignment is typically
declared if two out of four Terminal Framing bits (Ft) are incor-
rect. Therefore, the Tolerance bits are normally set to two and
the Range bits are normally set to four.
In T1DM mode, a Loss of Frame Alignment is typically declared
if TOLR out of RANG bits are incorrect. Therefore, the Tolerance
bits are normally set to two and the Range bits are normally set
to four.
102
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
Framing Control Register (FCR) - E1 Mode (Indirect Address = 0xn0H, 0x0BH)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Force Re-syn- CAS Re-syn- CAS Re-syn- CRC Re-syn- CRC Re-syn- FAS Re-syn- FAS Re-syn- FAS Re-syn-
chronization chronization chronization chronization chronization chronization chronization chronization
Criteria Bit 1 Criteria Bit 0 Criteria Bit 1 Criteria Bit 0 Criteria Bit 2 Criteria Bit 1 Criteria Bit 0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Force Re-synchronization
R/W
Force Re-synchronization:
This READ/WRITE bit-field forces the re-synchronization pro-
cess of the framer.
When this bit is set to one:
The framer started the re-synchronization process. After syn-
chronization is achieved, the bit is automatically cleared.
6 - 5
CAS Re-synchronization
Criteria
R/W
CAS Re-synchronization Criteria:
These READ/WRITE bit-field determine the criteria of Loss of
CAS Multi-frame Synchronization.
When these bits are set to 00:
Two consecutive CAS Multi-frame Alignment Signal errors in the
incoming frame will cause the declaration of Loss of CAS Multi-
frame Synchronization.
When these bits are set to 01:
Three consecutive CAS Multi-frame Alignment Signal errors in
the incoming frame will cause the declaration of Loss of CAS
Multi-frame Synchronization.
When these bits are set to 10:
Four consecutive CAS Multi-frame Alignment Signal errors in the
incoming frame will cause the declaration of Loss of CAS Multi-
frame Synchronization.
When these bits are set to 11:
Eight consecutive CAS Multi-frame Alignment Signal errors in
the incoming frame will cause the declaration of Loss of CAS
Multi-frame Synchronization.
103
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
4 - 3
CRC Re-synchronization
Criteria
R/W
CRC Re-synchronization Criteria:
These READ/WRITE bit-field determine the criteria of Loss of
CRC Multi-frame Synchronization.
When these bits are set to 00:
If four consecutive CRC Multi-frame Alignment Signal errors in
the incoming frames are detected, the framer will declare Loss of
CRC Multi-frame Synchronization.
When these bits are set to 01:
If two consecutive CRC Multi-frame Alignment Signal errors in
the incoming frames are detected, the framer will declare Loss of
CRC Multi-frame Synchronization.
When these bits are set to 10:
If eight consecutive CRC Multi-frame Alignment Signal errors in
the incoming frames are detected, the framer will declare Loss of
CRC Multi-frame Synchronization.
When these bits are set to 11:
If 915 or more consecutive CRC Multi-frame Alignment Signal
errors in the incoming frames are detected in one second, the
framer will declare Loss of CRC Multi-frame Synchronization.
104
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
2 - 0
FAS Re-synchronization
Criteria
R/W
FAS Re-synchronization Criteria:
These READ/WRITE bit-field determine the criteria of Loss of
FAS Multi-frame Synchronization.
When these bits are set to 000:
It is an illegal entry. The user should not set these bits to 000.
When these bits are set to 001:
If one FAS Multi-frame Alignment Signal error in the incoming
frame is detected, the framer will declare Loss of FAS Multi-
frame Synchronization.
When these bits are set to 010:
If two consecutive FAS Multi-frame Alignment Signal errors in
the incoming frames are detected, the framer will declare Loss of
FAS Multi-frame Synchronization.
When these bits are set to 011:
If three consecutive FAS Multi-frame Alignment Signal errors in
the incoming frames are detected, the framer will declare Loss of
FAS Multi-frame Synchronization.
When these bits are set to 100:
If four consecutive FAS Multi-frame Alignment Signal errors in
the incoming frames are detected, the framer will declare Loss of
FAS Multi-frame Synchronization.
When these bits are set to 101:
If five consecutive FAS Multi-frame Alignment Signal errors in the
incoming frames are detected, the framer will declare Loss of
FAS Multi-frame Synchronization.
When these bits are set to 110:
If six consecutive FAS Multi-frame Alignment Signal errors in the
incoming frames are detected, the framer will declare Loss of
FAS Multi-frame Synchronization.
When these bits are set to 111:
If seven consecutive FAS Multi-frame Alignment Signal errors in
the incoming frames are detected, the framer will declare Loss of
FAS Multi-frame Synchronization.
Receive Data Link Select Register (RDLSR) - T1 Mode (Indirect Address = 0xn0H, 0x0CH)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Reserved
Receive Data
Link Band-
width Select
Bits [1:0]
D/E Timeslot Destination
Select Bits [1:0]
Data Link Destination Select
Bits [1:0]
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
105
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
BIT NUMBER
BIT NAME
BIT TYPE
X
BIT DESCRIPTION
7-6
5-4
Reserved
Receive Data Link Band-
width Select
R/W
Receive Data Link Bandwidth Select:
These READ/WRITE bit-fields determined the bandwidth of
Facility Data Link channel of the framer when operating in ESF
mode.
When these bits are set to 00:
The Facility Data Link is a 4KHz channel. All available FDL bits
(first bit of every other frame) are used as data link bits.
When these bits are set to 01:
The Facility Data Link is a 2KHz channel. Only the odd FDL bits
(first bit of frame 1, 5, 9…) are used as data link bits.
When these bits are set to 10:
The Facility Data Link is a 2KHz channel. Only the even FDL bits
(first bit of frame 3, 7, 11…) are used as data link bits.
106
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3-2
D/E Timeslot Source
Select
R/W
D/E Timeslot Source Select:
These READ/WRITE bit-fields permit the user to select data
destination of D or E channel (D/E Timeslot) for the ISDN Pri-
mary Rate Interface.
The ISDN Primary Rate Interface (ISDN I.431) can carry B chan-
nel, D channel, E channel and H channel. B channel has a bit
rate of 64Kbit/s and is equivalent to a DS0 channel in T1 used for
payload transmission. D channel has a bit rate of 64Kbit/s and is
used primarily for signaling transmission. E channel has a bit
rate of 64Kbit/s and is used for signaling for circuit switching. It is
used only with multiple-access configuration. H channel has bit
rates of 384Kbit/s, 1536Kbit/s for T1 primary rate, and 1920Kbit/
s for E1 primary rate.
The signaling information presented on D or E channels can be
directed to several destinations. The user can send the signaling
information to the Receive Serial Data via the RxSer_n pins. The
user can also direct the signaling data to the Receive LAPD con-
troller. The signaling information can be extracted from the
Receive LAPD controller using microprocessor access. Finally,
the user can send the signaling information to Fraction T1 output
via the RxFrT1_n pins.
When these bits are set to 00:
The data link bits extracted form the D or E channel of incoming
DS1 frame are inserted into the Receive Serial Data Output
Interface via the RxSer_n pins.
When these bits are set to 01:
The data link bits extracted form the D or E channel of incoming
DS1 frame are inserted into the Receive HDLC Controller. The
user can read the Receive LAPD controller using microproces-
sor access.
When these bits are set to 10:
The data link bits extracted form the D or E channel of incoming
DS1 frame are inserted into the Receive Fractional T1 Output
Interface via the RxFrT1_n pins.
When these bits are set to 11:
The data link bits extracted form the D or E channel of incoming
DS1 frame are inserted into the Receive Serial Data Output
Interface via the RxSer_n pins.
107
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1-0
Data Link Source Select
R/W
Data Link Source Select:
These READ/WRITE bit-fields permit the user to select data
destination of the Facility Data Link bits.
The user can extract Facility Data Link bits of the incoming data
to the LAPD controller or SLCâ96 buffer. Both LAPD controller
and SLCâ96 buffer can be read through microprocessor access.
The user can also direct received Facility Data Link bits to
Receive Serial Data via RxSer_n pins. Overhead interface of the
framer can also be used to output Facility Data Link bits. Finally,
the user can force these data link bits to one.
When these bits are set to 00:
The Facility Data Link bits of the incoming data stream are
extracted to either the LAPD controller or the SLCâ96 buffer. The
Facility Data Link bits are also extracted into the Receive Serial
Data via the RxSer pin.
When these bits are set to 01:
The Facility Data Link bits of the incoming data stream are sent
to the Receive Serial Data output only.
When these bits are set to 10:
The Facility Data Link bits of the incoming data stream are
directed to the Overhead Interface via the RxOH_n pins. The
Facility Data Link bits are also extracted into the Receive Serial
Data via the RxSer pin.
When these bits are set to 11:
The Facility Data Link bits of the incoming data stream are forced
to one by the framer and are outputted to the Receive Serial
Data output.
Receive Data Link Select Register (RDLSR) - E1 Mode(Indirect Address = 0xn0H, 0x0CH)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Receive Sa8 Receive Sa8 Receive Sa8 Receive Sa8 Receive Sa8 Receive Signaling and Data Link Select Bits
Data Link
Select
Data Link
Select
Data Link
Select
Data Link
Select
Data Link
Select
[2:0]
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Receive Sa8 Data Link
Select
R/W
Receive Sa8 Data Link Select:
This READ/WRITE bit-field permit the user to select data desti-
nation of the Sa8 National bit.
When this bit is set to 0:
Destination of the Sa8 National bit is not the data link interface.
When this bit is set to 1:
Destination of the Sa8 National bit is the data link interface.
108
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
6
Receive Sa7 Data Link
Select
R/W
Receive Sa7 Data Link Select:
This READ/WRITE bit-field permit the user to select data desti-
nation of the Sa7 National bit.
When this bit is set to 0:
Destination of the Sa7 National bit is not the data link interface.
When this bit is set to 1:
Destination of the Sa7 National bit is the data link interface.
5
4
3
Receive Sa6 Data Link
Select
R/W
R/W
R/W
Receive Sa6 Data Link Select:
This READ/WRITE bit-field permit the user to select data desti-
nation of the Sa6 National bit.
When this bit is set to 0:
Destination of the Sa6 National bit is not the data link interface.
When this bit is set to 1:
Destination of the Sa6 National bit is the data link interface.
Receive Sa5 Data Link
Select
Receive Sa5 Data Link Select:
This READ/WRITE bit-field permit the user to select data desti-
nation of the Sa5 National bit.
When this bit is set to 0:
Destination of the Sa5 National bit is not the data link interface.
When this bit is set to 1:
Destination of the Sa5 National bit is the data link interface.
Receive Sa4 Data Link
Select
Receive Sa4 Data Link Select:
This READ/WRITE bit-field permit the user to select data desti-
nation of the Sa4 National bit.
When this bit is set to 0:
Destination of the Sa4 National bit is not the data link interface.
When this bit is set to 1:
Destination of the Sa4 National bit is the data link interface.
109
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
2-0
Receive Signaling and
Data Link Select
R/W
Receive Signaling and Data Link Select:
These READ/WRITE bit-fields permit the user to select data
destination of the National bits, the timeslot 16 octet as well as
the D or E time slot.
National Bits
When these bits are set to 000:
The data link interface is destination of the Sa4 through Sa8
Nation bits, if the corresponding Receive Sa Data Link Select
bit(s) (Bit 3 to Bit 7 of the Receive Signaling and Data Link Select
Register) are set to 1.
When these bits are set to 001:
The data link interface is destination of the Sa4 through Sa8
Nation bits, if the corresponding Receive Sa Data Link Select
bit(s) (Bit 3 to Bit 7 of the Receive Signaling and Data Link Select
Register) are set to 1.
When these bits are set to 010:
The Sa4 through Sa8 Nation bits are forced to 1.When these bits
are set to 011:The Sa4 through Sa8 Nation bits are forced to 1.
When these bits are set to 100:
The data link interface is destination of the Sa4 through Sa8
Nation bits, if the corresponding Receive Sa Data Link Select
bit(s) (Bit 3 to Bit 7 of the Receive Signaling and Data Link Select
Register) are set to 1.
When these bits are set to 101:
Reserved.
When these bits are set to 110:
Reserved.
When these bits are set to 111:
Reserved.
Timeslot 16 Octet
When these bits are set to 000:
Timeslot 16 octet is taken directly from the PCM data which in
term determines by the Receive Channel Control Register
(RCCR).
When these bits are set to 001:
Timeslot 16 octet is output by the Receive Overhead Input Inter-
face through the RxOH_n pin or by the Receive Signaling Serial
Interface through the RxSig_n pin. The Receive Signaling Regis-
ter Array (RSRA) of each timeslot stores its correspondent
Timeslot 16 octet as well.
When these bits are set to 010:
Timeslot 16 octet is output by the Receive Overhead Input Inter-
face through the RxOH_n pin or by the Receive Signaling Serial
Interface through the RxSig_n pin. The Receive Signaling Regis-
ter Array (RSRA) of each timeslot stores its correspondent
Timeslot 16 octet as well.
When these bits are set to 011:
Timeslot 16 octet is output by the Receive Overhead Input Inter-
face through the RxOH_n pin or by the Receive Signaling Serial
Interface through the RxSig_n pin. The Receive Signaling Regis-
ter Array (RSRA) of each timeslot stores its correspondent
Timeslot 16 octet as well.
110
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
When these bits are set to 100:
Timeslot 16 octet is taken directly from the PCM data which in
term determines by the Receive Channel Control Register
(RCCR).
When these bits are set to 101:
Reserved.
When these bits are set to 110:
Reserved.
When these bits are set to 111:
Reserved.D/E Time Slot
When these bits are set to 000:
D or E time slot data are output through the Receive Fractional
Data Input Interface (RxFrTD_n pin).
When these bits are set to 001:
D or E time slot data are output through the Receive Fractional
Data Input Interface (RxFrTD_n pin).
When these bits are set to 010:
D or E time slot data are output through the Receive Fractional
Data Input Interface (RxFrTD_n pin).
When these bits are set to 011:
D or E time slot data are output through the Receive Fractional
Data Input Interface (RxFrTD_n pin).
When these bits are set to 100:
D or E time slot data are output through the Receive Serial Sig-
naling Input Interface (RxSig_n pin).
When these bits are set to 101:
Reserved.
When these bits are set to 110:
Reserved.
When these bits are set to 111:
Reserved.
The following table summaries destinations of National bits,
Timeslot 16 octet and D or E time slots.
National Bits
(Sa4-Sa8)
Timeslot 16
Octet
D or E
Timeslot
RxSIGDL[2:0]
000
001
Data Link
Data Link
RCCR
RxFrTD_n
RxFrTD_n
RxSig_n or
RxOH
RxSig_n or
RxOH
RxSig_n or
RxOH
010
011
None
None
RxFrTD_n
RxFrTD_n
100
101
110
111
Data Link
Reserved
Reserved
Reserved
RCCR
RxSig_n
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
111
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
Signaling Change Register 0 (SCR0) (Indirect Address = 0xn0H, 0x0DH)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Signaling
Signaling
Signaling
Signaling
Signaling
Signaling
Signaling
Signaling
Change Bit of Change Bit of Change Bit of Change Bit of Change Bit of Change Bit of Change Bit of Change Bit of
Channel 0
Channel 1
Channel 2
Channel 3
Channel 4
Channel 5
Channel 6
Channel 7
RUR
0
RUR
0
RUR
0
RUR
0
RUR
0
RUR
0
RUR
0
RUR
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-0
Signaling Change
Indication
RUR
Signaling Change Indication:
These Reset Upon Read bit-fields indicate whether the signaling
data associated with Channel 0-7 has changed since the last
read of this register.
When these bits are zero:
Signaling data associated with certain channel has not changed
since last read of the register.
When these bits are one:
Signaling data associated with certain channel has changed
since last read of the register.
Signaling Change Register 1 (SCR0) (Indirect Address = 0xn0H, 0x0EH)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Signaling
Signaling
Signaling
Signaling
Signaling
Signaling
Signaling
Signaling
Change Bit of Change Bit of Change Bit of Change Bit of Change Bit of Change Bit of Change Bit of Change Bit of
Channel 8
Channel 9
Channel 10
Channel 11
Channel 12
Channel 13
Channel 14
Channel 15
RUR
0
RUR
0
RUR
0
RUR
0
RUR
0
RUR
0
RUR
0
RUR
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-0
Signaling Change
Indication
RUR
Signaling Change Indication:
These Reset Upon Read bit-fields indicate whether the signaling
data associated with Channel 8-15 has changed since the last
read of this register.
When these bits are zero:
Signaling data associated with certain channel has not changed
since last read of the register.
When these bits are one:
Signaling data associated with certain channel has changed
since last read of the register.
112
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
Signaling Change Register 2 (SCR2) (Indirect Address = 0xn0H, 0x0FH)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
Signaling
BIT 0
Signaling
Signaling
Signaling
Signaling
Signaling
Signaling
Signaling
Change Bit of Change Bit of Change Bit of Change Bit of Change Bit of Change Bit of Change Bit of Change Bit of
Channel 16
Channel 17
Channel 18
Channel 19
Channel 20
Channel 21
Channel 22
Channel 23
RUR
0
RUR
0
RUR
0
RUR
0
RUR
0
RUR
0
RUR
0
RUR
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-0
Signaling Change
Indication
RUR
Signaling Change Indication:
These Reset Upon Read bit-fields indicate whether the signaling
data associated with Channel 16-23 has changed since the last
read of this register.
When these bits are zero:
Signaling data associated with certain channel has not changed
since last read of the register.
When these bits are one:
Signaling data associated with certain channel has changed
since last read of the register.
Signaling Change Register 3 (SCR3) - E1 Mode Only (Indirect Address = 0xn0H, 0x10H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Signaling
Signaling
Signaling
Signaling
Signaling
Signaling
Signaling
Signaling
Change Bit of Change Bit of Change Bit of Change Bit of Change Bit of Change Bit of Change Bit of Change Bit of
Channel 24
Channel 25
Channel 26
Channel 27
Channel 28
Channel 29
Channel 30
Channel 31
RUR
0
RUR
0
RUR
0
RUR
0
RUR
0
RUR
0
RUR
0
RUR
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-0
Signaling Change
Indication
RUR
Signaling Change Indication:
These Reset Upon Read bit-fields indicate whether the signaling
data associated with Channel 24-31 has changed since the last
read of this register.
When these bits are zero:
Signaling data associated with certain channel has not changed
since last read of the register.
When these bits are one:
Signaling data associated with certain channel has changed
since last read of the register.
113
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
Receive National Bits Register (RNBR) - E1 Mode Only (Indirect Address = 0xn0H, 0x11H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
International International
Remote
National Bit
Sa4
National Bit
Sa3
National Bit
Sa2
National Bit
Sa1
National Bit
Sa0
Bit in FAS
Frame
Bit in Non- Alarm Indica-
FAS Frame
tion Bit
R/O
0
R/O
0
R/O
0
R/O
0
R/O
0
R/O
0
R/O
0
R/O
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
International Bit in FAS
Frame
R/O
R/O
R/O
International Bit in FAS Frame:
This READ-only bit-field corresponds to the value contained in
the International Bit of received FAS Frame.
6
5
International Bit in non-
FAS Frame
International Bit in non-FAS Frame:
This READ-only bit-field corresponds to the value contained in
the International Bit of received non-FAS Frame.
Remote Alarm Indication
Bit
Remote Alarm Indication Bit:
This READ-only bit-field corresponds to the value contained in
the Remote Alarm Indication (frame Yellow Alarm) bit position of
the received non-FAS Frame.
4
3
2
1
0
National Bit Sa4
National Bit Sa5
National Bit Sa6
National Bit Sa7
National Bit Sa8
R/O
R/O
R/O
R/O
R/O
National Bit Sa4:
This READ-only bit-field corresponds to the value contained in
the National bit Sa4 position of the received non-FAS frame.
National Bit Sa5:
This READ-only bit-field corresponds to the value contained in
the National bit Sa4 position of the received non-FAS frame.
National Bit Sa6:
This READ-only bit-field corresponds to the value contained in
the National bit Sa4 position of the received non-FAS frame.
National Bit Sa7:
This READ-only bit-field corresponds to the value contained in
the National bit Sa4 position of the received non-FAS frame.
National Bit Sa8:
This READ-only bit-field corresponds to the value contained in
the National bit Sa4 position of the received non-FAS frame.
114
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
Receive Extra Bits Register (REBR) - E1 Mode Only (Indirect Address = 0xn0H, 0x12H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Reserved
Extra Bit 1
Far-End
Remote
Extra Bit 2
Extra Bit 3
Alarm Indica-
tion Bit
R/O
0
R/O
0
R/O
0
R/O
0
R/O
0
R/O
0
R/O
0
R/O
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7 - 4
3
Reserved
Extra Bit 1
R/O
R/O
Extra Bit 1:
This READ-only bit-field corresponds to the value contained in
the Extra Bit 1 position (bit 5 in timeslot 16 of Frame 0 of the CAS
multi-frame) of the received E1 data.
2
Far-End Remote Alarm
Indication Bit
R/O
Far-End Remote Alarm Indication Bit:
This READ-only bit-field corresponds to the value contained in
the Far-End Remote Alarm Indication (CAS Multi-frame Yellow
Alarm) bit position (bit 6 in timeslot 16 of Frame 0 of the CAS
multi-frame) of the received non-FAS Frame.
1
0
Extra Bit 2
Extra Bit 3
R/O
R/O
Extra Bit 2:
This READ-only bit-field corresponds to the value contained in
the Extra Bit 2 position (bit 7 in timeslot 16 of Frame 0 of the CAS
multi-frame) of the received E1 data.
Extra Bit 3:
This READ-only bit-field corresponds to the value contained in
the Extra Bit 3 position (bit 8 in timeslot 16 of Frame 0 of the CAS
multi-frame) of the received E1 data.
Data Link Control Register (DLCR) (Indirect Address = 0xn0H, 0x13H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
SLCâ96
Enable
MOS ABORT Receive FCS
Automatic
Receive
LAPD
Transmit
ABORT
Sequence
Transmit
IDLE/FLAG
Sequence Message with
FCS
Transmit
LAPD
MOS or BOS
Select
Enable
Verification
Enable
Message
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
115
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
R/W
SLC 96 Enable
SLC 96 Enable:
This READ/WRITE bit-field permits the user to enable SLC 96
data link transmission in SLC 96 framing mode. In ESF framing
mode, this READ/WRITE bit-field allows Facility Data Link of the
framer to transmit and receive SLC 96-like message.
When this bit is set to zero:
In SLC 96 framing mode, the SLC 96 data link transmission is
disabled. The framer transmits Terminal Framing bits as in SF
framing mode. The Signaling Framing bits are forced to ones.
In ESF framing mode, Facility Data Link of the framer is config-
ured to transmit and receive regular data link message.
When this bit is set to one:
In SLC 96 framing mode, the SLC 96 data link transmission is
enabled. The framer transmits Terminal Framing bits as in SF
framing mode. The Signaling Framing bits are transmitted and
received in SLC 96 data link format.
In ESF framing mode, Facility Data Link of the framer is config-
ured to transmit and receive SLC 96-like message.
6
MOS ABORT Enable
R/W
MOS ABORT Enable:
This READ/WRITE bit-field enables and disables the Transmit
LAPD Controller of the framer to automatically insert an ABORT
sequence anytime it transitions from the Message Oriented Sig-
naling (MOS) mode to the Bit Oriented Signaling (BOS) mode.
When this bit is set to zero:
The Transmit LAPD Controller inserts an MOS ABORT
sequence to the data link message when the framer transitions
from MOS to BOS.
When this bit is set to one:
The Transmit LAPD Controller does not insert an MOS ABORT
sequence to the data link message when the framer transitions
from MOS to BOS.
5
Receive FCS Verification
Enable
R/W
Receive FCS Verification Enable:
This READ/WRITE bit-field enables and disables the Receive
LAPD Controller of the framer to compute and verify the Frame
Check Sequence (FCS) value in the incoming LAPD message.
When this bit is set to zero:
The Receive LAPD Controller computes and verifies the Frame
Check Sequence (FCS) of each MOS message.
When this bit is set to one:
The Receive LAPD Controller does not compute and verify the
Frame Check Sequence (FCS) of each MOS message.
116
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
4
Automatic Receive LAPD
Message
R/W
Automatic Receive LAPD Message:
This READ/WRITE bit-field configures the Receive LAPD Con-
troller of the framer to compare and discard any incoming LAPD
message that exactly match which is currently stored in the
Receive LAPD Controller.
When this bit is set to zero:
The Receive LAPD Controller does not discard any incoming
LAPD message. Every incoming LAPD message automatically
stores in the Receive LAPD Controller and overwrites the previ-
ous received LAPD message.
When this bit is set to one:
The Receive LAPD Controller compares any incoming LAPD
message with the previous message that is currently stored in
the Received LAPD Controller. If the incoming LAPD message is
the same as the previous one, it will be automatically discarded.
3
2
1
Transmit ABORT
Sequence
R/W
R/W
R/W
Transmit ABORT Sequence:
This READ/WRITE bit-field configures the Transmit LAPD Con-
troller to transmit an ABORT sequence into the Facility Data Link
channel to the remote terminal. An ABORT sequence is a string
of seven or more consecutive ones.
When this bit is set to zero:
The Transmit LAPD Controller does not insert an ABORT
sequence into the Facility Data Link channel.
When this bit is set to one:
The transmit LAPD Controller inserts an ABORT sequence into
the Facility Data Link channel.
Transmit IDLE/FLAG
Sequence
Transmit IDLE/FLAG Sequence:
This READ/WRITE bit-field configures the Transmit LAPD Con-
troller to insert a string of IDLE/Flag sequence into the Facility
Data Link channel to the remote terminal. An IDLE/FLAG
sequence is an octet of with value 0x7E.
When this bit is set to zero:
The Transmit LAPD Controller does not insert an IDLE/FLAG
sequence into the Facility Data Link channel.
When this bit is set to one:
The Transmit LAPD Controller inserts an IDLE/FLAG sequence
into the Facility Data Link channel.
Transmit LAPD Message
with FCS
Transmit LAPD Message with FCS:
This READ/WRITE bit-field forces the Transmit LAPD Controller
to include Frame Check Sequence (FCS) octets into the out-
bound LAPD message.
When this bit is set to zero:
The Transmit LAPD Controller does not include FCS octets into
the outbound LAPD message.
When this bit is set to one:
The Transmit LAPD Controller inserts FCS octets into the out-
bound LAPD message.
NOTE: This bit-field is ignored if the framer is configured to oper-
ate in BOS mode.
117
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
0
MOS or BOS Select
R/W
MOS or BOS Select:
This READ/WRITE bit-field specifies whether the Transmit and
Receive LAPD Controller to operate in Message Oriented Sig-
naling (MOS) or Bit Oriented Signaling (BOS) mode.
When this bit is set to zero:
The Transmit and Receive LAPD Controller transmit and receive
LAPD message in MOS mode.
When this bit is set to one:
The Transmit and Receive LAPD Controller transmit and receive
LAPD message in BOS mode.
Transmit Data Link Byte Count Register (TDLBCR) (Indirect Address = 0xn0H, 0x14H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Transmit Data
Link Buffer
Select
Transmit Data Link Byte Count Bits [6:0]
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Transmit Data Link Buffer
Select
R/W
Transmit Data Link Buffer Select:
This READ/WRITE bit-field permits the user to select which one
of the two Transmit Data Link Buffers will be loaded for transmis-
sion.
When this bit is set to zero:
The Transmit Data Link Buffer 0 will be loaded for transmission of
data link bits.
When this bit is set to one:
The Transmit Data Link Buffer 1 will be loaded for transmission of
data link bits.
118
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
6 - 0
Transmit Data Link Byte
Count [6:0]
R/W
Transmit Data Link Byte Count [6:0]:
These READ/WRITE bit-fields hold the length of the MOS mes-
sage to be transmitted or the number of repetitions of BOS to be
transmitted. The user should program these bit-fields to equal
the length of the MOS message in bytes or the number of repeti-
tions of BOS message.
The LAPD controller will load the value of these bits from the
Transmit Data Link Byte Count register and use it as its internal
counter at the beginning of each transfer. After the entire MOS
message is transmitted or x number of repetitions of BOS mes-
sage transmission is completed, the LAPD controller will gener-
ate the Transmit End of Transfer (TxEOT) interrupt.
Each Transmit Data Link Buffer is 96-bytes wide.
NOTE: In the case of BOS messaging, if these bit-fields are
equal to zero, the BOS message will be transmitted infinitely and
no Transmit End of Transfer (TxEOT) interrupt will be generated.
Receive Data Link Byte Count Register (TDLBCR) (Indirect Address = 0xn0H, 0x15H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Receive Data
Link Buffer
Select
Receive Data Link Byte Count Bits [6:0]
R
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Receive Data Link Buffer
Select
R
Receive Data Link Buffer Select:
This READ/WRITE bit-field informs the user which one of the
two Receive Data Link Buffers are available for receiving data
link messages.
When this bit is set to zero:
The Receive Data Link Buffer 0 will be used for received data link
bits.
When this bit is set to one:
The Receive Data Link Buffer 1 will be used for received data link
bits.
119
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
6 - 0
Receive Data Link Byte
Count [6:0]
R/W
Receive Data Link Byte Count [6:0]:
These READ/WRITE bit-fields hold the length of the MOS mes-
sage received or the number of repetitions of BOS message
received. The user should program these bit-fields to equal the
length of the MOS message in bytes or the number of repetitions
of BOS message.
The LAPD controller will load the value of these bits from the
Receive Data Link Byte Count register and use it as its internal
counter at the beginning of each transfer. After the entire MOS
message is received or x number of repetitions of BOS message
is received, the LAPD controller will generate the Receive End of
Transfer (RxEOT) interrupt.
Each Receive Data Link Buffer is 96-bytes wide.
NOTE: In the case of BOS messaging, these bit-fields cannot be
set to zero. Otherwise, no Receive End of Transfer (RxEOT)
interrupt will be generated.
Slip Buffer Control Register (SBCR) (Indirect Address = 0xn0H, 0x16H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Transmit Slip
Buffer is FIFO
Reserved
Force
Signaling
Freeze
Signaling
Freeze
Enable
Slip Buffer
Receive Syn-
chronization
Direction
Slip Buffer Enable Bit [1:0]
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Transmit Slip Buffer is
FIFO
R/W
Slip Buffer is FIFO:
This READ/WRITE bit-field allows the user to determine function
of the buffer when TxLineClk_n and TxSerClk_n are synchro-
nized with each other.
When this bit is 0:
The buffer acts as slip buffer if enabled by the Slip Buffer Enable
bit [1:0].
When this bit is 1:
The buffer acts as FIFO.
6 - 5
Reserved
120
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
4
Force Signaling Freeze
R/W
Force Signaling Freeze:
This READ/WRITE bit-field allows the user to stop further signal-
ing updating.
When this bit is 0:
The framer continues extracts and updates signaling information
received.
When this bit is 1:
The framer stops extracting signaling information received, this
is called Signaling Freeze.
3
Signaling Freeze Enable
R/W
Signaling Freeze Enable:
This READ/WRITE allows the user to stop the framer from
updating signaling information for one multi-frame after buffer
slipping. Enabling signaling freeze after buffer slipping can elimi-
nate incorrect signaling information been extracted and updated
by the framer.
When this bit is 0:
Signaling freeze is disabled. The framer will continue to extract
and update signaling information for one multi-framer after buffer
slipping.
When this bit is 1:
Signaling freeze is enabled. The framer will not extract and
update signaling information for one multi-framer after buffer slip-
ping.
2
Slip Buffer Receive Syn-
chronization Direction
R/W
Slip Buffer Receive Synchronization Direction:
When this bit is set to 0:
The Receive Single-Frame Synchronization signal (RxSync_n) is
an output if the Slip Buffer is not in bypass mode.
When this bit is set to 1:
The Receive Single-Frame Synchronization signal (RxSync_n) is
an input if the Slip Buffer is not in bypass mode.
121
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1-0
Slip Buffer Enable
R/W
Slip Buffer Enable:
When these bits are set to 00:
Slip Buffer is bypassed. The Receive Payload Data is passing
from the Receive Framer Module to the Receive Payload Data
Output Interface directly without routing through the Slip Buffer.
The Receive Serial Clock signal (RxSerClk_n) is an output.
When these bits are set to 01:
The Elastic Store (Slip Buffer) is enabled. The Receive Payload
Data is passing from the Receive Framer Module through the
Slip Buffer to the Receive Payload Data Output Interface. The
Receive Serial Clock signal (RxSerClk_n) is an input.
When these bits are set to 10:
The Slip Buffer acts as a FIFO. The FIFO Latency Register
(FLR) determines the data latency. The Receive Payload Data is
passing from the Receive Framer Module through the FIFO to
the Receive Payload Data Output Interface. The Receive Serial
Clock signal (RxSerClk_n) is an input.
When these bits are set to 11:
Slip Buffer is bypassed. The Receive Payload Data is passing
from the Receive Framer Module to the Receive Payload Data
Output Interface directly without routing through the Slip Buffer.
The Receive Serial Clock signal (RxSerClk_n) is an output.
FIFO Latency Register (FIFOLR) (Indirect Address = 0xn0H, 0x17H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Reserved
FIFO Latency [4:0]
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-5
4-0
Reserved
R/W
R/W
FIFO Latency
FIFO Latency:
These bits determine depth of the FIFO in terms of bytes. The
largest possible value is thirty-two bytes or one E1 frame.
122
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
Interrupt Control Register (ICR) (Indirect Address = 0xn0H, 0x1AH)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Reserved
Clear
Clear
Enable of
Interrupt
Interrupt
Interrupt
Status Bits By Enable Bits
Write
Generation
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-3
2
Reserved
R/W
R/W
Clear Interrupt Status Bit By Write:
Clear Interrupt Status
Bits By Write
This Read/Write bit field determines how to clear the interrupt sta-
tus bits.
When this bit is set to 0:
The status bits are reset upon read.
When this bit is set to 1:
The status bits are reset by writing a zero.
1
Clear Interrupt Enable
Bits
R/W
Clear Interrupt Enable Bit:
This Read/Write bit field determines how to clear the interrupt
enable bits.
When this bit is set to 0:
The status bits are not reset upon reading of corresponding sta-
tus bits.
When this bit is set to 1:
The status bits are reset upon reading of corresponding status
bits.
0
Enable of Interrupt
Generation
R/W
Enable of Interrupt Generation:
This Read/Write bit field is used to enable T1/E1 framer interrupt
generation.
When this bit is set to 0:
XRT84L38 will not generate interrupt. Instead, status polling of
the framer will be enabled.
When this bit is set to 1:
Interrupt generation is enabled.
123
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
LAPD Channel Select Register (LCSR) (Indirect Address = 0xn0H, 0x1BH)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Reserved
LAPD Channel Select
Bit [1:0]
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-2
1-0
Reserved
R/W
R/W
LAPD Channel Select
Bit [1:0]
LAPD Channel Select Bit [1:0]:
These Read/Write bit fields determine which one of the three
current LAPD channel being accessed.
When these bits are set to 00:
LAPD Channel 1 is being accessed.
When these bits are set to 01:
LAPD Channel 2 is being accessed.
When these bits are set to 10:
LAPD Channel 3 is being accessed.
When these bits are set to 11:
LAPD Channel 1 is being accessed.
Transmit Interface Control Register (TICR) (Indirect Address = 0xn0H, 0x20H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Transmit
Fraction Data
Interface
Reserved
Transmit
PayloadClock Fractional E1
Transmit
Transmit
Clock
Inversion
Transmit
Multiplex
Enable
Transmit
Interface
Mode Select Mode Select
Transmit
Interface
Select /
Transmit
Input Enable
Select
Bit 1
Bit 0
Sync- Pulse
Low Active
Select
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
124
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Transmit Fraction Data
Interface Select
R/W
Transmit Fraction Data Interface Select:
When this bit is set to 0:
The Transmit Serial Fractional Data (TxFrTD_n) input pins are
used to accept fractional serial data.
The Transmit Timeslot Clock (TxTsClk_n) pins are used to out-
put fractional data clock.
When this bit is set to 1:
The Transmit Timeslot Clock (TxTSClk_n) pins are used to input
fractional serial data enable signal.
Fractional serial data is clocked into the framer using ungapped
TxSerClk_n signals.
6
5
Reserved
Transmit Payload Clock
Select / Transmit Sync-
Pulse Low Active Select
R/W
Transmit Payload Clock Select / Transmit Sync- Pulse Low Active
Select:
When this bit is set to 0:
The TxSerClk_n pins will output ungapped Transmit clock for
correspondent DS1/E1 clock rates.
In non-1.544 MHz mode for DS1 or non-2.048 MHz mode for E1,
the XRT84L38 chip expects a HIGH active pulse for frame syn-
chronization.
When this bit is set to 1:
The TxSerClk_n pins will output a gapped Transmit clock with
OH bit period blocked for correspondent DS1/E1 clock rates.
In non-1.544 MHz mode for DS1 or non-2.048 MHz mode for E1,
the XRT84L38 chip expects a LOW active pulse for frame syn-
chronization.
125
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
4
Transmit Fractional E1
Input Enable
R/W
Transmit Fractional E1 Input Enable:
When this bit is set to 0:
The Transmit Time-slot Indication bits (TxTSb[4:0] are outputting
five-bit binary values of Time-slot number (0-31) being accepted
and processed by the Transmit Payload Data Input Interface
block of the framer.
The Transmit Time-slot Indicator Clock signal (TxTSClk_n) is a
256KHz clock that pulses HIGH for one E1 bit period whenever
the Transmit Payload Data Input Interface block is accepting the
LSB of each of the twenty-four time slots.
When this bit is set to 1:
The TxTSb[0]_n bit becomes the Transmit Fractional E1 Input
signal (TxFrTD_n) which carries Fractional E1 payload data into
the framer.
The TxTSb[1]_n bit becomes the Transmit Signaling Data Input
signal (TxSig_n) which is used to insert robbed-bit signaling data
into the outbound E1 frame.
The TxTSb[2]_n bit serially outputs all five-bit binary values of
the Time Slot number (0-31) being accepted and processed by
the Transmit Payload Data Input Interface block of the framer.
The TxTSb[3]_n bit becomes the Transmit Overhead Synchroni-
zation Pulse (TxOHSync_n) which is used to output an Over-
head Synchronization Pulse that indicates the first bit of each
E1multi-frame.
The TxTSClk_n will output gaped fractional E1 clock that can be
used by Terminal Equipment to clock out Fractional E1 payload
data at rising edge of the clock. Or,
The TxTSClk_n pin will be a clock enable signal to Transmit
Fractional E1 Input signal (TxFrTD_n) when the un-gaped Trans-
mit Serail Input Clock (TxSerClk_n) is used to clock in Fractional
E1 Payload Data into the framer.
3
Transmit Clock Inversion
R/W
Transmit Clock Inversion:
When this bit is set to 0:
Serial data transition happens on rising edge of the Transmit
Serial Clock.
When this bit is set to 1:
Serial data transition happens on falling edge of the Transmit
Serial Clock.
2
Transmit Multiplex Enable
R/W
Transmit Multiplex Enable:
When this bit is set to 0:
The Transmit Back-plane Interface block is configured to non-
channel-multiplexed mode
When this bit is set to 1:
The Transmit Back-plane Interface block is configured to chan-
nel-multiplexed mode
126
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1-0
Transmit Interface Mode
Select
R/W
Transmit Interface Mode Select:
When combined with the Transmit Multiplex Enable bit, these
bits determine the Transmit Back-plane Interface data rate.
The table below illustrates the Transmit Back-plane Interface
data rate for E1 mode with different Transmit Multiplex Enable bit
and Transmit Interface Mode Select Bits settings.
Transmit
Interface
Mode
Select Bit
1
Transmit
Interface
Mode
Select Bit
0
Transmit
Multiplex
Enable Bit
Back-plane
Interface
Data Rate
XRT84V24
Compatible
2.048Mbit/s
0
0
0
0
0
1
MVIP
2.048Mbit/s
0
0
1
1
1
0
0
1
0
4.096Mbit/s
8.192Mbit/s
-
Bit Multiplexed
16.384Mbit/s
1
1
1
0
1
1
1
0
1
HMVIP
16.384Mbit/s
H.100
16.384Mbit/s
Receive Interface Control Register (RICR) (Indirect Address = 0xn0H, 0x22H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Receive
Fraction Data
Interface
Reserved
Receive
PayloadClock Fractional E1
Receive
Receive
Clock
Inversion
Receive
Multiplex
Enable
Receive
Interface
Mode Select Mode Select
Receive
Interface
Select /
Receive
Input Enable
Select
Bit 1
Bit 0
Sync- Pulse
Low Active
Select
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
127
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Receive Fraction Data
Interface Select
R/W
Receive Fraction Data Interface Select:
When this bit is set to 0:
The Receive Serial Fractional Data (RxFrTD_n) output pins are
used to output fractional serial data.
The Receive Timeslot Clock (RxTsClk_n) pins are used to output
fractional data clock.
When this bit is set to 1:
The Receive Timeslot Clock (RxTSClk_n) pins are used to out-
put fractional serial data enable signal.
Fractional serial data is clocked out from the framer using
ungapped RxSerClk_n signals.
6
5
Reserved
Receive Payload Clock
Select / Receive Sync-
Pulse Low Active Select
R/W
Receive Payload Clock Select / Receive Sync- Pulse Low
Active Select:
When this bit is set to 0:
The RxSerClk_n pins will output ungapped Receive clock for cor-
respondent DS1/E1 clock rates.
In non-1.544 MHz mode for DS1 or non-2.048 MHz mode for E1,
the XRT84L38 chip generates a HIGH active pulse for frame
synchronization.
When this bit is set to 1:
The RxSerClk_n pins will output a gapped Receive clock with
OH bit period blocked for correspondent DS1/E1 clock rates.
In non-1.544 MHz mode for DS1 or non-2.048 MHz mode for E1,
the XRT84L38 chip generates a LOW active pulse for frame syn-
chronization.
128
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
4
Receive Fractional E1
Output Enable
R/W
Receive Fractional E1 Output Enable:
When this bit is set to 0:
The Receive Time-slot Indication bits (RxTSb[4:0] are outputting
five-bit binary values of Time-slot number (0-31) being accepted
and processed by the Receive Payload Data Output Interface
block of the framer.
The Receive Time-slot Indicator Clock signal (RxTSClk_n) is a
256KHz clock that pulses HIGH for one E1 bit period whenever
the Receive Payload Data Output Interface block is accepting the
LSB of each of the twenty-four time slots.
When this bit is set to 1:
The RxTSb[0]_n bit becomes the Receive Fractional E1 Output
signal (RxFrTD_n) which carries Fractional E1 payload data from
the framer.
The RxTSb[1]_n bit becomes the Receive Signaling Data Output
signal (RxSig_n) which is used to carry robbed-bit signaling data
extracted from the inbound E1 frame.
The RxTSb[2]_n bit serially outputs all five-bit binary values of
the Time Slot number (0-31) being accepted and processed by
the Receive Payload Data Output Interface block of the framer.
The RxTSClk_n will output gaped fractional E1 clock that can be
used by Terminal Equipment to latch in Fractional E1 payload
data at rising edge of the clock. Or,
The RxTSClk_n pin will be a clock enable signal to Receive
Fractional E1 Output signal (RxFrTD_n) when the un-gaped
Receive Serail Output Clock (RxSerClk_n) is used to latch in
Fractional E1 Payload Data into the Terminal Equipment.
3
Receive Clock Inversion
R/W
Receive Clock Inversion:
When this bit is set to 0:
Serial data transition happens on rising edge of the Receive
Serial Clock.
When this bit is set to 1:
Serial data transition happens on falling edge of the Receive
Serial Clock.
2
Receive Multiplex Enable
R/W
Receive Multiplex Enable:
When this bit is set to 0:
The Receive Back-plane Interface block is configured to non-
channel-multiplexed mode.
When this bit is set to 1:
The Receive Back-plane Interface block is configured to chan-
nel-multiplexed mode
129
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1-0
Receive Interface Mode
Select
R/W
Receive Interface Mode Select:
When combined with the Receive Multiplex Enable bit, these bits
determine the Receive Back-plane Interface data rate.
The table below illustrates the Receive Back-plane Interface data
rate for E1 mode with different Receive Multiplex Enable bit and
Receive Interface Mode Select Bits settings.
Receive
Interface
Mode
Select Bit
1
Receive
Interface
Mode
Select Bit
0
Receive
Multiplex
Enable Bit
Back-plane
Interface
Data Rate
XRT84V24
Compatible
2.048Mbit/s
0
0
0
0
0
1
MVIP
2.048Mbit/s
0
0
1
1
1
0
0
1
0
4.096Mbit/s
8.192Mbit/s
-
Bit Multiplexed
16.384Mbit/s
1
1
1
0
1
1
1
0
1
HMVIP
16.384Mbit/s
H.100
16.384Mbit/s
General Test Register (GTR) (Indirect Address = 0xn0H, 0x23H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
PRBS Type
Select
Error
Insertion
Data
Inversion
Select
Receive
Receive
Transmit
Receive DS1/ Transmit DS1/
PRBS Lock PRBS Block PRBS Block
Indication
E1 Framer
Bypassed
E1 Framer
Bypassed
Enable
R/W
0
Enable
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
PRBS Type Select
R/W
PRBS Type Select:
When this bit is set to 0:
The polynomial for generating the PRBS pattern is X15 + X14 +
1.
When this bit is set to 1:
A QRTS pattern is generated as the PRBS pattern.
130
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
6
Error Insertion
R/W
Error Insertion:
A zero to one transition of this bit will cause one bit of the outgo-
ing transmit data inverted.
5
Data Inversion Select
R/W
Data Inversion Select:
When this bit is set to 0:
The outgoing transmit data and incoming receive data are not
changed.
When this bit is set to 1:
The outgoing transmit data and incoming receive data are
inverted.
4
Receive PRBS Lock
Indication
R/W
Receive PRBS Lock Indication:
If the Receive PRBS block is enabled, this bit indicates whether
a PRBS pattern is found in the incoming received data and the
PRBS pattern is locked.
When this bit is set to 0:
There is no PRBS pattern found and locked in the incoming
received data stream.
When this bit is set to 1:
A PRBS pattern found and locked in the incoming received data
stream.
3
Receive PRBS Block
Enable
R/W
Receive PRBS Block Enable :
When this bit is set to 0:
The Receive PRBS block is disabled. The framer will not check
the incoming received data for PRBS pattern.
When this bit is set to 1:
The Receive PRBS block is enabled. The framer will check the
incoming received data for PRBS pattern.
2
Transmit PRBS Block
Enable
R/W
Transmit PRBS Block Enable :
When this bit is set to 0:
The Transmit PRBS block is disabled. The framer will not insert
PRBS pattern into the outgoing transmit data stream.
When this bit is set to 1:
The Transmit PRBS block is enabled. The framer will insert
PRBS pattern into the outgoing transmit data stream.
1
0
Receive DS1/E1 Framer
Bypassed
R/W
R/W
Receive DS1/E1 Framer Bypassed:
When this bit is set to 0:
The Receive DS1/E1 Framer is not bypassed.
When this bit is set to 1:
The Receive DS1/E1 Framer is bypassed.
Transmit DS1/E1 Framer
Bypassed
Transmit DS1/E1 Framer Bypassed:
When this bit is set to 0:
The Transmit DS1/E1 framer is not bypassed.
When this bit is set to 1:
The Transmit DS1/E1 framer is bypassed. Unframed DS1/E1
payload data are passed from backplane interface into the DS1/
E1 line.
131
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
Loop-back Code Control Register (LCCR) (Indirect Address = 0xn0H, 0x24H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Receive
Loop-back
Code
Receive
Loop-back
Code
Receive
Loop-back
Code
Receive
Loop-back
Code
Transmit
Loop-back
Transmit
Loop-back
Framed
Loop-back
Automatic
Loop-back
Select
Code Length Code Length Code Select
Activation
Activation
De-Activation De-Activation
Bit 1
Bit 0
Length Bit 1 Length Bit 0 Length Bit 1 Length Bit 0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-6
Receive Loop-back Code
Activation Length
R/W
Receive Loop-back Code Activation Length:
These bits are used to determine the Receive Loop-back Code
Activation length. The table below shows length of the Receive
Loop-back Activation code according to values of these bits.
Bit Value
Length of Loop-back Code
00
01
10
11
4
5
6
7
5-4
Receive Loop-back Code
De-Activation Length
R/W
Receive Loop-back Code Activation Length:
These bits are used to determine the Receive Loop-back Code
De-Activation length. The table below shows length of the
Receive Loop-back De-Activation code according to values of
these bits.
Bit Value
Length of Loop-back Code
00
01
10
11
4
5
6
7
132
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3-2
Transmit Loop-back Code
Length
R/W
Transmit Loop-back Code Length:
These bits are used to determine the Transmit Loop-back Code
Activation length. The table below shows length of the Transmit
Loop-back code according to values of these bits.
Bit Value
Length of Loop-back Code
00
01
10
11
4
5
6
7
1
0
Framed Loop-back Code
Select
R/W
R/W
Framed Loop-back Code Select:
When this bit is set to 0:
The Loop-back code that transmitted or recieved is unframed.
When this bit is set to 1:
The Loop-back code that transmitted or received is framed.
Automatic Loop-back
Select
Automatic Loop-back Select:
When this bit is set to 0:
Automatic Loop-back is disabled.
When this bit is set to 1:
Automatic Loop-back is enabled.
Transmit Loop-back Code Register (TLCR) (Indirect Address = 0xn0H, 0x25H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Transmit Loop-back Code Bit[6:0]
Transmit
Loop-back
Code Enable
R/W
1
R/W
0
R/W
1
R/W
0
R/W
1
R/W
0
R/W
1
R/W
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-1
Transmit Loop-back Code
Bit[6:0]
R/W
Transmit Loop-back Code Bit[6:0]:
These bits are the Transmit Loop-back Code sequence.
133
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
0
Transmit Loop-back Code
Enable
R/W
Transmit Loop-back Code Enable:
When this bit is set to 0:
Transmit Loop-back Code is disabled. Transmit Loop-back Code
is not sent to the line.
When this bit is set to 1:
Transmit Loop-back Code is enabled. Transmit Loop-back Code
is generated and repeatedly sent to the line instead of payload
data.
Receive Loop-back Activation Code Register (RLACR) (Indirect Address = 0xn0H, 0x26H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Receive Loop-back Activation Code Bit[6:0]
Receive
Loop-back
Activation
Code Enable
R/W
1
R/W
0
R/W
1
R/W
0
R/W
1
R/W
0
R/W
1
R/W
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-1
Receive Loop-back
R/W
Receive Loop-back Activation Code Bit[6:0]:
Activation Code Bit[6:0]
These bits are the Receive Loop-back Activation Code
sequence.
0
Receive Loop-back
R/W
Receive Loop-back Activation Code Enable:
Activation Code Enable
When this bit is set to 0:
Receive Loop-back Activation Code is disabled. Receive Loop-
back Activation Code is not sent to the line.
When this bit is set to 1:
Receive Loop-back Activation Code is enabled. Receive Loop-
back Activation Code is generated and repeatedly sent to the
line instead of payload data.
134
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
Receive Loop-back De-Activation Code Register (RLACR) (Indirect Address = 0xn0H, 0x27H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Receive Loop-back De-Activation Code Bit[6:0]
Receive
Loop-back
De-Activation
Code Enable
R/W
1
R/W
0
R/W
1
R/W
0
R/W
1
R/W
0
R/W
1
R/W
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-1
Receive Loop-back
De-Activation Code
Bit[6:0]
R/W
Receive Loop-back De-Activation Code Bit[6:0]:
These bits are the Receive Loop-back De-Activation Code
sequence.
0
Receive Loop-back
De-Activation Code
Enable
R/W
Receive Loop-back De-Activation Code Enable:
When this bit is set to 0:
Receive Loop-back De-Activation Code is disabled. Receive
Loop-back De-Activation Code is not sent to the line.
When this bit is set to 1:
Receive Loop-back De-Activation Code is enabled. Receive
Loop-back De-Activation Code is generated and repeatedly sent
to the line instead of payload data.
Transmit Sa Select Register (TSASR) (Indirect Address = 0xn0H, 0x030H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Transmit Sa8 Transmit Sa7 Transmit Sa6 Transmit Sa5 Transmit Sa4
Loop-back
Loop-back
Loop-back
Select
Select
Select
Select
Select
Mode 1 Auto Mode 2 Auto Release Auto
Enable
R/W
0
Enable
R/W
0
Enable
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Transmit Sa8 Select
R/W
Transmit Sa8 Select:
This bit determines whether the source of Sa8 bit is from trans-
mit serial input or transmit Sa8 register.
When this bit is set to 0:
The source of .Sa8 bit is from transmit serial input.
When this bit is set to 1:
The source of .Sa8 bit is from transmit Sa8 register.
135
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
6
5
4
3
2
Transmit Sa7 Select
Transmit Sa6 Select
Transmit Sa5 Select
Transmit Sa4 Select
R/W
Transmit Sa7 Select:
This bit determines whether the source of Sa7 bit is from trans-
mit serial input or transmit Sa7 register.
When this bit is set to 0:
The source of .Sa7 bit is from transmit serial input.
When this bit is set to 1:
The source of .Sa7 bit is from transmit Sa7 register.
R/W
R/W
R/W
R/W
Transmit Sa6 Select:
This bit determines whether the source of Sa6 bit is from trans-
mit serial input or transmit Sa6 register.
When this bit is set to 0:
The source of .Sa6 bit is from transmit serial input.
When this bit is set to 1:
The source of .Sa6 bit is from transmit Sa6 register.
Transmit Sa5 Select:
This bit determines whether the source of Sa5 bit is from trans-
mit serial input or transmit Sa5 register.
When this bit is set to 0:
The source of .Sa5 bit is from transmit serial input.
When this bit is set to 1:
The source of .Sa5 bit is from transmit Sa5 register.
Transmit Sa4 Select:
This bit determines whether the source of Sa4 bit is from trans-
mit serial input or transmit Sa4 register.
When this bit is set to 0:
The source of .Sa4 bit is from transmit serial input.
When this bit is set to 1:
The source of .Sa4 bit is from transmit Sa4 register.
Loop-back Mode 1 Auto
Enable
Loop-back Mode 1 Auto Enable :
The bit enables local loop-back of the framer while a certain con-
dition is happened.
When this bit is 0:
No local loop-back is activated.
When this bit is 1:
Local loop-back is activated if the following condition happened
from the transmit serial inputs:
• Sa5 = 0 for 8 consecutive times.
• Sa6 = 1111 for 8 consecutive times.
• Remote yellow alarm bit (A bit) is 1.
136
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1
Loop-back Mode 2 Auto
Enable
R/W
Loop-back Mode 2 Auto Enable :
The bit enables local loop-back of the framer while a certain con-
dition is happened.
When this bit is 0:
No local loop-back is activated.
When this bit is 1:
Local loop-back is activated if the following condition happened
from the transmit serial inputs:
• Sa5 = 0 for 8 consecutive times.
• Sa6 = 1010 for 8 consecutive times.
• Remote yellow alarm bit (A bit) is 1.
0
Loop-back Mode Release
Auto Enable
R/W
Loop-back Mode Release Auto Enable :
The bit enables local loop-back to be released automatically if a
certain condition is happened.
When this bit is 0:
No local loop-back is released.
When this bit is 1:
Local loop-back is released if the following condition happened
from the transmit serial inputs:
• Sa5 = 0 for 8 consecutive times.
• Sa6 = 0000 for 8 consecutive times.
Transmit Sa4 Register (TSA4R) (Indirect Address = 0xn0H, 0x33H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Transmit Sa4 Bit[7:0]
R/W
1
1
1
1
1
1
1
1
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-0
Transmit Sa4 Bit[7:0]
R/W
Transmit Sa4 bit[7:0]:
These Read/Write bit fields determine contents of the Sa4 bits
when Transmit Sa4 Enable bit is 0 and Transmit Sa4 Select bit is
1.
Bit 7 of this register is transmitted as Sa4 bit in Frame 2 of the
CRC-4 Multi-frame. Bit 6 of this register is transmitted as Sa4 bit
in Frame 4 of the CRC-4 Multi-frame, etc.
137
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
Transmit Sa5 Register (TSA5R) (Indirect Address = 0xn0H, 0x34H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Transmit Sa5 Bit[7:0]
R/W
1
1
1
1
1
1
1
1
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-0
Transmit Sa5 Bit[7:0]
R/W
Transmit Sa5 bit[7:0]:
These Read/Write bit fields determine contents of the Sa5 bits
when Transmit Sa5 Enable bit is 0 and Transmit Sa5 Select bit is
1.
Bit 7 of this register is transmitted as Sa5 bit in Frame 2 of the
CRC-4 Multi-frame. Bit 6 of this register is transmitted as Sa5 bit
in Frame 4 of the CRC-4 Multi-frame, etc.
Transmit Sa6 Register (TSA6R) (Indirect Address = 0xn0H, 0x35H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Transmit Sa6 Bit[7:0]
R/W
1
1
1
1
1
1
1
1
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-0
Transmit Sa6 Bit[7:0]
R/W
Transmit Sa6 bit[7:0]:
These Read/Write bit fields determine contents of the Sa6 bits
when Transmit Sa6 Enable bit is 0 and Transmit Sa6 Select bit is
1.
Bit 7 of this register is transmitted as Sa6 bit in Frame 2 of the
CRC-4 Multi-frame. Bit 6 of this register is transmitted as Sa6 bit
in Frame 4 of the CRC-4 Multi-frame, etc.
Transmit Sa7 Register (TSA7R) (Indirect Address = 0xn0H, 0x36H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Transmit Sa7 Bit[7:0]
R/W
1
1
1
1
1
1
1
1
138
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-0
Transmit Sa7 Bit[7:0]
R/W
Transmit Sa7 bit[7:0]:
These Read/Write bit fields determine contents of the Sa7 bits
when Transmit Sa7 Enable bit is 0 and Transmit Sa7 Select bit is
1.
Bit 7 of this register is transmitted as Sa7 bit in Frame 2 of the
CRC-4 Multi-frame. Bit 6 of this register is transmitted as Sa7 bit
in Frame 4 of the CRC-4 Multi-frame, etc.
Transmit Sa8 Register (TSA8R) (Indirect Address = 0xn0H, 0x37H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Transmit Sa8 Bit[7:0]
R/W
1
1
1
1
1
1
1
1
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-0
Transmit Sa8 Bit[7:0]
R/W
Transmit Sa8 bit[7:0]:
These Read/Write bit fields determine contents of the Sa8 bits
when Transmit Sa8 Enable bit is 0 and Transmit Sa8 Select bit is
1.
Bit 7 of this register is transmitted as Sa8 bit in Frame 2 of the
CRC-4 Multi-frame. Bit 6 of this register is transmitted as Sa8 bit
in Frame 4 of the CRC-4 Multi-frame, etc.
Receive Sa4 Register (RSA4R) (Indirect Address = 0xn0H, 0x3BH)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Receive Sa4 Bit[7:0]
R
0
0
0
0
0
0
0
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-0
Receive Sa4 Bit[7:0]
R/W
Receive Sa4 bit[7:0]:
These Read/Write bit fields store contents of the Sa4 bits
received from the incoming serial data.
Bit 7 of this register is received as Sa4 bit in Frame 2 of the CRC-
4 Multi-frame. Bit 6 of this register is transmitted as Sa4 bit in
Frame 4 of the CRC-4 Multi-frame, etc.
139
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
Receive Sa5 Register (RSA5R) (Indirect Address = 0xn0H, 0x3CH)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Receive Sa5 Bit[7:0]
R
0
0
0
0
0
0
0
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-0
Receive Sa5 Bit[7:0]
R/W
Receive Sa5 bit[7:0]:
These Read/Write bit fields store contents of the Sa5 bits
received from the incoming serial data.
Bit 7 of this register is received as Sa5 bit in Frame 2 of the CRC-
4 Multi-frame. Bit 6 of this register is transmitted as Sa5 bit in
Frame 4 of the CRC-4 Multi-frame, etc.
Receive Sa6 Register (RSA6R) (Indirect Address = 0xn0H, 0x3DH)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Receive Sa6 Bit[7:0]
R
0
0
0
0
0
0
0
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-0
Receive Sa6 Bit[7:0]
R/W
Receive Sa6 bit[7:0]:
These Read/Write bit fields store contents of the Sa6 bits
received from the incoming serial data.
Bit 7 of this register is received as Sa6 bit in Frame 2 of the CRC-
4 Multi-frame. Bit 6 of this register is transmitted as Sa6 bit in
Frame 4 of the CRC-4 Multi-frame, etc.
Receive Sa7 Register (RSA7R) (Indirect Address = 0xn0H, 0x3EH)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Receive Sa7 Bit[7:0]
R
0
0
0
0
0
0
0
0
140
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-0
Receive Sa7 Bit[7:0]
R/W
Receive Sa7 bit[7:0]:
These Read/Write bit fields store contents of the Sa7 bits
received from the incoming serial data.
Bit 7 of this register is received as Sa7 bit in Frame 2 of the CRC-
4 Multi-frame. Bit 6 of this register is transmitted as Sa7 bit in
Frame 4 of the CRC-4 Multi-frame, etc.
Receive Sa8 Register (RSA8R) (Indirect Address = 0xn0H, 0x3FH)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Receive Sa8 Bit[7:0]
R
0
0
0
0
0
0
0
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-0
Receive Sa8 Bit[7:0]
R/W
Receive Sa8 bit[7:0]:
These Read/Write bit fields store contents of the Sa8 bits
received from the incoming serial data.
Bit 7 of this register is received as Sa8 bit in Frame 2 of the CRC-
4 Multi-frame. Bit 6 of this register is transmitted as Sa8 bit in
Frame 4 of the CRC-4 Multi-frame, etc.
Transmit Channel Control Register (RCCR) (Indirect Address = 0xn02H, 0x00H - 0x1FH)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
LAPD Select LAPD Select
Bit 1 Bit 0
Transmit Zero Code
Suppression Select Bit [1:0]
(T1 Mode Only)
Transmit Conditioning Select Bit [3:0]
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
1
0
141
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-6
LAPD Select Bit [1:0]
R/W
LAPD Select Bit [1:0]:
When these bits are set to 00:
The first LAPD channel is used as data source for D or E time
slot.
When these bits are set to 01:
The second LAPD channel is used as data source for D or E
time slot.
When these bits are set to 10:
In T1 mode, the Transmit D/E Timeslot Source Select bits
(TxDE[1:0]) of the Transmit Data Link Select Register (TSDLSR)
will determine the data source for D/E time slot.
In E1 mode, the Transmit Signaling and Data Link Source Select
bits (TxSIGDL[2:0]) of the Transmit Data Link Select Register
(TSDLSR) will determine the data source for D/E time slot.
When these bits are set to 11:
The third LAPD channel is used as data source for D or E time
slot.
5-4
Transmit Zero Code
Suppression Select
{T1 Mode Only}
R/W
Transmit Zero Code Suppression Select:
When these bits are set to 00:
The input DS1 PCM data of this DS0 channel is unchanged. No
zero code suppression is used.
When these bits are set to 01:
AT&T Bit 7 stuffing is used and the input DS1 PCM data of this
DS0 channel is modified.
When these bits are set to 10:
GTE zero code suppression is and the input DS1 PCM data of
this DS0 channel is modified.
When these bits are set to 11:
DDS zero code suppression is and the input DS1 PCM data of
this DS0 channel is modified.
142
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3-0
Transmit Conditioning
Select
R/W
Transmit Conditioning Select:
When these bits are set to 0000:
The input DS1 PCM data of this DS0 channel is unchanged.
When these bits are set to 0001:
All 8 bits of the input DS1 PCM data of this DS0 channel are
inverted.
When these bits are set to 0010:
The even bits of the input DS1 PCM data of this DS0 channel are
inverted.
When these bits are set to 0011:
The odd bits of the input DS1 PCM data of this DS0 channel are
inverted.
When these bits are set to 0100:
The input DS1 PCM data of this DS0 channel are replaced by
the octet stored in User IDLE Code Register (UCR).
When these bits are set to 0101:
The input DS1 PCM data of this DS0 channel are replaced by
BUSY code (0x7F).
When these bits are set to 0110:
The input DS1 PCM data of this DS0 channel are replaced by
VACANT code (0xFF).
When these bits are set to 0111:
The input DS1 PCM data of this DS0 channel are replaced by
BUSY_TS code (111xxxxx).
When these bits are set to 1000:
The input DS1 PCM data of this DS0 channel are replaced by
MUX-Out-Of-Frame (MOOF) code with value 0x1A.
When these bits are set to 1001:
The input DS1 PCM data of this DS0 channel are replaced by
the A-law digital milliwatt pattern.
When these bits are set to 1010:
The input DS1 PCM data of this DS0 channel are replaced by
the u-law digital milliwatt pattern.
When these bits are set to 1011:
The MSB bit of the input DS1 PCM data of this DS0 channel is
inverted.
When these bits are set to 1100:
All bits of the input DS1 PCM data of this DS0 channel except
MSB bit are inverted.
When these bits are set to 1101:
The input DS1 PCM data of this DS0 channel are replaced by
PRBS pattern created by the internal PRBS Generator of
XRT84L38 framer.
When these bits are set to 1110:
The input DS1 PCM data of this DS0 channel is unchanged.
When these bits are set to 1111:
This channel is configured as D or E timeslot.
143
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
User IDLE Code Register (UCR) (Indirect Address = 0xn02H, 0x20H - 0x3FH)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
User IDLE Code Bit [7:0]
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-0
User IDLE Code
R/W
User IDLE Code:
These READ/WRITE bit-fields permits the user store any value
of IDLE code into the framer. When the Transmit Data Condition-
ing Select [3:0] bits of TCCR register of a particular DS0 channel
are set to 0100, the input E1 PCM data are replaced by contents
of this register and sent to the Transmit LIU Interface.
Transmit Signaling Control Register (TSCR) (Indirect Address = 0xn2H, 0x40H - 0x57H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Signaling Bit Signaling Bit Signaling Bit Signaling Bit
Reserved
Robbed-bit
Signaling
Enable
Transmit
Robbed-bit
Signaling
Source
Transmit
Robbed-bit
Signaling
Source
A
B
C
D
Control Bit 1 Control Bit 0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Signaling Bit A
Signaling Bit B
Signaling Bit C
Signaling Bit D
R/W
R/W
R/W
R/W
Signaling Bit A:
This bit is used to store Signaling Bit A that is sent as the least
significant bit of timeslot of frame number 6.
6
5
4
Signaling Bit B:
This bit is used to store Signaling Bit B that is sent as the least
significant bit of timeslot of frame number 12.
Signaling Bit C:
This bit is used to store Signaling Bit C that is sent as the least
significant bit of timeslot of frame number 18.
Signaling Bit D:
This bit is used to store Signaling Bit D that is sent as the least
significant bit of timeslot of frame number 24.
144
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
2
Robbed-bit Signaling
Enable
R/W
Robbed-bit Signaling Enable:
When these bits are set to 0:
Robbed-bit Signaling is disabled. No signaling data will be
inserted into the input PCM data no matter what the setting of
the Transmit Signaling Source Select [1:0] bits is.
When these bits are set to 1:
Signaling data is enabled and inserted into the input DS1 PCM
data according to setting of the Transmit Signaling Source Select
[1:0] bits.
1-0
Transmit Signaling
Source Select
R/W
Transmit Signaling Source Select:
When these bits are set to 00:
None of the signaling data, the CAS Multi-frame alignment pat-
tern, the X bit or the CAS Multi-frame Yellow Alarm bit Y is
inserted into the outgoing E1 PCM data by the framer. However,
the user can embed the signaling data, the CAS Multi-frame
alignment pattern, the X bit or the CAS Multi-frame Yellow Alarm
bit Y into E1 PCM data before routing the PCM data into the
framer.
When these bits are set to 01:
The signaling data, the CAS Multi-frame alignment pattern, the X
bit or the CAS Multi-frame Yellow Alarm bit Y is inserted into the
outgoing E1 PCM data from TSCR register of each timeslot.
When these bits are set to 10:
If the XRT84L38 framer is operating in E1 2.048Mbit/s mode and
if the TxFR2048 bit of the Transmit Interface Control Register
(TICR) is set to zero:
The signaling data, the CAS Multi-frame alignment pattern, the X
bit or the CAS Multi-frame Yellow Alarm bit Y is inserted into the
outgoing E1 PCM data from the TxOH_n input pin.
If the XRT84L38 framer is operating in E1 2.048Mbit/s mode and
if the TxFR2048 bit of the Transmit Interface Control Register
(TICR) is set to one:
The signaling data, the CAS Multi-frame alignment pattern, the X
bit or the CAS Multi-frame Yellow Alarm bit Y is inserted into the
outgoing E1 PCM data from the TxSig_n input pin.
When these bits are set to 11:
No signaling data or the CAS Multi-frame alignment pattern is
inserted into the input E1 PCM data by the framer. However, the
user can embed signaling data into E1 PCM data before routing
the PCM data into the framer.
The X bit is inserted into the outgoing E1 PCM data from TSCR
register.
The CAS Multi-frame Yellow Alarm Y bit is generated by the
XRT84L38 framer depends on operating condition of the E1 link.
145
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
Receive Channel Control Register (RCCR) (Indirect Address = 0xn2H, 0x60H - 0x7FH)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Receive
LAPD
Channel
Select Bit 1
Receive
LAPD
Channel
Select Bit 0
Receive Zero Code
Suppression Select Bit [1:0]
(T1 Mode Only)
Receive Conditioning Select Bit [3:0]
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
1
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-6
Receive LAPD Channel
Select [1:0]
Receive LAPD Channel Select Bit [1:0]:
When these bits are set to 00:
The first LAPD channel is used as data destination for D or E
time slot.
When these bits are set to 01:
The second LAPD channel is used as data destination for D or E
time slot.
When these bits are set to 10:
In T1 mode, the Transmit D/E Timeslot Source Select bits
(TxDE[1:0]) of the Transmit Data Link Select Register (TSDLSR)
will determine the data destination for D/E time slot.
In E1 mode, the Transmit Signaling and Data Link Source Select
bits (TxSIGDL[2:0]) of the Transmit Data Link Select Register
(TSDLSR) will determine the data destination for D/E time slot.
When these bits are set to 11:
The third LAPD channel is used as data destination for D or E
time slot.
6
Reserved
5-4
Receive Zero Code
Suppression Select
{T1 Mode Only}
R/W
Receive Zero Code Suppression Select:
When these bits are set to 00:
The received DS1 PAYLOAD data of this DS0 channel is
unchanged. No zero code suppression is used.
When these bits are set to 01:
AT&T Bit 7 stuffing is used.
When these bits are set to 10:
GTE zero code suppression is used.
When these bits are set to 11:
DDS zero code suppression is used.
146
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3-0
Receive Conditioning
Select
R/W
Receive Conditioning Select:
When these bits are set to 0000:
The received DS1 payload data of this DS0 channel is
unchanged.
When these bits are set to 0001:
All 8 bits of the input DS1 payload data of this DS0 channel are
inverted.
When these bits are set to 0010:
The even bits of the input DS1 payload data of this DS0 channel
are inverted.
When these bits are set to 0011:
The odd bits of the input DS1 payload data of this DS0 channel
are inverted.
When these bits are set to 0100:
The input DS1 payload data of this DS0 channel are replaced by
the octet stored in User IDLE Code Register (UCR).
When these bits are set to 0101:
The input DS1 payload data of this DS0 channel are replaced by
BUSY code (0x7F).
When these bits are set to 0110:
The input DS1 payload data of this DS0 channel are replaced by
VACANT code (0xFF).
When these bits are set to 0111:
The input DS1 payload data of this DS0 channel are replaced by
BUSY_TS code (111xxxxx).
When these bits are set to 1000:
The input DS1 payload data of this DS0 channel are replaced by
MUX-Out-Of-Frame (MOOF) code with value 0x1A.
When these bits are set to 1001:
The input DS1 payload data of this DS0 channel are replaced by
the A-law digital milliwatt pattern.
When these bits are set to 1010:
The input DS1 payload data of this DS0 channel are replaced by
the u-law digital milliwatt pattern.
When these bits are set to 1011:
The MSB bit of the input DS1 payload data of this DS0 channel
is inverted.
When these bits are set to 1100:
All bits of the input DS1 payload data of this DS0 channel except
MSB bit are inverted.
When these bits are set to 1101:
The input DS1 payload data of this DS0 channel are replaced by
PRBS pattern created by the internal PRBS Generator of
XRT84L38 framer.
When these bits are set to 1110:
The input DS1 payload data of this DS0 channel is unchanged.
When these bits are set to 1111:
This channel is configured as D or E timeslot.
147
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
Receive User IDLE Code Register (UCR) (Indirect Address = 0xn02H, 0x80H - 0x97H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Receive User IDLE Code Bit [7:0]
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-0
Receive User IDLE Code
R/W
Receive User IDLE Code:
These READ/WRITE bit-fields permits the user store any value
of IDLE code into the framer. When the Receive Data Condition-
ing Select [3:0] bits of RCCR register of a particular DS0 channel
are set to 0100, the received DS1 payload data are replaced by
contents of this register and sent to the Terminal Equipment.
Receive Signaling Control Register (RSCR) (Indirect Address = 0xn2H, 0xA0H - 0xB7H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Reserved
Receive
Signaling
Substitution
Enable
Receive
Signaling
Output
De-bounce
Enable
Receive
Signaling
Substitution
Receive
Signaling
Signaling
Extraction
Signaling
Extraction
Substitution Control Bit 1 Control Bit 0
Enable
Control Bit 1 Control Bit 0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
6
Reserved
Receive Signaling
Substitution Enable
R/W
Receive Signaling Substitution Enable:
When this bit is set to 0:
Signaling Substitution is disabled. The XRT84L38 framer will not
replace extracted signaling bits from the incoming DS1 payload
data with all ones or with signaling bits stored in RSSR registers.
When this bit is set to 1:
Signaling Substitution is enabled. The XRT84L38 framer will
replace extracted signaling bits from the incoming DS1 payload
data with all ones or with signaling bits stored in RSSR registers.
148
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
5
Receive Signaling
Output Enable
R/W
Receive Signaling Output Enable:
When these bits are set to 0:
The XRT84L38 framer will not send extracted signaling bits from
the incoming DS1 payload data to external equipment through
the Receive Signaling Output pin (RxSig_n).
When these bits are set to 1:
The XRT84L38 framer will send extracted signaling bits from the
incoming DS1 payload data to external equipment through the
Receive Signaling Output pin (RxSig_n).
4
3-2
Receive Signaling
Substitution Control
R/W
Receive Signaling Substitution Control:
When these bits are set to 00:
The received signaling bits are replaced by all ones and send to
the external equipment.
When these bits are set to 01:
Two-code signaling substitution is applied to the received signal-
ing bits. The replaced signaling information is sent to the exter-
nal equipment.
When these bits are set to 10:
Four-code signaling substitution is applied to the received signal-
ing bits. The replaced signaling information is sent to the exter-
nal equipment.
When these bits are set to 11:
Sixteen-code signaling substitution is applied to the received sig-
naling bits. The replaced signaling information is sent to the
external equipment.
NOTE: In SF mode, this option is disabled.
1-0
Signaling Extraction
Control
R/W
Signaling Extraction Control:
When these bits are set to 00:
The XRT84L38 framer does not extract signaling information
from incoming DS1 payload data.
When these bits are set to 01:
The XRT84L38 framer extracts sixteen-code signaling informa-
tion from incoming DS1 payload data.
When these bits are set to 10:
The XRT84L38 framer extracts four-code signaling information
from incoming DS1 payload data.
When these bits are set to 11:
The XRT84L38 framer extracts two-code signaling information
from incoming DS1 payload data.
149
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
Receive Substitution Signaling Register (RSSR) (Indirect Address = 0xn02H, 0xC0H - 0xD7H)
7-4
3
Reserved
R/W
SIG16-A
SIG4-A
SIG2-A
Sixteen-Code Signaling bit A
Four-Code Signaling bit A
Two-Code Signaling bit A
2
1
0
SIG16-B
SIG4-B
SIG2-A
Sixteen-Code Signaling bit B
Four-Code Signaling bit B
Two-Code Signaling bit A
SIG16-C
SIG4-A
SIG2-A
Sixteen-Code Signaling bit C
Four-Code Signaling bit A
Two-Code Signaling bit A
SIG16-D
SIG4-B
SIG2-A
Sixteen-Code Signaling bit D
Four-Code Signaling bit B
Two-Code Signaling bit A
Receive Signaling Register Array (RSRA)(Indirect Address = 0xn4H, 0x00H - 0x17H)
3
Signaling Bit A
R/W
Signaling Bit A:
This bit is used to store Signaling Bit A that is received and
extracted as the least significant bit of timeslot of frame number
6.
2
Signaling Bit B
R/W
Signaling Bit B:
This bit is used to store Signaling Bit B that is received and
extracted as the least significant bit of timeslot of frame number
12.
1
0
Signaling Bit C
Signaling Bit D
R/W
R/W
Signaling Bit C:
This bit is used to store Signaling Bit C that is received and
extracted as the least significant bit of timeslot of frame number
18.
Signaling Bit D:
This bit is used to store Signaling Bit D that is received and
extracted as the least significant bit of timeslot of frame number
24.
BIT 7
BIT 6
BIT 5
BIT 4
Receive
BIT3
BIT 2
BIT 1
BIT 0
PRBS Type
Select
Error
Insertion
Data
Inversion
Select
Receive
Transmit
Receive DS1/ Transmit DS1/
E1 Framer
Bypassed
PRBS Lock PRBS Block PRBS Block
Indication
E1 Framer
Bypassed
Enable
R/W
0
Enable
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
150
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
Block Interrupt Enable Register (BIER) (Indirect Address = 0xnAH, 0x00H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
SA6 Interrupt Loop-back
Receive
Clock Loss
Interrupt
One Second
Interrupt
HDLC
Controller
Interrupt
Slip Buffer
Interrupt
Alarm and T1/E1 Framer
Code
Interrupt
Error Interrupt
Interrupt
R
0
R
0
R
0
R
0
R
0
R
0
R
0
R
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
SA6 Interrupt
R
R
R
R
R
R
SA6 Interrupt:
When this bit is set to 0:
No SA6 interrupt is generated.
When this bit is set to 1:
An SA6 Interrupt is generated.
6
5
4
3
2
Loop-back Code Interrupt
Loop-back Code Interrupt:
When this bit is set to 0:
No Loop-back Code interrupt is generated.
When this bit is set to 1:
A Loop-back Code Interrupt is generated.
Receive Clock Loss Inter-
rupt
Receive Clock Loss Interrupt:
When this bit is set to 0:
No Receive Clock Loss interrupt is generated.
When this bit is set to 1:
A Receive Clock Loss Interrupt is generated.
One Second Interrupt
HDLC Controller Interrupt
Slip Buffer Interrupt
One Second Interrupt:
When this bit is set to 0:
No One Second interrupt is generated.
When this bit is set to 1:
A One Second Interrupt is generated.
HDLC Controller Interrupt:
When this bit is set to 0:
No HDLC Controller interrupt is generated.
When this bit is set to 1:
A HDLC Controller Interrupt is generated.
Slip Buffer Interrupt:
When this bit is set to 0:
No T1/E1 Framer interrupt is generated.
When this bit is set to 1:
A Slip Buffer Interrupt is generated.
151
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1
Alarm and Error Interrupt
R
Alarm and Error Interrupt:
When this bit is set to 0:
No Alarm and Error interrupt is generated.
When this bit is set to 1:
An Alarm and Error Interrupt is generated.
0
T1/E1 Framer Interrupt
R
T1/E1 Framer Interrupt:
When this bit is set to 0:
No T1/E1 Framer interrupt is generated.
When this bit is set to 1:
A T1/E1 Framer Interrupt is generated.
Block Interrupt Enable Register (BIER) (Indirect Address = 0xnAH, 0x01H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
SA6 Interrupt Loop-back
Receive
Clock Loss
Interrupt
Enable
One Second
Interrupt
HDLC
Controller
Interrupt
Enable
Slip Buffer
Interrupt
Enable
Alarm and T1/E1 Framer
Enable
Code
Interrupt
Enable
Error
Interrupt
Enable
Interrupt
Enable
Enable
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
SA6 Interrupt Enable
R
R
R
SA6 Interrupt Enable:
When this bit is set to 0:
Every interrupt generated by the Receive SA6 Interrupt Register
(RSAIR) is disabled.
When this bit is set to 1:
Every interrupt generated by the Receive SA6 Interrupt Register
(RSAIR) enabled.
6
Loop-back Code Interrupt
Enable
Loop-back Code Interrupt Enable:
When this bit is set to 0:
Every interrupt generated by the Receive Loop-back Code Inter-
rupt and Status Register (RLCISR) is disabled.
When this bit is set to 1:
Every interrupt generated by the Receive Loop-back Code Inter-
rupt and Status Register (RLCISR) enabled.
5
Receive Clock Loss
Interrupt Enable
Receive Clock Loss Interrupt Enable:
When this bit is set to 0:
The Receive Clock Loss Interrupt is disabled.
When this bit is set to 1:T
he Receive Clock Loss Interrupt is enabled.
152
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
4
One Second Interrupt
Enable
R
One Second Interrupt Enable:
When this bit is set to 0:
One Second Interrupt is disabled.
When this bit is set to 1:
One Second Interrupt is enabled.
3
2
1
0
HDLC Controller Interrupt
Enable
R
R
R
R
HDLC Controller Interrupt Enable:
When this bit is set to 0:
Every interrupt generated by the Data Link Status Register
(DLSR) is disabled.
When this bit is set to 1:
Every interrupt generated by the Data Link Status Register
(DLSR) is enabled.
Slip Buffer Interrupt
Enable
Slip Buffer Interrupt Enable:
When this bit is set to 0:
Every interrupt generated by the Slip Buffer Status Register
(SBSR) is disabled.
When this bit is set to 1:
Every interrupt generated by the Slip Buffer Status Register
(SBSR) is enabled.
Alarm and Error Interrupt
Enable
Alarm and Error Interrupt Enable:
When this bit is set to 0:
Every interrupt generated by the Alarm and Error Interrupt Sta-
tus Register (AEISR) is disabled.
When this bit is set to 1:
Every interrupt generated by the Alarm and Error Interrupt Sta-
tus Register (AEISR) is enabled.
T1/E1 Framer Interrupt
Enable
T1/E1 Framer Interrupt Enable:
When this bit is set to 0:
Every interrupt generated by the T1/E1 Framer Interrupt Status
Register (FISR) is disabled.
When this bit is set to 1:
Every interrupt generated by the T1/E1 Framer Interrupt Status
Register (FISR) is enabled.
Alarm and Error Status Register (AESR) - T1 Mode (Indirect Address = 0xnAH, 0x02H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Receive Red Receive AIS
Receive
Yellow Alarm
State
Receive Loss
of Signal
Receive
Bipolar
Violation
Receive Red Receive AIS
Alarm State State Change Yellow Alarm
Change
Receive
Alarm State
State
Change
State Change
State Change
R
0
R
0
R
0
RUR / WC
0
RUR / WC
0
RUR / WC
0
RUR / WC
0
RUR / WC
0
153
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
6
5
4
3
2
Receive Red Alarm State
R
Receive Red Alarm State:
When this bit is 0:
There is no Red Alarm condition detected in the incoming DS1
payload data.
When this bit is 1:
There is Red Alarm condition detected in the incoming DS1 pay-
load data.
Receive AIS State
R
Receive AIS State:
When this bit is 0:
There is no AIS alarm condition detected in the incoming DS1
payload data.
When this bit is 1:
There is AIS alarm condition detected in the incoming DS1 pay-
load data.
Receive Yellow Alarm
State
R
Receive Yellow Alarm State:
When this bit is 0:
There is no Yellow Alarm condition detected in the incoming DS1
payload data.
When this bit is 1:
There is Yellow Alarm condition detected in the incoming DS1
payload data.
Receive Loss of Signal
Change
RUR /
WC
Receive Loss of Signal:
When this bit is 0:
There is no change of Loss of Signal state in the incoming DS1
payload data.
When this bit is 1:
There is change of Loss of Signal state in the incoming DS1 pay-
load data.
Receive Bipolar Violation
State Change
RUR /
WC
Receive Bipolar Violation:
When this bit is 0:
There is no change of Bipolar Violation state in the incoming
DS1 payload data.
When this bit is 1:
There is change of Bipolar Violation state in the incoming DS1
payload data.
Receive Red Alarm State
Change
RUR /
WC
Receive Red Alarm State Change:
When this bit is 0:
There is no change of Red Alarm state in the incoming DS1 pay-
load data.
When this bit is 1:
There is change of Red Alarm state in the incoming DS1 payload
data.
154
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1
Receive AIS State
Change
RUR /
WC
Receive AIS State Change:
When this bit is 0:
There is no change of AIS state in the incoming DS1 payload
data.
When this bit is 1:
There is change of AIS state in the incoming DS1 payload data.
0
Receive Yellow Alarm
State Change
RUR /
WC
Receive Yellow Alarm State Change:
When this bit is 0:
There is no change of Yellow Alarm state in the incoming DS1
payload data.
When this bit is 1:
There is change of Yellow Alarm state in the incoming DS1 pay-
load data.
Alarm and Error Status Register (AESR) - E1 Mode (Indirect Address = 0xnAH, 0x02H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Receive Red Receive AIS Receive CAS Receive Loss
Receive
Bipolar
Violation
Receive Red Receive AIS
Alarm State State Change Yellow Alarm
Change
Receive
Alarm State
State
Multi-frame
Yellow Alarm
State Change
of Signal
Change
State Change
State Change
R
0
R
0
RUR / WC
0
RUR / WC
0
RUR / WC
0
RUR / WC
0
RUR / WC
0
RUR / WC
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Receive Red Alarm State
R
Receive Red Alarm State:
When this bit is 0:
There is no Red Alarm condition detected in the incoming DS1
payload data.
When this bit is 1:
There is Red Alarm condition detected in the incoming DS1 pay-
load data.
6
Receive AIS State
R
Receive AIS State:
When this bit is 0:
There is no AIS alarm condition detected in the incoming DS1
payload data.
When this bit is 1:
There is AIS alarm condition detected in the incoming DS1 pay-
load data.
155
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
5
4
3
2
Receive CAS Multi-frame
Yellow Alarm State
Change
RUR /
WC
Receive CAS Multi-frame Yellow Alarm State Change:
When this bit is 0:
There is no change of CAS Multi-frame Yellow Alarm state in the
incoming E1 payload data.
When this bit is 1:
There is change of CAS Multi-frame Yellow Alarm state in the
incoming E1 payload data.
Receive Loss of Signal
Change
RUR /
WC
Receive Loss of Signal:
When this bit is 0:
There is no change of Loss of Signal state in the incoming DS1
payload data.
When this bit is 1:
There is change of Loss of Signal state in the incoming DS1 pay-
load data.
Receive Bipolar Violation
State Change
RUR /
WC
Receive Bipolar Violation:
When this bit is 0:
There is no change of Bipolar Violation state in the incoming
DS1 payload data.
When this bit is 1:
There is change of Bipolar Violation state in the incoming DS1
payload data.
Receive Red Alarm State
Change
RUR /
WC
Receive Red Alarm State Change:
When this bit is 0:
There is no change of Red Alarm state in the incoming DS1 pay-
load data.
When this bit is 1:
There is change of Red Alarm state in the incoming DS1 payload
data.
1
0
Receive AIS State
Change
RUR /
WC
Receive AIS State Change:
When this bit is 0:
There is no change of AIS state in the incoming DS1 payload
data.
When this bit is 1:
There is change of AIS state in the incoming DS1 payload data.
Receive Yellow Alarm
State Change
RUR /
WC
Receive Yellow Alarm State Change:
When this bit is 0:
There is no change of Yellow Alarm state in the incoming DS1
payload data.
When this bit is 1:
There is change of Yellow Alarm state in the incoming DS1 pay-
load data.
156
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
Alarm and Error Interrupt Enable Register (AEIER) - T1 Mode (Indirect Address = 0xnAH, 0x03H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Reserved
Receive Loss
of Signal
Change
Receive
Bipolar
Violation
State Change
Interrupt
Enable
Receive Red Receive AIS
Alarm State State Change Yellow Alarm
Receive
Change
Interrupt
Enable
Interrupt
Enable
State Change
Interrupt
Interrupt
Enable
Enable
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
0
0
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-5
4
Reserved
Receive Loss of Signal
Interrupt Enable
R/W
R/W
R/W
Receive Loss of Signal Interrupt Enable:
When this bit is set to 0:
The Receive Loss of Signal interrupt is disabled. Occurrence of
Loss of Signals will not generate an interrupt.
When this bit is set to 1:
The Receive Loss of Signal interrupt is enabled. Occurrence of
Loss of Signals will generate an interrupt.
3
Receive Bipolar Violation
Interrupt Enable
Receive Bipolar Violation Interrupt Enable:
When this bit is set to 0:
The Receive Bipolar Violation interrupt is disabled. Occurrence
of one or more bipolar violations will not generate an interrupt.
When this bit is set to 1:
The Receive Bipolar Violation interrupt is enabled. Occurrence
of one or more bipolar violations will generate an interrupt.
2
Receive Red Alarm State
Change Interrupt Enable
Receive Red Alarm State Change Interrupt Enable:
When this bit is set to 0:
The Receive Red Alarm State Change interrupt is disabled. No
Receive Loss of Frame (RxLOF) interrupt will be generated upon
detection of LOF condition.
When this bit is set to 1:
The Receive Red Alarm State Change interrupt is enabled.
Receive Loss of Frame (RxLOF) interrupt will be generated upon
detection of LOF condition.
1
Receive AIS State
Change Interrupt Enable
R/W
Receive AIS State Change Interrupt Enable:
When this bit is set to 0:
The Receive AIS State Change interrupt is disabled.
When this bit is set to 1:
The Receive AIS State Change interrupt is enabled.
157
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
0
Receive Yellow Alarm
State Change Interrupt
Enable
R/W
Receive Yellow Alarm State Change Interrupt Enable:
When this bit is set to 0:
The Receive Yellow Alarm State Change interrupt is disabled.
Any state change of Receive Yellow Alarm will not generate an
interrupt.
When this bit is set to 1:
The Receive Yellow Alarm State Change interrupt is enabled.
Any state change of Receive Yellow Alarm will generate an inter-
rupt.
Alarm and Error Interrupt Enable Register (AEIER) - E1 Mode (Indirect Address = 0xnAH, 0x03H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Reserved
Receive CAS Receive Loss
Receive
Bipolar
Violation
State Change
Interrupt
Enable
Receive Red Receive AIS
Alarm State State Change Yellow Alarm
Receive
Multi-frame
Yellow Alarm
State Change
Interrupt
of Signal
Change
Interrupt
Enable
Change
Interrupt
Enable
Interrupt
Enable
State Change
Interrupt
Enable
Enable
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
0
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-6
5
Reserved
Receive CAS Multi-frame
Yellow Alarm State
R/W
Receive CAS Multi-frame Yellow Alarm State Change Inter-
rupt Enable:
Change Interrupt Enable
When this bit is set to 0:
The Receive CAS Multi-frame Yellow Alarm State Change inter-
rupt is disabled. Any state change of Receive CAS Multi-frame
Yellow Alarm will not generate an interrupt.
When this bit is set to 1:
The Receive CAS Multi-frame Yellow Alarm State Change inter-
rupt is enabled. Any state change of Receive CAS Multi-frame
Yellow Alarm will generate an interrupt.
4
Receive Loss of Signal
Interrupt Enable
R/W
Receive Loss of Signal Interrupt Enable:
When this bit is set to 0:
The Receive Loss of Signal interrupt is disabled. Occurrence of
Loss of Signals will not generate an interrupt.
When this bit is set to 1:
The Receive Loss of Signal interrupt is enabled. Occurrence of
Loss of Signals will generate an interrupt.
158
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3
Receive Bipolar Violation
Interrupt Enable
R/W
Receive Bipolar Violation Interrupt Enable:
When this bit is set to 0:
The Receive Bipolar Violation interrupt is disabled. Occurrence
of one or more bipolar violations will not generate an interrupt.
When this bit is set to 1:
The Receive Bipolar Violation interrupt is enabled. Occurrence
of one or more bipolar violations will generate an interrupt.
2
Receive Red Alarm State
Change Interrupt Enable
R/W
Receive Red Alarm State Change Interrupt Enable:
When this bit is set to 0:
The Receive Red Alarm State Change interrupt is disabled. No
Receive Loss of Frame (RxLOF) interrupt will be generated upon
detection of LOF condition.
When this bit is set to 1:
The Receive Red Alarm State Change interrupt is enabled.
Receive Loss of Frame (RxLOF) interrupt will be generated upon
detection of LOF condition.
1
0
Receive AIS State
Change Interrupt Enable
R/W
R/W
Receive AIS State Change Interrupt Enable:
When this bit is set to 0:
The Receive AIS State Change interrupt is disabled.
When this bit is set to 1:
The Receive AIS State Change interrupt is enabled.
Receive Yellow Alarm
State Change Interrupt
Enable
Receive Yellow Alarm State Change Interrupt Enable:
When this bit is set to 0:
The Receive Yellow Alarm State Change interrupt is disabled.
Any state change of Receive Yellow Alarm will not generate an
interrupt.
When this bit is set to 1:
The Receive Yellow Alarm State Change interrupt is enabled.
Any state change of Receive Yellow Alarm will generate an inter-
rupt.
Framer Interrupt Status Register (FISR) (Indirect Address = 0xnAH, 0x04H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
CAS
Multi-frame
Alignment
Changed (E1
Only)
National Bit
Updated
(E1 Only)
Signaling
Updated
Frame
Alignment
Changed
Framer
In-frame
State
Frame Mimic Synchroniza- Framing Error
State
tion Bit Error
Changed
RUR / WC
0
RUR / WC
0
RUR / WC
0
RUR / WC
0
RUR / WC
0
RUR / WC
0
RUR / WC
0
RUR / WC
0
159
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
6
5
4
3
CAS Multi-frame
Alignment Changed
(E1 Only)
RUR /
WC
CAS Multi-frame Alignment Changed:
When this bit is 0:
There is no change of CAS Multi-frame Alignment in the incom-
ing E1 payload data.
When this bit is 1:
There is change of CAS Multi-frame Alignment in the incoming
E1 payload data.
National Bit Updated
(E1 Only)
RUR /
WC
National Bit Updated:
When this bit is 0:
There is no change of National Bits in the incoming E1 payload
data.
When this bit is 1:
There is change of National Bits in the incoming E1 payload
data.
Signaling Updated
RUR /
WC
Signaling Updated:
When this bit is 0:
There is no change of signaling information in the incoming DS1/
E1 payload data.
When this bit is 1:
There is change of signaling information in the incoming DS1/E1
payload data.
Frame Alignment
Changed
RUR /
WC
Frame Alignment Changed:
When this bit is 0:
There is no change of Frame Alignment in the incoming DS1/E1
payload data.
When this bit is 1:
There is change of Frame Alignment in the incoming DS1/E1
payload data.
Framer In-frame State
RUR /
WC
Framer In-frame State:
When this bit is 0:
There is no change occur in the in-frame state in the incoming
DS1/E1 payload data. That is, if the framer is in-frame before,
then it is remained in-frame.
When this bit is 1:
There is change of in-frame state in the incoming DS1/E1 pay-
load data. That is, if the framer is in-frame before, then it is out-
of-frame now.
2
Frame Mimic State
Changed
RUR /
WC
Frame Mimic State Changed:
When this bit is 0:
There is no change Frame Mimic state in the incoming DS1/E1
payload data.
When this bit is 1:
There is change of Frame Mimic state in the incoming DS1/E1
payload data.
160
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1
Synchronization Bit Error
RUR /
WC
Synchronization Bit Error:
When this bit is 0:
There is no Synchronization Bit Error in the incoming DS1/E1
payload data.
When this bit is 1:
There is Synchronization Bit Error in the incoming DS1/E1 pay-
load data.
0
Framing Error
RUR /
WC
Framing Error:
When this bit is 0:
There is no Framing Error in the incoming DS1/E1 payload data.
When this bit is 1:
There is Framing Error in the incoming DS1/E1 payload data.
Framer Interrupt Enable Register (FIER) (Indirect Address = 0xnAH, 0x05H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
CAS
National Bit
Update
Interrupt
Enable
Signaling
Update
Interrupt
Enable
Frame
Alignment
Change
Interrupt
Enable
Framer
In-frame
State
Interrupt
Enable
Frame Mimic Synchroniza- Framing Error
Multi-frame
Alignment
Change
Interrupt
Enable
State Change tion Bit Error
Interrupt
Enable
Interrupt
Enable
Interrupt
Enable
(E1 Only)
(E1 Only)
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
CAS Multi-frame
RUR /
WC
CAS Multi-frame Alignment Changed Interrupt Enable:
When this bit is set to 0:
Alignment Change
Interrupt Enable
(E1 Only)
The CAS Multi-frame Alignment Change interrupt is disabled.
When this bit is set to 1:
The CAS Multi-frame Alignment Changed interrupt is enabled.
6
5
National Bit Update
Interrupt Enable
(E1 Only)
RUR /
WC
National Bit Updated Interrupt Enable:
When this bit is set to 0:
The National Bit Update interrupt is disabled.
When this bit is set to 1:
The National Bit Update interrupt is enabled.
Signaling Update
Interrupt Enable
RUR /
WC
Signaling Updated Interrupt Enable:
When this bit is set to 0:
The Signaling Update interrupt is disabled.
When this bit is set to 1:
The Signaling Update interrupt is enabled.
161
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
4
Frame Alignment Change
Interrupt Enable
RUR /
WC
Frame Alignment Changed Interrupt Enable:
When this bit is set to 0:
The Frame Alignment Change interrupt is disabled.
When this bit is set to 1:
The Frame Alignment Change interrupt is enabled.
3
2
Framer In-frame State
Interrupt Enable
RUR /
WC
Framer In-frame State Interrupt Enable:When this bit is set to
0:The Framer In-frame State interrupt is disabled. When this bit
is set to 1:The Framer In-frame State interrupt is enabled.
Frame Mimic State
Change Interrupt Enable
RUR /
WC
Frame Mimic State Changed Interrupt Enable:
When this bit is set to 0:
he Frame Mimic State Change interrupt is disabled.
When this bit is set to 1:
The Frame Mimic State Change interrupt is enabled.
1
0
Synchronization Bit Error
Interrupt Enable
RUR /
WC
Synchronization Bit Error Interrupt Enable:
When this bit is set to 0:
The Synchronization Bit Error interrupt is disabled.
When this bit is set to 1:
The Synchronization Bit Error interrupt is enabled.
Framing Error Interrupt
Enable
RUR /
WC
Framing Error Interrupt Enable:
When this bit is set to 0:
The Framing Error interrupt is disabled.
When this bit is set to 1:
The Framing Error interrupt is enabled.
Data Link Status Register (DLSR) (Indirect Address = 0xnAH, 0x06H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Message
Type
TransmitStart Receive Start Transmit End Receive End Frame Check
Receive
ABORT
Sequence
Receive IDLE
Flag
Sequence
of Transfer
of Transfer
of Transfer
of Transfer
Sequence
Error
Detection
RUR / WC
0
RUR / WC
0
RUR / WC
0
RUR / WC
0
RUR / WC
0
RUR / WC
0
RUR / WC
0
RUR / WC
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Message Type
RUR /
WC
Message Type:
When this bit is set to 0:
The Receive HDLC Controller receives and processes Bit-Ori-
ented Signaling (BOS) message.
When this bit is set to 1:
The Receive HDLC Controller receives and processes LAPD
protocol or Message-Oriented Signaling (MOS) message.
162
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
6
Transmit Start of Transfer
RUR /
WC
Transmit Start of Transfer:
When this bit is 0:
There is no data link message to be sent to the data link chan-
nel.
When this bit is 1:
The HDLC Controller will send a data link message to the data
link channel.
5
4
3
2
1
Receive Start of Transfer
Transmit End of Transfer
Receive End of Transfer
RUR /
WC
Receive Start of Transfer:
When this bit is 0:
There is no data link message in the data link channel.
When this bit is 1:
The HDLC Controller began to receive a data link message in
the data link channel.
RUR /
WC
Transmit End of Transfer:
When this bit is 0:
No data link message was sent to the data link channel.
When this bit is 1:
The HDLC Controller finished sending a data link message to
the data link channel.
RUR /
WC
Receive End of Transfer:
When this bit is 0:
No data link message was present in the data link channel.
When this bit is 1:
The HDLC Controller finished receiving a data link message in
the data link channel.
Frame Check Sequence
Error Detection
RUR /
WC
Frame Check Sequence Error Detection:
When this bit is 0:
There is no FCS error detected in the data link channel.
When this bit is 1:
The HDLC Controller receives an erroneous FCS in the data link
channel.
Receive ABORT
Sequence
RUR /
WC
Receive ABORT Sequence:
When this bit is 0:
There is no BOS ABORT sequence received in the data link
channel.
When this bit is 1:
The HDLC Controller receives MOS ABORT sequence in the
data link channel.
0
Receive IDLE Flag
Sequence
RUR /
WC
Receive IDLE Flag Sequence:
When this bit is 0:
The message received in the data link channel is BOS message.
When this bit is 1:
The message received in the data link channel is MOS mes-
sage.
163
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
Data Link Interrupt Enable Register (DLIER) (Indirect Address = 0xnAH, 0x07H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Reserve
TransmitStart Receive Start Transmit End Receive End Frame Check
Receive
ABORT
Sequence
Interrupt
Enable
Receive IDLE
Flag
Sequence
Interrupt
Enable
of Transfer
Interrupt
Enable
of Transfer
Interrupt
Enable
of Transfer
Interrupt
Enable
of Transfer
Interrupt
Enable
Sequence
Error
Detection
Interrupt
Enable
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
6
Reserved
Transmit Start of Transfer
Interrupt Enable
R/W
R/W
R/W
R/W
R/W
Transmit Start of Transfer Interrupt Enable:
When this bit is set to 0:
The Transmit Start of Transfer interrupt is disabled.
When this bit is set to 1:
The Transmit Start of Transfer interrupt is enabled.
5
4
3
2
Receive Start of Transfer
Interrupt Enable
Receive Start of Transfer Interrupt Enable:
When this bit is set to 0:
The Receive Start of Transfer interrupt is disabled.
When this bit is set to 1:
The Receive Start of Transfer interrupt is enabled.
Transmit End of Transfer
Interrupt Enable
Transmit End of Transfer Interrupt Enable:
When this bit is set to 0:
The Transmit End of Transfer interrupt is disabled.
When this bit is set to 1:
The Transmit End of Transfer interrupt is enabled.
Receive End of Transfer
Interrupt Enable
Receive End of Transfer Interrupt Enable:
When this bit is set to 0:
The Receive End of Transfer interrupt is disabled.
When this bit is set to 1:
The Receive End of Transfer interrupt is enabled.
Frame Check Sequence
Error Detection Interrupt
Enable
Frame Check Sequence Error Detection Interrupt Enable:
When this bit is set to 0:
The Frame Check Sequence Error Detection interrupt is dis-
abled.
When this bit is set to 1:
The Frame Check Sequence Error Detection interrupt is
enabled.
164
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1
Receive ABORT
Sequence Interrupt
Enable
R/W
Receive ABORT Sequence Interrupt Enable:
When this bit is set to 0:
The Receive ABORT Sequence interrupt is disabled.
When this bit is set to 1:
The Receive ABORT Sequence interrupt is enabled.
0
Receive IDLE Flag
Sequence Interrupt
Enable
R/W
Receive IDLE Flag Sequence Interrupt Enable:
When this bit is set to 0:
The Receive IDLE Flag Sequence interrupt is disabled.
When this bit is set to 1:
The Receive IDLE Flag Sequence interrupt is enabled.
Slip Buffer Status Register (SBSR) (Indirect Address = 0xnAH, 0x08H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Transmit Slip Transmit Slip Transmit Slip
SLC96 In
Multi-frame In Receive Slip Receive Slip Receive Slip
Buffer Full
Buffer Empty
Buffer Slip
Synchroniza- Synchroniza-
Buffer Full
Buffer Empty
Buffer Slip
tion
tion
RUR/WC
0
RUR/WC
0
RUR/WC
0
R
R
RUR/WC
0
RUR/WC
0
RUR/WC
0
0
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Transmit Slip Buffer Full
RUR/
WC
Transmit Slip Buffer Full:
When this bit is set to 0:
The Transmit Slip Buffer is not full.
When this bit is set to 1:
The Transmit Slip Buffer is full and one frame of data is dis-
carded.
6
5
Transmit Slip Buffer
Empty
RUR/
WC
Transmit Slip Buffer Empty:
When this bit is set to 0:
The Transmit Slip Buffer is not empty.
When this bit is set to 1:
The Transmit Slip Buffer is empty and one frame of data is
repeated.
Transmit Slip Buffer Slip
RUR/
WC
Transmit Slip Buffer Slip:
When this bit is set to 0:
The Transmit Slip Buffer does not slip.
When this bit is set to 1:
The Transmit Slip Buffer slips since either full or emptied.
165
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
4
3
2
SLC96 In Synchroniza-
tion
R
SLC96 In Synchronization:
When this bit is set to 0:
The framer is not in SLC96 Synchronization.
When this bit is set to 1:
The framer is in SLC96 Synchronization.
Multi-frame In Synchroni-
zation
R
Multi-frame In Synchronization:
When this bit is set to 0:
The framer is not in Multi-frame synchronization.
When this bit is set to 1:
The framer is in Multi-frame synchronization.
Receive Slip Buffer Full
RUR/
WC
Receive Slip Buffer Full:
When this bit is set to 0:
The Receive Slip Buffer is not full.
When this bit is set to 1:
The Receive Slip Buffer is full and one frame of data is dis-
carded.
1
0
Receive Slip Buffer
Empty
RUR/
WC
Receive Slip Buffer Empty:
When this bit is set to 0:
The Receive Slip Buffer is not empty.
When this bit is set to 1:
The Receive Slip Buffer is empty and one frame of data is
repeated.
Receive Slip Buffer Slip
RUR/
WC
Receive Slip Buffer Slip:
When this bit is set to 0:
The Receive Slip Buffer does not slip.
When this bit is set to 1:
The Receive Slip Buffer slips since either full or emptied.
Slip Buffer Interrupt Enable Register (SBIER) (Indirect Address = 0xnAH, 0x09H)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Transmit Slip Transmit Slip Transmit Slip
Reserved
Reserved
Receive Slip Receive Slip Receive Slip
Buffer Full
Interrupt
Enable
Buffer Empty
Interrupt
Buffer Slip
Interrupt
Enable
Buffer Full
Interrupt
Enable
Buffer Empty
Interrupt
Buffer Slip
Interrupt
Enable
Enable
Enable
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
166
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Transmit Slip Buffer Full
Interrupt Enable
R/W
Transmit Slip Buffer Full Interrupt Enable:
When this bit is set to 0:
The Transmit Slip Buffer Full interrupt is disabled.
When this bit is set to 1:
The Transmit Slip Buffer Full interrupt is enabled.
6
5
Transmit Slip Buffer
Empty Interrupt Enable
R/W
R/W
Transmit Slip Buffer Empty Interrupt Enable:
When this bit is set to 0:
The Transmit Slip Buffer Empty interrupt is disabled.
When this bit is set to 1:
The Transmit Slip Buffer Empty interrupt is enabled.
Transmit Slip Buffer Slip
Interrupt Enable
Transmit Slip Buffer Slip Interrupt Enable:
When this bit is set to 0:
The Transmit Slip Buffer Slip interrupt is disabled.
When this bit is set to 1:
The Transmit Slip Buffer slips Slip interrupt is enabled.
4-3
2
Reserved
Receive Slip Buffer Full
Interrupt Enable
R/W
R/W
Receive Slip Buffer Full Interrupt Enable:
When this bit is set to 0:
The Receive Slip Buffer Full interrupt is disabled.
When this bit is set to 1:
The Receive Slip Buffer Full interrupt is enabled.
1
0
Receive Slip Buffer
Empty Interrupt Enable
Receive Slip Buffer Empty Interrupt Enable:
When this bit is set to 0:
The Receive Slip Buffer Empty interrupt is disabled.
When this bit is set to 1:
The Receive Slip Buffer Empty interrupt is enabled.
Receive Slip Buffer Slip
Interrupt Enable
RUR/
WC
Receive Slip Buffer Slip Interrupt Enable:
When this bit is set to 0:
The Receive Slip Buffer Slip interrupt is disabled.
When this bit is set to 1:
The Receive Slip Buffer Slip interrupt is enabled.
167
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
Receive Loop-back Code Interrupt and Status Register (RLCISR) (Indirect Address = 0xnAH, 0x0AH)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Receive
Receive
CRC-4 to
CRC-4 to
Non-CRC-4
Receive
Loop-back
Code
Activation
Status
Receive
Loop-back
Code
De-Activation
Status
Receive
Loop-back
Code
Activation
Status
Receive
Loop-back
Code
De-Activation
Status
AUXP State AUXP State Non-CRC-4
Change
Interrupt
Inter-network- Inter-network-
ing Status
ing Status
Change
Interrupt
Change
Interrupt
Change
Interrupt
R
0
RUR/WC
0
R
0
RUR/WC
0
R
0
R
0
RUR/WC
0
RUR/WC
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Receive AUXP State
R
Receive AUXP State:
This bit indicates status of the Receive AUXP pattern.
When this bit is set to 0:
There is no AUXP pattern detected in the Receive data stream.
When this bit is set to 1:
There is AUXP pattern detected in the Receive data stream.
6
Receive AUXP State
Change Interrupt
RUR/
WC
Receive AUXP State Change Interrupt:
When this bit is set to 0:
There is no change in Receive AUXP pattern status.
When this bit is set to 1:
There is change in Receive AUXP pattern status. An interrupt
will be generated upon detection of the change in Receive AUXP
pattern.
5
4
CRC-4 to Non-CRC-4
Inter-networking Status
R
CRC-4 to Non-CRC-4 Inter-networking Status:
This bit indicates status of the CRC-4 Internetworking.
When this bit is set to 0:
There is no CRC-4 to non-CRC-4 internetworking established.
When this bit is set to 1:
There is CRC-4 to non-CRC-4 internetworking established.
CRC-4 to Non-CRC-4
Inter-networking Status
Change Interrupt
RUR/
WC
CRC-4 to Non-CRC-4 Inter-networking Status Change Inter-
rupt:
When this bit is set to 0:
There is no change in CRC-4 to Non-CRC-4 Inter-networking
Status.
When this bit is set to 1:
There is change in CRC-4 to Non-CRC-4 Inter-networking Sta-
tus. An interrupt will be generated upon detection of the change
in CRC-4 to Non-CRC-4 Inter-networking Status.
168
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3
Receive Loop-back Code
Activation Status
R
Receive Loop-back Code Activation Status:
This bit indicates status of the Receive Loop-back Code Activa-
tion.
When this bit is set to 0:
There is no Loop-back Activation code detected in the Receive
data stream.
When this bit is set to 1:
There is Loop-back Activation code detected in the Receive data
stream.
2
Receive Loop-back Code
De-Activation Status
R
Receive Loop-back Code De-activation Status:
This bit indicates status of the Receive Loop-back Code De-acti-
vation.
When this bit is set to 0:
There is no Loop-back De-activation code detected in the
Receive data stream.
When this bit is set to 1:
There is Loop-back De-activation code detected in the Receive
data stream.
1
Receive Loop-back Code
Activation Status Change
Interrupt
RUR/
WC
Receive Loop-back Code Activation Status Change Inter-
rupt:
When this bit is set to 0:
There is no change in Receive Loop-back Activation Code Sta-
tus.
When this bit is set to 1:
There is change in Receive Loop-back Activation Code Status.
An interrupt will be generated upon detection of the change in
Receive Loop-back Activation Code status.
0
Receive Loop-back Code
De-activation Status
Change Interrupt
RUR/
WC
Receive Loop-back Code De-activation Status Change Inter-
rupt:
When this bit is set to 0:
There is no change in Receive Loop-back De-activation Code
Status.
When this bit is set to 1:
There is change in Receive Loop-back De-activation Code Sta-
tus. An interrupt will be generated upon detection of the change
in Receive Loop-back De-activation Code status.
169
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
Receive Loop-back Code Enable Register (RLCER) (Indirect Address = 0xnAH, 0x0BH)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Reserved
Receive
AUXP State
Change
Interrupt
Enable
Reserved
CRC-4 to
Non-CRC-4
Inter-network-
ing Status
Change
Reserved
Reserved
Receive
Loop-back
Code
Activation
Status
Receive
Loop-back
Code De-
Activation
Status
Interrupt
Enable
Change
Interrupt
Enable
Change
Interrupt
Enable
R/W
0
R/W
0
R/W
0
R/W
0
0
0
0
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
6
Reserved
Receive AUXP State
Change Interrupt Enable
R/W
R/W
Receive AUXP State Change Interrupt Enable:
When this bit is set to 0:
The Receive AUXP State Change Interrupt is disabled.
When this bit is set to 1:
The Receive AUXP State Change Interrupt is enabled.
5
4
Reserved
CRC-4 to Non-CRC-4
Inter-networking Status
Change Interrupt Enable
CRC-4 to Non-CRC-4 Inter-networking Status Change Inter-
rupt Enable:
When this bit is set to 0:
The CRC-4 to Non-CRC-4 Inter-networking Status Change Inter-
rupt is disabled.
When this bit is set to 1:
The CRC-4 to Non-CRC-4 Inter-networking Status Change Inter-
rupt is enabled.
3
2
Reserved
Receive Loop-back Code
Activation Status Change
Interrupt Enable
R/W
Receive Loop-back Code Activation Status Change Inter-
rupt Enable:
When this bit is set to 0:
The Receive Loop-back Code Activation Status Change Inter-
rupt is disabled.
When this bit is set to 1:
The Receive Loop-back Code Activation Status Change Inter-
rupt is enabled.
1
Reserved
170
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
0
Receive Loop-back Code
De-activation Status
R/W
Receive Loop-back Code De-activation Status Change Inter-
rupt Enable:
Change Interrupt Enable
When this bit is set to 0:
The Receive Loop-back Code De-activation Status Change
Interrupt is disabled.
When this bit is set to 1:
The Receive Loop-back Code De-activation Status Change
Interrupt is enabled.
Receive Sa Interrupt Register (RSAIR) (Indirect Address = 0xnAH, 0x0CH)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Received
Sa6 = 1111
Interrupt
Received
Sa6 = 1110
Interrupt
Received
Sa6 = 1100
Interrupt
Received
Sa6 = 1010
Interrupt
Received
Sa6 = 1000
Interrupt
Received
Received
Received
Sa6 = 001X Sa6 = others Sa6 = 0000
Interrupt
R/W
0
Interrupt
R/W
0
Interrupt
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Received Sa6 = 1111
Received Sa6 = 1110
Received Sa6 = 1100
R/W
R/W
R/W
Received Sa6 = 1111:
When this bit is 0:
A de-bounced Sa6 bit of value equal to '1111' has not been
received from the incoming serial data.
When this bit is 1:
A de-bounced Sa6 bit of value equal to '1111' has been received
from the incoming serial data.
6
Received Sa6 = 1110:
When this bit is 0:
A de-bounced Sa6 bit of value equal to '1110' has not been
received from the incoming serial data.
When this bit is 1:
A de-bounced Sa6 bit of value equal to '1110' has been received
from the incoming serial data.
5
Received Sa6 = 1100:
When this bit is 0:
A de-bounced Sa6 bit of value equal to '1100' has not been
received from the incoming serial data.
When this bit is 1:
A de-bounced Sa6 bit of value equal to '1100' has been received
from the incoming serial data.
171
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
4
3
2
1
Received Sa6 = 1010
Received Sa6 = 1000
Received Sa6 = 001X
Received Sa6 = others
R/W
Received Sa6 = 1010:
When this bit is 0:
A de-bounced Sa6 bit of value equal to '1010' has not been
received from the incoming serial data.
When this bit is 1:
A de-bounced Sa6 bit of value equal to '1010' has been received
from the incoming serial data.
R/W
R/W
R/W
Received Sa6 = 1000:
When this bit is 0:
A de-bounced Sa6 bit of value equal to '1000' has not been
received from the incoming serial data.
When this bit is 1:
A de-bounced Sa6 bit of value equal to '1000' has been received
from the incoming serial data.
Received Sa6 = 001X:
When this bit is 0:
A de-bounced Sa6 bit of value equal to '001X' has not been
received from the incoming serial data.
When this bit is 1:
A de-bounced Sa6 bit of value equal to '001X' has been received
from the incoming serial data.Note:X can be either 0 or 1.
Received Sa6 = others:
When this bit is 0:
A de-bounced Sa6 bit of value equal to anything but other than
'1111', '1110', '1100', '1000', '001X' and '0000' has not been
received from the incoming serial data.
When this bit is 1:
A de-bounced Sa6 bit of value equal to anything but other than
'1111', '1110', '1100', '1000', '001X' and '0000' has been received
from the incoming serial data.
0
Received Sa6 = 0000
R/W
Received Sa6 = 0000:
When this bit is 0:
A de-bounced Sa6 bit of value equal to '0000' has not been
received from the incoming serial data.
When this bit is 1:
A de-bounced Sa6 bit of value equal to '0000' has been received
from the incoming serial data.
172
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
Receive Sa Interrupt Enable Register (RSAIER) (Indirect Address = 0xnAH, 0x0DH)
BIT 7
BIT 6
BIT 5
BIT 4
BIT3
BIT 2
BIT 1
BIT 0
Received
Sa6 = 1111
Interrupt
Received
Sa6 = 1110
Interrupt
Received
Sa6 = 1100
Interrupt
Received
Sa6 = 1010
Interrupt
Received
Sa6 = 1000
Interrupt
Received
Received
Received
Sa6 = 001X Sa6 = others Sa6 = 0000
Interrupt
Enable
Interrupt
Enable
Interrupt
Enable
Enable
Enable
Enable
Enable
Enable
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
R/W
0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Received Sa6 = 1111
Interrupt Enable
R/W
R/W
R/W
R/W
R/W
R/W
Received Sa6 = 1111 Interrupt Enable:
When this bit is 0:
The Received Sa6 = 1111 Interrupt is disabled.
When this bit is 1:
The Received Sa6 = 1111 Interrupt is enabled.
6
5
4
3
2
Received Sa6 = 1110
Interrupt Enable
Received Sa6 = 1110 Interrupt Enable:
When this bit is 0:
The Received Sa6 = 1110 Interrupt is disabled.
When this bit is 1:
The Received Sa6 = 1110 Interrupt is enabled.
Received Sa6 = 1100
Interrupt Enable
Received Sa6 = 1100 Interrupt Enable:
When this bit is 0:
The Received Sa6 = 1100 Interrupt is disabled.
When this bit is 1:
The Received Sa6 = 1100 Interrupt is enabled.
Received Sa6 = 1010
Interrupt Enable
Received Sa6 = 1010 Interrupt Enable:
When this bit is 0:
The Received Sa6 = 1010 Interrupt is disabled.
When this bit is 1:
The Received Sa6 = 1010 Interrupt is enabled.
Received Sa6 = 1000
Interrupt Enable
Received Sa6 = 1000 Interrupt Enable:
When this bit is 0:
The Received Sa6 = 1000 Interrupt is disabled.
When this bit is 1:
The Received Sa6 = 1000 Interrupt is enabled.
Received Sa6 = 001X
Interrupt Enable
Received Sa6 = 001X Interrupt Enable:
When this bit is 0:
The Received Sa6 = 001X Interrupt is disabled.
When this bit is 1:
The Received Sa6 = 001X Interrupt is enabled.
173
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
BIT NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1
Received Sa6 = others
Interrupt Enable
R/W
Received Sa6 = others Interrupt Enable:
When this bit is 0:
The Received Sa6 = others Interrupt is disabled.
When this bit is 1:
The Received Sa6 = others Interrupt is enabled.
0
Received Sa6 = 0000
Interrupt Enable
R/W
Received Sa6 = 0000 Interrupt Enable:
When this bit is 0:
The Received Sa6 = 0000 Interrupt is disabled.
When this bit is 1:
The Received Sa6 = 0000 Interrupt is enabled.
174
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
TABLE 9: PMON T1/E1 RECEIVE LINE CODE (BIPOLAR) VIOLATION COUNTER
REGISTER 303 PMON RECEIVE LINE CODE (BIPOLAR) VIOLATION COUNTER (RLCVCMSB) HEX ADDRESS: 0Xn8, 0X00
BIT
FUNCTION
TYPE
DEFAULT
DESCRIPTION-OPERATION
7-4 Unused
RO
0
These four Reset Upon Read bits along with PMON Receive Line Code Vio-
lation Counter - LSB, provides a 12-bit representation of the number of LIne
Code violations that have been detected by the Receive Framer block since
the last read of these registers.
3-0 RxLCV Count - High Byte
RUR
0
Lower 8 bits.
This register contains the lowest four bits within this 12 bit expression
TABLE 10: PMON T1/E1 RECEIVE LINE CODE (BIPOLAR) VIOLATION COUNTER
REGISTER 304
BIT
PMON RECEIVE LINE CODE (BIPOLAR) VIOLATION COUNTER (RLCVCLSB) HEX ADDRESS: 0Xn8, 0X01
FUNCTION
TYPE
DEFAULT
DESCRIPTION-OPERATION
These eight Reset Upon Read bits along with PMON Receive Line Code
Violation Counter - MSB, provides 12-bit representation of the number of
LIne Code violations that have been detected by Receive Framer Block since
the last read of these registers.
7-0 RxLCV Count - Low Byte
RUR
0
Upper 4 bits.
This register contains the upper 8 bits within this 12 bit expression.
.
TABLE 11: PMON T1/E1 RECEIVE FRAMING ALIGNMENT BIT ERROR COUNTER
REGISTER 305
BIT
PMON RECEIVE FRAMING ALIGNMENT ERROR COUNTER (RFAECLSB) HEX ADDRESS: 0Xn8, 0X02
FUNCTION
TYPE
DEFAULT
DESCRIPTION-OPERATION
These eight Reset Upon Read bits along with PMON E1 Receive Framing
Alignment Bit Error Counter- LSB, provides a 12-bit representation of the
number of Framing Alignment errors that have been detected by Receive E1
Framer number n since the last read of these registers.
Framing Alignment Error
Count - High Byte
7-0
RUR
0
This register contains the upper 8bits within this 12-bit expression.
TABLE 12: PMON T1/E1 RECEIVE FRAMING ALIGNMENT BIT ERROR COUNTER
REGISTER 306
PMON RECEIVE FRAMING ALIGNMENT BIT ERROR COUNTER (RFAB-ECMSB) HEX ADDRESS: 0Xn8, 0X03
BIT
FUNCTION
TYPE
DEFAULT
DESCRIPTION-OPERATION
7-4 Unused
R/O
0
These four Reset Upon Read bits along with PMON E1 Receive Framing
Alignment Bit Error Counter- MSB, provides 12-bit representation of the
number of Framing Alignment errors that have been detected by Receive E1
Framer Block since the last read of these register.
Framing Alignment Error
Count - Low Byte
3-0
RUR
0
This register contains the lowest four bits within this 12-bit expression
175
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
TABLE 13: PMON T1/E1 RECEIVE SEVERELY ERRORED FRAME COUNTER
PMON RECEIVE SEVERELY ERRORED FRAME COUNTER (RSEFC) HEX ADDRESS: 0Xn8, 0X04
REGISTER 307
BIT
FUNCTION
TYPE
DEFAULT
DESCRIPTION-OPERATION
Severely Errored 8-bit frame accumulation Counter
Severely Errored Frame
Count
Note: A severely errored frame event is defined as the occurrence of
two consecutive errored frame alignment signals that are not responsi-
ble for loss of frame alignment.
7-0
RUR
0
TABLE 14: PMON T1/E1 RECEIVE CRC-4 BLOCK ERROR COUNTER - MSB
REGISTER 308 PMON RECEIVE SYNCHRONIZATION BIT BLOCK ERROR COUNTER (RSBBECMSB) HEX ADDRESS: 0Xn8,
0X05
BIT
FUNCTION
TYPE
DEFAULT
DESCRIPTION-OPERATION
These eight Reset Upon Read bits along with PMON E1 Receive CRC-4
Block Error Counter - LSB, provides a 10-bit representation of the number of
CRC-4 Block errors detected by Receive E1 Framer Block since the last read
of these registers.
CRC-4 Block Error Count -
High Byte
7-0
RUR
0
This register contains the upper eight bits of this 10 bit expression
TABLE 15: PMON T1/E1 RECEIVE CRC-4 BLOCK ERROR COUNTER - LSB
REGISTER 309 PMON RECEIVE SYNCHRONIZATION BIT BLOCK ERROR COUNTER (RSBBECLSB) HEX ADDRESS: 0Xn8,
0X06
BIT
FUNCTION
TYPE
DEFAULT
DESCRIPTION-OPERATION
7-2 Unused
RO
0
These two Reset upon Read bits along with PMON E1 Receive CRC-4 Block
Error Counter - MSB, provides a 10-bit representation of the number of CRC-
4 Block errors that have been detected by a Receive E1 Framer Block since
the last read of these registers.
This register contains the lower two bits within this 10 bit expression.
Note: Counter contains the 10-bit synchronization bit error event. A synchro-
nization bit error event is defined as a CRC-4 error received. Counter is dis-
abled during loss of sync at either the Frame/FAS or ESF/CRC4 level, but it
will not be disabled if loss of multiframe sync occurs at the CAS level.
CRC-4 Block Error Count -
Low Byte
1-0
RUR
0
TABLE 16: PMON T1/E1 RECEIVE FAR-END BLOCK ERROR COUNTER - MSB
PMON RECEIVE FAR-END BLOCK ERROR COUNTER (E1RFEBECMSB) HEX ADDRESS: 0Xn8, 0X07
REGISTER 310
BIT
FUNCTION
TYPE
DEFAULT
DESCRIPTION-OPERATION
These eight Reset Upon Read bits along with PMON E1 Receive Far-End
Block Error Counter - LSB, provides a 10-bit representation of the number of
Far End Block Error events that have been detected by the Receive E1
Framer Block since the last read of these registers.
Far-End Block Error Count
- High Byte
7-0
RUR
0
This register contains the upper eight bits within this 10 bit expression.
176
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
TABLE 17: PMON T1/E1 RECEIVE FAR END BLOCK ERROR COUNTER
REGISTER 311
PMON RECEIVE FAR END BLOCK ERROR COUNTER (RFEBECLSB)
HEX ADDRESS: 0Xn8, 0X08
BIT
FUNCTION
TYPE
DEFAULT
DESCRIPTION-OPERATION
7-2 Unused
RO
0
These two Reset Upon Read bits along with PMON E1 Receive Far-End
Block Error Counter - MSB, provides a 10-bit representation of the number of
Far End Block Error events that have been detected by the Receive E1
Framer Block since the last read of these registers.
Far-End Block Error Count
-Low Byte
This register contains the lower two bits within this 10 bit expression.
Note: Counter contains the 10-bit far-end block error event. Counter
will increment once each time the received E-bit is set to zero. The
counter is disabled during loss of sync at either the FAS or CRC-4 level
and it will continue to count if loss of multiframe sync occurs at the
CAS level.
1-0
RUR
0
TABLE 18: PMON T1/E1 RECEIVE SLIP COUNTER
PMON RECEIVE SLIP COUNTER (RSC)
REGISTER 312
BIT
HEX ADDRESS: 0Xn8, 0X09
FUNCTION
TYPE
DEFAULT
DESCRIPTION-OPERATION
Note: counter contains the 8-bit receive buffer slip event. A slip event is
defined as a replication or deletion of a T1/E1 frame by the receiving slip
buffer.
7-0 Slip Count
RUR
0
Note: A 12 bit counter which counts the occurrence of a bipolar viola-
tion on the receive data line. This counter is of sufficient length so that
the probability of counter saturation over a one second interval at a 10 -
3-Bit Error Rate (BER) is less than 0.001%.
TABLE 19: PMON T1/E1 RECEIVE LOSS OF FRAME COUNTER
PMON RECEIVE LOSS OF FRAME COUNTER (RLFC)
REGISTER 313
HEX ADDRESS: 0Xn8, 0X0A
BIT
FUNCTION
TYPE
DEFAULT
DESCRIPTION-OPERATION
Note: LOFC is a count of the number of times a "Loss Of FAS Frame"
has been declared. This counter provides the capability to measure an
accumulation of short failure events.
7-0 Loss of Frame Counts
RUR
0
177
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
TABLE 20: PMON T1/E1 RECEIVE CHANGE OF FRAME ALIGNMENT COUNTER
PMON RECEIVE CHANGE OF FRAME ALIGNMENT COUNTER (RCFAC) HEX ADDRESS: 0Xn8, 0X0B
REGISTER 314
BIT
FUNCTION
TYPE
DEFAULT
DESCRIPTION-OPERATION
Change of Frame Alignment Accumulation counter.
Note: COFA is declared when the newly-locked framing is different from
the one offered by off-line framer.
7-0 COFA Count
RUR
0
TABLE 21: PMON LAPD T1/E1 FRAME CHECK SEQUENCE ERROR COUNTER
PMON LAPD FRAME CHECK SEQUENCE ERROR COUNTER (FCSEC) HEX ADDRESS: 0Xn8, 0X0C
REGISTER 315
BIT
FUNCTION
TYPE
DEFAULT
DESCRIPTION-OPERATION
Frame Check Sequence error Accumulation Counter.
7-0 FCS Error Count
RUR
0
Note: Counter accumulates the times of occurrence of receive frame
check sequence error detected by LAPD controller.
TABLE 22: T1/E1 PRBS BIT ERROR COUNTER MSB
T1/E1 PRBS BIT ERROR COUNTER MSB
REGISTER 316
HEX ADDRESS: 0Xn8, 0X0D
BIT
7
FUNCTION
TYPE
RUR
RUR
RUR
RUR
RUR
RUR
RUR
RUR
DEFAULT
DESCRIPTION-OPERATION
PRBSE[15]
0
0
0
0
0
0
0
0
Most significant bits of PRBS bit error Accumulation counter
6
PRBSE[14]
PRBSE[13]
PRBSE[12]
PRBSE[11]
PRBSE[10]
PRBSE[9]
PRBSE[8]
5
4
3
2
1
0
178
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
TABLE 23: T1/E1 PRBS BIT ERROR COUNTER LSB
T1/E1 PRBS BIT ERROR COUNTER LSB
REGISTER 317
HEX ADDRESS: 0Xn8, 0X0E
BIT
7
FUNCTION
TYPE
RUR
RUR
RUR
RUR
RUR
RUR
RUR
RUR
DEFAULT
DESCRIPTION-OPERATION
PRBSE[7]
0
0
0
0
0
0
0
0
Least significant byte of PRBS bit error accumulation counter.
6
PRBSE[6]
PRBSE[5]
PRBSE[4]
PRBSE[3]
PRBSE[2]
PRBSE[1]
PRBSE[0]
5
4
3
2
1
0
TABLE 24: T1/E1 TRANSMIT SLIP COUNTER
T1/E1 TRANSMIT SLIP COUNTER (T1/E1TSC)
REGISTER 318
BIT
HEX ADDRESS: 0Xn8, 0X0F
FUNCTION
TYPE
RUR
RUR
RUR
RUR
RUR
RUR
RUR
RUR
DEFAULT
DESCRIPTION-OPERATION
7
6
5
4
3
2
1
0
TxSLIP[7]
TxSLIP[6]
0
0
0
0
0
0
0
0
Slip accumulation counter.
TxSLIP[5]
TxSLIP[4]
TxSLIP[3]
TxSLIP[2]
TxSLIP[1]
TxSLIP[0]
179
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
1.7 THE INTERRUPT STRUCTURE WITHIN THE FRAMER
The XRT84L38 Framer is equipped with a sophisticated Interrupt Servicing Structure. This Interrupt Structure
includes an Interrupt Request output pin INT, numerous Interrupt Enable Registers and numerous Interrupt
Status Registers.
The Interrupt Servicing Structure, within the XRT84L38 Framer contains three levels of hierarchy:
• The Framer Level
• The Block Level
• The Source Level.
The Framer Interrupt Structure has been carefully designed to allow the user to quickly determine the exact
source of this interrupt (with minimal latency) which will aid the µC/µP in determining the which interrupt ser-
vice routine to call up in order to eliminate or properly respond to the condition(s) causing the interrupt.
The XRT84L38 Framer comes equipped with registers to support the servicing of this wide array of potential
"interrupt request" sources. Table 25 lists the possible conditions that can generate interrupts.
TABLE 25: LIST OF THE POSSIBLE CONDITIONS THAT CAN GENERATE INTERRUPTS, IN EACH FRAMER
INTERRUPT BLOCK
Framer Level
INTERRUPTING CONDITION
Loss of RxLineClk Signal· One Second Interrupt
HDLC Controller Block
Transmit HDLC - Start of Transmission
Receive HDLC - Start of Reception
Transmit HDLC - End of Transmission
Receive HDLC - End of Reception
FCS Error
Receipt of Abort Sequence
Receipt of Idle Sequence
Slip Buffer Block
Slip Buffer Full
Slip Buffer Empty
Slip Buffer - Slip
Alarm & Error Block
Receipt of CAS Multi-frame Yellow Alarm
Detection of Loss of Signal Condition
Detection of Line Code Violation
Change in Receive Loss of Framer Condition
Change in Receive AIS Condition
Receipt of FAS Frame Yellow Alarm
T1/E1 Frame Block
Change in CAS Multi-Frame Alignment
Change in National Bits· Change in CAS Signaling Bits
Change in FAS Frame Alignment· Change in the "In Frame" Condition
Detection of "Frame Mimicking Data"
Detection of Sync (CRC-4/CRC-6) Errors
Detection of Framing Bit Errors
General Flow of Interrupt Servicing
When any of the conditions presented in Table 25 occur, (if their Interrupt is enabled), then the Framer gener-
ates an interrupt request to the µP/µC by asserting the active-low interrupt request output pin, INT. Shortly after
the local µC/µP has detected the activated INT signal, it will enter into the appropriate user-supplied interrupt
service routine. The first task for the µP/µC, while running this interrupt service routine, may be to isolate the
source of the interrupt request down to the device level (e.g, the Framer IC), if multiple peripheral ICs exist in
the user's system. However, once the interrupting peripheral device has been identified, the next task for the
µP/µC is to determine exactly what feature of functional section within the device requested the interrupt.
180
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
Determine the Framer(s) Requesting the Interrupt
If the interrupting device turns out to be the Framer, then the µP/µC must determine which of the eight framer
channels requested the interrupt. Hence, upon reaching this state, one of the very first things that the µP/µC
must do within the user Framer interrupt service routine, is to perform a read of each of the Block Interrupt Sta-
tus Registers within all of the Framer channels that have been enabled for Interrupt Generation via their re-
spective Interrupt Control Registers.
Table 26 lists the Indirect Address for the Block Interrupt Status Registers associated with each of the Framer
channels within the Framer.
TABLE 26: ADDRESS OF THE BLOCK INTERRUPT
STATUS REGISTERS
FRAMER
NUMBER
ADDRESS OF BLOCK INTERRUPT STATUS
REGISTER
0
1
2
3
4
5
6
7
0x0A, 0x02
0x1A, 0x02
0x2A, 0x02
0x3A, 0x02
0x4A, 0x02
0x5A, 0x02
0x6A, 0x02
0x7A, 0x02
The bit-format of each of these Block Interrupt Status Registers is listed below.
181
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
TABLE 27: BLOCK INTERRUPT STATUS REGISTER
BLOCK INTERRUPT STATUS REGISTER (BISR)
REGISTER 319
HEX ADDRESS: 0XnA, 0X00
BIT
FUNCTION
TYPE
DEFAULT
DESCRIPTION-OPERATION
Sa6 Interrupt Status
7
Sa6
RO
0
Loopback Code Interrupt
7-6 LBCODE
RO
0
RxClk Los Interrupt Status
Indicates if Framer n has experienced a Loss of Recovered Clock interrupt
since last read of this register.
5
4
RxClkLOS
ONESEC
RUR
0
0 = Loss of Recovered Clock interrupt has not occurred since last read of this
register
1 = Loss of Recovered Clock interrupt has occurred since last read of this
register.
One Second Interrupt Status
Indicates if the XRT84L38 has experienced a One Second interrupt since the
last read of this register.
0 = No outstanding One Second interrupts awaiting service
1 = Outstanding One Second interrupt awaits service
RUR
0
0
HDLC Block Interrupt Status
Indicates if the HDLC block has an interrupt request awaiting service.
0 = No outstanding interrupt requests awaiting service
1 = HDLC Block has an interrupt request awaiting service. Interrupt Service
routine should branch to and read Data LInk Status Register (address
xA,06).
3
HDLC
RO
NOTE: This bit-field will be reset to 0 after the microprocessor has
performed a read to the Data Link Status Register.
Slip Buffer Block Interrupt Status
Indicates if the Slip Buffer block has any outstanding interrupt requests
awaiting service.
0 = No outstanding interrupts awaiting service
1 = Slip Buffer block has an interrupt awaiting service. Interrupt Service rou-
tine should branch to and read Slip Buffer Interrupt Status register (address
0xXA,0x09.
2
SLIP
RO
0
NOTE: This bit-field will be reset to 0 after the microprocessor has
performed a read of the Slip Buffer Interrupt Status Register.
Alarm & Error Block Interrupt Status
Indicates if the Alarm & Error Block has any outstanding interrupts that are
awaiting service.
0 = No outstanding interrupts awaiting service
1 = Alarm & Error Block has an interrupt awaiting service. Interrupt SerSta-
tus Register (address xA,02)
1
0
ALARM
RO
RO
0
0
NOTE: This bit-field will be reset to 0 after the microprocessor has
performed a read of the Alarm & Error Interrupt Status register.
T1/E1 Framer Block Interrupt Status
Indicates if an T1/E1 Frame Status interrupt request is awaiting service.
0 = No T1/E1 Frame Status interrupt is pending
T1/E1 FRAME
1 = T1/E1 Framer Status interrupt is awaiting service.
For a given Framer, the Block Interrupt Status Register presents the Interrupt Request status of each Interrupt
Block within the Framer. The Block Interrupt Status Register helps the µP/µC identify which Interrupt Block(s)
have requested the interrupt. Whichever bit(s) are asserted in this register identifies which block(s) have expe-
rienced an interrupt generating condition, as presented in Table 27. Once the µP/µC has read this register, it
182
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
can determine which branch within the interrupt service routine that it must follow in order to properly service
this interrupt.
The Framer IC further supports the Interrupt Block Hierarchy by providing the Block Interrupt Enable Register.
The bit-format of this register is identical to that for the Block Interrupt Status Register and is presented below.
TABLE 28: BLOCK INTERRUPT ENABLE REGISTER
REGISTER 320
BIT
BLOCK INTERRUPT ENABLE REGISTER (BIER)
HEX ADDRESS: 0XnA, 0X01
FUNCTION
TYPE
R/W
R/W
DEFAULT
DESCRIPTION-OPERATION
7
6
SA6_ENB
LBCODE_ENB
0
0
SA6 interrupt enable
Loopback code interrupt enable
RXCLKLOSS
ONESEC_ENB
HDLC_ENB
RxLineClk Loss Interrupt Enable
0 = Disables interrupt
1 = Enables interrupt
5
4
3
2
1
0
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
One Second Interrupt Enable
0 = Disables interrupt
1 = Enables Interrupt
HDLC Block Interrupt Enable
0 = Disables all HDLC Block interrupts
1 = Enables HDLC Block (for interrupt generation) at the block level
SLIP_ENB
Slip Buffer Block Interrupt Enable
0 = Disables all Slip Buffer Block Interrupts
1 = Enables Slip Buffer Block at the block level
ALARM_ENB
T1/E1FRAME_ENB
Alarm & Error Block Interrupt Enable
0 = Disables all Alarm & Error Block interrupts
1 = Enables Alarm & Error block at the block level
T1/E1 Frame Block Enable
0 = Disables all Frame Block interrupts
1 = Enables the Frame Block at the block level
The Block Interrupt Enable Register permits the user to individually enable or disable the interrupt requesting
capability of each of the "interrupt blocks" within the Framer. If a particular bit-field, within this register contains
the value "0"; then the corresponding functional block has been disabled from generating any interrupt re-
quests.
183
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
1.7.1 Configuring the Interrupt System, at the Framer Level
The XRT84L38 Framer IC permits the user to enable or disable each of the eight Framers for interrupt genera-
tion. Further, the chip permits the user to make the following configuration selection.
1. Whether the source-level Interrupt Status bits are Reset-upon-Read or Write-to-Clear.
2. Whether or not an activated interrupt is automatically cleared.
1.7.1.1 Enabling/Disabling the Framer for Interrupt Generation
Each of the eight (8) Framers of the XRT84L38 Framer can be enabled or disabled for interrupt generation.
This selection is made by writing the appropriate “0” or “1” to bit 0 (INTRUP_EN) of the Interrupt Control Regis-
ter corresponding to that framer, (see Table 29).
NOTE: Setting this bit-field to "1" does not enable all of the interrupts within the Framer. A given interrupt must also be
enabled at the block and source-level before it is enabled for interrupt generation.
TABLE 29: INTERRUPT CONTROL REGISTER
REGISTER 26
INTERRUPT CONTROL REGISTER (ICR)
HEX ADDRESS: 0Xn0, 0X1A
BIT
MODE
FUNCTION
TYPE
DEFAULT
DESCRIPTION-OPERATION
7-3
Unused
RO
0
Interrupt Write-to-Clear or Reset-upon-Read Select
Configures Interrupt Status bits to either RUR or Write-to-Clear
0=Interrupt Status bit RUR
1=Interrupt Status bit Write-to-Clear
2
1
0
INT_WC_RUR
ENBCLR
R/W
R/W
R/W
0
0
0
Interrupt Enable Auto Clear
0=Interrupt Enable bits are not cleared after status reading
1=Interrupt Enable bits are cleared after status reading
Interrupt Enable for Framer_n
Enables Framer n for Interrupt Generation.
0 = Disables corresponding framer block for Interrupt Generation
1 = Enables corresponding framer block for Interrupt Generation
INTRUP_ENB
1.7.1.2 Configuring the Interrupt Status Bits within a given Framer to be Reset-upon-Read or Write-
to-Clear.
The XRT84L38 Source-Level Interrupt Status Register bits can be configured to be either Reset-upon-Read or
Write-to-Clear. If the user configures the Interrupt Status Registers to be Reset-upon-Read, then when the µP/
µC is reading the interrupt status register, the following happens:
1. The contents of the Source-Level Interrupt Status Register automatically is reset to “0x00" following the
read operation.
2. The Interrupt Request Output pin (INT) automatically toggles false, or "High", upon reading the Interrupt
Status Register containing the last activated interrupt status bit.
If the user configures the Interrupt Status Registers to be Write-to-Clear, then when the µP/µC is reading the
interrupt status register, the following happens.
1. The contents of the Source-Level Interrupt Status Register is not cleared to "0x00" following the read oper-
ation. The µP/µC has to write 0x00 to the interrupt status register in order to reset the contents of the reg-
ister to 0x00.
2. Reading the Interrupt Status Register, which contains the activated bit(s) does not cause the Interrupt
Request Output pin (INT) to toggle false. The Interrupt Request Output pin does not toggle false until the
µP/µC has written 0x00 into this register. The Interrupt Service Routine must include this write operation.
The Interrupt Status Register associated with a given framer can be configured to be either Reset-upon-Read
or Write-to-Clear by writing the appropriate value into Bit 2 within the Interrupt Control Register (see Table 29).
1.7.1.3 Automatic Reset of Interrupt Enable Bits
184
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
Occasionally, the user's system which includes the Framer, may experience a fault condition, such that a Fram-
er Interrupt Condition continuously exists. If this particular interrupt has been enabled, then the Framer will
generate an interrupt request to the µP/µC. Afterwards, the µP/µC attempts to service this interrupt by reading
the appropriate Block-level and Source-Level Interrupt Status Register. Additionally, the local µP/µC attempts
to perform some system-related tasks in order to try to resolve these conditions causing the interrupt. After the
local µC/µP has attempted all of these things, the Framer negates the INT output pin. However, because this
system fault still remains, the condition causing the Framer to issue this interrupt also exists. Consequently, the
Framer generates another interrupt request which forces the µP/µC to once again attempt to service this inter-
rupt. This results in the local µP/µC being tied up in a continuous cycle of executing this one interrupt service
routine. Consequently, the µP/µC, along with portions of the overall system, now becomes non-functional.
To prevent this from occurring, the Framer can be configured to automatically reset the interrupt enable bits fol-
lowing their activation by writing the appropriate value to bit 1 of the Interrupt Control Register (see Table 29).
Writing a "1" to this bit-field configures the Framer to reset a given interrupt following activation. Writing a "0" to
this bit-field configures the Framer to leave the interrupt enabled, following its activation.
185
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
2.0 THE E1 FRAMING STRUCTURE
2.1 THE SINGLE E1 FRAME
A single E1 frame consists of 256 bits which is created 8000 times a second; thereby yielding a bit-rate of
2.048Mbps. The 256 bits within each E1 frame is grouped into 32 octets or timeslots. These timeslots are num-
bered from 0 to 31. Figure 17 presents a diagram of a single E1 frame.
FIGURE 17. SINGLE E1 FRAME DIAGRAM
E1 Frame
Timeslot 0
Timeslot 1
Timeslot 29
Timeslot 30
Timeslot 31
0
1
2
3
4
5
6
7
A single E1 frame consists of 32 timeslots. However, not all of these timeslots are available to transmit voice or user
data. For instance, timeslot 0 is always reserved for system use and timeslot 16 is sometimes used (reserved) by
the system. Hence, within each E1 frame, either 30 or 31 of the 32 timeslots are available for transporting user
or voice data.
TIMESLOT 0
In general, there are two types of E1 frames.
• FAS (Frame Alignment Signaling) frames
• non-FAS frames
In any E1 data stream, the E1 frame type alternates between the FAS and non-FAS frames.
The timeslot 0 octet within the FAS E1 frame contains a framing alignment pattern and therefore supports
framing. The timeslot 0 octet within the non-FAS E1 frame contains bits that support signaling or data link mes-
sage transmission.
TIMESLOT 0 OCTETS WITHIN FAS FRAMES
The bit-format of a timeslot 0 octet within a FAS frame is presented in Table 30.
TABLE 30: BIT FORMAT OF TIMESLOT 0 OCTET WITHIN A FAS E1 FRAME
BIT
7
6
5
4
3
2
1
0
Value
1
1
0
1
1
0
0
SI
Function
Frame Alignment Signaling (FAS) Pattern
International Bit
The fixed framing pattern (e.g., 0, 0, 1, 1, 0, 1, 1) is
used by the Receive E1 Framer at the Remote terminal of a CRC-4 calculation, which is discussed in greater detail in
for frame synchronization/alignment purposes. Section 2.2.1.
In practice, the Si bit within the FAS E1 Frame carries the results
DESCRIPTION-
OPERATION
The table above indicates that the FAS frame timeslot 0 octet consists of a single International Bit within bit-
field 0, Si, followed by a fixed 7-bit pattern within bit-fields 1 through 7.
186
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
BIT 0—SI (INTERNATIONAL BIT)
The Si bit within the FAS E1 Frame typically carries the results of a CRC-4 calculation, which is discussed in
greater detail in Section 2.2.1. The fixed framing pattern (e.g., 0, 0, 1, 1, 0, 1, 1) will be used by the Receive E1
Framer at the Remote terminal for frame synchronization/alignment purposes. Section discusses how the Re-
ceive E1 Framer uses these bits.
Timeslot 0 octets within non-FAS frames
The bit-format of a timeslot 0 octet within a non-FAS frame is presented in Table 31.
TABLE 31: BIT FORMAT OF TIMESLOT 0 OCTET WITHIN A NON-FAS E1 FRAME
BIT
7
6
5
4
3
2
A
1
0
Si
Value
Sa8 Sa7 Sa6 Sa5 Sa4
National bits
1
Function6
Yellow Alarm
Fixed Value
International Bit
Description- National Bits
Operation These bit-fields can be used This bit-field is used to transmit Bit-field “1” contains a
to carry data link information a Yellow alarm to the Remote fixed value “1”. This bit-
Terminal. This bit-field is set to field will be used for FAS
“0” during normal conditions, framing synchronization/
FAS Frame Yellow Alarm Bit Fixed at “1”
International Bit
The Si bit within the non-FAS
E1 Frame typically carries a
specific value that will be
used by the Receive E1
from the Local transmitting
terminal to the Remote
receiving terminal. Since the and is set to “1” whenever the
National bits only exist in the Receive E1 Framer detects an Remote Receive E1
alignment purposes by the Framer for CRC Multi-frame
alignment purposes.
non-FAS frames, they offer a LOS (Loss of Signal) or LOF
maximum signaling data link (Loss of Framing) condition in
Framer.
bandwidth of 20kbps.
the incoming E1 frame data.
The table above indicates the non-FAS frame timeslot 0 octet consists of a single international bit, Si, within bit-
field 0.
BIT 0—SI (INTERNATIONAL BIT)
The Si bit, within the non-FAS E1 Frame carries a specific value that will be used by the Receive E1 Framer, for
CRC Multi-frame alignment purposes. Section 7 discusses the exact role of the Si bit-field within the non-FAS
frames.
BIT 1—FIXED AT “1”
Bit-field “1” contains a fixed value “1”. This bit-field will be used for FAS framing synchronization/alignment pur-
poses by the Remote Receive E1 Framer. Section _ discusses how the Receive E1 Framer uses this bit-field.
BIT 2—A (FAS FRAME YELLOW ALARM BIT)
This bit-field is used to transmit a Yellow alarm to the Remote Terminal. This bit-field is set to “0” during normal
conditions, and is set to “1” whenever the Receive E1 Framer detects an LOS (Loss of Signal) or LOF (Loss of
Framing) condition in the incoming E1 frame data.
BIT 3 THROUGH 7—SA4–SA8 (NATIONAL BITS)
These bit-fields can be used to carry data link information from the Local transmitting terminal to the Remote
receiving terminal. Since the National bits only exist in the non-FAS frames, they offer a maximum signaling da-
ta link bandwidth of 20kbps.
2.2 THE E1 MULTI-FRAME STRUCTURES
The 84L38 Octal Framer supports two kinds of E1 Multi-frame structures:
• CRC Multi-frame
• CAS Multi-frame
2.2.1 The CRC Multi-frame Structure
A CRC Multi-frame consists of 16 consecutive E1 frames, with the first of these frames being a FAS frame.
From a Frame Alignment point of view, the timeslot 0 octets of each of these E1 frames within the Multi-frame
are the most important 16 octets. Table 32 presents the bit-format for all timeslot 0 octets within a 16 frame
CRC Multi-frame.
187
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
TABLE 32: BIT FORMAT OF ALL TIMESLOT 0 OCTETS WITHIN A CRC MULTI-FRAME
FRAME
NUMBER
SMF
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
1
0
1
C1
0
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
A
0
1
Sa4
1
1
Sa5
1
0
Sa6
0
1
Sa7
1
1
Sa8
1
2
C2
0
3
A
0
Sa4
1
Sa5
1
Sa6
0
Sa7
1
Sa8
1
4
C3
1
5
A
0
Sa4
1
Sa5
1
Sa6
0
Sa7
1
Sa8
1
6
C4
0
7
A
0
Sa4
1
Sa5
1
Sa6
0
Sa7
1
Sa8
1
2
8
C1
1
9
A
0
Sa4
1
Sa5
1
Sa6
0
Sa7
1
Sa8
1
10
11
12
13
14
15
C2
1
A
0
Sa4
1
Sa5
1
Sa6
0
Sa7
1
Sa8
1
C3
E
A
0
Sa4
1
Sa5
1
Sa6
0
Sa7
1
Sa8
1
C4
E
A
Sa4
Sa5
Sa6
Sa7
Sa8
Table 32 has the CRC Multi-frame divided into 2 sub Multi-Frames. Sub-Multi-Frame 1 is designated as SMF1
and Sub-Multi-Frame 2 is designated as SMF2.
SMF1 consists of E1 frames 0 through 7 consisting of 4 FAS frames and 4 non-FAS frames.
There are two interesting things to note in Table 32. First, all of the bit-field 0 positions within each of the FAS
frames are designated as C1, C2, C3 and C4. These four bit-fields contain the CRC-4 values which has been
computed over the previous SMF. Hence, while the Transmit E1 Framer is assembling a given SMF, it com-
putes the CRC-4 value for that SMF and inserts these results into the C1 through C4 bit-fields within the very
next SMF. These CRC-4 values ultimately are used by the Remote Receive E3 Framer for error-detection pur-
poses.
NOTE: This framing structure is referred to as a CRC Multi-Frame because it permits the remote receiving terminal to locate
and verify the CRC-4 bit-fields.
The second interesting thing to note regarding Table 32 is that the bit-field 0 positions within each of the non-
FAS frames are of a fixed six (6) bit pattern: 0, 0, 1, 0, 1, 1; along with two bits, each designated at “E”. This six
bit pattern is referred to as the CRC Multi-Frame alignment pattern. This six-bit pattern will ultimately be used
by the Remote Receive E1 Framer for CRC Multi-Frame synchronization/alignment. Section discusses how
the Receive E1 Framer uses this 6-bit CRC Multi-frame alignment pattern for frame synchronization/alignment.
The "E" bits are used to indicate that the Local Receive E1 framer has detected errored sub-Multi-Frames.
2.2.2 CAS Multi-Frames and Channel Associated Signaling
CAS Multi-Frames are only relevant if the user is using CAS or Channel Associated Signaling. If the user is im-
plementing Common Channel Signaling then the CAS Multi-Frame is not available. The exact role of CAS
Multi-Frames is discussed in some detail in the next section.
2.2.2.1 Channel Associated Signaling
If the user operates an E1 channel in Channel Associated Signaling (CAS) mode, then the timeslot 16 octets
within each E1 frame will be reserved for signaling. Such signaling would convey information such as On-Hook,
Off-Hook conditions, call set-up, control, etc. In CAS, this type of signaling data that is associated with a partic-
ular voice channel will be carried within timeslot 16 of a particular E1 frame within a CAS Multi-Frame.
188
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The CAS is carried in a Multi-Frame structure which consists of 16 consecutive E1 frames. The framing/byte
format of a CAS Multi-Frame is presented in Figure 18.
FIGURE 18. FRAME/BYTE FORMAT OF THE CAS MULTI-FRAME STRUCTURE
A Single CAS Multiframe
Timeslot 16
Frame 0
Timeslot 16
Frame 1
Timeslot 16
Frame 2
Timeslot 16
Frame 15
ABCD
ABCD
ABCD
xyxx
ABCD
ABCD ABCD
0000
Signaling Data
Associated with
Timeslot 15
Signaling Data
Associated with
Timeslot 2
Signaling Data
Associated with
Timeslot 1
CAS Multiframe
Alignment Pattern
Signaling Data
Associated with
Timeslot 31
Signaling Data
Associated with
Timeslot 17
Signaling Data
Associated with
Timeslot 18
x = “dummy bits”
y = Carries the Multiframe “Yellow Alarm” bit
Figure 18 indicates that timeslot 16 within Frame 1 of the CAS Multi-Frame, contains 4 bits of signaling data for
voice channel 1 and 4 bits of signaling data for voice channel 17. Likewise, timeslot 16 within Frame 2 contains
4 bits of signaling data for voice channel 2 and 4 bits of signaling data for voice channel 18; and so on.
Timeslot 16 within frame 0 is a special octet that is used for two purposes.
1. To convey CAS Multi-Frame alignment information, and
2. To convey Multi-Frame alarm information to the Remote Terminal.
The bit-format of timeslot 16 within frame 0 of a CAS Multi-Frame is 0000 xyxx.
The upper nibble of this octet contains all zeros and is used to identify itself as the CAS Multi-Frame alignment
signal. If CAS is used, then the user is advised to insure that none of the other timeslot 16 octets contain the
value "0000". The lower nibble of this octet contains the expression "xyxx". In this case, the x-bits are the spare
bits and should be set to "0" if not used. The y-bit is used to indicate a Multi-Frame alarm condition to the Re-
mote terminal. During normal operation, this bit-field is cleared to "0". However, if the Local Receive E1 Framer
detects a problem with the incoming Multi-Frames, then the Local Transmit E1 Framer will set this bit-field with-
in the next outbound CAS Multi-Frame to "1".
NOTE: The Local Transmit E1 Framer will continue to set the y-bit to "1" for the duration that the Local Receive E1 Framer
detects this problem.
2.2.2.2 Common Channel Signaling (CCS)
Common Channel Signaling is an alternative form of signaling from Channel Associated Signaling. In CCS,
whatever signaling data which is transported via the outbound E1 data stream, carries information that applies
to all of the voice channels as a set (e.g., timeslots 1 through 15 and 17 through 31) in the E1 frame. There are
numerous other variations of Common Channel Signaling that are available. Some of these are listed below.
• 31 Voice Channels with the common channel signaling being transported via the National Bits.
189
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
• 30 Voice Channels with the common channel signaling data being transported via the National Bits and CAS
data being transported via timeslot 16.
• 30 Voice Channels with the Common Channel Signaling being processed via timeslot 16. (e.g., Primary Rate
ISDN Signaling).
A more detailed discussion of these forms of Common Channel signaling are discussed in Section 10.0.
FIGURE 19. E1 FRAME FORMAT
Time Slot 0
Time Slot 16
Time Slots 1-15, 17-31
a. Even Frames 0, 2, 4-14
a. Frame 0
1
0
0
1
1
0
1
1
0
0
0
0
X
A
Y
B
X
C
X
D
Channel Data
FAS
MAS
b. Frames 1-15
b. Odd Frames 1, 3, 5-15
8 Bits/
Time Slot
1
1
A
N
N
N
N
N
A
B
C
D
1
2
3
4
5
6
7
8
TS
0
TS
1
TS
2
TS
3 - 14
TS
15
TS
16
TS
17
TS
18 - 28
TS
29
TS
30
TS
31
32 Time Slots/Frame
16 Frames/
Multiframe
FR
0
FR
1
FR
2
FR
3
FR
4
FR
5
FR
6
FR
7
FR
8
FR
9
FR
10
FR
11
FR
12
FR
13
FR
14
FR
15
190
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
3.0 THE DS1 FRAMING STRUCTURE
A single T1 frame is 193 bits long and is transmitted at a frame rate of 8000Hz. This results in an aggregate bit
rate of 193 bits X 8000/sec = 1.544 Mbits/sec. Basic frames are divided into 24 timeslots numbered 1 thru 24
and a framing bit, see Figure 20. Each timeslot is 8 bits in length and is transmitted most significant bit first,
numbered bit 0. This results in a single timeslot data rate of 8 bits x 8000/sec = 64 kbits/sec.
FIGURE 20. T1 FRAME FORMAT
DS1 Frame
125µs
Timeslot
24
S
bit
Timeslot
1
Timeslots
2 - 22
Timeslot
23
Timeslot
24
S
bit
Timeslot
1
(1/1.544)µs
Bit 0 Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7
(8/1.544)µs
3.1 T1 SUPER FRAME FORMAT (SF)
The Superframe Format (SF), is also referred to as the D4 format. The requirement for associated signaling in
frames 6 and 12 dictates that the frames be distinguishable. This leads to a multiframe structure consisting of
12 frames per superframe (SF). See Figure 21 and Table 33.
The SF structure consists of a multiframe of 12 frames. Each frame has 24 timeslots, plus an F-bit and 8 bits
per timeslot. A timeslot is equivalent to one voice circuit or one 64kb/s data circuit.
This structure of frames and multiframes is defined by the F-bit pattern. The F-bit is designated alternately as
an Ft bit (terminal framing bit) or Fs bit (signalling framing bit). The Ft bit carries a pattern of alternating zeros
and ones (101010) in odd frames that defines the boundaries so that one timeslot may be distinguished from
another. The Fs bit carries a pattern of (001110) in even frames and defines the multiframe boundaries so that
one frame may be distinguished from another.
191
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
FIGURE 21. T1 SUPERFRAME PCM FORMAT
Signalling
Information
Bit 7
B
During:
Frame12
Frame6
8 Bits per Timeslot
A
Bit 0 Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7
Ft
or
Fs
24TimeslotsperFrame
Frame = 193 Bits
TS
1
TS
TS
TS
------------------
-------------------
13
24
2
FR
FR
2
FR
7
FR
11
FR
12
Multiframe
SF = 12 Frames
------------------
-------------------
1
TABLE 33: SUPERFRAME FORMAT
F-BITS BIT USE IN EACH TIMESLOT
SIGNALLING
CHANNEL
FRAME
BIT
TERMINAL
TERMINAL
TRAFFIC
SIG
FRAMING FT
FRAMING FS
1
2
0
1
----
0
----
0
1-8
1-8
1-8
1-8
1-8
1-7
1-8
1-8
1-8
1-8
1-8
1-7
----
----
----
----
----
8
----
----
----
----
----
A
193
386
3
----
0
4
579
----
1
5
772
----
1
6
965
----
0
7
1158
1351
1544
1737
1930
2123
----
1
----
----
----
----
----
8
----
----
----
----
----
B
8
----
1
9
----
1
10
11
12
----
0
----
0
----
192
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
3.2 T1 EXTENDED SUPERFRAME FORMAT
In Extended Superframe Format (ESF), as shown in Figure 22 and Table 34, the multiframe structure is ex-
tended to 24 frames. The timeslot structure is identical to D4 (SF) format. Robbed-bit signaling is accommo-
dated in frame 6 (A-bit), frame 12 (B-bit), frame 18 (C-bit) and frame 24 (D-bit).
The F-bit pattern of ESF contains three functions:
1. Framing Pattern Sequence (FPS), which defines the frame and multiframe boundaries.
2. Facility Data Link (FDL), which allows data such as error-performance to be passed within the T1 link.
3. Cyclic Redundancy Check (CRC), which allows error performance to be monitored and enhances the reli-
ability of the receiver’s framing algorithm.
FIGURE 22. T1 EXTENDED SUPERFRAME FORMAT
SignallingInformation
Bit 7
D
During:
Frame24
C
B
Frame18
Frame12
Frame6
8 Bits per Timeslot
A
Bit 0 Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7
CRC
FDL
FPS
24TimeslotsperFrame
Frame = 193 Bits
TS
1
TS
TS
TS
or
------------------
-------------------
13
24
2
Fs
FR
FR
2
FR
13
FR
23
FR
24
Multiframe
ESF = 12 Frames
------------------
-------------------
1
193
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
TABLE 34: EXTENDED SUPERFRAME FORMAT
BIT USE IN EACH
F-BITS
SIGNALLING CHANNEL
TIMESLOT
FRAME
BIT
FPS
----
----
----
0
DL
m
CRC
----
C1
----
----
----
C2
----
----
----
C3
----
----
----
C4
----
----
----
C5
----
----
----
C6
----
----
TRAFFIC
1-8
1-8
1-8
1-8
1-8
1-7
1-8
1-8
1-8
1-8
1-8
1-7
1-8
1-8
1-8
1-8
1-8
1-7
1-8
1-8
1-8
1-8
1-8
1-7
SIG
----
----
----
----
----
8
16
----
----
----
----
----
A
4
2
1
2
0
----
----
----
----
----
A
----
----
----
----
----
A
193
----
m
3
386
4
579
----
m
5
772
----
----
----
0
6
965
----
m
7
1158
1351
1544
1737
1930
2123
2316
2509
2702
2895
3088
3281
3474
3667
3860
4053
4246
4439
----
----
----
----
----
8
----
----
----
----
----
B
----
----
----
----
----
B
----
----
----
----
----
B
8
----
m
9
----
----
----
1
10
11
12
13
14
15
16
17
18
19
20
21
22
23
----
m
----
m
----
----
----
0
----
----
----
----
----
8
----
----
----
----
----
C
----
----
----
----
----
C
----
----
----
----
----
A
----
m
----
m
----
----
----
1
----
m
----
----
----
----
----
8
----
----
----
----
----
D
----
----
----
----
----
B
----
----
----
----
----
A
----
m
----
----
----
1
----
m
24
----
NOTES:
1. FPS indicates the Framing Pattern Sequence (...001011...)
2. DL indicates the 4kb/s Data Link with message bits m.
3. CRC indicates the cyclic redundancy check with bits C1 to C6
4. Signaling options include 16 state, 4 state and 2 state.
194
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
3.3 SLC 96 FORMAT (SLC)
SLC framing mode allows synchronization to the SLC®96 data link pattern. This pattern described in the
Bellcore TR-TSY-000008, contains both signaling information and a framing pattern that overwrites the Fs bit of
the SF framer pattern. See Table 35.
TABLE 35: SLC®96 FS BIT CONTENTS
FRAME #
FS BIT
FRAME #
26
FS BIT
C2
C3
C4
C5
C6
C7
C8
C9
C10
C11
0
FRAME #
50
FS BIT
0
2
0
0
4
28
52
M1
M2
M3
A1
A2
S1
S2
S3
S4
1
6
1
30
54
8
1
32
56
10
12
14
16
18
20
22
24
1
34
58
0
36
60
0
38
62
0
40
64
1
42
66
1
44
68
1
46
70
C1
48
1
72
0
NOTES:
1. The SLC®96 frame format is similar to that of SF as shown in Table 33 with the exceptions shown
in this table.
2. C1 to C11 are concentrator bit fields.
3. M1 to M3 are Maintenance bit fields.
4. A1 and A2 are alarm bit fields.
5. S1 to S4 are line switch bit fields.
6. The Fs bits in frames 46, 48 and 70 are spoiler bitswhich are used to protect against false muti-
framing.
195
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
4.0 THE DS1 TRANSMIT SECTION
4.1 THE DS1 TRANSMIT PAYLOAD DATA INPUT INTERFACE BLOCK
4.1.1 Description of the Transmit Payload Data Input Interface Block
Each of the eight framers within the XRT84L38 includes a Transmit Payload Data Input Interface block. The func-
tion of this block is to provide an interface to the local Terminal Equipment (for example, a Central Office or switch-
ing equipment) that has data to send to a Far End terminal over a DS1 or E1 transport medium.
The Payload Data Input Interface module (also known as the Back-plane Interface module) supports payload da-
ta to be taken from or presented to the system. In DS1 mode, supported data rates are 1.544Mbit/s, MVIP
2.048Mbit/s, 4.096Mbit/s, 8.192Mbit/s, multiplexed 12.352Mbit/s, multiplexed 16.384Mbit/s, HMVIP 16.384Mbit/s
or H.100 16.384Mbit/s. In E1 mode, supported data rates are XRT84V24 compatible 2.048Mbit/s, MVIP
2.048Mbit/s, 4.096Mbit/s, 8.192Mbit/s, multiplexed 16.384Mbit/s, HMVIP 16.384Mbit/s or H.100 16.384Mbit/s.
The Transmit Payload Data Input Interface block supplies or accepts the following signals to the local Terminal
Equipment circuitry:
• Transmit Serial Data Input (TxSer_n)
• Transmit Serial Clock (TxSerClk_n)
• Transmit Single-frame Synchronization Signal (TxSync_n)
• Transmit Multi-frame Synchronization Signal (TxMSync_n)
• Transmit Time-slot Indicator Clock (TxTSClk_n)
• Transmit Time-slot Indication Bits (TxTSb[4:0]_n)
The Transmit Serial Data is an input pin carrying payload, signaling and sometimes Data Link data supplied by
the local Terminal Equipment to the XRT84L38.
The Transmit Serial Clock is an input or output signal used by the Transmit Payload Data Input Interface block to
latch in incoming serial data from the local Terminal Equipment. The Transmit Clock Inversion bit of the Transmit
Interface Control Register (TICR) determines at which edge of the Transmit Serial Clock would data transition on
the Transmit Serial Data pin occur.
The table below shows configurations of the Transmit Clock Inversion bit of the Transmit Interface Control Regis-
ter (TICR).
TRANSMIT INTERFACE CONTROL REGISTER (TICR) (INDIRECT ADDRESS = 0xn0H, 0x20H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3
Transmit Clock
Inversion
R/W
0 - Serial data transition happens on rising edge of the Transmit Serial Clock.
1 - Serial data transition happens on falling edge of the Transmit Serial Clock.
Throughout the discussion of this datasheet, we assume that serial data transition happens on the rising edge of
the Transmit Serial Clock unless stated otherwise.
The Transmit Single-frame Synchronization signal is either input or output. When configured as input, it indicates
the beginning of a DS1 frame. When configured as output, it indicates the end of a DS1 frame.
The Transmit Multi-frame Synchronization signal is either input or output. When configured as input, it indicates
the beginning of a DS1 multi-frame. When configured as output, it indicates the end of a DS1 multi-frame.
The Transmit Input Clock signal is multiplexed into the Transmit Multi-frame Synchronization pin (TxMSync_n) of
XRT84L38. When the framer is running at High-speed Back-plane Interface mode, the Transmit Input Clock func-
tions as the timing source for the High-speed Back-plane Interface.
By connecting these signals with the local Terminal Equipment, the Transmit Payload Data Input Interface accepts
payload data from the Terminal Equipment and routes it to the Transmit Framer module inside the device.
196
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
4.1.2 Brief Discussion of the Transmit Payload Data Input Interface Block Operating at 1.544Mbit/s
mode
If the framer is operating in normal 1.544Mbit/s Back-plane interface mode for DS1, timing source of the transmit
section can be one of the three clocks:
• Transmit Serial Input Clock
• OSCCLK Driven Divided Clock
• Recovered Receive Line Clock
The Transmit Timing Source Select [1:0] bits of the Clock Select Register (CSR) determine which clock is used as
the timing source. The following table shows configurations of the Transmit Timing Source Select [1:0] bits of the
Clock Select Register.
CLOCK SELECT REGISTER (CSR) (INDIRECT ADDRESS = 0xn0H, 0x00H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1-0
Transmit Timing
Source Select
R/W
These two READ/WRITE bit-fields permit the user to select the timing source of
Transmit section of the framer.
When the Transmit Back-plane interface is operating at a clock rate of 1.544MHz
for T1, these two READ/WRITE bit-fields also determine the direction of Single
Frame Synchronization Pulse (TxSync), Multi-frame Synchronization Pulse
(TxMSync) and Transmit Serial Clock Input (TxSerClk). When the framer is oper-
ating at other Back-plane mode, the Single Frame Synchronization Pulse
(TxSync), Multi-frame Synchronization Pulse (TxMSync) and Transmit Serial
Clock Input (TxSerClk) are all inputs.
00 - The Recovered Receive Line Clock is the timing source of Transmit section
of the framer. When operating at the non-multiplexed 1.544MHz Back-plane
Interface mode, the Single Frame Synchronization Pulse (TxSync), Multi-frame
Synchronization Pulse (TxMSync) and Transmit Serial Clock Input (TxSerClk)
are all outputs. Upon losing of the Recovered Receiver Line Clock, the OSCCLK
Driven Divided clock is automatically chosen to be the timing source of the
Transmit section of the framer.
01 - The Transmit Serial Clock is the timing source of Transmit section of the
framer. When operating at the non-multiplexed 1.544MHz Back-plane Interface
mode, the Single Frame Synchronization Pulse (TxSync), Multi-frame Synchro-
nization Pulse (TxMSync) and Transmit Serial Clock Input (TxSerClk) are all
inputs.
10 - The OSCCLK Driven Divided clock is the timing source of Transmit section
of the framer. When operating at the non-multiplexed 1.544MHz Back-plane
Interface mode, the Single Frame Synchronization Pulse (TxSync), Multi-frame
Synchronization Pulse (TxMSync) and Transmit Serial Clock Input (TxSerClk)
are all outputs. Upon losing of the Recovered Receiver Line Clock, the OSCCLK
Driven Divided clock is automatically chosen to be the timing source of the
Transmit section of the framer.
11 - The Recovered Receive Line Clock is the timing source of Transmit section
of the framer. When operating at the non-multiplexed 1.544MHz Back-plane
Interface mode, the Single Frame Synchronization Pulse (TxSync), Multi-frame
Synchronization Pulse (TxMSync) and Transmit Serial Clock Input (TxSerClk)
are all outputs. Upon losing of the Recovered Receiver Line Clock, the OSCCLK
Driven Divided clock is automatically chosen to be the timing source of the
Transmit section of the framer.
The Transmit Serial Clock (TxSerClk_n), Transmit Single-frame Synchronization Signal (TxSync_n) and Transmit
Multi-frame Synchronization Signal (TxMSync_n) can be either inputs or outputs depend on the timing source of
the Transmit section of the framer.
197
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
With the OSCCLK Driven Divided Clock or the Recovered Receive Line Clock being the timing source of the
transmit section, the Transmit Serial Clock (TxSerClk_n), Transmit Single-frame Synchronization Signal
(TxSync_n) and Transmit Multi-frame Synchronization Signal (TxMSync_n) are all outputs.
With the timing source of the transmit section being the Transmit Serial Input Clock, the Transmit Serial Clock
(TxSerClk_n), Transmit Single-frame Synchronization Signal (TxSync_n) and Transmit Multi-frame Synchroniza-
tion Signal (TxMSync_n) are all inputs.
The following table illustrates the input and output nature of these signals for different Transmit timing sources.
TABLE 36: SIGNALS FOR DIFFERENT TRANSMIT TIMING SOURCES
TRANSMIT TIMING SOURCE
Terminal Equipment Driven TxSerClk
OSCCLK Driven Divided Clock
Recovered Receive Line Clock
TXSERCLK_N
Input
TXSYNC_N
Input
TXMSYNC_N
Input
Output
Output
Output
Output
Output
Output
The Transmit Time-slot Indication Bits (TxTSb[4:0]_n) are multiplexed I/O pins. The functionality of these pins is
governed by the value of Transmit Fractional T1 Input Enable bit of the Transmit Interface Control Register (TICR).
The following table illustrates the configurations of the Transmit Fractional DS1 Input Enable bit.
TRANSMIT INTERFACE CONTROL REGISTER (TICR) (INDIRECT ADDRESS = 0xn0H, 0x20H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
4
Transmit
Fractional DS1
Input Enable
R/W
0 - The Transmit Time-slot Indication bits (TxTSb[4:0] are outputting five-bit
binary values of Time-slot number (0-23) being accepted and processed by the
Transmit Payload Data Input Interface block of the framer.
The Transmit Time-slot Indicator Clock signal (TxTSClk_n) is a 192KHz clock
that pulses HIGH for one DS1 bit period whenever the Transmit Payload Data
Input Interface block is accepting the LSB of each of the twenty-four time slots.
1 - The TxTSb[0]_n bit becomes the Transmit Fractional T1 Input signal
(TxFrTD_n) which carries Fractional DS1 payload data into the framer.
The TxTSb[1]_n bit becomes the Transmit Signaling Data Input signal (TxSig_n)
which is used to insert robbed-bit signaling data into the outbound DS1 frame.
The TxTSb[2]_n bit serially outputs all five-bit binary values of the Time Slot
number (0-23) being accepted and processed by the Transmit Payload Data
Input Interface block of the framer.
The TxTSb[3]_n bit becomes the Transmit Overhead Synchronization Pulse
(TxOHSync_n) which is used to output an Overhead Synchronization Pulse that
indicates the first bit of each DS1multi-frame.
The TxTSClk_n will output gaped fractional DS1 clock that can be used by Ter-
minal Equipment to clock out Fractional DS1 payload data at rising edge of the
clock. Or,The TxTSClk_n pin will be a clock enable signal to Transmit Fractional
DS1 Input signal (TxFrTD_n) when the un-gaped Transmit Serail Input Clock
(TxSerClk_n) is used to clock in Fractional DS1 Payload Data into the framer.
When configured to operate in normal condition (that is, when the Transmit Fractional T1 Input Enable bit is equal
to zero), these bits reflect the five-bit binary value of the Time Slot number (0 - 23) being accepted and processed
by the Transmit Payload Data Input Interface block of the framer. TxTSb[4] represents the MSB of the binary value
and TxTSb[0] represents the LSB.
When the Transmit Fractional T1 Input Enable bit is equal to one, the TxTSb[0]_n bit becomes the Transmit Frac-
tional T1 Input signal (TxFrTD_n). This input pin carries Fractional T1 Input data to be inserted into the outbound
DS1 data stream. The Fraction T1 Input Interface allows certain time-slots of outbound DS1 data stream to have
a different source other than the local Terminal Equipment. Function of the Fractional T1 Input signal will be dis-
cussed in details in later sections.
198
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
When the Transmit Fractional T1 Input Enable bit is equal to one, the TxTSb[1]_n bit becomes the Transmit Sig-
naling Data Input signal (TxSig_n). These input pins can be used to insert robbed-bit signaling data into the out-
bound DS1 frame. Function of the Transmit Signaling Data Input signal will be discussed in details in later sec-
tions.
When the Transmit Fractional T1 Input Enable bit is equal to one, the TxTSb[2]_n bit serially outputs all five-bit bi-
nary values of the Time Slot number (0-23) being accepted and processed by the Transmit Payload Data Input In-
terface block of the framer. MSB of the binary value is presented first and the LSB is presented last.
When the Transmit Fractional T1 Input Enable bit is equal to one, the TxTSb[3]_n bit becomes the Transmit Over-
head Synchronization Pulse (TxOHSync_n). These pins can be used to output an Overhead Synchronization
Pulse that indicates the first bit of each DS1multi-frame. Function of the Transmit Overhead Synchronization Out-
put signal will be discussed in details in later sections.
The TxTSb[4]_n bit is not multiplexed.
The table below shows functionality of the TxTSb[3:0] bits when the Transmit Fractional T1 Input bit is set to differ-
ent values.
TABLE 37: THE TXTSB[3:0] BITS WHEN THE TRANSMIT FRACTIONAL T1 INPUT BIT IS SET TO DIFFERENT VALUES
TRANSMIT FRACTIONAL T1 INPUT BIT = 0
TRANSMIT FRACTIONAL T1 INPUT BIT = 1
TxTSb[0]
TxTSb[1]
TxTSb[2]
TxTSb[3]
Output
Output
Output
Output
TxFrTD
TxSig
Input
Input
TxTS
Output
Output
TxOHSync
The Transmit Time-slot Indicator Clock signal (TxTSClk_n) is a multi-function output pin. When configured to op-
erate in normal condition (that is, when the Transmit Fractional T1 Input Enable bit is equal to zero), the
TxTSClk_n is a 192KHz clock that pulses HIGH for one DS1 bit period whenever the Transmit Payload Data Input
Interface block is accepting the LSB of each of the twenty-four time slots. The local Terminal Equipment should
use this clock signal to sample the TxTSb[0] through TxTSb[4] bits and identify the time-slot being processed via
the Transmit Section of the framer.
When the Transmit Fractional T1 Input Enable bit is equal to one, the TxTSClk_n will output gaped fractional DS1
clock at time-slots where Fractional T1 Input data is present. This clock can be used by Terminal Equipment to
clock out Fractional DS1 payload data at rising edge of the clock. The framer will then input Fractional DS1 pay-
load data using falling edge of the clock. Otherwise, this pin can be configured as a clock enable signal to Trans-
mit Fractional DS1 Input signal (TxFrTD_n) if the framer is set accordingly. In this way, Fractional DS1 payload da-
ta is clocked into the framer using un-gaped Transmit Serail Input Clock (TxSerClk_n). A detailed discussion of
the Fractional DS1 Payload Data Input Interface can be found in later sections.
Both the Transmit Time-slot Indicator Clock (TxTSClk_n) and the Transmit Time-slot Indication Bits (TxTS-
bb[4:0]_n) are output signals in normal 1.544Mbit/s Back-plane mode regardless of the timing source of the
Transmit Section of framer.
4.1.2.1 Connect the Transmit Payload Data Input Interface block to the Local Terminal Equipment if
Transmit Timing Source = TxSerClk_n
By setting the Transmit Timing Source [1:0] bits of the Clock Select Register to 01, the TxSerClk_n input signal is
configured to be the timing source for the Transmit section of the framer. The Terminal Equipment should supply
an external free-running clock with frequency of 1.544MHz to the TxSerClk_n input pin. The Transmit Single-
frame Synchronization signal and the Transmit Multi-frame Synchronization signal are inputs to the framer.
The Transmit Single-frame Synchronization signal should pulse “High” for one DS1 bit period (648ns) at the
Framing bit position of each DS1 frame. By sampling the “High” pulse on the Transmit Single-frame Synchroniza-
tion signal, the framer can position the beginning of a DS1 frame.
199
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The Transmit Multi-frame Synchronization signal should pulse HIGH for one DS1 bit period (648ns) at the Fram-
ing bit position of the first frame of a DS1 multi-frame. By sampling the HIGH pulse on the Transmit Multi-frame
Synchronization signal, the framer can position the beginning of a DS1 super-frame.
It is the responsibility of the Terminal Equipment to provide serial input data through the TxSer_n pin aligned with
the Transmit Single-frame Synchronization signal and the Transmit Multi-frame Synchronization signal. See
Figure 23 below for how to connect the Transmit Payload Data Input Interface block to the local Terminal Equip-
ment with the Transmit Serial clock being the timing source of transmit section.
FIGURE 23. INTERFACING XRT84L38 TO LOCAL TERMINAL EQUIPMENT WITH TXSERCLK_N AS TRANSMIT TIMING
SOURCE
XRT84L38
TxSerClk_0
TxSer_0
Transmit
TxMSync_0
TxSync_0
Payload
Data Input
Interface
Chn 0
TxTSClk_0
TxTSb[4:0]_0
Terminal
Equipment
TxSerClk_7
TxSer_7
Transmit
Payload
Data Input
Interface
Chn 7
TxMSync_7
TxSync_7
TxTSClk_7
TxTSb[4:0]_7
200
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
Figure 24 shows waveforms of the signals (TxSerClk_n, TxSer_n, TxSync_n, TxTSClk_n and TxTSb[4:0]_n) that
connect the Transmit Payload Data Input Interface block to the local Terminal Equipment with the Transmit Serial
clock being the timing source of transmit section.
FIGURE 24. WAVEFORMS OF THE SIGNALS THAT CONNECT THE TRANSMIT PAYLOAD DATA INPUT INTERFACE BLOCK
TO THE LOCAL TERMINAL EQUIPMENT WITH THE TRANSMIT SERIAL CLOCK BEING THE TIMING SOURCE OF THE
TRANSMIT SECTION
Timeslot 0
Timeslot 5
Timeslot 6
Timeslot 23
TxSerClk
TxSerClk (INV)
TxSer
Input Data
Input Data
Input Data
Input Data
F
F
TxSync(input)
TxTSClk
TxTSb[4:0]
Timeslot #0
A B C D
Timeslot #5
Timeslot #6
Timeslot #23
TxTSb[0]/TxSig
TxTSClk
A B C D
A B C D
A B C D
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
TxTSb[4:0]
TxTSb[1]/TxFrTD
1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8
4.1.2.2 Connect the Transmit Payload Data Input Interface block to the Local Terminal Equipment if
the Transmit Timing Source = OSCCLK
By setting the Transmit Timing Source [1:0] bits of the Clock Select Register (CSR) to 10, the OSCCLK Driven Di-
vided clock is configured to be the timing source for the Transmit section of the framer. A free-running clock
should apply to the OSCCLK input pin with frequencies of 12.352MHz, 24.704MHz and 49.408MHz depending
on the setting of OSCCLK Frequency Select [1:0] bits of the Clock Select Register (CSR).
The free-running OSCCLK is divided inside the XRT84L38 and routed to all eight framers. This OSCCLK Driven
Divided Clock has to be 12.352MHz in frequency. When these bits are set to 00, the framer will internally divide
the incoming OSCCLK by one. Therefore, the external oscillator clock applied to the OSCCLK pin should be
12.352MHz. When these bits are set to 01, the framer will internally divide the incoming OSCCLK by two. There-
fore, the external oscillator clock applied to the OSCCLK pin should be 24.704MHz. When these bits are set to
10, the framer will internally divide the incoming OSCCLK by four. Therefore, the external oscillator clock applied
to the OSCCLK pin should be 49.408MHz.
The following table shows configurations of the OSCCLK Frequency Select [1:0] bits of the Clock Select Register.
201
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
CLOCK SELECT REGISTER (CSR) (INDIRECT ADDRESS = 0xn0H, 0x00H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3-2
OSCCLK
Frequency
Select
R/W
OSCCLK Frequency Select:
These two READ/WRITE bit-fields permit the user to select internal clock divid-
ing logic of the framer depending on the frequency of incoming oscillator clock
(OSCCLK). The frequency of internal clock used by the framer should be
12.352MHz.
00 - The framer will internally divide the incoming OSCCLK by one. Therefore,
the external oscillator clock applied to the OSCCLK pin should be 12.352MHz.
01 - The framer will internally divide the incoming OSCCLK by two. Therefore,
the external oscillator clock applied to the OSCCLK pin should be 24.704MHz.
10 - The framer will internally divide the incoming OSCCLK by four. Therefore,
the external oscillator clock applied to the OSCCLK pin should be 49.408MHz.
The Transmit Serial clock signal pin (TxSerClk_n) is output from the framer. The framer outputs a 1.544MHz clock
through this pin to the local Terminal Equipment. The Transmit Single-frame Synchronization signal and the
Transmit Multi-frame Synchronization signal are also automatically configured to be output signals.
The Transmit Single-frame Synchronization signal should pulse HIGH for one DS1 bit period (648ns) at the last
bit position of each DS1 frame. By triggering on the HIGH pulse on the Transmit Single-frame Synchronization
signal, the local Terminal Equipment can identify the end of a DS1 frame and should start inserting payload data
of the next DS1 frame to the framer.
The Transmit Multi-frame Synchronization signal should pulse HIGH for one DS1 bit period (648ns) at the last bit
position of the last frame of a DS1 multi-frame. By triggering on the HIGH pulse on the Transmit Multi-frame Syn-
chronization signal, the local Terminal Equipment can identify the end of a DS1 super-frame and should start in-
serting payload data of the next DS1 multi-frame into the framer.
202
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
See Figure 25 for how to connect the Transmit Payload Data Input Interface block to the local Terminal Equipment
with the OSCCLK Driven Divided clock as the timing source of transmit section.
FIGURE 25. INTERFACING XRT84L38 TO THE LOCAL TERMINAL EQUIPMENT WITH THE OSCCLK DRIVEN DIVIDED
CLOCK AS TRANSMIT TIMING SOURCE
XRT84L38
TxSerClk_0
TxSer_0
Transmit
TxMSync_0
TxSync_0
Payload
Data Input
Interface
Chn 0
TxTSClk_0
TxTSb[4:0]_0
Terminal
Equipment
TxSerClk_7
TxSer_7
Transmit
Payload
Data Input
Interface
Chn 7
TxMSync_7
TxSync_7
TxTSClk_7
TxTSb[4:0]_7
OSCCLK
203
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
Figure 26 shows waveforms of the signals (TxSerClk_n, TxSer_n, TxSync_n, TxTSClk_n and TxTSb[4:0]_n) that
connect the Transmit Payload Data Input Interface block to the local Terminal Equipment with the OSCCLK Driven
Divided clock as the timing source of transmit section.
FIGURE 26. WAVEFORMS OF THE SIGNALS CONNECTING THE TRANSMIT PAYLOAD DATA INPUT INTERFACE BLOCK TO
THE LOCAL TERMINAL EQUIPMENT WITH THE OSCCLK DRIVEN DIVIDED CLOCK AS THE TIMING SOURCE OF THE
TRANSMIT SECTION
Timeslot 0
Timeslot 5
Timeslot 6
Timeslot 23
TxSerClk
TxSerClk (INV)
TxSer
Input Data
Input Data
Input Data
Input Data
F
F
TxSync(output)
TxTSClk
TxTSb[4:0]
Timeslot #6
Timeslot #0
A B C D
Timeslot #5
Timeslot #23
TxTSb[0]/TxSig
TxTSb[0]/TxSig
A B C D
A B C D
A B C D
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
TxTSClk
TxTSb[1]/TxFrTD
1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8
4.1.2.3 Connect the Transmit Payload Data Input Interface block to the Local Terminal Equipment
for Loop-timing applications
If the Transmit Timing Source [1:0] bits of the Clock Select Register are set to 00 or 11, the Recovered Receive
Line Clock is configured to be the timing source for the Transmit section of the framer. This is also known as the
Loop-timing mode.
If the Clock Loss Detection Enable bit of the Clock Select Register is set to one, and if the Recovered Receive
Line Clock from the LIU is lost, the framer will automatically begin to use the OSCCLK Driven Divided clock as
transmit timing source until the LIU is able to regain clock recovery.
204
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The following table shows configuration of the Clock Loss Detection Enable bit of the Clock Select Register
(CSR).
CLOCK SELECT REGISTER (CSR) (INDIRECT ADDRESS = 0xn0H, 0x00H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
4
Clock Loss
Detection
Enable
R/W
Clock Loss Detection Enable:
This READ/WRITE bit-field permits the user to enable the Clock Loss Detection
logic for the framer when the Recovered Receive Line Clock is used as transmit
timing source of the framer.
0 - The framer disables the Clock Loss Detection logic.
1 - The framer enables the Clock Loss Detection logic. If the Recovered Receive
Line Clock is used as transmit timing source of the framer, and if clock recovered
from the LIU is lost, the framer can detect loss of the Recovered Receive Line
Clock. Upon detecting of this occurrence, the framer will automatically begin to
use the OSCCLK Driven Divided clock as transmit timing source until the LIU is
able to regain clock recovery.
NOTE: This bit-field is ignored if the TxSerClk or the OSCCLK Driven Divided
Clock is chosen to be the timing source of Transmit Section of the framer.
The Transmit Serial Clock signal pin (TxSerClk_n) is output from the framer. The XRT84L38 routes the Recov-
ered Receive Line Clock internally across the framer and output through the Transmit Serial Clock signal pin to
the local Terminal Equipment. The Transmit Single-frame Synchronization signal and the Transmit Multi-frame
Synchronization signal are automatically configured to be output signals.
The Transmit Single-frame Synchronization signal should pulse HIGH for one DS1 bit period (648ns) at the last
bit position of each DS1 frame. By triggering on the HIGH pulse on the Transmit Single-frame Synchronization
signal, the local Terminal Equipment can identify the end of a DS1 frame and should start inserting payload data
of the next DS1 frame to the framer.
The Transmit Multi-frame Synchronization signal should pulse HIGH for one DS1 bit period (648ns) at the last bit
position of the last frame of a DS1 multi-frame. By triggering on the HIGH pulse on the Transmit Multi-frame Syn-
chronization signal, the local Terminal Equipment can identify the end of a DS1 super-frame and should start in-
serting payload data of the next DS1 multi-frame into the framer.
205
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
See Figure 27 for how to connect the Transmit Payload Data Input Interface block to the local Terminal Equipment
with the Recovered Receive Line Clock being the timing source of transmit section.
FIGURE 27. INTERFACING XRT84L38 TO LOCAL TERMINAL EQUIPMENT WITH RECOVERED RECEIVE LINE CLOCK AS
TRANSMIT TIMING SOURCE
XRT84L38
TxSerClk_0
RxLineClk_0
TxSer_0
Transmit
Payload
Data Input
Interface
Chn 0
TxMSync_0
TxSync_0
TxTSClk_0
TxTSb[4:0]_0
Terminal
Equipment
TxSerClk_7
TxSer_7
Transmit
Payload
Data Input
Interface
Chn 7
TxMSync_7
TxSync_7
TxTSClk_7
TxTSb[4:0]_7
RxLineClk_7
206
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The following Figure 28 shows waveforms of the signals (TxSerClk_n, TxSer_n, TxSync_n, TxTSClk_n and
TxTSb[4:0]_n) that connecting the Transmit Payload Data Input Interface block to the local Terminal Equipment
with the Recovered Receive Line Clock being the timing source of transmit section.
FIGURE 28. WAVEFORMS OF THE SIGNALS CONNECTING THE TRANSMIT PAYLOAD DATA INPUT INTERFACE BLOCK TO
THE LOCAL TERMINAL EQUIPMENT WITH THE RECOVERED RECEIVE LINE CLOCK BEING THE TIMING SOURCE OF THE
TRANSMIT SECTION
Timeslot 0
Timeslot 5
Timeslot 6
Timeslot 23
TxSerClk
TxSerClk (INV)
TxSer
Input Data
Input Data
Input Data
Input Data
F
F
TxSync(output)
TxTSClk
TxTSb[4:0]
Timeslot #6
Timeslot #0
A B C D
Timeslot #5
Timeslot #23
TxTSb[0]/TxSig
TxTSb[0]/TxSig
A B C D
A B C D
A B C D
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
TxTSClk
TxTSb[1]/TxFrTD
1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8
4.1.3 Brief Discussion of the Transmit High-Speed Back-Plane Interface
The High-speed Back-plane Interface supports payload data to be taken from or presented to the Terminal Equip-
ment at a rate higher than 1.544Mbit/s. In DS1 mode, supported High-speed data rates are MVIP 2.048Mbit/s,
4.096Mbit/s, 8.192Mbit/s, multiplexed 12.352Mbit/s, multiplexed 16.384Mbit/s, HMVIP 16.384Mbit/s or H.100
16.384Mbit/s. The Transmit Multiplex Enable bit and the Transmit Interface Mode Select [1:0] bits of the Transmit
Interface Control Register (TICR) determine the Transmit Back-plane Interface data rate.
The following table shows configurations of the Transmit Multiplex Enable bit and the Transmit Interface Mode Se-
lect [1:0] bits of the Transmit Interface Control Register (TICR).
TRANSMIT INTERFACE CONTROL REGISTER (TICR) (INDIRECT ADDRESS = 0xn0H, 0x20H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
2
Transmit
Multiplex Enable
R/W
0 - The Transmit Back-plane Interface block is configured to non-channel-multi-
plexed mode.
1 - The Transmit Back-plane Interface block is configured to channel-multiplexed
mode
1-0
Transmit
Interface Mode
Select
R/W
When combined with the Transmit Multiplex Enable bit, these bits determine the
Transmit Back-plane Interface data rate.
207
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The table below shows the combinations of Transmit Multiplex Enable bit and Transmit Interface Mode Select
[1:0] bits and the resulting Transmit Back-plane Interface data rates.
TABLE 38: TRANSMIT MULTIPLEX ENABLE BIT AND TRANSMIT INTERFACE MODE SELECT [1:0] BITS WITH THE
RESULTING TRANSMIT BACK-PLANE INTERFACE DATA RATES
TRANSMIT MULTIPLEX ENABLE
BIT
TRANSMIT INTERFACE MODE
SELECT BIT 1
TRANSMIT INTERFACE MODE
SELECT BIT 0
BACK-PLANE INTERFACE
DATA RATE
0
0
0
0
1
1
1
1
0
0
1
1
0
0
1
1
0
1
0
1
0
1
0
1
1.544Mbit/s
MVIP 2.048Mbit/s
4.096Mbit/s
8.192Mbit/s
Multiplexed 12.352Mbit/s
Bit Multiplexed 16.384Mbit/s
HMVIP 16.384Mbit/s
H.100 16.384Mbit/s
When the Transmit Multiplex Enable bit is set to zero, the framer is configured in non-channel-multiplexed mode.
The possible data rates are 1.544Mbit/s, MVIP 2.048Mbit/s, 4.096Mbit/s and 8.192Mbit/s. In non-channel-multi-
plexed mode, payload data of each channel are taken from the Terminal Equipment separately. Each channel us-
es its own Transmit Serial Clock, Transmit Serial Data, Transmit Single-frame Synchronization signal and Trans-
mit Multi-frame Synchronization signal as interface between the framer and the Terminal Equipment. Section
4.1.2.1, 4.1.2.2 and 4.1.2.3 provide details on how to connect the Transmit Payload Data Interface block with the
Terminal Equipment when the Back-plane interface data rate is 1.544Mbit/s.
When the Back-plane interface data rate is MVIP 2.048Mbit/s, 4.096Mbit/s and 8.192Mbit/s, the Transmit Serial
Clock, Transmit Serial Data, Transmit Single-frame Synchronization signal and Transmit Multi-frame Synchroniza-
tion signal are all configured as inputs. The Transmit Serial Clock is always an input clock with frequency of 1.544
MHz for all data rates. The TxMSync_n signal is configured as the Transmit Input Clock with frequencies of 2.048
MHz, 4.096 MHz and 8.192 MHz respectively. It serves as the primary clock source for the High-speed Back-
plane Interface.
The table below summaries the clock frequencies of TxSerClk_n and TxInClk_n inputs when the framer is operat-
ing in non-multiplexed High-speed Back-plane mode.
TRANSMIT MULTIPLEX ENABLE BIT = 0
TRANSMIT INTERFACE
MODE SELECT BIT 1
TRANSMIT INTERFACE
MODE SELECT BIT 0
BACK-PLANE
INTERFACE DATA RATE
TXSERCLK
TXMSYNC/TXINCLK
0
0
1
1
0
1
0
1
1.544Mbit/s
MVIP 2.048Mbit/s
4.096Mbit/s
1.544 MHz
1.544 MHz
1.544 MHz
1.544 MHz
-
2.048 MHz
4.096 MHz
8.192 MHz
8.192Mbit/s
When the Transmit Multiplex Enable bit is set to one, the framer is configured in channel-multiplexed mode. The
possible data rates are multiplexed 12.352Mbit/s, bit-multiplexed 16.384Mbit/s, HMVIP 16.384Mbit/s and H.100
16.384Mbit/s. In channel-multiplexed mode, every four channels share the Transmit Serial Data and Transmit Sin-
gle-frame Synchronization signal of one channel as interface between the framer and the local Terminal Equip-
ment. The TxMSync_n signal of one channel is configured as the Transmit Input Clock with frequencies of 12.352
MHz or 16.384. It serves as the primary clock source for the High-speed Back-plane Interface.
208
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
Payload and signaling data of Channel 0-3 are multiplexed onto the Transmit Serial Data pin of Channel 0. Pay-
load and signaling data of Channel 4-7 are multiplexed onto the Transmit Serial Data pin of Channel 4. The Trans-
mit Single-frame Synchronization signal of Channel 0 pulses HIGH at the beginning of the frame with data from
Channel 0-3 multiplexed together. The Transmit Single-frame Synchronization signal of Channel 4 pulses HIGH
at the beginning of the frame with data from Channel 4-7 multiplexed together. It is responsibility of the Terminal
Equipment to align the multiplexed transmit serial data with the Transmit Single-frame Synchronization pulse. Ad-
ditionally, each channel requires the local Terminal Equipment to provide a free-running 1.544 MHz clock into the
Transmit Serial Clock input.
The table below summaries the clock frequencies of TxSerClk_n and TxInClk_n inputs when the framer is operat-
ing in multiplexed High-speed Back-plane mode.
TRANSMIT MULTIPLEX ENABLE BIT = 1
TRANSMIT INTERFACE
MODE SELECT BIT 1
TRANSMIT INTERFACE
MODE SELECT BIT 0
BACK-PLANE INTERFACE
DATA RATE
TXSERCLK
TXMSYNC/TXINCLK
0
0
1
1
0
1
0
1
Multiplexed 12.352Mbit/s
Bit-multiplexed 16.384Mbit/s
HMVIP 16.384Mbit/s
1.544 MHz
1.544 MHz
1.544 MHz
1.544 MHz
12.352 MHz
16.384 MHz
16.384 MHz
16.384 MHz
H.100 16.384Mbit/s
The Transmit Serial Clock is always running at 1.544MHz for all the High-speed Back-plane Interface modes. It is
automatically the timing source of the Transmit Section of the framer in High-speed Back-plane Interface mode.
The Transmit Single-frame Synchronization signal should pulse HIGH or LOW for one bit period at the Framing bit
position of each DS1 frame. Length of the bit period depends on data rate of the High-speed Back-plane Inter-
face. The Transmit Synchronization Pulse Low bit of the Transmit Interface Control Register (TICR) determines
whether the Transmit Single-frame Synchronization signal is HIGH active or LOW active.
The table below shows configurations of the Transmit Synchronization Pulse LOW bit of the Transmit Interface
Control Register (TICR).
TRANSMIT INTERFACE CONTROL REGISTER (TICR) (INDIRECT ADDRESS = 0xn0H, 0x20H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3
Transmit
Synchronization
Pulse LOW
R/W
0 - The Transmit Single-frame Synchronization signal will pulse HIGH indicat-
ing the beginning of a DS1 frame when the High-speed Back-plane Interface
is running at a mode other than the 1.544Mbit/s.
1 - The Transmit Single-frame Synchronization signal will pulse LOW indicat-
ing the beginning of a DS1 frame when the High-speed Back-plane Interface
is running at a mode other than the 1.544Mbit/s.
Throughout the discussion of this datasheet, we assume that the Transmit Single-frame Synchronization signal
pulses HIGH unless stated otherwise.
The TxMSync_n signal, which is a multiplexed I/O pin, no longer functions as the Transmit Multi-frame Synchroni-
zation Signal. Indeed, it becomes the Transmit Input Clock signal (TxInClk) of the High-speed Back-plane Inter-
face of the framer. The local Terminal Equipment should provide a free-running clock with the same frequency as
the High-speed Back-plane Interface to this input pin.
The following sections discuss details of how to operate the framer in different Back-plane interface speed mode
and how to connect the Transmit Payload Data Input Interface block to the local Terminal Equipment.
209
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
4.1.3.1 T1 Transmit Input Interface - MVIP 2.048 MHz
When the Transmit Multiplex Enable bit is set to zero and the Transmit Interface Mode Select [1:0] bits are set to
01, the Transmit Back-plane interface of framer is running at a data rate of 2.048Mbit/s.
The interface consists of the following pins:
• Data input (TxSer_n)
• Transmit Serial Clock Input signal (TxSerClk_n)
• Transmit Single-frame Synchronization Input signal (TxSync_n)
• Transmit Input Clock (TxInClk_n)
• Transmit Time-slot Indication clock (TxTSClk_n)
• Transmit Time Slot indicator bits (TxTSb[4:0]_n)
The Transmit Back-plane interface is accepting data through TxSer_n at an E1 equivalent data rate of 2.048Mbit/
s. The local Terminal Equipment supplies a free-running 2.048MHz clock to the Transmit Input Clock pin of the
framer. The local Terminal Equipment also provides synchronized payload data at rising edge of the clock. The
Transmit High-speed Back-plane Interface of the framer then latches incoming serial data at falling edge of the
Transmit Input Clock. The local Terminal Equipment should pump in data grouped in 256-bit frame 8000 times ev-
ery second. Each frame consists of thirty-two octets as in E1. The local Terminal Equipment maps a 193-bit T1
frame into this 256-bit format as described below:
1. The Framing (F-bit) is mapped into MSB of the first E1 Time-slot. The local Terminal Equipment will stuff
the rest seven bits of the first octet with "don't care" bits that would be ignored by the framer.
2. Payload data of T1 Time-slot 0, 1 and 2 are mapped into E1 Time-slot 1, 2 and 3.
3. The local Terminal Equipment will stuff E1 Time-slot 4 with eight "don't care" bits that would be ignored by
the framer.
4. Following the same rules of Step 2 and 3, the local Terminal Equipment maps every three time-slots of T1
payload data into four E1 time-slots.
The mapping of T1 frame into E1 framing format is shown in the table below.
TABLE 39: THE MAPPING OF T1 FRAME INTO E1 FRAMING FORMAT
T1
E1
T1
E1
T1
E1
T1
E1
F-Bit
TS0
TS0
TS1
TS1
TS2
TS2
TS3
Don't Care Bits
TS4
TS3
TS5
TS4
TS6
TS5
TS7
Don't Care Bits
TS8
TS6
TS7
TS8
Don't Care Bits
TS12
TS9
TS10
TS14
TS16
TS22
TS22
TS30
TS11
TS15
TS17
TS23
TS23
TS31
TS9
TS10
TS13
TS18
TS19
TS26
TS11
TS14
TS19
TS20
TS27
TS13
TS15
TS21
TS21
TS29
Don't Care Bits
TS16
TS12
TS17
TS18
TS25
Don't Care Bits
TS20
Don't Care Bits
TS24
Don't Care Bits
TS28
The Transmit Single-frame Synchronization input signal (TxSync_n) should pulse HIGH at the beginning (F-bit
position) of the 256-bit frame indicating start of the frame. By sampling the HIGH pulse on the Transmit Single-
frame Synchronization signal, the framer can position the beginning of a DS1 frame. It is responsibility of the local
Terminal Equipment to align the Transmit Single-frame Synchronization signal with serial data stream going into
the framer.
Inside the framer, all the "don't care" bits will be stripped away. The framing bits, signaling and payload data are
then processed by the framer and send to LIU interface. The local Terminal Equipment provides a free-running
1.544MHz clock to the Transmit Serial Input clock. The framer will use this clock to carry the processed payload
and signaling data to the transmit section of the device.
210
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
See Figure 29 below for how to interface the local Terminal Equipment with the Transmit Payload Data Input Inter-
face block of the framer in MVIP 2.048Mbit/s mode.
FIGURE 29. INTERFACING XRT84L38 TO THE LOCAL TERMINAL EQUIPMENT USING MVIP 2.048MBIT/S DATA BUS
XRT84L38
TxSerClk_0
Transmit
TxSer_0
Payload
TxInClk_0 (2.048MHz) Data Input
Interface
Chn 0
TxSync_0
Terminal
Equipment
TxSerClk_7
Transmit
TxSer_7
Payload
Data Input
Interface
Chn 7
TxInClk_7 (2.048MHz)
TxSync_7
The timing diagram of input signals to the framer when running at MVIP 2.048Mbit/s mode is shown in Figure 30.
FIGURE 30. TIMING DIAGRAM OF THE INPUT SIGNALS TO THE FRAMER WHEN RUNNING AT MVIP 2.048MBIT/S MODE
TxSerClk
TxSerClk (INV)
TxSer
F
Don't Care
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
Don't Care
Don't Care
1 2 3 4 5 6 7 8
TxSync(input)
TxSync(input)
MVIP mode
Don't Care
Don't Care
A B C D
Don't Care
A B C D
TxTSb[0]/TxSig
Don't Care
A B C D
A B C D
Note: The following signals are not aligned with the signals shown above. The TxTSClk is derived from 1.544MHz transmit clock.
TxSyncFrd=0
TxTSClk
Don't Care
Don't Care
1 2 3 4 5 6 7 8
Don't Care
Don't Care
1 2 3 4 5 6 7 8
TxTSb[1]/TxFrTD
TxSyncFrd=1
1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8
TxTSb[1]/TxFrTD
TxTSClk
4.1.3.2 T1 Transmit Input Interface - 4.096 MHz
This interface mode is the same as running at 2.048 MHz. The only difference is that the Transmit Input Clock
runs two times faster at 4.096 MHz.
When the Transmit Multiplex Enable bit is set to zero and the Transmit Interface Mode Select [1:0] bits are set to
10, the Transmit Back-plane interface of framer is running at a clock rate of 4.096MHz.
211
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The interface consists of the following pins:
• Data input (TxSer_n)
• Transmit Serial Clock Input signal (TxSerClk_n)
• Transmit Single-frame Synchronization Input signal (TxSync_n)
• Transmit Input Clock (TxInClk_n)
• Transmit Time-slot Indication clock (TxTSClk_n)
• Transmit Time Slot indicator bits (TxTSb[4:0]_n)
The Transmit Back-plane interface is still accepting data through TxSer_n at an E1 equivalent data rate of
2.048Mbit/s. However, the local Terminal Equipment supplies a free-running 4.096MHz clock to the Transmit Input
Clock pin of the framer. The local Terminal Equipment provides synchronized payload data at every other rising
edge of the Transmit Input Clock. The Transmit High-speed Back-plane Interface of the framer then latches in-
coming serial data at every other falling edge of the clock. The local Terminal Equipment should pump in data
grouped in 256-bit frame 8000 times every second. Each frame consists of thirty-two octets as in E1. The local
Terminal Equipment maps a 193-bit T1 frame into this 256-bit format as described below:
1. The Framing (F-bit) is mapped into MSB of the first E1 Time-slot. The local Terminal Equipment will stuff
the rest seven bits of the first octet with "don't care" bits that would be ignored by the framer.
2. Payload data of T1 Time-slot 0, 1 and 2 are mapped into E1 Time-slot 1, 2 and 3.
3. The local Terminal Equipment will stuff E1 Time-slot 4 with eight "don't care" bits that would be ignored by
the framer.
4. Following the same rules of Step 2 and 3, the local Terminal Equipment maps every three time-slots of T1
payload data into four E1 time-slots.
The mapping of T1 frame into E1 framing format is shown in the table below.
TABLE 40: THE MAPPING OF T1 FRAME INTO E1 FRAMING FORMAT
T1
E1
T1
E1
T1
E1
T1
E1
F-BIT
TS0
TS0
TS1
TS1
TS2
TS2
TS3
DON'T CARE BITS
TS4
TS3
TS5
TS4
TS6
TS5
TS7
Don't Care Bits
TS8
TS6
TS7
TS8
Don't Care Bits
TS12
TS9
TS10
TS14
TS16
TS22
TS22
TS30
TS11
TS15
TS17
TS23
TS23
TS31
TS9
TS10
TS13
TS18
TS19
TS26
TS11
TS14
TS19
TS20
TS27
TS13
TS15
TS21
TS21
TS29
Don't Care Bits
TS16
TS12
TS17
TS18
TS25
Don't Care Bits
TS20
Don't Care Bits
TS24
Don't Care Bits
TS28
The Transmit Single-frame Synchronization input signal (TxSync_n) should pulse HIGH at the beginning (F-bit
position) of the 256-bit frame indicating start of the frame. By sampling the HIGH pulse on the Transmit Single-
frame Synchronization signal, the framer can position the beginning of a DS1 frame. It is responsibility of the local
Terminal Equipment to align the Transmit Single-frame Synchronization signal with serial data stream going into
the framer.
Inside the framer, all the "don't care" bits will be stripped away. The framing bits, signaling and payload data are
then processed by the framer and send to LIU interface. The local Terminal Equipment provides a free-running
1.544MHz clock to the Transmit Serial Input clock. The framer will use this clock to carry the processed payload
and signaling data to the transmit section of the device.
212
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
See Figure 31 below for how to interface the local Terminal Equipment with the Transmit Payload Data Input Inter-
face block of the framer in MVIP 4.096Mbit/s mode.
FIGURE 31. INTERFACING XRT84L38 TO THE LOCAL TERMINAL EQUIPMENT USING 4.096MBIT/S DATA BUS
XRT84L38
TxSerClk_0
Transmit
TxSer_0
Payload
TxInClk_0 (4.096MHz) Data Input
Interface
Chn 0
TxSync_0
Terminal
Equipment
TxSerClk_7
Transmit
TxSer_7
Payload
Data Input
Interface
Chn 7
TxInClk_7 (4.096MHz)
TxSync_7
The timing diagram of input signals to the framer when running at 4.096Mbit/s mode is shown in Figure 32
FIGURE 32. TIMING DIAGRAM OF THE INPUT SIGNALS TO THE FRAMER WHEN RUNNING AT 4.096MBIT/S MODE
TxSerClk (4MHz)
TxSerClk (2MHz)
TxSerClk (INV)
TxSer
F
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8
Don't Care
Don't care
Don't Care
TxSync(input)
TxTSb[0]/TxSig
Don't Care
Don't Care
A B C D
Don't Care
A B C D
Don't Care
A B C D
A B C D
Note: The following signals are not aligned with the signals shown above. The TxTSClk is derived from 1.544MHz transmit clock.
TxTSClk(INV)
Don't Care
1 2 3 4 5 6 7 8
Don't Care
1 2 3 4 5 6 7 8
TxTSb[1]/TxFrTD
4.1.3.3 T1 Transmit Input Interface - 8.192 MHz
This interface mode is the same as running at 2.048 MHz. The only difference is that the Transmit Input Clock
runs four times faster at 8.192MHz.
When the Transmit Multiplex Enable bit is set to zero and the Transmit Interface Mode Select [1:0] bits are set to
11, the Transmit Back-plane interface of framer is running at a clock rate of 8.192MHz.
The interface consists of the following pins:
213
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
• Data input (TxSer_n)
• Transmit Serial Clock Input signal (TxSerClk_n)
• Transmit Single-frame Synchronization Input signal (TxSync_n)
• Transmit Input Clock (TxInClk_n)
• Transmit Time-slot Indication clock (TxTSClk_n)
• Transmit Time Slot indicator bits (TxTSb[4:0]_n)
The Transmit Back-plane interface is still accepting data through TxSer_n at an E1 equivalent data rate of
2.048Mbit/s. However, the local Terminal Equipment supplies a free-running 8.192MHz clock to the Transmit Input
Clock pin of the framer. The local Terminal Equipment provides synchronized payload data at every other four ris-
ing edge of the Transmit Input Clock. The Transmit High-speed Back-plane Interface of the framer then latches in-
coming serial data at every other four falling edge of the clock. The local Terminal Equipment should pump in data
grouped in 256-bit frame 8000 times every second. Each frame consists of thirty-two octets as in E1. The local
Terminal Equipment maps a 193-bit T1 frame into this 256-bit format as described below:
1. The Framing (F-bit) is mapped into MSB of the first E1 Time-slot. The local Terminal Equipment will stuff
the rest seven bits of the first octet with "don't care" bits that would be ignored by the framer.
2. Payload data of T1 Time-slot 0, 1 and 2 are mapped into E1 Time-slot 1, 2 and 3.
3. The local Terminal Equipment will stuff E1 Time-slot 4 with eight "don't care" bits that would be ignored by
the framer.
4. Following the same rules of Step 2 and 3, the local Terminal Equipment maps every three time-slots of T1
payload data into four E1 time-slots.
The mapping of T1 frame into E1 framing format is shown in the table below.
TABLE 41: THE MAPPING OF T1 FRAME INTO E1 FRAMING FORMAT
T1
E1
T1
E1
T1
E1
T1
E1
F-Bit
TS0
TS0
TS1
TS1
TS2
TS2
TS3
Don't Care Bits
TS4
TS3
TS5
TS4
TS6
TS5
TS7
Don't Care Bits
TS8
TS6
TS7
TS8
Don't Care Bits
TS12
TS9
TS10
TS14
TS16
TS22
TS22
TS30
TS11
TS15
TS17
TS23
TS23
TS31
TS9
TS10
TS13
TS18
TS19
TS26
TS11
TS14
TS19
TS20
TS27
TS13
TS15
TS21
TS21
TS29
Don't Care Bits
TS16
TS12
TS17
TS18
TS25
Don't Care Bits
TS20
Don't Care Bits
TS24
Don't Care Bits
TS28
The Transmit Single-frame Synchronization input signal (TxSync_n) should pulse HIGH at the beginning (F-bit
position) of the 256-bit frame indicating start of the frame. By sampling the HIGH pulse on the Transmit Single-
frame Synchronization signal, the framer can position the beginning of a DS1 frame. It is responsibility of the local
Terminal Equipment to align the Transmit Single-frame Synchronization signal with serial data stream going into
the framer.
Inside the framer, all the "don't care" bits will be stripped away. The framing bits, signaling and payload data are
then processed by the framer and send to LIU interface. The local Terminal Equipment provides a free-running
1.544MHz clock to the Transmit Serial Input clock. The framer will use this clock to carry the processed payload
and signaling data to the transmit section of the device.
214
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
See Figure 33 below for how to interface the local Terminal Equipment with the Transmit Payload Data Input Inter-
face block of the framer in MVIP 8.192Mbit/s mode.
FIGURE 33. INTERFACING XRT84L38 TO THE LOCAL TERMINAL EQUIPMENT USING 8.192MBIT/S DATA BUS
XRT84L38
TxSerClk_0
Transmit
TxSer_0
Payload
TxInClk_0 (8.192MHz) Data Input
Interface
Chn 0
TxSync_0
Terminal
Equipment
TxSerClk_7
Transmit
TxSer_7
Payload
Data Input
Interface
Chn 7
TxInClk_7 (8.192MHz)
TxSync_7
The timing diagram of input signals to the framer when running at 8.192Mbit/s mode is shown in Figure 34.
FIGURE 34. TIMING DIAGRAM OF THE INPUT SIGNALS TO THE FRAMER WHEN RUNNING AT 8.192MBIT/S MODE
TxSerClk (8MHz)
TxSerClk (2MHz)
TxSerClk (INV)
TxSer
F
Don't Care
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
Don't care
Don't Care
1 2 3 4 5 6 7 8
TxSync(input)
TxTSb[0]/TxSig
Don't Care
Don't Care
A B C D
Don't Care
A B C D
Don't Care
A B C D
A B C D
Note: The following signals are not aligned with the signals shown above. The TxTSClk is derived from 1.544MHz transmit clock.
TxTSClk(INV)
Don't Care
1 2 3 4 5 6 7 8
Don't Care
1 2 3 4 5 6 7 8
TxTSb[1]/TxFrTD
4.1.3.4 T1 Transmit Input Interface - Multiplexed 12.352Mbit/s
When the Transmit Multiplex Enable bit is set to one and the Transmit Interface Mode Select [1:0] bits are set to
00, the Transmit Back-plane interface of framer is running at a clock rate of 12.352MHz.
The interface consists of the following pins:
• Data input (TxSer_n)
• Transmit Serial Clock Input signal (TxSerClk_n)
• Transmit Single-frame Synchronization Input signal (TxSync_n)
215
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
• Transmit Input Clock (TxInClk_n)
• Transmit Time-slot Indication clock (TxTSClk_n)
• Transmit Time Slot indicator bits (TxTSb[4:0]_n)
The Transmit Back-plane Interface is accepting data through TxSer_0 or TxSer_4 pins at 12.352Mbit/s. The local
Terminal Equipment multiplexes payload and signaling data of every four channels into one data stream. Payload
and signaling data of Channel 0-3 are multiplexed onto the Transmit Serial Data pin of Channel 0. Payload and
signaling data of Channel 4-7 are multiplexed onto the Transmit Serial Data pin of Channel 4.
Free-running clocks of 12.352MHz is supplied to the Transmit Input Clock pin of Channel 0 and Channel 4 of the
framer. The local Terminal Equipment provides multiplexed payload data at rising edge of this Transmit Input
Clock. The Transmit High-speed Back-plane Interface of the framer then latches incoming serial data at falling
edge of the clock.
The local Terminal Equipment maps four 1.544Mbit/s DS1 data streams into this 12.352Mbit/s data stream as de-
scribed below:
1. The F-bit of four channels are repeated and grouped together to form the first octet of the multiplexed data
stream. The F-bit of Channel 0 is sent first, followed by F-bit of Channel 1 and 2. The F-bit of Channel 3 is
sent last. The table below shows bit-pattern of the first octet.
FIRST OCTET OF 12.352MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
F0
F0
F1
F1
F2
F2
F3
F3
FX: F-bit of Channel X
2. Payload data of four channels are repeated and grouped together in a bit-interleaved way. The first payload
bit of Timeslot 0 of Channel 0 is sent first, followed by the first payload bit of Timeslot 0 of Channel 1 and 2.
The first payload bit of Timeslot 0 of Channel 3 is sent last. After the first bits of Timeslot 0 of all four chan-
nels are sent, it comes the second bit of Timeslot 0 of Channel 0 and so on. The table below demonstrates
how payload bits of four channels are mapped into the 12.352Mbit/s data stream.
SECOND OCTET OF 12.352MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
10
10
11
11
12
12
13
13
THIRD OCTET OF 12.352MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
20
20
21
21
22
22
23
23
XY: The Xth payload bit of Channel Y
3. The local Terminal Equipment also multiplexed signaling bits with payload bits and sent them together
through the 12.352Mbit/s data stream. When the Terminal Equipment is sending the fifth payload bit of a
particular channel, instead of sending it twice, it inserts the signaling bit A of that particular channel. Simi-
216
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
larly, the sixth payload bit of a particular channels is followed by the signaling bit B of that channel; the sev-
enth payload bit is followed by the signaling bit C; the eighth payload bit is followed by the signaling bit D.
The following table illustrates how payload bits and signaling bits are multiplexed together into the 12.352Mbit/
s data stream.
SIXTH OCTET OF 12.352MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
50
A0
51
A1
52
A2
53
A3
SEVENTH OCTET OF 12.352MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
60
B0
61
B1
62
B2
63
B3
EIGHTH OCTET OF 12.352MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
70
C0
71
C1
72
C2
73
C3
NINETH OCTET OF 12.352MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
80
D0
81
D1
82
D2
83
D3
XY: The Xth payload bit of Channel Y
AY: The signaling bit A of Channel Y
4. Following the same rules of Step 2 and 3, the local Terminal Equipment maps the payload data and signal-
ing data of four channels into a 12.352Mbit/s data stream.
The Transmit Single-frame Synchronization signal of Channel 0 pulses HIGH for one clock cycle at the first bit po-
sition (F-bit of channel 0) of the data stream with data from Channel 0-3 multiplexed together. The Transmit Sin-
gle-frame Synchronization signal of Channel 4 pulses HIGH for one clock cycle at the first bit position (F-bit of
Channel 4) of the data stream with data from Channel 4-7 multiplexed together. By sampling the HIGH pulse on
the Transmit Single-frame Synchronization signal, the framer can position the beginning of the multiplexed DS1
frame. It is responsibility of the Terminal Equipment to align the multiplexed transmit serial data with the Transmit
Single-frame Synchronization pulse.
Inside the framer, all the "don't care" bits will be stripped away. The framing bits, signaling and payload data are
de-multiplexed inside the XRT84L38 and send to each individual channel. These data will be processed by each
individual framer and send to LIU interface. The local Terminal Equipment provides a free-running 1.544MHz
clock to the Transmit Serial Input clock of each channel. The framer will use this clock to carry the processed pay-
load and signaling data to the transmit section of the device.
217
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
See Figure 35 below for how to interface the local Terminal Equipment with the Transmit Payload Data Input Inter-
face block of the framer in 12.352Mbit/s mode.
FIGURE 35. INTERFACING XRT84L38 TO THE LOCAL TERMINAL EQUIPMENT USING BIT-MULTIPLEXED 12.352MBIT/
S DATA BUS
XRT84L38
TxSer_0
Transmit
Payload
Data Input
Interface
Chn 0
TxInClk_0 (12.352MHz)
TxSync_0
TxSerClk_0 (1.544MHz)
TxSerClk_1 (1.544MHz)
TxSerClk_2 (1.544MHz)
TxSerClk_3 (1.544MHz)
Chn 1
Chn 2
Chn 3
Terminal
Equipment
TxSer_4
Transmit
Payload
Data Input
Interface
Chn 4
TxInClk_4 (12.352MHz)
TxSync_4
TxSerClk_4 (1.544MHz)
TxSerClk_5 (1.544MHz)
TxSerClk_6 (1.544MHz)
TxSerClk_7 (1.544MHz)
Chn 5
Chn 6
Chn 7
The Input signal timing is shown in Figure 36 below when the framer is running at 12.352Mbit/s mode.
FIGURE 36. TIMING DIAGRAM OF THE INPUT SIGNALS TO THE FRAMER WHEN RUNNING AT 12.352MBIT/S MODE
TxSerClk (12.352MHz)
TxSerClk (INV)
TxSer
F0 F0 F1 F1 F2 F2 F3 F3 10 X 11 X 12 X 13 X 20 X 21
X
30
X
40
X
50 A0 51 A1 52 A2 53 A3 60 B0 61 B1 62 B2 63 B3
TxSync(input)
4.1.3.5 T1 Transmit Input Interface - Bit-Multiplexed 16.384Mbit/s
When the Transmit Multiplex Enable bit is set to one and the Transmit Interface Mode Select [1:0] bits are set to
01, the Transmit Back-plane interface of framer is running at a clock rate of 16.384MHz.
The interface consists of the following pins:
• Data input (TxSer_n)
• Transmit Serial Clock Input signal (TxSerClk_n)
• Transmit Single-frame Synchronization Input signal (TxSync_n)
218
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
• Transmit Input Clock (TxInClk_n)
• Transmit Time-slot Indication clock (TxTSClk_n)
• Transmit Time Slot indicator bits (TxTSb[4:0]_n)
The Transmit Back-plane Interface is accepting data through TxSer_0 or TxSer_4 pins at 16.384Mbit/s. The local
Terminal Equipment multiplexes payload and signaling data of every four channels into one data stream. Payload
and signaling data of Channel 0-3 are multiplexed onto the Transmit Serial Data pin of Channel 0. Payload and
signaling data of Channel 4-7 are multiplexed onto the Transmit Serial Data pin of Channel 4.
Free-running clocks of 16.384MHz is supplied to the Transmit Input Clock pin of Channel 0 and Channel 4 of the
framer. The local Terminal Equipment provides multiplexed payload data at rising edge of this Transmit Input
Clock. The Transmit High-speed Back-plane Interface of the framer then latches incoming serial data at falling
edge of the clock.
The local Terminal Equipment maps four 1.544Mbit/s DS1 data streams into this 16.384Mbit/s data stream as de-
scribed below:
1. The F-bit of four channels are repeated and grouped together to form the first octet of the multiplexed data
stream. The F-bit of Channel 0 is sent first, followed by F-bit of Channel 1 and 2. The F-bit of Channel 3 is
sent last. The table below shows bit-pattern of the first octet.
FIRST OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
F0
F0
F1
F1
F2
F2
F3
F3
FX: F-bit of Channel X
2. After the first octet of data is sent, the local Terminal Equipment should insert seven octets (fifty-six bits) of
"don't care" data into the outgoing data stream.
3. Payload data of four channels are repeated and grouped together in a bit-interleaved way. The first payload
bit of Timeslot 0 of Channel 0 is sent first, followed by the first payload bit of Timeslot 0 of Channel 1 and 2.
The first payload bit of Timeslot 0 of Channel 3 is sent last. After the first bits of Timeslot 0 of all four chan-
nels are sent, it comes the second bit of Timeslot 0 of Channel 0 and so on. The table below demonstrates
how payload bits of four channels are mapped into the 16.384Mbit/s data stream.
NINETH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
10
10
11
11
12
12
13
13
TENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
20
20
21
21
22
22
23
23
XY: The Xth payload bit of Channel Y
219
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
4. The local Terminal Equipment also multiplexed signaling bits with payload bits and sent them together
through the 16.384Mbit/s data stream. When the Terminal Equipment is sending the fifth payload bit of a
particular channel, instead of sending it twice, it inserts the signaling bit A of that particular channel. Simi-
larly, the sixth payload bit of a particular channels is followed by the signaling bit B of that channel; the sev-
enth payload bit is followed by the signaling bit C; the eighth payload bit is followed by the signaling bit D.
The following table illustrates how payload bits and signaling bits are multiplexed together into the 16.384Mbit/
s data stream.
THIRTEENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
50
A0
51
A1
52
A2
53
A3
FOURTEENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
60
B0
61
B1
62
B2
63
B3
FIFTEENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
70
C0
71
C1
72
C2
73
C3
SIXTEENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
80
D0
81
D1
82
D2
83
D3
XY: The Xth payload bit of Channel Y
AY: The signaling bit A of Channel Y
5. After payload bits of Timeslot 0, 1 and 2 of all four channels are sent, the Terminal Equipment should stuff
another eight octets (sixty-four bits) of "don't care" data into the outgoing data stream.
6. Following the same rules of Step 2 to 5, the local Terminal Equipment stuffs eight octets of "don't care"
data after sending twenty-four octets of multiplexed payload and signaling data. A 16.384Mbit/s data
stream is thus created.
The Transmit Single-frame Synchronization signal of Channel 0 pulses HIGH for one clock cycle at the first bit po-
sition (F-bit of channel 0) of the data stream with data from Channel 0-3 multiplexed together. The Transmit Sin-
gle-frame Synchronization signal of Channel 4 pulses HIGH for one clock cycle at the first bit position (F-bit of
Channel 4) of the data stream with data from Channel 4-7 multiplexed together. By sampling the HIGH pulse on
the Transmit Single-frame Synchronization signal, the framer can position the beginning of the multiplexed DS1
frame. It is responsibility of the Terminal Equipment to align the multiplexed transmit serial data with the Transmit
Single-frame Synchronization pulse.
220
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
Inside the framer, all the "don't care" bits will be stripped away. The framing bits, signaling and payload data are
de-multiplexed inside the XRT84L38 and send to each individual channel. These data will be processed by each
individual framer and send to LIU interface. The local Terminal Equipment provides a free-running 1.544MHz
clock to the Transmit Serial Input clock of each channel. The framer will use this clock to carry the processed pay-
load and signaling data to the transmit section of the device.
See Figure 37 below for how to interface the local Terminal Equipment with the Transmit Payload Data Input Inter-
face block of the framer in Bit-multiplexed 16.384Mbit/s mode.
FIGURE 37. INTERFACING XRT84L38 TO THE LOCAL TERMINAL EQUIPMENT USING 16.384MBIT/S DATA BUS
XRT84L38
TxSer_0
Transmit
Payload
Data Input
Interface
Chn 0
TxInClk_0 (16.384MHz)
TxSync_0
TxSerClk_0 (1.544MHz)
TxSerClk_1 (1.544MHz)
TxSerClk_2 (1.544MHz)
TxSerClk_3 (1.544MHz)
Chn 1
Chn 2
Chn 3
Terminal
Equipment
TxSer_4
Transmit
Payload
Data Input
Interface
Chn 4
TxInClk_4 (16.384MHz)
TxSync_4
TxSerClk_4 (1.544MHz)
TxSerClk_5 (1.544MHz)
TxSerClk_6 (1.544MHz)
TxSerClk_7 (1.544MHz)
Chn 5
Chn 6
Chn 7
The Input signal timing is shown in Figure 38 below when the framer is running at Bit-Multiplexed 16.384Mbit/s
mode.
FIGURE 38. TIMING DIAGRAM OF THE INPUT SIGNALS TO THE FRAMER WHEN RUNNING AT BIT-MULTIPLEXED
16.384MBIT/S MODE
TxSerClk (16.384MHz)
TxSerClk (INV)
56 cycles
TxSer
F0 F0 F1 F1 F2 F2 F3 F3
10 X 11 X 12 X 13 X 20 X 21
X
30
X
40
X
50 A0 51 A1 52 A2 53 A3
TxSync(input)
4.1.3.6 T1 Transmit Input Interface - HMVIP 16.384Mbit/s
221
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
When the Transmit Multiplex Enable bit is set to one and the Transmit Interface Mode Select [1:0] bits are set to
10, the Transmit Back-plane interface of framer is running at a clock rate of 16.384MHz.
The interface consists of the following pins:
• Data input (TxSer_n)
• Transmit Serial Clock Input signal (TxSerClk_n)
• Transmit Single-frame Synchronization Input signal (TxSync_n)
• Transmit Input Clock (TxInClk_n)
• Transmit Time-slot Indication clock (TxTSClk_n)
• Transmit Time Slot indicator bits (TxTSb[4:0]_n)
The Transmit Back-plane Interface is accepting data through TxSer_0 or TxSer_4 pins at 16.384Mbit/s. The local
Terminal Equipment multiplexes payload and signaling data of every four channels into one data stream. Payload
and signaling data of Channel 0-3 are multiplexed onto the Transmit Serial Data pin of Channel 0. Payload and
signaling data of Channel 4-7 are multiplexed onto the Transmit Serial Data pin of Channel 4.
Free-running clocks of 16.384MHz is supplied to the Transmit Input Clock pin of Channel 0 and Channel 4 of the
framer. The local Terminal Equipment provides multiplexed payload data at rising edge of this Transmit Input
Clock. The Transmit High-speed Back-plane Interface of the framer then latches incoming serial data at falling
edge of the clock.
The local Terminal Equipment maps four 1.544Mbit/s DS1 data streams into this 16.384Mbit/s data stream as de-
scribed below:
1. The F-bit of four channels are repeated and grouped together to form the first octet of the multiplexed data
stream. The F-bit of Channel 0 is sent first, followed by F-bit of Channel 1 and 2. The F-bit of Channel 3 is
sent last. The table below shows bit-pattern of the first octet.
FIRST OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
F0
F0
F1
F1
F2
F2
F3
F3
FX: F-bit of Channel X
2. After the first octet of data is sent, the local Terminal Equipment should insert seven octets (fifty-six bits) of
"don't care" data into the outgoing data stream.
3. Payload data of four channels are repeated and grouped together in a byte-interleaved way. The first pay-
load bit of Timeslot 0 of Channel 0 is sent first, followed by the second payload bit of Timeslot 0 of Channel
0 and so on. After all the bits of Timeslot 0 of Channel 0 is sent repeatedly, the Terminal Equipment will
start sending the payload bits of Timeslot 0 of Channel 1 and 2. The payload bits of Timeslot 0 of Channel
3 are sent the last. After the payload bits of Timeslot 0 of all four channels are sent, it comes the payload
bits of Timeslot 1 of Channel 0 and so on. The table below demonstrates how payload bits of four channels
are mapped into the 16.384Mbit/s data stream.
NINTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
10
10
20
20
30
30
40
40
222
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
ELEVENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
11
11
21
21
31
31
41
41
THIRTEENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
12
12
22
22
32
32
42
42
FIFTEENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
13
13
23
23
33
33
43
43
XY: The Xth payload bit of Channel Y
4. The local Terminal Equipment also multiplexed signaling bits with payload bits and sent them together
through the 16.384Mbit/s data stream. When the Terminal Equipment is sending the fifth payload bit of a
particular channel, instead of sending it twice, it inserts the signaling bit A of that particular channel. Simi-
larly, the sixth payload bit of a particular channels is followed by the signaling bit B of that channel; the sev-
enth payload bit is followed by the signaling bit C; the eighth payload bit is followed by the signaling bit D.
The following table illustrates how payload bits and signaling bits are multiplexed together into the 16.384Mbit/s
data stream.
TENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
50
A0
60
B0
70
C0
80
D0
TWELFTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
51
A1
61
B1
71
C1
81
D1
FOURTEENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
52
A2
62
B2
72
C2
82
D2
223
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
SIXTEENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
53
A3
63
B3
73
C3
83
D3
XY: The Xth payload bit of Channel Y
AY: The signaling bit A of Channel Y
5. After payload bits of Timeslot 0, 1 and 2 of all four channels are sent, the Terminal Equipment should stuff
another eight octets (sixty-four bits) of "don't care" data into the outgoing data stream.
6. Following the same rules of Step 2 to 5, the local Terminal Equipment stuffs eight octets of "don't care"
data after sending twenty-four octets of multiplexed payload and signaling data. A 16.384Mbit/s data
stream is thus created.
The Transmit Single-frame Synchronization signal should pulse HIGH for four clock cycles (the last two bit posi-
tions of the previous multiplexed frame and the first two bits of the next multiplexed frame) indicating frame bound-
ary of the multiplexed data stream. The Transmit Single-frame Synchronization signal of Channel 0 pulses HIGH
to identify the start of multiplexed data stream of Channel 0-3. The Transmit Single-frame Synchronization signal
of Channel 4 pulses HIGH to identify the start of multiplexed data stream of Channel 4-7. By sampling the HIGH
pulse on the Transmit Single-frame Synchronization signal, the framer can position the beginning of the multi-
plexed DS1 frame. It is responsibility of the Terminal Equipment to align the multiplexed transmit serial data with
the Transmit Single-frame Synchronization pulse.
Inside the framer, all the "don't care" bits will be stripped away. The framing bits, signaling and payload data are
de-multiplexed inside the XRT84L38 and send to each individual channel. These data will be processed by each
individual framer and send to LIU interface. The local Terminal Equipment provides a free-running 1.544MHz
clock to the Transmit Serial Input clock of each channel. The framer will use this clock to carry the processed pay-
load and signaling data to the transmit section of the device.
224
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
See Figure 39 below for how to interface the local Terminal Equipment with the Transmit Payload Data Input Inter-
face block of the framer in HMVIP 16.384Mbit/s mode.
FIGURE 39. INTERFACING XRT84L38 TO THE LOCAL TERMINAL EQUIPMENT USING HMVIP 16.384MBIT/S DATA
BUS
XRT84L38
TxSer_0
Transmit
Payload
Data Input
Interface
Chn 0
TxInClk_0 (16.384MHz)
TxSync_0
TxSerClk_0 (1.544MHz)
TxSerClk_1 (1.544MHz)
TxSerClk_2 (1.544MHz)
TxSerClk_3 (1.544MHz)
Chn 1
Chn 2
Chn 3
Terminal
Equipment
TxSer_4
Transmit
Payload
Data Input
Interface
Chn 4
TxInClk_4 (16.384MHz)
TxSync_4
TxSerClk_4 (1.544MHz)
TxSerClk_5 (1.544MHz)
TxSerClk_6 (1.544MHz)
TxSerClk_7 (1.544MHz)
Chn 5
Chn 6
Chn 7
The Input signal timing is shown in Figure 40 below when the framer is running at HMVIP 16.384Mbit/s mode.
FIGURE 40. TIMING DIAGRAM OF THE INPUT SIGNALS TO THE FRAMER WHEN RUNNING AT HMVIP 16.384MBIT/S
MODE
TxSerClk (16.384MHz)
TxSerClk (INV)
56 cycles
56 cycles
TxSer
TxSig
73 73 83 83 F0 F0 F1 F1 F2 F2 F3 F3
Start of Frame
10 10 20 20 30 30 40 40 50 A0 60 B0
Xy : X is the bit number and y is the channel number
0 0 0 0 0 0 A0A0B0B0C0C0 0 0 A2A2
12 12
52 52
53 53 63 63 73 73 83 83
A3A3B3B3C3C3D3D3
C3C3D3D3 1 1 1 1 1 1 1 1
TxSync(input)
HMVIP, negative sync
TxSync(input)
HMVIP, positive sync
4.1.3.7 T1 Transmit Input Interface - H.100 16.384Mbit/s
When the Transmit Multiplex Enable bit is set to one and the Transmit Interface Mode Select [1:0] bits are set to
11, the Transmit Back-plane interface of framer is running at H.100 16.384Mbit/s mode.
225
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
(The HMVIP mode and the H.100 mode are essential the same except for the HIGH pulse position of the Trans-
mit Single-frame Synchronization Signal)
The interface consists of the following pins:
• Data input (TxSer_n)
• Transmit Serial Clock Input signal (TxSerClk_n)
• Transmit Single-frame Synchronization Input signal (TxSync_n)
• Transmit Input Clock (TxInClk_n)
• Transmit Time-slot Indication clock (TxTSClk_n)
• Transmit Time Slot indicator bits (TxTSb[4:0]_n)
The Transmit Back-plane Interface is accepting data through TxSer_0 or TxSer_4 pins at 16.384Mbit/s. The local
Terminal Equipment multiplexes payload and signaling data of every four channels into one data stream. Payload
and signaling data of Channel 0-3 are multiplexed onto the Transmit Serial Data pin of Channel 0. Payload and
signaling data of Channel 4-7 are multiplexed onto the Transmit Serial Data pin of Channel 4.
Free-running clocks of 16.384MHz is supplied to the Transmit Input Clock pin of Channel 0 and Channel 4 of the
framer. The local Terminal Equipment provides multiplexed payload data at rising edge of this Transmit Input
Clock. The Transmit High-speed Back-plane Interface of the framer then latches incoming serial data at falling
edge of the clock.
The local Terminal Equipment maps four 1.544Mbit/s DS1 data streams into this 16.384Mbit/s data stream as de-
scribed below:
1. The F-bit of four channels are repeated and grouped together to form the first octet of the multiplexed data
stream. The F-bit of Channel 0 is sent first, followed by F-bit of Channel 1 and 2. The F-bit of Channel 3 is
sent last. The table below shows bit-pattern of the first octet.
FIRST OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
F0
F0
F1
F1
F2
F2
F3
F3
FX: F-bit of Channel X
2. After the first octet of data is sent, the local Terminal Equipment should insert seven octets (fifty-six bits) of
"don't care" data into the outgoing data stream.
3. 3.Payload data of four channels are repeated and grouped together in a byte-interleaved way. The first pay-
load bit of Timeslot 0 of Channel 0 is sent first, followed by the second payload bit of Timeslot 0 of Channel
0 and so on. After all the bits of Timeslot 0 of Channel 0 is sent repeatedly, the Terminal Equipment will
start sending the payload bits of Timeslot 0 of Channel 1 and 2. The payload bits of Timeslot 0 of Channel
3 are sent the last. After the payload bits of Timeslot 0 of all four channels are sent, it comes the payload
bits of Timeslot 1 of Channel 0 and so on. The table below demonstrates how payload bits of four channels
are mapped into the 16.384Mbit/s data stream.
NINTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
10
10
20
20
30
30
40
40
226
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
ELEVENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
11
11
21
21
31
31
41
41
THIRTEENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
12
12
22
22
32
32
42
42
FIFTEENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
13
13
23
23
33
33
43
43
XY: The Xth payload bit of Channel Y
4. The local Terminal Equipment also multiplexed signaling bits with payload bits and sent them together
through the 16.384Mbit/s data stream. When the Terminal Equipment is sending the fifth payload bit of a
particular channel, instead of sending it twice, it inserts the signaling bit A of that particular channel. Simi-
larly, the sixth payload bit of a particular channels is followed by the signaling bit B of that channel; the sev-
enth payload bit is followed by the signaling bit C; the eighth payload bit is followed by the signaling bit D.
The following table illustrates how payload bits and signaling bits are multiplexed together into the 16.384Mbit/s
data stream.
TENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
50
A0
60
B0
70
C0
80
D0
TWELFTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
51
A1
61
B1
71
C1
81
D1
FOURTEENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
52
A2
62
B2
72
C2
82
D2
227
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
SIXTEENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
53
A3
63
B3
73
C3
83
D3
XY: The Xth payload bit of Channel Y
AY: The signaling bit A of Channel Y
5. After payload bits of Timeslot 0, 1 and 2 of all four channels are sent, the Terminal Equipment should stuff
another eight octets (sixty-four bits) of "don't care" data into the outgoing data stream.
6. Following the same rules of Step 2 to 5, the local Terminal Equipment stuffs eight octets of "don't care"
data after sending twenty-four octets of multiplexed payload and signaling data. A 16.384Mbit/s data
stream is thus created.
The Transmit Single-frame Synchronization signal should pulse HIGH for two clock cycles (the last bit position of
the previous multiplexed frame and the first bit position of the next multiplexed frame) indicating frame boundary
of the multiplexed data stream. The Transmit Single-frame Synchronization signal of Channel 0 pulses HIGH to
identify the start of multiplexed data stream of Channel 0-3. The Transmit Single-frame Synchronization signal of
Channel 4 pulses HIGH to identify the start of multiplexed data stream of Channel 4-7. By sampling the HIGH
pulse on the Transmit Single-frame Synchronization signal, the framer can position the beginning of the multi-
plexed DS1 frame. It is responsibility of the Terminal Equipment to align the multiplexed transmit serial data with
the Transmit Single-frame Synchronization pulse.
Inside the framer, all the "don't care" bits will be stripped away. The framing bits, signaling and payload data are
de-multiplexed inside the XRT84L38 and send to each individual channel. These data will be processed by each
individual framer and send to LIU interface. The local Terminal Equipment provides a free-running 1.544MHz
clock to the Transmit Serial Input clock of each channel. The framer will use this clock to carry the processed pay-
load and signaling data to the transmit section of the device.
228
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
See Figure 41 below for how to interface the local Terminal Equipment with the Transmit Payload Data Input Inter-
face block of the framer in H.100 16.384Mbit/s mode.
FIGURE 41. INTERFACING XRT84L38 TO THE LOCAL TERMINAL EQUIPMENT USING H.100 16.384MBIT/S DATA BUS
XRT84L38
TxSer_0
Transmit
Payload
Data Input
Interface
Chn 0
TxInClk_0 (16.384MHz)
TxSync_0
TxSerClk_0 (1.544MHz)
TxSerClk_1 (1.544MHz)
TxSerClk_2 (1.544MHz)
TxSerClk_3 (1.544MHz)
Chn 1
Chn 2
Chn 3
Terminal
Equipment
TxSer_4
Transmit
Payload
Data Input
Interface
Chn 4
TxInClk_4 (16.384MHz)
TxSync_4
TxSerClk_4 (1.544MHz)
TxSerClk_5 (1.544MHz)
TxSerClk_6 (1.544MHz)
TxSerClk_7 (1.544MHz)
Chn 5
Chn 6
Chn 7
The Input signal timing is shown in Figure 42 below when the framer is running at H.100 16.384Mbit/s mode.
FIGURE 42. TIMING DIAGRAM OF THE INPUT SIGNALS TO THE FRAMER WHEN RUNNING AT H.100 16.384MBIT/S
MODE
TxSerClk (16.384MHz)
TxSerClk (INV)
56 cycles
56 cycles
TxSer
TxSig
73 73 83 83 F0 F0 F1 F1 F2 F2 F3 F3
Start of Frame
10 10 20 20 30 30 40 40 50 A0 60 B0
12 12
52 52
53 53 63 63 73 73 83 83
A3A3B3B3C3C3D3D3
Xy : X is the bit number and y is the channel number
C3C3D3D3 1 1 1 1 1 1 1 1
0 0 0 0 0 0 A0A0B0B0C0C0
0 0
A2A2
TxSync(input)
H.100, negative sync
TxSync(input)
H.100, positive sync
Delayer H.100
TxSync(input)
H.100, negative sync
TxSync(input)
H.100, positive sync
229
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
5.0 THE DS1 RECEIVE SECTION
5.1 THE DS1 RECEIVE PAYLOAD DATA OUTPUT INTERFACE BLOCK
5.1.1 Description of the Receive Payload Data Output Interface Block
Each of the eight framers within the XRT84L38 includes a Receive Payload Data Output Interface block. The
function of the block is to provide an interface to the Terminal Equipment (for example, a Central Office or
switching equipment) that has data to receive from a "Far End" terminal over a DS1 or E1 transport medium.
The Payload Data Output Interface module (also known as the Back-plane Interface module) supports payload
data to be taken from or presented to the system. In DS1 mode, supported data rates are 1.544Mbit/s, MVIP
2.048Mbit/s, 4.096Mbit/s, 8.192Mbit/s, multiplexed 12.352Mbit/s, multiplexed 16.384Mbit/s, HMVIP
16.384Mbit/s or H.100 16.384Mbit/s. In E1 mode, supported data rates are XRT84V24 compatible 2.048Mbit/s,
MVIP 2.048Mbit/s, 4.096Mbit/s, 8.192Mbit/s, multiplexed 16.384Mbit/s, HMVIP 16.384Mbit/s or H.100
16.384Mbit/s.
The Receive Payload Data Output Interface block supplies or accepts the following signals to the Terminal
Equipment circuitry:
• Receive Serial Data Input (RxSer_n)
• Receive Serial Clock (RxSerClk_n)
• Receive Single-frame Synchronization Signal (RxSync_n)
• Receive Multi-frame Synchronization Signal (RxMSync_n)
• Receive Time-slot Indicator Clock (RxTSClk_n)
• Receive Time-slot Indication Bits (RxTSb[4:0]_n)
The Receive Serial Data is an output pin carrying payload, signaling and sometimes Data Link data supplied
by XRT84L38 to the local Terminal Equipment.
The Receive Serial Clock is an input or output signal used by the Receive Payload Data Input Interface block to
send out serial data to the local Terminal Equipment. The Receive Clock Inversion bit of the Receive Interface
Control Register (TICR) determines at which edge of the Receive Serial Clock would data transition on the Re-
ceive Serial Data pin occur.
The table below shows configurations of the Receive Clock Inversion bit of the Receive Interface Control Reg-
ister (RICR).
RECEIVE INTERFACE CONTROL REGISTER (RICR) (INDIRECT ADDRESS = 0xn0H, 0x22H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3
Receive Clock
Inversion
R/W
0 - Serial data transition happens on rising edge of the Receive Serial Clock.
1 - Serial data transition happens on falling edge of the Receive Serial Clock.
Throughout the discussion of this datasheet, we assume that serial data transition happens on the rising edge
of the Receive Serial Clock unless stated otherwise.
The Receive Single-frame Synchronization signal is either input or output. When configured as input, it indi-
cates beginning of a DS1 frame. When configured as output, it indicates the end of a DS1 frame.
The Receive Multi-frame Synchronization signal is an output pin from XRT84L38 indicating the end of a DS1
multi-frame.
By connecting these signals with the local Terminal Equipment, the Receive Payload Data Output Interface
routes received payload data from the Receive Framer Module to the local Terminal Equipment.
5.1.2 The Receive Payload Data Output Interface Block Operating at 1.544Mbit/s mode
The incoming Receive Payload Data is taken into the framer from the LIU interface using the Recovered Re-
ceive Line Clock. The payload data is then routed through the Receive Farmer Module and presented to the
Receive Payload Data Output Interface through the Receive Serial Data output pin (RxSer_n). This data is then
clocked out using the Receive Serial Clock (RxSerClk_n).
230
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
There is a two-frame (512 bits) elastic buffer between the Receive Framer Module and the Receive Payload
Data Output Interface. This buffer can be enabled or disabled via programming the Slip Buffer Enable [1:0] bits
in Slip Buffer Control Register (SBCR).
The following table shows configurations of the Slip Buffer Enable [1:0] bits in Slip Buffer Control Register.
SLIP BUFFER CONTROL REGISTER (SBCR) (INDIRECT ADDRESS = 0xn0H, 0x16H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1-0
Slip Buffer
Enable
R/W
00 - Slip Buffer is bypassed. The Receive Payload Data is passing from the
Receive Framer Module to the Receive Payload Data Output Interface directly
without routing through the Slip Buffer. The Receive Serial Clock signal
(RxSerClk_n) is an output.
01 - The Elastic Store (Slip Buffer) is enabled. The Receive Payload Data is
passing from the Receive Framer Module through the Slip Buffer to the Receive
Payload Data Output Interface. The Receive Serial Clock signal (RxSerClk_n) is
an input.
10 - The Slip Buffer acts as a FIFO. The FIFO Latency Register (FLR) deter-
mines the data latency. The Receive Payload Data is passing from the Receive
Framer Module through the FIFO to the Receive Payload Data Output Interface.
The Receive Serial Clock signal (RxSerClk_n) is an input.
11 - Slip Buffer is bypassed. The Receive Payload Data is passing from the
Receive Framer Module to the Receive Payload Data Output Interface directly
without routing through the Slip Buffer. The Receive Serial Clock signal
(RxSerClk_n) is an output.
If the Slip Buffer is not in bypass mode, then the user has the option of either providing the Receive Single-
Frame Synchronization pulse or getting the Receive Single-Frame Synchronization pulse on frame boundary at
the RxSync_n pin. The Slip Buffer Receive Synchronization Direction bit of the Slip Buffer Control Register
(SBCR) determines whether the Receive Single-Frame Synchronization signal is input or output.
The table below demonstrates settings of the Slip Buffer Receive Synchronization Direction bit of the Slip Buff-
er Control Register.
SLIP BUFFER CONTROL REGISTER (SBCR) (INDIRECT ADDRESS = 0xn0H, 0x16H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
2
Slip Buffer
Receive
R/W
0 - The Receive Single-Frame Synchronization signal (RxSync_n) is an output
if the Slip Buffer is not in bypass mode.
Synchronization
Direction
1 - The Receive Single-Frame Synchronization signal (RxSync_n) is an input if
the Slip Buffer is not in bypass mode.
If the Slip Buffer is in bypass mode, the Receive Payload Data is routed to the Receive Payload Data Output In-
terface from the Receive Framer Module directly. The Recovered Line Clock is used to carry the Receive Pay-
load Data all the way from the LIU interface, to the Receive Framer Module and eventually output through the
Receive Serial Data output pin. The Receive Serial Clock signal is therefore an output using the Recovered
Receive Line Clock as timing source. The Receive Single-Frame Synchronization signal is also output in Slip
Buffer bypass mode.
If the Slip Buffer is enabled, the Receive Payload Data is latched into the Elastic Store using the Recovered
Receive Line Clock. The local Terminal Equipment supplies a free-running 1.544MHz clock to the Receive Se-
rial Clock pin to latch the Receive Payload Data out from the Elastic Store. Since the Recovered Receive Line
Clock and the Receive Serial Clock are coming from different timing sources, the Slip Buffer will gradually fill or
empty. If the elastic buffer either fills or empties, a controlled slip will occur. If the buffer empties and a read oc-
curs, then a full frame of data will be repeated and a status bit will be updated. If the buffer fills and a write
comes, then a full frame of data will be deleted and another status bit will be set. A detailed description of the
231
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
Elastic Buffer can be found in later sections. In this mode, the Receive Single-Frame Synchronization signal
can be either input or output depending on the settings of the Slip Buffer Receive Synchronization Direction bit
of the Slip Buffer Control Register.
If the Slip Buffer is put into a FIFO mode, it is acting like a standard First-In-First-Out storage. A fixed READ
and WRITE latency is maintained in a programmable fashion controlled by the FIFO Latency Register
(FIFOLR). The local Terminal Equipment supplies a 1.544MHz clock to the Receive Serial Clock pin to latch
the Receive Payload Data out from the FIFO. However, it is the responsibility of the user to phase lock the input
Receive Serial Clock to the Recovered Receive Line Clock to avoid either over-run or under-run of the FIFO. In
this mode, the Receive Single-Frame Synchronization signal can be either input or output depending on the
settings of the Slip Buffer Receive Synchronization Direction bit of the Slip Buffer Control Register.
The following table summaries the input or output nature of the Receive Serial Clock and Receive Single-
Frame Synchronization signals for different Slip Buffer settings.
TABLE 42: THE RECEIVE SERIAL CLOCK AND RECEIVE SINGLE-FRAME SYNCHRONIZATION SIGNALS FOR DIFFERENT
SLIP BUFFER SETTINGS
RXSYNC_N
RECEIVE TIMING SOURCE
RXSERCLK_N
SLIP BUFFER SYNCHRONIZATION SLIP BUFFER SYNCHRONIZATION
DIRECTION BIT = 0
DIRECTION BIT = 1
Slip Buffer Bypassed
Slip Buffer Enabled
Output
Input
Output
Output
Output
Input
Slip Buffer Acts as FIFO
Input
Output
Input
The Receive Time-slot Indication Bits (RxTSb[4:0]_n) are multiplexed I/O pins. The functionality of these pins is
governed by the value of Receive Fractional T1 Output Enable bit of the Receive Interface Control Register
(RICR). The following table illustrates the configurations of the Receive Fractional DS1 Input Enable bit.
RECEIVE INTERFACE CONTROL REGISTER (RICR) (INDIRECT ADDRESS = 0xn0H, 0x22H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
4
Receive
Fractional DS1
Output Enable
R/W
0 - The Receive Time-slot Indication bits (RxTSb[4:0] are outputting five-bit
binary values of Time-slot number (0-23) being accepted and processed by the
Receive Payload Data Output Interface block of the framer.
The Receive Time-slot Indicator Clock signal (RxTSClk_n) is a 192KHz clock
that pulses HIGH for one DS1 bit period whenever the Receive Payload Data
Output Interface block is accepting the LSB of each of the twenty-four time slots.
1 - The RxTSb[0]_n bit becomes the Receive Fractional T1 Output signal
(RxFrTD_n) which carries Fractional DS1 payload data from the framer.
The RxTSb[1]_n bit becomes the Receive Signaling Data Output signal
(RxSig_n) which is used to carry robbed-bit signaling data extracted from the
inbound DS1 frame.
The RxTSb[2]_n bit serially outputs all five-bit binary values of the Time Slot
number (0-23) being accepted and processed by the Receive Payload Data Out-
put Interface block of the framer.
The RxTSClk_n will output gaped fractional DS1 clock that can be used by Ter-
minal Equipment to latch in Fractional DS1 payload data at rising edge of the
clock. Or,
The RxTSClk_n pin will be a clock enable signal to Receive Fractional DS1 Out-
put signal (RxFrTD_n) when the un-gaped Receive Serial Output Clock
(RxSerClk_n) is used to latch in Fractional DS1 Payload Data into the Terminal
Equipment.
232
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
When configured to operate in normal condition (that is, when the Receive Fractional T1 Input Enable bit is
equal to zero), these bits reflect the five-bit binary value of the Time Slot number (0 - 23) being outputted and
processed by the Receive Payload Data Output Interface block of the framer. RxTSb[4] represents the MSB of
the binary value and RxTSb[0] represents the LSB.
When the Receive Fractional T1 Output Enable bit is equal to one, the RxTSb[0]_n bit becomes the Receive
Fractional T1 Output signal (RxFrTD_n). This output pin carries Fractional T1 Output data extracted by the
framer from the incoming DS1 data stream. The Fractional T1 Output Interface allows certain time-slots of DS1
data to be routed to destinations other than the local Terminal Equipment. Function of the Fractional T1 Output
signal will be discussed in details in later sections.
When the Receive Fractional T1 Output Enable bit is equal to one, the RxTSb[1]_n bit becomes the Receive
Signaling Data Output signal (RxSig_n). These output pins can be used to carry robbed-bit signaling data ex-
tracted from the inbound DS1 frame. Function of the Receive Signaling Data Output signal will be discussed in
details in later sections.
When the Receive Fractional T1 Output Enable bit is equal to one, the RxTSb[2]_n bit serially outputs all five-
bit binary values of the Time Slot number (0-23) being outputted and processed by the Receive Payload Data
Output Interface block of the framer. MSB of the binary value is presented first and the LSB is presented last.
The RxTSb[3]_n and RxTSb[4}_n pins are not multiplexed.
The table below shows functionality of the RxTSb[2:0] bits when the Receive Fractional T1 Output bit is set to
different values.
TABLE 43: THE RXTSB[2:0] BITS WHEN THE RECEIVE FRACTIONAL T1 OUTPUT BIT IS SET TO DIFFERENT VALUES
RECEIVE FRACTIONAL T1 OUTPUT BIT = 0
RECEIVE FRACTIONAL T1 OUTPUT BIT = 1
RxTSb[0]
RxTSb[1]
RxTSb[2]
Output
Output
Output
RxFrTD
RxSig
RxTS
Output
Output
Output
The Receive Time-slot Indicator Clock signal (RxTSClk_n) is a multi-function output pin. When configured to
operate in normal condition (that is, when the Receive Fractional T1 Input Enable bit is equal to zero), the
RxTSClk_n is a 192KHz clock that pulses HIGH for one DS1 bit period whenever the Receive Payload Data
Output Interface block is outputting the LSB of each of the twenty-four time slots. The local Terminal Equipment
should use this clock signal to sample the RxTSb[0] through RxTSb[4] bits and identify the time-slot being pro-
cessed via the Receive Section of the framer.
When the Receive Fractional T1 Output Enable bit is equal to one, the RxTSClk_n will output gaped fractional
DS1 clock whenever Fractional DS1 payload data is present at the RxFrTD_n pin. The local Terminal Equip-
ment can latch in Fractional DS1 payload data at falling edge of the clock. Otherwise, this pin will be a clock en-
able signal to Receive Fractional DS1 output signal (RxFrTD_n) if the framer is configured accordingly. In this
way, Fractional DS1 payload data is clocked into the Terminal Equipment using un-gaped Receive Serial Out-
put Clock (RxSerClk_n). A detailed discussion of the Fractional DS1 Payload Data Output Interface can be
found in later sections.
A detailed discussion of how to connect the Receive Payload Data Output Interface block to the local Terminal
Equipment with Slip Buffer enabled or disabled can be found in the later sections.
5.1.2.1 Connect the Receive Payload Data Output Interface block to the Local Terminal Equipment if
the Slip Buffer is bypassed
By setting the Slip Buffer Enable [1:0] bits of the Slip Buffer Control Register to 00 or 11, the Receive Framer
Module routes the Receive Payload Data directly to the Receive Payload Data Output Interface without passing
through the Elastic Buffer. The XRT84L38 uses the Recovered Receive Line Clock internally to carry the Re-
ceive Payload Data directly across the whole chip. The Recovered Receive Line Clock is essentially become
timing source of the Receive Serial Clock output.
233
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
If the Slip Buffer is bypassed, the Receive Single-frame Synchronization signal is automatically configured to
be output signals. It should pulse HIGH for one DS1 bit period (648ns) at the last bit position of each DS1
frame. By triggering on the HIGH pulse on the Receive Single-frame Synchronization signal, the Terminal
Equipment can identify the end of a DS1 frame and should prepare to accept payload data of the next DS1
frame from the framer.
The Receive Multi-frame Synchronization signal should pulse HIGH for one DS1 bit period (648ns) at the last
bit position of a DS1 multi-frame. By triggering on the HIGH pulse on the Receive Multi-frame Synchronization
signal, the framer can identify the end of a DS1 super-frame and should prepare to accept payload data of the
next DS1 super-frame from the framer.
See Figure 43 for how to connect the Receive Payload Data Output Interface block to the local Terminal Equip-
ment when the Slip Buffer is bypassed and the Recovered Receive Line Clock is timing source of the Receive
section.
FIGURE 43. INTERFACING XRT84L38 LOCAL TERMINAL EQUIPMENT WITH SLIP BUFFER BYPASSED AND RECOV-
ERED RECEIVE LINE CLOCK AS RECEIVE TIMING SOURCE
XRT84L38
RxSerClk_0
RxLineClk_0
RxSer_0
Receive
Payload
Data Input
Interface
Chn 0
RxMSync_0
RxSync_0
RxTSClk_0
RxTSb[4:0]_0
Terminal
Equipment
RxSerClk_7
RxSer_7
Receive
Payload
Data Input
Interface
Chn 7
RxMSync_7
RxSync_7
RxTSClk_7
RxTSb[4:0]_7
RxLineClk_7
The following Figure 44 shows waveforms of the signals (RxSerClk_n, RxSer_n, RxSync_n, RxTSClk_n and
RxTSb[4:0]_n) which connecting the Receive Payload Data Output Interface block to the local Terminal Equip-
234
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
ment when the Slip Buffer is bypassed and the Recovered Receive Line Clock is timing source of the Receive
section.
FIGURE 44. WAVEFORMS OF THE SIGNALS CONNECTING THE RECEIVE PAYLOAD DATA OUTPUT INTERFACE BLOCK
TO THE LOCAL TERMINAL EQUIPMENT WHEN THE SLIP BUFFER IS BYPASSED AND THE RECOVERED LINE CLOCK IS
THE TIMING SOURCE OF THE RECEIVE SECTION
Timeslot 0
Timeslot 5
Timeslot 6
Input Data
Timeslot 16
Input Data
RxSerClk
RxSer
RxSync(input)
RxSync(output)
RxTSClk
RxTSb[4:0]
Timeslot #0
Timeslot #5
Timeslot #6
Timeslot #16
RxTSb[0]/RxSig
RxTSb[2]/RxTSb
A B C D
A B C D
A B C D
A B C D
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
RxTSClk
RxTSb[1]/RxFrTD
1 2 3 4 5 6 7 8
5.1.2.2 Connect the Receive Payload Data Output Interface block to the Local Terminal Equipment if
the Slip Buffer is enabled
By setting the Slip Buffer Enable [1:0] bits of the Slip Buffer Control Register to 01, the framer includes the two-
frame Elastic Buffer into its data path. The Receive Framer Module routes the Receive Payload Data to the
Elastic Buffer first. The Receive Payload Data is then presented to the Receive Payload Data Output Interface.
The XRT84L38 uses the Recovered Receive Line Clock internally to clock in the Receive Payload Data into the
Elastic Buffer. The Terminal Equipment should provide a 1.544MHz clock to the Receive Serial Clock input pin
to latch data out from the Elastic Buffer.
The Recovered Receive Line Clock and the Receive Serial Clock are generated from two different timing
sources. That is, the Recovered Receive Line Clock is originating from a remote site while Receive Serial
Clock generating by a local oscillator. Any mismatch in frequencies of these two clocks will result in the Slip
Buffer to gradually fill or deplete.
Overtime, the Elastic Buffer either fills or empties completely. Once that happened, a controlled slip by the
XRT84L38 will occur. The Receive Slip Buffer Slip bit of the Slip Buffer Status Register (SBSR) is set to 1.
If the buffer empties and a read occurs, then a full frame of data will be repeated and the Receive Slip Buffer
Empty bit of the Slip Buffer Status Register (SBSR) will be forced HIGH. If the buffer fills and a write comes,
then a full frame of data will be deleted and the Receive Slip Buffer Full bit of the Slip Buffer Status Register
(SBSR) will be forced HIGH.
The following table demonstrates settings of the Receive Slip Buffer Slip bit, Receive Slip Buffer Empty bit and
Receive Slip Buffer Full bit of the Slip Buffer Status Register.
235
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
SLIP BUFFER STATUS REGISTER (SBSR) (INDIRECT ADDRESS = 0xnAH, 0x08H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
2
Receive Slip
Buffer Full
R/W
0 - The Receive Slip Buffer is not full.
1 - The Receive Slip Buffer is full and one frame of data is discarded.
1
0
Receive Slip
Buffer Empty
R/W
R/W
0 - The Receive Slip Buffer is not empty.
1 - The Receive Slip Buffer is empty and one frame of data is repeated.
Receive Slip
Buffer Slip
0 - The Receive Slip Buffer does not slip.
1 - The Receive Slip Buffer slips since either full or emptied.
In this mode, the Receive Single-Frame Synchronization signal can be either input or output depending on the
settings of the Slip Buffer Receive Synchronization Direction bit of the Slip Buffer Control Register. When the
Slip Buffer Receive Synchronization Direction bit is set to 0, the Receive Single-Frame Synchronization signal
(RxSync_n) is an output. When the Slip Buffer Receive Synchronization Direction bit is set to 1,the Receive
Single-Frame Synchronization signal (RxSync_n) is an input.
If the Receive Single-Frame Synchronization signal is an output, it should pulse HIGH for one DS1 bit period
(648ns) at the last bit position of each DS1 frame. By triggering on the HIGH pulse on the Receive Single-
frame Synchronization signal, the Terminal Equipment can identify the end of a DS1 frame and should prepare
to accept payload data of the next DS1 frame from the framer.
If the Receive Single-Frame Synchronization signal is an input, it should pulse HIGH for one DS1 bit period
(648ns) at the first bit position (F-bit) of each DS1 frame. By sampling the HIGH pulse of the Receive Single-
frame Synchronization signal, the framer should identify the beginning of a DS1 frame and can send out data in
a synchronized way. It is the responsibility of the local Terminal Equipment to align the start of a DS1 frame
with the Receive Single-Frame Synchronization pulse.
The Receive Multi-frame Synchronization signal should pulse HIGH for one DS1 bit period (648ns) at the last
bit position of Frame number one of a DS1 multi-frame. By triggering on the HIGH pulse on the Receive Multi-
frame Synchronization signal, the framer can identify the end of a DS1 super-frame and should prepare to ac-
cept payload data of the next DS1 super-frame from the framer.
236
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
See Figure 45 for how to connect the Receive Payload Data Output Interface block to the local Terminal Equip-
ment when the Slip Buffer is enabled.
FIGURE 45. INTERFACING XRT84L38 TO LOCAL TERMINAL EQUIPMENT WITH SLIP BUFFER ENABLED OR ACTS AS
FIFO
XRT84L38
RxSerClk_0
RxSer_0
Receive
RxMSync_0
RxSync_0
Payload
Data Input
Interface
Chn 0
RxTSClk_0
RxTSb[4:0]_0
Terminal
Equipment
RxSerClk_7
RxSer_7
Receive
Payload
Data Input
Interface
Chn 7
RxMSync_7
RxSync_7
RxTSClk_7
RxTSb[4:0]_7
237
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The following Figure 46 shows waveforms of the signals (RxSerClk_n, RxSer_n, RxSync_n, RxTSClk_n and
RxTSb[4:0]_n) which connecting the Receive Payload Data Output Interface block to the local Terminal Equip-
ment when the Slip Buffer is enabled.
FIGURE 46. WAVEFORMS OF THE SIGNALS THAT CONNECT THE RECEIVE PAYLOAD DATA OUTPUT INTERFACE
BLOCK TO THE LOCAL TERMINAL EQUIPMENT WHEN THE SLIP BUFFER IS ENABLED
Timeslot 0
Timeslot 5
Timeslot 6
Input Data
Timeslot 16
Input Data
RxSerClk
RxSer
RxSync(input)
RxSync(output)
RxTSClk
RxTSb[4:0]
Timeslot #0
Timeslot #5
Timeslot #6
Timeslot #16
RxTSb[0]/RxSig
RxTSb[2]/RxTSb
A B C D
A B C D
A B C D
A B C D
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
RxTSClk
RxTSb[1]/RxFrTD
1 2 3 4 5 6 7 8
5.1.2.3 Connect the Receive Payload Data Output Interface block to the Local Terminal Equipment if
the Slip Buffer is configured as FIFO
By setting the Slip Buffer Enable [1:0] bits of the Slip Buffer Control Register to 10, the framer puts the Elastic
Buffer into FIFO mode. Receive Framer Module routes the Receive Payload Data through the First-In-First-Out
storage to the Receive Payload Data Output Interface. The XRT84L38 uses the Recovered Receive Line Clock
internally to clock in the Receive Payload Data into the FIFO. The Terminal Equipment should provide an exter-
nal 1.544MHz clock to the Receive Serial Clock input pin to latch data out from the FIFO.
It is the responsibility of the user to phase lock the input Receive Serial Clock to the Recovered Receive Line
Clock to avoid either over-run or under-run of the FIFO. The latency between writing a bit into the FIFO and
reading the same bit from it (READ and WRITE latency) is actually depth of the FIFO, which is maintained in a
programmable fashion controlled by the FIFO Latency Register (FIFOLR). The largest possible depth of the
FIFO is thirty-two bytes or one E1 frame. The default depth of the FIFO when XRT84L38 first powered up is
four bytes. The table below shows the FIFO Latency Register.
FIFO LATENCY REGISTER (FIFOLR) (INDIRECT ADDRESS = 0xn0H, 0x17H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
4-0
FIFO Latency
R/W
These bits determine depth of the FIFO in terms of bytes. The largest possible
value is thirty-two bytes or one E1 frame.
In this mode, the Receive Single-Frame Synchronization signal can be either input or output depending on the
settings of the Slip Buffer Receive Synchronization Direction bit of the Slip Buffer Control Register. When the
Slip Buffer Receive Synchronization Direction bit is set to 0, the Receive Single-Frame Synchronization signal
238
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
(RxSync_n) is an. When the Slip Buffer Receive Synchronization Direction bit is set to 1,the Receive Single-
Frame Synchronization signal (RxSync_n) is an input.
If the Receive Single-Frame Synchronization signal is an output, it should pulse HIGH for one DS1 bit period
(648ns) at the last bit position of each DS1 frame. By triggering on the HIGH pulse on the Receive Single-
frame Synchronization signal, the Terminal Equipment can identify the end of a DS1 frame and should prepare
to accept payload data of the next DS1 frame from the framer.
If the Receive Single-Frame Synchronization signal is an input, it should pulse HIGH for one DS1 bit period
(648ns) at the first bit position (F-bit) of each DS1 frame. By sampling the HIGH pulse of the Receive Single-
frame Synchronization signal, the framer should identity the beginning of a DS1 frame and can send out data in
a synchronized way. It is the responsibility of the local Terminal Equipment to align the start of a DS1 frame
with the Receive Single-Frame Synchronization pulse.
The Receive Multi-frame Synchronization signal should pulse HIGH for one DS1 bit period (648ns) at the last
bit position of Frame number one of a DS1 multi-frame. By triggering on the HIGH pulse on the Receive Multi-
frame Synchronization signal, the framer can identify the end of a DS1 super-frame and should prepare to ac-
cept payload data of the next DS1 super-frame from the framer.
See Figure 47 for how to connect the Receive Payload Data Output Interface block to the local Terminal Equip-
ment when the Slip Buffer is acted as FIFO.
FIGURE 47. INTERFACING XRT84L38 TO LOCAL TERMINAL EQUIPMENT WITH SLIP BUFFER ENABLED OR ACTS AS
FIFO
XRT84L38
RxSerClk_0
RxSer_0
Receive
RxMSync_0
RxSync_0
Payload
Data Input
Interface
Chn 0
RxTSClk_0
RxTSb[4:0]_0
Terminal
Equipment
RxSerClk_7
RxSer_7
Receive
Payload
Data Input
Interface
Chn 7
RxMSync_7
RxSync_7
RxTSClk_7
RxTSb[4:0]_7
The following Figure 48 shows waveforms of the signals (RxSerClk_n, RxSer_n, RxSync_n, RxTSClk_n and
RxTSb[4:0]_n) which connecting the Receive Payload Data Output Interface block to the local Terminal Equip-
ment when the Slip Buffer is acted as FIFO.
239
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
FIGURE 48. WAVEFORMS OF THE SIGNALS THAT CONNECT THE RECEIVE PAYLOAD DATA OUTPUT INTERFACE
BLOCK TO THE LOCAL TERMINAL EQUIPMENT WHEN THE SLIP BUFFER IS ACTED AS FIFO
Timeslot 0
Timeslot 5
Timeslot 6
Input Data
Timeslot 16
Input Data
RxSerClk
RxSer
RxSync(input)
RxSync(output)
RxTSClk
RxTSb[4:0]
Timeslot #0
Timeslot #5
Timeslot #6
Timeslot #16
RxTSb[0]/RxSig
RxTSb[2]/RxTSb
A B C D
A B C D
A B C D
A B C D
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
RxTSClk
RxTSb[1]/RxFrTD
1 2 3 4 5 6 7 8
5.1.3 High Speed Receive Back-plane Interface
The High-speed Back-plane Interface supports payload data to be taken from or presented to the local Termi-
nal Equipment at a rate higher than 1.544Mbit/s. In DS1 mode, supported High-speed data rates are MVIP
2.048Mbit/s, 4.096Mbit/s, 8.192Mbit/s, multiplexed 12.352Mbit/s, multiplexed 16.384Mbit/s, HMVIP
16.384Mbit/s or H.100 16.384Mbit/s. The Receive Multiplex Enable bit and the Receive Interface Mode Select
[1:0] bits of the Receive Interface Control Register (RICR) determine the Receive Back-plane Interface data
rate.
The following table shows configurations of the Receive Multiplex Enable bit and the Receive Interface Mode
Select [1:0] bits of the Receive Interface Control Register (RICR).
RECEIVE INTERFACE CONTROL REGISTER (RICR) (INDIRECT ADDRESS = 0xn0H, 0x22H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
2
Receive
Multiplex Enable
R/W
0 - The Receive Back-plane Interface block is configured to non-channel-multi-
plexed mode.
1 - The Receive Back-plane Interface block is configured to channel-multiplexed
mode
1-0
Receive
Interface Mode
Select
R/W
When combined with the Receive Multiplex Enable bit, these bits determine the
Receive Back-plane Interface data rate.
240
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The table below shows the combinations of Receive Multiplex Enable bit and Receive Interface Mode Select
[1:0] bits and the resulting Receive Back-plane Interface data rates.
TABLE 44: RECEIVE MULTIPLEX ENABLE BIT AND RECEIVE INTERFACE MODE SELECT [1:0] BITS WITH THE
RESULTING RECEIVE BACK-PLANE INTERFACE DATA RATES
RECEIVE MULTIPLEX ENABLE
BIT
RECEIVE INTERFACE MODE
SELECT BIT 1
RECEIVE INTERFACE MODE
SELECT BIT 0
BACK-PLANE INTERFACE
DATA RATE
0
0
0
0
1
1
1
1
0
0
1
1
0
0
1
1
0
1
0
1
0
1
0
1
1.544Mbit/s
MVIP 2.048Mbit/s
4.096Mbit/s
8.192Mbit/s
Multiplexed 12.352Mbit/s
Bit Multiplexed 16.384Mbit/s
HMVIP 16.384Mbit/s
H.100 16.384Mbit/s
When the Receive Multiplex Enable bit is set to zero, the framer is configured in non-channel-multiplexed
mode. The possible data rates are 1.544Mbit/s, MVIP 2.048Mbit/s, 4.096Mbit/s and 8.192Mbit/s. In non-chan-
nel-multiplexed mode, payload data of each channel are sending out from the Receive High-speed Back-plane
Interface separately. Each channel uses its own Receive Serial Clock, Receive Serial Data, Receive Single-
frame Synchronization signal and Receive Multi-frame Synchronization signal as interface between the framer
and the Terminal Equipment. Section 5.1.1.1, 5.1.1.2 and 5.1.1.3 provide details on how to connect the Re-
ceive Payload Data Interface block with the local Terminal Equipment when the Back-plane interface data rate
is 1.544Mbit/s.
When the Back-plane interface data rate is MVIP 2.048Mbit/s, 4.096Mbit/s and 8.192Mbit/s, the Receive Serial
Clock, Receive Serial Data and Receive Single-frame Synchronization are all configured as inputs. The Re-
ceive Multi-frame Synchronization signal is still output. The Receive Serial Clock is configured as an input tim-
ing source for the High-speed Back-plane Interface with frequencies of 2.048 MHz, 4.096 MHz and 8.192 MHz
respectively.
The table below summaries the clock frequencies of RxSerClk_n input when the framer is operating in non-
multiplexed High-speed Back-plane mode.
RECEIVE MULTIPLEX ENABLE BIT = 0
RECEIVE INTERFACE MODE
SELECT BIT 1
RECEIVE INTERFACE MODE
SELECT BIT 0
BACK-PLANE INTERFACE
DATA RATE
RXSERCLK
0
0
1
1
0
1
0
1
1.544Mbit/s
MVIP 2.048Mbit/s
4.096Mbit/s
1.544MHz
2.048 MHz
4.096 MHz
8.192 MHz
8.192Mbit/s
When the Receive Multiplex Enable bit is set to one, the framer is configured in channel-multiplexed mode. The
possible data rates are multiplexed 12.352Mbit/s, bit-multiplexed 16.384Mbit/s, HMVIP 16.384Mbit/s and H.100
16.384Mbit/s. In channel-multiplexed mode, four channels share the Receive Serial Data, Receive Single-
frame Synchronization signal and Receive Serial Clock of one channel as interface between the framer and the
Terminal Equipment. The Receive Serial Clock runs at frequencies of 12.352 MHz or 16.384 MHz. It serves as
the primary clock source for the High-speed Back-plane Interface.
241
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
Payload and signaling data of Channel 0-3 are multiplexed onto the Receive Serial Data pin of Channel 0. Pay-
load and signaling data of Channel 4-7 are multiplexed onto the Receive Serial Data pin of Channel 4. The Re-
ceive Single-frame Synchronization signal of Channel 0 pulses HIGH at the beginning of the frame with data
from Channel 0-3 multiplexed together. The Receive Single-frame Synchronization signal of Channel 4 pulses
HIGH at the beginning of the frame with data from Channel 4-7 multiplexed together.
The table below summaries the clock frequencies of RxSerClk_n input when the framer is operating in multi-
plexed High-speed Back-plane mode.
RECEIVE MULTIPLEX ENABLE BIT = 1
RECEIVE INTERFACE MODE
SELECT BIT 1
RECEIVE INTERFACE MODE
SELECT BIT 0
BACK-PLANE INTERFACE
DATA RATE
RXSERCLK
0
0
1
1
0
1
0
1
Multiplexed 12.352Mbit/s
Bit-multiplexed 16.384Mbit/s
HMVIP 16.384Mbit/s
12.352 MHz
16.384 MHz
16.384 MHz
16.384 MHz
H.100 16.384Mbit/s
When the frame is running at High-speed Back-plane Interface mode other than the 1.544Mbit/s data rate, the
Receive Single-frame Synchronization signal could pulse HIGH or LOW indicating boundaries of DS1 frames.
The Receive Synchronization Pulse Low bit of the Receive Interface Control Register (TICR) determines
whether the Receive Single-frame Synchronization signal is HIGH active or LOW active.
The table below shows configurations of the Receive Synchronization Pulse LOW bit of the Receive Interface
Control Register (RICR).
RECEIVE INTERFACE CONTROL REGISTER (RICR) (INDIRECT ADDRESS = 0xn0H, 0x22H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3
Receive
Synchronization
Pulse LOW
R/W
0 - The Receive Single-frame Synchronization signal will pulse HIGH indicat-
ing the beginning of a DS1 frame when the High-speed Back-plane Interface
is running at a mode other than the 1.544Mbit/s.
1 - The Receive Single-frame Synchronization signal will pulse LOW indicating
the beginning of a DS1 frame when the High-speed Back-plane Interface is
running at a mode other than the 1.544Mbit/s.
Throughout the discussion of this datasheet, we assume that the Receive Single-frame Synchronization signal
pulses HIGH unless stated otherwise.
The following sections discuss details of how to operate the framer in different Back-plane interface speed
mode and how to connect the Receive Payload Data Output Interface block to the local Terminal Equipment.
5.1.3.1 T1 Receive Input Interface - MVIP 2.048 MHz
When the Receive Multiplex Enable bit is set to zero and the Receive Interface Mode Select [1:0] bits are set to
01, the Receive Back-plane interface of framer is running at a data rate of 2.048Mbit/s.
The interface consists of the following pins:
• Data input (RxSer_n)
• Receive Serial Clock Input signal (RxSerClk_n)
• Receive Single-frame Synchronization Input signal (RxSync_n)
• Receive Input Clock (RxInClk_n)
• Receive Time-slot Indication clock (RxTSClk_n)
242
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
• Receive Time Slot indicator bits (RxTSb[4:0]_n)
The Receive Back-plane interface is pumping out data through RxSer_n at an E1 equivalent data rate of
2.048Mbit/s. The local Terminal Equipment supplies a free-running 2.048MHz clock to the Receive Serial Clock
input. The Receive High-speed Back-plane Interface of the framer then sends out serial data at rising edge of
the Receive Serial Clock. The local Terminal Equipment samples the serial data at falling edge of the clock.
The Terminal Equipment take in data grouped in 256-bit frame 8000 times every second. Each frame consists
of thirty-two octets as in E1. The Receive High-speed Back-plane Interface maps a 193-bit T1 frame into this
256-bit format as described below:
1. The F-bit is mapped into MSB of the first E1 Time-slot. The framer will insert seven "don't care" bits to the
rest of the first octet that would be ignored by the local Terminal Equipment.
2. Payload data of T1 Time-slot 0, 1 and 2 are mapped into E1 Time-slot 1, 2 and 3.
3. The Receive High-speed Back-plane Interface will stuff E1 Time-slot 4 with eight "don't care" bits that
would be ignored by the local Terminal Equipment.
4. Following the same rules of Step 2 and 3, the Receive High-speed Back-plane Interface maps every three
time-slots of T1 payload data into four E1 time-slots.
The mapping of T1 frame into E1 framing format is shown in the table below.
TABLE 45: THE MAPPING OF T1 FRAME INTO E1 FRAMING FORMAT
T1
E1
T1
E1
T1
E1
T1
E1
F-Bit
TS0
TS0
TS1
TS1
TS2
TS2
TS3
Don't Care Bits
TS4
TS3
TS5
TS4
TS6
TS5
TS7
Don't Care Bits
TS8
TS6
TS7
TS8
Don't Care Bits
TS12
TS9
TS10
TS14
TS16
TS22
TS22
TS30
TS11
TS15
TS17
TS23
TS23
TS31
TS9
TS10
TS13
TS18
TS19
TS26
TS11
TS14
TS19
TS20
TS27
TS13
TS15
TS21
TS21
TS29
Don't Care Bits
TS16
TS12
TS17
TS18
TS25
Don't Care Bits
TS20
Don't Care Bits
TS24
Don't Care Bits
TS28
The Receive Single-frame Synchronization input signal (RxSync_n) should pulse HIGH at the beginning of the
256-bit frame indicating start of the frame. By sampling the HIGH pulse of the Receive Single-frame Synchroni-
zation signal, the framer can identity the beginning of a DS1 frame and start pumping payload data out.
243
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
See Figure 49 below for how to interface the local Terminal Equipment with the Receive Payload Data Output
Interface block of the framer in MVIP 2.048Mbit/s mode.
FIGURE 49. INTERFACING XRT84L38 TO LOCAL TERMINAL EQUIPMENT USING MVIP 2.048MBIT/S DATA BUS
XRT84L38
RxSerClk_0 (2.048MHz)
Receive
RxSer_0
Payload
RxMSync_0
RxSync_0
Data Input
Interface
Chn 0
Terminal
Equipment
RxSerClk_7 (2.048MHz)
RxSer_7
Receive
Payload
Data Input
Interface
Chn 7
RxMSync
RxSync_7
The timing diagram of input signals to the framer when running at MVIP 2.048Mbit/s mode is shown in
Figure 50.
FIGURE 50. TIMING DIAGRAM OF INPUT SIGNALS TO THE FRAMER WHEN RUNNING AT MVIP 2.048MBIT/S
Timeslot 1
Timeslot 2
Timeslot 3
Timeslot 4
RxSerClk
RxSerClk(INV)
RxSer
F
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8
RxSync(input)
RxSync(input)
(MVIP)
RxTSb[0]/RxSig
RxTSb[2]/RxChn
RxTSClk(INV)
A B C D
A B C D
A B C D
A B C D
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
RxTSb[1]/FrRxD
RxTSClk
(RxSyncFrTD=1)
1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8
RxTSClk
(RxSyncFrTD=1)
[
5.1.3.2 T1 Receive Input Interface - 4.096 MHz
This interface mode is the same as running at 2.048 MHz. The only difference is that the Receive Serial Clock
runs two times faster at 4.096 MHz.
244
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
When the Receive Multiplex Enable bit is set to zero and the Receive Interface Mode Select [1:0] bits are set to
10, the Receive Back-plane interface of framer is running at a clock rate of 4.096MHz.
The interface consists of the following pins:
• Data input (RxSer_n)
• Receive Serial Clock Input signal (RxSerClk_n)
• Receive Single-frame Synchronization Input signal (RxSync_n)
• Receive Input Clock (RxInClk_n)
• Receive Time-slot Indication clock (RxTSClk_n)
• Receive Time Slot indicator bits (RxTSb[4:0]_n)
The Receive Back-plane interface is pumping out data through RxSer_n at an E1 equivalent data rate of
2.048Mbit/s. The local Terminal Equipment supplies a free-running 4.096MHz clock to the Receive Serial Clock
input. The Receive High-speed Back-plane Interface of the framer then sends out serial data at every other ris-
ing edge of the Receive Serial Clock. The local Terminal Equipment samples the serial data at every other fall-
ing edge of the clock.
The Terminal Equipment take in data grouped in 256-bit frame 8000 times every second. Each frame consists
of thirty-two octets as in E1. The Receive High-speed Back-plane Interface maps a 193-bit T1 frame into this
256-bit format as described below:
1. The F-bit is mapped into MSB of the first E1 Time-slot. The framer will insert seven "don't care" bits to the
rest of the first octet that would be ignored by the local Terminal Equipment.
2. Payload data of T1 Time-slot 0, 1 and 2 are mapped into E1 Time-slot 1, 2 and 3.
3. The Receive High-speed Back-plane Interface will stuff E1 Time-slot 4 with eight "don't care" bits that
would be ignored by the local Terminal Equipment.
4. Following the same rules of Step 2 and 3, the Receive High-speed Back-plane Interface maps every three
time-slots of T1 payload data into four E1 time-slots.
The mapping of T1 frame into E1 framing format is shown in the table below.
TABLE 46: THE MAPPING OF T1 FRAME INTO E1 FRAMING FORMAT
T1
E1
T1
E1
T1
E1
T1
E1
F-Bit
TS0
TS0
TS1
TS1
TS2
TS2
TS3
Don't Care Bits
TS4
TS3
TS5
TS4
TS6
TS5
TS7
Don't Care Bits
TS8
TS6
TS7
TS8
Don't Care Bits
TS12
TS9
TS10
TS14
TS16
TS22
TS22
TS30
TS11
TS15
TS17
TS23
TS23
TS31
TS9
TS10
TS13
TS18
TS19
TS26
TS11
TS14
TS19
TS20
TS27
TS13
TS15
TS21
TS21
TS29
Don't Care Bits
TS16
TS12
TS17
TS18
TS25
Don't Care Bits
TS20
Don't Care Bits
TS24
Don't Care Bits
TS28
The Receive Single-frame Synchronization input signal (RxSync_n) should pulse HIGH at the beginning of the
256-bit frame indicating start of the frame. By sampling the HIGH pulse of the Receive Single-frame Synchroni-
zation signal, the framer can identity the beginning of a DS1 frame and start pumping payload data out.
245
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
See Figure 51 below for how to interface the local Terminal Equipment with the Receive Payload Data Output
Interface block of the framer in 4.096Mbit/s mode.
FIGURE 51. INTERFACING XRT84L38 TO LOCAL TERMINAL EQUIPMENT USING 4.096MBIT/S DATA BUS
XRT84L38
RxSerClk_0 (4.096MHz)
Receive
RxSer_0
Payload
RxMSync_0
RxSync_0
Data Input
Interface
Chn 0
Terminal
Equipment
RxSerClk_7 (4.096MHz)
RxSer_7
Receive
Payload
Data Input
Interface
Chn 7
RxMSync_7
RxSync_7
The timing diagram of input signals to the framer when running at 4.096Mbit/s mode is shown in Figure 52.
FIGURE 52. TIMING DIAGRAM OF INPUT SIGNALS TO THE FRAMER WHEN RUNNING AT 4.096MBIT/S
RxSerClk (4MHz)
RxSer
F
Don't Care
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
Don't care
Don't care
1 2 3 4 5 6 7 8
RxSync(input)
RxChn[0]/RxSig
Don't Care
Don't Care
A B C D
Don't Care
A B C D
Don't Care
A B C D
A B C D
Note: The following signals are not aligned with the signals shown above. The RxChClk is derived from 1.544MHz transmit clock.
RxTSClk(INV)
Don't Care
1 2 3 4 5 6 7 8
Don't Care
1 2 3 4 5 6 7 8
RxTSb[1]/RxFrTD
5.1.3.3 T1 Receive Input Interface - 8.192 MHz
This interface mode is the same as running at 2.048 MHz. The only difference is that the Receive Serial Clock
runs four times faster at 8.192MHz.
When the Receive Multiplex Enable bit is set to zero and the Receive Interface Mode Select [1:0] bits are set to
11, the Receive Back-plane interface of framer is running at a clock rate of 8.192MHz.
The interface consists of the following pins:
• Data input (RxSer_n)
• Receive Serial Clock Input signal (RxSerClk_n)
246
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
• Receive Single-frame Synchronization Input signal (RxSync_n)
• Receive Input Clock (RxInClk_n)
• Receive Time-slot Indication clock (RxTSClk_n)
• Receive Time Slot indicator bits (RxTSb[4:0]_n)
The Receive Back-plane interface is pumping out data through RxSer_n at an E1 equivalent data rate of
2.048Mbit/s. The local Terminal Equipment supplies a free-running 8.192MHz clock to the Receive Serial Clock
input. The Receive High-speed Back-plane Interface of the framer then sends out serial data at every other
four rising edge of the Receive Serial Clock. The local Terminal Equipment samples the serial data at every
other four falling edge of the clock.
The Terminal Equipment take in data grouped in 256-bit frame 8000 times every second. Each frame consists
of thirty-two octets as in E1. The Receive High-speed Back-plane Interface maps a 193-bit T1 frame into this
256-bit format as described below:
1. The F-bit is mapped into MSB of the first E1 Time-slot. The framer will insert seven "don't care" bits to the
rest of the first octet that would be ignored by the local Terminal Equipment.
2. Payload data of T1 Time-slot 0, 1 and 2 are mapped into E1 Time-slot 1, 2 and 3.
3. The Receive High-speed Back-plane Interface will stuff E1 Time-slot 4 with eight "don't care" bits that
would be ignored by the local Terminal Equipment.
4. Following the same rules of Step 2 and 3, the Receive High-speed Back-plane Interface maps every three
time-slots of T1 payload data into four E1 time-slots.
The mapping of T1 frame into E1 framing format is shown in the table below.
TABLE 47: THE MAPPING OF T1 FRAME INTO E1 FRAMING FORMAT
T1
E1
T1
E1
T1
E1
T1
E1
F-Bit
TS0
TS0
TS1
TS1
TS2
TS2
TS3
Don't Care Bits
TS4
TS3
TS5
TS4
TS6
TS5
TS7
Don't Care Bits
TS8
TS6
TS7
TS8
Don't Care Bits
TS12
TS9
TS10
TS14
TS16
TS22
TS22
TS30
TS11
TS15
TS17
TS23
TS23
TS31
TS9
TS10
TS13
TS18
TS19
TS26
TS11
TS14
TS19
TS20
TS27
TS13
TS15
TS21
TS21
TS29
Don't Care Bits
TS16
TS12
TS17
TS18
TS25
Don't Care Bits
TS20
Don't Care Bits
TS24
Don't Care Bits
TS28
The Receive Single-frame Synchronization input signal (RxSync_n) should pulse HIGH at the beginning of the
256-bit frame indicating start of the frame. By sampling the HIGH pulse of the Receive Single-frame Synchroni-
zation signal, the framer can identity the beginning of a DS1 frame and start pumping payload data out.
247
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
See Figure 53 below for how to interface the local Terminal Equipment with the Receive Payload Data Output
Interface block of the framer in 8.192Mbit/s mode.
FIGURE 53. INTERFACING XRT84L38 TO LOCAL TERMINAL EQUIPMENT USING 8.192MBIT/S DATA BUS
XRT84L38
RxSerClk_0 (8.192MHz)
Receive
RxSer_0
Payload
RxMSync_0
RxSync_0
Data Input
Interface
Chn 0
Terminal
Equipment
RxSerClk_7 (8.192MHz)
RxSer_7
Receive
Payload
Data Input
Interface
Chn 7
RxMSync_7
RxSync_7
The timing diagram of input signals to the framer when running at 8.192Mbit/s mode is shown in Figure 54.
FIGURE 54. TIMING DIAGRAM OF INPUT SIGNALS TO THE FRAMER WHEN RUNNING AT 8.192MBIT/S
RxSerClk (8MHz)
RxSer
RxSync(input)
RxTSb[0]/RxSig
F
Don't Care
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
Don't care
Don't Care
1 2 3 4 5 6 7 8
Don't Care
Don't Care
A B C D
Don't Care
A B C D
Don't Care
A B C D
A B C D
Note: The following signals are not aligned with the signals shown above. The RxChClk is derived from 1.544MHz transmit clock.
RxTSClk(INV)
Don't Care
1 2 3 4 5 6 7 8
Don't Care
1 2 3 4 5 6 7 8
RxTSb[1]/RxFrTD
5.1.3.4 T1 Receive Input Interface - Multiplexed 12.352Mbit/s
When the Receive Multiplex Enable bit is set to one and the Receive Interface Mode Select [1:0] bits are set to
00, the Receive Back-plane interface of framer is running at a clock rate of 12.352MHz.
The interface consists of the following pins:
• Data input (RxSer_n)
• Receive Serial Clock Input signal (RxSerClk_n)
• Receive Single-frame Synchronization Input signal (RxSync_n)
• Receive Input Clock (RxInClk_n)
248
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
• Receive Time-slot Indication clock (RxTSClk_n)
• Receive Time Slot indicator bits (RxTSb[4:0]_n)
The Receive Back-plane Interface is pumping data through RxSer_0 or RxSer_4 pins at 12.352Mbit/s. It multi-
plexes payload and signaling data of every four channels into one data stream. Payload and signaling data of
Channel 0-3 are multiplexed onto the Receive Serial Data pin of Channel 0. Payload and signaling data of
Channel 4-7 are multiplexed onto the Receive Serial Data pin of Channel 4.
Free-running clocks of 12.352MHz are supplied to the Receive Serial Clock pin of Channel 0 and Channel 4 of
the framer. The Receive High-speed Back-plane Interface of the farmer provides data at rising edge of this Re-
ceive Serial Clock. The local Terminal Equipment then latches incoming serial data at falling edge of the clock.
The Receive High-speed Back-plane Interface multiplexes four 1.544Mbit/s DS1 data streams into this
12.352Mbit/s data stream as described below:
1. The F-bit of four channels are repeated and grouped together to form the first octet of the multiplexed data
stream. The F-bit of Channel 0 is sent first, followed by F-bit of Channel 1 and 2. The F-bit of Channel 3 is
sent last. The table below shows bit-pattern of the first octet.
FIRST OCTET OF 12.352MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
F0
F0
F1
F1
F2
F2
F3
F3
FX: F-bit of Channel X
2. Payload data of four channels are repeated and grouped together in a bit-interleaved way. The first payload
bit of Timeslot 0 of Channel 0 is sent first, followed by the first payload bit of Timeslot 0 of Channel 1 and 2.
The first payload bit of Timeslot 0 of Channel 3 is sent last. After the first bits of Timeslot 0 of all four chan-
nels are sent, it comes the second bit of Timeslot 0 of Channel 0 and so on. The table below demonstrates
how payload bits of four channels are mapped into the 12.352Mbit/s data stream.
SECOND OCTET OF 12.352MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
10
10
11
11
12
12
13
13
THIRD OCTET OF 12.352MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
20
20
21
21
22
22
23
23
XY: The Xth payload bit of Channel Y
3. The Receive High-speed Back-plane Interface also multiplexed signaling bits with payload bits and sent
them together through the 12.352Mbit/s data stream. When Receive High-speed Back-plane Interface is
sending the fifth payload bit of a particular channel, instead of sending it twice, it inserts the signaling bit A
of that particular channel. Similarly, the sixth payload bit of a particular channels is followed by the signal-
ing bit B of that channel; the seventh payload bit is followed by the signaling bit C; the eighth payload bit is
followed by the signaling bit D.
249
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The following table illustrates how payload bits and signaling bits are multiplexed together into the 12.352Mbit/
s data stream.
SIXTH OCTET OF 12.352MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
50
A0
51
A1
52
A2
53
A3
SEVENTH OCTET OF 12.352MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
60
B0
61
B1
62
B2
63
B3
EIGHTH OCTET OF 12.352MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
70
C0
71
C1
72
C2
73
C3
NINETH OCTET OF 12.352MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
80
D0
81
D1
82
D2
83
D3
XY: The Xth payload bit of Channel Y
AY: The signaling bit A of Channel Y
4. Following the same rules of Step 2 and 3, the Receive High-speed Back-plane Interface maps the payload
data and signaling data of four channels into a 12.352Mbit/s data stream.
The Receive Single-frame Synchronization signal of Channel 0 pulses HIGH for one clock cycle at the first bit
position (F-bit of channel 0) of the data stream with data from Channel 0-3 multiplexed together. The Receive
Single-frame Synchronization signal of Channel 4 pulses HIGH for one clock cycle at the first bit position (F-bit
of Channel 4) of the data stream with data from Channel 4-7 multiplexed together. By sampling the HIGH pulse
of the Receive Single-frame Synchronization signal, the Receive High-speed Back-plane Interface of the fram-
er can identify the beginning of a multiplexed frame and can start sending payload data of that frame.
250
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
See Figure 55 below for how to interface the local Terminal Equipment with the Receive Payload Data Output
Interface block of the framer in 12.352Mbit/s mode.
FIGURE 55. INTERFACING XRT84L38 TO LOCAL TERMINAL EQUIPMENT USING 12.352MBIT/S DATA BUS
XRT84L38
RxSerClk_0 (12.352MHz)
Receive
RxSer_0
Payload
RxMSync_0
RxSync_0
Data Input
Interface
Chn 0-3
Terminal
Equipment
RxSerClk_4 (12.352MHz)
RxSer_4
Receive
Payload
Data Input
Interface
Chn 4-7
RxMSync_4
RxSync_4
The Input signal timing is shown in Figure 56 below when the framer is running at 12.352Mbit/s mode.
FIGURE 56. TIMING DIAGRAM OF INPUT SIGNALS TO THE FRAMER WHEN RUNNING AT 12.352MBIT/S
RxSerClk (12.352MHz)
RxSerClk (INV)
RxSer
F0 F0 F1 F1 F2 F2 F3 F3 10 X 11 X 12 X 13 X 20 X 21
X
30
X
40
X
50 A0 51 A1 52 A2 53 A3 60 B0 61 B1 62 B2 63 B3
RxSync(input)
5.1.3.5 T1 Receive Input Interface - Bit-Multiplexed 16.384Mbit/s
When the Receive Multiplex Enable bit is set to one and the Receive Interface Mode Select [1:0] bits are set to
01, the Receive Back-plane interface of framer is running at a clock rate of 16.384MHz.
The interface consists of the following pins:
• Data input (RxSer_n)
• Receive Serial Clock Input signal (RxSerClk_n)
• Receive Single-frame Synchronization Input signal (RxSync_n)
• Receive Input Clock (RxInClk_n)
• Receive Time-slot Indication clock (RxTSClk_n)
• Receive Time Slot indicator bits (RxTSb[4:0]_n)
The Receive Back-plane Interface is pumping out data through RxSer_0 or RxSer_4 pins at 16.384Mbit/s. It
multiplexes payload and signaling data of every four channels into one data stream. Payload and signaling data
of Channel 0-3 are multiplexed onto the Receive Serial Data pin of Channel 0. Payload and signaling data of
Channel 4-7 are multiplexed onto the Receive Serial Data pin of Channel 4.
251
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
Free-running clocks of 16.384MHz are supplied to the Receive Serial Clock pin of Channel 0 and Channel 4 of
the framer. The Receive High-speed Back-plane Interface of the farmer provides data at rising edge of this Re-
ceive Serial Clock. The local Terminal Equipment then latches incoming serial data at falling edge of the clock.
The Receive High-speed Back-plane Interface maps four 1.544Mbit/s DS1 data streams into this 16.384Mbit/s
data stream as described below:
1. The F-bit of four channels are repeated and grouped together to form the first octet of the multiplexed data
stream. The F-bit of Channel 0 is sent first, followed by F-bit of Channel 1 and 2. The F-bit of Channel 3 is
sent last. The table below shows bit-pattern of the first octet.
FIRST OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
F0
F0
F1
F1
F2
F2
F3
F3
FX: F-bit of Channel X
2. After the first octet of data is sent, the Receive High-speed Back-plane Interface should insert seven octets
(fifty-six bits) of "don't care" data into the outgoing data stream.
3. Payload data of four channels are repeated and grouped together in a bit-interleaved way. The first payload
bit of Timeslot 0 of Channel 0 is sent first, followed by the first payload bit of Timeslot 0 of Channel 1 and 2.
The first payload bit of Timeslot 0 of Channel 3 is sent last. After the first bits of Timeslot 0 of all four chan-
nels are sent, it comes the second bit of Timeslot 0 of Channel 0 and so on. The table below demonstrates
how payload bits of four channels are mapped into the 16.384Mbit/s data stream.
NINTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
10
10
11
11
12
12
13
13
TENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
20
20
21
21
22
22
23
23
XY: The Xth payload bit of Channel Y
4. The Receive High-speed Back-plane Interface also multiplexed signaling bits with payload bits and sent
them together through the 16.384Mbit/s data stream. When the Receive High-speed Back-plane Interface
is sending the fifth payload bit of a particular channel, instead of sending it twice, it inserts the signaling bit
A of that particular channel. Similarly, the sixth payload bit of a particular channels is followed by the signal-
ing bit B of that channel; the seventh payload bit is followed by the signaling bit C; the eighth payload bit is
followed by the signaling bit D.
252
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The following table illustrates how payload bits and signaling bits are multiplexed together into the 16.384Mbit/
s data stream.
THIRTEENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
50
A0
51
A1
52
A2
53
A3
FOURTEENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
60
B0
61
B1
62
B2
63
B3
FIFTEENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
70
C0
71
C1
72
C2
73
C3
SIXTEENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
80
D0
81
D1
82
D2
83
D3
XY: The Xth payload bit of Channel Y
AY: The signaling bit A of Channel Y
5. After payload bits of Timeslot 0, 1 and 2 of all four channels are sent, the Receive High-speed Back-plane
Interface should stuff another eight octets (sixty-four bits) of "don't care" data into the outgoing data
stream.
6. Following the same rules of Step 2 to 5, the Receive High-speed Back-plane Interface stuffs eight octets of
"don't care" data after sending twenty-four octets of multiplexed payload and signaling data. A 16.384Mbit/
s data stream is thus created.
The Receive Single-frame Synchronization signal of Channel 0 pulses HIGH for one clock cycle at the first bit
position (F-bit of channel 0) of the data stream with data from Channel 0-3 multiplexed together. The Receive
Single-frame Synchronization signal of Channel 4 pulses HIGH for one clock cycle at the first bit position (F-bit
of Channel 4) of the data stream with data from Channel 4-7 multiplexed together. By sampling the HIGH pulse
of the Receive Single-frame Synchronization signal, the Receive High-speed Back-plane Interface of the fram-
er can identify the beginning of a multiplexed frame and can start sending payload data of that frame.
253
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
See Figure 57 below for how to interface the local Terminal Equipment with the Receive Payload Data Output
Interface block of the framer in Bit-multiplexed 16.384Mbit/s mode.
FIGURE 57. INTERFACING XRT84L38 TO LOCAL TERMINAL EQUIPMENT USING 16.384MBIT/S DATA BUS
XRT84L38
RxSerClk_0 (16.384MHz)
Receive
RxSer_0
Payload
RxMSync_0
RxSync_0
Data Input
Interface
Chn 0-3
Terminal
Equipment
RxSerClk_4 (16.384MHz)
RxSer_4
Receive
Payload
Data Input
Interface
Chn 4-7
RxMSync_4
RxSync_4
The Input signal timing is shown in Figure 58 below when the framer is running at Bit-Multiplexed 16.384Mbit/s
mode.
FIGURE 58. TIMING DIAGRAM OF INPUT SIGNALS TO THE FRAMER WHEN RUNNING AT BIT-MULTIPLEXED
16.384MBIT/S
RxSerClk (16.384MHz)
RxSerClk (INV)
56 cycles
RxSer
F0 F0 F1 F1 F2 F2 F3 F3
10 X 11 X 12 X 13 X 20 X 21
X
30
X
40
X
50 A0 51 A1 52 A2 53 A3
RxSync(input)
5.1.3.6 T1 Receive Input Interface - HMVIP 16.384Mbit/s
When the Receive Multiplex Enable bit is set to one and the Receive Interface Mode Select [1:0] bits are set to
10, the Receive Back-plane interface of framer is running at a clock rate of 16.384MHz.
The interface consists of the following pins:
• Data input (RxSer_n)
• Receive Serial Clock Input signal (RxSerClk_n)
• Receive Single-frame Synchronization Input signal (RxSync_n)
• Receive Input Clock (RxInClk_n)
• Receive Time-slot Indication clock (RxTSClk_n)
• Receive Time Slot indicator bits (RxTSb[4:0]_n)
The Receive Back-plane Interface is pumping out data through RxSer_0 or RxSer_4 pins at 16.384Mbit/s. The
Receive High-speed Back-plane Interface multiplexes payload and signaling data of every four channels into
254
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
one data stream. Payload and signaling data of Channel 0-3 are multiplexed onto the Receive Serial Data pin
of Channel 0. Payload and signaling data of Channel 4-7 are multiplexed onto the Receive Serial Data pin of
Channel 4.
Free-running clocks of 16.384MHz are supplied to the Receive Serial Clock pin of Channel 0 and Channel 4 of
the framer. The Receive High-speed Back-plane Interface of the farmer provides data at rising edge of this Re-
ceive Serial Clock. The local Terminal Equipment then latches incoming serial data at falling edge of the clock.
The Receive High-speed Back-plane Interface maps four 1.544Mbit/s DS1 data streams into this 16.384Mbit/s
data stream as described below:
1. The F-bit of four channels are repeated and grouped together to form the first octet of the multiplexed data
stream. The F-bit of Channel 0 is sent first, followed by F-bit of Channel 1 and 2. The F-bit of Channel 3 is
sent last. The table below shows bit-pattern of the first octet.
FIRST OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
F0
F0
F1
F1
F2
F2
F3
F3
FX: F-bit of Channel X
2. After the first octet of data is sent, the Receive High-speed Back-plane Interface insert seven octets (fifty-
six bits) of "don't care" data into the outgoing data stream.
3. Payload data of four channels are repeated and grouped together in a byte-interleaved way. The first pay-
load bit of Timeslot 0 of Channel 0 is sent first, followed by the second payload bit of Timeslot 0 of Channel
0 and so on. After all the bits of Timeslot 0 of Channel 0 is sent repeatedly, the Terminal Equipment will
start sending the payload bits of Timeslot 0 of Channel 1 and 2. The payload bits of Timeslot 0 of Channel
3 are sent the last. After the payload bits of Timeslot 0 of all four channels are sent, it comes the payload
bits of Timeslot 1 of Channel 0 and so on. The table below demonstrates how payload bits of four channels
are mapped into the 16.384Mbit/s data stream.
NINTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
10
10
20
20
30
30
40
40
ELEVENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
11
11
21
21
31
31
41
41
THIRTEENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
12
12
22
22
32
32
42
42
255
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
FIFTEENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
13
13
23
23
33
33
43
43
XY: The Xth payload bit of Channel Y
4. The Receive High-speed Back-plane Interface also multiplexed signaling bits with payload bits and sent
them together through the 16.384Mbit/s data stream. When the Receive High-speed Back-plane Interface
is sending the fifth payload bit of a particular channel, instead of sending it twice, it inserts the signaling bit
A of that particular channel. Similarly, the sixth payload bit of a particular channels is followed by the signal-
ing bit B of that channel; the seventh payload bit is followed by the signaling bit C; the eighth payload bit is
followed by the signaling bit D.
The following table illustrates how payload bits and signaling bits are multiplexed together into the 16.384Mbit/
s data stream.
TENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
50
A0
60
B0
70
C0
80
D0
TWELFTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
51
A1
61
B1
71
C1
81
D1
FOURTEENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
52
A2
62
B2
72
C2
82
D2
SIXTEENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
53
A3
63
B3
73
C3
83
D3
XY: The Xth payload bit of Channel Y
AY: The signaling bit A of Channel Y
256
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
5. After payload bits of Timeslot 0, 1 and 2 of all four channels are sent, the Receive High-speed Back-plane
Interface should stuff another eight octets (sixty-four bits) of "don't care" data into the outgoing data
stream.
6. Following the same rules of Step 2 to 5, Receive High-speed Back-plane Interface stuffs eight octets of
"don't care" data after sending twenty-four octets of multiplexed payload and signaling data. A 16.384Mbit/
s data stream is thus created.
The Receive Single-frame Synchronization signal should pulse HIGH for four clock cycles (the last two bit posi-
tions of the previous multiplexed frame and the first two bits of the next multiplexed frame) indicating frame
boundary of the multiplexed data stream. The Receive Single-frame Synchronization signal of Channel 0 puls-
es HIGH to identify the start of multiplexed data stream of Channel 0-3. The Receive Single-frame Synchroni-
zation signal of Channel 0 pulses HIGH to identify the start of multiplexed data stream of Channel 0-3. By sam-
pling the HIGH pulse of the Receive Single-frame Synchronization signal, the Receive High-speed Back-plane
Interface of the framer can identify the beginning of a multiplexed frame and can start sending payload data of
that frame.
See Figure 59 below for how to interface the local Terminal Equipment with the Receive Payload Data Output
Interface block of the framer in HMVIP 16.384Mbit/s mode.
FIGURE 59. INTERFACING XRT84L38 TO LOCAL TERMINAL EQUIPMENT USING 16.384MBIT/S DATA BUS
XRT84L38
RxSerClk_0 (16.384MHz)
Receive
RxSer_0
Payload
RxMSync_0
RxSync_0
Data Input
Interface
Chn 0-3
Terminal
Equipment
RxSerClk_4 (16.384MHz)
RxSer_4
Receive
Payload
Data Input
Interface
Chn 4-7
RxMSync_4
RxSync_4
The Input signal timing is shown in Figure 60 below when the framer is running at HMVIP 16.384Mbit/s mode.
FIGURE 60. TIMING DIAGRAM OF INPUT SIGNALS TO THE FRAMER WHEN RUNNING AT HMVIP 16.384MBIT/S
RxSerClk (16.384MHz)
RxSerClk (INV)
56 cycles
56 cycles
RxSer
RxSig
73 73 83 83 F0 F0 F1 F1 F2 F2 F3 F3
Start of Frame
10 10 20 20 30 30 40 40 50 A0 60 B0
12 12
52 52
53 53 63 63 73 73 83 83
A3A3B3B3C3C3D3D3
Xy : X is the bit number and y is the channel number
C3C3D3D3 1 1 1 1 1 1 1 1
0 0 0 0 0 0 A0A0B0B0C0C0
0 0
A2A2
RxSync(input)
HMVIP, negative sync
RxSync(input)
HMVIP, positive sync
257
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
5.1.3.7 T1 Receive Input Interface - H.100 16.384Mbit/s
When the Receive Multiplex Enable bit is set to one and the Receive Interface Mode Select [1:0] bits are set to
11, the Receive Back-plane interface of framer is running at H.100 16.384Mbit/s mode.
The HMVIP mode and the H.100 mode are essential the same except for the HIGH pulse position of the Re-
ceive Single-frame Synchronization Signal.
The interface consists of the following pins:
• Data input (RxSer_n)
• Receive Serial Clock Input signal (RxSerClk_n)
• Receive Single-frame Synchronization Input signal (RxSync_n)
• Receive Input Clock (RxInClk_n)
• Receive Time-slot Indication clock (RxTSClk_n)
• Receive Time Slot indicator bits (RxTSb[4:0]_n)
The Receive Back-plane Interface is pumping out data through RxSer_0 or RxSer_4 pins at 16.384Mbit/s. The
Receive High-speed Back-plane Interface multiplexes payload and signaling data of every four channels into
one data stream. Payload and signaling data of Channel 0-3 are multiplexed onto the Receive Serial Data pin
of Channel 0. Payload and signaling data of Channel 4-7 are multiplexed onto the Receive Serial Data pin of
Channel 4.
Free-running clocks of 16.384MHz are supplied to the Receive Serial Clock pin of Channel 0 and Channel 4 of
the framer. The Receive High-speed Back-plane Interface of the farmer provides data at rising edge of this Re-
ceive Serial Clock. The local Terminal Equipment then latches incoming serial data at falling edge of the clock.
The Receive High-speed Back-plane Interface maps four 1.544Mbit/s DS1 data streams into this 16.384Mbit/s
data stream as described below:
1. The F-bit of four channels are repeated and grouped together to form the first octet of the multiplexed data
stream. The F-bit of Channel 0 is sent first, followed by F-bit of Channel 1 and 2. The F-bit of Channel 3 is
sent last. The table below shows bit-pattern of the first octet.
FIRST OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
F0
F0
F1
F1
F2
F2
F3
F3
FX: F-bit of Channel X
2. After the first octet of data is sent, the Receive High-speed Back-plane Interface insert seven octets (fifty-
six bits) of "don't care" data into the outgoing data stream.
3. Payload data of four channels are repeated and grouped together in a byte-interleaved way. The first pay-
load bit of Timeslot 0 of Channel 0 is sent first, followed by the second payload bit of Timeslot 0 of Channel
0 and so on. After all the bits of Timeslot 0 of Channel 0 is sent repeatedly, the Receive High-speed Back-
plane Interface will start sending the payload bits of Timeslot 0 of Channel 1 and 2. The payload bits of
Timeslot 0 of Channel 3 are sent the last. After the payload bits of Timeslot 0 of all four channels are sent,
258
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
it comes the payload bits of Timeslot 1 of Channel 0 and so on. The table below demonstrates how payload
bits of four channels are mapped into the 16.384Mbit/s data stream.
NINTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
10
10
20
20
30
30
40
40
ELEVENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
11
11
21
21
31
31
41
41
THIRTEENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
12
12
22
22
32
32
42
42
FIFTEENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
13
13
23
23
33
33
43
43
XY: The Xth payload bit of Channel Y
4. The Receive High-speed Back-plane Interface also multiplexed signaling bits with payload bits and sent
them together through the 16.384Mbit/s data stream. When the Receive High-speed Back-plane Interface
is sending the fifth payload bit of a particular channel, instead of sending it twice, it inserts the signaling bit
A of that particular channel. Similarly, the sixth payload bit of a particular channels is followed by the signal-
ing bit B of that channel; the seventh payload bit is followed by the signaling bit C; the eighth payload bit is
followed by the signaling bit D.
The following table illustrates how payload bits and signaling bits are multiplexed together into the 16.384Mbit/
s data stream.
TENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
50
A0
60
B0
70
C0
80
D0
259
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
TWELFTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
51
A1
61
B1
71
C1
81
D1
FOURTEENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
52
A2
62
B2
72
C2
82
D2
SIXTEENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
53
A3
63
B3
73
C3
83
D3
XY: The Xth payload bit of Channel Y
AY: The signaling bit A of Channel Y
5. After payload bits of Timeslot 0, 1 and 2 of all four channels are sent, the Terminal Equipment should stuff
another eight octets (sixty-four bits) of "don't care" data into the outgoing data stream.
6. Following the same rules of Step 2 to 5, the Receive High-speed Back-plane Interface stuffs eight octets of
"don't care" data after sending twenty-four octets of multiplexed payload and signaling data. A 16.384Mbit/
s data stream is thus created.
The Receive Single-frame Synchronization signal should pulse HIGH for two clock cycles (the last bit position
of the previous multiplexed frame and the first bit position of the next multiplexed frame) indicating frame
boundary of the multiplexed data stream. The Receive Single-frame Synchronization signal of Channel 0 puls-
es HIGH to identify the start of multiplexed data stream of Channel 0-3. The Receive Single-frame Synchroni-
zation signal of Channel 0 pulses HIGH to identify the start of multiplexed data stream of Channel 0-3. By sam-
pling the HIGH pulse of the Receive Single-frame Synchronization signal, the Receive High-speed Back-plane
Interface of the framer can identify the beginning of a multiplexed frame and can start sending payload data of
that frame.
260
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
See Figure 61 below for how to interface the local Terminal Equipment with the Receive Payload Data Output
Interface block of the framer in H.100 16.384Mbit/s mode.
FIGURE 61. INTERFACING XRT84L38 TO LOCAL TERMINAL EQUIPMENT USING H.100 16.384MBIT/S DATA BUS
XRT84L38
RxSerClk_0 (16.384MHz)
Receive
RxSer_0
Payload
RxMSync_0
RxSync_0
Data Input
Interface
Chn 0-3
Terminal
Equipment
RxSerClk_4 (16.384MHz)
RxSer_4
Receive
Payload
Data Input
Interface
Chn 4-7
RxMSync_4
RxSync_4
The Input signal timing is shown in Figure 62 below when the framer is running at H.100 16.384Mbit/s mode.
FIGURE 62. TIMING DIAGRAM OF INPUT SIGNALS TO THE FRAMER WHEN RUNNING AT H.100 16.384MBIT/S
RxSerClk (16.384MHz)
RxSerClk (INV)
56 cycles
56 cycles
RxSer
RxSig
73 73 83 83 F0 F0 F1 F1 F2 F2 F3 F3
Start of Frame
10 10 20 20 30 30 40 40 50 A0 60 B0
12 12
52 52
53 53 63 63 73 73 83 83
A3A3B3B3C3C3D3D3
Xy : X is the bit number and y is the channel number
C3C3D3D3 1 1 1 1 1 1 1 1
0 0 0 0 0 0 A0A0B0B0C0C0
0 0
A2A2
RxSync(input)
H.100, negative sync
RxSync(input)
H.100, positive sync
Delayer H.100
RxSync(input)
H.100, negative sync
RxSync(input)
H.100, positive sync
261
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
6.0 THE E1 TRANSMIT SECTION
6.1 THE E1 TRANSMIT PAYLOAD DATA INPUT INTERFACE BLOCK
6.1.1 Description of the Transmit Payload Data Input Interface Block
Each of the eight framers within the XRT84L38 device includes a Transmit Payload Data Input Interface block.
The function of this block is to provide an interface to the local Terminal Equipment (for example, a Central Of-
fice or switching equipment) that has data to send to a "Far End" terminal over a DS1 or E1 transport medium.
The Payload Data Input Interface module (also known as the Back-plane Interface module) supports payload
data to be taken from or presented to the system. In DS1 mode, supported data rates are 1.544Mbit/s, MVIP
2.048Mbit/s, 4.096Mbit/s, 8.192Mbit/s, multiplexed 12.352Mbit/s, multiplexed 16.384Mbit/s, HMVIP
16.384Mbit/s or H.100 16.384Mbit/s. In E1 mode, supported data rates are XRT84V24 compatible 2.048Mbit/s,
MVIP 2.048Mbit/s, 4.096Mbit/s, 8.192Mbit/s, multiplexed 16.384Mbit/s, HMVIP 16.384Mbit/s or H.100
16.384Mbit/s.
The Transmit Payload Data Input Interface block supplies or accepts the following signals to the local Terminal
Equipment circuitry:
• Transmit Serial Data Input (TxSer_n)
• Transmit Serial Clock (TxSerClk_n)
• Transmit Single-frame Synchronization Signal (TxSync_n)
• Transmit Multi-frame Synchronization Signal (TxMSync_n)
• Transmit Time-slot Indicator Clock (TxTSClk_n)
• Transmit Time-slot Indication Bits (TxTSb[4:0]_n)
The Transmit Serial Data is an input pin carrying payload, signaling and sometimes Data Link data supplied by
the local Terminal Equipment to the XRT84L38 device.
The Transmit Serial Clock is an input or output signal used by the Transmit Payload Data Input Interface block
to latch in incoming serial data from the local Terminal Equipment. The Transmit Clock Inversion bit of the
Transmit Interface Control Register (TICR) determines at which edge of the Transmit Serial Clock would data
transition on the Transmit Serial Data pin occur.
The table below shows configurations of the Transmit Clock Inversion bit of the Transmit Interface Control Reg-
ister (TICR).
TRANSMIT INTERFACE CONTROL REGISTER (TICR) (INDIRECT ADDRESS = 0XN0H, 0X20H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3
Transmit Clock
Inversion
R/W
0 - Serial data transition happens on rising edge of the Transmit Serial Clock.
1 - Serial data transition happens on falling edge of the Transmit Serial Clock.
Throughout the discussion of this datasheet, we assume that serial data transition happens on rising edge of
the Transmit Serial Clock unless stated otherwise.
The Transmit Single-frame Synchronization signal is either input or output. When configured as input, it indi-
cates the beginning of an E1 frame. When configured as output, it indicates the end of an E1 frame.
The Transmit Multi-frame Synchronization signal is either input or output. When configured as input, it indicates
the beginning of an E1 multi-frame. When configure as output, it indicates the end of an E1 multi-frame.
The Transmit Input Clock signal is multiplexed into the Transmit Multi-frame Synchronization pin (TxMSync_n)
of the XRT84L38. When the framer is running at High-speed Back-plane Interface mode, the Transmit Input
Clock functions as the timing source for the High-speed Back-plane Interface.
By connecting these signals with the local Terminal Equipment, the Transmit Payload Data Input Interface ac-
cepts payload data from the Terminal Equipment and routes it to the Transmit Framer module inside the device.
6.1.2 Brief Discussion of the Transmit Payload Data Input Interface Block Operating at XRT84V24
Compatible 2.048Mbit/s mode
262
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
If the framer is operating in normal 2.048Mbit/s Back-plane interface mode for E1, timing source of the transmit
section can be one of the three clocks:
• Transmit Serial Input Clock
• OSCCLK Driven Divided Clock
• Recovered Receive Line Clock
The Transmit Timing Source Select [1:0] bits of the Clock Select Register (CSR) determine which clock is used
as the timing source. The following table shows configurations of the Transmit Timing Source Select [1:0] bits
of the Clock Select Register.
CLOCK SELECT REGISTER (CSR) (INDIRECT ADDRESS = 0XN0H, 0X00H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1-0
Transmit Timing
Source Select
R/W
Transmit Timing Source Select:
These two READ/WRITE bit-fields permit the user to select the timing source of
Transmit section of the framer.
When the Transmit Back-plane interface is operating at a clock rate of 2.048MHz
for E1, these two READ/WRITE bit-fields also determine the direction of Single
Frame Synchronization Pulse (TxSync), Multi-frame Synchronization Pulse
(TxMSync) and Transmit Serial Clock Input (TxSerClk). When the framer is oper-
ating at other Back-plane mode, the Single Frame Synchronization Pulse
(TxSync), Multi-frame Synchronization Pulse (TxMSync) and Transmit Serial
Clock Input (TxSerClk) are all inputs.
00 - The Recovered Receive Line Clock is the timing source of Transmit section
of the framer. When operating at the non-multiplexed 2.048MHz Back-plane
Interface mode, the Single Frame Synchronization Pulse (TxSync), Multi-frame
Synchronization Pulse (TxMSync) and Transmit Serial Clock Input (TxSerClk)
are all outputs. Upon losing of the Recovered Receiver Line Clock, the OSCCLK
Driven Divided clock is automatically chosen to be the timing source of the
Transmit section of the framer.
01 - The Transmit Serial Clock is the timing source of Transmit section of the
framer. When operating at the non-multiplexed 2.048MHz Back-plane Interface
mode, the Single Frame Synchronization Pulse (TxSync), Multi-frame Synchro-
nization Pulse (TxMSync) and Transmit Serial Clock Input (TxSerClk) are all
inputs.
10 - The OSCCLK Driven Divided clock is the timing source of Transmit section
of the framer. When operating at the non-multiplexed 2.048MHz Back-plane
Interface mode, the Single Frame Synchronization Pulse (TxSync), Multi-frame
Synchronization Pulse (TxMSync) and Transmit Serial Clock Input (TxSerClk)
are all outputs. Upon losing of the Recovered Receiver Line Clock, the OSCCLK
Driven Divided clock is automatically chosen to be the timing source of the
Transmit section of the framer.
11 - The Recovered Receive Line Clock is the timing source of Transmit section
of the framer. When operating at the non-multiplexed 2.048MHz Back-plane
Interface mode, the Single Frame Synchronization Pulse (TxSync), Multi-frame
Synchronization Pulse (TxMSync) and Transmit Serial Clock Input (TxSerClk)
are all outputs. Upon losing of the Recovered Receiver Line Clock, the OSCCLK
Driven Divided clock is automatically chosen to be the timing source of the
Transmit section of the framer.
The Transmit Serial Clock (TxSerClk_n), Transmit Single-frame Synchronization Signal (TxSync_n) and Trans-
mit Multi-frame Synchronization Signal (TxMSync_n) can be either inputs or outputs depend on the timing
source of the Transmit section of the framer.
With the OSCCLK Driven Divided Clock or the Recovered Receive Line Clock being the timing source of the
transmit section, the Transmit Serial Clock (TxSerClk_n), Transmit Single-frame Synchronization Signal
(TxSync_n) and Transmit Multi-frame Synchronization Signal (TxMSync_n) are all outputs.
263
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
With the timing source of the transmit section being the Transmit Serial Input Clock, the Transmit Serial Clock
(TxSerClk_n), Transmit Single-frame Synchronization Signal (TxSync_n) and Transmit Multi-frame Synchroni-
zation Signal (TxMSync_n) are all inputs.
The following table illustrates the input and output nature of these signals for different Transmit timing sources.
TRANSMIT TIMING SOURCE
Terminal Equipment Driven TxSerClk
OSCCLK Driven Divided Clock
Recovered Receive Line Clock
TXSERCLK_N
Input
TXSYNC_N
Input
TXMSYNC_N
Input
Output
Output
Output
Output
Output
Output
The Transmit Time-slot Indication Bits (TxTSb[4:0]_n) are multiplexed I/O pins. The functionality of these pins
is governed by the value of Transmit Fractional E1 Input Enable bit of the Transmit Interface Control Register
(TICR).
The following table illustrates the configurations of the Transmit Fractional E1 Input Enable bit.
TRANSMIT INTERFACE CONTROL REGISTER (TICR) (INDIRECT ADDRESS = 0XN0H, 0X20H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
4
Transmit
Fractional E1
Input Enable
R/W
0 - The Transmit Time-slot Indication bits (TxTSb[4:0] are outputting five-bit
binary values of Time-slot number (0-31) being accepted and processed by the
Transmit Payload Data Input Interface block of the framer.
The Transmit Time-slot Indicator Clock signal (TxTSClk_n) is a 256KHz clock
that pulses HIGH for one E1 bit period whenever the Transmit Payload Data
Input Interface block is accepting the LSB of each of the twenty-four time slots.
1 - The TxTSb[0]_n bit becomes the Transmit Fractional E1 Input signal
(TxFrTD_n) which carries Fractional E1 payload data into the framer.
The TxTSb[1]_n bit becomes the Transmit Signaling Data Input signal (TxSig_n)
which is used to insert robbed-bit signaling data into the outbound E1 frame.
The TxTSb[2]_n bit serially outputs all five-bit binary values of the Time Slot
number (0-31) being accepted and processed by the Transmit Payload Data
Input Interface block of the framer.
The TxTSb[3]_n bit becomes the Transmit Overhead Synchronization Pulse
(TxOHSync_n) which is used to output an Overhead Synchronization Pulse that
indicates the first bit of each E1multi-frame.
The TxTSClk_n will output gaped fractional E1 clock that can be used by Termi-
nal Equipment to clock out Fractional E1 payload data at rising edge of the clock.
Or,
The TxTSClk_n pin will be a clock enable signal to Transmit Fractional E1 Input
signal (TxFrTD_n) when the un-gaped Transmit Serail Input Clock (TxSerClk_n)
is used to clock in Fractional E1 Payload Data into the framer.
When configured to operate in normal condition (that is, when the Transmit Fractional E1 Input Enable bit is
equal to zero), these bits reflect the five-bit binary value of the Time Slot number (0-31) being accepted and
processed by the Transmit Payload Data Input Interface block of the framer. TxTSb[4] represents the MSB of
the binary value and TxTSb[0] represents the LSB.
When the Transmit Fractional E1 Input Enable bit is equal to one, the TxTSb[0]_n bit becomes the Transmit
Fractional E1 Input signal (TxFrTD_n). This input pin carries Fractional E1 Input data to be inserted into the
outbound E1 data stream. The Fraction E1 Input Interface allows certain time-slots of outbound E1 data stream
to have a different source other than the local Terminal Equipment. Function of the Fractional E1 Input signal
will be discussed in details in later sections.
When the Transmit Fractional E1 Input Enable bit is equal to one, the TxTSb[1]_n bit becomes the Transmit
Signaling Data Input signal (TxSig_n). These input pins can be used to insert robbed-bit signaling data into the
264
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
outbound E1 frame. Function of the Transmit Signaling Data Input signal will be discussed in details in later
sections.
When the Transmit Fractional E1 Input Enable bit is equal to one, the TxTSb[2]_n bit serially outputs all five-bit
binary values of the Time Slot number (0-31) being accepted and processed by the Transmit Payload Data In-
put Interface block of the framer. MSB of the binary value is presented first and the LSB is presented last.
When the Transmit Fractional E1 Input Enable bit is equal to one, the TxTSb[3]_n bit becomes the Transmit
Overhead Synchronization Pulse (TxOHSync_n). These pins can be used to output an Overhead Synchroniza-
tion Pulse that indicates the first bit of each E1multi-frame. Function of the Transmit Overhead Synchronization
Output signal will be discussed in details in later sections.
The TxTSb[4]_n bit is not multiplexed.
The table below shows functionality of the TxTSb[3:0] bits when the Transmit Fractional E1 Input bit is set to
different values.
TRANSMIT FRACTIONAL E1 INPUT BIT = 0
TRANSMIT FRACTIONAL E1 INPUT BIT = 1
TxTSb[0]
TxTSb[1]
TxTSb[2]
TxTSb[3]
Output
Output
Output
Output
TxFrTD
TxSig
Input
Input
TxTS
Output
Output
TxOHSync
The Transmit Time-slot Indicator Clock signal (TxTSClk_n) is a multi-function output pin. When configured to
operate in normal condition (that is, when the Transmit Fractional E1 Input Enable bit is equal to zero), the
TxTSClk_n is a 256KHz clock that pulses HIGH for one E1 bit period whenever the Transmit Payload Data In-
put Interface block is accepting the LSB of each of the twenty-four time slots. The local Terminal Equipment
should use this clock signal to sample the TxTSb[0] through TxTSb[4] bits and identify the time-slot being pro-
cessed via the Transmit Section of the framer.
When the Transmit Fractional E1 Input Enable bit is equal to one, the TxTSClk_n will output gaped fractional
E1 clock at time-slots where Fractional E1 Input data is present. This clock can be used by Terminal Equipment
to clock out Fractional E1 payload data at rising edge of the clock. The framer will then input Fractional E1 pay-
load data using falling edge of the clock. Otherwise, this pin can be configured as a clock enable signal to
Transmit Fractional E1 Input signal (TxFrTD_n) if the framer is set accordingly. In this way, Fractional E1 pay-
load data is clocked into the framer using un-gaped Transmit Serail Input Clock (TxSerClk_n). A detailed dis-
cussion of the Fractional E1 Payload Data Input Interface can be found in later sections.
Both the Transmit Time-slot Indicator Clock (TxTSClk_n) and the Transmit Time-slot Indication Bits (TxTS-
bb[4:0]_n) are output signals in normal 2.048Mbit/s Back-plane mode regardless of the timing source of the
Transmit Section of framer.
A detailed discussion of how to connect the Transmit Payload Data Input Interface block to the local Terminal
Equipment using different timing sources can be found in the later sections.
6.1.2.1 Connect the Transmit Payload Data Input Interface block to the Local Terminal Equipment if
Transmit Timing Source = TxSerClk_n
By setting the Transmit Timing Source [1:0] bits of the Clock Select Register to 01, the TxSerClk_n input signal
is configured to be the timing source for the Transmit section of the framer. The Terminal Equipment should
supply an external free-running clock with frequency of 2.048MHz to the TxSerClk_n input pin. The Transmit
Single-frame Synchronization signal and the Transmit Multi-frame Synchronization signal are inputs to the
framer.
The Transmit Single-frame Synchronization signal should pulse HIGH for one E1 bit period (488ns) at the first
bit position of each E1 frame. By sampling the HIGH pulse on the Transmit Single-frame Synchronization sig-
nal, the framer can position the beginning of an E1 frame.
265
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The Transmit Multi-frame Synchronization signal should pulse HIGH for one E1 bit period (488ns) at the first bit
position of the first frame of an E1 multi-frame. By sampling the HIGH pulse on the Transmit Multi-frame Syn-
chronization signal, the framer can position the beginning of an E1 super-frame.
It is the responsibility of the Terminal Equipment to provide serial input data through the TxSer_n pin aligned
with the Transmit Single-frame Synchronization signal and the Transmit Multi-frame Synchronization signal.
See Figure 63 below for how to connect the Transmit Payload Data Input Interface block to the local Terminal
Equipment with the Transmit Serial clock being the timing source of transmit section.
FIGURE 63. INTERFACING XRT84L38 TO LOCAL TERMINAL EQUIPMENT WITH TXSERCLK_N AS TRANSMIT TIMING
SOURCE
XRT84L38
TxSerClk_0
TxSer_0
Transmit
TxMSync_0
TxSync_0
Payload
Data Input
Interface
Chn 0
TxTSClk_0
TxTSb[4:0]_0
Terminal
Equipment
TxSerClk_7
TxSer_7
Transmit
Payload
Data Input
Interface
Chn 7
TxMSync_7
TxSync_7
TxTSClk_7
TxTSb[4:0]_7
266
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The following Figure 64 shows waveforms of the signals (TxSerClk_n, TxSer_n, TxSync_n, TxTSClk_n and
TxTSb[4:0]_n) that connecting the Transmit Payload Data Input Interface block to the local Terminal Equipment
with the Transmit Serial clock being the timing source of transmit section.
FIGURE 64. WAVEFORMS OF THE SIGNALS THAT CONNECT THE TRANSMIT PAYLOAD DATA INPUT INTERFACE BLOCK
TO THE LOCAL TERMINAL EQUIPMENT WITH THE TRANSMIT SERIAL CLOCK BEING THE TIMING SOURCE OF THE TRANS-
MIT SECTION
Timeslot 0
Timeslot 5
Timeslot 6
Timeslot 23
TxSerClk
TxSerClk (INV)
TxSer
Input Data
Input Data
Input Data
Input Data
F
F
TxSync(input)
TxSync(output)
TxChClk
TxChn[4:0]
Timeslot #0
A B C D
Timeslot #5
Timeslot #6
Timeslot #23
TxChn[0]/TxSig
TxTSClk
A B C D
A B C D
A B C D
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
TxTSb[4:0]
TxChn[1]/TxFrTD
1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8
6.1.2.2 Connect the Transmit Payload Data Input Interface block to the Local Terminal Equipment if
the Transmit Timing Source = OSCCLK
By setting the Transmit Timing Source [1:0] bits of the Clock Select Register (CSR) to 10, the OSCCLK Driven
Divided clock is configured to be the timing source for the Transmit section of the framer. A free-running clock
should apply to the OSCCLK input pin with frequencies of 16.384MHz, 32.768MHz and 65.536MHz depending
on the setting of OSCCLK Frequency Select [1:0] bits of the Clock Select Register (CSR).
The free-running OSCCLK is divided inside the XRT84L38 and routed to all eight framers. This OSCCLK Driv-
en Divided Clock has to be 16.384MHz in frequency. When these bits are set to 00, the framer will internally di-
vide the incoming OSCCLK by one. Therefore, the external oscillator clock applied to the OSCCLK pin should
be 16.384MHz. When these bits are set to 01, the framer will internally divide the incoming OSCCLK by two.
Therefore, the external oscillator clock applied to the OSCCLK pin should be 32.768MHz. When these bits are
set to 10, the framer will internally divide the incoming OSCCLK by four. Therefore, the external oscillator clock
applied to the OSCCLK pin should be 65.536MHz.
267
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The following table shows configurations of the OSCCLK Frequency Select [1:0] bits of the Clock Select Regis-
ter.
CLOCK SELECT REGISTER (CSR) (INDIRECT ADDRESS = 0XN0H, 0X00H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3-2
OSCCLK
Frequency
Select
R/W
These two READ/WRITE bit-fields permit the user to select internal clock divid-
ing logic of the framer depending on the frequency of incoming oscillator clock
(OSCCLK). The frequency of internal clock used by the framer should be
16.384MHz.
00 - The framer will internally divide the incoming OSCCLK by one. Therefore,
the external oscillator clock applied to the OSCCLK pin should be 16.384MHz.
01 - The framer will internally divide the incoming OSCCLK by two. Therefore,
the external oscillator clock applied to the OSCCLK pin should be 32.768MHz.
10 - The framer will internally divide the incoming OSCCLK by four. Therefore,
the external oscillator clock applied to the OSCCLK pin should be 65.536MHz.
The Transmit Serial clock signal pin (TxSerClk_n) is output from the framer. The framer outputs a 2.048MHz
clock through this pin to the local Terminal Equipment. The Transmit Single-frame Synchronization signal and
the Transmit Multi-frame Synchronization signal are also automatically configured to be output signals.
The Transmit Single-frame Synchronization signal should pulse HIGH for one E1 bit period (488ns) at the last
bit position of each E1 frame. By triggering on the HIGH pulse on the Transmit Single-frame Synchronization
signal, the local Terminal Equipment can identify the end of an E1 frame and should start inserting payload da-
ta of the next E1 frame to the framer.
The Transmit Multi-frame Synchronization signal should pulse HIGH for one E1 bit period (488ns) at the last bit
position of the last frame of an E1 multi-frame. By triggering on the HIGH pulse on the Transmit Multi-frame
Synchronization signal, the local Terminal Equipment can identify the end of an E1 super-frame and should
start inserting payload data of the next E1 multi-frame into the framer.
268
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
See Figure 65 for how to connect the Transmit Payload Data Input Interface block to the local Terminal Equip-
ment with the OSCCLK Driven Divided clock as the timing source of transmit section.
FIGURE 65. INTERFACING XRT84L38 TO LOCAL TERMINAL EQUIPMENT WITH OSCCLK DRIVEN DIVIDED CLOCK AS
TRANSMIT TIMING SOURCE
XRT84L38
TxSerClk_0
TxSer_0
Transmit
TxMSync_0
TxSync_0
Payload
Data Input
Interface
Chn 0
TxTSClk_0
TxTSb[4:0]_0
Terminal
Equipment
TxSerClk_7
TxSer_7
Transmit
Payload
Data Input
Interface
Chn 7
TxMSync_7
TxSync_7
TxTSClk_7
TxTSb[4:0]_7
OSCCLK
269
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The following Figure 66 shows waveforms of the signals (TxSerClk_n, TxSer_n, TxSync_n, TxTSClk_n and
TxTSb[4:0]_n) that connecting the Transmit Payload Data Input Interface block to the local Terminal Equipment
with the OSCCLK Driven Divided clock as the timing source of transmit section.
FIGURE 66. WAVERFORMS OF THE SIGNALS CONNECTING THE TRANSMIT PAYLOAD DATA INPUT INTERFACE BLOCK
TO THE LOCAL TERMINAL EQUIPMENT WITH THE OSCCLK DRIVEN DIVIDED CLOCK AS THE TIMING SOURCE OF THE
TRANSMIT SECTION
Timeslot 0
Timeslot 5
Timeslot 6
Timeslot 23
TxSerClk
TxSerClk (INV)
TxSer
Input Data
Input Data
Input Data
Input Data
F
F
TxSync(output)
TxChClk
TxChn[4:0]
Timeslot #0
A B C D
Timeslot #5
Timeslot #6
Timeslot #23
TxChn[0]/TxSig
TxChn[0]/TxSig
A B C D
A B C D
A B C D
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
TxChClk
TxChn[1]/TxFrTD
1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8
6.1.2.3 Connect the Transmit Payload Data Input Interface block to the Local Terminal Equipment
for Loop-timing applications
If the Transmit Timing Source [1:0] bits of the Clock Select Register are set to 00 or 11, the Recovered Receive
Line Clock is configured to be the timing source for the Transmit section of the framer. This is also known as the
Loop-timing mode.
If the Clock Loss Detection Enable bit of the Clock Select Register is set to one, and if the Recovered Receive
Line Clock from the LIU is lost, the framer will automatically begin to use the OSCCLK Driven Divided clock as
transmit timing source until the LIU is able to regain clock recovery.
270
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The following table shows configuration of the Clock Loss Detection Enable bit of the Clock Select Register
(CSR).
CLOCK SELECT REGISTER (CSR) (INDIRECT ADDRESS = 0XN0H, 0X00H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
4
Clock Loss
Detection
Enable
R/W
This READ/WRITE bit-field permits the user to enable the Clock Loss Detection
logic for the framer when the Recovered Receive Line Clock is used as transmit
timing source of the framer.
0 - The framer disables the Clock Loss Detection logic.
1 - The framer enables the Clock Loss Detection logic. If the Recovered Receive
Line Clock is used as transmit timing source of the framer, and if clock recovered
from the LIU is lost, the framer can detect loss of the Recovered Receive Line
Clock. Upon detecting of this occurrence, the framer will automatically begin to
use the OSCCLK Driven Divided clock as transmit timing source until the LIU is
able to regain clock recovery.
NOTE: This bit-field is ignored if the TxSerClk or the OSCCLK Driven Divided
Clock is chosen to be the timing source of Transmit Section of the framer.
The Transmit Serial Clock signal pin (TxSerClk_n) is output from the framer. The XRT84L38 device routes the
Recovered Receive Line Clock internally across the framer and output through the Transmit Serial Clock signal
pin to the local Terminal Equipment. The Transmit Single-frame Synchronization signal and the Transmit Multi-
frame Synchronization signal are automatically configured to be output signals.
The Transmit Single-frame Synchronization signal should pulse HIGH for one E1 bit period (488ns) at the last
bit position of each E1 frame. By triggering on the HIGH pulse on the Transmit Single-frame Synchronization
signal, the local Terminal Equipment can identify the end of an E1 frame and should start inserting payload da-
ta of the next E1 frame to the framer.
The Transmit Multi-frame Synchronization signal should pulse HIGH for one E1 bit period (488ns) at the last bit
position of the last frame of an E1 multi-frame. By triggering on the HIGH pulse on the Transmit Multi-frame
Synchronization signal, the local Terminal Equipment can identify the end of an E1 super-frame and should
start inserting payload data of the next E1 multi-frame into the framer.
271
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
See Figure 67 for how to connect the Transmit Payload Data Input Interface block to the local Terminal Equip-
ment with the Recovered Receive Line Clock being the timing source of transmit section.
FIGURE 67. INTERFACING XRT84L38 TO LOCAL TERMINAL EQUIPMENT WITH RECOVERED RECEIVE LINE CLOCK AS
TRANSMIT TIMING SOURCE
XRT84L38
TxSerClk_0
RxLineClk_0
TxSer_0
Transmit
Payload
Data Input
Interface
Chn 0
TxMSync_0
TxSync_0
TxTSClk_0
TxTSb[4:0]_0
Terminal
Equipment
TxSerClk_7
TxSer_7
Transmit
Payload
Data Input
Interface
Chn 7
TxMSync_7
TxSync_7
TxTSClk_7
TxTSb[4:0]_7
RxLineClk_7
272
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The following Figure 68 shows waveforms of the signals (TxSerClk_n, TxSer_n, TxSync_n, TxTSClk_n and
TxTSb[4:0]_n) that connecting the Transmit Payload Data Input Interface block to the local Terminal Equipment
with the Recovered Receive Line Clock being the timing source of transmit section.
FIGURE 68. WAVERFORMS OF THE SIGNALS CONNECTING THE TRANSMIT PAYLOAD DATA INPUT INTERFACE BLOCK
TO THE LOCAL TERMINAL EQUIPMENT WITH THE RECOVERED RECEIVE LINE CLOCK BEING THE TIMING SOURCE OF
TRANSMIT SECTION
Timeslot 0
Timeslot 5
Timeslot 6
Timeslot 23
TxSerClk
TxSerClk (INV)
TxSer
Input Data
Input Data
Input Data
Input Data
F
F
TxSync(output)
TxChClk
TxChn[4:0]
Timeslot #0
A B C D
Timeslot #5
Timeslot #6
Timeslot #23
TxChn[0]/TxSig
TxChn[0]/TxSig
A B C D
A B C D
A B C D
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
TxChClk
TxChn[1]/TxFrTD
1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8
6.1.3 Brief Discussion of the Transmit High-Speed Back-Plane Interface
The High-speed Back-plane Interface supports payload data to be taken from or presented to the Terminal
Equipment at different data rates. In E1 mode, supported High-speed data rates are MVIP 2.048Mbit/s,
4.096Mbit/s, 8.192Mbit/s, multiplexed 16.384Mbit/s, HMVIP 16.384Mbit/s or H.100 16.384Mbit/s. The Transmit
Multiplex Enable bit and the Transmit Interface Mode Select [1:0] bits of the Transmit Interface Control Register
(TICR) determine the Transmit Back-plane Interface data rate.
The following table shows configurations of the Transmit Multiplex Enable bit and the Transmit Interface Mode
Select [1:0] bits of the Transmit Interface Control Register (TICR).
TRANSMIT INTERFACE CONTROL REGISTER (TICR) (INDIRECT ADDRESS = 0XN0H, 0X20H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
2
Transmit
Multiplex Enable
R/W
0 - The Transmit Back-plane Interface block is configured to non-channel-multi-
plexed mode
1 - The Transmit Back-plane Interface block is configured to channel-multiplexed
mode
1-0
Transmit
Interface Mode
Select
R/W
When combined with the Transmit Multiplex Enable bit, these bits determine the
Transmit Back-plane Interface data rate.
273
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The table below shows the combinations of Transmit Multiplex Enable bit and Transmit Interface Mode Select
[1:0] bits and the resulting Transmit Back-plane Interface data rates.
TRANSMIT MULTIPLEX
ENABLE BIT
TRANSMIT INTERFACE
MODE SELECT BIT 1
TRANSMIT INTERFACE
MODE SELECT BIT 0
BACK-PLANE INTERFACE DATA RATE
0
0
0
0
1
1
1
1
0
0
1
1
0
0
1
1
0
1
0
1
0
1
0
1
XRT84V24 Compatible 2.048Mbit/s
MVIP 2.048Mbit/s
4.096Mbit/s
8.192Mbit/s
-
Bit Multiplexed 16.384Mbit/s
HMVIP 16.384Mbit/s
H.100 16.384Mbit/s
When the Transmit Multiplex Enable bit is set to zero, the framer is configured in non-channel-multiplexed
mode. The possible data rates are XRT84V24 Compatible 2.048Mbit/s, MVIP 2.048Mbit/s, 4.096Mbit/s and
8.192Mbit/s. In non-channel-multiplexed mode, payload data of each channel are taken from the Terminal
Equipment separately. Each channel uses its own Transmit Serial Clock, Transmit Serial Data, Transmit Single-
frame Synchronization signal and Transmit Multi-frame Synchronization signal as interface between the framer
and the Terminal Equipment. Section 1.1.2.1, 1.1.2.2 and 1.1.2.3 provide details on how to connect the Trans-
mit Payload Data Interface block with the Terminal Equipment when the Back-plane interface data rate is
1.544Mbit/s.
When the Back-plane interface data rate is MVIP 2.048Mbit/s, 4.096Mbit/s and 8.192Mbit/s, the Transmit Serial
Clock, Transmit Serial Data, Transmit Single-frame Synchronization signal and Transmit Multi-frame Synchroni-
zation signal are all configured as inputs. The Transmit Serial Clock is always an input clock with frequency of
2.048 MHz for all data rates. The TxMSync_n signal is configured as the Transmit Input Clock with frequencies
of 2.048 MHz, 4.096 MHz and 8.192 MHz respectively. It serves as the primary clock source for the High-speed
Back-plane Interface.
The table below summaries the clock frequencies of TxSerClk_n and TxInClk_n inputs when the framer is op-
erating in non-multiplexed High-speed Back-plane mode.
TRANSMIT MULTIPLEX ENABLE BIT = 0
TRANSMIT INTERFACE
MODE SELECT BIT 1
TRANSMIT INTERFACE
MODE SELECT BIT 0
BACK-PLANE
INTERFACE DATA RATE
TXSERCLK
TXMSYNC/TXINCLK
0
0
1
1
0
1
0
1
2.048Mbit/s
MVIP 2.048Mbit/s
4.096Mbit/s
2.048 MHz
2.048 MHz
2.048 MHz
2.048 MHz
-
2.048 MHz
4.096 MHz
8.192 MHz
8.192Mbit/s
When the Transmit Multiplex Enable bit is set to one, the framer is configured in channel-multiplexed mode.
The possible data rates are bit-multiplexed 16.384Mbit/s, HMVIP 16.384Mbit/s and H.100 16.384Mbit/s. In
channel-multiplexed mode, every four channels share the Transmit Serial Data and Transmit Single-frame Syn-
chronization signal of one channel as interface between the framer and the local Terminal Equipment. The
TxMSync_n signal of one channel is configured as the Transmit Input Clock with frequencies of 16.384 MHz. It
serves as the primary clock source for the High-speed Back-plane Interface.
274
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
Payload and signaling data of Channel 0-3 are multiplexed onto the Transmit Serial Data pin of Channel 0. Pay-
load and signaling data of Channel 4-7 are multiplexed onto the Transmit Serial Data pin of Channel 4. The
Transmit Single-frame Synchronization signal of Channel 0 pulses HIGH at the beginning of the frame with da-
ta from Channel 0-3 multiplexed together. The Transmit Single-frame Synchronization signal of Channel 4 puls-
es HIGH at the beginning of the frame with data from Channel 4-7 multiplexed together. It is responsibility of
the Terminal Equipment to align the multiplexed transmit serial data with the Transmit Single-frame Synchroni-
zation pulse. Additionally, each channel requires the local Terminal Equipment to provide a free-running 2.048
MHz clock into the Transmit Serial Clock input.
The table below summaries the clock frequencies of TxSerClk_n and TxInClk_n inputs when the framer is op-
erating in multiplexed High-speed Back-plane mode.
TRANSMIT MULTIPLEX ENABLE BIT = 1
TRANSMIT INTERFACE
MODE SELECT BIT 1
TRANSMIT INTERFACE
MODE SELECT BIT 0
BACK-PLANE
INTERFACE DATA RATE
TXSERCLK
TXMSYNC/TXCLK
0
0
0
1
-
-
-
Bit-multiplexed
16.384Mbit/s
2.048 MHz
16.384 MHz
1
1
0
1
HMVIP 16.384Mbit/s
H.100 16.384Mbit/s
2.048 MHz
2.048 MHz
16.384 MHz
16.384 MHz
The Transmit Serial Clock is always running at 1.544MHz for all the High-speed Back-plane Interface modes. It
is automatically the timing source of the Transmit Section of the framer in High-speed Back-plane Interface
mode.
The Transmit Single-frame Synchronization signal should pulse HIGH or LOW for one bit period at the First bit
position of each E1 frame. Length of the bit period depends on data rate of the High-speed Back-plane Inter-
face. The Transmit Synchronization Pulse Low bit of the Transmit Interface Control Register (TICR) determines
whether the Transmit Single-frame Synchronization signal is HIGH active or LOW active.
The table below shows configurations of the Transmit Synchronization Pulse LOW bit of the Transmit Interface
Control Register (TICR).
TRANSMIT INTERFACE CONTROL REGISTER (TICR)(INDIRECT ADDRESS = 0XN0H, 0X20H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3
Transmit
Synchronization
Pulse LOW
R/W
0 - The Transmit Single-frame Synchronization signal will pulse HIGH indicat-
ing the beginning of an E1 frame when the High-speed Back-plane Interface is
running at a mode other than the XRT84V24 Compatible 2.048Mbit/s.
1 - The Transmit Single-frame Synchronization signal will pulse LOW indicat-
ing the beginning of an E1 frame when the High-speed Back-plane Interface is
running at a mode other than the XRT84V24 Compatible 2.048Mbit/s.
Throughout the discussion of this datasheet, we assume that the Transmit Single-frame Synchronization signal
pulses HIGH unless stated otherwise.
The TxMSync_n signal, which is a multiplexed I/O pin, no longer functions as the Transmit Multi-frame Syn-
chronization Signal. Indeed, it becomes the Transmit Input Clock signal (TxInClk) of the High-speed Back-
plane Interface of the framer. The local Terminal Equipment should provide a free-running clock with the same
frequency as the High-speed Back-plane Interface to this input pin.
The following sections discuss details of how to operate the framer in different Back-plane interface speed
mode and how to connect the Transmit Payload Data Input Interface block to the local Terminal Equipment.
6.1.3.1 E1 Transmit Input Interface - MVIP 2.048 MHz
275
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
When the Transmit Multiplex Enable bit is set to zero and the Transmit Interface Mode Select [1:0] bits are set
to 01, the Transmit Back-plane interface of framer is running at a data rate of 2.048Mbit/s.
The interface consists of the following pins:
• Data input (TxSer_n)
• Transmit Serial Clock Input signal (TxSerClk_n)
• Transmit Single-frame Synchronization Input signal (TxSync_n)
• Transmit Input Clock (TxInClk_n)
• Transmit Time-slot Indication clock (TxTSClk_n)
• Transmit Time Slot indicator bits (TxTSb[4:0]_n)
The Transmit Back-plane interface is accepting data through TxSer_n at 2.048Mbit/s. The local Terminal Equip-
ment supplies a free-running 2.048MHz clock to he Transmit Input Clock pin of the framer. The local Terminal
Equipment also provides synchronized payload data at rising edge of the clock. The Transmit High-speed
Back-plane Interface of the framer then latches incoming serial data at falling edge of the Transmit Input Clock.
The Transmit Single-frame Synchronization input signal (TxSync_n) should pulse HIGH at the beginning of the
256-bit frame indicating start of the frame. By sampling the HIGH pulse on the Transmit Single-frame Synchro-
nization signal, the framer can position the beginning of an E1 frame. It is responsibility of the local Terminal
Equipment to align the Transmit Single-frame Synchronization signal with serial data stream going into the
framer.
See Figure 69 below for how to interface the local Terminal Equipment with the Transmit Payload Data Input In-
terface block of the framer in MVIP 2.048Mbit/s mode.
FIGURE 69. INTERFACING XRT84L38 TO LOCAL TERMINAL EQUIPMENT USING MVIP 2.048MBIT/S DATA BUS
XRT84L38
TxSerClk_0
Transmit
TxSer_0
Payload
TxInClk_0 (2.048MHz) Data Input
Interface
Chn 0
TxSync_0
Terminal
Equipment
TxSerClk_7
Transmit
TxSer_7
Payload
Data Input
Interface
Chn 7
TxInClk_7 (2.048MHz)
TxSync_7
276
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The timing diagram of input signals to the framer when running at MVIP 2.048Mbit/s mode is shown in
Figure 70.
FIGURE 70. TIMING DIAGRAM OF INPUT SIGNALS TO THE FRAMER WHEN RUNNING AT MVIP 2.048MBIT/S
TxSerClk
TxSerClk (INV)
TxSer
F
Don't Care
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
Don't Care
Don't Care
1 2 3 4 5 6 7 8
TxSync(input)
TxSync(input)
MVIP mode
Don't Care
Don't Care
A B C D
Don't Care
A B C D
TxChn[0]/TxSig
Don't Care
A B C D
A B C D
Note: The following signals are not aligned with the signals shown above. The TxChClk is derived from 1.544MHz transmit clock.
TxSyncFrd=0
TxChClk
Don't Care
Don't Care
1 2 3 4 5 6 7 8
Don't Care
Don't Care
1 2 3 4 5 6 7 8
TxChn[1]/TxFrTD
TxSyncFrd=1
1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8
TxChn[1]/TxFrTD
TxChClk
6.1.3.2 E1 Transmit Input Interface - 4.096 MHz
(This interface mode is the same as running at 2.048 MHz. The only difference is that the Transmit Input Clock
runs two times faster at 4.096 MHz)
When the Transmit Multiplex Enable bit is set to zero and the Transmit Interface Mode Select [1:0] bits are set
to 10, the Transmit Back-plane interface of framer is running at a clock rate of 4.096MHz.
The interface consists of the following pins:
• Data input (TxSer_n)
• Transmit Serial Clock Input signal (TxSerClk_n)
• Transmit Single-frame Synchronization Input signal (TxSync_n)
• Transmit Input Clock (TxInClk_n)
• Transmit Time-slot Indication clock (TxTSClk_n)
• Transmit Time Slot indicator bits (TxTSb[4:0]_n)
The Transmit Back-plane interface is still accepting data through TxSer_n at an E1 equivalent data rate of
2.048Mbit/s. However, the local Terminal Equipment supplies a free-running 4.096MHz clock to the Transmit
Input Clock pin of the framer. The local Terminal Equipment provides synchronized payload data at every other
rising edge of the Transmit Input Clock. The Transmit High-speed Back-plane Interface of the framer then latch-
es incoming serial data at every other falling edge of the clock.
Transmit Single-frame Synchronization input signal (TxSync_n) should pulse HIGH at the beginning of the 256-
bit frame indicating start of the frame. By sampling the HIGH pulse on the Transmit Single-frame Synchroniza-
tion signal, the framer can position the beginning of an E1 frame. It is responsibility of the local Terminal Equip-
ment to align the Transmit Single-frame Synchronization signal with serial data stream going into the framer.
277
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
See Figure 71 below for how to interface the local Terminal Equipment with the Transmit Payload Data Input In-
terface block of the framer in 4.096Mbit/s mode.
FIGURE 71. INTERFACING XRT84L38 TO LOCAL TERMINAL EQUIPMENT USING 4.096MBIT/S DATA BUS
XRT84L38
TxSerClk_0
Transmit
TxSer_0
Payload
TxInClk_0 (4.096MHz) Data Input
Interface
Chn 0
TxSync_0
Terminal
Equipment
TxSerClk_7
Transmit
TxSer_7
Payload
Data Input
Interface
Chn 7
TxInClk_7 (4.096MHz)
TxSync_7
The timing diagram of input signals to the framer when running at 4.096Mbit/s mode is shown in Figure 72.
FIGURE 72. TIMING DIAGRAM OF INPUT SIGNALS TO THE FRAMER WHEN RUNNING AT 4.096MBIT/S MODE
TxSerClk (4MHz)
TxSerClk (2MHz)
TxSerClk (INV)
TxSer
F
Don't Care
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
Don't care
Don't Care
1 2 3 4 5 6 7 8
TxSync(input)
TxChn[0]/TxSig
Don't Care
Don't Care
A B C D
Don't Care
A B C D
Don't Care
A B C D
A B C D
Note: The following signals are not aligned with the signals shown above. The TxChClk is derived from 1.544MHz transmit clock.
TxChClk(INV)
Don't Care
1 2 3 4 5 6 7 8
Don't Care
1 2 3 4 5 6 7 8
TxChn[1]/TxFrTD
6.1.3.3 E1 Transmit Input Interface - 8.192 MHz
(This interface mode is the same as running at 2.048 MHz. The only difference is that the Transmit Input Clock
runs four times faster at 8.192MHz)
When the Transmit Multiplex Enable bit is set to zero and the Transmit Interface Mode Select [1:0] bits are set
to 11, the Transmit Back-plane interface of framer is running at a clock rate of 8.192MHz.
The interface consists of the following pins:
278
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
• Data input (TxSer_n)
• Transmit Serial Clock Input signal (TxSerClk_n)
• Transmit Single-frame Synchronization Input signal (TxSync_n)
• Transmit Input Clock (TxInClk_n)
• Transmit Time-slot Indication clock (TxTSClk_n)
• Transmit Time Slot indicator bits (TxTSb[4:0]_n)
The Transmit Back-plane interface is still accepting data through TxSer_n at an E1 equivalent data rate of
2.048Mbit/s. However, the local Terminal Equipment supplies a free-running 8.192MHz clock to the Transmit
Input Clock pin of the framer. The local Terminal Equipment provides synchronized payload data at every other
four rising edge of the Transmit Input Clock. The Transmit High-speed Back-plane Interface of the framer then
latches incoming serial data at every other four falling edge of the clock.
The Transmit Single-frame Synchronization input signal (TxSync_n) should pulse HIGH at the beginning of the
256-bit frame indicating start of the frame. By sampling the HIGH pulse on the Transmit Single-frame Synchro-
nization signal, the framer can position the beginning of an E1 frame. It is responsibility of the local Terminal
Equipment to align the Transmit Single-frame Synchronization signal with serial data stream going into the
framer.
See Figure 73 below for how to interface the local Terminal Equipment with the Transmit Payload Data Input In-
terface block of the framer in 8.192Mbit/s mode.
FIGURE 73. INTERFACING XRT84L38 TO LOCAL TERMINAL EQUIPMENT USING 8.192MBIT/S DATA BUS
XRT84L38
TxSerClk_0
Transmit
TxSer_0
Payload
TxInClk_0 (8.192MHz) Data Input
Interface
Chn 0
TxSync_0
Terminal
Equipment
TxSerClk_7
Transmit
TxSer_7
Payload
Data Input
Interface
Chn 7
TxInClk_7 (8.192MHz)
TxSync_7
279
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The timing diagram of input signals to the framer when running at 8.192Mbit/s mode is shown in Figure 74.
FIGURE 74. TIMING DIAGRAM OF INPUT SIGNALS TO THE FRAMER WHEN RUNNING AT 8.192MBIT/S MODE
TxSerClk (8MHz)
TxSerClk (2MHz)
TxSerClk (INV)
TxSer
F
Don't Care
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
Don't care
Don't Care
1 2 3 4 5 6 7 8
TxSync(input)
TxChn[0]/TxSig
Don't Care
Don't Care
A B C D
Don't Care
A B C D
Don't Care
A B C D
A B C D
Note: The following signals are not aligned with the signals shown above. The TxChClk is derived from 1.544MHz transmit clock.
TxChClk(INV)
Don't Care
1 2 3 4 5 6 7 8
Don't Care
1 2 3 4 5 6 7 8
TxChn[1]/TxFrTD
6.1.3.4 E1 Transmit Input Interface - Bit-Multiplexed 16.384Mbit/s
When the Transmit Multiplex Enable bit is set to one and the Transmit Interface Mode Select [1:0] bits are set to
01, the Transmit Back-plane interface of framer is running at a clock rate of 16.384MHz.
The interface consists of the following pins:
• Data input (TxSer_n)
• Transmit Serial Clock Input signal (TxSerClk_n)
• Transmit Single-frame Synchronization Input signal (TxSync_n)
• Transmit Input Clock (TxInClk_n)
• Transmit Time-slot Indication clock (TxTSClk_n)
• Transmit Time Slot indicator bits (TxTSb[4:0]_n)
The Transmit Back-plane Interface is accepting data through TxSer_0 or TxSer_4 pins at 16.384Mbit/s. The lo-
cal Terminal Equipment multiplexes payload and signaling data of every four channels into one data stream.
Payload and signaling data of Channel 0-3 are multiplexed onto the Transmit Serial Data pin of Channel 0. Pay-
load and signaling data of Channel 4-7 are multiplexed onto the Transmit Serial Data pin of Channel 4.
Free-running clocks of 16.384MHz is supplied to the Transmit Input Clock pin of Channel 0 and Channel 4 of
the framer. The local Terminal Equipment provides multiplexed payload data at rising edge of this Transmit In-
put Clock. The Transmit High-speed Back-plane Interface of the framer then latches incoming serial data at fall-
ing edge of the clock.
The local Terminal Equipment maps four 2.048Mbit/s E1 data streams into this 16.384Mbit/s data stream as
described below:
1. Payload data of four channels are repeated and grouped together in a bit-interleaved way. The first payload
bit of Timeslot 0 of Channel 0 is sent first, followed by the first payload bit of Timeslot 0 of Channel 1 and 2.
The first payload bit of Timeslot 0 of Channel 3 is sent last.
280
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
After the first bits of Timeslot 0 of all four channels are sent, it comes the second bit of Timeslot 0 of Chan-
nel 0 and so on. The table below demonstrates how payload bits of four channels are mapped into the
16.384Mbit/s data stream.
FIRST OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
10
10
11
11
12
12
13
13
SECOND OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
20
20
21
21
22
22
23
23
XY: The Xth payload bit of Channel Y
2. The local Terminal Equipment also multiplexed signaling bits with payload bits and sent them together
through the 16.384Mbit/s data stream.
When the Terminal Equipment is sending the fifth payload bit of a particular channel, instead of sending it
twice, it inserts the signaling bit A of that particular channel. Similarly, the sixth payload bit of a particular
channels is followed by the signaling bit B of that channel; the seventh payload bit is followed by the signal-
ing bit C; the eighth payload bit is followed by the signaling bit D.
The following table illustrates how payload bits and signaling bits are multiplexed together into the
16.384Mbit/s data stream.
FIFTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
50
A0
51
A1
52
A2
53
A3
SIXTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
60
B0
61
B1
62
B2
63
B3
SEVENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
70
C0
71
C1
72
C2
73
C3
281
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
EIGHTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
80
D0
81
D1
82
D2
83
D3
XY: The Xth payload bit of Channel Y
AY: The signaling bit A of Channel Y
3. After the first octet of all four channels are sent, the local Terminal Equipment start sending the second
octets following the same rules of Step 1 and 2.
The Transmit Single-frame Synchronization signal of Channel 0 pulses HIGH for one clock cycle at the first bit
position of the data stream with data from Channel 0-3 multiplexed together. The Transmit Single-frame Syn-
chronization signal of Channel 4 pulses HIGH for one clock cycle at the first bit position of the data stream with
data from Channel 4-7 multiplexed together. By sampling the HIGH pulse on the Transmit Single-frame Syn-
chronization signal, the framer can position the beginning of the multiplexed E1 frame. It is responsibility of the
Terminal Equipment to align the multiplexed transmit serial data with the Transmit Single-frame Synchroniza-
tion pulse.
Inside the framer, all the "don't care" bits will be stripped away. The framing bits, signaling and payload data are
de-multiplexed inside the XRT84L38 device and send to each individual channel. These data will be processed
by each individual framer and send to LIU interface. The local Terminal Equipment provides a free-running
1.544MHz clock to the Transmit Serial Input clock of each channel. The framer will use this clock to carry the
processed payload and signaling data to the transmit section of the device.
See Figure 75 below for how to interface the local Terminal Equipment with the Transmit Payload Data Input In-
terface block of the framer in Bit-multiplexed 16.384Mbit/s mode.
282
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
FIGURE 75. INTERFACING XRT84L38 TO LOCAL TERMINAL EQUIPMENT USING 16.384MBIT/S DATA BUS
XRT84L38
TxSer_0
Transmit
Payload
Data Input
Interface
Chn 0
TxInClk_0 (16.384MHz)
TxSync_0
TxSerClk_0 (1.544MHz)
TxSerClk_1 (1.544MHz)
TxSerClk_2 (1.544MHz)
TxSerClk_3 (1.544MHz)
Chn 1
Chn 2
Chn 3
Terminal
Equipment
TxSer_4
Transmit
Payload
Data Input
Interface
Chn 4
TxInClk_4 (16.384MHz)
TxSync_4
TxSerClk_4 (1.544MHz)
TxSerClk_5 (1.544MHz)
TxSerClk_6 (1.544MHz)
TxSerClk_7 (1.544MHz)
Chn 5
Chn 6
Chn 7
The Input signal timing is shown in Figure 76 below when the framer is running at Bit-Multiplexed 16.384Mbit/s
mode.
FIGURE 76. IMING SIGNAL WHEN THE FRAMER IS RUNNING AT BIT-MULTIPLEXED 16.384MBIT/S MODE
TxSerClk (16.384MHz)
TxSerClk (INV)
56 cycles
TxSer
F0 F0 F1 F1 F2 F2 F3 F3
10 X 11 X 12 X 13 X 20 X 21
X
30
X
40
X
50 A0 51 A1 52 A2 53 A3
TxSync(input)
6.1.3.5 E1 Transmit Input Interface - HMVIP 16.384Mbit/s
When the Transmit Multiplex Enable bit is set to one and the Transmit Interface Mode Select [1:0] bits are set to
10, the Transmit Back-plane interface of framer is running at a clock rate of 16.384MHz.
The interface consists of the following pins:
• Data input (TxSer_n)
• Transmit Serial Clock Input signal (TxSerClk_n)
• Transmit Single-frame Synchronization Input signal (TxSync_n)
• Transmit Input Clock (TxInClk_n)
• Transmit Time-slot Indication clock (TxTSClk_n)
283
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
• Transmit Time Slot indicator bits (TxTSb[4:0]_n)
The Transmit Back-plane Interface is accepting data through TxSer_0 or TxSer_4 pins at 16.384Mbit/s. The lo-
cal Terminal Equipment multiplexes payload and signaling data of every four channels into one data stream.
Payload and signaling data of Channel 0-3 are multiplexed onto the Transmit Serial Data pin of Channel 0. Pay-
load and signaling data of Channel 4-7 are multiplexed onto the Transmit Serial Data pin of Channel 4.
Free-running clocks of 16.384MHz is supplied to the Transmit Input Clock pin of Channel 0 and Channel 4 of
the framer. The local Terminal Equipment provides multiplexed payload data at rising edge of this Transmit In-
put Clock. The Transmit High-speed Back-plane Interface of the framer then latches incoming serial data at fall-
ing edge of the clock.
The local Terminal Equipment maps four 2.048Mbit/s E1 data streams into this 16.384Mbit/s data stream as
described below:
1. Payload data of four channels are repeated and grouped together in a byte-interleaved way. The first pay-
load bit of Timeslot 0 of Channel 0 is sent first, followed by the second payload bit of Timeslot 0 of Channel
0 and so on. After all the bits of Timeslot 0 of Channel 0 is sent repeatedly, the Terminal Equipment will
start sending the payload bits of Timeslot 0 of Channel 1 and 2. The payload bits of Timeslot 0 of Channel
3 are sent the last.
After the payload bits of Timeslot 0 of all four channels are sent, it comes the payload bits of Timeslot 1 of
Channel 0 and so on. The table below demonstrates how payload bits of four channels are mapped into
the 16.384Mbit/s data stream.
FIRST OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
10
10
20
20
30
30
40
40
THIRD OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
11
11
21
21
31
31
41
41
FIFTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
12
12
22
22
32
32
42
42
SEVENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
13
13
23
23
33
33
43
43
XY: The Xth payload bit of Channel Y
2. The local Terminal Equipment also multiplexed signaling bits with payload bits and sent them together
through the 16.384Mbit/s data stream.
284
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
When the Terminal Equipment is sending the fifth payload bit of a particular channel, instead of sending it
twice, it inserts the signaling bit A of that particular channel. Similarly, the sixth payload bit of a particular
channels is followed by the signaling bit B of that channel; the seventh payload bit is followed by the signal-
ing bit C; the eighth payload bit is followed by the signaling bit D.
The following table illustrates how payload bits and signaling bits are multiplexed together into the
16.384Mbit/s data stream.
SECOND OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
50
A0
60
B0
70
C0
80
D0
FOURTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
51
A1
61
B1
71
C1
81
D1
SIXTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
52
A2
62
B2
72
C2
82
D2
EIGHTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
53
A3
63
B3
73
C3
83
D3
XY: The Xth payload bit of Channel Y
AY: The signaling bit A of Channel Y
3. After the first octet of all four channels are sent, the local Terminal Equipment start sending the second
octets following the same rules of Step 1 and 2.
The Transmit Single-frame Synchronization signal should pulse HIGH for four clock cycles (the last two bit po-
sitions of the previous multiplexed frame and the first two bits of the next multiplexed frame) indicating frame
boundary of the multiplexed data stream. The Transmit Single-frame Synchronization signal of Channel 0 puls-
es HIGH to identify the start of multiplexed data stream of Channel 0-3. The Transmit Single-frame Synchroni-
zation signal of Channel 4 pulses HIGH to identify the start of multiplexed data stream of Channel 4-7. By sam-
pling the HIGH pulse on the Transmit Single-frame Synchronization signal, the framer can position the begin-
ning of the multiplexed E1 frame. It is responsibility of the Terminal Equipment to align the multiplexed transmit
serial data with the Transmit Single-frame Synchronization pulse.
Inside the framer, all the "don't care" bits will be stripped away. The framing bits, signaling and payload data are
de-multiplexed inside the XRT84L38 device and send to each individual channel. These data will be processed
by each individual framer and send to LIU interface. The local Terminal Equipment provides a free-running
285
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
2.048MHz clock to the Transmit Serial Input clock of each channel. The framer will use this clock to carry the
processed payload and signaling data to the transmit section of the device.
See Figure 77 below for how to interface the local Terminal Equipment with the Transmit Payload Data Input In-
terface block of the framer in HMVIP 16.384Mbit/s mode.
FIGURE 77. INTERFACING XRT84L38 TO LOCAL TERMINAL EQUIPMENT USING 16.384MBIT/S DATA BUS
XRT84L38
TxSer_0
Transmit
Payload
Data Input
Interface
Chn 0
TxInClk_0 (16.384MHz)
TxSync_0
TxSerClk_0 (1.544MHz)
TxSerClk_1 (1.544MHz)
TxSerClk_2 (1.544MHz)
TxSerClk_3 (1.544MHz)
Chn 1
Chn 2
Chn 3
Terminal
Equipment
TxSer_4
Transmit
Payload
Data Input
Interface
Chn 4
TxInClk_4 (16.384MHz)
TxSync_4
TxSerClk_4 (1.544MHz)
TxSerClk_5 (1.544MHz)
TxSerClk_6 (1.544MHz)
TxSerClk_7 (1.544MHz)
Chn 5
Chn 6
Chn 7
The Input signal timing is shown in Figure 78 below when the framer is running at HMVIP 16.384Mbit/s mode.
FIGURE 78. TIMING SIGNAL WHEN THE FRAMER IS RUNNING AT HMVIP 16.384MBIT/S MODE
TxSerClk (16.384MHz)
TxSerClk (INV)
56 cycles
56 cycles
TxSer
TxSig
73 73 83 83 F0 F0 F1 F1 F2 F2 F3 F3
Start of Frame
10 10 20 20 30 30 40 40 50 A0 60 B0
Xy : X is the bit number and y is the channel number
0 0 0 0 0 0 A0A0B0B0C0C0 0 0 A2A2
12 12
52 52
53 53 63 63 73 73 83 83
A3A3B3B3C3C3D3D3
C3C3D3D3 1 1 1 1 1 1 1 1
TxSync(input)
HMVIP, negative sync
TxSync(input)
HMVIP, positive sync
6.1.3.6 E1 Transmit Input Interface - H.100 16.384Mbit/s
When the Transmit Multiplex Enable bit is set to one and the Transmit Interface Mode Select [1:0] bits are set to
11, the Transmit Back-plane interface of framer is running at H.100 16.384Mbit/s mode.
(The HMVIP mode and the H.100 mode are essential the same except for the HIGH pulse position of the
Transmit Single-frame Synchronization Signal)
286
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The interface consists of the following pins:
• Data input (TxSer_n)
• Transmit Serial Clock Input signal (TxSerClk_n)
• Transmit Single-frame Synchronization Input signal (TxSync_n)
• Transmit Input Clock (TxInClk_n)
• Transmit Time-slot Indication clock (TxTSClk_n)
• Transmit Time Slot indicator bits (TxTSb[4:0]_n)
The Transmit Back-plane Interface is accepting data through TxSer_0 or TxSer_4 pins at 16.384Mbit/s. The lo-
cal Terminal Equipment multiplexes payload and signaling data of every four channels into one data stream.
Payload and signaling data of Channel 0-3 are multiplexed onto the Transmit Serial Data pin of Channel 0. Pay-
load and signaling data of Channel 4-7 are multiplexed onto the Transmit Serial Data pin of Channel 4.
Free-running clocks of 16.384MHz is supplied to the Transmit Input Clock pin of Channel 0 and Channel 4 of
the framer. The local Terminal Equipment provides multiplexed payload data at rising edge of this Transmit In-
put Clock. The Transmit High-speed Back-plane Interface of the framer then latches incoming serial data at fall-
ing edge of the clock.
The local Terminal Equipment maps four 2.048Mbit/s E1 data streams into this 16.384Mbit/s data stream as
described below:
1. Payload data of four channels are repeated and grouped together in a byte-interleaved way. The first pay-
load bit of Timeslot 0 of Channel 0 is sent first, followed by the second payload bit of Timeslot 0 of Channel
0 and so on. After all the bits of Timeslot 0 of Channel 0 is sent repeatedly, the Terminal Equipment will
start sending the payload bits of Timeslot 0 of Channel 1 and 2. The payload bits of Timeslot 0 of Channel
3 are sent the last.
After the payload bits of Timeslot 0 of all four channels are sent, it comes the payload bits of Timeslot 1 of
Channel 0 and so on. The table below demonstrates how payload bits of four channels are mapped into
the 16.384Mbit/s data stream.
FIRST OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
10
10
20
20
30
30
40
40
THIRD OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
11
11
21
21
31
31
41
41
FIFTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
12
12
22
22
32
32
42
42
287
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
SEVENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
13
13
23
23
33
33
43
43
XY: The Xth payload bit of Channel Y
2. The local Terminal Equipment also multiplexed signaling bits with payload bits and sent them together
through the 16.384Mbit/s data stream.
When the Terminal Equipment is sending the fifth payload bit of a particular channel, instead of sending it
twice, it inserts the signaling bit A of that particular channel. Similarly, the sixth payload bit of a particular
channels is followed by the signaling bit B of that channel; the seventh payload bit is followed by the signal-
ing bit C; the eighth payload bit is followed by the signaling bit D.
The following table illustrates how payload bits and signaling bits are multiplexed together into the
16.384Mbit/s data stream.
SECOND OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
50
A0
60
B0
70
C0
80
D0
FOURTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
51
A1
61
B1
71
C1
81
D1
SIXTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
52
A2
62
B2
72
C2
82
D2
EIGHTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
53
A3
63
B3
73
C3
83
D3
XY: The Xth payload bit of Channel Y
AY: The signaling bit A of Channel Y
288
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
3. After the first octet of all four channels are sent, the local Terminal Equipment start sending the second
octets following the same rules of Step 1 and 2.
The Transmit Single-frame Synchronization signal should pulse HIGH for two clock cycles (the last bit position
of the previous multiplexed frame and the first bit position of the next multiplexed frame) indicating frame
boundary of the multiplexed data stream. The Transmit Single-frame Synchronization signal of Channel 0 puls-
es HIGH to identify the start of multiplexed data stream of Channel 0-3. The Transmit Single-frame Synchroni-
zation signal of Channel 4 pulses HIGH to identify the start of multiplexed data stream of Channel 4-7. By sam-
pling the HIGH pulse on the Transmit Single-frame Synchronization signal, the framer can position the begin-
ning of the multiplexed E1 frame. It is responsibility of the Terminal Equipment to align the multiplexed transmit
serial data with the Transmit Single-frame Synchronization pulse.
Inside the framer, all the "don't care" bits will be stripped away. The framing bits, signaling and payload data are
de-multiplexed inside the XRT84L38 device and send to each individual channel. These data will be processed
by each individual framer and send to LIU interface. The local Terminal Equipment provides a free-running
2.048MHz clock to the Transmit Serial Input clock of each channel. The framer will use this clock to carry the
processed payload and signaling data to the transmit section of the device.
See Figure 79 below for how to interface the local Terminal Equipment with the Transmit Payload Data Input In-
terface block of the framer in HMVIP 16.384Mbit/s mode.
FIGURE 79. INTERFACING XRT84L38 TO LOCAL TERMINAL EQUIPMENT USING 16.384MBIT/S DATA BUS
XRT84L38
TxSer_0
Transmit
Payload
Data Input
Interface
Chn 0
TxInClk_0 (16.384MHz)
TxSync_0
TxSerClk_0 (2.048MHz)
TxSerClk_1 (2.048MHz)
TxSerClk_2 (2.048MHz)
TxSerClk_3 (2.048MHz)
Chn 1
Chn 2
Chn 3
Terminal
Equipment
TxSer_4
Transmit
Payload
Data Input
Interface
Chn 4
TxInClk_4 (16.384MHz)
TxSync_4
TxSerClk_4 (2.048MHz)
TxSerClk_5 (2.048MHz)
TxSerClk_6 (2.048MHz)
TxSerClk_7 (2.048MHz)
Chn 5
Chn 6
Chn 7
289
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The Input signal timing is shown in Figure 80 below when the framer is running at H.100 16.384Mbit/s
mode.The E1 Receive Section
FIGURE 80. TIMING SIGNAL WHEN THE FRAMER IS RUNNING AT H.100 16.384MBIT/S MODE
TxSerClk (16.384MHz)
TxSerClk (INV)
56 cycles
56 cycles
TxSer
TxSig
73 73 83 83 F0 F0 F1 F1 F2 F2 F3 F3
Start of Frame
10 10 20 20 30 30 40 40 50 A0 60 B0
Xy : X is the bit number and y is the channel number
0 0 0 0 0 0 A0A0B0B0C0C0 0 0 A2A2
12 12
52 52
53 53 63 63 73 73 83 83
A3A3B3B3C3C3D3D3
C3C3D3D3 1 1 1 1 1 1 1 1
TxSync(input)
H.100, negative sync
TxSync(input)
H.100, positive sync
Delayer H.100
TxSync(input)
H.100, negative sync
TxSync(input)
H.100, positive sync
6.2 THE RECEIVE PAYLOAD DATA OUTPUT INTERFACE BLOCK
6.2.1 Description of the Receive Payload Data Output Interface Block
Each of the eight framers within the XRT84L38 device includes a Receive Payload Data Output Interface block.
The function of the block is to provide an interface to the Terminal Equipment (for example, a Central Office or
switching equipment) that has data to receive from a "Far End" terminal over an DS1 or E1 transport medium.
The Payload Data Output Interface module (also known as the Back-plane Interface module) supports payload
data to be taken from or presented to the system. In E1 mode, supported data rates are 1.544Mbit/s, MVIP
2.048Mbit/s, 4.096Mbit/s, 8.192Mbit/s, multiplexed 12.352Mbit/s, multiplexed 16.384Mbit/s, HMVIP
16.384Mbit/s or H.100 16.384Mbit/s. In E1 mode, supported data rates are XRT84V24 compatible 2.048Mbit/s,
MVIP 2.048Mbit/s, 4.096Mbit/s, 8.192Mbit/s, multiplexed 16.384Mbit/s, HMVIP 16.384Mbit/s or H.100
16.384Mbit/s.
The Receive Payload Data Output Interface block supplies or accepts the following signals to the Terminal
Equipment circuitry:
• Receive Serial Data Input (RxSer_n)
• Receive Serial Clock (RxSerClk_n)
• Receive Single-frame Synchronization Signal (RxSync_n)
• Receive Multi-frame Synchronization Signal (RxMSync_n)
• Receive Time-slot Indicator Clock (RxTSClk_n)
• Receive Time-slot Indication Bits (RxTSb[4:0]_n)
The Receive Serial Data is an output pin carrying payload, signaling and sometimes Data Link data supplied
by XRT84L38 device to the local Terminal Equipment.
The Receive Serial Clock is an input or output signal used by the Receive Payload Data Input Interface block to
send out serial data to the local Terminal Equipment. The Receive Clock Inversion bit of the Receive Interface
Control Register (TICR) determines at which edge of the Receive Serial Clock would data transition on the Re-
ceive Serial Data pin occur.
290
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The table below shows configurations of the Receive Clock Inversion bit of the Receive Interface Control Reg-
ister (RICR).
RECEIVE INTERFACE CONTROL REGISTER (RICR) (INDIRECT ADDRESS = 0XN0H, 0X22H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3
Receive Clock
Inversion
R/W
0 - Serial data transition happens on rising edge of the Receive Serial Clock.
1 - Serial data transition happens on falling edge of the Receive Serial Clock.
Throughout the discussion of this datasheet, we assume that serial data transition happens on rising edge of
the Receive Serial Clock unless stated otherwise.
The Receive Single-frame Synchronization signal is either input or output. When configure as input, it indicates
beginning of an E1 frame. When configure as output, it indicates end of an E1 frame.
The Receive Multi-frame Synchronization signal is an output pin from XRT84L38 indicating end of an E1 multi-
frame.
By connecting these signals with the local Terminal Equipment, the Receive Payload Data Output Interface
routes received payload data from the Receive Framer Module to the local Terminal Equipment.
6.2.2 Brief Discussion of the Receive Payload Data Output Interface Block Operating at XRT84V24
Compatible 2.048Mbit/s mode
The incoming Receive Payload Data is taken into the framer from the LIU interface using the Recovered Re-
ceive Line Clock. The payload data is then routed through the Receive Farmer Module and presented to the
Receive Payload Data Output Interface through the Receive Serial Data output pin (RxSer_n). This data is then
clocked out using the Receive Serial Clock (RxSerClk_n).
There is a two-frame (512 bits) elastic buffer between the Receive Framer Module and the Receive Payload
Data Output Interface. This buffer can be enabled or disabled via programming the Slip Buffer Enable [1:0] bits
in Slip Buffer Control Register (SBCR).
The following table shows configurations of the Slip Buffer Enable [1:0] bits in Slip Buffer Control Register.
SLIP BUFFER CONTROL REGISTER (SBCR)(INDIRECT ADDRESS = 0XN0H, 0X16H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1-0
Slip Buffer
Enable
R/W
00 - Slip Buffer is bypassed. The Receive Payload Data is passing from the
Receive Framer Module to the Receive Payload Data Output Interface directly
without routing through the Slip Buffer. The Receive Serial Clock signal
(RxSerClk_n) is an output.
01 - The Elastic Store (Slip Buffer) is enabled. The Receive Payload Data is
passing from the Receive Framer Module through the Slip Buffer to the Receive
Payload Data Output Interface. The Receive Serial Clock signal (RxSerClk_n) is
an input.
10 - The Slip Buffer acts as a FIFO. The FIFO Latency Register (FLR) deter-
mines the data latency. The Receive Payload Data is passing from the Receive
Framer Module through the FIFO to the Receive Payload Data Output Interface.
The Receive Serial Clock signal (RxSerClk_n) is an input.
11 - Slip Buffer is bypassed. The Receive Payload Data is passing from the
Receive Framer Module to the Receive Payload Data Output Interface directly
without routing through the Slip Buffer. The Receive Serial Clock signal
(RxSerClk_n) is an output.
If the Slip Buffer is not in bypass mode, then the user has the option of either providing the Receive Single-
Frame Synchronization pulse or getting the Receive Single-Frame Synchronization pulse on frame boundary at
the RxSync_n pin. The Slip Buffer Receive Synchronization Direction bit of the Slip Buffer Control Register
(SBCR) determines whether the Receive Single-Frame Synchronization signal is input or output. The table be-
291
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
low demonstrates settings of the Slip Buffer Receive Synchronization Direction bit of the Slip Buffer Control
Register.
SLIP BUFFER CONTROL REGISTER (SBCR)(INDIRECT ADDRESS = 0XN0H, 0X16H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
2
Slip Buffer
Receive
R/W
0 - The Receive Single-Frame Synchronization signal (RxSync_n) is an output
if the Slip Buffer is not in bypass mode.
Synchronization
Direction
1 - The Receive Single-Frame Synchronization signal (RxSync_n) is an input if
the Slip Buffer is not in bypass mode.
If the Slip Buffer is in bypass mode, the Receive Payload Data is routed to the Receive Payload Data Output In-
terface from the Receive Framer Module directly. The Recovered Line Clock is used to carry the Receive Pay-
load Data all the way from the LIU interface, to the Receive Framer Module and eventually output through the
Receive Serial Data output pin. The Receive Serial Clock signal is therefore an output using the Recovered
Receive Line Clock as timing source. The Receive Single-Frame Synchronization signal is also output in Slip
Buffer bypass mode.
If the Slip Buffer is enabled, the Receive Payload Data is latched into the Elastic Store using the Recovered
Receive Line Clock. The local Terminal Equipment supplies a free-running 2.048MHz clock to the Receive Se-
rial Clock pin to latch the Receive Payload Data out from the Elastic Store. Since the Recovered Receive Line
Clock and the Receive Serial Clock are coming from different timing sources, the Slip Buffer will gradually fill or
empty. If the elastic buffer either fills or empties, a controlled slip will occur. If the buffer empties and a read oc-
curs, then a full frame of data will be repeated and a status bit will be updated. If the buffer fills and a write
comes, then a full frame of data will be deleted and another status bit will be set. A detailed description of the
Elastic Buffer can be found in later sections. In this mode, the Receive Single-Frame Synchronization signal
can be either input or output depending on the settings of the Slip Buffer Receive Synchronization Direction bit
of the Slip Buffer Control Register.
If the Slip Buffer is put into a FIFO mode, it is acting like a standard First-In-First-Out storage. A fixed READ
and WRITE latency is maintained in a programmable fashion controlled by the FIFO Latency Register
(FIFOLR). The local Terminal Equipment supplies a 2.048MHz clock to the Receive Serial Clock pin to latch
the Receive Payload Data out from the FIFO. However, it is the responsibility of the user to phase lock the input
Receive Serial Clock to the Recovered Receive Line Clock to avoid either over-run or under-run of the FIFO. In
this mode, the Receive Single-Frame Synchronization signal can be either input or output depending on the
settings of the Slip Buffer Receive Synchronization Direction bit of the Slip Buffer Control Register.
The following table summaries the input or output nature of the Receive Serial Clock and Receive Single-
Frame Synchronization signals for different Slip Buffer settings.
RECEIVE TIMING SOURCE
RXSERCLK_N
RXSYNC_N
Slip Buffer Synchronization
Slip Buffer Synchronization
Direction Bit = 1
Direction Bit = 0
Slip Buffer Bypassed
Slip Buffer Enabled
Output
Input
Output
Output
Input
Output
Slip Buffer Acts as FIFO
Input
Output
Input
292
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The Receive Time-slot Indication Bits (RxTSb[4:0]_n) are multiplexed I/O pins. The functionality of these pins is
governed by the value of Receive Fractional E1 Output Enable bit of the Receive Interface Control Register
(RICR). The following table illustrates the configurations of the Receive Fractional E1 Input Enable bit.
RECEIVE INTERFACE CONTROL REGISTER (RICR) (INDIRECT ADDRESS = 0XN0H, 0X22H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
4
Receive
Fractional E1
Output Enable
R/W
0 - The Receive Time-slot Indication bits (RxTSb[4:0] are outputting five-bit
binary values of Time-slot number (0-31) being accepted and processed by the
Receive Payload Data Output Interface block of the framer.
The Receive Time-slot Indicator Clock signal (RxTSClk_n) is a 256KHz clock
that pulses HIGH for one E1 bit period whenever the Receive Payload Data Out-
put Interface block is accepting the LSB of each of the twenty-four time slots.
1 - The RxTSb[0]_n bit becomes the Receive Fractional E1 Output signal
(RxFrTD_n) which carries Fractional E1 payload data from the framer.
The RxTSb[1]_n bit becomes the Receive Signaling Data Output signal
(RxSig_n) which is used to carry robbed-bit signaling data extracted from the
inbound E1 frame.
The RxTSb[2]_n bit serially outputs all five-bit binary values of the Time Slot
number (0-31) being accepted and processed by the Receive Payload Data Out-
put Interface block of the framer.
The RxTSClk_n will output gaped fractional E1 clock that can be used by Termi-
nal Equipment to latch in Fractional E1 payload data at rising edge of the clock.
Or,
The RxTSClk_n pin will be a clock enable signal to Receive Fractional E1 Output
signal (RxFrTD_n) when the un-gaped Receive Serail Output Clock
(RxSerClk_n) is used to latch in Fractional E1 Payload Data into the Terminal
Equipment.
When configured to operate in normal condition (that is, when the Receive Fractional E1 Input Enable bit is
equal to zero), these bits reflect the five-bit binary value of the Time Slot number (0-31) being outputted and
processed by the Receive Payload Data Output Interface block of the framer. RxTSb[4] represents the MSB of
the binary value and RxTSb[0] represents the LSB.
When the Receive Fractional E1 Output Enable bit is equal to one, the RxTSb[0]_n bit becomes the Receive
Fractional E1 Output signal (RxFrTD_n). This output pin carries Fractional E1 Output data extracted by the
framer from the incoming E1 data stream. The Fractional E1 Output Interface allows certain time-slots of E1
data to be routed to destinations other than the local Terminal Equipment. Function of the Fractional E1 Output
signal will be discussed in details in later sections.
When the Receive Fractional E1 Output Enable bit is equal to one, the RxTSb[1]_n bit becomes the Receive
Signaling Data Output signal (RxSig_n). These output pins can be used to carry robbed-bit signaling data ex-
tracted from the inbound E1 frame. Function of the Receive Signaling Data Output signal will be discussed in
details in later sections.
When the Receive Fractional E1 Output Enable bit is equal to one, the RxTSb[2]_n bit serially outputs all five-
bit binary values of the Time Slot number (0-31) being outputted and processed by the Receive Payload Data
Output Interface block of the framer. MSB of the binary value is presented first and the LSB is presented last.
The RxTSb[3]_n and RxTSb[4}_n pins are not multiplexed.
293
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The table below shows functionality of the RxTSb[2:0] bits when the Receive Fractional E1 Output bit is set to
different values.
RECEIVE FRACTIONAL E1 OUTPUT BIT = 0
RECEIVE FRACTIONAL E1 OUTPUT BIT = 1
RxTSb[0]
RxTSb[1]
RxTSb[2]
Output
Output
Output
RxFrTD
RxSig
RxTS
Output
Output
Output
The Receive Time-slot Indicator Clock signal (RxTSClk_n) is a multi-function output pin. When configured to
operate in normal condition (that is, when the Receive Fractional E1 Input Enable bit is equal to zero), the
RxTSClk_n is a 256KHz clock that pulses HIGH for one E1 bit period whenever the Receive Payload Data Out-
put Interface block is outputting the LSB of each of the twenty-four time slots. The local Terminal Equipment
should use this clock signal to sample the RxTSb[0] through RxTSb[4] bits and identify the time-slot being pro-
cessed via the Receive Section of the framer.
When the Receive Fractional E1 Output Enable bit is equal to one, the RxTSClk_n will output gaped fractional
E1 clock whenever Fractional E1 payload data is present at the RxFrTD_n pin. The local Terminal Equipment
can latch in Fractional E1 payload data at falling edge of the clock. Otherwise, this pin will be a clock enable
signal to Receive Fractional E1 output signal (RxFrTD_n) if the framer is configured accordingly. In this way,
Fractional E1 payload data is clocked into the Terminal Equipment using un-gaped Receive Serial Output
Clock (RxSerClk_n). A detailed discussion of the Fractional E1 Payload Data Output Interface can be found in
later sections.
A detailed discussion of how to connect the Receive Payload Data Output Interface block to the local Terminal
Equipment with Slip Buffer enabled or disabled can be found in the later sections.
6.2.2.1 Connect the Receive Payload Data Output Interface block to the Local Terminal Equipment if
the Slip Buffer is bypassed
By setting the Slip Buffer Enable [1:0] bits of the Slip Buffer Control Register to 00 or 11, the Receive Framer
Module routes the Receive Payload Data directly to the Receive Payload Data Output Interface without passing
through the Elastic Buffer. The XRT84L38 device uses the Recovered Receive Line Clock internally to carry
the Receive Payload Data directly across the whole chip. The Recovered Receive Line Clock is essentially be-
come timing source of the Receive Serial Clock output.
If the Slip Buffer is bypassed, the Receive Single-frame Synchronization signal is automatically configured to
be output signals. It should pulse HIGH for one E1 bit period (488ns) at the last bit position of each E1 frame.
By triggering on the HIGH pulse on the Receive Single-frame Synchronization signal, the Terminal Equipment
can identify the end of an E1 frame and should prepare to accept payload data of the next E1 frame from the
framer.
The Receive Multi-frame Synchronization signal should pulse HIGH for one E1 bit period (488ns) at the last bit
position of an E1 multi-frame. By triggering on the HIGH pulse on the Receive Multi-frame Synchronization sig-
nal, the framer can identify the end of an E1 super-frame and should prepare to accept payload data of the next
E1 super-frame from the framer.
294
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
See Figure 81 for how to connect the Receive Payload Data Output Interface block to the local Terminal Equip-
ment when the Slip Buffer is bypassed and the Recovered Receive Line Clock is timing source of the Receive
section.
FIGURE 81. INTERFACING XRT84L38 TO LOCAL TERMINAL EQUIPMENT WITH SLIP BUFFER BYPASSED AND RECOV-
ERED RECEIVE LINE CLOCK AS RECEIVE TIMING SOURCE
XRT84L38
RxSerClk_0
RxLineClk_0
RxSer_0
Receive
Payload
Data Input
Interface
Chn 0
RxMSync_0
RxSync_0
RxTSClk_0
RxTSb[4:0]_0
Terminal
Equipment
RxSerClk_7
RxSer_7
Receive
Payload
Data Input
Interface
Chn 7
RxMSync_7
RxSync_7
RxTSClk_7
RxTSb[4:0]_7
RxLineClk_7
The following Figure 82 shows waveforms of the signals (RxSerClk_n, RxSer_n, RxSync_n, RxTSClk_n and
RxTSb[4:0]_n) which connecting the Receive Payload Data Output Interface block to the local Terminal Equip-
295
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
ment when the Slip Buffer is bypassed and the Recovered Receive Line Clock is timing source of the Receive
section.
FIGURE 82. WAVEFORMS OF THE SIGNALS CONNECTING THE RECEIVE PAYLOAD DATA OUTPUT INTERFACE BLOCK
TO THE LOCAL TERMINAL EQUIPMENT WHEN THE SLIP BUFFER IS BYPASSED AND THE RECOVERED LINE CLOCK IS
THE TIMING SOURCE OF THE RECEIVE SECTION
Timeslot 0
Timeslot 5
Timeslot 6
Input Data
Timeslot 16
Input Data
RxSerClk
RxSer
RxSync(input)
RxSync(output)
RxChClk
RxChn[4:0]
Timeslot #0
Timeslot #5
Timeslot #6
Timeslot #16
RxChn[0]/RxSig
RxChn[2]/RxChn
A B C D
A B C D
A B C D
A B C D
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
RxChClk
RxChn[1]/RxFrTD
1 2 3 4 5 6 7 8
6.2.2.2 Connect the Receive Payload Data Output Interface block to the Local Terminal Equipment if
the Slip Buffer is enabled
By setting the Slip Buffer Enable [1:0] bits of the Slip Buffer Control Register to 01, the framer includes the two-
frame Elastic Buffer into its data path. The Receive Framer Module routes the Receive Payload Data to the
Elastic Buffer first. The Receive Payload Data is then presented to the Receive Payload Data Output Interface.
The XRT84L38 device uses the Recovered Receive Line Clock internally to clock in the Receive Payload Data
into the Elastic Buffer. The Terminal Equipment should provide a 2.048MHz clock to the Receive Serial Clock
input pin to latch data out from the Elastic Buffer.
The Recovered Receive Line Clock and the Receive Serial Clock are generated from two different timing
sources. That is, the Recovered Receive Line Clock is originating from a remote site while Receive Serial
Clock generating by a local oscillator. Any mismatch in frequencies of these two clocks will result in the Slip
Buffer to gradually fill or deplete.
Overtime, the Elastic Buffer either fills or empties completely. Once that happened, a controlled slip by the
XRT84L38 device will occur. The Receive Slip Buffer Slip bit of the Slip Buffer Status Register (SBSR) is set to
1.
If the buffer empties and a read occurs, then a full frame of data will be repeated and the Receive Slip Buffer
Empty bit of the Slip Buffer Status Register (SBSR) will be forced HIGH. If the buffer fills and a write comes,
then a full frame of data will be deleted and the Receive Slip Buffer Full bit of the Slip Buffer Status Register
(SBSR) will be forced HIGH.
296
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The following table demonstrates settings of the Receive Slip Buffer Slip bit, Receive Slip Buffer Empty bit and
Receive Slip Buffer Full bit of the Slip Buffer Status Register.
SLIP BUFFER STATUS REGISTER (SBSR)(INDIRECT ADDRESS = 0XNAH, 0X08H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
2
Receive Slip
Buffer Full
R/W
0 - The Receive Slip Buffer is not full.
1 - The Receive Slip Buffer is full and one frame of data is discarded.
1
1
Receive Slip
Buffer Empty
R/W
R/W
0 - The Receive Slip Buffer is not empty.
1 - The Receive Slip Buffer is empty and one frame of data is repeated.
Receive Slip
Buffer Slip
0 - The Receive Slip Buffer does not slip.
1 - The Receive Slip Buffer slips since either full or emptied.
In this mode, the Receive Single-Frame Synchronization signal can be either input or output depending on the
settings of the Slip Buffer Receive Synchronization Direction bit of the Slip Buffer Control Register. When the
Slip Buffer Receive Synchronization Direction bit is set to 0, the Receive Single-Frame Synchronization signal
(RxSync_n) is an. When the Slip Buffer Receive Synchronization Direction bit is set to 1,the Receive Single-
Frame Synchronization signal (RxSync_n) is an input.
If the Receive Single-Frame Synchronization signal is an output, it should pulse HIGH for one E1 bit period
(488ns) at the last bit position of each E1 frame. By triggering on the HIGH pulse on the Receive Single-frame
Synchronization signal, the Terminal Equipment can identify the end of an E1 frame and should prepare to ac-
cept payload data of the next E1 frame from the framer.
If the Receive Single-Frame Synchronization signal is an input, it should pulse HIGH for one E1 bit period
(488ns) at the first bit position (F-bit) of each E1 frame. By sampling the HIGH pulse of the Receive Single-
frame Synchronization signal, the framer should identity the beginning of an E1 frame and can send out data in
a synchronized way. It is the responsibility of the local Terminal Equipment to align the start of an E1 frame with
the Receive Single-Frame Synchronization pulse.
The Receive Multi-frame Synchronization signal should pulse HIGH for one E1 bit period (488ns) at the last bit
position of Frame number one of an E1 multi-frame. By triggering on the HIGH pulse on the Receive Multi-
frame Synchronization signal, the framer can identify the end of an E1 super-frame and should prepare to ac-
cept payload data of the next E1 super-frame from the framer.
297
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
See Figure 83 for how to connect the Receive Payload Data Output Interface block to the local Terminal Equip-
ment when the Slip Buffer is enabled.
FIGURE 83. INTERFACING XRT84L38 TO LOCAL TERMINAL EQUIPMENT WITH SLIP BUFFER ENABLED OR ACTS AS
FIFO
XRT84L38
RxSerClk_0
RxSer_0
Receive
RxMSync_0
RxSync_0
Payload
Data Input
Interface
Chn 0
RxTSClk_0
RxTSb[4:0]_0
Terminal
Equipment
RxSerClk_7
RxSer_7
Receive
Payload
Data Input
Interface
Chn 7
RxMSync_7
RxSync_7
RxTSClk_7
RxTSb[4:0]_7
298
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The following Figure 84 shows waveforms of the signals (RxSerClk_n, RxSer_n, RxSync_n, RxTSClk_n and
RxTSb[4:0]_n) which connecting the Receive Payload Data Output Interface block to the local Terminal Equip-
ment when the Slip Buffer is enabled.
FIGURE 84. WAVEFORMS OF THE SIGNALS THAT CONNECT THE RECEIVE PAYLOAD DATA OUTPUT INTERFACE
BLOCK TO THE LOCAL TERMINAL EQUIPMENT WHEN THE SLIP BUFFER IS ENABLED
Timeslot 0
Timeslot 5
Timeslot 6
Input Data
Timeslot 16
Input Data
RxSerClk
RxSer
RxSync(input)
RxSync(output)
RxChClk
RxChn[4:0]
Timeslot #0
Timeslot #5
Timeslot #6
Timeslot #16
RxChn[0]/RxSig
RxChn[2]/RxChn
A B C D
A B C D
A B C D
A B C D
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
RxChClk
RxChn[1]/RxFrTD
1 2 3 4 5 6 7 8
6.2.2.3 Connect the Receive Payload Data Output Interface block to the Local Terminal Equipment if
the Slip Buffer is configured as FIFO
By setting the Slip Buffer Enable [1:0] bits of the Slip Buffer Control Register to 10, the framer puts the Elastic
Buffer into FIFO mode. Receive Framer Module routes the Receive Payload Data through the First-In-First-Out
storage to the Receive Payload Data Output Interface. The XRT84L38 device uses the Recovered Receive
Line Clock internally to clock in the Receive Payload Data into the FIFO. The Terminal Equipment should pro-
vide an external 2.048MHz clock to the Receive Serial Clock input pin to latch data out from the FIFO.
It is the responsibility of the user to phase lock the input Receive Serial Clock to the Recovered Receive Line
Clock to avoid either over-run or under-run of the FIFO. The latency between writing a bit into the FIFO and
reading the same bit from it (READ and WRITE latency) is actually depth of the FIFO, which is maintained in a
programmable fashion controlled by the FIFO Latency Register (FIFOLR). The largest possible depth of the
FIFO is thirty-two bytes or one E1 frame. The default depth of the FIFO when XRT84L38 first powered up is
four bytes. The table below shows the FIFO Latency Register.
FIFO LATENCY REGISTER (FIFOL) (INDIRECT ADDRESS = 0XN0H, 0X17H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
4-0
FIFO Latency
R/W
These bits determine depth of the FIFO in terms of bytes. The largest possible
value is thirty-two bytes or one E1 frame.
In this mode, the Receive Single-Frame Synchronization signal can be either input or output depending on the
settings of the Slip Buffer Receive Synchronization Direction bit of the Slip Buffer Control Register. When the
Slip Buffer Receive Synchronization Direction bit is set to 0, the Receive Single-Frame Synchronization signal
(RxSync_n) is an. When the Slip Buffer Receive Synchronization Direction bit is set to 1,the Receive Single-
Frame Synchronization signal (RxSync_n) is an input.
299
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
If the Receive Single-Frame Synchronization signal is an output, it should pulse HIGH for one E1 bit period
(488ns) at the last bit position of each E1 frame. By triggering on the HIGH pulse on the Receive Single-frame
Synchronization signal, the Terminal Equipment can identify the end of an E1 frame and should prepare to ac-
cept payload data of the next E1 frame from the framer.
If the Receive Single-Frame Synchronization signal is an input, it should pulse HIGH for one E1 bit period
(488ns) at the first bit position (F-bit) of each E1 frame. By sampling the HIGH pulse of the Receive Single-
frame Synchronization signal, the framer should identity the beginning of an E1 frame and can send out data in
a synchronized way. It is the responsibility of the local Terminal Equipment to align the start of an E1 frame with
the Receive Single-Frame Synchronization pulse.
The Receive Multi-frame Synchronization signal should pulse HIGH for one E1 bit period (488ns) at the last bit
position of Frame number one of an E1 multi-frame. By triggering on the HIGH pulse on the Receive Multi-
frame Synchronization signal, the framer can identify the end of an E1 super-frame and should prepare to ac-
cept payload data of the next E1 super-frame from the framer.
See Figure 85 for how to connect the Receive Payload Data Output Interface block to the local Terminal Equip-
ment when the Slip Buffer is acted as FIFO.
FIGURE 85. INTERFACING XRT84L38 TO LOCAL TERMINAL EQUIPMENT WITH SLIP BUFFER ENABLED OR ACTS AS
FIFO
XRT84L38
RxSerClk_0
RxSer_0
Receive
RxMSync_0
RxSync_0
Payload
Data Input
Interface
Chn 0
RxTSClk_0
RxTSb[4:0]_0
Terminal
Equipment
RxSerClk_7
RxSer_7
Receive
Payload
Data Input
Interface
Chn 7
RxMSync_7
RxSync_7
RxTSClk_7
RxTSb[4:0]_7
300
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The following Figure 86 shows waveforms of the signals (RxSerClk_n, RxSer_n, RxSync_n, RxTSClk_n and
RxTSb[4:0]_n) which connecting the Receive Payload Data Output Interface block to the local Terminal Equip-
ment when the Slip Buffer is acted as FIFO.
FIGURE 86. WAVEFORMS OF THE SIGNALS THAT CONNECT THE RECEIVE PAYLOAD DATA OUTPUT INTERFACE
BLOCK TO THE LOCAL TERMINAL EQUIPMENT WHEN THE SLIP BUFFER IS ACTED AS FIFO
Timeslot 0
Timeslot 5
Timeslot 6
Input Data
Timeslot 16
Input Data
RxSerClk
RxSer
RxSync(input)
RxSync(output)
RxChClk
RxChn[4:0]
Timeslot #0
Timeslot #5
Timeslot #6
Timeslot #16
RxChn[0]/RxSig
RxChn[2]/RxChn
A B C D
A B C D
A B C D
A B C D
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
RxChClk
RxChn[1]/RxFrTD
1 2 3 4 5 6 7 8
6.2.3 High Speed Receive Back-plane Interface
The High-speed Back-plane Interface supports payload data to be taken from or presented to the local Termi-
nal Equipment at different data rates. In E1 mode, supported High-speed data rates are MVIP 2.048Mbit/s,
4.096Mbit/s, 8.192Mbit/s, multiplexed 16.384Mbit/s, HMVIP 16.384Mbit/s or H.100 16.384Mbit/s. The Receive
Multiplex Enable bit and the Receive Interface Mode Select [1:0] bits of the Receive Interface Control Register
(RICR) determine the Receive Back-plane Interface data rate.
The following table shows configurations of the Receive Multiplex Enable bit and the Receive Interface Mode
Select [1:0] bits of the Receive Interface Control Register (RICR).
RECEIVE INTERFACE CONTROL REGISTER (RICR) (INDIRECT ADDRESS = 0XN0H, 0X22H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
2
Receive Multi-
plex Enable
R/W
0 - The Receive Back-plane Interface block is configured to non-channel-multi-
plexed mode
1 - The Receive Back-plane Interface block is configured to channel-multiplexed
mode
1-0
Receive Inter-
face Mode
Select
R/W
When combined with the Receive Multiplex Enable bit, these bits determine the
Receive Back-plane Interface data rate.
301
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The table below shows the combinations of Receive Multiplex Enable bit and Receive Interface Mode Select
[1:0] bits and the resulting Receive Back-plane Interface data rates.
RECEIVE MULTIPLEX
ENABLE BIT
RECEIVE INTERFACE
MODE SELECT BIT 1
RECEIVE INTERFACE
MODE SELECT BIT 0
BACK-PLANE INTERFACE DATA RATE
0
0
0
0
1
1
1
1
0
0
1
1
0
0
1
1
0
1
0
1
0
1
0
1
XRT84V24 Compatible 2.048Mbit/s
MVIP 2.048Mbit/s
4.096Mbit/s
8.192Mbit/s
-
Bit Multiplexed 16.384Mbit/s
HMVIP 16.384Mbit/s
H.100 16.384Mbit/s
When the Receive Multiplex Enable bit is set to zero, the framer is configured in non-channel-multiplexed
mode. The possible data rates are XRT84V24 Compatible 2.048Mbit/s, MVIP 2.048Mbit/s, 4.096Mbit/s and
8.192Mbit/s. In non-channel-multiplexed mode, payload data of each channel are sending out from the Receive
High-speed Back-plane Interface separately. Each channel uses its own Receive Serial Clock, Receive Serial
Data, Receive Single-frame Synchronization signal and Receive Multi-frame Synchronization signal as inter-
face between the framer and the Terminal Equipment. Section 2.1.1.1, 2.1.1.2 and 2.1.1.3 provide details on
how to connect the Receive Payload Data Interface block with the local Terminal Equipment when the Back-
plane interface data rate is 2.048Mbit/s.
When the Back-plane interface data rate is MVIP 2.048Mbit/s, 4.096Mbit/s and 8.192Mbit/s, the Receive Serial
Clock, Receive Serial Data and Receive Single-frame Synchronization are all configured as inputs. The Re-
ceive Multi-frame Synchronization signal is still output. The Receive Serial Clock is configured as an input tim-
ing source for the High-speed Back-plane Interface with frequencies of 2.048 MHz, 4.096 MHz and 8.192 MHz
respectively.
The table below summaries the clock frequencies of RxSerClk_n input when the framer is operating in non-
multiplexed High-speed Back-plane mode.
RECEIVE MULTIPLEX ENABLE BIT = 0
RECEIVE INTERFACE
MODE SELECT BIT 1
RECEIVE INTERFACE MODE
SELECT BIT 0
BACK-PLANE INTERFACE DATA RATE
RXSERCLK
0
0
1
1
0
1
0
1
XRT84V24 Compatible 2.048Mbit/s
MVIP 2.048Mbit/s
4.096Mbit/s
2.048MHz
2.048 MHz
4.096 MHz
8.192 MHz
8.192Mbit/s
When the Receive Multiplex Enable bit is set to one, the framer is configured in channel-multiplexed mode. The
possible data rates are bit-multiplexed 16.384Mbit/s, HMVIP 16.384Mbit/s and H.100 16.384Mbit/s. In channel-
multiplexed mode, four channels share the Receive Serial Data, Receive Single-frame Synchronization signal
and Receive Serial Clock of one channel as interface between the framer and the Terminal Equipment. The
Receive Serial Clock runs at frequencies of 12.352 MHz or 16.384 MHz. It serves as the primary clock source
for the High-speed Back-plane Interface.
Payload and signaling data of Channel 0-3 are multiplexed onto the Receive Serial Data pin of Channel 0. Pay-
load and signaling data of Channel 4-7 are multiplexed onto the Receive Serial Data pin of Channel 4. The Re-
302
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
ceive Single-frame Synchronization signal of Channel 0 pulses HIGH at the beginning of the frame with data
from Channel 0-3 multiplexed together. The Receive Single-frame Synchronization signal of Channel 4 pulses
HIGH at the beginning of the frame with data from Channel 4-7 multiplexed together.
The table below summaries the clock frequencies of RxSerClk_n input when the framer is operating in multi-
plexed High-speed Back-plane mode.
RECEIVE MULTIPLEX ENABLE BIT = 1
RECEIVE INTERFACE MODE
SELECT BIT 1
RECEIVE INTERFACE
MODE SELECT BIT 0
BACK-PLANE INTERFACE DATA RATE
RXSERCLK
0
0
1
1
0
1
0
1
-
-
Bit-multiplexed 16.384Mbit/s
HMVIP 16.384Mbit/s
H.100 16.384Mbit/s
16.384 MHz
16.384 MHz
16.384 MHz
When the frame is running at High-speed Back-plane Interface mode other than the 2.048Mbit/s data rate, the
Receive Single-frame Synchronization signal could pulse HIGH or LOW indicating boundaries of E1 frames.
The Receive Synchronization Pulse Low bit of the Receive Interface Control Register (TICR) determines
whether the Receive Single-frame Synchronization signal is HIGH active or LOW active.
The table below shows configurations of the Receive Synchronization Pulse LOW bit of the Receive Interface
Control Register (RICR).
RECEIVE INTERFACE CONTROL REGISTER (RICR)(INDIRECT ADDRESS = 0XN0H, 0X22H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3
Receive Syn-
chronization
Pulse LOW
R/W
0 - The Receive Single-frame Synchronization signal will pulse HIGH indicating
the beginning of an E1 frame when the High-speed Back-plane Interface is run-
ning at a mode other than the 2.048Mbit/s.
1 - The Receive Single-frame Synchronization signal will pulse LOW indicating
the beginning of an E1 frame when the High-speed Back-plane Interface is run-
ning at a mode other than the 2.048Mbit/s.
Throughout the discussion of this datasheet, we assume that the Receive Single-frame Synchronization signal
pulses HIGH unless stated otherwise.
The following sections discuss details of how to operate the framer in different Back-plane interface speed
mode and how to connect the Receive Payload Data Output Interface block to the local Terminal Equipment.
6.2.3.1 E1 Receive Input Interface - MVIP 2.048 MHz
When the Receive Multiplex Enable bit is set to zero and the Receive Interface Mode Select [1:0] bits are set to
01, the Receive Back-plane interface of framer is running at a data rate of 2.048Mbit/s.
The interface consists of the following pins:
• Data input (RxSer_n)
• Receive Serial Clock Input signal (RxSerClk_n)
• Receive Single-frame Synchronization Input signal (RxSync_n)
• Receive Input Clock (RxInClk_n)
• Receive Time-slot Indication clock (RxTSClk_n)
• Receive Time Slot indicator bits (RxTSb[4:0]_n)
The Receive Back-plane interface is pumping out data through RxSer_n at an E1 equivalent data rate of
2.048Mbit/s. The local Terminal Equipment supplies a free-running 2.048MHz clock to the Receive Serial Clock
303
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
input. The Receive High-speed Back-plane Interface of the framer then sends out serial data at rising edge of
the Receive Serial Clock. The local Terminal Equipment samples the serial data at falling edge of the clock.
The Receive Single-frame Synchronization input signal (RxSync_n) should pulse HIGH at the beginning of the
256-bit frame indicating start of the frame. By sampling the HIGH pulse of the Receive Single-frame Synchroni-
zation signal, the framer can identity the beginning of an E1 frame and start pumping payload data out.
See Figure 87 below for how to interface the local Terminal Equipment with the Receive Payload Data Output
Interface block of the framer in MVIP 2.048Mbit/s mode.
FIGURE 87. INTERFACING XRT84L38 TO LOCAL TERMINAL EQUIPMENT USING MVIP 2.048MBIT/S DATA BUS
XRT84L38
RxSerClk_0 (2.048MHz)
Receive
RxSer_0
Payload
RxMSync_0
RxSync_0
Data Input
Interface
Chn 0
Terminal
Equipment
RxSerClk_7 (2.048MHz)
RxSer_7
Receive
Payload
Data Input
Interface
Chn 7
RxMSync
RxSync_7
The timing diagram of input signals to the framer when running at MVIP 2.048Mbit/s mode is shown in
Figure 88.
FIGURE 88. TIMING DIAGRAM OF INPUT SIGNALS TO THE FRAMER WHEN RUNNING AT MVIP 2.048MBIT/S
Timeslot 1
Timeslot 2
Timeslot 3
Timeslot 4
RxSerClk
RxSerClk(INV)
RxSer
F
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8
RxSync(input)
RxSync(input)
(MVIP)
RxChn[0]/RxSig
RxChn[2]/RxChn
RxChClk(INV)
A B C D
A B C D
A B C D
A B C D
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
c1 c2 c3 c4 c5
RxChn[1]/FrRxD
RxChClk
(RxSyncFrTD=1)
1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8
RxChClk
(RxSyncFrTD=1)
6.2.3.2 E1 Receive Input Interface - 4.096 MHz
304
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
(This interface mode is the same as running at 2.048 MHz. The only difference is that the Receive Serial Clock
runs two times faster at 4.096 MHz)
When the Receive Multiplex Enable bit is set to zero and the Receive Interface Mode Select [1:0] bits are set to
10, the Receive Back-plane interface of framer is running at a clock rate of 4.096MHz.
The interface consists of the following pins:
• Data input (RxSer_n)
• Receive Serial Clock Input signal (RxSerClk_n)
• Receive Single-frame Synchronization Input signal (RxSync_n)
• Receive Input Clock (RxInClk_n)
• Receive Time-slot Indication clock (RxTSClk_n)
• Receive Time Slot indicator bits (RxTSb[4:0]_n)
The Receive Back-plane interface is pumping out data through RxSer_n at an E1 equivalent data rate of
2.048Mbit/s. The local Terminal Equipment supplies a free-running 4.096MHz clock to the Receive Serial Clock
input. The Receive High-speed Back-plane Interface of the framer then sends out serial data at every other ris-
ing edge of the Receive Serial Clock. The local Terminal Equipment samples the serial data at every other fall-
ing edge of the clock.
The Receive Single-frame Synchronization input signal (RxSync_n) should pulse HIGH at the beginning of the
256-bit frame indicating start of the frame. By sampling the HIGH pulse of the Receive Single-frame Synchroni-
zation signal, the framer can identity the beginning of an E1 frame and start pumping payload data out.
See Figure 89 below for how to interface the local Terminal Equipment with the Receive Payload Data Output
Interface block of the framer in 4.096Mbit/s mode.
FIGURE 89. INTERFACING XRT84L38 TO LOCAL TERMINAL EQUIPMENT USING 4.096MBIT/S DATA BUS
XRT84L38
RxSerClk_0 (4.096MHz)
Receive
RxSer_0
Payload
RxMSync_0
RxSync_0
Data Input
Interface
Chn 0
Terminal
Equipment
RxSerClk_7 (4.096MHz)
RxSer_7
Receive
Payload
Data Input
Interface
Chn 7
RxMSync
RxSync_7
305
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The timing diagram of input signals to the framer when running at 4.096Mbit/s mode is shown in Figure 90.
FIGURE 90. TIMING DIAGRAM OF INPUT SIGNALS TO THE FRAMER WHEN RUNNING AT 4.096MBIT/S MODE
TxSerClk (4MHz)
TxSerClk (2MHz)
TxSerClk (INV)
TxSer
F
Don't Care
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
Don't care
Don't Care
1 2 3 4 5 6 7 8
TxSync(input)
TxChn[0]/TxSig
Don't Care
Don't Care
A B C D
Don't Care
A B C D
Don't Care
A B C D
A B C D
Note: The following signals are not aligned with the signals shown above. The TxChClk is derived from 1.544MHz transmit clock.
TxChClk(INV)
Don't Care
1 2 3 4 5 6 7 8
Don't Care
1 2 3 4 5 6 7 8
TxChn[1]/TxFrTD
6.2.3.3 E1 Receive Input Interface - 8.192 MHz
(This interface mode is the same as running at 2.048 MHz. The only difference is that the Receive Serial Clock
runs four times faster at 8.192MHz)
When the Receive Multiplex Enable bit is set to zero and the Receive Interface Mode Select [1:0] bits are set to
11, the Receive Back-plane interface of framer is running at a clock rate of 8.192MHz.
The interface consists of the following pins:
• Data input (RxSer_n)
• Receive Serial Clock Input signal (RxSerClk_n)
• Receive Single-frame Synchronization Input signal (RxSync_n)
• Receive Input Clock (RxInClk_n)
• Receive Time-slot Indication clock (RxTSClk_n)
• Receive Time Slot indicator bits (RxTSb[4:0]_n)
The Receive Back-plane interface is pumping out data through RxSer_n at an E1 equivalent data rate of
2.048Mbit/s. The local Terminal Equipment supplies a free-running 8.192MHz clock to the Receive Serial Clock
input. The Receive High-speed Back-plane Interface of the framer then sends out serial data at every other
four rising edge of the Receive Serial Clock. The local Terminal Equipment samples the serial data at every
other four falling edge of the clock.
The Receive Single-frame Synchronization input signal (RxSync_n) should pulse HIGH at the beginning of the
256-bit frame indicating start of the frame. By sampling the HIGH pulse of the Receive Single-frame Synchroni-
zation signal, the framer can identity the beginning of an E1 frame and start pumping payload data out.
306
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
See Figure 91 below for how to interface the local Terminal Equipment with the Receive Payload Data Output
Interface block of the framer in 8.192Mbit/s mode.
FIGURE 91. INTERFACING XRT84L38 TO LOCAL TERMINAL EQUIPMENT USING 8.192MBIT/S DATA BUS
XRT84L38
RxSerClk_0 (8.192MHz)
Receive
RxSer_0
Payload
RxMSync_0
RxSync_0
Data Input
Interface
Chn 0
Terminal
Equipment
RxSerClk_7 (8.192MHz)
RxSer_7
Receive
Payload
Data Input
Interface
Chn 7
RxMSync_7
RxSync_7
The timing diagram of input signals to the framer when running at 8.192Mbit/s mode is shown in Figure 92.
FIGURE 92. TIMING DIAGRAM OF INPUT SIGNALS TO THE FRAMER WHEN RUNNING AT 8.192MBIT/S MODE
TxSerClk (8MHz)
TxSerClk (2MHz)
TxSerClk (INV)
TxSer
F
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
Don't Care
Don't care
Don't Care
1 2 3 4 5 6 7 8
TxSync(input)
TxChn[0]/TxSig
Don't Care
Don't Care
A B C D
Don't Care
A B C D
Don't Care
A B C D
A B C D
Note: The following signals are not aligned with the signals shown above. The TxChClk is derived from 1.544MHz transmit clock.
TxChClk(INV)
Don't Care
1 2 3 4 5 6 7 8
Don't Care
1 2 3 4 5 6 7 8
TxChn[1]/TxFrTD
6.2.3.4 E1 Receive Input Interface - Bit-Multiplexed 16.384Mbit/s
When the Receive Multiplex Enable bit is set to one and the Receive Interface Mode Select [1:0] bits are set to
01, the Receive Back-plane interface of framer is running at a clock rate of 16.384MHz.
The interface consists of the following pins:
• Data input (RxSer_n)
• Receive Serial Clock Input signal (RxSerClk_n)
• Receive Single-frame Synchronization Input signal (RxSync_n)
307
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
• Receive Input Clock (RxInClk_n)
• Receive Time-slot Indication clock (RxTSClk_n)
• Receive Time Slot indicator bits (RxTSb[4:0]_n)
The Receive Back-plane Interface is pumping out data through RxSer_0 or RxSer_4 pins at 16.384Mbit/s. It
multiplexes payload and signaling data of every four channels into one data stream. Payload and signaling data
of Channel 0-3 are multiplexed onto the Receive Serial Data pin of Channel 0. Payload and signaling data of
Channel 4-7 are multiplexed onto the Receive Serial Data pin of Channel 4.
Free-running clocks of 16.384MHz are supplied to the Receive Serial Clock pin of Channel 0 and Channel 4 of
the framer. The Receive High-speed Back-plane Interface of the farmer provides data at rising edge of this Re-
ceive Serial Clock. The local Terminal Equipment then latches incoming serial data at falling edge of the clock.
The Receive High-speed Back-plane Interface maps four 2.048Mbit/s E1 data streams into this 16.384Mbit/s
data stream as described below:
1. Payload data of four channels are repeated and grouped together in a bit-interleaved way. The first payload
bit of Timeslot 0 of Channel 0 is sent first, followed by the first payload bit of Timeslot 0 of Channel 1 and 2.
The first payload bit of Timeslot 0 of Channel 3 is sent last.
After the first bits of Timeslot 0 of all four channels are sent, it comes the second bit of Timeslot 0 of Chan-
nel 0 and so on. The table below demonstrates how payload bits of four channels are mapped into the
16.384Mbit/s data stream.
FIRST OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
10
10
11
11
12
12
13
13
SECOND OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
20
20
21
21
22
22
23
23
XY: The Xth payload bit of Channel Y
2. The Receive High-speed Back-plane Interface also multiplexed signaling bits with payload bits and sent
them together through the 16.384Mbit/s data stream.
When the Receive High-speed Back-plane Interface is sending the fifth payload bit of a particular channel,
instead of sending it twice, it inserts the signaling bit A of that particular channel. Similarly, the sixth pay-
load bit of a particular channels is followed by the signaling bit B of that channel; the seventh payload bit is
followed by the signaling bit C; the eighth payload bit is followed by the signaling bit D.
The following table illustrates how payload bits and signaling bits are multiplexed together into the
16.384Mbit/s data stream.
FIFTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
50
A0
51
A1
52
A2
53
A3
308
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
SIXTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
60
B0
61
B1
62
B2
63
B3
SEVENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
70
C0
71
C1
72
C2
73
C3
EIGHTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
80
D0
81
D1
82
D2
83
D3
XY: The Xth payload bit of Channel Y
AY: The signaling bit A of Channel Y
3. After the first octets of all four channels are sent, the Receive High-speed Back-plane Interface will start
sending the second octets following the same rules of Step 1 and 2.
The Receive Single-frame Synchronization signal of Channel 0 pulses HIGH for one clock cycle at the first bit
position of the data stream with data from Channel 0-3 multiplexed together. The Receive Single-frame Syn-
chronization signal of Channel 4 pulses HIGH for one clock cycle at the first bit position of the data stream with
data from Channel 4-7 multiplexed together. By sampling the HIGH pulse of the Receive Single-frame Syn-
chronization signal, the Receive High-speed Back-plane Interface of the framer can identify the beginning of a
multiplexed frame and can start sending payload data of that frame.
309
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
See Figure 93 below for how to interface the local Terminal Equipment with the Receive Payload Data Output
Interface block of the framer in Bit-multiplexed 16.384Mbit/s mode.
FIGURE 93. INTERFACING XRT84L38 TO LOCAL TERMINAL EQUIPMENT USING 16.384 MBIT/S DATA BUS
XRT84L38
RxSerClk_0 (16.384MHz)
Receive
RxSer_0
Payload
RxMSync_0
RxSync_0
Data Input
Interface
Chn 0-3
Terminal
Equipment
RxSerClk_4 (16.384MHz)
RxSer_4
Receive
Payload
Data Input
Interface
Chn 4
RxMSync_4
RxSync_4
The Input signal timing is shown in Figure 94 below when the framer is running at Bit-Multiplexed 16.384Mbit/s
mode.
FIGURE 94. TIMING SIGNAL WHEN THE FRAMER IS RUNNING AT BIT-MULTIPLEXED 16.384MBIT/S MODE
RxSerClk (16.384MHz)
RxSerClk (INV)
56 cycles
RxSer
F0 F0 F1 F1 F2 F2 F3 F3
10 X 11 X 12 X 13 X 20 X 21
X
30
X
40
X
50 A0 51 A1 52 A2 53 A3
RxSync(input)
6.2.3.5 E1 Receive Input Interface - HMVIP 16.384Mbit/s
When the Receive Multiplex Enable bit is set to one and the Receive Interface Mode Select [1:0] bits are set to
10, the Receive Back-plane interface of framer is running at a clock rate of 16.384MHz.
The interface consists of the following pins:
• Data input (RxSer_n)
• Receive Serial Clock Input signal (RxSerClk_n)
• Receive Single-frame Synchronization Input signal (RxSync_n)
• Receive Input Clock (RxInClk_n)
• Receive Time-slot Indication clock (RxTSClk_n)
• Receive Time Slot indicator bits (RxTSb[4:0]_n)
The Receive Back-plane Interface is pumping out data through RxSer_0 or RxSer_4 pins at 16.384Mbit/s. The
Receive High-speed Back-plane Interface multiplexes payload and signaling data of every four channels into
one data stream. Payload and signaling data of Channel 0-3 are multiplexed onto the Receive Serial Data pin
310
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
of Channel 0. Payload and signaling data of Channel 4-7 are multiplexed onto the Receive Serial Data pin of
Channel 4.
Free-running clocks of 16.384MHz are supplied to the Receive Serial Clock pin of Channel 0 and Channel 4 of
the framer. The Receive High-speed Back-plane Interface of the farmer provides data at rising edge of this Re-
ceive Serial Clock. The local Terminal Equipment then latches incoming serial data at falling edge of the clock.
The Receive High-speed Back-plane Interface maps four 2.048Mbit/s E1 data streams into this 16.384Mbit/s
data stream as described below:
1. Payload data of four channels are repeated and grouped together in a byte-interleaved way. The first pay-
load bit of Timeslot 0 of Channel 0 is sent first, followed by the second payload bit of Timeslot 0 of Channel
0 and so on. After all the bits of Timeslot 0 of Channel 0 is sent repeatedly, the Terminal Equipment will
start sending the payload bits of Timeslot 0 of Channel 1 and 2. The payload bits of Timeslot 0 of Channel
3 are sent the last.
After the payload bits of Timeslot 0 of all four channels are sent, it comes the payload bits of Timeslot 1 of
Channel 0 and so on. The table below demonstrates how payload bits of four channels are mapped into
the 16.384Mbit/s data stream.
FIRST OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
10
10
20
20
30
30
40
40
THIRD OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
11
11
21
21
31
31
41
41
FIFTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
12
12
22
22
32
32
42
42
SEVENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
13
13
23
23
33
33
43
43
XY: The Xth payload bit of Channel Y
2. The Receive High-speed Back-plane Interface also multiplexed signaling bits with payload bits and sent
them together through the 16.384Mbit/s data stream.
When the Receive High-speed Back-plane Interface is sending the fifth payload bit of a particular channel,
instead of sending it twice, it inserts the signaling bit A of that particular channel. Similarly, the sixth pay-
load bit of a particular channels is followed by the signaling bit B of that channel; the seventh payload bit is
followed by the signaling bit C; the eighth payload bit is followed by the signaling bit D.
311
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The following table illustrates how payload bits and signaling bits are multiplexed together into the
16.384Mbit/s data stream.
SECOND OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
50
A0
60
B0
70
C0
80
D0
FOURTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
51
A1
61
B1
71
C1
81
D1
SIXTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
52
A2
62
B2
72
C2
82
D2
EIGHTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
53
A3
63
B3
73
C3
83
D3
XY: The Xth payload bit of Channel Y
AY: The signaling bit A of Channel Y
3. After the first octets of all four channels are sent, the Receive High-speed Back-plane Interface will start
sending the second octets following the same rules of Step 1 and 2.
The Receive Single-frame Synchronization signal should pulse HIGH for four clock cycles (the last two bit posi-
tions of the previous multiplexed frame and the first two bits of the next multiplexed frame) indicating frame
boundary of the multiplexed data stream. The Receive Single-frame Synchronization signal of Channel 0 puls-
es HIGH to identify the start of multiplexed data stream of Channel 0-3. The Receive Single-frame Synchroni-
zation signal of Channel 0 pulses HIGH to identify the start of multiplexed data stream of Channel 0-3. By sam-
pling the HIGH pulse of the Receive Single-frame Synchronization signal, the Receive High-speed Back-plane
Interface of the framer can identify the beginning of a multiplexed frame and can start sending payload data of
that frame.
312
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
See Figure 95 below for how to interface the local Terminal Equipment with the Receive Payload Data Output
Interface block of the framer in HMVIP 16.384Mbit/s mode.
FIGURE 95. INTERFACING XRT84L38 TO LOCAL TERMINAL EQUIPMENT USING 16.384MBIT/S DATA BUS
XRT84L38
RxSerClk_0 (16.384MHz)
Receive
RxSer_0
Payload
RxMSync_0
RxSync_0
Data Input
Interface
Chn 0-3
Terminal
Equipment
RxSerClk_4 (16.384MHz)
RxSer_4
Receive
Payload
Data Input
Interface
Chn 4
RxMSync_4
RxSync_4
The Input signal timing is shown in Figure 96 below when the framer is running at HMVIP 16.384Mbit/s mode.
FIGURE 96. TIMING SIGNAL WHEN THE FRAMER IS RUNNING AT HMVIP 16.384MBIT/S MODE
RxSerClk (16.384MHz)
RxSerClk (INV)
56 cycles
56 cycles
RxSer
RxSig
73 73 83 83 F0 F0 F1 F1 F2 F2 F3 F3
Start of Frame
10 10 20 20 30 30 40 40 50 A0 60 B0
Xy : X is the bit number and y is the channel number
0 0 0 0 0 0 A0A0B0B0C0C0 0 0 A2A2
12 12
52 52
53 53 63 63 73 73 83 83
A3A3B3B3C3C3D3D3
C3C3D3D3 1 1 1 1 1 1 1 1
RxSync(input)
HMVIP, negative sync
RxSync(input)
HMVIP, positive sync
6.2.3.6 E1 Receive Input Interface - H.100 16.384Mbit/s
When the Receive Multiplex Enable bit is set to one and the Receive Interface Mode Select [1:0] bits are set to
11, the Receive Back-plane interface of framer is running at H.100 16.384Mbit/s mode.
(The HMVIP mode and the H.100 mode are essential the same except for the HIGH pulse position of the Re-
ceive Single-frame Synchronization Signal)
The interface consists of the following pins:
• Data input (RxSer_n)
• Receive Serial Clock Input signal (RxSerClk_n)
• Receive Single-frame Synchronization Input signal (RxSync_n)
• Receive Input Clock (RxInClk_n)
• Receive Time-slot Indication clock (RxTSClk_n)
• Receive Time Slot indicator bits (RxTSb[4:0]_n)
313
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The Receive Back-plane Interface is pumping out data through RxSer_0 or RxSer_4 pins at 16.384Mbit/s. The
Receive High-speed Back-plane Interface multiplexes payload and signaling data of every four channels into
one data stream. Payload and signaling data of Channel 0-3 are multiplexed onto the Receive Serial Data pin
of Channel 0. Payload and signaling data of Channel 4-7 are multiplexed onto the Receive Serial Data pin of
Channel 4.
Free-running clocks of 16.384MHz are supplied to the Receive Serial Clock pin of Channel 0 and Channel 4 of
the framer. The Receive High-speed Back-plane Interface of the farmer provides data at rising edge of this Re-
ceive Serial Clock. The local Terminal Equipment then latches incoming serial data at falling edge of the clock.
The Receive High-speed Back-plane Interface maps four 2.048Mbit/s E1 data streams into this 16.384Mbit/s
data stream as described below:
1. Payload data of four channels are repeated and grouped together in a byte-interleaved way. The first pay-
load bit of Timeslot 0 of Channel 0 is sent first, followed by the second payload bit of Timeslot 0 of Channel
0 and so on. After all the bits of Timeslot 0 of Channel 0 is sent repeatedly, the Receive High-speed Back-
plane Interface will start sending the payload bits of Timeslot 0 of Channel 1 and 2. The payload bits of
Timeslot 0 of Channel 3 are sent the last.
After the payload bits of Timeslot 0 of all four channels are sent, it comes the payload bits of Timeslot 1 of
Channel 0 and so on. The table below demonstrates how payload bits of four channels are mapped into
the 16.384Mbit/s data stream.
FIRST OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
10
10
20
20
30
30
40
40
THIRD OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
11
11
21
21
31
31
41
41
FIFTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
12
12
22
22
32
32
42
42
SEVENTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
13
13
23
23
33
33
43
43
XY: The Xth payload bit of Channel Y
2. The Receive High-speed Back-plane Interface also multiplexed signaling bits with payload bits and sent
them together through the 16.384Mbit/s data stream.
314
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
When the Receive High-speed Back-plane Interface is sending the fifth payload bit of a particular channel,
instead of sending it twice, it inserts the signaling bit A of that particular channel. Similarly, the sixth pay-
load bit of a particular channels is followed by the signaling bit B of that channel; the seventh payload bit is
followed by the signaling bit C; the eighth payload bit is followed by the signaling bit D.
The following table illustrates how payload bits and signaling bits are multiplexed together into the
16.384Mbit/s data stream.
SECOND OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
50
A0
60
B0
70
C0
80
D0
FOURTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
51
A1
61
B1
71
C1
81
D1
SIXTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
52
A2
62
B2
72
C2
82
D2
EIGHTH OCTET OF 16.384MBIT/S DATA STREAM
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
53
A3
63
B3
73
C3
83
D3
XY: The Xth payload bit of Channel Y
AY: The signaling bit A of Channel Y
3. After the first octets of all four channels are sent, the Receive High-speed Back-plane Interface will start
sending the second octets following the same rules of Step 1 and 2.
The Receive Single-frame Synchronization signal should pulse HIGH for two clock cycles (the last bit position
of the previous multiplexed frame and the first bit position of the next multiplexed frame) indicating frame
boundary of the multiplexed data stream. The Receive Single-frame Synchronization signal of Channel 0 puls-
es HIGH to identify the start of multiplexed data stream of Channel 0-3. The Receive Single-frame Synchroni-
zation signal of Channel 0 pulses HIGH to identify the start of multiplexed data stream of Channel 0-3. By sam-
pling the HIGH pulse of the Receive Single-frame Synchronization signal, the Receive High-speed Back-plane
Interface of the framer can identify the beginning of a multiplexed frame and can start sending payload data of
that frame.
315
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
See Figure 97 below for how to interface the local Terminal Equipment with the Receive Payload Data Output
Interface block of the framer in HMVIP 16.384Mbit/s mode.
FIGURE 97. INTERFACING XRT84L38 TO LOCAL TERMINAL EQUIPMENT USING 16.384MBIT/S DATA BUS
XRT84L38
RxSerClk_0 (16.384MHz)
Receive
RxSer_0
Payload
RxMSync_0
RxSync_0
Data Input
Interface
Chn 0-3
Terminal
Equipment
RxSerClk_4 (16.384MHz)
RxSer_4
Receive
Payload
Data Input
Interface
Chn 4
RxMSync_4
RxSync_4
The Input signal timing is shown in Figure 98 below when the framer is running at H.100 16.384Mbit/s mode.
FIGURE 98. TIMING SIGNAL WHEN THE FRAMER IS RUNNING AT H.100 16.384MBIT/S MODE
RxSerClk (16.384MHz)
RxSerClk (INV)
56 cycles
56 cycles
RxSer
RxSig
73 73 83 83 F0 F0 F1 F1 F2 F2 F3 F3
Start of Frame
10 10 20 20 30 30 40 40 50 A0 60 B0
12 12
52 52
53 53 63 63 73 73 83 83
A3A3B3B3C3C3D3D3
Xy : X is the bit number and y is the channel number
C3C3D3D3 1 1 1 1 1 1 1 1
0 0 0 0 0 0 A0A0B0B0C0C0
0 0
A2A2
RxSync(input)
H.100, negative sync
RxSync(input)
H.100, positive sync
Delayer H.100
RxSync(input)
H.100, negative sync
RxSync(input)
H.100, positive sync
316
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
7.0 DS1 OVERHEAD INTERFACE BLOCK
The XRT84L38 has the ability to extract or insert DS1 data link information from or into the following:
• Facility Data Link (FDL) bits in ESF framing format mode
• Signaling Framing (Fs) bits in SLC®96 and N framing format mode
• Remote Signaling (R) bits in T1DM framing format mode
The source and destination of these inserted and extracted data link bits would be from either the internal
HDLC Controller or the external device accessible through DS1 Overhead Interface Block. The operation of the
Transmit Overhead Input Interface Block and the Receive Overhead Output Interface Block will be discussed
separately.
7.1 DS1 TRANSMIT OVERHEAD INPUT INTERFACE BLOCK
7.1.1 Description of the DS1 Transmit Overhead Input Interface Block
The DS1 Transmit Overhead Input Interface Block will allow an external device to be the provider of the Facility
Data Link (FDL) bits in ESF framing format mode, Signaling Framing (Fs) bits in the SLC96 and N framing for-
mat mode and Remote Signaling (R) bit in T1DM framing format mode. This interface provides interface sig-
nals and required interface timing to shift in proper data link information at proper time.
The Transmit Overhead Input Interface for a given Framer consists of two signals.
• TxOHClk_n: The Transmit Overhead Input Interface Clock Output signal
• TxOH_n: The Transmit Overhead Input Interface Input signal.
The Transmit Overhead Input Interface Clock Output pin (TxOHCLK_n) generates a rising clock edge for each
data link bit position according to configuration of the framer. The Data Link equipment interfaced to the Trans-
mit Overhead Input Interface block should update the data link bits on the TxOH_n line upon detection of the
rising edge of TxOHClk_n. The Transmit Overhead Input Interface block will sample and latch the data link bits
on the TxOH_n line on the falling edge of TxOHClk_n. The data link bits will be included and transmitted via the
outgoing DS1 frames.
The figure below shows block diagram of the DS1 Transmit Overhead Input Interface of XRT84L38.
FIGURE 99. BLOCK DIAGRAM OF THE DS1 TRANSMIT OVERHEAD INPUT INTERFACE OF THE XRT84L38
TxOH_n
Transmit
Overhead Input
Interface
To Transmit
Framer Block
TxOHClk_n
7.1.2 Configure the DS1 Transmit Overhead Input Interface module as source of the Facility Data
Link (FDL) bits in ESF framing format mode
The FDL bits in ESF framing format mode can be inserted from:
• DS1 Transmit Overhead Input Interface Block
• DS1 Transmit HDLC Controller
• DS1 Transmit Serial Input Interface.
317
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The Transmit Data Link Source Select bits of the Transmit Data Link Select Register (TDLSR) controls the in-
sertion of data link bits into the FDL bits in ESF framing format mode. The table below shows configuration of
the Transmit Data Link Source Select bits of the Transmit Data Link Select Register (TDLSR).
TRANSMIT DATA LINK SELECT REGISTER (TDLSR) (INDIRECT ADDRESS = 0XN0H, 0X0AH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1-0
Transmit Data Link
Source Select
R/W
00 - The Facility Data Link bits are inserted into the framer through either
the LAPD controller or the SLCâ96 buffer.
01 - The Facility Data Link bits are inserted into the framer through the
Transmit Serial Data input Interface via the TxSer_n pins.
10 - The Facility Data Link bits are inserted into the framer through the
Transmit Overhead Input Interface via the TxOH_n pins.
11 - The Facility Data Link bits are forced to one by the framer.
If the Transmit Data Link Source Select bits of the Transmit Data Link Select Register are set to 10, the Trans-
mit Overhead Input Interface Block becomes input source of the FDL bits.
The XRT84L38 allows the user to select bandwidth of the Facility Data Link Channel in ESF framing format
mode. The FDL can be either a 4KHz or 2KHz data link channel. The Transmit Data Link Bandwidth Select bits
of the Transmit Data Link Select Register (TDLSR) determine the bandwidth of FDL channel in ESF framing
format mode.
The table below shows configuration of the Transmit Data Link Bandwidth Select bits of the Transmit Data Link
Select Register (TDLSR).)
TRANSMIT DATA LINK SELECT REGISTER (TDLSR) (INDIRECT ADDRESS = 0XN0H, 0X0AH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
5-4
Transmit Data Link
Bandwidth Select
R/W
00 - The Facility Data Link is a 4KHz channel. All available FDL bits (first
bit of every other frame) are used as data link bits.
01 - The Facility Data Link is a 2KHz channel. Only the odd FDL bits (first
bit of frame 1, 5, 9…) are used as data link bits.
10 - The Facility Data Link is a 2KHz channel. Only the even FDL bits (first
bit of frame 3, 7, 11…) are used as data link bits.
Figure 100 below shows the timing diagram of the input and output signals associated with the DS1 Transmit
Overhead Input Interface module in ESF framing format mode.
318
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
FIGURE 100. DS1 TRANSMIT OVERHEAD INPUT INTERFACE TIMING IN ESF FRAMING FORMAT MODE
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Frame #
TxSync
TxOhClk (4kHz)
TxOh (4kHz)
TxOhClk (2kHz, odd)
TxOh (2kHz, odd)
TxOhClk (2kHz, even)
TxOh (2kHz, even)
7.1.3 Configure the DS1 Transmit Overhead Input Interface module as source of the Signaling Fram-
ing (Fs) bits in N or SLC®96 framing format mode
The Fs bits in SLC®96 and N framing format mode can be inserted from:
• DS1 Transmit Overhead Input Interface Block
• DS1 Transmit HDLC Controller
• DS1 Transmit Serial Input Interface.
The Transmit Data Link Source Select bits of the Transmit Data Link Select Register (TDLSR) controls the in-
sertion of data link bits into the Fs bits in N or SLC®96 framing format mode. The table below shows configura-
tion of the Transmit Data Link Source Select bits of the Transmit Data Link Select Register (TDLSR).
TRANSMIT DATA LINK SELECT REGISTER (TDLSR) (INDIRECT ADDRESS = 0XN0H, 0X0AH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1-0
Transmit Data Link
Source Select
R/W
00 - The Signaling Framing bits are inserted into the framer through either
the LAPD controller or the SLCâ96 buffer.
01 - The Signaling Framing bits are inserted into the framer through the
Transmit Serial Data input Interface via the TxSer_n pins.
10 - The Signaling Framing bits are inserted into the framer through the
Transmit Overhead Input Interface via the TxOH_n pins.
11 - The Signaling Framing bits are forced to one by the framer.
If the Transmit Data Link Source Select bits of the Transmit Data Link Select Register are set to 10, the Trans-
mit Overhead Input Interface Block becomes input source of the Fs bits.
319
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
Figure 101 below shows the timing diagram of the input and output signals associated with the DS1 Transmit
Overhead Input Interface module in N or SLC®96 framing format mode.
FIGURE 101. DS1 TRANSMIT OVERHEAD INPUT TIMING IN N OR SLC®96 FRAMING FORMAT MODE
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Frame #
TxSync
TxOhClk (4kHz)
TxOh (4kHz)
7.1.4 Configure the DS1 Transmit Overhead Input Interface module as source of the Remote Signal-
ing (R) bits in T1DM framing format mode
The R bits in T1DM framing format mode can be inserted from:
• DS1 Transmit Overhead Input Interface Block
• DS1 Transmit HDLC Controller
• DS1 Transmit Serial Input Interface.
The Transmit Data Link Source Select bits of the Transmit Data Link Select Register (TDLSR) controls the in-
sertion of data link bits into the R bits in T1DM framing format mode. The table below shows configuration of
the Transmit Data Link Source Select bits of the Transmit Data Link Select Register (TDLSR).
TRANSMIT DATA LINK SELECT REGISTER (TDLSR) (INDIRECT ADDRESS = 0XN0H, 0X0AH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1-0
Transmit Data Link
Source Select
R/W
00 - The Remote Signaling bits are inserted into the framer through either
the LAPD controller or the SLCâ96 buffer.
01 - The Remote Signaling bits are inserted into the framer through the
Transmit Serial Data input Interface via the TxSer_n pins.
10 - The Remote Signaling bits are inserted into the framer through the
Transmit Overhead Input Interface via the TxOH_n pins.
11 - The Remote Signaling bits are forced to one by the framer.
If the Transmit Data Link Source Select bits of the Transmit Data Link Select Register are set to 10, the Trans-
mit Overhead Input Interface Block becomes input source of the R bits. Since R bit presents in Timeslot 24 of
every T1DM frame, therefore, bandwidth of T1DM data link channel is 8KHz.
Figure 102 below shows the timing diagram of the input and output signals associated with the DS1 Transmit
Overhead Input Interface module in T1DM framing format mode.
FIGURE 102. DS1 TRANSMIT OVERHEAD INPUT INTERFACE MODULE IN T1DM FRAMING FORMAT MODE
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Frame #
TxSync
TxOhClk (T1DM)
320
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
7.2 DS1 RECEIVE OVERHEAD OUTPUT INTERFACE BLOCK
7.2.1 Description of the DS1 Receive Overhead Output Interface Block
The DS1 Receive Overhead Output Interface Block allows an external device to be the consumer of the Facility
Data Link (FDL) bits in ESF framing format mode, Signaling Framing (Fs) bits in the SLC96 and N framing for-
mat mode and Remote Signaling (R) bit in T1DM framing format mode This interface provides interface signals
and required interface timing to shift out proper data link information at proper time.
The Receive Overhead Output Interface for a given Framer consists of two signals.
• RxOHClk_n: The Receive Overhead Output Interface Clock Output signal
• RxOH_n: The Receive Overhead Output Interface Output signal.
The Receive Overhead Output Interface Clock Output pin (RxOHCLK_n) generates a rising clock edge for
each data link bit position according to configuration of the framer. The data link bits extracted from the incom-
ing T1 frames are outputted from the Receive Overhead Output Interface Output pin (RxOH_n) at the rising
edge of RxOHClk_n. The Data Link equipment should sample and latch the data link bits at the falling edge of
RxOHClk_n.
The figure below shows block diagram of the Receive Overhead Output Interface of XRT84L38.
FIGURE 103. BLOCK DIAGRAM OF THE DS1 RECEIVE OVERHEAD OUTPUT INTERFACE OF XRT84L38
RxOH_n
Receive
Overhead Output
Interface
From Receive
Framer Block
RxOHClk_n
7.2.2 Configure the DS1 Receive Overhead Output Interface module as destination of the Facility
Data Link (FDL) bits in ESF framing format mode
The FDL bits in ESF framing format mode can be extracted to:
• DS1 Receive Overhead Output Interface Block
• DS1 Receive HDLC Controller
• DS1 Receive Serial Output Interface.
The Receive Data Link Source Select bits of the Receive Data Link Select Register (RDLSR) controls the ex-
traction of FDL bits in ESF framing format mode. The table below shows configuration of the Receive Data Link
Source Select bits of the Receive Data Link Select Register (RDLSR).
321
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
RECEIVE DATA LINK SELECT REGISTER (TDLSR) (INDIRECT ADDRESS = 0XN0H, 0X0AH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1-0
Receive Data Link
Destination Select
R/W
00 - The extracted Facility Data Link bits are stored in either the LAPD con-
troller or the SLCâ96 buffer. At the same time, the extracted Facility Data
Link bits are outputted from the framer through the Receive Serial Data
Output Interface via the RxSer_n pins.
01 - The extracted Facility Data Link bits are outputted from the framer
through the Receive Serial Data Output Interface via the RxSer_n pins.
10 - The extracted Facility Data Link bits are outputted from the framer
through the Receive Overhead Output Interface via the RxOH_n pins. At
the same time, the extracted Facility Data Link bits are outputted from the
framer through the Receive Serial Data Output Interface via the RxSer_n
pins.
11 - The Facility Data Link bits are forced to one by the framer.
If the Receive Data Link Source Select bits of the Receive Data Link Select Register are set to 10, the Receive
Overhead Output Interface Block becomes Output source of the FDL bits.
The XRT84L38 allows the user to select bandwidth of the Facility Data Link Channel in ESF framing format
mode. The FDL can be either a 4KHz or 2KHz data link channel. The Receive Data Link Bandwidth Select bits
of the Receive Data Link Select Register (RDLSR) determine the bandwidth of FDL channel in ESF framing
format mode.
The table below shows configuration of the Receive Data Link Bandwidth Select bits of the Receive Data Link
Select Register (TDLSR).
RECEIVE DATA LINK SELECT REGISTER (TDLSR) (INDIRECT ADDRESS = 0XN0H, 0X0AH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
5-4
Receive Data Link
Bandwidth Select
R/W
00 - The Facility Data Link is a 4KHz channel. All available FDL bits (first
bit of every other frame) are used as data link bits.
01 - The Facility Data Link is a 2KHz channel. Only the odd FDL bits (first
bit of frame 1, 5, 9…) are used as data link bits.
10 - The Facility Data Link is a 2KHz channel. Only the even FDL bits (first
bit of frame 3, 7, 11…) are used as data link bits.
Figure 104 below shows the timing diagram of the Output and output signals associated with the DS1 Receive
Overhead Output Interface module in ESF framing format mode.
322
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
FIGURE 104. DS1 RECEIVE OVERHEAD OUTPUT INTERFACE MODULE IN ESF FRAMING FORMAT MODE
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Frame #
RxSync
RxOhClk (4kHz)
RxOh (4kHz)
RxOhClk (2kHz, odd)
RxOh (2kHz, odd)
RxOhClk (2kHz, even)
RxOh (2kHz, even)
7.2.3 Configure the DS1 Receive Overhead Output Interface module as destination of the Signaling
Framing (Fs) bits in N or SLC®96 framing format mode
The Fs bits in SLC®96 and N framing format mode can be extracted to:
• DS1 Receive Overhead Output Interface Block
• DS1 Receive HDLC Controller
• DS1 Receive Serial Output Interface.
The Receive Data Link Source Select bits of the Receive Data Link Select Register (RDLSR) controls the des-
tination of Fs bits in N or SLC®96 framing format mode. The table below shows configuration of the Receive
Data Link Source Select bits of the Receive Data Link Select Register (RDLSR).
RECEIVE DATA LINK SELECT REGISTER (TDLSR) (INDIRECT ADDRESS = 0XN0H, 0X0AH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1-0
Receive Data Link
Source Select
R/W
00 - The extracted Facility Data Link bits are stored in either the LAPD con-
troller or the SLCâ96 buffer. At the same time, the extracted Facility Data
Link bits are outputted from the framer through the Receive Serial Data
Output Interface via the RxSer_n pins.
01 - The extracted Facility Data Link bits are outputted from the framer
through the Receive Serial Data Output Interface via the RxSer_n pins.
10 - The extracted Facility Data Link bits are outputted from the framer
through the Receive Overhead Output Interface via the RxOH_n pins. At
the same time, the extracted Facility Data Link bits are outputted from the
framer through the Receive Serial Data Output Interface via the RxSer_n
pins.
11 - The Facility Data Link bits are forced to one by the framer.
If the Receive Data Link Source Select bits of the Receive Data Link Select Register are set to 10, the Receive
Overhead Output Interface Block outputs Fs bits extracted from the incoming T1 data stream.
323
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
Figure 105 below shows the timing diagram of the output signals associated with the DS1 Receive Overhead
Output Interface module in N or SLC®96 framing format mode.
FIGURE 105. DS1 RECEIVE OVERHEAD OUTPUT INTERFACE TIMING IN N OR SLC®96 FRAMING FORMAT MODE
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Frame #
RxSync
RxOhClk (4kHz)
RxOh (4kHz)
7.2.4 Configure the DS1 Receive Overhead Output Interface module as destination of the Remote
Signaling (R) bits in T1DM framing format mode
The R bits in T1DM framing format mode can be extracted to:
• DS1 Receive Overhead Output Interface Block
• DS1 Receive HDLC Controller
• DS1 Receive Serial Output Interface.
The Receive Data Link Source Select bits of the Receive Data Link Select Register (RDLSR) controls the des-
tination of R bits in T1DM framing format mode. The table below shows configuration of the Receive Data Link
Source Select bits of the Receive Data Link Select Register (RDLSR).
RECEIVE DATA LINK SELECT REGISTER (RDLSR) (INDIRECT ADDRESS = 0XN0H, 0X0AH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1-0
Receive Data Link
Source Select
R/W
00 - The extracted Facility Data Link bits are stored in either the LAPD con-
troller or the SLC®96 buffer. At the same time, the extracted Facility Data
Link bits are outputted from the framer through the Receive Serial Data
Output Interface via the RxSer_n pins.
01 - The extracted Facility Data Link bits are outputted from the framer
through the Receive Serial Data Output Interface via the RxSer_n pins.
10 - The extracted Facility Data Link bits are outputted from the framer
through the Receive Overhead Output Interface via the RxOH_n pins. At
the same time, the extracted Facility Data Link bits are outputted from the
framer through the Receive Serial Data Output Interface via the RxSer_n
pins.
11 - The Facility Data Link bits are forced to one by the framer.
If the Receive Data Link Source Select bits of the Receive Data Link Select Register are set to 10, the Receive
Overhead Output Interface Block outputs the R bits extracted from the incoming T1 data stream. Since R bit
presents in Timeslot 24 of every T1DM frame, therefore, bandwidth of T1DM data link channel is 8KHz.
324
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
Figure 106 below shows the timing diagram of the output signals associated with the DS1 Receive Overhead
Output Interface module in T1DM framing format mode.
FIGURE 106. DS1 RECEIVE OVERHEAD OUTPUT INTERFACE TIMING IN T1DM FRAMING FORMAT MODE
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Frame #
RxSync
RxOhClk (4kHz)
RxOh (4kHz)
RxOhClk (2kHz, odd)
RxOh (2kHz, odd)
RxOhClk (2kHz, even)
RxOh (2kHz, even)
325
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
8.0 E1 OVERHEAD INTERFACE BLOCK
The XRT84L38 has the ability to extract or insert E1 data link information from or into the E1 National bit se-
quence. The source and destination of these inserted and extracted data link bits would be from either the in-
ternal HDLC Controller or the external device accessible through E1 Overhead Interface Block. The operation
of the Transmit Overhead Input Interface Block and the Receive Overhead Output Interface Block will be dis-
cussed separately.
8.1 E1 TRANSMIT OVERHEAD INPUT INTERFACE BLOCK
8.1.1 Description of the E1 Transmit Overhead Input Interface Block
The E1 Transmit Overhead Input Interface Block will allow an external device to be the provider of the E1 Na-
tional bit sequence. This interface provides interface signals and required interface timing to shift in proper data
link information at proper time.
The Transmit Overhead Input Interface for a given Framer consists of two signals.
• TxOHClk_n: The Transmit Overhead Input Interface Clock Output signal
• TxOH_n: The Transmit Overhead Input Interface Input signal.
The Transmit Overhead Input Interface Clock Output pin (TxOHCLK_n) generates a rising clock edge for each
National bit that is configured to carry Data Link information according to setting of the framer. The Data Link
equipment interfaced to the Transmit Overhead Input Interface should update the data link bits on the TxOH_n
line upon detection of the rising edge of TxOHClk_n. The Transmit Overhead Input Interface block will sample
and latch the data link bits on the TxOH_n line on the falling edge of TxOHClk_n. The data link bits will be in-
cluded in and transmitted via the outgoing E1 frames.
The figure below shows block diagram of the DS1 Transmit Overhead Input Interface of XRT84L38.
FIGURE 107. BLOCK DIAGRAM OF THE E1 TRANSMIT OVERHEAD INPUT INTERFACE OF XRT84L38
TxOH_n
Transmit
Overhead Input
Interface
To Transmit
Framer Block
TxOHClk_n
8.1.2 Configure the E1 Transmit Overhead Input Interface module as source of the National Bit
Sequence in E1 framing format mode
The National Bit Sequence in E1 framing format mode can be inserted from:
• E1 Transmit Overhead Input Interface Block
• E1 Transmit HDLC Controller
• E1 Transmit Serial Input Interface
The purpose of the Transmit Overhead Input Interface is to permit Data Link equipment direct access to the
Sa4 through Sa8 National bits that are to be transported via the outbound frames. The Transmit Data Link
Source Select [1:0] bits, within the Synchronization MUX Register (SMR) determine source of the Sa4 through
Sa8 National bits to be inserted into the outgoing E1 frames.
326
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The table below shows configuration of the Transmit Data Link Source Select [1:0] bits of the Synchronization
MUX Register (SMR).
SYNCHRONIZATION MUX REGISTER (SMR) (INDIRECT ADDRESS = 0XN0H, 0X09H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3-2
Transmit Data Link
Source Select [1:0]
R/W
00 - The Sa4 through Sa8 National bits are inserted into the framer
through the Transmit Serial Data input Interface via the TxSer_n pins.
01 - The Sa4 through Sa8 National bits are inserted into the framer
through the Transmit LAPD Controller.
10 - The Sa4 through Sa8 National bits are inserted into the framer
through the Transmit Overhead Input Interface via the TxOH_n pins.
11 - The Sa4 through Sa8 National bits are inserted into the framer
through the Transmit Serial Data input Interface via the TxSer_n pins.
If the Transmit Data Link Source Select bits of the Transmit Data Link Select Register are set to 10, the Trans-
mit Overhead Input Interface Block becomes input source of the FDL bits.
The XRT84L38 allows the user to decide on the following:
• How many of the National Bits will be used to carry the Data Link information bits
• Which of these National Bits will be used to carry the Data Link information bits.
The Transmit Sa Data Link Select bits of the Transmit Signaling and Data Link Select Register (TSDLSR) de-
termine which ones of the National bits are configured as Data Link bits in E1 framing format mode. Depending
upon the configuration of the Transmit Signaling and Data Link Select Register, either of the following cases
may exists:
• None of the National bits are used to transport the Data Link information bits (That is, data link channel of
XRT84L38 is inactive).
• Any combination of between 1 and all 5 of the National bits can be selected to transport the Data Link infor-
mation bits.
The table below shows configuration of the Transmit Sa Data Link Select bits of the Transmit Signaling and Da-
ta Link Select Register (TSDLSR).
TRANSMIT SIGNALING AND DATA LINK SELECT REGISTER (TSDLSR) (INDIRECT ADDRESS = 0XN0H,
0X0AH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Transmit Sa8 Data
Link Select
R/W
0 - Source of the Sa8 Nation bit is not from the data link interface.
1 - Source the Sa8 National bit from the data link interface.
6
5
4
3
Transmit Sa7 Data
Link Select
R/W
R/W
R/W
R/W
0 - Source of the Sa7 Nation bit is not from the data link interface.
1 - Source the Sa7 National bit from the data link interface.
Transmit Sa6 Data
Link Select
0 - Source of the Sa6 Nation bit is not from the data link interface.
1 - Source the Sa6 National bit from the data link interface.
Transmit Sa5 Data
Link Select
0 - Source of the Sa5 Nation bit is not from the data link interface.
1 - Source the Sa5 National bit from the data link interface.
Transmit Sa4 Data
Link Select
0 - Source of the Sa4 Nation bit is not from the data link interface.
1 - Source the Sa4 National bit from the data link interface.
327
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
For every Sa bit that is selected to carry Data Link information, the Transmit Overhead Input Interface will sup-
ply a clock pulse, via the TxOHClk_n output pin, such that:
• The Data Link equipment interfaced to the Transmit Overhead Input Interface should update the data on the
TxOH_n line upon detection of the rising edge of TxOHClk_n.
• The Transmit Overhead Input Interface will sample and latch the data on the TxOH_n line on the falling edge
of TxOHClk_n.
Figure 108 below shows the timing diagram of the input and output signals associated with the E1 Transmit
Overhead Input Interface module in E1 framing format mode.
FIGURE 108. E1 TRANSMIT OVERHEAD INPUT INTERFACE TIMING
Frame #
TxSync(input)
TxSync(output)
TxMSync(input)
TxMSync(output)
TxOhClk
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
TxOh
TxSerClk
Timeslot 0
Sa4 Sa5 Sa6 Sa7 Sa8
Timeslot 1
MSB
LSB Si
1
A
LSB
TxSer
TxSync(out)
TxSync(in)
TxOhClk
TxOh
Sa4
Sa7 Sa8
8.2 E1 RECEIVE OVERHEAD INTERFACE
8.2.1 Description of the E1 Receive Overhead Output Interface Block
The E1 Receive Overhead Output Interface Block will allow an external device to be the consumer of the E1
National bit sequence. This interface provides interface signals and required interface timing to shift out proper
data link information at proper time.
The Receive Overhead Output Interface for a given Framer consists of two signals.
• RxOHClk_n: The Receive Overhead Output Interface Clock Output signal
• RxOH_n: The Receive Overhead Output Interface Output signal.
The Receive Overhead Output Interface Clock Output pin (RxOHCLK_n) generates a rising clock edge for
each National bit that is configured to carry Data Link information according to setting of the framer. The data
link bits extracted from the incoming E1 frames are outputted from the Receive Overhead Output Interface Out-
put pin (RxOH_n) before the rising edge of RxOHClk_n. The Data Link equipment should sample and latch the
data link bits at the rising edge of RxOHClk_n.
328
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The figure below shows block diagram of the Receive Overhead Output Interface of XRT84L38.
FIGURE 109. BLOCK DIAGRAM OF THE E1 RECEIVE OVERHEAD OUTPUT INTERFACE OF XRT84L38
RxOH_n
Receive
Overhead Output
Interface
From Receive
Framer Block
RxOHClk_n
8.2.2 Configure the E1 Receive Overhead Output Interface module as source of the National Bit
Sequence in E1 framing format mode
The National Bit Sequence in E1 framing format mode can be extracted and directed to:
• E1 Receive Overhead Output Interface Block
• E1 Receive HDLC Controller
• E1 Receive Serial Output Interface
The purpose of the Receive Overhead Output Interface is to permit Data Link equipment to have direct access
to the Sa4 through Sa8 National bits that are extracted from the incoming E1 frames. Independent of the avail-
ability of the E1 Receive HDLC Controller module, the XRT84L38 always output the received National bits
through the Receive Overhead Output Interface block.
The XRT84L38 allows the user to decide on the following:
• How many of the National Bits is used to carry the Data Link information bits
• Which of these National Bits is used to carry the Data Link information bits.
The Receive Sa Data Link Select bits of the Receive Signaling and Data Link Select Register (TSDLSR) deter-
mine which ones of the National bits are configured as Data Link bits in E1 framing format mode. Depending
upon the configuration of the Receive Signaling and Data Link Select Register, either of the following cases
may exists:
• None of the received National bits are used to transport the Data Link information bits (That is, data link
channel of XRT84L38 is inactive).
• Any combination of between 1 and all 5 of the received National bits are used to transport the Data Link infor-
mation bits.
The table below shows configuration of the Receive Sa Data Link Select bits of the Receive Signaling and Data
Link Select Register (RSDLSR).
RECEIVE SIGNALING AND DATA LINK SELECT REGISTER (RSDLSR) (INDIRECT ADDRESS = 0XN0H,
0X0CH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Receive Sa8 Data
Link Select
R/W
0 - The received Sa8 Nation bit is not extracted to the data link interface.
1 - The received Sa8 Nation bit is extracted to the data link interface.
6
5
4
Receive Sa7 Data
Link Select
R/W
R/W
R/W
0 - The received Sa7 Nation bit is not extracted to the data link interface.
1 - The received Sa7 Nation bit is extracted to the data link interface.
Receive Sa6 Data
Link Select
0 - The received Sa6 Nation bit is not extracted to the data link interface.
1 - The received Sa6 Nation bit is extracted to the data link interface.
Receive Sa5 Data
Link Select
0 - The received Sa5 Nation bit is not extracted to the data link interface.
1 - The received Sa5 Nation bit is extracted to the data link interface.
329
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
RECEIVE SIGNALING AND DATA LINK SELECT REGISTER (RSDLSR) (INDIRECT ADDRESS = 0XN0H,
0X0CH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3
Receive Sa4 Data
Link Select
R/W
0 - The received Sa4 Nation bit is not extracted to the data link interface.
1 - The received Sa4 Nation bit is extracted to the data link interface.
For every received Sa bit that is determined to carry Data Link information, the Receive Overhead Output Inter-
face will supply a clock pulse, via the RxOHClk_n output pin, such that:
• The Receive Overhead Output interface should update the data on the RxOH_n line before the rising edge of
RxOHClk_n.
• The external Data Link equipment interfaced to the Receive Overhead Output Interface will sample and latch
the data on the RxOH_n line on the rising edge of RxOHClk_n.
Figure 110 below shows the timing diagram of the output signals associated with the E1 Receive Overhead
Output Interface module in E1 framing format mode.
FIGURE 110. E1 RECEIVE OVERHEAD OUTPUT INTERFACE TIMING
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Frame #
RxSync
RxMSync
RxOhClk
RxOh
RxSerClk
Channel 0
Sa4 Sa5 Sa6 Sa7 Sa8
Channel 1
MSB
LSB Si
1
A
LSB
RxSer
RxSync
RxOhClk
RxOh
Sa4 Sa5 Sa6 Sa7 Sa8
If Sa4, SA7 and Sa8 are selected.
330
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
9.0 DS1 TRANSMIT FRAMER BLOCK
9.1 HOW TO CONFIGURE XRT84L38 TO OPERATE IN DS1 MODE
The XRT84L38 Octal T1/E1/J1 Framer supports DS1, J1 or E1 framing modes. Since J1 standard is very simi-
lar to DS1 standard with a few minor changes, the J1 framing mode is included as a sub-set of the DS1 framing
mode. All eight framers within the XRT84L38 silicon can be individually configured to support DS1, J1 or E1
framing modes.
NOTE: If transmitting section of one framer is configured to support either one of the framing modes, the receiving section
is automatically configured to support the same framing modes.
The T1/E1 Select bit of the Clock Select Register (CSR) controls which framing mode, that is, T1/J1 or E1, sup-
ported by the framer. The table below illustrates configurations of the T1/E1 Select bit of the Clock Select Reg-
ister (CSR).
CLOCK SELECT REGISTER (CSR) (INDIRECT ADDRESS = 0XN0H, 0X00H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
6
T1/E1 Select
R/W
0 - The XRT84L38 framer is running in E1 mode.
1 - The XRT84L38 framer is running in T1 mode.
Since J1 and DS1 are two very similar standards, to configure the framer to run in J1 mode, the user has to se-
lect DS1 mode by setting the T1/E1 Select bit of the Clock Select Register to 1 first.
The next step is to set the J1 CRC Calculation bit of the Framing Select Register (FSR). If this bit is set to 1, the
XRT84L38 will do CRC-6 calculation in J1 mode. That is, the CRC-6 calculation is based on the actual values
of all 4,632 bits in DS1 multi-frame including framing bits. If this bit is set to 0, the XRT84L38 will perform CRC-
6 calculation in DS1 mode. That is, the CRC-6 calculation is done based on the actual values of 4,608 payload
bits of a DS1 multi-frame and assumes that all the framing bits are one.
The table below shows configurations of the J1 CRC Calculation bit of the Framing Select Register (FSR).
FRAMING SELECT REGISTER (FSR) (INDIRECT ADDRESS = 0XN0H, 0X07H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
5
J1 CRC
Calculation
R/W
In J1 format, CRC-6 calculation is done based on the actual values of all
payload bits as well as the framing bits.
In DS1 format, CRC-6 calculation is done based on the payload bits only
while assuming all the framing bits are one.
0 - The framer performs CRC-6 calculation in DS1 format.
1 - The framer performs CRC-6 calculation in J1 format. This feature per-
mits the driver to comply with J1 standard.
The table below provides summary of how to select different operating modes for the XRT84L38 framer.
T1/E1 SELECT BIT OF CSR
Set to 1
J1 CRC CALCULATION BIT OF FSR
T1
J1
E1
Set to 0
Set to 1
-
Set to 1
Set to 0
The purpose of the DS1 Transmit Framer block is to embed and encode user payload data into frames and to
route this DS1 frame data to the Transmit DS1 LIU Interface block. Please note that the XRT84L38 has eight
(8) individual DS1 Transmit Framer blocks. Hence, the following description applies to all eight of these individ-
ual Transmit DS1 Framer blocks.
331
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The purpose of the DS1 Transmit Framer block is:
• To encode user data, inputted from the Terminal Equipment into a standard framing format.
• To provide individual data control and signaling conditioning of each DS0 channel.
• To support the transmission of HDLC messages, from the local transmitting terminal, to the remote receiving
terminal.
• To transmit indications that the local receive framer has received error frames from the remote terminal.
• To transmit alarm condition indicators to the remote terminal.
The following sections discuss functionalities of the DS1 Transmit Framer block in details. We will also describe
how to configure the XRT84L38 to transmit DS1 frames according to system requirement of users.
9.2 HOW TO CONFIGURE THE FRAMER TO TRANSMIT DATA IN VARIOUS DS1 FRAMING FORMATS
The XRT84L38 Octal T1/E1/J1 Framer supports the following DS1 framing formats:
• Super-Frame format (SF), also referred to as D4 framing
• Extended Super-Frame format (ESF)
• Non-signaling format (N)
• T1DM framing format
• SLCâ96 data link framing format, which use the Super-Frame (SF) framing structure
NOTE: If the framer is configured to transmit DS1 frames according to one particular framing format, the receiving side of
the framer is also configured to receive DS1 frames according to the same framing format. The user can set the Framing
Format Select [2:0] bits of the Framing Select Register (FSR) to determine which DS1 framing format should XRT84L38 be
configured to operate.
The table below shows configurations of the Framing Format Select [2:0] bits of the Framing Select Register
(FSR).
FRAMING SELECT REGISTER (FSR) (INDIRECT ADDRESS = 0XN0H, 0X07H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
2-0
T1 Framing Select
R/W
T1 Framing Select:
These READ/WRITE bit-fields allow the user to select one of the five T1
framing formats supported by the framer. These framing formats include
ESF, SLCâ96, SF, N and T1DM mode.
Framing
Format
Bit 2
Bit 1
Bit 0
ESF
0
1
1
1
1
X
0
0
1
1
X
0
1
0
1
SLC®96
SF
N
T1DM
NOTE: Changing of framing format automatically forces the framer to per-
form re-synchronization.
9.2.1 How to configure the framer to input framing alignment bits from different sources
In DS1 mode, different framing formats are distinguished by different patterns and functions of the framing
alignment bit (first bit of a DS1 frame). The XRT84L38 can generate the framing alignment bits internally ac-
cording to a particular framing format.
332
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
At the same time, the users can generate the framing alignment bits externally and insert them into the framer
through the Transmit Serial Data Input Interface block via the TxSer_n pin. It is the user's responsibility to
maintain the accuracy and integrity of the framing alignment bits. The user also has to make sure that the fram-
ing alignment bits are inserted into the framer at right position and right timing. However, this option is only
available when the XRT84L38 is configured to run at a normal back-plane rate of 1.544Mbit/s.
The Framing Bit Source Select bit of the Synchronization MUX Register (SMR) controls source of the framing
alignment bit. The table below shows configurations of the Framing Bit Source Select bit of the Synchronization
MUX Register (SMR).
SYNCHRONIZATION MUX REGISTER (SMR) (INDIRECT ADDRESS = 0XN0H, 0X09H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
0
Framing Bit Source
R/W
Framing Bit Source:
This READ/WRITE bit-field permits the user to determine where the fram-
ing alignment bits should be inserted.
0 - The framing alignment bits are generated and inserted by the framer
internally.
1 - If the framer is operating in normal 1.544Mbit/s mode, the framing align-
ment bits are passed through from the Transmit Serial Data Input Interface
block via the TxSer_n pin.
9.2.2 How to configure the framer to input CRC-6 bits from different sources
If the framer is configured to operate in Extended Super-frame Format, the framing bits of Frame number 2, 6,
10, 14, 18 and 22 of an ESF multi-frame are used as Cyclic Redundancy Check (CRC-6) code of the last ESF
multi-frame. The CRC-6 bits are an indicator of the link quality and could be monitored by the user to establish
error performance report.
The XRT84L38 can generate the CRC-6 bits internally by calculating the CRC check-sum of all the 4,632 bits
in DS1 multi-frame while assuming the framing bits to be one.
At the same time, the users can generate the CRC-6 bits externally and insert them into the framer through the
Transmit Serial Data Input Interface block via the TxSer_n pin. It is the user's responsibility to correctly com-
pute the CRC-6 bits according to DS1 algorithm. Also, the user has to make sure that the CRC-6 bits are in-
serted into the framer at right position and right timing. However, this option is only available when the
XRT84L38 is configured to run at a normal back-plane rate of 1.544Mbit/s.
The CRC-6 Source Select bit of the Synchronization MUX Register (SMR) controls from where to input CRC-6
bits into the framer. The table below shows configurations of the CRC-6 Source Select bit of the Synchroniza-
tion MUX Register (SMR).
SYNCHRONIZATION MUX REGISTER (SMR) (INDIRECT ADDRESS = 0XN0H, 0X09H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1
CRC-6 Source
Select
R/W
CRC-6 Source Select:
This READ/WRITE bit-field permits the user to determine where the CRC-
6 bits should be inserted.
0 - The CRC-6 bits are generated and inserted by the framer internally.
1 - If the framer is operating in normal 1.544Mbit/s mode, the CRC-6 bits
are generated by external equipment and passed through from the Trans-
mit Serial Data Input Interface block via the TxSer_n pin.
333
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
9.3 HOW TO CONFIGURE THE FRAMER TO APPLY DATA AND SIGNALING CONDITIONING TO DS1 PAYLOAD DATA
ON A PER-CHANNEL BASIS
The XRT84L38 T1/J1/E1 Octal Framer provides individual control of each of the twenty-four DS0 channels.
The user can apply data and signaling conditioning to raw DS1 payload data coming from the Terminal Equip-
ment on a per-channel basis.
The XRT84L38 framer can apply the following changes to raw DS1 PCM data coming from the Terminal Equip-
ment on a per-channel basis:
• All 8 bits of the input PCM data are inverted
• The even bits of the input PCM data are inverted
• The odd bits of the input PCM data are inverted
• The MSB of the input PCM data is inverted
• All input PCM data except the MSB are inverted
Configuration of the XRT84L38 framer to apply the above-mentioned changes to raw DS1 PCM data are con-
trolled by the Transmit Data Conditioning Select [3:0] bits of the Transmit Channel Control Register (TCCR) of
each DS0 channel.
The XRT84L38 framer can also replace the incoming raw DS1 PCM data from the Terminal Equipment with
pre-defined or user-defined codes. The XRT84L38 supports the following conditioning substitutions:
• BUSY code - an octet with hexadecimal value of 0x7F
• BUSY_TS code - an octet of pattern "111xxxxx" where "xxxxx" represents the timeslot number
• VACANT code - an octet with hexadecimal value of 0xFF
• A-law Digital Milliwatt code
• u-law Digital Milliwatt code
• IDLE code - an octet defined by the value stored in the User IDLE Code Register (UCR)
• MOOF code - MUX-Out-Of-Frame code with hexadecimal value of 0x1A
• PRBS code - an octet generated by the Pseudo-Random Bit Sequence (PRBS) Generator block of the
framer
Once again, configuration of the XRT84L38 framer to replace raw DS1 PCM data with the above-mentioned
coding schemes are controlled by the Transmit Data Conditioning Select [3:0] bits of the Transmit Channel
Control Register (TCCR) of each DS0 channel.
Finally, the XRT84L38 framer can configure any one or ones of the twenty-four DS0 channels to be D or E
channels. D channel is used primarily for data link applications. E channel is used primarily for signaling for cir-
cuit switching with multiple access configurations.
The Transmit Data Conditioning Select [3:0] bits of the Transmit Channel Control Register (TCCR) of each
channel determine whether that particular channel is configured as D or E channel.
334
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The table below illustrates configurations of the Transmit Data Conditioning Select [3:0] bits of the Transmit
Channel Control Register (TCCR).
TRANSMIT CHANNEL CONTROL REGISTER (TCCR) (INDIRECT ADDRESS = 0XN2H, 0X00H - 0X1FH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3-0
Transmit
Conditioning
Select
R/W
0000 - The input DS1 PCM data of this DS0 channel is unchanged.
0001 - All 8 bits of the input DS1 PCM data of this DS0 channel are
inverted.
0010 - The even bits of the input DS1 PCM data of this DS0 channel are
inverted.
0011 - The odd bits of the input DS1 PCM data of this DS0 channel are
inverted.
0100 - The input DS1 PCM data of this DS0 channel are replaced by the
octet stored in User IDLE Code Register (UCR).
0101 - The input DS1 PCM data of this DS0 channel are replaced by
BUSY code (0x7F).
0110 - The input DS1 PCM data of this DS0 channel are replaced by
VACANT code (0xFF).
0111 - The input DS1 PCM data of this DS0 channel are replaced by
BUSY_TS code (111xxxxx).
1000 - The input DS1 PCM data of this DS0 channel are replaced by MUX-
Out-Of-Frame (MOOF) code with value 0x1A.
1001 - The input DS1 PCM data of this DS0 channel are replaced by the
A-law digital milliwatt pattern.
1010 - The input DS1 PCM data of this DS0 channel are replaced by the u-
law digital milliwatt pattern.
1011 - The MSB bit of the input DS1 PCM data of this DS0 channel is
inverted.
1100 - All bits of the input DS1 PCM data of this DS0 channel except MSB
bit are inverted.
1101 - The input DS1 PCM data of this DS0 channel are replaced by
PRBS pattern created by the internal PRBS Generator of XRT84L38
framer.
1110 - The input DS1 PCM data of this DS0 channel is unchanged.
1111 - This channel is configured as D or E timeslot.
9.3.1 How to apply User IDLE Code to the DS1 payload data
When the Transmit Data Conditioning Select [3:0] bits of the Transmit Channel Control Register (TCCR) of a
particular DS0 channel are set to 0100, input DS1 PCM data of this DS0 channel are replaced by the octet
stored in User IDLE Code Register (UCR). The table below shows contents of the User IDLE Code Register.
USER IDLE CODE REGISTER (UCR) (INDIRECT ADDRESS = 0XN02H, 0X20H - 0X37H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-0
User IDLE Code
R/W
These READ/WRITE bit-fields permits the user store any value of IDLE
code into the framer. When the Transmit Data Conditioning Select [3:0] bits
of TCCR register of a particular DS0 channel are set to 0100, the input
DS1 PCM data are replaced by contents of this register and sent to the
Transmit LIU Interface.
Let us study the following example of applying the User IDLE Code.
335
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
In T1DM mode, the time slot 24 of a DS1 frame is used for synchronization and alarm. To generate the T1DM
framing mode externally, the user can do the following:
• Write the T1DM synchronization word (0xBC) to the User IDLE Code Register of the time slot 24.
• Set the Transmit Data Conditioning Select [3:0] bits of the TCCR of channel 24 to "0100".
Upon doing the above, the payload data of channel 24 will be replaced by the T1DM synchronization code
0xBC.
9.4 HOW TO CONFIGURE THE XRT84L38 FRAMER TO APPLY ZERO CODE SUPPRESSION TO DS1 PAYLOAD DATA
ON A PER-CHANNEL BASIS
In order to guarantee adequate clock recovery from the received PCM data, a minimum "ones density" must be
maintained. In the case of an all zero channel, that is, if all the incoming PCM data of a particular DS0 channel
from the Terminal Equipment is zero, the raw PCM data is replaced by a certain pattern that no more than fif-
teen consecutive zeros will occur. It is known as zero code suppression.
The XRT84L38 framer supports three types of zero code suppression schemes:
• AT&T Bit 7 Stuffing - an old coding method that forces Bit 7 (the second LSB of a DS0 channel) to a 1 in an
all zero channel.
• GTE Zero Code Suppression - Bit 8 (the LSB of a DS0 channel) is stuffed by 1 in non-signaling frame in an
all zero channel. Otherwise, Bit 7 is stuffed by 1 in signaling frame if the signaling bit is zero.
• DDS Zero Code Suppression - an octet with hexadecimal value of 0x98 is used to replace the input data if it
is all zero.
The Transmit Zero Code Suppression Select [1:0] bits of the Transmit Channel Control Register (TCCR) of a
particular DS0 channel is used to select which type of zero code suppression scheme is used by the framer.
The table below shows configurations of the Transmit Zero Code Suppression Select [1:0] bits of the Transmit
Channel Control Register (TCCR).
TRANSMIT CHANNEL CONTROL REGISTER (TCCR) (INDIRECT ADDRESS = 0XN2H, 0X00H - 0X1FH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
5-4
Transmit Zero
Code Suppression
Select
R/W
00 - The input DS1 PCM data of this DS0 channel is unchanged. No zero
code suppression is used.
01 - AT&T Bit 7 stuffing is used.
10 - GTE zero code suppression is used.
11 - DDS zero code suppression is used.
9.5 HOW TO CONFIGURE THE XRT84L38 FRAMER TO TRANSMIT ROBBED-BIT SIGNALING INFORMATION
The XRT84L38 T1/J1/E1 Octal Framer supports insertion of Robbed-bit Signaling information into the outgoing
DS1 frame. It also supports extraction and substitution of Robbed-bit Signaling information from the incoming
DS1 frame. The following section provides a brief overview of Robbed-bit Signaling in DS1 mode.
9.5.1 Brief Discussion of Robbed-bit Signaling in DS1 Framing Format
Signaling is required when dealing with voice and dial-up data services in DS1 applications. Traditionally, sig-
naling is provided on a dial-up telephone line, across the talk-path. Bit robbing, or stealing the least significant
bit (8th bit) in each of the twenty-four voice channels in the signaling frames allows enough bits to signal be-
tween the transmitting and receiving end. That is how the name Robbed-bit signaling comes from. These ends
can be CPE to central office (CO) for switched services, or CPE to CPE for PBX-to-PBX connections.
Signaling is used to tell the receiver where the call or route is destined. The signal is sent through switches
along the route to a distant end. Common types of signals are:
• On hook
• Off hook
• Dial tone
336
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
• Dialed digits
• Ringing cycle
• Busy tone
Robbed-bit Signaling is supported in three DS1 framing formats:
• Super-Frame (SF)
• SLC®96
• Extended Super-Frame (ESF)
In Super-Frame or SLC®96 framing mode, frame number 6 and frame number 12 are signaling frames. In
channelized DS1 applications, these frames are used to contain the signaling information. In frame number 6
and 12, the least significant bit of all twenty-four timeslots is 'robbed' to carry call state information. The bit in
frame 6 is called the A bit and the bit in frame 12 is called the B bit. The combination of A and B defines the
state of the call for the particular timeslot that these two bits are located.
FRAME NUMBER
SIGNALING BIT
6
A
B
12
In Extended Super-Frame framing mode, frame number 6, 12, 18 and 24 are signaling frames. In these frames,
the least significant bit of all twenty-four timeslots is 'robbed' to carry call state information. The bit in frame 6 is
called the A bit, the bit in frame 12 is called the B bit, the bit in frame 18 is called the C bit and the bit in frame
24 is called the D bit. The combination of A, B, C and D defines the state of the call for the particular timeslot
that these signaling bits are located.
FRAME NUMBER
SIGNALING BIT
6
A
B
C
D
12
18
24
9.5.2 Configure the framer to transmit Robbed-bit Signaling
The XRT84L38 framer supports transmission of Robbed-bit Signaling in ESF, SF and SLC®96 framing for-
mats. Signaling bits can be inserted into the outgoing DS1 frame through the following:
• Signaling data is inserted from Transmit Signaling Control Registers (TSCR) of each timeslot
• Signaling data is inserted from TxSig_n pin
• Signaling data is embedded into the input PCM data coming from the Terminal Equipment
9.5.2.1 Insert Signaling Bits from TSCR Register
The four most significant bits of the Transmit Signaling Control Register (TSCR) of each timeslot can be used
to store outgoing signaling data. The user can program these bits through microprocessor access. If the
XRT84L38 framer is configure to insert signaling bits from TSCR registers, the DS1 Transmit Framer block will
strip off the least significant bits of signaling frames and replace it with the signaling bit stored inside the TSCR
registers. The insertion of signaling bit into PCM data is done on a per-channel basis. The most significant bit
(Bit 7) of TSCR register is used to store Signaling bit A. Bit 6 is used to hold Signaling bit B. Bit 5 is used to hold
Signaling bit C. Bit 4 is used to hold Signaling bit D.
In SF or SLCâ96 mode, the user can control the XRT84L38 framer to transmit no signaling (transparent), two-
code signaling, or four-code signaling. Two-code signaling is done by substituting the least significant bit (LSB)
of the specific channel in frame 6 and 12 with the content of the Signaling bit A of the specific TSCR register.
NOTE: The user should make sure that Signaling bit A and Signaling bit B of the specific TSCR register have the same
value.
337
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
Four-code signaling is done by substituting the LSB of channel data in frame 6 with the Signaling bit A and the
LSB of channel data in frame 12 with the Signaling bit B of the specific channel's TSCR register. If sixteen-code
signaling is selected in SF format, only the Signaling bit A and Signaling bit B information are used.
In ESF mode, the user can control the XRT84L38 framer to transmit no signaling (transparent) by disable sig-
naling insertion, two-code signaling, four-code signaling or sixteen code signaling. Two-code signaling is done
by substituting the least significant bit (LSB) of the specific channel in frame 6, 12, 18 and 24 with the content
of the Signaling bit A of the specific TSCR register.
NOTE: The user should duplicate the contents of Signaling bit A of the specific TSCR register to Signaling bit B, C and D.
Four-code signaling is done by substituting the LSB of channel data in frame 6 and frame 18 with the Signaling
bit A and the LSB of channel data in frame 12 and frame 24 with the Signaling bit B of the specific channel's
TSCR register.
NOTE: The user should duplicate the contents of Signaling bit A of the specific TSCR register to Signaling bit C and dupli-
cate the contents of Signaling bit B of the specific TSCR register to Signaling bit D.
Sixteen-code signaling is implemented by substituting the LSB of channel data in frames 6, 12, 18, and 24 with
the content of Signaling bit A, B, C, and D of TSCR register respectively.
In N mode, no robbed-bit signaling is allowed and the transmit data stream remains intact.
The table below shows the four most significant bits of the Transmit Signaling Control Register.
TRANSMIT SIGNALING CONTROL REGISTER (TSCR) (INDIRECT ADDRESS = 0XN2H, 0X40H - 0X57H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Signaling Bit A
R/W
This bit is used to store Signaling Bit A that is sent as the least significant
bit of timeslot of frame number 6.
6
5
4
Signaling Bit B
Signaling Bit C
Signaling Bit D
R/W
R/W
R/W
This bit is used to store Signaling Bit B that is sent as the least significant
bit of timeslot of frame number 12.
This bit is used to store Signaling Bit C that is sent as the least significant
bit of timeslot of frame number 18.
This bit is used to store Signaling Bit D that is sent as the least significant
bit of timeslot of frame number 24.
9.5.2.2 Insert Signaling Bits from TxSig_n Pin
The XRT84L38 framer can be configure to insert signaling bits provided by external equipment through the
TxSig_n pins. This pin is a multiplexed I/O pin with two functions:
• TxTSb[0]_n - Transmit Timeslot Number Bit [0] Output pin
• TxSig_n - Transmit Signaling Input pin
When the Transmit Fractional DS1 bit of the Transmit Interface Control Register (TICR) is set to 0, this pin is
configured as TxTSb[0]_n pin, it outputs bit 0 of the timeslot number of the DS1 PCM data that is transmitting.
When the Transmit Fractional DS1 bit of the Transmit Interface Control Register (TICR) is set to 1, this pin is
configured as TxSig_n pin, it acts as an input source for the signaling bits to be transmitted in the outbound
DS1 frames.
Figure 111 below is a timing diagram of the TxSig_n input pin. Please note that the Signaling Bit A of a certain
timeslot coincides with Bit 5 of the PCM data; Signaling Bit B coincides with Bit 6 of the PCM data; Signaling Bit
C coincides with Bit 7 of the PCM data and Signaling Bit D coincides with Bit 8 (LSB) of the PCM data.
338
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
FIGURE 111. TIMING DIAGRAM OF THE TXSIG_N INPUT
Timeslot 0
Timeslot 5
Timeslot 6
Input Data
Timeslot 23
TxSerClk
TxSerClk (INV)
TxSer
Input Data
Input Data
A B C D
Input Data
A B C D
F
F
TxSig
A B C D
A B C D
The table below shows configurations of the Transmit Fractional DS1 bit of the Transmit Interface Control Reg-
ister (TICR).
TRANSMIT INTERFACE CONTROL REGISTER (TICR)(INDIRECT ADDRESS = 0XN0H, 0X20H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
4
Transmit
Fractional DS1
R/W
This READ/WRITE bit-field permits the user to determine which one of the
two functions the multiplexed I/O pin of TxTSb[0]_n/TxSig_n is spotting.
0 - This pin is configured as TxTSb[0]_n pin, it outputs bit 0 of the timeslot
number of the DS1 PCM data that is transmitting.
1 - This pin is configured as TxSig_n pin, it acts as an input source for the
signaling bits to be transmitted in the outbound DS1 frames
9.5.2.3 Insert Signaling Data from TxSer_n Pin
Depends on applications, the Terminal Equipment can embed signaling information into the DS1 PCM data
and then send the data to the XRT84L38 framer device. In this case, the user should configure the framer not
to insert any signaling data. The input DS1 PCM data will then be directed to the Transmit LIU Interface without
any modifications.
9.5.2.4 Enable Robbed-bit Signaling and Signaling Data Source Control
The Transmit Signaling Control Register (TSCR) of each channel selects source of signaling data to be insert-
ed into the outgoing DS1 frame and enables robbed-bit signaling. As we mentioned before, the signaling data
can be inserted from Transmit Signaling Control Registers (TSCR) of each timeslot, from the TxSig_n input pin
or from the TxSer_n input pin.
339
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The Transmit Signaling Data Source Select [1:0] bits of the Transmit Signaling Control Register (TSCR) deter-
mines from which sources the signaling data is inserted from. The table below shows configurations of the
Transmit Signaling Data Source Select [1:0] bits of the Transmit Signaling Control Register (TSCR).
TRANSMIT SIGNALING CONTROL REGISTER (TSCR) (INDIRECT ADDRESS = 0XN2H, 0X40H - 0X57H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1-0
Transmit Signaling
Source Select
R/W
00 - No signaling data is inserted into the input DS1 PCM data by the
framer. However, the user can embed signaling data into DS1 PCM data
before routing the PCM data into the framer.
01 - Signaling data is inserted into the input DS1 PCM data from TSCR
register of each timeslot.
10 - Signaling data is inserted into the input DS1 PCM data from the
TxSig_n input pin.
11 - No signaling data is inserted into the input DS1 PCM data by the
framer. However, the user can embed signaling data into DS1 PCM data
before routing the PCM data into the framer.
The Robbed-bit Signaling Enable bit of the Transmit Signaling Control Register (TSCR) determines whether
Robbed-bit Signaling is available. The table below shows configurations of the Robbed-bit Signaling Enable bit
of the Transmit Signaling Control Register (TSCR).
TRANSMIT SIGNALING CONTROL REGISTER (TSCR) (INDIRECT ADDRESS = 0XN2H, 0X40H - 0X57H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1-0
Robbed-bit
Signaling Enable
R/W
0 - Robbed-bit Signaling is disabled. No signaling data will be inserted into
the input PCM data no matter what the setting of the Transmit Signaling
Source Select [1:0] bits is.
1 - Signaling data is enabled and inserted into the input DS1 PCM data
according to setting of the Transmit Signaling Source Select [1:0] bits.
9.6 HOW TO CONFIGURE THE XRT84L38 FRAMER TO GENERATE AND TRANSMIT ALARMS AND ERROR INDICA-
TIONS TO REMOTE TERMINAL
The XRT84L38 T1/J1/E1 Octal Framer can be configured to monitor quality of received DS1 frames. It can
generate error indications if the local receive framer has received error frames from the remote terminal. If cor-
responding interrupt is enabled, the local microprocessor operation is interrupted by these error conditions. Up-
on microprocessor interruption, the user can intervene by looking into the error conditions.
At the same time, the user can configure the XRT84L38 framer to transmit alarms and error indications to re-
mote terminal. Different alarms and error indications will be transmitted depending on the error condition. The
section below gives a brief discussion of the error conditions and appropriate alarms that should be generated
and transmitted by the XRT84L38 framer.
9.6.1 Brief discussion of alarms and error conditions
As defined in ANSI T1.231 specification, alarm conditions are created from defects. Defects are momentary
impairments present on the DS1 trunk. If a defect is present for a sufficient amount of time (called the integra-
tion time), then the defect becomes an alarm. Once an alarm is declared, the alarm is present until after the de-
fect clears for a sufficient period of time. The time it takes to clear an alarm is called the de-integration time.
Alarms are used to detect and warn maintenance personnel of problems on the DS1 trunk. There are three
types of alarms:
• Red alarm or Service Alarm Indication (SAI) Signal
340
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
• Blue alarm or Alarm Indication Signal (AIS)
• Yellow alarm or Remote Alarm Indication (RAI) Signal
To explain the error conditions and generation of different alarms, let us create a simple DS1 system model. In
this model, a DS1 signal is sourced from the Central Office (CO) through a Repeater to the Customer Premises
Equipment (CPE). At the same time, a DS1 signal is routed from the CPE to the Repeater and back to the Cen-
tral Office. Figure 112 below shows the simple DS1 system model.
FIGURE 112. SIMPLE DIAGRAM OF DS1 SYSTEM MODEL
CO
Repeater
CPE
DS1
Transmit
Section
DS1
Receive
Section
DS1 Receive
Framer Block
DS1 Receive
Framer Block
DS1
Receive
Section
DS1
Transmit
Section
DS1 Transmit
Framer Block
DS1 Transmit
Framer Block
Simple DS1 System Model
When the E1 system runs normally, that is, when there is no Loss of Signal (LOS) or Loss of Frame (LOF) de-
tected in the line, no alarm will be generated. Sometimes, intermittent outburst of electrical noises on the line
might result in Bipolar Violation or bit errors in the incoming signals, but these errors in general will not trigger
the equipment to generate alarms. They will at most trigger the framer to generate interrupts which would
cause the local microprocessor to create performance reports of the line.
Now, consider a case in which the E1 line from the Repeater to CPE is broken or interrupted, resulting in com-
pletely loss of incoming data or severely impaired signal quality. Upon detection of Loss of Signal (LOS) or
Loss of Frame (LOF) condition, the CPE will generate an internal Red Alarm, also known as the Service Alarm
Indication. This alarm will normally trigger a microprocessor interrupt informing the user that an incoming sig-
nal failure is happening.
When the CPE is in the Red Alarm state, it will transmit the Yellow Alarm to the Repeater indicating the loss of
an incoming signal or loss of frame synchronization. This Yellow Alarm informs the Repeater that there is a
341
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
problem further down the line and its transmission is not being received at the CPE. Figure ? below illustrates
the scenario in which the E1 connection from the Repeater to CPE is broken.
FIGURE 113. GENERATION OF YELLOW ALARM BY THE CPE UPON DETECTION OF LINE FAILURE
CPE declares Red
Alarm internally
CO
Repeater
CPE
Yellow
Alarm
DS1
Transmit
Section
DS1
Receive
Section
DS1 Receive
Framer Block
DS1 Receive
Framer Block
DS1
Receive
Section
DS1
Transmit
Section
DS1 Transmit
Framer Block
DS1 Transmit
Framer Block
The DS1 line is
broken
The Repeater, upon detection of Yellow Alarm originated from the CPE, will transmit a Blue Alarm, also known
as Alarm Indication Signal (AIS) to the CO. Blue alarm is an all ones pattern indicating that the equipment is
functioning but unable to offer service due to failures originated from remote side. It is sent such that the equip-
ment downstream will not lose clock synchronization even though no meaningful data is received. Figure ? be-
342
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
low illustrates this scenario in which the Repeater is sending an AIS to CO upon detection of Yellow alarm orig-
inated from the CPE.
FIGURE 114. GENERATION OF AIS BY THE REPEATER UPON DETECTION OF YELLOW ALARM ORIGINATED BY THE
CPE
Repeater detects
CPE declares Red
Yellow alarm and
Alarm internally
generate AIS to CO
CO
Repeater
CPE
Yellow
Alarm
AIS
DS1
Transmit
Section
DS1
Receive
Section
DS1 Receive
Framer Block
DS1 Receive
Framer Block
DS1
Receive
Section
DS1
Transmit
Section
DS1 Transmit
Framer Block
DS1 Transmit
Framer Block
The DS1 line is
broken
Now let us consider another scenario in which the DS1 line between CO and the Repeater is broken. Again,
upon detection of Loss of Signal (LOS) or Loss of Frame (LOF) condition, the Repeater will generate an inter-
nal Red Alarm. This alarm will normally trigger a microprocessor interrupt informing the user that an incoming
signal failure is happening.
The Repeater will also send an all ones AIS pattern downstream to the CPE. The CPE uses the AIS signal to
recover received clock and remain in synchronization with the system. Upon detecting the incoming AIS signal,
the CPE will generate a Yellow Alarm to the Repeater to indicate the loss of incoming signal. Figure ? below il-
343
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
lustrates this scenario in which the Repeater is sending an AIS to the CPE and the CPE is sending a Yellow
Alarm back to the Repeater.
FIGURE 115. GENERATION OF YELLOW ALARM BY THE CPE UPON DETECTION OF AIS ORIGINATED BY THE
REPEATER
Repeater declares
Red Alarm
internally
CO
Repeater
CPE
Yellow
Alarm
DS1
Transmit
Section
DS1
Receive
Section
DS1 Receive
Framer Block
DS1 Receive
Framer Block
AIS
DS1
Receive
Section
DS1
Transmit
Section
DS1 Transmit
Framer Block
DS1 Transmit
Framer Block
The DS1 line is
broken
Repeater detects
Yellow alarm and
generate AIS to CO
9.6.2 How to configure the framer to transmit AIS
As we discussed in the previous section, Alarm Indication Signal (AIS) or Blue Alarm is transmitted by the inter-
mediate node to indicate that the equipment is still functioning but unable to offer services. It is an all ones (ex-
cept for framing bits) pattern which can be used by the equipment further down the line to maintain clock recov-
ery and timing synchronization.
The XRT84L38 framer can generate two types of AIS:
• Framed AIS
• Unframed AIS
Unframed AIS is an all ones pattern. If unframed AIS is sent, the equipment further down the line will be able to
maintain timing synchronization and be able to recover clock from the received AIS signal. However, due to the
lack of framing bits, the equipment farther down the line will not be able to maintain frame synchronization and
will declare Loss of Frame (LOF).
On the other hand, the payload portion of a framed AIS pattern is all ones. However, a framed AIS pattern still
has correct framing bits. Therefore, the equipment further down the line can still maintain frame synchroniza-
tion as well as timing synchronization. In this case, no LOF or Red alarm will be declared.
344
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The Transmit Alarm Indication Signal Select [1:0] bits of the Alarm Generation Register (AGR) enable the two
types of AIS transmission that are supported by the XRT84L38 framer. The table below shows configurations
of the Transmit Alarm Indication Signal Select [1:0] bits of the Alarm Generation Register (AGR).
ALARM GENERATION REGISTER (AGR)(INDIRECT ADDRESS = 0XN0H, 0X08H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3-2
Transmit AIS
Select
R/W
These READ/WRITE bit-fields allows the user to choose which one of the
two AIS pattern supported by the XRT84L38 framer will be transmitted.
00 - No AIS alarm is generated.
01 - Enable unframed AIS alarm of all ones pattern.
10 - Enable framed AIS alarm of all ones pattern except for framing bits.
11 - No AIS alarm is generated.
9.6.3 How to configure the framer to generate Red Alarm
Upon detection of Loss of Signal (LOS) or Loss of Frame (LOF) condition, the Repeater will generate an inter-
nal Red Alarm when enabled. This alarm will normally trigger a microprocessor interrupt informing the user
that an incoming signal failure is happening.
The Loss of Frame Declaration Enable bit of the Alarm Generation Register (AGR) enable the generation of
Red Alarm. The table below shows configurations of the of Frame Declaration Enable bit of the Alarm Genera-
tion Register (AGR).
ALARM GENERATION REGISTER (AGR)(INDIRECT ADDRESS = 0XN0H, 0X08H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
6
Loss of Frame
Declaration Enable
R/W
This READ/WRITE bit-field permits the framer to declare Red Alarm in
case of Loss of Frame Alignment (LOF).
When receiver module of the framer detects Loss of Frame Alignment in
the incoming data stream, it will generate a Red Alarm. The framer will
also generate an RxLOFs interrupt to notify the microprocessor that an
LOF condition is occurred. A Yellow Alarm is then returned to the remote
transmitter to report that the local receiver detects LOF.
0 - Red Alarm declaration is disabled.
1 - Red Alarm declaration is enabled.
9.6.4 How to configure the framer to transmit Yellow Alarm
Upon detection of Loss of Signal (LOS) or Loss of Frame (LOF) condition, the receiver will transmit the Yellow
Alarm back to the source indicating the loss of an incoming signal. This Yellow Alarm informs the source that
there is a problem further down the line and its transmission is not being received at the destination.
The XRT84L38 framer supports transmission of Yellow Alarm when running at the following framing formats:
• SF Mode
• ESF Mode
• N Mode
• T1DM Mode
Yellow alarm is transmitted in different forms for various framing formats. The Yellow Alarm Generation Select
[1:0] bits of the Alarm Generation Register (AGR) enable transmission of different types of Yellow alarm that
are supported by the XRT84L38 framer.
9.6.4.1 Transmit Yellow Alarm in SF Mode
345
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
In SF mode, the XRT84L38 supports transmission of Yellow Alarm in two ways. When the Yellow Alarm Gener-
ation Select [1:0] bits of the Alarm Generation Register are set to 01 or 11, the second MSB of all DS0 chan-
nels is transmitted as zero. This is Yellow Alarm for DS1 standard.
When the Yellow Alarm Generation Select [1:0] bits of the Alarm Generation Register are set to 10, the Fram-
ing bit of Frame 12 is transmitted as one. This is Yellow Alarm for J1 standard.
9.6.4.2 Transmit Yellow Alarm in ESF Mode
In ESF mode, the XRT84L38 transmits Yellow Alarm on the 4Kbit/s data link channel. The Facility Data Link
bits are sent in the pattern of eight ones followed by eight zeros. The number of repetitions of this pattern de-
pends on the duration of Yellow Alarm Generation Select [1:0] bits of the Alarm Generation Register. When
these select bits are set to 01 or 11, the following scenario will happen:
1. If Bit 0 of Yellow Alarm Generation Select forms a pulse width shorter or equal to the time required to trans-
mit 255 patterns on the 4Kbit/s data link, the alarm is transmitted for 255 patterns.
2. If Bit 0 of Yellow Alarm Generation Select forms a pulse width longer than the time required to transmit 255
patterns on the 4Kbit/s data link, the alarm continues until Bit 0 goes LOW.
3. A second pulse on Bit 0 of Yellow Alarm Generation Select during an alarm transmission resets the pattern
counter. The framer will send another 255 patterns of the Yellow Alarm.
When these select bits are set to 10, Bit 1 of the Yellow Alarm Generation Select forms a pulse that controls the
duration of Yellow Alarm transmission. The alarm continues until Bit 1 goes LOW.
When these select bits are set to 01, the following scenario will happen:
1. If Bit 0 of Yellow Alarm Generation Select forms a pulse width shorter or equal to the time required to trans-
mit 255 patterns on the 4Kbit/s data link, the alarm is transmitted for 255 patterns.
2. If Bit 0 of Yellow Alarm Generation Select forms a pulse width longer than the time required to transmit 255
patterns on the 4Kbit/s data link, the alarm continues until Bit 0 goes LOW.
3. A second pulse on Bit 0 of Yellow Alarm Generation Select during an alarm transmission resets the pattern
counter. The framer will send another 255 patterns of the Yellow Alarm.
9.6.4.3 Transmit Yellow Alarm in N Mode
In N mode, when the Yellow Alarm Generation Select [1:0] bits of the Alarm Generation Register are set to 01,
10 or 11, the second MSB of all DS0 channels is transmitted as zero.
9.6.4.4 Transmit Yellow Alarm in T1DM Mode
In T1DM mode, when the Yellow Alarm Generation Select [1:0] bits of the Alarm Generation Register are set to
01, 10 or 11, the Yellow Alarm bit (the third LSB of Timeslot 23) is set to zero.The table below shows configura-
tions of the Yellow Alarm Generation Select [1:0] bits of the Alarm Generation Register (AGR).
346
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
)
ALARM GENERATION REGISTER (AGR)(INDIRECT ADDRESS = 0XN0H, 0X08H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
5-4
Yellow Alarm
R/W
00 - Transmission of Yellow Alarm is disabled.
Generation Select
01 - The framer transmits Yellow Alarm by converting the second MSB of
all outgoing twenty-four DS0 channel into zero.
10 - The framer transmits Yellow Alarm by sending the Super-frame Align-
ment Bit (Fs) of Frame 12 as one.
11 - The framer transmits Yellow Alarm by converting the second MSB of
all outgoing twenty-four DS0 channel into zero.
N Mode:
00 - Transmission of Yellow Alarm is disabled.
01, 10 or 11 - The framer transmits Yellow Alarm by converting the second
MSB of all outgoing twenty-four DS0 channel into zero.
ESF Mode:
When the framer is in ESF mode, it transmits Yellow Alarm pattern of eight
ones followed by eight zeros (1111_1111_0000_0000) through the 4Kbit/s
data link bits.
00 - Transmission of Yellow Alarm is disabled.
01 - The following scenario will happen:
1. If Bit 0 of Yellow Alarm Generation Select forms a pulse width
shorter or equal to the time required to transmit 255 patterns on the
4Kbit/s data link, the alarm is transmitted for 255 patterns.
2. If Bit 0 of Yellow Alarm Generation Select forms a pulse width longer
than the time required to transmit 255 patterns on the 4Kbit/s data
link, the alarm continues until Bit 0 goes LOW.
3. A second pulse on Bit 0 of Yellow Alarm Generation Select during
an alarm transmission resets the pattern counter. The framer will
send another 255 patterns of the Yellow Alarm.
10 - Bit 1 of the Yellow Alarm Generation Select forms a pulse that controls
the duration of Yellow Alarm transmission. The alarm continues until Bit 1
goes LOW.
11 - The following scenario will happen:
1. If Bit 0 of Yellow Alarm Generation Select forms a pulse width
shorter or equal to the time required to transmit 255 patterns on the
4Kbit/s data link, the alarm is transmitted for 255 patterns.
2. If Bit 0 of Yellow Alarm Generation Select forms a pulse width longer
than the time required to transmit 255 patterns on the 4Kbit/s data
link, the alarm continues until Bit 0 goes LOW.
3. A second pulse on Bit 0 of Yellow Alarm Generation Select during
an alarm transmission resets the pattern counter. The framer will
send another 255 patterns of the Yellow Alarm.
T1DM Mode:
00 - Transmission of Yellow Alarm is disabled.
01, 10 or 11 - The framer transmits Yellow Alarm by setting the Yellow
Alarm bit (Y-bit) to zero.
347
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
10.0 DS1 RECEIVE FRAMER BLOCK
10.1 HOW TO CONFIGURE XRT84L38 TO OPERATE IN DS1 MODE
The XRT84L38 Octal T1/E1/J1 Framer supports DS1, J1 or E1 framing modes. Since J1 standard is very simi-
lar to DS1 standard with a few minor changes, the J1 framing mode is included as a sub-set of the DS1 framing
mode. All eight framers within the XRT84L38 silicon can be individually configured to support DS1, J1 or E1
framing modes.
NOTE: If transmitting section of one framer is configured to support either one of the framing modes, the receiving section
is automatically configured to support the same framing modes.
The T1/E1 Select bit of the Clock Select Register (CSR) controls which framing mode supported by the framer.
The table below illustrates configurations of the T1/E1 Select bit of the Clock Select Register (CSR).
CLOCK SELECT REGISTER (CSR) (INDIRECT ADDRESS = 0XN0H, 0X00H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
6
T1/E1 Select
R/W
0 - The XRT84L38 framer is running in E1 mode.
1 - The XRT84L38 framer is running in T1 mode.
Since J1 and DS1 are two very similar standards, to configure the framer to run in J1 mode, the user has to se-
lect DS1 mode by setting the T1/E1 Select bit of the Clock Select Register to 1 first.
The next step is to set the J1 CRC Calculation bit of the Framing Select Register (FSR). If this bit is set to 1, the
XRT84L38 will do CRC-6 calculation in J1 mode. That is, the CRC-6 calculation is based on the actual values
of all 4,632 bits in DS1 multi-frame including framing bits. If this bit is set to 0, the XRT84L38 will perform CRC-
6 calculation in DS1 mode. That is, the CRC-6 calculation is done based on the actual values of 4,608 payload
bits of a DS1 multi-frame and assumes that all the framing bits are one.
The table below shows configurations of the J1 CRC Calculation bit of the Framing Select Register (FSR).
FRAMING SELECT REGISTER (FSR) (INDIRECT ADDRESS = 0XN0H, 0X07H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
5
J1 CRC
Calculation
R/W
In J1 format, CRC-6 calculation is done based on the actual values of all
payload bits as well as the framing bits.
In DS1 format, CRC-6 calculation is done based on the payload bits only
while assuming all the framing bits are one.
0 - The framer will perform CRC-6 calculation in DS1 format.
1 - The framer will perform CRC-6 calculation in J1 format. This feature
permits the driver to comply with J1 standard.
The table below provides summary of how to select different operating modes for the XRT84L38 framer.
J1 CRC CALCULATION BIT OF
T1/E1 SELECT BIT OF CSR
FSR
T1
J1
E1
Set to 1
Set to 1
Set to 0
Set to 0
Set to 1
-
The purpose of the DS1 Receive Framer block is to accept framed DS1 data from the Receive DS1 LIU Inter-
face block. The Receive Framer block will identify frame boundary and establish framing alignment synchroni-
zation of the incoming DS1 frame. The Receive Framer Block will then decode and extract user payload data
348
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
from received frames Please note that the XRT84L38 has eight (8) individual DS1 Transmit Framer blocks.
Hence, the following description applies to all eight of these individual Transmit DS1 Framer blocks.
The purpose of the DS1 Receive Framer block is:
• To identify frame boundary and establish framing alignment synchronization.
• To decode user data, inputted from the Receive DS1 LIU Interface block to the Terminal Equipment.
• To provide individual data control and signaling conditioning of each DS0 channel.
• To support the receiving and extraction of HDLC messages, from the remote receiving terminal.
• To detect error conditions and generate indications and interrupts to notify the user that the local receive
framer has received error frames from the remote terminal.
• To receive and decode alarm condition indicators from the remote terminal.
The following sections discuss functionalities of the DS1 Receive Framer block in details.
10.2 HOW TO CONFIGURE THE FRAMER TO RECEIVE DATA IN VARIOUS DS1 FRAMING FORMATS
The XRT84L38 Octal T1/E1/J1 Framer supports the following DS1 framing formats:
• Super-Frame format (SF), also referred to as D4 framing
• Extended Super-Frame format (ESF)
• Non-signaling format (N)
• T1DM framing format
• SLC®96 data link framing format, which use the Super-Frame (SF) framing structure
NOTE: If the framer is configured to receive DS1 frames according to one particular framing format, the transmitting side of
the framer is also configured to transmit DS1 frames according to the same framing format.
The user can set the Framing Format Select [2:0] bits of the Framing Select Register (FSR) to determine which
DS1 framing format should XRT84L38 be configured to operate.
The table below shows configurations of the Framing Format Select [2:0] bits of the Framing Select Register
(FSR).
FRAMING SELECT REGISTER (FSR) (INDIRECT ADDRESS = 0XN0H, 0X07H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
2-0
T1 Framing Select
R/W
These READ/WRITE bit-fields allow the user to select one of the five T1
framing formats supported by the framer. These framing formats include
ESF, SLC®96, SF, N and T1DM mode.
Framing
Format
Bit 2
Bit 1
Bit 0
ESF
0
1
1
1
1
X
0
0
1
1
X
0
1
0
1
SLC®96
SF
N
T1DM
NOTE: Changing of framing format will automatically force the framer to
perform re-synchronization.
10.3 HOW TO CONFIGURE THE FRAMER TO APPLY DATA AND SIGNALING CONDITIONING TO RECEIVED DS1 PAY-
LOAD DATA ON A PER-CHANNEL BASIS
349
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The XRT84L38 T1/J1/E1 Octal Framer provides individual control of each of the twenty-four DS0 channels.
The user can apply data and signaling conditioning to the received DS1 payload data coming from the DS1 LIU
Receive Block on a per-channel basis.
The XRT84L38 framer can apply the following changes to the received DS1 payload data coming from the Ter-
minal Equipment on a per-channel basis:
• All 8 bits of the received payload data are inverted
• The even bits of the received payload data are inverted
• The odd bits of the received payload data are inverted
• The MSB of the received payload data is inverted
• All received payload data except the MSB are inverted
Configurations of the XRT84L38 framer to apply the above-mentioned changes to the received DS1 PAYLOAD
data are controlled by the Receive Data Conditioning Select [3:0] bits of the Receive Channel Control Register
(RCCR) of each DS0 channel.
The XRT84L38 framer can also replace the incoming DS1 payload data from the DS1 LIU Receive Block with
pre-defined or user-defined codes. The XRT84L38 supports the following conditioning substitutions:
• BUSY code - an octet with hexadecimal value of 0x7F
• BUSY_TS code - an octet of pattern "111xxxxx" where "xxxxx" represents the timeslot number
• VACANT code - an octet with hexadecimal value of 0xFF
• A-law Digital Milliwatt code
• u-law Digital Milliwatt code
• IDLE code - an octet defined by the value stored in the User IDLE Code Register (UCR)
• MOOF code - MUX-Out-Of-Frame code with hexadecimal value of 0x1A
• PRBS code - an octet generated by the Pseudo-Random Bit Sequence (PRBS) Generator block of the
framer
Once again, configuration of the XRT84L38 framer to replace the received DS1 payload data with the above-
mentioned coding schemes are controlled by the Receive Data Conditioning Select [3:0] bits of the Receive
Channel Control Register (RCCR) of each DS0 channel.
Finally, the XRT84L38 framer can configure any one or ones of the twenty-four DS0 channels to be D or E
channels. D channel is used primarily for data link applications. E channel is used primarily for signaling for cir-
cuit switching with multiple access configurations.
The Receive Data Conditioning Select [3:0] bits of the Receive Channel Control Register (RCCR) of each
channel determine whether that particular channel is configured as D or E channel.
350
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The table below illustrates configurations of the Receive Data Conditioning Select [3:0] bits of the Receive
Channel Control Register (RCCR).
RECEIVE CHANNEL CONTROL REGISTER (RCCR) (INDIRECT ADDRESS = 0XN2H, 0X60H - 0X7FH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3-0
Receive
Conditioning
Select
R/W
0000 - The received DS1 payload data of this DS0 channel is unchanged.
0001 - All 8 bits of the input DS1 payload data of this DS0 channel are
inverted.
0010 - The even bits of the input DS1 payload data of this DS0 channel are
inverted.
0011 - The odd bits of the input DS1 payload data of this DS0 channel are
inverted.
0100 - The input DS1 payload data of this DS0 channel are replaced by
the octet stored in User IDLE Code Register (UCR).
0101 - The input DS1 payload data of this DS0 channel are replaced by
BUSY code (0x7F).
0110 - The input DS1 payload data of this DS0 channel are replaced by
VACANT code (0xFF).
0111 - The input DS1 payload data of this DS0 channel are replaced by
BUSY_TS code (111xxxxx).
1000 - The input DS1 payload data of this DS0 channel are replaced by
MUX-Out-Of-Frame (MOOF) code with value 0x1A.
1001 - The input DS1 payload data of this DS0 channel are replaced by
the A-law digital milliwatt pattern.
1010 - The input DS1 payload data of this DS0 channel are replaced by
the u-law digital milliwatt pattern.
1011 - The MSB bit of the input DS1 payload data of this DS0 channel is
inverted.
1100 - All bits of the input DS1 payload data of this DS0 channel except
MSB bit are inverted.
1101 - The input DS1 payload data of this DS0 channel are replaced by
PRBS pattern created by the internal PRBS Generator of XRT84L38
framer.
1110 - The input DS1 payload data of this DS0 channel is unchanged.
1111 - This channel is configured as D or E timeslot.
When the Receive Data Conditioning Select [3:0] bits of the Receive Channel Control Register (RCCR) of a
particular DS0 channel are set to 0100, the received DS1 payload data of this DS0 channel are replaced by the
octet stored in the Receive User IDLE Code Register (RUCR). The table below shows contents of the Receive
User IDLE Code Register.
RECEIVE USER IDLE CODE REGISTER (UCR) (INDIRECT ADDRESS = 0XN02H, 0X80H - 0X97H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-0
User IDLE Code
R/W
These READ/WRITE bit-fields permits the user store any value of IDLE
code into the framer. When the Receive Data Conditioning Select [3:0] bits
of RCCR register of a particular DS0 channel are set to 0100, the received
DS1 payload data are replaced by contents of this register and sent to the
Terminal Equipment.
351
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
10.4 HOW TO CONFIGURE THE XRT84L38 FRAMER TO APPLY ZERO CODE SUPPRESSION TO RECEIVED DS1 PAY-
LOAD DATA ON A PER-CHANNEL BASIS
In order to guarantee adequate clock recovery from the received PCM data, a minimum "ones density" must be
maintained. In the case of an all zero channel, that is, if all the incoming PCM data of a particular DS0 channel
from the Terminal Equipment is zero, the raw PCM data is replaced by a certain pattern that no more than fif-
teen consecutive zeros will occur. It is known as zero code suppression.
In the receive end, the user needs to know what type of zero code suppression scheme is applied on the re-
ceiving data. In this way, a correct decoding method or the reverse of zero code suppression can be done to
extract the payload data from the DS1 LIU Receive Block.
The XRT84L38 framer supports three types of zero code suppression schemes:
• AT&T Bit 7 Stuffing - an old coding method that forces Bit 7 (the second LSB of a DS0 channel) to a 1 in an
all zero channel.
• GTE Zero Code Suppression - Bit 8 (the LSB of a DS0 channel) is stuffed by 1 in non-signaling frame in an
all zero channel. Otherwise, Bit 7 is stuffed by 1 in signaling frame if the signaling bit is zero.
• DDS Zero Code Suppression - an octet with hexadecimal value of 0x98 is used to replace the input data if it
is all zero.
The Receive Zero Code Suppression Select [1:0] bits of the Receive Channel Control Register (RCCR) of a
particular DS0 channel is used to select which type of zero code suppression scheme is applied to the re-
ceived DS1 payload data. The table below shows configurations of the Receive Zero Code Suppression Select
[1:0] bits of the Receive Channel Control Register (RCCR).
RECEIVE CHANNEL CONTROL REGISTER (RCCR) (INDIRECT ADDRESS = 0XN2H, 0X60H - 0X7FH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
5-4
Receive Zero Code
Suppression
Select
R/W
00 - The received DS1 PAYLOAD data of this DS0 channel is unchanged.
No zero code suppression is used.
01 - AT&T Bit 7 stuffing is used.
10 - GTE zero code suppression is used.
11 - DDS zero code suppression is used.
10.5 HOW TO CONFIGURE THE XRT84L38 FRAMER TO EXTRACT ROBBED-BIT SIGNALING INFORMATION
The XRT84L38 T1/J1/E1 Octal Framer supports insertion of Robbed-bit Signaling information into the outgoing
DS1 frame. It also supports extraction and substitution of Robbed-bit Signaling information from the incoming
DS1 frame. The following section describes how does the XRT84L38 framer extract and substitute Robbed-bit
Signaling in DS1 mode.
10.5.1 Configure the framer to receive and extract Robbed-bit Signaling
The XRT84L38 framer supports receiving and extraction of Robbed-bit Signaling in ESF, SF and SLC®96
framing formats. The Receive Signaling Extraction Control [1:0] bits of the Receive Signaling Control Register
(RSCR) of each channel select either:
• No signaling extraction
• Two-code signaling
• Four-code signaling or
• Sixteen-code signaling
In SF or SLCâ96 mode, the Receive Signaling Extraction Control [1:0] bits can select no signaling (transpar-
ent), two-code signaling, or four-code signaling. Two-code signaling decoding is done by stripping the least sig-
nificant bit (LSB) of the specific channel in frame 6 and 12 and stores it into the Signaling Bit A position of
RSRA register array. Four-code signaling is done by stripping the LSB of channel data in frame 6 and the LSB
of channel data in frame 12, and store them into Signaling Bit A and Signaling Bit B position of RSRA register
352
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
array respectively. If 16-code signaling is selected in SF format, only the Signaling bit A and Signaling Bit B po-
sitions are filled.
In ESF mode, the Receive Signaling Extraction Control [1:0] bits can select no signaling (transparent), two-
code signaling, four-code, or sixteen-code signaling. Two-code signaling decoding is done by stripping the
least significant bit (LSB) of the specific channel in frame 6, 12, 18 and 24 and stores it into the Signaling Bit A
position of RSRA register array. Four-code signaling is done by stripping the LSB of channel data in frame 6
and frame 18 and the LSB of channel data in frame 12 and 24, and store them into Signaling Bit A and Signal-
ing Bit B position of RSRA register array respectively. Sixteen-code signaling is implemented by stripping the
LSB of channel data in frames 6, 12, 18, and 24 and stores them into the Signaling Bit A, Signaling Bit B, Sig-
naling Bit C and Signaling Bit D position of RSRA register array respectively.
The table below shows configurations of the Receive Signaling Extraction Control [1:0] bits of the Receive Sig-
naling Control Register.
RECEIVE SIGNALING CONTROL REGISTER (RSCR) (INDIRECT ADDRESS = 0XN2H, 0XA0H - 0XB7H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1-0
Signaling
Extraction Control
R/W
00 - The XRT84L38 framer does not extract signaling information from
incoming DS1 payload data.
01 - The XRT84L38 framer extracts sixteen-code signaling information
from incoming DS1 payload data.
10 - The XRT84L38 framer extracts four-code signaling information from
incoming DS1 payload data.
11 - The XRT84L38 framer extracts two-code signaling information from
incoming DS1 payload data.
Upon receiving and extraction of signaling bits from the incoming DS1 frames, the XRT84L38 framer compares
the signaling bits with the previously received ones. If there is a change of signaling data, a Signaling Update
(SIG) interrupt request may be generated at the end of a DS1 multi-frame. The user can thus be notified of a
Change of Signaling Data event.
To enable the Signaling Update interrupt, the Signaling Change Interrupt Enable bit of the Framer Interrupt En-
able Register (FIER) has to be set. In addition, the T1/E1 Framer Interrupt Enable bit of the Block Interrupt En-
able Register (BIER) needs to be one.
The table below shows configurations of the Signaling Change Interrupt Enable bit of the Framer Interrupt En-
able Register.
FRAMER INTERRUPT ENABLE REGISTER (FIER) (INDIRECT ADDRESS = 0XNAH, 0X05H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
5
Signaling Change
Interrupt Enable
R/W
0 - The Signaling Update interrupt is disabled.
1 - The Signaling Update interrupt is enabled.
353
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The table below shows configurations of the T1/E1 Framer Interrupt Enable bit of the Block Interrupt Enable
Register.
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X00H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1
T1/E1 Framer
Interrupt Enable
R/W
0 - Every interrupt generated by the Framer Interrupt Status Register
(FISR) is disabled.
1 - Every interrupt generated by the Framer Interrupt Status Register
(FISR) is enabled.
When these interrupt enable bits are set and the signaling information received is changed, the DS1 Receive
Framer block will set the Signaling Updated status bit of the Framer Interrupt Status Register (FISR) to one.
This status indicator is valid until the Framer Interrupt Status Register is read. Reading this register clears the
associated interrupt if Reset-Upon-Read is selected in Interrupt Control Register (ICR). Otherwise, a write-to-
clear operation by the microprocessor is required to reset these status indicators.
The table below shows the Signaling Update status bits of the Framer Interrupt Status Register.
FRAMER INTERRUPT STATUS REGISTER (FISR) (INDIRECT ADDRESS = 0XNAH, 0X04H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
5
Signaling Updated
RUR /
WC
0 - There is no change of signaling information in the incoming DS1 pay-
load data.
1 - There is change of signaling information in the incoming DS1 payload
data.
Now, there is only one problem remains. Since there are twenty-four DS0 channels in DS1, how do we know
signaling information of which channel is changed?
To solve this problem, the XRT84L38 provides three 8-bit Signaling Change Registers to indicate the chan-
nel(s) which signaling data change had occurred over the last DS1 multi-frame period. Each bit of the Signaling
Change Registers represents one timeslot of the DS1 frame. If any particular bit is zero, it means there is no
change of signaling data occurred in that particular timeslot over the last DS1 multi-frame period. If any partic-
ular bit is one, it means there is change of signaling data occurred over the last DS1 multi-frame period.
The table below shows configurations of the Signaling Change Registers.
SIGNALING CHANGE REGISTERS (SCR) (INDIRECT ADDRESS = 0XN0H, 0X0DH - 0X0FH)
LOCATION \ BIT
0XN0H - 0X0DH
0xn0H - 0x0EH
0xn0H - 0x0FH
BIT 7
CH 0
Ch 8
BIT 6
CH 1
BIT 5
CH 2
BIT 4
CH 3
BIT 3
CH 4
BIT 2
CH 5
BIT 1
CH 6
BIT 0
CH 7
Ch 9
Ch 10
Ch 18
Ch 11
Ch 19
Ch 12
Ch 20
Ch 13
Ch 21
Ch 14
Ch 22
Ch 15
Ch 23
Ch 16
Ch 17
By reading contents of the Signaling Update status bits of the Framer Interrupt Status Register and the Signal-
ing Change Registers, the user can clearly identify which one(s) of the twenty-four DS0 channels has changed
signaling information over the last multi-frame period.
Depending on configurations of the XRT84L38 framer, the signaling bits can be extracted from the incoming
DS1 frame and direct to all or any one of the following destinations:
• Signaling data is stored to Receive Signaling Register Array (RSRA) of each channel
• Signaling data is sent to the Terminal Equipment through the Receive Signaling Output pin (RxSig_n)
354
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
• Signaling data is embedded into the output PCM data sending towards the Terminal Equipment through the
Receive Serial Output pin (RxSer_n)
The follow sections discuss how to configure the XRT84L38 framer to extract signaling information bits and
send them to different destinations.
10.5.1.1 Store Signaling Bits into RSRA Register Array
The four least significant bits of the Receive Signaling Register Array (RSRA) of each timeslot can be used to
store received signaling data. The user can read these bits through microprocessor access. If the XRT84L38
framer is configure to extract signaling bits from incoming DS1 payload data, the DS1 Receive Framer block
will strip off the least significant bits of signaling frames and store them into appropriate locations of the RSRA.
The extraction of signaling bit from DS1 PCM data is done on a per-channel basis. The Bit 3 of RSRA register
is used to hole Signaling bit A. Bit 2 is used to hold Signaling bit B. Bit 1 is used to hold Signaling bit C. Bit 0 is
used to hold Signaling bit D.
The table below shows the four least significant bits of the Receive Signaling Register Array.
RECEIVE SIGNALING REGISTER ARRAY (RSRA) (INDIRECT ADDRESS = 0XN4H, 0X00H - 0X17H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3
Signaling Bit A
R/W
This bit is used to store Signaling Bit A that is received and extracted as
the least significant bit of timeslot of frame number 6.
2
1
0
Signaling Bit B
Signaling Bit C
Signaling Bit D
R/W
R/W
R/W
This bit is used to store Signaling Bit B that is received and extracted as
the least significant bit of timeslot of frame number 12.
This bit is used to store Signaling Bit C that is received and extracted as
the least significant bit of timeslot of frame number 18.
This bit is used to store Signaling Bit D that is received and extracted as
the least significant bit of timeslot of frame number 24.
10.5.1.2 Outputting Signaling Bits through RxSig_n Pin
The XRT84L38 framer can be configure to output extracted signaling bits to external equipment through the
RxSig_n pins. This pin is a multiplexed I/O pin with two functions:
• RxTSb[0]_n - Receive Timeslot Number Bit [0] Output pin
• RxSig_n - Receive Signaling Output pin
When the Receive Fractional DS1 bit of the Receive Interface Control Register (TICR) is set to 0, this pin is
configured as RxTSb[0]_n pin, it outputs bit 0 of the timeslot number of the DS1 PCM data that is receiving.
When the Receive Fractional DS1 bit of the Receive Interface Control Register (TICR) is set to 1, this pin is
configured as RxSig_n pin, it acts as an output source for the signaling bits to be received in the inbound DS1
frames.
The table below shows configurations of the Receive Fractional DS1 bit of the Receive Interface Control Regis-
ter (TICR).
RECEIVE INTERFACE CONTROL REGISTER (TICR) (INDIRECT ADDRESS = 0XN0H, 0X20H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
4
Receive Fractional
DS1
R/W
This READ/WRITE bit-field permits the user to determine which one of the
two functions the multiplexed I/O pin of RxTSb[0]_n/RxSig_n is spotting.
0 - This pin is configured as RxTSb[0]_n pin, it outputs bit 0 of the timeslot
number of the DS1 PCM data that is receiving.
1 - This pin is configured as RxSig_n pin, it acts as an output source for the
signaling bits to be received in the inbound DS1 frames
355
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
Figure 116 below is a timing diagram of the RxSig_n output pin. Please note that the Signaling Bit A of a cer-
tain timeslot coincides with Bit 3 of the Received serial output data; Signaling Bit B coincides with Bit 2 of the
Received serial output data; Signaling Bit C coincides with Bit 1 of the Received serial output data and Signal-
ing Bit D coincides with Bit 0 of the Received serial output data.
FIGURE 116. TIMING DIAGRAM OF THE RXSIG_N OUTPUT PIN
Timeslot 0
Timeslot 5
Timeslot 6
Input Data
Timeslot 16
Input Data
RxSerClk
RxSer
RxSig
A B C D
A B C D
A B C D
A B C D
The Receive Signaling Output Enable bit of the Receive Signaling Control Register (RSCR) determines wheth-
er the extracted signaling bits will be sent through the Receive Signaling Output pin (RxSig_n) to external
equipments. The table below shows configurations of the Receive Signaling Output Enable bit of the Receive
Signaling Control Register.
RECEIVE SIGNALING CONTROL REGISTER (RSCR) (INDIRECT ADDRESS = 0XN2H, 0XA0H - 0XB7H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
5
Receive Signaling
Output Enable
R/W
0 - The XRT84L38 framer will not send extracted signaling bits from the
incoming DS1 payload data to external equipment through the Receive
Signaling Output pin (RxSig_n).
1 - The XRT84L38 framer will send extracted signaling bits from the incom-
ing DS1 payload data to external equipment through the Receive Signaling
Output pin (RxSig_n).
10.5.1.3 Send Signaling Data through RxSer_n Pin
As mentioned in the above sections, signaling information embedded in the incoming DS1 PCM data can be
sent to either the RSRA register array and/or sent through the Receive Signaling Output pin, at the same time,
the signaling data will be directed to the Receive Serial Data Output pin together with other incoming DS1 pay-
load data. The external equipment can thus still extract signaling data from the received DS1 payload data sep-
arately.
10.5.1.4 Signaling Data Substitution
After channel conditioning, the signaling conditioning can be optionally enabled by the RSCR registers. The ac-
tual signaling bits in each channel can be replaced either with all ones or with signaling bits stored in the Re-
ceive Substitution Signaling Register (RSSR). To enable signaling substitution, the Receive Signaling Substitu-
356
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
tion Enable bit of the Receive Signaling Control Register (RSCR) has to be set to one. The table below shows
configuration of the Receive Signaling Substitution Enable bit of the Receive Signaling Control Register.
RECEIVE SIGNALING CONTROL REGISTER (RSCR) (INDIRECT ADDRESS = 0XN2H, 0XA0H - 0XB7H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
6
Receive Signaling
Substitution
Enable
R/W
0 - Signaling Substitution is disabled. The XRT84L38 framer will not
replace extracted signaling bits from the incoming DS1 payload data with
all ones or with signaling bits stored in RSSR registers.
1 - Signaling Substitution is enabled. The XRT84L38 framer will replace
extracted signaling bits from the incoming DS1 payload data with all ones
or with signaling bits stored in RSSR registers.
As mentioned before, the actual signaling bits in each channel can be replaced either with all ones or with sig-
naling bits stored in the Receive Substitution Signaling Register (RSSR). The table below shows configurations
of the Receive Substitution Signaling Register.
RECEIVE SUBSTITUTION SIGNALING REGISTER (RSSR) (INDIRECT ADDRESS = 0XN02H, 0X80H -
0X97H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-4
3
Reserved
R/W
SIG16-A
SIG4-A
SIG2-A
Sixteen-Code Signaling bit A
Four-Code Signaling bit A
Two-Code Signaling bit A
2
1
0
SIG16-B
SIG4-B
SIG2-A
Sixteen-Code Signaling bit B
Four-Code Signaling bit B
Two-Code Signaling bit A
SIG16-C
SIG4-A
SIG2-A
Sixteen-Code Signaling bit C
Four-Code Signaling bit A
Two-Code Signaling bit A
SIG16-D
SIG4-B
SIG2-A
Sixteen-Code Signaling bit D
Four-Code Signaling bit B
Two-Code Signaling bit A
In SF or SLC®96 mode, the Receive Signaling Substitution Control [1:0] bits can select all ones substitution,
two-code signaling substitution, or four-code signaling substitution. The XRT84L38 framer can substitute re-
ceived signaling bits with all ones. Two-code signaling substitution is done by substituting the least significant
bit (LSB) of the specific channel in frame 6 and 12 with the content of the SIG2-A bit of the Receive Substitu-
tion Signaling Register (RSSR). Four-code signaling substitution is done by substituting the LSB of channel da-
ta in frame 6 with the SIG4-A bit and the LSB of channel data in frame 12 with the SIG4-B bit of the RSSR reg-
ister. If 16-code signaling substitution is selected in SF format, only the SIG16-A bit and SIG16-B bit are used.
In ESF mode, the Receive Signaling Substitution Control [1:0] bits can select all ones substitution, two-code
signaling substitution, four-code signaling substitution, or sixteen-code signaling. The XRT84L38 framer can
substitute received signaling bits with all ones. Two-code signaling substitution is done by substituting the LSB
of the specific channel in frame 6, 12, 18, and 24 with the content of the SIG2-A bit of the register. Four-code
signaling substitution is done by substituting the LSB of channel data in frames 6 and 18 with the SIG4-A bit
and the LSB of channel data in frames 12 and 24 with the SIG4-B bit of the RSSR register. Sixteen-code sig-
357
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
naling substitution is implemented by substituting the LSB of channel data in frames 6, 12, 18, and 24 with the
content of SIG16-A, SIG16-B, SIG16-C, and SIG16-D bits of RSSR register respectively.
The table below shows configurations of the Receive Signaling Substitution Control [1:0] bits of the Receive
Signaling Control Register.
RECEIVE SIGNALING CONTROL REGISTER (RSCR) (INDIRECT ADDRESS = 0XN2H, 0X40H - 0X57H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3-2
Receive Signaling
Substitution
Control
R/W
00 - The received signaling bits are replaced by all ones and send to the
external equipment.
01 - Two-code signaling substitution is applied to the received signaling
bits. The replaced signaling information is sent to the external equipment.
10 - Four-code signaling substitution is applied to the received signaling
bits. The replaced signaling information is sent to the external equipment.
11 - Sixteen-code signaling substitution is applied to the received signaling
bits. The replaced signaling information is sent to the external equipment.
NOTE: In SF mode, this option is disabled.
10.6 HOW TO CONFIGURE THE FRAMER TO DETECT ALARMS AND ERROR CONDITIONS
The XRT84L38 T1/J1/E1 Octal Framer can be configured to monitor quality of received DS1 frames. It can
generate error indicators if the local receive framer has received error frames from the remote terminal. If cor-
responding interrupt is enabled, the local microprocessor operation is interrupted by these error conditions. Up-
on microprocessor interruption, the user can intervene by looking into the error conditions.
At the same time, the user can configure the XRT84L38 framer to transmit alarms and error indications to re-
mote terminal. Different alarms and error indications will be transmitted depending on the error condition.
The section below gives a brief discussion of the error conditions that can be detected by the XRT84L38 framer
and error indications that will be generated.
10.6.1 How to configure the framer to detect AIS Alarm
As we discussed before, transmission of Alarm Indication Signal (AIS) or Blue Alarm by the intermediate node
indicates that the equipment is still functioning but unable to offer services. It is an all ones (except for framing
bits) pattern which can be used by the equipment further down the line to maintain clock recovery and timing
synchronization.
The XRT84L38 framer can detect two types of AIS in DS1 mode:
• Framed AIS
• Unframed AIS
Unframed AIS is an all ones pattern. If unframed AIS is sent, the equipment further down the line will be able to
maintain timing synchronization and be able to recover clock from the received AIS signal. However, due to the
lack of framing bits, the equipment farther down the line will not be able to maintain frame synchronization and
will declare Loss of Frame (LOF).
On the other hand, the payload portion of a framed AIS pattern is all ones. However, a framed AIS pattern still
has correct framing bits. Therefore, the equipment further down the line can still maintain frame synchroniza-
tion as well as timing synchronization. In this case, no LOF or Red alarm will be declared.
The Alarm indication logic within the Receive Framer block of the XRT84L38 framer monitors the incoming
DS1 frames for AIS. AIS alarm condition are detected and declared according to the following procedure:
1. The incoming DS1 frames are monitored for AIS detection. AIS detection is defined as an unframed or
framed pattern with less than three zeros in two consecutive frames.
2. An AIS detection counter within the Receive Framer block of the XRT84L38 counts the occurrences of AIS
detection over a 6 ms interval. It will indicate a valid AIS flag when twenty-two or more of a possible twenty-
four AIS are detected.
358
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
3. Each 6 ms interval with a valid AIS flag increments a flag counter which declares AIS alarm when 255 valid
flags have been collected.
Therefore, AIS condition has to be persisted for 1.53 seconds before AIS alarm condition is declared by the
XRT84L38 framer.
If there is no valid AIS flag over a 6ms interval, the Alarm indication logic will decrement the flag counter. The
AIS alarm is removed when the counter reaches 0. That is, AIS alarm will be removed if over 1.53 seconds,
there is no valid AIS flag.
The Alarm Indication Signal Detection Select [1:0] bits of the Alarm Generation Register (AGR) enable the two
types of AIS detection that are supported by the XRT84L38 framer. The table below shows configurations of
the Alarm Indication Signal Detection Select [1:0] bits of the Alarm Generation Register (AGR).
ALARM GENERATION REGISTER (AGR) (INDIRECT ADDRESS = 0XN0H, 0X08H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1-0
AIS Detection
Select
R/W
00 - AIS alarm detection is disabled.When this bit is set to 01:Detection of
unframed AIS alarm of all ones pattern is enabled.
10 - AIS alarm detection is disabled.When this bit is set to 00:Detection of
framed AIS alarm of all ones pattern except for framing bits is enabled.
If detection of unframed or framed AIS alarm is enabled by the user and if AIS is present in the incoming DS1
frame, the XRT84L38 framer can generate a Receive AIS State Change interrupt associated with the setting of
Receive AIS State Change bit of the Alarm and Error Status Register to one.
To enable the Receive AIS State Change interrupt, the Receive AIS State Change Interrupt Enable bit of the
Alarm and Error Interrupt Enable Register (AEIER) have to be set to one. In addition, the Alarm and Error Inter-
rupt Enable bit of the Block Interrupt Enable Register (BIER) needs to be one.
The table below shows configurations of the Receive AIS State Change Interrupt Enable bit of the Alarm and
Error Interrupt Enable Register (AEIER).
ALARM AND ERROR INTERRUPT ENABLE REGISTER (AEIER) (INDIRECT ADDRESS = 0XNAH, 0X03H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1
Receive AIS State
Change Interrupt
Enable
R/W
0 - The Receive AIS State Change interrupt is disabled.
1 - The Receive AIS State Change interrupt is enabled.
The table below shows configurations of the Alarm and Error Interrupt Enable bit of the Block Interrupt Enable
Register.
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X01H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1
Alarm and Error
Interrupt Enable
R/W
0 - Every interrupt generated by the Alarm and Error Interrupt Status Reg-
ister (AEISR) is disabled.
1 - Every interrupt generated by the Alarm and Error Interrupt Status Reg-
ister (AEISR) is enabled.
When these interrupt enable bits are set and AIS is present in the incoming DS1 frame, the XRT84L38 framer
will declare AIS by doing the following:
359
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
• Set the read-only Receive AIS State bit of the Alarm and Error Status Register (AESR) to one indicating
there is AIS alarm detected in the incoming DS1 frame.
• Set the Receive AIS State Change bit of the Alarm and Error Status Register to one indicating there is a
change in state of AIS. This status indicator is valid until the Framer Interrupt Status Register is read.
Reading this register clears the associated interrupt if Reset-Upon-Read is selected in Interrupt Control Regis-
ter (ICR). Otherwise, a write-to-clear operation by the microprocessor is required to reset these status indica-
tors.
The table below shows the Receive AIS State Change status bits of the Alarm and Error Status Register.
ALARM AND ERROR STATUS REGISTER (AESR) (INDIRECT ADDRESS = 0XNAH, 0X02H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1
Receive AIS State
Change
RUR /
WC
0 - There is no change of AIS state in the incoming DS1 payload data.
1 - There is change of AIS state in the incoming DS1 payload data.
The Receive AIS State bit of the Alarm and Error Status Register (AESR), on the other hand, is a read-only bit
indicating there is AIS alarm detected in the incoming DS1 frame.
The table below shows the Receive AIS State status bits of the Alarm and Error Status Register.
ALARM AND ERROR STATUS REGISTER (AESR) (INDIRECT ADDRESS = 0XNAH, 0X02H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
6
Receive AIS State
R
0 - There is no AIS alarm condition detected in the incoming DS1 payload
data.
1 - There is AIS alarm condition detected in the incoming DS1 payload
data.
10.6.2 How to configure the framer to detect Red Alarm
The Alarm indication logic within the Receive Framer block of the XRT84L38 framer monitors the incoming
DS1 frames for red alarm or Loss of Frame (LOF) condition. Red alarm condition are detected and declared
according to the following procedure:
1. The red alarm is detected by monitoring the occurrence of Loss of Frame (LOF) over a 6 ms interval.
2. An LOF valid flag will be posted on the interval when one or more LOF occurred during the interval.
3. Each interval with a valid LOF flag increments a flag counter which declares RED alarm when 63 valid
intervals have been accumulated.
4. An interval without valid LOF flag decrements the flag counter. The Red alarm is removed when the
counter reaches zero.
If LOF condition is present in the incoming DS1 frame, the XRT84L38 framer can generate a Receive Red
Alarm State Change interrupt associated with the setting of Receive Red Alarm State Change bit of the Alarm
and Error Status Register to one.
To enable the Receive Red Alarm State Change interrupt, the Receive Red Alarm State Change Interrupt En-
able bit of the Alarm and Error Interrupt Enable Register (AEIER) has to be set to one. In addition, the Alarm
and Error Interrupt Enable bit of the Block Interrupt Enable Register (BIER) needs to be one.
360
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The table below shows configurations of the Receive Red Alarm State Change Interrupt Enable bit of the Alarm
and Error Interrupt Enable Register (AEIER).
ALARM AND ERROR INTERRUPT ENABLE REGISTER (AEIER) (INDIRECT ADDRESS = 0XNAH, 0X03H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
2
ReceiveRedAlarm
State Change
Interrupt Enable
R/W
0 - The Receive Red Alarm State Change interrupt is disabled. No Receive
Loss of Frame (RxLOF) interrupt will be generated upon detection of LOF
condition.
1 - The Receive Red Alarm State Change interrupt is enabled. Receive
Loss of Frame (RxLOF) interrupt will be generated upon detection of LOF
condition.
The table below shows configurations of the Alarm and Error Interrupt Enable bit of the Block Interrupt Enable
Register.
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X01H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1
Alarm and Error
Interrupt Enable
R/W
0 - Every interrupt generated by the Alarm and Error Interrupt Status Reg-
ister (AEISR) is disabled.
1 - Every interrupt generated by the Alarm and Error Interrupt Status Reg-
ister (AEISR) is enabled.
When these interrupt enable bits are set and Red Alarm is present in the incoming DS1 frame, the XRT84L38
framer will declare Red Alarm by doing the following:
• Set the read-only Receive Red Alarm State bit of the Alarm and Error Status Register (AESR) to one indicat-
ing there is Red Alarm detected in the incoming DS1 frame.
• Set the Receive Red Alarm State Change bit of the Alarm and Error Status Register to one indicating there is
a change in state of Red Alarm. This status indicator is valid until the Framer Interrupt Status Register is
read.
Reading this register clears the associated interrupt if Reset-Upon-Read is selected in Interrupt Control Regis-
ter (ICR). Otherwise, a write-to-clear operation by the microprocessor is required to reset these status indica-
tors.
The table below shows the Receive Red Alarm State Change status bits of the Alarm and Error Status Regis-
ter.
ALARM AND ERROR STATUS REGISTER (AESR) (INDIRECT ADDRESS = 0XNAH, 0X02H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
2
ReceiveRedAlarm
State Change
RUR /
WC
0 - There is no change of Red Alarm state in the incoming DS1 payload
data.
1 - There is change of Red Alarm state in the incoming DS1 payload data.
The Receive Red Alarm State bit of the Alarm and Error Status Register (AESR), on the other hand, is a read-
only bit indicating there is Red Alarm detected in the incoming DS1 frame.
361
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The table below shows the Receive Red Alarm State status bits of the Alarm and Error Status Register.
ALARM AND ERROR STATUS REGISTER (AESR) (INDIRECT ADDRESS = 0XNAH, 0X02H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
ReceiveRedAlarm
State
R
0 - There is no Red Alarm condition detected in the incoming DS1 payload
data.
1 - There is Red Alarm condition detected in the incoming DS1 payload
data.
10.6.3 How to configure the framer to detect Yellow Alarm
The Alarm indication logic within the Receive Framer block of the XRT84L38 framer monitors the incoming
DS1 frames for Yellow Alarm condition. The yellow alarm is detected and declared according to the following
procedure:
1. Monitor the occurrence of Yellow Alarm pattern over a 6 ms interval. A YEL valid flag will be posted on the
interval when Yellow Alarm pattern occurred during the interval.
2. Each interval with a valid YEL flag increments a flag counter which declares YEL alarm when 80 valid
intervals have been accumulated.
3. An interval without valid YEL flag decrements the flag counter. The YEL alarm is removed when the
counter reaches zero.
If Yellow Alarm condition is present in the incoming DS1 frame, the XRT84L38 framer can generate a Receive
Yellow Alarm State Change interrupt associated with the setting of Receive Yellow Alarm State Change bit of
the Alarm and Error Status Register to one.
To enable the Receive Yellow Alarm State Change interrupt, the Receive Yellow Alarm State Change Interrupt
Enable bit of the Alarm and Error Interrupt Enable Register (AEIER) has to be set to one. In addition, the Alarm
and Error Interrupt Enable bit of the Block Interrupt Enable Register (BIER) needs to be one.
The table below shows configurations of the Receive Yellow Alarm State Change Interrupt Enable bit of the
Alarm and Error Interrupt Enable Register (AEIER).
ALARM AND ERROR INTERRUPT ENABLE REGISTER (AEIER) (INDIRECT ADDRESS = 0XNAH, 0X03H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
0
Receive Yellow
Alarm State
Change Interrupt
Enable
R/W
0 - The Receive Yellow Alarm State Change interrupt is disabled. Any state
change of Receive Yellow Alarm will not generate an interrupt.
1 - The Receive Yellow Alarm State Change interrupt is enabled. Any state
change of Receive Yellow Alarm will generate an interrupt.
The table below shows configurations of the Alarm and Error Interrupt Enable bit of the Block Interrupt Enable
Register.
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X01H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1
Alarm and Error
Interrupt Enable
R/W
0 - Every interrupt generated by the Alarm and Error Interrupt Status Reg-
ister (AEISR) is disabled.
1 - Every interrupt generated by the Alarm and Error Interrupt Status Reg-
ister (AEISR) is enabled.
362
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
When these interrupt enable bits are set and Yellow Alarm is present in the incoming DS1 frame, the
XRT84L38 framer will declare Yellow Alarm by doing the following:
• Set the read-only Receive Yellow Alarm State bit of the Alarm and Error Status Register (AESR) to one indi-
cating there is Yellow Alarm detected in the incoming DS1 frame.
• Set the Receive Yellow Alarm State Change bit of the Alarm and Error Status Register to one indicating there
is a change in state of Yellow Alarm. This status indicator is valid until the Framer Interrupt Status Register is
read.
Reading this register clears the associated interrupt if Reset-Upon-Read is selected in Interrupt Control Regis-
ter (ICR). Otherwise, a write-to-clear operation by the microprocessor is required to reset these status indica-
tors.
The table below shows the Receive Yellow Alarm State Change status bits of the Alarm and Error Status Reg-
ister.
ALARM AND ERROR STATUS REGISTER (AESR)(INDIRECT ADDRESS = 0XNAH, 0X02H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
0
Receive Yellow
Alarm State
Change
RUR /
WC
0 - There is no change of Yellow Alarm state in the incoming DS1 payload
data.
1 - There is change of Yellow Alarm state in the incoming DS1 payload
data.
The table below shows the Receive AIS State Change status bits of the Alarm and Error Status Register.
The Receive Yellow Alarm State bit of the Alarm and Error Status Register (AESR), on the other hand, is a
read-only bit indicating there is Yellow Alarm detected in the incoming DS1 frame.
The table below shows the Receive Yellow Alarm State status bits of the Alarm and Error Status Register.
ALARM AND ERROR STATUS REGISTER (AESR) (INDIRECT ADDRESS = 0XNAH, 0X02H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
5
Receive Yellow
Alarm State
R
0 - There is no Yellow Alarm condition detected in the incoming DS1 pay-
load data.
1 - There is Yellow Alarm condition detected in the incoming DS1 payload
data.
10.6.4 How to configure the framer to detect Bipolar Violation
The line coding for the DS1 signal should be bipolar. That is, a binary "0" is transmitted as zero volts while a bi-
nary "1" is transmitted as either a positive or negative pulse, opposite in polarity to the previous pulse. A Bipo-
lar Violation or BPV occurs when the alternate polarity rule is violated. The Alarm indication logic within the Re-
ceive Framer block of the XRT84L38 framer monitors the incoming DS1 frames for Bipolar Violations.
If a Bipolar Violation is present in the incoming DS1 frame, the XRT84L38 framer can generate a Receive Bipo-
lar Violation interrupt associated with the setting of Receive Bipolar Violation bit of the Alarm and Error Status
Register to one.
To enable the Receive Bipolar Violation interrupt, the Receive Bipolar Violation Interrupt Enable bit of the Alarm
and Error Interrupt Enable Register (AEIER) has to be set to one. In addition, the Alarm and Error Interrupt En-
able bit of the Block Interrupt Enable Register (BIER) needs to be one.
363
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The table below shows configurations of the Receive Bipolar Violation Interrupt Enable bit of the Alarm and Er-
ror Interrupt Enable Register (AEIER).
ALARM AND ERROR INTERRUPT ENABLE REGISTER (AEIER) (INDIRECT ADDRESS = 0XNAH, 0X03H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3
Receive Bipolar
Violation Interrupt
Enable
R/W
0 - The Receive Bipolar Violation interrupt is disabled. Occurrence of one
or more bipolar violations will not generate an interrupt.
1 - The Receive Bipolar Violation interrupt is enabled. Occurrence of one
or more bipolar violations will generate an interrupt.
The table below shows configurations of the Alarm and Error Interrupt Enable bit of the Block Interrupt Enable
Register.
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X01H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1
Alarm and Error
Interrupt Enable
R/W
0 - Every interrupt generated by the Alarm and Error Interrupt Status Reg-
ister (AEISR) is disabled.
1 - Every interrupt generated by the Alarm and Error Interrupt Status Reg-
ister (AEISR) is enabled.
When these interrupt enable bits are set and one or more Bipolar Violations are present in the incoming DS1
frame, the XRT84L38 framer will declare Receive Bipolar Violation by doing the following:
• Set the Receive Bipolar Violation bit of the Alarm and Error Status Register to one indicating there are one or
more Bipolar Violations. This status indicator is valid until the Framer Interrupt Status Register is read.
Reading this register clears the associated interrupt if Reset-Upon-Read is selected in Interrupt Control Regis-
ter (ICR). Otherwise, a write-to-clear operation by the microprocessor is required to reset these status indica-
tors.
The table below shows the Receive Bipolar Violation status bits of the Alarm and Error Status Register.
ALARM AND ERROR STATUS REGISTER (AESR) (INDIRECT ADDRESS = 0XNAH, 0X02H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3
Receive Bipolar
Violation State
Change
RUR /
WC
0 - There is no change of Bipolar Violation state in the incoming DS1 pay-
load data.
1 - There is change of Bipolar Violation state in the incoming DS1 payload
data.
10.6.5 How to configure the framer to detect Loss of Signal
A Loss of Signal or LOS occurs when neither RPOS nor RNEG inputs of the framer receives a high level input
for 32 consecutive bit times. The Alarm indication logic within the Receive Framer block of the XRT84L38 fram-
er monitors the incoming DS1 frames for Loss of Signal conditions. If used in conjunction with EXAR LIUs, for
example, the XRT83L3x family, the XRT84L38 framer also declares LOS when the Receive LOS (RxLOS) in-
put pin is pulled HIGH.
The removal of LOS condition is through detection of 12.5% ones over 32 consecutive bits. In the other words,
XRT84L38 framer will remove LOS alarm when there is no 4 consecutive zeros received.
NOTE: The implementation of LOS detection and removal only apply to B8ZS coded bipolar inputs.
364
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
If Loss of Signal condition is present in the incoming DS1 frame, the XRT84L38 framer can generate a Receive
Loss of Signal interrupt associated with the setting of Receive Loss of Signal bit of the Alarm and Error Status
Register to one.
To enable the Receive Loss of Signal interrupt, the Receive Loss of Signal Interrupt Enable bit of the Alarm and
Error Interrupt Enable Register (AEIER) has to be set to one. In addition, the Alarm and Error Interrupt Enable
bit of the Block Interrupt Enable Register (BIER) needs to be one.
The table below shows configurations of the Receive Loss of Signal Interrupt Enable bit of the Alarm and Error
Interrupt Enable Register (AEIER).
ALARM AND ERROR INTERRUPT ENABLE REGISTER (AEIER) (INDIRECT ADDRESS = 0XNAH, 0X03H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
4
Receive Loss of
Signal Interrupt
Enable
R/W
0 - The Receive Loss of Signal interrupt is disabled. Occurrence of Loss of
Signals will not generate an interrupt.
1 - The Receive Loss of Signal interrupt is enabled. Occurrence of Loss of
Signals will generate an interrupt.
The table below shows configurations of the Alarm and Error Interrupt Enable bit of the Block Interrupt Enable
Register.
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X01H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1
Alarm and Error
Interrupt Enable
R/W
0 - Every interrupt generated by the Alarm and Error Interrupt Status Reg-
ister (AEISR) is disabled.
1 - Every interrupt generated by the Alarm and Error Interrupt Status Reg-
ister (AEISR) is enabled.
When these interrupt enable bits are set and one or more Loss of Signals are present in the incoming DS1
frame, the XRT84L38 framer will declare Receive Loss of Signal by doing the following:
• Set the Receive Loss of Signal bit of the Alarm and Error Status Register to one indicating there is one or
more Loss of Signals. This status indicator is valid until the Framer Interrupt Status Register is read.
Reading this register clears the associated interrupt if Reset-Upon-Read is selected in Interrupt Control Regis-
ter (ICR). Otherwise, a write-to-clear operation by the microprocessor is required to reset these status indica-
tors.
The table below shows the Receive Loss of Signal status bits of the Alarm and Error Status Register.
ALARM AND ERROR STATUS REGISTER (AESR) (INDIRECT ADDRESS = 0XNAH, 0X02H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
4
Receive Loss of
Signal State
RUR /
WC
0 - There is no change of Loss of Signal state in the incoming DS1 payload
data.
1 - There is change of Loss of Signal state in the incoming DS1 payload
data.
365
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
11.0 E1 TRANSMIT FRAMER BLOCK
11.1 HOW TO CONFIGURE XRT84L38 TO OPERATE IN E1 MODE
The XRT84L38 Octal T1/E1/J1 Framer supports DS1, J1 or E1 framing modes. Since J1 standard is very simi-
lar to DS1 standard with a few minor changes, the J1 framing mode is included as a sub-set of the DS1 framing
mode. All eight framers within the XRT84L38 silicon can be individually configured to support DS1, J1 or E1
framing modes.
NOTE: If transmitting section of one framer is configured to support either one of the framing modes, the receiving section
is automatically configured to support the same framing modes.
The T1/E1 Select bit of the Clock Select Register (CSR) controls which framing mode, that is, T1/J1 or E1, sup-
ported by the framer. The table below illustrates configurations of the T1/E1 Select bit of the Clock Select Reg-
ister (CSR).
CLOCK SELECT REGISTER (CSR) (INDIRECT ADDRESS = 0XN0H, 0X00H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
6
T1/E1 Select
R/W
0 - The XRT84L38 framer is running in E1 mode.
1 - The XRT84L38 framer is running in T1 mode.
The purpose of the E1 Transmit Framer block is to embed and encode user payload data into frames and to
route this E1 frame data to the Transmit E1 LIU Interface block. Please note that the XRT84L38 has eight (8)
individual E1 Transmit Framer blocks. Hence, the following description applies to all eight of these individual
Transmit E1 Framer blocks.
The purpose of the E1 Transmit Framer block is:
• To encode user data, inputted from the Terminal Equipment into a standard framing format.
• To provide individual data control and signaling conditioning of each DS0 channel.
• To support the transmission of HDLC messages, from the local transmitting terminal, to the remote receiving
terminal.
• To transmit indications that the local receive framer has received error frames from the remote terminal.
• To transmit alarm condition indicators to the remote terminal.
The following sections discuss the functionalities of E1 Transmit Framer block in detail. We will also describe
how to configure the XRT84L38 to transmit E1 frames according to system requirement of users.
11.2 HOW TO CONFIGURE THE FRAMER TO TRANSMIT AND RECEIVE DATA IN E1 FRAMING FORMAT
The XRT84L38 Octal T1/E1/J1 Framer is designed to meet the requirement of ITU-T Recommendation G.704.
The E1 framer supports the following:
• Frame Alignment Signal (FAS)
• CRC-4 Multi-frame
The ITU-T Recommendation G.704 also specifies two forms of signaling that can be supported by the E1
Transport medium:
• Channel Associated Signaling (CAS)
• Common Channel Signaling (CCS)
The XRT84L38 framer supports both CAS, CCS signaling format together with Clear Channel without signal-
ing.
11.2.1 How to configure the framer to choose FAS searching algorithm
The XRT84L38 framer can use two algorithms to search for FAS pattern and thus declare FAS alignment syn-
chronization. The FAS Selection bit of the Framing Select Register (FSR) allows the user to choose which one
of the two algorithms for searching FAS frame alignment.
366
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The table below shows configurations of the FAS Selection bit of the Framing Select Register (FSR).
FRAMING SELECT REGISTER (FSR) (INDIRECT ADDRESS = 0XN0H, 0X07H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
0
FAS Selection bit
R/W
This Read/Write bit field allows the user to determine which algorithm is
used for searching FAS frame alignment pattern. When an FAS alignment
pattern is found and locked, the XRT84L38 will generate Receive Synchro-
nization (RxSync_n) pulse.
0 - Algorithm 1 is selected for searching FAS frame alignment pattern.
1 - Algorithm 2 is selected for searching FAS frame alignment pattern.
11.2.2 How to configure the framer to enable CRC-4 Multi-frame alignment and select the locking cri-
teria
The CRC-4 Selection [1:0] bits of the Framing Select Register (FSR) enable the framer to search for CRC-4
Multi-frame alignment and select the criteria for locking the CRC-4 Multi-frame alignment.
The table below shows configurations of the CRC-4 Selection [1:0] bit of the Framing Select Register (FSR).
FRAMING SELECT REGISTER (FSR) (INDIRECT ADDRESS = 0XN0H, 0X07H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3-2
CRC-4 Selection
bit
R/W
Theses Read/Write bit fields allow the user to enable searching of CRC-4
Multi-frame alignment and determine what criteria are used for locking the
CRC-4 Multi-frame alignment pattern.
00 - Searching of CRC-4 Multi-frame alignment is disabled. The
XRT84L38 framer will not search for CRC-4 Multi-frame alignment and
thus will not declare CRC-4 Multi-frame synchronization. No Receive
CRC-4 Multi-frame Synchronization (RxCRCMsync_n) pulse will be gener-
ated by the framer.
01 - Searching of CRC-4 Multi-frame alignment is enabled. The XRT84L38
will search for and declare CRC-4 Multi-frame synchronization if:At least
one valid CRC-4 Multi-frame alignment signal is observed within 8 ms.
10 - Searching of CRC-4 Multi-frame alignment is enabled. The XRT84L38
will search for and declare CRC-4 Multi-frame synchronization if:At least
two valid CRC-4 Multi-frame alignment signals are observed within 8 ms.
The time separating two CRC-4 Multi-frame alignment signals is multiple
of 2 ms.
11 - Searching of CRC-4 Multi-frame alignment is enabled. The XRT84L38
will search for and declare CRC-4 Multi-frame synchronization if:At least
three valid CRC-4 Multi-frame alignment signals are observed within 8 ms.
The time separating two CRC-4 Multi-frame alignment signals is multiple
of 2 ms.
11.2.3 How to configure the framer to enable CAS Multi-frame alignment
The XRT84L38 framer can use two algorithms to search for CAS Multi-frame alignment pattern. Upon detect-
ing of CAS Multi-frame alignment pattern, the framer will declare CAS Multi-frame alignment synchronization
and generate the Receive CAS Multi-frame synchronization pulse (RxCASMsync_n). The CAS Selection [1:0]
bits of the Framing Select Register (FSR) enable the framer to search for CAS Multi-frame alignment.
367
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The table below shows configurations of the CAS Selection [1:0] bit of the Framing Select Register (FSR).
FRAMING SELECT REGISTER (FSR) (INDIRECT ADDRESS = 0XN0H, 0X07H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
5-4
CAS Selection bit
R/W
These Read/Write bit fields allow the user to enable searching of CAS
Multi-frame alignment and determine which algorithm of the two are used
for locking the CAS Multi-frame alignment pattern.
00 - Searching of CAS Multi-frame alignment is disabled. The XRT84L38
framer will not search for CAS Multi-frame alignment and thus will not
declare CAS Multi-frame synchronization. No Receive CAS Multi-frame
Synchronization (RxCRCMsync_n) pulse will be generated by the framer.
01 - Searching of CAS Multi-frame alignment is enabled. The XRT84L38
will search for and declare CAS Multi-frame synchronization using Algo-
rithm 1.
10 - Searching of CAS Multi-frame alignment is enabled. The XRT84L38
will search for and declare CAS Multi-frame synchronization using Algo-
rithm 2 (G.732).
11 - Searching of CAS Multi-frame alignment is disabled. The XRT84L38
framer will not search for CAS Multi-frame alignment and thus will not
declare CAS Multi-frame synchronization. No Receive CAS Multi-frame
Synchronization (RxCRCMsync_n) pulse will be generated by the framer.
11.2.4 How to configure the framer to input the framing alignment bits from different sources
In E1 mode, the Frame Alignment Signal (FAS) pattern of "0011011" contained in bit 2 to 8 of every other frame
(called FAS frame) are used to identify the frame boundaries. In addition, bit 2 of the non-FAS frames is fixed to
"1" to prevent simulation of the FAS frames.
In the non-FAS frames, bit 1 is used to transmit the 6-bit CRC-4 multi-frame alignment signal of "001011" and
two E bits. The 6-bit CRC-4 multi-frame alignment signal is used to identify the CRC-4 multi-frame boundaries.
The A bit at bit 3 of non-FAS frame is used as remote yellow alarm indication. When the A bit is "0", it denotes
undistributed operation of the framer. When the A bit is "1", it denotes yellow alarm condition.
The framing alignment bits include the FAS pattern, the CRC-4 multi-frame alignment bits and the A bit. Under
default condition, the XRT84L38 can generate these framing alignment bits internally.
At the same time, the users can generate the framing alignment bits externally and insert them into the framer
through the Transmit Serial Data Input Interface block via the TxSer_n pin. It is the user's responsibility to
maintain the accuracy and integrity of the framing alignment bits. The user also has to make sure that the fram-
ing alignment bits are inserted into the framer at right position and right timing. However, this option is only
available when the XRT84L38 is configured to run at a normal back-plane rate of 2.048Mbit/s in E1 mode.
368
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The Framing Bit Source Select bit of the Synchronization MUX Register (SMR) controls source of the framing
alignment bit. The table below shows configurations of the Framing Bit Source Select bit of the Synchronization
MUX Register (SMR).
SYNCHRONIZATION MUX REGISTER (SMR) (INDIRECT ADDRESS = 0XN0H, 0X09H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
0
Framing Bit Source
R/W
This READ/WRITE bit-field permits the user to determine where the fram-
ing alignment bits should be inserted.
0 - The framing alignment bits are generated and inserted by the framer
internally.
1 - If the framer is operating in normal 2.048Mbit/s mode, the framing align-
ment bits are passed through from the Transmit Serial Data Input Interface
block via the TxSer_n pin.
11.2.5 How to configure the framer to input CRC-4 bits from different sources
Each E1 CRC-4 multi-frame is divided into two sub-multi-frames. Each sub-multi-frame consists of 8 E1
frames. If the framer is configured to operate in CRC-4 multi-frame format, bit 1 of the FAS frames are used as
Cyclic Redundancy Check (CRC-4) code of the last CRC-4 sub- multi-frame. The CRC-4 bits are an indicator
of the link quality and could be monitored by the user to establish error performance report.
The XRT84L38 can generate the CRC-4 bits internally by calculating the CRC check-sum of all the payload
bits in each E1 sub-multi-frame.
At the same time, the users can generate the CRC-4 bits externally and insert them into the framer through the
Transmit Serial Data Input Interface block via the TxSer_n pin. It is the user's responsibility to correctly com-
pute the CRC-4 bits according to E1 algorithm. Also, the user has to make sure that the CRC-4 bits are insert-
ed into the framer at right position and right timing. However, this option is only available when the XRT84L38
is configured to run at a normal back-plane rate of 2.048Mbit/s.
The CRC-4 Source Select bit of the Synchronization MUX Register (SMR) controls from where to input CRC-4
bits into the framer. The table below shows configurations of the CRC-4 Source Select bit of the Synchroniza-
tion MUX Register (SMR).
SYNCHRONIZATION MUX REGISTER (SMR) (INDIRECT ADDRESS = 0XN0H, 0X09H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1
CRC-4 Source
Select
R/W
This READ/WRITE bit-field permits the user to determine where the CRC-
4 bits should be inserted.
0 - The CRC-4 bits are generated and inserted by the framer internally.
1 - If the framer is operating in normal 2.048Mbit/s mode, the CRC-4 bits
are generated by external equipment and passed through from the Trans-
mit Serial Data Input Interface block via the TxSer_n pin.
11.2.6 How to configure the framer to input E bits from different sources
Each E1 CRC-4 multi-frame is divided into two sub-multi-frames. Each sub-multi-frame consists of 8 E1
frames, 4 of them are FAS frames and the other 4 are non-FAS frames. Of the second CRC-4 sub-multi-frame,
bit 1 of the last 2 non-FAS frames is called E bit.
The E bits are used to indicate that the previous received sub-multi-frame is error-ed. When a sub-multi-frame
is received, the framer calculated the CRC-4 bits of the received sub-multi-frame. The frame then compares
the calculated CRC-4 bits with the received CRC-4 bits. If they are the same, the framer will set E bit to "1" and
transmit it to the remote terminal. If the calculated CRC-4 bits and the receive CRC-4 bits are different, the
369
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
framer will set E bit to "0" and transmit it out. The first E bit indicates error of the first CRC-4 sub-multi-frame
while the second E bit indicates error of the second CRC-4 sub-multi-frame.
The delay between the detection of an error-ed CRC-4 sub-multi-frame and the setting of the corresponding E
bit that represents the error state should not be more than one second. If the E bits are not used, they should
be set to "1".
NOTE: The E bits will always be taken into account even if the sub-multi-frame which contains them is error-ed.
Under default condition, the XRT84L38 generate the E bits internally by calculating the CRC check-sum of all
the payload bits in each received E1 sub-multi-frame and compare them against the received CRC-4 bits.
At the same time, the users can force the E bits to either "0" or "1". Source of the E bits can also be the internal
HDLC controller such that the E bits can be used to transmit data link message.
The E bit Source Select bit of the Synchronization MUX Register (SMR) controls from where to input E bits into
the framer. The table below shows configurations of the E bit Source Select bit of the Synchronization MUX
Register (SMR).
SYNCHRONIZATION MUX REGISTER (SMR) (INDIRECT ADDRESS = 0XN0H, 0X09H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-6
E bit Source Select
R/W
These READ/WRITE bit-fields permits the user to determine where the E
bits should be inserted and what the E bits should be.
00 - The E bits are generated and inserted by the framer internally.
01 - The E bits are forced to be "0" and are inserted by the framer inter-
nally.
10 - The E bits are forced to be "1" and are inserted by the framer inter-
nally.
11 - Source of the E bits is HDLC controller of the framer. The E bits are
used to carry data link messages.
11.3 HOW TO CONFIGURE THE FRAMER TO APPLY DATA AND SIGNALING CONDITIONING TO E1 PAYLOAD DATA ON
A PER-CHANNEL BASIS
The XRT84L38 T1/J1/E1 Octal Framer provides individual control of each of the thirty two DS0 channels. The
user can apply data and signaling conditioning to raw E1 payload data coming from the Terminal Equipment on
a per-channel basis.
The XRT84L38 framer can apply the following changes to raw E1 PCM data coming from the Terminal Equip-
ment on a per-channel basis:
• All 8 bits of the input PCM data are inverted
• The even bits of the input PCM data are inverted
• The odd bits of the input PCM data are inverted
• The MSB of the input PCM data is inverted
• All input PCM data except the MSB are inverted
Configuration of the XRT84L38 framer to apply the above-mentioned changes to raw E1 PCM data are con-
trolled by the Transmit Data Conditioning Select [3:0] bits of the Transmit Channel Control Register (TCCR) of
each DS0 channel.
The XRT84L38 framer can also replace the incoming raw E1 PCM data from the Terminal Equipment with pre-
defined or user-defined codes. The XRT84L38 supports the following conditioning substitutions:
• BUSY code - an octet with hexadecimal value of 0x7F
• BUSY_TS code - an octet of pattern "111xxxxx" where "xxxxx" represents the timeslot number
• VACANT code - an octet with hexadecimal value of 0xFF
• A-law Digital Milliwatt code
370
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
• u-law Digital Milliwatt code
• IDLE code - an octet defined by the value stored in the User IDLE Code Register (UCR)
• MOOF code - MUX-Out-Of-Frame code with hexadecimal value of 0x1A
• PRBS code - an octet generated by the Pseudo-Random Bit Sequence (PRBS) Generator block of the
framer
Once again, configuration of the XRT84L38 framer to replace raw E1 PCM data with the above-mentioned cod-
ing schemes are controlled by the Transmit Data Conditioning Select [3:0] bits of the Transmit Channel Control
Register (TCCR) of each DS0 channel.
Finally, the XRT84L38 framer can configure any one or ones of the thirty two DS0 channels to be D or E chan-
nels. D channel is used primarily for data link applications. E channel is used primarily for signaling for circuit
switching with multiple access configurations.
The Transmit Data Conditioning Select [3:0] bits of the Transmit Channel Control Register (TCCR) of each
channel determine whether that particular channel is configured as D or E channel.
The table below illustrates configurations of the Transmit Data Conditioning Select [3:0] bits of the Transmit
Channel Control Register (TCCR).
TRANSMIT CHANNEL CONTROL REGISTER (TCCR) (INDIRECT ADDRESS = 0XN2H, 0X00H - 0X1FH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3-0
Transmit
Conditioning
Select
R/W
0000 - The input E1 PCM data of this DS0 channel is unchanged.
0001 - All 8 bits of the input E1 PCM data of this DS0 channel are inverted.
0010 - The even bits of the input E1 PCM data of this DS0 channel are
inverted.
0011 - The odd bits of the input E1 PCM data of this DS0 channel are
inverted.
0100 - The input E1 PCM data of this DS0 channel are replaced by the
octet stored in User IDLE Code Register (UCR).
0101 - The input E1 PCM data of this DS0 channel are replaced by BUSY
code (0x7F).
0110 - The input E1 PCM data of this DS0 channel are replaced by
VACANT code (0xFF).
0111 - The input E1 PCM data of this DS0 channel are replaced by
BUSY_TS code (111xxxxx).
1000 - The input E1 PCM data of this DS0 channel are replaced by MUX-
Out-Of-Frame (MOOF) code with value 0x1A.
1001 - The input E1 PCM data of this DS0 channel are replaced by the A-
law digital milliwatt pattern.
1010 - The input E1 PCM data of this DS0 channel are replaced by the u-
law digital milliwatt pattern.
1011 - The MSB bit of the input E1 PCM data of this DS0 channel is
inverted.
1100 - All bits of the input E1 PCM data of this DS0 channel except MSB
bit are inverted.
1101 - The input E1 PCM data of this DS0 channel are replaced by PRBS
pattern created by the internal PRBS Generator of XRT84L38 framer.
1110 - The input E1 PCM data of this DS0 channel is unchanged.
1111 - This channel is configured as D or E timeslot.
371
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
When the Transmit Data Conditioning Select [3:0] bits of the Transmit Channel Control Register (TCCR) of a
particular DS0 channel are set to 0100, input E1 PCM data of this DS0 channel are replaced by the octet
stored in User IDLE Code Register (UCR). The table below shows contents of the User IDLE Code Register.
USER IDLE CODE REGISTER (UCR) (INDIRECT ADDRESS = 0XN02H, 0X20H - 0X3FH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-0
User IDLE Code
R/W
These READ/WRITE bit-fields permits the user store any value of IDLE
code into the framer. When the Transmit Data Conditioning Select [3:0] bits
of TCCR register of a particular DS0 channel are set to 0100, the input E1
PCM data are replaced by contents of this register and sent to the Transmit
LIU Interface.
11.4 HOW TO CONFIGURE THE XRT84L38 FRAMER TO TRANSMIT SIGNALING INFORMATION
Each 256-bit E1 frame is divided into 32 octets or time slots numbered 0 to 31. Each time slot is a 64kbits/s
channel carrying voice or data information. The time slot 0 is used for frame and multi-frame synchronization,
CRC-4 error detection, yellow alarm transmission and data link transmission. The time slot 1 to time slot 15
and time slot 17 to time slot 31 are used to carry a PCM encoded voice band signal or data. The remaining
64kbits/s channel time slot 16 may be used for signaling. The XRT84L38 T1/J1/E1 Octal Framer supports the
following signaling formats to interconnect to CEPT channelized service functions:
• Common Channel Signaling (CCS)
• Channel Associated Signaling (CAS)
• Primary Rate ISDN Message Oriented Signaling (ISDN-PRI)
The XRT84L38 T1/J1/E1 Octal Framer supports insertion of various types of signaling information into the
timeslot 16 of an outgoing E1 frame. It also supports extraction and substitution of signaling information from
the incoming E1 frame. The following section provides a brief overview of Common Channel Signaling, Chan-
nel Associated Signaling in E1 mode.
NOTE: The time slot 16 can also be configured to carry PCM encoded voice or data if neither CCS nor CAS signaling is
used. The XRT84L38 framer allows the user to choose which one of the CCS, CAS, ISDN-PRI message or PCM data to be
carries on the time slot 16.
11.4.1 Brief Discussion of Common Channel Signaling in E1 Framing Format
As the name referred, Common Channel Signaling is signaling information common to all thirty voice or data
channels of an E1 trunk. The time slot 16 may be used to carry Common Channel Signaling data of up to a rate
of 64kbits/s. The national bits of time slot 0 may also be used for Common Channel Signaling. Since there are
five national bits of time slot 0 per every two E1 frames, the total bandwidth of the national bits is 20kbits/s. The
Common Channel Signaling is essentially data link information that provides performance monitoring and
transmission quality report.
11.4.2 Brief Discussion of Channel Associated Signaling in E1 Framing Format
Signaling is required when dealing with voice and dial-up data services in E1 applications. Traditionally, signal-
ing is provided on a dial-up telephone line, across the talk-path. Signaling is used to tell the receiver where the
call or route is destined. The signal is sent through switches along the route to a distant end. Common types of
signals are:
• On hook
• Off hook
• Dial tone
• Dialed digits
• Ringing cycle
• Busy tone
372
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
A signal is consists of four bits namely A, B, C and D. These bits define the state of the call for a particular time
slot. The time slot 16 octet of each E1 frame can carry CAS signals for two E1 voice or data channels. There-
fore, sixteen E1 frames are needed to carry CAS signals for all 32 E1 channels. The sixteen E1 frames then
forms a CAS Multi-frame.
The time slot 16 of Frame number 0 of an E1 CAS Multi-frame carries the pattern of "0000 XYXX". The time
slot 16 of Frame number 1 carries signals of Channel 1 and Channel 17. The time slot 16 of Frame number 2
carries signals of Channel 2 and Channel 18, and so on. The following table shows the bit allocations of Chan-
nel Associated Signaling in E1 framing format.
TIME SLOT 16 OF FRAME 0
TIME SLOT 16 OF FRAME 1
TIME SLOT 16 OF FRAME 2
TIME SLOT 16 OF FRAME 3
0000
XYXX
ABCD of
Ch. 1
ABCD of
Ch. 17
ABCD of
Ch. 2
ABCD of
Ch. 18
ABCD of
Ch. 3
ABCD of
Ch. 19
TIME SLOT 16 OF FRAME 4
TIME SLOT 16 OF FRAME 5
TIME SLOT 16 OF FRAME 6
TIME SLOT 16 OF FRAME 7
ABCD of
Ch. 4
ABCD of
Ch. 20
ABCD of
Ch. 5
ABCD of
Ch. 21
ABCD of
Ch. 6
ABCD of
Ch. 22
ABCD of
Ch. 7
ABCD of
Ch. 23
TIME SLOT 16 OF FRAME 8
TIME SLOT 16 OF FRAME 9
TIME SLOT 16 OF FRAME 10
TIME SLOT 16 OF FRAME 11
ABCD of
Ch. 8
ABCD of
Ch. 24
ABCD of
Ch. 9
ABCD of
Ch. 25
ABCD of
Ch. 10
ABCD of
Ch. 26
ABCD of
Ch. 11
ABCD of
Ch. 27
TIME SLOT 16 OF FRAME 12
TIME SLOT 16 OF FRAME 13
TIME SLOT 16 OF FRAME 14
TIME SLOT 16 OF FRAME 15
ABCD of
Ch. 12
ABCD of
Ch. 28
ABCD of
Ch. 13
ABCD of
Ch. 29
ABCD of
Ch. 14
ABCD of
Ch. 30
ABCD of
Ch. 15
ABCD of
Ch. 31
The four zeros pattern is the multi-frame alignment signal that indicates the beginning of an E1 CAS Multi-
frame. The XRT84L38 framer, upon detection of the four zeros pattern in the time slot 16, declares CAS multi-
frame synchronization and would pulse the Receive CAS Multi-frame Synchronization pulse (RxCASMSync_n)
HIGH for one clock period. The user, triggering on the Receive CAS Multi-frame Synchronization pulse, would
thus identify the received CAS Multi-frame boundary.
The X in XYXX pattern located in the time slot 16 of Frame number 0 should be fixed to "1" and can be used to
prevent mimicking of CAS Multi-frame alignment pattern.
The Y in XYXX pattern is used for alarm indication of time slot 16 to the remote terminal. If signals of time slot
16 is transmitted and received correctly, the Y bit is set to "0". In an alarm condition, the Y bit is set to "1".
Therefore, Y bit is also known as CAS Multi-frame yellow alarm.
11.4.3 Configure the framer to transmit Channel Associated Signaling
The XRT84L38 framer supports transmission of Common Channel Signaling and Channel Associated Signal-
ing according to ITU-T Recommendation G.704. As discussed briefly before, Channel Associated Signaling in-
cludes the signaling bits, the CAS Multi-frame Alignment pattern and the X and Y bits.
Signaling bits can be inserted into the outgoing E1 frame through the following:
• Signaling data is inserted from the Transmit Signaling Control Registers (TSCR) of each timeslot.
• Signaling data is inserted from TxSig_n pin.
• Signaling data is inserted from TxOH-n pin.
373
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
• Signaling data is embedded into the input PCM data coming from the Terminal Equipment.
The CAS Multi-frame alignment pattern of four zeros can be inserted into the outgoing E1 frame by using the
following method:
• CAS Multi-frame alignment pattern is inserted from theTransmit Signaling Control Registers (TSCR).
• CAS Multi-frame alignment pattern is inserted from TxSig_n pin.
• CAS Multi-frame alignment pattern is inserted from TxOH-n pin.
• CAS Multi-frame alignment pattern is embedded into the input PCM data coming from the Terminal Equip-
ment.
The CAS Multi-frame Yellow Alarm Y bit and the X bits can be inserted into the outgoing E1 frame by using the
following method:
• The X and Y bits are inserted from the Transmit Signaling Control Register (TSCR).
• The X and Y bits are inserted from TxSig_n pin.
• The X and Y bits are inserted from TxOH-n pin.
• The X and Y bits are embedded into the input PCM data coming from the Terminal Equipment.
• The X bit is inserted from the Transmit Signaling Control Register (TSCR) and Y bit is generated by the
XRT84L38 framer according to operating condition of the E1 link.
11.4.3.1 Insert Signaling Bits from TSCR Register
The four most significant bits of the Transmit Signaling Control Register (TSCR) of each time slot can be used
to store outgoing signaling data. The user can program these bits through microprocessor access. If the
XRT84L38 framer is configure to insert signaling bits from TSCR registers, the E1 Transmit Framer block will fill
up the time slot 16 octet with the signaling bits stored inside the TSCR registers. The insertion of signaling bit
into PCM data is done on a per-channel basis. The most significant bit (Bit 7) of TSCR register is used to store
Signaling bit A. Bit 6 is used to hold Signaling bit B. Bit 5 is used to hold Signaling bit C. Bit 4 is used to hold
Signaling bit D.
The table below shows the four most significant bits of the Transmit Signaling Control Register.
TRANSMIT SIGNALING CONTROL REGISTER (TSCR) (INDIRECT ADDRESS = 0XN2H, 0X40H - 0X5FH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
6
5
4
Signaling Bit A
Signaling Bit B
Signaling Bit C
Signaling Bit D
R/W
R/W
R/W
R/W
This bit is used to store Signaling Bit A.
This bit is used to store Signaling Bit B.
This bit is used to store Signaling Bit C.
This bit is used to store Signaling Bit D.
11.4.3.2 Insert Signaling Bits from TxSig_n Pin
The XRT84L38 framer can be configure to insert signaling bits provided by external equipment through the
TxSig_n pins. This pin is a multiplexed I/O pin with two functions:
• TxTSb[0]_n - Transmit Timeslot Number Bit [0] Output pin
• TxSig_n - Transmit Signaling Input pin
When the Transmit Fractional E1 bit of the Transmit Interface Control Register (TICR) is set to 0, this pin is con-
figured as TxTSb[0]_n pin, it outputs bit 0 of the timeslot number of the E1 PCM data that is transmitting.
When the Transmit Fractional E1 bit of the Transmit Interface Control Register (TICR) is set to 1, this pin is con-
figured as TxSig_n pin, it acts as an input source for the signaling bits to be transmitted in the outbound E1
frames.
Figure 117 below is a timing diagram of the TxSig_n input pin. Please note that the Signaling Bit A of a certain
channel coincides with Bit 5 of the PCM data of that channel; Signaling Bit B coincides with Bit 6 of the PCM
374
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
data; Signaling Bit C coincides with Bit 7 of the PCM data and Signaling Bit D coincides with Bit 8 (LSB) of the
PCM data.
FIGURE 117. TIMING DIAGRAM OF THE TXSIG_N INPUT
Timeslot 0
Timeslot 5
Timeslot 6
Timeslot 23
TxSerClk
TxSerClk (INV)
TxSer
Input Data
Input Data
Input Data
Input Data
F
F
TxSig
A B C D
A B C D
A B C D
A B C D
The table below shows configurations of the Transmit Fractional E1 bit of the Transmit Interface Control Regis-
ter (TICR).
TRANSMIT INTERFACE CONTROL REGISTER (TICR) (INDIRECT ADDRESS = 0XN0H, 0X20H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
4
Transmit
Fractional E1
R/W
This READ/WRITE bit-field permits the user to determine which one of the
two functions the multiplexed I/O pin of TxTSb[0]_n/TxSig_n is spotting.
0 - This pin is configured as TxTSb[0]_n pin, it outputs bit 0 of the timeslot
number of the E1 PCM data that is transmitting.
1 - This pin is configured as TxSig_n pin, it acts as an input source for the
signaling bits to be transmitted in the outbound E1 frames
11.4.3.3 Insert Signaling Bits from TxOH_n Pin
The XRT84L38 framer can be configure to insert signaling bits provided by external equipment through the
Transmit Overhead TxOH_n input pins.
The TxOH_n pin can acts as an input source for the signaling bits to be transmitted in the outbound E1 frames.
When this pin is chosen as the input source for the signaling bits, any data presents on this pin in time slot 16
would be taken into the framer directly. The time slot 16 octet of the outbound E1 frame will be replaced by data
inputted from this pin in time slot 16.
Please note that the Signaling bit A of Channel 1-15 coincides with Bit 1 of the PCM data; Signaling bit B Chan-
nel 1-15 coincides with Bit 2 of the PCM data; Signaling bit C Channel 1-15 coincides with Bit 3 of the PCM;
Signaling bit D Channel 1-15 coincides with Bit 4 of the PCM data.
Similarly, the Signaling bit A of Channel 17-31 coincides with Bit 5 of the PCM data; Signaling bit B Channel
17-31 coincides with Bit 6 of the PCM data; Signaling bit C Channel 17-31 coincides with Bit 7 of the PCM; Sig-
naling bit D Channel 17-31 coincides with Bit 8 of the PCM data.
Figure 118 below is a timing diagram of the TxOH_n input pin.
FIGURE 118. TIMING DIAGRAM OF THE TXOH_N INPUT
11.4.3.4 Insert Signaling Data from TxSer_n Pin
Depends on applications, the Terminal Equipment can embed signaling information into the E1 PCM data and
then send the data to the XRT84L38 framer device. In this case, the user should configure the framer not to in-
sert any signaling data. The input E1 PCM data will then be directed to the Transmit LIU Interface without any
modifications.
375
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
11.4.3.5 Enable Channel Associated Signaling and Signaling Data Source Control
The Transmit Signaling Control Register (TSCR) of each channel selects source of signaling data to be insert-
ed into the outgoing E1 frame and enables Channel Associated signaling. As we mentioned before, the signal-
ing data can be inserted from Transmit Signaling Control Registers (TSCR) of each timeslot, from the TxSig_n
input pin, from the TxOH_n input pin or from the TxSer_n input pin. The Transmit Signaling Data Source Select
[1:0] bits of the Transmit Signaling Control Register (TSCR) determines from which sources the signaling data
is inserted from.
The table below shows configurations of the Transmit Signaling Data Source Select [1:0] bits of the Transmit
Signaling Control Register (TSCR).
TRANSMIT SIGNALING CONTROL REGISTER (TSCR) (INDIRECT ADDRESS = 0XN2H, 0X40H - 0X57H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1-0
Transmit Signaling
Source Select
R/W
00 - None of the signaling data, the CAS Multi-frame alignment pattern, the
X bit or the CAS Multi-frame Yellow Alarm bit Y is inserted into the outgo-
ing E1 PCM data by the framer. However, the user can embed the signal-
ing data, the CAS Multi-frame alignment pattern, the X bit or the CAS
Multi-frame Yellow Alarm bit Y into E1 PCM data before routing the PCM
data into the framer.
01 - The signaling data, the CAS Multi-frame alignment pattern, the X bit or
the CAS Multi-frame Yellow Alarm bit Y is inserted into the outgoing E1
PCM data from TSCR register of each timeslot.
10 - If the XRT84L38 framer is operating in E1 2.048Mbit/s mode and if the
TxFR2048 bit of the Transmit Interface Control Register (TICR) is set to
zero:
The signaling data, the CAS Multi-frame alignment pattern, the X bit or the
CAS Multi-frame Yellow Alarm bit Y is inserted into the outgoing E1 PCM
data from the TxOH_n input pin.
If the XRT84L38 framer is operating in E1 2.048Mbit/s mode and if the
TxFR2048 bit of the Transmit Interface Control Register (TICR) is set to
one:
The signaling data, the CAS Multi-frame alignment pattern, the X bit or the
CAS Multi-frame Yellow Alarm bit Y is inserted into the outgoing E1 PCM
data from the TxSig_n input pin.
11 - No signaling data or the CAS Multi-frame alignment pattern is inserted
into the input E1 PCM data by the framer. However, the user can embed
signaling data into E1 PCM data before routing the PCM data into the
framer.
The X bit is inserted into the outgoing E1 PCM data from TSCR register.
The CAS Multi-frame Yellow Alarm Y bit is generated by the XRT84L38
framer depends on operating condition of the E1 link.
11.5 HOW TO CONFIGURE THE XRT84L38 FRAMER TO GENERATE AND TRANSMIT ALARMS AND ERROR INDICA-
TIONS TO REMOTE TERMINAL
The XRT84L38 T1/J1/E1 Octal Framer can be configured to monitor quality of received E1 frames. It can gen-
erate error indications if the local receive framer has received error frames from the remote terminal. If corre-
sponding interrupt is enabled, the local microprocessor operation is interrupted by these error conditions. Upon
microprocessor interruption, the user can intervene by looking into the error conditions.
At the same time, the user can configure the XRT84L38 framer to transmit alarms and error indications to re-
mote terminal. Different alarms and error indications will be transmitted depending on the error condition. The
section below gives a brief discussion of the error conditions and appropriate alarms that should be generated
and transmitted by the XRT84L38 framer.
11.5.1 Brief discussion of alarms and error conditions
376
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
As defined in E1 specification, alarm conditions are created from defects. Defects are momentary impairments
present on the E1 trunk. If a defect is present for a sufficient amount of time (called the integration time), then
the defect becomes an alarm. Once an alarm is declared, the alarm is present until after the defect clears for a
sufficient period of time. The time it takes to clear an alarm is called the de-integration time.
Alarms are used to detect and warn maintenance personnel of problems on the E1 trunk. There are three
types of alarms:
• Red alarm or Service Alarm Indication (SAI) Signal
• Blue alarm or Alarm Indication Signal (AIS)
• Yellow alarm or Remote Alarm Indication (RAI) Signal
To explain the error conditions and generation of different alarms, let us create a simple E1 system model. In
this model, an E1 signal is sourced from the Central Office (CO) through a Repeater to the Customer Premises
Equipment (CPE). At the same time, an E1 signal is routed from the CPE to the Repeater and back to the Cen-
tral Office. Figure 119 below shows the simple E1 system model.
FIGURE 119. SIMPLE DIAGRAM OF E1 SYSTEM MODEL
CO
Repeater
CPE
E1
Transmit
Section
E1
Receive
Section
E1 Receive
Framer Block
E1 Receive
Framer Block
E1
Receive
Section
E1
Transmit
Section
E1 Transmit
Framer Block
E1 Transmit
Framer Block
Simple E1 System Model
When the E1 system runs normally, that is, when there is no Loss of Signal (LOS) or Loss of Frame (LOF) de-
tected in the line, no alarm will be generated. Sometimes, intermittent outburst of electrical noises on the line
might result in Bipolar Violation or bit errors in the incoming signals, but these errors in general will not trigger
the equipment to generate alarms. They will, depending on the system requirements, trigger the framer to gen-
erate interrupts that would cause the local microprocessor to create performance reports of the line.
Now, consider a case in which the E1 line from the CO to the Repeater is broken or interrupted, resulting in
completely loss of incoming data or severely impaired signal quality. Upon detection of Loss of Signal (LOS) or
Loss of Frame (LOF) condition, the Repeater will generate an internal Red Alarm, also known as the Service
Alarm Indication. This alarm will normally trigger a microprocessor interrupt informing the user that an incom-
ing signal failure is happening.
When the Repeater is in the Red Alarm state, it will transmit the Yellow Alarm to the CO indicating the loss of
an incoming signal or loss of frame synchronization. This Yellow Alarm informs the Repeater that there is a
377
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
problem further down the line and its transmission is not being received at the Repeater. Figure 120 below il-
lustrates the scenario in which the E1 connection from the CO to the Repeater is broken.
FIGURE 120. GENERATION OF YELLOW ALARM BY THE REPEATER UPON DETECTION OF LINE FAILURE
Repeater declares
Red Alarm
internally
Repeater generates
Yellow Alarm to CO
CO
Repeater
CPE
Yellow
Alarm
E1
Transmit
Section
E1
Receive
Section
E1 Receive
Framer Block
E1 Receive
Framer Block
E1
Receive
Section
E1
Transmit
Section
E1 Transmit
Framer Block
E1 Transmit
Framer Block
The E1 line is
broken
The Repeater will also transmit a Blue Alarm, also known as Alarm Indication Signal (AIS) to the CPE. Blue
alarm is an all ones pattern indicating that the equipment is functioning but unable to offer service due to fail-
ures originated from remote side. It is sent such that the equipment downstream will not lose clock synchroni-
378
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
zation even though no meaningful data is received. Figure 121 below illustrates this scenario in which the Re-
peater is sending an AIS to the CPE upon detection of line failure from the CO.
FIGURE 121. GENERATION OF AIS BY THE REPEATER UPON DETECTION OF LINE FAILURE
Repeater declares
Red Alarm
internally
Repeater generates
Yellow Alarm to CO
CO
Repeater
CPE
Yellow
Alarm
E1
Transmit
Section
E1
Receive
Section
E1 Receive
Framer Block
E1 Receive
Framer Block
AIS
E1
Receive
Section
E1
Transmit
Section
E1 Transmit
Framer Block
E1 Transmit
Framer Block
Repeater
generates AIS
to CPE
The E1 line is
broken
Now, the CPE uses the AIS signal sent by the Repeater to recover received clock and remain in synchroniza-
tion with the system. Upon detecting the incoming AIS signal, the CPE will generate a Yellow Alarm automati-
cally to the Repeater to indicate the loss of incoming data. Figure 122 below illustrates this scenario in which
the Repeater is sending an AIS to the CPE and the CPE is sending a Yellow Alarm back to the Repeater.
379
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
FIGURE 122. GENERATION OF YELLOW ALARM BY THE CPE UPON DETECTION OF AIS ORIGINATED BY THE
REPEATER
Repeater declares
Red Alarm
internally
CPE detects AIS and
Repeater generates
generates Yellow
Yellow Alarm to CO
Alarm to Repeater
CO
Repeater
CPE
Yellow
Alarm
Yellow
Alarm
E1
Transmit
Section
E1
Receive
Section
E1 Receive
Framer Block
E1 Receive
Framer Block
AIS
E1
Receive
Section
E1
Transmit
Section
E1 Transmit
Framer Block
E1 Transmit
Framer Block
Repeater
generates AIS
to CPE
The E1 line is
broken
Next, let us consider the scenario in which the signaling and data link channel (the time slot 16) of an E1 line
between a far-end terminal (for example, the CO) and a near-end terminal (for example, the repeater) is im-
paired. In this case, the CAS signaling data received by the repeater is corrupted. The Repeater will then send
an all ones pattern in time slot 16 (AIS16 pattern) downstream to the CPE. The repeater will also generate a
CAS Multi-frame Yellow Alarm upstream to the CO to indicate the loss of CAS Multi-frame synchronization.
380
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
Figure 123 below illustrates this scenario in which the Repeater is sending an "AIS16" pattern to the CPE while
sending a CAS Multi-frame Yellow Alarm to the CO.
FIGURE 123. GENERATION OF CAS MULTI-FRAME YELLOW ALARM AND AIS16 BY THE REPEATER
Repeater generates
CAS Multi-frame
Yellow Alarm to CO
CO
Repeater
CPE
CAS Multi-
frame Yellow
Alarm
E1
Transmit
Section
E1
Receive
Section
E1 Receive
Framer Block
E1 Receive
Framer Block
AIS16
E1
Receive
Section
E1
Transmit
Section
E1 Transmit
Framer Block
E1 Transmit
Framer Block
The timeslot 16
of an E1 line is
iimpaired
Repeater
generates
AIS16 to CPE
381
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The CPE, upon detecting the incoming AIS16 signal, will generate a CAS Multi-frame Yellow Alarm to the Re-
peater to indicate the loss of CAS Multi-frame synchronization. Figure 124 below illustrates the CPE sending a
CAS Multi-frame Yellow Alarm back to the Repeater
FIGURE 124. GENERATION OF CAS MULTI-FRAM YELLOW ALARM BY THE CPE UPON DETECTION OF “AIS16” PAT-
TERN SENT BY THE REPEATER
CPE detects AIS16
and generates CAS
Multi-frame Yellow
Alarm to Repeater
Repeater generates
CAS Multi-frame
Yellow Alarm to CO
CO
Repeater
CPE
CAS Multi-
frame Yellow
Alarm
CAS Multi-
frame Yellow
Alarm
E1
Transmit
Section
E1
Receive
Section
E1 Receive
Framer Block
E1 Receive
Framer Block
AIS16
E1
Receive
Section
E1
Transmit
Section
E1 Transmit
Framer Block
E1 Transmit
Framer Block
The timeslot 16
of an E1 line is
iimpaired
Repeater
generates
AIS16 to CPE
In summary, AIS or Blue Alarm is sent by a piece of E1 equipment downstream indicating that the incoming
signal from upstream is lost. Yellow Alarm is sent by a piece of E1 equipment upstream upon detection of Loss
of Signal, Loss of Frame or when it is receiving AIS.
Similarly, an "AIS16" pattern is sent by a piece of E1 equipment downstream indicating that the incoming data
link channel from upstream is damaged. The CAS Multi-frame Yellow Alarm is sent by a piece of E1 equipment
upstream upon detection of Loss of CAS Multi-frame synchronization or when it is receiving an "AIS16" pat-
tern.
11.5.2 How to configure the framer to transmit AIS
As we discussed in the previous section, Alarm Indication Signal (AIS) or Blue Alarm is transmitted by the inter-
mediate node to indicate that the equipment is still functioning but unable to offer services. It is an all ones (ex-
cept for framing bits) pattern which can be used by the equipment further down the line to maintain clock recov-
ery and timing synchronization.
The XRT84L38 framer can generate three types of AIS when it is running in E1 format:
• Framed AIS
• Unframed AIS
• AIS16
Unframed AIS is an all ones pattern. If unframed AIS is sent, the equipment further down the line will be able to
maintain timing synchronization and be able to recover clock from the received AIS signal. However, due to the
lack of framing bits, the equipment farther down the line will not be able to maintain frame synchronization and
will declare Loss of Frame (LOF).
382
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
On the other hand, the payload portion of a framed AIS pattern is all ones. However, a framed AIS pattern still
has correct framing bits. Therefore, the equipment further down the line can still maintain frame synchroniza-
tion as well as timing synchronization. In this case, no LOF or Red alarm will be declared.
"AIS16" is an AIS alarm that only supported in E1 framing format. It is an all ones pattern in time slot 16 of each
E1 frame. As we mentioned before, time slot 16 is usually used for signaling and data link in E1, therefore, an
"AIS16" alarm is transmitted by the intermediate node to indicate that the data link channel is having a prob-
lem. Since all the other thirty one time slots are still transmitting normal data (that is, framing information and
PCM data), therefore, the equipment further down the line can still maintain frame synchronization, timing syn-
chronization as well as receiving PCM data. In this case, no LOF or Red alarm will be declared by the equip-
ments further down the line. However, a CAS Multi-frame Yellow Alarm will be sent by the equipment further
down the line to indicate the loss of CAS Multi-frame alignment.
The Transmit Alarm Indication Signal Select [1:0] bits of the Alarm Generation Register (AGR) enable the three
types of AIS transmission that are supported by the XRT84L38 framer. The table below shows configurations
of the Transmit Alarm Indication Signal Select [1:0] bits of the Alarm Generation Register (AGR).
ALARM GENERATION REGISTER (AGR) (INDIRECT ADDRESS = 0XN0H, 0X08H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3-2
Transmit AIS
Select
R/W
These READ/WRITE bit-fields allows the user to choose which one of the
three AIS pattern supported by the XRT84L38 framer will be transmitted.
00 - No AIS alarm is generated.
01 - Enable unframed AIS alarm of all ones pattern.
11 - AIS16 pattern is generated. Only time slot 16 is carrying the all ones
pattern. The other time slots still carry framing and PCM data.
11 - Enable framed AIS alarm of all ones pattern except for framing bits.
11.5.3 How to configure the framer to generate Red Alarm
Upon detection of Loss of Signal (LOS) or Loss of Frame (LOF) condition, the Repeater will generate an inter-
nal Red Alarm when enabled. This alarm will normally trigger a microprocessor interrupt informing the user
that an incoming signal failure is happening.
The Loss of Frame Declaration Enable bit of the Alarm Generation Register (AGR) enable the generation of
Red Alarm. The table below shows configurations of the of Frame Declaration Enable bit of the Alarm Genera-
tion Register (AGR).
ALARM GENERATION REGISTER (AGR) (INDIRECT ADDRESS = 0XN0H, 0X08H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
6
Loss of Frame
Declaration Enable
R/W
This READ/WRITE bit-field permits the framer to declare Red Alarm in
case of Loss of Frame Alignment (LOF).
When receiver module of the framer detects Loss of Frame Alignment in
the incoming data stream, it will generate a Red Alarm. The framer will
also generate an RxLOFs interrupt to notify the microprocessor that an
LOF condition is occurred. A Yellow Alarm is then returned to the remote
transmitter to report that the local receiver detects LOF.
0 - Red Alarm declaration is disabled.
1 - Red Alarm declaration is enabled.
11.5.4 How to configure the framer to transmit Yellow Alarm
The XRT84L38 framer supports transmission of both Yellow Alarm and CAS Multi-frame Yellow Alarm in E1
mode.
383
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
Upon detection of Loss of Signal (LOS) or Loss of Frame (LOF) condition, the receiver will transmit the Yellow
Alarm back to the source indicating the loss of an incoming signal. This Yellow Alarm informs the source that
there is a problem further down the line and its transmission is not being received at the destination.
On the other hand, upon detection of Loss of CAS Multi-frame alignment pattern, the receiver section of the
XRT84L38 framer will transmit a CAS Multi-frame Yellow Alarm back to the source indicating the Loss of CAS
Multi-frame synchronization.
The Yellow Alarm Generation Select [1:0] bits of the Alarm Generation Register (AGR) enable transmission of
different types of Yellow alarm that are supported by the XRT84L38 framer.
11.5.4.1 Transmit Yellow Alarm
The Yellow Alarm bits are located at bit 3 of time slot 0 of non-FAS frames. A logic one of this bit denotes the
Yellow Alarm and a logic zero of this bit denotes normal operation. The XRT84L38 supports transmission of
Yellow Alarm automatically or manually.
When the Yellow Alarm Generation Select [1:0] bits of the Alarm Generation Register are set to 01, the Yellow
Alarm bit is transmitted by echoing the received FAS alignment pattern. If the correct FAS alignment is re-
ceived, the Yellow Alarm bit is set to zero. If the FAS alignment pattern is missing or corrupted, the Yellow
Alarm bit is set to one while Loss of Frame Synchronization is declared.
When the Yellow Alarm Generation Select [1:0] bits of the Alarm Generation Register are set to 10, the Yellow
Alarm bit is transmitted as zero.
When the Yellow Alarm Generation Select [1:0] bits of the Alarm Generation Register are set to 11, the Yellow
Alarm bit is transmitted as one.
11.5.4.2 Transmit CAS Multi-frame Yellow Alarm
Within the sixteen-frame CAS Multi-frame, the CAS Multi-frame Yellow Alarm bits are located at bit 6 of time
slot 16 of frame number 0. A logic one of this bit denotes the CAS Multi-frame Yellow Alarm and a logic zero of
this bit denotes normal operation. The XRT84L38 supports transmission of CAS Multi-frame Yellow Alarm au-
tomatically or manually.
When the CAS Multi-frame Yellow Alarm Generation Select [1:0] bits of the Alarm Generation Register are set
to 01, the CAS Multi-frame Yellow Alarm bit is transmitted by echoing the received CAS Multi-frame alignment
pattern (the four zeros pattern). If the correct CAS Multi-frame alignment is received, the CAS Multi-frame Yel-
low Alarm bit is set to zero. If the CAS Multi-frame alignment pattern is missing or corrupted, the CAS Multi-
frame Yellow Alarm bit is set to one while Loss of CAS Multi-frame Synchronization is declared.
When the CAS Multi-frame Yellow Alarm Generation Select [1:0] bits of the Alarm Generation Register are set
to 10, the CAS Multi-frame Yellow Alarm bit is transmitted as zero.
When the CAS Multi-frame Yellow Alarm Generation Select [1:0] bits of the Alarm Generation Register are set
to 11, the CAS Multi-frame Yellow Alarm bit is transmitted as one.
384
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The table below shows configurations of the Yellow Alarm Generation Select [1:0] bits of the Alarm Generation
Register (AGR).
ALARM GENERATION REGISTER (AGR) (INDIRECT ADDRESS = 0XN0H, 0X08H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
5-4
Yellow Alarm Gen-
eration Select
R/W
These READ/WRITE bit-fields allows the user to choose how the
XRT84L38 would generate Yellow Alarm and CAS Multi-frame Yellow
Alarm.
00 - Transmission of Yellow Alarm and CAS Multi-frame Yellow Alarm is
disabled.
01 - The Yellow Alarm bit is transmitted by echoing the received FAS align-
ment pattern. If the correct FAS alignment is received, the Yellow Alarm bit
is set to zero. If the FAS alignment pattern is missing or corrupted, the Yel-
low Alarm bit is set to one.
The CAS Multi-frame Yellow Alarm bit is transmitted by echoing the
received CAS Multi-frame alignment pattern (the four zeros pattern). If the
correct CAS Multi-frame alignment is received, the CAS Multi-frame Yellow
Alarm bit is set to zero. If the CAS Multi-frame alignment pattern is missing
or corrupted, the CAS Multi-frame Yellow Alarm bit is set to one.
10 - The Yellow Alarm and CAS Multi-frame Yellow Alarms are transmitted
as zero.
11 - The Yellow Alarm and CAS Multi-frame Yellow Alarms are transmitted
as one.
385
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
12.0 E1 RECEIVE FRAMER BLOCK
12.1 HOW TO CONFIGURE XRT84L38 TO OPERATE IN E1 MODE
The XRT84L38 Octal T1/E1/J1 Framer supports DS1, J1 or E1 framing modes. Since J1 standard is very simi-
lar to DS1 standard with a few minor changes, the J1 framing mode is included as a sub-set of the DS1 framing
mode. All eight framers within the XRT84L38 silicon can be individually configured to support DS1, J1 or E1
framing modes.
NOTE: If transmitting section of one framer is configured to support either one of the framing modes, the receiving section
is automatically configured to support the same framing modes.
The T1/E1 Select bit of the Clock Select Register (CSR) controls which framing mode, that is, T1/J1 or E1, sup-
ported by the framer. The table below illustrates configurations of the T1/E1 Select bit of the Clock Select Reg-
ister (CSR).
CLOCK SELECT REGISTER (CSR)(INDIRECT ADDRESS = 0XN0H, 0X00H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
6
T1/E1 Select
R/W
0 - The XRT84L38 framer is running in E1 mode.
1 - The XRT84L38 framer is running in T1 mode.
The purpose of the E1 Transmit Framer block is to embed and encode user payload data into frames and to
route this E1 frame data to the Transmit E1 LIU Interface block. Please note that the XRT84L38 has eight (8)
individual E1 Transmit Framer blocks. Hence, the following description applies to all eight of these individual
Transmit E1 Framer blocks.
The purpose of the E1 Transmit Framer block is:
• To encode user data, inputted from the Terminal Equipment into a standard framing format.
• To provide individual data control and signaling conditioning of each DS0 channel.
• To support the transmission of HDLC messages, from the local transmitting terminal, to the remote receiving
terminal.
• To transmit indications that the local receive framer has received error frames from the remote terminal.
• To transmit alarm condition indicators to the remote terminal.
The following sections discuss the functionalities of E1 Transmit Framer block in details. We will also describe
how to configure the XRT84L38 to transmit E1 frames according to system requirement of users.
12.2 HOW TO CONFIGURE THE FRAMER TO RECEIVE DATA IN VARIOUS E1 FRAMING FORMATS
The XRT84L38 Octal T1/E1/J1 Framer is designed to meet the requirement of ITU-T Recommendation G.704.
The E1 framer supports the following:
• Frame Alignment Signal (FAS)
• CRC-4 Multi-frame
The ITU-T Recommendation G.704 also specifies two forms of signaling that can be supported by the E1
Transport medium:
• Channel Associated Signaling (CAS)
• Common Channel Signaling (CCS)
The XRT84L38 framer supports both CAS, CCS signaling format together with Clear Channel without signal-
ing.
12.2.1 How to configure the framer to choose FAS searching algorithm
The XRT84L38 framer can use two algorithms to search for FAS pattern and thus declare FAS alignment syn-
chronization. The FAS Selection bit of the Framing Select Register (FSR) allows the user to choose which one
of the two algorithms for searching FAS frame alignment.
386
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The table below shows configurations of the FAS Selection bit of the Framing Select Register (FSR).
FRAMING SELECT REGISTER (FSR) (INDIRECT ADDRESS = 0XN0H, 0X07H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
0
FAS Selection bit
R/W
This Read/Write bit field allows the user to determine which algorithm is
used for searching FAS frame alignment pattern. When an FAS alignment
pattern is found and locked, the XRT84L38 will generate Receive Synchro-
nization (RxSync_n) pulse.
0 - Algorithm 1 is selected for searching FAS frame alignment pattern.
1 - Algorithm 2 is selected for searching FAS frame alignment pattern.
12.2.2 How to configure the framer to enable CRC-4 Multi-frame alignment and select the locking cri-
teria
The CRC-4 Selection [1:0] bits of the Framing Select Register (FSR) enable the framer to search for CRC-4
Multi-frame alignment and select the criteria for locking the CRC-4 Multi-frame alignment.
The table below shows configurations of the CRC-4 Selection [1:0] bit of the Framing Select Register (FSR).
FRAMING SELECT REGISTER (FSR) (INDIRECT ADDRESS = 0XN0H, 0X07H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3-2
CRC-4 Selection
bit
R/W
Theses Read/Write bit fields allow the user to enable searching of CRC-4
Multi-frame alignment and determine what criteria are used for locking the
CRC-4 Multi-frame alignment pattern.
00 - Searching of CRC-4 Multi-frame alignment is disabled. The
XRT84L38 framer will not search for CRC-4 Multi-frame alignment and
thus will not declare CRC-4 Multi-frame synchronization. No Receive
CRC-4 Multi-frame Synchronization (RxCRCMsync_n) pulse will be gener-
ated by the framer.
01 - Searching of CRC-4 Multi-frame alignment is enabled. The XRT84L38
will search for and declare CRC-4 Multi-frame synchronization if:
At least one valid CRC-4 Multi-frame alignment signal is observed within 8
ms.
10 - Searching of CRC-4 Multi-frame alignment is enabled. The XRT84L38
will search for and declare CRC-4 Multi-frame synchronization if:
At least two valid CRC-4 Multi-frame alignment signals are observed within
8 ms.
The time separating two CRC-4 Multi-frame alignment signals is multiple
of 2 ms.
11 - Searching of CRC-4 Multi-frame alignment is enabled. The XRT84L38
will search for and declare CRC-4 Multi-frame synchronization if:
At least three valid CRC-4 Multi-frame alignment signals are observed
within 8 ms.
The time separating two CRC-4 Multi-frame alignment signals is multiple
of 2 ms.
12.2.3 How to configure the framer to enable CAS Multi-frame alignment
The XRT84L38 framer can use two algorithms to search for CAS Multi-frame alignment pattern. Upon detect-
ing of CAS Multi-frame alignment pattern, the framer will declare CAS Multi-frame alignment synchronization
and generate the Receive CAS Multi-frame synchronization pulse (RxCASMsync_n). The CAS Selection [1:0]
bits of the Framing Select Register (FSR) enable the framer to search for CAS Multi-frame alignment.
387
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The table below shows configurations of the CAS Selection [1:0] bit of the Framing Select Register (FSR).
FRAMING SELECT REGISTER (FSR) (INDIRECT ADDRESS = 0XN0H, 0X07H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
5-4
CAS Selection bit
R/W
These Read/Write bit fields allow the user to enable searching of CAS
Multi-frame alignment and determine which algorithm of the two are used
for locking the CAS Multi-frame alignment pattern.
00 - Searching of CAS Multi-frame alignment is disabled. The XRT84L38
framer will not search for CAS Multi-frame alignment and thus will not
declare CAS Multi-frame synchronization. No Receive CAS Multi-frame
Synchronization (RxCRCMsync_n) pulse will be generated by the framer.
01 - Searching of CAS Multi-frame alignment is enabled. The XRT84L38
will search for and declare CAS Multi-frame synchronization using Algo-
rithm 1.
10 - Searching of CAS Multi-frame alignment is enabled. The XRT84L38
will search for and declare CAS Multi-frame synchronization using Algo-
rithm 2 (G.732).
11 - Searching of CAS Multi-frame alignment is disabled. The XRT84L38
framer will not search for CAS Multi-frame alignment and thus will not
declare CAS Multi-frame synchronization. No Receive CAS Multi-frame
Synchronization (RxCRCMsync_n) pulse will be generated by the framer.
12.3 HOW TO CONFIGURE THE FRAMER TO APPLY DATA AND SIGNALING CONDITIONING TO RECEIVED E1 PAY-
LOAD DATA ON A PER-CHANNEL BASIS
The XRT84L38 T1/J1/E1 Octal Framer provides individual control of each of the thirty two DS0 channels. The
user can apply data and signaling conditioning to the received E1 payload data coming from the E1 LIU Re-
ceive Block on a per-channel basis.
The XRT84L38 framer can apply the following changes to the received E1 payload data coming from the Ter-
minal Equipment on a per-channel basis:
• All 8 bits of the received payload data are inverted
• The even bits of the received payload data are inverted
• The odd bits of the received payload data are inverted
• The MSB of the received payload data is inverted
• All received payload data except the MSB are inverted
Configurations of the XRT84L38 framer to apply the above-mentioned changes to the received E1 PAYLOAD
data are controlled by the Receive Data Conditioning Select [3:0] bits of the Receive Channel Control Register
(RCCR) of each DS0 channel.
The XRT84L38 framer can also replace the incoming E1 payload data from the E1 LIU Receive Block with pre-
defined or user-defined codes. The XRT84L38 supports the following conditioning substitutions:
• BUSY code - an octet with hexadecimal value of 0x7F
• BUSY_TS code - an octet of pattern "111xxxxx" where "xxxxx" represents the timeslot number
• VACANT code - an octet with hexadecimal value of 0xFF
• A-law Digital Milliwatt code
• u-law Digital Milliwatt code
• IDLE code - an octet defined by the value stored in the User IDLE Code Register (UCR)
• MOOF code - MUX-Out-Of-Frame code with hexadecimal value of 0x1A
388
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
• PRBS code - an octet generated by the Pseudo-Random Bit Sequence (PRBS) Generator block of the
framer
Once again, configuration of the XRT84L38 framer to replace the received E1 payload data with the above-
mentioned coding schemes are controlled by the Receive Data Conditioning Select [3:0] bits of the Receive
Channel Control Register (RCCR) of each DS0 channel.
Finally, the XRT84L38 framer can configure any one or ones of the thirty two DS0 channels to be D or E chan-
nels. D channel is used primarily for data link applications. E channel is used primarily for signaling for circuit
switching with multiple access configurations.
The Receive Data Conditioning Select [3:0] bits of the Receive Channel Control Register (RCCR) of each
channel determine whether that particular channel is configured as D or E channel.
The table below illustrates configurations of the Receive Data Conditioning Select [3:0] bits of the Receive
Channel Control Register (RCCR).
RECEIVE CHANNEL CONTROL REGISTER (RCCR) (INDIRECT ADDRESS = 0XN2H, 0X60H - 0X7FH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3-0
Receive Condition-
ing Select
R/W
0000 - The received E1 payload data of this DS0 channel is unchanged.
0001 - All 8 bits of the input E1 payload data of this DS0 channel are
inverted.
0010 - The even bits of the input E1 payload data of this DS0 channel are
inverted.
0011 - The odd bits of the input E1 payload data of this DS0 channel are
inverted.
0100 - The input E1 payload data of this DS0 channel are replaced by the
octet stored in User IDLE Code Register (UCR).
0101 - The input E1 payload data of this DS0 channel are replaced by
BUSY code (0x7F).
0110 - The input E1 payload data of this DS0 channel are replaced by
VACANT code (0xFF).
0111 - The input E1 payload data of this DS0 channel are replaced by
BUSY_TS code (111xxxxx).
1000 - The input E1 payload data of this DS0 channel are replaced by
MUX-Out-Of-Frame (MOOF) code with value 0x1A.
1001 - The input E1 payload data of this DS0 channel are replaced by the
A-law digital milliwatt pattern.
1010 - The input E1 payload data of this DS0 channel are replaced by the
u-law digital milliwatt pattern.
1011 - The MSB bit of the input E1 payload data of this DS0 channel is
inverted.
1100 - All bits of the input E1 payload data of this DS0 channel except
MSB bit are inverted.
1101 - The input E1 payload data of this DS0 channel are replaced by
PRBS pattern created by the internal PRBS Generator of XRT84L38
framer.
1110 - The input E1 payload data of this DS0 channel is unchanged.
1111 - This channel is configured as D or E timeslot.
When the Receive Data Conditioning Select [3:0] bits of the Receive Channel Control Register (RCCR) of a
particular DS0 channel are set to 0100, the received E1 payload data of this DS0 channel are replaced by the
389
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
octet stored in the Receive User IDLE Code Register (RUCR). The table below shows contents of the Receive
User IDLE Code Register.
RECEIVE USER IDLE CODE REGISTER (UCR) (INDIRECT ADDRESS = 0XN02H, 0X80H - 0X97H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-0
User IDLE Code
R/W
These READ/WRITE bit-fields permits the user store any value of IDLE
code into the framer. When the Receive Data Conditioning Select [3:0] bits
of RCCR register of a particular DS0 channel are set to 0100, the received
E1 payload data are replaced by contents of this register and sent to the
Terminal Equipment.
12.4 HOW TO CONFIGURE THE XRT84L38 FRAMER TO EXTRACT ROBBED-BIT SIGNALING INFORMATION
The XRT84L38 T1/J1/E1 Octal Framer supports insertion of Robbed-bit Signaling information into the outgoing
E1 frame. It also supports extraction and substitution of Robbed-bit Signaling information from the incoming E1
frame. The following section describes how does the XRT84L38 framer extract and substitute Robbed-bit Sig-
naling in E1 mode.
12.4.1 Configure the framer to receive and extract Robbed-bit Signaling
The XRT84L38 framer supports receiving and extraction of CAS signaling. The Receive Signaling Extraction
Control [1:0] bits of the Receive Signaling Control Register (RSCR) of each channel select either:
• No signaling extraction
• Two-code signaling
• Four-code signaling or
• Sixteen-code signaling
The table below shows configurations of the Receive Signaling Extraction Control [1:0] bits of the Receive Sig-
naling Control Register.
RECEIVE SIGNALING CONTROL REGISTER (RSCR) (INDIRECT ADDRESS = 0XN2H, 0XA0H - 0XB7H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1-0
Signaling
Extraction Control
R/W
00 - The XRT84L38 framer does not extract signaling information from
incoming E1 payload data.
01 - The XRT84L38 framer extracts sixteen-code signaling information
from incoming E1 payload data.
10 - The XRT84L38 framer extracts four-code signaling information from
incoming E1 payload data.
11 - The XRT84L38 framer extracts two-code signaling information from
incoming E1 payload data.
Upon receiving and extraction of signaling bits from the incoming E1 frames, the XRT84L38 framer compares
the signaling bits with the previously received ones. If there is a change of signaling data, a Signaling Update
(SIG) interrupt request may be generated at the end of an E1 multi-frame. The user can thus be notified of a
Change of Signaling Data event.
To enable the Signaling Update interrupt, the Signaling Change Interrupt Enable bit of the Framer Interrupt En-
able Register (FIER) has to be set. In addition, the T1/E1 Framer Interrupt Enable bit of the Block Interrupt En-
able Register (BIER) needs to be one.
390
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The table below shows configurations of the Signaling Change Interrupt Enable bit of the Framer Interrupt En-
able Register.
FRAMER INTERRUPT ENABLE REGISTER (FIER) (INDIRECT ADDRESS = 0XNAH, 0X05H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
5
Signaling Change
Interrupt Enable
R/W
0 - The Signaling Update interrupt is disabled.
1 - The Signaling Update interrupt is enabled.
The table below shows configurations of the T1/E1 Framer Interrupt Enable bit of the Block Interrupt Enable
Register.
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X00H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1
T1/E1 Framer
Interrupt Enable
R/W
0 - Every interrupt generated by the Framer Interrupt Status Register
(FISR) is disabled.
1 - Every interrupt generated by the Framer Interrupt Status Register
(FISR) is enabled.
When these interrupt enable bits are set and the signaling information received is changed, the E1 Receive
Framer block will set the Signaling Updated status bit of the Framer Interrupt Status Register (FISR) to one.
This status indicator is valid until the Framer Interrupt Status Register is read. Reading this register clears the
associated interrupt if Reset-Upon-Read is selected in Interrupt Control Register (ICR). Otherwise, a write-to-
clear operation by the microprocessor is required to reset these status indicators.
The table below shows the Signaling Update status bits of the Framer Interrupt Status Register.
FRAMER INTERRUPT STATUS REGISTER (FISR) (INDIRECT ADDRESS = 0XNAH, 0X04H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
5
Signaling Updated
RUR /
WC
0 - There is no change of signaling information in the incoming E1 payload
data.
1 - There is change of signaling information in the incoming E1 payload
data.
Now, there is only one problem remains. Since there are thirty two DS0 channels in E1, how do we know sig-
naling information of which channel is changed?
To solve this problem, the XRT84L38 provides three 8-bit Signaling Change Registers to indicate the chan-
nel(s) which signaling data change had occurred over the last E1 multi-frame period. Each bit of the Signaling
Change Registers represents one timeslot of the E1 frame. If any particular bit is zero, it means there is no
change of signaling data occurred in that particular timeslot over the last E1 multi-frame period. If any particular
bit is one, it means there is change of signaling data occurred over the last E1 multi-frame period.
391
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The table below shows configurations of the Signaling Change Registers.
SIGNALING CHANGE REGISTERS (SCR) (INDIRECT ADDRESS = 0XN0H, 0X0DH - 0X10H)
LOCATION \ BIT
0xn0H - 0x0DH
0xn0H - 0x0EH
0xn0H - 0x0FH
0xn0H - 0x0FH
BIT 7
Ch 0
BIT 6
Ch 1
BIT 5
Ch 2
BIT 4
Ch 3
BIT 3
Ch 4
BIT 2
Ch 5
BIT 1
Ch 6
BIT 0
Ch 7
Ch 8
Ch 9
Ch 10
Ch 18
Ch 26
Ch 11
Ch 19
Ch 27
Ch 12
Ch 20
Ch 28
Ch 13
Ch 21
Ch 29
Ch 14
Ch 22
Ch 30
Ch 15
Ch 23
Ch 31
Ch 16
Ch 24
Ch 17
Ch 25
By reading contents of the Signaling Update status bits of the Framer Interrupt Status Register and the Signal-
ing Change Registers, the user can clearly identify which one(s) of the thirty-two DS0 channels has changed
signaling information over the last multi-frame period.
Depending on configurations of the XRT84L38 framer, the signaling bits can be extracted from the incoming E1
frame and direct to all or any one of the following destinations:
• Signaling data is stored to Receive Signaling Register Array (RSRA) of each channel
• Signaling data is sent to the Terminal Equipment through the Receive Signaling Output pin (RxSig_n)
• Signaling data is sent to the Terminal Equipment through the Receive Overhead Output pin (RxOH_n)
• Signaling data is embedded into the output PCM data sending towards the Terminal Equipment through the
Receive Serial Output pin (RxSer_n)
The follow sections discuss how to configure the XRT84L38 framer to extract signaling information bits and
send them to different destinations.
12.4.1.1 Store Signaling Bits into RSRA Register Array
The four least significant bits of the Receive Signaling Register Array (RSRA) of each timeslot can be used to
store received signaling data. The user can read these bits through microprocessor access. If the XRT84L38
framer is configure to extract signaling bits from incoming E1 payload data, the E1 Receive Framer block will
strip off the CAS signaling bits from time slot 16 of the incoming E1 frames and store them into appropriate lo-
cations of the RSRA. The extraction of signaling bit from E1 PCM data is done on a per-channel basis. The Bit
3 of RSRA register is used to hole Signaling bit A. Bit 2 is used to hold Signaling bit B. Bit 1 is used to hold Sig-
naling bit C. Bit 0 is used to hold Signaling bit D.
The table below shows the four least significant bits of the Receive Signaling Register Array.
RECEIVE SIGNALING REGISTER ARRAY (RSRA) (INDIRECT ADDRESS = 0XN4H, 0X00H - 0X1FH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3
2
1
0
Signaling Bit A
Signaling Bit B
Signaling Bit C
Signaling Bit D
R/W
R/W
R/W
R/W
This bit is used to store Signaling Bit A that is received and extracted.
This bit is used to store Signaling Bit B that is received and extracted.
This bit is used to store Signaling Bit C that is received and extracted.
This bit is used to store Signaling Bit D that is received and extracted.
12.4.1.2 Outputting Signaling Bits through RxSig_n Pin
The XRT84L38 framer can be configure to output extracted signaling bits to external equipment through the
RxSig_n pins. This pin is a multiplexed I/O pin with two functions:
• RxTSb[0]_n - Receive Timeslot Number Bit [0] Output pin
• RxSig_n - Receive Signaling Output pin
392
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
When the Receive Fractional E1 bit of the Receive Interface Control Register (RICR) is set to 0, this pin is con-
figured as RxTSb[0]_n pin, it outputs bit 0 of the timeslot number of the E1 PCM data that is receiving.
When the Receive Fractional E1 bit of the Receive Interface Control Register (RICR) is set to 1, this pin is con-
figured as RxSig_n pin, it acts as an output source for the signaling bits to be received in the inbound E1
frames.
The table below shows configurations of the Receive Fractional E1 bit of the Receive Interface Control Register
(RICR).
RECEIVE INTERFACE CONTROL REGISTER (RICR) (INDIRECT ADDRESS = 0XN0H, 0X20H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
4
Receive Fractional
E1
R/W
This READ/WRITE bit-field permits the user to determine which one of the
two functions the multiplexed I/O pin of RxTSb[0]_n/RxSig_n is spotting.
0 - This pin is configured as RxTSb[0]_n pin, it outputs bit 0 of the timeslot
number of the E1 PCM data that is receiving.
1 - This pin is configured as RxSig_n pin, it acts as an output source for the
signaling bits to be received in the inbound E1 frames
Figure 125 below is a timing diagram of the RxSig_n output pin. Please note that the Signaling Bit A of a cer-
tain timeslot coincides with Bit 3 of the Received serial output data; Signaling Bit B coincides with Bit 2 of the
Received serial output data; Signaling Bit C coincides with Bit 1 of the Received serial output data and Signal-
ing Bit D coincides with Bit 0 of the Received serial output data.
FIGURE 125. TIMING DIAGRAM OF RXSIG_N OUTPUT PIN
Timeslot 0
Timeslot 5
Timeslot 6
Input Data
Timeslot 16
Input Data
RxSerClk
RxSer
RxSig
A B C D
A B C D
A B C D
A B C D
12.4.1.3 Outputting Signaling Bits from RxOH_n Pin
The XRT84L38 framer can be configure to output extracted signaling bits to external equipment through the
Receive Overhead RxOH_n output pins.
The RxOH_n pin can acts as an output source for the signaling bits to be received in the inbound E1 frames.
When this pin is chosen as the output source for the signaling bits, any data presents in time slot 16 of the in-
coming E1 frames would be presented onto the pin directly.
Please note that the Signaling bit A of Channel 1-15 coincides with Bit 1 of the PCM data; Signaling bit B Chan-
nel 1-15 coincides with Bit 2 of the PCM data; Signaling bit C Channel 1-15 coincides with Bit 3 of the PCM;
Signaling bit D Channel 1-15 coincides with Bit 4 of the PCM data.
Similarly, the Signaling bit A of Channel 17-31 coincides with Bit 5 of the PCM data; Signaling bit B Channel
17-31 coincides with Bit 6 of the PCM data; Signaling bit C Channel 17-31 coincides with Bit 7 of the PCM; Sig-
naling bit D Channel 17-31 coincides with Bit 8 of the PCM data.
Figure 126 below is a timing diagram of the RxOH_n output pin.
FIGURE 126. TIMING DIAGRAM OF THE RXOH_N OUTPUT PIN
393
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
(REDRAW) Figure ?: Timing diagram of the RxOH_n Output pin
The Receive Signaling Output Enable bit of the Receive Signaling Control Register (RSCR) determines wheth-
er the extracted signaling bits will be sent through the Receive Overhead Output pin (RxOH_n) to external
equipments. The table below shows configurations of the Receive Overhead Output Enable bit of the Receive
Signaling Control Register.
RECEIVE SIGNALING CONTROL REGISTER (RSCR) (INDIRECT ADDRESS = 0XN2H, 0XA0H - 0XBFH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
5
Receive Signaling
Output Enable
R/W
0 - The XRT84L38 framer will not send extracted signaling bits from the
incoming E1 payload data to external equipment through the Receive
Overhead Output pin (RxOH_n).
1 - The XRT84L38 framer will send extracted signaling bits from the incom-
ing E1 payload data to external equipment through the Receive Overhead
Output pin (RxOH_n).
12.4.1.4 Send Signaling Data through RxSer_n Pin
As mentioned in the above sections, signaling information embedded in the incoming E1 PCM data can be
sent to either the RSRA register array and/or sent through the Receive Signaling Output pin, at the same time,
the signaling data will be directed to the Receive Serial Data Output pin together with other incoming E1 pay-
load data. The external equipment can thus still extract signaling data from the received E1 payload data sepa-
rately.
12.4.1.5 Signaling Data Substitution
After channel conditioning, the signaling conditioning can be optionally enabled by the RSCR registers. The ac-
tual signaling bits in each channel can be replaced either with all ones or with signaling bits stored in the Re-
ceive Substitution Signaling Register (RSSR). To enable signaling substitution, the Receive Signaling Substitu-
tion Enable bit of the Receive Signaling Control Register (RSCR) has to be set to one. The table below shows
configuration of the Receive Signaling Substitution Enable bit of the Receive Signaling Control Register.
RECEIVE SIGNALING CONTROL REGISTER (RSCR) (INDIRECT ADDRESS = 0XN2H, 0XA0H - 0XBFH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
6
Receive Signaling
Substitution
Enable
R/W
0 - Signaling Substitution is disabled. The XRT84L38 framer will not
replace extracted signaling bits from the incoming E1 payload data with all
ones or with signaling bits stored in RSSR registers.
1 - Signaling Substitution is enabled. The XRT84L38 framer will replace
extracted signaling bits from the incoming E1 payload data with all ones or
with signaling bits stored in RSSR registers.
As mentioned before, the actual signaling bits in each channel can be replaced either with all ones or with sig-
naling bits stored in the Receive Substitution Signaling Register (RSSR). The table below shows configurations
of the Receive Substitution Signaling Register.
RECEIVE SUBSTITUTION SIGNALING REGISTER (RSSR) (INDIRECT ADDRESS = 0XN02H, 0X80H -
0X9FH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7-4
Reserved
R/W
394
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
RECEIVE SUBSTITUTION SIGNALING REGISTER (RSSR) (INDIRECT ADDRESS = 0XN02H, 0X80H -
0X9FH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3
SIG16-A
SIG4-A
SIG2-A
Sixteen-Code Signaling bit A
Four-Code Signaling bit A
Two-Code Signaling bit A
2
1
0
SIG16-B
SIG4-B
SIG2-A
Sixteen-Code Signaling bit B
Four-Code Signaling bit B
Two-Code Signaling bit A
SIG16-C
SIG4-A
SIG2-A
Sixteen-Code Signaling bit C
Four-Code Signaling bit A
Two-Code Signaling bit A
SIG16-D
SIG4-B
SIG2-A
Sixteen-Code Signaling bit D
Four-Code Signaling bit B
Two-Code Signaling bit A
The Receive Signaling Substitution Control [1:0] bits can select all ones substitution, two-code signaling substi-
tution, four-code signaling substitution, or sixteen-code signaling.
The XRT84L38 framer can substitute received signaling bits with all ones. Two-code signaling substitution is
done by substituting all the four signaling bits with the content of the SIG2-A bit of the register. Four-code sig-
naling substitution is done by substituting the first two signaling bits of the four with the SIG4-A bit and the last
two signaling bits of the four with the SIG4-B bit of the RSSR register. Sixteen-code signaling substitution is
implemented by substituting the four signaling bits with the content of SIG16-A, SIG16-B, SIG16-C, and SIG16-
D bits of RSSR register respectively.
The table below shows configurations of the Receive Signaling Substitution Control [1:0] bits of the Receive
Signaling Control Register.
RECEIVE SIGNALING CONTROL REGISTER (RSCR) (INDIRECT ADDRESS = 0XN2H, 0X40H - 0X5FH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3-2
Receive Signaling
Substitution Con-
trol
R/W
00 - The received signaling bits are replaced by all ones and send to the
external equipment.
01 - Two-code signaling substitution is applied to the received signaling
bits. The replaced signaling information is sent to the external equipment.
10 - Four-code signaling substitution is applied to the received signaling
bits. The replaced signaling information is sent to the external equipment.
11 - Sixteen-code signaling substitution is applied to the received signaling
bits. The replaced signaling information is sent to the external equipment.
12.5 HOW TO CONFIGURE THE FRAMER TO DETECT ALARMS AND ERROR CONDITIONS
The XRT84L38 T1/J1/E1 Octal Framer can be configured to monitor quality of received E1 frames. It can gen-
erate error indicators if the local receive framer has received error frames from the remote terminal. If corre-
sponding interrupt is enabled, the local microprocessor operation is interrupted by these error conditions. Upon
microprocessor interruption, the user can intervene by looking into the error conditions.
At the same time, the user can configure the XRT84L38 framer to receive alarms and error indications to re-
mote terminal. Different alarms and error indications will be received depending on the error condition.
395
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The section below gives a brief discussion of the error conditions that can be detected by the XRT84L38 framer
and error indications that will be generated.
12.5.1 How to configure the framer to detect AIS Alarm
Transmission of Alarm Indication Signal (AIS) or Blue Alarm by the intermediate node indicates that the equip-
ment is still functioning but unable to offer services. It is an all ones (except for framing bits) pattern which can
be used by the equipment further down the line to maintain clock recovery and timing synchronization.
The XRT84L38 framer can detect three types of AIS in E1 mode:
• Framed AIS
• Unframed AIS
• AIS16
Unframed AIS is an all ones pattern. If unframed AIS is sent, the equipment further down the line will be able to
maintain timing synchronization and be able to recover clock from the received AIS signal. However, due to the
lack of framing bits, the equipment farther down the line will not be able to maintain frame synchronization and
will declare Loss of Frame (LOF).
On the other hand, the payload portion of a framed AIS pattern is all ones. However, a framed AIS pattern still
has correct framing bits. Therefore, the equipment further down the line can still maintain frame synchroniza-
tion as well as timing synchronization. In this case, no LOF or Red alarm will be declared.
"AIS16" is an AIS alarm that only supported in E1 framing format. It is an all ones pattern in time slot 16 of each
E1 frame. As we mentioned before, time slot 16 is usually used for signaling and data link in E1, therefore, an
"AIS16" alarm is transmitted by the intermediate node to indicate that the data link channel is having a prob-
lem. Since all the other thirty one time slots are still transmitting normal data (that is, framing information and
PCM data), therefore, the equipment further down the line can still maintain frame synchronization, timing syn-
chronization as well as receiving PCM data. In this case, no LOF or Red alarm will be declared by the equip-
ments further down the line. However, a CAS Multi-frame Yellow Alarm will be sent by the equipment further
down the line to indicate the loss of CAS Multi-frame alignment.
The Alarm indication logic within the Receive Framer block of the XRT84L38 framer monitors the incoming E1
frames for AIS (both framed and unframed) and AIS16 errors.
AIS alarm condition are detected and declared according to the following procedure:
1. The incoming E1 frames are monitored for AIS detection. AIS detection is defined as an unframed or
framed pattern with less than three zeros in two consecutive frames. In the case of framed AIS, time slot 0
is excluded.
2. An AIS detection counter within the Receive Framer block of the XRT84L38 counts the occurrences of AIS
detection over a 4 ms interval. It will indicate a valid AIS flag when thirteen or more of a possible sixteen
AIS are detected.
3. Each 4 ms interval with a valid AIS flag increments a flag counter which declares AIS alarm when 25 valid
flags have been collected.
Therefore, AIS condition has to be persisted for 104 ms before AIS alarm condition is declared by the
XRT84L38 framer.
If there is no valid AIS flag over a 4ms interval, the Alarm indication logic will decrement the flag counter. The
AIS alarm is removed when the counter reaches 0. That is, AIS alarm will be removed if in over 104 ms, there
is no valid AIS flag.
AIS16 alarm condition are detected and declared according to the following procedure:
1. The incoming E1 frames are monitored for AIS16 detection. AIS16 detection is defined as two consecutive
all ones time slot 16 bytes while CAS Multi-frame alignment pattern is missing or CAS Multi-frame is out of
synchronization.
2. An AIS16 detection counter within the Receive Framer block of the XRT84L38 counts the occurrences of
AIS16 detection.
3. Each valid AIS flag increments a flag counter which declares AIS alarm when 22 valid flags have been col-
lected.
396
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
If there is no valid AIS16 flag, the Alarm indication logic will decrement the flag counter. The AIS16 alarm is re-
moved when the counter reaches 0.
The Alarm Indication Signal Detection Select [1:0] bits of the Alarm Generation Register (AGR) enable the
three types of AIS detection that are supported by the XRT84L38 framer. The table below shows configurations
of the Alarm Indication Signal Detection Select [1:0] bits of the Alarm Generation Register (AGR).
ALARM GENERATION REGISTER (AGR) (INDIRECT ADDRESS = 0XN0H, 0X08H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1-0
AIS Detection
Select
R/W
00 - AIS alarm detection is disabled.
01 - Detection of unframed AIS alarm of all ones pattern is enabled.
10 - Detection of AIS16 alarm is enabled.
11 - Detection of framed AIS alarm of all ones pattern except for framing
bits is enabled.
If detection of unframed or framed AIS alarm is enabled by the user and if AIS is present in the incoming E1
frame, the XRT84L38 framer can generate a Receive AIS State Change interrupt associated with the setting of
Receive AIS State Change bit of the Alarm and Error Status Register to one.
To enable the Receive AIS State Change interrupt, the Receive AIS State Change Interrupt Enable bit of the
Alarm and Error Interrupt Enable Register (AEIER) have to be set to one. In addition, the Alarm and Error Inter-
rupt Enable bit of the Block Interrupt Enable Register (BIER) needs to be one.
The table below shows configurations of the Receive AIS State Change Interrupt Enable bit of the Alarm and
Error Interrupt Enable Register (AEIER).
ALARM AND ERROR INTERRUPT ENABLE REGISTER (AEIER) (INDIRECT ADDRESS = 0XNAH, 0X03H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1
Receive AIS State
Change Interrupt
Enable
R/W
0 - The Receive AIS State Change interrupt is disabled.
1 - The Receive AIS State Change interrupt is enabled.
The table below shows configurations of the Alarm and Error Interrupt Enable bit of the Block Interrupt Enable
Register.
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X01H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1
Alarm and Error
Interrupt Enable
R/W
0 - Every interrupt generated by the Alarm and Error Interrupt Status Reg-
ister (AEISR) is disabled.
1 - Every interrupt generated by the Alarm and Error Interrupt Status Reg-
ister (AEISR) is enabled.
When these interrupt enable bits are set and AIS is present in the incoming E1 frame, the XRT84L38 framer
will declare AIS by doing the following:
• Set the read-only Receive AIS State bit of the Alarm and Error Status Register (AESR) to one indicating
there is AIS alarm detected in the incoming E1 frame.
• Set the Receive AIS State Change bit of the Alarm and Error Status Register to one indicating there is a
change in state of AIS. This status indicator is valid until the Framer Interrupt Status Register is read.
397
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
Reading this register clears the associated interrupt if Reset-Upon-Read is selected in Interrupt Control Regis-
ter (ICR). Otherwise, a write-to-clear operation by the microprocessor is required to reset these status indica-
tors.
The table below shows the Receive AIS State Change status bits of the Alarm and Error Status Register.
ALARM AND ERROR STATUS REGISTER (AESR) (INDIRECT ADDRESS = 0XNAH, 0X02H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1
Receive AIS State
Change
RUR /
WC
0 - There is no change of AIS state in the incoming E1 payload data.
1 - There is change of AIS state in the incoming E1 payload data.
The Receive AIS State bit of the Alarm and Error Status Register (AESR), on the other hand, is a read-only bit
indicating there is AIS alarm detected in the incoming E1 frame.
The table below shows the Receive AIS State status bits of the Alarm and Error Status Register.
ALARM AND ERROR STATUS REGISTER (AESR) (INDIRECT ADDRESS = 0XNAH, 0X02H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
6
Receive AIS State
R
0 - There is no AIS alarm condition detected in the incoming E1 payload
data.
1 - There is AIS alarm condition detected in the incoming E1 payload data.
12.5.2 How to configure the framer to detect Red Alarm
The Alarm indication logic within the Receive Framer block of the XRT84L38 framer monitors the incoming E1
frames for red alarm or Loss of Frame (LOF) condition. Red alarm condition are detected and declared accord-
ing to the following procedure:
1. The red alarm is detected by monitoring the occurrence of Loss of Frame (LOF) over a 4 ms interval.
2. An LOF valid flag will be posted on the interval when one or more LOF occurred during the interval.
3. Each interval with a valid LOF flag increments a flag counter which declares RED alarm when 25 valid
intervals have been accumulated.
4. An interval without valid LOF flag decrements the flag counter. The Red alarm is removed when the
counter reaches zero.
If LOF condition is present in the incoming E1 frame, the XRT84L38 framer can generate a Receive Red Alarm
State Change interrupt associated with the setting of Receive Red Alarm State Change bit of the Alarm and Er-
ror Status Register to one.
To enable the Receive Red Alarm State Change interrupt, the Receive Red Alarm State Change Interrupt En-
able bit of the Alarm and Error Interrupt Enable Register (AEIER) has to be set to one. In addition, the Alarm
and Error Interrupt Enable bit of the Block Interrupt Enable Register (BIER) needs to be one.
398
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The table below shows configurations of the Receive Red Alarm State Change Interrupt Enable bit of the Alarm
and Error Interrupt Enable Register (AEIER).
ALARM AND ERROR INTERRUPT ENABLE REGISTER (AEIER) (INDIRECT ADDRESS = 0XNAH, 0X03H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
2
ReceiveRedAlarm
State Change
Interrupt Enable
R/W
0 - The Receive Red Alarm State Change interrupt is disabled. No Receive
Loss of Frame (RxLOF) interrupt will be generated upon detection of LOF
condition.
1 - The Receive Red Alarm State Change interrupt is enabled. Receive
Loss of Frame (RxLOF) interrupt will be generated upon detection of LOF
condition.
The table below shows configurations of the Alarm and Error Interrupt Enable bit of the Block Interrupt Enable
Register.
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X01H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1
Alarm and Error
Interrupt Enable
R/W
0 - Every interrupt generated by the Alarm and Error Interrupt Status Reg-
ister (AEISR) is disabled.
1 - Every interrupt generated by the Alarm and Error Interrupt Status Reg-
ister (AEISR) is enabled.
When these interrupt enable bits are set and Red Alarm is present in the incoming E1 frame, the XRT84L38
framer will declare Red Alarm by doing the following:
• Set the read-only Receive Red Alarm State bit of the Alarm and Error Status Register (AESR) to one indicat-
ing there is Red Alarm detected in the incoming E1 frame.
• Set the Receive Red Alarm State Change bit of the Alarm and Error Status Register to one indicating there is
a change in state of Red Alarm. This status indicator is valid until the Framer Interrupt Status Register is
read.
Reading this register clears the associated interrupt if Reset-Upon-Read is selected in Interrupt Control Regis-
ter (ICR). Otherwise, a write-to-clear operation by the microprocessor is required to reset these status indica-
tors.
The table below shows the Receive Red Alarm State Change status bits of the Alarm and Error Status Regis-
ter.
ALARM AND ERROR STATUS REGISTER (AESR) (INDIRECT ADDRESS = 0XNAH, 0X02H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
2
ReceiveRedAlarm
State Change
RUR /
WC
0 - There is no change of Red Alarm state in the incoming E1 payload
data.
1 - There is change of Red Alarm state in the incoming E1 payload data.
The Receive Red Alarm State bit of the Alarm and Error Status Register (AESR), on the other hand, is a read-
only bit indicating there is Red Alarm detected in the incoming E1 frame.
399
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The table below shows the Receive Red Alarm State status bits of the Alarm and Error Status Register.
ALARM AND ERROR STATUS REGISTER (AESR) (INDIRECT ADDRESS = 0XNAH, 0X02H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
ReceiveRedAlarm
State
R
0 - There is no Red Alarm condition detected in the incoming E1 payload
data.
1 - There is Red Alarm condition detected in the incoming E1 payload
data.
12.5.3 How to configure the framer to detect Yellow Alarm
The Alarm indication logic within the Receive Framer block of the XRT84L38 framer monitors the incoming E1
frames for Yellow Alarm condition. The yellow alarm is detected and declared according to the following proce-
dure:
1. Monitor the occurrence of Yellow Alarm pattern over a 4 ms interval. A YEL valid flag will be posted on the
interval when Yellow Alarm pattern occurred during the interval.
2. Each interval with a valid YEL flag increments a flag counter which declares YEL alarm when 80 valid
intervals have been accumulated.
3. An interval without valid YEL flag decrements the flag counter. The YEL alarm is removed when the
counter reaches zero.
If Yellow Alarm condition is present in the incoming E1 frame, the XRT84L38 framer can generate a Receive
Yellow Alarm State Change interrupt associated with the setting of Receive Yellow Alarm State Change bit of
the Alarm and Error Status Register to one.
To enable the Receive Yellow Alarm State Change interrupt, the Receive Yellow Alarm State Change Interrupt
Enable bit of the Alarm and Error Interrupt Enable Register (AEIER) has to be set to one. In addition, the Alarm
and Error Interrupt Enable bit of the Block Interrupt Enable Register (BIER) needs to be one.
The table below shows configurations of the Receive Yellow Alarm State Change Interrupt Enable bit of the
Alarm and Error Interrupt Enable Register (AEIER).
ALARM AND ERROR INTERRUPT ENABLE REGISTER (AEIER) (INDIRECT ADDRESS = 0XNAH, 0X03H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
0
Receive Yellow
Alarm State
Change Interrupt
Enable
R/W
0 - The Receive Yellow Alarm State Change interrupt is disabled. Any state
change of Receive Yellow Alarm will not generate an interrupt.
1 - The Receive Yellow Alarm State Change interrupt is enabled. Any state
change of Receive Yellow Alarm will generate an interrupt.
The table below shows configurations of the Alarm and Error Interrupt Enable bit of the Block Interrupt Enable
Register.
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X01H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1
Alarm and Error
Interrupt Enable
R/W
0 - Every interrupt generated by the Alarm and Error Interrupt Status Reg-
ister (AEISR) is disabled.
1 - Every interrupt generated by the Alarm and Error Interrupt Status Reg-
ister (AEISR) is enabled.
400
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
When these interrupt enable bits are set and Yellow Alarm is present in the incoming E1 frame, the XRT84L38
framer will declare Yellow Alarm by doing the following:
• Set the Receive Yellow Alarm State Change bit of the Alarm and Error Status Register to one indicating there
is a change in state of Yellow Alarm. This status indicator is valid until the Framer Interrupt Status Register is
read.
Reading this register clears the associated interrupt if Reset-Upon-Read is selected in Interrupt Control Regis-
ter (ICR). Otherwise, a write-to-clear operation by the microprocessor is required to reset these status indica-
tors.
The table below shows the Receive Yellow Alarm State Change status bits of the Alarm and Error Status Reg-
ister.
ALARM AND ERROR STATUS REGISTER (AESR) (INDIRECT ADDRESS = 0XNAH, 0X02H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
0
Receive Yellow
Alarm State
Change
RUR /
WC
0 - There is no change of Yellow Alarm state in the incoming E1 payload
data.
1 - There is change of Yellow Alarm state in the incoming E1 payload data.
12.5.4 How to configure the framer to detect CAS Multi-frame Yellow Alarm
The Alarm indication logic within the Receive Framer block of the XRT84L38 framer monitors the incoming E1
frames for CAS Multi-frame Yellow Alarm condition. The CAS Multi-frame Yellow Alarm is detected and de-
clared according to the following procedure:
1. Monitor the occurrence of CAS Multi-frame Yellow Alarm pattern over a 4 ms interval. An MYEL valid flag
will be posted on the interval when CAS Multi-frame Yellow Alarm pattern occurred during the interval.
2. Each interval with a valid MYEL flag increments a flag counter which declares MYEL alarm when 80 valid
intervals have been accumulated.
3. An interval without valid MYEL flag decrements the flag counter. The MYEL alarm is removed when the
counter reaches zero.
If CAS Multi-frame Yellow Alarm condition is present in the incoming E1 frame, the XRT84L38 framer can gen-
erate a Receive CAS Multi-frame Yellow Alarm State Change interrupt associated with the setting of Receive
CAS Multi-frame Yellow Alarm State Change bit of the Alarm and Error Status Register to one.
To enable the Receive CAS Multi-frame Yellow Alarm State Change interrupt, the Receive CAS Multi-frame
Yellow Alarm State Change Interrupt Enable bit of the Alarm and Error Interrupt Enable Register (AEIER) has
to be set to one. In addition, the Alarm and Error Interrupt Enable bit of the Block Interrupt Enable Register
(BIER) needs to be one.
The table below shows configurations of the Receive CAS Multi-frame Yellow Alarm State Change Interrupt
Enable bit of the Alarm and Error Interrupt Enable Register (AEIER).
ALARM AND ERROR INTERRUPT ENABLE REGISTER (AEIER) (INDIRECT ADDRESS = 0XNAH, 0X03H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
5
Receive CAS
Multi-frame Yellow
Alarm State
R/W
0 - The Receive CAS Multi-frame Yellow Alarm State Change interrupt is
disabled. Any state change of Receive CAS Multi-frame Yellow Alarm will
not generate an interrupt.
Change Interrupt
Enable
1 - The Receive CAS Multi-frame Yellow Alarm State Change interrupt is
enabled. Any state change of Receive CAS Multi-frame Yellow Alarm will
generate an interrupt.
401
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The table below shows configurations of the Alarm and Error Interrupt Enable bit of the Block Interrupt Enable
Register.
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X01H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1
Alarm and Error
Interrupt Enable
R/W
0 - Every interrupt generated by the Alarm and Error Interrupt Status Reg-
ister (AEISR) is disabled.
1 - Every interrupt generated by the Alarm and Error Interrupt Status Reg-
ister (AEISR) is enabled.
When these interrupt enable bits are set and CAS Multi-frame Yellow Alarm is present in the incoming E1
frame, the XRT84L38 framer will declare CAS Multi-frame Yellow Alarm by doing the following:
• Set the Receive CAS Multi-frame Yellow Alarm State Change bit of the Alarm and Error Status Register to
one indicating there is a change in state of CAS Multi-frame Yellow Alarm. This status indicator is valid until
the Framer Interrupt Status Register is read.
Reading this register clears the associated interrupt if Reset-Upon-Read is selected in Interrupt Control Regis-
ter (ICR). Otherwise, a write-to-clear operation by the microprocessor is required to reset these status indica-
tors.
The table below shows the Receive CAS Multi-frame Yellow Alarm State Change status bits of the Alarm and
Error Status Register.
ALARM AND ERROR STATUS REGISTER (AESR) (INDIRECT ADDRESS = 0XNAH, 0X02H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
5
Receive CAS
Multi-frame Yellow
Alarm State
RUR /
WC
0 - There is no change of CAS Multi-frame Yellow Alarm state in the incom-
ing E1 payload data.
1 - There is change of CAS Multi-frame Yellow Alarm state in the incoming
E1 payload data.
Change
12.5.5 How to configure the framer to detect Bipolar Violation
The line coding for the E1 signal should be bipolar. That is, a binary "0" is received as zero volts while a binary
"1" is received as either a positive or negative pulse, opposite in polarity to the previous pulse. A Bipolar Viola-
tion or BPV occurs when the alternate polarity rule is violated. The Alarm indication logic within the Receive
Framer block of the XRT84L38 framer monitors the incoming E1 frames for Bipolar Violations.
If a Bipolar Violation is present in the incoming E1 frame, the XRT84L38 framer can generate a Receive Bipo-
lar Violation interrupt associated with the setting of Receive Bipolar Violation bit of the Alarm and Error Status
Register to one.
To enable the Receive Bipolar Violation interrupt, the Receive Bipolar Violation Interrupt Enable bit of the Alarm
and Error Interrupt Enable Register (AEIER) has to be set to one. In addition, the Alarm and Error Interrupt En-
able bit of the Block Interrupt Enable Register (BIER) needs to be one.
402
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The table below shows configurations of the Receive Bipolar Violation Interrupt Enable bit of the Alarm and Er-
ror Interrupt Enable Register (AEIER).
ALARM AND ERROR INTERRUPT ENABLE REGISTER (AEIER) (INDIRECT ADDRESS = 0XNAH, 0X03H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3
Receive Bipolar
Violation Interrupt
Enable
R/W
0 - The Receive Bipolar Violation interrupt is disabled. Occurrence of one
or more bipolar violations will not generate an interrupt.
1 - The Receive Bipolar Violation interrupt is enabled. Occurrence of one
or more bipolar violations will generate an interrupt.
The table below shows configurations of the Alarm and Error Interrupt Enable bit of the Block Interrupt Enable
Register.
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X01H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1
Alarm and Error
Interrupt Enable
R/W
0 - Every interrupt generated by the Alarm and Error Interrupt Status Reg-
ister (AEISR) is disabled.
1 - Every interrupt generated by the Alarm and Error Interrupt Status Reg-
ister (AEISR) is enabled.
When these interrupt enable bits are set and one or more Bipolar Violations are present in the incoming E1
frame, the XRT84L38 framer will declare Receive Bipolar Violation by doing the following:
• Set the Receive Bipolar Violation bit of the Alarm and Error Status Register to one indicating there are one or
more Bipolar Violations. This status indicator is valid until the Framer Interrupt Status Register is read.
Reading this register clears the associated interrupt if Reset-Upon-Read is selected in Interrupt Control Regis-
ter (ICR). Otherwise, a write-to-clear operation by the microprocessor is required to reset these status indica-
tors.
The table below shows the Receive Bipolar Violation status bits of the Alarm and Error Status Register.
ALARM AND ERROR STATUS REGISTER (AESR) (INDIRECT ADDRESS = 0XNAH, 0X02H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3
Receive Bipolar
Violation State
Change
RUR /
WC
0 - There is no change of Bipolar Violation state in the incoming E1 pay-
load data.
1 - There is change of Bipolar Violation state in the incoming E1 payload
data.
12.5.6 How to configure the framer to detect Loss of Signal
A Loss of Signal or LOS occurs when neither RPOS nor RNEG inputs of the framer receives a high level input
for 32 consecutive bit times. The Alarm indication logic within the Receive Framer block of the XRT84L38 fram-
er monitors the incoming E1 frames for Loss of Signal conditions. If used in conjunction with EXAR LIUs, for
example, the XRT83L3x family, the XRT84L38 framer also declares LOS when the Receive LOS (RxLOS) in-
put pin is pulled HIGH.
The removal of LOS condition is through detection of 12.5% ones over 32 consecutive bits. In the other words,
XRT84L38 framer will remove LOS alarm when there is no 4 consecutive zeros received.
NOTE: The implementation of LOS detection and removal only apply to B8ZS coded bipolar inputs.
403
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
If Loss of Signal condition is present in the incoming E1 frame, the XRT84L38 framer can generate a Receive
Loss of Signal interrupt associated with the setting of Receive Loss of Signal bit of the Alarm and Error Status
Register to one.
To enable the Receive Loss of Signal interrupt, the Receive Loss of Signal Interrupt Enable bit of the Alarm and
Error Interrupt Enable Register (AEIER) has to be set to one. In addition, the Alarm and Error Interrupt Enable
bit of the Block Interrupt Enable Register (BIER) needs to be one.
The table below shows configurations of the Receive Loss of Signal Interrupt Enable bit of the Alarm and Error
Interrupt Enable Register (AEIER).
ALARM AND ERROR INTERRUPT ENABLE REGISTER (AEIER) (INDIRECT ADDRESS = 0XNAH, 0X03H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
4
Receive Loss of
Signal Interrupt
Enable
R/W
0 - The Receive Loss of Signal interrupt is disabled. Occurrence of Loss of
Signals will not generate an interrupt.
1 - The Receive Loss of Signal interrupt is enabled. Occurrence of Loss of
Signals will generate an interrupt.
The table below shows configurations of the Alarm and Error Interrupt Enable bit of the Block Interrupt Enable
Register.
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X01H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1
Alarm and Error
Interrupt Enable
R/W
0 - Every interrupt generated by the Alarm and Error Interrupt Status Reg-
ister (AEISR) is disabled.
1 - Every interrupt generated by the Alarm and Error Interrupt Status Reg-
ister (AEISR) is enabled.
When these interrupt enable bits are set and one or more Loss of Signals are present in the incoming E1
frame, the XRT84L38 framer will declare Receive Loss of Signal by doing the following:
• ·Set the Receive Loss of Signal bit of the Alarm and Error Status Register to one indicating there is one or
more Loss of Signals. This status indicator is valid until the Framer Interrupt Status Register is read.
Reading this register clears the associated interrupt if Reset-Upon-Read is selected in Interrupt Control Regis-
ter (ICR). Otherwise, a write-to-clear operation by the microprocessor is required to reset these status indica-
tors.
The table below shows the Receive Loss of Signal status bits of the Alarm and Error Status Register.
ALARM AND ERROR STATUS REGISTER (AESR) (INDIRECT ADDRESS = 0XNAH, 0X02H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
4
Receive Loss of
Signal State
RUR /
WC
0 - There is no change of Loss of Signal state in the incoming E1 payload
data.
1 - There is change of Loss of Signal state in the incoming E1 payload
data.
13.0 DS1 HDLC CONTROLLER BLOCK
13.1 DS1 TRANSMIT HDLC CONTROLLER BLOCK
404
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
13.1.1 Description of the DS1 Transmit HDLC Controller Block
XRT84L38 allows user to insert data link information to outbound DS1 frames. The data link information in
DS1raming format mode can be inserted from:
• DS1 Transmit Overhead Input Interface Block
• DS1 Transmit HDLC Controller
• DS1 Transmit Serial Input Interface
The Transmit Data Link Source Select [1:0] bits, within the Transmit Data Link Select Register (TSDLSR) deter-
mine source of the data link bits (Facility Data Link (FDL) bits in ESF framing format mode, Signaling Framing
(Fs) bits in SLC®96 framing format mode and Remote Signaling (R) bits in T1DM framing format mode) to be
inserted into the outgoing DS1 frames.
The table below shows configuration of the Transmit Data Link Source Select [1:0] bits of the Transmit Data
Link Select Register (TSDLSR).
TRANSMIT DATA LINK SELECT REGISTER (TSDLSR) (INDIRECT ADDRESS = 0XN0H, 0X0AH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1-0
Transmit Data
Link Source
Select [1:0]
R/W
00 - The data link bits are inserted into the framer through the Transmit HDLC
Controller.
01 - The data link bits are inserted into the framer through the Transmit Serial
Data input Interface via the TxSer_n pins.
10 - The data link bits are inserted into the framer through the Transmit Over-
head Input Interface via the TxOH_n pins.
11 - The data link bits are forced into 1.
If the Transmit Data Link Source Select bits of the Transmit Data Link Select Register are set to 00, the Trans-
mit HDLC Controller block becomes input source of the data link bits in outgoing DS1 frames.
Each of the eight framers within the XRT84L38 device contains a DS1 Transmit High-level Data Link Controller
(HDLC) block. The function of this block is to provide a serial data link channel in DS1 mode through the follow-
ing:
• Facility Data Link (FDL) bits in ESF framing format mode
• Signaling Framing (Fs) bits in SLC®96 framing format mode
• Remote Signaling (R) bits in T1DM framing format mode
• D or E signaling timeslot channel
Data link bits are automatically inserted into the Facility Data Link (FDL) bits in ESF framing format mode, Sig-
naling Framing (Fs) bits in SLC®96 framing format mode and Remote Signaling (R) bits in T1DM framing for-
mat mode or forced to 1 by the framer. Additionally, XRT84L38 allows the user to define any one of ones of the
twenty-four DS0 timeslots to be D or E channel. We will discuss how to configure XRT84L38 to transmit data
link information through D or E channels in later section.
The DS1 Transmit HDLC Controller block contains three major functional modules associated with DS1 fram-
ing formats. They are the:
• SLC®96 Data Link Controller
• LAPD Controller
• Bit-Oriented Signaling Processor.
There are two 96-byte transmit message buffers in shared memory for each of the eight framers to transmit da-
ta link information. When one message buffer is filled up, the Transmit HDLC Controller automatically switches
to the next message buffer to load data link messages. These two message buffers ping-pong among each
other for data link message transmission.
405
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The SLC®96 Enable bit and the LAPD Enable bit of the Data Link Control Register (DLCR) determines which
one of the three functions is performed by the Transmit HDLC Controller block. The table below shows configu-
ration of the SLC®96 Enable bit of the Data Link Control Register (DLCR).
DATA LINK CONTROL REGISTER (DLCR) INDIRECT ADDRESS = 0XN0H, 0X13H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
SLC®96 Enable
R/W
0 - In SLC®96 framing mode, the data link transmission is disabled. The framer
transmits the regular SF framing bits.
In ESF framing mode, the framer transmits regular ESF framing bits and Facility
Data Link (FDL) bits.
1 - In SLC®96 framing mode, the data link transmission is enabled.
In ESF framing mode, the framer transmits SLC®96-like message in the Facility
Data Link bits.
The table below shows configuration of the LAPD Enable bit of the Data Link Control Register (DLCR).
DATA LINK CONTROL REGISTER (DLCR) (INDIRECT ADDRESS = 0XN0H, 0X13H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
0
LAPD Enable
R/W
0 - The Transmit HDLC Controller will send out Bit-Oriented Signaling (BOS)
message.
1 - The Transmit HDLC Controller will send out LAPD protocol or so-called Mes-
sage-Oriented Signaling (MOS) message.
13.1.2 How to configure XRT84L38 to transmit data link information through D or E Channels
The XRT84L38 can configure any one or ones of the twenty-four DS0 channels to be D or E channels. D chan-
nel is used primarily for data link applications. E channel is used primarily for signaling for circuit switching with
multiple access configurations.
The Transmit Data Conditioning Select [3:0] bits of the Transmit Channel Control Register (TCCR) of each
channel determine whether that particular channel is configured as D or E channel. These bits also determine
what type of data or signaling conditioning is applied to each channel.
TRANSMIT CHANNEL CONTROL REGISTER (TCCR) (INDIRECT ADDRESS = 0XN2H, 0X00H - 0X1FH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3-0
Transmit Data
Conditioning
Select
R/W
1111 - This channel is configured as D or E timeslot.
If the Transmit Data Conditioning Select [3:0] bits of the Transmit Channel Control Register of a particular
timeslot are set to 1111, that timeslot is configured as a D or E timeslot.
Any D or E timeslot can be configured to take data link information from the following sources:
• DS1 Transmit Overhead Output Interface Block
• DS1 Transmit HDLC Controller Block
• DS1 Transmit Serial Output Interface Block
• DS1 Transmit Fractional Input Interface Block
The Transmit D or E Channel Source Select [1:0] bits of the Transmit Data Link Select Register (TSDLSR) de-
termines which one of the above-mentioned modules to be input sources of D or E timeslot. The table below
406
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
shows configuration of the Transmit D or E Channel Source Select [1:0] bits of the Transmit Data Link Select
Register (TSDLSR).
TRANSMIT DATA LINK SELECT REGISTER (TSDLSR) (INDIRECT ADDRESS = 0XN0H, 0X0AH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3-2
Transmit D or E
Channel Source
Select [1:0]
R/W
00 - The data link bits are inserted into the D or E channel through the Transmit
Serial Data input Interface via the TxSer_n pins.
01 - The data link bits are inserted into the D or E channel through the Transmit
HDLC Controller.
10 - The data link bits are inserted into the D or E channel through the Transmit
Serial Data input Interface via the TxSer_n pins.
11 - The data link bits are inserted into the D or E channel through the Transmit
Fractional T1 Input Interface via the TxFrT1_n pins.
For the Transmit HDLC Controller to be input source of D or E channel, the Transmit D or E Channel Source
Select [1:0] bits of the Transmit Data Link Select Register has to be set to 01.
13.1.3 Transmit BOS (Bit Oriented Signaling) Processor
The Transmit BOS Processor handles transmission of BOS messages through the DS1 data link channel. It
determines how many repetitions a certain BOS message will be transmitted. It also inserts BOS IDLE flag se-
quence and ABORT sequence to be transmitted on the data link channel. In the later sections, we will discuss
BOS message format and how to transmit BOS message.
13.1.3.1 Description of BOS
Bit-Oriented Signaling message is a sixteen-bit pattern carries the form of:
(0d5d4d3d2d1d0011111111)
Where d5 is the MSB and d0 is the LSB. The rightmost "1" is transmitted first. Bit-Oriented Signaling message
is classified into the following two groups:
• Priority Codeword Message
• Command and Response Information
Priority Codeword message is preemptive and has the highest priority among all data link information. Priority
Codeword information indicates a condition that is affecting the quality of service and thus shall be transmitted
until the condition no longer exists. The duration of transmission should not be less than one second. Priority
codeword information may be interrupted by software for 100 milliseconds to send maintenance commands
with a minimum interval of one second between interruptions. Yellow alarm (00000000 11111111) is the only
priority message defined in standard.
Command and response information is transmitted to perform various functions. The BOS Processor send
command and response message by transmitting a minimum of 10 repetitions of the appropriate codeword
pattern. Command and response data transmission initiates action at the remote end, while the remote end
will respond by sending Bit-Oriented response message to acknowledge the received commands. The activa-
tion and deactivation of line loop-back and payload loop-back functions are this type of signal.
13.1.3.2 How to configure the BOS Processor Block to transmit BOS
This section describes how to configure the BOS Processor Block to transmit BOS message in a step-by-step
basis.
13.1.3.2.1 Step 1: Find out the next available transmit data link buffer
To transmit a bit-oriented signal, a repeating message is sent of the form (0d5d4d3d2d1d0011111111), where
the "d5d4d3d2d1d0" represents a six-bit message. The user is recommended to read Transmit Data Link Byte
Count Register for next available transmit data link buffer number.
407
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The table below shows how content of the Buffer Enable bit of the Transmit Data Link Byte Count Register
(TDLBCR) determines what the next available transmit data link buffer number is.
TRANSMIT DATA LINK BYTE COUNT REGISTER (TDLBCR) (INDIRECT ADDRESS = 0XN0H, 0X14H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Buffer Select
R
0 - The next available transmit data link buffer for sending out BOS or MOS
message is Buffer 0.
1 - The next available transmit data link buffer for sending out BOS or MOS
message is Buffer 1.
13.1.3.2.2 Step 2: Write BOS Message into transmit data link buffer
After finding out the next available transmit data link buffer, the user should write the eight bits message that
are to be transmitted in the form (0d5d4d3d2d1d00) to the first location of the next available transmit data link
buffer. The writing of these buffers is through the LAPD Buffer 0 indirect data registers and the LAPD Buffer1
indirect data registers. LAPD Buffer 0 and 1 indirect data registers have addresses 0xn6H and 0xn7H respec-
tively. There is no indirect address register for transmit data link buffer 0 and 1.
A microcontroller WRITE access to the LAPD Buffer indirect data registers will access the transmit data link
buffer and a microcontroller READ will access the receive data link buffers. The very first WRITE access to the
LAPD Buffer indirect data register will always be direct to location 0 within the transmit data link buffer.
For example, if the BOS Message to be sent is (101011) and the next available transmit data link buffer of
Channel n is 1. The user should write pattern (01010110) into transmit data link buffer 1 of Channel n. The fol-
lowing microprocessor access to the framer should be done:
WR
n7H
56H
13.1.3.2.3 Step 3: Program BOS Message transmission repetitions
The user should program the value of message transmission repetitions into the Transmit Data Link Byte Count
Register. The framer will transmit the BOS message the same number of times as was stored in the Transmit
Data Link Byte Count Register (TDLBCR) before generating the Transmit End of Transfer (TxEOT) interrupts.
If the value stored inside the Transmit Data Link Byte Count Register (TDLBCR) is set to 0, the message will be
transmitted indefinitely and no Transmit End of Transfer interrupt will be generated.
The table below shows configurations of the Transmit Data Link Byte Count [6:0] bits the Transmit Data Link
Byte Count Register (TDLBCR).
TRANSMIT DATA LINK BYTE COUNT REGISTER (TDLBCR) (INDIRECT ADDRESS = 0XN0H, 0X14H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
6-0
Transmit Data Link
Byte Count [6:0]
R/W
Value of these bits determines how many times a BOS message pattern
will be transmitted by the framer before generating the Transmit End of
Transfer (TxEOT) interrupt.
NOTE: If these bits are set to 0, the BOS message will be transmitted
indefinitely and no Transmit End of Transfer interrupts will be generated.
13.1.3.2.4 Step 4: Configure BOS Message transmission control bits
Configuration of the Data Link Control Register determines whether the BOS Processor will insert IDLE flag
character or ABORT sequence to the data link channel. It also determines how the transition between MOS
mode to BOS mode is done.
If the IDLE Insertion bit of the Data Link Control Register is set, repeated flags of value 0x7E are transmitted as
soon as the current operation is finished (defined by the value in Transmit Data Link Byte Count Register).
408
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
However, if the Transmit Data Link Byte Count value is zero, the framer will not force a flag sequence on to the
data link channel.
The table below shows configurations of the IDLE Insertion bit of the Data Link Control Register (DLCR).
DATA LINK CONTROL REGISTER (DLCR) (INDIRECT ADDRESS = 0XN0H, 0X13H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
2
IDLE Insertion
R/W
0 - No flag sequence is sent on the data link channel.
1 - The framer forces a flag sequence of value 0x7E onto the data link
channel.
If the ABORT bit of the Data Link Control Register is set, a BOS abort sequence (9 consecutive ones) is trans-
mitted on the data link channel following by all-one transmission. In other words, all data link bits will be set to
1 after the transmission of the current message byte.
The table below shows configurations of the ABORT bit of the Data Link Control Register (DLCR).
DATA LINK CONTROL REGISTER (DLCR) (INDIRECT ADDRESS = 0XN0H, 0X13H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3
ABORT
R/W
0 - No ABORT sequence is sent on the data link channel.
1 - The framer forces an ABORT sequence of pattern (111111111) onto
the data link channel. All data link bits will be set to 1 after sending the
ABORT sequence.
Switching the data link channel from MOS mode to BOS mode while a message is being transmitted will inter-
rupt the message after the octet in progress is transmitted. If the MOS ABORT bit of the Data Link Control Reg-
ister is set, a MOS ABORT sequence (a zero followed by 7 ones) will be inserted before switching. Switching
the data link from BOS to LAPD will not take place until the current operation completes if Transmit BOS byte
count is not set to zero initially. If the Transmit BOS byte count value is set to zero, the transition from BOS
mode to MOS mode will take place right after finishing the current message octet.
The table below shows configurations of the MOS ABORT bit of the Data Link Control Register (DLCR).
DATA LINK CONTROL REGISTER (DLCR) (INDIRECT ADDRESS = 0XN0H, 0X13H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
6
MOS ABORT
R/W
0 - The framer forces an MOS ABORT sequence of one zero and seven
ones (01111111) onto the data link channel during the transition from MOS
mode to BOS mode.
1 - No MOS ABORT sequence is sent on the data link channel during the
transition from MOS mode to BOS mode.
13.1.3.2.5 Step 5: Enable transmit BOS message interrupts
The BOS Processor can generate a couple of interrupts indicating the status of BOS message transmission to
the microprocessor. These are the Transmit Start of Transfer (TxSOT) interrupt and the Transmit End of Trans-
fer (TxEOT) interrupt.
To enable these interrupts, the Transmit Start of Transfer Enable bit and the Transmit End of Transfer Enable bit
of the Data Link Interrupt Enable Register (DLIER) have to be set. In addition, the HDLC Controller Interrupt
Enable bit of the Block Interrupt Enable Register (BIER) needs to be one.
409
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The table below shows configurations of the Transmit Start of Transfer Enable bit and the Transmit End of
Transfer Enable bit of the Data Link Interrupt Enable Register.
DATA LINK INTERRUPT ENABLE REGISTER (DLIER) (INDIRECT ADDRESS = 0XNAH, 0X07H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
6
Transmit Start of
Transfer Enable
R/W
0 - The Transmit Start of Transfer interrupt is disabled.
1 - The Transmit Start of Transfer interrupt is enabled.
4
Transmit End of
Transfer Enable
R/W
0 - The Transmit End of Transfer interrupt is disabled.
1 - The Transmit End of Transfer interrupt is enabled.
The table below shows configurations of the HDLC Controller Interrupt Enable bit of the Block Interrupt Enable
Register.
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X00H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3
HDLC Controller
Interrupt Enable
R/W
0 - Every interrupt generated by the HDLC Controller is disabled.
1 - Every interrupt generated by the HDLC Controller is enabled.
When these interrupt enable bits are set and the BOS message is transmitted to the data link channel, the
BOS Processor changes the Transmit Start of Transfer and Transmit End of Transfer status bits of the Data Link
Status Register (DLSR). These two status indicators are valid until the Data Link Status Register is read. Read-
ing these register clears the associated interrupt if Reset Upon Read is selected in Interrupt Control Register
(ICR). Otherwise, a write-to-clear operation by the microprocessor is required to reset these status indicators.
The table below shows the Transmit Start of Transfer and Transmit End of Transfer status bits of the Data Link
Status Register.
DATA LINK STATUS REGISTER (DLSR) (INDIRECT ADDRESS = 0XNAH, 0X06H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
6
Transmit Start of
Transfer
RUR /
WC
0 - There is no data link message to be sent to the data link channel.
1 - The HDLC Controller will send a data link message to the data link
channel.
4
Transmit End of
Transfer
RUR /
WC
0 - No data link message was sent to the data link channel.
1 - The HDLC Controller finished sending a data link message to the data
link channel.
13.1.3.2.6 Step 6: BOS message transmission
A zero is then written into the LAPD enable bit of Data Link Control Register, which sets the transmitter to Bit-
Oriented mode and kicks off the transmission process. The LAPD Controller latches these control bits of the
Data Link Control Register and send a Transmit Start of Transfer interrupt (TxSOT) to the microprocessor to in-
dicate that a BOS message will be send. After the required number of times of BOS message is sent, the
LAPD Controller generates an Transmit End of Transfer interrupt (TxEOT) to the microprocessor to indicate
that the BOS message transmission comes to an end.
410
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The table below shows configurations of the LAPD Enable bit of the Data Link Control Register (DLCR).
DATA LINK CONTROL REGISTER (DLCR) (INDIRECT ADDRESS = 0XN0H, 0X13H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
0
LAPD Enable
R/W
0 - The Transmit HDLC Controller will send out Bit-Oriented Signaling
(BOS) message.
1 - The Transmit HDLC Controller will send out LAPD protocol or so-called
Message-Oriented Signaling (MOS) message.
13.1.4 Transmit MOS (Message Oriented Signaling) or LAPD Controller
The Transmit LAPD controller implements the Message-Oriented protocol based on ITU Recommendation
Q.921 Link Access Procedures on the D-channel (LAPD) type of protocol. It provides the following functions:
• Zero stuffing
• T1/E1 transmitter interface
• Transmit message buffer access
• Frame check sequence generation
• IDLE flag insertion
• ABORT sequence generation
Two 96-byte buffers in shared memory are allocated for LAPD transmitter to reduce the frequency of micropro-
cessor interrupts and alleviate the response time requirement for microprocessor to handle each interrupt.
There are no restrictions on the length of the message. However the 96-byte buffer is deep enough to hold one
entire LAPD path or test signal identification message. Figure 127 depicts the block diagram of both transmit
and receive LAPD controller.
FIGURE 127. LAPD CONTROLLER
FCS Check
Rx Register
FCS CRC Error
Zero Deletion
RxLAPDData
Rx
State
Machine
RxLAPDAck
RxLAPDRdy
Memory
Request
&
Address
Generation
MTxClk
uP
Multi-port
Memory
Interface
(Rx) Req, Ack, Addr
(Tx) Req, Ack, Rdy, Addr
PIO & DMA
Interface
Tx
State
Machine
TxLAPDRdy
TxLAPDAck
Tx Register
Zero Stuffing
TxLAPDData
Memory
FCS Generator
In the later sections, we will briefly discuss MOS message format and how to configure the LAPD Controller to
transmit MOS message.
411
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
13.1.4.1 Discussion of MOS
Message-Oriented signals (MOS) sent by the transmit LAPD Controller are messages conforming to ITU Rec-
ommendation Q.921 LAPD protocol as defined below.
Two types of Message-Oriented signals are defined. One is a periodic performance report generated by the
source or sink T1/E1 terminals as defined by ANSI T1.403. The other is a path or test signal identification mes-
sage that may be optionally generated by a terminal or intermediate equipment on a T1/E1 circuit.
Message-oriented signals shall use the frame structure, field definitions and elements of procedure of the
LAPD protocol defined in ITU recommendation Q.921 except the address field. Performance information is car-
ried by Message-Oriented signal using LAPD protocol. The message structures of the periodic performance
report and path or test signal identification message are shown in Figure 128 in format A and format B respec-
tively.
FIGURE 128. LAPD FRAME STRUCTURE
8
7
6
5
4
3
1
2
1
0
Octet
1
8
7
6
5
4
3
2
1
Octet
1
Flag
1
Flag
1
Flag
Flag
0
1
1
1
1
0
1
1
1
1
1
0
Address
(high order)
EA
0
Address
(high order)
EA
0
SAPI
C/R
SAPI
C/R
2
3
4
2
3
4
Address
(low order)
EA
1
Address
(low order)
EA
1
TEI
TEI
Control
Control
5
.
.
5
.
.
Information
One-second counts
Information
76 octets
12
80
FCS
(first octet)
FCS
(first octet)
13
14
81
82
FCS
(second octet)
FCS
(second octet)
Flag
1
Flag
1
Flag
Flag
0
1
1
1
1
1
0
0
1
1
1
1
1
0
Format A
Format B
13.1.4.1.1 Periodic Performance Report
The ANSI T1.403 standard requires that the status of the transmission quality be reported every one-second
interval. The one-second timing may be derived from the DS1 signal or from a separate equally accurate
(±32ppm) source. The phase of the one-second periods with respect to the occurrence of error events is arbi-
trary; that is, the one-second timing does not depend on the time of occurrence of any error event. A total of
four seconds of information is transmitted so that recovery operations may be initiated in case an error corrupts
a message.
Counts of events shall be accumulated in each contiguous one-second interval. At the end of each one-second
interval, a modulo-4 counter shall be incremented, and the appropriate performance bits shall be set in bytes 5
and 6 in Format A. These octets and the octets that carry the performance bits of the preceding three one-sec-
ond intervals form the periodic performance report.
The periodic performance report is made up of 14 bytes of data. Bytes 1 to 4, 13, and 14 are the message
header and bytes 5 to 12 contain data regarding the four most-recent one-second intervals. The periodic per-
formance report message uses the SAPI/TEI value of 14.
412
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
13.1.4.1.2 Transmission-Error Event
Occurrences of transmission-error events indicate the quality of transmission. The occurrences that shall be
detected and reported are:
• CRC Error Event: A CRC-6 error event is the occurrence of a received CRC code that is not identical to the
corresponding locally calculated code.
• Severely Errored Framing Event: A severely-errored-framing event is the occurrence of two or more framing-
bit-pattern errors within a 3-ms period. Contiguous 3-ms intervals shall be examined. The 3-ms period may
coincide with the ESF. The severely-errored-framing event, while similar in form to criteria for declaring a ter-
minal has lost framing, is only designed as a performance indicator; existing terminal out-of-frame criteria will
continue to serve as the basis for terminal alarms.
• Frame-Synchronization-Bit Error Event: A frame-synchronization-bit-error event is the occurrence of a
received framing-bit-pattern not meeting the severely-errored-framing event criteria.
• Line-Code Violation event: A line-code violation event is a bipolar violation of the incoming data. A line-code
violation event for an B8ZS-coded signal is the occurrence of a received excessive zeros (EXZ) or a bipolar
violation that is not part of a zero-substitution code.
• Controlled Slip Event: A controlled-slip event is a replication, or deletion, of a T1 frame by the receiving termi-
nal. A controlled slip may occur when there is a difference between the timing of a synchronous receiving ter-
minal and the received signal.
13.1.4.1.3 Path and Test Signal Identification Message
The path identification message is used to identify the path between the source terminal and the sink terminal.
The test signal identification message is used by test signal generating equipment. Both identification messag-
es are made up of 82 bytes of data. Byte 1 to 4, 81 and 82 are the message header and bytes 5 to 80 contain
six data elements. These messages use the SAPI/TEI value of 15 to differentiate themselves from the perfor-
mance report message.
13.1.4.1.4 Frame Structure
The message structure of message-oriented signal is shown in Figure 1?2. Two format types are shown in the
figure: format A for frames which are sending performance report message and format B for frames which con-
taining a path or test signal identification message. The following abbreviations are used:
• SAPI: Service Access Point Identifier
• C/R: Command or Response
• EA: Extended Address
• TEI: Terminal Endpoint Identifier
• FCS: Frame Check Sequence
13.1.4.1.5 Flag Sequence
All frames shall start and end with the flag sequence consisting of one 0 bit followed by six contiguous 1 bits
and one 0 bit. The flag preceding the address field is defined as the opening flag. The flag following the Frame
Check Sequence (FCS) field is defined as the closing flag. The closing flag may also serve as the opening flag
of the next frame, in some applications. However, all receivers must be able to accommodate receipt of one or
more consecutive flags.
13.1.4.1.6 Address Field
The address field consists of two octets. A single octet address field is reserved for LAPB operation in order to
allow a single LAPB data link connection to be multiplexed along with LAPD data link connections.
13.1.4.1.7 Address Field Extension bit (EA)
The address field range is extended by reserving bit 1 of the address field octets to indicate the final octet of
the address field. The presence of a 1 in bit 1 of an address field octet signals that it is the final octet of the ad-
dress field. The double octet address field for LAPD operation shall have bit 1 of the first octet set to a 0 and bit
1 of the second octet set to 1.
13.1.4.1.8 Command or Response bit (C/R)
413
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The Command or Response bit identifies a frame as either a command or a response. The user side shall
send commands with the C/R bit set to 0, and responses with the C/R bit set to 1. The network side shall do the
opposite; That is, commands are sent with C/R bit set to 1, and responses are sent with C/R bit set to 0.
13.1.4.1.9 Service Access Point Identifier (SAPI)
The Service Access Point Identifier identifies a point at which data link layer services are preceded by a data
link layer entity type to a layer 3 or management entity. Consequently, the SAPI specifies a data link layer entity
type that should process a data link layer frame and also a layer 3 or management entity, which is to receive in-
formation carried by the data link layer frame. The SAPI allows 64 service access points to be specified, where
bit 3 of the address field octet containing the SAPI is the least significant binary digit and bit 8 is the most sig-
nificant. SAPI values are 14 and 15 for performance report message and path or test signal identification mes-
sage respectively.
13.1.4.1.10 Terminal Endpoint Identifier (TEI)
The TEI sub-field allows 128 values where bit 2 of the address field octet containing the TEI is the least signifi-
cant binary digit and bit 8 is the most significant binary digit. The TEI sub-field bit pattern 111 1111 (=127) is
defined as the group TEI. The group TEI is assigned permanently to the broadcast data link connection asso-
ciated with the addressed Service Access Point (SAP). TEI values other than 127 are used for the point-to-
point data link connections associated with the addressed SAP. Non-automatic TEI values (0-63) are selected
by the user, and their allocation is the responsibility of the user. The network automatically selects and allo-
cates TEI values (64-126).
13.1.4.1.11 Control Field
The control field identifies the type of frame which will be either a command or response. The control field shall
consist of one or two octets. Three types of control field formats are specified: 2-octet numbered information
transfer (I format), 2-octet supervisory functions (S format), and single-octet unnumbered information transfers
and control functions (U format). The control field for T1/E1 message is categorized as a single-octet unac-
knowledged information transfer having the value 0x03.
13.1.4.1.12 Frame Check Sequence (FCS) Field
The source of either the performance report or an identification message shall generate the frame check se-
quence. The FCS field shall be a 16-bit sequence. It shall be the ones complement of the sum (modulo 2) of:
• The remainder of xk (x15 + x14 + x13 + x12 + x11 + x10 + x9 + x8 + x7 + x6 + x5 + x4 + x3 + x2 + x + 1)
divided (modulo 2) by the generator polynomial x16 + x12 + x5 + 1, where k is the number of bits in the frame
existing between, but not including, the final bit of the opening flag and the first bit of the FCS, excluding bits
inserted for transparency, and
• The remainder of the division (modulo 2) by the generator polynomial x16 + x12 + x5 + 1, of the product of
x16 by the content of the frame existing between, but not including, the final bit of the opening flag and the
first bit of the FCS, excluding bits inserted for transparency.
As a typical implementation at the transmitter, the initial content of the register of the device computing the re-
mainder of the division is preset to all 1s and is then modified by division by the generator polynomial on the
address, control and information fields; the ones complement of the resulting remainder is transmitted as the
16-bit FCS.
As a typical implementation at the receiver, the initial content of the register of the device computing the re-
mainder is preset to all 1s. The final remainder, after multiplication by x16 and then division (modulo 2) by the
generator polynomial x16 + x12 + x5 + 1 of the serial incoming protected bits and the FCS, will be
0001110100001111 (x15 through x0, respectively) in the absence of transmission errors.
13.1.4.1.13 Transparency (Zero Stuffing)
A transmitting data link layer entity shall examine the frame content between the opening and closing flag se-
quences, (address, control, information and FCS field) and shall insert a 0 bit after all sequences of five contig-
uous 1 bits (including the last five bits of the FCS) to ensure that an IDLE flag or an Abort sequence is not sim-
ulated within the frame. A receiving data link layer entity shall examine the frame contents between the open-
ing and closing flag sequences and shall discard any 0 bit which directly follows five contiguous 1 bits.
13.1.4.2 How to configure the Transmit HDLC Controller Block to transmit MOS
414
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
This section describes how to configure the LAPD Controller Block to transmit MOS message in a step-by-step
basis.
13.1.4.2.1 Step 1: Find out the next available transmit data link buffer
To transmit MOS message, the user is recommended to read Transmit Data Link Byte Count Register for next
available transmit buffer number.
The table below shows how contents of the Buffer Enable bit of the Transmit Data Link Byte Count Register
(TDLBCR) determines what the next available transmit buffer number is.
TRANSMIT DATA LINK BYTE COUNT REGISTER (TDLBCR) (INDIRECT ADDRESS = 0XN0H, 0X14H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Buffer Select
R
0 - The next available transmit buffer for sending out BOS or MOS mes-
sage is Buffer 0.
1 - The next available transmit buffer for sending out BOS or MOS mes-
sage is Buffer 1.
13.1.4.2.2 Step 2: Write MOS Message into transmit data link buffer
After finding out the next available transmit buffer, the user should write the entire message data to the avail-
able transmit data link buffer via PIO or DMA access. The writing of these buffers is through the LAPD Buffer 0
indirect data registers and the LAPD Buffer1 indirect data registers. LAPD Buffer 0 and 1 indirect data registers
have addresses 0xn6H and 0xn7H respectively. There is no indirect address register for transmit data link buff-
er 0 and 1.
A microcontroller WRITE access to the LAPD Buffer indirect data registers will access the transmit data link
buffer and a microcontroller READ will access the receive data link buffers. The very first WRITE access to the
LAPD Buffer indirect data register will always be direct to location 0 within the transmit data link buffer. The next
WRITE access to the LAPD Buffer indirect data register will be direct to location 1 within the transmit data link
buffer and so on, until all 96 bytes of the transmit buffer is filled.
For example, if the first byte of the MOS message to be sent is (01010110) and the next available transmit data
link buffer of Channel n is 1. The user should write pattern (01010110) into transmit data link buffer 1 of Chan-
nel n. The following microprocessor access to the framer should be done:
WR
n7H
56H
The first byte of MOS message is written into location 0 of the transmit data link buffer. If the next byte of the
MOS message is (10100101), the user should perform another microprocessor WRITE access:
WR
n7H
A5H
The second byte of MOS message is written into location 1 of the transmit data link buffer. The WRITE access
should be repeated until the entire block of MOS message is written into the transmit buffer or the transmit buff-
er is completely filled.
13.1.4.2.3 Step 3: Program the Transmit Data Link Byte Count Register
The user should program byte count of the MOS message into the Transmit Data Link Byte Count Register af-
ter the whole block of data is present in the buffer memory.
415
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The table below shows configurations of the Transmit Data Link Byte Count [6:0] bits the Transmit Data Link
Byte Count Register (TDLBCR).
TRANSMIT DATA LINK BYTE COUNT REGISTER (TDLBCR) (INDIRECT ADDRESS = 0XN0H, 0X14H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
6-0
Transmit Data Link
Byte Count [6:0]
R/W
Value of these bits determines length of the MOS message pattern to be
transmitted by the framer before generating the Transmit End of Transfer
(TxEOT) interrupt.
13.1.4.2.4 Step 4: Configure MOS Message transmission control bits
Configuration of the Data Link Control Register determines whether the LAPD Controller will insert IDLE flag
character, FCS or ABORT sequence to the data link channel. It also determines how the transition between
MOS mode to BOS mode is done.
If the IDLE Insertion bit of the Data Link Control Register is set, repeated flags of value 0x7E are transmitted as
soon as the current operation is finished (defined by the value in Transmit Data Link Byte Count Register). The
IDLE bit must be set to 1 at the last block of transfer to enable FCS and flag insertion for message completion.
The table below shows configurations of the IDLE Insertion bit of the Data Link Control Register (DLCR).
DATA LINK CONTROL REGISTER (DLCR) (INDIRECT ADDRESS = 0XN0H, 0X13H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
2
IDLE Insertion
R/W
0 - No flag sequence is sent on the data link channel.
1 - The framer forces a flag sequence of value 0x7E onto the data link
channel.
NOTE: If the entire message is longer than 96-byte in length or more than one full block of message has to be transmitted,
the IDLE Insertion bit should not be set to one until the last block of message has to be sent.
If the FCS Insertion bit of the Data Link Control Register (DLCR) is set to high, the LAPD Controller will calcu-
late and insert the frame check sequence to the last block of the transmitted message.
The table below shows configurations of the FCS Insertion bit of the Data Link Control Register (DLCR).
DATA LINK CONTROL REGISTER (DLCR) (INDIRECT ADDRESS = 0XN0H, 0X13H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1
FCS Insertion
R/W
0 - No FCS will be inserted into the last block of the transmitted MOS mes-
sage.
1 - The LAPD Controller will calculate and insert the FCS into the last block
of the transmitted MOS message.
If the FCS is not enabled at the end of a message, the controller will return to sending IDLE flags immediately
after the last octet is transmitted. This permits the use of a programmable FCS, which may be used for diag-
nostic tests or other test applications.
To abort a transmitting message, the LAPD Controller sets the ABORT bit in Data Link Control Register to 1.
This bit is cleared after the LAPD transmitter finishes sending the message octet in progress. The transmitter
then transmit an ABORT sequence of one zero followed by seven ones (01111111) before goes to idle if the
IDLE bit is set. The transmitter will keep transmitting IDLE flag characters until it is instructed otherwise.
416
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The table below shows configurations of the ABORT bit of the Data Link Control Register (DLCR).
DATA LINK CONTROL REGISTER (DLCR) (INDIRECT ADDRESS = 0XN0H, 0X13H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3
ABORT
R/W
0 - No ABORT sequence is sent on the data link channel.
1 - The framer forces an ABORT sequence of pattern (111111 10) onto the
data link channel. IDLE flag pattern will be transmitted after the ABORT
sequence is sent.
Switching the data link channel from MOS mode to BOS mode while a message is being transmitted will inter-
rupt the message after the octet in progress is transmitted. If the MOS ABORT bit of the Data Link Control Reg-
ister is set, a MOS ABORT sequence (a zero followed by 7 ones) will be inserted before switching. Switching
the data link from BOS to LAPD will not take place until the current operation completes if Transmit BOS byte
count is not set to zero initially. If the Transmit BOS byte count value is set to zero, the transition from BOS
mode to MOS mode will take place right after finishing the current message octet.
The table below shows configurations of the MOS ABORT bit of the Data Link Control Register (DLCR).
DATA LINK CONTROL REGISTER (DLCR) (INDIRECT ADDRESS = 0XN0H, 0X13H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
6
MOS ABORT
R/W
0 - The framer forces an MOS ABORT sequence of one zero and seven
ones [0111 1111] onto the data link channel during the transition from
MOS mode to BOS mode.
1 - No MOS ABORT sequence is sent on the data link channel during the
transition from MOS mode to BOS mode.
13.1.4.2.5 Step 5: Enable transmit MOS message interrupts
The LAPD Controller can generate a couple of interrupts indicating the status of MOS message transmission
to the microprocessor. These are the Transmit Start of Transfer (TxSOT) interrupt and the Transmit End of
Transfer (TxEOT) interrupt.
To enable these interrupts, the Transmit Start of Transfer Enable bit and the Transmit End of Transfer Enable bit
of the Data Link Interrupt Enable Register (DLIER) have to be set. In addition, the HDLC Controller Interrupt
Enable bit of the Block Interrupt Enable Register (BIER) needs to be one.
The table below shows configurations of the Transmit Start of Transfer Enable bit and the Transmit End of
Transfer Enable bit of the Data Link Interrupt Enable Register.
DATA LINK INTERRUPT ENABLE REGISTER (DLIER) (INDIRECT ADDRESS = 0XNAH, 0X07H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
6
Transmit Start of
Transfer Enable
R/W
0 - The Transmit Start of Transfer interrupt is disabled.
1 - The Transmit Start of Transfer interrupt is enabled.
4
Transmit End of
Transfer Enable
R/W
0 - The Transmit End of Transfer interrupt is disabled.
1 - The Transmit End of Transfer interrupt is enabled.
417
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The table below shows configurations of the HDLC Controller Interrupt Enable bit of the Block Interrupt Enable
Register.
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X00H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3
HDLC Controller
Interrupt Enable
R/W
0 - Every interrupt generated by the HDLC Controller is disabled.
1 - Every interrupt generated by the HDLC Controller is enabled.
When these interrupt enable bits are set and the MOS message is transmitted to the data link channel, the
LAPD Controller changes the Transmit Start of Transfer and Transmit End of Transfer status bits of the Data
Link Status Register (DLSR). These two status indicators are valid until the Data Link Status Register is read.
Reading these register clears the associated interrupt if Reset Upon Read is selected in Interrupt Control Reg-
ister (ICR). Otherwise, a write-to-clear operation by the microprocessor is required to reset these status indica-
tors.
The table below shows the Transmit Start of Transfer and Transmit End of Transfer status bits of the Data Link
Status Register.
DATA LINK STATUS REGISTER (DLSR) (INDIRECT ADDRESS = 0XNAH, 0X06H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
6
Transmit Start of
Transfer
RUR /
WC
0 - There is no data link message to be sent to the data link channel.
1 - The HDLC Controller will send a data link message to the data link
channel.
4
Transmit End of
Transfer
RUR /
WC
0 - No data link message was sent to the data link channel.
1 - The HDLC Controller finished sending a data link message to the data
link channel.
13.1.4.2.6 Step 6: MOS message transmission
A one is then written into the LAPD enable bit of Data Link Control Register, which sets the transmitter to Mes-
sage-Oriented mode and kicks off the transmission process. The LAPD controller latches these control bits of
the Data Link Control Register and send a Transmit Start of Transfer interrupt (TxSOT) to the microprocessor to
indicate that an MOS message will be send.
The LAPD transmitter will then transmit the open flag character (01111110) in the data link bit position first fol-
lowed by the entire message. If the message is longer than 96 bytes or more than one full block of data are to
be transmitted, the alternating buffer usage approach will provide more adequate time to allow the writing of
the message in the Ping-Pong buffers without overwriting good data in the transmitting buffer or repeating data
because it was written too late. User must fill in data fast enough in Ping-Pong buffer concatenation scenario to
avoid automatic flag insertion between two blocks of data that will cause far-end FCS errors.
After the entire MOS message is sent, the LAPD Controller generates the Transmit End of Transfer (TxEOT) in-
terrupt to the microprocessor indicating that the MOS message transmission is over.
418
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The table below shows configurations of the LAPD Enable bit of the Data Link Control Register (DLCR).
DATA LINK CONTROL REGISTER (DLCR) (INDIRECT ADDRESS = 0XN0H, 0X13H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
0
LAPD Enable
R/W
0 - The Transmit HDLC Controller will send out Bit-Oriented Signaling
(BOS) message.
1 - The Transmit HDLC Controller will send out LAPD protocol or so-called
Message-Oriented Signaling (MOS) message.
13.1.5 Transmit SLCâ96 Data link Controller
The SLC®96 T1 format is invented by AT&T and is used between the Digital Switch and a SLC®96 formatted
remote terminal. The purpose of the SLC®96 product is to provide standard telephone service or Plain Old
Telephone Service (POTS) in areas of high subscriber density but back-haul the traffic over T1 facilities.
To support the SLC®96 formatted remote terminal equipment, which is likely in an underground location, the
T1s needed methods to:
• Indicate equipment failures of the equipment to maintenance personal
• Indicate failures of the POTS lines
• Test the POTS lines
• Provide redundancy on the T1s
The SLC®96 framing format is a D4 Super-frame (SF) format with specialized data link information bits. These
data link information bits take the position of the Super-frame Alignment (Fs) bit positions. These bits consist
of:
• Concentrator bits (C, bit position 1 to 11)
• First Spoiler bits (FS, bit position 12 to 14)
• Maintenance bits (M, bit position 15 to 17)
• Alarm bits (A, bit position 18 to 19)
• Protection Line Switch bits (S, bit position 20 to 23)
• Second Spoiler bit (SS, bit position 24)
• Resynchronization pattern (000111000111)
In SLCâ96 mode, six six-bit data will generate one 9-ms frame of the SLCâ96 message format. The format of
the data link message is given in BELLCORE TR-TSY-000008. To select this mode, the Framing Select bits of
419
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
the Framing Select Register (FSR) must be set to binary number 100. The table below shows configuration of
the Framing Select bits of the Framing Select Register (FSR).
FRAMING SELECT REGISTER (FSR) (INDIRECT ADDRESS = 0XN0H, 0X07H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
2-0
T1 Framing Select
R/W
T1 Framing Select:
These READ/WRITE bit-fields allow the user to select one of the five T1
framing formats supported by the framer. These framing formats include
ESF, SLC®96, SF, N and T1DM mode.
Framing
Format
Bit 2
Bit 1
Bit 0
ESF
0
1
1
1
1
X
0
0
1
1
X
0
1
0
1
SLC®96
SF
N
T1DM
NOTE: Changing of framing format will automatically force the framer to
RESYNC.
When SLC®96 mode is enabled, the Fs bit is replaced by the data link message read from memory at the be-
ginning of each D4 super-frame. The XRT84L38 allocates two 6-byte buffers to provide the SLC®96 Data Link
Controller an alternating access mechanism for information transmission. The bit ordering and usage is shown
in the following table; and the LSB is sent first. Note that these registers are memory-based storage and they
need to be initialized.
TRANSMIT SLC®96 MESSAGE REGISTERS
BITBYTE
5
0
4
1
3
1
2
1
1
0
0
0
1
2
3
4
5
6
C1
C7
1
1
1
1
0
0
C6
0
C5
C11
M3
S4
C4
C10
M2
S3
C3
C9
M1
S2
C2
C8
0
A2
0
A1
1
S1
Each register is read out of memory once every six SF super-frames. The memory holding these registers
owns a shared memory structure that is used by multiple devices. These include DS1 transmit module, DS1 re-
ceive module, Transmit LAPD Controller, Transmit SLCâ96 Data Link controller, Bit-Oriented Signaling Proces-
sor, Receive LAPD Controller, Receive SLCâ96 Data Link Controller, Receive Bit-Oriented Signaling Proces-
sor and microprocessor interface module.
13.1.5.1 How to configure the SLC®96 Data Link Controller to transmit SLC®96 Data Link Messages
This section describes how to configure the SLC®96 Data Link Controller to transmit SLC®96 Data Link mes-
sage in a step-by-step basis.
13.1.5.1.1 Step 1: Find out the next available transmit data link buffer
420
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
To transmit SLC®96 Data Link message, the user is recommended to read Transmit Data Link Byte Count
Register for next available transmit buffer number.
The table below shows how contents of the Buffer Enable bit of the Transmit Data Link Byte Count Register
(TDLBCR) determines what the next available transmit buffer number is.
TRANSMIT DATA LINK BYTE COUNT REGISTER (TDLBCR) (INDIRECT ADDRESS = 0XN0H, 0X14H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Buffer Select
R
0 - The next available transmit buffer for sending out BOS or MOS mes-
sage is Buffer 0.
1 - The next available transmit buffer for sending out BOS or MOS mes-
sage is Buffer 1.
13.1.5.1.2 Step 2: Write SLC®96 Data Link Message into transmit data link buffer
After finding out the next available transmit buffer, the user should write the entire message data to the avail-
able transmit data link buffer via PIO or DMA access. The writing of these buffers is through the LAPD Buffer 0
indirect data registers and the LAPD Buffer1 indirect data registers. LAPD Buffer 0 and 1 indirect data registers
have addresses 0xn6H and 0xn7H respectively. There is no indirect address register for transmit data link buff-
er 0 and 1.
A microcontroller WRITE access to the LAPD Buffer indirect data registers will access the transmit data link
buffer and a microcontroller READ will access the receive data link buffers. The very first WRITE access to the
LAPD Buffer indirect data register will always be direct to location 0 within the transmit data link buffer. The next
WRITE access to the LAPD Buffer indirect data register will be direct to location 1 within the transmit data link
buffer and so on, until all 96 bytes of the transmit buffer is filled.
For example, if the first byte of the SLC®96 Data Link message to be sent is (101011) and the next available
transmit data link buffer of Channel n is 1. The user should write pattern (00101011) into transmit data link buff-
er 1 of Channel n. The following microprocessor access to the framer should be done:
WR
n7H
2BH
The first byte of the SLC®96 Data Link message is written into location 0 of the transmit data link buffer. If the
next byte of the data link message is (101001), the user should perform another microprocessor WRITE ac-
cess of pattern (00101001):
WR
n7H
29H
The second byte of data link message is written into location 1 of the transmit data link buffer. The WRITE ac-
cess should be repeated until all six bytes of SLC®96 Data Link message is written into the transmit buffer or
the transmit buffer is completely filled.
13.1.5.1.3 Step 3: Enable transmit data link message interrupt
The SLC®96 Data Link Controller can generate the Transmit Start of Transfer (TxSOT) interrupt indicating the
status of data link message transmission to the microprocessor. To enable this interrupt, the Transmit Start of
Transfer Enable bit of the Data Link Interrupt Enable Register (DLIER) have to be set. In addition, the HDLC
Controller Interrupt Enable bit of the Block Interrupt Enable Register (BIER) needs to be one.
The table below shows configurations of the Transmit Start of Transfer Enable bit of the Data Link Interrupt En-
able Register.
DATA LINK INTERRUPT ENABLE REGISTER (DLIER) (INDIRECT ADDRESS = 0XNAH, 0X07H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
6
Transmit Start of
Transfer Enable
R/W
0 - The Transmit Start of Transfer interrupt is disabled.
1 - The Transmit Start of Transfer interrupt is enabled.
421
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The table below shows configurations of the HDLC Controller Interrupt Enable bit of the Block Interrupt Enable
Register.
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X00H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3
HDLC Controller
Interrupt Enable
R/W
0 - Every interrupt generated by the HDLC Controller is disabled.
1 - Every interrupt generated by the HDLC Controller is enabled.
When this interrupt enable bit is set and the SLC®96 Data Link message is transmitted to the data link chan-
nel, the SLC®96 Data Link Controller changes the Transmit Start of Transfer status bits of the Data Link Status
Register (DLSR). This status indicator is valid until the Data Link Status Register is read. Reading this register
clears the associated interrupt if Reset Upon Read is selected in Interrupt Control Register (ICR). Otherwise, a
write-to-clear operation by the microprocessor is required to reset these status indicators.
The table below shows the Transmit Start of Transfer and Transmit End of Transfer status bits of the Data Link
Status Register.
DATA LINK STATUS REGISTER (DLSR) (INDIRECT ADDRESS = 0XNAH, 0X06H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
6
Transmit Start of
Transfer
RUR /
WC
0 - There is no data link message to be sent to the data link channel.
1 - The SLC®96 Data Link Controller will send SLC®96 data link message
to the data link channel.
13.1.5.1.4 Step 4: Program the Data Link Control Register to activate SLC®96 Data Link Transmission
The SLC®96 Enable bit and the LAPD Enable bit of the Data Link Control Register (DLCR) determines which
one of the three functions is performed by the Transmit HDLC Controller block. The table below shows configu-
ration of the SLC®96 Enable bit of the Data Link Control Register (DLCR).
DATA LINK CONTROL REGISTER (DLCR) (INDIRECT ADDRESS = 0XN0H, 0X13H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
SLC®96 Enable
R/W
0 - In SLC®96 framing mode, the data link transmission is disabled. The
framer transmits the regular SF framing bits.
In ESF framing mode, the framer transmits regular ESF framing bits and
Facility Data Link (FDL) bits.
1 - In SLC®96 framing mode, the data link transmission is enabled.
In ESF framing mode, the framer transmits SLC®96-like message in the
Facility Data Link bits.
422
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The table below shows configuration of the LAPD Enable bit of the Data Link Control Register (DLCR).
DATA LINK CONTROL REGISTER (DLCR) (INDIRECT ADDRESS = 0XN0H, 0X13H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
0
LAPD Enable
R/W
0 - The Transmit HDLC Controller will send out Bit-Oriented Signaling
(BOS) message.
1 - The Transmit HDLC Controller will send out LAPD protocol or so-called
Message-Oriented Signaling (MOS) message.
To enable SLC®96 data link transmission, the user has to set both of the SLC®96 Enable bit and the LAPD En-
able bit of the Data Link Control Register to 1.
Without inputting new message, the data link controller will loop on the same message over and over again. To
force the data link to output all ones is done by setting the ABORT bit in Data Link Control Register to 1. This
operation takes place after the current message finishes transmitting. The table below shows configurations of
the ABORT bit of the Data Link Control Register (DLCR).
DATA LINK CONTROL REGISTER (DLCR) (INDIRECT ADDRESS = 0XN0H, 0X13H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3
ABORT
R/W
0 - No ABORT sequence is sent on the data link channel.
1 - The framer forces an ABORT sequence of pattern (111111 10) onto the
data link channel.
Setting the SLCâ96 bit low will switch the data link back to transfer normal framing bits after the current mes-
sage transmit completes.
13.2 DS1 RECEIVE HDLC CONTROLLER BLOCK
13.2.1 Description of the DS1 Receive HDLC Controller Block
XRT84L38 allows user to extract data link information from incoming DS1 frames. The data link information in
DS1raming format mode can be extracted to the following:
• DS1 Receive Overhead Output Interface Block
• DS1 Receive HDLC Controller
• DS1 Receive Serial Output Interface
The Receive Data Link Source Select [1:0] bits, within the Receive Data Link Select Register (RSDLSR) deter-
mine destinations of the data link bits (Facility Data Link (FDL) bits in ESF framing format mode, Signaling
Framing (Fs) bits in SLC®96 framing format mode and Remote Signaling (R) bits in T1DM framing format
mode) extracted from the incoming DS1 frames.
423
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The table below shows configuration of the Receive Data Link Source Select [1:0] bits of the Receive Data Link
Select Register (RSDLSR).
RECEIVE DATA LINK SELECT REGISTER (RSDLSR) (INDIRECT ADDRESS = 0XN0H, 0X0CH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1-0
Receive Data Link
Source Select [1:0]
R/W
00 - The data link bits extracted from the incoming DS1 frame are sent to
the Receive HDLC Controller.
01 - The data link bits extracted from the incoming DS1 frame are sent to
the Receive Serial Data Output Interface via the RxSer_n pins.
10 - The data link bits extracted from the incoming DS1 frame are sent to
the Receive Overhead Output Interface via the RxOH_n pins.
11 - The data link bits are forced into 1.
If the Receive Data Link Source Select bits of the Receive Data Link Select Register are set to 00, the Receive
HDLC Controller block becomes output destination of the data link bits in incoming DS1 frames.
Each of the eight framers within the XRT84L38 device contains a DS1 Receive High-level Data Link Controller
(HDLC) block. The function of this block is to establish a serial data link channel in DS1 mode through the fol-
lowing:
• Facility Data Link (FDL) bits in ESF framing format mode
• Signaling Framing (Fs) bits in SLC®96 framing format mode
• Remote Signaling (R) bits in T1DM framing format mode
• D or E signaling timeslot channel
Data link bits are automatically inserted into the Facility Data Link (FDL) bits in ESF framing format mode, Sig-
naling Framing (Fs) bits in SLC®96 framing format mode and Remote Signaling (R) bits in T1DM framing for-
mat mode or forced to 1 by the framer. Additionally, XRT84L38 allows the user to define any one of ones of the
twenty-four DS0 timeslots to be D or E channel. We will discuss how to configure XRT84L38 to Receive data
link information through D or E channels in later section.
The DS1 Receive HDLC Controller block contains three major functional modules associated with DS1 framing
formats. They are the:
• SLC®96 Data Link Controller
• LAPD Controller
• Bit-Oriented Signaling Processor.
There are two 96-byte receive message buffer in shared memory for each of the eight framers to receive data
link information. When one message buffer is filled up, the DS1 Receive HDLC Controller automatically switch-
es to the next message buffer to store data link messages. These two message buffers ping-pong among each
other for data link message storage.
The SLC®96 Enable bit and the Message Type bit of the Data Link Status Register (DLSR) determines which
one of the three messages is received and processed by the Receive HDLC Controller block.
424
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The table below shows configuration of the SLC®96 Enable bit of the Data Link Control Register (DLCR).
DATA LINK CONTROL REGISTER (DLCR) (INDIRECT ADDRESS = 0XN0H, 0X13H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
SLC®96 Enable
R/W
0 - In SLC®96 framing mode, the data link transmission is disabled. The
framer receives the regular SF framing bits.
In ESF framing mode, the framer receives regular ESF framing bits and
Facility Data Link (FDL) bits.
1 - In SLC®96 framing mode, the data link transmission is enabled.
In ESF framing mode, the framer receives SLC®96-like message in the
Facility Data Link bits.
The table below shows configuration of the Message Type bit of the Data Link Status Register (DLSR).
DATA LINK STATUS REGISTER (DLSR) (INDIRECT ADDRESS = 0XNAH, 0X06H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Message Type
RUR /
WC
0 - The Receive HDLC Controller receives and processes Bit-Oriented Sig-
naling (BOS) message.
1 - The Receive HDLC Controller receives and processes LAPD protocol
or Message-Oriented Signaling (MOS) message.
13.2.2 How to configure XRT84L38 to Receive data link information through D or E Channels
The XRT84L38 can configure any one or ones of the twenty-four DS0 channels to be D or E channels. D chan-
nel is used primarily for data link applications. E channel is used primarily for signaling for circuit switching with
multiple access configurations.
The Receive Conditioning Select [3:0] bits of the Receive Channel Control Register (RCCR) of each channel
determine whether that particular channel is configured as D or E channel. These bits also determine what
type of data or signaling conditioning is applied to each channel.
RECEIVE CHANNEL CONTROL REGISTER (RCCR) (INDIRECT ADDRESS = 0XN2H, 0X60H - 0X7FH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3-0
Receive Condition-
ing Select
R/W
1111 - This channel is configured as D or E timeslot.
If the Receive Conditioning Select [3:0] bits of the Receive Channel Control Register of a particular timeslot are
set to 1111, that timeslot is configured as a D or E timeslot.
Any D or E timeslot can be configured to direct data link information to the following destinations:
• DS1 Receive Overhead Output Interface Block
• DS1 Receive HDLC Controller Block
• DS1 Receive Serial Output Interface Block
• DS1 Receive Fractional Output Interface Block
The Receive D or E Channel Source Select [1:0] bits of the Receive Data Link Select Register (RSDLSR) de-
termines which one of the above-mentioned modules to be output destinations of D or E timeslot. The table be-
425
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
low shows configuration of the Receive D or E Channel Source Select [1:0] bits of the Receive Data Link Select
Register (RSDLSR).
RECEIVE DATA LINK SELECT REGISTER (RSDLSR) (INDIRECT ADDRESS = 0XN0H, 0X0CH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3-2
Receive D or E
Channel Source
Select [1:0]
R/W
00 - The data link bits extracted form the D or E channel of incoming DS1
frame are inserted into the Receive Serial Data Output Interface via the
RxSer_n pins.
01 - The data link bits extracted form the D or E channel of incoming DS1
frame are inserted into the Receive HDLC Controller.
10 - The data link bits extracted form the D or E channel of incoming DS1
frame are inserted into the Receive Fractional T1 Output Interface via the
RxFrT1_n pins.
11 - The data link bits extracted form the D or E channel of incoming DS1
frame are inserted into the Receive Serial Data Output Interface via the
RxSer_n pins.
For the Receive HDLC Controller to be output destination of D or E channel, the Receive D or E Channel
Source Select [1:0] bits of the Receive Data Link Select Register has to be set to 01.
13.2.3 Receive BOS (Bit Oriented Signaling) Processor
The Receive BOS Processor handles receiving and processing of BOS messages through the DS1 data link
channel. It generates Receive End of Transfer (RxEOT) interrupt each time a BOS message is received and
stores the BOS message into the receive message buffer. In the later section, we will discuss how to configure
the BOS Processor Block to receive BOS message.
13.2.3.1 How to configure the BOS Processor Block to receive BOS
This section describes how to configure the BOS Processor Block to receive BOS message and how to read
out the BOS message. The operation of the receive BOS Processor is interrupt-driven. When a BOS message
is received, message octet is written to the next receive data link message buffer opposite to that last used.
The receive BOS Processor generates interrupts to the microprocessor notifying it that a BOS message is re-
ceived. The BOS message can then be extracted from the appropriate receive data link buffer.
13.2.3.1.1 Step 1: Enable receive BOS message interrupts
The BOS Processor can generate a couple of interrupts indicating the status of BOS message received to the
microprocessor. These are the Receive Start of Transfer (RxSOT) interrupt and the Receive End of Transfer
(RxEOT) interrupt.
To enable these interrupts, the Receive Start of Transfer Enable bit and the Receive End of Transfer Enable bit
of the Data Link Interrupt Enable Register (DLIER) have to be set. In addition, the HDLC Controller Interrupt
Enable bit of the Block Interrupt Enable Register (BIER) needs to be one.
The table below shows configurations of the Receive Start of Transfer Enable bit and the Receive End of Trans-
fer Enable bit of the Data Link Interrupt Enable Register.
DATA LINK INTERRUPT ENABLE REGISTER (DLIER) (INDIRECT ADDRESS = 0XNAH, 0X07H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
5
Receive Start of
Transfer Enable
R/W
0 - The Receive Start of Transfer interrupt is disabled.
1 - The Receive Start of Transfer interrupt is enabled.
3
Receive End of
Transfer Enable
R/W
0 - The Receive End of Transfer interrupt is disabled.
1 - The Receive End of Transfer interrupt is enabled.
426
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The table below shows configurations of the HDLC Controller Interrupt Enable bit of the Block Interrupt Enable
Register.
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X00H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3
HDLC Controller
Interrupt Enable
R/W
0 - Every interrupt generated by the HDLC Controller is disabled.
1 - Every interrupt generated by the HDLC Controller is enabled.
When these interrupt enable bits are set and the BOS message is received in the data link channel, the BOS
Processor changes the Receive Start of Transfer and Receive End of Transfer status bits of the Data Link Sta-
tus Register (DLSR). These two status indicators are valid until the Data Link Status Register is read. Reading
these register clears the associated interrupt if Reset Upon Read is selected in Interrupt Control Register
(ICR). Otherwise, a write-to-clear operation by the microprocessor is required to reset these status indicators.
The table below shows the Receive Start of Transfer and Receive End of Transfer status bits of the Data Link
Status Register.
DATA LINK STATUS REGISTER (DLSR) (INDIRECT ADDRESS = 0XNAH, 0X06H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
5
Receive Start of
Transfer
RUR /
WC
0 - There is no data link message in the data link channel.
1 - The HDLC Controller began to receive a data link message in the data
link channel.
3
Receive End of
Transfer
RUR /
WC
0 - No data link message was present in the data link channel.
1 - The HDLC Controller finished receiving a data link message in the data
link channel.
The BOS Processor can also generate interrupts when either the BOS ABORT sequence (nine consecutive
ones) or the IDLE flag character (hexadecimal value of 0x7EH) is received in the data link channel to the micro-
processor. These are the Receive ABORT Sequence (RxABORT) interrupt and the Receive IDLE Flag Se-
quence (RxIDLE) interrupt.
To enable these interrupts, the Receive ABORT Sequence Enable bit and the Receive IDLE Flag Sequence
Enable bit of the Data Link Interrupt Enable Register (DLIER) have to be set. In addition, the HDLC Controller
Interrupt Enable bit of the Block Interrupt Enable Register (BIER) needs to be one.
The table below shows configurations of the Receive ABORT Sequence Enable bit and the Receive IDLE Flag
Sequence Enable bit of the Data Link Interrupt Enable Register.
DATA LINK INTERRUPT ENABLE REGISTER (DLIER) (INDIRECT ADDRESS = 0XNAH, 0X07H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1
Receive ABORT
Sequence Enable
R/W
0 - The Receive ABORT Sequence interrupt is disabled.
1 - The Receive ABORT Sequence interrupt is enabled.
0
Receive IDLE Flag
Sequence Enable
R/W
0 - The Receive IDLE Flag Sequence interrupt is disabled.
1 - The Receive IDLE Flag Sequence interrupt is enabled.
When these interrupt enable bits are set and the BOS ABORT sequence or IDLE Flag Sequence is received in
the data link channel, the BOS Processor changes the Receive ABORT Sequence and Receive IDLE Flag Se-
quence status bits of the Data Link Status Register (DLSR). These two status indicators are valid until the Data
427
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
Link Status Register is read. Reading these register clears the associated interrupt if Reset Upon Read is se-
lected in Interrupt Control Register (ICR). Otherwise, a write-to-clear operation by the microprocessor is re-
quired to reset these status indicators.
The table below shows the Receive ABORT Sequence and Receive IDLE Flag Sequence status bits of the Da-
ta Link Status Register.
DATA LINK STATUS REGISTER (DLSR) (INDIRECT ADDRESS = 0XNAH, 0X06H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1
Receive ABORT
Sequence
RUR /
WC
0 - There is no BOS ABORT sequence received in the data link channel.
1 - The HDLC Controller receives BOS ABORT sequence in the data link
channel.
0
Receive IDLE Flag
Sequence
RUR /
WC
0 - The message received in the data link channel is BOS message.
1 - The message received in the data link channel is MOS message.
13.2.3.1.2 Step 2: Find out the next available receive data link buffer
To transmit a bit-oriented signal, a repeating message is sent of the form (0d5d4d3d2d1d0011111111), where
the "d5d4d3d2d1d0" represents a six-bit message. When receiving a BOS message, the received message
octet is written to the next available receive data link buffer in the form of (0d5d4d3d2d1d00). The user is rec-
ommended to read Receive Data Link Byte Count Register for next available receive data link buffer number.
The table below shows how contents of the Receive Buffer Pointer bit of the Receive Data Link Byte Count
Register (RDLBCR) determines what the next available receive data link buffer number is.
RECEIVE DATA LINK BYTE COUNT REGISTER (RDLBCR) (INDIRECT ADDRESS = 0XN0H, 0X15H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Receive Buffer
Pointer
R
0 - The next available receive data link buffer for reading out BOS or MOS
message is Buffer 0.
1 - The next available receive data link buffer for reading out BOS or MOS
message is Buffer 1.
13.2.3.1.3 Step 3: Program BOS Message receiving repetitions
The user should program the value of message receiving repetitions into the Receive Data Link Byte Count
Register. The framer will receive the BOS message the same number of times as was stored in the Receive
Data Link Byte Count Register (RDLBCR) before generating the Receive End of Transfer (RxEOT) interrupts.
If the value stored inside the Receive Data Link Byte Count Register (RDLBCR) is set to 0, the message will be
received indefinitely and no Receive End of Transfer interrupt will be generated.
The table below shows configurations of the Receive Data Link Byte Count [6:0] bits the Receive Data Link
Byte Count Register (RDLBCR).
428
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
RECEIVE DATA LINK BYTE COUNT REGISTER (RDLBCR) (INDIRECT ADDRESS = 0XN0H, 0X15H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
6-0
Receive Data Link
Byte Count [6:0]
R/W
Value of these bits determines how many times a BOS message pattern
will be received by the framer before generating the Receive End of Trans-
fer (TxEOT) interrupt.
NOTE: If these bits are set to 0, the BOS message will be received indefi-
nitely and no Receive End of Transfer interrupts will be generated.
13.2.3.1.4 Step 4: Read BOS Message from receive data link buffer
Upon detection of the Receive End of Transfer (RxEOT) interrupt, the user should read the Message Type bit of
the Data Link Status Register (DLSR) to find out what is the type of message received.
The table below shows how contents of the Message Type bit of the Data Link Status Register (DLSR) deter-
mines what the type of message received in the data link channel is.
DATA LINK STATUS REGISTER (DLSR) (INDIRECT ADDRESS = 0XNAH, 0X06H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Message Type
RUR /
WC
0 - There is no BOS ABORT sequence received in the data link channel.
1 - The HDLC Controller receives BOS ABORT sequence in the data link
channel.
After determined that the received message is a BOS one, the use should read eight bits message from the
first location of the next available receive data link buffer. The reading of these buffers is through the LAPD
Buffer 0 indirect data registers and the LAPD Buffer1 indirect data registers. LAPD Buffer 0 and 1 indirect data
registers have addresses 0xn6H and 0xn7H respectively. There is no indirect address register for receive data
link buffer 0 and 1.
A microcontroller WRITE access to the LAPD Buffer indirect data registers will access the receive data link
buffer and a microcontroller READ will access the receive data link buffers. The very first READ access to the
LAPD Buffer indirect data register will always be direct to location 0 within the receive data link buffer.
For example, if the BOS Message to received is (101011) and the next available receive data link buffer of
Channel n is 1. The user should be able to read pattern (01010110) from receive data link buffer 1 of Channel
n. The following microprocessor access to the framer should be done:
RD
n7H
The result of the READ access should be 0x56H.
13.2.4 Receive LAPD Controller
The receive LAPD controller implements the Message-Oriented protocol based on ITU Recommendation
Q.921 Link Access Procedures on the D-channel (LAPD) type of protocol. It provides the following functions:
• Zero deletion
• Pattern recognition for IDLE flag detection
• Pattern recognition for ABORT sequence detection
• Frame check sequence verification
• T1 receiver interface
• Receive data link message buffer access
Two 96-byte buffers in shared memory are allocated for receive LAPD Controller to reduce the frequency of mi-
croprocessor interrupts and alleviate the response time requirement for microprocessor to handle each inter-
429
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
rupt. There are no restrictions on the length of the message received. However, the 96-byte buffer is deep
enough to hold one entire LAPD path or test signal identification message.
The following section discuss how to configure the receive LAPD Controller to receive and extract MOS mes-
sages.
13.2.4.1 How to configure the Receive HDLC Controller Block to receive MOS message
This section describes how to configure the LAPD Controller Block to receive and extract MOS message in a
step-by-step basis.
The operation of the receive LAPD Controller is interrupt-driven. When an MOS message is receiving, mes-
sage octets are written to the next receive data link message buffer opposite to that last used. Each time the re-
ceiving data link message buffer is filled, a RxEOT interrupt is issued if it is enabled. This process continues
until an ABORT sequence is received or an IDLE flag is received.
An interrupt is issued when one of the following conditions occurs and the corresponding interrupt enable bit is
set.
• The RxSOT is set when the beginning of a data link message is received (the first non-flag message).
• The RxEOT is set when the end of a data link block is received.
• The RxIDLE is set if an IDLE flag sequence (b01111110) is received on the data link after either an ABORT
sequence is received or a complete message is received.
• The RxABORT is set when an ABORT sequence is received.
• The FCS_ERR is issued when an erroneous frame check sequence is detected at the end of a message or
an idle flag is received that is not octet aligned.
13.2.4.1.1 Step 1: Enable receive MOS message interrupts
The receive LAPD Controller can generate a couple of interrupts indicating the status of MOS message re-
ceived to the microprocessor. These are the Receive Start of Transfer (RxSOT) interrupt and the Receive End
of Transfer (RxEOT) interrupt.
To enable these interrupts, the Receive Start of Transfer Enable bit and the Receive End of Transfer Enable bit
of the Data Link Interrupt Enable Register (DLIER) have to be set. In addition, the HDLC Controller Interrupt
Enable bit of the Block Interrupt Enable Register (BIER) needs to be one.
The table below shows configurations of the Receive Start of Transfer Enable bit and the Receive End of Trans-
fer Enable bit of the Data Link Interrupt Enable Register.
DATA LINK INTERRUPT ENABLE REGISTER (DLIER) (INDIRECT ADDRESS = 0XNAH, 0X07H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
5
Receive Start of
Transfer Enable
R/W
0 - The Receive Start of Transfer interrupt is disabled.
1 - The Receive Start of Transfer interrupt is enabled.
3
Receive End of
Transfer Enable
R/W
0 - The Receive End of Transfer interrupt is disabled.
1 - The Receive End of Transfer interrupt is enabled.
The table below shows configurations of the HDLC Controller Interrupt Enable bit of the Block Interrupt Enable
Register.
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X00H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3
HDLC Controller
Interrupt Enable
R/W
0 - Every interrupt generated by the HDLC Controller is disabled.
1 - Every interrupt generated by the HDLC Controller is enabled.
430
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
When these interrupt enable bits are set and the MOS message is received in the data link channel, the LAPD
Controller changes the Receive Start of Transfer and Receive End of Transfer status bits of the Data Link Sta-
tus Register (DLSR). These two status indicators are valid until the Data Link Status Register is read. Reading
these register clears the associated interrupt if Reset Upon Read is selected in Interrupt Control Register
(ICR). Otherwise, a write-to-clear operation by the microprocessor is required to reset these status indicators.
The table below shows the Receive Start of Transfer and Receive End of Transfer status bits of the Data Link
Status Register.
DATA LINK STATUS REGISTER (DLSR) (INDIRECT ADDRESS = 0XNAH, 0X06H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
5
Receive Start of
Transfer
RUR /
WC
0 - There is no data link message in the data link channel.
1 - The HDLC Controller began to receive a data link message in the data
link channel.
3
Receive End of
Transfer
RUR /
WC
0 - No data link message was present in the data link channel.
1 - The HDLC Controller finished receiving a data link message in the data
link channel.
The LAPD Controller can also generate interrupts when either the MOS ABORT sequence (seven consecutive
ones) or the IDLE flag character (hexadecimal value of 0x7EH) is received in the data link channel to the micro-
processor. These are the Receive ABORT Sequence (RxABORT) interrupt and the Receive IDLE Flag Se-
quence (RxIDLE) interrupt.
To enable these interrupts, the Receive ABORT Sequence Enable bit and the Receive IDLE Flag Sequence
Enable bit of the Data Link Interrupt Enable Register (DLIER) have to be set. In addition, the HDLC Controller
Interrupt Enable bit of the Block Interrupt Enable Register (BIER) needs to be one.
The table below shows configurations of the Receive ABORT Sequence Enable bit and the Receive IDLE Flag
Sequence Enable bit of the Data Link Interrupt Enable Register.
DATA LINK INTERRUPT ENABLE REGISTER (DLIER) (INDIRECT ADDRESS = 0XNAH, 0X07H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1
Receive ABORT
Sequence Enable
R/W
0 - The Receive ABORT Sequence interrupt is disabled.
1 - The Receive ABORT Sequence interrupt is enabled.
0
Receive IDLE Flag
Sequence Enable
R/W
0 - The Receive IDLE Flag Sequence interrupt is disabled.
1 - The Receive IDLE Flag Sequence interrupt is enabled.
When these interrupt enable bits are set and the MOS ABORT sequence or IDLE Flag Sequence is received in
the data link channel, the LAPD Controller changes the Receive ABORT Sequence and Receive IDLE Flag Se-
quence status bits of the Data Link Status Register (DLSR). These two status indicators are valid until the Data
Link Status Register is read. Reading these register clears the associated interrupt if Reset Upon Read is se-
lected in Interrupt Control Register (ICR). Otherwise, a write-to-clear operation by the microprocessor is re-
quired to reset these status indicators.
431
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The table below shows the Receive ABORT Sequence and Receive IDLE Flag Sequence status bits of the Da-
ta Link Status Register.
DATA LINK STATUS REGISTER (DLSR) (INDIRECT ADDRESS = 0XNAH, 0X06H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1
Receive ABORT
Sequence
RUR /
WC
0 - There is no BOS ABORT sequence received in the data link channel.
1 - The HDLC Controller receives MOS ABORT sequence in the data link
channel.
0
Receive IDLE Flag
Sequence
RUR /
WC
0 - The message received in the data link channel is BOS message.
1 - The message received in the data link channel is MOS message.
Finally, the LAPD Controller generates Frame Check Sequence Error (FCS_ERR) interrupt when an erroneous
frame check sequence is detected at the end of a message or an IDLE flag is received that is not octet aligned.
To enable this interrupt, the Frame Check Sequence Error Detection Enable bit of the Data Link Interrupt En-
able Register (DLIER) have to be set. In addition, the HDLC Controller Interrupt Enable bit of the Block Inter-
rupt Enable Register (BIER) needs to be one.
The table below shows configurations of the Frame Check Sequence Error Detection Enable bit of the Data
Link Interrupt Enable Register.
DATA LINK INTERRUPT ENABLE REGISTER (DLIER) (INDIRECT ADDRESS = 0XNAH, 0X07H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
2
Frame Check
Sequence Error
Detection Enable
R/W
0 - The Frame Check Sequence Error Detection interrupt is disabled.
1 - The Frame Check Sequence Error Detection interrupt is enabled.
When the Frame Check Sequence Error Detection interrupt enable bits is set and an erroneous frame check
sequence is detected at the end of a message, the LAPD Controller changes the Frame Check Sequence Er-
ror Detection status bits of the Data Link Status Register (DLSR). This status indicator is valid until the Data
Link Status Register is read. Reading this register clears the associated interrupt if Reset Upon Read is select-
ed in Interrupt Control Register (ICR). Otherwise, a write-to-clear operation by the microprocessor is required
to reset this status indicator.
The table below shows the Frame Check Sequence Error Detection status bits of the Data Link Status Regis-
ter.
DATA LINK STATUS REGISTER (DLSR) (INDIRECT ADDRESS = 0XNAH, 0X06H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
2
Frame Check
Sequence Error
Detection
RUR /
WC
0 - There is no FCS error detected in the data link channel.
1 - The HDLC Controller receives an erroneous FCS in the data link chan-
nel.
13.2.4.1.2 Step 2: Find out the next available receive data link buffer
When the LAPD Controller is receiving MOS message, the received message octets are written to the next
available receive data link buffer. The user is recommended to read Receive Data Link Byte Count Register for
next available receive data link buffer number.
432
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The table below shows how contents of the Receive Buffer Pointer bit of the Receive Data Link Byte Count
Register (RDLBCR) determines what the next available receive data link buffer number is.
RECEIVE DATA LINK BYTE COUNT REGISTER (RDLBCR) (INDIRECT ADDRESS = 0XN0H, 0X15H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Receive Buffer
Pointer
R
0 - The next available receive data link buffer for reading out BOS or MOS
message is Buffer 0.
1 - The next available receive data link buffer for reading out BOS or MOS
message is Buffer 1.
13.2.4.1.3 Step 3: Reading the Receive Data Link Byte Count Register
The user should read the length of MOS message from the Receive Data Link Byte Count Register. The re-
ceive LAPD Controller increments the Receive Data Link Byte Count Register value when each octet of MOS
message is received. After the Receive End of Transfer (RxEOT) interrupt is generated, the Receive Data Link
Byte Count Register should contain the length of entire MOS message.
The table below shows configurations of the Receive Data Link Byte Count [6:0] bits of the Receive Data Link
Byte Count Register (RDLBCR).
RECEIVE DATA LINK BYTE COUNT REGISTER (RDLBCR) (INDIRECT ADDRESS = 0XN0H, 0X15H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
6-0
Receive Data Link
Byte Count [6:0]
R
Value of these bits determines how many times a BOS message pattern
will be received by the framer before generating the Receive End of Trans-
fer (TxEOT) interrupt.
13.2.4.1.4 Step 4: Read MOS Message from receive data link buffer
Upon detection of the Receive End of Transfer (RxEOT) interrupt, the user should read the Message Type bit of
the Data Link Status Register (DLSR) to find out what is the type of message received.
The table below shows how contents of the Message Type bit of the Data Link Status Register (DLSR) deter-
mines what the type of message received in the data link channel is.
DATA LINK STATUS REGISTER (DLSR) (INDIRECT ADDRESS = 0XNAH, 0X06H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Message Type
RUR /
WC
0 - Message received in the data link channel is BOS.
1 - Message received in the data link channel is MOS.
After determined that the received message is an MOS one, the use should read the entire message from the
available receive data link buffer. The reading of these buffers is through the LAPD Buffer 0 indirect data regis-
ters and the LAPD Buffer1 indirect data registers. LAPD Buffer 0 and 1 indirect data registers have addresses
0xn6H and 0xn7H respectively. There is no indirect address register for receive data link buffer 0 and 1.
A microcontroller WRITE access to the LAPD Buffer indirect data registers will access the receive data link
buffer and a microcontroller READ will access the receive data link buffers. The very first READ access to the
LAPD Buffer indirect data register will always be direct to location 0 within the receive data link buffer.
For example, if the first octet of the MOS Message received is (10101100) and the next available receive data
link buffer of Channel n is 1. The user should be able to read pattern (01010110) from receive data link buffer 1
of Channel n. The following microprocessor access to the framer should be done:
433
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
RD
n7H
The result of the READ access should be 0xACH.
13.2.5 Receive SLCâ96 Data link Controller
This section describes how to configure the Receive SLC®96 Data Link Controller block to receive SLC®96
Data Link message and how to read out the message from the receive data link message buffer. The operation
of the Receive SLC®96 Data Link Controller is interrupt-driven. When a 36-bit SLC®96 Data Link message is
received, message octet is written to the next receive data link message buffer opposite to that last used. The
receive SLC®96 Data Link Controller generates interrupts to the microprocessor notifying it that a message is
received. The data link message can then be extracted from the appropriate receive data link buffer.
In order to enable this mode of operation, the framing mode must be set to SLC®96. The XRT84L38 allocates
two 6-byte buffers to provide SLC®96 Data Link Controller an alternating access mechanism for information re-
ceived. The bit ordering and usage is shown in the following table. The bits 7 and 6 are forced to 0 by the
SLC®96 Data Link Controller.
RECEIVE SLC®96 MESSAGE REGISTERS
BITBYTE
1/7
7
0
0
0
0
0
0
6
0
0
0
0
0
0
5
0
4
1
3
1
2
1
1
0
0
0
2/8
C1
C7
1
1
1
1
0
0
3/9
C6
0
C5
C11
M3
S4
C4
C10
M2
S3
C3
C9
M1
S2
C2
C8
0
4/10
5/11
6/12
A2
0
A1
1
S1
13.2.5.1 How to configure the SLC®96 Data Link Controller to receive SLC®96 Data Link Messages
This section describes how to configure the SLC®96 Data Link Controller to receive SLC®96 Data Link mes-
sage in a step-by-step basis.
The operation of the receive SLC®96 Data Link Controller is interrupt-driven. When an SLC®96 Data Link
message is receiving, message octets are written to the next receive data link message buffer opposite to that
last used. Every time the SLC®96 Data Link controller receives a 36-bit SLC®96 data link message, an RxEOT
interrupt is issued if it is enabled. This process continues until an ABORT sequence is received.
An interrupt is issued when one of the following conditions occurs and the corresponding interrupt enable bit is
set.
• The RxSOT is set when the beginning of a data link message is received.
• The RxEOT is set when the end of a data link block is received.
• The RxABORT is set when an ABORT sequence is received.
13.2.5.1.1 Step 1: Enable receive SLC®96 Data Link message interrupts
The receive SLC®96 Data Link Controller can generate a couple of interrupts indicating the status of SLC®96
message received to the microprocessor. These are the Receive Start of Transfer (RxSOT) interrupt and the
Receive End of Transfer (RxEOT) interrupt.
To enable these interrupts, the Receive Start of Transfer Enable bit and the Receive End of Transfer Enable bit
of the Data Link Interrupt Enable Register (DLIER) have to be set. In addition, the HDLC Controller Interrupt
Enable bit of the Block Interrupt Enable Register (BIER) needs to be one.
434
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The table below shows configurations of the Receive Start of Transfer Enable bit and the Receive End of Trans-
fer Enable bit of the Data Link Interrupt Enable Register.
DATA LINK INTERRUPT ENABLE REGISTER (DLIER) (INDIRECT ADDRESS = 0XNAH, 0X07H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
5
Receive Start of
Transfer Enable
R/W
0 - The Receive Start of Transfer interrupt is disabled.
1 - The Receive Start of Transfer interrupt is enabled.
3
Receive End of
Transfer Enable
R/W
0 - The Receive End of Transfer interrupt is disabled.
1 - The Receive End of Transfer interrupt is enabled.
The table below shows configurations of the HDLC Controller Interrupt Enable bit of the Block Interrupt Enable
Register.
BLOCK INTERRUPT ENABLE REGISTER (BIER) (INDIRECT ADDRESS = 0XNAH, 0X00H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3
HDLC Controller
Interrupt Enable
R/W
0 - Every interrupt generated by the HDLC Controller is disabled.
1 - Every interrupt generated by the HDLC Controller is enabled.
When these interrupt enable bits are set and the SLC®96 message is received in the data link channel, the
SLC®96 Data Link Controller changes the Receive Start of Transfer and Receive End of Transfer status bits of
the Data Link Status Register (DLSR). These two status indicators are valid until the Data Link Status Register
is read. Reading these register clears the associated interrupt if Reset Upon Read is selected in Interrupt Con-
trol Register (ICR). Otherwise, a write-to-clear operation by the microprocessor is required to reset these status
indicators.
The table below shows the Receive Start of Transfer and Receive End of Transfer status bits of the Data Link
Status Register.
DATA LINK STATUS REGISTER (DLSR) (INDIRECT ADDRESS = 0XNAH, 0X06H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
5
Receive Start of
Transfer
RUR /
WC
0 - There is no data link message in the data link channel.
1 - The SLC®96 Data Link Controller began to receive a data link message
in the data link channel.
3
Receive End of
Transfer
RUR /
WC
0 - No data link message was present in the data link channel.
1 - The SLC®96 Data Link Controller finished receiving a data link mes-
sage in the data link channel.
The SLC®96 Data Link Controller can also generate interrupts when the ABORT sequence is received in the
data link channel to the microprocessor. This is the Receive ABORT Sequence (RxABORT).
To enable this interrupt, the Receive ABORT Sequence Enable bit of the Data Link Interrupt Enable Register
(DLIER) have to be set. In addition, the HDLC Controller Interrupt Enable bit of the Block Interrupt Enable Reg-
ister (BIER) needs to be one.
435
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The table below shows configurations of the Receive ABORT Sequence Enable bit and the Receive IDLE Flag
Sequence Enable bit of the Data Link Interrupt Enable Register.
DATA LINK INTERRUPT ENABLE REGISTER (DLIER) (INDIRECT ADDRESS = 0XNAH, 0X07H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1
Receive ABORT
Sequence Enable
R/W
0 - The Receive ABORT Sequence interrupt is disabled.
1 - The Receive ABORT Sequence interrupt is enabled.
When these interrupt enable bits are set and the SLC®96 ABORT sequence is received in the data link chan-
nel, the SLC®96 Data Link Controller changes the Receive ABORT Sequence status bit of the Data Link Sta-
tus Register (DLSR). This status indicator is valid until the Data Link Status Register is read. Reading the reg-
ister clears the associated interrupt if Reset Upon Read is selected in Interrupt Control Register (ICR). Other-
wise, a write-to-clear operation by the microprocessor is required to reset these status indicators.
The table below shows the Receive ABORT Sequence status bit of the Data Link Status Register.
DATA LINK STATUS REGISTER (DLSR) (INDIRECT ADDRESS = 0XNAH, 0X06H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
1
Receive ABORT
Sequence
RUR /
WC
0 - There is no BOS ABORT sequence received in the data link channel.
1 - The SLC®96 Data Link Controller receives ABORT sequence in the
data link channel.
13.2.5.1.2 Step 2: Find out the next available receive data link buffer
When the SLC®96 Data Link Controller is receiving SLC®96 message, the received message octets are writ-
ten to the next available receive data link buffer. The user is recommended to read Receive Data Link Byte
Count Register for next available receive data link buffer number.
The table below shows how contents of the Receive Buffer Pointer bit of the Receive Data Link Byte Count
Register (RDLBCR) determines what the next available receive data link buffer number is.
RECEIVE DATA LINK BYTE COUNT REGISTER (RDLBCR) (INDIRECT ADDRESS = 0XN0H, 0X15H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Receive Buffer
Pointer
R
0 - The next available receive data link buffer for reading out data link mes-
sage is Buffer 0.
1 - The next available receive data link buffer for reading out data link mes-
sage is Buffer 1.
13.2.5.1.3 Step 3: Read SLC®96 Data LInk Message from receive data link buffer
Upon detection of the Receive End of Transfer (RxEOT) interrupt, the use should read the entire SLC®96 Data
Link message from the available receive data link buffer. The reading of these buffers is through the LAPD Buff-
er 0 indirect data registers and the LAPD Buffer1 indirect data registers. LAPD Buffer 0 and 1 indirect data reg-
isters have addresses 0xn6H and 0xn7H respectively. There is no indirect address register for receive data link
buffer 0 and 1.
A microcontroller WRITE access to the LAPD Buffer indirect data registers will access the receive data link
buffer and a microcontroller READ will access the receive data link buffers. The very first READ access to the
LAPD Buffer indirect data register will always be direct to location 0 within the receive data link buffer.
436
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
For example, if the first octet of the SLC®96 Message received is (00101011) and the next available receive
data link buffer of Channel n is 1. The user should be able to read pattern (00101011) from receive data link
buffer 1 of Channel n. The following microprocessor access to the framer should be done:
RD
n7H
The result of the READ access should be 0x2BH.
437
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
14.0 E1 HDLC CONTROLLER BLOCK
14.1 E1 TRANSMIT HDLC CONTROLLER BLOCK
14.1.1 Description of the E1 Transmit HDLC Controller Block
XRT84L38 allows user to insert data link information to outbound E1 frames. The data link information in E1
framing format mode can be inserted from:
• E1 Transmit Overhead Input Interface Block
• E1 Transmit HDLC Controller
• E1 Transmit Serial Input Interface
The Transmit Data Link Source Select [1:0] bits, within the Synchronization MUX Register (SMR) determine
source of the data link bits to be inserted into the outgoing E1 frames.
The table below shows configuration of the Transmit Data Link Source Select [1:0] bits of the Synchronization
MUX Register (SMR).
SYNCHRONIZATION MUX REGISTER (SMR) (INDIRECT ADDRESS = 0XN0H, 0X09H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3-2
Transmit Data Link
Source Select [1:0]
R/W
00 - The data link bits are inserted into the framer through the Transmit
Serial Data input Interface via the TxSer_n pins.
01 - The data link bits are inserted into the framer through the Transmit
HDLC Controller.
10 - The data link bits are inserted into the framer through the Transmit
Overhead Input Interface via the TxOH_n pins.
11 - The data link bits are inserted into the framer through the Transmit
Serial Data input Interface via the TxSer_n pins.
If the Transmit Data Link Source Select bits of the Transmit Data Link Select Register are set to 01, the Trans-
mit HDLC Controller block becomes input source of the data link bits in outgoing E1 frames.
Each of the eight framers within the XRT84L38 device contains an E1 Transmit High-level Data Link Controller
(HDLC) block. The function of this block is to provide a serial data link channel in E1 mode through the follow-
ing:
• The National bits (Sa4 through Sa8) of Timeslot 0 of non-FAS frame
• Timeslot 16 octet when the framer is in Common Channel Signaling mode
• D or E signaling timeslot channel
We will discuss how to configure XRT84L38 to transmit data link information through each of these data link
channels in later sections.
The E1 Transmit HDLC Controller block contains two major functional modules associated with E1 framing for-
mats. They are the LAPD Controller and the Bit-Oriented Signaling Processor.
There are two 96-byte transmit message buffers in shared memory for each of the eight framers to transmit da-
ta link information. When one message buffer is filled up, the Transmit HDLC Controller automatically switches
to the next message buffer to load data link messages. These two message buffers ping-pong among each
other for data link message transmission.
The LAPD Enable bit of the Data Link Control Register (DLCR) determines whether the Transmit HDLC Con-
troller block should perform as the LAPD Controller or the BOS Processor.
438
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The table below shows configuration of the LAPD Enable bit of the Data Link Control Register (DLCR).
DATA LINK CONTROL REGISTER (DLCR) (INDIRECT ADDRESS = 0XN0H, 0X13H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
0
LAPD Enable
R/W
0 - The Transmit HDLC Controller will send out Bit-Oriented Signaling
(BOS) message.
1 - The Transmit HDLC Controller will send out LAPD protocol or so-called
Message-Oriented Signaling (MOS) message.
14.1.2 How to configure XRT84L38 to transmit data link information through the National bits (Sa4
through Sa8)
As mentioned in previous section, the National bits (Sa4 through Sa8) of Timeslot 0 of non-FAS frame can be
used to transmit data link information in E1 mode.
The XRT84L38 allows the user to decide on the following:
• Whether the National bits will be used to carry the data link information bits.
• How many of the National Bits will be used to carry the Data Link information bits.
• Which of these National Bits will be used to carry the Data Link information bits.
The Transmit Signaling and Data Link Control [2:0] bits of the Transmit Signaling and Data Link Select Register
(TSDLSR) determines if the National bits will be used to carry data link information. The table below shows
configuration of the Transmit Signaling and Data Link Control [2:0] bits of the Transmit Signaling and Data Link
Select Register (TSDLSR).
TRANSMIT SIGNALING AND DATA LINK SELECT REGISTER (TSDLSR) (INDIRECT ADDRESS =
0XN0H, 0X0AH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
2-0
Transmit Signaling
and Data Link
Select
R/W
000 - The data link interface is source of the Sa4 through Sa8 Nation bits.
001 - The data link interface is source of the Sa4 through Sa8 Nation bits.
010 - The Sa4 through Sa8 Nation bits are forced to 1.
011 - The Sa4 through Sa8 Nation bits are forced to 1.
1xx - The Sa4 through Sa8 Nation bits are forced to 1.
If the Transmit Signaling and Data Link Select [2:0] bits of the Transmit Signaling and Data Link Select Register
is set to 000 or 001, the data link interface becomes source of the Sa4 through Sa8 National bits.
The Transmit Sa Data Link Select bits of the Transmit Signaling and Data Link Select Register (TSDLSR) de-
termine which ones of the National bits are configured as Data Link bits in E1 framing format mode. Depending
upon the configuration of the Transmit Signaling and Data Link Select Register, either of the following cases
may exists:
• None of the National bits are used to transport the Data Link information bits (That is, data link channel of
XRT84L38 is inactive).
• Any combination of between 1 and all 5 of the National bits can be selected to transport the Data Link infor-
mation bits.
439
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
The table below shows configuration of the Transmit Sa Data Link Select bits of the Transmit Signaling and Da-
ta Link Select Register (TSDLSR).
TRANSMIT SIGNALING AND DATA LINK SELECT REGISTER (TSDLSR) (INDIRECT ADDRESS =
0XN0H, 0X0AH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Transmit Sa8 Data
Link Select
R/W
0 - Source of the Sa8 Nation bit is not from the data link interface.
1 - Source the Sa8 National bit from the data link interface.
6
5
4
3
Transmit Sa7 Data
Link Select
R/W
R/W
R/W
R/W
0 - Source of the Sa7 Nation bit is not from the data link interface.
1 - Source the Sa7 National bit from the data link interface.
Transmit Sa6 Data
Link Select
0 - Source of the Sa6 Nation bit is not from the data link interface.
1 - Source the Sa6 National bit from the data link interface.
Transmit Sa5 Data
Link Select
0 - Source of the Sa5 Nation bit is not from the data link interface.
1 - Source the Sa5 National bit from the data link interface.
Transmit Sa4 Data
Link Select
0 - Source of the Sa4 Nation bit is not from the data link interface.
1 - Source the Sa4 National bit from the data link interface.
14.1.3 How to configure XRT84L38 to transmit data link information through Timeslot 16 octet
In E1 mode, Timeslot 16 octet can be configured to transmit the following:
• Channel Associated Signaling (CAS) bits A, B, C and D
• Common Channel Signaling (CCS) bits
The Common Channel Signaling (CCS) messages are actually data link information applicable to all thirty-two
timeslots of an E1 frame, thus the name Common Channel Signaling. The Transmit Signaling and Data Link
Control [2:0] bits of the Transmit Signaling and Data Link Select Register (TSDLSR) determine if Timeslot octet
will be used to carry data link information or CAS signals. The table below shows configuration of the Transmit
Signaling and Data Link Control [2:0] bits of the Transmit Signaling and Data Link Select Register (TSDLSR).
TRANSMIT SIGNALING AND DATA LINK SELECT REGISTER (TSDLSR) (INDIRECT ADDRESS =
0XN0H, 0X0AH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
2-0
Transmit Signaling
and Data Link
Select
R/W
000 - Timeslot 16 octet is taken directly from the Transmit Serial Input
Interface through the TxSer_n pin.
001 - Timeslot 16 octet is taken directly from the Transmit Overhead Input
Interface through the TxOH_n pin or the Transmit Signaling Control Regis-
ter of Timeslot 16.
010 - Timeslot 16 octet is taken directly from the Transmit Serial Input
Interface through the TxSer_n pin.
011 - Timeslot 16 octet is taken directly from the Transmit Overhead Input
Interface through the TxOH_n pin or the Transmit Signaling Control Regis-
ter of Timeslot 16.
1xx - Timeslot 16 octet is taken from the data link interface.
If the Transmit Signaling and Data Link Select [2:0] bits of the Transmit Signaling and Data Link Select Register
are set to 1xx, the data link interface becomes source of the Timeslot 16 octet.
14.1.4 How to configure XRT84L38 to transmit data link information through D or E Channels
440
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
The XRT84L38 can configure any one or ones of the thirty-two E1 channels to be D or E channels except for
Channel number 0. D channel is used primarily for data link applications. E channel is used primarily for signal-
ing for circuit switching with multiple access configurations.
The Transmit Conditioning Select [3:0] bits of the Transmit Channel Control Register (TCCR) of each channel
determine whether that particular channel is configured as D or E channel. These bits also determine what
type of data or signaling conditioning is applied to each channel.
TRANSMIT CHANNEL CONTROL REGISTER (TCCR) (INDIRECT ADDRESS = 0XN2H, 0X00H - 0X1FH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3-0
Transmit Condi-
tioning Select
R/W
1111 - This channel is configured as D or E timeslot.
If the Transmit Conditioning Select [3:0] bits of the Transmit Channel Control Register of a particular timeslot
are set to 1111, that timeslot is configured as a D or E timeslot.
NOTE: Timeslot 0 can never be configured as D or E timeslot.
14.1.5 Transmit BOS (Bit Oriented Signaling) Processor
The Transmit BOS Processor handles transmission of BOS messages through the E1 data link channel. It de-
termines how many repetitions a certain BOS message will be transmitted. It also inserts BOS IDLE flag se-
quence and ABORT sequence to be transmitted on the data link channel. Please see Section ? for descriptions
of BOS message format and how to transmit BOS message.
14.1.6 Transmit MOS (Message Oriented Signaling) or LAPD Controller
The Transmit LAPD controller implements the Message-Oriented protocol based on ITU Recommendation
Q.921 Link Access Procedures on the D-channel (LAPD) type of protocol. It provides the following functions:
• Zero stuffing
• T1/E1 transmitter interface
• Transmit message buffer access
• Frame check sequence generation
• IDLE flag insertion
• ABORT sequence generation
Two 96-byte buffers in shared memory are allocated for LAPD transmitter to reduce the frequency of micropro-
cessor interrupts and alleviate the response time requirement for microprocessor to handle each interrupt.
There are no restrictions on the length of the message. However the 96-byte buffer is deep enough to hold one
entire LAPD path or test signal identification message. Please see Section ? for descriptions of MOS message
format and how to configure the LAPD Controller to transmit MOS message.
14.2 E1 RECEIVE HDLC CONTROLLER BLOCK
14.2.1 Description of the E1 Receive HDLC Controller Block
XRT84L38 detects and extracts data link information from incoming E1 frames. The data link information in E1
framing format mode can be extracted to:
• E1 Receive Overhead Output Interface Block
• E1 Receive HDLC Controller
• E1 Receive Serial Output Interface
The extracted data link information is routed to the E1 Receive Overhead Output Interface and the E1 Receive
Serial Output Interface no matter whether the E1 Receive HDLC Controller module is activated or not.
Each of the eight framers within the XRT84L38 device contains an E1 Receive High-level Data Link Controller
(HDLC) block. The function of this block is to establish a serial data link channel in E1 mode through the follow-
ing:
441
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
• The National bits (Sa4 through Sa8) of Timeslot 0 of non-FAS frame
• Timeslot 16 octet when the framer is in Common Channel Signaling mode
• D or E signaling timeslot channel
We will discuss how to configure XRT84L38 to transmit data link information through each of these data link
channels in later sections.
The E1 Transmit HDLC Controller block contains two major functional modules associated with E1 framing for-
mats. They are the LAPD Controller and the Bit-Oriented Signaling Processor.
There are two 96-byte receive message buffer in shared memory for each of the eight framers to receive data
link information. When one message buffer is filled up, the E1 Receive HDLC Controller automatically switches
to the next message buffer to store data link messages. These two message buffers ping-pong among each
other for data link message storage.
The Message Type bit of the Data Link Status Register (DLSR) determines which one of the three messages is
received and processed by the Receive HDLC Controller block.
The table below shows configuration of the Message Type bit of the Data Link Status Register (DLSR).
DATA LINK STATUS REGISTER (DLSR) (INDIRECT ADDRESS = 0XNAH, 0X06H)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Message Type
RUR /
WC
0 - The Receive HDLC Controller receives and processes Bit-Oriented Sig-
naling (BOS) message.
1 - The Receive HDLC Controller receives and processes LAPD protocol
or Message-Oriented Signaling (MOS) message.
14.2.2 How to configure XRT84L38 to receive data link information through the National bits (Sa4
through Sa8)
As mentioned in previous section, the National bits (Sa4 through Sa8) of Timeslot 0 of non-FAS frame can be
used to receive data link information in E1 mode.
The XRT84L38 allows the user to decide on the following:
• Whether the National bits will be used to carry the data link information bits.
• How many of the National Bits will be used to carry the Data Link information bits.
• Which of these National Bits will be used to carry the Data Link information bits.
The Receive Signaling and Data Link Control [2:0] bits of the Receive Signaling and Data Link Select Register
(RSDLSR) determines if the National bits will be used to carry data link information. The table below shows
configuration of the Receive Signaling and Data Link Control [2:0] bits of the Receive Signaling and Data Link
Select Register (RSDLSR).
RECEIVE SIGNALING AND DATA LINK SELECT REGISTER (RSDLSR) (INDIRECT ADDRESS = 0XN0H,
0X0CH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
2-0
Receive Signaling
and Data Link
Select
R/W
000 - The data link interface is destination of the Sa4 through Sa8 Nation
bits.
001 - The data link interface is destination of the Sa4 through Sa8 Nation
bits.
010 - The Sa4 through Sa8 Nation bits are forced to 1.
011 - The Sa4 through Sa8 Nation bits are forced to 1.
1xx - The Sa4 through Sa8 Nation bits are forced to 1.
442
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
If the Receive Signaling and Data Link Select [2:0] bits of the Receive Signaling and Data Link Select Register
are set to 000 or 001, the data link interface becomes destination of the Sa4 through Sa8 National bits.
The Receive Sa Data Link Select bits of the Receive Signaling and Data Link Select Register (RSDLSR) deter-
mine which ones of the National bits are configured as Data Link bits in E1 framing format mode. Depending
upon the configuration of the Receive Signaling and Data Link Select Register, either of the following cases
may exists:
• None of the National bits are used to transport the Data Link information bits (That is, data link channel of
XRT84L38 is inactive).
• Any combination of between 1 and all 5 of the National bits can be selected to transport the Data Link infor-
mation bits.
The table below shows configuration of the Receive Sa Data Link Select bits of the Receive Signaling and Data
Link Select Register (RSDLSR).
RECEIVE SIGNALING AND DATA LINK SELECT REGISTER (RSDLSR) (INDIRECT ADDRESS = 0XN0H,
0X0CH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
7
Receive Sa8 Data
Link Select
R/W
0 - Destination of the Sa8 Nation bit is not the data link interface.
1 - Destination of the Sa8 National bit is the data link interface.
6
5
4
3
Receive Sa7 Data
Link Select
R/W
R/W
R/W
R/W
0 - Destination of the Sa7 Nation bit is not the data link interface.
1 - Destination of the Sa7 National bit is the data link interface.
Receive Sa6 Data
Link Select
0 - Destination of the Sa6 Nation bit is not the data link interface.
1 - Destination of the Sa6 National bit is the data link interface.
Receive Sa5 Data
Link Select
0 - Destination of the Sa5 Nation bit is not the data link interface.
1 - Destination of the Sa5 National bit is the data link interface.
Receive Sa4 Data
Link Select
0 - Destination of the Sa4 Nation bit is not the data link interface.
1 - Destination of the Sa4 National bit is the data link interface.
14.2.3 How to configure XRT84L38 to receive data link information through Timeslot 16 octet
In E1 mode, Timeslot 16 octet can be configured to receive the following:
• Channel Associated Signaling (CAS) bits A, B, C and D
• Common Channel Signaling (CCS) bits
The Common Channel Signaling (CCS) messages are actually data link information applicable to all thirty-two
timeslots of an E1 frame, thus the name Common Channel Signaling. The Receive Signaling and Data Link
Control [2:0] bits of the Receive Signaling and Data Link Select Register (RSDLSR) determine if Timeslot octet
443
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
will be used to carry data link information or CAS signals. The table below shows configuration of the Receive
Signaling and Data Link Control [2:0] bits of the Receive Signaling and Data Link Select Register (RSDLSR).
RECEIVE SIGNALING AND DATA LINK SELECT REGISTER (RSDLSR) (INDIRECT ADDRESS = 0XN0H,
0X0CH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
2-0
Receive Signaling
and Data Link
Select
R/W
000 - Timeslot 16 octet is extracted directly to the Receive Serial Output
Interface through the RxSer_n pin.
001 - Timeslot 16 octet is extracted directly to the Receive Overhead Out-
put Interface through the RxOH_n pin or the Receive Signaling Control
Register of Timeslot 16.
010 - Timeslot 16 octet is extracted directly to the Receive Serial Output
Interface through the RxSer_n pin.
011 - Timeslot 16 octet is extracted directly to the Receive Overhead Out-
put Interface through the RxOH_n pin or the Receive Signaling Control
Register of Timeslot 16.
1xx - Timeslot 16 octet is extracted to the data link interface.
If the Receive Signaling and Data Link Select [2:0] bits of the Receive Signaling and Data Link Select Register
are set to 1xx, the data link interface becomes destination of the Timeslot 16 octet.
14.2.4 How to configure XRT84L38 to receive data link information through D or E Channels
The XRT84L38 can configure any one or ones of the thirty-two E1 channels to be D or E channels except for
Channel number 0. D channel is used primarily for data link applications. E channel is used primarily for signal-
ing for circuit switching with multiple access configurations.
The Receive Conditioning Select [3:0] bits of the Receive Channel Control Register (RCCR) of each channel
determine whether that particular channel is configured as D or E channel. These bits also determine what
type of data or signaling conditioning is applied to each channel.
RECEIVE CHANNEL CONTROL REGISTER (RCCR) (INDIRECT ADDRESS = 0XN2H, 0X60H - 0X7FH)
BIT
NUMBER
BIT NAME
BIT TYPE
BIT DESCRIPTION
3-0
Receive Condition-
ing Select
R/W
1111 - This channel is configured as D or E timeslot.
If the Receive Conditioning Select [3:0] bits of the Receive Channel Control Register of a particular timeslot are
set to 1111, that timeslot is configured as a D or E timeslot.
NOTE: Timeslot 0 can never be configured as D or E timeslot.
14.2.5 Receive BOS (Bit Oriented Signaling) Processor
The Receive BOS Processor handles receiving and processing of BOS messages through the E1 data link
channel. It generates Receive End of Transfer (RxEOT) interrupt each time a BOS message is received and
stores the BOS message into the receive message buffer. Please see Section ? for how to configure the BOS
Processor Block to receive BOS message.
14.2.6 Receive LAPD Controller
The receive LAPD controller implements the Message-Oriented protocol based on ITU Recommendation
Q.921 Link Access Procedures on the D-channel (LAPD) type of protocol. It provides the following functions:
• Zero deletion
• Pattern recognition for IDLE flag detection
• Pattern recognition for ABORT sequence detection
444
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
• Frame check sequence verification
• T1 receiver interface
• Receive data link message buffer access
Two 96-byte buffers in shared memory are allocated for receive LAPD Controller to reduce the frequency of mi-
croprocessor interrupts and alleviate the response time requirement for microprocessor to handle each inter-
rupt. There are no restrictions on the length of the message received. However, the 96-byte buffer is deep
enough to hold one entire LAPD path or test signal identification message.
Please see Section ? for how to configure the receive LAPD Controller to receive and extract MOS messages.
445
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
15.0 TRANSMIT LIU INTERFACE
The purpose of the Transmit LIU Interface is to take the outbound frame data from the Transmit Framer block
and to do the following:
• To encode the outbound frame data into any one of the following formats
• Single-Rail (e.g., a binary data stream)
• Dual-Rail, AMI Line Code
• Dual Rail, HDB3 Line Code
• To output this encoded data to an LIU device via the TxPOS, TxNEG and TxLineClk output pins.
16.0 RECEIVE LIU INTERFACE
The purpose of the Receive LIU Interface is to receive either single-rail or dual-rail data from an LIU IC and to
do the following:
• Decode this incoming data from the single-rail, AMI or HDB3 line code and convert it into a binary data
stream
• Route this binary data stream to the Receive Framer Block
• Detect and Declare the Loss of Signal Condition.
446
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV. 1.0.0
áç
ORDERING INFORMATION
PART NUMBER
PACKAGE
OPERATING TEMPERATURE RANGE
-400C to +850C
XRT84L38
388 Pin Plastic Ball Grid Array
PACKAGE DIMENSIONS
388 Pin Plastic Ball Grid Array
(35 x 35 mm PBGA)
Rev. 1.0 (Bottom View)
26
24
22
20
18
16
14
12
10
8
6
4
2
Chamfer
Optional
25
23
21
19
17
15
13
11
9
7
5
3
1
A
B
C
D
E
F
G
H
J
b
K
L
M
N
P
D
D1
R
T
U
V
W
Y
e
AA
AB
AC
AD
AE
AF
mp
e
D1
D
D2
C
b
A2
A
A1
Inches
Millimeters
Symbol
MIN
MAX
MIN
MAX
A
A1
A2
b
0.075
0.020
0.039
0.024
0.016
1.370
0.106
0.028
0.051
0.035
0.028
1.386
1.90
0.50
1.00
0.60
0.40
34.80
2.70
0.70
1.30
0.90
0.70
35.20
C
D
D1
D2
e
1.250BSC
1.177 1.185
0.050BSC
31.75BSC
29.90
30.10
1.27BSC
Note: The control dimension is the millimeter column
447
áç
XRT84L38
OCTAL T1/E1/J1 FRAMER
REV.1.0.0
REVISIONS
Rev. 1.0.0 - February 2004 - Release to Production
NOTICE
EXAR Corporation reserves the right to make changes to the products contained in this publication in order
to improve design, performance or reliability. EXAR Corporation assumes no responsibility for the use of
any circuits described herein, conveys no license under any patent or other right, and makes no represen-
tation that the circuits are free of patent infringement. Charts and schedules contained here in are only for
illustration purposes and may vary depending upon a user’s specific application. While the information in
this publication has been carefully checked; no responsibility, however, is assumed for inaccuracies.
EXAR Corporation does not recommend the use of any of its products in life support applications where
the failure or malfunction of the product can reasonably be expected to cause failure of the life support sys-
tem or to significantly affect its safety or effectiveness. Products are not authorized for use in such applica-
tions unless EXAR Corporation receives, in writing, assurances to its satisfaction that: (a) the risk of injury
or damage has been minimized; (b) the user assumes all such risks; (c) potential liability of EXAR Corpo-
ration is adequately protected under the circumstances.
Copyright 2004 EXAR Corporation
Datasheet February 2004.
Reproduction, in part or whole, without the prior written consent of EXAR Corporation is prohibited.
448
相关型号:
©2020 ICPDF网 联系我们和版权申明