Technical data

Solving Startup Problems
B-2 Computer Group Literature Center Web Site
B
II. There is a display
on the terminal,
but input from the
keyboard has no
effect.
A. The keyboard
may be connected
incorrectly.
Recheck the keyboard connections and power.
B. Board jumpers
may be
configured
incorrectly.
Check the board jumpers as described in this manual.
C. You may have
invoked flow
control by
pressing a
HOLD
or
PAUSE key, or
by typing:
<CTRL>-S
Press the HOLD or PAUSE key again.
If this does not free up the keyboard, type in:
<CTRL>-Q
III. Debug prompt
172-Bug> does
not appear at
powerup, and the
board does not
autoboot.
A. Debugger
EPROM/Flash
may be missing.
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
RESET
and
ABORT switches at the same time; release RESET first, wait
seven seconds, then release
ABORT.
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.
B. The board may
need to be reset.
IV. Debug prompt
172-Bug>
appears at
powerup, but the
board does not
autoboot.
A. The initial
debugger
environment
parameters may
be set incorrectly.
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.
!
Caution
Performing the next step
(env;d) will change some
parameters that may affect your
system’s operation.
(continues>)
B. There may be
some fault in the
board hardware.
Table B-1. Troubleshooting MVME172LX Boards
Condition Possible Problem Try This: