KA660 CPU System Maintenance Order Number EK–398AA–MM–001 Digital Equipment Corporation Maynard, Massachusetts

KA660 CPU System Maintenance Order Number EK–398AA–MM–001 Digital Equipment Corporation Maynard, Massachusetts

KA660 CPU System Maintenance

Order Number EK–398AA–MM–001

Digital Equipment Corporation

Maynard, Massachusetts

First Printing, December 1990

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.

The software, if any, described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software or equipment that is not supplied by Digital Equipment

Corporation or its affiliated companies.

Restricted Rights: Use, duplication or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer

Software clause at DFARS 252.227–7013.

© Digital Equipment Corporation 1990. All rights reserved.

Printed in U.S.A.

The Reader’s Comments form at the end of this document requests your critical evaluation to assist in preparing future documentation.

The following are trademarks of Digital Equipment Corporation: CompacTape, CX, DDCMP,

DEC, DECconnect, DECdirect, DECnet, DECscan, DECserver, DECUS, DECwindows,

DELNI, DEMPR, DESQA, DESTA, DSRVB, DSSI, IVAX, KDA, KLESI, MicroVAX, MSCP,

Q-bus, Q22-bus, RA, RQDX, RRD40, SDI, ThinWire, TK, TMSCP, TQK50, TQK70, TSV05,

TU, UNIBUS, VAX, VAX 4000, VAX DOCUMENT, VAXcluster, VAXELN, VAXlab, VAXserver,

VMS, VT, and the DIGITAL logo.

FCC NOTICE:

The equipment described in this manual generates, uses, and may emit radio frequency energy. The equipment has been type tested and found to comply with the limits for a Class A computing device pursuant to Subpart J of Part 15 of FCC Rules, which are designed to provide reasonable protection against such radio frequency interference when operated in a commercial environment. Operation of this equipment in a residential area may cause interference, in which case the user at his own expense may be required to take measures to correct the interference.

S1599

This document was prepared using VAX DOCUMENT, Version 1.2.

Contents

Preface

ix

Chapter 1 KA660 CPU and Memory Subsystem

1.1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–1

1.2

KA660 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–2

1.2.1

SOC Chip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–3

1.2.2

Clock Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–4

1.2.3

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

1–4

1.2.4

Cache Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–4

1.2.5

Memory Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–4

1.2.6

MicroVAX System Support Functions . . . . . . . . . . . . . . . .

1–5

1.2.7

1.2.8

Resident Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–5

Q22-Bus Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–6

1.2.9

KA660 Ethernet Interface . . . . . . . . . . . . . . . . . . . . . . . . .

1–6

1.2.10

KA660 DSSI Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–6

1.3

CPU Cover Panel (H3602–00) . . . . . . . . . . . . . . . . . . . . . . . .

1–9

1.4

MS650–Bn Memory Modules . . . . . . . . . . . . . . . . . . . . . . . . . 1–10

1.5

RF-Series ISE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–11

Chapter 2 Configuration

2.1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–1

2.2

General Module Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–1

2.2.1

Module Order for KA660 Systems . . . . . . . . . . . . . . . . . . .

2–2

2.3

Module Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–3

2.4

DSSI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–4

2.4.1

DSSI Cabling for the BA215 Enclosure . . . . . . . . . . . . . . .

2–5

2.4.1.1

DSSI Bus Termination and Length . . . . . . . . . . . . . . . .

2–6

2.4.2

Dual-Host Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–6

iii

2.4.3

Dual-Host Configuration . . . . . . . . . . . . . . . . . . . . . . . . . .

2–7

2.5

Configuration Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–7

Chapter 3 KA660 Firmware

3.1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3–1

3.2

KA660 Firmware Features . . . . . . . . . . . . . . . . . . . . . . . . . . .

3–1

3.3

Halt Entry and Dispatch Code . . . . . . . . . . . . . . . . . . . . . . . .

3–2

3.4

External Halts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3–3

3.5

Power-Up Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3–4

3.5.0.1

3.5.0.2

Mode Switch Set to Test . . . . . . . . . . . . . . . . . . . . . . . . .

Mode Switch Set to Language Inquiry . . . . . . . . . . . . . .

3–4

3–5

3.5.0.3

Mode Switch Set to Normal . . . . . . . . . . . . . . . . . . . . . .

3–6

3.6

Bootstrap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3–7

3.7

Operating System Restart . . . . . . . . . . . . . . . . . . . . . . . . . . .

3–8

3.7.1

Locating the RPB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3–9

3.8

Console I/O Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3–9

3.8.1

Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3–9

3.8.2

3.8.3

3.8.4

Address Specifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–11

Symbolic Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–11

Console Command Qualifiers . . . . . . . . . . . . . . . . . . . . . . . 3–15

3.8.5

Console Command Keywords . . . . . . . . . . . . . . . . . . . . . . . 3–16

3.9

Console Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–18

3.9.1

3.9.1.1

BOOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–18

Supported Boot Devices . . . . . . . . . . . . . . . . . . . . . . . . . 3–20

3.9.1.2

3.9.2

3.9.3

3.9.4

Boot Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–20

CONFIGURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–22

CONTINUE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–24

DEPOSIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–24

3.9.5

3.9.6

3.9.7

3.9.8

EXAMINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–25

FIND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–26

HALT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–27

HELP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–27

3.9.9

INITIALIZE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–29

3.9.10

MOVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–30

3.9.11

NEXT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–31

iv

3.9.12

REPEAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–32

3.9.13

SEARCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–33

3.9.14

SET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–35

3.9.15

SHOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–39

3.9.16

START . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–43

3.9.17

TEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–44

3.9.18

UNJAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–47

3.9.19

X—Binary Load and Unload . . . . . . . . . . . . . . . . . . . . . . . 3–47

3.9.20

!—Comment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–49

Chapter 4 Troubleshooting and Diagnostics

4.1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4–1

4.2

General Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4–1

4.3

KA660 ROM-Based Diagnostics . . . . . . . . . . . . . . . . . . . . . . .

4–2

4.3.1

Diagnostic Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4–3

4.3.2

Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4–6

4.3.3

User Created Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4–7

4.3.4

Console Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–10

4.3.5

System Halt Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–27

4.3.6

Console Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–28

4.3.7

VMB Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–29

4.4

Acceptance Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–30

4.5

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–36

4.5.1

FE Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–36

4.5.2

4.5.3

Isolating Memory Failures . . . . . . . . . . . . . . . . . . . . . . . . . 4–37

Additional Troubleshooting Suggestions . . . . . . . . . . . . . . . 4–40

4.6

Loopback Tests and Fuse Problems . . . . . . . . . . . . . . . . . . . . 4–41

4.6.1

Testing the Console Port . . . . . . . . . . . . . . . . . . . . . . . . . . 4–42

4.7

Module Self-Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–42

4.8

ISE Troubleshooting and Diagnostics . . . . . . . . . . . . . . . . . . . 4–44

4.8.1

4.8.2

DRVTST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–46

DRVEXR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–46

4.8.3

4.8.4

HISTRY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–48

ERASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–49

v

4.8.5

PARAMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–50

4.8.5.1

EXIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–50

4.8.5.2

4.8.5.3

HELP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–50

SET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–50

4.8.5.4

4.8.5.5

SHOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–51

STATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–51

4.8.5.6

WRITE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–51

4.9

Diagnostic Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–52

Appendix A KA660 CPU Address Assignments

A.1

KA660 Physical Address Space . . . . . . . . . . . . . . . . . . . . . . .

A–1

A.2

KA660 Detailed Physical Address Map . . . . . . . . . . . . . . . . .

A–3

A.3

External and Internal Processor Registers . . . . . . . . . . . . . . .

A–9

A.4

Global Q22-Bus Physical Address Space . . . . . . . . . . . . . . . . A–10

Appendix B Programming Parameters for RF-Series ISEs

B.1

RF-Series ISE Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . .

B–1

B.2

Entering the DUP Driver Utility . . . . . . . . . . . . . . . . . . . . . .

B–6

B.3

Setting Allocation Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B–7

B.4

Setting Unit Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B–8

B.5

Setting Node Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–10

B.6

Setting System ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–10

B.7

Exiting the DUP Server Utility . . . . . . . . . . . . . . . . . . . . . . . B–11

Index

Examples

3–1 Language Selection Menu . . . . . . . . . . . . . . . . . . . . . . . . . . .

3–6

4–1 Creating a Script with Utility 9F . . . . . . . . . . . . . . . . . . . . . .

4–9

4–2 Listing and Repeating Tests with Utility 9F . . . . . . . . . . . . . 4–10

4–3 Console Display (No Errors) . . . . . . . . . . . . . . . . . . . . . . . . . . 4–10

4–4 Sample Output with Errors . . . . . . . . . . . . . . . . . . . . . . . . . . 4–11

4–5 T 9C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–39

vi

B–1 SHOW DSSI Display (Embedded DSSI) . . . . . . . . . . . . . . . . .

B–5

B–2 SHOW UQSSP Display (KFQSA-Based DSSI) . . . . . . . . . . . .

B–6

B–3 Starting the DUP Driver Utility (Embedded DSSI) . . . . . . . .

B–7

B–4 Starting the DUP Driver Utility (KFQSA-Based DSSI) . . . . .

B–7

B–5 Setting Allocation Class for a Specified ISE . . . . . . . . . . . . . .

B–8

B–6 Setting a Unit Number for a Specified ISE . . . . . . . . . . . . . .

B–9

B–7 Changing a Node Name for a Specified ISE . . . . . . . . . . . . . . B–10

B–8 Changing a System ID for a Specified ISE . . . . . . . . . . . . . . . B–11

B–9 Exiting the DUP Driver Utility for a Specified ISE . . . . . . . . B–12

B–10 SHOW DSSI Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–12

B–11 SHOW UQSSP Display (KFQSA-Based DSSI) . . . . . . . . . . . . B–13

Figures

1–1 KA660 CPU Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–2

1–2 KA660 System CPU Block Diagram . . . . . . . . . . . . . . . . . . . .

1–7

1–3 CPU Cover Panel (H3602–00) . . . . . . . . . . . . . . . . . . . . . . . . 1–10

2–1 VAX 4000 Model 200 (BA430) Configuration Worksheet . . . . 2–10

2–2 VAX 4000 Model 200 (BA215) Configuration Worksheet . . . . 2–11

4–1 KA660 CPU Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–14

B–1 Attaching a Unit Number Label to the ISE Front Panel . . . .

B–9

Tables

2–1 ISE DIP Switch Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–4

2–2 Setting the KA660 Node ID . . . . . . . . . . . . . . . . . . . . . . . . . .

2–5

2–3 KA660 Power and Bus Loads . . . . . . . . . . . . . . . . . . . . . . . . .

2–8

3–1 Halt Action Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3–3

3–2 Language Inquiry on Power-Up or Reset . . . . . . . . . . . . . . . .

3–6

3–3 Console I/O Mode Special Characters . . . . . . . . . . . . . . . . . . . 3–10

3–4 Console Symbolic Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . 3–12

3–5 Symbolic Addresses Used in Any Address Space . . . . . . . . . . 3–14

3–6 Console Command Qualifiers . . . . . . . . . . . . . . . . . . . . . . . . . 3–15

3–7 Command Keywords by Type . . . . . . . . . . . . . . . . . . . . . . . . . 3–16

3–8 Console Command Summary . . . . . . . . . . . . . . . . . . . . . . . . . 3–17

3–9 VMB Boot Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–19

3–10 Boot Device Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–21

vii

4–1 Test and Utility Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . .

4–4

4–2 Scripts Available to Customer Services . . . . . . . . . . . . . . . . .

4–7

4–3 Values Saved, Machine Check Exception During EF . . . . . . . 4–12

4–4 Values Saved, Exception During Executive . . . . . . . . . . . . . . 4–13

4–5 KA660 Console Displays and FRU Pointers . . . . . . . . . . . . . 4–15

4–6 System Halt Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–27

4–7 Console Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–28

4–8 VMB Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–29

4–9 KA660 Fuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–41

4–10 Loopback Connectors for Q22-Bus Devices . . . . . . . . . . . . . . . 4–43

4–11 DRVTST Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–46

4–12 DRVEXR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–47

4–13 HISTRY Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–48

4–14 ERASE Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–49

4–15 ISE Diagnostic Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . 4–52

A–1 General Local Address Space Map . . . . . . . . . . . . . . . . . . . . .

A–2

A–2 Detailed Local Address Space Map . . . . . . . . . . . . . . . . . . . .

A–3

A–3 External, Internal Processor Registers . . . . . . . . . . . . . . . . . .

A–9

A–4 Global Q22-bus Physical Address Map . . . . . . . . . . . . . . . . . . A–10

B–1 How the VMS Operating System Identifies the ISEs . . . . . . .

B–4

viii

Preface

This guide describes the base system, configuration, ROM-based diagnostics, and troubleshooting procedures for systems containing the

KA660 CPU.

Intended Audience

This guide is intended for use by Digital Customer Services personnel and qualified self-maintenance customers.

Organization

This guide has four chapters and two appendixes, as follows:

Chapter 1 describes the KA660/MS650–Bn CPU and memory subsystem, and the RF-series Integrated Storage Elements (ISEs).

Chapter 2 contains system configuration guidelines, and provides a table listing current, power, and bus loads for supported options. It also describes the Digital Storage Systems Interconnect (DSSI) bus interface cabling between the RF-series ISEs, CPU, the CPU I/O panel, and the system control panel (SCP). (The control panel is known as the SCP on the BA430 enclosure and as the operator control panel (OCP) on the BA215 enclosure.)

Chapter 3 describes the firmware that resides in ROM on the KA660, and provides a list of console error messages and their meaning.

Chapter 4 describes the KA660 diagnostics and the diagnostics that reside on the RF-series ISEs.

Appendix A lists the KA660 address space.

Appendix B describes procedures for setting parameters on an ISE.

ix

Conventions

The following conventions are used in this manual:

Convention Meaning

Key

Ctrl/C

BOLD

A symbol denoting a terminal key used in text and examples in this book.

For example,

Break indicates that you press the Break key on your terminal keypad.

Return indicates that you press the Return key on your terminal keypad.

A symbol indicating that you hold down the Ctrl key while you press the

C key.

This bold type indicates user input. For example:

>>>

BOOT MUA0

This line shows that the user must type BOOT MUA0 at the console prompt.

NOTE

CAUTION

WARNING

Provides general information about the current topic.

Provides information to prevent damage to equipment or software.

Provides information to prevent personal injury.

The following are qualifier and argument conventions:

[ ]

{}

an optional qualifier or argument a required qualifier or argument

x

Chapter 1

KA660 CPU and Memory Subsystem

1.1 Introduction

This chapter describes the KA660 CPU (Figure 1–1). The KA660 is a quad-height VAX processor module for the Q22-bus (extended LSI–11 bus). It is designed for use in high-speed, real-time applications and for multiuser, multitasking environments. The KA660 employs a cache memory to maximize performance.

There are two variants: the KA660–AA, which runs multiuser software; and the KA660–BA, which runs single-user software.

The KA660 is the CPU of the VAX 4000 Model 200, which is housed in either a BA430 or a BA215 enclosure. Refer to the

BA430/BA440 Enclosure

Maintenance

manual.

CAUTION:

Static electricity can damage integrated circuits. Always use a grounded wrist strap (PN 29–11762–00) and grounded work surface when working with the internal parts of a computer system.

The KA660 CPU module and MS650–Bn memory modules combine to form a VAX CPU and memory subsystem that can use the on-board DSSI and

Ethernet busses and the Q22-bus to communicate with I/O devices. The

KA660 and MS650–Bn modules mount in standard Q22-bus backplane slots that implement the Q22-bus in the AB rows and the CD interconnect in the

CD rows. The KA660 can support up to four MS650–Bn modules, if enough

Q22/CD slots are available.

The KA660 communicates with the console device through the CPU cover panel (H3602–00), which also contains configuration switches and an LED display. The H3602–00 is described in Section 1.3.

KA660 CPU and Memory Subsystem

1–1

Figure 1–1: KA660 CPU Module

DSSI Memory J2

E28

D14

F3 E33

E27

Y4

DSSI

Termination

E31

DC542

E35

SHAC

E30

E29

W3

W2

W1

Y3

DC541

E18

SGEC

Console J1

E22

E12

High Byte

E19

E5

E4

F2 F1

E6

Low Byte

Y2

DC511

E2

SSC

DC557

E32

CMCTL

DC222

E23

SOC

DC527

E11

CQBIC

MLO-005867

1.2 KA660 Features

The major features of the KA660 CPU are listed below.

• The VAX central processor, which is implemented in a VLSI chip called the SOC, achieves a 35-ns microcycle and a 70-ns bus cycle at an operating frequency of 114 MHz. It supports full VAX memory management with demand paging and a 4-Gbyte virtual address space.

The SOC includes a floating-point accelerator with the MicroVAX chip subset of the VAX floating-point instruction set and data types.

• A console port compatible with the VAX processor whose baud rate can be set through an internal switch on the CPU cover panel.

1–2

KA660 CPU System Maintenance

• A set of processor clock registers that support:

– A VAX standard time-of-year (TOY) clock with support for battery backup. (Batteries are located in the CPU cover panel.)

– An interval timer with 10-ms interrupts.

– Two programmable timers, similar in function to the VAX standard interval timer.

• A boot and diagnostic facility with four on-board LEDs. This facility supports an external 4-bit display and configuration switches on the

CPU cover panel.

• 256 Kbytes of 16-bit wide ROM.

• A Q22-bus interface.

• A DSSI bus interface.

• An Ethernet interface.

1.2.1 SOC Chip

The SOC chip contains all general purpose registers (GPRs) visible to the

VAX processor, several system registers such as CCR, SCBB, the cache memory (6 Kbytes), and all memory management hardware, including a

28-entry translation buffer.

The SOC chip supports the MicroVAX chip subset of the VAX instruction set and data types, plus the following string instructions:

CMPC3

CMPC5

LOCC

MOVC3

MOVC5

SCANC

SKPC

SPANC

The SOC chip provides the following subset of the VAX data types:

Byte

Word

Longword

Quadword

Character string

Variable-length bit field

KA660 CPU and Memory Subsystem

1–3

Support for the remaining VAX data types can be provided through macrocode emulation.

1.2.2 Clock Functions

Clock functions are implemented by the SOC, which includes the clock chip,

FPA, CPU, and cache.

• Generates one auxiliary clock for other TTL logic

• Synchronizes reset signal

• Synchronizes data ready and data error signals

1.2.3 Floating-Point Accelerator

The floating-point accelerator is implemented on the SOC chip. The FPA subsystem executes the VAX f_, d_, and g_floating-point instructions (except for CLRx, MOVx, and TSTx), and accelerates the execution of MULL, DIVL, and EMUL integer instructions.

1.2.4 Cache Memory

The KA660 module incorporates a cache memory of six banks to maximize

CPU performance. The cache is implemented within the SOC chip. The cache is a 6-Kbyte, six-way associative, write-through cache memory, with a 35-ns cycle time.

1.2.5 Memory Controller

The main memory controller is implemented by a VLSI chip called the

CMCTL. The CMCTL contains approximately 25,000 transistors in a 132pin CERQUAD surface mount package. It supports ECC (error correction code) memory, with a 420-ns cycle time for longword read transfers and a

560-ns cycle time for quadword transfers. It has a 140-ns cycle time for unmasked longword writes and a 490-ns cycle time for masked longword writes.

The maximum amount of main memory supported by KA660 systems is 64 Mbytes on one to four MS650–BA or –BB (16-Mbyte or 8-Mbyte) memory modules, depending on system configuration. The MS650–Bn modules communicate with the KA660 through the MS650–Bn memory interconnect, which utilizes the CD interconnect and a 50-pin ribbon cable.

1–4

KA660 CPU System Maintenance

1.2.6 MicroVAX System Support Functions

System support functions are implemented by the System Support Chip

(SSC). The SSC contains approximately 83,000 transistors in an 84-pin

CERQUAD surface mount package. The SSC provides console and boot code support functions, operating system support functions, timers, and many extra features, including the following:

• Word-wide ROM unpacking

• 1-Kbyte battery-backed-up RAM

• Halt arbitration logic

• A console serial line

• An interval timer with 10-ms interrupts

• A VAX standard time-of-year (TOY) clock with support for battery backup

• An IORESET register

• Programmable CDAL bus timeout

• Two programmable timers

• A register for controlling the diagnostic LEDs

1.2.7 Resident Firmware

The resident firmware, arranged as words, consists of 256 Kbytes located on two 128-Kbyte x 8-bit wide EPROMs (27010). The firmware gains control when the processor halts, and contains programs that provide the following services:

• Board initialization

• Power-up self-testing of the KA660 and MS650–Bn modules

• Emulation of a subset of the VAX standard console (automatic or manual bootstrap, automatic or manual restart, and a simple command language for examining or altering the state of the processor)

• Booting from supported Q22-bus devices, DSSI devices, and Ethernet

• Multilingual capability

The firmware is described in detail in Chapter 3.

KA660 CPU and Memory Subsystem

1–5

1.2.8 Q22-Bus Interface

The Q22-bus interface is implemented by the CQBIC chip. The CQBIC chip contains approximately 40,870 transistors in a 132-pin CERQUAD surface mount package. It supports up to 16-word block mode transfers between a Q22-bus DMA device and main memory, and up to 2-word block mode transfers between the CPU and Q22-bus devices. It has a 420-ns cycle time for longword read transfers and an 560-ns cycle time for quadword read transfers. It has a 140-ns cycle time for unmasked longword writes and a 490-ns cycle time for masked longword writes. The Q22-bus interface contains the following:

• A 16-entry map cache for the 8,192-entry scatter/gather map that resides in main memory, used for translating 22-bit Q22-bus addresses into 26-bit main memory addresses

• Interrupt arbitration logic that recognizes Q22-bus interrupt requests

BR7–BR4

The Q22-bus interface handles programmed and power-up resets, and CPU halts (deassertion of DCOK).

The KA660–AA and –BA modules each contain 240-ohm termination for the Q22-bus.

1.2.9 KA660 Ethernet Interface

The KA660 features an on-board network interface implemented through a second-generation Ethernet chip (SGEC) and a 32 x 8-bit wide ROM.

This interface allows the KA660 to be connected to either a ThinWire or standard Ethernet cable through the CPU cover panel. Consult the

KA660

CPU Technical Manual

for a description.

1.2.10 KA660 DSSI Interface

See Figure 1–2 for a block diagram of the KA660 system CPU.

1–6

KA660 CPU System Maintenance

Standard

Ethernet

Ethernet

ThinWire

Console Line

RS-423

H3602

Console Panel

Battery Backup

User Interface

Switches

Ethernet

Functionality

LED Indicator

Panel

Interconnect

Memory Data Bus

Note:

Boards #2,3,4 are Optional

50-Pin

Conn.

MS650-BA

Memory Module

16 MBytes

Board #4

Board #3

Board #2

Board #1

40-Pin

Conn.

KA660

CPU Module

C-D

Fingers

A_B

Fingers

50-Pin

Conn.

C-D

Fingers

Side 1

Memory Address/Control

Note: BA430 Configuration use CD Fingers Side 1

Ba215 Configuration use 50-Pin Connector

Q-BUS

DSSI BUS

DSSI

Device

# 0

DSSI

Device

# 6

MLO-005868

The KA660 contains a Single-Host Adapter Chip (SHAC) chip that implements the Digital Storage Systems Interconnect (DSSI) bus interface.

The DSSI interface allows the KA660 to transmit packets of data to, and receive packets of data from, up to seven other DSSI devices (RF-series disk drives or a second KA660 module). The DSSI bus improves system performance for two reasons:

• It is faster than the Q22-bus.

• It relieves the Q22-bus of disk traffic, allowing more bandwidth for

Q22-bus devices.

The physical characteristics of the DSSI bus are as follows:

• 4-Mbytes-per-second bandwidth

• Distributed arbitration

• Synchronous operation

• Parity checking

• 6-meter total bus length (19.8 ft.) (includes internal and external cabling)

Configurations that exceed this length may be supported, if properly tested

• Single-ended bus transceivers

• Maximum of eight nodes (KA660 counts as one)

The KA660 CPU systems support four DSSI enclosures

• Eight data lines

• One parity line

• Eight control lines

Refer to the following sections for more information about the DSSI bus and disk drives:

Section 2.4

Section 3.9.14

Section 4.4

Section 4.8

Setting and changing DSSI node names, addresses and unit numbers, dual host configuration rules

Console SET command

DSSI drive acceptance testing

RF30 drive resident diagnostics and local programs

1–8

KA660 CPU System Maintenance

1.3 CPU Cover Panel (H3602–00)

The CPU cover panel (H3602–00, Figure 1–3) contains the console serial line connector, console baud rate switch, two Ethernet connectors and

LEDs, hexadecimal LED display, and Power-Up Mode switch. The switches are read by the firmware when the processor halts. For this reason, changing the baud rate on the cover panel does not take effect until the next power-up or system reset. The switches are also read when the Power-

Up Mode switch is in the test position. The cover panel has the following switches, connectors, and indicators:

• Baud rate select switch, on the back side of the panel.

• Power-Up Mode switch.

• Break Enable/Disable switch from the console keyboard

BREAK key or

CTRL/P

, depending on the state of SSCCR <15>. Break Enable is the default.

If this switch is set to the enable position, the system does not autoboot on power-up. It enters console I/O mode and displays the >>> prompt.

• Ethernet Connectors. The CPU cover panel has two connectors for

Ethernet cable: a 15-conductor connector for standard Ethernet cable, and a BNC connector for a ThinWire Ethernet coaxial cable. The cover panel contains a switch to select the Ethernet connector, and LEDs to indicate the selected connector and valid +12 Vdc for the selected connector.

• Hexadecimal LED display, which provides a countdown of the system power-up self-tests. See Table 4–5 for the meaning of this display.

KA660 CPU and Memory Subsystem

1–9

Figure 1–3: CPU Cover Panel (H3602–00)

CPU Cover Panel

Break

Enable/

Disable

Switch

Standard

Ethernet

Connector

LED Display

Power-Up

Mode Switch

Modified

Modular Jack

Ethernet

Connector Switch

ThinWire Ethernet

Connector

MLO-005504

1.4 MS650–Bn Memory Modules

The MS650–BA and MS650–BB memory modules are quad-height, Q22-bus modules. Timing of the MS650–BA (16 MBytes) and MS650–BB (8 Mbytes) modules is dependent upon the KA660 clock speed and CMCTL.

The MS650–AA memory module may not be used with the KA660 system

CPU.

The KA660 and the MS650–Bn memory modules are connected through the CD rows of backplane slots 1 through 5, and through a 50-conductor cable. The part number of this cable varies depending on the number of connectors, as follows:

1–10

KA660 CPU System Maintenance

Part Number

3

4

5

KA660 + 2 MS650–Bn modules

KA660 + 3 MS650–Bn modules

KA660 + 4 MS650–Bn modules

17–01898–01

17–01898–02

17–01898–03

1

Recommended cable. Use five-connector cable only if this cable is not available.

1

The cable is keyed so that it is installed in the correct connector on the

KA660 (the connector next to the module). The DSSI cable is attached to the connector ‘‘piggy backed’’ to the memory connector.

1.5 RF-Series ISE

The RF30 and RF31 ISEs are half-height, 13.3-cm (5.25-in) ISEs, for BA215,

BA213, or BA430 enclosures. The RF71 and RF72 ISEs are full-height ISEs for BA430 enclosures.

The RF-series ISE is based on the Digital Storage Systems Interconnect

(DSSI) architecture. DSSI supports up to seven storage devices, daisychained to the host system through the KA660 CPU or a host adapter module.

The disk drive controller is built into the RF-series ISE, rather than being a separate module. This feature enables many drive functions to be handled without host-system or adapter intervention, resulting in improved I/O performance and throughput rates.

DSSI node ID switches are located on the electronics controller module.

These switches give each ISE on the DSSI bus a unique node ID number.

The RF-series ISE contains three indicators: Ready, Write-protect, and

Fault.

The Ready indicator displays the activity status of the drive. It lights on power-up. After successful completion of the power-up diagnostics, the indicator goes out, until the media heads are on the requested cylinder and the drive is read/write ready.

When lit, the Write-protect indicator means the ISE is write-protected.

The Fault indicator lights at power-up. After successful completion of the power-up diagnostics, this indicator goes out. If the Fault indicator lights again after going out, a read/write safety error or a drive error condition has occurred.

KA660 CPU and Memory Subsystem

1–11

Chapter 2

Configuration

2.1 Introduction

This chapter describes the guidelines for changing the configuration of a

KA660 system, and for configuring a multihost system.

Before you change the system configuration, you must consider the following factors:

Module order in the backplane

Module configuration

Mass storage device configuration

If you are adding a device to a system, you must know the capacity of the system enclosure in the following areas:

Backplane

I/O panel

Power supply

Mass storage devices

2.2 General Module Order

The order of modules in the backplane depends on four factors:

• Relative use of devices in the system

• Expected performance of each device relative to other devices

• The ability of a device to tolerate delays between bus requests and bus grants (called delay tolerance or interrupt latency)

• The tendency of a device to prevent other devices farther from the CPU from accessing the bus

Configuration

2–1

2.2.1 Module Order for KA660 Systems

Observe the following rules about module order:

• Install the KA660 CPU in slot 1.

• Install MS650 memory modules in slots 2, 3, 4, and 5.

• Install all Q22-bus modules in the AB rows; single-height grant cards in the A row only. Do not install dual-height modules in the CD rows, which do not route the Q22-bus.

Here is the recommended module order in a KA660 system:

KA660–AA, –BA

MS650–BA, –BB

AAV11-SA

ADV11-SA

AXV11-SA

KWV11-SA

DRV1J-SA

KMV1A-SA/SB/SC

DMV11-SA

LNV21-SF

DEQNA/DELQA/DESQA-SA

DPV11-SA

DIV32-SA

VCB02-J/H/K

DZQ11-SA

DFA01-AB

CXM04-M

CXA16-AA

CXY08-AA

CXB16-AA

CXF32-AA/AB

LPV11-SA

DRV1W-SA

KRQ50-SA

IEQ11-SA

ADQ32-SA

DRQ3B-SA

DSV11-SY

KLESI-SA

IBQ01-SA

TSV05-S

KDA50-SE

KFQSA-SE

KZQSA-SA

2–2

KA660 CPU System Maintenance

TQK50-SA

TQK70-SA

RQDX3-SA

KDA50-SA/KFQSA-SA

M9060-YA

2.3 Module Configuration

Each module in a system must use a unique device address and interrupt vector. The device address is also known as the control and status register

(CSR) address. Most modules have switches or jumpers for setting the

CSR address and interrupt vector values. The value of a floating address depends on what other modules are housed in the system.

Set CSR addresses and interrupt vectors for a module by determining the correct values for the module with the CONFIGURE command at the console I/O prompt (>>>).

The CONFIG utility eliminates the need to boot the VMS operating system to determine CSRs and interrupt vectors. Enter the CONFIGURE command, then HELP for the list of supported devices:

>>>CONFIGURE

Enter device configuration, HELP, or EXIT

Device,Number? help

Devices:

