Supplemental Pod

Information for

9100A/ 9105A Users

July1987 Rev 2 3/88

—

@1988 John Fiuke Mfg. C0., Inc. All rights reserved. Litho in USA. —

MANUAL UPDATE PACKAGE

ISSUE NO: 1

DATE: 2/89

This Manual Update Package contains information necessary to ensure the

accuracy of the following manual:

MANUAL

Title: Supplemental Pod Information for 91OOA/9105A Users

Print Date: July 1987

Rev.- Date: 2, 3/88

PAGE EFFECTIVITY

Page No. Print Date

1 2/89

POD

Supplemental Pod Information

1802 POD ------------------ __

CONNECTION TO 9100 SERIES MAINFRAMES

Connect the pod cable with the 25-pin connector to the pod port on the

side of the mainframe. The cable with the 9-pin connector is not used

with 9100 Series products. Secure the connector using the slide locking

collar.

All 9100 Series probe stimulus/response functions can be used for the

UUTs with Vcc of 5V (the probe thresholds must be set to CMOS) .

NOTE

2/89

The 9100 Series probe may be used as a measurement device for UUTs with

Vcc greater than 5V if UUT logic low is below 0.8V. Again, the probe

thresholds must be set to CMOS. If the probe is used in this manner, be

aware that the thresholds of the probe do not match thresholds of

typical CMOS devices when Vcc is above 5V. The output functions of the

probe cannot be used for UUTs with Vcc greater than 5V.

1802-0

Supplemental Pod Information

TABLE OF CONTENTS

TITLE PAGE

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction—1

Operator ' 5 Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction-2

Pod Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction-L1

Programmer's Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. Introduction-5

1802 Pod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1802-1

6502 Pod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6502-1

6800 Pod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6800-1

6802 Pod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6802—1

6809 Pod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6809-1

68000 Pod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68000-1

8080 Pod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8080-1

8085 Pod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8085—1

80148 Pod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80118-1

8051 Pod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8051-1

8086 Pod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8086-1

8088 Pod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8088-1

80186 Pod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80186-1

80188 Pod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80188-1

9900 Pod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9900-1

Z80 Pod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280-1

Z8000 Pod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Z8000-1

Supplemental Pod Information

INTRODUCTION

Pods Supported

This manual provides information to support use of the Interface Pods

listed below with 9100 series testers. The manual is a supplement to the

Instruction Manual for each Pod.

1802 6502 6800 6802 6809 68000

8080 8085 80118 8051 8086 8088

80186 80188 9900 Z80 Z8000

Multiple Databases per Pod

Many Fluke microprocessor interface pods support more than one

microprocessor type. These pods fall into two types. The first type

enters a mode depending upon the type of microprocessor installed in the

pod and/or the configuration of switches on the pod. The second type of

pod is general enough in its operation that it can emulate several

processor types without knowing the specific type on the UUT.

The first type of pod reports to the mainframe which mode it is in and

the mainframe automatically loads a database appropriate to that mode.

The mainframe also automatically loads a database for the second type of

pod, but this may not be the database that enables the pod to most

closely emulate the processor type. A keystroke method is available to

choose a specific database. To do this, press the SETUP MENU key on the

front panel of the 9100 series tester. Then select the POD NAME softkey.

You can enter an alphanumeric value for the name of the database to be

loaded and used with the pod that is installed. Further information

about valid database names for each pod may be found in the sections for

pods that support this feature.

Introduction—1

Pod Information

OPERATOR'S INFORMATION

Reading the Database Version Number

Pod databases are disk files in the 9100 series Mainframe that contain

information to determine the pod's interface to the rest of the system.

To read the version number of the database from the front panel, press

the SETUP, ->, and SOFT KEYS keys, the POD__NAME softkey, then the ENTER

key. After a short disk operation, the front panel will display PODF‘ILE

: xxxxxx.# where xxxxxx is the pod database name and # is the revision

level of that database.

Understanding 9100 Pod Self Test Return Codes

I

I

