INFINEON PSB2186

ICs for Communications
ISDN Subscriber Access Controller for Terminals
ISAC®-S TE
PSB 2186
User’s Manual 10.94
PEB 2186
Revision History: 10.94
Previous Releases: 11.88; 3.89; 12.89; 02.95
Page
Subjects (changes since last revision)
The present documentation is an editorial update of the
Technical Manual 12.89
Data Classification
Maximum Ratings
Maximum ratings are absolute ratings; exceeding only one of these values may cause
irreversible damage to the integrated circuit.
Characteristics
The listed characteristics are ensured over the operating range of the integrated circuit. Typical
characteristics specify mean values expected over the production spread. If not otherwise
specified, typical characteristics apply at TA = 25 °C and the given supply voltage.
Operating Range
In the operating range the functions given in the circuit description are fulfilled.
For detailed technical information about “Processing Guidelines” and “Quality Assurance”
for ICs, see our “Product Overview”.
Edition 10.94
This edition was realized using the software system FrameMaker
Published by Siemens AG, Breech Belittler, Marketing-Communication,
Banisters 73, D-81541 Munching.

Siemens AG 1994. All Rights Reserved.
As far as patents or other rights of third parties are concerned, liability is only assumed for components per se, not
for applications, processes and circuits implemented within components or assemblies.
The information describes the type of component and shall not be considered as assured characteristics.
Terms of delivery and rights to change design reserved.
For questions on technology, delivery, and prices please contact the Offices of Semiconductor Group in Germany
or the Siemens Companies and Representatives worldwide (see address list).
Due to technical requirements components may contain dangerous substances. For information on the type in
question please contact your nearest Siemens Office, Semiconductor Group.
Siemens AG is an approved CECC manufacturer.
General Information
Table of Contents
Page
1
Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.1
Pin Definitions and Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.2
Logic Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.3
Functional Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.4
System Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.4.1
ISDN Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.4.2
Microprocessor Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2
Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.1
General Functions and Device Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.2
Interface and Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.3
IOM®-2 Mode Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.3.1
Basic IOM®-2 Frame Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.3.2
IOM®-2 Interface Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.3.3
mP Access to B and IC Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.3.4
MONITOR Channel Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
2.3.5
C/I-Channel Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
2.3.6
TIC-Bus Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
2.4
Layer-1 Functions for the S/T Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
2.4.1
S/T Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
2.4.2
Analog Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
2.4.3
S/T-Interface Circuitry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
2.4.4
S/T Interface Pre-Filter Compensation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
2.4.5
Receiver Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
2.4.5.1
Receive Signal Oversampling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
2.4.5.2
Adaptive Receiver Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
2.4.5.3
Level Detection Power Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
2.4.6
Timing Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
2.4.7
Activation/Deactivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
2.4.7.1
FAinfA_1fr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
2.4.7.2
FAinfB_1fr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
2.4.7.3
FAinfD_1fr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
2.4.7.4
FAinfA_kfr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
2.4.7.5
FAinfB_kfr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Semiconductor Group
3
General Information
Table of Contents
Page
2.4.7.6
FAinfD_kfr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
2.4.7.7
FAregain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
2.4.8
D-Channel Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
2.4.9
S- and Q-Channel Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
2.5
Terminal Specific Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
2.6
Test Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
2.7
Layer-2 Functions for the ISDN-Basic Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
2.7.1
Message Transfer Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
2.7.2
Protocol Operations (auto-mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
2.7.3
Reception of Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
2.7.4
Transmission of Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
2.7.5
Documentation of the Auto Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
2.7.5.1
Legend of the Auto-Mode Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
2.7.5.2
Additional General Considerations when Using the Auto Mode . . . . . . . . . . . . . . 77
2.7.5.3
Dealing With Error Conditions in Auto Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
3
Operational Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
3.1
Microprocessor Interface Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
3.2
Interrupt Structure and Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
3.3
Control of Layer 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
3.3.1
Activation/Deactivation of IOM® Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
3.3.2
Activation/Deactivation of S/T Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
3.3.2.1
Layer-1 Command/Indication Codes and State Diagrams . . . . . . . . . . . . . . . . . . 125
3.3.3
Example of Activation/Deactivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
3.4
Control of Layer-2 Data Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
3.4.1
HDLC-Frame Reception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
3.4.2
HDLC-Frame Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
3.5
Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
3.6
Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
4
Detailed Register Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
4.1
HDLC Operation and Status Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
4.1.1
Receive FIFO RFIFO Read Address 00-1FH . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
4.1.2
Transmit FIFO XFIFO Write Address 00-1FH . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
4.1.3
Interrupt Status Register ISTA Read Address 20H . . . . . . . . . . . . . . . . . . . . . . . 146
Semiconductor Group
4
General Information
Table of Contents
Page
4.1.4
Mask Register MASK Write Address 20H . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
4.1.5
Status Register STAR Read Address 21H . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
4.1.6
Command Register CMDR Write Address 21H . . . . . . . . . . . . . . . . . . . . . . . . . . 149
4.1.7
Mode Register MODE Read/Write Address 22H . . . . . . . . . . . . . . . . . . . . . . . . . 150
4.1.8
Timer Register TIMR Read/Write Address 23H . . . . . . . . . . . . . . . . . . . . . . . . . . 152
4.1.9
Extended Interrupt Register EXIR Read Address 24H . . . . . . . . . . . . . . . . . . . . 154
4.1.10
Transmit Address 1 XAD1 Write Address 24H . . . . . . . . . . . . . . . . . . . . . . . . . . 155
4.1.11
Receive Frame Byte Count Low RBCL Read Address 25H . . . . . . . . . . . . . . . . 156
4.1.12
Transmit Address 2 XAD2 Write Address 25H . . . . . . . . . . . . . . . . . . . . . . . . . . 156
4.1.13
Received SAPI Register SAPR Read Address 26H . . . . . . . . . . . . . . . . . . . . . . 156
4.1.14
SAPI1 Register SAP1 Write Address 26H . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
4.1.15
Receive Status Register RSTA Read Address 27H . . . . . . . . . . . . . . . . . . . . . . 157
4.1.16
SAPI2 Register SAP2 Write Address 27H . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
4.1.17
TEI1 Register 1 TEI1 Write Address 28H . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
4.1.18
Receive HDLC Control Register RHCR Read Address 29H . . . . . . . . . . . . . . . . 160
4.1.19
TEI2 Register TEI2 Write Address 29H . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
4.1.20
Receive Frame Byte Count High RBCH Read Address 2AH . . . . . . . . . . . . . . . 161
4.1.21
Status Register 2 STAR2 Read/Write Address 2BH . . . . . . . . . . . . . . . . . . . . . . 162
4.2
Special Purpose Registers: IOM®-2 Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
4.2.1
Serial Port Control Register SPCR Read/Write Address 30H . . . . . . . . . . . . . . . 163
4.2.2
Command/Indication Receive 0 CIR0 Read Address 31H . . . . . . . . . . . . . . . . . 164
4.2.3
Command/Indication Transmit 0 CIX0 Write Address 31H . . . . . . . . . . . . . . . . . 165
4.2.4
MONITOR Receive Channel 0 MOR0 Read Address 32H . . . . . . . . . . . . . . . . . 166
4.2.5
MONITOR Transmit Channel 0 MOX0 Write Address 32H . . . . . . . . . . . . . . . . . 166
4.2.6
Command/Indication Receive 1 CIR1 Read Address 33H . . . . . . . . . . . . . . . . . 166
4.2.7
Command/Indication Transmit 1 CIX1 Write Address 33H . . . . . . . . . . . . . . . . . 166
4.2.8
MONITOR Receive Channel 1 MOR1 Read Address 34H . . . . . . . . . . . . . . . . . 167
4.2.9
MONITOR Transmit Channel 1 MOX1 Write Address 34H . . . . . . . . . . . . . . . . . 167
4.2.10
Channel Register 1 C1R Read/Write Address 35H . . . . . . . . . . . . . . . . . . . . . . . 167
4.2.11
Channel Register 2 C2R Read/Write Address 36H . . . . . . . . . . . . . . . . . . . . . . . 167
4.2.12
B1-Channel Register B1CR Read Address 37H . . . . . . . . . . . . . . . . . . . . . . . . . 168
4.2.13
Synchronous Transfer Control Register STCR Write Address 37H . . . . . . . . . . . 168
4.2.14
B2-Channel Register B2CR Read Address 38H . . . . . . . . . . . . . . . . . . . . . . . . . 169
Semiconductor Group
5
General Information
Table of Contents
Page
4.2.15
Additional Feature Register 1 ADF1 Write Address 38H . . . . . . . . . . . . . . . . . . . 170
4.2.16
Additional Feature Register 2 ADF2 Read/Write Address 39H . . . . . . . . . . . . . . 171
4.2.17
MONITOR Status Register MOSR Read Address 3AH . . . . . . . . . . . . . . . . . . . . 172
4.2.18
MONITOR Control Register MOCR Write Address 3AH . . . . . . . . . . . . . . . . . . . 172
4.2.19
S-, Q-Channel Receive Register SQRR Read Address 3BH . . . . . . . . . . . . . . . 173
4.2.20
S, Q Channel Transmit Register SQXR Write Address 3BH . . . . . . . . . . . . . . . . 174
5
Electrical Characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
6
ISAC®-S TE Low Level Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
6.1
Architecture and Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
6.2
Summary of LLC Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
6.2.1
Layer-1 Related Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
6.2.2
HDLC-Controller Related Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
6.2.3
External Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
6.3
LLC-Code Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
6.3.1
Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
6.3.2
Definitions and Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
6.3.2.1
Type Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
6.3.2.2
Macro Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
6.4
Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
6.5
LLC-Routine Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
6.5.1
ISAC®-S TE Layer-1 Functions: The SBC Part . . . . . . . . . . . . . . . . . . . . . . . . . . 201
6.5.2
ISAC®-S TE HDLC-Controller Related Functions: The ICC Part . . . . . . . . . . . . 202
6.6
Listing of Driver Routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
7
Package Outlines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
IOM®, IOM®-1, IOM®-2, SICOFI®, SICOFI®-2, SICOFI®-4, SICOFI®-4µC, SLICOFI®, ARCOFI® , ARCOFI®-BA, ARCOFI®-SP,
EPIC®-1, EPIC®-S, ELIC®, IPAT®-2, ITAC®, ISAC®-S, ISAC®-S TE, ISAC®-P, ISAC®-P TE, IDEC®, SICAT®, OCTAT®-P,
QUAT®-S are registered trademarks of Siemens AG.
MUSAC™-A, FALC™54, IWE™, SARE™, UTPT™, ASM™, ASP™ are trademarks of Siemens AG.
Purchase of Siemens I2C components conveys a license under the Philips’ I2C patent to use the components in the I2C-system
provided the system conforms to the I2C specifications defined by Philips. Copyright Philips 1983.
Semiconductor Group
6
General Information
Introduction
The PSB 2186 ISAC®-S TE implements the four-wire S/T interface used to link voice/data
terminals to an ISDN.
The PSB 2186 combines the functions of the S-Bus Interface Circuit (SBC: PEB 2080) and the
ISDN Communications Controller (ICC: PEB 2070) on one chip.
The component switches B- and D-channels between the S/T and the ISDN Oriented Modular
(IOM®) interfaces, the latter being a standard backplane interface for the ISDN-basic access.
The device provides all electrical and logical functions of the S/T interface, such as: activation/
deactivation, mode dependent timing recovery and D-channel access and priority control.
The HDLC packets of the ISDN D-channel are handled by the ISAC-S which interfaces them
to the associated microcontroller. In one of its operating modes the device offers high level
support of layer-2 functions of the LAPD protocol.
The ISAC-S is a CMOS device, available in a P-DIP-40, P-LCC-44, P-MQFP-64 package. It
operates from a single + 5 V supply and features a power-down state with very low power
consumption.
Semiconductor Group
7
ISDN Subscriber Access Controller
for Terminals (ISAC®-S TE)
PSB 2186
Preliminary Data
1
CMOS IC
Features
Terminal IOM®-2 terminal specific version of the
PEB 2086:
● Pin and software compatible to PEB 2086
● Compatible to PEB 2085 (Symmetrical Receiver)
● Full duplex 2B+D S/T interface transceiver according to
CCITT I.430
● Conversion of the frame structure between the
S/T interface and IOM-2
● Receive timing recovery
● D-channel access control
● Activation and deactivation procedures with automatic
wake-up from power-down state
● Access to S and Q bits of S/T interface
● Adaptively switched receive thresholds
● Support of LAPD protocol
● FIFO buffer (2 x 64 bytes) for efficient transfer of
D-channel packets
● 8-bit microprocessor interface, multiplexed or
non-multiplexed
● Serial interface: IOM-2 interface including bit clock and
strobe signal
● Implementation of IOM-2 MONITOR and C/I-channel
protocol to control peripheral devices
● Microprocessor access to B- and intercommunicationchannels
● Watchdog timer
● Advanced CMOS technology
● Low power consumption: standby: 8 mW; active: 80 mW
P-MQFP-64
P-LCC-44
P-DIP-40
Type
Ordering Code
Package
PSB 2186H
Q67100-H6412
P-MQFP-64 (SMD)
PSB 2186N
Q67100-H6390
P-LCC-44 (SMD)
PSB 2186P
Q67100-H6389
P-DIP-40
The PSB 2186, ISAC-S TE is software compatible to the PEB 2085, ISAC-S.
Semiconductor Group
8
10.94
Features
Pin Configuration
(top view)
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
49
50
32
31
51
30
52
29
53
54
28
27
55
26
56
25
PSB 2186
57
24
58
23
59
22
60
21
61
20
62
19
16
15
14
13
12
11
10
9
8
7
6
5
N.C.
N.C.
A0
RD(DS)
WR(R/W)
CS
ALE
IDP1 (DU)
IDP0 (DD)
SX2
SX1
VDD
N.C.
N.C.
N.C.
N.C.
N.C.
N.C.
N.C.
N.C.
N.C.
VSSD
BCL
INT
N.C.
VSSA
XTAL2
XTAL1
VDD
SR2
N.C.
SR1
4
17
3
18
64
2
63
1
N.C.
A2
A1
SDS1
N.C.
RST
A5
EAW
VSSD
DCL
FSC1
N.C.
VSSD
N.C.
A4
A3
48
N.C.
N.C.
N.C.
N.C.
AD7 /D7
AD6 /D6
AD5 /D5
AD4 /D4
AD3 /D3
AD2 /D2
AD1 /D1
AD0 /D0
N.C.
N.C.
N.C.
N.C.
P-MQFP-64
A1
A2
AD7/ D7
AD6/ D6
AD5/ D5
AD4/ D4
AD3/ D3
AD2/ D2
AD1/ D1
AD0/D0
A0
P-LCC-44
6
SDS1
N.C.
RST
EAW/A5
VSSD
DCL
FSC1
N.C.
VSSD
4
3
2
1 44 43 42 41 40
39
8
38
9
37
10
36
11
35
12
PSB 2186
Semiconductor Group
34
13
33
14
32
15
31
16
30
17
18 19 20 21 22 23 24 25 26 27 28
A3
N.C.
N.C.
V SSD
BCL
INT
V SSA
XTAL2
XTAL1
SR2
SR1
N.C.
A4
5
7
9
29
RD(DS)
WR(R/W)
CS
ALE
IDP1 (DU)
IDP0 (DD)
SX2
SX1
VDD
N.C.
N.C.
ITP04471
ITP04470
Features
Pin Configuration
(top view)
P-DIP-40
AD4
1
40
AD3
AD5
2
39
AD2
AD6
3
38
AD1
AD7
4
37
AD0
N.C.
5
36
RD
SDS1
6
35
WR
N.C.
7
34
CS
RST
8
33
ALE
EAW
9
32
IDP1 (DU)
VSSD
10
31
IDP0 (DD)
DCL
11
30
SX2
FSC1
12
29
SX1
N.C.
13
28
V DD
VSSD
14
27
N.C.
N.C.
15
26
N.C.
N.C.
16
25
SR1
N.C.
17
24
SR2
VSSD
18
23
XTAL1
BCL
19
22
XTAL2
INT
20
21
VSSA
PSB 2186
ITP04469
Semiconductor Group
10
Features
1.1
Pin Definitions and Functions
Pin No.
P-DIP-40
Pin No.
Pin No.
Symbol
P-MQFP-64 P-LCC-44
37
38
39
40
1
2
3
4
37
38
39
40
41
42
43
44
41
42
43
44
1
2
3
4
AD0/D0
AD1/D1
AD2/D2
AD3/D3
AD4/D4
AD5/D5
AD6/D6
AD7/D7
Input (I)
Output (O)
Open
Drain (OD)
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
34
27
37
CS
I
–
28
38
R/W
I
35
28
38
WR
I
–
29
39
DS
I
36
29
39
RD
I
20
8
23
INT
OD
Semiconductor Group
11
Function
Multiplexed Bus Mode:
Address/data bus transfers
addresses from the µP system
to the ISAC-S TE and data
between the µP system and
the ISAC-S TE.
Non-Multiplexed Bus Mode:
Data bus. Transfers data
between the µP system and
the ISAC-S TE.
Chip Select: A “Low“ on this
line selects the ISAC-S TE for
a read/write operation.
Read/Write: When “High”
identifies a valid µP access as
a read operation. When “Low”,
identifies a valid µP access as
a write operation (Motorola
bus mode).
Write: This signal indicates a
write operation (Intel bus
mode).
Data Strobe: The rising edge
marks the end of a valid read
or write operation (Motorola
bus mode).
Read: This signal indicates a
read operation (Intel bus
mode).
Interrupt Request: The signal
is activated when the ISAC-S
TE requests an interrupt. It is
an open drain output.
Features
1.1
Pin Definitions and Functions (cont'd)
Pin No.
P-DIP-40
Pin No.
Pin No.
Symbol
P-MQFP-64 P-LCC-44
33
26
36
ALE
8
54
9
RST
12
59
13
FSC1
11
58
12
DCL
–
–
–
–
–
–
30
51
50
64
63
55
40
6
5
18
17
10
A0
A1
A2
A3
A4
A5
Semiconductor Group
12
Input (I)
Function
Output (O)
Open
Drain (OD)
I
Address Latch Enable: A
high on this line indicates an
address on the address/data
bus (multiplexed bus type
only). ALE also selects the
microprocessor interface type
(multiplexed or nonmultiplexed) P-LCC and
P-MQFP only.
I/O
Reset: A “High“ on this input
forces the ISAC-S TE into
reset state. The minimum
pulse length is four DCL-clock
periods or four ms. If the
terminal specific functions are
enabled, the ISAC-S TE may
also supply a reset signal.
O (I)
Frame Sync 1:
Frame sync output. “High“
during channel 0 on the IOM-2
interface. FSC1 becomes
Input if Test Mode is
programmed (ADF1).
O (I)
Data Clock: Clock of
frequency equal to twice the
data rate on the IOM-interface
Clock output 1536-kHz
IOM-2 mode
DCL becomes Input if Test
Mode is programmed (ADF1).
I
Address Bit 0
I
Address Bit 1
I
Address Bit 2(Non-multiplexed
I
Address Bit 3bus mode)
I
Address Bit 4
I
Address Bit 5
Features
1.1
Pin Definitions and Functions (cont'd)
Pin No.
P-DIP-40
Pin No.
Pin No.
Symbol
P-MQFP-64 P-LCC-44
9
56
10
EAW
6
52
7
SDS1
19
7
22
BCL
10, 14, 18
57, 6, 61
11, 15, 21 VSSD
Input (I)
Function
Output (O)
Open
Drain (OD)
I
External Awake (terminal
specific function). If a falling
edge on this input is detected,
the ISAC-S TE generates an
interrupt and, if enabled, a
reset pulse.
O
Serial Data Strobe 1.
A programmable strobe signal,
selecting either one or two Bor IC-channels on IOM-2
interface, is supplied via this
line. After reset, SDS1 takes
on its function only after a write
access to SPCR is made.
O
Bit Clock: Clock of frequency
768 kHz, IOM-2 mode.
–
Digital ground
21
10
24
–
Analog ground
28
13, 21
31
VSSA
VDD
–
Power supply (5 V ± 5 %)
23
12
26
XTAL1
I
22
11
25
XTAL2
O
24
25
29
14
16
22
27
28
32
SR2
SR1
SX1
I
I
O
30
23
33
SX2
O
31
32
24
25
34
35
IDP0(DD) I/O
IDP1(DU) I/O
Connection for crystal or
external clock input
Connection for external
crystal.
Left unconnected if external
clock is used.
S-Bus Receiver Input
S-Bus Receiver Input
S-Bus Transmitter Output
(positive)
S-Bus Transmitter Output
(negative)
IOM-Data Port 0 (DD)
IOM-Data Port 1 (DU)
Open drain without internal
pull-up resistor or push-pull
(ADF2:ODS)
Semiconductor Group
13
Features
1.2
Logic Symbol
0V
Reset
7.68 MHz ±100 ppm
VDD VSSA VSSD
RST
XTAL1
+5V 0V
SR2
IDP0 (DD)
R
IOM -2
XTAL2
TR = 100 Ω *)
IDP1 (DU)
SR1
EAW
S/T
FSC1
SX2
DCL
Clock Frame
Synchronization
TR = 100 Ω *)
BCL
SX1
SDS1
AD0...7
(D0...7)
WR RD
(A0...5) CS (R/W) (DS) INT ALE
µP
*) Terminating resistors only at the far ends of the connection
Figure 1
Logic Symbol of the ISAC®-S TE PSB 2186
Semiconductor Group
14
ITL04472
Features
1.3
Functional Block Diagram
R
IOM -2
S
B-Channel
Buffer
Switching
R
IOM
Interface
ISDN Basic
Access
Layer-1
Functions
D-Channel
Handling
Control
FIFO
µP Interface
ITB05406
µP
Figure 2
Block Diagram of the ISAC®-S TE
Semiconductor Group
15
Features
1.4
System Integration
1.4.1
ISDN Applications
The reference model for the ISDN-basic access according to CCITT I series recommendations
consists of
– an exchange and trunk line termination in the central office (ET, LT)
– a remote network termination in the user area (NT)
– a two-wire loop (U interface) between NT and LT
– a four-wire link (S interface) which connects subscriber terminals and the NT in the user
area as depicted in figure 3.
ISDN User Area
TE
ISDN Central Office
U
S
NT
LT
NT1
NT2
ET
NT1
T
TE
ITS02314
Figure 3
ISDN-Basic Subscriber Access Architecture
The NT equipment serves as a converter between the U interface at the exchange and the
S interface at the user premises. The NT may consist of either an NT1 only or an NT1 together
with an NT2 connected via the T interface which is physically identical to the S interface. The
NT1 is a direct transformation between layer 1 of S and layer 1 of U. NT2 may include higher
level functions like multiplexing and switching as in a PBX.
The ISAC-S TE is designed for the user area of the ISDN-basic access, especially for
subscriber terminal equipment with S interfaces. Figure 4 illustrates the application of the
ISAC-S TE.
Semiconductor Group
16
Features
PBX (NT2)
TE(1)
S
CP
TE(8)
SN
TE(1)
U
T
LT-S
LT-T
NT1
LT-S
CP = Central
Processor
Line
Card
TE(1)
TE(8)
R
SN = Switching
Network
Direct Subscriber Access
(point-to-point, short and extended
passive Bus)
= ISAC -S TE
U
S
NT1
ITS05407
Figure 4
Applications of the ISAC®-S TE (ISDN-Basic Access)
Terminal Applications
The concept of the ISDN basic access is based on two circuit-switched 64 kbit/s B channels
and a message oriented 16 kbit/s D channel for packetized data, signaling and telemetry
information.
Figure 5 shows an example of an integrated multifunctional ISDN-S terminal using the
ISAC-S TE. The ISAC-S TE provides the interface to the bus and separates the B- and
D channels.
The D channel, containing signaling data and packet switched data, is processed by the LAPD
controller contained in the ISAC-S TE and routed via a parallel µP interface to the terminal
processor. The high level support of the LAPD protocol which is implemented by the
ISAC-S TE allows the use of a low cost processor in cost sensitive applications.
The IOM-2 interface generated by the ISAC-S TE is used to connect different voice/data (V/D)
application modules:
– sources/sinks for the D channel
– sources/sinks for the B1- and B2 channels.
Semiconductor Group
17
Features
R
IOM -2
D,C/I
R
ICC
PEB 2070
ISAC -S TE
PSB 2186
B1
B2
IC1
Speech
Processing
DSP-COFI
IC2
Data
Encryption
HSCX
SAB 8252X
µC
Data Module
Speech Modules
Data Modules
ITD05408
Figure 5
Example of an ISDN®-S TE Voice/Data Terminal
Up to eight D-channel components (ICC: ISDN Communication Controller PEB 2070) may be
connected to the D- and C/I (Command/Indication) channels (TIC-bus). The ISAC-S TE and
ICC handle contention autonomously.
Data transfers between the ISAC-S TE and the voice/data modules are done with the help of
the IOM-MONITOR channel protocol. Each V/D module can be accessed by an individual
address. The same protocol enables the control of IOM-terminal modules and the allocation of
intercommunication channels inside the terminal. Two intercommunication channels IC1 and
IC2 allow a 2 × 64 kbit/s transfer rate between voice/data modules.
In the example above (figure 5), one ICC is used for data packets in the D channel. A voice
processor is connected to a programmable digital signal processing codec filter via IC1 and a
data encryption module to a data device via IC2. B1 is used for voice communication, B2 for
data communication.
Figure 6 shows the implementation of a ISDN feature phone using the ISAC-S TE and the
Audio Ringing Codec Filter featuring speakerphone (PSB 2165, ARCOFI-SP).
Semiconductor Group
18
Features
PSB 2165
ARCOFI R -SP
R
IOM -2
LCD
Control
LCD
Display
PSB 2186
R
ISAC -S TE
80C51
80C188
S-Bus
Power
Controller
PSB 2120
IRPC
ITS05409
Figure 6
ISDN-Feature Telephone
1.4.2
Microprocessor Environment
The ISAC-S TE is especially suitable for cost-sensitive applications with single-chip
microcontrollers (e.g. 8048, 8031, 8051). However, due to its programmable micro- processor
interface and non-critical bus timing, it fits perfectly into almost any 8-bit microprocessor
system environment. The microcontroller interface can be selected to be either of the Motorola
type (with control signals CS, R/W, DS) of the Siemens/Intel non-multiplexed bus type (with
control signals CS, WR, RD) or of the Siemens/Intel multiplexed address/data bus type (CS,
WR, RD, ALE).
An example how to connect the ISAC-S TE to a Siemens/Intel microcontroller is shown in
figure 7.
Semiconductor Group
19
Features
IOM R -2
+5V
INT(INTX)
INT
RD
RD
WR
ALE
ALE
80C51
(80C188)
RD
WR
WR
S0
(PSCX)
ALE
CS
R
ISAC -S TE
PSB 2186
SX1
SX2
SR1
SR2
A15 ... A8
AD ... AD0
A8 - A15
AD0 - AD7
AD7 ... AD0
Latch
Common Bus A15 - A0, D7 - D0
ITS05410
Memory
Figure 7
Connecting the ISAC®-S TE to Siemens/Intel Microcontroller
Semiconductor Group
20
Functional Description
2
Functional Description
2.1
General Functions and Device Architecture
The functional block diagram of the ISAC-S TE is shown in figure 8.
The left-hand side of the diagram contains the layer-1 functions, according to CCITT I series
recommendations:
– S-bus transmitter and receiver
– timing recovery and synchronization by means of digital PLL circuitry
– activation/deactivation
– access to S and Q channels
– handling of D channel
– test loops
– send single/continuous AMI pulses (diagnostics).
IDP1 (DU)
IDP0 (DD)
SX1
AMI
BIN
Buffer
SX2
R
IOM -2
Interface
D-CH
Access
V SSA
HDLC
Receiver
HDLC
Transmitter
Control
R-FIFO
SR2
AMI
BIN
X-FIFO
LAPD
Controller
Status
Command
Register
FIFO
Controller
V DD
V SS D
Buffer
RST
SR1
XTAL1
Timing
DPLL
µ P - Interface
XTAL0
ITS05411
BCL
DCL
FSC1 SDS1
Figure 8
Architecture of the ISAC®-S TE
Semiconductor Group
21
AD0 - AD7
A0 - A5&
D0 - D7
Control
INT
Functional Description
The right-hand side consists of:
– the serial interface logic for the IOM-2 interfaces, with B-channel switching capabilities
– the logic necessary to handle the D-channel messages (layer 2).
The latter consists of an HDLC receiver and an HDLC transmitter together with 64-byte deep
FIFO's for efficient transfer of the messages to/from the user's CPU.
In a special HDLC-controller operating mode, the auto mode, the ISAC-S TE processes
protocol handshakes (I- and S frames) of the LAPD (Link Access Procedure on the D channel)
autonomously.
Control and monitor functions as well as data transfers between the user's CPU and the D- and
B channels are performed by the 8-bit parallel µP-interface logic.
The IOM interface allows interaction between layer-1 and layer-2 functions. It implements
D-channel collision resolution for connecting other layer-2 devices to the IOM interface (TIC
bus), and the C/I and MONITOR channel protocols (IOM-2) to control peripheral devices.
The timing unit is responsible for the system clock and frame synchronization.
2.2
Interface and Operating Modes
The ISAC-S TE is configurable for the following application:
→
– ISDN terminals
TE mode
IOM®-2 Interface Mode (ADF2:IMS=1)
In this mode the IOM interface has the enhanced functionality of IOM-2. B-channel interfacing
is performed directly via the IOM-2 interface.
The ISAC-S TE supports the IOM-2 terminal mode frame structure (3 channels) according to
figure 11 (see chapter 2.3.1).
The operating mode is shown in table 1.
Table 1
Operating Mode and Functions of Specific Pins of the ISAC®-S PSB 2186 in IOM®-2 Mode
Pin No.
P-DIP-40-2
11
12
19
Pin No.
P-LCC-44-1
12
13
22
Pin No.
P-MQFP-64-1
58
59
7
Application
DCL
FSC1
BCL
TE
o:1536 kHz*
o:8 kHz*
o:768 kHz*
*) synchronized to the S/T interface
Semiconductor Group
o:output
22
Functional Description
The operating mode in relation to the timing recovery is illustrated in figure 9.
TE Mode, Terminal Timing Mode
CLOCK MASTER
768 kbit/s
768 kbit/s
IDP0 (DD)
IDP1 (DU)
V/D Module
DCL
R
ISAC -S TE
PSB 2186
FSC1 BCL
SDS1
1536 kHz
8 kHz
768 kHz
8 kHz
S
ITS05412
Figure 9
Operating Modes of ISAC®-S TE (IOM®-2)
Semiconductor Group
23
Functional Description
2.3
IOM®-2 Mode Functions
2.3.1
Basic IOM®-2 Frame Structure
The IOM-2 is a generalization and enhancement of the IOM-1. While the basic frame structure
is very similar, IOM-2 offers further capacity for the transfer of maintenance information. In
terminal applications, the IOM-2 constitutes a powerful backplane bus offering
intercommunication and sophisticated control capabilities for peripheral modules.
The channel structure of the IOM-2 is depicted in figure 10.
B1
B2
MONITOR
D
C/ Ι
M M
R X
ITD05672
Figure 10
Channel Structure of IOM®-2
● The 64-kbit/s channels, B1 and B2, are conveyed in the first two octets.
● The third octet (monitor channel) is used for transferring maintenance information between
the layer-1 functional blocks (SBCX, IECQ) and the layer-2 controller (see chapter 2.3.4).
● The fourth octet (control channel) contains
– two bits for the 16-kbit/s D channel
– four command/indication bits for controlling activation/deactivation and for additional control
functions
– two bits MR and MX for supporting the handling of the MONITOR channel.
Semiconductor Group
24
Functional Description
IOM®-2 TE Frame Structure
The frame is composed of three channels (figure 11):
● Channel 0 contains 144 kbit/s (for 2B+D) plus MONITOR and command/indication channels
for the layer-1 device.
● Channel 1 contains two 64-kbit/s intercommunication channels plus MONITOR and
command/indication channels for other IOM-2 devices.
● Channel 2 is used for IOM-bus arbitration (access to the TIC bus). Only the command/
indication bits are used in channel 2. See section 2.3.6 for details.
125 µs
FSC1
R
R
IOM -2 CH0
IPD0
(DD)
B1
B2
MON0 D CI0
MR
IPD1
(DU)
B1
B2
R
IOM -2 CH1
MON0 D CI0
MR
IC1
IC2
MON1
MX
IC1
IOM -2 CH2
CI1
MR
IC2
MX
MON1
MX
S/G
MX
BAC
A/B
CI1
MR
TAD
SDS1
ITD05413
Figure 11
Definition of IOM®-2 Channels in Terminal Timing Mode
The IOM-2 signals are:
IDP0, 1
DCL
FSC1
:
768 kbit/s
: 1536-kHz output
:
8-kHz output.
In addition, to support standard combos/data devices the following signals are generated as
outputs:
BCL
SDS1
: 768-kHz bit clock
:
8-kHz programmable data strobe signal for selecting one or both B/IC
channel(s).
Semiconductor Group
25
Functional Description
2.3.2
IOM®-2 Interface Connections
Output Driver Selection
The type of the IOM output is selectable via bit ODS (ADF2 register). Thus when inactive (not
transmitting) IDP0, 1 are either high impedance (ODS=1) or open drain "1" (ODS=0).
Normally the IOM-2 interface is operated in the "open drain" mode (ODS=0) in order to take
advantage of the bus capability. In this case pull-up resistors (1 kΩ – 5 kΩ) are required on
IDP0 and IDP1.
IOM® OFF Function
In IOM-2 terminal mode (SPCR:SPM=0) the IOM interface can be switched off for external
devices via IOF bit in ADF1 register. If IOF=1, the interface is switched off i.e. DCL, FSC1,
IDP0/1 and BCL are high impedance.
IOM® Direction Control
For test applications, the direction of IDP0(DD) and IDP1(DU) can be reversed during certain
time-slots within the IOM-2 frame. This is performed via the IDC bit in the SQXR register. For
normal operation SQXR:IDC should be set to "0".
Semiconductor Group
26
Functional Description
IOM® Data Ports in Terminal Mode
In this case the IOM has the 12-byte frame structure consisting of channels 0, 1 and 2 (see
figure 11):
– IDP0 carries the 2B+D channels from the S/T interface, and the MONITOR 0 and C/I 0
channels coming from the S/T controller;
– IDP1 carries the MONITOR 0 and C/I 0 channels to the layer-1.
Channel 1 of the IOM interface is used for internal communication in terminal applications. Two
cases have to be distinguished, according to whether the ISAC-S TE is operated as a master
device (communication with slave devices via MONITOR 1 and C/I 1), or as a slave device
(communication with one master via MONITOR 1 and C/I 1).
If IDC is set to "0" (master mode):
– IDP0 carries the MONITOR 1 and C/I 1 channels as output to peripheral (voice/data)
devices;
– IDP0 carries the IC channels as output to other devices, if programmed (C×C1 – 0 = 01 in
register SPCR).
If IDC is set to "1" (slave mode):
– IDP1 carries the MONITOR 1 and C/I 1 channels as output to a master device;
– IDP0 carries the IC channels as output to other devices, if programmed (C×C1 – 0 = 01 in
register SPCR).
If required (cf. DIM2-0, MODE register), bit 5 of the last byte in channel 2 on IDP0 is used to
indicate the S-bus state (stop/go bit) and bits 2 to 5 of the last byte are used for TIC-bus access
arbitration (see chapter 2.3.6).
Figure 12 shows the connection in a multifunctional terminal with the ISAC-S TE as a master
(figure 12b) and an ICC as a slave device.
Semiconductor Group
27
Functional Description
R
ISAC -S TE
S/T
Interface
R
IOM -2 Interface
Layer 1
(SBC)
IDP0 (DD)
IDP1 (DU)
IDP0
IDP1
DD
DU
MON1, C/I1, IC1, IC2
2B + D, C/I0, MON0, S/G, TIC
R
ISAC -S TE
in Master
Mode
(IDC = 0)
IDP0 IDP1
(DD) (DU)
IDP0 IDP1
Layer 2
(ICC)
Voice/Data
Module
ITS05414
Master
µC
Slave
Figure 12a
IOM® Data Ports 0, 1 in Terminal Mode (SPCR:SPM=0)
Semiconductor Group
28
e.g. PEB 2070
(ICC) in Slave
Mode (IDC = 1)
Functional Description
(a) Master Mode (IDC = 0)
CH0
CH1
MR
IPD0
(DD)
B1
B2
MON0 D CI0
R
S/T
IOM -2
Layer 1
Layer 2
MR
IPD1
(DU)
B1
R
IOM -2
B2
MON0 D CI0
S/T
Layer 2
Layer 1
CH2
MX
MR
IC1
IC2
MON1
IC Transmit
if Progr.
Layer 2
MX
CI1
R
IOM -2
MR
IC1
IC2
IC Receive
if Progr.
MON1
S/G A/B
MX
BAC TAD
MX
CI1
TIC-Bus
R
IOM -2
Layer 2
(b) Slave Mode (IDC = 1)
CH0
CH1
MR
IPD0
(DD)
B1
B2
MON0 D CI0
MR
IC1
IC2
MON1
MX
S/G A/B
CI1
R
S/T
IOM -2
Layer 1
B1
R
IOM -2
B2
MON0 D CI0
S/T
Layer 2
if Progr.
Layer 2
MR
IPD1
(DU)
CH2
MX
Layer 1
R
IOM -2
MX
IC1
MR
IC2
IC Transmit
if Progr.
Figure 12b
Semiconductor Group
Layer 2
29
MON1
MX
BAC TAD
CI1
TIC-Bus
Layer 2
R
IOM -2
ITD05415
Functional Description
µP Access to B and IC Channels
2.3.3
The microprocessor can access the B and IC (intercommunication) channels at the IOM-2
interface by reading the B1CR/B2CR or by reading and writing the C1R/C2R registers.
Furthermore it is possible to loop back the B channels from/to the S/T interface or to loop back
the IC channels from/to the IOM-2 interface without µP intervention.
These access and switching functions are selected with the channel connect bits (CxC1,
CxC0) in the SPCR register (table 2, figure 13).
External B-channel sources (voice/data modules) connected to the IOM-2 interface can be
disconnected with the IOM off function (ADF1:IOF) in order to not disturb the B-channel access
(see figure 13).
If the B-channel access is used for transferring 64-kbit/s voice/data information directly from
the µP port to the ISDN S/T interface, the access can be synchronized to the IOM interface by
means of a synchronous transfer interrupt programmed in the STCR register.
Table 2
Access to B/IC Channels (IOM®-2)
µP
C×C1
C×C0
C×R
C×R
B×CR
Read
Write Read
Output Applications
to
IOM-2
0
0
IC×
–
B×
–
B× monitoring, IC× monitoring
0
1
IC×
IC×
B×
IC×
B× monitoring, IC× looping from/to IOM-2
1
0
–
B×
B×
B×
B× access from/to S0;
transmission of a constant value in
B× channel to S0
1
1
B×
B×
–
B×
B× looping from S0;
transmission of a variable pattern in
B× channel to S0
Note: x=1 for channel 1 or 2 for channel 2
The general sequence of operations to access the B/IC channels is:
(set configuration register SPCR)
Program synchronous interrupt (ST0)
SIN – >
Read register (B×CR, C×R)
(write register)
Acknowledge SIN (SC0)
Semiconductor Group
30
Functional Description
R
ISAC -S TE
R
IOM -2 Interface
S/T Interface
IDP0 (DD)
IDP1 (DU)
Layer-1
Functions
Register: C1R/C2R
B1CR/B2CR SPCR
ADF1 : IOF
R
(IOM off)
µP Interface
ITS05416
Figure 13
Principle of B/IC-Channel Access
Semiconductor Group
31
Functional Description
R
IOM -2 Interface
S/T Interface
IDP0 (DD)
IDP1 (DU)
Layer-1
Functions
ICx
Bx
BxCR
CxR
µP
ITS05417
FSC
IDPO
(DD)
B1 B2
IC1 IC2
B1CR
B2CR
IDP1
(DU)
B1 B2
B1 B2
IC1 IC2
B1 B2
IC1 IC2
C2R
C1R
IC1 IC2
ITD05402
ST0
SC0 = 1
Figure 14
Access to B and IC Channels in IOM®-2 Terminal Mode
(a) SPCR:C×C1, C×C0 = 00
B× monitoring, IC× monitoring (SQXR:IDC=0)
Semiconductor Group
32
Functional Description
R
IOM -2 Interface
S/T Interface
IDP0 (DD)
IDP1 (DU)
Layer-1
Functions
Bx
ICx
BxCR
CxR
µP
ITS05418
FSC
IDPO
(DD)
B1 B2
IC1 IC2
B1CR
B2CR
IDP1
(DU)
B1 B2
B1 B2
IC1 IC2
B1 B2
IC1 IC2
C2R
C1R
IC1 IC2
ITD05403
ST0
SC0 = 1
(b) SPCR:C×C1, C×C0 = 01
B× monitoring, IC× looping (SQXR:IDC=0)
Semiconductor Group
33
Functional Description
R
IOM -2 Interface
S/T Interface
IDP0 (DD)
IDP1 (DU)
Layer-1
Functions
Bx
Bx
BxCR
CxR
µP
ITS05419
FSC
IDPO
(DD)
B1 B2
B1CR
IDP1
(DU)
IC1 IC2
B1 B2
IC1 IC2
B1 B2
IC1 IC2
C1R
B2CR
C2R
B1 B2
IC1 IC2
ITD05404
ST0
SC0 = 1
(c) SPCR:C×C1, C×C0 = 10
B× access from/to S/T
transmission of constant value to S/T
Semiconductor Group
34
Functional Description
R
IOM -2 Interface
S/T Interface
IDP0 (DD)
IDP1 (DU)
Layer-1
Functions
Bx
Bx
CxR
µP
ITS05420
FSC
IDPO
(DD)
B1 B2
IC1 IC2
B1 B2
IC1 IC2
IC1 IC2
B1 B2
IC1 IC2
B1CR
B2CR
IDP1
(DU)
B1 B2
ITD05405
ST0
SC0 = 1
(d) SPCR:C×C1, C×C0 = 11
B× looping from/to S/T
transmission of variable pattern to S/T
Semiconductor Group
35
Functional Description
2.3.4
MONITOR Channel Handling
In IOM-2 mode, the MONITOR channel protocol is a handshake protocol used for high speed
information exchange between the ISAC-S TE and other devices, in MONITOR channel "0" or
"1" (see figure 11). In the non-TE mode, only one MONITOR channel is available ("MONITOR
channel 0").
The MONITOR channel protocol is necessary:
● For programming and controlling devices attached to the IOM. Examples of such devices
are: layer-1 transceivers (using MONITOR channel 0), and peripheral V/D modules that do
not need a parallel microcontroller interface (MONITOR channel 1), such as the Audio
Ringing Codec Filter PSB 2165.
● For data exchange between two microcontroller systems attached to two different devices
on one IOM-2 backplane. Use of the MONITOR channel avoids the necessity of a dedicated
serial communication path between the two systems. This greatly simplifies the system
design of terminal equipment (figure 17).
Note: There is normally no necessity for monitor channel operations over "MONITOR
channel 0" since the internal layer-1 part of the ISAC-S TE does not support this
function. The implemented MONITOR handler can however be used with external
layer-1 transceivers in case only the ICC part of the ISAC-S TE is used (ADF1:TEM).
Semiconductor Group
36
Functional Description
R
IOM -2
Data Communication
(MONITOR1)
Control (MONITOR1)
V/D Module
V/D Module
R
ITAC PSB 2110
R
ARCOFI PSB 2160
R
ARCOFI -SP PSB 2165
µC
R
ISAC -S TE
PSB 2186
µC
ITS05421
Figure 15
Examples of MONITOR Channel Applications in IOM®-2 TE Mode
The MONITOR channel operates on an asynchronous basis. While data transfers on the bus
take place synchronized to frame sync, the flow of data is controlled by a handshake procedure
using the MONITOR Channel Receive (MR0 or 1) and MONITOR Channel Transmit (MX0 or
1) bits. For example: data is placed onto the MONITOR channel and the MX bit is activated.
This data will be transmitted repeatedly once per 8-kHz frame until the transfer is
acknowledged via the MR bit.
The microprocessor may either enforce a "1" (idle) in MR, MX by setting the control bit MRC1,
0 or MXC1, 0 to "0" (MONITOR Control Register MOCR), or enable the control of these bits
internally by the ISAC-S TE according to the MONITOR channel protocol. Thus, before a data
exchange can begin, the control bit MRC(1, 0) or MXC(1, 0) should be set to "1" by the
microprocessor.
The MONITOR channel protocol is illustrated in figure 16. Since the protocol is identical in
MONITOR channel 0 and MONITOR channel 1 (available in TE mode only), the index 0 or 1
has been left out in the illustration.
The relevant status bits are:
MONITOR Channel Data Received MDR (MDR0, MDR1)
MONITOR Channel End of Reception MER (MER0, MER1)
for the reception of MONITOR data, and
MONITOR Channel Data Acknowledged MDA (MDA0, MDA1)
MONITOR Channel Data Abort MAB (MAB0, MAB1)
for the transmission of MONITOR data (register: MOSR)
In addition, the status bit:
MONITOR Channel Active MAC (MAC0, MAC1)
indicates whether a transmission is in progress (register: STAR).
Semiconductor Group
37
Functional Description
µP
Transmitter
MON
MXE = 1
MOX = ADR
MXC = 1
MAC = 1
MDA Int.
MOX = DATA1
MDA Int.
MOX = DATA2
MDA Int.
MXC = 0
µP
Receiver
MX
MR
FF
FF
ADR
1
1
0
1
1
1
ADR
DATA1
DATA1
0
1
0
0
0
0
DATA1
DATA1
0
0
1
0
DATA2
DATA2
1
0
0
0
DATA2
DATA2
0
0
1
0
FF
FF
1
1
0
0
FF
FF
1
1
1
1
125 µ s
MDR Int.
RD MOR ( = ADR )
MRC = 1
MDR Int.
RD MOR ( = DATA1 )
MDR Int.
RD MOR ( = DATA2 )
MER Int.
MRC = 0
MAC = 0
ITD00870
Figure 16
MONITOR Channel Protocol (IOM®-2)
Semiconductor Group
38
Functional Description
Before starting a transmission, the microprocessor should verify that the transmitter is inactive,
i.e. that a possible previous transmission has been terminated. This is indicated by a "0" in the
MONITOR Channel Active MAC status bit.
After having written the MONITOR Data Transmit (MOX) register, the microprocessor sets the
MONITOR Transmit Control bit MXC to "1". This enables the MX bit to go active (0), indicating
the presence of valid MONITOR data (contents of MOX) in the corresponding frame. As a
result, the receiving device stores the MONITOR byte in its MONITOR Receive MOR register
and generates an MDR interrupt status.
Alerted by the MDR interrupt, the microprocessor reads the MONITOR Receive (MOR)
register. When it is ready to accept data (e.g. based on the value in MOR, which in a point-tomultipoint application might be the address of the destination device), it sets the MR control bit
MRC to "1" to enable the receiver to store succeeding MONITOR channel bytes and
acknowledge them according to the MONITOR channel protocol. In addition, it enables other
MONITOR channel interrupts by setting MONITOR Interrupt Enable to "1".
As a result, the first MONITOR byte is acknowledged by the receiving device setting the MR
bit to "0". This causes a MONITOR Data Acknowledge MDA-interrupt status at the transmitter.
A new MONITOR data byte can now be written by the microprocessor in MOX. The MX bit is
still in the active (0) state. The transmitter indicates a new byte in the MONITOR channel by
returning the MX bit active after sending it once in the inactive state. As a result, the receiver
stores the MONITOR byte in MOR and generates a new MDR-interrupt status. When the
microprocessor has read the MOR register, the receiver acknowledges the data by returning
the MR bit active after sending it once in the inactive state. This in turn causes the transmitter
to generate an MDA-interrupt status.
This "MDA interrupt – write data – MDR interrupt – read data – MDA interrupt" handshake is
repeated as long as the transmitter has data to send. Note that the MONITOR channel protocol
imposes no maximum reaction times to the microprocessor.
When the last byte has been acknowledged by the receiver (MDA-interrupt status), the
microprocessor sets the MONITOR Transmit Control bit MXC to "0". This enforces an inactive
("1") state in the MX bit. Two frames of MX inactive signifies the end of a message. Thus, a
MONITOR Channel End of Reception MER-interrupt status is generated by the receiver when
the MX bit is received in the inactive state in two consecutive frames. As a result, the
microprocessor sets the MR control bit MRC to 0, which in turn enforces an inactive state in
the MR bit. This marks the end of the transmission, making the MONITOR Channel Active
MAC bit return to "0".
During a transmission process, it is possible for the receiver to ask a transmission to be
aborted by sending an inactive MR bit value in two consecutive frames. This is effected by the
microprocessor writing the MR control bit MRC to "0". An aborted transmission is indicated by
a MONITOR Channel Data Abort MAB-interrupt status at the transmitter.
Semiconductor Group
39
Functional Description
2.3.5
C/I-Channel Handling
The command/indication channel carries real-time status information between the ISAC-S TE
and another device connected to the IOM.
1) One C/I channel (called C/I0) conveys the commands and indications between the layer-1
and the layer-2 parts of the ISAC-S TE. It can be accessed by an external layer-2 device
e.g. to control the layer-1 activation/deactivation procedures. C/I0 channel access may be
arbitrated via the TIC bus access protocol. In this case the arbitration is done in C/I
channel 2 (see figure 11).
The C/I0 channel is accessed via register CIR0 (in receive direction, layer-1 to layer-2) and
register CIX0 (in transmit direction, layer-2 to layer-1). The C/I0 code is four bits long.
A listing and explanation of the layer-1 C/I codes can be found in chapter 3.4.
In the receive direction, the code from layer-1 is continuously monitored, with an interrupt
being generated anytime a change occurs (ISTA:CISQ). A new code must be found in two
consecutive IOM frames to be considered valid and to trigger a C/I code change interrupt
status (double last look criterion).
In the transmit direction, the code written in CIX0 is continuously transmitted in C/I0.
2) A second C/I channel (called C/I1) can be used to convey real time status information
between the ISAC-S TE and various non-layer-1 peripheral devices e.g. PSB 2160
ARCOFI. The channel consists of six bits in each direction (see figure 11).
The C/I1 channel is accessed via registers CIR1 and CIX1. A change in the received C/I1
code is indicated by an interrupt status without double last look criterion.
Semiconductor Group
40
Functional Description
R
µP
IOM -2
ICC (7)
B-Channel
Voice/Data
Communication
with D-Channel
Signaling
ICC (1)
TIC-Bus
D-Channel
Telemetry/
Packet
Communication
B-Channel
Voice/Data
Communication
with D-Channel
Signaling
CCITT
S-Interface
R
ISAC -S TE
ITS05673
Figure 17
Applications of TIC Bus in IOM®-2 Bus Configuration
2.3.6
TIC-Bus Access
In IOM-2 interface mode the TIC-bus capability is only available in TE mode. The arbitration
mechanism implemented in the last octet of IOM channel 2 of the IOM allows the access of
external communication controllers (up to 7) to the layer-1 functions provided in the ISAC-S TE
and to the D channel. (TIC bus; see figure 17). To this effect the outputs of the controllers
(ICC:ISDN Communication Controller PEB 2070) are wired-or-and connected to pin IDP1. The
inputs of the ICCs are connected to pin IDP0. External pull-up resistors on IDP0/1 are required.
The arbitration mechanism must be activated by setting MODE:DIM2–0=001 (see
chapter 4.1.7).
An access request to the TIC bus may either be generated by software (µP access to the C/I
Semiconductor Group
41
Functional Description
channel) or by the ISAC-S TE itself (transmission of an HDLC frame). A software access
request to the bus is effected by setting the BAC bit (CIX0 register) to "1".
In the case of an access request, the ISAC-S TE checks the Bus Accessed-bit (bit 5 of IDP1
last octet of CH2, see figure 18) for the status "bus free", which is indicated by a logical "1". If
the bus is free, the ISAC-S TE transmits its individual TIC-bus address programmed in the
STCR register. The TIC bus is occupied by the device which sends its address error-free. If
more than one device attempt to seize the bus simultaneously, the one with the lowest address
values wins.
MR
MX
B1
B2
MON0 D CI0
IC1
MR
MX
IC2
MON1
CI1
BAC
TAD
2
1
TAD
BAC
ITD02575
0
TIC-Bus Address (TAD 2-0)
Bus Accessed (’1’ no TIC-Bus Access)
Figure 18
Structure of Last Octet of CH2 on IDP1 (DU)
When the TIC bus is seized by the ISAC-S TE, the bus is identified to other devices as
occupied via the IDP1 C/I Bus Accessed-bit state "0" until the access request is withdrawn.
After a successful bus access, the ISAC-S TE is automatically set into a lower priority class,
that is, a new bus access cannot be performed until the status "bus free" is indicated in two
successive frames.
If none of the devices connected to the IOM interface request access to the D- and C/I
channels, the TIC-bus address 7 will be present. The device with this address will therefore
have access, by default, to the D and C/I channels.
Note: Bit BAC (CIX0 register) should be reset by the µP when access to the C/I channels is
no more requested, to grant other devices access to the D- and C/I channels.
The availability of the S/T interface D channel is indicated in bit 5 "Stop/Go" (S/G) of the IDP0
last octet of C/I channel (figure 19).
S/G = 1 : stop
S/G = 0 : go
Semiconductor Group
42
Functional Description
MR
MX
B1
B2
MON0 D CI0
IC1
MR
MX
IC2
MON1
S/G
A/B
CI1
S/G A/B
STOP/GO
Available/Blocked
ITD05422
Figure 19
Structure of Last Octet of CH2 on IDP0 (DD)
The stop/go bit is available to other layer-2 devices connected to the IOM to determine if they
can access the S/T bus D channel.
The available busy bit is not influenced by the ISAC-S TE.
Semiconductor Group
43
Functional Description
2.4
Layer-1 Functions for the S/T Interface
– line transceiver functions for the S/T interface according to the electrical specifications of
CCITT I.430;
– conversion of the frame structure between IOM and S/T interface;
– conversion from/to binary to/from pseudo-ternary code;
– level detect;
– S/T-timing generation using IOM timing synchronous to system, or vice versa;
– D-channel access control and priority handling;
– activation/deactivation procedures, triggered by primitives received over the IOM C/I
channel or by INFO's received from the line;
– frame alignment;
– execution of test loops.
For a block diagram, see figure 8.
The wiring configurations in user premises, in which the ISAC-S TE can be used are illustrated
in figure 20.
Semiconductor Group
44
Functional Description
<_ 1.5 km 1)
R
ISAC -S TE
TR
TR
R
ISAC -S
LT-S
TE
<_ 1.5 km
1)
R
IOM -2
R
ISAC -S
TR
TR
Point-to-Point
Configurations
SBC
NT
LT-T
1)
R
The maximum line attenuation toleratet by the ISAC -S 15 dB at 96 kHz.
R
ISAC -S
LT-S
<_ 150 m
R
IOM -2
TR
TR
Short Passive
Bus
SBC
<_ 10 m
R
ISAC -S TE
TE1
NT
R
ISAC -S TE
TE8
R
ISAC -S
<_ 150 m
LT-S
<_ 35 m
R
IOM -2
TR
TR
<_ 10 m
Extended
Passive Bus
SBC
NT
TR:Terminating Resistor
R
ISAC -S TE
TE1
ITS05423
R
ISAC -S TE
TE8
Figure 20
Wiring Configurations in User Premises
Semiconductor Group
45
Functional Description
2.4.1
S/T Interface
According to CCITT recommendation I.430 pseudo-ternary encoding with 100% pulse width is
used on the S/T interface. A logical "1" corresponds to a neutral level (no current), whereas
logical "0" ’s are encoded as alternating positive and negative pulses. An example is shown in
figure 21.
0
1
0
0
1
1
0
0
0
1
1
+V
0V
-V
ITD00322
Figure 21
S/T-Interface Line Code
One frame consists of 48 bits, at a nominal bit rate of 192 kbit/s. Thus each frame carries two
octets of B1, two octets of B2, and four D bits, according to the B1+B2+D structure defined for
the ISDN-basic access (total useful data rate: 144 kbit/s). Frame begin is marked using a code
violation (no mark inversion). The frame structures (from network to subscriber, and subscriber
to network) are shown in figure 22.
48 Bits in 250 µs
DL. F L.
NT
B1
E D A FA N
B2
E DM
B1
EDS
B2
E D L. F L.
0
TE 1
0
2 Bits Offset
D L. F L.
TE
NT
0
1
0
B1
L. D L. FA L.
B2
L. D L.
B1
L. D L.
B2
L. D L. F L.
t
F = Framing Bit
L = DC Balancing Bit
D = D-Channel Bit
E = D-Echo-Channel Bit
FA = Auxiliary Framing Bit or Q-Bit
N = Bit set to a Binary Value N = FA
B1 = Bit within B Channel 1
B2 = Bit within B Channel 2
A = Bit used for Activation
S = Subchannel SC1 through SC5 bit position
M = Multiframing Bit
Figure 22
Frame Structure at Reference Points S and T (CCITT I.430)
Note: Dots demarcate those parts of the frame that are independently DC-balanced.
Semiconductor Group
46
ITD02330
Functional Description
2.4.2
Analog Functions
For both receive and transmit direction, a 2:1 transformer is used to connect the ISAC-S TE
transceiver to the 4 wire S/T interface. The corrections are shown in figure 23.
+5V
2:1
SX1
VDD
Transmit
Pair
ISAC-S TE
SX2
10 µF
PSB 2086
2186
PEB
VSSD
2:1
SR1
Receive
Pair
VSSA
SR2
GND
ITS05640
Figure 23
ISAC-S TE External S-Interface Circuitry
The full-bauded pseudo-ternary pulse shaping is achieved with the integrated transmitter
which is realized as a current limited voltage source. A voltage of 2.1 V is delivered between
SX1-SX2, which yields a current of 7.5 mA over 280 Ω.
The receiver is designed as a threshold detector with adaptively switched threshold levels. Pin
SR1 delivers 2.5 V as an output, which is the virtual ground of the input signal on pin SR2.
The external transformer of ratio 2:1 is needed in both receive and transmit direction to provide
for isolation and transform voltage levels according to CCITT recommendations.
The equivalent circuits of the integrated receiver and transmitter are shown in figure 24.
R
R
ISAC -S TE PSB 2186
ISAC -S TE PSB 2186
50 k Ω
40 k Ω
SX1
2.1 V
SR1
-
Ι ¾ 13.4 mA
+
40 k Ω
50 k Ω
SR2
SX2
2.1 V
2.5 V
ITS05940
ITS05939
switch position shown for negative pulses
Figure 24
Equivalent Internal Circuits of Receiver and Transmitter Stages
Semiconductor Group
47
Functional Description
Symmetrical S-Bus Receiver
The S-bus receiver of the PSB 2186 is a symmetrical one. This results in a simplification of the
external circuitry and PCB layout to meet the I.430 receiver input impedance specification.
2.4.3
S/T-Interface Circuitry
In order to comply to the physical requirements of CCITT recommendation I.430 and
considering the national requirements concerning overvoltage protection and electromagnetic
compatibility (EMC), the ISAC-S TE needs some additional circuitry.
Useful hints how to design such interface circuitry are contained on the Application Note “S/Tinterface circuitry using the PEB 2080 SBC or PEB 2085 ISAC-S (12/89)”.
The transmitter of the PSB 2186 ISAC-S TE is identical to that of both the PEB 2080 SBC and
PEB 2085/ISAC-S, hence, the line interface circuitry should be the same (figure 25). The
external resistors (20 … 40 Ω) are required in order to adjust the output voltage to the pulse
mask (nominal 750 mV according to CCITT I.430, to be tested with the command “SSZ”) on
the one hand and in order to meet the output impedance of minimum 20 Ω (transmission of a
binary zero according to CCITT I.430, to be tested with the command “SCZ“) on the other
hand.
20...40 Ω
2:1
SX1
2.7 V
R
ISAC -S TE
PSB 2186
GND
Overvoltage
Protection
VDD
S-Bus
Connector
20...40 Ω
SX2
DC Point
ITS04475
Figure 25
External Transmitter Circuitry
The receiver of the PSB 2186 ISAC-S TE is symmetrical as opposed to both PEB 2080 SBC
and PEB 2085 ISAC-S. Thus two resistors of 10 kΩ must be placed in series to the receiver
inputs.
In order to protect the ISAC-S inputs and comply to impedance requirements performed
without power supply (96-kHz test), the 10 kΩ tester is split-up.
A 1.8 kΩ resistor protects the device inputs, while the 8.2 kΩ resistors limit the maximum
current in impedance tests.
Semiconductor Group
48
Functional Description
8.2 k Ω
1.8 k Ω
2:1
SR1
47 pF
R
ISAC -S TE
PSB 2186
Overvoltage
Protection
VDD
GND
1.8 k Ω
S-Interface
Connector
8.2 k Ω
SR2
47 pF
DC Point
ITS04474
Figure 26
External Receiver Circuitry
2.4.4
S/T Interface Pre-Filter Compensation
To compensate for the extra delay introduced into the received signal by a filter, the sampling
of the receive signal can be delayed by programming bits TEM and PFS in the ADF1 register
as shown in table 3. Note that setting TEM to "1" and PFS to "0" has the effect of completely
disabling layer-1 functions, for test purposes (see section 2.6).
Table 3
TEM/PFS Function Table
TEM
PFS
Effect
0
0
No pre-filter (0 delay)
0
1
Pre-filter delay compensation 520 ns
1
1
Pre-filter delay compensation 910 ns
1
0
Test mode (layer-1 disabled)
This delay compensation might be necessary in order to comply with the "total phase deviation
input to output" requirement of CCITT recommendation I.430 which specifies a phase
deviation in the range of – 7% to + 15% of a bit period.
Semiconductor Group
49
Functional Description
2.4.5
Receiver Functions
2.4.5.1
Receive Signal Oversampling
In order to additionally reduce the bit error rate in severe conditions, the ISAC-S TE performs
oversampling of the received signal and uses majority decision logic.
As illustrated in figure 27, each received bit is sampled 29 times at 7.68-MHz clock intervals
inside the estimated bit window. The samples obtained are compared against a threshold
VTR1 or VTR2 (see section: Adaptive Receiver Characteristics).
If at least 16 samples have an amplitude exceeding the selected threshold, a logical "0" is
considered to be detected, otherwise a logical "1" (no signal) is considered detected.
VSR2 - VSR1
VTR1 or VTR2
0V
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
Derived 192-kHz Receive Bit Period
ITD02361
Figure 27
S/T-Receive Signal Oversampling
Semiconductor Group
50
Functional Description
2.4.5.2
Adaptive Receiver Characteristics
The integrated receiver uses an adaptively switched threshold detector. The detector controls
the switching of the receiver between two sensitivity levels. The hysteresis characteristics of
the receiver are shown in figure 28.
V SR2 - V SR1
V SR2 - V SR1
Logical 0
Logical 0
+ 375 mV
Logical 1
0V
Logical 0
- 375 mV
+ 225 mV
0V
Logical 1
- 225 mV
Logical 0
State 1
High Sensitivity
with V TR1 = ± 225 mV
State 2
Low Sensitivity
with V TR2 = ± 375 mV
V max > 1 V or V max < -1 V
in two Consecutive Frames
1
750 mV <_ V max <_ 1 V
2
V max < 750 mV and V max > -750 mV
V SR2 - V SR1 = Input Voltage
V TR1 V TR2 = Threshold Voltages of the Receiver Threshold Detector
V max = Maximum Value of V SR2 - V SR1 during one Frame
750 mV <_ V max <_ 1 V
ITD00774
Figure 28
Switching of the Receiver between High Sensitivity and Low Sensitivity
Semiconductor Group
51
Functional Description
2.4.5.3
Level Detection Power Down
In power down state, (see chapter 3.3.1) only an analog level detector is active. All clocks,
including the IOM interface, are stopped. The data lines are "high", whereas the clocks are
"low".
An activation initiated from the exchange side (Info 2 on S bus detected) will have the
consequence that a clock signal is provided automatically.
From the terminal side an activation must be started by setting and resetting the SPU bit in the
SPCR register (see chapter 4).
2.4.6
Timing Recovery
The transmit and receive bit clocks are derived, with the help of the DPLL, from the S-interface
receive data stream. The received signal is sampled several times inside the derived receive
clock period, and a majority logic is used to additionally reduce bit error rate in severe
conditions (see chapter 2.4.5). The transmit frame is shifted by two bits with respect to the
received frame.
The output clocks (DCL, FSC1 etc.) are synchronous to the S-interface timing.
TE Mode
BCL
DCL
PLL
FSC
ITS05425
Figure 29
Clock System of the ISAC®-S TE in TE Mode
Semiconductor Group
52
Functional Description
2.4.7
Activation/Deactivation
An incorporated finite state machine controls ISDN layer-1 activation/deactivation according to
CCITT (see chapter 3.4).
Loss of Synchronization / Resynchronization
The following section describes the behaviour of the PSB 2186 in respect to the CTS test
procedures for frame alignment.
Setting of the ISAC-S TE
The ISAC-S TE needs to be programmed for multiframe operation with the Q-bits set to ’1’.
STAR2: MULT = 0
SQXR:SQX1-4 = 1111B (xFH)
2.4.7.1
FAinfA_1fr
This test checks if no loss of frame alignment occurs upon a receipt of one bad frame. The
pattern for the bad frame is defined as IX_96 kHz. This pattern was revised so that a code
violation is generated at the begin of the next info 4 frame.
Code Violation
Info 4
Info 4
Info 4
IX_96 kHz
Info 3
Info 3
Info 3
Info 3
ITD05898
Device
Settings
Result
PSB 2186 V1.1
none
Pass
Semiconductor Group
53
Comments
Functional Description
2.4.7.2
FAinfB_1fr
This test uses a frame which has no framing and balancing bit.
Code Violation
Info 4
Info 4
Info 4
I4_BASIC
IX_I4noflag
Info 3
Info 3
Info 3
Info 3
ITD05899
Device
Settings
Result
PSB 2186 V1.1
none
Pass
2.4.7.3
Comments
FAinfD_1fr
This test uses a frame which remains at binary ’1’ until the first code violation in bit 16. Since
it is specified, that a terminal should mirror the received FA-bit in the transmitted FA-bit, a frame
is generated by the IUT which will not generate a second code violation. The pattern for a
correct i3_BASIC frame states that the FA-bit may have any value.
Info 4
Info 4
Info 4
FA = 1
Info 3
Info 3
Info 3
Info 3 with FA = 1
Device
Settings
Result
PSB 2186 V1.1
none
Pass
Semiconductor Group
54
ITD05900
Comments
Functional Description
2.4.7.4
FAinfA_kfr
This test uses a number of IX_96 kHz frames to check the loss of synchronization.
Info 4
Info 4
IX_96 kHz
Info 3
Info 3
IX_96 kHz
IX_96 kHz
Info 3
I3_SFAL
Info 0
ITD05901
Device
Settings
Result
PSB 2186 V1.1
n=2
Pass
2.4.7.5
Comments
FAinfB_kfr
This test uses a number of IX_I4noflag frames to check the loss of synchronization.
Info 4
Info 4
I4_BASIC
IX_I4noflag
Info 3
Info 3
Info 3
IX_I4noflag
I3_SFAL
IX_I4noflag
Info 0
ITD05902
Device
Settings
Result
PSB 2186 V1.1
n=2
Pass
Semiconductor Group
55
Comments
Functional Description
2.4.7.6
FAinfD_kfr
This test uses a number of IX_I4voil16 frames to check the loss of synchronization. The first
Info 3 frame with the FA-bit set to one looks like a i3_SFAL frame but it is a correct info 3 frame
since the receiver stays synchronous (see FAinfD_1fr).
Info 4
Info 4
Info 3
FA = 1
FA = 1
Info 3 with FA = 1
I3_SFAL
Info 3
ITD05903
Device
Settings
Result
PSB 2186 V1.1
n=2
Pass
2.4.7.7
Comments
FAregain
This test uses I4_BASIC frames to regain the frame alignment. The protocol tester evaluates
the difference between sending the first info 4 frame until a complete info 3 frame has been
received. This period is considered as ’m+1’. ’m’ must be specified before the test is started.
The PSB 2186 achieves synchronization after 5 or 6 frames. The actual value depends on
internal timing conditions which can not be influenced from extern. This is a result of changes
that were made to handle the iXvoil16 test case correctly. The info 4 pattern generates the
second code violation at the position of the F A-bit. Around that bit position, the state machine
changes its states. As a result of that overlap, the info 3 frame is transmitted after 5 frames or
one frame later.
Info X
1
2
3
4
5
6
7
Info 4
Info 4
Info 4
Info 4
Info 4
Info 4
Info 4
Info 3
Info 3
ITD05904
Device
Settings
Result
PSB 2186 V1.1
m = 5 or 6
Pass
Semiconductor Group
56
Comments
Functional Description
2.4.8
D-Channel Access
The D channel is submitted to the D-channel access procedure according to CCITT
recommendation I.430.
The D-channel access procedure according to CCITT I.430 including priority management is
fully implemented in the ISAC-S:
If collision detection is programmed (MODE:DIM2-0), a collision is detected if either an echo
bit of "0" is recognized and a D bit of "1" was generated, or an echo bit of "1" is recognized and
a D bit of "0" was generated. When this occurs, D-channel transmission is immediately
stopped, and the echo channel is monitored to enable a subsequent D-channel access to be
attempted.
Stop/Go Bit
As the collision resolution is performed by the layer-1 part of the device, an information about
the D-channel status ("ready" or "busy") must be sent back to the layer-2 part to control HDLC
transmission. For this goal a Stop/Go (S/G) bit is transmitted over the IOM interface to the
layer-2 device.
The S/G bit is transmitted in bit 90 of an IOM-2 frame (12-byte structure) (see figure 19).
A logical "1" of the S/G bit indicates a collision on the S bus. By sending the S/G bit a logical
"0" to the layer-2 controller in anticipation of the S bus D channel "ready"-state, the first valid
0 bits will emerge from the layer-1 part at exactly that moment an access is becoming possible.
Selection of D-Channel Access Mode
For proper operation of the D-channel access procedure, the ISAC-S TE must be programmed
via the MODE (see chapter 4.1.7) register to evaluate the stop/go bit. This is achieved by
setting MODE:DIM2-0 to 001 or 011.
Selection of the Priority Class
The priority class (priority 8 or priority 10) is selected by transferring the appropriate activation
command via the Command/Indicate (C/I) channel of the IOM interface to the layer-1
controller. If the activation of the S interface is initiated by a TE, the priority class is selected
implicitly by the choice of the activation command. If the S-Interface is activated from the NT,
an activation command selecting the desired priority class should be programmed at the TE
on reception of the activation indication (AI8). In the activated state, the priority class may be
changed whenever required simply by programming the respective activation request
command (AR8 or AR10). The following table summarizes the C/I codes used for setting the
priority classes:
Semiconductor Group
57
Functional Description
Table 4
Priority Commands/Indications
Command (upstream)
Abbr.
Code
Remarks
Activate request, set priority 8
AR8
1000
Activate request, set priority 10
AR10
1001
Activation command: Set D-channel
priority to 8
Activation command: Set D-channel
priority to 10
Indication (downstream)
Abbr.
Code
Remarks
Activate indication with priority
class 8
Activate indication with priority
class 10
AI8
1100
AI10
1101
Info 4 received: D-channel priority is 8
or 9
Info 4 received: D-channel priority is
10 or 11
2.4.9
S- and Q-Channel Access
Access to the received/transmitted S- or Q channel is provided via registers. As specified by
CCITT I.430, the Q bit is transmitted from TE to NT in the position normally occupied by the
auxiliary framing bit (FA) in one frame out of 5, whereas the S bit is transmitted from NT to TE
in a spare bit, see figure 22.
The functions provided by the ISAC-S are:
– Synchronization to the received 20 frame multiframe by means of the received M bit pattern.
Synchronism is achieved when the M bit has been correctly received during 20 consecutive
frames starting from frame number 1 (table 5).
– When synchronism is achieved, the four received S bits in frames 1, 6, 11 and 16 are stored
as SQR1 to SQR4 in the SQRR register if the complete M bit multiframe pattern was
correctly received in the corresponding multiframe. A change in any of the received four bits
(SQR1, 2, 3 or 4) is indicated by an interrupt (CISQ in ISTA and SQC in CIR0).
– When an M bit is observed to have a value different from that expected, the synchronism is
considered lost. The SQR bits are not updated until synchronism is regained. The
synchronization state is constantly indicated by the SYN bit in the SQRR register.
– When synchronism with the received multiframe is achieved, the four bits SQX1 to SQX4
stored in the SQXR register are transmitted as the four Q bits (FA-bit position) in frames 1,
6, 11 and 16 respectively (starting from frame number one). Otherwise the bit transmitted is
a mirror of the received FA-bit. At loss of synchronism (mismatch in M bit) the mirroring is
resumed starting with the next FA-bit.
– The S/T multiframe synchronization can be disabled in the STAR2 register (MULT bit).
Semiconductor Group
58
Functional Description
Table 5
S- and Q-Bit Position Identification and Multiframe Structure
S- and Q-Channel Structure
Frame Number
NT-to-TE
FA-Bit
Position
NT-to-TE
M Bit
NT-to-TE
S Bit
TE-to-NT
FA-Bit
Position
1
2
3
4
5
ONE
ZERO
ZERO
ZERO
ZERO
ONE
ZERO
ZERO
ZERO
ZERO
S1
ZERO
ZERO
ZERO
ZERO
Q1
ZERO
ZERO
ZERO
ZERO
6
7
8
9
10
ONE
ZERO
ZERO
ZERO
ZERO
ZERO
ZERO
ZERO
ZERO
ZERO
S2
ZERO
ZERO
ZERO
ZERO
Q2
ZERO
ZERO
ZERO
ZERO
11
12
13
14
15
ONE
ZERO
ZERO
ZERO
ZERO
ZERO
ZERO
ZERO
ZERO
ZERO
S3
ZERO
ZERO
ZERO
ZERO
Q3
ZERO
ZERO
ZERO
ZERO
16
17
18
19
20
ONE
ZERO
ZERO
ZERO
ZERO
ZERO
ZERO
ZERO
ZERO
ZERO
S4
ZERO
ZERO
ZERO
ZERO
Q4
ZERO
ZERO
ZERO
ZERO
1
2
etc.
ONE
ZERO
ONE
ZERO
S1
ZERO
Q1
ZERO
Semiconductor Group
59
Functional Description
2.5
Terminal Specific Functions
Watchdog and External Awake
In addition to the ISAC-S TE standard functions supporting the ISDN-basic access, the
ISAC-S TE contains optional functions, useful in various terminal configurations.
The terminal specific functions are enabled by setting bit TSF (STCR register) to "1". This has
two effects:
The EAW line is defined as an external awake input;
Second, the interrupts SAW and WOV (EXIR register) are enabled:
●
SAW (Subscriber Awake) generated by a falling edge on the EAW line
●
WOV (Watchdog timer OVerflow) generated by the watchdog timer. This occurs when the
processor fails to write two consecutive bit patterns in ADF1:
ADF1
WTC1
WTC2
Watchdog Timer Control 1, 0.
The WTC1 and WTC2 bits have to be successively written in the following manner within
128 ms:
1.
2.
WTC1
WTC2
1
0
0
1
As a result the watchdog timer is reset and restarted. Otherwise a WOV is generated.
Deactivating the terminal specific functions is only possible with a hardware reset.
Having enabled the terminal specific functions via TSF=1, the user can make the ISAC-S TE
generate a reset signal by programming the Reset Source Select RSS bit (CIXR/CIX0
register), as follows:
0 →A reset signal is generated as a result of
– a falling edge on the EAW line (subscriber awake)
– a C/I code change (exchange awake)
A falling edge on the EAW line also forces the IDP1 line of the IOM interface to zero.
The consequence of this is that the IOM interface and the ISAC-S TE leaves the
power-down state.
A corresponding interrupt status (CISQ or SAW) is also generated.
1 →A reset signal is generated as a result of the expiration of the watchdog timer
(indicated by the WOV interrupt status).
Note that the watchdog timer is not running when the ISAC-S TE is in the power-down
state (IOM not clocked).
Note: Bit RSS has a significance only if terminal specific functions are activated (TSF=1).
Semiconductor Group
60
Functional Description
The RSS bit should be set to "1" by the user when the ISAC-S TE is in power-up to prevent an
edge on the EAW line or a change in the C/I code from generating a reset pulse.
Switching RSS from 0 to 1 or from 1 to 0 resets the watchdog timer.
The reset pulse generated by the ISAC-S TE (output via RST pin) has a pulse width of:
– 125 µs when generated by the watchdog timer
– 16 ms when generated by EAW line or C/I-code change.
Semiconductor Group
61
Functional Description
2.6
Test Functions
The ISAC-S TE provides several test and diagnostic functions which can be grouped as
follows:
●
digital loop via TLP (Test Loop, SPCR register) command bit: IDP1 is internally connected
with IDP0, output from layer 1 (S/T) on IDP0 is ignored; this is used for testing ISAC-S TE
functionality excluding layer 1;
●
test of layer-2 functions while disabling all layer-1 functions and pins associated with them
(including clocking, in TE mode), via bit TEM (Test Mode in ADF1 register); the ISAC-S TE
is then fully compatible to the ICC (PEB 2070) seen at the IOM interface.
●
loop at the analog end of the S interface;
Test loop 3 is activated with the C/I-channel command Activate Request Loop (ARL). An S
interface is not required since INFO3 is looped back to the receiver. When the receiver has
synchronized itself to this signal, the message "Test Indication" (or "Awake Test Indication") is
delivered in the C/I channel. No signal is transmitted over the S interface.
In the test loop mode the S-Interface awake detector is enabled i.e. if a level is detected (e.g.
Info 2/Info 4) this will be reported by the Awake Test Indication (ATI). The loop function is not
effected by this condition and the internally generated 192-kHz line clock does not depend on
the signal received at the S interface.
Semiconductor Group
62
Functional Description
2.7
Layer-2 Functions for the ISDN-Basic Access
LAPD, layer 2 of the D-channel protocol (CCITT I.441) includes functions for:
– Provision of one or more data link connections on a D channel (multiple LAP).
Discrimination between the data link connections is performed by means of a data link
connection identifier (DLCI = SAPI + TEI)
– HDLC framing
– Application of a balanced class of procedure in point-multipoint configuration.
The simplified block diagram in figure 30 shows the functional blocks of the ISAC-S TE which
support the LAPD protocol.
Layer 1
IOM
HDLC
Receiver
HDLC
Transmitter
R
Layer-1
Functions
LAPD
Controller
S(D-Channel)
Status
Command
Registers
Layer 2
R-FIFO
2 x 32 byte
X-FIFO
2 x 32 byte
FIFO
Controller
µP-Interface
Upper
Layers
µC-System
ITS00861
Figure 30
D-Channel Processing of the ISAC®-S TE
For the support of LAPD the ISAC-S TE contains an HDLC transceiver which is responsible
for flag generation/recognition, bit stuffing mechanism, CRC check and address recognition.
A powerful FIFO structure with two 64-byte pools for transmit and receive directions and an
intelligent FIFO controller permit flexible transfer of protocol data units to and from the µC
system.
Semiconductor Group
63
Functional Description
2.7.1
Message Transfer Modes
The HDLC controller can be programmed to operate in various modes, which are different in
the treatment of the HDLC frame in the receive direction. Thus, the receive data flow and the
address recognition features can be programmed in a flexible way, which satisfies different
system requirements.
In the auto mode the ISAC-S TE handles elements of procedure of the LAPD (S and I frames)
according to CCITT I.441 fully autonomously.
For the address recognition the ISAC-S TE contains four programmable registers for individual
SAPI and TEI values SAP1-2 and TEI1-2, plus two fixed values for "group" SAPI and TEI,
SAPG and TEIG.
There are 5 different operating modes which can be set via the MODE register (addr. 22 H):
Auto-mode (MDS2, MDS1 = 00)
Characteristics:
– Full address recognition (1 or 2 bytes).
– Normal (mod 8) or extended (mod 128) control field format
– Automatic processing of numbered frames of an HDLC procedure (see 2.7.5)
If a 2-byte address field is selected, the high address byte is compared with the fixed value
FEH or FCH (group address) as well as with two individually programmable values in SAP1
and SAP2 registers. According to the ISDN LAPD protocol, bit 1 of the high byte address will
be interpreted as command/response bit (C/R) dependent on the setting of the CRI bit in
SAP1, and will be excluded from the address comparison.
Similarly, the low address byte is compared with the fixed value FFH (group TEI) and two
compare values programmed in special registers (TEI1, TEI2). A valid address will be
recognized in case the high and low byte of the address field match one of the compare values.
The ISAC-S TE can be called (addressed) with the following address combinations:
– SAP1/TEI1
– SAP1/FFH
– SAP2/TEI2
– SAP2/FFH
– FEH (FCH)/TEI1
– FEH (FCH)/TEI2
– FEH (FCH)/FFH
Only the logical connection identified through the address combination SAP1, TEI1 will be
processed in the auto mode, all others are handled as in the non-auto mode. The logical
connection handled in the auto-mode must have a window size 1 between transmitted and
acknowledged frames. HDLC frames with address fields that do not match with any of the
address combinations, are ignored by the ISAC-S TE.
Semiconductor Group
64
Functional Description
In case of a 1-byte address, TEI1 and TEI2 will be used as compare registers. According to
the X.25 LAPB protocol, the value in TEI1 will be interpreted as command and the value in
TEI2 as response.
The control field is stored in the RHCR register and the I field in the RFIFO. Additional
information is available in the RSTA.
Non-auto mode (MDS2, MDS1 = 01)
Characteristics:Full address recognition (1 or 2 bytes)
Arbitrary window sizes
All frames with valid addresses (address recognition identical to auto mode) are accepted and
the bytes following the address are transferred to the µP via RHCR and RFIFO. Additional
information is available in the RSTA.
Transparent mode 1 (MDS2, MDS1, MDS0 = 101)
Characteristics: TEI recognition
A comparison is performed only on the second byte after the opening flag, with TEI1, TEI2 and
group TEI (FFH). In the case of a match, the first address byte is stored in SAPR, the (first byte
of the) control field in RHCR, and the rest of the frame in the RFIFO. Additional information is
available in the RSTA.
Transparent mode 2 (MDS2, MDS1, MDS0 = 110)
Characteristics: no address recognition
Every received frame is stored in the RFIFO (first byte after opening flag to CRC field).
Additional information can be read from the RSTA.
Transparent mode 3 (MDS2, MDS1, MDS0 = 111)
Characteristics: SAPI recognition
A comparison is performed on the first byte after the opening flag with SAP1, SAP2 and group
SAPI (FE/FCH). In the case of a match, all the following bytes are stored in RFIFO. Additional
information can be read from the RSTA.
Semiconductor Group
65
Functional Description
2.7.2
Protocol Operations (auto-mode)
In addition to address recognition all S and I frames are processed in hardware in the automode. The following functions are performed:
– update of transmit and receive counter
– evaluation of transmit and receive counter
– processing of S commands
– flow control with RR/RNR
– response generation
– recognition of protocol errors
– transmission of S commands, if an acknowledgement is not received
– continuous status query of remote station after RNR has been received
– programmable timer/repeater functions.
The processing of frames in auto-mode is described in detail in chapter 2.7.5:
Documentation of the Auto-Mode.
Semiconductor Group
66
Functional Description
2.7.3
Reception of Frames
A 2 × 32 byte FIFO buffer (receive pools) is provided in the receive direction.
The control of the data transfer between the CPU and the ISAC-S TE is handled via interrupts.
There are two different interrupt indications concerned with the reception of data:
– RPF (Receive Pool Full) interrupt, indicating that a 32-byte block of data can be read from
the RFIFO and the received message is not yet complete.
– RME (Receive Message End) interrupt, indicating that the reception of one message is
completed, i.e. either
●
one message ≤ 32 bytes, or
●
the last part of a message > 32 bytes
is stored in the RFIFO.
Depending on the message transfer mode the address and control fields of received frames
are processed and stored in the Receive FIFO or in special registers as depicted in figure 32.
The organization of the RFIFO is such that up to two short (≤ 32 bytes), successive messages,
with all additional information can be stored. The contents of the RFIFO would be, for example,
as shown in figure 31.
RFIFO
Interrupts in
Wait Line
0
Receive
Message 1
( <_ 32 bytes)
31
0
RME
Receive
Message 2
( <_ 32 bytes)
RME
31
ITS01502
Figure 31
Contents of RFIFO (short message)
Semiconductor Group
67
Functional Description
Flag
Auto-Mode
(U-and
Ι-Frames)
-
Non-Auto
Mode
Transparent
Mode 1
Address
High
Address
Low
Control
Information
CRC
SAP1,SAP2
FE,FC
TEI1,TEI2
FF
RHCR
RFIFO
RSTA
(Note 1)
(Note 2)
(Note 3)
SAP1,SAP2
FE,FC
TEI1,TEI2
FF
RHCR
RFIFO
RSTA
(Note 1)
(Note 2)
(Note 4)
SAPR
TEI1,TEI2
FF
RHCR
RFIFO
RSTA
Flag
(Note 4)
Transparent
Mode 2
SAP1,SAP2
FE,FC
Transparent
Mode 3
RFIFO
RSTA
RFIFO
RSTA
Description of Symbols:
ITD05674
R
Checked automatically by ISAC -S TE
Compared with Register or Fixed Value
Stored Info Register or RFIFO
Figure 32
Receive Data Flow
Note 1Only if a 2-byte address field is defined (MDS0 = 1 in MODE register).
Note 2Comparison with Group TEI (FFH) is only made if a 2-byte address field is defined
(MDS0 = 1 in MODE register).
Note 3In the case of an extended, modulo 128 control field format (MCS = 1 in SAP2 register)
the control field is stored in the RHCR in compressed form (I frames).
Note 4In the case of extended control field, only the first byte is stored in the RHCR, the second in the RFIFO.
Semiconductor Group
68
Functional Description
When 32 bytes of a message longer than that are stored in the RFIFO, the CPU is prompted
to read out the data by an RPF interrupt. The CPU must handle this interrupt before more than
32 additional bytes are received, which would cause a "data overflow".This corresponds to a
maximum CPU reaction time of 16 ms (data rate 16 kbit/s).
After a remaining block of less than or equal to 16 bytes has been stored, it is possible to store
the first 16 bytes of a new message (see figure 33).
The internal memory is now full. The arrival of additional bytes will result in "data overflow"
(RSTA:RDO) and a third new message in "frame overflow" (EXIR:RFO).
The generated interrupts are inserted together with all additional information into a queue to
be individually passed to the CPU.
After an RPF or RME interrupt has been processed, i.e. the received data has been read from
the RFIFO, this must be explicitly acknowledged by the CPU issuing an RMC (Receive
Message Complete) command.
The ISAC-S TE can then release the associated FIFO pool for new data. If there is an
additional interrupt in the queue it will be generated after the RMC acknowledgement.
RFIFO
the Queue
Interrupts in
RFIFO
0
Interrupts in
the Queue
0
Long
Message 1
( <_ 46 bytes)
Long
Message
31
0
RPF
31
0
RPF
15
16
RME
Message 2
( <_ 32 bytes)
31
31
RPF
RME
ITS01501
Figure 33
Contents of the RFIFO (long messages)
Semiconductor Group
69
Functional Description
Information about the received frame is available for the µP when a RME interrupt is generated,
as shown in table 6.
Table 6
Receive Information at RME Interrupt
Information
Register (adr. Bit
hex)
Mode
First byte after flag
(SAPI of LAPD
address field)
SAPR
(26)
Transparent mode 1
Control field
RHCR
(29) –
Auto-mode, I (modulo 8) and U frames
Compressed control field
RHCR
(29)
–
Auto-mode, I frames (modulo 128)
2nd byte after flag
RHCR
(29)
–
Non-auto mode, 1-byte address field
3rd byte after flag
RHCR
(29)
–
Non-auto mode, 2-byte address field
Transparent mode 1
Type of frame
(Command/Response)
RSTA
(27)
C/R
Auto-mode, 2 byte address field
Non-auto mode, 2-byte address field
Transparent mode 3
Recognition of SAPI
RSTA
(27)
SA1-0
Auto-mode, 2 byte address field
Non-auto mode, 2-byte address field
Transparent mode 3
Recognition of TEI
RSTA
(27)
TA
All except transparent modes 2, 3
Result of CRC check
(correct/incorrect)
RSTA
(27)
CRC
ALL
Data available in RFIFO
(yes/no)
RSTA
(27)
RDA
ALL
Abort condition detected
(yes/no)
RSTA
(27)
RAB
ALL
Data overflow during
reception of a frame
(yes/no)
RSTA
(27)
RDO
ALL
Number of bytes received RBCL
in RFIFO
(25)
RBC4-0
ALL
Message length
(25) RBC11-0 ALL
(2A) OV
Semiconductor Group
RBCL
RBCH
–
70
Functional Description
2.7.4
Transmission of Frames
A 2 × 32 byte FIFO buffer (transmit pools) is provided in the transmit direction.
If the transmit pool is ready (which is true after an XPR interrupt or if the XFW bit in STAR is
set), the CPU can write a data block of up to 32 bytes to the transmit FIFO. After this, data
transmission can be initiated by command.
Two different frames types can be transmitted:
– Transparent frame (command: XTF), or
– I frames (command: XIF)
as shown in figure 34.
For transparent frames, the whole frame including address and control field must be written to
the XFIFO.
HDLC Frame
Flag
Address
Control
Information
CRC
Flag
Transmit I-Frame
(XIF)
Auto Mode,8 - Bit Addr.
Flag
XAD1
Control
XFIFO
CRC
Flag
Transmit I-Frame
(XIF)
Auto -Mode, 16 - Bit Addr.
Flag
XAD1 XAD2
Control
XFIFO
CRC
Flag
Transmit Transparent
Frame (XTF)
All Modes
Flag
CRC
Flag
XFIFO
ITD05667
Note: Length of Control Field is b or 16 Bit
Description of Symbols:
R
Generated automatically by ISAC -S TE
Written initially by CPU (Info Register)
R
Loaded (repeatedly) by CPU upon ISAC -S TE
request (XPR Interrupt)
Figure 34
Transmitter Data Flow
The transmission of I frames is possible only if the ISAC-S TE is operating in the auto-mode.
The address and control field is autonomously generated by the ISAC-S TE and appended to
the frame, only the data in the information field must be written to the XFIFO.
Semiconductor Group
71
Functional Description
If a 2-byte address field has been selected, the ISAC-S TE takes the contents of the XAD 1
register to build the high byte of the address field, and the contents of the XAD 2 register to
build the low byte of the address field.
Additionally the C/R bit (bit 1 of the high byte address, as defined by LAPD protocol) is set to
"1" or "0" dependent on whether the frame is a command or a response.
In the case of a 1 byte address, the ISAC-S TE takes either the XAD 1 or XAD 2 register to
differentiate between command or response frame (as defined by X.25 LAPB).
The control field is also generated by the ISAC-S TE including the receive and send sequence
number and the poll/final (P/F) bit. For this purpose, the ISAC-S TE internally manages send
and receive sequence number counters.
In the auto-mode, S frames are sent autonomously by the ISAC-S TE. The transmission of U
frames, however, must be done by the CPU. U frames must be sent as transparent frames
(CMDR:XTF), i.e. address and control field must be defined by the CPU.
Once the data transmission has been initiated by command (CMDR:XTF or XIF), the data
transfer between CPU and the ISAC-S TE is controlled by interrupts.
The ISAC-S TE repeatedly requests another data packet or block by means of an ISTA:XPR
interrupt, every time no more than 32 bytes are stored in the XFIFO.
The processor can then write further data to the XFIFO and enable the continuation of frame
transmission by issuing an XIF/XTF command.
If the data block which has been written last to the XFIFO completes the current frame, this
must be indicated additionally by setting the XME (Transmit Message End) command bit. The
ISAC-S TE then terminates the frame properly by appending the CRC and closing flag.
If the CPU fails to respond to an XPR interrupt within the given reaction time, a data underrun
condition occurs (XFIFO holds no further valid data). In this case, the ISAC-S TE automatically
aborts the current frame by sending seven consecutive "ones" (ABORT sequence).
The CPU is informed about this via an XDU (Transmit Data Underrun) interrupt.
It is also possible to abort a message by software by issuing a CMDR:XRES (Transmitter
RESet) command, which causes an XPR interrupt.
After an end of message indication from the CPU (CMDR:XME command), the termination of
the transmission operation is indicated differently, depending on the selected message
transfer mode and the transmitted frame type.
If the ISAC-S TE is operating in the auto mode, the window size (= number of outstanding
unacknowledged frames) is limited to "1"; therefore an acknowledgement is expected for every
I frame sent with an XIF command. The acknowledgement may be provided either by a
received S or I frame with corresponding receive sequence number.
If no acknowledgement is received within a certain time (programmable), the ISAC-S TE
requests an acknowledgement by sending an S frame with the poll bit set (P = 1) (RR or RNR).
If no response is received again, this process is repeated in total N2 times (retry count,
programmable via TIMR register).
Semiconductor Group
72
Functional Description
The termination of the transmission operation may be indicated either with:
– XPR interrupt, if a positive acknowledgement has been received,
– XMR interrupt, if a negative acknowledgement has been received, i.e. the transmitted
message must be repeated (XMR = Transmit Message Repeat),
– TIN interrupt, if no acknowledgement has been received at all after N2 times the expiration
of the time period t1 (TIN = Timer INterrupt, XPR interrupt is issued additionally).
Note: Prerequisite for sending I frames in the auto-mode (XIF) is that the internal operational
mode of the timer has been selected in the MODE register (TMD bit = 1).
The transparent transmission of frames (XTF command) is possible in all message transfer
modes. The successful termination of a transparent transmission is indicated by an XPR
interrupt.
In all cases, collisions which occur on the S-Bus (D channel) before the first XFIFO pool has
been completely transmitted and released are treated without µP interaction. The ISAC-S TE
will retransmit the frame automatically.
If a collision is detected after the first pool has been released, the ISAC-S TE aborts the frame
and requests the processor to repeat the frame with an XMR interrupt.
Semiconductor Group
73
Functional Description
2.7.5
Documentation of the Auto Mode
The auto mode of the ICC and ISAC-S TE is only applicable for the states 7 and 8 of the LAPD
protocol. All other states (1 to 6) have to be performed in Non-Auto Mode (NAM). Therefore
this documentation gives an overview of how the device reacts in the states 7 and 8, which
reactions require software programming and which are done by the hardware itself, when
interrupts and status register contents are set or change. The necessary software actions are
also detailed in terms of command or mode register access.
The description is based on the SDL diagrams of the ETSI TS 46-20 dated 1989.
The diagrams are only annotated by documentary signs or texts (mostly register descriptions)
and can therefore easily be interpreted by anyone familiar with the SDL description of LAPD.
All deviations that occur are specially marked and the impossible actions, paths etc. are
crossed out.
To get acquainted with this documentation, first read through the legend-description and the
additional general considerations, then start with the diagrams, referring to the legend and the
register description in the Technical Manual if necessary.
We hope you will profit from this documentation and use our software-saving auto-mode.
2.7.5.1
Legend of the Auto-Mode Documentation
a.Symbols within a path
There are 3 symbols within a path
a.1.
In the auto-mode the device processes all subsequent state
transitions branchings etc. up to the next symbol.
a.2.
In the auto-mode the device does not process the state transitions,
branchings etc. Within the path appropriate directions are given with
which the software can accomplish the required action.
a.3.
A path cannot be implemented and no software or hardware action
can change this. These paths are either optional or only applicable for
window-size > 1.
Semiconductor Group
74
Functional Description
b.Symbols at a path
There is 1 symbol at a path
b.1.
marks the beginning of a path, for which a.3 applies.
c.Symbols at an internal or external message box.
There are 2 symbols at a message box.
c.1.
This symbol means, that the action described in the box is not
possible. Either the action specified is not done at all or an additional
action is taken (written into the box).
Box
Note: The impossibility to perform the optional T203 timer-procedure is not explicitly
mentioned; the corresponding actions are only crossed out.
c.2.
This symbol means, that within a software-path, by taking the
prescribed register actions the contents of the box will be done
automatically.
Box
d.Text within boxes
Text within boxes can be grouped in one of two classes.
d.1.
Text
Box
or
Box
Text
The text denotes an interrupt which is always associated with the
event. (But can also be associated with other events). (See ISTA- and
EXIR-register description in the Technical Manual for an interrupt
description).
d.2.The text describes a register access
Box
Text
either a register read access to discriminate this state from others or
to reach a branching condition
or a register write access to give a command.
The text is placed in the box that describes the functions for which the register access is
needed.
Semiconductor Group
75
Functional Description
e.Text attached at the side of boxes
e.1.
Text
Box
e.2.
The text describes an interrupt associated with the contents of the
box. The interrupt is always associated with the box contents, if the
interrupt name is not followed by a "/", it is associated only under
appropriate conditions if a "/" is behind it.
The text describes a possible or mandatory change of a bit in a statusregister associated with the contents of the box.
Box
Text
(The attached texts can also be placed on the left side.)
f.Text above and below boxes
f.1.
Text
Box
f.2.
Box
Text
Text describes a mandatory action to be performed on the contents of
the box.
Text describes a mandatory action to be taken as a result of the
contents of the box.
Action here means register access.
g.Shade boxes
The box describes an impossible state or action for the device.
Box
Semiconductor Group
76
Functional Description
2.7.5.2
Additional General Considerations when Using the Auto Mode
a)Switching from auto-mode to non-auto mode.
As mentioned in the introduction the auto mode is only applicable in the states 7 and 8 of the
LAPD. Therefore whenever these states have to be left (which is indicated by a "Mode:NAM"
text) there are several actions to be taken that could not all be detailed in the SDL diagrams:
a.1)write non-auto mode and TMD = 0 into the mode register.
a.2)write the timer register with an arbitrary value to stop it. The timer T200 as specified in the
LAPD protocol is implemented in the hardware only in the states 7 and 8; in all other states this
or any other timer-procedure has to be done by the software with the possible use of the timer
in external timer mode.
a.3)read the WFA bit of the STAR2 register and store it in a software variable. The information
in this bit may be necessary for later decisions. When switching from auto mode to non-auto
mode XPR interrupts may be lost.
a.4)In the non-auto mode the software has to decode I-, U- and S frames because I and S
frames are only handled autonomously in the auto-mode.
a.5)The RSC and PCE interrupts, the contents of the STAR2 register and the RRNR bit in the
STAR register are only meaningful within the auto-mode.
a.6)leave some time before RHR or XRES is written to reset the counters, as a currently sent
frame may not be finished yet.
b)What has to be written to the XFIFO?
In the legend description when the software has to write contents of a frame to the XFIFO only
"XFIFO" is shown in the corresponding box. We shall give here a general rule of what has to
be written to the XFIFO:
a) For sending an I frame with CMDR:XIF, only the information field content, i.e. no SAPI, TEI,
Control field should be written to the XFIFO.
b) For sending a U frame or any other frame with CMDR:XTF, the SAPI, TEI and the control
field has to be written to the XFIFO.
c)The interrupts XPR and XMR.
The occurence of an XPR interrupt in auto-mode after an XIF command indicates that the
I frame sent was acknowledged and the next I frame can be sent, if STAR2:TREC indicates
state 7 and STAR:RRNR indicates Peer Rec not busy. If Peer Rec is busy after an XPR, the
software should wait for the next RSC interrupt before sending the next I frame. If the XPR
happens to be in the timer recovery state, the software has to poll the STAR2 register until the
state multiple frame established is reached or a TIN interrupt is issued which requires auto
mode to be left (One of these two conditions will occur before the time T200 × N200). In nonauto mode or after an XTF command the XPR just indicates, that the frame was sent
successfully.
Semiconductor Group
77
Functional Description
The occurence of an XMR interrupt in auto-mode after an XIF command indicates that the
I frame sent was either rejected by the Peer Entity or that a collision occured on the S interface.
In both cases the I frame has to be retransmitted (after an eventual waiting for the RSC
interrupt if the Peer Rec was busy; after an XMR the device will always be in the state 7). In
non-auto mode or after an XTF command the XMR indicates that a collision occured on the
S interface and the frame has to be retransmitted.
d)The resetting of the RC variable:
The RC variable is reset in the ICC and ISAC-S TE when leaving the state timer recovery. The
SDL diagrams indicate a reset in the state multiple frame established when T200 expires.
There is no difference to the outside world between these implementations however our
implementation is clearer.
e)The timer T203 procedure:
We do not fully support the optional timer T203 procedure, but we can still find out whether or
not S frames are sent on the link in the auto-mode. By polling the STAR2:SDET bit and
(re)starting a software timer whenever a one is read we can build a quasi T203 procedure
which handles approximately the same task. When T203 expires one is supposed to go into
the timer recovery state with RC = 0. This is possible for the ICC and ISAC-S TE by just writing
the STI bit in the CMDR register (auto-mode and internal timer mode assumed).
f)The congestion procedure as defined in the 1 TR 6 of the "Deutsche Bundespost":
In the 1 TR 6 a variable N2 × 4 is defined for the maximum number of Peer Busy requests. The
1 TR 6 is in this respect not compatible with the Q921 of CCITT or the ETSI 46-20 but it is,
nevertheless, sensible to avoid getting into a hangup situation. With the ICC and ISAC-S TE
this procedure can be implemented:
After receiving an RSC interrupt with RRNR set one starts a software-timer. The timer is reset
and stopped if one either receives another RSC interrupt with a reset RRNR, if one receives a
TIN interrupt or if other conditions occur that result in a reestablishment of the link. The timer
expires after N2 × 4 × T200 and in this case the 1 TR 6 recommends a reestablishment of the
link.
2.7.5.3
Dealing With Error Conditions in Auto Mode
In the Recommendation Q.921 of CCITT (Blue Book) several error conditions are described.
We shall deal with them as far as they touch the auto mode of the ISAC-S (which only applies
for states 7,8 of Q.921).
Throughout the following document in subsections 1 we shall give the original Q.921-Text. For
better discrimination against comments the original text is printed in italic characters. Please
note that Q.921/table 5 has been corrected according to Corrigendum No. 1 10/1989.
Subsections 2 document how the ISAC-S react in all cases, and subsections 3 will give hints
how your software should respond to these reactions.
Invalid Frames and Frame Abortion
During data transmission invalid frames and frame abortion generally lead to error conditions.
Semiconductor Group
78
Functional Description
Q921: Invalid Frames and Frame Abortion
Paragraphs 2.9 and 2.10 of the Q.921 deal with Invalid Frames and Frame Abortion. In the
following the original text is given.
Q.921 § 2.9: Invalid Frames
An invalid frame is a frame which:
a) is not properly bounded by two flags, or
b) has fewer than 6 octets between flags or frames that contain sequence numbers, or
c) does not consist of an integral number of octets prior to zero bit insertion or following zero
bit extraction, or
d) contains a frame check sequence error, or
e) contains a single octet address field, or
f) contains a service access point identifier (see § 3.3.3) which is not supported by the
receiver.
Invalid frames shall be discarded without notification to the sender. No action is taken as the
result of that frame.
Q.921 § 2.10: Frame Abort
Receipt of seven or more contiguous 1 bits shall be interpreted as an abort and the data link
layer shall ignore the frame currently being received.
Reaction of the ISAC-S TE
a) A frame which does not start with a flag is discarded in the ISAC-S TE. A frame which
does not end with a flag is one, that is aborted, i.e. if § 2.9b does not apply then the
ISAC-S TE
– discards the frame, if it was an S-frame
or, if it was an I or U-frame
– generates an ISTA: RME (or RPFs and a RME) and
– puts RSTA: RAB = 1 after the RME-Interrupt RAB = 1.
A frame is supposed to be unbounded according to § 5.8.5 if the byte counter RBCH, RBCL
after RPF or RME exceeds 528.
b) The frame is discarded by the ISAC-S TE if
with U-frames or undefined framesit contains less or equal to 4 octets or
with I-framesit contains less or equal to 5 octets
with S-frames it contains less than 6 octets.
For U-frames with a content between 4 and 5 octets exclusively or for I-frames between 5 and
6 octets exclusively an ISTA: RME interrupt is generated and afterwards the RSTA: CRC is set
to 0.
c) An S-frame is discarded. In the own-receiver-busy state I-frames are discarded.
For an I-frame in the normal state and U frames, after several possible RPF interrupts and
the final RME interrupt, the bit RSTA: CRC is set to 0 in this case.
d) In case of an -S frame,
the frame is discarded
-U and I-framesRSTA: CRC is set to "0" in this case.
e) the frame is discarded
f) the frame is discarded
Semiconductor Group
79
Functional Description
The reaction to § 2.10 has been already discussed under a)
Necessary Software Actions
The software should read the Register RSTA after a RME-interrupt. After having read RAB = 1
or CRC = 0, all frame contents read from the FIFO should be discarded and a CMDR: RMC
should be written. After each RPF or RBCH, RBCL should be read and if it exceeds 528,
CMDR: RRES should be written. In this way all invalid frames are discarded by the software.
Data Overflow
In case of a data overflow, which is only possible while receiving an I-frame or an U-frame with
a non-empty information field, the ISAC-S TE interrupt with ISTA: RME and sets RSTA: RDO
to 1. A RSTA: RDO and an ISTA: RFO are a hint that the dynamic reaction time of your
software to the RPF, RME interrupt is too slow, so you should change your software. During
the development phase you may set CMDR: RNR after an RDO, RFO-condition to protect
against further errors, but the final solution can only be to exclude RDO, RFO conditions by an
improved software design.
Frame Rejection Condition
Q.921 § 5.8.5: Frame Rejection Condition
A frame rejection condition results from one of the following conditions:
a)
b)
c)
d)
the receipt of an undefined frame (see § 3.6.1, third paragraph)
the receipt of a supervisory or unnumbered frame with incorrect length
the receipt of an invalid N(R), or
the receipt of a frame with an information field which exceeds the maximum established
length.
Upon occurrence of a frame rejection condition whilst in the multiple frame operation, the data
link layer entity shall:
– issue a MDL-ERROR-INDICATION primitive, and
– initiate re-establishment (see § 5.7.2).
Upon occurrence of a frame rejection condition during establishment of or release from
multiple frame operation, or whilst a data link is not established, the data link layer entity shall:
– issue a MDL-ERROR-INDICATION primitive, and
– discard the frame.
Note: For satisfactory operation it is essential that a receiver is able to discriminate between
invalid frames, as defined in § 2.9, and frames with an information field which exceeds
the maximum established length (see § 3.6.11 item d). An unbounded frame may be
assumed, and thus discarded, if two times the longest permissible frame plus two octets
are received without a flag detection.
Semiconductor Group
80
Functional Description
For a better understanding we insert the text of § 3.6.1, which is referred to in § 5.8.5 and which
reads:
§ 3.6.1 Commands and responses
The following commands and responses are used by either the user or the network data link
layer entities and are represented in Q.921/table 5. Each data link connection shall support
the full set of commands and responses for each application implemented. The frame types
associated with each of the two applications are identified in Q.921/table 5.
Frame types associated with an application not implemented shall be discarded and no action
shall be taken as a result of that frame.
For purposes of the LAPD procedures in each application, those frame types not identified in
Q.921/table 5 are identified as undefined command and/or response control field. The actions
to be taken are specified in § 5.8.5.
We include the original table 5 which is mentioned in § 3.6.1:
Semiconductor Group
81
Functional Description
Table 7
Q.921 (Table 5)
Application
Format
Information
Transfer
Supervisory
Unacknowledged
and MultipleFrame
acknowledged
Information
Transfer
Command
s
Responses
8 7 6 5 4 3 2 1
I(nformation)
0
4
N(R)
P
5
1
4
P/F
5
1
4
P/F
5
1
4
P/F
5
RR
(receive ready)
0
RNR
(receive not
ready)
RNR
(receive not ready)
0
REJ
(reject)
REJ
(reject)
0
0
0
0
0
0
0
N(R)
0
0
0
0
1
0
N(R)
0
0
0
1
0
0
N(R)
0
1
1
P
1
1
1
1
4
0
0
0
F
1
1
1
1
4
UI
(Unnumbered Information)
0
0
0
P
0
0
1
1
4
DISC
(disconnect)
0
1
0
P
0
0
1
1
4
UA
(unnumbered
Acknowledgement)
0
1
1
F
0
0
1
1
4
FRMR
(frame reject)
1
0
0
F
0
1
1
1
4
XID*
(Exch. Ident)
1
0
1
P
/
F
1
1
1
1
4
DM
(disconnected
mode)
Connection
Management
Oct
et
N(S)
RR
(receive ready)
SABME
(set async.
balanced
Mode extd).
Unnumbered
Encoding
XID*
(Exch. Ident)
*Note: Use of the XID frame other than for parameter negotiation procedures (see § 5.4) is for
further study. The commands and responses in Q.921/table 5 are defined in § 3.6.2 to
§ 3.6.12
Semiconductor Group
82
Functional Description
Reaction of the ISAC-S TE
In the following various possible actions to be taken according to § 5.8.5 parts a) through c)
are discussed separately.
a) There are different types of undefined frames:
1) I-frame which is not a command an ISTA: PCE-interrupt is generated
2) S-frame with bits 8-5 in Octet 4 = 0 an ISTA: PCE-interrupt is generated
3) A frame with bits 4-1 in octet 4
equal to "1101" (selective reject)
an ISTA: PCE is generated
4) Frame with bits 2-1 in octet 4 equal
to "11" but control field not contained
in ISTA: RME interrupt;
the control field can be read afterwards in
RHCR (after having checked for invalid
frame condition).
5) SABME, UI, DISC, not a command,
DM, UA, FRMR not a response
ISTA: RME interrupt;
the control field can be read afterwards in
RHCR, the C/R-bit in the SAPR-register
(after having checked for invalid frame
condition).
b) If the length of the frame is too small 1.1.1b) applies and the frame is invalid. Therefore
incorrect length can only mean:
1) S-frame with more than 6 octets an ISTA:PCE-interrupt is generated; the
contents of the additional octets is discarded.
2) Undefined frames with 5 octets,
bits 2-1 in octet 4 not being equal
to "11" (e.g. modulo 8 S-frame)
3) SABME, BM, DISC, UA-frame
with more than 5 octets
an ISTA:PCE-interrupt is generated
after ISTA:
RME and identifying the frame by RHCR the
RSTA:RDA bit is 1 if the frames had more
than 5 octets and 0 if they had exactly 5 octets.
4) A FRMR with not exactly 10 octetsAfter a RME and identifying FRMR by
reading RHCR-register, the software has to
read RBCH, RBCL. If OV = 1 or
RBC11-RBC0 = 0 … 101 then the FRMR did
not have exactly 10 octets.
c) An invalid N(R) is one that does not meet the condition
V(A) < N(R) < V(S)
This condition is automatically checked within the device and in the case of an invalid N(R) an
ISTA:PCE-interrupt is generated. An S-field response is done by the ISAC-S TE in all
prescribed cases of invalid N(R) automatically.
Semiconductor Group
83
Functional Description
The processor should read RBCH, RBCL after each RPF, RME interrupt. If after an RPF or
RME the byte count exceeds 528 then CMDR:RRES should be written (abort of frame). The
frame was invalid in this case but it was not a frame rejection condition. If after a RME the byte
count was between 260 and 528 inclusively and no other invalidity condition according to
section 1 applies or a data overflow according to section 2 occurred then a frame rejection
condition is detected.
Necessary Software Reactions
The software can find out all frame rejection conditions either by receiving PCE or by checking
RSTA, SAPR, RHCR, RBCH, RBCL after a RME interrupt, and RBCH, RBCL after an RPF
interrupt. In case of U-frames it has to be checked before, whether or not it is an invalid frame
and has only to be discarded or, whether it was valid but leads to a frame rejection condition.
(Only valid frames can lead to frame rejection conditions according to § 5.8.4 of Q.921).
In case of a frame rejection condition the software has to take the actions defined in § 5.7.2
and issue a MDL-ERROR-INDICATION.
The particular action in § 5.7.2 reads:
§ 5.7.2 Procedures
In all re-establishment situations, the data link layer entity shall follow the procedures defined
in § 5.5.1. All locally generated conditions for re-establishment will cause the transmission of
the SABME.
In case of data link layer and peer initiated re-establishments, the data link layer entity shall
also
– Issue a MDL-ERROR-INDICATION primitive to the connection management entity: and
– rf V(S) > V(A) prior to re-establishment issue a DL-ESTABLISH-INDICATION primitive
to layer 3 and discard all l-queues.
In case of layer-3 initiated re-establishment, or if a DL-ESTABLISH-REQUEST primitive
occurs pending re-establishment, the DL-ESTABLISH-CONFIRM primitive shall be used.
A frame rejection condition is not a peer initiated re-establishment.
§ 5.5.1 is pretty voluminous. Here just the necessary actions to be done with the ISAC-S TE
shall be given, in case the re-establishment is successful at once:
– the software should set the ISAC-S TE into non-auto mode by writing the Mode register
MODE: 6xH. Further actions that result from switching to non-auto mode should also be
taken according.
– it should write FIFO : 76H, 6FH, CMDR : XTF to send a SABME-command with p = 1.
– upon having received a correct UA-frame it should
– write CMDR : XRES, RRES to set V(S) = V(A) = V(R) = 0
– write MODE: 3xH to re-enter auto mode for the multiple-frame established state.
If the re-establishment is not successful at once, in the non-auto mode further software actions
according to § 5.5.1 have to be taken.
Semiconductor Group
84
Functional Description
Further Criteria Leading to a Re-Establishment
Q.921 § 5.7.1: Criteria for Re-Establishment
§ 5.7.1 Criteria for re-establishment
The criteria for re-establishing the multiple frame mode of operation are defined in this section
by the following conditions:
a) The receipt while in the multiple frame mode of operation, of an SABME;
b) The receipt of a DL-ESTABLISH-REQUEST primitive from layer 3 (see § 5.5.1.1);
c) The occurrence of N200 re-transmission failures while in the timer recovery condition
(see § 5.6.7)
d) The occurrence of a frame rejection condition as identified in § 5.8.5;
e) On the receipt, while in the multiple frame mode of operation of an FRMR response frame
(see § 5.8.6);
f) The receipt, while in the multiple frame mode of operation, of an unsolicited DM response
with the F bit set to 0 (see § 5.8.7);
g) The receipt while in the timer recovery condition, of a DM response with the F bit set to 1.
Reaction of the ISAC-S TE
a) after having checked for validity and non-occurrence of a frame rejection condition, the
error free SABME can be identified after RME-Interrupt by reading the RHCR-register; the
multiple frame est/timer recovery discrimination can be done by reading STAR2: TREC
b) –
c) A TIN-Interrupt occurs (of course MODE: TMD has to have been 1)
d) see section 3
e) see a)
f) see a)
g) see a)
Necessary Software Reactions
The same actions as in section 3 have to be taken. In addition, in case of a) the necessary
discrimination for the software is possible by reading STAR2: WFA while still in auto mode. If
WFA = 1 then V(S) > V(A); if WFA = 0, then V(S) = V(A).
Semiconductor Group
85
Functional Description
Further Possible Error Conditions
Appendix II of Q.921: Further Possible Error Conditions
Table 8
Q.921
Management Entity Actions for MDL Error Indications
Error Type
Error
Error
Affected
Network
Code
Condition
States
Management
Action
Receipt of
A
Supervisory
7
Error log
unsolicited
(F = 1)
response
B
DM(F = 1)
7, 8
Error log
C
UA(F = 1)
D
UA(F = 1)
E
Receipt of DM
7, 8
response (F = 0)
SABME
7, 8
Error log
SABME
5
DISC
6
Status Inquiry
8
TEI check
procedure;
then, if TEI:
– free, remove
TEI
– single, no action multiple:
TEI removal
procedure
Error log
Peer initiated F
Reestablishmen
t
Unsuccessful G
Retransmission
(N200 times) H
I
Semiconductor Group
4, 7, 8
TEI removal
procedure or
TEI check procedure; then, if
4, 5, 6, 7, 8 TEI:
– free, remove
TEI
– single, no action multiple:
TEI removal
procedure
86
Error log
User
Management
Action
Dependent on
implementation
Dependent on
implementation
TEI identity verify
procedure
or
remove TEI
Dependent on
implementation
Dependent on
implementation
TEI identity verify
procedure
or
remove TEI
Dependent on
implementation
Functional Description
Table 8
Q.921
Management Entity Actions for MDL Error Indications (cont’d)
Error Type
Error
Error
Affected
Network
Code
Condition
States
Management
Action
Other
J
N(R) Error
7, 8
Error log
K
Receipt of
FRMR
response
Receipt of non
implemented
frame
Receipt of I-field
not permitted
Receipt of frame with wrong
size
N201 Error
7, 8
Error log
L
M (see
Note 2)
N
O
User
Management
Action
Dependent on
implementation
Dependent on
implementation
4, 5, 6, 7, 8 Error log
Dependent on
implementation
4, 5, 6, 7, 8 Error log
Dependent on
implementation
Dependent on
implementation
4, 5, 6, 7, 8 Error log
4, 5, 6, 7, 8 Error log
Dependent on
implementation
Note 1: For the description of the affected states see Annex B.
Note 2: According to Q.921 § 5.8.5 this error code will never be generated.
Reactions of the ISAC-S TE and Necessary Software Reactions
As the auto mode is only to be used in states 7, 8 and as it has to be switched to non-auto
mode where in states 1-6, we do not have to deal with error code G and H.
A) The ISAC-S does not react at all (our implementation). The software is not informed, as
no action is mandatory according to Q.921.
B) see further Criteria Leading to a Reestablishment"
C) see further Criteria Leading to a Reestablishment
D) see further Criteria Leading to a Reestablishment
E) see further Criteria Leading to a Reestablishment
F see further Criteria Leading to a Reestablishment
I) see further Criteria Leading to a Reestablishment
J) see Frame Rejection Condition
K) see further Criteria Leading to a Reestablishment
L) see Frame Rejection Condition
M)
N) see Frame Rejection Condition
O) only internal software timer, no device action.
Conclusion:
For your error-processing with ISAC-S we suggest to implement the software design shown in
the following figures 35 through 38 into your interrupt service routine.
Semiconductor Group
87
Functional Description
RME &
/TIN & /PCE
RSTA:RAB = 1
or CRC = 0
?
Y
CMDR:RHR
Discard frame cont
Y
Please change your
software: dynamic reaction
time is too slow
N
Futher analysis outside
the auto-mode link
Y
Re-establishment
of the link
N
RSTA:RDO = 1
or ISTA:RFO = 1
?
N
RSTA:
which link,
auto-mode
?
Y
RBCH, RBCL > 260
?
N
CMDR:RMC
Cont. -> Layer 3
I-frame
RHCR, SAPR :
C/R control field
Not contained
in table 5 of
Q.921 3.6.1
Re-establishment
of the link
?
U-frame
U-frame
processing
Figure 35
Interrupt Service Routine after RME
Semiconductor Group
88
ITD05896
Functional Description
RPF &
/TIN & /PCE
RBCH, RBCL > 528
?
Y
CMDR:RHR
Discard frame cont
Note: In this case the software
has to react instantaneously
to the RPF ( < 500 µs)
N
Read FIFO
CMDR:RMC
TIN or PCE
RSC
Re-establishment
of the link
Change status
variable
Note: For the congestion procedure
defined in 1 TRG of
the Deutsche Bundespost
refer to the Technical Manual
XDU or RFO
Please change your software:
Dynamic reaction is too slow
ITD05895
Figure 36
Interrupt Service Routines after RPF (top), TIN or PCE (middle left), RSC (middle right),
and XDU or RFO (bottom)
Semiconductor Group
89
Functional Description
XPR &
/TIN & /PCE
Has a
frame been
sent since last
CMDR:XRES
?
N
End
Y
A frame
is currently
transmitted
Continue writing the contents
of the frame to XFIFO & issuing
Xmit command
Y
?
N
Last frame
written to XFIFO was
an I-frame
The transmission of the I-frame
was successful and has been
acknowledged by the peer station
Y
ACK1
?
N
SRC *
N
Transmission of the last
frame has finished
Xmit command
ACK2
?
Y
ACK1 & ACK2
* Special Request Condition : Last frame written to the XFIFO was an answer to an identity
request following a yet unacknowledged I-frame
Figure 37
Interrupt Service Routine after XPR
Semiconductor Group
90
ITD05893
Functional Description
XMR &
/TIN & /PCE
SRC
?
N
Re-transmit the
frame sent last
Y
Re-transmit the
Ι - frame sent last
ITD05894
Figure 38
Interrupt Service Routine after XMR
Semiconductor Group
91
Functional Description
7
MULTIPLE
FRAME
ESTABLISHED
DL
ESTABLISH
REQUEST
DISCARD
I QUEUE
DL
RELEASE
REQUEST
DISCARD
I QUEUE
DL-DATA
REQUEST
PUT IN
I QUEUE
I FRAME
QUEUED UP
PEER
RECEIVER
BUSY
STAR:RRNR
YES
NO
ESTABLISH
DATA LINK
RC = 0
P=1
I FRAME
QUEUED UP
(V)S = V(A) + K
YES
STAR2:WFA
NO
SET
LAYER 3
INITIATED
TX DISC
XFIFO
CMDR XTF
7
MULTIPLE
FRAME
ESTABLISHED
GET NEXT
I QUEUE
ENTRY
XFIFO
I FRAME
QUEUED UP
MODE NAM
5
AWAITING
ESTABLISHM.
STOP T203
RESTART T200
P=0
MODE NAM
TXI
COMMAND
6
AWAITING
RELEASE
CMDR:XIF
V(S) = V(S) + 1
CLEAR
ACKNOWLEDGE
PENDING
T200
RUNNING
YES
NO
STOP T203
START T200
Note: The regeneration of this signal does not affect
the sequence integrity of the I queue.
ITD02365
Figure 39a
Semiconductor Group
92
7
MULTIPLE
FRAME
ESTABLISHED
Functional Description
7
MULTIPLE
FRAME
ESTABLISHED
TIMER
T200
EXPIRY
MDL
REMOVE
REQUEST
PERSISTENT
DEACTIVATION
TRANSMIT
ENQUIRY
DISCARD
I AND UI
QUEUES
DISCARD
I AND UI
QUEUES
RC = 0
DL RELEASE
INDICATION
DL RELEASE
INDICATION
STOP T200
STOP T203
STOP T200
STOP T203
1
TEI
UNASSIGNED
4
TEI
ASSIGNED
TIMER
T203
EXPIRY
CMDR STI
RC = 0
YES
PEER
BUSY
NO
GET LAST
TRANSMITTED
I FRAME
TRANSMIT
ENQUIRY
8
TIMER
RECOVERY
STAR2:
TREC
V(S) = V(S) - 1
P=1
ITD02366
TX I
COMMAND
V(S) = V(S) + 1
CLEAR
ACKNOWLEDGE
PENDING
START T200
RC = RC + 1
8
TIMER
RECOVERY
STAR2:
TREC
Figure 39b
Semiconductor Group
93
Functional Description
7
MULTIPLE
FRAME
ESTABLISHED
RME
RME
RME
SABME
DISC
UA
RCHR:
RCHR:
RCHR:
F=P
DISCARD
I QUEUE
TX UA
STORE
STAR2:
WFA
F=P
XFIFO
CMDR XTF
CLEAR
EXCEPTION
CONDITIONS
YES
TX UA
XFIFO
CMDR XTF
MDL-ERROR
INDICATION
(F)
DL-RELEASE
INDICATION
V(S) = V(A)
STOP T200
STOP T203
STAR2:WFA = 0
MODE NAM
NO
4
TEI
ASSIGNED
DISCARD
I QUEUE
DL
ESTABLISH
INDICATION
STOP T200
STOP T203
CMDR:RHR;XRES
V(S) = 0
V(A) = 0
V(R) = 0
7
MULTIPLE
FRAME
ESTABLISHED
ITD02367
Figure 39c
Semiconductor Group
94
MDL-ERROR
INDICATION
(C,D)
7
MULTIPLE
FRAME
ESTABLISHED
Functional Description
7
MULTIPLE
FRAME
ESTABLISHED
RME
CLEAR OWN
RECEIVER
BUSY
SET OWN
RECEIVER
BUSY
DM
RHCR:
F=1
CLEAR
RECEIVER
BUSY
YES
RHCR
NO
MDL-ERROR
INDICATION
(E)
ESTABLISH
DATA LINK
CLEAR
LAYER 3
INITIATED
YES
CLEAR
RECEIVER
BUSY
NO
NO
MDL-ERROR
INDICATION
(B)
7
MULTIPLE
FRAME
ESTABLISHED
SET OWN
RECEIVER
BUSY
CMDR:RNR = 1
YES
STAR:XRNR
CLEAR OWN
RECEIVER
BUSY
CMDR:RNR = 0
F=0
F=0
TX RNR
RESPONSE
TX RR
RESPONSE
CLEAR
ACKNOWLEDGE
PENDING
CLEAR
ACKNOWLEDGE
PENDING
MODE NAM
5
AWAITING
ESTABLISHM.
7
MULTIPLE
FRAME
ESTABLISHED
Note: These signals are generated outside of this SDL representation,
and may be generated by the connection management entity.
Figure 39d
Semiconductor Group
95
ITD02368
STAR:XRNR
Functional Description
7
MULTIPLE
FRAME
ESTABLISHED
REJ
RR
CLEAR PEER
RECEIVER
BUSY
COMMAND
RSC /
CLEAR PEER
RECEIVER
BUSY
STAR:RRNR
NO
NO
F=1
YES
YES
COMMAND
F=1
NO
NO
NO
NO
MDL-ERRORINDICATION
(A)
YES
ENQUIRY
RESPONSE
STAR:RRNR
YES
YES
P=1
RSC /
P=1
YES
MDL-ERRORINDICATION
(A)
STAR2:SDET
ENQUIRY
RESPONSE
ITD05656
1
2
Figure 39 f
Figure 39 f
Figure 39e
Semiconductor Group
96
STAR2:SDET
Functional Description
1
2
_ N(R) <_ V(S)
V(A) <
NO
NO
YES
_ N(R) <_ V(S)
V(A) <
YES
XPR /
PCE
N(R) = V(S)
N(R) ERROR
RECOVERY
NO
YES
V(A) = N(R)
STAR2:WFA
MODE NAM
XPR /
YES
V(A) = N(R)
5
AWAITING
ESTABLISHM.
N(R) = V(A)
STAR2:WFA
STOP T200
START T203
NO
INVOKE
RETRANSMISSION
STOP T200
START T203
V(A) = N(R)
7
MULTIPLE
FRAME
ESTABLISHED
RESTART T200
7
MULTIPLE
FRAME
ESTABLISHED
ITD02370
Figure 39f
Semiconductor Group
97
XMR /
Functional Description
7
MULTIPLE
FRAME
ESTABLISHED
RME
RNR
FRMR
RHCR:
RSC /
SET PEER
RECEIVER
BUSY
MDL-ERROR
INDICATION
(K)
STAR:RRNR
NO
COMMAND
ESTABLISH
DATA LINK
YES
F=1
NO
P=1
CLEAR
LAYER 3
INITIATED
NO
MODE NAM
MDL-ERRORINDICATION
(A)
YES
ENQUIRY
RESPONSE
YES
5
AWAITING
ESTABLISHM.
STAR2:SDET
_ N(R) <_ V(S)
V(A) <
NO
YES
XPR /
N(R)
ERROR
RECOVERY
V(A) = N(R)
STAR2:WFA
MODE NAM
STOP T203
5
AWAITING
ESTABLISHM.
RESTART T200
RC = 0
7
MULTIPLE
FRAME
ESTABLISHED
ITD02371
Figure 39g
Semiconductor Group
98
PCE
Functional Description
7
MULTIPLE
FRAME
ESTABLISHED
I
COMMAND
OWN
RECEIVER
BUSY
YES
NO
N(S) = V(R)
DISCARD
INFORMATION
NO
YES
DISCARD
INFORMATION
V(R) = V(R) + 1
NO
P=1
YES
REJECT
EXCEPTION
CLEAR REJECT
EXCEPTION
NO
NOTE 2
F=1
YES
RME
DL-DATA
INDICATION
RFIFO, RHCR
NO
P=1
SET
REJECT
EXCEPTION
STAR2:SDET
YES
YES
P=1
TX RNR
CLEAR
ACKNOWLEDGE
PENDING
F=P
NO
ACKNOWLEDGE
PENDING
YES
TX REJ
F=P
STAR2:SDET
NO
ACKNOWLEDGE
PENDING
CLEAR
ACKNOWLEDGE
PENDING
TX RR
STAR2:SDET
NOTE 1
SET
ACKNOWLEDGE
PENDING
CLEAR
ACKNOWLEDGE
PENDING
ITD05657
3
Figure 39 i
Note 1: Processing of acknowledge pending is descripted on figure 39 i
Note 2: This SDL representation does not include the optional procedure in Appendix I.
Figure 39h
Semiconductor Group
99
Functional Description
3
_ N(R) <_ V(S)
V(A) <
NO
YES
PEER
RECEIVER
BUSY
N(R)
ERROR
RECOVERY
NO
YES
MODE NAM
XPR /
V(A) = N(R)
N(R) = V(S)
5
AWAITING
ESTABLISHM.
NO
STAR2:WFA
YES
XPR /
V(A) = N(R)
N(R) = V(A)
STAR2:WFA
NO
STOP T200
V(A) = N(R)
RESTART T203
RESTART T200
7
MULTIPLE
FRAME
ESTABLISHED
ITD02373
Figure 39i
Semiconductor Group
100
YES
PCE
Functional Description
7
MULTIPLE
FRAME
ESTABLISHED
ACKNOWLEDGE
PENDING
ACKNOWLEDGE
PENDING
NO
YES
CLEAR
ACKNOWLEDGE
PENDING
F=0
TX RR
STAR2:SDET
7
MULTIPLE
FRAME
ESTABLISHED
ITD02374
Figure 39j
Semiconductor Group
101
Functional Description
8
TIMER
RECOVERY
DL
ESTABLISH
REQUEST
DL
ESTABLISH
REQUEST
DL-DATA
REQUEST
DISCARD
I QUEUE
DISCARD
I QUEUE
PUT IN
I QUEUE
ESTABLISH
DATA LINK
RC = 0
P=1
I FRAME
QUEUED UP
SET
LAYER 3
INITIATED
TX DISC
8
TIMER
RECOVERY
MODE NAM
5
AWAITING
ESTABLISHM.
XFIFO
CMDR XTF
RESTART T200
MODE NAM
6
AWAITING
RELEASE
ITD02375
Figure 40a
Semiconductor Group
102
I FRAME
QUEUED UP
Functional Description
8
TIMER
RECOVERY
MDL
REMOVE
REQUEST
PERSISTENT
DEACTIVATION
DISCARD
I AND UI
QUEUES
DISCARD
I AND UI
QUEUES
MDL-ERROR
INDICATION(I)
DL-RELEASE
INDICATION
DL-RELEASE
INDICATION
ESTABLISH
DATA LINK
STOP T200
STOP T200
TIMR
TIMR
MODE NAM
MODE NAM
1
TEI
UNASSIGNED
4
TEI
ASSIGNED
TIMER
T200
EXPIRY
RC = N200
YES
NO
TIN
YES
V(S) = V(A)
NO
YES
PEER
BUSY
NO
TRANSMIT
ENQUIRY
GET LAST
TRANSMITTED
I FRAME
V(S) = V(S) - 1
P=1
CLEAR
LAYER 3
INITIATED
MODE NAM
5
AWAITING
ESTABLISHM.
TX I
COMMAND
V(S) = V(S) + 1
CLEAR
ACKNOWLEDGE
PENDING
START T200
RC = RC + 1
8
TIMER
RECOVERY
Figure 40b
Semiconductor Group
103
ITD02376
Functional Description
8
TIMER
RECOVERY
RME
RME
RME
SABME
DISC
UA
RHCR:
RHCR:
RHCR:
F=P
DISCARD
I QUEUE
TX UA
STORE
STAR2:
WFA
F=P
XFIFO
CMDR XTF
CLEAR
EXCEPTION
CONDITIONS
YES
TX UA
XFIFO
CMDR XTF
MDL-ERROR
INDICATION
(F)
DL-RELEASE
INDICATION
V(S) = V(A)
STOP T200
STAR2:WFA = 0
MODE NAM
NO
4
TEI
ASSIGNED
DISCARD
I QUEUE
DL
ESTABLISH
INDICATION
STOP T200
START T203
CMDR:RHR;XRES
V(S) = 0
V(A) = 0
V(R) = 0
7
MULTIPLE
FRAME
ESTABLISHED
STAR2:TREC
Figure 40c
Semiconductor Group
104
ITD02377
MDL-ERROR
INDICATION
(C, D)
8
TIMER
RECOVERY
Functional Description
8
TIMER
RECOVERY
RME
CLEAR OWN
RECEIVER
BUSY
SET OWN
RECEIVER
BUSY
DM
RHCR:
F=1
CLEAR
RECEIVER
BUSY
YES
RHCR
NO
MDL-ERROR
INDICATION
(E)
YES
NO
OWN
RECEIVER
BUSY
NO
MDL-ERROR
INDICATION
(B)
YES
SET OWN
RECEIVER
BUSY
CMDR:RNR = 1
STAR:XRNR
CLEAR OWN
RECEIVER
BUSY
CMDR:RNR = 0
ESTABLISH
DATA LINK
F=0
F=0
CLEAR
LAYER 3
INITIATED
TX RNR
RESPONSE
TX RR
RESPONSE
CLEAR
ACKNOWLEDGE
PENDING
CLEAR
ACKNOWLEDGE
PENDING
MODE NAM
5
AWAITING
ESTABLISHM.
8
TIMER
RECOVERY
Note: These signals are generated outside of this SDL representation,
and may be generated by the connection management entity.
Figure 40d
Semiconductor Group
105
ITD02378
STAR:XRNR
Functional Description
8
TIMER
RECOVERY
RR
REJ
CLEAR PEER
RECEIVER
BUSY
COMMAND
RSC /
STAR:RRNR
NO
YES
P=1
YES
F=1
NO
NO
NO
_ N(R) <_ V(S)
V(A) <
YES
YES
ENQUIRY
RESPONSE
STAR2:SDET
XPR /
V(A)=N(R)
STAR2:WFA
_ N(R) <_ V(S)
V(A) <
STOP T200
NO
START T203
YES
XPR /
PCE
N(R) ERROR
RECOVERY
V(A) = N(R)
STAR2:WFA
INVOKE
RETRANSMISSION
XMR /
MODE NAM
8
TIMER
RECOVERY
5
AWAITING
ESTABLISHM.
7
MULTIPLE
FRAME
ESTABLISHED
ITD02379
Figure 40e
Semiconductor Group
106
STAR2:TREC
Functional Description
8
TIMER
RECOVERY
RME
RNR
FRMR
RCHR:
RSC /
MDL-ERROR
INDICATION
(K)
BUSY
STAR:RRNR
COMMAND
NO
YES
ESTABLISH
DATA LINK
F=1
YES
CLEAR
LAYER 3
INITIATED
NO
P=1
NO
NO
MODE NAM
_ N(R) <_ V(S)
V(A) <
YES
YES
ENQUIRY
RESPONSE
V(A) = N(R)
5
AWAITING
ESTABLISHM.
XPR /
_ N(R) <_ V(S)
V(A) <
STAR2:WFA
STAR2:SDET
NO
RESTART T200
RC = 0
YES
XPR /
V(A) = N(R)
STAR2:WFA
N(R)
ERROR
RECOVERY
PCE
INVOKE
RETRANSMISSION
XMR /
MODE NAM
8
TIMER
RECOVERY
7
MULTIPLE
FRAME
ESTABLISHED
5
AWAITING
ESTABLISHM.
ITD02380
Figure 40f
Semiconductor Group
107
STAR2:TREC
Functional Description
8
TIMER
RECOVERY
I
COMMAND
OWN
RECEIVER
BUSY
YES
NO
N(S) = V(S)
DISCARD
INFORMATION
NO
YES
DISCARD
INFORMATION
V(R) = V(R) + 1
NO
P=1
YES
REJECT
EXCEPTION
CLEAR REJECT
EXCEPTION
NO
NOTE 2
F=1
YES
RME
DL-DATA
INDICATION
RFIFO, RHCR
NO
P=1
SET
REJECT
EXCEPTION
TX RNR
STAR2:SDET
YES
YES
P=1
CLEAR
ACKNOWLEDGE
PENDING
F=P
NO
ACKNOWLEDGE
PENDING
YES
TX REJ
F=P
STAR2:SDET
NO
ACKNOWLEDGE
PENDING
CLEAR
ACKNOWLEDGE
PENDING
TX RR
STAR2:SDET
NOTE 1
SET
ACKNOWLEDGE
PENDING
CLEAR
ACKNOWLEDGE
PENDING
ITD05658
4
Figure 40 h
Note 1: Processing of acknowledge pending is descripted on figure 40 i
Note 2: This SDL representation does not include the optional procedure in Appendix I.
Figure 40g
Semiconductor Group
108
Functional Description
4
_ N(R) <_ V(S)
V(A) <
NO
YES
XPR /
N(R)
ERROR
RECOVERY
V(A) = N(R)
STAR2:WFA
PCE
MODE NAM
8
TIMER
RECOVERY
5
AWAITING
ESTABLISHM.
Figure 40h
8
TIMER
RECOVERY
ACKNOWLEDGE
PENDING
ACKNOWLEDGE
PENDING
NO
YES
CLEAR
ACKNOWLEDGE
PENDING
F=0
TX RR
STAR2:SDET
8
TIMER
RECOVERY
Figure 40i
Semiconductor Group
109
ITD02383
ITD02382
Functional Description
RELEVANT
STATES
(NOTE 1)
DL
UNIT DATA
REQUEST
UI
FRAME
QUEUED UP
PLACE IN
UI QUEUE
REMOVE UI
FRAME FROM
QUEUE
UI
FRAME
QUEUED UP
P=0
NOTE 2
TX UI
COMMAND
XFIFO
CMDR: XTF
RME
UI COMMAND
RHCR
DL
UNIT DATA
INDICATION
NOTE 2
NOTE 2
Note 1: The relevant states are as follows
4 TEI-assigned
5 Awaiting-establishement
6 Awaiting-release
7 Multiple-frame-established
8 Timer-recovery
Note 2: The data link layer returns to the state it was in prior to the events shown.
ITD02384
Figure 41a
Semiconductor Group
110
Functional Description
RELEVANT
STATES
(NOTE 1)
CONTROL
FIELD
ERROR (W)
INFO NOT
PERMITTED
(X)
INCORRECT
LENGHT
(X)
MDL-ERROR
INDICATION
(L,M,N,O)
ESTABLISH
DATA LINK
CLEAR
LAYER 3
INITIATED
5
AWAITING
ESTABLISHM.
Note 1: The relevant states are as follows
7 Multiple-frame-established
8 Timer-recovery
ITD02385
Figure 41b
Semiconductor Group
111
PCE /
1 FRAME
TOO LONG
(Y)
Functional Description
RELEVANT
STATES
(NOTE 1)
CONTROL
FIELD
ERROR (W)
INFO NOT
PERMITTED
(X)
INCORRECT
LENGTH
(X)
I FRAME
TOO LONG
(Y)
MDL-ERRORINDICATION
(L, M, N, O)
NOTE 2
Note 1: The relevant states are as follows:
4 TEI-assigned
5 Awaiting-establishment
6 Awaiting-release
Note 2: The data link layer returns to the state
it was in prior to the events shown
Figure 41c
Semiconductor Group
112
ITD02577
Functional Description
N(R)
ERROR
RECOVERY
MDL-ERROR
INDICATION(J)
PCE
ESTABLISH
DATA LINK
ESTABLISH
DATA LINK
CLEAR
EXCEPTION
CONDITION
CMDR:RHR,XRES
MODE: NAM
RC = 0
P=1
CLEAR
EXCEPTION
CONDITIONS
TRANSMIT
ENQUIRY
CMDR:RHR,XRES
CLEAR PEER
RECEIVER
BUSY
P=1
CLEAR
REJECT
EXCEPTION
OWN
RECEIVER
BUSY
YES
NO
CLEAR
LAYER 3
INITIATED
TX SABME
XFIFO
CMDR:XTF
RESTART T200
STOP T203
CLEAR OWN
RECEIVER
BUSY
CMDR:RNR = 0
TX RR
COMMAND
TX RNR
COMMAND
CLEAR
ACKNOWLEDGE
PENDING
CLEAR
ACKNOWLEDGE
PENDING
START T200
ITD02386
Figure 41d
Semiconductor Group
113
Functional Description
ENQUIRY
RESPONSE
INVOKE
RETRANSMISSION
F=1
V(S) = N(R)
OWN
RECEIVER
BUSY
YES
NO
XMR
YES
V(S) =V(S) - 1
NO
I FRAME
QUEUED UP
TX RNR
RESPONSE
TX RR
RESPONSE
STAR2:SDET
STAR2:SDET
NOTE
BACK TRACK
ALONG
I QUEUE
CLEAR
ACKNOWLEDGE
PENDING
Note: The generation of the correct number of signals in order to cause the required
retransmission of I frames does not alter their sequence integrity.
ITD02387
Figure 41e
Semiconductor Group
114
Operational Description
3
Operational Description
The ISAC-S TE, designed for the connection of subscribers to an ISDN using a standard S/T
interface, has the following application, corresponding to the operating mode explained in
chapter 2:
Terminal Equipment TE1, TA
e.g.
3.1
ISDN-feature telephone,
ISDN-voice/data workstation
Terminal Adapter for non-ISDN terminals (TE2)
Microprocessor Interface Operation
The ISAC-S TE is programmed via an 8-bit parallel microcontroller interface. Easy and fast
microprocessor access is provided by 8-bit address decoding on the chip. Depending on the
chip package (P-DIP-40, P-LCC-44, P-MQFP-64) either one or three types of µP buses are
provided:
P-DIP-40 package:
The ISAC-S TE microcontroller interface is of the Siemens/Intel multiplexed address/data
bus type with control signals CS, WR, RD, ALE.
P-LCC-44/P-MQFP-64 package:
The ISAC-S TE microcontroller interface can be selected to be either of the
(1) – Motorola type with control signals CS, R/W, DS
(2) – Siemens/Intel non-multiplexed bus type with control signals CS, WR, RD
(3) – or of the Siemens/Intel multiplexed address/data bus type with control
signals CS, WR, RD, ALE.
The selection is performed via pin ALE as follows:
ALE tied to VDD
⇒
(1)
ALE tied to VSS
⇒
(2)
Edge on ALE
⇒
(3).
The occurrence of an edge on ALE, either positive or negative, at any time during the operation
immediately selects interface type (3). A return to one of the other interface types is possible
only if a hardware reset is issued.
Notes: 1) If the multiplexed address/data bus type (3) is selected, the unused address pins
A0-A5 are internally pulled low and may thus be left open. It is however
recommended to tie the unused input pins to a VDD voltage level.
2) If the non-multiplexed bus types (1) or (2) are selected, the EAW line can no longer
be used since pin 10 EAW/A5 has the function of an address pin (PLCC-44 only).
Semiconductor Group
115
Operational Description
The microprocessor interface signals are summarized in table 9.
Table 9
µP Interface of the ISAC®-S TE
Pin No. Pin No.
Function
Pin No.
Symbol Input (I)
P-DIP-40 P-LCC-44 P-MQFP-64
Output (O)
Open Drain
(OD)
37
38
39
40
1
2
3
4
41
42
43
44
1
2
3
4
37
38
39
40
41
42
43
44
AD0/D0
AD1/D1
AD2/D2
AD3/D3
AD4/D4
AD5/D5
AD6/D6
AD7/D7
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
Multiplexed Bus Mode: Address/Data
bus. Transfers addresses from the µP
system to the ISAC-S TE and data
between the µP system and the
ISAC-S TE.
Non-Multiplexed Bus Mode: Data bus.
Transfers data between the µP system and
the ISAC-S TE.
34
37
27
CS
I
38
28
R/W
I
38
28
WR
I
Chip Select. A 0 ("low") on this line selects
the ISAC-S TE for a read/write operation.
Read/Write. A 1 ("high"), identifies a valid
µP access as a read operation. A 0,
identifies a valid µP access as a write
operation (Motorola bus mode).
Write. This signal indicates a write
operation (Siemens/Intel bus mode).
39
29
DS
I
36
39
29
RD
I
20
23
8
INT
OD
Interrupt Request. The signal is activated
when the ISAC-S TE requests an interrupt.
It is an open drain output.
33
36
26
ALE
I
Address Latch Enable. A high on this line
indicates an address on the external
address bus (multiplexed bus type only).
ALE also selects interface mode.
40
30
A0
I
Address Bit 0 (non-multiplexed bus type).
6
51
A1
I
Address Bit 1 (non-multiplexed bus type).
5
50
A2
I
Address Bit 2 (non-multiplexed bus type).
18
64
A3
I
Address Bit 3 (non-multiplexed bus type).
17
63
A4
I
Address Bit 4 (non-multiplexed bus type).
10
55
A5
I
Address Bit 5 (non-multiplexed bus type).
35
Semiconductor Group
Data Strobe. The rising edge marks the
end of a valid read or write operation
(Motorola bus mode).
Read. This signal indicates a read
operation (Siemens/Intel bus mode).
116
Operational Description
3.2
Interrupt Structure and Logic
Since the ISAC-S TE provides only one interrupt request output (INT), the cause of an interrupt
is determined by the microprocessor by reading the Interrupt Status Register ISTA. In this
register, seven interrupt sources can be directly read. The LSB of ISTA points to eight noncritical interrupt sources which are indicated in the Extended Interrupt Register EXIR
(figure 42).
INT
RME
RPF
RSC
XPR
TIN
CISQ
SIN
EXI
MASK
RME
RPF
RSC
XPR
TIN
CISQ
SIN
EXI
ISTA
SQIE
XMR
XDU
PCE
RFO
SOV
MOS
SAW
WOV
EXIR
SQRR
C
O
D
R
0
MDR1
MER1
MDA1
MAB1
MDR0
MER0
MDA0
MAB0
MOSR
MRE1
MXE1
MRE0
MXE0
MOCR
Figure 42
ISAC®-S TE Interrupt Structure
Semiconductor Group
SQC
BAS
117
CI1E
CIC0
CIC1
SQXR
CIR0
R
IOM -2 only
CIR1
ITD02578
Operational Description
A read of the ISTA register clears all bits except EXI and CISQ. CISQ is cleared by reading
CIR0. A read of EXIR clears the EXI bit in ISTA as well as the EXIR register.
When all bits in ISTA are cleared, the interrupt line (INT) is deactivated.
Each interrupt source in ISTA register can be selectively masked by setting to "1" the
corresponding bit in MASK. Masked interrupt status bits are not indicated when ISTA is read.
Instead, they remain internally stored and pending, until the mask bit is reset to zero. Reading
the ISTA while a mask bit is active has no effect on the pending interrupt.
In the event of an extended interrupt and of a C/I- or S/Q channel change, EXI and CISQ are
set even when the corresponding mask bits in MASK are active, but no interrupt (INT) is
generated.
Except for CISQ and MOS all interrupt sources are directly determined by a read of ISTA and
(possibly) EXIR.
CISQ-Interrupt Logic
– A CISQ interrupt may originate
– from a change in the received S/Q code (SQC)
– from a change in the received C/I channel 0 code (CIC0)
or (in the case of IOM-2 terminal mode only)
– from a change in the received C/I channel 1 code (CIC1).
The three corresponding status bits SQC, CIC0 and CIC1 are read in the CIR0 register. SQC
and CIC1 can be individually disabled by clearing the enable bit SQIE (SQXR register) or,
respectively, CI1E (SQXR register). In this case the occurrence of a code change in SQRR/
CIR1 will not be displayed by SQC/CIC1 until the corresponding enable bit has been set to one.
Bits SQC, CIC0 and CIC1 are cleared by a read of CIR0.
An interrupt status is indicated every time a valid new code is loaded in SQRR, CIR0 or CIR1.
But in case of a code change, the new code is not loaded until the previous contents have been
read. When this is done and a second code change has already occurred, a new interrupt is
immediately generated and the new code replaces the previous one in the register. The code
registers are buffered with a FIFO size of two. Thus, if several consecutive codes are detected,
only the first and the last code is obtained at the first and second register read, respectively.
Semiconductor Group
118
Operational Description
MOS-Interrupt Logic
The MONITOR Data Receive (MDR) and the MONITOR End of Reception (MER) interrupt
status bits have two enable bits, MONITOR Receive interrupt Enable (MRE) and MR bit
Control (MRC). The MONITOR channel Data Acknowledged (MDA) and MONITOR channel
Data Abort (MAB) interrupt status bits have a common enable bit MONITOR Interrupt Enable
(MXE).
MRE prevents the occurrence of the MDR status, including when the first byte of a packet is
received. When MRE is active (1) but MRC is inactive, the MDR-interrupt status is generated
only for the first byte of a receive packet. When both MRE and MRC are active, MDR is
generated and all received monitor bytes – marked by a 1-to-0 transition in MX bit – are stored.
(Additionally, an active MRC enables the control of the MR handshake bit according to the
MONITOR channel protocol.)
Control of Edge-Triggered Interrupt Controllers
The INT output is level active. It stays active until all interrupt sources have been serviced. If
a new status bit is set while an interrupt is serviced, the INT line stays active. This may cause
problems if the ISAC-S TE is connected to edge-triggered interrupt controllers (figure 43).
To avoid these problems, it is recommended to mask all interrupts at the end of the interrupt
service program and to enable the interrupts again. This is done by writing FFH to the MASK
register and to write back the old value of the MASK register (figure 44).
Semiconductor Group
119
Operational Description
3
1
INT
5
2
4
ITD05430
➀
A status bit is set. This causes an interrupt.
➁
The microprocessor starts its service routine and reads the status registers.
➂
A new status bit is set before the first status bit has been read.
➃
The first status bit is read.
➄
The INT output stays active but the interrupt controller will not serve the interrupt
(edge triggered).
Figure 43
INT Handling
3
1
INT
2
4
5
6
7
8
9
ITD05431
➀
to ➃ see above
➄
’FF’ is written to the MASK register. This masks all interrupts and returns the INT
output to its inactive state.
➅
The old value is written to the MASK register. This will activate the INT output if
an interrupt source is still active.
➆
The microprocessor starts a new interrupt service program.
➇
The last status bit is read.
➈
The INT output is inactive.
Figure 44
Service Program for Edge-Triggered Interrupt Controllers
Semiconductor Group
120
Operational Description
~~
DCL
~~
INT
~~
RD
ITD02388
Figure 45
Timing of INT Pin
The INT line is switched with the rising edge of DCL. If no pending interrupts are internally
stored, a reading of ISTA respectively EXIR or CIR0 switches the INT line to high as indicated
in figure 45.
3.3
Control of Layer 1
3.3.1
Activation/Deactivation of IOM® Interface
The IOM interface can be switched off in the inactive state, reducing power consumption to a
minimum. In this deactivated state the clock line is low and the data lines are high.
The IOM interface can be kept active while the S interface is deactivated by setting the CFS
bit to "0" (SQXR register). This is the case after a hardware reset. If the IOM interface should
be switched off while the S interface is deactivated, the CFS bit should be set to "1". In this
case the internal oscillator is disabled when no signal (info 0) is present on the S bus. If the TE
wants to activate the line, it has first to activate the IOM interface either by using the "Software
Power-Up" function (SPCR:SPU bit) or by setting the CFS bit to "0" again.
For the TE case the deactivation procedure is shown in figure 46. After detecting the code DIU
(Deactivate Indication Upstream, i.e. from TE to NT/LT-S) the layer 1 of the ISAC-S TE
responds by transmitting DID (Deactivate Indication Downstream) during subsequent frames
and stops the timing signals synchronously with the end of the last C/I (C/I0) channel bit of the
fourth frame.
Semiconductor Group
121
Operational Description
R
IOM -2
Deactivated
FSC
DIU
DIU
DIU
DIU
DIU
DIU
DIU
DIU
DIU
DR
DR
DR
DR
DR
DID
DID
DID
DID
IDP1
(DU)
IDP0
(DD)
B1
B2
D
MONO
D CIO
CIO
DCL
ITD05963
Figure 46
Deactivation of the IOM® Interface
The clock pulses will be enabled again when the IDP1 line is pulled low (bit SPU, SPCR
register) i.e. the C/I command TIM = "0000" is received by layer 1, or when a non-zero level
on the S-line interface is detected. The clocks are turned on after approximately 0.2 to 4 ms
depending on the capacitances on XTAL 1/2.
DCL is activated such that its first rising edge occurs with the beginning of the bit following the
C/I (C/I0) channel.
After the clocks have been enabled this is indicated by the PU code in the C/I channel and,
consequently, by a CISQ interrupt. The IDP1 line may be released by resetting the Software
Power-Up bit SPCR:SPU=0, and the C/I code written in CIX0 is output on IDP1.
Semiconductor Group
122
Operational Description
CISQ CIS0 = TIM
Int. SPU = 0
~~
SPU = 1
FSC
TIM
TIM
PU
PU
PU
~~
IDP1
(DU)
TIM
~~
PU
PU
~~
IDP0
(DD)
~~
IOM -CH1
IOM -CH2
IOM -CH2
~~
~~
~~ ~~
IDP1
(DU)
~~ ~~
FSC
~~
R
R
B1
IDP0
(DD)
MR MX
~~
~~
0.2 to 4 ms
R
IOM -CH1
R
B1
~~
DCL
132 x DCL
R
Note : IDP0 is input and IDP1 is low during IOM -CH1 if SQXR : IDC = 1
R
IDP0 is low and IDP1 is input during IOM -CH1 if SQXR : IDC = 0
Figure 47
Activation of the IOM® Interface (CFS=1, register SQXR)
Semiconductor Group
123
ITD05962
Operational Description
The ISAC-S TE supplies IOM timing signals as long as there is no DIU command in the C/I (C/
I0) channel. If timing signals are no longer required and activation is not yet requested, this is
indicated by programming DIU in the CIX0 register.
As an alternative to activation via IDP1 (DU), the IOM interface can be activated by setting the
CFS bit to "0". The activation of FSC1 and DCL in this case is similar to figure 47. Note that
the IOM interface can be deactivated through DIU (power-down state, figure 46) only if CFS
is set to logical "1".
3.3.2
Activation/Deactivation of S/T Interface
Assuming the ISAC-S TE has been initialized with the required features of the application, it is
now ready to transmit and receive messages in the D channel (LAPD support).
But as a prerequisite, the layer 1 has to be activated.
The layer-1 functions are controlled by commands issued via the CIXR/CIX0 register. These
commands, sent over the IOM C/I channel 0 to layer 1, trigger certain procedures, such as
activation/deactivation, switching of test loops and transmission of special pulse patterns.
These are governed by layer-1 state diagrams in accordance with CCITT I.430. Responses
from layer 1 are obtained by reading the CIRR/CIR0 register after a CISQ interrupt (ISTA).
The state diagrams are shown in figure 49. The activation/deactivation implemented by the
ISAC-S TE agrees with the requirements set forth in CCITT recommendations. State identifiers
F1-F8 (TE) are in accordance with CCITT I.430.
In the state diagrams a notation is employed which explicitly specifies the inputs and outputs
on the S interface and in the C/I channel: see figure 48.
R
ISAC -S TE
OUT
C/ Ι
Ind.
R
ISAC -S TE
IN
Cmd.
State
S-INFO
iX
Unconditional
Transition
iY
ITD05676
Figure 48
Semiconductor Group
124
Operational Description
3.3.2.1
Layer-1 Command/Indication Codes and State Diagrams
Table 10
Commands
Command (upstream)
Abbr. Code
Remarks
Timing
TIM
0000
Activation of all output clocks is requested
Reset
RS
0001
(x)
Send continuous zeros
SCZ
0100
Transmission of pseudo-ternary pulses at
96-kHz frequency (x)
Send single zeros
SSZ
0010
Transmission of pseudo-ternary pulses at
2-kHz frequency (x)
Activate request, set priority 8
AR8
1000
Activation command,
priority to 8 (see note)
set
D-channel
Activate request, set priority 10
AR10
1001
Activation command,
priority to 10 (see note)
set
D-channel
Activate request loop
ARL
1010
Activation of test loop 3 (x)
Deactivate indication upstream
DIU
1111
IOM-interface clocks can be disabled
(x) unconditional commands
Important Note: When in the activated state (AI8/AI10 indication) the 2B+D channels are
only transferred from the IOM-2 to the S/T interface if an "Activate Request"
command is written to the CIX0 register.
Semiconductor Group
125
Operational Description
Table 11
Indications
Indication (downstream)
Abbr. Code
Remarks
Power-up
PU
0111
IOM clocking is provided
Deactivate request
DR
0000
Deactivation request by S interface
Error indication
EI
0110
Either: (pin RST = 1 and bit CFS = 0) or RS
Level detected
RSY
0100
Signal received, receiver not synchronous
Activate request downstream
ARD
1000
Info 2 received
Test indication
TI
1010
Test loop 3 activated or continuous zeros
transmitted
Awake test indication
ATI
1011
Level detected during test loop
Activate indication with
priority class 8
AI8
1100
Info 4 received, D-channel priority is 8 or 9
Activate indication with
priority class 10
AI10
1101
Info 4 received, D-channel priority is 10 or
11
Deactivate indication
downstream
DID
1111
Clocks will be disabled in TE, quiescent
state
Semiconductor Group
126
Operational Description
F3 Power-Down
This is the deactivated state of the physical protocol. The receive line awake unit is active
except during an RST pulse. Clocks are disabled if SQXR:CFS=1. The power consumption in
this state is approximately 80 mW when the clock is running, and 8 mW otherwise.
F3 Power-Up
This state is identical to "F3 power-down", except for the C/I-output message. The state is
invoked by a C/I command TIM = "0000" (or IDP1 static low). After the subsequent activation
of the clocks the PU message is outputted. This occurs 0.5 ms to 4 ms after application of TIM,
depending on crystal capacitances.
F3 Pending Deactivation
The ISAC-S TE reaches this state after receiving INFO0 (from states F5 to F8) for 16 ms (64
frames). This time constant is a "flywheel" to prevent accidental deactivation. From this state
an activation is only possible from the line (transition "F3 pend. deact." to "F5
unsynchronized"). A power-down state may be reached only after receiving DIU.
F4 Pending Activation
Activation has been requested from the terminal, INFO1 is transmitted, INFO0 is still received,
"Power-Up" is transmitted in the C/I channel. This state is stable: timer T3 (I.430) is to be
implemented in software.
F5 Unsynchronized
At the reception of any signal from the NT, the ISAC-S TE ceases to transmit INFO1 and awaits
identification of INFO2 or INFO4. This state is reached at most 50 µs after a signal different
from INFO0 is present at the receiver of the ISAC-S TE.
F6 Synchronized
When the ISAC-S TE receives an activation signal (INFO2), it responds with INFO3 and waits
for normal frames (INFO4). This state is reached at most 6 ms after an INFO2 arrives at the
ISAC-S TE (when the oscillator was disabled in "F3 power-down").
F7 Activated
This is the normal active state with the layer-1 protocol activated in both directions. Note that
in IOM-2 mode the 2B+D channels can only be transmitted to the S/T interface if an "Activation
Request" command is written to the CIX0 register. From state "F6 synchronized", state F7 is
reached at most 0.5 ms after reception of INFO4. From state "F3 power-down" with the
oscillator disabled, state F7 is reached at most 6 ms after the ISAC-S TE is directly activated
by INFO4.
Semiconductor Group
127
Operational Description
F8 Lost Framing
This is the condition where the ISAC-S TE has lost frame synchronization and is awaiting resynchronization by INFO2 or INFO4 or deactivation by INFO0.
Unconditional States
Loop 3 Closed
On Activate Request Loop command, INFO3 is sent by the line transmitter internally to the line
receiver (INFO0 is transmitted to the line). The receiver is not yet synchronized.
Loop 3 Activated
The receiver is synchronized on INFO3 which is looped back internally from the transmitter.
Data may be sent. The indication "TI" or "ATI" is output depending on whether or not a signal
different from INFO0 is detected on the S interface.
Test Mode Continuous Pulses
Continuous alternating pulses are sent.
Test Mode Single Pulses
Single alternating pulses are sent (2-kHz repetition rate).
Reset State
A software reset (RS) forces the ISAC-S TE to an idle state where the analog components are
disabled (transmission of INFO0) and the S line awake detector is inactive. Thus activation
from the NT is not possible. Clocks are still supplied (TE mode) and the outputs are in a low
impedance state.
The reset state should be left only with a "Deactivation Indication Upstream" (DIU) command
before any other command is given.
Semiconductor Group
128
Operational Description
DID
RST
DIU
TIM
F3 Power Down
i0
PU
ARU
i0
DIU
ARU
i0
DIU
TIM
F4 Pend. Act.
PU
TIM
DIS
F3 Power Up
ARU
i1
i0
i0
i0
i0
i0
RSYD
i4
X
F5 Unsynchroniz.
i0
i0
i0
i2
X
i0 DIU
i0
ARD
X
Uncond. States
TIM
F6 Synchronized
i3
i4
X
DR
i0
i0
F8 Lost Framing
i0
X
DIU
i0
i2
RSYD
i2
ARU
TIM
F3 Pend. Deact.
i0
i0
i0
OUT
IN
Ind.
Cmd.
i2
i4
SD
ARU
AID
F7 Activated
R
IOM -2
i0
State
i0
i3
S
i4
ix
iy
X: Unconditional Command
can be : ARL, RES,TM, SSP
ITD05429
Figure 49a
State Diagram
Semiconductor Group
129
Operational Description
PU
ARL
TI
ARL
SCZ
Loop 3 Closed
i3 1)
i3
*
SCZ
Test Mode
Continuous Puls.
ic
X
*
X
i3
TI
ATI
ARL
RS
EI
Reset State
Loop 3 Activated
i0
i3 1)
i0
i0
X
IOM
R
OUT
IN
Ind.
Cmd.
ix
*
X
SSZ
State
S
RS
iy
Any
Ind. SSZ
Test Mode
Single Pulses
is
*
X
: Only Internally
X : Forcing Commands
can be : ARL, RES, TM, SSP
is : Single Pulses, 4 kHz
ic : Test Pulses, 96 kHz
1)
ITD02333
Figure 49b
State Diagram: Unconditional Transitions
Semiconductor Group
130
Operational Description
3.3.3
Example of Activation/Deactivation
An example of an activation/deactivation of the S interface, with the time relationships
mentioned in the previous chapters, is shown in figure 50, in the case of an ISAC®-S TE in TE
and an ISAC-S in LT-S Mode.
R
R
ISAC -S TE
TE
ISAC -S / SBCX
LT-S
INFO 0
INFO 2
INFO 3
AID
AIU
0.5 ms
INFO 4
AR
max. 2 ms
ARD
max. 6 ms
RSYD
4 ms
INFO 1
ARU
DR
32 ms
INFO 0
16 ms
DR
16 ms
INFO 0
DIU
ITD05426
Figure 50
Example of Activation/Deactivation
Semiconductor Group
131
Operational Description
3.4
Control of Layer-2 Data Transfer
The control of the data transfer phase is mainly done by commands from the µP to ISAC-S TE
via the Command Register (CMDR).
Table 12 gives a summary of possible interrupts from the HDLC controller and the appropriate
reaction to these interrupts.
Table 13 lists the most important commands which are issued by a microprocessor by setting
one or several bits in CMDR.
The powerful FIFO logic, which consists of a 2 × 32 byte receive and 2 × 32 byte transmit FIFO,
as well as an intelligent FIFO controller, builds a flexible interface to the upper protocol layers
implemented in the microcontroller.
The extent of LAPD protocol support is dependent on the selected message transfer mode,
see section 2.3.2.
Table 12
Interrupts from ISAC®-S TE HDLC Controller
Mnemonic Register
(addr. hex)
Meaning
Reaction
Layer-2 Receive
RPF
ISTA
(20)
Receive Pool Full. Request to
read received bytes of an
uncompleted HDLC frame from
RFIFO
Read 32 bytes from RFIFO and
acknowledge with RMC.
RME
ISTA
(20)
Receive Message End. Request
to read received bytes of a
complete HDLC frame (or the
last part of a frame) from RFIFO.
Read RFIFO (number of bytes
given by RBCL4-0) and status
information and acknowledge
with RMC.
RFO
EXIR (24)
Receive Frame Overflow. A
complete frame has been lost
because storage space in
RFIFO was not available.
Error report for statistical
purposes. Possible cause:
deficiency in software.
PCE
EXIR (24)
Protocol Error. S- or I frame with Link re-establishment.
incorrect N(R) or S frame with
Indication to layer 3.
I field received (in auto-mode
only) or an I frame which is not a
command or S frame with an
undefined control field.
Semiconductor Group
132
Operational Description
Table 12 (cont’d)
Mnemonic Register
(addr. hex)
Meaning
Reaction
Layer-2 Transmit
XPR
ISTA
(20)
XMR
EXIR (24)
Transmit Message Repeat.
Transmission of the frame must
Frame must be repeated
be repeated. No indication to
because of a transmission error layer 3.
(all HDLC message transfer
modes) or a received negative
acknowledgement (auto mode
only) from peer station.
XDU
EXIR (24)
Transmit Data Underrun. Frame
has been aborted because the
XFIFO holds no further data and
XME (XIFC or XTFC) was not
issued.
RSC
ISTA
(20)
Receive Status Change.
Stop sending new I frames.
A status change from peer
station has been received (RR
or RNR frame), auto-mode only.
TIN
ISTA
(20)
Timer Interrupt. External timer
Link re-establishment.
expired or, in auto-mode,
Indication to layer 3. (autointernal timer (T200) and repeat mode)
counter (N200) both
expired.
Semiconductor Group
Transmit Pool Ready. Further
octets of an HDLC frame can be
written to XFIFO.
If XIFC was issued (auto mode),
indicates that the message was
successfully acknowledged with
S frame.
133
Write data bytes in the XFIFO if
the frame currently being
transmitted is not finished or a
new frame is to be transmitted,
and issue an XIF, XIFC, XTF or
XTFC command. In auto mode
applications read the
information in chapter 2.4.5.2.
Transmission of the frame must
be repeated. Possible cause:
excessive software reaction
times.
Operational Description
Table 13
List of Commands (CMDR (21) Register)
Command
Mnemonic
HEX
Bit 7…0
RMC
80
1000
0000 Receive Message Complete. Acknowledges a block
(RPF) or a frame (RME) stored in the RFIFO.
RRES
40
0100
0000 Reset HDLC Receiver. The RFIFO is cleared. The
transmit and receive counters (V(S), V(R)) are reset
(auto-mode).
RNR
20
0010
0000 Receiver Not Ready (auto-mode). An I- or S frame will be
acknowledged with RNR frame.
STI
10
0001
0000 Start Timer.
XTFC
(XTF+XME)
0A
0000
1010 Transmit Transparent Frame and Close. Enables the
"transparent" transmission of the block entered last in the
XFIFO. The frame is closed with a CRC and a flag.
XIFC
(XIF+XME)
06
0000
0110 Transmit I frame and Close. Enables the "auto-mode"
transmission of the block entered last in the XFIFO. The
frame is closed with a CRC and a flag.
XTF
08
0000
1000 Transmit Transparent Frame. Enables the "transparent"
transmission of the block entered last in the XFIFO
without closing the frame.
XIF
04
0000
0100 Transmit I frame. Enables the "auto-mode" transmission
of the block entered last in the XFIFO without closing the
frame.
XRES
01
0000
0001 Reset HDLC Transmitter. The XFIFO is cleared.
A frame currently in transmission will be aborted and
closed by an abort sequence (7 "1").
Semiconductor Group
Meaning
134
Operational Description
3.4.1
HDLC-Frame Reception
Assuming a normally running communication link (layer-1 activated, layer-2 link established,
TEI assigned), figure 51 illustrates the transfer of an I frame via the D channel. The transmitter
is shown on the left and the receiver on the right, with the interaction between the
microcontroller system and the ISAC-S TE in terms of interrupt and command stimuli.
When the frame (excluding the CRC field) is not longer than 32 bytes, the whole frame is
transferred in one block. The reception of the frame is reported via the Receive Message End
(RME) interrupt. The number of bytes stored in RFIFO can be read out from RBCL. The
Receive Status Register (RSTA) includes information about the frame, such as frame aborted
yes/no or CRC valid yes/no and, if complete or partial address recognition is selected, the
identification of the frame address.
Depending on the HDLC-message transfer mode, the address and control field of the frame
can be read from auxiliary registers (SAPR and RHCR), as shown in figure 52.
LAPD Link
RPF
XIF/XTF
XPR
R
ISAC -S
(LT-S)
R
XIF/XTF
me
ISAC -S TE
(TE)
I-Fra
µ CSystem
XPR
RMC
RPF
µ CSystem
RMC
XIFC/XTF
C
nsparent
XPR (Tra mit)
Trans
ame
S-Fr )*)
(RR
M
- ode
XPR (Automit)
Trans
RME
RMC
ITD05677
: = Data Transfer *) In Auto Mode the "RR" Response will be Transmitted Autonomously
Figure 51
Transmission of an I Frame in the D Channel (Subscriber to Exchange)
Semiconductor Group
135
Operational Description
Flag
Auto-Mode
(U-and
Ι-Frames)
-
Non-Auto
Mode
Transparent
Mode 1
Address
High
Address
Low
Control
Information
CRC
SAP1,SAP2
FE,FC
TEI1,TEI2
FF
RHCR
RFIFO
RSTA
(Note 1)
(Note 2)
(Note 3)
SAP1,SAP2
FE,FC
TEI1,TEI2
FF
RHCR
RFIFO
RSTA
(Note 1)
(Note 2)
(Note 4)
SAPR
TEI1,TEI2
FF
RHCR
RFIFO
RSTA
Flag
(Note 4)
Transparent
Mode 2
SAP1,SAP2
FE,FC
Transparent
Mode 3
RFIFO
RSTA
RFIFO
RSTA
Description of Symbols:
ITD05674
R
Checked automatically by ISAC -S TE
Compared with Register or Fixed Value
Stored Info Register or RFIFO
Figure 52
Receive Data Flow
Note 1
Only if a 2-byte address field is defined (MDS0 = 1 in MODE register).
Note 2
Comparison with Group TEI (FFH) is only made if a 2-byte address field is defined
(MDS0 = 1 in MODE register).
Note 3
In the case of an extended, modulo 128 control field format (MCS = 1 in SAP2
register) the control field is stored in RHCR in compressed form (I frames).
Note 4
In the case of an extended control field, only the first byte is stored in RHCR, the
second in RFIFO.
A frame longer than 32 bytes is transferred to the microcontroller in blocks of 32 bytes plus one
remainder block of length 1 to 32 bytes. The reception of a 32-byte block is reported by a
Receive Pool Full (RPF) interrupt and the data in RFIFO remains valid until this interrupt is
acknowledged (RMC). This process is repeated until the reception of the remainder block is
completed, as reported by RME (figure 51). When the total frame length exceeds 4095 bytes,
bit OV (RBCH) is set but the counter is not blocked. If the second RFIFO pool has been filled
or an end-of-frame is received while a previous RPF or RME interrupt is not yet acknowledged
by RMC, the corresponding interrupt will be generated only when RMC has been issued. When
Semiconductor Group
136
Operational Description
RME has been indicated, bits 0-4 of the RBCL register represent the number of bytes stored
in the RFIFO. Bits 7-5 of RBCL and bits 0 to 3 of RBCH indicate the total number of 32-byte
blocks which where stored until the reception of the remainder block.
The contents of RBCL, RBCH and RSTA registers are valid only after the occurrence of the
RME interrupt, and remain valid until the microprocessor issues an acknowledgement (RMC).
The contents of RHCR and/or SAPR, also remain valid until acknowledgement.
If a frame could not be stored due to a full RFIFO, the microcontroller is informed of this via the
Receive Frame Overflow interrupt (RFO).
3.4.2
HDLC-Frame Transmission
After the XFIFO status has been checked by polling the Transmit FIFO Write Enable (XFW) bit
or after a Transmit Pool Ready (XPR) interrupt, up to 32 bytes may be entered in XFIFO.
Transmission of an HDLC frame is started when a transmit command (see table 13) is issued.
The opening flag is generated automatically. In the case of an auto-mode transmission (XIF or
XIFC), the control field is also generated by the ISAC-S TE, and the contents of register XAD1
(and, for LAPD, XAD2) are transmitted as the address, as shown in figure 53.
HDLC Frame
Flag
Address
Control
Information
CRC
Flag
Transmit I-Frame
(XIF)
Auto Mode,8 - Bit Addr.
Flag
XAD1
Control
XFIFO
CRC
Flag
Transmit I-Frame
(XIF)
Auto -Mode, 16 - Bit Addr.
Flag
Control
XFIFO
CRC
Flag
Transmit Transparent
Frame (XTF)
All Modes
Flag
CRC
Flag
XAD1
XAD2
XFIFO
ITD05667
Note: Length of Control Field is b or 16 Bit
Description of Symbols:
R
Generated automatically by ISAC -S TE
Written initially by CPU (Info Register)
R
Loaded (repeatedly) by CPU upon ISAC -S TE
request (XPR Interrupt)
Figure 53
Transmit Data Flow
Semiconductor Group
137
Operational Description
The HDLC controller will request another data block by an XPR interrupt if there are no more
than 32 bytes in XFIFO and the frame close command bit (Transmit Message End XME) has
not been set. To this the microcontroller responds by writing another pool of data and reissuing a transmit command for that pool. When XME is set, all remaining bytes in XFIFO are
transmitted, the CRC field and the closing flag of the HDLC frame are appended and the
controller generates a new XPR interrupt.
The microcontroller does not necessarily have to transfer a frame in blocks of 32 bytes. As a
matter of fact, the sub-blocks issued by the microcontroller and separated by a transmit
command, can be between 0 and 32 bytes long.
If the XFIFO runs out of data and the XME command bit has not been set, the frame will be
terminated with an abort sequence (seven 1’s) followed by inter-frame time fill, and the
microcontroller will be advised by a Transmit Data Underrun (XDU) interrupt. An HDLC frame
may also be aborted by setting the Transmitter Reset (XRES) command bit.
3.5
Reset
After a hardware reset (pin RST), layer 1 will have reached the following state:
– F3 standby
according to CCITT I.430.
F3 standby state means that the internal oscillator, the DCL clock and FSC1 are active.
During the reset pulse pin SDS1 is "low", all other pins are in high impedance state. The S/T
interface awake detector is active after reset. The F3 power down state, where the internal
oscillator itself is disabled, can be reached by setting the CFS bit (SQXR register) to logical "1".
A subset of ISAC-S TE registers with defined reset values is listed in table 14.
Table 14
State of ISAC®-S TE Registers after Hardware Reset
Register (address (hex))
Value after
Reset (hex)
Meaning
ISTA
(20)
00
No interrupts
MASK
(20)
00
All interrupts enabled
EXIR
(24)
00
No interrupts
STAR
(21)
48 (4A)
– XFIFO is ready to be written to
– RFIFO is ready to receive at least 16 octets of
a new message
CMDR
(21)
00
No command
Semiconductor Group
138
Operational Description
Table 14 (cont’d)
Register (address (hex))
Value after
Reset (hex)
Meaning
MODE
(22)
00
– auto-mode
– 1-octet address field
– external timer mode
– receiver inactive
RBCL
RBCH
(25)
(2A)
00
XXX000002
– no frame bytes received
SPCR
(30)
00
– IDP1 pin = "High"
– Timing mode 0
– IOM interface test loop deactivated
– SDS1 pin = "Low"
CIR0
(31)
7C
– no change in S/Q channel
– another device occupies the D and C/I
channels
– received C/I code = "1111"
– no C/I code change
CIX0
(31)
3C
– TIC bus is not requested for transmitting a
C/I code
– transmitted C/I code = "1111"
STCR
(37)
00
– terminal specific functions disabled
– TIC-bus address = "0000"
– no synchronous transfer
ADF1
(38)
00
– no test mode
– active clock signals (standby) in TE mode
– no prefilter
– inter-frame time fill = continuous "1"
ADF2
(39)
00
– IOM-1 interface mode selected
– SDS1 low
SQXR
(3B)
0F/00
– S, Q interrupt not enabled
Semiconductor Group
139
Operational Description
3.6
Initialization
During initialization a subset of registers have to be programmed to set the configuration
parameters according to the application and desired features. They are listed in table 15.
After reset, the ISAC-S TE is in IOM-1 mode. As a result, the fist microcontroller operation has
to be an access to ADF2 to program IOM-2 interface mode.
Table 15
Application
Register (address)
Bit
Effect
ADF2
IMS
Program IOM-2 interface
mode
D1C2-0
ODS
Polarity of SDS1
IOM-output driver
tristate/open drain
SPU
Set the ISAC-S TE in
standby by requesting
clocks
(if CFS = 1, register SQXR)
TLP
IOM-interface test loop
C2C1-0
C1C1-0
B-channel switching or
B/IC channel connect
IDC
IOM-Data Port IDP0,1
direction control (must be
set to "0" for normal
operation)
CFS
0 Permanent standby
1 Power-down state
enabled
TEM
Test Mode
Tests with
layer
1 disabled
PFS
Prefilter enable
TE
IOF
IOM OFF/ON
RSS
Hardware reset generated
by either subscriber/
exchange awake or
watchdog timer
SPCR
(Note)
SQXR
ADF1
CIX0
(39H)
(30H)
(3BH)
(38H)
(31H)
Semiconductor Group
140
Restricted to
IOM-2
TE specific
functions
(TSF = 1)
Operational Description
Table 15 (cont’d)
Register (address)
Bit
Effect
STCR
TSF
Terminal specific function
enable
TBA2-0
TIC-bus address
MDS2-0
HDLC-message transfer
mode 2 bytes/1 byte address
TMD
Timer mode
external/internal
DIM2-0
Point-to-point/TIC-bus
configuration on IOM
interface, for D + C/I channel
arbitration
Point-to-point/bus
configuration on S/T
interface, for D-channel
access.
CNT
VALUE
N1 and T1 in internal timer
mode (TMD = 1)
T2 in external timer mode
MODE
(37H)
(22H)
Application
TIMR
(23H)
XAD1
XAD2
(24H)
(25H)
SAPI, TEI
Transmit frame address
SAP1/2
TEI1/2
(26H/27H)
(28H/29H)
Receive SAPI, TEI address
values for internal address
recognition
Restricted to
Bus
configuration
for D + C/I
(TIC)
Auto-mode
only
Auto-mode
only
Note: After a hardware reset the pin SDS1 is "low", until the SPCR is written to for the first
time. From that moment on, the function taken on by these pins depends on the state
of the IOM Mode Select bit IMS (ADF2 register).
Semiconductor Group
141
Register Description
4
Detailed Register Description
The parameterization of the ISAC-S TE and the transfer of data and control information
between the µP and ISAC-S TE is performed through two register sets.
The register set in the address range 00-2BH pertains to the HDLC transceiver and LAPD
controller. It includes the two FIFOs having an identical address range from 00-1FH.
The register set ranging from 30-3BH pertains to the control of layer-1 functions and of the IOM
interface.
The address map and a register summary are shown in the following tables:
Table 16
ISAC®-S TE Address Map 00-2BH
Address
(hex)
Read
Write
Name
Description
Name
Description
RFIFO
Receive FIFO
XFIFO
Transmit FIFO
20
ISTA
Interrupt Status Register
MASK
Mask Register
21
STAR
Status Register
CMDR
Command Register
22
MODE
Mode Register
23
TIMR
Timer Register
24
EXIR
Extended Interrupt
Register
XAD1
Transmit Address 1
25
RBCL
Receive Frame Byte Count
Low
XAD2
Transmit Address 2
26
SAPR
Received SAPI
SAP1
Individual SAPI 1
27
RSTA
Receive Status Register
SAP2
Individual SAPI 2
TEI1
Individual TEI 1
TEI2
Individual TEI 2
00
.
.
1F
28
29
RHCR
Receive HDLC Control
2A
RBCH
Receive Frame Byte Count
High
2B
STAR2
Status Register 2
Semiconductor Group
142
Register Description
Table 17
ISAC®-S TE Address Map 30-3BH
Address
(hex)
Read
Write
Name
Description
Name
Description
30
SPCR
Serial Port Control Register
31
CIR0
Command/Indication
Receive 0
CIX0
Command/Indication
Transmit 0
32
MOR0
MONITOR Receive 0
MOX0
MONITOR Transmit 0
33
CIR1
Command/Indication
Receive 1
CIX1
Command/Indication
Transmit 1
34
MOR1
MONITOR Receive 1
MOX1
MONITOR Transmit 1
35
C1R
Channel Register 1
36
C2R
Channel Register 2
37
B1CR
B1-Channel Register
STCR
Sync Transfer Control
Register
38
B2CR
B2-Channel Register
ADF1
Additional Feature Register 1
39
ADF2
Additional Feature Register 2
3A
MOSR
MONITOR Status Register
MOCR
MONITOR Control Register
3B
SQRR
S-, Q-Channel Receive
Register
SQXR
S-, Q-Channel Transmit
Register
Semiconductor Group
143
Register Description
Table 18
Register Summary: HDLC Operation and Status Registers
7
0
20H
RME
RPF
RSC
XPR
TIN
CISQ
SIN
EXI
ISTA
R
20H
RME
RPF
RSC
XPR
TIN
CISQ
SIN
EXI
MASK
W
21H
XDOV
XFW
MBR
MAC1
X
MAC0
STAR
R
21H
RMC
RRES
RNR
STI
XTF
XIF
XME
XRES
CMDR W
22H
MDS2
MDS1
MDS0
TMD
RAC
DIM2
DIM1
DIM0
MODE R/W
23H
XRNR RRNR
TIMR
R/W
EXIR
R
XAD1
W
RBCL
R
25H
XAD2
W
26H
SAPR
R
24H
CNT
XMR
XDU
VALUE
PCE
RFO
SOV
MOS
SAW
WOV
24H
25H
RBC7
RBC6
RBC5
26H
27H
RBC4
RBC3
RBC2
SAPI1
RDA
RDO
CRC
27H
RAB
SA1
SA0
SAPI2
28H
RBC1
RBC0
CRI
0
SAP1
W
C/R
TA
RSTA
R
MCS
0
SAP2
W
EA
TEI1
W
TEI1
29H
RHCR R
29H
EA
TEI2
TEI2
W
R
2AH
XAC
VN1
VN0
OV
RBC1
RBC1
RBC9
RBC8
RBCH
2BH
0
0
0
0
WFA
MULT
TREC
SDET
STAR2 R
2BH
0
0
0
0
0
MULT
0
0
STAR2 W
Semiconductor Group
144
Register Description
Table 19
Register Summary: Special Purpose Register IOM®-2 Mode
IOM®-2:
7
0
30H
SPU
0
31H
SQC
BAS
31H
RSS
BAC
0
TLP
C1C1
C1C0
C2C1
C2C0
SPCR
R/W
CODR0
CIC0
CIC1
CIR0
R
CODX0
1
1
CIX0
W
32H
MOR0 R
32H
MOX0
W
33H
CODR1
MR1
MX1
CIR1
R
33H
CODX1
1
1
CIX1
W
34H
MOR1 R
34H
MOX1
W
35H
C1R
R/W
36H
C2R
R/W
37H
B1CR
R
STCR
W
B2CR
R
37H
TSF
TBA2
TBA1
TBA0
ST1
ST0
SC1
SC0
38H
38H
WTC1
WTC2
TEM
PFS
IOF
0
0
ITF
ADF1
W
39H
IMS
0
0
0
ODS
D1C2
D1C1
D1C0
ADF2
R/W
3AH
MDR1
MER1
MDA1
MAB1
MDR0
MER0
MDA0
MAB0
MOSR R
3AH
MRE1
MRC1
MXE1
MXC1
MRE0
MRC0
MXE0
MXC0
MOCR W
3BH
IDC
CFS
CI1E
SYN
SQR1
SQR2
SQR3
SQR4
SQRR R
3BH
IDC
CFS
CI1E
SQIE
SQX1
SQX2
SQX3
SQX4
SQXR W
Semiconductor Group
145
Register Description
4.1
HDLC Operation and Status Registers
4.1.1
Receive FIFO
RFIFO
Read
Address 00-1FH
A read access to any address within the range 00-1FH gives access to the "current" FIFO
location selected by an internal pointer which is automatically incremented after each read
access. This allows for the use of efficient ’move string’ type commands by the processor.
The RFIFO contains up to 32 bytes of received frame.
After an ISTA:RPF interrupt, exactly 32 bytes are available.
After an ISTA:RME interrupt, the number of bytes available can be obtained by reading the
RBCL register.
4.1.2
Transmit FIFO
XFIFO
Write
Address 00-1FH
A write access to any address within the range 00-1FH gives access to the "current" FIFO
location selected by an internal pointer which is automatically incremented after each write
access. This allows for the use of efficient ’move string’ type commands by the processor.
Up to 32 bytes of transmit data can be written into the XFIFO following an ISTA:XPR interrupt.
4.1.3
Interrupt Status Register
ISTA
Read
Address 20H
Value after reset: 00H
7
0
RME
RME
RPF
RSC
XPR
TIN
CISQ
SIN
EXI
Receive Message End
One complete frame of length less than or equal to 32 bytes, or the last part of a frame
of length greater than 32 bytes has been received. The contents are available in the
RFIFO. The message length and additional information may be obtained from
RBCH + RBCL and the RSTA register.
RPF
Receive Pool Full
A 32-byte block of a frame longer than 32 bytes has been received and is available
in the RFIFO. The frame is not yet complete.
RSC
Receive Status Change. Used in auto-mode only.
A status change in the receiver of the remote station – Receiver Ready/Receiver Not
Ready – has been detected (RR or RNR S frame).
The actual status of the remote station can be read from the STAR register (RRNR
bit).
Semiconductor Group
146
Register Description
XPR
Transmit Pool Ready
A data block of up to 32 bytes can be written to the XFIFO.
An XPR interrupt will be generated in the following cases:
– after an XTF or XIF command, when one transmit pool is emptied and the frame is
not yet complete
– after an XTF together with an XME command is issued, when the whole
transparent frame has been transmitted
– after an XIF together with an XME command is issued, when the whole I frame has
been transmitted and a positive acknowledgement from the remote station has
been received, (auto-mode).
TIN
Timer Interrupt
The internal timer and repeat counter has expired (see TIMR register).
CISQ
C/I- or S/Q-Channel Change
A change in C/I channel 0, C/I channel 1 (only in IOM-2 TE mode) or S/Q channel has
been recognized. The actual value can be read from CIR0, CIR1 or SQRR.
SIN
Synchronous Transfer Interrupt
When programmed (STCR register), this interrupt is generated to enable the
processor to lock on to the IOM timing, for synchronous transfers.
EXI
Extended Interrupt
This bit indicates that one of six non-critical interrupts has been generated. The exact
interrupt cause can be read from EXIR.
Note:
A read of the ISTA register clears all bits except EXI and CISQ. EXI is cleared by
reading the EXIR register, CISQ is cleared by reading CIRR/CIR0.
4.1.4
Mask Register
MASK
Write
Address 20H
Value after reset: 00H
7
0
RME
RPF
RSC
XPR
TIN
CISQ
SIN
EXI
Each interrupt source in the ISTA register can be selectively masked by setting to "1"
the corresponding bit in MASK. Masked interrupt status bits are not indicated when
ISTA is read. Instead, they remain internally stored and pending, until the mask bit is
reset to zero.
Note:
In the event of an extended interrupt and of a C/I- or S/Q-channel change, EXI and
CISQ are set in ISTA even if the corresponding mask bits in MASK are active, but no
interrupt (INT pin) is generated.
Semiconductor Group
147
Register Description
4.1.5
Status Register
STAR
Read
Address 21H
Value after reset: 48H or 4A H
7
XDOV
XDOV
0
XFW
XRNR RRNR
MBR
MAC1
X
MAC0
Transmit Data Overflow
More than 32 bytes have been written in one pool of the XFIFO, i.e. data has been
overwritten.
XFW
Transmit FIFO Write Enable
Data can be written in the XFIFO. This bit may be polled instead of (or in addition to)
using the XPR interrupt.
XRNR
Transmit RNR. Used in auto-mode only
In auto-mode, this bit indicates whether the ISAC-S TE receiver is in the "ready" (0)
or "not ready" (1) state. When "not ready", the ISAC-S TE sends an RNR S frame
autonomously to the remote station when an I frame or an S frame is received.
RRNR
Receive RNR. Used in auto-mode only
In the auto-mode, this bit indicates whether the ISAC-S TE has received an RR or an
RNR frame, this being an indication of the current state of the remote station: receiver
ready (0) or receiver not ready (1).
MBR
Message Buffer Ready
This bit signifies that temporary storage is available in the RFIFO to receive at least
the first 16 bytes of a new message.
MAC1
MONITOR Transmit Channel 1 Active (IOM-2 terminal mode only)
Data transmission is in progress in MONITOR channel 1.
MAC0
MONITOR Transmit Channel 0 Active. Used in IOM-2 mode only.
Data transmission is in progress in MONITOR channel 0.
Note:
Bit 1 may toggle dependend the time of access.
Semiconductor Group
148
Register Description
4.1.6
Command Register
CMDR
Write
Address 21H
Value after reset: 00H
7
0
RMC
RRES
RNR
STI
XTF
XIF
XME
XRES
Note:
The maximum time between writing to the CMDR register and the execution of the
command is 2.5 DCL-clock cycles. During this time no further commands should be
written to the CMDR register to avoid any loss of commands.
RMC
Receive Message Complete
Reaction to RPF (Receive Pool Full) or RME (Receive Message End) interrupt. By
setting this bit, the processor confirms that it has fetched the data, and indicates that
the corresponding space in the RFIFO may be released.
RRES
Receiver Reset
HDLC receiver is reset, the RFIFO is cleared of any data.
In addition, in auto-mode, the transmit and receive counters (V(S), V(R)) are reset
RNR
Receiver Not Ready
Used in auto-mode only.
Determines the state of the ISAC-S TE HDLC receiver.
When RNR = "0", a received I or S-frame is acknowledged by an RR supervisory
frame, otherwise by an RNR supervisory frame.
STI
Start Timer
The ISAC-S TE hardware timer is started when STI is set to one. In the internal timer
mode (TMD bit, MODE register) an S command (RR, RNR) with poll bit set is
transmitted in addition. The timer may be stopped by a write of the TIMR register.
XTF
Transmit Transparent Frame
After having written up to 32 bytes in the XFIFO, the processor initiates the
transmission of a transparent frame by setting this bit to "1". The opening flag is
automatically added to the message by the ISAC-S TE.
XIF
Transmit I Frame
Used in auto-mode only
After having written up to 32 bytes in the XFIFO, the processor initiates the
transmission of an I frame by setting this bit to "1". The opening flag, the address and
the control field are automatically added by the ISAC-S TE.
Semiconductor Group
149
Register Description
XME
Transmit Message End
By setting this bit to "1" the processor indicates that the data block written last in the
XFIFO completes the corresponding frame. The ISAC-S TE terminates the
transmission by appending the CRC and the closing flag sequence to the data.
XRES
Transmitter Reset
HDLC transmitter is reset and the XFIFO is cleared of any data.
This command can be used by the processor to abort a frame currently in
transmission.
Notes: ● After an XPR interrupt further data has to be written in the XFIFO and the
appropriate Transmit Command (XTF or XIF) has to be written in the CMDR
register again to continue transmission, when the current frame is not yet complete
(see also XPR in ISTA).
●
4.1.7
During frame transmission, the 0-bit insertion according to the HDLC bit-stuffing
mechanism is done automatically.
Mode Register
MODE
Read/Write Address 22H
Value after reset: 00H
7
0
MDS2
MDS1
MDS0
TMD
RAC
DIM2
DIM1
DIM0
MDS2-0 Mode Select
Determines the message transfer mode of the HDLC controller, as follows:
Semiconductor Group
150
Register Description
MDS2
MDS1
MDS0
Mode
Number
Address Comparison
of
1. Byte
2. Byte
Address
Bytes
Remark
0 0 0 Auto-mode
1
TEI1, TEI2
–
One-byte address
compare. HDLC-protocol
handling for frames with
address TEI1
0 0 1 Auto-mode
2
SAP1, SAP2, SAPG
TEI1, TEI2, TEIG
Two-byte address
compare. LAPD-protocol
handling for frames with
address SAP1 + TEI1
0 1 0 Non-auto
1
TEI1, TEI2
–
One-byte address
compare.
2
SAP1, SAP2, SAPG
TEI1, TEI2, TEIG
Two-byte address
compare.
>1
–
TEI1, TEI2, TEIG
Low-byte address
compare.
–
–
–
No address compare.
All frames accepted.
>1
SAP1, SAP2, SAPG
–
High-byte address
compare.
mode
0 1 1 Non-auto
mode
1 0 0 Reserved
1 0 1 Transparent
mode 1
1 1 0 Transparent
mode 2
1 1 1 Transparent
mode 3
Note:
SAP1, SAP2: two programmable address values for the first received address byte
(in the case of an address field longer than 1 byte); SAPG = fixed value FC/FEH.
TEI1, TEI2: two programmable address values for the second (or the only, in the case
of a one-byte address) received address byte; TEIG = fixed value FFH.
TMD
Timer Mode
Sets the operating mode of the ISAC-S TE timer. In the external mode (0) the timer
is controlled by the processor. It is started by setting the STI bit in CMDR and it is
stopped by a write of the TIMR register.
In the internal mode (1) the timer is used internally by ISAC-S TE for timeout and retry
conditions (handling of LAPD/HDLC protocol in auto-mode).
RAC
Receiver Active
The HDLC receiver is activated when this bit is set to "1".
DIM2-0 Digital Interface Mode
These bits define the characteristics of the IOM-Data Ports (IDP0, IDP1) according to
following tables:
Semiconductor Group
151
Register Description
IOM®-2 Modes (ADF2:IMS = 1)
DIM2-0
Characteristics
000
001
010
011
IOM-2 terminal mode
SPCR:SPM = 0
×
×
×
×
Last octet of IOM channel 2
used for TIC-bus access
×
×
×
×
Stop/go bit evaluated for
D-channel access handling
100-111
×
Reserved
Applications
4.1.8
×
×
TE mode
Timer Register
TIMR
Value after reset: undefined (previous value)
7
0
CNT
CNT
Read/Write Address 23H
VALUE
The meaning depends on the selected timer mode (TMD bit, MODE register).
* internal Timer Mode (TMD = 1)
CNT indicates the maximum number of S commands "N1" which are transmitted
autonomously by the ISAC-S TE after expiration of time period T1 (retry, according
to HDLC).
Semiconductor Group
152
Register Description
The internal timer procedure will be started in auto-mode:
– after start of an I-frame transmission
or
– after an "RNR" S frame has been received.
After the last retry, a timer interrupt (TIN bit in ISTA) is generated.
The timer procedure will be stopped when
– a TIN interrupt is generated. The time between the start of an I-frame
transmission or reception of an "RNR" S frame and the generation of a TIN
interrupt is equal to: (CNT+1) × T1.
– or the TIMR is written
– or a positive or negative acknowledgement has been received.
Note: The maximum value of CNT can be 6. If CNT is set to 7, the number of retries
is unlimited.
* External Timer Mode (TMD = 0)
CNT together with VALUE determine the time period T2 after which a TIN interrupt
will be generated:
CNT × 2.048 s + T1
with T1 = (VALUE + 1) × 0.064 s,
in the normal case, and
T2 = 16348 × CNT × DCL + T1
with T1 = 512 × (VALUE + 1) × DCL
when TLP = 1 (test loop activated, SPCR register).
DCL denotes the period of the DCL clock.
The timer can be started by setting the STI bit in CMDR and will be stopped when a
TIN interrupt is generated or the TIMR register is written.
Note: If CNT is set to 7, a TIN interrupt is indefinitely generated after every
expiration of T1.
VALUE Determines the Time Period T1:
T1 = (VALUE + 1) × 0.064 s (SPCR:TLP = 0, normal mode)
T1 = 512 × (VALUE + 1) × DCL (SPCR:TLP = 1, test mode).
Semiconductor Group
153
Register Description
4.1.9
Extended Interrupt Register
EXIR
Read
Address 24H
Value after reset: 00H
7
0
XMR
XMR
XDU
PCE
RFO
SOV
MOS
SAW
WOV
Transmit Message Repeat
The transmission of the last frame has to be repeated because:
– the ISAC-S TE has received a negative acknowledgement to an I frame in automode (according to HDLC/LAPD)
– or a collision on the S bus has been detected after the 32nd data byte of a transmit
frame.
XDU
Transmit Data Underrun
The current transmission of a frame is aborted by transmitting seven "1's" because
the XFIFO holds no further data. This interrupt occurs whenever the processor has
failed to respond to an XPR interrupt (ISTA register) quickly enough, after having
initiated a transmission and the message to be transmitted is not yet complete.
Note:
When an XMR or and XDU interrupt is generated, it is not possible to send
transparent frames or I frames until the interrupt has been acknowledged by reading
EXIR.
PCE
Protocol Error
Used in auto-mode only.
A protocol error has been detected in auto-mode due to a received
– S- or I frame with an incorrect sequence number N(R) or
– S frame containing an I field.
– I frame which is not a command.
– S frame with an undefined control field.
RFO
Receive Frame Overflow
The received data of a frame could not be stored, because the RFIFO is occupied.
The whole message is lost.
This interrupt can be used for statistical purposes and indicates that the processor
does not respond quickly enough to an RPF or RME interrupt (ISTA).
SOV
Synchronous Transfer Overflow
The synchronous transfer programmed in STCR has not been acknowledged in time
via the SC0/SC1 bit.
MOS
MONITOR Status
A change in the MONITOR Status Register (MOSR) has occured.
Semiconductor Group
154
Register Description
SAW
Subscriber Awake
Used only if terminal specific functions are enabled (STCR:TSF = 1).
Indicates that a falling edge on the EAW line has been detected, in case the terminal
specific functions are enabled (TSF bit in STCR).
WOV
Watchdog Timer Overflow
Used only if terminal specific functions are enabled (STCR:TSF = 1).
Signals the expiration of the watchdog timer, which means that the processor has
failed to set the watchdog timer control bits WTC1 and WTC2 (ADF1 register) in the
correct manner. A reset pulse has been generated by the ISAC-S TE.
4.1.10
Transmit Address 1
XAD1
Write
Address 24H
7
0
Used in auto-mode only.
XAD1 contains a programmable address byte which is appended automatically to the
frame by the ISAC-S TE in auto-mode. Depending on the selected address mode
XAD1 is interpreted as follows:
* 2-Byte Address Field
XAD1 is the high byte (SAPI in the ISDN) of the 2-byte address field. Bit 1 is
interpreted as the command/response bit "C/R". It is automatically generated by the
ISAC-S TE following the rules of ISDN LAPD protocol and the CRI bit value in SAP1
register. Bit 1 has to be set to "0".
C/R Bit
Command
Response
Transmitting End
CRI Bit
0
1
subscriber
0
1
0
network
1
In the ISDN LAPD the address field extension bit "EA", i.e. bit 0 of XAD1 has to be
set to "0".
* 1-Byte Address Field
According to the X.25 LAPB protocol, XAD1 is the address of a command frame.
Note: In standard ISDN applications only 2-byte address fields are used.
Semiconductor Group
155
Register Description
4.1.11
Receive Frame Byte Count Low
RBCL
Read
Address 25H
Value after reset: 00H
7
0
RBC7
RBC6
RBC5
RBC4
RBC3
RBC2
RBC1
RBC0
RBC7-0 Receive Byte Count
Eight least significant bits of the total number of bytes in a received message. Bits
RBC4-0 indicate the length of the data block currently available in the RFIFO, the
other bits (together with RBCH) indicate the number of whole 32-byte blocks
received.
If exactly 32 bytes are received RBCL holds the value 20H.
4.1.12
Transmit Address 2
XAD2
Write
7
Address 25H
0
Used in auto-mode only.
XAD2 contains the second programmable address byte, whose function depends on
the selected address mode:
* 2-Byte Address Field
XAD2 is the low byte (TEI in the ISDN) of the 2-byte address field.
* 1-Byte Address Field
According to the X.25 LAPB protocol, XAD2 is the address of a response frame.
Note: See note to XAD1 register description.
4.1.13
Received SAPI Register
SAPR
7
Read
Address 26H
0
When transparent mode 1 is selected, SAPR contains the value of the first address
byte of a receive frame.
Semiconductor Group
156
Register Description
4.1.14
SAPI1 Register
SAP1
Write
Address 26H
7
0
SAPI1
SAPI1
CRI
0
SAPI1 Value
Value of the first programmable Service Access Point Identifier (SAPI) according to
the ISDN LAPD protocol.
CRI
Command/Response Interpretation
CRI defines the end of the ISDN user-network interface the ISAC-S TE is used on,
for the correct identification of "Command" and "Response" frames. Depending on
the value of CRI the C/R bit will be interpreted by the ISAC-S, when receiving frames
in auto-mode, as follows:
C/R Bit
CRI Bit
Receiving End
Command
Response
0
subscriber
1
0
1
network
0
1
For transmitting frames in auto-mode, the C/R-bit manipulation will also be done
automatically, depending on the value of the CRI bit (refer to XAD1-register
description).
In message transfer modes with SAPI address recognition the first received address
byte is compared with the programmable values in SAP1, SAP2 and the fixed group
SAPI.
In 1-byte address mode, the CRI bit is to be set to "0".
4.1.15
Receive Status Register
RSTA
Read
Address 27H
Value after reset: undefined
7
RDA
RDA
RDO
0
CRC
RAB
SA1
SA0
C/R
TA
Receive Data
A "1" indicates that data is available in the RFIFO. After an RME interrupt, a "0" in this
bit means that data is available in the internal registers RHCR or SAPR only (e.g.
S frame). See also RHCR-register description table.
RDO
Receive Data Overflow
At least one byte of the frame has been lost, because it could not be stored in RFIFO
(1).
Semiconductor Group
157
Register Description
CRC
CRC Check
The CRC is correct (1) or incorrect (0).
RAB
Receive Message Aborted
The receive message was aborted by the remote station (1), i.e. a sequence of 7 1’s
was detected.
SA1-0
SAPI Address Identification
TA
TEI Address Identification
SA1-0 are significant in auto-mode and non-auto mode with a two-byte address field,
as well as in transparent mode 3. TA is significant in all modes except in transparent
modes 2 and 3.
Two programmable SAPI values (SAP1, SAP2) plus a fixed group SAPI (SAPG of
value FC/FEH), and two programmable TEI values (TEI1, TEI2) plus a fixed group
TEI (TEIG of value FFH), are available for address comparison.
The result of the address comparison is given by SA1-0 and TA, as follows
Address Match with
Number of address
bytes = 1
Number of address
bytes = 2
SA1
SA0
TA
1st Byte
2nd Byte
x
x
x
x
0
1
TEI2
TEI1
–
–
0
0
0
0
1
1
1
0
0
1
1
0
0
1
0
1
0
1
0
1
x
SAP2
SAP2
SAPG
SAPG
SAP1
SAP1
TEIG
TEI2
TEIG
TEI1 or TEI2
TEIG
TEI1
reserved
Notes: ● If the SAPI values programmed to SAP1 and SAP2 are identical the reception of a
frame with SAP2/TEI2 results in the indication SA1 = 1, SA0 = 0, TA = 1.
●
Normally RSTA should be read by the processor after an RME interrupt in order to
determine the status of the received frame. The contents of RSTA are valid only
after an RME interrupt, and remain so until the frame is acknowledged via the RMC
bit.
Semiconductor Group
158
Register Description
C/R
Command/Response
The C/R bit identifies a receive frame as either a command or a response, according
to the LAPD rules:
4.1.16
Command
Response
Direction
0
1
Subscriber to network
1
0
Network to subscriber
SAPI2 Register
SAP2
Write
Address 27H
7
0
SAPI2
SAPI2
MCS
0
SAPI2 Value
Value of the second programmable Service Access Point Identifier (SAPI) according
to the ISDN LAPD protocol.
MCS
Modulo Count Select
Used in auto-mode only.
This bit determines the HDLC-control field format as follows:
0: One-byte control field (modulo 8)
1: Two-byte control field (modulo 128)
4.1.17
TEI1 Register 1
TEI1
Write
Address 28H
7
0
TEI1
EA
EA
Address Field Extension Bit
This bit has to be set "1" according to HDLC/LAPD.
In all message transfer modes except in transparent modes 2 and 3, TEI1 is used by
the ISAC-S for address recognition. In the case of a two-byte address field, it contains
the value of the first programmable Terminal Endpoint Identifier according to the
ISDN LAPD protocol.
In the auto-mode with a two-byte address field, numbered frames with the address
SAPI1-TEI1 are handled autonomously by the ISAC-S TE according to the LAPD
protocol.
Semiconductor Group
159
Register Description
Note:
If the value FFH is programmed in TEI1, received numbered frames with address
SAPI1-TEI1 (SAPI1-TEIG) are not handled autonomously by the ISAC-S TE.
In auto and non-auto-modes with one-byte address field, TEI1 is a command
address, according to X.25 LAPB.
4.1.18
Receive HDLC Control Register
RHCR
7
Read
Address 29 H
0
In all modes except transparent modes 2 and 3, this register contains the control field of a
received HDLC frame. In transparent modes 2 and 3, the register is not used.
SAPI1
Contents of RHCR
Mode
Modulo 8
(MCS = 0)
Modulo 128
(MCS = 1)
Contents of RFIFO
Auto-mode,
Control field
1-byte address
(U/I frames)
(Note 1)
U-frames only:
From 3rd byte after flag
Control field
(Note 4)
(Note 2)
Auto-mode,
Control field
2-byte address
(U/I frames)
(Note 1)
U-frames only:
From 4th byte after flag
Control field
(Note 4)
(Note 2)
Auto-mode,
1-byte address
(I frames)
Control field in
From 4th byte after flag
compressed form
(Note 4)
(Note 3)
Auto-mode,
2-byte address
(I frames)
Control field in
From 5th byte after flag
compressed form
(Note 4)
(Note 3)
Non-auto mode,
1-byte address
2nd byte after flag
From 3rd byte after flag
Non-auto mode,
2-byte address
3rd byte after flag
From 4th byte after flag
Transparent mode 1 3rd byte after flag
From 4th byte after flag
Transparent mode 2 –
From 1st byte after flag
Transparent mode 3 –
From 2nd byte after flag
Semiconductor Group
160
Register Description
Note 1: S frames are handled automatically and are not transferred to the microprocessor.
Note 2: For U frames (bit 0 of RHCR = 1) the control field is as in the modulo 8 case.
Note 3: For I frames (bit 0 of RHCR = 0) the compressed control field has the same format
as in the modulo 8 case, but only the three LSB’s of the receive and transmit counters
are visible:
7
0
N(R)2-0
P
N(S)2-0
0
Note 4: I field.
4.1.19
TEI2 Register
TEI2
Write
Address 29H
7
0
EA
TEI2
EA
Address Field Extension Bit
This bit is to be set to "1" according to HDLC/LAPD.
In all message transfer modes except in transparent modes 2 and 3, TEI2 is used by the
ISAC-S TE for address recognition. In the case of a two-byte address field, it contains the
value of the second programmable Terminal Endpoint Identifier according of the ISDN LAPD
protocol.
In auto and non-auto modes with one-byte address field, TEI2 is a response address,
according to X.25 LAPB.
4.1.20
Receive Frame Byte Count High
RBCH
Read
Address 2AH
Value after reset: 0XX000002.
7
0
XAC
XAC
VN1
VN0
OV
RBC11 RBC10 RBC9
RBC8
Transmitter Active
The HDLC transmitter is active when XAC = 1. This bit may be polled. The XAC bit is
active when
– either an XTF/XIF command is issued and the frame has not been completely
transmitted
– or the transmission of an S frame is internally initiated and not yet completed.
VN1-0
Version Number of Chip
00 ... V1.1 version
Semiconductor Group
161
Register Description
OV
Overflow
A "1" in this bit position indicates a message longer than 4095 bytes.
RBC8-11Receive Byte Count
Four most significant bits of the total number of bytes in a received message.
Note:
Normally RBCH and RBCL should be read by the processor after an RME interrupt
in order to determine the number of bytes to be read from the RFIFO, and the total
message length. The contents of the registers are valid only after an RME interrupt,
and remain so until the frame is acknowledged via the RMC bit.
4.1.21
Status Register 2
STAR2
Read/Write Address 2BH
Value after reset: 00H
a) WRITE
7
0
0
MULT
0
0
0
0
MULT
0
0
Used to enable or disable the multiframe structure (see chapter 2.4.9)
1: S/T multiframe disabled
0: S/T multiframe enabled
b) READ
7
0
0
0
0
0
WFA
MULT
TREC
SDET
WFA
Waiting for Acknowledge
This bit shows, if the last transmitted I frame was acknowledged, i.e. V(A) = V(S)
(⇒ WFA = 0) or was not yet acknowledged, i.e. V(A) < V(S) (⇒ WFA = 1).
MULT
The value written into the register bit is read.
TREC
Timer Recovery Status:
0: The device is not in the timer recovery state.
1: The device is in the timer recovery state.
SDET
S Frame Detected:
This bit is set to "1" by the first received correct I frame or S command with p = 1.
It is reset by reading STAR2.
Semiconductor Group
162
Register Description
4.2
Special Purpose Registers: IOM®-2 Mode
The following register description is only valid if IOM-2 is selected (ADF2:IMS-1).
4.2.1
Serial Port Control Register
Value after reset:
SPCR
Read/Write Address 30H
00H
7
0
SPU
Important Note
SPU
0
0
TLP
C1C1
C1C0
C2C1
C2C0
After a hardware reset the pin SDS1 is "low" until the SPCR is written to for
the first time. From that moment on, the function taken on by these pins depends on the state of the IOM Mode Select bit IMS (ADF2 register).
Software Power-Up.
Used in TE mode only.
If SQXR:CFS = 1, before activating the ISDN S interface in TE mode the SPU and
SQXR:IDC bits have to be set to "1" and then cleared again:
After a subsequent CISQ interrupt (C/I code change; ISTA) and reception of the C/I
code "PU" (Power-Up indication in TE mode) the reaction of the processor would be:
TLP
–
to write an activate request command as C/I code in the CIX0 register.
–
to reset the SPU and SQXR:IDC bits and wait for the following CISQ interrupt.
Test Loop
When set to 1 the IDP1 and IDP0 lines are internally connected together,
and the times T1 and T2 are reduced (cf. TIMR).
C1C1, C1C0 Channel 1 Connect
Determines which of the two channels B1 or IC1 is connected to register
C1R and/or B1CR, for monitoring, test-looping and switching data
to/from the processor.
C1R
B1CR
C1C1
C1C0
Read
Write
Read
Application(s)
0
0
1
0
1
0
IC1
IC1
–
–
IC1
B1
B1
B1
B1
1
1
B1
B1
–
B1 monitoring + IC1 monitoring
B1 monitoring + IC1 looping from/to IOM
B1 access from/to S0; transmission of
a constant value in B1 channel to S0.
B1 looping from S0; transmission of
a variable pattern in B1 channel to S0.
Semiconductor Group
163
Register Description
C2C1, C2C0 Channel 2 Connect
Determines which of the two channels B2 or IC2 is connected to register
C2R and/or B2CR, for monitoring, test-looping and switching data
to/from the processor.
C2R
B2CR
C2C1
C2C0
Read
Write
Read
Application(s)
0
0
1
0
1
0
IC2
IC2
–
–
IC2
B2
B2
B2
B2
1
1
B2
B2
–
B2 monitoring + IC2 monitoring
B2 monitoring + IC2 looping from/to IOM
B2 access from/to S0; transmission of
a constant value in B2 channel to S0.
B2 looping from S0; transmission of
a variable pattern in B2 channel to S0.
4.2.2
Command/Indication Receive 0
Value after reset:
CIR0
Read
Address 31H
7CH
7
0
SQC
SQC
BAS
CODR0
CIC0
CIC1
S/Q Channel Change
A change in the received 4-bit S-channel (TE or LT-T mode) has been detected. The
new code can be read from the SQRR. This bit is reset by a read of the SQRR.
BAS
Bus Access Status
Indicates the state of the TIC bus:
0: the ISAC-S TE itself occupies the D and C/I channel
1: another device occupies the D and C/I channel
CODR0 C/I Code 0 Receive
Value of the received Command/Indication code. A C/I code is loaded in CODR0 only
after being the same in two consecutive IOM frames and the previous code has been
read from CIR0.
(refer to chapter 3.3.2)
CIC0
C/I Code 0 Change
A change in the received Command/Indication code has been recognized. This bit is
set only when a new code is detected in two consecutive IOM frames. It is reset by a
read of CIR0.
Semiconductor Group
164
Register Description
CIC1
C/I Code 1 Change
A change in the received Command/Indication code in IOM channel 1 has been recognized. This bit is set when a new code is detected in one IOM frame. It is reset by
a read of CIR0.
CIC1 is only used if terminal mode is selected.
Note:
The BAS and CODR0 bits are updated every time a new C/I code is detected in two
consecutive IOM frames.
If several consecutive valid new codes are detected and CIR0 is not read, only the
first and the last C/I code (and BAS bit) is made available in CIR0 at the first and second read of that register, respectively.
4.2.3
Command/Indication Transmit 0
Value after reset:
CIX0
Write
Address 31H
3FH
7
0
RSS
RSS
BAC
CODX0
1
1
Reset Source Select
Only valid if the terminal specific functions are activated (STCR:TSF).
0:
Subscriber or Exchange Awake
As reset source serves:
– a falling edge on the EAW line (External Subscriber Awake)
– a C/I code change (Exchange Awake).
A logical zero on the EAW line activates also the IOM-interface clock and frame
signal, just as the SPU-bit (SPCR) does.
1:
Watchdog Timer
The expiration of the watchdog timer generates a reset pulse.
The watchdog timer will be reset and restarted, when two specific bit
combinations are written in the ADF1 register within the time period of 128 ms
(see also ADF1 register description).
After a reset pulse generated by the ISAC-S TE and the corresponding interrupt
(WOV, SAW or CISQ) the actual reset source can be read from the ISTA and
EXIR register.
BAC
Bus Access Control
Only valid if the TIC-bus feature is enabled (MODE:DIM2-0).
If this bit is set, the ISAC-S TE will try to access the TIC bus to occupy the C/I channel
even if no D-channel frame has to be transmitted. It should be reset when the access
has been completed to grant a similar access to other devices transmitting in that IOM
channel.
Semiconductor Group
165
Register Description
Note:
Access is always granted by default to the ISAC-S TE/ICC with TIC-bus address
(TBA2-0, STCR register) "7", which has the lowest priority in a bus configuration.
CODX0 C/I Code 0 Transmit
Code to be transmitted in the C/I channel / C/I channel 0.
(refer to chapter 3.3.2)
4.2.4
MONITOR Receive Channel 0
MOR0
Read
Address 32H
7
0
Contains the MONITOR data received in IOM MONITOR channel/
MONITOR channel 0 according to the MONITOR channel protocol.
4.2.5
MONITOR Transmit Channel 0
MOX0
Write
Address 32H
7
0
Contains the MONITOR data to be transmitted in IOM MONITOR channel/
MONITOR channel 0 according to the MONITOR channel protocol.
4.2.6
Command/Indication Receive 1
Value after reset:
CIR1
Read
Address 33H
FFH
7
0
MR1
CODR1
MX1
CODR1 C/I Code 1 Receive
Bits 7-2 of C/I channel 1
MR1
MR Bit
Bit 1 of C/I channel 1
MX1
MX Bit
Bit 0 of C/I channel 1
4.2.7
Command/Indication Transmit 1
Semiconductor Group
CIX1
166
Write
Address 33H
Register Description
Value after reset:
FFH
7
0
1
CODX1
1
CODX1 C/I Code 1 Transmit
Bits 7-2 of C/I channel 1
4.2.8
MONITOR Receive Channel 1
MOR1
Read
7
Address 34H
0
Contains the MONITOR data received in IOM channel 1 according to the
MONITOR channel protocol.
4.2.9
MONITOR Transmit Channel 1
MOX1
7
Write
Address 34H
0
Contains the MONITOR data to be transmitted in IOM channel 1 according to the
MONITOR channel protocol.
4.2.10
Channel Register 1
C1R
7
Read/Write Address 35H
0
Contains the value received/transmitted in IOM channel B1 or IC1, as the case may
be (cf. C1C1, C1C0, SPCR register).
4.2.11
Channel Register 2
C2R
7
Read/Write Address 36H
0
Contains the value received/transmitted in IOM channel B2 or IC2, as the case may
be (cf. C2C1, C2C0, SPCR register).
Semiconductor Group
167
Register Description
4.2.12
B1-Channel Register
B1CR
Read
Address 37H
7
0
Contains the value received in IOM channel B1, if programmed
(see C1C1, C1C0, SPCR register).
4.2.13
Synchronous Transfer Control RegisterSTCR
Value after reset:
Write
Address 37H
00H
7
0
TSF
TSF
TBA2
TBA1
TBA0
ST1
ST0
SC1
SC0
Terminal Specific Functions
0:
No terminal specific functions
1:
The terminal specific functions are activated, such as
– Watchdog Timer
– Subscriber/Exchange Awake (EAW).
In this case the EAW line is always an input signal which can serve as a request
signal from the subscriber to initiate the awake function in a terminal.
A falling edge on the EAW line generates an SAW interrupt (EXIR).
When the RSS bit in the CIX0 register is zero, a falling edge on the EAW line
(Subscriber Awake) or a C/I code change (Exchange Awake) initiates a reset
pulse.
When the RSS bit is set to one a reset pulse is triggered only by the expiration
of the watchdog timer (see also CIX0-register description).
Note:
The TSF bit will be cleared only by a hardware reset.
TBA2-0 TIC-Bus Address
Defines the individual address for the ISAC-S TE on the IOM TIC bus
(see chapter 2.3.6).
This address is used to access the C/I- and D-channel on the IOM.
Note:
One device liable to transmit in C/I- and D-fields on the IOM should always be given
the address value "7".
Semiconductor Group
168
Register Description
ST1
Synchronous Transfer 1
When set, causes the ISAC-S TE to generate an SIN-interrupt status (ISTA register)
at the beginning of an IOM frame.
ST0
Synchronous Transfer 0
When set, causes the ISAC-S TE to generate an SIN-interrupt status (ISTA register)
at the middle of an IOM frame.
SC1
Synchronous Transfer 1 Completed
After an SIN interrupt the processor has to acknowledge the interrupt by setting the
SC1 bit before the middle of the IOM frame, if the interrupt was originated from a Synchronous Transfer 1 (ST1). Otherwise an SOV interrupt (EXIR register) will be generated.
SC0
Synchronous Transfer 0 Completed
After an SIN interrupt the processor has to acknowledge the interrupt by setting the
SC0 bit before the start of the next IOM frame, if the interrupt was originated from a
Synchronous Transfer 0 (ST0).
Otherwise an SOV interrupt (EXIR register) will be generated.
Note:
ST0/1 and SC0/1 are useful for synchronizing MP accesses and
receive/transmit operations.
4.2.14
B2-Channel Register
B2CR
Read
7
0
Used only in terminal mode (SPCR:SPM = 0).
Contains the value received in the IOM channel B2, if programmed
(see C2C1, C2C0, SPCR register).
Semiconductor Group
Address 38H
169
Register Description
4.2.15
Additional Feature Register 1
Value after reset:
ADF1
Write
Address 38H
00H
7
0
WTC1
WTC2
TEM
PFS
IOF
0
0
ITF
WTC1, 2 Watchdog Timer Control 1, 2
After the watchdog timer mode has been selected (STCR:TSF = CIX0:RSS = 1) the
watchdog timer is started.
During every time period of 128 ms the processor has to program the WTC1- and
WTC2 bit in the following sequence:
1.
2.
WTC1
WTC2
1
0
0
1
to reset and restart the watchdog timer.
If not, the timer expires and a WOV interrupt (EXIR) together with a reset pulse is
generated.
TEM
Test Mode
In test mode (TEM = 1, PFS = 0) all layer-1 functions are disabled and the
ISAC-S TE behaves like an ICC (PEB 2070) device.
PFS
Prefilter Select
These bits together determine the pre-filter delay compensation and the test mode
(layer 1 disabled) of the ISAC-S TE, as follows:
IOF
TEM
PFS
Effect
0
0
No pre-filter (0 delay)
0
1
Pre-filter delay compensation 520 ns
1
1
Pre-filter delay compensation 910 ns
1
0
Test mode (layer 1 disabled)
IOM OFF. Used in terminal mode (SPCR:SPM = 0).
0: IOM interface is operational
1: IOM interface is switched off (DCL, FSC1, IDP0/1, BCL high impedance).
Note:
IOF should be set to "1" if external devices connected to the IOM interface should be
"disconnected" e.g. for power saving purposes or for not disturbing the internal IOM
connection between layer 2 and layer 1. However, the internal operation is
independent of the IOF bit.
Semiconductor Group
170
Register Description
ITF
Inter-Frame Time Fill
Selects the inter-frame time fill signal which is transmitted between HDLC frames.
0: idle (continuous 1 s),
1: flags (sequence of patterns: "0111 1110")
Note:
4.2.16
In TE applications with D-channel access handling (collision resolution), the only
possible inter-frame time fill signal is idle (continuous 1 s). Otherwise the D channel
on the S/T bus cannot be accessed.
Additional Feature Register 2
Value after reset:
ADF2
Read/Write Address 39H
00H
7
0
IMS
IMS
0
0
0
ODS
D1C2
D1C1
D1C0
IOM Mode Selection
IOM-2 interface mode is selected when IMS = 1.
ODS
Output Driver Selection
Tristate drivers (1) or open drain drivers (0) are used for the IOM interface.
D1C2-0 Data Strobe Control
These bits determine the polarity of the two independent strobe signals SDS1 as
follows:
D1C2
D1C1
D1C0
SDS1
0
0
0
0
1
1
1
1
0
0
1
1
0
0
1
1
0
1
0
1
0
1
0
1
always low
high during B1
high during B2
high during B1 + B2
always low
high during IC1
high during IC2
high during IC1 + IC2
The strobe signals allow standard combos or data devices to access
a programmable channel.
Semiconductor Group
171
Register Description
4.2.17
MONITOR Status Register
MOSR
Read
Address 3AH
Value after reset: 00H
7
0
MDR1
MER1
MDA1
MAB1
MDR0
MDR1
MONITOR Channel 1 Data Received
MER1
MONITOR Channel 1 End of Reception
MDA1
MONITOR Channel 1 Data Acknowledged
MER0
MDA0
MAB0
The remote end has acknowledged the MONITOR byte being transmitted.
MAB1
MONITOR Channel 1 Data Abort
MDR0
MONITOR Channel 0 Data Received
MER0
MONITOR Channel 0 End of Reception
MDA0
MONITOR Channel 0 Data Acknowledged
The remote end has acknowledged the MONITOR byte being transmitted.
MAB0
MONITOR Channel 0 Data Abort
4.2.18
MONITOR Control Register
MOCR
Write
Address 3AH
Value after reset: 00H
7
0
MRE1
MRE1,0
MRC1
MXE1
MXC1
MRE0
MRC0
MXE0
MXC0
MONITOR Receive Interrupt Enable (IOM channel 1,0)
MONITOR interrupt status MDR1/MDR0, MER1/0 generation is enabled (1) or
masked (0).
MRC1,0
MR Bit Control (IOM Channel 1,0)
Determines the value of the MR bit:
0: MR always "1". In addition, the MDR1/MDR0 interrupt is blocked, except for the
first byte of a packet (if MRE1/0 = 1).
1: MR internally controlled by the ISAC-S TE according to MONITOR channel
protocol. In addition, the MDR1/MDR0 interrupt is enabled for all received bytes
according to the MONITOR channel protocol (if MRE1 0 = 1).
Semiconductor Group
172
Register Description
MXE1,0
MONITOR Transmit Interrupt Enable (IOM channel 1,0)
MONITOR interrupt status MDA1/0, MAB1/0 generation is enabled (1) or
masked (0).
MXC1,0
MX Bit Control (IOM channel 1,0)
Determines the value of the MX bit:
0: MX always "1".
1: MX internally controlled by the ISAC-S TE according to MONITOR channel
protocol.
4.2.19
S-, Q-Channel Receive Register
Value after reset:
SQRR
Read
Address 3BH
0XH
7
0
IDC
CFS
CI1E
SYN
SQR1
SQR2
SQR3
IDC
Read-Back of Programmed IDC Bit (see SQXR register)
CFS
Read-Back of Programmed CFS Bit (see SQXR register)
CI1E
Read-Back of Programmed CI1E Bit (see SQXR register)
SYN
Synchronization State
SQR4
The S/T receiver has synchronized to the received FA and M bits (1) or has not (0).
SQR1-4
Received S/Q Bits
Received S bits in frames 1, 6, 11 and 16, respectively.
Semiconductor Group
173
Register Description
4.2.20
S, Q Channel Transmit Register
Value after reset:
SQXR
Write
Address 3BH
0FH
7
0
IDC
IDC
CFS
CI1E
SQIE
SQX1
SQX2
SQX3
SQX4
IOM Direction Control
0: Master (normal) mode
Layer 2 transmits IOM channel 0 and 2 on IDP1, channel 1 on IDP0.
1: Slave (test) mode
Layer 2 transmits IOM channel 0, 1 and 2 on IDP1.
Note:
Also refer to chapter 2.3.2
CFS
Configuration Select
This bit determines clock relations and recovery on S/T and IOM interfaces.
0: The IOM interface clock and frame signals are always active, "Power-Down" state
included.
The states "Power-Down" and "Power-Up" are thus functionally identical except
for the indication: PD = 1111 and PU = 0111.
With the C/I-command Timing (TIM) the processor can enforce the "Power-Up"
state.
With C/I-command Deactivation Indication (DIU) the "Power-Down" state is
reached again.
However, it is also possible to activate the S-interface directly with the
C/I-command Activate Request (AR 8/10/L) without the TIM command.
1: The IOM-interface clock and frame signals are normally inactive Power-Down").
For activating the S interface the "Power-Up" state can be induced by software
(SPU bit in SPCR register).
After that the S interface can be activated with the C/I-command Activate
Request (AR 8/10/L).
The "Power-Down" state can be reached again with the C/I commandDeactivation Indication (DIU).
Note:
After reset the IOM interface is always active. To reach the "Power-Down" state
the CFS bit has to be set.
Semiconductor Group
174
Register Description
CI1E
C/I Channel 1 Interrupt Enable
Interrupt generation of CIR0:CIC1 is enabled (1) or masked (0).
SQIE
S-, Q-Interrupt Enable
Generation of CIR0:SQC status (and the accompanying CISQ interrupt is enabled
(1) or masked (0).
SQX1-4
Transmitted Q Bits
transmitted FA bits in frames 1, 6, 11 and 16, respectively.
Semiconductor Group
175
Electrical Characteristics
5
Electrical Characteristics
Absolute Maximum Ratings
Parameter
Symbol
Limit Values
Unit
Voltage on any pin
with respect to ground
VS
– 0.4 to VDD + 0.4
V
Ambient temperature under bias
TA
0 to 70
°C
Storage temperature
Tstg
– 65 to 125
°C
Maximum voltage on V DD
VDD
6
V
Note: Stresses above those listed here may cause permanent damage to the device.
Exposure to absolute maximum rating conditions for extended periods may affect
device reliability.
Line Overload Protection
The maximum input current (under overvoltage conditions) is given as a function of the width
of a rectangular input current pulse (figure 54).
R
ISAC -S TE
Ι
Condition: All other pins grounded
t
t WI
ITS05678
Figure 54
Test Condition for Maximum Input Current
Semiconductor Group
176
Electrical Characteristics
Transmitter Input Current
The destruction limits for negative input signals are given in figure 55. Ri ≥ 2 Ω.
Ι
A
100
50
10
5
1
0.5
0.05
t WI
10 -10 10 -9 10 -8 10 -7 10 -6 10 -5 10 -4 10 -3 10 -2 10 -1
1 s
ITD02337
Figure 55
The destruction limits for positive input signals are given in figure 56. Ri ≥ 200 Ω.
Ι
A
50
5
0.5
0.05
t w1
10
-10
10
-9
10
-8
10
-7
10
-6
10
-5
10
-4
10
-3
10
-2
10
-1
1 s
ITD02340
Figure 56
Semiconductor Group
177
Electrical Characteristics
Receiver Input Current
The destruction limits are given in figure . Ri ≥ 300 Ω.
Ι
A
5
1
0.1
0.01
0.005
t w1
10
-10
10
-4
10
-1
1 s
ITD02338
Semiconductor Group
178
Electrical Characteristics
DC Characteristics
TA = 0 to 70 °C; VDD = 5 V ± 5 %, VSSA = 0 V, VSSD = 0 V
Parameter
Symbol
Limit Values
min
max
Unit Test Condition
Remarks
All pins
except
SX1,2,
SR1,2
L-input voltage
VIL
– 0.4
0.8
V
H-input voltage
VIH
2.0
VDD
+ 0.4
V
L-output voltage
L-output voltage
(IDP0)
VOL
VOL1
0.45
0.45
V
V
IOL = 2 mA
IOL = 7 mA
H-output voltage
H-output voltage
VOH
VOH
V
V
IOH = – 400 µA
IOH = – 100 µA
Power
supply
current
ICC
2.4
VDD
– 0.5
1.5
mA
17
mA
DCL = 1536 kHz
Emergency
B1 = FFH,
B2 = FFH,
D=1
7.7
mA
DCL = 1536 kHz
B1 = FFH,
B2 = FFH,
D = Flag
7.95
mA
DCL = 1536 kHz
B1 = 55H,
B2 = FFH,
D = Flag
8.75
mA
DCL = 1536 kHz
B1 = 00H,
B2 = FFH,
D = Flag
10
mA
DCL = 1536 kHz
ILI
10
µA
0 V < VIN < VDD to 0 V
ILO
10
µA
0 V < VOUT < VDD to 0 V
power
down
operational
(96 kHz)
Input leakage
current
Output leakage
current
Semiconductor Group
179
VDD = 5 V
Inputs at
VSS / VDD
No output
loads
except SX1,2
(50 Ω load)
All pins
except
CP/BCL,
X2,
SX1,2,
SR1,2,
A0, A1,
A3, A4
Electrical Characteristics
DC Characteristics
TA = 0 to 70 °C; VDD = 5 V ± 5 %, VSSA = 0 V, VSSD = 0 V (cont’d)
Parameter
Symbol
Limit Values
min
Unit Test Condition
Remarks
120
µA
0 V < VIN < VDD to 0 V
A0, A1,
A3, A4,
CP/BCL,
X2
SX1,2
max
Input leakage
current
internal pull-down
ILIPD
Absolute value
of output pulse
amplitude
(VSX2 – VSX1)
VX
2.03
2.10
2.31
2.39
V
V
RL = 50 Ω1)
RL = 400 Ω1)
Transmitter output current
IX
7.5
13.4
mA
RL = 5.6 Ω1)
Transmitter output impedance
RX
10
0
kΩ
Ω
Inactive or during binary one
during binary zero RL = 50 Ω
Receiver
output voltage
VSR1
2.35
2.6
V
IO < 5 µA
Receiver
threshold voltage
VSR2 – VSR1
VTR
225
375
mV
Dependent on peak level
Note:
1)
SR1,2
Due to the transformer, the load resistance seen by the circuit is four times RL.
Semiconductor Group
180
Electrical Characteristics
Capacitances
TA = 25 °C, VDD = 5 V ± 5 %, VSSA = 0 V, VSSD = 0 V, fc =1 MHz, unmeasuredpins grounded.
Parameter
Symbol Limit Values Unit Remarks
min.
max.
Input capacitance
I/O capacitance
CIN
CI/O
7
7
pF
pF
All pins except
SR1,2
Output capacitance
against VSSA
COUT
10
pF
SX1,2
Input capacitance
CIN
7
pF
SR1,2
Load capacitance
CL
50
pF
XTAL1,2
Recommended Oscillator Circuits
33 pF
19
XTAL1
External
Oscillator
Signal
XTAL 2
N.C.
CL
19
XTAL1
7.68 MHz
33 pF
18
18
XTAL 2
CL
Crystal Oscillator Mode
Driving from External Source
ITS00764
Figure 57
Oscillator Circuits
Crystal Specification
Parameter
Symbol
Limit Values
Unit
Frequency
f
7.680
MHz
max. 100
ppm
max. 50
pF
Frequency calibration tolerance
Load capacitance
CL
Oscillator mode
fundamental
Note: The load capacitance CL depends on the recommendation of the crystal
specification. Typical values for CL are 22 …33 pF.
Semiconductor Group
181
Electrical Characteristics
XTAL1 Clock Characteristics (external oscillator input)
Parameter
Limit Values
Duty cycle
min.
max.
1:2
2:1
AC Characteristics
T A = 0 to 70 °C, V DD = 5 V ± 5%
Inputs are driven to 2.4 V for a logical "1" and to 0.4 V for a logical "0". Timing measurements
are made at 2.0 V for a logical "1" and 0.8 V for a logical "0". The AC-testing input/output
waveforms are shown in figure 58.
2.4
2.0
2.0
Device
Under
Test
Test Points
0.8
0.8
C Load = 150 pF
0.45
ITS00621
Figure 58
Input/Output Waveform for AC Tests
Semiconductor Group
182
Electrical Characteristics
Microprocessor Interface Timing
Siemens/Intel Bus Mode
t RR
t RI
RD x CS
t DF
t RD
Data
AD0 - AD7
ITT00712
Figure 59
Microprocessor Read Cycle
t WW
t WI
WR x CS
t WD
t DW
Data
AD0 -AD7
ITT00713
Figure 60
Microprocessor Write Cycle
t AA
t AD
ALE
WR x CS or
RD x CS
t ALS
t AL
AD0 - AD7
t LA
Address
ITT00714
Figure 61
Multiplexed Address Timing
Semiconductor Group
183
Electrical Characteristics
WR x CS or
RD x CS
t AS
A0 - A5
t AH
Address
ITT00715
Figure 62
Non-Multiplexed Address Timing
Motorola Bus Mode
R/W
t DSD
t RWD
t RI
t RR
CS x DS
t DF
t RD
D0 - D7
Data
ITT00716
Figure 63
Microprocessor Read Timing
Figure 64
Microprocessor Write Cycle
Semiconductor Group
184
Electrical Characteristics
CS x DS
t AS
t AH
AD0 - AD5
ITT00718
Figure 65
Non-Multiplexed Address Timing
Microprocessor Interface Timing
Parameter
Symbol
Limit Values
min.
Unit
max.
ALE pulse width
tAA
50
ns
Address setup time to ALE
tAL
15
ns
Address hold time from ALE
tLA
10
ns
Address latch setup time to WR, RD
tALS
0
ns
Address setup time
tAS
25
ns
Address hold time
tAH
10
ns
ALE guard time
tAD
15
ns
DS delay after RW setup
tDSD
0
ns
RD pulse width
tRR
110
ns
Data output delay from RD
tRD
110
ns
Data float from RD
tDF
25
ns
RD control interval
tRI
70
ns
W pulse width
tWW
60
ns
Data setup time to W × CS
tDW
35
ns
Data hold time from W × CS
tWD
10
ns
W control interval
tWI
70
ns
Semiconductor Group
185
Electrical Characteristics
Serial Interface Timing
FSC1 (O)
t IIS
t FSD
DCL (O)
t IIH
IDP0/1 ( Ι )
t IOD
IDP0/1 (O)
t SDD
SDS1 (O)
t BCD
t BCD
BCL (O)
ITD05435
Figure 66
IOM® Timing (TE mode)
IOM® Timing
Parameter
Symbol
Limit Values
min.
max.
100
Unit
Test Condition
ns
IOM-2
IOM-2
IOM output data delay
tIOD
20
IOM input data setup
tIIS
20
ns
IOM input data hold
tIIH
20
ns
FSC1 strobe delay
tFSD
– 20
Strobe signal delay
tSDD
Bit clock delay
tBCD
Semiconductor Group
– 20
186
20
ns
120
ns
20
ns
Electrical Characteristics
HDLC Mode (ADF2: IMS = 0, ADF1: TEM = 1, MODE: DIM2 – 0 = 101 – 111)
Figure 67
FSC1 (strobe) Characteristics
HDLC Mode Timing
Parameter
Symbol
Limit Values
min.
Unit
max.
FSC1 set-up time
tFS1
100
ns
FSC1 hold time
tFH1
30
ns
Output data from high impedance to active
tOZD
80
ns
Output data from active to high impedance
tODZ
40
ns
Output data delay from DCL
tODD
20
100
ns
Input data setup
tIS
10
ns
Input data hold
tDH
30
ns
Semiconductor Group
187
Electrical Characteristics
Clock Timing
The clocks are summarized in table 20, with the respective duty ratios.
Table 20
ISAC®-S TE Clock Signals (IOM®-2 mode)
Application
DCL
FSC1
BCL
SDS1
TE
o:1536 kHz*
3:2
o:8 kHz*
1:2
o:768 kHz*
1:1
o:8 kHz
1:11
2:10
The 1536-kHz clock is phase-locked to the receive S signal, and derived using the internal
DPLL and the 7.68 MHz ± 100 ppm crystal.
A phase tracking with respect to "S" is performed once in 250 µs. As a consequence of this
DPLL tracking, the "high" state of the 1536-kHz clock may be either reduced or extended by
one 7.68-MHz period (duty ratio 2:2 or 4:2 instead of 3:2) once every 250 µs. Since the other
signals are derived from this clock, the "high" or "low" states may likewise be reduced or
extended by the same amount once every 250 µs.
The phase relationships of the clocks are shown in figure 68.
7.68 MHz
1536 kHz *
* Synchronous to receive S/T. Duty Ratio 3 : 2 Normally
768 kHz
ITD05427
Figure 68
Phase Relationships of ISAC®-S TE Clock Signals
*) Synchronous to receive "S" line
Semiconductor Group
188
Electrical Characteristics
R
DCL (IOM -2)
t BCD
t BCD
BCL
t FSD
FSC1
t SSD
t SBD
SDS1
ITD05428
Figure 69
Timing Relationships between ISAC®-S TE Clock Signals
Table 21
Parameter
Symbol
Limit Values
Unit
Condition
min.
max.
– 20
20
ns
IOM-2
Bit clock delay
tBCD
SDS1 delay from DCL
tSDD
120
ns
IOM-2
SDS1 delay from BCL
tSBD
120
ns
IOM-2
Semiconductor Group
189
Electrical Characteristics
3.5 V
0.8 V
t WH
t WL
tP
ITT00723
Figure 70
Definition of Clock Period and Width
Table 22
DCL-Clock Characteristics (IOM®-2)
Parameter
(TE) 1536 kHz
Semiconductor Group
Symbol
Limit Values
Unit
Test Condition
min.
typ.
max.
tPO
520
651
782
ns
osc ± 100 ppm
tWHO
240
391
541
ns
osc ± 100 ppm
tWLO
240
260
281
ns
osc ± 100 ppm
190
Electrical Characteristics
Jitter
In TE mode, the timing extraction jitter of the ISAC-S conforms to CCITT Recommendation
I.430 (– 7 % to + 7 % of the S-interface bit period).
Description of the Receive PLL (RPLL) of the ISAC-S TE
The receive PLL performs phase tracking each 250 µs after detecting the phase between the
F/L transition of the receive signal and the recovered clock. Phase adjustment is done by
adding or subtracting 130 ns to or form a 1.536-MHz clock cycle. The 1.536-MHz clock is than
used to generate any other clock synchronized to the line.
During (re)synchronization an internal reset condition may effect the 1.536-MHz clock to have
high or low times as short as 130 ns. After the S/T-interface frame has achieved the
synchronized state (after three consecutive valid pairs of code violations) the FSC output is set
to a specific phase relationship, thus causing once an irregular FSC timing.
Reset
Table 23
Reset Signal Characteristics
Parameter
Symbol Limit Values
Unit
Test Condition
ms
Power-on/Power-Down
to Power-Up (Standby)
min.
Length of active
high state
tRST
4
2 x DCL
clock cycles
During Power-Up (Standby)
t RST
RST
ITD02396
Figure 71
Reset
Semiconductor Group
191
Low Level Controller
6
ISAC®-S TE Low Level Controller
The following paragraphs outline the functionality and structure of a software driver example
for the ISAC-S TE. This example is based on the Siemens Low Level Controllers (LLC’s) for
Basic Access IC which are available in C source code. The ISAC-S TE software driver will be
also referred to as LLC or ISAC-S LLC.
It should be noted that the ISAC-S LLC does not access the complete palette of device
functions but rather a subset of them. For example not all message transfer modes are
supported. Please refer to paragraph ’Architecture and Functions’ for a more detailed
description.
The ISAC-S LLC presented here has been successfully tested in the Siemens ISDN PC
development system. Correct operation with a higher layer software has been verified by using
the Siemens ISDN-Software Development and Evaluation System (SIDES) and the Siemens
ISDN-Operational Software (IOS).
The ISAC-S LLC also apply for the ISAC®-S TE with the limitation of TE functionality only.
There is no adaptation in the listing to this limitation.
6.1
Architecture and Functions
The ISAC-S TE LLC may be divided into two major parts, one for layer 1 control, the ’SBC part’
and one for directing the HDLC-controller operations, the ’ICC part’. The naming conventions
’SBC part’ and ’ICC part’ have been introduced for two reasons: The first is that the ISAC-S TE
may be viewed as the one-chip integration of the Siemens ISDN Communications Controller,
PEB 2070 ICC, and the S-Bus Interface Circuit, PEB 2080 SBC. The second is that the SIPBmainboard firmware, the basis for this example software, actually uses the same code to
control either an ISAC-S TE or an ICC-SBC combination.
The ISAC-S TE LLC consists of driver functions and interrupt server. The driver functions
are implemented as a set of C functions which are responsible for interpreting hardware
related commands from the higher layers and carrying out the appropriate actions at the
hardware level. Driven by hardware interrupts, the interrupt server analyses the hardware
event and informs the higher software layers of that event.
It should be noted that this implementation has attempted to remove as many protocol specific
functions as possible from the LLC and to locate them instead in the higher layer protocol itself.
This has the advantage of making the LLC- more general and less likely to be in need of reprogramming for different protocols.
Semiconductor Group
192
Low Level Controller
OPERATING SYSTEM and
Higher Level Protocol Software
Status/
Error Messages
FUNCTION CALLS
Received
Frames
MMU - Service
Requests
...
Interrupt Server
Driver Functions
SBC Part
ICC Part
Layer-1
Functions
HDLC Controller
related Functions
SBC Part
ICC Part
Evaluation of Interrupt Cause
R
ISAC -S TE
ITS05679
Figure 73
LLC Architecture
The ISAC-S TE LLC supports following standard functions:
– Initialization of the SBC (layer 1) part.
– Activation of layer 1.
– Deactivation of layer 1.
HDLC-controller initialization.
The following HDLC-controller message transfer modes are supported:
auto-mode:
full two byte address compare, LAPD support.
non-auto mode:
full two byte address compare.
transparent mode 3: high byte address compare; called 'TRANSPARENT' mode in
the LLC.
transparent mode 2: no address compare; called 'EXTENDED TRANSPARENT'
mode in the LLC.
HDLC framing with two byte address field is assumed.
Semiconductor Group
193
Low Level Controller
–
–
–
–
HDLC-frame transmission.
Programming of TEI and SAPI values.
HDLC-transceiver control.
Local test loop switching.
The LLC assumes that the ISAC-S TE is operating in an IOM-2 TE configuration.
In addition to the ISAC-S TE standard functions supporting the ISDN-basic access, the ISAC-S
TE contains optional, terminal specific functions. These terminal specific functions (watchdog
and external awake) are not supported by this LLC.
6.2
Summary of LLC Functions
6.2.1
Layer-1 Related Functions
Mnemonic
ActL1_SBC
DeaL1_SBD
ArlL1_SBC
EnaClk_SBC
InitL1_SBC
ResL1_SBC
Purpose
Layer-1 activation.
Layer 1 deactivation.
Activation of a local loop.
Enable clocking in power down mode.
Layer-1 initialization and reset.
Layer-1 reset.
IntL1_SBC
Handling of CISQ interrupts.
The layer 1 related functions call DECODE_L1_STATUS to report a L1 status change to a
higher layer software.
6.2.2
HDLC-Controller Related Functions
Mnemonic
InitLay2_ICC
Loop_ICC
ResetHDLC_ICC
RecReady_ICC
SendFrame_ICC
StoreSAPI_ICC
StoreTEI_ICC
Purpose
HDLC-controller initialization.
Testloop activation at the serial outputs of the IOM interface.
HDLC-transceiver reset.
Setting the HDLC receiver ready or not ready.
HDLC-frame transmission.
SAPI programming.
TEI programming.
Int_ICC
Rx_ICC
Handling of XPR, RSC, TIN and EXI interrupts.
Handling of RPF and RME interrupts.
Semiconductor Group
194
Low Level Controller
6.2.3
External Functions
The LLC-program listing shows some references to external functions (indicated by an
’IMPORT’ declaration). These functions are used by the LLC but are not part of it. These
external functions must be provided by the operating system or a higher layer protocol
software.
MMU_req ()
By calling MMU_req the ISAC-S TE LLC requests memory for the temporary storage of a
received data frame. The memory management unit (MMU) of the operating system has to
provide a memory buffer of the required size (max. 260 bytes).
MMU_free ()
MMU_free is the counterpart to MMU_req. The operating system can release a previously
allocated memory buffer.
STRING_IN () and STRING_OUT ()
STRING_IN and STRING_OUT are assembler written functions for fast input and output of
data frames from/to the ISAC-S FIFO.
ENTERNOINT () and LEAVENOINT ()
ENTERNOINT and LEAVENOINT are called to disable and enable all system interrupts in time
critical sections.
Decode_S_Frame_BASIC ()
Decode_S_Frame_BASIC is called by the LLC-interrupt server to transfer a received HDLC
S frame to a higher layer protocol software.
Following information is passed to Decode_S_Frame_BASIC:
’pei’:
1-byte value identifying the performed address recognition. The bits 0, 1 and 2 of
’pei’ represent the bits TA, SA0 and SA1 of the ISAC-S’ RSTA register.
’sapi’:
1-byte value representing the received HDLC SAPI address byte. Bit 1 of ’sapi’ is
the C/R bit value (RSTA:CR). The most significant 6 bits of ’sapi’ are 0 in
auto-mode, non-auto mode and transparent mode.
’tei’:
1-byte value representing the received HDLC TEI address byte. ’tei’ is 0 in
auto-mode and non-auto mode.
’ctrl’:
2-byte value representing the contents of the received HDLC-control field.
’frame_status’:
1 byte value
= 0 × 00: frame is valid.
= 0 × 80: frame is mutilated (last byte of two byte control field missing).
= 0 × 82: frame is too long. S frame with I field.
’M128’: 1-byte value. 0 in modulo 8 operating mode (1-byte control field), 1 in modulo 128
operating mode (2-byte control field). For correct decoding of ’ctrl’ above.
Semiconductor Group
195
Low Level Controller
Decode_U_Frame_BASIC ()
Decode_U_Frame_BASIC is called by the LLC-interrupt server to transfer a received HDLC U
frame to a higher layer protocol software.
Following information is passed to Decode_U_Frame_BASIC:
’pei’:
(refer to Decode_S_Frame).
’sapi’:
(refer to Decode_S_Frame).
’tei’:
(refer to Decode_S_Frame).
’ctrl’:
1-byte value representing the contents of the received HDLC control field.
PassLongFrame_BASIC ()
PassLongFrame_BASIC is called by the LLC-interrupt server to transfer received HDLC I and
UI frames to a higher layer protocol software.
The LLC passes a pointer to a structure (FRAME_PASS) containing information about the
received frame to PassLongFrame_BASIC. Please refer to the following paragraph for a
description of this structure.
Semiconductor Group
196
Low Level Controller
6.3
LLC-Code Elements
6.3.1
Structures
The Structure ’ISAC’
As the various routines in the LLC require facilities to store information about the device they
control, the global variabel ’pt’ of the type ’ISAC’ has been introduced. The type ’ISAC’ is a
structure containing imperative information elements. These information elements are listed
below:.
Status Information
pt_op_mode
pt_state
pt_ModulMode
operating mode of the ISAC-S TE HDLC controller (auto-mode, nonauto mode…)
Flags of 'pt_state' indicate the various device states.
hardware configuration (TE or NT-S)
I/O buffer related elements
These elements are used when the HDLC data is transmitted or received. In both the transmit
and receive directions additional RAM is required to store data on an intermediate basis. This
buffer will be referred to as the data frame. Related information is stored in the following
elements:
Transmit buffer pointers
pt_tx_start
pt_tx_curr
pointer to the starting point of the data frame for transmission
pointer to the present byte to be sent
Receive buffer pointers
pt_rx_start
pt_rx_curr
pointer to the starting point of the receive data frame.
pointer to the next free position in the receive buffer.
Data byte counters
pt_tx_cnt
pt_rx_cnt
number of bytes yet to be transmitted
number of bytes currently received
The following elements are used to store the type of frame:
pt_rx_frame
pt_tx_frame
type of received frame.
type of transmitted frame.
Semiconductor Group
197
Low Level Controller
The Structure ’FRAME_PASS’
The variable ’fp’ of the type FRAME_PASS is used when the LLC-interrupt server has received
a valid HDLC I or UI frame. A pointer to ’fp’ is passed to PassLongFrame_BASIC.
FRAME_PASS contains all information about the received HDLC frame. Following elements
are used:
mmu_buff
start of MMU buffer which is used for the temporary storage of that HDLC
frame.
start_of_i_data Start of the I-data field in this MMU buffer.
i_data_cnt
Number of bytes in the I-data field.
Two_byte_cf
0 for a one byte HDLC control field, 1 for a two byte HDLC-control field.
ctrl_field
HDLC-control field.
pei
1-byte value identifying the performed address recognition. The bits 0, 1
and 2 of ’pei’ represent the bits TA, SA0 and SA1 of the ISAC-S’ RSTA
register.
frame
Type of HDLC frame; 0 = I frame, 1 = UI frame.
sapi
Received HDLC SAPI address byte. Bit 1 of ’sapi’ is the C/R-bit value
(RSTA:CR). The most significant 6 bits of ’sapi’ are 0 in auto-mode, nonauto mode and transparent mode.
tei
Received HDLC TEI-address byte. ’tei’ is 0 in auto-mode and non-auto
mode.
6.3.2
Definitions and Naming Conventions
Public functions are declared with an EXPORT (only for better readability). External functions
are imported using an IMPORT which is the redefinition of C’s ’extern’. Any function which is
only used locally is declared with a LOCAL (= ’static’).
6.3.2.1
Type Definitions
For reference here is a list of the type definitions used in the LLC’s.
type definitions meaning
BYTE
one byte value
WORD
word = two byte value
FPTR
far pointer to BYTE
Semiconductor Group
198
Low Level Controller
6.3.2.2
Macro Definitions
Error conditions and other states of the ISAC-S TE must be reported to higher layers. This
reporting is realized by a few macros which are executed when such conditions are detected.
These macros can be mapped to any form of message a higher layer software requires. Any
kind of immediately necessary actions may be defined in those macros as well. By using such
constructs the code can be kept compact and clearly readable.
Layer 1 Related Status Message
DECODE_L1_STATUS
for L1 status (IC-channel indication) decoding.
HDLC Controller Related Status and Error Messages
CRC_ERROR
CRC error.
MISSING_ACKNOWLEDGE
A ’Missing HDLC I-frame acknowledge’ is generated
when an acknowledge message for a previously
sent I frame is outstanding and the HDLC-message
transfer mode is changed from auto-mode to nonauto mode. An outstanding acknowledge is
indicated by the ISAC-S TE in register STAR2 (’timer
recovery status’ and ’waiting for acknowledge’ bits).
MMU_ERROR
No memory available to store incoming frame.
N201_ERROR
N201 error, HDLC frame is too long.
PEER_REC_READY
Peer receiver ready.
PEER_REC_BUSY
Peer receive busy.
PROTOCOL_ERROR
Protocol error (PCE interrupt).
REC_FRAME_OVERFLOW
Receive frame overflow.
REC_DATA_OVERFLOW
Receive data overflow (RDO interrupt).
REC_ABORTED
Receive aborted (RAB interrupt).
TX_ACKNOWLEDGE
Transmit frame acknowledge.
TIN_ERROR
TIN interrupt, status enquiry.
TX_DATA_UNDERRUN
Transmit data underrun (XDU interrupt).
XMR_ERROR
Transmit message repeat indication (XMR interrupt).
Following macros are used when a ’timer recovery status’ (register STAR2, bit TREC) is
recognized.
ENABLE_TREC_STATUS_CHECK
enable ’timer recovery status’ check procedure.
DISABLE_TREC_STATUS_CHECK disable ’timer recovery status’ check procedure.
Semiconductor Group
199
Low Level Controller
6.4
Interrupts
Int_ICC is to be called in the case of ISAC-S TE interrupts. The following interrupts are handled
directly in Int_ICC:
’Transmit pool ready’ interrupt (ISTA:XPR)
’Timer’ interrupt (ISTA:TIN).
’Receive Status Change’ interrupt (ISTA:RSC).
’Extended’ interrupt (ISTA:EXI).
The ’Receive Pool Full’ (ISTA:RPF) and ’Receive Message End’ (ISTA:RME) interrupts are
handled by function RX_ICC. The ’CI or SQ channel change’ interrupt (ISTA:CISQ) is handled
by IntL1_SBC.
Please note that the following interrupts are not handled by the interrupt service routine
described here:
ISTA:SIN
(synchronous transfer interrupt)
EXIR:SOV (synchronous transfer overflow)
EXIR:MOS (monitor status) is handled by external functions which are not part of this
description.
EXIR:SAW (subscriber awake)
EXIR:WOV (watchdog timer overflow)
Semiconductor Group
200
Low Level Controller
6.5
LLC-Routine Reference
6.5.1
ISAC®-S TE Layer-1 Functions: The SBC Part
ActL1_SBC ()
Initiates layer-1 activation. The appropriate CI code (activate request) is written to the CI
channel if the layer 1 is not already activated. ActL1_SBC then returns with ACK_DONE. The
subsequent status changes of the SBC will cause CI-channel status change (CISQ) interrupts
and these will be evaluated in the layer-1 interrupt service routine IntL1_SBC.
If the layer 1 is already activated nothing is carried out but ActL1_SBC calls
DECODE_L1_STATUS to report the activated state.
DeaL1_SBC ()
Initiates layer 1 deactivation. The appropriate CI code is written to the CI channel if the layer 1
is not already deactivated. The subsequent layer 1 status changes cause CI channel status
change (CISQ) interrupts and these will be evaluated in the layer 1 interrupt service routine
IntL1_SBC.
If the layer 1 is already deactivated nothing is carried out but DeaL1_SBC calls
DECODE_L1_STATUS to report the deactivated state.
ArL1_SBC ()
Activates a local loop in the SBC. The appropriate CI code (activate request loop) is written to
the SBC. ArL1_SBC returns with ACK_DONE. The subsequent status changes of the SBC will
generate CISQ interrupts and these will be evaluated and reported in the layer-1 interrupt
service routine IntL1_SBC.
EnaClk_SBC ()
EnaClk_SBC enables clocking in TE configurations when the layer 1 is in power-down state.
If first tests if clocks are actually there. If there are clocks the function returns with FALSE. If
there are no clocks (power-down state) the power-up procedure is implemented. The SPU bit
in register SPCR is set. The TIM code is written to the CI channel. EnaClk_SBC waits until the
power-up state (PU) is indicated before the SPU bit is reset to 0. The routine then returns with
TRUE.
InitL1_SBC ()
Initializes and resets the layer-1 controller (ResL1_SBC). Timing mode 0 is set and the TICbus address is also programmed.
Semiconductor Group
201
Low Level Controller
ResL1_SBC ()
This routine resets the layer 1 part of an ISAC-S. It also checks that the layer 1 part is operating
correctly.
Reset procedure:
A software reset command (RS) is sent to the layer 1 part via the IOM CI0 channel.
ResL1_SBC waits for the expected new state (EI) if no timeout condition occurs and issues a
release command (DIU).
If the new state (EI) is not observed the ISAC-S layer 1 part will be deemed to be defective.
IntL1_SBC ()
Interrupt Handler
Handles the CISQ interrupts which indicate changes in the layer 1 status. The final
confirmation of deactivation is carried out here. The actual layer 1 state is evaluated by reading
register CIR0. The following is then carried out:
If the CI-channel indication is ’pending deactivation’ state (DR), DIU is sent to deactivate the
layer 1.
If the indication is an ’activation indication’ (AI) the activation must be confirmed from the TE
side. IntL1_SBC does it automatically by writing an ’activation request’ (AR). In this way this
requirement of the ISAC-S TE is transparent to the higher protocol layers.
After every CI-channel status change interrupt (CISQ) DECODE_L1_STATUS is called to
report the current layer-1 state.
6.5.2
ISAC®-S TE HDLC-Controller Related Functions: The ICC Part
InitPeitab_ICC ()
Initializes the local variable ’pt’. InitPeitab_ICC is to be called once during the system
initialization phase.
InitLay2_ICC ()
Initializes the HDLC controller. The function arguments allow the selection of the HDLCcontroller message transfer mode (auto-mode, non-auto mode, ...), one or two byte HDLCcontrol field operation (modulo 8 or 128) and the setting of the ISAC-S TE internal hardware
timer.
After InitLay2_ICC is called the TEI values for a Broadcast Link are programmed (TEI = FF
hex). The HDLC controller is not reset.
StoreTEI_ICC ()
StoreTEI_ICC is used to program a TEI value in register TEI1 or TEI2 depending on the
function argument value.
Semiconductor Group
202
Low Level Controller
StoreSAPI_ICC ()
StoreSAPI_ICC is used to program a SAPI value in register SAP1 or SAP2 depending on the
function argument value.
RecReady_ICC ()
Sets HDLC receiver ready or not ready depending on the function argument value.
ResetHDLC_ICC ()
ResetHDLC_ICC resets the HDLC controller. Status flags of the local variable ’pt’ indicating
any on-going data transmissions or receptions are reset and memory buffers are released.
SendFrame_ICC ()
SendFrame_ICC initiates the transmission of HDLC frames (S, U, I, UI frames).
A frame can not be sent if the transmit path is still in use, i.e. if the previous transmission is not
finished, if the timer recovery state is indicated (only for I frames) or if the XFIFO is blocked
(STAR:XFW bit).
If the transmission is begun the interrupt handler (Int_ICC) will handle subsequent tasks, for
example shifting remaining data bytes into the XFIFO or calling the MMU to release the
memory buffer.
Loop_ICC ()
Switches testloop at the IOM interface on or off, i.e. connects internally the data upstream and
data downstream lines. This is achieved through setting/resetting the TLP bit in register SPCR.
If the layer-1 part does not deliver clocks while in the deactivated state the clocks will be
enabled when the loop is switched on by means of EnableClk_BASIC. In the Siemens Low
Level Controllers for BASIC access ICs EnableClk_BASIC is a function pointer which
addresses EnaClk_SBC if an ISAC-S or SBC(X) is used. When the loop is switched off the
layer 1 part will return to its normal deactivated state.
Semiconductor Group
203
Low Level Controller
Int_ICC ()
Interrupt Handler
Evaluates and handles the ISAC-S TE interrupts.
Interrupt service procedure:
The bits of the interrupt status register ISTA are scanned. XPR, TIN, RSC, and EXI interrupts
are handled directly by Int_ICC. For RPF and RME interrupts the function RX_ICC is called,
for CISQ interrupts IntL1_SBC is called. The interrupt related actions performed are:
– XPR(transmit pool ready) interrupt, but no TIN and no PCE (EXIR:PCE) interrupt:
a) HDLC controller reset was given previously.
b) last transmission is finished. The XFIFO will be loaded if there are more bytes to
be sent. If not, a 'transmit frame acknowledge' can be generated (if depends on
the message transfer mode and some other conditions).
– TIN interrupt:
The HDLC controller's internal timer has expired (in auto-mode only).
– RSC (receiver status change of remote station) interrupt:
A status change of the remote station's receiver has been detected. This is reported to the
higher layers.
– EXI (extended) interrupt:
One of the six non-critical interrupts has been generated. The exact cause is read from
register EXIR and reported to the higher layers.
RX_ICC ()
Interrupt Handler
Handles the receive pool full and receive message end (RPF and RME) interrupts if TIN and
PCE (EXIR:PCE) interrupt are not indicated. Received frames are handed over to the higher
software levels. Errors detected during the frame reception are reported to the higher layers.
RPF interrupt:
32 data bytes are in the RFIFO. The end of the received frame is yet to be
received and the message is not complete.
RME interrupt:
The receive message is complete. The RFIFO contains the last bytes of a
frame greater than 32 bytes long or a complete frame. In the case of a
long frame the beginning of this frame will already have been received
using the RPF interrupt. Address and control field information is
examined, the type of frame (HDLC U-, UI-, I- or S frame) is determined and
the validity of the frame is checked. Finally the frame or a error condition
message is sent to the higher layers.
Check_TREC_status_ICC ()
Check_TREC_status_ICC () is called periodically by the operating system, if 'timer recovery
status' (STAR2:TREC) was detected during a previous XPR interrupt handling. A 'transmit
frame acknowledge' for an HDLC I frame is generated if the TREC status is left and no timer
interrupt (ISTA:TIN) is indicated.
Semiconductor Group
204
Low Level Controller
6.6
Listing of Driver Routines
/***************************************************************************/
/*
*/
/*
SIEMENS ISDN-Userboard (c) 1987-1993
*/
/*
======================
*/
/*
*/
/*
Firmware:
driver functions for ICC/ISAC-S/ISAC-P
*/
/*
File
:
icc.c
*/
/*
*/
/***************************************************************************/
/* Include Files
/* =============
*/
*/
#include "def.h"
#include "basic.h"
#include "message.h"
/* Import Functions
/* ================
*/
*/
/* from
void
void
crt0.asm
STRING_IN ();
STRING_OUT ();
*/
IMPORT
IMPORT
/* from
PEITAB
basic00.c
*GetPeitab_BASIC ();
*/
IMPORT
/* from
void
void
int
basic_l1.c
IntLay1_BASIC ();
ResetLay1_BASIC ();
EnableClk_BASIC ();
*/
IMPORT
IMPORT
IMPORT
/* from
void
void
void
basic_l2.c
PassLongFrame_BASIC ();
Decode_S_Frame_BASIC ();
Decode_U_Frame_BASIC ();
*/
IMPORT
IMPORT
IMPORT
/* from
int
FPTR
mmu.c
*/
IMPORT
IMPORT
/* from
int
int
mofc.c
IMPORT
IMPORT
MMU_free ();
MMU_req ();
*/
IntMon_MOFC ();
Wr_IntMon_MOFC ();
/* Export Functions
/* ================
EXPORT
EXPORT
EXPORT
int
void
int
Semiconductor Group
*/
*/
Assign_ICC ();
Check_TREC_status_ICC ();
InitLay2_ICC ();
205
Low Level Controller
EXPORT
EXPORT
EXPORT
EXPORT
void
void
int
int
InitPeitab_ICC ();
Int_ICC ();
Loop_ICC ();
SwitchB_ICC ();
EXPORT
EXPORT
EXPORT
EXPORT
EXPORT
int
int
int
int
int
RecReady_ICC ();
ResetHDLC_ICC ();
StoreTEI_ICC ();
StoreSAPI_ICC ();
SendFrame_ICC ();
/* Local Functions
/* ===============
LOCAL
void
*/
*/
RX_ICC ();
/* Variables
/* =========
IMPORT
unsigned int
*/
*/
interrupt_act;
/* Function Declarations
/* =====================
*/
*/
/***************************************************************************/
/*
*/
/*
Function: InitPeitab_ICC ()
*/
/*
Parms
: ’*pt’
pointer to the assigned PEITAB array element
*/
/*
’base’ address of detected ICC/ISAC
*/
/*
purpose : initialization of the PEITAB elemtn for an ICC / ISAC-S
*/
/*
*/
/***************************************************************************/
EXPORT
void
InitPeitab_ICC (pt, base)
register PEITAB
*pt;
IO_PORT
base;
{
BYTE
version;
IO_PORT
reg_rbch = base + ICC_RBCH;
/*
/*
/*
/*
/*
read the ICC/ISAC-S (ISAC-P)
version number
0 for versions A1, A2, ..
1 and greater for versions
2.x [Bx] (x=1,2,3,4) and later
*/
*/
*/
*/
*/
version = inp (reg_rbch);
if (version != 0)
{
if (pt->pt_device == PT_ICC)
pt->pt_device = PT_ICC_B;
/* and set the device identifier
/* accordingly
if (pt->pt_device == PT_ISAC_S)
Semiconductor Group
206
*/
*/
Low Level Controller
pt->pt_device = PT_ISAC_S_B;
}
pt->pt_io_base = base;
pt->pt_r_fifo
pt->pt_r_ista
pt->pt_r_mask
pt->pt_r_star
pt->pt_r_cmdr
pt->pt_r_mode
pt->pt_r_timr
pt->pt_r_exir
pt->pt_r_xad1
pt->pt_r_xad2
pt->pt_r_sap1
pt->pt_r_sap2
pt->pt_r_rsta
pt->pt_r_tei1
pt->pt_r_tei2
pt->pt_r_rhcr
pt->pt_r_spcr
pt->pt_r_stcr
pt->pt_r_cixr
pt->pt_r_monr
pt->pt_r_adfr
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
base
base
base
base
base
base
base
base
base
base
base
base
base
base
base
base
base
base
base
base
base
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
ICC_FIFO;
ICC_ISTA;
ICC_MASK;
ICC_STAR;
ICC_CMDR;
ICC_MODE;
ICC_TIMR;
ICC_EXIR;
ICC_XAD1;
ICC_XAD2;
ICC_SAP1;
ICC_SAP2;
ICC_RSTA;
ICC_TEI1;
ICC_TEI2;
ICC_RHCR;
ICC_SPCR;
ICC_STCR;
ICC_CIXR;
ICC_MONR;
ICC_ADFR;
pt->pt_r_rbcl
pt->pt_r_rbch
pt->pt_r_mox1
pt->pt_r_mocr
pt->pt_r_cix1
pt->pt_r_adf2
=
=
=
=
=
=
base
base
base
base
base
base
+
+
+
+
+
+
ICC_RFBC;
ICC_RBCH;
ICC_MOX1;
ICC_MOCR;
ICC_CIX1;
ICC_ADF2;
pt->pt_r_rfbc
pt->pt_r_sfcr
pt->pt_r_sscx
= base + ICC_RFBC;
= base + ICC_SFCR;
= base + ICC_SSGX;
pt->pt_r_sqxr
= base + ISAC_SQXR;
/* store the base (IO) address
*/
/*
/*
/*
/*
*/
*/
*/
*/
the following structure
elements store the register IO
addresses (e.g. for FIFOs, ISTA,
MASK, etc.)
/* = CIX0/CIR0 in later versions
/* = MOX0/MOR0 in later versions
/* = ADF1 in later versions
*/
*/
*/
/* = RBCL in later version
*/
/* = MOSR (read access)
/* CIX1 and CIR1 register
*/
*/
/* S/Q channel transmit and
/* receive register
*/
*/
/* STAR2 register
*/
pt->pt_r_star2 = base + ICC_STR2;
DISABLE_TREC_STATUS_CHECK ();
}
/***************************************************************************/
/*
*/
/*
Function : InitLay2_ICC ()
*/
/*
Parameters:
*/
/*
*/
Semiconductor Group
207
Low Level Controller
/*
’pei’
0x00 D-channel controller
*/
/*
0x40 B-channel controller (A)
*/
/*
0x80 B-channel controller (B)
*/
/*
*/
/*
’modulo’
0
modulo 8 operation
*/
/*
1
modulo 128 operation
*/
/*
*/
/*
’mode’
operating mode. (automode, non automode, etc.)
*/
/*
*/
/*
’tim_mode’ value for the TIMR register (valid in auto mode only)
*/
/*
refer to the description of that register in the
*/
/*
data sheets.
*/
/*
*/
/*
Purpose: Initialization of an ICCs (ISAC-..) HDLC controller part. */
/*
After execution of InitLay2_ICC, the TEI values for
*/
/*
the Broadcast Link are programmed.
*/
/*
*/
/*
Note: No HDLC controller reset is done.
*/
/*
Only two byte address fields are supported
*/
/*
*/
/*
If the ICC (ISAC) is reprogrammed from AUTOMODE to NON - AUTOMODE */
/*
the successful transmission and acknowledgement of an I-frame
*/
/*
currently sent is not assured.
*/
/*
Switching from AUTOMODE to NON AUTOMODE causes an I frame to be
*/
/*
transmitted completely by the ICC. But the transmit acknowledge
*/
/*
(XPR interrupt) in NON AUTOMODE only indicates that the ICC has
*/
/*
sent the frame out of its XFIFO. It indicates not the successful */
/*
transmission of the I-frame as it is in AUTOMODE (timer super*/
/*
vision, polling for acknowledge frames)!
*/
/*
Therefore if an I-frame is outstanding and the mode is changed
*/
/*
from AUTOMODE to NON-AUTOMODE MISSING_ACKNOWLEDGE is called to
*/
/*
generate a warning message.
*/
/*
MISSING_ACKNOWLEDGE is also called if ’timer recovery’ status
*/
/*
(TREC) or ’waiting for acknowledge (WFA)’ is indicated.
*/
/*
*/
/***************************************************************************/
EXPORT int
InitLay2_ICC (pei, modulo, mode, tim_mode)
BYTE
pei, modulo, mode, tim_mode;
{
BYTE
mode_reg;
register PEITAB
*pt;
if (!(pt = GetPeitab_BASIC (pei)))
/* request pointer to the
/* corresponding PEITAB table
/* element
*/
*/
*/
/* no interrupts during init.
*/
return (ACK_NOT_SUPPORTED);
if (modulo != 0 && modulo != 1)
return (ACK_WRONG_PARM);
outp (pt->pt_r_mask, 0xFF);
mode_reg
= inp (pt->pt_r_mode) & (MODE_HMD2 | MODE_HMD1 | MODE_HMD0);
switch (mode)
Semiconductor Group
/* select OPERATING MODE
208
*/
Low Level Controller
{
/* *******************
case PT_MD_AUTO:
/* HDLC AUTO MODE
/* full address recognition,
/* internal timer mode, receiver
/* active, 2 bytes address fields
/* are selected.
mode_reg
|= (MODE_TMD | MODE_RAC | MODE_ADM);
outp (pt->pt_r_timr, tim_mode);
break;
case PT_MD_NON_AUTO:
mode_reg
/* HDLC NON AUTO MODE
/* full address recognition,
/* receiver active, 2 byte address
/* fields
|= (MODE_MDS0 | MODE_RAC | MODE_ADM);
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
if (((pt->pt_op_mode == PT_MD_AUTO) &&
(pt->pt_state & PT_TX_ACTIVE) && (pt->pt_tx_frame == PT_FR_I))
|| (inp(pt->pt_r_star2) & (STAR2_TREC | STAR2_WFA)))
{
MISSING_ACKNOWLEDGE (pei);
ResetHDLC_ICC (pei);
}
outp (pt->pt_r_timr, 0);
break;
case PT_MD_TRANSP:
mode_reg
break;
/* TRANSPARENT MODE
/* SAPI-address (high-byte)
/* recognition
|= (MODE_MDS1 | MODE_MDS0 | MODE_RAC | MODE_ADM);
case PT_MD_EXT_TRANSP:
case PT_MD_CLEAR_EXT:
mode_reg
break;
/* EXTENDED TRANSPARENT MODE
/* as well as clear mode
/* no address recognition
|= (MODE_MDS1 | MODE_MDS0 | MODE_RAC);
*/
*/
*/
*/
*/
*/
default:
outp (pt->pt_r_mask, 0x00);
return (ACK_WRONG_PARM);
}
pt->pt_op_mode = mode;
/* save MODE register settings
/* modulo: 1 (mod 128); 0 (mod 8)
outp (pt->pt_r_sap2, (BYTE) (modulo ? 0x02 : 0x00));
outp (pt->pt_r_tei2, 0xFF);
if (modulo)
pt->pt_state |= PT_M128;
else
pt->pt_state &= ~PT_M128;
outp (pt->pt_r_mode, mode_reg);
Semiconductor Group
209
*/
*/
Low Level Controller
outp (pt->pt_r_mask, 0x00);
return (ACK_DONE);
}
/***************************************************************************/
/*
*/
/*
Function: StoreTEI_ICC ()
*/
/*
Parms
: ’pei’, ’tei’ and ’reg2’
*/
/*
purpose : program TEI in register TEI1 (reg2 = 0) or TEI2 (reg2 = 0) */
/*
*/
/***************************************************************************/
EXPORT int
StoreTEI_ICC (pei, tei, reg2)
BYTE
pei, tei, reg2;
{
register PEITAB
*pt;
if (!(pt = GetPeitab_BASIC (pei)))
return (ACK_NOT_SUPPORTED);
if (reg2 == 1)
outp (pt->pt_r_tei2, tei);
else
{
outp (pt->pt_r_xad2, tei);
outp (pt->pt_r_tei1, tei);
}
return (ACK_DONE);
/* store TEI in register TEI2
*/
/* store TEI in register TEI1
*/
}
/***************************************************************************/
/*
*/
/*
Function: StoreSAPI_ICC ()
*/
/*
Parms
: pei, sapi, reg2
*/
/*
purpose : store SAPI in register SAPI1 (reg2 = 0) or SAPI2
*/
/*
(reg2 = 0)
*/
/*
*/
/***************************************************************************/
EXPORT int
StoreSAPI_ICC (pei, sapi, reg2)
BYTE
pei, sapi, reg2;
{
register PEITAB
*pt;
if (!(pt = GetPeitab_BASIC (pei)))
return (ACK_NOT_SUPPORTED);
sapi &= ~0x03;
if (reg2 == 1)
/* store SAPI in SAP2
*/
outp (pt->pt_r_sap2, sapi | ((pt->pt_state & PT_M128) ? 0x02 : 0x00));
else
{
/* store SAPI in SAP1
*/
outp (pt->pt_r_xad1, sapi);
if ((pt->pt_ModulMode == PT_MM_NT) || (pt->pt_ModulMode == PT_MM_LT_S))
sapi |= 0x02;
Semiconductor Group
210
Low Level Controller
outp (pt->pt_r_sap1, sapi);
}
return (ACK_DONE);
}
/***************************************************************************/
/*
*/
/*
Function: RecReady_ICC ()
*/
/*
Parms
: pei, ready
*/
/*
purpose : set HDLC receiver ready
(’ready’= 1)
*/
/*
not ready (’ready’= 0)
*/
/*
To be used in auto mode only
*/
/*
*/
/***************************************************************************/
EXPORT int
RecReady_ICC (pei, ready)
BYTE
pei, ready;
{
register PEITAB
*pt;
if (!(pt = GetPeitab_BASIC (pei)))
return (ACK_NOT_SUPPORTED);
outp (pt->pt_r_cmdr, (BYTE) (ready ? 0x00 : CMDR_RNR));
return (ACK_DONE);
}
/***************************************************************************/
/*
*/
/*
Function: ResetHDLC_ICC ()
*/
/*
Parms
: pei
*/
/*
purpose : reset HDLC controller
*/
/*
*/
/***************************************************************************/
EXPORT int
ResetHDLC_ICC (pei)
BYTE
pei;
{
register PEITAB
*pt;
if (!(pt = GetPeitab_BASIC (pei)))
return (ACK_NOT_SUPPORTED);
outp (pt->pt_r_mask, 0xFF);
/*
/*
/*
/*
/*
/*
clear receive and transmit
paths, i.e. clear the status
variables indicating any
transmission or reception of
frames and release the MMU
buffers
FREE_TX_PATH (pt->pt_pei);
if (pt->pt_rx_start)
{
MMU_free (pt->pt_rx_start);
pt->pt_rx_start
= NULL_PTR;
Semiconductor Group
211
*/
*/
*/
*/
*/
*/
Low Level Controller
pt->pt_state
pt->pt_rx_frame
pt->pt_rx_cnt
&= ~PT_REC_ACTIVE;
= 0x00;
= 0;
}
pt->pt_state
&= ~PT_REC_ACTIVE;
/*
/*
/*
/*
/*
set the reset flag in the state
variable. This allows the
interrupt service routine to
react correctly on the following
XPR interrupt
*/
*/
*/
*/
*/
pt->pt_state |= PT_HDLC_RESET;
/* the reset commands:
*/
/* - receive message complete (RME) */
/* - reset hdlc receiver
(RHR) */
/* - transmitter reset
(XRES)*/
outp (pt->pt_r_cmdr, CMDR_RMC | CMDR_RHR | CMDR_XRES);
if (pt->pt_op_mode == PT_MD_AUTO)
/* write TIMR register to stop the
/* internal timer in automode
outp (pt->pt_r_timr, inp(pt->pt_r_timr));
outp (pt->pt_r_mask, 0);
return (ACK_DONE);
/* now allow all interrupts again
*/
*/
*/
}
/***************************************************************************/
/*
*/
/*
Function:
SendFrame_ICC ()
*/
/*
Parms
:
’pei’
*/
/*
’frame_type’ specifying the frame
*/
/*
’cnt’
number of bytes to send
*/
/*
’frame_ptr’ pointer to the data bytes
*/
/*
*/
/*
purpose :
Initiate transmission of HDLC frames ( S, U, I, UI )
*/
/*
*/
/***************************************************************************/
EXPORT int
SendFrame_ICC (pei, frame_type, cnt, frame_ptr)
BYTE
pei, frame_type;
WORD
cnt;
FPTR
frame_ptr;
{
register PEITAB
*pt;
BYTE
cmd;
if (!(pt = GetPeitab_BASIC (pei)))
return (ACK_NOT_SUPPORTED);
/* return if XFIFO is not write
/* enable
*/
*/
/* return if transmit path still
/* blocked and not in automode
*/
*/
if (!(inp (pt->pt_r_star) & 0x40))
return (ACK_ACCESS_FAULT);
Semiconductor Group
212
Low Level Controller
if (pt->pt_state & PT_TX_ACTIVE && pt->pt_op_mode != PT_MD_AUTO)
return (ACK_ACCESS_FAULT);
if (pt->pt_op_mode == PT_MD_AUTO)
{
/* it is not allowed to send an I
/* frame in the timer recovery
/* or in waiting_for_acknowledge
/* status
if (inp(pt->pt_r_star2) & (STAR2_TREC | STAR2_WFA))
if (frame_type == PT_FR_I)
return (ACK_ACCESS_FAULT);
*/
*/
*/
*/
if (inp(pt->pt_r_star2) & STAR2_WFA)
if (pt->pt_state & PT_TX_MMU_FREE)
{
MMU_free (pt->pt_tx_start);
pt->pt_state &= ~PT_TX_MMU_FREE;
}
}
pt->pt_state
|= PT_TX_ACTIVE;
pt->pt_tx_start = frame_ptr;
pt->pt_tx_frame = frame_type;
/* transmitter is active
/* store data frame pointer
/* and frame type
*/
*/
*/
if (cnt <= 32)
{
/* if the number of bytes is <=32
/* the frame can be shifted
/* completely into the XFIFO
STRING_OUT (frame_ptr, pt->pt_r_fifo, cnt);
pt->pt_tx_cnt = 0;
*/
*/
*/
}
else
{
/* if the number of bytes is
/* greater 32 the first 32 are
/* shifted into the XFIFO, the
/* remaining are sent later
/* (interrupt service routine)
STRING_OUT (frame_ptr, pt->pt_r_fifo, 32);
pt->pt_tx_cnt = cnt - 32;
pt->pt_tx_curr = frame_ptr + 32;
*/
*/
*/
*/
*/
}
/*
/*
/*
/*
/*
/*
/*
/*
compute the command byte for
the CMDR register:
in automode the ’transmit I
frame’ command must be used
when it is an HDLC I frame.
The ’transmit transparent
frame’ command must be used in
all other cases
if (pt->pt_op_mode == PT_MD_AUTO)
{
cmd = (pt->pt_tx_frame == PT_FR_I) ? CMDR_XIF : CMDR_XTF;
Semiconductor Group
213
*/
*/
*/
*/
*/
*/
*/
*/
Low Level Controller
if (inp (pt->pt_r_star) & CMDR_RNR)
cmd |= CMDR_RNR;
}
else
cmd = CMDR_XTF;
/* When the frame fits completely
/* into the XFIFO the XME command
/* must be given
*/
*/
*/
/* now output the command byte to
/* the CMDR register
*/
*/
if (!pt->pt_tx_cnt)
cmd |= CMDR_XME;
outp (pt->pt_r_cmdr, cmd);
/* UI frame sent while waiting for
/* ackowledge in automode (an ID
/* check response UI frame)
/* The flag is checked by the
/* interrupt service routine when
/* handling the next XPR interrupt.
if (inp(pt->pt_r_star2) & STAR2_WFA && pt->pt_op_mode == PT_MD_AUTO
&& frame_type == PT_FR_UI)
pt->pt_state |= UI_SENT_WHILE_WAITING_FOR_ACK;
*/
*/
*/
*/
*/
*/
return (ACK_DONE);
}
/***************************************************************************/
/*
*/
/*
Function: Loop_ICC ()
*/
/*
Parms
: ’pei’
*/
/*
’on’
1 -> test-loop on
*/
/*
0 -> test-loop off
*/
/*
purpose: switch testloop at the IOM interface on/off
*/
/*
*/
/***************************************************************************/
EXPORT int
Loop_ICC (pei, on)
BYTE
pei;
BOOLEAN
on;
{
PEITAB
*pt_dch;
BYTE
r_spcr;
register PEITAB
*pt;
if (!(pt = GetPeitab_BASIC (pei)))
return (ACK_NOT_SUPPORTED);
pt_dch = GetPeitab_BASIC (0);
if (on)
{
pt->pt_state |= PT_LOOP;
/* Loop ON
*/
/* enable clocks in TE mode
*/
if (pt->pt_ModulMode == PT_MM_TE)
Semiconductor Group
214
Low Level Controller
{
/* dummy value in the cixr register */
/* prevents a false interpretation of*/
/* the incoming (looped) C/I channel */
if (EnableClk_BASIC (pt_dch))
outp (pt_dch->pt_r_cixr, 0x6F);
}
r_spcr = inp (pt->pt_r_spcr);
outp (pt->pt_r_spcr, r_spcr | SPCR_TPL);
}
else
/* Loop OFF
{
r_spcr = inp (pt->pt_r_spcr) & ~SPCR_TPL;
outp (pt->pt_r_spcr, r_spcr);
*/
pt->pt_state &= ~PT_LOOP;
}
return (ACK_DONE);
}
/***************************************************************************/
/*
*/
/*
Function: SwitchB_ICC ()
*/
/*
purpose : switch the B-channels in IOM1 configurations
*/
/*
to the SSI or SLD interface or back to network
*/
/*
*/
/***************************************************************************/
EXPORT int
SwitchB_ICC (pei, chan_ctrl, sip_act)
BYTE
pei, chan_ctrl;
BOOLEAN
sip_act;
{
register PEITAB
*pt;
BYTE
r_spcr;
if (!(pt = GetPeitab_BASIC (pei)))
return (ACK_NOT_SUPPORTED);
if (chan_ctrl > 0x0F)
return (ACK_WRONG_PARM);
if (!(pt->pt_state & PT_IOM2))
{
r_spcr = inp (pt->pt_r_spcr) & 0xF0;
if (sip_act)
r_spcr |= SPCR_SAC;
else
r_spcr &= ~SPCR_SAC;
/* activate SIP ?
/* yes: set SAC bit
*/
*/
/*
*/
no: clear SAC bit
outp (pt->pt_r_spcr, r_spcr | chan_ctrl);
}
return (ACK_DONE);
}
Semiconductor Group
215
Low Level Controller
/* ***
The interrupt service routines
***
*/
/************************************************************************/
/***************************************************************************/
/*
*/
/*
Function: Int_ICC ()
*/
/*
Parms
:’pt’
pointer to the corresponding PEITAB-table element
*/
/*
purpose : handle ICC (ISAC-S, ISAC-P) interrupts
*/
/*
Int_ICC is called from IntServ_BASIC in basic_l2.c which
*/
/*
is SIPB system specific.
*/
/*
*/
/***************************************************************************/
EXPORT void
Int_ICC (pt)
register PEITAB
*pt;
{
WORD
cnt;
BYTE
exir, cmd;
register BYTE ista;
if (!(ista = inp (pt->pt_r_ista)))
return;
exir = inp (pt->pt_r_exir);
/* XPR interrupt
/* =============
/* the XPR interrupt indicates
/* that the XFIFO is ready for new
/* data bytes.
/* Reasons:
/* - HDLC controller reset
/*
(CMDR:XRES)
/* - data transmission finished
if ((ista & ISTA_XPR) && !(ista & ISTA_TIN) && !(exir & EXIR_PCE))
{
/* transmit byte count is 0
/* -----------------------if ((cnt = pt->pt_tx_cnt) == 0)
{
/* HDLC controller reset command
/* given previously ?
/* ----------------------------/* do nothing when it was a HDLC
/* controller reset only the
/* indicating flag must be cleared
if (pt->pt_state & PT_HDLC_RESET)
pt->pt_state &= ~PT_HDLC_RESET;
else
{
/* XPR was generated because the
/* last transmission is finished
/* -----------------------------/* AUTOMODE operation ?
Semiconductor Group
216
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
Low Level Controller
if (pt->pt_op_mode == PT_MD_AUTO)
{
/* UI frame sent while waiting for
/* I frame acknowledge ?
if (pt->pt_state & UI_SENT_WHILE_WAITING_FOR_ACK)
{
/* the UI frame was sent out if the
/* XFIFO is empty (write enable)
if (inp(pt->pt_r_star) & STAR_XFW)
TX_ACKNOWLEDGE (pt->pt_pei, pt->pt_tx_frame);
*/
*/
*/
*/
pt->pt_state &= ~UI_SENT_WHILE_WAITING_FOR_ACK;
/* if we are in timer recovery
/* status the TREC status check
/* procedure is activated. The
/* transmit acknowledge for the I
/* frame must not be generated !!!
if (inp (pt->pt_r_star2) & STAR2_TREC)
ENABLE_TREC_STATUS_CHECK ();
else
TX_ACKNOWLEDGE (pt->pt_pei, (BYTE) PT_FR_I);
*/
*/
*/
*/
*/
}
else
{
/* if we are in timer recovery
/* status and the last frame was an
/* I frame the TREC status check
/* procedure is activated.
/* If not an transmit acknowledge
/* is generated
if (pt->pt_tx_frame == PT_FR_I &&
(inp (pt->pt_r_star2) & STAR2_TREC))
ENABLE_TREC_STATUS_CHECK ();
else
TX_ACKNOWLEDGE (pt->pt_pei, pt->pt_tx_frame);
*/
*/
*/
*/
*/
*/
/* In all other operating modes
/* (non automode, transparent mode,
/* ...) the transmit acknowledge
/* can be generated at once.
TX_ACKNOWLEDGE (pt->pt_pei, pt->pt_tx_frame);
*/
*/
*/
*/
}
}
else
/*
/*
/*
/*
/*
transmit byte count and status
flag are reset and any
MMU buffer used for temporary
transmit data storage is
released if necessary
pt->pt_tx_cnt = 0;
pt->pt_state &= ~PT_TX_ACTIVE;
if (pt->pt_state & PT_TX_MMU_FREE)
{
MMU_free (pt->pt_tx_start);
Semiconductor Group
217
*/
*/
*/
*/
*/
Low Level Controller
pt->pt_state &= ~PT_TX_MMU_FREE;
}
}
}
else
{
/* transmit count is not 0
/* more data to be sent !
/* -----------------------if (pt->pt_op_mode == PT_MD_AUTO)
cmd = (pt->pt_tx_frame ? CMDR_XTF : CMDR_XIF) |
(inp(pt->pt_r_star) & CMDR_RNR);
else
cmd = CMDR_XTF;
/* less than 32 bytes left ?
*/
*/
*/
*/
if (pt->pt_tx_cnt <= 32)
{
/* shift all bytes into the XFIFO
/* and give XME command
STRING_OUT (pt->pt_tx_curr, pt->pt_r_fifo, cnt);
pt->pt_tx_cnt = 0;
outp (pt->pt_r_cmdr, cmd | CMDR_XME);
}
else
{
/* more than 32 bytes are left to
/* be sent; write 32 into the XFIFO
STRING_OUT (pt->pt_tx_curr, pt->pt_r_fifo, 32);
outp (pt->pt_r_cmdr, cmd); /* give the transmit command,
pt->pt_tx_curr += 32;
/* update current buffer pointer
pt->pt_tx_cnt -= 32;
/* and counter of remaining bytes
*/
*/
*/
*/
*/
*/
*/
}
}
}
if (ista & ISTA_TIN)
{
/* TIN interrupt
/* =============
/* ResetHDLC_ICC (pt->pt_pei);
*/
*/
*/
/*
/*
/*
/*
/*
*/
*/
*/
*/
*/
DISABLE_TREC_STATUS_CHECK ();
TIN_ERROR (pt->pt_pei);
}
HDLC receiver interrupt ?
=========================
(receive pool full or receive
message end and not PCE and not
TIN)
if ((ista & (ISTA_RPF | ISTA_RME))
&& !(exir & EXIR_PCE) && !(ista & ISTA_TIN))
RX_ICC (ista & ISTA_RPF, pt);
/*
/*
/*
/*
/*
/*
Semiconductor Group
status change of the remote
station’s receiver
(i.e. RR or RNR received).
The status can be determined by
reading the RRNR bit of
register STAR
218
*/
*/
*/
*/
*/
*/
Low Level Controller
if (ista & ISTA_RSC)
{
if (inp (pt->pt_r_star) & 0x10)
PEER_REC_BUSY (pt->pt_pei);
else
PEER_REC_READY (pt->pt_pei);
}
/* peer receiver busy
*/
/* peer receiver ready
*/
/* B (2.x) versions of L1 device
*/
/* controllers can’t prevent CIC bit*/
/* being set even when masked.
*/
/* CIC interrupt ? (layer 1 device */
/*
status change) */
if ((ista & ISTA_CIC) && !interrupt_act)
IntLay1_BASIC (pt);
if (ista & ISTA_EXI)
{
/* Extended interrupt ?
/* ==================
/* transmit message repeat int. ?
if ((exir & EXIR_XMR) && !(exir & EXIR_PCE) && !(ista & ISTA_TIN))
{
XMR_ERROR (pt->pt_pei);
FREE_TX_PATH (pt->pt_pei);
}
*/
*/
*/
if (exir & EXIR_XDU)
/* transmit data underrun ?
{
TX_DATA_UNDERRUN (pt->pt_pei);
FREE_TX_PATH (pt->pt_pei);
}
*/
if (exir & EXIR_PCE)
{
/* protocol error interrupt ?
*/
/* ResetHDLC_ICC (pt->pt_pei);
*/
/* receive frame overflow int. ?
*/
PROTOCOL_ERROR (pt->pt_pei);
}
if (exir & EXIR_RFO)
{
MMU_free (pt->pt_rx_start);
pt->pt_rx_start
pt->pt_state
pt->pt_rx_frame
pt->pt_rx_cnt
=
&=
=
=
NULL_PTR;
~PT_REC_ACTIVE;
0;
0;
REC_FRAME_OVERFLOW (pt->pt_pei);
}
if (exir & EXIR_MOR)
if (interrupt_act)
IntMon_MOFC ();
else
Wr_IntMon_MOFC ();
Semiconductor Group
/* MON channel interrupt ?
219
*/
Low Level Controller
}
}
/***************************************************************************/
/*
*/
/*
Function: RX_ICC ()
*/
/*
Parms
: ’pt’ pointer to the assigned PEITAB array element
*/
/*
’rpf’ = 1 if RPF interrupt
*/
/*
purpose : handle interrupts generated by the receiver of an
*/
/*
ICC (ISAC-S, ISAC-P)
*/
/*
*/
/***************************************************************************/
LOCAL void
RX_ICC (rpf, pt)
BOOLEAN
rpf;
register PEITAB
*pt;
{
WORD
RecCnt, ctrl;
FPTR
ptr;
BYTE
pei = pt->pt_pei;
BYTE
rsta, tei, sapi, frame_status = VALID;
BOOLEAN
Two, AutoM, CR_of_I_valid = TRUE;
/*
/*
/*
/*
/*
/*
RPF interrupt:
32 bytes of a frame longer than
32 bytes have been received
and are now available in the
RFIFO.
The message is not complete.
*/
*/
*/
*/
*/
*/
/*
/*
/*
/*
/*
/*
RME interrupt:
Receive message end. The RFIFO
contains a complete frame
(length <= 32 byte) or the last
bytes or a frame (length > 32)
================================
*/
*/
*/
*/
*/
*/
if (rpf)
RecCnt = 32;
else
{
/* read byte count register(s) to
/* get the number of currently
/* received bytes
/* please note that ICC / ISAC-S
/* version Axx had only one byte
/* count register !!!
if (pt->pt_device == PT_ICC || pt->pt_device == PT_ISAC_S)
RecCnt = (BYTE) inp (pt->pt_r_rfbc);
else
RecCnt = (WORD) inp (pt->pt_r_rbcl) |
(WORD) (inp (pt->pt_r_rbch) & 0x0F) << 8;
*/
*/
*/
*/
*/
*/
if (RecCnt && !(RecCnt &= 0x1F))
RecCnt = 32;
}
/* ’RecCnt’ now contains the number */
/* of bytes actually received
*/
Semiconductor Group
220
Low Level Controller
/* was receiver active before or is */
/* the RPF/RME for a new incoming
*/
/* frame ?
*/
if (!(pt->pt_state & PT_REC_ACTIVE))
{
if (RecCnt > 0)
{
if (rpf)
pt->pt_rx_curr = pt->pt_rx_start = MMU_req (266);
else
pt->pt_rx_curr = pt->pt_rx_start = MMU_req (38);
if (pt->pt_rx_start == NULL_PTR)
{
MMU_ERROR (pei);
pt->pt_rx_frame = PT_FR_NO_MEMORY;
}
}
pt->pt_state |= PT_REC_ACTIVE;
pt->pt_rx_cnt = RecCnt;
}
else
/* if data has been already
/* received only the receive byte
/* counter must be updated
*/
*/
*/
pt->pt_rx_cnt += RecCnt;
/* automode and frame greater
/* 260 byte and automode link ?
if (pt->pt_op_mode == PT_MD_AUTO && pt->pt_rx_cnt > 260 &&
((inp (pt->pt_r_rsta) & 0x0D) == 9))
{
pt->pt_rx_frame = PT_FR_OVERFLOW;
/*
/*
/*
/*
/*
ICC B4, ISAC-S B3
reset the receiver if incoming
frame exceeds 528 byte I field
length ->
unbounded frame
if (rpf && pt->pt_rx_cnt > 528)
{
outp (pt->pt_r_cmdr, CMDR_RHR);
MMU_free (pt->pt_rx_start);
pt->pt_rx_start
pt->pt_state
pt->pt_rx_frame
pt->pt_rx_cnt
=
&=
=
=
NULL_PTR;
~PT_REC_ACTIVE;
0x00;
0;
N201_ERROR (pei);
return;
}
Semiconductor Group
221
*/
*/
*/
*/
*/
*/
*/
Low Level Controller
}
else
if (pt->pt_rx_cnt > 266)
pt->pt_rx_frame = PT_FR_OVERFLOW;
/* read the bytes from the RFIFO
/* if no error was detected
if (pt->pt_rx_frame < PT_FR_ERROR)
{
if (RecCnt)
{
STRING_IN (pt->pt_rx_curr, pt->pt_r_fifo, RecCnt);
pt->pt_rx_curr += RecCnt;
/* update buffer pointer
}
/* it points to the next free
/* location in the buffer
}
if (rpf)
/* return when it was a RPF int.
{
outp (pt->pt_r_cmdr, CMDR_RMC | (inp (pt->pt_r_star) & CMDR_RNR));
return;
}
*/
*/
*/
*/
*/
*/
/* RME interrupt handling !!!
/* ==========================
*/
*/
/* the receive status byte is in
/* register RSTA
*/
*/
rsta = inp (pt->pt_r_rsta);
/************************************************************************/
/* It follows a scanning section to get some information about the
*/
/* received data:
*/
/* - Performed address recognition
*/
/* - SAPI (’sapi’), TEI (’tei’) and control field byte(s) (’ctrl’)
*/
/*
as well as the type of frame (HDLC U, UI, S or I frame) are
*/
/*
determined.
*/
/* In addition the length of a frame is checked.
*/
/************************************************************************/
pei
AutoM
tei
sapi
ptr
/* set ’pei’ according to performed */
/* address recognition
*/
|= ((rsta & 0x0C) >> 1) | (rsta & 0x01);
= FALSE;
= 0;
= rsta & 0x02;
/* get the C/R bit value
*/
= pt->pt_rx_start;
switch (pt->pt_op_mode)
/*
/*
/*
/*
now get additional information
(TEI, SAPI, control field)
It depends on the selected
operating mode
*/
*/
*/
*/
{
case PT_MD_CLEAR_EXT:
Semiconductor Group
/* no address recognition,
/* no firmware interaction
222
*/
*/
Low Level Controller
pt->pt_rx_frame = PT_FR_TR;
ctrl = 0x00L;
break;
case PT_MD_EXT_TRANSP:
/* no address recognition, SAPI
/* and TEI are the first two bytes
/* of data
*/
*/
*/
/* high byte address recognition,
/* TEI is the first byte read
*/
*/
/* read TEI and control field
*/
if (pt->pt_rx_cnt > 0)
pt->pt_rx_cnt--;
sapi = *ptr++;
case PT_MD_TRANSP:
if (pt->pt_rx_cnt < 2)
frame_status = MUTILATED;
else
pt->pt_rx_cnt -= 2;
tei
ctrl
= *ptr++;
= (WORD) *ptr++;
if (pt->pt_op_mode == PT_MD_TRANSP)
pei |= 0x20;
else
pei |= 0x30;
break;
case PT_MD_AUTO:
case PT_MD_NON_AUTO:
/* full address recognition in
/* AUTO/nonAUTOMODE read only the
/* HDLC control field information
if (pt->pt_op_mode == PT_MD_AUTO)
/* AUTOMODE link ???
AutoM = ((rsta & 0x0D) == 0x09) ? TRUE : FALSE;
*/
*/
*/
*/
if (!AutoM)
pei |= 0x10;
/* the (first byte of the) control
/* field is in register RHCR
ctrl = (WORD) inp (pt->pt_r_rhcr);
break;
*/
*/
}
switch (ctrl & 0x03)
{
case 0x3:
Two = FALSE;
/* determine the frame type
/* ========================
/* *** HDLC U frame **
*/
*/
*/
/* one byte control field !
*/
if (pt->pt_rx_cnt == 0)
{
pt->pt_rx_frame = PT_FR_U;
break;
Semiconductor Group
223
Low Level Controller
}
else
/*
pt->pt_rx_frame = PT_FR_UI;/*
/*
/*
/*
break;
case 0x1:
as can be seen here U frames
with I field are always treated
as UI frames regardless whether
it’s an real UI frame or an
erroneous (= too long) U frame
/* *** HDLC S-Frame **
/* two byte control field ?
if ((Two = (pt->pt_state & PT_M128)))
{
ctrl <<= 8;
ctrl |= (WORD) *ptr++;
if (pt->pt_rx_cnt > 0)
pt->pt_rx_cnt--;
else
/* Second byte of the two byte
/* control field is missing !
frame_status = MUTILATED;
*/
*/
*/
*/
*/
*/
*/
*/
*/
}
if (pt->pt_rx_cnt > 0)
frame_status = TOO_LONG;
/* S frame with I-field !
*/
/* *** HDLC I frame **
*/
pt->pt_rx_frame = PT_FR_S;
break;
case 0x2:
case 0x0:
/* no address recognition
if (pt->pt_op_mode == PT_MD_CLEAR_EXT)
{
pt->pt_rx_frame = PT_FR_TR;
break;
}
*/
Two = (pt->pt_state & PT_M128);
pt->pt_rx_frame = PT_FR_I;
/* C/R bit of received I frame
/* valid (=1) in TE configuration ?
/* If ’CR_of_I_valid’ is FALSE the
/* automatic acknowledge of an
/* I frame in Automode is
/* prevented! A protocol software
/* will receive the PROTOCOL_ERROR
/* message and re-establish the
/* link.
if (AutoM && !(sapi & 0x02) && (pt->pt_ModulMode == PT_MM_TE))
CR_of_I_valid = FALSE;
if (AutoM)
break;
Semiconductor Group
224
*/
*/
*/
*/
*/
*/
*/
*/
*/
Low Level Controller
if (Two)
/* two byte control field ?
{
if (pt->pt_rx_cnt == 0)
frame_status = MUTILATED;
*/
if (pt->pt_rx_cnt > 0)
pt->pt_rx_cnt--;
ctrl <<= 8;
ctrl |= (WORD) *ptr++;
}
break;
}
if (pt->pt_rx_cnt > 260)
/* I part greater than 260 ?
*/
{
pt->pt_rx_frame = PT_FR_OVERFLOW;
N201_ERROR(pei);
/* must reset the controller
*/
outp (pt->pt_r_cmdr, CMDR_RMC | CMDR_RHR | CMDR_XRES);
outp (pt->pt_r_timr, inp(pt->pt_r_timr));
pt->pt_state |= PT_HDLC_RESET;
FREE_TX_PATH (pt->pt_pei);
}
else
if (!CR_of_I_valid)
/* C/R of I frame invalid in TE ?
*/
{
/* prevent acknowledging S-frame
*/
/* beeing sent and create
*/
/* PROTOCOL_ERROR message.
*/
pt->pt_rx_frame = PT_FR_FAULT;
PROTOCOL_ERROR (pt->pt_pei);
/* must reset the controller
*/
outp (pt->pt_r_cmdr, CMDR_RMC | CMDR_RHR | CMDR_XRES);
outp (pt->pt_r_timr, inp(pt->pt_r_timr));
pt->pt_state |= PT_HDLC_RESET;
FREE_TX_PATH (pt->pt_pei);
}
else
/* enter ’RMC’ command if not
*/
outp (pt->pt_r_cmdr, CMDR_RMC | (inp (pt->pt_r_star) & CMDR_RNR));
/************************************************************************/
/*
*/
/* Now all information about the received frame is available:
*/
/*
- performed address recognition or TEI and SAPI values.
*/
/*
- HDLC control field
*/
/*
- type of frame (HDLC U, UI, S, I frame).
*/
/*
- info about the validity of the frame
*/
/*
*/
/************************************************************************/
if (rsta = (rsta & (RSTA_RDO | RSTA_CRC | RSTA_RAB)) ^RSTA_CRC)
pt->pt_rx_frame = PT_FR_FAULT;
switch (pt->pt_rx_frame)
Semiconductor Group
225
Low Level Controller
{
case PT_FR_FAULT:
if (rsta & RSTA_RDO)
REC_DATA_OVERFLOW (pei);
if (rsta & RSTA_RAB)
REC_ABORTED (pei);
if (rsta & RSTA_CRC)
CRC_ERROR (pei);
/* CRC has already been inverted
*/
break;
case PT_FR_S:
/*
/*
/*
/*
Decode_S_Frame_BASIC (pei, sapi,
((pt->pt_state
MMU_free (pt->pt_rx_start);
break;
HDLC S frame ?
*/
==============
*/
extra parameter for 1 byte
*/
address field set to FALSE
*/
tei, ctrl, frame_status,
& PT_M128) ? 0x01 : 0x00), FALSE);
case PT_FR_U:
HDLC U frame ?
==============
extra parameter for 1 byte
address field set to FALSE
tei, (BYTE) ctrl, FALSE);
/*
/*
/*
/*
Decode_U_Frame_BASIC (pei, sapi,
MMU_free (pt->pt_rx_start);
break;
case PT_FR_UI:
case PT_FR_I:
case PT_FR_TR:
/* HDLC UI or I frame ?
/* ====================
/* ====================
*/
*/
*/
*/
*/
*/
*/
if (pt->pt_rx_frame < PT_FR_ERROR)
{
FRAME_PASS
fp;
fp.mmu_buff
fp.start_of_i_data
fp.i_data_cnt
fp.Two_byte_cf
fp.ctrl_field
fp.pei
fp.frame
fp.sapi
fp.tei
=
=
=
=
=
=
=
=
=
pt->pt_rx_start;
ptr;
pt->pt_rx_cnt;
Two;
ctrl;
pei;
pt->pt_rx_frame | frame_status;
sapi;
tei;
/* transfer the frame to the ’long
/* frame queue’
*/
*/
PassLongFrame_BASIC (&fp);
}
break;
}
/* end of ’switch (pt->pt_rx_frame)’ ------------------------------- */
Semiconductor Group
226
Low Level Controller
/* release the data buffer if the
/* frame reception or the frame
/* were erroneous
*/
*/
*/
if (pt->pt_rx_frame >= PT_FR_ERROR)
MMU_free (pt->pt_rx_start);
pt->pt_rx_start
pt->pt_state
pt->pt_rx_frame
pt->pt_rx_cnt
=
&=
=
=
NULL_PTR;
~PT_REC_ACTIVE;
0x00;
0;
}
/***************************************************************************/
/*
*/
/*
Function: Check_TREC_status_ICC ()
*/
/*
Parms
:
*/
/*
purpose : called periodically if timer recovery status was detected */
/*
during previous XPR interrupt handing. A
*/
/*
transmit-acknowledge for I frame is generated if the TREC */
/*
status is left.
*/
/*
*/
/***************************************************************************/
EXPORT void
Check_TREC_status_ICC ()
{
register PEITAB
*pt;
if (!(pt = GetPeitab_BASIC (0)))
return;
outp (pt->pt_r_mask, ~MASK_TIN);
/* allow only TIN interrupts
/* timer recovery status left ?
if (!(inp(pt->pt_r_star2) & STAR2_TREC))
{
if (inp(pt->pt_r_ista) & ISTA_TIN)
{
ResetHDLC_ICC (pt->pt_pei);
TIN_ERROR (pt->pt_pei);
}
else
/* generate a transmit acknowledge
/* I frame if there was no TIN
/* interrupt
TX_ACKNOWLEDGE (pt->pt_pei, (BYTE) PT_FR_I);
DISABLE_TREC_STATUS_CHECK ();
}
outp (pt->pt_r_mask, 0x00);
}
Semiconductor Group
227
*/
*/
*/
*/
*/
Low Level Controller
/***************************************************************************/
/*
*/
/*
SIEMENS ISDN-Userboard (c) 1987-1993
*/
/*
======================
*/
/*
*/
/*
Firmware:
driver functions for SBC / L1 part of ISAC-S
*/
/*
File
:
sbc.c
*/
/*
*/
/***************************************************************************/
/* Include Files
/* =============
*/
*/
#include "def.h"
#include "basic.h"
#include "message.h"
/* CI codes for SBC and ISAC-S
PM */
/*********************************************************/
#define
#define
#define
#define
#define
#define
#define
#define
#define
CI_PU
CI_TIM
CI_AI
CI_AR
CI_DIU
CI_DID
CI_DR
CI_RS
CI_EI
(BYTE)0x1C
(BYTE)0x00
(BYTE)0x30
(BYTE)0x20
(BYTE)0x3C
(BYTE)0x3C
(BYTE)0x00
(BYTE)0x04
(BYTE)0x18
/*
/*
/*
/*
/*
/*
/*
/*
/*
0111
0000
1100
1000
1111
1111
0000
0001
0110
/* Imported Functions
/* ==================
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
IMPORT
IMPORT
/* from
WORD
void
IMPORT
/* from basic00.c
PEITAB
*GetPeitab_BASIC ();
crt0.asm
ENTERNOINT ();
LEAVENOINT ();
*/
/* Export Functions
/* ================
*/
*/
*/
EXPORT
EXPORT
EXPORT
EXPORT
EXPORT
int
int
int
int
void
InitL1_SBC ();
ActL1_SBC ();
ArlL1_SBC ();
DeaL1_SBC ();
IntL1_SBC ();
EXPORT
EXPORT
int
int
ResL1_SBC ();
EnaClk_SBC ();
Semiconductor Group
PU indication
timing requested
activation indication
activation request
deactivation ind. upstream
deactivation ind. downst.
deactivation request
Reset
Error indicate downstream
228
Low Level Controller
/* Variables
/* =========
*/
*/
/* Function Declaration
/* ====================
*/
*/
/***************************************************************************/
/*
*/
/*
Function: EnaClk_SBC ()
*/
/*
Parms
: pointer to PEITAB table element
*/
/*
purpose : enable clocks for TE configurations
*/
/*
*/
/***************************************************************************/
EXPORT int
EnaClk_SBC (pt)
register PEITAB
*pt;
{
unsigned int
count, i = 0;
BYTE
BitSet, spcr;
/* Test to see if clocks are
*/
/* actually there. Because the SBC */
/* after reset does not deactivate */
/* its clocks immediately we will
*/
/* make pretty sure that the clocks */
/* are there before we leave this
*/
/* routine
*/
BitSet = inp (pt->pt_r_star) & STAR_BVS;
count = 0;
/* we test to see if 6 changes in
*/
/* the STAR:BVS bit indicating the */
/* reception of at least 3 frames
*/
/* (6 B channels). If at any time
*/
/* we fail to find a bit change
*/
/* and the counter i reaches its
*/
/* maximum then we assume that
*/
/* clocks are no longer present
*/
for (i = 0; i < 500; i++)
if ((inp(pt->pt_r_star) & STAR_BVS) != BitSet)
{
/* Of course we have to reset our
*/
/* counter every time a bit change */
if (++count > 6)
/* is observed to give the next
*/
return (FALSE);
/* bit change the same amount of
*/
/* time in which to occur !!!
*/
i = 0;
BitSet = inp (pt->pt_r_star) & STAR_BVS;
}
/*
/*
/*
/*
/*
/*
/*
/*
Semiconductor Group
the Bx versions reqire one edge
at FSC.
Otherwise the setting of the SPU
has no effect (result: no clock)
The IOM direction control bit
IDC in the ADF1 (SQXR) register
is set before and reset after
the system is clocking
229
*/
*/
*/
*/
*/
*/
*/
*/
Low Level Controller
/* ICC Bx: IDC is in reg. ADF1
*/
/* ISAC-S Bx: IDC is in reg. SQXR
*/
if (pt->pt_device == PT_ICC_B)
outp (pt->pt_r_adfr, 0x10);
if (pt->pt_device == PT_ISAC_S_B)
outp (pt->pt_r_sqxr, 0x80);
spcr = inp(pt->pt_r_spcr);
outp (pt->pt_r_spcr, spcr | SPCR_SPU);
if (pt->pt_state & PT_IOM2)
outp (pt->pt_r_cixr, CIXR_TBC | CI_TIM | 0x03);
else
outp (pt->pt_r_cixr, CIXR_TBC | CI_TIM);
/* wait for power up indication
while ((inp(pt->pt_r_cixr) & CIR_MASK) != CI_PU)
if (++i > 1000)
break;
/* time out
*/
*/
outp (pt->pt_r_spcr, spcr);
/* now reset the IDC bit
*/
/* ICC Bx: IDC is in reg. ADF1
*/
/* ISAC-S Bx: IDC is in reg. SQXR
*/
if (pt->pt_device == PT_ICC_B)
outp (pt->pt_r_adfr, 0x00);
if (pt->pt_device == PT_ISAC_S_B)
outp (pt->pt_r_sqxr, 0x00);
return (TRUE);
}
/***************************************************************************/
/*
*/
/*
Function: InitL1_SBC ()
*/
/*
Parms
: PEI value, mode of operation
*/
/*
purpose : initialize an SBC controlling ICC / L1 part of an ISAC-S
*/
/*
reset L1 to come to default state
*/
/*
*/
/***************************************************************************/
EXPORT int
InitL1_SBC (pei, mode_type)
BYTE
pei, mode_type;
{
register PEITAB
*pt;
BYTE
r_mode;
/* return if the addressed device
/* is not operational or not used
/* for LAYER 1 control
if (!(pt = GetPeitab_BASIC (pei)))
return (ACK_NOT_SUPPORTED);
if (!(pt->pt_state & PT_L1_CTRL))
Semiconductor Group
230
*/
*/
*/
Low Level Controller
return (ACK_NOT_SUPPORTED);
outp (pt->pt_r_mask, 0xFF);
/*
/*
/*
/*
compare the requested
initialization mode with
detected hardware configuration
(’pt_ModulMode’)
*/
*/
*/
*/
if (pt->pt_ModulMode != mode_type)
{
outp (pt->pt_r_mask, 0x00);
return (ACK_WRONG_MODUL_MODE);
}
/* timing mode 0 is used on the
/* SIPB for TE and NTS configu/* ration
*/
*/
*/
r_mode = inp (pt->pt_r_mode);
if (mode_type == PT_MM_TE)
outp (pt->pt_r_mode, (r_mode & ~(MODE_HMD2 | MODE_HMD1)) | MODE_HMD0);
else
outp (pt->pt_r_mode, r_mode & ~(MODE_HMD2 | MODE_HMD1 | MODE_HMD0));
if (pt->pt_state & PT_IOM2)
{
outp (pt->pt_r_adf2, 0x80);
/* IOM 2 mode ?
*/
/* program IOM2 mode in ICC/ISAC-S
*/
/* Changed to be terminal mode
/* timing rather than SPCR_SPM
*/
*/
/* no terminal specific functions
*/
switch (mode_type)
{
case PT_MM_NT:
outp (pt->pt_r_spcr, 0x00);
outp (pt->pt_r_stcr, 0x00);
outp (pt->pt_r_mode, (r_mode & ~(MODE_HMD2 | MODE_HMD0))
| MODE_HMD1);
break;
case PT_MM_TE:
outp (pt->pt_r_spcr, 0x00);
outp (pt->pt_r_stcr, 0x70);
/* terminal mode
/* TIC bus address ’7’
/* no watchdog timer
*/
*/
*/
break;
}
}
else
{
outp (pt->pt_r_adf2, 0x00);
outp (pt->pt_r_stcr, 0x70);
}
/* program IOM2 mode in ICC/ISAC-S
/* program TIC bus address
outp (pt->pt_r_mask, 0x00);
Semiconductor Group
231
*/
*/
Low Level Controller
if (!ResL1_SBC (pt))
return (ACK_ACCESS_FAULT);
return (ACK_DONE);
}
/***************************************************************************/
/*
*/
/*
Function: ActL1_SBC ()
*/
/*
Parms
: PEI value
*/
/*
purpose : establish L1 link
(= activation)
*/
/*
*/
/***************************************************************************/
EXPORT int
ActL1_SBC (pei)
BYTE
pei;
{
register PEITAB
*pt;
/* return if the addressed device
*/
/* is not operational or not used
*/
/* for LAYER 1 control
*/
if (!(pt = GetPeitab_BASIC (pei)))
return (ACK_NOT_SUPPORTED);
if (!(pt->pt_state & PT_L1_CTRL))
return (ACK_NOT_SUPPORTED);
/* the activation procedure is not
/* done if the layer 1 link is
/* already established. In that
/* case only an activation
/* indication message is generated
if (((pt->pt_CI_rec = inp(pt->pt_r_cixr)) & CIR_MASK) != CI_AI)
{
if (pt->pt_ModulMode == PT_MM_TE)
EnaClk_SBC (pt);
*/
*/
*/
*/
*/
if (pt->pt_state & PT_IOM2)
outp (pt->pt_r_cixr, CIXR_TBC | CI_AR | 0x03);
else
outp (pt->pt_r_cixr, CIXR_TBC | CI_AR);
return (ACK_DONE);
}
DECODE_L1_STATUS (pei, pt->pt_CI_rec);
return (ACK_DONE);
}
/***************************************************************************/
/*
*/
/*
Function: ArlL1_SBC ()
*/
/*
Parms
: PEI value
*/
/*
purpose : activate local loop
*/
/*
*/
/***************************************************************************/
EXPORT int
Semiconductor Group
232
Low Level Controller
ArlL1_SBC (pei)
BYTE
pei;
{
register PEITAB
*pt;
if (!(pt = GetPeitab_BASIC (pei)))
return (ACK_NOT_SUPPORTED);
if (pt->pt_ModulMode == PT_MM_TE)
EnaClk_SBC (pt);
if (pt->pt_state & PT_IOM2)
outp (pt->pt_r_cixr, 0x6B);
else
outp (pt->pt_r_cixr, 0x68);
return (ACK_DONE);
}
/***************************************************************************/
/*
*/
/*
Function: DeaL1_SBC
*/
/*
Parms
: PEI
*/
/*
purpose : release L1 link
*/
/*
*/
/***************************************************************************/
EXPORT int
DeaL1_SBC (pei)
BYTE
pei;
{
register PEITAB
*pt;
if (!(pt = GetPeitab_BASIC (pei)))
return (ACK_NOT_SUPPORTED);
if (!(pt->pt_state & PT_L1_CTRL))
return (ACK_NOT_SUPPORTED);
if (pt->pt_ModulMode != PT_MM_NT && pt->pt_ModulMode != PT_MM_LT_S)
return (ACK_WRONG_MODUL_MODE);
if (((pt->pt_CI_rec = inp (pt->pt_r_cixr)) & CIR_MASK) != CI_DIU)
{
if (pt->pt_state & PT_IOM2)
outp (pt->pt_r_cixr, CIXR_TBC | CI_DR | 0x03);
else
outp (pt->pt_r_cixr, CIXR_TBC | CI_DR);
return (ACK_DONE);
}
DECODE_L1_STATUS (pei, pt->pt_CI_rec);
return (ACK_DONE);
}
/***************************************************************************/
/*
*/
/*
Function: IntL1_SBC ()
*/
Semiconductor Group
233
Low Level Controller
/*
Parms
: pointer to PEITAB table element of ICC / ISAC-S
*/
/*
purpose : handle C/I interrupts
*/
/*
*/
/***************************************************************************/
EXPORT void
IntL1_SBC (pt)
register PEITAB
*pt;
{
pt->pt_CI_rec = inp (pt->pt_r_cixr);/* read CIRR (CIR0) register
*/
if (pt->pt_ModulMode == PT_MM_NT)
{
/* in NT / LT-S configuration:
*/
/* send DID if SBC/ISAC-S is in the */
/* DIU state
*/
/* -> deactivation
*/
if ((pt->pt_CI_rec & CIR_MASK) == CI_DIU)
{
if (pt->pt_state & PT_IOM2)
outp (pt->pt_r_cixr, CIXR_TBC | CI_DID | 0x03);
else
outp (pt->pt_r_cixr, CIXR_TBC | CI_DID);
}
}
else
{
/* TE configuration:
/* power down SBC/ISAC-S if it has
/* changed from activated to
/* pending mode
if ((pt->pt_CI_rec & CIR_MASK) == CI_DR)
{
if (pt->pt_state & PT_IOM2)
outp (pt->pt_r_cixr, CIXR_TBC | CI_DIU | 0x03);
else
outp (pt->pt_r_cixr, CIXR_TBC | CI_DIU);
*/
*/
*/
*/
}
/*
/*
/*
/*
/*
/*
activation confirmation in IOM2
configurations. The SBC
(ISAC-S) must confirm an
activation from network side.
Only then it will be transparent
for upstream B channel data
*/
*/
*/
*/
*/
*/
if ((pt->pt_state & PT_IOM2) &&
((pt->pt_CI_rec & CIR_MASK) == CI_AI))
outp (pt->pt_r_cixr, CIXR_TBC | CI_AR | 0x03);
}
DECODE_L1_STATUS (pt->pt_pei, pt->pt_CI_rec);
}
/***************************************************************************/
/*
*/
/*
Function: ResL1_SBC ()
*/
/*
Parms
: pointer to PEITAB table element of ICC / ISAC-S
*/
/*
purpose : Reset SBC / L1 part of ISAC-S
*/
/*
(also used for device test)
*/
Semiconductor Group
234
Low Level Controller
/*
*/
/***************************************************************************/
EXPORT int
ResL1_SBC (pt)
register PEITAB
*pt;
{
int
i, state, failed = FALSE;
BYTE
ForceCommand, NewState, ReleaseCommand, Loop, r_spcr;
switch (pt->pt_ModulMode)
{
case PT_MM_TE:
ForceCommand = CI_RS;
NewState
= CI_EI;
ReleaseCommand = CI_DIU;
break;
case PT_MM_NT:
ForceCommand = CI_DR;
NewState
= CI_DIU;
ReleaseCommand = CI_DID;
/*
/*
/*
/*
send the RES (reset) code
and wait for a change to the EI
state,
then send DIU
*/
*/
*/
*/
/*
/*
/*
/*
/*
send the deactivation request
code
and wait for DIU
then send DID to deactivate the
SBC
*/
*/
*/
*/
*/
break;
default:
if (pt->pt_Lay1id == SBC_LAY1)
pt->pt_Lay1id = UNK_LAY1;
return (FALSE);
}
if (pt->pt_state & PT_IOM2)
{
ReleaseCommand |= 0x03;
ForceCommand
|= 0x03;
}
state = ENTERNOINT ();
/* disable all system interrupts
*/
/* if testloop mode was programmed
/* switch it off to enable L1
/* status recognition
*/
*/
*/
r_spcr = inp (pt->pt_r_spcr);
if (Loop = (r_spcr & SPCR_TPL))
outp (pt->pt_r_spcr, (r_spcr & ~SPCR_TPL));
outp (pt->pt_r_mask, ~ISTA_CIC);
/* allow only C/I interrupts
*/
if (pt->pt_ModulMode == PT_MM_TE)
EnaClk_SBC (pt);
/* output the command code
outp (pt->pt_r_cixr, (BYTE) (CIXR_TBC | ForceCommand));
Semiconductor Group
235
*/
Low Level Controller
i = 0;
/* wait for the expected state
while ((inp(pt->pt_r_cixr) & CIR_MASK) != NewState)
if (i++ > 20000)
{
/* break if timeout
failed = TRUE;
break;
}
*/
/* output the release command
outp (pt->pt_r_cixr, (BYTE)(CIXR_TBC | ReleaseCommand));
*/
if (pt->pt_ModulMode == PT_MM_TE)
{
*/
*/
*/
*/
*/
*/
/*
/*
/*
/*
/*
/*
TE mode ?
Wait for DIU or AIU because
it can cause problems for the
enable clock routine if the
clocks disappear mid routine
due to an earlier reset
*/
for (i = 0; i < 20000; i++)
{
pt->pt_CI_rec = inp (pt->pt_r_cixr) & CIR_MASK;
if ((pt->pt_CI_rec == CI_DIU) || (pt->pt_CI_rec == CI_AI))
break;
}
if ((pt->pt_state & PT_IOM2) && (pt->pt_CI_rec == CI_AI))
outp (pt->pt_r_cixr, CIXR_TBC | CI_AR | 0x03);
}
if (Loop)
outp (pt->pt_r_spcr, r_spcr);
/* restore original value of SPCR
*/
outp (pt->pt_r_mask, 0x00);
LEAVENOINT (state);
/* enable interrupts again
*/
if (failed)
{
if (pt->pt_Lay1id == SBC_LAY1)
pt->pt_Lay1id = UNK_LAY1;
return (FALSE);
}
else
return (TRUE);
}
Semiconductor Group
236
Package Outlines
7
Package Outlines
2.54
1.5 max
0.45
+0.1
0.25 40x
40
~~ 1.3
3.7 ±0.3
0.5 min
5.1 max
P-DIP-40-2
(Plastic Dual-In-Line Package)
15.24 ±0.2
0.25 +0.1
14 -0.3
15.24 +1.2
21
1
20
50.9 -0.5
0.25 max
GPD05055
Index Marking
Dimensions in mm
Semiconductor Group
237
Package Outlines
GPL05102
Plastic Package, P-LCC-44-1 (SMD)
(Plastic-Leaded Chip Carrier)
Dimensions in mm
Semiconductor Group
238
Package Outlines
GPM05250
Plastic Package, P-MQFP-64-1 (SMD)
(Plastic Metric Quad Flat Package)
Sorts of Packing
Package outlines for tubes, trays etc. are contained in our
Data Book “Package Information”
Dimensions in mm
SMD = Surface Mounted Device
Semiconductor Group
239
PackageAppendix
Outlines
Transformers and Crystals Vendor List
Crystals:
Frischer Electronic
Schleifmühlstraße 2
D-91054 Erlangen, Germany
KVG
Waibstadter Straße 2-4
D-74924 Neckarbischofsheim 2, Germany
Tel.: (…7263) 648-0
NDK
2-21-1 Chome Nishihara Shibuya-Ku
Tokyo 151, Japan
Tel.: (03)-460-2111
or
Cupertino, CA, USA
Tel.: (408) 255-0831
S+M Components
Balanstraße 73
P.O. Box 801709
D-81617 Munich, Germany
Tel.: (…89) 4144-8041
Fax.: (…89) 4144-8483
Siemens Oostcamp
Belgium
Schott Corporation
Suite 108
1838 Elm Hill Pike, Nashville, TN 37210, USA
Tel.: (615) 889-8800
TDK
Christinenstraße 25
D-40880 Ratingen 1, Germany
Tel.: (…2192) 487-0
Universal Microelectronics
Saronix
4010 Transport at San Antonio
Palo Alto, CA 94303, USA
Tel.: (415) 856-6900
or
via Arthur Behrens KG
Schrammelweg 3
D-82544 Egling-Neufahrn, Germany
Vacuumschmelze (VAC)
Grüner Weg 37
Postfach 2253
D-63412 Hanau 1, Germany
Tel.: (…6181) 380
or
186 Wood Avenue South
Iselin, NJ OB830, USA
Tel.: (908) 603 5905
Tele Quarz
Landstraße 13
D-74924 Neckarbischofsheim 2, Germany
Valor
Steinstraße 68
D-81667 München, Germany
Tel.: (…89) 480 2823
Fax.: (…89) 484 743
Transformers:
Advanced Power Components (APC)
47 Riverside
Medway City Estate Strood
County of Kent, GB
Tel.: (044) 634-290 588
Vogt electronic AG
Postfach 1001
D-94128 Obernzell, Germany
Tel.: (…8591) 17-0
Fax.: (…8591) 17-240
Pulse Engineering
P.O. Box 12235
San Diego, CA 92112, USA
Tel.: (619) 268-2454
or
4, avenue du Quebéc
F-91940 Les Ulis, France
or
Dunmore Road
Tuam County Galway, Ireland
Tel.: (093) 24107
Semiconductor Group
240
This datasheet has been download from:
www.datasheetcatalog.com
Datasheets for electronics components.