LPV11

RLV12

DMV11

RRD50

KXJ11

TSV05

DELQA

RQC25

DLV11J

RXV21

DEQNA

KFQSA-DISK

DZQ11

DRV11W

DESQA

TQK50

RV20

CXA16

LNV21

KWV11C

DRQ3B

IDV11D

DESNA

KWV32

KFQSA-TAPE KMV11

CXB16

QPSS

ADV11D

VSV21

IAV11A

IGQ11

KZQSA

CXY08

DSV11

AAV11D

IBQ01

IAV11B

DIV32

IEQ11

VCB01

ADV11C

VCB02

IDV11A

MIRA

KIV32

DZV11

DRV11B

RQDX3

TQK70

DHQ11

QVSS

AAV11C

QDSS

IDV11B

ADQ32

DTCN5

DFA01

DPV11

KDA50

TU81E

DHV11

LNV11

AXV11C

DRV11J

IDV11C

DTC04

DTC05

See the description of the CONFIGURE command in Chapter 3

(Section 3.9.2) for an example of obtaining the correct CSR addresses and interrupt vectors using this command.

The LPV11–SA, which is the LPV11 version compatible with the BA200series and BA400-series enclosures, has two sets of CSR address and interrupt vectors. To determine the correct values for an LPV11–SA, enter

LPV11,2 at the DEVICE prompt for one LPV11–SA, or enter LPV11,4 for two LPV11–SA modules.

Configuration

2–3

2.4 DSSI Configuration

Each device must have a unique DSSI node ID. The ISE receives its node

ID from a plug on the system control panel (SCP). By convention, DSSI drives are mounted from right to left.

For more information on ISE node names, unit numbers, and other parameters, as well as information on the DUP server utility, see Appendix

B.

If the cable between the ISE and the SCP is disconnected, the ISE reads the node ID from three DIP switches on its electronics controller module

(ECM).

NOTE:

Pressing the system Reset button on the power supply has no effect on the ISEs. You must turn off the system and turn it back on.

The node ID switches are located behind the 50-pin connector on the ECM.

Switch 1 (the MSB) is nearest to the connector. Switch 3 (the LSB) is farthest from the connector. Table 2–1 lists the switch settings for the eight possible node addresses.

0

1

2

3

6

7

4

5

Table 2–1: ISE DIP Switch Settings

Node ID S1 S2 S3

Up

Up

Up

Up

Down

Down

Down

Down

Down

Down

Up

Up

Down

Down

Up

Up

Down

Up

Down

Up

Down

Up

Down

Up

The VMS operating system creates DSSI disk device names according to the following scheme: nodename $ DIA unit number.

For example,

SUSAN$DIA3

You can use the device name for booting, as follows:

>>> BOOT SUSAN$DIA3

You can access local programs in the ISE through the MicroVAX Diagnostic

Monitor (MDM), or through the VMS operating system (version 5.4.1 or later) and console I/O mode SET HOST/DUP command. This command creates a virtual terminal connection to the storage device and the

2–4

KA660 CPU System Maintenance

designated local program using the Diagnostic and Utilities Protocol (DUP) standard dialog. See Appendix B for the procedure for accessing DUP through the VMS operating system. Section 3.9.14 describes the console

I/O mode SET HOST/DUP command.

The KA660 DSSI node address is configured by three jumpers (W1, W2, and W3) that are found on the KA660 module as illustrated in Figure 1–1.

Table 2–2 lists the jumper positions and node IDs.

2

3

4

0

1

5

6

7

Table 2–2: Setting the KA660 Node ID

Node ID W3 W2 W1

In

In

In

Out

Out

Out

Out

In

Out

Out

In

In

Out

Out

In

In

Out

In

Out

In

Out

In

Out

In

2.4.1 DSSI Cabling for the BA215 Enclosure

The BA430 enclosure has no internal DSSI cabling. The connections are all realized by means of the backplane.

For the BA215, the cabling runs as follows:

A 50-conductor ribbon cable connects the ISE drive to the DSSI bus. A separate 5-conductor cable carries +5 Vdc and +12 Vdc to the drive from the enclosure power supply.

A 2-conductor cable connects the fifth pin on the ISE power connector to the SCP.

These cables carry the ACOK signal (same as POK) to the ISE. The SCP delays this signal to one ISE for each power supply to stagger the startup of one of two possible devices attached to each supply. This delay prevents excessive current draw at power-up. The BA215 enclosure has only one power supply, but implements this signal delay in the same way.

The 50-conductor DSSI ribbon cable connects to a 50-conductor round cable that is routed through the bottom of the mass storage area to the DSSI connector on the KA660.

CAUTION:

When removing or installing new drives, be sure to connect the rightmost connector of the DSSI ribbon cable to the round cable connected

Configuration

2–5

to the KA660. Do not ‘‘T’’ the bus by connecting the round connector to any of the ribbon cable’s center connectors.

2.4.1.1 DSSI Bus Termination and Length

The DSSI bus must be terminated at both ends. The KA660 module terminates the DSSI bus at one end. The DSSI bus terminates at a 50conductor connector on the left side of the enclosure. The terminator at this external connector can be removed to expand the bus.

The DSSI bus has a maximum length of 6 m (19.8 ft), including internal and external cabling.

In a dual-host system, the second KA660 module provides the bus termination.

2.4.2 Dual-Host Capability

An ISE has a multihost capability built into the firmware, which allows the drive to maintain connections with more than one DSSI adapter. Since the KA660 CPU has a built-in DSSI adapter, more than one KA660 CPU can be connected to the same DSSI bus, allowing each KA660 to access all other drives on the bus.

The primary application for such a configuration is a VAXcluster system using Ethernet as the interconnect medium between the boot and the satellite members. This configuration improves system availability, as described below.

Two KA660 systems are connected through an external DSSI cable

(BC21M). Each KA660 system is a boot member for a number of satellite nodes. The system disk resides in the first enclosure, and serves as the system disk for both KA660 systems. The KA660 in each enclosure has equal access to the system disk, and to any other DSSI disk in either enclosure.

If one of the KA660 modules fails, all satellite nodes booted through that

KA660 module lose connections to the system disk. However, the multihost capability enables each satellite node to know that the system disk is still available through a different path—that of the remaining good KA660 module. A connection through that KA660 is then established, and the satellite nodes are able to continue operation.

Thus, even if one KA660 module fails, the satellites booted through it are able to continue operation. The entire cluster will run in a degraded condition, since one KA660 is now serving the satellite nodes of both

KA660s. Processing can continue, however, until Customer Services can repair the problem.

2–6

KA660 CPU System Maintenance

A dual-host system cannot recover from the following conditions:

• System disk failure. If there is only one system disk, its failure causes the entire cluster to stop functioning until the disk failure is corrected.

Disk failure can be caused by such factors as a power supply failure in the enclosure containing the disk.

• DSSI cabling failure. If a failure in one of the DSSI cables renders access to the disks impossible, the cable must be repaired in order to continue operation. Since the DSSI bus cabling is not redundant, a cable failure usually results in a system failure.

2.4.3 Dual-Host Configuration

Dual-host systems have the following configuration limitations:

• A maximum of two systems can be connected, because of cabling and enclosure limitations.

• The DSSI bus supports eight devices or adapters. Since a dual-host system has two KA660 modules, and each has a connection to the DSSI bus, a maximum of six DSSI devices can be attached to the bus. See the

VAX 4000 Dual-Host Systems

manual, (EK–390AB–DH–002) for a complete list of supported dual-host configurations.

• Set DSSI node IDs as follows:

– The first (or only) KA660 is 7.

– The second KA660 in a dual-host system is 6. Table 2–2 explains how to set the KA660 node ID.

– The remaining devices in a dual-host system are 0–5.

2.5 Configuration Worksheet

Use the worksheet in Figure 2–1 or Figure 2–2 to make sure the configuration does not exceed the system’s limits for expansion space, I/O space, and power.

Table 2–3 lists power values for supported devices. To check a system configuration, follow these steps:

1. List all the devices to be installed in the system.

2. Fill in the information from Table 2–3 for each device.

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

Configuration

2–7

Table 2–3: KA660 Power and Bus Loads

Current (Amps)

(Max)

Power

(Max )

Option

AAV11–SA

ADQ32–SA

ADV11–SA

AXV11–SA

CXA16–M

CXB16–M

CXY08–M

DESQA–SA

DFA01–AA

DIV32–M

DPV11–SA

DRQ3B–SA

DRV1J–SA

DRV1W–SA

DSV11

DTQNA–BC

IBQ01–SA

IEQ11–SA

KA660–A/B

2

KDA50–SE

KDA50–

KLESI–SA

KMV1A–SA

KFQSA–SE

KRQ50–SA

KWV11–SA

KXJ11–SF

KZQSA–SA

LPV11–SA

MRV11–D

MS650–BA

MS650–BB

RF31E–AA

RF71E–AA

RV20

1

AC bus load must not exceed 22 A.

2

Value is for the unpopulated module only.

Module

A1009–PA

A030

A1008–PA

A026–PA

M3118–YA

M3118–YB

M3119–YA

M3127–PA

M3121–PA

M7528

M8020–PA

M7658–PA

M8049–PA

M7651–PA

M3108

M7130

M3125–PA

M8634–PA

M7626–A/B

M7164

M7165

M7740–PA

M7500–PA

M7769

M7552

M4002–PA

M7616

M5976–SA

M8086–PA

M8578

M7621

M7621

+5 V

3.50

6.0

6.93

6.57

3.20

2.6

5.50

1.80

1.80

5.43

6.00

5.00

2.10

4.45

2.00

2.00

1.60

2.00

1.64

2.40

1.97

5.5

1.20

4.50

1.1

3.9

1.25

1.25

3.0

2.70

2.20

6.00

5.4

2.80

1.60

2

+12 V

0.00

0.14

0.00

0.03

0.00

0.20

0.00

0.00

0.00

0.69

2.00

0.30

0.00

0.00

0.00

0.00

0.20

0.00

0.395

0.22

0.04

0.0

0.30

0.00

0.00

0.013

1.40

0.0

0.00

0.00

0.0

0.0

2.21

1.64

Watts

9.00

9.00

35.43

54.00

28.60

17.50

32.88

34.65

33.21

15.00

15.40

27.50

10.50

22.25

10.00

10.00

10.40

10.00

12.94

14.64

10.30

27.5

9.60

22.50

13.50

11.156

46.80

27.0

14.00

8.00

5.5

19.53

27.4

25.93

35.3.0

BusLoads

AC

1

DC

2.0

3.5

3.0

2.3

3.0

4.4

2.0

2.0

3.9

3.9

4.6

2.5

2.5

2.3

1.2

3.0

3.0

3.0

2.2

3.0

3.9

1.0

2.0

1.8

3.0

0.0

0.0

0.0

2.7

1.0

1.0

0.3

2.7

1.0

4.75

1.4

0.5

0.5

0.0

0.0

0.5

0.5

0.5

0.3

0.5

0.5

0.5

0.5

1.0

1.0

1.0

0.5

1.0

1.0

0.5

1.0

1.0

0.5

1.0

1.0

1.0

0.5

1.0

2–8

KA660 CPU System Maintenance

Table 2–3 (Cont.): KA660 Power and Bus Loads

Current (Amps)

(Max)

Power

(Max )

Option

TLZ04–JA

TK70E–AA

TQK70–SA

TSV05–SA

TSV05–SA

Module

M7559

M7530

M7206–PA

1

AC bus load must not exceed 22 A.

+5 V

2.20

1.50

3.2

6.50

6.50

+12 V

0.345

2.40

0.00

0.00

0.00

Watts

15.2

36.30

15.0

32.50

32.50

BusLoads

AC

1

DC

4.3

1.5

2.4

0.5

1.0

1.0

NOTE:

Slot 0 will always be occupied by the M9715–AA, which generates

0.1 A @ +5V dc and 1.0 A @ +12V dc, with a total power of 12.5 W.

NOTE:

The BA215 supports only the half-height ISEs.

Configuration

2–9

Figure 2–1: VAX 4000 Model 200 (BA430) Configuration Worksheet

Slot

0

CPU 1

Mem 2

Mem 3

Mem 4

Mem 5

Q/CD 6

Q/CD 7

Q/CD 8

Q/CD 9

Q/CD 10

Q/CD 11

Q/CD 12

Mass Storage:

Tape

1

2

Module

3

Total these columns:

Must not exceed:

+5 Vdc

Current (Amps)

+12 Vdc -3.3 Vdc -12 Vdc

Power

(Watts)

60.0 A 22.0 A 15.0 A 3.0 A 584.0 W

Note: Total output power from +3.3 Vdc and +5 Vdc must not exceed 330 W.

Bus Load

AC DC

31 20

MLO-005711

2–10

KA660 CPU System Maintenance

Figure 2–2: VAX 4000 Model 200 (BA215) Configuration Worksheet

Primary Power Supply

Slot Module

CPU 1

Mem 2

Q/CD 3

Q/CD 4

Q/CD 5

Q/CD 6

Mass Storage:

Tape Drive

Fixed Disk 0

Fixed Disk 1

Total these columns:

Must not exceed:

Current (Amps)

+5 Vdc

+12 Vdc

33.0 A 7.6 A

Power

(Watts)

Bus Load

AC DC

230.0 W

MLO-005712

Configuration

2–11

Chapter 3

KA660 Firmware

3.1 Introduction

This chapter describes the KA660 firmware, which gains control of the processor whenever the KA660 performs a processor halt. A processor halt transfers control to the firmware. The processor does not actually stop executing instructions.

3.2 KA660 Firmware Features

The firmware is located in two 128-Kbyte EPROMS on the KA660. The firmware address range is 20040000 through 2007FFFF, in the KA660 local

I/O space. The firmware displays diagnostic progress and error reports on the KA660 LEDs and on the console terminal. It provides the following features:

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

(Restart in this context is not the same as restarting or resetting the hardware.)

• Automatic or manual bootstrap of an operating system following processor halts.

• An interactive command language that allows you to examine and alter the state of the processor.

• Diagnostics that test all components on the board and verify that the module is working correctly.

• Support of various terminals and devices as the system console.

• Multilingual support. The firmware can issue system messages in several languages.

The processor must be functioning at a level able to execute instructions from the console program ROM for the console program to operate.

KA660 Firmware

3–1

The firmware consists of the following major functional areas:

Halt entry and dispatch code

Bootstrap

Console I/O mode

Diagnostics

The halt entry and dispatch code, bootstrap, and console I/O mode are described in this chapter. Diagnostics are described in Chapter 4.

3.3 Halt Entry and Dispatch Code

The processor enters the halt entry code at physical address 20040000 whenever a halt occurs. The halt entry code saves machine state, then transfers control to the firmware halt dispatcher.

After a halt, the halt entry code saves the current LED code, then writes an E to the LEDs. An E on the LEDs indicates that at least several instructions have been successfully executed, although if the CPU is functioning properly, it occurs too quickly to be seen. The halt entry code saves the following registers. The console intercepts any direct reference to these registers and redirects it to the saved copies:

R0–R15

PR$_SAVPSL

PR$_SCBB

DLEDR

ADxMAT

ADxMAT

General purpose registers

Saved processor status longword register

System control block base register

Diagnostic LED register

SSC address match register

SSC address mask register

The halt entry code unconditionally sets the following registers to fixed values on any halt, to ensure that the console itself can run and to protect the module from physical damage.

SSCCR

ADxMAT

ADxMSK

CBTCR

TIVRx

SSC configuration register

SSC address match register

SSC address mask register

CDAL bus timeout control register

SSC timer interrupt vector registers

The console command interpreter does not modify actual processor registers. Instead it saves the processor registers in console memory when it enters the halt entry code, then directs all references to the processor registers to the corresponding saved values, not to the registers themselves.

When the processor reenters program mode, the saved registers are restored and any changes become operative only then. References to processor memory are handled normally. The binary load and unload command (X, Section 3.9.19) cannot reference the console memory pages.

3–2

KA660 CPU System Maintenance

After saving the registers, the halt entry code transfers control to the halt dispatch code. The halt dispatch code determines the cause of the halt by reading the halt field (PR$_SAVPSL <13:08>), the processor halt action field (PR$_CPMBX <01:00>), and the Break Enable/Disable switch on the

CPU cover panel. Table 3–1 lists the actions taken, in sequence. If an action fails, the next action is taken, with the exception of bootstrap, which is not attempted after diagnostic failure.

Table 3–1: Halt Action Summary

F

F

F

F

F

F

F

F

F

T

T

T

Halt

Code= 3

x x x x x

1

0 x x

1

1

0

Enable

Switch

x x x

1

2

0

0

3

4

Defined

Halt

0, 1, 3

1 x

1

2

3

0

0

0

0

0

0

Program

Mailbox

x

2, 4 x

Action(s)

Diagnostics and console commands x

Diagnostics; if successful, boot, if fails, use console commands

Console

Restart; if this fails boot; if boot fails use console commands

Restart; if this fails, use console commands

Boot; if this fails, use console commands

Console

Restart; if this fails, boot; if boot fails, use console commands

Restart; if this fails, use console commands

Boot; if this fails, use console commands

Console

T = TRUE—indicates a Reset or Power-up condition.

F = FALSE—indicates a HALT instruction or error halt condition.

x = DON’T CARE—indicates that the condition is "don’t care".

3.4 External Halts

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

• The Break Enable/Disable switch is set to enable, and you press

BREAK on the system console terminal.

KA660 Firmware

3–3

• Assertion of the BHALT line on the Q-bus.

• Deassertion of DCOK. A halt is delivered if the processor is not running out of halt-protected space, and the BHALT ENB bit is set. The system restart switch deasserts DCOK. DCOK may also be deasserted by the

DESQA sanity timer, or any other Q22-bus module that chooses to implement the Q22-bus restart/reboot protocol.

The KA660 cannot detect the deassertion of DCOK when in console I/O mode, so no action is taken.

CAUTION:

Do not press the Restart button while in console I/O mode.

Doing so will destroy system state without notifying the firmware.

The action taken by the halt dispatch code on a console

BREAK or Q22-bus

BHALT is the same: the firmware enters console I/O mode if halts are enabled.

The halt dispatch code distinguishes between DCOK deasserted and

BHALT by assuming that BHALT must be asserted for at least 10 ms, and that DCOK is deasserted for at most 9 s. To determine if the BHALT line is asserted, the firmware steps out into halt-unprotected space after 9 ms. If the processor halts again, the firmware concludes that the halt was caused by the BHALT and not by the deassertion of DCOK. The firmware keeps a halt-in-progress flag to tell if it is halting because of stepping out into halt-unprotected space. This flag is cleared on power-up.

3.5 Power-Up Sequence

On power-up, the firmware performs several actions.

It locates and identifies the console device, performs a language inquiry, and runs the diagnostics.

Power-up actions differ, depending on the state of the Power-Up Mode switch on the CPU cover panel (Figure 1–3).

The mode switch has three settings: Test, Language Inquiry, and Normal. The differences are described in Sections 3.5.0.1 through 3.5.0.3.

3.5.0.1 Mode Switch Set to Test

Use the Test position on the H3602–00 to verify that the connection between the KA660 and the console terminal is good.

• To test the console terminal, insert the H3103 loopback connector into the H3602–00 console connector, and set the switch to the Test position.

You must install the loopback connector to run the test.

• To test the console cable, install the H8572 connector on the end of the console cable, and insert the H3103 into the H8572.

3–4

KA660 CPU System Maintenance

During the test, the firmware toggles between the active and passive states.

During the active state (3 seconds), the LED is set to 6. The firmware reads the baud rate and mode switch, then transmits and receives a character sequence.

During the passive state (5 seconds), the LED is set to 3.

If at any time the firmware detects an error (parity, framing, overflow, or no characters), the display hangs at 6. If the configuration switch is moved from the test position, the firmware continues as if on a normal power-up.

3.5.0.2 Mode Switch Set to Language Inquiry

If the Power-Up Mode switch is set to Language Inquiry, or the firmware detects that the contents of NVRAM are invalid, the firmware prompts you for the language to be used for displaying the following system messages:

Loading system software.

Failure.

Restarting system software.

Performing normal system tests.

Tests completed.

Normal operation not possible.

Bootfile.

The Language Selection Menu appears under the conditions listed in

Table 3–2. The position of the Break Enable/Disable switch has no effect on these conditions.

KA660 Firmware

3–5

Table 3–2: Language Inquiry on Power-Up or Reset

Mode

Language Not

Previously Set

1

Language

Previously Set

Language Inquiry

Normal

Prompt

2

Prompt

Prompt

No Prompt

1

Action if contents of NVRAM invalid same as Language Not Previously Set.

2

Prompt = Language Selection Menu displayed.

The Language Selection Menu is shown in Example 3–1. If no response is received within 30 seconds, the firmware defaults to English.

Example 3–1: Language Selection Menu

1) Dansk

2) Deutsch (Deutschland/Österreich)

3) Deutsch (Schweiz)

4) English (United Kingdom)

5) English (United States/Canada)

6) Español

7) Français (Canada)

8) Français (France/Belgique)

9) Français (Suisse)

10) Italiano

11) Nederlands

12) Norsk

13) Portugues

14) Suomi

15) Svenska

(1..15):

In addition, the console may prompt you for a default boot device. See

Section 3.6. After the language inquiry, the firmware continues as if on a normal power-up.

3.5.0.3 Mode Switch Set to Normal

The console displays the Language Selection Menu if the mode switch is set to Normal and the contents of NVRAM are invalid. The console uses the saved console language if the mode switch is set to Normal and the contents of NVRAM are valid.

3–6

KA660 CPU System Maintenance

3.6 Bootstrap

The KA660 supports bootstrap of VAX/VMS, VAXELN, and MDM diagnostics.

The firmware initializes the system to a known state before dispatching to the primary virtual memory bootstrap (VMB), as follows:

1. Checks CPMBX<2>(BIP), bootstrap in progress. If it is set, bootstrap fails and the console displays the message

Failure.

in the selected console language.

2. If this is an automatic bootstrap, prints the message

Loading system software.

on the console terminal.

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

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

5. Sets CPMBX<2>(BIP).

6. Initializes the Q22-bus scatter/gather map.

7. Validates the PFN bitmap. If invalid, rebuilds it.

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

9. Initializes the general purpose registers:

R0

R2

R3

R4

R5

R10

R11

AP

SP

PC

R1, R6, R7, R8,

R9, FP

Address of descriptor of the boot device name or 0 if none specified

Length of PFN bitmap in bytes

Address of PFN bitmap

Time-of-day of bootstrap from PR$_TODR

Boot flags

Halt PC value

Halt PSL value (without halt code and mapenable)

Halt code

Base of 128-Kbyte good memory block + 512

Base of 128-Kbyte good memory block + 512

0

10. Copies the VMB image from EPROM to local memory, beginning at the base of the 128 Kbytes of good memory block + 512.

11. Exits from the firmware to VMB residing in memory.

KA660 Firmware

3–7

VMB is the primary bootstrap for VAX processors. The KA660 VMB resides in the firmware, and is copied into main memory before control is transferred to it. VMB then loads the secondary bootstrap image and transfers control to it.

3.7 Operating System Restart

An operating system restart is the process of bringing up the operating system from a known initialization state following a processor halt.

A restart occurs under the conditions listed in Table 3–1, earlier in this chapter.

To restart a halted operating system, the firmware searches system memory for the restart parameter block (RPB), a data structure constructed for this purpose by VMB. If the firmware finds a valid RPB, it passes control to the operating system at an address specified in the RPB.

The firmware keeps a restart-in-progress (RIP) flag in CPMBX which it uses to avoid repeated attempts to restart a failing operating system. The operating system maintains an additional RIP flag in the RPB.

The firmware restarts the operating system in the following sequence:

1. Checks CPMBX<3>(RIP). If it is set, restart fails.

2. Prints the message

Restarting system software.

on the console terminal.

3. Sets CPMBX<3>(RIP).

4. Searches for a valid RPB. If none is found, restart fails.

5. Checks the operating system RPB$L_RSTRTFLG<0>(RIP) flag. If it is set, restart fails.

6. Writes a 0 (zero) to the diagnostic LEDs.

7. Dispatches to the restart address, RPB$L_RESTART, with:

SP = the physical address of the RPB plus 512

AP = the halt code

PSL = 041F0000

PR$_MAPEN = 0.

If the restart is successful, the operating system must clear CPMBX<3>(RIP).

If restart fails, the firmware prints

Failure.

on the console terminal.

3–8

KA660 CPU System Maintenance

3.7.1 Locating the RPB

The RPB is a page-aligned control block that can be identified by its signature in the first three longwords:

+00 (first longword) = physical address of the RPB

+04 (second longword) = physical address of the restart routine

+08 (third longword) = checksum of first 31 longwords of restart routine

The firmware finds a valid RPB as follows:

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

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

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

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

3.8 Console I/O Mode

In console I/O mode several characters have special meaning, as listed in

Table 3–3.

3.8.1 Command Syntax

The console accepts commands up to 80 characters long. Longer commands produce error messages. The character count does not include rubouts, rubbed-out characters, or the

RETURN at the end of the command.

You can abbreviate a command by entering only as many characters as are required to make the command unique. Most commands can be recognized from their first character.

The console treats two or more consecutive spaces and tabs as a single space. Leading and trailing spaces and tabs are ignored. You can place command qualifiers after the command keyword or after any symbol or number in the command.

All numbers (addresses, data, counts) are hexadecimal, but symbolic register names contain decimal register numbers. The hexadecimal digits are 0 through 9 and A through F. You can use uppercase and lowercase letters in hexadecimal numbers (A through F) and commands.

KA660 Firmware

3–9

Table 3–3: Console I/O Mode Special Characters

RETURN

X

Ctrl/A

Ctrl/B

Ctrl/C

Ctrl/D

Ctrl/E

Ctrl/F

Ctrl/H

Ctrl/O

Ctrl/Q

(Carriage Return) This character ends a command line. No action is taken on a command until after it is terminated by a carriage return. A null line terminated by a carriage return is treated as a valid, null command. No action is taken, and the console re-prompts for input. Carriage return is echoed as carriage return, line feed.

(Delete Character) When the operator types rubout, the console deletes the character that the operator previously typed. What appears on the console terminal depends on whether the terminal is a video terminal or a hardcopy terminal. For hard copy terminals, when a rubout is typed, the console echoes with a backslash ("<backslash>"), followed by the character being deleted. If the operator types additional rubouts, the additional characters deleted are echoed.

When the operator types a non-rubout character, the console echoes another backslash, followed by the character typed. The result is to echo the characters deleted, surrounding them with backslashes.

For video terminals, when RUBOUT is typed the previous character is erased from the screen and the cursor is restored to its previous position. The console does not delete characters past the beginning of a command line. If the operator types more rubouts than there are characters on the line, the extra rubouts are ignored. If a RUBOUT is typed on a blank line, it is ignored.

(or F14) Toggle insertion/overstrike mode for command line editing. By default, the console powers up to overstrike mode.

(or up_arrow or down_arrow) Recall previous command(s). Command recall is only operable if sufficient memory is available. This function may then be enabled and disabled using the SET RECALL command.

Control-C causes the console to echo ^C and to abort processing of a command.

Control-C has no effect as part of a binary load data stream. Control-C clears control-S, and reenables output stopped by control-O.

(Control-D or left_arrow) This character moves the cursor left one position.

(Control-E) Move cursor to the end of the line.

(Control-F or right_arrow) Moves the cursor right one position.

(Control-H, BACKSPACE or F12) Moves cursor to the beginning of the line.

(Control-O) This character causes the console to throw away transmissions to the console terminal until the next control-O is entered. Control-O is echoed as

^O<CR> when it disables output, but is not echoed when it reenables output.

Output is reenabled if the console prints an error message, or if it prompts for a command from the terminal. Displaying a REPEAT command does not reenable output. When output is reenabled for reading a command, the console prompt is displayed. Output is also enabled control-S.

(Control-Q) This character causes the output to the console terminal to resume.

Additional control-Q’s are ignored. Control-S and control-Q are not echoed.

3–10

KA660 CPU System Maintenance

Ctrl/S

Ctrl/U

Ctrl/R

Ctrl/P

BREAK

(Control-S) Stops output to the console terminal until control-Q is typed. Control-

S and control-Q are not echoed.

(Control-U) The console echoes ^U<CR>, and deletes the entire line. If control-

U is typed on an empty line, it is echoed, and the console prompts for another command.

(Control-R) Causes the console to echo <CR><LF> followed by the current command line. This function can be used to improve the readability of a command line that has been heavily edited. When control-C is typed as part of a command line, the console deletes the line as it does with control-U.

(Control-P) If in console I/O mode, causes the console to echo ^P and to abort processing of a command. If the console is in program I/O mode control-P is passed to the operating system.

(BREAK) If the console is in console I/O mode, BREAK is equivalent to control-C and is echoed as "^C".

NOTE:

If the local console is in program I/O mode and halts are disabled,

BREAK is ignored. If the console is in program I/O mode and halts are enabled, BREAK causes the processor to halt and enter console I/O mode.

3.8.2 Address Specifiers

Several commands take an address or addresses as arguments. An address defines the address space, and the offset into that space. The console supports six address spaces:

Physical memory

Virtual memory

Protected memory

General purpose registers (GPR)

Internal processor registers (IPR)

The PSL

The address space that the console references is inherited from the previous console reference, unless you explicitly specify another address space. The initial address space is physical memory.

3.8.3 Symbolic Addresses

The console supports symbolic references to addresses. A symbolic reference defines the address space, and the offset into that space. Table 3–4 lists symbolic references supported by the console, grouped according to address space. You do not have to use an address space qualifier when using a symbolic address.

KA660 Firmware

3–11

Table 3–4: Console Symbolic Addresses

Symbol Address Symbol Address

GPR Address Space (/G)

R0

R2

R4

R6

R8

R10

R12

R14

AP

SP

PSL

8

0A

0C

0E

0C

0D

4

6

0

2

R1

R3

R5

R7

R9

R11

R13

R15

FP

PC

9

0B

0D

0F

0D

0E

5

7

1

3

IPR Address Space (/I)

pr$_ksp pr$_ssp pr$_isp pr$_p0lr pr$_p1lr pr$_slr pr$_scbb pr$_astlv pr$_sisr pr$_nicr pr$_todr pr$_rxdb pr$_txdb pr$_ccr pr$_mser pr$_savpsl pr$_mapen pr$_tbis pr$_tbchk

00

02

04

09

0B

0D

11

13

15

19

1B

21

23

25

27

2B

38

3A

3F pr$_esp pr$_usp pr$_p0br pr$_p1br pr$_sbr pr$_pcbb pr$_ipl pr$_sirr pr$_iccr pr$_icr pr$_rxcs pr$_txcs pr$_tbdr pr$_mcesr pr$_savpc pr$_ioreset pr$_tbia pr$_sid

01

03

08

0A

0C

10

12

14

18

1A

20

22

24

26

2A

37

39

3E

3–12

KA660 CPU System Maintenance

Table 3–4 (Cont.): Console Symbolic Addresses

Symbol Address Symbol Address

Physical Memory (/P)

