Motorola MVME162P-344 Series Installation And Use Manual page 127

Table B-1. Troubleshooting MVME162P4 Boards
Condition Possible Problem
IV. Continued
V. The debugger is A. No apparent
in system mode
and the board
autoboots, or the
board has passed
self-tests.
http://www.motorola.com/computer/literature
Try This:
2. At the command line prompt, type in:
env;d <CR>
This restores the default parameters for the debugger
environment.
3. When prompted to Update Non-Volatile RAM, type in:
y <CR>
4. When prompted to Reset Local System, type in:
y <CR>
5. After the clock speed is displayed, immediately (within
five seconds) press the Return key:
<CR>
or
BREAK
to exit to the System Menu. Then enter a 3 for "Go to
System Debugger" and Return:
3 <CR>
Now the prompt should be:
162-Diag>
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 the selftests by typing in:
st <CR>
The tests take as long as 10 minutes, depending on RAM
size. They are complete when the prompt returns. (The
onboard self-test is a valuable tool in isolating defects.)
8. The system may indicate that it has passed all the self-
tests. 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.
problems —
troubleshooting is
done.
Solving Startup Problems
B-3
B