Digital PDFs

EK-A0514-MG-001

November 1991

115 pages

Original

4.2MB

view download

OCR Version

3.9MB

view download

Document:	MicroVAX 3100 Platform KA47 CPU System Maintenance
Order Number:	EK-A0514-MG
Revision:	001
Pages:	115
Original Filename:

OCR Text

§0:0.0.:0.8.0.8.0.0.0.0.880800:000.605.00.0809006000009.0:¢.6.6609.06.0.01
19.9.9.0.0.9.0.9.0.9.0.$.0.0.9.4.6.6.948.00.6.8.$9.09.00.0.99.6.6.6090.6.0.06096.69

)8.0.0.8.0.9.0.9.0.8.64.605.0806.0.846.98060468066060$¢6086$64644
p0.6.9.0.0.0.0.8.0.8.050850008.800900.646856¢60004.6606.¢60904
10.0,0.0.9.9.9.0.0.09.6.00080¢4:0¢000.080¢00066060¢0600¢/
19.0.0.0.0.9.8:8.0.0.005.0.8099.009.0.06¢00606060566090.61
30.0,0.0.09.0,0.8.0.6905.6.9.90.¢.6.0.6.08.69.699.68.89606441
00.0.0.8.0,0.0.0.6.94.089.0.9.990.5.0.60.000.08664600064
$9:9:0.9.0.0.:0,0.0.0.0.9,00.60.69.9¢00.9999849606064

$0.0,99.0.9:0,0.0.9.0.0:9.9.0.0099.6.96.5.009.69.0:4¢54
}:9.0,0.9:9:0.9.0.0.9.9.9.0.0.0.9.0.0.6.89.9.0.9.0,0.6.99.04
$10.0.0.0.0.9.6.9.0.0.0.0.0.0.0,0.005.80.0.6.9.00¢04

}:0.9.6.0.6:9.9.9:6:9:6.6.0.9.0.0.6.0.9.6.¢.0.9.8
6.9 ¢
$9.0.00.4.9.9.90.6.6.0.9.8:00.90.6.8.¢.¢.0.94
£8.0.0.0.0.0.0.9.0.0.6.6.0.69.9.69.0.0.0.6
$0:0.0:0.6.9.9.9.6.9:0.8:9.0.9.:6.6.6.¢¢

$5.0.8.0.6.0.4.9.8.9.0090008484
019.0.6.0.9.0.0.9.6,8.0.4,0.9.094
}9.8.9.0.¢.¢.¢.8.0.0.8.0.0
94

HEXAXXKKKKKX
X
119.4.6.8.9.0.6.9.6,0.¢

0:9.9:4.9.6.9:0.9{
XXKXXXX
)099,04

X¥X
'v

X
XXX

10.9.0.¢
KEXXXAK

:9.4.4.9.9.9.0.94

XX XKKAXYKAK
).0.9.¢:9.9.9.6.9.9.9.6.94

},0.9.9.9.6.9.6.9.9.0.99.¢.04

00.8.0:9.9.9.0.99.8.6.9¢9.¢04
19.8.9.9.0.8.9.9.0.0.9.9.9.¢.9.9.9.94

19.9.9.9.4.9.8.6.4.9.¢.495606000
XARAK
AKX AKX AL AXE
XK KA KL LA K

:9.0.9.9:6.9.0.9.8:9.0.9.9.0.0,0¢.89.0439.694
$0.9.0.0.,0.8:6.8.0.9.9.9:6,0.0.0.8:9.0.9.9.90.9.694
$09990
80.868.¢89080
8000066866664
00.9.0.9.0.90.06460829989604998649.009¢

$.9,9:9.9.9.9.6.9.0.9.0.9.9.0.09.09.4.999.00.9.¢,6:69.¢.664
}9.0.9.9.0.9.6:$.0.9.09.9.0.0.9.9.9:6.9.9.9.68.8.9.6.0.6649.9
¢4
$ 9.90.9.4.0.00.9.9.0:0496.9600808.0.90.9.656660080¢4
PO GO0 F 00900908960 060088.08:600.6606¢40601

100008000090 9¢.000600809000:0:0.80609.699008 057
18000088
09000000
6000.
0:0809.0.00.09.098
0050
.69.00094
1099090999000 0008000008080
KAAP LR

L EL LR LKA

LKL AT AL L LKA

oI Neseeeey

AR KUAA KA

1 9.9.0.9.9.9.990.9090 0090860080050086000000800.0.900,009008
98
1 0.9.9.9:998:0.00808 999096800590 8088500 6200 0PI

NPV

9.90

MicroVAX 3100 Platform

KA47 CPU System Maintenance
Order Number: EK-AD514-MG 001

Novemnber 1991

This manual gives maintenance information for systems that use the KA47
CPU module.

Revision Information:

Digita! Equipment Corporation
Maynard, Massachusetis

This 1s & new manual

November 1951

The information in this document is subject to change without notice and should not be
construed as a commitment by [higital Equipment Corporation. Iigital Equipment Corporation
assumes no responsibility for any errors that may appear n this document.
No responsibility 1s assumed for the use or reliability of software on equipment that is not
supplied by Digital Equipment Corporation or 1s affiliated companies

Resinicted Rights: Use, duplication, or disclosure by the U.S. Government s subject to
restrictions as set forth in subparagraph (c}(1){ii} of the Rights in Technical Data and Computer
Software clause at DFARS 252.227.7013.
© Digital Equipment Corporation 1991
All Rights Reserved.

The postpaid Reader's Comments forins at the end of this document request your critical
evaluation to assist in preparing future documentation.

The following are trademarks of Digital Equipment Corporation: DEC. Ihgptal, MicroVAX,
ThinWire, VAX, VAX DOCUMENT. VME. VT330, and the DIGITAL logo

This document was prepared using VAX DOCUMENT, Version 2.0

—

Contents
Preface

.....................................................

vii

KAA47 CPU Module Description
1.1

KA47 CPU Module . . . . ... .

... .

1~1

1.2

MS44 and MS44L Memory Modules

MS44 or MS44L Memory Option Installation

. ... ... ...

. ... .. ...,

.. ... ..

1-9

.. ... ..

1-11

... ... .. . ... .. .. ..., .

2-1

Configuration
2.1

Memory Configurations .. . .. ...

2.2

Mass Storage Devices. . ... ... ... .. .. ...

...

-1

221

Internal Mass Storage Devices. ...

.. .. ... . ....

2-1

222

External Mass Storage Devices .. .......
... . ... ... ..

2-2

223

SCSIID Numbers . .. .. ... ...

2-4

2.3

Communications Options . . .. ... ...

...

. ... .. .. .. . . . . ...,
...

2.31

Asynchronous Communications Options

232

Synchronous Communications Options

.. .. . ... ... ... .

2~4

. . . ... .. ... ..

2-5

.. . ...

2-5

3-1

...

. . .. ... ...

KAA47 Firmware
31

Power-Up Test and Imitialization .. ...

.. ..

3.2

Console Program .. ...

.. ... ...

321

Console Device . . .. ...

322

Console Commands ...

323

Console Mode . . ... ...

324

Console Security

325

...

3-4

. ... .. . . ... ...,

3-4

... .. ... ... .. .. .. . .. .. ...

3-6

. .. ...
..

. . ... ...

. .

...

. ...

...

... ...

3-6

...

... ... ...

3-7

3-9

3.3

Self-Test . .. .. ... ...

Console Command Conventions ... ... .. ..

... .

3-11

3.31

Additional Error Information for Self-Tests . . .. ... ...

3-14

332
3321

3322
3323
3.4

3.41

342

3.5

351
352

353

Test Environments . . . . . . ...

Customer Environment .. ... ... ... ...
Digital Services Environment . ... ... ...
Manufacturing Environment ... . ... ...

... . ...
... ... ..
L.

3-15
3-15

3-15
3-16

Utilities . . .. .. .. .

3-16

COMM Utilities . . ... ... ... . o
....
... ...
System Exerciser ........

3-19

SOSI UtHLIeS . . . oo D

3-17
3-19

..
Selective System Exerciser Test (T 106). .. ... .........

3-23

Additional Error Information for System Exerciser Tests . . .

3—-29

Summary SEreens .. ....... ...

3-24

Testing and Troubleshooting
General Troubleshooting Information

4-1

4.2

No Display on the Console Terminal

4-3

421

4.3

Troubleshooting Procedure . . . . ... ...
NVR Test (Test 1) . .. ..... ...

4.4

DZ Test (Test 3) ... ... ..

4-7

4.5

CACHE Test (Test 4) ...
.. ..

4.6

MEM Test (Test 5)

4-9

.. ... .. ..

4~-4

4-6

4.7

FPU Test (Test 6)

4-10

4.8

IT Test (Test 7)

4-11

SYS Test (Test 8)

4-11

410

NI Test (Test 9)

4-12

4.1

SCSI Test (Test 10)

4-14

.......................................

4112

Troubleshooting an RRD42 CDROM Drive . . ..
Troubleshooting an RX26 Diskette Dnive . . . . .

4113

Troubleshooting an RZ23L., an RZ24, or an R72’) I)1sk

4111

Drve ...

...

4-17
4-18
4-18

Troubleshooting a TZ’BU Tape Drive . . ..

4115

Troubleshooting a TZK10 Tape Drive ..

4-18

4116

Troubleshooting an External SCSI Device

4-19

412

4-18

4114

COMM Test (Test 12)

4121

Traub‘.eshoetmv
a DSW41 aor a DSW42 gvnchrgnmm

413

Communications Option
ASYNC Test (Test 14)
Troubleshooting a DHW41 or a DHW42 Asynchronous

4131

Communications Option
414

Troubleshooting Procedures for the Power Supply

4-19

4-20
4-21

4-23
4-24

. A Troubleshooting Flowchart
B

Memory Map

FRU Numbers
Ci
C11

FRU Number Assignments . ... . ...... .. ... .. .........
FRU Numbers of SCSI Devices . . ..... . ... ... ... .....

C-1

C-2

KA47 CPU Module Jumper Wires

Glossary
index

Figures

1-1

KA47 CPU Module.

1-2

1-3

KA47 CPU Module Block Diagram

Memory Expansion Connectors . ...... .. ......
... .. ..

1-10

1-5

Memory Module Installation . .. ... ..

1-12

2-1

SZ Expansion Box Numbering System . . .. .. ...

... .. . ..

2-3

Successful Power-Up Test Display .. .......
... .. ..
..

3-2

Unsuccessful Power-Up Test Display .. ... ... ... ... .. ...

3-3

Location of the Console-Related Ports and Switches . ...
. ..

3_5

Location of the NVR Caontacts for Clearing the Password . . .

3-9

3-5

Successful Self-Test Display . ... ...

... . .....

3-13

3-6

Unsuccessful Self-Test Display . . . .......
... ... ... .. . ..

3-13

3-7

Additional Error Information for Self-Tests . . ... ... ...

3-14

3-8

Successful System Exercigser Test . ... .. .. ... .

... ... ..

3-21

3-9

Unsuccessful System Exerciser Test. . .. . ...

... ... ... ..

3-22

3-10

Selective System Exerciser Test (T 106) Example ... ... . ..

3-23

3-11

Summary Screen for System Exerciser DZ Test .. ... ...
. ..

3-25

3-12

Summary Screen for System Exerciser NI Test .. ... ... ...

3-26

3-13

Summary Screen for System Exerciser SCSI Test . . .

3-27

3-14

Summary Screen for System Exerciser COMM Test . ...
. ..

3-28

. ... ...

...

... .. . ... ...

1-2

. ... ...........
... ..

1-4

KA47 Controls, Indicators, Ports, and Connectors . . ... ...
...

...

... . ... ... ..

...

1-8

3-15
3-16
4-1

4-2

Summary Screen for System Exerciser ASYNC Test .. ... ..
Additional Error Information for System Exerciser Tests . ..

3-30

Flowchart for Normal System Power-Up .. .. ... ... ... ...
Cable Loopback Connectors for the DSW41 and DSW42

Options
4-3

s @)

. . ... ...

4-21

Cable Loopback Connectors for DHW41 and DHW42
. .. . .. ..o

4-24

Flowchart for Troubleshooting the Power Supply . . .. .. .. ..
KA47 CPU Module Power Connector Pin Voltages . .. . ....

4-25

Drive Power Connector Pin Voltages ... .... ...

.. ... ...

4-26

Troubleshooting Flowchart (Page 1of4) . ... ...

...

OpPLiIONS

Troubleshooting Flowchart (Page 20f4) .. ... ...

4-28

.. ..

...

Troubleshooting Flowchart (Page 30f4) ... .. ... ... .. ...
Troubleshooting Flowchart (Page 4 of 4)
Memory Connectors . ... ... . ... ...

...

... .. ......

KA47 CPU Module Jumper Wires

Tables

1-1

Functions of Controls, Indicators, Connectors

1-2

KA47 CPU Module Memory Configurations

2-1

KA47 Internal Mass Storage Devices . ... .. ... .. .. ...

2-2

Supported External Mass Storage Devices.

2-3

Recommended SCSI ID Numbers for Devices

Supported Asynchronous Communications Options

2-5

Supported Synchronous Communications Options . . . ...
. ..

2-5

2-6

DSW41-AA and DSW42-AA Communications Support

2-6

3-1

Console Device Port Selection

3-4

3-2

Terminal Settings.

3-6

3-3

Console Mode Control Keys .. .. ... .....

13-4

Device Numbers and Mnemonics

3-5

Typical TEST Command Lines . . ... ...

3-6

Predefined System Exerciser Tests

4-1

Troubleshooting Procedures . .. . ...

4-2

SCSI Device Troubleshooting Procedures

B-1

Memory Map

C-1

FRU Numbers

2-2

. .....

2-3

. ... .. ... ...

2-4

. . ...

. .........
... ... ... . ..., . ...
..
... ... ... ... ..

3-10

...

... .. .....

3-12

3-20

... ...

... . . ...

.
4-17

Preface
This manual describes the KA47 CPU module used in the MicroVAXTM
3100 Mode! 80 system. It provides the configuration guidelines, ROM-based
diagnostic information, and troubleshooting information for systems containing
the KA47 CPU module.

Audience
This manual is for DigitalTM Services personnel who provide support and
maintenance for systems that use the KA47 CPU module. It is also for

customers who have a self-maintenance agreement with Digital Equipment
Corporation.

. Structure of This Manual
This manual is divided into four chapters, four appendixes, a glossary, and an

index:
Chapter 1 describes the KA47 CPU module.
Chapter 2 describes the KA47 system configurations.
Chapter 3 describes the structure and operation of the KA47 firmware.
Chapter 4 describes the ROM-based diagnostic testing and troubleshooting
procedures for the KA47 systems.

Appendix A gives a flowchart of the procedure used to troubleshoot KA47
systems.

Appendix B gives a memory map for a KA47 system.

Appendix C gives the FRU numbers of the devices in MicroVAX 3100
platform systems.

Appendix D gives the location and the function of the jumper wires on the
KA47 CPU module.

vil

Associated Documents

The following documents contain more information about the MicroVAX 3100
platform systems:

MicroVAX 3100 Model 40 and Model 80 Cover Letter, EK-A0517-CL

MicroVAX 3100 Model 40 and Model 80 Installation Information,

MicroVAX 3100 Model 40 and Model 80 Operator Information,

EK-A0523-IN

EK-A0524-UG

MicroVAX 3100 Model 40 and Model 80 Cugtemer Technical Information,
EK-A0525-TD

MicroVAX 3100 Model 40 and Model 80 Troubleshooting and Diagnostic
Information, EK-A0518-TM

VMSTM Factory Installed Software User Guide, EK-A0377-UG

Related Documents
The following documents contain additional maintenance information about
the KA47 CPU systems:

* Guide to MicroVAX 3100 Platform Maintenance Information Kit,
EK-A0512-MG

viii

CPU Reference Information, EK-A0574-HR.001

BA42-B Enclosure Maintenance, EK-A0511-MG.001

|PB, EK-MV310-IP

Options, EK-A0519-MG

TZ30 Cartridge Tape Drive Service Menual, EK-OTZ30-SV

. Conventions
The following conventions are used in this manual:
Convention

Description

Corlix

Ctrl/x indicates that you hold down the Ctrl key while you press
another key or mouse button (indicated here by x).

A lowercase italic x indicates the generic use of a letter. For
example, xxx indicates any combination of three alphabetic
characters.

A lowercase italic n indicates the generic use of a number. For
example, 19nn indicates a 4-digit number in which the last 2 digits
are unknown.

{}

In format descriptions, braces indicate required elements. You must
choose one of the elements.

[]
O

In format descriptions, brackets indicate optional elements. You can
choase none, one, or all of the options.
In format descriptions, parentheses delimit the parameter or
argument list.

In format descriptions, horizontal ellipsis points indicate one of the
following:

Anitem that is repeated

An omission such as additional optionai arguments

Additional parameters, values, or other information that you
can enter

|
ttalic type

In format descriptiuns, a vertical bar separates similar options, une
of which you can choose.
Italic type emphasizes important information, indicates varables,

and indicates the complete titles of manuals.

boldface type

Boldface type in examples indicates user input. Boldface type in text
indicates the first instance of terms defined either in the text, in the
glossary, or both.

nn nnn.nnn an

A space character separates groups of 3 digits in numerals with 5 or

more digits. For example, 10 000 equals ten thousand.
n.nn

A period in numerals signals the decimal point indicator. For
example, 1.75 equals one and three-fourths.

MONCSPACE

Text displayed on the screen is shown in monospace type.

Convention

Description

Radix indicators

The radix of a number is written as a word enclosed in parentheses,
for example, 23(decimal) or 34(hexadecimal).

>5>>

Three right angle brackets indicate the console prompt.

UPPERCASE

A word in uppercase indicates a command.

Note

A note contains information that is of special importance to the user.

Caution

A caution contains information to prevent damage to the equipment.

$9.0.6.8.90.600.890400060000000¢8000008006406400080004690.194
$$.9,0.8.0.0.08.08600800908008
30080608 884400¢800664¢¢.904$4

p9.600.08.6.0.58000.0000840.46.6880060060804600090490.64¢
D.00.¢.0.40.0.0.683 0085008639630 080804004600688.8¢9844

§ 0040080080808 0008004840888885600 0604454040044
$ 0946004809000 0858600400¢8.0.8.08590.6.4806¢00¢4

bSOV EE 00000080.608060000.00806846046¢$+6.4
$0.0.0.6.0.6.6.80.800.86004408.6089.6300540.00¢4664
§0.8.60.00.04.0000.0.00008400069.68008000944
$0.8.0.9.00.00090.8.06089648045606.48640964¢1

XU XAXL KX HAXK LA RE KX XA KKK DA XA
$$.0.9.6.000.9.0.0.09.600.0.0606$969969¢4

P000.40.9.8.0.90.96806646.4¢66808
444
$9.69.9.0.606.660.58660.00.066084
§.0.8.9.8.0.8.0.80.9.090.0.4446494.04
.#.0.9.8.0.9.0.9.8.00.0.0.8¢600¢04
$.0.8.9.0.0.6.4.0.4.0.9.3.44.6.0.0.0.¢
}:0.9.6.6.0.6.4.9.4.6.0.4.0.4.4
04
$9.9.6.5.9.4.0.4.9.6.6.6.¢94