ssc_tcr0 ssc_tnir0 ssc_tcr1 ssc_tnir1 memcsr0 memcsr2 memcsr4 memcsr6 memcsr8 memcsr10 memcsr12 memcsr14 qbio qbmbr rom bdr dscr dmear ipcr0 ipcr2 ssc_ram ssc_cdal ssc_ad0mat ssc_ad1mat memcsr16 nicsr0

—nicsr4 nicsr6

—nicsr10 nicsr12 nicsr14 sgec_setup

—sgec_tba sgec_mode

20140100

20140108

20140110

20140118

20080100

20080108

20080110

20080118

20080120

20080128

20080130

20080138

20000000

20080010

20040000

20084004

20080000

20080008

20001f40

20001f44

20140400

20140020

20140130

20140140

20080140

20008000

20008008

20008010

20008018

20008020

20008028

20008030

20008038

20008000

20008008

20008010

20008018 ssc_tir0 ssc_tivr0 ssc_tir1 ssc_tivr1 memcsr1 memcsr3 memcsr5 memcsr7 memcsr9 memcsr11 memcsr13 memcsr15 qbmem

—cacr

—dser dsear ipcr1 ipcr3 ssc_cr ssc_dledr ssc_ad0msk ssc_ad1msk memcsr17 nicsr1 nicsr3 nicsr5 nicsr7 nicsr9 nicsr11 nicsr13 nicsr15 sgec_poll sgec_rba sgec_status sgec_sbr

20140104

2014010c

20140114

2014011c

20080104

2008010c

20080114

2008011c

20080124

2008012c

20080134

2008013c

30000000

—-

20084000

—-

20080004

2008000C

20001f42

20001f46

20140010

20140030

20140134

20140144

20080144

20008004

2000800C

20008014

2000801C

20008024

2000802C

20008034

2000803C

20008004

2000800C

20008014

2000801C

KA660 Firmware

3–13

Table 3–4 (Cont.): Console Symbolic Addresses

Symbol Address Symbol Address

Physical Memory (/P)

—sgec_mfc sgec_verhi sgec_bpt shac_sswcr shac_pqbbr shac_pesr shac_ppr shac_pcq0cr shac_pcq2cr shac_pdfqcr shac_psrcr shac_pdcr shac_pmtcr

20008020

20008028

20008030

20008038

20004230

20004048

20004250

20004058

20004280

20004088

20004290

20004098

200042A0

200040A8 sgec_wdt sgec_verlo sgec_proc sgec_cmd shac_sshma shac_psr shac_pfar shac_pmcsr shac_pcq1cr shac_pcq3cr shac_pmfqcr shac_pecr shac_picr shac_pmtecr

20008024

2000802C

20008034

2000803C

20004244

2000404c

20004254

2000405C

20004284

2000408C

20004294

2000409C

200042A4

200040AC

Table 3–5 lists symbolic addresses that can be used in any address space.

*

+

Table 3–5: Symbolic Addresses Used in Any Address Space

Symbol Description

@

The location last referenced in an EXAMINE or DEPOSIT command.

The location immediately following the last location referenced in an EXAMINE or DEPOSIT command. For references to physical or virtual memory spaces, the location referenced is the last address, plus the size of the last reference (1 for byte, 2 for word, 4 for longword, 8 for quadword). For other address spaces, the address is the last address referenced plus one.

The location immediately preceding the last location referenced in an EXAMINE or DEPOSIT command. For references to physical or virtual memory spaces, the location referenced is the last address minus the size of this reference (1 for byte, 2 for word, 4 for longword, 8 for quadword). For other address spaces, the address is the last address referenced minus one.

The location addressed by the last location referenced in an EXAMINE or

DEPOSIT command.

3–14

KA660 CPU System Maintenance

3.8.4 Console Command Qualifiers

You can enter console command qualifiers in any order on the command line after the command keyword. The three types of qualifiers are: data control, address space control, and command specific. Table 3–6 lists and describes the data control and address space control qualifiers. Command specific qualifiers are described in Section 3.9.

Table 3–6: Console Command Qualifiers

Qualifier Description

Data Control

/B

/W

/L

/Q

/N:{count}

The data size is byte.

The data size is word.

The data size is longword.

The data size is quadword.

An unsigned hexadecimal integer that is evaluated into a longword. This qualifier determines the number of additional operations that are to take place on EXAMINE, DEPOSIT, MOVE, and SEARCH commands. An error message appears if the number overflows 32 bits.

/STEP:{size} Step. Overrides the default increment of the console current reference.

Commands that manipulate memory, such as EXAMINE, DEPOSIT, MOVE, and SEARCH, normally increment the console current reference by the size of the data being used.

/WRONG Wrong. Used to override or set error bits when referencing main memory. On writes, use the complement. On reads, ignore ECC errors.

Address Space Control

/G

/I

/V

/P

/M

/U

General purpose register (GPR) address space, R0–R15. The data size is always longword.

Internal processor register (IPR) address space. Accessible only by the MTPR and MFPR instructions. The data size is always longword.

Virtual memory address space. All access and protection checking occur. If access to a program running with the current PSL is not allowed, the console issues an error message. Deposits to virtual space cause the PTE<M> bit to be set. If memory mapping is not enabled, virtual addresses are equal to physical addresses. Note that when you examine virtual memory, the address space and address in the response is the physical address of the virtual address.

Physical memory address space.

Processor status longword (PSL) address space. The data size is always longword.

Access to console private memory is allowed. This qualifier also disables virtual address protection checks. On virtual address writes, the PTE<M> bit is not set if the /U qualifier is present. This qualifier is not inherited; it must be respecified on each command.

KA660 Firmware

3–15

3.8.5 Console Command Keywords

Table 3–7 lists command keywords by type. Table 3–8 lists the parameters, qualifiers, and arguments for each console command. Parameters, used with the SET and SHOW commands only, are listed in the first column along with the command.

Although it is possible to abbreviate by using the minimum number of characters required to uniquely identify a command or parameter, these abbreviations may become ambiguous at a later time if a new command or parameter is added in an updated version of the firmware. For this reason you should not use abbreviations in programs.

Table 3–7: Command Keywords by Type

Processor Control Data Transfer

B*OOT

C*ONTINUE

H*ALT

I*NITIALIZE

N*EXT

S*TART

U*NJAM

D*EPOSIT

E*XAMINE

M*OVE

SEA*RCH

X

Console Control

CONF*IGURE

F*IND

R*EPEAT

SET

SH*OW

T*EST

Qualifier Keywords

Data Control Address Space Control Command Specific

/B

/W

/L

/Q

/N:

/ST*EP:

/WR*ONG

/G

/I

/P

/V

/M

/U

/IN*STRUCTION

/NO*T

/R5: or /

/RP*B or /ME*M

/F*ULL

/DU*P or /MA*INTENANCE

/DS*SI or /U*QSSP

/DI*SK or /T*APE

/SE*RVICE

"*" indicates the minimal number of characters that are required to uniquely identify the keyword.

3–16

KA660 CPU System Maintenance

Table 3–8: Console Command Summary

Command Qualifiers

BOOT

CONFIGURE

CONTINUE

DEPOSIT

EXAMINE

FIND

HALT

HELP

INITIALIZE

MOVE

NEXT

REPEAT

SEARCH

SET BFL(A)G

SET BOOT

SET CONTROLP

SET HALT

SET HOST

SET HOST

/R5:{boot_flags} /{boot_flags}

/B /W /L /Q — /G /I /V /P /M /U

/N:{count} /STEP:{size} /WRONG

:{ecc}]

/B /W /L /Q — /G /I /V /P /M /U

/N:{count} /STEP:{size} /WRONG

/INSTRUCTION

/MEM /RPB

/B /W /L /Q — /V /P /U

/N:{count} /STEP:{size} /WRONG

[:{ecc}]

/B /W /L /Q — /V /P /U

/N:{count} /STEP:{size} /WRONG

/NOT

/DUP /DSSI /BUS:{0/1}

/DUP /UQSSP {/DISK ! /TAPE }

/DUP /UQSSP

SET HOST

SET LANGUAGE

SET RECALL

SET VERIFICATION

SHOW BFL(A)G

SHOW BOOT

SHOW CONTROLP

SHOW DEVICE

SHOW DSSI

/MAINTENANCE /UQSSP

/SERVICE

/MAINTENANCE /UQSSP

Argument

[{boot_device}]

{address}

[{address}]

{src_address}

[{count}]

{command}

{start_address}

Other(s)

{data} [{data}]

{dest_address}

{pattern} [{mask}]

{bitmap}

{device_string}

{0/1}

{halt_action}

{node_number}

{controller_number}

{csr_address}

{controller_number}

[{task}]

[{task}]

[{task}]

{csr_address}

{language_type}

{0/1}

{password}

KA660 Firmware

3–17

Table 3–8 (Cont.): Console Command Summary

Command Qualifiers Argument

SHOW ETHERNET

SHOW HALT

SHOW LANGUAGE

SHOW MEMORY

SHOW QBUS

SHOW RECALL

SHOW RLV12

SHOW SCSI —

SHOW TRANSLATION —

SHOW UQSSP —

SHOW VERIFICATION —

SHOW VERSION —

START

TEST

UNJAM

X

/FULL

{phys_address}

{address}

{test_number}

{address}

Other(s)

[{parameters}]

{count}

3.9 Console Commands

This section describes the console I/O mode commands.

Enter the commands at the console I/O mode prompt

>>>

.

3.9.1 BOOT

The BOOT command initializes the processor and transfers execution to

VMB. VMB attempts to boot the operating system from the specified device, or the default boot device if none is specified. The console qualifies the bootstrap operation by passing a boot flags bitmap to VMB in R5. Table 3–9 lists the supported R5 boot flags.

Format:

BOOT [qualifier-list] [boot_device]

If you do not enter either the qualifier or the device name, then the default value is used. Explicitly stating the boot flags or the boot device overrides but does not permanently change the corresponding default value.

Set the default boot device and boot flags with the SET BOOT and SET

BFLAG commands. If you do not set a default boot device, the processor times out after 30 seconds and attempts to boot from the on-board Ethernet port, EZA0. Table 3–10 lists the boot devices supported by the KA660–AA.

3–18

KA660 CPU System Maintenance

Command Specific Qualifiers:

/R5:{bitmap}

/{bitmap}

[boot_device or device list]

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

Same as /R5:{bitmap}

A character string of up to 39 characters. Longer strings cause a VAL TOO

BIG error message. Apart from length, the console makes no attempt to interpret or validate the device name. The console converts the string to uppercase, then passes VMB a string descriptor to this device name in R0.

Table 3–9: VMB Boot Flags

Bit Name Description

0

2

3

4

5

6

8

9

RPB$V_CONV

RPB$V_INIBPT

RPB$V_BBLOCK

RPB$V_DIAG

RPB$V_BOOBPT

RPB$V_HEADER

RPB$V_SOLICT

RPB$V_HALT

31:28 RPB$V_TOPSYS

Conversational boot. At various points in the system boot procedure, the bootstrap code solicits parameters and other input from the console terminal.

Initial breakpoint.

If RPB$V_DEBUG is set, the VMS operating system executes a BPT instruction in module INIT immediately after enabling mapping.

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

Diagnostic bootstrap. When set, the load image requested over the network is [SYS0.SYSMAINT]DIAGBOOT.EXE.

Bootstrap breakpoint. When set, a breakpoint instruction is executed in VMB and control is transferred to XDELTA before booting.

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

File name solicit. When set, VMB prompts the operator for the name of the application image file. The maximum file specification size is 17 characters.

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

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

KA660 Firmware

3–19

3.9.1.1 Supported Boot Devices

Table 3–10 lists the boot devices supported by the KA660 CPU. The table correlates the boot device names expected in a BOOT command with the corresponding supported devices.

Boot device names consist of a device code at least two letters (A through

Z) in length, followed by a single character controller letter (A through Z), and ending in a device unit number (0–16,383).

DSSI device names may also include a node prefix, consisting of either a node number (0–7) or a node name (a string of up to eight characters), ending in a dollar sign ($).

3.9.1.2 Boot Devices

The KA660 firmware passes the address of a descriptor of the boot device name to VMB through R0. This device name used for the bootstrap operation is one of the following:

• The local Ethernet device, if no default boot device has been specified or

• The default boot device specified at initial power-up or via a SET BOOT command, or

• The boot device name explicitly specified in a BOOT command line.

The device name may be any arbitrary character string, with a maximum length of 17 characters. Longer strings cause an error message to be issued to the console. Otherwise the console makes no attempt at interpreting or validating the device name. The console converts the string to all upper case, and passes VMB the address of a string descriptor for the device name in R0.

Table 3–10 correlates the boot device names expected in a BOOT command with the corresponding supported devices.

3–20

KA660 CPU System Maintenance

Table 3–10: Boot Device Names

Device Type Controller/Adapter

RF-series ISE

RF-series ISE

TK-series tape drive

Embedded DSSI host adapter

(part of CPU)

KFQSA storage adapter

TQK70/TQK50

TLZ04 tape drive KZQSA adapter

RRD40 compact disc drive KZQSA adapter

Device Logical Name

DImn

1

DUcn

MUcn

2

MKAn

DKAn

3

PROM (programmable read-only memory)

Ethernet adapter

MRV11 module PRAn

On-board (part of CPU) EZA0

Ethernet adapter

RA-series drives

DESQA Ethernet controller

KDA50

XQAn

DUcn

2

1 m = DSSI bus adapter (A = first bus (0), B = second bus (1), and so on.) n = unit number

When under operating system control, DIBn devices are recognized as DIAn devices.

2 c = MSCP controller designator (A = first, B = second, and so on.) n = unit number

3 c = TMSCP controller designator (A = first, B = second, and so on.) n = unit number

Examples:

>>> SHOW BOOT

0

>>> SHOW BFLAG

EZA0

>>> B! Boot using default boot flags and device.

(BOOT/R5:0 EZA0)

2..

-EZA0

>>> B XQA0 ! Boot from XQA0 using default boot flags.

(BOOT/R5:0 XQA0)

2..

-XQA0

>>> B/10 ! Boot using supplied boot flag (4)

(BOOT/R5:10 EZA0) ! and default device.

KA660 Firmware

3–21

2..

-EZA0

>>> BOOT /R5:220 XQA0 ! Boot using supplied boot flags

(BOOT/R5:220 XQA0) ! (5 and 9) and device.

2..

-XQA0

3.9.2 CONFIGURE

The CONFIGURE command invokes an interactive mode that permits you to enter Q22-bus device names, then generates a table of Q22-bus

I/O page device CSR addresses and interrupt vectors. CONFIGURE is similar to the VMS SYSGEN CONFIG utility. This command simplifies field configuration by providing information that is typically available only with a running operating system. Refer to the example below and use the

CONFIGURE command as follows:

1. Enter CONFIGURE at the console I/O prompt.

2. Enter HELP at the

Device, Number?

prompt to see a list of devices whose CSR addresses and interrupt vectors can be determined.

3. Enter the device names and number of devices.

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

The devices listed in the HELP display are not necessarily supported by the KA660–AA CPU.

Format:

CONFIGURE

Example:

>>> CONFIGURE

Enter device configuration, HELP, or EXIT

Device,Number? HELP

Devices:

LPV11

RLV12

DMV11

RRD50

KXJ11

TSV05

DELQA

RQC25

DLV11J

RXV21

DEQNA

KFQSA-DISK

DZQ11

DRV11W

DESQA

TQK50

RV20

CXA16

LNV21

KWV11C

DRQ3B

IDV11D

DESNA

KWV32

Numbers:

KFQSA-TAPE

CXB16

QPSS

ADV11D

VSV21

IAV11A

IGQ11

KZQSA

KMV11

CXY08

DSV11

AAV11D

IBQ01

IAV11B

DIV32

IEQ11

VCB01

ADV11C

VCB02

IDV11A

MIRA

KIV32

DZV11

DRV11B

RQDX3

TQK70

DHQ11

QVSS

AAV11C

QDSS

IDV11B

ADQ32

DTCN5

DFA01

DPV11

KDA50

TU81E

DHV11

LNV11

AXV11C

DRV11J

IDV11C

DTC04

DTC05

3–22

KA660 CPU System Maintenance

1 to 255, default is 1

Device,Number? kda50

Device,Number? kfqsa

Device is ambiguous

Device,Number? kfqsa-disk

Device,Number? kfqsa-tape

Device,Number? cxy08

Device,Number? cxa16

Device,Number? exit

Address/Vector Assignments

-772150/154 KDA50

-760334/300 KFQSA-DISK

-774500/260 KFQSA-TAPE

-760500/310 CXY08

-760520/320 CXA16

>>>

KA660 Firmware

3–23

3.9.3 CONTINUE

The CONTINUE command causes the processor to begin instruction execution at the address currently contained in the PC. It does not perform a processor initialization. The console enters program I/O mode.

Format:

CONTINUE

Example:

>>> CONTINUE

3.9.4 DEPOSIT

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

Format:

DEPOSIT [qualifier_list] {address} {data} [data...]

Qualifiers:

Data control:

/B, /W, /L, /Q, /N:{count}, /STEP:{size}, /WRONG

Address space control:

/G, /I, /P, /V, /U

Arguments:

{address} A longword address that specifies the first location into which data is deposited.

The address can be an actual address or a symbolic address.

{data} The data to be deposited. If the specified data is larger than the deposit data size, the firmware ignores the command and issues an error response. If the specified data is smaller than the deposit data size, it is extended on the left with zeros.

[data]

Examples:

Additional data to be deposited (as many as can fit on the command line).

>>> D/P/B/N:1FF 0 0 ! Clear first 512 bytes of physical memory.

>>> D/V/L/N:3 1234 5 ! Deposit 5 into four longwords starting

! at virtual memory address 1234.

>>> D/N:8 R0 FFFFFFFF ! Loads GPRs R0 through R8 with -1.

3–24

KA660 CPU System Maintenance

>>> D/N:200 - 0 ! Starting at previous address, clear 513

! bytes.

>>> D/L/P/N:10/S:200 0 8 ! Deposit 8 in the first longword of

! the first 17 pages in physical

! memory.

3.9.5 EXAMINE

The EXAMINE command examines the contents of the memory location or register specified by the address. If no address is specified, + is assumed.

The display line consists of a single character address specifier, the physical address to be examined, and the examined data.

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

Format:

EXAMINE [qualifier_list] [address]

Qualifiers:

Data control:

/B, /W, /L, /Q, /N:{count}, /STEP:{size}, /WRONG, /

INSTRUCTION

Address space control:

/G, /I, /M, /P, /V, /U

Command specific:

/INSTRUCTION Disassembles and displays the VAX Macro-32 instruction at the specified address.

Arguments:

[address] A longword address that specifies the first location to be examined. The address can be an actual or a symbolic address. If no address is specified,

+ is assumed.

Examples:

KA660 Firmware

3–25

>>> EX PC

G 0000000F FFFFFFFC

>>> EX SP

G 0000000E 00000200

>>> EX PSL

M 00000000 041F0000

>>> E/M

M 00000000 041F0000

>>> E R4/N:5

G 00000004 00000000

G 00000005 00000000

G 00000006 00000000

G 00000007 00000000

G 00000008 00000000

G 00000009 801D9000

>>> EXPR$_SCBB

I 00000011 2004A000

>>> E/P 0

P 00000000 00000000

! Examine the PC.

! Examine the SP.

! Examine the PSL.

! Examine PSL another way.

! Examine R4 through R9.

! Examine the SCBB, IPR 17

! (decimal).

! Examine local memory 0.

>>> EX /INS 20040000

P 20040000 11 BRB

>>> E /INS

P 20040048 DB MFPR

>>>

! Examine 1st byte of ROM.

20040019

>>> EX /INS/N:5 20040019

P 20040019 D0 MOVL

! Disassemble from branch.

I^#20140000,@#20140000

P 20040024 D2 MCOML @#20140030,@#20140502

P 2004002F D2 MCOML S^#0E,@#20140030

P 20040036 7D MOVQ

P 2004003D D0 MOVL

P 20040044 DB MFPR

R0,@#201404B2

I^#201404B2,R1

S^#2A,B^44(R1)

! Look at next instruction.

S^#2B,B^48(R1)

3.9.6 FIND

The FIND command searches main memory starting at address zero for a page-aligned 128-Kbyte segment of good memory, or a restart parameter block (RPB). If the command finds the segment or RPB, its address plus

512 is left in SP (R14). If it does not find the segment or RPB, the console issues an error message and preserves the contents of SP. If you do not specify a qualifier, /RPB is assumed.

Format:

FIND [qualifier-list]

Qualifiers:

3–26

KA660 CPU System Maintenance

Command specific:

/MEMORY Searches memory for a page-aligned block of good memory, 128 Kbytes in length.

The search looks only at memory that is deemed usable by the bitmap. This command leaves the contents of memory unchanged.

/RPB Searches all of physical memory for an RPB. The search does not use the bitmap to qualify which pages are looked at. The command leaves the contents of memory unchanged.

Examples:

>>> EX SP

G 0000000E 00000000

>>> FIND /MEM

>>> EX SP

G 0000000E 00000200

>>> FIND /RPB

?2C FND ERR 00C00004

>>>

! Check the SP.

! Look for a valid 128 Kbyte.

! Note where it was found.

! Check for valid RPB.

! None to be found here.

3.9.7 HALT

The HALT command has no effect. It is included for compatibility with other VAX consoles.

Format:

HALT

Example:

>>> HALT

>>>

! Pretend to halt.

3.9.8 HELP

The HELP command provides information about command syntax and usage.

Example:

>>>HELP

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

UPPERCASE denotes a keyword that you must type in

| denotes an OR condition

[]

<> denotes optional parameters denotes a field specifying a syntactically correct value

..

...

denotes one of an inclusive range of integers denotes that the previous item may be repeated

KA660 Firmware

3–27

Valid qualifiers:

/B /W /L /Q /INSTRUCTION

/G /I /V /P /M

/STEP: /N: /NOT

/WRONG /U

Valid commands:

BOOT [/R5:<boot_flags> | /<boot_flags>]

[<boot_device>[:]]

CONFIGURE

CONTINUE

DEPOSIT [<qualifiers>] <address> [<datum>

[<datum>]]

EXAMINE [<qualifiers>] [<address>]

FIND [/MEMORY | /RPB]

HALT

HELP

INITIALIZE

MOVE [<qualifiers>] <address> <address>

NEXT [count]

REPEAT <command>

SEARCH [<qualifiers>] <address> <pattern> [<mask>]

SET BFL(A)G <boot_flags>

SET BOOT <boot_device>

SET CONTROLP <0..1 | DISABLED | ENABLED>

SET HALT <0..4 | DEFAULT | RESTART | REBOOT | HALT | RESTART_REBOOT>

SET HOST/DUP/DSSI <node_number> [<task>]

SET HOST/DUP/UQSSP </DISK | /TAPE> <controller_number> [<task>]

SET HOST/DUP/UQSSP <physical_CSR_address> [<task>]

SET HOST/MAINTENANCE/UQSSP/SERVICE <controller_number>

SET HOST/MAINTENANCE/UQSSP <physical_CSR_address>

SET LANGUAGE <1..15>

SET RECALL <0..1 | DISABLED | ENABLED>

SHOW BFL(A)G

SHOW BOOT

SHOW DEVICE

SHOW DSSI

SHOW ETHERNET

SHOW HALT

SHOW LANGUAGE

SHOW MEMORY [/FULL]

SHOW RECALL

SHOW RLV12

SHOW QBUS

SHOW UQSSP

SHOW SCSI

SHOW TRANSLATION <physical_address>

SHOW VERSION

START <address>

TEST [<test_code> [<parameters>]]

UNJAM

X <address> <count>

>>>

3–28

KA660 CPU System Maintenance

3.9.9 INITIALIZE

The INITIALIZE command performs a processor initialization.

Format:

INITIALIZE

The following registers are initialized:

Register State at Initialization

PSL

IPL

ASTLVL

SISR

ICCS

RXCS

TXCS

MAPEN

Cache

Instruction buffer

Console previous reference

TODR

Main memory

General registers

Halt code

Bootstrap-in-progress flag

Uneffected

Uneffected

Uneffected

Internal restart-in-progress flag Uneffected

4

0

041F0000

1F

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

0

80

0

Enabled and flushed

Uneffected

Longword, physical, address 0

Uneffected

Uneffected

The firmware clears all error status bits and initializes the following:

CDAL bus timer

Address decode and match registers

Programmable timer interrupt vectors

SSCCR

Example:

>>> INIT

>>>

KA660 Firmware

3–29

3.9.10 MOVE

The MOVE command copies the block of memory starting at the source address to a block beginning at the destination address. Typically, this command has an /N qualifier so that more than one data is transferred.

The destination correctly reflects the contents of the source, regardless of the overlap between the source and the data.

The MOVE command actually performs byte, word, longword, and quadword reads and writes as needed in the process of moving the data.

Moves are supported only for the physical and virtual address spaces.

Format:

MOVE [qualifier-list] {src_address} {dest_address}

Qualifiers:

Data control:

/B, /W, /L, /W, /N:{count}, /STEP:{size}, /WRONG

Address space control:

/V, /U, /P

Arguments:

{src_address} A longword address that specifies the first location of the source data to be copied.

{dest_address} A longword address that specifies the destination of the first byte of data.

These addresses may be an actual address or a symbolic address. If no address is specified, + is assumed.

Examples:

! Observe destination.

>>> EX/N:4 0

P 00000000 00000000

P 00000004 00000000

P 00000008 00000000

P 0000000C 00000000

P 00000010 00000000

>>> EX/N:4 200

P 00000200 58DD0520

P 00000204 585E04C1

P 00000208 00FF8FBB

P 0000020C 5208A8D0

P 00000210 540CA8DE

>>> MOV/N:4 200 0

! Observe source data.

! Move the data.

3–30

KA660 CPU System Maintenance

>>> EX/N:4 0

P 00000000 58DD0520

P 00000004 585E04C1

P 00000008 00FF8FBB

P 0000000C 5208A8D0

P 00000010 540CA8DE

>>>

! Observe moved data.

3.9.11 NEXT

The NEXT command executes the specified number of macro instructions.

If no count is specified, 1 is assumed.

After the last macro instruction is executed, the console reenters console

I/O mode.

Format:

NEXT {count}

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

The following restrictions apply:

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

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

• The NEXT command elevates the IPL to 31 for long periods of time

(milliseconds) while single stepping over several commands.

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

Arguments:

{count} A value representing the number of macro instructions to execute.

Examples:

KA660 Firmware

3–31

>>> DEP 1000 50D650D4

>>> DEP 1004 125005D1

>>> DEP 1008 00FE11F9

>>> EX /INSTRUCTION /N:5 1000

P 00001000

P 00001002

P 00001004

P 00001007

D4 CLRL

D6 INCL

D1 CMPL

12 BNEQ

R0

R0

S^#05,R0

00001002

00001009 P 00001009

P 0000100B

11 BRB

00 HALT

>>> DEP PR$_SCBB 200

>>> DEP PC 1000

>>>

>>> N

P 00001002

P 00001004

P 00001007

P 00001002

>>> N 5

P 00001004

P 00001007

P 00001002

P 00001004

D6 INCL

D1 CMPL

12 BNEQ

D6 INCL

D1 CMPL

12 BNEQ

D6 INCL

D1 CMPL

12 BNEQ

R0

S^#05,R0

00001002

R0

S^#05,R0

00001002

R0

S^#05,R0

00001002 P 00001007

>>> N 7

P 00001002

P 00001004

P 00001007

P 00001002

P 00001004

P 00001007

P 00001009

>>> N

P 00001009

>>>

D6 INCL

D1 CMPL

12 BNEQ

D6 INCL

D1 CMPL

12 BNEQ

11 BRB

11 BRB

R0

S^#05,R0

00001002

R0

S^#05,R0

00001002

00001009

00001009

! Create a simple program.

! List it.

! Set up a user SCBB...

! ...and the PC.

! Single step...

! SPACEBAR

! SPACEBAR

! SPACEBAR

! CR

! ...or multiple step the program.

3.9.12 REPEAT

The REPEAT command repeatedly displays and executes the specified command. Press

CTRL/C to stop the command. You can specify any valid console command, except the REPEAT command.

Format:

REPEAT {command}

Arguments:

{command} A valid console command other than REPEAT.

Examples:

3–32

KA660 CPU System Maintenance

>>>REPEAT EXAMINE 0

P 00000000 00000004

P 00000000 00000004

P 00000000 00000004

P 00000000 00000004

P 00000000 00000004

P 00000000 00000004

P 00000000 00000004

P 0000^C

>>>

3.9.13 SEARCH

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

Format:

SEARCH [qualifier_list] {address} {pattern} [mask]

SEARCH accepts an optional mask that indicates bits to be ignored (

don’t care

bits). For example, to ignore bit 0 in the comparison, specify a mask of 1. The mask, if not present, defaults to 0.

A match occurs if (pattern AND mask complement) = (data AND mask complement), where: pattern is the target data mask is the optional don’t care bitmask (which defaults to 0) data is the data at the current address

SEARCH reports the address under the following conditions:

/NOT Qualifier

Absent

Absent

Present

Present

Match Condition

True

False

True

False

Action

Report address

No report

No report

Report address

The address is advanced by the size of the pattern (byte, word, longword, or quadword), unless overridden by the /STEP qualifier.

Qualifiers:

Data control:

/B, /W, /L, /Q, /N:{count}, /STEP:{size}, /WRONG, /NOT

Address space control:

/P, /V, /U

KA660 Firmware

3–33

Command specific:

/NOT Inverts the sense of the match.

Arguments:

{start_address} A longword address that specifies the first location subject to the search. This address can be an actual address or a symbolic address. If no address is specified, + is assumed.

{pattern} The target data.

[{mask}] A mask of the bits desired in the comparison.

Examples:

9wide\maximum)

>>>DEP /P/L/N:1000 0 0

>>>

! Clear some memory.

>>>DEP 300 12345678\BOLD) ! Deposit some "search" data.

>>>DEP 401 12345678\BOLD)

>>>DEP 502 87654321\BOLD)

>>>

>>>SEARCH /N:1000 /ST:1 0 12345678 ! Search for all occurances...

P 00000300 12345678

P 00000401 12345678

! ...of 12345678 on any byte...

! ...boundary.

>>>SEARCH /N:1000 0 12345678 ! Then try on longword...

P 00000300 12345678 ! ...boundaries.

>>>SEARCH /N:1000 /NOT 0 0 ! Search for all non-zero...

P 00000300 12345678 ! ...longwords.

P 00000400 34567800

P 00000404 00000012

P 00000500 43210000

P 00000504 00008765

>>>SEARCH /N:1000 /ST:1 0 1 FFFFFFFE ! Search for "odd" longwords...

P 00000502 87654321 ! ...on any boundary.

P 00000503 00876543

P 00000504 00008765

P 00000505 00000087

>>>SEARCH /N:1000 /B 0 12 ! Search for all occurrances...

P 00000303 12 ! ...of the byte 12.

P 00000404 12

