C-2
Computer Group Literature Center Web Site
Troubleshooting CPU Boards: Solving Startup Problems
C
II. There is a
display on the
terminal, but
input from the
keyboard
and/or mouse
has no effect.
A. The keyboard or
mouse may be
connected
incorrectly.
Recheck the keyboard and/or mouse connections and power.
B. Board jumpers
may be
configured
incorrectly.
Check the board jumpers per 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
PPC1-Bug>
does not
appear at
power-up,
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 EPROM or debugger Flash
memory is installed per this manual.
3. Reconnect power.
4. Restart the system by pressing the
RESET
switch.
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.
B. The board may
need to be reset.
IV. Debug
prompt
PPC1-Bug>
appears at
power-up, 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 will change
some parameters that may affect your
system operation.
(continues>)
B. There may be
some fault in the
board hardware.
Table C-1. Troubleshooting MVME2603/2604 Boards (Continued)
Condition
Possible Problem
Try This: