User`s manual

MOTOROLA Minimal PowerPC 603e Evaluation Board 15
Appendix A Troubleshooting
Table 6 provides some failure conditions and probable causes.
Table 6. Failure Analysis
Problem Symptom Possible Cause
Nothing happens on the terminal
after powerup.
All LEDs Off 5V Supply
Error, Status, ROM LEDs on ROM or RAM test failed
Corrupted or no code in ROM
PLL jumpers incorrect (too fast/slow)
PLL in bypass (no jumpers installed)
Power Supply Connection Faulty -
unplug and reconnect
Wiggler hardware interference -
disconnect Wiggler and try again
Error LED on, Status LED off Duart test failed
dl command ÒhangsÓ forever DINK prompt never returns Corrupted s-records
Baud rate too fast?
S-Record downloads cause DINK
error 0xfb00..
Autotyping results in
Òunrecognized command or
symbol error.Ó
Bits lost in serial transmission. Add
delay between lines in Autotype
protocol settings on terminal emulator.
Nothing happens on the terminal
after go nnnnn command.
ROM access LED ßashing Code has branched into ROM and is
looping there. Push reset.
SRAM access LED ßashing Code is in an inÞnite loop in RAM.
Wiggler might halt the processor and
provide the location of the currently
executing instruction.
No access LEDs ßashing Code is in an inÞnite loop in cache or
processor has taken a machine check.
Push reset.
Performance less than expected Code runs ÒslowÓ or SRAM access
LED ßashes during cache-bound
program.
Caches disabled. Modify HID0 register
to 0x8000c000
Data accesses are slow DCache marked Òcache inhibitedÓ for
user code. Modify dbat1l register to
0x00000012.
Heat sink area or processor is Òtoo
hotÓ to touch.
Physical contact with the board is
painful.
Processor is running Òtoo fastÓ for
ambient cooling conditions. Reduce
speed via PLL_CFG jumpers or cool
with moving air.