Digital PDFs

AA-PFM6C-TE

August 1993

100 pages

Original

5.1MB

Document:	KAV30 Hardware Installation and User’s Information
Order Number:	AA-PFM6C-TE
Revision:	0
Pages:	100
Original Filename:	AA-PFM6C-TE_KAV30_Hardware_Installation_and_Users_Information_Aug93.pdf

OCR Text

SDSHGEE

KAV30
Hardware Installation and User’s
Information
\

Order Number:

AA-PFM6C-TE

KAV30
Hardware Installation and User’s
Information
Order Number:

AA-PFM6C-TE

August 1993
This guide describes how to install and operate the KAV30 hardware.

Revision Information:

Digital Equipment Corporation
Maynard, Massachusetts

This manual supersedes the KAV30
Hardware Installation and User’s
Information, Version 1.1 (Order Number
AA-PFM6B-TE).

August

1993

Digital Equipment Corporation makes no representations that the use of its products in the
manner described in this publication will not infringe on existing or future patent rights, nor do

the descriptions contained in this publication imply the granting of hcenses to make, use, or sell
equipment or software in accordance with the description.
© Digital Equipment

Corporation

The postpaid Reader’s Comments

1992,

following

are

trademarks

DECconnect, DECnet,
the DIGITAL logo.
Motorola and
Corporation.

68000

DELNI,

forms at the end of this document

evaluation to assist in preparing future
The

1993.

of Digital

DESTA,

documentation.
Equipment

Corporation:

request your critical

CVAX,

DDCMP,

Digital, ThinWire, rtVAX, VAX, VAXELN,

are registered trademarks

of Motorola,

This document was prepared using VAX DOCUMENT,

Inc.

DEC,

VMS,

Intel is a trademark

Version 2.1.

and

of Intel

Contents
Preface

Preparing to Install the KAV30
1.1
1.2
1.3

Physical and Environmental Requirements .................
Unpacking Instructions .........0.
20.000. cece
ene
KAV30 Orientation...
0.0... 000.
eee

Installing the KAV30
2.1
2.2
2.3
2.4
2.4.1
2.4.2
2.4.3
2.9
2.6
2./
2.8
2.9

Vil

2-1
2-2

Beginning the Installation ...........0..
0.0...

Configuring the VMEbus Backplane

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

Configuring the VSB Backplane......................00..
Configuring the KAV30 ..........0
2... 0.0 ce eee ee eee
Jumper Posts .... 2... 0.0...
ee
eee eee
DIP Switches ..... 2... 0.00.
eee
Rotary Switch ..... 20... 0.2
ee
Inserting the KAV30 into a VMEbus Crate .................
Connecting Devices to the Serial Line Ports ................
Connecting Devices to the AUI Port.......................
Connecting Devices to the SCSI Port......................
Finishing the Installation ..........
0... 00... eee
ees

2-2
2-3
2-6
2-9
2-9
2-11
2-12
2-13
2-14

Testing the KAV30
3.1
3.2
3.2.1
3.3

Diagnostic Tests...
2...
Diagnostic Halt on Fatal Error
Differences between KAV30

Utilities

@¢©

@©

3-1

ee
eens
...................000008Revision Levels AandB
......
@

@®

@©

@®

#@#

@©

3-5
3-5

KAV30

Hardware

4.1
4.2
4.3

Overview of the KAV30 Hardware ..................0..2085
Status Display ..... 2... 0.0...
ee eee
Reset/Halt Switch .............
2.0... 0... eee eee ee ee ee

Operating the KAV30
5.1
5.1.1
5.1.2
5.1.3
5.2
5.3

5.4
5.5

Console Program ............
00 ccc eee eee eee nes
Running the Console Program ................0002000%
Console Program Commands ................20000008%
Console Program Messages ..............000
0c ee eeeee
Booting the KAV380............0..
0.00. cee
ee eee
Using Utilities ... 2...
ee ene

Testing the KAV30 Auxiliary Power Supply.................
Troubleshooting the SCSI Bus .....................0.4.5 -.

5-1
5—1
5-2
5-6
5-7
5-8

5-9
5-10

Replacing the KAV30 User ROM
6.1
6.2

Overview of the KAV30 User ROM
.....................0..
Removing the KAV30 from a VMEbus Crate ................

6-1
6-2

6.4

Programming the EPROMS

6-6

6.3

4—1
4-7
4-8

Replacing the EPROMS

..........
2.0... 00.0. ccc
ees
..............
0.0.0.0

6-4

KAV30 Hardware Specifications
A.1
A.2
A.3

A.4

Temperature and Humidity Specifications ..................
Power Supply Specifications. .............
002. .ee eee ee eee
Bus Load Specifications ........ 0.0... 0. cc
ee
ees

Timing Specifications ...........
0... ccc
eee eee nee

Diagnostic Tests

VAXELN Pascal Program

A-1
A-2
A-3

A-4

KAV30

Port Connectors

D.1
D.2
D.3

Console and Auxiliary Port Connectors .................04.
AUI Port Connector ..... 20.00.00... ce
eens
SCSI Port Connector ...... 2.0.0.0... 0. ccc
eee

D-1
D-3
D—4

Glossary
index

Figures

1-1
1-2
2-1
2-2
2-3
4-1
6-1
D-1
D-2

KAV380 Orientation...
KAV30

Parts

.. 20... 20.0... 0.

..... 0.0.0.0.

eee

1-6

eens

1-7

KAV30 Jumper Post Locations.................200008%

2-4

KAV30

2-7

DIP Switch Orientation

Inserting the KAV30

..................00055
..............

2-10

KAV30 Hardware Block Diagram......................

4-2

Replacing the KAV30

into a VMEbus
EPROMs

Crate

.....................2..

6-5

Serial Line Port Connector Layout.................000.

D-2

SCSI Port Connector Layout

..............
0.200 eee

D-—4

Kit Items...................200005-

1-4

KAV30 Module Options ...........
0.0... c eee eee eee
Additional KAV30 Hardware Installation Items...........
Settings for User ROM Size Jumper Posts...............

1-4
1-5
2-4

Settings for Auxiliary Power Source Jumpers

2-6

Tables

1-1
1-2
1-3
2-1
2-2
2-3
2-4
3-1
5-1
5-2
5-3
6-1
A-1
A-2

KAV30 Hardware

Settings for Boot Source Switches

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

................2000-

Default Console and Aumliary Port Settings

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

2-8
2-11

Diagnostic Test 3 Sub-Test Codes...................06.

3-3

Boot Source Device Names..............
00002 eee ee eee

5-2

KAV30 Utilities

.. 0... 2.2...

eee

5—8

Troubleshooting the SCSI Bus

.................2..005.

5-10

User ROM

Sizes...

Temperature

....

nee

6-2

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

eee

A-1

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

A-2

and Humidity Specifications

Maximum Power Supply Specifications

A-4
B—1
D-1

KAV30

Bus Load Specifications

System RAM
KAV30

.....

Access Timing-Specifications

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

e©

Serial Line Port Connector Pin Specification
AUI Port Connector Pin Specification

D-3

SCSI Port Connector Pin Specification

A-4

..............
©

#@®

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

B-1
D-—2
D—-3

Preface
This guide describes how to install and operate the KAV30

Who

Should

hardware.

Read This Guide

This guide is intended for anyone who wants to install or operate the KAV30.
However, to use this guide effectively, you must be familiar with the basic
backplane hardware concepts and the VMEbus environment.

Structure of This Guide
This guide is divided into six chapters, three appendixes, a glossary, and an
index:

Chapter 1 describes how to prepare to install the KAV30.
Chapter 2 describes how to install the KAV30.
Chapter 3 describes how to test the KAV30.
Chapter 4 describes the KAV30 hardware.
Chapter 5 describes how to operate the KAV30.
Chapter 6 describes how to replace the KAV30 user read-only
memory (ROM).
Appendix A gives the KAV30 hardware specifications.
Appendix B describes the KAV30

diagnostic tests.

Appendix C contains a sample VAXELN

error information.

Pascal program to read diagnostic

Appendix D describes the KAV30 port connectors.
The Glossary defines some of the important terms used in this guide.

vii

Associated

Documents

For more information, see the following documents:
KAV30 Hardware

Cover Letter (AV-PFSSB-TE)

KAV30 Hardware Release Notes (AV-PJRKA-TE)
KAV30 Software Cover Letter (AV-PEYFB-TE)
KAV30 Software Product Description (AE-PFB5B-TE)
KAV30 System Support Addendum

(AE-PFB6B-TE)

VAXELN KAV30 Programming Guide (AA-PRFBA-TE)

Documents

For additional information, see the following documents:
VMEbus

Specification, Revision C.1 (PRINTEX,

Phoenix, AZ, USA)

The VME Subsystem Bus (VSB) Specification, Revision B.1 (Motorola®,
Phoenix, AZ, USA)

Small Computer Systems Interface Developer’s Guide (Digital™,
EK-SCSIS-SP-001)
rtVAX 300 Hardware

User’s Guide (Digital, EK-382AA-UG)

VAXELN Utilities Guide (Digital, AA-PGXDA-TE)
VAXELN System Development Guide (Digital, AA-PGXCA-TE)

Conventions
The following conventions are used in this guide:
Convention

Description

Note

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

Caution

A caution contains information that the user needs to know

Warning

A warning contains information that is essential to people’s
safety.

Ctrl/x

viii

to avoid damaging the software or hardware.

Ctrl/x indicates that you hold down the Ctrl key while you

press another key (indicated here by x).

Convention

Description

Brackets enclose optional command

descriptions.

directory name in a VMS
italic type

arguments in command

Brackets are also used in the syntax of a
file specification.

Italic type emphasizes important information and indicates

the complete titles of manuals.

boldface type

Boldface type indicates the first occurrence of terms defined
either in text, in the glossary, or both.

Monospace

Monospace
input.

Type

n.nn
mnnan.nnn

type indicates both system

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

A space character separates groups of 3 digits in numerals

with 5 or more digits.
thousand.

UPPERCASE
<n..N>

displays and user

For example, 10 000 equals ten

Words in uppercase indicate software commands,

of a file, or hardware signal lines.

Three or more consecutive signal line numbers

in angle brackets.

the name

are enclosed

The first ine number is separated from

the last line number with two periods (..). For example,
signal lines </..4> represent signal lines /, 2, 3, and 4.

Preparing to Install the KAV30
This chapter describes how to prepare to install the KAV30.
information on the following:

1.1

Physical and environmental requirements (see Section 1.1)

Unpacking instructions (see Section 1.2)

KAV30

It gives

orientation (see Section 1.3)

Physical and Environmental Requirements
This section describes the physical and environmental requirements for
installing the KAV30. The KAV30 is a double-height! VMEbus module. To
satisfy physical and environmental requirements, follow these steps:
1.

Use a

crate that has the following characteristics:

The crate is a double-height crate.

The crate contains a double-height VMEbus

The crate is conductive.

The

crate is connected

backplane.

to earth.
Caution

If you do not house the KAV30 in a conductive crate connected to earth,
you risk the following:

VMEbus

—

Malfunction in the KAV30

—

Damage

to the KAV30

documents often use the term 6U to describe double-height modules.

Preparing to Install the KAV30

1-1

Preparing to Install the KAV30

The crate is product safety compliant with the local regulations such as
the UL1950, EN60950, and CSA950 standards that include the Safety
Extra Low Voltage (SELV) requirements.
Warning

If you do not house the KAV30 in a product safety compliant crate, you
risk personal injury, fire, or damage to equipment.

The power supply to the crate is product safety compliant with the local
regulations such as the UL1950, EN60950, and CSA950 standards that
include the SELV requirements.
Warning

If the power supply to the crate is not product safety compliant, you
risk personal injury, fire, or damage to equipment.

Use a VMEbus
¢

backplane that has the following characteristics:

The J1 and J2 backplane connectors must supply power to the modules
with which they mate.
Warning

If the J2 backplane connector on the VMEbus backplane does not

supply power to the modules, there is an overload of power on the J1
backplane connector. This power overload can cause personal injury,

fire, or damage to equipment.

The J2 backplane connector contains 64 user-defined pins. The KAV30
uses these pins to communicate with a VME subsystem bus (VSB)

backplane.

Connect only VSB devices to these pins.
Caution

If you connect non-VSB devices to the J2 backplane connector, you risk
damaging the VSB interface on the KAV30.

1-2

Preparing to Install the KAV30

Before you install the KAV30,

ensure that the VMEbus

system

configuration does not exceed the system’s limits for power supply and
bus loads.
Caution

If the VMEbus

system configuration exceeds the system’s limits for

power supply and bus loads, an equipment malfunction results.

To determine the VMEbus system’s limits for power supply and bus loads,
see the documentation for the system components. See Appendix A for the
KAV30 power supply and bus loads specifications.
Caution

Digital strongly recommends that you operate the module in creates or
environments with a forced cooling of at least 100 lfm. If you do not
follow this advice, the MTBF of your module may degrade significantly.

1.2

Unpacking Instructions
This section describes how to unpack the KAV30 hardware kit. To unpack the
KAV30 hardware kit, follow these steps:
1.

Look for external damage on the shipping container.
damage contact your Digital representative.

Do not dispose of the packing material until you successfully install the

KAV30. You might want to repack the KAV30 and return it to your Digital
representative. Keep the antistatic bag for storing or transporting the
KAV30.

If there is external

If you are a self-maintenance customer, keep the packing material.

To protect the KAV30 from ESD, wear an antistatic wrist strap while
handling the KAV30. Place the KAV30 on an antistatic mat.
Caution

If you do not wear an antistatic wrist strap while handling the KAV30,
or if you do not place the KAV30 on an antistatic mat, you risk
damaging the KAV30.

Unpack the KAV30 hardware kit.
Preparing to Install the KAV30

1-3

Preparing to Install the KAV30

Use the shipping list to verify that all the kit items are present.
items are missing, contact your Digital representative.
Table 1—1 lists the KAV30

Table 1-1

KAV30

If some

hardware kit items.

Hardware Kit Items

Item

Part Number

Shipping material

99-05016-01

Antistatic bag

99-07092-05

Antistatic bag seal

36-16159-00

KAV30

module

T6010-xx7

SCSI port ESD cover

2G-1908A-01¢

KAV30 Hardware Installation and User’s

AA-PFM6C-TE

KAV30 Hardware

Cover Letter

AV-PFSSB-TE

KAV30 Hardware Release Notes

AV-PJRKA-TE

VAXELN /KAV30 Run-time License Letter

AG-PG5BB-TE

Information

+A lowercase x denotes a character that depends on the version of the module.
information about versions of the KAV30 module.

See Table 1-2 for

tThe kit contains this item only if the KAV30 has a SCSI port.

There are four KAV30 module options. Table 1-2 lists the part number and
gives a brief description of each module.
Table 1-2

KAV30

Module Options

Module Option

Part Number

Description

KAV30-AA

T6010-AA

KAV30-AB

T6010-BA

Module with
system RAM

KAV30-AC

T6010-CA

Module with 4M bytes of system
RAM and a SCSI port

Module with 4M bytes of system

RAM

16M bytes of

(continued on next page)

1—4

Preparing to Install the KAV30

Table 1—2 (Cont.)

KAV30

Module Options

Module Option

Part Number

Description

KAV30-AD

T6010-DA

Module with 16M bytes of

system RAM

Inspect the KAV30 for shipping damage.
contact your Digital representative.

and a SCSI port

If there is shipping damage

Depending on how you want to use the KAV30, you might want one or more
hardware items that are not part of the KAV30 hardware kit. Table 1-3 lists
these items.
Table 1-3

Additional

KAV30

Hardware

Installation Items

Item

Supplier

Part Number

DEC™ 423 serial line cable

Digital

BC16E-xxtf

Ethernet cable

Digital

BNE4C-xxt

Ethernet loopback connector

Digital

12-22196-01

DELNI™

Ethernet transceiver

Digital

DELNI-xx7

DESTA™

Ethernet transceiver

Digital

DESTA-xxf

H4000 Ethernet transceiver

Digital

H4000-xxt

H4005 Ethernet transceiver

Digital

H4005-xxt

SCSI cable

Digital

BC56H-xxt

+A lowercase x denotes a variable character in a part number.

Variable characters in cable part

numbers depend on the length of the cable. Variable characters in other part numbers depend
either on the version of the item, or on the country in which you order the item.

1.3

KAV30

Orientation

This section describes the orientation of the KAV30.
height VMEbus

module.

side, and backplane connectors.

reference.

The KAV30 is a double-

Figure 1-1 shows the KAV30 front panel, component

This guide uses these terms as points of

Preparing to Install the KAV30

1-5

Preparing to Install the KAV30

Figure 1-1

KAV30 Orientation

Component Side

= 0

(ol)

caysoas

Front Panel

——————_]

P41
(Backplane
Connector)

x
RESET

Hoo
Pn
eraliai
/ i:

P2
(Backplane
Connector)

Sire

Cie
0

enzooen| |

Sites:
|| aceu

RE_EN05821A_90

1-6

Preparing to Install the KAV3O

Preparing to Install the KAV30

Figure 1-2 shows the component side of the KAV30 and its parts. This figure
also shows the location of the KAV30 revision information and serial number.
Figure 1-2

KAV30

Extractor

(T6010-XX.A01

KAV30-XX

Lever (2)

Parts

Status
Display
Console

T6010-XX.A01

Port ———~___
Auxiliary
Port
Reset/Halt
Switch

300

AUI
Port

System
RAM
Daughter
Card
Switches

rtVAX

Screw ing

DIP
So)

Grounding

KAV30-XX)

Odd
EPROM

SCSI
Port

Even
EPROM

rt\VAX 300
Daughter
Card
(MUXXXxx0x

30-35539XX.A01)
RE_ENOS822A_90A

Preparing to Install the KAV30

1-7

Installing the KAV30
This chapter describes how to install the KAV30.
following:

2.1

It gives information on the

Beginning the installation (see Section 2.1)

Configuring the VMEbus backplane (see Section 2.2)

Configuring the VSB backplane (see Section 2.3)

Configuring the KAV30

Inserting the KAV30

Connecting devices to the serial line ports (see Section 2.6)

Connecting devices to the attachment unit interface (AUI) port (see
Section 2.7)

Connecting devices to the small computer systems interface (SCSI) port
(see Section 2.8)

Finishing the installation (see Section 2.9)

(see Section 2.4)

into a VMEbus

crate (see Section 2.5)

Beginning the Installation
This section describes how to begin installing the KAV30.
the KAV30, follow these steps:
1.

To begin installing

To protect the KAV30 from ESD, wear an antistatic wrist strap while
handling the KAV30. Place the KAV30 on an antistatic mat.
Caution
If you do not wear an antistatic wrist strap while handling the KAV30,
or if you do not place the KAV30 on an antistatic mat, you risk
damaging the KAV30.

Installing the KAV30

2-1

Installing the KAV30

Back up all the software and data on the VMEbus

system.

Set the power switches on the SCSI devices connected to the VMEbus
system to the off position.

2.2

Set the power switches on the devices connected to the VMEbus
the off position.

Set the power switch on the VMEbus

Choose the backplane slot in which you want to insert the KAV30. If
you want the KAV30 to act as the system controller, choose the leftmost
backplane slot (slot 1).

Configuring the VMEbus

system to

crate to the off position.

Backplane

This section describes how to configure the VMEbus backplane. The VMEbus
backplane configuration depends on the configuration of the KAV30 you want
to install and on the backplane slot in which you want to install the KAV30.
See the VMEbus crate and backplane documentation for information on
configuring the VMEbus backplane.

2.3

Configuring the VSB

Backplane

This section describes how to configure the VSB backplane. If you want to use
the KAV30 with a VSB backplane and you do not have a VSB backplane in the
VMEbus crate, connect one now. See the VSB backplane documentation for
information on connecting the VSB backplane to the crate.

The VSB backplane configuration depends on the configuration of the KAV30

you want to install and on the backplane slot in which you want to install
the KAV30. See the VMEbus crate and VSB backplane documentation for
information on configuring the VSB backplane.

2.4

Configuring the KAV30
This section describes how to configure the KAV30.

You can use a combination

of jumpers, DIP switches, and a rotary switch to configure the KAV30. The
KAV30, as it is shipped, has the following default hardware configuration:

2-2

The user ROM

size is 256K bytes

The KAV30 responds to the VMEbus

The KAV30

Break key assertions on devices connected to the auxiliary port do not

signal

does not supply power to the SCSI bus TERMPWR

assert the VAX™ HALT signal

Installing the KAV30

RESET

signal

installing the KAV30

Ethernet devices can assert the VAX HALT

signal

There is no power source for the battery backed-up devices

The boot source is the Ethernet
The KAV30

allows Ethernet trigger boots

The KAV30 is not the VMEbus arbiter
Break key assertions on devices connected to the serial line ports assert

the VAX HALT signal
The VMEbus

AC_FAIL

signal asserts the VAX POWER_FAIL

The VMEbus

A24 base slave address is zero

signal

The rest of this section describes how to use the KAV30 jumper posts, DIP
switches, and the rotary switch to change the KAV30 hardware configuration.

2.4.1

Jumper

Posts

The KAV30 contains jumper posts that allow you to configure the KAV30
functionality.
Caution

Read this section carefully to ensure that you configure the KAV30
correctly. If you do not configure the KAV30 correctly, you risk causing
a malfunction in the module.

Figure 2-1 shows the location of the jumper posts.

posts to configure the following:
The user ROM

You can use the jumper

size

The KAV30 can have 128K bytes, 256K bytes, 512K bytes, or 1M byte
of user ROM. The KAV30 uses two erasable programmable read-only
memories (HPROMs) to implement the user ROM. The J1 and J3 jumper
posts determine the user ROM size (the jumper settings are the same for

user ROM

sizes of 128K bytes, 256K bytes, and 512K bytes). Table 2-1

describes how to configure these jumper posts.

Installing the KAV30

2-3

installing the KAV30

Table 2-1

Settings for User ROM

Size Jumper Posts

User ROM Size

J1 Jumper Posts

J3 Jumper Posts

128K bytes, 256K
bytes, or 512K
bytes

Jumper
posts

Jumper does not connect the posts

1M byte

Jumper connects the posts

Figure 2-1

does not connect the

KAV30 Jumper

Jumper connects the posts

Post Locations

[An
Front Panel

raeesecesscescescecascees O

EGEO
oOo

ee
teat

300

Ul 4

UE TS

Eig
at OE

—

(Backplane
Connector)

oOo

rtVAX

Sel TOT

OTF

_
J9

oso

co
oOo
KX
oO

°°

rt
ao

geoggu

;

LIL

:S yO

: AL

Connect
Backpl

RE_ENO5825A_90A

2—4

Installing the KAV30

The VMEbus RESET signal
The VMEbus RESET signal resets the entire VMEbus system. If you want
the KAV30 to drive the VMEbus RESET signal (that is, the signal is an
output from the KAV30), ensure that a jumper connects the J7 jumper
posts. If you want the KAV30 to respond to the VMEbus RESET signal
(that is, the signal is an input to the KAV30), ensure that a jumper does
not connect the J7 jumper posts. Note that the KAV30 can either drive
this signal or respond to it, but it cannot both drive and respond to it. The
KAV30 always drives this signal when you turn on the system.

The SCSI bus TERMPWR

signal

A SCSI bus must have at least one source of power for its TERMPWR
signal.

If you want the KAV30 to supply power to the TERMPWR signal, ensure
that a jumper connects the J5 jumper posts. If the KAV30 does not connect

to a SCSI bus, or if you do not want to supply power to the SCSI bus,
ensure that a jumper does not connect the J5 jumper posts.
Break key asserts the VAX HALT

signal

The VAX HALT signal halts the KAV30 CPU.
If you want to allow a break key assertion on a device connected to the

auxiliary port to assert the KAV30 VAX HALT signal, ensure that a jumper
connects the J6 jumper posts. If you do not want to allow a break key
assertion on a device connected to the auxiliary port to assert the KAV30
VAX HALT signal, ensure that a jumper does not connect the J6 jumper
posts.

Ethernet device asserts the VAX HALT signal
If you want to allow a device, which boots the KAV30 via the Ethernet (for
example, a remote trigger), to assert the VAX HALT signal on the KAV30,
ensure that a jumper connects the J8 jumper posts. If you do not want to
allow a device, which boots the KAV30 via the Ethernet, to assert the VAX
HALT signal on the KAV30, ensure that a jumper does not connect the J8
jumper posts.
Power source for the battery backed-up devices
The KAV30 has two battery backed-up devices: the battery backed-up
RAM and the calendar/clock. The power source for these battery backed-up

devices is called the auxiliary power source.
auxiliary power source as follows:

You can configure the

—

The KAV30 battery is the auxiliary power source

—

The VMEbus

standby power supply is the auxiliary power source
Installing the KAV30

2-5

Installing the KAV30

The J9 jumper posts determine the auxiliary power source. There are three
J9 jumper posts. Table 2—2 describes how to configure these jumper posts.
Table 2-2

Settings for Auxiliary Power Source Jumpers

Auxiliary Power
Source

Two

VMEbus standby
power supply

Jumper
posts

KAV30

Jumper connects the posts

battery

Posts Closest to J8
does not connect the

Two Posts Furthest from J8
Jumper connects the posts
Jumper does not connect the
posts

Caution

You must configure the KAV30

to provide standby power from the

on-board battery or from an external standby power supply to prevent
a malfunction of the KAV30.

Digital recommends that the auxiliary power source is always

connected to select the on-board battery when the KAV30 is installed in

your VME crate. In those cases where standby power is required and
you have connected the auxiliary power source to standby power, you
must supply the appropriate voltage to the standby power connection
at the backplane. If you do not adhere to these guidelines, there is a
possibility that the module will not operate correctly.
The module is shipped with the auxiliary power source jumperconnected to standby. You should change the jumper to the battery
position prior to installing the module in your VME crate.

The KAV30 also contains jumper posts that are reserved for Digital. These

jumper posts are J2, J4 and J40.

2.4.2

DIP Switches
A packet of eight DIP switches allows you to configure the KAV30.

You can put

each DIP switch in the on position or in the off position. Figure 2—2 shows a

KAV30 DIP switch orientation. In Figure 2-2 the arrow shows the view from
which the DIP switches are illustrated.

2-6

Installing the KAV30

installing the KAV30

Figure 2-2

KAV30 DIP Switch Orientation

DIP Switch
(Off Position)
DIP Switch
(On Position)

————

L.
— — DIP Switches

oo Ce _d

[UO
S SES
Co] C9: eee

f—1

_—eL_
eS SSS.

—

Rotary Switch

2 opooooa

2-92

Coo

~038

(Ct)
Or

eoEDO

;
cc

nim
002

<5 x

29?

z
oO

—————

9 BEDS
aD

(

RE_EN06018A_90

Installing the KAV30

2-7

Installing the KAV30

You can use the DIP switches to configure the following:
The boot source

Switches 1 to 3 set the default KAV30 boot source.
KAV30 boot source settings for these switches.
Table 2-3

Table 2—3 lists the

Settings for Boot Source Switches

Switch 1

Switch 2

Switch 3

Boot Source

Off

Ethernet (EZAO)

Off

Device connected to the auxiliary port that
operates at 9600 bits per second (bits/s)

(CSB2)t
Off

Off

Device connected to the auxiliary port that
operates at 2400 bits/s (CSB1)f

Off

Device connected to the auxiliary port that
operates at 1200 bits/s (CSBO)t+

Off

SCSI device or application program in the
KAV30 user ROM (PRB1)i

Off

User ROM (PRBO)

Off

Undefined

No boot

+The KAV30

performs a DECnet™

DDCMP™

boot.

+The KAV30 first copies the contents of the user ROM to the system RAM.

Whether or not to allow Ethernet trigger boots
If you want to allow a node on the Ethernet to perform a remote KAV30
trigger boot, move switch 4 to the on position. If you do not want to allow a

node on the Ethernet to perform a remote trigger, move switch 4 to the off
position.

The VMEbus

arbiter

If you want the KAV30 to act as the VMEbus arbiter, move switch 5 to the

on position. If you do not want the KAV30
move switch 5 to the off position.

2-8

Installing the KAV30

to act as the VMEbus

arbiter,

Installing the KAV30

Break key asserts the VAX HALT

signal

If you want a break key assertion on a device, which is connected to the
console port, to assert the KAV30 VAX HALT signal, move switch 6 to the
off position. If you do not want a break key assertion on a device, which is
connected to the console port, to assert the KAV30 VAX HALT signal, move
switch 6 to the on position.
¢

The VMEbus

AC_FAIL

signal

If you want the VMEbus AC_FAIL signal to assert the VAX POWER_FAIL
signal on the KAV30, move switch 8 to the off position. If you do not want
the VMEbus AC_FAIL signal to assert the VAX POWER_FAIL signal on
the KAV30, move switch 8 to the on position.
e

Whether

or not to boot after a fatal error

Starting with EPROM revision A02, DIP switch 7 is defined as Attempt
Boot on Fatal Error. All modules are shipped with this switch in the off
position. The actions Halt on Fatal Error and Attempt Boot on Fatal Error
are described in detail in Section 3.2. To identify the EPROM version and
revision of your module, see the KAV30 Hardware Release Notes, order

number AV-PJRKA-TE. The KAV30 Hardware Release Notes are shipped

with every module.

Note

The implementation of the action Attempt Boot on Fatal Error differs

from module revision levels A to B and higher.

2.4.3

Rotary Switch
Use the rotary switch to set the VMEbus

A24 base slave address.

To set the

address, use a screw driver to turn the inner wheel of the rotary switch until

the arrow points to the value you want.
must be unique to the VMEbus system.

2.5

The A24 base slave address you choose

Inserting the KAV30 into a VMEbus

Crate

This section describes how to insert the KAV30 into a VMEbus crate.
Figure 2—3 shows how to insert the KAV30 into a VMEbus crate. To insert the
KAV30 into a VMEbus crate, follow these steps:
1.

Insert the KAV30 into the appropriate backplane slot. While holding the
top and bottom extractor levers, lock the KAV30 in place by simultaneously

Installing the KAV30

2-9

Installing the KAV30

pushing down the top lever, pulling up the bottom lever, and pushing the
KAV30 into the backplane slot (see Figure 2—3 for more information).

Inserting the KAV30 into a VMEbus Crate

VMEbus Crate

\AAAAAAAAAAYAS NS
\AAAAAAAAAAANR
\AAAAAAAAAANAN
QSQXAAAAAAAAAN

\AAAAANAAAANHL

\\ I

QAQAAAAAAAAN
QAAAAAAAAAANL
QQAAAAAAAAAAN

Figure 2-3

RE_ENO5820A_90

Tighten the two front-panel screws that secure the KAV30 in the VMEbus
crate.

Caution
If you do not tighten the two front panel screws, you cannot ensure
that the KAV30 forms an electrical path with the crate.

2-10

Installing the KAV30

2.6

Connecting

Devices to the Serial Line Ports

This section describes how to connect devices to the KAV30 serial line ports.
The devices that you connect to the KAV30 serial line ports must be product
safety compliant with the local regulations, such as the UL1950, EN60950,
CSA950 standards which include the SELV requirements.
Warning
If you connect devices that are not product safety compliant to the
KAV30, you risk personal injury, fire, or damage to equipment.

You can connect DEC 423 compliant devices to the KAV30 serial line ports. For
example, you can connect printers, terminals, modems, and computers to the

serial line port.

To connect serial line devices to the KAV30, use a shielded DECconnect™

cable with modified modular plug (MMP) connectors.

office

Connect the ground cable

on the DECconnect office cable to the front panel grounding screw and tighten
the grounding screw.
Note

If you do not tighten the grounding screw, you lose essential mechanical
support for the KAV30.

The devices that you connect to the console port have KAV30
functionality.

console

Table 2—4 describes the default serial line port settings.

Table 2-4

Default Console and Auxiliary Port Settings

Setting

Value

Baud rate

9600

Number

of data bits

Number of parity bits

Number of stop bits

To connect serial line devices to the KAV30, plug one end of the cable into the
relevant port and the other end into the device that you want to connect.

Installing the KAV30

2-11

Installing the KAV30

2.7

Connecting Devices to the AUI Port
This section describes how to connect devices to the KAV30 AUI port. Connect

devices to the AUI port only when the power switch on the VMEbus
the off position.

crate is in

Caution

If you connect devices to the AUI port when the power switch on the
VMEbus crate is in the on position, you risk the following:

Malfunction in the KAV30 and devices connected to the KAV30

Damage to the KAV30 and devices connected to the KAV30

Connecting an Ethernet Network:

or standard Ethernet networks.

You can connect the KAV30 to ThinWire™

To connect to a ThinWire Ethernet network,

you must have a DESTA transceiver.
network, you must have a DELNI,

To connect to a standard Ethernet

H4000, or H4005 transceiver.

To connect an Ethernet network to the AUI port, use a straight-version
Ethernet transceiver cable. Use a straight-version cable because an angled-

version cable blocks the KAV30

SCSI port.

To connect a ThinWire Ethernet network to the AUI port, follow these steps:
1.

Connect the DESTA transceiver to the ThinWire Ethernet network.

Connect the cable’s male connector to the AUI port.

Connect the cable’s female connector to a DESTA transceiver.

To connect a standard Ethernet network to the AUI port, follow these steps:

2-12

Connect a DELNI,
network.

Connect the cable’s male connector to the AUI port.

Connect the cable’s female connector to the transceiver.

Installing the KAV30

H4000, or H4005 transceiver to the standard Etherne

Installing the KAV30

Connecting an Ethernet Loopback Connector:
If you do not connect an
Ethernet network to the AUI port, you must protect the AUI port from ESD.
To protect the AUI port from ESD, connect an Ethernet loopback connector to
the port.
Caution

If you do not protect the AUI port from ESD, you risk damaging the

KAV30.

2.8 Connecting Devices to the SCSI Port
This section describes how to connect devices to the KAV30 SCSI port. The
devices that you connect to the KAV30 SCSI port must be product safety
compliant with the local regulations such as the UL1950, EN60950, and
CSA950 standards that include the SELV requirements.
Warning
If you do not connect product safety compliant devices to the KAV30,
you risk personal injury, fire, or damage to equipment.

Connect devices to the SCSI port only when the power switch on the VMEbus
crate is in the off position.
Caution

If you connect devices to the SCSI port when the power switch on the
VMEbus crate is in the on position, you risk the following:
e

Malfunction in the KAV30 and devices connected to the KAV30

Damage to the KAV30

and devices connected to the KAV30

Installing the KAV30

2-13

Installing the KAV30

Setting the KAV30 SCSI ID: Before you connect the KAV30 to an external
SCSI bus, set the KAV30 SCSI ID. Choose a SCSI ID that is unique to the

SCSI bus.

The KAV30 stores the SCSI ID in its battery backed-up RAM. The default
SCSI ID is seven. You can use the KAV30 utility that begins at $2008’0050 to
change the SCSI ID. However, when the battery backed-up RAM loses power,
the SCSI ID is reset to seven. See Section 5.3 for information about the KAV30

utilities.

Connecting a SCSI Bus:

To connect a SCSI bus to the SCSI port, use a

Digital SCSI cable with a 68-pin female Honda connector at one end. Use the
68-pin Honda connector to connect to the SCSI port. See the Small Computer
Systems Interface Developer’s Guide for more information on connecting a SCSI

bus to the KAV30.

See Section D.3 for a description of the SCSI port.

Protecting the SCSI Port from ESD: If you do not connect a SCSI bus to the
SCSI port, you must protect the SCSI port from ESD. To protect the SCSI port

from ESD, fit the SCSI port ESD

cover on the port.
Caution

If you do not protect the SCSI port from ESD, you risk damaging the

KAV30.

2.9

Finishing the Installation
This section describes how to finish installing the KAV30.
the KAV30, follow these steps:

To finish installing

Insert conductive blank panels in the vacant backplane slots.
This ensures that the VMEbus system meets the airflow requirements.

Set the power switches on the SCSI devices connected to the VMEbus
system to the on position.

Set the power switches on the devices connected to the VMEbus
the on position.

Set the power switch on the VMEbus crate to the on position.
Monitor the KAV30

2-14

Installing the KAV30

diagnostic display.

system to

Installing the KAV30

When

you supply power to the KAV30,

the KAV30

executes its self-

test. Executing the KAV30 self-test consists of executing all the KAV30

diagnostic tests. The self-test takes approximately 30 seconds to complete
if the KAV30 has 4M bytes of system RAM, and approximately 2.5 minutes
to complete if the KAV30 has 16M bytes of system RAM.

The KAV30 sends diagnostic test status information to the KAV30 front

panel display and to the devices connected to the KAV30 console port.
If the KAV30 passes all of the diagnostic tests, it displays 0 on its high
status display and 5 on its low status display. See Section 3.1 for more
information.
:

You can now use the VAXELN™ KAV Toolkit Extensions for VMS™ to
configure the KAV30. See the KAV30 Programmer’s Reference Information
manual for more information.
Before you use a system containing the KAV30, you might have to satisfy the
local regulations for such systems. Examples of actions that you must perform

to satisfy the local regulations include the following:

Obtain an electromagnetic interference (EMI) operation license for the
system.
Obtain a Postal, Telephone, and Telegraph (PTT) administration operation
license, if you connect the system to public telephone networks.
Supply appropriate instructions to the end user of the system. Instructions
must include product safety information in the end user’s local language.

Installing the KAV30

2-15

Testing the KAV30
This chapter describes how to test the KAV30.
following:

It gives information on the

Diagnostic tests (see Section 3.1)
Diagnostic Halt on Fatal Error (see Section 3.2)
Utilities (see Section 3.3)

3.1

Diagnostic Tests
This section describes the KAV30 diagnostic tests. The KAV30 includes a

number of diagnostic tests that allow you to test the KAV30 hardware.
Appendix B for more information about the KAV30 diagnostic tests.

See

You can use any of the following methods to run the diagnostic tests:

Supply power to the KAV30
When you supply power to the KAV30, the KAV30 executes its self-

test. Executing the KAV30 self-test consists of executing all the KAV30
diagnostic tests. The self-test takes approximately 30 seconds to complete
if the KAV30 has 4M bytes of system RAM, and approximately 2.5 minutes
to complete if the KAV30 has 16M bytes of system RAM.
Reset the KAV30

When you reset the KAV30, the KAV30

executes its self-test.

Use the TEST console command
You can use the TEST console command to execute a single diagnostic test.
See Section 5.1.2 for more information about the TEST console command.
While the KAV30 executes a diagnostic test, it shows the relevant test number
on the high status display and the relevant error number on the low status
display. If the KAV30 finishes the self-test successfully, it displays a 0 on its
high status display and a 5 on its low status display.

Testing the KAV30

3-1

Testing the KAV30

The KAV30 also sends status information to the device that is connected

to the console port. The KAV30 diagnostic display is similar to the rest of
Digital’s VAX™ product line. The KAV30 displays the test number, a character
indicating the status of the test, and two periods (..). The following characters

indicate the status of the test:
e

A period (.) indicates a test that is successful

A question mark (?) indicates a test that fails

An underscore (_) indicates a test that is disabled or that the item being
tested 1s missing
Note

If a terminal is connected to the console port and the hold screen
command is active on the terminal, then the self-test stops at diagnostic
test number C. The self-test will not continue until you deactivate the
hold screen command.

A typical KAV30

console diagnostic display for the self-test is as follows:

E...D...C...B...A...9...8...7...6...5...4...3...2...1...

The following table describes error messages that the KAV30 might display,
and the actions that you must take if the KAV30

Message
D_

displays the messages.

Reason for
Message

User Action

Diagnostic test
D is disabled.

On initial power up (no battery connected or
discharged during power down), the state of

the memory

flag (long or short memory

unpredictable.

test) 1s

If you want to force short or extended

memory test, you have to invoke the utility.

See

Section 5.3 and Appendix B for more information on
disabling this diagnostic test.

The auxiliary
power supplyis

dead.

the VMEbus standby power supply, see the VMEbt.

The KAV30 does _
not contain a

If the KAV30 does not contain a SCSI controller, do
not take any action. If the KAV30 contains a SCSI

SCSI controller.

3-2

Testing the KAV30

If you use the KAV30 battery as the source of the
auxiliary power supply, see Table 3-1. If you use

system documentation. If you do not use either power
supply, do not take any action.

controller, contact your Digital representative.

Testing the KAV30

The on-board self-test 3 tests the realtime clock chip and the on-board battery.

The KAV30 may report problems when running this test. Table 3-1 contains
information about the problems that may be detected by this test. The sub-test
code is displayed on the lower front panel LED of the KAV30. The sub-test
code is not included in the console printout.

Table 3-1

Diagnostic Test 3 Sub-Test Codes

Sub-

Test

Code

Meaning

User Action

Oscillator failed. RTC calendar clock and batterybacked-up area may be invalid.

Informational message
only. No user action.

Battery is not connected, or battery is dead.

If the battery is connected,
recharge the KAV30 for 30
minutes. If the problem
persists contact your

Digital representative.

Clock running too fast, or too slow, or not
clocking.

Contact your Digital
representative.

When you turn on the KAV30 in the VMEbus crate, the self-test fails,
displaying a 3 on its high status display and an 8 on its low status display, in
the following circumstances:
e

When the J9 jumper posts are positioned so that the KAV30
disconnected.

battery is

When the KAV30 battery is not charged.

If this is the first execution of the self-test since the J9 jumper posts were
set to use the KAV30 battery as the auxiliary power source. In this case,
turn off the VMEbus crate and then turn it on again to complete the

self-test.

Note

To prolong battery life, the KAV30
disconnected.

is shipped with the battery

If errors other than those listed in this section occur, contact your Digital
representative.

Testing the KAV30

3-3

Testing the KAV30

3.2

Diagnostic Halt on Fatal Error
The current EPROM revision (see the Hardware Release Notes, AV-PJRKA-TE)
allows the user to select whether the KAV30 halts after detecting a fatal error
or continues to boot, if a boot source is selected, regardless of any fatal error.
The diagnostic self-tests always run to completion (test ..1) before they halt
or continue. You select the Halt on Fatal Error action using DIP switch 7.
If DIP switch 7 is set to the off position, which is the factory default setting,
the following occurs:
All the on-board self-tests run before the KAV30 halts. If a console
terminal is connected to the KAV30 it indicates that the self-test halted at
test 1.

The KAV30 LEDs display the code for the first failing test.
If a console terminal is connected to the KAV30, then a question mark
(2?) appears after each failing test. A dead or non-connected battery is
displayed as an underscore character (_), which indicates that a device is
missing. The diagnostics treat this as a fatal error and halt on test 1.
When the on-board diagnostics detect a failing test they record details of
the failing test in the battery-backed up RAM. The sample VAXELN Pascal
program in Appendix C demonstrates how to retrieve information

concerning the failing tests from the battery-backed up RAM.

If DIP switch 7 is set to the on position, the following occurs:
The KAV30 runs through all on-board self-tests before attempting to boot,

if a boot device is selected.

If a console terminal is connected to the KAV30,

then a question mark

(?) appears after each failing test. A dead or non-connected battery is

displayed as an underscore character (_), which indicates that a device is
missing.
When the on-board diagnostics detect a failing test they record details of
the failing test in the battery-backed up RAM. The sample VAXELN Pascal
program in Appendix C demonstrates how to retrieve information
concerning the failing tests from the battery-backed up RAM.
Note

Any error reported by the diagnostics should be viewed as a failure of
the KAV30. If the diagnostics detect errors and you continue to operate

the KAV30, unpredictable application behavior may result.

3—4

Testing the KAV30

3.2.1

Differences

between

KAV30

Revision

Levels A and

You can only use DIP switch 7 to select the Halt on Fatal Error action in

KAV30 modules of the revision level A. This is due to firmware changes in

the rtVAX300, which is incorporated in all KAV30 modules of revision level B
and higher. KAV30 modules of revision level B and higher have the following
functionality with DIP switch 7:
e

If DIP switch 7 is in the off position, the functionality is as described in
Section 3.2.

If DIP switch 7 is in the on position, the KAV30 halts at the console
prompt, after completing the self-test, whenever a fatal error occurs. In
other words, there is no automatic boot possible after a fatal error.

Ifa console terminal is connected to the KAV30 a question mark (?) is
displayed after each failing test. A dead or non-connected battery is

displayed as an underscore character (_), which indicates that a device is

missing.

3.3

The KAV30

treats this as a nonfatal error and continues to boot.

Utilities
This section describes the KAV30

utilities.

The user ROM

on the KAV30

you receive contains eight utilities. You can use the utilities to perform a

that

variety of functions, including testing and debugging the KAV30. The utilities
allow you to test, without using the KAV30 software, how the KAV30 interacts
with the other VMEbus modules. They also allow you to configure the VMEbus
and VSB.
Before you use the utilities, you must understand all aspects of the following:

The VMEbus

The KAV30

The devices with which the KAV30 communicates

See Section 5.3 for more information about the KAV30 utilities.

Testing the KAV30

3-5

4
KAV30
This chapter describes the KAV30

following:

hardware.

Hardware

It gives information on the

Overview of the KAV30 hardware (see Section 4.1)
Status display (see Section 4.2)
Reset/halt switch (see Section 4.3)

4.1

Overview of the KAV30

Hardware

This section gives an overview of the KAV30
block diagram of the KAV30 hardware.

hardware.

Figure 4-1 shows a

The KAV30 contains the following hardware:
Battery
The battery can back up the battery backed-up RAM and the calendar
/clock. See Section 2.4 for information on configuring the KAV30 to allow
the battery to back up the battery backed-up RAM and the calendar/clock.
Battery backed-up RAM
There are 32K bytes of battery backed-up RAM. You can configure the
KAV30 so that either the battery or the VMEbus standby power supply
backs up the RAM. You can also configure the KAV30 so that the RAM has
no backup power.
Byte-swap logic circuitry
The byte-swap logic circuitry allows the KAV30 (little-endian architecture)
to exchange data with modules containing 68000® processors (big-endian
architecture).

KAV30

Hardware

4—1

KAV30

Hardware

Figure 4—1

KAV30

Hardware

Block Diagram

Batte

SCSI
atte, Backed_Up| | Counter’ | |Serial Line
Controller | |BUfers} | Ran
Timers
Ports
A

Ethernet

Status
Displa

~vaxsoo YY
DIP

Switches

Reset/

User

System

ROM

RAM

SGM

Sach

WITC

Arbiter || Arbiter | +} Slave