XAXKXXXKXXXXKK
XAXAKXKK
AKX
.9.9.0.8.9.0.0.¢¢

XAXXXXX
XAXXX
XXX

XXXXX

XXXXXXX

XXXXXXXXX
XXXXXXKXARXX

).0.8.6,9.8.9.6.9.4.484
XHAXKKAXXKAA
KKK

09.6.9.6.0.4.0.9.9.0.6.9.6,4.6.6
£9.0.9.0.0.9,$.9.0.9599.8¢¢954
1 9.9.0.0.6.6.9.9.0.9.6.6.9.0.6.09.0.904

[03.6904.48 46009800 40.6490¢64
$9.0.6.0.0.09.6:90.49

8869466409404

$0.0.09.0.8.0.9.49.0.0.0.4.8$4.$696449¢91
$0.0.0.80.008.¢.9084848688490030¢0¢4
$.9.9.0.9.09.9.0.6009.0006084969046496004

F0.0.0.0.6.0.699000.¢.004.66.686.600.¢60.¢¢9664
$9.0.0.0.00 698900884064.0860989048¢8¢056¢
19.8.00.0.
800500898
0.0.80.90
6.406848¢0646400(
.89

$9.0.6.0.0.9.0.6.9,6.0.094.¢.0.0.090,6000.
6404996084
09686
§0.0.02.0.93.4.0.0:0,4.00.00.0.099.0889099.0.06069565449¢6

0000968006005 9.058.6.99,09908:6060.6.9 6900686596664
i0:0.0.9.0.0.0.9.840.8.65:08.000.90004000.000950.5598648¢¢604
0. 9.9.0.:9.9.9.9.9,0.0.0.9.009.9.9.5,0.9.9:90.0.988.004636:0:0,.$.¢.9:06.63.6$68¢
AP A

A P A

PP NI

A U N P

A P AP e P8 P4 Pt r

s 20 rAan FCas

e sdesstbnte

mmsmmannremnrn

1
KA47 CPU Module Description
This chapter describes the KA47 central processing unit (CPU) module that
is used in the MicroVAX 3100 Model 80 systems. It gives information on the
following:

KA47 CPU module

MS44 or MS441. memory modules

MS44 or MS441. memory option installation

1.1 KA47 CPU Module

The KA47 CPU module is based on the Mariah chip set. It uses MS44 or

MS44L memory modules and a set of supported small computer system

interface (SCSI) devices. Figure 1-1 shows the KA47 CPU module.

The KA47 CPU module is the primary component of the MicroVAX 3100
system in which it is installed. The KA47 CPU module contains the following
components:

The DC595 processor chip—This chip 1s a complementary metal oxide
semiconductor (CMOS) virtual memory microprocessor. The key features of
the chip are as follows:
—

Support for the MicroVAX chip subset of the VAXTM instruction set

—~

Support for the MicroVAX chip subset of the VAX data types

Full VAX memory management

—

30-bit and 32-bit physical memory addressing

KA47 CPU Module Description

1-1

KA47 CPU Module Description

Figure 1-1

KA47 CPU Module

RE ENOBAGAA 91

The DC598 clock chip

The DC596 floating-point accelerator chip

The DC7201 S-chip—This chip is the primary interface between the CDAL
bus and all memory and input/output circuits. It contains the following
primary logic circuits:
Memory system control

Cache invalidate assist
Single SCSI controller interface

Direct memory access DMA control

Input/output address decode and control for design specific features

1-2

256K bytes of second level write-through cache memory

QGate arrays DC7201 and DC7254A

KA47 CPU Module Description

* Basic systemn memory (8M "ytes of random-access memory [RAM]
consisting of two MS44-AA cr MS44L-AA memory modules)

Support for up to 72M bytes of RAM

256K bytes of read-only memory (ROM»—This ROM contains the boot

32.byte network address ROM

Time-of-year clock that includes 50 bytes of nonvolatile RAM

Four asynchronous communications ports as follows:

and diagnostic firmware for the system.

Three DEC423 ports—These ports are modified modular jack (MMJ)
connectors.

One modem control port—This port 1s a D-sub 25-way connector.

Ethernet controller for standard or ThinWireTM Ethernet

SCSI controller, NCR 53C94

Provision for asynchronous communications options that provide one of the
following:

—

Eight or sixteen additional DEC423 ports

— Eight additional modem ports
¢

Provision for synchronous communications options that provide:
=

Two synchronous ports

Figure 1-2 is a block diagram of the KA47 CPU module.

KA47 CPU Module Description

1-3

KA47 CPU Module Description

Figure 1-2 KA47 CPU Module Block Diagram
CDAL Opton Port
-

}

| (Asynchronous Expansion)

p-3

DC7245A

Mariah

Cache Control

q =

—

| | zseKoyes |
ache

] |

‘

DC595

DCs98

DC59%

;

P Chip

CLK Chip
F Chip

2F =

Memor
nsion
Expa

(8M bytes;
emcry

S Chp

Basc

DC 7201

‘ §

L L

Basic

Memory

__1

. i s

| [Cacre Moy| )'

{ One Mode
| Controt Port

]

i and Three

! DECA23 Ports

Modem Latches

and EIA Translabor

L_ ______

< i

% {

EDAL

[

. &

s 5

5¢e
o

55
Ly
W

Cache

?,La,

:;gj:daw

Ciock |

RAM

|I
53C84 SCSI

Controtiar

‘

Interna ['
Scs!
Port

AM 7992

Siagagz

| Coax Xcvr

Standard

Ethernet
Port

Extarnal
sCs|

) éhm\Mre
tharnet

Port

Por

RE ENOB4ATIM 91

KA47 CPU Module Description

The KA47 CPU module supports the following VAXTM data types:
*

byte, word, longword, quadword

character string

variable-length bit field

absolute queues

self-relative queues

f floating-point, d_floating-point, and g_floating-point

The operating system uses software emulation to support other VAX data
types. The KA47 CPU module supports the following VAX instructions:

’

1integer, arithmetic and logical

address

variable-length bit field

control

procedure call

miscellaneous

queue

character string instructions:

MOVC3/MOVCSH

CMPC3/CMPC5

LOCC

SCANC

SKPC

SPANC

operating system support

ffloating-point, d_floating-peint, and g_floating-point

The DC595 processor chip provides special microcode assistance to aid the
macrocode emulation of the following instruction groups:

Character string (other than those mentioned previcusly)

Decimasl string

KA47 CPU Module Description

1-5

KA47 CPU Module Description

CRC

EDITPC

The operating system uses software emulation to support other VAX
instructions. Figure 1-3 shows the controls, indicators, ports, and connectors
on the KA47 CPU module. Table 1-1 describes the functions of the controls,
indicators, ports, and connectors.

Figure 1-3 KA47 Controls, Indicators, Ports, and Connectors
DSw42
Logic Board

DHw42
Logic Beard

Connectars

‘/K

[

Connectors

[

internal SCS1 Connector

— Basic System

Mamory Connector

/ [~———~ Memory Expansion

/ /,

Connectors

33Vdc

Power Connector

_——— External SCSI
Conneactor

e e POWES
Connector

Basic

System

o~y

Memory

EAemory

onnactors

DHW42
/O Connectar

/Lfi

2 j?; \

/AN

MMJ Port 1

Ethernet Port

\ \\

[N\
\
/

A ThinWire

" W" \

DSWa2
/O Connector
MM.J Port 0

Connector .____,_.———\ N7
Cxpansuan

5 27\

\—— Ethernet

Switch

\— Standard
Ethernet Port
ED Di

N\
LED
Deelay
—— Break/Enable LED

\\
\\

Break/Enable Switch
\——— Halt Push Button

pu— Asynchronous Modem

Control Port 2

MM.J Port 3
RE ENOG466A 91

KA47 CPU Module Description

Tabie 1~1 Functions of Controis, Indicators, Connectors
Component

Internal SCSI connector
Basic system memory

Description

A connector that provides a connection for SCSI devices

mounted inside the system enclosure.

Two connectors for the basic system memory modules.

connectors

Memory expansion

Two pairs of connectors for memory options.

connectors

3.3 V direct current (dec)

A connector that provides a connection for 3.3 V dc power.

power connector

External SCSI connector
Power connector
ThinWire Ethernet port

A connector that provides a connection to SCSI devices that

are external to the system enclosure.

A connector for dc power.

A port that provides a connection to a ThinWire Ethernet
network.

Ethernet switch

Standard Ethernet port

A two-position switch that determines the type of Ethernet
that the system uses as follows:

Left position—selects the standard Ethernet type

Right position—selects the ThinWire Ethernet type

A port that provides a connection to a standard Ethernet
network.

LED display

A set of eight LEDs that provides power-up and self-test
diagnostic code information.

Break/Enable LED

A LED indicator that shows the function of MMJ port 3 as
follows:

On—MMJ pori 3 functions as a console port.

Off —MMJ port 3 functions as a communications port.

(continued on next page)

KA47 CPL Module Description

1-7

KA47 CPU Module Description

Table 1-1 (Cont.) Functions of Controls, Indicators, Connectors
Component

Description

Break/Enable switch'

A two-position switch that determines the function of MMJ

port 3 as follows:

Up position—MMJ port 3 functions as a console por-.
In this state, you can press the Break key on the
keyboard of a terminal connected to MMJ port 3 to put
the system in console mode

Down position—MMJ port 3 functions as a normal

communications port. MMJ port 0 functions as the
console port.

Halt push button

A momentary-contact push button that puts the system in

Asynchronous modem

EIA-232 compatible asynchronous port with modem control.

console mode.

control port 2

MMJ port 3

DEC423 compatible asynchronous port. This port functions
as an alternate console port when the Break/Enable switch
is set to the up position when you turn on the system.

MMJ port 1

MMJ port 0
DSW42 /O connector

DEC423 compatible asynchronous port.

DEC423 comnpatible asynchronous port. This port is the

primary console port.

A connector that provides a connection for the DSW42 input
/output cable.

DHW42 /0O connector

A connector that provides a connection for the DHW42 input
/output cable.

DSW42 logic board
connectors

Two connectors that provide connections for a DSW42 logic
board.

DHW42 logic board
connectors

Two connectors that provide connections for a DHW42 logic
board.

'The system recognizes the position of this switch only when the system is turned on.

1-8

KA47 CPU Module Description

. 1.2 MS44 and MS44L Memory Modules
The MS44 and the MS44L memory modules provide memory expansion for the
KA47 CPU module. The KA47 CPU module supports two variants of the MS44
unemory option and one variant of the MS44L option as follows:
The MS44L-BA (8M-bytes), which contains two MS44L-AA (4M-bytes)
memory modules

The MS44-BA (8M-bytes), which contains two MS44-AA (4M-bytes)
memory modules
The MS44-DA (32M-bytes), which contains two MS44-CA (16M-bytes)
memory modules
Note

Use only MS44 or MS44L memory modules qualified by Digital.

The rules for adding MS44 or MS44L memory options are as fnllows:
You must install both memory modules of a memory option. This means
that you can expand memory in 8M-byte or 32M-byte increments only.
You must install memory options in the next available connector pair in

ascending numerical order.
Figure 14 shows the location of the basic memory (8M bytes) and the memory

expansion connectors. Table 1-2 lists the memory configurations.

KA47 CPU Module Description

1-9

KA47 CPU Module Description

Figure 14 Memory Exparsion Connectors

Note: 1H and 1L are identifiers for the basic system memaory connectors.
RE _ENO6467A 91

1-10

KA47 CPU Module Description

Table 1-2 KA47 CPU Module Memory Configurations
Total

Basic System Memeory

increment 2

Memory

1H?

(bytes)

MS44-AA%7

MS44-AA

16M

MS44-AA

24M

MS44-AA

MS44.AA

MS44-AA

40M

MS44.AA

MS44-AA

MS44.CA®

MS44.CA

48M

MS44-AA

72M

MS44.AA

MS44-AA

MBS44-CA

Increment 3
3H

MS44-AA

MS44.CA

MS44-CA

V1H, 1L, 2H, 2L, 3H, 3L are connector identifiers (see Figure 14)
2The MS44-AA memory module is a8 4M-byte memory module. The MS44-BA memory option

consists of two MS44-AA memory modules. You cap use MS441-AA memory modules instead of
MS44-AA memory modules.

3The MS44-CA memory module is a 16M-byte memory module. The MS44.DA memory option

consists of two MS44-CA memory modules.

@ 1.3 MS44 or MS44L Memory Option Installation
The MS44 and MS44L memory options consist of two memory modules. Install

an MS44 or MS44L memory option on the KA47 CPU module as follows:
1.

Position the KA47 CPU module, component side up, so that the edge
connectors are facing you.

Identify the connectors on the KA47 CPU module into which you must
install the memory option (see Figure 1-4 and Table 1-2).

Insert the first memory module, with the side containing the bar code
facing you, into the connector on the KA47 CPU module (see Figure 1-5).

Caution
The connectors are keyed to ensure that you install the memory
modules with the correct orientation. Do not force the modules into the

connectors with an incorrect orientation.

KA47 CPU Mcdule Description

1-11

KA47 CPU Module Description

Caution

Make sure that you fully install the memory module into the connector
before you tilt the module towards the front of the enclosure.

Figure 1-5 Memory Module Instaliation

RE_ENOB470A
91

Tilt the memory module towards the front of the enclosure until the metal
locking clips on the connector lock the memory module in position.
Repest the procedure in step 1 for the second memory module. Insert it
into the other connector for that memory increment on the KA47 CPU

module.

1-12

KA47 CPU Module Description

6 Run the MEM diagnostic test (see Section 4.6) after you reinstall the

KA47 CPU module into the system enclosure to check that the memory is
working correctly.
Caution
When removing memory modules, you must release the metal clips on
the connectors of the CPU module.

KA47 CPU Module Description

1-13

P00 00000000 4000080080060880084000
006088096099 ¢8483
P08 6469060880 6009660000000080884800000990.699084944
$.9.800.0.049.0.866.40069069088088868048¢5.680500.008¢80.6494
DI

0.50.808808000808000008
8880 00090960449064.044

P4.8.0.8.60.0.060 05080808 08600808800¢00860.09800
04
f8.0.80.0.80.¢.0.0.8.00
0808 0.4406060.6.68408089048048069.¢
B0 00000008080 40060046080488¢4560¢6¢80900404
$.0.6.0.0.0.0.6.4.8.00890.00.00¢¢0868986966.6609864
p.9.0.6.09.0.¢.0.0868.00000 0446889600600 00 841

p.8.8.00.9.6.¢.0.9.8,9.8.690809.06.6.809.406.66$.¢¢
$.000.89.00.¢,88.06.0600.680806009$069004
:0.6,8,9,0.0,0.0.8.¢:4.8.99.¢0840044060904¢4

$.0.0.0.6.8.¢.63900.600000¢0903¢8
604

b0 060480800008 88060460604
pO.0.0.05.0.00 4808080688494
f.9.0.6.6.0.6.6.8.8.0,0.0.0.40.44644
p$.08.0.0.0.6.4.9.0.4.0.4,9.0.6¢4.
1 9.9,0.0,0.¢.6:8.6.6 50,0800
;9:4.8.0.0.0.0.5.8.8.¢.8¢,8
$4.9.6.0.6,4.0.4.9.4.4.94
XXXXKXXKAXKK
XUXXXXXAX
XUEAAXK

XXXXX
XXX
X

XAXXX
XXXAXXX

XXXKXXXXX

}9.9.2.0.0.6.6.9.694
XAXAXXKAXXAXX
}.9.9.9.8.9.9.9.0.5.4.0.5.9.94
XXAAXKARXK
KA XKL X
10.8:9.9.6.0.9.0.0.8692¢64¢.0
XAKU XX KA LKA H U

AL KXAK AL

}9.8.9.60.0.06.4.0.4.8$4.693090¢44

9.98.9085008880808.86484446¢4
HAXAKAAXKXAXAXR
KA KX AR RXKKX
$.9.8.0.9.0.6.00096.06$6.006849¢4940¢44
B 90000488 8660009.058.099846699060564

$0.6.6.8.0.8.0.0.4.60.09000666990080.0564
80504
$9.9.8.9.09,0.4.0.0.0800080808.006080.90866.46065

$0,9.6.0.0.0.0.¢.0.00960.9.6068480.00460084050.9900.9.4
0,0.0.0.9.00.6.0.0.080.$085500886089060 695580906643

1096.9000.900.480.0.0000666660600600996¢80640865.4
088, 80:0.8.0.6.90.8.09.0.09.9.000940606:598606:6.0.9:606059.044
§9.9.9.9.0.9.99.6.960.09.00¢.00008035004696.69890559¢00044

19:9.0.090.¢.98.590.08$9.00084694976.060000966.09.0606.§8509004¢

109.0,0,0.098¢.0600.90908.9.9.09095059006600.096.908665806480

f 02000840800 889508809600.0000000000809:0.9.000.0.900°¢60¢

2
Configuration
This chapter describes the KA47 system configurations. It gives information
on the following:
¢

Memory configurations

Mass storage devices

Communications options

2.1 Memory Configurations
A KA47 system has a basic memory of 8M bytes. This consists of two MS44LAA memory modules. You can add memory in 8M-by‘e or 32M-byte increments,

up to a maximum of 72M bytes. See Section 1.2 for information on the memory
configurations.

2.2 Mass Storage Devices
A KA47 system supports mass storage devices in the following categories.

Internal mass storage devices—These devices are mounted inside the
system enclosure.

External mass storage devices—These devices are self-contained units that

you can connect to the system externally.

2.2.1

Internal Mass Storage Devices
Table 2~1 shows the internal mass storage devices that a KA47 system
supports.

Configuration

2-1

Contiguration

Table 2-1

KAA7 Internal Mass Storage Devices

Option Name

Description

Size'

Capacity

(in)

RZ23L

Disk drive

3.5

120M bytes

RZ24

Disk dnive

3.5

209M bytes

RZ25

Disk dnve

400M bytes

TZ30°

Tape drive

5.25

95M-byte cartridge

TZK10*
RX264

Tape drive

5.25

Range of cartridges®

Diskette drive

Range of diskettes®

RRD42*

CDROM drive

525

600 Mbytes

!3ize of half-height device.
Z3upports 320-Mbyte and 525-Mbyte cartridges.

35;uppurt5 1.4-Mbyte and 2.8-Mbyvte diskettes.
1K 2movable media device.

The system enclosure determines the combinations of internal mass storage
devices in a KA47 system. See the BA42-B Enclosure Maintenance manual for
move information.

2.2.2 External Mass Storage Devices
The external mass storage devices connect to KA47 systems via the SCSI
connector on the back of the system enclosure. In KA47 systems, the SCSI bus
supports a maximum of seven mass storage devices. Therefore, the number of
external mass storage devices that you can connect depends on the number of
mass storage devices that are mounted inside the system enclosure.
The maximum number of mass storage devices in the system enclosure is five.
This means that you can connect at least two external mass storage devices.

A KAA47 system supports the SZ series of mass storage expansion boxes. The

SZ number defines the contents of each expansion box. Figure 2-1 shows the
numbering system for SZ expansion boxes.

2-2

Configuration

Figure 2-1

SZ Expansion Box Numbering System
SZ1nx-xXx

l———- Power Cord Type

Enciosure Type

A=120Vac

2 = BA42 Enclosure

6 = BA46 Enciosure

B-=240Vac

Left Compartment

Right Compartment

A =RZ55
B = RZ56
¢ = RZ57

A = RZ55
B = RZ56
C = AZ57

R = RZ58
X = Empty

E = TZK10

D = TLZ2042

"= RZ25"

F = RRD42

H = TZ30
L = RX23
M = RX33

P -RZ25'

R - RZ58

X = Empty
' The RZ25 disk drive fils in the BA42 enciosure only
2 The TLZ04 tape drive fits in the BA46 enciosure only

‘A KAA47 system also supports other types of external mass storage devices.
Table 2-2 gives the other external mass storage devices that a KA47 system
supports.

Table 2-2

Supported External Mass Storage Devices

Device

Description

RRD42-DA

RRD42 CDROM tabletop

TLZ04-FA

TLZ04 tape drive tabletop

TK50Z-GA/G3

TK50Z tape drive tabletop

The following rules apply when you are adding mass storage devices:

You can add a maximum of four external SCSI devices. A fully configured
SZ12 enclosure contains two SCSI devices.

You can add a maximum of two SCSI tape devices. Depending on the
configuration, the system may support two TLZ04 tape drives.

The BA40 single dnve expansion box contains one SCSI device.

Configuration

2-3

Configuration

is a single SCSI device. You can add a
e The RRD42 CDROM drive CDROM
drives.
maximum of three RRD42

Terminate the SCSI bus correctly. Failure to do this can cause a system

failure or corrupt data.

Digital recommends that you connect all SCSI devices to the same ac power
source.

Do not add or remove devices that are connected to the SCSI bus while the
power is on.

Digital does not guarantee the correct operation of a SCSI bus that does
not use the cables supplied by Digital or is not configured in accordance
with Digital recommendations.

2.2.3 SCSI ID Numbers
Each mass storage device must have a unique SCSI ID number. Table 2-3
gives the recommended SCSI ID numbers for the different types of internal
and external mass storage devices.
Table 2-3

SCSl D

Recommended SCS! ID Numbers for Devices

Device

RZ2* !

RZ2*'

RZ2* ! isystem disk)

RRD42

TZ30 or TZK10 isystem backup device)

SCSI controller (INITR)

'The asterisk (*) indicates that these devices can be RZ231., RZ24, or RZ25 disk drives.

2.3 Communications Options
A KAA47 system supports the following types of communications options:

Asynchronous communications options

Synchronous communications options

Configuration

Contfiguration

Each communications option has components that are installed in the system
enclosure and components that connect to the system externally.

2.3.1

Asynchronous Communications Options
Table 2-4 gives the asynchronous communications options that KA47 systems
suppo:t.

Table 2-4

2.3.2

Supported Asynchronous Communications Options

Option

Description

DiHW42-AA

Eight-line DEC423 asynchronous option

DHW42-BA

Sixteen-line DEC423 asynchronous module option

DHW42.CA

Eight-line EIA-232 modem asynchronous module option

DHW42.UP

Eight-line to 16-line DEC423 asynchronous upgrade option

Synchronous Communications Options
Table 2-5 gives the synchronous communications options that KA47 systems
support.

Table 2-5
Option

Supported Synchionous Communications Options
Description

Model 30

DSW41.-AA'

One-line EIA-232/V.24 synchronous option with one external cable,
BC19D-02 (17-01110-01)

Model 40

DSW42-AA?

Two-line EIA-232/V.24 synchronous option with two external cables.
BC19D-02 (17-01110-01)

This option is supphied with one external cable that supports the EIA-232/V.24 interface.

2This option is supplied with two external cables that support the EIA-232/V.24 interface.
The DSW41-AA and the DSW42-AA options also support the communications

interfaces histed in Table 2-6, but you must order the external cables

separately.

Configuration

2-5

Configuration

Table 2-6 DSW41-AA and DSW42-AA Communications Support
Communications Interface

External Cable

ElA-423/V.10

BC19E-02' (17-01111-01)

ElA-422/V.11

BC19B-02' (17-01108-01

"Two required for DSW42-AA

2-6

Configuration

p0.0.0.0.0.0.0 8086000000 80000060 040 00680800400888.004600.8.04
PO

0 8000000

ER 0P 0S 00000009000 00808000 00909064

Di0.0.46600 06600005000 04000008 084880800000408.0804464
P00000.000006905050000000086490086080649.44.4

PS40 888800008686000
00880 8090860660808044
FO0.00.0 809000000008 000008.6000880400068¢464¢4

pO9 80600000000000880800080088808¢90000.¢4
1600006000049 8064486880660888084048906¢
F 8000860068 000.08080¢44088 0845486044
$.0.00.9.6.0.9.0.0.0.0.008600004$90848.098¢664
PS08000000000080008884098600¢
§.6.4.0.8.6.8.08.6.088.0600.049889808883$4
0.0.0.0.6.9.0.9,6.0.0.8.0.4.0.9.6.00.8¢0.¢.0¢91

$ 4099548690680 0.80456468494
XX XXX

KK KA XA ZX AN XK XXXKK

$9.5.6.0.9.4.4.8.09.6$6464964¢04
$8.0.6.0.0.6.6.6.6.9.0.4.0.9.0.0.6.41
$.6.4.4.6.8.6.6.0.6.4.¢.4.49.99
6.9.0.0.9.9.4.0.0.9.¢.4.4.¢4
}:9.0.$.9.4.9.49.¢.9.9.44
KAXAXEXEHXX

XAXAXXAKX
XXXUXEX
9.9, ¢4
XXX
X

XXX
XAXXX

XAKXXAXX

XAXXXXXXK
).0.9.8.6.8.0.64044
$.0.9.8.9.4.86.6.44.0.9.4
AAXXXUXKAXXXXXK

XAXX KX XKXAXXKAKAX
1$.4.6.9.8.8.¢.69.0.4.¢¢9.¢¢
644

)$.9.0.0.610.9.9.9.9:4.9.4.9.9.9.9.4
494
XA KA RKA KX KX UL XA

