
User’s Manual 25
PRELIMINARY—SUBJECT TO CHANGE WITHOUT NOTICE
User’s Manual
If power is on and LEDs are active while reset pressed,
release reset and monitor PCI bus activity. If the PCI LED on the SP3 motherboard is
not active (flickering), DINK is not running
from the ROM. This can be caused by:
1. Improper configuration of the MPPMC
card (review configuration guide)
2. Improper configuration of the SP3 board
(refer to this document).
3. Socketed SDRAM loose (reseat).
Reseat socketed devices, and/or restore the
system to factory defaults (shaded settings
on MPPMC configuration guides and as
stated in this document).
If power is on, LEDs are active, system is in default
configuration. If the PCI LED flickers momentarily and
then stops, the cause could be the PCI boot
ROM:
1. A mis-programmed flash (user code)
2. Broken ROM socket (common with
mishandled PromJETs).
Restore or replace the DINK ROM and
retry. Also consider trying the ROM in a
second Sandpoint or verifying it on an
external programming system.
If power is on, LEDs are active, system is in default
configuration, and the PCI LED is active continuously: DINK is running. Check the serial port
connections.
1. Make sure you are using a null-modem
cable. A standard cable will not work.
2. Make sure the cable is in COM1 on the
Sandpoint system (nearest the power cord).
3. Make sure you’re using the COM port
your terminal expects (try the other one).
If power is on, LEDs are active, system is in default
configuration, and the PCI LED is active continuously, and
the connections are correct.
DINK is running. Check the terminal setup:
1. Check that the terminal is setup for no-
handshaking:
Remove the cable from the Sandpoint and
connect a wire or piece of metal between
pins 2 and 3. There are no dangerous
voltages present. If you can type on the
terminal, the handshaking is correct.
If power is on, LEDs are active, system is in default
configuration, and the PCI LED is active continuously, and
the connections and handshaking are correct.
Contact Motorola technical support.
DINK writes
characters to the
screen, but they’re
illegible.
Make sure the terminal program is set to 9600 baud, 8N1,
no handshaking. Check settings.
Make sure the DINK baud rate has not been changed with
the ENV command. Press the backspace key and hold it down
while pressing RESET. If DINK comes up,
enter the command “ENV -c”
Table6-1. Troubleshooting SP3
Problem What to Check Verify