NAME

grex2.diag − Exception tests for graphics boards, pt.2 of 3

DESCRIPTION

In the system, all boards are supposed to be capable of detecting certain kinds of exception conditions, no matter which board in the system actually caused the problem.  This test checks that the graphics board is able to detect all of this class of errors. 

DETAILS

The test initiates a bus transaction between the CPU board and the memory board and, as in cpmex1.diag (and cpmex2.diag), deliberate errors are forced using the test register on the CPU board.  Following receipt of the interrupt that is expected, the test checks that the graphics board also registered the same error. 

BOARDS THAT MUST BE INSTALLED

This test needs a CPU board, at least one memory board,  a graphics board, and a known good I/O board for downloading the test. 

SPECIAL COMMAND LINE PARAMETERS

None

MENU ITEMS SPECIFIC TO THIS TEST

rtResponder test - this is the only test in the menu.  The graphics board is simply acting as a bus watcher in this case.  The error of some kind has been deliberately set, and though the graphics board is not a participant, it is expected to notice that this kind of error occured and latch it into its own S Bus Status register. 

INTERPRETING THE ERROR CODES

The following errors may be generated by this test.  (The actual error wording may differ, however the type of error is as summarized here.) 

206The test was not able to find a memory board that it could use for this test. 

210The graphics board S Bus Status register failed to register the error that was generated. 

September 02, 1992