Table of Contents
Advertisement
Check the est Status LEDs, then locate that test number in the table to determine what to
do. For test numbers above 19, the name of the test is usually in the failure message, so look
for the test name in able 4-1. Refer to the \Service Related Menus" section of this guide for
detailed descriptions of each test.
Note
Not all error messages are listed in the table. Many error messages describe the
problem clearly and require no further explanation, so they are not included in
this guide.
Some error messages are only partially reproduced, because the remainder of
the message is speci c to the error (e.g., provides address at which the failure
occurred).
<
num indicates either an address or a value. hese may be in decimal or
hexadecimal notation.
Test
Test Name
1
680x0 Processor
2
BootROM Checksum
3
Main ROM Checksum Errors: Same as for test #2.
Table 4-1. Analyzer Self-Tests
Applicable Error Messages and Notes
Errors begin with \CPU TEST F IL."
Remove CPU board, and check U105, U106, and TP103 (CPU clock). Then check
U121 and U122. If test still fails, replace CPU board.
Errors:
Bad checksum table at . . .
ROM Checksum Failure in bank . . .
Checksum Table is Blank. ROM may be blank.
Unexpected ROM Id at num
Bad ROM count in Checksum table . ..
Bad ROM size in Checksum table . . .
This tests checksum of bootROM chip. Replace CPU board or U335.
This tests checksum of main
ash EPROM. Reload rmware from
oppy disk. If
test still fails, replace the CPU board or check U301 and the EPROM chips
U302-U305 or U308 and U309 (whichever are loaded).
>
T roubleshoot ng and Block D agrams
4-11
Advertisement
Table of Contents