A LAKLK

} 80566850 08.0546048946446441
$0.8.0.8.0.0.0.40.0.8490.68048.4$044.0¢099
P09 0088080000 00.666.906¢¢.04640944

PO GG E4300 04890400.90.0.6900649040.94¢
$.0.5.0.0.6.0046400880048.0869.68056480006¢4
$0.8.6.0.0.0.0.980.800000406.849¢4645904590.64
$0.0.60.000.8.0.0.0.008006040.98.480699.44594566684

D 0.8.0.0.9.0.0.0.0.8004850.060000.089.8.9.6.88090¢0004

§0.8.0.0606.9.0.00.8¢88003606005680606606000006044
6:8.4,9.0:0,0.0.6.9.0.8.9.0.6,9.000.0.40.9.0.09.6.0.¢,9.9,0,6.6.6¢0.0.06.9¢1
}9:0.0,0.0.0.0.0.0.0.0.9.0.0.0.0.0.04.89.06.06.$99000858580.$6045984¢
19,0.8:9.9.0.¢.0,0.0.99.9.9.0.9980.90400.00680.0006.06.0¢68.0668¢996.904

$9.9,0.9.4.0.6,0.0,0.9.8.6.¢.9.0.6.$,0.8.96.6.9:0.9980.0608506.650964696868
$9.0.8.0.0.9.0.9.8,0.6809.0004.9.8.95¢9604006,50$0.0.0686.669666466.9.01

3
KA47 Firmware
This chapter describes the structure and operation of the KA47 firmware. It
gives information on the following:

Power-Up test and initialization—This code tests and initializes all the

devices in a KA47 system.
¢

Console program—This program parses and executes all the commands

entered at the console prompt (>>>),
®

Self-Test—This code executes when a user runs a diagnostic self-test
by entering the command TEST at the console prompt. This code also
executes when a user runs tests in the Manufacturing test environment.

Utilities—This code provides device-specific functions that are not provided
by the other KA47 firmware functions.

System exerciser—This code tests the operation of devices in the system
concurrently. The purpose of this code is to provide a high level of DMA
and interrupt activity for devices in the KA47 system.

3.1

Power-Up Test and Initialization
When you turn on the system, the system executes the power-up test and
itialization code, which builds a power.up test display on the console

terminal that is connected to the system unit. When the default recovery
action 18 set to 3 (see CFU Reference Information, Section 1.11.5), the system
is in console mode when the power-up test and initialization code is completed.

Figure 3-1 shows a successful power-up test display. The display differs

slightly depending on the type of console terminal you use.

KA47 Firmware

3-1

KA47 Firmware

Figure 3-1 Successtul Power-Up Test Display
kaga7-a vi. 0P
08-00-2B-04-03-12 @
312
@

AAS NI RR IR IR o
B LB R R BB URERERRR
REGARRBBEREBRRARRENBR
>> 6

A-On a Standard ASCHl Terminal

@
Kas7-2 vi.0
08-00-2B-04-03-12 @
w2
@

>>> @

B-On a Graphics Display Terminal

The CPU name and the version of the KA47 firmware. The character V
indicates the version of the system firmware. The number 1.0 indicates the
release number.

The Ethernet address of the system.
The size of the internal system memory.

The status bar shows the progress of the test. When the status bar reaches
the completion mark, the test 1s completed successfully.
The console prompt.

Figure 3-2 shows an unsuccessful power-up test display In Figure 3-2, the
incomplete status bar shows that the power-up test did not complete because of
an error. The system displays the error information under the status bar.

3-2

KA47 Firmware

Figure 3-2 Unsuccessful Power-Up Test Display
Ka47-a v1.0@p
08-00-2B-04-03-12@
32
@
O

22 001

e e —~+@

0066 &

>>> @

A-On a Standard ASCll Terminal

KA47-A V1.0@)
08-00~2B-04-03-12 @
3@

I ©
22 001

0066 @

>>> @

B-On a Graphics Display Terminal

The CPU name and the version of the KA47 firmware. The character V
indicates the version of the system firmware. The number 1.0 indicates the
release number.

000606

The Ethernet address of the system.

The size of the internal system memory.
Incomplete status bar.
Completion mark.
An error message—The elements are as follows:

Two question marks (??) indicate a hard error, that is, an error that
you must correct before you boot the system. A single question mark (7)
indicates a soft error, that is, an error that you do not have to correct
before you boot the system.