>>>SEARCH /N:1000 /ST:1 /w 0 FE11 ! Search for all words which...

>>>

>>>

>>> ! Note, none found.

! ...could be interpretted as...

! ...a "spin" (10$: brb 10$).

3–34

KA660 CPU System Maintenance

3.9.14 SET

The SET command sets the parameter to the value you specify.

Format:

SET {parameter} {value}

Parameters:

BFLAG Set the default R5 boot flags. The value must be a hexadecimal number of up to 8 digits. See Table 3–9 under the BOOT command description for a list of the boot flags.

BOOT

CONTROLP

HALT

Set the default boot device. The value must be a valid device name as specified in the BOOT command description Section 3.9.1.

Set Control-P as the console halt condition instead of break. Value of 1 sets Control-P; value of 0 disables Control-P.

Set the user-defined halt action; acceptable values are 0 through 4 or the following keywords: DEFAULT, RESTART, REBOOT, HALT, and

RESTART_REBOOT.

KA660 Firmware

3–35

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

/DUP

—Use the DUP driver to execute local programs of a device on either the DSSI bus or the Q22-bus.

/DSSI node

—Attach to the DSSI node. A node is a name up to 8 characters in length or a number from 0 to 7. OB

/UQSSP

—Attach to the UQSSP device specified using one of the following methods:

/DISK n

—Specifies the disk controller number, where n is a number from 0 to 255. The resulting fixed address for n=0 is

20001468 and the floating rank for n>0 is 26.

/TAPE n

—Specifies the tape controller number, where n is a number from 0 to 255. The resulting fixed address for n=0 is

20001940 and the floating rank for n>0 is 30.

csr_address

—Specifies the Q22-bus I/O page CSR address for the device.

/MAINTENANCE

—Examines and modifies KFQSA EEPROM configuration parameters. Does not accept a task value.

/UQSSP

— Attach to the UQSSP device specified using one of the following methods:

/SERVICE n

—Specifies the KFQSA module n where n is a value from 0 to 3. (The resulting fixed address of a KFQSA module in service mode is 20001910+4*n.)

/csr_address

—Specifies the Q22-bus I/O page CSR address for the KFQSA.

LANGUAGE Sets console language and keyboard type. If the current console terminal does not support the Digital Multinational Character Set (MCS), then this command has no effect and the console message appears in English.

Values are 1 through 15. Refer to Example 3–1 for the languages you can select.

RECALL Sets command recall state to either 1 or 0 (ENABLED or DISABLED).

Qualifiers:

Listed in the parameter descriptions above.

Examples:

>>>

>>> SET BFLAG 220

>>>

>>> SET BOOT

>>>

>>> SET CONTROLP 0

>>>

>>> SET HALT REBOOT

>>>

>>> SET HOST/DUP/DSSI 0

Starting DUP server...

3–36

KA660 CPU System Maintenance

DSSI Node 0 (SUSAN)

Copyright © 1990 Digital Equipment Corporation

DRVEXR V1.0

D 5-JUL-1990 15:33:06

DRVTST V1.0

D 5-JUL-1990 15:33:06

HISTRY V1.0

D 5-JUL-1990 15:33:06

ERASE V1.0

D 5-JUL-1990 15:33:06

PARAMS V1.0

D 5-JUL-1990 15:33:06

DIRECT V1.0

D 5-JUL-1990 15:33:06

End of directory

Task Name?

params

Copyright © 1990 Digital Equipment Corporation

PARAMS>

stat path

ID Path Block Remote Node DGS_S DGS_R MSGS_S MSGS_R

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

0 PB FF811ECC Internal Path

6 PB FF811FD0 KFQSA KFX V1.0

0

0

0

0

0

0

0

0

1 PB FF8120D4 KAREN RFX V101

4 PB FF8121D8 WILMA RFX V101

5 PB FF8122DC BETTY RFX V101

2 PB FF8123E0 DSSI1 VMS V5.0

3 PB FF8124E4 3 VMB BOOT

0

0

0

0

0

0

0

0

0

0

0

0

0

14328

61

0

0

0

14328

61

PARAMS>

exit

Exiting...

Task Name?

Stopping DUP server...

>>>

>>> SET HOST/DUP/DSSI 0 PARAMS

Starting DUP server...

DSSI Node 0 (SUSAN)

Copyright © 1990 Digital Equipment Corporation

PARAMS>

show node

Parameter Current Default Type Radix

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

NODENAME SUSAN RF30 String Ascii

PARAMS> SHOW ALLCLASS

Parameter Current Default Type Radix

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

ALLCLASS 1 0 Byte Dec

PARAMS> EXIT

Exiting...

Stopping DUP server...

>>>

>>> SET HOST /DUP/DSSI/BUS:1

0

Starting DUP server...

B

B

KA660 Firmware

3–37

DSSI Bus 1 Node 0 (SUSAN)

Copyright © 1990 Digital Equipment Corporation

DRVEXR V1.0

D 5-JUL-1990 15:33:06

DRVTST V1.0

D 5-JUL-1990 15:33:06

HISTRY V1.0

D 5-JUL-1990 15:33:06

ERASE V1.0

D 5-JUL-1990 15:33:06

PARAMS V1.0

D 5-JUL-1990 15:33:06

DIRECT V1.0

D 5-JUL-1990 15:33:06

End of directory

Task Name?

params

Copyright © 1990 Digital Equipment Corporation

PARAMS>

stat path

ID Path Block Remote Node DGS_S DGS_R MSGS_S MSGS_R

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

0 PB FF811ECC Internal Path

6 PB FF811FD0 KFQSA KFX V1.0

0

0

0

0

0

0

0

0

1 PB FF8120D4 KAREN RFX V101

4 PB FF8121D8 WILMA RFX V101

5 PB FF8122DC BETTY RFX V101

2 PB FF8123E0 DSSI1 VMS V5.0

3 PB FF8124E4 3 VMB BOOT

0

0

0

0

0

0

0

0

0

0

0

0

0

14328

61

0

0

0

14328

61

PARAMS>

exit

Exiting...

Task Name?

Stopping DUP server...

>>>

>>> SET HOST /DUP/DSSI/BUS:1 0 PARAMS

Starting DUP server...

DSSI Bus 1 Node 0 (SUSAN)

Copyright © 1990 Digital Equipment Corporation

PARAMS> show node

Parameter Current Default Type Radix

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

NODENAME SUSAN RF31 String Ascii

PARAMS>

show allclass

Parameter Current Default Type Radix

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

ALLCLASS 1 0 Byte Dec

PARAMS> exit

Exiting...

Stopping DUP server...

>>>

>>> SET HOST /MAINT/UQSSP 20001468

UQSSP Controller (772150)

B

B

3–38

KA660 CPU System Maintenance

Enter SET, CLEAR, SHOW, HELP, EXIT, or QUIT

Node CSR Address Model

0

1

772150

760334

21

21

4

5

7

? HELP

760340

760344

21

21

------ KFQSA ------

Commands:

SET <node> /KFQSA

SET <node> <CSR_address> <model>

CLEAR <node>

SHOW

HELP

EXIT

QUIT set KFQSA DSSI node number enable a DSSI device disable a DSSI device show current configuration print this text program the KFQSA don’t program the KFQSA

Parameters:

<node>

<CSR_address>

<model>

?

set 6 /kfqsa

?

show

Node

0

1

4

CSR Address

772150

760334

760340

Model

21

21

21

5

6

760344 21

------ KFQSA ------

?

EXIT

Programming the KFQSA...

>>>

>>> SET LANGUAGE 5

>>>

>>> SET RECALL 1

>>>

>>> SET VERIFICATION CATNMOUSE

0 to 7

760010 to 777774

21 (disk) or 22 (tape)

3.9.15 SHOW

The SHOW command displays the console parameter you specify.

Format:

SHOW {parameter}

Parameters:

BFLAG Displays the default R5 boot flags.

BOOT

CONTROLP

DEVICE

Displays the default boot device.

Displays current state of halt recognition, either ENABLED or

DISABLED.

Displays all devices displayed by the SHOW DSSI, SHOW ETHERNET, and SHOW UQSSP commands.

KA660 Firmware

3–39

DSSI

ETHERNET

HALT

LANGUAGE

MEMORY

QBUS

RECALL

RLV12

Displays the status of all nodes that can be found on the DSSI bus. For each node on the DSSI bus, the firmware displays the node number, the node name, and the boot name and type of the device, if available. The command does not indicate if the device contains a bootable image.

The node that issues the command is listed with a node name of *

(asterisk).

The device information is obtained from the media type field of the MSCP command GET UNIT STATUS. If a node is not running or is not capable of running an MSCP server, then no device information is displayed.

Displays hardware Ethernet address for all Ethernet adapters that can be found, both on-board and on the Q22-bus. Displays as blank if no

Ethernet adapter is present.

Show the user-defined halt action.

Displays console language and keyboard type. Refer to the corresponding

SET LANGUAGE command for the meaning.

Displays main memory configuration board by board.

/FULL

—Additionally, displays the normally inaccessible areas of memory, such as the PFN bitmap pages, the console scratch memory pages, the Q22-bus scatter/gather map pages. Also reports the addresses of bad pages, as defined by the bitmap.

Displays all Q22-bus I/O addresses that respond to an aligned word read, and vector and device name information. For each address, the console displays the address in the VAX I/O space in hexadecimal, the address as it would appear in the Q22-bus I/O space in octal, and the word data that was read in hexadecimal.

This command may take several minutes to complete. Press

CTRL/C to terminate the command. During execution, the command disables the scatter/gather map.

Shows the current state of command recall, either ENABLED or

DISABLED.

Displays all RL01 and RL02 disks that appear on the Q22-bus.

3–40

KA660 CPU System Maintenance

SCSI

TRANSLATION

UQSSP

Shows any SCSI devices on the system.

Shows any virtual addresses that map to the specified physical address.

The firmware uses the current values of page table base and length registers to perform its search; it is assumed that page tables have been properly built.

Displays the status of all disks and tapes that can be found on the Q22bus that support the UQSSP protocol. For each such disk or tape on the Q22-bus, the firmware displays the controller number, the controller

CSR address, and the boot name and type of each device connected to the controller. The command does not indicate if the device contains a bootable image.

This information is obtained from the media type field of the MSCP command GET UNIT STATUS. The console does not display device information if a node is not running (or cannot run) an MSCP server.

VERSION Displays the current firmware version.

Qualifiers:

Listed in the parameter descriptions above.

Examples:

>>>

>>> SHOW BFLAG

00000220

>>>

>>> SHOW BOOT

>>>

>>> SHOW DEVICE

DSSI Bus 0 Node 0 (SUSAN)

-DIA0 (RF31)

DSSI Bus 0 Node 1 (KAREN)

-DIA1 (RF31)

DSSI Bus 0 Node 3 (*)

DSSI Bus 0 Node 4 (WILMA)

-DIA4 (RF31)

DSSI Bus 0 Node 5 (BETTY)

-DIA5 (RF31)

DSSI Bus 0 Node 6 (KFQSA)

SCSI Adapter 0 (761300), SCSI ID 7

-DKA100 (DEC RZ31 (C) DEC)

-DKA300 (MAXTOR XT-8000S)

UQSSP Disk Controller 0 (772150)

-DUA0 (RF31)

UQSSP Disk Controller 1 (760334)

-DUB1 (RF31)

UQSSP Disk Controller 2 (760340)

-DUC3 (RF31)

UQSSP Disk Controller 3 (760344)

-DUD4 (RF31)

KA660 Firmware

3–41

Ethernet Adapter

-(08-00-2B-03-82-78)

>>>

>>> SHOW DSSI

DSSI Bus 0 Node 0 (SUSAN)

-DIA0 (RF31)

DSSI Bus 0 Node 1 (KAREN)

-DIA1 (RF31)

DSSI Bus 0 Node 3 (*)

DSSI Bus 0 Node 4 (WILMA)

-DIA4 (RF31)

DSSI Bus 0 Node 5 (BETTY)

-DIA5 (RF31)

DSSI Bus 0 Node 6 (KFQSA)

>>>

>>> SHOW ETHERNET

Ethernet Adapter

-(08-00-2B-03-82-78)

>>>

>>> SHOW HALT

Reboot

>>> SHOW LANGUAGE

English (United States/Canada)

>>>

>>> SHOW MEMORY

Memory 0: 00000000 to 003FFFFF, 4MB, 0 bad pages

Total of 4MB, 0 bad pages, 98 reserved pages

>>>

>>> SHOW MEMORY /FULL

Memory 0: 00000000 to 003FFFFF, 4MB, 0 bad pages

Total of 4MB, 0 bad pages, 98 reserved pages

Memory Bitmap

-003F3C00 to 003F3FFF, 2 pages

Console Scratch Area

-003F4000 to 003F7FFF, 32 pages

Qbus Map

-003F8000 to 003FFFFF, 64 pages

Scan of Bad Pages

>>>

>>> SHOW QBUS

Scan of Qbus I/O Space

-200000DC (760334) = 0000 (300) RQDX3/KDA50/RRD50/RQC25/KFQSA-DISK

-200000DE (760336) = 0AA0

-200000E0 (760340) = 0000 (304) RQDX3/KDA50/RRD50/RQC25/KFQSA-DISK

-200000E2 (760342) = 0AA0

-200000E4 (760344) = 0000 (310) RQDX3/KDA50/RRD50/RQC25/KFQSA-DISK

-200000E6 (760346) = 0AA0

-20001468 (772150) = 0000 (154) RQDX3/KDA50/RRD50/RQC25/KFQSA-DISK

-2000146A (772152) = 0AA0

-20001F40 (777500) = 0020 (004) IPCR

3–42

KA660 CPU System Maintenance

Scan of Qbus Memory Space

>>>

>>> SHOW RLV12

>>>

>>> SHOW SCSI

SCSI Adapter 0 (761300), SCSI ID 7

-DKA100 (DEC RZ31 (C) DEC)

-DKA300 (MAXTOR XT-8000S)

>>>

>>> SHOW TRANSLATION 1000

V 80001000

>>>

>>> SHOW UQSSP

UQSSP Disk Controller 0 (772150)

-DUA0 (RF31)

UQSSP Disk Controller 1 (760334)

-DUB1 (RF31)

UQSSP Disk Controller 2 (760340)

-DUC4 (RF31)

UQSSP Disk Controller 3 (760344)

-DUD5 (RF31)

>>>

>>> SHOW VERIFICATION wadenmargo

>>>

>>> SHOW VERSION

KA660-A V4.0, VMB 2.12

>>>

3.9.16 START

The START command starts instruction execution at the address you specify. If no address is given, the current PC is used. If memory mapping is enabled, macro instructions are executed from virtual memory, and the address is treated as a virtual address. The START command is equivalent to a DEPOSIT to PC, followed by a CONTINUE. It does not perform a processor initialization.

Format:

START [{address}]

Arguments:

[address] The address at which to begin execution. This address is loaded into the user’s

PC.

Example:

>>> START 1000

KA660 Firmware

3–43

3.9.17 TEST

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

Refer to Chapter 4 for a detailed explanation of the diagnostics.

Format:

TEST [test_number [test_arguments]]

Arguments:

{test_number} A two-digit hexadecimal number specifying the test to be executed.

{test_arguments} Up to five additional test arguments. These arguments are accepted but they have no meaning to the console.

Examples:

KA660-A T3.5-14, VMB 2.12

Performing normal system tests.

95..94..93..92..91..90..89..88..87..86..85..84..83..82..81..80..

79..78..77..76..75..74..73..72..71..70..69..68..67..66..65..64..

63..62..61..60..59..58..57..56..55..54..53..52..51..50..49..48..

47..46..45..44..43..42..41..40..39..38..37..36..35..34..33..32..

31..30..29..28..27..26..25..24..23..22..21..20..19..18..17..16..

15..14..13..12..11..10..09..08..07..06..05..04..03..

Tests completed.

>>>>>>T 9E

Test

# Address Name Parameters

___________________________________________________________________________

20052400 SCB

20053314 De_executive

30 2005D07C MS650_Init_Bitmap *** mark_Hard_SBEs ******

31 2005CE3C MS650_Setup_CSRs **********

32 2005C984 CMCTL regs

33 2005C940 CMCTL_powerup

MEMCSR0_addr *********

*

34 20054A24 SSC_ROM *

3F 2005EEBC MS650_FDM_Addr_shorts *** cont_on_err ******

40 2005F6A4 MS650_count_pages First_board Last_bd Soft_errs_allowed *******

41 20062718 Board_Reset *

42 20054AE4 Chk_for_Interrupts *****

43 2005AD88 SOC_DI_Cache_w_mem cache_config start_add end_add add_incr ******

44 2005A5BC SOC_D_Cache_w_Mem cache_config start_add end_add add_incr ******

45 2005A21C SOC_Cache_mem_CQBIC cache_config start_add end_add add_incr ******

46 2005B2A4 SOC_Cache1_diag_mode cache_config addr_incr ********

47 2005F434 MS650_Refresh start_a end incr cont_on_err time_seconds *****

48 2005EAF4 MS650_Addr_shorts start_add end_add * cont_on_err pat2 pat3 ****

49 2005E530 MS650_FDM *** cont_on_err ******

4A 2005E288 MS650_ECC_SBEs start_add end_add add_incr cont_on_err ******

4B 2005E048 MS650_Byte_Errors start_add end_add add_incr cont_on_err ******

4C 2005DAEC MS650_ECC_Logic

4D 2005D95C MS650_Address

4E 2005D768 MS650_Byte start_add end_add add_incr cont_on_err ****** start_add end_add add_incr cont_on_err ****** start_add end_add add_incr cont_on_err ******

3–44

KA660 CPU System Maintenance

4F 2005D4BC MS650_Data

51 200627E7 FPA

52 20055090 SSC_Prog_timers

53 20055360 SSC_TOY_Clock start_add end_add add_incr cont_on_err ******

******* which_timer wait_time_us *** repeat_test_250ms_ea Tolerance ***

54 20054BB9 Virtual_Mode

55 20055512 Interval_Timer

*********

*

58 20061370 SHAC_RESET dssi_bus port_number time_secs

59 200604C4 SGEC_LPBCK_ASSIST time_secs **

5A 2005A120 SOC_CMCTL

5C 20060A2C SHAC

5F 2005F878 SGEC

60 20059D51 SSC_Console_SLU dont_report_memory_bad repeat_count * shac_number ******* loopback_type no_ram_tests ****** start_BAUD end_BAUD ******

62 20055950 console_QDSS

63 20055ACC QDSS_any mark_not_present selftest_r0 selftest_r1 ***** input_csr selftest_r0 selftest_r1 ******

80 20059731 CQBIC_memory_LMGH **********

81 200555B4 Qbus_MSCP IP_csr ******

82 20055779 Qbus_DELQA

83 200569CA QZA_LPBCK1

84 20058070 QZA_LPBCK2

85 20055C28 QZA_memory

86 200560E4 QZA_DMA

87 200592B0 QZA_EXTLPBCK

90 2005500E CQBIC_registers

91 20054FA4 CQBIC_powerup device_num_addr **** controller_number ******** controller_number ********* incr test_pattern controller_number *******

Controller_number main_mem_buf ******** controller_number ****

*

**

99 200629F5 Flush_Ena_Caches

9A 200618FC INTERACTION dis_flush_cache ********* pass_count disable_device ****

9B 200625D8 Init_memory_4MB *

9C 2005BB4A List_CPU_registers *

9D 2005C826 Utility

9E 20055586 List_diagnostics

9F 20062B32 Create_A0_Script

C1 200546D0 SSC_RAM_Data

Expnd_err_msg get_mode init_LEDs clr_ps_cnt

*

**********

*

C2 200548A6 SSC_RAM_Data_Addr *

C5 20059581 SSC_registers *

C6 20054614 SSC_powerup *********

C7 2005967C SSC_CBTCR_timeout ***

Scripts

# Description

A0 User defined scripts

A1 Powerup tests, Functional Verify, continue on error, numeric countdown

A3 Functional Verify, stop on error, test # announcements

A4 Loop on A3 Functional Verify

A5 Address shorts test, run fastest way possible

A6 Memory tests, mark only multiple bit errors

A7 Memory tests

A8 Memory acceptance tests, mark single and multi-bit errors, call A7

A9 Memory tests, stop on error

B5 SOC Cache debug script

>>>! List all diagnostic tests

KA660 Firmware

3–45

>>>>>>T 9C

SBR=017B8000

P0BR=80000000

TODR=0010E085

TCR0=00000000

TCR1=00000001

RXCS=00000000

SCR=0000D000

SLR=00002021 SAVPC=20044827 SAVPSL=04190304

P0LR=00100A80

ICCS=00000000

TIR0=00000000

P1BR=0A0A0A08

TNIR0=00000000

P1LR=000B0B0B

MAPEN=00000000

TIVR0=00000078

TIR1=0052680A TNIR1=0000000F TIVR1=0000007C

RXDB=0000000D TXCS=00000000

DSER=00000000 QBEAR=0000000F

TXDB=00000030

DEAR=00000000

BDR=08D0EFFF DLEDR=0000000C SSCCR=00D55537 CBTCR=00000004

DSSI_0=00 (BUS_0)

PSR_0=00000000

PQBBR_0=03060022

PESR_0=00000000

PMCSR_0=00000000

PFAR_0=00000000

SCBB=20052400

SID=14000006

BDMTR=20084000

BDMKR=0000007C

QBMBR=017F8000

IPCR0=0000

SSHMA_0=0000CA20

PPR_0=00000000

NICSR0=1FFF0003 3=00004030 4=00004050 5=8039FF00 6=83E0F000 7=00000000

NICSR9=04E204E2 10=00040000 11=00000000 12=00000000 13=00000000 15=0000FFFF

NISA=08-00-2B-12-BC-AC RDES0=00441300

TDES0=00008C80

1=00000000

1=07000000

2=05EE0000

2=00400000

3=000046F0

3=000040FA

MEM_FRU 1

MEM_FRU 2

MEM_FRU 3

MEM_FRU 4

MCSR_0=80000017

MCSR_4=81000016

MCSR_8=00000000

MCSR12=00000000

1=80400017

5=81400016

9=00000000

13=00000000

2=80800017

6=00000016

10=00000000

14=00000000

MEMCSR17=00000013 MEMCSR16=00000044 CSR16_page_address=00000000

MSER=00000000 CCR=00000014

3=80C00017

7=00000016

11=00000000

15=00000000

>>>T 9F

SP=201406A8

Script in ?[0=SSC, 2=RAM] :0

Script starts at 20140794

36 bytes left

Test number (? for list) or script number :80

CQBIC_memory_LMGH>> Run from ?[0=ROM, 2=RAM, 3=fastest possible] (0):0

CQBIC_memory_LMGH>> Error severity ? [0,1,2,3] (02):0

CQBIC_memory_LMGH>> Console error report? [0=none,1=full] (01):0

CQBIC_memory_LMGH>> Stop script on error? [0=NO,1=YES] (01):0

CQBIC_memory_LMGH>> Repeat? [0=no,1=forever,>1=count] (00):0

CQBIC_memory_LMGH>> LED on entry (01):0

CQBIC_memory_LMGH>> Console Announcement on entry (80):1

32 bytes left

Test number (? for list) or script number :1

No such diagnostic!

32 bytes left

Test number (? for list) or script number :

>>>

>>>! Execute test script.

>>>T FE

Bitmap=00FF3000, Length=00001000, Checksum=807F, Busmap=00FF8000

Test_number=41, Subtest=00, Loop_Subtest=00, Error_type=00

Error_vector=0000, Last_exception_PC=00000000, Severity=02

Total_error_count=0000, Led_display=0C, Console_display=03, save_mchk_code=80 parameter_1=00000000 2=00000000 3=00000000 4=00000000 5=00000000 parameter_6=00000000 7=00000000 8=00000000 9=00000000 10=00000000 previous_error=00000000, 00000000, 00000000, 00000000

Flags=00FFFC10440E, SET_mask=FF

Return_stack=201406D4, Subtest_pc=20062730, Timeout=00030D40

>>>

3–46

KA660 CPU System Maintenance

3.9.18 UNJAM

The UNJAM command performs an I/O bus reset, by writing a 1 (one) to

IPR 55 (decimal).

Format:

UNJAM

Examples:

>>> UNJAM

>>>

3.9.19 X—Binary Load and Unload

The X command is for use by automatic systems communicating with the console.

The X command loads or unloads (that is, writes to memory, or reads from memory) the specified number of data bytes through the console serial line

(regardless of console type) starting at the specified address.

Format:

X {address} {count} CR {line_checksum} {data} {data_checksum}

If bit 31 of the count is clear, data is received by the console and deposited into memory. If bit 31 is set, data is read from memory and sent by the console. The remaining bits in the count are a positive number indicating the number of bytes to load or unload.

The console accepts the command upon receiving the carriage return.

The next byte the console receives is the command checksum, which is not echoed. The command checksum is verified by adding all command characters, including the checksum and separating space (but not including the terminating carriage return, rubouts, or characters deleted by rubout), into an 8-bit register initially set to zero. If no errors occur, the result is zero. If the command checksum is correct, the console responds with the console I/O prompt and either sends data to the requester or prepares to receive data. If the command checksum is in error, the console responds with an error message. The intent is to prevent inadvertent operator entry into a mode where the console is accepting characters from the keyboard as data, with no escape mechanism possible.

If the command is a load (bit 31 of the count is clear), the console responds with the console I/O prompt (>>>), then accepts the specified number of bytes of data for depositing to memory, and an additional byte of received data checksum. The data is verified by adding all data characters and the checksum character into an 8-bit register initially set to zero. If the final

KA660 Firmware

3–47

content of the register is nonzero, the data or checksum is in error, and the console responds with an error message.

If the command is a binary unload (bit 31 of the count is set), the console responds with the console I/O prompt (>>>), followed by the specified number of bytes of binary data. As each byte is sent, it is added to a checksum register initially set to zero. At the end of the transmission, the two’s complement of the low byte of the register is sent.

If the data checksum is incorrect on a load, or if memory or line errors occur during the transmission of data, the entire transmission is completed, then the console issues an error message. If an error occurs during loading, the contents of the memory being loaded are unpredictable.

The console represses echo while it is receiving the data string and checksums.

The console terminates all flow control when it receives the carriage return at the end of the command line in order to avoid treating flow control characters from the terminal as valid command line checksums.

You can control the console serial line during a binary unload using control characters (

CTRL/C

,

CTRL/S

,

CTRL/O

, and so on). You cannot control the console serial line during a binary load, since all received characters are valid binary data.

The console has the following timing requirements:

• It must receive data being loaded with a binary load command at a rate of at least one byte every 60 seconds.

• It must receive the command checksum that precedes the data within

60 seconds of the carriage return that terminates the command line.

• It must receive the data checksum within 60 seconds of the last data byte.

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

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

3–48

KA660 CPU System Maintenance

3.9.20 !—Comment

The comment character (an exclamation point) is used to document command sequences. It can appear anywhere on the command line. All characters following the comment character are ignored.

Format:

!

Examples

>>> ! The console ignores this line.

>>>

KA660 Firmware

3–49

Chapter 4

Troubleshooting and Diagnostics

4.1 Introduction

This chapter contains a description of KA660 ROM-based diagnostics, acceptance test procedures, and power-up self-tests for common options.

4.2 General Procedures

Before troubleshooting any system problem, check the site maintenance guide for the system’s service history. Ask the system manager two questions:

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

• Have changes been made to the system recently?

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

• Incorrect cabling

• Module configuration errors (incorrect CSR addresses and interrupt vectors)

• Incorrect grant continuity

Most communications modules use floating CSR addresses and interrupt vectors. If you remove a module from the system, you may have to change the addresses and vectors of other modules.

If you change the system configuration, run the CONFIGURE utility at the console I/O prompt (

>>>

) to determine the CSR addresses and interrupt vectors recommended by Digital. These recommended values simplify the use of the MDM diagnostic package, and are compatible with VMS device drivers. Nonstandard addresses can be selected, but they require a special setup for use with VMS drivers and MDM.

When troubleshooting, note the status of cables and connectors before you perform each step. Label cables before you disconnect them to save time and prevent you from introducing new problems.

Troubleshooting and Diagnostics

4–1

If the system fails (or appears to fail) to boot the operating system, check the console terminal screen for an error message. If the terminal displays an error message, see Section 4.3. Check the LEDs on the device you suspect is faulty. If no errors are indicated by the device LEDs, run the

ROM-based diagnostics described in this chapter. In addition, check the following connections:

• If no message appears, make sure the console terminal and the system are on. Check the power switch on both the console terminal and the system. If the terminal has a green DC OK indicator, be sure it is on.

• Check the cabling to the console terminal.

• If you cannot get a display of any kind on the console terminal, try another terminal.

• If the system green DC OK LED remains off, check the power supply and power supply cabling.

• Check the hexadecimal display on the CPU cover panel. If the display is off, check the CPU module LEDs and the CPU cabling. If a hexadecimal error message appears on the cover panel or the module, see Section 4.3.

If the system boots successfully, but a device seems to fail or an intermittent failure occurs, check the error log first for a device problem. The failing device is usually in one of the following areas:

CPU

Memory

Mass storage

Communications devices

4.3 KA660 ROM-Based Diagnostics

The KA660 ROM-based diagnostic facility, rather than the MicroVAX Diagnostic Monitor (MDM), is the primary diagnostic tool for troubleshooting and testing of the CPU, memory, Ethernet, and DSSI subsystems. ROMbased diagnostics have significant advantages:

• Load time is virtually nonexistent.

• The boot path is more reliable.

• Diagnosis is done in a more primitive state. (MDM requires successful loading of the operating system.)

The ROM-based diagnostics can indicate several different FRUs, not just the CPU module. For example, they can isolate one of up to four memory modules as FRUs.

4–2

KA660 CPU System Maintenance

The diagnostics run automatically on power-up. While the diagnostics are running, the LEDs on the H3602–00 display a hexadecimal countdown of the tests from F to 3 (though not in precise reverse order) before booting the operating system, and 2 to 0 while booting the operating system. A different countdown appears on the console terminal.

The ROM-based diagnostics are a collection of individual tests with parameters that you can specify. A data structure called a

script

points to the tests. (See Section 4.3.2.) There are several field and manufacturing scripts. Qualified Customer Services personnel can also create their own scripts interactively.

A program called the

diagnostic executive

determines which of the available scripts to invoke.

The script sequence varies if the KA660 is in a manufacturing environment. The diagnostic executive interprets the script to determine what tests to run, the correct order to run the tests, and the correct parameters to use for each test.

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

4.3.1 Diagnostic Tests

Table 4–1 shows a list of the ROM-based tests and utilities. To get this listing, enter T 9E at the console prompt (T is the abbreviation of TEST).

The column headings have the following meanings:

• Test is the test code or utility code.

• Address is the test or utility’s base address in ROM. This address varies.

The addresses shown are examples only. If a test fails, entering T

FE displays diagnostic state to the console. You can subtract the base address of the failing test from the last_exception_pc to find the index into the failing test’s diagnostic listing (available on microfiche).

• Name is a brief description of the test or utility.

• Parameters shows the parameters for each diagnostic test or utility.

Tests accept up to ten parameters.

The asterisks (*) represent parameters that are used by the tests but that you cannot specify individually. These parameters are encoded in ROM and are provided by the diagnostic executive.

Troubleshooting and Diagnostics

4–3

Table 4–1: Test and Utility Numbers

Test

41

42

43

30

31

32

33

34

3F

40

44

45

46

47

48

49

4A

4B

4C

4D

4E

4F

51

52

53

54

55

Address

1

20052400

20053314

2005D07C

2005CE3C

2005C984

2005C940

20054A24

2005EEBC

2005F6A4

20062718

20054AE4

2005AD88

2005A5BC

2005A21C

2005B2A4

2005F434

2005EAF4

2005E530

2005E288

2005E048

2005DAEC

2005D95C

2005D768

2005D4BC

200627E7

20055090

20055360

20054BB9

20055512

Name Parameters

SCB

De_executive

MS650_Init_Bitmap

MS650_Setup_CSRs

CMCTL regs

CMCTL_powerup

SSC_ROM

*** mark_Hard_SBEs ******

**********

MEMCSR0_addr *********

*

*

MS650_FDM_Addr_shorts *** cont_on_err ******

MS650_count_pages First_board Last_bd Soft_errs_allowed

*******

Board_Reset

Chk_for_Interrupts

*

*****

SOC_DI_Cache_w_mem cache_config start_add end_add add_ incr ******

SOC_D_Cache_w_Mem cache_config start_add end_add add_ incr******

SOC_Cache_mem_CQBIC cache_config start_add end_add add_ incr ******

SOC_Cache1_diag_mode cache_config addr_incr ********

MS650_Refresh start_a end incr cont_on_err time_ seconds *****

MS650_Addr_shorts start_add end_add * cont_on_err pat2 pat3 ****

MS650_FDM

MS650_ECC_SBEs

MS650_Byte_Errors

MS650_ECC_Logic

MS650_Address

*** cont_on_err ****** start_add end_add add_incr cont_on_ err ****** start_add end_add add_incr cont_on_ err ****** start_add end_add add_incr cont_on_ err ****** start_add end_add add_incr cont_on_ err ******

MS650_Byte

MS650_Data

FPA

SSC_Prog_timers

SSC_TOY_Clock

Virtual_Mode

Interval_Timer start_add end_add add_incr cont_on_ err ****** start_add end_add add_incr cont_on_ err ******

******* which_timer wait_time_us *** repeat_test_250ms_ea Tolerance ***

*********

*

1

These addresses may change with different versions of the software.

4–4

KA660 CPU System Maintenance

Table 4–1 (Cont.): Test and Utility Numbers

86

87

90

91

99

9A

9B

9C

9D

9E

9F

C1

C2

C5

C6

C7

82

83

84

85

63

80

81

5C

5F

60

62

Test

58

59

5A

Address

1

20061370

200604C4

2005A120

20060A2C

2005F878

20059D51

20055950

20055ACC

20059731

200555B4

20055779

200569CA

20058070

20055C28

200560E4

200592B0

2005500E

20054FA4

200629F5

200618FC

200625D8

2005BB4A

2005C826

20055586

20062B32

200546D0

200548A6

20059581

20054614

2005967C

Name Parameters

SHAC_RESET dssi_bus port_number time_secs

SGEC_LPBCK_ASSIST time_secs **

SOC_CMCTL

SHAC dont_report_memory_bad repeat_count

* shac_number *******

SGEC

SSC_Console_SLU console_QDSS loopback_type no_ram_tests ****** start_BAUD end_BAUD ****** mark_not_present selftest_r0 selftest_ r1 *****

QDSS_any input_csr selftest_r0 selftest_r1 ******

CQBIC_memory_LMGH **********

Qbus_MSCP IP_csr ******

Qbus_DELQA

QZA_LPBCK1

QZA_LPBCK2

QZA_memory device_num_addr **** controller_number ******** controller_number ********* incr test_pattern controller_number

*******

Controller_number main_mem_buf ******** QZA_DMA

QZA_EXTLPBCK

CQBIC_registers

CQBIC_powerup controller_number ****

*

**

Flush_Ena_Caches

INTERACTION

Init_memory_4MB

List_CPU_registers

Utility dis_flush_cache ********* pass_count disable_device ****

*

*

Expnd_err_msg get_mode init_LEDs clr_ps_cnt

* List_diagnostics

Create_A0_Script

SSC_RAM_Data

SSC_RAM_Data_Addr

SSC_registers

SSC_powerup

SSC_CBTCR_timeout

**********

*

*

*

*********

***

1

These addresses may change with different versions of the software.

Troubleshooting and Diagnostics

4–5

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

54 20054BB9 Virtual mode ******

30 2005D07C MEM_bitmap *** mark_Hard_SBEs ******

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

>>> T 54

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

>>> T 30 0 0 0 1

You must enter a value of either 0 (zero) or 1 (one) for the first three parameters. (0 is used in this example.) The values have no effect on the test; they are simply place holders for the first three parameters. You do not have to specify a value for parameters that follow the user-defined parameter.

4.3.2 Scripts

Most of the tests shown by utility 9E are arranged into scripts. A

script

is a data structure that points to various tests and defines the order in which they are run. Different scripts can run the same set of tests, but in a different order and/or with different parameters and flags. A script also contains the following information:

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

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

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

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

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

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

Additional scripts are included in the ROMs for use in manufacturing and engineering environments. Customer Services personnel can run these scripts and tests individually, using the T command. When doing so, note that certain tests may be dependent upon a state set up from a previous test.

For this reason you should use the UNJAM and INITIALIZE commands,

4–6

KA660 CPU System Maintenance

described in Chapter 3, before running an individual test. You do not need to use these commands on system power-up, however, because system power-up leaves the machine in a defined state.

Customer Services personnel with a detailed knowledge of the KA660 hardware and firmware can also create their own scripts, by using the

9F utility. (See Section 4.3.3.) Table 4–2 lists the scripts.

A0

A1

A3

A4

A5

A6

A7

Table 4–2: Scripts Available to Customer Services

Script

Enter with

Command

A8

A9

B5

Soft script created by T 9F

Functional verify, usually continue-on-error, with countdown announcements

Functional verify, stop on error, test no. announcements

Loop on A3 functional verify

Address shorts test, run fastest way possible

Memory tests, mark only multi-bit errors

Memory tests; can be run by itself; will continue on error; useful when you want to bypass the bitmap test

Memory acceptance tests; marks single and multi-bit ECC errors in the bitmap; calls A7

Memory tests; halts on the first hard or soft error

SOC cache debug script

4.3.3 User Created Scripts

You can create your own script using utility 9F, to control the order in which tests are run and to select specific parameters and flags for individual tests.

In this way you do not have to use the defaults provided by the hardwired scripts.

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

Run test 9F first to build the user script. (See Example 4–1.) Press Return to use the default parameters or flags, which are shown in parentheses. 9F prompts you for the following information:

• Script location. The script can be located in the 1-Kbyte NVRAM in the SSC or in main memory. A script is limited by the size of the data structure that contains it. A larger script can be developed in main memory.

• Test number

Troubleshooting and Diagnostics

4–7

• Run environment. This defines where the actual diagnostic test can be run from. The choices are 0 = ROM, 2 = main memory, and 3 = fastest possible. Choose number 3 to select the fastest possible data structure to run from that will not overwrite the test.

• Repeat code

• Error severity level

• Console error report

• Script error treatment

• LED display

• Console display

• Parameters

Example 4–1 shows how to build and run a user script.

The utility displays the test name after you enter the test number, and the number of bytes remaining after you enter the information for each test.

When you have finished entering tests, press Return at the next

Next test number: prompt to end the script building session. Then enter T A0 and press Return to run the new script.

You can review or edit a script you have created.

4–8

KA660 CPU System Maintenance

Example 4–1: Creating a Script with Utility 9F

>>>T 9F

SP=201406A8

Script in ?[0=SSC, 2=RAM] :0

Script starts at 20140794

36 bytes left

Test number (? for list) or script number :80

CQBIC_memory_LMGH>> Run from ?[0=ROM,2=RAM,3=fastest possible] (0):0

CQBIC_memory_LMGH>> Error severity ? [0,1,2,3] (02):0

CQBIC_memory_LMGH>> Console error report? [0=none,1=full] (01):0

CQBIC_memory_LMGH>> Stop script on error? [0=NO,1=YES] (01):0

CQBIC_memory_LMGH>> Repeat? [0=no,1=forever,>1=count<FF] (00):0

CQBIC_memory_LMGH>> LED on entry (01):0

CQBIC_memory_LMGH>> Console Announcement on entry (80):1

32 bytes left

Test number (? for list) or script number :1

No such diagnostic!

32 bytes left

Test number (? for list) or script number :

>>>

>>>! Execute test script.

>>>T A0

01..

>>>

Example 4–2 shows the script building procedure to follow if (a) you are unsure of the test number to specify, and (b) you want to run one test repeatedly. If you are not sure of the test number, enter ? at the

Next test number: prompt to invoke test 9E and display test numbers, test names, and so on. To run one test repeatedly enter the following sequence:

1. Enter the test number (40 in Example 4–2) at the

Next test number: prompt.

2. Enter A0 at the next

Next test number: prompt.

3. Press Return at the next

Next test number: prompt.

4. Enter T A0 to begin running the script repeatedly.

5. Press

CTRL/C to stop the test.

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

Troubleshooting and Diagnostics

4–9

Example 4–2: Listing and Repeating Tests with Utility 9F

>>>T 9F

SP=201406A8

Script in ?[0=SSC, 2=RAM] :0

Script starts at 20140794

36 bytes left

Test number (? for list) or script number :80

CQBIC_memory_LMGH>> Run from ?[0=ROM, 2=RAM, 3=fastest possible] (0):2

CQBIC_memory_LMGH>> Error severity ? [0,1,2,3] (02):2

CQBIC_memory_LMGH>> Console error report? [0=none,1=full] (01):0

CQBIC_memory_LMGH>> Stop script on error? [0=NO,1=YES] (01):0

CQBIC_memory_LMGH>> Repeat? [0=no,1=forever,>1=count<FF] (00):0

CQBIC_memory_LMGH>> LED on entry (01):0

CQBIC_memory_LMGH>> Console Announcement on entry (80):1

32 bytes left

Test number (? for list) or script number :1

No such diagnostic!

32 bytes left

Test number (? for list) or script number :

>>>

>>>! Execute test script.

>>>

Example 4–3: Console Display (No Errors)

KA660-A Vn.n VMB 2.12

Performing normal system tests.

95..94..93..92..91..90..89..88..87..86..85..84..83..82..81..80..

79..78..77..76..75..74..73..72..71..70..69..68..67..66..65..64..

63..62..61..60..59..58..57..56..55..54..53..52..51..50..49..48..

47..46..45..44..43..42..41..40..39..38..37..36..35..34..33..32..

31..30..29..28..27..26..25..24..23..22..21..20..19..18..17..16..

15..14..13..12..11..10..09..08..07..06..05..04..03..

Tests completed.

>>>

4.3.4 Console Displays

Example 4–3 shows a typical console display during execution of the ROMbased diagnostics. The numbers on the console display do not refer to actual test numbers. Refer to Table 4–5 to see the correspondence between the numbers displayed (listed in the Console Display column) and the actual tests being run (listed in the Test column).

4–10

KA660 CPU System Maintenance

The first line contains the firmware revision and the virtual memory bootstrap (VMB) revision.

Diagnostic test failures, if specified in the firmware script, produce an error display in the format shown in Example 4–4.

Example 4–4: Sample Output with Errors

?45 2 10 FF 0000 0002 00; SUBTEST_45_10, DE_SOC_Cache_mem_CQBIC.LIS

P1=00000010 P2=00000000 P3=04000000 P4=04000000 P5=00000015

P6=20089000 P7=00000001 P8=80000400 P9=00000010 P10=00000000 r0=00000000 r1=00000000 r2=43214321 r3=30080000 r4=00000400 r5=20089000 r6=43214321 r7=43214321 r8=00000000 EPC=00000000

Tests completed

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

Test Severity Subtestlog Error_type Vector Count Loop_subtestlog

• Test identifies the diagnostic test.

• Severity is the severity level of a test failure, as dictated by the script.

Failure of a severity level 2 (SV2) test causes the display of this fiveline error printout, and halts an autoboot. An error of severity level

1 causes a display of the first line of the error printout, but does not interrupt an autoboot. Most tests have a severity level of 2.

• Subtestlog is two hexadecimal digits identifying, usually within 10 instructions, where in the diagnostic the error occurred.

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

FF—Normal error exit from diagnostic

FE—Unanticipated interrupt

FD—Interrupt in cleanup routine

FC—Interrupt in interrupt handler

FB—Script requirements not met

FA—No such diagnostic

EF—Unanticipated exception in executive

Troubleshooting and Diagnostics

4–11

• Vector identifies the SCB vector (0000 in the example above) through which the unexpected exception or interrupt trapped, when the error_ type field detects an unexpected exception or interrupt (FE, FD, FC, or

EF).

• Count is four hexadecimal digits. It shows the number of previous errors that have occurred (two in Example 4–4).

• Loop_subtestlog is used for calling out routines that identify specific errors.

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

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

Table 4–3: Values Saved, Machine Check Exception During EF

Parameter Value

P1

P2

P3

P4

P5

P6

P7

P8

P9

P10

Contents of SP, points to vector value in P2

Vector = 04, vector of exception 04–3FC

Address of PC pointing to failed instruction, P9

Byte count = 10

Machine check code

Most recent virtual address

Internal state information 1

Internal state information 2

PC, points to failing instruction

PSL

4–12

KA660 CPU System Maintenance

Table 4–4: Values Saved, Exception During Executive

Parameter Value

P1

P2

P3

P4

P5

P6

P7

P8

P9

P10

Contents of SP, points to vector value in P2

Vector = nn, vector of exception 04–3FC

Address of PC pointing to failed instruction, P4

PC, points to instruction following failed instruction

PSL

Contents of stack

Contents of stack

Contents of stack

Contents of stack

Contents of stack

Lines 4 and 5 of the error printout are general registers R0 through R8 and the exception PC (if it occurred).

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

The Default Action on Error column refers to the action taken by the diagnostic executive under the following circumstances:

• The diagnostic executive detects an unexpected exception or interrupt.

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

The Default on Error column does not refer to the action taken by the memory tests. The diagnostic executive either halts the script or continues execution at the next test in the script.

Troubleshooting and Diagnostics

4–13

Most memory tests have a continue-on-error parameter (labeled cont_on_ error, as shown in test 47 in Example 4–2). If you explicitly set cont_on_ error using parameter 4 in a memory test, the test marks bad pages in the bitmap and continues without notifying the diagnostic executive of the error. In this case, a halt on error does not occur even if you specify halt on error in the diagnostic executive (by answering Yes to

Stop script on error?

in Utility 9F), since the memory test does not notify the diagnostic executive that an error has occurred.

Figure 4–1 shows the LEDs on the KA660 CPU. They correspond to the hexadecimal display on the CPU cover panel.

Figure 4–1: KA660 CPU Module LEDs

Green

DC OK LED

Value On

Value Off

8

0

Red LEDs

4

0

2

0

1

0

MLO-005869

4–14

KA660 CPU System Maintenance

81

80

79

78

76

75

74

73

72

71

70

69

68

67

91

90

89

88

87

95

94

93

92

85

84

83

82

Table 4–5: KA660 Console Displays and FRU Pointers

No.

Test LED Description FRUs Conditions script_A1:

53

C1

34

C5

C7

46

46

46

46

46

46

46

46

44

31

30

54

49

60

9D

42

33

32

90

C6

52

52

C

C

C

C

C

B

B

B

B

B

B

B

B

B

B

8

6

8

8

8

8

C

B

C

C

7

C

Utility check_for_intrs

CMCTL_chk_init

CMCTL_registers

CSR_setup map_setup virtual memory_test_fdm serial_line registers

CSSC_chk_init

PROG_TIME

PROG_TIME

TOY

SSC_RAM

ROM_logic

SSC_registers

CBTCR_timeout

SOC_cache_diag_mode

SOC_cache_diag_mode

SOC_cache_diag_mode

SOC_cache_diag_mode

SOC_cache_diag_mode

SOC_cache_diag_mode

SOC_cache_diag_mode

SOC_cache_diag_mode 1

SOC_D_Cache_w_memory 1

1

1

1

1

1

1

1

1

1

1

7, 1

1

1

1

1

1, 4

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-ROM

1, 2

1, 2

RPE-CON-SV2-VOF-RHP-ROM

RPE-STP-SV2-VOF-RHP-ROM

1 RPE-CON-SV2-VOF-RHP-ROM

2, 1, 3 RPE-CON-SV2-VOF-RHP-ROM

1, 6 RPE-CON-SV2-VOF-RHP-ROM

1

1

1, 4, 3 RPE-CON-SV2-VOF-RHP-ROM

1 RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

Field-replaceable Units

:

FRU 1: KA660; FRU 2: MS650; FRU 3: Backplane; FRU 4: Q22-Bus Device; FRU 5:

System Power Supply; FRU 6: CPU Cover Panel; FRU 7: Battery

Conditions

:

NER-0, RPE-1 : Report error

CON-0, STP-1 : Action on error

SV1-1, SV2-2 : Severity level

VOF-0, VON-1 : Virtual mode

RHP-0, RHU-1 : Halt protection

ROM-0, RAM-2, FAST-3 : Run environment

Troubleshooting and Diagnostics

4–15

Table 4–5 (Cont.): KA660 Console Displays and FRU Pointers

No.

Test LED Description FRUs Conditions

8

8

8

8

8

8

B

B

B

B

8

8

8

8

8

8

8

8

8

8

8

8

8

8

8

8

8

8

script_A1:

47

46

45

44

43

42

40

39

38

37

53

52

51

50

48

62

61

60

59

58

66

65

64

63

57

56

55

54

48

48

48

48

47

40

44

44

44

44

48

48

48

48

48

4B

4A

3F

48

48

4F

4E

4D

4C

48

48

48

48 memory_data memory_byte memory_addr memory_ECC_error mask_write_w_errs

ECC_correction mem_FDM_addr_shorts addr_shrts addr_shrts addr_shrts addr_shrts addr_shrts addr_shrts

2, 1, 3 RPE-CON-SV2-VOF-RHP-ROM

2, 1, 3 RPE-CON-SV2-VOF-RHP-FAST

2, 1, 3 RPE-CON-SV2-VOF-RHP-FAST

2, 1, 3 RPE-CON-SV2-VOF-RHP-FAST

2, 1, 3 RPE-CON-SV2-VOF-RHP-FAST

2, 1 RPE-CON-SV2-VOF-RHP-FAST

2, 1, 3 RPE-CON-SV2-VOF-RHP-FAST

2, 1, 3 RPE-CON-SV2-VOF-RHP-FAST

2, 1, 3 RPE-CON-SV2-VOF-RHP-FAST

2, 1, 3 RPE-CON-SV2-VOF-RHP-FAST

2, 1, 3 RPE-CON-SV2-VOF-RHP-FAST

2, 1, 3 RPE-CON-SV2-VOF-RHP-FAST

2, 1, 3 RPE-CON-SV2-VOF-RHP-FAST addr_shrts addr_shrts addr_shrts addr_shrts addr_shrts

2, 1, 3 RPE-CON-SV2-VOF-RHP-FAST

2, 1, 3 RPE-CON-SV2-VOF-RHP-FAST

2, 1, 3 RPE-CON-SV2-VOF-RHP-FAST

2, 1, 3 RPE-CON-SV2-VOF-RHP-FAST

2, 1, 3 RPE-CON-SV2-VOF-RHP-FAST addr_shrts addr_shrts addr_shrts addr_shrts

2, 1, 3

2, 1, 3

2, 1, 3

2, 1, 3 memory_refresh count_bad_pages

2, 1

2

SOC_D_Cache_w_memory 1, 2

RPE-CON-SV2-VOF-RHP-FAST

RPE-CON-SV2-VOF-RHP-FAST

RPE-CON-SV2-VOF-RHP-FAST

RPE-CON-SV2-VOF-RHP-FAST

RPE-CON-SV2-VOF-RHP-FAST

RPE-CON-SV1-VOF-RHP-ROM

NER-CON-SV1-VOF-RHU-ROM

SOC_D_Cache_w_memory 1, 2

SOC_D_Cache_w_memory 1, 2

SOC_D_Cache_w_memory 1, 2

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

Field-replaceable Units

:

FRU 1: KA660; FRU 2: MS650; FRU 3: Backplane; FRU 4: Q22-Bus Device; FRU 5:

System Power Supply; FRU 6: CPU Cover Panel; FRU 7: Battery

Conditions

:

NER-0, RPE-1 : Report error

CON-0, STP-1 : Action on error

SV1-1, SV2-2 : Severity level

VOF-0, VON-1 : Virtual mode

RHP-0, RHU-1 : Halt protection

ROM-0, RAM-2, FAST-3 : Run environment

4–16

KA660 CPU System Maintenance

Table 4–5 (Cont.): KA660 Console Displays and FRU Pointers

No.

Test LED Description FRUs Conditions

8

A

B

B

4

5

8

7

7

7

B

B

B

B

B

7

7

7

7

7

B

C

B

B

B

B

7

7

script_A1:

15

14

13

12

11

10

09

08

07

06

20

19

18

17

16

32

31

30

29

27

36

35

34

33

26

24

23

21

83

84

85

43

43

5A

51

5F

5C

9A

43

43

43

43

43

80

45

45

45

45

44

44

44

C2

45

45

43

43

SOC_D_Cache_w_memory 1, 2

SOC_D_Cache_w_memory 1, 2

SOC_D_Cache_w_memory 1, 2

SSC_RAM_addr_shrts 1

CQBIC_memory cache_mem_cqbic cache_mem_cqbic cache_mem_cqbic cache_mem_cqbic cache_mem_cqbic cache_mem_cqbic

1, 2

1, 2

SOC_DI_Cache_w_memory 1, 2

SOC_DI_Cache_w_memory 1, 2

1, 2

1, 2

1, 2

1, 2

1, 2

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-FAST

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-FAST

NER-CON-SV1-VOF-RHU-FAST

SOC_DI_Cache_w_memory 1, 2

SOC_DI_Cache_w_memory 1, 2

SOC_DI_Cache_w_memory 1, 2

SOC_DI_Cache_w_memory 1, 2

SOC_DI_Cache_w_memory 1, 2

NER-CON-SV1-VOF-RHU-FAST

NER-CON-SV1-VOF-RHU-FAST

NER-CON-SV1-VOF-RHU-FAST

NER-CON-SV1-VOF-RHU-FAST

NER-CON-SV1-VOF-RHU-FAST

SOC_DI_Cache_w_memory 1, 2

SOC_DI_Cache_w_memory 1, 2

SOC_CMCTL

FPA

1, 2

1

SGEC_func

SHAC_func

Interaction_func

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-FAST

RPE-CON-SV2-VOF-RHP-RAM

RPE-CON-SV2-VOF-RHP-FAST

1, 6

1, 3

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-ROM

1, 2, 3 RPE-CON-SV2-VOF-RHP-FAST qza_lpbck1 qza_lpbck2 qza_memory

4

4

4

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-ROM

Field-replaceable Units

:

FRU 1: KA660; FRU 2: MS650; FRU 3: Backplane; FRU 4: Q22-Bus Device; FRU 5:

System Power Supply; FRU 6: CPU Cover Panel; FRU 7: Battery

Conditions

:

NER-0, RPE-1 : Report error

CON-0, STP-1 : Action on error

SV1-1, SV2-2 : Severity level

VOF-0, VON-1 : Virtual mode

RHP-0, RHU-1 : Halt protection

ROM-0, RAM-2, FAST-3 : Run environment

Troubleshooting and Diagnostics

4–17

Table 4–5 (Cont.): KA660 Console Displays and FRU Pointers

No.

Test LED Description FRUs Conditions script_A1:

05

04

03

86

99

41

7

B

C qza_dma flush_ena_caches board_reset

4

4

1, 4

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-ROM

script_A2:

52

52

53

C1

34

91

C5

9D

42

C6

60

46

46

46

46

46

99

55

46

46

46

52

52

53

C1

34

91

C5

9D

42

C6

60

46

46

46

46

46

99

55

46

46

46

C

C

C

C

C

7

C

C

B

C

6

B

B

B

B

B

B

B

B

B

B

Utility check_for_intrs

CSSC_chk_init

Serial_line

PROG_TIME

PROG_TIME

TOY

SSC_RAM

ROM_logic

CQBIC_chk_init

SSC_registers interval_timer

SOC_cache_diag_mode

SOC_cache_diag_mode

SOC_cache_diag_mode

SOC_cache_diag_mode

SOC_cache_diag_mode

SOC_cache_diag_mode

SOC_cache_diag_mode

SOC_cache_diag_mode flush_ena_caches

1

1

1

1

1

1

1

1

1

1

1, 2

1, 4

1

1, 6

RPE-STP-SV2-VOF-RHP-ROM

RPE-STP-SV2-VOF-RHP-ROM

RPE-STP-SV2-VOF-RHP-ROM

RPE-STP-SV2-VOF-RHP-ROM

1

1

7, 1

1

RPE-STP-SV2-VOF-RHP-ROM

RPE-STP-SV2-VOF-RHP-ROM

RPE-STP-SV2-VOF-RHP-ROM

RPE-STP-SV2-VOF-RHP-ROM

1 RPE-STP-SV2-VOF-RHP-ROM

1, 4, 3 RPE-STP-SV2-VOF-RHP-ROM

1 RPE-STP-SV2-VOF-RHP-ROM

RPE-STP-SV2-VOF-RHP-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

RPE-STP-SV2-VOF-RHP-ROM

Field-replaceable Units

:

FRU 1: KA660; FRU 2: MS650; FRU 3: Backplane; FRU 4: Q22-Bus Device; FRU 5:

System Power Supply; FRU 6: CPU Cover Panel; FRU 7: Battery

Conditions

:

NER-0, RPE-1 : Report error

CON-0, STP-1 : Action on error

SV1-1, SV2-2 : Severity level

VOF-0, VON-1 : Virtual mode

RHP-0, RHU-1 : Halt protection

ROM-0, RAM-2, FAST-3 : Run environment

4–18

KA660 CPU System Maintenance

Table 4–5 (Cont.): KA660 Console Displays and FRU Pointers

No.

Test LED Description FRUs Conditions script_A2:

90

32

C7

5C

90

32

C7

5C

C

5

7

8 registers

CMCTL_registers

CBTCR_timeout

SHAC_func

1, 4, 3 RPE-STP-SV2-VOF-RHP-ROM

1, 2 RPE-STP-SV2-VOF-RHP-ROM

1

1, 3

RPE-STP-SV2-VOF-RHP-ROM

RPE-STP-SV2-VOF-RHP-ROM

script_A3:

C1

C5

55

C7

46

46

C6

52

52

53

31

30

54

49

60

91

90

9D

42

33

C1

C5

55

C7

46

46

C6

52

52

53

31

30

54

49

60

91

90

9D

42

33

B

C

B

C

C

B

C

C

C

C

B

8

8

8

C

B

8

6

7

7

Utility check_for_intrs

CMCTL_chk_init

CSR_setup map_setup virtual memory_test_fdm

Serial_line

CQBIC_chk_init registers

CSSC_chk_init

PROG_TIME

PROG_TIME

TOY

SSC_RAM

SSC_registers interval_timer

CBTCR_timeout

SOC_cache_diag_mode

SOC_cache_diag_mode

1

1

1

1

1

1

1

1

1

7, 1

1

1, 4

1

RPE-STP-SV2-VOF-RHP-ROM

RPE-STP-SV2-VOF-RHP-ROM

RPE-STP-SV2-VOF-RHP-ROM

1, 2

2, 1

RPE-STP-SV2-VOF-RHP-ROM

RPE-STP-SV2-VOF-RHP-ROM

1 RPE-STP-SV2-VOF-RHP-ROM

2, 1, 3 RPE-STP-SV2-VOF-RHP-ROM

1, 6 RPE-STP-SV2-VOF-RHP-ROM

1, 4, 3 RPE-STP-SV2-VOF-RHP-ROM

1, 4, 3 RPE-STP-SV2-VOF-RHP-ROM

RPE-STP-SV2-VOF-RHP-ROM

RPE-STP-SV2-VOF-RHP-ROM

RPE-STP-SV2-VOF-RHP-ROM

RPE-STP-SV2-VOF-RHP-ROM

RPE-STP-SV2-VOF-RHP-ROM

RPE-STP-SV2-VOF-RHP-ROM

RPE-STP-SV2-VOF-RHP-ROM

RPE-STP-SV2-VOF-RHP-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

Field-replaceable Units

:

FRU 1: KA660; FRU 2: MS650; FRU 3: Backplane; FRU 4: Q22-Bus Device; FRU 5:

System Power Supply; FRU 6: CPU Cover Panel; FRU 7: Battery

Conditions

:

NER-0, RPE-1 : Report error

CON-0, STP-1 : Action on error

SV1-1, SV2-2 : Severity level

VOF-0, VON-1 : Virtual mode

RHP-0, RHU-1 : Halt protection

ROM-0, RAM-2, FAST-3 : Run environment

Troubleshooting and Diagnostics

4–19

Table 4–5 (Cont.): KA660 Console Displays and FRU Pointers

No.

Test LED Description FRUs Conditions

8

8

8

8

8

8

8

8

8

8

8

8

8

B

8

B

B

B

B

B

B

B

B

B

B

B

B

B

script_A3:

48

48

48

48

48

48

4B

4A

3F

48

44

4F

4E

4D

4C

46

46

44

44

44

46

46

46

46

44

44

44

44

48

48

48

48

48

48

4B

4A

3F

48

44

4F

4E

4D

4C

46

46

44

44

44

46

46

46

46

44

44

44

44

SOC_cache_diag_mode

SOC_cache_diag_mode

SOC_cache_diag_mode

SOC_cache_diag_mode

1

1

1

1

SOC_cache_diag_mode

SOC_cache_diag_mode

1

1

SOC_D_Cache_w_memory 1, 2

SOC_D_Cache_w_memory 1, 2

SOC_D_Cache_w_memory 1, 2

SOC_D_Cache_w_memory 1, 2

SOC_D_Cache_w_memory 1, 2

SOC_D_Cache_w_memory 1, 2

SOC_D_Cache_w_memory 1, 2

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

SOC_D_Cache_w_memory 1, 2 memory_data 2, 1, 3

NER-CON-SV1-VOF-RHU-ROM

RPE-STP-SV2-VOF-RHP-ROM memory_byte memory_addr memory_ECC_error

2, 1, 3

2, 1, 3

2, 1, 3

RPE-STP-SV2-VOF-RHP-FAST

RPE-STP-SV2-VOF-RHP-FAST

RPE-STP-SV2-VOF-RHP-FAST mask_write_w_errs

ECC_correction mem_FDM_addr_shorts addr_shrts addr_shrts addr_shrts addr_shrts addr_shrts addr_shrts addr_shrts

