Digital PDFs

EK-A0513-MG-001

November 2000

116 pages

Original

8.9MB

view download

OCR Version

5.9MB

view download

Document:	MicroVAX 3100 Platform KA45 CPU System Maintenance
Order Number:	EK-A0513-MG
Revision:	001
Pages:	116
Original Filename:

OCR Text

MicroVAX 3100 Platform
KA45 CPU System Maintenance
Order Number: EK-A05*3-MG.001

November 1891

Thie manual gives maintenance information for systems that use the KA45
CPU module.

Revigion infermation:

Digital Equipment Corporation
Maynard, Massachusstts

This ic 2 new manual.

November 1961

The information in this document is subject to change without notice and should not be
construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation
assumes no responsibility for any errors that may appear in this document.
No responsibility is assumed for the use or reliability of sofiware on equipment that is not
supplied by Digital Equipment Corporation or its affiliated companies.
Restricted Rights: Use, duplicetion, or disclosure by the U.S. Government is subject to
restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer
Software clauvse at DFARS 2562.227.7018.
© Digital Equipment Corporation 1991.

All Rights Reserved.
The postpaid Reader'’s Comments forms 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, Digital, MicroVAX,
ThinWire, VAX DOCUMENT, VMS, VT380, and the DIGITAL logo.

This document was prepared using VAX DOCUMENT, Version 2.0.

Contents
P O
1

KASCPUModule.............ooiiiiiiiiiiiiiiii
MS44 and MS44L Memory Modules . .....................
MS44 or MS44L Memory Option Installation ...............

1-1
1-8
1-10

D ........ .

KA4S5 CPU Module Description
1.1
1.2
1.3

2 Configuration

2.2
2.2.1
2.2.2
223
23
2.3.1
232

Memory Configurations . ..........oovvunnnrenneneeennn.

Mass Storage Devices. ... ........ ... .. i,
Internal Mass Storage Devices. .. .....................
External Mass Storage Devices .......................
SCSIIDNumbers ..........ccoiiiiiiiiiiieennnnn.
..
Communiecations Options . . ........... ...
Asynchronous Communications Options ................
Synchronous Communications Options . ................

2-1

2-1
2-1
2-2
2-4
2-4
2-5
2-5

KA4S Firmware
3.1
3.2
3.2.1
3.22
3.23
3.24
3.25
3.3
3.3.1

Power-Up Test and Initialization . ........................
..
...,
...
....
... ...
Console Program . ....
Console Device . ...... ... . ... i,
Console Commands . ..........
... iiiieirnneennn.
ConsoleMode . . ..........
...
i
.
i,
... . ....
Console Security ....
Console Command Conventions .. .....................
e
e
e
SelfTest .. ...
Additional Error Information for Self-Tests ...........
...

3-1
3-4
3-4
3-8
3-6
3-7
3-9
3-11
3-14

ifi

TestEnviromments ... ...ttt
33.2
....
...
... ...
Customer Envirenment ............
3321
Digital Services Environment .....................
3322
Manufacturing Environment ......................
33.23
TPV
1
DLt
34
e
e e
SOSI UtItEes . . .- .o oot et e
3.4.1
i e
ieie
et
COMMUtIHtIES .. ...c oot et ittt
342
3.5
System Exerciser ....... ... ..ot

3.5.1
3.5.2
3.5.3

Selective System Exerciser Test (T106). . ......covvennn.

c.c
ittt iiiiainaann
Summary SCreens ............

Additional Ervor Information for System Exerciser Tests ...

15 @
3-15
3-15
3-16
3-16
3-17
3-19
3-19
3-23
3-24
3-29

4 Testing and Troubleshooting
4.1
4.7
4.2 1
4.3

4.4

45
4.6

4.7
48
4.9

4.10
4.1

General Troubleshooting Information......................
No Display on the Console Terminal ... ...... .............
Troubleshooting Procedure for No Display on the Console
Terminal ........ ..ottt
SURTest (Test 1), . ..ottt
ittt et
er e enneneaannns
ittt
DZ Mest (o8t 3) . ... i

CACHE Test (Test 4) ................ e e,
MEM Test (Test 5) . ..o
ittt iieii ittt iinianaeans
ey
FPUTest (Test 6) . .. ... oii ittt iiiiee i
MTest Mest 7). . ... oo
it iiiennnn ee
S Mot (T8 8) ..o i vttt it ittt i e it e
Sy
NI Test (Test 9)
i et ie i ennnes
ttt
ittt ittt
SCSITest (Test 10) . ..o
--------------------------------------

411.2
4113

Troubieshooting an RRD42 CDROM Drive ..............
Troubleshooting an RX26 Diskette Drive . . . . ............
Troubleshooting an RZ23L, an RZ24, or an RZ25 Disk

411.4

DIIVE ..
e
e
e
e e
Troublesheoting a TZ30 Tape Drive . . ... ...............

4.11.1

4118

441.6
412
412.1

493
4.13.1

4-12

4-13

4-15
4-18
4-18
4-18

4-19

Troubleshooting a TZK10 Tape Drive. ... ... ... ... ...
Troubleshooting an External SCSI Device ... ............
COMM Test (Test 12)

419

CommunicationsOption . . . . .........
... ... vinnn.
ASYNC Test (Test 14)
Troubleshooting a DHW41 or a DHW42 Asynchronous
Communications Option
Troubleshooting Procedures for the Power Supply

4-21

Troubleshooting a DSW41 or a DSW42 Synchronous

---------------------------------

-----------------------------

414

4-~10
4-1

------------

4-19

4-23
4-24

4-25

' A Troubleshooting Flowchart
B Memory Map
C FRU Numbers
C.1

C.1.4

FRU Number Assignments .................. ...t

FRU Numbers of SCSI Devices

-----------------------

D KA45 CPU Module Jumper Wires
Glogsary
index
Figures

1-1

1-2

1-3
1-4
i-5

KA5CPUModule...............coiieniiiinnn,

KA45 CPU Module Block Diagram ....................

1-2
1-4

KA45 Controls, Indicators, Ports, and Connectors . . ... ....
Memory Expansion Connectors . ......................
Memory Module Installation .........................

111

2-1

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

2-3

3-1
3-2
33
34
3-5
3-6
3-7
3-8
3-9
3-10
3-11
3-12
3-13
3-14

Successful Power-Up Test Display .....................
Uncuccessful Power-Up Test Display ... ................
Location of the Console-Related Ports and Switches .......

3-2

Location of the NVR Contacts for Clearing the Password . . .
Successful Self-Test Display . .........................
Unsuccessful Self-Test Display . . ......................
Additional Error Information for Self-Tests
Successful System ExerciserTest . . ... .................
Unsuccessful System Exerciser Test
Selective System Exerciser Test (T 106) Example
Summary Screen for System Exerciser DZTest . . .........
Summary Screen for System Exerciser Ni Test . ..........
Suminary Screen for System Exerciser SCS" Test . ........
Summary Screen for System Exerciser COMM Test .......
--------------

--------------------

.........

1-6
1-9

3-13
3-13

3-14

3-21
3-22
3-23

3-25
3-26
3-27

3-28

3-15

Summary Screen for System Exerciser ASYNC Test .. ..... 3-29 ‘

4-1
4-2

Flowchart for Normal System Power-Up ................

3-18

4-3

4-4
45
4-6
A-1
A-2

Additional Ervor Information for System Exerciser Tests ...

Cable Loopback Connectors for the DSW41 and DSW42
e
i e
i
OpIODE . ... v it
Cable Loopback Connectors for the DHW41 and DHW42
e
e
e
OpHONS ... ...
. ....
Flowchart for Troubleshooting the Power Supnly . . ...
KA45 CPU Module Power Connector Pin Voltages.........
Drive Power Connector Pin Voltages ...................

3-30

4-4
4-22

4-25
4-26
4-27
4-27

Troubleshocting Flowchart(Page1of4) .........
... ...
Troubleshooting Flowchart (Page20f4) ................

A-2
A-3

A-3

Troubleshooting Flowchart (Page3of4) ................

A-4
8-1

Troubleshooting Flowchart (Page 40f4) ................
Memory Connectors ...........c.cvvitiueeennennann.

A-5
B-2

D-1

KA45 CPU Module Jumper Wires . ....................

D-2

Tables
1-1

Functions of the Controls, Indicators, Ports, and

1-7

1-2

KA45 CPU Module Memory Configurations . . .. ..........

1-10

2-1

KAd45 Internal Mass Storage Devices...................

2-2

-2

Supported External Mass Storage Devices.

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

2-3

Recommended SCSI ID Numbers for Devices ............

2-4

Supported Asynchronous Communications Options . .......

2-5

-5
2-6

Supported Synchronous Communications Options .. .......
DSW41-AA and DSW42-AA Communications Support. . . ...

2-6
2-6

3~1
3-2

Console Device Port Selection ........................
Terminal Settings. . ...,

34
3-5

3-3

3-10
3-11

3-5

Console ModeControl Keys . .........................
Device Numbers and Mnemonies ......................
Typical TEST Command Lines. . ...........
... ......

3-6
4~1
42

Predefined System Exerciser Tests. . ...................
Troubleshooting Procedures . .........................
SCSI Device Troubleshooting Procedures . . . .............

3-20
4-3
4-17

B-1

Memory Map ...........ccoiiiiiiiiiiin
tinennnn

B-1

COMDECEOTS . . .o v ittt

3-12

vii

Page viii is a blank page

Preface
This manual describes the KA45 CPU module used in the MicroVAXTM 3100
Model 30 and Model 40 systems. It provides the configuration guidelines,
ROM-based diagnostic information, and troubleshooting information for
systems containing the KA45 CPU module.

Audience

This manual is for DigitalTM Services personnel who provide support and
maintenance fGi systems that use the KA45 CPU module. It is also for
customers whe 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:
e

Chapter 1 describes the KA45 CPU module.

Chapter 2 describes the KA45 system configurations.

Chapter 3 describes the structure and operation of the KA45 firmware.

Chapter 4 describes the ROM-based diagnostic testing and troubleshooting
procedures for the KA45 systems.

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

Appendix B gives a memory map for a KA45 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
KA45 CPU module.

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

MicroVAX 3100 Model 30 Cover Letter, EK-A0515-CL

MicroVAX 3100 Model 30 Installation Information, EK-A0520-IN

MicroVAX 3100 Model 30 Operator Information, EK-A0521-UG
MicroVAX 3100 Model 30 Customer Technical Information, EK-A0522-TD
MicroVAX 3100 Model 30 Troubleshooting and Diagnostic Information,
ER-A0516-TM

MicroVAX 3100 Model 40 and Model 80 Cover Letter, EK-A0517-CL
MicroVAX 3100 Model 40 and Model 80 Installation Information,
EK-A0523-IN

MicroVAX 3100 Model 40 and Model 80 Operator Information,
EK-A0524-UG

MicroVAX 3100 Model 40 and Model 80 Customer 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 KA45 CPU systems:

Guide to MicroVAX 3100 Platform Maintenance Information Kit,

EK-A0512-MG

CPU Reference Information, EK-A0574-HR

BA42-A Enclosure Maintenance, EK-A0510-MG
BA42-B Enclosure Maintenance, EK-A0511-MG
IPB, EK-MV310-1P

Options, EK-A0519-MG

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

Conventions
The following conventions are used in this manual:
Convention

Description

Ctrl/x

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 eiements. You must
choose one of the elements.

Q1
O

In format descriptions, brackets indicate optional elements. You can

choose none, one, or all of the options.

In format descriptions, parentheses delimit the parameter or
argument list.

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

Anitem that is repeated

An omission such as additional options] arguments

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

In format descriptions, a vertical bar separates similar options, one
of which you can choose.
italic type

Italic type emphasizes important information, indicates variables,
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 R nR

nan

MONOSPACE

A space character separates groups of 3 digits in numerals with 5 or
more digits. For example, 10 000 equals ten thousand.
A period in numerals signals the decimal point indicator. For
example, 1.75 equals one and three-fourths.
Text displayed on the screen is shown in moncspace type.

Convention
Radix indicators

Description
‘The radix of a number is written as a word enclosed in parentheses,

for example, 23(decimal) or 34(hexadecimal).

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 cau*ion contains information to prevent damage to the equipment.

P 5. 0. 5. 9:¢.4

Py WESEVI

N N A R A R R LA RSSO KM

AR A
A X RM
MM

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

KA45 CPU module

MS44 or MS44L memory modules

MS44 or MS44L memory option installation

1.1 KA45 CPU Moduie
The KA45 CPU module is based on system-on-a-chip (SOC) silicon technology.
It uses MS44 or MS44L memory modules and a set of supported small
computer sysiem interface (SCSI) devices. Figure 1-1 shows ths KA45 CPU
module.

The KA45 CPU module is th= primary component of the MicroVAX 3100
gystem in which it is instailed. The KA45 CPU module contains the following
components:

The DC222 (SOC) processor chip—-This chip is a 32-bit complementary
metal oxide semiconductor (CMQOS) virtual mewmory microprocessor.
it includes an internal floating-point unit and a cache memory. The key
features of the chip are as follows:

Suppor: 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

Contains a 32-bit external data bus

KA45 CPU Module Description

1-1

KASS GPU MOGUIe Descrpuon

Packaged in a single chip

Figure 1-1

KA4S CPU Module

91
RE_ENO8195A

'The DC7201 S-chip—This chip is the primary interface between the CDAL
bus and all memory, video, 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 numerous design specific
features.

1=2

8M bytes of onboard random-access memory (RAM) with parity checking

Support for up to 24M bytes of additional RAM

256K bytes of read-only memory (ROM)-This ROM contains the boot
and diagnostic firmware for the system.

KA45 CPU Module Description

Provision for 32K bytes of additional 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 onboard options.

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

One modem control port—This port is 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 additional DEC423 ports for Model 30 systems and zight or
sixteen additional DEC423 ports for Model 40 systems

Four additional modem control ports for Model 30 systems and eight
additional modem control ports for Model 40 systems

Provision for synchronous communications options that provide:

One synchronous port for Model 30 systems and two synchronous ports

for Model 40 systems

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

KA45 CPU Module Description

1-3

Ka45 CPU Module Description

Figure 1-2 KA45 CPU Module Block Diagram
=

CDAL Option Port
{Asynchronous Expangion)

DeTm

S_Chip

64K
%

o Ld

Onboard

L_...,.___J

(8M bytes)

ofy Expan

- 3

EDAL Option Fort

Modem Latches
and E1A Transgiation

{Synchroncus txpansion)

One Mousm
Conwel Port
and Three
DEC423 Ports

Stendard
Ethamat
Port

53C84 SCS!I
inteenal
SCsi

Port

i=-4 KA45 CPU Module Description

ThinWire

Extermnal
| SCSI

Pont

LB Ethemet
Port

RE_ENO0S188M_31

KA45 CPU Module Description

The KA45 CPU module supports the following VAXTM data types:
e

byte, word, longword, quadword

character string

variable-length bit field

e ffloating-point, d_floating-point, and g_iloating-point

The operating system uses software emulation to support other VAX deata
types. The KA45 CPU module supports the following VAX instructions:
e

integer and logical

address

variable-length bit field

control

procedure call

miscellaneous

Qqueue

character string instructions:

CMPC3/CMPC5

LOCC

MOVC3/MOVC5

SCANC

SKPC

SPANC

operating system support

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

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

KA45 CPU Module Description 1-5

KA45 CPU Module Description

Figure 1-3 KA4S Comntrols, indicators, Ports, and Connectors
DHW41/DHW42
Logic Board

DSW41/DSW42
Logic Board

Connectors
A N\

Connectors

;

e |t8rN2] SCSI| Connector
—

Gonnectors

Memory Expansion

External SCS!
Connector
Power
Connector

Standard

VO Connsector

——

LED Display

‘— Break/Enable LED

DSW4411/DSW42

Break/Enable Switch

¥O Connactor

Hak Push Button

MM, Port 0

MM, Port 1

Ethernet Port

DHW41/DHW42

\——Thianre

us Modem
Asynchrono
Control Port 2
MMJ Port 3

RE_ENOB19TA_91

-8 KA4S UPU Module Description

KA45 CPU Module Description

Teble 1-1 Functions of the Coatrols, Indicators, Porte, and Connectors
Component

Internal SCSI connector
Memory expansion

Doscription

A connector that provides a connection to SCSI devices

mounted inside the system enclosure.

Three pairse of connectors for memory options.

connectors

External SCSI connector

A connector that provides a connection to SCSI devices that

are external to the system enclosure.

Power connector

A connector for direct current (dc) power.

ThinWire Ethernet port

A port that provides a connection to 8 ThinWire Ethernet

Ethernet switch

A two-position switch that determines the type of Ethernet

Standard Ethernet port

network.

that the system uses as follows:

Left position—selects the standard Ethernet type

Right position--sslacts 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

Break/Enable LED

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

Breal/Enable switch’

diagnostic code information.
follows:

On—MMJ port 3 functions as a console port.

Off—MMJ port 3 functions as a communications port.

A two-position switch that determines the function of MMJ
port 3 as follows:

Up position—MMJ port 3 functions as a console port.
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.

1The system recogrizes the position of this switch only when the system is turned on.
(continued on next nage)

KA45 CPU Module Description

1~7

KA45 CPU Module Description

Table 1-1 (Cont.)

Functions of the Controls, indicators, Ports, and Connectors

Component

Description

Halt push button

A momentary-contact push button that puts the system in
console mode.

Asynchronous r..odem

EIA-232 compatible asynchronous port with modem control.

cantrol port 2

MMJ port 3

DEC423 compatible asynchronous port. This port functions
as an alternate console port when the Bresl/Enable switch

is set to the up position when you turn on the system.

MMJ poit 1

DEC423 compatible asynchronous port.

MM.J port 0

DEC423 compatible agynchronous port. This port is the
primary console port.

DSW41 or DSW42 I/O

A connector that provides a connection for the DSWa1 input

DHW41 or DHW42 VO
connector

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

DHW41 or DHW42 logic
board connectors

Two connectors that provide connertions for a DHWA41 logic
board or a DHW42 logic board.

DSW41 or DSW42 logic
board connectors

Two connectors that provide conrections for a DSW41 logic
board
or a DSW42 logic board.

connector

/output cable or the DSW42 input/output cable.

1.2 MS44 and MS44L Memory Modules
The MS44 and MS44L memory modules provide memory expansion for the
KA45 CPU module. The KA45 CPU module supports the MS44-BA (8M-byte)
option, which contains two MS44L-AA (4M-byte) memory modules, and the
MS44L-BA (8M-byte) memory option, which contains two MS44L-AA (4M-byte)
memory modules.
]

Note

Use only MS44 or MS44L memory modulzs qualified by Digital.

The rules for adding MS44-AA or MS44L-AA memory modules are as follows:

1-8

You must install both memory modules of a memory option. This means
that you can expand memory in 8M-byte increments.

You must install memory options in the next available connector pair in

ascending numerical order.

KA45 CPU Module Description

iKA45 CPU Module Description

Figure 1-~4 shows the location of the onboard memory (8M bytes) and the
memory expansion connectors. Table 1-2 lists the memory configurations.
Flgure -4 Memory Expansion Connectors
iL

RE_ENOE198A_91

KA45 CPU Module Description

KA45 CPU Module Deacription

Table 1-2 KA4S CPU Module Memory Configurations
Total

Onboard

Memary Memory

incrament 1

Increment 2

1M'

(bytes)

16M

MS44-AA?

MBS44-AA

24M

MB44-AA

MS#4-AA

MS44-AA

inerement 3

13H, 1L, 2H, 2L, 3H, 3L are the connector identifiers (see Figure 1—4).
2The MS44-AA memory module is a 4M-byte memory module. The MS44-BA memory option

consists of two MS44-AA memory modules. You can use MS44L-AA memory modules instead of
MS44-AA 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 KA45 CPU module as follows:
.
1.

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

Identify the connectors on the KA45 CPU module into which you must
inetall 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 KA45 CPU module (see Figure 1-5).
Caustion
The connectors are keyed so that you install the memory modules with
the correct orientation. Do not force the modules into the connectors
with an incorrect orientation.

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

1-10

KA45 CPU Module Description

Filgure 1-6 WMemory biocdule installation

RE_ENOB199A_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.
5.

Repeat the procedure in step 1 for the second memory module. Insert it
into the other connector for that memory increment on the KA45 CPU
module.

Run the MEM diagnostic test (see Section 4.6) after you reinstall the
KA45 CPU module into the system enclosure to check that the memory is
working correctly.

KA45 CPU wlodule Description

1-11

A45 CPU Modl Description

Caution

When removing memory modules, you must release the metal clips . n
the connectors of the CPU module.

1=12

KA45 CPU Module Description

8 o

D A

s T2t i

KRR
RARA
RN
BRARR

el
diotetsdiseet
o
pesstveosededd

pieeiotes
o eiend
0000
nONHox
44,964

K
X

00O

G000ONGNONGNNOGNNH
X KX XANOOOLX

YK
GOONGHONNNOO0N
X ROOO0NGL X KNG
NNINO0000K

NO0GONNGOCOOOONCODARNNNRNHGOGTOCHDNNONCGOOOGOIXKX
X

OOOGONU

X0
OCGDOENNN0CONRNOCONCOAN0OA0N00MK

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

Memory configurations

Mass storage devices

Communications options

2.1 Memory Configurations
A KA45 system has 8M bytes of onboard memory. You can add memory in
8M-byte increments, up to a maximum of 32M bytes. See Section 1.2 for
information on the memory configurations.

2.2 Mass Storage Devices
A KA45 systern supports mass storage devices in the following categories:

2.2.1

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 cennect to the system externally.

internal Mass Storage Devices
Table 2-1 shows the internal mass storage devices that a KA45 system
supports.

Configuration

2-1

Configuration

Table 2-1

KA4S Internal Mass Storage Devices

Option Name

Description

Size'

Capacity

(in)
RZ28L

Disk drive

3.5

120M bytes

RZ24

Disk drive

3.5

209M bytes

RZ25

Disk drive

385

400M bytes

TZ30°

Tape drive

5.25

95M-byte cartridge

TZK10*
RX264

Tape drive
Diskette drive

5.25
35

Range of cartridges®
Range of diskettes®

RRD42*

CDROM drive

5.25

600 Mbytes

1Size of half-heig):t device.
2Supports 320-Mbyte and 525-Mbyte cartridges.
3Supports 1.4-Mbyte and 2.8-Mbyte diskettes.
‘Removable media device.
The combinations of internal mass storage devices that you can have in a
KA45 system depend on thc system enclosure. See the BA42-A Enclosure
Maintenance or the BA42-B Enclosure Maintenance manual.

2.2.2 Bxternal Mass Storage Devices
The external mass storage devices connect to KA45 systems via the SCSI
connector on the back of the system enclosure. In KA45 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.
In Model 30 systems, the maximum number of mass storage devices in the

system enclosure is three. This means that *vu can connect at least four
external mass storage devices.
in Model 40 systems, 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 KA45 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

Configuration

Figure 2-1

SZ Expansion Box Numberin® System
SZinx-xx

Enclosure Type

2 = 8A42 Enclosure
6 « BA4S Enclosure

l—- Powsr Cord Typa
A=120Veac
B8=240Var

