User`s guide

System Troubleshooting and Diagnostics
5.3 Power-On Self-Test (POST) and ROM-Based Diagnostic (RBD) Failures
Subtest log is two hex digits identifying, usually within 10 instructions,
where in the diagnostic the error occurred.
Loop_subtest_log is an additional log generated out of the current test
specified by the current test number and subtestlog. Usually these logs
occur in common subroutines called from a diagnostic test.
Error_type (diagnostic executive error) signals the diagnostic’s state and
any illegal behavior. This field indicates a condition that the diagnostic
expects on detecting a failure. FE or EF in this field means that an
unexpected exception or interrupt was detected. FF indicates an error as a
result of normal testing, such as a miscompare. The possible codes are:
Error Code Description
FF Normal error exit from diagnostic
FE Unanticipated interrupt
FD Interrupt in cleanup routine
FC Interrupt in interrupt handler
FB Script requirements not met
FA No such diagnostic
EF Unanticipated exception in executive
ASCII messages Shows the name of the listing file that contains the failed
diagnostic.
Ve c identifies the SCB vector through which the unexpected exception or
interrupt trapped, when the de_error field detects an unexpected exception
or interrupt (FE or EF).
Prev_errs is four hex digits showing the number of previous errors that
have occurred (four in Example 5–11).
Lines 2 and 3 of the error printout are parameters 1 through 10. When the
diagnostics are running normally, these parameters are the same parameters
listed in Example 4–4.
When returning a module for repair, always record the the test number,
subtest, and Err_type from line 1 of the printout. Also record the Vec from line
2. If possible, record additional information. If the error can be saved onto a
printer, then enclose the full printout with the failing module.
5–42 System Troubleshooting and Diagnostics