Table of Contents
Advertisement
Troubleshooting CPU Boards
Table D-1. Troubleshooting MVME162LX Boards (Continued)
Condition
II. There is a
display on the
terminal, but
input from the
D
keyboard
and/or mouse
has no effect.
III. Debug prompt
162-Bug>
does not
appear at
power-up, and
the board does
not autoboot.
IV. Debug prompt
162-Bug>
appears at
powerup, but
the board does
not autoboot.
D-2
Possible Problem
Try This:
A. The keyboard or
Recheck the keyboard and/or mouse connections and
mouse may be
power.
connected
incorrectly.
B. Board jumpers
Check the board jumpers per this manual.
may be
configured
incorrectly.
C. You may have
Press the
invoked flow
If this does not free up the keyboard, type in:
control by
<CTRL>-Q
pressing a
or
HOLD
PAUSE
key, or by
typing:
<CTRL>-S
A. Debugger
1. Disconnect all power from your system.
EPROM/Flash
2. Check that the proper debugger EPROM or debugger
may be missing
Flash memory is installed per this manual.
3. Reconnect power.
B. The board may
need to be reset.
4. Restart the system by "double-button reset": press the
RESET
RESET
5. If the debug prompt appears, go to step IV or step V, as
indicated. If the debug prompt does not appear, go to step
VI.
A. The initial
1. Start the onboard calendar clock and timer. Type:
debugger
set mmddyyhhmm <CR>
environment
where the characters indicate the month, day, year, hour,
parameters
and minute. The date and time will be displayed.
may be set
incorrectly.
B. There may be
some fault in the
board hardware.
or
key again.
HOLD
PAUSE
and
switches at the same time; release
ABORT
first, wait seven seconds, then release
Performing the next step
!
(env;d) will change some
parameters that may affect
Caution
your system's operation.
.
ABORT
(continues>)
Advertisement
Table of Contents
