Motorola MVME162P2 Series Installation And Use Manual page 114

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