Digital PDFs

EK-329AB-MG-002

May 2000

238 pages

Original

14MB

view download

OCR Version

9.9MB

view download

Document:	KN210 CPU Module Set System Maintenance
Order Number:	EK-329AB-MG
Revision:	002
Pages:	238
Original Filename:

OCR Text

KN210 CPU Module Set
System Maintenance
Order Number EK-329AB-MG-002

digital equipment corporation
maynard, massachusetis

Firet Printing, July 188D
Rovised, Decambay 138D
The informeation in this decument is enbject to change without notios and should not be
construed 2o e esmmitmept by Digital Equipment Corporation.
Digital Equipment Corporation sssumes o regpangl® lity for any errors that may appsar in
this decument.

Any software described in this document is furnished under & license and may be used or
copisd only in accordance with the terms of such license. No responsibility
is essurmed for
the use or reliability of seftware or equipment that ip mot supplied by Digital Equipmaent
Corporation or its affiliated companies.
Restricta? Righta: Use, duplication, or distlosure by the U.8. Government is subject to
restrictions as st forth in subparagraph (eX{1)ii) of the Rights in Technical Data and Computer
Software clauze at DFARS 252 .227-7013.

® Digital Equipment Corporation 1888

All nghte reserved. Printed in U.S. A
The Reader's Commants form at the end of this document requests your critical evaluation to
essist in preparing future documentation.

The following are trademarks of Digital Equipment Corporation:

COMPACTape
DDCuP
DEC
DECmaste
DECuaast
DECesrver
DECoyster 5400
DECUS
DECwriter
DELN]
DEIRQA
DEGQNA
DESTA

DIBOL
DSS8]
MASSBUS
MieroVAX

PDP
PrOS
Professiana)
Q-bus
Raintaw
RsGIS
RQDX
RSTS
RSX

RT
ThinWire
ULTRIX
UNIBUS
VAX
VAXcluster
VAX DOCUMENT
VARELN
VAXleb

#FCC NOTICE: The equipment describad in this manual generates, uses, and may emit radio
frequaney energy. The equipment has been type tested and found to comply with the limits for

a Class A computing device pursuant to SubpartJ of Part 16 of FCC Rules, which are designed
to provide reasonable protection against such radio frequency intesference when operated in
& commarcial environment. Operation of this equipment in 2 regidential arez may cause
interference,
in which cage the user at his own expense may be required to take measures to
correct the interferencs.

$1329

Thig documsnt was prepared using VAX DOCUMENT, Vereion 1.2.

Contents
Preface

Chapter 1

KN210 CPU and Memory Subsystem

1.1

KN2I00verview ............ccc0tiieenncannansenens

1-1

KN210Features.................cceeverrnnnoosanses

1-7

1.2.1

RICOORISC Processor . .........c.cc0veeinnnanrnnnsn

1-8

1.22

Floating-Point Accelerator .........................

1-8

123

Cache Memory ...........ciiiiiirininennneeannnn

1-8

124

MemoryController.............
... ... ..o ia.t.

1-9

125

ConeoleSemalline ................
it iinnnn..

1-9

1.2.6

Time-of-Year Clockand Timers .....................

1-9

1.2.7

Boot and Diagnostic Facility .......................

i.2.8

Q22-busInterface. . ..........
... ittt

1-10

129

CVAX DiagnosticProcessor ...................
0000

1--10

1210

NetworkInterface .............
...
iiirier.es

1-11

12,11

Mases StorageInterface

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

1-11

1.3

H3602-ABCPUI/OPanel .................ciivvnen..

1-12

MS650-BAMemory .......c.oiiiiiiiinerinnnnennnnns

1-15

Chapter 2

Configuration

Introduction .............
... iiiiiriniroenannonnns

2-1

General ModuleOrder ..............
...
iiiiinnn.

2-1

2.3

Module Order for KN210 Systems ................0unn.

2-2

ModuleConfiguration. ... ..........i0iiiiinnnconnas

2-2

DSSIConfiguration ..............
i iiiritirnernnn

2-4

25.1

ChangingtheNodeName .........................

2-6

2562

ChangingtheUnit Number ........................

2-6

253

DSSICabling.......c.viieriinienenaiannannasans

2-8

... ... 2-11
Configuration Worksheet ... ... ................

Chapter 3

KN210 Firmware

3.1
32

Introduction ... ... .. ... . ...
KN210 Firmware Features .. ... ...... ... ...........

3-1
3-2

3.3

CVAX Halt Entry and Dispaich Code. ... ... ... ... ... ...

Power-Up.......
.. i
Power-Up Sequence: Operation Switch Set to Normal....
341
Power-Up Sequence: Operation Switch Set to Maintenance
342
34.3
Operation Switch Set to Action: Loopback Tests ... ... ..
Operation Switch Set to Action: Languege Query . ... ...
344

3-6
3-6

36
Bootstrap ...........
... ..
356.1
ULTRIX-32 Bootstrap . ...........
...
v,
3.56.2
MDM Bootstrap . . ............. ..
..
MDMRestart . .. ... ... ... ...
3563
Normal ModeOverview .. ... ... . ... ... ... . .cc......
36
3.6.1
Control Characters in Normal Mode . ... .............
362
Environment Variables in Normal Mode . . ............
Normal ModeCommands............................
37
... ......
Conventions Used in This Section . . ... .....
3.7.1
i
GettingHelp ... ... ... ... ...
3.72
3.73
bBoOt ...e
CONBIMIUE . . . . . ottt e
3.74
ddeposit) .. ... ... ...
3.7.6
dump ... ...
376
@ {eXBMING) . . . . .
3.9.7

3-8
39
3-10
3-14
3-16

3.78
o| I R
B0 . i e
3.79
3710 help ... ... ..
OO
K T 2% 5 N
InEt . ..
3.7.12
printenv. ... ... ...
3713
BelenV. .. .. e
8714
e
UNBEtBNIV . . . . e
3715
Maintenance ModeOverview . . . ... ... ... ... ... ... ..
38

3-28
3-29
3-3¢
3-31
332
3-33
3-34
336
3-36

3-6
3-6
37

3-15
3-16
3-17
3-19
3-19

3-20
3-23
3-24
3-26
3-27

38.1

Command Syntax in Maintenance Mode . ..........
...

3-37

382

Address Specifiers in Maintenance Mode . . .. ..........

337

3.83

Symbolic Addresses in Maintenance Mode . . . . ... ... ...

3-38

3.8.4

Command Qualifiers in Maintenance Mode .. ... .......

3-41

386

Maintenance Mode Command Keywords . . ............

3-43

Maintenance Mode Commands .......................

3-4b6

391

BOOT . ... ...

3456

382

CONFIGURE ............
.. .
i

3-46

393

CONTINUE .........0
.
it

3-48

394

DEPOSIT ....... ...

3-49

3956

EXAMINE ... ... ... . . e

3-60

396

EXIT .....

3-62

397

FIND ...

398

HALT . ... o

3-54

399

HELP......

... . . e

3-66

39.10

INITIALIZE . .. ... ... e

3-67

3911

MOVE . ... . . . . e

3-59

39.12

NEXT . ...

. . .
e

3-51

3813

REPEBAT.........

.. .0, R

3-63

3914

SEARCH ......

... . . .
e

3-64

38.16

SET . ...

3-66

3916

SHOW . ... . . . . . . e
e

3-69

39.17

START . ... . . . e
e

3-73

39.18

TEST ...... .

3-74

3919

UNJAM ..... ... ... . . . ... e

...

315

3920

X—BinaryloadandUnload ............
... .........

3-76

3921

!(Comment)..........
... . .. .. .. ... .. ...,

3-78

Chapter 4

... . . e

...

3-563

Troublashooting and Diagnostics

Imtroduction ............
... . ... . .. ...

4-1

GeneralProcedures ................................

4-1

4.3

KN210 CVAX ROM-Based Diagnostics. . ... .............

4-3

431

DiegnosticTests..............
... ... . ... .cioin..

432

Scripts ... ... ...
e

4-7

433

Script CallingSequence . . . ........................

4-9

434

CreatingSeriptsa.............
... ... ... ... . ...

4-11

4.3.5

Console Diaplays . . .. ..... ...

... ..

4-15

436

System Halt Messages . . ... ... ....................

4-27

4.3.7

Console Brror Messages . . . ... .....................

4-28

438

VMB Error Messages (CVAX). . . ....................

4-29

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

AcceptanceTesting . .. ....... ... ...

...

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

4-30

Troubleshooting .............
... ... ... .. ... . ... ....

4-37

4.6.1

FEUtlity. . .......

... i

4-37

45.2

Isolating Memory Failures . . . ... ...................

440

46.3

Additional Troubleshooting Suggestions . . . . . . ... ......

4-43

LoopbackTests..............
... ... .. .. .. .. .. . ...

444

46.1

DSSIProblems . . ......... ...

...

444

462

Ethernet Problems . . . . ....... ... ... ...............

4-44

46.3

Testing the Console Port .. . . . .....................

4-46

ModuleSelf-Tests..........
... ... ... . ... ... ....

4-45

4.8

RF-Series ISE Troubleshooting and Diagnostics

. .........

446

48.1

DRVIST . . ... e

448

482

DRVEXR ....... ...

4-49

483

HISTRY .. ...

484

ERASE . ... ..

4856

PARAMS .. ...

...

... ... . ...

.. .. . . . e,

. .

4-60
4-651

.. ... ..

4-52

48.5.1

EXIT ... . e
e

4-53

4.8.5.2

HELP . ...

4-53

48563

SET ... e

4-63

4854

SHOW .. ...

4-54

48556

STATUS . . . . e

4-64

4.8.5.6

WRITE . . ...

4-54

486

DiegnosticErrorCodes ... ........................

Appendix A

4-56

ULTRIX-32 Exerciser and Uerf Command

Summary
Al

Online ULTRIX Exerciser ...........................

A-1

A1l

Communications Exerciser {Asynchronous Serial Lines) ..

A-2

Al2

DiskExerciser ......... ...... . . ... . ...

A13

[FileSystem Exerciser .. ... .......................

A-4

Ald

LinePrinterExerciser ........... .00,

AlS5

MemoryEzerciser ..............c0itiiiiiiinennn

A-b

Al6

MagtapeExzerciser .................
i iiiiii,
TCP/IPNetworkEgerciser .........................

A-6
A-7

Al17
A2
UedErrorlogCommands...........................

Appendix B

A-8

KN210 Address Assignments
B-1

Accessing Physical Locations (R3000) ..................
B.1
B2
KN210CPUModule...........cooiiiiiiiiiiininenns
B.2.1
R3000 Physizal Address Space Map (M7636-AA) .......
B.2.2
KN210 Diagnostic Processor Physical Address Space Map

B-3
B-3

B.2.3

Diagnostic Processor Registers. .....................

B-8

B.2.4

Global @22-bus Memory Space Map.................. B-10

M7635—AA) .. ....coii

ittt inianesnnroncnnnans

KN2I0VOModule............ciiiiiiiiiriinnnnnnnn

B-11

B.3.1

R3000 Physical 'O Address Space Map (M7636-AA) ....

B-11

B.3.2

Diagnostic Physical I/O Address Space Map (M7636-AA) . B-12

Appendix C
Cl
C.2

_Configuring the KFQSA

KFQSAOVerview ..........covvevneeecronssnnonnnss
Configuring the KFQSA at Installation .................

C-1
C-2

C.2.1
Entering Maintenance Mode .......................
C4
C.2.2
Displaying Current Addresges ......................
C-5
C.2.3
Running the Configure Utility . .....................
C-6
C.3
Programmingthe KFQSA .............. ...t
C-8
C.4
Reprogrammingthe KFQSA .....................
... C-13
C.6
Changing the ISE Unit Number ...................... C-16

Appendix D

Field Replaceable Units (FRUs)

Appendix E

directory

Task Name?
Copyright

PARAMS>

PARAMS
1988

SHO

Equipment

Current

URNITNUM

1
SHO

FORCEUNI

Parameter
DR
R
D
D

Corporation

UNITNUM

Paramster

PARAMS>

Digital

Current
e

FORCEUNI

Default

Type
-

PARAMS>

SET

UNITNUM

PARAMS>

SET

FORCEUNI

PARRMS> WRITE

'This
'to

command writes

the

Radix
=

Boolean

the

-—-

0/1

changes

EEPROM.

PARAMS> EX

Exiting...
Task Name?

Example 2-2 Cont’d on next page

Configuration

2-7

Example 2-2 (Cont.):

Changing a DSSI Unit Number

server...

Stopping DUP
>

>>>

SHOW

DSSI

Node

-DIAO

DSSI

(MDC)

-rf£(0,0,%)

Node

-DIA14
DSSI

DSSI

(RF71)

(R3QJNE)

-rf(l1,14,%)

Node

(RF71)

'The unit number has changed
'and the node

ID remains at

(*)

2.5.3 DSSI Cabling
A 50-conductor, multiconnector ribbon cable connects the RF71 ISE to the
DSSI bus (Figure 2-1). A separate 5-conductor cable carries +6 Vdc and
+12 Vdc to the ISE from the enclosure power supply.

A 10-conductor cable connects the ISE to the operator control panel (OCP,
Figure 2-2). In the BA213 enclosure, there are two cables that connect the
power supplies to the ISEs:

QOne cable connects the ISEs to the power supply located on the right
side, which supplies power to the two right-side mass storage devices.

One cable connects the ISEs to the power supply located on the left
side, which supplies power to the two left-side mass storage devices.

These cables carry the ACOK signal (same as POK) to each ISE. The OCP
delays this signal to one ISE for each power supply to stagger the start-up of
one of two possible devices attached to each supply. This delay prevents the
ISEs from drawing excessive current from the power supplies at power-up.
The 50-conductor, multiconnector DSSI ribbon cable connects to a 50conductor round cable that is routed through the bottom of the mass storage
area to the DSSI connector on the KN210 I/O module.

CAUTION: When removing or installing new ISEs, be sure to connect the

rightmost connector of the DSSI multiconnector ribbon cable to the round
cable coming from the KN210 I/0 module. Do not “T” the bus by connecting
the round connector to any of the ribbon cable’s center connectors.

2-8

KN210 CPU Modu!e Set System Maintsnance

Flgure 2-1:

DSSI Cabling, BA213 Enclosure

7l
5

|
.

From Power

Supply to

Supply to
RF Seres ISE

, RF Sernes ISE

ToRF2

DSS!
Cable
To RF3

torr2

)

(]

AC OK Signal
Staggers

Power Up
DSSI Bus

‘

Termination

‘

From

}i :
:

Backp'ane

(A.

J’&

Power

Supply

~ 10 I3E

DSSi

g Cable
KN210 DSSI

Connector

MO Ry,

Configuration

2-9

Flgure 2-2:

wF-Series OCP
To POK Lead
Right Power

Yo POK Lead
Lett Power

10-Pin to

Backplane

Supply

Drive Select

[ ]

‘

A
y

Dnve Faults
{Red)

Write-Protect

{7}

Buttons

Ready Buttons

Sysiem DC OK

(Green)

10-Pin

to AF2

c:&_ —_
o

jl S

Restart

2-10

CPU Hatt

KN210 CPU Module Set System Maintenance

ML 0D

The DSSI bus has 2 maximum length of 6 m (19.8 ft), including internal
and external cabling. The DSSI bus must be terminated at both ends. The
KN210 /O module terminates the DSSI bus at one end. A 50-pin Honda
terminator on the left side of the media faceplate terminates the bus at the
other end. This terminator can be removed if you need to expand the bus.

2.6 Configuration Worksheet
This section provides a configuration worksheet for the BA213 system
enclosure (Figure 2-3). Use the worksheet to make sure the configuration
does not oxceed the system's limits for expansion space, I/O gpace, and
power.

Table 2-3 lists power values for supported devices.
configuration, follow these steps:

To check a system

List all the devices already installed in the system.

List all the devices ycu plan to install in the system.

Fill in the information for each device, using the data listed in
Table 2-3.

Add up the columns. Make sure the totals are within the limits for the

Using the procedure described in Section 2.4, confirm CSR address and
vectors for all modules installed in the backpiane.

enclosure.

In the BA213 enclosure, you must install a quad-height load module

(M9060-YA) in one of backplane slots 7 through 12 if the continuous

minimum current drawn on the second power supply is less than 6 amperes.
If the minimum current of 5 amperes is not reached, the power supply
enters an error mode and shuts down the system.

Configuration

2-11

Table 2-3:

Power and Bus Loads for KN210 Options
Current

(Ampe)

Power

Bus Loads

Option

Module

+6VY

+12V

Watte

CXA16-AA/-AF

M3118-YA

0.20

10.4

3.0

0.6

CXBl6-AA/-AF

M3118-YB

0.0

10.0

3.0

0.6

CXY08-AA/-AF

M3119-YA

1.64

0.386

12.94

3.0

0.6

24
543

0.2
0.69

14.6
35.4

33
3.9

0.5
1.0

DELQA-SA

M7516-FA

2.7

KDAS0-Q
KDAS0-Q
KFQSA-SA
KLESI-S8A
KN210-AA

M7164
M7165
MT763
M7i40-PA
M7636-AA

6.83
6.67
5.6
4.0
45

0.0
0.03
0.0
0.0
0.13

346
33.21
276
200
24.0

30
4.4
5.0
3.5

0.5
0.6
1.0
1.0

KN210-AA

M7636-AA

6.0

0.23

27.8

0.0

LPV11-8A
MO060-YA

Me08s-PA
-

238
63

0.0
0.0

14.0
26.6

18
0.0

0.5
0.0

DESQA-SA
DSVii-8SA

M327-PA
M3108-PA

195

0.5

MS8s50-BA

M7622-AA

1.1

0.0

5.5

0.0

RF30

1.10

0.80

16.1

RF71%-SA
TK70E-EA
TQK70-SA

M7659

1.26
15
3.5

4.64
24
0.0

26.5
383
17.C

4.3

0.6

2-12

¥N210 CPU Module Set System Maintenance

Figure 2-3:

BA213 Configuration Worksheet

RIGHT POWER SUPPLY

SLOT

MODULE

vde e vae

53."(&',

FIXED DISK O
Yoial ineae columns.

Must not 9xcesd:

33.0A

7.6A

2300 W

LEFT POWER SUPPLY

MODULE

o5 ganr
ot AT
e

(ot

SLOT

10
11

2488 GYCRAQE:
FIXED DiSK 1
FIXED DISK 2
Tota) thase columns.

Must not gxosed:

33.0A

78A

2300 W
MLO-003805

Configuration

2-13

Chapter 3

KN210 Firmware
3.1 Introduction
This chapter describes the KN210 firmware.

The firmware is located in two 128-Kbyte EPROMS (one per processor) on
the KN210. The EPROMSs are arranged as 32-bit words and are located at
the following R3000 and CVAX restart locations:
e

R3000: physical address 1FC00000

CVAX: physical address 20040000

DIFFERENCES: In the KN210 system, the firmware resides in two
EPROMS: R3000 and CVAX. In similar MicroVAX systems, the firmware
resides in only the CVAX EPROM.

The CVAX and R3000 firmware contain the major functional blocks of code
Y| s
| FPR

Li_ o
J=14
RODUTRY BED TfiUlc

Table 3-1:

KN210 Firmware Code

CVAX Firmware Code

Halt entry, dispetch, and exit
Primary and secondary bootstrap
(MDM)

R3000 Firmwere Code

Primary and eecondary bootstrap (ULTRIX-32)
Console program

tnorma] mode commends)

Console program
{meintenance mode cominands)
Syctem restert

ROM-baged diagnostice

KN210 Firmware

J3-1

This chapter discuases the following
e

(CVAX halt procedures

Power-up procedures

Bootstrap procedures for ULTRIX-12 and MDM

R3000 console program and normal mode commands

("VAX console program and maintenance mode commands

The CVAX ROM-based diagnostics are described in Chapter 4.

3.2 KN210 Firmware Features
The KN210 CVAX and R3000 firmware provide the following features:
°

Automatic or manual bootstrap of customer application images at
power-up, resct, or conditionally after processor halts.

A CVAX interactive command language (maintenance mode) that allows
you to exanune and alter the state of the processor

An R3000 interactive command language (normal mode) that allows
you to make use of environment varables to pass information to the
ULTRIX-32 operating system.

Diagnostics and console utihities that test all components on the KN210
and memory modulee and perform extended tests on the DSSI bus and
Ethernet The KN210 firmware also provides RF-series ISEs and the
H3602-AB CPU /O panel, to venfy that the components are working
correctly

LEDs and displays on the KN210 CPU module and console terminel
that display diagnostic progress and error reports

Multilingual support
several languages

The firmware can issue system messages in

The processor must be functioning at a level capable of executing
instructions from the niaintenance program ROM for the maintenance
program to operaie

3-2

KN210 CPU Module Set System Maintenance

3.3 CVAX Halt Entry and Dispatch Code
The CVAX processor enters the halt entry ende at physical address
20040000 whenever a halt occurs The halt entry code saves machine state,
then transfers control to the firmware halt dispatcher

After a halt. the halt entry code saves the current LED code, then writes
an € to the LEDs An E on the LEDs indicates that at least several

matructions have been successfully executed, although if the CPU is

functioning properly. it occurs too quickly to be seen. The halt entry code

saves the following regsteras. The console intercepts any direct reference
to these registers and redirects it to the raved copies:
Ro-R16

General purpose registere

PR$_SAVPS|.

Saved procesanr status longword regiater

PRE SCBB

System control bloch hase regster

DLEDR

Maegnestic LED register

S8CCR

S8C configuration regneter

ADzMCH

S8C eddresa motch register

AlmMSK

S8 sddreas mesk register

The halt entry code unconditionally sets the following registers to fized
values on any halt, to ensure that the console itself cen run.
S8CCR
ADsMCH
ADzMSK

88C configuration regiater
SS(* addreas match regioter
SSC addrezs mash register

CBTCR

CDAL bus imeout control register

TIVRz

S8C timer interrupt vector registers

The coneole command interpreter does not modify actual processor
registers Inste.d it saves the processor registers in console memory when
it enters the halt entry code, then directs all references to the processor
registers to the corresponding saved values, not to the registers themselves.
When the processor reenters normal mode, the saved registers are restored
and any changes become operative only then
References to processor
memory are handled normally The binary load and unload command (X,
Section 3 9 20) cannot reference the console memory pages.

After saving the registers, the halt entry code transfers control to the halt
dispatch code The halt dispatch code determines the cause of the halt
by reading the halt field (PR$_SAVPSL <13:08>), the processor halt action
field (PR$_CPMBX <01:00>), and the break enable switch on the H3602AB panel. Table 3-2 lists the actions taken, by sequence. If an action
fails. the next action 1s taken, with the exception of bootstrap, which is not
attempted after diagnostic failure

KN210 Firmware

3-3

Table 3-2:
Breaks
Enabled on

Actions Taken on a Halt

H3s02-AB

Power-Up Balt' Halt Action®

Action

Diagnostics, halt

Hait

Diagnostics, halt

Restart, halt

Halt

1Power-up halt: PR$_SAVPSL<13:08>=3
Helt action. PR$_CPMRX.01-00>
¥T - conditzon e true, F = condition is falee, X = does not metter

Several conditions can trigger an external halt, and different actions are
taken depending on the condition. The conditions are listed below.

The function switch is set to enable, and you press Eea] on the system

Agsertion of the BHALT line on the Q22-bua

Deassertion of DCOK. A halt 18 delivered :f the srocessor is not running
out of halt-protected space, and the BHALT ENB bit is set. The system
restart switch deasserts DCOK DCOK may also be deasserted by the
DELQA sanity timer, or any other @22-bus module that chooses to

console terminal.

implement the @22-bus restart/reboot protocol.

When in maintenance mode, the processor halts on the deassertion of
DCOK. If halts are enabled, the firmware enters maintenance mode. If
halta are dissbled, the firmware takes the action dictated by the halt action
feld
The action taken by the halt dispatch code on a console
or Q22-bus
BHALT 18 the same: the firmware enters maintenance mode if halts are
enahled
The hait dispatch code distinguishes between DCOK deasserted and
BHALT by assuming that BHALT must be asserted for at least 10 msec,
and that DCOK is deaseerted for at most 9 usec. To determine if the BHALT
line is asserted, the firmware steps out into halt-unprotected space after
9 meec. If the processor halts again, the firmware concludes that the halt
was caused by the BHALT and not by the deassertion of DCOK.

KN210 CPU Module Set System Maintenance

3.4 Power-Up
On power-up, the CVAX firmware performs several unique actions. It runs
the initial power-up test (IPT), locates and identifies the conaole device,
performs a language inguiry, and runs the remaining diagnostics.
The IPT waits for power to stabilize by monitoring SCR<6>(POK). Once
power is stable, the IPT verifies that the console private nonvolatile RAM
(NVRAM) 18 vahd (backup battery is charged) If it is invalid o zero
(battery is discharged), the iPT tests and in.uializes the NVRAM.

After the battery check, the firmware tries (o determine the type of terminal
attached to the console seral line. If the terminal is a known type, it is
treated as the system console
Once a console device has been 1dentified, the firmware displays the KN210
banner message:
RKN210-A Vn.n

The banner message contains the processor name (KN210-A) and the

version of the firmware (Vn.n), where n.n denotes the major and minor
release numbers.

Power-up actions differ, depending on the state of the operation switch
located on the H3602-AB CPU /O panel, shown previously in Figure 1-6.

3.4.1 Power-Up Sequence: Operation Switch Set to Normal

CVAX powers up (begins execution at a location pointed to by physical
address 20040000).

CVAX runs self-test diagnostics.

If you set the operation switch on the H3602-AB CPU I/O panel to the
normal position { ), the powe: sequence is as follows:

R3000 begins execution at an address stored in 1FC00000.

CVAX executes an EXIT command (a 1 is written into the SPR).
CVAX hangs on a DMA grant.

If the bootmode environment variable is set to a, the R3000
attempte to avtoboot. If the bootpath environment variable is
valid, the autoboot succeeds. See Section 3.6.2 for a description
of environment variabies.

KN210 Firmware

3-5

If the bootmode environment variable is not initialized (*) or if it is
set to d, the R3000 prompts you for a command at the normal mode
prompt (>>)

If you enter maint at the >> prompt (a zero is written in the
SPR), the R3000 hangs on a RDBUSY stall and the CVAX resumes
execution (the >>> prompt is displayed).
In addition, the console displays the language selection menu if the
operation switch is zet to the normal position ( +) and the contente of

NVRAM are invalid. The console uses the saved console language if the
operation switch is set to the norma!l position and the contents of NVRAM
are valid.

2.4.2 Power-Up Sequence: Operation Switch Set to
Malntenance
If you set the operation switch on the H3602-AB CPU 1/0 panel to the
maintenance pogition (). the power-up sequence is as follows:
1

CVAX powers up (begins execution at a location pointed to by physical
address 20040000).
CVAX runs self-test diagnostics
CVAX enters maintenance mode and prompts you for commands at the
maintenance mode prompt (>>>)

If you enter EXIT at the >>> prompt, the CVAX hangs on a DMA
grant end the R3000 hegina execution (the >> prompt is displayed).

3.4.3 Operation Switch Set to Action: Loopback Tests
You can verify the connection between the KN210 CPU module set and the
console terminal, as follows
1.

Set the operation switch to the action position ({~).

Set the function switch to enable ().

To test the console port, connect the H3103 loopback connector to the
H3602-AB console connector. (You must install the loopback connector
for the test to run.)

To test the console cable, connect the H8572 connector to the end of the
conesole cable, and connect the H3103 to the H8572

KN210 CPU Module Set System Maintenance

During the test, the firmware toggles between the active and passive states.
During the active state (3 seconds), the LED is set to 7. The firmware reads
the baud rate and operation switch setting, then transmits and receives a
character sequence.

During the paesive state (7 seconds), the LED is set to 4.

If at any time the firmware detects an ervor (parity, framing, overfiow, or
no characters), the display hange at 7. If you move the operation switch
from the action position, the firmware continues as on a normal power-up.

3.4.4 Operation Switch Set to Action: Language Query
If you set the operation switch to the action position ({c) and the function

switch to query ( ), or if the firmware detacts that the contents of NVRAM
are invalid, the firmware prompts you for the language to be used for
displaying the following system messages:
Loading system software.
Failure.
Restarting system software.
Performing normal system tests.
Tests completed.
Normal operation not possible.
Bootfile.

The selection menu for the language »nd keyboard type is shown in
Example 3-1. If no response is received within 30 seconds, the firmware

defaults to English.

NOTE: Some older terminals, such as the VT100, do not support multiple
languages. In these terminals, the language selection menu does not appear
and the system defaulis to English.

KN210 Firmware

3-7

Examplie 3-1:
RN210-A

Language Selection Menu

X0.2-9

Dansk

Deutsch

(Deutschland/Osterreich)

Deutsch

(Schweiz)

English

(United

Kingdom)

English

(United

States/Canada)

Espaiiol

Francais

(Canada)

Frangais

(France/Belgique)

Frangais

(Suisse)

10)

Italiano

11)

Hederlands

12)

Norsk

13)

Portugués

14)

Suomi

15)

Svenska

