DataMuseum.dk

Presents historical artifacts from the history of:

Rational R1000/400 DFS Tapes

This is an automatic "excavation" of a thematic subset of
artifacts from Datamuseum.dk's BitArchive.

See our Wiki for more about Rational R1000/400 DFS Tapes

Excavated with: AutoArchaeologist - Free & Open Source Software.


top - download

⟦5552e037e⟧ ERRMESS, TextFile

    Length: 2048 (0x800)
    Types: ERRMESS, TextFile
    Names: »P1FIU.ERRMESS«

Derivation

└─⟦b4205821b⟧ Bits:30000743 8mm tape, Rational 1000, DFS, D_12_7_3 SEQ288
    └─ ⟦this⟧ »P1FIU.ERRMESS« 
└─⟦b434774df⟧ Bits:30000528 8mm tape, Rational 1000, DFS, D_12_6_5
    └─ ⟦this⟧ »P1FIU.ERRMESS« 
└─⟦bc1274df5⟧ Bits:30000750 8mm tape, Rational 1000, DFS backup from PAM's R1000
    └─ ⟦this⟧ »P1FIU.ERRMESS« 

TextFile

0	No errors found in PHASE1 of the FIU BOARD test.
1	The FIU's status after a hard reset was not ES_RESET.
2	The FIU RESET command did not assert FSM_DONE.
3	The FIU TRIGGER_SCOPE command did not assert FSM_DONE and
	the diagnostic to find and isolate problems with DIAGFREEZE~
	found no errors.
4	The FIU TRIGGER_SCOPE command did not assert FSM_DONE and
	no further isolation was done.  The error could be caused by
	a problem with the DIAGFREEZE~ signal.
5	FIU FSM_DONE error.  The FIU responded with a DONE status when
	a RUNNING status was expected.
6	FIU FSM_DONE error.  The FIU responded with a DONE status when
	a RUNNING status was expected.  No further isolation was done.
7	While trying to isolate why the FIU could not drive freeze the
	TEST_PAREG experiment would not run to completion.
8	The FIU BOARD PARITY SCAN CHAIN TEST failed.
9	The FIU BOARD MACHINE_CHECK TEST failed.
10	All tests that see if the FIU can assert DIAGFREEZE~ and get
	its DFSM in the FREEZE state have failed, yet the FREEZE
	isolation program found no errors.
11	All tests that see if the FIU can assert DIAGFREEZE~ and get
	its DFSM in the FREEZE state have failed, but no further
	isolation has been done.
12	The FIU can assert DIAGFREEZE~ by forcing it with the DFSM,
	yet trying to assert DIAGFREEZE~  due to a parity error
	has failed.  This could be caused by a bad DFSM prom
	or MACHINE_CHECK~ is not connected to pin 12 of DNAN3D.
13	The FIU could not disable its DFSM from getting frozen by
	asserting MY_FREEZE.EN~.
14	The FIU BOARD MAR_SCAN_CHAIN TEST failed.
15	The FIU BOARD MDR_SCAN_CHAIN TEST failed.
16	The FIU BOARD UIR_SCAN_CHAIN TEST failed.
17	The FIU BOARD UIR_SCAN_CHAIN TEST failed, and no further isolation
	was done.  The error could be due to SYNC being stuck low.
18	The FIU BOARD MAR_TO_UIR test failed.
19	The FIU's NOVRAM CHECKSUM is incorrect.
20	The NOVRAM on the FIU board has an incorrect PART_NUMBER.
21	The FIU NOVRAM DATA test failed.
22	The FIU NOVRAM ADDRESS test failed.«nul»