SBCTRBA/LT1 January 1996 Dear Valued Customer: Thank you for your purchase of a Motorola Computer Group single board computer (SBC) CPU (68K or 88K) board product.
Troubleshooting CPU Boards 2
ATroubleshooting CPU Boards: Solving Startup Problems T ❏ Try these simple troubleshooting steps before calling for help or sending your CPU board back for repair. ❏ Some of the procedures will return the board to the factory debugger environment. (The board was tested under these conditions before it left the factory.) ❏ Selftest may not run in all user-customized environments. Table T-1. Basic Troubleshooting Steps for ALL CPU Boards Condition Possible Problem Try This: I.
T Troubleshooting CPU Boards: Solving Startup Problems Table T-1. Basic Troubleshooting Steps for ALL CPU Boards (Continued) Condition Possible Problem Try This: 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.
T Table T-2. Troubleshooting MVME147 Series Boards Only Condition Possible Problem Try This: III. Debug prompt A. Debugger EPROM may be missing. 147-Bug> does not appear at powerup, and the board does not auto boot. B. The board may need to be reset. 1. Disconnect all power from your system. 2. Check that the proper debugger EPROM is installed per this manual. 3. Reconnect power. ! Caution Performing the next step will change some parameters that may affect your system operation. 4.
T Troubleshooting CPU Boards: Solving Startup Problems Table T-2. Troubleshooting MVME147 Series Boards Only (Continued) Condition Possible Problem Try This: IV. Debug prompt A. The initial debugger environment parameters may be set wrong. 147-Bug> appears at powerup, but the board does not auto boot. B. There may be some fault in the board hardware. 1. Type in env;d This sets up the default parameters for the debugger environment. 2. When prompted to Update Non-Volatile RAM, type in y 3.
T Table T-2. Troubleshooting MVME147 Series Boards Only (Continued) Condition Possible Problem Try This: V. The debugger is in system mode and the board auto boots, or the board has passed selftests. A. No problems troubleshooting is done. No further troubleshooting steps are required. VI. The board has failed one or more of the tests listed above, and can not be corrected using the steps given. A. There may be some fault in the board hardware or the on-board debugging and diagnostic firmware. 1.
T Troubleshooting CPU Boards: Solving Startup Problems Table T-3. Troubleshooting MVME162 Series Boards Only Condition Possible Problem Try This: III. Debug prompt A. Debugger EPROM/Flash may be missing does not appear at powerup, and the board does not auto boot. B. The board may need to be reset. 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.
T Table T-3. Troubleshooting MVME162 Series Boards Only (Continued) Condition Possible Problem Try This: 5. Change to the diagnostic directory by typing sd Now the prompt should be 162-Diag> 6. Run selftest by typing in st The tests take as much as 10 minutes, depending on RAM size. They are complete when the prompt returns. (The onboard selftest is a valuable tool in isolating defects.) 7. The system may indicate that it has passed all the selftests. Or, it may indicate a test that failed.
T Troubleshooting CPU Boards: Solving Startup Problems Table T-4. Troubleshooting MVME166/167/176/177/187/188/188A Boards Only Condition Possible Problem Try This: III. Debug prompt A. Debugger EPROM/Flash may be missing 1xx-Bug> does not appear at powerup, and the board does not auto boot. T-8 B. The board may need to be reset. 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.
T Table T-4. Troubleshooting MVME166/167/176/177/187/188/188A Boards Only (Continued) Condition Possible Problem Try This: IV. Debug prompt A. The initial debugger environment parameters may be set wrong. 1xx-Bug> appears at powerup, but the board does not auto boot. B. There may be some fault in the board hardware. 1. Start the onboard calendar clock and timer. Type set mmddyyhhmm where the characters indicate the month, day, year, hour, and minute. The date and time will be displayed.
T Troubleshooting CPU Boards: Solving Startup Problems Table T-4. Troubleshooting MVME166/167/176/177/187/188/188A Boards Only (Continued) Condition Possible Problem Try This: 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 and step 3. 7. Run selftest by typing in st The tests take as much as 10 minutes, depending on RAM size. They are complete when the prompt returns.
T Table T-5. Troubleshooting MVME197 Series Boards Only Condition Possible Problem Try This: III. Debug prompt A. Debugger EPROM/Flash may be missing 197-Bug> does not appear at powerup, and the board does not auto boot. B. The board may need to be reset. 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.
T Troubleshooting CPU Boards: Solving Startup Problems Table T-5. Troubleshooting MVME197 Series Boards Only (Continued) Condition Possible Problem Try This: IV. Debug prompt A. The initial debugger environment parameters may be set wrong. 197-Bug> appears at powerup, but the board does not auto boot. B. There may be some fault in the board hardware. 1. Start the onboard calendar clock and timer. Type set mmddyyhhmm where the characters indicate the month, day, year, hour, and minute.
T Table T-5. Troubleshooting MVME197 Series Boards Only (Continued) Condition Possible Problem Try This: 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 and step 3. 7. Run selftest by typing in st The tests take as much as 10 minutes, depending on RAM size. They are complete when the prompt returns. (The onboard selftest is a valuable tool in isolating defects.) 8.
T Troubleshooting CPU Boards: Solving Startup Problems T-14