{(1..15):

3.5 Bootstrap
Bootstrapping is the process of loading and transferring control to an
operating system. The KN210 bootstrap support is as follows:
e

CVAX (maintenance mode) supports the bootstrap of MDM diagnostics.

R3000 (normal mode) supports the bootstrap of ULTRIX-32, as well as
any user application image that conforms to the boot formats described
in this section.

DIFFERENCES: The

KN210

system

coniains

iwo

console

programs:

matintenance mode (CVAX) and normal mode (R3000). See Section 3.7
for normal mode commands that you type at the >> prompt.
Normal
mode commands are ccse sernsitive. See Section 3.9 for maintenance mode
commands that you type at the >>> prompt.
Similar MicroVAX systems contain one CVAX console program
A KNZ210 bootstrap occurs under the following conditions:
¢

You type BoOT at the maintenance mode prompt (>>>).

After bootpath is set, you type boot (lowercase letters) at the normal
mode prompt (>>).

3-8

KN210 CPU Module Set System Maintenance

3.5.1 ULTRIX-32 Bootstrap
The ULTRIX-32 operating system is booted by the R3000 processor under
one of the following conditions:

‘The operation switch is set to the normal position and either of the
following is true:

—~

Autoboot is set to a.

Ycu type boot at the normal mode prompt (>>).

The operating system initiates a reb:~* operation.

You can use one of the following ports as the ULTRIX-32 boot device:

KN210 /O module Ethernet controller

KN210 VO module DSSI controller

KN210 Q22-bus MSCP or TMSCP controller

Tabie 3-3 iists the supporied ULTRIX—32 boot devices. The table correlates
the boot device names expected in a boot command with the corresponding
supported devir=s.

Boot device names consist of a two- or three-letter device code (letters a
through z).

Table 3-3:

ULTRIX-32 Supported Boot Devices

Device Type

Frotocol

RF-geries ISE
RA-series fized-disk
Ethernet adapter

Tope drive

Number of Units

Per Storage Adapter

Device Name

D8si
MSCP

7
4

rf
e

MoP

mop

TMSCP

You boot the ULTRIX-32 operating system at the normal mode prompt (>>),
using the commands explained in Section 3.6. Normal mode commands are
case sensitive (see Section 3.7).

Boot the system as follows:
On Instalistion

On the H3602-AB CPU VO panel, set the operation switch to the
normal position ( ).

KN210 Firmware

3-9

Set the cn/off power switch to 1 (on).

After the system has completed the power-up self-tests successfully, the
normal mode prompt is displayed (>~).
To define the bootpath, define the environment variable for the desired
boot device, using lowercase letters, then boot the system to save the
desired boot device. In Example 3-2, the boot device is an ISE at node
0.

Example 3-2:
>>

Command Procedure to Boot on Inglalistion

setenv bootpath rf£(0,0,0)

'For

file

'vmunix

name,

type

'application

file name.

>> boot

On Power-Up of Existing System
1.

On the H3802-AB CPU /O panel, set the operation switch to the
norimal position ( -).
Set the on/off power switch to on (1).

After the system has completed the power-up self-tests successfully,
the R3000 processor attempts to boot the operating system through the
previously defined boot device.

3.5.2 MDM Bootstrap
When you enter maintenance mode and type BOOT MUxx or SET BOOT MUxx
at the >>> prompt, the CVAX processor boots the MDM operating system.

Before dispatching to the primary CVAX bootstrap (VMB), the KN210 CVAX
processor firmware initializes the system to a known state, as follows:
1.

Checks CPMBX<2>(RIP), bootstrap in progress. If it is set, bootstrap
fails and the console displays the message Failure. in the selected
console language.

Validates the boot device name. [If none exists, supplies a list of
available devices and issues a hoot device prompt. If you do not specify
a device within 30 seconds, uses ESAQ.

Writes a form of this boot request, including active boot flags and boot
device (BOOT/R5:0 ESAOQ, for example), to the console terminal.

Sets CPMBX<2>(BIP).

3-10

KN210 CPU Module Set System Maintenance

Initializes the Q22-bus scatter-gather map.

Validates the PFN bitmap. If invalid, rebuilds it.

Searches for a 128-Kbyte contiguous block of good memory as defined
by the PFN bitmap. If 128 Kbytes cannot be found, the bootstrap fails.

Initializes the general purpose regisiers:
Ro
R2
R3

Addreaa of descriptor of the boot device name or 0 if none gpecified
Length of PFN bitmap in byies
Addrees of PFN bitmap

Time-of-day of bootatrap from PR$_TODR

Boot flags
Hait PC value

R10

R11

Halt PSL value (without halt code and mapenable)

AP
sp

Halt code
Rase of 128-Kbyte good memory block plue 612

Base of 128-Kbyte good memory block plus 512

Ri.R8, R7, R8,
R9, FP

Copies the virtual memory bootstrap (VMB) image from EPROM to
local memory, beginning at the base of the 128 Kbytes of good memory

block plus 512.

10. Exits from the firmware to VMB residing in miemory.

Virtual Memory Bootstrap (VMB) is the primary MDM bootstrap. The
KN210 VMB resides in the CVAX firmware and is copied into main memory
before control is transferred to it. VMB then loads the secondary beotstrap
image and transfers control to it.

KN210 Firmware

3-11

Table 3—4 lists the supported R5 boot flags.

Table 3-4:

VMB Boot Flags

Bit

HName

Description

RPB$V_CONV

Conversatior al boot.
At various points in the system boot
procedure, tie bootstrep code solicite parametors and other
input from the console terminal.

RPBS$V_DEBUG

Debug. If this flag is set, the code for the XDELTA debugger is
mapped into the system page tables of the running system.

RPBYV_INIBPT

RPB$V_BBLOCK

Secondary bootstrap from bootblock. When set, VMB reads
logicel block number 0 of the boot device and tests it for
conformance with the bootblock formet. If in conformance, the
block is executed to continue the bootstrap. No attempt is made
to perform a Files-11 bootatrap.

RPBEV_DIAG

Diegnostic bootstrap. When get, the load image requested over
the network is [SYS0.SYSMAINTIDIAGBOOT.EXE.

RPBSV_BOOBPT

Bootstrep breakpoint. When set, a breakpoint instruction ie
ezecuted ‘n VMB and control is transferred to XDELTA before
booting.

RPB$V_HEADER

Image header. When set, VMB transfers control to the address
specified by the file's image header.
When not set, VMB
transfers control to the firat location of the load image.

RPB$V_SOLICT

Pile name solicit. When set, VMB prompts the operator for
the name of the application image file. The meximum file
epecification size is 17 characters.

RPB$V_HALT

Halt before tranafer. When set, VMB halts before transferring
control to the application image.

31:28

RPB$V_TOPSYS

This field can be any value from 0 through F. This flag changes
the top-level directory name for system disks with multiple
operating gystems. For example, if TOPSYS is 1, the top-level
directory name is (SYS1...].

3-12

KN210 CPU Module Set System Maintenance

Initial breakpoint.

If RPBYV_DEBUGC is set, the VMS

operating system executes a BPT instruction in moduie iFIT

immediately efter enabling mapping.

Table 3-6 lists the supported MDM boot devices.

Table 3-5:

Supported MDM Boot Devices

Boot Name

Controller Tyne

Device Type(s)

[node$§)DiAn
DUen

On-board DSSI
RQDX3 MSCP

RF-series [SEs
l?.mlz-seriea fired disk drives, RX33,

KDABO MSCP

RA-gerive fixed disk drives

KFQSA MSCP

RF-geries ISEs

KLES!
RIVi2

RC25
RLO1, RLO2

Disk

Dien

Tape
MUcn

TQK70 MSCP

TK70

KLESI

TUBIE

ESA0

On-board Eithernet

XQen

DELQA

Network

DESQA

KN210 Firmware

3-13

3.5.3 MDM Restart
An MDM restart is the process of bringing up the YDM operating system
from a known initialization state following a processor halt.
A restart occurs under the conditions listed in Table 3-2, earlier in this
chapter.
To restart MDM, the firmware searches system memory for the Restart
Parameter Block (RPB), a data structure constructed for this purpose by
VMB. If the firmware finds a valid RPB, it passes control to the operating
system at an address specified in the RPB.
The firmware keeps a RIP (restart-in-progress) flag in CPMBX, which it
uses to avoid repeated attempts to restart a failing operating system. The
operating system maintains an additional RIP flag in the RPB. The RPB is
a page-aligned control block that can be identified by its signature in the
first three longwords:
+00 (first longword) = physical address of the RPB
+04 (second longword) = physical address of the restart routine
+08 (third longword) = checksum of first 31 longwords of restart routine
The firmware finds a valid RPB as follows:
1.

Searches for a nage of memory that contains its address in the first
longword. If none is found, the search for a valid RPB has failed.

Reads the second longword in the page (the physical address of the
restart routine). If it is not a valid physical address, or if it is zero,
returns to step 1. The check for zero is necessary to ensure that a page
of zeros does not pass the test for a valid RPB.

Calculates the 32-bit two's-complement sum (ignoring overflows) of the
first 31 longwords of the restart routine. If the sum does not match the
third longword of the RPB, returns to step 1.

If the sum matches, a valid RPB has been found.

3-14

KN210 CPU Module Set System Maintenance

3.6 Normal Mode Overview
When the KN210 is in normal mode, the console reads and interprets
commands reccived on the cunsole terminal at the normal mode prompt
{>>)

This R3000 interactive command language allows you to make use of
environment vanables to pass information to the ULTRIX-32 operating
system.

You can use normal mode commands to boot the ULTRIX-32 operating
system, set up automatic booting. and deposit or examine I/O address space
and memory.

3.6.1 Control Characters in Normal Mode
Table 3-6 lists the characters that have special meaning in normal mode.
Table 3-6:

Cheracter

Normal-Mode Control Characters
Action
Ends 8 command hne .mmand charscters are buffsred until vou

preas [Rown)

Deletea the previcusly typed character.
If vou define the console terminal as hard copy (environment
variable term set to hardcopy),

surrounded by backslashes

the deleted tert 18 displayed

f the coneole terminal 18 a CRT

tenvironment varishle term set to crt), each delete 18 displayed
with the sequence <BS><SP><BS>

[leletes recerved are ignored when there are no characters to be

3lia

deleted

Cauaes the congrole to ebort the proceasing of a command.

Causea console output to be discarded until you enter the nest

:CWO| or until the next console prompt or error measage is issued.
3

CWO) 18 alan canceled when you enter [Coic]

Resumes console output thet was suspended when you entered

Causes the current command line to be displayed without any
deleted characters

Suspends output on the console terminal until you onu-r.
hacards ell charactera accumulated for the current line

Suppreeses

any

specal

meaning

associeted

with

the

character.

KN210 Firmware

3-15

3.6.2 Environment Variables in Normal Mode
The KN210 console makes use of environment variables to pass information
to the operating system.

There are three types of variables
o

Volatile (lost when power resumes)

Nonvolatile (maintained after power resumes)

Fixed (rebuilt when power is turned on)

You can define additional environment variables, but those you define will
be lost when power is removed.
Table 3-7 lists the default variables.

Table 3-7:

Environment Variables

Variabie

Type

hatd

Fzed

bitmap

Fized

Description
The baud rate of the console terminal line ia determined

by the baud rete select switch inaside the H3602-AB
CPU /O panel. The factory setting is 9800 Allowed
values are 300, 600, 2400, 4800. 8800, 19.200. and
38,400

Indicates the address of the memory bitmap

The

bitmap keeps track of good eand bad memory pages.
Each it corresponds to one pege in memory, i

indicates the page is good, eand O indicates the page
i® bad

butmaplen

Fized

Indicates the length of the memory bitmap 1n bytes.

bootpath

Norvolatile

Indicates the default bootpath. The system uses this

variable when you type the suto command. An example
of a bootpath definition is: rf10,0,0vmunix.

bootmode

Nonvolatile

Determines what programs run when the gystem is

turned on or reeet. Use one of the following codes:
8

Autaboots the operating eystem using the bootpath
vanable

Halts the system
disgnostica

after

performing

power-up

console

Fiuzed

The aystem always selects TTY(0) @s the console device.

osconsole

Fized

The aystem elways pelects TTY(0) as the console device

3-16

KN210 CPU Module Set System Maintenance

Table 3-7 (Cont.):

Environment Variables

Variable

Type

Deecription

avatype

Fized

Contains information used to identify the processor

Bits 24:31 contain the CPU type Bita 16:23 contain
the system type (giz for KN210). Bita 8:16 contain the
firmware revision level. Bita 07 contain the hardware
verwien level

3.7 Normal Mode Commands
The R3000 console program displays the normal mode prompt (>>) when it
is ready to accept commands.

Table 3-8 lists the supported normal mode console commands.

Table 3-8:

KN210 Normal Mode Commands

Command

Description 7

boot

Boota the operating system

continue

Raturna control to the procesaes interrupted by & halt gignel

Deposita deta st 2 given addrees

dump

Dumps memory to the arreen

Ezemines memory

ill]

Deposits deta in an addreas range

Resumes execution of the program in memory

help

Diaplavs the syntag of console commands

Displaye the syntax of congole commands

init

Retinitializea memory

maint

Causes the console to enter maintenance mode

printenv

heplaye console environment varisblee

setenv

Sets console environment vanablea

unastenv

Unaets console environment vanablea

KN210 Firmware

3-17

Obgerve the following rules when you type normal mode commands:

All commands typed at normal mode level are case sensitive with
respect to parsing commands; case ie preserved when you sssign values
to environment variables.

Type all normal mode console commands, uging cnly ASCII characters.
Values that you enter for environment variables may contain any 8-bit
character code.

Command execution begins when you prees (Reer].
Enter numeric valuee as follows:

Enter decimal values as a string of decimal digits with no leading
zeroe (for example, 123).

Enter octal values ae a string of octal digits with a leading zero (for
example, 0177).

—~

Enter hexadecimal values as a string of hexadecimal digite precedcd
by Ox (for example, Ox3f.

Enter dinary ralues as 8 string of binary digits preceded by 0b (for
example, 0b1001).

When reading or writing to memory. you have a choice of data sizes:

byte, halfword, or word Leading zeros are dropped.
Because a word is 4 bytes, successive addresses, when referenced by a
word, are successive multiples of 4 For example, the address following
0x80000004 is 0xB80000008 An error occurs
if you try to specify an
addrese that is not on a boundary for the data size you are using.

3-18

KN210 CPU Module Set System Maintenance

3.7.1 Conventions Used in This Section
Letters are to be typed exactly as they appear.
Lettere in iialics represent arguments for which you supply values.
(Note that the Help and menu screens display these arguments in all
capital letters )

Arguments enclosed in square brackeis ({ ]) are optional.
Ellipses (...) follow an argument that can be repeated.
A vertical bar( | ) separates choices.

Parentheses are used as in algebraic expressions.
following sequence means enter -b or -h or -w-

For example, the

={blhiw)

3.7.2 Getting Help
You can get help with console command syntax in several ways:
You can type the word h=!p or a question mark (?) to display a menu
of all console commands.
You can enter the name of the command for which you want help as an
argument to help or as a question mark (7).

For example, entering ? e at the console prompt (>>) displays the syntax
for the examine (e) command:
e

[-(blhiw)]

ADDR

If you type an incorrect command line, you get a Help screen.

For example, the e command requires an addr argument. If you type
e -b at the console prompt (>>) without entering an address, the screen

will display the correct syntax for the command:
@

(-(blhiw)]

ADDR

KN210 Firmware

3-19

3.7.3 boot
The boot command loads the file that contains the operating system.
Format:

boot (-f file] (-8} {-n] {arg...]
The optional -f flag followed by the file parameter specifies the file you want
to use during a boot procedure. If you do not specify the -f flag and a file,
the file specified by the environment variable bootpath is loaded.

The file parameter has the format.

devi[controller |,unit-number) |,partition-number
) filename)
o

dev indicates the device from which you are booting the operating
system. Typical devices are rf for RF-series ISEs, ra for RA-series hard
disk drives, tm for a tape, and mop for a network. Typing mop nullifies
the other arguments in the list. Table 3-9 lists the device names for
each device.

Table 3-9:

Boot Device Names (Normal Mode)

Device Type

Protocel

RF -geries [SE
RA-gerien fined-diak
Ethernot edaptar

Tape drive

Number of Units

Per Blorage Adapter

Device Name

DSSi

)

MSCP

MOP

mop

TMSCP

controller indicates the ID number of the controller for the device from

unit-number indicates the unit number of the device from which you
are booting the operating system.

which you are booting the operating system.

To diaplay a list of devices, their unit numbers, and controller numbers,
enter maintenance mode and issue the command sHow DEVICE at the
maintenance prompt >>>. After viewing the display, type EXIT and

press

3-20

to return to the normal console prompt >>.

KN210 CPU Module Set System Maintenance

Example:
>> maint
>>>

SHOW

DES1

DEVICE

Node

=DIAO
DSSI

Hode

-DIAl

(RF71)

(R3QDVA)

-rf{1,1.*)

Node

DSSI

(R3WBOA)

-rf£(0,0,%)

(RF71)

(%)

UQSSP

Tape Controller 0

-MUAO

-tm(0,0)

Ethernet

Adapter

~ESAO0 -se
>>>

(774500)

(TK70)

-mop()

(08-00-2B-0C-C4-75)

EXIT

As in the preceding example, the SHOW DEVICE command displays
the CVAX device names and the R3000 device names, which are
followed by the controller number and unit number in parentheses. The
asterisk indicates the pertition-number variable, which is determined
software.
svetem
during instaliation of the operating
&
~J
partition-number indicates the number (or other designator) of the
partition from which you are booting the operating system. When you
are booting from a tape, this number is not used because the boot file
must be the first file on the tape. When you are booting from a disk, this
number depends cn how you partitioned the disk when you installed
your operating system software. Refer to your software instaliation
manual if you need a reminder about disk partition indicators.

filename indicates the name of the operating system file:.
The optional -5 flag causes the operating system to boot in single-user mode.
Unless -8 is specified, the system will boot in multiuser mode.

The optional -n flag causes the specified file to be loaded but not executed.
The optional arg parameter contains any information to be passed to the
booted image.

KN210 Firmware

3~21

Examples:
>>

boot

-f

ra(0,0,0)vmuniz

This command boots the file vinunix, located in the (a) partition of the first
hard disk (unit number 0), using controller 0.
>>

boot

-f

rf(2,2,c)vmunix

This command boots the file vinunix, located in the ¢ partition of the second
RF-geries ISE (unit number 2), using controller 2.
>>

boot

-f

tm(0,5)

This command boots from the tape, which is unit 5 and controller 0.

3-22

KN210 CPU Module Set System Maintenance

3.7.4 continue
CAUTION: If the operating system siate has not been properly saved
(halted), do not type continue. Doing so may cause the processor to hang.

The continue command returns control to the processes interrupted by a
halt signal. Use this command if you inadvertently halt the system by
or the Halt button.
pressing
Format:

continue

KN210 Firmware

3-23

3.7.5 d (deposit)

The d (deposit) command deposits a single byte, halfword, or word value at
the specified address.

NOTE: The R3000 halfword consists of 16 bits, and the word consists of 32
bits.
Format:

val
iw)
addr
d[-(bih

The first parameter, which is optional, indicates the data size. If not given,
date size detanlts to word. If vou do not epecify a data size, a word is used.
o

.b deposits 1 byte of data.

.h deposits a halfword (2 bytes) of data.

.w deposits a word (4 bytes) of data.

The addr parameter indicates the address to which you want data written.
System address space is in the range 0x80000000 to 0xbf000000.

The val parameter containe the data you want deposited at the given
address.

Example:
>> d

-w OxB0000000 OxFfEfffff

This commanad deposits the value O, with a data size of one word, at
addresas 0x80000000.

3-24

KN210 CPU Module Set System Maintenance

3.7.6 dump
This command shows a formatted display of the contents of memory.
Format:

dump [(bilhiw)] [-(oldlulxlciB)]mg

The first paramete-, which is optional, indicates the data size. If not given,
data size defaulis to word. If you do not specify a data size, the system
uses a word.

.b displays memory in bytes.

.h displays memory in halfwords.

.w displays memory in words.

The next parameter, also optional, detevmines how data is displayed.
¢

.o displays memory in octal format.

.d displays memory in decimal format.

.u displays memory in unsigned decimal format.

.x displays memory in hexadecimal format.

.c displays memory in ASCI! format.

.B displays memory in binary format.

If no format argument is given, hexadecimal format is used.

The rng parameter indicates the range of memory you want to see. You can
specify the range in one of two ways:

addré#cnt displays the number of addresses specified by cnt, beginning

addr:addr displays all values between the specified addresses.

at addr.

KN210 Firmware

3-25

Examples:
>>

dump

0xB80000000§0xf

This command uses hexadecimal format to dump the first 156 words of
memory to the screen.
>> dump

-b 0xB0000000§0xf

This command uses hexadecimal format to dump the first 16 bytes of
memory to the screen.

The dump display shows rows of address contents. The lefimost column
gives the address of the first field in each row.

3-26

KN210 CPU Module Set System Maintenance

3.7.7 e (examine)
The e (examine) command examines the byte, halfword, or word at the
specified address.

NOTE: The R3000 halfword consists of 16 bits, and the word consists of 32
bits.
Format:

e [-(bihiw) addr

The first parameter, which is optional, indicates the data size. If not given,
data size defaults to word. If you do not specify the data size, a word is
used.
e

.b indicates a single byte.

.j:indicates a halfword.

.windicates a word.

The addr parameter indicates an address in the range 0x80000000 to
0xbf000000.

When you enter the examine command, a display similar to the following
appears:

0xB80000005:

Ox41

'A’

The left-hand field echoes the address you entered.

The next three fields display the contents of the address in decimal,
hexadecimal, and ASCII formats, respectively. If the ASCII charscter is
unprintable, it is displayed as an octal value preceded by a backslash: for
example, '\ 032'.

Example:
>>

0x80000000

This command examines the word at address 0x80000000. The resulting
display might look like this:
0x80000000:

1008385985

Ox3clabfcl

\301’

KN210 Firmware

3-27

3.7.8 fill
The fill command writes a specified value to a range of memory. If you do
not specify a value, the system puts zercs in the memory range.
Format:

fill [-(b 1 h | w)] [-v val]l g
The first parameter, which is optional, indicates the data size. If not given,
data size defaults to word.
®

-b indicates bytes.

.h indicates halfwords.

.w indicates words.

The optional parameter -v val specifies the numeric value to write to
memory. If you do not specify a value, all zeros are written. If the size
of val does not match the data size parameter, val is truncated or expanded
28 necessary.

The rng parameter indicates the memory range. You can specify the range
in one of two ways:

addr#cnt fills addresses beginning at addr and continuing for cnt
locations.

addr:addr fills all locations between the two given addresses.

Example:
>>

£ill

-v OXfEfff£Ff

OxB0000010:0xB800000£f

This command sets all bits to 1 at addresses 16 te 255.

3-28

KN210 CPU Module Set System Maintenance

3.7.9 go
The go command transfers control to the indicated entry-point address.
Format:

go pe)
The optional pc parameter indicates the entry-point address you want to
use.

If you do not snecify an entry address, the syatem uses the entry point of

the program mudule chat was most recently loaded. If no program module
was previously loaded, the system uses 0 as the entry-point address.

KN210 Firmware

3-29

3.7.10 help
The help command displays the correct syntax for the console commands.
Format:

help (cmd]
The optional cmd parameter indicates the command for which you want
information. If you do not specify cmd, the complete console menu appears.

Examgle:
>>

help

CMD
:
boot

[-f

FILE}

[-s]

[-n]

[ARG...]

cont inue

{-(tblhiw)]

ADDR

VAL

dump

[-(blhiw)]

[-(oldiulx|cIB)]

fill

[~(bthiw)]

[-v

[-(blhiw)]

RNG

ADDR
VAL]

RRG

{PC]

help

[CMD]

init
maint

printenv
setenv

unsetenv

[EVAR...)

gVAR

STR

EVAR

(CMD)

RNG:

ADDRECNT
ADDR
: ADDR

3-30

KN210 CPU Module Set System Maintenance

3.7.11 ?
The ? command functions exactly like the help command (Section 3.7.10).
Format:

? {cmd)

KN210 Firmware

3-31

3.7.12 imit
The init command fully initializes the system.
Format:
imit
The system performs the following:
¢

(Clears memory

Resets VO

[nitializes all supported devices

The effect of the init command is identical to turning the power on or
pressing the Reset button, except that the system does not execute its selftest. The memory size and Ethernet address are displayed.
Example:
>>

init

Memory

Size:

Ethernet

3-32

1677721€

Address:

(0x1000000)

bytes

08-00-2b-0c-c5-f6

KN210 CPU Module Set System Maintenance

3.7.13 printenv
The pnntenv command displays the current value for the specified
environment variable.
Format:

printenv [evar...}

The optional evar parameter indicates the variable whose value you want
to see. If you do not specify a variable, the complete environment variable
table appears.
Examples:
>> printenv
bootpath=rf
(0,0, 0)vmunix
bootmode=*
console=0

baud=9600
systype=0x82060102

bitmap=0xa000£ccO
bitmaplen=0xc0O

osconsocle=0
>>

printenv

bootpath

boctpath=rf
(0, 0,0)vmunix

KN210 Firmware

3-33

3.7.14 setenv
The setenv command assigns new values to the specified environment
variable Refer to the discussion of the printenv command (Section 3.7.13)
for a description of each variable.
Format:
setenv evar ofr

The evar parameter indicates the variable you want to set.

The str parameter indicates the value you want to epecify.

Example:
>>

getenv

bootmode

The command in the example above assigne a value of “a” to the bootmode
variable. This will cause the systemn to autoboot at power-up.

You can also add your own environment variables, es explained in
Section 3.7.
These variables are stored in volatile memory
The
environment variables table can contain up to 16 variables, for a total of
256 characters.

3-34

KN210 CPU Module Set System Malmenance

3.7.15 unsetenv

The

unsetenv

command removes the specified

environment variables table.

variable from

the

Format:
uneetanv eoar

The evar parameter indicates the variable you are removing. Refer to
Table 3-7 earlier in this section for a description of each variable.

The unsetenv command does not affect the environment variables sicred in

nonvolatile memory. These variables are reset at the next reset or power

cycle.

KN210 Firmware

3-35

3.8 Maintenance Mode Overview
Whenever the CVAX console program is running, the maintenance mode
prompt (>>>) is displayed on the console terminal and the KN210 is halted

as described in Section 3.3.

In maintenance mode, you can examine and alter the state of the processor
by typing certain console commands and characters. Table 3-10 lists the
keypad control characters that have special meaning in maintenance meode.

Table 3-10:

KN210

Console Control

Characters

(Maintenance

Mode)
Character

Action
Also <CR>.

The carriage return ends a commend line. No action ie

taken on 8 command until after it is terminated by @ carriage retum.
A null line terminsted by e carriage return is treated ee o valid, null
commend. No action is taken, and the console prompts for input.
Carriage return is echoed @8 carriage return, line feed (<CR><LF5>).

[x] (Rubout)

When you press the (X}rubout) key, the console deletes the previously

typed character

The resulting display differs, depending on whether

the conzole 18 & video or ¢ herd-copy terminal.

For hard-copy terminals, the conssle echoss e backslach (\), followed
by the character being deleted.

If you prese ndditional rubouts, the

additional deleted charactere ove echoed.
If you type @ nonrubout
character, the console echoere enother bachslash, followed by the
character typed.
The vesult is to echo the charseters deleted,
surrounding them with backslashes For example:

EXAMI.E{X] (rubout)
(%] (rubout) NE<CR>
The connole echoes: EXAMIE\E;\ NE<CR>
The console sees the command line: EXAMINE<CR>
For video terminals, the previous charectsr in eresed and the cureor is
restored (o its previous poaition.
The console does not delete charscters past the beginning of e commeand
line. If you press more rubsute then there ere characiere on the line,
the extre rubouts are ignared. A rubout entered on a blank line is

;

3
7
3

;:fl

ignored.

ignored if typed on en empty line.

Stops output to the console terminal until [C%3] is typed. Not echoed.
Resumes output to the conzole terminal. Not echosd.

Echoes <CR><LF>, followed by the current command line. Cen be used

to improve the readability of 2 command line thet has been heevily
edited.

Echoes "C<CR> and sborts processing of 8 commeand When entered
es part of @ command line, deletes the line.

Table 3-10 (Cont.):
Charecter

Cr0]

KN210 Console Control Characters (Malntenance Mode)

Action

Ignores trensmissicns to the console terminal until the next

is entered. [Echoee "O when dissbling ocutput, not echoed when it
reenables cutput. Output ie reenabled if the conzole prints en error
mesaage, or if it prompta for @ command from the terminal. Qutput
is
aleo enabled by entering maintenance mode, by pressing the

and by preesing [Cw<].

key,

3.8.1 Command Syniax in Maintenance Mode
The console accepts commands up to 80 characters long. Longer commands
produce error messages. The character count does not include rubouts,
rubbed-out characters, or the
at the end of the command.

You can abbreviate a command by entering only as many characters as are
required to make the command unique. Most commands can be recognized
from their first character See Table 3-14.
The console treats two or more consecutive spaces and tabs as a single
space. Leading and trailing spaces and tabs are ignored. You can place
command qualifiers after the command keyword or after any symbol or
number in the command.

All numbers (addresses, data, counts) are hexadecimal (hex) except for GPR
symbolic names, which are in decimal. The hex digits are 0 through 9 and
A through F. You can use uppercase and lowercase letters in hex numbers
(A through F) and commands.
The following symbols are qualifier and argument conventions:
[l

en optional qualifier or argument

8 required qualifier or argument

3.8.2 Address Specifiers in Maintenance Mode
Several commands take an address or addresses as arguments. An address
defines the address space and the offset into that space. The console
supports six address spaces:

Physical memory
Virtual memory
Protecied memory

General purpose registers (GPRs)
Internal processor registers (IPRs)
The PSL

KN210 Firmware

3-37

The addreas apace that the conasle references is inherited from the previcus

console reference, unless you explicitly specify another addresa space. The
initial address space is physical memory.

3.8.3 Symbolic Addresses in Maintenance Mode
The console supports symbolic references to addresses. A symbolic reference
defines the address space and the offset into that space. Table 3-11 lists
symbotlic references supported by the console, grouped according to address
space. You do not have to use an address space qualifier when using a
symbolic address.

Tabie 3-11:

Console Symbolic Addresses (Maintenance Mode)

Symbol

Address

Symbeol

Address

GPR Address Space (/G)
RO

]

R2
R4

2
4

R3
R5

3
&

R10

R11

Ri12
Ri14
AP

oC
O
oC

R13
R16
FP

oD
OoF
oD

PSL

PR Address 8pace (/)

pr$_kep

prd_esp

pré_isp
pré_pOlr

04
09

pr$_pObr
pré_plbr

08
0A

pré_pllr

pré_sbr

pré_slr

pré_pcbb

prd_sisr
pr$_nicr
prd_todr

16
19
1B

pré_icer
pré_icr
pré_rzce

18
1A
20

pr$_sep

pr$_scbb
pré_astlv

pré_rzdb

3-38

11
13

pré_usp

pré_ipl
pré_sirr

prd_txes

KN210 CPU Module Se! Systemn Maintenance

12
14

Table 3-11 (Cont.):
Symbol

Console Symbolic Addresses (Maintenance
Mode)

Address

Symbol

Addrese

pré_tbdr
pré_meear
pré_savpe
pré_ioreset
pré_tbia
pré_sid
-

24
2
2A
37
39
3E
-

IPR Address Space (/I)

pré_txdb
pré_cadr
pr$_meer
prd_savpasl
pré_mapen
prd_tbis
prd_tbehk

23
Z5
27
2B
38
3A
3F

Physical Memory (/P)
gbio

20000000

qbmem

gbmbr

20080010

30000000
-

rom

200400600

cacr

20084000

bdr

20084004

daecr

26080000

daer

20080004

dmear
iperd

20080008
20001140

dsear
iperl

2008000C
20001142

iper2

20001144

ipcr3

20001148

esc_rem
esc_cdal

20140400
201406020

sac_cr
sec_dledr

20140010
20140030

sec_od0mat

20140130

esc_adOmak

20140134

sec_adimet

20140140

eac_adimek

20140144

sar_ter0

20140100

sac_tir0

20140104

eac_tnird

20140108

sge_tive)

2014010

sus_terl
gec_tnirl

20140110
20140118

asc_tirl
sse_tivel

20140114
2014011¢

memeer(

20080100

memear 1

20080104

memcar2

20080108

memezr3

2008010c

memeerd

206080110

memecerh

20080114

memesrd

0080118

nemeer7

2008011¢c

memaur8
memeer 10

20080120
20080128

memeerd
memeszr1]

20080124
2008012¢

memcar 12

20080130

memesrl3

20080134

memear14

20080138

memeerlb

2008013¢

memcer 16

20080140

memesr17

20080144

nisarom

20084200

nirdp

20084400

nirap

20084404

nibuf

20120000

KN210 Firmware

3-39

Table 3-11 (Cont.):
Symbol

Console Symbolic Addresses (Malntenance
Mode)

Address

Symbol

Addreass

Physical Memery (/P)
mei_sbb

20084600

mei_scl

20084804

mei_scZ

20084608

msi_car

2008480C

mei_id

20084810

mei_glesr

20084614

mai_destat
msi_data

20084618
20084620

mei_dstmo
mgi_dmetrl

20608481C
20084824

mgi_cmliote
mei_dmaddrh
mei_stlp

20084628
20084830
20084638

mai_dmaddr]
mei_dmaebyte
mai_ltlp

2008482C
20084634
2008483C

20084648

msi_dstat

2008484C

msi_ilp

mai_cstat

20084640

msi_dsctrf

20084644

msi_comm

20084650

msi_dictr]

20084854

mei_clock
msi_pidisg

20064658
20084680

mai_bhdieg
mei_dmdiag

20084856C
20084864

mei_mcdieg

20084668

msi_ram

2010600060

Table 3-12 lists symbolic addresses that you can use in any address space.

3-40

KN210 CPU Module Set System Maintenance

Table 3-12:
Symbol

Symbolic Addresses Used in Any Address Space

Description
The location last referenced in en EXAMINE or DEPOSIT command.

The location immediately following the last locaticn referenced in an EXAMINE
or DEPOSIT command. For references to phyeical or virtual memory spaces, the
location referenced is the imst address, plua the gize of the last reference (1 for
byte, 2 for word, 4 for longword, 8 for quadword). For other address spaces, the
eddress ia the last addreas referenced plus one.

The location immedistely preceding the last location referenced in an EXAMINE
or DEPOSIT command.

For references to physical or virtual memory spaces,

the location referented is the lust address minus the size of this reference (1 for

byte, 2 for word, 4 for longword, 8 for quadword). For other address spaces, the
addreaa is the last address referenced minus one.

The locstion addressed by the last location referenced in an EXAMINE or
DEPOSIT command.

3.8.4 Command Qualifiers in Maintenance Mode
You can enter console command qualifiers in any order on the command
line after the command keyword. There are three types of qualifiers: data
conirol, address space control, and command specific. Table 3-13 lists and
describes the data control and address space control qualifiers. Command
specific qualifiers are listed in the descriptions of individual commands.

KN210 Firmware

3-41

Table 3-13:
Qualifier

Console Command Qualifiers (Maintenance Mode)
Description

Data Control

The data size is byte.

The date size is word.

The data size is longword.

]