l

I

l

l

I

I

I

I

I

I

l

I

I

I

I

9100 series mainframe pod test algorithms are improved over those of

9000 series mainframes. Hence, the error codes returned by the 9100

series mainframes have different meanings. Table 1 details the steps

that the 9100 takes in testing pods and their corresponding error codes.

NOTES FOR TABLE 1 (on next page):

UUT power sensing circuit fault.

Control line(s) cannot be driven.

Address line(s) cannot be driven.

Wrong data read.

Data line(s) cannot be driven.

Forcing or interrupt line buffer(s) or associated logic faulty.

H H II II II II

FF for 8-bit interface pods.

FFFE for 16-bit interface pods.

maxdata :

the number of enableable lines in the pod.

the number of address spaces in the pod.

Introduction-2

Supplemental Pod Information

Table 1. 9100 Pod Selftest Error Codes

I

ERROR I I POSSIBLE

CODE l IEAULTS WHEN

(DECIMAL)I ATTEMPTED ACTION IACTION FAILS

I I

I I

0000 IReadspecial addr OFFOOFFO. Reset and initialize pod. I A, B C, D

0001 IWritespecial addr OFFOOFFO, data EOOFOEFO AND maxdataI A, B C, E

7

V

0002 ITest control lines. I B

0003 IDisable all enableable lines. I F

000A ISync on ADDR. I A, F

0005 IReadspecial addr 0000FO0F. I A, B, C, D

0006 IWritespecial addr 00000001, data FFFFFEEE AND maxdataI A, B, C, E

0007 IWritespecial addr 00000002, data FFFFFFFD AND maxdatal A, B, C, E

0008 IWritespecial addr 0000000“, data FFFFFFFB AND maxdatal A, B, C, E

0009 IWritespecial addr 00000008, data FFFFFFF7 AND maxdatal A, B, C, E

0010 IWPitespecial addr 00000010, data FEFFFFEF AND maxdatal A, B, C, E

0011 IWritespecial addr 00000020, data FFFFFFDF AND maxdatal A, B, C, E

0012 IWritespecial addr 000000A0, data FFFFFFBF AND maxdatal A, B, C, E

0013 IWritespecial addr 00000080, data FFFFFF7F AND maxdatal A, B, C, E

I I I I I

I I I I I

V I V I V

003A IWritespecial addr 10000000, data EFFFFFFF AND maxdataI A, B, C, E

0035 IWritespecial addr 20000000, data DFFFFFFF AND maxdatal A, B, C, E

0036 IWritespecial addr A0000000, data BFFFFFFF AND maxdatal A, B, C, E

A, B, C, E

0038 IEnable first pod enableable line. I F

0039 IEnable second pod enableable line. F

I I I I

I I I I

V I V V

0037+N IEnable last pod enableable line (N defined in NOTES). F

0038+N IWrite maxdata to low address of first address space. A, B, C, E

I(N defined in NOTES on previous page)

0038+N IWrite maxdata to high address of first address space. A, B, C, E

+1 |(N defined in NOTES on previous page)

I I I I

I I I I

V I V V

B, C, E

I(N and S defined in NOTES on previous page)

I

2001 IPod is not in selftest socket.

2002 IUnexpected powerfail.

2003 INo powerfail when expected.

200A IPod not reporting ABORT when ABORT line toggled.

2005 IPod reporting ABORT unexpectedly.

2006 IPod drops dead unexpectedly.

2007 IPod gives error setting enableable lines.

2008 IPod gives error setting fault mask.

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

I 0037 IWritespecial addr 80000000, data 7FFFFFFF AND maxdatal

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

I

I

I

I

I

I

I

I

I

I

0038+N+25IWrite maxdata to high address of last address space. I A,

I

I

I

I

I

I

I

I

I

I

I

Introduction-3

1 ' timer-ta) Pod Information

POD LALiBiiA'i‘iGii

Calibration is the process by which the internal delay lines in the I/O

module and Prob; are adjusted to correctly line up, in time, the clock

