PEB20320H-V34 Infineon Technologies, PEB20320H-V34 Datasheet
PEB20320H-V34
Specifications of PEB20320H-V34
PEB20320H-V34IN
Available stocks
Related parts for PEB20320H-V34
PEB20320H-V34 Summary of contents
Page 1
ICs for Communications Multichannel Network Interface Controller for HDLC MUNICH32 PEB 20320 Version 3.4 User’s Manual 01.2000 DS3 ...
Page 2
... Components used in life-support devices or systems must be expressly authorized for such purpose! 1 Critical components of the Infineon Technologies AG, may only be used in life-support devices or systems the express written approval of the Infineon Technologies AG critical component is a component used in a life-support device or system whose failure can reasonably be expected to cause the failure of that life-support device or system affect its safety or effectiveness of that device or system ...
Page 3
Preface The Multichannel Network Interface Controller for HDLC (MUNICH32 Multichannel Protocol Controller for a wide area of telecommunication and data communication applications. Organization of this Document This User’s Manual is divided into 9 chapters organized as ...
Page 4
User’s Manual 4 PEB 20320 01.2000 ...
Page 5
Table of Contents 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ...
Page 6
Table of Contents 5.1.3.2 Hardware Reset Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177 5.1.4 Test ...
Page 7
Introduction The Multichannel Network Interface Controller for HDLC (MUNICH32 Multichannel Protocol Controller, which handles data channels of a full duplex PCM highway. It performs layer 2 HDLC formatting/deformatting or V.110 and X.30 protocols up ...
Page 8
Multichannel Network Interface Controller for HDLC MUNICH32 Version 3.4 1.1 Features • Serial Interface – independent communication channels. – Serial multiplexed (full duplex) input/output for 2048-, 4096-, 1544- or 1536-Kbit/s PCM highways. • Dynamic Programmable Channel Allocation ...
Page 9
V.110/X.30 Protocol – Automatic synchronization in receive direction, automatic generation of the synchronization pattern in transmit direction – bits freely programmable in transmit direction, van be changed during transmission; changes monitored and reported in ...
Page 10
General – Connection four MUNICH32 supporting a 128-channel basic access D-channel controller. – ON-CHIP receive and transmit data buffer; the buffer size is 256 bytes each. – HDLC protocol or transparent mode, support of ECMA 102, ...
Page 11
Pin Configuration (top view) 120 110 D8 121 D10 A10 130 D11 A11 D12 A12 D13 A13 V 140 ...
Page 12
Pin Definitions and Functions Pin Definitions and Functions Pin No. Symbol P-MQFP-160-1 83, 87, 88, 92 97, 103, 104, 110, 111, 117, 123, 130, 136, 141, 144, 150, 151, 157 10, 16, 22, 23, 29, ...
Page 13
Pin Definitions and Functions (cont’d) Pin No. Symbol P-MQFP-160-1 33 A29 DP1 28 A28 DP0 26, 21, 19, 15, A(27:2) 13 160, 156, 154, 149, 147, 143, 139, 135, 133, 128, 126, 122, 120, 116, 114, 109, ...
Page 14
Pin Definitions and Functions (cont’d) Pin No. Symbol P-MQFP-160-1 38, 34, 32, 27, D(31:0) 25, 20, 18, 14, 12 159, 153, 148, 146, 142, 138, 134, 132, 127, 125, 121, 119, 115, 113, 108, 106, 101, 99, ...
Page 15
Pin Definitions and Functions (cont’d) Pin No. Symbol P-MQFP-160-1 90 W/R R/W 75 READY DSACK User’s Manual Input (I) Function Output (O) O Write/Read (Intel bus mode) This signal distinguishes write from read operations. O Read/Write (Motorola bus mode) This ...
Page 16
Pin Definitions and Functions (cont’d) Pin No. Symbol P-MQFP-160-1 76 BERR 74 B16 User’s Manual Input (I) Function Output (O) I Bus Error (Intel and Motorola bus mode) This active low signal informs the MUNICH32 that a bus cycle error ...
Page 17
Pin Definitions and Functions (cont’d) Pin No. Symbol P-MQFP-160-1 82 HOLD BR 79 HLDA BG 81 BGACK PM User’s Manual Input (I) Function Output (O) O Bus Hold Request (Intel bus mode) This signal is driven high when the MUNICH32 ...
Page 18
Pin Definitions and Functions (cont’d) Pin No. Symbol P-MQFP-160-1 80 HLDAO BGO 66 AR User’s Manual Input (I) Function Output (O) O Bus Hold Acknowledge Passing ON (Intel bus mode) If another MUNICH32 has initiated a HOLD REQUEST the HOLD ...
Page 19
Pin Definitions and Functions (cont’d) Pin No. Symbol P-MQFP-160-1 40 INT/INT 44 RCLK 45 RSP 46 RDATA 61 SCLK User’s Manual Input (I) Function Output (O) O Interrupt Request An interrupt is given when a transmission/ reception error is detected, ...
Page 20
Pin Definitions and Functions (cont’d) Pin No. Symbol P-MQFP-160-1 51 … 47 CI(4:0) 56 … 53 JTEST (3:0) 65 TEST 67 TDATA 68 TSP 69 TCLK User’s Manual Input (I) Function Output (O) I Chip Identification Up to four MUNICH32 ...
Page 21
Pin Definitions and Functions (cont’d) Pin No. Symbol P-MQFP-160-1 60 RESET 41, 42, 43, 52, N.C. 70, 71, 72 User’s Manual Input (I) Function Output (O) I Reset - No Connect These pins are reserved and should not be connected ...
Page 22
Logic Symbol BE (3: (31:0) W/R R/W ADS/AS DS/PCHK Microprocessor Bus READY/DSACK Interface BERR B16 HOLD/BR HLDA/BG BGACK/PM HLDAO/BGO AR INT/INT 1) A31/DP3, A30/DP2, A29/DP1, A28/DP0, A[27:2] Figure 2 MUNICH32 Logic Symbol User’s Manual 30 32 MUNICH32 ...
Page 23
Functional Block Diagram TCLK TSP TDATA CD TF Transmit Formatter TB Transmit Buffer (3:0) A (31:2) D (31:0) ADS Figure 3 Block Diagram of MUNICH32 User’s Manual TEST RESET SCLK JTEST 4 Serial ...
Page 24
The internal functions of MUNICH32 are partitioned into 8 major blocks. 1. Serial Interface, Formatter Control Unit CD – Parallel-Serial conversion, PCM timing, switching of the test loops, controlling of the multiplex procedure. 2. Transmit Formatter TF – HDLC frame, ...
Page 25
System Integration The MUNICH32 is designed to handle data channels of a PCM highway. It transfers the data between the PCM highway and a memory shared with a host processor via a 32-bit P interface. At ...
Page 26
PCM Highway (2.048 Mbit/s, 1.544 Mbit/s, 1.536 Mbit/s, 4.096 Mbit/s) MUNICH32 Figure 5 General System Interface (Intel Bus Mode) PCM Highway MUNICH32 MUNICH32 Figure 6 General System Interface (Motorola Bus Mode) User’s Manual System Bus Memory CPU ...
Page 27
MUNICH32’s bus interface consists bit bidirectional data bus (D31 … D0), 32/28 Address lines (A31 … A2, BE3 … BE0) or (A27 … A2, BE3 … BE0), four data byte parity lines DP(3:0), five lines (W/R/R/W, ADS/AS, ...
Page 28
PCM Highway R EPIC PEB 2056 INT/INT MUNICH32 PEB 20320 PCM System Interface CPU Bus Arbitration Figure 8 Architecture of a Central D-Channel Handler User’s Manual Signaling Highway Interrupt HSCX Controller SAB 82525 System Bus System Bus Controller AR Local ...
Page 29
FALC54 PEB 2254 INT/INT MUNICH32 PEB 20320 PCM System Interface CPU Bus Arbitration Figure 9 Architecture of a Packet Switch/Router User’s Manual V.24, V.21, V.35, ... T1/S2 Line Line Interface Line Driver Interrupt ESCC8 SAB 82538 Controller System Bus System ...
Page 30
PCM System Interface Figure 10 MUNICH32 in a System with a RISC CPU Note: To reduce complexity the host interface is not explicitly shown here. User’s Manual T1/S2 Line Line Interface FALC54 Interrupt PEB 2254 Controller System Bus INT/INT System ...
Page 31
FALC54 PEB PCM System Interface INT/INT MUNICH32 PEB Figure 11 MUNICH32 in a System using Multiport Memory Note: To reduce complexity the host interface is not explicitly shown here. User’s Manual T1/S2 Line Line Interface Interrupt 2254 Controller System Bus ...
Page 32
Functional Description 2.1 Serial Interface The serial interface of MUNICH32 includes a data receive (RDATA) and a data transmit line (TDATA) as well as the accompanying control signals (RCLK = Receive Clock, RSP = Receive Synchronization Pulse, TCLK = ...
Page 33
SLOT PCM - Frame SLOT TCLK TSP TDATA FILL/MASK T1/DS1 - Mode Transmit Frame Timing SLOT 23 ...
Page 34
SLOT PCM - Frame SLOT TCLK TSP TDATA FILL/MASK T1/DS1 - Mode Transmit Frame Timing SLOT ...
Page 35
SLOT PCM - Frame SLOT TCLK TSP TDATA FILL/MASK CEPT - Mode Transmit Frame Timing SLOT ...
Page 36
SLOT TSP RSP 4.096 Mbit/s PCM-format: even numbered slot allocation 6 7 TSP RSP 4.096 Mbit/s PCM-format: odd numbered slot allocation Figure 15 4.096 Mbit/s PCM Frame Timing Note 1: A ...
Page 37
Figure 16 Example: Programmable ...
Page 38
Microprocessor Interface A 64-channel DMA controller (32 channels in receive direction and 32 channels in transmit direction) with buffer chaining capability is integrated in the MUNICH32. It provides DMA functions for full duplex channels and allows ...
Page 39
Intel Mode The Intel mode has two submodes – parity mode (even parity) and non parity mode – chosen by strapping PM to ‘1’ or ‘0’ respectively. In Intel mode the lower (higher) ordered byte of a ...
Page 40
If the HOLD ACKNOWLEDGE is driven low while the MUNICH32 is performing a bus cycle, the bus is released later than two clock periods after de-assertion of HOLD ACKNOWLEDGE. The current bus cycle is finished with a bus cycle error. ...
Page 41
WRITE SCLK A31-A2 BE(3:0) [A27-A2] W/R ADS READY BERR [DP3-DP0], D(31:0) INT [PCHK] Figure 19 Write Cycle Timing Diagram (Intel mode) User’s Manual Functional Description WRITE BERR 41 PEB 20320 Tristate ITD03502 01.2000 ...
Page 42
SCLK Tristate HOLD (extern) Tristate HOLD (intern) HLDA HLDAO Figure 20 Bus Management for Intel Bus Mode Note 1: Bus Cycle means, that the MUNICH32 under consideration starts a read or write access at most 4 clock periods after HLDA ...
Page 43
Motorola Mode In Motorola mode the bus is used in an asynchronous manner. The bus operation uses the handshake lines (AS, DS, DSACK and BERR) to control data transfer as shown in Figure 21, Figure 22. Address strobe AS ...
Page 44
SCLK A31-A2, BE (3:0) R DSACK D (31:0) BERR Figure 21 Read Bus Cycle Timing Diagram for Motorola Bus Mode SCLK A31-A2, BE (3:0) R DSACK D (31:0) BERR INT Figure 22 Write Bus Cycle Timing ...
Page 45
SCLK BR (extern) BR (intern) BG BGACK (extern) BGACK (intern) BGO Figure 23 Bus Management for Motorola Mode Note the Bus Management example it is assumed that the MUNICH32 under consideration has a higher priority than the other ...
Page 46
DMA Priorities Prioritization of Queueing DMA Cycles Priority Interrupt Highest priority Receive link list including accesses to the descriptors Transmit link list including accesses to the descriptors Lowest priority Configuration of a channel (action requests) The MUNICH32 will perform ...
Page 47
Basic Functional Principles MUNICH32 is a Multichannel Network Interface Controller for HDLC, offering a variety of additional features like subchanneling, data channels comprising of one or more time slots, DMI transparent or V.110/X.30 transmission and programmable ...
Page 48
RDATA Bit 0 Bit 1 RCLK Active Receive X 1 Channel (external) SCLK Active Receive X 0 Channel (internal) Load CD, CSR Data for X into Protocol Operation disabled RDATA CD CSR Bit 2 ...
Page 49
TDATA Bit 7 Bit 0 TCLK Active Transmit Channel (external) SCLK Active Transmit X 0 Channel (internal) Load CSR Data Protocol Operation for X into TF Phase of TF Protocol might write new Operation disabled Channel Config ...
Page 50
For example: a) 2.048-Mbit/s PCM highway 32 64-Kbit/s data channels (8 bits are sent with each PCM frame). Two long words of the buffer are allocated to each data channel 2.048-Kbit/s data channel The maximum buffer size for ...
Page 51
The receive buffer (RB FIFO buffer and also has a size of 64 long words, which allows storing the data of eight complete PCM frames before transferring to the shared memory. Figure 27 Partitioning of RB The data ...
Page 52
Receive Receive DATA DATA Receive Receive Descriptor Descriptor Transmit Transmit DATA DATA Transmit Transmit Descriptor Descriptor Receive Receive DATA DATA Receive Receive Descriptor Descriptor Transmit Transmit DATA DATA Transmit Transmit Descriptor Descriptor Receive Receive DATA DATA Receive Receive Descriptor Descriptor ...
Page 53
The shared memory allocated for each transmit and receive channel is organized as a chaining list of buffers set up by the host. Each chaining list is composed of descriptors and data sections. The descriptor contains the pointer to the ...
Page 54
The following Sections give Examples of Typical Transmit Situations for the Individual Modes Variable Size Frame Oriented Protocols (HDLC, TMB, TMR) Normal operation, handling of frame end (FE) indication and hold (H) indication. Note: 1. FNUM0 must be set to ...
Page 55
Figure 29 User’s Manual Functional Description 55 PEB 20320 01.2000 ...
Page 56
Fixed Size Frame Oriented Protocols (V110/X.30) Normal operation change (indicated by the V.110-bit in the transmit descriptor) Example for TRV = ‘11’ Note: 1. FNUM must be 0 for all transmit descriptors. 2. The actual E-, S-, ...
Page 57
Figure 30 User’s Manual Functional Description 57 PEB 20320 01.2000 ...
Page 58
Fixed Size Frame Oriented Protocols (V.110/X.30) Handling of frame end (FE) indication Note: 1. FNUM must be ‘0’ for all transmit descriptors. 2. The frame ( DATA 2 the octet no. y, containing the last data bit of ...
Page 59
Figure 31 User’s Manual Functional Description 59 PEB 20320 01.2000 ...
Page 60
Fixed Size Frame Oriented Protocols (V110/X.30) Handling of hold (H) indication Figure 32 User’s Manual Functional Description 60 PEB 20320 01.2000 ...
Page 61
Time Slot Oriented Protocol (TMA) Normal operation, handling of frame end (FE) indication and hold (H) indication. Note: 1. FNUM must be set to zero for TMA and the programmed flag with ...
Page 62
Figure 33 User’s Manual Functional Description 62 PEB 20320 01.2000 ...
Page 63
An activated transmission hold (hold bit in descriptor) prevents the MUNICH32 from sending more data frame end has not occurred just before, the current frame will be aborted and an interrupt generated. Afterwards, the interframe time-fill bytes will ...
Page 64
Data 2 Flag Frame ( ..., Data 1 FE FNUM2 ... Data 1 TH=1 in the Channel Specification handed over from ...
Page 65
Fixed Size Frame Oriented Protocol (V.110/X.30) Reaction to a channel specification containing Normal operation t Note: 1. The times and 1 2. The current frame processed, when handed over aborted, ...
Page 66
... (1) Frame ( Data 1 10-y Octets FE ... Data 1 Figure 35 Time Slot Oriented Protocol (TMA) Reaction to a channel specification containing Note ...
Page 67
Time-Slot Boundaries , Data 1 FE= FNUM0 ... Data 1 TH=1 in the Channel Specification handed over from Data 2 , TC, TC, ...
Page 68
Variable Size Frame Oriented Modes (HDLC, TMB, TMR) Reaction to a channel specification containing Silencing of poll cycles for hold. Note pulse for an action specification leading should be issued after ...
Page 69
... ... Flag Flag, Frame ( ..., Data 1 ) FNUM0 . . . Poll H=1? FE= FNUM0 H = ... Data 1 TH=1 in the Channel Specification handed over from ...
Page 70
Fixed Size Frame Oriented Protocol (V110/.30) Silencing of poll cycles Note: 1. The times t and 1 2. The TH bit (as all channel commands) is not synchronized with TB! (as opposed to the H-bit in ...
Page 71
AR (1) Frame ( Data 1 ) Frame ( 10-y Octets 10 Octets FE ... Data 1 TH=1 TH=0 in the in the t t Channel Channel 1 2 Specif. Specif. handed ...
Page 72
Time Slot Oriented Protocol (TMA) Reaction to a channel specification containing Note for TMA and the programmed flag for TMA and FNUM2 is ignored. The ...
Page 73
... ... ... , Data 1 FNUM0 . . . Poll No Poll H=1? FE= FNUM0 H = ... Data 1 TH=1 in the Channel Specification handed over from ...
Page 74
In receive direction the MUNICH32 reads a receive descriptor, calculates the data address, writes the current receive descriptor address into the CCS, and exchanges data between the on-chip receive buffer and the external memory. After the data section has been ...
Page 75
Monitoring functions are implemented in MUNICH32 to discover errors or condition changes, i.e. – Receive frame end – Receive frame abort by overflow of the receive buffer or hold condition or recognized ABORT flag – Frame overflow frame ...
Page 76
Detailed Protocol Description In the following sections the protocol support of the MUNICH32 is described in detail for transmit and receive direction separately. Each section starts with a discussion of the general features proceeds with protocol variants and options ...
Page 77
E y= FE=1 Figure 40 x Note the biggest integer smaller than . -- - For FNUM – < – the kind of Frame Check Sequence (FCS) ...
Page 78
Interrupts The possible interrupts for the mode in transmit direction are: HI: issued if the HI bit is detected in the transmit descriptor (not maskable) FI: issued if the FE bit is detected in the transmit descriptor (maskable by FIT ...
Page 79
Desc 31 0 A0010002 0 31 FE=1 HOLD=0 HI=1 NO=1 CSM=0 FNUM=2 Time Increases FLAG DATA ..... 01111110 01010101 00010100010111110 01111110 11111111 8 Zero Insertion FLAG 01111110 111110111110111110111110111110111110111110111110 DATA 3 0101010100010100010111110 Figure 41 Note: 1. Data is transmitted ...
Page 80
No FCS is generated here as CSM is ‘1’ for the second and third transmit descriptor. The FCS is supposed to be the last 2 bytes to be transmitted in this case, their validity is not checked internally. 6. ...
Page 81
HDLC Receive Direction General Features In receive direction: 1. The starting and ending flag (7E and extracted change of the interframe time-fill is recognized and reported by an interrupt. 3. The zero insertions (a ‘0’-bit after five ‘1’s ...
Page 82
The receiver is always in one of two possible interframe time-fill states called F and O. The following diagram explains them. A change from and from reported by an IFC ...
Page 83
For frames not fulfilling check a) no data are transferred to the shared memory irrespective of CS. Only an interrupt with the bit FI, SF and (possibly) ERR is generated. For frames fulfilling check a) but not check b) ...
Page 84
ERR: issued if one of the following error conditions has occurred: – FCS was incorrect – the bit length was greater than MFL – the frame was stopped by 7F – the frame could only be partly stored because of ...
Page 85
FLAG ..... 01111110 0100 0011 10111100 0011 1101 Abort Sequence 3 01111111 Generate HI-Int. 8800203D st 1 Desc 31 0 20080000 40080000 31 DATA Figure 44 User’s Manual DATA ...
Page 86
FLAG 01111110 (shared) FLAG 01111110 FLAG 01111110 rd 3 Desc 31 200C0000 C0080000 DATA 2 FCS 2 Figure 45 User’s Manual DATA 2 0000 0000 0011 0101 1001 0010 1101 1111 0 FCS 2 0000 0011 0010 0101 0100 1111 ...
Page 87
DATA 4 0101 0101 1101 1110 2 Flags with shared 0 0111 1110 111 1110 0000 FLAG DATA 6 01111110 0101 0101 1101 1110 1010 0101 1000 0000 0010 0111 DATA Ignored up to next Flag 1 1111110101000110011100111010 0111 Generate ...
Page 88
LFD is issued and always accompanied by NOB. CRCO shouldn’t be interpreted for a LFD frame. 7. Here the ending flag of the second frame is the starting flag of the third frame. 8. After an abort sequence data ...
Page 89
Desc 31 0 000C0000 C0041800 31 CRCO, NOB Last Access of a NOB Frame should be Ignored Figure 48 Note: 1. Only the 7 leading bytes are reported (the last 4 are supposed to be the FCS even ...
Page 90
For CRC = 0 (CRC 16) the correct FCS e.g. zeros for DATA 4 would be 00001 0100 0101 1110 the 5 Figure 49 For Intel interface the only difference is in the receive data sections. They would be st ...
Page 91
TMB Transmit Direction General Features In transmit direction: – The starting and ending flag (00 – The interframe time-fill between frames is generated automatically. Options The different options for this mode are: – The number of interframe time-fill characters as ...
Page 92
Generate HI-Interrupt 88002005 31 0 20020000 0 31 FLAG DATA 1 ..... Figure 51 Note: 1. Data is transmitted according to Q.921 §2.8 and fully transparent transmit descriptor with ...
Page 93
TMB Receive Direction General Features 1. The starting and ending flag (00 fill is recognized and extracted. 2. The number of bits within a frame is checked to be divisible The number of bytes within a frame ...
Page 94
Interrupts The possible interrupts for the mode in receive direction are: HI: issued if HI bit is detected in the receive descriptor (not maskable). FI: issued if a received frame has been finished as discussed in 1b) of the protocol ...
Page 95
DATA 1 FLAG 1 00000000 10111001 10000000 non octet synchronous FLAG 10111100 0000000 10100000 11110111 Generate FI-Int. 8800102A st 1 Desc 31 0 00040000 C0020000 31 DATA Figure 52 User’s Manual octet synchronous DATA ...
Page 96
Generate HI-Int. 8800202A th 4 Desc 31 0 20080000 40080000 31 DATA 4 01 Last Access of a LFD Frame should be Ignored Figure 53 Note: 1. After Receive Initialization is detected all data are ignored until the starting sequence ...
Page 97
For INV = 1 (channel inversion) all bits of the data stream (including DATA, FLAG) are interpreted inversely e.g. 1111 1111 0 would be interpreted as starting sequence then. For Intel interface the only difference is in the receive data ...
Page 98
TMR Transmit Direction General Features In transmit direction – the starting and ending flag (00 00 automatically. Options The different options for this mode are – the number of interframe time-fill characters as shown in Figure 29 by choosing FNUM ...
Page 99
Generate HI-Interrupt 88002005 31 0 20020000 0 31 FLAG DATA 1 ..... Frame of Effective 1 Length Byte Figure 55 Note: 1. Data is transmitted according to Q.921 §2.8 and fully ...
Page 100
TMR Receive Direction General Features 1. The starting and the ending flag (00 00 characters of the starting flag and the last character of the ending flag is extracted. 2. The number of bits within a frame is checked to ...
Page 101
Options There are no options in receive direction for this mode. Interrupts The possible interrupts for the mode in receive direction are identical to those of TMB. Example: TMR channel with INV = 0 (no inversion) CRC = 1 (required) ...
Page 102
FLAG 1 .... 00000000 00000000 10111001 DATA 10000000 00000000 10111100 DATA 4 11110011 11110111 11011101 Generate FI-Int. 88001035 st 1 Desc 00040000 C0030000 31 0 DATA Generate HI-Int. 88002035 th ...
Page 103
After receive initialization is detected all data are ignored until a starting sequence (16 ‘zeros’, ‘one’) is detected. 2. The octet synchronous (end) flag of one frame can be part of the (start) flag of the next frame. Note, ...
Page 104
TMA Transmit Direction General Features In the transmit direction – a slot-synchronous transparent data transmission – a high impedance overwrite for the masked bits in the slot – a programmable number of programmable fill characters between data (also slot synchronous) ...
Page 105
Example 1: (no subchanneling by fill/mask bits) TMA channel with TFLAG = B2 H INV = 0 (no data inversion) CRC = 0 (required) TRV = 00 (required (flag filtering) MODE = 00 (TMA) IFTF = 0 ...
Page 106
For INV = 1 the data stream would be inverted completely DATA 1 DATA 2 … Figure 59 For TFLAG has to be programmed to 00 DATA 1 DATA 2 D5 ...
Page 107
Example 2: (subchanneling by fill/mask bits) TMA channel with TFLAG = 00 (required for this case) H INV = 0 (no data inversion) CRC = 0 (required) TRV = 00 (required (required for subchanneling) MODE = 00 ...
Page 108
Figure 63 Note: Example 2 uses the same descriptors as example 1. Those bits in the data stream that are at places where fill/mask is ‘zero’ are overwritten by ‘Z’ i.e. high impedance. In all other protocols bits of the ...
Page 109
TMA Receive Direction General Features In the receive direction – a slot synchronous transparent data reception – a ‘1’ overwrite for masked bits in the slot – for FA = ‘1’ a slot synchronous programmable flag extraction is performed automatically. ...
Page 110
Slot 0 7 Boundaries 00040000 40040000 Figure 64 Note: The FE bit is never set in a receive descriptor. The data are formatted according to §2.8 Q.921. For (and therefore TFLAG = ...
Page 111
For INV = 1 the receiver filters the inverse of the TFLAG as TC out of the data stream and inverts the data (only the octet synchronous 28 For Intel interface the data sections would ...
Page 112
Slot Boundaries Fill/Mask "one" Overwrite External Data (RDATA) Internal Data For INV 00040000 40040000 Figure 66 User’s Manual ...
Page 113
V.110/X.30 Transmit Direction General Features In transmit direction – the synchronization pattern for V.110/X.30 frame as shown in Table 1. – the framing for the different data rates with programmable E-, S-, X-bits – sending ‘0’ before all frames is ...
Page 114
Options The different options for this mode are: – the framing pattern, as shown in Table 2 to Table 5, is programmed by the bits TRV. Interrupts HI: issued if the HI bit is detected in the transmit descriptor (not ...
Page 115
Example X.30/V110 channel with (required) INV = 0 CRC = 0 TRV variable (all values shown in examples (required) MODE = 10 (V.110/X.30) Intel interface Channel No 00028000 20030000 0 ...
Page 116
TRV = ...
Page 117
TRV = ...
Page 118
TRV = ...
Page 119
V.110/X.30 Receive Direction General Features In receive direction – the starting sequence (00 loss of synchronism is detected. – the synchronization pattern is monitored, after 3 consecutive erroneous frames a loss of synchronism is detected. – a change of E-, ...
Page 120
Table 2 Framing for Networks with 600-bit/s Data Rate Intermediate Rate = 8 Kbit/s, i.e. Subchannelling with Only 1 Fill/Mask Bit Set Octet No ...
Page 121
Table 4 Framing for Networks with 2400-bit/s Data Rate Intermediate Rate = 8 Kbit/s, i.e. Subchannelling with Only 1 Fill/Mask Bit Set Octet No ...
Page 122
Options The different options for this mode are the framing pattern as shown in Table 2 to Table 5 is programmed by the bits TRV. Interrupts The possible interrupts for this mode are FRC: issued if the receiver has detected ...
Page 123
. . . ...
Page 124
...
Page 125
Desc 31 00080000 40042000 Loss of Synch. Figure 71 For Intel mode the data sections have the form: Figure 72 User’s Manual 8E5B002D 8E5B002D 8800022D Desc 20040000 40040000 ...
Page 126
Boundary Scan Unit In MUNICH32 a Test Access Port (TAP) controller is implemented. The essential part of the TAP is a finite state machine (16 states) controlling the different operational modes of the boundary scan. Both, TAP controller and ...
Page 127
Table 6 Boundary Scan Sequence in PEB 20320 JTEST2 (TDI) Pin Pin No. 1 Reset 2 SCLK 3 TEST TDATA 6 TSP 7 TCLK 8 I/M 9 B16 10 Ready/DSACK 11 BERR 12 HLDA/BG 13 HLDAO/BGO 14 ...
Page 128
Table 6 Boundary Scan Sequence in PEB 20320 (cont’d) JTEST2 (TDI) Pin D10 42 A10 43 D11 44 A11 45 D12 46 A12 47 D13 48 A13 49 D14 ...
Page 129
Table 6 Boundary Scan Sequence in PEB 20320 (cont’d) JTEST2 (TDI) Pin 71 D25 72 A25 73 D26 74 A26 75 D27 76 A27 77 D28 78 A28/DP0 79 D29 80 A29/DP1 81 D30 82 A30/DP2 83 D31 84 A31/DP3 ...
Page 130
Table 7 Boundary Scan Test Modes Instruction (Bit 2 … 0) 000 001 010 011 111 others EXTEST is used to examine the interconnection of the devices on the board. In this test mode at first all input pins capture ...
Page 131
Operational Description 3.1 Reset State Upon reset MUNICH32 is set to its initial state. The active high system reset clears the internal logic and causes MUNICH32 to tristate all output lines. Channel processing is deactivated. After reset all buffers ...
Page 132
Transmit Descriptor FNUM = 00 , i.e. shared flags in HDLC, only eight zero bits between sent frames for H TMB. The E-, S-, X-bits are all set to zero internally by the reset. The receiver is set into the ...
Page 133
CI4 Figure 74 CI4 CI3 CI2 CI1 CI0 Loc. of Ctrl ...
Page 134
Detailed Register Description 4.1 Organization of the Shared Memory Because the MUNICH32 reads only long words, all addresses of the link lists, interrupt queue and the CCS must be a multiple of four; i.e. the two least significant bits ...
Page 135
Receive DATA Channel 0 Receive Descriptor Channel 0 Transmit DATA Channel 0 Transmit Descriptor Channel 0 Figure 76 Organization of the Shared Memory User’s Manual Detailed Register Description CCBA Control Start Address Action Specification Interrupt Circular Queue Interrupt Queue Specification ...
Page 136
Control and Configuration Section Table 8 Buffer Size of the Control and Configuration Section Control and Configuration Section Action specification Interrupt queue specification Time slot assignment Channel specification Current descriptor address 4.2.1 Action Specification (Read Once After Each Action ...
Page 137
IN: Initialization procedure; setting this bit to one causes MUNICH32 to fetch all the time slot assignments and the channel specification of the selected channel (channel number). To avoid collision all time slots being reinitialized should deactivated ...
Page 138
Channelwise external loop One single logical channel is mirrored logically from serial data input to serial data output. The other channels are not affected by this operation. The data rate for this single logical channel has to be identical ...
Page 139
PCM MFL Initialization Procedure Read the complete time-slot assignment and the channel spec. ...
Page 140
Interrupt Queue Specification The interrupt queue is specified as a kind of block (queue), starting on a start address ...
Page 141
Interrupt Information The next table shows the bit assignments for the interrupt information long word INT Interrupt Information When an interrupt occurs MUNICH32 sets the INT bit and ...
Page 142
Action request interrupts ARACK: Action Request Acknowledge; MUNICH32 sets the ARACK bit to indicate that an action request has been serviced. ARF: Action Request Fail; MUNICH32 aborts an ACTION REQUEST, if the required configuration cannot be performed. An action ...
Page 143
Where ‘1’ means that the bit is always ‘1’ for this mode ‘0’ means that the bit is always ‘0’ for this mode ‘F’ means the bit is fixed by the version number ‘R’ means a bit that can only ...
Page 144
FE bit; ERR and FI are set if a transmit descriptor contains a HOLD bit no FE bit IFC: (HDLC mode, receive direction only) ...
Page 145
V.110/X.30 mode one of the following receive errors occurred: – data could only partly stored due to internal buffer overflow of RB – 3 consecutive frames had an error in the synchronization pattern (loss of synchronism) – a fast ...
Page 146
RB. 1.2 HDLC, TMB, TMR The MUNICH32 is unable to access the shared memory in time or has detected a bus cycle error (BERR = 0) ...
Page 147
General VN(3...1) Framing Bits Changed V.110/X30 mode received E, S, ...
Page 148
Time Slot Assignment (Read only once after each action request pulse with an action specification with set IN or RES bit) The time slot assignment provides the cross reference between the 32 (24) time slots of the PCM highway ...
Page 149
Channel Number: The channel number identifies the data channel. Its transmission mode is described in the respective channel specification. TTI: Transmit Time slot Inhibit; setting this bit to ‘1’ causes MUNICH32 to tristate the transmit time slot. The data is ...
Page 150
If an event leads to an interrupt with several bits set (e.g. FI and ERR) masking only a proper subset of them (e.g. ERR) will lead to an interrupt with the nonmasked bits set (e.g. FI). If all bits of ...
Page 151
CCS. For HDLC, TMB, TMR the rest of a frame which was only partially transferred before suspension of the receive descriptor is ...
Page 152
IFC bit after received bits. • For V.110/X.30: if the receiver was in the synchronized frame state it will go to the unsynchronized state after current ...
Page 153
For V.110/X.30 and TMA data bits might get lost. General Notes to Receive Commands: 1. After a pulse at the reset pin a channel having a time slot with ...
Page 154
For HDLC, TMB, TMR the first part of the frame of the suspended descriptor is sent and append by at least at least Afterwards the next frame is started. For V.110/X.30 three 10-octet frames with errors in the synchronization pattern ...
Page 155
(clears receive off condition, sets transmit abort condition, affects only the serial interface) This abort is performed in the transmit formatter at the serial interface. The currently transmitted ...
Page 156
(clears a previous transmit abort condition, affects the DMA interface and the serial interface) Before the MUNICH32 has got a transmit initialization command it will not transmit anything ...
Page 157
HDLC, V.110/X.30,TMB, TMR, TMA respectively and then set it into the transmit off condition. 4. Before changing the MODE, CRC, CS, TRV, INV, TFLAG bits or TTI or time slot ...
Page 158
Receive Frame Examples: a) 0x7E, data byte, 0x7E data byte copied to shared memory + frame end status SF-bit set no SF indication interrupt generated FI indication interrupt generated ERR interrupt generated due to wrong CRC’ b) 0x7E, data byte ...
Page 159
TRV: Transmission Rate of V.110/X.30. These signals determine the number of repeated D-bits in a V.110/X.30 frame. Table 9 TRV No. of Repetitions Note: In the other modes these bits must be ...
Page 160
FTDA: First Transmit Descriptor Address points to the beginning of the transmit data chaining list. This descriptor is only interpreted with a fast transmit abort or a transmit jump or a transmit initialization command read but ignored with ...
Page 161
Current Receive and Transmit Descriptor Address 31 Current Receive Descriptor Address Channel 0 Current Receive Descriptor Address Channel 31 Current Transmit Descriptor Address Channel 0 Current Transmit Descriptor Address Channel 31 For easier monitoring of the link lists the ...
Page 162
Transmit Descriptor HOLD V.110 CSM FE: Frame End; this bit is valid in all modes. It indicates that after sending the data in the ...
Page 163
HOLD: If the MUNICH32 detects a hold bit it – generates an interrupt with ERR bit set V.110/X.30 mode – sends the data in the current transmit data section – generates the FCS bits for ...
Page 164
Intel Mode Motorola Mode ...
Page 165
FNUM = k means that after the current frame characters are sent ( times – 1) times times times TFLAG (k + ...
Page 166
For example (Intel mode): 1) ADD = 01 ADD = 00 ADD = 10 For example (Motorola-mode): 1) ADD = 01 ADD = 00, NO ...
Page 167
Next Transmit This 32-bit pointer contains the start address of the next transmit Descriptor Pointer: descriptor. After sending the indicated number of data bytes, MUNICH32 branches to the next transmit descriptor to continue transmission. The transmit descriptor is read entirely ...
Page 168
Receive Descriptor HOLD Status The receive descriptor contains 4 long words; the first, third and fourth have to be ...
Page 169
Afterwards the next received frame is transferred into the next receive descriptor. Interrupts are also generated again. • For V.110/X.30, TMA the device puts the next data into the next receive descriptor. Interrupts are also generated again. The HOLD ...
Page 170
HDLC, TMB, TMR if the end of a frame was stored in the receive data section status gives the receive status determined by RD (interrupt with set FI bit is generated) • for V.110/X.30 mode ...
Page 171
NI means the bit may be ‘1’ or ‘0’ but does not cause an interrupt with set ERR bit. ILN means that it may be ‘1’ or ‘0’ but should not be evaluated if LFD or NOB is also ‘1’. ...
Page 172
Note: In case of multiple errors all relevant bits are set. In case of ROF = 1 only the error conditions of the frame within which the overflow occurred are reported. Later frames that are aborted do not change the ...
Page 173
Application Notes 5.1 Test Loops 5.1.1 Test Loop Definitions for the MUNICH32 Two basic types of test loops are provided by the MUNICH32, internal and external. Each of these types is further subdivided into channelwise and complete test loops ...
Page 174
Internal Channelwise Test Loop One (and only one) logical channel is mirrored from the serial data output to the serial data input. The other logical channels are not affected by this operation. The transmit and receive data rates for ...
Page 175
CD Enable Ext. Complete Loop P Interface Figure 83 5.1.1.4 External Channelwise Test Loop One (and only one) logical channel is mirrored from the serial data input to the serial data output. The other logical channels are not affected by ...
Page 176
Test Loop Activation All of the test loops are closed (activated) and opened (deactivated) by setting/resetting the appropriate combination of bits in the Action Specification (Table 10). Any unlisted combination of LOC, LOOP and LOOPI is an invalid operation. ...
Page 177
Software Operations Close and open internal complete loop. Close and open internal channelwise loop. Close and open external complete loop. Close and open external channelwise loop. Change from internal complete loop to internal channelwise loop. Change from external complete ...
Page 178
Test Loop Examples 5.1.4.1 Internal Channelwise Test Loop Generate HW RESET, and hold off RSP/TSP for 1000 SCLK cycles. ASP: IQS: TSA[0]: TSA[1…31]: CSP[0]: CSP[1…31] CRA[0…31] CTA[0…31] ICQ: FRDA: FTDA: User’s Manual A104-8004 ;CEPT, MFL=260, IN, IA=1 ICQ 0000-001F ...
Page 179
Generate AR Pulse and wait for INT signal (set up TS0 and CH0). Read interrupt queue: ICQ: Set ASP for Internal Channelwise Loop test ASP: Generate AR Pulse and wait for INT signal. Read interrupt queue: ICQ: Clear HOLD bit ...
Page 180
External Channelwise Test Loop Generate HW RESET, and hold off RSP/TSP for 1000 SCLK cycles. ASP: IQS: TSA[0]: TSA[1…31]: 0000-0000 ( 31) CSP[0]: CSP[1…31] 0000-0000 CRA[0…31] 0000-0000 ( 32) CTA[0…31] 0000-0000 ( 32) ICQ: FRDA: FTDA: User’s Manual A104-8004 ...
Page 181
Generate AR Pulse and wait for INT signal (set up TS0 and CH0). Read interrupt queue: ICQ: Set ASP for External Channelwise test loop ASP: Generate AR Pulse and wait for INT signal. Read interrupt queue: ICQ: Read receive descriptors: ...
Page 182
MUNICH32 in a LAN/WAN Router 5.2.1 Introduction Subject of this application note is an ISDN/LAN Router, a communication system that enables two LANs to communicate via the ISDN. LAN Figure 85 ISDN/LAN Router The structure of the whole system ...
Page 183
Hardware The processor system is based on a Motorola 68040 processor. It contains 512 KByte SRAM, a bus controller and peripherals like timer, EPROM and interrupt controller. The application specific hardware is integrated by using a Peripheral Connector and ...
Page 184
Application Specific Hardware The application specific hardware consists of an ISDN primary rate interface and an Ethernet interface. The MUNICH32 PEB 20320 in conjunction with the layer 1 SIEMENS components ACFA (Advanced CMOS Frame Aligner) PEB 2035 and PRACT (Primary ...
Page 185
System Architecture The system architecture is shown in Figure 88. The MUNICH32, the CPU and the LAN controller store data in the shared memory. The communication between CPU and alternate bus master is done via the shared memory. The CPU ...
Page 186
Bus Arbitration Since three devices are using the bus it is necessary to implement a bus arbitration. Each bus master requests bus mastership and awaits bus control given the arbiter. The bus arbitration protocol is also Motorola ...
Page 187
Bus Timing Adaptation The bus controller manages memory accesses of all bus masters (CPU, MUNICH32 or LAN controller). The bus controller timing is Motorola 68040 specific. The MUNICH32 bus interface is either Intel specific or Motorola 68020/030 specific. Therefore ...
Page 188
The LAN controller’s (i82596) bus timing also needs to be adapted. The address lines A1, AO, Size 0 and Size 1 need to be generated, because the LAN controller performs 8 bit and 16 bit cycles as well as 32 ...
Page 189
DDS Tasks The message transfer between the modules is the main task of the DDS, realized by some service routines. DDMs and APMs are integrated in the DDS by executing a Module Init Routine. The Module Init Routine is called ...
Page 190
Message Descriptor Pool MUNICH32/LAN Controller Descriptor Pool Figure 92 Memory Management User’s Manual Allocate Free Allocate 190 PEB 20320 Application Notes Free ITS08290 01.2000 ...
Page 191
Device Driver Module MUNICH32 Tasks The MUNICH32 Device Driver Module has to prepare all memory structures for the MUNICH32. The ACTION REQUEST Pulse has to be generated. The device driver module also has to treat the MUNICH32 interrupts. Message ...
Page 192
Function TxShutDown RcJump RcShutDown SwitchlnternalChanLoop SwitchlnternalCompLoop ShowMunich32VersionNr CheckActionRequestQueue Looks for messages to be processed and branches to Interrupt Entry Point The information in the interrupt queue is read and a message containing that information is sent to the user. In ...
Page 193
Programming the MUNICH32 for this Application The basic programming of the MUNICH32 for this application is realized in the Module Initialization Routine. Further programming is done by calling the function ‘Init Channel’ for each channel once. Transmit data is then ...
Page 194
Send Frame Routine Calling ‘SendFrame’ after initialization of a channel results in executing ‘AddHdlcFrame’. In that routine the transmit descriptors are disconnected from the message and linked to the memory structures. If the message source is the ‘MROUTE Application Module’ ...
Page 195
ISDN 64 kbit/s each Channel Frame Descr Ch1 Count Count EOF = 0 Frame Descr Ch 2 Count Count EOF 1 = Figure 93 Insertion of additional Information To make efficient use of the available bandwidth, the parallel use of ...
Page 196
The fe-bit marks the end of one HDLC frame, the EOF bit marks the end of the Ethernet frame. The additional information comprises the 8-bit word descriptor count, 16-bit word frame count and EOF a 8-bit variable which indicates the ...
Page 197
Performance Considerations Some considerations about the performance are made by investigating the maximum data rate. Further investigations are made about the bus occupancy by all busmasters and the MUNICH32 poll access’ influence on the data rate. Finally the processing ...
Page 198
Bus Occupancy The bus occupancy during normal operation is shown in Figure 96. In this case the data buffer size was 32 Byte. The CPU has busmastership during 90% of the time. The MUNICH32 as well as the LAN controller, ...
Page 199
MUNICH32 Polling The influence of the polling can be illustrated by showing the bus occupancy of MUNICH32 poll accesses only. Figure 97 Bus Occupancy During Polling Here the MUNICH32 is polling 31 channels (= 31 Every access is 5 clock ...
Page 200
Frame Processing During normal operation the processing of a frame comprises three consecutive parts. During transmission from ISDN to LAN the frame is first processed from the MUNICH32, then from the CPU and finally from the LAN controller. MUNICH32 CPU ...