The data size is qusdword.

/N:{count)

An unsigned hexadecimal integer that is evaluated into @ longword. This

/8TEP:{sizel

qualifier determines the number of additional operations that are to take place
on EXAMINE, DEPOSIT, MOVE, and SEARCH commands. An error messags
sppears if the number overflows 32 bita.
Step.

Overrides the defsult increment of the console current reference.

Commande that manipulate memeory, such as EXAMINE, DEPOSIT, MOVE,

and SEARCH, normally increment. the console current reference by the size
of the data being used.

fWRONG

Wrong. Used to override or set error bits when referencing main memory. On
writes, uses the complement. On reads, ignores ECC errors.

Address Space Control
G

General purpose register (GPR) addreas space, R0O-R15.
always longword.

The data size is

Internsl processor register (IPR) addreas space. Acceesible oniy by the MTPR
and MFPR instructions. The data size is always longword.

Virtuel memory addrees space. All access and protection checking oceur. If
access to & program runring with the current PSL is not allowed, the console

iesues an ervor message. Deposita to virtual space cause the PTE<M> bit to be

set. [f memory mapping is not enabled, virtusl addresses are equal to physical
aeddresses. Note that when you examine virtual memory, the addrese space
and address in the response ia the physical address of the virtual addrese.

Physical memory address epace.

Processor status longword (PSL) address space.

longword.

The data size is always

Access to console private memory is allowed. This qualifier also disables
virtual address protection checks. On virtusl address writes, the PTE<M>

bit is not eet if the /U qualifier is present. This qualifier is not inherited; it
must be respecified on each command.

3-42

KN210 CPU Module Set System Maintenance

3.2.5 Maintenance Mode Command Keywords
Table 3-14 lists maintenance mode command keywords by type. Table 3-15
lists the parameters, qualifiers, and arguments for each console command.
Parameters, used with the SET and SHOW command: only, are listed in
the first column along with the eommand.
Although it is possible to abbreviate by using the minimum number of
characters required to uniquely identify a command or parameter, these
abbreviations may become ambiguous at a later time if & new command or
parameter is added in an updated version of the firmware. For this reason,
you should not use abbreviations in programs.

Table 3-14:

Command Keywords by Type (Malntenance Mode)

Processor Control

Date Tramsfer

Console Control

BOOT

EXAMINE

CONFIGURE

CONTINU

DEPOSIT

FIND

HALT
INITIALIZE
NEX "~

MOVE
SEARCH
X

REPEAT
SET
SHOW

UNJAM

!
EXIT

Table 3-15:

Console Command Summeary (Malntenance Mode)

Command

Quelifiors’

Argument

Other(s)

BOOT

/R5:(boot_flage) or /{bust_flegs!

|[{bost_device}]

CONFIGURE

CONTINUE

DEPCSIT

BWIAQ

{addressi

{data) {{data}]

EXAMINE

BW/LKQ

(eddreas!

MEM /RPB

GCINPMNU
/N:\count} /STEP:imize}
/WRONG | .imask])

MANPRR
/N:{count} /'STEP:{wire)
ARONG/INSTRUCTION

EXIT
FIND
HALT

1{ | denoles & mandatory item that must be syntactically correct.
[ ] denstes an optional item

KN210 Firmware

3-43

Table 3-15 (Cont.):

Console Command Summary (Malntet:ance
Mode)

Conmand

Qualifiers’

Argumeont

Other(s)

HELP

INITIALIZE

{eve _address)

{dest_nddress)

[eount]
{command}

MOVE

NP As

N icount! STEP (@mze)
WRONG | (maek]]

NEXT
REPEAT

SFARCH

/B W /L 'Q
NpAal

{start_addresa)

ipattern) {imaak))

N {ecunt) STEP:laze)
WRONG/NOT

SET BFLAG