and data signals. (Data, in this context, refers to the signal to be

sampled, be it address, data, etc. ) To calibrate an I/O Module or Probe

to a pod, for a particular pod sync mode, the user is prompted to probe

a signal on the UUT. A particular edge on that signal is found by

adjusting the delay lines in the I/O module or Probe relative to the

internal PODSYNC signal . Once the edge is found, an offset is applied to

that edge to determine just where in time the I/O module or Probe will

latch data.

This manual lists the calibration data for each pod and sync mode.

Following is an example for the imaginary xyz pod showing how the data

is listed in the manual, and how this data would apply to real

waveforms.

EXAMPLE:

In the imaginary xyz pod, Address sync is to be calibrated to the

rising edge of the NALE line. For this example, valid address is

best captured when sampled 24ns before the rising edge of ~ALE. The

data would appear in the manual like this:

| | | l l

I SYNC MODE | UUT SIGNAL I EDGE OF SIGNAL I OFFSET FROM EDGE I

I | | | l

I I I | I

I ADDR I “ALE I RISING I -2U,ns I

l I | I I

The waveforms would look like this:

PODSYNC

m

A

24 S t |

n »< ca»!

DATA LATCHED HERE ———SPECIF|ED EDGE

NOTE: In this manual, any active-low signal name starts with ' ~ ' .

Introduction-I4

Supplemental Pod Information

If calibration is not performed, a default setting is used for teal,

(the location of the ~ALE signal relative to ~PODSYNC). The -2L1ns offset

is applied to this setting. When calibration is performed, tcal is

actually measured, and the default is replaced with the measured value.

If the TL/1 function "getoffset" were executed after calibration, an

offset of -211ns should be returned, (or a number near -211, reflecting

the granularity of the hardware delay lines) . If other offsets are

desired, the TL/1 function "setoffset" can be used. See the description

of setoffset and getoffset in the TL/1 documentation for exact syntax

and details.

PROGRAMMER' S INFORMATION

Fault Masks

Faults raised during testing may be processed by fault handlers written

in TL/1, or displayed on the front panel of the 9100 series mainframe.

System fault names and arguments associated with those faults are listed

in Appendix G of the TL/1 Reference Manual. Many of the faults listed

there have an argument named mask, mask_tied, mask__low, or mask__high.

The format of these masks is a character string of exactly 611 ones ( 1 )

and zeros (0). "X" can be used for "don’t care" bits. The rightmost

position in the character string represents the least significant bit

(LSB) position of the data item with the fault. The leftmost position of

the string represents bit 63 of the data item with the fault.

The format of TL/1 fault masks follows directly from the model of a

microprocessor used by the 9100 system. Processor signal lines are

divided into address, data, status, and control groups. The format of

each mask type is as follows:

Address, Data: Bit positions map starting from MSB to LSB of mask.

Bits beyond the processor bus width are unused.

Status, Control: Bit positions map directly from the pod underside

decal or from the Status and Control Line Bit

Assignment table in the pod manual . Other bits are

unused.

Exceptions to this general fault mask structure are covered in the

sections for the 80118, 8051, 80186, and 80188 pods.