(01 is the field replaceable unit (FRU) number of the device that
fails. See Appendix C for the list of FRU numbers.

9 s the test number (in this example, the Ethernet test number).

NI is the test mnemonic (in this example, the Ethernet test mnemonic).

KA47 Firmware

3-3

KA47 Firmware

e 0066(decimal) is an error code (see CPU Reference Information, Table
3-11).

The console prompt.
Note

The rest of the console screen illustrations in this manual show
the system output only on an American Standard Code for
Information Interchange (ASCII) terminal. The system output
on a graphics display terminal is slightly different from a standard
ASCII terminal; a solid status bar replaces the line of number signs (#).

3.2 Console Program
The console program is firmware code that controls a device (the console
device). This device allows you to enter diagnostic test commands (console
commands) when the system is in a halt state (console mode).
The console program also contains the input and output routines that

control the transfer of data to and from the console device. The power-up

tests, extended self-tests, utilities, system exerciser, and virtual machine

bootstrap (VMB) program also use these routines to transfer data to and from
the console device.

3.2.1

Console Device
When you turn on the system with the default recovery action set to 3 (see

CPU Reference Information, Section 1.11.5), the system is in console mode
after the power-up tests are completed. Depending on the position of the

break/Enable switch on the back of the system unit, the terminal connected to
either MM port 0 or MMJ port 3 is the console device (see Table 3-1).
Table 3-1

Console Device Port Selection

Break/enable Switch

Posltion’

Console Terminal Port

Down

MMJ Port 0

MMJ Port 3?

"The system recognizes the position of the switch only when you turn on the system.

20n a terminal connected to MMJ port 3, you can press the Break key to put the system in console
mode.

3-4

KA47 Firmware

FRFRV
S

VI
RAN W

Figure 3-3 shows the location of the MMJ ports on the system module.
Figure 3-3

Location of the Console-Related Ports and Switches

\ _____
\

Braak/Enable
LED

Break/Enabie
Switch
-

Halt Push Button

MMJ Port 3
.

M) Port 0
RE_EN0G4B8A 91

When a system 1s delivered, the break/enable switch is set to the down position,
therefore MMJ port 0 1s the console terminal port. To use MMJ port 3 as the
console terminal, follow these steps:

Turn off the system unit.

Set the break/enable switch to the up position.

Turn on the system unit.

MMJ port 3 1s now the console port terminal. You can connect one of the

following console devices to this port:
A VTTM geries type terminal (for example, VT330TM)
¢

A printer (for example, LA34)

KA47 Firmware

3-5

KA47 Firmware

e A host computer that runs special test software (for example, APT)

If you connect a VT series type terminal to MMJ port 3, you can press the
Break key on the keyboard to put the system in console mode. To ensure the

correct operation of the terminal, you must set the cemmunication parameters
for 4 terminal connected to MMJ port 3. Table 3-2 gives the correct terminal
settings.

Table 3-2 Terminal Settings
Feature

Setting

Terminal mode

VTnnn-7bit

Transmit speed

9600 baud

Receive speed

recelve = transmit

Character format

8 bits, no parity

Stop bits

Comm1 port

DEC-423 (data-leads-only)

3.2.2 Console Commands

You can enter console commands from a console device. CPU Reference

Information, Chapter 1, describes the console commands that you can enter.
When you enter a command at the console prompt, the console program parses

and exect:tes the command. If the conscle program detects an error, it displays
an ervor message. CPU Reference Information, Chapter 2, gives the console
messages for KA47 systems.

3.2.3 Console Mode
The system is in console mode when one of the following conditions occurs:
e

System power-up—When you turn on the system, and the recovery action
flag is set to halt the system.

3-6

External halt—You can initiate an external halt in one of two ways:
—

Press the halt push button on the back of the system unit.

—

Press the Break key on the keyboard of a console device that is
connected to MMJ port 3 on the back of the system unit. This function
is effective only when the break/enable switch is set to the break (up)
position before you turn on the system.

Boot failure—The system fails to boot correctly.

KAA47 Firmware

KA47 Firmware

(ritical CPU condition—The system forces a CPU restart or a reboot when
it detects an event that it interprets as a severe corruption of its operating
environment. The VMS sysgen parameter, BUGREBOOT, determines if
the system restarts or reboots. If BUGREBOOT is 0, the system restarts;
if BUGREBOOT is 1, the system reboots.

Kernel program mode—The system processes a halt instruction in kernel
program mode. The recovery action flag is set to halt the system.

When the system is in console mode, it displays the console prompt. You
can enter console commands at this prompt (see CPU Reference Information,
Chapter 1).

3.2.4 Console Security
The KA47 systems have a console security feature that you can use to restrict

the use of certain console commands to authorized users. You use the SET
PSE command to enable the security system (see CPU Reference Information,

Section 1.11.8), and you use the SET PSWD command to enter a console
security password (see CPLU Reference Information, Section 1.11.9). Users must
know this password to access the full range of console commands. When the
console security feature is enabled, there are two console modes in which the
system operates as follows:
*

Unprivileged console mode

Privileged console mode

When you put the system in console mode, and the console security system is
enabled, the system operates in unprivileged console mode. You can enter only

the following console commands:
e

BOOT (without parameters)

CONTINUE

! (Comment)

When you enter a command other than the four commands shown previously
while the system is in unprivileged console mode, the system displays an error
message as follows:
223 ILL CMD

You can use the LOGIN command (see CPU Reference Information, Section 1.9)

to enter privileged console mode. To use this command, you must know the

current console security password. When you enter the correct password, you
can use all of the console commands.

KA47 Firmware

3-7

KAA47 Firmware

In privileged console mode, you can use the SET PSE command to disable the .
console security feature (see CPU Reference Information, Section 1.11.8). When
the system is in privileged conscle mode, you can enter one of the following
commands to return the system to unprivileged console mode:
¢

BOOT

CONTINUE

HALT

START

If the system owner forgets the password, you can clear the password in the
nonvolatile RAM (NVR) as follows:
1.

Set the on/off switch on the system unit to the off (O) position.

Remove the enclosure cover. See the BA42-B Enclosure Maintenance
manual for more information.

Use a screwdniver to short-circuit two NVR contacts on the CPU module
(see Figure 3—4).

3-8

KA47 Firmware

KAA47 Firmware

Figure 3-4 Location of the NVR Contacts for Clearing the Password

MMJ Port 1

MMJ Port 3
Asynchronous
Modem Control
Port 2

3.3 Vdc Power
Connector

Install the enclosure cover.

Turn on the system unit.

RE EN0G49GA
G1

When the console prompt is displayed, the owner can use the SET PSWD

command (see CPU Reference Information, Section 1.11.9) to enter a new
password.

3.2.5 Console Command Conventions
When entering console commands, the following rules apply:

Commands cannot be more than 80 characters long.

The command interpreter is not sensitive to case. The command
interpreter treats lowercase ASCII characters as uppercase ASCII

characters.
¢

The command parser rejects the characters that have ASCII codes greater
than 7FH. You can, however, include these characters in comments.

Type-ahead text entry is not supported. The command interpreter checks
characters that it receives before it displays the console prompt, but ignores

all other characters except control characters (see Table 3-3).

KA47 Firmware

3-9

KA47 Firmware

In console mode, certain keys have special control functions. Table 3-3 lists

these keys and control functions.

Table 3-3 Console Mode Control Keys
Key

Function

Return key

Ends a command line.

Delete key

Deletes the previously typed character. On VT series terminals,

press this key to delete a character from the screen. On hard copy
terminals, the system prints a slash (/) before and after the deleted
character.

Break key '

On a console device connected to MMJ port 3, press the Break key

Ctri/C

Causes the console program to abort processing a command. The

Ctrl/O

Causes the console program to discard output until you enter the
next Ctrl/O sequence or until the console program receives the next
console prompt or error message. Ctrl/C also cancels Ctri/O. The

to put the system in console mode.

console program displays Ctrl/C as *C.

console program displays Ctrl/O as *O.

Ctrl/Q

Ctrl/R
Cerl/S

Resumes the console output that is suspended when you press Ctrl
/8.

Causes the current command line to be displayed, without the
deleted characters.

Suspends the current command line that the console program
displays until the next Ctrl/Q sequence.

Ctrl/U

Discards all the characters on the current command line. The

console program does not abort a command if it receives this control
character while processing the command. The console program
displays this control key as *U.

! Applies only if the break/enable switch on the back of the systemn unit is set to the break (up}

position before you turn on the system.

Note

During X command data transfers, the command interpreter treats the
codes for the control keys as binary data.

3-10

KAA47 Firmware

KA47 Firmware

. 3.3 Self-Test
The KA47 firmware provides a set of diagnostic tests that you can access using
the console command, TEST (see CPU Reference Information, Section 1.14).
The console program passes a list of the device numbers (or device mnemonics)
and test parameters to the test command dispatcher. The test command
dispatcher is the code that runs the self-test for each device that the console
program passes. The tests run until all the tests complete successfully or an
error occurs.

When you use the TEST command, you must specify a device. Table 3—4 gives
the device number and device mnemonic for all the devices in KA47 systems.
Table 3-4

Device Numbers and Mnemonics

Device Number

Device Mnemonic

Description

NVR

Nonvolatile RAM

Reserved for future use

Serial line controller

CACHE

Cache system

MEM

Memory

FPU

Floating-point unit

Interval timer

SYS

Miscellaneous CPU module hardware

Network interface

SCSs1

SCSI controller

Reserved for future use

COMM

Synchronous communications option
Reserved for future use

ASYNC

15 to 99

Asynchronous communications option
Reserved for future use

When you use the TEST command to test a device, you can specify either the

device number or the device mnemonic. You can enter a command to test the
following:

A single device

Multiple devices

A range of devices

KA47 Firmware

3-11

KA47 Firmware

e A combination of the three previous options
Table 3-5 gives some typical TEST (T) command lines.
Table 3-5 Typical TEST Command Lines

Type

Single device

Command

Using Device

Numbers

Mnemonics

TS5

T MEM

Description

Runs the self-test on
memory.

Multiple devices

T 3,4

T DZ,CACHE

Device range

T 5:7

T MEM:IT

Combination

T 1,3,8:10

T NVR,DZ,SYS:SCSI

Runs the self-test on the
serial line controller and
the cache system.

Runs the self-test on the

memory in the system, the
floating-point unit, and the
interval timer (IT).

Runs the self-test on the

nonvolatile RAM, serial line
controller, miscellaneous
CPU module hardware,

network interface, and
SCSI controller.

You can include device numbers and device mnemonics on the same TEST
command line. The following command is an example of a TEST command
that has device numbers and device mnemonics on the command line:
>>> T 10:8,€6,MEM:D2Z

When you enter the test commands, the following rules apply:

You can specify device numbers and mnemonics in any order on the
command line.
You can include a device number or a device mnemonic many times on the
same command line.

The maximum number of tests specified on a single command line must
not exceed fifteen.

3-12

KA47 Firmware

‘

KAA47 Firmware

In the example shown previously, although the combined number of device
mnemonics and device numbers on the command line is five, the number of
tests specified is seven. This means that you can specify only eight more tests
on this command line. Figure 3-5 shows a successful self-test display.
Figure 3-5 Successful Self-Test Dispiay
>>> T 9:7
fwmmm—————

ok®
>>>

A console status message that indicates a successful test.

Figure 3-6 shows an unsuccessful self-test display.
Figure 3-6

Unsuccessful Self-Test Display

>>»>> T 9.7
bomemca——— +

$iit @

22 001 07 FP 22

84 FAILED
>>>

Incomplete status bar.
Two question marks (??) indicate a hard error, that is, an error that you
must correct before you boot the system. One question mark (?) indicates

QOO0
0

a soft error, that is, an error that you do not have to correct before booting
the system.
The FRU number of the device that 1 .ils.
The device number of the device that fails.

The device mnemonic of the device that fails.
An error code that corresponds to a specific device error.

A console error message that indicates a test failure (see CPU Reference
Information, Chapter 2).

KA47 Firmware

3-13

KA47 Firmware

CPU Reference Information, Chapter 3, lists the error codes and messages that .

the KA47 diagnostic tests generate.

3.3.1 Additional Error Information for Seif-Tests
When a test fails, you can get more error information about the test using the
following command:
>>>

SHOW ERROR

Figure 3-7 is an example of the information that this command displays.
Figure 3—7

o 6
2% 401

Additional Error Information for Self-Tests

0050

001 000B 00000051 00000220 00001E08 00000000 00000000 000000000
>>>

Two question marks (??) indicate a hard error, that is, an error that you
must correct before booting the system. One question mark (?) indicates a

soft error, that is, an error that you do not have to correct before you boot
the system.

The FRU number of the device that fails.

The device number of the device that fails.
The device mnemonic of the device that fails.
An error code that corresponds to a specific device error.

A line of error information that is related to the device name (or test
number) on the line immediately preceding it. In the example, the
additional error information line is related to the DZ test (test 3). See
CPU Reference Information, Chapter 3, for information about the formats
and meaning of the additional error information for the various tests.

3-14

KA47 Firmware

. 3.3.2 Test Environments

You can run diagnostic self-tests in three different environments as follows:
¢

Customer environment

Digital Services environment

Manufacturing environment

The test environment determines the level of device testing. For example,
testing in the Customer environment is minimal, whereas testing in the Digital
Services environment and the Manufacturing environment is more extensive.
3.3.2.1

Customer Environment
This 1s the default test environment in which the user tests the operation of
the system. To return the system to the Customer environment from another
test environment, enter the following command:
>>>

3.3.2.2

SET DIACENV

Digital Services Environment
This is the test environment that Digital Services personnel use to test the
system.

Note
You must connect a loopback connector (29-24795-00) to the

asynchronous modem control port 2 on the back of the system unit
before you can put the system in the Digital Services environment.

The firmware verifies that the loopback connector is present by checking that
pin 12 and pin 18 of asynchronous modem control port 2 are looped. To put the

system in the Digital Services environment, enter the following command:
>>> SET DIAGENV 2

In this test environment, certain tests and utilities require loopback connectors

(see Chapter 4).

KA47 Firmware

3-15

KA47 Firmware

3.3.2.3 Manufacturing Environment

This is the test environment that Manufacturing personnel use to test the
system. Running tests in this environment is also known as extended self-test.
Note

You must connect a loopback connector (29-24795-00) to the
asynchronous modem control port 2 on the back of the system unit
before you can put the system in the Manufacturing environment.

The firmware verifies that the loopback connector is present by checking that
pin 12 and pin 18 of asynchronous modem control port 2 are looped. To put the
system in the Manufacturing environment, enter the following command:
>>>

SET DIAGENV 3

In this test environment, certain tests require loopback connectors and media
with special keys (see Section 3.4) to which the system can write data (see
Chapter 4).

3.4 Utilities

The KA47 firmware provides utilities for the following devices:
*

SCSI

COMM

You invoke a utility using a TEST command that has the following format.:
>>> T{EST)/UT[{ILITY]

<devnam

devnbr>

where:
¢

T/EST) s the TEST command

JUT/ILITY] is the utility qualifier

devnam is the device mnemonic

deuvnbr is the device number

If an error occurs or you press Ctrl/C to interrupt a utility, the console
generates a display similar to the following:

3-16

KA47 Firmware

scel £ err 196@
84 ralL@®
>>>

3.4.1

Utility error message and code (see CPU Reference Information, Chapter 4)

Console error message (see CPU Reference Information, Chapter 2)

SCSi Utilities
To get a list of the utilities available for SCSI devices, enter the following
command:
>>> TEST/UTIL SCSI

The system displays the following menu:
1 ~ SCSI-flp key
2

= SCSI-tp key

3 - SCSI~hd
dsk _eras
4

- SCsI-flp
fmt

SCSI util>>>

The functions of these utilities are as follows:

SCSI-flp_key—Puts a special diagnostic key on a floppy diskette that
enables the firmware to write data to the diskette during tests in the
Manufacturing environment.

Note
This utility works only in the Digital Services environment. To put the
system in the Digital Services environment, see Section 3.3.2.2.

SCSI-tp_key—Puts a special diagnostic key on a tape cartridge that
enables the firmware to write data to the tape cartridge during tests in the
Manufacturing environment.
Note

This utility works only in the Digital Services environment. To put the

system in the Digital Services environment, see Section 3.3.2.2.

KA47 Firmware

3-17

KAA47 Firmware

Caution

You can use the SCSI-hd_dsk_eras utility in the Customer
environment.

SCSI-hd_dsk_eras—Erases the contents of a disk dnive.

SCSI-flp_fmt—Formats a floppy diskette.

For example, to erase the data on a hard disk, enter 3 at the SCSI_util>>>
prompt as follows:
SCSI util>>> 3

The KA47 firmware prompts you for the SCSI ID of the disk drive from which
you want to erase the data. If the SCSI ID of the disk drive is 1, for example,
enter 1 in response to the prompt as follows:
5CsI_1d{0-7)>>> 1

The KA47 firmware prompts you for the logical number of the drive, usually 0,
unless there is another SCSI controller in the system. Enter 0 in response to
the prompt as follows:

SCSI lun{(0-7)>>> 0
The KA47 firmware displays a status message, then a prompt. You must enter

OK in response to this prompt as follows:
SCSI HD DSK_ERAS UTIL

DKA100

OK> OK

The KA47 firmware displays a status bar, indicating that the erasing of the
disk is progressing. This operation takes several minutes. When the operation
1s complete, the KA47 firmware displays a complete status bar and status

messages as follows:
Fo8E0408000000000444
SCSI
bb repl 0
SCSI_util succ

3-18

KA47 Firmware

. 3.4.2 COMM Utilities
The KA47 firmware includes some utilities for synchronous communications

devices. These utilities are not intended for use by Digital Services personnel.

3.5 System Exerciser
The KA47 firmware has a system exerciser that tests the simultaneous
operation of multiple devices in a KA47 system. The system exerciser tests the
interaction of devices in the system by causing maximum DMA and interrupt
activity. You invoke the system exerciser by entering a TEST command that
has a test number in the range 100 to 106. For example:
>>> T 100

The KA47 firmware causes the VMB program to load the system test kernel
and monitor. The system test monitor determines which TEST command

caused it to load. Control then passes to the system test kernel, which defines
the appropriate operating environnment. You can run the system exerciser in

any of the following environments:

(Customer environment

Digital Services environment

Manufacturing environment

Table 3-6 gives the predefined system exerciser commands and the test
environments in which they run.

Caution
The system exerciser tests, T 102 and T 104, are destructive tests.

When you run these tests, the data on the disk drives (excluding the
system disk that contains VMS) and the data on the removable media,
which are installed in tape drives and diskette drives, are deleted.

KA47 Firmware

3-19

KA47 Firmware

Table 3-6

Predefined System Exerciser Tests

Command

Action

Environment

Code

T 100

Runs two passes of the

Customer environment

Runs two passes of the

Digital Services

T 102

Runs the system exerciser

Digital Services

T 103

Runs the system exerciser

Manufacturing

T 104

Runs the system exerciser

Special’

T 1086

huns the system exerciser on

Digital Services or

T 101

system exerciser.

until you press Ctrl/C.
until you press Ctrl/C.

until you press Ctrl/C.

selected tests. The firmware

Manufacturing?

prompts you to choose the
tests you want to run.

!This is a special environment used by Manufacturing.
2Use the SET DIAGENV command to put the system in the environment you want (see CPU
Reference Information, Section 1.11.3).

Figure 3-8 shows a successful system exerciser test.

3-20

KA47 Firmware

Figure 3-8 Successful System Exerciser Test
>>> T 101

KA45/47 v1.0

System Test CS

oz #44 ©

NI #448484

sCsI §

coM $#444

ASYNC §#844

##%%% SYT DISPLY SUMRY (('1'=Y),

0 00:00:59

("O'=N)).............
. ... >

© The CPU name and the version of the console program. The character V
indicates the version of the system firmware. The number 1.0 is the release

number.
CS is the Digital Services environment (see Table 3-6).
The duration of the test in the format: days hours:minutes:seconds.
A status bar for each device that the system exerciser tests.
A prompt for summary screens (see Section 3.5.2)—Enter 1 to display the
summary screens; enter 0 to display the console prompt.

Figure 3-9 shows an unsuccessful system exerciser test.

KA47 Firmware

3-21

KA47 Firmware

Figure 3-9 Unsuccessful System Exerciser Test
>>>

TN
AL

T
+

KA45/47 V1.0
3

Dz #

NI ¢§

0 00:00:59

System Test CS

SCSI #

com ¢

ASYNC

0305

0 06:01:26

*exx* SYT DISPLY SUMRY {("1'=Y), C'0'=N))......
... .......... )
@

The CPU name and the version of the console program. The character V
indicates the version of the system firmware. The number 1.0 is the release

number.

CS is the Digital Services environment (see Table 3-6).
The duration of the test in the format: days hours:minutes:seconds.
Two question marks (??) indicate a hard error, that is, an error that you
must correct before booting the system. One question mark (?) indicates a
soft error, that is, an error that you do not have to correct before booting

the system.
The device number of the failing device.

The device mnemonic of the failing device.
The number of the most suspect

FRU.

A device-specific error code (a decimal number, see CPU Reference
Information, Section 5.3).

The time when the test failure occurred.
A prompt for the summary screens (see Section 3.5.2). Enter 1 to display

the summary screens; enter 0 to display the console prompt.

3-22

KA47 Firmware

. 3.5.1 Selective System Exerciser Test (T 106)
In the Digital Services and Manufacturing environments, you can use the
command T 106 to select devices that you want to include in the system

exerciser test. When you enter this command, the system prompts you to
choose if you want to include or exclude any of the devices in the system
exerciser. Figure 3-10 is an example of the display that the system exerciser
command T 106 produces.

Figure 3-10

Selective System Exerciser Test (T 106) Example

>>> T 106

TST DEV - DL

TST DEV - NI

TST DEV -~ SCSI

TST DEV - COMM

TST DEV = ASYNC

In Figure 3-10, you must enter 1 or 0 after each prompt. Enter 1 to include
the device in the system exerciser test; enter 0 to exclude it. In Figure 3-10,

the system exerciser runs on the devices DZ, NI, and ASYNC.
Note

When you run test T 106 and if you do not include the DZ test, you
cannot press Ctrl/C to stop the test. When a console terminal is

connected to MMJ port 3, you can press the Break key to stop the
test. When a console terminal is connected to MMJ port 0, you can
press the Halt button on the back of the system unit to stop the test.

When the test is finished, you can enter the SHOW ESTAT command to display
the summary screens that test T 106 generated.

KA47 Firmware

3-23

KA47 Firmware

3.5.2 Summary Screens

The system exerciser generates summary screens that show the progress
or results of the most recent system exerciser test. The system displays a
summary screen when one of the following conditions is satisfied:
e

When the system exerciser test completes and you choose to view the
summary screens

When you press Ctrl/C to interrupt a system exerciser test and you choose

When you enter the command SHOW ESTAT (see CPU Reference

to view the summary screen

Information, Section 1.12.7)

The summary screens are displayed in the order in which the tests were
performed. When the system exerciser test is complete, it displays a prompt at
the bottom of the screen as follows:
*x+¥+ QYT DISPLY SUMRY

({('1'=Y),

('0'=N))

Enter 1 to view the first summary screen or 0 to display the console prompt.
Figure 3-11 is an example of a summary screen for the DZ test that was

performed during a system exerciser test. The summary screen formats of the

individual tests are the same in all test environments.

324

KA47 Firmware

Figure 311 Summary Screen for System Exerciser DZ Test
1]

xaxxwxxxxsx FST EXT ERRPT

Line

L Param

0
1
2
3

*wxiwxrxrs

3DZ

Chr Xmt

Chr Rec

00000780
00000780
00000780
00000000

00000780
CO0DO7B0
00000780
00000000

SYST
NXT
ST
SCR

0 00:01:25 **¥xxxxxns

Error

*xx*
****x No Err
****x No Err
*x*x*
*¥*** No Err
***x*
*Not Tstd - Cons_lin*

('1'=Y),

("'0'=N))......... > @

Summary screen identifier.

Test number and mnemonic.

The time taken to complete the test.
The number of the line being tested as follows:
0 represents MMJ port 0
1 represents MMJ port 1

2 represents asynchronous modem control port 2
3 represents MMJ port 3

0000

The communication line parameters (displayed only when an error occurs).

The number of characters transmitted.
The number of characters received.

A comment denoting the type of error.
A prompt for the next summary screen. Enter 1 to display the next
summary screen, enter 0 to display the console prompt.

KA47 Firmware

3-25

KA47 Firmware

Figure 3-12 is an example of a summary screen for the NI test that was
performed during a system exerciser test.

Figure 3-12 Summary Screen for System Exerciser Ni Test

sxesexxser FST EXT ERRPT

(3]

9NI

sxxtrressx SYSTS
NXT SCR
T ((*

0 00:01:35 *#sswxwans

((*1'=Y),

(“0'=N)).

... ... > @

@ Summary screen identifier.

@ Test number and mnemonic.
© The time taken to complete the test.
@ A prompt for the next summary screen. Enter 1 to display the next
summary screen, enter 0 to display the console prompt.
Figure 3-13 1s an example of a summary screen for the SCSI test that was
performed during a system exerciser test.

3-26

KA47 Firmware

Figure 3-13 Summary Screen for System Exerciser SCSI Test

WRTS

RDS

ADR
A

®©

G Ah
B Rt

e
BT

0 00:01:31 *xxxxreees

10SCSI

sxes2exees FST EXT ERRPT

S e

MerSh

PHS INF LBNSTRT

Gs TS
AN

EERr

e
R Em

1/0 00010987 00000000

3/0 00005643 00005643

4/0 00000028 00000028 160 150
-

——

- =

®®®0 6000006000 0C

sxwxxexeee SYSTST
NXT SCR ((*

T W TS G A S

©®

900

ERR FRU CMD

(('1'=Y),

R R AR

XFERSIZ
D D e e

1378

119

("0'=N)). ....... > @

Summary screen identifier.
Test number and mnemonic.
The time taken to complete the test.

The SCSI ID and the logic unit number of each device.
The number of read operations (decimal) performed on each device.
The number of write operations (decimal) performed on each device.
The error code (hexadecimal).
The field replaceable unit number.

The SCSI command (hexadecimal) that was executing at the time of failure.
The SCSI bus phase (hexadecimal) at the time of failure.
Error infermation code (see CPU Reference Information, Section 3.9.1).

The starting logical block-number of the data transfer that failed.
The size (in blocks) of the data transfer that failed.
A prompt for the next summary screen—Enter 1 to display the next
summary screen; enter 0 to display the console prompt.

KA47 Firmware

3-27

KAA47 Firmware

Figure 3-14 is an example of a summary screen for the COMM test that was .

performed during a system exerciser test.

Figure 3-14 Summary Screen for System Exerciser COMM Test

*xxxxxxxx* FST EXT ERRPT

[

COMM Test Summary

- M
Ja

12COMM

0 00:01:29 **xxaxxxxx

SCreen......................

; SR 7 SARERARRERAA

CH1 TX:00000030 RX:00000030 ERR:00000000
CH2 TX:00000030 RX:00000030 ERR: 00000000
CH3 TX:0000000C RX:0000000C ERR: 00000000
COMM Test Status Block

FRU: 0014
CSrR:

DAC4

FTY: 0006 @
STA:

0001

HWV:

0003

Swv:

CCOD

CCi: 0000
MOD: (001
CHN: 0002
PROT:. 0002
ABI: 0002
BPS: 5214

<ccz2: G000
CNT: 0002
SEL: 0003
SCM: FOCZ
ALO: 4000
SIzZ: 0008

EXP:

ACT:

0000

... ... ... ...........

0000

2332222221 SYSTST_NXT_SCF(

(¢

(('1'=Y),

("O0'=NY)Y.. ......

? 0

Summary screen identifier.
Test number and mnemonic.
The time taken to complete the test.

The number of the channel being tested as follows:

3-28

CH]1 corresponds to synchronous port 1.

CH2 corresponds to synchronous port 0.

CHa3 is not used.

The number of transmit operations performed on each channel.
The number of receive operations performed on each channel.
The number of errors detected on each channel.
The contents of relevant status registers.

KA47 Firmware

© A prompt for the next summary screen—Enter 1 to display the next
summary screen, enter O to display the console prompt.

Figure 3-15 is an example of 2 summary screen for the ASYNC test that was

performed during a system exerciser test.

Figure 3-15 Summary Screen for System Exerciser ASYNC Test

0 00:02:02 *xwexwraxs

14ASYNC

*axkaexxwx FST EXT ERRPT
ASYNC Test

Summary Screen.. ...................

ASYNC Test

P 1t 4y S

e D A T ma TS W

Status Block....

FRU: 0028

STA: 0000€)

CSR:
EXT:

0101
0000

LPR:
MOD:

FF18
0000

PRT:
BPS:

0000
0Q0F

EXP-

0000

ACT:

0000

e W U W TS O

e T

e P

e W5 WP O

... ... ...

VR S

e WP S

... ... ...

®0 000

SYT EXT STATUS - PRNT
NXT SCRN * @
Summary screen identifier.
Test number and mnemonic.
The time taken to complete the test.

The contents of relevant status registers.
A prompt indicating that the last summary screen is displayed. Press

Return to display the console prompt.

3.5.3 Additional Error Information for System Exerciser Tests
When the system exerciser test is complete, you can get more information
about the test using the following command:
>>>

SHOW ERROR

Figure 3-16 is an example of the information that this command displays.

KA47 Firmware

3-29

KA47 Firmware

Figure 3-16 Additional Error Information for System Exerciser Tests
e

22 130

SCsI

0018

000

NVR

0003

130 0Q0E 00000003 00120012 20180200 FFFFO01B 0000000C (1000000 FFFFFFFF®

One question mark (?) indicates a soft error, that is, an error that you do
not have to correct before you boot the system. Two question marks (?7)
indicate a hard error, that is, an error that you must correct before you
boot the system.

The FRU number of the device that fails.
The device number of the device that fails.
The device mnemonic of the device that fails.
An error code that corresponds to a specific device error.
A line of error information that 1s related to the test name (or test number
on the line immediately preceding it). In the example, the additional error
information line is related to the SCSI test (test 10). See CPU Reference
Information, Chapter 3, for information about the formats and meaning of

the additional error information for the various tests.

3-30

KA47 Firmware

DSLOEDE.0.0.8.0.0.08008.0.0.00.0.6.00.8.080.60.000.0.0.9
0960000
.900:96
0
P00 00008000000.0.8.0.5.60.0.0/6.0.060.010.0.0.00.0.0
8.:0.99:87
60004
9
BOS L0 E 0000008 880000000000.0000 0000000080000
000
PRES DS 00000000000.40.9.00.010.06.600.6
0.0 0898500
9.0:00
04
PRSI0 0809858680000 0600.00.6000600.0:0 998060000
DOEO G
0009800 88.000.008804909089000

XAXAAK KL KX KK KA XA KA AR KKK AR XA XK AKX LA KKK
D$.0.00.8.0.0.0.8.0.8.8.0.6.6.080.0.0:0.0,4°9.0.0.0:9:0
0409
.0.9
¢
DE0.9.0.8.0.08000480.00.0090966.6.960.90.0949081
19.9.0.9.6,0.8.8.0.0.00.090000.0004665.0006090¢04

b04,0.9,6.00.9
69 40000
0V 00000004
.0
F0.9,6,¢.6.0.0.4.0.8:0.0.0.4.0.6.6.0.0,610.0.0.0.¢9,
9.4
9

BP0 000
84.600048460.00000
0004
0

000606
60.806064¢460441
6

DS H 8500.0.400.6.0604.0000591
X
XAUXK XA
A
RAKKAKKX Y

9:8,6.6.0.4.4.0.¢.9.9.6.0,6.6.6.4.64
9.6.0.8.4.9.6.4.9.4:9.6.0.614.4

0,0.9.9.0.¢.9.4.6.9.¢.9.9,04
EXXKX
KXX
XARXXK

$.6:9.0.4.4.9.9.9.4.4

XAAANAAAX
)$:6.4.9.4.9.4

XXXXX
XXXXKXXX

XEXXXXAAX
19.0.4.4.6.9.4.9:¢.9.¢

EXXXXXXXXKXXXX
$,9.9.9.9.8.¢.4.9.¢.8.4.¢.4.64

19,08.8.8.4.06.40.64.064.44¢
1O.0:0.8.4.9.6.0.0.9.6:0.6.0.40.4
0.5 ¢

$06.00.66548¢66404684004.6]
D0900.64.0.9.4.60.69.0.600696001

DO0.98.0.86009.46066800.009.64
RO $ 0060080006 0.65540068¢404.04

PO 0,090,004 6000600505 90008990¢¢4
PSS D098085060
08 800069
600
069000
8
1
KUK

XK UK KK

AL AR AR AR KK

KAARX

P00 0
S
080000
06:0.0.00
080
9 990000
0890¢ 01
DE0.0.0.0.8.0.0.0.056.00 0400006560008 0.00049
00E0Y
YED00050.000.0.90.405060000.89.80.0:
04990
0:0:0.65
4
ROD00.0.9.9900.60.08069560050000
066068
9:00.
00000
60
RS2 2090.0.0.4.0.0,0.8,0.8.5.9.061000.9.09.6
09,9 909000
.0:0:9.0
01
.
0.218.9.8.0.0.9.0.0.0.0.,0.6:0:0.6:
0169009
9.8:0:6
0000.0:970:
00000009
00
RODOF G009080000
¢000 00000
50
00000
06
0000
e e

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

XXXXXXXXXXXXX

XXXXXXXXXXXXXXXXXXXXXxXXXXXXXXXXXXXX

XXXXXXXXXXXXXXX

4
Testing and Troubleshooting
This chapter describes how to troubleshoot a MicroVAX 3100 system that uses
the KA47 CPU module. It gives information on the following:
e

General troubleshooting information

No display on the console terminal

NVR test (test 1)

DZ test (test 3)

CACHE test (test 4)

MEM test (test 5)

FPU test (test 6)

IT test (test 7)

SYS test (test 8)

NI test (test 9)

SCSI test (test 1u,

COMM test (test 12)

ASYNC test (test 14)

Power supply troubleshooting procedures

4.1 General Troubleshooting Information
You perform troubleshooting procedures while the system is in console
mode, that is, while the operating system software is in a halt state. The
troubleshooting procedures are based on the diagnostic test irmware provided
with the system. When you turn on the system, it runs the power-up test and
initialization. This test runs the individual diagnostic tests that check the
various components in the system. Table 4-1 lists the diagnostic tests and the
FRUs on which each diagnostic test focuses.

Testing and Troubleshooting

4-1

Troubleshooting

The system runs the power-up test and initialization automatically when you
turn on the system. If the power-up and initialization test fails, follow these

steps:

Read the console terminal display or read the code on the LED display (see

CPU Reference Information, Chapter:6).

Note the test number and mnemonic of the failing device or use the LED
code that you read during step 1 to identify the test number and mnemonic
of the failing device (see Table 4-1).

See Table 4-1 for a reference to a section in this chapter that provides the
testing and troubleshooting information for the failing dewvice.

The testing and troubleshooting procedures that Table 4-1 references, describe
the procedures for isolating a fault to FRU level.
In general, it is recommended that you run the individual self-test (see
Section 3.3) on the failing device when the system is in the Digital Services
environment.

Note

You must connect a loopback connector (29-24795-00) to the

asynchronous modem control port 2 before you can put the system
in the Digital Services environment.

To put the system in the Digital Services environment, enter the following
command at the console prompt:
>>>

SET DIAGENV 2

CPU Reference Information, Section 1.11.3, lists all the test environments.
In the Digital Services environment, you must use loopback connectors,
terminators, or test media to run certain tests successfully The sections that

Table 4-1 references describe the requirements of each test.

For more comprehensive testing and to check the interaction of devices in

the system, you can run the system exerciser (see Section 3.5). The system
exerciser 1s also useful for troubleshooting intermittent errors in the system.

4-2

Testing and Troubleshooting

Troubleshooting

Table 4-1

Troubleshooting Procedures

Failing

Device

LED Dispiay

Most Suspect

Section

Test

Mnemonic

Indication

FRUs

Reference

NVR

0001 xxxx !

CPU module

4.3

0011 xxxx

CPU module

4.4

CACHE

0100 rxrx

CPU module

4.5

MEM

0101 xxxx

MS44 or MS441. memory option

4.6

CPU module

4.6

FPU

0110 xxxx

CPU module

4.7

0117 xxxx

CPU module

5Y8

1000 xxxx

CPU module

4.9

1001 xxxx

CPU moduie

4.10

SCsSI

1010 xxxx

RZ2* 2 disk drive

411

TZ30 tape drive

411

TZK10 tape drive

4.11

RX26 diskette drive

4.11

RRD42 CDROM drive

4.11

CPU module

4.11

DSW41 or DSW42 synchronous

4.12

COMM

1100 xxxex

communicat:ons option

ASYNC

1110 xxxx

CPU module

4.12

DHW41 or DHW42 asyn-

4.13

chronous communications option

CPU module

4.13

Ixxxt represents device-specific codes.

2This device can be RZ23L, R724, or RZ25.

4.2 No Display on the Console Terminal
Figure 4-1 shows the sequence of events that occurs when you turn on the

system. Follow the procedure in Section 4.2.1 if the console terminal does not

show any display.

Testing and Troubleshooting

4-3

Troubleshooting

Figure 4-1

Flowchart for Normal System Power-Up
Tum on the sysltem

v
The green LED on the front of the

system unit tumns on The LED display
on the back ot the system unit counts

down If not, see Secton 4 21

)
The power-up lest and initalization
display is shown on the console
terminal that is connected to the
system unit. Afler 2.5 minutes, the
display is complete {1 not, see
Section 421

!
If no fatal errors are detected dunng
the power-up test and mnitialization

and the defauit recovery action flag

s setto 1 or 2. the sysilem displays
the boot device

the default
recovery action
37

The sysiem automatically boots from the
delault boot device or from the Ethemet
if the detault boo! device s null

The system halts automatcally

——

Press the halt push button on the back

of the systermn unit to retum the syStem
to the console mode for testing purposes

4.2.1

Troubleshooting Procedure
Follow these steps to locate the failing FRU:

Ensure that the terminal is properly connected to the system unit. Make
sure that the terminal is on. The LED indicator on the terminal turns on
when the terminal is turned on. Check the terminal setup. The correct
setup values for the terminal are as follows:
e

4-4

DEC423 operation

Testing and Troubleshooting

Troubleshooting

Transmit = Receive = 9600 baud

Eight bits

One stop bit

No panty

If you do not know how te change the terminal setup, see the terminal
documentation. Turn the brightness control until the raster scan is shown
on the terminal display. When the terminal does not display a raster scan,
see the terminal troubleshooting documentation.
Turn off the system unit. Check the position of the break/enable switch on
the back of the system unit. The switch must be set to the down position
before you turn on the system if you want to use the terminal that is
connected to MMJ port 0 as the console device. Ensure that the switch
15 in the up position before you turn on the system if you want to use the
terminal connected to MMJ port 3 as the console device. Confirm that the
terminal does not produce a display when it is connected to either port.
Note

The system reads the position of the break/enable switch only when
you turn on the system.

Turn on the system unit. Check that the green LED on the front of the
system unit is on and that you can hear the sound of the fans operating. If
this does not occur, follow the procedure in Section 4.14.
Turn off the system unit, and remove the upper and lower dnve-mounting

shelf combination. See the BA42-B Enclosure Maintenance manual for
more information.

Remove the logic boards of the asynchronous communications options
(DHW41 or DHW42) and the synchronous communications options (DSW41
or DSW42) from the CPU module (if connected).
Remove the MS44 or MS44L. memory modules from connectors 2H, 2L and
3H, 3L on CPU module (if connected). Do not remove the memory modules
from the connectors 1H, 1L. This is the basic system memory. The system
cannot operate without this memory.

Testing and Troubleshooting

4-5

Troubleshooting

7. Turn on the system. If the terminal produces a display, one of the

components that you disconnected is causing the problem. Install the
components, one at a time in the order you removed them, and test
the system each time. If the terminal does not produce a display, the
component that you installed last is the cause of the problem.

If the terminal does not produce a display, turn off the system unit, replace

the CPU module, and go to step 8.

Turn on the system unit. When the terminal produces a display,
reassemble the system unit.

4.3 NVR Test (Test 1)
The NVR test checks the nonvolatile RAM (NVR) and the time-of-year
(TOY) clock on the CPU module. This test runs automatically, as part of the
power-up test and initialization, when you turn on the system. This NVR test
performs the following subtests:
e

NVR subtest—This subtest checks the NVR for valid data. When the NVR
is not initialized, this subtest checks all NVR locations and initializes the
NVR. When the NVR is initiahzed, this test checks the temporary NVR
locations only.

¢ TOY subtest——This subtest checks that the TOY clock contains a valid time .
entry. If not, this subtest checks all TOY registers by writing and reading
values to the TOY registers.

If the test fails during a power-up test ind initialization, put the system in the
Digital Services environment (see CPU Reference Information, Section 1.11.3),
and run the NVR test as an individual self-test. To run the NVR test as an
individual self-test, enter one of the following commands at the console prompt:
>>> T

>>> T NVR

If the NVR test fails, the LED display on the back of the system unit
displays an error code in the range 10 to 11(hexadecimal) (see CPU Reference
Information, Table 6-2), and the console terminal displays a hard error code as
follows:
7?2 001

1 NVR 0004

The error code, 0004(decimal) in this example, indicates a battery fault.

CPU Reference Information, Table 3-1, describes the error codes that the NVR
test produces. If this test fails, you must replace the CPU module.

4-6

Testing and Troubleshooting

Troubleshooting

. 4.4 DZ Test (Test 3)
The DZ test checks the asynchronous MMJ ports 0,1, and 3 and the modem
control port (2) on the CPU module. This test runs automatically, as part of
the power-up test and initialization, when you turn on the system. This test
performs the following subtests:

Reset subtest—This subtest resets the DZ chip and sets the communication
parameters of the serial lines to their default values. When the device does
not reset or the communication parameters of the serial lines cannot be set
correctly, this subtest generates an error.

Polled subtest—This subtest configures the DZ chip in polled mode and
checks each serial line in internal loopback mode.

Interrupt subtest—This subtest configures the DZ chip in interrupt mode

and checks each serial line in internal loopback mode. Interrupts are
enabled and characters are transmitted on all serial lines excluding
the serial line that the console device uses. The subtest compares the
characters returned with the characters transmitted. It signals an error if
the characters are not equal.

If the DZ test fails during the power-up test and initialization, put the system
in the Digital Services environment (see CPU Reference Information, Section
1.11.3), and run the DZ test as an individual self-test.
Note

In the Digital Services environment, you must connect the H3103

loopback connectors to MMJ ports 0,1, and 3, excluding the port to
which the console terminal connects. You must also connect a loopback
connector (29-24795-00) to the asynchronous modem control port (2).

The test fails if you do not install the loopback connectors.

To run the DZ test as an individual self-test, enter one of the following
commands at the console prompt:
>>> T

>>> T D2

If the DZ test fails, the LED display on the back of the system unit displays an
error code in the range 30 to 34(hexadecimal} (see CPU Reference Information,
Table 6-3), and the console terminal displays a hard error code as follows:
27 001 2 Dz 0064

Testing and Troubleshooting

4-7

Troubleshooting

The error code, 0064(decimal) in this example, indicates that the polled test

failed. CPU Reference Information, Table 3-2, describes the error codes that
the DZ test produces. To get additional information about the error, enter the

command:
>>>

SHOW ERROR

CPU Reference Information, Section 3.2.1, gives the formats and describes the
additional error information that the DZ test produces. The additional error
information indicates which serial line is faulty.

To troubleshoot intermittent failures, you can run the system exerciser (see
Section 3.5). CPU Reference Information, Section 5.1, gives the errer messages
that the system exerciser produces for this test. If this test fails repeatedly,
you must replace the CPU module.

4.5 CACHE Test (Test 4)
The CACHE test checks the cache memory on the CPU module. This test runs
automatically, as part of the power-up test and initialization, when you turn on
the system. This test performs the following s+btests:
e

Data store subtest—This subtest checks the data store of the pnmary
cache memory. The subtest includes read, compare, complement, and write

operations in the forward and reverse direction. The subtest accesses the
data store through the /O address space.

Tag store subtest—This subtest checks the tag store of the primary cache

memory. The subtest includes read, compare, complement, and write
operations in both the forward and reverse direction. The subtest accesses
the tag store through the /O address space.
If the CACHE test fails during the power-up test and initialization, put the
system in the Digital Services environment (see CPU Reference Information,

Section 1.11.3) and run the test as an individual self-test.
To run the CACHE test as an individual self-test, enter one of the following
commands at the console prompt:
>>> T 4
>>> T

CACHE

If the CACHE test fails, the LED display on the back of the system unit

displays an error code in the range 41 to 4C(hexadecimal) (see CPU Reference
Information, Table 6—4), and the console terminal displays a hard error code as
follows:
27 001 4 CACHE 0512

4-8

Testing and Troubleshooting

Troubleshooting

The error code, 0512(decimal) in this example, indicates that the test failed
on a read/write operation to the data store. CPU Reference Information, Table
3—4 describes the error codes that the CACHE test produces. To get more
information about the error, enter the command:
>>> SHOW ERROR

CPU Reference Information, Section 3.3.1, gives the formats and describes the
additional error information that the CACHE test produces. If this test fails,
you must replace the CPU module.

4.6 MEM Test (Test 5)
The MEM test checks the system memory, that is, the memory on the system
module and the MS44 or MS44L, memory options. This test runs automatically,
as part of the power-up test and initialization, when you turn on the system.
This test performs the following subtests:
*

Byte mask subtest—This subtest checks the byte mask signals that the
CPU generates. The subtest operates on each page boundary. When

the subtest 1s complete, all free memery locations contain the number
AA(hexadecimal).
*

Forward pass memory subtest—This subtest includes read, compare,

complement, and write operations to all memory locations in the forward
direction.
*

Reverse pass memory subtest—This subtest includes read, compare,

complement, and write operations to all memory locations in the reverse

direction.
*

Final parity subtest—This subtest fills all the memory locations with the

pattern O01h. The subtest then reads the contents of each location and
checks that the parity bit is set. If the parity bit of any location is not set,
the subtest generates an error. The unused memory locations are set to the
pattern 01010101h.
If the MEM test fails during the power-up test and initialization, put the
system in the Digital Services environment (see CPU Reference Information,

Section 1.11.3), and run the MEM test as an individual self-test. To run the
MEM test as an individual self-test, enter one of the following commands at
the console prompt.
>»
T>
§
>>>

T MEM

Testing and Troubleshooting

4~9

Troubleshooting

If the MEM test fails, the LED display on the back of the system unit

displays an error code in the range 50 to 54(hexadecimal) (see CPU Reference

Information, Table 6-5), and the console terminal displays a hard error code as
follows:
7% 001 5 MEM 0770

The error code, 0770(decimal) in this example, indicates that the test failed
a comparison check while performing the reverse pass memory test. CPU
Reference Information, Table 3-5, describes the error codes that the MEM test
produces. To get more information about the error, enter the command:
>>>

SHOW ERROR

CPU Reference Information, Section 3.4.1, gives the formats and describes the
additional error information that the MEM test produces. The additional error
information gives an FRU number that identifies which memory module is
faulty.

4.7 FPU Test (Test 6)
The FPU test checks the floating-point unit (FPU) on the CPU module. This
test runs automatically, as part of the power-up test and initialization, when
you turn on the system. The FPU test performs instruction tests on the FPU.

If an instruction produces unexpected results or an exception occurs during

the execution of an instruction, this test generates an error. If the FPU test
fails during the power-up test and initialization, put the system in the Digital
Services environment (see CPU Reference Information, Section 1.11.3) and run
the FPU test as an individual self-test. To run the FPU test as an individual
self-test, enter one of the following commands at the console prompt:
>»> T

>>>

FPU

If the FPU test fails, the LED display on the back of the system unit displays
the error code 60(hexadecimal), and the console terminal displays a hard error
code as follows:
2% Gl 6 FpPU 0258

The error code, 0258(decimal) in this example, indicates that the test failed
during the MOVF instruction. CPU Reference Information, Table 3-7, describes
the error codes that the FPU test produces. To get more information about the

error, enter the command:
>>>

4-10

SHOW ERROR

Testing and Troubleshooting

Troubleshooting

CPU Reference Information, Section 3.5.1, gives the format and descripuion of
the additional errcr information that the FPU test produces. If the FPU test
fails, replace the CPU module.

4.8 IT Test (Test 7)
The IT test checks the interval timer (IT) on the CPU module. This test runs
automatically, as part of the power-up test and initialization, when you turn
on the system. The IT test enables interval timer interrupts. If there are
too many or too few interrupts within a 30 millisecond (ms) interval, the test
generates an €rror.

If the IT test fails during the power-up test and initialization, put the system
in the Digital Services environment (see CPU Reference Information, Section
1.11.3) and run the IT test as an individual self-test. To run the IT test as an
individual self-test, enter one of the foliowing commands at the console prompt:
T 17
>>>
>>> T

If the IT test fails, the LED display on the back of the system unit displays the
error code 70(hexadecimal) and the console terminal dispiays a hard error code
as follows:

22 001 7 FPU 0002

The error code, 0002(decimal) in this example, indicates that the test failed

because the IT is not interrupting at the correct rate. CPU Reference
Information, Table 3-7, describes the error code that the IT test produces.
Additional error information is not available for this test. If the IT test fails,
replace the CPU module.

4.9 SYS Test (Test 8)
The SYS test checks the system ROMs and the invalidate filter RAM on the
CPU module. This test runs automatically, as part of the power-up test and
initialization, when you turn on the system. This test performs two subtests as

follows:

System ROM subtest—This subtest checks each byte of the system ROMs
to ensure that they contain the correct Manufacturing check data and the
correct checksum.

Filter RAM subtest—This subtest performs two passes on the invalidate
filter RAMs. The subtest detects address locations that cannot be changed

and data faults.

Testing and Troubleshooting

4-~11

Troubleshooting

If the SYS test fails during the power-up test and initialization, put the system
in the Digital Services environment (see CPU Reference Information, Section
1.11.3) and run the SYS test as an individual self-test. To run the SYS test
as an individual self-test, enter one of the following commands at the console
prompt:
>>> T 8
>>>

§5YS

If the SYS test fails, the LED display on the back of the system unit displays
an error code in the range 80 to 82(hexadecimal) (see CPU Reference
Information, Table 6-6), and the console terminal displays a hard error
code as follows:
27 001 & SYS 0128

The error code, 0128(decimal) in this example, indicates that the test failed
the invalidate filter RAM subtest. CPU Reference Information, Table 3-10,
describes the error code that the SYS test produces. To get more information
about the error, enter the command>>>

SHOW ERROK

CPU Reference Information, Section 3.7.1, gives the format and describes the
additional error information that the SYS test produces. If the SYS test fails,
replace the CPU module.

4.10 NI Test (Test 9)
The NI test checks the network interconnection circuitry on the system module.
This test runs automatically, as part of the power-up test and initialization,

when you turn on the system. This test performs nine subtests as follows:
*

Network address ROM subtest—This subtest checks the 32-byte network

address ROM, which contains the unique 6-byte network address, a 2byte checksum, and the test data type. The subtest checks for a null or
multicast address, calculates and compares the checksums, and verifies the

test data bytes.
¢

LANCE register subtest—This subtest checks the address and data paths
to the LANCE register address port (RAP) and the register data port

(RDP) for each of the four control status registers (CSRs).
¢

LANCE initialization subtest—This subtest sets up the LANCE data
structures and initializes the LANCE chip, which causes the LANCE
circuit to perform a single word DMA read operation on the system
memory.

4-12

Testing and Troubleshooting

Troubleshooting

LANCE internal looptack subtest—This subtest verifies the correct
operation of the LANCE transmit and receive circuitry in internal loopback
mode. The subtest also verifies burst-mode DMA read and DMA write
operations on non-word-aligned data buffers for data packets of varying
length and different data patterns.

LANCE interrupt subtest—This subtest enables, forces, and services
the LANCE interrupts for initialization, transmission, and reception in
internal loopback mode.

LANCE CRC subtest—This subtest checks the LANCE character
recognition code (CRC) generation during data transmission. The
subtest also performs incorrect CRC detection during data reception in
internal loopback mode.

LANCE receive MISS/BUFF subtest—This subtest checks the LANCE
circuits for any missed data packets and buffer errors during a data
reception in internal loopback mode.
LANCE collision subtest—This subtest verifies a collision detection and
retry activity during a data transmission in the internal loopback mode.

LANCE address filtering subtest—This subtest checks the LANCE receiver

address filtering for the broadcast, promiscuous, and null destinations in
the internal loopback mode.
If the NI test fails during the powe:-up test and initialization, put the system

in the Digital Services environment (see CPU Reference Information, Section
1.11.3; and run the NI test as an individual self-test.
Note

When the network select switch is set for a ThinWire Ethernet

operation, the NI test gencrates an error if you do not connect the

system to a ThinWire Ethernet network or install the ThinWire
Ethernet T-connector and terminators.
2.

When the network select switch is set for a standard Ethernet

operation, the NI test generates an error if you do not connect the
system to a standard network or install the standard Ethernet
loopback (12-22196-01).

Testing and Troubleshooting

4-13

Troubleshooting

To run the NI test as an individual self-test, enter one of the following
commands at the console prompt:
>»>» T 9
>>>

T NI

If the NI test fails, the LED display on the back of the system unit displays an
error code in the range 90 to 9B(hexadecimal) (see CPU Reference Information,
Table 6-7), and the console terminal displays a hard error code as follows:
?? 001 9 NI 0166

The error code, 0166(decimal) in this example, indicates that the test produced
a packet comparison failure in the external loopback mode. CPU Reference
Information, Table 3-11, describes the error codes that the NI test produces.
To get more information about the error, enter the command:
>>> SHOW ERROR

CPU Reference Information, Section 3.8.1, gives the format and describes
the additional error information that the NI test produces. If the NI test
fails and the system is connected to a network, disconnect the system from
the network, and connect either the ThinWire Ethernet terminators or the

standard loopback connector depending on the type of network to which the
system connects.

Run the NI test again. If the system passes the NI test, something in the
network is causing the problem; contact the network co-ordinator. If the

system fails the NI test, replace the CPU module.
To troubleshoot intermittent failures, you can run the system exerciser (see
Section 3.5). The system exerciser runs this test when testing the interaction
of components in the system. CPU Reference Information, Section 5.2, gives
the error messages that the system exerciser produces for this test. If this test
fails repeatedly, replace the CPU module.

4.11 SCSI Test (Test 10)
The SCSI test checks the SCSI controller on the CPU module and its interface
with all the SCSI devices on the SCSI bus. This test runs automatically as
part of the power-up test and initialization when you turn on the system. The
SCSI test performs three subtests as follows:
*

are fully operational.

4~-14

Testing and Troubleshooting

Troubleshooting

Interrupt subtest—This subtest checks the SCSI bits in the interrupt mask

register, the interrupt request register, and the interrupt clear register.
The subtest forces a SCSI interrupt when the SCSI bit in the interrupt
mask is set to 1, then set to 0. The subtest repeats this operation for both
high-priority interrupts and low-priority interrupts.

Data transfer subtest—This subtest verifies the SCSI bus communication
between the SCSI controller and SCSI devices on the SCSI bus. It also
checks the data path between the SCSI controller, the system chip (S-chip),
and memory. The subtest issues four inquiry commands to each SCSI
device in four different modes as follows:

Programmed input/output mode

Asynchronous mode with DMA

—

Asynchronous mode with DMA, starting on a nonword-aligned
boundary and crossing a page boundary

Synchronous mode with DMA

If the test fails during the power-up test and initialization, put the system
in the Digital Services environment (see CPU Referenice Information, Section

1.11.3), and run the SCSI test as an individual self-test.

To run the SCSI test as an individual self-test, enter one of the following
commands at the console prompt:
>>> T 10
>>> T SCSI

If the SCSI test fails, the LED display on the back of the system unit

displays an error code in the range A0 to Ab(hexadecimal) (see CPU Reference
Information, Table 6-8), and the console terminal displays a hard error code as
follows:
27 150 10 SCsI

0050

The error code, 0050(decimal) in this example, indicates that the SCSI minimal
device test failed. CPU Reference Information, Table 3-12, describes the error
codes that the SCSI test produces. To get more information about the error,

enter the command:
>>>

SHOW ERROR

CPU Reference Information, Section 3.9.1, gives the format and describes the
additional error information that the SCSI test produces. If the SCSI test fails,
the problem may be the CPU module or one of the SCSI devices connected to
the SCSI bus.

Testing and Troubleshooting

4-15

Troubleshooting

In the Digital Services environment, you must install test media in the

removable media devices.

Enter the command SHOW DEVICE (see CPU Reference Information, Section
1.12.4) or SHOW CONFIG (see CPU Reference Information, Section 1.12.3) to
check that the SCSI controller on the CPU module acknowledges all the SCSI
devices on the SCSI bus. If the display does not show all the SCSI devices in
the system, check the following:
*

Each SCSI device has a unique SCSI ID. See Table 2-3 for the
recommended SCSI ID numbers for devices.

The internal power cable and the internal SCSI cable are correctly
connected to each internal SCSI device.

The power cable and the SCSI cable are correctly connected to each
external SCSI device.

When you are sure that all the SCSI devices have unique SCSI IDs and that
the cables are connected correctly, run the SCSI test again. When the SCSI

controller acknowledges all the SCSI devices on the SCSI bus, but the fault
persists, disconnect any external SCSI devices from the system unit, and
connect the SCSI terminator to the SCSI port.

Run the SCSI test again. When the test passes, the fault is in one of the
external devices connected to the system unit or the last SCSI device on the
SCSI bus is not terminated correctly.

Run the SCSI test. If the test fails, replace the CPU module. When the test
passes, reconnect the internal SCSI cable to the CPU module.
Run the SCSI test again. If the test passes, the internal SCSI cable er the
connection to the CPU module is faulty. I{ the test fails, enter the command
SHOW ERROR (see CPU Reference Information, Section 1.12.6) to get more
information about the SCSI error. CPU Reference Information, Section 3.9.1,
gives the format and description of the additional error information that the
SCSI test produces. The additional error information gives you the SCSI
ID of the failing SCSI device. The SCSI ID also indicates the type of failing
SCSI device. Table 4-2 lists the subsections in this chapter that describe the
troubleshooting procedures for each type of SCSI device.

4-16

Testing and Troubleshooting

Troubleshooting

Table 4-2 SCSI Device Troubleshooting Procedures

SCSI Device Type

Section

RRD42 CDROM drive

4.11.1

RX26 diskette drive

4.11.2

RZ23L, RZ24, RZ25 disk drives

4.11.3

TZ30 tape drive

4.114

TZK10 tape drive

4.11.5

External SCSI devices

4.11.6

To perform a more comprehensive test on the SCSI devices, put the system in
the Digital Services environment (see Section 3.3.2.2), and enter the following
command:
>>> T 106

The system prompts you for the devices you want to test (see Section 3.5.1).
Select the SCSI device you want to test. If the test is successful, the display
shows the following:
10 sCs1 ¢

If the test is not successful, the display shows the following:
77 10

SCSI

150

0160

B8:18:41

The error code, 0160(decimal) in this example, indicates a device test failure.
CPU Reference Information, Table 5-4, describes the error codes that the
system exerciser produces for the SCSI test.

The system exerciser generates a summary screen. When the test completes,
press Return to display the summary screen. Section 3.5.2 gives examples
of the summary screens that the system exerciser generates. The system
exerciser summary screen shows which SCSI device is faulty. Replace the
faulty SCSI device.

4.11.1

Troubleshooting an RRD42 CDROM Drive
The RRD42 CDROM drive is a single FRU. When the SCSI test (test 10)
isolates the fault to an RRD42 CDROM drive, you must replace the RRD42
CDROM drive (RRD42-AA). See the BA42-B Enclosure Maintenance manual
for information about removing and replacing FRUs.

Testing and Troubleshooting

4~17

Troubleshooting

4.11.2 Troubleshooting an RX26 Diskette Drive

When the SCSI test (test 10) isolates the fault to an RX26 diskette drive, you
must identify the faulty FRU. The RX26 diskette drive contains three FRUs:
1.

SCSI/FDI board (54-20764-02)

RX26 diskette drive unit (RX26-AA)

RX26 ribbon cable (17-00285-00)

To identify the faulty FRU, replace each FRU in turn, in the order shown
previously, and run the SCSI test (test 10) again until the test passes. See the

BA42-B Enclosure Mainienance manual for information about removing and
replacing FRUs. The last FRU that you replace is the faulty FRU.

4.11.3 Troubleshooting an RZ23L, an RZ24, or an RZ25 Disk Drive
The RZ23L, RZ24, and RZ25 disk drives are single FRUs. When the SCSI test
(test 10) isolates the fault to an RZ23L, an RZ24, or an RZ25 disk drive, you
must replace the disk drive. See the BA42-B Enclosure Maintenance manual
for information about removing and replacing FRUs.

4.11.4 Troubleshooting a

TZ30 Tape Drive

When the SCSI test (test 10) isolates the fault to a TZ30 tape drive, you must
identify the faulty FRU. The TZ30 tape drive contains two FRUs:
e

Take-up leader (74-34273-01)

TZ30 tape drive unit (TZ30-AX)

To identify the faulty FRU, inspect the take-up leader for damage. If necessary,
replace the take-up leader according to the instructions in the TZ30 Cartridge
Tape Drive Service manual (EK-OTZ30-SV). If the take-up leader is not
damaged or incorrectly aligned, replace the TZ30 tape drive. See the BA42-B
Enclosure Maintenance manual for information about removing and replacing
the FRUs.

4.11.5 Troubleshooting a TZK10 Tape Drive
The TZK10 tape drive is a single FRU. When the SCSI test (test 10) isolates
the fault to a TZK10 tape drive, you must replace the TZK10 tape drive
(TZK10-AA). See the BA42-B Enclosure Maintenance manual for information
about removing and replacing the FRUs.

4-18 Testing and Troubleshooting

Troubleshooting

. 4.11.6 Troubleshooting an External SCSI Device
When the SCSI test (test 10) isolates the fault to an external SCSI device,
replace the external SCSI device according to the maintenance information for
that device.

4.12 COMM Test (Test 12)
The COMM test checks the operation of the synchronous communications
option (DSW41 or DSW42) in the system. This test runs automatically, as part
of the power-up test and initialization, when you turn on the system. This test
performs eight subtests as follows:
¢

Subtest 1—This subtest verifys the checksum of the 128K-byte read-only
memory (ROM).

Subtest 2—This subtest checks the 256K-byte static RAM. The operations

performed include write, verify, complement, verify.
¢

Subtest 3—This subtest performs a self-test on the MC68302 processor.

Subtest 4-—This subtest checks the RAM dual access.

Subtest 5—This subtest checks the electrically programmable read-only
memory (EPROM) dual access.

Subtest 6—This subtest checks that the synchronous communications
option can interrupt the system CPU.

Subtest 7—This subtest checks the host buffer loopback and interrupt.
The test transfers data from the CPU to the synchronous communications
option, returns it, and waits for an interrupt.

Subtest 8—This subtest resets the synchronous communications option and
waits for an interrupt.

If the COMM test fails during the power-up test and initialization, follow these
steps:

1.
2.

Disconnect all the external cables from the synchronous communications
ports on the back of the system unit.
Put the system in the Digital Services environment (see CPU Reference
Information, Section 1.11.3).

Testing and Troubleshooting

4-19

Troubleshooting

3. Run the COMM test as an individual self-test.

Note

In the Digital Services environment, you must connect one H3199
loopback (DSW41) or two H3199 loopback connectors (DSW42) to the
synchronous communications ports on the back of the system unit. The
test fails on ports that do not have loopback connectors fitted.
To run the COMM test as an individual self-test, enter one of the following
commands at the console prompt.:
>>> T 12
>>> T COMM

If the COMM test fails, the LED display on the back of the system unit
displays an error code in the range C0 to C8(hexadecimal) (see CPU Referen.e
Information, Table 6-9), and the console terminal displays a hard error code as
follows:
27 020 12 COMM 0274

communications option diagnostic test did not complete. CPU Reference

The error code, 0274(decimal) in this example, indicates that the synchronous
Information, Table 3-15, describes the error codes that the COMM test
produces. To get more information about the error, enter the command:
>>> SHOW ERROR

CPU Reference Information, Section 3.10.2, gives the format and describes
the additional error information that the COMM test produces. The system
exerciser runs this test when testing the interaction of components in the
system. CPU Reference Information, Section 5.4, gives the error messages that
the system exerciser produces for this test. See Section 4.12.1 to identify the
faulty FRU.

4.12.1 Troubleshooting a DSW41 or a DSW42 Synchronous
Communications Option
The DSW41 and DSW42 synchronous communications options contain the
following FRUs:

4-20

Input/output module

Logic board

Ribbon cable

Testing and Troubleshooting

Troubleshooting

External cables

To identify the faulty FRU, run the COMM test (test 12) repeatedly as an
individual self-test, replacing the FRUs, one at a time in the order shown
previously, until you find the faulty FRU.
To check the external cables, you can connect cable loopback connectors and
run the test again. The external cable loopback connectors that you must
connect depend on the communications interface you are using. Figure 4-2
shows the loopback connectors for the different communications interfaces that
the DSW41 and DSW42 synchronous communications options support.
Figure 4-2 Cable Loopback Connectors for the DSW41 and DSW42 Options

System Unit

Systern Loopback
H3199

Synchronous
Communications

Part 0

[]

Cabie Loopback

l__]

H3248 for EIA-232/V
24

External Cable

17-01110-01 for EIA-232/V
24
17-01111-01 for EIA-423/V
.10
17-01108-01 for EIA-422/V
11

H3198 for EIA-423/V
10

H3198 for EIA-422/V.11

Note: You mus! also conneci ioopback connectors to
synchronous cormmurications port 1.

4.13 ASYNC Test (Test 14)
The ASYNC test checks the operation of the asynchronous communications
option (DHW41 or DHW42) in the system. This test runs automatically, as
part of the power-up test and initialization, when you turn on the system. If

the ASYNC test fails during the power-up test and initialization, follow these
steps:

Disconnect all the external cables from the asynchrenous communications

ports, which the option provides on the back of the system unit.
2.

Put the system in the Digital Services environment (see CPU Reference
Information, Section 1.11.3).

Testing and Troubleshoating

4-21

Troubleshooting

3. Run the ASYNC test as an individual self-test.

Note

In the Digital Services environment, you must connect loopback
connectors to the asynchronous ports on the back of the system unit as
follows:

If a system has one eight-channel data only port, connect a H3101
loopback connector.

If a system has two eight-channel data only ports, connect two
H3101 loopback connectors.

If 3 system has one four-channel modem control port, connect a
H4081-A loopback connector.

If a system has two four-channel modem control ports, connect two
H4081-A loopback connectors.

To run the ASYNC test as an individual self-test, enter one of the following
commands at the console prompt:

>>> T 14
>>> T ASYRC

If the ASYNC test fails, the LED display on the back of the system unit
displays an error code in the range E0O to EE(hexadecimal) (see CPU Reference
Information, Table 6-10), and the console terminal displays a hard error code
as follows:
??

021 14 ASYNC 1280

The error code, 1280(decimal) in this example, indicates that the asynchronous
communications option failed the receiver interrupt test. CPU Reference
Information, Table 3-17, describes the error codes that the ASYNC test

produces. To get more information about the error, enter the command:
>>> SHOW ERROR

CPU Reference Information, Section 3.11.1, gives the formats and describes
the additional error information that the ASYNC test produces. If the ASYNC
test fails, enter the SHOW ERROR command to get more information about
the error. The additional error information indicates which asynchronous
communications channel is faully. See Section 4.13.1 to identify the faulty

FRU.

4-22

Testing and Troubleshooting

Troubleshooting

The system exerciser (see Section 3.5) runs this test when testing the
interaction of components in the system. CPU Reference Information, Section
5.5, gives the error messages that the system exerciser produces for this test.

Troubleshooting a DHW41 or a DHW42 Asynchronous
Communications Option
The DHW41 and DHW42 asynchronous communications options contain the
following FRUs:
L

4.13.1

Input/output module

Harmonicas (DHW42-AA, DHW42-BA only)

Logic board

Ribbon cable
External cables

To isolate the faulty FRU, run the ASYNC test (test 14) repeatedly as an
individual self-test, replacing the FRUs, one at a time in the order shown
previously, until you find the faulty FRU.

To check the external cables, you can connect cable loopback connectors and
run the test again. The external cable loopback connectors that you must

connect depend on the communication type (data only ¢r modem control)
that you are using. Figure 4-3 shows the loopback connectors for the
different communication types that the DHW41 and DHWA42 asynchronous
communications options support. Use Digital Services procedures to
troubleshoot the operation of the harmonicas or the 4-way modem cables.

Testing and Troubleshooting

4-23

Troubleshooting

Figure 4-3 Cable Loopback Connectors for DHW41 and DHW42 Options

System Unit

System Loopback
H3101 for eight-data only port

Asynchronous
Gomr;mr\‘x:uom
°

—
]
]

H4081-A for four-modem contral port

External Cabie

)

H3104 Harmonica
Use Digital Services procedures 10
troubleshoot external cables

Cable Loopback

17-01174-01 for eight-data only port
a

H3101

—
beed

Extemal Cable

17-02941-C1 for four-modem controf port

|| Use Digital Services procedui
s to
~

roubleshootl extemal cables

—

Note: You must also connect extenai cables and loopback

connectors 1o asynchronous communications port B

4.14 Troubleshooting Procedures for the Power Supply
Figure 4-4 is a flowchart for troubleshooting the power supply in a KA47
system.

4-24

Testing and Troubleshooting

;

Traubleshooting

Figure 4-4 Flowchart for Troubleshooting the Power Supply

Is power

Call an electncian.

present at

outiet?

Plug in power cord.

Set the power on/oft
swilch toon

Is the green

LED on the front
of the system unit
on and can you hear
the intemal fans
operating?,

Check the voltages shown in
Figure 4-6 and 4-7.

voliages within

5% Wierance?

Figure 4-5 shows the voltages on the pins of the power connector (see
Figure 1-3), which is next to the ThinWire Ethernet connector on the KA47
CPU module. See the BA42-B Enclosure Maintenance manual for more
information on power distribution.

Testing and Troubleshooting

4-25

Troubleshooting

Figure 4-5 KA47 CPU Module Power Connector Pin Voltages
Ground

-9.0 V de Retum

+51Vdc

+51Vdec

\+51 Vde /

Ground

/ .~ Ground

2] 1

~90vm/fifif[§]@9\-1zwm
Ground

+35Vdcto

Ground

+525Vdc

+12.1Vdc

+51Vde

Note: The -9.0 V dec supply is an tsolaled supply.

Figure 4-6 shows the voltages on the pins of the connectors on the power

cables that provide power to the internal mass storage device. See the BA42-B
Enclosure Maintenance manual for more information on power distribution.
Figu.e 4-6

Drive Power Connector Pin Voltages

+5.1 V dc (Red Cable)

Ground (Black Cable)
Ground (Black Cable)
+12 1 V dc (Orange Cabie)

4-26

Testing and Troubleshooting

PO000 806888080808000840.0000000088600806066.000:6060044
P

800008080040008000
000060000800
006008
080890009.04

§ 000066800080 088804 008080886060 00800.000008096.0
P00 0040080900808 008¢6080000.009 0084490000609

p00000000
BURIEESIEI 00000880060 009000¢0.00 060
BRSO EI IO
DO

EDN VO00080009$0050888¢0.¢:84

000000800408
00008 006606680034
080

f0.0.0.9.6.0.0.8.0.0.0840.0.0¢04.0.0.8.¢.6.044.0860.04669.44
[8.0.0.0,08.0.0.60.6.04$:¢.06440.000.696.0¢0.¢0.66.09

§$.0.8.0.00.6009.6949699400¢905800.96004
)00,6.0.96.00.60800.08¢80090048
484484
Je 0600080000808 885800086840.40

JO009.038.¢006.06000.0.00000804004
XXX KAXAX
XA
A XAXK
KKK
KK

P000080.00.00.80¢80000¢04904
D00045.06000969.064¢8464

XAXA XA XK XX KK AKKX AKX
$.9.8.0.0.0.8.0.00.9.¢6.¢0.949

1.8.0.4.9.6.0.5.6.04,8.¢641

XXXXXXAXXXKKX
$.0.6.8.6.0.6.0.9.4.¢4

XAKANKX
XXXXXKX
XXXXX

XXX
X

X
XXX
XXXXX

AXXXXAX
$9.4.4.8.4.4.9.¢.4

EXXXAKXXXXK
XAXKXXKXKAXKKK
XXXAXXXXKKKLAAK

$60.6.0.4.646699¢0.664
f8.6.9.9.0.0.0.8.6.0.9.6.¢.6.0.9.6.41

XX KUK LKA XX AR ALK AKXAAAK
$4.09.0.6.9.90:80.6846.¢.0¢00¢444

P800 09048006 6846460009604
P006.64.0666680.60600806046084

PO 80890094960 03.6.40608.¢0490¢.041

P00 0040.0,0.0.8.0.000.0.046064.060686909
[9.8,6.0.0.08944.0.60000.08.6800090666666¢]

FH OSSO0 00 08044446600 00808088008089041
Q000006 6000600900088 8.6660000¢6606¢4¢

PH.0.0.0:0.0.6.80606600.000080008.840.6690.90:40984
¢4
.0.0.9.6.0.0/6006.89.5.009.890.0000083.0096060.900040801
0.0.0.9.0.0.
5600000
0.0.0.
00088.00.908
09.8.0
9.006906.009
.6.00
4
F0,9.0.9.0.0.0.80.0.00.64.0.68 9668404000990 0000.69.00.8 0000

D93V90.0.0.0.008088400008030068800000.0.096090001
0.00.00
2GS000088
886800030
800
00 000840
098
0400009606600
0

DO.68.0.,9,08.0.0.6.9.6.00:6.900.0.0.0.0.6.0.0.0.900.6:0.00.0.0:6.¢9.9
660000001
.0¢

A
Troubleshooting Flowchart
This appendix shows a flowchart of the procedure used to troubleshoot KA47
systems.

Troubleshooting Flowcharnt

A-1

Troubleshooting Flowchart

Figure A-1 Troubleshooting Flowchart (Page 1 of 4)

LED Dispiay
0001 XXXX

Repiace the
CPU Module

LED Display

| 0011 XX XX [
Put tha sysiem in the

DZ Test
(Test 3)

Disconnact extemal

Fai

Digital Services
environmant

cables and connect

ioopbacks to MMJ
pons 1, 3, and modam

Pass

cPU Modm

control port 2

LED Display
Extemal davice
5 the cause of

Replace the
CPU Module

CACHE Test
(Tast 4}

he prodiam

Pass

LED Dspiay

l 0101 XXXX I

Erter
tha SHOWERROR |
crm:asr;d o checs

MEM Tes!

that

{Test 5)

4 memory

{0 1ha SHOW MEM
command to datermine

OpIONS are recognsed
by the sysiem

Pass
LED Display
X
0110 XXX

FPU Test
(Test 6)

Repiace the
CPU Module

' This assumes that the consoia terminal is connaciad to MMJ pon G.

A-2

Troubleshooting Flowchart

which MS44 memory
oplion & taulty

Repiace the taulty

(- MS44 memory module
or the CPU module

Troubleshooting Flowchart

Figure A-2 Troubleshooting Flowchart (Page 2 of 4)
LED Display
0711 XXXX

Repacethe

CPU Madule

Pass

LED Dispiay
1000 XXXX

SYS Test

thé
Repiace

{Test 8)

CPU Module

Fal

LED Dispiay

[ 1001 XXXX l
NI Test
(Tes1 9)

ral

Check the Ethermet
swilch position

:’U'D"‘G ;Y;Lflm " 1 | Disconnect the network
theEnaronment
Dign
VICes 1 cabig and connect the

Run

N Test
(Test 9)

Replace the
CPU Module

ThinWire terminators or
standard loopback

Network tault,
S86 1he Natwork

co-orginator

Troubleshooting Flowchan

A-3

Troubleshooting Flowchart

Figure A-3 Troubleshooting Flowchart (Page 3 of 4)

LED Display

[Foroxxxx ]

SCSi Test
(Tas1 10)

Enter SHOW DEVICE

or SHOW CONFIG
1o check that the
CPU recogmises all

Devices
rdave unique

Reconfigure the

SCSHIDs

S¢S IDs and

run tha power-up
test agan.

SCS devices.

Put the system in the Digita! Services

emaronment. instali test media in
removabia madia devices

Disconnect extermal SCSI devices
ang connect the SCSI! terminator
to tha systam unit.

Run

Extarnal SCSI
dgevico or CPU

SCSI Tes!

{Test 10)

mogduie s taulty

Check cabie and
connaclion 1o

CPRUModule.

Enter the SHOW ERROR commana or
run the System Exerciser 1o dentity
the SCSI 1D of the faully devics.

Rapiace the taulty SCS! device ]

A-4

Troubleshooting Flowchan

Troubleshooting Fliowchart

Figure A-4 Troubleshooting Flowchart (Page 4 of 4)

LED Display
1100 XXXX

(Test 12)

]

Fal

Put the syslem in the Dignat Services environmant.

Disconnect extemal cables and connect opbacks
(H3199) to synchronous ports 0 and 1.

External commurications
davica 15 causing tha problem

Enter the SHOW ERROR command

Error into

isolates 'ault 1o
Sync Option

Repiace the

CPU Moduie

Yes

LED Display

Replace the

;

\111 © XXXX

Sync Option FRU

ASYNC Test

{Test 14)

Fail
Pul the system in Digrtal Servicas ervironment,

disconnact axtemal cabias and connect oopbacks!
10 asynchronous ports A and B.

External communications
device Is causing the problem

isolates faull to
Async Option

Raptace the
CPU Module

Rapiaca the
Async Option FRU

' For data only ponts use H3101.

For modam control ponts use H4081-A

Troubleshooting Flowchart

A-5

$ 00080006006806080060060000080808000000008868.0448¢44
106060080086800.8808005000
08000068 860000080¢006489444
p0.8.40.400 8086088008808088058000808088480404654¢84¢04
P84 0000098000808800500888808080608808006608884
P00 00008000000
8000000000 00000808998 0¢004¢4
P00 0404488800000 0080808806404680480404040¢4

P 8.0.9060.0600006
0000600808 0848 08600006004/
P0.0.4.60.66.0.690006000800080800864.806400044
$.6.0.0.0.6.0.080605.00060608060008864640¢44
p 000.6.690.60.686.00800560.00000.¢6.0.00¢4
p.O 08009 0808000.00400.09000.¢6.0046064
}9.0.8.6.8.6.0.0.0.80.0.0.6.0.60.6.69.9.6.0.0.0.4,¢
¢4

1$0.060.89049098688609908680964
$0.8.8.0.8.0.9.8.0.9066608065¢000034
pe.0.0.6.00.0.¢00088808469045004
J.014.8.0.4.0.0.83006.04045¢0
4
$0860.0.0.0.0006048604
}.8.€.6.6.0.0.0.6,¢.0.0.9.¢.9.4.0.4
}.4.4.0.9.0.6,0.60.6.4.9.44

b0.9.4.6069648
444
KXXAXXXAKKX
$8.6.8.6.0.8.0.64
XXXAXKX
XXXXX

XXX
X

XXXAX

AXXXAAKL
KXXAKAXEX

XXXXXXXKAKX
$9.9,6.0.0.4.9.0.4.9.4.44
}.0.9.4.9.6.0.¢.6.4¢.0.9.444

XX EXAXAXAXAXXKXXXX

XXXXAKXKX
XA AKX XAXKAKK
$0.9.0.64404986.8400808444
$ 0800050.9.0080800848¢4044¢

PG000.9696080888.806080644
0886880084 8088008600800080¢44
p40.5.9.0.6.08093808648008484804494

190080808 090498060660004¢000¢4 004

B8 0000 0000800800000 83449994844 09]
F3.0.8.8.0.65860696886008.06840006696¢¢4¢4
P09 8000040004 0080800696840809694496¢463

PO S8 0088080800084 8600400880084804484.¢444¢4
§8.0.0.0490000.90640000085008.4036.060$09$669.5¢504
.0.0.0.9.9.0.0,6.9.08.0.0.9,4.0.400006450.0.4906.606¢489¢090.491
19.0.9.0.00.¢.9.8.0.0.96.9.9.6.90.00.900490956066¢0¢608646.64686
p9.90.0.9.00.9.090009.4.008880098640880400¢00609669460¢6491
D90.6890080806004
8800080 5600064.006960866066
.0000
884¢4

§20.0.9:8.0.06.0688060064490008056008400060.6.90.00669866¢470.94

Memory Map
Table B-1 is a memory map for MicroVAX 3100 systems that use the KA47
CPU module (Model 80).

Memory Map

B-1

Memory Map

Tabi2 B-1

Memory Map

Address Renge

System Memory Size (M bytes)

00000000 to 003FFFFF

Bas!

Bas

00400000 to 007FFFFF

Bas

00800000 to 00BFFFFF

—

1st?

1st

ist

00C00000 to OOFFFFFF

—

18t

1st

Ist

1st

01000000 to 013FFFFF

—

2nd?

1st

2nd

1st

01400000 to 017FFFFF

—

2nd

lst

2nd

1st

01800000 to O1BFFFFF

—

—_

—

2nd

1st

01C00000 o 01FFFFFF

—

1st

2nd

18t

02000000 to 023FFFFF

—

lat

2nd

1st

02400000 to 027FFFFF

—

_—

Ist

2ad

1st

02800000 to 02BFFFFF

—

2nd

02C00009 to 02FFFFFF

—

2nd

03000000 to 033FFFFF

—

2nd

03400000 to 037FFFFF

—

2nd

—

2nd

03800000 to 63BFFFFF

03C00000 to 03FFFFFF

—

—_

—

2nd

04000000 to 043FFFFF

—

2nd

04400000 to 047FFFFF

—

2nd

1 Bas indicates the basic systern memory {(connectors 1H and 1L; see Figure B-1).
21st indicates the first memory increment (connectors 2H and 2L; see Figure B-1).

32nd indicates the second memory increment (connzctors 3H and 3L see Figure B-1).

B-2

Memory Map

Figure B-1 Memory Connectors
1L

Note: 1H and 1L are identifiers for the basic system memory connectors.
RE_ENO06467A_91

Note

A failing address ending in 0 or 8 indicates that the memory module in
connector 1H, 2H, or 3H is faulty. A failing address ending in 4 or C

indicates that the memory module in connector 1L, 2L, or 3L is faulty.

Memory Map

B-3

fe0.000.0 000808480000 064 5008800000000000.0:04006.60.0500004

B08.00.0 006000000000 000.06800008600066:0.09080.00 0.4
PRS00 08¢0ttt bEt sttt 00000006800000000.0.0.0.6004
1080400088 0.0606 40000000000608000806004999.9.0.904
PG00 8800000000.00008000806000006060404.004

PG0084048000
060406060808
000008¢649 0
084
PES SOOI OSSO0 PP 00000080
0000.40646.66008

BRI E PP O 080000080000000480800090800004
pE00000.968.0.40060.00840980669.66086606

P00.0085
864 000080¢0666
6908
090¢969.1
0
pE8088008000
00 0400088
880
00 t0eNd
0

§8.0,6.0.8.6.80.006699.08040.6.0.0.6.666.90.4

P80.0.9.8.4.8.9.659.6:0.0690604.66060464
POV 800600668046 0006¢460041

P40.0.8.6.0.9.4.000.600¢8640084.94
§E.0.0.9.600.0.6.6.0.40.¢066848

XAXAK
N KA XA XAKE
AX
KKK
P OO088484646¢6064

XXX XX XXKKXKAXY
$.0.8.6.0.0.9.40.0.6¢4.4

p.9.4.0.4.9.4.4.0.4.4.4

XXXXXUXKX
XXXXXXX
XXXXX
XXX
X

X
XXX

XXXXX
XXXXXXX

XAXXXKAXX
$9.0.0.9.0.6.9.6
¢4

1., 803086446641
EXAAAXKAKAXAAXK
. 9.0.9.9:6.8.0¢.0.0.4.¢.¢4.44¢4

10.8.¢.8.4,0.6,0.0.040.0.6.4.4¢¢4
pO0.64.40.9.84.0.00604900¢4

$0.9.60.0.50.0.8.6.0.6¢940.06.664664

§0.00.008.0808.09.0.5¢¢996800484
DO.45.6.060888009049864060448¢41

PN 0.6.08080006600060060068¢6004

D04000600960.0.0.6606800.40489090]
XAAKXXX
AE KX XA XK KAKXK
KK XK KK KA KKK
X
D O000006000880000000868 6960040604994

00.8.0.0.0.059909.06060900600066606.6.6.5.66.0.9¢944
2O O00800 0 e

008000900660 908006.6000.090000

§9.0.0
090640800
000
00.00000
.08
08606.90
46.
650080
86

PO00.0.0804 480080000000 5600000.0.09900.90¢¢680001
E9.2.9.9,0.6.0.9.0.00.0.¢.00.6.0.¢05.600.099.0.0¢.0.60.0¢6$0006¢80

01
Y90.0.9.4.
0000
0.60
F P00 EOI
,000
N0 E
00
0080
GV
8

PO000.0.09.0.00.08.09.060.0.06.00.80.¢6000.6999.09.00000909390

9¢,

ROD.9.0,0.8:0.0.0.0.0.8.0809.0.0.0.0.00.00.800699.9.6.090.0.
9090099
0.00.0
090

C
FRU Numbers
This appendix gives the FRU numbers of devices in MicroVAX 3100 platform
systems.

C.1

FRU Number Assignments
Table C-1 lists the FRU numbers of devices in MicroVAX 3100 platform
systems.

Table C~1

FRU Numbers

FRU Number

Definltion

(Decimal)
001

CPU module

020

Synchrorious communications moduie DSW42

021

Asynchronous communications module DHW42

040

Memory module in connector 1L

041

Memory module in connector 1H

042

Memory module in connector 2L

043

Memory module in connector 2H

044

Memory module in connector 3L

045

Memory module in connector 3H

100-199

SCSI devices (see Section C.1.1)

FRU Numbers

C-1

FRU Numbers

C.1.1 FRU Numbers of SCSI Devices
The FRU numbers of SCSI devices have the following format:
X1Xg X3

where:

x; is the SCSI controller number. This number is always 1 because there

15 is a number in the range 0 to 7. This number is the SCSI ID number of

is only one SCSI controller in the system.
the SCSI device.

x3 is a number in the range 0 to 8. This number is the logical unit number.

C-2

FRU Numbers

PSS 0600 04000008000 0.600.¢ 000000008968 0000.00800.008404
P09.08,0.05.00 8000004440008 6,0004080600.00.000804000004.¢4

P800 668000000 86888888080860900000.0060408080004044
PO 8859050580608.0.60000000
00000 0408480.066094.606
XXXX XK KOO

XX XK XXX XA XA UK KA KA XK XA AKX

F 000000800880t
es s s800000000.0000480005084¢
B0 00000500008 808000088600 9480888404004

p.40.60.0.0.6088806000000808068 8600004406044
P99.6.0.6.006.60086600580880.800088¢640044

P488000.0.000084000468080.8040000040¢4
PO9.0.000.668480466008580848840048¢¢4
$.0.6.6.0.0.0.0.6.00.6.668068049.64664464¢44

$:4.8.6.0.6.0.9.60.60.005.00544.9096:96¢
p.9.9.809969.0.00.0044.099.60009664
$0.0.9.9.0.8.0.60.6084600446.00.04.4

p.0.6.00.6.0.0.08.09.846.480.6¢4¢

D00.40.8.6.60008088048444
EXXXUXEX
XX XAXL KKK
P8 00.9.08.6.8848
4484
p4.4.6.4.0.6.6.0.6.4¢¢4

$ 66066966661
p.8.4.4.9..9.6.9.4

XXXXXXX
XXXXX

XXX
X

XAXXX
XXXXXXX

XXXALKXAKX
EXXXAXXXARKXX

XX KAAAKXXAXAXK
§.0.8.0.9.6.4.6.¢.6¢¢94¢4
D0.8.6.8.6.0.0.80890404¢44

XAKAXX
KX XX KX XXLAAKR
XUXX XK XA XY XK KA XAXKXEX

XXX XAXK XK KK LRXAXALAXAAAK

$ 8. 00.4.0.60846.46408444496066¢
0.9.9.0.8.04.689000¢6699.0669¢64041
199008049040 6906080.980606446604¢4
p 00000064088006080809806049940641

D08 000800080400 4499064990088640000
XXX XK XX KX KL AL XL XL KL XA XK XXX XAKARKK

000NN E00809.0.90.00.00960806600

)9.4.0.0.
8900000
9.0.0.9.
00040600800800600
866¢6

P O00860.04080 0890008800068 08 6808066600000
¢4
§30.6.0060009090560000.5000608
660 660088840464
4948

10,0.6.0.0.0690.0.89.6:4.8.00.96.0.0950.0.00.0.00506606¢99¢$66981
b00.6.0.8.8.4.8080600.60006.4.90.086.00000660¢06600¢0800
18.9.0.9.6.0.0.0.6.09.0.904.6.060.0005.0000866:4066096806680040404

D00 0406008 0000080808 0000 0000000060.606.0009.09.060.6094

D
KA47 CPU Module Jumper Wires
This appendix describes the functions of the jumper wires on the KA47 CPU
module. Figure D-1 identifies the location of each jumper wire and describes
the function of each jumper wire on the KA47 CPU module.

KA47 CPU Moduie Jumper Wires

D-1

KA47 CPU Module Jumper Wires

Figure D-1

KA47 CPU Module Jumper Wires
Stancard Ethemet

Asynchronous

Connecior

Modem Controi Port 2

IEEE 802.3 compliance;
the jumper 1S normally in

the hoiging position (2-3).

When the jumper isin ——|

positon {1-2), pin 1 of
asynchronous modem contro!

port 2 is connected 10
chassis ground, the jumper
is normally in the holding

position (2- 3.

SCS! oscillaior power
enabie; must be fited for

S—chip oscillator power
enable; must be fited for

normal operaton.

MARR clock oscillator

power enable; must be

fitted for normal operation.

-2

KA47 CPU Module Jumper Wires

]

nomai operaton

PO00.0.0.6.0.0/08000.80000.080

00800
009000
.0000
000000
0609
8
RO L0008 09 608000000050.0660000
.006
000000
.00006008
009
O29 00,00 8.0.000.0 0 00.600.0.00/0.6.0°
0°6.0.
000899
09.09.
0000000
0T

POLE20.8.00 0,000 080500000000¢8000.0090008
990000004¢

PRV 008000000 00.0.000.040.0.007087¢ 000009009909
0
PP00.8.05.0000.00000000.06060000006000099
004
OO0 20000006908 06.0600080000.00.60:09 0000006
POES PN 0.8 00t 000000000688,0
0006000
.9.0
008
9
2E$0.8.08.050.0608004.400906600.0.009909604
PS40.0.8.6.0686.6600.0.0.06000060600.08004
JIV

TS D5300.0.0.000064.040:508004

DO00.0.00.00.9004090680009.0.6004
§90.940.8.04.00004604.6.0060¢49:0,04

DOH0080.68000000680064.06004
po9.9.848.0006¢.0¢000.9004.004
$0 0080.4080006.00640090
XAXA
EX
XK AKX
XX
ALK

XX
XXX AXKAAOK
X
KEXXXXXKKXXKNKXE
0000060964664

04.9,0.0.9.9.¢.40.¢.4

$9.6.4.0.9.6.¢.94
KAXXXXX
XEXXX
XXX
X

XAXXX
1,2.9.0.9.9.44
XAXXNXKXXXX

XXXXXAXKAKX
KXUAKXAXEXXXK

EARAXA
KX XAHAXK
XX

b40.8.0.8.86446.460440
XXXAXXXAXXKA
AKX XX
XK X

B3 4.8.806.09.9004.6469040
hEO 900.080¢8800000409¢44
b EO.0.0.00.89.0000.0.¢.09 084606044

pOO G050 008060600609
494 994
FO.0.0.0.68.0.05406.06.4009060009000
01
DS SO0 000000000 8000.00.0:0:0.0.00
¢80

PEOSD 400946460.00.0.0.00.0.00
80040
90.90
6
00000.8.0.0.00.0.5.00.690.0.
00000
0.9.90
9001

LTS

E0.0.8.0.0.0.0.0.60.9.0.6.¢:00.06.010.0.0.
69300
0.9.4.0
980
04
RO P 00.0.0.0.0.6.0.0000.00.0.90.90.619 00990
0000000
RED OO09.0.0.8,090.608/0.0.0.0506.0
.0000000000¢6¢0e
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXX

XXXXXXXXXXXXXYXXXXXXXXXXXX&XXX
XXXXXXXYXXXXXXXXX
1000000000068
088 8 8 AR A R A A L e LT
Ty

Glossary
The glossary defines some of the technical terms used in this manual.
ASCH

American standard code for information interchange.
CNOS

Complementary metal oxide semiconductor.
CPuU

Central processing unit. The main unit of a computer containing the circuits
that control the interpretation and execution of instructions. The CPU holds
the main storage, arithmetic unit, and special registers.
CRC

Character code recognition. The use of pattern recognition techniques to
identify characters by automatic means.
CSR

Control status register. A register used to control the operation of a device and
record the status of an operation or both.

DMA

Direct memory access. A method of accessing a device’s memory without
interacting with the device’s CPU.
EPROM
Erasable programmable read-only memory. EPROM 1s a type of read-only
memory that can be erased and so returns the device to a blank state.
FPU

Floating-point unit. A unit that handles the automatic positioning of the

decimal point during arithmetic operations.
Glossary-1

Field replaceable unit.
IT

Interval timer.
LED

Light emitting diode.
MMJ

Moedified modular jack.
NVR

Nonvolatile random access memory. A memory device that retains information
in the absence of power.
RAM

Random access memory. A read/write memory device.
RAP

ROM

Read-only memory. A memory device that cannot be altered during the normal
use of the computer.

S-chip

System chip. A single integrated circuit containing most of the system’s
functionahty.

SCSt

Small computer system interface. An interface designed for connecting disks
and other peripheral devices to computer systems. SCSI is defined by an
American National Standards Institute (ANSI) standard.
SOC

System-on-a-chip. An integrated circuit design architecture.

Glossary-2

TOY
Time of year.

vMB

Virtual machine bootstrap. The VMB program loads and runs the operating
system,

VMS
Virtual memory system. The operating system for a VAX computer.

Glossary-3

PONG S ST S P 00800880000000600E000006000000800.060406.404

XX0O0OOC
K
XX KUK
OOOO
AR XK XK KA XK KKOOO
LEXK I AKAX
PO00.849 000800040840 000800668604000000¢0.08540.9.464
PARD

0000000800804 4¢80888000000800 000000600004

PG00 000000000888 0000.60845809005004000008¢0

PO 808000040008 0080800000000060089.89084.64.04

PRS00 008006
00
000006
060880888000 0464
pOE PS00604800.00086000006000606000008004
PO

E 0000060000000 00800004604500.0046644

P00808085000808
080 0000666.000644
0
$ 0,886,080 5.008 0088064844008860644

P8808.6.0980060.008406490.0606000
b90.66086906060850640646094
p 08806609 ¢6680644803¢4.944

p0008.04600.906040004044

10.04008000060.666041

.9.0,8.8.6.6.6.6.60.6.5.4.9.4¢4
$8.0.6.54.666464880044
$.0.6.0.4.0.6.¢.6.0.4¢44
.4.0.4.9.4.6.0.6.0.¢.4

KHXXAXKXA

KAXXXXK
XXXXX
b9.4

XXXXX

XAAXAXX
XXXXXXXXX

b0.0.00.9.664464
$.9.0.9.8.0.8.0.60.64.¢4
KXXAXXKXXXANAXK

XUXXEAXXAX
XK KXXAKK
EXAXAXXAXXXKAXAXANK

$9.4.606.06.098¢6086606061

p0.8.8.0.609688¢80666.000¢091
p8.8.9.8.009.94¢6.069864060604¢
¢4
$0.009.0.0440580648006060.6000¢64¢

F .000404.0.4.40909006060004606060¢4
b 60065000009 088008080806606600
KXXXKXAX XX KX KL XX XK KA XK KA XK KA

KKK

P068.0.0.6000000.0080869800080006000¢1
P60 0000008000000000.980¢066000.600.604
BEG0D 8080004000000 000006068646 998:60¢060¢44

120.0.0.8.9.0.0.0.90.6.600.00966800006000.0080¢609000.94
PRGOS G0 0000 00E90800.04000008 0060990980094

BP0 8040000000000 0¢80.000009000006090.00¢09000644
B0 00000000000
00 800
30 08.0.0:0 000000096
000
9094
8

RO.£.0.8.0.0.90.0.8.9
00060046006
.0.0.6.
00 0.0099.09
0¢00.0.
00800600
P 0.0.4:0.0.0.0.080 608980008
0 000060
600
0.0.99.06009
0V
080

Index
Console devices (cont’d)

A
ASYNC test, 4-21
Asynchronous communications device
testing,

control keys,

4-21

troubleshooting, 4-23
Asynchronous communications interfaces
support for,

2-5

Asynchronous communications options
list of,

function of, 3—4
types of, 3-5
Console mode, 3-6

2-6

privileged,

3-10

3-7

unprivileged,

Console port,

3-7

3-4

Console program

function of,

Console security,
Controls
function of,

3-7

1-7

identification of,

Block diagram, 1-3
Break/Enable switch
function of, 3-5

1-6

Customer environment,

3-15

Device mnemonics

Cache memory test,
CACHE test, 4-8

Cleaning the password,

COMM test,

hist of,

4-8
3-8

Device numbers

4-19

Communications devices,

2-4

Communications options,

2-4

list of,

1-9

setting,

Connectors
function of,

1-6

loopback requirement,

3-15

DSWi41

3-6

troubleshooting,

Console devices

communication parameters,

3-11

Digital Services test environment,

Console commands
overview of,

3-15

Diagnostic tests,

1-7

identification of,

3-11

DHW41
troubleshooting, 4-23
Diagnostic test environment

Configuration
memory,

3-11

Device names
list of, 3-11

3-6

4-20

DSW42
troubleshooting,

4-20, 4-23

Index-1

DZ serial line controiler test, 4-7
DZ test,

4-7

K
KA47 CPU module

1-3

biock diagram of,
1-1

features of,

Environment
testing, 3-15

Error information, 3-14, 3-29
Ethernet circuit test, 4-12
Extended self-test, 3-16
External mass storage devices, 2-2

KA47 system
communications options, 24
configurations of, 1-1, 2-1
mass storage device configurations,
2-1

2-3

list of,
F

Firmware overview,
Floating-point unit
See FPU, 4-10

3-1

numbers for,

Manufacturing test environment,
loopback requirement, 3-16
Mass storage devices, 2-1
external,

3-16

2-2

internal, 2-1
SCSI ID assignments,

FPU, 4-10
FPU test, 4-10
FRUs

2-4

MEM test, 4-9
Memory

C-1

configurations,

1-11

expansion connector identification,

expansion of,

Halt state,

1-9

rules for adding,

1-9

Memory configuration

Indicators
function of,
Initialization,

1-6

3-1

Internal mass storage devices
list of,

2-1

Interval timer

See IT,

4-11

IT, 4-11
4-11

KA47 system,

2-1

Memory modules,

1-9

Memaory option

1-7

identification of,

IT test,

installation of,
Memory test,

1-11

4-9

Miscellaneous system test,
Modem communications,

4-11

4-7, 4-22

Modes
for diagnostic tests,

3-15

MS44 memory modules,

1-9

N
NI test, 4-12
Nonvolatile RAM
See NVR,
NVR, 4-6

4-6

clearing the password,

index-2

2-1

memory configurations,

3-8

1-9

NVR test, 4-6

Serial line controller test, 4-7

complete, 3-1
Synchronous communications device

Onboard memory
location of, 1-9

troubleshooting, 4-20
Synchronous communications devices

Status bar

testing,

4-19

Synchronous communications options

Password

Synchronous communications standards

list of,

clearing,
Ports

3-8

2-5

support for,
SYS test,

function of, 1-7
identification of, 1-6

3-21

error format, 3-22
overview of, 3-19
predefined tests, 3-19

troubleshooting, 4-24
Power-up test, 3-1
display format, 3-1

TEST command format,

error format, 3-3
successful, 3-1

test results, 3-24
System initialization,

3-3

Privileged console mode,

4-11

System exerciser
display format,

Power supply

unsuccessful,

2-5

3-7

3-19

3-1

System test kernel

function of,

3-19

System test monitor

function of,

RRD42
troubleshooting, 4-17
RX26
troubleshooting,

T
Terminal settings,
TEST eommand
rules, 3-12

4-18

RZ23L
troubleshooting,

4-18

variations of,

RZ24
troubleshooting,

3-6

3-11

Test command dispatcher
function of, 3-11
TEST command lines

4-18

RZ25
troubleshooting,

3-19

4-18

typical examples,

3-11

Test environments
customer environment, 3-15

Digital Services environment,

SCSI ID assignments
recommendations for,
SCSI test,
Security,

4-14
3-7

Self-test
display format,

3-13

error format,

3-13

overview of,

3-11

2-4

list of,

3-15

Manufacturing environment,
Test results
for system exerciser, 3-24
TOY clock, 4-6
Troubleshooting

3-16

index-3

Troubleshooting (cont’'d)

asynchronous communications devices,

TZ30
troubleshooting, 4-18

4-23
DHW41, 4-23

TZK10
troubleshooting, 4-18

DHW42, 4-23
DSW41, 4-20
DSW42, 4-20

external SCSI devices, 4-19

Unprivileged console mode, 3-7 -

general procedures, 4-1

Utilities

no screen display, 4-3

RRD42, 4-17
RX26, 4-18
RZ23L, 4-18
RZ24, 4-18
RZ25, 4-18
synchronous communications devices,
4-20
TZ30, 4-18
TZK10, 4-18

index-4

error format,

3-16
overview of, 3-16
TEST command format, 3-16
\,
VAX data types

support of,

1-5

VAX instructions

support of,

1-5