Table of Contents
Advertisement
Troubleshooting the MVME177: Solving Startup Problems
Condition ...
F
V. The debugger
is in system mode
and the board
auto boots, or the
board has passed
selftests.
VI. The board has
failed one or
more of the tests
listed above, and
can not be
corrected using
the steps given.
F-4
Table F-1. Basic Troubleshooting Steps (Continued)
Possible Problem ...
A. No problems -
troubleshooting is
done.
A. There may be some
fault in the board
hardware or the on-
board debugging and
diagnostic Þrmware.
Try This ...
6.You may need to use the cnfg command (see
your board Debugger Manual) to change clock
speed and/or Ethernet Address, and then later
return to
env <CR>
and step 3.
7. Run selftest by typing in
st <CR>
The tests take as much as 10 minutes,
depending on RAM size. They are complete
when the prompt returns. (The onboard
selftest is a valuable tool in isolating defects.)
8. The system may indicate that it has passed
all the selftests. Or, it may indicate a test that
failed. If neither happens, enter
de <CR>
Any errors should now be displayed. If there
are any errors, go to step VI. If there are no
errors, go to step V.
No further troubleshooting steps are required.
Note
Even if the board passes all tests,
it may still be bad. Selftest does
not try out all functions in the
board (for example, SCSI, or
VMEbus tests).
1. Document the problem and return the board
for service.
2. Phone 1-800-222-5640.
Advertisement
Table of Contents