Reece cnene

yyy

SGM

Logic

VMEbus||

VSB

Vv
CSR Bits

Cpr

‘|

VMEbus

»|

Interrupt

Interrupt | !

|: :{Requester! | Handler | !

;<<—+—3») Master || Master |; :

SSB

«eal
vi
Interf
nterface Functionality
Functionality
---------2 : 3

Interrupt
Handler

leneece

bane een ee nee nb een nnn enn
Vv
Outgoing
;

VMEbus || VSB | !|VMEbus

Timer

patent denen ene
;
+ | Incoming

Watchdog

Clock

Calendar/

Interrupt _.......2

Functionality

Calendar/clock
The calendar/clock keeps absolute time to a resolution of 10 milliseconds

(ms). It can format this time into 12- or 24-hour mode, with the following
counting functionality:

Day of week counting
Day of year counting
Automatic leap year counting

4-2

KAV30

Hardware

KAV30

Hardware

You can configure the KAV30 so that either the battery or the VMEbus
standby power supply backs up the calendar/clock.
Control and status register (CSR) bits
The CSR bits consist of input bits and output bits.

The CSR input bits

report on the status of the KAV30 hardware, while the CSR output bits
control the KAV30

hardware.

Counter/timers

There are fifteen 16-bit counter/timers.

You can cascade two counter/timers

to form one virtual 32-bit counter/timer. See the KAV30 Programmer’s
Reference Information manual for more information.
First-in/first-out (FIFO) buffers

The KAV30 uses hardware to implement four independently-operating

FIFO buffers. You can access the FIFO buffers either in FIFO mode or in
last-in/first-out (LIFO) mode.
Each FIFO buffer has 255 32-bit entries. However, you can perform byte,
word, longword, quadword, and octaword operations on these buffers.
See the KAV30 Programmer’s Reference Information manual for more

information about the FIFO buffers.
Front panel

The KAV30 has a conductive aluminum grounded front-panel.
side of the front panel is anodized.

chromatized.

The front

The reverse side of the front panel is

Hardware revision registers
The hardware

KAV30.

revision registers indicate the hardware revision of the

Incoming scatter-gather map (SGM) logic circuitry
The incoming SGM allows other devices on the VMEbus to access the
KAV30 system RAM, FIFO buffers, and VMEbus reset register. The KAV30

incoming SGM consists of 256 64K-byte pages.

Each incoming SGM entry offers page write-protect functionality. Also, you
can set each incoming SGM page to interrupt the CPU when it receives a
read or write access.
Outgoing SGM

logic circuitry

The outgoing SGM

allows the KAV30

VMEbus or VSB. The outgoing SGM

VMEbus

or VSB

address space.

to access other devices on the

consists of 3584 64K-byte pages of

KAV30

Hardware

4-3

KAV30

Hardware

Each outgoing SGM entry offers VMEbus address modifier, VSB
space, and page write-protect functionality.
e

address

rtVAX'™ 300 processor
The rtVAX 300 processor is a 3-inch by 5-inch daughter card.

the following:
—

A CVAX™

—

A floating-point unit (FPU) coprocessor

—

A second-generation Ethernet controller (SGEC)

—

An interval timer

ROM

—

Control logic circuitry

It includes

microprocessor

The CVAX microprocessor implements a central processing unit (CPU),
which allows the KAV30 to run VAXELN applications. The CVAX
microprocessor can store accesses in a 1 kilobyte, two-way associative,
write-through memory cache. The KAV30 hardware maintains cache
coherency for VMEbus, VSB, SCSI, and SGEC bus cycles.
The KAV30 uses the FPU, the CVAX microprocessor, and the VAXELN
emulated instruction trap handlers to execute VAX floating-point
instructions.
The SGEC allows the KAV30 to communicate with Ethernet networks.
The SGEC can perform direct memory access (DMA) operations with the
the KAV30 system RAM. However, the SGEC cannot move data from one
system memory to another.
The VAXELN kernel uses the interval timer to maintain the current time.
The interval timer interrupts the CVAX microprocessor every 10 ms.

The rtVAX 300 ROM

contains firmware and diagnostic code. The rtVAX

300 firmware emulates a typical VAX console.

code performs two functions:
—

It tests the rtVAX 300 hardware.

—

It checks the KAV30
KAV30 hardware.

user ROM

The rtVAX 300 diagnostic

for diagnostic code to test the remaining