{.oft Compartmant

Right Compartment

A=R235
8 = RZ58
C = RZ87

AeRZ85
B=R258
C = RZ57

R = R258
X = Empty

£aTA10
F « RRD42

P «RZ2S"

D = TL2042
HeTZ30
L=R¥X23
M« RX33

P=RZ225'
R = RZ58

X« Empty

! The RZ25 disk drive fits in the BA42 enclosure only.

2 Tho TLZ04 tape drive fits in the BA48 enclosure only.

A KAd45 system also supports other types of external mass storage devices.
Table 2-2 gives the other external mass storage devices that a KA45 system
supports.

Table 2-2 Supportr = “xternai Muss Storage Devices
Davice

Dagcription

RRD42-DA

RRD42 CDROM tabletop

TLZO04-FA

TLZ04 tape drive tabletop

TK50Z-GA/G3

TKS50Z 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

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

The BA40 single drive expansion box contains one SCSI device.

SZ12 enclosure contains two SCSI devices.

Configuration

2-3

Configuration

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

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 doss

not wse the cables supplied by Digital or is not configured in accordance
with Digital recommendations.

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

SCSi ID

Device

Rz2+!

Rz2* !

RZ2° ! (system disk)

RRD42

TZ30 or TZK10 (system backup device)

SCSI controller (INITR)

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

2.3 Communications Options
A KAd5 system supports the followang types of communications options:

2-4

Asynchronous communications options

Synchronous communications options

Configuration

‘

Contiguration

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
The asynchronous communications options that a KA45 system supports
depend on the model type of the system. Table 2—4 gives the asynchronous
communications options that the KA45 systems support.

Table 2-4 Supported Asynchronous Communications Options
Modet 30

DHW41-AA

Eight-line DEC423 asynchronous option

DHW41-BA

Four-line EIA-232 modem control asynchronous option

Hode! 40

DHW42-AA

Eight-line DEC423 asynchronous option

DHW42.BA

Sixteen-line DEC423 asynchronous option

DHW42-CA

Eight-line EIA-232 asynchronous modem control option

DHW42.UP

Eight-line to 16-line DEC423 asynchronous upgrade option

2.3.2 Synchronous Communications Options
The synchronous communications options that a KA45 system supports

depend on the model type of the system. Table 2-6 gives the synchronous
communications options that the KA45 systems support.

Configuration 2-5

Configuration

Table 2-5 Supported Synchronous Communications Options
Deseription

Option

Yodel 30

DSW41-84A°'

One-line EIA-232/V.24 synchronous option with one external cabie,

BC15D-02 (17-01110.01)

DSW42-AA°

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

YThis option is supplied with one external cable that supports the EIA-232/V.24 interface.
2This option is supplied with two external cabies that support the EIA-232/V.24 interface.
The DSW41-AA and the DSW42-AA options also support the communications
interfaces lsted in
in Table
Table 2-§,
2-8, but you must order the external cables
separately.
-

‘0’

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

External Cable

EIA-423/V.10

BC29E-02! (17-01111-01)

Ela-422/V.11

BC19B-02! (17-01108-01)

wo required for DSW42-AA.

2-6 Configuration

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

Power-Up test and initialization—This code tests and initializes all the
devices in a KA45 system.

(Console program—This program parses and executes all the commands
entered at the console prompt (>>3).

Self-Test—This code executes when a user runs a diagnostic self-test
by entering the comnmand TEST at the console prempt. 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 KA45 firmware functions.

Svetem evercicor—This code tests the oporation of devices in the gystem
concurrently. The purpose of this code is to provide a high level of DMA
and interrupt activity for devices in the KA45 system.

3.1 Power-Up Test and Initialization
When you turn on the system, the svstem executes the power-up test and
initialization code, which builds a power-up test display on the console
terminal that is connected to the system unit. When the default recovery
action is set to 3 (see CPU 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.

KA4S Firmware

3=1

Figure 3-1 Successful Power-Up Test Display
KA4S-a V1.0Q)

08-C0=2B~04-03~12

T“Hfl######f#fl#####fl““###fl*@fl#@#fl#”i#####"#Q [ ]
>»> @

A~-On a Standerd ASCH Terminal

Ka4s-a v1.09
08~00-28-04-03-12 @
2m@

>>0

8-0On a Graphics Display Termina!

The CPU name and the version of the KA45 firmware. The character V
indicates the version of the system firmware. The number 1.0 indicates the
reieaze 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 is 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 KA45 Firmware

KA45 Firmware

Figure 3-2 Unsuccessiul Power-Up Test Display
Ka4s-A v1.0@
08-00-2B-04-03-12 @
28

HEEE0008000000
00080000 0000000000 0000000000 ©
2?2 001

0066 &

»@

A-On a Standard ASCH Terminal

KA¢S-A V1.0@
08-00-2B-04-03-12 @

22 001

0066 @

»> @

B-0On a Graphics Display Terminal

The CPU name and the version of the KA45 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.
Incomplete status bar.

Completion mark.

An error message—The elements are as follows:
¢

Two question marks (??7) indicate a hard error, that is, an error that
you must correct before you boot the system. A single question mark (?)
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 is the test number (in this example, the Ethernet test number).
NI is the test mnemonic (in this example, the Ethernet test mnemonic).

KA4S Firmware

3-3

KA4SFinmware

¢ (066(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
Informntion Interchange (ASCII) terminal. The system output
n a graphics display terminalis siightly different from a standard

tprmmal 2 nnhrl flfnhlfi hnr mnlgnes the lific of"umb:.r. Sigl.'-—ls (#)
C

3.2 Console Program
‘ine consoie program 1s irmware 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 machire
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 MIMJ port 0 or MMJ port 3 is the console device (see Table 3-1).

Table 3-1

Console Device Port Selection

Breal/enable Switch

Position’

Console Terminal Port

Down

MMJ Port 0

MMJ Port 32

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

34 KA4S Firmware

KA45 Firmware

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

Halt Push Button

iMiMJ Port 3
MMJ Port 0
RE_ENGS200A_1

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

Turn off the system unit.

Set the break/enable switch to the up position.

Turn on the system unit.

MMJ port 3 is now the console port terminal. You can connect one of the
following console devices to this port:
o

A VTTM geries type terminal (for example, VT330TM)

A printer (for example, LA34)

KA45 Firmware

3-8

KA4S Flrmware

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 congole mode. To ensure the

correct operation of the terminai, you must set the communicaticn parameters
for a 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

Recsive speed

receive = transmit

Character format

8 bits, no parity

Stop bits

Comm] port

DEC-423 (data-leads-only)

3.2.2 Console Commands

You can enter comsole 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 executes the command. If the console program detects an error, it displays
an error message. CPU Reference Information, Chapter 2, gives the console
messages for KA4D systems.

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

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

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 funclion
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.

3-6 KA4S Firmware

KA4S Flrmware

Critical CPU condition—The system forces a CPU restart or 2 reboot

when it detects an event that it interprets as a severe corruption of its
operating environment. The virtual memory system (VMS) sysgen
parameter, BUGREBOOCT 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 KA45 systems have & conscle 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 CPU 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:
e

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:
o

BOOT (without parameters}

CONTINUE

! (Comment)

When you enter a commang ~i:er than the four commands shown previously
while the system is in unpriviieged console mode, the system displays an error
message as follows:
223 ILL CMD

KA4S Firmware 3-7

You can use the LOGIN command (see CPU Reference Information, Section 1.9) O
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.

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

BOOT

CONTINUE

HALT

START

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

1.
2.
3.

Set the on/off switch on the system unit to the off (O) position.
Remove the enclosure cover. See the BA42-A Enclosure Maintenance or the

BA42-B Enclosure Maintenance manual for more information.

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

3-8 KA4S Firmware

KA4S Firmware

Figure 3-4 Location of the NVR Contacte for Clearing the Password
MiMJ Port 0
MM Port 1

MM Port 3
Asynchronous
Modem Control
Port 2

NVR Contacts (2)
NVR

RE_ENCI01A_O

Install the enclosure cuver.

Turn on the system unit.

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.25 Console Commmand Conventions
When entering console commands, the following rules apply:

Commands cannot be more than 80 characters long.

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

The commarid 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).

Kads Firmwaro

3-8

KA45 Firmware

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

these keys and control functions.

Tabie 3-3 Console MMode Control Keys
Key

Function

Return key

Ends a command line.

Delete key

Deletes the previously typed character. On VT series terminals,
press thie 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

Ctrl/C

Causes the console program to abort processing a command. The

CerV/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 Ctrl/O. The

to put the system in console mode.

console program displays Ctrl/C as AC.

console program displays Ctrl/O as AO.

Cual/Q

%sumes the console output that is suspended when you press Ctrl

CtrlR

Causes the current command line to be displayed, without the

Cerl/'s

Suspends the current command line that the console program

Cal/U

Discards all the characters on the current command line. The

deleted characters.

displays until the next Ctr/@ sequence.

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 AU.

1 Applies only if the brealvenable switch on the back of the system unit is set o 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

KA4S Firmware

KA45 Firmware

3.3 Self-Test
The KA45 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
digpatcher is the code that runs the seif-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 KA45 systems.
rs
and Mnemonice
Veble 3-4 Device Numbe
Devieo Mumber

Dgvice Mnamonic

Deseription

NVR

Nonvolatile RAM
Regerved for future use

2
3

D7z

Serial line controller

CACHE

Cache system

MEM

Memory

FPU

Floating-point unit

Interval timer

SYs

Miscellaneous CPU module hardware

Network interface

8Csl

SCSI controller

Reserved for future use

COMM

Synchronous communications option
Reserved for future use

ASYNC

150 99

Asynchronous ccmmunications 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:
o

A single device

Multiple devices

KA4S Firmware 3-11

KA45 Firmware

e A range of devices
e

A combination of the three previous options

Table 3-5 gives some typical TEST (T) command lines.
Tabie 3-5 Typical TEST Command Lines
Type

Single devics

Command

Using Device

Kumbers

énemaonics

TS5

T MEM

Description

Runs the self-test on
memory.

Multiple devices

T 3,4

T DZ,CACHE

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

Device range

T 57

T MEM:IT

Runs the self-test on the
memory in the system, the
floating-point unit, and the
imterval timer (IT).

Combination

T 1,3,8:10

T NVR,DZ,SYS:SCSI Runs the self-test on the

nonvolatile RAM, serial line
controller, miscellaneous
CPU moduie 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:DZ

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

=12

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.

KA4S5 Firmware

KA4S 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 Display
>>>'.l‘97

mmm O
ox®
>»>

@® Complete status bar.

@ A console status message that indicates a successful test.
Figure 3-8 shows an unsuccessful self-test display.
Figure 3-6 Unsuccesstul Self-Test Display

fl#z‘
'w 001 07 FP 22

84 FaIL®
>>>

Incomplete status bar.

Two guestion marks (??) indicate a hard error, that is, an error that you
must correct before you boot 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 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 console error message that indicates a test faiiure (see CPU Reference
Information, Chapter 2).

KA4S Firmware

3-13

KA45 Firmware

CPU Reference Information, Chapter 3, lists the error codes and messages that .
the KA45 diagnostic tests generate.

3.3.1 Additional Error Iinformation for Self-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 Additional Error Information for Self-Tests

@06

22001

6
3

0050

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

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 line for the various tests.

3-14 KA4S Firmware

KA4S5 Firmware

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

Customer environment

Digital Services environmerit

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 is 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:
>>> SET DIAGENV 1

3322 Digital S*vices 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) ¢ 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 cantrol port 2 are leoned, To put the

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

In this test environment, ceriain tests and utilities require loopback connectors
(see Chapter 4).

KA45 Firmware

2-18

an o
o e

& aph TSRO
AP

FARD PIIIIIEIC

3323 Mamnufacturing 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 ? yn 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 KA45 firmware provides utilities for the following devices:

o
-

SCSI
Falal Vo V3

UJiNEIVE

You invoke a utility using a TEST command that has the following format:
>>> T[EST}/UT{ILITY] <devnan |

devnbr>

where:

T[EST] is the TEST command

/UTLITY] is the utility qualifier

devnam is the device mnemonic

devnbr 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-18

KA45 Firmware

scs1_E err 196@
84 Fa1L@®
>

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

3.4.1 SCS| Utilities
To get a list of the utilities available for SCSI devices, enter the following
command:

>>> TEST/UTIL SCSI

The system dispiays the following menu:
1
2
3
4

- SCSI-flp key
- SCSI-tp_key
- SCSI-hd_dsk_eras
- SCSI-flp fmt

SCSI_util>>>

The functions of these utilities are as follows:

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

Note

This utility works only in the Digiiai 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 ihie
system in the Digital Services environment, see Section 3.3.2.2.

KA4S Firmware 317

KaAd5 Flrmware

Caution

You can use the SCSI-hd_dsk_eras utility in the Customer

‘II'

environment.

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

SCSIi-fip_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 KA45 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:
SCSI_id{0=7)>>> 1

The KA45 firmware prompts you for the logical number of the drive, usually 0,
uniecss there is another STSI controlier in the gystem. Enter 0 in responsc to
the prompt as follows:

5CSI_lun(0-7)>>> 0

The KA45 firmware displays a status message, then a prompt. You must enter
OK in response to this prompt as foliows:
SCSI HD_DSK_ERAS UTIL

DKA100

