Note_To_User_For_Sadie_Version_3.5__Number_03 0244 05 Note To User For Sadie Version 3.5 Number 03

User Manual: Pdf Note_To_User_For_Sadie_Version_3.5__Number_03-0244-05

Open the PDF directly: View PDF .
Page Count: 138

Download
Open PDF In Browser	View PDF

'\:

NOTE TO USER
·FOR
SADIE VERSION 3.5

Document Number:

03-0244-05

Zilog, Inc.
October, 1984

1.1~

NTU

Zilog

NTU

INTRODUCTION

This document ~rovides an overview of the Stand-Alone Diagnostic
Interactive Executive
(SADIE)
3.5 release and the
supporting documentation.
SADIE is intended for use by qualified, service personnel
with adequate technical knowledge and training on the theory
of operation of the·System 8000 and major components.
2.1.

DOCUMENTATION

The documentation package for SADIE 3.5 consists of the following:
SADIE Note To User, Version 3.5 (03-0244-05)
SADIE Reference Manual (03-3264-02)
SADIE Refe~ence Manual 3.5 Update Package (U3-3264-A2)
SADIE Quick Reference Guide (03-3274-01)

The Update Package consists of changed
incorporated into the existing SADIE
describe the SADIE 3.5 release •

pages that,
when
Reference Manual,

3.1.

DESCRIPTION OF SOFTWARE RELEASE

SADIE 3.5 supports the High Perfocmance Central Processing
Unit (HPCPU) based systems and all earlier versions.
Refer to Apppendix A in the System 8000 SADIE Reference
Manual for a complete list oE the SADIE diagnostics.
4.1.

CHANGES FROM PREVIOUS RELEASE

Three tests have been added since SADIE 3.4 that
HPCPU board which are:
CIO'fST

HPCPU on-board CIa test

SCC'fs'r

HPCPU on-board SCC test

CACHETST.-- HPCPU on-board CACHE

Memo~y

check

the

test

The test sequence has been changed to follow a mo~e
logical
order of diagnostic groupings for the user's convenience.
SIOMODEM, SIOTEST, CENT.PRT, and DP.PRT tests can support up
to four 3SB boards.

Zilog

NTU

Zilog

NTU

When the CPU board type affects a test, the'program checks
for and announces the existence of an HPCPU boardo
SIOMODEM
and SIOTEST menus,
for example,
offer different choices
depending on the ty~e of CPU board in use.

5.1.,

SYSTEM REQUIREMENTS

SCCTST, CACHETST, and
installed.

CIOTEST

must

have

HPCPU

board

SCCTST and ICPTST3 require Zilog part number 59-0327 Revision B cable assembly.· Contact Zilog Field Service personnel for availability.
SIOMODEM, ICPTST2,
and ICPTST3 require the Zilog part
numb~r
59-0293 null modem cable assembly.
Contact Zilog
Field Service personnel for availability.
CPU board and SSB board jumper changes are necessary for
CENT.PRT and DP.PRT test execution.
Refer to CENT/DPoPRT in
the SADIE Reference Manual for these changes.

6.1.

INSTALLATION

The following subsections provide a SADIE
list and initialization instructions.

6.1.1.

materials

check~

Materials Checklist

Cartridge Tape, SADIE 3.5 Release, 14-0009-09
SADIE Note To User, Version 3.5, 03-0244-05

6.1.2.

Installation Instructions

To initialize SADIE, follow these steps:
1 ..

Ensure that the System Administrator has taken the system down and already backed up all files before
proceeding ..

Insert the
drive.

Press RESET.

cartridge

tape

Zilog

.2
~ ~ ~--

.. -.. -~

into

the

cartridge

tape

-~~--'-'-----------'-'-----------="==-='---------------~-

NTU

Zi10g

Enter T.
This command executes System Power-Up
Diagnostics
(SPUD)
in the prom monitor on the (HP)CPU
board.
If no errors are observed, proceed to step 5,
otherwise investigate and correct the error condition
before proceeding.

Enter Z T.
A command level menu is now displayed.
(Refer to the SADIE Reference Manual for further information and instructions.)

7.1.

KNOWN BUGS AND LIMITATIONS

CACHETST cannot be performed without an HPCPU jumper change.
Some early versions of the board do not contain the required
jumper selection, and CACHETST cannot be performed on such
boards, (PCB fabrication, revision 2 or older).
CENT.PRT and DP.PRT cannot detect the presence of an SSB
board in the system, and will appear to execute these tests
without err.ors even though no SSB board is installed for the
printer port under test.
When using SADIE "WDCFMT" or "WDCMON" to format disks with
WDC firmware Version 7.1, ignore the sector numbers in the
bad sector display.
Version 7.1 uses track sparing instead
of sector sparing,
therefore,
only the cylinder and head
numbers are relevant.
In FPPTST,
the program does not generate
numbers to check the instruction "Fremstep".

all

possible

MTCMON is not operational at this time.

2110g

NTU

Zilog

NTU

,-_..

\)
\...- .. -

Zilog

DeN

Zilog

DeN

DOCUMENT CHANGE NOTICE
CHANGE INFORMATION
MANUAL TITLE

System 8000 SADIE Reference Manual

PUBLICATION NUMBER

03-3264-02

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

ISSUE DATE

7-84

OR 03-3264-01 with Update Packages tl3-3264-Al and U3-3264~B1
~

DCN NUMBER

. 1,ff"

DATE ISSUED

U3-3264-A2

9/4/84

This document Change Notice (DCN) contains instructions for
changes made to this manual subsequent to the latest revision. The affected manual title,
publication numberi and
document change notice number, are identified.

(~"

The DeN statement clearly defines the pages affected and, as
required, the purpose of the change. The type of change may
be specified as "add", "delete" or "replace". The attached
change pages will remain in effect for subsequent releases
unless specifically amended by another DeN or superseded by
a publication reprint.
Each change page is marked with the
issue date at the bottom of the page so that it can be
clearly identified as such after it is integrated into the
manual.
Retain the Revision Record behind the manual's cover page to
a record of changes.

mai~tain

DESCRIPTION OF CHANGES

The changes described herein reflect SADIE version 3.5.
Three new tests are added to support the HPCPU board, and
eleven old tests are to be replaced with changed testso
IQPTST4 will become a separate document and is replaced with
a single page of explanation. The title page, preface and
front matter of section 2 are replaced to support the new
documentation. The table of contents is amended to include
four append~ces, which are added for convenience.
INSTRUCTIONS

Refer to the revision record and insert and replace tests as
indicated.

'--

.., '

Zilog
10/25/84

DCN

Zilog

DCN

+-----------------------------------"-~---~-------------------+

REVISION RECORD

1----------+---------+-------+------------+------------------1
IDCN NUMBERI
DATE
IRELEASEI TYPE CHANGEl SHEETS AFFECTED I
1----------+---------+-------+------------+------------------1
1

\U3-3264-A2110-15-84

IU3-3264-A2\10-15-84

I
I
I
I

3.5
3.5

I U3"';3264-A2110-15-84 I

3.5

I
I
\

Replace
Replace

Add

I
I
I

3.5

Replace

IU3-3264-A2\10-15-84 I

3.5

I
I
I

Add

IU3-3264-A2\10-15-84

3.5

\U3-3264-A2\10-15-84

I
I
I

I
I
I U3-3264-A2110-15-84 I
I
I
I

3.5

IU3-3264-A2\10-15-84 I
IU3-3264-A2110-l5-84 I

3.5
3.5

IU3-3264-AZI10-l5-84
IU3-3264-A2110-15-84
IU3-3264-A2110-15-84
IU3-3264-A2(10-15-84

IU3-3264-A2(10-15-84

IU3-3264-A2110-15-84

I
I
I U3-3264-A2110-l5-84
I
I
I
I
IU3-3264-A2110-15-84

IU3-3264-A2\10-15-84
I U3-3264-A2110-15-84

I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I

3.5.
3.5
3.5
3.5
3.5
3.5
3 5
D

3.5
3.5

I
I
I

I
I
I
I
I
I
I
I
I
I
I

Replace
Add
Replace
Replace
Replace
Replace
Replace
Replace
Re~lace

(Replace

I
I
I
I
I
I
I
I

Add
Replace
Replace

3" 5 !

Title Page
Preface -

iii-iv

I
I
I
I

1 Table of Con ten ts I

I
I

I
I
I
I

Add

Page vi
\
\ Section 2, pages I
I 2-1 - 2-4
I
I CACHETST after
I
I Sect.2, page 2-4 I
ICENT/DP.PRT
I

I
I
I
I

CIOTST after
CENT/DP. PRT
ICPTST3
I ICPTST4

I
I
I
I
I
I
(
I
I
I
I
I
I
I
I
I
I
I
I
I

I
I

I
I
I
I
I
I

MDCCRC·
MDCFMT
MDCMEDIA

I.
I
I
I
I
I
I
I
I
I

MDCMON
MDCTEST
MMUTST
SCCTs'r after
MTCOM

I
I
I
I

SIOMODEM
SIOTEST"

1 Appendices A-D

after WDCTEST

+----------+---------+-------+------------+------------------+
Copyright 1984 by Zilog
All rights
r

Inc~

resecved~

Printed in the United States of America.
Address all comments concerning this pUblication to 2i10g or
use
the ~:nclosed reader comment card located in the back of
t his P Ll b lie a t ion "

Zilog
1(1/25/84

~. ___ "./)

SYSTEM 8000 SADIE REFERENCE MANUAL
SADIE Release 3.5

10/25/84

SADIE

Zilog

SADIE

Zilog

SADI8

Preface

The System 8000 SADIE Reference Manual describes the organization,
o~eration,
and test
functions of the Stand-Alone
Diagnostic Interactive Executive
(SADIE)
diagnostic
tape
library.
NOTE
The manual is addressed to
field engineers and
service personnel and supercedes any SADIE documentation contained in the System 8000 Hardware
Reference Manuals.

The manual is organized in this manner:
Section 1

Introduction to SADIE Documentation

Section 2

SADIE Tests

Appendices A through D
Section 1 explains the purpose, organization, and operation
of the SADIE diagnostic tape, and the various command level
test functions and displays.
Section 2 is an alphabetical library of the SADIE diagnostic
tests.
Appendix A provides
SADIE tests.

alpha-numeric

cross

reference

Appendix B defines mWDC packet commands and tape
controller
. status bits for use with MDCMON and TCUMON tests, respectively.
AP pen d i x Cpr 0 vi des 1 a p sum In a rye 0 n ten t i n for m"a t ion foe dis k
controller tests.
Appendix D contains two SPUD ecroe lists.
The
first
list
applies
to systems using a CPU boaed other than the HPCPU.
The second list applies to systems using an HPCPU baaed with
Monit~r firmware, Version 10.0 and above.

iii

2i.10g

10/25/84

iii

SADIE

Zilog

SADIE

This manual and the celated manuals listed
technical documentation foe the System 8000.

below

Title

pcovide

Zilog Part Number

V Hacdware Reference Manual, Models 21/31, 21 Plus,

03-3237

31 Plus
Maintenance Manual, Models 22/32

03-3281

User Guidel Models 22/32

03-3286

Hardware Reference Manual, Models 11/11 Plus

03-3227

*
1'}.

~~.

v ZEUS Reference Manual

03-3255

/..... ZEUS utilities Manual

03-3250

ZEUS Languages/Programming Tools Manual

03-3249

ZEUS Administrator Manual

03-3246

UNlXTM A Quick Ref"erence Guide to Zi10g' s Enhanced
Unix System

03-3269

Zilog Components Data Book

00-2034

Hardware Reference Manual, Winchester Disk
Controller

03-3203

Hardware Reference Manual, Nine-Track Magnetic Tape
Controller

03-3262

Subsystem Operation and Maintenance Manual,
Nine-Track Tape

03-3253

Hardware Subsystem Manual, 5 1/4" "Drive

03-3289"

~Hardware

Reference Manual, Central processing unit

~)
\,

03-3200
::>

Hardware Subsystem Manual, High Performance Central
Processing unit (HPCPU)

03-0315

Hardware Reference Manual, Secondary Serial Board

03-3201

SADIE Quick Reference Card

03-3274

Scheduled for future celease

UNl~M

is a trademark of AT&T Bell Laboratories.
Zilog is licensed by AT&T Technologies, lnco

Zi10g

10/25/84

SADIE

Zi10g

SADIE

Table of Contents

SECTION 1

INTRODUCTION TO SADIE ...•

•••••

•••••••••••

1.1. Purpose of SADIE .............................. .
1.2. Organization and Principles of Operation ....... .
1.3. SADIE Tape Organization ............
1.4. SADIE Program Initialization .................. .
1.5. SADIE Diagnostic Functions ••.••.•
1.5.1 .. Console Interactions ••..•..••
1.5.2. START and RESET Interactions ...•.......••
1.6. Command Level Test Functions •.•.•..••.•..••...
1.6.1. Command Level T: Choose
and run a single TEST .............................
1.6.2. Command Level R: REPEAT previously
loaded single test •••..•.••.•.••..••.•..••••...
1.6.3. Command Level L:
Run current test LIST ............................
1.6.4. Command Level C:
CHOOSE and run a test list ••.••••••.
1.6.5. Command Level E:
EDIT test list •.•.•.•••
1.6.6. Command Level D:
DISPLAY error log .•.•••
1.6.7. Command Level A: Cumulative
error log-ALL tests in list ••••.••••.•.•••••••..
1.6.8. Command Level M: do tape MAINTENANCE ••• ~
1.6.9. Command Level Q: QUIT .•..••....•.••..•••
1.7. SADIE Test List and Control Statements .........
1.7.1. SADIE Test List ~ •.... o • • • • • • • • • • • • • • • • • • •
1.7.2. Control Statements ••.••••.•..••.•••.•••••
1.8. Using SADIE ••
0

..........

•••
0

••••••••

••••••

.....

SECTION 2

•••••••••••

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

1-1
1-2
1-2
1-3
1-4
1-4
1-8
1-10
1-10
1-14
1-14
1-15
1-16
1-20
1-20
1-21
1-21
1-21
1-21
1-22
1-23

SADIE TESTS •••.•.•••••••••••.•..••••...•••.

2-1

2.1. Introduction •••••.••.••••••••••
2.2. SADIE Monitor Diagnostic Tests .•...•..••.••...
2.3. Test List .............................

2-1
2-1
2-4

•••••••••••••

1-1

Zilog

••••••••

SADIE

Zilog

APPENDIX A

SADIE Test and Monitor Cross Reference •..

APPENDIX B

mWDC Packet Commands/Tape Controller
Status Bits
•••••

•••••

O.0

••

••••••

A-I

B-1

APPENDIX C

Lap Summary Contents •..•.•...••........•..

C-l

APPENDIX D

System Power Up Diagnostic Error Lists ••••

D-l

,
\

Zilog
10/25/84

Zi10g

SADIE

SECTION 2
SADIE TESTS

201e

Introduction

This section describes the System 8000 tests that appear on
the SADIE test tape.
All tests listed can apply to all
Models of the system, with the following exceptions:
All tests prefixed by "MDC" apply only to systems with 5-1/4
inch disk drives. Tests beginning with "WDC" apply tosysterns with 8 inch disk drives and tests beginning with "SMD"
apply to systems with 14 inch disk driveso
CACHETST, CIOTST, and SCCTST are designed solely for systems
using an HPCPU board.
ICPTST4, for Exxon Office Systems use
only, is not documented here.
The test name prefix is associated with a sUb-system controller,
a printed circuit board, or board component. The
test name suffix defines test function.
For example:
MDCMON
MDCFMT
SCCTST
TCOM
SMDCRC
MTCOM
FPPMON
'"

2.2.

= mini-Winchester Disk Controller Monitor

mini-Winchester Disk Controller Formatting

= Serial Communications Controller Test
= Tape Command Exerciser

storage Module Device Read Error Check

= Mag-Tape Controller Command Exerciser

= Floating Point Processor Board Set Monitor

SADIE Monitor Diagnostic Tests

The SADIE monitor diagnostics are interactive tests designed
to allow the user full access and control of the subsystem
for System 8000 troubleshooting.
All SADIE tests with the
"-MON" suffix (i~eo, WDCMON, TCUMON) are similar in structure and user interface.
Some commands are shared by all
SADIE monitors, while others are unique to each monitor
type.

",.--'
2-1

Zi109
10/25/84

2-1

SADIE

Z,i log

Most commands may be abbreviated to the first group of characters
that uniquely defines the command during user
interaction.
For example, "DISPLAY" may be shortened to
"DISP".
Some commands have special abbreviations for convenience, such as "RD" for "READ", in MDCMON and SMDMON.
Monitor commands are always entered in UPPER CASE.
Command parameters must be entered after the command and on
the same line, separated from the command and other parameters by one or more blanks o
Most commands have default parameters that are described
the individual monitor documentationo

Parameters are interpreted as decimal unless followed by

"H".
EXAMPLE:
a.
be

256 is interpreted as 256 decimals
l00H is interpreted as 100 hexadecimal, which is 256
decimal.

NOTE
The following examples use MDCMON commandsQ
A simple. command is defined as a command
zero or more parameters.

name

followed

EXAMPLE: Simple Commands
a.

SU 1
RD 1 0 5 200
WR 2 0 1 200

c.
d.

A complex command is one of the following:
ao

An optional repeat factor followed by a simple commande

An optional repeat factor followed by
complex command.

A parenthesized complex command followed by any
of parenthesized complex commands

parenthesized
number

2-2

Zi10g
10/25/84

2-2

SADIE

Zilog

SADIE

EXAMPLE: Complex Commands

a. 10 RD 1 0 5 200
b. (WR 2 0 1 200)(RD 1 0 1 200)
Co l0«WR 2 0 1 200)(RD 1 0 1 200) (CMP 2 0 1 0 l)(IBLK 1»
Example c first writes one sector beginning
200 from memory segment 2, offset 0.

Then one sector, beginning' at disk block 200, is
memory segment 1, offset 08

disk
read

block
into

The data stored in memory segment 2, offset 0 is then compared with the data read into memory segment I, offset 0.
The data from one segment only is compared.
Finally, the block number is incremented by 1.
. is repeated 10 timesD

The sequence

command line is a simple or complex command followed by
carriage return ..

Omitted parameters take on their previous values (or default
values if not set explicitly).
Example:

Command?
RD 1 0 5 200
Command?
RD

The first RD (read) command reads 5 sectors beginning at
disk block 200 into memory segment I, offset 0.
The second
RD command does the same thinge
Example:

WR 1 0 1 200
RD 2 0 1 200
CMP 1 0 2 0 1
l00«WR)(RD)(CMP»

The first three lines above write a sector from segment I,
read the same sector back into segment 2, then compare the
two copies..
The fourth line will repeat those three operations one hundred times, using the same parameters.
Some commands will check for boundary conditions and if the
bound is exceeded, will display a message to that effect and
otherwise ignore the command.
For example, if the current block number is 19999,
issuing
an "IBLK 1"
command for a
drive with only 20000 blocks
available (0-19999) will result in an error message.

2-3

Zilog
10/25/84

2-3

SADIE

Zilog

SADIE

CAUTION

Monitor diagnostics will not protect the user from
destroying. either data in memory (i.e., segment 0
SADIE or diagnostic code) or on a device (ice&1
a
disk with the ZEUS operating system on it). Generally, memory segment 0 should never be touched
by the user of a monitor diagnostic.
For details of command syntax specific to a particular monitor diagnostic, type the "HELP" command while the diagnostic
is invoked ..
2.3.

List of Diagnostics

The list below represents the order in which SADIE 3.5 tests
are documented in the following text o
Refer to Appendix A
for a numeric list of tests as they are presented on the
SADIE menu.
$
$
6)
$
6)

$
$
6)

$
$
$
$
('I)

$
6)
6}
$

$$
$
6)
6)
@
$

$
6)

$TCOM
CACHETST (for HPCPU testing)
$TCUMON
CENT-DP.PRT
$TEX
CIOTST (for HPCPU testing)
$WDCCRC
ECCTEST
@WDCFMT
FPPMON
$WDCMEDIA
FPPTST
$WDCMON
FPPWHET
$WDCTEST
ICPTSTI
ICPTST2
ICPTST3
ICPTST4 (for Exxon Office Systems only)
MDCCRC
MDCFMT
MDCMEDIA
MDCMON
MDCTEST
MEMTEST
MMUTST
MTCMON (not operational at this time)
MTCOM
SCCTST (for HPCPU testing)
SIOMODEM
SIOTEST
SMDINTRO (For supplemental information only)
SflDCRC
SMDFMT
SMDMEDIA
sr1DMON
SMDTEST

2-4

Zi10g
10/31/84

CACHETST

1.10

Zilog

CACHETST

The text which follows provides an overview of CACHETST~ set
up and parameter entry information~ a general test sequence
flow chart~ and error message and lap summary descriptions.
CACHETST performs a thorough test of the HPCPU
memory.

board

cache

Up to five tests are selected during parameter entry,
and
execute in order of test number for each selected bank.
The
test sequence is repeated the number of times specified during SADIE #REPS entry, and ends with a lap summary.
Four parameter entry options allow:
Selection of cache bank to be tested
Cross checking between both cache banks
during tests 3 and 4
Creation of a test window
A

brief description of each test follows:

(1 )

Test 1 checks the eight high order bits of each tag
Test time:
register in the bank currently under testa
~ 5 seconds per bank

(2)

Test 2 tests individual tag register address lines from
the CPU side of the cache.
Test time: ~ 11.5 minutes
per bank

(3)

Test 3 checks individual tag register read/write updating from the Ziloq Bus Interface (ZBI) side of the
cache.
Test time: ~ 24 minutes per bank (without
cross-checking)

(4)

Test 4 checks updating function for
the selected tag
bank, referencing odd segments for data due to.even/odd
cache segment mapping described in Subsection 1.2.
Test time:
~
5 seconds per bank
(without crosschecking)

(5)

Test 5 checks cache memory, slot
(4
bytes)
by slate
Test 5 uses a 16K main memory block separate from the
other memory locations to access the slot under test.
This method checks the four tag register low order bits
that are inaccessible during tests 1 through 4.
Test
time: ~ 70 minutes per bank

Zilog
10/25/84

CACHETST

Zilog

CACHETST

The five tests will run in sequence unless parameters 3 and
4
(Subsection le3)
are set to create a shorter sequencee
If, for example:
Parameter 3

Parameter 4 = 3

Only tests two and three will be executed,
in that order.
To run one test only, enter the selected test number for
both parameter 3 and 4.
Test three and test five perform extensive register and
memory tests and therefore require allocation of a large
block of test time.
These tests could be entered on a
test
list (via parameters 3 and 4) and executed at the user's
convenience, without user interactionv

1.2.

Set Up

To ensure proper test execution, the HPCPU board must be
jumpered to map out even memory segments so that CACHETST
can separate the code and data spaces. Refer to the System
8000 Hardware Subsystem HPCPU Manual for additional information on cache memory mappingu

NOTE
The jumper selection described below does not
exist on some early versions of the HPCPU board.
DO NOT ATTEMPT TO EXECUTE THIS TEST IF JUMPER
SELECTIONS E13-E14 and E14-E15 ARE NOT PRESENT.
Execution of CACHETST on such boards will result
in error message displays. The required jumper
selection is found on HPCPU boards marked Revision
3 and above on the solder sideQ
Prior to running CACHETST, make the following jumper change:
Remove jumper
Install jumper

E13-E14
E14-E15

NOTE
For proper HPCPU performance, the jumper installed
at E14-E15 must be removed and restored to its
original E13-E14 position upon test completiono

Zi10g
10/25/84

CACHETST

Zilog

CACHETST

If a parity memory board is in use, ensure that the fabrication part number is l0-0304-XX, regardless of core memory
size. The l0-02l7-XX parity memory board does not allow
cache circuitry to read a 32-bit data word, and cannot be
used wi th an HPCPU board that has cache enabled, ..

Parameter Entry

1.3.

This test uses standard SADIE parameter
described under "SADIE" in this manualo

entry

prompts

After CACHETST selection from the SADIE test list menu, the
program prompts for parameter entry and number of repetitions desired ..
Parameters allow the following test modifications:
Parameter
1

Purpose
Selects number of cache bank to be tested.
(0

= Bank 0

1 = Bank 1

2 = Both banks
Default: bank=2
2

Flag to cross check between both cache banks.
(0

= Disables cross checking

1 = Checks bank 1 for abnormal effects while

testing bank 0, and vice versa
Default: xcheck=l
3

Select starting test number.
Use with parameter 4 to create a test window.
Default:

Select ending test number.
Use with parameter 3 to create a test window.
Default:

Start

End # = 5

Zilog
10/25/84

CACHETST

Zilog

CACHETs'r

"-----.-.-

1.4 •. Test Sequence
The test sequence flowcharted below assumes
tests are running.

that

all

Check for type of CPU board in use and
display an error message if other than HPCPU.

five

I
I

If an HPCPU board is present, display jumper
change instructionso

Check parameters; perform tests and cross
checks accordinglye

For Test One, Display:
Memory from segment 0 through
Now checking tag register for bank #

Perform "walking ones" test, toggling each
bit.
Disregard parameter 28

Report any errors to SADIE as hard errors;
display an error message; record for lap
summary.

For Test 2, Display:

Now checking tag address lines- for bank #

I
I

Check tag register address lines from cache
CPU side.
Expose any address lines stuck to
either 0 or 1 ..

I
A

Zilog
10/25/84

'-----~

CACHETST

Zilog

CACHETST

------------------------------------------------Report any errors to SADIE as hard errors,
display an error message, record for lap
summary.

------------------------------------------------------------------------------------------------- I
I For Test 3, Display:

Now checking individual tag read/write updating
for banki

Test each tag update function from ZBI side:
- Read target memory location to force tag update
- Check tag register for correct update value
- Check remaining tags for duplicate updates
that indicate bad data and/or address lines
- Check corresponding tag register in other bank
if specified by parameter 2

Report any errors to SADIE as hard errors~
display a bank selection fault error message~
record for lap summary_

I
I

For Test 4, Display:
Now checking tag bank updating for bank #

I
I

Read 16K blocks of selected bank memory to
force update of all tags.

I
I
I

Reference different odd segments to create
"walking ones" pattern through the seven high
order bits of the tag register.

I
I
I

Zi10g
10/25/84

Zilog

CACHETST

.J
'-----

B
\

For Test 5, Display:
\ Now checking cache memory for bank I

Read test:

Perform walking ones test on each cache memory
slot, toggling each bit.

I
I
I

I
I

Check remaining slots in bank for duplicate
I
entries indicating bad data and/or address lines \

I
I
I

Write test:
Perform walking zeroes test on each cache memory
slot, toggling each bitD

I
I
I

Check corresponding main memory slot for write
I
\ through {or store through) cache memory functions. \

Display error messages; check parameter 1

If parameter 1 = 2 (test both banks):
Bank 0 test lap is complete;
Repeat all tests for Bank 1

Display Lap Summary

Zil09
10/25/84

Zilog

CACHETST

1050

CACHETST

Error Messages

This subsection lists error messages displayed when CACHETST
detects the referenced fault.
Variable values are shown
enclosed in < > symbols. Boldface text represents duplication of the actual display.
Error description abbreviations:
TB .....
Tag Bank
eBo .............. Cache Bank
# •••• o o o o e • • number
act ......... o • • actual value
expo .......... expected value
adr ••. o . o • • • • address of tag register or cache memory
err adr ••••.• error address
targt adr •••• target address
data ••..•
register contents
0.0

.....

o ....

CACHETST ERROR LIST
All CACHETST error messages begin with:
ERROR IN:

CACHETST

Possible error displays are listed below, followed by a brief
explanation of the source of each message.
Not an HPCPU board!!

CACHETST does not recognize the CPU board under test
HPCPU board, and aborts the test.

No main memory above segment 011

Indicates that CACHETST has detected no m~in memory above
segment zero. The test will abort following this message.
TB<#> bad compare: adr=<####>, exp=<##>, act=<##>

The tag register at the specified address contains the value
shown at 'act' rather than the expected value, 'exp.'
TB<#> dupl write:

targt adr=<####>, err adr=<####>, data=<##>

A tag register at 'err adr' was erroneously accessed during
check of tag register at 'targt adr.'
Probable Cause: Bad
tag address lines.

Zilog
10/25/84

CACHETST

TB<#>bad update:

Zilog

CACHETST

adr=<####>, exp=<##>, act=<##>

The tag register at "adr" was updated with the
rather than the expected value "exps"

"act"

value

TB<#> unexpd updt: targt adr=<####>, err adr=<####>, data=<##>

A tag register at "err adr" was erroneously updated instead
of or along with the target tag register at "targt adr."
The contents of the register at the erroneous address are
shown after "data". Probable Cause: Bad tag address linese
TB<#> wrong bank selected for updt:

adr=<####>, data=<##>

The wrong tag bank was updated.
Probable Cause:
parator circuitry which performs the selection.
CB<#> bad read:

Bank

com-

adr=<###I>, exp=<########>, act=<########>

The cache memory slot"at "adr" contains the value shown as
"act," which differs from the expected value, shown as
"exp." Probable Cause: The slot did not update correctly
during a read from main memory into the location.
CB<#> dupl rd:

targt adr=<####>,

Cache memory slot at
ing "targt adr" slot
contents of the slot
cache memory address
CB bad write:

err adr=<####>t data=<########>

"err adr" was erroneously accessed durcheck. The "data" value represents the
at "err adrQ"
Probable Cause:
Bad
lines.

adr=<####>, exp=, act=<########>

The cache memory slot at the address "adr" did not update
correctly during a write operation to that location. Consequently, the expected value "exp" and actual value,
"act,"
do not matcho
CB<#> bad wrt thru:

adr=t exp=<########>, act=<#I######>

The main memory location

which

corresponds

the

cache

memory
slot at the address "aden did not update or
incorrectly updated to the value,
"acte"
The contents
expected at that memory location are shown after "exp$"

Zi10g
10/25/84

)
'-..."

Zilog

CACH8TST

1.6.

CACHETST

Lap Summary

Upon completion of each test series, CACHETST displays the
lap number and error counts for each banko
Acronyms used to
display the cumulative error tally for each bank are defined
in the table belowD
Tag Banks

I?i'

CMP
RDUP
UNEXUP
DUPWRT
WRTUP
BKSEL

tag register compare error
tag update error during read
unexpected tag update
duplicate tag register write error
tag update error during write
bank selection error
Cache Banks

RD
DUPRD
WRT
WRTHRU

cache memory slot read error
duplicate slot read
cache memory write error
slot write through error

Note that an identical lap summary, with the addition
status line, is available via the SADIE 'PAUSE' menu e

Press the system START button to interrupt the test in progress and access the 'PAUSE' menu.
Select IE' from the menu
to view a detailed error log for the current test.

Zilog
10/25/84

... -.

..•

CENT/DP.PRT

1.1.

CENT/DPoPRT

Zilog

CENT/DP.PRT

CENT/DPaPRT represents two printer tests:
CENTePRT (CENTRONICS printer interface test)
DP.PRT (DATA PRODUCTS printer interface test)
CENT.PRT and DPDPRT are interactive tests for the Centronics
and Data Products printer interface, respectively. The
printer port tests prompt the user to verify that the
printer is online.
If the printer is online, the tests send the printable character set to PIO Channel B,. the number of times entered during SADIE #REPS parameter entry. To stop the test, the user
presses any character on the console keyboardo
These tests do not check for the presence of SSB boards in
the system.
Therefore, if a printer test is initiated when
an SSB board is not mounted for the selected port, the test
appears to execute without errors.
PIO interrupts are disabled during these tests.
polled by the test.
1.2.

The PIO

Set Up

The printer tests require jumper changes relevant to the
port selected for test, and to the printer type.
The table
on page two of this test lists jumper settings for printer
ports on the standard CPU board and secondary serial boards
(SSB).
Note that there is no printer port on the HPCPU
board.
1.3

Parameter Entry

Port selection parameters will vary with the type of CPU
board in use.
The chart which follows defines parameter
entry choices.
For the HPCPU:

For the standard CPU:

Port:

1 = first SSB printer port

o = CPU board printer port

second SSB printer port
3 = third SSB printer port
4 = fourth SSB printer port
No default value

= first SSB printer port
2 = second SSB printer port

Default = 0

Zilog
10/25/84

CENT/DP.PRT

Zilog

CENT/DP.PRT

Note:
A '0' port selection entry when an HPCPU
will result in an error message display.

use

Printer type parameters are the same for systems with either
CPU board in use:
Type: 0 = Centronics
1 = Data Products
Before running a test, ensure that the proper jumpers are in place:
\ PRINTER
PORT \ TYPE

I
I

CENTRONICS

HPCPU Board

I
I

no I/O port for
printer

DATA PRODUCTS
no I/O port for
printer

-------------------------------------------------------------------Ordinary
El7-El8 El3-El4
E16-E17 E14-E15
I
CPU Board

SSB 1

I
I

-------------------------------------------------------------------"I
I

E2-E3
E4-E5
E7-E8

E10-Ell
El3-El4

El-E2
E5-E6
E7-E8

E10-Ell
El3-El4

*
*

E2-E3
El0-Ell *
I
El-E2
E10-Ell *
I
E4-E5
El3-E14 *
I
E5-E6
El3-El4 *
I
E8-E9
1
E8-E9
1
--------~---------------------------------------------------~-------I
I
1
I
SSB 3
I
E2-E3
Ell-E12 *
I
EI-E2
Ell-E12 *
1
I
E4-E5
E13-E14 *
I
E5-E6
E13-E14 *
1
I
E7-E8
I
E7-E8
I
SSB 2

--------------------------------------------------------------------1
I
I
I
SSB 4

I
I
I

E2-E3
E4-E5
E8-E9

Ell-E12
E13-E14

*
*

I
I
I

E1-E2
E5-E6
E8-E9

Ell-El2
El3-E14

Applies to SSB board assembly revision level C and aboveo

1.4.

Error Messages

A "Printer Busy Too Long" message is displayed if the proper
connection does not exist between" the System 8000 and the
printer.
Ensure that the printer is online and that cable
connections are secure.

Zilog
10/25/84

*
*

I
I
I

CENT/DP.PRT

Zilog

CENT/DP .. PRT

If a zero is entered as the port selection
board is in use, the program announces:

when

HPCPU

ILLEGAL printer port is entered

and presents a menu of allowed choices.

Zilog
10/25/84

CENT/DP.PRT

Zilog

CENT/DP.PRT

'"'---- -

Zi10g

10/25/84

1.1.

CIOTST

Zilog

CIOTST

CIOTST is made up of
clock problems are
an HPCPU board is in
an HPCPU installed
message described in

two tests designed for use if HPCPU
suspected. The test will run only when
usea
Attempting to run CIOTST--wIthout
in the system will result in an error
error message paragraphs.

Test 1 checks HPCPU board Z8536 CIa data paths, and
checks counter/timer functionality.

Test

One test lap is complete in approximately three seconds.
CIOTST is entirely software controlled and requires no
cial cable or jumper changes.
1.2.

spe-

Parameter Entry

When CIOTST is selected from the SADIE test menu,
the program announces the test and promnts for #REPS an~ parameter
entry.

Respond to the following prompt with the desired test
number,
or press the carriage return to accept the default
value:
Parameter 1 test num=
Enter value in decimal or to leave value the same
The only parameter entry required for this test chooses
which test will run.
Test 1 is the default test and will
run if Parameter 1 is not changed, or if an invalid test
number is entered.
1.3.

CIOTST Screens

Following test selectionl CIOTST displays:
This is CIOTST - Version
This is a pair of tests of the HPCPU onboard CIO.
The test is described, and after completion of a test lap,
the program summarizes:
:

lap:1

Total Errors Errors This Lap

On completion of the specified number of repetitions, CIOTST
adds to the display:
Exiting CIOTST. The test is finished
and the SADIE command level menu returns.

Zilog
10/25/84

CIOTST

1.4e

Zilog

CIOTST

Test One

Test 1 is a counter/timer
functions as follows:

write/read

test

which

I Check for type of CPU board in use and
I display an error message if a HPCPU is not installed.

write ones only to each read/write CIa counter/timer register. \

I Verify that each read/write register contains ones only.\
I Display error messages on reads containing any value
I other than ones and store errors for lap summary.
I Write zeroes only to each read/write CIa counter/

timer registero

I Verify that each read/write register contains
I zeroes only.
I Display error messages on reads containing any
I
I number other than zero and store errors for lap summary.l

I
I
lc4.1e

Repeat the test the number of times specified
by #REPS parameter entry~ display lap summary.

I
I

Test One Error Messages

checks for presence of an HPCPU boardo
If it
finds none, the test is aborted and this message displayed:

CIaTST'~first

HOST PROCESSOR IS NOT AN HPCPU - TEST ABORTING

Zilog
10/25/84

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

CIOTST

Zilog

CIOTST

When Test 1 is run, any error will result in this message at
the end of the lap:
REGISTER ERROR: REG IS SHOULD BE
This message means that the value shown as SHOULD BE was
written to the named register and, when read, returned the
value displayed after IS.

1.4.20

Test One Lap Summary

The lap summary, displayed at the end of each lap,
this information for Test 1:
REGISTER TEST:

provides

LAP: TOTAL ERRORS: <#cumulative errors>
ERRORS THIS LAP: <#errors>

If errors occurred during the test lap, the display

reads:

REG IS SHOULD BE
Refer to Paragraph 1.4.1 for interpretation of this error.

1.5.

Test Two

Test 2,
a
counter/timer interrupt test,
checks linked
counter/timers 1 and 2 for ability to count and interrupt.
The Z8536 is set to interrupt 16 msec from the beginning of
the count.
Failure to do so within 20 msec results in an
error message described in Paragraph 1.5.1.

1.501.

Test Two Error Messages

CIOTST first checks for presence of an HPCPU board.
If it
finds none, the test is aborted and this message displayed:
HOST PROCESSOR IS NOT AN HPCPU - TEST ABORTING
When Test 2 is running, the Z8536 timers on the HPCPU board
are linked and set to interrupt 16 msec from the beginning
of the count.
If the counters fail to interrupt within 20
msec, the console displays:
COUNTER/TIMER DID NOT INTERRUPT

Zilog
10/25/84

CIOTST

1.SQ2.

CIOTST

Zilog

Test Two Lap Summary

The lap summary for Test 2 provides the
tion:
COUNTER/TIMER TEST:

following

informa-

LAP: TOTAL ERRORS
ERRORS THIS LAP:

If an error occurred
includes the message:

during

the

lap,

the

lap

summary

COUNTER/TIMER DID NOT INTERRUPT
Refer to Paragraph 1~5.1 on Test 2
interpretation of this messagee

error. messages

for

Zilog
10/25/84

Zilog

1.1.

ICPTST3

ICPTST3, Phase III of ICP testing, is an interactive exercise monitor' for systems which include an Intelligent Communications Processor (ICP) board and an ICP I/O panel.
ICPTST3 is a menu driven, interactive program, and as such
requires no parameter entrieso It is not intended for use in
an automated, comprehensive "test list".
The test provides
a special detailed error log accessed from the SADIE "PAUSE"
mode menu, which identifies faulty integrated circuitso
ICPTST3 interacts with the user similarly to ICPTST2.
An
ICP board jumper change as well as special cable connections
are required to run the test, and are described under the
"set-up" subsection for each tests
ICPTST3 provides a choice of asynchronous or bisynchronous
loopback testse
Menu choice 'I' invokes the asynchronous
test and menu choice 'B' invokes the bisynchronous test.
A
"Q" selection returns the SADIE executive menu.
ICPTST3
menu choices are presented this way:

SELECT OPTION FOR SADIE TEST OF ICP:
"I" = INTERNAL LOOP TEST OF SCC CHANNELS
"B" = EXTERNAL LOOP TEST OF THE BISYNCHRONOUS MODEM PORT
"Q"

QUIT

NOTE
When the program references TTY ports 0-7, for
example, it does not refer to the I/O ports associated with the CPU or SSB boards which are
labeled TTY. The TTY ports referenced in ICPTST3
prompts are ICP I/O panel ports associated with
ICP board SCC channels.

Zilog
10/25/84

1.2.

ICPTST3

Zilog

ICPTST3

Internal Loopback Test

The internal loopback test runs an asynchronous local
back on see channels 0 throu~h 7 in the polled mode.
102.1.

loop-

Internal Loopback Test Set Up

Press I to invoke the test, and the program prompts the user
to remove all "TTY cables" and make these jumper connections
on the Iep board:
CONNECT
E12-E13 •• To set ICP ports 6 and 7 to asynchronous mode
E17-E18 \
\ •••••• Factory installed - check only
E20-E22
E23-E25
/
E24-E26 /
ENTER "R" WHEN READY

Disconnect all Iep port cables for the Internal Loopback
Test, make the jumper change, and enter "R". FAILURE TO
REMOVE CABLES FROM THE Iep I/O PANEL WILL RESULT IN ERROR
MESSAGESo
1.2.2.

Internal Loopback Test Sequence

Each lap transfers
displays:

1024

characters

INTERNAL LOOPBACK TRANSMISSION TEST,
TRANSFERRED,
<# errors> ERRORS
1.3.

Bisynchronous

Loopb~ck

CHARS

Test

Command "B" entry invokes the Bisynchronous Loopback Testo
This test runs a 9600 baud bisynchronous loopback test
between the 6th and 7th ICP ports,
using the first five
ports as external clock sourceso
1.3.10

Bisynchronous Loopback Test Set Up

When the program prompts for jumper changes,
remove rcp
board jumper E12-E13 to set the rcp ports to the synchronous
mode, and verify that the factory installed jumpers are in
place as for the internal loopback testo

Zil09
10/25/84

ICPTST3

Zilog

ICPTST3

"The program then prompts
Interconnect ports 6 and 7, then connect clock to a
port (0-5) and enter its port number when readyo
To connect the I/O test cable (Zilog part number 59-0327):
Connect PI to the sixth port, and P2 to the seventh port.
Connect P3 to any other ICP I/O port selected as a clock
source.
Contact a Zilog Field Service Representative concerning cable availability.
Type in the selected clock port number as prompted.
1.3.2.

Bisynchronous Loopback Test Sequence

On each lap, 256 characters are transferred in
tions, followed by the prompt:

both

direc-

BISYNCHRONOUS TRANSMISSION TEST, <#characters> CHARS
TRANSFERRED EACH WAY, <#errors> ERRORS

1.4.

Error Messages

All error messages are preceded by an audible "beep" on the
console.
Hard errors reported on the console terminate the
test and return the ICPTST3 menu.
To view a simple error log at the end of the test, enter "Q"
from the ICPTST3 menu, or press the system START button for
the Pause menu, and then enter "D"
via the console.
For
information on the detailed error log, refer to paragraph
1.4.1.
DO NOT PRESS START TO INITIATE A PAUSE WHILE ICPTS~3
IS RUNNING.
Error messages are listed below in boldface type, with variable values shown as .
Error message interpretation followso
SCC TRANSMIT BUFFER EMPTY FLAG WAS NOT SET, ICP<#>, TTY
Bit 2 of Read register 0 was not set on the transmit
during the internal loopback transmission test.

Zilog
10/25/84

port

ICPTST3

Zilog

ICPTST3

SCC RECEIVE CHARACTER AVAILABLE FLAG WAS
TTY

NOT

SET,

ICP,

Bit 0 of Read register 0 was not set on the receive
during the internal loopback transmission test.

port

CTS NOT SEEN BY TTYd, ICP
Bit 5 of Read register 0 (CTS) did not go high when RTS in
transmit port was set high during the bisynchronous loopback
transmission test.
DCD NOT SEEN BY TTYd, ICP
Bit 3 of Read register 0 (DCD) of the receive port did not
go high when transmit port DTR was set high during the
bisynchronous loopback transmission test.
RECEIVE SYNCHRONIZATION NOT ACHIEVED BY TTY, ICP
The receive port failed to achieve
three 50 sync character tries.

synchronization

within

SLAVE MEMORY PARITY ERROR, STATUS=
A slave memory parity error caused a non-vectored interrupt
in the host.
STATUS is the hexadecimal value of offending
rcp status register.
SLAVE SOFTWARE NO LONGER RUNNING
The slave CPU has not responded to the· host within the
imumallowable time.

max-

SLAVE OUT OF SYNCHRONIZATION WITH HOST, ICP
A non-vectored interrupt occurred in the slave processor
with Bit 15 of the non-vectored interrupt flag equal to
zero.
INVALID OPTION RECEIVED BY ICP<#>
A non-vectored interrupt occurred in the slave processor
with an unexpected value in the non-vectored interrupt flag.
UNKNOWN MESSAGE FROM SLAVE
A non-vectored interrupt occurred in the host processor with
an unexpected value in the non-vectored interrupt flag.

Zilog
10/25/84

1.4.1.

ICPTST3

Zilog

IcP'rST3

Detailed Error Summary

An "E" PAUSE menu choice summons a detailed error log
display which provides chip-level rcp board fault isolation
when errors have occurred during rCPTST3.
To access the PAUSE menu, press the system START button at a
time when no test is in progress, and the program is waiting
for user input.
Enter "E" to view this detailed error log
test:

for

the

current

INTERNAL LOOPBACK TEST SUMMARY:
TEST

ICP

TTY

RESULT

PASS

FAIL

FAILING TEST PATH

or
U ••••• u

BISYNCHRONOUS LOOPBACK TEST SUMMARY:
Iep

TTY

RESULT

PASS

<,>

FAIL

TEST

FAILING TEST PATH

·0

U.",o •• U<'>

The program isolates problem rcs in this way:
The rcp board contains 145 chips, which, for fault isolation
purposes, form a 145 dimensional vector spaceo
This vector space contains test paths in which:
i-th component = 1
i-th component

if Ui is in the test data path
if Ui is not in the test data path

rCPTST3 stores rc designations in tables for each test path,
which enables boaed fault isolation to the chip level.
rcp
port selection{s) determine which path the test will take.

Zilog
10/25/84

ICPTST3

Zilog

)
\

The program displays "PASS" under "RESULTS" when the test is
successful, and "FAIL" when the test is unsuccessfulo
PASS
FAIL

the union of all successful test paths

= the union of all unsuccessful test paths

The set complement of PASS together with FAIL determine a
set of components in one or more failing paths. (The set
complement of PASS represents a set of ICs which are not in
a successful test path, such as those in untested paths.)
Test paths from the input connector PI to the CPU (U63)
are
assumed to PASS, and test path reporting is limited to those
paths between the CPU and connector P2.

1 5.
0

Lap Summary

The number of characters transferred
errors is displayed after each lap.

Zilog
10/25/84

and

the

number

Icp crST4

1.1

Zilog

ICPTST4

ICPTST4 is an EXXON OFFICE SYSTEM customer
such, is not documented in this manual.

option

and,

Zi10g
10/25/84

)
"-~.

MDCCRC

2;ilog

MDCCRC
~\

1.ls

MDCCRC

MDCCRC is a nondestructive verification of the data on a
1/4" mini-Winchester disk.

1.2.

MDCCRC Overview

MDCCRC reads every track on
parameter 1.
Parameter 1
(default: unit = 0)

the
=

disk unit
unit number

specified by
to be tested

Before the test begins, MDCCRC issues a software reset command to the mini-Winchester Disk Controller (mWDC).
If the
mWDC does not respond or fails to pass its self-test, a message is displayed and MDCCRC aborts the test. Otherwise,
MDCCRC issues an mWDC firmware identifier read command to
determine the firmware version.
Whenever a read error is .detected, an error message is
displayed and logged.
The message identifies the type of
error encountered, the start disk address and whether the
error was corrected (soft error)
or uncorrectable (hard
error) •
MDCCRC repeats the test the number
SADIE #REPS entry.

times

specified

The disk drive heads move to the innermost cylinder
end of the test.

1.3.

by
the

Initialization and Self Test Error Messages

MDCCRC displays one of the following error messages whenever
an mWDC initialization or self-test error occurs:
MDC NOT RESPONDING DURING INITl1

The test initiated a software reset to the host and
sent the segment and offset of a packet. The mini Winchester Disk Controller did not indicate self-test
start and thereby acknowledge receipt of the reset.
DMA OR RAM ERROR: PACKET NOT CLEAREDl1

The mWDC began self test, thereby acknowledging receipt
of reset from the host.
However, the packet was not
cleared by the mWDC, indicating that there is a
Direct
Memory Access or memory problem.

Zilog
10/25/84

MDCCRC

Zilog

MDCCRC

MDe TIMED-OUT ON SELF-TEST!l

The mWDC must indicate completion of its self-test
within 1.5 minutes of its start. MDCCRC waited the
correct amount of time and the mWDC had not yet indicated end of self-test.
Moe SELF-TEST ERROR: PROM CRC1!
The mWDC failed its PROM
test.

checksum

test

during

self-

MDC SELF-TEST ERROR: RAM ERROR AT
The mWDC on-board RAM test failed during self-test. The
RAM offset where the error occurred is a hexadecimal
number.
MDC SELF-TEST ERROR: INVALID COMPLETION CODE:

The mWDC returned an unrecognizable self-test completion code (shown in hexadecimal) in the packet dispatch
word. The host interprets this as a
fatal self-test
error.

1.4.

1_.

Read Error Messages

\ ..

This heading lists possible read error
during the test as an error occurs.
1~4.1.

messages

displayed

Error Description Conventions

Conventions used to describe possible
are:

read

error

messages

Non-variable messages such as "DISK="
are
shown
as
displayedo
Variable information which further defines error
types is indicated within"<
>" symbols~
,
for example.
Disk unit and logical block
addresses,
data patterns,
cimal numbers

numbers are decimal numbers~
and buffer contents are hexade-

,-. _ _ C

Zilog
10/25/84

MDCCRC

Zilog

MDCCRC
/~.

Any of the messages listed below
:

may

appear

place

"wait Abort"
"Parity"
Wri te Faul til
Seek Not Complete"
Cylinder Not Found"
Drive Not Selected"
Block Not Found"
Invalid Command"
No Track 0 Found"
Drive Not Ready"
Bad Interrupt"
Bad Defect Map"
Illegal Cylinder"
Burst Error"
Read Abort"
Unknown"

.'{1

1.4020
fr"\

Error Descriptions

A brief description of the error message source follows each
error listed in the following text.
HARD ERR-- DISK= READ 17 SEes
The mWDC returned an uncorrectable error status in Command
Word 5 status field upon completion of a packet commando
Example Display:
HARD ERR--Burst Error DISK=0,200
This error message indicates
Error
(data error) occurred
0, block 200.

SEes

an uncorrectable Burst
while read ing disk unit

SOFT ERR-- DISK= READ 17 SEes
The mWDC returned a correctable error code in the status
field of Command Word 5 upon completion of a read packet
command.

Zilog
10/25/84

MDCCRC

Zilog

MDCCRC

Example Display:

SOFT ERR--Burst Error

DISK=1,1333

This error message indicates a
Error
(data
error)
occurred
unit I, block 1333~

1.5a

READ 17 SEes
correctable Burst
while reading disk

Lap Summary

At the end of each lap, the program displays a lap summary
of cumulative statistics for all laps completed in the
current MDCCRC test run o
Appendix C provides details of lap
summary content ..

Zilog
10/25/84

)
.'

Zilog

MDCFMT

1.1.

MDCFMT

MDCFMT is a DATA DESTRUCTIVE formatting of the entire mini
Winchester
Disko
This text first provides a general
description of the test, followed by parameter and error
message definitions.
lo2e

MDCFMT Overview

Before disk formatting begins, MDCFMT issues a software
reset command to the mini-Winchester Disk Controller (~WDC)o
If the mWDC does not respond or fails to pass its self-test,
an error message is displayed and MDCFMT aborts the test.
Otherwise, MDCFMT issues an mWDC firmware identifier read
command to determine the firmware versionQ
If the mWDC initialization sequence is successful and the
controller board switch settings are set to a drive type
that MDCFMT recognizes, no drive parameters need be entered.
If mWDC switch settings indicate that universal drive types
7 exists for the current disk unit, the program prompts for
entry of disk drive parameters for the number of heads and
physical cylinders, and the reduced-write current cylinder
numbero To obtain these parameters, refer to the hardware
reference manual appropriate for the system under testo
When the program is satisfied with the disk
displays:

parameters,

The following physical limitations will be used for unitl,
iblocks #cylinders 'heads
#sectors per track
MDCFMT then formats the disk track by tracke
The number of
repetitions
(IREPS) entered in the test l"ine determines the
number of times MDCFMT repeats the format0
If,
however,
#REPS is more than one, the defect map does not carryover
from one repetition to another. The disk drive heads move
to the innermost cylinder at the end of the test.
Disk formatting proceeds automatically unless parameter 4
specifies manual defect map entry, in which case the program
prompts for appropriate entries. Manual defect map entry is
normally not required
(refer to Subsection 1.4 for more
information).
7~

For each track, MDCFMT sets up a buffer with sector header
information and sends the FMT packet command to the mWDC.
Defective blocks are added to a memory resident,
temporary

Zi109
10/25/84

MDCFMT

Zilog

MDCFMT

defect map, which can accommodate up to 127 defective blocks
depending on the firmware version used on the mWDC.
NOTE

MDCFMT will not tolerate any defective sectors on
cylinder 0, and will abort the formatting if any
defects,including soft defects, are found on that
cylinder numbere.

After all tracks are formatted, MDCFMT writes a copy of the
defect map on the first block of every track on cylinder 0.
It also displays the defective physical block numbers on the
console.
The disk drive parameters (number of cylinders, number of
heads, number of blocks/cylinder, etcG) are also written to
the second block of each track on cylinder 0.
1.30

MDCFMT Parameters

The program prompts for these parameter entries. If a value
is not entered, the default value is used for the test.
Parameter

The disk unit number
(Default: unit = 0).

formatted.

Parameter 2 =

The. number of scans during surface analysiso
(Default: scans = 5, max scans number is 7).

The informative messages displayed on the
consoleg
If zero, only error messages are
allowedo
(Default: verbose = 1).

Parameter 4 =

The defect map entry mode.
If non-zero,
MDCFMT will find the defective sectors during
surface analysis&

Parameter 3

If zero, the user must enter the defect map,
using the defect table provided by the disk
drive manufacturer.
(Default: automap = 1).

Zilog
10/25/84

)

'---

MDCFMT

Zi10g

MDCFMT

P~rameter

2 determines the quantity of surface

analysis

be done.
WHERE:
Scans

Scans

MDCFMT formats only (not usual
does not map defects)

procedure~

MDCFMT performs write-read-andcompare tests in addition to read
and compare testso

.~.

Data patterns used are:

1)
2)
3)
4)

6DB6DB6DB6DB
B6DB6DB6DB6D
DB6DB6DB6DB6
FFFF

0000

6)
7)

AAAA

5555

The pattern used when Scans = 0 is 0000.
This chart
trates the result of each Parameter 2 choice:

illus-

Result

# Scans

--------~-+--------------------------------

I
2
3
4

5
6
7
.c,

I
I
I
I
I
I
I
I

Format
Scan I
Scan 2
Scan 3
Scan 4
Scan 5
Scan 6

plus
plus
plus
plus
plus
plus
plus

write/read
write/read
write/read
write/read
write/read
write/read
write/read

A non-zero parameter 3 (verbose) entry
gress report displays on the console.
only error messages will be displayedo

6DB6H
B6DBH
DB6DH
FFFFH

00000
AAAAH
5555H
produces test proIf parameter 3 is 0,

If parameter 4 (automap) is non-zero, MDCFMT will
find the
defective sectors on the disk drive during surface analysis
(scans> 0).
If parameter 4 is zero, the defect map must be
manually entered (refer to Subsection 104).

MDCFMT checks all the parameters entered for validity.
The
number of heads and cylinders are checked for values zero
through the number of heads minus one, and one through the
number of cylinders minus two, respectively.

Zilog
10/25/84

MDCFMT

Zilog

MDCFMT

.)
1.4.

Manual Defect Map Entry

\---."

CAUTION

Manual entry of the media defect table should have
already been performed at the factory, and is normally not required of Zilog Field Service person-,
nelGl

To initiate manual defect map entry:
1.

Set Parameter 4 to zero
entry.

allow

manual

defect

map

Enter drive parameters if necessaryo

Obtain head, cylinder and byte-from-index parameters
for
the defective drive from the drive manufacturer's
defect table and enter when promptedo

If the byte-from-index parameter does not fall within a data
section of the track, the program displays:
BYTE-FROM-INDEX IS NOT WITHIN A SECTOR DATA FIELD-ENTRY NOT ALLOWED
Press and proceed to
display.

the

input

following

this

If the entry is allowed, the program displays:

ADDING PHYSICAL BLOCKi to DEFECT MAP
ENTRY#
If the entry already exists in the defect map (which can
occur when two byte-from-indexes lie within the same sector), the user is informed:
PHYSICAL BLOCK* ALREADY IN MAP
count> ENTRIES

-- to proceed to the next input after this message.
The mess?ge, HARD ERR-- Too many defects on disk,
indicates
that the defect map is full and no more entries are allowed.

Zilog
10/25/84

MDCFMT

Zilog

MDCFMT

Parameters 2 and 4 should be used in conjunctione
ple:
Parm 2

1.5.

For exam-

Result

Parm 4

Scans == 5

Automap == 0

additional surface analysis
defects added to user entered
defect map

Scans == 0

Automap == 0

user entered defect map only
entered onto disk drive

Error Messages

MDCFMT displays an error message whenever an mWDC initialization error or self-test error occurse These error messages are described in the documentation of MDCCRCo
Other error messages are described in the following texto
Messages are shown in boldface type, and variable values
indicated inside < > symbolse
:~

One of the following error status messages will be displayed
in place of :
"Parity"
"Write Fault"
"Seek Not Complete"
"Cylinder Not Found"
"Drive Not Selected"
"Block Not Found"
"Invalid Command"
"No Track 0 Found"
Drive Not Ready"
Bad Interrupt"
Bad Defect Map"
Illegal Cylinder"
Burst Error"
Read Abort n
Unknown"

Zilog
10/25/84

MDCFMT

Zilog

MDCFMT

HARD ERR-- RECALIBRATING DRIVE

Before MDCFMT begins the formatting and after it finishes
formatting the last track, it issues a HOME packet command
to the mWDC. This message appears when an uncorrectable
error status is returnedo
SOFT ERR-- RECALIBRATING DRIVE

MDCFMT sensed a correctable error status upon completion
a HOME packet command.
HARD ERR-- FORMATTING CYL HEAD

MDCFMT senses an uncorrectable error status upon completion
of a FMT packet command. The decimal numbers identifying
the cylinder and head being formatted are given.
SOFT ERR-- FORMATTING CYL HEAD

MDCFMT senses a correctable error status upon completion of
a FMT packet commando The decimal numbers identifying the
cylinder and head being formatted are given.
HARD ERR-- WRITING-, Cyl 0, Blk
HARD ERR-- WRITING-, DISK=

MDCFMT sensed an uncorrectable error status upon writing a
data pattern to the indicated physical block numbero The
first message appears if the block was on cylinder 0, and
indicates a fatal disk defecto
The second message appears if the block was not on cylinder
0,
which means that the block will be added to tne defect
map. The data pattern being written is shown in hexadecimal
after WRITING.
SOFT ERR-- WRITING-, Cyl 0, Blk
SOFT ERR-- WRITING=, DISK=

These messages are similar to the previous messages, but
indicate a correctable error status was returned upon completion of the writeo
If the first message appears,
the
defect was on cylinder 0, and it is considered fatal even
though it was correctableo

Zilog
10/25/84

MDCFMT

Zilog

HARD ERR-- READING-, Cyl 0, Blk
HARD ERR-- READING-, DISK=

This message appears when MDCFMT senses an uncorrectable
error status upon reading a data pattern to physical block
number shown.
The first message appears if the block is on cylinder 0, and
it is considered a fatal erroro The second message appears
if the block is not on cylinder 0, which means that the
block will be added to the defect map.
SOFT ERR-- READING-, Cyl 0, Blk
SOFT ERR-- READING-, DISK-

These messages are similar to the previous messages, but
indicate a correctable error status was returned upon completion of the read.
If the block is on cylinder 0,
it is
considered fatal, even though it was correctable.
HARD ERR--COMPARING-, Cyl 0, Blk
HARD ERR--COMPARING-, DISK-
,~\

MDCFMT compared a buffer written to the physical block
number shown with another buffer read from the same block,
and a mismatch was found.
The pattern written is displayed
in hexadecimal.
The first message appears if the block was on cylinder 0,
which is considered fatal.
The second message appears if
the block is not on cylinder 0, which means that the block
will be added to the defect map.
HARD ERR-- WRITING MAP ON BLOCK

MDCFMT was writing a copy of the completed defect map onto
the block number indicated, and an uncorrectable error
status was returned.
SOFT ERR-- WRITING MAP ON BLOCK

This message is similar to the previous message,
cates a correctable error status was returned.

Zi10g
10/25/84

but

indi-

MDCFMT

Zilog

MDCFMT

HARD ERR-- WRITING DRIVE PARMS, BLOCK
MDCFMT was writing a copy of the drive parameters onto the
indicated block, and an uncorrectable error status was
returnedD
SOFT ERR-- WRITING DRIVE PARMS, BLOCK
This message is similar to the previous message,
cates a correctable error status was returned.

but

indi-

HARD ERR--Too many defects on disk
More than the maximum number of defective blocks were found
during
the surface analysiso
This is considered a fatal
error because the map can hold only a
fixed number of
entries.

1.6.

Lap Summary

A lap summary is displayed at the conclusion of each lap of
MDCFMTo
The lap summary is a table of statistics that is
cumulative for all laps completed so far in the current run
of MDCFMTo
Lap summary contents are described in Appendix
C.

Zilog
10/25/84

)

MDCMEDIA

Zilog

MDCMEDIA

.r-r,
I

.1 . . 1$

MDCMEDIA

MDCMEDIA is a DATA-DESTRUCTIVE test of the disk media. This
text first provides test parameter descriptions, followed by
the test sequence, information on error messagese

102.

Overview

To exercise the disk, MDCMEDIA performs a write-read or
write-read-compare test on each track, dependent on parameter settings. write pattern choices are listed below under
parameter 3.

1.3. Parameters
Parameter 1 =

Unit to be tested (default: unit = 1)

Parameter 2 =