Because the mainframe generates different fault masks (Data, Address,

(Jontrol, or Status) depending on the type of fault, the meaning

associated with a particular position changes from type to type. For

instance, in the 68000 pod, bit 1 can mean either ~BR fault (for status

faults), ~VMA fault (for control faults), data bit 1 fault (for data

faults) , or address bit 1 fault (for address faults) , depending on what

type of fault occurred.

Table 2 lists the TL/1 fault masks for the 08000 pod.

Introduction—5

\mental Pod Information

Table 2. Bit Positions for 68000 Pod Fault Masks

L

O dT d d d

RK T GE e e 6

TS LA SS SSW S S S

NA AMGUEO12DD~ S U .U U

OM HVBDRCCCLU/An n n n

C -~ U~ FFUL-R~ EU U U

|||||||||1 i l l i i llllllllllllllllllllllllllllll d

6

Mi t.

O Pd

#0 86

S .L C St

UK Ti 8 SP.

TS K T Kfln VIZ-G d d 88

AA T CRE CF 9 e e S

TM .|._ ARSAA 012F885 S S AS

5 ARGEEDLTRLLLtttU .U U Dia

HBBBRVDWPDLPHOOU n n V

---~DLwiII.lnnU U U ~An

P

|||||| | 1 i I l I I I I I l I Illlllliiillllllllllllll TV

ON

d d d n

AK 01123use e e .0

TS 0123Hw56789 1 1 1 1 4|4|S S S Kn

AA DDDDDDDDDDDDDDDDU U U ca

DM n n n A

U U U TK

DC

|.||| I I I I I I! I I I I I IIIIIIIIIIIIIIIIII ~ A

T

S FD

S d e~

EK O123Hw567890123 e h

RS 0123",».56789 1 1 1 1 1 1 1 1 112222 S th

DA AAAAAAAAAAAAAAAAA,AAAAAAA U lt

DM N GO

A U NB

O 0-

Ti S

TT 0123Hw567890123 .U. 3 E

II O123u5r0789 1 1 1 1 1 1 1 1 112222 2 6 T

B S O

O N

Di

When testing within a fault handler, often only a particular fault is of

interest. To do this, the fault mask can be compared against a string of

As an example, suppose that only bit 3 is of

interest. The comparison might be done something like this:

ones, zeros, and X5.

XXXiXXX"

: "XXXXX . . .

testmask

if (mask

testmask) then . . .

The Xs

where the one is in the fourth position from the right (bit 3) .

Other

cause any other fault to be temporarily ignored in the comparison.

individual faults can be tested by changing the testmask string.

Introduction-6

Supplemental. Pod Information

Examples of Fault Masks

The following examples show how fault masks are used to handle specific

types of faults.

EXAMPLE : Forcing Line Fault Handlers

A pod_forcing__active fault raised during the read operation in program

EXAMPLE1 below would cause the handler for pod_forcing_active to

activate. The argument mask passed to the fault handler contains the

string "OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO100" . This

string means that the fault raised is due to a problem with bit 2 of the

status word for this pod (since the status word reports forcing line

faults) . EXAMPLEl tests this particular bit position, and if the fault

is present, the fault handler disables further reporting of the

pod_forcing_active fault by using the podsetup statement to turn off

forcing line fault reports. (See the heading "Pod-Specific Setup

Information" further on in this section for more information on using

the podsetup function with pod-specific setup information.)

program EXAMPLEl

handle pod_forcing__active ( mask )

declare string mask

! Turn off reporting of forcing line faults if one is reported.

if (mid str mask, from 62, length 1) = "1" then

podsetup 'report forcing' "off"

end if

end pod_f0rcing_active

read addr 0

end EXAMPLE1

Introduction-7

:iupplementai Pod Information

EXAMPLE : Enableable Line Fault Handling

Each section in this manual contains information about the bit positions

of the pod ' s enableable lines in the enableable line mask. Handling

enableable line faults is exactly like handling other faults that use

fault masks to report the bit position of the faulty line. For example,

in the 6800 pod, there are three enableable lines; TSC in bit position

3, DBE in bit position 14, and ~HALT in bit position 5 of the enableable

line mask. The mask for a pod__timeout_enabled_line fault for this pod

would be of the format:

"0OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO0OOOOOOOOOOOOOOOOOOOOOOOXYZOOO"

where the X would contain a 1 if TSC caused a pod timeout and 0

otherwise. Y would contain a 1 if DBE caused a pod timeout, etc. A fault

handler could test for which enableable line caused the timeout (as

was done in EXAMPLE1).

Raising Built-in Faults from TL/1 —

TL/1 programs may raise system built-in faults. Information about system

faults can be found in appendices G and H of the TL/l Reference Manual.

Raising built-in faults from a TL/1 program often requires that the fault

mask format be passed as an argument to the fault statement. Care must be

taken to ensure the mask is exactly 611 characters long. Program

EXAMPLEZ shows how to raise a bus__data_low_tied fault on data line D11 .

Assuming no handlers for this fault exist in the calling chain for

EXAMPLEZ, the fault would report on the 9100 series front panel just as

if the front panel BUSTEST found D14 tied low. Other built-in faults may

be raised in the same manner.

program EXAMPLE2

declare string fift6_05

fift6_0s = "00000000000000000000000000000000000000000000000000000000" _

! The program somehow decides that 014 is tied low. A fault is

raised to indicate that fault.

!

!

! Raise the fault:

fault bus_data_low_tied mask fift6_0s + "00010000"

! If no handlers for this fault are in the calling chain for

! EXAMPLEZ, the 9100 series front panel will display:

! "data line DU pin xx stuck low" —

! The pin number xx in the fault message is pod—dependent.

end EXAMPLE2

Introduction—8

Supplemental Pod Information

Pod-Specific Setup Information

Some pods have setup information that is only used for that pod. The

TL/I manual describes the podsetup command and gives examples of the

podsetup command that can be used with any pod.

There are differences between the way the podsetup command works with

the general setups and pod-specific setups. The following examples using

the podsetup command are for the Z8000 pod. See the Z8000 section of

this manual for a list of the setups that are available for that pod.

NOTE

TL/I hexadecimal data requires a "$“ prefix character.

program SETUP

l

l

l

I

I

l

I

I

I

I

|

l

l

I

I

I

I

I

l

l

I

I

I

I

I

I

I

I

l

I

I

I

I

I

l

l

I

I

l

I

I

I

I

I

I

I

l

I

l

I

I

I

I

l

l

l

I

I

I

I

I

I

I

l

l

I

I

I

I

I

This program is a example of how to use the podsetup function

with pod-specific setup arguments (example pod-specific setup

information is from the 28000 pod database) .

IMPORTANT NOTES:

All character strings are case insensitive.

Standard (not pod-specific) setups use syntax with single

quoted arguments and double quoted values, eg. :

podsetup 'report intr' "off"

Pod specific setups either use a single single-quoted argument

or a single-quoted argument followed by a non-quoted value:

podsetup ' intr_ack on'

podsetup 'seg__reg ds' $F800

I Note, even though enableable status

I lines ~BUSRQ, NWAIT are

' pod-specific, "enable" is not, so

I these use the "built-in" syntax .

podsetup 'enable ~busrq' "off"

podsetup ‘enable ~wait' "off"

I These examples are all Z8000

I pod-specific.

podsetup ' trnsp_rd high_ad’ $IOOF

podsetup ‘ ~mo_sig state active'

podsetup 'refresh rate' $15

podsetup 'refresh status active'

I Note upper case works too.

podsetup ‘TRNSP_RD HIGH_AD' $100F

podsetup ' ~MO_SIG STATE ACTIVE‘

podsetup 'REFRESH RATE‘ $15

podsetup 'REERESH STATUS ACTIVE’

end SETUP

Introduction—9

NOTE

Supplemental Pod Information

------------------ -- I802 POD ---_-_-_------------

Read the Introduction section for important information needed to

operate and program this pod with the 9100 series mainframes.

POD ADDRESS SPACE OPTIONS AVAILABLE

The following pod address space options are available.

SPACE

MEMORY

I/O

‘ POD—SPECIFIC SETUP INFORMATION

I I I I I

| POD SETUP | RANGE/KEY | DEFAULT I POD MANUAL REFERENCE I

I I I I I

I I I I I

I DMA_TRAP key I ON/OFF I ON I See Section LI-2I and Tbl 14-21

I QLINE key I ON/OFF I OFF I See Table 14-2 I

I I I I I

AVAILABLE TL/1 SUPPORT PROGRAMS

NOTE

TL/I hexadecimal data requires a "$" prefix character.

CLR_MBIO This program clears Multi—Bank I/O mode operation. For further

DMA_IND

information, see Section lI-I9 and Table lI-2 in the 1802 pod manual .

Arguments : None.

Faults : None.

Returns : Nothing.

This program returns the data from the most recent DMA IN operation,

resets the DMA IN flag, and re-enables DMA operations. For more

information, see Section lI-2I and Table 14—2 in the 1802 pod manual.

Arguments : None.

Faults : None.

Returns : The data from the most recent DMA IN operation that was

trapped by the pod.

1802-1

my" 'emental Pod Tr‘f‘nrmation

DMA_OUTD This program returns the data from the most recent DMA OUT operation ,

resets the DMA OUT flag, and re-enables DMA operations. For more

information, see Section A-21 and Table A-2 in the 1802 pod manual .

Arguments : None.

Faults : None.

Returns : The data from the most recent DMA OUT operation that was

trapped by the pod.

QWK_IO__R This program returns the data present at the passed 1/0 port

number and places the pod in Quick Looping Read mode at that I/O

port. For further information , see Section Ll-15 through 14-20 and

Table 14-2 of the 1802 pod manual.

Arguments : PORT - The port number at which the Quick Looping

Read is to be performed. PORT may take values

from 1 through 7.

Faults : test_aborted

reason "Illegal port number" .

The value of the PORT argument does not

conform to the restrictions detailed above.

Returns : The data found at the passed port during the first cycle

of the Quick Looping Read.

QWK_IO_W This program repeatedly writes the passed data to the passed l/O

port number . For further information , see Section 11—15 through

Section 11-20 and Table 11-2 in the 1802 pod manual .

Arguments : PORT - The port number at which the Quick Looping

Read is to be performed. PORT may take values

from 1 through 7.

DATA - The data that is to be written to the above

I/O port . Any number between 0 and FF is a

legal value for this argument .

Faults : test__aborted

reason "Illegal port number".

The value of the PORT argument does not

conform to the restrictions detailed above .

reason "Illegal data" .

The value of the DATA argument does not

conform to the restrictions detailed above .

Returns : Nothing.

1802-2

RD_DMAR

Supplemental Pod Information

This program places the pod in Quick Looping read mode at the

passed address. For further information about Quick Looping read

mode, see Section Ll-15 of the 1802 pod manual.

Arguments : ADDR — The address at which to perform the Quick

Looping read . Any number between 0 and FFFF

is a legal value for this argument.

Faults : test_aborted

reason "Illegal address".

The ADDR argument does not conform to the

specification detailed above.

Returns : The byte that is found at the address specified by the

argument during the first UUT access of the Quick

Looping read mode.

This program may be used to put the pod in Quick Looping write

mode using the data and address specified by the arguments. For

further information on Quick Looping write mode, see Section “~15

of the 1802 pod manual.

Arguments : ADDR - The address at which to perform the

quick—looping write. Any number between 0 and

FFFF is a legal value for this argument.

DATA - The data that is to be written to the address

specified by the ADDR argument. Any number

between 0 and FF is a legal value for this

argument.

Faults : test_aborted

reason "Illegal address".

The value of ADDR does not conform to the

restrictions detailed above.

reason "Illegal data".

The value of DATA does not conform to the

restrictions detailed above.

Returns : Nothing.

This program returns the current DMA register contents ( 16 bits) .

For further information, see Section 11-21 and Table 11-2 in the

1802 pod manual.

Arguments : None.

Faults : None.

Returns : The 16 bit-wide contents of the DMA register.

1802—3

Supplemental Pod Information

RD_TRV

SET_DMAR

SET_MBIO

This program returns the current value of the I/O transfer vector

(16 bits). For further information, see Section 11-16 through

Section 11-20 and Table 11-2 in the 1802 pod manual.

Arguments : None.

Faults : None.

Returns : The 16 bit-wide value of the I/O transfer vector.

This program sets the DMA register contents to the passed ADDR and

writes the passed DATA to that address. For further information,

see Section 11-21 and Table 11-2 in the 1802 pod manual.

Arguments : ADDR - This is the value to be loaded in the DMA ~

register and the address to which the passed

data will be written. This argument will take

any value from 0 to FFFF.

DATA - This is the data to be written to the above

address. Valid values for this argument are

any number between 0 and FF.

Faults : test_abor.ted

reason "Illegal address".

The value of ADDR does not conform to the

restrictions detailed above.

reason "Illegal data".

The value of DATA does not conform to the

restrictions detailed above.

Returns : Nothing.

This program sets up Multi-Bank I/O mode. After use of this l

program, every I/O operation will be preceded by a write of the

passed DATA to the passed PORT. For further information, see

Section 14-19 and Table 11-2 in the 1802 pod manual.

Arguments : PORT - This is the port that the bank selection data

will be written to before each I/O operation.

Any number between 1 and 7 is a legal value

for this argument.

DATA - The data to be written to the above port _

before each I/O operation. Any number between

0 and FF is a legal value for this argument.

Faults : test_aborted “

reason "Illegal port number".

The value of PORT does not conform to the

restrictions detailed above. »

1802-11 _

Supplemental Pod Information

reason "Illegal data" .

The value of DATA does not conform to the

restrictions detailed above .

Returns : Nothing.

SET_TRV This program sets the I/O transfer vector to the value of the

passed argument. For further information, see Section III—16 through

II-ZO and Table LII-2 in the I802 pod manual.

Arguments : VECTOR - The value that is to be the new I/O transfer

vector. Any number between 0 and FFFF is a

legal value for this argument.

Faults : test_aborted

reason "Illegal vector".

The value of VECTOR does not conform to the

restrictions detailed above.

Returns : Nothing.

WR_DMA__V This program writes the passed data to the address the DMA

register points to. For further information, see Section 11-21 and

Table 14-2 in the 1802 pod manual.

Arguments : DATA — The value to be written to the address the

DMA register points to. Any number between 0

and FF is a legal value for this argument.

Faults : test_aborted

reason "Illegal data" .

The value of DATA does not conform to the

restrictions placed above.

Returns : Nothing.

SYNC MODES

I I I I

I NAME I MNEMONIC I CODE I

I I I I

I I I I

I DMA Address Sync | DMA_ADDR l O I

I DMA Data Sync I DMA_DATA | I I

| Address Sync I ADDR I A |

| Data Sync I DATA I D I

I I I I

1802-5

Inpplemental Pod Information

POD SYNC CALIBRATION DATA

I I I l I

I SYNC MODE | UUT SIGNAL I EDGE OF SIGNAL I OFFSET FROM EDGE I

I I I I l

I | I I I

I ADDR I TPA I EALLING I -II5ns I

I DATA I TPB | FALLING I —LI5ns I

I DMA_ADDR I TPA I EALLING I -145ns I

I DMA_DATA I TPB I EALLING I —1I5ns I

I I I I I

ENABLEABLE LINES

The mnemonics below are used in the TL/I podsetup ’enable‘ statement.

The bit positions correspond to bit positions in the

pod_timeout_enabled_line fault mask.

NAME BIT POSITION

~WAIT

|

l

I

|

I bit A

I

TL/1 FAULT CONDITIONS

This section lists the TL/I fault conditions that can result from pod

operation.

Handlers for most fault conditions are based on one of the LI mask types:

address, data, status, or control. See the Programmer ' s Information in

the Introduction of this manual for information about the format of each

fault mask.

Fault Conditions Using the Data Mask

pod__data_incorrect

pod_data__tied

Fault Conditions Using the Address Mask

p0d__addr_tied

Fault Conditions Using the Status Mask

pod_forcing__active

pod_interrupt_active

pod__timeout__enabled_line

1802—6

Fault Conditions Using the Control Mask

pod__control__tied

Fault Conditions With No Fault Mask

pod_timeout_bad_pwr

pod_timeout__no_cll<

pod_timeout_recovered

pod_timeout_setup

pod_uut_power

1802—7

Supplemental Pod Information