The CX28394/28395/28398 is a family of multiple framers for T1/E1/J1 and Integrated
Service Digital Network (ISDN) primary rate in terfaces operating at 1.5 44 Mbps or 2 .048
Mbps. All framers are totally independent, and each combines a sophisticated framing
synchronizer and transmit/receive slip buffers. Operations are controlled through a
series of memory-mapped registers accessible via a parallel microprocessor port.
Extensive register support is provided for alarm and error monitoring, signaling
supervision (including ISDN D-channel/SS7 process), per-channel trunk conditioning,
and Facility Data Link (FDL) maintenance. A flexible serial Time Division Multiplexed
(TDM) system interface that supports bus rates from 1.536 to 8.192 MHz is featured.
Extensive test and diagnostic functions include a full set of loopbacks, Pseudo Random
Bit Sequence (PRBS) test pattern generation, Bit Error Rate (BER) meter, and forced
error insertion.
Information in this document is provided in connection with Conexant Systems, Inc. (“Conexant”) products. These materials are
provided by Conexant as a service to its customers and may be used for informational purposes only. Conexant assumes no
responsibility for errors or omissions in these materials. Conexant may make changes to specifications and product descript ion s at
any time, without notice. Conexant makes no commitment to update the information and shall have no responsibility whatsoever for
conflicts or incompatibilities arising from future changes to its specifications and product descriptions.
No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted by this document. Except as
provided in Conexant’s Terms and Conditions of Sale for such products, Conexant assumes no liability whatsoever.
THESE MATERIALS ARE PROVIDED “AS IS” WITHOUT WARRANTYOF ANY KIND, EITHER EXPRESS OR IMPLIED, RELATING
TO SALE AND/OR USE OF CONEXANT PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A
PARTICULARPURPOSE, CONSEQUENTIAL OR INCIDENTAL DAMAGES,MERCHANTABILITY, OR INFRINGEMENT OF ANY
PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTYRIGHT. CONEXANT FURTHER DOES NOT WARRANT THE
ACCURACY OR COMPLETENESS OF THE INFORMATION, TEXT, GRAPHICS OR OTHER ITEMS CONTAINED WITHIN THESE
MATERIALS. CONEXANT SHALL NOT BE LIABLE FOR ANY SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
DAMAGES,INCLUDING WITHOUT LIMITATION, LOST REVENUES OR LOST PROFITS, WHICH MAYRESULT FROM THE USE
OF THESE MATERIALS.
Conexant products ar e not intended for use in medical, lifesaving or life sustaining applications. Conexant customers using or selling
Conexant products for use in such applications do so at their own risk and agree to fully indemnify Conexant for any damages
resulting from such improper use o r sale.
The following are trademarks of Conexant Systems, Inc.: Conexant™, the Conexant C symbol, and “What’s Next in Communications
Te chnologies”™. Product names or services listed in this publication are for identification purposes only, and may be trademark s of
third parties. Third-par ty brands and names are the property of their respective owners.
For additional disclaimer information, please consult Conexant’s Legal Information posted at www.conexant.com,whichis
incorporated by reference.
Reader Response: Conexant strives to produce quality documentation and welcomes your feedback. Please send comments and
suggestions to tech.pubs@conexant.com. For tec hnical questions, contact your local Conexant sales office or field applicat ions
engineer.
100054EConexant
Page 3
Typical Quad T1/E1 Application
Address
Bus
Microprocessor
Data
Bus
Typical x16 T1/E1 Application
12
T1 or E1 Connection at DSX Levels
CX28380 (Quad LIU)
CX28394 (Octal T1/E1 Framer)
8
Local PCM Highway (8192 kbps)
8394-8-5_015
T1 or E1 Line Interfaces, SONET/SDH Mapper or M13/E13 Mux
Address
Bus
Microprocessor
Data
Bus
Selects
12
8
2
Chip
CX28395 ( x16 T1/E1 Framer)
Local PCM Highways 32 at 1536 kbps to 8 at 8192 kbps)
CX28395 ( x16 T1/E1 Framer)
2
Ordering Information
Model NumberNumber of FramersPackageOperating Temperature
CX28394-224128-pin TQFP–40 to 85 °C
CX28398-228208-pin PQFP–40 to 85 °C
CX28398-238272-pin B G A–40 to 85 °C
CX28395-1916318-pin BGA–40 to 85 °C
8394-8-5_014
CX28395-1816318-pin BGA0 to 70 °C
CX28398-248208-pin CABGA–40 to 85 °C
BT00-D660-00 1CX28398/CX283 80 Ev a lu a t io n Mod ule
100054EConexant
Page 4
Detailed Feature Summary
Frame Alignm ent
• Framed formats:
– Independent transm it and receive
The CX2839x devices each contain multiple T1/E1 framers which provide the
data access and framing portion of T1 and E1 physical layer interfaces:
1.1.1 External Datalink
1.1.2 RINDO/TINDO
Device
CX283944
CX283988
CX2839516
While the framers are identical, there are minor dif ferences among the de vices
due to the pins provided. These differences are summarized below.
The CX28394 and CX28398 devices include an External Datalink (DL3) which
provides signal access to any bit(s) in any time slot of all frames, odd frames, or
even frames, including T1 framing bits. Refer to Section 2.2.8, External Receive
Data Link (CX28394 and CX28398 Only), and 2.4.1, External Transmit Data
Link (CX28394 and CX28398 Only). The DL3 signals are not available on the
CX28395 device.
Receive and Transmit Time Slot Indicator signals are provided by each framer to
mark selected (programmable) recei ve an d transmit system bus time slot s. On the
CX28394 and CX28398 de vices, the se signals appe ar on dif feren t pins depen ding
on whether Multi plex ed System Bus mode o r Non-Multiple x ed Syst em Bus mode
is selected. On the CX28395, they are available only in Multiplexed Bus mode.
Number of Framers
100054EConexant1-1
Page 20
1.0 Product DescriptionCX28394/28395/28398
1.1 OverviewQuad/x16/Octal—T1/E1/J1 Framers
1.1.3 LIU Serial Port
The CX28394 and CX28398 devices include a serial interface which allows a
microprocessor to indirectly communicate with a line interface unit such as the
CX28380 Quad T1/E1 LIU. This interface allows the microprocessor to control
and query the LIU status. This serial interface is not available on the CX28395.
1.1.4 Transmit/Receive Line Interface
The CX28394 and CX28398 devi ces inc lu de li ne in terfac es which can operate in
either of two modes: bipolar NRZ or unipolar NRZ. In bipolar NRZ mode,
receiver signals RPOSI, RNEGI, and RCKI are used; and transmitter signals
TPOSO, TNEGO, and TCKO are used. In unipolar NRZ mode, receiver signals
RNRZ and RCKI are used, and transmitter signals TNRZO and TCKO are used.
The CX28395 device provides only unipolar NRZ operation and signals.
Figure 1-1 illustrates the CX28395 Functional Block Diagram (single framer).
Figure 1-1. CX28395 Functional Block Diagram
Receive NRZ Data
Receive NRZ Clock
Transmit NRZ Data
Transmit NRZ Clock
T1/E1
Receive
Framer
Overhead
Insertion
Data Link Controllers
Transmit
DL1 + DL2
T1/E1
Framer
RX
Slip
Buffer
TX
Slip
Buffer
Receive
System
Bus
Transmit
System
Bus
8394-8-5_011
1-2Conexant100054E
Page 21
CX28394/28395/283981.0 Product Description
Quad/x16/Octal—T1/E1/J1 Framers
1.2 Pin Assignments
The CX28394 is packaged in a 128-pi n Quad Flat P ac k (TQFP). The CX 28395 is
packaged in a 318-pin Ball Grid Array (BGA) multi-chip module (MCM). The
CX28398 has two package alternatives: a 208-pin Quad Flat Pack (MQFP) and a
272-pin BGA. Pinout diagrams are provided in Figures 1-2 through 1-6 and
Tables 1-1 through 1-4 summarize pin assignments for system bus pins. Table 1-5
lists all other pin assignments.
the hardware signals.
remain unconnected if the active high input state is desired:
A[7:0]Address lines unused in INTEL bus mode.
MOTO*Pullup selects INTEL bus mode if unconnected.
SYNCMDPullup selects synchronous processor interface.
TDI (CX28394/28398)JTAG unused if not connected.
TDI1, TDI2 (CX28395) JTAG unused if not connected.
TMSJTAG unused if not connected.
TCKDisables JTAG if not connected.
TRST*Disables JTAG reset if not connected.
RST*Disables hardware reset if not connected.
SERDIMay be left unconnected if not used.
1.2 Pin Assignments
Figures 1-7 through 1-12 illustrate the devices’ logic, and Table 1-6 defines
The following input pins cont ain an i nt ernal pul lu p r esi sto r ( >50 k
power-up state and all PIO pins to the input state. RST*
is not mandatory since power-on reset circuit performs
an identical function. RST* must remain asserted for a
minimum of 2 processor clock cycles (MCLK or SYSCKI,
depending on SYNCMD selectio n).
from external source.
with synchronous MPU applicatio ns. MCLK is used
when SYNCMD = 1 and i gnored when SYNCMD = 0.
with respect to MCLK. Supports Intel- or Motorola-style
buses:
0 = Asynchronous Bus; read and write latches are
asynchronously controlled by CS*, DS*, and R/W*
signals.
1 = Synchronou s Bus; MCLK rising edge samples
CS*, DS*, and R/W* to determine valid read/write cycle
timing.
MOTO*Motorola Bus
Mode
A[10:0]Address Bus4IAddress used to identify a register for subsequent
A[11:0]Address Bus5, 8IAddress used to identify a re gister for subsequent
AD[7:0]Data Bus or
Address Data
AS*(ALE)Address St robe4, 5, 8IFor all processor bus modes, AS* fallin g edge
CS1*, CS2*Chip Select5IActive-low enables read/write decoder. Active high ends
4, 5, 8ISelects In tel- or Motorola-style microprocess or
interface. DS*, R/W*, A[11:0], and AD[7:0] functions are
affected.
0 = Motorola; AD[7:0] is data, A[11:0] is address,
DS* is data strobe, and R/W* indicates read (high) or
write (low) data direction.
1 = Intel; AD[7:0] is multiplexed address/data, A[7:0]
is ignored, A[11:8] is address, DS* is read strobe (RD*),
and R/W* is write strobe (WR*).
read/write data transfer cycle. In Motorola bus mode, all
eleven address bits (A[10:0]) are valid. In Intel bus
mode, only upper three bits (A[10:8]) are used.
read/write data transfer cycl e. In Motorola bus mode, all
twelve address bits (A[11:0]) are valid. In Intel bus
mode, only upper four bits (A[11:8]) are used.
4, 5, 8I/OMultiplexed address/data (Intel) or data only(Motorola).
Refer to MOTO* signal definition.
asynchronously latches address from A[11:0]
(Motorola) or A[11:8], AD[7:0] (Intel) to identify one
register for subsequent read/write data transfer cycle.
current read or write cycle and places data bus output in
high impedance. CS1* is the chip select pin for framers
1 to 8, CS2* is the chip select for framers 9 to 16.
CS*Chip Select4, 8IActive-low enables read/write decoder. Active high ends
(1)
I/ODefinition
current read or write cycle and places data bus output in
high impedance.
DS*(RD*)Data Strobe or
Read Strobe
R/W*(WR*)Read/Write
Direction or
Write Strobe
ONESECOne Second
Timer
ONESEC1
ONESEC2
INTR*Interrupt
INTR1*
INTR2*
One Second
Timer
Request
Interrupt
Request
4, 5, 8IAct ive-low read data strobe (RD*) for MOTO* = 1, or
data strobe (DS*) for MOTO* = 0.
4, 5, 8IActive-low write data strobe (WR*) for MOTO* = 1, or
data select (R/W*) for MOTO* = 0.
4, 8PIOControls or marks one-second interval used for status
reporting. When input, the timer is aligned to ONESEC
rising edge. When outp ut, rising edge indicates start of
each one-second interval.
5PIOControls or marks one-second interval used for status
reporting. When input, the timer is aligned to ONESEC
rising edge. When output, rising edge indicates start of
each one-second interval. ONESEC1 is the one second
timer for framers 1 to 8, ONESEC2 is the one second
timer for framers 9 to 16.
4, 8OOpen drain act ive low output signifies one or more
pending interrupt requests. INTR* goes to
high-impedance state with weak (>50 kΩ) internal pullup
resistance after processor has serviced all pending
interrupt requests.
5OOpen drain active low output signifies one or more
pending interrupt requests. INTRn* goes to
high-imped an ce st at e wi th we ak ( >50 k Ω) interna l pullup
resistance after processor has serviced all pending
interrupt requests. INTR1* is the interrupt request for
framers 1 to 8, INTR2* is the interrupt request for
framers 9 to 16.
DTACK*Data Transfer
Acknowledge
DTACK1*
DTACK2*
Data Transfer
Acknowledge
4, 8OOpen drain act ive low output signifie s in-progress data
transfer cycle. DTACK* remains asserted (low) for as
long as AS* and CS* are both active-low.
5OOpen drain active low output signifies in-progress data
transfer cycle. DTACKn* remains asserted (low) for as
long as AS* and CSn* are both active-low.
1-32Conexant100054E
Page 51
CX28394/28395/283981.0 Product Description
Quad/x16/Octal—T1/E1/J1 Framers
1.2 Pin Assignments
Table 1-6. Hardware Signal Definitions (3 of 9)
Pin LabelSignal NameDevice
SERDISerial Data Input4, 8ISerial data input from an L IU is sampled on rising edge
SERCKOSerial Clock4, 8OSerial bit clock provided for transmitting and receiving
SERDOSerial Data
Output
SERCS*Serial Chip
Select
SERCS1*
SERCS2*
Serial Chip
Selects
(1)
LIU Serial Interface
4, 8OAddress a nd data is output to an LIU serially on SERDO.
4OChip select line used to select an LIU’s serial port for
8OChip select li nes used to select an LIU’s serial port for
Transmitter (XMTR)
I/ODefinition
of SERCKO and written into Seri al Data Register; addr
023.
serial LIU data on SERDI and SERDO. SERCKO
frequency is 1.024 MHz or 8.192 MHz selectable.
Data changes on falli ng edge of SERCKO.
communication. SERCS is controlled in Serial
Configuration Register; addr 025.
communication. SERCS1* and SERCS2* are
independently controlled in Serial Configuration
Register; addr 025.
TCKI[4:1]
TCKI[8:1]
TCKI[16:1]
T1ACKIT1 All Ones
E1ACKIE1 All Ones
TPOSO[4:1]
TPOSO[8:1]
TNEGO[4:1]
TNEGO[8:1]
TDLI[4:1]
TDLI[8:1]
TX Clock Input4
Clock
Clock
TX Positive Rail
Output
TX Negative Rail
Output
TX Data Link
Input
IPrimary TX line rate clocks for tra nsmitter signals:
8
5
4, 5, 8ISystem optionally applies T1ACKI to use for T1 AIS
4, 5, 8ISystem optionally applies E1ACKI to use for E1 AIS
4
8
4
8
4
8
TPOSO, TNEGO, TNRZO, MSYNCO, TDLI, and TDLCKO.
If TSLIP is bypassed, TCKI also clocks TSB signals.
transmission in case the selected primary transmit clock
source fa ils . T1ACKI is eith er ma nually or automatical ly
switched to replace TCKI (see [AI SCLK; addr 075]).
Systems without a T1 AIS clock should tie T1ACK I to
ground.
transmission in case the selected primary transmit clock
source fa ils . E1ACKI is eith er ma nually or automatical ly
switched to replace TCKI (see [AI SCLK; addr 075]).
Systems without an E1 AIS clock should tie E1ACKI to
ground.
OLine rate data output from ZCS encoder changes on
rising edge of TCKO. Active-high marks transmissi on of
a positive AMI pulse.
OLine-rate dat a output from ZCS encoder changes on
rising edge of TCKO. Active high marks transmission of a
negative AMI pulse.
ISelected time slot bits are sample d on TD LCKO falling
edge for insertion into th e transm it outpu t stream d uring
external data link applications.
TDLCKO[4:1]
TDLCKO[8:1]
TX Data Link
Clock
4
8
OGapped version of TCKI for ext ernal data link
applications. TDLCKO high clock pulse coin cides with
low TCKI pulse interval during selected time slot bits,
else TDLCKO low (see [DL3_TS; addr 015]).
OLine rate clock. TCKO equals selected TCKI or T1ACKI
(E1ACKI).
OLine-rate data output from transmitter on rising edge of
TCKO. TNRZO does not inclu de ZCS encoded bipolar
violations.
OActive high for one TCKI clock cycle to mark the first bit
of TX multiframe coinc id en t wi th TN RZO. Output on
rising edge of TCKO.
ILine rate clock samples RPOSI and RNEGI or RNRZ.
ILine rate data input on rising edge of RCKI. Non-return
to zero (NRZ) receive data.
ILine rate data input on rising edge of RCKI. RPOSI and
RNEGI levels are interpre ted as received AMI pulses,
encoded as follows:
RPOSIRNEGIRX Pulse Polarity
00No pulse
01Negative AMI pulse
10Positive AMI pulse
11Invalid (decoded as a p ul se)
Unipolar. Non-return to zero (NRZ) data may be
connected to RPOSI or RNEGI in which case the other
input should be connected to ground. In this
configuratio n RAMI [RCR0;addr040] shou ld be set to 1
(receive AMI line format) and DIS_LCV
[RALM; addr 045] should be set to 1 (disable LCV
counting and reporting).
RNEGI[4:1]
RNEGI[8:1]
RDLO[4:1]
RDLO[8:1]
RDLCKO[4:1]
RDLCKO[8:1]
RX Negative Rail
Input
RX Data Link
Output
RX Data Link
Clock Output
4
8
4
8
4
8
ILine rate data input on rising edge of RCKI. See RPOSI
signal definition.
OLine rate NRZ data output from receiver on falling edge
of RCKI. All receive data is rep resented at the RDLO pin.
However, selective RDLO bit positions are also marked
by RDLCKO for external data link applications.
OGapped version of RCKI for external data link
applications. RDLCKO high clock pulse coinci des with
low RCKO pulse interval during selected time slot bits,
otherwise RDLCKO is low (see Figure 2-4, Receive
IBit clock and I/O signal ti ming for TSB according to
system bus mode (see [SBI_CR; ad dr 0D0]). System
chooses from one of two different clocks to act as TSB
clock source (see [CMUX; addr 01A]). Rising or falling
edge clocks are independently configurable for data
signals TPCMI, TSIGI, TINDO and sync signa ls TFS YNC
and TMSYNC (see [TPCM_NEG and TSYN_ NEG;
addr 0D4]). When configured to operate at twice the data
rate, TSB clock is internally divided by 2 before clocking
TSB data signals.
ISerial data formatted into TSB frames consisting of DS0
channel time slots and optional F- bits. One group of 24
T1 time slots or 32 E1 time slots is selected from up to
four available groups; data from the group is sampled by
TSBCKI, then sent towards transmitter output. Time
slots are routed through transmit slip buffer (see
[TSLIPn; addr 140–17F]) according to TSLIP mode (see
[TSBI; addr 0D4]). F-bits are taken from the start of each
TSB frame or from within an embedded time slot (see
[EMBED; addr 0D0]) and optionally inserted into the
transmitter output (see [TFRM; addr 072] register).
ISerial data formatted in to TSB frames containing ABCD
signaling bits for each system bus time slot. Four bits of
TSIGI time slot carry signaling state for each
accompanying TPCMI time slot. Signalin g state of every
time slot is sampled during first frame of the TSB
multiframe and then transferred into transmit signaling
buffer [TSIGn; addr 120–13F].
OActive-high output pulse marks selective transmit
system bus time slots as programmed by SBCn [addr
0E0-0FF], TINDO occurs on TSBCKI rising or falling
edges as selected by TPCM_NEG (see [TSBI; addr 0D4]).
PIOInput or output TSB frame sync (see [TFSYNC_IO; addr
018]). TFSYNC output is active high for one TSB clock
cycle at programmed offset bit location (see
[TSYNC_BIT; addr 0D5]), marki ng offset bit position
within each TSB frame and repeating once every 125 µs.
When transmit framer is also enabled, TSB timebase and
TFSYNC output frame alignment are establ ished by
transmit framer's examination of TPCMI serial data
input. When TFSYNC is programmed as an input, the
low-to-high signal transit ion is detected and is used to
align TSB timeba se to programmed offse t bit value. TSB
timebase flywheels at 125 µs frame interval after the last
TFSYNC is applied.
PIOInput or output TSB multifram e syn c (s e e [T MSYNC_IO;
addr 018]). TMSYNC output is active high for one TSB
clock cycle at programmed offset bit location (see
[TSYNC_BIT; addr 0D5]), marki ng offset bit position
within each TSB multiframe and repeating once every 6
ms coincident with TFSYNC. When transmit framer is
also enabled, TSB timebase and TMSYNC output
multiframe alignment are established by transmit
framer's examination of TPCMI serial data input. When
TMSYNC is programmed as an input, the low-to-high
signal transition is detected and is used to align TSB
timebase to programmed offset bit value and first frame
of the multiframe. TS B t imebase flywheels at 6 ms
multiframe inter vals after the last TMSYNC is applied. If
system bus applies TMSYNC input, TFSYNC input is not
needed.
IBit clock and I/O signal timing for RSB according to
system bus mode (see [SBI_CR; ad dr 0D0]). System
chooses from one of two different clocks to act as RSB
clock source (see [CMUX; addr 01A]). Rising or falling
edge clocks are independently configurable for data
signals RPCMO, RSIGO, RINDO and sync signals
RFSYNC, RMSYNC (see [RPCM_NEG and RSYN_NEG;
addr 0D1]). When con figu red to oper ate at twic e th e dat a
rate, RSB clock is inte r n al ly div ided by 2 before clocking
RSB data signals.
RSB Time Slot
Indicator
Bused RSB Time
Slot Indicator
4
8
5
4,5,8
5,8
5
5
4
8
4,5,8
5,8
5
5
OSerial data formatte d in to RSB frames consistin g of DS0
channel time slots , op tional F-bits and op tio n al AB CD
signaling. Time slots are routed through receive slip
buffer (see [RSLIPn; addr 1C0–1FF]) according to RSLIP
mode (see [RSBI; addr 0D1]). Data for each ou tp ut time
slot is assigned sequentially from received time slot data
according to system bus channel programming (see
[ASSIGN; addr 0E0–0FF]). F-bits are output at the start
of each RSB frame or at the embedded time slot location
(see [EMBED; addr 0D0]). ABCD signaling is optionally
inserted on a per-channel basis (see [INSERT;
addr 0 E0–0FF]) from the local signaling buffer (see
[RLOCAL; addr 180–19F]) or from the receive signal ing
buffer [RSIGn; addr 1A0–1BF]. When enabl ed, robbed
bit signaling or CAS reinsertion is performed according
to T1/E1 mode: The eighth time slot bit of every sixth T1
frame is replaced, or the 4-bit signaling value in the E 1
time slot 16 is replaced.
OActive high output pulse marks selective receive system
bus time slots as programmed by SBCn [addr 0E0-0FF].
RINDO occurs on RSBCKI rising or falling edges as
selected by RPCM_NEG (see [RSBI; addr 0D1]). On ly
available in Mul tiplexed System Bu s mode on CX28395
(see [FCR; addr 080]).
OSerial data formatted into RSB frames consisting of
ABCD signaling bits for each system bus time slot. Four
bits of RSIGO time slot carry signaling state for ea ch
accompanying RPCMO time slot. Local or through
signaling bits are output in every frame for each time slot
and updated once per RSB multiframe, regardless of
per-channel RPCMO signaling reinsertion.
PIOInput or output RSB frame sync (see [RFSYNC_IO;
addr 018]). RFSYNC output is active high for one RSB
clock cycle at programmed offset bit location (see
[RSYNC_BIT; addr 0D2]), markin g offset bit within each
RSB frame and repeating once every 125 µs. RSB
timebase and RFSYNC output frame alignment begins at
an arbitrary posi tion and ch anges alig nment acc ording to
RSLIP mode (see [RSBI; addr 0D1]). When RFSYNC is
programmed as an inpu t, the low-to-high signal
transition is detected and used to align R SB timebase to
the programmed offset. RSB timebase flywheels at
125 µs frame interval after the last RFSYNC is applied.
1.2 Pin Assignments
RMSYNC[4:1]
RMSYNC[8:1]
RMSYNC[16:1]
SIGFRZ[4:1]
SIGFRZ[8:1]
RSB Multiframe
Sync
Signaling Freeze4
4
8
5
8
PIOInput or output RSB multifr ame sync (s ee [RMS YNC_IO ;
addr 018]). RMSYNC output is active high for one RSB
clock cycle at programmed offset bit location (see
[RSYNC_BIT; addr 0D2]), marking offset bit within each
RSB multiframe and repeating once every 6 ms
coincident with RFSYNC. RSB timebase and RMSYNC
output multiframe alignment begins at an arbit rary
position and changes alignment according to RSLIP
mode (see [RSBI; addr 0D1]). When RMSYNC is
programmed as an inpu t, the low-to-high signal
transition is detected and is used to align the RSB
timebase to programmed offset and first frame of the
multiframe. RSB timebase flywheels at 6 ms multiframe
interval after the last RMSYNC is applied.
OActive high indicates that signaling bit updates are
suspended for both receive signaling buffer [RSIGn;
addr 1 A0 –1BF] and stack [STACK; addr 0DA] register.
SIGFRZ is clocked by RSB clock, goes high coincident
with receive loss of frame al ignment (see RLOF;
addr 047) and returns low 6–9 ms after recovery of
frame alignment.
TCKJTAG Clock4, 5, 8IClock input samples TDI on rising edge and outputs TDO
(1)
Joint Test Access Group (JTAG)
I/ODefinition
on falling edge.
TDI1, TDI2JTAG Test Data
Input
TDIJTAG Test Data
Input
TMSJTAG Test mode
Select
TDOJTAG Test Data
Output
TDO1, TDO2JTAG Test Data
Output
5ITest data input per IEE E Std 11 49 .1 - 19 90 . Us ed for
loading all serial in structions and data into inte rn al tes t
logic. Sampled on the rising edge of TCK. TDI can be left
unconnected if it is not being used because it is pulled up
internally. TDI1 is the test data input for framers 1 to 8,
TDI2 is the test data input for framers 9 to 16.
4, 8ITest data input per IEEE Std 1149.1-1990. Used for
loading all serial in structions and data into inte rn al tes t
logic. Sampled on the rising edge of TCK. TDI can be left
unconnected if it is not being used because it is pulled up
internally.
4, 5, 8IActive low t est mode select input per IEEE Std
1149.1-1990. Internally pulled-up input signal used to
control the test-logic state machine. Sampled on the
rising edge of TCK. TMS can be left unconnected if it is
not being used because it is pulled up internally.
4, 8O Test data output per IEEE Std 1149.1-1990 . TDO is a
three-state output used for reading all serial
configuration an d test data from internal test logic.
Updated on the falling edge of TCK.
5OTest data output per IEEE Std, 1149.1-1990. TD O is a
three-state output used for reading all serial
configuration an d test data from internal test logic.
Updated on the falling edge of TCK. TDO1 is the test data
output for framers1 to 8, TDO2 is the test da ta output for
framers 9 to 16.
TRST*JTAG Reset4, 5, 8IActive low input to initialize Tap Controller.
4, 5, 8I+3.3 Vdc ±5%. Connect to +5 Vdc ±5% to ensure 5 V
tolerance in applica t io ns whic h inc lu de 5 V logi c dri vi ng
signals.
1-38Conexant100054E
Page 57
CX28394/28395/283981.0 Product Description
Quad/x16/Octal—T1/E1/J1 Framers
1.2 Pin Assignments
Table 1-6. Hardware Signal Definitions (9 of 9)
Pin LabelSignal NameDevice
TSTO[16:1]Test Output5OTest output. Leave disconnected for normal operation.
TSTI[16:1]Test Input5ITest input. Connect through 50k ohm pull-up resistor to
NOTE(S):
(1)
4 = CX28394
5 = CX28395
8 = CX28398
1. A ll RSB and TSB outputs can be placed in high-impedance state (see SBI_OE; addr 0D0).
2. I = Input, O = Output
3. PIO = Programmable I/O; control s located at address 018.
4. Multiple signal names show mutually exclusive p in functions.
Figures 2-1 and 2-2 illustrate detailed framer b lock di agrams for non-mult iple x ed
and multiplexed system bus modes. To show the details of these circuits,
individual b lock diagrams of the functions listed bel o w have been created and are
placed, along with descriptions, throughout this section:
•Receiver (RCVR)
•Receive System Bus (RSB)
•Transmit System Bus (TSB)
•Transmitter (XMTR)
•Microprocessor Interface (MPU)
•Joint Test Access Group Port (JTAG)
•Serial Port (SERIO)
100054EConexant2-1
Page 60
2.0 Circuit DescriptionCX28394/28395/28398
2.1 Functional Block D iag r a mQuad/x16/Octal—T1/E1/J1 Framers
Figure 2-1. Detailed Framer Block Diagram (Multiplexed System Bus Mode)
MCLK
MOTO*
SYNCMD
SYSCKI
CS*
AS*
DS*
R/W*
DTACK*
AD[7:0]
A[11:0]
INTR*
ONESEC
RST*
SERCS[1:0]
SERCLK
SERDO
SERI
TCK
TMS
TDI
TDO
TRST*
Microprocessor PortJTAG Port
(1)
Serial Port
RNRZI[1]
(1)
RPOSI[1]
(1)
RNEGI[1]
RCKI[1]
TCKO[1]
(1)
TPOSO[1]
(1)
TNEGO[1]
TNRZO[1]
MSYNCO [1]
Decoder
Line Loopback
TZCS
Encoder
RZCS
Framer Loopback
PDV Enforcer
RDLCKO[1]RDLO[1]
(1)(1)
External DLINK
PRBS/Inband LB
DLINK2 Buffer
DLINK1 Buffer
Sa-Byte/BOP
PDV Mo nitor
Error Counters
Alarm Monitor
Receiver Framer
Receive
Timebase
Transmitter
Timebase
Alarm/Error Insert
PRBS Inband LB
DLINK1 Buffer
DLINK2 Buffer
Sa-Byte/BOP
(1)
TDLI[1]
TDLCKO[1]
RSIG
Buffer
RSIG
Local
RSLIP
Buffer
AIS
RPHASE
Clock
Monitor
TPHASE
T1/E1 Frame Insert
External Dlink
TSLIP
Buffer
TSIG
Buffer
TSIG
(1)
Buffer
Remote Loopback
RSIG
Stack
RSIGO[1]
Per-Channel
Per-Channel
Local Loopback
RSB
Timebase
TSB
Timebase
Transmit
Framer
RPCMO[A]
SIGFRZ[1]
RINDO[A]
RFSYNC[A]
RMSYNC[1]
RSBCKI[A]
TCKI
E1ACKI
TIACKI
TSBCKI[A]
TFSYNC[A]
TMSYNC[1]
TINDO[A]
TPCMI[A]
TSIGI[1]
FRAMER 1
FRAMER 2
8394-8-5_001
NOTE(S):
(1)
Not available on CX 28395.
2-2Conexant100054E
Page 61
CX28394/28395/283982.0 Circuit Description
Quad/x16/Octal—T1/E1/J1 Framers
Figure 2-2. Detailed Framer Block Diagram (Non-multiplexed System Bus Mode)
MCLK
MOTO*
SYNCMD
SYSCKI
CS*
AS*
DS*
R/W*
DTACK*
AD[7:0]
A[11:0]
INTR*
ONESEC
RST*
SERCS[1:0]
SERCLK
SERDO
SERI
TCK
TMS
TDI
TDO
TRST*
Microprocessor PortJTAG Port
(1)
Serial Port
RNRZI[1]
(1)
RPOSI[1]
(1)
RNEGI[1]
RCKI[1]
TCKO[1]
(1)
TPOSO[1]
(1)
TNEGO[1]
TNRZO[1]
MSYNCO [1]
Decoder
Line Loopback
TZCS
Encoder
RZCS
Framer Loopback
PDV Enforcer
RDLCKO[1]RDLO[1]
(1)
External DLINK
PRBS/Inband LB
DLINK2 Buffer
DLINK1 Buffer
Sa-Byte/BOP
PDV Mo nitor
Error Counters
Alarm Monitor
Receiver Framer
Receive
Timebase
Transmitter
Timebase
Alarm/Error Insert
PRBS Inband LB
DLINK1 Buffer
DLINK2 Buffer
Sa-Byte/BOP
(1)
TDLI[1]
TDLCKO[1]
(1)
RSIG
Buffer
RSIG
Local
RSLIP
Buffer
AIS
RPHASE
Clock
Monitor
TPHASE
T1/E1 Frame Insert
External Dlink
TSLIP
Buffer
TSIG
Buffer
TSIG
(1)
Buffer
2.1 Functional Block Diagram
RSIG
Stack
RSIGO[1]
Per-Channel
Remote Loopback
Per-Channel
Local Loopback
RSB
Timebase
TSB
Timebase
Transmit
Framer
RPCMO[1]
SIGFRZ[1]
RINDO[1]
RFSYNC[1]
RMSYNC[1]
RSBCKI[1]
TCKI[1]
E1ACKI
TIACKI
TSBCKI[1]
TFSYNC[1]
TMSYNC[1]
TINDO[1]
TPCMI[1]
TSIGI[1]
FRAMER 1
FRAMER N
8394-8-5_001a
NOTE(S):
(1)
Not available on CX 28395.
100054EConexant2-3
Page 62
2.0 Circuit DescriptionCX28394/28395/28398
2.2 ReceiverQuad/x16/Octal—T1/E1/J1 Framers
2.2 Receiver
The Receiver (RCVR) inputs single rail NRZ data or decodes positive and
negative rail NRZ data into single rail NRZ da ta. The RCVR, illustrated in
Figure 2-3, consists of the following elements: Receive Zero Code Suppression
(RZCS) Decoder, In-Band Loopback Code Detector, Error Counters, Error
Monitor, Alarm Monitor, Test Pattern Receiver, Receive Framer, External
Receive Data Link, and Receive Data Links.
Figure 2-3. RCVR Diagram
MPU
Registers
RDLO
RDLCKO
RNRZI
RPOSI
RNEGI
Line
Loopback
2.2.1 ZCS Decoder
RZCS
Decoder
Loopback
Framer
External DLINK
PRBS/Inband LB
Sa-Byte
RPDV Monitor
Error Monitor
Error Counters
Alarm M onitor
Receive Framer
Receiver Timebase
RCKI
DLINK1
MOP/BOP
To RSB
DLINK2
MOP
RNRZ
The Receive Zero Code Suppression (RZCS) decoder is applicable only to the
CX28394 and CX28398. The decoder decodes the dual rail data (bipolar) into
single rail data (unipolar). The Receive AMI bit (RAMI) in the Receiver
Configuration register [RCR0; addr 040] controls whether the received signal is
B8ZS/HDB3 decoded, depending on T1/E1N [addr 001] line rate selection, or if
the RZCS decoder is bypassed. If the line code is unknown, the ZCSUB bit in
Receive Line Code Status [RSTAT; addr 021] indicates the RPOSI/RNEGI input
received one or more B8ZS/HDB3 substitution patterns. If the line code is
B8ZS/HDB3-encoded, the RZCS bit in RCR0 should be set to keep the LCV
counter from counting BPVs that are part of the B8ZS/HDB3 code.
2-4Conexant100054E
Page 63
CX28394/28395/283982.0 Circuit Description
Quad/x16/Octal—T1/E1/J1 Framers
2.2.2 In-Band Loopback Code Detection
The in-band loopback code detector circuitry detects receive data with in-band
codes of configurable value and length. These codes can be used to request
loopback of terminal equipment signals or other user specified applications. The
two codes are referred to as loopback-activate and loopback-deactivate, although
the detectors need not be used only for loopback codes. Generally, any repeating
1–7 bit pattern can be selected. The loopback application is described in Section
9.3.1 of ANSI T1.403-1995. The loopback activate code is set in the Loopback
Activat e Code P attern [LB A; addr 043 ]. The loo pback deact iv ate c ode is set in the
Loopback Deactivate Code Pattern [LBD; addr 044].
The sequence length for the loopback activate and deactivate codes can be
programmed for 4, 5, 6, or 7 bits by setting the code length bits of the Receive
Loopback Code Detector Configuration register [RLB; addr 042]. Shorter codes
can be programmed by repeating the expected pattern (e.g. 3+3 bit code
programmed as 6-bit code).
T1 In-Band Loopback Codes
Activate 00001
Deactivate 001
When a loopback code is detected, the LOOPUP or LOOPDN status bit is set
in Alarm 2 register [ALM2; addr 048], and the corresponding LOOPUP or
LOOPDN bit in Alarm 2 Interrupt Status register (ISR6; addr 005] is set. The
loopback detection interrupt can be enabled using the Alarm 2 Interrupt Enable
register [IER6; add r 0 0D]. When enabled, a loop-up or loop-down code det ecti on
causes the Alarm 2 Interrupt bit [ALARM2] to be set in the Interrupt Request
register [IRR; addr 003] and generates an interrupt. Since loopbacks are not
automatically initiated, the processor must intercept and interpret the inter rupt
status condition to determine when it must enable or disable the loopback control
mechanism (e.g., LLOOP; addr 014).
2.2 Receiver
2.2.3 Error Counters
The following P e rformance Monitoring (PM) count ers are a vailable in the RCVR:
•Framing Bit Errors (FERR)
•CRC Errors (CERR)
•Line Code Vi olations (LCV)
•Far End Block Errors (FEBE)
All PM count registers are reset on read unless LATCH_CNT is set in the
Alarm/Error/Counter Latch Configuration register [LATCH; addr 046].
LATCH_CNT enables the one-second latching of counts coincident with the
one-second timer interrupt [ISR6; addr 005]. One-second latching of PM counts
is required if AUTO_PRM responses are enabled. All PM counters can be
disabled during RLOF, RLOS, and RAIS, using the STOP_CNT bit in the
LATCH register.
Note that if ST OP_CNT is ne gat ed, error monitoring during RLOF conditions
will detect FERR, CERR, and FEBE according to the last known frame
alignment.
100054EConexant2-5
Page 64
2.0 Circuit DescriptionCX28394/28395/28398
2.2 ReceiverQuad/x16/Octal—T1/E1/J1 Framers
2.2.3.1 Frame Bit Error
Counter
2.2.3.2 CRC Error
Counter
2.2.3.3 LCV Error
Counter
2.2.3.4 FEBE CounterThe 10-bit Far End Block Error (FEBE) counter [FEBE; addr 056 and 057]
The 12-bit Framing Bit Error Counter [FERR; addr 050 and 051] increments
every time a receive Ft, Fs, T1DM, FPS, or FAS error is detected. Fs (T1) and
NFAS (E1) errors can be included in the FERR count by setting FS_NFAS in
Receive Alarm Signal Configuration [RALM; addr 045]. An interrupt is a vai lable
to indicate that the FERR counter overflowed in the Counter Overflow Interrupt
Status register [ISR4; addr 007].
The 10-bit Cyclic Redundancy Check Error Counter [CERR; addr 052 and 053]
increments each time a receive CRC4 (E1) or CRC6 (T1) error is detected. An
interrupt is available to indicate that CERR counter overflowed in ISR4.
The 16-bit Line Code Violation Error Counter [LCV; addr 054 and 055]
increments each time a receive Bipolar Violation (BPV)—not including line
coding—is detected. The LCV count can include EXZ if EXZ_LCV in the
Receive Alarm Signal Configuration register [RALM; addr 045] is set. EXZ can
be configured [RZCS; addr 040] to be 8 or 16 successive zeros, following a one.
An interrupt is available to indicate that the LCV counter overflowed in ISR4.
increments every time the RCVR encounters an E1 far-end block error. An
interrupt is available to indicate that the FEBE counter overflowed in ISR4.
2.2.4 Error Monitor
The following signal errors are detected in the RCVR:
•Frame Bit Error (FERR)
•MFAS Error (MERR)
•CAS Error (SERR)
•CRC Error (CERR)
•Pulse Density Violation (PDV)
Each error type has an interrupt enable bit that enables an interrupt to occur
marking the event, an d an interrupt register bit that is read by th e interrupt service
routine to determine which event caused the interrupt. All error status registers
are reset on read unless the LATCH_ERR bit is set in the Alarm/Error/Counter
Latch Configuration register [LATCH; addr 046]. LATCH_ERR enables the
one-second latching of alarms coincident with the one-second timer interrupt
[ISR6; addr 005]. With LATCH_ERR enabled, any error detected during the one
second interval is latched and held during the following one-second interval.
LATCH_ERR allows the processor to gather error statistics based on the
one-second interval.
2.2.4.1 Frame Bit ErrorFERR is reported for the receive direction in the Error Interrupt Status register
[ISR5; addr 006] and for the transmit direction in Pattern Interrupt Status
[ISR0; addr 00B]. FERR indicates that one or more Ft/Fs/FPS frame-bit errors or
FAS-pattern errors occurred since the last time the interrupt status was read. The
FERR type is determined by the recei v e framer’s configuration [CR0; address 001].
2-6Conexant100054E
Page 65
CX28394/28395/283982.0 Circuit Description
Quad/x16/Octal—T1/E1/J1 Framers
2.2.4.2 MFAS ErrorWhen CRC4 framing is enabled , MERR is reported for the recei ve direction in the
Error Interrupt Status register [ISR5; addr 006] and for the transmit direction in
Pattern Interrupt Status [ISR0; addr 00B]. MERR is applicable only in E1 mode,
and indicates that one or more MFAS pattern errors occurred since the interrupt
status was last read.
2.2.4.3 CAS ErrorWhen CAS framing is enabled, SERR is reported for the receive direction in the
Error Interrupt Status register [ISR5; addr 006] and for the transmit direction in
Pattern Interrupt Status [ISR0; addr 00B]. SERR is only applicable in E1 mode,
and indicates that one or more errors were received in the TS16 Multiframe
Alignment Signal (MAS) since the interrupt status was last read.
2.2.4.4 CRC ErrorCERR is reported for the receive direction in the Error Interrupt Status register
[ISR5; addr 006] and for the transmit direction in Pattern Interrupt Status
[ISR0; addr 00B]. CERR is only applicable in T1 ESF and E 1 MFAS modes, and
indicates that one or more bit errors we re found in the CRC4/CRC6 patt ern block
since the interrupt status was last read.
2.2.4.5 Pulse Density
Violation
PDV is reported when the receive signal does not meet the pulse density
requirements of ANSI T1.403-1995 ( Secti on 5.6) . A PDV is declared when more
than 15 consecuti ve z eros or the average ones density falls below 12.5 %. RPDV is
reported for the receive direction in the Alarm 1 Interrupt Status register
[ISR7; addr 004].
2.2 Receiver
2.2.5 Alarm Monitor
The following signal alarms are detected in the RCVR:
•Loss Of Frame (LOF)
•Loss Of Signal (LOS)
•Receive Analog Loss Of Signal (RALOS)
•Alarm Indication Signal (AIS)
•Remote Alarm Indication (RAI) or Yellow Alarm (YEL)
•Multiframe Yellow Alarm (MYEL)
•Severely Errored Frame (SEF)
•Change Of Frame Alignment (COFA)
•Multiframe AIS (MAIS)
Each alarm has the following: a status register bit that reports the real-time
status of the event; an interrupt enable bit that enables an interrupt to mark the
event; and an interrupt regist er bi t r ead by th e i nt errupt service routi ne to identify
the event that caused the interrupt. All alarm status registers are reset on read
unless the LATCH_ALM bit is set in the Alarm/Error/Counter Latch
Configuration register [LATCH; addr 046]. LATCH_ALM enables the
one-second latching of alarms coincident with the one-second timer interrupt
[ISR6; addr 005]. With LATCH_ALM enabled, any alarm detected during the
one-second interval is latched and held during the following one-second interval.
100054EConexant2-7
Page 66
2.0 Circuit DescriptionCX28394/28395/28398
2.2 ReceiverQuad/x16/Octal—T1/E1/J1 Framers
2.2.5.1 Loss of FrameReceive Loss Of Frame (RLOF) is declared w hen the re ceiv e data stream does not
meet the framing criteria specified in the Receiver Configuration register
[RCR0; addr 040].
If the line rate is E1 [T1/E1N; addr 001], RLOF is the logically OR'ed status
of FAS, MFAS, and CAS alignment. These alignments, FRED, MRED and
SRED, respectively, are available separately in the Alarm 3 Status register
[ALM3; addr 049]. Once RLOF is declared the LOF[1:0] bits in ALM3 report the
reason for E1 loss of frame alignment. In T1 mode, RLOF is equal to FRED.
The RLOF real-time status is available in Alarm 1 Status register
[ALM1; addr 047], and the interrupt status is set in th e Alarm 1 Interrupt St at us
register [ISR7; addr 004]. The RLOF interrupt is enabled by setting RLOF in the
Alarm 1 Interrupt Enable register [IER7; addr 00C].
An FRED count [FRED[3:0 ] ; a ddr 05A] is also available in the
SEF/LOF/COFA Alarm Counter [AERR; addr 05A]. An interrupt in Counter
Overflow Interrupt Status [ISR4; addr 007] indicates that the FRED counter
overflowed.
While T1 framing mode is enabled, the RLOF status and RLOF interrupt
status are integrated over 2.0 to 2.5 seconds if the RLOF_INTEG bit is set in the
Receive Alarm Signal Configuration register [RALM; addr 045]. The FRED
count is unaffected by RLOF_INTEG.
2.2.5.2 Loss of SignalIf the line rate is T1, the criteria for Receive Loss Of Signal (RLOS) is 100
contiguous zeros (consistent with the standard requirement of 175
±75 zeros). If
the line rate is E1, the criteria for RLOS is 32 contiguous zeros. RLOS is cleared
upon detecting an average pulse density of at least 12.5% (occurring during a
period of 175
± 75 bits starting with the receipt of a pulse, and where no
occurrences of 100/32 contiguous zeros are detect ed). The RLOS rea l-time status
is available in ALM1, and the interrupt is available in ISR7. The XMTR can be
configured to automatically generate an Alarm Indication Signal (AIS) in the
transmit direction when RLOS is declared (see AUTO_AIS [TALM; addr 075]).
2.2.5.3 Receive Analog
Loss of Signal
RALOS [ALM1; addr 047] can be configured to report loss of receive clock
(RCKI) or loss of receive signal [RLOS; addr 047] for 1 msec depending on the
RALOS configuration bit [RAL_CON; addr 020]. RALOS status is provided for
compatibility with ANSI T1. 431 loss of signa l det ection requir ements; and works
in conjunction with LIUs which detect loss of signal if the received signal level
falls below a certain threshold and which have a signal ‘squelch’ feature. If
RAL_CON is set for loss of signal, RALOS indicates that all zeros have been
received for at least 1 msec (RLOS is active for 1 msec). If RAL_CON is set for
loss of clock, RALOS becomes active (1) if the receive clock on the RCKI pin is
not present, and inactive (0) if the clock is present.
2.2.5.4 Alarm
Indication Signal
If the line rate is T1 [T1/E1N; addr 001], th e criteria for Recei v e Alarm Indicati on
Signal (RAIS) is the reception of four or fewer zeros in a period of 3 ms (4632
bits) and assertion of RLOF. If the line rate is E1, RAIS is set if two consecutive
double frames e ach cont ai n two or fewer zeros out o f 512 bits and FAS alignment
is lost [FRED; addr 049]. The RAIS real-time status is available in ALM1. The
RAIS interrupt is available in ISR7.
2.2.5.5 Yellow AlarmThe criteria for Yellow Alarm (YEL) is described in Table 3-13, Receive Yellow
Alarm Set/Clear Criteria. YEL real-time status is available in ALM1; YEL
interrupt is available in ISR7.
2-8Conexant100054E
Page 67
CX28394/28395/283982.0 Circuit Description
Quad/x16/Octal—T1/E1/J1 Framers
2.2.5.6 Multiframe YELThe criteria for M ultiframe Yellow Alarm is described in Table3-13, Receive
Yellow Alarm Set/Clear Criteria. The MYEL real-time status is available in
ALM1, and the interrupt is available in ISR7.
2.2.5.7 Severely Errored
Frame
2.2.5.8 Change of
Frame
Alignment
2.2.5.9 Receive
Multiframe AIS
A SEF is reported when the receive signal does not meet the requirements of
ANSI T1.231. SEF real-time status is available in ALM3. A 2-bit counter is also
available [SEF; addr 05A]. An interrupt is available in ISR4 to indicate that the
SEF counter ov er f lowed.
Each COFA increments a 2-bit counter [COFA; addr 05A]. An interrupt is
available in ISR4 to indicate that the COFA counter overflowed.
Receive Multiframe AIS (RMAIS) is reported when the receive TS16 signal
contains three or fewer zeros out of 128 bits in each multiframe over two
consecutive multiframes, according to the requirements of ITU–T
Recommendation G.775. RMAIS is only checked in E1 CAS mode. RMAIS
real-time status is available in ALM3 [addr 049].
2.2 Receiver
2.2.6 Test Pattern Receiver
The test pattern receiver circuitry can sync on framed or unframed PRBS patterns
and count bit errors. This feature is particularly useful for system diagnostics,
production testing, and test equipment appl icat ions. The PRBS patterns avai l able
include 2E11-1, 2E15- 1, 2E20-1, and 2E23 -1. Each pattern can op tionall y include
Zero Code Suppression (ZCS).
The Receive Test Pattern Configuration register [RPATT; addr 041] controls
the test pattern re ceiver circuit. The BSTART control bit (in RPATT) must be
active to enable the test pattern receiver and to begin counting bit errors. RPATT
controls the PRBS patte rn, ZCS setting (Z LIMIT), and T1/E1 framing
(FRAMED). RPATT selects which PRBS pattern the receiver should hunt for
pattern sync. ZLIMIT selects the maximum number of consecutive zeros the
pattern is allowed to contain. FRAMED mode informs the PRBS pattern receiver
not to search for the pattern in the frame bit in T1 mode or search for the pattern
in time slot 0 (and time slot 16 if CAS framing is selected) in E1 mode. CAS
framing is selected by setting RFRAME[3] to 1 in the Primary Control register
[CR0; addr 001]. If FRAMED is disabled, the PRBS pattern receiver searches all
time slots for the test pattern.
The RESEED bit in RPATT informs the receive PRBS sync circuit to begin a
PRBS pattern search. Once the search begins, any additional writes to RESEED
restarts the pattern sync search at a differen t point in th e pattern. The time to sy nc
depends on the pattern and number of bit errors in the pattern.
Pattern sync is reported (when found) in PSYNC status of the Pattern
Interrupt Status register [ISR0; addr 00B]. Next, the PRBS Pattern Error counter
[BERR; addr 058 and 059] counts bit errors detected on the incoming pattern,
provided that BSTART remains active. Error counting stops if th e BSTART bi t i s
cleared. The BERR counter is reset to zero after every read, or latched on every
ONESEC inter rupt as selected by LATCH_CNT [addr 046]. An interrupt is
available to indicate the BERR counter overflowed in ISR4.
100054EConexant2-9
Page 68
2.0 Circuit DescriptionCX28394/28395/28398
2.2 ReceiverQuad/x16/Octal—T1/E1/J1 Framers
2.2.7 Receive Framing
Two framers are in the receive data stream: an offline framer and an online frame
status monitor. The offline framer recovers receive frame alignment; the online
framer monitors frame alignment patterns and recovers multiframe alignment in
E1 modes. Table 2-1 lists supported RCVR framing modes. Frame and
multiframe synchronization criteria used by the framers, as well as the monitoring
criteria of the online framer, are selected in RFRAME[3:0] of the Primary
Control register [CR0; addr 001]. Table 2-2 details framing loss/recovery criteria.
Receive frame synchronizati on is initi ated by the online framer’s activ at ion of
the Receive Loss Of Frame (RLOF) status bit in the Alarm 1 Status register
[ALM1; addr 047]. The RLOF criteria is set in the RLOFA, RLOFB, RLOFC,
and RLOFD bits of the Receiver Configuration register [RCR01; addr 040]. The
online framer supports the following LOF criteria for T1: 2 out of 4, 2 out of 5,
and 2 out of 6. For E1, the online framer supports 3 out of 3, with or without 915
out of 1000 CRC errors.
When RLOF is asserted, the offline framer automatically starts searching the
receive data stream for a new frame alignment, provided that receive framing is
enabled [RABORT; addr 040]. If receive framing is disabled, the offline framer
does not automatically sear ch for the frame alignment, but waits for a reframe
command [RFORCE; addr 040] to start a frame alignment search. If RLOF
integration is enabled [RLOF_INTEG; addr 045] the RLOF status [ALM1; addr
047] and RLOF interrupt status [ISR7; addr 004] is integrated for 2.0 to 2.5
seconds.
The online framer continuously monitors for loss of frame (RLOF) condition
[ALM1; addr 047] and searches for E1 multiframe alignment after basic frame
alignment is recovered by the offline framer. Receive multiframe alignment is
declared when multiframe alignment criteria are met. The receive online framer
reports multiframe errors, as well as frame errors and CRC errors in the Error
Interrupt Status [ISR5; addr 006].
The offline framer is shared between the RCVR and XMTR and can search
only in one direction at any time. Consequently, the processor arbitrates which
direction is searched by enabling the reframe request (RLOF and TLOF) for that
direction.
2-10Conexant100054E
Page 69
CX28394/28395/283982.0 Circuit Description
Quad/x16/Octal—T1/E1/J1 Framers
Table 2-1. Receive Framer Modes
2.2 Receiver
T1/E1NRFRAME[3:0]Receive Framer Mode
0000XFAS Only
0001XFAS Only + BSLIP
0010XFAS + CRC
0011XFAS + CRC + BSLIP
0100XFAS + CAS
0101XFAS + CAS + BSLIP
0110XFAS + CRC + CAS
0111XFAS + CRC + CAS + BSLIP
10000FT Only
10001ESF + No CRC (FPS on ly )
10100SF
10101SF + JYEL
10110SF + T1DM
11000SLC + FSLOF
11001SLC
11100ES F + Mimic CRC
11101ES F + Force CRC
100054EConexant2-11
Page 70
2.0 Circuit DescriptionCX28394/28395/28398
2.2 ReceiverQuad/x16/Octal—T1/E1/J1 Framers
Table 2-2. Criteria for Loss/Recovery of Receive Framer Alignment
ModeDescription
FASBasic Frame Alignment (BFA) is recovered when the following search criteria are satisfied:
•FAS pattern (0011011) is found in frame N.
•Frame N+1 contains bit 2 equal to 1.
•Fra me N+2 also contains FAS pattern (0011011).
During FAS-only modes, BFA is recovered when the followin g search cr iteria are satisfied:
•FAS pattern (0011011) is found in frame N.
•No mi mics of the FAS pattern are present in frame N+1.
•FAS pattern (0011011) is found in frame N+2.
NOTE(S): If FAS pattern is not found in frame N+2, or if FAS mimic is found in frame N+1, the search restarts in
frame N+2.
Loss of FAS frame alignment (FRED) is d eclared when one of the following criteria is met:
•Three consecutive FAS pattern errors are detected when the FAS pattern consists of a 7-bit (x0011011)
pattern in FAS frames and—if FS_NFAS is also active [addr 045]—the FAS pattern includes bit 2 of
NFAS frames.
•Loss of MFAS (MRED) is due to 915 or more CRC errors out of 1000.
•Failure to locate two valid MFAS patterns within 8 ms after BFA.
NOTE(S): In all cases, FRED causes next search for FAS alignment to begin 1 bit after the current FAS location.
BSLIPFAS Bit Slip Enable. Applicable only for Dutch PTT national applicati ons. If BSLIP is enabled, the online framer
is allowed to change RX timebase by
±1 bit when a 1-bit FAS pa ttern slip is de tected . BSLIP does not affect the
offline framer's search crit eria.
MFASCRC4 Multiframe Alignment is recovered when the following search criteria are satisfied:
•BFA is recovered, identifying FAS and NFAS frames.
•Within 8 ms after BFA, bit 1 of NFAS frames contai ns two MFAS patterns (001011xx). The second
MFAS must be aligned with respect to first MFAS, but the second MFAS pattern is not necessarily
received in consecutive frames.
•Within 8 ms after BFA, bit 1 of NFAS frames contains the second MFAS pattern (001011xx), aligned to
first MFAS.
Loss of MFAS alignment (MRED) declared when one of the followin g criteria is met:
•91 5 or more CRC4 errors out of 1000 (submultiframe) blocks.
•Loss of FAS (FRED).
NOTE(S): If Disable 915 CRC Reframe is set [RLOFD; addr 040], then MRED is activated only by FRED.
CASCAS Multiframe Alignment is recovered when the following search criteria are satisfied:
•BFA is recovered, identifying TS0 through TS31.
•MA S ( 0000xxxx) multifr a me alignment signal pattern is found in the first 4 bits of TS16, and 8 bits of
TS16 in preceding frame contains nonzero value.
Loss of CAS alignment (S RED) is declared when one of th e following criteria is met:
•Two consecutive MAS pattern errors are det ected.
•TS16 contains all zeros in two multif rames (32 consecutive frames).
•Loss of FAS (FRED).
FT OnlyTerminal frame alignment is recovered when:
The first valid Ft pattern (1010) is found in 12 alternate F-bit locations (3 ms), where F-bits are separated by
193 bits.
During Ft-only mode, loss of frame alignment (FRED) is declare d when:
Number of Ft bit errors detected meets selected loss of frame criteria [RLOFA–RLOFC; addr 04 0].
2-12Conexant100054E
Page 71
CX28394/28395/283982.0 Circuit Description
Quad/x16/Octal—T1/E1/J1 Framers
2.2 Receiver
Table 2-2. Criteria for Loss/Recovery of Receive Framer Alignment
ModeDescription
SFSuperframe alignment is recovered when:
•Terminal frame alignment is recovered, identifying Ft bits.
•Depends on SF submode:
If JYEL, only Ft bits are used, Fs bits are ignored.
If no JYEL, SF pattern (001110) found in Fs bits.
During any SF mode, loss of frame alignment (FRED) is declared when:
Number of frame errors detected—either Ft or Fs bit errors—meets selected loss of frame criteria
[RLOFA–RLOFC; addr 040]. FS_NFAS [addr 045] determines whether Fs bits are included in error count.
SLCSuperframe alignment is recovered when:
Terminal frame alignment is recovered, identifying Ft bits.
SLC pattern (refer to Table A-3, SLC-96 Fs Bit Contents) is found in 16 of 3 6 Fs bits, according to Bellcore
TR-TSY-000008.
During SLC modes without FSL OF, loss of frame alignment (FRED) is declared when:
Number of Ft bit errors detected meets selected reframe criteria [RLOFA–RLOFC; addr 040].
FSLOFFSLOF instructs the online fram er to monitor 16 of 36 Fs bits (SLC multiframe pattern) for loss of frame
alignment criteria. FS_NFAS [addr 045] must also be set to in clude Fs bits in loss of frame. FSLOF does not
affect the offline framer's search criteria.
ESFEx tended Superframe alignment is recovered when:
A valid FPS candidate is located (001011). Candidate bits are each separated by 772 digits and are received
without pattern errors.
If there is only one val id FPS candidate and the mode is one of the following:
No CRC mode—align to FPS, regardless of CRC6 comparison.
Mimic CRC mode—align to FPS, regardless of CRC6 comparison.
Force CRC mode—align to FPS, only if CRC6 is correct.
If there are two or more valid FPS candidates and the mode is one of the following:
No CRC mode—do not align (INVALID status).
Mimic CRC mode—align to first FPS with correct CRC6.
Force CRC mode—align to first FPS with correct CRC6.
During any ESF mode, loss of frame alignment (FRED) is declared when:
Number of FPS pattern errors detect ed meets selected loss of frame criteria [RLOFA–RLOFC; addr 040].
T1DMDuring T1DM mo de, frame alignment is recovered in two steps:
1. A 6-bit T1DM pattern (10111xx0) is found.
2. A valid F-bit pattern (Ft, Fs, or FPS) is found in the first six consecutive frames of the 12-frame cycle
aligned to the T1DM pattern.
During T1DM mode, loss of frame alignment (FRED) is declared when:
Number of frame errors detected, either Ft , Fs, or T1DM errors, meets selected loss of frame criteria
[RLOFA–RLOFC; addr 040]. FS_NFAS [addr 046] does not affect T1DM mode .
NOTE(S): To be compatible with Bellcore TA-TSY-000278, the processor must select SF + T1DM fra mer mode
and reframe criteria = 2 out of 6 F-bit errors [RLOFA–RLOFC; addr 040].
100054EConexant2-13
Page 72
2.0 Circuit DescriptionCX28394/28395/28398
2.2 ReceiverQuad/x16/Octal—T1/E1/J1 Framers
The offline framer waits until the current search is complete (see [FSTAT;
addr 017]) before checking for pending LOF reframe requests. If both online
framers have pending reframe requests, the offline framer aligns to the direction
opposite from that which was most recently searched. For example, if TLOF is
pending at the conclusion of a receive search which timed out without finding
alignment, the offline framer switches to search in the transmit direction. T he
TLOF switchover is prevented in the preceding example if the processor asserts
TABORT to mask the transmit reframe request. TABORT does not affect TLOF
status reporting. For applications that frame in only one direction, the opposite
direction should be masked. If, at the concl usion of a recei v e search, TLOF status
is asserted but masked by TABORT, the offline framer continues to search in the
receive di recti on. For applications that frame in both di recti ons, the processor c an
allow the offline framer to automatically arbitrate among pending reframe
requests, or may elect to manually control reframe precedence. An example of
manual control follows:
1Initialize RABORT = 1 and TABORT = 1
2Enable RLOF and TLOF interrupts
3Read clear pending ISR interr upts
4Release RABORT = 0
5Call LOF Ser vice Routine if either RLOF or TLOF interrupt;
{
(check curre nt LOF sta t u s [ALM1, 2; addr 047, 048 ]
If RLOF recovered and TLOF lost
—Assert RABORT = 1
—Release TABORT = 0
If RLOF lost or TLOF recovered
—Assert TABORT = 1
—Release RABORT = 0
}
The status of the offline framer can be monitored for diagnostic purposes
using the Offline Framer Status register [FSTAT; addr 017]. The register reports
the following: w het her the of fli ne framer is looking at th e recei v e or transmit dat a
streams (RX/TXN); whether the framer is actively searching for a frame
alignment (ACTIVE); whether the framer found multiple framing candidates
(TIMEOUT); whether the framer found frame sync (FOUND); and whether the
framer found no frame alignment candidates (INVALID). Note that these status
bits are updated in real time and might be active f or only v ery short (1-bit) periods
of time. Table 2-1 lists the receive framer modes.
2-14Conexant100054E
Page 73
CX28394/28395/283982.0 Circuit Description
Quad/x16/Octal—T1/E1/J1 Framers
2.2.8 External Receive Data Link (CX28394 and CX28398 Only)
The External Data Link (DL3) pro vi des signal access to any b it(s) in a ny ti me slot
of all frames, odd frames, or e v en frames, incl uding T1 framing bit s. Pin access t o
the DL3 receiver is provided through RDLCKO and RDLO. These two pins serve
as the DL3 clock output (RDLCK O) and data out put (RDLO). The data link mode
of the pins is selected using the RDL_IO bit in the Programmable Input/Output
register [PIO; addr 018].
Control of DL3 is provided in two registers: External Data Link Channel
[DL3_TS; add 015] and External Data Link Bit [DL3_BIT; addr 016]. RDL3 is
set up by selecting the bit(s) (DL3_BIT) and time slot [TS[4:0]; addr 015] to be
monitored, and then enabling the data link [DL3EN; addr 015], which star ts the
RDLCKO and TDLCKO gapped clock outputs that mark the selected bits, as
shown in Figure 2-4.
NOTE: DL3 signals are not provided on the CX28395. Therefore, DL3_TS must
be written to 00 to disable the DL3 transmitter and prevent transmit data
corruption.
Figure 2-4. Receive External Data Link Waveforms
RDLO
(T1: ESF)
Frame 1
24 F 1223241 2F
Frame 2Frame 3Frame 4Frame 5
24 F 1 2
23
23 2412
2.2 Receiver
F
23 241FF12232
RDLCKO
RCKi
RDLO
RDLCKO
NOTE(S): This waveform represents ESF FDL extraction; any combination of bits can alternatively be selected.
TS24TS1
F
2.2.9 Sa-Byte Receive Buffers
The Sa-Byte buffers give read access to the odd frame Sa bits in E1 mode. Five
receive Sa-Byte buffers [RSA4 to RSA8; addr 05B to 05F] are available. As a
group, the buffers are updated every multiframe from Sa-bits received in TS0.
This gives the processor up to 2 ms after the receive multiframe interrupt [RMF;
addr 008] occurs to read any Sa-Byte buffer before the buffer content changes.
8394-8-5_074
100054EConexant2-15
Page 74
2.0 Circuit DescriptionCX28394/28395/28398
2.2 ReceiverQuad/x16/Octal—T1/E1/J1 Framers
2.2.10 Receive Data Link
The RCVR contains two independent data link controllers (DL1 and DL2) and a
Bit-Oriented Protocol (BOP) transceiver. DL1 and DL2 can be programmed to
send and receive HDLC formatted messages in the Message-Oriented Protocol
(MOP) mode. Alternativel y, unformatted serial data can be sent and received ov er
any combination of bits within a selected time slot or F-bit channel. The BOP
transceiver can preemptively receive and transmit BOP messages, such as ESF
Yellow Alarm.
2.2.10.1 Data Link
Controllers
DL1 and DL2 control two serial data channels operating at mul tiples o f 4 kbps up
to the full 64 kbps time slot rate by selecting a combination of bits from odd,
even, or all frames. Both DL1 and DL2 support ESF Facilities Data Link (FDL),
SLC-96 Data Link, Sa Data Link, Common Channel Signaling (CCS), Signaling
System #7 (SS7), ISDN LAPD channels, Digital Multiplexed Interface (DMI)
Signaling in TS24, as well as the latest ETSI V.51 and V.52 signaling channels.
DL1 and DL2 each contain a 64-byte receive FIFO buffer.
Both data link controllers are configured identically, except for their offset in
the register map. The DL1 address range is 0A4 to 0AE, and the DL2 address
range is 0AF to 0B9. From this poin t on, DL 1 i s used to describe the op erati on of
both data link controllers.
DL1 is enabled using the DL1 Control register [DL1_CTL; addr 0A6]. DL1
will not function until it is enabled. DL1_CTL also controls the format of t he
data. The following data formats [DL1[1:0]; addr 0A6] are supported on the data
link: Frame Check Sequence (FCS), non-FCS, Pack8, or Pack6. FCS and
non-FCS are HDLC formatted messages. Pack8 and Pack6 are unformatted
messages with 8 bits per FIFO access, or 6 bits per FIFO access, respectively (see
Table 2-3).
Table 2-3. Commonly Used Data Link Settings
Data LinkFrameTime SlotTime Slot BitsMode
ESF FDLOdd0 (F-bits)Don’t CareFCS
T1DM R BitAll2400000010FCS
SLC-96Eve n0 (F-bits)Don’t CarePack6
ISDN LAPDAllN11111111FCS
Sa4Odd100001000FCS
NOTE(S): N represents any T1/E1 time slot.
The time slot and bit selection are performed through the DL1 Time Slot
Enable register [DL1_TS; addr 0A4] and t he DL1 Bit Enable register [DL1_BIT;
addr 0A5]. The DL1 Time Slot Enab l e re gist er sele cts the frames and time slo t to
extract the data link. The frame select tells the receiver to extract the time slot in
all frames, odd frames, or even frames. The time slot enable is a value between 0
and 31 that selects which time sl ot to extract. The DL1 Bit Enabl e re g ister sel ects
which bits will be extracted in the selected time slot. Refer to Table 2-3 for the
common frame, time slot, time slot bits, and modes used.
2-16Conexant100054E
Page 75
CX28394/28395/283982.0 Circuit Description
Quad/x16/Octal—T1/E1/J1 Framers
FIFO buffer is formatted differently than the transmit FIFO buffer. The Receive
buffer contains not only received messages, but also a status byte preceding each
message that specifies the size of the received message and the status of that
message. The message status reports if the message was aborted, received with a
correct or incorrect FCS, or continued. A continued message means the byte
count represents a partial message. When all message bytes are read, the buffer
contains another status byte. Message bytes can be differentiated from status
bytes in the buffer by reading the RSTAT1 bit in the RDL #1 Status register
[RDL1_STAT; addr 0A9]. RSTAT1 reports whether the next byte read from the
buffer will be a status byte or some number of message bytes.
can be tuned to the syst em’s CPU bandwidth . For systems with one dedicated
CPU, the data link status can be polled. For systems where a single CPU controls
multiple devices, the data link can be interrupt-driven. See Figures 2-5 and 2-6
for a high-level description of polling and interrupt driven Receive Data Link
Controller software.
very little microprocessor interrupt overhead. Block tran sfers from the buffer can
be controlled by the Near Full Threshold in the FIFO Fill Control register
[RDL1_FFC; addr 0A7]. The Near Full Threshold is a user programmable value
between 0 and 63. This value represents the maximum number of bytes that can
be placed in the Receive buffer without the near full being declared. Once the
threshold is set, the Near Full Status (RNEAR1) in RDL #1 Status [RDL1_S TAT;
addr 0A9] is asserted when the Near Full Threshold is reached. An interrupt,
RNEAR, in Data Link 1 Interrupt Status [ISR2; addr 009], is also available to
mark this e v e n t.
request register directing software to the lower levels (see Master Interrupt
Request register; addr 081 and Interrupt Request register; addr 003). Of all the
interrupt sources, the two most significant bandwidth requirements are signaling
and data link interrupts. Each data link controller has a top-level interrupt status
register that reports data link operations (see Data Link 1 and 2 Interrupt Status
registers [ISR2, ISR1; addr 009 and 00A). The processor uses a three-step
interrupt scheme for the data link:
2.2 Receiver
The Receive Data Link FIFO #1 [RDL1; addr 0A8] is 64 bytes. The Receive
The receive data link controller has a versatile microprocessor interface that
Using the Receive FIFO buffer, an entire block of data can be received with
The device uses a hierarchical inte rrupt structure, with one top-level i nterrupt
1. Read the Master Interrupt Request register to determine which framer
interrupted.
2. Read the Interrupt Request register for that framer.
3. Use that register value to read the corresponding Data Link Interrupt
Status register.
100054EConexant2-17
Page 76
2.0 Circuit DescriptionCX28394/28395/28398
2.2 ReceiverQuad/x16/Octal—T1/E1/J1 Framers
Figure 2-5. Polled Receive Data Link Processing
Receive Message
Read Data Link Status
Wait N Milliseconds
If
FIFO EMPTY
No
If
Message Status
on FIFO
Yes
Read Message Status from FIFO
Read X Message Bytes from FIFO
Yes
If
Message Status
is Continue
Wait N Milliseconds
Yes
Read Message Byte from FIFO
and Discard
No
No
If
Message Status
is Good
No
Error Receiving Message
Return
NOTE(S): Message status contains number of message bytes (X) in FIFO.
Yes
Return
2-18Conexant100054E
Page 77
CX28394/28395/283982.0 Circuit Description
Quad/x16/Octal—T1/E1/J1 Framers
Figure 2-6. Interrupt-Driven Receive Data Link Processing
Interrupt Service Routine
Interrupt Oc curred
Read Interrupt Status
Complete MSG
or Near Full
Interrupt
Yes
Read Data Link Status
Read Message Byte from FIFO
and Discard
No
Message Status
on FIFO
2.2 Receiver
No
Process Other Interrupt
If
Return
Yes
Read Message Status from FIFO
Read X Message Bytes from FIFO
If
Message Status
is Good or
Continue
No
Error Receiving Message
Return
NOTE(S): Message status contains number of message bytes (X) in FIFO.
including the ESF Yellow Alarm, which consists of repeated 16-bit patterns with
an embedded 6-bit codeword as shown in this example:
0xxxxxx0 11111111 (received right to left)
[543210] RBOP = 6-bit codeword
The BOP message channel is configured to operate over the same channel
selected by Data Link #1 [DL1_TS; addr 0A4]. It must be configured to operate
over the FDL channel so RBOP can detect priority, command, and response
codeword messages according to ANSI T1.403, Section 9.4.1.
RBOP is enabled using the RBOP_START bit in Bit Oriented Protocol
Transceiver register [BOP; address 0A0]. BOP codewords are received in the
Receive BOP Codeword register [RBOP; addr 0A2], which contains the 6-bit
codew ord, a valid flag (RBOP_VALID), and a lost flag (RBOP_LOST). The valid
flag is set each time a new codew ord is put in RBOP, and is cleared on reading the
codeword. The lost flag indicates a new codeword overwrote a valid codeword
before being read by the processor.
The BOP receiver can be configured to update RBOP using a message length
filter and integration filter. The recei ve BOP message length filter [RBOP_LEN;
addr 0A40] sets the number of successive identical messages required before
RBOP is updated. RBOP_LEN can be set to 1, 10, or 25 messages. When
enabled, the RBOP integration filter [RBOP_INTEG; add 0A0] requires receipt
of two identical consecutive 16-bit patterns, without gaps or errors between
patterns, to validate the first codeword. RBOP integration is needed to meet the
codeword detection criteria while receiving 1/1000 bit error ratio.
The real-time status of the codeword reception can be monitored using the
RBOP_ACTIVE bit in the BOP Status register [BOP_STAT; addr 0A3]. Each
time a message is put in RBOP register, an interrupt is generated, and the RBOP
bit is set in the Data Link 2 Interrupt Status register [ISR1; addr 00A].
2-20Conexant100054E
Page 79
CX28394/28395/283982.0 Circuit Description
Quad/x16/Octal—T1/E1/J1 Framers
2.3 System Bus
Each framer provides high-speed, transmit and receive serial TDM interfaces.
These interfaces can be configured as non-multiplexed, individual system buses,
or they can be multiplexed internally or externally to provide 2xE1 (4096 Mbps)
and 4xE1 (8192 Mbps) buses. The system bus is compatible with the Mitel
ST-Bus, the Siemens PEB Bus, and the AT&T CHI Bus and directly connects to
other Conexant serial TDM bus devices without the need for any external
circuitry. The following five bus rates are supported:
•1.536 MHz—T1 rate, 24 time slots, without framing bit
•1.544 MHz—T1 rate with framing bit
•2.048 MHz—E1 rate, 32 time slots
•4.096 MHz—twice the E1 rate, 64 time slots
•8.192 MHz—four times the E1 rate, 128 time slots
2.3.1 Non-Multiplexed Mode
2.3 System Bus
In Non-Multiplexed mode, each framer has a separate system bus interface
consisting of the following pin functions:
The signal available on dual function pins is controlled using register PIO
[addr 018].
To use Non-Multiplexed mode, SBIMODE[0] and/or SBIMODE[1] in the
Framer Control register [FCR; addr 080] must be zero to disable Internally
Multiplexed mode. The system bus rate i s independent of the line rate and must
be selected using SBI[3:0] in the System Bus Interface Configuration register
[SBI_CR; addr 0D0]. Register bit SBI_OE [SBI_CR; addr 0D0] must also be set
to 1 to enable system bus outputs.
Transmit System Bus (TSB)
100054EConexant2-21
Page 80
2.0 Circuit DescriptionCX28394/28395/28398
2.3 System BusQuad/x16/Octal—T1/E1/J1 Framers
2.3.2 Externally Multiplexed Mode
Externally Multiplexed mode allows any two, three, or four framers (in the same
or different devices) to share a common high speed system bus (see Figure 2-7).
The 4.096 and 8.192 MHz bus modes contain multiple bus members (bus groups
A, B, C, D) which allow multiple T1/E1 signals to share the same system bus.
This is done by interleaving the time slots from up to four framers (see
Figures 2-10 and 2-11).
To use Externally Multiplexed mode, SBIMODE[0] and/or SBIMODE[1] in
the Framer Control register [FCR; addr 080] must be zero to disable Internally
Multiplexed mode. The system bus rate i s independent of the line rate and must
be selected using SBI[3:0] in the System Bus Interface Configuration register
[SBI_CR; addr 0D0]. SBI[3:0] is also used to assign each framer to a different
bus group. Register bits SBI_OE [SBI_CR; addr 0D0], BUS_RSB [RSB_CR;
addr 0D1], and BUS_TSB [TSB_CR; addr 0D 4] must be set to 1 to all ow system
bus outputs to share common connections.
device (or from different
devices) can be externally
multiplexed with no additional
circuitry.
2.048 Mbps
1.544 Mbps
8394-8-5_003
2-22Conexant100054E
Page 81
CX28394/28395/283982.0 Circuit Description
Quad/x16/Octal—T1/E1/J1 Framers
2.3.3 Internally Multiplexed Mode
Internally Multiplexed mode operation is very similar to Externally Multiplexed
mode. The framers in each device are internally grouped into four-framer groups
to allow an internally multiplexed mode (see Figure 2-8). In the CX28398,
framers 1 through 4 form a group (lo wer group or group A) and framers 5 through
8 form another (upper group or group B). The CX28395 supports fou r groups: A,
B, C, and D. The CX28394’s four framers are also grouped in the same manner. In
this mode, system bus signals from all four framers are internally connected and
the interface pin functions are redefined. The advantage of this mode is that all
system bus signals which are normally available on dual function pins, are now
available on separate pins. In Internally Multiplexed mode, the following signals
are available for each four-framer group (lower group shown):
Receive System Bus (RSB)
RSBCKI[A]TSBCKI[A]
RPCMO[A]TPCMI[A]
RFSYNC[A]TFSYNC[A]
RINDO[A]TINDO[A]
2.3 System Bus
Transmit System Bus (TSB)
Common, internally
connected to all four
framers.
RSIGO[1:4]TSIGI[1:4]
RMSYNC[1:4]TMSYNC[1:4]
RDLCKO[1:4]
RDLO[1:4]
(1)
(1)
TDLCKO[1:4]
TDLI[1:4]
(1)
(1)
Separate signals.
SIGFRZ[1:4]—
NOTE(S):
(1)
These signals are not provided on the CX28395.
To use Internally Multiplexed mode, SBIMODE[0] and/or SBIMODE[1] in
the Framer Control re gister [FCR; ad dr 08 0] must b e set to 1. The system bus rate
is independent of the line rate and must be selected using SBI[3:0] in the System
Bus Interface Configuration register [SBI_CR; addr 0D0]. SBI[3:0] is also used
to assign each framer to a different bus group. Register bits SBI_OE [SBI_CR;
addr 0D0], BUS_RSB [RSB_CR; addr 0D1], and BUS_TSB [TSB_CR; addr
0D4] must be set to 1 to allow system bus outputs to share common connections.
Because RFSYNC (and TFSYNC) signals are bused, all four framers’ RFSYNC
(and TFSYNC) signals must be configured as inputs and driven externally or,
alternatively, three framers’ sync signals can be configured as inputs and one as
an output [PIO; addr 018].
Two separte 8.192
Mbps buses is the
typical application for
Internally Multiplexed
mode.
8.192 Mbps
2.3.4 Receive System Bus
The Receive System Bus (RSB) provides a high-speed, serial interface between
the RCVR and the system bus. The RSB has the following pins:
Framer 1
Framer 2
Framer 3
Framer 4
Framer 5
Framer 6
Framer 7
Framer 8
CX28398
4.096 Mbps
In this application, Framers 3 and 4
are used as back-up line interfaces
and are connected to the system bus;
but are disabled.
8.192 Mbps
In this application, Framer 8 is used as
a back-up line interface and is
connected to the system bus; but is
disabled.
8394-8-5_004
Pin NameFunction
RSBCKIReceive System Bus Clo c k
RPCMOReceive PCM Data
RFSYNC/RMSYNCReceive Frame Sync or
Receive Multiframe Sync
RINDO/RDLCKOReceive Time Slot Indicator or
Receive Datalink Clock
RSIGO/RDLOReceive Signaling Data or
Receive Datalink Data
SIGFRZSignaling Freeze
2-24Conexant100054E
Page 83
CX28394/28395/283982.0 Circuit Description
Quad/x16/Octal—T1/E1/J1 Framers
are provided in Table 1-6, Hardware Si gnal Definitions. RSB dat a out put s can be
configured to output on the rising or falling edge of RSBCKI (see the Receive
System Bus Configuration register [RSB_CR; addr 0D1]).
Figure 2-9. RSB Waveforms
RSBCKI
Frame48TS31Frame1TS0
E1
T1
RPCMO
RINDO
RSIGO
RPCMO
RINDO
RSIGO
123456781234 567812
ABCDABCDABCDABCDAB
Frame48TS24Frame1TS1
12345678F123456781
ABCDABCDXABCDABCDA
2.3 System Bus
Figure 2-9 illustrates the relationship betw een th ese signals. Si gnal definitions
SIGFRZ
RFSYNC
RMSYNC
NOTE(S): The Receive Multif rame Sync (RMSYNC) occurs every 6 ms, 48 T1 or 48 E1 frames.
The RSB supports five different system bus rates (MHz):
•1.536 MHz—T1 rate, 24 time slots, without framing bit
•1.544 MHz—T1 rate with framing bit
•2.048 MHz—E1 rate, 32 time slots
•4.096 MHz—twice the E1 rate, 64 time slots
•8.192 MHz—four times the E1 rate, 128 time slots
100054EConexant2-25
Page 84
2.0 Circuit DescriptionCX28394/28395/28398
2.3 System BusQuad/x16/Octal—T1/E1/J1 Framers
The 4.096 and 8.192 MHz bus modes contain multiple bus members (A, B,
C, D) which allow multiple T1/E1 signals to share the same system bus. This is
done by interleaving the time slots from up to four framers, without external
circuitry (see Figures 2-10 and 2-11). The system bus rate is independent of the
line rate and must be selected using the System Bus Interface Configuration
register [SBI_CR; addr 0D0].
Figure 2-10. RSB 4096K Bus Mode Time Slot Interleaving
RSBCKI
RPCMO
RSIGO
RFSYNC
NOTE(S): A and B time slot comes from different framers. Output data on rising edg e clock, RCPM_NEG = 0 [addr 0D1].
TS31ATS31BTS0ATS0B
SIG31ASIG31BSIG0ASIG0B
Output sync on rising edge clock, RSYN_NEG = 0 [addr 0D1]. RSBCKI operates at 1 times the data rate.
Figure 2-11. RSB 8192K Bus Mode Time Slot Interleaving
RSBCKI
RPCMO
RSIGO
RFSYNC
NOTE(S): A, B, C, and D data comes from differe nt framers. Output dat a on rising edge clock, RCPM_NEG = 0 [addr 0D1] .
TS31ATS31BTS31CTS31DTS0ATS0BTS 0CTS0D
SIG31ASIG31BSIG31CSIG31DSIG0ASIG0BSIG0CSIG0D
Output sync on rising edge cl ock, RSYN_NEG = 0 [addr 0D1]. RSBCKI operates at 1 times the data rate. RSB.OFFSET equals
zero.
2-26Conexant100054E
Page 85
CX28394/28395/283982.0 Circuit Description
Quad/x16/Octal—T1/E1/J1 Framers
32 (CEPT) line rate time slots can be mapped to 24, 32, 64, or 128 system bus
time slots as listed in Table 2-4. The system bus rate must be greater than or equal
to the line rate, except for 1536K bus mode.
Table 2-4. RSB Interface Time S lot Mapping
2.3 System Bus
The RSB maps line rate time slots to system bus time slots. Th e 24 (DS1) or
The RSB, Figure 2-12, consists of a timebase, slip buffer, a signaling buffer,
and a signaling stack.
RSIG
Buffer
RSIG
Local
RSLIP
Buffer
AIS
RPHASE
Loopback
Remote
Channel
RSBCK
Local
Channel
Loopback
RSIG
STACK
RSB
Timebase
RSIGO
RPCMO
SIGFRZ
RINDO
RFSYNC
RMSYNC
RSBCKI
TSBCKI
I/O From Pins
}
100054EConexant2-27
Page 86
2.0 Circuit DescriptionCX28394/28395/28398
2.3 System BusQuad/x16/Octal—T1/E1/J1 Framers
2.3.4.1 TimebaseThe RSB timebase synchronizes RFSYNC, RMSYNC, and RINDO with the
Receive System Bus Clock (RSBCKI). The RSBCK can be slaved to two
different clock sources: Receive System Bus Clock Inp ut (RSBCKI), or Transmit
System Bus Clock Input (TSBCKI). The R SB clock sel ection is made thro ugh the
Clock Input Mux register [CMUX; addr 01A]. The system bus clock can also be
configured to run at twice the data rate by setting the X2CLK bit in the System
Bus Interface Configuration register [SBI_CR; addr 0D0].
In Non-Multiplexed mode, the RFSYNC/RMSYNC dual function pin is
configured for either RFSYNC or RMSYNC using the RMSYNC_EN register bit
[PIO; addr 018]. RFSYNC and RMSYNC can be configured as inputs or outputs
[PIO; addr 018]. RFSYNC and RMSYNC should be configured as inputs when
the RSB timebase is slaved to the system bus [SBI_OE; addr 0D0]. RFSYNC an d
RMSYNC should be configured as outputs when the RSB timebase is master of
the system bus. RFSYNC and RMSYNC can be also configured as rising or
falling edge outputs [RSB_CR; addr 0D1]. In addition to having RFSYNC and
RMSYNC active on the frame boundary, a programmable offset is available to
select the time slot and bit offset in the frame. See the Receive System Bus Sync
Time Slot Offset [RSYNC_TS; addr 0D3] and the Receive System Bus Sync Bit
Offset [RSYNC_BIT; addr 0D2].
the Receiver Clock (RCKI) and data (RNRZ), to the Receive System Bus Clock
(RSBCK) and data (RPCMO). RSLIP acts like an elastic store b y clocking RNRZ
data in with RCKI and clocking PCM data out on RPCMO with RSBCK.
If the system bus rate is greater than the line rate (i.e., T1 line rate and E1
system bus rate), there will be a mismatched number of time slots. The m a pping
of line rate time slots to system bus time slots is done by time slot assignments
with the ASSIGN bit in the Sy stem Bus Per-Channel Control register [SBC0 to
SBC31; addr 0E0 to 0FF]. ASSIGN selects which system bus time slots are used
to transport line rate time slots. Time slot mapping is done by mapping the first
line rate time slot to the first assigned system bus time slot. For example, T1 to E1
mapping might make every fourth time slot unassigned (i.e., 3, 7, 11, 15, 19, 23,
27, 31); see Figure 2-13. This distribution of unassigned time slots averages out
the idle time slots and op timizes the use of the slip buffer.
2-28Conexant100054E
Page 87
CX28394/28395/283982.0 Circuit Description
Quad/x16/Octal—T1/E1/J1 Framers
Figure 2-13. T1 Line to E1 System Bus Time Slot Mapping
Frame AFrame B
F
RNRZ
RPCMO
NOTE(S):
(1)
u = unassigned time slots
(2)
FA = T1 frame bit, frame A
(3)
FB = T1 frame bit, frame B
2 3 4 524 FB1 241233
A
02 3 4 5162830 31 0 1292
6
u
u
7
RSLIP has four modes of operation: Two Frame Normal, 64-bit Elastic,
Two-Frame Short, and Bypass. RSLIP mode is set in the Receive System Bus
Configuration register [RSB_CR; addr 0D1]. RSLIP is organized as a two-frame
buffer. This allows MPU access to frame data, regardless of the RSLIP mode
selected. Each byte offset into the frame buffer is a different time slot: offset 0 in
RSLIP is always time slot 0 (TS0), offset 1 is always TS1, and so on. The slip
buffer has processor read/write access.
Two-Frame Norm alIn Normal mode, the slip buffer total depth is two 193-bit frames (T1) or two
256-bit frames (E1). Data is written to the slip buffer using RXCLK, and read
from the slip buffer using RSBCK. If a slight rate difference between the clocks
occurs, the slip buffer changes from its initial condition—approximately half
full—by either adding or removing frames. If RXCLK writes to the slip buffer
faster than RSBCK reads th e data, the buffer will fill up. When the slip buffer in
Normal mode is full, an entire frame of data is deleted. Conversely, if RSBCK
reads the slip buffer faster than RXCLK writes the data, the buffer will become
empty. When the slip buffer in Normal mode is empty, an entire frame of data is
duplicated. When an entire frame is deleted or duplicated it is known as a Frame
Slip (FSLIP), which i s al w a ys one full frame of data. The FSLIP status is reported
in the Slip Buffer Status register [SSTAT; addr 0D9]. In T1 mode, the F-bit is
treated as part of the frame and can slip accordingly.
2.3 System Bus
22
u
27
u
100054EConexant2-29
Page 88
2.0 Circuit DescriptionCX28394/28395/28398
2.3 System BusQuad/x16/Octal—T1/E1/J1 Framers
64-Bit ElasticIn 64-bit Elastic mod e, the slip buffer total depth i s 64 bits, and the initial
throughput delay is 32 bits, one-ha lf of the total depth. Similar to Normal mode ,
Elastic mode allows the system bus to operate at any of the programmable rates,
independent of the li ne rate. T he adv a ntage of thi s mode over the Normal mode is
that throughput delay is reduced from one frame to an average of 32 bits, and the
output multiframe always retains its alignment with respect to the out put data.
The disadvantage of th is mode is handling t he full and empty buf fer conditions. In
Elastic mode, an empty or full buffer condition causes an Uncontrolled Slip
(USLIP). Unlike an FSLIP, a USLIP is of unknown size within the range of 1 to
256 bits of data. The USLIP status is reported in SSTAT.
Two-Frame ShortThe Two-Fr ame Short mode combines the depth of t he Normal mode wit h th e
throughput delay of the Elastic mode. The Two-Frame Short mode begins in the
Elastic mode with a 32-bit initial throughput delay, and switches to the Normal
mode when the buffer beco mes empty or full; thereafte r the Two-Fr ame Short and
normal mode perform identically. If the slip buffer is full (two frames) in the
Two-Frame Short mode, an FSLIP is reported, after which the slip buffer and
Two-Frame mode perform identically.
BypassIn Bypass mode, data is immediately clocked th rough RS LIP f r om the R C VR
to RSB, and RCKI internally replaces the system bus clock.
2.3.4.3 Signaling BufferThe 32-byte Receive Signaling Buffer [RSIG; addr 1A0 to 1BF] stores a single
multiframe of signaling data. Each byte offset into RSIG contains signaling data
for a different time slot: offset 0 stores TS0 signaling data, offset 1 stores TS1
signaling data and so on. The signali ng data is stored in th e least si gnificant 4 bits
of RSIG. The output signaling data is stored in the most significant 4 bits of
RSIG. Similar to RSLIP, the RSIG buffer has read/write processor access to read
or overwrite signaling information. RMSYNC extracts robbed-bit signaling from
RSIG onto RPCMO; RFSYNC extracts ABCD signaling from RSIG onto
RSIGO.
The RSIG buffer has the following configurable features: transparent,
robbed-bit signaling; signaling freeze; debounce signaling; and unicode
detection. Each feature is available in the Receive Signaling Configuration
register [RSIG; addr 0D7]. See the registers section for more details.
2-30Conexant100054E
Page 89
CX28394/28395/283982.0 Circuit Description
Quad/x16/Octal—T1/E1/J1 Framers
2.3 System Bus
2.3.4.4 Signaling StackThe Receive Signaling Stack (RSTACK) allows the processor to quickly extract
signaling changes without polling every channel. RSTACK is activated on a
per-channel basis by set ting the Received Signaling Stack (SIG_STK) control bit
in the Receive Per-Channel Control register [RPC0 to RPC31; addr 180 to 19F].
The signaling stack stores the channel and the A, B, C, and D signaling bits that
changed in the last multiframe. The stack has the capacity to store signaling
changes for all 24 (T1) or 30 (E1) PCM channels.
At the end of any mul t iframe where one or more ABCD signaling values hav e
changed, an interrupt occurs with RSIG set in the Timer Interrupt Status register
[ISR3; addr 008]. The processor then reads the Receiv e Signali ng Stack [STACK;
addr 0DA] twice to ret rie v e the chan nel nu mber (WORD = 0) and the new ABCD
value (WORD = 1), and continues to read from STACK until the MORE bit in
STACK is cleared, indicating the RSIG stack is empty.
Optionally, the processor can select RSIG interrupt (SET_RSIG; addr 0D7) t o
occur at each multiframe boundary in T1 modes, regardless of signaling change.
This mode provides an interrupt aligned to the mu ltiframe to read the RSIG
buffer, rather than to read RSTACK.
2.3.4.5 Embedded
Framing
Embedded framing mode bit (EMBED; addr 0D0) instructs the RSB to embed
framing bits in RPCMO while in T1 mode.
The Embedded mode supports ITU-T Recommendation G.802, which
describes how 24 T1 time slots and one framing bit (193 bits) are mapped to 32
E1 time slots (256 bits). This mapping is done by leaving TS0 and TS16
unassigned; by storing the 24 T1 time slots in TS1 to TS15, and TS17 to TS25;
and by storing the frame bit in bit 1 o f TS26 (see Figure 2-14). TS26 through
TS31 are also unassigned.
Figure 2-14. G.802 Embedded Framing
F
RNRZ
RPCMO
E1 FramingE1 Multiframe/Signalling
Time Slot
21424 FB1 223 241 2123F
A
uuuuu
02141
Frame A
16 17
15
15
16 17
Time Slot
Frame B
181 2
2426 2731250
F
X XX X X XX
B
C
NOTE(S):
(1)
X = unused bits
(2)
u = unassigned time slot (see ASSIGN bit [addr 0E0 to 0FF])
(3)
FA = T1 frame bit, frame A
(4)
FB = T1 frame bit, frame B
(5)
FC = T1 frame bit, frame C
100054EConexant2-31
Page 90
2.0 Circuit DescriptionCX28394/28395/28398
2.3 System BusQuad/x16/Octal—T1/E1/J1 Framers
2.3.5 Transmit System Bus
The Transmit System Bus (TSB) consists of a timebase, slip buffer, signaling
buffer , and transmit framer (Figure 2-15). It provides a hi gh-spe ed serial interface
between the XMTR and the system bus.
Figure 2-15. TSB Interface Bloc k Diagram
From
Transmit
Timebase
TNRZ
Remote
Channel
TXDATA
Loopback
TPHASE
TSLIP
Buffer
TSIG
Local
TSIG
Local
Local
Channel
Loopback
Timebase
TSB
Transmit
Framer
The TSB contains the fol l owing five pins:
Pin NameFunction
TSBCKITransmit System Bus Clock
TPCMITransmit PCM Data
TFSYNC/TMSYNCTransmit Frame Sync or
Transmit Multifram e Sync
TINDO/TDLCKOTransmit Time Slot Indicator or
Transmit Datalink Clock
TSIGI/TDLITransmit Signaling Data or
Transmit Datalink Data
RSBCKI
TSBCKI
TINDO
TFSYNC
TMSYNC
TPCMI
TSIGI
8394-8-5_035
2-32Conexant100054E
Page 91
CX28394/28395/283982.0 Circuit Description
Quad/x16/Octal—T1/E1/J1 Framers
Refer to Figure 2-16 for the relationship between these signals. Signal
definitions are provided in Table 1-6, Hardware Signal Definitions. TSB data
outputs can be configured to input data on the rising or falling edge of TSBCKI
(see the Transmit System Bus Configuration register [TSB_CR; addr 0D4].
Figure 2-16. Transmit System Bus Waveforms
TSBCKI
Frame48TS31Frame1TS0
E1
T1
TPCMO
TINDO
TSIGI
TPCMI
TINDO
TSIGI
TFSYNC
123456781234567812
XXXXABCDXXXXABCDXX
Frame48TS24Frame0TS1
12345678F123456781
XXXXABCDXXXX XABCDX
2.3 System Bus
TMSYNC
The TSB supports five different system bus rates (MHz):
•1.536 MHz—T1 rate, 24 time slots, without framing bits
•1.544 MHz—T1 rate with framing bits
•2.048 MHz—E1 rate, 32 time slots
•4.096 MHz—twice the E1 rate, 64 time slots
•8.192 MHz—four times the E1 rate, 128 time slots.
100054EConexant2-33
Page 92
2.0 Circuit DescriptionCX28394/28395/28398
2.3 System BusQuad/x16/Octal—T1/E1/J1 Framers
The 4.096 and 8.192 MHz bus modes contain mu lti ple bus members (A, B, C,
and D) of which one bus member is selected by the SBI [3:0] bits in the System
Bus Interface Configuration register [SBI_CR; 0D0] (see Figures 2-17 and 2-18).
The system bus rate is in depe ndent o f th e l in e rat e and must be selected using the
System Bus Interface Configuration register.
Figure 2-17. TSB 4096K Bus Mode Time Slot Interleaving
TSBCKI
TPCMI
TSIGI
TFSYNC
NOTE(S): A and B time slot data comes from different framers. TS BC KI can be operated at 1 or 2 times the dat a rate.
TS31ATS31BTS0ATS0B
SIG31ASIG31BSIG0ASIG0B
Figure 2-18. TSB 8192K Bus Mode Time Slot Interleaving
TSBCKI
TPCMI
TSIGI
TFSYNC
NOTE(S): A, B, C, and D time slot data comes from different framers. TSBCKI can be operated at 1 or 2 times t he data rate.
TS31AT S31BTS31CTS31DTS0ATS0BTS0CTS0D
SIG31ASIG31BSIG31CSIG31DSIG0ASIG0BSIG0CSIG0D
2-34Conexant100054E
Page 93
CX28394/28395/283982.0 Circuit Description
Quad/x16/Octal—T1/E1/J1 Framers
2.3.5.1 TimebaseThe TSB timebase synchronizes TPCMI, TFSYNC, TMSYNC, and TINDO wit h
the Transmit System Bus Clock (TSBCK). The TSBCK can be slaved to three
different clock sources: Transmit Clock Input (TCKI), Transmit System Bus
Clock Input (TSBCKI), and Receive System Bus Clock Input (RSBCKI). The
TSB clock selection is ma de t hrou gh t he C l ock In put Mu x register [CMUX; addr
01A]. TCKI is automatically selected when the transmit slip buffer is bypassed.
The system bus clock can also be configured to run at twice the data rate by
setting the X2CLK bit in the System Bus Interface Configuration register
[SBI_CR; addr 0D0] when TSLIP is not in Bypass mode.
In Non-Multiplexed mode, the TFSYNC/TMSYNC dual function pin is
configured for either TFSYNC or TMSYNC using the TMSYNC_EN register bit
[PIO; addr 018]. TFSYNC and TMSYNC can be individually configured as
inputs or outputs, [PIO; addr 01 8]. TFSYNC and TMSYNC should b e configured
as inputs when the TSB timebase is sl aved to the system bus, the transmit framer
is disabled [TABORT; addr 071], or TSB carries embedded T1 framing.
TFSYNC and TMSYNC should be configured as outputs wh en the TSB timeb ase
is master of the system bus, or the transmit framer is enabled. TFSYNC and
TMSYNC can be also configured as rising or falling edge outputs [TSB_CR;
addr 0D4]. In addition to having TFSYNC and TMSYNC active on the frame
boundary, a programmable offset is available to select the time slot and bit offset
in the frame (see Tran smit S ystem Bus S ync Time Slot Offset [TSYNC_TS; addr
0D6] and Transmit System Bus Sync Bit Offset [TSYNC_BIT; addr 0D5]).
2.3 System Bus
2.3.5.2 Slip BufferThe 64-byte Transmit PCM Slip Buffer [TSLIP; addr 140 t o 17 F] resynchronizes
the Transmit System Bus Clock (TSBCK ) and data (TPCMI) to the Transmit
Clock (TXCLK) and data (TNRZ). TSLIP acts like an elastic store by clocking
PCM data in on TPCMI wi th TS BCK and cl ocking TNRZ dat a out with T XCLK.
TPCMI can be configured to sample on the ri sing or falling edge of TSBCKI (se e
the Transmit System Bus Configuration register [TSB_CR; addr 0D4]).
TSLIP has four modes of operation: Two Frame Normal, 64-bit Elastic, Two
Frame Short, and Bypass. TSLIP mode is set in the Transmit System Bus
Configuration register [TSB_CR; addr 0D4]. It is organized as a two-frame
buffer, with high frame and low frame buffers. This allows MPU access to frame
data, regardless of the TSLIP mode selected. Each byte offset into the frame
buffer is a di fferent time slot , offset 0 in TSLIP is always time slot 0 (TS0); offset
1 is always TS1, and so on. The slip buffer has processor read/write access.
Two-Frame Norm alIn Normal mode, the slip buffer total depth is two 193-bit frames (T1), or two
256-bit frames (E1) . Data is written to the slip buf fer us ing TSBCK and read f rom
the slip buffer using TXCLK. If there is a slight rate difference between the two
clocks, the slip buffer changes from its initial condition—approximately half
full—by either adding or removing frames. If TSBC K writes to the slip buffer
faster than TXCLK reads the data, the buffer becomes full. When the slip buffer
in Normal mode is full, an entire frame of data is deleted. Conversely, if TXCLK
is reading the slip buffer at a faster rate than TSBCK is writing the data, the buffer
will eventually empty, and an entire frame of data is duplicated. When an entire
frame is deleted or duplicated, it is known as a Frame Slip (FSLIP). An FSLIP is
always one full frame of data. The FSLIP status is reported in the Slip Buffer
Status register [SSTAT; addr 0D9].
100054EConexant2-35
Page 94
2.0 Circuit DescriptionCX28394/28395/28398
2.3 System BusQuad/x16/Octal—T1/E1/J1 Framers
64-Bit ElasticIn 64-bit Elastic mod e, the slip buffer total depth i s 64 bits and the initial
throughput delay is 32 bits, or one-half of the total depth. Similar to Normal
mode, Elastic mode allows the system bus to operate at any of the programmable
bus rates, independent of the line rate. The advantage of this mode over the
two-frame mode is that t hroughput del a y is reduced from on e frame to an average
of 32 bits, and the transmit multiframe can retain its alignment with respect to the
transmit data. The disadv ant age of thi s mode is hand ling t he full and empt y buf fer
conditions. In 64-bit Elastic mode, an empty or full buffer condition causes an
Uncontrolled Slip (USLIP). Unlike an FSLIP, a USLIP is of unknown size,
ranging from 1 to 256 bits of data. The USLIP status is reported in SSTAT.
Two-Frame ShortThe Two-Fr ame Short mode combines the depth of t he Normal mode wit h th e
throughput delay of the Elastic mode. This mode begins in Elastic mode with a
32-bit initial throughput delay, and switches to Normal modes when the buffer is
empty or full; thereafter, the Two-Frame Short and Normal modes perform
identically. If the slip buffer is full (two frames) in the Two-Frame Short and
normal modes, an FSLIP is reported; thereafter, the slip buffer performs exactly
like Normal mode.
BypassIn Bypass mode, data is clocked through TSLIP from the TSB to the XMTR
using TXCLK as selected by the TXCLK input clock mux.
2.3.5.3 Signaling BufferThe 32-byte Transmit Signaling Buffer [TSIG; addr 120–13F] stores a single
multiframe of signaling data input from TSIGI pin and is updated as each time
slot is received in e v ery TSB frame. Each b yte of fset into TSIG is a dif ferent time
slot’s signaling data: offset 0 stores TS0 signaling data, offset 1 stores TS1
signaling data, etc. The si gnaling data is stored in the lea st significant 4 bits of the
signaling buffer. Similar to TSLIP, TSIG has read/write processor access for
accessing or o v erwriting signaling i nformation. TFSYNC is used b y the si gnaling
buffer to identify the frame boundaries in the TSIGI data stream.
2.3.5.4 T r an smi t
Framing
A transmit framing option is provided to allow the transmitter to auto matically
align to the transmit PCM data on TPCMI. In this mode , the Transmit Framer
searches transmit data for a valid E1 or T1 framing pattern. The transmit data
stream has two framing functi ons: offline framer and an onl ine framer . The of fline
framer recovers the transmit frame alignment (TFSYNC). The online framer
monitors the frame alignment found by the offline framer and recovers
multiframe alignment (TMSYNC).
T ra nsmit Frame AlignmentTransmit frame resynchronization is initiated by activating the Transmit Loss
Of Frame (TLOF) status bit in the Alarm 2 status [ALM2; addr 048] register by
the online framer. The TLOF criteria is set in the TLOFA, TLOFB, and TLOFC
bits of the Transmitter Configuration register [TCR1; addr 071]. The online
framer supports the following LOF criteria for T1: 2 frame bit errors out of 4, 2
out of 5, or 2 out of 6; for E1, it supports 3 out of 3. Figure 2-19 illustrates
transmit framing and timebase alignment options.
2-36Conexant100054E
Page 95
CX28394/28395/283982.0 Circuit Description
Quad/x16/Octal—T1/E1/J1 Framers
Figure 2-19. Transmit Framing and Timebase Alignment Options
A
B
TSLIP
Buffer
01
Off-Line
Framer
Pass
MF
Pass
MF
TPCMI
TFSYNCI
TMSYNCI
TFSYNCO
TMSYNCO
TSB
Offset
FSYNC MSYNC
TSB Timebase
TSB Aligns to TPCMI (EMBED = 0)
A
TSBAlignstoTX(TSB_ALIGN=1)
B
2.3 System Bus
TNRZ
TPHASE
MFAS
CAS
On-Line
C
D
Recenter
(TUSLIP)
FSYNCMSYNCFASCAS
TX Timebase
TSB Aligns to TNRZ (EMBED = 1)
C
TX Aligns to TSB (TX_ALIGN = 1)
D
On-Line
NOTE(S):
(1)
EMBED located in SBI_CR (addr 0D0).
(2)
TSB_ALIGN and TX_ALIGN located in TSB_CR (add r 0D4).
When TLOF is asserted, the offline framer searches the transmit data stream
for a new frame alignment, provided that transmit framing is enabled [TABORT;
addr 071]. If embedded framing is enabled [EMBED; addr 0D0], the offline
framer examines the TSLIP buffer output—TNRZ—for transmit frame
alignment. If embedded framing is disabled, the offline framer examines the slip
buffer input (TPCMI) for transmit frame alignment. This case (EMBED = 0) is
only applicable if TPCMI is configured to operate at the line rate—2,048 kbps
E1, or 1,544 kbps T1. If transmit framing is disabled, the offline framer waits for
a reframe command [TFORCE; addr 071] before beginning a frame alignment
search.
Transmit Multiframe
Alignment
After the offline framer recovers frame alignment, the online framer monitors
TLOF and searches for mul tiframe alignment using criteria defined by the
Transmit Frame mode [TFRAME; addr 070]. The online framer conducts a
multiframe alignment search each time the of flin e framer recovers transmit frame
alignment—as reported by high-to-low transition of transmit loss of frame status
[TLOF; addr 048]. After TLOF recovery, th e onli ne f ramer sea rches c ontin uousl y
for multiframe alignm e nt until the correct pattern sequence is located, or until
basic frame alignment is lost (TLOF goes active-high). After multiframe
alignment recovery, the online framer checks subsequent multiframes for errored
alignment patterns, but does not use those errors as part of the criteria for loss of
basic frame alignment.
100054EConexant2-37
Page 96
2.0 Circuit DescriptionCX28394/28395/28398
2.3 System BusQuad/x16/Octal—T1/E1/J1 Framers
Note that the online framer's multiframe search status is not d ire ctly reported
to the processor, but instead is monitored by examination of transmit error status:
TMERR, TSERR, and TCERR [addr 00B]. If the system incorporates a certain
number of multiframe pattern errors (or a certain error ratio) into the loss of
transmit frame alignment criteria, the processor must count multiframe pattern
errors to determine when to force a transmit reframe [TFORCE; addr 071].
T ra nsmit Frame Alignment
Criteria
The frame synchronization criteria used by the offline framer is set in the
TFRAME[3:0] of the Transmit Framer Configuration register [TCR0; addr 070].
(Tables 3-15 and 3-16 illustrate sup po rted transmit framin g formats. Also, see
Tables 3-17 and 3-18, Criteria for Loss/Recovery of Transmit Frame Alignment.)
Transmit/Receive Framer
Arbitration
The offline framer is shared between the RCVR and XMTR and can only
search in one direction at a time. Consequently, the host processor can manually
arbitrate between RCVR and XMTR reframe requests by manipulating the
ABORT and FORCE controls, or by allowing the framer to automatically
arbitrate LOF requests.
The offline framer waits until the current search is complete [FSTAT;
addr 017] before checking for pending LOF reframe requests. If both online
framers have pending reframe requests, the offline framer aligns to the opposite
direction of that most recently searched. For example, if TLOF is pending at the
conclusion of a receive search which timed out without finding alignment, the
offline framer switches to search in the transmit direction. The TLOF switchover
is prevented in the preceding example if the processor asserts TABORT to mask
the transmit reframe request. T ABORT does not affect TLOF status reporting. For
applications that frame in only one direction, framing in the opposite direction
must be masked. If, at the conclusion of a receive search timeout, TLOF status is
asserted but masked by TABORT, the offline framer continues to search in the
receive direction.
For applications that frame in both directions, the processor can manually
arbitrate among pending reframe requests by controlling the reframe precedence.
An example of manual control follows:
1Initialize RABORT = 1 and TABORT = 1.
2Enable RLOF and TLOF interrupts.
3Read clear pending ISR interrupts.
4Release RABORT = 0.
5Call LOF Ser vice Routine if either RLOF or TLOF interrupt;
{
(check current LOF status (ALMI, 2; add r 047, 048)
If RLOF recovered and TLOF lost
—Assert RABORT = 1
—Release TABORT = 0
If RLOF lost or TLOF recovered
—Assert TABORT = 1
—Release RABORT = 0
}
2-38Conexant100054E
Page 97
CX28394/28395/283982.0 Circuit Description
Quad/x16/Octal—T1/E1/J1 Framers
Status register [F STAT; addr 017]. The register reports the f ollowing: whether the
offline framer is looking at the receive or transmit data streams (RX/TXN);
whether the framer is actively searc hing for frame a lignme nt (ACTIVE); whether
the framer found multiple framing candidates (TIMEOUT); whether the framer
found frame sync (FOUND); and whether the framer found no frame alignment
candidates (INVALID).
2.3.5.5 Embedded
Framing
Embedded framing mode [EMBED; addr 0D0] instructs the transmit framer to
search TSLIP buffer output (TNRZ) for framing bits while in T1 mode, or for
MFAS and CAS in E1 mode. Embedded framing allows the transmit timebase to
align with the transmit framer multiframe alignment of the PCM signal
transported across the system bus.
describes ho w 24 T1 time slo ts and framing bit (193 bits) are mapped to the 32 E1
time slots (256 bits): by leaving TS0 and TS16 unassigned; by storing the 24 T1
time slots in TS1 to T S1 5, and in TS17 to TS25 ; and by storing the frame bit in
Bit 1 of TS26 (see Figure 2-14, G.802 Embedded Framing).
2.3 System Bus
The status of the offline framer can be monitored using the Offline Framer
The Embedded mode supports ITU-T Recommendation G.802, which
100054EConexant2-39
Page 98
2.0 Circuit DescriptionCX28394/28395/28398
2.4 TransmitterQuad/x16/Octal—T1/E1/J1 Framers
2.4 Transmitter
The Transmitter (XMTR) insert s T1/E1 overhead data and outputs single rail
NRZ data from the TSB or ZCS-encoded P and N rail NRZ data. The CX28395
only provides single rail NRZ transmit signals.
The XMTR, Figure 2-20, consists of the following elements: two Transmit
Data Links, Test Pattern Generator, In-Band Loopback Code Generator , Overhead
Pattern Generator, Alarm Generator, Zero Code Suppression (ZCS) Encoder,
External Transmit Data Link (CX28394 and CX28398 only), CRC Generation,
Framing Pattern Insertion, and Far End Block Er ror Generator.
Figure 2-20. XMTR Diagram
TXCLK
TPOSO/TNRZO
TNEGO/MSYNCO
Line
Loopback
Framer
Loopback
AIS
Generator
ZCS
Encoder
TPDV Enforcer
Alarm/Error Insert
Transmitter
Timebase
Sa-Byte/BOP
PRBS/Inband LB
Data Link 1 Buffer
To TSBI
TNRZ
External DL3
Data Link 2 Buffer
T1/E1 Frame Insert
TDLI
TDLCKO
2-40Conexant100054E
Page 99
CX28394/28395/283982.0 Circuit Description
Quad/x16/Octal—T1/E1/J1 Framers
2.4.1 External Transmit Data Link (CX28394 and CX28398 Only)
The External Data Link (DL3) allows the system to externally supply an y bit( s) in
any time slot in al l frame s, odd frames or even frames, i ncludi ng T1 framing bi ts.
Pin access to the DL3 transmitter is provided t hrough TDLCKO and TDLI. These
two pins serve as the TDL3 clock output (TDLCKO) and data input (TDLI). The
mode of the pins is selected using the TDL_IO bi t in the Programmable
Input/Output register [PIO; addr 018].
Control of DL3 format is provided in two registers: External Data Link
Channel [DL3_TS; add 015] and External Data Link Bit [DL3_BIT; addr 016].
Transmit DL3 is set up by selecting the bit(s) [DL3_BIT], time slot [TS[4:0];
addr 015], and frames [EVEN/ODD; addr 015] to be overwritten, then enabling
the data link [DL3EN; addr 015]. Enabling the data link will start TDLCKO
gating the NRZ data provided on TDLI ( see Figure 2-21).
NOTE: DL3 signals are not provided on the CX28395. Therefore, DL3_TS must
be written to 00 to disable the DL3 transmitter and prevent transmit data
corruption.
Figure 2-21. Transmit External Data Link Waveforms
2.4 Transmitter
TDLCKO
TS8TS9TS10
TDLI
NOTE(S): This example shows bits 1, 2, 7, and 8 of TS9 selected. Any combination of time slot bits can b e selected.
1278
2.4.2 Transmit Data Links
The XMTR contains two independent data link controllers (DL1, DL2), a
Performance Report Message (PRM) generator, and a Bit-Oriented Protocol
(BOP) transceiver. DL1 and DL2 can be programmed to send and receive HDLC
formatted messages in the Message Oriented Protocol (MOP) mode or
unformatted serial data o v er an y combination of bit s within a sel ected t ime slot or
F-bit channel. The PRM message generator can immediately or automatically
send one-second performance reports. The BOP transceiver can preemptively
transmit BOP messages, such as ESF Yellow Alarm.
2.4.2.1 Data Link
Controllers
DL1 and DL2 control serial data channels operating at multiples of 4 kbps up to
the full 64 kbps time slot rate by selecting a combination of bits from odd, even,
or all frames. Both data link controllers support ESF Facilities Data Link (FDL),
SLC-96 data link, Sa data link, Common Channel Signaling (CCS), Signaling
System #7 (SS7), ISDN LAPD channels, Digital Multiplexed Interface (DMI)
signaling in TS24, as well as the latest ETSI V.51 and V.52 signaling channels.
DL1 and DL2 each contain a 64-byte transmit buffer which function either as
programmable length circular buffers in transparent (unformatted) mode, or as
full-length data FIFOs in formatted (HDLC) mo de.
100054EConexant2-41
Page 100
2.0 Circuit DescriptionCX28394/28395/28398
2.4 TransmitterQuad/x16/Octal—T1/E1/J1 Framers
DL1 and DL2 are configured identically, except for their offset in the register
map. The DL1 address range is 0A4 to 0AE, and the DL2 address range is 0AF to
0B9. From this point on, the DL1 is used to describe the operation of both data
link controllers. Transmit Data Link 1 (TDL1) can be viewed as having a higher
priority than Transmit Data Link 2 (T DL2) because TDL1 overwrites the primary
rate channel after TDL2 . Thus, any data that TDL2 writes to the primary rate
channel can be overwritten by TDL1, if TDL1 is configured to transmit in the
same time slot as TDL2.
The TDL1 is enabled using the DL1 Control register [DL1_CTL; addr 0A6].
TDL1 will not overwrite time slot data until it is enabled. DL1_CTL also controls
the data format and the circular buffer/FIFO mode.
The following data formats [DL1[1,0]; addr 0A6] are supported on the data
link: Frame Check Sequence (FCS), non-FCS, Pack8, or Pack6. FCS and
non-FCS are HDLC-formatted messages. Pack8 and Pack6 are unformatted
messages with 8 bits per FIFO access, and 6 bits per FIFO access, respectively.
2.4.2.2 Circular BufferThe Circular Buffer/FIFO control bit [TDL1_RPT; addr 0A6] allo ws the FIFO t o
act as a circular buffer; in this mode, a message can be transmitted repeatedly.
This feature is available on ly for unformatted transmit data link appli cat ions. T he
processor can repeatedly send fixed patterns on the selected channel by writing a
1- to 64-byte message into the circular buffer. The programmed message length
repeats until the processor writes a new message. The first byte of each
unformatted message is output automatically, aligned to the first frame of a
24-, or 16-frame transmit multiframe (SF/ESF/MFAS). This allows the processor
to source overhead or data elements aligned to the TX timebase. In both SF and
ESF T1 modes, unformatted messages are aligned on 24-frame boundaries.
Therefore, in SF applications t he repeati ng message must be design ed to span two
SF multiframes.
Each unformatted message written is output-aligned only after the preceding
message completes transmission. Theref ore, data continuity is retain ed during the
linkage of consecutive messages, provided that the contents of each message
consists of a multiple of th e mu ltiframe length.
2-42Conexant100054E
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.