DALLAS DS3134

PRELIMINARY
DS3134
Chateau – Channelized T1 And
E1 And HDLC Controller
www.dalsemi.com
FEATURES
•
•
•
•
•
•
•
•
•
•
256 Channel HDLC Controller that Supports
up to 64 T1 or E1 Lines or Two T3 Lines
256 Independent bi-directional HDLC
channels
16 physical ports (16 Tx & 16 Rx) that can
be configured as either channelized or
unchannelized
Two fast (52 Mbps) ports/other ports capable
of speeds up to 10 Mbps (unchannelized)
Channelized Ports 0 to 15 handle one, two or
four T1 or E1 lines
Supports up to 64 T1 or E1 data streams
Per channel DS0 loopbacks in both direction
Support transparent Mode
V.54 loopback code detector
Onboard Bit Error Rate Tester (BERT) with
auto error insertion capability
•
•
•
•
•
•
•
•
•
•
•
•
BERT function can be assigned to any
HDLC channel or any port
104 Mbps full duplex throughput
Large 16 kbits FIFO in both receive and
transmit directions
Efficient scatter / gather DMA
Receive data packets are Time stamped
Transmit packet priority setting
Local bus allows for PCI bridging or local
access
Intel or Motorola bus signals supported
25 MHz to 33 MHz 32-bit PCI (V2.1)
backplane interface
3.3V low power CMOS with 5V tolerant I/O
JTAG support IEEE 1149.1
256 Lead Plastic BGA (27 mm x 27 mm)
DESCRIPTION
The DS3134 Chateau device is a 256-channel HDLC controller. The DS3134 is capable of handling up to
64 T1 or E1 data streams or 2 T3 data streams. Each of the 16 physical ports can handle one, two or four
T1 or E1 data streams. The Chateau consists of the following blocks:
• Layer Block
• HDLC Block
• FIFO Block
• DMA Block
• PCI Bus
• Local Bus
1 of 203
101600
DS3134
There are 16 HDLC Engines (one for each port) that are capable of operating at speeds up to 8.192 Mbps
in channelized mode and up to 10 Mbps in unchannelized mode. There are also two Fast HDLC Engines,
which only reside on Ports 0 and 1 and they are capable of operating at speeds up to 52 Mbps.
Applications/Markets include:
•
•
•
•
•
•
•
•
•
•
Channelized T1/E1
Clear channel (unchannelized) T1/E1
Channelized T3/E3
Dual clear channel (unchannelized) T3/E3
High density Frame Relay access
xDSL (each port can support up to 10 Mbps)
Dual HSSI
V.35
SONET/SDH EOC/ECC Termination
Any applications require large number of HDLC channels
The device fully meets the following specifications: ANSI (American National Standards Institute)
T1.403-1995 Network-to-Customer Installation DS1 Metallic Interface March 21, 1995 and PCI Local
Bus Specification V2.1 June 1, 1995. ITU Q.921 March 1993 and ISO Standard 3309-1979 Data
Communications – HDLC Procedures – Frame Structure.
2 of 203
DS3134
REVISION HISTORY
Version 1 (1/30/98)
Original release.
Version 2 (4/4/98)
1. Assigned signals to leads (Section 2.1).
2. Added more information to Sections 1, 5, 7, and 10.
3. Removed the P3VEN signal pin (Section 2.1 and 2.5).
4. Added FIFO Priority Control bits to the MC register (Section 4.2).
5. Added Abort and Bit Stuffing Control bits to the RHCD and THCD registers (Section 6.2).
6. Changed the Absolute Maximum Voltage Rating and IOH numbers (Section 12).
7. Changed the Low Water Mark definition (Section 7.1).
8. Added Section 14 on Applications.
Version 3 (6/22/98)
1. Corrected JTRST* lead from V19 to U19 (Section 2.1).
2. Added TEST lead at C3 (Section 2.1).
3. Added the Valid Receive Done Queue Descriptor bit (Section 8.1.4).
4. Corrected JTAG Device Code from 0000614Ch to 00006143h (Section 11.3).
5. Changed the order of the TABTE & TZSD bits in the THCD Register (Section 6.2).
6. Added JTAG Scan Control Information into Table 11.4A (Section 11.4).
7. Added Minimum Grant & Maximum Latency Settings to PINTL0 (Section 9.2).
8. Remove the HDLC channel restriction that required channels 1 to 128 to be assigned to ports 0 to 7
and HDLC channels 129 to 256 to be assigned to port 8 to 15 (Sections 1, 5.1, 5.3 and 6.1).
Version 4 (11/18/98)
1. Added information about queues full and empty states (Sections 8.1.3, 8.1.4, 8.2.3, and 8.2.4).
2. Changed BERT ones and zeros detector from 32 consecutive to 31 consecutive (Section 5.6).
3. Changed BERT Bit and Error Counters to count during loss of receive synchronization (Section 5.6).
4. Corrected Table 1E (Section 1).
5. Added bit numbers to register descriptions.
6. Changed Local Bus Configuration Mode AC Timing Parameter A7 from 5ns to 40ns. (Section 12).
Version 5 (09/01/99)
1. Typos corrections and add clarifications.(Section 2.5, 3.5, 4.4, 5.3, 5.5, 5.6, 6.2, 7.1, 8.1.1, 8.2.3)
2. Change the number of T1/E1 support from 64 to 56 due to design over sight (Section 1)
3. Added clarifications for Receive High Water Mark and corrected Transmit Low Water Mark to a
value from 1 to smaller or equal to N –2, where N = the number of linked blocks.
4. Removed bit 1 of the RDMAQ register, this function is automatically implemented. Please refer to
section 8.1.3 (page 90)
5. Figure 10.3A signal LRD* is moved back one LCLK cycle to align with the rising edge of LCLK #1.
6. Figure 103B signal LWR* is moved back one LCLK cycle to align with the rising edge of LCLC #1.
3 of 203
DS3134
Version 6 (05/01/00) Rev B1/B2 silicon release
1. Typo correction on the following pages: 7, 53, 61, 80, 107, 114 and 115
2. Add (notes) clarifications on the following pages: 60, 63, 73, 76, 87, 88, 90, 93, 95, 110, 111 and 117
3. Update Layer 1 configuration restrictions for silicon Rev B1/B2 release, on page 10.
4. Update reset wait cycles on page 11.
5. Remove bit 1 form register RDMAQ on page 97.
6. Local Bus timing update, corrected t3 and t6 on page 169.
7. Change the number of T1/E1 support from 56 back to 64 (Section 1), this will be supported in the
next rev of silicon.
8. Added a product preview page.
Version 7 (09/15/00)
1. Update figure 9.1C.
2. Update figure 14C in Section 14.
3. Typo correction.
4 of 203
DS3134
TABLE OF CONTENTS
Section 1: Introduction……………………………………………………………………………………..7
Section 2: Signal Description……………………………………………………………………………
2.1 Overview / Signal Lead List…………………………………………………………………
2.2 Serial Port Interface Signal Description……………………………………………………
2.3 Local Bus Signal Description……………………………………………………………….
2.4 JTAG Signal Description……………………………………………………………………
2.5 PCI Bus Signal Description…………………………………………………………………
2.6 Supply & Test Signal Description…………………...……………………………………..
16
16
22
24
27
28
31
Section 3: Memory Map………………………………………………………………………………… 32
3.0 Introduction………………………………………………………………………………….. 32
3.1 General Configuration Registers………………………………………………………….. 32
3.2 Receive Port Registers…………………………………………………………………….. 33
3.3 Transmit Port Registers……………………………………………………………………. 33
3.4 Channelized Port Registers……………………………………………………………….. 34
3.5 HDLC Registers……………………………………………………………………………. 35
3.6 BERT Registers…………………………………………………………………………….. 35
3.7 Receive DMA Registers……………………………………………………………………. 35
3.8 Transmit DMA Registers…………………………………………………………………… 36
3.9 FIFO Registers……………………………………………………………………………… 36
3.10 PCI Configuration Registers for Function 0…………………………………………….
36
3.11 PCI Configuration Registers for Function 1…………………………………………….
37
Section 4: General Device Configuration & Status/Interrupt…………………………………………..
4.1 Master Reset & ID Register Description………………………………………………….
4.2 Master Configuration Register Description……………………………………………….
4.3 Status & Interrupt……………………………………………………………………………
4.3.1 Status & Interrupt General Description………………………………………
4.3.2 Status & Interrupt Register Description………………………………………
4.4 Test Register Description…………………………………………………………………..
37
37
38
40
40
43
50
Section 5: Layer One…………………………………………………………………………………… 51
5.1 General Description………………………………………………………………………… 51
5.2 Port Register Description………………………………………………………………….. 55
5.3 Layer One Configuration Register Description…………………………………………..
59
5.4 Receive V.54 Detector…………………………………………………………………….. 65
5.5 BERT…………………………………………………………………………………………69
5.6 BERT Register Description……………………………………………………………….. 70
Section 6: HDLC………………………………………………………………………………………… 77
6.1 General Description……………………………………………………………………….. 77
6.2 HDLC Register Description………………………………………………………………. 79
5 of 203
DS3134
Section 7: FIFO………………………………………………………………………………………… 85
7.1 General Description & Example…………………………………………………………. 85
7.2 FIFO Register Description………………………………………………………………..
87
Section 8: DMA………………………………………………………………………………………… 96
8.0 Introduction………………………………………………………………………………… 96
8.1 Receive Side………………………………………………………………………………. 97
8.1.1 Overview……………………………………………………………………….
97
8.1.2 Packet Descriptors…………………………………………………………….
103
8.1.3 Free Queue…………………………………………………………………….
105
8.1.4 Done Queue…………………………………………………………………… 110
8.1.5 DMA Configuration RAM…………………………………………………….. 116
8.2 Transmit Side………………………………………………………………………………. 120
8.2.1 Overview……………………………………………………………………….. 120
8.2.2 Packet Descriptors…………………………………………………………….
129
8.2.3 Pending Queue………………………………………………………………… 132
8.2.4 Done Queue……………………………………………………………………. 136
8.2.5 DMA Configuration RAM……………………………………………………… 142
Section 9: PCI Bus………………………………………………………………………………………147
9.1 PCI General Description…………………………………………………………………… 147
9.2 PCI Configuration Register Description………………………………………………….. 153
Section 10: Local Bus…………………………………………………………………………………
10.1 Local Bus General Description…………………………………………………………..
10.2 Local Bus Bridge Mode Control Register Description…………………………………
10.3 Examples of Bus Timing for Local Bus PCI Bridge Mode Operation………………..
165
165
171
173
Section 11: JTAG……………………………………………………………………………………… 181
11.1 JTAG Operation……………………………………………………………………………181
11.2 TAP Controller State Machine Description…………………………………………….. 181
11.3 Instruction Register and Instructions…………………………………………………… 184
11.4 Test Registers…………………………………………………………………………….. 185
Section 12: AC Characteristics………………………………………………………………………….191
Section 13: Mechanical Dimensions…………………………………………………………………….173
Section 14: Applications……………………………………………………………………………… 174
6 of 203
DS3134
SECTION 1: INTRODUCTION
The DS3134 Chateau device is a 256 channels HDLC controller. The primary features of the device are
listed in Table 1A. This data sheet is split in Sections along the major the blocks of the device as shown
in Figure 1A. Throughout the data sheet, certain terms will be used and these terms are defined in Table
1B. The DS3134 device is designed to meet certain specifications and a listing of these governing
specifications is shown in Table 1C.
DS3134 BLOCK DIAGRAM Figure 1A
Receive Direction
Transmit Direction
RC0
RD0
RS0
TC0
TD0
TS0
RC1
RD1
RS1
TC1
TD1
TS1
RC2
RD2
RS2
TC2
TD2
TS2
HDLC
Block
FIFO
Block
DMA
Block
PCI
Block
(Sec. 6)
(Sec. 7)
(Sec. 8)
(Sec. 9)
Layer
One
Block
PXAS*
PXDS*
PXBLAST*
(Sec. 5)
RC15
RD15
RS15
TC15
TD15
TS15
Local
Bus
Block
BERT
(Sec. 10)
(Sec. 5)
JTRST*
JTDI
JTMS
JTCLK
JTDO
PCLK
PRST*
PAD[31:0]
PCBE[3:0]*
PPAR
PFRAME*
PIRDY*
PTRDY*
PSTOP*
PIDSEL
PDEVSEL*
PREQ*
PGNT*
PPERR*
PSERR*
JTAG
Test
Access
(Sec. 11)
blockdia
7 of 203
LA[19:0]
LD[15:0]
LWR*(LR/W*)
LRD*(LDS*)
LIM
LINT*
LRDY*
LMS
LCS*
LHOLD(LBR*)
LHLDA(LBG*)
LBGACK*
LCLK
LBHE*
Pin Names in ( )
are active when
the device is in
the MOT mode
(i.e. LIM = 1)
DS3134
DS3134 FEATURE LIST Table 1A
Layer Can Support Up to 64 T1 or E1 Data Streams or Two T3 Data Streams
One 16 Independent Physical Ports all Capable of Speeds Up to 10 MHz
Two of These Ports are also Capable of Speeds Up to 52 MHz
Each Port can be Independently Configured for Either Channelized or Unchannelized Operation
Each Physical Channelized Port can Handle One, Two, or Four T1 or E1 Data Streams
Supports N x 64 kbps and N x 56 kbps
Onboard V.54 Loopback Detector
Onboard BERT Generation and Detection
Per DS0 Channel Loopback in Both Directions
Unchannelized Loopbacks in Both Directions
HDLC 256 Independent Channels
104 Mbps throughput in both the Receive and Transmit Directions
Transparent Mode
Two Fast HDLC Controllers Capable of Operating Up to 52 MHz
Automatic Flag Detection and Generation
Shared Opening and Closing Flag
Interfame Fill
Zero Stuffing and Destuffing
CRC16/32 Checking and Generation
Abort Detection and Generation
CRC Error and Long/Short Frame Error Detection
Bit Flip
Invert Data
FIFO Large 16 kB Receive and 16 kB Transmit Buffers Maximize PCI Bus Efficiency
Small Block Size of 16 Bytes Allows Maximum Flexibility
Programmable Low and High Water Marks
Programmable HDLC Channel Priority Setting
DMA Efficient Scatter-Gather DMA Minimizes PCI Bus Accesses
Programmable Small and Large Buffer Sizes Up to 8191 Bytes & Algorithm Select
Descriptor Bursting to Conserve PCI Bus Bandwidth
Programmable Packet Storage Address Offset
Identical Receive & Transmit Descriptors Minimize Host Processing in Store-and-Forward
Automatic Channel Disabling and Enabling on Transmit Errors
Receive Packets are Timestamped
Transmit Packet Priority Setting
PCI
Bus
32-Bit 33 MHz
Version 2.1 Compliant
Contains Extension Signals that Allow Adoption to Custom Buses
Can Burst Up to 256 32-Bit Words to Maximize Bus Efficiency
8 of 203
DS3134
Local Can Operate as a Bridge from the PCI Bus or a Configuration Bus
Bus In Bridge Mode; can arbitrate for the Bus
8 or 16 Bits Wide
In Bridge Mode, Supports a 1M Byte Address Space
Supports both Intel and Motorola Bus Timing
JTAG TEST ACCESS
3.3V LOW POWER CMOS WITH 5V TOLERANT INPUTS AND OUTPUTS
256 LEAD PLASTIC BGA PACKAGE (27 MM X 27 MM)
9 of 203
DS3134
DATA SHEET DEFINITIONS Table 1B
Acronym
Or Term
Definition
BERT
Descriptor
Dword
DMA
FIFO
HDLC
Host
n/a
V.54
Bit Error Rate Tester.
A message passed back and forth between the DMA and the Host.
Double Word. A 32-bit data entity.
Direct Memory Access.
First In First Out. Temporary memory storage scheme.
High level Data Link Control.
The main controller that resides on the PCI Bus.
Not Assigned.
A pseudorandom pattern used to control loopbacks (see ANSI T1.403)
GOVERNING SPECIFICATIONS Table 1C
ANSI (American National Standards Institute) T1.403-1995 Network-to-Customer Installation DS1
Metallic Interface March 21, 1995.
PCI Local Bus Specification V2.1 June 1, 1995.
GENERAL DESCRIPTION
The Layer One Block handles the physical input and output of serial data to and from the DS3134. The
DS3134 is capable of handling up to 64 T1 or E1 data streams or 2 T3 data streams. Each of the 16
physical ports can handle up to two or four T1 or E1 data streams. Section 14 contains some examples of
how this is performed. The Layer One Block prepares the incoming data for the HDLC Block and grooms
data from the HDLC Block for transmission. The block has the ability to perform both channelized and
unchannelized loopbacks as well as search for V.54 loop patterns. It is in the Layer One Block that the
Host will enable HDLC channels and assign them to a particular port and/or DS0 channel(s). The Host
assigns HDLC channels via the R[n]CFG[j] and T[n]CFG[j] registers, which are described in Section 5.3.
The Layer One Block interfaces directly to the Bit Error Rate Tester (BERT) Block. The BERT Block
can generate and detect both pseudorandom and repeating bit patterns and it is used to test and stress data
communication links.
The HDLC Block consists of two types of HDLC controllers. There are 16 Slow HDLC Engines (one for
each port) that are capable of operating at speeds up to 8.192 Mbps in channelized mode and up to
10 Mbps in unchannelized mode. There are also two Fast HDLC Engines, which only reside on Ports 0
and 1 and they are capable of operating at speeds up to 52 Mbps. Via the RP[n]CR and TP[n]CR
registers in the Layer One Block, the Host will configure Port 0 and 1 to use either the Slow or the Fast
HDLC engine. The HDLC Engines perform all of the Layer 2 processing which include, zero stuffing
and destuffing, flag generation and detection, CRC generation and checking, abort generation and
checking.
10 of 203
DS3134
In the receive path, the following process occurs. The HDLC Engines collect the incoming data into
32-bit dwords and then signal the FIFO that the engine has data to transfer to the FIFO. The 16 ports are
priority decoded (Port 0 gets the highest priority) for the transfer of data from the HDLC Engines to the
FIFO Block. Please note that in a channelized application, a single port may contain up to 128 HDLC
channels and since HDLC channel numbers can be assigned randomly, the HDLC channel number has no
bearing on the priority of this data transfer. This situation is of no real concern however since the
DS3134 has been designed to handle up to 104 Mbps in both the receive and transmit directions without
any potential loss of data due to priority conflicts in the transfer of data from the HDLC Engines to the
FIFO and vice versa.
The FIFO transfers data from the HDLC Engines into the FIFO and checks to see if the FIFO has filled to
beyond the programmable High Water Mark. If it has, then the FIFO signals to the DMA that data is
ready to be burst read from the FIFO to the PCI Bus. The FIFO Block controls the DMA Block and it
tells the DMA when to transfer data from the FIFO to the PCI Bus. Since the DS3134 can handle
multiple HDLC channels, it is quite possible that at any one time, several HDLC channels will need to
have data transferred from the FIFO to the PCI Bus. The FIFO determines which HDLC channel the
DMA will handle next via a Host configurable algorithm, which allows the selection to be either round
robin or priority, decoded (with HDLC Channel 1 getting the highest priority). Depending on the
application, the selection of this algorithm can be quite important. The DS3134 cannot control when it
will be granted PCI Bus access and if bus access is restricted, then the Host may wish to prioritize which
HDLC channels get top priority access to the PCI Bus when it is granted to the DS3134.
When the DMA transfers data from the FIFO to the PCI Bus, it burst reads all available data in the FIFO
(even if the FIFO contains multiple HDLC packets) and tries to empty the FIFO. If an incoming HDLC
packet is not large enough to fill the FIFO to the High Water Mark, then the FIFO will not wait for more
data to enter the FIFO, it will signal the DMA that a End Of Frame (EOF) was detected and that data is
ready to be transferred from the FIFO to the PCI Bus by the DMA.
In the transmit path, a very similar process occurs. As soon as a HDLC channel is enabled, the HDLC
(Layer 2) Engines begin requesting data from the FIFO. Like the receive side, the 16 ports are priority
decoded with Port 0 getting the highest priority. Hence, if multiple ports are requesting packet data, the
FIFO will first satisfy the requirements on all the enabled HDLC channels in the lower numbered ports
before moving on to the higher numbered ports. Again there is no potential loss of data as long as the
transmit throughput maximum of 104 Mbps is not exceeded. When the FIFO detects that a HDLC Engine
needs data, it then transfers the data from the FIFO to the HDLC Engines in 8-bit chunks. If the FIFO
detects that the FIFO is below the Low Water Mark, it then checks with the DMA to see if there is any
data available for that HDLC Channel. The DMA will know if any data is available because the Host on
the PCI Bus will have informed it of such via the Pending Queue Descriptor. When the DMA detects that
data is available, it informs the FIFO and then the FIFO decides which HDLC channel gets the highest
priority to the DMA to transfer data from the PCI Bus into the FIFO. Again, since the DS3134 can handle
multiple HDLC channels, it is quite possible that at any one time, several HDLC channels will need the
DMA to burst data from the PCI Bus into the FIFO. The FIFO determines which HDLC channel the
DMA will handle next via a Host configurable algorithm, which allows the selection to be either round
robin or priority, decoded (with HDLC Channel 1 getting the highest priority).
11 of 203
DS3134
When the DMA begins burst writing data into the FIFO, it will try to completely fill the FIFO with HDLC
packet data even if it that means writing multiple packets. Once the FIFO detects that the DMA has filled
it to beyond the Low Water Mark (or an EOF is reached), the FIFO will begin transferring 32-bit dwords
to the HDLC Engine.
One of the unique attributes of the DS3134 is the structure of the DMA. The DMA has been optimized to
maintain maximum flexibility yet reduce the number of bus cycles required to transfer packet data. The
DMA uses a flexible scatter/gather technique, which allows that packet data to be place anywhere within
the 32-bit address space. The user has the option on the receive side of two different buffer sizes which
are called “large” and “small” but that can be set to any size up to 8191 bytes. The user has the option to
store the incoming data either, only in the large buffers, only in the small buffers, or fill a small buffer
first and then fill large buffers as needed. The varying buffer storage options allow the user to make the
best use of the available memory and to be able to balance the tradeoff between latency and bus
utilization.
The DMA uses a set of descriptors to know where to store the incoming HDLC packet data and where to
obtain HDLC packet data that is ready to be transmitted. The descriptors are fixed size messages that are
handed back and forth from the DMA to the Host. Since this descriptor transfer utilizes bus cycles, the
DMA has been structured to minimize the number of transfers required. For example on the receive side,
the DMA obtains descriptors from the Host to know where in the 32-bit address space to place the
incoming packet data. These descriptors are known as Free Queue Descriptors. When the DMA reads
these descriptors off of the PCI Bus, they contain all the information that the DMA needs to know where
to store the incoming data. Unlike other existing scatter/gather DMA architectures, the DS3134 DMA
does not need to use any more bus cycles to determine where to place the data. Other DMA architectures
tend to use pointers, which require them to go back onto the bus to obtain more information and hence
use more bus cycles.
Another technique that the DMA uses to maximize bus utilization is the ability to burst read and writes
the descriptors. The device can be enabled to read and write the descriptors in bursts of 8 or 16 instead of
one at a time. Since there is fixed overhead associated with each bus transaction, the ability to burst read
and write descriptors allows the device to share the bus overhead among 8 or 16 descriptor transactions
which reduces the total number of bus cycles needed.
The DMA can also burst up to 256 dwords (1024 bytes) onto the PCI Bus. This helps to minimize bus
cycles by allowing the device to burst large amounts of data in a smaller number of bus transactions
which reduces bus cycles by reducing the amount of fixed overhead that is placed on the bus.
The Local Bus Block has two modes of operation. It can be used as either a Bridge from the PCI Bus in
which case it is a bus master or it can be used as a Configuration Bus in which case it is a bus slave. The
Bridge Mode allows the Host on the PCI Bus to access the local bus. The DS3134 will map data from the
PCI Bus to the local bus. In the Configuration Mode, the local bus is used only to control and monitor the
DS3134 while the HDLC packet data will still be transferred to the Host via the PCI Bus.
Restrictions
In creating the overall system architecture, the user must balance the port, throughput, and HDLC channel
restrictions of the DS3134. Table 1D lists all of the upper bound maximum restrictions on the DS3134.
12 of 203
DS3134
DS3134 RESTRICTIONS FOR REV B1/B2 SILICON Table 1D
Port
maximum of 16 channelized and unchannelized physical ports
Unchannelized
ports 0 & 1: maximum data rate of 52 Mbps
port 2 to 15: maximum data rate of 10 Mbps
Channelized
Channelized and with frame interleave interfaces or a minimum of
two/multiple of two consecutive DS0 time slot assigned to one
HDLC channel:
40 T1/E1 channels
Channelized
Channelized and with byte interleave interfaces:
32 T1/E1 channels
Throughput
maximum receive: 104 Mbps
maximum transmit: 104 Mbps
HDLC
maximum of 256 channels
if the Fast HDLC Engine on Port 0 is being used, then it must be
HDLC Channel 1*
if the Fast HDLC Engine on Port 1 is being used, then it must be
HDLC Channel 2*
* The 256 HDLC channels within the device are numbered from 1 to 256.
INTERNAL DEVICE CONFIGURATION REGISTERS
All of the internal device configuration registers (with the exception of the PCI Configuration Registers
which are 32-bit registers) are 16 bits wide and they are not byte addressable. When the Host on the PCI
Bus accesses these registers, the particular combination of byte enables (i.e. PCBE* signals) is not
important but at least one of the byte enables must be asserted for a transaction to occur. All the registers
are read/write registers unless otherwise noted. Not assigned bits (identified as n/a in the data sheet)
should be set to zero when written to allow for future upgrades to the device. These bits have no meaning
and could be either zero or one when read.
13 of 203
DS3134
INITIALIZATION
On a system reset (which can be invoked by either hardware action via the PRST* signal or software
action via the RST control bit in the Master Reset and ID register), all of the internal device configuration
register are set to zero (0000h). Please note that the Local Bus Bridge Mode Control register (LBBMC) is
not affected by software invoked system reset, it will be forced to all zeros only by hardware reset. The
internal registers within that are accessed indirectly (these are listed as "indirect registers" in the data
sheet and consist of the Channelized Port registers in the Layer One Block, the DMA Configuration
RAMs, the HDLC Configuration registers, and the FIFO registers) are not affected by a system reset and
they must be configured on power-up by the Host to a proper state. Figure 1B lists the ordered steps to
initialize the DS3134.
Note:
After device power up and reset, it takes 0.625 mS to get a port up and operating. In other words, the
ports must have wait a minimum of 0.625 mS before packet data can be processed.
INITIALIZATION STEPS Figure 1B
Initialization Step
Comments
1. Initialize the PCI Configuration
Registers
Achieved by asserting the PIDSEL signal.
2. Initialize All Indirect Registers
It is recommended that all of the indirect
registers be set to 0000h. See Table 1E.
3. Configure the Device for Operation
Program all the necessary registers, which
includes the Layer One, HDLC, FIFO, and
DMA registers.
4. Enable the HDLC Channels
Done via the RCHEN and TCHEN bits in
the R[n]CFG[j] and T[n]CFG[j] registers.
5. Load the DMA Descriptors
Indicate to the DMA where packet data can
be written and where pending data (if any)
resides
6. Enable the DMAs
Done via the RDE and TDE control bits in
the Master Configuration (MC) register.
7. Enable DMA for each HDLC Channel
Done via the Channel Enable bit in the
Receive & Transmit Configuration RAM
14 of 203
DS3134
INDIRECT REGISTERS Table 1E
Register Name (Acronym)
Channelized Port registers (CP0RD to CP15RD)
Number of Indirect Registers
6144 (16 Ports x 128 DS0 Channels x 3
Registers for each DS0 Channel)
Receive HDLC Channel Definition register (RHCD)
256 (one for each HDLC Channel)
Transmit HDLC Channel Definition register (THCD)
256 (one for each HDLC Channel)
Receive DMA Configuration register (RDMAC)
1536 (one for each HDLC Channel)
Transmit DMA Configuration register (TDMAC)
3072 (one for each HDLC Channel)
Receive FIFO Staring Block Pointer register (RFSBP)
256 (one for each HDLC Channel)
Receive FIFO Block Pointer register (RFBP)
1024 (one for each FIFO Block)
Receive FIFO High Water Mark register (RFHWM)
256 (one for each HDLC Channel)
Transmit FIFO Staring Block Pointer register (TFSBP)
256 (one for each HDLC Channel)
Transmit FIFO Block Pointer register (TFBP)
1024 (one for each FIFO Block)
Transmit FIFO Low Water Mark register (TFLWM)
256 (one for each HDLC Channel)
15 of 203
DS3134
SECTION 2: SIGNAL DESCRIPTION
2.1 OVERVIEW / SIGNAL LEAD LIST
This section describes the input and output signals on the DS3134. Signal names follow a convention that
is shown in Table 2.1A. Table 2.1B lists all of the signals, their signal type, description, and lead
location.
Signal Naming Convention Table 2.1A
First Letter
R
T
L
J
P
Signal Category
Receive Serial Port
Transmit Serial Port
Local Bus
JTAG Test Port
PCI Bus
Section
2.2
2.2
2.3
2.4
2.5
Signal Description / Lead List (sorted by symbol) Table 2.1B
Lead
V19
U18
T17
W20
U19
G20
G19
F20
G18
F19
E20
G17
F18
E19
D20
E18
D19
C20
E17
D18
C19
B20
C18
B19
A20
L20
H20
J20
Symbol
JTCLK
JTDI
JTDO
JTMS
JTRST*
LA0
LA1
LA2
LA3
LA4
LA5
LA6
LA7
LA8
LA9
LA10
LA11
LA12
LA13
LA14
LA15
LA16
LA17
LA18
LA19
LBGACK*
LBHE*
LCLK
Type
I
I
O
I
I
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
O
O
O
Signal Description
JTAG IEEE 1149.1 Test Serial Clock.
JTAG IEEE 1149.1 Test Serial Data Input.
JTAG IEEE 1149.1 Test Serial Data Output.
JTAG IEEE 1149.1 Test Mode Select.
JTAG IEEE 1149.1 Test Reset.
Local Bus Address Bit 0. LSB.
Local Bus Address Bit 1.
Local Bus Address Bit 2.
Local Bus Address Bit 3.
Local Bus Address Bit 4.
Local Bus Address Bit 5.
Local Bus Address Bit 6.
Local Bus Address Bit 7.
Local Bus Address Bit 8.
Local Bus Address Bit 9.
Local Bus Address Bit 10.
Local Bus Address Bit 11.
Local Bus Address Bit 12.
Local Bus Address Bit 13.
Local Bus Address Bit 14.
Local Bus Address Bit 15.
Local Bus Address Bit 16.
Local Bus Address Bit 17.
Local Bus Address Bit 18.
Local Bus Address Bit 19. MSB.
Local Bus Grant Acknowledge.
Local Bus Byte High Enable.
Local Bus Clock.
16 of 203
DS3134
Lead
K19
V20
U20
T18
T19
T20
R18
P17
R19
R20
P18
P19
P20
N18
N19
N20
M17
L18
L19
M18
K20
M19
H18
K18
H19
A2
A8
A11
A19
B2
B18
J18
J19
K1
K2
K3
L1
L2
L3
M20
U14
W2
W9
Y1
Y19
Symbol
LCS*
LD0
LD1
LD2
LD3
LD4
LD5
LD6
LD7
LD8
LD9
LD10
LD11
LD12
LD13
LD14
LD15
LHLDA(LBG*)
LHOLD(LBR*)
LIM
LINT*
LMS
LRD*(LDS*)
LRDY*
LWR*(LR/W*)
NC
NC
NC
NC
NC
NC
NC
NC
NC
NC
NC
NC
NC
NC
NC
NC
NC
NC
NC
NC
Type
I
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I
O
I
I/O
I
I/O
I
I/O
-
Signal Description
Local Bus Chip Select.
Local Bus Data Bit 0. LSB.
Local Bus Data Bit 1.
Local Bus Data Bit 2.
Local Bus Data Bit 3.
Local Bus Data Bit 4.
Local Bus Data Bit 5.
Local Bus Data Bit 6.
Local Bus Data Bit 7.
Local Bus Data Bit 8.
Local Bus Data Bit 9.
Local Bus Data Bit 10.
Local Bus Data Bit 11.
Local Bus Data Bit 12.
Local Bus Data Bit 13.
Local Bus Data Bit 14.
Local Bus Data Bit 15. MSB.
Local Bus Hold Acknowledge (Local Bus Grant).
Local Bus Hold (Local Bus Request).
Local Bus Intel/Motorola Bus Select.
Local Bus Interrupt.
Local Bus Mode Select.
Local Bus Read Enable (Local Bus Data Strobe).
Local Bus PCI Bridge Ready.
Local Bus Write Enable ( Local Bus Read/Write Select).
No Connect. Do not connect any signal to this lead.
No Connect. Do not connect any signal to this lead.
No Connect. Do not connect any signal to this lead.
No Connect. Do not connect any signal to this lead.
No Connect. Do not connect any signal to this lead.
No Connect. Do not connect any signal to this lead.
No Connect. Do not connect any signal to this lead.
No Connect. Do not connect any signal to this lead.
No Connect. Do not connect any signal to this lead.
No Connect. Do not connect any signal to this lead.
No Connect. Do not connect any signal to this lead.
No Connect. Do not connect any signal to this lead.
No Connect. Do not connect any signal to this lead.
No Connect. Do not connect any signal to this lead.
No Connect. Do not connect any signal to this lead.
No Connect. Do not connect any signal to this lead.
No Connect. Do not connect any signal to this lead.
No Connect. Do not connect any signal to this lead.
No Connect. Do not connect any signal to this lead.
No Connect. Do not connect any signal to this lead.
17 of 203
DS3134
Lead
V17
U16
Y18
W17
V16
Y17
W16
V15
W15
V14
Y15
W14
Y14
V13
W13
Y13
V9
U9
Y8
W8
V8
Y7
W7
V7
U7
V6
Y5
W5
V5
Y4
Y3
U5
Y16
V12
Y9
W6
Y2
Symbol
PAD0
PAD1
PAD2
PAD3
PAD4
PAD5
PAD6
PAD7
PAD8
PAD9
PAD10
PAD11
PAD12
PAD13
PAD14
PAD15
PAD16
PAD17
PAD18
PAD19
PAD20
PAD21
PAD22
PAD23
PAD24
PAD25
PAD26
PAD27
PAD28
PAD29
PAD30
PAD31
PCBE0*
PCBE1*
PCBE2*
PCBE3*
PCLK
Type
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I
Y11
W10
W4
Y6
W18
V10
W12
PDEVSEL*
PFRAME*
PGNT*
PIDSEL
PINT*
PIRDY*
PPAR
I/O
I/O
I
I
O
I/O
I/O
Signal Description
PCI Multiplexed Address & Data Bit 0.
PCI Multiplexed Address & Data Bit 1.
PCI Multiplexed Address & Data Bit 2.
PCI Multiplexed Address & Data Bit 3.
PCI Multiplexed Address & Data Bit 4.
PCI Multiplexed Address & Data Bit 5.
PCI Multiplexed Address & Data Bit 6.
PCI Multiplexed Address & Data Bit 7.
PCI Multiplexed Address & Data Bit 8.
PCI Multiplexed Address & Data Bit 9.
PCI Multiplexed Address & Data Bit 10.
PCI Multiplexed Address & Data Bit 11.
PCI Multiplexed Address & Data Bit 12.
PCI Multiplexed Address & Data Bit 13.
PCI Multiplexed Address & Data Bit 14.
PCI Multiplexed Address & Data Bit 15.
PCI Multiplexed Address & Data Bit 16.
PCI Multiplexed Address & Data Bit 17.
PCI Multiplexed Address & Data Bit 18.
PCI Multiplexed Address & Data Bit 19.
PCI Multiplexed Address & Data Bit 20.
PCI Multiplexed Address & Data Bit 21.
PCI Multiplexed Address & Data Bit 22.
PCI Multiplexed Address & Data Bit 23.
PCI Multiplexed Address & Data Bit 24.
PCI Multiplexed Address & Data Bit 25.
PCI Multiplexed Address & Data Bit 26.
PCI Multiplexed Address & Data Bit 27.
PCI Multiplexed Address & Data Bit 28.
PCI Multiplexed Address & Data Bit 29.
PCI Multiplexed Address & Data Bit 30.
PCI Multiplexed Address & Data Bit 31.
PCI Bus Command / Byte Enable Bit 0.
PCI Bus Command / Byte Enable Bit 1.
PCI Bus Command / Byte Enable Bit 2.
PCI Bus Command / Byte Enable Bit 3.
PCI & System Clock. A 25MHz to 33 MHz clock is applied
here.
PCI Device Select.
PCI Cycle Frame.
PCI Bus Grant.
PCI Initialization Device Select.
PCI Interrupt.
PCI Initiator Ready.
PCI Bus Parity.
18 of 203
DS3134
Lead
V11
V4
W3
Y12
W11
Y10
V18
Y20
W19
B1
D1
F2
H2
M1
P1
P4
V1
B17
B16
C14
D12
A10
B8
B6
C5
D2
E2
G3
J4
M3
R1
T2
U3
D16
C15
A14
B12
C10
A7
D7
A3
C2
E3
F1
H1
Symbol
PPERR*
PREQ*
PRST*
PSERR*
PSTOP*
PTRDY*
PXAS*
PXBLAST*
PXDS*
RC0
RC1
RC2
RC3
RC4
RC5
RC6
RC7
RC8
RC9
RC10
RC11
RC12
RC13
RC14
RC15
RD0
RD1
RD2
RD3
RD4
RD5
RD6
RD7
RD8
RD9
RD10
RD11
RD12
RD13
RD14
RD15
RS0
RS1
RS2
RS3
Type
I/O
O
I
O
I/O
I/O
O
O
O
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
Signal Description
PCI Parity Error.
PCI Bus Request.
PCI Reset.
PCI System Error.
PCI Stop.
PCI Target Ready.
PCI Extension Signal: Address Strobe.
PCI Extension Signal: Burst Last.
PCI Extension Signal: Data Strobe.
Receive Serial Clock for Port 0.
Receive Serial Clock for Port 1.
Receive Serial Clock for Port 2.
Receive Serial Clock for Port 3.
Receive Serial Clock for Port 4.
Receive Serial Clock for Port 5.
Receive Serial Clock for Port 6.
Receive Serial Clock for Port 7.
Receive Serial Clock for Port 8.
Receive Serial Clock for Port 9.
Receive Serial Clock for Port 10.
Receive Serial Clock for Port 11.
Receive Serial Clock for Port 12.
Receive Serial Clock for Port 13.
Receive Serial Clock for Port 14.
Receive Serial Clock for Port 15.
Receive Serial Data for Port 0.
Receive Serial Data for Port 1.
Receive Serial Data for Port 2.
Receive Serial Data for Port 3.
Receive Serial Data for Port 4.
Receive Serial Data for Port 5.
Receive Serial Data for Port 6.
Receive Serial Data for Port 7.
Receive Serial Data for Port 8.
Receive Serial Data for Port 9.
Receive Serial Data for Port 10.
Receive Serial Data for Port 11.
Receive Serial Data for Port 12.
Receive Serial Data for Port 13.
Receive Serial Data for Port 14.
Receive Serial Data for Port 15.
Receive Serial Sync for Port 0.
Receive Serial Sync for Port 1.
Receive Serial Sync for Port 2.
Receive Serial Sync for Port 3.
19 of 203
DS3134
Lead
M2
P2
R3
T4
C17
A16
B14
C12
B10
C8
A5
B4
D3
E1
G2
J3
N1
P3
U1
V2
A18
D14
C13
A12
A9
B7
C6
D5
C1
G4
H3
J1
N3
T1
U2
V3
C16
A15
A13
C11
C9
C7
A4
B3
C3
Symbol
RS4
RS5
RS6
RS7
RS8
RS9
RS10
RS11
RS12
RS13
RS14
RS15
TC0
TC1
TC2
TC3
TC4
TC5
TC6
TC7
TC8
TC9
TC10
TC11
TC12
TC13
TC14
TC15
TD0
TD1
TD2
TD3
TD4
TD5
TD6
TD7
TD8
TD9
TD10
TD11
TD12
TD13
TD14
TD15
TEST
Type
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
I
Signal Description
Receive Serial Sync for Port 4.
Receive Serial Sync for Port 5.
Receive Serial Sync for Port 6.
Receive Serial Sync for Port 7.
Receive Serial Sync for Port 8.
Receive Serial Sync for Port 9.
Receive Serial Sync for Port 10.
Receive Serial Sync for Port 11.
Receive Serial Sync for Port 12.
Receive Serial Sync for Port 13.
Receive Serial Sync for Port 14.
Receive Serial Sync for Port 15.
Transmit Serial Clock for Port 0.
Transmit Serial Clock for Port 1.
Transmit Serial Clock for Port 2.
Transmit Serial Clock for Port 3.
Transmit Serial Clock for Port 4.
Transmit Serial Clock for Port 5.
Transmit Serial Clock for Port 6.
Transmit Serial Clock for Port 7.
Transmit Serial Clock for Port 8.
Transmit Serial Clock for Port 9.
Transmit Serial Clock for Port 10.
Transmit Serial Clock for Port 11.
Transmit Serial Clock for Port 12.
Transmit Serial Clock for Port 13.
Transmit Serial Clock for Port 14.
Transmit Serial Clock for Port 15.
Transmit Serial Data for Port 0.
Transmit Serial Data for Port 1.
Transmit Serial Data for Port 2.
Transmit Serial Data for Port 3.
Transmit Serial Data for Port 4.
Transmit Serial Data for Port 5.
Transmit Serial Data for Port 6.
Transmit Serial Data for Port 7.
Transmit Serial Data for Port 8.
Transmit Serial Data for Port 9.
Transmit Serial Data for Port 10.
Transmit Serial Data for Port 11.
Transmit Serial Data for Port 12.
Transmit Serial Data for Port 13.
Transmit Serial Data for Port 14.
Transmit Serial Data for Port 15.
Test. Factory tests signal; leave open circuited.
20 of 203
DS3134
Lead
E4
F3
G1
J2
N2
R2
T3
W1
A17
B15
B13
B11
B9
A6
B5
C4
D6
D10
D11
D15
F4
F17
K4
K17
L4
L17
R4
R17
U6
U10
U11
U15
A1
D4
D8
D9
D13
D17
H4
H17
J17
M4
N4
N17
U4
Symbol
TS0
TS1
TS2
TS3
TS4
TS5
TS6
TS7
TS8
TS9
TS10
TS11
TS12
TS13
TS14
TS15
VDD
VDD
VDD
VDD
VDD
VDD
VDD
VDD
VDD
VDD
VDD
VDD
VDD
VDD
VDD
VDD
VSS
VSS
VSS
VSS
VSS
VSS
VSS
VSS
VSS
VSS
VSS
VSS
VSS
Type
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
-
Signal Description
Transmit Serial Sync for Port 0.
Transmit Serial Sync for Port 1.
Transmit Serial Sync for Port 2.
Transmit Serial Sync for Port 3.
Transmit Serial Sync for Port 4.
Transmit Serial Sync for Port 5.
Transmit Serial Sync for Port 6.
Transmit Serial Sync for Port 7.
Transmit Serial Sync for Port 8.
Transmit Serial Sync for Port 9.
Transmit Serial Sync for Port 10.
Transmit Serial Sync for Port 11.
Transmit Serial Sync for Port 12.
Transmit Serial Sync for Port 13.
Transmit Serial Sync for Port 14.
Transmit Serial Sync for Port 15.
Positive Supply. 3.3V (+/- 10%).
Positive Supply. 3.3V (+/- 10%).
Positive Supply. 3.3V (+/- 10%).
Positive Supply. 3.3V (+/- 10%).
Positive Supply. 3.3V (+/- 10%).
Positive Supply. 3.3V (+/- 10%).
Positive Supply. 3.3V (+/- 10%).
Positive Supply. 3.3V (+/- 10%).
Positive Supply. 3.3V (+/- 10%).
Positive Supply. 3.3V (+/- 10%).
Positive Supply. 3.3V (+/- 10%).
Positive Supply. 3.3V (+/- 10%).
Positive Supply. 3.3V (+/- 10%).
Positive Supply. 3.3V (+/- 10%).
Positive Supply. 3.3V (+/- 10%).
Positive Supply. 3.3V (+/- 10%).
Ground Reference.
Ground Reference.
Ground Reference.
Ground Reference.
Ground Reference.
Ground Reference.
Ground Reference.
Ground Reference.
Ground Reference.
Ground Reference.
Ground Reference.
Ground Reference.
Ground Reference.
21 of 203
DS3134
Lead
U8
U12
U13
U17
Symbol
VSS
VSS
VSS
VSS
Type
-
Signal Description
Ground Reference.
Ground Reference.
Ground Reference.
Ground Reference.
2.2 SERIAL PORT INTERFACE SIGNAL DESCRIPTION
Signal Name:
RC0 / RC1 / RC2 / RC3 / RC4 / RC5 / RC6 / RC7 / RC8 / RC9 / RC10 / RC11 /
RC12 / RC13 / RC14 / RC15
Signal Description: Receive Serial Clock
Signal Type:
Input
Data can be clocked into the device either on falling edges (normal clock mode) or rising edges (inverted
clock mode) of RC. This is programmable on a per port basis. RC0 & RC1 can operate at speeds up to
52 MHz. RC2 to RC15 can operate at speeds up to 10 MHz. If not used, should be tied low.
Signal Name:
RD0 / RD1 / RD2 / RD3 / RD4 / RD5 / RD6 / RD7 / RD8 / RD9 / RD10 / RD11 /
RD12 / RD13 / RD14 / RD15
Signal Description: Receive Serial Data
Signal Type:
Input
Can be sampled either on the falling edge of RC (normal clock mode) or the rising edge of RC (inverted
clock mode). If not used, should be tied low.
Signal Name:
RS0 / RS1 / RS2 / RS3 / RS4 / RS5 / RS6 / RS7 / RS8 / RS9 / RS10 / RS11 /
RS12 / RS13 / RS14 / RS15
Signal Description: Receive Serial Data Synchronization Pulse
Signal Type:
Input
A one RC clock wide synchronization pulse that can be applied to the Chateau to force byte/frame
alignment. The applied sync signal pulse can be either active high (normal sync mode) or active low
(inverted sync mode). The RS signal can be sampled either on the falling edge or on rising edge of RC
(see Table 2.2A below for details). The applied sync pulse can be during the first RC clock period of a
193/256/512/1024 bit frame or it can be applied 1/2, 1, or 2 RC clocks early. This input sync signal resets
a counter that rolls over at a count of either 193 (T1 mode) or 256 (E1 mode) or 512 (4.096 MHz mode)
or 1024 (8.192 MHz mode) RC clocks. It is acceptable to only pulse the RS signal once to establish byte
boundaries and allow Chateau to keep track of the byte/frame boundaries by counting RC clocks. If the
incoming data does not require alignment to byte/frame boundaries, then this signal should be tied low.
22 of 203
DS3134
RS SAMPLED EDGE Table 2.2A
0 RC Clock Early Mode
1/2 RC Clock Early Mode
1 RC Clock Early Mode
2 RC Clock Early Mode
Normal RC Clock Mode
Inverted RC Clock Mode
falling edge
rising edge
falling edge
falling edge
rising edge
falling edge
rising edge
rising edge
Signal Name:
TC0 / TC1 / TC2 / TC3 / TC4 / TC5 / TC6 / TC7 / TC8 / TC9 / TC10 / TC11 /
TC12 / TC13 / TC14 / TC15
Signal Description: Transmit Serial Clock
Signal Type:
Input
Data can be clocked out of the device either on rising edges (normal clock mode) or falling edges
(inverted clock mode) of TC. This is programmable on a per port basis. TC0 & TC1 can operate at
speeds up to 52 MHz. TC2 to TC15 can operate at speeds up to 10 MHz. If not used, should be tied low.
Signal Name:
TD0 / TD1 / TD2 / TD3 / TD4 / TD5 / TD6 / TD7 / TD8 / TD9 / TD10 / TD11 /
TD12 / TD13 / TD14 / TD15
Signal Description: Transmit Serial Data
Signal Type:
Output
Can be updated either on the rising edge of TC (normal clock mode) or the falling edge of TC (inverted
clock mode). Data can be forced high.
Signal Name:
TS0 / TS1 / TS2 / TS3 / TS4 / TS5 / TS6 / TS7 / TS8 / TS9 / TS10 / TS11 /
TS12 / TS13 / TS14 / TS15
Signal Description: Transmit Serial Data Synchronization Pulse
Signal Type:
Input
A one TC clock wide synchronization pulse that can be applied to the Chateau to force byte/frame
alignment. The applied sync signal pulse can be either active high (normal sync mode) or active low
(inverted sync mode). The TS signal can be sampled either on the falling edge or on rising edge of TC
(see Table 2.2B below for details). The applied sync pulse can be during the first TC clock period of a
193/256/512/1024 bit frame or it can be applied 1/2, 1, or 2 TC clocks early. This input sync signal resets
a counter that rolls over at a count of either 193 (T1 mode) or 256 (E1 mode) or 512 (4.096 MHz mode)
or 1024 (8.192 MHz mode) TC clocks. It is acceptable to only pulse the TS signal once to establish byte
boundaries and allow Chateau to keep track of the byte/frame boundaries by counting TC clocks. If the
incoming data does not require alignment to byte/frame boundaries, then this signal should be tied low.
TS SAMPLED EDGE Table 2.2B
0 TC Clock Early Mode
1/2 TC Clock Early Mode
1 TC Clock Early Mode
2 TC Clock Early Mode
Normal TC Clock Mode
Inverted TC Clock Mode
falling edge
rising edge
falling edge
falling edge
rising edge
falling edge
rising edge
rising edge
23 of 203
DS3134
2.3 LOCAL BUS SIGNAL DESCRIPTION
Signal Name:
LMS
Signal Description: Local Bus Mode Select
Signal Type:
Input
This signal should be tied low when the device is to be operated either with no Local Bus access or if the
Local Bus will be used to act as a bridge from the PCI bus. This signal should be tied high if the Local
Bus is to be used by an external host to configure the device.
0 = Local Bus is in the PCI Bridge Mode (master)
1 = Local Bus is in the Configuration Mode (slave)
Signal Name:
LIM
Signal Description: Local Bus Intel/Motorola Bus Select
Signal Type:
Input
The signal determines whether the Local Bus will operate in the Intel Mode (LIM = 0) or the Motorola
Mode (LIM = 1). The signal names in parenthesis are operational when the device is in the Motorola
Mode.
0 = Local Bus is in the Intel Mode
1 = Local Bus is in the Motorola Mode
Signal Name:
LD0 to LD15
Signal Description: Local Bus Non-Multiplexed Data Bus
Signal Type:
Input / Output (tri-state capable)
In PCI Bridge Mode (LMS = 0), data from/to the PCI bus can be transferred to/from these signals. When
writing data to the Local Bus, these signals will be outputs and updated on the rising edge of LCLK.
When reading data from the Local Bus, these signals will be inputs, which will be sampled on the rising
edge of LCLK. Depending on the assertion of the PCI Byte Enables (PCBE0 to PCBE3) and the Local
Bus Width (LBW) control bit in the Local Bus Bridge Mode Control Register (LBBMC), this data bus
will utilize all 16-bits (LD[15:0]) or just the lower 8-bits (LD[7:0]) or the upper 8-bits (LD[15:8]). If the
upper LD bits (LD[15:8]) are used, then the Local Bus High Enable signal (LBHE*) will be asserted
during the bus transaction. If the Local Bus is not currently involved in a bus transaction, then all 16
signals will be tri-stated. In the Configuration Mode (LMS = 1), the external host will configure the
device and obtain real time status information about the device via these signals. When reading data from
the Local Bus, these signals will be outputs that are updated on the rising edge of LCLK. When writing
data to the Local Bus, these signals will become inputs which will be sampled on the rising edge of
LCLK. In the Configuration Mode, only the 16-bit bus width is allowed (i.e. byte addressing is not
available).
24 of 203
DS3134
Signal Name:
LA0 to LA19
Signal Description: Local Bus Non-Multiplexed Address Bus
Signal Type:
Input / Output (tri-state capable)
In the PCI Bridge Mode (LMS = 0), these signals are outputs that will be asserted on the rising edge of
LCLK to indicate which address to be written to or read from. These signals will be tri-stated when the
Local Bus is not currently involved in a bus transaction and driven when a bus transaction is active. In the
Configuration Mode (LMS = 1), these signals are inputs and only the bottom 16 (LA[15:0]) are active, the
upper four (LA[19:16]) are ignored and should be tied low. These signals will be sampled on the rising
edge of LCLK to determine the internal device configuration register that the external host wishes to
access.
Signal Name:
LWR* (LR/W*)
Signal Description: Local Bus Write Enable (Local Bus Read/Write Select)
Signal Type:
Input / Output (tri-state capable)
In the PCI Bridge Mode (LMS = 0), this output signal is asserted on the rising edge of LCLK. In Intel
Mode (LIM = 0) it will be asserted when data is to be written to the Local Bus. In Motorola Mode (LIM
= 1), this signal will determine whether a read or write is to occur. If bus arbitration is enabled via the
Local Bus Arbitration (LARBE) control bit in the Local Bus Bridge Mode Control Register (LBBMC),
then this signal will be tri-stated when the Local Bus is not currently involved in a bus transaction and
driven when a bus transaction is active. When bus arbitration is disabled, this signal is always driven. In
the Configuration Mode (LMS = 1), this signal is sampled on the rising edge of LCLK. In Intel Mode
(LIM = 0) it will determine when data is to be written to the device. In Motorola Mode (LIM = 1), this
signal will be used to determine whether a read or write is to occur.
Signal Name:
LRD* (LDS*)
Signal Description: Local Bus Read Enable (Local Bus Data Strobe)
Signal Type:
Input / Output (tri-state capable)
In the PCI Bridge Mode (LMS = 0), this active low output signal is asserted on the rising edge of LCLK.
In Intel Mode (LIM = 0) it will be asserted when data is to be read from the Local Bus. In Motorola Mode
(LIM = 1), the rising edge will be used to write data into the slave device. If bus arbitration is enabled via
the Local Bus Arbitration (LARBE) control bit in the Local Bus Bridge Mode Control Register
(LBBMC), then this signal will be tri-stated when the Local Bus is not currently involved in a bus
transaction and driven when a bus transaction is active. When bus arbitration is disabled, this signal is
always driven. In the Configuration Mode (LMS = 1), this signal is an active low input which is sampled
on the rising edge of LCLK. In Intel Mode (LIM = 0) it will determine when data is to be read from the
device. In Motorola Mode (LIM = 1), the rising edge will be used to write data into the device.
Signal Name:
LINT*
Signal Description: Local Bus Interrupt
Signal Type:
Input / Output (open drain)
In the PCI Bridge Mode (LMS = 0), this active low signal is an input which sampled on the rising edge of
LCLK. If asserted and unmasked, this signal will cause an interrupt at the PCI bus via the PINTA*
signal. If not used in the PCI Bridge Mode, this signal should be tied high. In the Configuration Mode
(LMS = 1) this signal is an open drain output which will be forced low if one or more unmasked interrupt
sources within the device is active. The signal will remain low until the interrupt is either serviced or
masked.
25 of 203
DS3134
Signal Name:
LRDY*
Signal Description: Local Bus PCI Bridge Ready [PCI Bridge Mode Only]
Signal Type:
Input
This active low signal is sampled on the rising edge of LCLK to determine when a bus transaction is
complete. This signal is only examined when a bus transaction is taking place. This signal is ignored
when the Local Bus is in the Configuration Mode (LMS = 1) and should be tied high.
Signal Name:
LHLDA (LBG*)
Signal Description: Local Bus Hold Acknowledge (Local Bus Grant) [PCI Bridge Mode Only]
Signal Type:
Input
This input signal is sampled on the rising edge of LCLK to determine when the device has been granted
access to the bus. In Intel Mode (LIM = 0) this is an active high signal and in Motorola Mode (LIM = 1)
this is an active low signal. This signal is ignored and should be tied high when the Local Bus is in the
Configuration Mode (LMS = 1). Also, in the PCI Bridge Mode (LMS = 0), this signal should be tied
deasserted when the Local Bus Arbitration is disabled via the Local Bus Bridge Mode Control Register.
Signal Name:
LHOLD (LBR*)
Signal Description: Local Bus Hold (Local Bus Request) [PCI Bridge Mode Only]
Signal Type:
Output
This active low signal will be asserted when the Local Bus is attempting to take control of the bus. It will
be deasserted in the Intel Mode (LIM = 0) when the bus access is complete. It will be deasserted in the
Motorola Mode (LIM = 1) when the Local Bus Hold Acknowledge/Grant signal (LHLDA/LBG*) has
been detected. This signal is tri-stated when the Local Bus is in the Configuration Mode (LMS = 1) and
in the PCI Bridge Mode (LMS = 0) when the Local Bus Arbitration is disabled via the Local Bus Bridge
Mode Control Register.
Signal Name:
LBGACK*
Signal Description: Local Bus Grant Acknowledge [PCI Bridge Mode Only]
Signal Type:
Output (tri-state capable)
This active low signal is asserted when the Local Bus Hold Acknowledge/Bus Grant signal
(LHLDA/LBG*) has been detected and it continues it's assertion for a programmable (32 to 1048576)
number of LCLKs based upon the Local Bus Arbitration Timer setting in the Local Bus Bridge Mode
Control Register (LBBMC) register. This signal is tri-stated when the Local Bus is in the Configuration
Mode (LMS = 1).
Signal Name:
LBHE*
Signal Description: Local Bus Byte High Enable [PCI Bridge Mode Only]
Signal Type:
Output (tri-state capable)
This active low output signal is asserted when all 16-bits of the data bus (LD[15:0]) are active. It will
remain high if only the lower 8-bits (LD[7:0)] is active. If bus arbitration is enabled via the Local Bus
Arbitration (LARBE) control bit in the Local Bus Bridge Mode Control Register (LBBMC), then this
signal will be tri-stated when the Local Bus is not currently involved in a bus transaction and driven when
a bus transaction is active. When bus arbitration is disabled, this signal is always driven. This signal will
remain in tri-state when the Local Bus is not currently involved in a bus transaction and when the Local
Bus is in the Configuration Mode (LMS = 1).
26 of 203
DS3134
Signal Name:
LCLK
Signal Description: Local Bus Clock [PCI Bridge Mode Only]
Signal Type:
Output (tri-state capable)
This signal outputs a buffered version of the clock applied at the PCLK input. All Local Bus signals are
generated and sampled from this clock. This output is tri-stated when the Local Bus is in the
Configuration Mode (LMS = 1). It can be disabled in the PCI Bridge Mode via the Local Bus Bridge
Mode Control Register (LBBMC).
Signal Name:
LCS*
Signal Description: Local Bus Chip Select [Configuration Mode Only]
Signal Type:
Input
This active low signal must be asserted for the device to accept a read or write command from an external
host. This signal is ignored in the PCI Bridge Mode (LMS = 0) and should be tied high.
2.4 JTAG SIGNAL DESCRIPTION
Signal Name:
JTCLK
Signal Description: JTAG IEEE 1149.1 Test Serial Clock
Signal Type:
Input
This signal is used to shift data into JTDI on the rising edge and out of JTDO on the falling edge. If not
used, this signal should be pulled high.
Signal Name:
JTDI
Signal Description: JTAG IEEE 1149.1 Test Serial Data Input
Signal Type:
Input (with internal 10k pull up)
Test instructions and data are clocked into this signal on the rising edge of JTCLK. If not used, this signal
should be pulled high. This signal has an internal pull-up.
Signal Name:
JTDO
Signal Description: JTAG IEEE 1149.1 Test Serial Data Output
Signal Type:
Output
Test instructions are clocked out of this signal on the falling edge of JTCLK. If not used, this signal
should be left open circuited.
Signal Name:
JTRST*
Signal Description: JTAG IEEE 1149.1 Test Reset
Signal Type:
Input (with internal 10k pull up)
This signal is used to asynchronously reset the test access port controller. At power up, JTRST must be
set low and then high. This action will set the device into the boundary scan bypass mode allowing
normal device operation. If boundary scan is not used, this signal should be held low. This signal has an
internal pull-up.
27 of 203
DS3134
Signal Name:
JTMS
Signal Description: JTAG IEEE 1149.1 Test Mode Select
Signal Type:
Input (with internal 10k pull up)
This signal is sampled on the rising edge of JTCLK and is used to place the test port into the various
defined IEEE 1149.1 states. If not used, this signal should be pulled high. This signal has an internal pullup.
2.5 PCI BUS SIGNAL DESCRIPTION
Signal Name:
PCLK
Signal Description: PCI & System Clock
Signal Type:
Input (Schmitt triggered)
This clock input is used to provide timing for the PCI bus and to the internal logic of the device. A 25
MHz to 33 MHz clock with a nominal 50% duty cycle should be applied here.
Signal Name:
PRST*
Signal Description: PCI Reset
Signal Type:
Input
This active low input is used to force an asynchronous reset to both the PCI bus and the internal logic of
the device. When forced low, this input forced all the internal logic of the device into its default state and
it forces the PCI outputs into tri-state and the TD[15:0] output port data signals high.
Signal Name:
PAD0 to PAD31
Signal Description: PCI Address & Data Multiplexed Bus
Signal Type:
Input / Output (tri-state capable)
Both Address and Data information are multiplexed onto these signals. Each bus transaction consists of
an address phase followed by one or more data phases. Data can be either read or written in bursts.
During the first clock cycle of a bus transaction, the address is transferred. When the Little-Endian format
is selected, PAD[31:24] is the msb of the DWORD, when Big-Endian is selected, PAD[7:0] contain the
msb. When the device is an initiator, these signals are always outputs during the address phase. They
remain outputs for the data phase(s) in a write transaction and become inputs for a read transaction.
When the device is a target, these signals are always inputs during the address phase. They remain inputs
for the data phase(s) in a read transaction and become outputs for a write transaction. When the device is
not involved in a bus transaction, these signals remain tri-stated. These signals are always updated and
sampled on the rising edge of PCLK.
Signal Name:
PCBE0* / PCBE1* / PCBE2* / PCBE3*
Signal Description: PCI Bus Command and Byte Enable
Signal Type:
Input / Output (tri-state capable)
Bus Command and Byte Enables are multiplexed onto the same PCI signals. During an address phase,
these signals define the Bus Command. During the data phase, these signals as used as Bus Enables.
During data phases, PCBE0 refers to the PAD[7:0] and PCBE3 refers to PAD[31:24]. When this signal is
high, the associated byte is invalid, when low; the associated byte is valid. When the device is an
initiator, this signal is an output and is updated on the rising edge of PCLK. When the device is a target,
this signal is input and is sampled on the rising edge of PCLK. When the device is not involved in a bus
transaction, these signals are tri-stated.
Signal Name:
PPAR
28 of 203
DS3134
Signal Description: PCI Bus Parity
Signal Type:
Input / Output (tri-state capable)
This signal provides information on even parity across both the PAD address/data bus and the PCBE bus
command/byte enable bus. When the device is an initiator, this signal is an output for writes and input for
reads and is updated on the rising edge of PCLK. When the device is a target, this signal is input for
writes and an output for reads and is sampled on the rising edge of PCLK. When the device is not
involved in a bus transaction, PPAR is tri-stated.
Signal Name:
PFRAME*
Signal Description: PCI Cycle Frame
Signal Type:
Input / Output (tri-state capable)
This active low signal is created by the bus initiator and is used to indicate the beginning and duration of a
bus transaction. PFRAME* is asserted by the initiator during the first clock cycle of a bus transaction and
it will remain asserted until the last data phase of a bus transaction. When the device is an initiator, this
signal is an output and is updated on the rising edge of PCLK. When the device is a target, this signal is
input and is sampled on the rising edge of PCLK. When the device is not involved in a bus transaction,
PFRAME* is tri-stated.
Signal Name:
PIRDY*
Signal Description: PCI Initiator Ready
Signal Type:
Input / Output (tri-state capable)
This active low signal is created by the initiator to signal the target that it is ready to send/accept or to
continue sending/accepting data. This signal handshakes with the PTRDY* signal during a bus
transaction to control the rate at which data transfers across the bus. During a bus transaction, PIRDY* is
deasserted when the initiator cannot temporarily accept or send data and a wait state is invoked. When the
device is an initiator, this signal is an output and is updated on the rising edge of PCLK. When the device
is a target, this signal is input and is sampled on the rising edge of PCLK. When the device is not
involved in a bus transaction, PIRDY* is tri-stated.
Signal Name:
PTRDY*
Signal Description: PCI Target Ready
Signal Type:
Input / Output (tri-state capable)
This active low signal is created by the target to signal the initiator that it is ready to send/accept or to
continue sending/accepting data. This signal handshakes with the PIRDY* signal during a bus transaction
to control the rate at which data transfers across the bus. During a bus transaction, PTRDY* is deasserted
when the target cannot temporarily accept or send data and a wait state is invoked. When the device is a
target, this signal is an output and is updated on the rising edge of PCLK. When the device is an initiator,
this signal is input and is sampled on the rising edge of PCLK. When the device is not involved in a bus
transaction, PTRDY* is tri-stated.
29 of 203
DS3134
Signal Name:
PSTOP*
Signal Description: PCI Stop
Signal Type:
Input / Output (tri-state capable)
This active low signal is created by the target to signal to the initiator that it requests the initiator stop the
current bus transaction. When the device is a target, this signal is an output and is updated on the rising
edge of PCLK. When the device is an initiator, this signal is input and is sampled on the rising edge of
PCLK. When the device is not involved in a bus transaction, PSTOP* is tri-stated.
Signal Name:
PIDSEL
Signal Description: PCI Initialization Device Select
Signal Type:
Input
This input signal is used as a chip select during configuration read and writes transactions. This signal is
disabled when the Local Bus is set in the Configuration Mode (LMS = 1). When PIDSEL is set high
during the address phase of a bus transaction and the Bus Command signals (PCBE0 to PCBE3) indicate
a register read or write, then the device allows access to the PCI configuration registers and the
PDEVSEL* signal is asserted during the PCLK cycle. PIDSEL is sampled on the rising edge of PCLK.
Signal Name:
PDEVSEL*
Signal Description: PCI Device Select
Signal Type:
Input / Output (tri-state capable)
This active low signal is created by the target when it has decoded the address sent to it by the initiator, as
it's own to indicate that that the address is valid. If the device is an initiator and does not see the signal
asserted within six PCLK cycles, then the bus transaction is aborted and the PCI Host is alerted. When the
device is a target, this signal is an output and is updated on the rising edge of PCLK. When the device is
an initiator, this signal is input and is sampled on the rising edge of PCLK. When the device is not
involved in a bus transaction, PDEVSEL* is tri-stated.
Signal Name:
PREQ*
Signal Description: PCI Bus Request
Signal Type:
Output (tri-state capable)
This active low signal is asserted by the initiator to request that the PCI bus arbiter allow it access to the
bus. PREQ* is updated on the rising edge of PCLK.
Signal Name:
PGNT*
Signal Description: PCI Bus Grant
Signal Type:
Input
This active low signal is asserted by the PCI bus arbiter to indicate to the PCI requesting agent that access
to the PCI bus has been granted. The device samples PGNT* on the rising edge of PCLK and if detected,
will initiate a bus transaction when it has sensed that the PFRAME* signal has been deasserted.
Signal Name:
PPERR*
Signal Description: PCI Parity Error
Signal Type:
Input / Output (tri-state capable)
This active low signal reports parity errors that occur. PPERR* can be enabled and disabled via the PCI
Configuration Registers. This signal is updated on the rising edge of PCLK.
30 of 203
DS3134
Signal Name:
PSERR*
Signal Description: PCI System Error
Signal Type:
Output (open drain)
This active low signal reports any parity errors that occur during the address phase. PSERR* can be
enabled and disabled via the PCI Configuration Registers. This signal is updated on the rising edge of
PCLK.
Signal Name:
PINTA*
Signal Description: PCI Interrupt
Signal Type:
Output (open drain)
This active low (open drain) signal is asserted low asynchronously when the device is requesting attention
from the device driver. PINTA will be deasserted when the device interrupting source has been service or
masked. This signal is updated on the rising edge of PCLK.
PCI Extension Signals
These signals are not part of the normal PCI Bus signal set. There are additional signals that are asserted
when Chateau is an Initiator on the PCI Bus to help users interpret the normal PCI Bus signal set and
connect them to a non-PCI environment like an Intel i960 type bus. The timing for these signals is shown
below.
Signal Name:
PXAS*
Signal Description: PCI Extension Address Strobe
Signal Type:
Output
This active low signal is asserted low on the same clock edge as PFRAME* and is deasserted after one
clock period. This signal will only be asserted when the device is an initiator. This signal is an output
and is updated on the rising edge of PCLK.
Signal Name:
PXDS*
Signal Description: PCI Extension Data Strobe
Signal Type:
Output
This active low signal is asserted when the PCI bus either contains valid data to be read from the device
or can accept valid data that is written into the device. This signal will only be asserted when the device
is an initiator. This signal is an output and is updated on the rising edge of PCLK.
Signal Name:
PXBLAST*
Signal Description: PCI Extension Burst Last
Signal Type:
Output
This active low signal is asserted on the same clock edge as PFRAME* is deasserted and is deasserted on
the same clock edge as PIRDY* is deasserted. This signal will only be asserted when the device is an
initiator. This signal is an output and is updated on the rising edge of PCLK.
31 of 203
DS3134
2.6 SUPPLY & TEST SIGNAL DESCRIPTION
Signal Name:
TEST
Signal Description: Factory Test Input
Signal Type:
Input (with internal 10k pull up).
This input should be left open circuited by the user.
Signal Name:
VDD
Signal Description: Positive Supply
Signal Type:
n/a
3.3V (+/- 10%). All VDD signals should be tied together.
Signal Name:
VSS
Signal Description: Ground Reference
Signal Type:
n/a
All VSS signals should be tied to the local ground plane.
32 of 203
DS3134
SECTION 3: MEMORY MAP
3.0 INTRODUCTION
All addresses within the memory map on dword boundaries even though all of the internal device
configuration registers are only one word (16 bits) wide. The memory map consumes an address range of
4 kB (12 bits). When the PCI Bus is the Host (i.e. the Local Bus is in the Bridge Mode), the actual 32-bit
PCI Bus addresses of the internal device configuration registers is obtained by adding the DC Base
Address value in the PCI Device Configuration Memory Base Address Register (see Section 9.2 for
details) to the offset listed in Sections 3.1 to 3.11. When an external host is configuring the device via the
Local Bus (i.e. the Local Bus is in the Configuration Mode), the offset is 0h and the Host on the Local
Bus will use the 16-bit addresses listed in Sections 3.1 to 3.11.
MEMORY MAP ORGANIZATION Table 3.0A
Section
3.1
3.2
3.3
3.4
3.5
3.6
3.7
3.8
3.9
3.10
3.11
Register Name
General Configuration Registers
Receive Port Registers
Transmit Port Registers
Channelized Port Registers
HDLC Registers
BERT Registers
Receive DMA Registers
Transmit DMA Registers
FIFO Registers
PCI Configuration Registers for Function 0
PCI Configuration Registers for Function 1
PCI Host
[offset from DC Base]
(0x000)
(0x1xx)
(0x2xx)
(0x3xx)
(0x4xx)
(0x5xx)
(0x7xx)
(0x8xx)
(0x9xx)
(PIDSEL)
(PIDSEL)
Local Bus Host
(16-bit address)
(00xx)
(01xx)
(02xx)
(03xx)
(04xx)
(05xx)
(07xx)
(08xx)
(09xx)
(0Axx)
(0Bxx)
3.1 GENERAL CONFIGURATION REGISTERS (0XX)
Offset/
Address
0000
0010
0020
0024
0028
002C
0030
0034
0040
0050
Acronym
MRID
MC
SM
ISM
SDMA
ISDMA
SV54
ISV54
LBBMC
TEST
Register Name
Master Reset & ID Register.
Master Configuration.
Master Status Register.
Interrupt Mask Register for SM.
Status Register for DMA.
Interrupt Mask Register for SDMA.
Status Register for V.54 Loopback Detector.
Interrupt Mask Register for SV54.
Local Bus Bridge Mode Control Register.
Test Register.
33 of 203
Section
4.1
4.2
4.3.2
4.3.2
4.3.2
4.3.2
4.3.2
4.3.2
10.2
4.4
DS3134
3.2 RECEIVE PORT REGISTERS (1XX)
Offset/
Address
0100
0104
0108
010C
0110
0114
0118
011C
0120
0124
0128
012C
0130
0134
0138
013C
Acronym
Register Name
Section
RP0CR
RP1CR
RP2CR
RP3CR
RP4CR
RP5CR
RP6CR
RP7CR
RP8CR
RP9CR
RP10CR
RP11CR
RP12CR
RP13CR
RP14CR
RP15CR
Receive Port 0 Control Register.
Receive Port 1 Control Register.
Receive Port 2 Control Register.
Receive Port 3 Control Register.
Receive Port 4 Control Register.
Receive Port 5 Control Register.
Receive Port 6 Control Register.
Receive Port 7 Control Register.
Receive Port 8 Control Register.
Receive Port 9 Control Register.
Receive Port 10 Control Register.
Receive Port 11 Control Register.
Receive Port 12 Control Register.
Receive Port 13 Control Register.
Receive Port 14 Control Register.
Receive Port 15 Control Register.
5.2
5.2
5.2
5.2
5.2
5.2
5.2
5.2
5.2
5.2
5.2
5.2
5.2
5.2
5.2
5.2
3.3 TRANSMIT PORT REGISTERS (2XX)
Offset/
Address
0200
0204
0208
020C
0210
0214
0218
021C
0220
0224
0228
022C
0230
0234
0238
023C
Acronym
Register Name
Section
TP0CR
TP1CR
TP2CR
TP3CR
TP4CR
TP5CR
TP6CR
TP7CR
TP8CR
TP9CR
TP10CR
TP11CR
TP12CR
TP13CR
TP14CR
TP15CR
Transmit Port 0 Control Register.
Transmit Port 1 Control Register.
Transmit Port 2 Control Register.
Transmit Port 3 Control Register.
Transmit Port 4 Control Register.
Transmit Port 5 Control Register.
Transmit Port 6 Control Register.
Transmit Port 7 Control Register.
Transmit Port 8 Control Register.
Transmit Port 9 Control Register.
Transmit Port 10 Control Register.
Transmit Port 11 Control Register.
Transmit Port 12 Control Register.
Transmit Port 13 Control Register.
Transmit Port 14 Control Register.
Transmit Port 15 Control Register.
5.2
5.2
5.2
5.2
5.2
5.2
5.2
5.2
5.2
5.2
5.2
5.2
5.2
5.2
5.2
5.2
34 of 203
DS3134
3.4 CHANNELIZED PORT REGISTERS (3XX)
Offset/
Address
0300
0304
0308
030C
0310
0314
0318
031C
0320
0324
0328
032C
0330
0334
0338
033C
0340
0344
0348
034C
0350
0354
0358
035C
0360
0364
0368
036C
0370
0374
0378
037C
Acronym
Register Name
Section
CP0RDIS
CP0RD
CP1RDIS
CP1RD
CP2RDIS
CP2RD
CP3RDIS
CP3RD
CP4RDIS
CP4RD
CP5RDIS
CP5RD
CP6RDIS
CP6RD
CP7RDIS
CP7RD
CP8RDIS
CP8RD
CP9RDIS
CP9RD
CP10RDIS
CP10RD
CP11RDIS
CP11RD
CP12RDIS
CP12RD
CP13RDIS
CP13RD
CP14RDIS
CP14RD
CP15RDIS
CP15RD
Channelized Port 0 Register Data Indirect Select.
Channelized Port 0 Register Data.
Channelized Port 1 Register Data Indirect Select.
Channelized Port 1 Register Data.
Channelized Port 2 Register Data Indirect Select.
Channelized Port 2 Register Data.
Channelized Port 3 Register Data Indirect Select.
Channelized Port 3 Register Data.
Channelized Port 4 Register Data Indirect Select.
Channelized Port 4 Register Data.
Channelized Port 5 Register Data Indirect Select.
Channelized Port 5 Register Data.
Channelized Port 6 Register Data Indirect Select.
Channelized Port 6 Register Data.
Channelized Port 7 Register Data Indirect Select.
Channelized Port 7 Register Data.
Channelized Port 8 Register Data Indirect Select.
Channelized Port 8 Register Data.
Channelized Port 9 Register Data Indirect Select.
Channelized Port 9 Register Data.
Channelized Port 10 Register Data Indirect Select.
Channelized Port 10 Register Data.
Channelized Port 11 Register Data Indirect Select.
Channelized Port 11 Register Data.
Channelized Port 12 Register Data Indirect Select.
Channelized Port 12 Register Data.
Channelized Port 13 Register Data Indirect Select.
Channelized Port 13 Register Data.
Channelized Port 14 Register Data Indirect Select.
Channelized Port 14 Register Data.
Channelized Port 15 Register Data Indirect Select.
Channelized Port 15 Register Data.
5.3
5.3
5.3
5.3
5.3
5.3
5.3
5.3
5.3
5.3
5.3
5.3
5.3
5.3
5.3
5.3
5.3
5.3
5.3
5.3
5.3
5.3
5.3
5.3
5.3
5.3
5.3
5.3
5.3
5.3
5.3
5.3
3.5 HDLC REGISTERS (4XX)
Offset/
Address
0400
0404
0410
0480
0484
Acronym
Register Name
Section
RHCDIS
RHCD
RHPL
THCDIS
THCD
Receive HDLC Channel Definition Indirect Select.
Receive HDLC Channel Definition.
Receive HDLC maximum Packet Length. One per Device
Transmit HDLC Channel Definition Indirect Select.
Transmit HDLC Channel Definition.
6.2
6.2
6.2
6.2
6.2
35 of 203
DS3134
3.6 BERT REGISTERS (5XX)
Offset/
Address
0500
0504
0508
050C
0510
0514
0518
051C
Acronym
Register Name
Section
BERTC0
BERTC1
BERTRP0
BERTRP1
BERTBC0
BERTBC1
BERTEC0
BERTEC1
BERT Control 0.
BERT Control 1.
BERT Repetitive Pattern Set 0 (lower word).
BERT Repetitive Pattern Set 1 (upper word).
BERT Bit Counter 0 (lower word).
BERT Bit Counter 1 (upper word).
BERT Error Counter 0 (lower word).
BERT Error Counter 1 (upper word).
5.6
5.6
5.6
5.6
5.6
5.6
5.6
5.6
3.7 RECEIVE DMA REGISTERS (7XX)
Offset/
Address
0700
0704
0708
070C
0710
0714
0718
071C
0730
0734
0738
073C
0740
0744
0750
0754
0770
0774
0780
0790
0794
Acronym
Register Name
Section
RFQBA0
RFQBA1
RFQEA
RFQSBSA
RFQLBWP
RFQSBWP
RFQLBRP
RFQSBRP
RDQBA0
RDQBA1
RDQEA
RDQRP
RDQWP
RDQFFT
RDBA0
RDBA1
RDMACIS
RDMAC
RDMAQ
RLBS
RSBS
Receive Free Queue Base Address 0 (lower word).
Receive Free Queue Base Address 1 (upper word).
Receive Free Queue End Address.
Receive Free Queue Small Buffer Start Address.
Receive Free Queue Large Buffer Host Write Pointer.
Receive Free Queue Small Buffer Host Write Pointer.
Receive Free Queue Large Buffer DMA Read Pointer.
Receive Free Queue Small Buffer DMA Read Pointer.
Receive Done Queue Base Address 0 (lower word).
Receive Done Queue Base Address 1 (upper word).
Receive Done Queue End Address.
Receive Done Queue Host Read Pointer.
Receive Done Queue DMA Write Pointer.
Receive Done Queue FIFO Flush Timer.
Receive Descriptor Base Address 0 (lower word).
Receive Descriptor Base Address 1 (upper word).
Receive DMA Configuration Indirect Select.
Receive DMA Configuration.
Receive DMA Queues Control.
Receive Large Buffer Size.
Receive Small Buffer Size.
8.1.3
8.1.3
8.1.3
8.1.3
8.1.3
8.1.3
8.1.3
8.1.3
8.1.4
8.1.4
8.1.4
8.1.4
8.1.4
8.1.4
8.1.2
8.1.2
8.1.5
8.1.5
8.1.3/.4
8.1.1
8.1.1
36 of 203
DS3134
3.8 TRANSMIT DMA REGISTERS (8XX)
Offset/
Address
0800
0804
0808
080C
0810
0830
0834
0838
083C
0840
0844
0850
0854
0870
0874
0880
Acronym
Register Name
Section
TPQBA0
TPQBA1
TPQEA
TPQWP
TPQRP
TDQBA0
TDQBA1
TDQEA
TDQRP
TDQWP
TDQFFT
TDBA0
TDBA1
TDMACIS
TDMAC
TDMAQ
Transmit Pending Queue Base Address 0 (lower word).
Transmit Pending Queue Base Address 1 (upper word).
Transmit Pending Queue End Address.
Transmit Pending Queue Host Write Pointer.
Transmit Pending Queue DMA Read Pointer.
Transmit Done Queue Base Address 0 (lower word).
Transmit Done Queue Base Address 1 (upper word).
Transmit Done Queue End Address.
Transmit Done Queue Host Read Pointer.
Transmit Done Queue DMA Write Pointer.
Transmit Done Queue FIFO Flush Timer.
Transmit Descriptor Base Address 0 (lower word).
Transmit Descriptor Base Address 1 (upper word).
Transmit DMA Configuration Indirect Select.
Transmit DMA Configuration.
Transmit DMA Queues Control.
8.2.3
8.2.3
8.2.3
8.2.3
8.2.3
8.2.4
8.2.4
8.2.4
8.2.4
8.2.4
8.2.4
8.2.2
8.2.2
8.2.5
8.2.5
8.2.3/.4
3.9 FIFO REGISTERS (9XX)
Offset/
Address
0900
0904
0910
0914
0920
0924
0980
0984
0990
0994
09A0
09A4
Acronym
Register Name
Section
RFSBPIS
RFSBP
RFBPIS
RFBP
RFHWMIS
RFHWM
TFSBPIS
TFSBP
TFBPIS
TFBP
TFLWMIS
TFLWM
Receive FIFO Starting Block Pointer Indirect Select.
Receive FIFO Starting Block Pointer.
Receive FIFO Block Pointer Indirect Select.
Receive FIFO Block Pointer.
Receive FIFO High Water Mark Indirect Select.
Receive FIFO High Water Mark.
Transmit FIFO Starting Block Pointer Indirect Select.
Transmit FIFO Starting Block Pointer.
Transmit FIFO Block Pointer Indirect Select.
Transmit FIFO Block Pointer.
Transmit FIFO Low Water Mark Indirect Select.
Transmit FIFO Low Water Mark.
7.2
7.2
7.2
7.2
7.2
7.2
7.2
7.2
7.2
7.2
7.2
7.2
3.10 PCI CONFIGURATION REGISTERS FOR FUNCTION 0 (PIDSEL/AXX)
Offset/
Address
0x000/0A00
0x004/0A04
0x008/0A08
0x00C/0A0C
0x010/0A10
0x03C/0A3C
Acronym
Register Name
Section
PVID0
PCMD0
PRCC0
PLTH0
PDCM
PINTL0
PCI Vendor ID / Device ID 0.
PCI Command Status 0.
PCI Revision ID / Class Code 0.
PCI Cache Line Size / Latency Timer / Header Type 0.
PCI Device Configuration Memory Base Address.
PCI Interrupt Line & Pin / Min. Grant / Max. Latency 0.
9.2
9.2
9.2
9.2
9.2
9.2
37 of 203
DS3134
3.11 PCI CONFIGURATION REGISTERS FOR FUNCTION 1 (PIDSEL/BXX)
Offset/
Address
0x100/0B00
0x104/0B04
0x108/0B08
0x10C/0B0C
0x110/0B10
0x13C/0B3C
Acronym
Register Name
Section
PVID1
PCMD1
PRCC1
PLTH1
PLBM
PINTL1
PCI Vendor ID / Device ID 1.
PCI Command Status 1.
PCI Revision ID / Class Code 1.
PCI Cache Line Size / Latency Timer / Header Type 1.
PCI Device Local Base Memory Base Address.
PCI Interrupt Line & Pin / Min. Grant / Max. Latency 1.
9.2
9.2
9.2
9.2
9.2
9.2
38 of 203
DS3134
SECTION 4: GENERAL DEVICE CONFIGURATION & STATUS/INTERRUPT
4.1 MASTER RESET & ID REGISTER DESCRIPTION
The Master Reset & ID (MRID) register can be used to globally reset the device. When the RST bit is set
to one, all of the internal registers (except the PCI configuration registers) will be placed into their default
state, which is 0000h. The Host must set the RST bit back to zero before the device can be programmed
for normal operation. The RST bit does not force the PCI outputs to tri-state as does the hardware reset
which is invoked via the PRST* pin. A reset invoked by the PRST* pin will force the RST bit to zero as
well as the rest of the internal configuration registers. See Section 1 for more details on device
initialization.
The upper byte of the MRID register is read only and it can be read by the Host to determine the chip
revision. Contact the factory for specifics on the meaning of the value read from the ID0 to ID7 bits.
Register Name:
MRID
Register Description: Master Reset and ID Register
Register Address:
0000h
7
6
5
4
3
2
1
0
n/a
n/a
n/a
n/a
n/a
n/a
n/a
RST
15
14
13
12
11
10
9
8
ID7
ID6
ID5
ID4
ID3
ID2
ID1
ID0
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
Bit 0 / Master Software Reset (RST).
0 = normal operation
1 = force all internal registers (except LBBMC) to their default value of 0000h
Bits 8 to 15 / Chip Revision ID Bit 0 to 7 (ID0 to ID7). Read only. Contact the factory for details on
the meaning of the ID bits.
4.2 MASTER CONFIGURATION REGISTER DESCRIPTION
The Master Configuration (MC) register is used by the Host to enable the receive and transmit DMAs as
well as to control their PCI Bus bursting attributes and to select which port the BERT is to be dedicated
to.
Register Name:
MC
Register Description: Master Configuration Register
Register Address:
0010h
7
6
5
4
3
2
1
0
BPS0
PBO
TDT1
TDT0
TDE
RDT1
RDT0
RDE
15
14
13
12
11
10
9
8
TFPC1
TFPC0
RFPC1
RFPC0
BPS4
BPS3
BPS2
BPS1
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
39 of 203
DS3134
Bit 0 / Receive DMA Enable (RDE). This bit is used to enable the receive DMA. When it is set to zero,
the receive DMA will not pass any data from the receive FIFO to the PCI Bus even if there is one or more
HDLC channels enabled. On device initialization, the Host should fully configure the receive DMA
before enabling it via this bit.
0 = receive DMA is disabled
1 = receive DMA is enabled
Bit 1 / Receive DMA Throttle Select Bit 0 (RDT0).
Bit 2 / Receive DMA Throttle Select Bit 1 (RDT1).
These two bits select the maximum burst length that the receive DMA is allowed on the PCI Bus. The
DMA can be restricted to a maximum burst length of just 32 dwords (128 bytes) or it can be
incrementally adjusted up to 256 dwords (1024 bytes). The Host will select the optimal length based on a
number of factors including the system environment for the PCI Bus, the number of HDLC channels
being used, and the trade off between channel latency and bus efficiency.
00 = burst length maximum is 32 dwords
01 = burst length maximum is 64 dwords
10 = burst length maximum is 128 dwords
11 = burst length maximum is 256 dwords
Bit 3 / Transmit DMA Enable (TDE). This bit is used to enable the transmit DMA. When it is set to
zero, the transmit DMA will not pass any data from the PCI Bus to the transmit FIFO even if there is one
or more HDLC channels enabled. On device initialization, the Host should fully configure the transmit
DMA before enabling it via this bit.
0 = transmit DMA is disabled
1 = transmit DMA is enabled
Bit 4 / Transmit DMA Throttle Select Bit 0 (TDT0).
Bit 5 / Transmit DMA Throttle Select Bit 1 (TDT1).
These two bits select the maximum burst length that the transmit DMA is allowed on the PCI Bus. The
DMA can be restricted to a maximum burst length of just 32 dwords (128 bytes) or it can be
incrementally adjusted up to 256 dwords (1024 bytes). The Host will select the optimal length based on a
number of factors including the system environment for the PCI Bus, the number of HDLC channels
being used, and the trade off between channel latency and bus efficiency.
00 = burst length maximum is 32 dwords
01 = burst length maximum is 64 dwords
10 = burst length maximum is 128 dwords
11 = burst length maximum is 256 dwords
Bit 6 / PCI Bus Orientation (PBO).
This bit selects whether HDLC packet data on the PCI Bus will operate in either Little Endian format or
Big Endian format. Little Endian byte ordering places the least significant byte at the lowest address
while Big Endian places the least significant byte at the highest address. This bit setting only affects
HDLC data on the PCI Bus. All other PCI Bus transactions to the internal device configuration registers,
PCI configuration registers, and Local Bus, are always in Little Endian format.
0 = HDLC Packet Data on the PCI Bus is in Little Endian format
1 = HDLC Packet Data on the PCI Bus is in Big Endian format
40 of 203
DS3134
Bits 7 to 11 / BERT Port Select Bits 0 to 4 (BPS0 to BPS4). These 5 bits select which port has the
dedicated resources of the BERT.
00000 = Port 0
00001 = Port 1
00010 = Port 2
00011 = Port 3
00100 = Port 4
00101 = Port 5
00110 = Port 6
00111 = Port 7
01000 = Port 8
01001 = Port 9
01010 = Port 10
01011 = Port 11
01100 = Port 12
01101 = Port 13
01110 = Port 14
01111 = Port 15
10000 = Port 0 (hi speed)
10001 = Port 1 (hi speed)
10010 = n/a
10011 = n/a
10100 = n/a
10101 = n/a
10110 = n/a
10111 = n/a
11000 = n/a
11001 = n/a
11010 = n/a
11011 = n/a
11100 = n/a
11101 = n/a
11110 = n/a
11111 = n/a
Bit 12 / Receive FIFO Priority Control Bit 0 (RFPC0).
Bit 13 / Receive FIFO Priority Control Bit 1 (RFPC1).
These 2 bits select the algorithm the FIFO will use to determine which HDLC Channel gets the highest
priority to the DMA to transfer data from the FIFO to the PCI Bus. In the priority decoded scheme, the
lower the HDLC channel numbers, the higher the priority.
00 = all HDLC channels are serviced Round Robin
01 = HDLC Channels 1 & 2 are Priority Decoded; other HDLC Channels are Round Robin
10 = HDLC Channels 1 to 16 are Priority Decoded; other HDLC Channels are Round Robin
11 = HDLC Channels 1 to 64 are Priority Decoded; other HDLC Channels are Round Robin
Bit 14 / Transmit FIFO Priority Control Bit 0 (TFPC0).
Bit 15 / Transmit FIFO Priority Control Bit 1 (TFPC1).
These 2 bits select the algorithm the FIFO will use to determine which HDLC Channel gets the highest
priority to the DMA to transfer data from the PCI Bus to the FIFO. In the priority decoded scheme, the
lower the HDLC channel numbers, the higher the priority.
00 = all HDLC channels are serviced Round Robin
01 = HDLC Channels 1 & 2 are Priority Decoded; other HDLC Channels are Round Robin
10 = HDLC Channels 1 to 16 are Priority Decoded; other HDLC Channels are Round Robin
11 = HDLC Channels 1 to 64 are Priority Decoded; other HDLC Channels are Round Robin
4.3 STATUS & INTERRUPT
4.3.1 Status & Interrupt General Description of Operation
There are three status register in the device, Status Master (SM), Status for the Receive V54 Loopback
Detector (SV54), and Status for DMA (SDMA). All three registers report events in real time as they
occur by setting a bit within the register to a one. All bits that have been set within the register are cleared
when the register is read and the bit will not be set again until the event has occurred again. Each bit has
the ability to generate an interrupt at the PCI Bus via the PINTA* output signal pin and if the Local Bus is
in the Configuration Mode, then an interrupt will also be created at the LINT* output signal pin. Each
status register has an associated Interrupt Mask Register, which can allow/deny interrupts from being
generated on a bit-by-bit basis. All status remains active even if the associated Interrupt is disabled.
41 of 203
DS3134
SM Register
The Status Master (SM) register reports events that occur at the Port Interface, at the BERT receiver, at
the PCI Bus and at the Local Bus. See Figure 4.3.1A for details.
The Port Interface reports Change Of Frame Alignment (COFA) events. If the software detects that one
of these bits as being set, the software must then begin polling the RP[n]CR or TP[n]CR registers of each
active port (a maximum of 16 reads) to determine which port or ports has incurred a COFA. Also via the
Interrupt Enable for Receive COFA (IERC) and Interrupt Enable for Transmit COFA (IETC) control bits
in the RP[n]CR and TP[n]CR registers respectively, the Host can allow/deny the COFA indications to be
passed on to the SRCOFA and STCOFA status bits.
The BERT receiver will report three events, a change in the receive synchronizer status, a bit error being
detected, and if either the Bit Counter or the Error Counter overflows. Each of these events can be
masked within the BERT function via the BERT Control Register (BERTC0). If the software detects that
the BERT has reported an event has occurred, then the software must read the BERT Status Register
(BERTEC0) to determine which event(s) has occurred.
The SM register also reports events as they occur in the PCI Bus and the Local Bus. There are no control
bits to stop these events from being reported in the SM register. When the Local Bus is operated in the
PCI Bridge Mode, SM reports any interrupts detected via the Local Bus LINT* input signal pin and if any
timing errors occur because of the use of the external timing signal LRDY*. When the Local Bus is
operated in the Configuration Mode, the LBINT and LBE bits are meaningless and should be ignored.
SV54 Register
The Status for Receive V.54 Detector (SV54) register reports if the V.54 loopback detector has either
timed out in its search for the V.54 loop up pattern or if the detector has found and verified the loop
up/down pattern. There is a separate status bit (SLBP) for each port. When set, the Host must read the
VTO and VLB status bits in the RP[n]CR register of the corresponding port to find the exact state of the
V.54 detector. When the V.54 detector experiences a time out in it's search for the loop up code (VTO =
1), then the SLBP status bit will be continuously set until the V.54 detector is reset by the Host toggling
the VRST bit in RP[n]CR register. There are no control bits to stop these events from being reported in
the SV54 register. See Figure 4.3.1A for details on the status bits and Section 5 for details on the
operation of the V.54 loopback detector.
SDMA Register
The Status for DMA (SDMA) register reports events that occur regarding the Receive and Transmit DMA
blocks as well as the receive HDLC controller and FIFO. The SDMA will report when the DMA reads
from either the Receive Free Queue or Transmit Pending Queue or writes to the Receive or Transmit
Done Queues. Also reported are error conditions that might occur in the access of one of these queues.
The SDMA will report if any of the HDLC channels experiences a FIFO overflow/underflow condition
and if the receive HDLC controller encounters a CRC error, abort signal, or octet length problem on any
of the HDLC channels. The Host can determine which specific HDLC channel incurred a FIFO
overflow/underflow, CRC error, octet length error or abort by reading the status bits as reported in Done
Queues which are created by the DMA. There are no control bits to stop these events from being reported
in the SDMA register.
42 of 203
DS3134
STATUS REGISTER BLOCK DIAGRAM FOR SM & SV54 Figure 4.3.1A
BERT
BERTEC0 Bit 1 (BECO)
OR
BERTEC0 Bit 2 (BBCO)
BERTC0 Bit 13 (IEOF)
Change in BERTEC0 Bit 0 (SYNC)
BERTC0 Bit 15 (IESYNC)
BERTEC0 Bit 3 (BED)
BERTC0 Bit 14 (IEBED)
OR
Transmit
Port I/F # 0
Receive
Port I/F # 0
TCOFA
TP0CR
Bit #14
RCOFA
RP0CR
Bit #14
#1
#2
#3
#1
#2
#3
#13
#14
#15
#13
#14
#15
int_bd
OR
OR
SM: Status Master Register
LBINT
LBE
n/a
n/a
ST
PPERR PSERR SBERT
COFA
SR
COFA
SV54: Status for V54 Detector
SLBP15 SLBP14 SLBP13
SLBP5 SLBP4 SLBP3 SLBP2 SLBP1 SLBP0
Change in
V.54 Detector
(SLBP)
Change in
V.54 Detector
(SLBP)
Change in
V.54 Detector
(SLBP)
Change in
V.54 Detector
(SLBP)
Port #15
Port #14
Port #1
Port #0
43 of 203
DS3134
4.3.2 STATUS & INTERRUPT REGISTER DESCRIPTION
Register Name:
SM
Register Description: Status Master Register
Register Address:
0020h
7
6
5
4
3
2
1
0
n/a
n/a
n/a
PPERR
PSERR
SBERT
STCOFA SRCOFA
15
14
13
12
11
10
9
8
LBINT
LBE
n/a
n/a
n/a
n/a
n/a
n/a
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
Bit 0 / Status Bit for Receive Change Of Frame Alignment (SRCOFA). This status bit will be set to a
one if one or more of the receive ports has experienced a Change Of Frame Alignment (COFA) event.
The host must read the RCOFA bit in the Receive Port Control Registers (RP[n]CR) of each active port to
determine which port or ports has seen the COFA. The SRCOFA bit will be cleared when read and will
not be set again, until one or more receive ports has experienced another COFA. If enabled via the
SRCOFA bit in the Interrupt Mask for SM (ISM), the setting of this bit will cause a hardware interrupt at
the PCI Bus via the PINTA* signal pin and also at the LINT* if the Local Bus is in the Configuration
Mode.
Bit 1 / Status Bit for Transmit Change Of Frame Alignment (STCOFA). This status bit will be set to
a one if one or more of the transmit ports has experienced a Change Of Frame Alignment (COFA) event.
The host must read the TCOFA bit in the Transmit Port Control Registers (TP[n]CR) of each active port
to determine which port or ports has seen the COFA. The STCOFA bit will be cleared when read and
will not be set again, until one or more transmit ports has experienced another COFA. If enabled via the
STCOFA bit in the Interrupt Mask for SM (ISM), the setting of this bit will cause a hardware interrupt at
the PCI Bus via the PINTA* signal pin and also at the LINT* if the Local Bus is in the Configuration
Mode.
Bit 2 / Status Bit for Change of State in BERT (SBERT). This status bit will be set to a one if there is
a major change of state in the BERT receiver. A major change of state is defined as either a change in the
receive synchronization (i.e. the BERT has gone into or out of receive synchronization), a bit error has
been detected, or an overflow has occurred in either the Bit Counter or the Error Counter. The Host must
read the status bits of the BERT in the BERT Status Register (BERTEC0) to determine the change of
state. The SBERT bit will be cleared when read and will not be set again until the BERT has experienced
another change of state. If enabled via the SBERT bit in the Interrupt Mask for SM (ISM), the setting of
this bit will cause a hardware interrupt at the PCI Bus via the PINTA* signal pin and also at the LINT* if
the Local Bus is in the Configuration Mode.
Bit 3 / Status Bit for PCI System Error (PSERR). This status bit is a software version of the PCI Bus
hardware pin PSERR. It will be set to a one if the PCI Bus detects an address parity error or other PCI
Bus error. The PSERR bit will be cleared when read and will not be set again until another PCI Bus error
has occurred. If enabled via the PSERR bit in the Interrupt Mask for SM (ISM), the setting of this bit will
cause a hardware interrupt at the PCI Bus via the PINTA* signal pin and also at the LINT* if the Local
Bus is in the Configuration Mode. This status bit is also reported in the Control/Status register in the PCI
Configuration registers, see Section 9 for more details.
44 of 203
DS3134
Bit 4 / Status Bit for PCI System Error (PPERR). This status bit is a software version of the PCI Bus
hardware pin PPERR. It will be set to a one if the PCI Bus detects parity errors on the PAD and PCBE*
buses as experienced or reported by a target. The PPERR bit will be cleared when read and will not be set
again until another parity error has been detected. If enabled via the PPERR bit in the Interrupt Mask for
SM (ISM), the setting of this bit will cause a hardware interrupt at the PCI Bus via the PINTA* signal pin
and also at the LINT* if the Local Bus is in the Configuration Mode. This status bit is also reported in the
Control/Status register in the PCI Configuration registers, see Section 9 for more details.
Bit 14 / Status Bit for Local Bus Error (LBE). This status bit applies to the Local Bus when it is
operate d in the PCI Bridge Mode. It will be set to a one when the Local Bus LRDY* signal is not
detected within nine LCLK periods. This indicates to the Host that an aborted Local Bus access has
occurred. If enabled via the LBE bit in the Interrupt Mask for SM (ISM), the setting of this bit will cause a
hardware interrupt at the PCI Bus via the PINTA* signal pin and also at the LINT* if the Local Bus is in
the Configuration Mode. The LBE bit is meaningless when the Local Bus is operated in the configuration
mode and should be ignored.
Bit 15 / Status Bit for Local Bus Interrupt (LBINT). This status bit will be set to a one if the Local
Bus LINT* signal has been detected as asserted. This status bit is only valid when the Local Bus is
operated in the PCI Bridge Mode. The LBINT bit will be cleared when read and will not be set again
until once again the LINT* signal pin has been detected as asserted. If enabled via the LBINT bit in the
Interrupt Mask for SM (ISM), the setting of this bit will cause a hardware interrupt at the PCI Bus via the
PINTA* signal pin. The LBINT bit is meaningless when the Local Bus is operated in the configuration
mode and should be ignored.
Register Name:
ISM
Register Description: Interrupt Mask Register for SM
Register Address:
0024h
7
6
5
4
3
2
1
0
n/a
n/a
n/a
PPERR
PSERR
SBERT STCOFA SRCOFA
15
14
13
12
11
10
9
8
LBINT
LBE
n/a
n/a
n/a
n/a
n/a
n/a
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
Bit 0 / Status Bit for Receive Change Of Frame Alignment (SRCOFA).
0 = interrupt masked
1 = interrupt unmasked
Bit 1 / Status Bit for Transmit Change Of Frame Alignment (STCOFA).
0 = interrupt masked
1 = interrupt unmasked
Bit 2 / Status Bit for Change of State in BERT (SBERT).
0 = interrupt masked
1 = interrupt unmasked
45 of 203
DS3134
Bit 3 / Status Bit for PCI System Error (PSERR).
0 = interrupt masked
1 = interrupt unmasked
Bit 4 / Status Bit for PCI System Error (PPERR).
0 = interrupt masked
1 = interrupt unmasked
Bit 14 / Status Bit for Local Bus Error (LBE).
0 = interrupt masked
1 = interrupt unmasked
Bit 15 / Status Bit for Local Bus Interrupt (LBINT).
0 = interrupt masked
1 = interrupt unmasked
Register Name:
SV54
Register Description: Status Register for the Receive V.54 Detector
Register Address:
0030h
7
6
5
4
3
2
1
0
SLBP7
SLBP6
SLBP5
SLBP4
SLBP3
SLBP2
SLBP1
SLBP0
15
14
13
12
11
10
9
8
SLBP15 SLBP14 SLBP13 SLBP12 SLBP11 SLBP10
SLBP9
SLBP8
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
Bits 0 to 15 / Status Bit for Change of State in Receive V.54 Loopback Detector (SLBP0 to
SLBP15). These status bits will be set to a one when the V.54 loopback detector within the port has
either timed out in its search for the loop up pattern or it has detected and validated the loop up or down
pattern. There is one status bit per port. The Host must read the VTO and VLB status bits in RP[n]CR
register of the corresponding port to determine the exact status of the V.54 detector. If the V.54 detector
has timed out in it's search for the loop up code (VTO = 1), then SLBP will be continuously set until the
Host resets the V.54 detector by toggling the VRST bit in RP[n]CR. If enabled via the SLBP[n] bit in the
Interrupt Mask for SV54 (ISV54), the setting of these bits will cause a hardware interrupt at the PCI Bus
via the PINTA* signal pin and also at the LINT* if the Local Bus is in the Configuration Mode. See
Section 5 for specific details on the operation of the V.54 loopback detector.
46 of 203
DS3134
Register Name:
ISV54
Register Description: Interrupt Mask Register for SV54
Register Address:
0034h
7
6
5
4
3
2
1
0
SLBP7
SLBP6
SLBP5
SLBP4
SLBP3
SLBP2
SLBP1
SLBP0
15
14
13
12
11
10
9
8
SLBP15 SLBP14 SLBP13 SLBP12 SLBP11 SLBP10
SLBP9
SLBP8
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
Bits 0 to 15 / Status Bit for Change of State in Receive V.54 Loopback Detector (SLBP0 to
SLBP15).
0 = interrupt masked
1 = interrupt unmasked
Register Name:
SDMA
Register Description: Status Register for DMA
Register Address:
0028h
7
6
5
4
3
2
1
0
RLBRE
RLBR
ROVFL RLENC RABRT RCRCE
n/a
n/a
15
14
13
12
11
10
9
8
TDQWE TDQW
TPQR
TUDFL RDQWE RDQW
RSBRE
RSBR
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
Bit 2 / Status Bit for Receive HDLC CRC Error (RCRCE). This status bit will be set to a one if any
of the receive HDLC channels experiences a CRC check sum error. The RCRCE bit will be cleared when
read and will not be set again until another CRC check sum error has occurred. If enabled via the RCRCE
bit in the Interrupt Mask for SDMA (ISDMA), the setting of this bit will cause a hardware interrupt at the
PCI Bus via the PINTA* signal pin and also at the LINT* if the Local Bus is in the Configuration Mode.
Bit 3 / Status Bit for Receive HDLC Abort Detected (RABRT). This status bit will be set to a one if
any of the receive HDLC channels detects an abort. The RABRT bit will be cleared when read and will
not be set again until another abort has been detected. If enabled via the RABRT bit in the Interrupt Mask
for SDMA (ISDMA), the setting of this bit will cause a hardware interrupt at the PCI Bus via the PINTA*
signal pin and also at the LINT* if the Local Bus is in the Configuration Mode.
Bit 4 / Status Bit for Receive HDLC Length Check (RLENC). This status bit will be set to a one if
any of the HDLC channels:
- Exceeds the octet length count (if so enabled to check for octet length)
- Receives a HDLC packet that does not meet the minimum length criteria of either 4 or 6 bytes
- Experiences a non-integral number of octets in between opening and closing flags.
The RLENC bit will be cleared when read and will not be set again until another length violation has
occurred. If enabled via the RLENC bit in the Interrupt Mask for SDMA (ISDMA), the setting of this bit
47 of 203
DS3134
will cause a hardware interrupt at the PCI Bus via the PINTA* signal pin and also at the LINT* if the
Local Bus is in the Configuration Mode.
Bit 5 / Status Bit for Receive FIFO Overflow (ROVFL). This status bit will be set to a one if any of
the HDLC channels experiences an overflow in the receive FIFO. The ROVFL bit will be cleared when
read and will not be set again until another overflow has occurred. If enabled via the ROVFL bit in the
Interrupt Mask for SDMA (ISDMA), the setting of this bit will cause a hardware interrupt at the PCI Bus
via the PINTA* signal pin and also at the LINT* if the Local Bus is in the Configuration Mode.
Bit 6 / Status Bit for Receive DMA Large Buffer Read (RLBR). This status bit will be set to a one
each time the Receive DMA completes a single read or a burst read of the Large Buffer Free Queue. The
RLBR bit will be cleared when read and will not be set again, until another read of the Large Buffer Free
Queue has occurred. If enabled via the RLBR bit in the Interrupt Mask for SDMA (ISDMA), the setting
of this bit will cause a hardware interrupt at the PCI Bus via the PINTA* signal pin and also at the LINT*
if the Local Bus is in the Configuration Mode.
Bit 7 / Status Bit for Receive DMA Large Buffer Read Error (RLBRE). This status bit will be set to
a one each time the Receive DMA tries to read the Large Buffer Free Queue and it is empty. The RLBRE
bit will be cleared when read and will not be set again, until another read of the Large Buffer Free Queue
detects that it is empty. If enabled via the RLBRE bit in the Interrupt Mask for SDMA (ISDMA), the
setting of this bit will cause a hardware interrupt at the PCI Bus via the PINTA* signal pin and also at the
LINT* if the Local Bus is in the Configuration Mode.
Bit 8 / Status Bit for Receive DMA Small Buffer Read (RSBR). This status bit will be set to a one
each time the Receive DMA completes a single read or a burst read of the Small Buffer Free Queue. The
RSBR bit will be cleared when read and will not be set again, until another read of the Small Buffer Free
Queue has occurred. If enabled via the RSBR bit in the Interrupt Mask for SDMA (ISDMA), the setting
of this bit will cause a hardware interrupt at the PCI Bus via the PINTA* signal pin and also at the LINT*
if the Local Bus is in the Configuration Mode.
Bit 9 / Status Bit for Receive DMA Small Buffer Read Error (RSBRE). This status bit will be set to a
one each time the Receive DMA tries to read the Small Buffer Free Queue and it is empty. The RSBRE
bit will be cleared when read and will not be set again, until another read of the Small Buffer Free Queue
detects that it is empty. If enabled via the RSBRE bit in the Interrupt Mask for SDMA (ISDMA), the
setting of this bit will cause a hardware interrupt at the PCI Bus via the PINTA* signal pin and also at the
LINT* if the Local Bus is in the Configuration Mode.
Bit 10 / Status Bit for Receive DMA Done Queue Write (RDQW). This status bit will be set to a one
when the Receive DMA writes to the Done Queue. Based of the setting of the Receive Done Queue
Threshold Setting (RDQT0 to RDQT2) bits in the Receive DMA Queues Control (RDMAQ) register, this
bit will be set either after each write or after a programmable number of writes from 2 to 128. See
Section 8.1.4 for more details. The RDQW bit will be cleared when read and will not be set again until
another write to the Done Queue has occurred. If enabled via the RDQW bit in the Interrupt Mask for
SDMA (ISDMA), the setting of this bit will cause a hardware interrupt at the PCI Bus via the PINTA*
signal pin and also at the LINT* if the Local Bus is in the Configuration Mode.
48 of 203
DS3134
Bit 11 / Status Bit for Receive DMA Done Queue Write Error (RDQWE). This status bit will be set
to a one each time the Receive DMA tries to write to the Done Queue and it is full. The RDQWE bit will
be cleared when read and will not be set again until another write to the Done Queue detects that it is full.
If enabled via the RDQWE bit in the Interrupt Mask for SDMA (ISDMA), the setting of this bit will
cause a hardware interrupt at the PCI Bus via the PINTA* signal pin and also at the LINT* if the Local
Bus is in the Configuration Mode.
Bit 12 / Status Bit for Transmit FIFO Underflow (TUDFL). This status bit will be set to a one if any
of the HDLC channels experiences an underflow in the transmit FIFO. The TUDFL bit will be cleared
when read and will not be set again until another underflow has occurred. If enabled via the TUDFL bit
in the Interrupt Mask for SDMA (ISDMA), the setting of this bit will cause a hardware interrupt at the
PCI Bus via the PINTA* signal pin and also at the LINT* if the Local Bus is in the Configuration Mode.
Bit 13 / Status Bit for Transmit DMA Pending Queue Read (TPQR). This status bit will be set to a
one each time the Transmit DMA reads the Pending Queue. The TPQR bit will be cleared when read and
will not be set again until another read of the Pending Queue has occurred. If enabled via the TPQR bit in
the Interrupt Mask for SDMA (ISDMA), the setting of this bit will cause a hardware interrupt at the PCI
Bus via the PINTA* signal pin and also at the LINT* if the Local Bus is in the Configuration Mode.
Bit 14 / Status Bit for Transmit DMA Done Queue Write (TDQW). This status bit will be set to a one
when the Transmit DMA writes to the Done Queue. Based of the setting of the Transmit Done Queue
Threshold Setting (TDQT0 to TDQT2) bits in the Transmit DMA Queues Control (TDMAQ) register,
this bit will be set either after each write or after a programmable number of writes from 2 to 128. See
Section 8.2.4 for more details. The TDQW bit will be cleared when read and will not be set again until
another write to the Done Queue has occurred. If enabled via the TDQW bit in the Interrupt Mask for
SDMA (ISDMA), the setting of this bit will cause a hardware interrupt at the PCI Bus via the PINTA*
signal pin and also at the LINT* if the Local Bus is in the Configuration Mode.
Bit 15 / Status Bit for Transmit DMA Done Queue Write Error (TDQWE). This status bit will be set
to a one each time the Transmit DMA tries to write to the Done Queue and it is full. The TDQWE bit
will be cleared when read and will not be set again until another write to the Done Queue detects that it is
full. If enabled via the TDQWE bit in the Interrupt Mask for SDMA (ISDMA), the setting of this bit will
cause a hardware interrupt at the PCI Bus via the PINTA* signal pin and also at the LINT* if the Local
Bus is in the Configuration Mode.
49 of 203
DS3134
Register Name:
ISDMA
Register Description: Interrupt Mask Register for SDMA
Register Address:
002Ch
7
6
5
4
3
2
1
0
RLBRE
RLBR
ROVFL RLENC RABRT RCRCE
n/a
n/a
15
14
13
12
11
10
9
8
TDQWE TDQW
TPQR
TUDFL RDQWE RDQW
RSBRE
RSBR
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
Bit 2 / Status Bit for Receive HDLC CRC Error (RCRCE).
0 = interrupt masked
1 = interrupt unmasked
Bit 3 / Status Bit for Receive HDLC Abort Detected (RABRT).
0 = interrupt masked
1 = interrupt unmasked
Bit 4 / Status Bit for Receive HDLC Length Check (RLENC).
0 = interrupt masked
1 = interrupt unmasked
Bit 5 / Status Bit for Receive FIFO Overflow (ROVFL).
0 = interrupt masked
1 = interrupt unmasked
Bit 6 / Status Bit for Receive DMA Large Buffer Read (RLBR).
0 = interrupt masked
1 = interrupt unmasked
Bit 7 / Status Bit for Receive DMA Large Buffer Read Error (RLBRE).
0 = interrupt masked
1 = interrupt unmasked
Bit 8 / Status Bit for Receive DMA Small Buffer Read (RSBR).
0 = interrupt masked
1 = interrupt unmasked
Bit 9 / Status Bit for Receive DMA Small Buffer Read Error (RSBRE).
0 = interrupt masked
1 = interrupt unmasked
Bit 10 / Status Bit for Receive DMA Done Queue Write (RDQW).
0 = interrupt masked
1 = interrupt unmasked
50 of 203
DS3134
Bit 11 / Status Bit for Receive DMA Done Queue Write Error (RDQWE).
0 = interrupt masked
1 = interrupt unmasked
Bit 12 / Status Bit for Transmit FIFO Underflow (TUDFL).
0 = interrupt masked
1 = interrupt unmasked
Bit 13 / Status Bit for Transmit DMA Pending Queue Read (TPQR).
0 = interrupt masked
1 = interrupt unmasked
Bit 14 / Status Bit for Transmit DMA Done Queue Write (TDQW).
0 = interrupt masked
1 = interrupt unmasked
Bit 15 / Status Bit for Transmit DMA Done Queue Write Error (TDQWE).
0 = interrupt masked
1 = interrupt unmasked
4.4 TEST REGISTER DESCRIPTION
Register Name:
TEST
Register Description: Test Register
Register Address:
0050h
7
6
5
4
3
2
1
0
n/a
n/a
n/a
n/a
n/a
n/a
n/a
FT
15
14
13
12
11
10
9
8
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
Bit 0 / Factory Test (FT).
This bit is used by the factory to place the DS3134 into the test mode. For normal device operation, this
bit should be set to zero whenever this register is written to. Setting this bit places the RAMs into a low
power standby mode.
Bit 1 to 15 / Device internal test bits. Bits 1 to 15 shown in the above table is for CHATEAU internal
(Dallas Semiconductor) tests use, not user test mode controls. Values of these bits should always be “0”.
If any of these bits are set to “1” device will not function properly.
51 of 203
DS3134
SECTION 5: LAYER ONE
5.1 GENERAL DESCRIPTION
The Layer One Block is shown in Figure 5.1A. Each of the 16 Layer One ports on the DS3134 can be
configured to support either a channelized application or an unchannelized application. Users can mix the
applications on the ports as needed. Some or all of the ports can be channelized while the others can be
configured as unchannelized. A channelized application is defined as one that requires a 8 kHz
synchronization pulse to subdivide the serial data stream into a set of 8-bit DS0 channels (also called
timeslots) which are Time Division Multiplexed (TDM) one after another. Ports running a channelized
application require an 8 kHz pulse at the RS and TS signals. An unchannelized application is defined as a
synchronous clock and data interface. No synchronization pulse is required and the RS and TS signals are
forced low in this application. Section 14 contains examples of some various configurations.
In channelized applications, the Layer One ports can be configured to operate in one of four modes as
shown in Table 5.1A below. Each port is capable of handling one, two, or four T1/E1 data streams.
When more than one T1/E1 data stream is applied to the port, the individual T1/E1 data streams must be
TDM into a single data stream at either a 4.096 MHz or 8.192 MHz data rate. Since the DS3134 can map
any HDLC channel to any DS0 channel, it can support any form (byte interleaved, frame interleaved, etc.)
of TDM that the application may require. On a DS0 by DS0 basis, the DS3134 can be configured to
process all 8 bits (64 kbps), the seven most significant bits (56 kbps), or no data.
CHANNELIZED PORT MODES Table 5.1A
Mode
T1 (1.544 MHz)
E1 (2.048 MHz)
4.096 MHz
8.192 MHz
Description
N x 64 kbps or N x 56 kbps; where N = 1 to 24 (one T1 data stream)
N x 64 kbps or N x 56 kbps; where N = 1 to 32 (one T1 or E1 data stream)
N x 64 kbps or N x 56 kbps; where N = 1 to 64 (two T1 or E1 data streams)
N x 64 kbps or N x 56 kbps; where N = 1 to 128. (four T1 or E1 data streams)
Each port in the Layer One Block is connected to a Slow HDLC Engine. The Slow HDLC Engine is
capable of handling channelized applications at speeds up to 8.192 Mbps and unchannelized applications
at speeds of up to 10 Mbps. Ports 0 and 1 have the added capability of Fast HDLC Engines that are
capable of only handling unchannelized applications but at speeds of up to 52 MHz.
Each port has an associated Receive Port Control Register (RP[n]CR where n = 0 to 15) and a Transmit
Port Control Register (TP[n]CR where n = 0 to 15). These control registers are defined in detail in
Section 5.2 and they control all of the circuitry in the Layer One Block with the exception of the Layer
One State Machine which is shown in the center of the Block Diagram in Figure 5.1A.
52 of 203
DS3134
Each port contains a Layer One State Machine, which connects directly to the Slow HDLC Engine. The
Layer One State Machine prepares the raw incoming data for the Slow HDLC Engine and grooms the
outgoing data from the Slow HDLC Engine. The Layer One State Machine performs a number of tasks,
which include:
- Assigning the HDLC channel number to the incoming & outgoing data
- Channelized Local and Network loopbacks
- Channelized selection of 64 kbps, 56 kbps, or no data
- Channelized transmits DS0 channel fill of all ones
- Routing data to and from the BERT function
- Routing data to the V.54 loop pattern detector.
The DS3134 has a set of three registers per DS0 channel for each port, which determine how each DS0
channel will be configured. These three registers are defined in Section 5.3. If the Fast (52 Mbps) HDLC
Engine is enabled on Port 0, then HDLC Channel 1 is assigned to it and likewise HDLC Channel 2 will
be assigned to the Fast HDLC Engine on Port 2 if it is enabled.
The DS3134 contains an onboard full-featured Bit Error Rate Tester (BERT) function, which is capable
of generating and detecting both pseudorandom and repeating serial bit patterns. The BERT function is
a shared resource among the 16 ports on the DS3134 and it can only be assigned to one port at a time.
The BERT function can be used in both channelized and unchannelized applications and at speeds up to
52 MHz. In channelized applications, data can be routed to and from any combination of DS0 channels
that are being used on the port. The details on the BERT function are covered in Section 5.5.
The Layer 1 Block also contains a V.54 detector. Each of the 16 ports within the DS3134 contains a V.54
loop pattern detector on the receive side. The device can search for the V.54 loop up and down patterns
in both channelized and unchannelized applications at speeds up to 10 MHz. In channelized applications,
the device can be configured to search for the patterns in any combination of DS0 channels. Section 5.4
describes all of the details on the V.54 detector.
53 of 203
DS3134
LAYER ONE BLOCK DIAGRAM Figure 5.1A
1 of 16
RC
RS
RD
Local
LoopBack
(LLB)
V.54
Detector
Invert
Clock /
Data /
Sync
LLB
TC
TS
TD
Force
All
Ones
Port
0&1
Only
OverSample
with
PCLK
Receive
UNLB
Invert
Clock /
Data /
Sync
BERT/
Fast
HDLC
Mux
OverSample
with
PCLK
Layer One
State Machine
PORT
RAM
(see
Sec.
5.3)
UnChannelized
Network
Loopback
(UNLB)
Channelized
Local
LoopBack
(CLLB)
Channelized
Network
LoopBack
(CNLB)
SLOW
HDLC
From
(One
per
Port)
Ports 0 & 1 Only
FAST
HDLC
l1_bd
54 of 203
FIFO
Block
Transmit
BERT Mux
(see Figure 5.5A)
To /
DS3134
PORT TIMING (FOR CHANNELIZED AND UNCHANNELIZED APPLICATIONS)
Figure 5.1B
RC[n] / TC[n]
Normal Mode
RC[n] / TC[n]
Inverted Mode
Bit 191 or 254
or 510 or 1022
RD[n]
TD[n]
Bit 192 or 255
or 511 or 1023
Last Bit of
the Frame
Bit 0
Bit 1
First Bit of
the Frame
RS[n] / TS[n]
0 Clock Early &
Not Inverted
RS[n] / TS[n]
1/2 Clock Early &
Inverted
RS[n] / TS[n]
1 Clock Early &
Not Inverted
RS[n] / TS[n]
2 Clocks Early &
Not Inverted
tdm_tim
55 of 203
DS3134
5.2 PORT REGISTER DESCRIPTIONS
Receive Side Control Bits (one each for all 16 ports)
Register Name:
RP[n]CR where n = 0 to 15 for each Port
Register Description: Receive Port [n] Control Register
Register Address:
See the Register Map in Section 3
7
6
5
4
3
2
1
0
RSS1
RSS0
RSD1
RSD0
VRST
RISE
RIDE
RICE
15
14
13
12
11
10
9
8
RCOFA
IERC
VLB
VTO
n/a
LLB
RUEN
RP[i]HS
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
Bit 0 / Invert Clock Enable (RICE).
0 = do not invert clock (normal mode)
1 = invert clock (inverted clock mode)
Bit 1 / Invert Data Enable (RIDE).
0 = do not invert data (normal mode)
1 = invert data (inverted data mode)
Bit 2 / Invert Sync Enable (RISE).
0 = do not invert sync pulse (normal mode)
1 = invert sync pulse (inverted sync pulse mode)
Bit 3 / V.54 Detector Reset (VRST). Toggling this bit from a 0 to a 1 and then back to a 0 causes the
internal V.54 detector to be reset and begin searching for the V.54 loop up pattern. See Section 5.4 for
more details on the operation of the V.54 detector.
Bit 4 / Sync Delay Bit 0 (RSD0).
Bit 5 / Sync Delay Bit 1 (RSD1).
These two bits define the format of the sync signal that will be applied to the RS[n] input. These bits are
ignored if the port has been configured to operate in an unchannelized fashion (RUEN = 1).
00 = sync pulse is 0 clocks early
01 = sync pulse is 1/2 clock early
10 = sync pulse is 1 clock early
11 = sync pulse is 2 clocks early
56 of 203
DS3134
Bit 6 / Sync Select Bit 0 (RSS0).
Bit 7 / Sync Select Bit 1 (RSS1).
These 2 bits select the mode in which each port is to be operated. Each port can be configured to accept
24, 32, 64, or 128 DS0 channels at an 8 kHz rate. These bits are ignored if the port has been configured
to operate in an unchannelized fashion (RUEN = 1).
00 = T1 Mode (24 DS0 channels & 193 RC clocks in between RS sync signals)
01 = E1 Mode (32 DS0 channels & 256 RC clocks in between RS sync signals)
10 = 4.096 MHz Mode (64 DS0 channels & 512 RC clocks in between RS sync signals)
11 = 8.192 MHz Mode (128 DS0 channels & 1024 RC clocks in between RS sync signals)
Bit 8 / Port 0 High Speed Mode (RP0(1)HS). If enabled, the Port 0(1) Layer State Machine logic is
defeated and RC0(1) and RD0(1) are routed to some dedicated high speed HDLC processing logic. Only
present in RP0CR and RP1CR. Bit 8 is not assigned in Ports 2 through 15.
0 = disabled
1 = enabled
Bit 9 / Unchannelized Enable (RUEN). When enabled, this bit forces the port to operate in an
unchannelized fashion. When disabled, the port will operate in a channelized mode.
0 = channelized mode
1 = unchannelized mode
Bit 10 / Local Loopback Enable (LLB). This loopback routes transmit data back to the receive port. It
can be used in both channelized and unchannelized port operating modes, even on ports 0 & 1 operating
at speeds up to 52 MHz. See Figure 5.1A. In channelized applications, a per-channel loopback can be
realized by using the Channelized Local LoopBack (CLLB) function. See Section 5.3 for details on
CLLB.
0 = loopback disabled
1 = loopback enabled
Bit 12 / V.54 Time Out (VTO). This read only bit reports the real time status of the V.54 detector. It
will be set to a one when the V.54 detector has finished searching for the V.54 loop up pattern and has not
detected it. This indicates to the Host that the V.54 detector can now be used to search for the V.54 loop
up pattern on other HDLC channels and the Host can initiate this by configuring the RV54 bits in the
RP[n]CR register and then toggling the VRST control bit. See Section 5.4 for more details on how the
V.54 detector operates.
Bit 13 / V.54 Loopback (VLB). This read only bit reports the real time status of the V.54 detector. It
will be set to a one when the V.54 detector has verified that a V.54 loop up pattern has been seen. When
set, it will remain set until either the V.54 loop down pattern is seen or the V.54 detector is reset by the
Host (i.e. by toggling VRST). See Section 5.4 for more details on how the V.54 detector operates.
Bit 14 / Interrupt Enable for RCOFA (IERC).
0 = interrupt masked
1 = interrupt enabled
57 of 203
DS3134
Bit 15 / COFA Status Bit (RCOFA). This latched read only status bit will be set if a Change Of Frame
Alignment is detected. The COFA is detected by sensing that a sync pulse has occurred during a clock
period that was not the first bit of the 193/256/512/1024 bit frame. This bit will be reset when read and it
will not be set again until another COFA has occurred.
Transmit Side Control Bits (one each for all 16 ports)
Register Name:
TP[n]CR where n = 0 to 15 for each Port
Register Description: Transmit Port [n] Control Register
Register Address:
See the Register Map in Section 3
7
6
5
4
3
2
1
0
TSS1
TSS0
TSD1
TSD0
TFDA1*
TISE
TIDE
TICE
15
14
13
12
11
10
9
8
TCOFA
IETC
n/a
n/a
TUBS
UNLB
TUEN
TP[i]HS
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
Bit 0 / Invert Clock Enable (TICE).
0 = do not invert clock (normal mode)
1 = invert clock (inverted clock mode)
Bit 1 / Invert Data Enable (TIDE).
0 = do not invert data (normal mode)
1 = invert data (inverted data mode)
Bit 2 / Invert Sync Enable (TISE).
0 = do not invert sync pulse (normal mode)
1 = invert sync pulse (inverted sync pulse mode)
Bit 3 / Force Data All 1's (TFDA1*).
0 = force all data at TD to be one
1 = allow data to be transmitted normally
Bit 4 / Sync Delay Bit 0 (TSD0).
Bit 5 / Sync Delay Bit 1 (TSD1).
These 2 bits define the format of the sync signal that will be applied to the TS[n] input. These bits are
ignored if the port has been configured to operate in an unchannelized fashion (TUEN = 1).
00 = sync pulse is 0 clocks early
01 = sync pulse is 1/2 clock early
10 = sync pulse is 1 clock early
11 = sync pulse is 2 clocks early
58 of 203
DS3134
Bit 6 / Sync Select Bit 0 (TSS0).
Bit 7 / Sync Select Bit 1 (TSS1).
These 2 bits select the mode in which each port is to be operated. Each port can be configured to accept
24, 32, 64, or 128 DS0 channels at an 8 kHz rate. These bits are ignored if the port has been configured
to operate in an unchannelized fashion (TUEN = 1).
00 = T1 Mode (24 DS0 channels & 193 RC clocks in between TS sync signals)
01 = E1 Mode (32 DS0 channels & 256 RC clocks in between TS sync signals)
10 = 4.096 MHz Mode (64 DS0 channels & 512 RC clocks in between TS sync signals)
11 = 8.192 MHz Mode (128 DS0 channels & 1024 RC clocks in between TS sync signals)
Bit 8 / Port 0 High Speed Mode (TP0(1)HS). If enabled, the Port 0(1) Layer 1 State Machine logic is
defeated and TC0(1) and TD0(1) are routed to some dedicated high speed HDLC processing logic. Only
present in TP0CR and TP1CR. Bit 8 is not assigned in Ports 2 through 15.
0 = disabled
1 = enabled
Bit 9 / Unchannelized Enable (TUEN). When enabled, this bit forces the port to operate in an
unchannelized fashion. When disabled, the port will operate in a channelized mode. This bit overrides
the Transmit Channel Enable (TCHEN) bit in the Transmit Layer 1 Configuration (T[n]CFG[j]) registers
which are described in Section 5.3.
0 = channelized mode
1 = unchannelized mode
Bit 10 / Unchannelized Network Loopback Enable (UNLB). See Figure 5.1A for details. This
loopback cannot be used for ports 0 & 1 when they are being operated at speeds greater than 10 MHz.
0 = loopback disabled
1 = loopback enabled
Bit 11 / Unchannelized BERT Select (TUBS). This bit is ignored if TUEN = 0. This bit overrides the
Transmit BERT (TBERT) bit in the Transmit Layer 1 Configuration (T[n]CFG[j]) registers which are
described in Section 5.3.
0 = source transmit data from the HDLC controller
1 = source transmit data from the BERT block
Bit 14 / Interrupt Enable for TCOFA (IETC).
0 = interrupt masked
1 = interrupt enabled
Bit 15 / COFA Status Bit (TCOFA). This latched read only status bit will be set if a Change Of Frame
Alignment is detected. A COFA is detected by sensing that a sync pulse has occurred during a clock
period that was not the first bit of the 193/256/512/1024 bit frame. This bit will be reset when read and it
will not be set again until another COFA has occurred.
59 of 203
DS3134
5.3 LAYER ONE CONFIGURATION REGISTER DESCRIPTION
There are three configuration registers for each DS0 channel on each port. These three registers are
shown in Figure 5.3A. As shown in Figure 5.1A, each of the 16 ports contains a PORT RAM, this
controls the Layer One State Machine. These 384 registers (three registers x 128 DS0 channels per port)
make up the PORT RAM for each port and they control and provide access to the Layer One State
Machine. These registers are accessed indirectly via the Channelized Port Register Data (CP[n]RD)
register. The Host must first write to the Channelized Port Register Data Indirect Select (CP[n]RDIS)
register to chose which DS0 channel and which channelized PORT RAM that it wishes to configure or
read. On power-up, the Host must write to all of the used R[n]CFG[j] and T[n]CFG[j] locations to make
sure that they are set into a known state.
LAYER ONE REGISTER SET Figure 5.3A
C[n]DAT[j]: Channelized DS0 Data
RDATA(8): Receive DS0 Data
msb
TDATA(8): Transmit DS0 Data
lsb
R[n]CFG[j]: Receive Configuration
RCH#(8): Receive HDLC Channel Number
msb
RCHEN RBERT
n/a
RV54
n/a
CLLB
lsb
T[n]CFG[j]: Transmit Configuration
TCH#(8): Transmit HDLC Channel Number
msb
TCHEN TBERT
n/a
n/a
CNLB
n/a
n/a
R56
lsb
TFAO
T56
Register Name:
CP[n]RDIS where n = 0 to 15 for each Port
Register Description: Channelized Port [n] Register Data Indirect Select
Register Address:
See the Register Map in Section 3
7
6
5
4
3
2
1
0
n/a
CHID6
CHID5
CHID4
CHID3
CHID2
CHID1
CHID0
15
14
13
12
11
10
9
8
IAB
IARW
n/a
n/a
n/a
n/a
CPRS1
CPRS0
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
Bits 0 to 6 / DS0 Channel ID (CHID0 to CHID6). The number of DS0 channels used depends on
whether the port has been configured for an unchannelized application or for a channelized application
and if set for a channelized application, then whether the port has been configured in the T1, E1, 4.096
MHz, or 8.192 MHz mode.
0000000 (00h) = DS0 Channel Number 0
1111111 (7Fh) = DS0 Channel Number 127
60 of 203
Port Mode
Unchannelized Mode (RUEN/TUEN = 1)
Channelized T1 Mode (RUEN/TUEN = 0 & RSS0/TSS0 = 0 & RSS1/TSS1 = 0)
Channelized E1 Mode (RUEN/TUEN = 0 & RSS0/TSS0 = 1 & RSS1/TSS1 = 0)
Channelized 4.096 MHz Mode (RUEN/TUEN = 0 & RSS0/TSS0 = 0 &
RSS1/TSS1 = 1)
Channelized 8.192 MHz Mode (RUEN/TUEN = 0 & RSS0/TSS0 = 1 &
RSS1/TSS1 = 1)
DS3134
DS0 Channels
Available
0
0 to 23
0 to 31
0 to 63
0 to 127
Bit 8 / Channelized PORT RAM Select Bit 0 (CPRS0).
Bit 9 / Channelized PORT RAM Select Bit 1 (CPRS1).
00 = Channelized DS0 Data (C[n]DAT[j])
01 = Receive Configuration (R[n]CFG[j])
10 = Transmit Configuration (T[n]CFG[j])
11 = illegal selection
Bit 14 / Indirect Access Read/Write (IARW). When the host wishes to read data from the internal
Channelized PORT RAM, this bit should be written to a one by the host. This causes the device to begin
obtaining the data from the DS0 channel location indicated by the CHID bits and the PORT RAM
indicated by the CPRS0 and CPRS1 bits. During the read access, the IAB bit will be set to one. Once the
data is ready to be read from the CP[n]RD register, the IAB bit will be set to zero. When the host wishes
to write data to the internal Channelized PORT RAM, this bit should be written to a zero by the host.
This causes the device to take the data that is currently present in the CP[n]RD register and write it to the
PORT RAM indicated by the CPRS0 and CPRS1 bits and the DS0 channel indicated by the CHID bits.
When the device has completed the write, the IAB will be set to zero.
Bit 15 / Indirect Access Busy (IAB). When an indirect read or write access is in progress, this read only
bit will be set to a one. During a read operation, this bit will be set to a one until the data is ready to be
read. It will be set to zero when the data is ready to be read. During a write operation, this bit will be set
to a one while the write is taking place. It will be set to zero once the write operation has completed.
61 of 203
DS3134
Register Name:
CP[n]RD where n = 0 to 15 for each Port
Register Description: Channelized Port [n] Register Data
Register Address:
See the Register Map in Section 3
7
6
5
4
3
2
1
0
CHD7
CHD6
CHD5
CHD4
CHD3
CHD2
CHD1
CHD0
15
14
13
12
11
10
9
8
CHD15
CHD14
CHD13
CHD12
CHD11
CHD10
CHD9
CHD8
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
Bits 0 to 15 / DS0 Channel Data (CHD0 to CHD15). The 16-bit data that is to either be written into or
read from the PORT RAM specified by the CP[n]RDIS register.
Port RAM Indirect Access Figure 5.3B
CP[n]RDIS
CP[n]RD
Port RAM (one each for all 16 Ports; n = 0 to 15)
C[n]DAT0
R[n]CFG0
T[n]CFG0
C[n]DAT1
R[n]CFG1
T[n]CFG1
C[n]DAT2
R[n]CFG2
T[n]CFG2
C[n]DAT3
R[n]CFG3
T[n]CFG3
C[n]DAT4
R[n]CFG4
T[n]CFG4
...
...
...
C[n]DAT126 R[n]CFG126 T[n]CFG126
C[n]DAT127 R[n]CFG127 T[n]CFG127
62 of 203
DS3134
Register Name:
C[n]DAT[j] where n = 0 to 15 for each Port & j = 0 to 127 for each DS0
Register Description: Channelized Layer 1 DS0 Data Register
Register Address:
Indirect Access Via CP[n]RD
7
6
5
4
3
2
1
RDATA(8): Receive DS0 Data
15
14
13
12
11
10
9
TDATA(8): Transmit DS0 Data
Note: Bits that are underlined are read only, all other bits are read-write.
0
8
Note: In normal device operation, the Host must never write to the C[n]DAT[j] registers.
Bits 0 to 7 / Receive DS0 Data (RDATA). This register holds the most current DS0 byte received. It is
used by the transmit side Layer One State Machine when Channelized Network LoopBack (CNLB) is
enabled.
Bits 8 to 15 / Transmit DS0 Data (TDATA). This register holds the most current DS0 byte transmitted.
It is used by the receive side Layer One State Machine when Channelized Local LoopBack (CLLB) is
enabled.
Register Name:
R[n]CFG[j] where n = 0 to 15 for each Port & j = 0 to 127 for each DS0
Register Description: Receive Layer 1 Configuration Register
Register Address:
Indirect Access via CP[n]RD
7
6
5
4
3
2
1
RCH#(8): Receive HDLC Channel Number
15
14
13
12
11
10
9
RCHEN RBERT
n/a
RV54
n/a
CLLB
n/a
Note: Bits that are underlined are read only, all other bits are read-write.
0
8
R56
Bits 0 to 7 / Receive Channel Number (RCH#). The CPU will load the number of the HDLC channel
associated with this particular DS0 channel. If the port is running in an unchannelized mode (RUEN = 1),
then the HDLC Channel Number only needs to be loaded into R[n]CFG0. If the Fast (52 Mbps) HDLC
Engine is enabled on Port 0, then HDLC Channel 1 is assigned to it and likewise HDLC Channel 2 will
be assigned to the Fast HDLC Engine on Port 2 if it is enabled. Hence, these HDLC channel numbers
should not be used if the Fast HDLC Engines are enabled.
00000000 (00h) = HDLC Channel Number 1 (also used for the Fast HDLC Engine on Port 0)
00000001 (01h) = HDLC Channel Number 2 (also used for the Fast HDLC Engine on Port 1)
00000010 (02h) = HDLC Channel Number 3
11111111 (FFh) = HDLC Channel Number 256
63 of 203
DS3134
Bit 8 / Receive 56 kbps (R56). If the Port is running a channelized application, this bit determines
whether the LSB of each DS0 should be processed or not. If this bit is set, then the LSB of each DS0
channel will not be routed to the HDLC controller (or the BERT if it has been enabled via the RBERT
bit). This bit does not affect the operation of the V.54 detector (it always searches on all 8 bits in the
DS0).
0 = 64 kbps (use all 8 bits in the DS0)
1 = 56 kbps (use only the first seven bits received in the DS0)
Bit 10 / Channelized Local LoopBack Enable (CLLB). Enabling this loopback forces the transmit data
to replace the receive data. This bit must be set for each and every DS0 channel that is to be looped back.
In order for the loopback to become active, the DS0 channel must be enabled (RCHEN = 1) and the DS0
channel must be set into the 64 kbps mode (R56 = 0).
0 = loopback disabled
1 = loopback enabled
Bit 12 / Receive V.54 Enable (RV54E). If this bit is cleared, this DS0 channel will not be examined to
see if the V.54 loop pattern is present. If set, the DS0 will be examined for the V.54 loop pattern. When
searching for the V.54 pattern within a DS0 channel, all 8 bits of the DS0 channel are examined
regardless of how the DS0 channel is configured (i.e. 64k or 56k).
0 = do not examine this DS0 channel for the V.54 loop pattern
1 = examine this DS0 channel for the V.54 loop pattern
Bit 14 / Route Data Into BERT (RBERT). Setting this bit will route the DS0 data into the BERT
function. If the DS0 channel has been configured for 56 kbps operation (R56 = 1), then the LSB of each
DS0 channel is not routed to the BERT block. In order for the data to make it to the BERT block, the
Host must also configure the BERT for the proper port via the Master Control register (see Section 4).
0 = do not route data to BERT
1 = route data to BERT
Bit 15 / Receive DS0 Channel Enable (RCHEN). This bit must be set for each active DS0 channel in a
channelized application. In a channelized application, although a DS0 channel is deactivated, the channel
can still be set up to route data to the V.54 detector and/or the BERT block. In addition, although a DS0
channel is active, the loopback function (CLLB = 1) overrides this activation and will route transmit data
back to the HDLC controller instead of the data coming in via the RD pin. In an unchannelized mode
(RUEN = 1), only the RCHEN bit in R[n]CFG0 needs to be configured.
0 = deactivated DS0 channel
1 = active DS0 channel
Register Name:
T[n]CFG[j] where n = 0 to 15 for each Port & j = 0 to 127 for each DS0
Register Description: Transmit Layer 1 Configuration Register
Register Address:
Indirect Access via CP[n]RD
7
6
5
4
3
2
1
TCH#(8): Transmit HDLC Channel Number
15
14
13
12
11
10
9
TCHEN TBERT
n/a
n/a
CNLB
n/a
TFAO
Note: Bits that are underlined are read only, all other bits are read-write.
64 of 203
0
8
T56
DS3134
Bits 0 to 7 / Transmit Channel Number (TCH#). The CPU will load the number of the HDLC channel
associated with this particular DS0 channel. If the port is running in an unchannelized mode (TUEN = 1),
then the HDLC Channel Number only needs to be loaded into T[n]CFG0. If the Fast (52 Mbps) HDLC
Engine is enabled on Port 0, then HDLC Channel 1 is assigned to it and likewise HDLC Channel 2 will
be assigned to the Fast HDLC Engine on Port 2 if it is enabled. Hence, these HDLC channel numbers
should not be used if the Fast HDLC Engines are enabled.
00000000 (00h) = HDLC Channel Number 1 (also used for the Fast HDLC Engine on Port 0)
00000001 (01h) = HDLC Channel Number 2 (also used for the Fast HDLC Engine on Port 1)
00000010 (02h) = HDLC Channel Number 3
11111111 (FFh) = HDLC Channel Number 256
Bit 8 / Transmit 56 kbps (T56). If the port is running a channelized application, this bit determines
whether the LSB of each DS0 should be processed or not. If this bit is set, then the LSB of each DS0
channel will not be routed from the HDLC controller (or the BERT if it has been enabled via the RBERT
bit) and the LSB bit position will be forced to a one.
0 = 64 kbps (use all 8 bits in the DS0)
1 = 56 kbps (use only the first 7 bits transmitted in the DS0; force the LSB to one)
Bit 9 / Transmit Force All Ones (TFAO). If this bit is set, then eight ones will be placed into the DS0
channel for transmission instead of the data that is being sourced from the HDLC controller. If this bit is
cleared, then the data from the HDLC controller will be transmitted. This bit is useful in instances when
Channelized Local LoopBack (CLLB) is being activated to keep the looped back data from being sent out
onto the network. This bit overrides TCHEN.
0 = transmit data from the HDLC controller
1 = force transmit data to all ones
Bit 11 / Channelized Network LoopBack Enable (CNLB). Enabling this loopback forces the receive
data to replace the transmit data. This bit must be set for each and every DS0 channel that is to be looped
back. This bit overrides TBERT, TFAO, and TCHEN.
0 = loopback disabled
1 = loopback enabled
Bit 14 / Route Data from BERT (TBERT). Setting this bit will route DS0 data to the TD pin from the
BERT block instead of from the HDLC controller. If the DS0 channel has been configured for 56 kbps
operation (T56 = 1), then the LSB of each DS0 channel will not be routed from the BERT block but will
be forced to a one instead. In order for the data to make it from the BERT block, the Host must also
configure the BERT for the proper port via the Master Control register (see Section 4). This bit overrides
TFAO and TCHEN.
0 = do not route data from BERT
1 = route data from BERT (override the data from the HDLC controller)
65 of 203
DS3134
Bit 15 / Transmit DS0 Channel Enable (TCHEN). This bit must be set for each active DS0 channel in
a channelized application. In a channelized application, although a DS0 channel is deactivated, the
channel can still be set up to route data from the BERT block. In addition, although a DS0 channel is
active, the loopback function (CNLB = 1) overrides this activation and will route receive data to the TD
pin instead of from the HDLC. In an unchannelized mode (TUEN = 1), only the TCHEN bit in T[n]CFG0
needs to be configured.
0 = deactivated DS0 channel
1 = active DS0 channel
5.4 RECEIVE V.54 DETECTOR
Each port within the device contains a V.54 loop pattern detector. V.54 is a pseudorandom pattern that
will be sent for at least 2 seconds followed immediately by an all ones pattern for at least two seconds if
the channel is to be placed into loopback. The exact pattern and sequence is defined in Annex B of ANSI
T1.403-1995.
When a port is configured for unchannelized operation (RUEN = 1), all of the data entering the port via
RD is routed to the V.54 detector. If the Host wishes not to utilize the V.54 detector, then the SLBP
status bits in the Status V.54 (SV54) register should be ignored and their corresponding interrupt mask
bits in ISV54 should be set to 0 to keep from disturbing the Host. Details on the status and interrupt bits
can be found in Section 4.
When the port is configured for channelized operation (RUEN = 0), then it is the Host's responsibility to
determine which DS0 channels should be searched for the V.54 pattern. In channelized applications, it
may be that there will be multiple HDLC channels that the Host wishes to look for the V.54 pattern in. If
this is true, then the Host will perform the routine shown in Table 5.4A. A flowchart of the same routine
is shown in Figure 5.4A
66 of 203
DS3134
Receive V.54 Search Routine Table 5.4A
Step #1: Set Up the Channel Search
The Host will determine in which DS0 channels the V.54 search is to take place by configuring the RV54
bit in the R[n]CFG[j] register. If this search sequence does not detect the V.54 pattern, then the Host can
pick some new DS0 channels and try again.
Step #2: Toggle VRST
Once the DS0 channels have been set, the Host will toggle the VRST bit in the RP[n]CR register and
begin monitoring the SLBP status bit.
Step #3: Wait for SLBP
The SLBP status bit reports any change of state in the V.54 search process. It can also generate a
hardware interrupt, see Section 4 for more details. When SLBP is set, then the Host knows that
something significant has occurred and that it should read the VLB and VTO real time status bits in the
RP[n]CR register.
Step #4: Read VTO & VLB
If VTO = 1, then the V.54 pattern did not appear in this set of channels and the Host can now reconfigure
the search in other DS0 channels and hence move back to Step #1.
If VLB = 1, then the V.54 loop up pattern has been detected and the channel should be placed into
loopback. A loopback can be invoked by the Host by configuring the CNLB bit in the T[n]CFG[j]
register for each DS0 channel that needs to be placed into loopback. Move back to Step #3.
If VLB = 0, if the DS0 channels are already in loopback, then the Host will monitor VLB to know when
the loop down pattern has been detected and hence when to take the channels out of loopback. The DS0
channels are taken out of loopback by again configuring the CNLB bits. Move on to Step #1.
67 of 203
DS3134
Receive V.54 Host Algorithm Figure 5.4A
ALGORITHM
Set Up the
DS0 Channel
Search
Toggle VRST
Wait for
SLBP = 1
Yes
VTO = 1?
NOTES
DS0 channels can be configured to search
for the V.54 loop pattern via the Receive
Layer 1 Configuration Register (see Section 5.3)
VRST is a control bit that is in the Receive
Port Control Register (see Section 5.2)
SLBP is a status bit that is reported
in the SV54 register (see Section 4.3)
VTO is a status bit that is in the Receive
Port Control Register (see Section 5.2)
No
Place DS0
Channels into
Loopback
Wait for
SLBP = 1
Take DS0
Channels out
of Loopback
DS0 channels can be placed into loopback
via the Receive Layer 1 Configuration Register
(see Section 5.3)
SLBP is a status bit that is reported
in the SV54 register (see Section 4.3)
DS0 channels can be taken out of loopback
via the Receive Layer 1 Configuration Register
(see Section 5.3)
v54host
68 of 203
DS3134
Receive V.54 State Machine Figure 5.4B
VRST = 1
VLB = 0
VTO = 0
SLBP = 0
CLK
V.54 State
Machine
Data
VRST (in RP[n]CR)
Time Out (VTO)
Loopback (VLB);
both in RP[n]CR
Change of
State in Status
(SLBP); in SV54
SYSCLK
Search for
Loop Up
Pattern for
32 VCLKs
Sysclk is used only to time
a 4 second timer. It is run into
a 2E27 counter which provides
a 4.03 second time out with a
33MHz clock and a 5.37 second
time out with a 25MHz clock
Sync = 0
Sync = 1
Reset 4 second timer;
wait for Loss of Sync or
All 1s (64 in a Row)
or for the 4 second
timer to expire
Sync = 0 or
4 Second Timer
Has Expired
All Ones
SLBP = 1
Search for
Loop Down
Pattern
VLB = 1
Sync = 0
Sync = 1
Sync = 0
wait for Loss of Sync or
All 1s (64 in a Row)
All Ones
VTO = 1
VLB = 0
SLBP = 1
69 of 203
v54sm
DS3134
5.5 BERT
The BERT Block is capable of generating and detecting the following patterns:
- The pseudorandom patterns 2E7, 2E11, 2E15, and QRSS
- A repetitive pattern from 1 to 32 bits in length
- Alternating (16-bit) words which flip every 1 to 256 words
The BERT receiver has a 32-bit Bit Counter and a 24-bit Error Counter. It can generate interrupts on
detecting a bit error, a change in synchronization, or if an overflow occurs in the Bit and Error Counters.
See Section 4 for details on status bits and interrupts from the BERT Block. To activate the BERT Block,
the Host must configure the BERT mux (see Figure 5.5A) and in channelized applications, the Host must
also configure the Layer One State Machine to send/obtain data to/from the BERT Block via the Layer
One Configuration Registers (see Section 5.3).
BERT Mux Diagram Figure 5.5A
Port 0 (slow)
Port 1 (slow)
Port 2 (slow)
Port 3 (slow)
Port 4 (slow)
SBERT Status Bit
in SM
BERT
Block
BERT
Mux
Port 5 (slow)
Port 13 (slow)
Internal Control &
Configuration Bus
Port 14 (slow)
Port 15 (slow)
Port 0 (fast)
bertbd
Port 1 (fast)
BERT Select (5)
In the Master Configuration
Register
70 of 203
DS3134
5.6 BERT REGISTER DESCRIPTION
BERT Register Set Figure 5.6A
BERTC0: BERT Control 0
n/a
TINV
RINV
msb
IESYNC IEBED
IEOF
BERTC1: BERT Control 1
EIB2
EIB1
EIB0
msb
PS2
PS1
PS0
LC
lsb
RESYNC
n/a
RPL3
RPL2
RPL1
RPL0
SBE
n/a
n/a
n/a
lsb
TC
Alternating Word Count
BERTRP0: BERT Repetitive Pattern Set 0 (lower word)
BERT Repetitive Pattern Set (lower byte)
msb
BERT Repetitive Pattern Set
lsb
BERTRP1: BERT Repetitive Pattern Set 1 (upper word)
BERT Repetitive Pattern Set
msb
BERT Repetitive Pattern Set (upper byte)
lsb
BERTBC0: BERT Bit Counter 0 (lower word)
BERT 32-Bit Bit Counter (lower byte)
msb
BERT 32-Bit Bit Counter
lsb
BERTBC1: BERT Bit Counter 0 (upper word)
BERT 32-Bit Bit Counter
msb
BERT 32-Bit Bit Counter (upper byte)
lsb
BERTEC0: BERT Error Counter 0 / Status
n/a
RA1
RA0
RLOS
BED
BBCO
msb
BERT 24-Bit Error Counter (lower byte)
BERTEC1: BERT Error Counter 1 (upper word)
BERT 24-Bit Error Counter
msb
BERT 24-Bit Error Counter (upper byte)
71 of 203
BECO
lsb
SYNC
lsb
DS3134
Register Name:
BERTC0
Register Description: BERT Control Register 0
Register Address:
0500h
7
6
5
4
3
2
1
0
n/a
TINV
RINV
PS2
PS1
PS0
LC
RESYNC
15
14
13
12
11
10
9
8
IESYNC IEBED
IEOF
n/a
RPL3
RPL2
RPL1
RPL0
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
Bit 0 / Force Resynchronization (RESYNC). A low to high transition will force the receive BERT
synchronizer to resynchronize to the incoming data stream. This bit should be toggled from low to high
whenever the host wishes to acquire synchronization on a new pattern. Must be cleared and set again for
a subsequent resynchronization. Note: Bit 2, 3 & 4 must be set, minimum of 64 system clock cycles,
before toggle the Resync bit (bit 0).
Bit 1 / Load Bit and Error Counters (LC). A low to high transition latches the current bit and error
counts into the host accessible registers BERTBC and BERTEC and clears the internal count. This bit
should be toggled from low to high whenever the host wishes to begin a new acquisition period. Must be
cleared and set again for a subsequent loads.
Bit 2 / Pattern Select Bit 0 (PS0).
Bit 3 / Pattern Select Bit 0 (PS1).
Bit 4 / Pattern Select Bit 1 (PS2).
000 = Pseudorandom Pattern 2E7 - 1
001 = Pseudorandom Pattern 2E11 - 1
010 = Pseudorandom Pattern 2E15 - 1
011 = Pseudorandom Pattern QRSS (2E20 - 1 with a one forced if the next 14 positions are zero)
100 = Repetitive Pattern
101 = Alternating Word Pattern
110 = illegal state
111 = illegal state
Bit 5 / Receive Invert Data Enable (RINV).
0 = do not invert the incoming data stream
1 = invert the incoming data stream
Bit 6 / Transmit Invert Data Enable (TINV).
0 = do not invert the outgoing data stream
1 = invert the outgoing data stream
Bit 8 / Repetitive Pattern Length Bit 0 (RPL0).
Bit 9 / Repetitive Pattern Length Bit 1 (RPL1).
Bit 10 / Repetitive Pattern Length Bit 2 (RPL2).
72 of 203
DS3134
Bit 11 / Repetitive Pattern Length Bit 3 (RPL3).
RPL0 is the LSB and RPL3 is the MSB of a nibble that describes the how long the repetitive pattern is.
The valid range is 17 (0000) to 32 (1111). These bits are ignored if the receive BERT is programmed for
a pseudorandom pattern. To create repetitive patterns less than 17 bits in length, the user must set the
length to an integer number of the desired length that is less than or equal to 32. For example, to create a
6 bit pattern, the user can set the length to 18 (0001) or to 24 (0111) or to 30 (1101).
Repetitive Pattern Length Map
Length
17 Bits
21 Bits
25 Bits
29 Bits
Code
0000
0100
1000
1100
Length
18 Bits
22 Bits
26 Bits
30 Bits
Code
0001
0101
1001
1101
Length
19 Bits
23 Bits
27 Bits
31 Bits
Code
0010
0110
1010
1110
Length
20 Bits
24 Bits
28 Bits
32 Bits
Code
0011
0111
1011
1111
Bit 13 / Interrupt Enable for Counter Overflow (IEOF). Allows the receive BERT to cause an
interrupt if either the Bit Counter or the Error Counter overflows.
0 = interrupt masked
1 = interrupt enabled
Bit 14 / Interrupt Enable for Bit Error Detected (IEBED). Allows the receive BERT to cause an
interrupt if a bit error is detected.
0 = interrupt masked
1 = interrupt enabled
Bit 15 / Interrupt Enable for Change of Synchronization Status (IESYNC). Allows the receive
BERT to cause an interrupt if there is a change of state in the synchronization status (i.e. the receive
BERT either goes into or out of synchronization).
0 = interrupt masked
1 = interrupt enabled
Register Name:
BERTC1
Register Description: BERT Control Register 1
Register Address:
0504h
7
EIB2
15
6
EIB1
14
5
EIB0
13
4
3
2
1
0
SBE
n/a
n/a
n/a
TC
12
11
10
9
8
Alternating Word Count
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
Bit 0 / Transmit Pattern Load (TC). A low to high transition loads the pattern generator with
Repetitive or pseudorandom pattern that is to be generated. This bit should be toggled from low to high
whenever the host wishes to load a new pattern. Must be cleared and set again for a subsequent loads.
73 of 203
DS3134
Bit 4 / Single Bit Error Insert (SBE). A low to high transition will create a single bit error. Must be
cleared and set again for a subsequent bit error to be inserted.
Bit 5 / Error Insert Bit 0 (EIB0).
Bit 6 / Error Insert Bit 1 (EIB1).
Bit 7 / Error Insert Bit 2 (EIB2).
Will automatically insert bit errors at the prescribed rate into the generated data pattern. Useful for
verifying error detection operation.
EIB
2
EIB
1
EIB
0
Error Rate Inserted
0
0
0
0
1
1
1
1
0
0
1
1
0
0
1
1
0
1
0
1
0
1
0
1
no errors automatically inserted
10E-1
10E-2
10E-3
10E-4
10E-5
10E-6
10E-7
Bits 8 to 15 / Alternating Word Count Rate. When the BERT is programmed in the alternating word
mode, the words will repeat for the count loaded into this register then flip to the other word and again
repeat for the number of times loaded into this register. The valid count range is from 05h to FFh.
Register Name:
BERTRP0
Register Description: BERT Repetitive Pattern Set 0
Register Address:
0508h
Register Name:
BERTRP1
Register Description: BERT Repetitive Pattern Set 1
Register Address:
050Ch
BERTRP0: BERT Repetitive Pattern Set 0 (lower word)
7
6
5
4
3
2
1
0
BERT Repetitive Pattern Set (lower byte)
15
14
13
12
11
10
9
8
BERT Repetitive Pattern Set
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
74 of 203
DS3134
BERTRP1: BERT Repetitive Pattern Set 1 (upper word)
23
22
21
20
19
18
17
16
BERT Repetitive Pattern Set
31
30
29
28
27
26
25
24
BERT Repetitive Pattern Set (upper byte)
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
Bits 0 to 31 / BERT Repetitive Pattern Set (BERTRP0 and BERTRP1). These registers must be
properly loaded for the BERT to properly generate and synchronize to a repetitive pattern, a
pseudorandom pattern, or an alternating word pattern. For a repetitive pattern that is less than 32 bits,
then the pattern should be repeated so that all 32 bits are used to describe the pattern. For example if the
pattern was the repeating 5-bit pattern …01101… (Where right most bits are one sent first and received
first) then PBRP0 should be loaded with xB5AD and PBRP1 should be loaded with x5AD6. For a
pseudorandom pattern, both registers should be loaded with all ones (i.e. xFFFF). For an alternating word
pattern, one word should be placed into PBRP0 and the other word should be placed into PBRP1. For
example, if the DDS stress pattern "7E" is to be described, the user would place x0000 in PBRP0 and
x7E7E in PBRP1 and the alternating word counter would be set to 50 (decimal) to allow 100 bytes of 00h
followed by 100 bytes of 7Eh to be sent and received.
Register Name:
BERTBC0
Register Description: BERT 32-Bit Bit Counter (lower word)
Register Address:
0510h
Register Name:
BERTBC1
Register Description: BERT 32-Bit Bit Counter (upper word)
Register Address:
0514h
BERTBC0: BERT Bit Counter 0 (lower word)
7
6
5
4
3
2
1
0
BERT 32-Bit Bit Counter (lower byte)
15
14
13
12
11
10
9
8
BERT 32-Bit Bit Counter
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
BERTBC1: BERT Bit Counter 0 (upper word)
23
22
21
20
19
18
17
16
BERT 32-Bit Bit Counter
31
30
29
28
27
26
25
24
BERT 32-Bit Bit Counter (upper byte)
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
75 of 203
DS3134
Bits 0 to 31 / BERT 32-Bit Bit Counter (BERTBC0 and BERTBC1). This 32-bit counter will
increment for each data bit (i.e. clock) received. This counter is not disabled when the receive BERT
loses synchronization. This counter will be loaded with the current bit count value when the LC control
bit in the BERTC0 register is toggled from a low (0) to a high (1). When full, this counter will saturate
and set the BBCO status bit.
Register Name:
BERTEC0
Register Description: BERT 24-Bit Error Counter (lower) & Status Information
Register Address:
0518h
7
n/a
15
6
RA1
14
5
4
3
2
1
0
RA0
RLOS
BED
BBCO
BECO
SYNC
13
12
11
10
9
8
BERT 24-Bit Error Counter (lower byte)
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
Bit 0 / Real Time Synchronization Status (SYNC). Real time status of the synchronizer (this bit is not
latched). Will be set when the incoming pattern matches for 32 consecutive bit positions. Will be cleared
when 6 or more bits out of 64 are received in error.
Bit 1 / BERT Error Counter Overflow (BECO). A latched bit which is set when the 24-bit BERT
Error Counter (BEC) overflows. Cleared when read and will not be set again until another overflow
occurs.
Bit 2 / BERT Bit Counter Overflow (BBCO). A latched bit which is set when the 32-bit BERT Bit
Counter (BBC) overflows. Cleared when read and will not be set again until another overflow occurs.
Bit 3 / Bit Error Detected (BED). A latched bit which is set when a bit error is detected. The receive
BERT must be in synchronization for it detect bit errors. Cleared when read.
Bit 4 / Receive Loss Of Synchronization (RLOS). A latched bit which is set whenever the receive
BERT begins searching for a pattern. Once synchronization is achieved, this bit will remain set until
read.
Bit 5 / Receive All Zeros (RA0). A latched bit which is set when 31 consecutive zeros are received.
Allowed to be cleared once a one is received.
Bit 6 / Receive All Ones (RA1). A latched bit which is set when 31 consecutive ones are received.
Allowed to be cleared once a zero is received.
Bits 8 to 15 / BERT 24-Bit Error Counter (BEC). Lower word of the 24-bit error counter. See the
BERTEC1 register description for details.
76 of 203
DS3134
Register Name:
BERTEC1
Register Description: BERT 24-Bit Error Counter (upper)
Register Address:
051Ch
7
6
5
4
3
2
1
0
BERT 24-Bit Error Counter
15
14
13
12
11
10
9
8
BERT 24-Bit Error Counter (upper byte)
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
Bits 0 to 15 / BERT 24-Bit Error Counter (BEC). Upper two words of the 24-bit error counter. This
24-bit counter will increment for each data bit received in error. This counter is not disabled when the
receive BERT loses synchronization. This counter will be loaded with the current bit count value when
the LC control bit in the BERTC0 register is toggled from a low (0) to a high (1). When full, this counter
will saturate and set the BECO status bit.
77 of 203
DS3134
SECTION 6: HDLC
6.1 GENERAL DESCRIPTION
The DS3134 contains two different types of HDLC controllers. Each port has a Slow HDLC Engine (type
#1) associated with it that can operate in either a channelized mode up to 8.192 Mbps or an unchannelized
mode at rates up to 10 Mbps. Ports 0 and 1 also have associated with them, an additional Fast HDLC
Engine (type #2) that is capable of operating in only an unchannelized fashion up to 52 Mbps. Via the
Layer One registers (see Section 5.2), the Host will determine which type of HDLC controller will be
used on a Port and if the HDLC controller is to be operated in either a channelized or unchannelized
mode. If the HDLC controller is to be operated in the channelized mode, then the Layer One registers
(see Section 5.3) will also determine which HDLC channels are associated with which DS0 channels. If
the Fast HDLC Engine is enabled on Port 0, then HDLC Channel 1 is assigned to it and likewise HDLC
Channel 2 will be assigned to the Fast HDLC Engine on Port 1 if it is enabled.
The HDLC controllers are capable of handling all the normal real-time tasks required. Table 6.1B lists all
of the functions supported by the Receive HDLC and Table 6.1C lists all of the functions supported by the
Transmit HDLC. Each of the 256 HDLC channels within Chateau are configured by the Host via the
Receive HDLC Channel Definition (RHCD) and Transmit Channel Definition (THCD) registers. There
is a separate RHCD and THCD register for each HDLC channel. The Host can access the RHCD and
THCD registers indirectly via the RHCDIS indirect select and THCDIS indirect select registers. See
Section 6.2 for details.
On the receive side, when the HDLC Block is processing a packet, one of the outcomes shown in
Table 6.1A will occur. For each packet, one of these outcomes will be reported in the Receive Done
Queue Descriptor (see Section 8.1.4 for details). On the transmit side, when the HDLC Block is
processing a packet, an error in the PCI Block (parity or target abort) or transmit FIFO underflow will
cause the HDLC Block to send an Abort sequence (8 ones in a row) followed continuously by the selected
Interfill (either 7Eh or FFh) until the HDLC channel is reset by the transmit DMA Block (see Section
8.2.1 for details). This same sequence of events will occur even if the transmit HDLC channel is being
operated in the transparent mode. In the transparent mode, when the FIFO empties the device will send
either 7Eh or FFh.
Receive HDLC Packet Processing Outcomes Table 6.1A
Outcome
EOF / Normal
Packet
EOF / Bad FCS
Abort Detected
EOF / Too Few
Bytes
Too Many Bytes
EOF / Bad # of Bits
FIFO Overflow
Criteria
Integral number of packets > min. & < max. is received & CRC is okay
Integral number of packets > min. & < max. is received & CRC is bad
Seven or more ones in a row detected
Less than 4 or 6 bytes received
Greater than the packet maximum is received (if detection enabled)
Not an integral number of bytes received
Tried to write a byte into an already full FIFO
78 of 203
DS3134
If any of the 256 receive HDLC channels detects an abort sequence, a FCS checksum error, or if the
packet length was incorrect, then the appropriate status bit in the Status Register for DMA (SDMA) will
be set. If enabled, the setting of any of these statuses can cause a hardware interrupt to occur. See
Section 4.3.2 for details on the operation of these status bits.
Receive HDLC Functions Table 6.1B
Zero Destuff
- This operation is disabled if the channel is set to transparent mode.
Flag Detection & Byte Alignment
- Okay to have two packets separated by only one flag or by two flags sharing a zero.
- This operation is disabled if the channel is set to transparent mode.
Octet Length Check
- The minimum check is for 4 bytes with CRC-16 and 6 bytes with CRC-32 (packets with less
than the minimum lengths are not passed to the PCI bus).
- The maximum check is programmable up to 65,536 bytes via the RHPL register.
- The maximum check can be disabled via the ROLD control bit in the RHCD register.
- The minimum and maximum counts include the FCS.
- An error is also reported if a non-integer number of octets occur between flags.
CRC Check
- Can be either set to CRC-16 or CRC-32 or none.
- The CRC can be passed through to the PCI bus or not
- The CRC check is disabled if the channel is set to transparent mode.
Abort Detection
- Checks for seven or more ones in a row.
Invert Data
- All data (including the flags & FCS) is inverted before HDLC processing.
- Also available in the transparent mode.
Bit Flip
- The first bit received becomes either the LSB (normal mode) or the MSB (telecom mode) of the
byte stored in the FIFO.
- Also available in the transparent mode.
Transparent Mode
- If enabled, flag detection, zero destuffing, abort detection, length checking, and FCS checking
are disabled.
- Data is passed to the PCI Bus on octet (i.e. byte) boundaries in channelized operation.
79 of 203
DS3134
Transmit HDLC Functions Table 6.1C
Zero Stuffing
- Only used in between opening and closing flags.
- Will be disabled in between a closing flag and an opening flag and for sending aborts and/or
interfill data.
- Disabled if the channel is set to the transparent mode.
Interfill Selection
- Can be either 7Eh or FFh.
Flag Generation
- A programmable number of flags (1 to 16) can be set in between packets.
- Disabled if the channel is set to the transparent mode.
CRC Generation
- Can be either CRC-16 or CRC-32 or none.
- Disabled if the channel is set to transparent mode.
Invert Data
- All data (including the flags & FCS) is inverted after processing.
- Also available in the transparent mode
Bit Flip
- The LSB (normal mode) of the byte from the FIFO becomes the first bit sent or the MSB
(Telecom mode) becomes the first bit sent.
- Also available in the transparent mode.
Transparent Mode
- If enabled, flag generation, zero stuffing, and FCS generation is disabled.
- Will pass bytes from the PCI Bus to Layer 1 on octet (i.e. byte) boundaries.
Invert FCS
- When enabled, it will invert all of the bits in the FCS (useful for HDLC testing).
6.2 HDLC REGISTER DESCRIPTION
Register Name:
RHCDIS
Register Description: Receive HDLC Channel Definition Indirect Select
Register Address:
0400h
7
6
5
4
3
2
1
0
HCID7
HCID6
HCID5
HCID4
HCID3
HCID2
HCID1
HCID0
15
14
13
12
11
10
9
8
IAB
IARW
n/a
n/a
n/a
n/a
n/a
n/a
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
Bits 0 to 7 / HDLC Channel ID (HCID0 to HCID7).
00000000 (00h) = HDLC Channel Number 1 (also used for the Fast HDLC Engine on Port 0)
00000001 (01h) = HDLC Channel Number 2 (also used for the Fast HDLC Engine on Port 1)
00000010 (02h) = HDLC Channel Number 3
11111111 (FFh) = HDLC Channel Number 256
80 of 203
DS3134
Bit 14 / Indirect Access Read/Write (IARW). When the host wishes to read data from the internal
Receive HDLC Definition RAM, this bit should be written to a one by the host. This causes the device to
begin obtaining the data from the channel location indicated by the HCID bits. During the read access,
the IAB bit will be set to one. Once the data is ready to be read from the RHCD register, the IAB bit will
be set to zero. When the host wishes to write data to the internal Receive HDLC Definition RAM, this bit
should be written to a zero by the host. This causes the device to take the data that is current present in
the RHCD register and write it to the channel location indicated by the HCID bits. When the device has
completed the write, the IAB will be set to zero.
Bit 15 / Indirect Access Busy (IAB). When an indirect read or write access is in progress, this read only
bit will be set to a one. During a read operation, this bit will be set to a one until the data is ready to be
read. It will be set to zero when the data is ready to be read. During a write operation, this bit will be set
to a one while the write is taking place. It will be set to zero once the write operation has completed.
Register Name:
RHCD
Register Description: Receive HDLC Channel Definition
Register Address:
0404h
7
6
5
4
3
2
1
RABTD
RCS
RBF
RID
RCRC1 RCRC0
ROLD
15
14
13
12
11
10
9
n/a
n/a
n/a
n/a
n/a
n/a
n/a
Note: Bits that are underlined are read only, all other bits are read-write.
0
RTRANS
8
RZDD
Bit 0 / Receive Transparent Enable (RTRANS). When this bit is set low, the HDLC engine performs
flag delineation, zero destuffing, abort detection, octet length checking (if enabled via ROLD), and FCS
checking (if enabled via RCRC0/1). When this bit is set high, the HDLC engine does not perform flag
delineation, zero destuffing, and abort detection, octet length checking, or FCS checking.
0 = transparent mode disabled
1 = transparent mode enabled
Bit 1 / Receive Octet Length Detection Enable (ROLD). When this bit is set low, the HDLC engine
does not check to see if the octet length of the received packets exceeds the count loaded into the Receive
HDLC Packet Length (RHPL) register. When this bit is set high, the HDLC engine checks to see if the
octet length of the received packets exceeds the count loaded into the RHPL register. When an incoming
packet exceeds the maximum length, then the packet is aborted and the remainder is discarded. This bit is
ignored if the HDLC channel is set into Transparent mode (RTRANS = 1).
0 = octet length detection disabled
1 = octet length detection enabled
81 of 203
DS3134
Bit 2 & Bit 3 / Receive CRC Selection (RCRC0/RCRC1). These 2 bits are ignored if the HDLC
channel is set into Transparent mode (RTRANS = 1).
RCRC1
RCRC0 Action
0
0
no CRC verification performed
0
1
16-bit CRC (CCITT/ITU Q.921)
1
0
32-bit CRC
1
1
illegal state
Bit 4 / Receive Invert Data Enable (RID). When this bit is set low, the incoming HDLC packets are not
inverted before processing. When this bit is set high, the HDLC engine inverts all the data (flags,
information fields, and FCS) before processing the data. The data is not re-inverted before passing to the
FIFO.
0 = do not invert data
1 = invert all data (including flags and FCS)
Bit 5 / Receive Bit Flip (RBF). When this bit is set low, the HDLC engine will place the first HDLC bit
received in the lowest bit position of the PCI Bus bytes (i.e. PAD[0] / PAD[8] / PAD[16] / PAD[24]).
When this bit is set high, the HDLC engine will place the first HDLC bit received in the highest bit
position of the PCI Bus bytes (i.e. PAD[7] / PAD[15] / PAD[23] / PAD[31]).
0 = the first HDLC bit received is placed in the lowest bit position of the bytes on the PCI Bus
1 = the first HDLC bit received is placed in the highest bit position of the bytes on the PCI Bus
Bit 6 / Receive CRC Strip Enable (RCS). When this bit is set high, the FCS is not transferred through
to the PCI Bus. When this bit is set low, the HDLC engine will include the two byte FCS (16-bit) or four
byte FCS (32-bit) in the data that it transfers to the PCI Bus. This bit is ignored if the HDLC channel is
set into Transparent mode (RTRANS = 1).
0 = send FCS to the PCI Bus
1 = do not send the FCS to the PCI Bus
Bit 7 / Receive Abort Disable (RABTD). When this bit is set low, the HDLC engine will examine the
incoming data stream for the Abort sequence, which are seven or more consecutive ones. When this bit is
set high, the incoming data stream is not examined for the Abort sequence and if an incoming Abort
sequence is received, no action will be taken. This bit is ignored when the HDLC engine is configured in
the Transparent Mode (RTRANS = 1).
Bit 8 / Receive Zero Destuffing Disable (RZDD). When this bit is set low, the HDLC engine will zero
destuff the incoming data stream. When this bit is set high, the HDLC engine will not zero destuff the
incoming data stream. This bit is ignored when the HDLC engine is configured in the Transparent Mode
(RTRANS = 1).
82 of 203
DS3134
Register Name:
RHPL
Register Description: Receive HDLC Maximum Packet Length
Register Address:
0410h
7
6
5
4
3
2
1
0
RHPL7
RHPL6
RHPL5
RHPL4
RHPL3
RHPL2
RHPL1
RHPL0
15
14
13
12
11
10
9
8
RHPL15 RHPL14 RHPL13 RHPL12 RHPL11 RHPL10 RHPL9
RHPL8
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0s.
This is a globe control only one per device and it is not one for each individual HDLC channel.
Bits 0 to 15 / Receive HDLC Packet Length (RHPL0 to RHPL15). If the Receive Length Detection
Enable bit is set to one, then the HDLC engine will check the number of received octets in a packet to see
if they exceed the count in this register. If the length is exceeded, then the packet is aborted and the
remainder is discarded. The definition of "octet length" is everything in between the opening and closing
flags which includes the address field, control field, information field, and FCS.
Register Name:
THCDIS
Register Description: Transmit HDLC Channel Definition Indirect Select
Register Address:
0480h
7
6
5
4
3
2
1
0
HCID7
HCID6
HCID5
HCID4
HCID3
HCID2
HCID1
HCID0
15
14
13
12
11
10
9
8
IAB
IARW
n/a
n/a
n/a
n/a
n/a
n/a
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
Bits 0 to 7 / HDLC Channel ID (HCID0 to HCID7).
00000000 (00h) = HDLC Channel Number 1 (also used for the Fast HDLC Engine on Port 0)
00000001 (01h) = HDLC Channel Number 2 (also used for the Fast HDLC Engine on Port 1)
00000010 (02h) = HDLC Channel Number 3
11111111 (FFh) = HDLC Channel Number 256
Bit 14 / Indirect Access Read/Write (IARW). When the host wishes to read data from the internal
Transmit HDLC Definition RAM, this bit should be written to a one by the host. This causes the device
to begin obtaining the data from the channel location indicated by the HCID bits. During the read access,
the IAB bit will be set to one. Once the data is ready to be read from the THCD register, the IAB bit will
be set to zero. When the host wishes to write data to the internal Transmit HDLC Definition RAM, this
bit should be written to a zero by the host. This causes the device to take the data that is current present in
the THCD register and write it to the channel location indicated by the HCID bits. When the device has
completed the write, the IAB will be set to zero.
Bit 15 / Indirect Access Busy (IAB). When an indirect read or write access is in progress, this read only
bit will be set to a one. During a read operation, this bit will be set to a one until the data is ready to be
read. It will be set to zero when the data is ready to be read. During a write operation, this bit will be set
to a one while the write is taking place. It will be set to zero once the write operation has completed.
83 of 203
DS3134
Register Name:
THCD
Register Description: Transmit HDLC Channel Definition
Register Address:
0484h
7
6
5
4
3
2
1
TABTE TCFCS
TBF
TID
TCRC1 TCRC0
TIFS
15
14
13
12
11
10
9
n/a
n/a
n/a
TZSD
TFG3
TFG2
TFG1
Note: Bits that are underlined are read only, all other bits are read-write.
0
TTRANS
8
TFG0
Bit 0 / Transmit Transparent Enable (TTRANS). When this bit is set low, the HDLC engine will
generate flags and the FCS (if enabled via TCRC0/1) and perform zero stuffing. When this bit is set high,
the HDLC engine does not generate flags or the FCS and does not perform zero stuffing.
0 = transparent mode disabled
1 = transparent mode enabled
Bit 1 / Transmit Interfill Select (TIFS).
0 = the interfill byte is 7Eh (01111110)
1 = the interfill byte is FFh (11111111)
Bit 2 & Bit 3 / Transmit CRC Selection (TCRC0/TCRC1). These 2 bits are ignored if the HDLC
channel is set into Transparent mode (TTRANS = 1).
TCRC1
0
0
1
1
TCRC0
0
1
0
1
Action
no CRC is generated
16-bit CRC (CCITT/ITU Q.921)
32-bit CRC
illegal state
Bit 4 / Transmit Invert Data Enable (TID). When this bit is set low, the outgoing HDLC packets are
not inverted after being generated. When this bit is set high, the HDLC engine inverts all the data (flags,
information fields, and FCS) after the packet has been generated.
0 = do not invert data
1 = invert all data (including flags and FCS)
Bit 5 / Transmit Bit Flip (TBF). When this bit is set low, the HDLC engine will obtain the first HDLC
bit to be transmitted from the lowest bit position of the PCI Bus bytes (i.e. PAD[0] / PAD[8] / PAD[16] /
PAD[24]). When this bit is set high, the HDLC engine will obtain the first HDLC bit to be transmitted
from the highest bit position of the PCI Bus bytes (i.e. PAD[7] / PAD[15] / PAD[23] / PAD[31]).
0 = the first HDLC bit transmitted is obtained from the lowest bit position of the bytes on the
PCI Bus
1 = the first HDLC bit transmitted is obtained from the highest bit position of the bytes on the
PCI Bus
84 of 203
DS3134
Bit 6 / Transmit Corrupt FCS (TCFCS). When this bit is set low, the HDLC engine will allow the
Frame Checksum Sequence (FCS) to be transmitted as generated. When this bit is set high, the HDLC
engine will invert all the bits of the FCS before transmission occurs. This is useful in debugging and
testing HDLC channels at the system level.
0 = generate FCS normally
1 = invert all FCS bits
Bit 7 / Transmit Abort Enable (TABTE). When this bit is set low, the HDLC engine will perform
normally only sending an Abort sequence (eight ones in a row) when an error occurs in the PCI Block or
the FIFO underflows. When this bit is set high, the HDLC engine will continuously transmit an all ones
pattern (i.e. an Abort sequence). This bit is still active when the HDLC engine is configured in the
Transparent Mode (TTRANS = 1).
Bits 8 to 11/ Transmit Flag Generation Bits 0 to 3 (TFG0/TFG1/TFG2/TFG3). These 4 bits
determine how many flags and interfill bytes will be sent in between consecutive packets.
TFG3 TFG2 TFG1 TFG0
Action
0
0
0
0
share closing and opening flag
0
0
0
1
closing flag / no interfill bytes / opening flag
0
0
1
0
closing flag / 1 interfill bytes / opening flag
0
0
1
1
closing flag / 2 interfill bytes / opening flag
0
1
0
0
closing flag / 3 interfill bytes / opening flag
0
1
0
1
closing flag / 4 interfill bytes / opening flag
0
1
1
0
closing flag / 5 interfill bytes / opening flag
0
1
1
1
closing flag / 6 interfill bytes / opening flag
1
0
0
0
closing flag / 7 interfill bytes / opening flag
1
0
0
1
closing flag / 8 interfill bytes / opening flag
1
0
1
0
closing flag / 9 interfill bytes / opening flag
1
0
1
1
closing flag / 10 interfill bytes / opening flag
1
1
0
0
closing flag / 11 interfill bytes / opening flag
1
1
0
1
closing flag / 12 interfill bytes / opening flag
1
1
1
0
closing flag / 13 interfill bytes / opening flag
1
1
1
1
closing flag / 14 interfill bytes / opening flag
Bit 12 / Transmit Zero Stuffing Disable (TZSD). When this bit is set low, the HDLC engine will
perform zero stuffing on the outgoing data stream. When this bit is set high, the outgoing data stream is
not zero stuffed. This bit is ignored when the HDLC engine is configured in the Transparent Mode
(TTRANS = 1).
85 of 203
DS3134
SECTION 7: FIFO
7.1 GENERAL DESCRIPTION & EXAMPLE
Chateau contains one 16k byte FIFO for the receive path and another 16k byte FIFO for the transmit path.
Both of these FIFOs are organized into Blocks. A Block is defined as four dwords (i.e. 16 bytes). Hence,
each FIFO is made up of 1024 Blocks. See the FIFO example in Figure 7.1A.
The FIFO contains a state machine that is constantly polling the 16 ports to determine if any data is ready
for transfer to/from the FIFO from/to the HDLC engines. The 16 ports are priority decoded with Port 0
getting the highest priority and Port 15 getting the lowest priority. Hence, all of the enabled HDLC
channels on the lower numbered ports are serviced before the higher numbered ports. As long as the
maximum throughput rate of 104 Mbps is not exceeded, the DS3134 has been designed to insure that
there is enough bandwidth in this transfer to prevent any loss of data in between the HDLC Engines and
the FIFO.
The FIFO also controls which HDLC channel the DMA should service to read data out of the FIFO on the
receive side and to write data into the FIFO on the transmit side. Which channel gets the highest priority
from the FIFO is configurable via some control bits in the Master Configuration (MC) register (see
Section 4.2). There are two control bits for the receive side (RFPC0 and RFPC1) and two control bits for
the transmit side (TFPC0 and TFPC1) that will determine the priority algorithm as shown in Table 7.1A.
When a HDLC channel is priority decoded the lower the number of the HDLC channel, the higher the
priority. Hence HDLC channel number 1 always has the highest priority in the priority decoded scheme.
FIFO Priority Algorithm Select Table 7.1A
Option
HDLC Channels that are
Priority Decoded
HDLC Channels that are
Serviced Round Robin
1
2
3
4
none
1 to 2
1 to 16
1 to 64
1 to 256
3 to 256
17 to 256
65 to 256
To maintain maximum flexibility for channel reconfiguration, each Block within the FIFO can be
assigned to any of the 256 HDLC channels. In addition, Blocks are link-listed together to form a chain
whereby each Block points to the next Block in the chain. The minimum size of the link-listed chain is 4
Blocks (64 bytes) and the maximum is the full size of the FIFO which is 1024 Blocks.
To assign a set of Blocks to a particular HDLC channel, the Host must configure the Starting Block
Pointer and the Block Pointer RAM. The Starting Block Pointer assigns a particular HDLC channel to a
set of link-listed Blocks by pointing to one of the Blocks within the chain (it does not matter which Block
in the chain is pointed to). The Block Pointer RAM must be configured for each Block that is being used
within the FIFO. The Block Pointer RAM indicates the next Block in the link-listed chain.
Figure 7.1A shows an example of how to configure the Starting Block Pointer and the Block Pointer
RAM. In this example, only three HDLC channels are being used (channels 2, 6, and 16). The device
knows that channel 2 has been assigned to the eight link-listed Blocks of 112, 118, 119, 120, 121, 122,
125, and 126 because a Block Pointer of 125 has been programmed into the channel 2 position of the
86 of 203
DS3134
Starting Block Pointer. The Block Pointer RAM tells the device how to link the eight Blocks together to
form a circular chain.
The Host must set the Water Marks for the receive and transmit paths. The receive path has a High Water
Mark and the transmit path has a Low Water Mark.
FIFO Example Figure 7.1A
HDLC
Channel
Number
Starting Block
Pointer
1024 Block FIFO
(1 Block = 4 dwords)
not used
Block Pointer
RAM
CH 1
not used
CH 2
Block Pointer 125
CH 3
not used
CH 4
not used
CH 5
not used
CH 6
Block Pointer 113
CH 7
not used
CH 8
not used
CH 9
not used
CH 10
not used
Block 112
Channel 2
Block 112
Block 118
CH 11
not used
Block 113
Channel 6
Block 113
Block 114
CH 12
not used
Block 114
Channel 6
Block 114
Block 113
CH 13
not used
Block 115
not used
Block 115
not used
CH 14
not used
Block 116
not used
Block 116
not used
CH 15
not used
Block 117
not used
Block 117
not used
CH 16
Block Pointer 5
Block 118
Channel 2
Block 118
Block 119
CH 17
not used
Block 119
Channel 2
Block 119
Block 120
CH 18
not used
Block 120
Channel 2
Block 120
Block 121
CH 19
not used
Block 121
Channel 2
Block 121
Block 122
CH 20
not used
Block 122
Channel 2
Block 122
Block 125
CH 21
not used
Block 123
not used
Block 123
not used
Block 124
not used
Block 124
not used
Block 125
Channel 2
Block 125
Block 126
not used
Block 126
Channel 2
Block 126
Block 112
not used
Block 127
not used
Block 127
not used
Block 1022
not used
Block 1022
not used
Block 1023
not used
Block 1023
not used
CH 255
CH 256
fifobd.drw
Block 0
Block 1
Block 2
Block 3
Block 4
Block 5
Block 6
not used
Channel 16
Channel 16
Channel 16
Channel 16
not used
87 of 203
Block 0
Block 1
Block 2
Block 3
Block 4
Block 5
Block 6
not used
not used
Block 4
Block 5
Block 3
Block 2
not used
DS3134
Receive High Water Mark
The High Water Mark indicates to the device how many Blocks should be written into the receive FIFO
by the HDLC engines before the DMA will begin sending the data to the PCI Bus. Alternatively, in other
words, how full should the FIFO get before it should be emptied by the DMA. When the DMA begins
reading the data from the FIFO, it will read all available data and try to completely empty the FIFO even
if one or more EOF (End Of Frames) is detected. As an example, if four Blocks were link-listed together
and the Host programmed the High Water Mark to three Blocks, then the DMA would read the data out of
the FIFO and transfer it to the PCI Bus after the HDLC engine has written three complete Blocks in
succession into the FIFO and still had one Block left to fill. The DMA would not read the data out of the
FIFO again until another three complete Blocks had been written into the FIFO in succession by the
HDLC engine or until an EOF was detected. In this example of four Blocks being link-listed together, the
High Water Mark could also be set to 1 or 2 but no other values would be allowed. If an incoming packet
does not fill the FIFO enough to reach the High Water Mark before an EOF is detected, the DMA will
still request that the data be sent to the PCI Bus, it will not wait for additional data to be written into the
FIFO by the HDLC engines.
Transmit Low Water Mark
The Low Water Mark indicates to the device how many Blocks should be left in the FIFO before the
DMA should begin getting more data from the PCI Bus. In other words, how empty should the FIFO get
before it should be filled again by the DMA. When the DMA begins reading the data from the PCI Bus, it
will read all available data and try to completely fill the FIFO even if one or more EOF (i.e. HDLC
packets) is detected. As an example, if five Blocks were link-listed together and the Host programmed
the Low Water Mark to two Blocks, then the DMA would read the data from the PCI Bus and transfer it
to the FIFO after the HDLC engine has read three complete Blocks in succession from the FIFO and
hence still had two blocks left before the FIFO was empty. The DMA would not read the data from the
PCI Bus again until another three complete Blocks had been read from the FIFO in succession by the
HDLC engines. In this example of five Blocks being link-listed together, the Low Water Mark could also
be set to any value from 1 to 3 (inclusive) but no other values would be allowed. In another words the
Transmit Low Water Mark can be set to a value of 1 to N – 2, where N = number of blocks are linked
together. When a new packet is written into a completely empty FIFO by the DMA, the HDLC engines
will wait until the FIFO fills beyond the Low Water Mark or until an EOF is seen before reading the data
out of the FIFO.
7.2 FIFO REGISTER DESCRIPTION
Register Name:
RFSBPIS
Register Description: Receive FIFO Starting Block Pointer Indirect Select
Register Address:
0900h
7
6
5
4
3
2
1
0
HCID7
HCID6
HCID5
HCID4
HCID3
HCID2
HCID1
HCID0
15
14
13
12
11
10
9
8
IAB
IARW
n/a
n/a
n/a
n/a
n/a
n/a
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
88 of 203
DS3134
Bits 0 to 7 / HDLC Channel ID (HCID0 to HCID7).
00000000 (00h) = HDLC Channel Number 1
11111111 (FFh) = HDLC Channel Number 256
Bit 14 / Indirect Access Read/Write (IARW). When the host wishes to write data to set the internal
Receive Starting Block Pointer, this bit should be written to a zero by the host. This causes the device to
take the data that is currently present in the RFSBP register and write it to the channel location indicated
by the HCID bits. When the device has completed the write, the IAB will be set to zero.
Note: The RFSBP is a write only register. Once this register has been written to and operation started,
DS3134 internal state machine will change the value in this register.
Bit 15 / Indirect Access Busy (IAB). When an indirect read or write access is in progress, this read only
bit will be set to a one. During a read operation, this bit will be set to a one until the data is ready to be
read. It will be set to zero when the data is ready to be read. During a write operation, this bit will be set
to a one while the write is taking place. It will be set to zero once the write operation has completed.
Register Name:
RFSBP
Register Description: Receive FIFO Starting Block Pointer
Register Address:
0904h
7
6
5
4
3
2
1
RSBP7
RSBP6
RSBP5
RSBP4
RSBP3
RSBP2
RSBP1
15
14
13
12
11
10
9
n/a
n/a
n/a
n/a
n/a
n/a
RSBP9
Note: Bits that are underlined are read only, all other bits are read-write.
0
RSBP0
8
RSBP8
Bits 0 to 9 / Starting Block Pointer (RSBP0 to RSBP9). These 10 bits determine which of the
1024 blocks within the receive FIFO, the host wants the device to configure as the starting block for a
particular HDLC channel. Any of the blocks within a chain of blocks for a HDLC channel can be
configured as the starting block. When these 10 bits are read, they will report the current Block Pointer
being used to write data into the Receive FIFO from the HDLC Layer 2 engines.
0000000000 (000h) = Use Block 0 as the Starting Block
0111111111 (1FFh) = Use Block 511 as the Starting Block
1111111111 (3FFh) = Use Block 1023 as the Starting Block
89 of 203
DS3134
Register Name:
RFBPIS
Register Description: Receive FIFO Block Pointer Indirect Select
Register Address:
0910h
7
6
5
4
3
2
1
0
BLKID7 BLKID6 BLKID5 BLKID4 BLKID3 BLKID2 BLKID1 BLKID0
15
14
13
12
11
10
9
8
IAB
IARW
n/a
n/a
n/a
n/a
BLKID9 BLKID8
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
Bits 0 to 9 / Block ID (BLKID0 to BLKID9).
0000000000 (000h) = Block Number 0
0111111111 (1FFh) = Block Number 511
1111111111 (3FFh) = Block Number 1023
Bit 14 / Indirect Access Read/Write (IARW). When the host wishes to read data from the internal
Receive Block Pointer RAM, this bit should be written to a one by the host. This causes the device to
begin obtaining the data from the block location indicated by the BLKID bits. During the read access, the
IAB bit will be set to one. Once the data is ready to be read from the RFBP register, the IAB bit will be
set to zero. When the host wishes to write data to the internal Receive Block Pointer RAM, this bit
should be written to a zero by the host. This causes the device to take the data that is current present in
the RFBP register and write it to the channel location indicated by the BLKID bits. When the device has
completed the write, the IAB will be set to zero.
Bit 15 / Indirect Access Busy (IAB). When an indirect read or write access is in progress, this read only
bit will be set to a one. During a read operation, this bit will be set to a one until the data is ready to be
read. It will be set to zero when the data is ready to be read. During a write operation, this bit will be set
to a one while the write is taking place. It will be set to zero once the write operation has completed.
Register Name:
RFBP
Register Description: Receive FIFO Block Pointer
Register Address:
0914h
7
6
5
4
3
2
1
RBP7
RBP6
RBP5
RBP4
RBP3
RBP2
RBP1
15
14
13
12
11
10
9
n/a
n/a
n/a
n/a
n/a
n/a
RBP9
Note: Bits that are underlined are read only, all other bits are read-write.
0
RBP0
8
RBP8
Bits 0 to 9 / Block Pointer (RBP0 to RBP9). These 10 bits indicate which of the 1024 blocks is the next
block in the link list chain. A block is not allowed to point to itself.
0000000000 (000h) = Block 0 is the Next Linked Block
0111111111 (1FFh) = Block 511 is the Next Linked Block
1111111111 (3FFh) = Block 1023 is the Next Linked Block
Register Name:
RFHWMIS
90 of 203
DS3134
Register Description: Receive FIFO High Water Mark Indirect Select
Register Address:
0920h
7
6
5
4
3
2
1
0
HCID7
HCID6
HCID5
HCID4
HCID3
HCID2
HCID1
HCID0
15
14
13
12
11
10
9
8
IAB
IARW
n/a
n/a
n/a
n/a
n/a
n/a
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
Bits 0 to 7 / HDLC Channel ID (HCID0 to HCID7).
00000000 (00h) = HDLC Channel Number 1
11111111 (FFh) = HDLC Channel Number 256
Bit 14 / Indirect Access Read/Write (IARW). When the host wishes to read data from the internal
Receive High Water Mark RAM, this bit should be written to a one by the host. This causes the device to
begin obtaining the data from the channel location indicated by the HCID bits. During the read access,
the IAB bit will be set to one. Once the data is ready to be read from the RFHWM register, the IAB bit
will be set to zero. When the host wishes to write data to the internal Receive High Water Mark RAM,
this bit should be written to a zero by the host. This causes the device to take the data that is currently
present in the RFHWM register and write it to the channel location indicated by the HCID bits. When the
device has completed the write, the IAB will be set to zero.
Bit 15 / Indirect Access Busy (IAB). When an indirect read or write access is in progress, this read only
bit will be set to a one. During a read operation, this bit will be set to a one until the data is ready to be
read. It will be set to zero when the data is ready to be read. During a write operation, this bit will be set
to a one while the write is taking place. It will be set to zero once the write operation has completed.
Register Name:
RFHWM
Register Description: Receive FIFO High Water Mark
Register Address:
0924h
7
6
5
4
3
2
1
RHWM7 RHWM6 RHWM5 RHWM4 RHWM3 RHWM2 RHWM1
15
14
13
12
11
10
9
n/a
n/a
n/a
n/a
n/a
n/a
RHWM9
Note: Bits that are underlined are read only, all other bits are read-write.
0
RHWM0
8
RHWM8
Bits 0 to 9 / High Water Mark (RHWM0 to RHWM9). These 10 bits indicate the setting of the
Receive High Water Mark. The High Water Mark setting is the number of successive blocks that the
HDLC engine will write to the FIFO before the DMA will send the data to the PCI Bus. The High Water
Mark setting must be between (inclusive) one block and one less than the number of blocks in the link-list
chain for the particular channel involved. For example, if four blocks are linked together, then the High
Water Mark can be set to 1, 2 or 3. In another words the High Water Mark can be set to a value of 1 to N
– 1, where N = number of blocks are linked together. Any other numbers are illegal.
0000000000 (000h) = invalid setting
0000000001 (001h) = High Water Mark is 1 Block
91 of 203
DS3134
0000000010 (002h) = High Water Mark is 2 Blocks
0111111111 (1FFh) = High Water Mark is 511 Blocks
1111111111 (3FFh) = High Water Mark is 1023 Blocks
Register Name:
TFSBPIS
Register Description: Transmit FIFO Starting Block Pointer Indirect Select
Register Address:
0980h
7
6
5
4
3
2
1
0
HCID7
HCID6
HCID5
HCID4
HCID3
HCID2
HCID1
HCID0
15
14
13
12
11
10
9
8
IAB
IARW
n/a
n/a
n/a
n/a
n/a
n/a
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
Bits 0 to 7 / HDLC Channel ID (HCID0 to HCID7).
00000000 (00h) = HDLC Channel Number 1
11111111 (FFh) = HDLC Channel Number 256
Bit 14 / Indirect Access Read/Write (IARW). When the host wishes to write data to the internal
Transmit Starting Block Pointer RAM, this bit should be written to a zero by the host. This causes the
device to take the data that is currently present in the TFSBP register and write it to the channel location
indicated by the HCID bits. When the device has completed the write, the IAB will be set to zero.
Note: The TFSBP is a write only register. Once this register has been written to and operation started,
DS3134 internal state machine will change the value in this register.
Bit 15 / Indirect Access Busy (IAB). When an indirect read or write access is in progress, this read only
bit will be set to a one. During a read operation, this bit will be set to a one until the data is ready to be
read. It will be set to zero when the data is ready to be read. During a write operation, this bit will be set
to a one while the write is taking place. It will be set to zero once the write operation has completed.
Register Name:
TFSBP
Register Description: Transmit FIFO Starting Block Pointer
Register Address:
0984h
7
6
5
4
3
2
1
TSBP7
TSBP6
TSBP5
TSBP4
TSBP3
TSBP2
TSBP1
15
14
13
12
11
10
9
n/a
n/a
n/a
n/a
n/a
n/a
TSBP9
Note: Bits that are underlined are read only, all other bits are read-write.
92 of 203
0
TSBP0
8
TSBP8
DS3134
Bits 0 to 9 / Starting Block Pointer (TSBP0 to TSBP9). These 10 bits determine which of the 1024
blocks within the transmit FIFO, the host wants the device to configure as the starting block for a
particular HDLC channel. Any of the blocks within a chain of blocks for a HDLC channel can be
configured as the starting block. When these 10 bits are read, they will report the current Block Pointer
being used to read data from the Transmit FIFO by the HDLC Layer 2 engines.
0000000000 (000h) = Use Block 0 as the Starting Block
0111111111 (1FFh) = Use Block 511 as the Starting Block
1111111111 (3FFh) = Use Block 1023 as the Starting Block
Register Name:
TFBPIS
Register Description: Transmit FIFO Block Pointer Indirect Select
Register Address:
0990h
7
6
5
4
3
2
1
0
BLKID7 BLKID6 BLKID5 BLKID4 BLKID3 BLKID2 BLKID1 BLKID0
15
14
13
12
11
10
9
8
IAB
IARW
n/a
n/a
n/a
n/a
BLKID9 BLKID8
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
Bits 0 to 9 / Block ID (BLKID0 to BLKID9).
0000000000 (000h) = Block Number 0
0111111111 (1FFh) = Block Number 511
1111111111 (3FFh) = Block Number 1023
Bit 14 / Indirect Access Read/Write (IARW). When the host wishes to read data from the internal
Transmit Block Pointer RAM, this bit should be written to a one by the host. This causes the device to
begin obtaining the data from the block location indicated by the BLKID bits. During the read access, the
IAB bit will be set to one. Once the data is ready to be read from the TFBP register, the IAB bit will be
set to zero. When the host wishes to write data to the internal Transmit Block Pointer RAM, this bit
should be written to a zero by the host. This causes the device to take the data that is currently present in
the TFBP register and write it to the channel location indicated by the BLKID bits. When the device has
completed the write, the IAB will be set to zero.
Bit 15 / Indirect Access Busy (IAB). When an indirect read or write access is in progress, this read only
bit will be set to a one. During a read operation, this bit will be set to a one until the data is ready to be
read. It will be set to zero when the data is ready to be read. During a write operation, this bit will be set
to a one while the write is taking place. It will be set to zero once the write operation has completed.
93 of 203
DS3134
Register Name:
TFBP
Register Description: Transmit FIFO Block Pointer
Register Address:
0994h
7
6
5
4
3
2
1
TBP7
TBP6
TBP5
TBP4
TBP3
TBP2
TBP1
15
14
13
12
11
10
9
n/a
n/a
n/a
n/a
n/a
n/a
TBP9
Note: Bits that are underlined are read only, all other bits are read-write.
0
TBP0
8
TBP8
Bits 0 to 9 / Block Pointer (TBP0 to TBP9). These 10 bits indicate which of the 1024 blocks is the next
block in the link list chain. A block is not allowed to point to itself.
0000000000 (000h) = Block 0 is the Next Linked Block
0111111111 (1FFh) = Block 511 is the Next Linked Block
1111111111 (3FFh) = Block 1023 is the Next Linked Block
Register Name:
TFLWMIS
Register Description: Transmit FIFO Low Water Mark Indirect Select
Register Address:
09A0h
7
6
5
4
3
2
1
0
HCID7
HCID6
HCID5
HCID4
HCID3
HCID2
HCID1
HCID0
15
14
13
12
11
10
9
8
IAB
IARW
n/a
n/a
n/a
n/a
n/a
n/a
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
Bits 0 to 7 / HDLC Channel ID (HCID0 to HCID7).
00000000 (00h) = HDLC Channel Number 1
11111111 (FFh) = HDLC Channel Number 256
Bit 14 / Indirect Access Read/Write (IARW). When the host wishes to read data from the internal
Transmit Low Water Mark RAM, this bit should be written to a one by the host. This causes the device
to begin obtaining the data from the channel location indicated by the HCID bits. During the read access,
the IAB bit will be set to one. Once the data is ready to be read from the TFLWM register, the IAB bit
will be set to zero. When the host wishes to write data to the internal Transmit Low Water Mark RAM,
this bit should be written to a zero by the host. This causes the device to take the data that is currently
present in the TFLWM register and write it to the channel location indicated by the HCID bits. When the
device has completed the write, the IAB will be set to zero.
Bit 15 / Indirect Access Busy (IAB). When an indirect read or write access is in progress, this read only
bit will be set to a one. During a read operation, this bit will be set to a one until the data is ready to be
read. It will be set to zero when the data is ready to be read. During a write operation, this bit will be set
to a one while the write is taking place. It will be set to zero once the write operation has completed.
94 of 203
DS3134
Register Name:
TFLWM
Register Description: Transmit FIFO Low Water Mark
Register Address:
09A4h
7
6
5
4
3
2
1
TLWM7 TLWM6 TLWM5 TLWM4 TLWM3 TLWM2 TLWM1
15
14
13
12
11
10
9
n/a
n/a
n/a
n/a
n/a
n/a
TLWM9
Note: Bits that are underlined are read only, all other bits are read-write.
0
TLWM0
8
TLWM8
Bits 0 to 9 / Low Water Mark (TLWM0 to TLWM9). These 10 bits indicate the setting of the
Transmit Low Water Mark. The Low Water Mark setting is the number of Blocks left in the Transmit
FIFO before the DMA will get more data from the PCI Bus. The Low Water Mark setting must be
between (inclusive) 1 block and one less than the number of blocks in the link list chain for the particular
channel involved. For example, if five blocks are linked together, then the Low Water Mark can be set to
1, 2, or 3. In another words the Low Water Mark can be set at a value of 1 to N – 2, where N = number of
blocks are linked together. Any other numbers are illegal.
0000000000 (000h) = invalid setting
0000000001 (001h) = Low Water Mark is 1 Block
0000000010 (002h) = Low Water Mark is 2 Blocks
0111111111 (1FFh) = Low Water Mark is 511 Blocks
1111111111 (3FFh) = Low Water Mark is 1023 Blocks
95 of 203
DS3134
SECTION 8: DMA
8.0 INTRODUCTION
The DMA block (see Figure 1.1A) handles the transfer of packet data from the FIFO block to the PCI
block and vice versa. Throughout this Section, the terms Host and Descriptor will be used. Host is
defined as the CPU or intelligent controller that sits on the PCI Bus and instructs the device on how to
handle the incoming and outgoing packet data. Descriptor is defined as a pre-formatted message that is
passed from the Host to the DMA block or vice versa to indicate where packet data should be placed or
obtained from.
On power-up, the DMA will be disabled because the RDE and TDE control bits in the Master
Configuration register (see Section 4) will be set to zero. The Host must configure the DMA by writing
to all of the registers listed in Table 8.0A (which includes all 256 channel locations in the Receive and
Transmit Configuration RAMs) then enable the DMA by setting to the RDE and TDE control bits to one.
The structure of the DMA is such that the receive and transmit side descriptor address spaces can be
shared even among multiple chips on the same bus. Via the Master Control (MC) register, the Host will
determine how long the DMA will be allowed to burst onto the PCI bus. The default value is 32 dwords
(128 bytes) but via the RDT0/1 and TDT0/1 control bits, the Host can enable the receive or transmit
DMAs to burst either 64 dwords (256 bytes), 128 dwords (512 bytes), or 256 dwords (1024 bytes).
The receive and transmit Packet Descriptors have almost identical structures (see Sections 8.1.2 and
8.2.2) which provides a minimal amount of Host intervention in store-and-forward applications. In other
words, the receive descriptors created by the receive DMA can be used directly by the transmit DMA.
The receive and transmit portions of the DMA are completely independent and will be discussed
separately.
96 of 203
DS3134
DMA Registers that must be configured by the Host on Power-Up Table 8.0A
Address
0700
0704
0708
070C
0710
0714
0718
071C
0730
0734
0738
073C
0740
0744
0750
0754
0770
0774
0780
0790
0794
0800
0804
0808
080C
0810
0830
0834
0838
083C
0840
0844
0850
0854
0870
0874
0880
Acronym
RFQBA0
RFQBA1
RFQEA
RFQSBSA
RFQLBWP
RFQSBWP
RFQLBRP
RFQSBRP
RDQBA0
RDQBA1
RDQEA
RDQRP
RDQWP
RDQFFT
RDBA0
RDBA1
RDMACIS
RDMAC
RDMAQ
RLBS
RSBS
TPQBA0
TPQBA1
TPQEA
TPQWP
TPQRP
TDQBA0
TDQBA1
TDQEA
TDQRP
TDQWP
TDQFFT
TDBA0
TDBA1
TDMACIS
TDMAC
TDMAQ
Register
Receive Free Queue Base Address 0 (lower word).
Receive Free Queue Base Address 1 (upper word).
Receive Free Queue End Address.
Receive Free Queue Small Buffer Start Address.
Receive Free Queue Large Buffer Host Write Pointer.
Receive Free Queue Small Buffer Host Write Pointer.
Receive Free Queue Large Buffer DMA Read Pointer.
Receive Free Queue Small Buffer DMA Read Pointer.
Receive Done Queue Base Address 0 (lower word).
Receive Done Queue Base Address 1 (upper word).
Receive Done Queue End Address.
Receive Done Queue Host Read Pointer.
Receive Done Queue DMA Write Pointer.
Receive Done Queue FIFO Flush Timer.
Receive Descriptor Base Address 0 (lower word).
Receive Descriptor Base Address 1 (upper word).
Receive DMA Configuration Indirect Select.
Receive DMA Configuration (all 256 channels).
Receive DMA Queues Control.
Receive Large Buffer Size.
Receive Small Buffer Size.
Transmit Pending Queue Base Address 0 (lower word).
Transmit Pending Queue Base Address 1 (upper word).
Transmit Pending Queue End Address.
Transmit Pending Queue Host Write Pointer.
Transmit Pending Queue DMA Read Pointer.
Transmit Done Queue Base Address 0 (lower word).
Transmit Done Queue Base Address 1 (upper word).
Transmit Done Queue End Address.
Transmit Done Queue Host Read Pointer.
Transmit Done Queue DMA Write Pointer.
Transmit Done Queue FIFO Flush Timer.
Transmit Descriptor Base Address 0 (lower word).
Transmit Descriptor Base Address 1 (upper word).
Transmit DMA Configuration Indirect Select.
Transmit DMA Configuration (all 256 channels).
Transmit Queues FIFO Control.
97 of 203
Section
8.1.3
8.1.3
8.1.3
8.1.3
8.1.3
8.1.3
8.1.3
8.1.3
8.1.4
8.1.4
8.1.4
8.1.4
8.1.4
8.1.4
8.1.2
8.1.2
8.1.5
8.1.5
8.1.3/.4
8.1.1
8.1.1
8.2.3
8.2.3
8.2.3
8.2.3
8.2.3
8.2.4
8.2.4
8.2.4
8.2.4
8.2.4
8.2.4
8.2.2
8.2.2
8.2.5
8.2.5
8.2.3/.4
DS3134
8.1 RECEIVE SIDE
8.1.1 OVERVIEW
The receive DMA uses a scatter gather technique to write packet data into main memory. The Host will
keep track of and decide where the DMA should place the incoming packet data. There are a set of
descriptors that is handed back and forth between the DMA and the Host. Via these descriptors, the Host
can inform the DMA where to place the packet data and the DMA can tell the Host when the data is ready
to be processed.
The operation of the receive DMA has three main areas as shown in Figures 8.1.1A and 8.1.1B and
Table 8.1.1A. The Host will write to the Free Queue Descriptors informing the DMA where it can place
the incoming packet data. Associated with each free data buffer location is a free Packet Descriptor
where the DMA can write information to inform the Host about the attributes of the packet data (i.e.
status information, number of bytes, etc.) that it will output. To accommodate the various needs of packet
data, the Host can quantize the free data buffer space into two different buffer sizes. The Host will set the
size of the buffers via the Receive Large Buffer Size (RLBS) and the Receive Small Buffer Size (RSBS)
registers.
Register Name:
RLBS
Register Description: Receive Large Buffer Size Select
Register Address:
0790h
7
6
5
4
3
2
1
0
LBS7
LBS6
LBS5
LBS4
LBS3
LBS2
LBS1
LBS0
15
14
13
12
11
10
9
8
n/a
n/a
n/a
LBS12
LBS11
LBS10
LBS9
LBS8
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
Bits 0 to 12 / Large Buffer Select Bit (LBS0 to LBS12).
0000000000000 (0000h) = Buffer Size is 0 Bytes
1111111111111 (1FFFh) = Buffer Size is 8191 Bytes
Register Name:
RSBS
Register Description: Receive Small Buffer Size Select
Register Address:
0794h
7
6
5
4
3
2
1
0
SBS7
SBS6
SBS5
SBS4
SBS3
SBS2
SBS1
SBS0
15
14
13
12
11
10
9
8
n/a
n/a
n/a
SBS12
SBS11
SBS10
SBS9
SBS8
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
98 of 203
DS3134
Bits 0 to 12 / Small Buffer Select Bit (SBS0 to SBS12).
0000000000000 (0000h) = Buffer Size is 0 Bytes
1111111111111 (1FFFh) = Buffer Size is 8191 Bytes
On a HDLC channel basis in the Receive DMA Configuration RAM, the Host will instruct the DMA on
how to use the large and small buffers for the incoming packet data on that particular HDLC channel.
The Host has three options (1) only use Large Buffers, (2) only use Small Buffers, and (3) first fill a Small
Buffer then if the incoming packet requires more buffer space, use one or more Large Buffers for the
remainder of the packet. The Host selects which option via the Size field in the Receive Configuration
RAM (see Section 8.1.5). Large Buffers are best used for data intensive, time insensitive packets like
graphics files whereas small buffers are best used for time sensitive information like real-time voice.
Receive DMA Main Operational Areas Table 8.1.1A
Name
Section
Description
Packet
Descriptors
8.1.2
A dedicated area of memory that describes the location
and attributes of the packet data.
Free Queue
Descriptors
8.1.3
A dedicated area of memory that the Host will write to
inform the DMA where to store incoming packet data.
Done Queue
Descriptors
8.1.4
A dedicated area of memory that the DMA will write to
inform the Host that the packet data is ready for
processing.
The Done Queue Descriptors contain information that the DMA wishes to pass to the Host. Via the Done
Queue Descriptors the DMA informs the Host about the incoming packet data and where to find the
Packet Descriptors that it has written into main memory. Each completed Descriptor contains the starting
address of the data buffer where the packet data is stored.
If enabled, the DMA can burst read the Free Queue Descriptors and burst writes the Done Queue
Descriptors. This helps minimize PCI Bus accesses, freeing the PCI Bus up to do more time critical
functions. See Sections 8.1.3 and 8.1.4 for more details on this feature.
99 of 203
DS3134
Receive DMA Actions
A typical scenario for the Receive DMA is as follows:
1. The receive DMA gets a request from the Receive FIFO that it has packet data that needs to be sent to
the PCI Bus.
2. The receive DMA determines whether the incoming packet data should be stored in a large buffer or a
small buffer.
3. The receive DMA then reads a Free Queue Descriptor (either by reading a single descriptor or a burst
of descriptors) indicating where in main memory there exists some free data buffer space and where
the associated free Packet Descriptor resides.
4. The receive DMA starts storing packet data in the previously free buffer data space by writing it out
through the PCI Bus.
5. When the receive DMA realizes that the current data buffer is filled (by knowing the buffer size it can
calculate this), it then reads another Free Queue Descriptor to find another free data buffer and Packet
Descriptor location.
6. The receive DMA then writes the previous Packet Descriptor and creates a linked list by placing the
current descriptor in the Next Descriptor Pointer field and then it starts filling the new buffer location.
Figure 8.1.1A provides an example of Packet Descriptors being link listed together (see Channel 2).
7. This continues to all of the packet data is stored.
8. The receive DMA will either wait until a packet has been completely received or until a
programmable number (from 1 to 7) of data buffers have been filled before writing the Done Queue
Descriptor which indicates to the Host that packet data is ready for processing.
Host Actions
The Host will typically handle the receive DMA as follows:
1. The Host is always trying to make available free data buffer space and hence it tries to fill the Free
Queue Descriptor.
2. The Host will either poll or be interrupted that some incoming packet data is ready for processing.
3. The Host then reads the Done Queue Descriptor circular queue to find out which channel has data
available, what the status is, and where the receive Packet Descriptor is located.
4. The Host then reads the receive Packet Descriptor and begins processing the data.
5. The Host then reads the Next Descriptor Pointer in the link listed chain and continues this process
until either a number (from 1 to 7) of descriptors have been processed or an end of packet has been
reached.
6. The Host then checks the Done Queue Descriptor circular queue to see if any more data buffers are
ready for processing.
100 of 203
DS3134
Receive DMA Operation Figure 8.1.1A
Free Queue Descriptors
(circular queue)
00h
Free Data Buffer Address
unused
08h
Free Data Buffer Address
unused
10h
Free Desc. Ptr.
Free Desc. Ptr.
Free Data Buffer Address
unused
Free Desc. Ptr.
Open Descriptor Space
Available for Use by the DMA
Open Descriptor Space
Available for Use by the DMA
Free Data Buffer
(up to 8191 bytes)
Free Data Buffer
(up to 8191 bytes)
Free Packet Descriptors & Data Buffers
Used Packet Descriptors & Data Buffers
Done Queue Descriptors
(circular queue)
00h EOF Status CH #5
04h EOF Status CH #2
08h EOF Status CH #9
0Ch EOF Status CH #
Desc. Ptr.
Desc. Ptr.
Data Buffer Address
Status # Bytes Next Desc. Ptr.
Timestamp
CH #2
Unused
Desc. Ptr.
Desc. Ptr.
Data Buffer Address
Status # Bytes Next Desc. Ptr.
Timestamp
CH #5
Data Buffer Address
Status # Bytes Next Desc. Ptr.
Timestamp
CH #2
Data Buffer Address
Status # Bytes Next Desc. Ptr.
Timestamp
CH #2
dmarbd
First Filled
Data Buffer
for Channel 2
Data Buffer Address
Status # Bytes Next Desc. Ptr.
Timestamp
CH #9
101 of 203
Single Filled
Data Buffer
for Channel 5
Second Filled
Data Buffer
for Channel 2
Last Filled
Data Buffer
for Channel 2
Single Filled
Data Buffer
for Channel 9
DS3134
Receive DMA Memory Organization Figure 8.1.1B
Internal Chateau Registers
Main Offboard Memory
(32-Bit Address Space)
Free Data Buffer Space
Used Data Buffer Space
Free Queue Base Address (32)
Free Queue Large Buffer Host Write Pointer (16)
Free Queue Large Buffer DMA Read Pointer (16)
Receive Free Queue Descriptors:
Contains 32-Bit Addresses for Free Data
Buffers & their Associated
Free Packet Descriptors
Free Queue Small Buffer Start Address (16)
Free Queue Small Buffer Host Write Pointer (16)
Free Queue Small Buffer DMA Read Pointer (16)
Up to 64K Dual dwords
Free Queue Descriptors Allowed
Free Queue End Address (16)
Done Queue Base Address (32)
Done Queue DMA Write Pointer (16)
Receive Done Queue Descriptors:
Contains Index Pointers to
Used Packet Descriptors
Done Queue Host Read Pointer (16)
Up to 64K dwords Done Queue
Descriptors Allowed
Done Queue End Address (16)
Descriptor Base Address (32)
Receive Packet Descriptors:
Contains 32-Bit Addresses
to Free Buffer as well as
Status/Control Information and
Links to Other Packet Descriptors
dmarbd
Up to 64K Quad dwords
Descriptors Allowed
102 of 203
DS3134
8.1.2 PACKET DESCRIPTORS
In main memory resides a contiguous section up to 65,536 quad dwords that make up the Receive Packet
Descriptors. The Receive Packet Descriptors are aligned on a quad dword basis and can be placed
anywhere in the 32-bit address space via the Receive Descriptor Base Address (see Table 8.1.2A).
Associated with each descriptor is a data buffer. The data buffer can be up to 8191 bytes long and must
be a contiguous section of main memory. The host can set two different data buffer sizes via the Receive
Large Buffer Size (RLBS) and the Receive Small Buffer Size (RSBS) registers (see Section 8.1.1). If an
incoming packet requires more space than the data buffer allows, then Packet Descriptors will be linklisted together by the DMA to provide a chain of data buffers. Figure 8.1.2A is an example of how three
descriptors were linked together for an incoming packet on HDLC Channel 2. Figure 8.1.1A shows a
similar example. Channel 9 only required a single data buffer and hence only one Packet Descriptor was
used.
Packet Descriptors can be either free (i.e. available for use by the DMA) or used (i.e. currently contain
data that needs to be processed by the host). Free Packet Descriptors are pointed to by the Free Queue
Descriptors and used Packet Descriptors are pointed to by the Done Queue Descriptors.
Receive Descriptor Address Storage Table 8.1.2A
Register Name
Receive Descriptor Base Address 0 (lower word)
Receive Descriptor Base Address 1 (upper word)
Acronym
Address
RDBA0
RDBA1
0750h
0754h
Receive Descriptor Example Figure 8.1.2A
Base + 00h
Free Queue Descriptor Address
Done Queue Descriptor Pointer
Base + 10h
Channel 2 First Buffer Descriptor
Base + 20h
Channel 9 Single Buffer Descriptor
Base + 30h
Free Descriptor
Base + 40h
Free Descriptor
Base + 50h
Channel 2 Second Buffer Descriptor
Base + 60h
Free Descriptor
Base + 70h
Base + 80h
Maximum of 65536
Descriptors
Free Descriptor
Channel 2 Last Buffer Descriptor
Free Descriptor
Base + FFFD0h
Free Descriptor
Base + FFFF0h
Free Descriptor
103 of 203
DS3134
Receive Packet Descriptors Figure 8.1.2B
dword 0
Data Buffer Address (32)
dword 1
BUFS (3)
dword 2
Byte Count (13)
Next Descriptor Pointer (16)
Timestamp (24)
HDLC Channel (8)
dword 3
unused (32)
Note: The organization of the Receive Descriptor is not affected by the enabling of Big Endian
dword 0; Bits 0 to 31 / Data Buffer Address. Direct 32-bit starting address of the data buffer that is
associated with this receive descriptor.
dword 1; Bits 0 to 15 / Next Descriptor Pointer. This 16-bit value is the offset from the Receive
Descriptor Base Address of the next descriptor in the chain. Only valid if Buffer Status = 001 or 010.
Note: This is an index, not absolute address.
dword 1; Bits 16 to 28 / Byte Count. Number of bytes stored in the data buffer. Maximum is 8191
bytes (0000h = 0 bytes / 1FFFh = 8191 bytes). This byte count does not include the buffer offset. The
Host will determine the buffer offset (if any) via the Buffer Offset field in the Receive DMA
Configuration RAM (see Section 8.1.5).
dword 1; Bits 29 to 31 / Buffer Status. Must be one of the three states listed below.
001 = first buffer of a multiple buffer packet
010 = middle buffer of a multiple buffer packet
100 = last buffer of a multiple or single buffer packet (equivalent to EOF)
dword 2; Bits 0 to 7 / HDLC Channel Number. HDLC channel number, which can be from 1 to 256.
00000000 (00h) = HDLC Channel Number 1
11111111 (FFh) = HDLC Channel Number 256
dword 2; Bits 8 to 31 / Timestamp. When each descriptor is written into memory by the DMA, this
24-bit timestamp is provided to keep track of packet arrival times. The timestamp is based on the PCLK
frequency divided by 16. For a 33 MHz PCLK, the timestamp will increment every 485 ns and will
rollover every 8.13 seconds. For a 25 MHz clock, the timestamp will increment every 640 ns and will
rollover every 10.7 seconds. The host can calculate the difference in arrival times of packets by knowing
the PCLK frequency and then taking the difference in timestamp readings between consecutive Packet
Descriptors.
dword 3; Bits 0 to 31 / Unused. Not written to by the DMA. Can be used by the host. Application
Note: dword 3 is used by the Transmit DMA and in store and forward applications, the Receive and
Transmit Packet Descriptors have been designed to eliminate the need for the Host to groom the
descriptors before transmission. In these types of applications, the Host should not use dword 3 of the
Receive Packet Descriptor.
104 of 203
DS3134
8.1.3 FREE QUEUE
The Host will write to the Receive Free Queue, the 32-bit addresses of the available (i.e. free) data buffers
and their associated Packet Descriptors. The descriptor space is indicated via a 16-bit pointer which the
DMA will use along with the Receive Packet Descriptor Base Address to find the exact 32-bit address of
the associated Receive Packet Descriptor.
Receive Free Queue Descriptor Figure 8.1.3A
dword 0
Free Data Buffer Address (32)
dword 1
Unused (16)
Free Packet Descriptor Pointer (16)
Note: The organization of the Free Queue is not affected by the enabling of Big Endian
dword 0; Bits 0 to 31 / Data Buffer Address. Direct 32-bit starting address of a free data buffer.
dword 1; Bits 0 to 15 / Free Packet Descriptor Pointer. This 16-bit value is the offset from the
Receive Descriptor Base Address of the free descriptor space associated with the free data buffer in dword
0. Note: This is an index not an absolute address.
dword 1; Bits 16 to 31 / Unused. Not used by the DMA. Can be set to any value by the Host and will
be ignored by the Receive DMA.
The Receive DMA will read from the Receive Free Queue Descriptor circular queue which data buffers
and their associated descriptors are available for use by the DMA.
The Receive Free Queue Descriptor is actually a set of two circular queues. See Figure 8.1.3B. There is
one circular queue that indicates where free large buffers and their associated free descriptors exist and
there is another circular queue that indicates where free small buffers and their associated free descriptors
exist.
Large and Small Buffer Size Handling
Via the Receive Configuration RAM Buffer Size field, the DMA knows for a particular HDLC channel,
whether the incoming packets should be stored in the large or the small free data buffers. The Host
informs the DMA of the size of both the large and small buffers via the Receive Large and Small Buffer
Size (RLBS/RSBS) registers. For example, when the DMA knows that data is ready to be written onto
the PCI Bus, it checks to see if the data is to be sent to a large buffer or a small buffer and then it goes to
the appropriate Free Queue Descriptor and pulls the next available free buffer address and free descriptor
pointer. If the Host wishes to have only one buffer size, then the Receive Free Queue Small Buffer Start
Address will be set equal to the Receive Free Queue End Address and in the Receive Configuration
RAM, none of the active HDLC channels will be configured for the small buffer size.
To keep track of the addresses of the dual circular queues in the Receive Free Queue, there are a set of
internal addresses within the device that are accessed by both the Host and the DMA. On initialization,
the Host will configure all of the registers shown in Table 8.1.3B. After initialization, the DMA will only
write to (i.e. change) the read pointers and the Host will only write to the write pointers.
105 of 203
DS3134
Empty Case
The Receive Free Queue is considered empty when the read and write pointers are identical.
Receive Free Queue Empty State
read pointer >
empty descriptor
empty descriptor
empty descriptor
empty descriptor
empty descriptor
empty descriptor
empty descriptor
< write pointer
Full Case
The Receive Free Queue is considered full when the read pointer is ahead of the write pointer by one
descriptor. Hence, one descriptor must always remain empty.
Receive Free Queue Full State
read pointer >
valid descriptor
valid descriptor
empty descriptor
valid descriptor
valid descriptor
valid descriptor
valid descriptor
< write pointer
Table 8.1.3A describes the manner in which to calculate the absolute 32-bit address of the read and write
pointers for the Receive Free Queue.
Receive Free Queue Read/Write Pointer Absolute Address Calculation
Table 8.1.3A
Buffer
Large
Small
Algorithm
Absolute Address = Free Queue Base + Write Pointer * 8
Absolute Address = Free Queue Base + Read Pointer * 8
Absolute Address = Free Queue Base + Small Buffer Start * 8 + Write Pointer * 8
Absolute Address = Free Queue Base + Small Buffer Start * 8 + Read Pointer * 8
106 of 203
DS3134
Receive Free Queue Internal Address Storage Table 8.1.3B
Register Name
Acronym
Receive Free Queue Base Address 0 (lower word)
Receive Free Queue Base Address 1 (upper word)
Receive Free Queue Large Buffer Host Write Pointer
Receive Free Queue Large Buffer DMA Read Pointer
Receive Free Queue Small Buffer Start Address
Receive Free Queue Small Buffer Host Write Pointer
Receive Free Queue Small Buffer DMA Read Pointer
Receive Free Queue End Address
RFQBA0
RFQBA1
RFQLBWP
RFQLBRP
RFQSBSA
RFQSBWP
RFQSBRP
RFQEA
Address
0700h
0704h
0710h
0718h
070Ch
0714h
071Ch
0708h
Note: Both RFQSBSA & RFQEA are not absolute addresses. i.e. The absolute end address is “Base +
RFQEA * 8”.
107 of 203
DS3134
Receive Free Queue Structure Figure 8.1.3B
Free Queue Large Buffer
Host Write Pointer
Free Queue Large Buffer
DMA Read Pointer
Base + 00h
Host Readied
Free Queue Descriptor
Base + 08h
DMA Acquired
Free Queue Descriptor
Base + 10h
DMA Acquired
Free Queue Descriptor
Base + 18h
DMA Acquired
Free Queue Descriptor
Base + 20h
Host Readied
Free Queue Descriptor
Large
Buffer
Circular
Queue
Host Readied
Free Queue Descriptor
Free Queue Small Buffer
Start Address
Host Readied
Free Queue Descriptor
Host Readied
Free Queue Descriptor
Free Queue Small Buffer
Host Write Pointer
DMA Acquired
Free Queue Descriptor
DMA Acquired
Free Queue Descriptor
Small
Buffer
Circular
Queue
DMA Acquired
Free Queue Descriptor
Free Queue Small Buffer
DMA Read Pointer
Maximum of 65536
Free Queue Descriptors
Base + End Address
Host Readied
Free Queue Descriptor
Host Readied
Free Queue Descriptor
dmarfq
Once the Receive DMA is activated (by setting the RDE control bit in the Master Configuration register;
see Section 4), it can begin reading data out of the free queue. It knows where to read data out of the free
queue by reading the Read Pointer and adding it to the Base Address to obtain the actual 32-bit address.
Once the DMA has read the Free Queue, it increments the Read Pointer by two dwords. A check must be
made to make sure the incremented address does not equal or exceed either the Receive Free Queue Small
Buffer Start Address (in the case of the large buffer circular queue) or the Receive Free Queue End
Address (in the case of the small buffer circular queue). If the incremented address does equal or exceed
of these addresses, then the incremented read pointer will be set equal to 0000h.
108 of 203
DS3134
Status / Interrupts
On each read of the Free Queue by the DMA, the DMA will set either the Status Bit for Receive DMA
Large Buffer Read (RLBR) or the Status Bit for Receive DMA Small Buffer Read (RSBR) in the Status
Register for DMA (SDMA). The DMA also checks the Receive Free Queue Large Buffer Host Write
Pointer and the Receive Free Queue Small Buffer Host Write Pointer to make sure that an underflow does
not occur. If it does occur, then the DMA will set either the Status Bit for Receive DMA Large Buffer
Read Error (RLBRE) or the Status Bit for Receive DMA Small Buffer Read Error (RSBRE) in the Status
Register for DMA (SDMA) and it will not read the Free Queue nor will it increment the Read Pointer. In
such a scenario, the Receive FIFO may overflow if the Host does not provide Free Queue Descriptors.
Each of the status bits can also (if enabled) cause a hardware interrupt to occur. See Section 4 for more
details.
Free Queue Burst Reading
The DMA has the ability to read the Free Queue in bursts. This allows for a more efficient use of the PCI
Bus. The DMA can grab messages from the Free Queue in a group rather than one at a time, freeing up
the PCI Bus for more time critical functions.
Internal to the device there is a FIFO that can store up to 16 Free Queue Descriptors (32 dwords since
each descriptor occupies two dwords). The Free Queue can either operate in dual or singular circular
queue mode. The Free Queue can be divided into Large Buffer and Small Buffer. The LBSA (Large
Buffer Starting Address) and the LBEA (Large Buffer Ending Address) forms the Large Buffer Queue
and the SBSA (Small Buffer Starting Address) and the RFQEA (Receive Free Queue End Address) forms
the Small Buffer Queue. When the SBSA is not equal to, and greater than, the RFQEA the Free Queue is
set up in a dual circular mode. If the SBSA is equal to the RFQEA, the Free Queue is operating in a single
queue mode. When the Free Queue is operated as a dual circular queue supporting both large and small
buffers, then the FIFO is cut into two 8 message FIFOs. If the Free Queue is operated as a single circular
queue supporting only the large buffers, then the FIFO is set up as a single 16 descriptor FIFO. The Host
must configure the Free Queue FIFO for proper operation via the Receive DMA Queues Control
(RDMAQ) register (see below).
When enabled via the Receive Free Queue FIFO Enable (RFQFE) bit, the Free Queue FIFO will not read
the Free Queue until it reaches the Low Water Mark. When the FIFO reaches the Low Water Mark
(which is two descriptors in the dual mode or four descriptors in the single mode,) it will attempt to fill
the FIFO with additional descriptors by burst reading the Free Queue. Before it reads the Free Queue, it
checks (by examining the Receive Free Queue Host Write Pointer) to make sure that the Free Queue
contains enough descriptors to fill the Free Queue FIFO. If the Free Queue does not have enough
descriptors to fill the FIFO, then it will only read enough to keep from underflowing the Free Queue. If
the FIFO detects that there are no Free Queue descriptors available for it to read, then it will set the either
the Status Bit for Receive DMA Large Buffer Read Error (RLBRE) or the Status Bit for Receive DMA
Small Buffer Read Error (RSBRE) in the Status Register for DMA (SDMA) and it will not read the Free
Queue nor will it increment the Read Pointer. In such a scenario, the Receive FIFO may overflow if the
Host does not provide Free Queue Descriptors. If the Free Queue FIFO can read descriptors from the
Free Queue, then it will burst read them, increment the read pointer, and set either the Status Bit for
Receive DMA Large Buffer Read (RLBR) or the Status Bit for Receive DMA Small Buffer Read (RSBR)
in the Status Register for DMA (SDMA). See Section 4 for more details on Status Bits.
109 of 203
DS3134
Register Name:
RDMAQ
Register Description: Receive DMA Queues Control
Register Address:
0780h
7
6
5
4
3
2
1
0
n/a
n/a
RDQF
RDQFE RFQSF
RFQLF
n/a
RFQFE
15
14
13
12
11
10
9
8
n/a
n/a
n/a
n/a
n/a
RDQT2 RDQT1 RDQT0
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
Bit 0 / Receive Free Queue FIFO Enable (RFQFE). To enable the DMA to burst read descriptors from
the Free Queue; this bit must be set to a one. If this bit is set to zero, descriptors will be read one at a
time.
0 = Free Queue Burst Read Disabled
1 = Free Queue Burst Read Enabled
Bit 2 / Receive Free Queue Large Buffer FIFO Flush (RFQLF). When this bit is set to one, the
internal Large Buffer Free Queue FIFO will be flushed (currently loaded Free Queue Descriptors are lost).
This bit must be set to zero for proper operation.
0 = FIFO in normal operation
1 = FIFO is flushed
Bit 3 / Receive Free Queue Small Buffer FIFO Flush (RFQSF). When this bit is set to one, the
internal Small Buffer Free Queue FIFO will be flushed (currently loaded Free Queue Descriptors are lost).
This bit must be set to zero for proper operation.
0 = FIFO in normal operation
1 = FIFO is flushed
Bit 4 / Receive Done Queue FIFO Enable (RDQFE). See Section 8.1.4 for details.
Bit 5 / Receive Done Queue FIFO Flush (RDQF). See Section 8.1.4 for details.
Bits 8 to 10 / Receive Done Queue Status Bit Threshold Setting (RDQT0 to RDQT2). See Section
8.1.4 for details.
8.1.4 DONE QUEUE
The DMA will write to the Receive Done Queue when it has filled a free data buffer with packet data and
has loaded the associated Packet Descriptor with all the necessary information. The descriptor location is
indicated via a 16-bit pointer which the Host will use along with the Receive Descriptor Base Address to
find the exact 32-bit address of the associated Receive Descriptor.
Receive Done Queue Descriptor Figure 8.1.4A
dword 0
V EOF Status (3)
BUFCNT(3) HDLC Channel (8)
Descriptor Pointer (16)
Note:
1) Organization of the Done Queue is not affected by the enabling of Big Endian
2) Descriptor Pointer is an index and is not an absolute address.
110 of 203
DS3134
dword 0; Bits 0 to 15 / Descriptor Pointer. This 16-bit value is the offset from the Receive Descriptor
Base Address of a Receive Packet Descriptor that has been readied by the DMA and is available for the
host to begin processing. Note: This is index not absolute address.
dword 0; Bits 16 to 23 / HDLC Channel Number. HDLC channel number, which can be from 1 to
256.
00000000 (00h) = HDLC Channel Number 1
11111111 (FFh) = HDLC Channel Number 256
dword 0; Bits 24 to 26 / Buffer Count (BUFCNT). If a HDLC channel has been configured to only
write to the Done Queue after a packet has been completely received (i.e. the Threshold field in the
Receive DMA Configuration RAM is set to 000) then BUFCNT will always be set to 000. If the HDLC
channel has been configured via the Threshold field to write to the Done Queue after a programmable
number of buffers (from 1 to 7) have been filled, then BUFCNT corresponds to the number of buffers
which have been written to Host memory. The BUFCNT will be less than the Threshold field value when
the incoming packet does not require the number of buffers specified in the Threshold field.
000 = indicates that a complete packet has been received (only used when Threshold = 000)
001 = 1 buffer has been filled
010 = 2 buffers have been filled
111 = 7 buffers have been filled
dword 0; Bits 27 to 29 / Packet Status. These three bits report the final status of an incoming packet.
They are only valid when the EOF bit is set to a one (EOF = 1).
000 = no error, valid packet received
001 = receive FIFO overflow (remainder of the packet discarded)
010 = CRC checksum error
011 = HDLC frame abort sequence detected (remainder of the packet discarded)
100 = non-aligned byte count error (not an integral number of bytes)
101 = long frame abort (max packet length exceeded; remainder of the packet discarded)
110 = PCI abort (remainder of the packet discarded)
111 = reserved state (will never occur in normal device operation)
dword 0; Bit 30 / End Of Frame (EOF). This bit will be set to a one when this Receive Descriptor is
the last one in the current descriptor chain. This indicates that a packet has been fully received or an error
has been detected which has caused a premature termination.
dword 0; Bit 31 / Valid Done Queue Descriptor (V). This bit will be set to a zero by the Receive
DMA. Instead of reading the Receive Done Queue Read Pointer to locate completed Done Queue
Descriptors, the Host can use this bit (since the DMA will set the bit to a zero when it is written into the
queue). If the latter scheme is used, the Host must set this bit to a one when the Done Queue Descriptor is
read.
The Host will read from the Receive Done Queue to find which data buffers and their associated
descriptors are ready for processing.
111 of 203
DS3134
The Receive Done Queue is circular queue. To keep track of the addresses of the circular queue in the
Receive Done Queue, there are a set of internal addresses within the device that accessed by both the Host
and the DMA. On initialization, the Host will configure all of the registers shown in Table 8.1.4A. After
initialization, the DMA will only write to (i.e. change) the write pointer and the Host will only write to the
read pointer.
Empty Case
The Receive Done Queue is considered empty when the read and write pointers are identical.
Receive Done Queue Empty State
read pointer >
empty descriptor
empty descriptor
empty descriptor
empty descriptor
empty descriptor
empty descriptor
empty descriptor
< write pointer
Full Case
The Receive Done Queue is considered full when the read pointer is ahead of the write pointer by one
descriptor. Hence, one descriptor must always remain empty.
Receive Done Queue Full State
read pointer >
valid descriptor
valid descriptor
empty descriptor
valid descriptor
valid descriptor
valid descriptor
valid descriptor
< write pointer
112 of 203
DS3134
Receive Done Queue Internal Address Storage Table 8.1.4A
Register Name
Acronym
Address
Receive Done Queue Base Address 0 (lower word)
Receive Done Queue Base Address 1 (upper word)
Receive Done Queue DMA Write Pointer
Receive Done Queue Host Read Pointer
Receive Done Queue End Address
Receive Done Queue FIFO Flush Timer
RDQBA0
RDQBA1
RDQWP
RDQRP
RDQEA
RDQFFT
0730h
0734h
0740h
073Ch
0738h
0744h
Note:
1) Receive Done Queue End Address is not an absolute address. The absolute end address is “Base +
RDQEA * 4 ”.
Receive Done Queue Structure Figure 8.1.4B
Done Queue DMA Write Pointer
Done Queue Host Read Pointer
Maximum of 65536
Done Queue Descriptors
Base + 00h
DMA Readied
Done Queue Descriptor
Base + 04h
DMA Readied
Done Queue Descriptor
Base + 08h
Host Processed
Done Queue Descriptor
Base + 0Ch
Host Processed
Done Queue Descriptor
Base + 10h
Host Processed
Done Queue Descriptor
Base + 14h
DMA Readied
Done Queue Descriptor
Base + End Address
DMA Readied
Done Queue Descriptor
dmardq
Once the Receive DMA is activated (via the RDE control bit in the Master Configuration register; see
Section 4 for more details), it can begin writing data to the Done Queue. It knows where to write data
into the Done Queue by reading the Write Pointer and adding it to the Base Address to obtain the actual
32-bit address. Once the DMA has written to the Done Queue, it increments the Write Pointer by one
dword. A check must be made to make sure the incremented address does not exceed the Receive Done
Queue End Address. If the incremented address does exceed this address, then the incremented write
pointer will be set equal to 0000h (i.e. the Base Address).
113 of 203
DS3134
Status Bits / Interrupts
On writes to the Done Queue by the DMA, the DMA will set the Status Bit for Receive DMA Done
Queue Write (RDQW) in the Status Register for DMA (SDMA). The Host can configure the DMA to
either set this status bit on each write to the Done Queue or only after multiple (from 2 to 128) writes.
The Host controls this by setting the RDQT0 to RDQT2 bits in the Receive DMA Queues Control
(RDMAQ) register. See the description of the RDMAQ register at the end of Section 8.1.4 for more
details. The DMA also checks the Receive Done Queue Host Read Pointer to make sure that an overflow
does not occur. If this does occur, then the DMA will set the Status Bit for Receive DMA Done Queue
Write Error (RDQWE) in the Status Register for DMA (SDMA) and it will not write to the Done Queue
nor will it increment the Write Pointer. In such a scenario, packets may be lost and unrecoverable. Each
of the status bits can also (if enabled) cause a hardware interrupt to occur. See Section 4 for more details.
Buffer Write Threshold Setting
In the DMA Configuration RAM (see Section 8.1.5), there is a Host controlled field called Threshold
(bits RDT0 to RDT2) that informs the DMA on when it should write to the Done Queue. The Host has
the option to have the DMA place information in the Done Queue after a programmable number (from 1
to 7) data buffers have been filled or wait until the completed packet data has been written. The DMA
will always write to the Done Queue when it has finished receiving a packet even if the threshold has not
been met.
Done Queue Burst Writing
The DMA has the ability to write to the Done Queue in bursts. This allows for a more efficient use of the
PCI Bus. The DMA can hand off descriptors to the Done Queue in-groups rather than one at a time,
freeing up the PCI Bus for more time critical functions.
Internal to the device there is a FIFO that can store up to 8 Done Queue Descriptors (8 dwords since each
descriptor occupies one dword). The Host must configure the FIFO for proper operation via the Receive
DMA Queues Control (RDMAQ) register (see below).
When enabled via the Receive Done Queue FIFO Enable (RDQFE) bit, the Done Queue FIFO will not
write to the Done Queue until it reaches the High Water Mark. When the Done Queue FIFO reaches the
High Water Mark (which is six descriptors), it will attempt to empty the Done Queue FIFO by burst
writing to the Done Queue. Before it writes to the Done Queue, it checks (by examining the Receive
Done Queue Host Read Pointer) to make sure that the Done Queue has enough room to empty the Done
Queue FIFO. If the Done Queue does not have enough room, then it will only burst write enough
descriptors to keep from overflowing the Done Queue. If the FIFO detects that there is no room for any
descriptors to be written, then it will set the Status Bit for Receive DMA Done Queue Write Error
(RDQWE) in the Status Register for DMA (SDMA) and it will not write to the Done Queue nor will it
increment the Write Pointer. In such a scenario, packets may be lost and unrecoverable. If the Done
Queue FIFO can write descriptors to the Done Queue, then it will burst write them, increment the write
pointer, and set the Status Bit for Receive DMA Done Queue Write (RDQW) in the Status Register for
DMA (SDMA). See Section 4 for more details on Status bits.
114 of 203
DS3134
Done Queue FIFO Flush Timer
To make sure that the Done Queue FIFO does get flushed to the Done Queue on a regular basis, the
Receive Done Queue FIFO Flush Timer (RDQFFT) is used by the DMA to determine the maximum wait
time in between writes. The RDQFFT is a 16-bit programmable counter that is decremented every PCLK
divided by 256. It is only monitored by the DMA when the Receive Done Queue FIFO is enabled
(RDQFE = 1). For a 33 MHz PCLK, the timer is decremented every 7.76 us and for a 25 MHz clock it is
decremented every 10.24 us. Each time the DMA writes to the Done Queue it resets the timer to the
count placed into it by the Host. On initialization, the Host will set a value into the RDQFFT that
indicates the maximum time the DMA should wait in between writes to the Done Queue. For example,
with a PCLK of 33 MHz, the range of wait times are from 7.8 us (RDQFFT = 0001h) to 508 ms
(RDQFFT = FFFFh) and PCLK of 25 MHz, the wait times range from 10.2 us (RDQFFT = 0001h) to 671
ms (RDQFFT = FFFFh).
Register Name:
RDQFFT
Register Description: Receive Done Queue FIFO Flush Timer
Register Address:
0744h
7
6
5
4
3
2
1
0
TC7
TC6
TC5
TC4
TC3
TC2
TC1
TC0
15
14
13
12
11
10
9
8
TC15
TC14
TC13
TC12
TC11
TC10
TC9
TC8
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
Bits 0 to 15 / Receive Done Queue FIFO Flush Timer Control Bits (TC0 to TC15). Please note that
on system reset, the timer will be set to 0000h which is defined as an illegal setting. If the Receive Done
Queue FIFO is to be activated (RDQFE = 1), then the Host must first configure the timer to a proper state
and then set the RDQFE bit to one.
0000h = illegal setting
0001h = Timer Count Resets to 1
FFFFh = Timer Count Resets to 65536
Register Name:
RDMAQ
Register Description: Receive DMA Queues Control
Register Address:
0780h
7
6
5
4
3
2
1
0
n/a
n/a
RDQF
RDQFE RFQSF
RFQLF
n/a
RFQFE
15
14
13
12
11
10
9
8
n/a
n/a
n/a
n/a
n/a
RDQT2 RDQT1 RDQT0
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
Bit 0 / Receive Free Queue FIFO Enable (RFQFE). See Section 8.1.3 for details.
Bit 2 / Receive Free Queue Large Buffer FIFO Flush (RFQLF). See Section 8.1.3 for details.
Bit 3 / Receive Free Queue Small Buffer FIFO Flush (RFQSF). See Section 8.1.3 for details.
115 of 203
DS3134
Bit 4 / Receive Done Queue FIFO Enable (RDQFE). To enable the DMA to burst write descriptors to
the Done Queue; this bit must be set to a one. If this bit is set to zero, messages will be written one at a
time.
0 = Done Queue Burst Write Disabled
1 = Done Queue Burst Write Enabled
Bit 5 / Receive Done Queue FIFO Flush (RDQF). When this bit is set to one, the internal Done Queue
FIFO will be flushed by sending all data into the Done Queue. This bit must be set to zero for proper
operation.
0 = FIFO in normal operation
1 = FIFO is flushed
Bits 8 to 10 / Receive Done Queue Status Bit Threshold Setting (RDQT0 to RDQT2). These 3 bits
determine when the DMA will set the Receive DMA Done Queue Write (RDQW) status bit in the Status
Register for DMA (SDMA) register.
000 = set the RDQW status bit after each descriptor write to the Done Queue
001 = set the RDQW status bit after 2 or more descriptors are written to the Done Queue
010 = set the RDQW status bit after 4 or more descriptors are written to the Done Queue
011 = set the RDQW status bit after 8 or more descriptors are written to the Done Queue
100 = set the RDQW status bit after 16 or more descriptors are written to the Done Queue
101 = set the RDQW status bit after 32 or more descriptors are written to the Done Queue
110 = set the RDQW status bit after 64 or more descriptors are written to the Done Queue
111 = set the RDQW status bit after 128 or more descriptors are written to the Done Queue
8.1.5 DMA CHANNEL CONFIGURATION RAM
Onboard the device there is a set of 768 dwords (3 dwords per channel times 256 channels) that are used
by the host to configure the DMA and by the DMA to store values locally when it is processing a packet.
Most of the fields within the DMA Configuration RAM are for use by the DMA and the Host will never
write to these fields. The Host is only allowed to write (i.e. configure) to the lower word of dword 2 for
each HDLC channel. The Host configurable fields are denoted with a thick box as shown below.
116 of 203
DS3134
RECEIVE DMA CONFIGURATION RAM Figure 8.1.5A
msb
31
000h
HDLC
Channel 004h
1
008h
00Ch
HDLC
Channel 010h
2
014h
Receive DMA Configuration RAM
lsb
0
Current Packet Data Buffer Address (32)
Start Descriptor Pointer (16)
Threshold
Count (3)
Byte Count (13)
Current Descriptor Pointer (16)
Size CH
FBF unused (5) Threshold(3) Offset (4) (2) EN
Current Packet Data Buffer Address (32)
Start Descriptor Pointer (16)
Threshold
Count (3)
Byte Count (13)
Current Descriptor Pointer (16)
Size CH
FBF unused (5) Threshold(3) Offset (4) (2) EN
BF4h
Current Packet Data Buffer Address (32)
HDLC
Channel BF8h
Start Descriptor Pointer (16)
Current Descriptor Pointer (16)
256
Size CH
Threshold
BFCh Count (3)
Byte Count (13)
FBF unused (5) Threshold(3) Offset (4) (2) EN
dmarcram
Fields shown within the thick box
are written by the Host; all other
fields are for usage by the DMA and
can only be read by the Host
- FOR DMA USAGE ONLY / HOST CAN ONLY READ THIS FIELD dword 0; Bits 0 to 31 / Current Data Buffer Address. The current 32-bit address of the data buffer that
is being used. This address is used by the DMA to keep track of where data should be written to as it
comes in from the Receive FIFO.
- FOR DMA USAGE ONLY / HOST CAN ONLY READ THIS FIELD dword 1; Bits 0 to 15 / Current Descriptor Pointer. This 16-bit value is the offset from the Receive
Descriptor Base Address of the current Receive Descriptor being used by the DMA to describe the
specifics of the data being stored in the associated data buffer.
- FOR DMA USAGE ONLY / HOST CAN ONLY READ THIS FIELD dword 1; Bits 16 to 31 / Starting Descriptor Pointer. This 16-bit value is the offset from the Receive
Descriptor Base Address of the first Receive Descriptor in a link-list chain of descriptors. This pointer
will be written into the Done Queue by the DMA after a specified number of data buffers (see the
Threshold value below) have been filled.
- HOST MUST CONFIGURE dword 2; Bit 0 / Channel Enable (CHEN). This bit is controlled by the host to enable and disable a
HDLC channel.
0 = HDLC Channel Disabled
1 = HDLC Channel Enabled
117 of 203
DS3134
- HOST MUST CONFIGURE dword 2; Bits 1 & 2 / Buffer Size Select. These bits are controlled by the host to select the manner in
which the Receive DMA will store incoming packet data.
00 = use large size data buffers only
01 = use small size data buffers only
10 = fill a small buffer first followed then by large buffers as needed
11 = illegal state and should not be selected
- HOST MUST CONFIGURE dword 2; Bits 3 to 6 / Buffer Offset. These 4 bits are controlled by the host to determine if the packet
data written into the first data buffer should be offset by up to 15 bytes. This allows the host complete
control over the manner in which data will be written into main memory.
0000 (0h) = 0 byte offset from the data buffer address of the first data buffer
0001 (1h) = 1 byte offset from the data buffer address of the first data buffer
1111 (Fh) = 15 byte offset from the data buffer address of the first data buffer
- HOST MUST CONFIGURE dword 2; Bits 7 to 9 / Threshold. These 3 bits are controlled by the host to determine when the DMA
should write into the Done Queue that data is available for processing.
000 = DMA should write to the Done Queue only after packet reception is complete
001 = DMA should write to the Done Queue after 1 data buffer has been filled
010 = DMA should write to the Done Queue after 2 data buffers have been filled
011 = DMA should write to the Done Queue after 3 data buffers have been filled
100 = DMA should write to the Done Queue after 4 data buffers have been filled
101 = DMA should write to the Done Queue after 5 data buffers have been filled
110 = DMA should write to the Done Queue after 6 data buffers have been filled
111 = DMA should write to the Done Queue after 7 data buffers have been filled
- FOR DMA USAGE ONLY / HOST CAN ONLY READ THIS FIELD dword 2; Bits 10 to 14 / DMA Reserved. Could be any value when read. Should be set to zero when
written to by the Host.
- FOR DMA USAGE ONLY / HOST CAN ONLY READ THIS FIELD dword 2; Bit 15 / First Buffer Fill (FBF). This bit will be set to a one by the Receive DMA when it is in
the process of filling the first buffer of a packet. This bit is used by the DMA to know when to switch to
Large Buffers when the Buffer Size Select field is set to 10.
- FOR DMA USAGE ONLY / HOST CAN ONLY READ THIS FIELD dword 2; Bits 16 to 28 / Byte Count. The DMA uses these 13 bits to keep track of the number of bytes
stored in the data buffer. Maximum is 8191 bytes (0000h =0 bytes / 1FFFh = 8191 bytes).
118 of 203
DS3134
- FOR DMA USAGE ONLY / HOST CAN ONLY READ THIS FIELD dword 2; Bits 29 to 31 / Threshold Count. These 3 bits keep track of the number of data buffers that
have been filled so that the Receive DMA knows when to write to the Done Queue based on the Host
controlled field called Threshold.
000 = threshold count is 0 data buffers
001 = threshold count is 1 data buffer
010 = threshold count is 2 data buffers
011 = threshold count is 3 data buffers
100 = threshold count is 4 data buffers
101 = threshold count is 5 data buffers
110 = threshold count is 6 data buffers
111 = threshold count is 7 data buffers
Register Name:
RDMACIS
Register Description: Receive DMA Channel Configuration Indirect Select
Register Address:
0770h
7
6
5
4
3
2
1
0
HCID7
HCID6
HCID5
HCID4
HCID3
HCID2
HCID1
HCID0
15
14
13
12
11
10
9
8
IAB
IARW
n/a
n/a
n/a
RDCW2 RDCW1 RDCW0
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
Bits 0 to 7 / HDLC Channel ID (HCID0 to HCID7).
00000000 (00h) = HDLC Channel Number 1
11111111 (FFh) = HDLC Channel Number 256
Bits 8 to 10 / Receive DMA Configuration RAM Word Select Bits 0 to 2 (RDCW0 to RDCW2).
000 = lower word of dword 0
001 = upper word of dword 0
010 = lower word of dword 1
011 = upper word of dword 1
100 = lower word of dword 2 (only word that the Host can write to)
101 = upper word of dword 2
110 = illegal state
111 = illegal state
Bit 14 / Indirect Access Read/Write (IARW). When the host wishes to read data from the internal
Receive DMA Configuration RAM, this bit should be written to a one by the host. This causes the device
to begin obtaining the data from the channel location indicated by the HCID bits. During the read access,
the IAB bit will be set to one. Once the data is ready to be read from the RDMAC register, the IAB bit
will be set to zero. When the host wishes to write data to the internal Receive DMA Configuration RAM,
this bit should be written to a zero by the host. This causes the device to take the data that is current
present in the RDMAC register and write it to the channel location indicated by the HCID bits. When the
device has completed the write, the IAB bit will be set to zero.
119 of 203
DS3134
Bit 15 / Indirect Access Busy (IAB). When an indirect read or write access is in progress, this read only
bit will be set to a one. During a read operation, this bit will be set to a one until the data is ready to be
read. It will be set to zero when the data is ready to be read. During a write operation, this bit will be set
to a one while the write is taking place. It will be set to zero once the write operation has completed.
Register Name:
RDMAC
Register Description: Receive DMA Channel Configuration
Register Address:
0774h
7
6
5
4
3
2
1
D7
D6
D5
D4
D3
D2
D1
15
14
13
12
11
10
9
D15
D14
D13
D12
D11
D10
D9
Note: Bits that are underlined are read only, all other bits are read-write.
0
D0
8
D8
Bits 0 to 15 / Receive DMA Configuration RAM Data (D0 to D15). Data that is written to or read
from the Receive DMA Configuration RAM.
8.2 TRANSMIT SIDE
8.2.1 OVERVIEW
The Transmit DMA uses a scatter gather technique to read packet data from main memory. The Host will
keep track of and decide where (and when) the DMA should grab the outgoing packet data from. There
are a set of descriptors that is handed back and forth between the Host and the DMA. Via the descriptors
the Host can inform the DMA where to obtain the packet data from and the DMA can tell the Host when
the data has been transmitted.
The operation of the Transmit DMA has three main areas as shown in Figures 8.2.1A and 8.2.1B and
Table 8.2.1A. The Host will write to the Pending Queue informing the DMA which channels have packet
data that is ready to be transmitted. Associated with each Pending Queue Descriptor is a data buffer that
contains the actual data payload of the HDLC packet. The data buffers can be between 1 and 8191 bytes
in length (inclusive). If an outgoing packet requires more than memory than a data buffer contains, then
the Host can link the data buffers to handle packets of any size.
The Done Queue Descriptors contain information that the DMA wishes to pass to the Host. The DMA
will write to the Done Queue when it has completed transmitting either a complete packet or data buffer
(see the discussion on DMA Update to the Done Queue below). Via the Done Queue Descriptors, the
DMA informs the Host about the status of the outgoing packet data. If an error occurs in the
transmission, the Done Queue can be used by the Host to recover the packet data that did not get
transmitted and the Host can then re-queue the packets for transmission.
If enabled, the DMA can burst read the Pending Queue Descriptors and burst writes the Done Queue
Descriptors. This helps minimize PCI Bus accesses, freeing the PCI Bus up to do more time critical
functions. See Sections 8.2.3 and 8.2.4 for more details on this feature.
120 of 203
DS3134
Transmit DMA Main Operational Areas Table 8.2.1A
Name
Packet
Descriptors
Section
8.2.2
Description
A dedicated area of memory that describes the location
and attributes of the packet data.
Pending
Queue
Descriptors
8.2.3
A dedicated area of memory that the Host will write to
inform the DMA that packet data is queued and ready
for transmission
Done Queue
Descriptors
8.2.4
A dedicated area of memory that the DMA will write to
inform the Host that the packet data has been
transmitted
Host Linking of Data Buffers
As mentioned earlier, the data buffers are limited to a length of 8191 bytes. If an outgoing packet requires
more memory space than the available data buffer contains, then the Host can link multiple data buffers
together to handle a packet length of any size. The Host does this via the End Of Frame (EOF) bit in the
Packet Descriptor. Each data buffer has a one-to-one association with a Packet Descriptor. If the Host
wishes to link multiple data buffers together, then the EOF bit will be set to zero in all but the last data
buffer. Figure 8.2.1A contains an example for HDLC channel number 5 where the Host has linked three
data buffers together. The transmit DMA knows where to find the next data buffer when the EOF bit is
set to zero via the Next Descriptor Pointer field.
Host Linking of Packets (Packet Chaining)
The Host also has the option to link multiple packets together in a chain. Via the Chain Valid (CV) bit in
the Packet Descriptor, the Host can inform the transmit DMA that the Next Descriptor Pointer field
contains the descriptor of another HDLC packet that is ready for transmission. The transmit DMA
ignores the CV bit until it sees EOF = 1 which indicates the end of a packet. If CV = 1 when EOF = 1,
then this indicates to the transmit DMA that it should use the Next Descriptor Pointer field to find the
next packet in the chain. Figure 8.2.1C provides an example of packet chaining. Each column in Figure
8.2.1C represents a separate packet chain. In column 1, three data buffers have been linked together by
the Host for Packet #1 and then the Host has created a packet chain by setting CV = 1 in the last
descriptor of Packet #1.
121 of 203
DS3134
DMA Linking of Packets (Horizontal Link Listing)
The transmit DMA also has the ability to link packets together. Internally, the transmit DMA can store up
to two packets chains but if the Host places more packet chains into the Pending Queue, then the transmit
DMA must begin linking these chains together externally. The transmit DMA does this by writing to
Packet Descriptors. As an example, see Figure 8.2.1C. If columns 1 and 2 were the only two packet
chains queued for transmission, then the transmit DMA would not need to begin linking packet chains
together but as soon as column 3 was queued for transmission, the transmit DMA had to store the third
chain externally because it had no more room internally. The transmit DMA links the packet chain in the
third column to the one in the second column by writing the 1st descriptor of the third chain in the Next
Pending Descriptor Pointer field of the 1st descriptor of the second column (it also sets the PV bit to one).
As shown in Figure 8.2.1C, this chaining was carried one step farther to link the forth column to the third.
Priority Packets
The Host has the option to change the order in which packets are transmitted by the DMA. If the Host
sets the Priority Packet (PRI) bit in the Pending Queue Descriptor to a one, then the transmit DMA knows
that this packet is a priority packet and should be transmitted ahead of all standard packets. The rules for
packet transmission are:
1. Priority packets will be transmitted as soon as the current standard packet (not packet chain) finishes
transmission.
2. All priority packets will be transmitted before any more standard packets are transmitted.
3. Priority packets are ordered on a first come, first served basis.
Figure 8.2.1D provides an example of a set of priority packets interrupting a set of standard packets. In
the example, the first priority packet chain (shown in column 2) was read by the transmit DMA from the
Pending Queue while it was transmitting standard packet #1. It waited until standard packet #1 was
complete and then begins sending the priority packets. While column 2 was being sent, the priority
packet chains of columns 3 and 4 arrived in the Pending Queue so the transmit DMA linked column four
to column three and then waited until all of the priority packets were transmitted before returning to the
standard packet chain in column 1. Note that the packet chain in column 1 was interrupted to transmit the
priority packets. In other words, the transmit DMA did not wait for the complete packet to finish
transmitting, only the current packet.
122 of 203
DS3134
Transmit DMA Operation Figure 8.2.1A
EOF = 1
Data Buffer Address
EOF CV # Bytes Next Desc. Ptr.
unused
CH #5
unused PV Next Pend. Desc.
Done Queue Descriptors
(circular queue)
00h
Status
CH#5 Free Desc. Ptr.
04h
Status
CH#1 Free Desc. Ptr.
08h
Status
CH#
Free Desc. Ptr.
0Ch Status
CH#
Free Desc. Ptr.
10h
Status
CH#
Free Desc. Ptr.
14h
Status
CH#
Free Desc. Ptr.
EOF = 0
Data Buffer Address
EOF CV # Bytes Next Desc. Ptr.
unused
CH #1
unused PV Next Pend. Desc.
EOF = 0
Data Buffer Address
EOF CV # Bytes Next Desc. Ptr.
unused
CH #1
unused PV Next Pend. Desc.
EOF = 1
Data Buffer Address
EOF CV # Bytes Next Desc. Ptr.
unused
CH #1
unused PV Next Pend. Desc.
Transmitted
Data Buffer
for Channel 5
1st Transmitted
Data Buffer
for Channel 1
2nd Transmitted
Data Buffer
for Channel 1
Last Transmitted
Data Buffer
for Channel 1
Open Descriptor Space
Available for Use by the Host
Open Descriptor Space
Available for Use by the Host
Pending Queue Descriptors
(circular queue)
00h
PRI
CH#5 Free Desc. Ptr.
04h
PRI
CH#1 Free Desc. Ptr.
08h
PRI
CH#
Free Desc. Ptr.
0Ch
PRI
CH#
Free Desc. Ptr.
EOF = 0
Data Buffer Address
EOF CV # Bytes Next Desc. Ptr.
unused
CH #5
unused PV Next Pend. Desc.
EOF = 0
Data Buffer Address
EOF CV # Bytes Next Desc. Ptr.
unused
CH #5
unused PV Next Pend. Desc.
EOF = 1
Data Buffer Address
EOF CV # Bytes Next Desc. Ptr.
unused
CH #5
unused PV Next Pend. Desc.
dmatbd
EOF = 0
Data Buffer Address
EOF CV # Bytes Next Desc. Ptr.
unused
CH #1
unused PV Next Pend. Desc.
123 of 203
1st Queued
Data Buffer
for Channel 5
2nd Queued
Data Buffer
for Channel 5
Last Queued
Data Buffer
for Channel 5
Queued
Data Buffer
for Channel 1
DS3134
Transmit DMA Memory Organization Figure 8.2.1B
Internal Chateau Registers
Main Offboard Memory
(32-Bit Address Space)
Free Data Buffer Space
Used Data Buffer Space
Pending Queue Base Address (32)
Pending Queue Host Write Pointer (16)
Transmit Pending Queue Descriptors:
Contains Index Pointers to Packet Descriptors
of Queued Data Buffers that are Ready
to be Transmitted
Pending Queue DMA Read Pointer (16)
Up to 64K dwords
Free Queue Descriptors Allowed
Pending Queue End Address (16)
Done Queue Base Address (32)
Done Queue DMA Write Pointer (16)
Transmit Done Queue Descriptors:
Contains Index Pointers to Packet Descriptors
of Data Buffers that have been Transmitted
Done Queue Host Read Pointer (16)
Up to 64K dwords
Done Queue Descriptors Allowed
Done Queue End Address (16)
Descriptor Base Address (32)
Transmit Packet Descriptors:
Contains 32-Bit Addresses
to Data Buffers as well as
Status/Control Information and
Links to Other Packet Descriptors
dmatbd
Up to 64K Quad dwords
Descriptors Allowed
124 of 203
DS3134
Transmit DMA Packet Handling Figure 8.2.1C
Transmit DMA Configuration RAM
Last Pending Descriptor Pointer
Next Pending Descriptor Pointer
Next Descriptor Pointer
Start Descriptor Pointer
Next Pending
Descriptor Pointer
stored within the
Packet Descriptor
1st Descriptor
(EOF=0/CV=0)
Buffer 1
Packet 1
2nd Descriptor
(EOF=0/CV=0)
Buffer 2
Packet 1
Last Descriptor
(EOF=1/CV=1)
Buffer 3
Packet 1
Last Descriptor
(EOF=1/CV=0)
Buffer 1
Packet 2
Packet Chain
Column 1
1st Descriptor
(EOF=0/CV=0)
PV=1
Buffer 1
Packet 3
Next Pending
Descriptor Pointer
stored within the
Packet Descriptor
Last Descriptor
(EOF=1/CV=0)
PV=1
Buffer 1
1st Descriptor
(EOF=0/CV=0)
Buffer 1
Packet 6
Packet 5
2nd Descriptor
(EOF=0/CV=0)
2nd Descriptor
(EOF=0/CV=0)
Buffer 2
Packet 3
Buffer 2
Packet 6
Last Descriptor
(EOF=1/CV=1)
Last Descriptor
(EOF=1/CV=0)
Buffer 3
Packet 3
Buffer 3
Packet 6
Last Descriptor
(EOF=1/CV=0)
Buffer 1
Packet 4
Packet Chain
Column 2
Packet Chain
Column 3
Packet Chain
Column 4
dmatpf
125 of 203
DS3134
Transmit DMA Priority Packet Handling Figure 8.2.1D
Transmit DMA Configuration RAM
Standard Queue Pointers
Last Pending Descriptor Pointer
Priority Queue Pointers
Next Pending Descriptor Pointer Last Pending Descriptor Pointer
Next Descriptor Pointer
Next Pending Descriptor Pointer
Start Descriptor Pointer
Next Descriptor Pointer
See
Note #1
Below
1st Descriptor
(EOF=0/CV=0)
Buffer 1
Packet 1
2nd Descriptor
(EOF=0/CV=0)
Buffer 2
Packet 1
Next Pending
Descriptor Pointer
stored within the
Packet Descriptor
Last Descriptor
(EOF=1/CV=1)
Buffer 3
Packet 1
1st Descriptor
(EOF=0/CV=0)
Service
Priority
Packets
Buffer 1
Pri. Packet 1
Last Descriptor
(EOF=1/CV=0)
PV = 1 Buffer 1
Buffer 1
Pri. Packet 4
Pri. Packet 3
Last Descriptor
(EOF=1/CV=1)
Normal
Path if No
Priority
Packets
Had
Occurred
1st Descriptor
(EOF=0/CV=0)
2nd Descriptor
(EOF=0/CV=0)
Buffer 2
Pri. Packet 1
Buffer 2
Pri. Packet 4
Last Descriptor
(EOF=1/CV=0)
Last Descriptor
(EOF=1/CV=0)
Buffer 1
Pri. Packet 2
Buffer 3
Pri. Packet 4
All Priority Packets Have Been Serviced
Last Descriptor
(EOF=1/CV=0)
dmatppf
Buffer 1
Packet 2
Standard
Packet Chain
Column 1
Priority
Packet Chain
Column 2
Priority
Packet Chain
Column 3
Priority
Packet Chain
Column 4
Note #1
The Start Descriptor Pointer field in the Transmit DMA Configuration RAM is used by
both the nomal and priority pending queues.
126 of 203
DS3134
DMA UPDATES TO THE DONE QUEUE
The Host has two options as to when the transmit DMA should write descriptors that have completed
transmission to the Done Queue. On a channel-by-channel basis, via the Done Queue Select (DQS) bit in
the Transmit DMA Configuration RAM, the Host can condition the DMA to:
1. Write to the Done Queue only when the complete HDLC packet has been transmitted (DQS = 0)
2. Write to the Done Queue when each data buffer has been transmitted (DQS = 1)
The Status field in the Done Queue Descriptor will be configured based on the setting of the DQS bit. If
DQS = 0, then when a packet has successfully completed transmission the Status field will be set to 000.
If DQS = 1, then when the first data buffer has successfully completed transmission the Status field will
be set to 001. When each middle buffer (i.e. the second through the next to last) has successfully
completed transmission the Status field will be set to 010. When the last data buffer of a packet has
successfully completed transmission, the Status field will be set to 011.
ERROR CONDITIONS
While processing packets for transmission, the DMA can encounter a number of error conditions, which
include;
- PCI error (an abort )
- Transmit FIFO underflow
- Channel is disabled (CHEN = 0) in the Transmit DMA Configuration RAM
- Channel number discrepancy between the Pending Queue & the Packet Descriptor
- Byte count of 0 bytes in the Packet Descriptor.
If any of these errors occur, the transmit DMA will automatically disable the affected channel by setting
the Channel Enable (CHEN) bit in the Transmit DMA Configuration RAM to zero and then it will write
the current descriptor into the Done Queue with the appropriate error status as shown in Table 8.2.1B
below.
Done Queue Error Status Conditions Table 8.2.1B
Packet
Status
100
101
110
111
Description of the Error
software provisioning error; this channel was not enabled
descriptor error; either byte count = 0 or channel code inconsistent with
Pending Queue
PCI error; abort
transmit FIFO error; it has underflowed
Since the transmit DMA has disabled the channel, any remaining queued descriptors will not be
transmitted and will be written to the Done Queue with a Packet Status of 100 (i.e. reporting that the
channel was not enabled). At this point, the Host has two options. Option 1, it can wait until all of the
remaining queued descriptors are written to the Done Queue with an errored status and then manually reenable the channel by setting the CHEN bit to one and then re-queue all of the affected packets. Option 2,
as soon as it detects an errored status, it can force the channel active again by setting the Channel Reset
(CHRST) bit to a one for the next descriptor that it writes to the Pending Queue for the affected channel.
As soon as the transmit DMA detects that the CHRST is set to a one, it will re-enable the channel by
127 of 203
DS3134
forcing the CHEN bit to a one. The DMA will not re-enable the channel until it has finished writing all of
the previously queued descriptors to the Done Queue. Then the Host can collect the errored descriptors as
they arrive in the Done Queue and then re-queue them for transmission by writing descriptors to the
Pending Queue so the transmit DMA knows where to find the packets that did not get transmitted
(software housekeeping note: the Host must set the Next Pending Descriptor Pointer and PV fields in the
Packet Descriptor to zero to ready them for transmission). The second option allows the software a
cleaner error recovery technique. See Figure 8.2.1E for more details.
Transmit DMA Error Recovery Algorithm Figure 8.2.1E
Read Done Queue
Data Buffers &
Packet Descriptor
Space Available
for Reuse
No
Status = 1xx?
Yes
Set CHRST = 1
for the Next
Descriptor
Written to the
Pending Queue
Set the PV & the Next
Pending Descriptor Pointer
Fields to zero in the Errored
Packet Descriptor
Place the Errored Packet
Descriptor back into the
Pending Queue for
Re-transmission
dmaerror
Host Actions
The Host will typically handle the Transmit DMA as follows:
1. The Host will place readied packets into the Pending Queue.
2. The Host will either poll or be interrupted that some outgoing packets have completed transmission
and that it should read the Done Queue.
3. If Done Queue reports that an error was incurred and that a packet was not transmitted, then the Host
must re-queue the packet for transmission.
Transmit DMA Actions
A typical scenario for the Transmit DMA is as follows:
1. The transmit DMA constantly reads the Pending Queue looking for packets that are queued for
transmission.
2. The transmit DMA will update the Done Queue as packets or data buffers complete transmission.
3. If an error occurs, then the transmit DMA will disable the channel and wait for the Host to request that
the channel be enabled.
128 of 203
DS3134
8.2.2 Packet Descriptors
In main memory resides a contiguous section up to 65,536 quad dwords that make up the Transmit Packet
Descriptors. The Transmit Packet Descriptors are aligned on a quad dword basis and can be placed
anywhere in the 32-bit address space via the Transmit Descriptor Base Address (see Table 8.2.2A).
Associated with each descriptor is a data buffer. The data buffer can be up to 8191 bytes long and must
be a contiguous section of main memory. The host will inform the DMA of the actual size of the data
buffer via the Byte Count field that resides in the Packet Descriptor. If an outgoing packet requires more
space than the data buffer allows, then Packet Descriptors will be link-listed together by the Host to
provide a chain of data buffers. Figure 8.2.2A is an example of how three descriptors were linked
together for an incoming packet on HDLC Channel 7. Channel 3 only required a single data buffer and
hence only one Packet Descriptor was used. Figure 8.2.1A shows a similar example for channels5 and 1.
Packet Descriptors can be either pending (i.e. queued up by the host and ready for transmission by the
DMA) or completed (i.e. have been transmitted by the DMA and are available for processing by the host).
Pending Packet Descriptors are pointed to by the Pending Queue Descriptors and completed Packet
Descriptors are pointed to by the Done Queue Descriptors.
Transmit Descriptor Address Storage Table 8.2.2A
Register Name
Acronym
Transmit Descriptor Base Address 0 (lower word)
Transmit Descriptor Base Address 1 (upper word)
TDBA0
TDBA1
Transmit Descriptor Example Figure 8.2.2A
Done Queue Descriptor Pointer
Pending Queue Descriptor Address
Base + 00h
CH 5 Single Sent Buffer Descriptor
Base + 10h
CH 7 1st Queued Buffer Descriptor
Base + 20h
CH 3 Single Queued Buffer Desc.
Base + 30h
CH 7 Sent 1st Buffer Descriptor
Base + 40h
Base + 50h
Base + 60h
Free Descriptor
CH 7 2nd Queued Buffer Descriptor
Free Descriptor
Base + 70h CH 7 Last Queued Buffer Descriptor
Base + 80h
Maximum of 65536
Descriptors
CH 7 Last Sent Buffer Descriptor
Base + FFFD0h
Free Descriptor
Base + FFFF0h
Free Descriptor
dmatde
129 of 203
Address
0850h
0854h
DS3134
Transmit Packet Descriptors Figure 8.2.2B
dword 0
Data Buffer Address (32)
dword 1
EOF CV
dword 2
unused
Byte Count (13)
Next Descriptor Pointer (16)
unused (24)
HDLC Channel (8)
dword 3
unused (15)
PV
Next Pending Descriptor Pointer (16)
Note:
1. The organization of the Transmit Descriptor is not affected by the enabling of Big Endian
2. The format of the Transmit Descriptor is almost identical to the Receive Descriptor; this lessens the
burden of the Host in preparing descriptors in store-and-forward applications
3. Next Descriptor pointer is an index and not an absolute address.
dword 0; Bits 0 to 31 / Data Buffer Address. Direct 32-bit starting address of the data buffer that is associated
with this transmits descriptor.
dword 1; Bits 0 to 15 / Next Descriptor Pointer. This 16-bit value is the offset from the Transmit Descriptor
Base Address of the next descriptor in the chain. Only valid if EOF = 0 (next descriptor in the same packet chain)
or if EOF = 1 and CV = 1 (first descriptor in the next packet).
dword 1; Bits 16 to 28 / Byte Count. Number of bytes stored in the data buffer. Maximum is 8191 bytes (0000h
= 0 bytes / 1FFFh = 8191 bytes).
dword 1; Bit 29 / Unused. This bit is ignored by the transmit DMA and can be set to any value.
dword 1; Bit 30 / Chain Valid (CV). If CV is set to a one when EOF = 1, then this indicates that the Next
Descriptor Pointer field is valid and corresponds to the first descriptor of the next packet that is queued up for
transmission. The CV bit is ignored when EOF = 0.
dword 1; Bit 31 / End Of Frame (EOF). When set to a one, this bit indicates that the descriptor is the last
buffer in the current packet. When set to a zero, this bit indicates that Next Descriptor Pointer field is valid and
points to the next descriptor in the packet chain.
dword 2; Bits 0 to 7 / HDLC Channel Number. HDLC channel number, which can be from 1 to 256.
00000000 (00h) = HDLC Channel Number 1
11111111 (FFh) = HDLC Channel Number 256
dword 2; Bits 8 to 31 / Unused. These bits are ignored by the transmit DMA and can be set to any value.
dword 3; Bits 0 to 15 / Next Pending Descriptor Pointer. This 16-bit value is the offset from the Transmit
Descriptor Base Address to another the descriptor chain that is queued up for transmission. The transmit DMA
can store up to 2 queued packet chains internally but additional packet chains must be stored as a link list by the
transmit DMA using this field. This field is only valid if PV = 1 and it should be set to 0000h by the Host when
the Host is preparing the descriptor.
dword 3; Bit 16 / Pending Descriptor Valid (PV). If set, this bit indicates that the Next Pending Descriptor
Pointer field is valid and corresponds to the first descriptor of the next packet chain that is queued up for
transmission. This field is written to by the transmit DMA to link descriptors together and should always be set to
0 by the Host.
dword 3; Bits 17 to 31 / Unused. These bits are ignored by the transmit DMA and can be set to any value.
130 of 203
DS3134
8.2.3 PENDING QUEUE
The Host will write to the Transmit Pending Queue, the location of the readied descriptor, channel
number and control information. The descriptor space is indicated via a 16-bit pointer which the DMA
will use along with the Transmit Packet Descriptor Base Address to find the exact 32-bit address of the
associated Transmit Packet Descriptor.
Transmit Pending Queue Descriptor Figure 8.2.3A
dword 0
unused Status(3)
CH RST
PRI
HDLC Channel (8)
Descriptor Pointer (16)
Note:
1) rganization of the Pending Queue is not affected by the enabling of Big Endian
2) Descriptor pointer is an index and not an absolute address.
dword 0; Bits 0 to 15 / Descriptor Pointer. This 16-bit value is the offset from the Transmit Descriptor
Base Address to the first descriptor in a packet chain (can be a single descriptor) that is queued up for
transmission.
dword 0; Bits 16 to 23 / HDLC Channel Number. HDLC channel number, which can be from 1 to
256.
00000000 (00h) = HDLC Channel Number 1
11111111 (FFh) = HDLC Channel Number 256
dword 0; Bit 24 / Priority Packet (PRI). If this bit is set to a one, then this indicates to the transmit
DMA that the packet or packet chain pointed to by the Descriptor Pointer field should be transmitted
immediately after the current packet transmission (whether it be standard or priority) is complete.
dword 0; Bit 25 / Channel Reset (CHRST). Under normal operating conditions, this bit should always
be set to zero. When an error condition occurs and the transmit DMA places the channel into an out-ofservice state by setting the Channel Enable (CHEN) bit in the Transmit DMA Configuration Register to
zero, the Host can force the channel active again by setting the CHRST bit to a one. Only the first
descriptor loaded into the Pending Queue after an error condition should have CHRST set to a one, all
subsequent descriptors (until another error condition occurs) should have CHRST set to zero. The
transmit DMA examines this bit and will force channel active (CHEN = 1) if CHRST is set to one. If
CHRST is set to zero, then the transmit DMA will not modify the state of the CHEN bit. See Section
8.2.1 for more details on how error conditions are handled.
dword 0; Bits 26 to 28 / Packet Status. Not used by the DMA. Can be set to any value by the Host and
will be ignored by the transmit DMA. This field will be used when the transmit DMA when it writes to
the Done Queue to inform the Host of the status of the outgoing packet data.
dword 0; Bits 29 to 31 / Unused. Not used by the DMA. Can be set to any value by the Host and will
be ignored by the transmit DMA.
131 of 203
DS3134
The Transmit DMA will read from the Transmit Pending Queue Descriptor circular queue which data
buffers and their associated descriptors are ready for transmission. To keep track of the addresses of the
circular queue in the Transmit Pending Queue, there are a set of internal addresses within the device that
are accessed by both the Host and the DMA. On initialization, the Host will configure all of the registers
shown in Table 8.2.3A. After initialization, the DMA will only write to (i.e. change) the read pointers
and the Host will only write to the write pointers.
Empty Case
The Transmit Pending Queue is considered empty when the read and write pointers are identical.
Transmit Pending Queue Empty State
read pointer >
empty descriptor
empty descriptor
empty descriptor
empty descriptor
empty descriptor
empty descriptor
empty descriptor
< write pointer
Full Case
The Transmit Pending Queue is considered full when the read pointer is ahead of the write pointer by one
descriptor. Hence, one descriptor must always remain empty.
Transmit Pending Queue Full State
read pointer >
valid descriptor
valid descriptor
empty descriptor
valid descriptor
valid descriptor
valid descriptor
valid descriptor
< write pointer
132 of 203
DS3134
Transmit Pending Queue Internal Address Storage Table 8.2.3A
Register Name
Acronym
Address
Transmit Pending Queue Base Address 0 (lower word)
TPQBA0
0800h
Transmit Pending Queue Base Address 1 (upper word)
TPQBA1
0804h
Transmit Pending Queue Host Write Pointer
TPQWP
080Ch
Transmit Pending Queue DMA Read Pointer
TPQRP
0810h
Transmit Pending Queue End Address
TPQEA
0808h
Note: Transmit Free Queue End Address is not an absolute address. The absolute end address is “Base +
TPQEA”.
Transmit Pending Queue Structure Figure 8.2.3B
Pending Queue Host Write Pointer
Pending Queue DMA Read Pointer
Maximum of 65536
Pending Queue Descriptors
Base + 00h
Host Readied
Pending Queue Descriptor
Base + 04h
Host Readied
Pending Queue Descriptor
Base + 08h
DMA Acquired
Pending Queue Descriptor
Base + 0Ch
DMA Acquired
Pending Queue Descriptor
Base + 10h
DMA Acquired
Pending Queue Descriptor
Base + 14h
Host Readied
Pending Queue Descriptor
Base + End Address
Host Readied
Pending Queue Descriptor
dmatpq
Once the Transmit DMA is activated (by setting the TDE control bit in the Master Configuration register;
see Section 4), it can begin reading data out of the pending queue. It knows where to read data out of the
pending queue by reading the Read Pointer and adding it to the Base Address to obtain the actual 32-bit
address. Once the DMA has read the Pending Queue, it increments the Read Pointer by one dword. A
check must be made to make sure the incremented address does not exceed the Transmit Pending Queue
End Address. If the incremented address does exceed this address, then the incremented read pointer will
be set equal to 0000h.
Status / Interrupts
On each read of the Pending Queue by the DMA, the DMA will set the Status Bit for Transmit DMA
Pending Queue Read (TPQR) in the Status Register for DMA (SDMA). The status bits can also (if
enabled) cause a hardware interrupt to occur. See Section 4 for more details.
133 of 203
DS3134
Pending Queue Burst Reading
The DMA has the ability to read the Pending Queue in bursts. This allows for a more efficient use of the
PCI Bus. The DMA can grab descriptors from the Pending Queue in-groups rather than one at a time,
freeing up the PCI Bus for more time critical functions.
Internal to the device there is a FIFO that can store up to 16 Pending Queue Descriptors (16 dwords since
each descriptor occupies one dword). The Host must configure the Pending Queue FIFO for proper
operation via the Transmit DMA Queues Control (TDMAQ) register (see below).
When enabled via the Transmit Pending Queue FIFO Enable (TPQFE) bit, the Pending Queue FIFO will
not read the Pending Queue until it reaches the Low Water Mark. When the Pending Queue FIFO reaches
the Low Water Mark (which is four descriptors), it will attempt to fill the FIFO with additional
descriptors by burst reading the Pending Queue. Before it reads the Pending Queue, it checks (by
examining the Transmit Pending Queue Host Write Pointer) to make sure that the Pending Queue
contains enough descriptors to fill the Pending Queue FIFO. If the Pending Queue does not have enough
descriptors to fill the FIFO, then it will only read enough to empty the Pending Queue. If the FIFO
detects that there are no Pending Queue descriptors available for it to read, then it will wait and try again
later. If the Pending Queue FIFO can read descriptors from the Pending Queue, then it will burst read
them, increment the read pointer, and set the Status Bit for Transmit DMA Pending Queue Read (TPQR)
in the Status Register for DMA (SDMA). See Section 4 for more details on Status Bits.
Register Name:
TDMAQ
Register Description: Transmit DMA Queues Control
Register Address:
0880h
7
6
5
4
3
2
1
0
n/a
n/a
n/a
n/a
TDQF
TDQFE
TPQF
TPQFE
15
14
13
12
11
10
9
8
n/a
n/a
n/a
n/a
n/a
TDQT2 TDQT1 TDQT0
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
Bit 0 / Transmit Pending Queue FIFO Enable (TPQFE). To enable the DMA to burst read descriptors
from the Pending Queue; this bit must be set to a one. If this bit is set to zero, descriptors will be read one
at a time.
0 = Pending Queue Burst Read Disabled
1 = Pending Queue Burst Read Enabled
Bit 1 / Transmit Pending Queue FIFO Flush (TPQF). When this bit is set to one, the internal Pending
Queue FIFO will be flushed (currently loaded Pending Queue Descriptors are lost). This bit must be set
to zero for proper operation.
0 = FIFO in normal operation
1 = FIFO is flushed
134 of 203
DS3134
Bit 2 / Transmit Done Queue FIFO Enable (TDQFE). See Section 8.2.4 for details.
Bit 3 / Transmit Done Queue FIFO Flush (TDQF). See Section 8.2.4 for details.
Bits 8 to 10 / Transmit Done Queue Status Bit Threshold Setting (TDQT0 to TDQT2). See Section
8.2.4 for more details.
8.2.4 DONE QUEUE
The DMA will write to the Transmit Done Queue when it has finished either transmitting a complete
packet chain or a complete data buffer. This option is selected by the Host when it configures the DQS
field in the Transmit DMA Configuration RAM. See Section 8.2.5 for more details on the Transmit
DMA Configuration RAM. The descriptor location is indicated in the Done Queue via a 16-bit pointer
which the Host will use along with the Transmit Descriptor Base Address to find the exact 32-bit address
of the associated Transmit Descriptor.
Transmit Done Queue Descriptor Figure 8.2.4A
dword 0
unused
Status(3)
CH RST
PRI
HDLC Channel (8)
Descriptor Pointer (16)
Note: The organization of the Done Queue is not affected by the enabling of Big Endian
dword 0; Bits 0 to 15 / Descriptor Pointer. This 16-bit value is the offset from the Transmit Descriptor
Base Address to either the first descriptor in a HDLC packet (can be a single descriptor) that has been
transmitted (DQS = 0) or the descriptor that corresponds to a single data buffer that has been transmitted
(DQS = 1).
dword 0; Bits 16 to 23 / HDLC Channel Number. HDLC channel number, which can be from 1 to
256.
00000000 (00h) = HDLC Channel Number 1
11111111 (FFh) = HDLC Channel Number 256
dword 0; Bit 24 / Priority Packet (PRI). This field is meaningless in the Done Queue and could be set
to any value. See the Pending Queue description in Section 8.2.3 for details.
dword 0; Bit 25 / Channel Reset (CH RST). This field is meaningless in the Done Queue and could be
set to any value. See the Pending Queue description in Section 8.2.3 for details.
dword 0; Bits 26 to 28 / Packet Status. These 3 bits report the final status of an outgoing packet. All
of the error states cause a HDLC abort sequence (8 ones in a row followed by continuous Interfill Bytes of
either FFh or 7Eh) to be sent and the channel will be placed out of service by the transmit DMA setting
the Channel Enable (CHEN) bit in the Transmit DMA Configuration RAM to zero. The status state of
000 will only be used when the channel has been configured by the Host to write to the Done Queue only
after a complete HDLC packet (can be a single data buffer) has been transmitted (i.e. DQS = 0). The
status states of 001, 010, and 011 will only be used when the channel has been configured by the Host to
write to the Done Queue after each data buffer has been transmitted (i.e. DQS = 1).
000 = packet transmission complete and the Descriptor Pointer field corresponds to the first
descriptor in a HDLC packet (can be a single descriptor) that has been transmitted (DQS = 0)
001 = first buffer transmission complete of a multi (or single) buffer packet (DQS = 1)
135 of 203
DS3134
010 = middle buffer transmission complete of a multi-buffer packet (DQS = 1)
011 = last buffer transmission complete of a multi-buffer packet (DQS = 1)
100 = software provisioning error; this channel was not enabled
101 = descriptor error; either byte count = 0 or channel code inconsistent with Pending Queue
110 = PCI error
111 = transmit FIFO error; it has underflowed
dword 0; Bits 29 to 31 / Unused. Not used by the DMA. Could be any value when read.
The Host will read from the Transmit Done Queue to find which data buffers and their associated
descriptors have completed transmission. The Transmit Done Queue is circular queue. To keep track of
the addresses of the circular queue in the Transmit Done Queue, there are a set of internal addresses
within the device that accessed by both the Host and the DMA. On initialization, the Host will configure
all of the registers shown in Table 8.2.4A. After initialization, the DMA will only write to (i.e. change)
the write pointer and the Host will only write to the read pointer.
Empty Case
The Transmit Done Queue is considered empty when the read and write pointers are identical.
Transmit Done Queue Empty State
read pointer >
empty descriptor
empty descriptor
empty descriptor
empty descriptor
empty descriptor
empty descriptor
empty descriptor
< write pointer
Full Case
The Transmit Done Queue is considered full when the read pointer is ahead of the write pointer by one
descriptor. Hence, one descriptor must always remain empty.
Transmit Done Queue Full State
read pointer >
valid descriptor
valid descriptor
empty descriptor
valid descriptor
valid descriptor
valid descriptor
valid descriptor
< write pointer
136 of 203
DS3134
Transmit Done Queue Internal Address Storage Table 8.2.4A
Register Name
Acronym
Address
Transmit Done Queue Base Address 0 (lower word)
TDQBA0
0830h
Transmit Done Queue Base Address 1 (upper word)
TDQBA1
0834h
Transmit Done Queue DMA Write Pointer
TDQWP
0840h
Transmit Done Queue Host Read Pointer
TDQRP
083Ch
Transmit Done Queue End Address
TDQEA
0838h
Transmit Done Queue FIFO Flush Timer
TDQFFT
0844h
Note: Transmit Done Queue End Address is not an absolute address. The absolute end address is “Base +
TDQEA * 4”.
Transmit Done Queue Structure Figure 8.2.4B
Base + 00h
DMA Readied
Done Queue Descriptor
Base + 04h
DMA Readied
Done Queue Descriptor
Base + 08h
Host Processed
Done Queue Descriptor
Base + 0Ch
Host Processed
Done Queue Descriptor
Base + 10h
Host Processed
Done Queue Descriptor
Base + 14h
DMA Readied
Done Queue Descriptor
Base + End Address
DMA Readied
Done Queue Descriptor
Done Queue DMA Write Pointer
Done Queue Host Read Pointer
Maximum of 65536
Done Queue Descriptors
dmatdq
Once the Transmit DMA is activated (via the TDE control bit in the Master Configuration register; see
Section 4 for more details), it can begin writing data to the Done Queue. It knows where to write data
into the Done Queue by reading the Write Pointer and adding it to the Base Address to obtain the actual
32-bit address. Once the DMA has written to the Done Queue, it increments the Write Pointer by one
dword. A check must be made to make sure the incremented address does not exceed the Transmit Done
Queue End Address. If the incremented address does exceed this address, then the incremented write
pointer will be set equal to 0000h (i.e. the Base Address).
Status Bits / Interrupts
On writes to the Done Queue by the DMA, the DMA will set the Status Bit for Transmit DMA Done
Queue Write (TDQW) in the Status Register for DMA (SDMA). The Host can configure the DMA to
either set this status bit on each write to the Done Queue or only after multiple (from 2 to 128) writes.
The Host controls this by setting the TDQT0 to TDQT2 bits in the Transmit DMA Queues Control
(TDMAQ) register. See the description of the TDMAQ register at the end of this section for more details.
137 of 203
DS3134
The DMA also checks the Transmit Done Queue Host Read Pointer to make sure that an overflow does
not occur. If this does occur, then the DMA will set the Status Bit for Transmit DMA Done Queue Write
Error (TDQWE) in the Status Register for DMA (SDMA) and it will not write to the Done Queue nor will
it increment the Write Pointer. In such a scenario, information on transmitted packets will be lost and
unrecoverable. Each of the status bits can also (if enabled) cause a hardware interrupt to occur. See
Section 4 for more details.
Done Queue Burst Writing
The DMA has the ability to write to the Done Queue in bursts. This allows for a more efficient use of the
PCI Bus. The DMA can hand off descriptors to the Done Queue in-groups rather than one at a time,
freeing up the PCI Bus for more time critical functions.
Internal to the device there is a FIFO that can store up to 8 Done Queue Descriptors (8 dwords since each
descriptor occupies one dword). The Host must configure the FIFO for proper operation via the Transmit
DMA Queues Control (TDMAQ) register (see below).
When enabled via the Transmit Done Queue FIFO Enable (TDQFE) bit, the Done Queue FIFO will not
write to the Done Queue until it reaches the High Water Mark. When the Done Queue FIFO reaches the
High Water Mark (which is six descriptors), it will attempt to empty the Done Queue FIFO by burst
writing to the Done Queue. Before it writes to the Done Queue, it checks (by examining the Transmit
Done Queue Host Read Pointer) to make sure that the Done Queue has enough room to empty the Done
Queue FIFO. If the Done Queue does not have enough room, then it will only burst write enough
descriptors to keep from overflowing the Done Queue. If the FIFO detects that there is no room for any
descriptors to be written, then it will set the Status Bit for Transmit DMA Done Queue Write Error
(TDQWE) in the Status Register for DMA (SDMA) and it will not write to the Done Queue nor will it
increment the Write Pointer. In such a scenario, information on transmitted packets will be lost and
unrecoverable. If the Done Queue FIFO can write descriptors to the Done Queue, then it will burst write
them, increment the write pointer, and set the Status Bit for Transmit DMA Done Queue Write (TDQW)
in the Status Register for DMA (SDMA). See Section 4 for more details on Status bits.
Done Queue FIFO Flush Timer
To make sure that the Done Queue FIFO does get flushed to the Done Queue on a regular basis, the
Transmit Done Queue FIFO Flush Timer (TDQFFT) is used by the DMA to determine the maximum wait
time in between writes. The TDQFFT is a 16-bit programmable counter that is decremented every PCLK
divided by 256. It is only monitored by the DMA when the Transmit Done Queue FIFO is enabled
(TDQFE = 1). For a 33 MHz PCLK, the timer is decremented every 7.76 us and for a 25 MHz clock it is
decremented every 10.24 us. Each time the DMA writes to the Done Queue it resets the timer to the
count placed into it by the Host. On initialization, the Host will set a value into the TDQFFT that
indicates the maximum time the DMA should wait in between writes to the Done Queue. For example,
with a PCLK of 33 MHz, the range of wait times are from 7.8 us (RDQFFT = 0001h) to 508 ms
(RDQFFT = FFFFh) and PCLK of 25 MHz, the wait times range from 10.2 us (RDQFFT = 0001h) to
671 ms (RDQFFT = FFFFh).
138 of 203
DS3134
Register Name:
TDQFFT
Register Description: Transmit Done Queue FIFO Flush Timer
Register Address:
0844h
7
6
5
4
3
2
1
0
TC7
TC6
TC5
TC4
TC3
TC2
TC1
TC0
15
14
13
12
11
10
9
8
TC15
TC14
TC13
TC12
TC11
TC10
TC9
TC8
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
Bits 0 to 15 / Transmit Done Queue FIFO Flush Timer Control Bits (TC0 to TC15). Please note that
on system reset, the timer will be set to 0000h which is defined as an illegal setting. If the Receive Done
Queue FIFO is to be activated (TDQFE = 1), then the Host must first configure the timer to a proper state
and then set the TDQFE bit to one.
0000h = illegal setting
0001h = Timer Count Resets to 1
FFFFh = Timer Count Resets to 65536
Register Name:
TDMAQ
Register Description: Transmit DMA Queues Control
Register Address:
0880h
7
6
5
4
3
2
1
0
n/a
n/a
n/a
n/a
TDQF
TDQFE
TPQF
TPQFE
15
14
13
12
11
10
9
8
n/a
n/a
n/a
n/a
n/a
TDQT2 TDQT1 TDQT0
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
Bit 0 / Transmit Pending Queue FIFO Enable (TPQFE). See Section 8.2.3 for details.
Bit 1 / Transmit Pending Queue FIFO Flush (TPQLF). See Section 8.2.3 for details.
Bit 3 / Transmit Done Queue FIFO Enable (TDQFE). To enable the DMA to burst write descriptors
to the Done Queue; this bit must be set to a one. If this bit is set to zero, descriptors will be written one at
a time.
0 = Done Queue Burst Write Disabled
1 = Done Queue Burst Write Enabled
Bit 4 / Transmit Done Queue FIFO Flush (TDQF). When this bit is set to one, the internal Done
Queue FIFO will be flushed by sending all data into the Done Queue. This bit must be set to zero for
proper operation.
0 = FIFO in normal operation
1 = FIFO is flushed
139 of 203
DS3134
Bits 8 to 10 / Transmit Done Queue Status Bit Threshold Setting (TDQT0 to TDQT2). These 3 bits
determine when the DMA will set the Transmit DMA Done Queue Write (TDQW) status bit in the Status
Register for DMA (SDMA) register.
000 = set the TDQW status bit after each descriptor write to the Done Queue
001 = set the TDQW status bit after 2 or more descriptors are written to the Done Queue
010 = set the TDQW status bit after 4 or more descriptors are written to the Done Queue
011 = set the TDQW status bit after 8 or more descriptors are written to the Done Queue
100 = set the TDQW status bit after 16 or more descriptors are written to the Done Queue
101 = set the TDQW status bit after 32 or more descriptors are written to the Done Queue
110 = set the TDQW status bit after 64 or more descriptors are written to the Done Queue
111 = set the TDQW status bit after 128 or more descriptors are written to the Done Queue
8.2.5 DMA CHANNEL CONFIGURATION RAM
Onboard the device there is a set of 1536 dwords (6 dwords per channel times 256 channels) that are used
by the Host to configure the DMA and by the DMA to store values locally when it is processing a packet.
Most of the fields within the DMA Configuration RAM are for use by the DMA and the Host will never
write to these fields. The Host is only allowed to write (i.e. configure) to the lower word of dword 1 for
each HDLC channel. The Host configurable fields are denoted with a thick box as shown below.
Transmit DMA Configuration RAM Figure 8.2.5A
msb
31
Current Packet Data Buffer Address (32)
000h
004h
unused (9)
HDLC
008h
Channel
1
00Ch
PRI
PPP ST(2)
unCH
used DQS EN
Next Pending Descriptor Pointer (16)
unused (16)
Next Priority Descriptor Pointer (16)
Next Priority Pending Descriptor Pointer (16)
Last Priority Pending Descriptor Pointer (16)
Current Packet Data Buffer Address (32)
unused (9)
PRI
PPP ST(2)
PEND
ST(2) EOF CV
Start Descriptor Pointer (16)
unCH
used DQS EN
Next Pending Descriptor Pointer (16)
unused (16)
17F8h
Byte Count (13)
Next Descriptor Pointer (16)
Last Pending Descriptor Pointer (16)
17F4h
17FCh
Byte Count (13)
Next Descriptor Pointer (16)
Last Pending Descriptor Pointer (16)
17D8h
HDLC
17DCh
Channel
256
17F0h
PEND
ST(2) EOF CV
Start Descriptor Pointer (16)
010h
014h
lsb
0
Transmit DMA Configuration RAM
Next Priority Descriptor Pointer (16)
Next Priority Pending Descriptor Pointer (16)
Last Priority Pending Descriptor Pointer (16)
Fields shown within the thick box
are written by the Host; all other
fields are for usage by the DMA and
can only be read by the Host
dmatcram
140 of 203
DS3134
- FOR DMA USAGE ONLY / HOST CAN ONLY READ THIS FIELD dword 0; Bits 0 to 31 / Current Data Buffer Address. The current 32-bit address of the data buffer that
is being used. This address is used by the DMA to keep track of where data should be read from as it is
passed to the transmit FIFO.
- HOST MUST CONFIGURE dword 1; Bit 0 / Channel Enable (CHEN). This bit is controlled by both the Host and the transmit
DMA to enable and disable a HDLC channel. The DMA will automatically disable a channel when an
error condition occurs (see Section 8.2.1 for a discussion on error conditions). The DMA will
automatically enable a channel when it detects that the Channel Reset (CHRST) bit in the Pending Queue
descriptor is set to a one.
0 = HDLC Channel Disabled
1 = HDLC Channel Enabled
- HOST MUST CONFIGURE dword 1; Bit 1 / Done Queue Select (DQS). This bit determines whether the transmit DMA will write
to the Done Queue only after a complete HDLC packet (which may be only a single buffer) has been
transmitted (in which case the Descriptor Pointer in the Done Queue will correspond to the first descriptor
of the packet) or whether it should write to the Done Queue after each data buffer has been transmitted (in
which case the Descriptor Pointer in the Done Queue will correspond to a single data buffer). The setting
of this bit also affects the reporting of the Status field in the Transmit Done Queue. When DQS = 0, the
only non-errored status possible is a setting of 000. When DQS = 1, then the non-errored settings of 001,
010, and 011 are possible.
0 = write to the Done Queue only after a complete HDLC packet has been transmitted
1 = write to the Done Queue after each data buffer is transmitted
- FOR DMA USAGE ONLY / HOST CAN ONLY READ THIS FIELD dword 1; Bit 2/ Unused. This field is not used by the DMA and could be any value when read.
- FOR DMA USAGE ONLY / HOST CAN ONLY READ THIS FIELD dword 1; Bits 3 to 15 / Byte Count. The DMA uses these 13 bits to keep track of the number of bytes
stored in the data buffer. Maximum is 8191 bytes (0000h =0 bytes / 1FFFh = 8191 bytes).
- FOR DMA USAGE ONLY / HOST CAN ONLY READ THIS FIELD dword 1; Bit 16 / Chain Valid (CV). This is an internal copy of the CV field that resides in the current
Packet Descriptor that the DMA is operating on. See Section 8.2.2 for more details on the CV bit.
- FOR DMA USAGE ONLY / HOST CAN ONLY READ THIS FIELD dword 1; Bit 17 / End Of Frame (EOF). This is an internal copy of the EOF field that resides in the
current Packet Descriptor that the DMA is operating on. See Section 8.2.2 for more details on the EOF
bit.
141 of 203
DS3134
- FOR DMA USAGE ONLY / HOST CAN ONLY READ THIS FIELD dword 1; Bits 18 to 19 / Pending State (PENDST). This field is used by the transmit DMA to keep
track of queued descriptors as they arrive from the Pending Queue and for the DMA to know when it
should create a horizontal linked list of transmit descriptors and where it can find the next valid
descriptor. This field handles standard packets and the PRIST field handles priority packets.
State
Next Descriptor
Next Pending Descriptor
Pointer field
Pointer field
00
not valid
not valid
01
valid
not valid
10
not valid
valid
11
valid
valid
- FOR DMA USAGE ONLY / HOST CAN ONLY READ THIS FIELD dword 1; Bits 20 to 21 / Priority State (PRIST). This field is used by the transmit DMA to keep track
of queued priority descriptors as they arrive from the Pending Queue and for the DMA to know when it
should create a horizontal linked list of transmit priority descriptors and where it can find the next valid
priority descriptor. This field handles priority packets and the PENDST field handles standard packets.
State
Next Priority Descriptor
Next Priority Pending
Pointer field
Descriptor Pointer field
00
not valid
not valid
01
valid
not valid
10
not valid
valid
11
valid
valid
- FOR DMA USAGE ONLY / HOST CAN ONLY READ THIS FIELD dword 1; Bit 22/ Processing Priority Packet (PPP). This bit will be set to a one when the DMA is
currently processing a priority packet.
- FOR DMA USAGE ONLY / HOST CAN ONLY READ THIS FIELD dword 1; Bits 23 to 31/ Unused. This field is not used by the DMA and could be any value when read
- FOR DMA USAGE ONLY / HOST CAN ONLY READ THIS FIELD dword 2; Bits 0 to 15 / Next Descriptor Pointer. This 16-bit value is the offset from the Transmit
Descriptor Base Address of the next Transmit Packet Descriptor for the packet that is currently being
transmitted. Only valid if EOF = 0 or if EOF = 1 and CV = 1.
- FOR DMA USAGE ONLY / HOST CAN ONLY READ THIS FIELD dword 2; Bits 16 to 31 / Start Descriptor Pointer. This 16-bit value is the offset from the Transmit
Descriptor Base Address of the first Transmit Packet Descriptor for the packet that is currently being
transmitted. If DQS = 0, then this pointer is written back to the Done Queue when the packet has
completed transmission. This field is used by the DMA for processing standard as well as priority
packets.
- FOR DMA USAGE ONLY / HOST CAN ONLY READ THIS FIELD dword 3; Bits 0 to 15 / Next Pending Descriptor Pointer. This 16-bit value is the offset from the
Transmit Descriptor Base Address of the first Transmit Packet Descriptor for the packet that is queued up
next for transmission.
142 of 203
DS3134
- FOR DMA USAGE ONLY / HOST CAN ONLY READ THIS FIELD dword 3; Bits 16 to 31 / Last Pending Descriptor Pointer. This 16-bit value is the offset from the
Transmit Descriptor Base Address of the first Transmit Packet Descriptor for the packet that is queued up
last for transmission.
- FOR DMA USAGE ONLY / HOST CAN ONLY READ THIS FIELD dword 4; Bits 0 to 15 / Next Priority Descriptor Pointer. This 16-bit value is the offset from the
Transmit Descriptor Base Address of the next Transmit Priority Packet Descriptor for the priority packet
that is currently being transmitted. Only valid if EOF = 0 or if EOF = 1 and CV = 1.
- FOR DMA USAGE ONLY / HOST CAN ONLY READ THIS FIELD dword 4; Bits 16 to 31/ Unused. This field is not used by the DMA and could be any value when read.
- FOR DMA USAGE ONLY / HOST CAN ONLY READ THIS FIELD dword 5; Bits 0 to 15 / Last Priority Pending Descriptor Pointer. This 16-bit value is the offset from
the Transmit Descriptor Base Address of the first Transmit Priority Packet Descriptor for the priority
packet that is queued up last for transmission.
- FOR DMA USAGE ONLY / HOST CAN ONLY READ THIS FIELD dword 5; Bits 16 to 31 / Next Priority Pending Descriptor Pointer. This 16-bit value is the offset from
the Transmit Descriptor Base Address of the first Transmit Priority Packet Descriptor for the packet
priority that is queued up next for transmission.
Register Name:
TDMACIS
Register Description: Transmit DMA Configuration Indirect Select
Register Address:
0870h
7
6
5
4
3
2
1
0
HCID7
HCID6
HCID5
HCID4
HCID3
HCID2
HCID1
HCID0
15
14
13
12
11
10
9
8
IAB
IARW
n/a
n/a
TDCW3 TDCW2 TDCW1 TDCW0
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
Bits 0 to 7 / HDLC Channel ID (HCID0 to HCID7).
00000000 (00h) = HDLC Channel Number 1
11111111 (FFh) = HDLC Channel Number 256
143 of 203
DS3134
Bits 8 to 11 / Transmit DMA Configuration RAM Word Select Bits 0 to 3 (TDCW0 to TDCW3).
0000 = lower word of dword 0
0001 = upper word of dword 0
0010 = lower word of dword 1 (only word that the Host can write to)
0011 = upper word of dword 1
0100 = lower word of dword 2
0101 = upper word of dword 2
0110 = lower word of dword 3
0111 = upper word of dword 3
1000 = lower word of dword 4
1001 = upper word of dword 4
1010 = lower word of dword 5
1011 = upper word of dword 5
Bit 14 / Indirect Access Read/Write (IARW). When the host wishes to read data from the internal
Transmit DMA Configuration RAM, this bit should be written to a one by the host. This causes the
device to begin obtaining the data from the channel location indicated by the HCID bits. During the read
access, the IAB bit will be set to one. Once the data is ready to be read from the TDMAC register, the
IAB bit will be set to zero. When the host wishes to write data to the internal Transmit DMA
Configuration RAM, this bit should be written to a zero by the host. This causes the device to take the
data that is current present in the TDMAC register and write it to the channel location indicated by the
HCID bits. When the device has completed the write, the IAB bit will be set to zero.
Bit 15 / Indirect Access Busy (IAB). When an indirect read or write access is in progress, this read only
bit will be set to a one. During a read operation, this bit will be set to a one until the data is ready to be
read. It will be set to zero when the data is ready to be read. During a write operation, this bit will be set
to a one while the write is taking place. It will be set to zero once the write operation has completed.
Register Name:
TDMAC
Register Description: Transmit DMA Configuration
Register Address:
0874h
7
6
5
4
3
2
1
D7
D6
D5
D4
D3
D2
D1
15
14
13
12
11
10
9
D15
D14
D13
D12
D11
D10
D9
Note: Bits that are underlined are read only, all other bits are read-write.
0
D0
8
D8
Bits 0 to 15 / Transmit DMA Configuration RAM Data (D0 to D15). Data that is written to or read
from the Transmit DMA Configuration RAM.
144 of 203
DS3134
SECTION 9: PCI BUS
9.1 PCI GENERAL DESCRIPTION OF OPERATION
The PCI Block interfaces the DMA Block to an external high-speed bus. The PCI Block complies with
Revision 2.1 (June 1, 1995) of the PCI Local Bus Specification. HDLC packet data will always pass to
and from Chateau via the PCI bus. The user has the option to configure and monitor the internal device
registers either via the PCI bus (Local Bus Bridge mode) or via the Local Bus (Local Bus Configuration
mode). When the Local Bus Bridge mode is used, the Host on the PCI bus can also bridge to the Local
Bus and will set/monitor the PCI Configuration registers. When the Local Bus Configuration mode is
used, the CPU on the Local Bus will set/monitor the PCI Configuration registers.
The PCI Configuration registers (see Figure 9.1A) are described in detail in Section 9.2. The following is
a set of notes that apply to the PCI Configuration registers:
1. All unused locations (the shaded areas of Figure 9.1A) will return zeros when read
2. Read only locations can be written with either a one or zero with no affect
3. All bits are read/write unless otherwise noted.
PCI Configuration Memory Map Figure 9.1A
0x000
Device ID
Vendor ID
0x004
Status
Command
Header Type
0x00C
0x010
0x03C
Revision ID
Class Code
0x008
Latency Timer
Base Address for Device Configuration
Min. Grant
Max. Latency
Cache Line Size
0x000
Interrupt Pin
Interrupt Line
0x100
Device ID
Vendor ID
0x104
Status
Command
0x108
0x10C
0x110
0x13C
Class Code
Revision ID
Header Type
Base Address for Local Bus
0x00000
Interrupt Pin
Interrupt Line
145 of 203
pci_reg
DS3134
PCI Read Cycle
A read cycle on the PCI bus is shown in Figure 9.1B. During clock cycle #1, the initiator asserts the
PFRAME* signal and drives the address onto the PAD signal lines and the bus command (which would
be a read) onto the PCBE* signal lines. The target reads the address and bus command and if the address
matches it's own, then it will assert the PDEVSEL* signal and begin the bus transaction. During clock
cycle #2, the initiator stops driving the address onto the PAD signal lines and switches the PCBE* signal
lines to now indicate byte enables. It also asserts the PIRDY* signal and begins monitoring the
PDEVSEL* and PTRDY* signals. During clock cycle #4, the target asserts PTRDY* indicating to the
initiator that valid data is available to be read on the PAD signal lines by the initiator. During clock cycle
#5, the target is not ready to provide data #2 because PTRDY* is deasserted. During clock cycle #6, the
target again asserts PTRDY* informing the initiator to read data #2. During clock cycle #7, the initiator
deasserts PIRDY* indicating to the target that it is not ready to accept data. During clock cycle #8, the
initiator asserts PIRDY* and acquires data #3. In addition, during clock cycle #8, the initiator deasserts
PFRAME* indicating to the target that the bus transaction is complete and no more data needs to be read.
During clock cycle #9, the target deasserts PTRDY* and PDEVSEL* and the initiator deasserts PIRDY*.
The PXAS*, PXDS*, and PXBLAST* signals are not part of a standard PCI bus. These PCI extension
signals that are unique to the device. They are useful in adapting the PCI bus to a proprietary bus scheme.
They are only asserted when the device is a bus master.
PCI Bus Read Figure 9.1B
PCLK
1
2
3
4
5
6
7
8
9
10
PFRAME*
PAD
PCBE*
Address
CMD
data #1
Byte Enable #1
data #2
BE #2
data #3
BE #3
PIRDY*
PTRDY*
PDEVSEL*
PXAS*
PXDS*
PXBLAST*
pci_read
146 of 203
DS3134
PCI Write Cycle
A write cycle on the PCI bus is shown in Figure 9.1C. During clock cycle #1, the initiator asserts the
PFRAME* signal and drives the address onto the PAD signal lines and the bus command (which would
be a write) onto the PCBE* signal lines. The target reads the address and bus command and if the address
matches it's own, then it will assert the PDEVSEL* signal and begin the bus transaction. During clock
cycle #2, the initiator stops driving the address onto the PAD signal lines and begins driving data #1. It
also switches the PCBE* signal lines to now indicate the byte enable for data #1. The initiator asserts the
PIRDY* signal and begins monitoring the PDEVSEL* and PTRDY* signals. During clock cycle #3, the
initiator detects that PDEVSEL* and PTRDY* are asserted which indicates that the target has accepted
data #1 and the initiator begins driving the data and byte enable for data #2. During clock cycle #4, since
PDEVSEL* and PTRDY* are asserted, data #2 is written by the initiator to the target. During clock cycle
#5, both PIRDY* and PTRDY* are deasserted indicating that neither the initiator nor the target are ready
for data #3 to be passed. During clock cycle #6, the initiator is now ready so it asserts PIRDY* and
deasserts PFRAME* which indicates that data #3 will be the last one passed. During clock cycle #8, the
target asserts PTRDY* which indicates to the initiator that data #3 is ready to be accepted by the target.
During clock cycle #9, the initiator deasserts PIRDY* and stops driving the PAD and PCBE* signal lines.
The target deasserts PDEVSEL* and PTRDY*.
The PXAS*, PXDS*, and PXBLAST* signals are not part of a standard PCI bus. These PCI extension
signals that are unique to the device. They are useful in adapting the PCI bus to a proprietary bus scheme.
They are only asserted when the device is a bus master.
PCI Bus Write Figure 9.1C
PCLK
1
2
3
4
5
6
7
8
9
10
PFRAME*
PAD
PCBE*
Address
data #1
CMD
BE #1
data #2
BE #2
data #3
BE #3
PIRDY*
PTRDY*
PDEVSEL*
PXAS*
PXDS*
PXBLAST*
pci_writ
147 of 203
DS3134
PCI Bus Arbitration
The PCI bus can be arbitrated as shown in Figure 9.1D. The initiator will request bus access by asserting
PREQ*. A central arbiter will grant the access some time later by asserting PGNT*. Once the bus has
been granted, the initiator will wait until both PIRDY* and PFRAME* are deasserted (i.e. an idle cycle)
before acquiring the bus and beginning the transaction. As shown in Figure 9.1C, the bus was still being
used when it was granted and the device had to wait until clock cycle #6 before it acquired the bus and
begin the transaction. The arbiter can deassert PGNT* at any time and the initiator must relinquish the
bus after the current transfer is complete (which can be limited by the latency timer).
PCI Bus Arbitration Signaling Protocol Figure 9.1D
PCLK
1
2
3
4
5
6
7
8
9
10
PREQ*
PGNT*
PFRAME*
Wait for PGNT* Asserted
and then PFRAME* &
PIRDY* Deasserted
Bus is
Relinquished
Bus is Acquired
pci_arb
PCI Initiator Abort
If a target fails to respond to an initiator by asserting PDEVSEL* and PTRDY* within 5 clock cycles,
then the initiator will abort the transaction by deasserting PFRAME* and then one clock later deasserting
PIDRY* (see Figure 9.1E). If such a scenario occurs, it will be reported via the Master Abort status bit in
the PCI Command/Status configuration register (see Section 9.2).
PCI Initiator Abort Figure 9.1E
PCLK
1
2
3
4
5
6
7
8
9
10
PFRAME*
PIRDY*
PTRDY*
PDEVSEL*
pci_iabt
148 of 203
DS3134
PCI Target Retry
Targets can terminate the requested bus transaction before any data is transferred because the target is
busy and temporarily unable to process the transaction. Such a termination is called a target retry and no
data is transferred. A target retry is signaled to the initiator by the assertion of PSTOP* and not asserting
PTRDY* on the initial data phase (see Figure 9.1F). When Chateau is a target, it will only issue a target
retry when the Host is accessing the Local Bus. This will occur when the Local Bus is being operated in
the arbitration mode and at the instant the Host requests access to the Local Bus, it is busy. See Section
10.1 for more details on the operation of the Local Bus.
PCI Target Retry Figure 9.1F
PCLK
1
2
3
4
5
6
7
8
9
10
PFRAME*
PIRDY*
PTRDY*
PSTOP*
PDEVSEL*
pci_tret
PCI Target Disconnect
A target can terminate a transaction prematurely by asserting PSTOP* (see Figure 9.1G). Depending on
the current state of the ready signals when PSTOP* is asserted, data may or may not be transferred. The
target will always deassert PSTOP* when it detects that the initiator has deasserted PFRAME*. When
Chateau is a target, it will disconnect with data after the first data phase is complete if the master attempts
a burst transaction. This is because the device does not support burst transactions when it is a target.
When it is an initiator and experiences a disconnect from the target, it will attempt another bus transaction
(if it still has the bus granted) after waiting either one (disconnect without data) or two clock cycles
(disconnect with data).
149 of 203
DS3134
PCI Target Disconnect Figure 9.1G
PCLK
1
2
3
4
5
6
7
8
9
10
PFRAME*
PSTOP*
PDEVSEL*
pci_tdis
PCI Target Abort
Targets can also abort the current transaction which means that it does not wish for the initiator to attempt
the request again. No data is transferred in a target abort scenario. A target abort is signaled to the
initiator by the simultaneous assertion of PSTOP* and deassertion of PDEVSEL* (see Figure 9.1H).
When Chateau is a target, it will only issue a target abort when the Host is accessing the Local Bus. This
will occur when the Host attempts a bus transaction with a combination of bytes enables (PCBE*) that is
not supported by the Local Bus. If such a scenario occurs, it will be reported via the Target Abort
Initiated status bit in the PCI Command/Status configuration register (see Section 9.2). See Section 10.1
for details on Local Bus operation. When Chateau is a bus master, if it detects a target abort, then it will
be reported via the Target Abort Detected by Master status bit in the PCI Command/Status configuration
register (see Section 9.2).
PCI Target Abort Figure 9.1H
PCLK
1
2
3
4
5
6
7
8
9
10
PFRAME*
PTRDY*
PSTOP*
PDEVSEL*
pci_tabt
PCI Fast Back-to-Back
Fast back-to-back transactions are two consecutive bus transactions without the usually required idle
cycle (PFRAME* and PIRDY* deasserted) between them. This can only occur when there is a guarantee
that there will not be any contention on the signal lines. The PCI specification allows two types of fast
back-to-back transactions, those that access the same agent (Type 1) and those that do not (Type 2).
Figure 9.1J shows an example of a fast back-to-back transaction where no idle cycle exists. As a bus
master, Chateau is no capable of performing a Type 2 access. As a target, it can accept both types of fast
back-to-back transactions.
150 of 203
DS3134
PCI Fast Back-to-Back Figure 9.1J
PCLK
1
2
3
4
5
6
7
8
9
10
PFRAME*
PAD
PCBE*
Address
data #1
data #2
Address
data #1
CMD
BE #1
BE #2
CMD
BE #1
data #2
BE #2
PIRDY*
PTRDY*
PDEVSEL*
pci_fbb
9.2 PCI CONFIGURATION REGISTER DESCRIPTION
Register Name:
PVID0
Register Description: PCI Vendor ID / Device ID Register 0
Register Address:
0x000
lsb
Vendor ID (Read Only / set to EAh)
Vendor ID (Read Only / set to 13h)
Device ID (Read Only / set to 34h)
msb
DeviceID (Read Only / set to 31h)
Bits 0 to 15 / Vendor ID. These read only bits identify Dallas Semiconductor as the manufacturer of the
device. The Vendor ID was assigned by the PCI Special Interest Group and is fixed at 13EAh.
Bits 16 to 31 / Device ID. These read only bits identify the DS3134 as the device being used. The
Device ID was assigned by Dallas Semiconductor and is fixed at 3134h.
151 of 203
DS3134
Register Name:
PCMD0
Register Description: PCI Command / Status Register 0
Register Address:
0x004
lsb
STEPC
PARC
VGA
MWEN
SCC
Reserved (Read Only / set to all zeros)
MASC
MSC
IOC
FBBEN
PSEC
FBBCT
UDF
66 MHz
Reserved (Read Only / set to all zeros)
msb
PPE
PSE
MABT TABTM
TABT
DTS1
DTS0
PARR
Note : Read only bits in the PCMD0 register are indicated above by being underlined. All other bits are
read-write.
The lower word (bits 0 to 15) of the PCMD0 register is the Command portion and is used for control of
the PCI bus. When all bits in the lower word are set to zero, then the device is logically disconnected
from the bus for all accesses except for accesses to the configuration registers. The upper word (bits 16 to
31) is the Status portion and it is used for status information. Reads to the Status portion behave normally
but writes are unique in that bits can be reset (i.e. forced to zero) but not set (i.e. forced to one). A bit in
the Status portion will be reset when a one is written to that bit position. Bit positions that have a zero
written to them will not be reset.
COMMAND BITS
Bit 0 / I/O Space Control (IOC). This read only bit is forced to zero by the device to indicate that it
does not respond to I/O Space accesses.
Bit 1 / Memory Space Control (MSC). This read/write bit controls whether or not the device will
respond to accesses by the PCI bus to the memory space (which is the internal device configuration
registers). When this bit is set to zero, the device will ignore accesses attempted to the internal
configuration registers and when set to one; the device will allow accesses to the internal configuration
registers. This bit should be set to zero when the Local Bus is operated in the Configuration Mode. This
bit is force to zero when a hardware reset is initiated via the PRST* pin.
0 = ignore accesses to the internal device configuration registers
1 = allow accesses to the internal device configuration registers
Bit 2 / Master Control (MASC). This read/write bit controls whether or not the device can act as a
master on the PCI bus. When this bit is set to zero, the device cannot act as a master and when it is set to
one, the device can act as a bus master. This bit is forced to zero when a hardware reset is initiated via
the PRST* pin.
0 = deny the device from operating as a bus master
1 = allow the device to operate as a bus master
Bit 3 / Special Cycle Control (SCC). This read only bit is forced to zero by the device to indicate that it
cannot decode Special Cycle operations.
Bit 4 / Memory Write & Invalidate Command Enable (MWEN). This read only bit is forced to zero
by the device to indicate that it cannot generate the Memory Write and Invalidate command.
152 of 203
DS3134
Bit 5 / VGA Control (VGA). This read only bit is forced to zero by the device to indicate that it is not a
VGA compatible device.
Bit 6 / Parity Error Response Control (PARC). This read/write bit controls whether or not the device
should ignore parity errors. When this bit is set to zero, the device will ignore any parity errors that it
detects and continue to operate normally. When this bit is set to one, the device must act on parity errors.
This bit is forced to zero when a hardware reset is initiated via the PRST* pin.
0 = ignore parity errors
1 = act on parity errors
Bit 7 / Address Stepping Control (STEPC). This read only bit is forced to zero by the device to indicate
that it is not capable of address/data stepping.
Bit 8 / PCI System Error Control (PSEC). This read/write bit controls whether or not the device
should enable the PSERR* output pin. When this bit is set to zero, the device will disable the PSERR*
pin and when this bit is set to one, the device will enable the PSERR* pin. This bit is forced to zero when
a hardware reset is initiated via the PRST* pin.
0 = disable the PSERR* pin
1 = enable the PSERR* pin
Bit 9 / Fast Back-to-Back Master Enable (FBBEN). This read only bit is forced to zero by the device
to indicate that it is not capable of generating fast back-to-back transactions to different agents.
Bits 10 to 15 / Reserved. These read only bits are forced to zero by the device.
STATUS BITS
The upper word in the PCMD0 register is the Status portion, which report events as they occur. As
mentioned earlier, reads of the Status portion occur normally but writes are unique in that bits can only be
reset (i.e. forced to zero). This occurs when a one is written to a bit position. Writes with a zero to a bit
position have no affect. This allows individual bits to be reset.
Bits 16 to 20 / Reserved. These read only bits are forced to zero by the device.
Bit 21 / 66 MHz Capable (66 MHz). This read only bit is forced to zero by the device to indicate that it
is not capable of running at 66 MHz.
Bit 22 / User Definable Features Capable (UDF). This read only bit is forced to zero by the device to
indicate that it does not support User Definable Features.
Bit 23 / Fast Back-to-Back Capable Target (FBBCT). This read only bit is forced to one by the device
to indicate that it is capable of accepting fast back-to-back transactions when the transactions are not from
the same agent.
Bit 24 / PCI Parity Error Reported (PARR). This read/write bit will be set to a one when the device is
a bus master and detects or asserts the PPERR* signal when the PARC command bit is enabled. This bit
can be reset (set to zero) by the Host by writing a one to this bit.
0 = no parity errors have been detected
1 = parity errors detected
153 of 203
DS3134
Bit 25 & 26 / Device Timing Select Bits 0 & 1 (DTS0 & DTS1). These two read only bits are forced to
01b by the device to indicate that it is capable of the medium timing requirements for the PDEVSEL*
signal.
Bit 27 / Target Abort Initiated (TABT). This read only bit is forced to zero by the device since it will
not terminate a bus transaction with a target abort when the device is a target.
Bit 28 / Target Abort Detected by Master (TABTM). This read/write bit will be set to a one when the
device is a bus master and it detects that a bus transaction has been aborted by the target with a target
abort. This bit can be reset (set to zero) by the Host by writing a one to this bit.
Bit 29 / Master Abort (MABT). This read/write bit will be set to a one when the device is a bus master
and the bus transaction is terminated with a master abort (except for Special Cycle). This bit can be reset
(set to zero) by the Host by writing a one to this bit.
Bit 30 / PCI System Error Reported (PSE). This read/write bit will be set to a one when the device
asserts the PSERR* signal (even if it is disabled via the PSEC Command bit). This bit can be reset (set to
zero) by the Host by writing a one to this bit.
Bit 31 / PCI Parity Error Reported (PPE). This read/write bit will be set to a one when the device
detects a parity error (even if parity is disabled via the PARC Command bit). This bit can be reset (set to
zero) by the Host by writing a one to this bit.
Register Name:
PRCC0
Register Description: PCI Revision ID / Class Code Register 0
Register Address:
0x008h
lsb
Revision ID (Read Only / set to 00h)
Class Code (Read Only / set to 00h)
Class Code (Read Only / set to 80h)
msb
Class Code (Read Only / set to 02h)
Bits 0 to 7 / Revision ID. These read only bits identify the specific device revision and are selected by
Dallas Semiconductor.
Bits 8 to 15 / Class Code Interface. These read only bits identify the sub-class interface value for the
device and are fixed at 00h. See Appendix D of PCI Local Bus Specification Revision 2.1 for details.
Bits 16 to 23 / Class Code Sub-Class. These read only bits identify the sub-class value for the device
and are fixed at 80h, which indicate "Other Network Controller". See Appendix D of PCI Local Bus
Specification Revision 2.1 for details.
154 of 203
DS3134
Bits 24 to 31 / Class Code Base Class. These read only bits identify the base class value for the device
and are fixed at 02h, which indicate "Network Controllers". See Appendix D of PCI Local Bus
Specification Revision 2.1 for details.
Register Name:
PLTH0
Register Description: PCI Latency Timer / Header Type Register 0
Register Address:
0x00Ch
lsb
Cache Line Size
Latency Timer
Header Type (Read Only / set to 80h)
msb
BIST (Read Only / set to 00h)
Bits 0 to 7 / Cache Line Size. These read/write bits indicates the cache line size in terms of dwords. If
the burst size of a data read transaction exceeds this value, then the PCI Block will use the memory read
multiple command. Valid settings are 04h (4 dwords), 08h, 10h, 20h, and 40h (64 dwords). Other
settings are interpreted as 00h. These bits are forced to zero when a hardware reset is initiated via the
PRST* pin.
Bits 8 to 15 / Latency Timer. These read/write bits indicate the value of the Latency Timer (in terms of
the number of PCI clocks) for use when the device is a bus master. These bits are forced to zero when a
hardware reset is initiated via the PRST* pin.
Bits 16 to 23 / Header Type. These read only bits are forced to 80h, which indicate a multifunction
device.
Bits 24 to 31 / Built-In Self-Test (BIST). These read only bits are forced to zero.
Register Name:
PDCM
Register Description: PCI Device Configuration Memory Base Address Register
Register Address:
0x010h
Base Address (Read Only / set to 0h)
Base Address
PF
TYPE1
TYPE0
lsb
MSI
Base Address (Read Only / set to 0h)
Base Address
msb
Base Address
155 of 203
DS3134
Read only bits in the PDCM register are indicated above by being underlined. All other bits are readwrite.
Bit 0 / Memory Space Indicator (MSI). This read only bit is forced to zero to indicate that the internal
device configuration registers are mapped to memory space.
Bits 1 & 2 / Type 0 & Type 1. These read only bits are forced to 00b to indicate that the internal device
configuration registers can be mapped anywhere in the 32 bit address space.
Bit 3 / Prefetchable (PF). This read only bit is forced to zero to indicate that prefetching is not supported
by the device for the internal device configuration registers.
Bits 4 to 11 / Base Address. These read only bits are forced to zero to indicate that the internal device
configuration registers require 4k bytes of memory space.
Bits 12 to 31 / Base Address. These read/write bits define the location of the 4k memory space that is
mapped to the internal configuration registers. These bits correspond to the most significant bits of the
PCI address space.
Register Name:
PINTL0
Register Description: PCI Interrupt Line & Pin / Minimum Grant / Maximum Latency Register 0
Register Address:
0x03Ch
lsb
Interrupt Line
Interrupt Pin (Read Only / set to 01h)
Minimum Grant (Read Only / set to 05h)
msb
Maximum Latency (Read Only / set to 0Fh)
Bits 0 to 7 / Interrupt Line. These read/write bits indicate and store interrupt line routing information.
The device does not use this information; it is only posted here for use by the Host.
Bits 8 to 15 / Interrupt Pin. These read only bits are forced to 01h to indicate that the uses PINTA* as
an interrupt.
Bits 16 to 23 / Minimum Grant. These read only bits are used to indicate to the Host, how long of a
burst period the device needs assuming a clock rate of 33 MHz. The value placed in these bits specifies a
period of time in 0.25 us increments. These bits are forced to 05h.
Bits 24 to 31 / Maximum Latency. These read only bits are used to indicate to the Host, how often the
device needs to gain access to the PCI bus. The value placed in these bits specifies a period of time in
0.25 us increments. These bits are forced to 0Fh.
156 of 203
DS3134
Register Name:
PVID1
Register Description: PCI Vendor ID / Device ID Register 1
Register Address:
0x100
lsb
Vendor ID (Read Only / set to EAh)
Vendor ID (Read Only / set to 13h)
Device ID (Read Only / set to 34h)
msb
DeviceID (Read Only / set to 31h)
Bits 0 to 15 / Vendor ID. These read only bits identify Dallas Semiconductor as the manufacturer of the
device. The Vendor ID was assigned by the PCI Special Interest Group and is fixed at 13EAh.
Bits 16 to 31 / Device ID. These read only bits identify the DS3134 as the device being used. The
Device ID was assigned by Dallas Semiconductor and is fixed at 3134h.
Register Name:
PCMD1
Register Description: PCI Command / Status Register 1
Register Address:
0x104
lsb
STEPC
PARC
VGA
MWEN
SCC
MASC
Reserved (Read Only / set to all zeros)
FBBCT
msb
PPE
UDF
66 MHz
PSE
MABT
MSC
IOC
FBBEN
PSEC
Reserved (Read Only / set to all zeros)
TABTM
TABT
DTS1
DTS0
PARR
Read only bits in the PCMD1 register are indicated above by being underlined. All other bits are readwrite.
The lower word (bits 0 to 15) of the PCMD1 register is the Command portion and is used for control of
the PCI bus. When all bits in the lower word are set to zero, then the device is logically disconnected
from the bus for all accesses except for accesses to the configuration registers. The upper word (bits 16 to
31) is the Status portion and it is used for status information. Reads to the Status portion behave normally
but writes are unique in that bits can be reset (i.e. forced to zero) but not set (i.e. forced to one). A bit in
the Status portion will be reset when a one is written to that bit position. Bit positions that have a zero
written to them will not be reset.
157 of 203
DS3134
COMMAND BITS
Bit 0 / I/O Space Control (IOC). This read only bit is forced to zero by the device to indicate that it
does not respond to I/O Space accesses.
Bit 1 / Memory Space Control (MSC). This read/write bit controls whether or not the device will
respond to accesses by the PCI bus to the memory space (which is the Local Bus). When this bit is set to
zero, the device will ignore accesses attempted to the Local Bus and when set to one; the device will
allow accesses to the Local Bus. This bit should be set to zero when the Local Bus is operated in the
Configuration Mode. This bit is force to zero when a hardware reset is initiated via the PRST* pin.
0 = ignore accesses to the Local Bus
1 = allow accesses to the Bus
Bit 2 / Master Control (MASC). This read only bit is forced to zero by the device since it cannot act as
a bus master.
Bit 3 / Special Cycle Control (SCC). This read only bit is forced to zero by the device to indicate that it
cannot decode Special Cycle operations.
Bit 4 / Memory Write & Invalidate Command Enable (MWEN). This read only bit is forced to zero
by the device to indicate that it cannot generate the Memory Write and Invalidate command.
Bit 5 / VGA Control (VGA). This read only bit is forced to zero by the device to indicate that it is not a
VGA compatible device.
Bit 6 / Parity Error Response Control (PARC). This read/write bit controls whether or not the device
should ignore parity errors. When this bit is set to zero, the device will ignore any parity errors that it
detects and continue to operate normally. When this bit is set to one, the device must act on parity errors.
This bit is forced to zero when a hardware reset is initiated via the PRST* pin.
0 = ignore parity errors
1 = act on parity errors
Bit 7 / Address Stepping Control (STEPC). This read only bit is forced to zero by the device to indicate
that it is not capable of address/data stepping.
Bit 8 / PCI System Error Control (PSEC). This read/write bit controls whether or not the device
should enable the PSERR* output pin. When this bit is set to zero, the device will disable the PSERR*
pin and when this bit is set to one, the device will enable the PSERR* pin. This bit is forced to zero when
a hardware reset is initiated via the PRST* pin.
0 = disable the PSERR* pin
1 = enable the PSERR* pin
Bit 9 / Fast Back-to-Back Master Enable (FBBEN). This read only bit is forced to zero by the device
to indicate that it is not capable of generating fast back-to-back transactions to different agents.
Bits 10 to 15 / Reserved. These read only bits are forced to zero by the device.
158 of 203
DS3134
STATUS BITS
The upper word in the PCMD1 register is the Status portion, which report events as they occur. As
mentioned earlier, reads of the Status portion occur normally but writes are unique in that bits can only be
reset (i.e. forced to zero). This occurs when a one is written to a bit position. Writes with a zero to a bit
position have no affect. This allows individual bits to be reset.
Bits 16 to 20 / Reserved. These read only bits are forced to zero by the device.
Bit 21 / 66 MHz Capable (66 MHz). This read only bit is forced to zero by the device to indicate that it
is not capable of running at 66 MHz.
Bit 22 / User Definable Features Capable (UDF). This read only bit is forced to zero by the device to
indicate that it does not support User Definable Features.
Bit 23 / Fast Back-to-Back Capable Target (FBBCT). This read only bit is forced to one by the device
to indicate that it is capable of accepting fast back-to-back transactions when the transactions are not from
the same agent.
Bit 24 / PCI Parity Error Reported (PARR). This read only bit is forced to a zero by the device since
the device cannot act as a bus master.
Bit 25 & 26 / Device Timing Select Bits 0 & 1 (DTS0 & DTS1). These two read only bits are forced to
01b by the device to indicate that it is capable of the medium timing requirements for the PDEVSEL*
signal.
Bit 27 / Target Abort Initiated (TABT). This read/write bit will be set to a one when the device
terminates a bus transaction with a target abort. This will only occur when the Local Bus is being
operated in the bus arbitration mode and the Local Bus does not have bus control when the Host requests
access. This bit can be reset (set to zero) by the Host by writing a one to this bit.
Bit 28 / Target Abort Detected by Master (TABTM). This read only bit is forced to a zero by the
device since the device cannot act as a bus master.
Bit 29 / Master Abort (MABT). This read only bit is forced to a zero by the device since the device
cannot act as a bus master.
Bit 30 / PCI System Error Reported (PSE). This read/write bit will be set to a one when the device
asserts the PSERR* signal (even if it is disabled via the PSEC Command bit). This bit can be reset (set to
zero) by the Host by writing a one to this bit.
Bit 31 / PCI Parity Error Reported (PPE). This read/write bit will be set to a one when the device
detects a parity error (even if parity is disabled via the PARC Command bit). This bit can be reset (set to
zero) by the Host by writing a one to this bit.
159 of 203
DS3134
Register Name:
PRCC1
Register Description: PCI Revision ID / Class Code Register 1
Register Address:
0x108h
lsb
Revision ID (Read Only / set to 00h)
Class Code (Read Only / set to 00h)
Class Code (Read Only / set to 80h)
msb
Class Code (Read Only / set to 06h)
Bits 0 to 7 / Revision ID. These read only bits identify the specific device revision and are selected by
Dallas Semiconductor.
Bits 8 to 15 / Class Code Interface. These read only bits identify the sub-class interface value for the
device and are fixed at 00h. See Appendix D of PCI Local Bus Specification Revision 2.1 for details.
Bits 16 to 23 / Class Code Sub-Class. These read only bits identify the sub-class value for the device
and are fixed at 80h, which indicate "Other Bridge Device". See Appendix D of PCI Local Bus
Specification Revision 2.1 for details.
Bits 24 to 31 / Class Code Base Class. These read only bits identify the base class value for the device
and are fixed at 06h, which indicate "Bridge Devices". See Appendix D of PCI Local Bus Specification
Revision 2.1 for details.
Register Name:
PLTH1
Register Description: PCI Latency Timer / Header Type Register 1
Register Address:
0x10Ch
lsb
Cache Line Size (Read Only / set to 00h)
Latency Timer (Read Only / set to 00h)
Header Type (Read Only / set to 80h)
msb
BIST (Read Only / set to 00h)
Bits 0 to 7 / Cache Line Size. These read only bits are forced to zero.
Bits 8 to 15 / Latency Timer. These read only bits are forced to a zero by the device since the device
cannot act as a bus master.
Bits 16 to 23 / Header Type. These read only bits are forced to 80h, which indicate a multifunction
device.
Bits 24 to 31 / Built-In Self Test (BIST). These read only bits are forced to zero.
160 of 203
DS3134
Register Name:
PLBM
Register Description: PCI Local Bus Memory Base Address Register
Register Address:
0x110h
lsb
Base Address (Read Only / set to 0h)
Base Address
PF
TYPE1
TYPE0
MSI
Base Address (Read Only / set to 0h)
Base Address
msb
Base Address
Read only bits in the PLBM register are indicated above by being underlined. All other bits are readwrite.
Bit 0 / Memory Space Indicator (MSI). This read only bit is forced to zero to indicate that the Local
Bus is mapped to memory space.
Bits 1 & 2 / Type 0 & Type 1. These read only bits are forced to 00b to indicate that the Local Bus can
be mapped anywhere in the 32 bit address space.
Bit 3 / Prefetchable (PF). This read only bit is forced to zero to indicate that prefetching is not supported
by the device for the Local Bus.
Bits 4 to 19 / Base Address. These read only bits are forced to zero to indicate that the Local Bus
requires 1M byte of memory space.
Bits 20 to 31 / Base Address. These read/write bits define the location of the 1M byte memory space that
is mapped to the Local Bus. These bits correspond to the most significant bits of the PCI address space.
161 of 203
DS3134
Register Name:
PINTL1
Register Description: PCI Interrupt Line & Pin / Minimum Grant / Maximum Latency Register 1
Register Address:
0x13Ch
lsb
Interrupt Line
Interrupt Pin (Read Only / set to 01h)
Maximum Grant (Read Only / set to 00h)
msb
Maximum Latency (Read Only / set to 00h)
Bits 0 to 7 / Interrupt Line. These read/write bits indicate and store interrupt line routing information.
The device does not use this information; it is only posted here for use by the Host.
Bits 8 to 15 / Interrupt Pin. These read only bits are forced to 01h to indicate that the uses PINTA* as
an interrupt.
Bits 16 to 23 / Minimum Grant. These read only bits are forced to zero.
Bits 24 to 31 / Maximum Latency. These read only bits are forced to zero.
162 of 203
DS3134
SECTION 10: LOCAL BUS
10.1 LOCAL BUS GENERAL DESCRIPTION
The Local Bus can operate in two modes, as a PCI Bridge (master mode) and as a Configuration Bus
(slave mode). This selection is made in hardware by tying the LMS pin high or low. Figures 10.1A
through 10.1C describe the two modes. Figure 10.1A shows an example of the Local Bus being operated
in the PCI Bridge Mode. In this example, the Host can access the control ports on the T1/E1 devices via
the Local Bus.
Figure 10.1B also shows an example of the PCI Bridge Mode but in this example, the Local Bus
Arbitration is enabled which allows a Local CPU to control when the Host can have access to the Local
Bus. To access the Local Bus, the Host must first request the bus and then wait until it is granted.
Figure 10.1C displays an example of the Configuration Mode. In this mode, the CPU on the Local Bus
will configure and monitor the DS3134. In this mode, the Host on the PCI/Custom Bus cannot access the
DS3134 and the PCI/Custom Bus is only used to transfer HDLC packet data to and from the Host.
Table 10.1A lists all of the Local Bus pins and their application in both operating modes. The Local Bus
operates only in a non-multiplexed fashion; it is not capable of operating as a multiplexed bus. For both
operating modes, the Local Bus can be set up for either Intel or Motorola type busses. This selection is
made in hardware by tying the LIM pin high or low.
Local Bus Signals Table 10.1A
Signal Name
Signal Description
LD[0:15]
Data Bus
LA[0:19]
LWR*(LR/W*)
LRD*(LDS*)
LBHE*
LIM
LINT*
LMS
LCLK
LRDY*
LCS*
LHOLD(LBR*)
LHLDA(LBG*)
LBGACK*
Address Bus
Bus Write (Read/Write Select)
Bus Read (Data Strobe)
Byte High Enable
Intel/Motorola Select
Interrupt
Mode Select
Bus Clock
Bus Ready
Chip Select
Hold Request (Bus Request)
Hold Acknowledge (Bus Grant)
Bus Acknowledge
PCI Bridge Mode
(LMS = 0)
Input on Read /
Output on Write
Output
Output
Output
Output
Input
Input
Input
Output
Input
Ignored
Output
Input
Output
Configuration Mode
(LMS = 1)
Input on Write /
Output on Read
Input
Input
Input
Tri-Stated
Input
Output
Input
Tri-Stated
Ignored
Input
Tri-Stated
Ignored
Tri-Stated
Notes:
1. Signals shown in parenthesis () are active when Motorola Mode (LIM = 1) is selected.
2. Signals suffixed with an asterisk (*) are active low signals.
163 of 203
DS3134
Bridge Mode Figure 10.1A
T1 / E1
Framer or
Transceiver
DS3134 Chateau
PCI /
Custom
Bus
Host
Processor
and Main
Memory
T1 / E1
Framer or
Transceiver
T1 / E1
Framer or
Transceiver
T1 / E1
Framer or
Transceiver
lb_cnfga
Local Bus
Bridge Mode with Arbitration Enabled Figure 10.1B
T1 / E1
Framer or
Transceiver
DS3134 Chateau
PCI /
Custom
Bus
T1 / E1
Framer or
Transceiver
T1 / E1
Framer or
Transceiver
1
2
T1 / E1
Framer or
Transceiver
3
1. Request
Bus Access
2. Bus Access
Granted
3. Transaction
Occurs
Local Bus
Local CPU that Handles
the Real Time Tasks Required
by the T1 / E1 Interfaces
Local RAM &
ROM
164 of 203
Host
Processor
and Main
Memory
lb_cnfgb
DS3134
Configuration Mode Figure 10.1C
T1 / E1
Framer or
Transceiver
DS3134 Chateau
PCI /
Custom
Bus
No
Access
Allowed
T1 / E1
Framer or
Transceiver
T1 / E1
Framer or
Transceiver
Host
Processor
and Main
Memory
Only Used to
Transfer HDLC
Data
T1 / E1
Framer or
Transceiver
lb_cnfgc
Local Bus
CPU Confgures and
Monitors DS3134
Local RAM &
ROM
PCI Bridge Mode
In the PCI Bridge Mode, data from the PCI bus can be transferred to the Local Bus. In this mode, the
Local Bus acts as a "master" and can create all the needed signals to control the bus. In the PCI Bridge
Mode, the user must configure the Local Bus Bridge Mode Control Register (LBBMC) which is described
in Section 10.2.
With 20 address lines, the Local Bus can address a 1M byte address space. The Host on the PCI bus will
determine where to map this 1M byte address space within the 32-bit address space of the PCI bus by
configuring the Base Address in the PCI Configuration Registers (see Section 9).
Bridge Mode 8 & 16 Bit Access
During a bus access by the Host, the Local Bus can determine how to map the four possible byte positions
from/to the PCI bus to/from the Local Bus data bus (LD) pins by examining the PCBE* signals and the
Local Bus Width (LBW) control bit which resides in the Local Bus Bridge Mode Control (LBBMC)
register. If the Local Bus is to be used as an 8-bit bus (LBW = 1), then the Host must only assert one of
the PCBE* signals. The PCI data will be mapped to/from the LD[7:0] signal lines, the LD[15:0] signal
lines remain inactive. The Local Bus Block will drive the A0 and A1 address lines according to the
assertion of the PCBE* signals by the Host. See Table 10.1B for details. If the Host asserts more than
one of the PCBE* signals when the Local Bus is configured as an 8-bit bus, then the Local Bus will reject
the access and the PCI Block will return a Target Abort to the Host. See Section 9 for details on a Target
Abort.
165 of 203
DS3134
Local Bus 8-Bit Width Address / LBHE* Setting Table 10.1B
PCBE*
[3:0]
1110
1101
1011
0111
A1
A0
LBHE*
0
0
1
1
0
1
0
1
1
1
1
1
Note:
1. All other possible states for PCBE* will cause the device to return a Target Abort to the Host.
2. The 8-bit data picked from the PCI bus will be routed/sample to/from the LD[7:0] signal lines.
3. If no PCBE* signals are asserted during an access, a Target Abort is not return and no transaction
occurs on the Local Bus.
If the Local Bus is to be used as a 16-bit bus, then the LBW control bit must be set to zero. In 16-bit
accesses, by asserting the appropriate PCBE* signals (see Table 10.1C) the Host can either perform a
16-bit access or an 8-bit access. For a 16-bit access, the Host will enable the combination of either
PCBE0*/PCBE1* or PCBE2*/PCBE3* and the Local Bus block will map the word from/to the PCI bus
to/from the LD[15:0] signals. For an 8-bit access in the 16-bit bus mode, the Host must assert just one of
the PCBE0* to PCBE3* signals. If the Host asserts a combination of PCBE* signals not supported by the
Local Bus, then the Local Bus will reject the access and the PCI Block will return a Target Abort to the
Host. See Section 9 for details on a Target Abort. Section 10.3 contains a number of timing examples for
the Local Bus.
Local Bus 16-Bit Width Address / LD / LBHE* Setting Table 10.1C
PCBE*
[3:0]
1110
1101
1100
1011
0111
0011
8/16
A1
A0
8
8
16
8
8
16
0
0
0
1
1
1
0
1
0
0
1
0
LD[15:8]
active
active
active
active
LD[7:0]
LBHE*
active
1
0
0
1
0
0
active
active
active
Note:
1. All other possible states for PCBE* will cause the device to return a Target Abort to the Host.
2. The 16-bit data picked from the PCI bus will be routed/sample to/from the LD[7:0] & LD[15:8] signal
lines as shown.
3. If no PCBE* signals are asserted during an access, a Target Abort is not return and no transaction
occurs on the Local Bus.
166 of 203
DS3134
Bridge Mode Bus Arbitration
In the Bridge Mode, the Local Bus has the ability to arbitrate for bus access. In order for the feature to
operate, the Host must access the PCI Bridge Mode Control Register (LBBMC) and enable it via the
LARBE control bit (the default is bus arbitration disabled). If bus arbitration is enabled, then before a bus
transaction can occur, the Local Bus will first request bus access by asserting the LHOLD(LBR*) signal
and then wait for the bus to be granted from the Local Bus arbiter by sensing that the LHLDA(LBG*) has
been asserted. If the Host on the PCI Bus attempts a Local Bus access when the Local Bus is not granted
by the Local Bus master (LBGACK* is deasserted), then the Local Bus block will immediately inform the
Host that the Local Bus is busy and cannot be accessed at this time (in other words, come back later) by
issuing a PCI Target Retry. See Section 9 for details on the PCI Target Retry. When this happens, the
Local Bus block will not attempt the bus access and will keep the LA, LD, LBHE*, LWR*(LR/W*), and
LRD*(LDS*) signals tri-stated.
If the Host attempts a Local Bus access when the bus is busy, the Local Bus block will go ahead and
request bus access and after it has been granted, it will seize the bus for the time programmed into the
Local Bus Arbitration Timer (LAT0 to LAT3 in the LBBMC register) which can be from 32 to 1048576
clocks. As long as the local bus has been granted and the arbitration timer has at least 16 clocks left, then
the Host is allowed to access the Local Bus. See Figure 10.1D and the timing examples in Section 10.3
for more details.
Bridge Mode Bus Transaction Timing
When the Local Bus is operated in PCI Bridge Mode, the bus transaction time can be determined either
from an external ready signal (LRDY*) or from the PCI Bridge Mode Control Register (LBBMC) which
will allow a bus transaction time of 1 to 11 LCLK cycles. If the total access time to the Local Bus
exceeds 16 PCLK cycles, the PCI access will time out and a PCI Target Retry will be sent to the Host.
This will only occur when LRDY* has not been detected within 9 clocks. If this happens, the Local Bus
Error (LBE) status bit in the Status Master (SM) register will be set. Additional details on the LBE status
bit can be found in Section 4 and more details on transaction timing can be found in Figure 10.1D and the
timing examples in Section 10.3.
Bridge Mode Interrupt
In the PCI Bridge mode, the Local Bus can detect an external interrupt via the LINT* signal. If the Local
Bus detects that the LINTA* signal has been asserted, then it will set the LBINT status bit in the Status
Master (SM) register. The setting of this status bit can cause a hardware interrupt to occur at the PCI bus
via the PINTA* signal. This interrupt can be masked via the ISM register. See Section 4 for more
details.
Configuration Mode
In the Configuration Mode, the Local Bus is used only to configure the device and obtain status
information from the device. It is also used to configure the PCI Configuration Registers and hence the
PCI Bus signal PIDSEL is disabled when the Local Bus is in the Configuration Mode. Data cannot be
passed from the Local Bus to the PCI bus in this mode. The PCI bus will only be used as a high speed I/O
bus for the HDLC packet data. In this mode, bus arbitration, bus format, and the user settable bus
transaction time features are disabled. In the Configuration Mode, all bus accesses are based on 16-bit
addresses and 16-bit data. The upper four addresses (LA[19:16]) are ignored and 8-bit data accesses are
not allowed. See Section 12 for details on the AC timing requirements.
167 of 203
DS3134
Local Bus Access Flowchart Figure 10.1D
PCI Host Initiates a
Local Bus Access
No
Is Arbitration Enabled
for the Local Bus?
Yes
Is the Local Bus
Granted?
Request
the Bus
No
Yes
Are there 16 Clocks
Remaining?
No
Yes
Yes
Is the External Local Bus
Ready (LRDY*) Being Used?
No
Start 9 Clock Timer
LRDY* Active?
Yes
Local Bus Access
Progresses
No
Timer Expired?
No
Yes
Local Bus Access
Progresses
lb_fc1
Set the LBE Status Bit
Normal Access
Occurs
168 of 203
PCI Target Retry
Issued
DS3134
10.2 LOCAL BUS BRIDGE MODE CONTROL REGISTER DESCRIPTION
Register Name:
LBBMC
Register Description: Local Bus Bridge Mode Control Register
Register Address:
0040h
Note: This register can only be accessed via the PCI Bus and hence only in the PCI Bridge Mode. In the
Configuration Mode, this register cannot be accessed. It will be set to all zeros upon a hardware reset
issued via the PRST* pin. It will not be affected by a software reset issued via the RST control bit in the
Master Reset and ID (MRID) register.
7
6
5
4
3
2
1
0
n/a
LBW
LRDY3 LRDY2 LRDY1 LRDY0 LARBE LCLKE
15
14
13
12
11
10
9
8
n/a
n/a
n/a
n/a
LAT3
LAT2
LAT1
LAT0
Note: Bits that are underlined are read only, all other bits are read-write; default value for all bits is 0.
Bit 0 / Local Bus Clock Enable (LCLKE).
0 = tri-state the LCLK output signal pin
1 = allow LCLK to appear at the pin
Bit 1 / Local Bus Arbitration Enable (LARBE). When enabled, the LHOLD(LBR*), LBGACK*, and
LHLDA(LBG*) signal pins are active and the proper arbitration handshake sequence must occur for a
proper bus transaction. When disabled, the LHOLD(LBR*), LBGACK* and LHLDA(LBG*) signal pins
are deactivated and bus arbitration on the Local Bus is not invoked. In addition, the Arbitration Timer is
enabled (see the description of the LAT0 to LAT3 bits) when LARBE is set to a one.
0 = Local Bus Arbitration is disabled
1 = Local Bus Arbitration is enabled
Bit 2 / Local Bus Ready Control Bit 0 (LRDY0). lsb
Bit 3 / Local Bus Ready Control Bit 1 (LRDY1).
Bit 4 / Local Bus Ready Control Bit 2 (LRDY2).
Bit 5 / Local Bus Ready Control Bit 3 (LRDY3). msb
These control bits determine the duration of the Local Bus transaction in the PCI Bridge Mode. The bus
transaction can either be control via the external LRDY* input signal or via a predetermined period of 1
to 11 LCLK periods.
0000 = use the LRDY* signal input pin to control the bus transaction
0001 = bus transaction is defined as 1 LCLK period
0010 = bus transaction is defined as 2 LCLK periods
0011 = bus transaction is defined as 3 LCLK periods
0100 = bus transaction is defined as 4 LCLK periods
0101 = bus transaction is defined as 5 LCLK periods
0110 = bus transaction is defined as 6 LCLK periods
0111 = bus transaction is defined as 7 LCLK periods
1000 = bus transaction is defined as 8 LCLK periods
1001 = bus transaction is defined as 9 LCLK periods
1010 = bus transaction is defined as 10 LCLK periods
169 of 203
DS3134
1011 = bus transaction is defined as 11 LCLK periods
1100 = illegal state
1101 = illegal state
1110 = illegal state
1111 = illegal state
Bit 6 / Local Bus Width (LBW).
0 = 16 bits
1 = 8 bits
Bits 8 to 11 / Local Bus Arbitration Timer Setting (LAT0 to LAT3). These 4 bits determine the total
time the Local Bus will seize the bus when it has been granted in the Arbitration Mode (LARBE = 1).
This period is measured from LHLDA(LBG*) being detected to LBGACK* inactive.
0000 = when granted, hold the bus for 32 LCLKs
0001 = when granted, hold the bus for 64 LCLKs
0010 = when granted, hold the bus for 128 LCLKs
0011 = when granted, hold the bus for 256 LCLKs
0100 = when granted, hold the bus for 512 LCLKs
1101 = when granted, hold the bus for 262144 LCLKs
1110 = when granted, hold the bus for 524288 LCLKs
1111 = when granted, hold the bus for 1048576 LCLKs
170 of 203
33 MHz
0.97 us
1.9 us
3.9 us
7.8 us
15.5 us
7.9 ms
15.9 ms
31.8 ms
25 MHz
1.3 us
2.6 us
5.1 us
10.2 us
20.5 us
10.5 ms
21.0 ms
41.9 ms
DS3134
10.3 EXAMPLES OF BUS TIMING FOR LOCAL BUS PCI BRIDGE MODE
OPERATION
Figure 10.3A
8-Bit Read Cycle
Intel Mode (LIM = 0)
Arbitration Enabled (LARBE = 1)
Bus Transaction Time = 4 LCLK (LRDY = 0100)
An attempted access by the Host causes the Local Bus to request the bus. If bus access has not been
granted (LBGACK* deasserted), then the timing shown at the top of the page will occur with LHOLD
being asserted and then once LHLDA is detected, the Local Bus will grab the bus for 32 to 1048576
clocks and then release it. If the bus has already been granted (LBGACK* asserted), then the timing
shown at the bottom of the page will occur.
LCLK
LHOLD
LHLDA
32 to 1048576 LCLKs
LBGACK*
Note: LA / LD / LBHE* / LWR* / LRD* are tri-stated.
1
LCLK
tri-state
LA[19:0]
2
3
4
Address Valid
LD[7:0]
LD[15:8]
tri-state
LBHE*
tri-state
LWR*
tri-state
LRD*
lb pi
171 of 203
DS3134
Figure 10.3B
16-Bit Write Cycle
Intel Mode (LIM = 0)
Arbitration Enabled (LARBE = 1)
Bus Transaction Time = 4 LCLK (LRDY = 0100)
An attempted access by the Host causes the Local Bus to request the bus. If bus access has not been
granted (LBGACK* deasserted), then the timing shown at the top of the page will occur with LHOLD
being asserted and then once LHLDA is detected, the Local Bus will grab the bus for 32 to 1048576
clocks and then release it. If the bus has already been granted (LBGACK* asserted), then the timing
shown at the bottom of the page will occur.
LCLK
LHOLD
LHLDA
32 to 1048576 LCLKs
LBGACK*
Note: LA / LD / LBHE* / LWR* / LRD* are tri-stated.
1
LCLK
tri-state
LA[19:0]
tri-state
LD[7:0]
tri-state
LD[15:8]
2
3
4
Address Valid
Data Valid
Data Valid
tri-state
LBHE*
tri-state
LRD*
lb_pi
tri-state
LWR*
172 of 203
DS3134
Figure 10.3C
8-Bit Read Cycle
Intel Mode (LIM = 0)
Arbitration Disabled (LARBE = 0)
Bus Transaction Time = Timed from LRDY* (LRDY = 0000)
LCLK
LA[19:0]
1
2
3
4
5
6
7
8
9
10
Address Valid
LD[7:0]
LD[15:8]
LBHE*
LWR*
LRD*
LRDY*
lb_pi1_V2
10.3C
03/22/99
Note: The LRDY* signal must be detected by the 9th LCLK or the bus access attempted by the Host will
be unsuccessful and the LBE status bit will be set.
173 of 203
DS3134
Figure 10.3D
16-Bit Write (only upper 8-bits active) Cycle
Intel Mode (LIM = 0)
Arbitration Disabled (LARBE = 0)
Bus Transaction Time = Timed from LRDY* (LRDY = 0000)
LCLK
LA[19:0]
1
2
3
4
5
6
7
8
9
10
Address Valid
LD[7:0]
LD[15:8]
Data Valid
LBHE*
LRD*
LWR*
LRDY*
lb_pi1_v2
10.3D
03/22/99
Note: The LRDY* signal must be detected by the 9th LCLK or the bus access attempted by the Host will
be unsuccessful and the LBE status bit will be set.
174 of 203
DS3134
Figure 10.3E
8-Bit Read Cycle
Motorola Mode (LIM = 1)
Arbitration Enabled (LARBE = 1)
Bus Transaction Time = 6 LCLK (LRDY = 0110)
An attempted access by the Host causes the Local Bus to request the bus. If bus access has not been
granted (LBGACK* deasserted), then the timing shown at the top of the page will occur with LBR* being
asserted and then once LBG* is detected, the Local Bus will grab the bus for 32 to 1048576 clocks and
then release it. If the bus has already been granted (LBGACK* asserted), then the timing shown at the
bottom of the page will occur.
LCLK
LBR*
LBG*
32 to 1048576 LCLKs
LBGACK*
Note: LA / LD / LBHE* / LDS* / LR/W* are tri-stated.
1
LCLK
tri-state
LA[19:0]
2
3
4
5
6
Address Valid
Data Valid
LD[7:0]
LD[15:8]
tri-state
LBHE*
LR/W*
tri-state
lb_pm
tri-state
LDS*
175 of 203
DS3134
Figure 10.3F
8-Bit Write Cycle
Motorola Mode (LIM = 1)
Arbitration Enabled (LARBE = 1)
Bus Transaction Time = 6 LCLK (LRDY = 0110)
An attempted access by the Host causes the Local Bus to request the bus. If bus access has not been
granted (LBGACK* deasserted), then the timing shown at the top of the page will occur with LBR* being
asserted and then once LBG* is detected, the Local Bus will grab the bus for 32 to 1048576 clocks and
then release it. If the bus has already been granted (LBGACK* asserted), then the timing shown at the
bottom of the page will occur.
LCLK
LBR*
LBG*
32 to 1048576 LCLKs
LBGACK*
Note: LA / LD / LBHE* / LDS* / LR/W* are tri-stated.
1
LCLK
tri-state
LA[19:0]
tri-state
LD[7:0]
2
3
4
5
6
Address Valid
Data Valid
tri-state
LD[15:8]
tri-state
LBHE*
LR/W*
tri-state
tri-state
LDS*
lb_pm
176 of 203
DS3134
Figure 10.3G
16-Bit Read Cycle
Motorola Mode (LIM = 1)
Arbitration Disabled (LARBE = 0)
Bus Transaction Time = Timed from LRDY* (LRDY = 0000)
LCLK
LA[19:0]
1
2
3
4
5
6
7
8
9
10
Address Valid
LD[7:0]
LD[15:8]
LBHE*
LR/W*
LDS*
LRDY*
lb_pm1_v2
10.3G
03/22/99
Note:
The LRDY* signal must be detected by the 9th LCLK or the bus access attempted by the Host will be
unsuccessful and the LBE status bit will be set.
177 of 203
DS3134
Figure 10.3H
8-Bit Write Cycle
Motorola Mode (LIM = 1)
Arbitration Disabled (LARBE = 0)
Bus Transaction Time = Timed from LRDY* (LRDY = 0000)
LCLK
LA[19:0]
LD[7:0]
1
2
3
4
5
6
7
8
9
10
Address Valid
Data Valid
tri-state
LD[15:8]
LBHE*
LR/W*
LDS*
LRDY*
lb_pm1_v2
10.3H\
03/22/99
Note:
The LRDY* signal must be detected by the 9th LCLK or the bus access attempted by the Host will be
unsuccessful and the LBE status bit will be set.
178 of 203
DS3134
SECTION 11: JTAG
11.1 JTAG DESCRIPTION
The DS3134 device supports the standard instruction codes SAMPLE/PRELOAD, BYPASS, and
EXTEST. Optional public instructions included are HIGHZ, CLAMP, and IDCODE. See Figure 11.1A
for a Block Diagram. The DS3134 contains the following items, which meet the requirements, set by the
IEEE 1149.1 Standard Test Access Port and Boundary Scan Architecture:
Test Access Port (TAP)
TAP Controller
Instruction Register
Bypass Register
Boundary Scan Register
Device Identification Register.
The Test Access Port has the necessary interface pins, namely JTCLK, JTRST*, JTDI, JTDO, and JTMS.
Details on these pins can be found in Section 2.4. Details on the Boundary Scan Architecture and the Test
Access Port can be found in IEEE 1149.1-1990, IEEE 1149.1a-1993, and IEEE 1149.1b-1994.
JTAG Block Diagram Figure 11.1A
Boundary Scan
Register
Identification
Register
Mux
Bypass
Register
Instruction
Register
Select
Test Access Port
Controller
10K
JTDI
10K
JTMS
Tri-State
10K
JTCLK
JTRST*
JTDO
jtag_bd
11.2 TAP CONTROLLER STATE MACHINE DESCRIPTION
This section covers the details on the operation of the Test Access Port (TAP) Controller State Machine.
Please see Figure 11.2A for details on each of the states described below. The TAP controller is a finite
state machine, which responds to the logic level at JTMS on the rising edge of JTCLK.
179 of 203
DS3134
TAP Controller State Machine Figure 11.2A
Test-Logic-Reset
1
0
Run-Test/Idle
1
Select
DR-Scan
1
0
1
Select
IR-Scan
0
0
1
1
Capture-DR
Capture-IR
0
0
Shift-IR
Shift-DR
0
0
1
1
1
Exit1-DR
1
Exit1-IR
0
0
Pause-DR
Pause-IR
0
0
1
0
0
0
Exit2-DR
Exit2-IR
1
1
Update-DR
1
Update-IR
0
1
0
jtag_bd
Test-Logic-Reset
Upon power-up of the DS3134, the TAP controller will be in the Test-Logic-Reset state. The Instruction
register will contain the IDCODE instruction. All system logic on the DS3134 will operate normally.
Run-Test-Idle
Run-Test-Idle is used between scan operations or during specific tests. The Instruction register and Test
register will remain idle.
Select-DR-Scan
All test registers retain their previous state. With JTMS low, a rising edge of JTCLK moves the
controller into the Capture-DR state and will initiate a scan sequence. JTMS high moves the controller to
the Select-IR-SCAN state.
180 of 203
DS3134
Capture-DR
Data may be parallel loaded into the Test Data registers selected by the current instruction. If the
instruction does not call for a parallel load or the selected register does not allow parallel loads, the Test
register will remain at its current value. On the rising edge of JTCLK, the controller will go to the
Shift-DR state if JTMS is low or it will go to the Exit1-DR state if JTMS is high.
Shift-DR
The Test Data register selected by the current instruction will be connected between JTDI and JTDO and
will shift data one stage towards its serial output on each rising edge of JTCLK. If a Test register selected
by the current instruction is not placed in the serial path, it will maintain its previous state.
Exit1-DR
While in this state, a rising edge on JTCLK with JTMS high will put the controller in the Update-DR
state, which terminates the scanning process. A rising edge on JTCLK with JTMS low will put the
controller in the Pause-DR state.
Pause-DR
Shifting of the Test registers is halted while in this state. All Test registers selected by the current
instruction will retain their previous state. The controller will remain in this state while JTMS is low. A
rising edge on JTCLK with JTMS high will put the controller in the Exit2-DR state.
Exit2-DR
While in this state, a rising edge on JTCLK with JTMS high will put the controller in the Update-DR state
and terminate the scanning process. A rising edge on JTCLK with JTMS low will enter the Shift-DR
state.
Update-DR
A falling edge on JTCLK while in the Update-DR state will latch the data from the shift register path of
the Test registers into the data output latches. This prevents changes at the parallel output due to changes
in the shift register. A rising edge on JTCLK with JTMS low, will put the controller in the Run-Test-Idle
state. With JTMS high, the controller will enter the Select-DR-Scan state.
Select-IR-Scan
All Test registers retain their previous state. The Instruction register will remain unchanged during this
state. With JTMS low, a rising edge on JTCLK moves the controller into the Capture-IR state and will
initiate a scan sequence for the Instruction register. JTMS high during a rising edge on JTCLK puts the
controller back into the Test-Logic-Reset state.
Capture-IR
The Capture-IR state is used to load the shift register in the Instruction register with a fixed value. This
value is loaded on the rising edge of JTCLK. If JTMS is high on the rising edge of JTCLK, the controller
will enter the Exit1-IR state. If JTMS is low on the rising edge of JTCLK, the controller will enter the
Shift-IR state.
181 of 203
DS3134
Shift-IR
In this state, the shift register in the Instruction register is connected between JTDI and JTDO and shifts
data one stage for every rising edge of JTCLK towards the serial output. The parallel register, as well as
all Test registers remains at their previous states. A rising edge on JTCLK with JTMS high will move the
controller to the Exit1-IR state. A rising edge on JTCLK with JTMS low will keep the controller in the
Shift-IR state while moving data one stage through the Instruction shift register.
Exit1-IR
A rising edge on JTCLK with JTMS low will put the controller in the Pause-IR state. If JTMS is high on
the rising edge of JTCLK, the controller will enter the Update-IR state and terminate the scanning
process.
Pause-IR
Shifting of the Instruction register is halted temporarily. With JTMS high, a rising edge on JTCLK will
put the controller in the Exit2-IR state. The controller will remain in the Pause-IR state if JTMS is low
during a rising edge on JTCLK.
Exit2-IR
A rising edge on JTCLK with JTMS low will put the controller in the Update-IR state. The controller
will loop back to the Shift-IR state if JTMS is high during a rising edge of JTCLK in this state.
Update-IR
The instruction shifted into the Instruction shift register is latched into the parallel output on the falling
edge of JTCLK as the controller enters this state. Once latched, this instruction becomes the current
instruction. A rising edge on JTCLK with JTMS low will put the controller in the Run-Test-Idle state.
With JTMS high, the controller will enter the Select-DR-Scan state.
11.3 INSTRUCTION REGISTER AND INSTRUCTIONS
The Instruction register contains a shift register as well as a latched parallel output and is 3 bits in length.
When the TAP controller enters the Shift-IR state, the instruction shift register will be connected between
JTDI and JTDO. While in the Shift-IR state, a rising edge on JTCLK with JTMS low will shift data one
stage towards the serial output at JTDO. A rising edge on JTCLK in the Exit1-IR state or the Exit2-IR
state with JTMS high will move the controller to the Update-IR state. The falling edge of that same
JTCLK will latch the data in the instruction shift register to the instruction parallel output. Instructions
supported by the DS3134 and their respective operational binary codes are shown in Table 11.3A.
Instruction Codes Table 11.3A
Instructions
Selected Register
SAMPLE/PRELOAD
BYPASS
EXTEST
CLAMP
HIGHZ
IDCODE
Boundary Scan
Bypass
Boundary Scan
Boundary Scan
Boundary Scan
Device Identification
182 of 203
Instruction Codes
010
111
000
011
100
001
DS3134
SAMPLE/PRELOAD
A mandatory instruction for the IEEE 1149.1 specification. This instruction supports two functions. The
digital I/Os of the DS3134 can be sampled at the Boundary Scan register without interfering with the
normal operation of the device by using the Capture-DR state. SAMPLE/PRELOAD also allows the
DS3134 to shift data into the Boundary Scan register via JTDI using the Shift-DR state.
EXTEST
EXTEST allows testing of all interconnections to the DS3134. When the EXTEST instruction is latched
in the instruction register, the following actions occur. Once enabled via the Update-IR state, the parallel
outputs of all digital output pins will be driven. The Boundary Scan register will be connected between
JTDI and JTDO. The Capture-DR will sample digital inputs into the Boundary Scan register.
BYPASS
When the BYPASS instruction is latched into the parallel Instruction register, JTDI connects to JTDO
through the one-bit Bypass Test register. This allows data to pass from JTDI to JTDO not affecting the
device's normal operation.
IDCODE
When the IDCODE instruction is latched into the parallel Instruction register, the Identification Test
register is selected. The device identification code will be loaded into the Identification register on the
rising edge of JTCLK following entry into the Capture-DR state. Shift-DR can be used to shift the
identification code out serially via JTDO. During Test-Logic-Reset, the identification code is forced into
the instruction register's parallel output. The device ID code will always have a one in the LSB position.
The next 11 bits identify the manufacturer's JEDEC number and number of continuation bytes followed
by 16 bits for the device and 4 bits for the version. The device ID code for the DS3134 is 00006143h.
11.4 TEST REGISTERS
IEEE 1149.1 requires a minimum of two Test registers; the Bypass register and the Boundary Scan
register. An optional Test register has been included in the DS3134 design. This Test register is the
Identification register and is used in conjunction with the IDCODE instruction and the Test-Logic-Reset
state of the TAP controller.
Bypass Register
This is a single one-bit shift register used in conjunction with the BYPASS, CLAMP, and HIGHZ
instructions, which provides a short path between JTDI and JTDO.
Identification Register
The Identification register contains a 32-bit shift register and a 32-bit latched parallel output. This
register is selected during the IDCODE instruction and when the TAP controller is in the Test-LogicReset state.
Boundary Scan Register
This register contains both a shift register path and a latched parallel output for all control cells and digital
I/O cells and is TBD bits in length. Table 11.4A shows all of the cell bit locations and definitions.
183 of 203
DS3134
Boundary Scan Control Bits Table 11.4A
Bit
Symbol
Lead
I/O
Control Bit Description
213
212
211
210
209
208
207
206
205
204
203
202
201
200
199
198
197
196
195
194
193
192
191
190
189
188
187
186
185
184
183
182
181
180
179
178
177
176
175
174
173
172
171
LD.iocntl
LD0
LD1
LD2
LD3
LD4
LD5
LD6
LD7
LD8
LD9
LD10
LD11
LD12
LD13
LD14
LD15
LIM
LMS
LHOLD(LBR*)
LHLDA(LBG*)
LBGACK*
LINT.iocntl
LINT*
LCS*
LRDY*
LCLK
LBHE*
LWR.iocntl
LWR*(LR/W*)
LRD.iocntl
LRD*(LDS*)
LA.iocntl
LA0
LA1
LA2
LA3
LA4
LA5
LA6
LA7
LA8
LA9
V20
U20
T18
T19
T20
R18
P17
R19
R20
P18
P19
P20
N18
N19
N20
M17
M18
M19
L19
L18
L20
K20
K19
K18
J20
H20
H19
H18
G20
G19
F20
G18
F19
E20
G17
F18
E19
D20
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I
I
O
I
O
I/O
I
I
O
O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
0=LD0 to LD15 are inputs;1=LD0 to LD15 are outputs
0 = LINT* is an input; 1 = LINT* is an output
0 = LWR* is an input; 1 = LWR* is an output
0 = LRD* is an input; 1 = LRD* is an output
0 = LA0 to LA19 are inputs; LA0 to LA19 are outputs
184 of 203
DS3134
Bit
Symbol
Lead
I/O
170
169
168
167
166
165
164
163
162
161
160
159
158
157
156
155
154
153
152
151
150
149
148
147
146
145
144
143
142
141
140
139
138
137
136
135
134
133
132
131
130
129
128
127
126
LA10
LA11
LA12
LA13
LA14
LA15
LA16
LA17
LA18
LA19
RC8
RS8
RD8
TC8
TS8
TD8
RC9
RS9
RD9
TC9
TS9
TD9
RC10
RS10
RD10
TC10
TS10
TD10
RC11
RS11
RD11
TC11
TS11
TD11
RC12
RS12
RD12
TC12
TS12
TD12
RC13
RS13
RD13
TC13
TS13
E18
D19
C20
E17
D18
C19
B20
C18
B19
A20
B17
C17
D16
A18
A17
C16
B16
A16
C15
D14
B15
A15
C14
B14
A14
C13
B13
A13
D12
C12
B12
A12
B11
C11
A10
B10
C10
A9
B9
C9
B8
C8
A7
B7
A6
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I
I
I
I
I
O
I
I
I
I
I
O
I
I
I
I
I
O
I
I
I
I
I
O
I
I
I
I
I
O
I
I
I
I
I
Control Bit Description
185 of 203
DS3134
Bit
Symbol
Lead
I/O
125
124
123
122
121
120
119
118
117
116
115
114
113
112
111
110
109
108
107
106
105
104
103
102
101
100
99
98
97
96
95
94
93
92
91
90
89
88
87
86
85
84
83
82
81
TD13
RC14
RS14
RD14
TC14
TS14
TD14
RC15
RS15
RD15
TC15
TS15
TD15
RC0
RS0
RD0
TC0
TS0
TD0
RC1
RS1
RD1
TC1
TS1
TD1
RC2
RS2
RD2
TC2
TS2
TD2
RC3
RS3
RD3
TC3
TS3
TD3
RC4
RS4
RD4
TC4
TS4
TD4
RC5
RS5
C7
B6
A5
D7
C6
B5
A4
C5
B4
A3
D5
C4
B3
B1
C2
D2
D3
E4
C1
D1
E3
E2
E1
F3
G4
F2
F1
G3
G2
G1
H3
H2
H1
J4
J3
J2
J1
M1
M2
M3
N1
N2
N3
P1
P2
O
I
I
I
I
I
O
I
I
I
I
I
O
I
I
I
I
I
O
I
I
I
I
I
O
I
I
I
I
I
O
I
I
I
I
I
O
I
I
I
I
I
O
I
I
Control Bit Description
186 of 203
DS3134
Bit
Symbol
Lead
I/O
80
79
78
77
76
75
74
73
72
71
70
69
68
67
66
65
64
63
62
61
60
RD5
TC5
TS5
TD5
RC6
RS6
RD6
TC6
TS6
TD6
RC7
RS7
RD7
TC7
TS7
TD7
PRST*
PCLK
PGNT*
PREQ*
PAD.iocntl
R1
P3
R2
T1
P4
R3
T2
U1
T3
U2
V1
T4
U3
V2
W1
V3
W3
Y2
W4
V4
-
I
I
I
O
I
I
I
I
I
O
I
I
I
I
I
O
I
I
I
O
-
59
58
57
56
55
54
53
52
51
50
49
48
47
46
45
44
43
42
41
40
39
38
37
PAD31
PAD30
PAD29
PAD28
PAD27
PAD26
PAD25
PAD24
PCBE3.iocntl
PCBE3*
PIDSEL
PAD23
PAD22
PAD21
PAD20
PAD19
PAD18
PAD17
PAD16
PCBE2.iocntl
PCBE2*
PFRAME.iocntl
PFRAME*
U5
Y3
Y4
V5
W5
Y5
V6
U7
W6
Y6
V7
W7
Y7
V8
W8
Y8
U9
V9
Y9
W10
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
Control Bit Description
0 = PAD0 to PAD31 are inputs;PAD0 to PAD31 are
outputs
0 = PCBE3* is an input; 1 = PCBE3* is an output
0 = PCBE2* is an input; 1 = PCBE2* is an output
0 = PFRAME* is an input; 1 = PFRAME* is an output
187 of 203
DS3134
Bit
Symbol
Lead
I/O
Control Bit Description
36
35
34
33
32
PIRDY.iocntl
PIRDY*
PTRDY.iocntl
PTRDY*
PDEVSEL.iocntl
V10
Y10
-
I/O
I/O
-
0 = PIRDY* is an input; 1 = PIRDY* is an output
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
PDEVSEL*
PSTOP.iocntl
PSTOP*
PPERR.iocntl
PPERR*
PSERR*
PPAR.iocntl
PPAR
PCBE1.iocntl
PCBE1*
PAD15
PAD14
PAD13
PAD12
PAD11
PAD10
PAD9
PAD8
PCBE0.iocntl
PCBE0*
PAD7
PAD6
PAD5
PAD4
PAD3
PAD2
PAD1
PAD0
PINT*
PXAS*
PXDS*
PXBLAST*
Y11
W11
V11
Y12
W12
V12
Y13
W13
V13
Y14
W14
Y15
V14
W15
Y16
V15
W16
Y17
V16
W17
Y18
U16
V17
W18
V18
W19
Y20
I/O
I/O
I/O
O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
O
O
O
O
0 = PTRDY* is an input; 1 = PTRDY* is an output
0 = PDEVSEL* is an input; 1 = PDEVSEL* is an
output
0 = PSTOP* is an input; 1 = PSTOP* is an output
0 = PPERR* is an input; 1 = PPERR* is an output
0 = PPAR is an input; 1 = PPAR is an output
0 = PCBE1* is an input; 1 = PCBE1* is an output
0 = PCBE0* is an input; 1 = PCBE0* is an output
188 of 203
DS3134
SECTION 12: AC CHARACTERISTICS
ABSOLUTE MAXIMUM RATINGS*
Voltage on Any Lead with Respect to VSS (except VDD)
Supply Voltage (VDD) with Respect to VSS
Operating Temperature
Storage Temperature
Soldering Temperature
-0.3V to 5.5V
-0.3V to 3.63V
0C to +70C
-55C to +125C
See J-STD-020A specification
* This is a stress rating only and functional operation of the device at these or any other conditions above
those indicated in the operation sections of this specification is not implied. Exposure to absolute
maximum rating conditions for extended periods of time may affect reliability.
Note: The typical values listed below are not production tested.
RECOMMEND DC OPERATING CONDITIONS
Parameter
Logic 1
Logic 1 (Schmitt Input for PCLK)
Logic 0
Logic 0 (Schmitt Input for PCLK)
Supply
Symbol
VIH
VIHS
VIL
VILS
VDD
DC CHARACTERISTICS
Parameter
Supply Current @ VDD = 3.6V
Lead Capacitance
Schmitt Hysteresis
Input Leakage
Input Leakage (w/ pull-ups)
Output Leakage
Output Current (2.4V)
Output Current (0.4V)
Min
2.0
1.7
-0.3
-0.3
3.0
(0°C TO +70°C)
Typ
Max
5.5
5.5
0.8
0.7
3.6
Units
V
V
V
V
V
Notes
(0°C TO +70°C; VDD = 3.0V TO 3.6V)
Symbol
IDD
CIO
VTH
IIL
IILP
ILO
IOH
IOL
Min
Typ
Max
TBD
7
0.6
-10
-500
-10
-4.0
+4.0
+10
+500
+10
Units
ma
pF
V
uA
uA
uA
mA
mA
Notes
1
2
2
3
Notes:
1. RC0 to RC15 and TC0 to TC15 = 2.048 MHz / PCLK = 33 MHz / other inputs at VDD or grounded /
other outputs left open circuited.
2. 0V < VIN < VDD.
3. Outputs in Tri-State.
189 of 203
DS3134
AC CHARACTERISTICS - LAYER ONE PORTS
(0°C TO +70°C; VDD = 3.0V TO 3.6V)
Parameter
RC / TC Clock Period
RC / TC Clock Low Time
RC / TC Clock High Time
RD Set Up Time to the Falling Edge
or Rising Edge of RC
RS / TS Set Up Time to the Falling
Edge or Rising Edge of RC / TC
RD Hold Time from the Falling Edge
or Rising Edge of RC
RS / TS Hold Time from the Falling
Edge or Rising Edge of RC / TC
Delay from the Rising Edge or
Falling Edge of TC to Data Valid on
TD
Symbol
t1
t1
t2
t2
t3
t3
t4
t4
t4
Min
100
19
40
8
40
8
5
2
5
t5
t5
t5
5
1
5
t1 – 10
t6
t6
5
3
25
15
Notes:
1. Ports 0 to 15 in applications running up to 10 MHz.
2. Port 0 or Port 1 running in applications up to 52 MHz.
190 of 203
Typ
Max
t1 – 10
Units
ns
ns
ns
ns
ns
ns
ns
ns
ns
Notes
1
2
1
2
1
2
1
2
1
ns
ns
1
2
1
ns
ns
1
2
DS3134
LAYER ONE PORT AC TIMING DIAGRAM Figure 12A
t1
t2
t3
RC[n] / TC[n]
Normal Mode
RC[n] / TC[n]
Inverted Mode
t4
t5
RD[n] / RS[n] /
TS[n]
t6
TD[n]
l1 ac
Note:
TC and RC are independent from each other. In the above timing diagram, all the signals started with “T”
are reference to the transmit clock TC and all the signals started with “R” are reference to the receive
clock RC.
AC CHARACTERISTICS - LOCAL BUS IN BRIDGE MODE (LMS = 0)
(0°C TO +70°C; VDD = 3.0V TO 3.6V)
Parameter
Delay Time from the Rising Edge of
LCLK to Output Valid from Tri-State
Delay Time from the Rising Edge of
LCLK to Tri-State from Output Valid
Delay Time from the Rising Edge of
LCLK to Output Valid from an
Already Active Drive State
LD[15:0] Set Up Time to the Rising
Edge of LCLK
LD[15:0] Hold Time from the Rising
Edge of LCLK
Input Set Up Time to the Rising Edge
of LCLK
Input Hold Time from the Rising
Edge of LCLK
Symbol
t1
Min
2
t2
Max
10
Units
ns
2
15
ns
t3
2
10
ns
t4
5
ns
t5
2
ns
t6
10
ns
t7
15
ns
191 of 203
Typ
Notes
DS3134
LOCAL BUS BRIDGE MODE (LMS = 0) AC TIMING DIAGRAM Figure 12B
LCLK
t1
LA[19:0] / LD[15:0] / LBHE* /
LWR*(LR/W*) / LRD*(DS)
Tri-State
Data Valid
t2
LA[19:0] / LWR*(LR/W*) /
LRD*(LDS*) / LBHE*
Tri-State
Data Valid
t3
LA[19:0] / LWR*(LR/W*) /
LRD*(DS) / LHOLD(LBR*) /
LBGACK*
Data Valid
t4
t5
t6
t7
LD[15:0]
LINT* / LRDY*
LHLDA(LBG*)
lbus_ac
192 of 203
DS3134
AC CHARACTERISTICS - LOCAL BUS IN CONFIGURATION MODE (LMS = 1)
(0°C TO +70°C; VDD = 3.0V TO 3.6V)
Parameter
Set Up Time for LA[15:0] Valid to LCS*
Active
Set Up Time for LCS* Active to Either
LRD*, LWR*, or LDS* Active
Delay Time from Either LRD* or LDS*
Active to LD[15:0] Valid
Hold Time from Either LRD*, LWR*, or
LDS* Inactive to LCS* Inactive
Hold Time from LCS* Inactive to
LD[15:0] Tri-State
Wait Time from Either LWR* or LDS*
Active to Latch LD[15:0]
LD[15:0] Set Up Time to Either LWR* or
LDS* Inactive
LD[15:0] Hold Time from Either LWR*
or LDS* Inactive
LA[15:0] Hold from Either LWR* or
LDS* Inactive
Symbol
t1
Min
0
t2
0
t3
Typ
Max
Units
ns
ns
120
ns
t4
0
t5
5
t6
75
ns
t7
40
ns
t8
2
ns
t9
5
ns
193 of 203
Notes
1
ns
20
ns
1
DS3134
LOCAL BUS CONFIGURATION MODE (LMS = 1) AC TIMING DIAGRAM
Figure 12C
Intel Read Cycle
t9
LA[15:0]
Address Valid
Data Valid
LD[15:0]
t5
LWR*
t1
LCS*
t2
t3
t4
LRD*
LOCAL BUS CONFIGURATION MODE (LMS = 1) AC TIMING DIAGRAM
Figure 12C Continued
Intel Write Cycle
t9
LA[15:0]
Address Valid
LD[15:0]
t7
t8
LRD*
t1
LCS*
t2
t6
t4
LWR*
lb_ac1
194 of 203
DS3134
Motorola Read Cycle
t9
LA[15:0]
Address Valid
Data Valid
LD[15:0]
t5
LR/W*
t1
LCS*
t2
t3
t4
LDS*
Motorola Write Cycle
t9
LA[15:0]
Address Valid
LD[15:0]
t7
t8
LR/W*
t1
LCS*
t2
t6
t4
LDS*
lb_ac1
195 of 203
DS3134
AC CHARACTERISTICS - PCI BUS INTERFACE
(0°C TO +70°C; VDD = 3.0V TO 3.6V)
Parameter
PCLK Period
PCLK Low Time
PCLK High Time
All PCI Inputs & I/O Set Up Time to the
Rising Edge of PCLK
All PCI Inputs & I/O Hold Time from the
Rising Edge of PCLK
Delay from the Rising Edge of PCLK to
Data Valid on all PCI Outputs & I/O
Delay from the Rising Edge of PCLK to
Tri-State on all PCI Outputs & I/O
Delay from the Rising Edge of PCLK to
Data Valid from Tri-State on all PCI
Outputs & I/O
Symbol
t1
t2
t3
t4
Min
30
12
12
7
t5
0
t6
2
Typ
Max
40
ns
t7
t8
11
ns
28
ns
2
ns
PCI BUS INTERFACE AC TIMING DIAGRAM Figure 12D
t1
t2
t3
PCLK
t4
t5
PCI Input
& I/O
t6
PCI Output
& I/O
t7
PCI Output &
I/O to Tri-State
Tri-State
Data Valid
t8
PCI Output &
I/O from Tri-State
Tri-State
Data Valid
pci_ac
196 of 203
Units
ns
ns
ns
ns
Notes
DS3134
AC CHARACTERISTICS - JTAG TEST PORT INTERFACE
(0°C TO +70°C; VDD = 3.0V TO 3.6V)
Parameter
JTCLK Clock Period
JTCLK Clock Low Time
JTCLK Clock High Time
JTMS / JTDI Set Up Time to the
Rising Edge of JTCLK
JTMS / JTDI Hold Time from the
Rising Edge of JTCLK
Delay Time from the Falling Edge of
JTCLK to Data Valid on JTDO
Symbol
t1
t2
t3
t4
Min
1000
400
400
50
t5
50
t6
2
Typ
Max
Units
ns
ns
ns
ns
ns
50
JTAG TEST PORT INTERFACE AC TIMING DIAGRAM Figure 12E
t1
t2
t3
JTCLK
t4
t5
JTMS / JTDI
t6
JTDO
jtag_ac
197 of 203
ns
Notes
DS3134
SECTION 13: MECHANICAL DIMENSIONS
198 of 203
DS3134
SECTION 14: APPLICATIONS
Section 14 describes some possible applications for the DS3134. The number of potential configurations
is numerous and only a few are shown. Users are encouraged to contact the factory for support of their
particular application. Contact information is shown in Table 14A.
Telecom Applications Support Contact Information Table 14A
email
web
[email protected]
www.dalsemi.com
The T1 and E1 channelized application examples shown in Section 14 will be one of two types. The first
type is where a single T1 or E1 data stream is routed to and from the DS3134. This first type is
represented as a thin arrow in the application examples and the electrical connections are shown in
Figure 14B. The second type is where four T1 or E1 data streams have been Time Division Multiplexed
(TDM) into a single 8.192 MHz data stream, which is routed to and from the DS3134. This second type
is represented as a thick arrow and the electrical connections are shown in Figure 14C.
Application Drawing Key Figure 14A
1x
4x
Single T1 or E1 Line at 1.544MHz or 2.048MHz
Quad (4) T1 or E1 Lines Byte Interleaved at 8.192M
Single T1/E1 Connection Figure 14B
Single T1/E1 Line Connection
DS3134
CHATEAU
RC
RD
RS
RCLK
RSER
RSYNC
Dallas Framer or
Transceiver
TC
TD
TS
TCLK
TSER
TSYNC
(elastic stores
disabled)
app_ovr
Note:
A looped timed application is shown. The transmit clock may be decoupled from the receive in applications
that are a timing master.
199 of 203
DS3134
QUAD T1/E1 CONNECTION Figure 14C
16 Port T1 or E1 with 256 HDLC Channel Support
Figure 14D shows an application where 16 T1 ports are interfaced to a single DS3134. In this
application, the T1 lines can be either clear channel or channelized. The DS21Q552 Quad T1 Transceiver
performs the line interface function and frames to the T1 line. To convert this application to an E1
design, the DS21Q552 is replaced with the DS21Q554 Quad E1 Transceiver, which is pin-for-pin
compatible. The DS21Q552 and DS21Q554 devices also are available in 3.3V versions (DS21Q352 and
DS21Q354 respectively).
16 Port T1 Application Figure 14D
DS3134
CHATEAU
Port 0
Port 1
Port 2
Port 3
Port 4
Port 5
Port 6
Port 7
Port 8
Port 9
Port 10
Port 11
Port 12
Port 13
Port 14
Port 15
DS21Q552
Quad T1
Transceiver
Four
T1 Lines
DS21Q552
Quad T1
Transceiver
Four
T1 Lines
DS21Q552
Quad T1
Transceiver
Four
T1 Lines
DS21Q552
Quad T1
Transceiver
Four
T1 Lines
app_d
200 of 203
DS3134
Dual T3 with 256 HDLC Channel Support
Figure 14E shows an application where two T3 lines are interfaced to a single DS3134. In this
application, the T3 lines are demultiplexed by the M13 block and passed to the DS21FF42 Four x Four 16
Channel T1 Framer and DS21FT42 Four x Three 12 Channel T1 Framer devices. The T1 framers locate
the frame and multiframe boundaries and interface to the DS3134 by aggregating four T1 lines into a
single 8.192 MHz data stream, which then flows into and out of the DS3134. The T1 lines can be either
clear channel or channelized.
Dual T3 Application Figure 14E
DS3134
CHATEAU
app_a
Port 0
Port 1
Port 2
Port 3
Port 4
Port 5
Port 6
Port 7
Port 8
Port 9
Port 10
Port 11
Port 12
Port 13
Port 14
Port 15
DS21FF42
Four x Four
16 Channel
T1 Framer
DS21FT42
Four x Three
12 Channel
T1 Framer
DS21FF42
Four x Four
16 Channel
T1 Framer
DS21FT42
Four x Three
12 Channel
T1 Framer
1
2
16
17
18
M13
Interface
T3
Line
#1
M13
Interface
T3
Line
#2
28
1
2
16
17
18
28
201 of 203
DS3134
Single T3 with 512 HDLC Channel Support
Figure 14F shows an application where a T3 line is interfaced to two DS3134. In this application, the T3
line is demultiplexed by the M13 block and passed to the DS21FF42 Four x Four 16 Channel T1 Framer
and DS21FT42 Four x Three 12 Channel T1 Framer devices. The T1 framers locate the frame and
multiframe boundaries and interface to the DS3134. In this application, aggregating four T1 lines into a
single 8.192 MHz data stream is not required since the DS3134 has enough physical ports to support the
application but aggregation could be done to cut down on the number of electrical connections between
the DS3134 and the T1 framers. The T1 lines can be either clear channel or channelized.
T3 Application (512 HDLC Channels) Figure 14F
DS3134
CHATEAU
#1
DS3134
CHATEAU
#2
Port 0
Port 1
Port 2
Port 3
Port 4
Port 5
Port 6
Port 7
Port 8
Port 9
Port 10
Port 11
Port 12
Port 13
Port 14
Port 15
Port 0
Port 1
Port 2
Port 3
Port 4
Port 5
Port 6
Port 7
Port 8
Port 9
Port 10
Port 11
Port 12
Port 13
Port 14
Port 15
DS21FF42
Four x Four
16 Channel
T1 Framer
1
2
16
M13
Interface
17
18
28
DS21FT42
Four x Three
12 Channel
T1 Framer
app_b
202 of 203
DS3134
Single T3 with 672 HDLC Channel Support
Figure 14G shows an application where a T3 line is interfaced to three DS3134. In this application, the
T3 line is demultiplexed by the M13 block and passed to the DS21FF42 Four x Four 16 Channel T1
Framer and DS21FT42 Four x Three 12 Channel T1 Framer devices. The T1 framers locate the frame
and multiframe boundaries and interface to the DS3134. In this application, aggregating four T1 lines
into a single 8.192 MHz data stream is not required since the DS3134 has enough physical ports to
support the application but aggregation could be done to cut down on the number of electrical connections
between the DS3134 and the T1 framers. The T1 lines can be either clear channel or channelized.
T3 Application (672 HDLC Channels) Figure 14G
DS3134
CHATEAU
#1
(Supports
10 T1 Lines)
DS3134
CHATEAU
#2
(Supports
10 T1 Lines)
DS3134
CHATEAU
#3
(Supports
8 T1 Lines)
Port 0
Port 1
Port 2
Port 3
Port 4
Port 5
Port 6
Port 7
Port 8
Port 9
Port 10
Port 11
Port 12
Port 13
Port 14
Port 15
Port 0
Port 1
Port 2
Port 3
Port 4
Port 5
Port 6
Port 7
Port 8
Port 9
Port 10
Port 11
Port 12
Port 13
Port 14
Port 15
DS21FF42
Four x Four
16 Channel
T1 Framer
1
2
16
M13
Interface
17
18
28
DS21FT42
Four x Three
12 Channel
T1 Framer
Port 0
Port 1
Port 2
Port 3
Port 4
Port 5
Port 6
Port 7
Port 8
Port 9
Port 10
Port 11
Port 12
Port 13
Port 14
Port 15
app_c
- END -
203 of 203