User`s manual

T-6
Troubleshooting CPU Boards: Solving Startup Problems
T
Table T-3. Troubleshooting MVME162 Series Boards Only
Condition Possible Problem Try This:
III. Debug
prompt
162-Bug>
does not appear
at powerup, and
the board does
not auto boot.
A. Debugger
EPROM/Flash
may be missing
1. Disconnect all power from your system.
2. Check that the proper debugger EPROM is installed
per this manual.
3. Remove jumper from J22, pins 9 and 10. This enables
use of the EPROM instead of the Flash memory.
4. Reconnect power. Restart the system.
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
162-Bug>
appears at
powerup, but the
board does not
auto boot.
A. The initial
debugger
environment
parameters may
be set wrong.
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.
2. Type in
env;d <CR>
This sets up 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>
After a cold start, the debug prompt
162-Bug>
is displayed. (continues>)
B. There may be
some fault in the
board hardware.