Digital PDFs

AC-8234D-NC

September 1978

79 pages

Original

2.7MB

Document:	DEC X11 Module Programmers Guide
Order Number:	AC-8234D-NC
Revision:	0
Pages:	79
Original Filename:	http://bitsavers.org/pdf/dec/pdp11/xxdp/x11_listings/AC-8234D-NC_DEC_X11_Module_Programmers_Guide_Sep78.pdf

OCR Text

eee
eee
eee
eee
eee
·eee
eee
eee
eee
eee
eee
eee
eee
eee
cee

eeeeec-..;eeece
eceeeceeeece
eeeeeeeeeeee

xxx
xxx
xxx

XXX
XXX

xxx

xxx
XXX
XXX
XXX

XXX
XXX
XXX

XXX
XXX

ccecoecccee:e

eccceecceecc
cccccccccccc

MMM
MMM
MMM
MMM
MMM
MfVliVI
MMMMMM
MMrM.'lMrJi
MMIVIMrl1M
MMf/lMMM
MMMrJlMM
MMMMMM
MMM
MMM
MMM
MMM
MMM
MMM
rJI"v1M
Mf'l1M
MMM
MMM
MMM
MMM
MMM
MMM
MrJlM
MMM
MMM
MMM
M!Vl~v1
MMM
MMM
MMM
MMM
MMM
MIVlM
MMM
MMM
MMM
MMM
MMM
MMM
MMM
MMM

x~x

}\XX
XXX
XXX

000
000

GOO
GOO

000

OOQ

GOO
GOO
QOO
QOO

OO(~

000

QOO

XXX
XXX
XXX

XXX

000
000
000
000

XXX
XXX

EEEEEEEEEEEEEEE
EEEEEEEEEEEEEEE
EEEEEEEEEEEEEEE
EEE
EEE
EEE
EEE
EEE
EEE
EEEEEEEEEEEE
EEEEEEEEEEEE
EEEEEEEEEEEE
EEE
EEE
EEE
EEE
EEE
EEE
EEEEEEEEEEEEEEE
EEEEEEEEEEEEEEE
EEI:.EEEEEEEEEEEE

GOO

000
000

QOO
QOQ

;"AAAAAAAA
AAAAAAJ\AA
AAAAAAAAA

GOO

000
000
000
000
000
000

GOO
GOO

XXX
XXX
XXX
XXX
XXX
XXX

QQQQQQOOQ
OC)QQQQOQQ
OOQQOQOOQ

OOQ
(~~t)j?CH~

OOOQOO

QQQQOQ

000

QQQ
GOO
000

MM?1l
MMM

MMM

Mr.~M

Mr/lM

MMMMMM

Mf\,r:1~~11\'~rJt

MMIv'lMMM

MlW.1r;1MM

MMM

MMM
MMM

MMiJI

I. .TMM

Mf;IM

iV!MM
MMM
MMM
Mr.~M

MMM
MMM
MMM
MMM
MMM
MMM
MMM

AAA
AAA
AAA

P;FF

/~,AA

FFfl'

AAA
AAA

FFF
FFF

DDDDDDDDDDDD
DDDDDDDDDDDD
DODDDDDDDDDD
DOD
DOD
DOD
DOD
DOD
DOD
DOD
DOD
DOD
DOD
DOD
DOD
DOD
DOD
DOD
DOD
DOD
DOD
DOD
DOD
DOD
DOD
DOD
DOD
DOD
DOD
DOD
DOD
DOD
DOD
DDOOODDOOOrH)

DDDDDDDDDDDD
DDDDDDDDDDDD

W,MM

Mi\tiMMW.Jl

MMM

AAA
AAA
AAA
AAA
AAA
AAA
AAA
AAA
AAA
AAA
AAA
AAA
AAA
AAA
P,AA
AAA
AAA
AAA
AAAAAAAAAJ\AAAAA
AAAAAAAAAAAAAAA
AAAAAAAAAAAAAAA
AAA
AAA
. AAA
AAA
AAA
AM\

FFFFFFFFFFFF:FFF
FFFFFFFFFFFFFFF
FFFFFFFFFFFFFFF
FFF
FFF
FFF
FFF
FFF
FFF
FFFFFFFFFFFF
FFFFFFFFFFFF
FFFFFFFFFFFF
FFF
FFF
FFF
FFF
FFF

MMr.iM\!iM
MMM
MMM
IViMM
i\.i:vlM
i\1iv'lM

MMM
MMM
MMM
MMM
MMM

MMM
MMM
MMM

MMM
IVfiVIM

XERSPL v8rsion 10~(2203)/3(C1) runr:ing on MTA065
*START* User BROWN,D!~K (400,3114] Job CXQUAA Seq. 7057 Date 03-Jan-79 13:49:37 Monitor IPC-F 603 [7CO] *START*
/TO:ML2',-4:BROWN, .. - Disti'inut'lon to ML21-4, slot 1:32
File: DSKM:CXQAFD.ME~~255>[400,1066] Created: 02-0ct-78 15:08:00 Printed: 03-Jan-79 13:50:10
QUEUE Sw~tche~: /PR~NT:ARRCW /FILE:ASCII /COPIES:1 /SPAeING:1 /LIMIT:728 /FORMS:NORMAL

IDENTIFICATION

PRODUCT CODE:

AC-8234D-MC

PRODUCT NAME:

CXQAFDO DEC/X11 MOD PROGMR GDE

PRODUCT DATE:

SEPTEMBER 1978

MAINTAINER:

DEC/X11 Support Group

THE INFORMATION IN THIS DOCUMENT IS SUBJECT TO
CHANGE WITHOUT NOTICE AND SHOULD NOT .BE CONSTRUED
AS A COMMITMENT BY DIGITAL EQUIPMENT CORPORATION.
DIGITAL
EQUIPMENT
CORPORATION
ASSUMES
NO
RESPONSIBILITY FOR ANY ERRORS THAT MAY APPEAR IN
THIS MANUAL.
THE SOFTWARE DESCRIBED IN THIS
DOCUMENT
IS
FURNISHED TO THE PURCHASER UNDER A LICENSE FOR USE
ON A SINGLE COMPUTER SYSTEM AND CAN BE COPIED
(WITH INCLUSION OF DIGITALS COPYRIGHT NOTICE) ONLY
FOR USE IN SUCH SYSTEM, EXCEPT AS MAY OTHERWISE BE
PROVIDED IN WRITING BY DIGITAL.
Digital
Equipment
Corporation
assumes
no
responsibi lity for the use or reliability of its
software on equipment that is not supplied by
Digital.
copyright
(c)
corporation

1975,1978

digital

equipment

Page 2

DEC/X 11 MODU LE

PROGRArr.:\~ERS

GU I DE

TABLE OF CONTENTS

Page

1.0

INTRODUCTION

2.0

DEC/X11 ABSTRACT

3.0

DEFINITION OF DEC/X11 MODULE

4.0

4.2
4.3
4.4
4.5
4.6
4.7

DEC/X11 MODULE CLASSIFICATION
BKMOD
NBKMOD
SBKMOD
IOMOD
rOMODX
IOMODP
IOMODR

5.0
5.01
5.02
5.03
5.04
5.05
5.06
5.07
5.08

HEADER MACRO CALL
MODULE NAME FORMAT
ADDR
VECTOR
Br-?1, BR2
DVC (DVID1)
RBUFVA
RBUFSZ
WBUFRQ

5.1
5.2

MODULE STATUS WORD
SR1-SR4 SOFTWARE SWITCH REGISTERS

6.0

IlSTART" TAG
IlRESTARTIt TAG

4. 1

6.1

6
6

6
6
7
7
.7
8

8
9

11
11
12
14
14

15
15

Page 3
TABLE OF CONTENTS
7.0
7.1
7.2
7.3
7.4
7.4.1
7.5
7.6

7.7
7.7.3
7.8
7.8.2
7.9
7.10
7. 1 1

7.12
7.13
7.14
7.15
7.16

(CONT)

MACRO CALLS
G~JBUF F
GETPA
MAP22
CKDATA
CHECK DATA ERROR
DATERR
HRDER
HRDER EXTENDED PRINTOUT
SOFER
MSGN,MSGS
MSG
BREAK
EXIT
PIRQ
ENDIT
ENDMOD
OTOA
BTOD
RAND

PAGE
16

17
17

18
20
20
21
22
23
24
24
25
25
26

26
28
28
28
29
30

8.3

MODULE CODE
Module Program Organization
Initialization Code
Device Service Code
Interrupt Service Code
Module Code Restrictions
Programming Standards

30
30
30
31
31
31
33

9.0

Assembling Source Program

10.0

Module Code Check List

11 .0

Module Checkout Procedure

8.0
8. 1
8. 1 • t
8.1 .2
8.1 .3

8.2

Appendix A:

Summary Table of Macros

Ap'pendi x B:

Assembled Module Example (RKAA) 40

Appendix

Appendix 0:

Source Module Example (RKAA)

List of Error Codes

Page 4
1.0

INTRODUCTION
The purpose of this document is to explain how to code a
Exerciser Module.
Before attHmpting to write a
DEC/Xl1
DEC/Xl1 module, the programmer must be fami 1 i ar with the
exerciser package, concepts, and have a working
DEC/Xl1
knowledge of the MACY 11 Assembly Language ,.
The following discussion assumes
that
the
programmer
understands the programming and hardware specification of the
device the module is being written for, and has constructed a
preliminary flow chart of the program.

~.O

DEC/X11 ABSTRACT
DEC/X11 is the system exerciser for the PDP-11 family.
It is
designed to promote system interaction and to detect system
fai lures, if any, caused by said interaction.
DEC/Xll
is
designed to be used as an overall system confidence test, and
to provide an indication of the integrity of individual
system components.
To that effect, the lndividual exerciser
modules can be written to be either simple or extehsive,
depending on the exact purpose.
The basic

component~

of the DEC/Xl1 package are:

DEC/Xll monitor library.

DEC/Xll option/device exerciser'modules.

DEC/Xll configurator/linker program.

DEC/Xl1 documentation.

The monitor library, exerciser optian modules, and the
configurator/linker program are used to generate a "Runtime
exerciser" that is loadable by the standard ASS loader.
The
configurator/linker program is used to configure and )ink the
desired monitor and modules and to generate the exerciser.
The exerciser includes only the monitor and exerciser modules
required to exercise the system.
This document does not
concern
itself
with the configuration-linking process.
Description and instructions for the configurator/linker are
found in the DEC/Xll Users Manual
DEC/Xl1 software is in modular form.
This format wi 11 allow
The
the final
exerciser to be only as large as necessary.
and
modular format also
provides
for
ea~y
updates
modifications.

Page 5
3.0

DEFINITION OF A DEC/X11 OPTION MODULE
A module is a program which is dedicated to one device,
controller or option and
is interfaced to t~e DEC/X11
monitor.
Each module is only part of the system exerciser
which can be made up of numerous modules. The monitor
provides various support and utility routines which can be
used by each module.
The module should be written in such a way as to ~Exercise"
the device.
It should not be written with a stand-alone
diagnostic in mind.
One must remember that when DEC/X1~
is
run,
the stand-alone diagnostics have been run and. the
devices verified.
The DEC/X11 exerciser modules are written
to find system problems,
not static problems. The module
should be designed to exercise the devices with the emphasis
on throughput and a minimum amount of overhead.
It should be
noted that tests requiring "operator intervention" should not
be included in the modules.

4.0

DEC/X11 OPTION MODULE CLASSIFICATION
Modules need software hooks so that they can communicate with
the monitor.
Different types of modules require different
software hooks.
These software-hooks are generated by the
use of "Header Statement ll macros.
DEC/X·11 modules have been
categorized into six groups depending upon the type of option
or device that is being tested.
By using the various types
of Header Statments that have been defined for each group
(section 4.1 to 4.6), the software hooks that are required by
the modu 1 e wi 1 I be generated Wil€-n the modu l e i s assemb 1ed
with the common library fi Ie called IIDDXCOM.P11". This file
includes macro call definitions and Common tags that are
required by the different types of modules.
NOTE
The first
thing
that
has
to
be
determined by the programmer,
is the
type of module that is being written.
This has to be done to determine the appropriate "Header
Statement" required by the module so that the proper software
hooks wil I be generated.
[Read the "Header" definitions
described in section 4.1
to 4.6 to determine the proper
Header Statement required.]
NOTE
The "Header" statement macro mlJst be the
first line of code in the module.

Page 6
4.1

BKMOD
The BKMOD type module runs in what is called the background
mode.
When writing BKMOD modules, the "START" and IIRESTRT"
tags must be at the same location.
BKMOD's are used when
exercising non-interrupt devices or functions~
For example,
the CPA module tests all
the basic instructions of the
PDP-11.
The format for the header macro call for a BKMOD is
shown below:
BKMOD

4.2

<ABCD >,ADDR,VECTOR,BR1,BR2.DVC,ICONST,IDNO

NBKMOD
The NBKMOD type module runs in non-restartable background
mOde,.
This type of module is run first and only once.
After it runs successfully it never runs again unless the
exercise is aborted and started over. An example would be a
module to check timing or parity on the system before the
other modules were run.
The format for the header macro call
for an NBKMOD module is shown below:
NBKMOD

4.3

<ABCD >,ADDR,VECTOR,BR1,BR2,DVC,ICONST,IDNO

SBKMOD
The SBKMOD type module runs in special background mode.
This
type of module runs only once after every relocation of the
exerciser.
This module type runs before NBKMOD's.
An
example would be a multi-processor enviroment using a bus
switch where the modules function would be required !whenever
the exerciser altered it's position in core. The format for
the header macro is shown below:
SBKMOD

4.4

<ABCD >.ADDR,VECTOR,BR1,BR2,DVC,ICONST,IDNO

IOMOD
Th~ IOMOD type
module operates in an input/output Mode.
These modules are interrupt driven and are capable of
input/output operation. They are generally associated with
buffer driven devices, ie: devices that do not do NPR's and
do not have IIword countll registers.
Examples are:
the TA-11
cassette,
the floppy disk, papertape reader/punch, and line
printers.
The format for the header macro call for a IOMOD
module is shown below:

IOMOD

<ABCD >,ADDR,VECTOR,BR1,BR2.DVC,ICONST,IDNO

Page 7

4.5

IOMODX
The IOMODX type module is an extended IOMOD.
It is used for
NPR devices and provides added capabilities not required by
IOMODls.
Some of these added capabilities include;
use of
the monitor suppl ied write buffer, abilitv to change the size
of the read and write buffers, access to the monitorls CHECK
DATA uti 1 ity, and conversion routines to get 18-bit addresses
from 16-bit addresses and, on certain cpuls, 22-bit addresses
from 18-bit addresses.
An example of this type of module
would be the RK-11 disk module. The format for the header
macro call for an IOMODX is as follows:
IOMODX
<ABCD >,ADDR,VECTOR,BR1,BR2,DYC,ICONST,IDNO,RBUFVA,RB
UFSZ,WBUFRQ

4.6

IOMODP
The IOMODP type module is a partially relocatable IOMODX.
This means that the module, because of hardware restrictions,
must be relocated only on certain fixed t)oundaries such as
32K.
Please consult with the DEC/X11 group if this type of
module is necessary.
The format for the header macro call
for the IOMODP is as follows:
IOMODP
<ABCD >,ADDR,VECTOR,BR1,BR2,DYC,ICONST,IDNO,RBUFVA,RB
UFSZ,WBUFRQ

4.7

IOMODR
The IOMODR type module is a restricted IOMOD which can not be
relocated at all because of hardware restrictions. This type
of module will only be permitted to run when the exerciser is
in the lowest memory bank (relocated to 0). The Unibus
tester module (BTB) is an example of this.
Please consult
the DEC/X11 group if this type of module is necessary. The
format fbr the header macro call is as follows:
IOMODR

<ABCD >,ADDR,VECTOR,BR'.BR2,DVC,ICONST,IDNO

Page 8
5.0

HEADER MACRO CALL
In the Header macro Statement, there is a string of arguments
that must be defined.
The type of module being defined
determines which arguments to be used. These arguments are
explained in detail in Sections 5.01 to 5.08.
An example of a header statement, taken from the RKA
is shown below.
IOMODX <RKAA >, 177400,
1024.

220, 5, 0, 0, 512.,

BUFIN,

module,
256.~

NAME <ABCD >
ADDR VECTOR BR1 BR2 DVC ICONST IDNO RBUFVA
RBUFSZ WBUFRQ
2b 1;. f i . j
The code generated, from this header call is shown on page
42.

5.01

Module Name Format
The format for naming the module in the title statement is as
follows:
<ABeD>
The argument consists of five characters within angle
brackets.
The last character must be left blank and is filled by the
configurator/linker at configuration time to identify
multiple
copies of the same module.
The first four characters which
must be
supplied will fo1 low the following convention:
AS

Any two alpha mneumonic characters that
identify the hardware and thus the module.
example would be a "RP"
for the RP-11 disk.

Alpha character to distinguish between two or
more
different modules for the same generic device.
The sequence A,
B, C, etc. must be used for each additional
module.
The RPB module for the RP04 would be an
example
of the second RP module that was written.

Alpha character used to specify the module
revision.
The sequence A, 8, C, etc. ~ust be used for each
new

Page 9
revision.
RPBC would show that this would be the
th i r'd
version of this program.
(SPACE)

S.02

ADDR

Numeric character used at configuration time
to distinguish between multiple copies of the
same module. This
space is filled by the configurator/linker. You
wi 11
always leave this as a space character when you
code your source program.
address of Device or Option

This specifies the unibus address of the device or option.
If more than one address is assigned, "ADDR" should specify
the first address in the group of contiguous addresses. When
the
header macro is executed, "ADDR" will be placed in word 6
[ADDR:] of the module interface [shown on page 42].
If the address will not be known until configuration time,
IIADDR" should be specified as a 1. If the operator
did not follow directions and set up the address, this will
generate an
odd address system error. This will reduce the possibility
of
chasing false errors.
"ADDR" must always be equal to zero for a BKMOD.
This word "ADDR:" must be used to derive any addresses the
module needs to access the device registers. Two examples
are shown below:

S. 02.1

S.02.2

Example #1:
MOV

ADDR.RS

;GET 1ST ADDRESS

MOV
MOV
MOV
MOV

#10000,2(R5)
#1024. ,4(RS)

;SET POWER CLEAR BIT IN COMMAND REG.
;LOAD BYTE COUNT REG.
;LOAD MEMORY ADDRESS REG.
; LOAD THE Cm~1MAND REG.

