- HELP
EVDTB, a FUNCTIONAL level (Level 2R) diagnostic, contains three
tests which will establish the functionality of the KCT32.
The program provides error messages which identify data and
I/O errors. The program runs with the Diagnostic Supervisor
under VAX/VMS from any terminal.
- DEVICE
EVDTB tests the KCT32 option. The KCT32 is a DCT11 based high
performance communications front end processor for the UNIBUS.
KCT32 provides two serial communication lines, DMA capability,
a PDP-11 instruction set and 56K bytes of user programmable RAM
memory (minus the memory requirements for the KCT32 executive
firmware).
The KCT32 communications executive manages the KCT32 CSR inter-
face and the KCT32 packet queue interface for the diagnostic
firmware. The executive implements a set of generic KCT32
commands. The executive also defines generic commands which are
passed to the diagnostic firmware residing in the KCT32. The exe-
cutive is located in the 56K bytes of user memory, and is linked
with the diagnostic firmware before being loaded into the KCT32.
- KCT32
Device: High Performance communications front end processor
Link: DWn
Recommended Generic: UKan
Additional Information:
UNIBUS CSR [octal 760000-777770] <764400>
UNIBUS Vector [octal 000-770] <FLOATING>
UNIBUS BR Level [decimal 4-7] <5>
Tested by: EVDTA, EVDTB
- ATTACH
**** NOTE: EVDTB.EXE must be LOADED before ATTACHing the device. ****
ATT DW780 HUB DW0 3 4 ; attaches UBA TO 11/780
or
ATT DW750 HUB DW0 ; attaches UBA to 11/750
or
ATT DW730 HUB DW0 ; attaches UBA to 11/730
The following is an example of how to attach a KCT32 :
DS> LOAD EVDTB.EXE ; Load The Diagnostic
DS> ATT KCT32 ; Attach The KCT32
DEVICE LINK? DW0 ; The Option Is Linked To The UBA
DEVICE NAME? UKA0 ; The Option Is Named Unit A (Range=A-Z)
; and numbered 0
CSR? 764400 ; The CSR Adrs In Octal (Range=760000-777770)
VECTOR?300 ; Vector Adrs In Octal (Range=000-770)
BR? 5 ; BR Interrupt Level Is 5 (Range=4-7)
DS> SEL UKA0 ; Select The KCT32 For Testing
; UKB for 2nd unit
; UKC for 3rd unit
; UKD for 4th unit
The above attach could have been done in a single line of input, as follows :
DS> ATT KCT32 DW0 UKA0 764400 300 5
- DATA_PATTERNS
Complete descriptions of the comprehensive test patterns used are
given in the VAX-11 Diagnostic Design Guide, under "Guidelines
for Register Testing", section 6.6. The KCT is a 16 bit machine
so 5 data patterns are used.
- SECTIONS
DEFAULT section is run when "START" is typed. It runs all tests
in the diagnostic.
See also QUICK.
- QUICK
The QUICK section runs the default section, omitting the test
of BiSync and Asynchronous protocols in Test 2, subtest 1.
- EVENT_FLAGS
EXTERNAL LOOPBACK FLAG
Setting event flag number 2 enables external loopback of the data.
When using external loopback make sure the lines are looped back,
using the loopback cables provided, line 0 looping to line 0
and line 1 looping to line 1.
See also REQUIREMENTS
422 PROTOCOL FLAG
When using external loopback mode with a 422 distribution panel
set event flag number 3 along with number 2. This assumes that
both distribution panels are 422s.
- SUMMARY
The SUMMARY section is not implemented by this diagnostic.
- ERRORS
Errors are reported by the program as they occur (if not
inhibited). The report conforms to the Diagnostic Supervisor
error report format, and consists of a description of the
error, the test number, subtest number, device address,
and basic And extended error information.
ERROR MESSAGE EXAMPLE 1
******** KCT32 Functional Level Diagnostic - 1.0 *******
Pass 1, Test 2, Subtest 0, Error 2 15-MAY-83 09:01:42.36
Hard Error while testing : UKA0:
Error during Load and Start instruction on Line 1 <Channel A>
Returned "Device Timeout" Error Status.
******* End of Hard Error number 2 ***********************
NOTE: The Error Message Printout Routines Are Set for Extended
Message Format. The Error Display will stop after 8 byte com-
parison errors on one data buffer. If any errors are found in
a data buffer, the number of bad bytes found will be summarized.
- REQUIREMENTS
HARDWARE REQUIREMENTS
VAX-11 Family Processor with enough memory to run VMS
VAX-11 Family UNIBUS Adaptor
KCT32 Micro Processor Option
External Loopback connectors (test connectors)
Part #H325
SOFTWARE REQUIREMENTS
VAX/VMS Operating System (Version 3.2 or Later)
VAX Diagnostic Supervisor ( 6.7 Or Later)
UKDriver must be loaded
EVDTB.Mic and EVDTA.Mic must be present in [SYSMAINT]
PREREQUISITES
Functional VAX-11 Family Central Processor And Memory
Functional UNIBUS Channel Adapter
Functional Console Terminal
Functional VAX/VMS Diagnostic Supervisor
Functional VAX/VMS Operating System
- EPROM_Version_Numbers
The EPROM Version Numbers are provided for informational
purposes only. The numbers for the On-Board versions
probably will NOT be identical to the Loaded versions.
If you suspect that the On-Board firmware and the Loadable
firmware are incompatible, call your Software Representitive
to get the current version numbers. If those numbers do
not match those printed out by the Level 2, then you need
to obtain new firmware.