OK? (K

The KA45 firmware displays a status bar, indicating that the erasing of the
disk is progressing. This operation takes several minutes. When the operation
is complete, the KA45 firmware displays a complete status bar and status
messages as follows:

YTTTTTTrTrrrrrrITIN
SCSI_bb_repl 0
SCSI_util succ

3-18

KA4S Firmware

3.4.2 COWNM Utiiities
The KA45 firmware inci.. :8 some utilities for synchronous communications

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

Y
& System Exerciser

The KA45 firmware has a system exerciser that tests the simultaneous

operation of multiple devicesin a KA45 system. The system exerciser tests the
interaction of devicesin the sysiem by
causing maximum DMA and interrupt
activity. You invoke the system exerciser by entering 2 TEST command that
has a test number in the range 100 to 106. For example:
>»> T 100

The KA45 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. Centrol then passes to the system test kernel, which defines
the appropriate operating environment. 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 exerciger tests, T 102 and T 104, are destruciive 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.

KA4S Firmware 3-18

KA4S Firmware

Table 3-6 Predefined System Exerciser Tests

Cammand

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 108

Runs the system exerciser

Manufacturing

T 104

Runs the system exerciser

Special!

T 106

Runs the system exerciser on

Digital Services or

101

system exerciser.

until vou prees Crl/C.

until you press Curl/C.

until you press Cerl/C.

selected tests. The firmware
prompts you to choose the

Manufacturing®

tests
you want to run.

YThis 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 that was run in the
Digital Services environment.

3-20 KA45 Firmware

KA45 Firmware

Flgure -8 Successfu! System Exerciser Test
>>> T 101

KA45/47 V1.0

System Test CS

2t @

NI §

SCSI ¢

com #

AsyNC §

0 00:01:29

s#xwwt SYT DISPLY SUMRY ((‘1'=Y), (*0'sN))............co.nnn, > @

@© 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 hiours:minutes:zseconds.
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 that was run in the
Digital Services environment.

KA48 Firmware 3-21

KA4S Flrmware

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

Kad45/47 V1.0

System Test CS

opz¢

NI ¢

SCSI ¢

cox §

ASYRC

&8@&

0305

‘

0 00:00:59

0 00:01:26

re%dd SYT DISPLY SUMRY (('1'=Y), ("O0'=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 marke (7?) indicate a hard error, that is, an error that you

must correct before booting the system. One question mark (?) indicates a
soft arver, that is, an ervor that you do not have to correct before hooting
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 eccurred.

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.

322

KA45 Firmware

KA4S Firmware

3.5.1 Sslective 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

=PRAO

TST DEV = DZ

TST DEV - NI

TST DEV - SCSI

TST DEV - COMM

TST DEV - ASYRC

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.

KA4S Firmware 2-23

KA4S Flrmaware

3.5.2 Summeary 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
SUmMmMAary screens

When you press Ctrl/C to interrupt a system exerciser test and you choose
to view the summary screen

When vou enter the command SHOW ESTAT (see CPU Reference
Information, Section 1.12.7)

The summary screens are displayed in the order in which the tests are
performed. When the system cxerciser test is complete, it displays a prompt at
the bottom of the screen as follows:
*#xx# SYT DISPLY SUMRY ((‘1'=Y),

("O’'=N))..........c0cuv..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 screens formats of the ’
individual tests are the same in all test environments.

3-24 KA4S Firmware

A4S Flrmware

Figure 3-11 Summary Screen for Sygtem Exerciser DZ Test

wxawaadwck FST EXT ERRPT

Line

0
1
2
3

L_Param Chr Xmt

00000780
00000780
00000780
00000000

3D2

0 00:01:25 ##wwmavasns

Chr_Rec

00000780
00000780
00000780
06000000

Error

*#*** No Exrr = w##se
=##=¥% No Err = ww#et
*###%#* No Err - #w¥e
*Not Tstd - Cons_lin*

whaakwaeks GYSTST
MXT SCR ((' (('1'=Y), ("O’'=N))......... 1 @
Summary screen identifier.
Test number and mnemonic.

The time taken to complete the test.

The number of the line that is being tested as follows:
e

( represents MMJ port 0

1 represents MMJ port 1

2 represents asynchronous modem control port 2

3 represents MMJ port 3

The communication line parameters (displayed only wher 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.

Ka4s Fumware 3-28

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

Flgure 3-12 Summary Screen for System Exerclser Ni Test

twszwsersrs FST EXT ERRPT

9NI

0 00:01:35 swereaznss

treewraees SYSTST
NXT SCR ((‘ (('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 is an example of a summary screen for the SCSI test that was
performed during a system exerciser test.

328

KA45 Firmware

KA4S Flrmware

Figure 3-13 Summary Sceeen for System Exerciser SCSI Test
@

#ewukanrrs FST EXT ERRPT

ADR

RDS

WRTS

10SCSI

000

ERR FRU CMD

1/0 00010987 00000000
3/0 00005643 00005643
4/0 00000028 00000028 160 150

0 00:01:31 *rwxsxesres

PBS INF LBNSTRT

XFERSIZ

1378

119

sexrseirer SYSTS
NXT SCR
T ((* (('1'=Y), (*0'=N))......... * @

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

The SCSI ID and the legic unit number of each device.
The number of read operations (decimal) performed cn 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 information code {see CPU Reference Information, Sec.ion 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 displar the next
summary screen; enter 0 to display the console prompt.

KA45 Firmware

3-27

KA4S 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

skxveasrsr PST EXT ERRPT
COMM Test Summary

12C0MM

0 00:01:29 **r#xkxxnx

SCreen.............ccco0veeos

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

FTY: 0006 @
STA:
SWv:
CC2:
CNT:

0001
000D
0000
0002

CHM: 0002
PROT: 0002
AHI: 0002
BPS: 5214

SEL:
SCM:
ALO:
SIZ:

0003
FOC2
4000
0008

CSR:
BWV:
cci:
MOD:

0A04
0003
0000
0001

............cccvvin..

EXP- 0000 ACT: 0000

#rwwrwessr SYSTST
NXT SCR ((* (('1'=Y), ("0'=N))......... > @

@ Summary screen identifier.

@ Test number and mnemonic.
@ The time taken to complete the test.
@ The number of the channel that is being tested as follows:
e

CH1 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.

3-28

KA4S Firmware

@ A prompt for the next summary screen—Enter 1 to display the next
summary screen; enter 0 to display the console prompt.

Figure 3-15 is an example of a summary screen for the ASYNC test that was
performed during a system exerciser test.
Figure 3-15 Summary Screen for System Exerciser ASYNC Test

wxgdkkaees FST EXT ERRPT

14ASYNC

0 00:02:02 wexswaaias

ASYNC Test Summary SCreen...............c..e.e.

ASYNC Test Status Block..........coviiivnvnnn.

FRO: 0028

CSR: 0101
EXT: 0600
anm.

&b .

STA: 00009

LPR: FF18
¥O0D: 0009

AANKN
VUUY

BPS: 000F
EXe: 0000

ACT:

0000

SYT EXT STATUS - PEMT NyT ochn > @

@ 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.

35.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 exampie of the information that this command displays.

&30

RASD cilffhvane

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

27 130

SCSI

0018

000

NVR

0003

130 000E 00000003 00120012 00180000 FFFFOOLB 06000000 00000000 FFFFFFFFr@
Une question mark (7) indicates a goft error, that is, an ervor 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 is related ts the test name {or {est number
on the line immediately preceding it). In the example, the additional error
information line is related to the SCSI test (test 10). See CPUJ Reference
Information, Chapter 3, for information about the formats and meaning of
the additional error information for the various tests.

‘

iesting and Troubleshooting
This chapter describes how to troubleshoot a MicroVAX 3100 system that uses
the KA45 CPU module. It gives information on the following:
¢

General troublesheooting information

No display on the console termins)

NVR test (test 1)

DZ test (test 3)

CACHE test (test 4)

MEM test (test 5)

FPU test (test 6)

[IT tagt (tect 7)

SYS test (test 8)

NI test (test 9)

SCSI test (test 10}

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 firmware 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.

The system runs the power-up t st and initialization automatically when you e
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, Chap:er 6).

Note the test number and mnemonic of the faiiing 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 device.

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

WNote

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 envirenment, enter the Hllowing
command at the console prompt:
>>> SET DIAGENV 2

See the CPU Reference Information, Section 1.11.3, for a list of all the test
environments. In the Digital Services environment, vou 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, vou can run the system exerciser (see Section 3.5). The system
exerciser is also useful for troubleshootin’ intermittent errors in the system.

&2 Testing and Troubleshooting

Troubleshooting

Foling

Devico

LED Display

Most Suspect

Seciion

Test

fnemonlc

lndication

FRUs

Reference

NVR

0001 xxxx !

CPU module

0011 oz

CPU module

4.4

CACHE

0100 xxxx

CPU module

4.5

MEM

0101 sxxx

MS44 or MS44L memory option

4.6

CPU module

FPU

0110 xxxx

CPU module

4.7

0111 xxxx

CPU module

4.8

SYs

1000 xxxx

CPU module

4.9

1001 xxxx

CPU module

4.10

SCsi

1010 zxxx

R22* 2 digk drive

4.11

TZ30 tape drive

4.11

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

CPU module

4.12

DHW41 or DHW42 asyn-

4.1

COMM

ASVNC

1100 xxxx

1110 zmx=

communications option

chronous communications option

CPU module

4.13

lyrex represents device-specific codes.

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

4.2 No Display on the Console Terminai
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

Troubieshooting

Flaure 4-1 Flowchart for Normal System Power-Up

The green LED on the front of the
system unit wms on. The LED display
on the back of e sysiam unit counts
down. If not, see Section 4.2.1.

%
display is ehown on the conadle
tarminal
that is oonnacied o the
gyatem unit, After 2.5 minutes, the
cisplay is compiste.
i not, sge
Saction 4.2.1.

I 1 no fatal emors are detectad during
the power-up
tast and initizlization
and tho dafault recovery action fieg
i3 88t
0 1 Or 2, T syBleTM displays

The eystem sutomatically
boots from the

dafault boot device or from the Ethemet
if the delauk boot device is nufl,

The sysiem haits automatically.

Press the halt push bution on the back
of the system unit to retum the system
o the conzale mads for (as8ng puiposes.

4.2.1 Troubleshooting Procedure for No Display on the Console
Terminal
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

é=4 Testing and Troubleshooting

Troubleshooting

when the terminel is turned on. Check the terminal setup. The correct
setup values for the terminal are as follows:
=

DEC423 operation

Tranemit = Raraive
= Q800 haud

Fight hits

One stow bit

e o
o et
No pavivy

If you do not know how to change the terminal setup, see the terminal
documentation. Turn the brightness contro! until the raster scau iz shown
on the terminal display. When the terminal does not display a raster scan,
see the terminal troubleshooting documentation.
.

Tum off the system unit. Check the position of the break/enuble switch on
the back of the system unit. The switch must be set to the riown position
bifore 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

18 in the up position before you turn on the system if you want to use the
termina! connected to MMJ port 3 as the connole device. Confirm that the
terminal does not produce a display when it is connected to either port.

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 greer: L.LED on the front of the
system unit is on and that you can hear the scund of the fans operating. If
this does not occur, follow the procedure in Suciion 4.14.

Turn off the system unit and remove the following drive-mounting panels
depending on the enclesure type:
¢

For a system in a BA42-A enclosure, remove the drive mounting panel.

See the BA42-A Enclosure Maintenance manual for more information.
¢

For a system in a BA42-B enclosurz, remove the upper and lower drive
mounting panel combination. See the BA42-B Enclosure Maintenance
manus! for more information.

Remove the logic boards of the asynchronous communications options

(DHW41 or DI{W42) and the synchronous communications options (DSW41
or DSW42) from the CPU module (if connected).

Testing and Troubleshooting

4-8

Troubleshooting

6. Femove the MS44 or MS44L memory modules from the CPU module (if e
connected).

Tuarn on the system. If the terminal produces a display, one of the
comnponents that you disconnected is causing the problem. Install the
components, one &t a time in the order you removed them and test
the svstem each time. If the terininal does not produce a display, the
component that you installed last is the cause of the problem.
v

e ehamn anex®

e
2
.
If the terminal
does not produce a display,
turn
of whe sysiem unii, replace

the CPU module, and go to step 8.
8.

Turn on the system unit. When the terminal produces a dizplay,
reagsemble ¢he gystem 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 fellowing subtests:
®

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 initialized, this test checks the temporary NVR
locations only.

TOY sublesi~—This subtest checks that the TOY clock contains a velid time
eniry. If not, this subiest checks aii TUY registers by writing and reading
values to the TOY registers.

If the test fails during a power-up test and initialization, put the system in the
Digital Services environment (see CPU Heference 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:
> 71
>>> T NVR

If the NVR test fails, the LED display on the back of the sysiem cnit
displays an error code in the range 10 to 11(hexadecimal) (see CPU Reference
Information, Table 6-2), and the coi.sole terminal displays a hard error code as
follows:
?? 001 1 NVR 0004

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

Troubleshooting

CPU Reference Injormaiion, Tabie 3-1 describes the error codes that the NVR
test produces. If chis test fails, you must repiace the CFU module.

A 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 charactsrs are not egual.

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
__ T __ 1%
- o A2
oy
—
—
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 consoie terminal connects. You must also connect a 2924795-00 loopback connector to the asynchronous modem control port

(2). The test fails if you do not instsall the loopback connectors.

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

Testing and Troubleshooting 4-7

Trauibisehanting
T U

A e -,
GT T e

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 digplays a hard error code as follows:
?? 001 3 DZ 0064

The error code, 0064(decimal) in this example, indicates that the polled test
failed. CPU Reference Information, Taeble 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
Sactisn 3.5). CPU Reference Informaiion, Seciion 5.1, gives the error 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 subtests:
e

Data store sultest—This subtest checks the date store of the primary
cache memory. The subtost 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 I/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 CACEE

4-8 Testing and Troubleshooting

Troubleshooting

if the CACEE 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:

?? 001 4 CACHE 0512

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
8-4, describes the error codes that the CACHE test produces. Te 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.0 micm 1est (1esi 9)
2

DAOTOHBR

T
o

.
o B

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 is complete, all free memory 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 ali memory locations in the reverse
direction.

Final parity subtest—This subtest fills all the memory locations with the
pattern O1h. 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.

Testing and Troubleshooting 4-9

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, erter one of the following commeads at
the console prompt:
>>»> 7T 5
»>>
T MEM

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 2 hard error code as
follows:

?? 001 5 MEM 0770

The error code, 0770(decimal) in this example, indicates that the tsst 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 prcduces. 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 oi 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 eccurs 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:
3> 7 6
>»> T FPU

4-1¢ Testing and Troubleshooting

Troubleshooting

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 follovrs:

?? 001 6 FPU 0258

The error code, 0258( lecimal) 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:
>>> SHOW ERROR

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

4.8 (T 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 sysicm. The IT test enables interval timer interrupts. If there are
too many or too faw interrupts within a 30 millisecond (ms) interval, the test
generates an error.

f 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 following commands at the console prompt:
»> T 17
>»> T IT

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 displays a hard error code
as follows:
?? 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.
Additiona! error information is not available for this test. If the IT test fails,
replace the CPU module.

Testing and Troubleshooting

4~11

BOANRG

4.9 SYS Test (Test 8)

The SYS test checks the system KOMs 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
éollows:

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.

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
>>> T S5%§

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:
?? 001 8 SYS 0128

The error code, 0128(c2cimel) 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 ERROR

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-12

Testing and Troubleshooting

‘

Troubleshooting

N! Test (Tast 2)
The NI test checks the network interconnection circuitry on the gsystem moduie.
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 foliows:
¢

Network address ROM subtest—This subtest checks the 32-byte network
address ROM, which centains 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.

LANCE interral loopback 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
uperations 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 dotection during data reception in
internal loopback mode.

LANCE receive MISS/BUFF subtest—This subtest checks the LANCE
circuits for any missed dats packets and buffer errors during a data
reception in internal leopback mode.

LANCE collision subtest—This subtest verifies a collision detection and
retry cctivity duving a data transmission in ¢t~ e internal loopback mode.

LANCE address filtering subtest—This subtest checks the LANCE receiver
address filtering for the broadcast, promiscuous, and null destinations in
the internzl loopback mode.

Testing and Troubleshooting

4-13

If the NI 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 NI test as an individual self-test.
Note

When the network select switch is set for a ThinWire Ethernet
operation, the NI test generates an error if you do not connect the
system to a ThinWire Ethernet network or install the ThinWire
Ethernet T-connector and terminators.

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).

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

>>> T ¢

>>> T N1

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:
27 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, Tab'e 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, ané 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
gystem fails the NI test, replace the CPU module.

4-14 Testing and Troubleshooting

Troubleshooting

To troubleshoot intermittent failures, you can run the gystem exerciser (see
Section 3.5). The system exerciser rurs this test when testing the interaction
of components in the system. CPU Reference Information, Section 5.2, gives
the error messages that the sysiem exerciser produces for this tesr. 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 che system. The
SCSI test performs three subtests as follows:
o

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

are fully operational.

register, the interrupt requesi 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 controlier 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 izzues four inguiry commands to cach 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

Synchronous mode with DMA

waes wasa

boundary and crossing a page boundary

If the 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 SCSI {est as an individual self-test.

To vun the SCSI test as an individual self-test, enter one of the following
comiv.ands at the console prompt:
> T 10
>>> T 8CSI

Troubleshooting

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

dispiays an error code in the range A0 to A5(hexadecimal) (see CPU Reference
Information, Tuble 6-8), and the console terminal displays a hard error code as
follows:

?? 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 faiis,
the problem may be the CPU module or one of the SCSI devices connected to
the SCSI bus.

Note

In thz 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 sysiem, check the foiiowing:
e

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

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

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

At WoF

When you are sure that ail the 3CSI 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.

4-16 Testing and Troubleshonting

Troubleshesting

Run the SC31 test again. When the test passes, the fauit is in one of the
gxtemal uevices 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 or the
connection to the CPU module is faulty. If 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 preduces. 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.
Teble 4-2 SCSI Device Troubleshooting Procedures
SCSi Device Type

Section

RRD42 CDROM drive

4.11.1

RX26 diskette drive

4112

RZ23L, RZ24, RZ25 disk drives

4.11.3

TZ30 tape drive

4.11.4

TZK10 tape drive

41156

External SCS] devices

4116

To perform a more comprehensive test on the SCSI devices, put the system in
the Digiial 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 {(gee Section 3.5.1).

Select the SCSI device that 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:
27 10

SCSI

150

0160

8:18:41

Testing and Troubleshooting

8-17

Troubleshooting

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
syatem exerciser nroduces 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 SUSI device is fauity. Replace the
faulty SCSI device.

2.11.1 Troublsshootling an RRD42 COROM Drive
The RRD42 CDROM drive is a single ¥RU. 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 3A42-A Enclosure Maintenance or the
BA42-B Enclosure Maintenance manual for information about removing and
it DDRTY,

fipl“fiu% & AU e

4.11.2 Troubleshooting an RX26 Diskette Drive
When the STSI 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. SCSUFDI board (54-20764-02)
2.

RX26 diskette drive unit (RX26-AA)

RX26 ribbon cable (17-00285-00)

To identify the fauity FRU, replace each FRU in turn, in the order shown
previously, and run the SC5I test (test 10) again until the test passes. See the
BA42-A Enclosure Mainter.ance or the BA42-B Enclosure Maintenance manual
for information about removing and replacing FRUs. The last FRU that you
replace is the faulty FRU.

4.11.3 Troubieshooiing an RZ2Z3L, an RZ24, or an RZ25 Disk Drive
o

=
.

The RZ23L, R224, and RZ225 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-A Enclosure Maintenance or the
BA42-B Enclosure Maintengnce manual for information about removing and
replacing FRUs.

418 Testing and Trouhlechogting

Troubleshooting

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:
1\

aa
Taks-up
leaderS (74-34273-0%)

TZ30 tape drive unit (TZ30-AX)

manliter BWETY
34 h& b f

tnvamand dha I-Alonaem landne fawm damwan

SHIELY WIS Lmaivy & %W/, AIDTR.W WIG

ot
.

U ICERAGY AUE unnln\ge ll umauurv.

replace the take-up leader according to the instructions in the TZ30 Cartridge
Tope Drive Service manual (EK-OTZ30-SV). If the take-up leaderis not
damaged or incorrectly aligned, replace the TZ30 tape drive. See the DA42-A
Enclosure Mairtenance or the BA42-B Enclosure RMaintengnce 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) isoiates
the fault to & TZK10 tape drive, you must replace the TZK10 tape drive

(TZK10-AA). See the BA42-A Enclosure Maintenance or the BA42-B Enclosure

Maintenance manual for information about removing and replacing the FRUs.

4.91.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

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

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 programmabie rzad-only

wamory (ROM).

performed inciude write, verify, compiement, verify.

memory (EPROM) dual access.

Testing and Troubleshooting

4-19

Subtest §—~This subtest checks that the synchronous communications
optiss: can interrupt the system CPU.

Subtest 7—This subtest checks the host buffer leopback and interrupt.
option. returns it, and waits for en interrupt,

Subisst 5—This sublesi reseis the synchronous communications option and
waits for an interrupt.

If the COMM test fails dunig the power-up test and initialization, follow these
etana:
Al o
s
o

2.
3.

Disconnect all the external cables from the synchronous communications
A
AL o oA
e
S
ports- on
the-~ back
of the sysiem unit.

P .8

Put the system in the Digital Services environment (see CPU Reference

Informaiion, Section 1.11.3).

Run the COMM tast az an individus) eslf.tast
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.

Te run the COMM test ss an individual self-test, enter one of the following
commands at the console prompt:
o3> 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 CO to C8(hexadecimal) (see CPLY Reference
Information, Table 6-8), and the conssle terminal displays a hard error code as
&

AWGFTY G
T

follows:
?? 020 12 ComMt 0274

The error code, 0274(decimal) in this example, indicates that the svachronous
communications option diagnostic test did not complete. CPL Reference
Information, Table 3-15 describes the error codes that the COMM test
produces. To get more information about the error, enter the command:
>>> SEOW ERROR

520

Testing and Troubleshooting

5 &

CPU Reference quormat:on, Section 3.10.2, gives the format and describes
the additiens! srvov information that the COMM test produces. The -"s
exerciser runs this test when testing theinteraction of compenentsin the

system. CPU Referenceinjormation, aecuon 5.4, gives the error messages that
the system exerciser produces for this test. See Sectmn 4.12.1 to identify the
fauity FRU.

Troubleshooting a DSW41 or a DSW42 Synchronous
Communications Option

The DSW41 and DSW42 synchronous communications options contain the
following FRUs:

Input/output module

Logic board

Ribbon cable

External cables

Tidentify the faulty FRU, run the COMM test (test 12) repeatedly as an
mdmdual self-test, replacing the FRUs one at a time in the order shown
previcusly, until you find the faulty FRU.

To check the externsal cables, you can connect cable leopback connectors and
run the test again. The external cable loopback connectors that you must
connect depend on the commumeahons interface you are using. Figure 4-2
shows the }@Gfi'fi&un connectors for the different communications interfaces that
the DSW41 and DSW42 synchronous communications options support.

Testing and Troubleshooting

4-21

Figure 4-2 Cable Loopback Connectors for the DSW41 and DSW42 Options &
Modsi30

Systam Unit

=
H3198

Synchronous
Conmrunications

Port O

—
_—

Calslo Loopback
Extomnal Ceble

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

por 1.
connacions 10 synchronous conevunications

4-22 Testing and Troubleshooting

H3248 for EIA-232/V.24
H3188 for EIA-423/V.10
H3188 for EIA-422/V.11

Troubleshooting

4.13 ASYNC Test (Test 14)
The ASYNC test checks the operation of the asynchronous communieations
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, foliow these
steps:

2.
3.

Disconnect all the external eables from the asynchronous communications
ports, which the option provides on the back of the system unit.

Put the system in the Digital Services environment (see CPU Reference

Information, Section 1.11.3).

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

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 a system has one four-channel modem control port, connect a
H4081-A loopback connector.
If a gystem 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 ASYNC

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

Testing and Troubleshooting

4-23

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:
>>> SBOW 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 eommand to get more information about
the error. The additional error information indicates which asynchronous
communications channel is faulty. See Section 4.13.1 to identify the faulty
FRU.

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.

4.13.1 Troubleshooting a DHW41 or @ DHWA42 Asynchronous
Communications Option

Input/output module

ol
S

The Driw4l and DE W42 asynchronous communications options contain the
following FRUs:

Logic board

Ribbon cable

Harmonicas (DHW41-AA, DHW42-AA, DHW42-BA)

External cables

To isolate the fault to an FRU, run the ASYNC test (test 14) repeatedly as

an individuel self-test, replacing the FRUs, one at a time in the order shown
previcusly, until you find the fauity 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 or modem controi)
that you are using. Figure 4-3 shows the loopback connectors for the
different communication types that the DHW41 and DHW42 asynchronous
communications options support. Use Digital Services procedures to
troubleshoot the operation of the harmonicas or the 4-way modem cables.

4-24 Testing and Troubleshooting

Troubleshooting

igure 4-3 Cable Loopback Connectors for the DHW41 and DHW42 Options
Model
3

Systam Loopback
.
a
only port
H3101 for gight~dat
H4081-A
oy tour-modam contral port

#3104 Harmonica

Usa Dighal Services procedunes
t

m troubleghoot extermnal cables

Btama) Ceble

17-01174-01 for sight-data only post

Cable Loophark

H3101

Exiamal Cabls

17-02841-01 for fowr-modam control pont

:I goubmshoot cxicrnal cabliss

Noto: For Mods! 40 gysiems, you musl 820 connet! extamal cablss and loopback
connecions © ayrchioncus communicstions pon B.

4.14 Troubleshooting Procedures for the Power Supply
Figure 44 is a flowchart for troubleshooting the power supply in a KA45
system.

Testing and Troubleshooting 4-28

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 KA45
CPU module.

&-26 Testing and Troubleshooting

Troubleshooting

Figure 4-5 KAA4S CPU Module Power Connector Pin Voltages
+51vVde

+5.1Vde

» Ground

V de Retum -8.0

~-121Vde

-80Vde

Figure 4-6 shows the voltages on the pins of the connectors on the power
cables that provide power to the internal mass storage devices. See the BA42-A
Enclosure Maintenance manuzl or the BA42-B Enclosure Maintenance manual
for more information on power distribution.
Figure 4-6

Drive Power Connector Pin Voltages

+5.1 V dc (Red Cable)
Ground (Black Cable)
Ground (Black Cable)
+12.1 V de (Crange Cable)

Testing and Troubleshooting

4-27

P LIy
RFRP LRI UFRY WP
0944
0 64 8h
8000
£
G DA SR D I O S RATI RN FiS b FALB AT R IR IR FS

Troubleshooting Flowchart
This appendix shows a flowchart of the procedure used to troubleshoot KA45
gystems.

Troubisshosting Fiowchat

Troubleshooting Flowchart

Flaure A-1

Troublashooting Flowchart (Page 1 of 4)

CPU Wirdute

Put the syatem inthe

Enter tha SHOW
MEM
command
to dalerming

which
MS44 memory

by the gystem

j.0110 XXXX |

FPUTest

(Tesi 6) > Fal

Rapiaoo the
CPU Module

' This sssumes thet the conscle terminal is connacied to M4 pon 0.

a=h

A-2 Troubleshooting Fiowchan

option
is taulty

Repizns
the tauky

1544 momory module
orthe
CPU motiula

trgubleshoating Fiowohant

Figure A-2 Ticulleshooting Flowchari (Page 2 of 4)

Chack
the Ethemat

swilch position.

|| Disconneat the network

cabis and connect the

ThinWire eminators or

standiand loopbaci.

/M\
M Tem

Raplace the

(Tes®) L Fai CPU Module

Pazs
Network taul;

880 thy network
co-ordinglor

Troubleshooting Flowchant

A-3

Troubleshosting Flowechant

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

LED Osptsy

L1010 00 | | Ermer SHOW DEVICE
or SHOW CONFIG

t 0 EheCkK thas the

Facontame e
Deviczs

unikes
Have
poivine
g

A& Troubleshooting Flowchan

No | sCsits end
run the power—up
iS5 agan.

Troubleshooting Flowchart

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

Te2t12) .~ fad
Pasa

Disconnedt exiamel cables and connadt lbopbadis
(M3198) 10 synchronous
ports O and 1.

Run

COMM Test

Peas | Exemal communications

lsoietas titio

| Repiacthee

(Veat 12)

davics g causing S problam

CPLiAfodule

! For data only pots use HI101.

For modem contrel pune use HeDBI-A

Troubleshaoting Flowchan

A-8

AAARNAARARDLRR R R
o

GBS

Memory Map
Table B-1 is a memory map for MicroVAX 3100 systems that have a KA45
CPU module (Model 30 and Model 40 systems).
Table B-1

Memory Map

temory (M Bytes)

Address Range

Memory Component

00000000 to 003FFFFF

System module

00400000 to 007TFFFFF

System module

00800000 to COBFFFFF

1st!

00C00000 to 0OFFFFFF

1st

01000000 to 01SFFFFF

2nd?

01400000 to 017TFFFFF

2nd

01800000 to 01BFFFFF

3rd®

01C00000 to C1FPFFPRE

ard

V18t indicates the first memory increment (connectors 1H and 1L; see Figure B-1).

“2nd indicates the second memory increment (connectors 2H and 2L; see Figure B-1).
33rd indicates the third memory increment (connectors 3H and 3L; see Figure B-1).

Memory wiap

-1

sre

|-*-

B-1

RMemarv Connastara
verwes e 3

2L 3L

91
RE_ENG5108A_

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
T oma sl
indicates that the memory module in connecior 1L, ZL, or 3L is fauity.

8-2 Memory Map

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

Definition

(Decimal)
001

CPU module

020

Synchronsus commmunicatione module DSW41 or DSW42

021

Asynchronous communications module DHW41 or DHW42

041

Memory madulein connector 1H

042

Memery modulein connector 2L

043

Memory medule in connactor 2H

Memory module in connector 3L

045

Memory module in connector 3H

160-199

8C8I devices (zee Section C.1.1)

FRU Numbers

C-1

C.1.1 FRU Numbers of SCSi

Devicas

The FRU numbers of SCSI devices have the following format:
£1Eg Xy

where:
@

x1 is the SCSI controller number. This number is always 1 because there
is only one SCSI controller in the system.

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

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

C-2 FRU Numbers

mmwwwmw

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

KA45 CPU Module Jumper Wires

D-1

Wi3

Nommaly ot for

IEEE 802.3 compllance.

W <~

NanTgly out, even inateiied it

W21

R
3

SO osciianr
power enable;
st be fitled foy norva)

0-2 KA45 CPU Module Jumper Wires

T 4 5 BE e VB dw on Zu e

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

American standard code for information interchange.
CMOS
Complementary metal oxide semniconductor.
CPY

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 technigues to

identify characters by automatic means.
&1

Control status register. A register used to control the operation of a device and
record the status of an nperation o= 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 is a type of read-only
memory that can be erased and so returns the device to a blank state.
FPU

Floating-point unit. A umt that handles the automatic positioning of the
decimal point during arithmetic operations.
Glossery-1

FRU

Field-replaceable unit.
iT

Interval timer.
LED

Light emitting diode.
AR

Modified 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

functionality.

SCSI

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

(AN3I) standard.

§GC

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

TOV

Time of year.
viie

Virtual machine bootstrap. The VMB program loads and runs the eperating
gystem.

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

@R m&Wwfi:“flnflfi‘““fl-mn Gy D y

Index
Console devices (cont’d)

A
ASYNC test, 4-23
Asynchronous communications device
interfaces support for, 2-5
troubleshooting, 4-24
Asynchronous communications devices
testing, 4-23
Asynchronous communications options
list of, 2-5

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

Cache memory test, 4-8
CACHE test, 4-8
3-8

C~uamunications option types,

2—4

Configuration
memory, 1-8
Conuectors
function of, 1-7

identification of, 1-5
Console commands
overview of, 3-6
Consnle devices
communication parameters,

function of, 3-4

Controls

function of, 1-7
identification of, 1-5
Customer enivironment, 3-15

C
Clearing the password,
COMM test, 4-19

types of, 3-5
Console mode, 3-%
privileged, 3-7
unprivileged, 3-7
Console port, 3-4
Console program
function of, 3-4
Console security, 3-7

Device mnemonics
list of, 3-11
Device names
Hat of, 2-11
Device numbers
list of, 3-11
DHW41
troubleshooting, 4-24
Diagnostic test environment
gotting, 3-156
Diegnoctic tests, 3-11
Digital Services test environment, 3-i5
logpback requirement, 3-15
DSW41
troubleshooting, 4-21

DSW42
3-8

troublezhooting,

4-21, 4-24

DZ szerial line controller test,

4-7

inden-1

D2 test, 4-7

Manufacturing test environment, 3-16
loopback requirement, 3-16
Mass storage devices, 2-1
external, 2-2
internal, 2-1
SCSI ID assignments, 2-4
MEM test, 4-9
Memory
configurations, 1-10
expansion connector identification, 1-8
expansion of, 1-8
map, o-1
rules for adding, 1-8
Memary configuration
KA45 system, 2-1
Memory modules, 1-8
Memory option
installation of, 1-10
Memory test, 49
Miscellaneous system test, 4-12
Modem communications, 4-7, 4-23
Modes
for diagnostic tests, 3-156
AECE 2
PR,
T, P
]
fodd InanoY w
i u}“ i-6

Environment
testing,

3-16

Evror information, 3-14, 3-29
Ethernet circuit test, 4-13
Eutended self-test, 3-16
External mass storage devices, 2-2
list
of, 2-3

F
Firmware overview, 3-1
Floating-point unit test, 4-10
FPU test, 4-10
FRUs
numbers for, C-1

i
Halt state, 3-4

Indicators
function of, 1-7
identification of, 1-8
Initialization, 3-1
Intornal mass storage devices
iist of, 2-1
Interval timer
See IT, 4-11
IT test, 4-11

MS44L prittrivry JvileGl
ulés, i-0

N
N1 test, 4-13
Nonvolatile RAM
See NVR, 4-86
NVR

clearing the password, 3-8
NVR test, 4-6

K
KA4b CPU module
block diagram of,
features of, 1-1

)

1-3

Onboard memory

KA4S5 system
communications options,

location of,

2-4

configmanons of, 2-1
storage device configurations,

mmm’y mnfiguratmns, 2-1

2-1

1-8

Synchronous communications options
list of, 2-5

Synchrenous communications standards

Pagsword

support for,

clearing, 3-8
Do

System exerciser

EUT

function of,

2-6

SYS test, 4-12

1-7

identification of, 1-5
Power supply
troubleshooting, ¢-25
Power-up test, 3-1
display format, 3-1
error format, 3-3
Privileged console mode, 3-7

RRD42
troubleshooting, 4-18

display format, 3-21
error format, 3-22
overview of, 3-19

predefined tests, 3-19
TEST command format, 3-19
test results, 3-24
System initialization, 3-1
System test kernel
function of, 3-19
System test monitor
function of, 3-19

troubleshooting, 4-18

TEST command

RZ23L
troubleshooting, 4-18
RZ24

rules, 3-12
variations of, 3-11
Test command dispatcher

troubleghooting, 4-18

function of, 3-11
TEST command lines
typical examples, 3-11

RZ25
troubleshooting, 4-18

Test envirenments
customer environment, 3-15

S
SC8I ID assionmanis
recommendations for,

2-4

SCSI test, 4-15
Security,

3-7

Self-test
display format, 3-13
error format, 3-13
overview of, 3-11

Serial line controller test, 4-7
Status bar
complete,

3-1

Synchronous communications device testing,
4~19

Synchronous communications devices
troubleshooting,

4-21

Digital Services er.vironment, 3-15
list of, 3-15
Test results
for system exerciser, 3-24
Troubleshooting

asynchronous communications devices,
4-24

DHW41, 4-24
DHW42, 4-24
DSW41, ¢-21
DsW4z, 4-21
external SCSI devices, 4-19
flowchart, A-1
general procedures, 4-1
no ecreen display, 4-3

RRD42, ¢-18

indox-3

U
Unprivileged console mode, 3-7
Utilities
error format, 3-16
overview of,

3-16

TEST command format, 3-16

A
VAX data types

support of, 1-5
VAX instructions
support of, 1-5