⟦168407f21⟧

TextFile

0	No errors found in PHASE1 of the VAL BOARD test.
1	The 8751 was not in the RESET state when it was polled immediately
	after a global reset was issued;
2	After a global reset, the TRIGGER_SCOPE command was executed but it
	never got to the DONE state.
3	After a global reset, the TRIGGER_SCOPE command was executed but it
	never got to the DONE state. No further isolation was done. The error
	could be caused either by FREEZE being stuck low or by a problem on
	the VAL board.
4	The VAL BOARD is unable to read its own board id.
5	The parity register (PAREG) scan chain cannot scan correctly.
6	The UIR scan chain cannot scan correctly.
7	The VAL board UIR scan chain test failed, and no further isolation
	was done.  The error could be caused either by SYNC being stuck low,
	or a problem on the VAL board.
8	The WDR scan chain cannot scan correctly.
9	The mode bits of the VAL BOARD DFSM are not working correctly.
10	The VAL BOARD cannot generate a MACHINE check correctly.
11	The NOVRAM on the VAL BOARD returned a bad checksum when the 
	PART TYPE location was read.
12	The contents of the PART TYPE location in the NOVRAM was incorrect
	(i.e. the NOVRAM does not think this is a VAL board).
13	The NOVRAM on the VAL BOARD returned a bad checksum when the 
	BOARD REV NUMBER location was read.
14	An invalid REV number for any VAL board was stored in the NOVRAM.
15	The NOVRAM on the VAL BOARD returned a bad checksum when the 
	ECO LEVEL location was read.
16	This VAL board does not have all of the ECO's installed on it that
	are necesary for running the complete set of FRU isolation tests.
	Report this error to your RATIONAL customer service representative
	to get a new VAL board.
17	The NOVRAM on the VAL BOARD does not pass the read/write test.«nul»
DataMuseum.dk

Rational R1000/400 DFS Tapes

⟦168407f21⟧ ERRMESS, TextFile

Derivation

TextFile