The rtVAX 300 is the source of the data and address lines (DAL) bus, a 32bit multiplexed bus. See the rt{VAX 300 User’s Guide for more information
about the rtVAX 300 processor.

4—4

KAV30

Hardware

KAV30

Hardware

SCSI controller
The SCSI controller is optional. The KAV30 contains a SCSI controller only
if you order a KAV30 that has one. You cannot install the SCSI controller
as an upgrade.
The SCSI controller can perform synchronous transfers at a rate of
2.5 megabytes per second and asynchronous transfers at a rate of 1.5
megabytes per second.
The SCSI controller can perform DMA operations with the KAV30 system
RAM. However, the SGEC cannot move data from one system memory to
another.
The SCSI controller contains an embedded Reduced Instruction Set
Computer (RISC) processor. This RISC processor allows the SCSI

controller to process lists of instructions, called scripts.
Status display

The status display shows the diagnostic and operation status information.

See Section 4.2 for more information about the status display.
System RAM

Depending on the KAV30 that you order, it has either 4M bytes or 16M
bytes of system RAM. The KAV30 uses a 4M byte dynamic random-access
memory (DRAM) daughter card to implement 4M bytes of system RAM.

The KAV30 uses a 16M byte DRAM
of system RAM.

daughter card to implement 16M bytes
:

The KAV30 system RAM is parity-protected, with one parity bit for each
byte of system RAM. The 4M byte DRAM daughter card consists of
thirty-six 1-megabit chips. The 16M byte DRAM daughter card consists of
thirty-six 4-megabit chips. The system RAM uses 32 chips to store data
bits and four chips to store parity bits.
The CVAX microprocessor, SGEC, SCSI controller, and VMEbus slave data
interface logic circuitry can read from and write to the system RAM.
Serial line ports

The KAV30 has two DEC 423 comphant serial line ports: the console

port and the auxiliary port. It uses a universal asynchronous receiver
/transmitter (UART) to implement these ports. The default baud rate is
9600 baud. You can program the ports to have baud rates between 75 and
19 200 baud. However, when you supply power to the KAV30, the baud
rate is reset to 9600.

KAV30

Hardware

4—5

KAV30

Hardware

e¢

User ROM
The KAV30 can have 128K bytes, 256K bytes, 512K bytes, or 1M byte of
user ROM. The KAV30 uses two 16-bit EPROMs connected to 40-pin Joint
Electron Device Engineering Council (JEDEC) sockets to implement the

user ROM. You can upgrade or replace the user ROM. The user ROM you
receive contains KAV30 firmware.

You can program the user ROM with application programs. However, if
you do, you must overwrite the SCSI boot user application program with
the application programs. See Chapter 6 for more information.
e¢

VMEbus

arbiter functionality

The KAV30 includes logic circuitry that implements VMEbus arbiter
functionality. Use a DIP switch to enable the KAV30 VMEbus arbiter
functionality. However, if you want the KAV30 to act as the VMEbus
arbiter, you must place it in the leftmost backplane slot (slot 1) of the
VMEbus system.
The VMEbus arbiter can provide prioritized, round-robin, or single-level
bus arbitration.
¢

VMEbus

interrupt handler logic circuitry

The KAV30 includes logic circuitry that can handle vectored and
autovectored interrupt requests (IRQs) that it receives from the VMEbus.

It can handle vectored interrupt requests on the VMEbus IRQ<6..1> lines.
It can handle autovectored interrupt requests on the VMEbus

and POWER_FAIL lines.
¢

VMEbus

IRQ<’7..1>

interrupt requester logic circuitry

The KAV30 includes logic circuitry that can generate vectored VMEbus
IRQs. It can request interrupts on the VMEbus IRQ<7..1> lines.
¢

VMEbus

master data interface logic circuitry

The KAV30 includes VMEbus
supports the following:

e¢

—-

Ai6, A24, and A382 addressing modes

—-

)D08, D16, and D32 data transfers

—

Read-modify-write cycles

VMEbus

slave data interface logic circuitry

The KAV30

includes VMEbus

the following:

4-6

KAV30

master data interface logic circuitry that

Hardware

slave interface logic circuitry that supports

KAV30

—

VMEbus A24 and A32 addressing modes

—-

)D08, D16, D32, and block mode data transfers

—

Read-modify-write cycles

The VMEbus slave data interface can access the KAV30
FIFO buffers, and the VMEbus reset register.
e

VSB

Hardware

system RAM,

arbiter functionality

The KAV30 includes logic circuitry that implements VSB arbiter
functionality. Use the VAXELN KAV Toolkit Extensions for VMS to
enable the KAV30 VSB arbiter functionality. However, if you want the
KAV30 to act as the VSB arbiter, you must place it in the leftmost
backplane slot (slot 0) of the VSB system.
¢

VSB interrupt handler logic circuitry
The KAV30 includes logic circuitry that can handle autovectored IRQs that
it receives on its VSB IRQ line.

VSB master data interface logic circuitry
The KAV30

includes VSB

VSB ALTERNATE,
e

master interface logic circuitry that supports

SYSTEM, and I/O address spaces.

Watchdog timer
The KAV30 has a watchdog timer. If you enable the watchdog timer, it
asserts the RESET signal when the KAV30 application enters an infinite
loop. Application programs must periodically refresh the watchdog timer,
otherwise the watchdog timer asserts the RESET signal. Use the VAXELN
KAV Toolkit Extensions for VMS to enable, disable, or refresh the watchdog
timer.

4.2

Status Display
This section describes the KAV30 status display. While the KAV30 is receiving
power, it shows the diagnostic and operation status information on its status
display. This status display shows a high-order digit above a low-order digit,
with a decimal point on either side of each digit.

The KAV30 uses the digits on the status display to display its diagnostic status
information. See Section 2.9 for more information on the KAV30 diagnostic
status information.

KAV30

Hardware

4~-7

KAV30

Hardware

The KAV30 uses the decimal points on the status display to indicate its
operation status information. There are two decimal points on each display:
one to the left of the digit and one to the right of the digit. The KAV30 hghts
the decimal points as follows:
e

The KAV30 lights the decimal point to the left of the digit, on the low
status display, if it is configured to act as the VMEbus arbiter.

The KAV30 lights the decimal point to the nght of the digit, on the low

The KAV30 lights the decimal point to the left of the digit, on the high
status display, if it connects to a SCSI bus on which there is a power supply
to the TERMPWR signal. You can use the status of this decimal point to

status display, if it is configured to act as the VSB arbiter.

troubleshoot the SCSI bus. See Section 5.5 for more information.
e

4.3

The KAV30 lights the decimal point to the right of the digit, on the high

status display, if there is a VMEbus slave access to the KAV30. Because
this pulse is not sufficient in length to allow the human eye to see the
display, the KAV30 extends the pulse length to 0.5 seconds.

Reset/Halt Switch
This section describes the KAV30 reset/halt switch. The reset/halt switch is on
the KAV30 front panel. You can use this switch to reset the KAV30, or halt the

KAV30 CPU.

This switch remains in the center, unless you move it. While the switch is in
the center, the KAV30 operates normally. However, you can move the switch to

either of the following settings:
e

Reset
If you move the switch to this setting you reset the KAV30,
executes its diagnostic tests.

Halt
If you move the switch to this setting you halt the CPU,
starts its console program.

There is momentary

contact between these switch settings.

returns to the center when you release your finger.

4-8

KAV30

and the KAV30

Hardware

and the KAV30
That is, the switch

Operating the KAV30
This chapter describes how to operate the KAV30.
following:

5.1

Console program (see Section 5.1)

Booting the KAV30

Using utilities (see Section 5.3)

Testing the KAV30

Troubleshooting the SCSI bus (see Section 5.5)

It gives information on the

(see Section 5.2)

auxiliary power supply (see Section 5.4)

Console Program
This section describes the KAV30

console program.

You can enter commands

that control the operation of the KAV30 CPU via the console program.

The

console program runs on a terminal that is connected to the KAV30 console
port. It is similar to the console programs supported by the rest of Digital’s
VAX product line. See Section 2.6 for more information on how to connect a
terminal to the KAV30 console port.

5.1.1

Running the Console Program
To run the console program, set the KAV30 reset/halt switch to the halt
position. When you run the console program, it displays the console prompt
(>>>) on the terminal connected to the KAV30 console port. Enter console
commands at the console prompt.
The KAV30
occurs:

also runs the console program when one of the following conditions

A program executing on the KAV30 CPU executes a HALT instruction.

A KAV30

A program executing on the KAV30 CPU encounters a severe error.

restart or boot operation fails, and the default recovery action is

to halt the CPU.

Operating the KAV30

5-1

Operating the KAV30

5.1.2

Console Program Commands
This section describes the console program

commands.

the same as the rtVAX 300 console program commands.

Hardware
follows:

B[OOT]

User’s Guide for more information.
[/<DATUM>]

The commands

are

See the rtVAX 300

The console commands

are as

[<device-name>[:] ]

This command loads and starts an application program on the KAV30.
The <DATUM> qualifier is optional. It specifies a hexadecimal value
representing the boot flags. The console program passes the <DATUM>
information as a longword to the bootstrap program. If, for example, the
<DATUM> qualifier has a value of 4, the VAXELN kernel debugger, if it is
present on the VAXELN system, is invoked with the application program.
The <device-name> parameter is optional. This parameter specifies the
name of the device containing the application program. Table 5—1 describes
the device names that you can use. You can type a colon (:) at the end of
the device name, but it is not required.
Table 5—1

Boot Source Device Names

Device
Name

Boot Source

EZAO

Ethernet

CSBO

Device} connected to the auxiliary port that operates at 1200 bits/s

CSB1

Device? connected to the auxiliary port that operates at 2400 bits/s

CSB2

Device+ connected to the auxiliary port that operates at 9600 bits/s

PRBO

User ROM

PRB1

User ROM¢

(SCSI boot)

+The KAV30 performs a DECnet DDCMP boot.
tThe KAV30

first copies the contents of the user ROM

to the system RAM.

If you do not specify the boot flag information or the device name, the
console program uses default values. The default values depend on the
KAV30 configuration.
B[OOT]

[/<DATUM>]

PRB1[:]

This command invokes the SCSI bootstrap program. The SCSI bootstrap
program loads an application program from a SCSI device to the KAV30
system RAM and starts the application.

5-2

Operating the KAV30

The SCSI bootstrap program searches each SCSI device for the
[SYSO.SYSEXE]SYSBOOT.EXE file and loads this file (the user application)
into the KAV30 system RAM, before starting the application. The SCSI
bootstrap program first searches the device with the lowest SCSI ID, then
the device with the next-lowest SCSI ID, and so on until it searches the
device with the highest SCSI ID. If the SCSI bootstrap program encounters
errors while searching a device, it ends the search of that device and
continues the search with the next device.
The <DATUM> qualifier is optional. It specifies a hexadecimal value
representing the boot flags. The console program passes the <DATUM>
value as a longword to the SCSI bootstrap program. The following table
describes the possible <DATUM> values:
Value

Action

00000002

Causes the bootstrap program to halt if it encounters errors,
other than Fatal drive error and Device not responding errors,
while searching a device.

00000010