IIJBU FPA, 6( RS)
CMD,2(RS)

Example #2:
MOV
MOV
TST
MOV

ADDR,RS
RS,MTS
(RS)+
R5,MTC

;GET 1ST ADDRESS
;SET UP STATUS REG. POINTER
;MAKE CERTAIN REG. CAN BE ACCESSED
;SET UP COMMAND REG. POINTER

Page 10

TST
MOV
TST
MOV

(RS )+
RS,MTBC
(RS)+
RS,MTMA

;MAKE CERTAIN REG. CAN BE ACCESSED
;SET UP BYTE COUNT REG. POINTER
;MAKE CERTAIN REG. CAN BE ACCESSED
;SET UP ADDRESS REG. POINTER

MOV
MOV

#100,@MTC

WBUFPA,@MTMA

;SET POWER CLEAR BIT IN COMMAND REG.
; LOAD MEMORY ADDRESS REG.

Page 11
The first technique requires less storage and is more
efficient to use but requires that you save and restore'R5 if
you need to access registers in the interrupt service
routine.
This method is not recommended and Should be
avoided.
The second technique is less
efficient
but
eliminates the need to save and restore the registers in the
interrupt service routine.
It also makes the program easier
to follow and maintain. This is the recommended method.

5.03

Vector address of device or option

VECTOR

This argument specifies the vector address assigned to the
device or option.
If more than one vector is assigned,
"VECTOR" will specify th~ first vector address in the group.
When the header macro is executed, "VECTOR" will be placed in
word 10 [VECTOR:] of the module interface [shown on page 42].
"VECTOR" must always be equal to zero for a BKMOD.
If no vector is aSSigned or if it will
not be known until
configuration time, "VECTOR" should be specified as a 1.
If
the operator did not follow directions and set up the vector,
this will
generate an odd address system error.
This
minimizes the possibi lity of this module destroying some
other modulets vector.
"VECTOR" must be used in conjunction
with BR1 and BR2 to set up the interrupt vectors.

5.04

BR1, BR2

Bus priority levels

"BR1", and "BR2 must always be equal to zero for a BKMOD.
These arguments specify the BR priority
levels assigned to
interrupt driven devices.
Normally only BR1 will be used.
BR2 wil I only have to be specified if the device has the
capability of interrupting at two different levels. When the
macro is executed the values specified arl.~ encoded and placed
in word 12 of the modulets interface [shown on page 42].
"BR1" is put into the low byte, and "BR2" into the high byte.
For this reason, always use a "MOVB" instruction to load BR1
and BR2.
The following example shows a use of "VECTOR" and
"BR 1, BR2".
5.04.1

Example:
MOV
MOV
MOVB
TSTB

VECTOR,RO
HMTINTR,(RO)+
BR1,(RO)+
(RO)+

;GET VECTOR ADDRESS
;POINT VECTOR TO INTERRUPT SERVICE.
;SET BR1 LEVEL
;SET BACK TO EVEN ADDRESS

Page 12
5.05

Device Count

OVC

OVC is specified at configuration time.
This indicates the
number of active devices to be exercised by the module.
"OVC" contains the octal number of devices.
It is converted
in OVID1 50 each bit represents one device.
If the value of
OVC is defined as a 0, DVID1 will get assembled to equal a 1.
This means the module wi 11 try to test device 0.
Up to 16
seperate devices may be selected.
If, at configuration time,
3 devices were to be exercised, then the number 3 would be
entered
for
the
device
count
(DVC).
When
the
configurator/Linker types out the evc, it wi 11 now contain
the number 7---one bit
location representing each device.
This is the number that
is placed in DVID1, location 14
[shown on page 42] in the module interface.
For example,
if
3 were entered for DVC, then DVID1 would be set to:
BITO (1)
BIT1 (1)
BIT2 (1)

DEVICE 0 SELECTED
DEVICE 1 SELECTED
DEVICE 2 SELECTED

Hence 3 devices are selected and in OVID1 there is a 7.
At
run time
"DVID1" can be modified to specify any combination
of devices to be exercised.
The module w'ill use "DVID1"
to
determine which devices are to be exercised.
The only way to exercise non-consecutive devices is to modify
"DVID1" after configuration and just befor'e run time by using
the MOD command.
Tne MOD command is explained in the Users
Manua J •
The location "DV1D1" should not be modifiE~d by any code in
the module.
The contents of "DVID1" should be moved to a
work location and that location can be used by the module.
A
reason for modifying the temporary location would be to
eliminate devices with hard errors from the exercise.
The
normal config~red parameter must not be changed. An example
of the use of "DVID1" is shown beloltJ:

Page 13
5.05.1

Example:
Assume the module exercises 8 devices

KC1 :

1 $:

MOV
MOV
MOV
INC
BIT
BNE
CMP
BEQ
MOVB

DVID1 tTDVD
# 1 MSK
#-1 R 1
R1
MSK t TDVD
t

#10 R1
OUT
R1,CMD+1
t

;SAVE SELECTION PARAMETER
;SET DEVICE MASK
;SETUP R1
;GENERATE A NUMBER
;SELECT BIT SET?
:BR IF YES
;DONE 8 UNITS?
; BR I F YES
;SELECT UNIT

CODE TO EXERCISE SELECTED UNIT

ASL
BR

MSK
KC1

;SHIFT SELECT BIT
;GO TEST NEXT UNIT

If, in the exercise routine, the module determines that the
selected device was off line, the module could drop the
device from the exercise.

1$:
5.05.2

ICONST

MSK,TDVD
BIC
1$
BNE
END
continue

;DESELECT BAD DEVICE
;BR IF ANY SELECT BITS SET
;DROP THE MODULE

Iteration Constant

The Iteration Constant is the number of
should run to be considered end of pass.
be adjusted as follows:

times the module
This number should

The program run time for an invisible loMoO (eg:
floppy
disk) should be 30-40 sec.
The program run time for a visible 10MOD (e.g.
Line Printer)
should be one minute.
The program run time for a BKMoO (e.g. CP Test) should be 20
sec.
ICoNST is moved to location ICONT in the header during
assembly.
This location is used by thl~ "ENOlT" macro call
described in Section 7.12.
5.05.3

IOND

Module Identification Number

Each module has a unique 1.0. number for use by APT. During
assembly this number is moved to location IDNUM in the
header. Consult the DECX Group for the appropriate number.
5.06

RBUFVA

Virtual Address of the Read Buffer

Page 14
This argument, passed with the IOMODX and IOMODP calls,
is
the starting location for the read buffer' located within the
module.
The read buffer area contains the data that was read
from the device.
The most commonly used tag to denote the
starting location of this buffer is uBUFINu.
This read
buffer should normally be placed towards the end of the
module.
The monitor uses this tag as a reference point when
the check data [CKDATA] and get physical address [GETPA]
macros are called.

5.07

RBUFSZ

Read Buffer Size

This location, passed with the IOMODX and IOMODP calls,
contains the actual
size (or length) of the read buffer in
words.
Presently, read buffers are suggested to be a maximum
of
256 words.
The monitor uses this location as an
indication of the number of words to be checked in a Check
Data [CKDATA] call.
This value is assumed to be in Octal;
therefore, a period
must follow any number representing the base 10 system.

5.08

WBUFRQ

Write Buffer Size Requested

This location, passed with the IOMODX and IOMODP calls,
contains the desired write buffer transfer size in words.
If
the write buffer request is larger than the avai lable write
buffer,
uTHE LARGEST SIZE AVAILABLE"
is stored in header
location "WBUFSZ" [shown on page 42].
For this reason the
module should always reference the "WBUFSZ" location for
transfer size and not WBUFRQ.
This value is assumed to be in Octal, therefore, a period
must fol low any number representing the base 10 system. The
standard default size is 1024. words (1K).

Page 15
5.1

MODULE STATUS WORD
This status word is located at location 26 in the module
header interface. When the module program is assembled, each
macro generates different active bits in the status word of
that module. The status word also contains informative bits
of the module's condition.
The module status bits have the following meanings.
BIT 14 ( 1 )
BIT 14 (0 )
(1)

Module selected
Module deselected

eIr 13 (0 )

Module had been running but was
dropped by the monitor
Module wao not dropped

BrT 1 1 ( 1 )
BIT 1 1 (0 )

Module ;s active
Module ; s inactive

IOMOD

100000

IOMODR

112000

IOMODP

102000

IOMODX

110000

BKMOD

000020

NBKMOD

001000

SBKMOD

000000

BIT

The right half of the status word indicates the processor
status when running the module.
In the BKMOD, bit 4 is set.
Note:
BIT 11 (active bit) will always be zero for BKMODS
when it's status word is outputted by a keyboard command such
as SUM, MAP OR EXAM.

5.2

SR1,SR2,SR3,SR4

SOFTWARE SWITCH REGISTERS

The software switch registers are located at locations 16-24
in each module header interface. These words can be used by
the module program as general purpose program switches.
These words can be used to define or specify a unique device
option or to pOint to a specific routine in the module.
These words "MUST NOT" be modified by the software.
Any
SR1-SR4 options must be specified by the operator before the
module is run.
All SR1-SR4 bit definitions must be

defined

the

module

Page 16
documentation.
This will
enable to operator to correctly
modify "SR1-SR4" to meet specific needs.

5.2.1

Example:
Consider the RK11 (Appendix B Page 51) module.
SR1 defined:

BIT 2 RESET (0) TYPEOUT DATA LATE ERRORS.
BIT 2 SET (1) DO NOT TYPEOUT DATA LATE ERRORS
BIT
NBIT2,SR1
;TYPEOUT ERROR?
BNE
6$
;NO
MSGN$,DLTERR,BEGIN

In this example, SR1 is used to decide which direction the
module wi 11 take. One way it will type out the error message
and the other way it will omit the error message.

6.0

START TAG
The tag "START" must be used to identify the first executable
instruction in the module.
When the module is assembled, the address of "START"
is
inserted into the "INIT" word in the module "Header" [shown
on page 42] and the monitor uses the contents of this
location as the starting address of the module.

6.1

RESTART TAG - RESTRT
This tag must be used to identify the restart location in the
module.
The monitor will
return to this location after
completing the final ENDIT call.
"RESTRT 11 is normally at the
beginning of the program, just after the initialization code.
In "BKMOD" modules, the "START" and IIRESTFH" tags must be in
the same place.

7.0

MACRO CALLS
DEC/X11 has many macro calls available for use in the coding
of DEC/X11 modules.
Some are necessary and must be used,
while others simply make life easier. These macros include
calls for determining buffer sizes, check data routines,
monitor service routines, and different error reporting
routines.

Page 17
7.1

GWBUFF

Get Write Buffer

This macro is used in IOMODX and IOMODP modules to get write
buffer information from the monitor.
The monitor uses the
"write buffer" as an area to write "from" and not "into".
Information should never be written into the write buffer for
it could be destroying its own program.
The monitor will
size memory to determine the avai lable core left that can be
used for a write buffer.
The monitor
then compares this
value against the size of the write buffer requested (WBUFRQ)
in the module header.
If the write buffer size requested was
larger than the amount available, the monitor will store the
size avai lable in the Write Buffer Size (WBUFSZ location 142.
on page 43)
location in the header of the module.
If the
amount available was larger than the amount requested,
the
amount that was requested in the Write Buffer Request
(WBUFRQ) would be stored in the write buffer size (WBUFSZ)
location.
NOTE
For this reason it is essential that the
module program use the "Write Buffer
Si ze" (WBUFSZ) and not the "~lJri te Buffer
Size Requested" (WBUFRQ) .value to obtain
the size of the Write Buffer.
The GWBUFF macro also places the physical starting address of
the write buffer into the "WBUFPA" location and the extended
addr~essing bits into the
"WBUFEA"
lOCation.
The extended
addreSSing bits (16 and 17) are placed into bit positions 4
and 5 since this is the location of the EA bits in most of
the peripherals.
The locations WSUFSZ and WBUFRQ in the
module header must not be modified.
This macro should be
used before each new transfer cycle (eg:
[GWBUFF], WRITE.
Read, Check data, [GWBUFF], WRITE, Read, etc.).
The "WBUFSZ" value is a positive number and often must be
negated before being used.
The RKA module in "Appendix B"
shows a good example on how to use this macro. An example is
also shown below:
GWBUFF
MOV
WBUFSZ,WCNT
NEG
WCNT
MOV
WCNT,@RKWC
MOV
WBUFPA,@RKBA
BIS
WBUFEA,FUNCT

;GET THE WRITE BUFFER INFORMATION
;GET WRITE BUFFER SIZE
;CONVERT TO A NEGATIVE NUMBER
;LOAD RK WORD COUNT REG
;LOAD RK BUS ADDRESS
;LOAD EXTENDED ADDRESSING BITS IN
;FUNCTION COMMAND LOCATION.

The assembled appearance of GWBUFF will be "GWBUF$t BEGIN".

7.2

GETPA ADR

Get Physical Address

Page 18
This macro is used to convert a 16-bit virtual address to an
18-bit physical address.
"ADR" is an argument which contains
the virtual address.
The monitor takes tt,is virtual address,
converts
it to an 18-bit address, and places it in the two
locations following the "ADR" location.
These 3 locations
are already in the header for of the "IOMODX,IOMODR" and
IOMODP" modules.
NOTE
When using any other type of module,
make sure that that the following three
locations are provided, and in this
order.
ADR:
PA:
EA:

16-bit Virtual Address
will
contain
16-bit
physical
address on return
will contain extended addressing
(16 and 17) in bit positions 4 and
5 on return

The call "GETPA" will normally be used to get the physical
address of the read buffer, which the module ~~i 11 load into
the device register before issuing a read command.
This
command may be used, though, by any type of module whenever a
physical address is needed.
The physical address equivalent
of a virtual address will change only between an End Of Pass
and restart.
Thus "GETPA" cal Is should occur
in
the
START/RESTART code only.
The RK modul~ in Appendix BuseS
this macrO. Below is an example of "GETPA" macro.
GETPA RBUFVA
MOV
BIS

RBUFPA,@RKBA
RBUFEA,FUNCT

;GET THE PHYSICAL ADDRESS OF THE
;CONTENTS OF RBUFVA
;LOAD BUFFER ADDRESS OF DEVICE
;LOAD EXTENDED ADDRESSING BITS
;IN FUNCTION COMMAND LOCATION

The assembled appearance of GETPA ADR will be "GETPA$.

7.3

MAP22

ADR

ADR".

Map 22 Bit Physical Address

This macro is used to convert an 18-bit unibus address to a
22-bit physical address. MAP22 is used on devices capable of
22 bit addressing, such as RH70 devices on the PDP-11/70.
"ADR"
is an argument which contains the lower 16 bits of the
18-bit address.
Location XMEM. which immediately fol lows
ADR, must contain the shifted extended address bits (16 +
17). The monitor converts this to, a 22 bit address and
places it in the 2 locations immediately following the "XMEM"
location.

Page 19
NOTE
When using this call, make sure four
locations are provided in the modUle in
the following order:
ADR:

lower 16
address.

bits

thl~

bit

XMEM:

contains bits 16 and
positions 4 and 5.

bit

PA22:

wil I contain the lower 16 bits of
the physical 22 bit address.

EA22:

will
cantoin
the
extend~d
addressing bits (16 to 22) in bit
positions 0 through 4.

The IMAP22" call will normally be used to get the physical
address of the read buffer, which the module will load into
the device register before issuing a read command.
Word
"CONFIG"
in the module header is loaded with the 22-bit
addressing bit (bit 09)
if the hardware and the monitor
suppor t 22-b it addressi ng. Tt1e term ADDR22 is equated to
bit 09 in DDXCOM, the macro file for DEC/X11 option modules.
II

An example for this macro taken from the
below:
BIT
BEQ
MOV
ASR
ASR
ASR
ASR
MAP22
MOV
MOV

I~P8A

module is shown

#ADDR22,CONFIG ;22-BIT ADDRESSING?
1$
;NO, BRANCH
@RI-IBA, PA 18
;YES, GET 18 BIT ADDRESS
;EA BITS IN XMEM PREVIOUSLY SETUP
XMEM
XMEM
;MOVE EA BITS
;TO POSITION 4 + 5
XMEM
XMEM
;GET 22 BIT ADDRESS
PA18
PA22,@RHBA
;SETUP BUS ADDRESS REGISTER
;SETUP EXTENDED ADDRESS REGISTER
EA22,@RHBAE

;NEED NEXT FOUR LOCATIONS FOR MAP22
PA18:

XMEM:

PA22:

EA22:

;LOWER 16 BITS OF THE 18 BIT
;UNIBUS ADDRESS
;EA BITS OF THE 18 BIT ADDRESS
;IN BIT POSITIONS 4 + 5
;LOWER 16 BITS OF THE 22 BIT
;UNIBUS ADDRESS
;EA BITS OF THE 22 BIT UNIBUS
;ADDRESS (SITS 0 TO 4)

The
assembled
appearance
"MAP22$,BEGIN,ADR".

MAP22

ADR

wi 11

bit

Page 20
7.4

CKDATA ADR,ERRET

Request for monitor to Check Data

This macro requests the monitor to do a data comparison.
It
is used only in IOMODX and IOMODP modules.
The "ADR"
argument used with this macro must be the tag of the location
that contains the lower 16 bit address of the data being
compared.
This location is immediately followed by a word
containing the EA bits shifted into position 4 and 5,
fol lowed by a third word containing the size of the buffer.
The CKDATA macro compares the buffer indicated in the
argument with the write buffer. The write buffer information
is located in the "header" starting at WBlJFPA and must have
been previously set up by the call GWBUFF.
The "ADR" argument most commonly used with this call
is
RBUFPA.
The IOMODX module has allowed room in the header for
the locations needed.
These locations in the header appear
as follows:
RBUFPA:
RBUFEA:
RBUFSZ:
WBUFPA:
WBUFEA:
WBUFRQ:
WBUFSZ:

;Read buffer physical addr(~ss
;Read buffer EA bits
;Size of the Read Buffer
;Write buffer physical add!"'ess
;Write buffer EA bi ts
; Wr i te buffer size request(~d
;Write buffer size available

For example, the source macro call would be CKDATARBUFPA and
the assembled version will appear as:
CKDATA$,BEGIN,RBUFPA
The monitor wi 11 automatically handle all
data
error
reporting associated with this Check Data (CKDATA) call.
The argument ERRET (if defined) will request the monitor to
set return PC to that location if there was a data error.
If
there are no errors, or ERRET is not defined, processing will
contjnue with the next instruction following the CKDATA call.
7.4.1

CHECK DATA ERROR
If the monitor discovers a data error while checking the
buffer,
it will
report it. The printout looks the same as
that for a regular data error (7.5.1).
In a "CKDATA" call,
all
errors in a given transfer are counted as one error in
the mOdule error counter.
This count
is not incremented
until after the data errors have been !"'eported. The total
number of words in the transfer and the total number of
errors encountered are also reported.

Page 21
7.5

DATERR
Th is ca 11 is used to repor t an
lin-core I
data compar i son
errOrS.
The "DATERR" call
is usually never used in the
IDrJlODX or IOMODP modules.
Instead,
they use the "CKDATA"
call
to request monitor checking of their data.
Refer to
section 7.4.
Prior to using the "DATERR" call, ,the module
must
load certain words in the module interface. This is to
enable the monitor to report address and contents information
on the error typeout.
The words that must be loaded are
listed below:

7.5.1

ACSR

Address Control Status Register - Address of
control reg.

the

SBADR

Should Be Address
correct data.

WASADR

Was Address - Address of
"Was".

ASB

Actual data Should BE - Test data, what the
is supposed to be.

data

AWAS

Actual data
peal ly was.

data

Address of the "Should Be" or

Was - Actual

what

data,

the

data

what

the

really

Example of the Data Printout
The data printout looks as follows:
ABCDO
PC XXXXXX APC YYYYYV
CSRA AAAAAA SIB BBBBBB WAS WWWWWW

PASS#NNNNN.
ERR#NNNNN.
WRADR 000000 RDADR EEEEEE

Where:
ABCDO
PC XXXXXX
APC' YYYYYY
PASS#NNNNN:
ERR#NNNNN.
CSRA AAAAAA
SIB BBBBBB
WAS WWWWWW
WRADR DDDDDD
RDADR EEEEEE

Failing Module name.
Actual 22 bit phySical address of DATER$
call.
Assembled PC of DATER$ call.
Pass number during which error
occurred
(Dec i ma I)
Total number of errors encountered (DeCimal)
CSR address of fai ling device.
Data should be (Good Data)
Data was (Bad Data)
Address of expected data
Address of bad data.

Page 22
7.6

HRDER , <COMMENT>
This is used to request that the monitor print out an error
message for the module on the console. This call can be used
for a 11 hard errors.
The opt i ona 1 argument "Cm~MENT" perm its
the cause of the error to be printed out 2S a comment
statement in the assembled listing.
prior to coding the
"HRDER" call, the module code must load up the following
words in the modules interface:
CSRA with the address of the control register
ACSR with the contents of the control register
ASTAT with the contents of the status register,
if
applicable.
ERRTYP with the code for the particular error.
see
APPENDIX D for list of error codes.
If not
listed. consult the DeCX group and a new code will
be generated.
These locations cannot be loaded with any information other
than that indicated.
The reason for loading these locations
is that when the monitor first initializes the module.
these
locations are zeroed, and after each error, the status of
these registers could change. After printing the error,
the
monitor transfers control back to the statement immediately
following the "HRDER" call.
NOTE
If these locations do not get loaded
prior to the 1st error call, they will
be printed out as all zeros.

7.6.1

Example:
Assume R4 contains the CSR address and R5 contains the status
register address:
MOV
MOV
MOV
MOV
HRDER,

R4,CSRA
;LOAD ADDRESS OF CSR
(R4),ACSR
;LOAD CONTENTS OF CSR
(R5),ASTAT
;LOAD CONTENTS OF STATUS REG.
#11,ERRTVP
;ILLEGAL INTERRUPT OR DONE NOT SET
<ILLEGAL INTERRUPT>
RESTRT

The comma between HRDER and <comment> signifies the argument
"ADR" is not used. see section 7.7 for "ADR" explanation.

Page 23
7.6.2

Error Printout
The error printout looks as follows:
ABCDO
PC XXXXXX APC YYYYYY
PASS#NNNNN,
HARD ERR#NNNNN
CSRA AAAAAA
CSRC CCCCCC
STATC SSSSSS ERRTYP NNNNN
Where:
Failing module name.
Actual 22 bit physical address of error call
Assembled pc of error call.
Pass number during which error
occurred
(decimal)
HARD ERR#NNNNN. Total number of errors encountered (decimal)
CSR address of failing device, 0 if not
CSRA AAAAAA
applicable
Contents of device CSR, 0 if not applicable
CSRC CCCCCC
Contents of device status reg. if applicable
STATC SSSSSS
octal code for type of error
ERRTYP NNNNN
ABCDO
PC XXXXXX
APC YYYYYY
PASS#NNNNN.

7.7

HDRER ADR <COMMENT>

Extended Error Printout

This call requests the monitor to print out the standard
"HRDER" message (section 7.6)~ and also the contents of all
addresses in a table specified by the argument "ADR".
The
contents of all addresses in the table are printed out until
the terminator (177777) is encountered. After the printing
is done,
control
to the module resumes at.the location
immediately following the "HRDER" call.

7.7.1

Example Code:
To print out the contents of all the registers for the
Disk, the code would look like the following:
HRDER
TABLE:

177400
1 77402
1 77404
177406
177410
175412
177416
177777

RK-11

TABLE <DUMP THE CONTENTS OF THE RK DISK REG.>
;POINTERS TO THE RK REGISTERS

;TABLE TERMINATOR
NOTE

Before each "HRDER" call, the locations
CSRA, ACSR, ERRTYP and ASTAT must be

Page 24
loaded as in 7.6.
7.7.2

"EXTENDED" Error Printout Example
ABCDO PC XXXXXX APC YYYYYY PASS# NNNNN. HARD ERR# NNNNN.
CSRA AAAAAA CSRC CCCCCC STATC SSSSSS ERRTYP NNNNNN
XXXXXX XXXXXX XXX XXX XXXXXX XXXXXX XXXXXX xxx XXX XXX XXX
The first two lines of the extended error printout have the
same meaning as the error printout in section 7.6.2. The
third AND any additional lines, consist of up to eight (8)
octal
values
per
line.
They are p~inted to provide
additional inform~tion on the nature of the error.
These
octal values that are typed out should be well defined in the
module's documentation, since only numbers are actually
printed.
If the table contains device registers,
the
registers in the table should be in the same order as the
actual device registers.

7.7.3

SOFER ADR <COMMENT>
This call is used for "SOFT" data errors.
It is called and
used in the same manner as "HRDER". The arguments "ADR" and
"COMMENT" are of course optional. The standard and extended
error printouts give SOFT ERR#NNNNN. All prior setup for
SOFER call should be done as shown in section 7.6.
In
addition, if "ADR" is used - refer to section 7.7.1.

7.8

MSGN ADR

Message Call, MSGS ADR Message Call

These calls provide the means to print pure ASCIZ messages.
In the ASCIZ string the apostrophe (') serves to delimit the
message and the per-cent sign (%)
is interpreted by the
monitor as a CR/LF.
ADR is the pointer to a table of
messages.
The table must terminate with a 177777 entry. The
MSGN call produces a header line identifying the module name
and the MSGS call does not.
7.8.1

Example of Source Code
MSGN

SOFT

SOFT:

MES2
177777

;MESSAGE POINTI:'R
;TERMINATOR

MES2:

.ASCIZ

'%SOFT ERROR%'

Example Code Assembled:

MSGN$,SOFT,BEGIN

Page 25
7.8.2

Message Ca I I

MSG ADR

This call provides the means to print pure ASCII messages
(one message only - not a table as in MSGN). The apostrophe
(I) serves to delimit the message and the percent sign (%) is
interpreted as a CR/lF.
ADR is the address of the message.
Since no header identifying the module is produced,
the
module name should be included somewhere in the message.
7.8.3 Example of Source Code
MSG

TEXT

.ASCIZ I%RPA - TOO MANY WRITE ERRORS%I

TEXT:

Example Code Assembled:

7.9

BREAK

MSG$,BEGIN,TEXT

Temporarily Return to the Monitor

This call is used to transfer control,
t(?mporari ly bilCk to
the monitor.
It allows the monitor to transfer control to
pending requests while the current module is waiting for some
asychronous event to occur before proceeding. When executed,
the monitor obtains the return address of the module as the
address
immediately following the "BREAK" call. The monitor
saves the general registers in the Module Header locations
SVRO through SVR6,
then checks the queues for pending
requests.
When all previous requests have been serviced, the
monitor restores the registers and returns control to the
module at the instruction immediately follo~ing the break
call. Example follows:

NOTE
No timer/timeout loops, wait loops, etc.
of any kind are permitted without a
BREAK in the loop.
7.9.1

Example of a wait loop Using the

WAIT:
1 $:

MOV
#177777.ClK
BREAK
BIT
BNE
DEC
BNE
JSR

#BIT6,@lRKDS
2$
elK
1$

PC,DROP

BRE~K

call

;SET UP TIMER
;RETURN TO MONITOR TO LET OTHER
;MODULES RUN
;IS THE DRIVE READY?
;YES CONTINUE
;NO, WAIT SOME MORE+TRY AGAIN
;WAIT AGAIN
;TIMES OUT, DROP THE DRIVE.

The assembled code at 1$ wi 11 look 1 ike the following:

Page 26
1$:
BREAK$,BEGIN
BREAK$,BEGIN

7.10

EXIT

;RETURN TO MONITOR TO
;LET THE MODULES RUN

Exit to the Monitor - module waits for interrupt

This c a l l i s necessary since DEC/X11 modules are
not
permitted to "sit and wait" for interrupts to occur.
It is
used to return control of the processor back to the monit6r
when the module is waiting for an interrupt.
It is important
to remember that some instruction prior to the "EXIT"
is
necessary that wi 11 generate a subsequent interrupt.
If this
is not done, the module will never receive control again and
in effect, stop running.
For this reason an "EXIT" call is
never used when coding a module for a non-interrupt driven
device.
Another
important point to remember is that the
"EXIT" call is not a RTI and should never be used to return
from an
interrupt service routine. When the "EXIT" COlomand
is executed, the monitor saves the general
registers
in
locations SVRO through SVR6 located in the header of the
module [shown on page 42].
The monitor then passes control
to the next module waiting to be serviced. The following is
an example of the use of the EXIT call.

7.10.1

Example:
MOV
MOV

BIS
EXIT

WB,TMWC
WBU FPA, TMBA
WRCMD,TMCS

;LOAD BYTE COUNT REGISTER
;LOAD MEMORY ADDRESS REGISTER
;5ET WRITE COMMAND AND INT ENABLE
;RETURN TO MONITOR.
NOTE

If there is no system clock in the
exercise, and an interrupt does not
occur after an uEXIT" call is lJsed.
the
system
will
hang UP and all other
modules wi 11 stop. after an end of pass.
The source code of this macro will be
Code will be "EXIT$".

7.11

PIRQ ADR

~EXIT".

The

assembled

Do an RTI and continue at tag ADR

This call is the DEC/X11 method used to exit an interrupt
service routine and defer servicing at a lower priority.
This call is placed first in the interrupt service routine
whenever possible. This will increase the system throughput
by defering non-critical
interrupt service routines at a

Page 27
lower priority.
For instance, when the RK11 module receives
an inter~upt, it is known that none of
its registers ne~d
immediate
service or are in the process of changing.
Therefore, a PIRQ is used and checking for errors is done at
a lower
level.
On the otherhand, a communications device
such as the DH11, may have to empty a silo buffer immediately
or data may be lost.
After the necessary functions have been
taken care of, then'a PIRQ or an RTI (if more interrupts are
expected)
may be used.
When PIRQ is executed, the monitor
stores the request in a first-in/first-out queue at priority
7 and does an RTI.
This turns control of the processor back
to whatever code had control when this module interrupted.
It
is necessary"to keep interrupt service routines as short
as possible to prevent the other modules
from
being
temporari ly locked out and possibly getting data late or
timing errors.
When the PIRQ request is serviced from the monitor Queue, the
general
registers are restored from the module header
locations" SVRO through SVR6.
The monitor then transfers
control
back to the module at the location specified by the
"ADR" argument.
NOTE
If it is necessary to use the general
registers
in
the interrupt service
routine before using the "PIRQ" request,
the registers must first be saved.
This
is required because these
registers
belong
to the code that was being
executed when this module interrupted.
These registers must also be restored
before using the "PIRQ" or an "RTlu.

7.11.1

Example:
;INTERRUPT SERVICE ROUTINE
NTRUPT:
PIRQ 1$
;REQUEST TO HANDLE
;INTERRUPT SERVICE
;FOR THE RK MODULE
1$:
JSR
R5,ERRORS ;GO CHECK FOR ERRORS
Assembled Version:
NTRUPT:

; -----------------------------_ ... _------------------

PIRQ$,1$ BEGIN

;QUEUE UP TO CONTINUE AT 1$ AND RTI

; ---------- ------ ------------------------------ ---

7.12

1 $:

JSR

ENDIT

End of Iteration

R5,ERRORS

Page 28
This call infOrms the monitor that an end of iteration has
occurred.
The monitor will
increment Loc.
ICOUNT in the
header and compare ICONT with ICQUNT.
If equal, the monitor
will
report end of pass on the console and restart it at the
module's "RESTRT" tag.
If not equal,
th(~
monitor restarts
the module at the location immediately following the "ENDIT"
call. The module program should never modify locations ICONT
or ICOUNT.
NOTE
It is important to disable
interrupts
before each ENDIT call.
If an interrupt
occurs during an ENDIT
call
which

I,;nals Gnd of pass, th~ WholQ exerciser
may relocate and the return address from
the interrupt wi 11 be incorrect.
7.12.1

ENDIT Example From the RK Module
PASS:
The assembled code at locat ion PASS wi 11

look 1 ike:

PASS:
ENDIT$,BEGIN

7.13

ENDMOD

;SIGNAL END OF ITERATION
;monitor shall test end of pass

Drop Module from Exercise

This call is used to request that the monitor drop the module
from the exercise.
It would be used if the module detected a
fatal error that would prevent the module from continuing.
For example, the device selected for test was off line. When
this macro is executed the monitor stops the module by
setting bit 13 of the word "STAT" in module interface [shown
on page 42]. This prevents the module from ever getting
control
again.
It
is important that you 'shut down' the
module (eg:
turn off all
interrupt enables) prior to
executing the "ENDMOD" call macro.
Th(~ monitor prints the
fol lowing message to inform the operator that the module was
dropped:
ABCDO

7.14

DROPPED

OTOA NUM,ADR

APC

YYYYY

Octal to ASCII Conversion

This call converts one octal number to six ASCII characters.
This may be useful
prior to a print message using "MSGN".
Six "BYTES" must be provided. starting at location "ADR".
to

Page 29
store the result."NUM" is a location containing the number to
be converted.

7.14.1

Example
OTOA

NUM,ADR

;call macro to convert it to ascii

NUM:
ADR:

12345

;number to be converted
;reserve six bytes •

. BLKW 3

when assembled the result would look like:
OTOA$,BEGIN,NUM,ADR
and the result would be:
ADR+O
+1
+2
+3
+4

7.15

+5
BTOD NUM,ADR

060
061
062
063
064
065

Binary to Decimal Conversion

This call converts a binary number to its decimal equivalent
represented by 5 ASCII characters. This may be useful prior
to a print message using "MSGN".
Five bytes must be
provided,
starting at "ADR", to store the result. NUM is a
location containing the number to be converted.

7.15.1

Example
BTOD

NUM,ADR

;call the maCro to convert the
; number

ADR:
NUM:

.BLKW 3
00237

;reserve six bytes
;number to be converted

When assembled the result would look like:
BTOD$,BEGIN,NUM,ADR
and the results would be:
ADR+O
+1

060
060

Page 30
+2
+3
+4

7.16

RAND

061
065
071

Call to Monitor for Random Number

This call is used to request the monitor to generate a new
random number.
Location RANNUM in the module header will
contain the random number.

7.16.1

Exampl&

RAND
MOV

;cal1 for random number·
RANNUM,BLOCK ;To get new block

When assembled the result would look like:

RAND$,BEGIN
MOV
RANNUM,BLOCK ;To get new block

8.0

MODULE CODE
Standard PDP-11 code is used for writing DEC/X11 modules.

8.1

MO~ULE

PROGRAM ORGANIZATION

In most cases, a DEC/X11 module can be divided into 3
sections.
They are:
initialization, interrupt service, and
device service.

8. 1 .1

INITIALIZATION CODE
This code initializes the DEC/X"
are being tested.

module and the devices that

Page 31
8.1 .2

DEVICE SERVICE CODE
This section is the main portion of the module and will
be
supported by subroutines.
This will make the program flow
easier to follow and easier to debug.
This code will
initialfze t setup the device or options that are being tested
and issue the I/O commands for the I/O devices.

8.1 .3

INTERRUPT SERVICE CODE
This code is required to acknowledge the fact that an
interrupt has been received and to provide service to that
interrupt.
It i$ PQ~llblQ using thG PIRQ call to queue uP a
reQU&it to "6!RVIC~" the 1nt'Fr~pttng devlae at ~ 'at~~ time.
Tho philosophy applied t is that modules must spend a Minimal
amount of time in an interrupt service routine at a processor
status other than O.
This must be done in order to prevent
other devices from being locked out.
See Section 7.11 for
the proper use of the PIRQ instruction.

8.2

MODULE CODE RESTRICTIONS
Due to the monitor/module relationshipt
the
restrictions are in effect for exerciser modules:

following

Code must be capable of running on all PDP-11
processors.

No HALT instructions (except during debug).

NO WAIT instructions.

NO EMT cal Is.

No user trap calls

No processor status word modifications.

I/O modules must not perform waiting
not contain a BREAK call.

If some code must be performed in the interrupt
service routine before the PIRQ, and the general
purpose registers must be used,
the GPRS must be
saved
first and then restored before the PIRQ
instruction. The GPRS do not have to be saved when
executing code after the PIRQ instruction.

The stack pointer must not be modified in order
exit an interrupt sequence (use PIRQ call).

loops

family

that

Page 32
j.

NO alteration of the module header may be made by the
module, except, of course. use of the stack.

Load Medium Indicator: XXDP places in loc3tion 41
a
code which indicates which type of device was the
load medium for
the current boot.
Location 40
contains
the
actual
device
number
(e.g.
DK~,DK1),etc.).
If your device is an XXDP supported
load
medium,
your module must check these two
locations to determine if one of the units was in
fact the load medium.
If it was,that unit cannot be
tested and must be dropped.
An example of the
required code is in the module listing in APPENDIX A.
For a list of XXDP supported load media, along with
the meanings of the codes in locations 40 and 41, see

the XXOP SUPPORT GROUP.

Page 33
8.3

PROGRAMMING STANDARDS
Programming standards are needed to help insure similarity,
consistency
and
uniformity throughout all
the DEC/X11
modules.
Using these standards will make life easier for all
those who use DEC/X11.
The standards are as follows:
1.

is the 1st part of the module.
It will
include a brief abstract.
requirements (hardware and
software),
pass
definitions,
execution
time,
configuration
requirements.
device/option
setups,
operation options, non-standard printouts and any other
information that
is pertinent to the module.
A flow
chart can also be added to the documentation to show the
general operation of the module.

The header statement with its arguments should be on
first page following the documentation.

the

All constants and variables will be defined on
fo1 lowing the module header code.

the

page

The tag "START" should be Oil the 1st I ine
page, indicating the first line of code.

the

Tags should have meaningful names.

All local tags wi 11 appear in numerical
wi th 1$.

Every
line of code
meaningful comments.

Messages should be placed at the end of the program.

Subroutines
function.

Docu~entation

will

have

designed

order

beginning
line

least

support

10. All subroutines must contain a standard
for subrout i nes.
Th is IN i I I
inc 1 ucle
function or task of subroutine, the call
get to the subroutine. the parameters
registers used,
external parameters,
routines or notes.

single

document header
the entry name,
that was used to
passed (if any),
speCial
error

11. Any general purpose regist~rs (RO-R5) to be modified in a
subroutine, must be saved immediately upon entry to the
subroutine and restored just before leaving.
Using
registers to pass arguments is discouraged.
12. Nesting of subroutines is discouraged.
subroutines, such as convert octal
like, are acceptable.
13. Multiple entry

points

are

discouraged

Use of support
to ascii, and the
and

should

Page 34
avoided. When used, a1 I multiple entry pOints must be at
the beginning of the routine, and branched to the proper
location from there.
14. There will be only one exit from the routine and it
be the last line of executable code.

will

15. Subroutines must exit with an RTS instruction.
All
returns from subroutines (including error ret~rns and any
others) must be to the instructions immediately following
the JSR call.

9.0

ASSEMBLING THE MODULE PROGRAM
The fol lowing discussion assumes the programmer knows how to
edit and assemble programs using one of the following
techniques:
1.

On a PDP11 DDS system using

On a PDP10 system using "MACY11"

~MACR011~.

The
assembled
object
file
will
be
used
by
the
configurator/linker program to make it part of a system
exerciser load module.
The following steps are required:
1.

Using an appropriate editor program, a module source file
is created, having a fi Ie extension of ~.P11".

Using the appropriate assembler the source program is
assembled with the fi Ie DDXCOM.P11 [File containing the
DEC/X11 maCro call definitions and common tags].

After assembly, the fol lowing files should exist:

A source file with a ".P11" extension.

An object file with a ".OBJ" extension.

An assembly listing file with a ".LSTK
extension.

(or

similar)

Using the"appropriate Peripheral Interchange Program:
a.

Output the listing to a line printer.

Output the object file.
in PDP11
absolute
format, to a paper tape or multi-media.

loader

The Configurator/Linker will accept input from paper
tape, and multi-media. The only restriction is that
all modules to be 1 inked must be on the same medium.

Page 35
the
Having the listing of the module object file on
appropriate
input
medium, the module is ready to be
the
configured,
linked,
and
run.
Refer
to
Configurator/Linker
section
in
the
DEC/Xl1
document
[MAINDEC-11-DXQBA] for the required procedures.

.10.0

MODULE CODE CHECK LIST
programmer in
many problems

The following check 1 ist is an aid for the
checking the module code.
It highlights
encountered while writing the first modules.
1.

Use

~ADR~

to set up the required address pointers.

Use

~VECTOR~,

Use a byte instruction to set up

Prior to an ~EXIT~ call, execute
generate a subsequent interrupt.

that

wi 11

If the module is driving a non-interrupt device,
certain that there are no "EXIT~ or "PIRQ" calls.

make

Use an RTI
instruction to
service routine only when
used.

The "PIRQ" call should
service routine.

Make sure that there are
interrupt service routines.

The module must save and restore any registers
needed during the interrupt service routine.

10.

Prior to the

~BR1",

~HRDER"

~ACSR."ERRTYP~t",

and

and "BR2" to set up the vector area.

and

"BR1~

some

~BR2".

code

return from an· interrupt
the PIRQ instruction isn't
used
no

"SOFER"

exit

MONITOR

calls,

an
calls

load

interrupt
in

the

that

are

"CSRA~,

~ASTAT".

11.

Prior to the "DATERR" call, load "CSRA",
"WASADR", and "SBADR".

12.

Make sure the module can
after non-fatal errors.

13.

If a fatal error was foUnd that makes it impossible
continue, use an "ENDMOD~ call to drop the module.

recover

and

"AloJAS" ,
continue

running
to

Page 36

11.0

14.

Use an "ENDITII call
to
completed an iteration.

report

that

the

15.

Make sure there are no wait loops in the module
not include the BREAK call.

that

16.

Take care of any pending interrupts
any monitor calls.

executing

17.

Absolute memory references are

18.

Do not use any HALT, WAIT, TRAP or EMT instructions.

19.

Use "DVID1" properly to check for multiple devices.

20.

If the device has extended memory capability,
use
IIEABITS" properly to set up the extended memory bits.

21.

Turn off interrupt enable prior to executing any
call s ~

22.

Use the tag "START" to identify
instruction in the module code.

23.

In "BKMOD II modules, the "STARTII and
in the same place.

prior

module

has
do

prohibit~d.

the

first

"I~ESTRT"

monitor

executable
tags must be

DEC/X11 Monitor/Module Checkout Procedure
I.

DOCUMENTATION
a.

Ii.

All documentation must be complete and correct.

CODE
a.

The code must adhere to DEC/X11 Module standards
uniformity and compatability.

for

The code must adhere to DEC/X11 Module
coding
standards and conventions as outlined in this guide.

Page 37
Iii.

Eva 1 ua t i on

Every attempt must be made to validate the operational
integrity of the module.
By adhering to the following
procedure, an acceptable level of quality can be assured.

RUNNING ALONE
The module must be capable of
default conditions.

running

alone

under

The module must be run continuously for not less
hours and preferably 16.

than

ThG madul~ must b@ capable Qf running morG than 1

device

(or un; t, or 1 i he, Or cl"lannel t
etc.) t
minimum number of 2 devices must be run.

the abso1 ute

All error reports and
checked for accuracy.

messages

must

simulated

and

SR1-SR4
All
operational.

must

used

and

validated

Various combinations of DVID1 must be tried and validated
for proper operation.

Various transfer sizes must be tried (where applicable).

The module must be run in bipolar and/or MOS memory (
available ).

The module must run on all
PDP-11
the pDP-ll/70 and the LSI-11.

The module must be run (ie:
the program relocated)
in
all
banks of available memory on a system with memory
management (KTll).

options

processors

including

10) The module must be capable of recovering without'
from a powerfail in different banks of memory.
b.

its

errors

RUNNING IN A SYSTEM ENVIRONMENT
The module must be capable of running in a system environment
with other DEC/Xll modules.
The minimum system must include:
KTll, 28K memory, high speed disk, a communications device,
Magtape or Dectape, and an L or P clock.
1)

The module must be run in a system envi~onment for
not less than 8 hours and preferably 24 hours.

The largest system (the smallest being the
minimum system noted above) available must be used.

Page 38

At least 1 disk must be included as part
of the system.

At least 1 clock module (KW11-L, KW11-P)
must be configured in as part of the system.

The module must be run on the shared bus
of a DT03 ( if available ).

The module must be configured before any disk module
to assure it does not wipe out any modules following it~

The same tests required when the module
is running alone must be performed
with the module operating in this system environment.

Page 39

APPENDIX A

Summary Table of Macros

ASSEMBLED APPEARANCE

CODED APPEARANCE

-------_.._-,--------

--------.~------

GWBUFF

ADR

GWBUF$,BEGIN,ADR

GETPA

ADR

GETPA$,BEGIN,ADR

CKDATA

ADR

CDATA$,BEGIN.ADR
EXIT$,BEGIN

EXIT
PIRQ

ADR

PIRQ$,BEGIN,ADR

HRDER

ADR <COMMENT>

HRDER$,BEGIN,ADR ;COMMENT

SOFER

ADR <COMMENT>

SOFER$,BEGIN,ADR ;COMMENT

OAT ERR

DATER$,BEGIN

ENDIT

ENDIT$,BEGIN

ENDMOD

END$,BEGIN

S'REAK

SREAK$,BEGIN
BREAK$,BEGIN
ADR

MSGS

MSGS$,BEGIN,ADR

MSGN

ADR

MSGN$,BEGIN,ADR

MSG

ADR

MSG$,BEGIN,ADR

OTOA

NUM,ADR

OTOA$,SEGIN,NUM,ADR

BTOD

NUM,ADR

BTOD$,BEGIN,NUM,ADR

RAND

RAND$,BEGIN

Page 40

APPENDIX B
Assembled Module Example (RKAA)

RKAA DEC/X11 SYSTEM EXERCISER MODULE
RKAA.P11
13-MAR-78 00:00

MACY11 30A(1052)

20-MAR-78

.REM

IDENTIFICATION

PRODUCT CODE:

MAINDEC-11-DXRKA-G-D

PRODUCT NAME:

DEC/X11 RK11 MODULE

DATE:

JANUARY 1978

MAINTAINER:

DIAGNOSTIC GROUP

AUTHOR(S):

ROBERT E. UNDERWOOD

15:47

PAGE 2

Page 41

APPENDIX B

MACV11 30A(1052)

RKAA DEC/X11 SYSTEM EXERCISER MODULE
RKAA.P11
13-MAR-78 00:00

20-MAR-78

15:47

PAGE 3

ABSTRACT
RKA IS AN IOMODX THAT EXERCISES RK02, RK03, ~K04. RK05 DISK DRIVES ON AN
RK11 CONTROLLER. IT EXERCISES THE DRIVES BY DOING WRITES,
WRITE-CHECKS, READS, AND IN-CORE COMPARISONS.
ALL ERRORS DETECTED ARE REPORTED ON THE CONSOLE TTY.

REQUIREMENTS
HARDWARE:

TO 8 RK DISK DRIVES WITH AN RK11 CONTROLLER

STORAGE:: RKAA REQUIRES:
1. DECIMAL WORDS: 1043
2. OCTAL WORDS: 02023
3. OCTAL BYTES: 4046
3.

PASS DEFINITION
ONE PASS OF THE RKA MODULE CONSISTS OF 512 CYCLES OF THE BASIC TEST
SEQUENCE (WRITE, WRITE-CHECK, READ, DATA-CHECK). THE TEST SEQUENCE
WRITES 1024 WORDS, WRITE-CHECKS SAME, READS THE FIRST 256 WORDS,
AND DATA-CHECKS SAME.

EXECUTION TIME
ONE PASS OF RKA RUNNING ALONE ON A PDP-11/40 TAKES APPROXIMATELY 1 MINUTE.

CONFIGURATION REQUIREMENTS
DEFAULT PARAMETERS:
DEVADR: 177400, VECTOR: 220, SR1: 5, DEVCNT: 1
REQUIRED PARAMETERS:
NONE

DEVICE/OPTION SETUP
MAKE CERTAIN THAT ALL DRIVES ARE POWERED UP, WRITE ENABLED, AND READY

Page 42

APPENDIX B
MACY11 30A(1052)

RKAA DEC/X11 SYSTEM EXERCISER MODULE
RKAA.P11
13-MAR-78 00:00
7.

20-MAR-78

15:47

PAGE 4

MODULE OPERATION
TEST SEQUENCE:
A.
B.
C.
D.
E.
F.
G.
H.
I.
J.

SETUP DEVICE REGISTER ADDRESSES AND MODULE VARIABLES
RESET ALL DRIVES ON-LINE AND DROP ALL THAT ARE NOT
GET A DISK ADDRESS AND A FRESH BLOCK OF DATA
GET A DRIVE ADDRESS
DO A WRITE -- IF ERRORS, REPORT AND RETRY UP TO RETRY LIMIT
DO A WRITE-CHECK -- IF ERRORS, REPORT AND RETRY UP TO RETRY LIMIT
DO A READ -- IF ERRORS, REPORT AND RETRY UP TO RETRY LIMIT
DO A DATA-CHECK -- IF ERRORS. REPORT AND CONTINUE
IF END OF PASS, REPORT AND GO TO C
IF END OF DRIVES, GO TO C ELS~ GO TO 0

OPERATION OPTIONS
SRl BIT 0 SET(1):
IF THE RETRY LIMIT IS EXCEEDED ON ANY FUNCTION. A HARD ERROR
IS ASSUMED AND THE DRIVE IS DROPPED
SRl BIT 0 CLEAR(O):
IF THE RETRY LIMIT IS EXCEEDED, THE FUNCTION IS ABORTED AND
THE TESTING CONTINUES
S'R1 BIT 2SET(1):
WILL NOT TYPE OUT DATA LATE ERRORS BUT WIll KEEP TRACK
OF THE NUMBER OF DATA LATE ERRORS
SRl BIT 2 CLEAR(O):
TYPE OUT DATA LATE ERRORS AND KEEP TRACK OF THE NUMBER
OF DATA LATE ERRORS IN DLTCNT

NON-STANDARD PRINTOUTS
A.

MOST PRINTOUTS HAVE THE STANDARD FORMATS DESCRIBED IN
THE DEC/Xl1 DOCUMENT

ERROR MESSAGES DUMP THE CONTENTS OF THE 8 RK11 REGISTERS
IN THE FOLLOWING ORDER:
RKDS

RKER

RKCS

RKWC

RKBA

RKDA

RKMR

RKDB

Page 43

APPENDIX B

RKAA DEC/Xl1 SYSTEM EXERCISER MODULE
RKAA.Pl1
13-MAR-78 00:00
IOMODX
MODULE
.TITLE
DDXCOM

000000'
000000'

MACY11 30A(10S2)

20-MAR-78

15:47

PAGE 5

<RKAA >,177400,220,5,0,0,512.,S,BUFIN,256.,1024.
lS0000,RKAA
,177400,220,S,0,O,S12.,5,BUFIN,256.,1024.
RKAA DEC/Xl1 SYSTEM EXERCISER MODULE
VERSION S
26-JAN-78
. LIST
BIN
;************************************************~**********************

000000'
000000'
000005'
000006"
000010'
000012'
000013'
000014'
000016'
000020'
000022'
000024'
000026'
000030'
000032 1
000034 1
000036 1
000040'
000042 1
000044'
000046 1
000050 1
000052 1
000054 1
000056'
000060'
000062'
000064'
000066'
000070'
000072'
000074'
000076'
000100'
000102'
000102'
000104'
000104'
000106'
000106'
000110'
000112'

045522
000
177400
000220
240
000
000001
000000
000000
000000
000000
150000
000252'
000252'
000000
001000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000·
000000
000000
000000
000000
000416'

054101

040

BEGIN:
MODNAM:
XFLAG:
ADDR:
VECTOR:
BR1 :
BR2:
DV I D1 :
SRl :
SR2:
SR3:
SR4:

.ASCII /RKAA / ;MODULE NAME.
;USED TO KEEP· TRACK OF WBUFF USAGE
.BYTE
OPEN
17'7400+0
~lST DEVI~f ADDR.
;lST DEVICE VECTOR.
220+0
; 1 ST BR LEVE L.
PRTYS+O
.BYTE
PRTYO+O
;2ND BR LEVEL.
.BYTE
0+·1
;DEVICE INDICATOR 1.
;SWITCH REGISTER 1
OPEN
;SWITCH REGISTER 2
OPEN
;SWITCH REGISTER 3
OPEN
tSWITCH REGISTER 4
OPEN

, ;**********************************************************************
STAT:

150000
START
SPOINT: MODSP
PASCNT: o
ICONT:
51:2.
ICOUNT:
SOFCNT:
HRDCNT: o
SOFPAS: o
HRDPAS: o
SYSCNT:
RANNUM: o
RESl :
o
RES2:
o
SVRO:
OPEN
SVRl :
OPEN
SVR2:
OPEN
SVR3:
OPEN
SVR4:
OPEN
SVR5:
OPEN
SVR6:
OPEN
CSRA:
OPEN
SSADR:
ACSR:
OPEN
WASADR:
ASTAT:
OPEN
ERRTYP:
ASS:
OPE.N
A~;JAS:
OPEN
RSTRT:
RESTRT
HUT:

;STATUS WORD.
;MODULE START ADDR.
;MODULE STACK POINTER.
;PASS COUNTER.
;# OF ITERATIONS PER PASS=S12.
;LOC TO COUNT ITERATIONS
;LOC TO SAVE TOTAL SOFT ERRORS
;LOC TO SAVE TOTAL HARD ERRORS
;LOC TO SAVE SOFT ERRORS PER PASS
;LOC TO SAVE HARD ERRORS PER PASS
;# OF SYS ERRORS ACCUMULATED
;HOLDS RANDOM # WHEN RAND ~ACRO IS CALLED
;RESERVED FOR MONITOR USE
;RESERVED FOR MONITOR USE
;LOC TO SAVE RO.
;LOC TO SAVE Rl.
;LOC TO SAVE R2.
;LOC TO SAVE R3.
;LOC TO SAVE R4.
;LOC TO SAVE RS.
;LOC TO SAVE R6.
;ADDR OF CURRENT CSR.
;AODR OF GOOD DATA, OR
;CONTENTS OF CSR.
;ADDR OF BAD DATA, OR
;STATUS REG CONTENTS.
;TYPE OF ERROR
;EXPECTED DATA.
;ACTUAL DATA.
;RESTART ADDRESS AFTER END OF PASS

Page 44

APPENDIX B
000114 1
000116 1
000120 1
000122 1
000124 1
000126 1
000130 1
000132 1
000134 1
000136 1
000140 1
000142 1
000144 1
000146 1
000150 1

000252 1

000000
000000
000000
000005
002560 1
000000
000000
000400
000000
000000
002000
000000
000000
000000
000000
000040

WOTO:
IfJDFR:
INTR:
IONUM:
RBUFVA:
RBUFPA:
RBUFEA:
RBUFSZ:
WBUFPA:
IfJ8UFEA:
WBUFRQ:
WBUFSZ:
CDERCT:
CDWDCT:
FREE:

OPEN
OPEN
OPEN
5

SUFIN
OPEN
OPEN
256.

OPEN
OPEN
1024.

OPEN
OPEN
OPEN
OPEN
• REPT
• N LI 5T
.If'JORD
.LIST
.ENDR

SPSIZ

;WORDS TO MEMORY PER ITERATION
;WORDS FROM MEMORY PER ITERATION
;# OF INTERRUPTS PER ITERATION
;MODULE IDENTIFICATION NUMBER=5
;READ BUFFER VIRTUAL ADDRESS
;READ BUFFER PHYSICAL ADDRESS
;READ BUFFER EA BITS
;SIZE OF,THE READ SUFFER
;WRITE BUFFER PHYSICAL ADDRESS
;WRITE BUFFER EA BITS
;WRITE SUFFER SIZE REQUESTED
;WRITE BUFFER SIZE AVAILABLE
;CDATA/DATCK ERROR COUNT
;CDATA/DATCK WORD COUNT
;RESERVED FOR FUTURE USE
;MODUlE STACK STARTS HERE •

MOOSP:

;***********************************************************************

Page 45

APPENDIX 8
RKAA DEC/X11 SYSTEM EXERCISER MODULE
RKAA.P11
13-MAR-78 00:00
207
209 000256' 012767 000400 177630
210 000264' 012767 002000 177624
211
000272' 012767 000003 177620
212 000300' 005067 003534
213 000304' 005067 002210
214 000310' 016767 177500 002214
215 000316' 016767 002210 002210
216 000324' 012767 177775 002210
217 000332' 005067 002200
218 000336' 012767 160000 002174
219 000344' 122737 000002 000041
220 000352' 001006
000000
012701
221
113700 000040
222
12701
223
000001
105700
224
001404
225
006301
105300
005202
000772
130167 002150
001404
010267 002146
004767 000716
224
225 000370' 012767 177777 002140
226 000376' 004767 001576
227. 000402' 004767 001774
228 000406' 005767 002120
229 000412' 001536
230 000414' 000404
231
000416' 005767 002100
232 000422' 001001
233 000424' 000712
234 000426'
235 000426' 104415 000000' 000124 1
236 000434' 016767 177472 002112
237 000442 ' 005467 002106
238
239 000446' 004767 000676
240 000452' 104414 000000'
241
000456' 016767 177460 002066
242 000464' 005467 002062
243 000470' 016700 002046
244 000474' 004767 001600
245
246 000500' 004767 001022
247 000504' 005767 002022
248 000510' 001477
249 000512' 132767 000010 003321
250 000520' 001352
251
000522 1 042767 160000 002000

MACY11 30A(1052)
START:

MOV
MOV
MOV
C LI~
C L1~

MOV
MOV
MOV
C L1~

MOV
CMPB
BNI::
MOV
MOV8
MOV
1 $:

2$:

BEQ
ASIL
DEC8
INC
BR
BI TB
BEQ
MOV
JSli

1$:

MOV
JSI~

JSFl
TST
BE(~

20-MAR-78

15:47

#256. ,WDTO
WORDS TO MEM
#1024.,WDFR
WORDS FROM M,EM
#3,INTR
# OF1NTERRURrS/ITERATION
SIDE
CLEAR FLAGS A~D SIDE INDICATOR
DLTCNT
CLEAR DATA LATEEROR COUNTER
DVID1,DVICE
GET DRIVE INDICATOR
ALSO SAVE IT IN DRIVE
DVICE,DRIVE
#-3,BLK1
INITIALIZE BLOCK COUNTER
DRYVE
ZERO UNIT NUMBER
#160000,DRVSFT
INITIALIZE THE SHIFTED DRIVE #
#BIT1,@l#41
IS RK UNIT G THE LOAD MEDIUM?
NO, CONTINUE
3$
; INITIALIZE DRIVE COUN'r
#0.R2
@#40,RO ; GET LOAD MEDIUM COUNT
# 1 ,R 1
: LOAD UP R1 TO POINT TO DRIVE 0
TST8
RO
;IF RO EQUAL TO 0 THEN
2$
;GO TO 2$
R1
;ELSE UPDATE DRIVE POINTER
RO
; DECREr,~ENTCOUNT
R2
; UPDATE DRIVE NUMBER
1$
;TRY AGAIN
R1.DVICE
;IF DRIVE NOT SELECTED TO BE TESTED THEN
3$
;GO TO 3$
R2.DRYVE
;ELSE LOAD DRIVE ADDRESS TO BE DROPPED
;GO DROP IT
PC,DROP
#-1,DRYVE
PC, SETUP
PC. REZET
DVICE
FINI
RSTRT1
PASCNT
RSTRT1
START

INITIALIZE DRIVE COUNTER
GENERATE REGISTER ADDRESSES
INITIALIZE RK REGS. AND ALL DRIVES
DROP THE MODULE ?
YES
;+
/ THIS IS
;+
/
SUPPORT
;+ /
FOR
;+ /
OT03
;+/
BUS SWITCH
;GET PHYSICAL ADDRESS FROM 16-61T RBUFVA
SAVE READ BUFFER SIZE
; GET THE 2'S COMPLEMENT

PC,BLOCK
BEGIN
WBUFSZ,WCNT1
WCNT1
BLK1,RO
PC,CONVRT

; GET NEXT BLOCK NUMBER
;GET WRITE BUFFER INFORMATION
SAVE WRITE BUFFER SIZE
GET THE 2'5 COMPLEMENT
LOAD BLOCK # FOR CONVRT
GENERATE DISK ADR. FROM BLOCK #

GR
RESTRT: TS'r
8NI::
8R
RSTRT1:
GETPA$,BEGIN, RBUFVA
MOV
RBUFSZ,WCNT2
NEG
WCNT2
STRT:

JSR

GWI3UF$ ,
MOV
NEG
MOV
JSI~

JSI~

TST
BEQ
BITB
BNI:.
BIG

PAGE 7

PC,DRVADR
DVICE
FINI
#BIT3,FLAG
STRT
#160000,DSKADR

GET A DRIVE ADDRESS
ANY DRIVES LEFT ?
NO, GO DROP THE MODULE
ALL DRIVES DONE ?
YES, GO GET ANOTHER BLOCK
CLEAR DRIVE ADDRESS

APPENDIX B
252
253
254
255
256
257
258
259
260
261
262
263
264

000530 1 056767
000536 1 016777
000544' 032777
000552 1 001406
000554 1 004767
000560 1 104403
000566 1 000744
000570 1 032777
000576 1 001003
000600 1 004767
000604 1 000720
000606 1 005067
0006121 105067

002004
001766
000040

001772
003030
003010

000526
000000 1 004014 1
000100

002764

1$:

001014
003230
003226

2$:

DRVSFT,DSKADR
LOAD DRIVE ADDRESS
BIS
DSKADR,@RKDA
LOAD DISK ADDRESS
MOV
#BIT5,@RKDS
WRITE PROTECTED?
BIT
1$
NO, CONTINUE
BEC)
PC,DROP
YES, DROP THE DRIVE
JSH
MSGN$,BEGIN,DRP ;ASCII MESSAGE CALL WITH COMMON HEADER
NEXT
GO ON TO NEXT DRIVE
BR
#BIT6,@RKDS
DRIVE READY ?
BIT
2$
Y£:S, CONTINUE
BNE
NO, llJAIT FOR READY
PC,NOTRDY
JSn
STRT
TRY AGAIN
BR
TRY1
ZERO RETRY COUNTERS
CLH
TRY3
CLF~B

Page 46

Page 47

APPENDIX B
RKAA DEC/Xl1 SYSTEM EXERCISER MODULE
RKAA.P11
13-MAR-78 00:00
265
266
267 000616 1 004567 000212
268 0006221 000434
269 000624 I 132767 000004 003207
270 000632 1 001407
000634 I 142767 000004 003177
271
272 0006421 012767 177775 001672
273 000650 1 000676
274 000652 1 004567 000210
275 000656 1 000430
276 000660 1 004567 000234
277 000664 1 000437
278 000666' 104412 000000' 000126'
279 000674' 000676 1
280
281
283 000702'
284 000702' 104413 000000'
285
286 000706' 000674
287
288 000710'
289 000710' 104410 000000'
290
291
292
293
294 000714' 105267 003122
295 000720' 122767 000003 003114
296 000726' 001333
297 000730' 104403 000000' 003772'
298 000736' 000423
299
300 000740 1 105267 003077
301
000744' 122767 000003 003071
302 000752 1 001337
303 000754' 104403 000000' 004000'
304 000762 1 000411
305
306 000764' 105267 003054
307 000770 1 122767 000003 003046
308 000776' 001330
309 001000' 104403 000000' 004006'
310
311
001006' 032767 000001
177002
312 001014 1 001405
313 001016' 004767 000264
314 001022' 104403 000000' 004014'
315 001030' 000167 177444
316

MACY11 30A(1052)

GO:

GOA:
GOB:

20-MAR-78

R5, ItJR I TE
RETRYl
#BIT2,FLAG
GOA
#BIT2,FLAG
#-3,BLKl
STRT
RS,WRITCK
RETRY2
JSI~
R5, READ
BR
RETRY3
CDATA$,BEGIN,RBUFPA
.+:2
JSI~

BR
BITB
BEq
BICB
MOV
BR
JSR
BR

15:47

PAGE 9

WRITE SOME DATA
IF ERRORS, TRY IT AGAIN
DID THE DISK OVERFLOW?
NO, CONTINUE
YES, CLEAR THE OVERFLOW FLAG
RESET THE BLOCK NUMBER
START OVER AT BEGINNING OF DISK
WRITE-CHECK THE DATA
IF ERRORS, TRY AGAIN
READ THE DATA WRITTEN
IF ERRORS, TRY AGAIN
REQUEST FOR MONITOR TO CHECK DATA
IF ERROR, CONTINUE

PASS:
ENIJIT$.BEGIN
BR

;SIGNAL END OF ITERATION.
;MONITOR SHALL TEST END OF PASS

FINI:
END$,BEGIN

DROP THE MODULE

TRY1
RETRY1: INCB
·CMPB
#3,TRYl
BNI:::
GO
MSGN$,BEGIN,EXCEDl
BR
NEXTA

; COUNT THE RETRYS
; LIMIT EXCEEDED?
• NO, GO TRY IT AGAIN
;ASCII MESSAGE CALL WITH COMMON HEADER
GO ON TO NEXT DRIVE

RETRY2: I NCB
TRY2
#3,TRY2
CMPB
GOA
BNI:::
MSGN$,BEGIN,EXCED2
BR
NEXTA

; COUNT RETRYS
; LIMIT EXCEEDED ? .
• NO, TRY AGft.IN
;ASCII MESSAGE CALL WITH COMMON HEADER
GO ON TO NEXT DRIVE

RETRY3: INCB
TRY3
CMPB
#3,TRY3
BNI:::
GOB
MSGN$,BEGIN,EXCED3

; COUNT RETRYS
; LIMIT EXCEEDED ?
; NO, GO TRY AGAIN
;ASCII MESSAGE CALL WITH COMMON HEADER

NEXTA:

"1$:

BIT
#BITO,SRl
; DROP THE DRIVE?
BEQ
1$
; NO, SKIP TO NEXT DRIVE
JSR
PC,DROP
: YES, DROP OFFENDING DRIVE
MSGN$,BEGIN,DRP ;ASCII MESSAGE CALL WITH COMMON HEADER
JMP
NEXT
GO ON TO NEXT DRIVE

Page 48

APPENDIX B
RKAA DEC/X11 SYSTEM EXERCISER MODULE
RKAA.P11
13-MAR-78 00:00
317
318
319
320
321
001034' 012767 000503 001462
322 001042' 016777 001504 002520
323 001050' 016777 177060 002514
324 001056' 016767 177054 001442
325 001064' 000462
326 001066~ 012767 000507 001430
327 001074' 016777 001452 002466
328 001102' 016777 177026 002462
:32e 001110' 016767 177022 001410
330 001116' 000445
331
001120' 012767 000505 001376
332 001126' 016777 001422 002434
333 001184' 016777 176766 002430
334 001142' 016767 176762 001356
335 001150' 000430
336
337 001152' 012777 000001
002406
338 001160' 004767 001260
339 001164' 016777 001350 002402
340
001172' 032777 000100 002362
341
001200' 001001
342 001202' 000205
343 001204' 012777 000015 002354
344 001212' 004767 000530
345 001216' 012777 000001
002342
346 001224' 004767 001214
347 001230' 000205
348
349 001232' 012777 001266' 176550
350 001240' 016777 001264 002326
351
001246' 056767 001254 001250
352 001254' 016777 001244 002304
353 001262' 104400 000000'
354
355 0012.66'
356
357 001266' 000004 000000' 001274'
358
359
360
001274' 004567 000516
361
001300' 000205
362 001302' 005725
363 001304' 000205
364

MACY11 30A(1052)

20-MAR-78

15:47

PAGE 10

RK11 DISK DRIVERS
WRITE:

MOV
MOV
MOV
MOV
BR
~m I TCK: MOV
MOV
MOV
MOV
ElR
READ:
MOV
MOV
MO\!
MOV
BR

CLEAR:

MOV
JSf~

MOV

BIT
81\E

2$:

RTS
MOV
JSI~

MOV
JSI~

RTS
GOGO:

NTRUPT:

#503,FUNC
~vCNT 1 , @RK~vC

WBUFPA,@lRKBA
WBUFEA,XMEM
GOGO
#507,FUNC
t>JCNT 1 ,@RKWC
WBUFPA,@lRKBA

W6UFEA,XMEM
GOGO
#505,FUNC
WCNT2,@RKWC
RBUFPA,@lRKBA
RBUFEA,XMEM
GOGO
#1 ,@RKCS
PC,WAIT1
DRVSFT ,@lRI{DA
#BIT6,@lRKDS
2$
R5
#15,@RKCS
PC,WAIT
#1,@lRKCS
PC,WAIT1
R5

MOV
#NTRUPT,@lVECTOR
MOV
DSKADR,@RKDA
BIS
XMEM,FUNC
MOV
FUNC,@lRKCS
EXIT$,BEGIN

LOAD WRITE FUNCTION
LOAD WORD COUNT
LOAD BUFFER .ADDRESS
LOAD EXTENDED MEMQRY BITS
CONTINUE
LOAD WRITE-CHECK FUNCTION
LOAD WORD COUNT
LOAD BUFFER ADDRESS

LOAD ExT~NCED MEMORY 6ITS
CONTINUE
LOAD READ FUNCTION
LOAD WORD COUNT
LOAD BUFFER ADDRESS
LOAD EXTENDED MEMORY BITS
CONTINUE
ISSUE A CONTROL RESET
GO WAIT FOR CONTROLLER READY
RELOAD THE DRIVE ADDRESS
DR I VE REf-.DY ?
YES, CONTINUE
NO, ABORT DRIVE RESET.
ISSUE A DRIVE RESET
GIVE IT TIME TO COMPLETE
ISSUE ANOTHER CONTROLLER RESET
WAIT FOR CONTROLLER READY
RETURN
SET INTERUPT ENTRY POINTER
LOAD THE DISK ADDRESS
LOAD EXTENDED MEMORY BITS
EXECUTE THE FUNCTION
;EXIT TO MONITOR. MODULE WAIT FOR INTERRUPT.

,
._--------------------------------------------------------------; QUEUE UP TO CONTINUE AT 1$ AND RTI

PIRQ$,BEGIN,1$

; -.----------------------.~----------------------.

1$:

JSf~

RTS
TST
RTS

R5,ERRORS
R5
(R5)+
R5

----.-------------

GO CHECK FOR ERRORS
ERRORS DETECTED, RETURN
NO ERRORS, SKIP RETRY
RETURN OK

Page 49

APPENDIX B
RKAA DEC/X11 SYSTEM EXERCISER MODULE
RKAA.P11
13-MAR-78 00:00
365
366
000001
367 001306' 012701
368 001312' 016700 001220
369 001316' 001403
370 001320' 006301
371
001322' 005300
372 001324' 001375
373 001326' 040167 001200
375
376
377
~7B

001J3G'

1044~O

319

001~441

004030

380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
41:2
413
414
415
416
417
418
419

000000'

MACY11 30A(1052)

DROP:

MOV
MOil
BE(~

1$:

2$:

ASL
DEC
BNt:.
BIC

20-MAR-78

# 1 ,R 1

DRYVE,RO
2$
R1
RO
1$
R1,DVICE

15:47

PAGE 11

INITIALIZE DROP PICKER
GET THE DRIVE NUMBER
IF DRIVE 0 GO DROP IT
NO, AIM AT THE NEXT DRIVE
IS THIS THE ONE?
NO, LOOK AGAIN
DROP THE DRIVE

;***************************************************************
;CONVERT DRYVE TO ASCII AND
;~TORE AT ADR1

gQ~iJQ'

;**************************************************************

001346' 000207

RTS

RETURN

#3,BLK1
#4799.,BLK1
1$
BLK1
BLK1,BLK2
PC

STEP TO NEXT BLOCK
BLOCK LIMIT REACHED ?
NO, CONTINUE
YES, RESET BLOCK #
READ WHERE WRITE
RETURN

BLK1,RO
#2399. ,R1
R2
#2399.,RO
1$
#2400. ,RO
#256.,BSIZ
#BIT11,@lRKDS
2$
BSIZ
RO,R1
BSIZ,R2

SAVE THE CURRENT BLOCK NUMBER
LOAD MAX. NUMBER OF BLOCK PER SIDE
ZERO REG. 2
IS SIDE 0 DONE?
NO, CONTINUE
YES, NORMALIZE BLOCK # FOR SIDE 1
HI DENSITY BLOCK SIZE
HI DENSITY DRIVE?
YES, CONTINUE
NO, SET TO 128 -- LO DENSITY
GET # OF BLOCKS LEFT ON DISK
GET TOTAL NUMBER OF WORDS LEFT
ALL BLOCKS ADDED IN ?
NO, KEEP ADDING
IS # OF WORDS LEFT ON DISK NEG. ?
YES
IS TRANSFER SIZE NEG. ?
YES
NO, GO COMPARE
IS TRANSFER SIZE POS. ?
YES
WAS THERE ENOUGH ROOM FOR THE TRANSFER ?
NO, RETURN OK
YES, MUST BE A R~ALERROR
RETURN. ERROR
SET OVERFLOW FLAG

001350'
001356 1
001364 1
001366 1
001372 1
001400 1

062767
022767
100002
005067
016767
000207

000003
011277

001164
001156

BLOCK:

ADD
CMP
BPIi.

001150
001144

001144

1 $:

MOV
RTS

001402'
001406'
001412'
001414'
001420'
001422'
001426'
001434'
001442'
001444'
001450'
001452'
001456'
001460'
001462'
001464'
001466'
001472'
001474'
001476'
001502'
001504'
001510'
001512'
001514'
001516'

016700
012701
005002
022700
002002
162700
012767
032777
001002
006267
160001
066702
005301
003374
005702·
100404
005767
1 00411
000403
005767
100003
020267
002402
005725
000205
152767

001134
004537

ROOM:

MOV
MOV
CLH
CMF>

CLI~

004537

BGE.

004540
000400
004000

001112
002120

1$:

001076
2$:
3$:

001070

176450
4$:

176440
176432

000004

002315

7$:

SUI3
MOV
BIT
BNI:.
ASli
SUI3
ADD
DEC
BGT
TST
BMI
TST
BMI
BR
TST
BPt
CMIP
BLT
TST
RTS
BISB

3$
R2
4$
WBUFSZ
7$
5$

WBUFSZ
6$
R2, ~'JBUFSZ
7$
(R5)+
R5
. #BIT2.FLAG

APPENDIX 8
420

001524 1 000205

RTS

Page 50

RETURN OK

Page 51

APPENDIX B
RKAA DEC/Xl1 SYSTEM EXERCISER MODULE
13-MAR-78 00:00
RKAA.Pl1
421
422
423
424 001526 1 005267 001004
425 001532 1 062767 020000 001000
426 001540 1 142767 000010 002273
427 001546 1 022767 000010 000762
428 001554 1 001404
429 001556 1 006267 000752
430 001562 1 103361
431
001564 1 000207
432
433 001566 1 152767 000010 002245
434 001574 1 012767 177777 000734
435 001602 1 012767 160000 000730
436 001610 1 016767 0007 ·16 000716
437 001616 1 000207
438
439
440
441
001620 1 012767 177777 000710
442 001626 1 012767 160000 000704
443 001634 1 016767 000672 000672
444 001642 1 004767 177660
445 001646 1 132767 000010 002165
446 001654 1 001012
447 001656 1 016777 000656 001710
448 001664 1 032777 000100 001670
449 001672 1 001363
450 001674 1 004767 000046
451
001700 1 000760
452 001702 1 000207
453
454
455
456 001704 1 014167 176176
457 001710 1 010167 176166
458 001714 1 014267 176170
459 00i720 1 010267 176160
460 001i24 1 005721
461
001726 1 005722
462
463 001730 1 016767 001632 176142
464 001736 1 017767 001624 176136
465 001744 1 000207
466

MACY11 30A(1052)

DRVADR: INC
ADD
BICB
CMP
BEQ
ASf~

BCC
RTS
BISB

MOV
MOV

MOV
RTS

20-MAR-78

15:47

DRYVE
#BIT13,DRVSFT
#BIT3,FLAG
#8. ,DRYVE

PAGE 12

DRIVE
DRVADR
PC

COUNT A DRIVE
DRIVE COUNT LINED UP WITH RKDA
CLEAR END OF DRIVES FLAG
ALL DRIVES CHECKED ?
YES, GO FLAG END OF DRIVES
NO, IS NEXT DRIVE CHOSEN?
NO, GO TRY ANOTHER DRIVE
RETURN

#BIT3,FLAG
#-1,DRYVE
#160000,DRVSFT
DVICE,DRIVE
PC

SET END OF DRIVES FLAG
RESET DRIVE COUNTER
ZERO THE SHIFTED DRIVE #
RESTORE CHOSEN DRIVES
RETURN

--------~--~-------------

NOTRDY: MOV

MOV
MOV

lI-t,DRYVE
#160000,DRVSFT
DVICE,DRIVE
PC,DRVADR
# g(T3, FLAG

START WITH FIRST DRIVE

RESET DRIVE SELECT
GET A DRIVE ADDRESS
ALL DRIVES CHECKED ?
YES, RETURN
NO, LOAD NEXT DRIVE ADDRESS
IS THIS DRIVE READY?
YES, CONTINUE
NO, vJAIT FOR IT
GO CHECK REST OF DRIVES
RETURN

TST

-(R1),ASB
R1,SBADR
-(R2),AWAS
R2,WASADR
(R 1 ) +
(R2)+

LOAD THE DATA
LOAD ADDRESS OF DATA WRITTEN
LOAD THE DATA
LOAD ADDRESS OF DATA READ
RESET REG. 1
RESET REG. 2

ERSUB1: MOV
MOV
RTS

RKCS,CSRA
@RKCS,ACSR
PC

LOAD ADR. OF CURRENT CSR
LOAD CONTENTS OF CURRENT CSR
RETURN

1$:

JSI~

BITB
BNE
MOV
BIT
BNI:
JSH

2$:

BR
RTS

ERSUB2: MOV
MOV
MOV
MOV
TST

DRVSFT,@RKDA
.#BIT6,@RKDS
1$

.' . PC, WA I T
1$

APPENDIX B
RKAA DEC/X11 SYSTEM EXERCISER MODULE
RKAA.P11
13-MAR-78 00:00
4.67
468
469
470
471
001746' 012767 077777 001604
472 001754'
473 001754' 104407 000000'
474 001760' 104407 000000'
475 001764' 032777 000100 001570
476 001772' 001010
477 001774' 005367 001560
478 002000' 001365
479 002002' 004767 177300
480 002006 1 104403 000000' 004014'
491
002014' 000207
482
483 002016' 004767 177706
484 002022' 032777 040000 001536
485 002030' 001006
486 002032' 032777 000003 001524
487 002040' 001041
488 002042' 005725
489 002044' 000205
490 002046' 032777 040000 001510
491
002054' 001403
492 002056' 004567 177320
493 002062' 000442
494 002064' 032777 001000 001472
495 002072' 00141 1
496 002074' 005267 000420
497 002100' 032767 000004 175710
498 002106' 001013
499 002110' 104403 000000' 004024 1
500 002116'
501
002116' 104403 000000' 003762 1
502 002124' 005067 175756
5G3
504 002130 1 104405 000000 ' 003562 1
505
506 002136' 004567 177010
507 002142' 000411
508 002144'
509 002144' 104403 000000' 003766 1
510 002152' 012767 000001
175726
511
512 002160' 104406 000000' 003562'
513
514 002166' 000205
515 002170' 004567 176756
516 002174' 005725
517 002176' 000205
518

MACY11 30A(1052)

WAIT:

MOV

Page 52
20-MAR-78

#77777,CLK

15:47

PAGE 14

; SET THE TIMER

1 $:

2$:

BREAK$,BEGIN
;TEMPORARY RETURN TO MONITOR .•.•
BREAK$,BEGIN
;THEN CONTINUE AT NEXT INSTRUCTION.
BIT
#BIT6,@RKDS
DRIVE READY ?
BNi:
2$
YES, RETURN
DEC
ClK
; NO, WAIT SOME MORE?
BNE
1$
; YES, WAIT
JSH
PC,DROP
; tIME-OUT, DROP THE DRIVE
MSGNS,BEGIN,DRP ;ASCII MESSAGE CALL WITH COMMON HEADER
RETURN
RTS
PC

ERRORS: JSR
BIT
BNt:
BIT
BNI:
TST
RTS
1$:
BIT

7$ :

PC,ER5UB1
#BIT14,@RKCS
1$
#3,@RKER
3$
(RS)+
RS
#BIT14,@RKER
BE(~
7$
JSH
RS,ROOM
BR
5$
BIT
#BIT9,@RKER
SEQ
2$
INC
DLTCNT
BIT
#BIT2,SR1
BNI:
6$
MSGN$,BEGIN,DLTERR

lOAD ERROR INFORMATION
HARD ERROR ?
YES, GO REPORT
SOFT ERROR ?
YES, GO REPORT
NO, SKIP RETRY
RETURN 01<
DISK OVERFLOW'?
NO, CONTINUE
YES, IS IT A REAL ERROR?
NO, CONTINUE
;DATA LATE ERROR?
;NO
;INCREMENT ERROR COUNTER
;TYPE OUT ERROR?
iNO
;ASCII MESSAGE CALL WITH CbMMON HEADER

MSGN$,BEGIN,HARD
CLI<
ERRTYP

;ASCII MESSAGE CALL WITH COMMON HEADER

2$:
;******************************~********************************

HRDER$,BEGIN,TABLE
6$:

;

;***************************************************************

JSR
BR

R5,CLEAR
4$

; GO CLEAR OUT ERRORS
; RETURN

3$:
MSGN$,BEGIN,SOFT
MOV
#1,ERRTYP

;ASCII MESSAGE CALL WITH COMMON HEADER
; DATA ERROR

;**************~*************************************************

SOFER$,BEGIN,TABLE
4$:

5$:

;****************************************************************

RTS
JSR
TST
RTS

R5
R5,CLEAR
(R5)+
R5

RETURN, ERRORS
CLEAR OUT ERRORS
SKIP RETRY
RETURN OK

Page 53

APPENDIX B
RKAA DEC/X11 SYSTEM EXERCISER MODULE
13-MAR-78 00:00
RKAA.P11
519
520
521
002200 1 016700 175602
522 002204 1 010067 001352
523 002210 1 005720
524 002212 1 010067 001346
525 002216 1 005720
526 002220 1 010067 001342
527 002224 1 005720
528 002226 1 010067 001336
529 002232 1 005720
530 002234 1 010067 001332
531
002:240 1 005720
532 002:242' 010067 001326
533 002246 1 005720
534 002250 1 010067 001322
535 002254 1 005720
536 002256 1 010067 001316
537
538 002262 1 016700 175522
539 002266 1 012720 000446 1
540 002272 1 116710 175514
541
542 002276 1 000207
543
544
545
546 002300 1 005001
547 002302 1 105067 001532
548 002306 1 012703 177764
549 002312 1 012704 000013
550 002316 1 022700 004537
551
002322 1 002005
552 002324 1 '152767 000020 001506
553 002332 1 062700 173240
554 002336 1 020400
555 002340 1 002003
556 002342 1 060300
557 002344 1 005201
558 002346 1 000773
559 002350 1 010067 000154
560 002354 1 156767 001460 000146
561
002362 1 012702 000005
562 002366 1 006301
563 002370 1 005302
564 002372 1 003375
565 002374 1 050167 000130
566 002400 1 000207
567

20-MAR-78

MACY11 30A(1052)

SETUP:

2$:

~.DOR, RO

MOV
MOV
MOVB

VECTOR,RO
#STRT,(RO)+
BR 1 , ( RO)

GET THE VECTOR ADDRESS
SET POINTER JUST IN CASE
SET PRIORITY

3$ :

GET DEVICE ADDRESS
GENERATE CONTROLLER REGS. ADDRESSES

RTS

RETURN

R1
SIDE
#-12.,R3
#11.,R4
#2399.,RO
1$
HBIT4,SIDE
#-2400.,RO
R4,RO
2$
R3,RO
R1
1$
RO,DSKADR
SIDE,DSKADR
1t5,R2
R1
R2
3$
R1,DSKADR
PC

ZERO REG. 1
ZERO THE SIDE INDICATOR
LOAD REG. 3
LOAD REG. 4
IS BLOCK ON SIDE 0 ?
YES, CONTINUE
NO, FLIP TO SIDE 1
NORMALIZE BLOCK # FOR SIDE
FIND THE RIGHT CYLINDER ?
YES, CONTINUE
NO, SUBTRACT 1 2 SECTOF~S ( 1 CYLINDER)
KEEP TRACK OF CYLINDER ADDRESS
GO TRY AGAIN
LOAD THE SECTOR ADDRESS
LOAD THE SIDE ADDRESS
SET UP FOR SHIFT
LINE UP CYL. ADR. WITH DSKADR
DONE ?
NO. GO SHIFT AGAIN
YES, LOAD THE CYLINDER ADDRESS
RETURN

RO,RKOS
(RO)+
RO, R~(ER
(RO)+
RO,RKCS
(RO)+
RO,RKWC
(RO)+
RO,RKBA
(RO)+

RO,RKDA
(RO)+
RO,RKMR
( RO)+
RO,RKOB

--_.---------------------.cum

2..$:

PAGE 15

MOV
MOV
TST
MOV
TST
MOV
TST
MOV
TST
MOV
Tsr
MOV
TST
MOV
TST
MOV

CONVRT: CLH

1 $:

15:47

MOV
MOV
CMf'
BGE
elSB
ADD
CMP
BGE
ADD
INC
BR
MOV
elSB
MOV
ASL
DEC
BGT

BIS

_ _----------------_
RTS
......

...

Page 54

APPENDIX B
RKAA DEC/Xll SYSTEM EXERCISER MODULE
RKAA.Pl1
13-MAR~78 00:00
568 002402 1 012777 000001
001156
569 002410 1 004767 000030
1
570 002414 004767 177200
571
002420 1 004767 ;77102
572 002424' 132767 000010 001407
573 002432 1 001003
574 002434' 004567 176512
575 002440' 000767
576 002442' 000207
577
578
579
580 002444' 012767 077777 001106
581

00:2452' 105777

582
583
584
585
586
587
588
589
590
591
592
593
594
595
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
6·'3
614
615
616
617
618
619
620
621
622

002456' 100417
002460' 104407
002464' 104407
002470' 005367
002474' 001366
002476' 012767
002504'

104405

002512 1 000167
002516' 000207
002520'
002524'
002526'
002530'
002532'
002534 1
002536'
002540'
002542 1
002544'
002546'
002550'
002552'
002554'
002556'
002560'
003560'
003562'
003562'
003564'
003566'
003570'
003572'
003574'
003576'
003600'
003602'

000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000400
000400
000000
000000
000000
000000
000000
000000
000000
000000
000000
177777

MACY11 30A(1052)
REZET:

IVIO\l

1$:

JS1<
JSH
JSf(
BITB
BNI:
JSf~

2$:

#1 ,@RKCS
PC.WAIT1
PC,NOTRDY
PC,DRVADR
#BIT3,FLAG
2$
R5,CLEAR
1$
PC

175402

#77777.CLK
TSTB
@RKCS
8MI
2$
BREAK$,BEGIN
BREAKS,BEGIN
DEC
CLK
BNE
1$
MOV
#3,ERRTYP

000000' 003562'

HRDER$,8EGIN,TABLE

001110

WAIT1:
1$:

BR
RTS

20-MAR-78

000000'
000000'
001064
000003

MO\l

15:47

PAGE 16
EXECUTE CONTROLLER RESET
GO WAIT FOR CONTROLLER READY
MAKE SURE ALL CHOSEN DRIVES ARE READY
GET A DRIVE ADDRESS
ALL DRIVES DONE ?
YES, RETURN
ISSUE DRIVE RESET AND CONTROLLER CLEAR
KEEP GOING
RETURN

; SET THE TIMER
; CONTROLLER READY ?
; YES, CONTINUE
;TEMPORARY RETURN TO MONITOR ..•.
;THEN CONTINUE AT NEXT INSTRUCTION.
; WAIT SOME MORE ?
; YES
; CONTROLLER NOT READY

;***************************************************************
; CONTROLLER NOT READY

;***************************************************************

176172

JMP
FINI
GO DROP THE MODULE
RTS
PC
READY, RETURN
.... _-------------------_ ....

2$:

DLTCNT:
FUNC:
XMEM:
DS~~ADR :
DVICE:
DRIVE:
DRYVE:
DRVSFT:
BlK 1 :
BlK2:

0
0
0
0
0
0
0
0

BSIZ:
TBUF:
'tJCNT 1 :
WCNT2:
BUFlEN:
BUFIN:
ClK:
TABLE:
RKDS:
RKER:
RKCS:
Ri'(lt-JC:

RKBA:
RKDA:
RI\MR:

RKDB:

0
0
0

0
0
25€).
. BLKW
0
0
0

0
0
0
0
0
0
177771

256 •

Page 55

APPENDIX B
RKAA DEC/X11 SYSTEM EXERCISER MODULE
13-M/\R-78 00:00
RKAA.P11
623 003604' 020040 044040 051101
624 003612' 020104 051105 047522
625 003620' 000122
626 003622' 020040 051440 043117
627 003630' 020124 051105 047522
628 003636' 000122
629 003640' 020040 051104 053111
630 003646' 020105 000040
631
003652' 020040 051104 050117
000
632 003660' 042520 022504
040 042522 051124
633 003665'
054105 042503
634 003672' 020131
635 003700' 042105 042105 000045
636 003706' 053440 044522 042524
000
637 003714'
040 051127 052111
638 003715'
639 003722' 026505 044103 041505
640 003730' 000113
641
003732' 051040 040505 000104
642 003740' 040504 040524 046040
643 003746' 052101
020105 051105
644 003754' 047522 022522
000
003762'
645
646 003762' 003604'
647 003764' 177777
648 003766' 003622'
649 003770' 177777
650 003772' 003706'
651
003774' 003665'
652 003776' 177777
653 004000' 003715'
654 004002' 003665'
655 004004' 177777
656 004006' 003732'
657 004010' 003665'
658 004012' 177777
6S9 004014' 003640'
660 004016' 004035'
661
004020' 003652'
662 004022' 177777
663 004024' 003740'
664 004026' 177777
665 004030' 000005
000
666 004035'
667 004036' 000000
000
668 004040'
000
669 004041 '
670
000
671
004042'
000
672 004043'
000
673 004044'
004046'
674
675
000001
676

20-MAR-78

MACY11 30A(1052)

15:47

MES1:

.ASCIZ

HARD ERROR'

MES2:

.ASCIZ

SOFT ERROR'

MES4:

.ASCIZ

DRIVE

MESS:

.ASCIZ

DROPPED%'

MES6:

.ASCIZ

, RETRY EXCEEDED%'

MES7:

.ASCIZ

, WRITE'

MESa:

.ASCIZ

, WRITE-CHECK'

MES9:
MES10:

.ASCIZ
.ASCIZ

HARD:
SOFT:
EXCED1 :
EXCED2:
EXCED3:
DRP:

DLTERR:
ADR1 :
NUMB:
SIDE:
FLAG:
TRY1
TRY2
TRY3

, READ'
'DATA LATE ERROR%'

.EVEN
ME!>1
177777
MES2
177777
MES7
MES6
177777
MEsa
MES6
177777
MES9
MES6
177777
MES4
NUMB
MES5
177777
MES10
177777

.BLKS
.BYTE
.WORD
.BYTE
.BYTE
.EVEN
.BYTE
.BYTE
.BYTE
.EVEN
.END

5
0
0

0
0
0
0
0

PAGE 17

Page 56

APPENDIX B
RKAA DEC/X11 SYSTEM EXERCISER MODULE
13-MAR-78 00:00
RKAA.P11
178#
464*
ACSR
000102R
145#
521
ADDR
000006R
665#
378
ADR1
004030R
182#
456*
ASB
000106R
180#
ASTAT
000104R
183#
458*
AWAS
000110R
142#
235
BEGIN
OOOOOOR
378
473
207#
221
BITO
000001
207#
219
BIT1
000002
207#
B1T10
002000
207#
401
BIT 11
004000
207#
B1 T12
010000
207#
425
BIT13
020000
207#
484
B1T14
040000
207#
BIT15
100000
207#
BIT2
269
000004
207#
249
BIT3
000010
207#
552
BIT4
000020
207#
254
BITS
000040
207#
259
BIT6
000100
207#
BIT7
000200
207#
BIT8
000400
207#
494
BI T9 .
001000
243
BlK1
216*
002542R
605#
BlK2
389*
002544R
385#
239
BLOCK
001350R
207#
473
BREAK$= 104407
147#
540
BR1
000012R
148#
BR2
000013R
BSIZ
400*
403*
002546R
207#
BTOD$
104421
611#
189
BUFIN
002560R
610#
BUFLEN 002556R
207#
CDATA$= 104412
278
197#
CDERCT 000144R
198#
CDWDCT 000146R
337#
506
CLEAR
001152R
elK
471*
477*
003560R
231
CNT
208*
002522R
546#
244
CONVRT 002300R
176#
CSRA
463*
000100R
207#
DATCK$= 10441 1
207#
DATER$= 104404
DLTCNT 002520R
496*
213*
663#
DLTERR 004024R
499
DRIVE
215*
429*
002534R
223
256
DROP
001306R
314
257
ORP
004014R
424#
246
DRVADR 001526R
252
DRVSFT 002540R
218*
DRYVE
217*
225*
002536R
DSKADR 002530R
251*
252*
215
DVICE
214*
002532R

MACY11 30A(1052) 20-MAR-78 15:47 PAGE 19
CROSS REFERENCE TABLE -- USER SYMBOLS

257
480

278
499

284
501

271
426

419
433

497
445

572

340

448

475

272*

:385*

386

474

!583

584

405

(306#

515
580*
282*

!j74
!j85*
!j96#

240
474
311

289
504

297
509

303
512

388*

389

394

604#

442*
427
560*
373*

447
434*
565*
.436

603#
441*
5,99#
443

490

612#

595#
436*
313
480
430
339
368
253
221

443*
:367#
659#
444
425*
:374
:350
:228

601#
479
571
435*
424*
559*
247

602#
600#

309
583

314
584

353
589

357

APPENDIX 8
OVID1
000014R
ENOIT$= 104413

149#
207#

214
284

Page 57

APPENDIX B
RKAA DEC/Xl1 SYSTEM EXERCISER MODULE
13-MAR-78 00:00
RKAA.P11
207#
END$
289
104410
360
483#
ERRORS 002016R
181#
ERRTYP 000106R
502*
463#
ERSUB1
483
001730R
456#
ERSUB2 001704R
650#
297
EXCED1
003772R
653#
EXCED2 004000R
303
656#
EXCED3 004006R
309
207#
EXIT$
353
104400
229
248
FINI
000710R
FLAG
249
004041R
269
199#
FREE
000150R
FUNC
321*
002524R
326*
207#
GETPA$= 104415
235
267#
296
GO
000616R
274#
270
GOA
000652R
276#
308
GOB
000660R
325
330
GOGO
001232R
207#
240
GWBUF$= 104414
646#
HARD
501
003762R
162#
HRDCNT 000044R
207#
504
HRDER$= 104405
164#
HRDPAS 00OO50R
159#
ICONT
000036R
160#
ICOUNT 000040R
188#
IDNUM
000122R
200#
241
IMODX.= 000000
156#
INIT
0OO03CR
187#
INTR
000120R
211 *
207#
MAP22$= 104416
623#
MES1
646
003604R
642#
MES10
663
003740R
626#
648
MES2
003622R
629#
MES4
659
003640R
631#
661
MESS
003652R
633#
651
MES6
003665R
636#
650
MES7
003706R
638#
653
MES8
003715R
641#
656
MES9
003732R
143#
MODNAM OOOOOOR
157
205#
MODSP
000252R
207#
MSGN$
257
104403
207#
MSGS$
104402
207#
MSG$
104401
246#
NEXT
258
000500R
304
NEXTA
298
001006R
441#
261
NOTRDY 001620R
355#
NTRUPT 001266R
349
207#
NULL
000000
660
666#
NUMB
004035R
144
150
OPEN
000000
178
180
198
199
207#
OTOA$
378
104420

Page 58

MACY11 30A(1052) 20-MAR-78 15:47 PAGE 20
CROSS REFERENCE TABLE -- USER SYMBOLS
510*

~)87*

288#
271*

419*

426*

433*

331*

:351 *

352

597#

309

153
185

~591

445

572

669#

314

480

499

501

509

169
186

170
187

171
190

172
l' 91

17:3
193

302
335

:349#

589

654

~357

297

:303

286
311#
570

:315

151
182
207#

'152
183

174
194

175
196

176
197

APPENDIX B
PASCNT
PASS

000034R
000702R

'58#
283#

Page 59

Page 60

APPENDIX B
RKAA DEC/X11 SYSTEM EXERCISER MODULE
RKAA.P11
13-MAR-78 00:00
357
PIRQ$ = 000004
207#
POPSP = 005726
207#
POPSP2= 022626
207#
PRTY
000000
207#
207#
PRTYO
000000
148
PRTY1
000040
207#
PRTY2
000100
207#
PRTY3
000140
207#
PRTY4
000200
207#
207#
PRTY5
000240
147
PRTY6
000300
207#
PRTY7
000340
207#
PS
177776
207#

PSW
PUSH

• 177776
= 005746

PUSH2
RAND$
RANNUM
RBUFEA
RBUFPA
RBUFSZ
RBUFVA
READ
RESTRT
RES1
RES2
RETRY1
RETRY2
RETRY3
REZET
RKBA
RKCS
RKDA
RKDB
RKDS
RKER
RKMR
RKWC
ROOM
RSTRT
RSTRT1
SBADR
SETUP
SIDE
SOFCNT
SOFER$=
SOFPAS
SOFT
SPOINT
SPSIZ
SR1
SR2
SR3
SR4

024646
104417
000054R
000130R
000126R
000132R
000124R
001120R
000416R
000056R
000060R
000714R
000740R
000764R
002402R
003572R
003566R
003574R
003600R
003562R
003564R
003576R
003570R
0014.02R
000112R
000426R
000102R
002200R
004040R
000042R
104406
000046R
003766R
000032R
000040
000016R
000020R
000022R
000024R

MACY11 30A(1052)
20-MAR-78 15:47 PAGE 21
CROSS REFERENCE TABLE -- USER SYMBOLS

207#
207#
207#
207#
166#
191#
190#
192#
189#
276
184
167#

334
278
236
235
331#
231#

333

16~#

26m
275
277
. 227
323*
337*
253*
536*
254
486
534*
322*
394#
184#
230
177#
226
212*
161#
207#
163#
509
157#
1#
150#
151#
152#
153#

294#
300#

306#
568#
328*
343*
339*
621#
259

333*
345*
350*
340

401

490

494

!,24*

448
615#

620#
327*
492

332*

!528*

617#

!560

668#

232
457*
521#
547*

:352*
447*

618#
463
532*

234#
552*

512
648#
200
311

!530*

497

464
619#

484

526*

475

522*

614#

568*

58'1

616#

APPENDIX B
START
STAT

000252R
000026R

156
155#

208#

233

Page 61

Page 62

APPENDIX B
RKAA DEC/Xl1 SYSTEM EXERCISER MODULE
RKAA.Pl1
13-MAR-78 00:00
250
STRT
000446R
239#
SVRO
000062R
169#
SVRl
000064R
170#
SVR2
000066R
171#
SVR3
000070R
172#
SVR4·
000072R
173#
SVR5
000074R
174#
SVR6
000076R
175#
SYSCNT 000052R
165#
512
TABLE
003562R
504
TBUF
002550R
607#
TRPDFD= 000022
207#
294*
TRY1
004042R
263*
301
TRY2·
004043R
300*
TRY3
004044R
264*
306*
VECTOR 000010R
146#
349*
450
WAIT
001746R
344
346
WAIT1
002444R
338
WASADR 000104R
179#
459*
324
WBUFEA 000136R
194#
323
WBUFPA 000134R
193#
WBUFRQ 000140R
195#
241
WBUFSZ 000142R
196#
242*
WCNT1
002552R
241*
237*
WCNT2
002554R
236*
WDFR
000116R
186#
210*
WDTO
000114R
185#
209*
326#
WRITCK 001066R
274
321#
WRITE
001034R
267
XFLAG
000005R
144#
329*
XMEM
002526R
324*
611#
004046R
279

MACV11 30A(1052) 20-MAR-78 15:47 PAGE 22
CROSS REFERENCE TABLE -- USER SYMBOLS
262
273
539

589

613#

295
672#
307
538
471#
569

E571#

B73#
~;80#

329
328

410
322
332

413

334*
645#

:351
E565#

:327
E509#

415
608#

598#

674#

Page 63

APPENDIX 8
RKAA DEC/X1i SYSTEM EXERCISER MODULE
RKAA.P11
13-MAR-78 00:00
BKMOD
1#
BREAK
1#
472
583
BTOD
1#
CKDATA
1#
278
DATACK
1#
DATERR
1#
DFSEVN
1#
207
DSEVNT
1#
207
END
1#
288
ENDIT
1#
283
EQUATS
1#
207
EXIT
1#
353
GETPA
1#
235
GWBUFF
1#
240
HRDER
1#
503
SBa
10MOD
1#
10MODP
1#
1#
IOMODR
1#
136
IOMODX
1#
MAP22
1#
137
MODULE
1#
MSG
1#
257
MSGN
297
303
MSGS
1#
NBKMOD
1#
OTOA
1#
375
1#
PIRQ
355
1#
RAND
1#
SBKMOD
SOFER
1#
511
. ABS.
000000
000
004046

001

ERRORS DETECTED:
0
DEFAULT GLOBALS GENERATED: 0
RKAA,RKAA/CRF/SOL=DDXCOM,RKAA
RUN-TIME: 1 2 .4 SECONDS
RUN-TIME RATIO: 37/4=8.1
CORE USED:
7K (13 PAGES)

MACY11 30A(1052) 20-MAR-78 15:47 PAGE 24
CROSS REFERENCE TABLE -- MACRO NAMES

309

:314

480

499

500

508

Page 64
APPENDIX C
Source Module Example (RKAA)

.REM

IDENTIFICATION

PRODUCT CODE:

MAINDEC-11-DXRKA-E-D

PRODUCT NAME:

DEC/X11 RK11 MODULE

DATE:

21 MAR 1974

MAINTAINER:

DIAGNOSTIC GROUP

AUTHOR(S):

ROBERT E. UNDERWOOD

REVISED BY:

S.J.H.(3/7~5)

COPYRIGHT (C) 1975
Digital Equipment Corporation, Maynard, Mass.
This software is furnished under a license for use only
on a single computer system and m~y be copied only with
the inclusion of the above copyright notice. This
software, or any other copies thereof, may not be provided
or otherwise made avai lable to any other p(~rson except
for use on such system and to one who agrees to these
license terms. Title to and ownership of the software
shall at al I times remain in DEC.
The information in this document is subject to change
without notice and should not be construed as a
commitment by digital equipment corportation.
DEC assumeS no'responsibility for the use or reliability
of its software on equipment which is not supplied by
DEC.

APPENDIX C
1.

Page 65

ABSTRACT
RKA IS AN IOMODX THAT EXERCISES RK02, RK03, RK04, RK05 DISK
DRIVES ON AN RK11 CONTROLLER.
IT EXERCISES THE DRIVES BY
DOING WRITES, WRITE-CHECKS, READS, AND IN-CORE COMPARISONS.
ALL ERRORS DETECTED ARE REPORTED ON THE CONSOLE TTY.

REQUIREMENTS
HARDWARE:
1 TO 8 RK DISK DRIVES WITH AN
STORAGE: RKA REQUIRES 983 WORDS OF STORAGE

RK11

CONTROLLER

PASS DEFINITION
ONE PASS OF THE RKA MODULE CONSISTS OF !512 CYCLES OF THE
BASIC TEST SEQUENCE (WRITE, WRITE-CHECK, READ, DATA-CHECK).
THE TEST SEQUENCE WRITES 1024 WORDS, WRITE-CHECKS SAME, READS
THE FIRST 256 WORDS, AND DATA-CHECKS SAME.

EXECUTION TIME
ONE PASS OF RKA RUNNING
APPROXIMATELY 1 MINUTE.

ALONE ·ON

PDP-11/40

TAKES

CONFIGURATION REQUIREMENTS
DEFAULT PARAMETERS:
DEVADR:
177400, VECTOR:

220, SR1:

5. DEVCNT:

REQUIRED PARAMETERS:
NONE
6.

DEVICE/OPTION SETUP
MAKE CERTAIN THAT ALL DRIVES ARE POWERED UP,
AND READY

WRITEtENABLED,

APPENDIX C
7.

Page 66

MODULE OPERATION
TEST SEQUENCE:
A. SETUP DEVICE REGISTER ADDRESSES AND MODULE VARIABLES
B. RESET ALL DRIVES ON-LINE AND DROP ALL THAT ARE NOT
C. GET A DISK ADDRESS AND A FRESH BLOCK OF DATA
D. GET A DRIVE ADDRESS
E. DO A WRITE -- IF ERRORS, REPORT AND RETRY UP TO RETRY
LIMIT
F. DO A WRITE-CHECK -- IF ERRORS, REPORT AND RETRY UP TO
RETRY LIMIT
G. DO A READ -- IF ERRORS, REPORT AND RETRY UP TO RETRY
LIMIT
H. DO A DATA-CHECK -- IF ERRORS, REPORT AND CONTINUE
I. IF END OF PASS, REPORT AND GO TO C
J.
IF END OF DRIVES, GO TO C ELSE GO TO D

OPERATION OPTIONS
SR1 BIT 0 SET(1):
IF THE RETRY LIMIT IS EXCEEDED ON ANY FUNCTION, A HARD
IS ASSUMED AND THE DRIVE IS DROPPED.
SRi BIT 0 Cl.EAR(O):
IF THE RETRY LIMIT IS EXCEEDED, THE FUNCTION IS
THE TESTING CONTINUES.

ERROR

ABORTED

AND

SRi BIT 2 SET(1):
WILL NOT TYPE OUT DATA LATE ERRORS BUT WILL KEEP TRACK OF THE
NUMBER OF DATA LATE ERRORS.
SRi BIT 2 CLEAR(O):
TYPE OUT DATA LATE ERRORS AND KEEP TRACK
DATA LATE ERRORS IN DLTCNT.
9.

THE

NUMBER

NON-STANDARD PRINTOUTS
A. MOST PRINTOUTS HAVE THE STANDARD FORMATS DESCRIBED IN
THE DEC/Xii DOCUMENT
B. ERROR MESSAGES DUMP THE CONTENTS
REGISTERS IN THE FOLLOWING ORDER:
RKDS RKER RKCS RKWC RK8A RKDA RKMR RKDB

THE

RKi1

APPENDIX C

START:

IOMODX
. PAGE

<RKAA

>,177400.220,5.0,O,512.,S,BUFIN,256.,1024 •

MOV
MOV
MOV
CLR
CLR
MOV
MOV
MOV
CLR
MOV
CMPB
BNE

#256. ,WDTO
#1024. ,WDFR
#3,INTR
SIDE
DLTCNT
DV I D1 ,DV ICE
DVICE,DRIVE
#-3,BLK1
DRYVE
#160000,DRVSFT
#B I T1 ,@#41
1$

WORDS TO MEM
WORDS FROM MEM
# OF INTERRUPTS/ITERATION
CLEAR FLAGS AND SIDE INDICATOR
CLEAR DATA LATE EROR COUNTER
GET DRIVE INDICATOR
ALSO SAVE IT IN DRIVE
INITIALIZE BLOCK COUNTER
ZERO UNIT NUMBER
INITIALIZE THE SHIFTED DRIVE #
IS RK UNIT 0 THE LOAD MEDIUM 1
NO, CONTINUE

BIT

IISITO,OVICE

YES, ANO IS ORIV~ 0 CHOSEN?

SEQ

JSR

PC,DROP
#-1,DRYVE
PC,SETUP
PC,REZET
DVICE
FINI
RSTRT1
PASCNT
RSTRT1
START

NO. CONTINUE
YES, GO DROP IT
INITIALIZE DRIVE COUNTER
GENERATE REGISTER ADDRESSES
INITIALIZE RX REGS. AND ALL DRIVES
DROP THE MODULE ?
YES
;+
/ THI SIS
SUPPORT
i+
/
FOR
;+ /
DT03
;+ /
BUS SWITCH
;+/

MOV
JSR
JSR
TST
BEQ
BR
RESTRT: TST
BhlE
BR
RSTRT1 :
GETPA
MOV
NEG

RBUFVA
RBUFSZ,WCNT2
WCNT2

SAVE READ BUFFER SIZE
GET THE 2 1 S COMPLEMENT

STRT:

PC,BLOCK

GET NEXT BLOCK NUMBER

WBUFSZ,WCNT1
WCNT1
BLK1,RO
PC,CONVRT

SAVE WRITE BUFFER SIZE
GET THE 2 1 S COMPLEMENT
LOAD BLOCK # FOR CONVRT
GENERATE DISK ADR. FROM BLOCK #

PC,DRVADR
DVICE
FINI
#BIT3,FLAG
STRT
#160000,DSKADR
DRVSFT,DSKADR
DSKADR,@RKDA
#BIT5,@RKDS

GET A DRIVE ADDRESS
ANY DRIVES LEFT ?
NO, GO DROP THE MODULE
ALL DRIVES DONE?
YES, GO GET ANOTHER BLOCK
CLEAR DRIVE ADDRESS
LOAD DRIVE ADDRESS
LOAD DISK ADDRESS
WRITE PROTECTED?
NO, CONTINUE
YES, DROP THE DRIVE

1 $:

JSR
GWBUFF
MOV
NEG
MOV
JSR
JSR
TST
BEQ
BITB
BNE
BIC
BIS
MOV
BIT
BEQ
JSR
MSGN
BR
BIT
BNE

PC,DROP
DRP
NEXT
#BIT6,@RKDS
2$

GO ON TO NEXT DRIVE
DRIVE READY?
YES, CONTINUE

Page 67

APPENDIX C

GO:

GOA:
GOB:

PASS:
FINI:

JSR
BR
CLR
CLRB
.PAGE

PC,NOTRDY
STRT
TRYl
TRY3

NO, WAIT FOR READY
TRY AGAIN
ZERO RETRY COUNTERS

JSR
BR
BITB
BEQ
BICB
MOV
BR
JSR
BR
JSR
BR
CKDATA

R5,WRITE
RETRY1
#BIT2,FLAG
GOA
IIBIT2,FLAG
#-3,BLK1
STRT
R5,WRITCK
RETRY2
R5,READ
RETRY3
RSUFPA

WRITE SOME DATA
IF ERRORS. TRY IT AGAIN
DID THE DISK OVERFLOW?
NO, CONTINUE
YES, CLEAR THE OVERFLOW FLAG
RESET THE BLOCK NUMBER
START OVER AT BEGINNING OF DISK
WRITE-CHECK THE DATA
IF ERRORS, TRY AGAIN
READ THE DATA WRITTEN
IF ERRORS, TRY AGAIN

ENDIT
BR

ENDMOD

< DROP THE MODULE>

RETRYl : INCB
CMPB
BNE
MSGN
BR

TRYl
#3.TRYl
GO
EXCEDt
NEXTA

COUNT THE RETRYS
LIMIT EXCEEDED ?
NO, GO TRY IT AGAIN

RETRY2: INCB
CMPB
BNE
MSGN
8R

TRY2
113,TRY2
GOA
EXCED2
NEXTA

COUNT RETRYS
LIMIT EXCEEDED ?
NO, TRY AGAIN

RETRY3: INCB
CMPB
BNE
MSGN

TRY3
#3,TRY3
GOB
EXCED3

COUNT RETRYS
LIMIT EXCEEDED ?
NO, GO TRY AGAIN

1$
PC,DROP
DRP
NEXT

NO, SKIP TO NEXT DRIVE
YES, DROP OFFENDING DRIVE

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

GO ON TO NEXT DRIVE

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

NEXTA:

------------------------IIBITO,SR1
DROP THE DRIVE ?
BIT

1$:

SEQ
JSR
MSGN
JMP

------------------------.PAGE

GO ON TO NEXT DRIVE

Page 68

APPENDIX C
RK11 DISK DRIVERS
WRITE:

MOV
MOV
MOV
MOV
BR
WRITCK: MOV
MOV
MOV
MOV
BR
READ:
MOV
MOV
MOV

CLEAR.

2$:

GOGO:

LOAD WRITE FUNCTION
LOAD \vORD COUNT
LOAD BUFFER ADDRESS
LOAD EXTENDED MEMORY BITS
CONTINUE
LOAD WRITE-CHECK FUNCTION
LOAD WORD COUNT
LOAD BUFFER ADDRESS
LOAD EXTENDED MEMORY BITS
CONTINUE
LOAD READ FUNCTION
LOAD WORD COUNT
LOAD BUFFER ADDRESS

MOV

RBUFEA,XMEM

LOAD EXTENDED MEMORY BITS

GOGO

CONTINUE

MOV
uSR
MOV
BIT
BNE
RTS
MOV
uSR
MOV
uSR
RTS

# 1 ,@lRKCS
PC, WAIT1
DRVSFT,@lRKDA
#BIT6,@lRKDS
RS
#1S,@lRKCS
PC,IrJAIT
# 1 ,@lRKCS
PC,WAIT1
RS

ISSUE A CONTROL RESET
GO WAIT FOR CONTROLLER READY
RELOAD THE DRIVE ADDRESS
DRIVE READY?
YES, CONTINUE
NO, ABORT DRIVE RESET
ISSUE A DRIVE RESET
GIVE IT TIME TO COMPLETE
ISSUE ANOTHER CONTROLLER RESET
WAIT FOR CONTROLLER READY
RETURN

#NTRUPT,@lVECTOR
DSKADR,@lRKDA
XMEM,FUNC
FUNC,@lRKCS

SET INTERUPT ENTRY POINTER
LOAD THE DISK ADDRESS
LOAD EXTENDED MEMORY BITS
EXECUTE THE FUNCTION

MOV
MOV
BIS
MOV
EXIT

NTRUPT: PIRQ
1 $:

#S03,FUNC
WCNT1,@lRKWC
WBUFPA,@RKBA
WBUFEA,XMEM
GOGO
#S07,FUNC
weNT1,@lRKWC
WBUFPA,@lRKBA
ItJBUFEA,XMEM
GOGO
#SOS,FUNC
WCNT2,@lRKWC
RBUFPA,@RKBA

uSR
RTS
TST
RTS

1$
RS,ERRORS
RS
(RS)+
RS

GO CHECK FOR ERRORS
ERRORS DETECTED, RETURN
NO ERRORS, SKIP RETRY
RETURN OK

#1 ,R 1
DRYVE,RO

INITIALIZE DROP PICKER
GET THE DRIVE NUMBER
IF DRIVE 0 GO DROP IT
NO. AIM AT THE NEXT DRIVE
IS THIS THE ONE ?
NO, LOOK AGAIN
DROP THE DRIVE
PUSH DRIVE # ONTO STACK

.PAGE
DROP:
1 $:

2$:

MOV
MOV
BEQ
ASL
DEC
BNE
BIC
MOV
OTOA

R1
RO
1$
R1 ,DVICE
DRYVE,-(R6)
DRYVE,ADR1

Page 69

APPENDIX C

BLOCK:

1 $:

ROOM:

1 $:

2$:
3$:

4$:

5$:
6$:
7$:

RTS

RETURN

ADD
CMP
BPL
CLR
MOV
RTS

#3,BLK1
#4799. ,BLK1

STEP TO NEXT BLOCK
BLOCK LIMIT REACHED ?
NO, CONTINUE
YES, RESET BLOCK #
READ WHERE WRITE
RETURN

MOV
MOV
CLR
CMP
BGE
SUB
MOV
BIT
BNE
ASR
SUB
ADD
DEC
BGT
TST
BMI
TST
BMI
BR
TST
BPL
CMP
BLT
TST
RTS
BISB
RTS

BlK1,RO
#2399 •• R1
R2

BlK1
BLK 1 ,BLK2
PC

#2:399. fRO
1$

#2400. ,RO
#2S6. ,BSIZ
#BIT11,@RKDS
2$

BSIZ
RO,R1
BSIZ,R2
R1

R2
4$

WBUFSZ
7$
S$

WBUFSZ
6$

R2,WBUFSZ
7$

(RS)+
RS
#BIT2,FLAG
RS

SAVE THE CURRENT BLOCK NUMBER
lOAD MAX. NUMBER OF BLOCK PER SIDE
Z~RCI REG. ~
IS SID~ 0 DONfl ?
NO, CONTINUE
YES, NORMALIZE BLOCK # FOR SIDE 1
HI DENSITY BLOCK SIZE
HI DENSITY DRIVE?
YES, CONTINUE
NO, SET TO 128 -- LO DENSITY
GET # OF BLOCKS LEFT ON DISK
GET TOTAL NUMCER OF WORDS LEFT
ALL SLOCKS ADDED IN ?
NO, KEEP ADDING
IS # OF WORDS LEFT ON DISK NEG. ?
YES
IS TRANSFER SIZE NEG. ?
YES
NO, GO CmllPARE
IS TRANSFER SIZE pas. ?
YES
WAS THERE ENOUGH ROOM FOR THE TRANSFER ?
NO, RETURN OK
YES, MUST BE A REAL ERROR
RETURN, ERROR
SET OVERFLOW FLAG
RETURN OK

.PAGE
DRVADR: INC
ADD
BICB
CMP
BEQ
ASR
BCC
RTS
1$:

BISB
MOV

DRIVE
DRVADR
PC

COUNT A DRIVE
DRIVE COUNT LINED UP WITH RKDA
CLEAR END OF DRIVES FLAG
ALL DRIVES CHECKED?
YES, GO FLAG END OF DRIVES
NO, IS NEXT DRIVE CHOSEN?
NO, GO TRY ANOTHER DRIVE
RETURN

#BIT3,FLAG
#-1 ,DRYVE

SET END OF DRIVES FLAG
RESET DRIVE COUNTER

DRYVE
#BIT13,DRVSFT
#BIT3,FLAG
#8. ,DRYVE
1$

Page 70

APPENDIX C
MOV
MOV
RTS

#160000,DRVSFT
DVICE,DRIVE
PC

ZERO THE SHIFTED DRIVE #
RESTORE CHOSEN DRIVES
RETURN

NOTRDY: MOV
MOV
MOV
1$:
JSR
BITB
BNE
MOV
BIT
BNE
JSR
BR
2$:
RTS

#-1 ,DRYVE
#160000,DRVSFT
DVICE,DRIVE
PC,DRVADR
#BIT3,FLAG
2$
DRVSFT,@RKDA
#BIT6,@RKDS
1$
PC.WAIT
1$
PC

START WITH FIRST DRIVE

ERSUB2: MOV
MOV
MOV
MOV
TST
TST

-(R1),ASB
R1,SBADR
-(R2),AWAS
R2,WASADR
(R2)+

LOAD THE DATA
LOAD ADDRESS OF DATA WRITTEN
LOAD THE DATA
LOAD ADDRESS OF DATA READ
RESET REG.· 1
RESET REG. 2

ERSUB1: MOV
MOV
RTS

RKCS,CSRA
@lRKCS,ACSR
PC

LOAD ADR. OF CURRENT CSR
LOAD CONTENTS OF CURRENT CSR
RETURN

#77777,CLK

SET THE TIMER

#BIT6,@RKDS
2$
CLK
1$
PC,DROP
DRP
PC

DRIVE READY?
YES, RETURN
NO,. \'JAIT SOME MORE ?
YES, WAIT
TIME-OUT, DROP THE DRIVE

PC, ERSUB1
#BIT14,@lRKCS
1$
#3.@lRKER
3$
(RS)+
RS
#BIT14,@RKER

LOAD ERROR INFORIVlATION
HARD ERROR ?
YES, GO REPORT
SOFT ERROR ?
YES, GO REPORT
NO, SKIP RETRY
RETURN OK
DISK OVERFLOW ?

(R 1 ) +

RESET DRIVE SELECT
GET A DRIVE ADDRESS
ALL DRIVES CHECKED?
YES, RETURN
NO, LOAD NEXT DRIVE ADDRESS
IS THIS DRIVE READY ?
YES, CONTINUE
NO, WAIT FOR IT
GO CHECK REST OF DRIVES
RETURN

.PAGE

WAIT:
1$:

2$:
;

MOV
BREAK
BIT
BNE
DEC
BNE
JSR
MSGN
RTS

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

ERRORS: JSR
BIT
BNE
BIT
BNE
TST
RTS
1 $:
BIT

RETURN

Page 71

APPENDIX C

7$:

6$:

4$:

5$:

BEQ
JSR
BR
BIT
BEQ
INC
BIT
BNE
MSGN
MSGN
CLR
HRDER
JSR
SR
MSGN
MOV
SOFER
RTS
JSR
TST
RTS

7$
RS,ROOM
5$

#8IT9,@lRKER
2$

DLTCNT
#BIT2,SR1
6$

DLTERR
HARD
ERRTYP
TABLE
RS,CLEAR
4$

SOFT
#1 ,ERRTYP
TABLE
RS
RS,CLEAR
(RS)+
RS

NO, CONTINUE
YES, IS IT A REAL ERROR?
NO, CONTINUE
;DATA LATE ERROR?
;NO
;INCREMENT ERROR COUNTER
;TYPE OUT ERROR?
;NO

GO CLEAR OUT ERRORS
RETURN
DATA ERROR
RETURN, ERRORS
CLEAR OUT ERRORS.
SKIP RETRY
RETURN OK

.PAGE
SETUP:

2$:

MOV
MOV
TST
MOV
TST
MOV
TST
MOV
TST
MOV
TST
MOV
TST
MOV
TST
MOV

ADDR,RO
RO,RKDS
(RO)+
RO,RKER
(ROJ+
RO,RKCS
(RO)+
RO,RKWC
(RO)+
RO,RKBA
(RO)+
RO,RKDA
(RO)+
RO,RKMR
(RO)+
RO,RKDS

GET DEVICE ADDRESS
GENERATE CONTROLLER REGS. ADDRESSES

MOV
MOV
MOVB

VECTOR,RO
#STRT,(RO)+
BR1, (RO)

GET THE VECTOR ADDRESS
SET POINTER JUST IN CASE
SET PRIORITY

RTS

RETURN

ZERO REG. 1
ZERO THE SIDE INDICATOR
LOAD REG. 3
LOAD REG. 4
IS SLaCK ON SIDE 0 ?

CONVRT: CLR
CLRB
MOV
MOV
CMP

SIDE
#-12.,R3
# 1 1 • , R4

#2399. ,RO

Page 72

APPENDIX C

2$:
3$:

REZET:
1$:

2$:

WAIT1:
1$:

2$:
DLTCNT:
FUI'JC:
XMEM:
DSKADR:
DVICE:
DRIVE:
DRYVE:
DRVSFT:
BLK 1 :
BLK2:
BS I Z:
TBUF:
WCNT1:

BGE
BISB
ADD
CMP
BGE
ADD
INC
BR
MOV
BISa
MOV
ASL
DEC
BGT
8IS
RTS
.PAGE
MOV
JSR
JSR
JSR
BIT8
BNE
J5R
BR
RTS

MOV
TST8
BMI
BREAK
DEC
BNE
MOV
HRDER
JMP
RTS
0
0

o·
0
0
0
0
0
0
0
0
0
0

#BIT4,SIDE
#-2400. ,RO
R4,RO
2$
R3,RO
R1
1$
RO,DSKADR
SIDE,DSKADR
#5,R2
R1
R2
3$
R1 ,DSKADR
PC
# 1 ,@lRKCS
PC,vJAIT1
PC,NOTRDY
PC,DRVADR
#BIT3,FLAG

YES, CONTINUE
NO, FLIP TO SIDE 1
NORMALIZE BLOCK # FOR SIDE 1
FIND THE RIGHT CYLINDER ?
YES, CONTINUE
NO, SUBTRACT 12 SECTORS (1 CYLINDER)
KEEP TRACK OF CYLINDER ADDRESS
GO TRY AGAIN
LOAD THE SECTOR ADDRESS
LOAD THE SIDE ADDRESS
SET UP FOR SHIFT
LINE UP CYL. ADR. WITH DSKADR
DONE?
NO, GO SHIFT AGAIN
YES, LOAD THE CYLINDER ADDRESS
RETURN

EXECUTE CONTROLLER RESET
GO WAIT FOR CONTROLLER READY
MAKE SURE ALL CHOSEN DRIVES ARE READY
GET A DRIVE ADDRESS
ALL DRIVES DONE?
YES, RETURN
ISSUE DRIVE RESET AND CONTROLLER CLEAR
KEEP GOING
RETURN

#77777,CLK
@lRKCS
2$

SET THE TIMER
CONTROLLER READY ?
YES, CONTINUE

R5,CLEAR
1$

elK

WAIT SOME MORE?
YES
#3,ERRTYP
; CONTROLLER NOT READY
TABLE
< CONTROLLER NOT READY>
FINI
GO DROP THE MODULE
PC
READY, RETURN
1$

Page 73

APPENDIX C
WCNT2:
BUFlEN:
BUFIN:
ClK:
TABLE:
RKDS:
RKER:
RKCS:
RKWC:
RKBA:
RKDA:
RKMR:
RKDB:
MES1 :
MES2:
MES4:
MESS:
MES6:
MES7:
MESS!
MES9:
MES10:
HARD:
SOFT:
EXCED1 :
EXCED2:
EXCED3:
DRP:

DlTERR:
ADR1 :
NUMB:
SIDE:
FLAG:
TRY1
TRY2
TRY3

0
256.
~BlKW

256.

0
0
0
0
0
0
0
0

0
177777
.PAGE
.ASCIZ
. ASC I Z
.ASCIZ
.ASCIZ
.ASCIZ
.ASCIZ
.ASCIZ
.ASCIZ
.ASCIZ
.EVEN
MES1
177777
MES2
177777
MES7
MES6
177777
MESS
MES6
177777
MES9
MESS
177777
MES4
NUMB
MESS
177777
MES10
177777
.BLKB
.BYTE
.WORD
.BYTE
.BYTE
.EVEN
.BYTE
.BYTE
.BYTE
.EVEN

HARD ERROR'
SOFT ERROR'
DRIVE
DROPPED%'
, RETRY
EXCEEDED%'
I
, WRITE'
, WRITE-CHECK'
READ'
'DATA LATE ERROR%'

5
0
0
0
0

0
0
0

Page 74

APPENDIX C
.END

Page 75

APPENDIX D
TABLE OF ERROR CODES
ERROR

TYPE ___ -

Not Defined
Data Error

Data Late

Controller not ready

Block not found

Block missed

Device off-line. nonexistent or not ready

Selection ERROR

Non-existent memory

111 ega 1 interrupt occurred
or "Done" did not set

Premature end of file
encountered

Rewind error (rewind took
too long)

Incorrect vector address

"Busy" wonlt clear in time

Unknown receiver error

Unknown transmitter error

Overrun error

Framing error

Device failed to interrupt

Time-out-shift out error

of interrupts incorrect

Page 76

APPENDIX D
TYPE

ERROR
25

Bit stuck in Register or
DID not change state in
TIME

A-D CONVERSION OUT OF SPEC.

Interrupt enable error

Unknown ERROR during data
Transfer

AID RMS or peak noise
exceeded 1 i mit

NPR error

Device not in maintenance
mode

Device will not initialze

Buffer fill error

Unable to execute a Read
FUNCTION

Unable to excute a write
function

Transfer read bit did not
set

Transmit data late error

Active bit in register
should be set - not cleared

Cyclic redundancy check
error detected

Flag should not be set

Floating point mathemaTical
operation produced INCORRECT
results

Clock overflow failed to
trigger AID conversion

Controller would not clear

Data set line change

BAD SEEK

Page 77

ERROR

APPENDIX D
TYPE ___ _

MICRO CODE NOT LOADED

Page 78