2, 1, 3

2, 1

2, 1, 3

2, 1, 3

2, 1, 3

RPE-STP-SV2-VOF-RHP-FAST

RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

RPE-STP-SV2-VOF-RHP-FAST

RPE-STP-SV2-VOF-RHP-FAST

RPE-STP-SV2-VOF-RHP-FAST

Field-replaceable Units

:

FRU 1: KA660; FRU 2: MS650; FRU 3: Backplane; FRU 4: Q22-Bus Device; FRU 5:

System Power Supply; FRU 6: CPU Cover Panel; FRU 7: Battery

Conditions

:

NER-0, RPE-1 : Report error

CON-0, STP-1 : Action on error

SV1-1, SV2-2 : Severity level

VOF-0, VON-1 : Virtual mode

RHP-0, RHU-1 : Halt protection

ROM-0, RAM-2, FAST-3 : Run environment

4–20

KA660 CPU System Maintenance

Table 4–5 (Cont.): KA660 Console Displays and FRU Pointers

No.

Test LED Description FRUs Conditions

7

7

7

7

7

7

7

7

7

B

B

B

B

B

B

8

8

8

8

8

8

8

8

8

B

B

8

B

script_A3:

80

45

45

45

45

45

45

45

45

43

44

44

44

44

44

48

48

48

48

47

48

48

48

48

40

44

44

44

80

45

45

45

45

45

45

45

45

43

44

44

44

44

44

48

48

48

48

47

48

48

48

48

40

44

44

44 addr_shrts addr_shrts addr_shrts addr_shrts addr_shrts addr_shrts addr_shrts addr_shrts memory_refresh

2, 1, 3

2, 1, 3

2, 1, 3

2, 1, 3

2, 1, 3

2, 1, 3 count_bad_pages 2

SOC_D_Cache_w_memory 1, 2

SOC_D_Cache_w_memory 1, 2

SOC_D_Cache_w_memory 1, 2

RPE-STP-SV2-VOF-RHP-FAST

RPE-STP-SV2-VOF-RHP-FAST

RPE-STP-SV2-VOF-RHP-FAST

RPE-STP-SV2-VOF-RHP-FAST

RPE-STP-SV2-VOF-RHP-FAST

RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1 RPE-STP-SV2-VOF-RHP-FAST

RPE-STP-SV2-VOF-RHP-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

SOC_D_Cache_w_memory 1, 2

SOC_D_Cache_w_memory 1, 2

SOC_D_Cache_w_memory 1, 2

SOC_D_Cache_w_memory 1, 2

SOC_D_Cache_w_memory 1, 2

CQBIC_memory cache_mem_cqbic cache_mem_cqbic cache_mem_cqbic cache_mem_cqbic cache_mem_cqbic cache_mem_cqbic cache_mem_cqbic cache_mem_cqbic

1, 2

1, 2

SOC_DI_Cache_w_memory 1, 2

1, 2

1, 2

1, 2

1, 2

1, 2

1, 2

1, 2

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

RPE-STP-SV2-VOF-RHP-FAST

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-FAST

Field-replaceable Units

:

FRU 1: KA660; FRU 2: MS650; FRU 3: Backplane; FRU 4: Q22-Bus Device; FRU 5:

System Power Supply; FRU 6: CPU Cover Panel; FRU 7: Battery

Conditions

:

NER-0, RPE-1 : Report error

CON-0, STP-1 : Action on error

SV1-1, SV2-2 : Severity level

VOF-0, VON-1 : Virtual mode

RHP-0, RHU-1 : Halt protection

ROM-0, RAM-2, FAST-3 : Run environment

Troubleshooting and Diagnostics

4–21

Table 4–5 (Cont.): KA660 Console Displays and FRU Pointers

No.

Test LED Description FRUs Conditions script_A3:

43

43

43

43

43

43

43

43

43

9A

99

41

9D

5A

51

5F

5C

43

43

43

43

43

43

43

43

43

9A

99

41

9D

5A

51

5F

5C

B

B

B

B

B

B

B

B

B

C

C

8

B

4

5

8

A

SOC_DI_Cache_w_memory 1, 2

SOC_DI_Cache_w_memory 1, 2

SOC_DI_Cache_w_memory 1, 2

SOC_DI_Cache_w_memory 1, 2

SOC_DI_Cache_w_memory 1, 2

SOC_DI_Cache_w_memory 1, 2

SOC_DI_Cache_w_memory 1, 2

SOC_DI_Cache_w_memory 1, 2

SOC_DI_Cache_w_memory 1, 2

SOC_CMCTL

FPA

SGEC_func

SHAC_func

Interaction_func flush_ena_caches board_reset

Utility

NER-CON-SV1-VOF-RHU-FAST

NER-CON-SV1-VOF-RHU-FAST

NER-CON-SV1-VOF-RHU-FAST

NER-CON-SV1-VOF-RHU-FAST

NER-CON-SV1-VOF-RHU-FAST

NER-CON-SV1-VOF-RHU-FAST

NER-CON-SV1-VOF-RHU-FAST

NER-CON-SV1-VOF-RHU-ROM

NER-CON-SV1-VOF-RHU-FAST

1, 2

1

1, 6

1, 3

RPE-STP-SV2-VOF-RHU-RAM

RPE-STP-SV2-VOF-RHP-FAST

RPE-STP-SV2-VOF-RHP-ROM

RPE-STP-SV2-VOF-RHP-ROM

1, 2

1, 2

RPE-STP-SV2-VOF-RHP-FAST

RPE-STP-SV2-VOF-RHP-ROM

2, 1, 3 RPE-STP-SV2-VOF-RHP-ROM

1 RPE-STP-SV2-VOF-RHP-ROM

script_A5:

48

48

48

48

3F

48

48

48

48

48

48

3F

48

48

8

8

8

8

8

8

8 mem_FDM_addr_shorts addr_shrts addr_shrts addr_shrts addr_shrts addr_shrts addr_shrts

2, 1, 3 RPE-CON-SV2-VOF-RHU-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

Field-replaceable Units

:

FRU 1: KA660; FRU 2: MS650; FRU 3: Backplane; FRU 4: Q22-Bus Device; FRU 5:

System Power Supply; FRU 6: CPU Cover Panel; FRU 7: Battery

Conditions

:

NER-0, RPE-1 : Report error

CON-0, STP-1 : Action on error

SV1-1, SV2-2 : Severity level

VOF-0, VON-1 : Virtual mode

RHP-0, RHU-1 : Halt protection

ROM-0, RAM-2, FAST-3 : Run environment

4–22

KA660 CPU System Maintenance

Table 4–5 (Cont.): KA660 Console Displays and FRU Pointers

No.

Test LED Description FRUs Conditions script_A5:

48

48

48

48

48

48

48

48

48

48

48

48

48

48

48

48

8

8

8

8

8

8

8

8 addr_shrts addr_shrts addr_shrts addr_shrts addr_shrts addr_shrts addr_shrts addr_shrts

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

script_A6:

30

4F

4D

4C

4B

4A

3F

48

47

40

80

30

4F

4D

4C

4B

4A

3F

48

47

40

80

8

8

8

8

8

8

8

8

8

8

7

script_A7:

4F

4E

4F

4E

8

8 map_setup memory_data memory_addr memory_ECC_error mask_write_w_errs

ECC_correction mem_FDM_addr_shorts addr_shrts memory_refresh count_bad_pages

CQBIC_memory memory_data memory_byte

1, 2 RPE-STP-SV2-VOF-RHP-ROM

2, 1, 3 RPE-STP-SV2-VOF-RHP-ROM

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1

2

1, 2

RPE-STP-SV2-VOF-RHP-FAST

RPE-STP-SV2-VOF-RHP-ROM

RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-ROM

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

Field-replaceable Units

:

FRU 1: KA660; FRU 2: MS650; FRU 3: Backplane; FRU 4: Q22-Bus Device; FRU 5:

System Power Supply; FRU 6: CPU Cover Panel; FRU 7: Battery

Conditions

:

NER-0, RPE-1 : Report error

CON-0, STP-1 : Action on error

SV1-1, SV2-2 : Severity level

VOF-0, VON-1 : Virtual mode

RHP-0, RHU-1 : Halt protection

ROM-0, RAM-2, FAST-3 : Run environment

Troubleshooting and Diagnostics

4–23

Table 4–5 (Cont.): KA660 Console Displays and FRU Pointers

No.

Test LED Description FRUs Conditions

8

8

8

8

8

8

7

8

8

C

8

8

8

8

8

8

8

8

8

8

8

8

8

script_A7:

48

48

48

48

48

48

47

40

80

41

3F

48

48

48

48

4D

4C

4B

4A

48

48

48

48

48

48

48

48

48

48

47

40

80

41

3F

48

48

48

48

4D

4C

4B

4A

48

48

48

48 memory_byte memory_ECC_error mask_write_w_errs

ECC_correction mem_FDM_addr_shorts addr_shrts addr_shrts addr_shrts addr_shrts addr_shrts addr_shrts addr_shrts addr_shrts addr_shrts addr_shrts addr_shrts addr_shrts addr_shrts addr_shrts memory_refresh count_bad_pages

CQBIC_memory board_reset

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1 RPE-STP-SV2-VOF-RHP-FAST

2

1, 2

RPE-CON-SV2-VOF-RHU-ROM

RPE-CON-SV2-VOF-RHU-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-ROM

script_A8:

31 31 8 CSR_setup 1, 2 RPE-STP-SV2-VOF-RHP-ROM

Field-replaceable Units

:

FRU 1: KA660; FRU 2: MS650; FRU 3: Backplane; FRU 4: Q22-Bus Device; FRU 5:

System Power Supply; FRU 6: CPU Cover Panel; FRU 7: Battery

Conditions

:

NER-0, RPE-1 : Report error

CON-0, STP-1 : Action on error

SV1-1, SV2-2 : Severity level

VOF-0, VON-1 : Virtual mode

RHP-0, RHU-1 : Halt protection

ROM-0, RAM-2, FAST-3 : Run environment

4–24

KA660 CPU System Maintenance

Table 4–5 (Cont.): KA660 Console Displays and FRU Pointers

No.

Test LED Description FRUs Conditions script_A8:

30

49

30

49

8

8 map_setup memory_test_fdm

2, 1 RPE-STP-SV2-VOF-RHP-ROM

2, 1, 3 RPE-STP-SV2-VOF-RHP-ROM

script_A9:

47

40

41

4F

4E

4D

4C

4B

47

40

41

4F

4E

4D

4C

4B

8

8

8

8

8

8

8

C memory_data memory_byte memory_addr memory_ecc_error mask_write_w_errs memory_refresh count_bad_pages board_reset

2, 1, 3 RPE-STP-SV2-VOF-RHP-ROM

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-STP-SV2-VOF-RHP-FAST

2, 1, 3 RPE-CON-SV2-VOF-RHU-ROM

2, 1, 3 RPE-CON-SV2-VOF-RHU-ROM

script_B5:

46

46

46

44

44

46

46

46

46

46

46

46

44

44

46

46

46

46

B

B

B

B

B

B

B

B

B

SOC_cache_diag_mode

SOC_cache_diag_mode

SOC_cache_diag_mode

SOC_cache_diag_mode

1

1

1

1

SOC_cache_diag_mode

SOC_cache_diag_mode

SOC_cache_diag_mode

1

1

1

SOC_D_Cache_w_memory 1, 2

SOC_D_Cache_w_memory 1, 2

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-ROM

Field-replaceable Units

:

FRU 1: KA660; FRU 2: MS650; FRU 3: Backplane; FRU 4: Q22-Bus Device; FRU 5:

System Power Supply; FRU 6: CPU Cover Panel; FRU 7: Battery

Conditions

:

NER-0, RPE-1 : Report error

CON-0, STP-1 : Action on error

SV1-1, SV2-2 : Severity level

VOF-0, VON-1 : Virtual mode

RHP-0, RHU-1 : Halt protection

ROM-0, RAM-2, FAST-3 : Run environment

Troubleshooting and Diagnostics

4–25

Table 4–5 (Cont.): KA660 Console Displays and FRU Pointers

No.

Test LED Description FRUs Conditions

B

B

B

B

B

B

B

B

B

B

7

B

7

7

7

B

B

B

B

B

B

7

7

7

7

script_B5:

43

43

43

43

43

43

99

45

43

43

43

43

44

44

45

45

45

44

44

44

44

45

45

45

45

43

43

43

43

43

43

99

45

43

43

43

43

44

44

45

45

45

44

44

44

44

45

45

45

45

SOC_D_Cache_w_memory 1, 2

SOC_D_Cache_w_memory 1, 2

SOC_D_Cache_w_memory 1, 2

SOC_D_Cache_w_memory 1, 2

SOC_D_Cache_w_memory 1, 2

SOC_D_Cache_w_memory 1, 2 cache_mem_cqbic cache_mem_cqbic cache_mem_cqbic

1, 2

1, 2

1, 2 cache_mem_cqbic cache_mem_cqbic cache_mem_cqbic cache_mem_cqbic

1, 2

1, 2

1, 2

1, 2 cache_mem_cqbic 1, 2

SOC_DI_Cache_w_memory 1, 2

SOC_DI_Cache_w_memory 1, 2

SOC_DI_Cache_w_memory 1, 2

SOC_DI_Cache_w_memory 1, 2

SOC_DI_Cache_w_memory 1, 2

SOC_DI_Cache_w_memory 1, 2

SOC_DI_Cache_w_memory 1, 2

SOC_DI_Cache_w_memory 1, 2

SOC_DI_Cache_w_memory 1, 2

SOC_DI_Cache_w_memory 1, 2 flush_ena_caches 1, 2

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-FAST

RPE-CON-SV2-VOF-RHP-FAST

RPE-CON-SV2-VOF-RHP-FAST

RPE-CON-SV2-VOF-RHP-FAST

RPE-CON-SV2-VOF-RHP-FAST

RPE-CON-SV2-VOF-RHP-FAST

RPE-CON-SV2-VOF-RHP-FAST

RPE-CON-SV2-VOF-RHP-FAST

RPE-CON-SV2-VOF-RHP-ROM

RPE-CON-SV2-VOF-RHP-FAST

RPE-CON-SV2-VOF-RHP-ROM

Field-replaceable Units

:

FRU 1: KA660; FRU 2: MS650; FRU 3: Backplane; FRU 4: Q22-Bus Device; FRU 5:

System Power Supply; FRU 6: CPU Cover Panel; FRU 7: Battery

Conditions

:

NER-0, RPE-1 : Report error

CON-0, STP-1 : Action on error

SV1-1, SV2-2 : Severity level

VOF-0, VON-1 : Virtual mode

RHP-0, RHU-1 : Halt protection

ROM-0, RAM-2, FAST-3 : Run environment

4–26

KA660 CPU System Maintenance

4.3.5 System Halt Messages

Table 4–6 lists messages that may appear on the console terminal when a system error occurs.

?19

?1A

?1B

?1D

?1E

?1F

?3F

Table 4–6: System Halt Messages

Code Message Explanation

?02

_03

?04

?05

?06

?07

?08

?0A

?0B

?0C

?10

?11

?12

?13

EXT HLT

——-

ISP ERR

DBL ERR

HLT INST

SCB ERR3

SCB ERR2

CHM FR ISTK

CHM TO ISTK

SCB RD ERR

MCHK AV

KSP AV

DBL ERR2

DBL ERR3

PSL EXC5

1

PSL EXC6

1

PSL EXC7

1

PSL REI5

1

PSL REI6

1

PSL REI7

1

MICROVERIFY

FAILURE

External halt, caused by either console BREAK condition,

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

Power-up, no halt message is displayed.

However, the presence of the firmware banner and diagnostic countdown indicates this halt reason.

In attempting to push state onto the interrupt stack during an interrupt or exception, the processor discovered that the interrupt stack was mapped NO ACCESS or NOT VALID.

The processor attempted to report a machine check to the operating system, and a second machine check occurred.

The processor executed a HALT instruction in kernel mode.

The SCB vector had bits <1:0> equal to 3.

The SCB vector had bits <1:0> equal to 2.

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

The SCB vector for a change mode had bit 0 set.

A hard memory error occurred while the processor was trying to read an exception or interrupt vector.

An access violation or an invalid translation occurred during machine check exception processing.

An access violation or translation not valid occurred during processing of a kernel stack not valid exception.

Double machine check error. A machine check occured while trying to service a machine check.

Double machine check error. A machine check occured while trying to service a kernel stack-not-valid exception.

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

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

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

PSL<26:24> = 5 on an rei instruction

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

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

Microcode power-up self-test failed.

Troubleshooting and Diagnostics

4–27

4.3.6 Console Error Messages

Table 4–7 lists messages issued in response to an error or to a console command that was entered incorrectly.

?73

?74

?75

?76

Table 4–7: Console Error Messages

Code Message Description

?61

?62

?63

?64

?65

?66

?67

?68

?69

?6A

?6B

?6C

?6D

?6E

?6F

?70

?71

?72

CORRUPTION

ILLEGAL REFERENCE

ILLEGAL COMMAND

INVALID DIGIT

LINE TOO LONG

ILLEGAL ADRRESS

The console program database has been corrupted.

Illegal reference. The requested reference would violate virtual memory protection, the address is not mapped, the reference is invalid in the specified address space, or the value is invalid in the specified destination.

The command string cannot be parsed.

A number has an invalid digit.

The command was too large for the console to buffer.

The message is issued only after receipt of the terminating carriage return.

The address specified falls outside the limits of the address space.

VALUE TOO LARGE The value specified does not fit in the destination.

QUALIFIER CONFLICT Qualifier conflict, for example, two different data sizes are specified for an EXAMINE command.

UNKNOWN QUALIFIER The switch is unrecognized.

UNKNOWN SYMBOL The symbolic address in an EXAMINE or DEPOSIT command is unrecognized.

CHECKSUM

HALTED

The command or data checksum of an X command is incorrect. If the data checksum is incorrect, this message is issued, and is not abbreviated to "Illegal command".

The operator entered a HALT command.

FIND ERROR

TIME OUT

MEMORY ERROR

UNIMPLEMENTED

A FIND command failed either to find the RPB or 128 kb of good memory.

During an X command, data failed to arrive in the time expected (60 seconds).

A machine check occurred with a code indicating a read or write memory error.

Unimplemented function.

NO VALUE QUALIFIER Qualifier does not take a value.

AMBIGUOUS QUALIFIER There were not enough unique characters to determine the qualifier.

VALUE QUALIFIER Qualifier requires a value.

TOO MANY QUALIFIERS Too many qualifiers supplied for this command.

TOO MANY ARGUMENTS Too many arguments supplied for this command.

AMBIGUOUS COMMAND There were not enough unique characters to determine the command.

4–28

KA660 CPU System Maintenance

Table 4–7 (Cont.): Console Error Messages

Code Message Description

?77

?78

?79

?7A

?7B

?7C

?7D

TOO FEW ARGUMENTS Insufficient arguments supplied for this command.

TYPEAHEAD OVERFLOW The typeahead buffer overflowed.

FRAMING ERROR A framing error was detected on the console serial line.

OVERRUN ERROR

SOFT ERROR

HARD ERROR

MACHINE CHECK

An overrun error was detected on the console serial line.

A soft error occurred.

A hard error occurred.

A machine check occurred.

4.3.7 VMB Error Messages

Table 4–8 lists the boot error messages and their descriptions.

Table 4–8: VMB Error Messages

Message

Number Mnemonic Interpretation

?52

?53

?54

?55

?49

?4A

?4B

?4C

?4D

?4E

?4F

?50

?51

?40

?41

?42

?43

?44

?45

?46

?47

?48

NOSUCHDEV

DEVASSIGN

NOSUCHFILE

FILESTRUCT

BADCHKSUM

BADFILEHDR

BADIRECTORY

FILNOTCNTG

ENDOFFILE

BADFILENAME

BUFFEROVF

CTRLERR

DEVINACT

DEVOFFLINE

MEMERR

SCBINT

SCB2NDINT

NOROM

NOSUCHNODE

INSFMAPREG

RETRY

IVDEVNAM

No bootable devices found.

Device is not present.

Program image not found.

Invalid boot device file structure.

Bad checksum on header file.

Bad file header.

Bad directory file.

Invalid program image format.

Premature end of file encountered.

Bad file name given.

Program image does not fit in available memory.

Boot device I/O error.

Failed to initialize boot device.

Device is offline.

Memory initialization error.

Unexpected SCB exception or machine check.

Unexpected exception after starting program image.

No valid ROM image found.

No response from load server.

Invalid memory configuration.

No devices bootable, retrying.

Invalid device name.

Troubleshooting and Diagnostics

4–29

Table 4–8 (Cont.): VMB Error Messages

Message

Number Mnemonic

?56

DRVERR

Interpretation

Drive error.

4.4 Acceptance Testing

Perform the acceptance testing procedure listed below, after installing a system or whenever replacing the following:

KA660 module

MS650 module

Memory data interconnect cable

Backplane

DSSI drive

H3602–00

1. Run five error-free passes of the power-up scripts by entering the following command:

>>> R T 0

Press

CTRL/C to terminate the scripts.

2. Perform the next two steps for a granular test of memory.

>>> T A8

>>> R T A7

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

The second command runs script A7 repeatedly. This command runs the memory tests only and does not reset the bitmap. Press

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

If any of the memory tests fail, they mark the bitmap and continue with no error printout to the console. An exception is test 40 (count bad pages). If any single-bit or multi-bit ECC errors are detected, they are reported in test 40. Such a failure indicates that pages in memory have been marked bad in the bitmap because of solid single-bit and/or multi-bit ECC errors.

4–30

KA660 CPU System Maintenance

3. Check the memory configuration again, since test 31 can check for only a few invalid configurations. For example, test 31 cannot report that a memory board is missing from the configuration, since it has no way of knowing if the board should be there or not. In the following four examples, the SHOW MEMORY/FULL command is shown first without errors and then with errors inserted.

>>>SHOW MEMORY/FULL

Memory 0: 00000000 to 00FFFFFF, 16MB, 0 bad pages

Total of 16MB, 0 bad pages, 104 reserved pages

Memory Bitmap

-00FF3000 to 00FF3FFF, 8 pages

Console Scratch Area

-00FF4000 to 00FF7FFF, 32 pages

Qbus Map

-00FF8000 to 00FFFFFF, 64 pages

Scan of Bad Pages

The following command deposits errors into memory.

>>>D FF3100 9/9/0

Running SHOW MEMORY/FULL this time points out the errors.

>>>SHOW MEMORY/FULL

Memory 0: 00000000 to 00FFFFFF, 16MB, 32 bad pages

Total of 16MB, 32 bad pages, 104 reserved pages

Memory Bitmap

-00FF3000 to 00FF3FFF, 8 pages

Console Scratch Area

-00FF4000 to 00FF7FFF, 32 pages

Qbus Map

-00FF8000 to 00FFFFFF, 64 pages

Scan of Bad Pages

-00100000 to 00103FFF, 32 pages

>>>

Memories 0 through 3 are the MS650 memory modules. The Q22-bus map always spans the top 32 Kbytes of good memory. The memory bitmap always spans two pages (1 Kbyte) per 4 Mbytes of memory configured.

Use utility 9C to compare the contents of configuration registers

MEMCSR 0–15 with the memory installed in the system:

Troubleshooting and Diagnostics

4–31

>>>T 9C

SBR=017B8000

P0BR=80000000

TODR=0010E085

TCR0=00000000

TCR1=00000001

RXCS=00000000

SCR=0000D000

SLR=00002021 SAVPC=20044827 SAVPSL=04190304

P0LR=00100A80

ICCS=00000000

TIR0=00000000

P1BR=0A0A0A08

TNIR0=00000000

P1LR=000B0B0B

MAPEN=00000000

TIVR0=00000078

TIR1=0052680A TNIR1=0000000F TIVR1=0000007C

RXDB=0000000D TXCS=00000000

DSER=00000000 QBEAR=0000000F

TXDB=00000030

DEAR=00000000

BDR=08D0EFFF DLEDR=0000000C SSCCR=00D55537 CBTCR=00000004

DSSI_0=00 (BUS_0)

PSR_0=00000000

PQBBR_0=03060022

PESR_0=00000000

PMCSR_0=00000000

PFAR_0=00000000

SCBB=20052400

SID=14000006

BDMTR=20084000

BDMKR=0000007C

QBMBR=017F8000

IPCR0=0000

SSHMA_0=0000CA20

PPR_0=00000000

NICSR0=1FFF0003 3=00004030 4=00004050 5=8039FF00 6=83E0F000 7=00000000

NICSR9=04E204E2 10=00040000 11=00000000 12=00000000 13=00000000 15=0000FFFF

NISA=08-00-2B-12-BC-AC RDES0=00441300

TDES0=00008C80

1=00000000

1=07000000

2=05EE0000

2=00400000

3=000046F0

3=000040FA

MEM_FRU 1

MEM_FRU 2

MEM_FRU 3

MEM_FRU 4

MCSR_0=80000017

MCSR_4=81000016

MCSR_8=00000000

MCSR12=00000000

1=80400017

5=81400016

9=00000000

13=00000000

2=80800017

6=00000016

10=00000000

14=00000000

MEMCSR17=00000013 MEMCSR16=00000044 CSR16_page_address=00000000

MSER=00000000 CCR=00000014

3=80C00017

7=00000016

11=00000000

15=00000000

One memory bank is enabled for each 4 Mbytes of memory. The

MEMCSRs map modules as follows:

MEMCSR 0-3

MEMCSR 4-7

MEMCSR 8-11

MEMCSR 12-15

First MS650 memory module

Second MS650 memory module

Third MS650 memory module

Fourth MS650 memory module

Verify the following:

• If a memory board is not present, bits <31:0> are all zeros for the corresponding group of four MEMCSRs. See the values for

MEMCSR 8–11 in the example.

• Bits <25:22> should increment by one starting at zero in any group of four MEMCSRs whose bit 31 equals 1. In the example above, bits <25:22> of MEMCSR 4 and 5 increment by one, resulting in an increment of four in their longwords. If bit 31 equals 0, <25:22> should equal zero.

4. Check the Q22-bus and the Q22-bus logic in the KA660 CQBIC chip, and the configuration of the Q22-bus, as follows:

4–32

KA660 CPU System Maintenance

>>> SHOW QBUS

Scan of Qbus I/O Space

-20000120 (760440) = 0080 DHQ11/DHV11/CXA16/CXB16/CXY08

-20000122 (760442) = F081

-20000124 (760444) = DD18

-20000126 (760446) = 0200

-20000128 (760450) = 0000

-2000012A (760452) = 0000

-2000012C (760454) = 8000

-2000012E (760456) = 0000

-20001920 (774440) = FF08 DESQA

-20001922 (774442) = FF00

-20001924 (774444) = FF2B

-20001926 (774446) = FF06

-20001928 (774450) = FF16

-2000192A (774452) = FFF2

-2000192C (774454) = 00F8

-2000192E (774456) = 1030

-20001940 (774500) = 0000 TQK50/TQK70/TU81E/RV20/K-TAPE

-20001942 (774502) = 0BC0

-20001F40 (777500) = 0020 IPCR

Scan of Qbus Memory Space

>>>

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

First column = the VAX I/O address of the CSR, in hexadecimal

(20001F40).

Second column = the Q22-bus address of the CSR, in octal (777500).

Third column = the data, contained at the CSR address, in hexadecimal (0020).

Fourth column = the device vector in octal, according to the fixed or floating Q22-bus and UNIBUS algorithm (004).

Fifth column = the device name (IPCR, the KA660 interprocessor communications register).

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

The last line, Scan of Qbus Memory Space, displays memory residing on the Q22-bus, if present. VAX memory mapped by the Q-22 bus map is not displayed.

If the system contains an MSCP or TMSCP controller, run test 81. This test performs step one of the UQ port initialization sequence, performs the SA wraparound test, and checks the Q-22 bus interrupt logic.

Troubleshooting and Diagnostics

4–33

NOTE:

This test will erroneously generate messages indicating the

KFQSA module has failed.

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

>>> T 81 20001940

You can specify other addresses if you have multiple MSCP or TMSCP devices in the first parameter. This action may be useful to isolate a problem with a controller, the KA660, or the backplane. Use the

VAX address provided by the SHOW QBUS command to determine the

CSR value. If you do not specify a value, the MSCP device at address

20001468 is tested by default.

5. Check that all UQSSP, MSCP, TMSCP, and Ethernet controllers and devices are visible by entering the following command:

>>> SHOW DEVICE

DSSI Bus 0 Node 0 (R3YRME)

-DIA0 (RF31)

DSSI Bus 0 Node 1 (R3VBNC)

-DIA1 (RF31)

DSSI Bus 0 Node 7 (*)

UQSSP Tape Controller 0 (774500)

-MUA0 (TK70)

Ethernet Adapter

-EZA0 (08-00-2B-08-E8-6E)

Ethernet Adapter 0 (774440)

-XQA0 (08-00-2B-06-16-F2)

In the above example, the console displays the remote DSSI node names and node numbers of two ISE controllers it recognizes. The lines below each node name and number are the logical unit numbers of any attached devices, DIA0 and DIA1 in this case.

DSSI Node 7 (*) is the KA660 DSSI adapter. In most cases, the KA660 is the local DSSI node shown by the asterisk and has a node number of 7. DSSI node names, node numbers, and unit numbers should be unique.

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

The next two lines show the logical name and station address for the

KA660 Ethernet adapter.

4–34

KA660 CPU System Maintenance

The last two lines refer to DESQA controller, the Q22-bus CSR address, logical name (XQA0), and the station address.

6. Test the DSSI subsystem using the KA660 ROM-based Diagnostics and

Utilities Protocol (DUP) facility. This facility allows you to connect to the DUP server in the RF drive controller. Examples follow.

>>> SET HOST /DUP/DSSI 7

Starting DUP server...

Stopping DUP server...

In this example, a DUP connection was made with DSSI node 7, the

KA660. The DUP server times out, since no local programs exist and no response packet was received.

>>> SET HOST /DUP/DSSI 1

Starting DUP server...

DSSI Bus 0 Node 1 (R3VBNC)

DRVEXR V1.0

D 21-FEB-1988 21:27:54

DRVTST V1.0

D 21-FEB-1988 21:27:54

HISTRY V1.0

D 21-FEB-1988 21:27:54

ERASE V1.0

D 21-FEB-1988 21:27:54

PARAMS V1.0

D 21-FEB-1988 21:27:54

DIRECT V1.0

D 21-FEB-1988 21:27:54

End of directory

Task Name? DRVTST

Write/read anywhere on medium? [1=Yes/(0=No)]: <CR>

5 minutes for test to complete.

Compare failed on head 1 track 1091.

Compare failed on head 0 track 529.

Task Name? DRVEXR

Write/read anywhere on medium? [1=Yes/(0=No)]: <CR>

Test time in minutes? [(10)-100]:

10 minutes for test to complete.

R3VBNC::MSCP$DUP 21-FEB-1988 21:37:35 DRVEXR CPU=00:00:01.88 PI=43

