Digital PDFs

EK-DS725-UG-001

2000

90 pages

Original

5.2MB

view download

OCR Version

3.8MB

view download

Document:	VAX-11/725 Diagnostic System Overview Manual
Order Number:	EK-DS725-UG
Revision:	001
Pages:	90
Original Filename:

OCR Text

VAX-11/725
Diagnostic System
Overview Manual

dlilgliltiall

EK-DS725-UG-001

- VAX-11/725
Diagnostic System
Overview Manudl

Digital Equipment Corporation

1st Edition, February 1984

The information in this document is subject to change without notice and should not be
construed as a commitment by Digital Equipment Corporation. Digital Equipment
Corporation assumes no responsibility for any errors that may appear in this document.

Printed in U.S.A.

This document was set on a DIGITAL DECset Integrated Publishing System.

The following are trademarks of Digital Equipment Corporation:

dlilgli[t[a]!

DIBOL

DECwriter

Rainbow

RSTS

KMC

RSX

DECmate
DECset

KMS
MASSBUS

VAX

DECsystem-10

PDP

VMS

DECSYSTEM-20

P/OS

DECUS

Professional

Work Processor

DEC

UNIBUS

CONTENTS

Page

INTRODUCTION
W
N —

et e et e e te s e s et sasnsaeneeaneeens 1-1
ttt
ettt
MANUAL SCOPE ...
VAX-11/725 DIAGNOSTIC SYSTEM STRUCTURE...........cccccoovii, 1-2

ee e e et s arie s st s saen s saasennaenes 1-4
etttt
DIAGNOSTIC STRATEGY ..o
i, 1-4
VAX-11/725 REMOTE DIAGNOSIS OPTION......ccccccoiiim

CONSOLE SUBSYSTEM
2.1

2.2
2.2.1

2.2.2
2.2.3
2.3
2.4
2.5

2.5.1
2.5.2
2.5.3

2.5.4
2.5.5

2.5.6

2.5.7
2.5.8

2.5.9
2.5.10
2.5.11
2.5.12
2.5.13

N —

W N —

INT RODU CTION Lottt
e et e e et tee e st teeraaeesttaeessnasatesrannsasanseerennnnns 3-1
COLD START (BOOT).....oeteiuiiiiieeeeeisiessese
s sssseeseeseesssesessesesassssassssssenes 3-1
Console Subsystem Action on a Cold Start ........ccccooovviiiiiiiii, 3-1
VMB.EXE OPeration .........cccccvvieeeeiiiriiieiiieeeeniiiiiniieeee
e 3-6
SYSBOOT.EXE Operation .........ccceevvivierimiiiiiiiiieiiieeeeiieneeceneene
s 3-6
DIAGBOOT.EXE OpPeration ........ccccccvveeeeeereerierensieiieenierererrenierreneesennens 3-6
WARM START (RESTART) ..ottt
eeeeeeneveaaes 3-6
Restart Parameter Block (RPB) ..o 3-8
RiESTATT R OULIIC . oottt
ettt et e e ee e eraesternesnassnesaessnaranssnsanneennss 3-8

W W WNNNNDNN
-

COLD AND WARM START FUNCTIONS

WL LW W W WL W

2.5.14
2.5.15

N T R O DU CT T ION oot
e e e et e et e e s esataeraaasatasraaaaaaasaansaannnsrens 2-1
FRONT PANEL CONTROLS AND INDICATORS ..., 2-3
Six-Position Keylock SWitCh ......cooooiiiiiiiiiiii, 2-3
AUTO/RESTART SWitCh....uvviiiiiiiiiieeeeeeceeceiiiie
e 2-3
e, 2-4
State Indicator Lights.........oooiiiiiiiiiiiiiiee
POWE
R -UP SELF-TEST ..ottt
ettt et e saeeatesraeraaesaaesaesnsenenanns 2-4
CONSOLE MODIES ... oottt
et e er e e s ae e e st e s e esnaesaseserassaaaneaernannes 2-7
CONSOLE COMMAND LANGUAGE ...t 2-9
(0001180 IO 170 v (61 15) s UTUTRTUU T
U TRUP PO 2-9
st ertessraesataeasteeeanesarneaannsaennnnns 2-10
eer e eee e rte ettt
BOOT COMMANG ...
CONTINUE COMMEANG ...oiiniiieeee et
erie e e raeesseeeneesnnaenanns 2-10
DIRECTORY COMMANG ...ovniinniiiiieei ettt eeteesessesaessessiessnneees 2-10
EXAMINE and DEPOSIT Commands .........oovvuviiiiiiiiiiiiniiiiieeiieeereeeieeeeenenen 2-11
HALT COMMANG ...iiniiiiieie ettt teeetee e eteeeseesenesanesasaaasansassnsannnnsns 2-13
INAIreCt COMMANG ...ooeeeieeiee ettt
e e et e e aeeesesan e st seanesasnseennenes 2-13
INITIALIZE COMMANA ....ooniinieeeeieeeiieeeee
et teiee i eraeesresaeraasstassnesannsasnsennes 2-13
LOAD COMMANG....oiiiiiiniiiee
ettt e etee et et ertteeesteesnaesstnsasnaarnnsaarsserennnns 2-14
MICROSTEP COmMMANG.....covneeieiiiiiiiieiiiee
et eerieeere e st e eaneeeaiesaanaaeannaes 2-14
NEXT COMMANG.. ..ottt ettt teee e eirereeetteersesterneessaessaesrnssneesanesenes 2-15
REPEAT COMMANA ....ooniiiniieeeeeeeeeeeie
et eeieeeeteeereessteesnnessteessneesnnssasseennnns 2-16
START COMMANG....o.iiiiiieiie ettt
et etee et eresenessaeesasssaesseseaassnseees 2-16
TEST COmMMAnd ....oooniiiieeeie ettt et eeetrere e st erreessssnesneesnnasnes e 2-17
W AT COMMANA ..ottt
et e e e et esbeetnersnesanersneasnsarasannnnns 2-17

CONTENTS (Cont)

Page

MICRODIAGNOSTICS

INTRODUCGTION ..ottt e 4-1
LOADING THE MICMON ... .ot 4-2
MICRODIAGNOSTIC MONITOR COMMANDS .............. e ———— 4-5
MICRODIAGNOSTIC ERRORS. ... 4-5

4.1
4.2

4.3

VAX-11/725 DIAGNOSTIC SUPERVISOR AND LOAD PATH

B wo—

INTRODUCGCTION ..ot 5-1

LOADING THE SUPERVISOR THROUGH THE PRIMARY LOAD PATH... 5-1
Loading the Supervisor Off-Line from the Diagnostic Distribution Disk......... 5-1
Loading the Diagnostic Supervisor Off-Line from the System Disk ................ 5-2
Loading the Supervisor On-Line from the Distribution Disk.............ccc..oveeie.. 5-3
Loading the Supervisor On-Line from the System Disk ..............ccccccoooeeiini
. 5-4
LOADING THE DIAGNOSTIC SUPERVISOR THROUGH THE
SECONDARY LOAD PATH ..., 5-4
Executing Diagnostics for the Load Path...............c.oooo 5-5
DIAGNOSTIC SUPERVISOR COMMANDS ... .o 5-6

LOADING AND EXECUTING THE LEVEL 4 DIAGNOSTIC PROGRAM ... 6-1

m—t ot

W b —

SARSASANSAICA

EXECUTING THE LEVEL 4 DIAGNOSTIC PROGRAM

Loading EVKAA from the TUS8 Tape Cartridge ..........ccovvvvviiiieeeeeiiriiiiiinnn, 6-1
Loading and Executing EVKAA from the Disk Pack..............ccccccooeeiiiinnn. 6-2
Executing EVIKAA oo
e
e e e 6-2
EVKAA ERROR INTERPRETATION AND LOOP CONTROL...................... 6-2

—
w

W
H WL

—

CUSTOMER RUNNABLE DIAGNOSTICS

7.4.2

INTRODUCGCTION ...ttt
e e e e e e 7-1
CRD MINIMUM SYSTEM CONFIGURATION ....ccoooiiiiiiiieee e, 7-1
AUTO MODE.......................e
eeeeee et ———eeeeetet i ——eeeeeet b ———eeeeat—aaaarar—aans 7-2
AUTO Mode EVOCAtION........cuiiiiiiiiiiiiiiiieee
e
e e e 7-3
AUTO MoOAE MESSAZES ......uvneiiiiiie ettt
e et 7-3
AUTO MoOAE EITOTS....ooiniiiiiiiiiee
et e e 7-6
MENU MODKE ... oot
ee e eeeeees 7-6
MENU Mode EvOCation........cccoooiiiiiiiiiiiiiiee
e 7-7
MENU MOAE EITOIS ...t
e 7-13

CONTENTS (Cont)

Page

INTRODUCGTION .ottt
eeee
e e e e e e e 8-1

APPENDIX A

VAX-11/725 INTERNAL PROCESSOR REGISTERS

APPENDIX B

MICRODIAGNOSTIC MONITOR COMMANDS

NN
N -

00 00 90 00

BUILDING AND UPDATING THE SYSTEM DISK DIAGNOSTIC AREA

BUILDING AND UPDATING THE DIAGNOSTIC AREA.........cccoovviieee 8-1
Building and Updating the Diagnostic Area with the COPY Command......... 8-1
Building and Updating the Diagnostic Area with DUCT ...............ooeviiiininnnnnee. 8-2

CHAPTER 1

INTRODUCTION

1.1 MANUAL SCOPE
This manual describes the use of the VAX diagnostic system with the VAX-11/725 computer system. It
covers the following topics:
e

Console commands

Self test

Microdiagnostics

Levels 4 and 3 macrodiagnostics

Diagnostic supervisor

Customer runnable diagnostics

Maintenance disk

This manual serves as a reference for Field Service engineers and as a resource for field service,
manufacturing, and customer training programs. To use this manual, the user should be familiar with
VAX architecture, VAX/VMS software, and VAX-11/725 hardware.
This manual is part of a four-level documentation set, as shown in Figure 1-1.

These four levels of documentation form a progression from general to specific. The general level being the
VAX Diagnostic System User’s Guide and the specific being the Diagnostic Program Listings. To apply
the VAX diagnostic system effectively, the user should become familiar with each documentation level.
The VAX Diagnostic System User’s Guide contains stable information that applies to all VAX computer
systems. It explains the VAX diagnostic system structure and strategy and the various uses of the
diagnostic supervisor. The VAX Diagnostic System User’s Guide is available in hardcopy and microfiche.
This manual, the VAX-11/725 Diagnostic System Overview Manual, is available in hardcopy, microfiche, and ASCII files. The manual may be revised periodically. Revisions will be available on microfiche
and magnetic media and distributed with other diagnostic system microfiche updates.
Program documentation files and program listings are available on microfiche and magnetic media. These
are revised and distributed periodically. The program documentation files give information that helps the
user to effectively use the diagnostic programs.

1-1

VAX DIAGNOSTIC

— PRINTED

SYSTEM USER’S GUIDE

— MICROFICHE

EVNDX

PROCESSOR

SUBSYSTEM

DIAGNOSTIC
PROGRAM

SPECIFIC
OVERVIEW

SPECIFIC
— MICROFICHE
OVERVIEW | — MAGNETIC MEDIA

INDEX

MANUAL

DIAGNOSTIC PROGRAM
DOCUMENTATION FILES

— MAGNETIC MEDIA

DIAGNOSTIC PROGRAM

— MICROFICHE

LISTINGS

— MAGNETIC MEDIA

— MICROFICHE

TK-3424

Figure 1-1

VAX-11 Diagnostic System User Documentation

Digital Equipment Corporation also distributes EVNDX, the VAX Diagnostic Index, on microfiche and
magnetic media. EVNDX enables users to keep up with the periodic changes and additions to the VAX-11

diagnostic system.
Table 1-1 lists related documentation.
1.2

VAX-11/725 DIAGNOSTIC SYSTEM STRUCTURE

The VAX-11 diagnostic structure consists of the following six program levels.
Level 1 - VAX/VMS-based Operating system diagnostic program using logical or virtual queue

1/0, such as:
VAX System Diagnostic (exerciser)
Level 2R - Diagnostic supervisor-based diagnostic programs restricted to running under VMS only

using physical queue 1/0, such as:

Certain peripheral diagnostic programs
Level 2 — Diagnostic supervisor-based diagnostic programs that can be run either under VAX/VMS

(on-line) or in the standalone mode using physical queue I/0O, such as:
Formatter and reliability level peripheral diagnostic programs

1-2

Level 3 - Diagnostic supervisor-based diagnostic programs that can be run in standalone mode only
using physical queue I/0O, such as:
Functional level peripheral diagnostic programs
Repair level peripheral diagnostic programs
CPU cluster diagnostic programs
Level 4 — Standalone macrodiagnostic programs that run without the supervisor, such as:
Hard-core instruction set

Level 5 — Console-based diagnostic programs that can be run in the standalone mode only, such as:
Microdiagnostics
Microdiagnostic monitors
Console diagnostics

Table 1-1

VAX-11/725 Related Documentation

Title

Order Number

VAX-11/725 User’s Guides:
Diagnostic System
DMF32 Multi-Function Communications Interface
Hardware

EK-VX11D-UG

CRD Users

EK-CR725-UG

VAX-11/725 Installation Guide

EK-725CI-IN

DEUNA User Guide
11725 Field Maintenance Print Set
RC25 Disk Subsystem Operation Guide
RC25 Disk Subsystem Installation Guide

EK-DMF32-UG
EK-11730-UG

EK-DEUNA-UG
MP-01728-01

EK-ORC25-OP
EK-ORC25-IN

VAX-11/725 Technical Descriptions:

Central Processor Unit

EK-KA730-TD

Memory System

EK-MS730-TD
EK-PS730-TD
EK-FP730-TD
EK-KC730-TM
EK-BA11-A-TM
EK-DMR11-TM

Power System

FP730 Floating Point Accelerator
KA730 Remote Diagnostics Option
BAIl-A Mounting Box and Power System
DMRI1 Sync Controller
VAX-11 Handbooks:

Architecture
Hardware
Software
VAX-11 Reference Manual

EB-19580
EB-21710
EB-21812
EK-VAXAR-RM

Overlapping four levels (levels 5, 4, 3, and 2) of the diagnostic system structure is the Customer Runnable
Diagnostic (CRD). CRD is a special program which simplifies the execution of these diagnostics with a
single command. Refer to Chapter 7 for further information on CRD.
Most diagnostic programs that test peripheral devices are not processor-specific. They run on the VAX11/725 processor as well as on other VAX processors. These programs are called transportable diagnostics. They are identified by the letter V as the second character of the five-character program (for
example, EVREA).
Of the diagnostic programs that test a VAX-11/725 system, some are transportable and some are
processor-specific. VAX-11/725 processor-specific diagnostic programs are identified by the letter N as
the second character of the five-character program code (for example, ENSAA).
See the VAX Diagnostic Index, EVNDX, for a complete list of VAX diagnostic programs. Refer to the
appropriate program documentation file to answer questions concerning the use of any specific diagnostic
program.

The VAX-11/725 diagnostic system provides flexibility concerning the load paths and execution control
of different program levels. For example, the diagnostic supervisor and level 2 and level 3 programs can be
loaded from either the console load media (TUS8 tape drive) or from the system disk. If the primary mass
storage load path does not work properly, the TUS8 can load diagnostic programs, which help to repair the
load path problem. (Refer to Chapter 5.) Although level 2 programs are flexible and run in the user mode
or in the standalone mode, levels 2R, 3, and 4 programs are less flexible.
1.3

DIAGNOSTIC STRATEGY

CRD forms the basis of the DIGITAL strategy for VAX-11/725 system maintenance.

The SYE utility can be used to generate an error log report. Analyze this report to isolate the problem to a
failing subsystem or option. Further testing can be done using on-line diagnostics (levels 2 and 2R) for
fault isolation. If the system is off-line, CRD can be used to identify the failing subsystem or option.
Individual microdiagnostics and level 3 macrodiagnostics then can be used to isolate to a fleld replaceable
unit.
Implementation of a specific diagnostic strategy is area-dependent (US, GIA, EUROPE).

1.4

VAX-11/725 REMOTE DIAGNOSIS OPTION

The Remote Diagnosis Option (KC730) is installed in the VAX-11/725 system to allow an operator at a

remote terminal (at a remote support center) to perform the same operations as the local operator at the
system console terminal. These operations include booting the operating system, controlling the system and

communicating with the user programs, and loading and running the diagnostics. These operations are
enabled only when the local operator sets the VAX-11/725 keyswitch to the REMOTE or REMOTE
DISABLE position.
The local DIGITAL Field Service representative initiates any request for remote support customer site
personnel are not involvedin this procedure.

NOTE

Normal system operation for the VAX-11/725 system is not affected by the installation of the KC730
Remote Diagnostic option.

1-4

CHAPTER 2

CONSOLE SUBSYSTEM

2.1
INTRODUCTION
The VAX-11/725 console subsystem is an important diagnostic tool. It enables the operator to perform

the following functions:
e
®

Starts and stops the CPU instruction set processor
Examines and deposits information in locations in main memory I/O registers, processor

registers, and internal registers
°

Controls CPU execution

The console subsystem hardware consists of a dedicated console terminal, switches and lights on the front
panel of the CPU cabinet, dual integral TUSS8 tape cartridge drives, and remote access port.

The VAX-11/725 console runs in two modes: the program and console I/O modes. These modes are
mutually exclusive. One of these modes is always enabled while power is applied to the system.
In the program I/O mode, the console terminal functions like a user terminal on the VAX-11/725 system.
It passes characters between itself and the program running in the CPU.

In the console mode, the CPU is in the idle loop and réceptive to console commands.
The CPU enters the console I/O mode when the front panel keyswitch is set to either the LOCAL or
REMOTE position and one of the following occurs:
®

Power is cycled with the AUTO RESTART switch in the OFF position.

Power is cycled with the AUTO RESTART switch in the ON position, if the restart attempt

fails.
®

Power is cycled with the AUTO RESTART switch in the ON position, if the cold start fails.

Power is cycled with the AUTO RESTART switch in the ON position, if both the warm and

the cold start attempts fail.
®

A boot, continue, or start console command fails.

The operator types CTRL/P on the console terminal.

The instruction set processor executes
HALT codes and their meanings.)

a HALT MACRO-32 instruction. (See Table 2-1 for

Table 2-1

CPU Halt Codes and Halt Conditions

Code

Halt Conditions

Halt command - given by the operator while the processor is in the Console mode.

Self-test was successful.

CPU Halt - operator typed CTRL/P while the machine was in the Program mode.

Typed by the console on a power fail restart. Does not appear in the halt message.

Invalid interrupt stack (IS) or unable to read system control block (SCB).

CPU double error. A second machine check occurred before a previous one could be
reported.

CPU Halt - CPU executed a halt instruction in the kernel mode.

Invalid system control block (SCB) vector (bits <01:00> of the SCB vector =3).

No user WCS - SCB vector bits <01:00> = 2 with no user WCS installed.

Error Pending on HALT - processor was halted by a CTRL/P before an error halt could be
performed.

Change Mode from internal stack instruction was executed when the PSL <IS> bit was set.

Change Mode to interrupt stack instruction was executed when the exception vector for a
change mode had bit <0> set.

0C |

SCB Read Error - uncorrectable memory error occurred when CPU tried to read an
exception of interrupt vector.

When the CPU enters the console mode, it prints on the console terminal:

A question mark followed by a two-digit halt code (Table 2-1).
The address contained in the program counter (PC).
The console prompt symbol, >>>.
For example:

"P
702
>>>

PC=nnnnnnnn

!
!

CTRL/P typed at the console terminal
Halt code followed by the PC address

Console

prompt

2-2

2.2 FRONT PANEL CONTROLS AND INDICATORS
The front panel of the VAX-11/725 system has two switches and four indicator lights. These switches,
indicator lights, and their functions are identified below.
2.2.1

Six-Position Keylock Switch

The six positions of keylock switch and the functions of each are shown in Table 2-2.

Table 2-2

Functions of the Six-Position Keylock Switch

Position

Function

OFF

No power is applied to the CPU or to memory.

STD BY

Power is applied to main memory, the WCS module and to the TUS8 tape
drives.

LOCAL

Power is applied to the CPU and to memory allowing the CPU to respond to
~ console commands. The remote access port is disabled.

LOCAL/DISABLE

The CPU does not respond to console commands, however the console terminal
functions as a user terminal. The remote access port is disabled. The BOOT
position of the AUTO RESTART switch is ignored.

REMOTE/DISABLE

The console terminal is disabled. The remote access port is enabled, allowing a
terminal connected to it to be used as a user terminal. The CPU does not
respond to console commands from this remote terminal.

REMOTE

The remote terminal functions as the console terminal. The console terminal is
disabled unless enabled by the remote terminal.

2.2.2 AUTO/RESTART Switch
This three-position switch controls the machine in a power-up sequence, power restoration and software
crash. The three positions of the AUTO/RESTART switch and the functions of each are shown in Table
2-3.

2-3

Table 2-3

The Functions of the Three-Position AUTO/RESTART Switch

Position

Function

OFF

The system halts and prints the console prompt “>>>"" after loading the micro-

code or executing a HALT instruction.
ON

The system loads the microcode and bootstraps the system disk using the bootstrap command procedure (DEFBOO.CMD) automatically, if one of the following conditions occur:
o

During initial power up

After a brief power failure

After the CPU microcode detects an error condition (HALT instruction is

executed in the kernel mode)
BOOT

This momentary contact position reboots the system (using DEFBOO.CMD)
when the system is in the console mode (>>> is displayed on the console

terminal).

2.2.3 State Indicator Lights
The functions of the state indicator lights on the front panel are shown in Table 2-4.

Table 2-4

Front Panel State Indicator Lights

Light

Function

RUN

The processor CPU is executing instructions.

DC ON

The dc voltages are applied to the system.

R/D

Remote diagnostics procedures are being performed on the system.

2.3 POWER-UP SELF-TEST
On initial powerup, the VAX-11/725 console subsystem goes through a sequence of events that is shown
in Figure 2-1. If the self-enable switch (SW1) on E47 of the WCS module (M8394, slot 3) is OFF (high),

the console microprocessor performs a test of the +15 V and —15 V power and the PROM resident selftest. If SW1 is ON (low), the PROM resident self-test is bypassed.

2-4

CPOWE R-UP)
FROM MICMON

0’S ~ 8085A PC

(RETURN)

TRY TO READ BOOT
(DD1 1S CURRENT

{

VES

LOAD

BLOCK FROM DD1

(START PROG)

CONSOL.EXE

DRIVE)

DISABLE 8085A
INTERRUPTS

NEGATE CPU RUN

ASSERT UNIBUS:

CHANGE

CURRENT DRIVE

YES

AC LO, DC LO,

CINIT, BBSY
LOAD
TRY TO READ BOOT

CONSOL.EXE

BLOCK FROM DDO
(DDO IS CURRENT

DRIVE)

+15V OK

“VERSION XX.NN*

YES

LOAD BOOT BLOCK

j\\\\\\\

FROM CURRENT

TO CONSOLE

SUCCESS

/0 MODE
LOAD

DRIVE TO RAM

ENKAA.EXE

Y ES

(MICMON)

4100-4BFF

SELF TEST
ROM CHKSUM,
USARTS, RAM (LOOP
ON ERROR. POWER
DOWN/UP TO RELEASE).
"CONVxxx'

CHANGE

CURRENT DRIVE
RAM

4100
= C3
PRINT ROM PROMPT

(ROM>)

LOAD
ENKAA.EXE

(MICMON)

YES

INITIALIZE

SET UP PROG FLAGS,
USARTS, AND STACK
POINTER.

CONTROLC

EXECUTE

“MIC>"

UNIBUS POWER-UP

SEQUENCE. ENABLE

MICRODIAGNOSTIC

8085A INTERRUPTS

MONITOR

TK-7989

Figure 2-1

Power-Up Sequence of Events

2-35

During the self-test the word “CONVxyz” is printed on the console terminal. The “xyz” designation will
vary according to the version of the console program. Each letter and digit of this word is a series of
subtest completion flags. One letter or digit of the word “CONVxyz” is printed between each subtest and

the last two digits are printed at the end of the test (Example 2-1). The self-test sequence is as follows:

<LF><CR>"(C"

;

Start

"O"

;

PROM

"N"

;

USARTs

Loopback

"V"

;

USARTs

Dual

"x"

;

RAM

Float

"yz"

;

RAM

March

Test

CCNVxyz

(1)

VERSICN

xx.nn

(2)

>>>a2POWER.CMD

(3)

>>>L/C

Self-Test

CHECKSUM

CONSLE.CFU

(power-up)

Test
Test

Address

Test

>>>L/C/S:0800

'VERSION

MMIE.CPU

>>>L/C/S:0E00

'!VERSION

vyy

POWER.CPU

(3b)

'VERSION

(3c)

>>>S/C
>>>W

(3d)

(3a)

(3e)

>>>a8CODECO.CMD

(4)

>>>L/C/S:0EQ0

FP.CPU

>>>L/C/S:1A00

IVERSION

BITFLD.CPU

>>>L/C/S:1D00

CM.CPU

!VERSION

vyy

(4b)

>>>L/C/S:3300

!VERSION

BASIC.CPU

(4c)

>>>L/C/S:4BC0

QUEUE.CPU

>>>1

(5)

>>>

(6)

Example 2-1

(4a)

'!VERSION

(4¢)

JWERSION

(4e)

Printout Produced by the Console Terminal as the CPU Enters the Console 1/0 Mode

NOTE
The console message and the subtests performed
may change as later versions of the program microcode are released.

If an error is detected while checking the 15 V power, or during a subtest, the console microprocessor loops
on that failing subtest. The two RAM subtests have a failing subtest error message. The other subtests do
not print a failure message.

2-6

The PROM resident self-test 1s as follows:

PROM CHECKSUM Test - The PROM code is verified by calculating_a checksum on the

USARTSs Loopback Test — The three USARTs are verified by sending out data and reading it
back via a wraparound function in the USARTs.

USARTs Dual Address Test — The three USARTSs address response is verified by writing
different data to each USART command register, then reading the data back. This ensures that
each USART responds only to.its unique address and no other address.

RAM Float 1 Test - The RAM data test checks the RAM data lines, the first location of RAM
(4000 hex) is read/write tested with a pattern of ones (1) floating through a field of zeros (0).

PROM and comparing it to a known checksum stored in the last location of the PROM.

Failing Test Printout:
Expected
XXXXXXXX

Received

XXXXXXXX

RAM March Test - The RAM march test writes a background of Os, then marches a 1 through
it. This leaves a background of ls through which a 0 is marched. This subtest has a delay
inserted in it so that the RAM refresh hardware is also tested.
Failing Test Printout:
Expected

Received

XXXXXXXX

2.4 CONSOLE MODES
Immediately following the completion of the self-test, the CPU enters one of three modes depending upon
whether a tape cartridge is inserted into a TUS8 tape drive unit and whether that tape contains the console
or microdiagnostic files. The mode entered is indicated by the console terminal. It prints either the ROM
idle loop prompt (ROM>), the console I/O mode prompt (>>>), or the micromonitor mode prompt
(MIC>).
If no tape cartridge is inserted into either tape drive unit, the CPU enters the ROM idle loop mode and the
console terminal prints the ROM> prompt. The console subsystem stays in ROM idle mode until a
CTRL/C is typed. When CTRL/C is typed, the console subsystem performs the self-test again and then

looks for a tape cartridge in one of the drives.
If the console file (CONSOL.EXE) is found on the tape cartridge inserted into a tape drive unit, the
console terminal produces a printout similar to Example 2-1 and the CPU enters the console I/O mode.

The steps indicated in Example 2-1 are outlined below:
1.

These are console self-test flags.

This is the console program release version.

The boot block instructions are executed by the console microprocessor. They load the file
CONSOL.EXE from the console tape cartridge in the TUS8 drive unit into the CPU writable
control store (WCS). The console prompt (>=>>) is printed. The indirect command file POWER.CMD is accessed on the cartridge. The commands within this file are performed.

2-7

[Load the basic console microcode from the file CONSLE.CPU into the CPU WCS
starting at microaddress O.
Load the memory management, interrupts, and exceptions microcode from the file
MMIE.CPU into the CPU WCS starting at microaddress 0800 (hex).
Load the initializing microcode from the file POWER.CPU into the CPU WCS starting
at microaddress OEOO (hex).

Start the CPU microcode running at microaddress OB (hex). This microcode jumps to the
INIT sequence at microaddress O EOQO (hex). The CPU is initialized, the first 64K bytes
of good main memory is found, and the presence of the internal disk controller (IDC) and
the floating-point accelerator (FPA) is noted.
C.

The console microprocessor waits for the CPU initialization sequence to be completed.

The indirect command file CODEO1.CMD is accessed on the cartridge. The commands within
this file are now performed.

These commands load the microcode from the files on the cartridge into CPU WCS starting at
the addresses shown below:

Step

File Name

CPU WCS Address (hex)

4a
4b
4c
4d
4e
4f

FP.CPU
BITFLD.CPU
CM.CPU
BASIC.CPU
QUEUE.CPU
IDC.CPU

OEO00
1A00
1D00
2200
3B00
4000

The indirect command file CODEO1.CMD is one of four possible command files that can load
selected microcode into the CPU WCS. The file used depends on the presence of the FPA and
the IDC. (The IDC is not used in the VAX-11/725 system.) This presence is determined by a
value passed to the console microprocessor from the execution of the microcode at OEOO
(POWER.CPU). The values passed to the console microprocessor to indicate which command
file is used are shown below.
Value Returned
File Used

FPA

IDC

CODE00.CMD
CODEOL.CMD

0
0

0
1*

CODE(02.CMD
CODEO03.CMD

1
|

0
1

*1 indicates presence
5.

The CPU i1s initialized to a known state.

The console prompt is printed. The console subsystem is now ready to perform any console
command.

If the CONSOLE file is not found and the microdiagnostic file (ENSAA.EXE) is found on the tape
cartridge inserted into a tape drive unit, the CPU enters the microdiagnostic monitor mode (see Chapter
4), and the console terminal prints the MIC> prompt.
2.5

CONSOLE COMMAND LANGUAGE

When the CPU is not executing instructions, it is in the console I/O mode idle loop. In this mode, the CPU

is receptive to console commands. These commands enable the user to communicate with the VAX11/725 firmware from the console terminal. A console command is specified either as a control character
(CTRL/C) or as a single letter or word with optional modifiers.

This section covers commands that are VAX-11/725 processor-specific.
2.5.1

Control Characters

Table 2-5 lists the control characters and their functions for the console I/O mode.

Table 2-5

Control Characters for the Console /0 Mode

Control Character

Function

CTRL/P (program I/O mode)

Aborts the current command, prints halt message, and returns
the console to the console I/O mode idle loop
The console prints:

P
202PC=nnnnnnnnn
>>>

ICTRL/P.
'Halt message.
~!Console

idle

!loop.

Aborts the current operation and returns the console to the

CTRL/C

console I/0 mode idle loop

Same as CTRL/C

CTRL/P (console 1/O mode)

CTRL/U

Aborts acceptance of the current input line; instructs the con-

sole program to return to the idle loop and reissue the console
prompt

CTRL/S

Stops the terminal from printing the current output; only con-

CTRL/Q

Resumes printing on the teminal after CTRL/S is issued

CTRL/O

Enables and disables the console printout

trol characters are recognized while in this state

2-9

2.5.2
BOOT Command
The BOOT command is:

B[<space><TUS58-select>][<space><device-name>k <CR>
This command loads and executes a bootstrap command file from a drive device (TUS8).

>>>B

2.5.3

DUOD

Loads

the

and

executes

default

Loads

the

and

tape

executes

default

tape

DEFBCC.CMD

from

drive.
DUCBOO.CMD

from

drive.

CONTINUE Command

The CONTINUE command is:

C<CR>

If the CPU clock is running, the C@NTINUE command restarts execution of a halted program at the
address currently in the PC.
If the CPU clock is not running because of a microcode break point or the CPU is in the microstep mode,
the CONTINUE command restarts the clock and the console remains in the console I/O mode.
2.5.4

DIRECTORY Command

The DIRECTORY command is:
DIR<CR>

This command prints the directory of tape cartridge that is either inserted into the default TUS8 tape
drive or inserted into a specified TUS8 tape drive, as shown below:

>>>DIR
>>>DIR

DDn:

Prints the directory of the tabe

inserted

Prints

!
!

inserted
(DDO: or

the

default

directory

in the
DD1:).

TU58
the

specified

drive.
tape

TUS58

drive

NOTE
If only one tape cartridge is inserted, then the DIR
command prints the directory on that tape. Howeyv-

er, if one tape cartridge is inserted into each TU5S8
tape drive, then the DIR command prints the direc-

tory of the tape in the default drive DD1..

2-10

2.5.5 EXAMINE and DEPOSIT Commands
The EXAMINE and DEPOSIT commands are, respectively:

E/[<qualifier>]<space><address><CR> and
D/[<qualifier>]<space><address><space><data><CR>
The EXAMINE AND DEPOSIT commands are explained together because their formats are similar.

Both commands require definition of the address space and size of the operand in addition to the address.
The EXAMINE command reads and the DEPOSIT command writes <data> at the <address> specified.

The address and data lengths used depend upon the qualifier or qualifiers specified with the command. If
no address qualifier is specified, the default is the last used address and data length; following another
EXAMINE or DEPOSIT, the same address as that of the previous command will be used as the default.

If no data length qualifier is used (Table 2-6), the default for a physical or virtual EXAMINE or
DEPOSIT is whatever the data length was in the previous EXAMINE or DEPOSIT.

Table 2-6

Qualifier

EXAMINE and DEPOSIT Qualifiers and Definitions

Definitions

Data Length Qualifers

Byte

Word

Longword

Repetition Qualifiers
/N:<count>

Executes the EXAMINE and DEPOSIT <count>+1 times
(>>>E/P/L/N:3

1000), and examines the 4-hexadecimal

address in physical address space, starting in location 1000
Address Space Qualifiers

Virtual Address: This does not work unless mapping is set up
for the virtual address reference also. Virtual address examines
the display of the translated physical address.

Physical address

Internal Processor Register (IPR)
(Listed in Appendix A)

General Processor Register (GPR)

Machine-Dependent Internal Register

Console Microprocessor (ROM or RAM): A console 1/0
device may be examined using this command (>>>E/U FFaa
where aa is an 1/O device address 00 through FF).

CPU Writable Control Store (WCS)

2-11

Table 2-6

EXAMINE and DEPOSIT Qualifiers and Definitions (Cont)

Qualifier

Definitions

Internal Register Address Specification

PSL or PS

Processor status longword

CPU program counter (GPR F)

SP
Rn

Currently active stack pointer (GPR E)
General purpose register (GPR)

n=0 to F (Hex)

Symbolic Address Specification

Next location

® |

Last location

Previous location

Last data used as address

The <address> information must be either a one-to-eight hexadecimal digit, a register address specification (Table 2-6), or a symbolic address specification (Table 2-6). The initial default is zero; however, the
default is unpredictable when the address space is changed.
Following another virtual or physical EXAMINE or DEPOSIT, the default is the sum of the address from
the last EXAMINE/DEPOSIT plus the data length from the last EXAMINE/DEPOSIT. Typing a plus
sign (+) or minus sign (—) for <address> (for DEPOSIT only) gets this default. Following another IPR or
GPR EXAMINE/DEPOSIT, the default is the sum of the address from the last EXAMINE/DEPOSIT
plus one. Using PSL for the <address> performs a longword reference of the Processor Status Longword,
independent of the address and data length.

The <data> information must be represented by one-to-eight hexadecimal digits.
If more digits than specified by the data length qualifier are supplied, the extra digits to the left are
ignored; if fewer digits are supplied, zeros are appended to the left. Examples of EXAMINE and
DEPOSIT commands are shown below.

>DO>>E %

>>>E

>>>E/G

>>>E/I

>>>E/P

>>>E/V

Examines the
deposited

last location
into.

Examines

the

Examines

GPR

number

<address>.
register

number

Examines

<address>.

Examines

physical

Examines

virtual

2-12

IPR

examined

location.

<address>.

>>>E

PSL

>>>E/P/W

Examines

PSL.

Examines

word

physical

>>>E/U

FF20

Examines

console

>>>E/C

3800

Examines

WCS

>>>E/M

Examines

machine

Deposits

<data> in the

sequential

Deposits

>>>D+

>>>D/G

>>>D/V/W

>>>D

PSL

>>>D/U

>>>D/C

<data>

<data>

5177

3B00

device

20.

3B00.
internal

address.

<data>

into

Deposits

virtual

Deposits

<data>

word

GPR

<address>.

<data>

<address>.

Deposits

microprocessor

Deposits

43FF11

I/0

<address>.

into

5177

PSL.

into

RAM.

43FF11

into

WCS

console

3B00.

2.5.6 HALT Command
The HALT command is:

H<CR>

The HALT command does not halt the CPU. HALT causes the console to print the contents of the PC
when the CPU is already halted (CTRL/P is used to halt the CPU).
2.5.7 Indirect Command
The indirect command is:
@<file specification><CR>

The @ command loads and executes the indirect conimand file specified on the power-up sequence or by
the operator.
2.5.8 INITIALIZE Command
The INITIALIZE command is:
[<CR>

The INITIALIZE command performs the following:
e

[Initializes the TUS8 controller

Initializes the internal machine constants

[Initializes the processor to a known state

(Generates new processor status longword (PSL)

Deposits starting address of first good 64K bytes + 200 to SP

2-13

2.5.9 LOAD Command
The LOAD command is:

L/[<qualifier>]<space><file specification><CR>
The LOAD command reads data from the specified file on the console load device to main memory,
console microprocessor memory, or to the WCS. If no qualifier is given with the command, then physical

main memory is loaded.
LOAD qualifiers are shown in Table 2-7.

Table 2-7

Qualifier

LOAD Qualifiers and Definitions

Definitions

/S:<address>

This start qualifier specifies a starting address for the load. If

this qualifier is not given, then the console starts loading at

address 0.

This qualifier forces physical main memory to be the destination of the load.

This qualifier forces the console microprocessor memory to be
the destination of the load.

This qualifier forces the WCS to be the destination of the load.

Examples of the LOAD command are shown below:
>>>L/P/S:nnnn

DDn:filename

>>>L/P/S:d

!
!

Loads the specified file
physical main memory,

starting

(hex).

address

Loads

data

TU58

drive

memory,

address specified by the
Last data deposited or
examined.

the

nnnn

from

device

starting

default
main
the

2.5.10 MICROSTEP Command
The MICROSTEP command is:

M[<space><count>]<CR>
The MICROSTEP command stops the CPU clock and allows the CPU to execute the number of
microinstructions indicated by <count>. The console then prints the address of the next microinstruction

to be performed, starts the clock and enters the idle loop.

2-14

If <count> is not specified the CPU clock is stopped and one instruction is executed, then the console
enters the space-bar STEP mode. In space-bar STEP mode, the next microinstruction is executed when
the space-bar is depressed. The clock is started and the idle loop is entered by typing <CR>.
NOTE

Stepping through instructions that access the console will not work.
Examples of the MICROSTEP command are shown below.

>>>M

2<CR>

The

console

clock

and

stops

the

executes

CPU

two

micro-

instructions.
UPC=nnnnnnnn
UPC=nnnnnnnn

UPC=nnnnnnnn

>>>

>>>M<KCR>

Address

-Address

instruction.
instruction.

Address of next
Start CPU clock
idle Lloop.

instruction.
and enter

Stop CPU clock, execute
one microinstruction

and

enter

space-bar

Space-bar

depressed.

Execute

address.

<CR>

!
I

Start

CPU

>>>

idle

Lloop.

UPC=nnnnnnnn

<SPACE>

|
UPC=nnnnnnnn

Address

instruction

clock

STEP

mode.

instruction.

and

Llast

enter

>>>

2.5.11
NEXT Command
The NEXT command is:

N[<space><COUNT=>]<CR>
The NEXT command executes the number of macroinstructions indicated by <COUNT>. The console

enters the program I/O mode to perform the instruction, prints the halt code and current contents of the
PC, then returns to the console I/O mode idle loop after the <COUNT=> completes.
If no number is given for the <COUNT=>, one instruction is executed and console enters the space-bar
STEP mode. In space-bar STEP mode, the next microinstruction is executed when the space-bar is
depressed. The console enters the console I1/O mode idle loop from the space-bar STEP mode when a
<CR> is typed.

NOTE
During execution of the NEXT command, interrupts
are blocked.

Examples of the NEXT command are shown below.

>>>N

2<CR>

7nn

PC=nnnnnnnn

!
'
!

Halt

code

and

7nn

PC=nnnnnnnn

Halt

code

and

address.

PC=nnnnnnnn

Halt

code

and

address.

>>>

Enters

>>>N<LKCR>

Executes

and

enter

PC=nnnnnnnn

Halt

code

Space-bar

depressed.

PC=nnnnnnnn

Halt

and

Enters

7nn
<SPACE>

2nn
<CR>

The

console

executes

two

macro-

instructions.

idle

Lloop.

one

code

address.

macroinstruction

space-bar
and

idle

next
next

STEP

mode.

address.
address.

Lloop.

>>>
>>>

2.5.12 REPEAT Command
The REPEAT command is:

R <space><console command><CR>
The REPEAT command causes the console to repeatedly execute the <console command> (either
DEPOSIT, EXAMINE or INITIALIZE) specified until execution is terminated by CTRL/C, CTRL/P
or the BREAK key.
2.5.13 START Command
The START command is:

S[<space><address>]<CR> or S/C<space><address><CR>
The START command starts execution of a program that is loaded into memory (see LOAD command).
The command starts execution of the program that begins at the specified address in the CPU PC. If no
address is given then the data last examined or deposited is used as the CPU PC starting address.
The START command performs the following functions:
1.

Initializes the CPU.

Deposits the specified address into the PC. If no address is specified, then the current value in
the PC is used.

Performs the CONTINUE command to begin program CPU execution.

>>>S

1000<CR>

a<CR>

Starts

address

Uses

examined

2-16

the

program

data

that

begins

(Hex).

1000

last

the

deposited

starting

address.

2.5.14 TEST Command
The TEST command is:
T<qualifier><CR>

The TEST command performs the self-test then loads and starts one of three diagnostic programs from a
console drive device, depending on whether a qualifier is used and, if so, which one. The qualifiers used
are:

-None

Loads and starts the customer-runnable diagnostic AUTO Mode package

(ENSAB.EXE) (See Chapter 7)

Loads and starts the customer-runnable diagnostic MENU Mode package (See

Chapter 7)

Loads and starts the microdiagnostic monitor package (ENKAA.EXE) (See

Chapter 4)

The operating state of the machine is altered whether or not the program is found. If the program is not
found, the console subsystem returns to the console I/O mode to reload itself from the console tape. If the
program is found, the console subsystem loads that program into memory and transfers control to it. For
example:
>>>T

CONVxyz
201

FILE

702

READ

702

READ

NOT

FOUND

Loads

customer

diagnostics.

DD1:ENSAB.EXE

and

start

AUTO

Mode

runnable

The

Performs

AUTO

the

self-test.

file

was

not

found

Mode

CRD

DD1.

CONTINUING
ERROR DDO:
CONTINUING

ERROR DDO:
CONTINUING

(Load

and

files

enter

from

console

CONSOLE

I/0

cartridge

mode

1idle

Loop.)

2.5.15 WAIT Command
The WAIT command is:
W<CR>

The WAIT command is used by the console subsystem to detect the completion of POWER.CPU on a
power-up sequence.

2-17

CHAPTER 3

COLD AND WARM START FUNCTIONS

3.1

INTRODUCTION

Whether the VAX-11/725 console subsystem performs a cold start of the operating system or diagnostic
supervisor, or a warm start of the operating system, is determined by the following conditions:
The setting of the front panel AUTO/RESTART switch during a power-up sequence, power
restoration, or a system HALT

The command typed at the console terminal while the CPU is in the console I/O mode wait
loop

The failure of a warm start

The setting of the AUTO/RESTART switch while the CPU is in the console I/O mode wait
loop

At most, the VAX-11/725 attempts one cold start of the operating system and the diagnostic supervisor,
and one warm start of the operating system.
3.2 COLD START (BOOT)
Cold start or boot refers to loading either the operating system or the diagnostic supervisor and starting it.
Cold start for the VAX-11/725 operating system is initiated by one of the actions listed below:
A power-up sequence with the AUTO/RESTART switch set to ON

Typing the BOOT command while the CPU is in the console I/O mode wait loop
Setting the AUTO/RESTART switch to the momentary contact position of BOOT
Setting the AUTO/RESTART switch to the ON position and executing a HALT instruction
while the CPU is in the kernel mode
Failure of a warm start while the AUTO/RESTART switch is set to the ON position

Cold start for the diagnostic supervisor is initiated by typing the BOOT supervisor command while the
system is in the console I/O mode (Chapter 5).
3.2.1 Console Subsystem Action on a Cold Start
When cold starting either the operating system or the diagnostic supervisor, the console subsystem initiates
the sequence of events shown in Figure 3-1.

3-1

14v1S3y/01Nv
14Vv1S

1QH1Vv012S

3-2

3X3°'10 89VvIA
{

avOn GNVY
1HVv1S

aINVXI NA
1OOavonHNLVNIIILLYSAHOW3W
VLS 1V

13s a102

avon IVH3IN3IO

PIoD1eISJo1YyaylFunerad()wAISAS10aylonsoudel(q10s1a13dng
Sl

SH31S193Y
SH-0Y 8 dS

40OLNIAHOW3W
dS

JZITVILINI
‘ndd4009
avolg5v9

4S30Aav

OV14 13S

J1I0SONSV8IA HOSIAYH3INS o<8N<.s,

INIHd

1O~sAAA~s
I/l1v3AQ0WNm d007

HOLIMS 13S
|s

10 8 ONI1lvHd3d0O <<<,, 8 INS

W3L1SAS

3d0w
;xAAAww

1HVv1S34d/01nv dN-43M0d W34NivdHVYM 1HV30IS 370SNOJ O/1

S3A LA3v4

WH10J3114IS9MASOSN1HI0LLvIH8Md,3d0

XX 0 9X AWI'

0STLI-ML

0Z+8Xv9

aAvNOoV1 IX3°L08SAS

As shown in Figure 3-1, the sequence of events is essentially the same for all actions initiating a cold start.
The sequence of events for each action is outlined in the following paragraphs.

)

Power-Up Cold Start Sequence — A power-up cold start of the operating system causes the
console subsystem to perform the following sequence of events:
Execute the self-test, load the console program (Chapter 2), and check the setting of the
AUTO/RESTART switch. If the switch is set to the OFF position, the CPU enters the
console I/O mode wait loop. However, if the switch is set to the ON position, the console
subsystem prints the message ATTEMPTING SYSTEM BOOT on the console terminal.
Examine the cold start flag. If the flag is set, indicating a cold start has previously been
attempted, the message SYSTEM BOOT FAILED is printed on the console terminal. The
CPU then enters the console I/O mode wait loop. However, if the cold start flag is not set,
indicating that a cold start has not been attempted, the console subsystem sets the cold
start flag.

Execute the indirect command file (XXXBOO.CMD) associated with the type of cold
start to be performed. This file executes the functions necessary to cold start the operating
system.

(2)

Warms Start Failure Cold Start Sequence — The failure of a warm start causes the console
subsystem to perform the following sequence of events:

Check the setting of the AUTO/RESTART switch. If the switch is set to the OFF
position, the console I/O mode wait loop is entered. However, if the switch is set to the ON
position the console subsystem prints the message ATTEMPTING SYSTEM BOOT on
the console terminal.
Examine the cold start flag. If the flag is set, indicating a cold start has previously been
attempted, the message SYSTEM BOOT FAILED is printed on the console terminal. The
CPU then enters the console I/O mode wait loop. However, if the cold start flag is not set,
indicating that a cold start has not been attempted, the console subsystem sets the cold
start flag.

Execute the indirect command file (XXXBOO.CMD) associated with the type of cold
start to be performed. This file executes the functions necessary to cold start the operating
system.

)

Console 1/0 Mode BOOT Command Sequence — Typing the BOOT command at the console
terminal while the CPU is in the console I/O mode wait loop causes the console subsystem to
perform the following sequence of events:
Set the cold start flag.

Execute the indirect command file (XXXBOO.CMD) associated with the type of cold
start to be performed. This file executes the functions necessary to cold start the operating
system.

AUTO/RESTART Switch Set to BOOT Sequence - Setting the AUTO/RESTART switch to
the BOOT position, while the CPU is in the console I/O mode wait loop, causes the console
subsystem to perform the following sequence of events:
®

Print the message ATTEMPTING SYSTEM BOOT on the console terminal.

Examine the cold start flag. If the flag is set, indicating a cold start has previously been
attempted, the message SYSTEM BOOT FAILED is printed on the console terminal. The

CPU then enters the console I/O mode wait loop. However, if the cold start flag is not set,
indicating that a cold start has not been attempted, the console subsystem sets the cold
start flag.
e

Execute the indirect command file (XXXBOO.CMD) associated with the type of cold
start to be performed. This file executes the functions necessary to cold start the operating
system.

)

Console I/0 Mode Diagnostic Supervisor BOOT Command Sequence — Typing the console
[/O mode BOOT command for the diagnostic supervisor causes the console subsystem to
perform the following sequence of events:
e
e

Set the cold start flag.
Execute the indirect command file (XXXBOO.CMD) associated with the type of cold
start to be performed. This file executes the functions necessary to cold start the diagnostic
SUPErvisor.

(6)

XXXBOO.CMD Execution Sequence — The indirect command file executed by the cold start

sequence performs the appropriate functions to cold start either the operating system or
diagnostic supervisor. The name of this file reflects the instructions contained within it.
The name of this file is in the following format:

XXXB0OO.CMD

where XXXBOO describes the cold start device and whether the file cold starts the operating

system or diagnostic supervisor. For example:

Su0B0O.CMD
su0B0O.CMD
DEFBOO.CMD

;

Cold

;

DUAD.

;

Cold

;

DUAD.

starts

the

diagnostic

supervisor

from

starts

the

diagnostic

supervisor

from

starts

the

;

Cold

;

default

system

operating

device

system

from

the

(DUAO).

The instructions contained within these indirect command files causes the console subsystem to perform
the following sequence of events (Figure 3-1):
[nitialize the CPU to a known state and load the address of the first 64K bytes of good memory
plus 200, which was located by the console program, into the stack pointer (SP which is GPR

E).

Load parameters into the general registers RO through RS5. These parameters inform the
primary bootstrap program what to load (either the operating system or diagnostic supervisor),

what device to load from and how to load it. The parameters that can be loaded into the general
registers are shown in Table 3-1.

3-4

Table 3-1

Parameters Loaded into the General Registers at BOOT

Parameters

Description

<07:00>

Cold start device type code

1 (hex)
2 (hex)
3 (hex)
17 (hex)
32 (hex)
64 (hex)

RKO06/7
RLO1/2
IDC (R80, RL02, LESI)
UDA-50 (RA80, RA81, RA60)
HSC on CI
TUS8

<15:08>

Reserved for future expansion

<31:16>

Device class dependent (RPBSWROUBVECQ).

UNIBUS-optional vector address; 0
implies use the default vector.
R1

Cold start device bus adapter address
<31:04>

MBZ

<03:00>

TR number of adapter

<31:18>

MBZ

UNIBUS bootstrap device code
<17:00>

UNIBUS address of cold start device’s

CSR
R3

Cold start device controller unit number

Cold start block logical block number (LBN)

<09:00>
0 (hex)
1 (hex)
2 (hex)
3 (hex)
4 (hex)
5 (hex)
6 (hex)
7 (hex)
8 (hex)
9 (hex)

Software cold start control flags

Conversational cold start
Debug
Initial Breakpoint
Boot block
Diagnostic monitor cold start
Bootstrap breakpoint
Image header
Memory test inhibit
File name (query)
Halt before transfer

Examine the stack pointer (SP) for the address of the first 64K bytes of good memory. This
address is placed in a console RAM location to be used when the @ symbol replaces this
address.
Load the primary bootstrap program VMB.EXE into memory starting at the address in the SP,
then start the program.
Start processing instructions in VMB.EXE. VMB.EXE takes control and loads the secondary
bootstrap program (either SYSBOOT.EXE for cold starting the operating system or
DIAGBOOT.EXE for cold starting the diagnostic supervisor) into memory and starts it
running.

3-5

3.2.1.1

VMB.EXE Operation — The primary bootstrap program VMB.EXE performs the following

functions:

Creates a temporary System Control Block (SCB) to be used during bootstrapping.

Creates and stores warm start data in the operating system data structure called the Restart
Parameter Block (RPB).

Identifies all bus adapters and memory in the hardware system configuration.

Tests all memory to mark each good page in a bit map.

Initializes the cold start device’s adapter.

Prompts for a secondary bootstrap program file specification if the BOOT command specified
the solicit flag (bit O in R5).

Locates the secondary bootstrap program file and loads that file into memory.

Transfers control to the secondary bootstrap program.

3.2.1.2 SYSBOOT.EXE Operation - SYSBOOT is the secondary bootstrap program for the operating
system. This program loads the operating system into memory, and transfers control to its initialization
code.

3.2.1.3 DIAGBOOT.EXE Operation - DIAGBOOT is the secondary bootstrap program for the diagnostic supervisor. It loads the supervisor into memory, and transfers control to its initialization code.
3.3 WARM START (RESTART)
Warm start or restart refers to restarting the operating system without reloading it into memory. When the
console subsystem gains control of the VAX-11/725 following a CPU halt or power restoration, it
performs the sequence of events shown in Figure 3-2.
The sequence of events performed by the console subsystem for warm starting the operating system is
outlined in the following list.
The console subsystem:

Examineé the AUTO/RESTART switch to determine what action will be taken. If the switch is

in the OFF position, the CPU enters the console I/O mode wait loop. If the switch is set to the
ON position the console subsystem prints the console terminal message RESTART IN
PROGRESS.
Examines main memory to determine if data has been preserved. If no data is preserved the
warm start fails.

Checks for the presence of the restart parameter block (RPB) in memory. If the RPB is not
found, the warm start fails. If the RPB is found, then the console subsystem checks to see if it is
valid (see Section 3.3.1.) If the RPB is not valid warm start fails. If the RPB is valid the console
terminal loads the SP with the address of the RPB plus X200.

Loads the AP (GPR C) with a value that indicates the cause of the warm start.

Jumps to the location contained in the second longword of the RPB and starts execution of the
operating system restart routine (Section 3.3.2).

3-6

( WARM START >
IS

AUTO/RESTART

SWITCH SET
TO ‘ON’

CONSOLE 1/0 MODE

MODE WAIT LOOP

“LLL

“SYSTEM RESTART

FAILED"”

PRINT
“ATTEMPTING SYSTEM

RESTART”

‘

ATTEMPT

BOOT

EXAMINE

MEMORY FOR
PRESERVED
DATA

CHECK

FOR VALID

RPB

LOAD AP

WITH HALT

CODE

'
START EXECUTION

OF WARM START
ROUTINE

TK-9706

Figure 3-2

Warm Start of the Operating System

3-7

If warm start fails, the console subsystem prints the console terminal message RESTART FAILED and
attempts to cold start the operating system (Section 3.2).

If the operating system warm starts successfully, it sends a message to the console subsystem, causing the
console to clear the cold and warm start flags.
3.3.1

Restart Parameter Block (RPB)

The RPB (Figure 3-3) is a block of four longwords starting on a page boundary. It contains sufficient data

for the operating system to warm start itself from the point at which either a power failure or software
crash occurred. The console subsystem performs the following actions with the RPB during a warm start
sequence:

Searches through physical memory for a paged, aligned longword that contains its own address.

Compares the first longword to the second longword of the RPB. If these longwords are equal,
the RPB is not valid, and the warm start fails. However, if these longwords are unequal, the
console subsystem compares the checksum of the first 31 longwords of the restart routine
against the contents of the third longword in the RPB. If the checksum is valid, the RPB is

valid.
3.

Checks the warm start flag in the fourth longword. If the warm start flag is set, the warm start
fails. If the warm start flag is not set, the console subsystem starts execution of the restart
routine.

PHYSICAL ADDRESS OF THE RPB

PHYSICAL ADDRESS OF THE VMS WARM START ROUTINE

CHECKSUM OF THE FIRST 31: LONGWORDS OF WARM START ROUTINE

WARM START FLAG (BIT 0)

TK-4306

Figure 3-3

Restart Parameter Block (RPB)

3.3.2 Restart Routine
The restart routine attempts to recover from a power failure or software crash by recreating a consistent

software environment. The restart routine sets the warm start flag to prevent warm start looping by
displaying a WARM START IN PROGRESS message. It then restarts the operating system. If the warm
start succeeds, the operating system requests the console subsystem to clear both the cold and warm start
flags.

3-8

CHAPTER 4
MICRODIAGNOSTICS

4.1

INTRODUCTION

Microdiagnostics are the lowest level of diagnostics (level 5) in the VAX-11/725 diagnostic system. These
diagnostics test the system at the console microprocessor and CPU microcode levels, and should be
executed when higher level diagnostics (levels 4, 3, 2, 2R and 1) are unable to load or execute. They are
the only level of diagnostics that provide for call-out of faulty module(s) for repair.
Digital Equipment Corporation supplies the microdiagnostics programs on a single TUS8 tape cartridge,
labeled 11725/730 MICRODIAG (TUS8 #36), and on the diagnostic distribution media, labeled VAX725/730 CMPLT DIAG. These microdiagnostic programs are divided into two groups of multiple
sections; ENKBx and ENKCx (where x is sections A through G).
NOTE

Throughout the remainder of this chapter, individual
microdiagnostic programs will be referred to as
microdiagnostic sections.

The microdiagnostic group ENKBx executes from the console microprocessor RAM, and tests the
hardware on the WCS (Writable Control Store) and the DAP (Data Path) modules. The console
microprocessor group sections are listed in Table 4-1.

Table 4-1

ENKBx Microdiagnostic

Section

Number of Tests

ENKBA
ENKBB
ENKBC
ENKBD
ENKBE
ENKBF*
ENKBG*

1-8
9-F
10-1D
1E-26
27-2D
2E

Sections ENKBF and ENKBG are only executed when specifically called out by the section qualifier.
These tests are not executed when the diagnose command, MIC>DI, is given with no section selected.
ENKBEF tests the WCS RAM memory thoroughly using a ““march” pattern, which takes approximately 5 minutes to execute.

ENKBG tests the remote diagnosis (RD) port on the M8394 board. It requires a modem loopback
connector (H3248 may be used) on the RD port.

4-1

The ENKCx group executes from the WCS RAM (which writes over any system microcode that may be

loaded) and uses the CPU micromachine to test the parts of the system listed in Table 4-2.
NOTE
There is no microdiagnostic for the DMF32 (COMBO board), as it is a UNIBUS device. The DMF32
contains a ROM board hard-core self-test which is
evoked by either the power-up self-test (Chapter 2)
or

commands

from

the

execution

macrodiagnostics (Chapter 5).

Table 4-2

Section

Number of Tests

Parts Tested

ENKCA

ENKCB

1-20
1-B

CPU
CPU

ENKCC*
ENKCD

1-44
1-10

Memory Controller (MCT)
CPU/MCT

1-45

Floating-Point Acc. (FPA)
Internal Disk Cont. (IDC)

ENKCE

ENKCF**

ENKCG**

ENKCH**
*

ENKCx Microdiagnostic Group Sections

1-35

~
|

Internal Disk Cont. (IDC)
Internal Disk Cont. (IDC)

Tests 1-33 of section ENKCC are executed automatically when the MICMON diagnose command
MIC=>DI is used alone. Tests 34-43 of ENKCC are executed automatically if a UNIBUS exerciser

(UBE) module is present in the system. Test 44 of ENKCC thoroughly tests the main memory array
boards using a march test pattern. It is executed only when explicitly called out by the command,
DS>DI TE 44.
**These tests are not used by the VAX-11/725 processor.

One other diagnostic program is the microdiagnostic monitor or MICMON (ENKAA.EXE). The
MICMON provides the code to load, control, and monitor all microdiagnostic sections. This program loads

the microdiagnostic sections from the TUSS8 tape cartridge into the proper test area. It is also responsible
for reporting any errors that occur during its loading, and for controlling and monitoring the microdiagnostic tests.

NOTE
The MICMON and the microdiagnostics are also
loaded and executed under Customer Runnable
Diagnostics (CRDs). Refer to Chapter 7.

4.2 LOADING THE MICMON
The console microprocessor loads the MICMON from the TU58 tape cartridge into the console RAM by

one of two methods. The MICMON can be loaded either before or after the system microcode is loaded.

4-2

Method 1 loads the MICMON prior to loading the system microcode. Perform the procedures below:
1.

Insert TUS8 tape cartridge #36 (labeled 11725/730 MICRODIAG) into TUS8 tape drive 1.
CAUTION
Make sure that the stabilizer foot is extended from
the bottom of the system cabinet before the CPU
mounting box is extended.

Set the AUTO-RESTART/BOOT switch to the OFF position.

Turn the keyswitch to the LOCAL position.

The VAX-11/725 powers up and the CPU enters the microdiagnostic monitor (MICMON), causing the
console to produce a printout as shown in Example 4-1.

CONxyz

740

FILE

NOT

FOUND

DD1:CONSOL.EXE

CONTINUING

727

READ

ERROR

DDO:

CONTINUING

227

READ

ERROR

DDO:

CONTINUING
VER

X.Y

MMM.YY

MIC>

Example 4-1

Console Printout at Powerup as the CPU Enters MICMON

Method 2 loads the MICMON after the console microcode. Perform the following procedure:

Insert the TUS8 tape cartridge #34 (labeled VAX 11725/730 CONSOLE) into TUS8 tape
drive 1.
CAUTION
Make sure that the stabilizer foot is extended from
the bottom of the system cabinet before the CPU
mounting box is extended.

Set the AUTO-RESTART/BOOT switch to the OFF position.

4-3

Turn the keyswitch to the LOCAL position.
The VAX-11/725 powers up into the console I/O mode and the console terminal produces a
printout as shown in Example 4-2.

Insert the TUS8 tape cartridge #36 (labeled 11725/730 MICRODIAG) into TU58 tape drive 0
and type T/C in response to the console prompt, >>>, to load and execute the microdiagnostic
monitor.
The console terminal produces a printout as shown in Example 4-3.

Once the CPU is in MICMON, the microdiagnostics are executed by commands typed in response to the
MICMON prompt (MIC>).

CONSOLE

VERSION

XX.nn

>>>aPOWER.CMD

>>>L/C

CONSLE.CPU

IVERSION

>>>L/C/S:0800

MMIE.CPU

I'VERSION

>>>L/C/S:0ECO

POWER.CPU

''VERSION

>>>S/C

>>>W

>>>aC0ODEQO.CMD

>>>L/C/S:0E00

FP.CPU

IVERSION

>>>L/C/S:1A00

BITFLD.CPU

IVERSION

>>>L/C/S:1000

CM.CPU

'VERSION

>>>L/C/S:2200

BASIC.CPU

IVERSICN

>>>L/C/S:3B00

QUEUE.CPU

IVERSION

>>>1
>>>

Example 4-2

Console Printout at Powerup as the CPU Enters the Console 1/0O Mode

>>>T/C

CONSOLE

740

FILE

NOT

FOUND

DD1:ENKAA.EXE

CONTINUING
VER

XX.XX

MIC>

Example 4-3

Console Printout of the CPU Entering the MICMON from the Console 1/O Mode

4.3 MICRODIAGNOSTIC MONITOR COMMANDS
The following is a list of MICMON commands to execute the microdiagnostics:
RETURN
CONTINUE

DIRECTORY
T/E
REPEAT
DIAGNOSE
START

S/U
INITIALIZE
DEPOSIT/EXAMINE
SET/CLEAR

LOAD
SHOW

These commands are defined and illustrated with examples in Appendix B.
4.4

MICRODIAGNOSTIC ERRORS
Microdiagnostic errors are detected and error messages are displayed under two conditions:
e

Any time the CPU is under the control of the MICMON.

When the individual microdiagnostic sections are executed. When errors are detected while the
CPU is under control of the MICMON, due to conditions such as testing timeout or WCS
parity, the MICMON prints an error message such as those shown in Examples 4-4 and 4-5.
Example 4-5 is the error message MICMON prints if the SE TR command was entered.

MIC>DI
ENKCC

ENKCC

Vxx.xXx

UPC

FFFF

?xx

ERROR

MIC>

Example 4-4

MIC>DI

ENKCC

v00.05

ENKCC

TEST
TEST

01
02

03
04
05

ENKCC
ENKCC

TEST

ENKCC
ENKCC

TEST

ENKCC

TEST

ENKCC

TEST
TEST

07
08

ENKCC

MICMON Error Printout

TEST

(1)

(2)

(3)

(4)

(5)

(6)

(7)

(8)

SECT

TST

ERR

EXP

REC

OTHER

MSK

MODULE

ENKCC

0000000c

000OQOOA

N/A

FFFFFFOO

M8391

MIC>

Example 4-5

MICMON Error Printout After SE TR Command

4-5

The xx in the error message shown in Example 4-4 is the hex error code shown in Table 4-3.
The microdiagnostic error printout in Example 4-5 is explained below:

(1)

Diagnostic section in which an error occurred

(2)

Test number within that diagnostic section

(3)

Error number. Within a particular test, several pieces of hardware may be tested, each by a
subtest. The error number identifies the unique subtest that failed.

(4)

Expected correct data

(5)

Received data

(6)

OTHER field will contain N/A (not applicable) or pertinent data. When datais present, the

errors sectlon of the test listing on microfiche will define the data.

(7)

(8)

MASKis the error mask used to check the result. Bits set to a 1 in this mask correspond to bits
~in the result that are not checked.
MODULE is the suspected failing module.

Table 4-3

MICMON Error Code List (Hex)

Error Code

Definition

Board not found

No test number found

No pass count found

Continue not available at this point

No address or no data input with command

No WCS image for exam or deposit routine

Examine or Deposit main memory reports error

Sequence error in WCS testing or nonexistent test

Timeout error in WCS testing

TUSS8 error
Parity error in WCS

Checksum error in MICMON

28
2A

DI TE attempted with possible invalid test code loaded (do DI SE or DI BO)
UPC does not match on verify of 32 bit data write
INIT done without file loaded

Checksum error in X command

No X command address found

No X command count found

4-6

CHAPTER 5§

VAX-11/725 DIAGNOSTIC SUPERVISOR AND LOAD PATH

5.1
INTRODUCTION
The VAX-11/725 diagnostic supervisor may be loaded off-line from the RC25 diagnostic distribution
disk, the RC25 system disk, or the TUS8 tape drive. If the user disk drive is not used by VMS, the
supervisor is loaded from the distribution disk while the system is operating in the user mode. However, if
the user disk drive is unavailable, the supervisor is loaded from the system disk. The supervisor is loaded
from the TUS58 only if it cannot be loaded from the user or the system disk drives.
NOTE
The [SYSMAINT] directory on the system disk
must

contain

the

diagnostic

supervisor

file

ENSAA.EXE before the supervisor can be booted
from that disk.

Loading the supervisor from the disk drive is considered loading through the primary load path. In
contrast, loading the supervisor from the TUS58 is considered loading through the secondary load path. The
primary path is used first, but if the system has a hardware failure in the disk subsystem (LESI or its disk
drives) or in the CPU cluster, the supervisor may be loaded through the secondary load path. However,
before the supervisor is loaded from the TUSS, level 4 diagnostics are executed. If the level 4 diagnostics
execute without error, the supervisor is executed, followed by the execution of level 3 disk subsystem
diagnostics.
5.2 LOADING THE SUPERVISOR THROUGH THE PRIMARY LOAD PATH
The VAX-11/725 computer system uses low end storage interface (LESI) based disk drives to provide the
primary load path for the diagnostic supervisor program.
5.2.1
Loading the Supervisor Off-Line from the Diagnostic Distribution Disk
The diagnostic supervisor is loaded off-line from the diagnostic distribution disk by booting the supervisor
from that disk. To boot the diagnostic supervisor from the diagnostic distribution disk, perform the
following procedures:
1.

Press the EJECT switch to open the cartridge receiver door.

Load the diagnostic distribution disk labeled “VAX 725/730 CMPLT DIAG” into the disk
drive, close the receiver door, and press the RUN switch to place the drive on line.

When the RUN indicator on the disk drive is continuously lit, type the following command at
the console prompt (>>>) to boot the supervisor.
>>>B

SUOD

5-1

When

you

NOTE
command “>>>B SU0”,
1.75 minutes elapses before any

type

approximately

the

messages are printed on the console terminal.

The console responds by printing a boot message and the diagnostic supervisor prompt (DS>) as shown in
Example 5-1. The DS> prompt indicates that the diagnostic supervisor is loaded and executing.

>>>B

SUC

>>>aDD1:SUCBOC.CMD
>>>1

>>>D/G/L

>>>D/G

3F468

>>>D/G6

>>>D/G

>>>D/G6

>>>D/G

>>>E

COCOOC0OE

>>>L/P/S:a
>>>S

0O0GOCe00
VMB.EXE

DIAGNGSTIC

SUPERVISOR.

ZZ-ENSAA-x.x=-xxx

DD-MMM-YYYY

HH:MM:SS

DS>

Example 5-1

Booting the Diagnostic Supervisor from the RC25 Diagnostic Distribution Disk

5.2.2 Loading the Diagnostic Supervisor Off-Line from the System Disk
|
The diagnostic supervisor is loaded off-line from the system disk by booting the supervisor from that disk.

To boot the diagnostic supervisor from the system disk, perform the following procedures:
1.

Press the RUN switch to place the system drive on-line.

When the RUN indicator on the disk drive is continuously lit, type the following command at

the console prompt (>>>) to boot the supervisor.
>>>B

SU1

The console responds by printing a boot message and the diagnostic supervisor prompt (DS>) as
shown in Example 5-2. The DS> prompt indicates the diagnostic supervisor is loaded and
executing.

5-2

>>>B

SU1

>>>abD1:SU1TBOC.CMD
>>>1

>>>b/6/L

>>>D/G

3F468

>>>D/G6

>>>D/G

>>>D/G6

>>>D/G

>>>E

000CO0CE

>>>L/P/S:d

>>>S

0000G200
VMB.EXE

DIAGNOSTIC

SUPERVISOR.

ZZ-ENSAA-x.x=xxx

DD-MMM-YYYY

HH:MM:SS

DS>

Example 5-2

Booting the Diagnostic Supervisor from the RC25 System Disk

5.2.3 Loading the Supervisor On-Line from the Distribution Disk
To load and execute the diagnostic supervisor in the on-line mode (with VMS) from the distribution disk,

perform the following procedures:
1.

Press the EJECT switch to open the cartridge receiver door.

Load the diagnostic distribution disk labeled “VAX 725/730 CMPLT DIAG” into the disk
drive, close the receiver door, and press the RUN switch to place the drive on-line.
When the RUN indicator on the disk drive is continuously lit, type the following command at

the VMS prompt ($) to mount the distribution disk.
$MOUNT

DUAO:

CRDPACK

The terminal responds with the following message to indicate that the disk is mounted properly.

MOUNT-I-MOUNTED,

CRDPACK

mounted

DUAO:

$
In response to the VMS prompt, type the following command to set default to the directory
containing the diagnostic supervisor program (ENSAA.EXE).

SET

DEFAULT

DUAO:[SYSMAINT]

Type the following command to load and execute the diagnostic supervisor.

RUN

ENSAA.EXE

5-3

When the diagnostic supervisor starts, it prints the following message:
DIAGNOSTIC

SUPERVISOR.

ZZ-ENSAA-x.x=-xxx

DD-MMM-YYYY

HH:MM:SS

DS>

5.2.4 Loading the Supervisor On-Line from the System Disk
To load and execute the diagnostic supervisor in the on-line mode (with VMS) from the system disk,
perform the following procedures:
1.

In response to the VMS prompt, type the following command to set default to the directory
containing the diagnostic supervisor program (ENSAA.EXE):
$

SET

DEFAULT

SYSSMAINTENANCE

Type the following command to load and execute the diagnostic supervisor:
$

RUN

ENSAA.EXE

When the diagnostic supervisor starts, it prints the following message:

DIAGNOSTIC

DS>

SUPERVISOR.

ZZ-ENSAA-=X.X—XXX

DD-MMM-YYYY HH:MM:SS

5.3 LOADING THE DIAGNOSTIC SUPERVISOR THROUGH THE SECONDARY LOAD PATH
If the diagnostic supervisor cannot be booted from the distribution or system disk, use the secondary load
path (TUS8 tape drive) to load programs which test the hardware in the primary load path. These
programs are called load path diagnostics.
Digital Equipment Corporation supplies load path diagnostics for the VAX-11/725 system on the following TUS8 cassette tapes:

VAX 11 HARDCORE INSTR (TUSS8 #7)

11725/730 DIAG SUPER (TUS8 #35)

VAX RC25 SUBSYSTEMS (TUS58 #58)

TUS8 tape cartridge #7, labeled VAX 11 HARDCORE INSTR, is inserted into a TUS58 tape drive and
the level 4 diagnostic (EVKAA.EXE) is loaded and executed using the console command language. This
diagnostic program functionally verifies the kernel instruction set used by the diagnostic supervisor. If the
level 4 diagnostic program executes without error, the diagnostic supervisor (ENSAA.EXE) is loaded and
executed from the TUSS8 tape cartridge #35, labeled 11725/730 DIAG SUPER. The functional integrity
of the disk controller (LESI) and its attached disk drives are then tested with the disk subsystem diagnostic
programs that reside on TUS58 tape cartridge #39, labeled VAX 725/ 730 IDC DIAG and on TUSS8 tape
cartridge #58, labeled VAX RC25 SUBSYSTEMS.

5-4

The diagnostic programs on the VAX RC25 SUBSYSTEMS (TUS8) tape cartridge are listed below:
EVRMA.EXE

I
!

VAX

EVRMB.EXE

VAX

EVRMB.HLP
EVRMC.EXE

!
!

Help File for the EVRMB Diagnostic
VAX RC25 Level 3 Disk Formatter

EVRMC.HLP

Help

EVRMA.HLP

RC25

Help

File
RC25

File

Disk

for

Exerciser
the EVRMA

Front

for

End

the

Diagnostic

Test

EVRMC

Diagnostic

5.3.1
Executing Diagnostics for the Load Path
The level 4 diagnostic is loaded from the tape cartridge and executed using the console command
language.
To load the level 4 diagnostic from the tape cartridge, follow the procedures below:
1.

Insert the TUS8 tape cartridge #7, labeled VAX 11 HARDCORE INSTR, into the TU58 tape
drive 0.
|
In response to the console prompt, >>>, type the following commands to load and execute the
level 4 diagnostic EVKAA .EXE.:
>>>1

>>>p/P/L

FEOQOO

>>>L/P/S:0

>>>S

DDO:EVKAA.EXE

200

If EVKAA executes successfuly, at the end of each 16 passes the console produces a printout as
shown below and rings the terminal bell.

EVKAA

Vn.n

PASS

#nn

DONE!

EVKAA

Vn.n

PASS

#nn

DONE!

EVKAA

Vn.n

PASS

#nn

DONE!

This program continues to execute and produce the above printout until a CTRL/P is typed. At
that time the system returns to the console I/O mode and prints the console prompt, >>>.
If the level 4 diagnostic executes without error, the diagnostic supervisor (ENSAA.EXE) is
loaded from TUS8 #35 and executed using the console command language. Then, the disk
subsystem diagnostic is loaded and executed.

Remove TUS8 #7 from TUS8 tape drive O.
Insert TUSS8 tape cartridge #35, labeled 11725/730 DIAG SUPER, into TUS8 tape drive O.
In response to the console prompt, type the following commands to load and execute the
diagnostic supervisor from the tape cartridge:
>>>1

>>>L/P/S:FEOO0

>>>S

DDO:ENSAA.EXE

10000

5-5

When the diagnostic supervisor starts, it prints the following message:
DIAGNOSTIC

SUPERVISOR.

ENSAA=-x.x=xx

DD-MMM-YYYY

HH:MM:SS

DS>

Use the ATTACH command to define the system hardware configuration, as shown below:

DS>ATTACH

KA730

HUB

KAO

DS>ATTACH

DW730

HUB

DWO

DS>ATTACH

LESI

DWO

DS>ATTACH

RC25

DAA

DS>ATTACH

RCF25

DAA

DAAD

DAA

YES

O3FF

772150

0154

2048
05

DAA1

Select the disk drives for testing with the following command:

DS>SELECT

DAAO,

DAA1

Remove TUS8 #35 from TUS8 tape drive O.

Insert the TUS8 tape cartridge #58, labeled “VAX RC25 SUBSYSTEMS,” into TU58 tape
drive O.

10.

Use the HELP command to obtain system set-up information on the diagnostic programs
EVRMA.EXE, EVRMB.EXE, and EVRMC.EXE.
DS>HELP

DS>HELP

EVRMA
EVRMB

DS>HELP

EVRMC

Perform the set-up procedures, then run the diagnostics with the RUN command:
DS>RUN

EVRMA.EXE

DS>RUN

EVRMB.EXE

5.4
DIAGNOSTIC SUPERVISOR COMMANDS
Commands for the diagnostic supervisor are obtained by using the HELP utility. If the supervisor was
loaded from a disk device, the HELP utility is invoked by typing the HELP command (for example, DS>
HELP). This command used in conjunction with a particular topic (for example, DS> HELP SHOW)
displays general diagnostic environment and supervisor command information.

5-6

Most diagnostics programs also have HELP files to assist in their execution. These HELP files have the
same filename as the diagnostic program file, but the file extension is named .HLP (EVRMA.HLP). Help
files are accessed by typing the HELP command followed by the filename (DS> HELP EVRMA). Using
this command in conjunction with the diagnostic program name displays diagnostic information specific to
that diagnostic.
System configuration is bypassed to the diagnostic supervisor either with individually typed ATTACH
commands or by executing the autosizer program on the diagnostic distribution disk.
The autosizer program (EVSBA.EXE) sizes the system on which it is executed (under the diagnostic
supervisor in the console mode) and passes the system configuration to the diagnostic supervisor with a
single command.
To execute the autosizer, perform the following procedures:
1.

Load and execute the autosizer in its self-test mode by typing the following commands:
DS>SET

FLAG

DS>RUN

EVSBA/SECTION:SELFTEST

QUICK

The autosizer is'foaded and executed and produces the prompt: COMMAND?. At this prompt,
type the following command to instruct the autosizer to determine the hardware configuration
of the system. Then, pass this information to the diagnostic supervisor:
COMMAND?

SIZE

The autosizer prints ATTACH commands as they are passed to the diagnostic supervisor
(Example 5-3).

Type ATTACH to the COMMAND? prompt to actually build the database in the diagnostic
SUPErvisor.

Type EXIT to the COMMAND? prompt to exit the autosizer program. The autosizer prints the
completion message shown below (if no errors were encountered) on exiting. It then returns
console control to the diagnostic supervisor, DS>.
COMMAND?

..End

time

EXIT

run,

errors

dd-mmm-yyyy

detected,

pass

count

HH:MM:SS

DS>

Select the devices to be tested. Then use the RUN command to load and execute the diagnostic
program.

See Chapters 4 and 5 of the VAX Diagnostic System User’s Guide for details on the diagnostic supervisor
commands.

5-7

AUTOMATIC

SIZING

CONFIGURATION

PROGRAM.

FILE

FOR

GENERATED

CPU

TYPE

LEADING

COMPUTER

!
!

NUMERIC

FILE

VALID

TIME

*%x*xQUICK

VALUES

WITH

ONLY

SYSTEM.

FOR

STANDARD

dd=-mmm-yyyy

hh:mm:ss

FLAG

SET.

CHECKS

KAO

YES

MICROCODE

ZERC

ARE

REVE LEVEL
ASSIGNED.

HARDWARE

CONFIGURATION.

MADE

TERMINALS

FOR

DZ11'S*%x%

[
|

DEFINE

DS>

PROCESSOR...

ATTACH

DEFINE

KA73C

UNIBUS

HUB

O3FF

0148

ADAPTERS...

ATTACH

DW730

DS>

ATTACH

LESI

DWO

DAA

DS>

ATTACH

RC25

DAA

DAAO

DS>

ATTACH

RCF25

DS>

HUB

DWC

DAA

772150

0154

DAA1

DS>

ATTACH

DMF32S

DWO

XGAO

DS>

ATTACH

DMF32A

DWO

TXA

760340

0300

0377

DS>

ATTACH

DMF32P

DWO

LCA

760340

0300

OTHER

760340

0300

NONE

96G0

INTERNAL

COMMAND?

Example 5-3

Typical Autosizer Printout of a VAX-11/725 System

5-8

YES

CHAPTER 6

EXECUTING THE LEVEL 4 DIAGNOSTIC PROGRAM

6.1 LOADING AND EXECUTING THE LEVEL 4 DIAGNOSTIC PROGRAM
Only one level 4 diagnostic program applies to the VAX-11/725 - EVKAA, a hardcore instruction test.

DIGITAL ships this diagnostic program for the VAX-11/725 on the following diagnostic distribution
media:

TUSS8, #7 labeled VAX 11 HARDCORE INSTR

RC25, #1 labeled VAX 725/730 CMPLT DIAG

The method for loading the level 4 diagnostic into memory from the TUS58 tape cartridge is different from
loading it from the disk pack.

The level 4 diagnostic is loaded into memory from the TUS8 tape cartridge by using the console command
language. However, the diagnostic is loaded into memory from the disk pack with the diagnostic
SUPErvisor.
,
After the diagnostic is loaded into memory, it is executed from the console I/O mode with the START
command.

6.1.1

Loading EVKAA from the TUS8 Tape Cartridge

The level 4 diagnostic EVKAA is loaded and executed with the console command language as shown in
the following steps:

Insert the TUSS8 tape cartridge #11, labeled VAX 11 HARDCORE INSTR, into the TUS58
drive O.

At the console prompt, >>>, type the following commands to load and execute EVKAA:

>>>1

>>>p/P/L

FEQO

>>>L/P/S:0

DDO:EVKAA.EXE

Initializes

the

Zero

memory

Llocation

Loads

the

>>>

CPU.

diagnostic

FEQO.
into

After EVKAA is loaded into memory, it is executed using the procedure in Section 6.1.3.

6-1

memory.

6.1.2 Loading and Executing EVKAA from the Disk Pack
EVKAA is loaded and executed from the disk pack as described in the following:
1.
2.

Boot the diagnostic supervisor from the disk pack as described in Chapter 5.
When the DS> prompt is displayed, load EVKAA from the disk pack into memory by using

the LOAD command:
DS>LOAD

EVKAA

Loads

the

diagnostic

into

memory.

Exit from the diagnostic supervisor to the console I/O mode by typing the EXIT command:
DS>EXIT

702

Terminates

the

supervisor.

Enters

diagnostic

PCc=0001A5D8

>>>

the

console

I/0

mode.

6.1.3

Executing EVKAA
After EVKAA is loaded into memory it is executed at memory location 200 with the following command:
>>>Ss

200

Executes

memory

the

diagnostic

location

program

200.

If EVKAA executes successfully, at the end of each 100 passes the console produces one line of the
printout shown below and rings the terminal bell.
EVKAA

Vx.x

PASS

#nn

DONE!

EVKAA

Vx.x

PASS

#nn

DONE!

EVKAA

Vx.x

PASS

#nn

DONE!

This program continues to execute and produce the above printout until a CTRL/P

is typed. At that time

the system returns to the console I/O mode and prints the console prompt, >>>.
If EVKAA does not execute successfully, it prints the error message shown below and returns control to
the console I/O mode.
??7?7ERROR

(one

Line

TEST

#nn,

SUBTEST

description

EXPECTED

DATA:

XXXXXXXX

RECEIVED

DATA:

XXXXXXXX

706

#nn

(instruction)

FAILED

failure)

00009301

>>>

6.2

EVKAA ERROR INTERPRETATION AND LOOP CONTROL
When EVKAA detects an error and the halt code is 06, it indicates that the processor executed a HALT

instruction at the error. Other halt codes indicate that the program is not executing properly. See Table 2-1
for a list of halt codes and their meanings.
If the error message was printed and the halt code is 06, the user can look in the listing for the algorithm
used to determine the failure.

6-2

NOTE
If the base address for the program is not 0, the user
must find the base address and subtract it from the

PC in order to find the corresponding HALT
instruction in the listing.

General register 10 contains the base address and is examined by typing the following command:
>>>E/G

00000010

00000000

Examines

Base

address

R10.

00000000.

Consider the case where the user executes the hardcore instruction test and gets the console output in
Example 6-1.

>>>1
>>>p/P/L

FEOO

>>>L/P/S:0
>>>S

DDO:EVKAA
. EXE

200

???2ERROR

(one

TEST

Lline

#nn,

SUBTEST

description

EXPECTED

DATA:

XXXXXXXX

RECEIVED

DATA:

XXXXXXXX

2706

Initializes

the

Zero

memory

Location

Loads

the

Starts

#nn

CPU.
FEOQO.

diagnostic

the

into

diagnostic

(instruction)

memory.

program.

FAILED

failure)

00009301

>>>

Example 6-1

HALT in Hardcore Instruction Test

Look up the location 9300 (the PC minus 1) in the program listing. Read the test description and analyze
the code. If the fault is a hard error, the user can cause the program to loop (on the next pass) by replacing
the HALT instruction with a NOP instruction.
NOTE
The user should examine the location first to make
sure that it contains a HALT instruction.
By replacing the HALT with a NOP, the error message printing is cancelled.
Example 6-2 shows an EXAMINE and DEPOSIT to the location that contains the HALT instruction.

>>>E/P/B

9300

00009300

>>>p/P/B

9300

Examines

Llocation

Deposits

9300.

00
01

the

byte

Location 9300.
Continue. The program

>>>C

Loop

Example 6-2

should

error.

Level 4 Diagnostic Program Set Up to Loop on Hard Error

6-3

at.

However, if the error is intermittent, the program may progress out of the loop on the first success. In
order for the program to loop every time, the user must find the instruction which checks for success or
failure and replace it with a NOP instruction (see Example 6-3).

92C1
92C1

12591
12592

T12 _S§55:

92CC

12593

5%:

92D5
9207

12594
12595

BISPSW
TSTW

92DD

12596

92DF
92Eb

12597
12598

92EQ

12599

MOVPSL

#-1,TEMPO
#15
TEMPO
R

BICL
MOVL

HNZVC,R1
#8 ,R0

XORLS

RO,R1,R2

Compare

and received data.
Test for success.

BEQL

109

12601

MOVAB

92F4
92F8

12602
12603

TSTL

92FA
92FC
92FE

12604
12605
12606

B"1045%,°X44(R11)
#1, X40(R11)
(R11)
1045%

MOVW
BEQL

JSB
BRB

12607
12608

1045%:

9303

12609

10%:

Example 6-3

HALT

Branch
next

BRB

CLRL

expected

test.

Halt.
Loop PC

9300
9301

(R12)
108

12600

92ED
92EF

#°X55,SUBNUM

MOVL
MOVW

printed.

part

test.

Level 4 Program Listing Sample EVKAA, Test 12, Subtest 55

In this case, the BELQ 10$ instruction at line 12600 checks for success of the test operation. Also, the
BRB 10$ instruction at line 12606 branches to the next test after completion of another operation. Two
bytes correspond to each instruction. Both the instruction and displacement in the instructions are replaced
with two NOP instructions (0101) as shown in Example 6-4.

>>>E/P/W
P

92ED

000092ED

>>>D/P/W

92ED

>>>E/P/W

92FE

>>>E/P/B

9300

>>>b/P/B

0101

000092FE

>>>D/P/W

9300

Examine

the

two

bytes

92ED.

|
!

Deposit
Examine

two

NOP
two

codes
bytes

the

92ED.
92FE.

!
!

Deposit
Examine

two

NOP

the

HALT

!
|
!

Replace the HALT with
Continue. The program
on the error.

0311

0101

00009300

1413

codes at 92FE.
Llocation.

>>>C(C

Example 6-4

Setting Up a Loop on an Intermittent Error

6-4

NOP.

should

Lloop

CHAPTER 7
CUSTOMER RUNNABLE DIAGNOSTICS

7.1
INTRODUCTION
Customer runnable diagnostics (CRD) is a special control program that simplifies the execution of microand macrodiagnostics in the VAX-11 diagnostic system on the VAX-11/725 system.

The CRD package operates in two modes: AUTO and MENU. In the AUTO mode, off-line bottom-up
testing is performed on the system without user intervention. In the MENU mode, the user is offered, with
menu prompts, the opportunity to further off-line test (beyond AUTO mode testing) any device, including
added options, on the system.
NOTE
Both TUSS8 tape drives, the removable media disk
drive, and the console terminal are used for CRD, so
they must be functional.

For more informatior; on customer runnable diagnostics, refer to the documentation entitled Customer
Runnable Diagnostics User Guide.
7.2 CRD MINIMUM SYSTEM CONFIGURATION
The minimum VAX-11/725 system requirements on which CRD testing is performed consist of the
following:

VAX-11/725 CPU cluster with 1M bytes of memory

Disk controller (LESI)

Dual TUS58 tape drive

Console terminal

RC25 disk drive

TUSS, #34 “VAX 11725/730 CONSOLE” tape cartridge

TUSS, #36 “VAX 11725/730 MICRODIAG” tape cartridge

RC25, #1 “VAX 725/730 CMPLT DIAG” disk cartridge

7.3

AUTO MODE

CRD AUTO mode performs the following tests in the order shown:
l.

Test the CPU, memory, and FPA with microdiagnostics.

Test the CPU with level 4 diagnostics.
Boot the Diagnostic Supervisor from the disk drive.
Test the LESI and RC25 disk drives with macrodiagnostics.
NOTE
The DMF32 module is not tested in AUTO Mode;

this testing must be performed manually in the
MENU Mode. Refer to Paragraph 7.4 for this
procedure.

Once AUTO mode is invoked, device testing is completed without user intervention in approximately 15
minutes. An exception to this would be when the system is improperly set up. In this instance, the AUTO
mode program displays an informational message and halts (Example 7-1). The operator has a chance to
properly prepare the system, and resume execution of the AUTO mode by typing a <CR>.

* X %

BEGIN

VERSION

CPU

x.x

PART

RUN

VAX-11/730,725
TIME

MEMORY
CPU

PART

FPA
CPU

PART

PROPER

CHECK

INSERTED

AND

CORRECT,

SETUP
FOR

SETUP

RC25

PART

RC25

PART

RCF25
AUTO

TEST

**kk%

END

MEN U

MODE

RUN

TIME

PASSED

TESTING

STARTED

RUN

TIME

PASSED

TESTING

STARTED

RUN

TIME

" PASSED

TESTING

STARTED

RUN

TIME

1:45

TESTING

STARTED

RUN

TIME

4.00

=--

TYPE

TESTING
NO

entered

CONTINUE

'CRDPACK'®

* %

DRIVE

PROBLEMS

STARTED

TIME

STARTED

RUN
=--

=--

RUN

* *

PASSED

TIME

PASSED

TIME

ERRORS

AUTO

this

TEST

**%x%

point.

AUTO Mode Testing with Improper System Setup

7-2

PASSED

DAAO:

RC25

TESTING

VAX-11/730,725

Example 7-1

DRIVE

TESTING

<CR>

PACK

POSSIBLE

DAAD

COMPLETE

=--

SPINNING

DAA1T

* % %
MINUTES

STARTED

DIAGNOSTIC

DAAO

TEST
15:00

TESTING

REQUIRED

RC25

AUTO

APPROXIMATELY

PASSED

Upon successfully completion of AUTO mode CRD enters MENU mode (see Section 7.4).
7.3.1
AUTO Mode Evocation
AUTO mode is invoked after system preparation is performed. The system is prepared for testing and
AUTO mode is invoked by performing the following procedures:
1.

Insert TUSS8 tape cartridge #34, labeled VAX 11725/730 CONSOLE, into TUS8 tape drive 1.

Insert TUSS8 tape cartridge #36, labeled 11725/730 MICRODIAG, into TUS8 tape drive O.

Press the EJECT switch to open the cartridge receiver door.

Load the diagnostic distribution disk labeled VAX 725/730 CMPLT DIAG into the disk drive,
close the receiver door, and press the RUN switch to place the drive on-line.

When the RUN indicator on the disk drive is continuously lit, proceed with the next step. This
drive and the system disk drive may or may not be WRITE PROTECTed.
NOTE
CRD AUTO mode performs nondestructive disk
testing on VAX/VMS disk cartridges. If the disk
which is inserted into the disk drive is formatted
under systems other than VAX/VMS, WRITE
PROTECT the disk to protect that data.

Obtain the console prompt, >>>, as described in Chapter 2.
NOTE
After

xx.yy, a
CTRL/C may be typed since all microcode needed
to execute CRDs is loaded.
7.
>>>T

the console prints VERSION

Invoke AUTO mode by typing T to the console prompt as shown below:
<CR>

NOTE
When the command, >>>T, is typed, there is a time

span of approximately 35 seconds before the first
message is printed on the console terminal.

If no errors are encountered, the console terminal produces a printout similar to that in Example
7-2.

7.3.2 AUTO Mode Messages .
Messages normally seen while executing the diagnostic programs are replaced in the AUTO mode with
plain English messages. These consist of progress messages, warning messages, and error messages.
Progress messages are printed to assure the user that the AUTO mode CRD is progressing properly. These
messages are printed when device testing is begun and completed (Example 7-2).

BEGIN VAX-11/730,725 AUTO TEST

VERSION

CPU

x.x

PART

RUN

TIME

APPROXIMATELY

*kxxx’

15:00

MINUTES

TESTING

STARTED

RUN

TIME

= 3:30

PASSED

TESTING

STARTED

RUN

TIME

1:30

PASSED

TESTING

STARTED

RUN

TIME

= 0:45

PASSED

TESTING

STARTED
==

RUN

TIME

1:45

TESTING

STARTED

RUN

TIME

4:00

PASSED

RC25 PART 1

DAAO TESTING STARTED -- RUN TIME = 0:30

PASSED

RC25

DAAO

1:00

PASSED

DAA1T TESTING STARTED ;- RUN TIME= 1:00

PASSED

MEMORY
CPU

PART

FPA
FPA

NOT

AVAILABLE

PASSED

CPU

PART

RCF25
AUTO

TEST

xxk*

END

MODE

COMPLETE

OF
is

TESTING

Example 7-2

RUN

TIME

ERRORS

VAX-11/730,725
entered

STARTED

AUTO

this

TEST

*x*x

point.

AUTO Mode Testing Sequence (No Errors Encountered)

Warning messages are printed to inform the user that the system is improperly set up (Example 7-1).

These messages are printed in the following situations:
1.

The user disk drive does not contain the proper diagnostic disk cartridge.

The user (removable) and system (fixed) disk drives are off-line (RUN switch not activated).

The system disk drive is WRITE PROTECTed.

The diagnostic tape in the TUS8 tape drive has missing or corrupted diagnostic program files.

After printing warning messages, AUTO mode handles each of the above situations differently. AUTO

mode pauses for the first two situations above to allow the user to properly set up the disk drive (Example
7-1). However, for the third and fourth situations, AUTO mode continues testing after printing a warning
message indicating that testing is incomplete. AUTO mode executes the appropriate macrodiagnosticin
NOWRITE mode for the third situation (Example 7-3). AUTO mode handles the fourth situation as an
error and aborts further testing (Example 7-4).
Error messages are printed when an error occurs during diagnostic testing. These messages identify the

device that caused the error and the next action to be taken by the user. For more error information, refer

to Section 7.3.3.

7-4

*kk*k

VERSION
CPU

BEGIN
x.x RUN

PART

VAX-11/730,725 AUTO TEST
TIME APPROXIMATELY 15:00

MEMORY
CPU

PART

FPA
CPU

PART

* k k%

MINUTES

TESTING

STARTED

RUN

TIME

3:30

PASSED

TESTING

STARTED

=--

RUN

TIME

1:30

PASSED

TESTING

STARTED

RUN

TIME

0:45

PASSED

TESTING

STARTED

RUN

TIME

1:45

PASSED

TESTING

STARTED

RUN

TIME

4:00

PASSED

RC25

PART

DAAO

TESTING

STARTED

RUN

TIME

0:30

PASSED

RC25

PART

DAAQD

TESTING

STARTED

RUN

TIME

1:00

PASSED

RCF25

DAA1 TESTING STARTED -- RUN TIME = 1:00

* %

**x

UNIT

DAA1:

AUTO

DISK

TEST

WRITE-PROTECTED

DRIVE

TESTING

INCOMPLETE

* %

INCOMPLETE

ERRORS

CHECK DEVICE PREPARATION -- IF OK, THEN CALL
*kx*x END OF VAX-11/730,725 AUTO TEST *x**x*

Example 7-3

* % % %
VERSION

BEGIN
x.x RUN

FIELD

SERVICE
-

AUTO Mode Testing Sequence (DAA1 WRITE-PROTECTed)

VAX-11/730,725 AUTO TEST
TIME APPROXIMATELY 15:00

* %k k %
MINUTES

CPU PART 1

TESTING STARTED == RUN TIME = 3:30

PASSED

MEMORY

TESTING

STARTED

RUN

TIME

1:30

PASSED

TESTING

STARTED

RUN

TIME

0:45

PASSED

DRIVE

CPU

PART

PROPER

CHECK

SET

AUTO

TEST

xxx%

END

SETUP

REQUIRED

DIAGNOSTIC

CORRECT,

TAPE

CANNOT

INSERTED

POSSIBLE

CONTINUE
IN

TUS58

TAPE

DRIVE

AUTO

TEST

* %

PROBLEM

*=*

ABORTED

Example 7-4

VAX-11/730,

725

#**%*

AUTO Mode Testing Sequence (Missing a Microdiagnostic Program File)

7-5

7.3.3

AUTO Mode Errors

Errors detected during AUTO mode cause an error message to be printed and the current diagnostic test

to be aborted. Also, depending on which diagnostic test detected the error, AUTO mode aborts. If errors
are detected during microdiagnostic or level 4 diagnostic testing, the program that detected the error along

with the remaining test programs are aborted (Example 7-5). Also, if microdiagnostics attempt to test a
device that is missing (other than the FPA), AUTO mode is aborted. By contrast, errors detected during
macrodiagnostic testing of a device abort only that program and not any other programs that test the

device. AUTO mode then proceeds with execution of the remaining diagnostic programs (Example 7-6).
However, there are some situations where AUTO mode will abort:
¢

Errors encountered in the diagnostic disk drive

Improper system setup (for example, if the programs to be executed cannot be found on the

diagnostic disk)

When AUTO mode testing is aborted due to microdiagnostic errors or AUTO mode completes with
macrodiagnostic errors, the user has the option of restarting the AUTO mode testing or returning to the

console I/O mode (Example 7-5). This is announced to the user after completion of testing.

* % %k

BEGIN

VERSION

CPU

x.x

PART

RUN

VAX-11/730,725
TIME

TESTING

MEMORY
CPU

PART

FPA
CPU

PART

TIME

RUN

PASSED

TESTING STARTED =-- RUN TIME = 1:30

PASSED.

TESTING

STARTED

RUN

TIME

0:45

PASSED

TESTING

STARTED

=--

RUN

TIME

1:45

PASSED

TESTING

STARTED

RUN

TIME

4:00

*FAILLEDx*

ABORTED

CPU

ENTER

RETURN

CONSOLE,

*xxx

END

Example 7-5

* % % %
MINUTES

3:30

TEST

TEST
15:00

STARTED

AUTO

APPROXIMATELY

BAD

VAX-11/730,725

-2

AUTO

CALL
TO

FIELD

RESTART

TEST

SERVICE
AUTO

TEST

**x*x*

AUTO Mode Testing Sequence (Error Detected during Microdiagnostic Testing)

7.4 MENU MODE
MENU mode is invoked for system testing by one of the following methods:
1.

Automatically at the successful completion of AUTO mode

Manually with the console I/O mode command, T/M

Manually with the diagnostic supervisor command, CRD

In the first of the above methods, MENU mode is invoked once AUTO mode testing has successfully
completed. In this method, MENU mode testing is started without operator intervention, but further
system preparation may be required if options are added to the minimum system configuration.

7-6

* ke K

VERSION

CPU

BEGIN VAX-11/730,725 AUTO TEST

x.x

PART

RUN

TIME

APPROXIMATELY

¥ KkK

15:00

MINUTES

TESTING

STARTED

RUN

TIME

3:30

PASSED

TESTING

STARTED

RUN

TIME

1:30

PASSED

TESTING

STARTED

RUN

TIME

0:45

PASSED

FPA

TESTING

STARTED

RUN

TIME

1:30

PASSED

CPU PART 3

TESTING STARTED =--

RUN

TIME

4:00

PASSED

MEMORY

CPU

PART

RC25

PART

DAAD

TESTING

STARTED

RUN

TIME

0:30

PASSED

RC25

PART

DAAD

TESTING

STARTED

RUN

TIME

1:00

*FAILEDX*

DAA1

TESTING

STARTED

RUN

TIME

1:00

PASSED

RCF25
AUTO

TEST

*kk%x

END

COMPLETE

Example 7-6

DAAO

VAX-11/730,725

BAD

AUTO

CALL

TEST

FIELD

SERVICE

**x*x%

AUTO Mode Testing Sequence (Error Detected during Microdiagnostic Testing)

7.4.1
MENU Mode Evocation
MENU mode is invoked after the ‘“base” system is fully prepared. Prepare the ‘“base” system by
performing the following steps:

Insert TUS8 tape cartridge #34, labeled VAX 11725/730 CONSOLE, into the TUS8 tape
drive 1.

Insert TUSS8 tape cartridge #36, labeled 11725/730 MICRODIAG, into the TUS58 tape drive 0.

Press the EJECT switch to open the cartridge receiver door.

Load the diagnostic distribution disk labeled VAX 725/730 CMPLT DIAG into the disk drive,
close the receiver door, and press the RUN switch to place the drive on-line.

When the RUN indicator on the disk drive is continuously lit, proceed to the next step. This
drive and the system disk drive may or may not be WRITE-PROTECTed.
NOTE
CRD MENU mode performs nondestructive disk

testing on VAX/VMS disk cartridges. If the disk
that is inserted into the disk drive is formatted under
systems other than VAX/VMS, WRITE PROTECT the disk to protect the data.

7-7

Invoke MENU by one of the following methods:

Console 1/0 Mode Method
a.

Obtain the console prompt, >>>, as described in Chapter 2.

Type T/M in response to the console prompt as shown below:
>>>T/M<LCR>

NOTE
When the command >>>T/M is typed there is a
time span of approximately 1.5 minutes before the
first message is printed on the console terminal.
Diagnostic Supervisor Method

Obtain the diagnostic supervisor prompt DS> as described in Chapter 5.

Type CRD in response to the supervisor prompt as shown below:
DS>CRD<CR>

Whichever method is used to evoke CRD MENU mode, user control is passed to the Main

Menu which produces a printout similar to Example 7-7.

***kx

BEGIN

Type

the

VAX-11/730,725

CTRL

interrupt

key

and

Test

VAX-11/730,725
PLEASE

TEST

key

*x%x%

(together)

any

time

RUN

TIME

Processing...

HARDWARE

IDENTIFICATION

HARDWARE

IDENTIFICATION

COMPLETE

00:30

Minutes

WAIT...

VAX-11/730,725

MAIN

the

Functional

Test

Exit

Llist

preparation

Select

and

TEST

ALL

one

Type

Enter

MAIN

Test
of

identified

test

required

hardware

supported

the

above

system

for

from

hardware

test
TEST

and

support

supported

hardware

(for

example,

A),

and

choice:
Example 7-7

MENU Mode Main Menu

7-8

press

status

RETURN,

In Main Menu, selections are provided to allow the user to perform the following functions:
e

Exit from MENU mode.

Print a list of devices on the system and determine whether they are supported.

Print the preparation required to test the available devices.

Select either a single device or all devices on the system for diagnostic testing.

Choice A:

If choice A is selected, MENU mode is aborted and user control is returned to the console I/O mode
(Example 7-8).

!
!
Type

one

Enter

TEST

x*kxx

END

706

MAIN

the

STOPPED

RETURNING

above

(for

choice:

example,

A),

and

press

RETURN,

OPERATOR

VAX-11/730,725
VAX-11/730,725

TEST

**x*x%

CONSOLE,

WAIT

FOR

'>>>'

PROMPT...

PC=0001E822

>>>

Example 7-8

MENU Mode: Choice A Selected from Main Menu

Choice B:

If choice B is selected, MENU mode prints a list of devices available on the system (Example 7-9). This
list also includes the device generic name and determines if the device is supported for testing. After this
list is printed, the Main Menu is printed again.
Choice C:

If choice C is selected, MENU Mode prints a list of the system preparations required to test the supported
devices on the system (Example 7-10). After this list is printed, the Main Menu is printed again.

Type

one

Enter

the

MAIN

above

choice:

and

press

Generic

Support
Status

Console

CSAQ

DW730

DWO

Support

LESI

DAA

Support

DMF32S

XGAQO

Supported

DMF32A

TXA

Supported

DMF32P
RC25

LCA

Supported

DAAQ

Supported

MAIN

Supported

DAA1

LEnd

Main

the

Llist]

Menu)
MENU Mode: Choice B Selected from Main Menu

above

(for

choice:

KA730,

Preparation:

Hardware:

RC25,

Preparation:

example,

DMF32A,

hardware

press

DMF32P,

RETURN,

DMF32S

preparation

Insert

removable

Push

Pull

out

Wait
CEnd

Main

and

required

RCF25

switch

A),

Hardware:

(return

RETURN,

Name

Example 7-9

Enter

A),

Hardware

(return

one

example,

Name

RCF25

Type

(for

RUN

disk

Write-protect

(not

drive

switch
REMOVE

for RUN indicator
of Llistl

stop

Menu)

Example 7-10

MENU Mode: Choice C Selected from Main Menu

7-10

and

FIXED

Llighted)
blinking

Choice D:

If choice D is selected, user control is passed to Test Menu, which produces a printout similar to Example
7-11. This menu lists the devices that can be tested. To test a device, type the menu choice that
corresponds to the device to be tested (that is, typing choice D1 causes the MENU mode to test all
supported devices). See Example 7-12.

Type

one

the

Main

Enter

TEST

above

(for

choice:

example,

and

press

RETURN,

KA730

CPU

KAQO

RC25

DISK

DAAO

RCF25

DISK

DAA1

DMF32S

COMM.

XGAOQ

DMF32A

COMM.

TXA

DMF32P

COMM.

LCA

TEST

Type

A),

one

ALL

the

above

(for

RETURN

start

testing.

Enter

TEST

choice:

Example 7-11

supported

example,

hardware

A1), and

press

MENU Mode: Choice D Selected from Main Menu

Example 7-12 is a typical functional test printout produced by MENU mode. This printout indicates to
the user which device is currently being tested, the time spent to test that device, and at the end of the test,
whether the device passed or failed. At the completion of testing, MENU mode returns control to the
Main Menu.

7-11

Type

one

the

start

testing.

Enter

TEST

Press

the

any

CTRL

time

kkkkkkkkkkx

above

(for

choice:

key

and

type

interrupt

BEGIN

RUN

15:00

A1),

key

and

press

RETURN

(together)

Test...

TESTING

*kkkkkkkkx

MINUTES

KA730

PART

KAO

MINUTES

PASSED

KA730

PART

KADO TESTING STARTED -- RUN TIME = 02:00 MINUTES

PASSED

KA730

PART

KAO

TESTING

STARTED

=-- RUN

TIME =

02:45

MINUTES

PASSED

KA730

PART

KAO

TESTING

STARTED

=--

RUN

TIME

02:00

MINUTES

PASSED

KA730

PART

KAO

TESTING

STARTED

RUN

TIME

03:00

MINUTES

PASSED

RC25

PART

DAAO

TESTING

STARTED

RUN

TIME

00:30

MINUTES

PASSED

RC25

PART

DAAO

TESTING

STARTED

RUN

TIME

01:00

MINUTES

PASSED

DAA1T TESTING STARTED -- RUN TIME = 01:00 MINUTES

PASSED

XGAO TESTING STARTED =-- RUN TIME = 01:00 MINUTES

PASSED

RCF25

TESTING

the

Functional

FUNCTIONAL

TIME

example,

STARTED

=--

RUN

TIME

00:45

DMF32S

COMM.

DMF32A

COMM.

TXA

TESTING

STARTED

RUN

TIME

00:30

MINUTES

PASSED

DMF32P

COMM,

LCA

TESTING

STARTED

RUN

TIME

00:30

MINUTES

PASSED

FUNCTIONAL

TESTING

(return

Main

COMPLETE

ERRORS

Menu)

Example 7-12 MENU Mode Successful Testing Sequence: Choice D Selectéd from Test Menu

MENU Mode can be interrupted or suspended at any time by typing CTRL/C. This causes a menu to be

printed (Example 7-13), giving the user a choice of three actions to take. If choice A is selected, the Exit
message 1s printed (Example 7-8) and MENU mode exits, returning control to the console I/O mode.

Selecting choice B aborts whatever MENU Mode process was being performed at the time of the
CTRL/C, and returns control to the Main Menu (Example 7-7). Conversely, if choice C is selected, the
MENU Mode process interrupted by the CTRL/C continues.

Press

the

CONTROL

key

and

type

Test

the

key

together

CONTROL- MENU
A

Exit

Abort the current process, and
Resume the process interrupted

Type

Enter

one

the

CONTROL-C

above

(for

choice:

Example 7-13

7.4.2

return

example,

MAIN

CONTROL-C

A),

and press

RETURN.

CONTROL-C Menu

MENU Mode Errors

Errors detected during device testing are listed on the functional test printout (similar to Example 7-14) as
having failed the test (FAILED). Also, at the end of the functional test printout, the failed device is called
out by its generic name.
When the device diagnostic test detects an error, that test is aborted (printing FAILED) and the next test
is executed. Once all the selected devices are tested, control is passed back to Main Menu.

fype one of the above (for example, A1),
start

testing.

Enter

TEST

Press

the CTRL

any

time

khkkkkkkkkx

type

interrupt

BEGIN
RUN

and

the

15:00

MINUTES

PASSED

STARTED

RUN

TIME

02:00

MINUTES

PASSED

TESTING

STARTED

RUN

TIME

02:45

MINUTES

PASSED

KAQO

TESTING

STARTED

RUN

TIME

02:00

MINUTES

PASSED

KAQO

TESTING

STARTED

RUN

TIME

03:00

MINUTES

PASSED

DAAD

TESTING

STARTED

RUN

TIME

00:30

MINUTES

PASSED

DAAOD

TESTING

STARTED

RUN

TIME

01:00

MINUTES

PASSED

TESTING

PART

KAO

KA730

PART

KA730

PART

RC25

PART

RC25

PART

*xkkkkkkkk

MINUTES

KAQO

KA730

(together)

Test...

00:45

PART

TIME

STARTED

KA730

RETURN

RUN

TESTING

PART

key

TESTING

KAQO

KA730

Functional

FUNCTIONAL

TIME

press

choice:

key

and

7-13

RCF25

DAA1

TESTING

STARTED

=--

RUN

TIME

01:00

MINUTES

*FAILED*

DMF32S

COMM.

XGAO

TESTING

STARTED

RUN

TIME

01:00

MINUTES

*FAILED*

DMF32A

COMM.

TXA

TESTING

STARTED

=--

RUN

TIME

00:30

MINUTES

PASSED

DMF32P

COMM.

LCA

TESTING

STARTED

RUN

TIME

00:30

MINUTES

PASSED

FUNCTIONAL

FAILED

CALL

TESTING

HARDWARE

FIELD

(return

Example 7-14

TESTING:

SERVICE

Main

INCOMPLETE
XGAO,

ERRORS

DAA1

#*x*

Menu)

Unsuccessful MENU Mode Testing Sequence: Choice D1 Selected from Test Menu

7-14

CHAPTER 8

BUILDING AND UPDATING THE SYSTEM DISK DIAGNOSTIC AREA

8.1

INTRODUCTION

The VAX-11/725 is shipped with an RC25 diagnostic distribution disk cartridge. This FILES-11 structured diagnostic distribution media is labeled VAX 11725/730 CMPLT DIAG. This media contains all
microdiagnostic programs appropriate to the VAX-11/725 system.

Because the diagnostic area of a newly created system disk contains no diagnostic programs, selected
diagnostic programs from the distribution media are copied to this area. These selected diagnostic
programs are those programs that test the devices on the VAX-11/725 system on which the programs
reside. The process of copying diagnostic programs to the system disk diagnostic area is referred to as
building the diagnostic area.
NOTE
If the system disk does not contain sufficient room
for the selected diagnostic programs, the diagnostic
programs should remain on the distribution media.

Digital Equipment Corporation periodically releases new versions of existing diagnostic programs and, in
some cases, may release entirely new diagnostic programs. When new versions or entirely new diagnostic
programs are released for devices on a VAX-11/725 system, then these diagnostic programs are copied to
the diagnostic area of the system disk (if diagnostic programs reside there). The process of copying these
diagnostic programs to the diagnostic area is referred to as updating.
8.2 BUILDING AND UPDATING THE DIAGNOSTIC AREA
Building the diagnostic area of the system disk is accomplished under control of the operating system using
one of two methods:
e

Using the COPY command

Using the Diagnostic Update Configuration Tool (DUCT)

Updating the diagnostic is accomplished under control of the operating system using DUCT.
8.2.1 Building and Updating the Diagnostic Area with the COPY Command
To build the diagnostic area on the system disk perform the following procedure:

1.
2.

Ensure that VMS is executing properly and the DCL prompt, $, is displayed on the terminal.
Ensure that the diagnostic distribution media, labeled VAX 11725/730 CMPLT DIAG, is
loaded or mounted onto the drive.

Place the drive containing the diagnostic distribution media on-line by pressing the RUN switch

on that drive.

8-1

When the RUN indicator stops blinking, type the following command at the “$” prompt to

mount the diagnostic distribution cartridge.

$MOUNT

DAAO:

CRDPACK

Type one of the following commands at the “$”’ prompt to copy all selected diagnostic program

files to the system disk.
$COPY

DAAT1:[SYSMAINT]filename.ext

SYSEMAINTENANCE

Filename.ext is the name of the diagnostic program file to be copied to the system disk
maintenance area.
$COPY

DAAT:[SYSMAINTI*.%x;

SYSSMAINTENANCE

This copies all diagnostic programs file to the system disk maintenance area.
Type the following commands to make the system disk maintenance area bootable:
$COPY/CONTIG
$PURGE

DAAT:[SYSMAINTIDIAGBCOT.EXE

DAAT:[SYSMAINT]*.*x;(

DUA1:[SYSMAINTIDIAGBOCOT.EXE

NOTE
.
SYSSMAINTENANCE is the logical name for the
diagnostic area on the system disk drive.
8.2.2

Building and Updating the Diagnostic Area with DUCT
DUCT is a copying utility that copies diagnostic files from the distribution media to the diagnostic area on
the system disk. DUCT copies diagnostic files from tapes or disks. To use DUCT, perform the following
procedure:
1.

Ensure that VMS is executing properly and that the DCL prompt $ is displayed on the terminal.

Ensure that the diagnostic distribution media labeled VAX 11725/730 CMPLT DIAG, is
loaded or mounted onto the drive.
|
Place the drive containing the diagnostic distribution media on-line by pressing the LOAD

button on that drive.

At the § prompt, type the following command to mount the diagnostic distribution cartridge:
$MCUNT

DAAQ:

CRDPACK

Type the following command at the $ prompt to execute DUCT from the distribution media:
$RUN

DAAC:[SYSMAINTIDUCT.EXE

When DUCT prints the menu below (shown in Example 8-1), type the HELP command and
follow the instructions to either build or update the system diagnostic area.

8-2

Select

one

the

following

diagnostic

for

Initialize

for

New

add

for

Update

for

Query

the

for

Verify

for

Execution

for

Exit

for

Help

Example 8-1

option

entries:

account

diagnostic