The SCSI bootstrap program searches SCSI devices for a
called [SYSMAINTIDIAGBOOT.EXE

file

and loads this file (the

application program) into the KAV30 system RAM before starting
the application.
00000100
|
n0000000

The SCSI bootstrap program prompts you for the name of a file
containing the application program.
The SCSI bootstrap program searches the SCSI devices for a

file called [SYSn.SYSEXE|JSYSBOOT.EXE and loads the file
(the application program) into the KAV30 system RAM before
executing it.

You can combine boot flags. For example, if you set the <DATUM> qualifier to
00000102, the SCSI bootstrap program prompts you for the name of a file.
The bootstrap program halts if it encounters errors.
The PRB1 parameter indicates that you want to invoke the SCSI bootstrap
program. The SCSI bootstrap program is in the KAV30 user ROM. If you
replace the SCSI bootstrap program with an application program, this
command invokes the application program. You can type a colon (:) at the
end of the device name, but it is not required.

Operating the KAV30

5-3

Operating the KAV30

D[(EPOSIT]

[/<QUALIFIER>]

<DATUM>

This command writes the specified data into a specified address.
use the following optional qualifiers with this command:
Qualifier

Explanation

A byte access

A word access

A longword access

A virtual memory access

A physical memory access

An internal register access

A general-purpose register access

/N:<COUNT>

Repeat the command
integer

Access protected addresses

<COUNT>

You can

times, where <COUNT>

is an

Note the following points about the qualifiers:
If you do not specify qualifiers with a DEPOSIT command, the console
program uses the previous set of qualifiers that you specified with this
command.
If you specify conflicting qualifiers, the console program
perform the command and displays an error message.

does not

The /U and /N qualifiers affect only the command in which you type

them.

The /U qualifier allows you to access almost all the addresses. If you
do not specify the /U qualifier, a protected DEPOSIT or EXAMINE

command can access memory only in the PFN map, or physical
addresses between 20000000 and 3FFFFFFF.

The <ADDRESS> parameter is a hexadecimal value representing a memory
address. The DEPOSIT command supports the following symbolic

addresses:

5—4

Symbol

Explanation

The address last referenced by an examine or deposit command.

Operating the KAV30

Symbol

Explanation

The address last referenced by an examine

The address immediately following the address last referenced by an

exception of general register addresses.
examine or deposit command.

memory

or deposit command,

with the

For references to physical or virtual

spaces, the address is the final address in the memory

space

plus the size of the last reference (1 for byte, 2 for word, 4 for longword).

The address immediately preceding the address last referenced by an

examine or deposit command.

For references to physical or virtual

memory spaces, the address is the final address in the memory space
minus the size of the last reference (1 for byte, 2 for word, 4 for longword).

The default <ADDRESS> value is equal to the + symbolic address.
The <DATUM> parameter is a hexadecimal value representing data that you
want to place in the memory location. The default <DATUM> value is zero.
E{XAMINE]

[/<QUALIFIER>]

[<ADDRESS>]

This command displays the contents of the specified address in hexadecimal
format.
The supported qualifiers and the address specification are identical to those
of the DEPOSIT command.
HE([LP]
This command displays all the console commands,
and available options.

supported parameters,

I (NITIALIZE]

This command
R[EPEAT]

initializes the CPU.

This command repeatedly executes the specified command.
executing the command, press Ctr//C.
The <COMMAND> parameter can be any valid KAV30
the exception of REPEAT.
S[TART]

To stop

console command,

with

This command executes instructions at a specified address. The address
is within the context of the user’s memory management mode (physical or
virtual).

Operating the KAV30

5-5

Operating the KAV30

To execute this command, the Interrupt Stack Pointer (ISP) must contain
a valid virtual or physical address. The console program pushes two
longwords onto the interrupt stack. If the interrupt stack contains an
invalid address, the console program displays the following message:
204

ISP

ERR

Note
The ISP is undefined after you switch on the power or reset the KAV30.

T[EST]

<test-name>

This command executes a specified diagnostic test. The <test-name>
parameter specifies a diagnostic test name. Before you execute this
command, execute the UNJAM command to reset the KAV30. See

Appendix B for information on the KAV30 diagnostic test names.

See

Section 3.1 for information on how to monitor the status of the KAV30
diagnostic tests.

As with the self-test, in most cases the console program stops executing a
diagnostic test and displays error information if it detects a serious error.

If diagnostic tests complete successfully, the console program displays the
console prompt. If diagnostic tests are disabled or the console program
detects that the hardware function that you want to test is missing, the
console program displays the following message:
240

NOSUCHDEV

U[NJAM]

This command resets the system. It resets all the registers to zero, and
resets all the logic circuitry to state zero.
e = =6<COMMAND>

! <COMMENT>

The exclamation point (!) prefixes a comment. If the console program
encounters an exclamation point, it ignores the rest of the line.

5.1.3

Console Program

Messages

The console program displays informational and error messages. Informational
messages do not have message numbers. They consist only of text. However,
error messages display a question mark (?), followed by a 2-digit hexadecimal
number, followed by an abbreviated text message. The 2-digit hexadecimal
number is the message number. See the rtVAX 300 Hardware User’s Guide for
an explanation of the console program error messages.

5-6

Operating the KAV30

5.2

Booting the KAV30
This section describes how to boot the KAV30.
the following methods:
e

Execute a BOOT

To boot the KAV30, use one of

console command

See Section 5.1.2 for information about the BOOT
e

console command.

Execute a programmed boot command
Use software to enter a programmed boot command.
use depends on the programming language you use.
Development Utilities Guide for more information.

The command you
See the VAXELN

Perform a remote trigger
Perform remote triggers from a host VAX computer that 1s running the
VMS operating system and is connected to the KAV30 via Ethernet. To
perform a remote trigger, you must have the following:
-

A KAV30

that is configured to allow remote triggering.

A VAX host computer with a network database that is set up to access

for information on configuring the KAV30.

See Section 2.4

the KAV30.

To set up the host computer network database to access the KAV30,
use the network control program (NCP) on the host computer. Use
the NCP program to define the KAV30 node name, address, hardware
address, and load file. For example, to set the hardware address, node
name, and load file for QNA-O, enter the following commands at the
NCP prompt:
NCP>
NCP>
NCP>

SET
SET
SET

NODE
NODE
NODE

KAV30
KAV30
KAV30

HARD ADDRESS 08-00-2B-16-39-45
SERVICE CIRCUIT QNA-0LOAD FILE USER: [DAY] TEST. EXE

However, before you boot the KAV30, ensure that the network services
are enabled on the host computer. For example, to enable the network
services on QNA-O, enter the following commands at the NCP prompt:
NCP>
NCP>
NCP>

SET
SET
SET

CIRCUIT
CIRCUIT
CIRCUIT

QNA-0
QNA-0
QNA-0

STATE OFF
SERVICE ENABLE
STATE ON

To perform a remote trigger, enter the TRIGGER NCP command on the
host computer. See the NCP help utility for more information about

the NCP commands.

Operating the KAV30

5-7

Operating the KAV30

An Ethernet link between the KAV30 and the VAX host computer. See
Section 2.7 for information on connecting the KAV30 to an Ethernet

network.

See the VMS documentation
listed in this section.

for more

information

on the VMS

commands

Supply power to, or reset, the KAV30
When you supply power to, or reset, the KAV30, it uses its default
configuration to determine the boot options and automatically boots.

5.3

Using Utilities
This section describes how to use the KAV30 utilities. The user ROM on the
KAV30 that you receive contains eight utilities. You can use the utilities to
perform a variety of functions, including testing and debugging the KAV30.
To execute a utility, enter the KAV30 START console command and specify the
start address of the utility.

However, before you execute utilities, enter the

following console commands to initialize the rtVAX 300:
>>>
>>>

UNJAM
INIT

Table 5—2 describes the KAV30 utilities. It gives the start address of each
utility and describes the function that the utility performs.
Table 5—2

KAV30 Utilities

Start Address

Function

$200870040

Continuously runs the KAV30 self-test. Digital recommends that you
execute the UNJAM console command before executing this utility. If
the first running of the self-test does not complete, you must reset or

$200870044

Allows you to enable or disable the running of the comprehensive
system memory diagnostic test (test number D) during the self-test.

switch off the power on the KAV30

and execute the utility again.

See Appendix B for more information about diagnostic test number D.

$2008’0048

Allows you to set the calendar/clock’s date and time.

$2008’004C

Continuously shows the calendar/clock’s date and time.

$2008’0050

Displays information about the SCSI targets on the SCSI bus, and

allows you to set the KAV30 SCSI ID.

(continued on next page)

5-8

Operating the KAV30

Table 5-2 (Cont.)

KAV30 Utilities

Start Address

Function

$2008'0054

Tests the VMEbus and VSB.

$2008’0058

Displays information that helps you to use the utility that starts at
address $2008’0054.

$2008’005C

Displays this table.

5.4 Testing the KAV30 Auxiliary Power Supply
This section describes how to test the KAV30 auxiliary power supply. The
auxiliary power supply is the source of power for the KAV30 battery backed-up

RAM and the KAV30 calendar/clock. To test the KAV30 auxiliary power supply,
perform one of the following actions:

Execute diagnostic test number 3.
See Section 5.1.2 for information about executing KAV30 diagnostic tests.
If the >>> prompt is not displayed, and the KAV30 displays a 3 on its
high status display and an 8 on its low status display, the auxiliary power
supply has failed. This is expected behavior when the KAV30 battery is
the auxiliary power supply and the battery has been connected for the first
time (see Section 3.1 for more information).
Call the appropriate KAV30

system service.

See the KAV30 Programmer’s

Reference Information manual for more information.

If the auxiliary power supply fails, the contents of the calendar/clock and
battery backed-up RAM are unpredictable. The auxiliary power supply can fail
under the following conditions:
The battery is the auxiliary power supply and the battery is dead.
The VMEbus
has failed.

standby power supply is the auxiliary power supply, and it

Neither the battery nor the VMEbus
power supply.

standby power supply is the auxiliary

Operating the KAV30

5-9

Operating the KAV30

5.5

Troubleshooting the SCSI Bus
This section helps you to troubleshoot a SCSI bus. If you order a KAV30 that
has a SCSI controller, the KAV30 contains a SCSI port. You can connect a
SCSI bus to the SCSI port. The SCSI bus must have at least one source of
power to its TERMPWR signal. Any device on the SCSI bus can supply power
to this signal. You can use the KAV30 status display to troubleshoot the power
supply to the TERMPWR signal.

You can troubleshoot the power supply to the TERMPWR signal only when the
VMEbus crate that houses the KAV30 has its power switch in the on position.
When the power switch is in the on position, the KAV30

uses the decimal point

to the left of the digit on the high status display to indicate status information
about the TERMPWR signal. Table 5—3 describes how you can use the status
of the decimal point to troubleshoot the SCSI bus.

Table 5-3

Troubleshooting the SCSI Bus

Other Devices

Jumper

set

Status of

on the SCSI
Bus

to Supply
TERMPWR

Decimal
Point

Not lighting

The high status display is
functioning correctly.

Lighting

The high status display is not
functioning correctly.

Yes

Not lighting

The SCSI termination power fuse
has blown.

Yes

Lighting

The SCSI termination power fuse
is intact.

Yes

Not lighting

No other device on the SCSI bus
supplies power to the TERMPWR
signal.

Yes

Lighting

At least one other device on the
SCSI bus supplies power to the
TERMPWR signal.

Yes

Not lighting

Explanation

The SCSI bus termination power

fuse has blown and no device,
other than the KAV30, supplies
power to the TERMPWR signal.

(continued on next page)

5-10

Operating the KAV30

Table 5-3 (Cont.)
Other Devices

Troubleshooting the SCSI Bus

Jumper

set

on the SCSI

to Supply

Yes

Bus

TERMPWR

Status of

Decimal
Point

Explanation

Lighting

At least one device on the
SCSI bus supples power to the

TERMPWR

signal.

Operating the KAV3O

5-11

Replacing the KAV30 User ROM
This section describes how to replace the KAV30 user ROM. It gives

information on the following:

6.1

Overview of the KAV30 user ROM (see Section 6.1)

Removing the KAV30

Replacing the EPROMs

Programming the EPROMs

from a VMEbus

crate (see Section 6.2)

(see Section 6.3)

Overview of the KAV30

(see Section 6.4)

User ROM

This section gives an overview of the KAV30 user ROM. The KAV30 that you
receive contains 256K bytes of user ROM. The KAV30 uses two 16-bit wide
EPROMs to implement the user ROM. Each EPROM is 128K bytes in size.
The first 96K bytes of the user ROM are reserved for Digital. These bytes
contain the code for the KAV30 diagnostic tests and utilities. The user area of
the user ROM starts at 96K bytes. The user area on the KAV30 that Digital
ships contains SCSI boot code. You can replace this SCSI boot code with a user
application. However, the user application code must begin at the start of the
user area, and thus overwrites the SCSI boot code.

If you want to store a user application in the user area of the user ROM, you

might need to replace the KAV30 EPROMs with larger capacity EPROMs.
Table 6-1 describes the possible user ROM sizes. The user area on the
KAV30 that Digital ships is 160K bytes (256K bytes minus 96K bytes) in size.
However, the KAV30 accommodates EPROMs that provide a capacity of up to
1M byte of user ROM. Therefore, 904K bytes (1M byte minus 96K bytes) is the
size of the largest user area, and also the largest user application, that you can
have.
If you want to replace the KAV30 EPROMs,
following conditions:

the new EPROMs

must satisfy the

Replacing the KAV30 User ROM

6-1

Replacing the KAV30 User ROM

The

access time must

The disable time must be 50 ns or less

The enable time must be 50 ns or less

Table 6-1
User

ROM

User ROM

120 nanoseconds

(ns) or less

Sizes

EPROMs

EPROM

128K bytes

Two 32K by 16-bit EPROMs

27C0512

256K bytes

Two 64K by 16-bit EPROMs

27C1024

512K bytes

Two

128K by 16-bit EPROMs

27C2048

1M byte

Two 256K by 16-bit EPROMs

27C4096

Part

Number

Note

The part numbers listed in Table 6-1 refer only to EPROMs supplied
by Digital. If you use similar EPROMs made by other manufacturers,
the part numbers are different. The KAV30 operates correctly, however,
if the EPROMs are of the correct type and size.

On the KAV30, two JEDEC

you to connect the EPROMs.

sockets, an even socket and an odd socket, allow

The EPROM

you connect to the even socket

supplies the low-order 16 data bits of each 32-bit longword that you store
in the user ROM. The EPROM you connect to the odd socket supplies the

high-order 16 data bits of each 32-bit longword that you store in the user ROM.
Note

Different revisions of the KAV30

module are shipped with different

EPROMs. See the KAV30 Hardware Release Notes for information
about the EPROMs that are shipped with each revision of the KAV30.

6.2

Removing the KAV30 from a VMEbus

Crate

This section describes how to remove the KAV30 from a VMEbus
remove the KAV30 from a VMEbus crate, follow these steps:
1.

6-2

Back up all the software and data on the VMEbus

Replacing the KAV30 User ROM

system.

crate.

Replacing the KAV30 User ROM

Set the power switches of the SCSI devices connected to the VMEbus
system to the off position.
Set the power switches of the devices connected to the system to the off
position.
Set the power switch on the VMEbus

crate to the off position.

To protect the KAV30 from ESD, wear an antistatic wrist strap while
handling the KAV30. Place the KAV30 on an antistatic mat.
Caution

If you do not wear an antistatic wrist strap while handling the KAV30,
or if you do not place the KAV30 on an antistatic mat, you risk
damaging the KAV30.

Unplug the connections to the KAV30.
Unscrew the two front panel screws that secure the KAV30
crate.

in the VMEbus

Unlock the KAV30 by simultaneously pulling up the top extractor-lever,
pushing down the bottom extractor-lever, and pulling the KAV30 out of the
VMEbus crate.
Pull out and remove the KAV30 from the VMEbus

crate.

10. If the battery is the auxiliary power supply, and you do not want to back
up the battery backed-up RAM and calendar/clock, configure the battery
jumper to prevent battery wastage. See Section 2.4.1 for more information.

11. Place the KAV30 in an antistatic bag.
Caution

If you do not place the KAV30 in an antistatic bag, you risk damaging

the KAV30.

If you want to use the system from which you removed the KAV30, follow these
steps:

Reconfigure the system’s VMEbus and VSB backplanes. See the system
documentation and the VSB documentation for more information on
configuring the backplanes.

Replacing the KAV30 User ROM

6-3

Replacing the KAV30

User ROM

Insert a conductive blank panel in the backplane slot that you removed the
KAV30 from.

Set the power switches on the SCSI devices connected to the system to the

on position.

Set the power switches on the devices connected to the system to the on
position.
Set the power switch on the crate to the on position.

6.3

Replacing the EPROMs
This section describes how to replace the KAV30 EPROMs.
how to replace the KAV30

EPROMs.

Figure 6-1 shows

Note

Some versions of the KAV30 are shipped with a piggyback socket on
the EPROM sockets. The part number for the piggyback socket is

FD-23361-01.

Caution

Never remove the piggyback sockets from the EPROM
remove the EPROMs from the piggyback sockets.

sockets.

Instead,

To replace the KAV30 EPROMs, follow these steps:
1.

Remove the KAV30 from the VMEbus
for more information.

crate.

See steps 1 to 8 in Section 6.2

Remove both EPROMs from the KAV30. Make a note of the odd and even
EPROMs. Place the EPROMs to one side, you will need them later.
Program the new EPROMs with the KAV30 firmware and the application
programs you want to include. See Section 6.4 for more information.
Insert the new EPROMs. See Figure 6—1 for more information. Make sure
to insert the EPROMs so that pin 1 of the EPROM is in the socket for
pin 1.

6—4

Replacing the KAV30 User ROM

Figure 6-1

Replacing the KAV30

REV:
SN:

EPROMs

Socket for
Pin 1

WFO16P0084

ENET:

08-00-2B-16-03-09

EPROM
Sockets

EPROM

Pin 1

EPROM
(Upside Down)
RE_EN05826A_90

Caution

If you do not insert pin 1 of the EPROM
risk damaging the EPROM.

into the socket for pin 1, you

Insert the KAV30 into the backplane slot that you removed it from in
Turn on the VMEbus
information.

system.

See steps 2 to 4 in Section 2.9 for more

Replacing the KAV30 User ROM

6-5

Replacing the KAV30 User ROM

6.4

Programming the EPROMs
This section describes how to program the EPROMs

with code for the KAV30

diagnostic tests, the KAV30 utilities, and a user application. To program the
EPROMs with code for the KAV30 diagnostic tests, the KAV30 utilities, and a

user application, follow these steps:

Note

If you program the EPROMs

the KAV30 SCSI boot code.

with user application code, you overwrite

Convert the application programs into VAXELN images using the VAXELN
System Builder with the destination set to ROM. See the VAXELN System
Development Guide for more information about the VAXELN System

Builder.

Convert the VAXELN image, created in step 1, into two files.
One file contains the low-order 16-bits of each longword, and the other
file contains the high-order 16-bits of each longword. This conversion is
necessary because of the physical arrangement of the user ROM:

EPROM

supplies the low-order 16-bits, and the odd EPROM

high-order 16-bits of each longword read from the user ROM.
3.

Read the contents of the even EPROM
into the ROM burner memory.

the even

supplies the

that you removed from the KAV30

The even EPROM contains the low-order
make up the KAV30 firmware.

16-bits of the longwords that

Caution

If you do not include the code for the KAV30 diagnostic tests and
utilities in the new EPROMs, you risk causing a malfunction in the

KAV30.
4.

5.
6.

6-6

Append the file containing the low-order 16-bits of each longword in the
application programs (see step 2) to the contents of the ROM
memory, starting at 96K bytes.

burner

Program the new even EPROM

burner

memory.

with the contents of the ROM

Repeat steps 3, 4, and 5 for the odd EPROM.

Replacing the KAV30 User ROM

The EPROMs now contain code for the KAV30
utilities, and a user application.

diagnostic tests, the KAV30

Replacing the KAV30 User ROM

6-7

KAV30 Hardware Specifications
This appendix gives the KAV30
on the following:

A.1

hardware

specifications.

e¢

Temperature

Power supply specifications (see Section A.2)

Bus load specifications (see Section A.3)

Timing specifications (see Section A.4)

It gives information

and humidity specifications (see Section A.1)

Temperature and Humidity Specifications
This section gives the KAV30 hardware temperature and humidity
specifications. Table A—1 lists the KAV30 hardware temperature and humidity
specifications.
Table A-1

Temperature and Humidity Specifications

Parameter

Specification

Operating conditions:
Temperature range

5°C to 50°C

Temperature rate of change

20°C/h

Relative humidity

10% to 95% RH (noncondensing)

Maximum relative humidity rate of change

10% RH/h

Maximum wet bulb temperature

32°C

Minimum dew point temperature

2°C

Heat dissipation

45 W (maximum)
(continued on next page)

KAV30

Hardware Specifications

A-—1

KAV30 Hardware Specifications

Table A-—1 (Cont.)

Temperature and Humidity Specifications

Parameter

Specification

Nonoperating conditions:
Temperature range

-40°C to 66°C

Relative humidity

95% RH

(maximum)

Storage conditions:
Temperature range

5°C to 50°C

Relative humidity

10% to 95% RH

Note

Digital strongly recommends that you operate the module in crates or
environments with a forced cooling of at least 100 Ifm. If you do not
follow this advice, the MTBF of your module may degrade significantly.

A.2

Power Supply Specifications
This section gives the KAV30 power supply specifications.
the KAV30 maximum power supply specifications.
Table A-2

Maximum

Table A—2 indicates

Power Supply Specifications

Supply

5°C

20°C

50°C

+5 V

9.5A

TOA

+12 V

200 mA

-12 V

200 mA

These power specifications do not include the +12 V power requirement of

devices that you connect to the AUI port. However, this current is limited by a
fuse and by the capacity of the backplane connector. These power specifications
include the +5 V power requirement of the SCSI terminators.
The typical power consumption for a KAV30 is 6.1A at 25°C for the +5 V
power supply. This does not include the +5 V power requirement of the SCSI

terminators.

A-2

KAV30 Hardware Specifications

A.3

Bus Load Specifications
This section gives the KAV30 bus load specifications.
KAV30 bus load specifications.
Table A-3

Table A—3 lists the

KAV30 Bus Load Specifications

Signal Name

Capacitive

Load (pF)

hi (uA)

loz. (uA)

lin (uA)

lozH (HA)

-1

-50

ACFAIL

-1

AMO

-100

-50

AQl1 - A31

-1

- AM5

BBSY

-100

BCLR

—

BERR

-1

-100

—

-200

BGOIN

- BG3IN

BGOOUT

BG30UT
BRO

- BR3

DSO

50
_—

-50

—

- DS1

-1

-50

DOO - D31

DTACK

-l

-5

IACK

120

IACKIN

—

IACKOUT

—

IRQ1

-20

-100

100

- IRQ7

-1

-50

LWORD

SERCLK

—

-50
—

SERDAT

—

SYSCLK

—

-50

SYSFAIL

-10

SYSRESET

-1

-50

WRITE

-1

-50

KAV30 Hardware Specifications

A-3

KAV30 Hardware Specifications

A.4

Timing Specifications
This section gives the KAV30 timing specifications. Table A44 lists the KAV30
system RAM

Table A-4

access timing-specifications.

System

RAM

Access Timing-Specifications

Type of Access

Time (ns)

rtVAX 300
Byte access

200

Word-aligned word access

200

Word access with bits <1:0> set to 11

300

Aligned longword access

200

Nonaligned longword access

300

Aligned quadword access

300

Nonaligned quadword access

400

Aligned octaword access

500

Nonaligned octaword access

600

SCSI! Controllert

Aligned longword access

400

VMEbus Slave Logic Circuitryt
Aligned longword access

500

Block access

500

+The access times do not include the delay involved in obtaining control of the DAL bus. Typically,

this delay takes between 100 ns and 1000 ns. However, this delay depends on what instruction the
CVAX is currently executing, and can be much longer.

A-4

KAV30 Hardware Specifications

Diagnostic Tests
This appendix describes the KAV30 diagnostic tests. Table B—1 lists the
KAV30 diagnostic tests. Supply the test name when you execute a test. The
KAV30 displays the test number on its high status display and on the console
terminal, when it executes a test. The KAV30 displays a test’s error number
on its low status display, when it tests that error condition.
Table B—1

KAV30 Diagnostic Tests

Test

Error

Name

Number

Description

Tests that the rtVAX 300 power supply is correct and
that the rtVAX 300 can write to the rtVAX 300 display
register.
Tests that the rtVAX 300 ROM

checksum is correct,

that the high and low bytes of the rtVAX 300 ROM are

the same version, and that the rtVAX 300 ROM

test

patterns are correct. It also tests the functionality of
the rtVAX 300 LED registers.
Initializes and verifies the rtVAX 300 scratch memory.
The rtVAX 300 scratch memory is random-access

memory (RAM). The rtVAX 300 ROM code uses the

rtVAX 300 scratch memory. The test uses a bit-pattern
test, an address test, and a cleared to zero test. You

must have 16K bytes of valid memory to pass this test.
Checks that the rtVAX 300 console responds to the

console address, and tests the functionality of the
console serial line unit (SLU).

Not implemented.
Verifies the operation of the rtVAX 300 FPU.

(continued on next page)

Diagnostic Tests

B-1

Diagnostic Tests

Table B-1

(Cont.)

KAV30

Test
Name

Test
Number

Error
Number

Diagnostic Tests
Description

Verifies that the rtVAX 300 interval timer interrupt
signal exists, that the interval timer generates
interrupts when enabled, and that it is accurate.
Tests the functionality of the rtVAX 300 Ethernet
interface. Tests that the Ethernet network ID ROM
contains a valid network identification, and that the
Ethernet network checksum is correct.
Verifies the system RAM, SGM RAM, and the FIFO
buffer RAM. It also tests the functionality of the FIFO
buffer RAM write interrupt.

Tests the functionality of the four FIFO buffers, that

the FIFO buffer entries are processed in the correct
order, that the read operations from an empty FIFO
buffer result in an error, and that the write operations
to a full FIFO buffer result in an error.
Tests that the KAV30

CPU

can correctly access the

logic circuitry that implements the CSR bits.

Tests that the logic circuitry that implements the CSR

bits can interrupt the KAV30 CPU.

Tests the auxiliary power supply and that the KAV30

CPU can correctly access the calendar/clock. Verifies
the battery backed-up RAM and tests that the KAV30
CPU can correctly access the VMEbus interrupt logic
circuitry.
Tests that the KAV30 CPU can correctly access the
SCSI controller, and that the SCSI controller can
correctly interrupt the KAV30 CPU.

Reserved for future use by Digital.
Indicates that the system is waiting for or executing a
console command.

Indicates that the system is trying to boot.
Indicates that the boot host is found, or that a ROM

footprint is located.

Indicates that the ROM

invalhid.

or SLU is not present or is
(continued on next page)

B-2

Diagnostic Tests

Table B-1 (Cont.)

KAV30 Diagnostic Tests

Test

Number

Name

Error

Description

Indicates that control is passed to an Ethernet boot or

to an external ROM

code.

Diagnostic Tests

B-3

VAXELN

Pascal Program

This appendix contains a sample Pascal Program that can be used to read
diagnostic error information stored in the battery backed-up RAM on board the
KAV30 module.
MODULE

read_diag_error_info;

{KAKA

R KERR

KK KKK RRR

KH KR KKK KKK

KEK

KKK

KERR

AK KKK KKK KKK KKK KK KKK KKK KKK HK KK KKK KAKA

{*
{*

(C)

1992

DIGITAL

EQUIPMENT

CORPORATION

* }

THIS SOFTWARE MAY BE COPIED WITHOUT FEE PROVIDED THAT THE
COPIES
ARE
*}
NOT
MADE OR DISTRIBUTED FOR DIRECT COMMERCIAL ADVANTAGE,
THAT CREDIT
*}
TO THE SOURCE IS GIVEN AND THAT THIS ENTIRE COPYRIGHT NOTICE IS INCLUDED.*}

{*
{*
{ *
{ *

THE
INFORMATION
IN
COMMITMENT BY DIGITAL

{ *
{*
{*

THIS
SOFTWARE
SHOULD
EQUIPMENT CORPORATION.

NOT

CONSTRUED

DIGITAL EQUIPMENT CORPORATION ASSUMES NO RESPONSIBILITY FOR
SUPPORT, OR RELIABILITY OF THIS SOFTWARE.
THIS SOFTWARE IS
DISTRIBUTED "AS IS."

{*
{*
{*
{*
{RAK

RRR KKK KKK RK KERR

{ This

KKK

Program

can

non-volatile

RAM.

}

INCLUDE

used

read

the

KKK KKK KKK KKK KR K KKK

diagnostic

error

*}
*}

USE,

*}
*}
* }

KKK KKK KK KKK KKK KE |

information

stored

Sget_message_text;

PROCEDURE
VAR

RK KR KEK KKK KKK RK KARE

THE

handle_error(

error_text

status

: INTEGER);

: VARYING_STRING(255);

BEGIN
ELNSGET_STATUS_TEXT

( status,
[STATUSSIDENT, STATUSSFACILITY, STATUSSTEXT,
STATUSSSEVERITY],
error text);

WRITELN (error_text) ;

VAXELN

Pascal Program

C-—1

VAXELN

Pascal Program

END;

PROGRAM

read_diag_error_info(

INPUT,

OUTPUT);

CONST

diag_error_page = %X20110600;
mem_offset
= SX0FC;
data_offset
= %X108;

TYPE
byte = [BYTE] 0..255;
error_info = PACKED RECORD
upper_led :
filler 1
lower_led :
filler 2
count_info

END;

= PACKED RECORD
count : [POS(0)])
END;

error_info_array
VAR

[POS(0)] byte;
[POS(8)] ARRAY [1..3] OF byte;
[P0S(32)] wees
[POS(40)] ARRAY [1..3] OF byte;

filler

: [POS(8)]

= ARRAY

[1..90]

byte;

ARRAY

memory_ptr
data_ptr

: “count_info;
: “error_info_array;

page_ptr

“ANYTYPE;

error count

INTEGER;

page_ptr_value
1
status

[1..3]

OF BYTE;

error_info;

INTEGER;

: INTEGER;
: INTEGER;

BEGIN
{ map

page

containing

diagnostic

error

information

ALLOCATE_MEMORY(
IF

page_ptr, 1024, PHYSICAL
STATUS := status);
NOT ODD(status) THEN
BEGIN
handle _error( status);
EXIT

}

diag_error_page,

END;
page_ptr_value

page_ptr

INTEGER;

memory_ptr :: INTEGER := page_ptr_value + mem_offset;
data_ptr :: INTEGER := page_ptr_value + data_offset;

C-2

VAXELN

Pascal Program

VAXELN

{

how

many

errors

have?

}

error_count := memory_ptr®.count
IF error count > 0 THEN
BEGIN
WRITELN(’***

WRITELN;
WRITELN('***

Diagnostics

The

following

DIV

8 -

detected’,

test(s)

Pascal Program

1;
error_count,’

failed

error(s)');

***’);

WRITELN;

FOR

END
ELSE

i := 1 TO error count DO
WRITELN (data_ptr®[1].upper_led,

WRITELN(’***

errors

detected

data_ptr%*[1i].lower_led)

diagnostics

***')

END.
END;

VAXELN

Pascal Program

C-3

D
KAV30
This appendix describes the KAV30
the following:

D.1

Port Connectors

port connectors.

It gives information on

Console and auxiliary port connectors (see Section D.1)

AUI port connector (see Section D.2)

SCSI port connector (see Section D.3)

Console and Auxiliary Port Connectors
This section describes the console and auxiliary port connectors. The console
and auxiliary port connectors have the same layout and pin specification.
Both ports use a modified modular jack (MMJ) connector. These ports are
collectively known as serial line ports. Figure D—1 shows the serial line port
connector layout.

KAV30

Port Connectors

D-1

Port Connectors

Figure D-1

Serial Line Port Connector Layout

Table D—1 describes the serial line port connector pin specification.

D-2

Table D-1

Serial Line Port Connector Pin Specification

Signal Name _—_— Explanation

+5 V

Ready out

TXD+

Transmit Data+

GND

Transmit Data-

RXD-

Receive data-

RXD+

Receive data+

Not used

Ready in

KAV30

Port Connectors

D.2

AUI

Port Connector

This section describes the AUI port connector.
port connector pin specification.
Table D-2

Table D-—2 describes the AUI

AUI Port Connector Pin Specification

Signal Name

Explanation

GND

Control In circwit Shield

COLL+

Control In circuit A

XMIT+

Data Out circuit A

GND

Data In circuit Shield

RCV+

Data In circuit A

GND

Voltage common

Not used

GND

Control Out circuit Shield

COLL

Control In circuit B

XMIT-

Data Out circuit B

GND

Data Out circuit Shield

RCV-

Data In circuit B

+12 V

Voltage Plus

GND

Voltage shield

Not used

KAV30

Port Connectors

D-3

Port Connectors

D.3

SCSI

Port Connector

This section describes the SCSI port connector. Figure D-—2 shows the SCSI
port connector layout. Table D-3 describes the SCSI port connector pin
specification.
Figure D—2

D—4

KAV30

SCSI

Port Connectors

Port Connector

Layout

Port Connectors

Table D-3

SCSI Port Connector Pin Specification

Signal
Name

Explanation

Signal
Name

Explanation

No Connection

# - DB(O)

Data 0

GND

Ground

GND

Ground

No Connection

- DB(1)

Data

No Connection

GND

Ground

No Connection

- DB(2)

Data 2

GND

Ground

GND

Ground

No Connection

- DB(3)

Data 3

GND

Ground

GND

Ground

No Connection

~=—- DB(4)

Data 4

No Connection

GND

Ground

No Connection

= - DB(5)

Data 5

GND

Ground

GND

Ground

No Connection

+ - DB(6)

Data 6

GND

Ground

GND

Ground

No Connection

= - DB(7)

Data 7

No Connection

GND

Ground

No Connection

-DB(P)

Data parity

No Connection

ATN

Attention

No Connection

-BSY

Busy

No Connection

-ACK

Acknowledge

No Connection

GND

Ground

GND

Ground

-RST

Reset

No Connection

-MSG

Message

No Connection

-SEL

Select

No Connection

-C/D

Cmd/Data

No Connection

- REQ

Request

No Connection

-VO

Input/Output

No Connection
(continued on next page)

KAV30

Port Connectors

D—5

Port Connectors

Table D-3 (Cont.)

D-—6

SCSI Port Connector Pin Specification

Signal
Name

Explanation

Signal
Name

Explanation

29.

TERMPWR2

Term +5 V

No Connection

GND

Ground

No Connection

33.

No Connection

KAV30

Port Connectors

Glossary
The glossary defines some of the important terms used in this guide.
application program

A program that performs an end-user task.
AU!
Attachment unit interface. An IEEE 802.3 compliant compatibility interface.
auxiliary power supply
The source of power for the KAV30 battery backed-up RAM and KAV30
calendar/clock. The source of the auxiliary power supply can either be the
KAV30 battery or the VMEbus standby power supply.
backplane
A printed circuit board at the rear of a crate which, by means of its attached
connectors, mates with the modules and constitutes the crate segment.
back up
The process of making copies of the data stored on the disk, so that you can
recover that data after an accidental loss.

big-endian device
A device based on the 68000 family of processors.
boot

To execute the boot loader program.
system when the power is on.

This program is always present in the

boot dévice
The device that contains the application program that is booted when the
system starts up.

Glossary-—1

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

CSR bit
Control and status register bit.

The CSR bits consist of both input bits and

output bits. The CSR input bits report on the status of the KAV30 hardware,

whereas the CSR output bits control the KAV30
DAL

hardware.

bus

Data and address lines bus. A 32-bit multiplexed bus. The rtVAX 300 is the
source of the DAL bus.
DECconnect

The Digital cabling system that extends Ethernet and terminal
interconnections into offices and work areas.

DELNI
A local area network interconnect product that gives eight separate network
interfaces from a single transceiver tap.

DESTA
A station adapter that acts as a ThinWire Ethernet transceiver. A DESTA
adapter allows you to connect a station with a transceiver cable to ThinWire
Ethernet.
diagnostics
The programs that detect and identify malfunctioning hardware.

DMA
Direct memory access. A method of accessing a device’s memory without
interacting with the device’s CPU.
down-line

load

To send a copy of a system image or other file over a line to the memory
target node.

of a

DRAM
Dynamic read-only memory. A read/write memory
retained by a continually circulating signal.

Glossary—2

device in which data is

electromagnetic
Pertaining to the force fields generated through electrical processes.

EMI
Electromagnetic interference

EPROM
Erasable programmable read-only memory. EPROM is a type of read-only
memory that can be erased, and so returns the device to a blank state.
ESD
Electrostatic discharge.
Ethernet

A type of local area network (LAN) based on Carrier Sense Multiple Access
with Collision Detection (CSMA/CD).

FIFO
First-in/first-out. The order in which processing is performed.
FIFO queue processes data on a first-come, first-served basis.
FIFO
An

For example, a

buffer

area in which

devices

can store and retrieve data.

FPU
Floating point unit.
points.

A device that can process expressions that include decimal

ground
A voltage reference point in a system that has a zero voltage potential.

H4000
An Ethernet

transceiver.

H4005
An

Ethernet

transceiver.

ISP
Interrupt stack pointer. The stack pointer for the interrupt stack. Unlike the
stack pointers for process context stacks, which are stored in the hardware
PCB, the interrupt stack pointer is stored in an internal register.
Glossary-—3

JEDEC
Joint Electron Device Engineering Council.
jumper
A short length of wire used to complete a circuit temporarily, or to bypass a
circuit.

LIFO
Last-in/first-out. The order in which processing is performed.
LIFO queue processes data on a last-come, first-served basis.

For example,

little-endian device

A device based on the Intel™ family of processors.
MMJ
Modified modular jack. A socket that accepts an MMP
attached to electrical circuits at the other.

at one end and is

MMP
Modified modular plug.

A plug that connects to an MMJ.

module

A printed circuit board that contains electrical components and electrically
conductive pathways between components. A module stores data or memory,
controls the functions of a device.

NCP
Network control program. The block that contains the necessary information
to set up a virtual circuit or to accept or reject a request to set up a virtual
circuit.
port
The physical connector.
printed circuit board
A circuit wired or etched on a phenolic or fiberglas material, complete with all
the necessary components for performing a specific function.

PTT
Postal, Telephone, and Telegraph.

Glossary—4

RAM
Random-access memory.

A read/write memory device.

RISC
Reduced instruction set computer.

ROM
Read-only memory. A memory in which information is permanently stored at
the time of production and is not alterable by computer instructions.

scsi
Small computer systems interface. An interface designed for connecting disks
and other peripheral devices to computer systems. SCSI is defined by an
American National Standards Institute (ANSI) standard.
SELV
Safety Extra Low Voltage. According to UL 1950 (US) and EN 60950 (Europe);

a SELV circuit is a secondary circuit, which is so designed and protected,
that under normal and single fault conditions the voltage between any two
accessible parts, or between one accessible part and the protective earthing
terminal equipment for Class I equipment does not exceed a safe value.

Under normal conditions this limit is either 42.4 V peak, or 60 V dc. Under

fault conditions higher limits are specified in this standard for transient
deviation.

SGEC
Second-generation Ethernet controller.

SGM
Scatter-gather map.

transfer:
e
¢

A means

of allowing either of the following types of data

From pages in memory that are not contiguous to contiguous blocks on a

bus

From contiguous blocks on a bus to pages in memory
contiguous

that are not

slot

A position where a printed circuit board can be installed into a backplane.

Glossary—5

SLU
Serial line unit. A port you can use to connect serial line devices such as

terminals and printers to the KAV30.
standard

Ethernet

An IEEE 802.3 compliant Ethernet network composed of standard Ethernet
cable as opposed to thin Ethernet cable.
system
A combination of system hardware, software, and peripheral devices that
performs specific processing operations.
terminator

A special connector that gives electrical termination of a bus.
ThinWire

A trademark used to describe Digital’s IEEE
local distribution of data communication.

802.3 compliant products used for

transceiver

A device that gives a single physical connection between standard Ethernet
and Ethernet communication equipment.

UART
Universal asynchronous receiver/transmitter.
data using serial lines.

A UART

receives or transmits

VSB
VME

subsystem bus.

802.3
An IEEE standard describing the physical and data link layers of a local area
network based on bus typology and Carrier Sense Multiple Access/Collision

Detect (CSMA/CD).

Glossary-6

Index
Battery backed-up RAM,
6-3
Battery jumper, 6-3
Baud rate

A
A24 base slave address

setting the, 2-9
AC_FAIL signal, 2—2, 2-9
Airflow requirements, 2-14

Antistatic bag,

Antistatic mat,

serial line ports,

1-3, 2-1, 6-3

Arbiter functionality, 2-8
VMEbus,
4-2, 4-6,4-8

VSB, 4-2, 4-7, 4-8
AUI port, 1-7, D-3
connecting an Ethernet loopback
connector,

2-13

connecting an Ethernet network,
connecting devices,

pin specification,

2-12 to 2-13

D-3

Auxihary port, 1-7, 2-2, 2-5, D-1
connecting devices, 2-11
layout, D-2

pin specification,

D-2

Auxilary power source,

Auxiliary power supply,

2—5

3-2, 6-3

Byte-swap logic circuitry,
2-12

CSR bits
Cable
DEC

423 serial line,

DECconnect office,
Ethernet,

SCSI,

2-14

1—5, 2-12

Calendar/clock,

1-2, 1-5