Compare pattern read with pattern written.
If compare = (0
If compare = 1

compare step skipped
compare step done

(default: compare
Parameter 3 =

Patterns used to test the disk medium.
If allpat

only worst-case MFM pattern,
"B6DB6DB6DB6D" , is used.

If allpat

all patterns used:
"FFFF",
"AAAA" and "B6DB6DB6DB6D".

(default: al1pat

Zilog
10/25/84

1.4.

MDCMEDIA

Zilog

MDCMEDIA

Test Sequence

An overview of the test sequence is flowcharted below:
MDCMEDIA issues a software
reset command to the mini-Winchester Disk
Controller (mWDC)0

I
I

______I \ _______

No Response
or
Failed Self Test

Self-Test Passed

I
I
I

Firmware Identifier
Read Command Issued

Test Aborted

Check Parameters

Check Test List
#REPS

I
\

Parm 2
Compare=l

Parm 2
Compare=0

Write/Read/Compare

Write/Read

/ \
/
Parm 3
Allpat=l

FFFF
AAAA
B6DB6D

B6DB6D

I
I

Parm 3
Allpat=l

Parm 3
Allpat=0

FFFF
AAAA
B6DB6D

/ \

Parm 3
Allpat=0

B6DB6D

I
I

Repeat <#REPS> Times

Message on Error

End of Test
(Disk Drive Heads Move
to Innermost Cylinder)

Lap Summary
' ....

Zilog
10/25/84

1$5

t1DCMEOIA

Zilog

MDCMEOIA

Error Messages

This heading lists possible error messages displayed as an
error occurs, other than initialization and self-test error
messages, which are documented under MDCCRC.
Refer to Appendix B for error status code descriptions.
Conventions used to describe possible error messages are:
Non-variable messages such as
"DISK="
are
shown
as
displayed.
Variable information that further defines error
types is indicated within "<
>" symbols~
,
for example.
Disk unit and logical block
addresses,
data patterns,
cimal numbers.

numbers are decimal numbers~
and buffer contents are hexade-

Any of the messages listed below
:

may

appear

place

"wait Abort"
Parity"
write Fault"
Seek Not Complete"
Cylinder Not Found"
Drive Not Selected"
Block Not Found"
Invalid Command"
No Track 0 Found"
Drive Not Ready"
Bad Interrupt"
Bad Defect Map"
Illegal Cylinder"
Burst Error"
Read Abort"
Unknown"
A brief description of the error message source follows each
error listed in the following texto
HARD ERR-- DISK= WRITE-

The MOC returned an uncorrectable-error code in the status
field of Command Word 5 upon completion of a write packet
command.

2ilog
10/25/84

MDCMEDIA

Zilog

SOFT ERR-- DISK= WRITE-
The MDC returned a
field of Command
command.

correctable-error code in the status
Word 5 upon completion of a write packet

HARD ERR-- DISK= READ-
The MDC returned an uncorrectable-error code in the status
field of Command Word 5 upon completion of a read packet
command.

SOFT ERR-- DISK= READ-
The MDC returned a
field of Command
command.

correct.able-error code in the sta tus
Word 5 upon completion of a read packet

COMP ERR: DISK= ADDR= GOOD= BAD=
A mismatch was found when a source buffer containing a pattern written to a sector was compared with a destination
buffer read from that sector. The data read from the destination buffer is displayed after "BAD".

,/-,
\.~-.-.'

The address number is the offset in
compare error occurrede
1e6

the

buffer

where

the

Lap Summary

A lap summary is displayed at the conclusion of each
MDCMEDIA test lap. The lap summary is a table of statistics
which includes errors accumulated during all completed laps
of the current test run.
Refer to ~ppendix C for more
information on lap summaries.

Zilog
10/25/84

1 •1 •

MDCMON

Zilog

MDCMON

MDCMON'

MDCMON is a POTENTIALLY DATA DESTRUCTIVE interactive monitor
for testing mini-Winchester Disk Controller (mWDC) board
function.
The user enters command lines via the system console'keyboard and thereby controls the mWDC.
1.2.

Test Sequence

The flowchart below provides an overview of user interaction
with the MDCMON program:
MDCMON issues a software
reset command to the mini-Winchester Disk
Controller (mWDC).

I
1

______I \ _______
/
\

No Response
or
Failed Self Test

Self-Test Passed

Command? <-----------1
1

Test Aborted

Enter Command Line

1
1

HELP

I
I
I
I

Command,Parm
List Displayed

1_ _ _ 1

Execute

QUIT
CAUTION

A read into segment 0 will destroy parts of the
memory resident SADIE code, the MDCMON code, the
SADIE catalog or other, information stored~there.
1.3. Command Description Conventions
The foliowing conventions apply to MDCMON
tions:
1.

command

descrip-

Basic commands are shown in upper-case letters.
Lower
case acronyms which describe values to be entered
represent optional arguments.
The entire command syntax is in boldface type.

Zilog
10/25/84

MDCMON

Zilog

MDCMON

Command names may be abbreviated to the shortest string
that uniquely defines the command,
in which case,
default values may replace arguments.
Arguments are shown in the order in which they must
entered.

Example:
IBLK

I
I
I
I

incval

Sets value by which the block number
increments (optional)

If not followed with above argument, increments
block by last value entered.
If no previous
value exists, block number increments by default 1.

Some commands are described together for convenience.
In these cases, a slash ("/") separates the commands.
Example:
a.
b.

BMODE / RMODE
SMD/SME

Each example represents two distinct commands which are
related in function.
3.

This text may show memory addresses as displayed, with
the segment enclosed in greater than and lesser than
symbols, and the offset number immediately following.
For example, <1>0 refers to segment I, offset 0.

MDCMON operates in one of two modes:
Raw Mode

Block Mode
Disk address entries
interpreted as block number.

Disk address entries
interpreted as cylinderhead-sector.

In this text, arguments for each mode are
example:
RD rseg roff blkcnt blk
RD rseg roff blkcnt cyl head sec

Zilog
10/25/84

showno

For

(block mode)
(raw mode)

)....

- .-,.

MDCMON

Zilog

MDCMON

MDCMON always maintains the current disk address in
both the block and raw representations.
If MDCMON is
in block mode and the current block number is changed/
the current cylinder/ head/ and sector numbers are also
changed.
5.

Command arguments
changed.

1.4

MDCMON Commands

remain

the

same

until

The following text describes commands used
Commands are in alphabetical order.

explicitly

run

MDCMON.

BHODE / RHODE
BMODE sets MDCMON into block mode.
Block mode means that
all disk address parameters are interpreted as a block
number.
MDCMON is in block mode/ by default.
RMODE sets MDCMON into raw mode. Raw mode means that all
disk address parameters are interpreted as cylinder/ head/
and sector numbers.
Example

Interpretation

BMODE
RD 1

200

RMODE
RD 1

Block mode:
Raw
2

mode:

200

block

41=

4 = cylinder #
2 = head 41=
7 = sector 41=

CEC unitnum clearall / REC unitnum
CEC with no arguments clears error and
for the currently selected disk unit.

command

statistics

If a unit number value (unitnum) is entered/
MDCMON
error and command statistics for that unit number.

clears

A non-zero clear-all value entry clears:
-

Error and command counts for specified unit
Messages for specified unit
SADIE cumulative error log
Global MDCMON error counter

The lap count always resets to 1.

Zilog
10/25/84

MDCMON

Zilog

MDCMON

REC with no arguments displays the error and command statistic table for the current disk unit.
Enter REC and a unit number to
table for a specific unit.
NOTE:

view

the

error

statistics

The unit number entered does not become the current
unit numbero
Example Command

Description

SU 0
REC 1

Selects unit 0 (long form = SUNIT)
Displays error stats for unit 1
(current unit is 0)
Clears error counts for unit 0, the
current unit

CEC

COMPARE srcseg srcoff destseg destoffcount

srcseg
srcoff
destseg destoff count {

source buffer segment number
source buffer offset number
destination buffer. segment number
destination buffer offset number
sector count in block mode
(#words-per-sector * count)
word count in raw mode .

A compare error message is displayed if a mismatch occurs.
The default source buffer begins at <2>0.
count is 1 block.

The default

Example:
BMODE
CMP 2

BMODE sets block mode.
eMP compares the source buffer at
segment 2,
offset 0 with the destination buffer at segment
I, offset 0. The length compared is 5 times the number of
bytes in a sector.
RMODE
CMP 2

200H

RMODE sets raw mode.
CMP compares the first 200 (hex) words
of the source buffer at segment 2, offset 0 with the destination buffer at segment 1, offset 0.

Zilog
10/25/84

'-,.--~.

DBLK

MDCMON

Zilog

MDCMON

decvalue

DBLK decrements the current disk block number by decvalue.
If the decrement would tause underflow (block number < 0), a
warning message is issued and the block number remains
unchanged.
The block number decrement causes MDCMON to change the
cylinder,
head, and sector numbers into the equivalent disk
address, regardless of whether MDCMON is in block or raw
mode.
(See IBLK to increment the current disk block number.)
Example:
SBLK
DBLK

DINT /

Sets block number to 5
Decrements current block
number to 4

EINT

DINT sets MDCMON into polled mode.
Subsequent packet
mands are issued without the Enable-Interrupt bit set.

com-

BINT sets MDCMON into interrupt mode. Subsequent packet commands are issued with the Enable-Interrupt bit set. Default
mode = EINT set.
Example

Descripti.on.

DIN'r
RD 1

2000

Issues read command
in polled mode.

EINT
RD 1

2000

Issues read command
in interrupt mode

DISPLAY dseg doff Inth
DISPLAY displays the contents of memory beginning
at
doff for lnth words.
Default display buffer begins at
<1>0. Default length is 1 word.
Example
DISPLAY 1 0 l00H

Description
Displays 100 (hex) words
beginning at segment I, offset 0

Zilog
10/25/84

DOPKT

MDCMON

Zilog

MDCMON

opcode

cwl

cw2

cw3

cw4

cw5

DOPKT allows the user to issue an arbitrary packet command
to the currently selected disk unit. Refer to Appendix B
for packet command descriptions.
Opcode is sent 'in Command Word 0,
along with the EnableInterrupt bit and/or Sector- Map-Disable bit, depending upon
the current state of MDCMON.
Command words cwl,
cw2,
cw3,
cw4,
and cw5 become the packet-command parameterso MDCMON
initializes opcode, cw1, cw2, cw3, cw4 and cw5 to 0.
Example Command:
DOPKT 10H

2000

This syntax issues the packet command 10 (hex), a
multisector command, to the mWDC.
Command parameters are:
and cw4 = 0.

cwl

2000, cw2

6, cw3

read

DPRINT / EPRINT
DPRINT disables MDCMON informative message printing.
It
does not affect error message printing, which cannot be disabled.
Recommended application:
Enter DPRINT before entering
mand lines with large repeat factors.

com-

EPRINT enables printing of informative messages.
When a
command is parsed, MDCMON may echo information concerning a
command which it will issue to the mWDC.
Default mode = EPRINT

DRDY
DRDY issues a Test Drive Ready packet command to the current
unit.
If the drive is not ready,
an error message is
displayed.
FBLK
FBLK fills the current write buffer with the current disk
block number in hexadecimalo
It fills the buffer with the
exact number of 'words in a sector ..

Zi10g
10/25/84

Zilog

MDCMON

~he current write buffer (wseg
woff)
is filled with 256
·words of the current block number in hexadecimal.
(Refer to
the MDCMON WRITE command for information on setting the
"wseg woff" address.)

FILL

wseg woff Inth fpat

This command fills the write buffer beginning at
with lnth words of the pattern fpat.

woff

Default parameters are:
wseg = 2, woff
Inth = I, fpat

0000H
6db6H

Example Command:
FILL

256

AAAAH

256 words of the pattern "AAAA" (hex) are put into
write buffer beginning at segment I, offset 0.
HALT /

the

NOHALT

HALT causes MDCMON to pause and display a message after any
uncorrectable error occurs during command execution. The
user must then enter a carriage return to resume processing.
NOHALT causes MDCMON to continue processing without pausing
when an uncorrectable error is encountered during command
execution.
Default mode

NOHALT

HALT and NOHALT are effective on all subsequent commands.
Example Command:
HALT
100«WR 3 0 1 50)(RD 2 0 1 50)(CMP 3 0 201»
Any hard errors occurring during execution of the command syntax which follows HALT will cause an error
display and a pause in the read, write or compare process.
MDCMON then prompts the user to enter a carriage return
to resume execution of the command line.

Zilog
10/25/84

MDCMON

Zilog

MDCMON

Example Command:
NOHAL'r
100«WR 3 0 1 50)(RD 2 0 1 50)(CMP 3 0 201»
MDCMON will execute the command
without pausing for hard errors.

following

nohalt

HELP
This command causes MDCMON to display the list of available
commands.
Press the carriage return key to scroll through
the list r one screen at a time.
HOME
The HOME packet command is issued to the mWDC to recalibrate
. the disk drive.
IBLK incval /
IBLK
ICYL
IHEAD
ISEC

ICYL incval /

increments
increments
increments
increments

the
the
the
the

IHEAD incval /

current
current
current
current

ISEC incval

)

block number by incval.
cylinder number by incvalo
head number by incval.
sector number by incvalo

,,--~~

If no parameter value is entered after IBLK, ICYL r IHEAD, or
ISEC,
the the block number is incremented by the last vaLue
entered.
If no previous incval was entered r the default value of 1 is
used.
Whenever the current block number is incremented,
the
current cylinderr
head r and sector numbers are changed to
the equivalent disk addressi and conversely, whenever the
cylinderr
head,
or sector numbers are changed, the current
block number is changed to the equivalent disk address.
MDCMON checks to see if the maximum block number on the
current disk unit will be exceeded before executing an
increment commando
If the maximum will be exceeded,
the
command does not change the current disk address.

Zilog
1~/25/84

MDCMON

Zilog

MDCMON
./'\
Example Command:
(SBLK

5) (IBLK

10)

This command sets the current block to 5 and increments by
10,
resulting in a block number of 15.
The current
cyl inder " head I
and sector numbers are changed to the
equivalent disk address.
ILC

The Incremental Lap Counter (ILC) maintains a lap counter to
simulate running laps. When selected, ILC begins with 1 and
increments the lap counter by Ie
The table invoked by the
REC command displays the lap count.
Description

Example Command
CEC
ILC

Resets lap counter to 1
Increments lap counter to 2

INITMDC
~

MDCMON performs a software reset of the mWDC.
QUIT

MDCMON quits and returns to SADIE.
RAND
RAND

rndseg rndoff rblkcnt (block mode)
rndseg rndoff rwords (raw mode)

rndseg
rndoff
rblkcnt rwords

source buffer segment number
source buffer offset number
words per sector * random block count
random words

MDCMON randomizes the contents of the buffer beginning at
rndoff.
If in block mode, MDCMON fills the buffer
with #words-per-sector * rblkcnt words.
If in raw mode,
MDCMON fills the buf£er with rwords words.
The default random-buffer address is the same as the writebuffer address. The default buffer size is 1 sector, or 256
words.

Zilog
110/25/84

MDCMON

Zilog

MDCMON
/~
\
\,.

Example Command:
BMODE
RAND 2

...

_---

BMODE sets MDCMON to block mode. The next command syntax
fills segment 2, offset 0 with 256 * 5 words of random data.
Example Command:
RMODE
RAND 2

RMODE sets MDCMON to raw modeo The RAND syntax fills segment
2, offset 0 with 5 words of random data.

RBLK / RCYL / RHEAD / RSEe
RBLK
RCYL
RHEAD
RSEC

randomizes
randomizes
randomizes
randomizes

the
the
the
the

current
current
current
current

disk
disk
disk
disk

block number.
cylinder numbero
head number.
sector number.

These commands result in a random disk
within the range of blocks on the disk.

address

that

RBLK randomizes the current physical block number which in
turn
increments or decrements the cylinder/head/sector
count. The new block number lies between 0 and the maximum
block on the disk.
Conversely, when RCYL, RHEAD or RSEC randomize the current
cylinder, head and sector numbers, the physical block number
increments o~ decrements to correspond with the change.

RDDRV
The Read Drive Parameters command is sent to the mWDC.
<1',

RDMAP

rseg

roff

The Read Sector Defect Map packet command is issued
mWDC, and the read buffer begins at roff.

the

The maximum number of entries in a sector defect map is
Each entry is one warde

45.

The entry offset plus the entry is a physical block
where a defect was found by the mWDC during formato
Example Command:
RDMAP 1 0

Zilog
10/25/84

number

READ
READ

MDCMON

Zilog

MDCMON

rseg roff blkcnt blk
rseg roff blkcnt cyl head sec

(block mode)
(raw mode)

This command issues the Read multisector packet
the mWDC.
The read buffer is at roff.
read.

The

blkcnt

command
sectors

to
are

The disk address is either a block number or a
cylinder,
head,
sectoc address;
depending upon whether MDCMON is in
block or raw mode.
rt>'

The default read-buffer begins at <1>0.
The default
number (and cylinder, head, sector numbers) is 0.
Note:

block

RD is a special abbreviation of READo
Example Command:
BMODE
RD 1 0

155

BMODE sets MDCMON to block mode.
The RD syntax causes
a
6 sector read into segment 1, offset 0, beginning at
block 155
0

Example Command:
RMODE
RD 1 0

RMODE sets MDCMON to the raw modeG
The RD ~yntax
causes a 6 sector read into segment 1, offset 0, beginning at cylinder 7, head 0, sector 2.

Zi10g
10/25/84

MDCMON

Zilog

SBLKCNT blkcnt /
SBLKCNT
IBLKCNT

MDCMON

IBLKCNT blkinc

sets the current block count to blkcnt.
increments the current block count by blkince

Default blkcnt is 0001H, and default blkinc

Example Command:
SBLKCNT
SBLK 0
100«WR

50
3

0)(RD

0)(CMP

0)(IBLK

1»

All the commands above use a block count of 50, because
the SBLKCNT command sets it to 50, and no block counts
are specified in any of the WR, RD or CMP commandso
Example Command:
IBLKCNT 50
100«WR 3

0)(RD

0)(CMP

0)(IBLK

1»

The block count was set to 50 in the first example, and
increments by 50 in this example, resulting in a
block count of 100 for the ensuing WR,·RD, and CMP commandso

"- _.A

SBLK blk / SCYL cyl / SHEAD head / SSEC sec
SBLK sets the current block number to bIke SCYL, SHEAD and
SSEC set the current cylinder, head, and sector numbers to
cyl, head, and sec values, respectively.
MDCMON always changes the block-mode disk address to the
equivalent
raw-mode address whenever the block number
changeso Similarly, it changes the raw-mode disk address to
the equivalent block-mode address whenever the cylinder,
head, or sector number changes.
Default values for all four commands are the last parameters
used for that command or 0 if no parameter has been entereda
Example Commands:
SCYL 5
SHEAD
0
SSEC 14
SBLK 0
The SBLK command sets the block number to 00
It
sets the cylinder, head, and sector numbers to 00

Zi109

10/25/84

also

1../
\_
.

MDCMON

Zilog

MDCMON

SDRIVE
SDRIVE prompts the user for the correct number of physical
cylinders and heads, and the reduced write current cylinder
number for the current disk unit.

SEEK

blk

(block mode) SEEK

cyl

(raw mode)

The Seek packet command is issued to the mWDC.
cial abbreviation of SEEK.
Example Command: SK

SK is a spe-

If in raw mode, MDCMON requests the mWDC to seek to
cylinder 5.
In block mode, the mWDC is asked to seek
to block 5.

SHIP
·SHIP moves the disk drive heads
to
the
zone, which is the innermost cylindero
SMD

shipping/loading

SME

SMD requests MDCMON to issue all subsequent packet commands
In this mode, the mWDC interin Sector-Map-Disable modeo
prets the block number as a
physical block number rather
than a
logical block numbero
lise of this command provides
the only direct access !£ physicar-cyr±nder 0~
requests MDCMON to issue all subsequent packet commands
in Sector-Map-Enable mode9
All block numbers in packet commands are interpreted by mWDC as logical block numberso
The
mWDC uses the Sector Defect Map to translate the logical
block number into the appropriate physical block number.
SME

MDCMON uses SME mode by defaulto
NOTE

After the disk has been formatted,
the drive
parameters and defect table reside in 0 and I,
respectively, on all heads in physical cylinder 00
If SMD mode has been previously entered, commands
which invoke random block numbers and do writing
could destroy the contents of physical cylindero
Physical cylinder 0 is only vulnerable t~ write
operations invoked in the monitor when SMD mode
has been entered.

Zi10g
10/25/84

MDCMON

. Zilog

MDCMON

Example Command:
SMD
RD 1

This command reads physical block 0 on the current
unit, which is the first sector on cylinder 0, head 0.
Example Command:
SME
RD
This command reads logical block 0, which is not the
same address as physical block 0, because cylinder 0 is
reserved for the·Sector Defect Map and for diagnostics.

SMEM maxseg
This command sets the largest memory segment number available to MDCMON.
Any commands that increment the read or
write segment numbers check against th~ "maxseg" value for
possible overflow.
Example Command:
SMEM 15
STATUS

MDCMON displays the current status of the current disk unit,
including:
1.
2.
3.
40

5.
6.

The unit number
The mode, block or raw
The current disk address in both block number
and cylinder, head, sector representations
The drive parameterso Indicates the number of
blocks, cylinders, heads and sectors
The dispatch word in the packet
All five command words in the unit's subpacket
ao
Command Word 0 -- opcode
+ Enable-Interrupt bit
+ Sector-Map-Enable bit
+ Soft-Error bit
b.
Command Word 1
Block number
c.
Command Word 2
Block (sector) count
d.
Command Word 3
Transfer address bits 0-15 (Offset)
eo
Command Word 4
Transfer address bits 16-31 (Segment)
f.
Command Word 5
Interrupt vector Command Completion
Status

Zi10g
10/25/84

Zilog

MDCMON

SUNIT

~1DCMON

unit

This command sets the current unit number.
All
subsequent
oacket commands issued to the mWDC are set into the sub~acket for the current unit, and the dispatch word bits for
the current unit are set to command-pending.
The default unit number is unit 0.
Example Command:
SUNIT 1
WRITE
WRITE

wseg woff blkcnt blk
(block mode)
wseg waff blkcnt cyl head sec
(raw mode)

The Write multisector packet command is issued to the mWDC.
The write-buffer begins at woff and is blkcnt sectors
long.
In block mode, "blk" represents a block number.
In raw mode, the syntax "cyl head sec" represents cylinder,
head p
and sector numbers. WR is a special abbreviation of
WRITE.
Example Command:
BMODE
WR 1

200

BMODE sets the block mode.
The WR syntax writes to
block 200.
MDCMON converts the block number into the
equivalent cylinder, head, and sector numberse
Example Command:
RMODE
WR 1

200

RMODE sets raw mode.
200.

The WR syntax writes to

The head and sector number values carryover
first WR ..

cylinder
from

the

1.5. Error Messages
~

The ensuing subsections explain conventions used in this
text to define possible MDCMON error messages, and provide

Zi10g
10/25/84

MDCMON

Zilog

error message examples and interpretations. Information
the "error statistics table is also included.

Refer to Appendix C for error status code descriptionso
Information on SADIE initialization and self test error messages is found in MDCCRC documentation.

1.5010

Error Description Conventions

conventions used to describe possible error messages are:
Non-variable messages such as "DISK="
are
shown
as
displayede Variable information which further defines error
types is indicated within"<
>" symbols;
,
for example.
Disk unit and logical block
addresses, data patterns,
cimal numbers.

numbers are decimal numbers~
and buffer contents are hexade-

Any of the messages listed below
:

may

appear

place

"Wait Abort"
"Parity"
"Write Fault"
"Seek Not Complete"
"Cylinder Not Found"
"Drive Not Selected"
"Block Not Found"
Invalid Command"
No Track 0 Found"
Drive Not Ready"
Bad Interrupt"
Bad Defect Map"
Illegal Cylinder"
Burst Error"
Read Abort"
Unknown"

Zi10g
10/25/84

'''-"

MDCMON

Zilog

MDCMON

A brief description of the error message source follows each
error listed in the following text.
HARD ERR-- DISK= PACKET CMD=
The mWDC returned an uncorrectable error status in Command
Word 5 status field upon completion of a packet commando
Example Display:
HARD ERR--Burst Error

DISK=0, 200

PACKET CMD=10

This error message indicates
an uncorrectab1e Burst
Error
(data error) occurred while reading disk unit
0, block 2000
The opcode for the Read
mu1tisector
packet command is 10 (hex).
SOFT ERR--Burst Error

DISK=l, 1333

PACKET CMD=ll

This error message indicates a
correctable Burst
Error
(data
error)
occurred
while writing disk
unit 1, block 1333.
The opcode for the Write multisector packet command is 11 (hex).

CMP ERR

DISK= ADDR= GOOD= BAD=

A mismatch was found when a source buffer containing a pattern- written to a sector was compared with a destination
buffer read from that sector. The corrupted data read from
the destination buffer is displayed after "BAD".
Example Display:
CMP ERR

DISK=0, 0 ADDR=8000

GOOD=b6db, BAD=ffff

The mismatched data was: b6db (hex)
in the source
buffer and ffff (hex) in the destination buffer. The
offset address of the destination buffer was 8000
(hex).
The current disk address
(and presumably the
last disk block read) is unit 0, block 0.

Zi10g
10/25/84

MDCMON

Zilog

MDCMON

.J
\ ....

le6.

Error Statistics

MDCMON is an interactive monitor, and as such, does not run
laps and display a lap summarYa Use of the REC (Read Error
Counters) command, however, provides a table of statistics
which contains error informationo Refer to Appendix C for
more information on the table of statistics.
To see error statistics for the currently
unit:
Enter REC (Read Error Counters)

selected

disk
W

To see error statistics for any other unit:

Displays statistics for
disk unit named, regardless
of selected unit.

Enter REC [unit i]

To clear error statistics for the
unit:

currently

selected

disk

Enter CEC (Clear Error Counters)
To clear error counters for a non-selected unit:.

.J
,---

Enter CEC [unit i]

Zilog
10/25/84

MDc'rEST

Zilog

1010

MDCTEST

MDCTEST is a pair of DATA-DESTRUCTIVE random
mini-Winchester Disk Controller (mWDC).

tests

the

1G2 Parameters
Parameter 1 =
Parameter 2

1~3o

unit to be tested.

(default: unit = 0)

test number to be performed.
If test# = 1, test 1 is performed.
If test# = 2, test 2 is performed.
(default: test# = 1)

MDCTEST Overview

MDCTEST consists of two tests, each of which is described
belowo
The test to be performed is selected by parameter 2.
If an invalid test number is in parameter 2, test 1 will be
performed.
Before either test begins, MDCTEST issues a software reset
command to the mWDC.
If the mWDC does not respond to the
reset or fails "to pass its self-test, a message is displayed
and MDCTEST aborts the testa Otherwise, MDCTEST issues a
mWDC firmware identifier read command to determine the
firmware version.
The selected test repeats the number of times
#REPS in the test 1ineo

specified

The disk drive heads move to the inner most cylinder"at
end of the test.

1.4.

as
the

Test One

Test I is a random seek test.
Initially, test 1 creates a
queue of 128 random logical disk sector addresseso Associated with each element of the queue is a unique single sector source buffer in memory segment 1 and destination buffer
in segment 2. All 128 source buffers are filled with random
data.

Zi10g
10/25/84

Zilog

MDc'rEST

MDCTEST

)
\,

Then for each repetition of test 1:
1.

All 128 source buffers are written to their
disk sectors.

For each disk sector number in the queue:

associated

The sector is read into the associated destination
buffer ..

The source and destination buffers are comparedg

CII

A
new random sector number is generated and
checked for uniqueness against all other sector
numbers in the queue .. If it is not unique, another
random sector number is generated,
and so on.
When a unique number is found, it replaces the old
sector number in the queue
0

The associated source buffer is re-randomizedo

Test I displays an error message for all disk read,
disk
write and compare errors. On all write and read error messages, the disk address, a description of the error, and the
disk command (read or write) are shown.

.~
"-,-

Compare error messages show the last disk sector address
read and the data in both the source and destination buffers
where the mismatch occurred. The segment offset where the
mismatch occurred is also showno

1 .. 5..

Test Two

Test 2 is a test of random-length writes and readsQ
Initially,
memory segments 1 through 3 are set to a background
pattern, 'AAAA'.
Then, for each lap, the' following series
of steps repeat 50 times:
I..

A source buffer is randomly chosen which is a random
multiple of the sector length, up to 64 sectors.
The
source buffer may cross segment boundaries, but must be
wholly contained within segments 1 through 3. The
source buffer is filled with random data.

A destination buffer of the same length as the source
buffer is randomly allocated.
The same restrictions
apply to the location of this buffer as to the source
buffer,
and, in addition, it must not collide with the
source buffer ..
\

Zi10g
10/25/84

'---.-'

MDCTEST

Zilog

A random disk sector address is found, such that writing the source buffer beginning at that sector will not
overflow the disk pack.

4. . The source buffer is written to the disk address;
the
disk address is read to the destination buffer~ and the
write and read buffers are comparedm

The source and destination buffers are filled with
background pattern.

the

Segments 1-3 are checked for corruption in the area
outside the two buffers which may have occurred during
the write or read.

Test 2 displays and logs an error message whenever it
encounters a read, write, or compare error. The error message format is the same as that for test 1 errors.
1.6e

Error Messages

MDCTEST displays an error message whenever an mWDC initialization error or self-test error occurs. These error messages
are described in MDCCRC documentation.
Error messages which may be displayed during MDCTEST are
described in the following text.
Information in boldface
type represents the error message as displayed.
Variable
values are shown enclosed in < > symbols.
One of the following messages
place of .

will

displayed

"Wait Abort"
"Parity"
"Write Fault"
"Seek Not Complete"
"Cylinder Not Found"
"Drive Not Selected"
"Block Not Found"
"Invalid Command"
"No Track 0 Found"
"Drive Not Ready"
"Bad Interrupt"
"Bad Defect Map"
"Illegal Cylinder"
"Burst Error"
"Read Abort"
"Unknown"

Zi10g
10/25/84

MDCTEST

Zilog

Test 1 and Test 2 display the following error messages whenever an error occurs:
TEST 1 ERROR MESSAGES
HARD ERR--

DISK= WRITE SECTOR

The mWDC returned an uncorrectable error status upon completion of a write packet command.
SOFT ERR--

DISK= WRITE SECTOR

The mWDC returned a correctable error status upon completion
of a write packet command.
HARD ERR--

DISK=

READ SECTOR

The mWDC returned an uncorrectable error status upon completion of a read pa~ket command.
SOFT ERR--

DISK=

READ SECTOR

This message has a similar meaning as the previous message,
but indicates the error status was for a correctable error.
CMP ERR IN BUFFERS: SRC= DST=
ORIG BUFS: WR RD
L= DISK=
This 2-line error message indicates a compare error occurred
when comparing a
source buffer written to a destination
buffer read from the same disk block.
The exact segment and offset addresses and the mismatched
data found there are displayed following SCR and DST.
The start address of the source and destin~tion buffers follow WR and RDo
The buffer length in words is shown after
1

Zi10g
10/25/84

MDCTEST

HARD ERR--
SECS

~iDCTEs'r

Zilog

DISK=(uniti,blockt)

WRITE

The mWDC returned an uncorrectable error status upon completion of a write multisector packet command.
SOFT ERR--
SEeS

DISK=(uniti,blockl)

The mWDC returned a correctable error status upon completion
of a write multisector packet command.
HARD ERR--

DISK= READ

SEeS

The mWDC returned an uncorrectable error status upon completion of a read multisector packet command.
SOFT ERR--

DISK= READ <'sectors> SEeS

The mWDC returned a correctable error status upon completion
of a read multisector packet commando
,~\

CMP ERR IN BUFFERS: SRC=
offsetl>=

DST RD L= DISK=
This 2-line error message shows that a mismatch occurred
when comparing a buffer written with a buffer read from the
same disk address. The message fields are the same as for
the compare error message for test 1.
CMP ERR IN BACKGR: SRC=
DST=
ORIG BUFS: WR RD
L= DISK=
This 2-line compare error message shows that a mismatch
occurred upon comparison of two words in 'background'.
Background is defined as all memory in segments 1-3 outside
of the current write and read buffecse
This error indicates that the last multisector read package
command caused corruption of memory locations outside the
intended read buffer.

Zilog
10/25/84

Zi109

MDCTEST

,)
The background locations with the mismatched data follow SRC
and DST.
The current write and read buffer addresses are
shown after WR and RD, respectively, followed by the buffer
length in words ..

1.7.

Lap Summary

A lap summary is displayed at the conclusion of each lap of
MDCTESTo
The lap summary is a table of statistics that is
cumulative for all laps completed so far in the current run
of MDCTEST. Refer to Appendix C for more information on lap
summaries.

Zilog
10/25/84

,~~

1.1.

MMUTST

Zilog

MMUTST

MMUTST performs a series of tests on the Code,
Stack Z8010 Memory Management units (MMUs).

Data

and

Each test begins with a message which announces the test and
cites the type of CPU board (HPCPU or other) to be tested
and whether the operating system is segmented or nonsegmented.
Tests run in the order listed below unless otherwise
fied:

speci-

A CONTROL register test, where random data is written
to each control register, then read and verified.

A random data and random access
Descriptor Registers (SDRS).

3 ..

A block random data test of all SDRs.

A test of the LIMIT registers ..

test

the

Segment

"5555" and "AAAA" data test on all SDRs.

test of the READ-ONLY flags.

A test of the DIRW (direction and warning) flags.
8.

An address translation test
test:

which

uses

each

SDR

- Data accesses for DATA and STACK MMUs
- Instruction accesses for the CODE MMU

1.2.

Error Messages

MMUTST reports all errors to SADIE as HARD errors.
Error
messages
which indicate where the MMU error occurred
display whenever an access violation causes a segment trap ..

Zilog
10/25/84

MMUTST

Zilog

MMUTST

)
103.

Lap Summary

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

On completion of each repetition of the series of tests,
MMUTST displays the lap number, error count, and for each
MMU:
1.

The number of block data errors.

The number of random SDR errors ..

3 ..

The number of "5555" and "AAAA" data errors ..

The number of these control register errors:
Segment Address Register (SAR)
Descriptor Selection Counter Register (DSCR)
Mode Register

The number of access violations of the following types:
a.

read only

limit

direction

translation

For information about the MMUs, refer to:
Z80l0 Z-MMU Memory Management Unit Product
Specification, March, 1981

Zilog
10/25/84

Zilog

SCCTST

1.1.

SCCTST

This text provides:

1.2.

an overview of the four tests which make up SCCTST

set up and user interaction information

sequential screen displays

detailed test and error message descriptions
Overview

SCCTST is an interactive test of the HPCPU onboard Serial
Communications Controller (SCC), and related modem signals.
The test is intended only for use on systems with an HPCPU
board.
SADIE requires no parameter entry for this interactive test,
and errors are summarized at the end.of each test within
SCCTST, rather than in a lap summary •
.~

SCCTST tests these SCC functions:

Character transmission, local loop mode

Character transmission, polled mode

+
+
+
+
+
+
+

Character transmission, interrupt mode
SCC modem signals (RTS, CTS, DTR, nCD), polled mode
SCC modem signals, interrupt mode
Transmit interrupts
Receive interrupts
External status interrupts
Character transmission at all standard baud rates

Zilog
10/25/84

SCCTs'r

Zilog

SCCTST

After port selection; the four tests described below automatically run in the order shown unless the user responds when
prompted with an entry which returns to the SCCTST menu or
ends all tests (refer to Paragraph 1.301).
Ie

Local Loop Mode Character Test

Tests SCC character transmission in local loop
mode at 9600 Baud

Polled Mode Character/Modem Test

Tests character transmission and SCC modem
signals at 9600 Baud

Modem/Character Interrupt Test

Tests character transmission at 9600 Baud
in
interrupt
mode
where "status affects
vector" is true.
Tests:

Interrupt Mode Character Test

SCC modem signals
Transmit Interrupts
Receive Interrupts
External/Status
Interrupts

Tests character transmission
in
interrupt
mode
where "status affects
vectors" is true.
Tests
all
baud rates.

1030

standard

Test Sequence

This sUbsection provides a description of the sequence of
events which follows SCCTST initiation.
Subsections 1.6,
1.7, 108 and 1.9 describe individual test results which are
output to the console screen.
The see port selected for test is configure~ to loop
transmission and control signals back to the same porto
The four tests will run
port until a console
occurso

continuously for either selected
key is pressed, or until an error

Zilog
10/25/84

2·

SCCTST

Zilog

SCCTST

NOTE
Do not press the system START button for a non
maskable interrupt (NMI) while the test is running. Console I/O is redirected following SCCTST
menu test selection, and an attempted NMI could
disable the system.
1.3.1.

SCCTST Screens

After SADIE initiation and
displays:

- -

SCCTST

selection,

the-

console

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

Checking Test List
This is a test of HPCPU on-board serial I/O (TTY) ports
It tests the selected TTY port for:
1. Local loop mode transmission at 9600 Baud
2. Polled mode modem controls and transmission at
9600 Baud
30 Interrupt mode modem controls and transmission
at 9600 Baud
4. Interrupt mode transmission at six baud rates

Console I/O is redir~cted during parts of the test.
Therefore DO NOT PRESS START BUTTON during test,
unless waiting for a main menu response (below).
To exit, enter "Q" in response to test prompts.
NOTE: THIS TEST REQUIRES SPECIAL SERIAL I/O
NULL MODEM PLUG (SEE DOCUMENTATION IN
SYSTEM 8000 SADIE REFERENCE MANUAL)
0

Zilog
10/25/84

SCCTST

Zilog

)
The menu that provides port selection appears next.
At this
time SCCTST allows the user ,to pre~ the ,system START (NMI)
key' for· ?AUS~ ~ a'ccesS:--

SELECT
A =
B =
Q =

'-~

PORT TO BE TESTED:
DIAGNOSTIC PORT (TTY0)
CONSOLE PORT (TTYl)
END ALL TESTS

ceo·

If any key other than A, B or Q is pressed,
SCCTST
the following message, then returns to the menu:

issues

Invalid Choice -- Try again!!
Following an acceptable menu selection, SCCTST provides connector installation instructions for selected port "A" or
"B", or returns to the SADIE menu in response to menu
choice"QII.

'\.-_.-

1.4..

Set Up

SCCTST requires no HPCPU modifications,
but does require
installation of a
specially wired connector to carry the
modern signals.
Test one, the local loop mode test,
will
function with or without the connector.
The connector is installed in the I/O panel TTY 0 port to
test SCC channel A (the diagnostic port), or TTY 1 port to
test SCC channel B (the console port).
Connector P3 of the rep test cable Zilog PN 59-0327, Rev. B,
is intended for use as th~ "null modem plug" referenced in
this test. The standard RS232, 25 pin male connector which
carries the modem signals is modified to a loop configuration:
Signal
Xmit Data
RTS
DSR

Pin#

Signal

4
6

Receive Data
CTS
DTR

Pin#

jumper to

SCCTST refers to pin 6 (DSR by RS232C standards) as DCD.

,J
.'..---.....--..

Zi10g
10/25/84

SCCTST

Zi10g

Following port selection, the program prompts for
cable and/or connector changes.
To ensure proper test function, follow
the order described be10we
1.4.1.

program

necessary
prompts

Port A Cable Connections

Port A has been selected from the menu, and SCCTST prompts:
Now connect null modem plug to TTY 0
Hit R when ready or S to return to menu
Or Q to end all tests
Install P3 of the ICP cable in the HPCPU I/O panel
port at this time, then press "R" to begin the test.
1.4.2.

TTY

Port B Cable Connections

Port B has been selected from the menu, and SCCTST prompts:
Plug console terminal into TTY 0
Type R when ready
Respond to the prompt in this way:
Ie

Remove P3 (the null modem plug), if present,
from
TTY0, and disconnect the console cable from TTY 1.

Connect the console I/O cable to the TTY
then press "R" on the console keyboard.

port,

The next prompt instructs:
Now connect null modem plug to TTY 1
Hit R when ready, or S to return to menu
or Q to end all tests
To begin Test 1 on SCC port B (console port), connect P3 of
the test cable to
the I/O port labeled TTY I, then press
n

R" •

Zi10g
10/25/84

SCCTST

Zilog

SCCTST

Error Message Conventions

1.5.

If an error occurs:
1.
2.
3.
40

The
The
The
The

console "beeps".
test stops.
program displays an error message.
port selection menu returns.

After each test description in this text,
pertinent error
messages are shown in ·boldface type, followed by a brief
description of the error source.
Values shown after CHAR= refer to 8-bit ASCII characters.
The value shown for TTY represents the sec channel selected
for test.
Status refers to read register 0 contents for the
selected porto
sce read register 0 status bit definitions are~
ID7ID6\DsID4ID3ID2\DIID01
.
----------------------.

Rx character available
Zero count
Tx buffer empty
DCD
SYNC/HUNT
CTS
Tx UNDERRUN/EOM
BREAK/ABORT
For more information on sec registers, refer to the
Zilog Components Data Book.

I.S.1e

) ......

\...

current

Display Description Conventions

In this text, messages identical to those seen on the console screen are reproduced in boldface type.
Variable data
is shown inside < > sy~bols.

1.6.

Local Loop Mode Test

When the proper connectors are in place (refer to Subsection
104), press "R" to begin tests 1 through 4. The first test
is the local loop mode test which prompts:
LOCAL LOOP MODE TEST, TTY0
HIT ANY CHARACTER TO GO ON TO NEXT TEST

Zilog
10/25/84

SCCTST

Zilog
I~\

At this point, allow the test to run, or enter any character, including the space bar, to skip this test and go on to
the polled mode character test.
The test runs in the asynchronous mode at 9600 baud with bit
4 of write register 14 set. One test cycle is complete when
256 characters have been successfully transmitted.
A summary of errors and characters transmitted since test
initiation for the current port selection displays at the
end of each test cycle:
LOCAL LOOP TEST ON TTY#: CHARS, ERRORS
The error count represents the number of times the character
received differs from the character transmitted.
Paragraph 1.6.1 discusses error messages which may interrupt
the test.
1.6.1.

Local Loop Mode Test Error Messages

All error messages are preceded by an audible 'beep'. Conventions and status code definitions found in Subsection 1.5
apply to the error descriptions below.
LOCAL LOOP MODE ERROR MESSAGES
NO CHARACTER RECEIVED, LOCAL LOOP MODE, TTY, CHAR=
The ASCII character shown after CHAR= was transmitted, but no
character was received.
CHAR MISMATCH, LOCAL LOOP MODE, TTY<#>, OUT = <##>, IN = <##>
OUT= character transmitted
IN= next character received

1.7.

IN and OUT do not match.

Polled Mode Test

The polled mode test transmits 256 ASCII characters at
baud with the sec in polled mode, and then displays:

9600

POLLED TEST ON TTY<#>, <###> CHARS, <##> ERRORS
/;~~\

CHARS represents
transmitted.

the

total

number

Zilog
10/25/84

ASCII

characters

SCCTST

Zilog

SCCTST

The error count represents the number of times the character
received differs from the character transmitted.
Both totals are cumulative from the beginning of the current
SCC port test:
the message remains constant on the screen
while the totals increment.
The test continues to cycle until a character is entered via
the console.
1.7.1.

Polled Mode Test Error Messages

All error messages are preceded by an audible
'beep'. Conventions and status code definitions found under Subsection
1.5. apply to the errors described below.
When error messages occur during the polled mode test, check
the "null modem plug" for broken jumper wires or loose pins.
POLLED MODE ERROR MESSAGES
NO CHARACTER RECEIVED, POLLED MODE, TTY, CHAR=<##>
The character represented by CHAR was transmitted asynchronously at 9600 baud, but no character was received.
CHAR MISMATCH, POLLED MODE, TTY<#>, OUT

<##>, IN = <#i>

The character shown after OUT was transmitted, and the
character received was that shown after INo
MODEM ERROR STATUS

, oeD AND/OR CTS SET, TTY

When testing transmit modem signals in the polled mode,
RTS
and DTR were reset,
but DCD and/or CTS failed to reset.
(Check P3 of the rcp test cable for broken wires or loose
(?inso)
MODEM ERROR STATUS

CTS NOT BACK ON, TTY<#>

During (?olled mode modem signal testing, RTS was set high~
DTR was set low.
The ex(?ected RS232 line conditions did not
occuro
Expected test results:
DCD low
CTS high
MODEM ERROR STATUS = ,
TTY<#>

DCD

NOT

BACK

ON,

During polled mode modem signal testing, DTR was set high;
CTS was set low, and expected RS232 line conditions did not
occur.
Expected test results:
DCD high
CTS low

Zilog
10/25/84

,~
,~

108.

SCCTST

Zilog

SCCTST

Modem Interrupt Test

A successful modem/character interrupt test transmits 256
ASCII characters at 9600 baud, then displays this summary:
MODEM INTERRUPTS ON TTY:
CHARS represents
transmitted.

the

total

CHARS,
number

ERRORS
ASCII

characters

The error count represents the number of times the character
received differs from the character transmitted.
Both totals are cumulative from the beginning of the current
SCC port test:
the message remains constant on the screen
while the totals incremento
The test continues to cycle until a character is entered via
the console.
1.8.10

Modem Interrupt Test Error Messages

All error messages are preceded by an audible
'beep'. Conventions and status code definitions found under Subsection
1.50 apply to the errors described below.
MODEM INTERRUPT ERROR MESSAGES
CTS INTERRUPT NOT RECEIVED, TTY, STATUS=
RS232 signals RTS and DTR were reset during modem signal
interrupt mode testing.
A subsequent' DCD and CTS reset
should then have generated an interrupt, but failed to do
so. '
Note:
If both polled mode and interrupt mode modem tests
fail,
carefully check the wiring inside P3 of the test
cable.
If only one modem test fails, the sec is the probable cause.
CTS NOT SET/DCD CLEARED AFTER RTS SET, TTY<#>, STATUS=
An interrupt occurred following RTS and DTR reset,
and CTS did not reset.

but

DCD

oeD INTERRUPT NOT RECEIVED, TTY, STATUS=
~

DCD was set

true~

DTR was

set~

yet interrupt did not occur.

Zilog
10/25/84

SCCTST

Zilog

SCCTST

STATUS=

DCD NOT SET/CTS RESET AFTER DTR SET, TTY<#),

--.

DTR was set and the interrupt occurred, but the expected DCD
true and CTS false status did not occur.
NO CHAR RECEIVED, MODEM INTERRUPT TEST, TTY<#>
STATUS=

CHAR=<##>

An SCC character-received interrupt failed to occur during
interrupt mode modem testing.
CHAR= character which failed
to transmit.
CHAR MISMATCH, MODEM .INT TEST, TTY<#>,

OUT =<##> IN =

The value after OUT = is the character transmitted, and the
value after IN = represents the next character received.
MODEM LINES DROPPED ON TTY<#>

STATUS=

An external/status interrupt - which indicates a
change in
one of the modem signal states - occurred during character
transmission.

NO TRANSMIT INTERRUPTS, MODEM INT TEST, TTY<#>, STATUS=
No transmit buffer empty interrupts have occurred on
transmit modem during transmission of 256 characters.
le9.

the

Interrupt Mode Test

The interrupt mode test uses 'character received' interrupts
to signal receipt of each character, and 'transmit buffer
empty' to signal character transmission.
Characters from 00 to FF are transmitted at
baud rates:

19200
9600
4800

these

standard

1200
300

110

The test transmits 256 ASCII characters at each of the baud
rates listed above, reducing the number of characters sent
as the baud rate decreases.
The display updates accordingly:
SPEED = BAUD,

Zilog
10/25/84

TEST CYCLE

'\~
..'.
'-... -

SCCTsrr

SCCTST

Zilog

1--""'",
When a console key is pressed to terminate
message appears:

the

test,

this

SPEED = BAUD, TEST CYCLE <#> LAST CYCLE
The current test cycle is completed, then this summary is
displayed:
INTERRUPT TEST ON TTY<#>:
.

CHARS represents
transmitted .

the

<###>CHARS,

total

number

<##> ERRORS
of

ASCII

characters

Interrupt Mode Test Error Messages

All error messages are preceded by an audible
'beep'. Conventions found under Subsection 1.5. apply to the interrupt
test errors described below.
INTERRUPT MODE ERROR MESSAGES
TRANSMIT INTERRUPT NOT RECEIVED, TTY# , CHAR=
The transmit buffer empty interrupt failed to
interrupt mode testing.

occur

during

RECEIVE INTERRUPT NOT RECEIVED, TTyt, CHAR=
Character received interrupt failed to
mode testing ..

occ~r

during interrupt

CHAR MISMATCH, INTERRUPT MODE, TTYi, OUT=<##>, IN=<##>
The OUT value represents the character transmitted7
value represents the next character received.

Zilog
10/25/84

the

seeTST

1.10.

Zilog

seeTST

Special Error Condition

The error message shown below represents an interrupt which
should not occur as a result of any currently implemented
sec test:
ERROR:

SPECIAL RECEIVE CONDITION INTERRUPT

The message indicates that the sec modem believes it detects
a serious error condition such as a parity or framing error.

)

"--...

....

Zilog
10/25/84

SIOMODEM

1.1.

SIOMODEM

Zilog

SIOMODEM

SIOMODEM is a test of the Serial Input/Output Controllers
(SIOs), including modem·signalso SIOMODEM is an interactive
test~ it receives no parameters from SADIE.
Errors are summarized at the end of the test rather than in a lap summary.
8IOMODEM tests the following SIO functions:
~

Character transmission, polled-mode

Character transmission, interrupt-mode ("status affects
vectors" is false)

Character transmission, interrupt-mode ("status affects
vectors" is true)

SIO modem signals (RT8,DCD,DTR,CT8), polled-mode

810 modem signals, interrupt-mode

Transmit interrupts

External status interrupts

Character transmissions, mismatched baud rates

Character transmission at all standard baud rates

The tests are arranged in three different test sequences,
all of which are performed for each selected 810 port pair.
The tests are:

The polled mode test, which performs
transmission and 810 modem signal test.

The interrupt mode test, which performs a character
transmission test in the interrupt-mode, where "status
affects vectors" is false. It tests character transmission of mismatched baud rates, and tests all standard
baud rates.

The modem control test, which performs a character
transmission test in the interrupt-mode, where "status
affects vectors" is tru97 and tests 810 modem signals,
transmit interrupts, and external status interrupts.
This test is recommended for extended testing, since it
tests for the greatest number of possible errorso

Zilog
10/25/84

character

SIOMODEM

Zilog

SIOMODEM

SIOMODEM prompts for the appropriate SIO cable connections.
The program presents a menu appropriate to the type of CPU
board in use ..
For example, the menu presented for systems that use a CPU
board other than the HPCPU references console and diagnostic
po~t tests~ the menu for systems with an
HPCPU board does
noto
When an HPCPU board is installed in the system under test,
SIOMODEM tests only the 8SB board portso
(Use SCCTST for
HPCPU on-board serial I/O testingo)
Each test continues indefinitely, until a console key is
pressed to terminate the testo
(To prevent execution of
inadvertent menu choices, do not type ahead$)
All errors produce an audible "beep" and a message on the
console screen explaining the error. A "beep" also signifies that the program expects input from the consolev
NOTE
Do not press the system START button

for

non-

maskable interrupt (NMI) while the test is runninge Console I/O is redirected during SIOMODEM
execution,
systeme
102.

and an attempted NMI could disable the

Set Up

SIOMODEM requires a null-modem cable to carry the modem signals between SIO portso
The interconnecting cable is terminated with two
RS232, 25-pin male connectors, wired as follows:
A

xmitted data
rcvd data
RTS
DSR

CTS
signal ground
DTR

------

standard

B
3

3 ----- 2
4 ----- 5
6 ----- 20
5 ----- 4

7 ----- 7
20 ------ 6

received data
transmitted data
CTS
DTR
RTS

signal ground
DSR

Only the signals listed should be wired ..
Pin 6, DSR in
RS-232C standards, is referred to as DeD in this test ..

Zilog
10/25/84

the

Zi10g

SIOMODEM

If a null modem cable is not available, modem tests cannot
be
performed,
and SIOTEST diagnostics should be used
instead.
The program prompts
for
cable
connections
corresponding to the ports selected for testo
1.2.1.

User Interaction When an HPCPU Board is Not Used

When testing a system with a CPU board other than the HPCPU,
CPU board SIO ports as well as SSB board DART ports may be
tested.
The program first prompts for board selection, then
for port pair connection.
For example:
SELECT TEST TO BE PERFORMED:

o = CPU BOARD ONLY (TTY 0 - TTY7)
1 = SSB-l BOARD ONLY (TTY 8 2
SSB-2 BOARD ONLY (TTY16 3 = SSB-3 BOARD ONLY (TTY24 4 = SSB-4 BOARD ONLY (TTY32 5 = ALL BOARDS (TTY0 - TTY39)

~.'

TTY15)
TTY23)
TTY31)
TTY39)

If "0" is selected, SIOMODEM prompts for null modem cable
connection between ports 2 and 6 and tests those ports~ then
repeats prompts for port pair 3 and 7:
NOW CONNECT TTY3 WITH TTY7
HIT nR n WHEN READY, OR US" TO SKIP THIS TEST
OR "Q" TO END ALL TESTS
An "S" response proceeds to the next TTY pair, while
entry returns the SADIE executive test menu~

"Q"

To test ports 3 and 7, connect the null modem cable to those
ports and press "R"o
On test completion, SIOMODEM prompts:
DO YOU WANT TO MOVE CONSOLE PORT TO ANOTHER PORT SO SIOMODEM
CAN TEST PORTS ?
TYPE VALID PORT NUMBER (0-39) FOR NEW CONSOLE PORT, OR 99 TO
SKIP TEST
A "99" entry returns the SIOMODEM test menu.
To test
untested ports, including TTYl, enter the number of a previously tested port, and connect the console cable to that I/O
port when prompted:
PLUG CONSOLE TERMINAL INTO

TYPE "R n WHEN READY

Zi10g
10/25/84

SIOMODEM

Zi10g

SIOMODEM

Type "R" as prompted, and SIOMODEM prompts:
NOW CONNECT TTy WITH TTYo
HIT "R W WHEN READY,. OR uSn TO SKIP THIS
OR "Q" TO END ALL TESTS

T~ST

Use the null modem cable to interconnect
prompted,
then enter "R"~
or enter "S" to
next untested port paira
SIOMODEM then
selected channel as the console, and tests
when the console was TTY 1.

the ports as
proceed to the
programs
the
ports deferred

When the test is complete, the program prompts for return of
the console to its original channel.
Remove the null modem
cable, and reconnect the console cable to the I/o panel TTYI
port to continue testing.
PresS "R" as prompted, then, on
test completion, press "Q" to return to the SADIE executive
command menu ..
1.2.2.

User Interaction With an HPCPU Board in the System

When the program detects an HPCPU board, it prompts for
board selection:
1 = SSB-1 BOARD· ONLY
2 = SSB-2 BOARD ONLY
3 = SSB-3 BOARD·· ONLY
4 = SSB-4 BOARD ONLY
5 = ALL BOARDS (TTY2

8SB

(TTY2 .... TTY9)
(TTY10 - TTY17)

(TTY18 - TTY25)
(TTY26 - TTY 33)

- TTY33)

When "5" is entered to test all SSBs in the system, the null
modem cable must be connected to TTY 2 and TTY 18 to begin
testing.
The next pair tested is TTY 3 and TTY 19.
TTY
ports are paired in this manner until all ports have been
tested ..
Any other menu selection initiates prompts for the appropriate null modem cable connectiono
For example, when "1" is
selected from the board menu, this display appears:
NOW CONNECT TTY2 WITH TTY6g
HIT "R" WHEN READY, OR HS" TO SKIP THIS TEST
OR "Q" TO END ALL TESTS
SIOMODEM does not move the console port for systems using an
HPCPO boardo
Use SCCTST to test on-board HPCPU console and
diagnostic port functionso
Enter "s" when prompted to defer testing of any port pair., /
Enter "R" to begin the test, and SIOMODEM will continually

Zilog
10/25/84

SIOMODEM

Zilog

SIOMODEM

update
the display with the test information described in·
Subsections 1.4 through 1.6.1.
To stop the test, enter any character.

103.

General Error Messages

The error messages that follow, as well as the statements
concerning status codes and chips, apply to all the tests
within SIOMODEM.
Errors that pertain to a
particular test
are defined under the sUbsection that discusses that test.
All error messages are preceded by an audible "beep" on the
console.
The status codes displayed are the contents of
read register 0 on the appropriate SIO or DART chip.
The SIOs are located on the CPU boards other than the HPCPU,
and the DARTs are located on the SSB boards.
For additional
information on the SIO and DART registers,
refer to the
Zilog Components Data Booke
These error messages could appear during any SIOMODEM test:

SPECIAL RECEIVE CONDITION INTERRUPT
No test currently implemented should cause the above referenced interrupt to occur.
The receive SIO modem believes it
is detecting a serious error condition, such as a parity or
framing error.
Can Not Test TTYs on HPCPU board

This message is displayed when an HPCPU is installed in the
system and a zero is entered in response to SELECT TEST TO
BE PERFORMED. A zero entry is reserved for CPU boards which
contain I/O ports 0 to 7. Only the console and diagnostic
I/O ports exist on the HPCPU board, and are not tested by
SIOMODEM.
SCCTST is designed to test HPCPU on-board console
and diagnostic channels.
INVALID 'CHOICE

TRY AGAIN! I

SIOMODEM displays this message when an entry is made that
differs from the menu choicese
For example, a "6" entry in
response to SELECT TEST TO BE PERFORMED constitutes an
invalid choice.

Zilog
10/25/84

SIOMODEM

Zilog

SIOMODEM

SKIPPING TEST OF AND -- SERIAL I/O
NOT PRESENT !!

HARDWARE

This message indicates that the null modem cable is not connected to the selected ports, and typically occurs when the
"all boards" menu selection is chosen, and TTY ports 2 and
18 have not been connected.
104.

Polled Mode Test

This message is displayed at the completion of each cycle of
the polled-mode test
(after 256 characters have been successfully transmitted in each direction):

POLLED TEST ON TTYi, CHARS, <#1> ERRORS,
ON TTY#, CHARS, ERRORS
Totals are cumulative from initiation of the
current pair of SIO poits.

test

for

the

If the error count- is zero in both directions, the test is
successful.
The error count represents the number of times
that the character received differed from the character
transmittedD

~
\

The polled-mode test continues until a character is input on
the console ..
1.4.1.

Polled Mode Error Messages

This sUbsection describes the source of error messages
may be displayed during the polled mode test.

NO CHARACTER RECEIVED, POLLED MODE,

TTY#, CBAR=

No character was transmitted between the ports in a polledmode transmissiono
All possible ASCII characters from 00 to
FF are transmitted in both directions, and
the error text
reveals which character was attempting to be transmitted.
Probable Cause:
If the failed character was 00,
check the
cable used to connect the port pair under testa
This message occurs if one of the connectors is loose, a wire is
broken,
a pin has come loose, or if the cable is connected
to the wrong porte

Zilog
10/25/84

'-..~-

SIOMODEM

'Zilog

SIOMODEM
/~

TTYi RECEIVE MODEM ERROR STATUSl = , DeD AND/OR

An error occurred during transmit modem signal polled mode
testing.
RTS and DTR were reset in the receive modem, but
DCD and/or CTS failed to be reset in the transmit modem.
Check the interconnecting cable for broken wires or loose
pins.
TTYi TRANSMIT MODEM ERROR STATUSl
CTS SET

= ,

DCD AND/OR

An error has occurred during transmit modem signal polled
mode testinge RTS and DTR were reset in the receive modem,
but DCD and/or CTS failed to be reset in the transmit modem.
Check the interconnecting cable.

TTY# RECEIVE MOD8M ERROR STATUS2
TURNED BACK ON

= ,

CTS NOT

Error in polled-mode testing of modem signals. RTS and DTR
were set high in the transmit modem, but the expected
receive modem status, DCD low and CTS high, did not occur •
.~

TTY# TRANSMIT MODEM ERROR STATUS2
TURNED BACK ON

= ,

DCD

NOT

Error in polled-mode testing of modem signals.
DTR was set
in the receive modem,
but the expected transmit modem
status, DCD high and CTS low, did not occur.
1.5.

Interrupt Mode Test

This message is displayed at the beginning of each
tion of the interrupt mode test:

interac-

SPEED= <#ii#> BAUD, TEST CYCLE
The interrupt-mode test is similar to the polled-mode test,
except that SIO character received interrupts signal the
receipt of each character.
Characters from 00
for each of the
1200, 300, and 110
ted decreases with
/"-~

to FF are transmitted in each direction
standard line speeds: 19,200, 9600, 4800,
baud.
The number of characters transmitslower baud rates.

The interrupt-mode test continues until a character is input
on the console
When a character is input, the test terminates on completion of the current cycle. The LAST CYCLE
0

Zilog
10/25/84

SIOMODEM

Zilog

display appears after the test cycle number, indicating that
no new cycle will be startedo
This message is displayed at the end of
each cycle of the interrupt-mode test:

each

iteration

INTERRUPT TEST ON TTY#, CHARS, <##>ERRORS,
ON TTyt, CHARS, ERRORS
Character and error counts are cumulative for all test
cycles.
Zero error counts in both directions indicate a
successful test.
The error count is the number of times
that the transmitted character failed to match the received
character.
1.5.1

Interrupt Mode Error Messages

The following error messages may occur during interrupt mode
test execution.
INTERRUPT NOT RECEIVED, TTY#, FAILED

ON CHARACTER

Character-received interrupt failed to occur in. interruptmode testing
("status affects vectors" = false, interrupt
vector =0x20).
The TTY number of the receive port is given.
CHARACTERS MATCH WITH MIS-MATCHED BAUD RATES!!
Indicates that 256 characters were successfully transmitted
despite differing baud rates in the transmit and receive
ports.
Probable cause:
The baud rate clocks are not
correctly seto
CTS INTERRUPT NOT RECEIVED, TTyt, STATUS=
An error occurred in interrupt-mode testing of modem signals.
RTS and DTR were reset in the transmit modem, which
should have generated an interrupt in the receive modem when
neD and CTS are reset.
If both polled-mode and interrupt-mode modem tests fail, the
interconnecting cable should be carefully checkedo
If only
one modem test fails, the SIO is probably at faulto
DCD AND/OR CTS NOT CLEARED AFTER RTS/DTR CLEARED g

TTYi, STATUS=

The interrupt described in the previous error occurred in
the receive SIO modem; however, the expected status of zero
for both DCD and CTS did not occuro

Zi10g
10/25/84

SIOMODEM

Zilog

CTS INTERRUPT NOT RECEIVED, TTYI,

STATUS=

RTS was set on the transmit modem, which should have
an interrupt on the receive modem when CTS is set.

caused

TTYi CTS NOT SET AND DCD CLEARED AFTER RTS SET, STATUS =
The interrupt described in the previous error occurred7 however,
the expected status, CTS set and DCD reset, did not
occur.
DCD INTERRUPT NOT RECEIVED, TTY#,

STATUS=

DTR was set on the receive port, which should have caused an
interrupt on the transmit port when nCD was set true.
TTY. DCD NOT SET AND CTS RESET AFTER DTR SET, STATUS=
The interrupt described in the previous error occurred,
but
the expected status, DeD true and CTS false, did not occur.
1.6.

Modem Interrupt Test

This message is displayed on completion of each iteration of
the modem interrupt test (after 256 characters are successfully transmitted in each direction):
MODEM INTERRUPTS ON TTY', CHRS, <#i>ERRORS,
ON TTyt, CHRS, <#i>ERRORS
The character and error counts are cumulative from the
beginning of the test.
The error count is the number of
times the character transmitted did not match the character
received.
The test is successful when the error count is
zero in both directions.
106.1

Modem Interrupt Test Errors

This sUbsection provides explanations for error messages
that may be displayed during the Modem Interrupt Test.
NO CHAR RECEIVED, MODEM INTERRUPT TEST ON TTYig RECEIVE
STATUS= FAILED ON CHARACTER= <##>, TRANSMIT STATUS=

A character-received interrupt failed to occur on the
receive
SIO during interrupt-mode modem testing.
The
interrupt-mode character test is repeated,
except that
"status affects vectors" is true, and interrupt vectors.0x24
and 0x2C are used for character interrupts, instead of 0x20.

Zilog
10/25/84

SIOMODEM

Zilog

SIOMODEM

,'J
The status of the transmit and receive modems and the character attempting to be transmitted are given.
MODEM LINES HAVE DROPPED BETWEEN TTYi AND TTYi,
RECEIVE STATUS= , TRANSMIT STATUS=
An external/status interrupt, indicating a change in one of
the states of the modem signals, occurred during the
transmission of characterso The status of the receive and
transmit modems is giveno
It may not be possible to recover
from this error, in which case the test is restarted.
NO TRANSMIT INTERRUPTS OCCURRED, MODEM INTERRUPT TEST,
TTY#, STATUS=

No transmit buffer empty interrupts have occurred on the
transmit modem during the transmission of 256 characters.

Zi10g
10/25/84

SIOTEST

1.1"

Zilog

SIOTEST

SIOTEST is an interactive, menu-driven test of the SIOs and
CTCs not used by the console.
(SADIE uses SIO 0, Channel B,
to communicate with the consoles
The test assumes that SIO
0, Channel B, is functioning.)
SIOTEST was called S168IO in earlier versions of SADIE
(Release 3.1 and below).
SIOTEST reflects increased serial
I/O test capability, depending on board types~ and corrects
some known problems and limitations associated with the
older S16SIO.
.e .

If a CPU board other than an HPCPU is in use, seven on-board
SIO channels may be tested in addition to the SSB board I/O
ports.
Serial Communications Controllers (SCCs) provide console and
diagnostic port serial I/O for the HPCPU board, and SCCTST
tests those devices.
.
When an HPCPU board is present in the system under test, all
other serial I/O resides on Secondary Serial Boards (SSBs),
or optional Intelligent Communications Processor Boards
(ICPs).
SIOTEST tests the serial I/O devices on the SSB
boards, and ICPTSTI through ICPTST3 tests support ICP board
serial I/O channels.
Regardless of CPU board type, all SSB board serial I/O may
be tested with SIOTEST.
SIOTEST determines the type of CPU
board in use, then displays the appropriate menu.

102.

Set Up

This test requires a auxiliary terminal, which SIOTEST calls
AUX.
The auxiliary terminal must not be connected to the
selected TTY until SADIE transfers
The test menu allows the user to select the board to be
tested,
then the TTY port that corresponds to the selected
SIO channel ..
The test prompts the user to plug
the auxiliary terminal
into a
specified port on the system rear panel.
Any key
pressed on the console signals the test to proceed.
Press "X" after the menu appears, to exit the test ..

Zi10g
10/25/84

SlOT EST

1.3.

Zilog

SlOTEST

Test Sequence

After any console key is pressed,
SIOTEST displays the
entire set of ASCII printable characters continuously, until
any key on the console is pressed again.
If SIOTEST fails to respond to , ensure that the auxiliary terminal is connected to the correct port, then press
several keys in succession on the console.
When testing any channel except SIO 0, channel A, any character pressed on AUX is echoed back to AUX. Any console
keystroke terminates "echo mode" and returns to the SIOTEST
menu.
When testing SIO 0, channel A, there is no echo mode, and
the first key pressed on the console returns the board menu.
NOTE
Do not press the system START button for a
nonmaskable
interrupt
(NMI) while the test is runConsole I/O is redirected during SIOTEST
nioge
execution,
and an attempted NMI could disable the
system. The menu provides the option to exit
SIOTEST.

Zilog
10/25/84

)
"-

Zilog

APPENDIX A

APPENDIX A
SADIE TEST AND MONITOR CROSS REFERENCE

A.I.

GENERAL

Page two of this appendix lists SADIE 3.5 tests and monitors
as displayed on the Choose and Run a Single Test Menu
accessed when "T" is pressed following boot-up.
Tests are
listed numerically.
Page three of this appendix lists SADIE tests and monitors
alphabetically, as they appear in this manual, followed by a
description and the corresponding test numbere

.~.

A-I

Zilog
10/25/84

A.-I

APPENDIX A

A.2.
No.
1

2
3
4
5
6
7
8
9
10
11
12
13

14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38

Zi10g

APPENDIX A

NUMERICAL LISTING OF SADIE TESTS AND MONITORS
Name

CONTROL
MDCFMT
MDCMEDIA
MDCTEsrr
MDCMON
MDCCRC
SMDFMT
SMDMEDIA
SMDTEST
SMDMON
SMDCRC
WDCFMT
WDCMEDIA
WDCTEST
WDCMON
WOCCRC
TCUMON
TCOM
TEX
CIOTST
SCCTST
CACHETST
MEMTEsrr
MMUTST
CENT.PRT
DP.PRT
SIOTEST
SIOMODEM
ECCTEST
MTCMON*
MTCOM
ICPTS'fl
ICPTST2
ICPTST3
ICPTST4
FPp'rST
FPPMON
FPPWHET

Description
Display menu of test-list control lines
Mini-disk format program7 DESTRUCTIVE
Mini-disk media test7 DESTRUCTIVE
Mini-disk random tests7 DESTRUCTIVE
Mini-disk monitor; DESTRUCTIVE
Read-only test of Mini-disk
DATA-DESTRUCTIVE format of SMD disk
Test of SMD disk media; DESTRUCTIVE
Random SMD disk tests; DESTRUCTIVE
Interactive SMD Monitor; DESTRUCTIVE
Read-only test of SMD disk
DATA-DESTRUCTIVE format of 8" WDt disk
8" WDC disk media test; DESTRUCTIVE
8" WDC tandom test; DESTRUCTIVE
Interactive 8" WDC monitor; DESTRUCTIVE
Read-only test of 8" WOC disk
Interactive TCU tape monitor;
DESTRUCTIVE
TCU .tape command exerciser; DESTRUCTIVE
Tape media verification test
HPCPU on-board CIO test
HPCPU on-board SCC test
HPCPU CACHE test-must set jumper
Thorough memory test
Thorough test of MMUs
Tests CENTRONICS printer interface
Tests DATA PRODUCTS printer interface
Interactive SIO and CTC test
Interactive SIO test w/MOOEM controls
ECC error correction/detection test
Interactive 9-track tape monitor
9-track tape command exerciser
Host/ICP communication test
Async interrupt mode test
Async polled mode & bisync test
Test EXXON office System
The Go/NoGo FPP board diagnostic
Control store loader and FPP monitor
Whetstone benchmark and test of FPP

....

* Not operational at this time

A-2

Zilo']
10/25/84

A-2

APPENDIX A

Ao3e

APPENDIX A

ALPHABETICAL LISTING OF SADIE TESTS AND MONITORS

Name
CACHETST
CENT.PRT
CIOTST
CONTROL
DP.PRT
ECCTEST
FPPMON
FPPTST
FPPWHET
ICPTSTl
ICPTST2
ICPTST3
ICPTST4
MDCCRC
MDCFMT
MDCMEDIA
MDCMON
MOCTEST
MEMTEST
MMUTST
MTCMON*
MTCOM
SCC'rST
SIOMODEM
SIOT.EST
SMDCRC
SMOFMT
SMDMEDIA
SMOMON
SMDTEST
TCOM
TCUMON
TEX
WOCCRC
WDCFMT
WDCMEDIA
WDCMON
WDC'rEST

Zilog

Description
HPCPU CACHE test-must set jumper
Tests CENTRONICS printer interface
HPCPU on-board CIO test
Display menu of test-list control lines
Tests DATA PRODUCTS printer interface
ECC error correction /detection test
Control store loader and FPP monitor
The Go/NoGo FPP board diagnostic
Whetstone benchmark and test of FPP
Host/ICP communication test
Async interrupt mode test
Async polled mode & bysync test
Test EXXON Office System
Read-only test of Mini-disk
Mini-disk format program~ DESTRUCTIVE
Mini-disk media test~ DESTRUCTIVE
Mini-disk monitor; DESTRUCTIVE
Mini-disk random tests~ DESTRUCTIVE
Thorough memory test
Thorough test of MMUs
Interactive 9-track tape monitor
9-track tape command exerciser
HPCPU on-board SCC test
Interactive SIO test w/MODEM controls
Interactive SIO test and CTC test
Read-only test of SMD disk
DATA-DESTRUCTIVE format of SMD disk
Test of SMD disk media~ DESTRUCTIVE
Interactive SMD Monitor; DESTRUCTIVE
Random SMD disk tests; DESTRUCTIVE
TCU Tape command exerciser; DESTRUCTIVE
Interactive TCU Tape monitor; DESTRUCTIVE
Tape media verification test
Read-only test of 8" WDC disk
DATA-DESTRUCTIVE format of 8" WOC disk
8 11 WDC disk media test ~ DEs'rRUCTIVE
Interactive 8" WDC monitor; DESTRUCTIVE
8" WDC random test; DESTRUCTIVE

Test
No.
22
25
20
1
26
29
37
36
38

32
33
34
35
6
2

5
4

23
24
30
31
21
28
27
11
7
8
10
9
18
17
19
16
12
13

15
14

Not operational at this time

A-3

Zilog
10/25/84

A-3

APPENDIX A

A-4

Zilog

2110 9
10/25/84

APPENDIX A

A-4

Zilog

APPENDIX B

APPENDIX B
mWDC PACKET COMMANDS/TAPE CONTROLLER STATUS BITS
For Use With MDCMON and TCUMON Tests

B.I.

GENERAL

The tables in this appendix provide command and dispatch
word definitions which make up the mWDC command packet
buffer, as well as tape controller status bit definitions.
The information provided is intended for use when running
MDCMON and TCUMON SADIE tests.
Table B-1, which briefly describes mWDC drive command words
that make up the drive command packet buffer, is followed by
bit definitions for those words.
Table B-2 provides mWDC
command set descriptions, and Table B-3 contains tape controller status bits.

Table B-1

mWDC Drive Command Packet Buffer

COMMAND WORD
DWO

FUNCTION
Dispatch Word
SUBPACKET FOR DRIVE 0

CW0*
CWl*
CW2*
CW3*
CW4*
CW5*

B-1

Command Field and Opcode
Logical Block Number
Transfer Sector Count
Transfer Address Bits 0-15
Transfer Address Bits 16-31
status and Interrupt Vector

CW0 through CW5 describe a single subpacket for a
unito

Zilog
10/25/84

disk

B-1

APPENDIX B

Zilog

APPENDIX B

There are four units and four subpackets, each identical to
the other except for unit number.
The command word and bit
descriptions are:

DW0

DISPATCH WORD
15

MSB

7 6

x --------- x

b a

Reserved

5 4
b a
3 Un i t

Un i t

3 2

1 0

b a

Unit 1

Unit (0

LSB

Bit a

Input from host indicating that the subpacket
is ready to be read for the appropriate unit.

Bit b

Output to host indicating a command is pending
(command has been read but not yet completed).

Bit x

Reserved, must be zero.

The dispatch word (DW0) implements a handshake
controller and the host'system.

between

the

Setting any unitls'bit "a" indicates to the controller
command subpacket for the unit is ready to be read.

the

Bit "btl is set when the controller has finished reading the
The host must not issue a command when
command subpacket.
bits na" and "b" are set. The mWDC will clear bits "a"
and
"b" when the command is complete.

CW0

Command Word

(COMMAND FIELD AND OPCODE)

MSB 15
14 x x x 10
Retry
Reserved

EI SMD

7 x x x x x x 0
Command Opcode

COMMAND FIELD BITS

FUNCTION

Bit 15

After command completion, if a
correctable error occurred, this
bit will be a 1. Otherwise, it
will always be zero.

,Bits 10 through 14

LSB

Reserved

Bit 9

SMD Mode (Sector Map Disabled)

Bit 8

Enable Interrupt on command complete.

B-2

Zilog
10/25/84

B-2

~)
\

. . . ,.

Zilog

APPENDIX B

COMMAND OPCODE

Bits 0 through 7

CWI

LOGICAL BLOCK NUMBER WORD

Bits 0 through 15
Bits 0 through 31

CW2

Bits 0 through 31

B-3

I BLOCK COUNT WORD

The host may pass up to sixteen
bits that signify the number of
sectors to be transferred when
the mWDC I board is in use.
If this causes a pack overflow, an illegal
cylinder error is returned.
A 32-bit sector count transfer when
the mWDC II or III board is in usee

TRANSFER ADDRESS BITS 0 - 15 WORD

Bits 0 through 15
13"'

The mWDC I accepts a l6-bit block
number from the host.
The mWDC II or III accepts a 32-bit block
number from the hosto

TRANSFER SECTOR

Bi ts 0 through 15·

CW3

Specific controller command codes
are input to the controller
through these bits~

The host must pass a 24-bit
address to the controller for commands involving I/O. This transfer
address is the location of the
first word of a block of memory
allocated for the transfer.
The
direction of transfer is determined by the command. Read sector
moves data from the disk to host
memory. Write sector moves data
from the host to the disko These
bits are used to pass the low
order 16 bits of a 24-bit transfer
address.

Zilog
10/25/84

B-3

APPENDIX B

Zi10g

CW4

APPENDIX B

Bits 0 through 7

These bits are used to pass the
high order 8 bits of a 24-bit
transfer address (Segment number).

Bits 8 through 15

Reserved for transfer of address
Bits 24-31.

CW5

STATUS WORD

Bits 0 through 7

Interrupt vector: Input from
host indicating the desired
interrupt vector for the
current command.
(Nonsignificant if in polled mode.)

Bits 8 through 12

At command completion, the output
from the mWDC is the completion
status code.

BINARY
12 8
00000
000001
00010
00011
00100
00101
00110
00111
01000
01001
01010
01011
01100
101101
01110
01111
10000
10001
10010
10011

B-4

-----00

TRANSFER ADDRESS BITS 16 - 31 WORD

COMPLETION CODE
No error
Read abort
Wait abort condition (Fatal)
Parity error during bus transfer
Write fault condition (Fatal)
Seek not complete (Fatal)
Cylinder not found
Drive not selected (Fatal)
Head and/or sector/record not found
Invalid command
No track 0 found (Fatal)
Drive not ready (Fatal)
Bad interrupt generated within mWDC
Cylinder 0 defective or greater than
45 bad sectors on disk (Fatal)
Illegal cylinder selected or beyond
disk boundary
Burst Error Processor (BEP) error
Soft BEP error
Soft head and/or sector not found
Soft cylinder not found
Soft read abort

Zilog
10/25/84

B-4

Zilog

APPENDIX B

On command completion, the
logical unit number

Bits 13 through 15
BIT 15

LOGICAL UNIT

Unit number 0 mini-disk
unit number 1 mini-disk
unit number 2 mini-disk,
Models 21+ and 22 only
Unit number 3 mini-disk,
Models 21+ and 22 only
Not used
Not used

0
0
0

0
1
0

1
1

o
o

Bits 8 - 15

APPENDIX B

On command input, these bits are
normally set by the host to zeros.
However, the host may request that
only part of the last sector (see
CW2) be transferred by setting
bits 8-15 to the number of words
to be read from the last sector.

CONTROLLBR COMMAND SET
The command set for the mWDC is described in Table B-3
the following binary command opcodes (Bit 7- Bit 0).

!it>

B-5

OPCODE

COMMAND

00000000 LSB
00000001
00000101
00010000
00010001
00010011
00010100
00010101

Test Drive Ready
Read Drive Parameters
Read Sector Sparing Map
Read Multiple Sector
Write Multiple Sector
Reca1ibrate Drive
Format TrackSeek

Zilog
10/25/84

for

B-5

APPENDIX B

Zilog

Table B-2

APPENDIX B

mWDC Command Set Descriptions

COMMAND

DESCRIPTION

TEST DRIVE READY ! UNIT/

Test Drive Ready selects the
drive and verifies drive ready.

READ DRIVE PARAMETERS
/UNIT/ ADDRESS

The host reads the drive
parameters at the address
specified.

READ SECTOR SPARING MAP
/UNIT/ ADDRESS

The host reads the sector
sparing map at the address
specified.

READ MULTI SECTOR /UNIT/
LOGICAL BLOCK NUMBER /
BLOCK COUNT / ADDRESS

Generates an implicit seek.
Requires disk address (unit,
logical block number)
and system buffer address
(block count, address)
0

WRITE MULTI SECTOR /UNIT/
LOGICAL BLOCK NUMBER /
BLOCK COUNT / ADDRESS

Generates an implicit seek.
Requires disk address (unit,
logical block number) and
host system buffer address
(block count, address).

RECALIBRATE /UNIT/

positions drive heads to
Track 0 restoring the drive
seek logico Execution is
slower than seek command.

FORMAT TRACK / UNIT/
LOGICAL BLOCK NUMBER/
ADDRESS

Format a track designated by
target cylinder, head, and
sector numberso The host
provides the appropriate format
buffer.

SEEK / UNIT /
BLOCK NUMBER

The mWDC does an explicit seek
and read and then compares the

LOGICAL

cylinder number for the correct

cylinder.

'--

8-6

Zilog
10/25/84

B-6

Zilog

APPENDIX B

Table B-3

.f<

APPENDIX B

Tape Controller Status Register Bit Definitions

BIT

NAME

DEFINITION

Bit 0
Bit 1

NOTAP
FMDET

Bit
Bit
Bit
Bit
Bit
Bit
Bit
Bit
Bit
Bit
Bit
Bit
Bit
Bit

HWERR
INVAL
INAP
(Not Used)
BPARM
BLKTAP
PROT
LBOT
LEOT
RTRYAT
UNIT0
UNITl
TRK0
TRKI

No tape cartridge in drive
File mark detected during read or
skip blocks
Hardware error
Invalid command
Inappropriate command

B-7

2
3
4
5
6
7
8
9

10
11
12
13
14
15

Bad DMA parameters
Blank tape
Tape cartridge write protected
Tape at logical beginning of tape
Tape at logical end of tape
dne or more retries attempted
Tape drive address Bit 0
Tape drive address Bit 1
Track address Bit 0
Track address Bit 1

Zilog
10/25/84

B-7

APPENDIX B

Zi10g

APPENDIX B

,l
\.,

----

,----

8-8

Zi10g

10/25/84

B-8

Zilog

APPENDIX C

APPENDIX C
LAP SUMMARY CONTENTS

CGl.

General

This appendix lists types of information found in
maries for:

lap

sum-

MDC Tests
WDC 'rests
SMD Tests
A lap summary is a table of statistics that are cumulative
for all laps completed so far in the current test run.
The lap summary includes:

unit number

total number of errors of all types

list of each packet command issued or status
returned during test, and number of times issued
tallies of hard, soft and other error types,
occurred (during which process)

and

bit
when

The remainder of this appendix provides a more detailed
description of commands and error types found in specific
lap summaries, beginning with MDC.

C.2.

MDC Test Lap Summaries

This text documents the type of information found in lap
summaries displayed at the end of MDCCRC, MDCFMT and MDCTST.
The SADIE "REC" command provides a means of viewing error
statistics when running MDCMON.

C-l

Zi10g
10/25/84

C-1

APPENDIX C

C.2.1.

Zilog

APPENDIX C

MDC Packet Commands

Lap summaries for the various MDC tests include tallies
the number of times these packet commands were issued:
Command

Description

SEEK
READ
WRITE
FMT
HOME
RDDRV
DRVRDY
READMAP

Explicit Seek
Read Multi-sector
Write Multi-sector
Format Disk (entire volume)
Home (recalibrate) Drive
Read Drive Parameters
Drive Ready
Read Sector Defect Map

C.2.2.

MDC Soft Error Tallies

The error statistic table includes a tally of the number of
times each correctable (soft) error was returned upon completion of the following packet commands:
Command

Description

TOTAL
BEP
BNF
CNF
RDABT

Total number of correctable errors
Burst Error
Block Not Found
Cylinder Not Found
Read Abort
Undefined error code

.l
I..
......

_--

C-2

Zilog
10/25/84

C-2

...... ~.

APPENDIX C

Co2.3.

Zilog

APPENDIX C

MDC Hard Error Tallies

The error statistic table provides a tally of the number of
uncorrectable
(hard) errors returned upon completion of the
following packet commands:
Command

Description

TOTAL
BNF
NR
WF
CNF
SINT
BEP
ABORT
PAR
SNC
NSEL
NTRK0
BDMAP
IC
INVC
RDABT
UE

Total number of uncorrectable errors
Block Not Found
Drive Not Ready
Drive Write Fault
Cylinder Not Found
Bad Interrupt
Burst Error
Wai t Abort
Parity
Seek Not Complete
Drive Not Selected
No Track 0 Signal
Bad Sector Defect Map
Illegal Cylinder
Invalid Packet Command
Read Abort
Undefined error code

C.2.4.

All Other MDC Hard Errors

All other uncorrectable errors are categorized
as follows:

<-J.

C.3.

and

Error Type

Description

TOTAL
INIT
eMP
CYL0
MAPOFL

Total number of other errors
MDC Initialization or self-test errors
Compare errors
Cylinder 0 error during format
Map Overflow

SMD Test Lap Summaries

These headings list statistics found in lap summaries
follow SMDFMT, SMDCRC,
SMDMEDIA and SMDTST tests.
statistics are accessible from SMDMON via the SADIE
command.

C-3

tallied

Zilog
10/25/84

which
Error
"REC"

C-3

APPENDIX C

C.3el.

Zilog

APPENDIX C

SMD Packet Commands

SMD error statistic tables include the number of times these
packet commands were issued:
Command

Description

TOTAL
nop
wram
rram
sel
pri
reI
rst
seek
fmt
wIng
wri
frd
rIng
read
size
inv

Total packet commands issued
NOP commands
WRAM commands
RRAM commands
SELECT commands
PRISEL commands
PRIREL commands
RESET commands
SEEK commands
FMT commands
WLONG commands
WRITE commands
FRD commands
RLONG commands
READ commands
SIZE commands
invalid packet commands
NOTE

"Invalid" packet commands may include valid commands issued by SMDMON via the DOPKT command.

C.3.2.

SMD Soft Error Tally

The error statistic table tallies all soft errors reported
by the SMD controller following packet command execution,
including:
Error

Description

TOTAL

# times one or more error status
bits (SB) returned when Ending
Status (ES) indicated none occurred

rty

soft errors with retries attempted

corr

soft errors with correction attempted

soft errors with disk rezero attempted
.

C-4

Zilog
10/25/84

C-4

.--.."

Zilog

APPENDIX C

C.3.3.

APPENDIX C

SMD Hard Error Tally

Error

Description

TOTAL

* times

hard error returned in
ending status

rty

hard data errors with retries
attempted

corr

hard data errors with correction
attempted

hard data errors with disk rezero
attempted

C.3.4.

SMD Drive Error Tally

Drive errors encountered during execution. of packet commands
are tallied as:

C-5

Error

Description

TOTAL

times one or more drive errors
occurs during packet command execution

drive faults

drive seek errors

noc

drive not-on cylinder errors

nrdy

drive not ready errors

busy

dual-access busy errors

Zilog
10/25/84

C-5

APPENDIX C

C.3.5e

Zilog

APPENDIX C

SMD Controller Time Out Errors

SMD controller timeout errors which occur during packet command execution are listed this way:
Timeout Type

Description

TOTAL

total # timeout errors

idle

timeouts in controller idle loop

ius

timeouts waiting for IP/IUS to clear

dma

timeouts waiting for DMA completion

timeouts waiting for drive on cylinder

sclk

timeouts waiting for Servo clock

dclk

timeouts waiting for Data clock

mark

timeouts waiting for Sector/index
mark

isnc

timeouts waiting for ID sync

)
\.

dsnc

timeouts waiting for Data sync

.;r.

C-6

Zilog
10/25/84

C-6

APPENDIX C

Zilog

Co3.6.'

Other Packet Command Errors

Other packet command errors found on
include:

so
me
sel
ct
rze
ae
ofl
pf
snf
wpv
inv
(\,

unk

C~3.7.

statistics

table

Description

Error Type
TOTAL
init

the

number other packet command errors
initialization errors (SMD controller
reports incomplete Dispatch Table address
and/or Interrupt vector
sector overruns
memory parity errors
select errors (0 or multiple drives)
byte/sector Count errors
rezero errors (rezero did not clear a
fault)
address errors
pack overflows
power-fail detected
sector not found errors
write protect violations
SMD controller reports invalid packet
commands
SMD controller returns unknown ending
status code

Diagnostic Error Tally

This list describes errors types detected by the diagnostic:
Error Type
TOTAL
cmp
htrk

strk

resp
sto

C-7

Description
number of diagnostic detected errors
errors detected during 2 buffer compare
# tracks with multiple hard error defects
(reported by SMDFMT only)
# tracks with soft defects unable to
flag as bad due to presence of multiple
soft defects or a hard defect on same track
(reported by SMDFMT only)
SMD controller not responding
(polled-mode commands only)
SMD controller timeout -- controller
failed to interrupt within expected
time (polled or interrupt mode)

Zilog
10/25/84

C-7

APPENDIX e

Zilog

APPENDIX

C.4' •. WDC Soft Error Lap Summary

Lap Summaries associated with WDe tests include a
tally of
the number of times the disk controller returned the following status bits when a soft error occurred:
TOT
DAT

pas

FOR
NR
SVE
RWF
SPE
PL
WPT
DSE
NCL
GB
PLE
UNS
DCE
DTO
P/M
ADE
DF
NOL
CTO

ewp
VF

CRDT
ME
C.4.1.

total number of errors
eRe errors
sector not found
format error (sector header field error)
unit not ready
servo error
read or write fault
speed error
power loss
write protected
seek error
not on cylinder
guard band error
PLO error
unsafe
invalid command
timeout error
POR/MR
address error
drive fault
drive not on-line
controller oper~tion timed out
write protect error
verify failure
bad disk: excessive media defects
can't read defect table
map error
WDC Hard Error Lap Summary

Lap summaries associated with WDC tests contain tallies of
hard errors for the same status bits listed for soft errors,
with the addition of:
INVC
eMP
INIt

invalid command
compare error
WDe not responding during initialization

Refer to the Winchester Disk Controller Hardware Reference
Manual (03-3203-01) for detailed disk controller command and
status register informationu

C-8

Zilog
10/25/84

C-8

APPENDIX D

Zilog

APPENDIX D

APPENDIX D
SYSTEM POWER UP DIAGNOSTICS ERROR LISTS

B.1.

GENERAL

This appendix provides diagnostic error lists which interpret error code displays that may occur during system power
up diagnostics ..
The first list references error codes for systems using
boards other than the HPCPU.

CPU

The second list is applicable only to systems in which HPCPU
monitor firmware version 10.0 and above is installed.
Note that the type of disk drive controller board
(referenced in error numbers 1000 through 1002 and 3000 on the
first list) may differ, depending on system configuration.
Referenced boards may include the mWDC II, mWDC III, and the
WDC ..

D-l

Zilog
10/25/84

D-l

APPENDIX

Zi10g

)
'-'_.~A'

SYSTEM POWER-UP DIAGNOSTIC (SPUD) ERROR LIST
ERROR
#

SEG#

ADDR

0100
0101
0102
0103
0104

SEG#
SEG#
SEG#
SEG#

ADDR
ADDR
ADDR
ADDR

TD
TD
TD
TD

0100
0101
0102
0103

SEG#
SEG#
SEG#
SEG#

ADDR
ADDR
ADDR
ADDR

TD
TD
TD
TD

0000
0001

0200
0201
0202
0203

SEG#

ADDR

0300

MMU

SDR

0303

PORT #
MMU
PORT #
MMU
PORT #
MMU

FIELD #
SDR
FIELD #
SDR
FIELD #
TD

0304

CMD#
REG #

.TD

0301
0302

0305

MMU
ID #

SDR#

CURS *
PRINTED

DESCRIPTION

P
0

No External Memory**
Seg. Addr Fault **

RD
RD
RD
RD

Mem. Addr Fault
Data Line Fault
'As' Data Fault
'5s' Data Fault
No Good Segments Above Zero**

RD
RD
RD
RD

Segment Zero Memory Test
(Descriptions As Above)

.:!

R (sp)
U
P (sp)

ECC
ECC
ECC
ECC

MMU's Not Individually Addressable

SAR or DSCR Indexing Fault

SDR 'As' or '5s' Data Fault

MMU Control Register 'As' or
'5s' Fault

System/Normal Break Register
'As' or '5s' Fault
Stack MMU Did Not Trap On
Limit Test
Unexpected Trap
Unexpected Trap
Data MMU Did Not Trap On
Limit Test
Stack MMU Did Not Trap On
Read-Only Test
Data MMU Did Not Trap On
Read-Only Test
Translation Fault On Data MMU

VDAT

0305

0307
0308
0309
0310
0311
0312

)

A
G
N

MMU
Port #
MMU
PORT
MMU
PORT
MMU
PORT
MMU
PORT
MMU
PORT
MMU
PORT

Single-bit Correction Failure
two-bit trap failure
two-bit error not reported
Check Byte RAM error

0305
0305
0305

0306

SDR #

SDR#

VDAT

SDR#

VDAT

SDR#

VDAT

..-

Unexpected Trap

#
RD

Translation Fault On Stack MMU

#
Unexpected Trap

#
RD

Translation Fault On Code MMU

#
Unexpected Trap

#
SDR#

S (sp)

No Trap On Code MMU Limit
Test

"\
'---

D-2

Zi10g
10/25/84

D-2

APPENDIX D

Zilog

APPENDIX D
~,

SPUD Error List (continued)
ERROR
#
1000
1001
1002
2000
2001
2002
2003
2004

··fJ
2005

(\.

3000
3001
3002
3003
3004
3005
3006
3007
3008
3009
3010
3011
3012
3013
3014
3015
3016
3017
3018
4000
4001
4002
4003

DS2

DS3

DS4

TD
TD
STATO
REG
STATO
REG

RD
RD
MIC
REG
MIC
REG

DSI

REG #
REG #
IV
REG
IV
REG

CHRS *
PRINTED

WDC Not Responding
RAM Error (PI holds location)
PROM Checksum Error
Time Out Condition
Read ABORT Error
Wait ABORT Error
Parity Error
Not Used But Reserved
Seek Not Complete Error
Cylinder Not Found
Drive Not Selected
Head/Secter Not Found
Invalid Command
No Track 0 Found
Drive Not Ready
Bad Interrupt
Bad MAP
Illegal Cylinder Selected
BEP Error

ADDR

SMC Not Responding
SMC Initialization Error
SMC RAM Error
SMC Self Test Timed Out Host
Waiting (PI holds SMC status
register)
Drive 0 Not Selected
Drive 0 Not Ready
Drive 0 Not On Cylinder
Drive 0 Read Only
Drive 0 Drive Fault
Drive 0 Seek Error
Drive 0 Not Formatted (Can't Size
Disk)

STATUS

4004
4005
4007
4008
4009

4010
COMPLETE

D-3

No WDC Board In System
WDC Self Test Error
WDC Drive 0 Error
No TCC Board In System
Busy Bit Always Set***
'5s' Data Fault
'As' Data Fault
TCC Self-Test Error***
TCC Hardware Error***

4006
J>.

DESCRIPTION

Last Characters of SPUD Message

Zi10g
10/25/84

D-3

APPENDIX D

Zilog

APPENDIX D

SPUD Error-List (continued)
LEGEND

* -** -*** --

Characters of SPUD message printed before entering test
Fatal error preventing further memory-related tests from being run
The TCU test may take up to two minutes if the drive is busy or if the 'busy' status bit is stuck. The
last two TCU error messages dump out the contents of the status registers for troubleshooting.

Pn -- Test parameters of error printed (in hexadecimal):
segment number
SEO#
address offset
ADDR
TD
test data
RD
returned data
full work port number of MMU under test
MMUPORT#
MMU port number with command 'ored' in
MMUCMD#
indicates a particular SDR in the range 0-255
SDRFIELD#
ID of MMU(s) returned from a segment trap
MMUID#
1 = code MMU
2 = data MMU
4 = stack MMU
logical segment number or set of SDR's (0-63)
SDR#
violation data from a single MMU trapping.
VDAT
(HB)- bus cycle status register data
(LB)- violation type register data
DSI
WDC detailed status - always 0
DS2
- always 0
- operation error status
DS3
- self-test error status
DS4
register port number of unit under test
REO #
no parameter printed
STATUS
SMC status port contents
When the diagnostics are complete, the maximum available segment number will be displayed as follows (xx in
hexadecimal) :
MODEL 21 PLUS
(STD.CONFIG.)
POWER UP DIAGNOSTICS
POWER UP DIAGNOSTICS
ACTIVE PERIPHERALS:
ACTIVE PERIPHERALS:
MDC
TCC
WOC
ECC (optional)
TCC
ECC (optional)
ICPn (optional)
SSBO, SSBI (optional)
SSBn (optional),
where n = board I.D. no.
MTC (optional)
ICPO-7 (optional)
COMPLETE
COMPLETE
SEGMENTED JUMPERS
SEGMENTED JUMPERS
MAXSEG = < xx >
MAXSEG = < xx >
MODEL" 11 Plus

D-4

Zilog
10/25/84

MODEL 31 PLUS
(STD.CONFIG.)
POWER UP DIAGNOSTICS
ACTIVE PERIPHERALS:
SMC
TCC
ECC
SSBO, SSB 1 (optional)
MTC (optional)
ICPO-7 (optional)
COMPLETE
SEGMENTED JUMPERS
MAXSEG = < xx >

D-4

Zilog

APPENDIX D

SYSTEM POWER UP DIAGNOSTICS (SPUD) ERROR LIST

(For HPCPU Monitor Firmware, Version 1000 and Above)

------------------------------------------------------------------------DESCRIPTION
P4
CHRS
P3
P2
PI
ERROR
PRINTED

------------------------------------------------------------------------PROM checksum error*
Scratchpad RAM error*
Console port sec error*

0010
0020
0030
0000
0001

No external memory**
Segment address fau1t**

ADDR

0040+
0041+

REG#

CIO register error
CIO counter/timer error

0050+
0051+

REG#
REG#

RD
RD

frD

Tag bank #0 register error
Tag bank #1 register error

0100
0101
0102
0103
0104

SEG#
SEG#
SEG#
SEG#

ADDR
ADDR
ADDR
ADDR

TD
TO
TD
TD

RD
RD
RD
RD

Memory Address Fault**
Data Line Fau1t**
'As' Data Fau1t**
'5s' Data Fau1t**
No Good Segments Above zero***

0100
0100
0102
0103

SEG#
SEG#
SEG#
SEG#

ADDR
ADDR
ADDR
ADDR

TD
TO
TO
TO

RD
RD
RD
RD

Segment Zero Memory Test
(Description As Above)

0200

R(sp)

Ece Single-bit Correction
Fai1ure**

0201

0202
0300+
0301+
0302+
0303+
0304+
0305+
("\

r·1

SEG#

Bce 2-bit Trap Fai1ure**
BCe 2-bit error not reported**
MMUs Not Individually
Addressable
SAR or DSeR Indexing Fault

SDR 'As' or '5s' Data Fault

MMU
PORT#
MMU
PORT#
MMU
PORT#
MMU
CMD#
REG#

SDR
FIELD#
SDR
FIELD#
SOR
FIELD#
TO

MMU
ID#

SDR#

VDAT

0306+

w
E

0-5

Zi10g
10/25/84

MMU Control Register 'As' or
'5s' Fault
Normal Break Register 'As',
'5s', 'Fs' or 'Os' Fault
Stack MMU Oid Not Trap On
Limi t Test
UnexpectEH~ Trap

D-5

APPENDIX D

Zilog

SPUD Error List for 10.0 Proms (continued)

ERROR
#

CHRS
PRINTED

0307+
0308+

0309+

p(sp)

0310+

0311+

R(sp)

0400

MMU
SDR#
PORT#
MMU
SDR#
PORTi
MMU
SDR#
PORT#
MMU
SDR#
PORTi
MMU
SDR#
POR'r#
MMU
SDR#
PORTi
MMU
. SDR#
PORT#
REG#
TD

0401
0402

REG#
SEG#

TD
AD DR

RD
TD

0403

REG#

10404

SEG#

ADDR

0405

SEG#

ADOR

0410

REG:ft:

0411
0412

REG:ft:
SEG:ft:

TO
ADDR

10413

REG#

0414

SEG#

ADDR

10415

SEG#

ADDR

0312
0313+
0314
0315+
0316

0317+

'RD

V-DAT
TD

Unexpected Trap
Data MMU Did Not Trap On
Limit Test
Stack MMU Did Not Trap On
Read-Only Test
Data MMU Did Not Trap On
Read-Only Test
Translation Fault On Data MMU
Unexpected Trap****

VDAT
TD

DESCRIPTION

Translation Fault On Stack MMU
Unexpected Trap****

VDAT

Translation Fault On Code MMU

)

Unexpected Trap****

RD
RD

No Trap On Code MMU Limit Test

Tag did not update correctly,
bank #0
Unexpected tag value (bank #1)
Cache memory read-in data fault,
bank #0
Tag did not remain updated
after write, bank #10
"t.
Cache memory write-to data
fault, bank #:0
Cache write through fault
for bank *0
Tag did not update correctly,
bank #1
Unexpected tag value, bank #0
Cache memory read-in data
fault, bank #1
Tag did not remain updated
after write, bank *1
Cache memory write-to fault,
bank #1
Cache write through fault for . ~
bank #1
)

RD
RD

C
S

,--.

D-6

Zilog
10/25/84

D-6

APPENDIX D

Zi10g

APPENDIX D

SPUD Error List For 10.0 Proms (continued)

------------------------------------------------------------------------p2
P4
CHRS
DESCRIPTION
P3
ERROR
PI
PRINTED

~~,

~I··
it>

1000
1001
10((:12
2000
2001
200"2
2003

2004

2005

n
.,

3000
3001
3002
3003
3004
3005
3006
3007

DSI

DS2

DS3

REG#
REG#
IV
REG
IV
REG

TD
TD
STATO
REG
STATO
REG

RD
RD
MIC
REG
MIC
REG

DS4

TCC Hardware Error*****
MDC Not Responding
RAM Error
PROM Checksum Error
Time Out Condition
Read ABORT Error
~"la i t ABORT Error
Parity Error
Write Fault (Should Never
Occur)
Seek Not Complete
Cylinder Not Found
Drive Not Selected
Head/Sector Not Found
Invalid Command
No Track #0 Found
Drive Not Ready
Bad Interrupt
Bad Map
Illegal Cylinder Selected
BEP Error

ADDR

3008
3009
3010
3011
3012
3013
3014
3015
3016
30~7

b.
f;;

3018

';'.

4000
4001
4002
4003

r-'\,

(

SMC Not Responding
SMC Initializing Error
SMC RAM Error
SMC Timed Out Host Waiting
For Interrupt
Drive #0 Not Selected
Drive #0 Not Ready
Drive #0 Not On Cylinder
Drive #0 Read Only
Drive #0 Drive Fault
Drive #0 Seek Error
Drive #0 Not Formatted (Can't
Size Disk)

STATUS -

4004
4005
4006
4007
4008
4009
4010

D-7

WDC Not Responding
WDC Self-Test Error
WDC Drive 0 Error
TCC Not Responding
Busy Bit Always Set*****
'5s' Data Fault
'As' Data Fault
TCC Self-Test Error*****

Zi10g
10/25/84

D-7

'''..

APPENDIX D

Zilog

APPENDIX 0

SPUD Error List For 1000 Proms (Continued)
*
**'
***
**** ***** -

, ... ..J

Loop on test applicable.
Test executed only at power-on or reset.
Power-on fatal error.
Fatal error preventing f~rther memory-related test execution.
Error number only. Loop on test number inapplicable.
The TCU test may take up to two minutes if the drive is busy or
if the 'busy' status bit is stuck. The last, two TCU
error messages dump out the contents of th~ status registers for
troubleshooting.

- Test parameters of error
SEG#
ADDR
TD
RD
MMU PORT#
MMU CMD#
SDR FIELD#
MMU ID#

snR#
VDAT
DSI
DS2
DS3
DS4
REG#
STATUS

pri~ted

(in hexadecimal):

- segment number
address offset
- test data
- returned data
- full work port number of MMU under test
- MMU port number with command 'ORed' in
indicates a particular snR in the range 0-255
- ID of MMU(s) returned from a segment trap
1 '= code MMU
2 = data MMU
3 = stack MMU
- logical segment number or set of SDR's (0-63)
violation data.from a single MMU trapping
hig~ byte - bus cycle status register data
low byte - violation type register data
- WDC detailed status - disk ready register
II
II
II
disk status register
"
"
II
operation error status
II
..
..
self-test error status
- register port number of unit under test
- no parameter printed
- SMC status contents

When. the diagnostics are complete, the maximum available
segment number will be displayed as follows. Peripherals listed are
dependent on the system model number and options. The value
is in hexadecimal.
MONITOR POWER UP DIAGNOSTICS
ACTIVE PERIPHERALS:
MDC (models,12, 22)
SMC
(model 32)
TCC
SSBn (optional), where n = board 1.0. no.
ICPn (optional), where n = board I.D. no.
MTC (optional, model 32)
FPP
(optional, models '22,32)
COMPLETE
MAXSEG=
D-8

Zilog
10/25/84

D-8

.~~. ,

Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.4 Linearized : No XMP Toolkit : Adobe XMP Core 4.2.1-c041 52.342996, 2008/05/07-21:37:19 Format : application/pdf Create Date : 2018:04:19 09:56:54-07:00 Creator Tool : Hewlett-Packard MFP Modify Date : 2018:04:19 09:56:54-07:00 Metadata Date : 2018:04:19 09:56:54-07:00 Producer : Adobe Acrobat 9.0 Paper Capture Plug-in Document ID : uuid:f8b12c77-93bf-5a41-aef5-41b1b2b96077 Instance ID : uuid:d2c554a9-4090-744a-b11d-720fdfbfa565 Page Count : 138 Creator : Hewlett-Packard MFP
EXIF Metadata provided by EXIF.tools

Note_To_User_For_Sadie_Version_3.5__Number_03 0244 05 Note To User For Sadie Version 3.5 Number 03

Navigation menu

Versions of this User Manual:

Views

Navigation