- Help
EVWAB is a standalone diagnostic which currently supports the
VS100 graphics workstation. Up to sixteen device may be selected
for testing. Testing mode is sequential, one device tested per
program pass.
- Attach
Attaching to 11/780 CPU
Diagnostic Supervisor. ZZ-ESSAA-6.12.937 15-Jan-1983 12:00:00.00
DS> Load EVWAB
DS> Attach DW780 Hub DW0 3 4
DS> Attach VS100 DW0 VBA0 760440 700 5
DS> Select VBA0
DS> Start
Attaching to 11/750 CPU
Diagnostic Supervisor. ZZ-ECSAA-6.12-346 15-Jan-1983 12:00:00.00
DS> Load EVWAB
DS> Attach DW750 Hub DW0 4
DS> Attach VS100 DW0 VBA0 760440 704 5
DS> Select VBA0
DS> Start
Attaching to 11/730 CPU
Diagnostic Supervisor. ZZ-ECNAA-6.12-463 15-Jan-1983 12:00:00.00
DS> Load EVWAB
DS> Attach DW730 Hub DW0
DS> Attach VS100 DW0 VBA0 760440 710 5
DS> Select VBA0
DS> Start
- Sections
EVWAB contains the following sections: DEFAULT, UBW, ROM, MICRO,
GRAPHICS, COPY, DRAW, FLOOD, FILL, PRINT, MANUAL and MONITOR.
All tests are contained within the DEFAULT section with the
exception for the Idle Loop Monitor and manual intervention tests
which are contained in the MONITOR and MANUAL sections respectively.
- UBW
This section may be used to test the Unibus Window Module while it
is disconnected from the remaining portions of the VS100 subsystem
The maintenance mode testing can either be done with electrical
loop back or optical loop back (see event flag 21). Note that
running this section while the UBW is connected to the subsystem
or running the default section while the UBW is disconnected may
cause erroneous errors from the diagnostic.
- ROM
This section provides an easy access to all of the tests which perform
excersizes on the resident ROM code.
- Micro
This section is provided as an easy means of invoking the ROM
resident micro diagnostics within the VS100. Errors detected by
the VS100 micro diagnostics will be sent to the host and reproted
by the diagnostic. Error codes will be transformed to an english
language representation.
- Graphics
This section gives easy access to those tests which excersize the
graphics functions of the 68000. There are five sub-sections
contained within this section, they are as follows; Copy, Draw,
Flood, Fill, and Print. Each of these sections allows for the
diagnostic program to continually loop on the suspected function
if the operator so desires. Each of these tests will (when not
in QUICK mode) read back the screen and decide whether the screen
was printed correctly or not. Please note that when the QUICK flag
is set the run time for the program is cut by more than half, but
the program does not perform the screen check. Visual screen checking
would be necessary.
- Copy
This section contains four copy function tests. It provides
easy access and looping capabilities to this specific function.
The tests will exersize the VS100'S ability to copy Host memory,
off screen memory, and visible screen memory; to perform large
block data transfers; to perform logical functions on bitmap data,
and to copy and overlap a bitmap.
- Draw
This section contains two draw function tests. It provides
easy access and looping capabilities to the Draw Line and
Draw Curve Tests. The tests will draw a series of random sized
triangles, a string art type design, and then a series of expanding
circles.
- Flood
This section tests the flood function. It provides
easy access and looping capabilities to this specific function.
The monitor will be set up with an area boundary to be flooded
with all of the half-tones.
- Fill
This section tests the fill function. It provides
easy access and looping capabilities to this specific function.
A series of polygons are used as the borders while a seed is
placed within these borders to fill the area.
- Print
This section exercises the print text function. The entire screen
is filled with text. It provides easy access and looping capabilities
to this specific function.
- Monitor
This section may be used to monitor the condition of the VS100
multibox logic by starting the ROM resident idle diagnostic loop
on all devices selected for testing and then monitoring the device
status on a continual basis. Monitor times can be set from 1 minute
to 24 hours, and a per device error limit may be set by the operator
at which point a selected device will be dropped from the monitor.
Time stamps showing the number of devices running are given every
15 minutes.
- Manual
This section is used for manual intervention and may be useful in
trouble shooting specific problems. It contains graphics functions
as well as rom based housekeeping functions.
- Commands
* Indicates that a load function is required initially
in order to down load micro code for graphics functions.
The following are legal operator supported functions:
Reset -- Perform device initialize
Powerup -- Perform resident micro diagnostics
Link on -- Turn fiber optics on
Link off -- Turn fiber optics off
Finite -- Set 68k crc retries to finite (128)
Infinite -- Set 68k crc retries to infinite
Load -- Load microcode to VS100
BBA on --* Enable BBA operation (only valid after load
function)
BBA off --* Disable BBA operation (only valid after load
function)
Clear --* Clear screen to black or white
Copy --* Copy a block of black, white or haltone to
the screen
Print --* Repeatedly print user selected text
Fill --* Perform fill area function
Flood --* Flood and area of the screen
Draw --* Draw straight or curved lines on the screen
Exit -- Exit from this test
- Requirements
EVWAB requires one additional files for diagnostic operation. This
file is the VS100 loadable graphics microcode EVWAA.BIN
which is used during any test that requires graphics functions
This file is packaged with the diagnostic by the
Software Distribution Center. In the event that this file becomes
lost it will be necessary to use the microcode files located on the
user system disk in directory VSTA$MICRO:EVWAA.BIN. In order for
the diagnostic to gain access to these files it will be necessary to
ATTACH the user system disk and after loading the diagnostic, use the
Diagnostic Supervisor SET LOAD command to use DxA0:[SYSEXE] as the
default load area.
Also, please note that using console media as the default load device
will increase program run times.
- Summary
Summary messages are printed at the end of each pass for all selected
devices. Error totals are cumulative. Summary messages may be
deleted by using the following command DS> SET IES
- Run_Times
Run times are approximately 9 minutes per device depending on the
event flags, section options selected, and the type of load media
available.
- Event_Flags
Event Flag 23
When set, this flag will enable idle loop testing of a device while
other devices are being tested by the diagnostic. This flag can only
be enabled when more than one device has been selected for testing,
multiple passes have been selected, and the running section of the
diagnostic is the DEFAULT section.
Event Flag 22
When set will cause the unit under test to be deleted from the
testing sequence when an error has been detected.
Event Flag 21
This flag, when set specifies that the optical loop is present on
the UBW module.
Event Flag 20
When set will cause stalls within the program in order to aid the
operator in inspecting images presented on the monitor. Please note
that this can cause diagnostic run times to be greatly exagerated.
Event Flag 19
This flag, when set will cause error report messages to occur for
retryable link CRC errors and link transitions. Otherwise these
errors will be accumulated by the program and outputed only during
the program run time summary messages.
Event Flag 18
Under normal operation the default micro code file is EVWAA.BIN
located on the default diagnostic supervisor device directory.
This flag, when set will allow the operator to enter a substitute
file designation for the micro code to be down loaded to the
workstation. The format is ddcu:[directory]file-name. If the
device is not the current load device the device must be attached
using the diagnostic supervisor attach interface commands.
Event Flag 17
This flag, when set will cause the command "SET BAA OFF" to be sent
following a microcode load operation. This will prevent the micro
code from using the BBA for graphics commands. This flag may be set
when it is suspected that the BBA may be faulty.
- Tests
The following tests are included in EVWAB.
Test 1: UBW Register Access Test * UBW
Test 2: UBW Register Data Test * UBW
Test 3: UBW Maintenance Loop Test * UBW
Test 4: Link Continuity Test * UBW
Test 5: Link Transition Interrupt Test * UBW
Test 6: Maintenance Loop Interrupt Test * UBW
Test 7: Reset Function Test * ROM
Test 8: Resident Micro Diagnostic Test * ROM, Micro
Test 9: 68000 Interrupt Test * ROM
Test 10: DMA Transfer Timeout Test * ROM
Test 11: CRC Error Dectection Test * ROM
Test 12: Report Status Test * ROM
Test 13: Link Data Test * ROM
Test 14: VS100 Program Memory Data Test * ROM
Test 15: VS100 Frame Buffer Data Test * ROM
Test 16: CRC Error Recovery Test * ROM
Test 17: M68000 Data Flow Test * ROM
Test 18: BBA Data Flow Test * Graphics, Copy
Test 19: BBA Extended Transfer Test * Graphics, Copy
Test 20: Mapping Functions Test * Graphics, Copy
Test 21: BBA Computed Direction Test * Graphics, Copy
Test 22: Cursor Positioning Test * Graphics
Test 23: Draw Line Test * Graphics, Draw
Test 24: Draw Curve Test * Graphics, Draw
Test 25: Flood Function Test * Graphics, Flood
Test 26: Fill Area Function Test * Graphics, Fill
Test 27: Print Text Function Test * Graphics, Print
Test 28: Manual Intervention Section * Manual
Test 29: Idle Test Monitor Section * Monitor