{boot _flags!

SET BOGOT

{device_string)

SET HOST

DUP /DSS1 n VQSSP;

{nodel n

ITISK n
TAPE n cer_address)
AMAINTENANCE UQSSP!

{controller_number|

{itask))

{SERVICE n cer_addreaas!

SET LANGUAGE

{language_typel

SHOW BFLAG

SHOW BOCT

SHOW DEVICE

SHOW DSSI

SHOW ETHERNET

SHOW LANGUAGE

SHOW MEMORY

FULL

SHOW QRBRUS

SHOW RIVi2

SHOW UQSSP

SHOW VERSION

START

({eddreaal ]

TEST
UNJAM
X

{test_number)
{eddreas)

{{perumeters))
{count)

| | denotes & mendetory item that must be syntactically correct.
{ | denotes an optional item.

3-44

KN210 CPU Module Set System Maintenance

3.9 Maintenance Mode Commands
This section describes the maintenance mode commands.
Enter the
commands at the maintenance mode prompt (>>>) These commands may
be typed in uppercase or lowercase leiters However, they are shown in all
uppercase letters in this document to differentiate them from the normal
mode commands, which must be typed in all lowercase leiters.

3.9.1 BOOT
The BOOT command initializes the processor and transfers execution to
VMB. VMB attempts to boot MDM from the specified device, or from the
default boot device if none is specified. The console qualifies the bootstrap
operation by passing a boot flags bitmap to VMB in R5.
Format:

BOOT (qualifier-list] [device_name)

If you do not enter either the qualifier or the device name, the default value
is used Explicitly stating the boot flags or the boot device overrides, but
does not permanently change, the corresponding default value.
Set the default boot device and boot flags with the SET BOOT and SET
BFLAG commands. If you do not set a default boot device, the processor

times out after 30 seconds and a.iempts to boot from the on-board Ethernet
port, ESA0Q

Qualifiers:
Command specific:
/R5:(bitmap!

A 32-bit hex value passed to VMB in R5. The console does not interpret this
value Use the SET BFLAG command to specify a default boot flage longword.

Use the SHOW BFLAG command to display the longword. Table 34 lista the

supported R5 boot fiege

/{batmapl
Same as /N5 bitmap!
[device_rame! A chsaracter string of up to 39 charactern.
BIG error message

Longer etrings cause 8 VAL TOO

Apart from length, the console makes no attempt to

interpret or velidate the device name. The console converts the string to
uppercase, then passes to VMB a string descriptor to this device name in RO.

Example:
>>> BOOT XQAO
{BOOT/R5:10 DUAO)

Boot using default boot
gspecified device.

flags and

2..
~-XQAOD

KN210 Firmware

3-45

3.9.2 CONFIGURE
The CONFIGURE command invokes an interactive mode thai permits
you to enter @22-bus device names, then generates a table of Q22-bus
I/0 page device CSR addresses nnd interrupi vectors. CONFIGURE is
similar to the VMS SYSGEN CONFIG utility. Thir command simplifies
field configuration by providing information that is typically available only
with a running operating system. Refer to the example below and use the
CONFIGURE cvmmand as follows:

Enter CONF1GURE at the r:~inienance mode prompt (>>>).

Enter HELP at the Device, Number? prompt to see a list of devices whose
CSR addresses and interrupt vectors can be determined.

Enter the device names and number of devices.

Enter EXIT to obtain the CSR address and interrupt vector assignments.

The devices listed in the HELP display are not necessarily supported by
the KN210-AA CPU.
Format:

CONFIGURE

3-46

KN210 CPU Module Set System Maintenance

Example:
>>>

CONFIGURE

Enter

device

configuration,

Device, Number?

HELP,

or EXIT

help

Devices:

LPV11i1
RLV12
pMvV11
RRD50

KXJ11
TSVOS
DELQA
RQC25

DLV11J
RXV21
DEQNA
KFQSA-DISK

DZQ11
DRV11W
DESQA
TQKS50

D2vll
DRV11B
RQDX3
TQK70

DFAO1
DPV11
KDASO0
TUBLE

RV20
CHAle

KFQSA-TAPE
CHB16

EKMV11l
CXY0B

1IEQ11
vCceol

DHQ11
QVss

DHV11
LNV11

LNV21

QPSS

psvll

ADV11C

AAV11C

AXV11lcC

RKWV1l1lcC
DRQ3B

ADV11D
vsval

ARV1L1D
I1BQO1

VCBOZ2
IDV11A

QDSSs
IDbV11B

DRV11J
ibvi1lc

IDV1i1D

IAV11A

IAV11B

MIRA

ADQ32

DTCO4

DESNA

I1IGQ1l1

Numbers:

255,

default

Device, Number?

Device,

Number?

tgk70

cxalé,Z

Device, Number?

dtc04

Device, Humber?

lpvll

Device, Number?

exit

Address /Vector

Assignments

~777514/200

LPV11

~774500,/260 TQK70
-76044{0/300

CXAlé

-760460/310

CXAle6

-761242/320

DTCO4

>>>

KN210 Fimware

3-47

3.9.3 CONTINUE
CAUTION: If the operating system state has not been properly saved
(halted), do not type cONTINUE. Doing so may cause the processor to hang.
The CONTINUE command causes the processor to begin instruction
execution at the address currently contained in the PC. It does not perform
a processor initialization. The console enters maintenance mode.
Format:

CONTINUE
Example:
>>>

COWTINUE

3-48

KN210 CPU Module Set System Maintenance

3.9.4 DEPOSIT
The DEPOSIT command deposits data into the address specified. If you
do not specify an address space or data size qualifier, the console uses the
last address space and data size used in a DEPOSIT, EXAMINE, MOVE,
or SEARCH command. After processor initialization, the default address
apace is physical memory, the default data size is longword, and the default
address is zero. [f you specify conflicting address space or data sizes, the
congole ignores the command and issues an error message.
Forma?:

DEPOSIT [qualifier_list] (address) (data) [dats...]
@Qualifiers:

'
Data control: /B, 'W, /L, /1Q, /N:icount), /STEP:{sizel, WRONG
Address space control /G, 1, /P. NV, /U, /M
Arguments:

{addressl

A longword addresa thst epecifies the first location into which deta is deposited.

The addrean can he an actusl addreas or & symrbolic eddress.

The data to be deposited If the specified data is larger than the deposit deta size,

datal

the firmware ignores the command and iesues an error response. If the specified
deta is smaller than the depaait data size, it is ext=nded on the left with zercs.

({dmta)

Additiona) data to be depogited 188 meany es can fit on the command line).

Example=
>>> D/P/B/N:1FF
»>>

D/V/L/N:3

1234

Clear

Deposit

at
>>>

D/N:8

D/N:200

>>>

D/L/P/H:10,/5:200

virtual

Loads

FFFFFFFF

first

GPRs

512

into

bytee

four

memory
RO

of physical

longwords

address

through RB

starting

1234.
with

Starting at previous address,

memory.

-1.

clear

513

bytes.

Depc:-1t

in the

first

the first 17 pages
memory starting at

longword of

in physical
location O.

KN210 Firmware

3-49

3.9.5 EXAMINE
The EXAMINE command examines the contents of the memory location or
register specified by the address. If no address is specified, + is assumed.
The display line consists of a single character address specifier, the physical
address to be examined, and the examined data.

EXAMINE uses the same qualifiers as DEPOSIT However, the 'WRONG
gualifier causes examines to ignore ECC errors on reads from physical
memory
The EXAMINE command also supports an /INSTRUCTION
qualifier, which will disassemble the instructions at the current address.
Format:
AMINE

[qualifier_list] [address]

Qualifiers:

Data control: /B, /W, /L, /Q, /N:|count), /STEP:(sizel, WRONG
Address space control: /G, /1, /P, IV, /U, M
Command specific:
ANSTRUCTION

[Disasesembles end displaye the VAX MACRO-32 instruction at the specified
address.

Arguments:
|[eddreas)

A longword addresa that epecifies the first location to be examined. The
asddress can be an actusl or = symbolic addrega. If no eddreas ie epecified,
+ is agaumed

3-50

KN210 CPU Module Set System Maintenance

Examples:
>>> EHAMINE PC

Examine the PC.

>>> EXAMINE SP
G O000000E 00000200

Examine the SP.

>>> EXAMINE PSL

Examine the PSL.

Examine PSL another way.

Examine R4

EXAMIWE PRS_SCBB

Examine the

00000011

(decimal).

Examine local memory O.

Examine

Disassamble

G O0000000F FFFFFFFC

M 00000000 041F0000

>>> EXAMINE/M
M 20000000

041F0000

>>> EXAMINE R4/W:5

through R9.

G 00000004 00000000
G 00000005 00000000
G 00000006 00000000
G 00000007

00000000

G 00000008

00000000

G 00000009 801D9000
>>>

>>> EXRMINE/P

2004R000

SCBB,

IPR

P 00000000 00000000
>>> EXAMINE/INS

20040000

P 20040000

11 BRB

>>> EXAMINE/INS/N:5

lst

20040019

P 20040019
P 20040024

DO MOVL
D2 MCOML

1~420140000,0420140000
@820140030,@§420140502

P
P
P
P

D2
7D
DO
DB

S~Q0E,@£20140030
RO, @8201404R2
178201404B2,R1
S“82A,B
44 (R1)

2004002F
20040036
2004003D
20040044

MCOML
MOVQ
MOVL
MFPR

>>> EXAMINE/INS
P 200400486

'
DB MEFPR

instruction

ROM.

from branch.

Look at next instruction.

S~§28B,B"46
(R1)

>>>

KN210 Firmware

3-51

XiT

- N

The EXIT command exite from maintenance mode (>>>) to the normal mode
prompt (>>). This command idles the CVAX chip. The maint command,
typed in lowercase letters from the normal mode prompt, returns you to
maintenance mode.
Format:

BEXIT

Example:
>»>»> BXIT
>> maint

From maintenance mode,

normal

From normal mode,

maintenance mode.

>5>

3-52

exit to

mode.

KN219 CPU Module Set System Maintenance

oxit to

3.9.7 FIND
The FIND command searches main memory starting at address zero for a

page-aligned 128-Kbyte segment of good memory, or a restart parameter

block (RPB). If the command finds the segment or RPB, its address plus
512 is left in SP (R14). If it does not find the segment or RPB, the conasole
issues an ervor message and preserves the contents of SP. If you do not
specify a qualifier, /RPB is assumed.
Format:

FIND [qualifier-list]
Qualifiers:

Command specific:
/MEMORY Sezrches memory for o page-aligned block of good memory, 128 Kbytes in length.
The search looks only et memory that is deemed usable by the bitmap. This
command leaves the contents of memory unchanged.

/RPB

Searches all of physicel memory for en RPB.
The search does not use the bitmap

the contents of memory
to qualify which pages are looked et. The command leaves
unchanged.

Examples.
>>> EXAMINE SP

Check the SP.

!
!

Look for a valid 128 Rbyte.
Note where it was found.

G 0000000E 00000000

>>> FIND /MEM
>>> EXAMINE SP
G 0000000E

00000200

»>>> FIND /RPB
2?2C FND ERR 0CCO00004

! Check for valid RPB.
! Noene to be found here.

>>>

KN210 Firmware

3-53

3.9.8 HALT
The HALT command has no effect.
other VAX consoles.

It is included for compatibility with

Format:

HALT
Example:
>>>

HALT

Pretend

to halt.

>>>

3-54

KN210 CPU Module Set System Maintenance

3.9.9 HELP
The HELP command provides information about command syntax and
usage.

Format:

HELP
Example:
>>>

RELP

Following is a brief summary of all the commands supported by
the console:

UPPERCASE
|

denotes a keyword that you must type in
denoctes an OR condition

{1
< >

denotes optional parameters

denotes a field that must be filled in
with a syntactically correct value

Valid qualifiers:

/B /W /L /Q /INSTRUCTION
/G /1 /V /P /M
/STEP: /N: /NOT
/WRONG /U
Valid commands:

DEPOSIT (qualifiers] <address>
EXAMINE [qualifiers] [address]
MOVE [qualifiers) <address>

[datum

[datum]]

SEARCH
<pattern>

[(qualifiers]

[mask]

SET BFLAG <boot_flags>
SET BOOT <boot_device>

SET HOST/DUP/DSSI <node_ number> (task]
/TAPE>
SET HOST/DUP/UQSSP </DISK
<controller number>

[task]

SET HOST/DUP/UQSSP <physical CSR_address>

[task]

SET HOST/MAINTENANCE/UQSSP/SERVICE <controller_number> [task]
SET HOST/MAINTENANCE/UQSSP <physical CSR_address> [task]
SET LANGUAGE <language_ number>

KN210 Firmware

3-55

SHOW BFLAG

SHOW BOOT

SHOW DEVICE
SHOW DSSI
SHOW ETHERNET

SHOW LANGUAGE
SHOW MEMORY [/FULL)
SHOW QBUS

SHOW RLV1Z2
SHOW UQSSP

SHOW VERSION
HALT

INITIALIZE
UNJAM

CONTINUE

START <address>

REPEAT <command>
X <address>

<count>

FIND [/MEMORY or /RPB]
TEST ([tfest code [parameters]]

BOOT

[/RS:<boot_flags> or /<bouot_flags>]

{[count)

[boot_device]

EXIT

CONFIGURE

HELP
>o>

3-56

KN210 CPU Module Set System Maintenance

3.9.10 INITIALIZE
The INITIALIZE command performs a processor initialization.
Format:

INITIALIZE

The following registers are initialized:

State at Initinlizstion

PSL

041F0000

IPL

ASTLVL

SISR

iICC8s

Bits <6> and <0> clear; the rest are unpredictable
0
80

RXCS
TXCS

MAPEI

CVAX cache

Disabled, all entries invalid

Instruction. buffer

Unaffected

Congole previous reference

Longword, physicsl, addrees 0

TODR

Unaffected

Main memory

Unaeffected

Gensral regiaters

Uneffected

Halt code

Uneffected

Bootstrap-in-progress flag

Unaffected

Internal restart-in-progress flag

Unaffected

KN210 Firmwase

3-57

The firmware clears all error status bits and initializes as follows:
1.

Clears any interrupts.

Initializes pr$_scbb to console SCB.

Initializes the IPR.
1pri$l_ipr

ipri%1_val

= 4

ipride_ipni

prd_astivi
pr_sisr
pré_ices

= *200000004
= Ar0D00GEIN
= Az00000000

pré_rrce
pré_tzce
pr$_mapen

= ~z00000000
= AxQDOG0080
= ArO0D00000

prd_ipl

= ~R0000001F

ctz_beee plua ctx$1_pal

~204 1F0000

Flushes and disables the chip cache.
Initializes the SSC.

Inttializes the console state:

Sets the current and previous reference to PHYSICAL and LONG
at address 0; current datum is then 0; clears the exit flag:
ca_baee plus cafl_addrees

ce_base plis cs§]_prev_addresr

ca_bsee plue ca$l_datus_size

= 4

cs_baee plus ca$q_datum

ca_hase plus cs$l_qv

plua 4°qualév_n
ctz_base plus ctz8b_exit

Example:
>>>

INIT

>>>

3-58

KN210 CPU Module Set System Maintenance

3.9.11 MOVE
The MOVE command copies the biock of memory starting at the source
address to a block beginning ai the destination address. Typically, this
command has an /N gualifier so that more than one datum is transferred.
The destination correctly reflects the original contents of the source,
regardiess of the overlap between the source and the data.
The MOVE command actually performs byte, word, longword, and
quadword reads and writes as needed in the process of moving the data.
Moves are supported only for the physical and virtual address speces.
Format:

MOVE [qualifier-list] {erc_address) {dest_address)
Qualifiers:

Data control: /B, /W, /L. /Q, /N:{count], /STEP:(size), WRONG
Address space control: IV, /U, /P
Arguments:

{src_address)
|dest_addressl

A longword address that specifies the first location of the source data to be

copied.

A longword addreas that apecifies the destination of the firat byte of dsta.

These addresses may be an actual addrese or a8 symbolic address.
address ie specified, + 18 agsumed.

If no

KN210 Firmware

3-59

Examples:
T YO
T T

>>>

EXAMINE/N:4

00000000

00000004

00000000

00000008

00000000

0000000C

00000000

00N05010

00000000

EXAMINE/N:4

200

destination.

Observe

source

data.

00000204

S85E04C1

00000208

O0PFBFBB

0000020C

5208A8DO

00000210

540CABDE

o B

58DD0520

00000200

>>>

Observe

>>> MOVE/N:4

200

>>> BEXAMINE/N:4

Move

the

data.

Observe moved data.

58DD0520

00000000

00000004

585E04C1

00000008

OOFF8FBB

0000000C

520BRBDO

00000010

540CABDE

>3>

3-60

KN210 CPU Module Set System Maintenance

3.9.12 NEXT
The NEXT command executes the specified number of macro instructions.
If no count is specified, 1 (one) is assumed.
After the last macro instruction is executed,
maintenance mode.

the console reenters

Format:

NEZXT [count]

The console implements the NEXT command, using the trace trap enable
and trace pending bits in the PSL and the trace pending vector in the SCB.
The following restrictions apply:

If memory management is enabled, the NEXT command works only if
the first page in SSC RAM is mapped in S0 (system) space.

QOverhead associated with the NEXT command affects execution time
of an instruction.

The NEXT command elevates the IPL to 31 for long periods of time
(milliseconds) while single-stepping over several commands.

Unpredictable results occur if the macro instruction being stepped over
modifies either the SCBB or the trace trap entry. This means that you
cannot use the NEXT command in conjunction with other debuggers.

Arguments:
[count]

A value representing the number of macro instructions to ezecute.

Examples:
>>>

EXAMINE

G 0000C00OF
>>>

REXT

>>>

MEAT

00000200

= 00000202
4

PC = 00000213
55>

KN210 Firmware

3-61

NOP

00000001

NOP

00000002

NOP

0u 000003

NOP

00000004

®WOP

00000005

WOP

00000006

NOP

00000007

NOP

00000008

BRB

0000000A

WOP

00000008

NOP

0000000C

HALT

0000000D

HALT

O0COOCOO0E

HALT

000O000O0F

HALT

00000010

HALT

00000011

HALT

NOP

ROP

NOP

ROP

00000000

LI BB

>>> EXAMINE/INS/N:10

>>>

DEP

>>>

P
>>>

P
>5»>

00000002

00000001
W

00000002
N

00000003
W

00000004
N

00000005
W

00000006

NOP

00000007

NOP

00000008

BRB

00000002

NOP

00000003

NOP

3-62

00000002

KN210 CPU Module Set System Maintenance

3.9.13 REPEAT

The REPEAT command repeatedly displays and exzecutes the specified
command. Press
to stop the command You can specify any valid
console command except the REPEAT command.
Format:

REPFAT {command)
Arguments:

{commeand|l A valid coneple commend other then REPEAT

Examples:
REPEAT EXAMINE PRS_TUDR

SAFET8FD

SAFET7900

] P

SAFE78D1

00000018

0000001B
0000001B

et Gd

SAFETBCE

00000018

SAFET7903

g God bed Gad bod Bmd ok Cnd Bl bmd Bt b

>>>

0Q00001B

SAFET7207

00600618

SAFE790A

0000001B

SAFE?90D

00000018

SAFET7910

00000018

SAFE793C

0000001B

SAFE793F

00000018

SAFE7942

0060G0O
1B

SAFET946

0000C01B

SAFE7949

00000018

SAFETI94C

0000018

SAYE794F

0CcoN001B

5~C

Watch

the

clock.

>>>

KN210 Firmware

3-63

3.9.14 SEARCH
The SEARCH command finds all occurrences of a pattern and reports the
addresses where the pattern was found. If the /NOT qualifier is present,
the command reports all addresses in which the pattern did not match.
Format:

SEARCH [qualifier_list] (address) {pattern) [(masgk)}]

SEARCH accepts an optional mask that indicates bits to be ignored (dont
care bits). For example, to ignere bit 0 in the comparison, specify @8 mask
of 1. The mask, if not present, defaults to 0.

A match occurs if (pattern AND mask complement) = (data AND mask

complement), where:

pattern is the target data

mask is the optional don't care bitmask (which defaults to 0)
data is the data at the current addvess
SEARCH reports the address under the following conditions:
MOT Quelifier

Match Condition

Action

Abgent
Absent
Preecent
Present

True
Falee
True
Falge

Report addrees
No report
No report
Report address

The address is advanced by the size of the pattern (byte, word, longword,
or quadword), uniess overridden by the /STEF quatlifier.
Qualifiers:

Data control: /B, W, /L., /Q, /N:{count}, /STEP:{sizel, WRONG
Address space control: /P, IV, U

Command-specific:
MNOT

3-64

Inverta the sense of the match.

KN210 CPU Module Set System Maintenance

Arguments:
{start_address| A longword addrees that specifies the first location subject to the search. Thie
address can be en actual eddress or @ symbolic eddress.
specified, + is assumed.

{patter)
[imask))

If no addrese is

The target data.

A longword containing the bits degired in the comparison.

Examples:
>>>

DEPOSIT /P/L/N:1000 0 O

tClear

DEPOSIT 300 12345678
DEPOSIT 401 12345678
DEPOSIT 502 87654321

'Deposit

some memory.

>>>

>>>
>2>>

>>>

some search data.

>>>
25>

SEARCH /N:1000 /ST:1 0 12345678

1Search for all occurrences
12345678 on any byte

00000300

12345678

fof

00000401

12345678

'boundary.

>>>

SEARCH /N:1000 O
00000300

12345678

/NOT O O

00000300
00000400

34567800

SEARCH /N:1000

00000404

00000012

L L B

>>>

000005L2

43210000

>>>

12345678

!Try on

longword bounderies.

1Search

for

12345678

SEARCH /M:1000 /ST:1
87654321

00000504

D0O00B765

00000505 00000087

00000502
00000503

FFFFFFFE
for odd

longwords

fon any boundary.

00875543

SEARCH /N:1000 /B 0 12

tSearch

00000303

'of the byte

00000404

SEARCH /N:1000 /ST:1 /W O FE1l1

for

all

cccurrences

12.

tSearch for all words that

>2>>

tcould be

>>>

'spin

>>>

non-zero

00000504 00008765

1Search

>>>

all

!longvords.

interpreted as &

(10$:bxb 10S$).
None were found.

KN210 Firmware

3-65

3.9.15 SET
The SET command sets the parameter to the value you specify.
Format:

SET (parameter) (value}
Parameters:
BFLAG

Sets the default R6 boot flags. The value must be @ hex number of up to 8

BOOT

Sets the default boot device. The value must be a velid device name as specified

HOST

Connects to the DUP or MAINTENANCE driver on the selected node or device.
Note the hierarchy of the BET HOST qualifiers below.

digits. See Table 3-4, VMB Boot Flags, for a list of the boot flags.

in the BOOT command description, Section 3.9.1.

MDUP-—Uees the DUP driver to execute local programs of a device on either the
D8S! bus or the §22-bus.
D881 mode—Attaches to the DSSI node.

charactere in length or @ number from 0 to 7.

A node is @ name up to 8

RUQESP—Attachee to the UQSSP device specified, using one of the
following methods:

/DISK m—Specifies the disk controller number, where n is @ number
from O to 2565. The resulting fized eddrees for n=0 is 20001488 for the
firet TMSCP controller, and the floating rank for n>0 is 26.
FTAPE n—Specifies the tape controller number, where n is 2 number
irom 0 to 266. The resulting fixed address for n=0 is 20001840 for the
first MSCP controller, and the floating rank for n>0 is 30.
cor_address—Sperifies the §22-bus /O pege CSR aeddress for the
device.

MAINTENANCE—Ezamines and modifies DSSI controller module configuration values. Does not accept a task value.

rngssP—

ISERVICE a—Specifies service for D8SI controller module n, where n
is 2 value from 0 to 3. (The resulting fized address of @ DSSI controller
module in meintenance mode is 20601910+4*n.)

leer_address—Specifies the Q22-bus 1/O page CSR address for the
DSSI controller module.

LANGUAGE Sets console language and keyboard type. If the current console termins] does
not support the Digital Multinetional Character Set (MCS), then thia command
has no effect and the console messsge sppeare in English. Values ere 1 through
15. Refer to Example 3-1 for the lsnguages you can select.

Qualifiers: Listed in the parameter descriptions above.

3-66

KN210 CPU Module Set System Maintenance

Examples:
>>> SET BFLAG 220
>>>

!
!

Sets boot flags 5 and 9 (See boot flag
in the BOOT command description.)

table

SET BOOT DUAO

>>> SET HOST/DUP/DSSI
Starting DUP

server...

DSSI

(SUSAN)

DRVEXR V1.0

Node

2-JUN-1989 10:01:35

DRVTST V1.0
HISTRY V1.0

D 2-JUN-1989 10:01:35
D 2-JUN-1989 10:01:35

ERASE
V1.0
PARAMS V1.0

D 2-JUN-1989 10:01:35
D 2-JUN-1989 10:01:35

DIRECT V1.0
D 2-JUN-1989 10:01:35
Copyright ® 1988
Digital Equipment Corporation
Task Name? PARAMS

Digital Equipment Corporation

STAT PATH

Path Block

FFBLlECC

1
4
S
2
3

PB
FPB
PB
PB
PB

FF8120D4
FF8121D8
FF8120DC
FFB122E0
FF81l24E4

Remote Node

DGS_S

DGS_R

MSGS_S

MSGS_R

Internal Path

0
0
0
0
0

0
0
0
816
50

0
0
0
3045
52

KAREN
WILMA
BETTY
DSSI1
3

RFX
RFX
RFX
VMS
VMB

V101
V101
V101
V5.0
BOOT

PARAMS> EXIT

Exiting...
Task Name?

Stopping DUP

server...

KN210 Firmware

3-67

>>> SET HOST/DUP/DSSI
Starting
DSS1

DUP

Node

(SUSAN)

0 PARAMS

server...

Digital Equipment

Corpcration

SHOW NODE

Parameter

Current

Default

Type

Radix

NODENAME

SUSAN

RF30

String

Ascii

PARAMS> SHOW ALLCLASS

Parameter

Current

Default

Type

Radix

ALLCLASS

Byte

Dec

PARAMS>

EXIT

Exiting...

Stopping DUP server...
>5>

3-68

KN210 CPU Module Set System Maintenance

3.9.16 SHOW
The SHOW command displays the console parameter you specify.
Format:

SHOW (parameter}
Parameters:
BFLAG

Displays the default R5 boot flags.

BOOT

Displays the default boot device.

DEVICE

Displays all devices displayed by the SHOW DSSI, SHOW ETHERNET, and

DSSI

Displaya the status of all nodes that can be found on the DSS] bus. For each
node on the DSS! bus, the firmware displays the node number, the node name,
and the boot name and type of the device, if available. The command does not

SHOW UQSSP commeands.

indicate whether the device contains a bootable image.

The node that issues the command is listed with a node name of© (asterigk).
The device information is obtained from the media type fieid of the MSCP
command GET UNIT STATUS. If a node is not running or is not capable of
running an MSCP server, then no device information iz displayed.

ETHERNET

Displays hardwere Ethernet address for all Ethernet adapters thet can be
found, both on-board and on the Q22-bus. Displaye as blank if no Ethernet
adapter is present.

LANGUAGE Displaye console language and keyboard type. Refer to the corresponding SET
LANGUAGE command for the meaning.
MEMORY

Displays mein memory configuration board-by-board.
MPULL—Additionally, displays the normally insccegsible aress of memory, such

as the PFN bitmap pages, the console scratch memory pages, the Q22-bus

scatter-gather maep pages. Also reports the addregses of bad pages, as defined

by the bitmep.

QRUS

Displays all Q22-bus /0 addresses that respond to an aligned word read, and
vector and deviee name information. For each addrees, the console displays the
address in the VAX I/O space in hex, the address as it would appear in the Q22bus I/0 space in octal, and the word data thet was read in hex. Also displaye

the vgtmé 2,‘,“ you should eet up and device name(s) that could be associated
with

the

CSR.

This commsand mey take several minutes to complete. Press[CVX] to terminate

the command. During execution, the commend disables the acatter-gather map
8o that it can search for memory on the @-bus.

KN210 Firmware

3-69

RLV12

Dieplaye all RLO1 and RLO2 diske that appear on the §22-bus.

UQssp

Displays the status of all disks and tapes thet can be found on the @22-bus that

gupport the UQSSP protocol. For each such disk v tape on the @22-bus, the
firmware displays the controller number, the controller CSR address, and the
boot name and type of each device connected to the controller. The command
does not indicate whether the device contains a bootable image.
This information is obtained from the media type field of the MSCP commsnd
GET UNIT STATUS. The console does not display device information if a node
is not running (or cannot run) an MSCP server.

VERSION

Displays the current firmware version.

Qualifiers: Listed in the parameter descriptions above.
Examples:
>>>

SHOW BFLAG

00000220
>>>

SHOW BOOT

DUAO

>>>

SHOW DEVICE

>>>ghow

device

DSSI Node
-DIA0O

DSSI Node
-DIAl

(SUSAN)

-xr£(0,0,*)

(KAREN)

-r£(1,1,*)

DSSI Node

(RF71)

(%)

UQSSP

Tape

-MURAO

-tm(0,0)

Ethernet

(RF71)

Controller

(772150)

(TK70)

Adapter

-ESA0

-se

-mop()

(08-00-2B-0C-C4-75)

3-70

KN210 CPU Module Set System Maintenance

>>>

SHOW DSSI

DSS1

Node

(SUSAN)

-rf(0,0,%)

=-DIAC

(RF71)

DSSI Node 1 (KAREN)
(RF71)
-DIAl -rf(1,1,%)
DSSI
>>>

Node 7

(*)

SHOW ETHERNET

Adapter

Ethernet

-ESA0 -se -mop()
>>>

SHOW LANGUAGE

English
>>>

(United States/Canada)

SHOW MEMORY

Memory 0:

00000000 to OO03FFFFF,

Total of 4MB,
>>>

(08-00-2B-~0C-C4-75)

O bad pages,

4MB,

0 bad pages

reserved pages

SHOW MEMORY/FULL

Memory 0:
Total

00000000 to OO3FFFFF,

of 4MB,

0 bad pages,

4MB,

0 bad pages

reserved pages

Memory Bitmap

-003F8000 to
Console

OO3FFFFF,

2 pages

Scratch Area

~003F4000 to

O003F7FFF,

pages

OO3FFFFF,

pages

Qbus Map
-003F8000
Scan

Bad

Pages

KN210 Firmware

3-71

>>>

SHOW QBUS

Qbus

/0 Space

(772150)

= 4000

-2000146A

(772152)

0B4O

-20001940

(774500)

0000

-20001942

(774502)

~20001F
40

(777500)

Scan

>»>>

SHOW

Qbus

Memory

Tepe

=MUBO

-tm(0,0)

S540W

(154)

RQDX3/KDAS0/RRD50/RQC25/X-DISK

(260)

TQKSO/TQK70/TUS1E/RV20/X~-TAFPE

(004)

IPCR

OBCO
0020

Space

UQSSP

»>>

[

-20001468

]

Scan

Controller

(772150)

(TK70)

VERSION

KN210~--A Vn.n
5>

3-72

KN210 CPU Module Set System Maintenance

3.9.17 START
The START command starts instruction execution at the address you

specify. If no address is given, the current PC is used. If memory mapping
is enabled. macro instructions are executed from virtual memory, and the

addresa is treated as a virtual address. The START command is equivalent
to a DEPOSIT to PC, followed by a CONTINUE. The START command doen
not perform a processor initialization.

Format:

START {address]
Arguments:

|addreas)

The address st which to begin execution. This address s loaded into the user's
PC.

Example:
>>>

START

1000

KN210 Firmware

3-73

3.9.18 TEST
The TEST command invokes a diagnostic test program specified by the test
number If you enter a test number of 0 (zero), all tests allowed to be
executed from the console terminal are executed. The console accepts an
optional list of up to five additional hexadecimal arguments.
Refer to Chapter 4 for a detailed explanation of the diagnostics.
Format:

TEST (test_number) [test_arguments]
Arguments:
{tegt_number)
{teet_argumentsa)

A two-digit hen number specifying the test to be executed.
Up to five additional test argumenta. These arguments are accepted

but they have no meaning to the console.

Example:
>>> TEST O

tExecute the power-up diagnostic

script.

'Test

power-up.

has

the

same

effect

51..50..49..48..47..46..45..44..43..42..41..40..39..38..37..36..35..
34..33..32..31..30..29..28..27..26..25..24..23..22..21..20..19..18..
17..16..15..14..13..12..11..10..,09..08..07..06..05..04..03..
>>>

3-74

KNZ10 CPU Module Set System Maintenance

3.9.19 UNJAM
The UNJAM command performs an 1/0 bus reset, by writing a 1 (one) to
iPR 55 (decimal}.
Format:

UNJAM
Example:
S>>

UNJAM

KN210 Firmware

3-75

3.9.20 X—Binary Load and Unload
The X command is for use by automatic systems communicating with the
console.

The X command loads or unloads (that is, writes to memory or reads from
memory) the specified number of data bytes through the console serial line
(regardless of console type), starting at the specified address.
Format:

X (addrees) (count) CR (line_checksum) {data) (date_checksum)
If bit 31 of the count is clear, data is received by the console and deposited
into memory. If bit 31 is set, data is read from memory and sent by the
console. The remaining bits in the count are a positive number indicating
the number of bytes to load or unload.
The console accepts the command upon receiving the carriage - turn.
The next byte the console receives is the command checksum, which is
not echced. The command checkeum is verified by adding all command
characters, including the checksum and separating space (but not including
the terminating carriage return, rubouts, or characters deleted by rubout),
into an 8-hit register initially set to zero. If no errors occur, the result is
zero. If the command checksum is correct, the console responds with the
input prompt and either sends data to the requester or prepares to receive
data. If the command checksum is in error, the console responds with an
error message. The intent is to prevent inadvertent operator entry into a
mode where the console is accepting characters from the keyboard as data,
with no escape mechanism possible.
If the command is a load (bit 31 of the count is clear), the console responds
with the input prompt (>>>), then accepts the specified number of bytes
of data for depositing to memory, and an additional byte of received data
checksum
The data is verified by adding all data characters and the
checksum character into an 8-bit register initially set to zero. If the final
content of the register is nonzero, the data or checksum is in error, and the
console responds with an error message.

If the command is a binary unload (bit 31 of the count is set), the console
responds with the input prompt (>>>), followed by the specified number of
bytes of binary data. As each byte is sent, it is added to a checksum register
initially set to zero. At the end of the {ransmission, the two's compilement
of the low byte of the register is sent.

3-76

KN210 CPU Module Set System Maintenance

if the data checksum is incorrect on a load or if memory or line errors occur
during the transmission of data, the entire transmission is completed, then
the console issues an error message. If an error cccurs during loading, the
contents of the memory being loaded are unpredictable.
The console represses echo while it is receiving the data string and
checksums.

The conscle terminates all flow control when it receives the carriage return
at ithe end of the command line in order to avoid treating flew control

characters from the terminal as valid command line checksums.

You can control the console serial line during a binary unload, using control
characters (<], [ows], [cwo], and so on). You cannot control the console
serial line during a binary load, since all received characters are valid
binary data.

The console has the following timing requirements:

e
e
e

[t must receive data being loaded with a binary load command at a rate

of at least one byte every 60 seconds.

[t must receive the command checksum that precedes the data within
60 seconds of the carmage return that terminates the command line.
[t must receive the data checksum within 60 seconds of the last data

byte.

If any of these timing requirements is not met, the console aborts the
transmission: by issuing an error message and returning to the console
prompt.

The entire command, including the checksum, can be sent to the console
as a single burst of characters at the specified character rate of the console
gerial line. The console is able to receive at least 4 Kbytes of data in a
single X command.

KN210 Firmware

3-77

3.9.21 1 (Comment)
The comment character (an exclamation point) 18 used to document
command sequences. [t can appear anywhere on the command line. All
characters following the comment character are ignored.
Format:

Example:
>>>

The

console

ignores

this

line.

>5>

3-78

KN210 CPU Module Set System Maintenance

Chapter 4

Troubleshooting and Diagnostics
4.1 Introduction
Thia chapter contains a description of KN210 ROM-based diagnostics,
acceptance test and troubleshooting procedures, diagnostics, and power-up
gelf-tests for common options.

4.2 General Procedures
Before troubleshooting any system problem, check the site maintenance

guide for the system's service history.

Ask the system manager two

questions:

°*

Has the system been used before and did it work correctly?

jave changas been made o the sysiem recently?

Three problems commonly occur when you make a change to the system:
®

Incorrect cabling

Module configuration errors (incorrect CSR addresses and interrupt
veciors)

[ncorrect grant continuity

Most communications moduies use floating CSR addresses and interrupt
veciors. If you remove a module from the system, you may have to change
the addresses and vectors of other modules. Microsystems Options lists
address and vector values for most options.

If you change the system configuration, run the CONFIGURE utility at
the maintenance mode prompt (>>>) to determine the CSR addresses and
interrupt vectors recommended by Digital.

See the MicroVAX Diagnostic Monitor User’s Guide for information about
the CONNECT and IGNORE commands, which are used to set up MDM
for testing nonstandard configurations.

See Appendix A for a summary of ULTRIX-32 Exercizer and Uerf
commands to help you troubleshoot and diagnose errors.
When

Troubleshooting and Diagnostics

4-1

troubleshooting, note the status of cables and connectors before you perform
each step. Label cables before you disconnect them to save time and prevent
you from introducing new problems.
If the system fails (or appears to fail) to boot the operating system, check the
console terminal screen for an error message. If the terminal displays an
error message, see Section 4.3. Check the LEDs on the device you suspect
is bad. If no errors are indicated by the device LEDs, run the ROM-based
diagnostics described in this chapter In addition, check the following:

If the ~vstem DC OK LED remains off, check the power supply and
power =upply cabling.
If no message appears, make sure the console terminal and the system
are on. Check the on/off power switch on both the console terminal and
the system. If the terminal has a DC OK LED, b sure it is on.
Check the cabling to the console terminal.

Check the hex display on the H3602-AB. If the display is off, check
the CPU module LEDs and the CPU cabling. If a hex error message
appears on the H3602-AB or the module, see Section 4.3. On power-up,

the display changes to reflect the power-up self-tests (see Section 4.3.5).
If you carnot get a display of any kind on the console terminal, try
another terminal.
If the system boots successfully, but a device seems to fail or an intermittent
failure occurs, check the error log first for a device problem. The failing

device is usually in one of the following areas:
CPU
Memory
Mass storage
Communications devices

4-2

KN210 CPU Moduie Set System Maintenance

4.3 KN210 CVAX ROM-Based Diagnostics
The KN210 CVAX ROM-based diagnostic facility, rather than the
MicroVAX Diagnostic Monitor (MDM), is the primary diagnostic tool for
troubleshooting and testing of the CPU, memory, Ethernet, and DSSI
subsysteme ROM:-based diagnostics have significant advantages:
e

Load time is virtually nonexistent.

The boot path is more reliable.

Diagnosis is done in a more primitive state.

loading of the operating system )

(MDM requires successful

The ROM-based diagnostics can indicate several different FRUs, not just
the CPU module. For example, they can isolate one of up to four memory
modules as FRUs. (Table 4-7 lists the FRUs indicated by ROM-based
diagnostic error messages.)
The diagnostice run automatically on power-up. While the diagnostics are
running, the LEDs on the H3602-AB display a he xaderimal countdown of
the tests from F to 4 (though not in precise revers. order) before booting
the operating system, and 2 to 0 while booting the operating system. A
different countdown appears on the console terminel

The ROM-based diagnostice are a collection of individual tests with
parameters that you can specify. A data structure called a script points
to the tests. (See Section 4 3
2.) There are several field and manufacturing
scripts. Qualified Customer Services personnel can also create their own
scripts interactively.
A program called the diagnostic executive determines which of the available
scripts to invoke
The script sequence varies if the KN210 is in a
manufacturing environment. The diagnostic executive interprets the script

to determine what tests to run, the correct order to run the tests, and the

correct parameters to use for each test.

The diagnostic executive also controls tests so that errors can be detected
and reported. It also ensures that when the tests are run, the machine is
left in a consistent and well-defined state

Troubleshooting and Diagnostics

4-3

4.3.1 Diagnostic Tests
Table 4-1 shows a list of the CVAX ROM-based tests and utilities. To
get this listing, enter T 98 at the maintenance mode prompt (T is the
abbreviation of TEST). The column headings have the following meanings:
¢

Test is the test code or wtility code.

Addressis the test or utility's base address in ROM. This address varies.
The addresses shown are only examples. If a test fails, entering T FE
displays the diagnostic state to the console. You can subtract the base
address of the failing test from the last_exception_pc to find the index
into the failing test's diagnostic listing.

Name is a brief description of the tes" or utility.

Parameters shows the parameters for each diagnostic test or utility.
Tests accept up to 10 parameters.
The asterisks (*) represent
parameters that are used by the tests but that you cennot specify
individually. These parameters are encoded in ROM and are provided
by the diagnostic executive.

4-4

KN210 CPU Module Set System Maintenance

Table 4-1:
Test

ol ]

Test and Utility Numbers

Addrees

Name

2004C000

De_SCB

20048200

CP_SCB

Parameters

2004D8DC

8SC_powerup

BSU0R0VED

Z004DTOE

CBTCR timeout

ese

2004D858

ROM logic test

200403920

CMCTL_powerup

32
o1
80
80
&0
82
B3
13

20040968
2004DABC
2004DB1C
2004DBOE
2004E1C5
2004E512
2004F7D8
2004E283

CMCTL regs
CQBIC _powerup
CQBIC regs
CQBIC_memory
Conzole serial
Prog timer
TOY clock
".aterval timer

MEMCSRO_addr #oseessoe
we
¢
¢8639%629
elari_havd end_baud ¢svese
which_timer wait_time_us **®
repeat_test_260mse_ea tolerance *9°
b

2004E9F?

VAXCMCTL.CDAL

don!_report_memory_bad repeat_count ®

2004E7308

Cache_mem_cgbsic

start_saddr end_addr addr_incy **°®

2004F DFO

Cachel_diag_md

.ddr_‘“fl' eSS PeHLY

2002 741A

fList diage

20( 47440

MSCP.QBUS test

'P~m s%eqen

2004F802

DELQA

device_num_sddyr ®%°°

2004F7DD

SSC RAM

]

2004F9A4

SSC RAM ALL

2004FB20

SSC regs

2004FC14

SIi_ext_loopbck

2004FF19

SIl_initintor

flll‘l_mt oo ed0

20040C0C

Skl target

run_tost **%9ees

200523D2

DSSI reaet

port_no time_seca

SHi_memoery

iner m.p‘tm m_m Lol
1o 2l

20062788

200527CD

NI_memory

incr tegt_pattern run_test °®o%%ee

200562BF8

S _registers

run_test *%°®

20052DC4

Ni_test

do_ext] where run_test ®°*0%%¢

2008392E

Virtual mode

SOOHGHehe

200583C04

Board reset

[L1

26053DB1

Check_for_intrs

20063D2F

MEM_setup_CSRs

QOO PRRES

20054323

MEM _bitmap

*¢¢ mark_hard_SBEs #e*99°

20064758

MEM data

stert_add end_sdd add_incr cont_on_err *¥27%°

2005481C

MEM_byte

20054A31

MEM _address

start_add end_add add_incr cont_on_egr **%¢*

20054BC3

MEM_ECC _error

etart_add end_edd add_incr cont_on_err *°%°%°

start_add end_edd add_iner cont_on_err #°®*%°

Troubleshooting and Diagnostics

4-5

Table 4-1 (Cont.):

Test and Utility Numbers

Test

Address

Naeme

Parametere

20056084

MEM_maekd_erra

etart_add end_edd add_incr cont_on_err #2°°%°

2006526
E

MEM _correction

start_edd end_sdd add_incy cont_on_ery *2900°

20056471

MEM_FDM_logic

*o% cont_on_ery $000®

2005564490

MEM _eddr_shrta

start_add end_add ° cont_on_err pat2 pat3
[ 21

20066097

20056222

MEM_count_errs

start end incr cont_on_err time_seconds ¢#ve®
First_board Last_board Saft_erve_sllowed *o029®

20058563C

Cache_memory

addr_incy ®%ovssesee

20056888

Utilitiea

MEM _refrech

Enxpnd_err_msg get_mode init LEDe elr_ps_
ent

2005698C

List CPU rege

200572AF

Create script

RERBOS

20057A0F

M76386 present

20057A3C

R30080_cache

L
L2

20067A83

R3000_fpu

20057A68

R3000_ub

20067A7D

R3000_reg_intrf

loop run_test **°

20067497

R3000_buf intrf

increment pattern start_sdd end_gdd *%*

20067AB1

R3000_mem_intrl

increment pattern start_add end_add **°

20057ACB

R3000_interrupt

run_teat

20057AES

R3000_mov_inver

increment * start_edd end_add °°°

20087AFF

R3000_write_buf

Parameters that you can specify are written out, as shown in the following
examples:
54

2004ES557

Virtual

20053CéD

MEM bitmap

mode

LA X

***

]

mark_Hard SBEs

***w#w

The virtual mode test on the first line contains several parameters, but you
cannot specify any of them. To run this test individually, enter:
>>>

The MEM_bitmap test on the second line accepts ten parameters, but you
can specify only the fourth one. To mark pages bad in the bitmap for singlebit or multibit errors, enter a 1 in the fourth parameter field:
>5»>>

000
1

You must enter a value of either 0 (zero) or 1 (one) for the first three
perameters. (0 is used in this example.) The values have no effect on
the test; they are simply placeholders for the first three parameters. You

4-6

KN219 CPU Module Set System Maintenance

do not have to specify a value for parameters that iollow the user-defined
parameter.

4.3.2 Scripts
Most of the tests shown by utility 9E are arranged into scripts. A script
18 a data structure that points to various tests and defines the order in
which they are run. Different scripts can run the same set of tests, but in
a different order and/or with different parameters and flags. A script also
contains the following information:

The parameters and flags that need to be passed to the test.

Where the tests can be run from. For example, certain tests can be run
only from the EPROM. Other tests are program-independent code, and
can be run from EPROM, cache diagnostic space, or main memory to
enhance execution speed.

What is to be shown, if anything, on the console.

What is to be shown, if anything, in the LED display.

What action to take on errors (halt, repeat, continue).

The power-up script runs every time the system is powered on. You can
also invoke the power-up script at any time by entering T 0.

Additional scripts are included in the ROMs for use in manufacturing and

engineering environments.

Customer Services personnel can run scripts and tests individually, using
the T command. When doing so, note that cert.in tests may be dependent
upon a state set up from a previous test. For this reason you should use
the UNJAM and INITIALIZE commands, described in Chapter 3, before
running an individual test after the operating system has crashed or has
been halted. You do not need to use these commands on system power-up,
however, because system power-up leaves the machine in a defined state.

Customer Services personnel with a detailed knowledge of the i 1'210
hardware and firmware can also create their own scripts by using the 9F
utility. (See Section 4.3 4.)

Troubleshooting and Diagnostics

4-7

Table 4-2 lists the scripts that are available to Custorser Services.

Table 4-2:

Scripts Available to Customer Services

Beript®

Enter with
TEST
Commend

Description

Soft seript created by de_teat8{ Enter T 8F to create.

Al AA,
AB, AC,

Common section of power-up script. Scripis AA, AB, end AC
invoke thie ecript et power-up.

0.3

A7, A8

Memory test portion invoked by Script AS8. Revruns the memory

Memory acceptance. Running Script AB with Script A7 testa

Memory tests. Halts and reporta the fivet ervor. Does
not reset
the bitmap or busmap.

AA, 0

Console SLU. Invokea Seripts BA, BC, and A). Does not invoke

AC,3

AE
AF

AE. AD
AF

BA, 2, AA

BC,AA AC,0,3

AA, A5, BD,BE

A4A BF

testns without rebuilding erd reinitielizging the bitmep. Rum
Seript A3 once befare running Script A7 esparately (o ellow
mapping cut of both aingle-bit and double-bit main memory
ECC ervore.

main memory more extensively. It enables hard single-bit and
multibit main memory ECC errore to be marked bed in the
bitmep. Invokes Script A7 when it hee completed ito testa.

any tests directly.

Power-up. Invokes Scripte BC end Al.

teots directly Invoked st power-up.

Duasa not invoke any

Coneole program. Runs memory teate, marks bitmap, resets
busmap, and reeets caches. Calls Seript AE.

Console program. Resets memory CSRe and resets caches.
Congole vogram. Resets busmep and resets caches.
Initie] power-up ecript for console SLU before first console

ennouncement. Invoked at power-up.

Called by Scripts AA end AC. Provides console announcements.
Invoked at power-up.

Runs R3000 CPU, flosting-point unit, cache, TLB (translation

lockzeide buffer), and 1/0 module interface tasis.

Runs KN210 /0 module teeta.

'Scripts A2-AS, B6-B3, and B5 ere for menufacturing use. They should not be used by
Customer Services. Scripts AB and BB are used to test the QDSS, which is not supported.
Seripts BD, B4, end B8-B9 are not used.

4-8

KN210 CPU Module Set System Maintenance

‘

In most cases, Customer Services needs only the commands shown in

Table 4-3 for effective troubleshooting and acceptance testing.

Table 4-3:

Commonly Used Fleld Service Scripts

Command

Description

Automaticelly invokee the proper acripts; runs the same tests es during powerup.

Primarily runs the memory tests; halts upon firet hard or soft error.

Memory acceptance ecript; merkes hard multibit end single-bit ECC ervors in

the bitmap. Script A8 calls Script A7 when this commend is entered. Secript
A7 contains the memory tests that will ontinue on ervor.
A7

Cen be run vy itself: useful when you want to bypeaes the bitmap test.

Power-up ecript that can be run by iteelf. Bypagses the bitmap test.

4.3.3 Script Calling Sequence
Actions at Power-Up

In a nonmanufacturing environment where the intended console device is
the serial line unit (SLU), the console program (referred to as CP below)
performs the following actions at power-up:
1.

Rune the IPT.

Assumes console device 18 SLU.

Calls the diagnostic executive (DE) with Test Code = 2.

DE determines that the environment is nonmanufacturing from
H3602-AB. (Manufacturing sets a jumper on the H3602-AB for
testing.)

DE selects script sequence for console SLU.

¢.

DE executes Script BA.

—
d.

Script BA directs DE to execute test. (Console announcements
are off.)

DE passes control back to the CP.

Establishes SLU as console device (whether or not SLU test passed).
Prints banner message.

Displays language inquiry menu on console if console supports MCS
and any of the following is true:

Troubleshooting and Diagnostics

4-9

Battery is dead.

H3602-AB switch set to action (language inquiry).

Contents of SSC NVRAM are invalid.
7.

Calls DE with Test Code = 3.
a.

DE executes Script AC.

Script AC directs DE to execute Scripts BC and Al.
~

Secript BC directs DE to execute tests. (Console announcements
are on.)

Script Al directs DE to execute tests. (Console announcements
are on.)

DE passes control back to CP.

CP issues end message and >>> prompt. CP may exit to >> prompt.

Actions After You Enter T O

In a nonmanufacturing environment where the intended console device is
the SLU, the console program (CP) performs the following actions after you
enter T 0 at the console prompt (>>> T 0):
1.

Calls the diagnostic executive (DE) with Test Code = 0.

DE determines environment is nonmanufacturing from H3602-AB
switch setting.

DE executes Script AA.

Script AA directs DE to execute Scripts BA, BC, and Al.
~

—

Script BA directs DE to execute tests. (Console announcements
are off.)

Secript BC directs DE to execute tests. (Console announcements
are on.)

Seript Al directs DE to execute tests. (Console announcements
are on.)

DE passes control back to the CP.

CP prints end message and >>> prompt. Console may exit to >> prompt.

Note that although the sequence of actions is different in the two cases
above, the same tests (those in Scripts BA, BC, and Al) are run both times.

4-10

KN210 CPU Module Set System Maintenance

4.3.4 Creating Scripts
You can create your own script, using utility 9F to control the order in which
tests are run and to select specific parameters and flags for individual tests.
In this way, you do not have to use the defaults provided by the hard-wired
scripts.

Utility 9F also provides an easy way to see what flags and parameters are
used by the diagnostic executive for each test.

Run test 9F first to build the user script (see Example 4-1). Press[fsam] to

use the default parameters or flags, which are shown in parentheses. Test
9F prompts you for the following information:

Script location. The script can be located in the 1-Kbyte NVRAM in
the SSC, in the 128-Kbyte mass storage interface (MSI) RAM in the
SII chip, or in main memory. A script is limited by the size of the data
structure that contains it. A larger script can be developed in main
memory than in MSI RAM, and a larger script can be built in MSI
RAM than in NVRAM.

A escript cannot, however, always be located in main memory. For
example, a script that runs memory tests will overwrite the user script,
since the diagnostic executive cannot relocate the user script to another
area. The diagnostic executive notifies you if you have violated this type
of restriction by issuing a script incompatibility message.
Test number

Run environment. This defines the environment from which the actual
diagnostic test can be run. The choices are 0 = ROM, 1 = MSI RAM, 2
= Main Memory, and 3 = Fastest Possible. Choose number 3 to select
the fastest possible environment that will not overwrite the test.
Repeat code
Error severity level

Console error report
Script error treatment
LED display

Console display
Parameters

Troubleshooting and Diagnostics

4-11

Example 41 shows how to build and run a user script.
The utility displays the test name after you enter the test number, and the
number of bytes remaining after you enter the information for each test.
When you have finished entering tests, press [feum] at the next Next test
number: p . mpt to end the script-building session. Then, type T A0 [Ream]
to run the new script.

You cannot review or edit a script you have created.
Example 4-1:

Creating a Script with Utiity 9F

SP=201406A8
Create

script

Script

starts at 2011FC00

1024 bytes
Next

test

in ?[0=SSC,

1=Diag_RAM,

peossible]

:70

>2=count<FF]

(O=no,

l=on error,

severity?

>>Console

error

(0,

report?

R3000_cache >>LED on entry

[0=NO,

number

(70):

1=Diag_ RAM,

2=RAM,

[O=no,

1=on error,

2=forever,

(0):0

R3000_fpu >>Error severity?

(0,

(2):2

R3000_fpu >>Conscle error report?

[O=none,

R3006_fpu >>Stop script

[0=NO,

on error?

>>LED on entry

R3000_f£pu >>Console
Next test

1=full]

1=YES]

(07):

on entry

(71):

left

number

1009 bytes

:A0

script

left

Next test number

>>> T AQ
70..7%..
>>>

4-12

3=fastest

(0):3

>2=count<FF)]

bytes

(1):1

:71

R3000_fpu >>Repeat?

1010

1=full]

1=YES]

left

R3000_fpu >>Run from ?[0=ROM,

R3000_£fpu

(2):2

(07):

R3000_cache >>Conscle on entry

possible)

3=fastest

2=forever,

[O=none,

R3000_cache >>Stop script on error?

1017 bytes

2=RAM,

(0):0

R3000_cache >>Error
R3000_cache

1=Diag RAM,

(0):3

R3000_cache >>Repeat?

test

left
anumber

R3000_cache >>Run from 7[0=ROM,

2=RAM|

KN210 CPU Module Set System Maintenance

(1):1

Ezample 4-2 show ¥ » ecript-building procedure to follow if (a) you are
unsure of the test ...mber to specifv. and (b) you want to run one test
repeatedly. If you are not sure of the test number, enter 7 at the Next test
number: prompt to invoke test 9E and display t{est numbers, test names,
2nd so on. To run one test repeatedly, enter the following sequence:
1.

Enter the test number (40 in Example 4-2) at the Next test number:

Enter a0 at the next Next test number: prompt.

prompt.

Enter T a0 to begin running the script repeatedly.

Press [fsam] at the next Next test number: prompt.
Press [cvic] to etop the test.

The seguence above is a useful alternative to using the REPEAT console
command to run a test, because REPEAT (test) displays only line feeds; it
does not display the console test announcement.

Troubleshooting and Diagnostics

4-13

Example 4-2:
>>>t

Listing and Repeating Teste with Utliity SF

SP=201406A8
Create scraipt in
Scraipt starts at
24 bytes left
Next test number
Test

?{0=SSC,
201407E0

1=z

Diag_RAM,

2=RAM]

]

Address

Name

Parameters

Cé
C?
34

F
C
2004p200
2004D6DC
2004D79E
2004D85F

De_SCB
CpP_sSCB
SSC_powerup
CBTCR timeout
ROM logic test

fotannted
sen
*

47
40

2005608B
20056216

KEM Refresh
WTMEM Count _Errs

start end incr c©ont _on_err time_seconds *“*A%s
First board Last board Soft exra allowed wevwean

200%5687C

Utilities

Expnd_err
msg get _mode init_LEDs clr_ps_cnt

20056530

9C
9F
70

20056980
20057195
2005768B8

73
74
75
76

200578F9
20057913
200%792Dp
20057947

71
72

200578CF
200578E4

77
78

20057961
20057C47

bytes

test

Cache_memory

addr_incr

Liat

CPU regs
scrapt
R3I000_cache

wessesiow

.
tucnae
¢

Create

R3000 fpu
R3000 tlb

*
*

R3000_
_reg_intrf
R3I000 buf intrf
23000 mem intrf
RI000TM
1nterrupt

R3000
_mov_inver
RI000TM nrxte buf

loop run_test
*%¢
incr pattern start
incr pattern start
run_test

add end add
add end add

run _test
*=*

incr * start _add end_add **
*

lef:
number

:40

MEMCount Ezts>»?un from 7(0=ROM, 1=Diag RAM, 3=fasteat possible)
MEM _Count Errs>>Pepeat’
{0=no, 1=0n error,2=forever, >2=count<FF}

MEH Count

Errs))Lrtor severity °

(C,1,2,7)

HEM Count Etts)»Console arror report?
MEM Count Erx4)>5top script on error?
MEM Count _Erra>>LED on entry
(04)
MEM _Count “Ercs>>Console

MEM

Count

.rrg>>

First

MEM _Count _Errs>> Last

entry

board

anrd

(40)-

00000001

Soft_
_errs_allowed

S bytes Teft
test

bytes

test

>»>t

40
40.

number

(2)-

00000004

000CO0004

00000000

(00000004

FFFFFFFF

? (FFEFFFFF)

scrapt

left

4C. .40
. 40.
40

number

.40..40..40
.~C

40.

.40

40..40.
.40. .40..40

40..40..40

#4LO-003600

>>>

4-14

(0):
3
(0):0

(O=znone,l=full]
(1):
[0=RO, 1=YES]
(1):

00000001

MEM Count Errs>>

*¢

KN210 CPU Module Set System Maintenance

4.3.5 Console Displays
Example 4-3 shows a typical console display during execution of the CVAX
ROM-based diagnostics (power-up).
Example 4-3:

Consoie Display (No Errors)

KN21G-A Vn.n

Paerforming Normal

System Tests

51..50..49..48..47..46..45..44..43..42..41..40..39..38..37..36..35..

34..33..32..31..30..29..28,.27..26..25..24..23..22,.21..20..19..18,.
17..16..15..14..13..12..11..10..09..08..07..06..05..04..03..,
Tests

completed

>>>

The first line contains the module (KN210-A) and the firmware version
(Vn.n).
The numbers on the console display do not refer to actual test numbers.
Table 44 shows the actual ROM-based diagnostic tests that run during
power-up.

Table 4-4:

Tests Qun During Power-Up

Number

51/91

34/C7

18/C6

50/ 80

33/ 46

17/ 46

49/ 33

32/C2

18/ BA

48/ 32

317/ 4F

16/ BC

47/ 60

30/ 4E

14/ 86D

46/ BB

29/ 4D

i13/5E

45/ 31

28/ 4C

12/ 6F

44/ 49

27/ 4B

11/72

43/ 30

26/ 4A

10/71

42/ 62

25/ 48

9/70

41/862

24/ 47

B/78

40/ 63

23/ &0

7/173

39/Ch

22/ 44

6/74

"8/34

21/ 80

6/76

37/CH

20/ 64

4/76

36/57

19/ 34

3/41

Displayed/Test Run

Displayed/Test Ram

Displayed/Toat Run

36/ 56

Troubleshooting and Diagnostics

4-15

During execution of the IPT, normal error messages are displayed if the
console terminal is working. Console announcements, such as test numbers
and countdown, however, are suppressed. Tests continue to run after the
IPT, up to and including the appropriate console test.
Diagnostic test failures, if specified in the firmware script, produce error
displays in the forinats shown in Examples 44 and 4-5.
Example 4-4:
?46

07 FE

Sample Output with Errors (CVAX)
10 0002

P1=002F0000 P2=00000000 P3=00000000 P4=00FF0000

p5=00000000

P6=00000000 P7=00000000 PB=00000000 P9=00FF0000

P10=00000000

r0=00000000

rl1=00010000

r2=555555%55

r3i=00000080

r4=RARARRAR

r5=00000080

r6=01EF0000

r7=20000144

rB8=00010000

ERF=20140770

Normal

operation

not

possible.

>>>

Example 4-5:
773

35 FE

Sample Output with Errors (R3000)
00

0002

P1=00000100

P2=00000000 P3=00000000

P4=00000000

P5=00000000

P6=00000000

P7=00000000 P8=00000000

P9=00000000

P10=55555555

epc=BFC15850

sr=B0400000 badvaddr=00000000

gp=00000000

sp=AOFF7BBO

Normal

operation

not

cause=30002000

fp=00000000

possible.

>>>

The errors are printed in a five-line display. The first line has six fields:
Test

Severity

Error

De_error

Vector

Count

Test identifies the diagnostic test. In Example 44, the test is 46.

Severity is the severity level of a test failure, as dictated by the script.
In Example 44, 2 is the severity level. Failure of a severity level 2 test
causes the display of this five-line ervor printout and halts en autoboot.
An error of severity level 1 causes a display of the first line of the error
printout but does not interrupt an autoboot. Most tests have a severity
level of 2.

4-16

KN210 CPU Module Set System Maintenance

Error is two hex digits identifying, usually within 10 instructions,
where in the diagnostic the error occurred. This field is also called the
subtestiog. In Example 4—4, 07 is the area where the error occurved.

De_errvor (diagnostic executive error) signals the diagnostic's state and
any illegal behavior. This field indicates a condition that the diagnostic
expects on detecting a failure. FE or EF in this field means that an
unexpected exception or interrupt was detected. FF indicates an error
as a result of normal testing, such as » miscompare. The possible codes
are:

FP—Normal error exit from diagnostic
FE—Unanticipated interrupt (as in Example 4—4)
FD—Interrupt in cleanup routine
FC—Interrupt in interrupt handler
FB—Script requirements not met
FA—No such diagnoetic
EF—Unanticipated exception in executive
¢

Vector identifies the SCB vector (10 in the example above) through

which the unexpected exception or interrupt trapped, when the de.
error field detects an unexpected exception or interrupt (FE or EF).
e

Count is four hex digits. It shows the number of previous errors that
have occurved (two in Example 4—4).

Lines 2 and 3 of the error printout are parameters 1 through 10. When
the diagnostics are running normally, these parameters are the same
parameters that are listed in Table 4-1.

Troubleshooting and Diagnostics

4-17

When an unexpected machine check exception or other type of exception
occurs during the executive (de_error is EF), the stack is saved in the
parameters on lines 2 and 3, as listed in Tables 4-5 and 4-6.

Table 4-5:

Values

Saved,

Machine

Check

Exception

During

Executive (CVAX)
Perameter

Value

Contents of SP, pointa to vector value in P2

P2
P3

Vector = 04, vector of exception 04-FC, 00 = Q-bus
Address of PC pointing to failed instruction, P9

Byte count = 10

PB
P&

Machine check code
Mast recent virtual address

internal etate informetion 1

Internal state information 2

PC, points to failing instruction

P10

PSL

Table «-6:

Valucs Saved, Exception During Executive (CVAX)

Peremete~

Valve

Contents uf SP, points to vector value in P2

P2
P3

Vector = nn, vector of exception 04-FC, 00 = Q-bue
Addreas of PC pointing to failed instruction, P4

PC, points to instruction following (ailed instruction

PSL

Contenta of stack

Contents of stack

Contenta of stack

P10

Contents of stack

4-18

KN210 CPU Module Set System Maintenance

Lines 4 and 5 of the error printout are general registers RO through R8 and
the hardware error summary register.

When returning a module for repair, record the first line of the
error printout and the version of the ROMs on the module repair
tag.

Table 4-7 lists the hex LED display, the default action on errors, and the
most likely FRUs. The table is divided into IPTs and scripts.
The Default on Error column refers to the action taken by the diagnostic
executive under the following circumstances:
o

The diagnostic executive detects an unexpected exception or interrupt.

A test fails and that failure is reported to the diagnostic executive.

The Default on Error column does not refer to the action taken by the
memory t{ests. The diagnostic executive either halts the script or continues
execution at the next test in the script.
Most memory tests have a continue on error parameter (labeled cont_on_
error, as shown in test 47 in Example 4-2). If you explicitly set cont_on_
error, using parameter 4 in a memory test, the test marks bad pages in
the bitmap and continues without notifying the diagnostic executive of the
error. In this case, a halt on error does not occur even if ynu specify halt
on error in the diagnostic executive (by answering Yes to Stop script on
error? in Utility 9F), since the memory test does not notify the diagnostic
executive that an error has occurred.

Figure 4-1 shows the LEDs on the KN210 CPU. They correspond to the
hex display on the H3602-AB.
Figure 4-1:

KN210 CPU Moduie LEDs

Green
DC OK LED
Red LEDs

Value On

Value Off

Troubleshooting and Diagnostics

4-19

Table 4-7:
Hezx

LED

KN210 Console Displays and FRUs

Normal Errvor

Console Conscle Default

Display Display om Error

Description

FRU!

Initial Power-Up Tests
F
D

None
None

None
Nene

Loop on test
Loop on test

Power-up
WAIT _POK

7,.1,6,6
1

4
7

None
None

Loop on self
Loop ontest

Entering IPT
SLU_EXT_LOOPBACK?

1
8,91

Continue

Utilitien

1,2

742

Continue
Continue

Check_for_intre
S8C_power-up

1,2
1,2

Continue

CONSOLE_SERIAL

1,2

Seript BA
C

None

None
None

C
7

None

Cé
180

End of script.

Seript AC
Invoke ecript BC.
invoke seript Al.
End of ecript.

1jn the case of multiple FRUs, refer to Section 4.5.2 for further informatica. If a problem
recurs with the eame FRU, check that the tolerance for system power supply +6 Vdc, +12 Vde,
and ac ripple ere within epecification.

2This test runs only if the power-up mode switch on the K3602-AB is set to the test pogition.
See Section £8.3.

FRU key:

1 = KN210 CPU module
2 = KN210 VO module
3 = MSE50 moedule
4 = Memory interconnect cable
B = @22-bus device
8 = Q22/CD backplane
7 = System power supply

8 = H3602-AB CPU /O panel
9 = H3602-AB cable
10 = CPU and /0 meduie interconnest cable

4-20

KN210 CPU Module Set System Maintenance

Table 4-7 (Cont.):
Hez

LED

KN210 Console Displays and FRUs

Normal Ervor
Comnsole Comsole Default

Display Display om Error

Description

FRU!

Script AA
Invoke script BA.

{nvoke script BC.
Invoke acript Al.

End of ecript.

Seript BC

8
8

g
50

21
780

Coniinue
Continue

CQBIC_power-up
CQBIC_registere

i
1

9
8

733
732

Continue
Continue

CMCTL_power-up
CMCTL_regioters

)
1

49
48
47

760

Continue

M7638_present

10,2, 1

%8B

Continue

731

Continue

kivv_setup_CSRs

1,3,6,%

2
)

&4
43

749
730

Continue
Halt

MEM_FDM _logic
MEM _bitmep

3.1,4,8
3.1,4,8

gietere

End of exript.

Script Al
Invoke script BD.

End of ecript.

'in the case of multiple FRUs, refer to Section 4.5.2 for further information. If a problem

recurs with the same FRU, check that the tolerance for eystem power supply +6 Vée, 12 Vde,
and ac ripple are within specification.

FRU key:
1 = KN210 CPU module
2 = KN210 /O mod: le

3 = MB8E50 module

4 = Memory interconnect cable

5 = @22-bus device
6 = Q22/CD backplane
7 = Syslem power supplv
8 = H3802-AB CPU LU penel
9 = H36802-AB cable

10 = CPU end /O module interconnect cable

Troubleshooting and Diagnostics

4-21

Table 4-7 (Cont.):
Hez
LED

KN210 Console Displays and FRUs

Normal Ervor

Conscle Console Defnult
Display Dieplay om Ervor

Description

FRU!

Seript BD
C

762

Continue

PROGC TIMER_O

C
C

41
40

762
%63

Continue
Continue

PROG_TIMER_1
TOY_CLOCK

1
1

Continue

SSC_RAM

734

Continue

ROM logic test

*Ch

Continue

SSC_registers

Continue

Sil_memory

Continue

INTERVAL_TIMER

Continue

CBTCR_timeout

Continue

8SC_RAM _al}

]

Continue

MEM_dota

3.1,4,8

Continue

MEM_oddr

3,1,4,8

]
2]

28
27

74C
4B

Continue
Continue

MEM_ECC _error
MEM_masked_ervors

3.1,4,8
31,46

9
2
]
B

26
24
23
22

248
47
740
44

Continue
Continue
Continue
Continue

MEM_aeddress_chorts
MEM _refresh
MEM_count_erve
CACHE1_MEMORY

3,1,4,8
3.1,4,8
3,1,4.6
1,3, 4,8

]

748

74E

780
764

Continue

CACHE1_DIAG_MODE

Continue

MEM _byte

Continue

MEM _correction

Continue

CQBIC_MEMORY

Continue

VIRTUAL_MODE

3.1,4,¢

3,1, 4,8

1,3,6,4.8
1.3, 4,6
-

'In the caege of multiple FRUs, refer to Section 4.5.2 for further information. If e problem

recurs with the same FRU, check that the tolerance for eyetem power supply 48 Vde, +12 Vdc,
and ac ripple ere within specifiestion.
FRU key:

1 = KN210 CPU medule
2 = KN210 IO module

3 = MSES0 module
4 = Memory interconnect cahle

6 = Q22-bus device

6 = Q22/CD bachkplane
7 = System power supply

8 = H3802-AB CPU VO panel
8 = H3802-AR cable

10 = CPU end /0 module interconnect aable

4-22

KN210 CPU Module Set System Maintenance

‘

Table 4-7 (Coi:.):
Hez

LED

KN210 Console Displays and FRUs

Normeal Ervor

Conssole Conscle Default

Display Dieplay on Error

Description

FRO!

Scwipt BD
(Continuved from previous page.)

C
C

19
18

734
¥CH

Continue
Continue

ROM _logic
SCC_registers

1
1

76A

Continue

VAX CMCTL CDAL

]

746

Continue

CACHE_MEM_CQBIC

1,3,6,4,6

76C

Continue

Sll_initietor

2,1

5
3
A
A
A

i3
12
11
10
09

76E
75F
772
(4p
770

Cuntinue
Continue
Continue
Continue
Continue

Ni_memory
NI_test
R3000_tlb
R3000_fpu
R3000_cache

2,1
2,1
1
1
1

A
A
A
A
A

08
o7
06
06
04

75D

778
7?3
714
775
778

Continue

Continue
Continue
Continue
Continue
Continue

Sil_target

R3000_write_buf
R3000_reg_intrf
R3000_buf_intef
R3000_mem_intrf
R3000_interrupt

2,1

1
1,2
2.1
3,1,4,6
1,2

741

Continue

Board reset

1,6

74F
4E

Halt
Halt

MEM_deta
MEM_byte

3,1,4,6
3,1,4,6

End of acript.

Seript AS

9
9

4F
4E

'in the ceee of multiple FRUe, refer to Section 4.6.2 for further information. If & problem
recure with the asame FRU, check that the tolerance for system power supply +b Vdc, +12 Vdc,
end ac ripple are within specification.
FRU key:

1 = KN210 CPU module
2 = KN210 /O module
3 = MS8650 module
4 = Memory interconnect cable
6 = @22-bus device
8 = Q22/CD backplane
7 = Syatem power supply

8 = H3602-AB CPU /O panel
9 = H3602-AB cable

10 = CPU end /O module interconnect cable

Troubleshooting and Diagnostics

4-23

Table 4-7 (Cont.):
Her

LED

KN210 Console Dispiays and FRUs

Normal Ervor
Console Conscle Defaunlt

Display Display om Error

Description

FRU!

Script AD
(Continved from previous page.)

24D

Halt

MEM_.ddr

3,1,4,8

4acC

Halt

MEM_ECC _error

3.1,4,86

Halt

MEM_masked_errore

3,1,4,6

Halt

MEM_correction

3,1,4,8

748

Continue

MEM_Addr_chrie

3,1,4,8

247

Continue

MEM_refresh

3,1,4,8

9
C

40
41

740
741

Continue
Continue

MEM _eonnt_erve
Board reast

3.1,4,6
i, 6

End of seript.

Secript AB

Halt

CMCTL _setup_CSRe

1,3,4,8

749

Helt

MEM_FDM_logic

3.1,4,8

730

Halt

MEM _bitmep

1,3, 4,8

Invoke secript A7.
End of ecript.

Seript A7

Halt

MEM_data

3,1, 4,6

N4E

Halt

MEM_byte

3,1,4,8

'In the case of multiple FRUs, refer to Section 4.5.2 for further information. If & problem

recure with the same FRU, check thet the tolerance for system power supply +8 Vde, +12 Vdc,
and ec ripple are within specification.

FRU key:
1 = KN210 CPU module
2 = KN210 /O niodule
3 = MSE50 module
4 = Memory interconnect cable
b = @22-bus device
6 = @22/CD backplane
7 = System power supply
8 = H3602-AB CPU IO panel
9 = H3602-AB cable

10 = CPU and I/O module interconnect cable

4-24

KN210 CPU Module Set System Maintenance

Table 4-7 (Cont.):
Hez

LED

KN210 Console Dispiays and FRUs

Normal Error
Console Comsole Defauit

Displesy Display on Ervor

Description

FRU!

MEM _addr
MEM_ECC_ervor
MEM_masked_errore
MEM_correction
MEM_addreas_shorts
MEM _refresh
MEM_count_bad pages
CQBIC_memory

3,1,4,8
3,1,4,6
3,1,4,8
3,1,4,6
3,1,4,8
3,1, 4,6

Board reset

1,6

Script AT
(Continved from previous page.)

9
9
9
9
9
9
9
8

4D
4C
4B
4A
48
47
40
80

4D
74C
74B
4A
748
47
740
780

Helt
Helt
Helt
Halt
Heit
Halt
Continue
Continue

741

Halt

3,1,4,8
1,3,6,4,6

End of seript.

Script BE

772

A
A
8
A
A

70
78
60
73
74

770
778
760
773
174

Halt
Halt
Continue
Helt
Halt

776

Halt

177

Helt

Helt
Halt

R3000_tlb

R3000_fpu

R3000 cache
R3000_write_buf
M7638_present
R3000_reg_intrf
R3000_buf_intyf

1
1
10,2, 1
2.1
1,2

R3000_interrupt

1,2

R3000_mem_intef
R3000_mov_inver

3,1,4,8
1,2

'In the case of multiple FRUs, refer to Section 4.5.2 for further information. If a problem
recurs with the same FRU, check that the tolerance for system power supply +6 Vde, +12 Vde,
end ac ripple are within epecification.

FRU key:

1 = KN210 CPU module
2 = KN210 /O module
3 = MSE860 module
4 = Memory interconnect cable
B = Q22-bus device
6 = Q22/CD backplane
7 = System power supply
8 = H3802-AB CPU I/O pane!
9 = H3602-AB cable

10 = CPU and I/O module interconnect cable

Troubleshooting and Diagnostics

4-25

Table 4-7 (Cont.):
Hez

KN210 Console Displays and FRUs

Normal Ervor

Console Console Default

LED Display Dieplay on Error

Description

FRU?

Script BE
(Comtinued from previous page.)
End of ecript.

Script BF

760

Continue

Halt

M7636_present
Sli_registers

10,2, 1
2,1

8
8

B7
8C

67
75C

Halt
Halt

SII_memory
Sli_initiator

2,1
2,1

6
B

5E
BF

768
BF

Halt
Halt

NI_memory
NI_teat

2,1
2,1

%8B

Halt

SIi_target

2,1

End of script.

!In the case of multiple FRUs, refer to Section 4.5.2 for further information. If & problem
recurs with the same FRU, check that the tolerance for system power supply +6 Vde, +12 Vdc,
and ec ripple are within specification.
FRU key:

1 = KN210 CPU module
2 = KN210 /O module
3 = MS850 module
4 = Memory interconnect cable
6 = @22-bua device
6 = Q22/CD backplane
7 = System power supply
8 = H36802-AB CPU IO panel
8 = H3602-AB cable

10 = CPU and /O module interconnect cable

4-26

KN210 CPU Module Set Sysiem Maintenance

4.3.6 System Halt Messages
Table 4-8 lists messages that may sppear on the console terminal when a
system error oCCurs.

Table 4-8:

System Halt Messages

Code

Message

202

EXT HLT

Ezxplanation
External halt, caused cither by console BREAK condition or

bacause Q22-bus BHALT_L or DBR<AUX_HLT> bit was set
while enabled.

703

Power-up; no halt meessage displayed. The presence of the

704

ISP ERR

Caused by attempt to push interrupt or exception state onto
the interrupt atack when the interrupt stack wes mapped NO
ACCESS or NOT VALID.

706

DBL ERR

A second machine check occurred while the processor was

708

HLT INST

The processor executed a HALT instruction in kernel mode.

SCB ERR3

The vector had bits <1:0> = 3.

708

SCB ERR2

The vector had bits <1:0> = 2.

CHM FR ISTK

A change mode instruction was executed when PSL<IS> was

CHM TO ISTK

The SCB vector for 8 change mode had bit <0> set.

SCB RD ERR

A hard memory error occurred during a processor read of an

710

MCHK AV

An access violation or an invelid translation occurred during

711

KSP AV

An access violi%on or an invalid trenslation occurred during

712

DBL ERR2

Double machine check errc=.
A machine check occurred
during en attompt to eervice @ mechine check.

713

DBL ERR3

Double machine check error.
A machine check occurred
during an atteapt to service @ kernel steck not valid

719

PSL EXC5

PSL «28:24> = 5 on inter rupt or exception.

PSL EXC6

PSL <26:24> = 6 on interrupt or exception.

PSL EXC7

PSL <26:24> = 7 on interrupt or exception.

PSL REIb

PSL «26:24> = 6 on an rei ingtruction.

PSL REI6

PSL <26:24> = 6 on an rei instruction.

?1F

PSL REI7

PSL <26:24> = 7 on an rei instruction.

gr::ware banner and diagnostic countdown indicates this
alt.

attempting to service 8 normal exception.

set.

exception or interrupt vector.

machine check exception processing.

invalid kernel e?ack pointer exception proceseing.

exception.

Troubleshooting and Diagnostics

4-27

4.3.7 Console Error Messages
Table 4-9 lists messages issued in response to an error or to a console
command that was entered incorrectly.
Table 4-9:

Console Error Messages

Cede Messago

Explanation

CORRPTN

The console data base wae corrupted. The console simulates

721

ILL REF

The requested reference would violate virtual memory

722
723

ILLCMD
INV DGT

The command string cannot be parged.
A number has an invalid digit.

724

LTL

The command was too large for the conacle to buffer. The

726
726
27

iLL ADR
VAL TOO LRG
SW CONF

The specified address is not in the address space.
The specified value does not fit in the destination.
Switch conflict.
For example, an EXAMINE command

728
720

UNKSW
UNK SYM

The switch is not recognized.
The EXAMINE or DEPOSIT symbolic address is not

724

CHKSM

An X commend has an incorrect command or data checkrum.

72B
72C

HLTED
FNDERR

The operator entered a HALT command.
A FIND command failed either to find the RPB or 64 Kbytes

TMOUT

”E
72F

MEM ERR
UNXINT

a power-up sequence and rebuilds its data base.

protection, address is not mapped or is invalid in the specified
address space, or value is invalid in the specified destination.

messsge is sent only after the console receives the [Reaam] at
the end of the command.

specifies two different deta sizes.

recognized.

If the data checksum is incorrect, this meesage is issued and
ie not abbreviated to “Illegal command.”

of good memory.

Data failed to arrive in the ezpected time during an X

command.

Memrory error or machine check accurred.
An unexpected interrupt or exception occurred.

730

UNIMPLEMENTED

Unimplemented function.

731

QUAL NOVAL

Qualifier does not take & value.

732
733
734
735

QUAL AMBG
QUAL REQ VAL
QUAL OVERF
ARG OVERF

Ambiguous quslifier.
Qualifier requires a value,
Too many qualifiers.
Too many arguments.

AMBG CMD

Ambiguous command.

737

INSUF ARG

Too few arguments.

4-28

KN210 CPU Module Set System Maintenance

4.3.8 VMB Error Messages (CVAX)
If VMB is unable to boot MDM, it returns an error message to the console.
Table 4-10 lists the error messages and their descriptions.
Table 4-10:
Message

VMB Error Messages

Number

Mnemonic

Interpretation

740

NOSUCHDEV

No bootable devices found

741
742
43

DEVASSIGN
NOSUCHFILE
FILESTRUCT

Device i not present
Program image not found
Invalid boot device file structure

744

BADCHKSUM

Bad checksum on header file

745

BADFILEHDR

Bad file header

748

BADDIRECTORY

Bad directory file

FILNOTCNTC

Invalid program image format

748

ENDOFFILE

Premature end-of-file encountered

749

BADFILENAME

Bad file name given

MA
4B

Program image does not fit in available memory
Boot device I/0 error

4C
4D

BUFFEROVF
CTRLERR
DEVINACT
DEVOFFLINE

MEMERR

Memory initialization error

24F

SCRINT

Unexpected SCB exception or machine check

750

SCB2NDINT

Unexpected exception after starting program image

751

NOROM

No valid ROM image found

762
763

NOSUCHNODE
INSFMAPREG

No response from load aerver
Insufficient Q-bus mapping registers due to invalid
memory configuration, bad memory, or beceuse Q-bue

764

RETTY

Failed to initialize boot device
Device ig off line

map was not relocated to main memory

No devices bootable, retrying

Troubleshooting and Diagnostics

4-29

4.4 Acceptance Testing
Perform the acceptance tcsting procedure listed below, after installing a
system or whenever replacing the following:
KN210 CPU module
KN210 VO module
MS650-BA memory module
Memory data interconnect cable
Backplane
DSSI device
H3602-AB

Run five error-free passes of the power-up scripts by entering the

following command:
>>»>

Press
2.

to terminate the scripts.

Enter the following command to run script Al, which invokes CPU and
memory tests without resetting the bitmap to mark only solid multibit
ECC errors in main memory. This command gives you a quick memory
check, since most tests run on a 266-Kbyte boundary.
>>>

Perform the next two steps for a more thorough test of memory.
>>>

T A8

>»>

The first command runs script A8 for one pass. This command enables
mapping out of solid single-bit ECC as well as multibit ECC errors. It
will also run script A7 for one pass.

4-30

KNZ10 CPU Module Set System Maintenance

The second command runs script A7 repeatedly. This command runs

the memory tests only and does not reset the bitmap. Press[cw<] after

two passes to terminate the script. This test takes up to 5 minutes per
pass, depending on the amount of memory in the system. Most of the
memory diagnostics test memory on a page boundary.

The third command runs script BE repeatedly This command runs
a series of R3G00 tests. Press
after five passes to terminate the
script.

If any of the memory tests fails, it marks the bitmap and continues
with no error printout to the console. An exception is test 40 (count
bad pages). If any single-bit or multibit ECC errors are detected,
they are reported in test 40. Such a failure indicates that pages in
memory have been marked bad in the bitmap because of solid singlebit and/or multibit ECC errors The error printout does not display the
20 longwords, since it is a severity level 1 error.
Check the memory configuration again, since test 31 can check for only
a few invahid configurations. For example, test 31 cannot report that a
memory board is missing from the configuration, since it has no way of
knowing if the board should be there or not.

To check the memory configuration, enter the following command line:
>>>

SHOW

MEMORY/FULL

Memory O:
Total

00000000 to OOFFFFFF,
16MB,

O bad pages,

104

16MB,

0 bad pages

reserved pages

Memory Bitmap
-00FF3000

Console

OOFF3FFF,

pages

Scratch Area

~-00FF4000

to OOFFTFFF,

pages

€4

pages

Qbua Map
-O0FFB8000

Scan

Bad

OOFFFFFF,

Pages

>>>

Troubles!t .oting and Diagnostics

4-31

Memories 0 through 3 are the MS660 memory modules. The Q22-bus
map always spans the top 32 Kbytes of good memory. The memory
bitmap always spans two pages (1 Kbyte) per 4 Mbytes of memory
configured
Use utility 9C to compare the contents of configuration registers
MEMCSR 0-15 with the memory installed in the system:
>>»>

%¢

TOY

=96C972ES

ICCS

=00000000

TCRO

=00000000

TIRO

=00000000

TNIRG=00000000

TIVRO=00000078

TCR1

=80000084

TIR1l

=00000000

TNWNIR1=00000000

TIVR1=0000007C

RXCS

=00000000

RXDB

=00000011

TXCS

=00000000

TXDB =00000030

MSER =00000000

CADR

=0000000C

BDR

=FFFTFFE2

DLEDR=0000000B

SSCCR=00D46677

CBTCR=00000004

SCR

=0000D000

DSER

QBEAR=0000000F

DEARR =000000G0

OBMBR=00000000

=00000000

IPCRn=0000

MEM_FRU1 MEMCSR_0=80000017

1=80400017

2=80800017

3=80C00017

MEM FRU2

5=81400017

6=81800017

7=81C00017

MEMCSR

4=81000017

HEM FRU3 MEMCSR
MEM FRU4

8=82000017

9=82400017

10=82800017

11=82C00017

MEMCSR12=83000017

13=83400017

14=83800017

15=83C00017

MEMCSR16=8190000F

17=00002000

Ethernet

SII

SA =

08-00-2B-0F-8D-C2

NICSRO=0004

MSIDRO =0000

MSIDR1

=0000

MSIDR2 =0000

MSICSR =0000

MSIIDR =0007

MSITR

=0000

MSITLP =0000

MSIILP =0000

MSIDSCR=0000

MSIDSSR=R480

MSIDCR =0000

>>>

One memory bank is enabled for each 4 Mbytes of memory.
MEMCSRs map modules as follows:
MEMCSR 0-3

First MS650 memory module

MEMCSR 4-7

Second MSE50 memory module

MEMCSR 8-11

Third MS650 memory module

MEMCSR 12-15

Fourth MS650 memory module

4-32

KN210 CPU Module Set System Maintenance

The

Verify the following:

The bank enable bits are set in all four MEMCSRs. MEMCSRe
<6:0> should equal 17 hex for all four MEMCSRs. See the values
for MEMCSR 0-3 in the example.

[f a memory board is not present, bits <31:0> are all zeros for
the corresponding group of four MEMCSRs. See the values for
MEMCSR 8-11 in the example.

Bits <25:22> should always incremen: by one starting at zero
in MEMCSRO if bit <31> equals 1. I the example above, bits
<25:22> of MEMCSR 0 through 7 increment by one, resulting in an
increment in each word. If bit <31> equals 0, <25:22> should equal
Zero.

Check the @22-bus and the Q22-bus logic in the KN210 CQBIC chip,
and the configuration of the Q22-bus, as follows:
>>>

SHOW

QBUS

Scan of Qbus

I/0

Space

-20000120

(760440)

= 0080

-20000122

(760442)

= FO081

-20000124

(760444)

= DD18

-20000126

(760446)

-20000128

(760450)

= 0000

-2000012A

(760452)

0000

-2000012C

(760454)

8000

-2000012E

(760456)

= 0000

-20001920

(774440)

= FFO8

-20001922

(774442)

= FFO0O

~20001924

(774444)

-20001926

(774446)

= FFO€

=-20001928

(774450)

= FF16

-2000192A

(774452)

= FFF2

-2000192C

(774454)

= OOQF8

-2000192E

(774456)

=-20001940

(774500)

= 0000

-20001942

(774502)

= ORBRCO

-20001F40

(777500)

0020

(300)

DHQ11/DHV11/CXA16/CXBl16/CHY0B

(120)

DELQA/DEQNA

(260)

TQKS0/TQK70/TUBLlE/RV20/K-TAPE

(004)

IPCR

0200

FF2B

1030

Scan of Qbus Memory Space
>>>

Troubleshooting and Diagnostics

4-33

The columns are described below. The examples listed are from the last
line of the example above.

First column = the VAX /O address of the CSR, in hex (20001F40).
Second column = the @22-bus address of the CSR, in octal (777500).
Third column = the data, contained at the CSR address, in hex
(0020).

Fourth column = the device vector in octal, according to the fixed
or floating Q@22-bus and UNIBUS algorithm (004).
Fifth column = the device name (IPCR, the KN210 interprocessor
communications register).

Additional lines for the device are displayed if more than one CSR
exists.

The last line, Scan of @bus Memory Space, displays memory residing
on the Q22-bus, if present. VAX memory mapped by the Q22-bus map
is not displayed.
If the system containe an MSCP or TMSCP controller, run test 81. This
test performs the following functions:
Performs step one of the UQ port initialization sequence
Performs the SA wraparound test
Checks the Q@22-bus interrupt logic

If you do not specify the CSR address, the test searches for and runs
on the first MSCP device by default. To test the first TMSCP device,
you must specify the first parameter:
>>>

20001940

You can specify other addresses if you have multiple MSCP or TMSCP
devices in the first parameter. This action may be useful to isolate
a problem with a controller, the KN210, or the backplane. Use the
VAX address provided by ti.e SHOW QBUS ~ommand to determine the
CSR value. If you do not specify a value, the MSCP device at address
20001468 is tested by default.

4-34

KN210 CPU Module Set System Maintenance

Check that all UQSSP, MSCP, TMSCP, and Ethernet controllers and
devices are visible hy typing the following command line:
>>>

SHOW DEVICE

DSSI

Node

(R3WBOA)

-DIAO -rf(0,0,*)

-DIA,

-rf(1,1,*)

(RF71)

(*)

Node

DSSI

(R3QDVA)

DSSI Node

(RF71)

UQSSP Tape Controller 0
-MUAQ0

-tm{(0,0)

Ethernet

-ESA0

(774500)

(TK70)

Adapter

-se

-mop()

(08-00-2B~0C-C4-75)

in the example above, the console displays the DSSI node names
and numbers, then the CVAX device names and the R3000 devices
names, which are followed by the controller number and unit number
in parentheses.

DSSI Node 7 (*) is the DSS1 adapter located on the KN210 I/0 module.
In most cases, the KN210 I/O module is the local DSSI node shown
by the asterisk and has a node number of 7. DSSI node names, node
numbers, and unit numbers should be unique.

The UQSSP (TQK70) tape controller and its CSR address are also
shown. The line below this display shows a TK70 connected.

The next two lines show the logical name and station address for the
Ethernet adapter located on the KN210 /0 medule.
Test the DSSI subsystem using the KN210 ROM-based Diagnostics and
Utilities Protocol (DUP) facility. This facility allows you to connect to
the DUP server in the RF drive controller. Here are some examples:
>>>

SET HOST/DUP/DSSI

Starting DUP

server...

Stopping

server...

DUP

In this example, a DUP connection was made with DiSSI node 7, the
KN210 /O module The DUP server times out, since no local programs

exist and no response packet was received.

Troubleshooting and Diagnostics

4-35

>>>

SET

HOST/DUP/DSSI

Starting DUP

server...

DSSI

(R3VBNC)

Node

DRVEXR V1.0
DRVTST V1.0
HISTRY V1.0

D 21-FEB-1988 21:27:54
D 21-FEB-1988 21:27:54
D 21-FEB-1988 21:27:54

FRASE

V1.0
PARAMS V1.0

D 21-FEB-1988 21:27:54
D 21-FEB-i%88 21:27:54

DIRECT V1.0

End of
Tesk

21-FEB-1988

Name?

DRVTST

Write/read anywhere
5

21:27:54

directory

minutea

for

test

on medium?
to

(l=Yes/ (0=No)]:

Compare

failed on head

track

1091.

Compare

failed on head

track

529.

Task

Name?

DRVEXR

Write/read anyvhere on medium?
10

[l=Yeas/ (0=No)):

time

in minutes?

[(10)-100}:

minutes

for teat

completa.

Tast

<CR>

complete.

<CR>

R3VBHMC: :MSCPSDUP 21-FEB-1988 21:37:35 DRVEXR CPU=00:00:01.88 PI=43
R3IVBNC: :MSCPSDUP 21-FEB-1988 21:37:38 DRVEXR CPU=00:00:03.38 PI=79
Compare

failed

head

track

1021.

R3IVBNC: :MSCPSDUP 21-FEB-1988 21:37:40 DRVEXR CPU=00:00:04.97 PI=116
Y
>>>

In the example above, the local programs DRVTST and DRVEXR are
run on drive 1. Do not enter 1 in response to the question Write/read
anywhere on medium?. Doing so will destroy the data on the disk. Press
[Reaam], which uses the default, allowing reads and writes to the DBNs

only.
or
displays a message as shown in the DRVEXR example
above (the lines beginning with R3VBNC::) In the example, [c1] has

been pressed twice to show the difference in the time and :n the value
of the progress indicator (PI).

Press [cvc] to terminate the program

Use the local programs HISTRY (Section 483) and PARAMS
(Section 4.85) to determine the cause of errors displayed during
DRVTST or DRVEXR. DRVTST should run succssefully for one pass on
each drive. Custrmer Services can refer to the RF71 Disk Drive Service
Manual for details about the DUP local programs and corrective action.
7.

If there are one or more DELQA modules in the system, use test 82 to

invoke the Ethernet option's self-test and receive status from the host

firmware. Test 82 is useful for acceptance testing if you cannot access
the system enclosure to see the DELQA LEDs.

4-36

KN210 CPU Module Set System Maintenance

Afer the steps above have completed successfully, load MDM and run
the system tests from the Main Menu. If they run successfully, the
system has gone through its basic checkout and you can load the
software.

4.5 Troubleshooting
This section contains suggestions for determining the cause of ROM-based
diagnostic test failures.

4.5.1 FE Utility
If any of the IPT tests fail, the major test code is displayed on the LEDs.
After the IPT tests are completed, any test that fails is displayed on both
the LEDs and through a console display. Run the FE utility if the message,
Normal operation not possible, is displayed afier the tests have completed
and there is no other error indication, or if you need more information than
what is provided in the error display.

The FE utility dumps diagnostic state to the console (Example 4-6). This
state indicates the major and minor test codes of the test that failed, the
10 parameters associated with the test, and the hardware error summary
register.

Example 4-6:
>>>

FE Utility Example

T FE

bitmap=00BF3400,

length=0C00,

checksum=007E

buemap=00BF8000

return_stack=201406A8
subtest pc=2004F4C4

timeout=00000001,

error=0B,

de_error_vector=18,

de_error=FE

severity code=02,

previous_error=FEOB5D5D,

00000000,

total_error_count=0001

00000000,

00000000

last_exception_pc=20050807
flages=01FFFD7F,

test_flags=20

highest_severity=00

led_display=05
conscle_display=5D

save_mchk_code=80,

save_err_f1lags=000000

param_ 1=00000100 2=00000100 3=000000F7 4=00000000
param_6=00000004

7=20050527

5=00000001

8=00000000 9=20140698 10=200521F4

Troubleshooting and Diagnostics

4-37

The most useful fields displayed above are as follows:
¢

De_error_vector, which is the SCB vector through which the unexpected
interrupt or exception trapped if de_error equals FE or EF.

Total_error_count. Four hex digits showing the number of previous
errors that have occurred.

Previous_error. Contains the history of the last four errors. Each
longword contains four bytes of information. From left to right these
are the de_error, subtest_log, and test number (copied in both bytes).

Save machine check code (save_mchk_code). Valid only if the test halts
on error. This field has the same format as the hardware error summary
register.

Save error flags (save_err_flags). Valid only if the test halts on error.
This field has the same format as the hardware error summary register.
e

Parameters 1 through 10. Valid only if the test halts on error. The
parameters have the same format as the hardware error summary
register.

FE in the previous_error field indicates that an unexpected exception has
occurred. If any of the tests that announce to the console fails, and the
error code is FE, examine the last longword of the error printout. The last
longword is the hardware error summary register and contains the machine
check code (<31:24>) and KN210 ervor status bits (<23:0>). Table 4-11 lists
the status bits.

4-38

KN210 CPU Module Set System Maintenance

Table 4-11: Hardware Error Summary Register

Bit

31
30
29

Machine check code
Machine check code
Machine check code
Machine check code

28
26

Machine check code
Bachine check code

Machine check code

24
23

Machine check code

MBSER <b6>

21
20
19

MSER <4>
MSER <1>
MBSER <0>

MSER <8»

Description

; CDAL date parity error

; Mchn chek CDAL parity error
; Machine check cache parity
: Cache deta parity error
; Cache tag parity error

Unueed

17
i8
16
i4
13

MEMCSRI16 <31>
MEMCSR16 <30>
MEMCSR16 <25>
MEMCSR18 «<25>
MEMCSR16 <2¢>

; Uncorrectable ECC error
; Two or more uncorrectable errors
; Correctable gingle-bit error
: Page address bits 25:22 of
: Location that caused error.

MEMCSR168 <22>

; failing 4-Mbyte bank of memory.

MEMCSRI6 <23>

: Theee four bits point to the

10
9

MEMCSRI16 <8>
MEMCSR18 <7>

; DMA reed/write error.
: CDAL parity error on write.

CBCTR <31>

, CDAL bus timeout.

7
@
4

CBCTR <30>
DSER «7>
DSER <6>

; CPU read/write bus timeout.
: Q22-bus NXM.
; @22-bus parity error.

3
2

DSER <4>
DSER «3>

: Pead mein memory error.
; Losat error.

1
0

DSER «2>
[PCRn <16>

; No grant timeout.
; DMA Q22-bus memory error.

Troubleshooting and Diagnostics

4-39

4.5.2 isolating Memory Failures
This section describes procelures for isolating memory subsystem failures,
particularly when the system contains more than one MS6560 memory
module.
1.

SHOW MEMORY/FULL
Use the SHOW MEMORY/FULL command to examine failures detected
by the memory tests. Use this command if test 40 fails, which indicates
that pages have been marked bad in the bitmap.

You can also use SHOW MEMORY/FULL after terminating a script that
is taking an unusually long time to run. Press [c#<] to terminate the
script afler the completion of the current test. (cv<] on the KN210
coneole takes effect only after the entire script completes.) After
terminating the script, enter SHOW MEMORY/FULL to see if the tests
have marked any pages bad up to that point. See Section 4.4 for an
example of this command.
T A9
>>>

[memory

test]

starting board_number

ending board number

Script A9 runs only the memory tests and halts on the first error
detected. Unlike the power-up script, it does not continue. Since the

script does not rerun the test, it detects memory-related failures that
are not hard errors. You should then run the individual test that failed
on each memory module one MS6560 module at a time. You can input
pevameters 1 and 2 of tests 40, 47, 48, and 4A through 4F as the
starting and ending address for testing. It is easier, however, to input
the memory module numbers 1-4. For example, if test 4F fails, test
the second memory module ae follows:
>>>
T 4F 2 2

If a failure is detected for a second of three MS650 modules, for example,
repeat this procedure for all memory modules to isolate the MS6560
module that is the FRU, using the process of elimination.

You can also specify the address increment. For example, to test the
third memory module on each page boundary, type:
>>>

200

By default, most memory tests test one longword on a 256-Kbyte
boundary. If an error is detected, the tests start testing on a page
boundary. Test 48 (address shorts test) is an exception: it checks every
location in memory since it can do so in a reasonable amount of time.
Other tests, such as 4F (floating ones and zeros test), can take up to

4-40

KN210 CPU Module Set System Maintenance

one hour, depending on the amount of memory, if each location were
to be tested. If you do specify an address increment, do not input less
than 200 (testing on a page boundary), since almost all hard memory
failures span at least one page. For normal servicing, do not specify the
address increment, since it adds unnecessary repair time; most memory
subsystem failures can be found using the default parameter.

All the memory tests, with the exception of 40, save MEMCSR17 and

MEMCSR16 memory status and error registers in parameters 7 and 8,
respectively.
T 9C

The utility 9C is useful if test 31 or some other memory test failed
because memory was not configured corre~tly.
To help in isolating an FRU, examine registers MEMCSR 0--16 by
entering T 9C at the console /O mode prompt (Example 4-7). Utility
9C is also useful for examining the error registers MSER, DSER, and
MEMCSRI16, upon a fatal system crash or similar event.
T 40

Although the SHOW MEMORY command displays pages that are
marked bad by the memory test and is easier to interpret than test
40, there is one instance in which test 40 reports information that
SHOW MEMORY does not report. You can use test 40 as an alternative
to running script A9 to detect soft memory errors. Specify the third
parameter in test 40 (see Table 4—1) to be the threshold for soft errors.
To allow 0 (zero) errors, enter the following:
»»>»TA4C 140

This command tests the memory on the four memory modules. Use it
after running memory tests individually or within a script. If test 40
fails with subtestlog = 6, examine longwords P5~P8 to determine how
many errors have been detected on memory modules one through four,
as follows:

Troubleshooting and Diagnostics

4-41

Longword

Memory Module Number

Example 4-7:
74F

(solating Bad Memory Using T 9C

SCBINT

>>>t

TOY

=96C972ES5

ICCS

=00000000

TCRO

=00000000

TIRO

=00000000

TCR1

=80000084

TIR1

=00000000

TNIR0=00000000
TNIR1=00000000

TIVRO=00000078
TIVR1=0000007C

RXCS

=00000000

RXDB

=00000011

TXCS

=00000000

TXDB =00000030

MSER =00000000

CADR =0000000C

BDR

=FFFFFFE2

DLEDR=0000000B

SSCCR=00D46677

CBTCR=00000004

SCR

=0000D000

DSER

=00000000

QBEAR=0000000F

DEAR =00000000

OBMBR=00000000

IPCRn=0000

MEMCSR_0=80000017

1=80400017

2=80800017

3=80C00017

MEM_FRU2 MEMCSR_4=81000017
MEM_FRU3 MEMCSR_8=82000017

5=81400017
9=82400017

6=81800017
10=82800017

11=82C00017

13=83400017

14=83800017

15=83C00017

MEM_FRU1

MEM_FRU4 MEMCSR12=83000017
MEMCSR16=8190000F
Ethernet

SII

7=81C00017

17=00002000

SA = 08-00-2B-0F-8D-C2

NICSRO=0004

MSIDRO =0000

MSIDR1 =0000

MSIDR2 =0000

MSICSR =0000

MSIIDR =0007

MSITR

=0000

MSITLP =0000

MSIILP =0000

MSIDSCR=0000

MSIDSSR=A480

MSIDCR =0000

>>>

In this case, the diagnostics have passed but MDM does not boot. One
of the console/VMB error messages is displayed. Run utility 2C and
examine the error registers. Bit 31 in MEMCSR 16 is set, indicating an
uncorrectable ECC error in memory. If any of bits <31:29> is set, there
was a memory error. Compare the bite MEMCSR16 <25:22> against
MEMCSR 0-16 <25:22>. If they match and the MEMCSRn <31> is set,
then the board that was experiencing the failure (the memory FRU) is
the MEM_FRU number on the left.

In Example 4-7, the FRU is the second memory FRU, which is
the second MS650-BA module because both conditions are met by

4-42

KN210 CPU Module Set Syste~ Maintenance

MEMCSR_6 in the MEM_FRU 2 row.
shown in Example 4-8:

The following conditions are

MEMCSR_6 matches MEMCSR16,

The Bank Enable bit <31> in MEMCSR_6 is set, which indicates

Number) match.

since bits <25:22> (Bank

that the bank number is valid.

Exampie 4-8:

9C—Conditions for Determining a Memory FRU
3

MEMCSR16 = 8194000F Hex

1000 0001

MEMCSR_6 = 81800017 Hex

1000 0001

1001

0100 0000 0000 0000

1111

1000 0000 0000 0000 0001

0111

bit

[}

set

25:22 match

4.5.3 Additional Troubleshooting Suggestions
Note the following additional suggestions when diagnosing a possible

memory failure.

If more than one memory module is failing, you should suspect the KN210
CPU module, KN210 /O module, CPU/memory cable, backplane, or MS650
modules as the cause of failure.

Always check the seating of the memory cable first before replacing a
KN210 or MS650 module. if the seating appears to be improper, rerun
the tests. Also remember to leave the middle connector disconnected for a
three-connector cable when the system is configured with only one MS650.
If you are rotating MS650 modules to verify that a particular memory

module is causing the failure, be aware that a module may fail in a different
way when in a different slot.

Be sure to put the modules back in their original positions when you are

finished.

If memory errors are found in the error log, use the KN210 ROM-based
diagnostics to see if it is an MS650 problem or if it is related to the
KN210, CPU/memory interconnect cable, or backplane. Follow steps 1-3 of
Section 4.4 and Section 4.5.2 to aid in isolating the failure.

Use the SHOW QBUS, SHOW DEVICE, and SET HOST/DUP commands

when troubleshooting 1/0 subsystem problems.

Troubleshooting and Diagnostics

4-43

Use the CONFIG command te help with configuration problems or when
installing new options onto the Q-bus. See the command descriptions in
Chapter 3.

You can run a DSSI device power-up diagnostic without performing a cold
restart or spinning the disk drives down and back up.
Type the following at the console program:
>>> T 58 <node_number>

A CI Reset command is issued to the DSSI device, causing the device to
perform its power-up diagnostics.

Parameter 1 is the DSSI node or port number. It must be in the range of
0-7 (0 is the default). Use the default for parameter 2.
You can perform this test repeatedly with the REPEAT coinmand (R T 68
<node_number>). In that case the drive's self-tests run repeatedly until
you press

to terminate the test.

Once the test has completed successfully, you can examine the DSSI
device's internal error logs by running the DUP local programs HISTRY and
PARAMS. Refer to Section 4.8.3 and Section 4.8.5 for further information.

4.6 Loopback Tests
You can use external loopback tests to localize problems with the Ethernet,
console, and DSSI subsystems.

4.6.1 DSSI Problems
For DSSI problems, run the SII external loopback test (test 66). To check
the DSSI bus out to the KN210 I/0 module connector, plug one end of the
cable (17-02216-01) to the H3281 loopback connector and the other end to
the DSSI connector on the KN210 /0O module. To test out to the end of
the DSSI bus, power down the system, remove all DSSI devices with the
exception of the KN210 from the bus, and plug the external DSSI loopback
connector 12-30702-01 in place of the DSSI bus terminator.

4.6.2 Ethernet Problems
For Ethernet problems, run the external loopback test (NI test, number 5F)
by entering the following:
>>>

4-44

1<CR>

KN210 CPU Module Set System Maintenance

Set parameter 1 to run this test. Only the external loopback test runs. Be
sure to set the ThinWire/standard Ethernet switch on the H3602-AB to the
appropriate position.

Use two 50-ohm H8225 terminators connected to an H8223 T-connector.
Before running the test, attach this assembly to the H3602-AB ThinWire
port.

To test the standard Ethernet connector, attach loopback connector 122219602 to the H3602-AB standerd Ethernet port.

4.6.3 Testing the Console Port
To test the console port at power-up. set the operation switch on the H3602AB, using the procedure in Section 3.4.3. The H3103 connects the console
port transmit and receive lines. At power-up, the SLU_EXT_LOOPBACK
IPT then runs a continuous loopback test

To test the end of the console terminal cable:
1.

Plug the MMJ end of the console terminal cable into the H3602-AB.

Disconnect the other end of the cable from the terminal.

Plug an H8572 adapter into the disconnected end of the cable.

Connect the H3103 to the H8572.

While the test is running, the LED display on the CPU 1/O insert should
alternate between 7 and 4 A value of 7 latched in the display indicates a
test failure. If the test fails, one of the following parts is faulty: the KN210,
the H3602-AB, the cabling, or the CPU module.

4.7 Module Self-Tests
Module self-tests run when you power up the system. A module self-test
can detect hard or repeatable errors, but usually not intermittent errovs.

Module LEDs dispiay pass/fail test results.
A pass by a module self-test dues not guarantee that the module is good,
because the test usually checks only the controller logic. The test usually
does not check the module @22-bus interface, the line drivers and receivers,
or the connector pins—all of which have relatively high failure rates.
A fail by a module self-test is accurate, because the test does not require
any other part of the system to be working.

Troubleshooting and Diagnostics

4-45

The fc'lowing modules do not have LED self-test indicators:
KLESI
LPV11
TSVO05

The following modules have one green LED, which indicates that the
module is receiving +5b and +12 Vdc:
CXAl16
CXB16
CXY08

Table 4-12 lists loopback connectors for common KN210 system modules.
Refer to Microsystems Options for a d~scription of specific module selftests.

Table 4~12:

Loopback Connectors for Q22-bus Devices

Device

Module Loopback

CXA16/CXB16

H3103 + Ha572!

CXYo08

H3046 (50-pin)

DELQA

12-22196-(2

KN210/H3802-AB

H3103

Cable Loopback
H3197 (26-pin)

H3103 + H8572

'For DSSI to KN210 or RF-series connector, use 17-02216-01 plus H3281 loopback. For
connection to end of bur use the DSS] loopback connector 12-30702-01.

4.8 RF-Series ISE Troubieshooting and Diagnostics
An RF-series integrated storage element (ISE) may fail either during initial
power-up or during normal operation. In both cases, the failure is indicated
by the lighting of the red fault LED on the OCP on the enclosure front panel.
The ISE also has a red fault LED, but it is not visible from the outside of
the system enclosure.

If the drive ie unable to execute the Power-On Self-Test (POST) successfully,
the red fault LED remains lit and the ready LED does not come on, or both
LEDs remain on.

POST is also used to handle two types of error conditions in the drive:

Controller errors are caused by the hardware associated with the
controller function of the drive module. A controller error is fatal to the
operation of the drive, since the controller cannot establish a logical

connection to the host. If the red fault LED remains lit, replace the
drive module.

4-46

KN210 CPU Module Set System Maintenance

Drive errors are caused by the hardware associated with the drive
control function of the drive module. These errors are not fatal to
the drive, since the drive can establish a logical connection and report
the error to the host. Both LEDs go out for about 1 second, then the
red fault LED lights. In this case, run either DRVTST, DRVEXR, or
PARAMS (described in the next sections) to determine the error code.

Three configuration errors also commonly occur:

More than one node with the same node number

Jdentical node names

Identical unit numbers

The first error cannot be detected by sofiware. Use the SHOW DSSI
command to display the second and third errors. This command lists each
device connected to the DSSI bus by node name and unit number.

If the ISE is connected to the OCP, you must install 2 aait ID plug in the
corresponding socket on the OCP. If the ISE is not connected to the OCP,
the ISE reads its unit ID from the three-switch DIP switchpack on the side
of the drive.

The RF-series ISE contains the following local programs (described in the

following sections):
DIRECT

A directory, in DUP gpecified format, of available local programs

DRVTST
DRVEXR
HISTRY
ERASE
PARAMS

A comprehengive drive functionality verification test
A utility that exercisee the ISE

A utility thet saves information retsined by the drive
A utility that ereses all user deta from the disk
A utility that allows you to loock at or change drive status, history, and
parametere

A description of each local program follows, including a table showing the
dialog of each program. The table aleo indicates the type of messages
cortained in the dialog, although the screen display will not indicate the
message type. Message types are abbreviated as follows:
Q—Question
I—Information
T—Termination
FE—Fatal errvor

To access these local programs, use the console SET HOST/DUP command,
which creates a virtual terminal connection to the storage device and the
designated local program, using the Diagnostic and Utilities Protocol (DUP)
standard dialog.

Troubleshooting and Diagnostics

4-47

Once the connection is established, the local program is in control. When
the program terminates, control is returned to the KN210 console. Tob
abort or prematurely terminate a program and return conirol {o the KN210

or [cwv].

console, press

4.8.1 DRVTST
DRVTST 18 a comprehensive functionality test. Evrors detected by this test

are isolated to the FRU level The messages are listed in Table 4-13.

Table 4-13:
Message

DRVTST Messages

Meecsage

Write/read anywhere on the mediaum? (1-yea/!t0=no)]

User deta will be corrupted. Proceed? |1=yea/(0=no)]

Five minutea to complete.

Test pacsed.

Or.

Unit 18 currently in use !

Operetion aborted by user.

zxxz—Unit read/write test failed ?

zxzs—Unit diagnostics failed2

1Either the drive 1s moperatlve,-i; use by 8 hogt, or 18 currently running snother local program.
2Refe~ to the diagnoatic error code list at the end of this chapter.

Answering No to the first question (“Write/read..?") or pressing [Ream]
results in a read-only test DRVTST, however, writes to a diagnostic area
on the disk

Answering Yes to the first question or pressing [Reun| causes
the second guestion to be displayed

Answering No to the second question (“Proceed?”) or pressing [Rewm] is the
same as answering No to the first question. Answering Yes to the second
question permits write and read operations anywhere on the medium.
DRVTST resets the ECC error counters, then calls the timed I/0 routine.
After the timed I/O routine ends (5 minutes), DRVTST saves the counters
again. It computes the uncorrectable error rate and byte (symbol) error
rate. If either rate is too high, the test fails and the appropriate error code
is displayed

4-48

KN210 CPU Module Set System Maintenance

4.8.2 DRVEXR
The DRVEXR local program exercises the ISE. The test is data transfer
intensive and indicates the overall integrity of the device. Table 4~14 lists
the DRVEXR messages.

Table 4-14:
Meesage

DRVEXR Messages

Type

Message

Write/read anywhere on the medium? {1=yea/t 0=no)]

User date will be corrupted. Proceed? [1=-yea/t0=no)]

Test time in minutes? [(10)-100]

ddd minutes to complete

dddddddd blocks (5612 bytes) transferred.

dddddddd bytes in ervor (soft).

dddddddd uncorrectable EC'C errore (recoverable).

Complete.

Or:

FE
FE
FE
FE

Unit is currently in use.!
Operation aborted by user.
zexz—Unit diagnostics failed.?
saxz—Unit read/write test failed ?

!Either the drive is inoperative. in use by a host, or 18 carrently running another local program.
2Refer to the diagnostic error list st the end of this chapter.

Answering No to the first question (“Write/read...”") results in a read-only
test DRVEXR, however, writes to a diagnostic area on the disk. Answering
Yes to the first question causes the second question to be displayed.
Answering No to the second question (“Proceed?”) is the same as answering
No to the first question. Answering Yes to the second question permits write
and read operations anywhere on the medium.

NOTE: If the write-protect switch o1 the OCP is pressed in (LED on) and
you answer Yes to the second question, the drive does not allow the test to
run. DRVEXR displays the error message 2006—Unit read / write test failed.
In this case, the test has not failed but has been prevented from running.

Troubleshooting and Diagnostics

4-49

DRVEXR saves the error counters, then calls the timed I/O routine. After
the timed /O routine ends, DRVEXR saves the counters again. It then
reports the total number of blocks transferred, bits in ervor, bytes in error,
and uncorrectable errors.

DRVEXR uses the same timed I/O routine as DRVTST, with two exceptions:
e

DRVTST always uses a fixed time of five minutes, whereas you specify
the time of the DRVEXR routine

DRVTST determines whether the drive is good or bad. DRVEXR reports
the data but does not determine the condition of the drive.

4.8.3 HISTRY
The HISTRY local program displays information about the history of the
ISE Table 4-15 lists the HISTRY messages.

Table 4-15:
Meapage

Pield Length

Pield Meaning

47 ASCIHI characters

Copynight notice

4 ASCII characteve

Product name

12 ASCI! charactere

Drive gerial number

6 ASCII characters

Node name

1 ASCIl charecter

Allocation clsas

8 ASCH charactere

Firmware revigion level

17 ASCI] chavectere

Hardware revigion level

6 ASCll chavacters

Power-on houre

5 ASCII cheracters

Power cyclea

4 ASCII charecteve

Type

HISTRY Messages

Hezadecimal fault code
Complete

IDisplays the last 11 fault codes es informational messages Refer to the diagnostic error code
list st the end of thus chapler

4-50

KN210 CPU Module Set System Maintenance

The following example shows a typical screen display when you run
HISTRY

ENO1082
SUSAN
0O

RFX

v101

RF71

PCB-5/ECO-00

617
21

AO4F
AO4F
2103

AO4F
R404
AO4F
A404
AO4F

A404

AO4F
A404
Complete.

If no errors have been logged, no hexadecimal fault codes are displayed.

4.8.4 ERASE

The ERASE local program overwrites application data on the drive while
leaving the replacement control table (RCT) intact. This local program is
used if an HDA must be replaced and the customer wants to protect any

confidential or sensitive data.

Use ERASE only if the HDA must be replaced and only after you have
backed up the customer's data.

Troubleshooting and Diagnostics

4-51

Table 4-16 lists the ERASE messages.

Table 4-16:
Message

ERASE Messages

Type

Message

Write/read anywhere on the medium? [1=yes/(0=no}]

Q
I

User deta will be corrupted. Proceed? (1=yee/(0=no)]
6 minutes to complete.

Complete.

Or:

Unit is currently in use.

Operation aborted by user.

FE
FE

zxxx—Unit diagnostics failed.!
xxxx—Operation failed.?

1Refer to the diagnostic error code list at the end of this chapter.

23xxx = one of the following ervor codes:

000D : Cannot write the RCT.
O00E : Cannot read the RCT.
000F : Cannot find an RBIN to revector to.

0010 : The RAM copy of the bed block table is full.

If a failure is detected, the message indicating the failure will be followed

by one or more messages containing error codes.

4.8.5 PARAMS
The PARAMS local program supports modifications to device parameters
that you may need to change, such as device node name and allocation
class. You invoke it in the same way as the other local programs. However,
you use the following commands to make the modifications you need:

SET

Terminates PARAMS program
Prints a brief list of commuands and their syntax
Sets a parameter to a value

SHOW

Dieplays a parameter or a clesa of parameters

EXIT
HELP

STATUS
WRITE

4-52

Displays module configuration, history, or current counters, depending on the

status type chosen

Alters the device parametera

KN210 CPU Module Set System Maintenance

4.8.5.1 EXIT

In maintenance mode, use the EXIT command to terminate the PARAMS
local program.

4.8.5.2 HELP

In maintenance mode, use the HELP command tc display a brief list of
available PARAMS commands, as shown in the example below.
PARAMS>

HELP

EXIT
HELP

SET

(parameter

SHOW

(parameter

/&aLL
/SERVO

/CONST
/SCS

value

,class)

/DRIVE
/MSCP

/DUP
STATUS

[type]

CONFIG

LOGS

DATALINK

PATHS

WRITE

PARAMS>

4.8.5.3 SET

in maintenance mode, use the SET command to change the value of a given
parameter. Parameter is the name or abbrevietion of the parameter to be
changed. Value is the value assigned to the parameter.
For example, SET NODE SUSAN sets the NODENAME parameter to

SUSAN.

The following parameters are useful to Customer Services:
ALLCLASS
FIVEDIME

UNITNUM
FORCEUNI
NODENAME

FORCENAM

The controller sllocetion claes. The allocation class should be szt to metch
that of the host.

True (1) if MSCP ehould support five connections with ten credits each. Fulse

(0) if MSCP ghould support seven connections with seven credits each.

The MSCP unit number.
True (1)
if the unit number should be taken from the DSSI ID. False (0) if the

UNITNUM value should be used insteed.

The controller's SCS nede name.

True (1) if the SCS node name should be forced to the string RF71x (where 2

io & letter from A to H corresponding to the DSSI bue ID) instead of using the
NODENAME value. False (0)if NODENAME is to be used.

Troubleshooting and Diagnostics

4-53

4.8.54 SHOW

Use the SHOW command to display the settings of a parameter or a class of
parameters. The SHOW command displays the full name of the parameter
(8 characters or less), the current value, the default value, radix and type,
and any flags associated with each parameter.
4.8.5.5 STATUS

Use the STATUS command to display module configuration, history, or
current counters, depending on the type specified. Type is the optional
ASCII string that denotes the type of display desired. If you omit Type, all
available status information is displayed. If present, it may be abbreviated.
The following types are available:
CONFIG

Displays the module name, node neme, power-on hours, power cycles, and
other such configuration information. Unit failures ere also displayed, if
applicable.

LOGS

Displays the last 11 machine and bug checks on the module. The display

includes the processor registers (D0-D7, A0-A7), the time end date of each
fatlure (if available; otherwise the date 17 November 1858 is displayed), and
some of the hardware registers.

DATALINK

Displays the data lirk counters.

PATHS

Displeya available path information (open virtusl eircuits} from the point of
view of the controller. The display includes the remote node names, DSSI IDs,
software type and version, and counters for the messages and datagrems sent
and/or received.

4.8.5.6 WRITE

Use the WRITE command to write the changes made while in PARAMS
to the drive nonvolatile memory. The WRITE command is similar to the
VMS SYSGEN WRITE command. Parameters are not available, but you
must be aware of the system and/or drive requirements and use the WRITE
command accordingly or it may not succeed in writing the changes.
The WRITE command may fail for one of the following reasons:
®

You altered a parameter that required the unit, and the unit cannot be
acquired (that is, the unit i1s not available to the host). Changing the
unit number is an example of a parameter that requires the unit.

You altered a parameter that required a controller initialization, and
you replied negatively to the request for reboot. Changing the node
name or the allocation class are examples of parameters that require
controller initialization.

Initial drive calibrations were in progress on the unit. The use of the
WRITE command is inhibited while these calibrations are running.

4-54

KN210 CPU Module Set System Maintenance

4.8.6 Diagnostic Error Codes
Diagnostic error codes appear when you are running DRVTST, DRVEXR,
or PARAMS. Most of the error codes indicate a failure of the drive module.
The exce stiona are listed below. The error codes are listed in Table 4-17. If
you see any error code other than those listed below, replace the module.

Table 4-17:

RF-Serles ISE Diagnostic Error Codes

Code

Message

2032A032

Failed tosee FLT go away

Meaning
FLT bit of the epindle control status register was

ssserted for one of the following reasons:
1. Reference clock not present
2. Stuck rotor

3. Bad connection between HDA and module

203A/A03A
13148314

Cannot spin up, ACLOW
ia set in WrtFit
Fromt panel is broken

Did not see ACOK signal, which is supplied by the
host system power supply for staggered spin-up.
Could be either the module or the operator control
panel or both.

Troubleshooting and Diagnostics

4-55

Appendix A

ULTRIX-32 Exerciser and Uerf
Command Summary
This appendix contains a summary of ULTRIX-32 exerciser and uerf
cornmands to help you troubleshoot and diagnose errors in the DECsystem
5400.

See the following documents for detailed information on the commands:
e

ULTRIX-32 Guide to System Exercisers

ULTRIX-32 Guide to the Error Logger System

A.1 Online ULTRIX Exerciser
The ULTRIX exercisers perform functional system and device testing. The

exercisers are run in single- or multiuser mode from an account with root
privileges.

The exercisers log status information in LOG files. Normal device errors
are handled by the error log and uerf. You can run each of the exercisers
in the background by ending each command line with an ampersand (&).
This allows many (the same or different) exercisers to be run concurrently,
which enhances your ability to perform system testing.

To run the exercisers, your current directory must be the field account. To
terminate the exercisers, enter
if the job is in the foreground, or kill
-18 pidifin the background. When you run an exerciser in the background,
the pid is displayed when the command is invoked.
A time stamp entry is made in the system error log each time you stop or
start an exerciser. Use the uerf option -r 350 to include these in an error
report. All the system exercisers, except netx, have the -0 option. The -0
option allows you to specify a file where diagnostic output is saved when
the exerciser terminates.

Exercising More Than One Part of the System

You can run more than one exerciser at the same time. Keep in mind,

however, that the more processes you have running, the slower the system

ULTRIX-32 Exerciser and Uerf Command Summary

A-1

performs. Before exercising the system extensively, make sure there are no
other users on the system.

To exercise more than one part of the system simultaneously, use the
eyscript maintenance command. The syscript command asks you which
exercisers you want to run, how long you want to run each exerciser, and
how many exercisers you want to run at one time. The syscript command
allows you to exercise a device, a subsystem, or the entire system.
You can start each exerciser by using either of the following methods:
e

Manually, by specifying the time parameter (-t option) and by placing
each command in the background before executing the next command

By typing the syscript command as follows:
¢ syscript

Once the syescript command is running, answer the questions displayed
on the console.
The syecript command then executes the individual
exercisers and creates a file called testsuite, which contains all the answers
you entered. You can reexecute the commands in the testsuite file by
entering the following, which causes testsuite to execute using the original
commands and parameters that you specified:
§ sh testsuite

A.1.1 Communications Exerciser (Asynchronous Serial
Lines)
The communications exerciser writes, reads, and validates random data
and packet lengths on communication lines as specified.

Syntax
cmx({-b}i-ofile}[-tmin]-Uine#

Options
b

Printa a help measage.

-ofile

Writes run-time statistics to file. Default file is 4LOG_CMX_u#.

&mun

Runs the ererciser for ¥ minutes. Default is run continuously.

Mined

Specifies the line number to exercize.

A-2

etercised ia /dev [ttyD3, line#t=03.

For ezample, if the line to be

KN210 CPU Module Set System Maintenance

Usage

Any line to be exercised MUST have a loopback connector on the
communication option's bulkhead panel or the end of the cable. Any line to
be exercised MUST be disabled in the /etc/ttys file by setting the status to
off.

EXAMPLE:

Exercise line tty01 and tty03 for 10 minutes in the background:
emx -t10 -101 03

A.1.2 Disk Exerciser
CAUTION: This exerciser can DESTRUCTIVELY WRITE on a disk. Do not
use this exerciser on any portion of a disk that contains customer data.
The -p and -¢ options destroy data on a disk. The -rdev command does not
overwrite data.

Syntan
dskx{options]-rdev
dek=z{options]-pdevpart
dekx{options}-cdev
Arguments
-rdev

Random read-only tes? on sll but the ¢ partition

-pdevpart

Writes, reads, and validatea on device dev on pertition part.

edet

Writeo, reads, and validates on device dev on sll but the ¢ partition.

Options
b

Prints e help measage

-ofile

Writes run-time statistics to file Defeult file is 8L.0G DSEX 84

«tm

Runs the ezercieer for m min' *26. Defeult is run continuously.

EXAMPLE:

Test (read only) the first RA disk in the system (ra0) for 20 minutes in
the background Diagnostics display every 5 minutes:
dskx -rra0 -t20 -db &

ULTRIX-32 Exerciser and Uer Command Summary

A-3

A.1.3 File System Exerciser
The file system exerciser initiates multiple processes and creates, writes,
closes, opens, and reads a test file of random data.
Syntax

fexl-bl{-ofile}{-tmin]}-fpath{-pn)
Options
b

Printa a help meesage

ofile

Writee run-time statistics to file. Defsult file is LOG FSX #0.

«Lonen

Runs the ezeraser for x minutes. Defazult is run continuously.

fpath

Path name of the file system directory to test. Default is /uss/ilald.

“pn

Number of fzx processss to spawn. Magimum is 250. Defoult is 20.

Usage

This test writes and reads daia on the disk; it is not destructive to the
customer's data. The file system exerciser can also be used on an NFSmounted file system.
EXAMPLE:

Ezercise the /usr/tmp file system continuously using 10 processes in
the background:
fex -pl0 -ffusr/tmp &

A.1.4 Line Printer Exerciser
Syniax
ip=l-h)i-ofile}{-tmin)-fpath{-pn]
Arguments
Jdev

Printer device name to exerciee.

Options
B

Prints 2 help message.

-afile

Writes run-time statistics to filz. Default file is $LOG_LPX 44.

£-4

KN210 CPU Module Set System Maintenance

-trun

Runa the enerciger for 2 minutce Default ia run continuously.

-pn

To save paper. pauses printing for » minutes end only exercizes the
controller. Default 18 15. A value of 0 indicates no peuse.

EXAMPLE:

Exercise Ipl: Ipx -dlpl

A.1.5 Memory Exerciser
Syntax
memx{-hi{-s){-ofile]{-tmin]{-m/]-pk]

Options
-l

Prints & help message.

Disables shered memory testing. Shared memory ie software functionslity,
not hardware

-ofile

Writes run-time statistics to file. Default file is $LOG_MEMX 6.

tmen

Runs exercieer for ¥ minutes. Defeult ie run continuoualy.

ERyY

Memory size in j bytes to be tested by each spawned procesa. Default ie

-pk

Number of memx processes to epawn. Maximum is 20. Default is 20.

{total memoryVv20.

Usage

The memory exerciser is restricted by available swap space. Errors like out
of memory generally indicate swap space was used up. If you have more
physical memory than swap space, you may see this problem. If so, reduce
the number of spawned processes and/or the size of memory you are testing.

Running the memory exerciser can also cause other users to have the same

memory problem.

EXAMPLE:

Exercise all memory and the shared memory functionality for 10
minutes in the background:
memx -t10 &

ULTRIX-32 Exerciser and Uerf Command Summary

A-5

A.1.6 Magtape Exerciser
The magtape exerciser reads, writes, and validates random data from the
heginning of the tape (BOT) to the end of the tape (EOT).
Syntax
méx{options]-adev
mixioptions]-sdev
méxfoptions]-idev
mtxfoptions)-vdev
Arguments
-adev

Usge short-, long-, and variable-length record teats on raw device dev.

-aedev

Use short records on raw dev.

ldev

Use long records on raw dev.

-vdev

Use variable records on raw dev.

Options
<

Prints 8 ' .clp message.

«ofile

Writes run-time statistica to file. Default file is #LOG_MTX
_#4.

-t

Runs ezerciser for 1 minutes. Default is run continuously.

oK)

Record length for long record test. Range is 1 to 20480. Default is 10240.

-th

Size of file in 2 number of records. Default: -1, go to EOT.

EXAMPLE:

Run all record lengths on tape drive rmtOh for 5 minutes in the

background:

mtx -armtOh -t5 &

A-6

KN210 CPU Module Set System Maintenance

A.1.7 TCP/IP Network Exerciser
Syn‘ax

netzl-h){-tmin}{-pmlnodename
Arguments

Node name of target system to test. May aleo be the host system name

nodename

Options
-

Prints & help message.

-tmin

Runs exerciger for x minutes. Defeult is run continuously.

“pm

Port number.

Usage

The TCP echo service defined in the /etc/inetd.conf file must not be
commented out (# at start of line) on the host and target systems.
EXAMPLE:

Exercise the network from the local host to the remote node max

continuously in the backg—ound:
netz max &

ULTRIX-~32 Exerciser and Uerf Command Summary

A-7

A.2 Uerf Error Log Commands
The Uerf utility generates error log reports and does bit-to-text translation
for hardware device registers and messages, similar to ERF on VMS. Syntax
18 case sensitive If no options are specified, all errors are reported.
To disable ervor logging to an error log file, type:
§ /etc/eli -d

To enable error logging in multiuser mode, type:
¢ /etc/els -e

Syntax
lete/uerfloptions...)

Optlons
A adapter tvpe

EXAMPLE: /etctuerf -A uba nmi

ale

BVP controller

alo

BVP controller

bia

Bi LESI edapter

bua

BI UNIBUS adepter

mend

NMI ervore

uba

VAX UNIBUS adapter

defoult

Report all error types

¢ classes

EXAMPLE: /etc/uerf -¢ oper

ory

All hardware and software ervors

maind

Maintenance events

Gper

System statue; etartup/ashutdown; configuretion

-8

KN210 CPU Module Set System Maintenance

Reporta ervore for MSCP digks (ra, rd).
diake are reported.
EXAMPLE: /etc/uerf -D ra80

Default: ol MSCP

Specifiea the ervor log file to be used to generate the report.
EXAMPLE: /etciucef -f old erroriog
-h

Dieplaya @ brief help messege.

‘B

Selecta ervore only for the apecificd system neme.
EXAMPLE: /etc/uerf -H guru

B mainframe ervors

EXAMPLE: /etcverf -M mem

cpo

Reports CPU errore and machine checks.

mein

Reports memory ervore (SBE end DBE).

default

Reports all error typee.

Uerf runs.

Waita for evroras to be logged and immediately

reporis them.

-0 outpuf

EXAMPLE: /etc/uerf -0 full

brief

Reports ervors in brief format (defau!t).

full

Reports all information for each ervor.

tores

No bit-to-text transistion for register values.

-O operating system events

EXAMPLE: /etc/uerf -O segref

aef

Arithmetic exception foults

ast

Asynchronous trap exception faults

bpt

Breakpoint instruction faults

cmp

Compatibility mode feults

pag

Pege fauits

ULTRIX-32 Exerciser and Uerf Command Summary

A-9

Privileged instruction faulta

pro

Protection faults

ptf

Page table faulta

raf

Reserved sddress faults

sof

Reserved operand faults

ecf

Syetem call exception faults

eeg

Segmentation faults

tra

Trace exception faults

pio

Reports xfc instruction faults

Reports errors in reverse chronolagical order.

-x record_type

EXAMPLE: /ete/uerf -r 102,210,250

Haerdware Detected Error Types:

160

Machine check

1018

Memory CRD/RDS errors

102

Disk errors

103

Tspe errors

104

Device controller errors

168

Adapter errors

108

Bus errors

1077

Stray interrupts

) [1:]

Asynchronous write errore

109

Exceptions/faults

113

Stack dump

A-10

KN210 CPU Module Set System Maintenance

Software Detected Ervor Typea:
200

Panica (bug checks)

201

Cl ppd information

informational ASCII Mesaage Types:

Informational

260
Ope rational Meessage Types:

890

Startup

901

Shutdown

310

Time change

380

Diegnostic information

861

Repair information

-p sequence numbers

Reporta errors for the specified sequence numbers.

-8

Summarizes errnr information.

EXAMPLE: /etc/uerf -8 1011,1320

EXAMPLE: /etc/uerf -S -0 full

-t a.dd-mmm-yyyy.hh:mm:zs e.dd-mmm.yyyyhh:mm:zs

EXAMPLE: /etc/uerf -t 5:08-aug-1889:13:20:00
8

Starting datz and time

)

Ending date and time

Day

EnsRn

Month

Lappd

Year

ULTRIX-32 Exerciser and Uerf Command Summary

A-11

SEE

Hour

Minute
Second

Reports errors for TMSCP tapes (th, tu). Default: all TMSCP
tapee are reported.
EXAMPLE: /etefuerf -T tuBl

Excludes specified error types from the report.
EXAMPLE: /etc/uerf -x -r 102,103

Displaye the entire error record as hexadecimal data. Used
only for debugging.

A-12

KN210 CPU Module Set System Maintenance

Appendix B

KN210 Address Assignments
This appendix explains how to access R3000 physical address locations and
provides physical address space maps for the KN210 CPU module set.

B.1 Accessing Physical Locations (R3000)
From the R3000 processor, you must use virtual addresses to access
physical locations. The R3000 processor accepts virtual addresses only.
Figure B-1 shows the virtual memory map for the R3000 and CVAX
processore. Note that the R3000 virtual addresses are separated into kernel
segments (ksegs):
e

To address physical locations, use the upper four bits of the kerrel
segment.

Always reference kernel segment 1 for I/O addresses, which are
unmapped and uncached.

To calculate the virtuai address for kernel segment 0, add 80000000 as
an offeet to the physicai address.

To calculate the virtual address for kernel segment 1, add a0000000 as
an offset to the physical address.

For example, from the R3000 processor:

If you are using kernel segment 0 (80000000; unmapped and cached),
use 8001a340 to access physical location 0001a340.

[f you are using kernel segment 1 (a0000U(0; unmapped and uncached).
use a001a340 to access physical location 000 1a340.

Use a008000c¢ to access DMA error address register 1008000c (physical).

KN210 Address Assignments

B-1

KN210 Virtual Memory Map

Figure B-1:

g
g

i,
il

slef,
HE I

Ao off o
i

g
2

o [l
8

B-2

$ls 818 8|5 E;s

o
e

KN210 CPU Module Set System Maintenance

B.2 KN210 CPU Module
Sections B.2.1 through B.2.4 list contents and address ranges for the KN210
CPU module (M7635~AA).

B.2.1 R3000 Physical Address Space Map (M7635-AA)
Table B-1:

R3000 Memory Space

Contento

Address Range

Local memory space (up to 64 Mbytes'

0000 0000-03FF FFFF

Reserved memory space

0400 0000-OFFF FFFF

Table B-2:

R3000 input/Output Space

Contents

Address Range

Reserved Q22-bus /0 space

1000 00001000 0007

€22-bus flioating address apace

1000 0008-1000 O07FF

User reserved Q22-bus /0 space

1000 0800-1000 OFFF

Reserved and fixed CSR Q22-bus 1/0 space

1000 1600-1000 1F3F

Interprocessor communication register

1000 1F40

Reserved Q22-bus I/0 space

1000 1F42-1000 1FFF

Regerved /0 module address space

1000 2000-1003 FFFF

Two copies of local ROM

1004 0000-1007 FFFF

DMA system configuration register

1008 0000

DMA system error register

1008 0004

Q-bus error address register

1008 0008

DMA ervor addresa register

1008 000C

Q22-bus map baee register

1008 G010

Reeerved

1008 0014-1008 OOFF

Muin memory configuration register 00

1008 0100

Main memory configuration register 01

1008 0104

Mein memory configuration register 02

1008 0108

Mein memory configuration register 03

1008 010C

Main memory configuration register 04

1008 0110

Mein memory configuration register 05

1008 0114

Mein memory configuration regieter 06

1008 0118

Mein memory configuration register 07

1008 011C

Main memory configuration register 68

1008 0120

Main memory configuration register 09

1008 0124

Main memory configuration register 10

1008 0128

KN210 Address Assignments

B8-3

Table B-2 (Cont.):

R3000 input/Output Space

Contents

Address Range

Main memory configuration register 11
Main memory configuration register 12

1068 012C
1008 0130

Mein memory configuration regieter 13

1008 0134

Maoin memory configurstion rester 14

1008 0138

Me'n memory configuration register 16

1008 013C

Mein memory ciror etatus register

1008 0140

Main memory control/diagnostics status register

1008 0144

Reasrved /O module addroas space

1008 0148-1008 SFFF

Interrupt status

1008 4000

Boot end diagnoatic register

1008 4004

Select proceesor register

1008 4008

Reserved /0 module address space

1008 400C-1008 TFFF

Q22-bus map regislers

1008 8000-1008 FFFF

Reserved /O module addrees apace

1008 0000-1013 FFFF

88C baee addreea register

1014 0000

Reserved

10140004-1014000F

88C eonfigurstion register

1014 0010

Regerved

10140014-1014001F

CDAL bus timeout control register

1014 0020

Regerved

10140024 -1014002F

Diagnostic LZD register

1014 0030

Reserved 1/O module address space

1014 0034-1014 0088

Time-of-year register

1014 006C

Remerved

1014 0070-1014 007C

Console receiver control/stetus

1014 0080

Console receiver data buffer

1014 0084

Congole trensmitter control/statue

1014 0088

Console transmitter data buffer

1014 ¢08C

Reserved

1014 0080-1014 GODB

10 system reset register

1014 6ODC

Reserved

1014 00E0-1014 OOEF

ROM deta register

1014 GOFO

Bue timeout counter

1014 004

Intervel timer

1014 00F8

Reserved

1014 0OFC-1014 0OFF

Timer 0 control register

1014 0100

Timer 0 interval register

1014 0104

Timer 0 next intervel register

1014 0108

Timer 0 interrupt vector

1014 016C

Timer 1 control register

1014 0110

B-4

KN210 CPU Module Set System Maintenance

Table B-2 (Cont.):

R3000 Input/Output Space

Contents

Address Ronge

Timer 1 interval register

1014 0114

Timer 1 next interval registes

1014 0118

Timer 1 interrupt vector

1014 011C

Reserved

1014 0120-1014 0129

Address decode match register 0

1014 0130

Regerved

10140138-1014013F

Addreaa decode mask register 0

1014 0134

Addreas docode match register 1

1014 0140

Addreen
decode mash register 1

1014 0144

Regerved

1014 0148-1014 03FF

Battery backed-up RAM

1014 34001014 O7FF

Regerved

10140800-13FF FFFP

Local §22-bus memory apace

1460 0000-143F FFFF

Reserved (4 copies local Q22-bus memory)

1440 0000-14FF FFFF

Regerved

1660 0000-16060 CO4F

Vector road register 0!

1800 0050

Vector read register 1!

1600 00564

Vector read register 2!

1600 0058

Vector reed register 3!

1600 005C

Reeerved
Write-ervor addreas regster!
Regerved

1600 0080-16FF FFFF
1760 G000
1700 00604-1FBF FFFF

Regerved

1FC2 0000-FFFF FFFF

ROM!

1FCO 0000-1FC1 FFFF

1 Acceasible only from R3000 proceasor.

KN210 Address Assignments

B-5

B.2.2 KN210 Diagnostic Processor Physical Address Space
Map (M7635-AA)
Table B-3:

Dlagnostic Processor Memory Space

Contents

address Range

Locel memory space (up to 64 iMbytes)
Reserved memory space

0000 C000-03FF FFFP
0400 0000-1FFF FFFF

Table B-4:

Dilagnostic Processor Input/Output Space

Comtents

Address Range

Reserved Q22-bus /0 space
Q22-bus floating addrees epace

2060 0000-2000 0007

User reserved Q22-bus /O epace

2000 0800-2000 OFFF

Reeerved and fized CSR Q22-bus I/0 space

2000 1000-2000 1F3F

Interprocessor communication register

2000 1F¢0

Reeerved Q@22-bus 1/0 space
Regerved 1/0 module address epace

2000 1F42-2000 1FFF
2000 2000-2003 FFFF

MicroVAX system type register (in ROM)

2004 0004

Local ROM; halt mode
Local ROM; run mode

2004 0000-2005 FFFF
2008 0000-2007 FFFF

DMA system configuration register

2008 0000

2000 0008-2000 07FF

DMA eystem ervor register

2008 06004

@-bus error address register

2008 0008

DMA ervor eddrees register

2008 000C

Q22-bit mep baee register

2008 0010

Reserved

2008 0014-2008 COFF

Main memory configuration register 00

2008 0100

Main memory configuration regicter 01

2008 0104

Meain memory configuration regisicr 02

2008 0108

Mein memory configurstion register 03

2008 010C

Main memory configuration register 04
Mein memcory configuration regicter 04

2008 0110
2008 0110

Main memecry configuration register 05

2008 0114

Main memaory configuretion register 08

2008 0118

Mein memory configuration register 07

2008 011C

Mein memory configuration register 08

2008 0120

Mein memory configuration register 09
Main memory configuration register 10

2008 0124
2008 0128

Main mems:7 configuration regiater 11

2008 012C

KN210 CPU Module Set System Maintenance

Table 8-4 (Cont.):

Dlagnostic Processor input/Output Space

Contents

Address Range

Main memory configuration register 12

2008 0130

Main memory configuration register 13

2008 0134

Main memory conflguration register 14

2008 0138

Main memory configuration register 156

2008 013C

Main memory error status register

2008 0140

Main memory control/disgnostica status register

2008 0144

Regerved /O module addrees gpace

2008 0148-2008 3FFF

Interrupt etatus

2008 4000

Boot and diagnostic register

2008 4004

Select processor register

2008 4008

Reserved /O module addrees space

2008 400C-2008 TFFF

Q22-bus map registers

2008 8000-2008 FFFF

Reserved /O module address space

2008 0000-2013 FFFF

88C base sddreen register

2014 0000

Regeyved

2014 0004-2014 O0OF

S8C configuration register

2014 0010

Regerved

2014 0014-2014 C01F

CDAL bus timeout control register

2014 0020

Regerved

2014 0024-2014 CO2F

Diegnostic LED register

2014 0030

Reserved /0 module eddrees space

2014 0034-2014 0088

Time-of-year register

2014 008C

Regerved

2014 0070-2014 007C

Congzole receiver control/etatus

2014 0080

Conaole receiver date buffer

2014 0084

Conssle transmitter control/status

2014 6088

Console transmitter data buffer

2014 008C

Reserved

2014 0090-2014 00DB

1/0 oystem reset register

2014 0ODC

Reeerved

2014 00E0-2014 OOEF

ROM date register

2014 00F0

Bua timgout counter

2014 00F4

Interval timer

2014 0OF8

Regerved

2014 GOC-2014 OOFF

Timer 0 control register

2014 01060

Timer 0 intervel register

2014 0104

Timer 0 next interval register

2014 0108

Timer 0 interrupt vector

2014 0106C

Timer 1 control register

2014 0110

Timer 1 interval regicter

2014 0114

KN210 Address Assignments

B-7

Table B—4 (Cont.):

Dlagnostic Processor input/Output Space

Contents

Address Range

Timer 1 nest interval register
Timer 1 interrupt vector

2014 0118
2014 011C

Reserved

2014 0120-2014 C12F
2014 0130
2014 0134

Addresa decode match register 0
Address decode mask register 0

2014 0138-2014 013F
2014 0140

Reeerved
Addrean decode match register 1

2014 0144

Address decode mesh register 1

2014 0148-2014 033F
2014 0400-2014 O7FF
2014 0800-2FFF FFFF
3000 0000-303F FFFF
3040 0000 IFFF FFFF

Reeerved
Batlery becked-up RAM
Regerved /O module addrees apace
Local @22-bue memory space
Reeerved /O module addreas apace

B.2.3 Diagnostic Processor Registers
Several KN210 internal processor registers (IPRs) are implemented in
the SSC chip rather than the CVAX chip. These registers are listed in
Table B~5. The R3000 accesses these registers through R3000 memory
space.

Table B-5:

Diagnostic Processor Registers

Dec

Hex

Reogister Name

Mnemonic

Type

Location

1
2
3

Kernel Stack Pointer

Ezecutive Stack Pointer
Supervisor Stack Pointer
User Stack Pointer

KSP

ESP
Ssp
USsP

riw

CVAX

4
)
6
7

4
B
8
?

Interrupt Stack Poincer
Reserved
Reserved

ISP

r/w

77 Buss Regimer

POB
POLR

v/w
riw

CVAX
CVAX
CVAX
CVAX

1
2
3

8
9

11
i2
.o
14

B-8

8
9

Reserved
PO Base Register
PO Length Register

B
C
D
E

P1 Length Register
System Base Regioter
System Length Register
Reserved

PIRR

PILR
SBR
SLR

riw
riw
r’w

KN210 CPU Module Set System Maintenance

riw
viw
r/w

CVAX
CVAX
CVAX

Cvax
CVAX

Ccvax

CVAX
CVAX
CVAX
CVAX

Table B-5 (Cont.):

Dilagnostic Processor Registers

Dec

Hex

16
16

F
10

Reserved
Proceas Control Block Baee

19
20

13
14

22
23
24

interval Clock Control Status

ICCS

riw

CVAX

Neat Interval Count

NICR

CVAX

Interval Count

ICR

CVAX

27
28
29
30

iB
1C
1D
1E

Time-of-year Regieter
Console Storage Receiver Status
Console Storage Receiver Data
Console Storage Transmitter

TOY
CSRS!
CSRD!
CSTS!

riw
riw
r
r/'w

88C
88C
88C
88C

31
32

IF
20

Console Storage Transmitter Date CSDB!
Console Receiver Control Statue RXCS

w
ri'w

8sC
88C

Console Transmitter Control

riw

Console Trenamitter Data Buffer

38
37

24
26

38
39

Mpnemonic

Type

System Control Block Base

PCBB
SCBB

r/w
riw

Interrupt Priority Level

IPL

viw

CVAX

AST Level
Software Interrupt Request

ASTLVL
SIRR

riw
w

CVAX
CVAX

Software Interrupt Summary

SISR

riw

CVAX

16
17

Reserved
Regerved

Status

Console Receiver Data Buffer

Location
CVAX
CVAX

CVAX

CVAX
CVAX

8SsC

TXDB

8scC

Trenalation Buffer Diagble
Cache Disable

TBDR
CADR

riw
riw

CVAX
CVAX

28
27

Machine Check Ervor Summery
Memory System Error

MCESR
MSER

r'w
r/w

CVAX
CVAX

40
41
42

28
29
2A

Reserved
Reserved
Consocle Saved PC

SAVPC

CVAX
CVAX
CVAX

43
44
45

2B
2C
2D

Console Seved PSL
Reserved
Regerved

SAVPSL

46
47

2E
2F

Reeserved
Reaesrved

IO System Reeet Register

Status

RXDB
TXCS

S8C

CVAX
CVAX
CVAX
CVAX
CVAX

IORESET

CVAX

KN210 Address Assignments

B-9

B.2.4 Global Q22-bus Memory Space Map
Table B-6:

Q22-bus Memory Space

Contents

Address Range

Q22-bus memory epace (ortal)

G000 0000-17T7 TT1TT

Table B-7:

Q22-bus /0 Space with BBS7 Asserted

Contente

Address Range

Q22-bus /O space (octal)

1778 0000-177T7 TI7T7

Reeerved Q22-bus 1/0 space

1776 0000-1778 0007

Q22-bus flosting address space

1776 0010-1778 3777

User-reserved @22-bus /0 apace

1778 4000-1778 T77T7

Reserved and fized CSR Q22-bus 1/0 space

1777 0000-1777 7477

Interprocesscr communication register

1777 7600

Regerved @22-bus 140 space

1777 16021777 7777

B-10

KN210 CPU Module Set System Maintenance

B.3 KN210 /O Module
Sections B.3.1 and B.3.2 list the contents and address ranges for the KN210
1/0 module (M7636-AA).

B8.3.1 R3000 Physical /O Address Space Map (M7636-AA)
Tabie B~-8:

R3000 Physical Addresses

Contents

Address Range

Regerved /O module address space
Reserved 110 module addreas space
Reserved /O module address space
N1 etation address ROM
Regerved /O module addrees space

1000 2000-1003 FFFF
1008 0148-10G3 3FFF
1008 460C-1008 4200
1008 4200-1008 427C
1008 4280-1008 43FF

Reserved /O module address space

1008 4408-1008 45FF

NI regioter data port
NI register eddress port

1008 4400
1008 4404

MBI diegnostic register 0
M8S! diagnostic register 1
MSI diagnostic vezister 2
MSI control and status register
MSH ID register
Reserved MSI regicter
Reserved MSI register
MSI timeout register
Reserved MSI register
Reserved MSI regioter
Reserved MBI register
Reserved MBI register
Reserved MSI register
Reserved MSI register
MSI short target list pointer
MSI long target list pointer
M8SI initietor list pointer
BiSI DSSI control register
MSI DSSI status register
Reserved MSI register
Reegerved MSI regieter
MSI diagnosatic control regieter
MBI clock control register

1008 4800
1008 4804
1008 4608
1008 480C
1008 4610
1008 4614
1008 4618
1008 461C
1008 4620
1008 4824
1008 4628
1008 482C
1008 4630
1008 4834
1008 4638
1008 463C
1008 46840
1008 4644
1008 4648
1008 464C
1008 4850
1008 4854
1008 4658

MSI internal state register 0

1008 465C

KN210 Address Assignments

B-11

Table B-8 (Cont.):

R3000 Physical Addresses

Contents

Address Range

MSI internal state register 1

1008 4650

MSI internal state register 2

1008 4664

MSI internal state register 2

1008 4668

Regerved MSI register

1008 466C
1008 4670

Reserved MSI register
Regerved MSI register

Regerved MSI register
Regerved MS! regicter

1008 4674
1008 4678
1008 487C

Regerved /O module address space

1008 4680-1008 7FFF

Reserved 1/0O module address space

1009 0000-1009 FFFF

MSI buffer RAM

1010 0000-1011 FFFF

NI buffer RAM

1012 0000-1013 FFFF

B.3.2 Diagnostic Physical /O Address Space Map
(M7636—-AA)
Table B-9:

Diagnostic Input/Output Addresses

Contenta

Addrese Range

Reserved 170 module addrees space
Reserved 1/0 module addresa space

2000 20692003 FFFF
2008 0148-2008 3FFF

Regerved /O module address space

2008 400C-2008 4200

NI station addrees ROM

2008 4200-2008 427C

Reserved /O module address space

2008 42802008 43FF

NI register data port

2008 4400

NI register address port

2008 4404

Regerved 1/0 module addresa epace

2008 4408.-2008 45FF

MSI diagnostic register 0

2008 4600

MSI diagnostic register 1

2008 4604

MSI diagnostic register 2

2008 4608

MSI control and atatus register

2008 460C

MSI ID register
Reserved MSI register
Reserved MSI register

2008 4610

MSI timeout register

2008 461C

Reserved MSI register

2008 4620

2008 4614
2008 4618

Reserved MSI register

2008 4624

Reserved MSI register

2008 4628

B-12

KN210 CPU Module Set System Maintenance

Table B-9 (Cont.):

Diagnostic input/Output Addresses

Contents

Address Range

Reserved MSI register
Reserved MSI register

2008 462C
2008 4630

Regerved MSI register

2008 4634

MSI short target list pointer
MSI long target list pointer

1008 4638
2008 463C

MSI initiator list pointer

2008 4640

MSI DSSI control register
MSI DSSI status register

2008 4644
2008 4648

Reserved MSI register

2008 464C

Reserved MSI register

2008 4650

MSI diegnostic control regirter

2008 4854

MBSI clock control register

2008 4658

MEI interneal state regiater 0

2008 485C

MSI internal state register 1

2008 4660

MSI internal state register 2

2008 4654

MSI internal state register 2
Regerved MBI register

2008 4888
2008 488C

Regerved MSI register

2008 4670

Reserved MSI register

2008 4674

Reserved MS] register

2008 4678

Resgerved MSI register

2008 487C

Reserved /0 module address space

2008 4£880-2008 7FFF

Regerved 1/0O module address space

2009 0000-2009 FFFF

MSI buffer RAM

2010 00600-2011 FFFF

NI buffer RAM

2012 0000-2013 FFFF

KN210 Address Assignments

B-13

HOA PG POt eeaot et etesed ottt tetdorssetts st ntededssissed
mxxmmmmmmxxmx

Appendix C

Configuring the KFQSA
This appendix describes the KFQSA storage adapter and explains how to:
o

Configure the KFQSA storage adapter at installation

Enter console I/O mode

Run the Configure utility

Program the EEROM on the KFQSA

Reprogram the EEROM on the KFQSA

Change the ISE's allocation class and unit number

C.1 KFQSA Overview
The KFQSA module is a storage adapter that allows Q-bus host systems
that support the KFQSA to communicate with storage peripherals based on
the Digital Storage Architecture (DSA), using the Digital Storage Svatem
Interconnect (DSSI). In a KN210-based system, one KFQSA module can
connect up to six RF-series integrated storage elements (ISEs) to the host
system, using a single DSSI bus cable.

The KFQSA contains the addressing logic required to make a connection

between the host and a requested ISE on the DSSI bus. Each ISE has

its own controller, which contains the intelligence and logic necessary to
control data transfers over the DSSI bus. The KFQSA presents a mass
storage contro! protocol (MSCP) U/Q port for each ISE.

The EEROM on the KFFQSA contains a configuration table. After you install
the KFQSA, you program the EEROM with the CSR address for each ISE
in the system.

Configuring the KFQSA

C-1

C.2 Configuring the KFQSA at Installation
At installation, configure the KFQSA as follows:

CAUTION: Static electricity can damage integrated circuits. Use the
wrist strap and antistatic mat found in the Antisiatic Kit (29-26246)
when you work with the internal parts of a computer system.
1.

Check the KFQSA module for the presence of a jumper intended for
manufacturing use or.’y. The location of this jumper is shown in
Figure C-1. Remove the jumper, if present.

Toset a temporary CSR address that enables you to access the EEROM,
use the four-position DIP switchpack shown in Figure C-1 as follows:
a.

Setswitches 1, 2, 3, and 4 to reflect a fixed CSR address to allow the
KFQSA to be programmed. Example C—1 shows the correct switch
settings for a system with only one KFQSA.

Install the KFQSA adapter module into the backplane according to
the procedures in the appropriate enclosure maintenance manual.

C-2

KN210 CPU Module Set System Maintenance

Figure C-1:

KFQSA Module Layout (M7769)

Four-Position
Switchback
On

LEDs

<17

Jumper /

(For Manutacturing
Use Only)

#MLO-001878

Configuring the KFQSA

C-3

Examiple C-1:

KFOSA (M7769) Service Mode Swich Settings

KFQSA Four-Position

Switchpack

S/N

Mode

Fx/Fl

MSB

LSB

Switches:

hddress

First

RFQSA

of £

0774420

Additional:

off

0774424

off

0774430

of f

off

0774434

S/ =

Service mode/Wormal

Fu/Fl

Fixed

operating mode

fizxed/floating CSR address

C.2.1 Entering Maintenance Mode
After installing the KFQSA, you issue a senes of commands to the KN210
system at the maintenance mode prompt (>>>) in order to program the

EEROM on the KFQSA You may type these commands in either uppercase
or lowercase letters. Unless otherwise specified, type each command, then

press [Rowm].

Enter maintenance mode as follows:
1

Set the operation switch on the H3602-AB CPU cover panel to the
maintenance position (¢)

Set the function switch on the CPU cover panel to the enable position
()

Set the on/off power switch to on (1)
When the power-up self-tests complete, the console prompt appears, as
shown in Example C-2.

C-4

KN210 CPU Module Set System Maintenance

Entering Console Mode Display

Example C-2:

system tests.

Per forming normal

.40, .39,.38..37..36..35..
51..50..49 ..48..47..46..45..44. .43..42..41.

34..33..32..31

.30..29..28..27..26..25..24..23..22..21..20..19..18..

17..16..15 ..14..13..12..11..10..09..08..07..06. .05..04..03.,.

Tests

completed.

>>>

C.2.2 Displaying Current Addresses
Type sHow 0BUS to display the current Q22-bus addresses (Ezample C-3).
Note that the KFQSA adapter appears in service mcde as i\FQSA #0.
Example C-3:
>>>

SHOW QBUS Display

SHOW QBUS

(774422)

GAAO

-200019%20

(174450)

-20001922

(774442)

FF0O

-20001924

(774444)

FF2B

~200019%9z6
-200C1928

(774446)

FFO09

FFA3

-2000192A

(774452)

-2000192C

(774454)

8000

=2000192E

(774456)

-20001940

(774500)

-200019242

(774502)

=20001F40

{777500)

FFO8

(000)

KFQSA $0

{120)

DELQA/DEQNA/DESQA

(260)

TQEKSO/TQK?70/TUB1E/RV20/KFQSA-TAPE

(004)

IPCR

1030

FF96

0000

(7744%0)

0000

-200019212

Space

(774420)

I/0

-20001910

Scan of Qbus

OBCO

0020

Scan of Qbus Memory Space
>>>

Configuring the KFQSA

C-5§

C.2.3 Running the Configure Utility
Now that you have physically reconfigured the system by installing the
KFQSA storage adapter, you must run the Configure utility to find the
correct addrese for each device and module in the system. The Configure
utility uses Q-bus/UNIBUS fired and floating address space rules.

Run tue Configure utility as follows. Refer to Example C4.
1

At the maintenance mode prompt, type CONFIGURE, then type HELP at
the Device,Number? prompt for a list of devices that can be configured.

NOTE: Some of the devices listed in the HELP display are not supported
by the KN210-A CPU.
For each device in the system, type the device name at the
Device,Number? prompt. If you have more than one of the same
type, type a comma followed by the total number of that device. In
Example C—4, the system contains one KFQSA with six ISEs.

Be sure you list all the devices: those already installed and those you
plan to install.
Type ExiT. The Configure utility displays an address and vector
assignment for each device. Example C—4 shows the address and vector
assignments and the device input. Write down the addresses for the
KFQSA devices.
For all modules except the KFQSA, verify that the CSR addresses are
set correctly by comparing the addresses listed in the SHOW QBUS
command with those listed in the Configure utility display. If necessary,
remove modules from the backplane and reset switches or jumpers to
the addresses in your Configure display, using module removal and
replacement procedures in BA213 Enclosure Maintenance.

C-6

KN210 CPU Module Set System Maintenance

Exemple C-4:

>>>

Configure Dispiay

CONFIGURE

Enter

device

configuration,

Device, Number?

HELP,

or EXIT

help

Devices:

Lrvil

K¥XJ11

DLV11J

DZQ11

bzZvll

DFAO1

RLV12

TSVOS

RXv21

DRV11W

DRV11B

DPV11

DMVil

DELQA

DEQRA

DESQA

RQDX3

KDASO

RRDS50

RQC25

RFQSA-DISK

TQRSO

TOQK70

TUB1E

RV20

KFOQSA-TAPE

KMV11

IEQ11

DRQ11

DRV11

CHRAl6
LNvV21
Kuviic

CXB16
QPSS
ADV11D

CXYo8
D§V1l
AAV11D

VCBO1
ADV11lcC
vCcBo2

QVss
ARV11C
QDss

LNvVil
AXviilc
DRV11J

DRQ3B

vsvzl

18QO1

IDV11A

ILV11B

IbV11cC

IDV1iD

IAV11A

IAV11B

MIRA

ADQ32

DTCO4

DESHA

IGR11

Numbers:

to 255,

default

Device, Number?

RFQSA-DISK,
6

Device, Number?

DESQA

Devica, Number?

TQK70

Device,Number?

EXIT

Address/Vector Assignments
=774440/120

DESQA

~772150/154

KFQSA-DISK

'Hode

=760334/300 KFQSA-DISK

'Node

~760340/304

KFQSA-DISK

!'Node

=760344/310

KFQSA-DISK

'Node

-760350/314

KFQSA-DISK

'Node

-760354/320

KFQSA-DISK

!'Node

=774500/260

TQKTO

(assigned

order,

0 to n)

Configuring the KFQSA

C-7

C.3 Programming the KFQSA
Program the configuration table in the EEROM of the KFQSA to include
all ISEs on the DSSI bus, as follows. Refer to Examples C-56, C-6, and C~7.
1.

Determine the DSSI node plug address for each ISE you are configuring.
Start with node 0, then continue up through node 5. In Example C-4,
nodes 0, 1, 2, 3, 4, and 5 are used; node 7 is saved for the KFQSA
adapter.

To program the KFFQSA, type SET HOST/UQSSP/MAINT/SERV 0 at the
console prompt on each system.

Type HELP to display a list of supported commands.

Program the KFQSA to include each DSSI devire in the system:

For each ISE: type seT, followed by the node number, the CSR
address (from the list of addresses you obtained from the Configure
utility), and the model number (disk ISE's are model 21).

Type sHow to display the configuration table you just programmed.

¢.

Check the display to make sure the addresses are correct.

Type EXIT to save the configuration table or QUIT to delete the
table.

C-8

KN210 CPU Module Set System Maintenance

Example C-5: Digplay for Programming
the Firet KFQSA
>>> SET ROST/UQSSP/MAINT/SERV 0

'0 refers to first KFQSA
tin the

UQSSP Controller

(772150)

Enter SET,

SHOW,

Node

CLEAR,

CSR Address

HELP,

EXIT,

system.

or QUIT

Model

weccccs KFQSA =-o====-

? HELP
Commands:

SET <node> /KFQSA

'Sets KFQSA DSSI node
tnumber

SET <node> <CSR_address> <model>

!Enables a DSSI device

CLEAR <node>

'Disables @ DSSI device

SHOW

Digplays current
'configuration

HELP
EXIT

'Diepleys this display
'Saves the KFQSA program

QuUIT

'Does not msave the KFQSA
!'program

Parametoers:

<node>
<CSR_sddress>
<mode l>
?

SET 0 772150 21

SET 1 760334

SET 2

SET 3 760344

SET 4

760350 21

SET 5

760354

SHOW

'0 through 7
1760010 to 777774
121 (disk) or 22 (tape)

760340 21
21
21

Node

CSR Address

Model

762105

760334

760340

760344

760350

760354

vwesve

KFQSA sovooee

exit

Programming the KFQSA...

!Noete

from the system that

'the KFQSA is
'being programmad.

Configuring the KFQSA

C-8

Turn the system power off by setting the on/off switch to off (0).

Remove the KFQSA from the backplane.

Confirm that the unit ID plugs on the enclosure's operator control panel

On the KFQSA, set switch 1 on the four-position switchpack to Off (1).

(OCP) match the node IDs you just programmed.

(Figure C~1 shows the location and position of the switchpack.) This

action sets the KFQSA to the normal operating mode; switches 2, 3,
and 4 are ignored since switch 1 is set to off, and the DSSI addresses
are read from the EEROM.
9.

Reinstall the KFQSA in the backplane.

10. Power on the system by setting the on/off switch to on (1). Wait for the
self-tests to complete.

11, At the maintenance mode prompt, type sHOW QBUS to verify that all
addresses are present and correct, as shown in Example C-6.

12. Type sHOW DEVICE to verify that all ISEs are displayed correctly, as
shown in Example C-7.

C-10

KN210 CPU Module Set System Maintenance

Example C-6:
>>>

SHOW QBUS Digplay

SHOW QBUS

Scan of Qbus 1/0 Space
=200000DC

{760334)=0000

~200000DE

(760336)=0AR0

=200000E0

(760340)=0000

=200000E2

(760342)=0AR0

=200000E4

{760344)=0000

=-200000E6

(760346)=0AR0

=200000E8

(760350)=0000

=200000EA

(760352)=0AR0

«200000EC
=200000EE

(760354)=0000

=20001468

(772150)=0000

=2000146A

(772152)=0AM0

=20001920

(774440)-FF08

-20001922

1774442)=FF00

-20001924

(774444)=FF2B

(300)

ROQDX3/KDASO/RRD50/RQC25/KFQSA-DISK

(304)

RQDX3/KDA50/RRD50/RQC25/KFQSA-DISK

(310)

RQDX3/KDAS50/RRD50/RQC25/KFQSA-DISK

(314)

RODX3/KDAS0/RRD50/RQC25/KFQSA-DISK

(320)

RQDX3/KDAS0/RRD50/RQC25/KFQSA-DISK

(154)

RQDX3/KDAS0/RRD50/RQC25/KFQSA-DISK

(120)

DELQA/DEQNA/DESQA

(260)

TQKS0/TQK70/TUB1E/RV20/RFQSA~TAPE

(760356)=0AR0

=20001926

(774446)=FF09

-20001928

(774450)=FFA3

=2000192A

(774452)=FF96

=2000192C

(774454)=0050

«2000192E

=20001940

(774456)=1030
(774500)=0000

=20001942

(" 7450Z,=0BCO

=20001F40

(77.500)=(004)

IPCR

Scan of Qbus Mumorv Space
>>>

Configuring the KFQSA

C-~11

Example C-7:

SHOW DEVICE Display

>>> SHOW DEVICE

DSSI

=DIAO
DSSI
-DIAl

DSSI
-DIA2
DSSI

=DIA3

Node

(772150)

-rf(0,0,%)
Node

(760334)

-rf£(1,1,*)

Neode

(RF71)

(760340)

-xf(2,2,%*)
Node

(RF71)

(760344)

~-rf£(3,3,*)

(RF71)

DSSI

Nede

(760350)

DSSI

Rode

(760354)

=DIAS
DSSI

-x£(5,5,*)
Node

(%)

UQSSP

Tape

-MUAO

-tm{0,0)

Ethernet

(RF71)

Controller

(774500)

(TK70)

Adapter
-mop()

(774440)

=ESA0

-gse

(08-00-2B-0C-C4-75)

C-12

KN210 CPU Module Set System Maintenance

C.4 Reprogramming the KFQSA
When you add a new DSSI device to a system with at least one RF-series
ISE that has been programmed correctly, you must reprogram each KFQSA
on the DSSI bus to include the new device(s) as follows:
L

Enter maintenance mode, using the procedure in Section C.2.1.

At the maintenance mode prompt, type siow DEVICE for a display of all
devices currently in the system. The display includes tape drives and
the Ethernet adapter, as shown in Section C.3, Example C-7.
This display lists the Q-bus address and port name of the device, such
as DUAO RF71.
Type show oBUs for a display of the eight-digit Q-bus address (hex) for
each device, as shown in Section C.3, Example C-6.
Find the eight-digit Q-bus address for an ISE attached to the KFQSA

that you are reprogramming. Use the SET HOST command to enter
the KFQSA through an existing port and edit the configuration table
as follows. Refer to Example C-8.
a.

Type seT HOsT/UQsspP/MAINT followed by the Q-bus address.

Use the SET and CLEAR commands to reconfigure the KFQSA, as
shown in Example C-8.

Type sHow to display the new KFQSA configuration table setting.

Type EXIT to save the configuration table or QUIT to cancel the
reprogramming.

Configuring the KFQSA

C-13

Example C-8:
>>>

Reprogramming the KFQSA Display

SET HOST/UQSSP/MAINT 20001468

UQSSP

Contreller

(772150)

Node

CSR Address

772150

760334

760340

760344

760350

760354

eeee- KFQSA

CLEAR

SHOW

Model

21
~coce-

Rede

CSR Address

Model

772150

760334

760340

760344

760350

cwco= KFQSA

SET

SHOW

760354

21
ecwmcw-

Node

CSR Address

Model

772150

i
2

760334
760340

21
21

760344

760350

760354

esece

KFQSA

21
-cwec=-

EXIT

Programming the KFQSA...

!'Note
'KFQSA

C-14

from the system that the
is being programmed.

KN210 CPU Module Set System Maintenance

C.5 Changing the ISE Unit Number
This section describes how to change the ISE unit number. For most
configurations, you will not need to change the default unit numbers.
NOTE: Ifyou add a new device to the system, you must rebuild the JJLTRIX32 kernel to include the device.

Change the unit number, using the console-based DUP driver utility, as

follows. Refer to Example C-9.

Enter maintenance mode, using the procedure in Section C.2.1.

At the maintenance mode prompt, type SET HOST/DUP/UQSSPE/DISK 0
pARAMS (0 through 6 for the ISE to which you want to connect) to start
the DUP server.

Type sHow UNITNUM to check the unit number.
To change the ISE's unit number from the default value, type SET
UNITNUM n (where n is the new unit number). For example, type SET
UNITNUM 20 to change the unit number from 0 to 20.

Type SET FORCEUNI 0 to set the forceunit flag to zero in order to use a
nondefault value. If you do not change the FORCEUNI parameter, the

drive unit number defaults to the number of the corresponding DSSI
plug on the operator control panel (OCP).

Type SHOW UNITNUM to show the new unit number.

Type sHOW FORCEUNI to show the new forceunit flag values.

Type WRITE, then type Y to save the new values into the EEROM or
to cancel the reprogramming.

Type sHOw DEVICE to make sure you have programmed the first ISE to
have a unit number of 20. When you boot the operating system, the
display shows the new unit number.

Configuring the KFQSA

C-15

Example C-8:

Digplay for Changing Unit Numbsr

>>> SET HOST/DUP/UQSSP/DISK O PARAMS
Starting JUP

UQSSP

server...

Disk Controllexr

(c)

1988

(772150)

Digital Equipment

Corporation

SHOW UNITNUM

Parameter

Current

PARAMS>

SET UNITNOM 20

PARAMS>

SET FORCEUNI

PARAMS>

SHOW UNITNUM

Parametexr

PARAMS>

Default

Type

Radix

Default

Type

Radix

Default

Type

Radix

Boolean

0/1

Current

SHOW FORCEUNI

Farameter

Current

FORCEUNI

PARAMS> WRITE
Stopping DUP
>>>

server...

SHOW DEVICE

DSSI

Node 0

-DIA20
DSSI
-DIAl
DSSI
-DIA2

DSSI

=-DIA3

Hode

Wode 2

DSSI
=DIAS

(RF71)

(760354)

-z£(5,5,%)

DSSI Node

(RF71)

(760350)

~-rf(4,4,*)
5

(RF71)

(760344)

-rf£(3,3,%)

Hode

(RF71)

(760340)

-rf(2,2,*)

Node

(RF71)

(760334)

-rf(1,1,*)

DSSI Nede 4
-DIR4

(772150)

-xr£(0,20,%*)

(RF71)

(v¥)

lo C-9 Cont'd on next pag
e

C-16

Kn210 CPU Module Set System Maintenance

Example C-0 (Coni):

Display for Changing Unit Number

UQSSP Tape Controller
-MOA0

=tm(0,0)

(774500)

(TK7D)

Ethernet Adapter

~ESA0

(08-00-2B-0C~C4-75)

-se -mop()

(774440)

Configuring the KFOSA

C~17

Appendix D

Field Replaceable Units (FRUS)
This appendix lists the major field replaceable units (FRUs) for the KN210based system (DECsystem 5400).
FRU Description

Part Number

EN210 Base Sysiem
H3602-AB bulkhead assambly
KN210 CPU module
KN210 VO module
MS650-BA memory module, 16 Mbyte

70-25776-02
M7635-AA
M7636-AA
M7622-AA

Digital Storage System Interconnect (DSSI)
DSSI cable, external
DSSI cable, round

17-02152-03
17-02058-01

DSSI daisy-chain eable, flat

17-01836-01

DSSI operator control pansl (OCP)

70-25752-01

DSSI tarminator

12-29258-01

KFQSA module

M7768-00

RFF30/71 drive bracket

70-36498-01

RF71 drive module

54-18316-01

RF71 head disk agaembly (HDA)

70-23557-01

RF71 integrated storage alement (ISE)

RF71-EA

RF71 shock mount, bottom

70-25452-03

RF71 shock assembly, top

70-25452-04

RF-geries lens, encoder eat

12-28766-19

Field Replaceable Units (FRUs)

D-1

FRU Deseription

Part Number

Digital Btorage Architecture (DSA)
RA70 slectronic control module (ECM)
RA70 head diek assembly (HDA)
RA70 operator control panel (OCP)
RA7(/KDAB0 gignal cable
RAS0 electromic control module (ECM)
RAS0 head disk assembly (HDA)
Ré-geriee drive brackat, top
RA-garies drive brackst, bottom
RA-series drive cable, 4-pin
RA-aorien drive cable, 20-pin
RA-egriea drive shoek mount 1
RA-ssries drive check mount 2
8SDI cable, external

70-22484-01
70-21846-01
64-17232-02
17-06251-03
70-22842-02
70-229851-01
70-24558-01
70-24559-02
17-015603-01
17-00847-06
70-28997-06
70-23997-06
17-00464-12

Cables, Base System

Backplane to operator control panel (OCP) cable
KN210 CPU module to KN210 IO module
Memory cable
Memory cable
Memory cable
TK-serica tape drive power eable
H38602-AB cable

17-01864-01
17-02418-01
17-01888-01
17-01898-02
17-01888-03
17-01837-01
17-02430-01

Option Modules

CXA16-M module

M3118-YA

CXB16-k module
CXY08-M module
DEQNA-SA module
DELQA-SA module
DESQA-SA module
DPV11-8A medule
KDA50 medules

M3118-YB
M3118-YA
M7504-PA
M7516-PA
M3127-PA
M8086-PA
716400

KLESI-SA controller module
Load madule
LPV11-8A module
TQK70 controller module

M7740-PA

D-2

R7165-00

248060-YA
bM8086-PA
M7559-00

KN210 CPU Module Set System Mainianance

FRU Description

Part Number

BA213 Enclosure
Batiery pack

12-1924¢5-01

Blank labels

86-26883-01

Backplane, eplit bus DC

70-23712-01

Bulkhead cover, ngle

70-23981-01

Bulkhead cover, dual

70-23882-02

CD filler panel

74~-33507-01

Fan amembly

70-23988-01

Fan, +12 Vde

12-23608-04

FCC cip/handles

12-28340-01

Pilter ingut agaembly

70-23768-01

EOS clip

12~-28822-01

Mess siorage power harnees, left

17-01888-01

Mags storege power hernsss, right

17-01€80-01

One quarter-tuvn fastensr/handle

12-28848-01

Power mupply, 120 Vac

H7868-A

Power supply, 240 Vec

H7888-B

Side gep filler panel (2)

70-24505-01

Swiich aseembly

70-23988-01

Miscellaneous
BA213 chassis assemhly, 120 Vac

70-24227-03

BA213 chasms assermbly, 240 Vac

70-24227-04

Contrel power ewitch 886-A

30-30166-01

Control power ewitch 886-B

30-30166-02

Power controlier, 120 Vee

00-874-D

Power controller, 240 Vaz

G0-874-F

Power control cable, 3-pin

70-08288--06

Loopback Conneetore
CXY08 loopback

122688401

DEQNA Etharnet loopbach

12-22186-02

H3108-00 (MIMJ) loopback

12-25083-01

H3187-00 CXY08 loopback

12--15336-07

Field Replacsable Units (FRUs)

D-3

Appendix E