DEC DECstation 5000 Model 200 Maintenance Manual

Hide thumbs Also See for DECstation 5000 Model 200:

Table of Contents

Quick Links

Download this manual

EK-370AA-MG-002

DECstation 5000/

DECsystem 5000

Model 200

Maintenance Guide

digital equipment corporation

maynard, massachusetts

Table of Contents

Troubleshooting

Summary of Contents for DEC DECstation 5000 Model 200

Page 1 EK-370AA-MG-002 DECstation 5000/ DECsystem 5000 Model 200 Maintenance Guide digital equipment corporation maynard, massachusetts...
Page 2 First printing, April 1990 Second printing, October 1990 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document.
Page 3: Table Of Contents
Contents Using This Guide xvii ......... . . 1 A Look at DECstation/DECsystem 5000 Model 200 Hardware System Hardware Conﬁgurations .
Page 4 Removing and Installing a Serial Number Plate ..2–9 To Remove a Serial Number Plate ....2–9 To Install a Serial Number Plate .
Page 5 Distinguishing Event Types ......3–11 Memory error logs ......3–11 Error and status register error logs .
Page 6 Removing and Installing the Keyboard and Mouse ..5–18 To remove the keyboard and mouse and their cables ........5–19 To install the keyboard and mouse and their 5–19...
Page 7 e Command ........C–17 erl Command .
Page 8 Floating-Point Unit (FPU) Test ..... . D–21 FPU test error messages ..... D–21 RAM Select Lines Test .
Page 9 cnfg Command ........E–5 Conﬁguration summary ..... . E–5 SCSI, Ethernet, and graphics conﬁgurations .
Page 10 Serial Line Mixed Silo Test ......F–9 Serial line single silo parameters and error messages ........F–9 Modem and Printer Test .
Page 11 Registers Test ........F–28 Registers test parameters and error codes ..F–28 Internal Loopback Test .
Page 12 Box Test ......... F–46 Box test parameters and error codes .
Page 13 Removing hardware from an old system module ... 5–5 Installing hardware on a new system module ... . . 5–7 ESAR chip location .
Page 14 Major FRUs ......... . B–3 Basic Components .
Page 15 Serial Line Test Error Codes ......F–5 Serial Line Silo Alarm Test Parameters ....F–6 Serial Line Silo Alarm Test Error Codes .
Page 16 F-42 Collision Test Error Codes ......F–33 F-43 Promiscuous Mode Test Parameters ..... . F–34 F-44 Promiscuous Mode Test Error Codes .
Page 17: Using This Guide
Using This Guide Intended Audience This guide is for Digital customer service representatives who have completed training in DECstation/DECsystem 5000 Model 200 maintenance. This guide assumes that you are familiar with basic maintenance and troubleshooting operations and that you have experience with desktop computer systems. How To Use This Guide This guide explains how to identify and replace failed ﬁeld- replaceable units (FRUs).
Page 18 To identify failed FRUs, refer to Chapter 4, ‘‘Identifying Failed FRUs.’’ For a description of the hardware, troubleshooting procedures, and replacement procedures for base system FRUs, refer to Chapter 5. For a description of the hardware, troubleshooting procedures, and replacement procedures for TURBOchannel options, drives, and monitors, refer to the TURBOchannel Maintenance Guide.
Page 19: Conventions Used In This Guide
Conventions Used in This Guide Table 1. Conventions Used in This Guide Convention Monospace Anything that appears on your monitor screen type is set in monospace type, like this. Boldface Anything you are asked to type is set in boldface type type, like this.
Page 20: Possible System Hardware Conﬁgurations
A Look at DECstation/DECsystem 5000 Model 200 Hardware This chapter describes Possible system hardware conﬁgurations Basic system hardware Optional system hardware A Look at DECstation/DECsystem 5000 Model 200 Hardware 1–1...
Page 21: System Hardware Conﬁgurations
System Hardware Conﬁgurations The DECstation/DECsystem 5000 Model 200 is a reduced instruction set computer (RISC), ULTRIX-based desktop sys- tem. Depending on the actual hardware, the system operates as either a server or a workstation. DECstation/DECsystem 5000 Model 200 system hardware includes basic hardware that supports graphics, drives, additional Ethernet connections, and additional memory.
Page 22 a t i o n / D E C s y s t e m 5 0 0 0 M o d e l 2 0 0 H a r d w a r e 1 – 3 h a r d w a r e c o n ﬁ g u r a t i o n s W S E 2 M 0 0 1 d r i v e s U p t o s e v e n...
Page 23: Basic System Hardware
Basic System Hardware The basic system hardware includes a system unit with controls, indicators, and system connectors. System Unit The system unit, shown in Figure 1-2, includes the following: One system module and chassis, which includes One central processing unit (CPU) One ﬂoating-point unit (FPU) One small computer system interface (SCSI) controller One serial line controller...
Page 24 a t i o n / D E C s y s t e m 5 0 0 0 M o d e l 2 0 0 H a r d w a r e 1 – 5...
Page 25: System Unit Controls And Indicators
System Unit Controls and Indicators The system unit controls and indicators, shown in Figure 1-3, have the following uses: The on/off switch turns the system on and off. Press down the 0 on the switch to turn off the power. Press down the 1 on the switch to turn on the power.
Page 26: System Unit Connectors
System Unit Connectors The system unit connectors, shown in Figure 1-4, have the following purposes: The power connector connects the system unit power supply and the system unit power cord. The monitor-to-system-unit connector provides electric power to the monitor power cord. The ThinWire Ethernet connector links the system unit to a ThinWire Ethernet.
Page 27: Decstation/Decsystem 5000 Connectors
Option module Monitor-to-system-unit connectors connector PM AG V~ 10 0-1 20 A 3.0 V~ 22 0-2 PM AZ 40 A 1.7 PM AD V~ 10 0- 12 0/2 20 A 7.9 /4. -2 40 Hz 50 -6 W 35 9 SCSI connector ThinWire...
Page 28: Hardware Options
Hardware Options The system module has slots for additional memory and TURBOchannel option modules. Figure 1-5 shows the location of memory and option module expansion slots on the system module. Option module Option module System expansion slots module Memory module Memory module expansion slots...
Page 29: Optional Turbochannel Modules
Optional TURBOchannel Modules The three TURBOchannel expansion slots on the system unit support a maximum of three option modules. Any optional SCSI or Ethernet controller modules operate in addition to the SCSI and ThickWire Ethernet controller built in to the system module. Drives Each SCSI controller supports up to seven drives that connect in a chain that attaches to the SCSI controller through the back...
Page 30: Service Operations
Service Operations This chapter explains how to perform routine service operations. It explains how to Avoid electrostatic damage when handling components Use an alternate terminal Remove the system unit cover Remove the front cover plate Remove and replace the serial number plate Install and remove terminators and loopback connectors Enter console mode and operating mode Use console command passwords...
Page 31: Using An Antistatic Kit
Using an Antistatic Kit The Digital antistatic kit contains the equipment you need to handle static-sensitive materials safely. When handling static-sensitive materials, always Place the antistatic wrist strap around your wrist and attach the other end of the strap to the snap-on fastener attached to the antistatic mat before you handle any static-sensitive item.
Page 32: Using An Alternate Terminal
Using an Alternate Terminal If the original monitor is not working properly, you can use an alternate terminal to run tests. When the alternate console is set, the alternate terminal displays the same text as a regular system monitor. You can use either the original or alternate keyboard to type commands.
Page 33 Remove any graphics modules installed in the system before Note: you enable the alternate terminal. Install a communications line adapter on the commu- nications line that is on the left as you face the back of the system. Refer to ‘‘Removing and Installing Loopback Connectors and Terminators’’...
Page 34: Removing And Installing The System Unit Cover
Removing and Installing the System Unit Cover Figure 2-3 shows how to remove and install the system unit cover. PM AG V~ 10 0-1 20 A 3.0 V~ 22 0-2 40 A 1.7 PM AZ PM AD V~ 10 0- 12 0/2 20 A 7.9 /4.
Page 35: To Remove The System Unit Cover
To Remove the System Unit Cover Turn off the system power. Disconnect the system unit power cord. Loosen the captive screw that holds the cover. Face the front of the system unit and grip each side of the system unit cover. Pull the cover toward you until it comes loose from the chassis.
Page 36: Removing And Installing The Front Cover Plate
Removing and Installing the Front Cover Plate Figure 2-4 shows how to remove and install the front cover plate. Captive screw System Front unit cover Captive chassis plate screw WSE2M014 Figure 2-4. Removing and installing the front cover plate Service Operations 2–7...
Page 37: To Remove The Front Cover Plate
To Remove the Front Cover Plate Make sure the system power is off. Remove the system unit cover. Refer to the previous section for directions. Loosen the two captive screws. Tilt the top of the plate down and lift it away from the chassis.
Page 38: Removing And Installing A Serial Number Plate
Removing and Installing a Serial Number Plate To Remove a Serial Number Plate Turn off the system unit power. Remove the system unit cover. Refer to ‘‘Removing and Installing the System Unit Cover’’ earlier in this chapter for directions. Peel the tamper-proof tape off the two nuts that hold the serial number plate.
Page 39 n s t a l l i n g a s e r i a l n u m b e r p l a t e W S E 2 M 0 5 0 W 3 5 9 H z 5 0 - A 7 .
Page 40: Removing And Installing Loopback Connectors And Terminators
Removing and Installing Loopback Connectors and Terminators To remove and install a ThinWire terminator, follow the directions in Figure 2-6. To remove and install a ThickWire loopback connector, follow the directions in Figure 2-7. To remove and install a communications loopback connector, follow the directions in Figure 2-8.
Page 41: To Remove A Thinwire Terminator
To Remove a ThinWire Terminator Twist the collar on the ThinWire T-connector as far as possible to the left. Pull the T-connector off of the system unit connector. To Install a ThinWire Terminator Press a terminator onto each unused end of the T-connector. Turn the terminator to the right until it locks into place.
Page 42: To Remove A Thickwire Loopback Connector
To Remove a ThickWire Loopback Connector Firmly grip the ThickWire loopback connector. Pull the ThickWire loopback connector away from the ThickWire connector on the system unit. To Install a ThickWire Loopback Connector Align the wide end of the loopback connector and the wide end of the ThickWire Ethernet connector.
Page 43: To Remove A Communications Loopback Connector
To Remove a Communications Loopback Connector Firmly grip the communications loopback connector. Pull the communications loopback connector away from the communications connector. To Install a Communications Loopback Connector Align the wide end of the loopback connector and the wide end of the communications connector. Firmly press the loopback connector onto the communica- tions connector.
Page 44: To Remove A Scsi Chain Terminator
To Remove a SCSI Chain Terminator Push the wire brackets away from the terminator. Pull the terminator off of the SCSI connector. To Install a SCSI Chain Terminator Firmly press the chain terminator onto the unused connector on the drive at the end of the chain. Fasten the SCSI connector wire brackets onto the SCSI terminator.
Page 45: To Remove A Communications Line Adapter
To Remove a Communications Line Adapter Loosen the two screws that hold the adapter to the communications connector. Pull the communications line adapter away from the system unit. To Install a Communications Line Adapter Firmly press the communications line adapter onto the communications connector.
Page 46: Entering Console And Operating Modes
Entering Console and Operating Modes The system operates in either of two modes: Console mode Use console mode to Run tests Display hardware conﬁgurations Set environment variables Boot the system software In console mode, the system displays the prompt >> .
Page 47: To Enter Console Mode
To Enter Console Mode Enter console mode by turning on the system power or pressing the reset button. If the system is running software, shut down the system software before you enter console mode. When you turn on the system power, the system completes a power-up self-test before displaying the console prompt.
Page 48: Using Console Command Passwords
Using Console Command Passwords You can set the system so that you can use only the boot and password commands until you enter a password. A system that requires a password before you can use all console commands displays the prompt R> until you enter the correct password. To be able to use all console commands on a system that requires a password, type passwd at the prompt R>.
Page 49: To Erase A Password You Do Not Know
To Erase a Password You Do Not Know You can erase a password by inserting a clear-nonvolatile-RAM (NVR) jumper. After you insert a clear-NVR jumper, you will need to reset all environment variables. To erase a password you do not know, Turn off the system power.
Page 50: Inserting And Removing A Clear-Nvr Jumper
Inserting and removing a clear-NVR jumper Figure 2-11 shows how to insert and remove the clear-NVR jumper. Clear NVR Clear NVR pins System module WSE2M047 Figure 2-11. Inserting and removing a clear-NVR jumper Service Operations 2–21...
Page 51 To insert the jumper, Turn off the system unit. Remove the system unit cover. Refer to ‘‘Removing and Installing the System Unit Cover’’ earlier in this chapter for directions. Locate the clear-NVR pins on the system module. The clear-NVR jumper pins are a two-pin ﬁxture. Slide the jumper entirely over the clear-NVR pins.
Page 52: Booting The System Software
Booting the System Software To boot the system, use the boot command. Booting a system can take several minutes. If the system displays the ULTRIX prompt before the prompt login: appears, press Ctrl-D to continue with the boot operation. If the boot is successful, the monitor displays the prompt login: If the system fails to boot, do the following: Use the printenv command to display the environment...
Page 53: Shutting Down The System Software
Shutting Down the System Software If the system is running ULTRIX software, shut down the system before you perform customer service. To shut down the software, type the following command at the ULTRIX prompt: /etc/shutdown -h (now | hhmm | +n) Specify the now parameter to shut down the software immediately.
Page 54: Troubleshooting Tools
Troubleshooting Tools This chapter explains the system troubleshooting tools. It explains how to Use different types of tests Set up tests for groups of selected modules Interpret test results Examine and interpret error logs Use boot error messages Use console status messages Troubleshooting Tools 3–1...
Page 55: Using Tests
Using Tests The system uses two types of tests to check system hardware operation: Power-up self-tests, which run a comprehensive test of the system hardware Subtests, which test individual modules that you choose Subtests can be individual tests or test scripts, which are groups of individual tests.
Page 56: Running Power-Up Self-Tests
Running Power-Up Self-Tests The system runs a power-up self-test when you turn on the system power. The monitor and diagnostic LEDs report any errors the power-up self-test detects. To ﬁnd the corrective action for any error codes the power-up self-test reports, refer to Chapter 4.
Page 57: Running Subtests
Running Subtests In addition to the power-up self-test, you can use subtests to troubleshoot. Subtests run individual tests or test scripts. Running Individual Tests To run an individual test, type t [-l] slot/test [arg1] [arg2] [arg3] . . . When you type an individual test command, t is the command to run a test.
Page 58: Running Test Scripts
Running Test Scripts Use the sh command to run a test script. To run a test script once and then stop, type sh script, where you replace script with the name of the test script you want to run. Then press Return. To have a test script run and keep repeating until you press Ctrl-C, include the optional -l parameter in the command.
Page 59: To Display Existing Scripts That Test An Individual Module
Entries in the other columns represent the individual test parameters, if any. The value in brackets next to each parameter is the default value for that parameter. For a detailed explanation of individual self-tests and their parameters, refer to Appendix D. To display existing scripts that test an individual module To display all the scripts that do not loop, type ls slot, where slot represents the slot number of the module for which you...
Page 60: Creating Test Scripts
Creating Test Scripts You can create test scripts that test modules under test conditions you choose. To create a test script, Type script name, where you replace name with the name that you want to give the script you are creating. Then press Return.
Page 61: Interpreting Test Error Messages
Interpreting Test Error Messages For every error that a self-test detects, an error message appears on the screen. Error messages appear in the following format: ?TFL slot/test (code: description) [module]. ?TFL indicates that an error occurred. slot represents the slot number of the module that reported the error.
Page 62: Using Error Logs
Using Error Logs The system records events and errors in the ULTRIX error logs. Use the memory error, error and status register, and system overheat error logs to troubleshoot intermittent problems. The ULTRIX error logs are not the same as the test error logs Note: that appear when you use the erl console command.
Page 63 In this display, EVENT CLASS lists the error log’s general category. Possible EVENT CLASS categories are Operational events, which are changes in system operation that are not errors Error events, which are actual errors in system operation OS EVENT TYPE describes the type of error or event recorded in the log.
Page 64: Distinguishing Event Types
Distinguishing Event Types The second line of each error log lists the code number and name of the error log event type. The following sections describe memory, error and status, and system overheat error logs. For a detailed explanation of other error logs that involve the system unit, refer to the ULTRIX documentation.
Page 65 The UNIT INFORMATION section describes the type of module that reported the error. UNIT CLASS shows that the error occurred in a memory module. UNIT TYPE lists the particular type of memory module in which the error occurred. ERROR SYNDROME describes the nature of the error. The ERROR &...
Page 66: Error And Status Register Error Logs
Error and status register error logs Error and status register error logs record nonmemory errors. This is a sample of the error log sections that are unique to error and status register error logs. ----- ERROR & STATUS REGS ----- CAUSE x80002000 EXCEPTION CODE EXTERNAL...
Page 67: System Overheat Error Messages
The ERROR & STATUS REGS section lists the error and status register contents followed by phrases explaining these values. CAUSE lists the type of event that caused the error. STATUS lists various system settings in effect when the error occurred. SP is a stack pointer that identiﬁes where the CPU contents were sent when the error occurred.
Page 68: Identifying Failed Frus
Identifying Failed FRUs This chapter explains how to Follow the troubleshooting process for this system Interpret power-up self-test error messages to identify FRUs Troubleshoot when the power-up self-test does not complete Interpret error logs to ﬁnd intermittent failures Troubleshoot when the printer, modem, or alternate terminal does not operate properly Identifying Failed FRUs 4–1...
Page 69: Troubleshooting Process
Troubleshooting Process Troubleshoot the system as follows: Make sure there is power to the system unit. If the system unit has no power, refer to ‘‘Power Supply’’ in Chapter 5 to troubleshoot. Turn on the system and check the results of the power-up self-test.
Page 70: Interpreting Test Results
Interpreting Test Results Use the error messages that appear on the monitor and on the diagnostic LEDs to identify failed FRUs. Interpreting Error Messages That Appear on the Monitor Error messages on the monitor have the form ?TFL slot/test_name (n: description) [module] slot represents the slot number of the FRU that reported the failure.
Page 71: Interpreting Test Error Messages Displayed On The Monitor
Table 4-1. Interpreting Test Error Messages Displayed on the Monitor Test Listed in the Error Message Component Tested Corrective Action Graphics module for which Refer to the TURBOchannel Maintenance the slot number appears Guide to troubleshoot. in the error message cntl SCSI controller for which Refer to Chapter 5 for directions.
Page 72 Table 4-1 (Cont.). Interpreting Test Error Messages Displayed on the Monitor Test Listed in the Error Message Component Tested Corrective Action misc/kbd Keyboard or mouse Refer to ‘‘Keyboard and Mouse’’ in misc/mouse Chapter 5 to troubleshoot. misc/pstemp Power supply Refer to ‘‘Power Supply’’ in Chapter 5 to troubleshoot.
Page 73: Troubleshooting When The Power-Up Self-Test Does Not Complete
Troubleshooting When the Power-Up Self-Test Does Not Complete If the power-up self-test does not complete, the left set of diagnostic LEDs display an error code that indicates the slot number of the FRU that caused the power-up self-test to stop. Table 4-2 lists the corrective action for each location where the test can stop.
Page 74: Using Error Logs To Troubleshoot
Using Error Logs to Troubleshoot The event type listed on the second line of the error log describes the general event that the error log recorded. Table 4-3 lists possible event type codes and their meaning. Table 4-3. Error Log Event Types Code Event Type Machine check...
Page 75: Memory Error Logs
Memory Error Logs Use these parts of the memory error log to determine the error: The number after MODULE NUM in the log’s check syndrome section is the slot number of the memory module that reported the error. The phrase after ERROR ADDR REG describes the type of error that occurred.
Page 76: Overheat Error Messages
Table 4-4. Hardware Physical Addresses Physical Address Range Indicated Hardware 00000000 to 1DFFFFFF Main memory 1E000000 to 1E3FFFFF Module in option slot 0 1E400000 to 1E7FFFFF Module in option slot 1 1E800000 to 1EBFFFFF Module in option slot 2 1EC00000 to 1EFFFFFF Reserved 1F000000 to 1F3FFFFF Reserved...
Page 77: Troubleshooting When A Printer, Modem, Or Alternate Terminal Does Not Operate Properly
Troubleshooting When a Printer, Modem, or Alternate Terminal Does Not Operate Properly If the system tests report no errors, but a printer, modem, or alternate terminal does not operate properly, run an external loopback serial line test to isolate the problem. Before you run the external loopback serial line test, make sure the following items are installed on the back of the system unit: Communications loopback connectors on both communica-...
Page 78: For Further Information
For Further Information For an explanation of troubleshooting the SCSI, Ethernet, TURBOchannel options, and the drives and monitors they support, refer to the TURBOchannel Maintenance Guide. Identifying Failed FRUs 4–11...
Page 79: Basic Hardware
Basic Hardware This chapter discusses hardware, troubleshooting procedures, and removal and installation instructions for the following FRUs: System module and chassis Memory module Keyboard Mouse Power supply Basic Hardware 5–1...
Page 80: System Module And Chassis
System Module and Chassis System Module and Chassis Hardware The system module and chassis, shown in Figure 5-1, provides basic system functions. The system module and chassis are a single unit that contains Two diagnostic system ROMs One Ethernet station address register (ESAR) chip One SCSI controller with its own diagnostic ROM One ThinWire Ethernet controller with its own diagnostic Two communications line controllers...
Page 81: Troubleshooting The System Module
Troubleshooting the System Module Table 5-1 lists the appropriate response to each system module test error message. Table 5-1. Interpreting System Module Error Messages Failed System Module Test Component Tested Corrective Action cache/ System module Replace the system module and chassis. Refer to this section for directions.
Page 82: Replacing A System Module And Chassis
Replacing a System Module and Chassis To replace a system module and chassis, transfer the removable parts from the old system module onto the new system module. The system module and chassis are one unit. Never remove Warning: a system module from the chassis. Removing the system module from the chassis destroys the system module compliance with FCC radio emission regulations.
Page 83: Removing Hardware From An Old System Module
Remove the serial number plate from the back of the system unit. Refer to Chapter 2 for directions. Check whether there are customer property identiﬁcation labels on the old system unit chassis. If the old system unit chassis has any such tags, have the customer transfer the tags to the new system unit module and chassis.
Page 84 To install parts on the new system module, Remove the system unit cover if it is on the chassis. Refer to Chapter 2 for directions. Install the ESAR chip from the old system module in the new system module. Refer to ‘‘Removing and installing an ESAR chip’’...
Page 85 B a s i c H a r d w a r e 5 – 7 a r e o n a n e w s y s t e m m o d u l e W S E 2 M 0 1 8...
Page 86: To Remove And Install An Esar Chip
To remove and install an ESAR chip Figure 5-4 shows how to remove and install an ESAR chip. To remove an ESAR chip, Turn off the system unit power and remove the system unit cover. Locate the ESAR chip. Gently pry the ESAR chip loose. To install an ESAR chip, Orient the chip as shown in Figure 5-4.
Page 87: Memory Modules
Memory Modules Memory Module Hardware The system module memory slots support up to 15 of the 8-Mbyte modules shown in Figure 5-5. Table 5-2 shows the address range assigned to each memory slot. WSE2M019 Figure 5-5. Memory module Basic Hardware 5–9...
Page 88: Memory Module Address Ranges
Table 5-2. Memory Module Address Ranges Memory Module Slot Number Memory Address Range a0000000 to a07FFFFF a0800000 to a0FFFFFF a1000000 to a17FFFFF a1800000 to a1FFFFFF a2000000 to a27FFFFF a2800000 to a2FFFFFF a3000000 to a37FFFFF a3800000 to a3FFFFFF a4000000 to a47FFFFF a4800000 to a4FFFFFF a5000000 to a57FFFFF a5800000 to a5FFFFFF...
Page 89: Troubleshooting The Memory Modules
Troubleshooting the Memory Modules If a self-test reports an error code that includes mem, the problem is in a memory module or the system module. The additional information statement in the error message lists the slot number of the memory module that reported the problem. Before replacing either module, make sure the memory modules are ﬁrmly seated on the system module.
Page 90 RAM board test error messages use the format ?TFL 7/mem/code: board (x: description). The string ?TFL 7/mem indicates that the RAM board test failed. code is a number that indicates which part of the RAM board test failed. board indicates the memory module that reported the problem.
Page 91: Removing And Installing A Memory Module
Removing and Installing a Memory Module Figure 5-6 shows how to remove and install a memory module. Captive screw Memory module Captive screw Memory module slot numbers WSE2M020 Figure 5-6. Removing and installing a memory module Basic Hardware 5–13...
Page 92 To remove a memory module, Turn off the workstation. Remove the system unit cover. Refer to ‘‘Removing and Installing the System Unit Cover’’ in Chapter 2 for directions. Loosen the two captive screws that hold the memory module retaining bar. Then remove the bar. Grip each end of the memory module and pull the module out of its connector.
Page 93: Keyboard And Mouse
Keyboard and Mouse Keyboard and Mouse Hardware The system uses a LK201 keyboard and VSXXX-AA mouse. The keyboard and mouse each connect to the end of a keyboard- mouse cable that connects to the back of the system unit, as shown in Figure 5-7.
Page 94: Troubleshooting The Keyboard And Mouse
Troubleshooting the Keyboard and Mouse If the system reports an error message that includes misc/kbd or misc/mouse, the problem is in the keyboard, mouse, keyboard-mouse cable, or system module. Troubleshoot these items as follows: Make sure that the keyboard and mouse are attached correctly to the keyboard-mouse cable and that the keyboard-mouse cable is attached correctly to the system unit.
Page 95: Keyboard Test
Keyboard test The keyboard test checks the keyboard. To run the keyboard test, type t 7/misc/kbd and press Return. This is a sample keyboard test error message: ?TFL 7/misc/kbd (missing?) The message misc/kbd after the slot number indicates that the keyboard test failed.
Page 96: Removing And Installing The Keyboard And Mouse
Removing and Installing the Keyboard and Mouse Figure 5-8 shows how to remove and install a keyboard and mouse. WSE2M023 Figure 5-8. Removing and installing a keyboard and mouse 5–18 Basic Hardware...
Page 97: To Remove The Keyboard And Mouse And Their Cables
To remove the keyboard and mouse and their cables To remove the mouse, pull the end of the mouse cable out of its connector. To remove the keyboard, pinch the tab on the end of the keyboard cable. Then pull the cable out of its connector. To detach the keyboard-mouse cable from the back of the system unit, loosen the connector holding screws.
Page 98: Power Supply
Power Supply Power Supply Hardware The power supply, shown in Figure 5-9, provides 244 watts of DC power to the system unit. The back of the power supply has a power connector and monitor-to-system-unit connector. An LED on the front panel glows green when the power supply is operating properly.
Page 99: Troubleshooting The Power Supply
Troubleshooting the Power Supply Troubleshooting if the system unit has no power If the system unit has no power, Check the power supply LED. If the LED does not glow green, make sure the power is on and the power cord is connected to the back of the system unit and to a power outlet.
Page 100 p o w e r c o r d c o n n e c t i o n s W S E 2 M 0 5 1...
Page 101: Troubleshooting If The System Unit Overheats
Troubleshooting if the system unit overheats If the system reports the message 7/misc/pstemp (system is *HOT*!), troubleshoot the power supply fans. Remove the system unit cover. Turn on the system power. Check whether the power supply fans rotate when the system unit power is on.
Page 102 p o w e r s u p p l y f a n a s s e m b l y c o n n e c t i o n W S E 2 M 0 4 5...
Page 103: Removing And Installing The Power Supply
Removing and Installing the Power Supply Figure 5-12 shows how to remove and install the power supply. On/off switch System unit power cord Power supply Back view Captive allen screws (2) System module power cords Front view WSE2M025 Figure 5-12. Removing and installing the power supply Basic Hardware 5–25...
Page 104: For Further Information
To remove the power supply, Turn off the workstation. Disconnect the power cord. Remove the system unit cover and front cover plate. Refer to Chapter 2 for directions. Disconnect the system module power cords. Loosen the two captive Allen screws that hold the power supply.
Page 105: A Equipment Speciﬁcations
Equipment Speciﬁcations This appendix lists the physical speciﬁcations, operating conditions, and nonoperating conditions for the following components: System unit LK201 keyboard VSXXX-AA mouse Equipment Speciﬁcations A–1...
Page 106: System Unit Description
Table A-1. System Unit Description Weight Height Width Depth System unit 12.7 kg 92 mm 509.5 mm 434.8 mm (28 lb) (3.62 in) (20.06 in) (17.12 in) Table A-2. System Unit Speciﬁcations Input voltage Adjust to 100 to 120 Vac to 220-240 Vac Input current 5 amps at 100 to 120 Vac 2.4 amps at 220 to 240 Vac...
Page 107: Lk201 Keyboard Description
Table A-5. LK201 Keyboard Description Weight Height Width Depth Keyboard 2 kg 51 mm 533 mm 171 mm (4.5 lb) (2 in) (21 in) (6.75 in) Including attachable feet Table A-6. LK201 Keyboard Speciﬁcations Number of keys Number of indicators 4 status LEDs Language variations Diagnostics...
Page 108: Lk201 Keyboard Nonoperating Conditions
Table A-8. LK201 Keyboard Nonoperating Conditions Temperature range - 40° C to 66° C (- 40° F to 151° F) Relative humidity 10% to 95%, noncondensing Maximum wet-bulb temperature 46° C (115° F), packaged Minimum dew-point temperature 2° C (36° F) Altitude 4,900 m (16,000 ft) at 36°...
Page 109: Vsxxx-Aa Mouse Description
Table A-9. VSXXX-AA Mouse Description Weight Height Diameter Mouse 170 g 40 mm 88 mm (0.37 lb) (1.57 in) (3.47 in) Table A-10. VSXXX-AA Mouse Speciﬁcations Baud rate 4800 Cable length 1.5 m (5 ft), shielded, 6 conductors and terminals in a 7-pin micro-DIN-type connector (male) Resolution 79 counts (200 counts/in)
Page 110: Vsxxx-Aa Mouse Nonoperating Conditions
Table A-12. VSXXX-AA Mouse Nonoperating Conditions Temperature range - 40° C to 66° C (- 40° F to 151° F) Relative humidity 5% to 95% Maximum wet-bulb temperature 46° C (115° F), packaged Minimum dew-point temperature 2° (36° F) Altitude 4,900 m (16,000 ft) at 36°...
Page 111: B Recommended Spares List
Recommended Spares List Tables B-1 through Table B-6 in this appendix contain the part numbers for DECstation/DECsystem 5000 Model 200 loopback connectors, plugs, test media, major FRUs, basic components, cords, cables, connectors, and related documentation. Item numbers in Table B-2 correspond to item numbers shown in Figure B-1.
Page 112: Decstation 5000 Unit Assembly
Figure B-1. DECstation 5000 Unit Assembly B–2 Recommended Spares List...
Page 113: System Module And Chassis
Table B-2. Major FRUs Item Number Description Part Number System module and chassis 70-26722-02 Power supply assembly 30-32506-01 Memory module, 8Mb MS02-AA System unit cover 70-27056-01 Front cover plate 70-27053-01 Table B-3. Basic Components Item Order Number VR262, 19-inch monochrome monitor, 120 volts VR262-AA VR262, 19-inch monochrome monitor, 240 volts VR262-A3...
Page 114: Cords, Cables, And Connectors
Table B-3 (Cont.). Basic Components Item Order Number RZ57 hard disk drive, 1.2 Gbytes RZ57-E - RZ57 hard disk drive HDA and frame assembly 29-28158-01 - RZ57 hard disk drive PCB 29-28159-01 RRD40 optical compact disc drive, 600 Mbytes RRD40-FA TK50Z tape drive, 95 Mbytes, 120 volts TK50Z-GA TK50Z tape drive, 95 Mbytes, 240 volts...
Page 115: Software Documentation
Documentation Overview for RISC Processors AA-MM05A-TE Table B-6. Hardware Documentation Item Order Number DECstation 5000 User Documentation Kit EK-384AA-DK DECstation 5000 Model 200 Installation Guide EK-365AA-IN DECstation 5000 Model 200 Operator’s Guide EK-366AA-OG DECstation 5000 Model 200 Workstation Reference EK-367AA-IC Card...
Page 116: Console Commands
Console Commands This appendix explains The rules to follow when you type console commands Terms commonly used in this discussion of console commands The command format and purpose of each console command Possible console command error messages Console Commands C–1...
Page 117: Entering Console Commands
Entering Console Commands This section describes the conventions to follow when you enter console commands. Rules for Entering Console Commands You can use console commands when the system monitor displays the prompt >> or R>. When the system displays the prompt R>, you can use only the boot and passwd commands until you enter the console command password.
Page 118: Conventions Used In This Chapter
Conventions Used in This Chapter Letters in boldface type like this are to be typed exactly as they appear. Letters in italic type like this are variables that you replace with actual values. Arguments enclosed in square brackets ([ ]) are optional. Ellipses (...) follow an argument that can be repeated.
Page 119: Console Command Reference
Console Command Reference This section describes console commands used by the following hardware: System module Memory modules Ethernet controllers SCSI controllers Color frame-buffer graphics modules 2D graphics accelerator modules 3D graphics modules Console commands in this appendix appear in the same order as they appear in the system console command Help menu.
Page 120: Console Command Format Summary
Console Command Format Summary Here are the console commands and their formats displayed in the Help menu that appears when you enter ?: CMD: boot [[-z #] [-n] #/path [ARG...]] cat SCRPT cnfg [#] d [-bhw] [-S #] RNG val e [-bhwcdoux] [-S #] RNG erl [-c] go [ADR]...
Page 121: Console Command Functions
Table C-1 lists each console command and its function. Table C-1. Console Command Functions Commands Function Displays a list of console commands and formats. boot Boots the system. Displays the contents of a script. cnfg Displays system conﬁguration information. Deposits data into memory. Examines memory contents.
Page 122: Command
? Command Use the ? command to display a list of available console commands and their formats. The ? command format is ? [cmd] When you type the ? command, To display the format for all available console commands, omit the optional cmd parameter. To display the format for a single command, replace the optional cmd parameter with the name of the test for which you want a command format display.
Page 123: Important Information About Typing The Boot Command
To boot from a drive, the ﬁle speciﬁcation form is slot/(rz | tz)drive/ ﬁle. When you type this ﬁle speciﬁcation, use the (rz | tz) parameter to specify the type of drive that performs the boot operation. Specify rz to boot from a hard disk or compact disc drive.
Page 124: Cat Command
cat Command Use the cat command to display the contents of a script or other ﬁle. The cat command format is cat slot/script When you type the cat command, Replace slot with the slot number of the module that has the contents you want to display.
Page 125: Cnfg Command
cnfg Command Use the cnfg command to display hardware conﬁgurations. The cnfg command format is cnfg [slot] To display a general system conﬁguration, type the cnfg command without the slot parameter. To display a detailed conﬁguration for an individual module, replace the optional parameter slot with the slot number of the module for which you want a conﬁguration display.
Page 126 The rightmost column lists additional information about each module. The meaning of each message depends on the type of module being described. For the system module and memory modules, the additional information lists the amount of memory on the system. For Ethernet controllers, the additional information lists the Ethernet station address.
Page 127: Base System Conﬁguration Displays
Base system conﬁguration displays To obtain a base system conﬁguration display, type cnfg 7 and press Return. This is a sample conﬁguration display for the base system conﬁguration, which is in slot 7. KN02-AA T5.2a TCF0 ( 24 MB) mem( 0): a0000000:a07fffff ( 8 MB) mem( 1): a0800000:a0ffffff ( 8 MB)
Page 128: Scsi Controller Displays
PMAZ-AA T5.2a TCF0 (SCSI = 7) ---------------------------------------------------- SCSI DEV ===== ================= =========== ======= ======== RZ55 (C) DEC 0700 RZ56 (C) DEC 0200 RRD40 (c) DEC 0700 CD-ROM In the SCSI conﬁguration display, the ﬁrst line has the same meaning as the SCSI description in the general system conﬁguration display.
Page 129: Color Frame-Buffer Graphics Module Conﬁguration Displays
REV shows the revision number for the drive. SCSI DEV also describes the drive type. DIR, which represents a direct access drive, appears in entries for hard disk drives. SEQ, which represents a sequential access drive, appears in entries for tape drives. CD-ROM appears in entries for optical compact disc drives.
Page 130: 2D Graphics Accelerator Module Conﬁguration Displays
PMAG-DA is the part identiﬁer for low and mid 3D graphics modules. High 3D graphics module displays list PMAG-FA as the part identiﬁer. DEC is the module manufacturer. The column third from the right lists the ﬁrmware version in each module ROM.
Page 131: Command
The rightmost phrase indicates the 3D graphics module type and how many VSIMMs and z-buffer modules are on the base graphics module. The ﬁrst part of the phrase identiﬁes the type of graphics module in the system. The value DA: PXG indicates that the module is a low 3D graphics module.
Page 132: Command
To deposit a number of values across a range of addresses, replace rng with the address range. Use the form address_low:address_high to deﬁne the range. When you enter the address range, replace address_low with the starting address for storing values and replace address_high with the ending address for storing values.
Page 133 Include the optional -S count parameter to have the command repeatedly fetch the value but display the value only once. When you type this parameter, replace count with the number of times that you want to fetch the value. Use the rng parameter to specify the range of addresses you want to examine.
Page 134: Erl Command
erl Command Use the erl command to display or clear the log of the ﬁrst several errors that occurred since the most recent power-up or reset. The erl command format is erl [-c] To display the current error message log, use the erl command without the -c option.
Page 135: Init Command
init Command Use the init command to initialize module hardware. The init command format is init [slot] [- m] To initialize the entire system, include no additional arguments the init command. To initialize an individual module, replace the optional slot parameter with the slot number of the module that you want to initialize.
Page 136: Printenv Command
To clear an existing password, include the -c parameter when you type the passwd command. First use the passwd command to enter the existing password. After the console prompt >> appears, type passwd -c and press Return. The system then removes the password requirement. To set a new password, include the -s parameter.
Page 137: Setenv Command
After you press Return, type the commands that you want to include in the script. Press Return after each command that you type. When you ﬁnish typing the commands that you are including, enter Ctrl-d or press Return twice to complete the script.
Page 138: Environment Variables In The Environment Variable Display
Table C-2. Environment Variables in the Environment Variable Display Environment Variable Description boot Sets the default boot path. console Selects the system console. - If you set the console to s, the system uses a terminal connected to the printer connector as the console. - If you set console to any value other than s, the system automatically conﬁgures the console.
Page 139: Sh Command
sh Command Use the sh command to run a script. The sh command format is sh [-b] [-e] [-l] [-v] [-s] [slot/script] [arg...]) When you type the sh command, Include the optional -b parameter to run a script. This runs the script directly, instead of by a subshell.
Page 140: Command
t Command Use the t command to run individual tests. The t command format is t [-l] slot/test [arg...]) When you type the t command, Include the optional -l parameter to have the test loop until you press Ctrl-c or reset the system. Replace slot with the slot number of the speciﬁc module that you want to test.
Page 141: Console Command Error Messages
Console Command Error Messages Table C-3 lists the error messages that the console commands can return. Table C-3. Console Command Error Messages Error Message Meaning ?IO:slot/device An I/O device reported an error. slot represents the I/O device slot number. device represents an additional message about the error.
Page 142: D Test Commands And Messages
Test Commands and Messages This appendix describes commands and messages for the following tests: System module tests Memory module tests Initial power-up tests Test Commands and Messages D–1...
Page 143: Locating Individual Tests In This Appendix
Locating Individual Tests in This Appendix This appendix groups together individual tests for each module. The individual tests in each group are listed in alphabetical order by test command. Table D-1 lists the individual tests for each module. Table D-1. Individual Tests and Utilities for Each Module Module Tested Individual Test Test Command...
Page 144 Table D-1 (Cont.). Individual Tests and Utilities for Each Module Module Tested Individual Test Test Command Nonvolatile RAM (NVR) test 7/rtc/nvr [pattern] Real-time clock period test 7/rtc/period Real-time clock register test 7/rtc/regs Real-time test 7/rtc/time Translation lookaside buffer (TLB) 7/tlb/prb probe test Translation lookaside buffer (TLB) 7/tlb/reg [pattern]...
Page 145: System Module Tests
System Module Tests The following entries explain the commands, parameters, and error codes for each individual system module test. Cache Data Test The cache data test writes data patterns to the cache and then reads them. To run the cache data test, type t 7/cache/data [cache] [address] and press Return.
Page 146: D-2 Cache Data Test Error Messages
Table D-2. Cache Data Test Error Messages Error Information Description (address=xxxxxxxx, sb yyyyyyyy) Error occurred writing data pattern to cache RAM. The address value is the actual value at a given address, followed by the correct value. (2 ) Cache parity error occurred while test was reading ﬂoating 1.
Page 147: Cache Isolate Test
Cache Isolate Test The cache isolate test isolates data patterns to the cache and then reads and writes them. To run the cache isolate test, type t 7/cache/isol [cache] and press Return. When you type the cache isolate test command, replace cache with a value that speciﬁes the cache you want to test.
Page 148: Cache Reload Test
Table D-3 (Cont.). Cache Isolate Test Error Codes Error Code Description (12 ) Reading data address pattern returned a miscompare error. Cache Reload Test The cache reload test uses rotating-parity data patterns to perform a read and write operation on the cache. To run the cache reload test, type t 7/cache/reload [cache] [address] and press Return.
Page 149: Cache Segment Test
Table D-4 describes error descriptions used in cache reload test error messages. Table D-4. Cache Reload Test Error Descriptions Error Description Meaning (PE address= xxxxxxxx, sb Unexpected parity error occurred. The yyyyyyyy) address value is the actual value at a given address, followed by the correct value.
Page 150: Cache Segment Test Error Codes And Descriptions
Table D-5 describes error codes and descriptions found in cache segment test error messages. Table D-5. Cache Segment Test Error Codes and Descriptions Error Code and Description Meaning (1: address= xxxxxxxx, sb Error occurred when the system tried yyyyyyyy) to read the cache contents. The address parameter is the actual value at a given address, followed by the correct value.
Page 151: Serial Line Silo Alarm Test
Serial Line Silo Alarm Test The serial line silo alarm test checks the ability of the serial line controller to generate a silo alarm interrupt. To run this test, type t 7/dz/alrm [loopback] [line] and press Return. When you type the serial line silo alarm test, Replace loopback with a value that speciﬁes the type of test you want to run.
Page 152: Modem And Printer Test
Modem and Printer Test The modem and printer test checks the ability of the serial line controller to interface with a modem, printer, or alternate terminal connected to a communications line. To run the modem and printer test, type t 7/dz/modem [port] [cts-lbk] and press Return.
Page 153: Serial Line Silo Overﬂow Test
Serial Line Silo Overﬂow Test The serial line silo overﬂow test checks the ability of the serial line controller to signal a silo overﬂow. To run this test, type t 7/dz/ovrﬂw and press Return. When you type the serial line silo overﬂow test command, never specify the intl or extl parameter that appears in the test command format display.
Page 154: Serial Line Silo Overﬂow Test Error Descriptions
Table D-8. Serial Line Silo Overﬂow Test Error Descriptions Error Description Meaning (line N: timeout: no trdy) Timeout occurred while waiting for transmit ready (trdy) response. N represents the number of the line on which the timeout occurred. (line N check: CSR=xxxx, sb Error occurred while checking for correct yyyy) line in serial line current status register...
Page 155: Serial Line Single Silo Test
Serial Line Single Silo Test The serial line single silo test checks the ability of the serial line controller to ﬁll and empty the silo. To run the serial line single silo test, type t 7/dz/silo-1 [loopback] [line] and press Return.
Page 156: Serial Line Single Silo Test Error Descriptions
Table D-9. Serial Line Single Silo Test Error Descriptions Error Description Meaning (timeout: no trdy) Timeout occurred while waiting for transmit ready (trdy) response. (line: CSR=xxxx, sb xxxx) Error occurred in a serial line. CSR lists the value in the serial line current status register (CSR), followed by the correct value.
Page 157: Serial Line Mixed Silo Test
Serial Line Mixed Silo Test The serial line mixed silo test checks the ability of the serial line controller to ﬁll and empty the silo using multiple lines. To run the serial line mixed silo test, type t 7/dz/silo-m [loopback] and press Return.
Page 158: Serial Line Mixed Silo Test Error Descriptions
Table D-10. Serial Line Mixed Silo Test Error Descriptions Error Description Meaning (timeout: line N: no trdy) Timeout occurred while waiting for transmit ready. N represents the number of the line that reported the timeout. (line N: CSR=xxxx, sb yyyy) Error occurred in a serial line.
Page 159: Serial Line Transmit And Receive Test
Serial Line Transmit and Receive Test The serial line transmit and receive test checks the ability of the serial line controller to receive and transmit characters. To run the serial line transmit and receive test, type t 7/dz/tx-rx [loopback] [line] and press Return. When you type the serial line transmit and receive test command, Replace the optional loopback parameter with a value that...
Page 160: Serial Line Transmit And Receive Test Error Descriptions
Table D-11. Serial Line Transmit and Receive Test Error Descriptions Error Description Meaning (TCR= xxxx, sb yyyy) The value in the transmit control register (TCR) is incorrect. The TCR value is the actual value in the TCR register, followed by what the value should be. (tx: CSR=xxxx, sb yyyy) Error occurred during transmission operation.
Page 161: Error-Correcting Code (Ecc) Generate Test
Error-Correcting Code (ECC) Generate Test The error-correcting code (ECC) generate test performs a write and read operation in memory and then compares the resulting ECC with the computed value. To run the ECC generate test, type t 7/ecc/gen [address] and press Return. When you type the ECC generate test command, replace the optional address parameter with the speciﬁc address at which you want to perform the read and write operation.
Page 162: Floating-Point Unit (Fpu) Test
Floating-Point Unit (FPU) Test The ﬂoating-point unit (FPU) test uses the FPU to perform simple arithmetic and compares the result to known values. To run the FPU test, type t 7/fpu and press Return. FPU test error messages FPU test error messages have the form ?TFL: 7/(code) ?TFL 7/fpu indicates that the FPU test reported an error.
Page 163: Fpu Test Error Codes
Table D-13. FPU Test Error Codes Error Code Meaning Values did not match. Value should be 00000000. Values did not match. Value should be 55555555. Values did not match. Value should be AAAAAAAA. Values did not match. Value should be FFFFFFFF. Least-signiﬁcant bit failed when the system was converting doubleword to word (CVT D.
Page 164: Ram Select Lines Test
RAM Select Lines Test The RAM select lines test checks for RAM select line faults during RAM register selection. To run the RAM select lines test, type t 7/mem/select and press Return. RAM select lines test error messages The only RAM select test error message is ?TFL: 7/mem/select (1: address= xxxxxxxx, sb yyyyyyyy).
Page 165: Keyboard Test
Keyboard Test The keyboard test checks the keyboard and its serial line controller on the system module. To run the keyboard test, type t 7/misc/kbd [loopback] and press Return. When you type the keyboard test command, replace the optional loopback parameter with a value that speciﬁes whether the test should look for a keyboard loopback.
Page 166: Mouse Test
Mouse Test The mouse test checks the mouse and its serial line controller on the system module. To run the mouse test, type t 7/misc/mouse [loopback] and press Return. When you type the mouse test command, use the optional loopback parameter to specify whether the test should also search for a mouse or mouse loopback connector.
Page 167: Ram Refresh Test
RAM Refresh Test The RAM refresh test checks whether the RAM refresh process is working. To run the RAM refresh test, type t 7/misc/rfrsh and press Return. RAM refresh test error messages RAM refresh test error messages have the form ?TFL: 7/misc/rfrsh [(RTC)] The message ?TFL 7/misc/rfrsh indicates that the RAM refresh test reported an error.
Page 168: Partial Write Test
Partial Write Test The partial write test writes to a speciﬁc memory address and then checks whether the written values are correct. To run the partial write test, type t 7/misc/wbpart and press Return. Partial write test error messages Partial write test error messages have the form ?TFL: 7/misc/wbpart (code) ?TFL 7/misc/wbpart indicates that the partial write test reported an error.
Page 169: Nonvolatile Ram (Nvr) Test
Nonvolatile RAM (NVR) test The nonvolatile RAM (NVR) test checks the system module nonvolatile RAM. To run the NVR test, type t 7/rtc/nvr [pattern] and press Return. When you type the NVR test command, replace the optional pattern parameter with a speciﬁc pattern that you want to use in the test.
Page 170: Real-Time Clock (Rtc) Period Test
Real-Time Clock (RTC) Period Test The real-time clock (RTC) period test checks the RTC periodic interrupt operation. To run the RTC period test, type t 7/rtc/period and press Return. RTC period test error messages RTC period test error messages have the form ?TFL: 7rtc/period/ (code) ?TFL 7/rtc/period indicates that the RTC period test reported an error.
Page 171: Real-Time Clock Register Test
Real-Time Clock Register Test The real-time clock register test checks the real-time clock (RTC) registers. To run the real-time clock register test, type t 7/rtc/regs and press Return. Real-time clock register test error messages Real-time clock register test error messages have the form ?TFL: 7/rtc/regs (code description) ?TFL 7/rtc/regs indicates that the real-time clock register test reported an error.
Page 172: Real-Time Test
Real-Time Test The real-time test checks times generated by the real-time clock against hard-coded time values. To run the real-time test, type t 7/rtc/time and press Return. Real-time test error codes Real-time test error messages have the form ?TFL: 7/rtc/time (code) ?TFL 7/rtc/real indicates that the real time test reported an error.
Page 173: Translation Lookaside Buffer (Tlb) Probe Test
Translation Lookaside Buffer (TLB) Probe Test The TLB probe test checks whether all TLB registers respond to an address match operation. To run the TLB probe test, type t 7/tlb/prb and press Return. TLB probe test error messages The only TLB probe test error message is ?TFL: 7/tlb/prb (match(0,N)= xxxxxxxx, sb yyyyyyyy), which indicates that the value at address 0 did not match the value at the address represented by N.
Page 174: Translation Lookaside Buffer (Tlb) Registers Test
Translation Lookaside Buffer (TLB) Registers Test The translation lookaside buffer (TLB) registers test performs a read and write operation on the TLB. To run the TLB registers test, type t 7/tlb/reg [pattern] and press Return. TLB registers test and error messages TLB registers test error messages have the form ?TFL: 7/tlbregs/ (description) ?TFL 7/tlb/regs indicates that the test reported an error.
Page 175: Memory Module Tests
Memory Module Tests The following entries explain the commands and error codes for each memory module self-test. RAM Board Test The RAM board test performs a full pattern test on an entire memory module. To run the RAM board test, type t 7/mem [board] [threshold] [pattern] and press Return.
Page 176: Ram Board Test Error Codes And Descriptions
Table D-22. RAM Board Test Error Codes and Descriptions Error Code and Description Meaning (1: board x: too many More than the allowable number of MBEs: y) multiple-bit errors occurred. The x represents the slot number of the memory module that failed the test. The y represents the number of MBEs that the memory module reported.
Page 177: Floating 1/0 Memory Test
Floating 1/0 Memory Test The ﬂoating 1/0 memory test writes ﬂoating 1s across one location in RAM. To run the ﬂoating 1/0 memory test, type t 7/mem/ﬂoat10 [address] and press Return. When you type the ﬂoating 1/0 memory test, replace the optional address parameter with a speciﬁc address at which you want to start writing 1s.
Page 178: Power-Up Led Displays
Power-Up LED Displays The system completes a series of tests and other functions whenever you turn on the system power. If the system halts at one of these functions, the diagnostic LEDs display a code that indicates where in the power-up sequence the system halted. Table D-23 lists the hexadecimal equivalent of the power-up LED displays and what they indicate about the power-up sequence.
Page 179: Console Commands
Console Commands Generated by Version PDE3 ROM Chips This appendix explains the use and format of the console commands generated by Version PDE3 ROM chips. It tells you how to Follow console command conventions Display information about system hardware Set environment variables Enable and disable serial line connections Write data into memory Examine memory contents...
Page 180: Information About Using Console Commands
Information About Using Console Commands Rules for Typing Console Commands Use console commands when the system monitor displays the prompt >>. When typing console commands, follow these rules: Type uppercase and lowercase letters exactly as they appear in command lines. The system recognizes uppercase and lowercase letters as different input.
Page 181: Conventions Used In This Appendix
The following key combinations have an immediate effect in console mode: Ctrl-S freezes the screen display. Ctrl-Q releases a frozen screen display. Ctrl-C aborts a command. Ctrl-U erases a partially typed command line. Conventions Used in This Appendix Letters in bold face type like this are to be typed exactly as they appear.
Page 182: E-1 Console Commands
Table E-1 is an alphabetical list of the valid console commands. Table E-1. Console Commands Command boot Boots the operating system. cnfg Displays the system’s hardware conﬁgurations. ctrs Displays network counters. Deposits data at a given address. disable Disables a device. dump Dumps memory to the screen.
Page 183: Displaying Information About System Hardware
Displaying Information About System Hardware To see what hardware the system has and how it is conﬁgured, use the cnfg command. To see which devices are on a SCSI bus, use the scsi prb command. cnfg Command The cnfg command displays the system’s current hardware conﬁgurations.
Page 184 In this display Bsys refers to the system and memory modules. Entries under the Bsys heading mean the following: Mem lists the amount of system memory. RS232 is the system’s communications protocol. Optn# 5 is the SCSI controller on the system module. Listings under Optn# 5 show any devices on this SCSI controller’s bus.
Page 185: Scsi, Ethernet, And Graphics Conﬁgurations
SCSI ID addresses 1 and 2: Optn# 2 - [PMAZ-AA /0x5419876/0x0] SCSI: (szn/ncr53c94 chip) [x.-000] 2: rz(1,2) -- Pid="RZ55’ (C)DEC", Vid=DEC, Rev"0700" 1: rz(1,1) -- Pid="RZ55’ (C)DEC", Vid=DEC, Rev"0700" The second line shows the following: The leftmost term indicates the module’s type.
Page 186: Symbols Used In Optional Module Conﬁguration Displays
Following entries describe the drive itself. Table E-2 explains entries that may appear in these lines. This is a sample display for a graphics module in option slot 0: Optn# 0 - [PMAG-BA /0x1010/0x0] Vid: 8-bit color frame buffer (crta/crta) [x.-000] The second line indicates the type and version of the graphics module.
Page 187: System And Memory Module Conﬁgurations
#1 - [Pdev] #2 - #3 - Optn# 5 - [PMAZ-AA /0x5419876/0x0] SCSI: 2: rz(0,2) -- Pid = RZ55 (C)DEC, Vid=DEC, Rev=0700 1: rz(0,1) -- Pid = RZ55 (C)DEC, Vid=DEC, Rev=0700 Optn# 6 - Net: 00-00-00-00-00-00 (mop/LANCE chip) [xx.y-00] Net: 08-00-2B-0C-E3-EA (mop/LANCE chip) [x.-00] In this display, Bsys refers to the system and memory modules.
Page 188: Driver Conﬁgurations
Driver conﬁgurations To display the system’s drivers and their hierarchies, type cnfg d and press Return. A display similar to the following appears on the monitor: mop: [boot server/se ethernet] se( 0) Optn# 6 [LANCE chip/LANCE Ethernet driver] [scsi disk] szn( 0) Optn# 5 [ncr53c94 chip/NCR53C94 SCSI Port driver] [scsi tape] szn( 0) Optn# 5 [ncr53c94 chip/NCR53C94 SCSI Port driver]...
Page 189: Scsi Prb Command
The monitor’s scsi prb display looks similar to this: 6: * 5: Pid="", Vid=", Rev="" 0x0001d001<PDT=Tape,PQ=0,DTQ=50,RMB,ANSI=1,RDF=0> 0x00000000 3: Pid="RZ56" (C) DEC", Vid="DEC", Rev="0102" 0x01010000<PDT=Disk,PQ=0,DTQ=0,ANSI=1,RDF=1> 0x1000001f<Alen=31,Sync> In this display, the numbers in the left column are the device’s SCSI addresses. An asterisk appears after the SCSI controller’s address.
Page 190: Setting Environment Variables
Setting Environment Variables Environment variables set system operating conditions. Console commands allow you to display, set and remove environment variables. To display existing environment variables, use the printenv command. To set environment variables, use the setenv command. To remove environment variables, use the unsetenv command.
Page 191: Environment Variables Set By The User
Table E-3. Environment Variables Set by the User Environment Variable Description baud2 Baud rate of the right communications line. The default value is 1200. baud3 Baud rate of the left communications line. The default value is 4800. bootpath Default bootpath speciﬁcation. testaction Test script to run when the system power turns on.
Page 192 Table E-3 (Cont.). Environment Variables Set by the User Environment Variable Description console One or more devices to use as the console terminal. If more than one device is designated as a console, the system accepts input from and sends output to all designated devices.
Page 193: Printenv Command
Table E-4. Environment Variables Set by the System Environment Variable Description bitmap Address in memory of a bitmap of good and bad memory pages. You cannot change this variable by using the setenv command. bitmaplen The bitmap’s length in words. You cannot change this variable by using the setenv command.
Page 194: Setenv Command
setenv Command To set an environment variable, use the setenv command. Type setenv evar val, and press Return. When you use this command, Replace evar with the environment variable you want to set. Replace val with the new value you want to give this environment variable.
Page 195: Writing Data Into Memory
Writing Data into Memory To write a byte, halfword, or word at a speciﬁc memory address, use the d (deposit) command. To write a speciﬁc value to a range of memory, use the ﬁll command. d (deposit) Command The d (deposit) command writes a single byte, halfword, or word to a speciﬁed address.
Page 196: Fill Command
ﬁll Command Use the ﬁll command to write a speciﬁc value to a range of memory. To use the ﬁll command, type ﬁll [- | -h | w] [-v\bold)val] rng and press Return. include the optional ﬁrst parameter to specify data size. Word is the default value.
Page 197: Setting Serial Line Connections
Setting Serial Line Connections To remove a terminal from the possible working consoles, use the disable command. To enable a terminal to work as a console, use the enable command. disable Command The disable command disables a working console. It also removes the console from the recognized console terminals in the environment variables list.
Page 198: Enable Command
Enable Command The enable command enables a working console. It also adds the console to the recognized console terminals in the environment variables list. To use the enable command, type enable [tty(x )] and press Return. Include the optional tty(x) parameter to enable a speciﬁc console.
Page 199: Examining Memory Contents
Examining Memory Contents To obtain a formatted display of memory contents, use the dump command. To see the contents at a speciﬁc address, use the examine command. To display the network counters, use the ctrs command. dump Command The dump command gives a formatted display of the contents of memory.
Page 200 Include the second optional parameter to specify the display format. Specify -o to display memory in octal format. Specify -d to display memory in decimal format. Specify -u to display memory in unsigned decimal format. Specify -x to display memory in hexadecimal format. Specify -c to display memory in ASCII format.
Page 201: E (Examine) Command
This command uses hexadecimal format to display the ﬁrst 15 bytes in memory to the screen. The dump display shows rows of address contents. The leftmost column gives the address of the ﬁrst ﬁeld in each row. e (examine) Command The e (examine) command displays the byte, halfword, or word at a speciﬁc address.
Page 202: Ctrs Command
ctrs Command Use the ctrs command to display all the network counters. To use the ctrs command, type ctrs and press Return. A display of network counters then appears on the screen. A typical display looks like this: 15905 : seconds since zeroed 0 : bytes received 0 : bytes sent 0 : frames received...
Page 203: Displaying Console Command Formats
Displaying Console Command Formats To display a list of console commands and their format, use the help command or the ? command. To display a list of test commands and their format, use the t ? command. help Command To use the help command, type help [cmd] and press Return. Include the optional cmd parameter to display the format for a single command.
Page 204: T ? Command
t ? Command The t ? command displays a list of test commands and their format. To use the t ? command, type t ? test and press Return. Include the optional test parameter to display the format of a speciﬁc test.
Page 205: Booting The System Software
Booting the System Software Use the boot command to boot the system software. Type boot [ -fﬁle] [-n] [arg...] and press Return. The boot command loads the ﬁle that contains the operating system. To boot a speciﬁc ﬁle, replace the optional -f ﬁle parameter with the name of the ﬁle you want to use.
Page 206 Include the optional -n parameter to load but not execute a speciﬁc ﬁle. The optional arg parameter contains any information to be passed to the booted image. Examples: >> boot -f rz(0,0,0)vmunix This command boots the ﬁle vmunix, located in the A partition of the ﬁrst hard disk (unit number 0), using controller 0.
Page 207: F Test Commands And Messages Produced By Version Pde3 Rom Chips
Test Commands and Messages Produced by Version PDE3 ROM Chips This appendix describes test commands and messages that the old PDE3 ROM chips generate for the following: System module tests Memory module tests SCSI controller tests Ethernet controller tests Graphics module tests Initial power-up tests Test Commands and Messages Produced by Version PDE3 ROM Chips F–1...
Page 208: System Module Tests
System Module Tests The following entries explain the commands, parameters, and error codes for each individual system module test. FPU Test This test uses the FPU to perform simple arithmetic. To run the FPU test, type t f21 and press Return. FPU test error messages In FPU test error messages, the parameter P1 indicates the value the test last read from the coprocessor.
Page 209: Fpu Error Codes
Table F-1. FPU Error Codes Error Code Meaning Could not enable coprocessor 1 (CP1) in status register. Could not write to CP1 register. 3 - 6 Patterns did not match. Convert doubleword to word (CVT D. W. ) least signiﬁcant failed.
Page 210: Serial Line Test
Serial Line Test The Serial Line test checks the serial line controller’s ability to receive and transmit characters. To run this test, type t f41 P1 P2 and press Return. Serial line test parameters and error messages Table F-2 describes the parameters used in serial line test commands and error messages.
Page 211: Serial Line Test Error Codes
Table F-3. Serial Line Test Error Codes Error Code Meaning Serial line transmit/receive test failed. Serial line was not ready. Serial line received no interrupt. Serial line timeout error occurred. Serial line interrupt error occurred. Serial line read buffer error occurred. 7 - 9 Not used.
Page 212: Serial Line Silo Alarm Test
Serial Line Silo Alarm Test The serial line silo alarm test checks the serial line controller’s ability to generate a silo alarm interrupt. To run this test, type t f42 P1 P2 and press Return. Serial line silo alarm test error messages Table F-4 describes the parameters in serial line silo alarm test commands and error messages.
Page 213: Serial Line Single Silo Test
Serial Line Single Silo Test The serial line single silo test checks the serial line controller’s ability to ﬁll and empty the silo. To run this test, type t f43 P1 P2 and press Return. Serial line single silo test error messages Table F-6 describes the parameters in serial line single silo test commands and error messages.
Page 214: Serial Line Silo Overﬂow Test
Serial Line Silo Overﬂow Test The serial line silo overﬂow test checks the serial line controller’s ability to signal a silo overﬂow. To run this test, type t f44 P1, and press Return. Serial line silo overﬂow test error messages Table F-8 describes the parameters in serial line silo overﬂow test commands and error messages.
Page 215: Serial Line Mixed Silo Test
Serial Line Mixed Silo Test The serial line mixed silo test checks the serial line controller’s ability to ﬁll an empty the silo with multiple lines. To run this test, type t f45 P1 and press Return. Serial line single silo parameters and error messages Table F-10 describes the parameters used in serial line mixed silo test commands and error messages.
Page 216: Modem And Printer Test
Modem and Printer Test The modem and printer test checks the serial line controller’s ability to interface with the modem and printer. To run this test, type t f46 P1 P2 and press Return. Modem and printer test parameters and error messages Table F-12 describes the parameters used in modem and printer test commands and error messages.
Page 217: Keyboard And Mouse Test
Keyboard and Mouse Test The keyboard and mouse test checks the keyboard, mouse and serial line controller on the system module. To run a keyboard and mouse test, type t f41 P1 P2 and press Return. Keyboard and mouse test parameters and error messages Table F-14 lists the parameters used in keyboard and mouse test commands and error messages.
Page 218: Real-Time Clock Register Test
Table F-15. Keyboard and Mouse Test Error Codes Error Code Meaning Self-test failed. Serial line timeout waiting for receive done (rdone). Search for loopback failed. Returned value was not zero. Real-Time Clock Register Test The real-time clock register test checks the real-time clock registers.
Page 219: Real-Time Test Error Codes
Table F-17 describes the error codes used in real-time test error messages. Table F-17. Real-Time Test Error Codes Error Code Meaning UIP bit remained set past allotted time. Error occurred when setting real-time clock control registers. Real-time clock interrupt was pending when its should not Error occurred setting real-time clock time registers.
Page 220: Real-Time Clock Period Test
Real-Time Clock Period Test The real-time clock period test checks the real-time clock’s periodic interrupt operation. To run the real-time clock period test, type t f53 and press Return. Real-time clock period test error messages Table F-18 describes the error codes used in real-time clock period test error messages.
Page 221: Cache Data Test
Cache Data Test The cache data test writes then reads and veriﬁes data patterns to the cache. To run the cache data test, type t f60 P1 P2 and press Return. Cache data test parameters and error messages Table F-19 describes the parameters used in cache data test commands and error messages.
Page 222 Table F-20 (Cont.). Cache Data Test Error Codes Error Code Description Cache read miscompare occurred. Value read back should be address complement. Cache address complement read caused a parity error. F–16 Test Commands and Messages Produced by Version PDE3 ROM Chips...
Page 223: Cache Isolate Test
Cache Isolate Test The cache isolate test isolates then reads and writes data patterns to the cache. To run the cache isolate test, type t f61 P1 and press Return. Cache isolate test parameters and error messages Table F-21 describes the parameters used in cache isolate test commands and error messages.
Page 224: Overtemp Detect Test
Table F-22 (Cont.). Cache Isolate Test Error Codes Error Code Description Reading 55555555 pattern returned a data miscompare. Test failed reading AAAAAAAA pattern. Reading AAAAAAAA pattern returned a cache parity error. Reading AAAAAAAA pattern returned a cache miss error. Reading AAAAAAAA pattern returned a data miscompare. Failure occurred reading data address pattern.
Page 225: Show Versions Utility
Show Versions Utility The show versions utility displays the ID numbers of all versions of the system and optional modules. To run the show versions utility, type t fC3 module, and press Return. To ﬁnd the version ID of a single module, replace module with the slot number of the module for which you want the version ID number.
Page 226: Script Acquire Utility
Script Acquire Utility The script acquire utility creates test scripts. This utility asks the user a series of questions that set test script conditions. To use the script acquire utility, type ffe P1, where P1 represents the memory address where the script is stored, and press Return.
Page 227: Memory Module Tests
Memory Module Tests The following entries explain the commands and error codes for each memory module self-test. RAM Data Test The RAM data test checks the operation of individual memory modules. To run a RAM data test on all memory modules, type 8f21 and press Return.
Page 228: Ram Conﬁguration Test
RAM Conﬁguration Test The RAM conﬁguration test checks memory module’s base addresses. To run the RAM conﬁguration test, type f32 and press Return. RAM conﬁguration test error messages Table F-26 describes each RAM Data test error code. Table F-26. RAM Conﬁguration Test Error Codes Error Code Meaning Attempt to write pattern to module’s base address failed.
Page 229: Error Correcting Code Generate Test
Error Correcting Code Generate Test The error correcting code (ECC) test performs a write and read operation in memory, then compares the resulting ECC with the computed value. To run the ECC generate test, type f33 P1 and press Return. ECC generate test error messages Table F-27 describes the parameters in ECC generate test error messages.
Page 230: Ecc Single Bit Error Fix Test
ECC Single Bit Error Fix Test The ECC single bit error (SBE) ﬁx test writes ﬂoating 1s with ECC set for zero then checks if the results are zero. To run this test, type t f34 P1, where you replace P1 with the address at which you want to start writing 1s, and press Return.
Page 231 Table F-30 (Cont.). ECC SBE Fix Test Error Codes Error Code Meaning ERRADR VALID bit was not set. Error was possibly not detected. ERRADR CPU bit was not set. ERRADR WRITE bit was set on what should have been a read error.
Page 232: Partial Write Test
Partial Write Test This test performs a read and write to a speciﬁc address, then checks if the read and write values are the same. To run the Partial Write test, type t f35 P1, where you replace P1 with the memory address to which you want to write, and press Return.
Page 233: Build Bitmap Utility
Build Bitmap Utility This utility constructs a bitmap that contains memory size, and good and bad pages. To run the Bitmap utility, type t f3d, and press Return. Zero RAM Test The Zero RAM test ﬂoods memory with zeroes as fast as possible.
Page 234: Ethernet Tests
Ethernet Tests The following entries explain the purpose, test commands, and error messages for each individual Ethernet test. Registers Test The registers test performs a read/write operation on the Ethernet register. To run the registers test, type t x01, where x represents the unit number of the Ethernet controller you want to test, and press Return.
Page 235: Internal Loopback Test
Internal Loopback Test The internal loopback test sends and receives data packets to the Ethernet in internal loopback mode. To run the internal loopback test, type t x02 P1, and press Return. When you use this test command Replace x with the unit number of the Ethernet module you want to test.
Page 236: External Loopback Test
External Loopback Test The external loopback test sends an external loopback packet and tests the system’s connection to the network. To run the external loopback test, type t x03 P1, and press Return. When you use this test command Replace x with the unit number of the Ethernet module you want to test.
Page 237: Cyclic Redundancy Code Detect Test
Cyclic Redundancy Code Detect Test The cyclic redundancy code (CRC) detect test checks the ethernet’s CRC veriﬁcation and bad CRC detection abilities. To run the CRC detect test, type t x04 P1 and press Return. When you use this test command, Replace x with the unit number of the Ethernet controller you want to test.
Page 238: Crc Detect Error Codes
Table F-40. CRC Detect Error Codes Error Code Description Error occurred reading Ethernet station address ROM. Error occurred initializing Ethernet chip. Error occurred transmitting packet. Error occurred receiving packet. Ethernet chip ﬂagged a good CRC on a packet with a bad CRC.
Page 239: Collision Test
Collision Test The collision test checks the Ethernet’s collision detect circuitry by forcing a collision on transmit. To run the collision test, type t x05 P1 and press Return. When you use this test command, Replace x with the unit number of the Ethernet controller that you want to test.
Page 240: Promiscuous Mode Test
Promiscuous Mode Test The promiscuous mode test checks the Ethernet’s ability to receive packets in promiscuous mode. To run the promiscuous mode test, type t x06 P1, and press Return. When you use this test command Replace x with the unit number of the Ethernet module that you want to test.
Page 241: Multicast Test
Table F-44. Promiscuous Mode Test Error Codes Error Code Description Error occurred reading Ethernet station address ROM. Error occurred initializing the Ethernet controller chip. Error occurred sending packet. Error occurred receiving packet. An inappropriate packet was received in nonpromiscuous mode. Packet receive routine returned a miscellaneous error.
Page 242: Multicast Test Parameters And Error Codes
Multicast test parameters and error codes Table F-45 describes the parameters used in multicast test commands and error messages. Table F-46 lists the error codes used in multicast test error messages. Table F-45. Multicast Test Parameters Parameter Description Ethernet RAM address used to set up structures Return status from any of the common subroutines Last value read from CSR0 Table F-46.
Page 243: Interrupt Request Test
Interrupt Request Test The interrupt request (IRQ) test checks the Ethernet controller’s ability to generate an interrupt to the R3000 chip. To run the IRQ test, type t x08 P1, and press Return. When you use this test command Replace x with the unit number of the Ethernet controller that you want to test.
Page 244: Ethernet Ram Test
Ethernet RAM Test The Ethernet RAM test checks the Ethernet RAM’s operation. To run the Ethernet RAM test, type t x20 P1 and press Return. When you use this command, Replace x with the unit number of the Ethernet controller you want to test.
Page 245: Ethernet Station Address Rom Test
Ethernet Station Address ROM Test The ethernet station address ROM (ESAR) test checks the ethernet station address ROM on the Ethernet controller. To run the ESAR test, type t x21 and press Return. ESAR test error codes Table F-51 lists error codes used in ESAR test error messages. Table F-51.
Page 246: Scsi Controller Tests
SCSI Controller Tests The following entries explain each SCSI controller test and its test commands and error messages. SCSI Controller Chip Test The SCSI controller chip test checks the SCSI controller chip’s operation. To run the SCSI controller chip test, type x11, where x represents the unit number of the SCSI controller you want to test, and press Return.
Page 247: Scsi Buffer Test
SCSI Buffer Test The SCSI buffer test checks the SCSI buffer’s operation. To run the SCSI buffer test, type x12 P1 P2 and press Return. When you type this command, Replace x with the unit number of the SCSI controller you want to test.
Page 248: Scsi Ram Test
SCSI RAM Test The SCSI RAM test performs a read/write operation on the SCSI controller’s RAM. To run the SCSI RAM test, type x13, where x represents the unit number of the SCSI controller you want to test, and press Return. SCSI RAM test parameters and error codes The SCSI RAM test returns an error message if the read and write values do not match.
Page 249: Scsi Port Test
SCSI Port Test The SCSI port test checks the devices on a speciﬁed SCSI controller’s bus. To run the SCSI port test, type x14 P1 and press Return. When you type this command, Replace x with the unit number of the SCSI controller’s bus you want to test.
Page 250: Graphics Module Tests
Graphics Module Tests The following entries explain each individual graphics module test and its test commands and error messages. Initialize Video Digital to Analog Converter Registers Test The initialize video digital to analog converter (VDAC) registers test attempts to initialize the VDAC registers. To run the initialize VDAC registers test, type x01, where x represents the graphics module’s unit number, and press Return.
Page 251: Video Ram Test
Video RAM Test The video RAM test performs a read/write operation on the video RAM. To run the video RAM test, type x02, where x represents the graphics module unit number, and press Return. Video RAM test parameters and error codes Table F-61 describes the parameters used in video RAM test error messages.
Page 252: Font Test
Font Test The font test ﬁlls the monitor screen with a speciﬁed character. To run the Font test, type x03, and press Return. Replace x with the graphics module unit number. Replace the optional parameter P1 with the hexadecimal value for the speciﬁc character you want to display. Replace P1 with 0 to display all fonts.
Page 253: Cursor Test
Cursor Test The cursor test the cursor RAM. To run the cursor test, type x12, where x represents the graphics module unit number, and press Return. Cursor test parameters and error codes Table F-63 describes the parameters used in cursor test commands and error messages.
Page 254: Analog Video Output Test
Analog Video Output Test The analog video output test displays a series of patterns on the monitor. To run the analog video output test, type x13, where you replace x with the graphics module unit number, and press Return. Analog video output test parameters and error codes Table F-65 describes the parameters used in pattern test commands and error messages.
Page 255: Initial Power-Up Tests
Initial Power-Up Tests The system completes a series of initial system checks whenever you turn on the system power. If the system halts at one of these tests, the diagnostic LEDs display a code that indicates the problem. Table F-67 lists initial power-up test LED displays and their meaning.
Page 256 Table F-67 (Cont.). Initial Power-Up Test Error Codes Error Code Description Test could not invoke portable diagnostic executive to dump any pending error messages. Test halted after return from main console. Test halted at start of test stack. Writing pattern of 5s to the ﬁrst 192 Kbytes failed. Reading pattern of 5s from ﬁrst 192 Kbytes returned a miscompare.
Page 257: Generated By Version Pde3 Rom Chips
Console Status and Error Message Codes Generated by Version PDE3 ROM Chips This appendix explains the codes used in console status and error messages generated by the Version PDE3 ROM chips. It includes Major error and status code numbers and phrases, which indicate the general condition that generated the console message.
Page 258: Major Error And Status Error Codes
Major Error and Status Code Numbers and Phrases Table G-1 lists the major codes found in console error and status messages. Table G-1. Major Error and Status Error Codes Major Code Displayed Phrase Meaning Invld prm Invalid parameter received. Intrnl err optn Error detected in an optional controller ROM code.
Page 259 Table G-1 (Cont.). Major Error and Status Error Codes Major Code Displayed Phrase Meaning Wrt err I/O error detected during a write operation. IO err I/O error detected. Bootng (^C => System is booting. To abort the boot abrt) operation. press Ctrl-C. Rstrtng System is restarting.
Page 260: Minor Console Error And Status Error Codes
Minor Console Error and Status Error Codes Table G-2 lists minor codes used in error and status messages. Table G-2. Minor Error and Status Error Codes Minor code Meaning 03e9 Option conﬁguration is invalid. 03ea There is no driver to support the controller. 03eb Auto boot attempted but no bootpath is set.
Page 261 Table G-2 (Cont.). Minor Error and Status Error Codes Minor code Meaning 0410 Console device must be a character device. 0411 Command is not deﬁned in command table. 0412 System cannot give help on undeﬁned command. 0413 String overﬂow occurred in video_enable. 0416 Overﬂow occurred in ahtob routine.
Page 262 Table G-2 (Cont.). Minor Error and Status Error Codes Minor code Meaning 043e Unable to handle empty circular buffer here. 043f No more unused I/O available. 0440 No more unused I/O-control blocks available. 0441 Invalid ﬁle name encountered by ﬁlename parser. 0442 Corrupted job pointer.
Page 263 Table G-2 (Cont.). Minor Error and Status Error Codes Minor code Meaning 045e Password string hashed to zero. 045f Unprivileged user attempted privileged form of password. 0460 Two new password strings did not match. 0461 Unprivileged user attempted to use privileged form of password.
Page 264 Table G-2 (Cont.). Minor Error and Status Error Codes Minor code Meaning 047d SCSI has no iopb. 047e SCSI device is inappropriate type. 047f SCSI check condition status reported. 0480 SCSI unexpected status reported. 0481 SCSI sense failure occurred. 0482 SCSI sense failure occurred.
Page 265 Table G-2 (Cont.). Minor Error and Status Error Codes Minor code Meaning 049b Major SCSI problem occurred. 049c SCSI IO parity error occurred. 049d SCSI sent too many message bytes. 049e SCSI sent no message. 049fS SCSI reselect error occurred. 04a0 SCSI is selected when it should not be.
Page 266: Index
Index Alternate terminal, 2–3 to 2–4 Diagnostic LEDs Antistatic kit, 2–2 error codes, 4–3 to 4–6 in power-up self-tests, 3–3 system unit, 1–6 Diagnostic ROM’s, 5–2 Booting software, 2–23 Drives, 1–10 Cache tests, D–4 to D–9 Equipment speciﬁcations Communication connectors, 1–7 keyboard (LK201), A–3 to A–4 Communications line adapter mouse (VSXXX-AA), A–5 to A–6...
Page 267 Error messages (Cont.) interpreting, 3–8 ESAR chip, 5–4, 5–6 Memory error logs, 3–11 to 3–12 removing and installing, 5–8 FRU failure, 4–8 Ethernet connector, 1–7 Memory module, 5–9 to 5–14 address ranges, 5–10 expansion slots, 1–9 to 1–10 RAM board test, 5–11 FPU test, D–21 to D–22 removing and installing, 5–13 to FRU (Field Replacement Unit)
Page 268 SCSI chain terminator (Cont.) removing and installing, 2–15 SCSI controller, 5–2 P1 parameter, 5–11 options, 1–10 Partial Write test, D–27 Serial line tests, 5–17, D–19 Part numbers Serial number plate basic components, B–3 removing and installing, 2–9 to 2–10 cords, cables, and connectors, B–4 Service operations, 2–24 hardware, B–1 to B–4 Slot number...
Page 269 ThickWire Ethernet loopback connector mouse, 5–16 removing and installing, 2–13 power supply, 5–21 to 5–26 ThinWire Ethernet controller, 5–2 software, 2–23 ThinWire Ethernet terminator system module, 5–3 removing and installing, 2–12 tests used for, 3–2 Troubleshooting t slot/? command, 3–5 FRU failure, 4–2 to 4–11 incomplete self-test, 4–6 keyboard, 5–16...

DEC DECstation 5000 Model 200 Maintenance Manual

Using this Guide

Tables

Figures

Service Operations

Troubleshooting Tools

Identifying Failed Frus

Basic Hardware

A Equipment Speciﬁcations

B Recommended Spares List

Console Commands

D Test Commands and Messages

Quick Links

Troubleshooting

Related Manuals for DEC DECstation 5000 Model 200

Summary of Contents for DEC DECstation 5000 Model 200