R3VBNC::MSCP$DUP 21-FEB-1988 21:37:38 DRVEXR CPU=00:00:03.38 PI=79

Compare failed on head 1 track 1091.

R3VBNC::MSCP$DUP 21-FEB-1988 21:37:40 DRVEXR CPU=00:00:04.97 PI=116

^C

>>>

In the above example, the local programs DRVTST and DRVEXR are run on drive 1.

CAUTION:

Do not enter 1 in response to the question

Write/read anywhere on medium?

. Doing so will destroy data on the disk.

Troubleshooting and Diagnostics

4–35

Press Return, which uses the default, allowing reads and writes to the DBNs only.

CTRL/T or

CTRL/G displays a message as shown in the

DRVEXR example above (the lines beginning with R3VBNC::). In the example,

CTRL/T has been pressed twice, to show the difference in the time and in the value of the progress indicator (PI).

Press

CTRL/C to terminate the program.

Use the local programs PARAMS (Section 4.8.5) and HISTRY

(Section 4.8.3) to determine the cause of errors displayed during

DRVTST or DRVEXR. DRVTST should run successfully for one pass on each drive.

7. If there are one or more DELQA modules in the system, use test 82 to invoke the Ethernet option’s self-test and receive status from the host firmware. Test 82 is useful for acceptance testing if you cannot access the system enclosure to see the DELQA LEDs.

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

4.5 Troubleshooting

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

4.5.1 FE Utility

The FE utility dumps the diagnostic state to the console as shown below.

>>> T FE

Bitmap=00FF3000, Length=00001000, Checksum=807F, Busmap=00FF8000

Test_number=41, Subtest=00, Loop_Subtest=00, Error_type=00

Error_vector=0000, Last_exception_PC=00000000, Severity=02

Total_error_count=0000, Led_display=0C, Console_display=03, save_mchk_code=80 parameter_1=00000000 2=00000000 3=00000000 4=00000000 5=00000000 parameter_6=00000000 7=00000000 8=00000000 9=00000000 10=00000000 previous_error=00000000, 00000000, 00000000, 00000000

Flags=00FFFC10440E, SET_mask=FF

Return_stack=201406D4, Subtest_pc=20062730, Timeout=00030D40

>>>

The most useful fields displayed above are as follows:

• Error_type_vector. The SCB vector through which the unexpected interrupt or exception trapped if error_type equals FE, FD, FC, or EF.

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

4–36

KA660 CPU System Maintenance

• Previous_error. Contains the history of the last four errors. Each longword contains four bytes of information. From left to right these are the error_type, subtest_log, test number, and loop_subtestlog.

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

• Parameters 1 through 10. Valid on the last text run.

• Last_exception_PC. PC of exception if error_type is FE, FD, FC, or EF.

4.5.2 Isolating Memory Failures

This section describes procedures for isolating memory subsystem failures, particularly when the system contains more than one MS650 memory module.

1. SHOW MEMORY/FULL

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

FULL will break out the number of pages marked bad if any on each individual memory board present.

2. T A9

Script A9 runs only the memory tests and halts on the first hard or soft error found. This script will not continue after an error, and it will not fully mark the bitmap with all errors. The main purpose for

A9 is to find the first test that caused an error and print out the error message. The user can then determine the specific error with a listing for the test. Script A9 is generally not needed to determine a failing field- replaceable unit (FRU).

3. Continue on Error flag.

The fourth parameter allows the user to determine, after a memory error, if a test should continue or stop immediately to allow a printout.

All scripts except A9 have Continue on Error set to allow the memory bitmap to be fully marked correctly for all errors. When running an individual memory test, the default for parameter 4 is to stop on any error. You have to specifically set parameter 4 to a 1 to enable Continue on Error.

When Continue on Error is 0, there is no retry after a soft or a hard error. In other words, if you run any memory test (47, 48, 4A, or 4F) with the default value for parameter 4 (0), or if you run the A9 script,

Troubleshooting and Diagnostics

4–37

any error, hard or soft, will cause the test to stop, print an error, and also mark the bitmap. The bitmap is always marked in 256 KB sections to allow tests to run quicker when errors occur.

The memory tests have a soft error counter for each board. These counters are only incremented if a soft error occurs during a test and

Continue on Error is enabled (1). The soft error counters are also not incremented during the A6 script, which only marks multiple bit errors.

The A6 script should not normally be used because it will not mark off hard single-bit errors.

Soft errors are defined in these tests as single-bit errors, and when the data is rewritten, no error occurs on the next read of the data.

4. Running an individual test

Parameters 1 and 2 determine the starting address for each memory test. Use the SHOW MEMORY command to print out the addresses for all boards. The first board is board 0.

Instead of an address, you can also enter a starting and ending board number. The first board is number 1. After the test starts, board numbers are replaced with the actual addresses.

You can also change the address increment parameter 3 for each memory tests. Tests 4F, 4E, 4A, 4B and 4C run very slowly. The normal address increment for these tests would 256 Kbytes (0x40000) or greater. Smaller increments would normally be used when selecting a smaller address range from starting to ending address. For example, run test 4F on the second memory board, increment address by 100000 hexadecimal (1 MByte), and continue testing if an error occurs.

>>>T 4F 2 2 100000 1

Run test 4C on every location from address 0x40000 to 0x4FFFF. Stop on the first error if any. End address actually specifies the last byte location + 1 to test.

>>>T 4C 40000 50000 8

5. T 40

The SHOW MEMORY command displays pages that are marked bad by the memory tests and is easier to interpret than test 40. There is only one instance in which test 40 reports information that SHOW

MEMORY does not report. Test 40 reports the number of soft errors that have been counted by the memory tests, if any, for each memory board. The default when running test 40 is to ignore soft errors. To count soft errors, enter the following command:

4–38

KA660 CPU System Maintenance

>>>T 40 1 4 0

This command causes all soft and hard errors to be checked against all memory boards present. For soft errors the limit to check against is

0, which is the third parameter. If test 40 fails with SUBTESTLOG =

07, then R5-R8 in the error dump list refers to soft errors for boards 1 through 4.

6. T 9C

The utility 9C is useful after system crashes or similar events because it dumps the current contents of most CPU registers on the KA660.

To help in isolating an FRU, examine registers MEMCSR 0–15 by entering

T 9C at the console I/O mode prompt (Example 4–5). Utility 9C is also useful for examining the error registers MSER, CACR, DSER, and

MEMCSR16, upon a fatal system crash or similar event. See Example 4–5 for an example of T 9C.

Example 4–5: T 9C

>>>>>>T 9C

SBR=017B8000

P0BR=80000000

TODR=0010E085

TCR0=00000000

TCR1=00000001

RXCS=00000000

SCR=0000D000

SLR=00002021 SAVPC=20044827 SAVPSL=04190304

P0LR=00100A80

ICCS=00000000

TIR0=00000000

P1BR=0A0A0A08

TNIR0=00000000

P1LR=000B0B0B

MAPEN=00000000

TIVR0=00000078

TIR1=0052680A TNIR1=0000000F TIVR1=0000007C

RXDB=0000000D TXCS=00000000

DSER=00000000 QBEAR=0000000F

TXDB=00000030

DEAR=00000000

BDR=08D0EFFF DLEDR=0000000C SSCCR=00D55537 CBTCR=00000004

DSSI_0=00 (BUS_0)

PSR_0=00000000

PQBBR_0=03060022

PESR_0=00000000

PMCSR_0=00000000

PFAR_0=00000000

SCBB=20052400

SID=14000006

BDMTR=20084000

BDMKR=0000007C

QBMBR=017F8000

IPCR0=0000

SSHMA_0=0000CA20

PPR_0=00000000

NICSR0=1FFF0003 3=00004030 4=00004050 5=8039FF00 6=83E0F000 7=00000000

NICSR9=04E204E2 10=00040000 11=00000000 12=00000000 13=00000000 15=0000FFFF

NISA=08-00-2B-12-BC-AC RDES0=00441300

TDES0=00008C80

1=00000000

1=07000000

2=05EE0000

2=00400000

3=000046F0

3=000040FA

MEM_FRU 1

MEM_FRU 2

MEM_FRU 3

MEM_FRU 4

MCSR_0=80000017

MCSR_4=81000016

MCSR_8=00000000

MCSR12=00000000

1=80400017

5=81400016

9=00000000

13=00000000

2=80800017

6=00000016

10=00000000

14=00000000

MEMCSR17=00000013 MEMCSR16=00000044 CSR16_page_address=00000000

MSER=00000000 CCR=00000014

3=80C00017

7=00000016

11=00000000

15=00000000

>>>

3

1

2

5

2

2

MEMCSR16 = 8094000F hex = 1000 0000 1001 0100 0000 0000 0000 1111

|| ||

MEMCSR_5 = 80800016 hex = 1000 0000 1000 0000 0000 0000 0001 0110

^ ^ bit 31 set 25:22 match

Troubleshooting and Diagnostics

4–39

4.5.3 Additional Troubleshooting Suggestions

Note the following additional suggestions when diagnosing a possible memory failure.

• If more than one memory module is failing, you should suspect the

KA660 module, CPU/memory cable, backplane, or MS650 modules as the cause of failure.

• Always check the seating of the memory cable first before replacing a

KA660 or MS650 module. If the seating appears to be improper, rerun the tests. Also remember to leave the middle connector disconnected for a three-connector cable when the system is configured with only one

MS650.

• If you are rotating MS650 modules to verify that a particular memory module is causing the failure, be aware that a module may fail in a different way when in a different slot.

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

• If memory errors are found in the error log, use the KA660 ROM-based diagnostics to see if it is an MS650 problem, or if it is related to the

KA660, CPU/memory interconnect cable, or backplane. Follow steps

1–3 of Section 4.4 and Section 4.5.2 to aid in isolating the failure.

• Use the SHOW QBUS, SHOW DEVICE, and SET HOST/DUP commands when troubleshooting I/O subsystem problems.

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

• You can run a DSSI device power-up diagnostic without performing a cold restart or spinning the disk drives down and back up.

Enter the following at the console prompt:

>>>T 58 {node_number}

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

Parameter 1 is the DSSI node ID or port number. It must be in the range of 0–7 (0 is the default). Use the default for parameter 2.

You can perform this test repeatedly with the REPEAT command (

R T

58 {node_ID}

). In that case the drive’s self-tests run repeatedly until you press

CTRL/C to terminate the test.

4–40

KA660 CPU System Maintenance

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

4.6 Loopback Tests and Fuse Problems

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

Check that dc power and pico fuses on the KA660 are functioning correctly.

Three 1.5-A pico fuses (PN 12–10929–08) are located near the handle on the component side of the KA660 module, as shown in Figure 1–1. The fuses are numbered from left to right as follows:

F1, F2: Backplane fingers

F3: Memory and I/O connectors

Replace the fuse, not the KA660, if a fuse has gone bad. Table 4–9 lists some symptoms of faulty fuses.

Table 4–9: KA660 Fuses

Bad Fuse Symptom

F1 bad (+5 V)

F2 bad (+12 V)

Cover panel hexadecimal LED display is off.

Both Thinwire and standard Ethernet LEDs on the CPU cover panel are off.

F3 bad (DSSI Term) DSSI terminator LED is off

Ethernet external loopback test 5F fails (for ThinWire only, since the fuse protects +12 V supplied to the DESTA on the CPU cover panel).

The LED on the loopback connector (PN 12–22196–02) for standard Ethernet is off; external loopback tests for standard Ethernet pass, however.

Console SLU external loopback test fails.

Only local DSSI node (typically node 7 for the KA660) is reported by SHOW DEVICE or SHOW

DSSI commands.

DSSI external loopback test 56 fails.

DSSI Problems

For DSSI problems, run the SHAC external loopback test (test 56). To check the DSSI bus out to the KA660 connector, plug one end of the test cable

(PN 17–02216–01) to the H3281 loopback connector and the other end to the KA660 DSSI connector. To test out to the end of the DSSI bus, turn off the system, remove all DSSI devices with the exception of the KA660

Troubleshooting and Diagnostics

4–41

from the bus, and plug the external DSSI loopback connector in place of the DSSI bus terminator.

Ethernet Problems

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

>>> T 5F 1

Set parameter 1 to run this test. Only the external loopback test runs. Be sure to set the Ethernet Connector switch on the CPU cover panel to the

ThinWire position. Use two 50-ohm H8225 terminators connected to an

H8223 T-connector.

To test the standard Ethernet connector, use loopback connector (PN 12–

22196–02) in conjunction with MDM.

4.6.1 Testing the Console Port

To test the console port at power-up, set the Power-Up Mode switch on the CPU cover panel to the Test position, and install an H3103 loopback connector into the MMP of the cover panel. The H3103 connects the console port transmit and receive lines. At power-up, the SLU_EXT_LOOPBACK

IPT then runs a continuous loopback test.

While the test is running, the LED display on the CPU I/O insert should alternate between 6 and 3. A value of 6 in the display indicates a test failure. If the test fails, one of the following parts is faulty: the KA660

CPU module, the CPU cover panel, or the cabling.

To test out to the end of the console terminal cable:

1. Plug the MMJ end of the console terminal cable into the CPU cover panel.

2. Disconnect the other end of the cable from the terminal.

3. Place an H8572 adapter into the disconnected end of the cable.

4. Connect the H3103 to the H8572.

4.7 Module Self-Tests

Module self-tests run when you turn on the system. A module self-test can detect hard or repeatable errors, but usually not intermittent errors.

Module LEDs display pass/fail test results.

4–42

KA660 CPU System Maintenance

A pass by a module self-test does not guarantee that the module is good, because the test usually checks only the controller logic. The test usually does not check the module Q22-bus interface, the line drivers and receivers, or the connector pins—all of which have relatively high failure rates.

A fail by a module self-test is accurate, because the test does not require any other part of the system to be working.

The following modules do not have LED self-test indicators:

DFA01

DPV11

DRQ3B

DZQ11

KLESI

LPV11

TSV05

The following modules have one green LED, which indicates that the module is receiving +5 and +12 Vdc:

CXA16

CXB16

CXY08

KZQSA

Table 4–10 lists loopback connectors for common KA660 system modules.

Table 4–10: Loopback Connectors for Q22-Bus Devices

Device Module Loopback Cable Loopback

CXA16/CXB16

CXY08

DELQA

DPV11

DSSI

2

DZQ11

Ethernet

3

LPV11

KA660/H3602–00

KMV1A

H3103 + H8572

1

H3046 (50-pin)

PN 12–22196–02

H3259

PN 12–15336–00 or H325

None

H3103

H3255

H3197 (25-pin)

H3260

H329 (PN 12–27351–01)

None

H3103 + H8572

H3251

1

Use the appropriate cable to connect transmit-to-receive lines. H3101 and H3103 are doubleended cable connectors.

2

For DSSI to KA660 or RF-series connector, use PN 17–02216–01 plus H3281 loopback. For connection to end of bus, use the DSSI loopback connector PN 12–30702–01.

3

For ThinWire, use H8223–00 plus two H8225–00 terminators. For standard Ethernet, use

PN 12–22196–02.

Troubleshooting and Diagnostics

4–43

Table 4–10 (Cont.): Loopback Connectors for Q22-Bus Devices

Device

KZQSA

Module Loopback

PN 12-30552-02

Cable Loopback

4.8 ISE Troubleshooting and Diagnostics

An ISE may fail either during initial power-up or during normal operation.

In both cases the failure is indicated by the lighting of the red fault LED on the SCP on the enclosure front panel. The ISE also has a red fault LED, but it is not visible from the outside of the system enclosure.

If the ISE is unable to execute the Power-On Self-Test (POST) successfully, the red fault LED remains lit and the Ready indicator does not light, or both LEDs remain on.

POST is also used to handle two types of error conditions in the ISE:

1.

Controller errors

are caused by the hardware associated with the controller function of the ISE module. A controller error is fatal to the operation of the ISE, since the controller cannot establish a logical connection to the host. The red Fault indicator lights. If this occurs, replace the ISE module.

2.

Drive errors

are caused by the hardware associated with the ISE control function of the ISE module. These errors are not fatal to the ISE, since the ISE can establish a logical connection and report the error to the host. Both LEDs go out for about 1 second, then the red

Fault indicator lights. In this case, run either DRVTST, DRVEXR, or

PARAMS (described in the next sections) to determine the error code.

4–44

KA660 CPU System Maintenance

Here are three common configuration errors:

• More than one node with the same node number

• Identical bus node ID

• Identical unit numbers

The first error cannot be detected by software. Use the SHOW DSSI command to display the second and third errors. This command lists each device connected to the DSSI bus by node name and unit number.

Install the bus node ID plug in the socket on the ISE. If the ISE has no bus node ID plug, the ISE reads its bus node ID from the three-position DIP switch on the side of the ISE.

The ISE contains the following local programs (described in the following sections):

DIRECT

DRVTST

DRVEXR

HISTRY

ERASE

PARAMS

A directory, in DUP specified format, of available local programs

A comprehensive ISE functionality verification test

A utility that exercises the ISE

A utility that saves information retained by the ISE

A utility that erases all user data from the disk

A utility that allows you to look at or change ISE status, history, and parameters

A description of each local program follows, including a table showing the dialog of each program. The table also indicates the type of messages contained in the dialog, although the screen display will not indicate the message type. Message types are abbreviated as follows:

Q—Question

I—Information

T—Termination

FE—Fatal error

Access these local programs using the console SET HOST/DUP command, which creates a virtual terminal connection to the storage device and the designated local program using the Diagnostic and Utilities Protocol (DUP) standard dialog.

Once the connection is established, the local program is in control. When the program terminates, control is returned to the KA660 console. To abort or prematurely terminate a program and return control to the KA660 console, press

CTRL/C or

CTRL/Y

.

Troubleshooting and Diagnostics

4–45

4.8.1 DRVTST

DRVTST is a comprehensive functionality test. Errors detected by this test are isolated to the FRU level. The messages are listed in Table 4–11.

Table 4–11: DRVTST Messages

Message

Type Message

Q

I

I

Q

T or

FE

FE

FE

FE

Copyright © 1990 Digital Equipment Corporation

Write/read anywhere on the medium? [1=yes/(0=no)]

User data will be corrupted. Proceed? [1=yes/(0=no)]

5 minutes to complete.

Test passed.

Unit is currently in use.

1

Operation aborted by user.

xxxx—Unit diagnostics failed.

2 xxxx—Unit read/write test failed.

2

1

Either the ISE is inoperative, in use by a host, or is currently running another local program.

2

Refer to the diagnostic error list at the end of this chapter.

Answering No to the first question (‘‘Write/read...?’’) results in a read-only test. DRVTST, however, writes to a diagnostic area on the disk. Answering

Yes to the first question causes the second question to be displayed.

Answering No to the second question (‘‘Proceed?’’) is the same as answering

No to the first question. Answering Yes to the second question permits write and read operations anywhere on the medium.

DRVTST resets the ECC error counters, then calls the timed I/O routine.

After the timed I/O routine ends (5 minutes), DRVTST saves the counters again. It computes the uncorrectable error rate and byte (symbol) error rate. If either rate is too high, the test fails and the appropriate error code is displayed.

4.8.2 DRVEXR

The DRVEXR local program exercises the ISE. The test is data transfer intensive, and indicates the overall integrity of the device. Table 4–12 lists the DRVEXR messages.

4–46

KA660 CPU System Maintenance

I

I

I

I

T

Q

Q

I

Q

Table 4–12: DRVEXR Messages

Message

Type Message

Copyright © 1990 Digital Equipment Corporation

Write/read anywhere on the medium? [1=yes/(0=no)]

User data will be corrupted. Proceed? [1=yes/(0=no)]

Test time in minutes? [(10)-100] ddd minutes to complete.

dddddddd blocks (512 bytes) transferred.

dddddddd bytes in error (soft).

dddddddd uncorrectable ECC errors (recoverable).

Complete.

Or:

FE

FE

FE

FE

Unit is currently in use.

1

Operation aborted by user.

xxxx—Unit diagnostics failed.

2 xxxx—Unit read/write test failed.

2

1

Either the ISE is inoperative, in use by a host, or is currently running another local program.

2

Refer to the diagnostic error list at the end of this chapter.

Answering No to the first question (

Write/read...?

) results in a read-only test. DRVEXR, however, writes to a diagnostic area on the disk. Answering

Yes to the first question results in the second question being asked.

Answering No to the second question (

Proceed?

) is the same as answering

No to the first question. Answering Yes to the second question permits write and read operations anywhere on the medium.

NOTE:

If the Write-Protect switch on the SCP is pressed in (LED on) and you answer Yes to the second question, the ISE does not allow the test to run. DRVEXR displays the error message

2006---Unit read/write test failed.

In this case, the test has not failed, but has been prevented from running.

DRVEXR saves the error counters, then calls the timed I/O routine. After the timed I/O routine ends, DRVEXR saves the counters again. It then reports the total number of blocks transferred, bits in error, bytes in error, and uncorrectable errors.

DRVEXR uses the same timed I/O routine as DRVTST, with two exceptions.

First, DRVTST always uses a fixed time of five minutes, while you specify

Troubleshooting and Diagnostics

4–47

the time of DRVEXR routine. Second, DRVTST determines whether the

ISE is good or bad. DRVEXR reports the data but does not determine the condition of the ISE.

4.8.3 HISTRY

The HISTRY local program displays information about the history of the

ISE. Table 4–13 lists the HISTRY messages.

Table 4–13: HISTRY Messages

Message

Type Field Length Field Meaning

I

I

I

I

I

I

1

T

I

I

I

I

47 ASCII characters

4 ASCII characters

12 ASCII characters

6 ASCII characters

1 ASCII character

8 ASCII characters

17 ASCII characters

6 ASCII characters

5 ASCII characters

4 ASCII characters

Copyright notice

Product name

Drive serial number

Node name

Allocation class

Firmware revision level

Hardware revision level

Power-on hours

Power cycles

Hexadecimal fault code

Complete

1

Displays the last 11 fault codes as informational messages. Refer to the diagnostic error list at the end of this chapter.

The following example shows a typical screen display when you run

HISTRY:

Copyright © 1988 Digital Equipment Corporation

RF31

EN01082

SUSAN

0

RFX V101

RF31 PCB-5/ECO-00

617

21

A04F

A04F

A103

A04F

A404

A04F

A404

4–48

KA660 CPU System Maintenance

A04F

A404

A04F

A404

Complete.

If no errors have been logged, no hexadecimal fault codes are displayed.

4.8.4 ERASE

The ERASE local program overwrites application data on the ISE while leaving the replacement control table (RCT) intact. This local program is used if an HDA must be replaced, and there is a need to protect confidential or sensitive data.

Use ERASE only if the HDA must be replaced and only after you have backed up all data.

Table 4–14 lists the ERASE messages.

Table 4–14: ERASE Messages

Message

I

Q

Q

I

T or

FE

FE

FE

FE

Copyright © 1988 Digital Equipment Corporation

Write/read anywhere on the medium? [1=yes/(0=no)]

User data will be corrupted. Proceed? [1=yes/(0=no)]

6 minutes to complete.

Complete.

Unit is currently in use.

Operation aborted by user.

xxxx—Unit diagnostics failed.

1 xxxx—Operation failed.

2

1

Refer to the diagnostic error list at the end of this chapter.

2 xxxx = one of the following error codes:

000D : Cannot write the RCT.

000E : Cannot read the RCT.

000F : Cannot find an RBN to revector to.

0010 : The RAM copy of the bad block table is full.

If a failure is detected, the message indicating the failure will be followed by one or more messages containing error codes.

Troubleshooting and Diagnostics

4–49

4.8.5 PARAMS

The PARAMS local program supports modifications to device parameters that you may need to change, such as device node name and allocation class. You invoke it in the same way as the other local programs. However, you use the following commands to make the modifications you need:

EXIT

HELP

SET

SHOW

STATUS

WRITE

Terminates PARAMS program

Prints a brief list of commands and their syntax

Sets a parameter to a value

Displays a parameter or a class of parameters

Displays module configuration, history, or current counters, depending on the status type chosen

Alters the device parameters

4.8.5.1 EXIT

Use the EXIT command to terminate the PARAMS local program.

4.8.5.2 HELP

Use the HELP command to display a brief list of available PARAMS commands, as shown in the example below.

PARAMS> HELP

EXIT

HELP

SET {parameter | .} value

SHOW {parameter | . | /class}

/ALL /CONST /DRIVE

/SERVO /SCS /MSCP

/DUP

STATUS [type]

CONFIG LOGS

PATHS

WRITE

DATALINK

PARAMS>

4.8.5.3 SET

Use the SET command to change the value of a given parameter.

Parameter

is the name or abbreviation of the parameter to be changed. To abbreviate, use the first matching parameter without regard to uniqueness.

Value

is the value assigned to the parameter.

For example, SET NODE SUSAN sets the NODENAME parameter to

SUSAN.

The following parameters are useful:

4–50

KA660 CPU System Maintenance

ALLCLASS

FIVEDIME

UNITNUM

The controller allocation class. The allocation class should be set to match that of the host.

True (1) if MSCP should support five connections with ten credits each. False

(0) if MSCP should support seven connections with seven credits each.

The MSCP unit number.

FORCEUNI True (1) if the unit number should be taken from the DSSI ID. False (0) if the

UNITNUM value should be used instead.

NODENAME The controller’s SCS node name.

FORCENAM True (1) if the SCS node name should be forced to the string RF31x (where x is a letter from A to H corresponding to the DSSI bus ID) instead of using the

NODENAME value. False (0) if NODENAME is to be used.

SYSTEMID The SYSTEMID parameter provides a number that uniquely identifies the ISE to the operating system. This parameter is modified only when replacing an

ISE. Only Customer Services representatives and qualified self-maintenance customers can remove an ISE.

4.8.5.4 SHOW

Use the SHOW command to display the settings of a parameter or a class of parameters. It displays the full name of the parameter (8 characters or less), the current value, the default value, radix and type, and any flags associated with each parameter.

4.8.5.5 STATUS

Use the STATUS command to display module configuration, history, or current counters, depending on the type specified.

Type

is the optional

ASCII string that denotes the type of display desired. If you omit

Type

, all available status information is displayed. If present, it may be abbreviated.

The following types are available.

CONFIG

LOGS

DATALINK

PATHS

Displays the module name, node name, power-on hours, power cycles, and other such configuration information. Unit failures are also displayed, if applicable.

Displays the last eleven machine and bug checks on the module. The display includes the processor registers (D0–D7, A0–A7), the time and date of each failure, and some of the hardware registers.

Displays the data link counters.

Displays available path information (open virtual circuits) from the point of view of the controller. The display includes the remote node names, DSSI IDs, software type and version, and counters for the messages and datagrams sent and/or received.

4.8.5.6 WRITE

Use the WRITE command to write the changes made while in PARAMS to the ISE’s nonvolatile memory. The WRITE command is similar to the

VMS SYSGEN WRITE command. Parameters are not available, but you must be aware of the system and/or ISE requirements and use the WRITE command accordingly or it may not succeed in writing the changes.

Troubleshooting and Diagnostics

4–51

The WRITE command may fail for one of the following reasons:

• You altered a parameter that required the unit, and the unit cannot be acquired (that is, the unit is not in the available state with respect to the host). Changing the unit number is an example of a parameter that requires the unit.

• You altered a parameter that required a controller initialization, and you replied negatively to the request for reboot. Changing the node name or the allocation class are examples of parameters that require controller initialization.

• Initial ISE calibrations were in progress on the unit. The use of the

WRITE command is inhibited while these calibrations are running.

4.9 Diagnostic Error Codes

Diagnostic error codes appear when you are running DRVTST, DRVEXR, or PARAMS. Most of the error codes indicate a failure of the ISE module.

The exceptions are listed below. The error codes are listed in Table 4–15. If you see any error code other than those listed below, replace the module.

Table 4–15: ISE Diagnostic Error Codes

Code Message Meaning

2032/A032 Failed to see FLT go away FLT bit of the spindle control status register was asserted for one of the following reasons:

1. Reference clock not present

2. Stuck rotor

3. Bad connection between HDA and module

203A/A03A Cannot spin up, ACLOW is set in WrtFlt

1314/9314 Front panel is broken

Did not see ACOK signal, which is supplied by the host system power supply for staggered spin-up.

Could be either the module or the operator control panel or both.

4–52

KA660 CPU System Maintenance

Appendix A

KA660 CPU Address Assignments

This appendix lists the CPU address assignments in general and detail for various aspects of memory.

A.1 KA660 Physical Address Space

Table A–1 lists general address assignments for VAX memory and I/O space.

KA660 CPU Address Assignments

A–1

Table A–1: General Local Address Space Map

Address Range Description

VAX Memory Space

0000 0000 - 1FFF FFFF Local Memory Space (512 Mbytes)

VAX I/O Space

2000 0000 - 2000 1FFF

2000 2000 - 2003 FFFF

2004 0000 - 2007 FFFF

2008 0000 - 201F FFFF

2020 0000 - 23FF FFFF

2400 0000 - 27FF FFFF

2008 0000 - 2BFF FFFF

2C08 0000 - 2FFF FFFF

3000 0000 - 303F FFFF

3040 0000 - 33FF FFFF

3400 0000 - 37FF FFFF

3800 0000 - 3BFF FFFF

3C00 0000 - 3FFF FFFF

Local Q22-Bus I/O Space (8 Kbytes)

Reserved Local I/O Space (248 Kbytes)

Local ROM Space

Local Register I/O Space (1.5 Mbytes)

Reserved Local I/O Space (62.5 Mbytes)

Reserved Local I/O Space (64 Mbytes)

Reserved Local I/O Space (64 Mbytes)

Reserved Local I/O Space (64 Mbytes)

Local Q22-Bus Memory Space (4 Mbytes)

Reserved Local I/O Space (60 Mbytes)

Reserved Local I/O Space (64 Mbytes)

Reserved Local I/O Space (64 Mbytes)

Reserved Local I/O Space (64 Mbytes)

A–2

KA660 CPU System Maintenance

A.2 KA660 Detailed Physical Address Map

Table A–2 lists detailed address assignments for VAX memory and I/O space.

Table A–2: Detailed Local Address Space Map

Description Address Range

VAX Memory Space

Local Memory Space, 64 Mbytes (Q22-bus Map at top 32 Kbytes of Main Memory)

0000 0000 - 03FF FFFF

Reserved Memory Space (448 Mbytes) 0400 0000 - 1FFF FFFF

Local Q22-bus I/O Space

Reserved Q22-bus I/O Space

Q22-bus Floating Address Space

User Reserved Q22-bus I/O Space

Reserved Q22-bus I/O Space

Interprocessor Comm Reg

Reserved Q22-bus I/O Space

Local Register I/O Space

Reserved Local Register I/O Space

SHAC SSWCR

Reserved Local Register I/O Space

SHAC SSHMA

SHAC PQBBR

SHAC PSR

SHAC PESR

SHAC PFAR

SHAC PPR

2000 0000 - 2000 1FFF

2000 0000 - 2000 0007

2000 0008 - 2000 07FF

2000 0800 - 2000 0FFF

2000 1000 - 2000 1F3F

2000 1F40

2000 1F44 - 2000 1FFF

2000 2000 - 2003 FFFF

2000 4202 - 2000 422F

2000 4230

2000 4234 - 2000 4043

2000 4244

2000 4248

2000 424C

2000 4250

2000 4254

2000 4258

KA660 CPU Address Assignments

A–3

Table A–2 (Cont.): Detailed Local Address Space Map

Description Address Range

Local Register I/O Space 2000 2000 - 2003 FFFF

SHAC PMCSR

Reserved Local Register I/O Space

SHAC PCQ0CR

SHAC PCQ1CR

SHAC PCQ2CR

SHAC PCQ3CR

SHAC PDFQCR

SHAC PMFQCR

SHAC PSRCR

SHAC PECR

SHAC PDCR

SHAC PICR

SHAC PMTCR

SHAC PMTECR

Reserved Local Register I/O Space

NICSR0 - Vector Add, IPL, Sync/Async

NICSR1 - Polling Demand Register

NICSR2 - Reserved

NICSR3 - Receiver List Address

NICSR4 - Transmitter List Address

NICSR5 - Status Register

NICSR6 - Command and Mode Register

NICSR7 - System Base Address

2000 425C

2000 4260 - 2000 427F

2000 4280

2000 4284

2000 4288

2000 428C

2000 4290

2000 4294

2000 4298

2000 429C

2000 42A0

2000 42A4

2000 42A8

2000 42AC

2000 42B0 - 2000 7FFF

2000 8000

2000 8004

2000 8008

2000 800C

2000 8010

2000 8014

2000 8018

2000 801C

A–4

KA660 CPU System Maintenance

Table A–2 (Cont.): Detailed Local Address Space Map

Description Address Range

Local Register I/O Space 2000 2000 - 2003 FFFF

NICSR8 - Reserved

NICSR9 - Watchdog Timers

NICSR10- Reserved

NICSR11- Rev Num & Missed Frame Count

NICSR12- Reserved

NICSR13- Breakpoint Address

NICSR14- Reserved

NICSR15- Diagnostic Mode & Status

Reserved Local Register I/O Space

2000 8020+

2000 8024+

2000 8028+

2000 802C+

2000 8030+

2000 8034+

2000 8038+

2000 803C

2000 8040 - 2003 FFFF

Local EPROM I/O Space

µVAX System Type Register (In EPROM)

Local EPROM - (Halt Protected)

Local Register I/O Space

Q22 System Configuration Register

Q22 System Error Register

Q22 Master Error Address Register

Q22 Slave Error Address Register

Q22-bus Map Base Register

Reserved Local Register I/O Space

Main Memory Error Status Register

Main Memory Control/Diag Status Register

Reserved Local Register I/O Space

2004 0000 - 2007 FFFF

2004 0004

2004 0000 - 2007 FFFF

2008 0000 - 201F FFFF

2008 0000

2008 0004

2008 0008

2008 000C

2008 0010

2008 0014 - 2008 00FF

2008 0140

2008 0144

2008 0148 - 2008 3FFF

KA660 CPU Address Assignments

A–5

Table A–2 (Cont.): Detailed Local Address Space Map

Description Address Range

Local Register I/O Space 2008 0000 - 201F FFFF

Boot and Diagnostic Reg (32 Copies)

Reserved Local Register I/O Space

Q22-bus Map Registers

Reserved Local Register I/O Space

SSC Base Address Register

SSC Configuration Register

CDAL Bus Timeout Control Register

Diagnostic LED Register

Reserved Local Register I/O Space

2008 4000 - 2008 407C

2008 4080 - 2008 7FFF

2008 8000 - 2008 FFFF

2009 0000 - 2013 FFFF

2014 0000

2014 0010

2014 0020

2014 0030

2014 0034 - 2014 006B

NOTE:

The following addresses allow those KA660 internal processor registers that are implemented in the SSC chip (external, internal processor registers) to be accessed via the local I/O page. These addresses are documented for diagnostic purposes only and should not be used by nondiagnostic programs.)

Time Of Year Register

Console Storage Receiver Status

Console Storage Receiver Data

Console Storage Transmitter Status

Console Storage Transmitter Data

Console Receiver Control/Status

Console Receiver Data Buffer

Console Transmitter Control/Status

2014 006C

2014 0070*

2014 0074*

2014 0078*

2014 007C*

2014 0080

2014 0084

2014 0088

A–6

KA660 CPU System Maintenance

Table A–2 (Cont.): Detailed Local Address Space Map

Description Address Range

Console Transmitter Data Buffer

Reserved Local Register I/O Space

I/O Bus Reset Register

Reserved Local Register I/O Space

Rom Data Register

Bus Timeout Counter

Interval Timer

Reserved Local Register I/O Space

Timer 0 Control Register

Timer 0 Interval Register

Timer 0 Next Interval Register

Timer 0 Interrupt Vector

Timer 1 Control Register

Timer 1 Interval Register

Timer 1 Next Interval Register

Timer 1 Interrupt Vector

Reserved Local Register I/O Space

BDR Address Decode Match Register

BDR Address Decode Mask Register

Reserved Local Register I/O Space

Battery Backed-Up RAM

2014 008C

2014 0090 - 2014 00DB

2014 00DC

2014 00E0

2014 00F0**

2014 00F4**

2014 00F8**

2014 00FC - 2014 00FF

2014 0100

2014 0104

2014 0108

2014 010C

2014 0110

2014 0114

2014 0118

2014 011C

2014 0120 - 2014 012F

2014 0130

2014 0134

2014 0138 - 2014 03FF

2014 0400 - 2014 07FF

KA660 CPU Address Assignments

A–7

Table A–2 (Cont.): Detailed Local Address Space Map

Description Address Range

Reserved Local Register I/O Space

Reserved Local I/O Space

Local Q22-bus Memory Space

Reserved Local Register I/O Space

2014 0800 - 201F FFFF

2020 0000 - 2FFF FFFF

3000 0000 - 303F FFFF

3040 0000 - 3FFF FFFF

A–8

KA660 CPU System Maintenance

32

33

34

35

55

28

29

30

31

A.3 External and Internal Processor Registers

Several of the internal processor registers (IPR’s) on the KA660 are implemented in the SSC chip rather than the SOC CPU chip. These registers are referred to as external and internal processor registers and are listed below.

Table A–3: External, Internal Processor Registers

IPR # Register Name Mnemonic

27 Time of Year Register TOY

Console Storage Receiver Status CSRS*

Console Storage Receiver Data

Console Storage Transmitter Status

CSRD*

CSTS*

Console Storage Transmitter Data CSDB*

Console Receiver Control/Status RXCS

Console Receiver Data Buffer RXDB

Console Transmitter Control/

Status

TXCS

Console Transmitter Data Buffer TXDB

I/O System Reset Register IORESET

KA660 CPU Address Assignments

A–9

A.4 Global Q22-Bus Physical Address Space

Table A–4 lists the global Q22-bus physical address map.

Table A–4: Global Q22-bus Physical Address Map

Description Address Range

Q22-bus Memory Space

Q22-bus Memory Space (Octal) 0000 0000 - 1777 7777

Q22-bus I/O Space (BBS7 Asserted)

Q22-bus I/O Space (Octal)

Reserved Q22-bus I/O Space

Q22-bus Floating Address Space

User Reserved Q22-bus I/O Space

Reserved Q22-bus I/O Space

Interprocessor Comm Reg

Reserved Q22-bus I/O Space

1776 0000 - 1777 7777

1776 0000 - 1776 0007

1776 0010 - 1776 3777

1776 4000 - 1776 7777

1777 0000 - 1777 7477

1777 7500

1777 7502 - 1777 7777

A–10

KA660 CPU System Maintenance

Appendix B

Programming Parameters for RF-Series

ISEs

This appendix describes the procedures for setting and examining parameters for RF-series ISEs.

Two types of DSSI storage adapters are available for VAX 4000, MicroVAX

3000-series, MicroVAX II, and DECsystem systems: an embedded DSSI host adapter that is part of the CPU and the KFQSA storage adapter.

Each storage adapter provides a separate DSSI bus that can support up to seven RF-series ISEs (six ISEs for a dual-host configuration). The adapters make a connection between the CPU and the requested ISE on their respective DSSI bus. Each ISE has its own controller and server that contain the intelligence and logic necessary to control data transfers over the DSSI bus.

B.1 RF-Series ISE Parameters

Six principal parameters are associated with each RF-series ISE:

• Bus Node ID

• ALLCLASS

• UNITNUM

• FORCEUNI

• NODENAME

• SYSTEMID

NOTE:

Each of the above ISE parameters, with the exception of the Bus

Node ID, are programmed and examined using the console-based Diagnostic and Utility Protocol (DUP) driver utility. The ISE Bus Node ID is physically determined by the numbered bus node ID plug that inserts into the ISE front panel.

Programming Parameters for RF-Series ISEs

B–1

A brief description of each parameter follows:

The Bus Node ID parameter is provided by the bus node ID plug on the

ISE front panel. Each DSSI bus can support up to seven ISEs, bus nodes

0 through 6 (0 through 5 for dual-host systems). Refer to your

Operation

manual for instructions on changing bus node ID plugs.

The ALLCLASS parameter determines the device allocation class. The allocation class is a numeric value from 0 to 255 that is used by the VMS operating system to derive a path-independent name for multiple access paths to the same ISE. RF-series ISEs are shipped from the factory with a default allocation class of zero. Each RF-series ISE to be served to the cluster should have an allocation class that matches the allocation class of the host system. Refer to the

VMS VAXcluster

manual for rules for specifying allocation class values.

The UNITNUM parameter determines the unit number of the ISE. By default, the ISE unit number is supplied by the Bus Node ID plug on the

ISE front panel. Certain multiple bus configurations, described later on in this section, require that the default values be replaced with unique ISE unit numbers. To set unit numbers and override the default values, you use the console-based DUP driver utility to supply values to the UNITNUM parameter and to set a value of zero to ISE parameter FORCEUNI.

The FORCEUNI parameter controls the use of UNITNUM to override the default ISE unit number supplied by the Bus Node ID plug. When

FORCEUNI is set to a value of zero, the operating system uses the value assigned to the UNITNUM parameter; when FORCEUNI is set to a value of one, the operating system uses the value supplied by the Bus Node ID plug.

The NODENAME parameter allows each ISE to have an alphanumeric node name of up to eight characters. RF-series ISEs are shipped from the factory with a unique identifier, such as R7CZZC, R7ALUC, and so on. You can provide a node name of your choosing if you prefer.

The SYSTEMID parameter provides a number that uniquely identifies the ISE to the operating system. This parameter is modified only when replacing an ISE. Only Customer Services representatives and qualified self-maintenance customers can remove an ISE.

The following describes how the operating system uses the ISE parameters to form unique identifiers for each ISE. Configurations that require you to assign new unit numbers for ISEs are also described.

With an allocation class of zero, the operating system can use the default parameter values to provide each ISE with a unique device name. The operating system uses the node name along with the device logical name in the following manner:

B–2

KA660 CPU System Maintenance

NODENAME$DIA

u

where:

NODENAME is a unique node name and

u

is the unit number.

With a nonzero allocation class, the operating system relies on unit number values to create a unique device name. The operating system uses the allocation class along with the device logical name in the following manner:

$ALLCLASS$DIA

u

where:

ALLCLASS is the allocation class for the system and ISEs, and

u

is a unique unit number.

Using the KFQSA storage adapter and mass storage expanders, you can fill multiple DSSI busses. Each bus can have seven ISEs (bus nodes 0–

6). When a second bus is added to the system, and your system is using a nonzero allocation class, you need to assign new unit numbers for ISEs on one of the busses, as the unit numbers for ISEs throughout the system must be unique. Table B–1 illustrates the need to program unit numbers for a system using both more than one DSSI bus and a nonzero allocation class. In the case of the nonzero allocation class, the operating system sees the ISEs as having duplicate device names.

Programming Parameters for RF-Series ISEs

B–3

Table B–1: How the VMS Operating System Identifies the ISEs

Allocation Class=0

Nonzero Allocation Class (Example;

ALLCLASS=1)

R7CZZC$DIA0 $1$DIA0

R7ALUC$DIA1

R7EB3C$DIA2

R7IDFC$DIA0

R7IBZC$DIA1

R7IKJC$DIA2

R7ID3C$DIA3

$1$DIA1

$1$DIA2

$1$DIA0

$1$DIA1

$1$DIA2

$1$DIA3

R7XA4C$DIA4

R7QIYC$DIA5

$1$DIA4

$1$DIA5

R7DA4C$DIA6 $1$DIA6

Nonzero allocation class examples with an asterisk indicate duplicate device names. For one of the DSSI busses, the unit numbers need to be reprogrammed to avoid this error.

The following instructions describe how to change ISE parameters using the DUP driver utility. In the sample procedures, the allocation class will be set to 2, the ISEs will be assigned new unit numbers, and the system disk will be assigned a new node name.

1. Enter the console mode.

The procedure for programming internal parameters for RF-series ISEs requires that you issue commands to those RF-series ISEs at the console prompt (>>>). You may enter these commands in either uppercase or lowercase letters. Unless otherwise instructed, enter each command, then press Return.

Enter console mode as follows: a. Set the Break Enable/Disable switch on the CPU cover panel to the enable position.

b. Set the power switch for each unit (both hosts for a dual-host system, and any expanders for expanded systems) to on (1).

Wait for the system to display the console prompt (

>>>

).

B–4

KA660 CPU System Maintenance

2. Make sure the ISEs for which you want to set parameters are on line and are not write protected. The Run/Ready button should be (lit), and the Write-Protect button should be out (not lit).

3. For systems with embedded DSSI, enter

SHOW DSSI at the console prompt for a display of all DSSI devices in your expanded system. For

KFQSA-based DSSI, enter

SHOW UQSSP

.

The firmware displays two lines of information for each ISE. The first line contains the node number and node name. The second line contains the device name and unit number followed by the device type in parentheses.

For embedded DSSI, the device name consists of the letters DIA

n

and the DSSI host adapter is identified by an asterisk (*). For KFQSAbased DSSI, the device name consists of the letters DU

cn

, where

c

is the controller letter, and

n

is a unique unit number.

The following examples show a system with three RF31 ISEs. Example B–1 shows a system with embedded DSSI and Example B–2 shows a system with KFQSA-based DSSI.

Example B–1: SHOW DSSI Display (Embedded DSSI)

>>>SHOW DSSI

DSSI Bus 0 Node 0 (R7CZZC)

-DIA0 (RF31)

DSSI Bus 0 Node 1 (R7ALUC)

-DIA1 (RF31)

DSSI Bus 0 Node 2 (R7EB3C)

-DIA2 (RF31)

DSSI Bus 0 Node 7 (*)

>>>

Programming Parameters for RF-Series ISEs

B–5

Example B–2: SHOW UQSSP Display (KFQSA-Based DSSI)

>>>SHOW UQSSP

UQSSP Disk Controller 0 (772150)

-DUA0 (RF31)

UQSSP Disk Controller 1 (760334)

-DUB1 (RF31)

UQSSP Disk Controller 2 (760340)

-DUC2 (RF31)

UQSSP Tape Controller 0 (774500)

-MUA0 (TK70)

In this example, each ISE will be assigned an allocation class of 2, and the system disk will be given a new node name. Also, ISEs DIA0, DIA1, and

DIA2 (or DUA0, DUB1, and DUC2) will be assigned unit numbers 10, 11, and 12, respectively.

B.2 Entering the DUP Driver Utility

To examine and change internal RF-series ISE parameters, you must first activate the DUP driver utility by setting host to the specific ISE for which you want to modify or examine parameters.

Use the following command for embedded DSSI:

SET HOST/DUP/DSSI <node_number> PARAMS

where:

<node_number> is the bus node ID (0–6) for the ISE on the bus.

Use the following command for KFQSA-based DSSI:

SET HOST/DUP/UQSSP/DISK <node_number> PARAMS

where:

<node_number> is the bus node ID (0–6) for the ISE on the bus.

The following examples show the commands entered at the console prompt to start the DUP server for the ISE at node 0. In Example B–3, you enter

SET HOST/DUP/DSSI 0 PARAMS for embedded DSSI. In Example B–4, you enter

SET HOST/DUP/UQSSP/DISK 0 PARAMS for KFQSA-based DSSI.

B–6

KA660 CPU System Maintenance

Example B–3: Starting the DUP Driver Utility (Embedded DSSI)

>>>SET HOST/DUP/DSSI 0 PARAMS

Starting DUP server...

Copyright (c) 1990 Digital Equipment Corporation

PARAMS>

Example B–4: Starting the DUP Driver Utility (KFQSA-Based DSSI)

>>>SET HOST/DUP/UQSSP/DISK 0 PARAMS

Starting DUP server...

Copyright (c) 1990 Digital Equipment Corporation

PARAMS>

B.3 Setting Allocation Class

After entering the DUP driver utility for a specified ISE, you can examine and set the allocation class for the ISE as follows:

1. At the

PARAMS> prompt, enter

SHOW ALLCLASS to check the allocation class of the ISE to which you are currently connected.

2. Enter

SET ALLCLASS 2

(or enter the allocation class you desire).

3. Enter

SHOW ALLCLASS to verify the new allocation class.

Example B–5 shows the steps for examining and changing the allocation class for a specified ISE. In the example, the allocation class is changed from an allocation class of 0 to an allocation class of 2.

Programming Parameters for RF-Series ISEs

B–7

Example B–5: Setting Allocation Class for a Specified ISE

PARAMS>SHOW ALLCLASS

Parameter Current Default Type Radix

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

ALLCLASS 0 0 Byte Dec B

PARAMS>SET ALLCLASS 2

PARAMS>SHOW ALLCLASS

Parameter Current Default Type Radix

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

ALLCLASS 2 0 Byte Dec B

B.4 Setting Unit Number

After entering the DUP driver utility for a specified ISE, you can examine and set the unit number for the ISE as follows:

1. At the

PARAMS> prompt, enter

SHOW UNITNUM to check the unit number of the ISE to which you are currently connected.

2. Enter

SET UNITNUM 10

(or enter the unit number you desire).

3. Enter

SET FORCEUNI 0 to override the default unit number value supplied by the bus node ID plug.

4. Enter

SHOW UNITNUM to verify the new unit number.

5. Enter

SHOW FORCEUNI to verify that the current value for the

FORCEUNI parameter is 0.

Example B–6 shows the steps for changing the unit number of a specified ISE from unit number 0 to unit number 10.

6. Label the ISE with its unit number, using the unit number labels shipped with your system. Figure B–1 shows where to affix a unit number label on the ISE front panel.

B–8

KA660 CPU System Maintenance

Example B–6: Setting a Unit Number for a Specified ISE

PARAMS>SHOW

UNITNUM

Parameter Current Default Type Radix

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

UNITNUM 0 0 Word Dec U

PARAMS>SET UNITNUM 10

PARAMS>SET FORCEUNI 0

PARAMS>SHOW UNITNUM

Parameter Current Default Type Radix

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

UNITNUM 10 0 Word Dec U

PARAMS>SHOW FORCEUNI

Parameter Current Default Type Radix

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

FORCEUNI 0 1 Boolean 0/1 U

Figure B–1: Attaching a Unit Number Label to the ISE Front Panel

Attach Unit

Number Label

0

10

MLO-004237

Programming Parameters for RF-Series ISEs

B–9

B.5 Setting Node Name

After entering the DUP driver utility for a specified ISE, you can examine and set the node name for the ISE as follows:

1. At the

PARAMS> prompt, enter

SHOW NODENAME to check the node name of the ISE to which you are currently connected.

2. Enter

SET NODENAME SYSDSK

(or enter the desired alphanumeric node name of up to eight characters).

3. Enter

SHOW NODENAME to verify the new node name.

Example B–7 shows the steps for changing the node name of a specified

ISE from the factory-supplied name to SYSDSK.

Example B–7: Changing a Node Name for a Specified ISE

PARAMS>SHOW NODENAME

Parameter Current Default Type Radix

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

NODENAME R7CZZC RF31 String Ascii

PARAMS>SET NODENAME SYSDSK

PARAMS>SHOW NODENAME

Parameter Current Default Type Radix

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

NODENAME SYSDSK RF31 String Ascii

B

B

B.6 Setting System ID

NOTE:

This parameter is modified only when replacing an ISE. Only

Customer Services representatives and qualified self-maintenance customers should remove an ISE. All parameters for the replacement ISE should be programmed to match those of the original ISE. When replacing a ISE, be sure to set the SYSTEMID parameter to match the that of the original.

After entering the DUP driver utility for a specified ISE, you can examine and set the system ID for the ISE as follows:

1. At the

PARAMS> prompt, enter

SHOW SYSTEMID to check the system ID of the ISE to which you are currently connected.

2. Enter

SET SYSTEMID System ID

(enter the desired serial number-based system ID).

B–10

KA660 CPU System Maintenance

3. Enter

SHOW SYSTEMID to verify the new system ID.

Example B–8 shows the steps for changing the system ID of a specified ISE from the factory-supplied system ID to 1402193310841 (the system ID for the replacement ISE is programmed to match that of the original ISE).

Example B–8: Changing a System ID for a Specified ISE

PARAMS>SHOW SYSTEMID

Parameter Current Default Type Radix

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

SYSTEMID 0402193310841 0000000000000 Quadword Hex B

PARAMS>SET SYSTEMID 1402193310841

PARAMS>SHOW SYSTEMID

Parameter Current Default Type Radix

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

SYSTEMID 1402193310841 0000000000000 Quadword Hex B

B.7 Exiting the DUP Server Utility

After you have completed setting and examining internal ISE parameters, enter the WRITE command at the

PARAMS> prompt to save the ISE parameters you have changed using the

SET command. The changes are recorded to nonvolatile memory.

If you have changed the allocation class or node name of an ISE, the DUP driver utility will ask you to initialize the controller. Answer Yes (Y) to allow the changes to be recorded and to exit the DUP driver utility.

If you have not changed the allocation class or node name, enter the EXIT command at the

PARAMS> prompt to exit the DUP driver utility for the specified ISE. Example B–9 shows the procedure for saving parameter changes. In the example, the controller is initialized.

Programming Parameters for RF-Series ISEs

B–11

Example B–9: Exiting the DUP Driver Utility for a Specified ISE

PARAMS>WRITE

Changes require controller initialization, ok? [Y/(N)] Y

Stopping DUP server...

>>>

NOTE:

You must repeat the procedures in this chapter for each ISE for which you want to change parameters.

Example B–10 shows the display for the SHOW DSSI command for a system with embedded DSSI after the unit numbers for the ISEs have been changed from 0, 1, and 2 to 10, 11, and 12. Notice that the bus 0 device names are now DIA10, DIA11, and DIA12.

Example B–10: SHOW DSSI Display

>>>SHOW DSSI

DSSI Bus 0 Node 0 (SYSDSK)

-DIA10 (RF31)

DSSI Bus 0 Node 1 (R7ALUC)

-DIA11 (RF31)

DSSI Bus 0 Node 2 (R7EB3C)

-DIA12 (RF31)

DSSI Bus 0 Node 7 (*)

>>>

Example B–11 shows the display for the SHOW UQSSP command for a system with KFQSA-based DSSI.

B–12

KA660 CPU System Maintenance

Example B–11: SHOW UQSSP Display (KFQSA-Based DSSI)

>>>SHOW UQSSP

UQSSP Disk Controller 0 (772150)

-DUA0 (RF31)

UQSSP Disk Controller 1 (760334)

-DUB1 (RF31)

UQSSP Disk Controller 2 (760340)

-DUC2 (RF31)

UQSSP Tape Controller 0 (774500)

-MUA0 (TK70)

Programming Parameters for RF-Series ISEs

B–13

! (comment command), 3–49

9E utility, 4–7 examples, 4–8

9C utility, 4–31, 4–39

A

Acceptance testing, 4–30

Address assignments, A–1 processor registers, A–9 to

A–10

ALLCLASS, B–2 setting, B–7

B

BOOT command, 3–18

Boot Devices, 3–20 names, 3–20 supported, 3–20

Boot devices, supported, 3–20

Boot flags, 3–19

Bootstrap conditions, 3–7 device names, 3–19 initialization, 3–7

BREAK ignored, 3–11

Bus length (DSSI), 2–6

C

Cabling

BA215, 2–5

BA430, 2–5

CPU to memory, 1–10

DSSI, 2–5

ISE, 2–5

Index

Cache memory, 1–4

CFPA chip, 1–4

CMCTL chip, 1–4

Comment command (!), 3–49

Configuration, 2–1 to 2–9 and module order, 2–1

DSSI, 2–4 dual-host, 2–7 rules, 2–2 worksheet, 2–7

CONFIGURE command, 2–3, 3–22

Connector, CPU to memory, 1–10

Console commands address space control qualifiers,

3–15 address specifiers, 3–11 binary load and unload (X), 3–47

BOOT, 3–18

! (comment), 3–49

CONFIGURE, 3–22

CONTINUE, 3–24 data control qualifiers, 3–15

DEPOSIT, 3–24

EXAMINE, 3–25

FIND, 3–26

HALT, 3–27

HELP, 3–27

INITIALIZE, 3–29 keywords, 3–16

MOVE, 3–30

NEXT, 3–31 qualifier and argument conventions, x qualifiers, 3–15

REPEAT, 3–32

SEARCH, 3–33

SET, 3–35

Index–1

Console commands (Cont.)

SHOW, 3–39

START, 3–43 symbolic addresses, 3–11 syntax, 3–9

TEST, 3–44

UNJAM, 3–47

X (binary load and unload), 3–47

Console displays, 4–10 and FRUs, 4–14

Console error messages, 4–27 list of, 4–28 sample of, 4–11

Console I/O mode restart caution, 3–4 special characters, 3–9

Console port, testing, 4–42

CONTINUE command, 3–24

CPU cover panel, 1–9

CQBIC, 1–6

Current and power values, 2–9

D

DEPOSIT command, 3–24

Diagnostic executive, 4–3 error field, 4–11

Diagnostic tests list of, 4–3 parameters for, 4–3

DRVEXR local program, 4–35, 4–46

DRVTST local program, 4–35, 4–46

DSSI bus characteristics, 1–6 bus length, 2–6 bus termination, 2–6 cabling, 2–5 configuration, 2–4 drive order, 2–4 dual-host, 2–6 dual-host configuration, 2–7 node ID, 2–4 testing with H3281 loopback,

4–41 unique addresses, 4–34

Dual-host capability, 2–6 configuration, 2–7

DUP driver utility, B–1, B–4 entering, B–6 exiting, B–11

E

Entry and dispatch code, 3–2

ERASE local program, 4–49

Error messages console, list of, 4–28 console, sample of, 4–11 halt, 4–27

VMB, 4–29

Errors messages incorrect boot device name,

3–20

Ethernet interface chip (SGEC), 1–6

EXAMINE command, 3–25

F

FE utility, 4–36

FIND command, 3–26

Firmware, 1–5, 3–1 to 3–49 power-up sequence, 3–4

Floating-point accelerator (CFPA),

1–4

FORCEUNI, B–2

FRUs and console display, 4–14

Fuses, on KA660 module, 4–41

G

General purpose registers (GPR) in error display, 4–13 initialization of, 3–7 symbolic addresses for, 3–11

H

H3103 loopback connector, 3–4,

4–42

Index–2

H3281 loopback connector for DSSI,

4–41

H3602–00 CPU cover panel, 1–9

H3602–00 I/O panel, 4–42

H3602–00 mode switch set to language inquiry, 3–5 set to normal, 3–6 set to test, 3–4

H8572 loopback connector, 4–42

HALT command, 3–27

Halts conditions for external halt, 3–3 entry and dispatch code, 3–2 messages, list of, 4–27 registers saved, 3–2 registers set to fixed values, 3–2

HELP command, 3–27

HISTRY local program, 4–36, 4–48

I

INITIALIZE command, 3–29

Initial power-up test

See IPT

Internal processor registers (IPR) symbolic addresses for, 3–12

IPT, 3–4

ISE cabling, 2–5 configuration errors, 4–45 diagnostic error codes, 4–52 diagnostics, 4–44

ISE local programs

DRVEXR, 4–35, 4–46

DRVTST, 4–35, 4–46

ERASE, 4–49

HISTRY, 4–36, 4–48 list of, 4–45

PARAMS, 4–36, 4–50

K

KA660 fuses, 4–41

LEDs, 4–26

KA660 (Cont.) variants, 1–1

L

Language selection menu conditions for display of, 3–5 example of, 3–6 messages, list of, 3–5

Load module, M9060–YA, 2–7

Loopback testing serial line using H3103,

3–4

Loopback connectors

H3103, 3–4, 4–42

H8572, 4–42 list of, 4–43 tests, 4–41

M

M9060–A load module, 2–7

MEMCSR 0–15, 4–31

Memory acceptance testing of, 4–31 cache, 1–4 controller chip (CMCTL), 1–4 isolating FRU, 4–32, 4–37 on KA660, 1–4 testing, 4–37

Module configuration, 2–3 order, in backplane, 2–1 self-tests, 4–42

MOVE command, 3–30

MS650–Bn memory modules, 1–10

N

NEXT command, 3–31

Node ID changing KA660, 2–5 for dual-host systems, 2–7

NODENAME, B–2 setting, B–10

Index–3

O

OCP, 4–45

P

Parameters for diagnostic tests, 4–6 in error display, 4–12

PARAMS local program, 4–36, 4–50 commands, 4–50

Physical Address Space, A–1 to A–8

Physical memory symbolic addresses for, 3–12

Power supply minimum load, 2–9

Power-up sequence, 3–4

Power values, 2–9

Q

Q22-bus interface chip (CQBIC), 1–6

R

REPEAT command, 3–32

Restart caution, 3–4

RF-series ISE node ID switches, 2–4

ROM-based diagnostics, 4–2 to

4–52 and memory testing, 4–39 list of, 4–3 parameters, 4–3 utilities, 4–3

S

SCP cabling, 2–5

Scripts, 4–3, 4–6 to 4–9 creation of, using 9E utility, 4–7 list of, 4–7

SEARCH command, 3–33

Self-test, for modules, 4–42

Serial line test using H3103, 3–4

SET command, 3–35

SET HOST/DUP command, 3–36

SGEC, 1–6

SHOW command, 3–39

SHOW commands, B–5

SOC chip, 1–3

SSC (system support chip), 1–5

START command, 3–43

Symbolic addresses, 3–11 for any address space, 3–14 for GPRs, 3–11 for IPRs, 3–12 for physical memory, 3–12

System control panel

See SCP

SYSTEMID, B–2 setting, B–10

System support chip (SSC), 1–5

T

TEST command, 3–44

Tests, diagnostic list of, 4–3 parameters for, 4–6

Troubleshooting, 4–36 to 4–52

U

UNITNUM, B–2 setting, B–8

UNJAM command, 3–47

Utilities, diagnostic, 4–3

V

Virtual memory bootstrap

See VMB

VMB, 3–7 boot flags, 3–19 error messages, 4–29

X

X command, 3–47

Index–4

Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Related manuals