Digital Equipment VAXstation 4000 90 Service Information

Table of Contents

Quick Links

Digital Equipment Corporation

VAXstation 4000 Model 90

Service Information

EK-KA490-SV. A01

Digital Equipment Corporation

Table of Contents

Need help?

Do you have a question about the VAXstation 4000 90 and is the answer not in the manual?

Questions and answers

Summary of Contents for Digital Equipment VAXstation 4000 90

Page 1 Digital Equipment Corporation VAXstation 4000 Model 90 Service Information EK-KA490-SV. A01 Digital Equipment Corporation...
Page 2 First Edition, August 1992 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 Preface System Module Introduction ........... . . 1–1 System Overview .
Page 4 System Console Commands ........4–2 Alternate Consoles .
Page 5 Installing the TURBOchannel Option ....... . . 6–55 TURBOchannel Speciﬁcations ........6–63 Appendix A Diagnostic Error Codes Overview .
Page 6 2–6 Main Conﬁguration Table ......... . . 2–21 2–7 Device Conﬁguration Table .
Page 7 6–13 Installation Details ..........6–32 6–14 Installing the SPXg 8-plane Option .
Page 8 4–6 Processor Control Commands ........4–21 4–7 BOOT Command Syntax .
Page 9 A–18 AUD Self-Test Error Codes ......... A–45 A–19 Synch Comm Device Test Error Codes .
Page 10 D–3 Miscellaneous Hardware ......... . . D–5 D–4 Cables and Terminators .
Page 11: Preface
Preface Overview Purpose and This manual is a support and reference document for Digital Audience Services personnel who perform maintenance work on the VAXstation 4000 Model 90 workstation. It is also intended for Digital customers who have a self-maintenance agreement with Digital.
Page 12 Overview, Continued Organization Appendix A, Diagnostic Error Codes, contains tables listing (continued) error codes, error messages, and utilities. Appendix B, Reading the Diagnostic LED codes, describes how to read the diagnostic LED codes. Appendix C, Troubleshooting, contains troubleshooting information. Appendix D, FRU Part Numbers, contains tables that provide part numbers for FRUs.
Page 13 Overview, Continued Conventions This guide uses the following conventions: Convention Description WARNING Contains important information that relates to personal safety. CAUTION Contains information to prevent damage to the equipment. NOTE Contains general information. Part number Ctrl/C This type of key sequence means you hold down the ﬁrst key while you type the letter of the next key.
Page 15: System Module
Chapter 1 System Module Introduction This chapter describes the features of the VAXstation 4000 Model In this Chapter 90 system module. The topics covered include: System Overview Central Processor Unit (CPU) Interrupts and Exceptions Cache Memory Main Memory System ROM Memory Graphics Controller Network Interface Controller Serial Line Controller...
Page 16: System Overview
System Overview The KA49 CPU module combines with either the 4-MB or 16-MB Overview (or both) SIM modules to form the CPU/memory subsystem for the VAXstation 4000 Model 90 product. The VAXstation 4000 Model 90 system is housed in a BA46 enclosure. The subsystem uses the SCSI-1 bus to communicate with mass storage devices, and transceiver cable (Thickwire or ThinWire connector) to connect with an Ethernet network.
Page 17: Major Components
System Overview, Continued Table 1–1 lists the major hardware components found on the Components KA49 CPU module. Table 1–1 Major Components DC246 Central processor NVAX Cache RAMs 256-KB Bcache —– DC243 NDAL to CDAL I/O bus interface chip DC244 Main memory controller, with ownership bit control NCR 53C94 Advanced SCSI controller...
Page 18: Ka49 Cpu Module Components
System Overview, Continued Chip Locations Figure 1–1 shows the major chip locations on the KA49 CPU module. Figure 1–1 KA49 CPU Module Components T h i c k W i r e E t h e r n e t R S 2 3 2 P r i n t K B D...
Page 19: Central Processor Unit
Central Processor Unit Figure 1–2 shows how, functionally, the KA49 CPU module is Overview divided into ﬁve major areas. Central processing subsystem Graphics subsystem System support subsystem I/O Subsystem Memory control subsystem Continued on next page 1–5...
Page 20: Ka49 Cpu Module Block Diagram
Central Processor Unit, Continued Figure 1–2 KA49 CPU Module Block Diagram G - B I T S 2 5 6 K B N V A X C A C H E & T A G N C A N M C N D A L C O N S O L E S G E C...
Page 21 Central Processor Unit, Continued Central The NVAX CPU (DC246) chip is the heart of the KA49 CPU Processing module. It executes the VAX base instruction group as deﬁned in the VAX Architecture Reference Manual plus the optional VAX Subsystem vector instructions and the virtual machine instructions. The NVAX processor also supports full VAX memory management with demand paging and a 4-gigabyte virtual address space.
Page 22 Central Processor Unit, Continued System The system support subsystem handles the basic functions Support required to support the console in a system environment. This subsystem contains the ﬁrmware ROMs, the ﬁrmware ROM Subsystem controller, the conﬁguration register, and the station address ROM.
Page 23 Central Processor Unit, Continued Sound generator Four asynchronous lines Time-of-Year clock Ethernet identiﬁcation ROM NVAX CP-Bus To provide buffering and connection to the I/O devices, the KA49 contains a DC243, NDAL to CDAL adapter (NCA). The NCA Bus Adapter provides an interface between the NVAX NDAL bus and two CP- Buses where the I/O device adapters reside.
Page 24 Central Processor Unit, Continued through a scatter/gather map that allows physically discontiguous pages of data to appear to be contiguous to the bus adapter option. Sound output uses the DTMF tone generation capability of Sound the 79C30 chip. Two tone generators may be individually Generator programmed for frequency and amplitude;...
Page 25 Central Processor Unit, Continued cache memory, as well as providing a secure interlock mechanism for synchronization between NVAX and the I/O devices. The memory controller is implemented by the NVAX memory controller chip (DC244). The NMC is an ECC protected memory controller.
Page 26: General Purpose Register Descriptions
Central Processor Unit, Continued Non-privileged software can access the GPRs and the processor status word (bits <15:00> of the PSL). The IPRs and bits <31:16> of the PSL can only be accessed by privileged software. The IPRs are explicitly accessible only by the move-to-processor register (MTPR) and the move-from-processor register (MFPR) instructions which can be executed only while running in kernel mode.
Page 27 Central Processor Unit, Continued Internal The internal processor registers (IPRs) that are implemented by Processor the KA49 CPU chip, and those that are required of the system Registers environment, are logically divided into ﬁve groups, as follows: Normal—Those IPRs that address individual registers in the KA49 CPU chip or system environment Bcache Tag IPRs—The read-write block of IPRs that allow direct access to the Bcache tags...
Page 28: Interrupts And Exceptions
Interrupts and Exceptions Both interrupts and exceptions divert execution from the normal Overview ﬂow of control. An interrupt is caused by some activity outside the current process and typically transfers control outside the process (for example, an interrupt from an external hardware device). An exception is caused by the execution of the current instruction and is typically handled by the current process (for example, an arithmetic overﬂow).
Page 29: Interrupt Priority Levels
Interrupts and Exceptions, Continued Interrupt Table 1–3 lists KA49 interrupt conditions, associated priority Priority Levels levels, and SCB offsets. Note that Table 1–3 is intended as a quick reference, and may not include all possible causes of the various interrupts. Table 1–3 Interrupt Priority Levels Priority Level Interrupt Condition...
Page 30 Interrupts and Exceptions, Continued Table 1–3 (Continued) Interrupt Priority Levels Priority Level Interrupt Condition SCB Offset Correctable main memory errors Uncorrectable main memory errors Correctable O-bit memory errors Pending read times out waiting for disown write No acknowledgment on returned read data from NMC NDAL Data parity errors Pcache tag or data parity errors...
Page 31 Interrupts and Exceptions, Continued Table 1–3 (Continued) Interrupt Priority Levels Priority Level Interrupt Condition SCB Offset IRQ_H[2] asserted Unused Interval timer (IRQ_H[2] takes priority) IRQ_H[1] asserted IRQ_H[0] asserted Network interface 13:10 Unused 0F:01 Software interrupt requests 84-BC ** These conditions generate a hardware halt procedure with a halt code of 2 (external halt). Exceptions There are six categories of exceptions.
Page 32: Exception Categories
Interrupts and Exceptions, Continued Table 1–4 Exception Categories Exception Class Instances Arithmetic traps/faults Integer overﬂow trap Integer divide-by-zero trap Subscript range trap Floating overﬂow fault Floating divide-by-zero fault Floating underﬂow fault Memory management Access control violation fault exceptions Translation not valid fault M=0 fault Operand reference Reserved addressing mode fault...
Page 33 Interrupts and Exceptions, Continued Trap A trap is an exception that occurs at the end of the instruction Exceptions that caused the exception. Therefore, the PC saved on the stack is the address of the next instruction that would normally have been executed.
Page 34: Cache Memory
Cache Memory The NVAX memory subsystem follows a hierarchical structure. Overview The VIC, Pcache, Bcache, and ﬁnally the main memory form the hierarchical memory subsystem of the KA49. The hierarchical ordering of the various levels of KA49 memory is shown in Figure 1–3.
Page 35 Cache Memory, Continued layer for storing references. Furthermore, care must be taken to ensure that the state of the system is singularly and accurately represented by the combined contents of the caches and main memory. In the KA49 this issue is most critical between main memory and the Bcache and Pcache, because main memory can be accessed by DMA devices as well as the NVAX CPU.
Page 36 Cache Memory, Continued The VIC is a 2-KB, direct-mapped cache for caching I-stream data. The VIC is located within the NVAX CPU chip. In order to reduce the overhead associated with virtual-to-physical address translation, the VIC caches references based on virtual addresses. In the event that the virtual references made by the instruction prefetcher hit in the VIC, the I-stream data is loaded from the VIC directly to the IPQ.
Page 37 Cache Memory, Continued scheme, the write operation updates the contents of the Pcache, and the write operation is propagated to the next level of memory hierarchy, the Bcache. The Pcache is maintained as a strict subset of the Bcache. Backup Cache The backup cache (Bcache) is direct-mapped, with quadword access size, and a hexaword (32 bytes) block size.
Page 38: Main Memory System
Main Memory System The main memory system is implemented in the NVAX memory Overview controller chip (NMC). The NMC communicates with SIM modules over the NVAX memory interconnect (NMI). Up to eight SIM modules are supported, for a maximum of 128 MB of main memory.
Page 39: Rom Memory
ROM Memory The system board ROM contains processor restart, diagnostic and Overview console code, and the primary bootstrap program. Another small ROM is uniquely programmed for each system with its network address. System Board The system board ROM contains four 128 KB x 8 FLASH ROM chips that collectively hold 512 KB of data.
Page 40: Graphics Controller
Graphics Controller The VAXstation 4000 Model 90 workstation supports three Overview graphics options: LCSPX, SPXg, and SPXgt. The LCSPX module is a low cost graphics module, while the SPXg/gt modules support high performance 3D graphics. The SPXg is an 8-plane graphics module and the SPXgt is a 24-plane graphics module.
Page 41: Diagnostic Rom/Conﬁguration Register Bit Deﬁnitions
Graphics Controller, Continued Table 1–6 Diagnostic ROM/Conﬁguration Register Bit Deﬁnitions Name Deﬁnition <31> Scanproc Test This bit is driven by the Scanproc chip during diagnostics. <30> Time Out This bit is set when 2 VRAM refresh pulses occur while DS is low, indicating a hung system. <29:18>...
Page 42: Network Interface Controller
Network Interface Controller The KA49 includes a network interface that is implemented by Overview the second generation Ethernet controller (SGEC). This interface allows the KA49 module to be connected to either a ThinWire or standard Ethernet network and supports the Ethernet data link layer.
Page 43: Serial Line Controller
Serial Line Controller The serial line controller handles four asynchronous serial lines. Overview The DC7085 chip is used as the serial line controller. The DC7085 directly controls an external 64-entry silo shared by all four receive lines. Access to the DC7085 by the CPU and interrupt processing for the DC7085 are controlled by the CEAC.
Page 44: Time-Of-Year Clock
Time-of-Year Clock The time-of-year (TOY) clock consists of an MC146818BM CMOS Overview watch chip that keeps the date and time of day and contains 50 bytes of general purpose RAM storage. This chip includes a time base oscillator and a lithium battery on-chip. The battery powers the chip with logic and oscillator while system power is off.
Page 45: Scsi Controller
SCSI Controller The SCSI interface is a single-ended, bi-directional, 8-bit-wide bus Overview to which up to eight devices can be attached. The KA49 system module is one of those devices, allowing the attachment of up to seven additional devices. Devices may play one of two roles: initiator or target.
Page 46 SCSI Controller, Continued SCSI Bus Table 1–8 describes the SCSI bus signals used by the SCSI Signals controller. Table 1–8 SCSI Bus Signals Bus Signal Description DB7..0 and DBP An 8-bit parallel data bus with an associated odd parity bit. The use of the parity bit is optional but strongly encouraged.
Page 47: Dsw21 Synchronous Communications Adapter
DSW21 Synchronous Communications Adapter The DSW21 syncrhonous communications adapter is a Overview synchronous serial communications interface for the VAXstation 4000 Model 90 workstation. It has full modem control and multiple protocol support. Figure 1–4 shows the DSW21 communications adapter. Figure 1–4 Synchronous Communications Adapter MLO-005915 The adapter is an option board that connects internally to the CPU board by a 64-pin option connector.
Page 48: Dsw21 Connections
DSW21 Synchronous Communications Adapter, Continued Figure 1–5 DSW21 Connections 64-PIN 50-PIN CONN CONN 128K BYTE 256K BYTE PROM SRAM EDAL MC68302 CONTROL LOGIC INTERRUPT LJ-02225-TI0 1–34...
Page 49: Firmware
Chapter 2 Firmware Overview Introduction This chapter provides an overview of the VAXstation 4000 Model 90 system ﬁrmware. The ﬁrmware is located in four EPROMs, which hold a total of 512 KB of data. The system ﬁrmware has ﬁve distinct areas of operation. This chapter discusses the following topics: Power-Up Initialization Code Console Mode...
Page 50: Power-Up Initialization Code
Power-Up Initialization Code The power-up initialization code is executed when power is Overview applied to the VAXstation 4000 Model 90 workstation or any time volatile console data structures are altered. Power-Up Table 2–1 describes the power-up initialization sequence. Initialization Sequence Table 2–1 Power-Up Initialization Sequence Stage What the System Does...
Page 51 Power-Up Initialization Code, Continued Table 2–1 (Continued) Power-Up Initialization Sequence Stage What the System Does Tests the serial lines. If this test fails, the console terminal is not enabled and the only output is the HEX display. If... And... Then... No video option is —–...
Page 52 Power-Up Initialization Code, Continued Table 2–1 (Continued) Power-Up Initialization Sequence Stage What the System Does Test dispatcher tests the functional blocks of the system. This test displays a blank ruler on the screen. The length of the ruler is dependent on the devices in the system.
Page 53: Console Mode
Console Mode The VAXstation 4000 Model 90 console mode allows operation of a Overview console device, which can be one of the following: A workstation video device and LK401 keyboard and mouse A terminal connected to line three of the serial port A remote system connected using the Ethernet Console Mode The console mode can be entered if:...
Page 54: Extended Self-Test
Extended Self-Test The extended self-tests are started by entering the TEST Overview command at the console prompt, followed by the test number or numbers you wish to run. The test dispatcher runs the self-test requested until an error occurs or until all tests are completed. Test Dispatcher The dispatcher uses the main conﬁguration table (MCT), device conﬁguration table (DCT), and drive descriptor data structures...
Page 55 Extended Self-Test, Continued Table 2–2 (Continued) Test Dispatcher Procedure Stage What the Dispatcher Does Reads the ﬂags ﬁeld in the DCT to determine if the diagnostic uses a shared diagnostic driver. If... Then... The self-test diagnostic The dispatcher gets the directory entry and the uses a shared pointer to the driver descriptor from the DCT.
Page 56: Utilities
Utilities A utility test is started at the console prompt by entering a Overview command using the following format: TEST/UTIL dev_nbr util_nbr op1...opn Format Meaning /UTIL Instructs the test dispatcher to run a utility dev_nbr The device on which the utility operates util_nbr The utility number op1...opn...
Page 57 Utilities, Continued Table 2–3 (Continued) Running a Utility Process Stage Dispatcher Process Reads the ﬂags ﬁeld in the DCT to determine if the utility uses a shared diagnostic driver. If... Then... The utility uses a The dispatcher gets the directory entry and the shared diagnostic pointer to the driver descriptor from the DCT.
Page 58: System Test
System Test The system test tests the device interaction in the system by Overview creating maximum DMA and interrupt activity. The test consists Modiﬁed VAXELN kernel System test monitor System diagnostics Shared drivers (if present) The system test can be run in three environments, selected by the SET DIAGENV command.
Page 59: System Rom
System ROM The base VAXstation 4000 Model 90 ﬁrmware contains 512 KB of Overview ROM split into four 128-KB wide ROMs. This provides the full 32-bit wide memory data path shown in Figure 2–1. Figure 2–1 System ROM Format R O M 3 R O M 2 R O M 1 R O M 0...
Page 60: System Rom Part Format
System ROM, Continued Figure 2–2 System ROM Part Format 1 5 ..8 7 ..0 w o r d 0 R e s e r v e d f o r R O M s e t D a t a R e s e r v e d f o r R O M s e t D a t a w o r d 1 R e s e r v e d f o r R O M s e t D a t a...
Page 61: System Rom Part Formats
System ROM, Continued System ROM Table 2–4 shows the part formats in the system ROM. Part Format Table 2–4 System ROM Part Formats Byte Name Description Word 02h Version Contains the low 8 bits of the version number of the console code for the Model 90 system ﬁrmware.
Page 62: System Rom Physical Addresses
System ROM, Continued System ROM Table 2–5 shows the physical addresses in the system ROM. These Set Format addresses are ﬁxed. Table 2–5 System ROM Physical Addresses Physical Address Name Description 2004.0000 Processor restart The hardware begins execution at this address when: Power is turned on.
Page 63 System ROM, Continued Table 2–5 (Continued) System ROM Physical Addresses Physical Address Name Description 2004.008A System This word contains the system diagnostic diagnostic ﬁrmware revision number. ﬁrmware revision number 2004.008C Diagnostic This longword contains the physical descriptor address of the beginning of the system level diagnostic boot block.
Page 64: Option Rom
Option ROM Each option in the Model 90 system has its own ROM ﬁrmware. Overview The ROM memory on the option board may be implemented as discussed in the following sections. Option ROM The option ROM part format is provided for each byte in the ROM Part Format set.
Page 65 Option ROM, Continued Byte Name Description Data path Indicates the size of the ROM data indicator path. The data path must be one of the following: 1: One byte per longword. Bytes in ROM occupy the low byte of each longword. 2: Two bytes per longword.
Page 66: Option Rom Set Data
Option ROM, Continued Byte Name Description ROM part Indicates the length of each byte length address in the set. It is the number of bytes associated with each byte in the ROM in Kbytes. NOTE The number of bytes in the ROM set equals the sum of the number of bytes in each of the ROM parts divided by the data path of each device.
Page 67 Option ROM, Continued Name Description Option revision This number controls changes in both the option hardware and ﬁrmware. Option index value An index value of the last DCT entry. A zero in this ﬁeld indicates a single DCB for the device, a one indicates two device control blocks for this device.
Page 68: Conﬁguration Table
Conﬁguration Table Information on the VAXstation 4000 Model 90 devices is stored in Overview the system conﬁguration tables during the power-up initialization. The initialization code sizes the system by reading the ROM-based device conﬁguration tables (DCT) and builds a memory resident conﬁguration data structure.
Page 69: Main Conﬁguration Table
Conﬁguration Table, Continued Figure 2–6 Main Conﬁguration Table Minor Version ID Major Version ID Number of Devices Edit Version ID Device ID Pointer to Device Configuration Table Device ID Pointer to Device Configuration Table Number of Devices *8 Device ID Pointer to Device Configuration Table (Number of Devices *8)+4 LJ-00104-TI0...
Page 70 Conﬁguration Table, Continued Table 2–6 (Continued) MCT Components Name Description Pointer to device Points to the DCT for the particular conﬁguration table device Replicated for each device in the system. Device There is a device conﬁguration table (DCT) entry for each device Conﬁguration in the Model 90 system.
Page 71: Device Conﬁguration Table
Conﬁguration Table, Continued Figure 2–7 Device Conﬁguration Table Minor Version ID Major Version ID Number of Devices Edit Version ID Device Name Pointer to Driver Descriptors Device Status Pointer to Extended Status Size of Extended Status Pointer to Extended Config Pointer to Permanent Memory Size of Permanent Memory System Test Status...
Page 72: Dct Components
Conﬁguration Table, Continued The components of the DCT are as follows: Table 2–7 DCT Components Name Description Minor version ID Tracks minor changes in the device diagnostic routines Major version ID Tracks major changes in the devices diagnostic routines Number of Number of directory entries for the device.
Page 73 Conﬁguration Table, Continued Table 2–7 (Continued) DCT Components Name Description Size of Amount of permanent memory (in pages) that has been allocated. permanent This ﬁeld is ﬁlled in by the diagnostic the ﬁrst time that it allocates memory memory. System test Saved the last time that system test was ran on this device without status doing intervening test commands.
Page 74 Conﬁguration Table, Continued Table 2–7 (Continued) DCT Components Name Description DP SIZE Contains the data path size of the ROM in which the piece of code resides. Deﬁnition Meaning ROM Width is one byte wide. ROM Width is two bytes wide. ROM Width is four bytes wide.
Page 75: Driver Descriptor
Driver Descriptor Any device that provides a shared port driver or shared class Overview driver must provide a descriptor that supplies the Model 90 base system ﬁrmware, system test monitor, and any other piece of software speciﬁc information about the drive. The format for a driver descriptor is shown in Figure 2–8.
Page 76 Driver Descriptor, Continued Name Description Length of driver Contains the length of the device driver in bytes. This ﬁeld is used by both the base system ROM and the system test monitor to determine the amount of code that needs to be loaded into RAM.
Page 77: Interfacing To Diagnostic Drivers
Interfacing to Diagnostic Drivers The network device contains routines to UNJAM the device and to Overview run self-test routines, system test routines, console routines, and a shared diagnostic driver routine. Figure 2–9 shows how these pieces of code relate to each other. Figure 2–9 Diagnostic Driver Console Support Model Self-Test...
Page 78 Interfacing to Diagnostic Drivers, Continued Overview Call the INIT_DRIVER routine with the following (continued) parameters: — Pointer to the I/O segment table — Pointer to the driver data area — Pointer to the driver function block or console function block —...
Page 79: Console Driver Interface
Console Driver Interface The Model 90 console code is split into a class/port driver scheme. Overview The class driver contains the main console functions, such as PUTCHAR and GETCHAR. The port drivers contain the device speciﬁc code required to support these functions. Figure 2–10 shows the division of the console function.
Page 80 Console Driver Interface, Continued line, the console responds to the serial line driver for both input and output. The console class driver contains the generic routines that interface to the console and user application to perform terminal input and output transactions. The console class driver interfaces with the port driver depending on the current console device.
Page 81: Scia Data Structure
Console Driver Interface, Continued The SCIA data structure is shown in Figure 2–11. Figure 2–11 SCIA Data Structure Console Type LK401 Keyboard Type Address of US Font Table Address of MCS Font Table Address of Keyboard Translation Table Address of Keyboard Map Table Console Class Device ID Console Class Driver Driver Descriptor DZ Device ID...
Page 82: Console Port Driver Function Block
Console Driver Interface, Continued Console Port The ﬁelds of the console port drivers driver descriptor are the Driver same as the console class drivers driver descriptor, with one exception: the port driver contains pointers to the console port level routines. The port driver supports all functions whether or not the device supports console output only or console input /output.
Page 83: System Conﬁguration
Chapter 3 System Conﬁguration Overview This chapter describes the system box used with the VAXstation In this Chapter 4000 Model 90 workstation and its components, cabling, and speciﬁcations. The topics covered in this chapter are: System Box Mass Storage Device Areas Power Supply Internal Cabling System Box Control Panel...
Page 84: System Box
System Box The BA46 enclosure is used for desktop and ﬂoorstand Overview installations of the VAXstation 4000 Model 90 system. Figure 3–1 shows the Model 90 system box and its components. Figure 3–1 Model 90 System Box 5 4 2 0 8 5 4 - 0 2 2 4 - P L A N E 7 0 2 8 1 0 7 - 0 1 F R A M E B U F F E R...
Page 85 System Box, Continued Mass Storage The Model 90 system box can hold two half-height, ﬁxed media Device Areas drives (8.9 cm [3.5 in]) in the H bracket (front left, Figure 3–1), and one half-height, removable media drive (13.3 cm [5.25 in] or 8.9 cm [3.5 in]) in another bracket (front right, Figure 3–1).
Page 86 System Box, Continued AC power for system monitor The power supply speciﬁcations are listed in the following tables. Power Supply Speciﬁcations Input Speciﬁcations Parameter Speciﬁcations Line voltage 120 V 240 V Voltage tolerance 88 V to 132 V 176 V to 264 V Frequency 60 Hz 50 Hz...
Page 87 System Box, Continued Parameter Speciﬁcations Minimum Typical Maximum +12.1 V reg. +11.70 V +12.10 V +12.50 V Short term +12.1 V reg. +11.50 V +12.10 V +12.70 V Long term -12.0 V reg. -11.40 V -12.00 V -12.60 V Long term -9.0 V (isolated) -8.55 V -9.00 V...
Page 88 System Box, Continued Parameter Speciﬁcations Minimum Typical Maximum Ripple and noise 1.0% 2.0% (except +5.1 V and 10 MHz to +3.3 V) 50 MHz Ripple and noise 10 MHz to 50 MHz +5.1 V +3.3 V 30 mV 50 mV 20 mV 30 mV Physical Dimensions...
Page 89: Internal System Devices And Cables
System Box, Continued Figure 3–2 Internal Cabling Power Cable To RX26 Controller Module (Optional) SCSI Cable Graphics Board Power Supply Memory Modules Removable Drive (RRD42, RX26, TZK10 Drives) TLZ06 Fixed Disk Drives (RZ23L, RZ24L, RZ24, RZ25) LJ-02218-TI0 Table 3–1 Internal System Devices and Cables System Device Cable PN Description...
Page 90 System Box, Continued The controls and indicators for the system box are located behind System Box Control Panel the ﬂip-down door on the front bezel (Figure 3–3) of the box. Figure 3–3 System Box Control Panel Audio Selector Switch Alternate Console Switch Handset Jack...
Page 91 System Box, Continued Alternate console switch This switch selects either the graphics terminal or printer/console port to be the system’s console. Halt button When actuated, this button sends a halt signal to the CPU module. Diagnostic lights These lights are located on the right side of the control panel.
Page 92: Model 90 I/O Panel
System Box, Continued Figure 3–4 Model 90 I/O Panel LJ-00639-TI0 Continued on next page 3–10...
Page 93: External System Devices And Cables
System Box, Continued Table 3–2 lists external system devices and their cables. Table 3–2 External System Devices and Cables Device/Cable Cable P/N Description System to monitor BC27R-03 3 coax Dsub. to 3 BNC 39 in (99.1 cm) Remote video BC27R-10 3 coax Dsub.
Page 94: System Box Operating Conditions
System Box, Continued System Box The system box speciﬁcations are listed in the following tables. Speciﬁcations Table 3–3 lists the system box operating conditions and Table 3–4 lists the electrical speciﬁcations. NOTE The operating clearance is 8.9 cm (3.5 in) minimum on the sides and back of the system box.
Page 95: Using The Console
Chapter 4 Using the Console Overview This chapter describes the system console commands and how to In this Chapter use alternate consoles. Diagnostic commands used to troubleshoot a system are described in Chapter 5. The following topics are covered in this chapter: System Console Commands Alternate Consoles 4–1...
Page 96: System Console Commands
System Console Commands Standard console commands for the VAXstation 4000 Model 90 Standard Console are listed by functional groups as follows: Commands Operator assistance commands are HELP or the question mark (?), LOGIN, and REPEAT. SET/SHOW commands are used to set or examine system parameters and conﬁguration.
Page 97 System Console Commands, Continued Operator REPEAT Assistance The REPEAT command repeats a console command entered on Commands the same line following the REPEAT command. (continued) BOOT, INIT, and UNJAM cannot be repeated. The commands being repeated are terminated by pressing Ctrl C Example: This command repeats the memory test.
Page 98: Set/Show Parameters
System Console Commands, Continued The SET and SHOW commands are used to set and examine SET and SHOW Commands system parameters. Table 4–1 lists the SET/SHOW parameters and their meanings. Table 4–1 SET/SHOW Parameters Parameter Meaning SHOW BFLG Default bootﬂag BOOT Default boot device CONFIG...
Page 99 System Console Commands, Continued Table 4–1 (Continued) SET/SHOW Parameters Parameter Meaning SHOW SCSI System SCSI ID TRIGGER Enable network console The following is the syntax for the SET and SHOW commands SET and SHOW and parameters: Command Syntax Syntax: >>> SHOW parameter >>>...
Page 100 System Console Commands, Continued BOOT The BOOT parameter is the default boot device. The boot device can be set to a bootable SCSI drive or the network device. To see the valid device boot names, type >>> SHOW DEVICE. The ﬁrst column of the table (VMS/VMB) lists the device names.
Page 101 System Console Commands, Continued Example: This example shows the information the SHOW CONFIG command displays. >>> SHOW CONFIG KA49-A V0.0-051-V4.0 08-00-2B-F3-31-03 16 MB DEVNBR DEVNAM INFO ------ ------ ---- LCSPX Highres - 8 Plane 4MPixel FB - V1.0 CACHE 16MB 0A,0B,0C,0D = 4MB, 1E,1F,1G,1H = 0MB SCSI 0-RZ24...
Page 102 System Console Commands, Continued Response Meaning 9 NI OK Ethernet 10 SCSI OK SCSI and drives 11 AUD OK Sound 12 COMM OK DSW21 communications device DEVICE The DEVICE parameter displays SCSI and Ethernet device information. The SET command does not apply to this parameter. Example: This example shows the information the SHOW DEVICE command displays.
Page 103 System Console Commands, Continued Response Meaning VMS/VMB The VMS device name, and console boot name for the device. ADDR Ethernet hardware address or SCSI device ID. The SCSI device ID has the format: A/DEVICE_ID/LOGICAL_ID The LOGICAL ID is always 0. DEVTYPE Device type, RODISK is a read-only disk (CDROM).
Page 104 System Console Commands, Continued DIAGENV The DIAGENV parameter determines the diagnostic environment that the diagnostics run under. Table 4–2 lists the diagnostic environments and their use. Table 4–2 Diagnostic Environments Mode Usage Customer No setup is required. Default mode on power-up. Digital Services Provides a more thorough test than in customer mode.
Page 105: Set Diagenv Command
System Console Commands, Continued Setting the To set the diagnostic environment, enter a console command listed Diagnostic in Table 4–3. Note that all settings except DIAGENV 1 require a loopback connector be installed. Environment Table 4–3 SET DIAGENV Command Command Result SET DIAGENV 1 Resets environment to customer mode.
Page 106 System Console Commands, Continued ERROR The ERROR parameter displays extended error information about any errors that occur during the last execution of: Initialization (power-up) test Extended test System test The SET command does not apply. Example: >>> SHOW ERROR ?? 150 10 SCSI 0032 150 000E 00000005 001D001D 03200000 00000024 (cont.) 00000002 00000000 00000004 The ESTAT parameter displays status information about the...
Page 107 System Console Commands, Continued ETHER The ETHER parameter displays the Ethernet hardware address. The SET command does not apply. Example: >>> SHOW ETHER ETHERNET = 08-00-2B-1B-48-E3 The FBOOT (fast boot) parameter determines whether the FBOOT memory is tested when power is turned on. The test time is reduced when main memory is not tested.
Page 108 System Console Commands, Continued HALT The HALT parameter determines the recovery action that the system takes after power-up, system crash, or halt. The following table lists the HALT parameter values and their meanings: Value Meaning System tries to restart the operating system. If restart fails, then the system tries to reboot.
Page 109 System Console Commands, Continued 0) Dansk 8) Francais (Suisse Romande) 1) Deutsch 9) Italiano 2) Deutsch (Schweiz) 10) Nederlands 3) English 11) Norsk 4) English (British/Irish) 12) Portugues 5) Espanol 13) Suomi 6) Francais 14) Svenska 7) Francais (Canadian) 15) Vlaams >>>...
Page 110 System Console Commands, Continued The MOP bit enables the NI (Ethernet) listener while the system is in console mode. The listener can send and receive messages on the network. The default mode is listener enabled (MOP = 1). Examples: >>> SET MOP 1 MOP = 00000001 >>>...
Page 111 System Console Commands, Continued Response Meaning PSDW0>>> xxxxxxxxxxxxxxxx Old password (only if a password has been previously set) PSWD1>>> 1234567890ABCDEF New password PSWD2>>> 1234567890ABCDEF Verify new password Example: >>> SET PSE 1 PSE = 1 NOTE After PSE is set to 1, type LOGIN at the >>> prompt, and type the password at the PSWD0>>>...
Page 112 System Console Commands, Continued TRIGGER The TRIGGER bit enables the entity-based module (EBM). With EBM and the NI listener enabled (TRIGGER = 1, MOP = 1) you can access the console or boot the system from a remote system. Examples: >>>...
Page 113: Deposit Command Qualiﬁers
System Console Commands, Continued Deposit The DEPOSIT command is used to write to memory locations from the console. Syntax: DEPOSIT /QUALIFIERS ADDRESS DATA Table 4–4 lists the DEPOSIT command qualiﬁers and what each one speciﬁes. Table 4–4 DEPOSIT Command Qualiﬁers Data size /B - Byte (8 bits) /W - Word (16 bits)
Page 114: Examine Command Qualiﬁers
System Console Commands, Continued >>> DEPOSIT/P/N:5 00100000 01234567 P 00100000 01234567 P 00100004 01234567 P 00100008 01234567 P 0010000C 01234567 P 00100010 01234567 P 00100014 01234567 EXAMINE The EXAMINE command displays speciﬁc memory locations from the console. Syntax: EXAMINE/QUALIFIERS ADDRESS Table 4–5 lists the qualiﬁers and what each one speciﬁes.
Page 115: Processor Control Commands
System Console Commands, Continued The ADDRESS speciﬁes the address (or ﬁrst address) to be read. Example: This example reads the Ethernet hardware address. >>> EXAMINE/P/N:5 20090000 P 20090000 0000FF08 P 20090004 0000FF00 P 20090008 0000FF2B P 2009000C 0000FF1B P 20090010 0000FF48 P 20090014 0000FFE3 Processor Table 4–6 lists the processor control commands and their...
Page 116: Boot Command Syntax
System Console Commands, Continued Boot The boot command starts the bootloader, which loads the operating system and starts it. The boot command causes the system to exit console mode and enter program mode. Table 4–7 lists boot commands and their meanings. Syntax: >>>...
Page 117 System Console Commands, Continued CONTINUE The CONTINUE command switches the system from console mode to program mode. The CPU starts running at the current program counter (PC). Example: >>> CONTINUE UNJAM and INITIALIZE The UNJAM command resets the system devices. The INITIALIZE command resets the processor registers.
Page 118 System Console Commands, Continued START The START command sets the program counter (PC) and starts the CPU. The command causes the system to exit console mode and enter program mode. Syntax: >>> START ADDRESS ADDRESS is the value loaded into the PC. Example: This example starts the bootloader.
Page 119: Alternate Consoles
Alternate Consoles Description The Model 90 provides two ways to use alternate consoles if the graphics subsystem fails. Console commands can be entered on a terminal connected to the printer/communications port, communications/printer (RS232) port, or from either Ethernet (standard, ThinWire) network port. The two alternate consoles are described in the following sections.
Page 120 Alternate Consoles, Continued The following VAXstation 4000 computer parameters must be set: — A console password — MOP, TRIGGER Once the Model 90 is set up, perform the following steps from the other VMS operating system to connect to the console: Log in to a user account (no special privileges are required).
Page 121 Alternate Consoles, Continued ! Floating point accelerator ! Interval timer ! Other system functions ! Ethernet SCSI ! SCSI and drives 0-RZ24 1-RZ25 2-RRD42 6-INITR ! Sound COMM ! DSW21 communications device Ctrl/D NCP> EXIT $ LO NOTE Do not run memory test; it causes the console to hang and you will have to power down the system.
Page 123: Diagnostic Testing
Chapter 5 Diagnostic Testing Overview This chapter describes the diagnostic testing and test commands In this Chapter that are used with the Model 90 system. It includes procedures for setting up the diagnostic environments, running self-tests and system tests, and invoking utilities. The following topics are included in this chapter: Diagnostic Functions System Power-Up Test...
Page 124 Overview, Continued Updating Firmware by Disk Troubleshooting For the troubleshooting process, it is assumed that problems are not caused by such things as faulty power cords or loose modules and connectors. Actual error codes and their meanings are provided in Appendix 5–2...
Page 125: Diagnostic Functions
Diagnostic Functions The system ﬁrmware provides the diagnostic functions listed in Table 5–1. Table 5–1 Diagnostic Functions Function Description Power-Up test Tests initialization and all devices. Extended self-test Tests devices in the system sequentially with the TEST command. System test Tests all devices in the system interactively.
Page 126: System Power-Up Test
System Power-Up Test The system power-up self-test sequentially tests the devices in the Overview system. This test takes about one minute to complete for a 16-MB base system. When the test successfully completes, the console prompt appears. Figure 5–1 shows the prompt. Factors increasing the test time are: Additional memory Maximum memory conﬁgurations take approximately seven...
Page 127: Successful Power-Up
System Power-Up Test, Continued At the end of the power-up sequence the system enters console mode, as indicated by the >>> prompt, if the HALT parameter is set to 3. If the HALT parameter is set to 1 or 2, the system tries to boot the default boot device.
Page 128: Unsuccessful Power-Up
System Power-Up Test, Continued Figure 5–2 Unsuccessful Power-Up KA49-A V1.0 08-00-2b-04-03-12 32MB ?? 001 10 SCSI 0034 >>> LJ-01825-TI0 Continued on next page 5–6...
Page 129 System Power-Up Test, Continued Error The general format for error information is: Information ?? Fru Dev_nbr Dev_nam Err_nbr Format Meaning Two question marks (??) indicate a fatal error; one question mark (?) indicates a non-fatal error. Identiﬁes the ﬁeld replaceable unit of the device that failed Dev_nbr The device number of the failing function...
Page 130: Displaying System Conﬁguration
Displaying System Conﬁguration The Model 90 ﬁrmware provides two conﬁguration commands, Conﬁguration Commands SHOW DEVICE and SHOW CONFIG. SHOW DEVICE determines what type of mass storage devices are included in the system. SHOW CONFIG determines the overall system conﬁguration. The SHOW DEVICE command determines the presence of storage SHOW DEVICE devices, such as a hard disk, diskette drives, or other drives.
Page 131 Displaying System Conﬁguration, Continued Column Meaning ADDR If the device is an Ethernet device, the ADDR column shows the Ethernet address. If the device is a system device, the ﬁrst character shown is the bus (A or B); the second character represents the device number (3, 5, 6);...
Page 132 Displaying System Conﬁguration, Continued Example: >>> SHOW CONFIG KA49-A V0.0-051-V4.0 08-00-2B-F3-31-03 16 MB DEVNBR DEVNAM INFO ------ ------ ---- LCSPX Highres - 8 Plane 4MPixel FB - V0.8 CACHE 16MB 0A,0B,0C,0D = 4MB, 1E,1F,1G,1H, = 0MB SCSI 0-RZ24 1-RZ25 2-RRD42 6-INITR COMM Response...
Page 133 Displaying System Conﬁguration, Continued Response Meaning Sound 11 AUD OK DSW21 Communications device 12 COMM OK To determine the quantity of memory in the system, note line 5, the MEM line, in the example. This line shows 4 Mbytes for each memory module in slots 0A, 0B, 0C, 0D.
Page 134: Displaying Additional Error Information
Displaying Additional Error Information Use the SHOW ERROR utility to obtain detailed error Overview information about any failing device. To determine if an error has occurred on a particular device, type SHOW ERROR followed by the device number. To show all of the system errors, type SHOW ERROR.
Page 135: Setting Up The Diagnostic Environment
Setting Up the Diagnostic Environment Procedure You must take the following actions before running a self-test: Step Action Comment Put the system in Shut down the operating system console mode. or power up the system if you do not have the console prompt. Attach loopbacks if See Table 5–4.
Page 136: Set Diagenv Command
Setting Up the Diagnostic Environment, Continued Setting the To set the diagnostic environment, enter one of the console Diagnostic commands listed in Table 5–3. Note that all diagnostic environments except DIAGENV 1 require a loopback connector. Environment Table 5–3 SET DIAGENV Command Command Result SET DIAGENV 1...
Page 137: Device Tests
Device Tests Device Test Table 5–4 lists the device tests and corresponding mnemonics, IDs and decimal ID, binary ID, and loopback requirements. Mnemonics Table 5–4 Device Test IDs and Mnemonics Decimal Binary Loop Device Mnemonic back Non-Volatile RAM 0001 2D or Other graphics LCSPX or 0010 Serial line controller...
Page 138 Device Tests, Continued Running This section describes the test command interface used to run Self-Tests the self-test on a device. Table 5–4 lists the device IDs and mnemonics. Device Test Table 5–5 describes the syntax used to run device self-tests. Syntax Rules Table 5–5 Device Test Syntax Rules If you want to...
Page 139: Successful And Unsuccessful Self-Test
Device Tests, Continued To test a range of devices, separate the device numbers being tested by a colon (:). To separate individual tests or ranges of devices, use a comma or a space. Example: This example tests devices 8 through 10 device 6, then devices 3 through 5.
Page 140: Multiple Device Tests
Device Tests, Continued Devices can be speciﬁed individually, or as a range using the conventions listed in Table 5–5. The following table describes the order of execution for multiple device tests: Table 5–6 Multiple Device Tests Example Description T 10:8,6,5:3 Tests devices 10 through 8, then device 6, and then devices 5 through 3.
Page 141: Self-Test Descriptions
Self-Test Descriptions This section describes the following self-tests. The test IDs and mnemonics are listed in Table 5–4. TOY/NVR LCSPX/SPXg/gt SCSI DMA RAM, OBIT RAM, BCACHE Memory Floating Point Unit System Network Interconnect SCSI Audio Synchronous Communication TURBOchannel NOTE The self-tests are described in order by the decimal ID, contained in parentheses after the text name.
Page 142 Self-Test Descriptions, Continued Checks the NVR for valid data. If the NVR is not initialized, a register test is performed on all of the NVR locations and the NVR is initialized. If the NVR is initialized, only the temporary locations are tested in the NVR. TOY Test Checks to see if time has been set in the TOY.
Page 143 Self-Test Descriptions, Continued DZ Self-Test (T The DZ self-test tests the serial line controller. Setup Notes The DZ Interrupt test fails in the Digital Services or manufacturing environments if no external loopbacks are present on the communication port. The mouse test fails if the mouse is not plugged in and the console is a video device.
Page 144 Self-Test Descriptions, Continued LK401 Test Checks for the presence of an LK401 when the console device is a video device. Mouse test Checks for the presence of a mouse when the console device is a video device. This is the cache system self-test. SCSI DMA RAM, OBIT The following tests are included:...
Page 145 Self-Test Descriptions, Continued The following tests are included: Byte Mask test Checks the byte mask signals that are generated by the CPU. This test is performed on each page boundary. Once the test is complete, all free memory is ﬁlled with AAh. Memory test (forward) Performs a read/compare/complement/write on the memory in the forward direction.
Page 146 Self-Test Descriptions, Continued Interval Timer The following test is included: Self-Test (T 7) Interrupt test Enables the interval timer interrupts. It lowers the IPL for 30 ms and counts the number of interrupts. If there are too few or too many interrupts, an error occurs. System The following test is included: Self-Test (T 8)
Page 147 Self-Test Descriptions, Continued Sets up the SGEC data structures and initializes the SGEC chip, which causes the SGEC to perform a single word DMA read to the system memory. SGEC Internal Loopback test Veriﬁes the correct operation of the SGEC transmitter and receiver during an internal loopback.
Page 148 Self-Test Descriptions, Continued SCSI Self-Test The SCSI self-test is for the SCSI controller. (T 10) Setup Notes CDROM devices fail in extended mode if media is not installed in removable media drives. If some or all devices do not show up in the conﬁguration display after running the test, ensure that all devices have a unique ID number.
Page 149 Self-Test Descriptions, Continued The following tests are included: Register test Veriﬁes that the 53C94A Controller Chip registers are fully functional. All read/write bits that can be written are written to. It also veriﬁes the bits. Interrupt test Veriﬁes the SCSI bits in the interrupt mask register, interrupt request register, and the interrupt clear register.
Page 150 Self-Test Descriptions, Continued Audio Self-Test The audio self-test tests the sound chip. (T 11) The following tests are included: Register test Performs a write/read to registers in the 79C30 DSC chip. Interrupt test Enables interrupts, sends and receives an 8-byte packet by way of internal loopback.
Page 151: Turbochannel Adapter Self-Test
Self-Test Descriptions, Continued EPROM test Checks the EPROM dual access; EPROM bus arbitration. Host Interrupt test Checks the host interrupt; veriﬁes option can interrupt the CPU. Host Loopback test Checks the host buffer loopback and interrupt; moves data from the CPU to the communication option, loops it back and waits for an interrupt.
Page 152 Self-Test Descriptions, Continued Table 5–7 (Continued) TURBOchannel Adapter Self-Test (13) Self-Test Function TCA Interrupt Generates an interrupt. Tests to see if the Interrupt Service Routine (ISR) can be reached and then turns off interrupts and makes sure that the ISR is not reached. TCA FIFO Loads up the TCA FIFO at longwords with an increasing value, starting at 1 and ending with 512.
Page 153: System Test Environment Conﬁguration
System Test Environment Conﬁguration The system test is a strenuous test of the workstation. All devices Overview are exercised simultaneously to ﬁnd system interaction problems. The system test can be used to ﬁnd faults that only occur when the system interaction is high. The system test can be run in three environments, which you select with the SET DIAGENV command.
Page 154: System Test Monitor
System Test Monitor Running the This section describes the test command interface to use to run System Test the system test on a device or on the whole system. Table 5–8 shows the general format for running the system test with the test command.
Page 155: Successful System Test
System Test Monitor, Continued This example runs two passes of the system test in customer mode. >>>T 100 This example runs the system test for speciﬁc devices. The system prompts you for a speciﬁc device; 1 = yes; 0 = no. >>>T 106 Display from Figure 5–4 shows the response to a successful system test.
Page 156: Unsuccessful System Test
System Test Monitor, Continued Response Meaning KA49-A The system module ID. V1.0 The ROM version number. The environment in which the test is running. 00 00:02:00.03 The CPU time used during testing. Figure 5–5 shows the system response when the system test is unsuccessful.
Page 157 System Test Monitor, Continued When a device fails, the device status line in the response becomes the error message. You can get extended error information using the SHOW ERROR command. Interpretation of the error code is explained in Appendix A. System Test You can get summary information about the most recent system test using either of the following two methods:...
Page 158 System Test Monitor, Continued Each system diagnostic is also able to display extended status and error information on its own summary screen. Figure 5–6 shows an example of the summary screen with a SCSI failure. Figure 5–6 Summary Screen 10 SCSI 000101 000125 00 00:01:56:01 targ devnam wrts...
Page 159 System Test Monitor, Continued Burst Mode - Performs in the same way as functional mode except the lines are tested at 19.2K baud, 8-bit characters, and parity is odd. The following is a example of the DZ System test error. This error code means that not all characters were received on line 1 and line 2.
Page 160 System Test Monitor, Continued Network This section explains the Network Interconnect (NI) System test. Interconnect Setup Notes System Test The selected NI port must be connected to a network, or have a loopback installed. A more thorough test is done if the system is connected to a live network and MOP is enabled.
Page 161 System Test Monitor, Continued SCSI System This section describes the SCSI system test. Test CAUTION Do not use manufacturing mode in the ﬁeld. This erases customer data on hard disks, excluding the system disk. Setup Notes If some or all devices are not in the summary screen after running the system test, verify that all devices have unique ID numbers.
Page 162 System Test Monitor, Continued The following tests are included: Inquiries test Performs inquiries to ﬁnd out which devices are connected to the SCSI bus. Size Bus test Spins up all the hard disk drives, ensures that the drives are ready (if not in customer mode), forces disk block sizes to 600 bytes, and obtains the capacity of the drives.
Page 163 System Test Monitor, Continued Examples: The following is an example of a successful SCSI system test message: 10 SCSI ################## 4 The following example shows an unsuccessful (error) SCSI system test message. The error is on ID 5. ?? 10 SCSI 150 0076 8:18:41 The following is an example of the SCSI system test summary message: WRTS...
Page 164 System Test Monitor, Continued In order for writes to occur, a key pattern must be installed on writeable removable media (ﬂoppies and tapes). The key pattern is put on the media by the SCSI utilities. This is described in SCSI Utilities. DSW21 The system test loads and runs 68302 test/scheduler.
Page 165: Utilities
Utilities TEST commands run or display available utilities. Utilities can Overview either be run with all parameters input at the command line or the utilities prompt for additional input. The format for a utility test that runs completely from the command line is shown next. >>>...
Page 166 Utilities, Continued Step Action Comment Enter T/UTIL 2 The LCSPX main utility routine displays a list of the available utilities (as shown in Figure 5–7) and then displays the prompt SPX_util>>>. Enter the utility In Figure 5–7, utility 8 is number that you want selected.
Page 167: Utilities List
Utilities, Continued Figure 5–7 Utilities List >>> T/UT 2 0 - SPX-wh-scrn 1 - SPX-rd-scrn 2 - SPX-bl-scrn 3 - SPX-gn-scrn 4 - SPX-4c-cbar 5 - SPX-8c-cbar 6 - SPX-8g-gscl 7 - SPX-ee-scrn 8 - SPX-ci-xhct 9 - SPX-sc-hhhs A - SPX-wh-half B - SPX-rd-half C - SPX-gn-half D - SPX-bl-half...
Page 168 Utilities, Continued The console ﬁrmware provides the following utilities: Utility Group Functions LCSPX/SPXg/gt (2) Provides colored screens and geometric patterns. Use the SET and SHOW commands for: MOP - NI listener Trigger - Entity-Based Module (EBM) SCSI (10) Key utilities, ﬂoppy formatter, and disk eraser TCA (13) TURBOchannel conﬁguration display...
Page 169 Utilities, Continued The following is an example of the LCSPX utility menu. An LCSPX Utility Menu explanation of the items is included to the right of the menu. See Figure 5–7. 0 - SPX-wh-scrn !White screen 1 - SPX-rd-scrn !Red screen 2 - SPX-bl-scrn !Blue screen 3 - SPX-gr-scrn...
Page 170 Utilities, Continued NI Utility The NI utility is invoked by the SET or SHOW commands, not by the TEST/UTIL command. The NI utility functions are: SET/SHOW MOP - Enable/Disable NI listener SET/SHOW TRIGGER - Enable/Disable EBM NI Listener The NI listener can send and receive messages while the system is in console mode.
Page 171 Utilities, Continued SCSI Utilities The SCSI utilities are described in the next table. Table 5–9 SCSI Utilities Utility Function SHOW DEVICE This is a console command that displays information about the Ethernet controller and the SCSI drives attached to the system. Floppy Key This utility is used in Digital Services mode.
Page 172: Invoking Scsi Utilities
Utilities, Continued Invoking SCSI The next table describes how to invoke the SCSI utilities. Utilities Table 5–10 Invoking SCSI Utilities Step Action Result Enter the T/UT Displays the SCSI Utility Menu. SCSI command. Enter the utility Selects the utility. number. Enter the SCSI Selects the drive.
Page 173: Scsi Utility Response
Utilities, Continued Command Comment T/UT 10 Enter this command (or T/UT SCSI) 1 - SCSI-ﬂp_key Floppy key utility. 2 - SCSI-tp_key Tape key utility. 3 - SCSI-hd_dis_eras Hard disk erase. 4 - SCSI-ﬂp_fmt Floppy formatter. SCSI_util>>> 3 Enter the utility number. SCSI_id(0-7)>>>...
Page 174 Utilities, Continued SCSI Utility Follow these guidelines about the SCSI utilities: Notes Never run a SCSI utility on the Host ID (ID = 6). An error mnemonic of SCSI_E_type indicates you cannot perform the utility on the speciﬁed device, for example, running the tape key utility on a ﬁxed disk.
Page 175: Mips/Rex Emulator
MIPS/REX Emulator Invoking the Enter the following command to invoke the MIPS/REX emulator: Emulator >>> T/UT TCA The system responds with the following message: **KA49 TURBOCHANNEL REX EMULATOR** >> Available Enter the following command for a list of available script Option Script functions: Functions...
Page 176 MIPS/REX Emulator, Continued Option Enter the following command for self-test availability: Self-Tests >>T TC0/? flash eprom sram rmap phycsr nirom intlpbk iplsaf pmccsr pktmem >>> Invoking The command syntax you use to invoke an individual option the Option self-test is as follows: Self-Test Syntax: >>...
Page 177 MIPS/REX Emulator, Continued Option Error The following is an example of an emulator self-test error Message message. Example Example: >> t tc0 flash 10 *emul: t tc0 flash 10 ERR-MIPS - ROM OBJECT REPORTED A SEVERE ERROR >> NOTE Consult the option ﬁrmware speciﬁcations if you receive an error message that is dependent on the device.
Page 178: Product Fault Management
Product Fault Management This section describes how errors are handled by the microcode Overview and software, how the errors are logged, and how, through the symptom-directed diagnosis (SDD) tool, VAXsimPLUS, errors are brought to the attention of the user. This section also provides the service theory used to interpret error logs to isolate the FRU.
Page 179 Product Fault Management, Continued these errors do not result in a machine check exception or high level interrupt (results in device level IPL 14–17 versus error level IPL 1A, 1D), the VMS machine check handler has a polling routine that searches for this state at one second intervals. This results in the host logging a polled error entry.
Page 180 Product Fault Management, Continued Determine if the threshold has been exceeded for various errors (typically the threshold is exceeded if three errors occur within a 10 minute interval). If the threshold has been exceeded for a particular type of cache error, mark a ﬂag that signiﬁes that this resource is to be disabled (the cache will be disabled in most, but not all, cases).
Page 181 Product Fault Management, Continued Crash process or system, dependent upon PSL (current mode) with a fatal bugcheck for the following situations: — Retry is not possible. — Memory page could not be replaced for uncorrectable ECC memory error. — Uncorrectable tag store ECC errors present in Bcache. —...
Page 182: Vms Error Handler Entry Types
Product Fault Management, Continued NOTE The results of the VMS error handler may be preserved within the operating system session (for example, disabling a cache) but not across reboots. Although the system can recover with cache disabled, the system performance is degraded because access time increases as available cache decreases.
Page 183: Event Log Entry Format
Product Fault Management, Continued Each entry consists of a VMS header, a packet header, and one or more subpackets (Figure 5–9). Entries can be of variable length based on the number of subpackets within the entry. The FLAGS software register in the packet header shows which subpackets are included within a given entry.
Page 184: Machine Check Stack Frame Subpacket
Product Fault Management, Continued Machine Check Machine check exception entries contain, at a minimum, a Exception machine check stack frame subpacket (Figure 5–10). Entries Figure 5–10 Machine Check Stack Frame Subpacket 00000018 (hex) byte count (not including this longword, PC or PSL) Machine xxxxxx Check Code...
Page 185 Product Fault Management, Continued Processor INT54, INT60, polled, and some machine check entries contain a Register processor register subpacket (Figure 5–11), which consists of some Subpacket 40-plus hardware registers. Figure 5–11 Processor Register Subpacket BPCR (IPR D4) MMEADR (IPR E8) PAMODE (IPR E7) VMAR...
Page 186: Memory Subpacket For Ecc Memory Errors
Product Fault Management, Continued Bugcheck Bugcheck entries generated by the VMS kernel error handler Entries include the ﬁrst 23 registers from the Processor register subpacket along with the Time-of-Day register (TODR) and other software context state. Uncorrectable ECC memory error entries include a memory Uncorrect ECC subpacket (Figure 5–12).
Page 187: Memory Sbe Reduction Subpacket (Correctable Memory Errors)
Product Fault Management, Continued Correctable Correctable memory error entries have a memory (single-bit error) Memory Error SBE reduction subpacket (Figure 5–13). This subpacket, unlike all others, is of variable length. It consists solely of software Entries registers from state maintained by the error handler, as well as hardware state transformed into a more usable format.
Page 188: Correctable Read Data Entry Subpacket Header
Product Fault Management, Continued Figure 5–14 Correctable Read Data Entry Subpacket Header Logging Reason Page Mapout CNT MEMCON Valid Entry CNT Current Entry MLO-007268 Following the subpacket header are one to 16 ﬁxed-length memory CRD entries (Figure 5–15). The number of memory CRD entries is shown in VALID ENTRY CNT.
Page 189 Product Fault Management, Continued Each memory CRD entry represents one unique DRAM within the memory subsystem. A unique set, bank, and syndrome are stored in footprint to construct a unique ID for the DRAM. Rather than logging an error for each occurrence of a single symbol correctable ECC memory error, the VMS error handler maintains the CRD buffer;...
Page 190 Product Fault Management, Continued If the FOOTPRINT/DRAM experiences another error (CRD CNT > 1), VMS sets HARD SINGLE ADDRESS or MULTIPLE ADDRESSES along with SCRUBBED in STATUS. Scrubbing is no longer performed; instead, pages are marked bad. In this case, VMS logs the CRD buffer immediately.
Page 191 Product Fault Management, Continued As in this example, the VMS error handler also provides support for the /INCLUDE qualiﬁer, such that CPU and MEMORY error entries can be selectively translated. Since most kernel errors are bounded to either the processor module/system board or memory modules, the individual error ﬂags and ﬁelds are not covered by the service theory.
Page 192 Product Fault Management, Continued Interpreting If the following two conditions are satisﬁed, the most likely FRU is the CPU module. Faults Using No memory subpacket is listed in the third column of the ANALYZE/ERROR FLAGS register. NCA_CESR register bit <09>, CP2 IO error, is equal to zero in the KA49 register subpacket.
Page 193 Product Fault Management, Continued V A X / V M S SYSTEM ERROR REPORT COMPILED 14-JAN-1992 18:55:52 PAGE ******************************* ENTRY 1. **************************** ERROR SEQUENCE 11. LOGGED ON: SID 13000202 DATE/TIME 27-SEP-1991 14:40:10.85 SYS_TYPE 01390601 SYSTEM UPTIME: 0 DAYS 00:12:12 SCS NODE: COUGAR VAX/VMS V5.5-1 MACHINE CHECK KA49-A...
Page 194 Product Fault Management, Continued NOTE Ownership (O-bit) memory correctable or fatal errors (MESR <04> or MESR <03> of the Processor register subpacket set equal to 1 are processor module errors, NOT memory errors. Next is an example showing the system respone to using the SHOW ERROR command using VMS.
Page 195 Product Fault Management, Continued NOTE Although the VMS error handler has built-in features to aid services in memory repair, good judgment is needed by the Service Engineer. It is essential to understand that in many, if not most cases, correctable ECC errors are transient in nature.
Page 196 Product Fault Management, Continued errors. The FOOTPRINT longword for this entry contains the message ‘‘Uncorrectable ECC errors due to disown write’’. The failing module should be replaced for this error. V A X / V M S SYSTEM ERROR REPORT COMPILED 6-NOV-1991 10:16:49 PAGE...
Page 197 Product Fault Management, Continued MEMCON 00010101 MEMORY CONFIGURATION: MS44-AA Simm Memory Module (4MB) Loc 0A MS44-AA Simm Memory Module (4MB) Loc 0B MS44-AA Simm Memory Module (4MB) Loc 0C MS44-AA Simm Memory Module (4MB) Loc 0D _Total memory = 16MB _sets enabled = 00000001 MEMORY ERROR STATUS: SIMM MEMORY MODULES: LOCATIONS 0A...
Page 198 Product Fault Management, Continued In the next example, 5ffb8 (under the page frame number [PFN] column) is identiﬁed as the single page that has been replaced. The command EVAL 5ffb8 * 200 converts the PFN to a physical page address. The result is 0bff7000. (Bits <8:0> of the addresses may differ since the page address from EVAL always shows bits <8:0>...
Page 199 Product Fault Management, Continued Look for the following: SCRUBBED If SCRUBBED is the only bit set in the STATUS register, memory modules should not generally be replaced. The kernel performs memory scrubbing of DRAM memory cells that may ﬂip due to transient alpha particles. Scrubbing reads the corrected data and writes it back to the memory location.
Page 200 Product Fault Management, Continued NOTE Under VMS, the page mapout threshold is calculated automatically. If "PAGE MAPOUT THRESHOLD EXCEEDED" is set in SYSTAT, the failing memory module should be replaced. In cases of a new memory module used for repair or as part of system installation, you can elect to replace the module rather than have diagnostics map them out, even if the threshold has not been reached for hard single-address...
Page 201 Product Fault Management, Continued NOTE If footprints are being generated for more than one memory module, especially if they all have the same bit in error, the processor module, backplane, or other component could be the cause. NOTE An uncorrectable ECC error due to a ‘‘disown write’’, results in a CRD entry similar to those for correctable ECC errors.
Page 202 Product Fault Management, Continued MEMORY CRD ENTRY 1. FOOTPRINT 0000003D MEMORY ERROR STATUS: _SIMM MEMORY MODULE: LOCATION _set = 0. Bank = B VALID ENTRY CNT 00000001 CURRENT ENTRY 00000001 MEMORY CRD ENTRY 1. FOOTPRINT 0000003D MEMORY ERROR STATUS: _SIMM MEMORY MODULE: LOCATION _set = 0.
Page 203 Product Fault Management, Continued logged by the host, and one or more device attention and other assorted entries logged by the device drivers. In these cases the processor module or one of the four memory modules are the most likely cause of the errors. Therefore, it is essential to analyze polled error entries, since a polled entry usually represents the source of the error versus other entries, which are aftereffects of the original error.
Page 204 Product Fault Management, Continued MEMCON 00010101 MEMORY CONFIGURATION: MS44-AA Simm Memory Module (4MB) Loc 0A MS44-AA Simm Memory Module (4MB) Loc 0B MS44-AA Simm Memory Module (4MB) Loc 0C MS44-AA Simm Memory Module (4MB) Loc 0D _Total memory = 16MB _sets enabled = 00000001 MEMORY ERROR STATUS: SIMM MEMORY MODULES: LOCATIONS...
Page 205 Product Fault Management, Continued 00000000 00000000 ARB FAIL CNT = 0. SEL FAIL CNT = 0. PARITY ERR CNT = 0. PHASE ERR CNT = 0. BUS RESET CNT = 0. BUS ERROR CNT = 0. CONTROLLER ERROR CNT = 0. SCSI RETRY CNT 00000000 0000...
Page 206: Using Mop Ethernet Functions
Using MOP Ethernet Functions The console requester can receive LOOPED_DATA messages from Console Requester the server by sending out a LOOP_DATA message using NCP to set this up. Examples: Identify the Ethernet adapter address for the system under test (system 1) and attempt to boot over the network. ***system 1 (system under test)*** >>>SHOW ETHERNET Ethernet Adapter...
Page 207 Using MOP Ethernet Functions, Continued Identify the system’s Ethernet circuit and circuit state, enter the SHOW KNOWN CIRCUITS command from the system conducting the test (system 2). ***system 2 (system conducting test)*** $ MCR NCP NCP>SHOW KNOWN CIRCUITS Known Circuit Volatile Summary as of 14-NOV-1991 16:01:53 Circuit State Loopback...
Page 208 Using MOP Ethernet Functions, Continued NCP>LOOP CIRCUIT ISA-0 PHYSICAL ADDRESS 08-00-2b-28-18-2C ASSISTANT PHYSICAL ADDRESS 08-00-2B-1E-76-9E WITH MIXED COUNT 20 LENGTH 200 HELP FULL NCP> Instead of using the physical address, you could use the assistant node’s area address. When using the area address, system 3 is running VMS.
Page 209 Using MOP Ethernet Functions, Continued ***system 2*** $ MCR NCP NCP>SET MODULE CONFIGURATOR CIRCUIT ISA-0 SURVEILLANCE ENABLED NCP>SHOW MODULE CONFIGURATOR KNOWN CIRCUITS STATUS TO ETHER.LIS NCP>EXIT $ TYPE ETHER.LIS Circuit name = ISA-0 Surveillance flag = enabled Elapsed time = 00:09:37 Physical address = 08-00-2B-28-18-2C Time of last report...
Page 210: User Environmental Test Package
User Environmental Test Package When the user environmental test package (UETP) encounters Overview an error, it reacts like a user program. It either returns an error message and continues, or it reports a fatal error and terminates the image or phase. In either case, UETP assumes the hardware is operating properly and it does not attempt to diagnose the error.
Page 211 User Environmental Test Package, Continued UETP Log Files UETP stores all information generated by all UETP tests and phases from its current run in one or more UETP.LOG ﬁles, and it stores the information from the previous run in one or more OLDUETP.LOG ﬁles.
Page 212 User Environmental Test Package, Continued Possible UETP This section lists some problems you might encounter while Errors running UETP. The following are the most common failures encountered while running UETP: Wrong quotas, privileges, or account UETINIT01 failure Ethernet device allocated or in use by another application Insufﬁcient disk space Incorrect VAXcluster setup Problems during the load test...
Page 213: Feprom Firmware Update
FEPROM Firmware Update KA49 ﬁrmware is located on four chips, each 128 KB by 8 bits of Overview FLASH programmable EPROMs, for a total of 512 KB of ROM. (A FLASH EPROM [FEPROM] is a programmable read-only memory that uses electrical [bulk] erasure rather than ultraviolet erasure.) FEPROMs provide nonvolatile storage of the CPU power-up diagnostics, console interface, and operating system primary bootstrap (VMB).
Page 214: Firmware Update Utility Layout
FEPROM Firmware Update, Continued A ﬁrmware update utility image consists of two parts: the update program and the new ﬁrmware, as shown in Figure 5–16. The update program uniformly programs, erases, reprograms, and veriﬁes the entire FEPROM. Figure 5–16 Firmware Update Utility Layout Update Program New Firmware Image MLO-007271...
Page 215 FEPROM Firmware Update, Continued Updating To update ﬁrmware across the Ethernet, the ‘‘client’’ system (the Firmware by target system to be updated) and the ‘‘server’’ system (the system Ethernet that serves boot requests) must be on the same Ethernet segment. The maintenance operation protocol (MOP) is the transport used to copy the network image.
Page 216 FEPROM Firmware Update, Continued Step Action Comment On the client system, The system then prompts you for enter the command the ﬁle name. BOOT/100 EZ at the NOTE Do not type the .SYS console prompt (>>>). ﬁle extension when entering the Ethernet bootﬁle name.
Page 217 FEPROM Firmware Update, Continued ***** On Server System ***** $ MCR NCP NCP>SET CIRCUIT ISA-0 STATE OFF NCP>SET CIRCUIT ISA-0 SERVICE ENABLED NCP>SET CIRCUIT ISA-0 STATE ON NCP>EXIT $ COPY KA680_V41_EZ.SYS MOM$LOAD:*.* ***** On Client System ***** >>> BOOT/100 EZA0 (BOOT/R5:100 EZA0) Bootfile: K680_V41_EZ >>>...
Page 218 FEPROM Firmware Update, Continued Updating This table describes how to update ﬁrmware on disk. Firmware on Disk Step Action Create a top level directory on the disk. CREATE/DIR DKA100:[FIRMWARE] Copy the ﬁrmware update savesets to the directory. Use the following command: $ COPY <filename>:[FIRMWARE]*.* On the client system, enter this command at the console prompt:...
Page 219 FEPROM Firmware Update, Continued Example 5–1 FEPROM Update by Disk >>> b/100 dka100 Bootfile: [firmware]bl9.sys -DKA100 FEPROM BLASTING PROGRAM ---CAUTION--- EXECUTING THIS PROGRAM WILL CHANGE YOUR CURRENT ROM --- Do you really want to continue [Y/N] ? : Y DO NOT ATTEMPT TO INTERRUPT PROGRAM EXECUTION! DOING SO WILL RESULT IN LOSS OF OPERABLE STATE! The program will take at most several minutes.
Page 220: Updating Firmware On Tape
Updating Firmware On Tape To update ﬁrmware on tape, the system must have a TZ30 tape Overview drive. If you need to make a bootable tape, copy the bootable image ﬁle to a tape as shown in the following example. Refer to the release notes for the name of the ﬁle.
Page 221 Updating Firmware On Tape, Continued Step Action Comment After the FEPROM upgrade program is CAUTION loaded, press Y at the Once you enter the bootﬁle prompt to start the name, do not interrupt the FEPROM blast. FEPROM blasting program, as this can damage the CPU module.
Page 222 Updating Firmware On Tape, Continued >>> BOOT MKA500 Bootfile: KA49_V41_EZ -MKA500 1..0.. FEPROM BLASTING PROGRAM blasting in V4.1... ---CAUTION--- EXECUTING THIS PROGRAM WILL CHANGE YOUR CURRENT ROM --- Do you really want to continue [Y/N] ? : Y DO NOT ATTEMPT TO INTERRUPT PROGRAM EXECUTION! DOING SO MAY RESULT IN LOSS OF OPERABLE STATE! The program will take at most several minutes.
Page 223 Updating Firmware On Tape, Continued FEPROM The next table lists the error messages generated by the FEPROM Update Error update program and the actions to take if the errors occur. Messages Message Action update enable jumper is Reposition update enable jumper (Preparing the disconnected Processor for an FEPROM Update).
Page 224 Updating Firmware On Tape, Continued Patchable The next table lists the error messages that may appear if there Control Store is a problem with the PCS. The PCS is loaded as part of the Loading Error power-up stream (before ROM-based diagnostics are executed). Messages Message Comment...
Page 225: Frus Removal And Replacement
Chapter 6 FRUs Removal and Replacement Overview Introduction This chapter describes how to remove and replace the ﬁeld replaceable units (FRUs) in the Model 90 system box. Appendix D lists the Model 90 FRUs and their part numbers. Each section describes the removal procedure for the FRU. Unless otherwise speciﬁed, you can install a FRU by reversing the steps in the removal procedure.
Page 226: Precautions
Precautions Removing and Only qualiﬁed service personnel should remove or install FRUs. Installing FRUs NOTE It is the customer’s responsibility to back up the software before Digital Services personnel arrive at the site. This is important to ensure that data is not lost during the service process.
Page 227: System Fru Removal
System FRU Removal Perform these preliminary steps before removing and replacing a Before Starting FRU. Step Action Verify that the symptom is not caused by improper conﬁguration or a loose cable. Conﬁrm with the customer that data has been backed up.
Page 228 System FRU Removal, Continued System FRU Figure 6–1 shows the location of the system FRUs. Locations Figure 6–1 System FRU Locations 5 4 2 0 8 5 4 - 0 2 2 4 - P L A N E 7 0 2 8 1 0 7 - 0 1 F R A M E B U F F E R C O V E R A S S E M B L Y 5 4 2 0 4 5 4 - 0 1...
Page 229: System Preparation
System Preparation Prepare the Prepare the system for removing or replacing FRUs by following System these next steps. Shut down the operating system. Enter console mode by pressing the halt button (Figure 6–2) on the front of the system box behind the door on the lower right.
Page 230 System Preparation, Continued NOTE After adding the new device or module, halt the system when you ﬁrst turn it on. Use the diagnostic tests described in Chapter 5 to determine if the new device or module is connected correctly. Before adding a new device or module, review the current system conﬁguration.
Page 231 System Preparation, Continued To determine the quantity of memory in the system, look at the MEM line. The memory line (line 5) shows that there is 80 MB of system memory. There are 4-MB memory modules in each of 0A, 0B, 0C, 0D and 16-MB memory modules in each of 1E, 1F, 1G, 1H.
Page 232: Mass Storage Drive Removal
Mass Storage Drive Removal This section describes how to remove mass storage devices from Overview the VAXstation 4000 Model 90 workstation. Mass storage devices installed in the system share the same SCSI and dc power cable. Each device has its own connector on the power cable.
Page 233 Mass Storage Drive Removal, Continued Step Action Comment Lift the drive from the bracket. Match the SCSI ID Figure 6–3 and Figure 6–4 with the error code to show the disk drive ID jumper verify that the failed locations. Table 6–1 contains drive was removed.
Page 234: Rz23L Disk Drive Scsi Id Jumper Location
Mass Storage Drive Removal, Continued Step Action Comment Set the SCSI ID The jumpers are used in the jumpers of the top following manner: disk drive as speciﬁed Install the jumper for IN in Table 6–1. Remove the jumper for Install a new drive by Note: When installing a drive reversing the steps in...
Page 235: Rz24 Disk Drive Scsi Id Jumper Location
Mass Storage Drive Removal, Continued Figure 6–4 RZ24 Disk Drive SCSI ID Jumper Location 50-Pin SCSI SCSI ID Signal Terminator Jumpers Connector Packs Connector to Power HDA Module Connector LJ-00622-TI0 Continued on next page 6–11...
Page 236: Rz25 Disk Drive Scsi Id Jumper Location
Mass Storage Drive Removal, Continued Figure 6–5 RZ25 Disk Drive SCSI ID Jumper Location MLO-005323 Continued on next page 6–12...
Page 237: Hard Disk Drive Scsi Jumper Settings
Mass Storage Drive Removal, Continued The following table lists the hard disk drive SCSI jumper settings. Table 6–1 Hard Disk Drive SCSI Jumper Settings SCSI ID Comment Out Out Out Out Out Out In Out Out In Out In Out In Usually reserved for SCSI controller The following table lists the standard ID numbers for the SCSI devices.
Page 238 Mass Storage Drive Removal, Continued This section describes how to remove an RRD42 CDROM drive. RRD42 CDROM Drive Removal Figure 6–1 shows the RRD42 CDROM drive. Step Action Remove the hard disk drive. Push the colored tab at the right upper front of the bracket toward the power supply, and push the tab behind the screw hole at the bottom left center of the bracket to the right.
Page 239: Rrd42 Cdrom Jumper Settings
Mass Storage Drive Removal, Continued Step Action The SCSI ID jumpers should be in the factory-set positions for SCSI ID 4. This is the default SCSI ID setting for the drive. Verify that the jumpers are set to the following positions (left to right) for SCSI ID 4: OFF, OFF, ON.
Page 240 Mass Storage Drive Removal, Continued Installing a To install a new drive, reverse the steps in RRD42 CDROM Drive New Drive Removal. You do not need to push the tabs to insert the bracket. The bracket snaps into place if positioned correctly. RX26 (Diskette) This section describes how to remove the RX26 diskette drive.
Page 241: Rx26 Diskette Type Number
Mass Storage Drive Removal, Continued Use the following procedure to verify or set the drive type number switches and the SCSI ID settings. Step Action Locate the type number switches 0, 1, and 2 on the drive, as shown in Figure 6–7. Use a pen or small pointed object to move the switches side to side.
Page 242: Rx26 (Diskette) Drive Scsi Id Switch Location
Mass Storage Drive Removal, Continued Figure 6–8 RX26 (Diskette) Drive SCSI ID Switch Location Switches Positions: SCSI ID 5 Up (Off) Down (On) 1 2 3 MLO-002886 This section describes how to remove a TZK10 QIC tape drive. TZK10 QIC Figure 6–1 shows the drive location.
Page 243 Mass Storage Drive Removal, Continued TZK10 Before installing the new drive, verify the drive ID setting. (Tape) Drive Figure 6–9 shows the drive SCSI ID switch locations for the tape Replacement drive. Use the following procedure to verify or set the drive SCSI ID jumpers.
Page 244: Tzk10 (Qic) Tape Drive Scsi Id Jumper Location
Mass Storage Drive Removal, Continued Installing a To install a new drive, reverse the steps in the TZK10 QIC Tape New Drive Drive Removal procedure. You do not need to push the tabs to insert the bracket. The bracket snaps into place if positioned properly.
Page 245: Power Supply Removal
Power Supply Removal Removing the This section describes how to remove the system power supply Power Supply (H7819-AA) from the system box. Figure 6–1 shows the system power supply. NOTE Refer to System Preparation before removing or replacing a device or module. WARNING Do not attempt to open the power supply.
Page 246 Power Supply Removal, Continued Power Supply To install a new power supply, reverse the steps in the Power Replacement Supply Removal procedure. You do not need to pull the tab. When replacing the power supply, ensure that you also do the following: Install an H7819-AA power supply.
Page 247: Module Removal
Module Removal The following sections describe how to remove and replace the Overview VAXstation 4000 Model 90 system modules. NOTE Refer to System Preparation before removing or replacing a device or module. CAUTION Wear an anti-static wrist strap and place modules on an anti-static mat when removing and replacing system modules.
Page 248 Module Removal, Continued Light and To replace the light and switches module, perform the following Switches steps: Module Replacement Step Action Align the switches with their respective holes in the front bezel. Align the connector on the lower side of the module with the connector on the system module and seat the connector.
Page 249 Module Removal, Continued Figure 6–10 Memory Module Identiﬁcation AA = 4 Megabyte Memory Board CA = 16 Megabyte Memory Board LJ-00499-TI0 MS44 Memory This section describes how to remove the MS44 memory modules from the system. Module Removal CAUTION Memory components are easily damaged with static electricity.
Page 250 Module Removal, Continued NOTE Memory modules must always be removed starting from the front of the system. For example, to replace the module at the rear of the system board, you must remove any modules at the front of the board and work toward the rear.
Page 251 Module Removal, Continued MS44 Memory To install a new MS44 memory module, perform the following Module steps. Replacement NOTE When installing memory modules (sets of four), each set must be installed in the slots identiﬁed for a particular set. These designators are to the right of each slot and identiﬁed with a 0x (where x=A1x [where x=E,F,G,H] for set 1.
Page 252: Spxg 8-Plane Option
SPXg 8-Plane Option The SPXg 8-plane option includes the following: Overview One graphics subsystem processor module One 8-plane frame buffer module Two 2-MB single in-line memory modules (SIM modules) Video connector bracket (attached to graphics subsystem processor module) NOTE The video connector is mounted upside down compared to the LCSPX.
Page 253: Removing The Spxg 8-Plane Option
SPXg 8-Plane Option, Continued Figure 6–11 Removing the SPXg 8-Plane Option Graphics Boards RFI Gasket Switch Package MR-0234-92DG Continued on next page 6–29...
Page 254 SPXg 8-Plane Option, Continued Installing the Reassemble the option assembly with the new FRU as follows: SPXg 8-plane Option Step Action Comment If the new FRU is a SIM module, install it on the frame buffer module. Set switch 2 towards the B Before installing the SPXg, ensure that switch marker on the frame buffer 2 of the two-switch package on the frame buffer...
Page 255 SPXg 8-Plane Option, Continued See Figure 6–14. Carefully The two hooks on the system box subchassis slip tilt the assembly into through the square holes in the lower curve of position the connector bracket. Insert the assembly. With the assembly in position, align the graphics subsystem processor and system module inter- module connectors .
Page 256 SPXg 8-Plane Option, Continued Figure 6–13 Installation Details Frame Buffer Gasket Video Connector Graphics Subsystem Processor Video Connector Bracket Ridge Hook System Box Subchassis WMO_SPXGGT_009 Continued on next page 6–32...
Page 257 SPXg 8-Plane Option, Continued Figure 6–14 Installing the SPXg 8-plane Option Tail Bracket Frame Buffer Module H-Bracket Graphics Boards RFI Gasket Switch Package LJ-02221-TI0 6–33...
Page 258: Spxgt 24-Plane Option
SPXgt 24-Plane Option The SPXgt 24-plane option includes the following: Overview One graphics subsystem processor module One 24-plane frame buffer module Plastic module clip (attached to graphics subsystem processor and frame buffer modules) Video connector bracket (attached to graphics subsystem processor module) NOTE This connector is mounted upside down compared...
Page 259 SPXgt 24-Plane Option, Continued Removing the The shape and size of the 24-plane frame buffer module prohibits SPXgt 24-Plane removing the SPXgt as an assembly. See Figure 6–15 and remove Option the components as follows: Step Action Turn off the system power, move the monitor, and open the system unit cover as described in System Preparation Remove the plastic clip (not shown) that holds the graphics subsystem processor module to the frame buffer...
Page 260 SPXgt 24-Plane Option, Continued Figure 6–15 Removing the SPXgt 24-Plane Option Tail Bracket Frame Buffer Module H-Bracket Tail Bracket Frame Buffer Graphics Subsystem Module Processor Module RFI Gasket Board Latches 4 MR-0218-92DG Continued on next page 6–36...
Page 261 SPXgt 24-Plane Option, Continued Installing the Reassemble the option assembly with the new FRU as follows: SPXgt 24-Plane Option Step Action Align the graphics module and system module inter- module connectors. Mate the connectors by pressing down on the module. The module latches should snap into place to secure the module.
Page 262 SPXgt 24-Plane Option, Continued Figure 6–16 Installing the SPXgt 24-Plane Option Tail Bracket H-Bracket Graphics Boards Tail Bracket RFI Gasket LJ-02220-TI0 6–38...
Page 263: Cpu Module
CPU Module This section describes how to remove the system module. System Module (CPU) Removal CAUTION Wear an antistatic wrist strap and place an antistatic mat under the system when removing and replacing any modules. To remove the system module (CPU), perform the following steps: Step Action Disconnect the cables attached to the module at the rear...
Page 264 CPU Module, Continued NOTE When the system module is replaced, the Ethernet ROM must be removed and installed on the new system module, otherwise, the Ethernet hardware address is lost on system module replacement. To install a new system module (CPU), reverse the steps in the System System Module (CPU) Removal procedure.
Page 265: Dsw21 Removal And Replacement
DSW21 Removal and Replacement To remove the DSW21 from the system box, perform the following DSW21 Removal steps: Step Action Remove the system box cover. Disconnect the SCSI cable, located directly in front of the DSW21. Disconnect the communications cable or terminator from the back of the system box.
Page 266: Bezel Removal
Bezel Removal Use the next procedure and refer to Figure 6–1 to remove the System Bezel Removal system bezel. Step Action Remove the cover. Remove the removable media bracket, with drives. See the RRD42 CDROM Drive Removal or RX26 (Diskette) Drive Removal procedures.
Page 267: Synchronous Communications Adapter Cables
Bezel Removal, Continued Synchronous Adapter cables for the synchronous communications adapter Communications vary according to the option. Table 6–3 lists the adapter cable variations. Adapter Cables Table 6–3 Synchronous Communications Adapter Cables DSW21 Model Adapter Cables DSW21-AA 1 Line sync comm BC19V EIA-232/V.24 DSW21-AB 1 Line sync comm...
Page 268 Bezel Removal, Continued Installing the This section describes how to install the synchronous Synchronous communications adapter interface in the system unit. Communications NOTE Adapter Refer to the system preparation instructions before installing any module in the workstation. To install the communications interface, do the following: Step Action Remove any rear panels or shields (if applicable) from the...
Page 269: Environmental Speciﬁcations
Bezel Removal, Continued Environmental Table 6–4 lists the synchronous communications model Speciﬁcations environmental speciﬁcations. Table 6–4 Environmental Speciﬁcations Operating temperature 5°C to 50° C (41°F to 122 °F) Nonoperating -40°C to 66° C (-40°F to 155°F) temperature Relative humidity 10% to 95% (noncondensing) (operating) Maximum wet 32 °C (90°F)
Page 270: Physical Speciﬁcations
Bezel Removal, Continued NOTE De-rate the maximum operating temperature by 1.82 degrees Celsius for each 1000 meters of altitude above sea level. This device is to operate in a non-caustic environment. Physical The synchronous communications adapter is a four-layer circuit Speciﬁcations board assembly.
Page 271: Clearing System Password
Clearing System Password NOTE Power to the system must be off to perform this procedure. To clear the system password, short the two triangles on the system module with a screwdriver. The triangles are located at the rear to the right of the CPU module, and to the right of the large TOY IC with the alarm clock emblem on it.
Page 272: Testing The Vaxstation 4000 Model 90 System
Testing the VAXstation 4000 Model 90 System Testing the This section describes how to test the system after completing the System removal or replacement process. Restoring the Before you can test the system, you must restore the system to System its previous operating state.
Page 273 Testing the VAXstation 4000 Model 90 System, Continued Step Action Display the system device conﬁguration by using the SHOW CONFIG command (see the System Preparation section). Compare the latest conﬁguration display with the conﬁguration display you viewed during system preparation. You should see the new device and the other devices present in the system.
Page 274: Turbochannel Option
TURBOchannel Option The TURBOchannel option is a high-performance input/output Overview interconnection that provides a data communications path. It allows you to install additional options, such as the following, in your system: A second Ethernet connection A second SCSI channel An FDDI network A VME adapter A third-party TURBOchannel device 6–50...
Page 275: Shipping Contents
Shipping Contents Figure 6–17 shows the components that ship with the TURBOchannel Adapter TURBOchannel adapter. Components Figure 6–17 TURBOchannel Adapter Components MLO-008166 Continued on next page 6–51...
Page 276 Shipping Contents, Continued Adapter Table 6–6 describes the TURBOchannel adapter components Component shown in Figure 6–17. Descriptions Table 6–6 TURBOchannel Adapter Components Number Component Function FCC Shield Seals the opening Metal option Helps to mount the option plate TURBOchannel Converts bus adapter board Four plastic Hold the adapter board in place...
Page 277 Shipping Contents, Continued Figure 6–18 shows the components that ship with the TURBOchannel Option TURBOchannel option. Components Figure 6–18 TURBOchannel Option Components MLO-008525 Important Use the option guide and the screws in the adapter shipping package when installing the TURBOchannel option The document and the two screws that ship with this option...
Page 278: Turbochannel Adapter And Option Modules
TURBOchannel Adapter and Option Modules Table 6–7 provides an overview of how to remove and replace the TURBOchannel Adapter TURBOchannel adapter and the TURBOchannel option. and Option Removal Table 6–7 TURBOchannel Adapter/Option Removal Step Action Disconnect the TURBOchannel option cable. Remove the two screws that hold the option plate over the outside of the TURBOchannel option.
Page 279: Installing The Turbochannel Option
Installing the TURBOchannel Option Installation Table 6–8 provides an overview of the TURBOchannel option Overview installation procedure. Each step is explained in more detail in the following sections. Table 6–8 TURBOchannel Option Installation Procedure Step Action Touch the TOUCH HERE space on the power supply.
Page 280 Installing the TURBOchannel Option, Continued TOUCH HERE As soon as you remove the cover, and before you remove anything Space else, touch the space labeled TOUCH HERE (Figure 6–19 ), to avoid damage from static discharge. Figure 6–19 Inside the System Box MLO-008167 Disconnect the Disconnect the SCSI cable from the system unit by pushing the...
Page 281 Installing the TURBOchannel Option, Continued Remove the Remove the option plate that covers the TURBOchannel option Option Plate port opening. Squeeze the tabs together, then pull the plate out, as shown by the arrows in Figure 6–20. Figure 6–20 Removing the Filler Plate MLO-008524 Remove the If there is a a graphics board present, you need to remove it.
Page 282 Installing the TURBOchannel Option, Continued Figure 6–21 Inserting the TURBOchannel Adapter Board MLO-008168 Replace the Replace the graphics board in your system unit. Refer to the Graphics Installing the SPXg 8-plane Option procedure. Board Continued on next page 6–58...
Page 283 Installing the TURBOchannel Option, Continued Attaching the Attach the FCC shield to the front of the TURBOchannel option FCC Shield module, over the metal bracket, as shown in Figure 6–22. Figure 6–22 Attaching the FCC Shield MLO-008519 Reconnect the Reconnect the SCSI cable to the port slot above the SCSI Cable TURBOchannel option port.
Page 284 Installing the TURBOchannel Option, Continued Install the Install the TURBOchannel option module to the right of the TURBOchannel graphics board. Option Slide the TURBOchannel option module ﬁrmly towards the front. Press the rear of the module so that the connector underneath slides into the connector on the TURBOchannel adapter board.
Page 285 Installing the TURBOchannel Option, Continued Attach the Place the metal option plate over the outside of the Option Plate TURBOchannel option, as shown in Figure 6–24. Screw the option plate into the TURBOchannel option module using the two Phillips screws, as shown in Figure 6–24. Figure 6–24 Screwing on the Option Plate MLO-008520 This completes the TURBOchannel option installation.
Page 286 Installing the TURBOchannel Option, Continued Testing the To test your TURBOchannel option installation, follow the Installation instructions in Testing the VAXstation 4000 Model 90 System. Callout of Figure 6–25 shows the line in the SHOW CONFIG display that indicates a successful TURBOchannel option installation.
Page 287: Turbochannel Speciﬁcations
TURBOchannel Speciﬁcations Table 6–9 provides the speciﬁcations for the TURBOchannel Speciﬁcations option. Table 6–9 TURBOchannel Speciﬁcations Air ﬂow 150 LFM Connector 96-pin DIN Data path 32-bit multiplexed address/data Nonoperating storage 0 to 50°C (32 to 89.6°F) temperature Operating temperature 10 to 40°C (50 to 104°F) Operating temperature 15 to 32°C (59 to 90°F) With tape or ﬂoppy...
Page 289: Appendix A Diagnostic Error Codes
Appendix A Diagnostic Error Codes Overview In this Chapter The system ﬁrmware always tries to report any detected hardware errors to the console device and to the LEDs located on the front of the system box. Errors are reported as a result of failures during the power-up tests or during user initiated tests.
Page 290 Overview, Continued — TURBOchannel Adapter — LCSPX System Test Error Messages — SCSI — DSW21 Communications Device Utility Error Messages — SCSI — LCSPX — SPXg/gt A–2...
Page 291: Error Messages
Error Messages The system reports two kinds of self-test errors. Overview Errors that display on the console immediately after running the self test These error messages consist of one or two question marks to indicate a nonfatal or fatal error, the failing FRU, the device that failed, and a general error code.
Page 292 Error Messages, Continued Message Meaning The device identiﬁcation (decimal). This value corresponds to the left bank of four LEDs (hexadecimal). This ID also corresponds to the mnemonic in the next ﬁeld. Use Table 5–4 to correlate the error code to a device. SCSI The mnemonic of the device ID.
Page 293 Error Messages, Continued Message Meaning First line of error message Indicates whether the failure is fatal or non-fatal. A double question mark (??) indicates a fatal error. A single question mark (?) indicates a non-fatal error. Field replaceable unit (FRU). See Table A–1. Device identiﬁcation (Value is given in decimal.
Page 294 Error Messages, Continued FRU Codes The FRU code identiﬁes the ﬁeld replaceable unit that failed. The FRU codes and their names are listed in the following table. Table A–1 FRU Codes Code System module. The mnemonic identiﬁes the device. Keyboard Mouse Monitor #1 Monitor #2...
Page 295 Error Messages, Continued Table A–1 (Continued) FRU Codes Code SCSI Drive Codes 100-199 Code Drive with ID A–7...
Page 296: Self-Test Error Messages
Self-Test Error Messages Table A–2 lists the TOY/NVR self-test decimal and hexadecimal TOY/NVR error messages and their meanings. Table A–2 TOY/NVR Self-Test Error Messages Decimal Hexadecimal Meaning Battery faulty. NVR Register test has failed. Battery down and NVR Register test has failed.
Page 297: Dz Self-Test Error Codes
Self-Test Error Messages, Continued Table A–2 (Continued) TOY/NVR Self-Test Error Messages Decimal Hexadecimal Meaning Update in progress has failed to clear; soft error. Update in progress has failed and VRT bit failure. Table A–3 lists the error messages in decimal and hexadecimal format that are returned by the DZ self-test.
Page 298 Self-Test Error Messages, Continued Extended Error Format 001 000A ssssssss cccccccc lprlprlp llllllll rrrrrrrr eeeeeeee Format Meaning ssssssss The sub-error code cccccccc The value of the DZ CSR lprlprlp The contents of the line parameter register llllllll The line number rrrrrrrr The data read back eeeeeeee...
Page 299: Dz Suberror Codes
Self-Test Error Messages, Continued The suberror codes reported by the DZ self-test are as follows: Table A–4 DZ Suberror codes Suberror (hexadecimal) Meaning READ LPR Baud rate is incorrectly set READ LPR Character width is incorrectly set READ LPR Parity bit is incorrectly set READ LPR Receiver on bit is incorrectly set DZ Modem test - Failed RTS <->...
Page 300: Scsi Dma Self-Test Error Codes
Self-Test Error Messages, Continued Table A–4 (Continued) DZ Suberror codes Suberror (hexadecimal) Meaning DZ Interrupt test - Character received != Character transmitted DZ LK401 test - transfer has timed out DZ LK401 test - LK401 has failed self-test DZ Mouse test - transfer has timed out DZ Mouse test - Mouse has failed self-test This table lists the SCSI DMA self-test error codes.
Page 301: Obit Self-Test Error Codes
Self-Test Error Messages, Continued Table A–6 lists the OBIT self-test decimal and hexadecimal error OBIT codes. Table A–6 OBIT Self-Test error codes Decimal Hexadecimal Meaning Failed ﬂoating 1s and 0s data test Failed verify background pattern = AAAAAA, write 555555 Failed verify second pattern = 555555, write 0 Failed verify background pattern = 0,...
Page 302: Cache Self-Test Error Codes
Self-Test Error Messages, Continued CACHE Table A–7 lists the CACHE self-test decimal and hexadecimal error codes. Table A–7 CACHE Self-Test Error codes Decimal Hexadecimal Meaning Backup Tag Store was not written correctly Backup Cache Data Line Test Error Backup Cache Data RAM March Test Error Backup Cache Mask Write Error byte Backup Cache Mask Write Error word...
Page 303 Self-Test Error Messages, Continued Extended errors reported by the SCSI DMA, OBIT, and BCACHE tests are formatted as follows: 001 000a aaaaaaaa bbbbbbbb cccccccc dddddddd Format Meaning aaaaaaaa BCTAG IPR address that failed the test bbbbbbbb Expected value of the data pattern cccccccc Data that was read from the failing address dddddddd...
Page 304: Mem Self-Test Error Codes
Self-Test Error Messages, Continued Table A–8 MEM Self-Test Error Codes Decimal Hexadecimal Meaning Bank 0 1 or more SIM modules missing. Bank 0 SIM modules not all same size. Bank 2 1 or more SIM modules missing. Bank 2 SIM modules not all same size.
Page 305: Mem Sim Module Fru Values
Self-Test Error Messages, Continued Extended Error Format: xxx 4 MEM yyyy xxx 00a bbbbbbbb cccccccc dddddddd eeeeeeee Format Meaning The FRU where the failure occurred yyyy The error code in Hexadecimal Extended error information format type bbbbbbbb The contents of the Memory System Error register (MSER) cccccccc The failing address...
Page 306 Self-Test Error Messages, Continued Table A–9 (Continued) MEM SIM Module FRU Values (decimal) Module BANK Table A–10 lists the ﬂoating point diagnostic decimal and hexadecimal error codes. Table A–10 FPU Self-Test Error Codes Decimal Hexadecimal Meaning MOVF Instruction test has failed. Unexpected Exception has occurred during MOVF test.
Page 307 Self-Test Error Messages, Continued Table A–10 (Continued) FPU Self-Test Error Codes Decimal Hexadecimal Meaning 1538 CVTFD/CVTFG Instruction test has failed. 1540 Unexpected Exception has occurred during CVTFD/CVTFG test. 1794 CVTFx Instruction test has failed. 1796 Unexpected Exception has occurred during CVTFx test. 2050 CVTxF Instruction test has failed.
Page 308 Self-Test Error Messages, Continued Table A–10 (Continued) FPU Self-Test Error Codes Decimal Hexadecimal Meaning 3586 TSTF Instruction test has failed. 3588 Unexpected Exception has occurred during TSTF test. The FPU test displays extended error information when an error occurs. Enter the SHOW ERROR Command to view the extended error information.
Page 309 Self-Test Error Messages, Continued Table A–11 (Continued) FP Exception Vectors Vector Description Reserved operand vector Reserved Addressing mode vector Arithmetic Trap vector Interval Timer Table A–12 lists the interval timer self-test decimal and hexadecimal error codes and their meanings. Table A–12 IT Self-Test Error Codes Decimal Hexadecimal Meaning Interval Timer is not interrupting at...
Page 310 Self-Test Error Messages, Continued Extended Error Format: This format displays when there is an invalidate ﬁlter RAM error. 001 0010 aaaaaaaa rrrrrrrr eeeeeeee Format Meaning The FRU number (system board) 0010 The format number aaaaaaaa The failing invalidate ﬁlter address rrrrrrrr The data read Network...
Page 311 Self-Test Error Messages, Continued Table A–14 (Continued) NI Self-Test Error Codes Decimal Hexadecimal Meaning Network Address ROM: bad test patterns SGEC CSR0 R/W error SGEC CSR1 R/W error SGEC CSR2 R/W error SGEC CSR3 R/W error SGEC CSR4 R/W error SGEC CSR5 R/W error SGEC CSR6 R/W error SGEC CSR7 R/W error...
Page 312 Self-Test Error Messages, Continued Table A–14 (Continued) NI Self-Test Error Codes Decimal Hexadecimal Meaning SGEC Chip self-test: Self-Test loopback error SGEC Initialization: Setup frame send failure SGEC Interrupts: initialization failed SGEC Interrupts: transmit failed SGEC Interrupts: receive failed SGEC Interrupts: packet comparison failed SGEC Interrupts: NI ISR not entered SGEC Interrupts: NI ISR entered...
Page 313 Self-Test Error Messages, Continued Table A–14 (Continued) NI Self-Test Error Codes Decimal Hexadecimal Meaning SGEC Address ﬁltering: initialization failed SGEC Address ﬁltering: transmit failed SGEC Address ﬁltering: receive failed SGEC Address ﬁltering: packet comparison failed SGEC Address ﬁltering: broadcast ﬁltering failed SGEC Address ﬁltering: promiscuous mode failed SGEC Address ﬁltering: null...
Page 314 Self-Test Error Messages, Continued NI EXTENDED ERROR FORMAT 1h: Register Error 0001 0001 aaaaaaaa bbbbbbbb cccccccc Format Meaning aaaaaaaa The register number bbbbbbbb The expected data - data written cccccccc The actual data - data read NI EXTENDED ERROR FORMAT Bh: Network Address ROM Address Group Error 0001 000B aaaaaaaa bbbbbbbb cccccccc 0000dddd Format...
Page 315 Self-Test Error Messages, Continued NI EXTENDED ERROR FORMAT Eh: Transmit Error 0001 000E aaaaaaaa bbbbbbbb cccccccc dddddddd Format Meaning aaaaaaaa Actual value of SGEC CSR5 bbbbbbbb Physical address of current transmit descriptor cccccccc First longword of the transmit descriptor dddddddd Second longword of transmit descriptor NI EXTENDED ERROR FORMAT Fh: Receive Error 0001 000F aaaaaaaa bbbbbbbb cccccccc dddddddd...
Page 316 Self-Test Error Messages, Continued NI EXTENDED ERROR FORMAT 11h: Interrupt Error 0001 0011 aaaaaaaa Format Meaning aaaaaaaa Actual value of SGEC CSR5 Table A–15 lists the decimal and hexadecimal error codes SCSI returned by the SCSI self-test. Table A–15 SCSI Self-Test Error Codes Decimal Hexadecimal Meaning SCSI Reset Register test has failed.
Page 317 Self-Test Error Messages, Continued Table A–15 (Continued) SCSI Self-Test Error Codes Decimal Hexadecimal Meaning SCSI Interrupt test Low Ipl, Mask Enabled has failed. SCSI Data Transfer Test, Prom Function has failed. SCSI Data Transfer Test, DMA Mapping has failed. SCSI Data Transfer Test, Non-DMA Inquiry has failed.
Page 318 Self-Test Error Messages, Continued Table A–15 (Continued) SCSI Self-Test Error Codes Decimal Hexadecimal Meaning SCSI Map Error Test, Map Error Will Not Set. SCSI Map Error Test, Parity Error Will Not Clear. SCSI Map Error Test, Prom Function has Failed. SCSI Prom Function has failed.
Page 319 Self-Test Error Messages, Continued EXTENDED ERROR FORMAT B(h): This error format is used by the register test. 001 000B aaaaaaaa bbbbbbbb cccccccc Format Meaning aaaaaaaa The error code bbbbbbbb The address of register or location being accessed cccccccc Information about the error EXTENDED ERROR FORMAT C(h): This error format is used by the interrupt test.
Page 320 Self-Test Error Messages, Continued EXTENDED ERROR FORMAT D(h): This error format is used when not enough data is returned to the self-test after a SCSI command is executed. aaa 000D bbbbcccc ddddeeee ffffgggg hhhhhhhh Format Meaning The FRU bbbb Logical unit number cccc Device ID dddd...
Page 321 Self-Test Error Messages, Continued Format Meaning gggg Mode of operation hhhh Byte 14 of the request sense packet (device FRU) iiii Information about the error jjjjjjjj SCSI Bus phase at the time of the error kkkk Contents of the Controller Status register at the time of error llll Contents of the Controller Interrupt register...
Page 322 Self-Test Error Messages, Continued Format Meaning kkkkkkkk Request sense key EXTENDED ERROR FORMAT 10(h): This error format is used when a request sense command is executed, but not enough sense bytes are received. aaa 0010 bbbbcccc ddddeeee ffffgggg hhhhiiii jjjjjjjj kkkkkkkk Format Meaning bbbb...
Page 323 Self-Test Error Messages, Continued EXTENDED ERROR FORMAT 11(h): This error format is used when the data out phase sends less bytes than expected. aaa 0011 bbbbcccc ddddeeee ffffgggg hhhhiiii jjjjkkkk llllllll mmmmmmmm Format Meaning The FRU bbbb The logical unit number cccc Device ID dddd...
Page 324 Self-Test Error Messages, Continued EXTENDED ERROR FORMAT 12(h): This error format is used when an unsupported message is seen. aaa 0012 bbbbcccc ddddeeee ffffgggg hhhhiiii jjjjjjjj kkkkllll mmmmmmmm Format Meaning bbbb Logical unit number cccc Device ID dddd Actual command opcode eeee Current command opcode ffff...
Page 325 Self-Test Error Messages, Continued EXTENDED ERROR FORMAT 13(h): This error format is used by the Map Error test. aaa 0013 bbbbcccc dddddddd eeeeeeee ffffffff gggggggg hhhhhhhh iiiiiiii Format Meaning The FRU bbbb Logical unit number cccc Device ID dddddddd DMA Address where the SCSI command is located eeeeeeee DMA Address where the SCSI data is located...
Page 326 Self-Test Error Messages, Continued EXTENDED ERROR FORMAT 14(h): This error format is used by the Data Transfer test when the number of bytes received from two transfers is different. aaa 0014 bbbbbbbb cccccccc dddddddd Format Meaning The FRU bbbbbbbb The ﬁrst number of bytes cccccccc The second number of bytes dddddddd...
Page 327 Self-Test Error Messages, Continued The FRU reported by all error formats is either 1 for the system board FRU, or (100 + device_id*10 + logical unit number. Table A–16 lists the information values reported by some extended SCSI self-test errors. Hexadecimal values are used for self-test.
Page 328 Self-Test Error Messages, Continued Table A–16 (Continued) SCSI Information Values Information Decimal Hexadecimal Meaning Selected bit set in Controller Interrupt register Select with attention bit clear in Controller Interrupt register Select with attention bit set in Controller Interrupt register Reselected bit clear in Controller Interrupt register Reselected bit set in Controller Interrupt register...
Page 329 Self-Test Error Messages, Continued Table A–16 (Continued) SCSI Information Values Information Decimal Hexadecimal Meaning SCSI Reset bit set in Controller Interrupt register Arbitration not won Selection timeout Invalid sequence in Sequence Step register FIFO ﬂags are not clear FIFO ﬂags are clear Unexpected ISR hit SCSI Interrupt request set in system interrupt request register...
Page 330 Self-Test Error Messages, Continued Table A–16 (Continued) SCSI Information Values Information Decimal Hexadecimal Meaning Phase did not go to message in phase Command phase changed too soon Data out phase changed too soon Message in phase changed too soon Message out phase changed too soon Stuck in command phase Stuck in message in phase Stuck in message out phase...
Page 331 Self-Test Error Messages, Continued Table A–16 (Continued) SCSI Information Values Information Decimal Hexadecimal Meaning Unexpected message reject from device FIFO ﬂag count is wrong Message is unsupported Bus device reset was sent, but device didn’t drop off bus Illegal phase Should not be in data in phase Problem with a device trying to reconnect...
Page 332 Self-Test Error Messages, Continued Mode Values The mode values reported by some extended SCSI self-test errors are as follows: Table A–17 SCSI mode values Mode (hexadecimal) Meaning Asynchronous mode with programmed I/O Asynchronous mode with DMA Synchronous mode with DMA The audio self-test (AUD) is divided into three major sections.
Page 333 Self-Test Error Messages, Continued Audio Table A–18 lists the decimal and hexadecimal error codes returned by the AUD self-test. Table A–18 AUD Self-Test Error Codes Decimal Hexadecimal Meaning AUD$LIU_LSR_SAE Register test has failed. AUD$LIU_LPR_SAE Register test has failed. AUD$LIU_LPR_NZE Register test has failed.
Page 334 Self-Test Error Messages, Continued Table A–18 (Continued) AUD Self-Test Error Codes Decimal Hexadecimal Meaning AUD$INTR_RECEIVE_BYTE_ AVAILABLE test has failed. AUD$INTR_BAD_DLC_LOOPBACK_ DATA Test has failed. AUD$INTR_TIME_OUT test has failed. AUD$INTR_INVALID_IR_VALUE test has failed. AUD$INTR_NO_INT_GENERATED test has failed. AUD$INTR_NOT_ALL_INTS_RCVD test has failed. AUD$INTR_INT_NOT_DISABLED TEst has failed.
Page 335 Self-Test Error Messages, Continued Format Meaning cccccccc The contents of data register (DR) dddddddd EXTENDED ERROR FORMAT 11(h): This error format is used by all audio interrupt tests. aaa 0011 bbbbbbbb cccccccc dddddddd Format Meaning The FRU bbbbbbbb The error number cccccccc The contents of D channel status register 2 (DSR2)
Page 336 Self-Test Error Messages, Continued DSW21 Synch Table A–19 lists the DSW21 Synch communications test error Communications codes. Test Error Codes Table A–19 Synch Comm Device Test Error Codes Decimal Hexadecimal Meaning Self-Test was unsuccessful Transmit underﬂow Transmitter busy Receiver busy Transmitter error Carrier detect loss Sync Comm Receive Failures...
Page 337 Self-Test Error Messages, Continued Table A–19 (Continued) Synch Comm Device Test Error Codes Decimal Hexadecimal Meaning Invalid test Synch Comm. Device Failures Comm option test failure Comm option copy to RAM failed Comm option RAM test failed Comm option dual RAM access test Comm option interrupt test Comm option reset test Comm option internal loopback...
Page 338 Self-Test Error Messages, Continued Table A–19 (Continued) Synch Comm Device Test Error Codes Decimal Hexadecimal Meaning Synch Comm. IMP Failures IMP IDMA Timeout IMP SCC Transmit timeout IMP SCC Receive timeout IMP Command timeout IMP ERR Timeout IMP PB8 Timeout IMP SMC2 Timeout IMP SMC1 Timeout IMP Watchdog timeout...
Page 339 Self-Test Error Messages, Continued Table A–19 (Continued) Synch Comm Device Test Error Codes Decimal Hexadecimal Meaning Synch Comm. IMP Failures IMP Timer 2 timeout IMP SCC3 Timeout IMP PB9 Timeout IMP Timer 1 timeout IMP SCC2 Timeout IMP IDMA Timeout IMP SDMA Timeout IMP SCC1 Timeout IMP PB10 Timeout...
Page 340 Self-Test Error Messages, Continued Table A–19 (Continued) Synch Comm Device Test Error Codes Decimal Hexadecimal Meaning Synch Comm. IMP Failures IMP Timer 2 timeout IMP Transmit ready timeout IMP Receive ready timeout IMP Invalid SCC channel Data Compare error IMP Carrier detect asset timeout IMP Carrier detect deassert timeout IMP CTS Assert timeout IMP CTS Deassert timeout...
Page 341 Self-Test Error Messages, Continued Table A–19 (Continued) Synch Comm Device Test Error Codes Decimal Hexadecimal Meaning Memory free error UTIL Invalid utility number UTIL Invalid cable code DSW21 Comm. Timeout Failures Timeout comm option set response RA Timeout comm option clear command Timeout comm option set scheduler run SR Timeout comm option set transmit...
Page 342 Self-Test Error Messages, Continued Table A–19 (Continued) Synch Comm Device Test Error Codes Decimal Hexadecimal Meaning ROM Test ROM Checksum error Ctrl C entered at console Comm option receive error-CRC follow error Comm option MC68302 component is not REV B Test request sequence error IMP Timeout waiting for host to clear IMP Timeout waiting for host to clear...
Page 343 Self-Test Error Messages, Continued Table A–19 (Continued) Synch Comm Device Test Error Codes Decimal Hexadecimal Meaning ROM Test error FBUG Secure error-reserved operation Port PB3 Signal stuck high Timer 3 not counting Comm option diagnostics did not complete Comm option SDMA bus error occurred Timeout waiting for IRQ assertion Transmit restart of 10 exceeded...
Page 344 Self-Test Error Messages, Continued Table A–20 (Continued) TURBOchannel Adapter Self-Test Error Codes Decimal Hexadecimal Meaning 0010 000A FIFO Not empty after retrieving data 0012 000C Data read from FIFO does not match loaded data 0014 000E Forced invalid reference error not seen 0016 0010...
Page 345 Self-Test Error Messages, Continued Decimal The following example shows a TCA decimal error code. Format >>>T TCA ?? 013 13 TCA 0026 Hexadecimal The following example shows a TCA hexadecimal error code. Format >>>SHOW ERROR ?? 013 13 TCA 001A TURBOchannel There is no system test for the TURBOchannel adapter.
Page 346 Self-Test Error Messages, Continued Example: >> T TC0 ? REX CMDS: T TC0 / <tstnam> | ? T TC0 SCRIPT <scriptnam> T TC0 INIT T TC0 CNFG T TC0 LS T TC0 CAT <scriptnam> >> The examples are for the single-width DEFZA TURBOchannel FDDI option.
Page 347 Self-Test Error Messages, Continued ROM Object The following table deﬁnes the ROM object symbols. Symbols Symbol Meaning Symbolic link --> Executable image Separator between the two parameters Scripts (built-in tests to be executed one after the pst-q, other) pst-t, Use these tests with the pst-m T TC0 CAT [SCRIPTNAM] commands.
Page 348 Self-Test Error Messages, Continued t ${#}/rtostim t ${#}/botim t ${#}/extlpbk t ${#}/extmemtst t ${#}/dmatst >> DEFINITION ${#} is script language for "substitute the slot number here." When the emulator executes each test in a script, it automatically substitutes the slot number for ${#}.
Page 349 Self-Test Error Messages, Continued The option test results are option dependent. TURBOchannel options can display the tests differently. Some options show only the <tstnam> strings. Also, some options do not have a HELP feature, therefor the T TC0 /? command does not display (it could even cause an error to be reported by some options).
Page 350 Self-Test Error Messages, Continued Example: >> T TC0 SCRIPT PST-Q *emul: t tc0 pst-q t 0/flash t 0/eprom t 0/68K t 0/sram t 0/rmap t 0/phycsr t 0/mac t 0/elm t 0/cam t 0/nirom t 0/intlpbk t 0/iplsaf t 0/pmccsr t 0/rmc t 0/pktmem t 0/rtostim...
Page 351 Self-Test Error Messages, Continued The initialization object is optional, therefore a TURBOchannel option may or may not have an initialization function. No error occurs if an option does not have an initialization object. The emulator’s function is to execute the tests. While an error MIPS/REX Emulator status code is maintained during testing, the emulator does not...
Page 352 Self-Test Error Messages, Continued Corrective Action Check the option seating, and the option connector and option ROM for bent pins. Message ERR-MIPS - ROM OBJECT REPORTED A SEVERE ERROR Description The emulator received a severe error status code back from a TURBOchannel object.
Page 353 Self-Test Error Messages, Continued Table A–21 Synch Communications Self-Test Sequence Numbers Test Number Decimal Hexadecimal Routine Description imp_exc Exception vector initialization imp_vec User interrupt vector initialization imp_rdb Local register RDB initialization imp_pub_ Up block initialization init imp_op_ Option register init initialization imp_br_init Base register...
Page 354 Self-Test Error Messages, Continued Table A–21 (Continued) Synch Communications Self-Test Sequence Numbers Test Number Decimal Hexadecimal Routine Description imp_loc_ Local scratch RAM SCR init initialization imp_idb_ Interrupt data block init initialization imp_pcb_ Process control block init initialization imp_ic_init Interrupt controller initialization imp_cable_ Read cable code...
Page 355 Self-Test Error Messages, Continued Table A–21 (Continued) Synch Communications Self-Test Sequence Numbers Test Number Decimal Hexadecimal Routine Description imp_ Modem signal test modem_ test imp_elb_ SCC External loop test imp_isdn_ ISDN test test imp_rdb Runtime register RDB initialization imp_loc_ Runtime SCR RAM init initialization imp_cable_...
Page 356 Self-Test Error Messages, Continued Table A–21 (Continued) Synch Communications Self-Test Sequence Numbers Test Number Decimal Hexadecimal Routine Description imp_s3_ Runtime SCC3 ISR inte imp_t1_ Runtime timer 1 start start imp_t2_ Runtime timer 2 start start imp_t3_ Runtime timer 3 start start imp_dainit Runtime RAM dual...
Page 357 Self-Test Error Messages, Continued Format Meaning aaaa Test status bbbb Data size (1=byte access, 2=word access, 4=long access) cccc Address low dddd Address high eeee Actual data ffff Expected data Extended Error Format 0002: This format is used by the DSW21 communications device self- tests.
Page 358 Self-Test Error Messages, Continued Format Meaning kkkk Current SCC mode llll Current protocol mmmm Data size nnnn Current channel speed oooo Address low pppp Address high qqqq Expected data rrrr Actual data Extended Error Format 0003: This format is used by the DSW21 communications device dual access tests.
Page 359 Self-Test Error Messages, Continued Format Meaning External channel count kkkk Current SCC mode llll Current protocol mmmm Data size nnnn Current channel speed oooo Address low pppp Address high qqqq Expected data rrrr Actual data Extended Error Format 0004: This format is used by the DSW21 communications device interrupt test.
Page 360 Self-Test Error Messages, Continued Format Meaning Internal loopback mode (0=internal, 1=external) External channel count kkkk Current SCC mode llll Current protocol mmmm Data size nnnn Current channel speed oooo Address low pppp Address high qqqq Expected data rrrr Actual data Extended Error Format 0005: This format is used by the DSW21 communications device modem signal tests.
Page 361 Self-Test Error Messages, Continued Format Meaning Current channel under test (1, 2, 3) Current electrical interface Internal loopback mode (0=internal, 1=external) External channel count kkkk Current SCC mode llll Current protocol mmmm Data size nnnn Current channel speed oooo Address low pppp Address high qqqq...
Page 362 Self-Test Error Messages, Continued Format Meaning Current software revision Current channel under test (1, 2, 3) Current electrical interface Internal loopback mode (0=internal, 1=external) External channel count kkkk Current SCC mode llll Current protocol mmmm Data size nnnn Current channel speed oooo Address low pppp...
Page 363 Self-Test Error Messages, Continued Extended Error Format 0008: This format is used by the synchronous communication option null request. 020 0008 0008 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 Format Meaning The FRU for the DSW21 communications device 0008 Format type...
Page 364 Self-Test Error Messages, Continued Extended Error Format 10: This format is used by the DSW21 communications device when it ﬁrst executes code, and is used to verify that the 68K is executing instructions. 020 000A 00040003 00060005 00080007 00100009 00120011 00140013 00160015 Format Meaning...
Page 365 Self-Test Error Messages, Continued LCSPX The LCSPX module provides error information that can be utilized to identify faults down to a logical block. The following is a break down of the error information provided in the power-up error code format by the LCSPX diagnostic ROM. ?? 001 LCSPX 0128...
Page 366 Self-Test Error Messages, Continued Failing Logical The failing logical block ﬁeld points in an area that can be used Block Field as a starting point for diagnosing the fault. This does not mean that it is the actual fault but the error was detected at that point. Table A–23 lists the failing logical blocks.
Page 367 Self-Test Error Messages, Continued Table A–24 Test Number Summary Test Number Hexadecimal/Decimal Test 01/01 TBC Register 02/02 TBC Horizontal Timing 03/03 TBC Vertical Timing 04/04 TBC LEGO Load 05/05 Brooktree Register 06/06 Brooktree Memory 07/07 ScanProc Register 08/08 ScanProc Scratch RAM 09/09 ScanProc Microcode RAM 0A/10...
Page 368 Self-Test Error Messages, Continued Table A–24 (Continued) Test Number Summary Test Number Hexadecimal/Decimal Test 19/25 ScanProc Copy Opaque Rectangle 1A/26 ScanProc Basic Trapezoid 1B/27 ScanProc Basic Vector 1C/28 Frame Buffer Stream Write 1D/29 Frame Buffer Stream Read 1E/30 VRAM Serial Shift 1F/31 Brooktree LEGO Load 20/32...
Page 369 Self-Test Error Messages, Continued 0022 SPXG 0080 0081 FFFF0000 FF00FF00 22004400 00000000 00000000 00000000 Extended Data 6 Extended Data 5 Extended Data 4 Extended Data 3 Extended Data 2 Extended Data 1 Error Number Failing Test Failing Block Failing Logical The failing logical block ﬁeld points in an area that can be used as Block Field a starting point for diagnosing the fault.
Page 370 Self-Test Error Messages, Continued Test Numbers The following table lists all the tests provided in the SPXG self- test ROM. The test number is found in the failing test ﬁeld of the error code. Table A–26 Test Number Summary Test Number Hexadecimal LED Codes /Decimal...
Page 371 Self-Test Error Messages, Continued Table A–26 (Continued) Test Number Summary Test Number Hexadecimal LED Codes /Decimal (Hexadecimal) 0150/0336 ScanProc Stream Write 0160/0352 FIFO Transfer 0170/0368 ScanProc External Write 0180/0384 ScanProc Stream Read 0190/0400 LCG DMA 01A0/0416 LCG OTF 01B0/0432 DMA Stream 01C0/0448 OTF Stream 01D0/0464...
Page 372: System Test Error Messages
System Test Error Messages Table A–27 lists the error codes returned by the SCSI system SCSI test. Table A–27 SCSI System Test Error Codes Decimal Hexadecimal Meaning WST Call failed ELN Call failed Inquiry failed when sizing bus Not enough inquiry data returned when sizing bus Start unit failed when sizing bus Test unit ready failed when sizing bus...
Page 373 System Test Error Messages, Continued Table A–27 (Continued) SCSI System Test Error Codes Decimal Hexadecimal Meaning Wrong number bytes read when checking for boot block Non-DMA inquiry failed in data transfer test Synchronous DMA inquiry failed in data transfer test Number bytes miscompare in data transfer test Data miscompare in data transfer test...
Page 374 System Test Error Messages, Continued Format Meaning Field replaceable unit (hexadecimal if FRU gotten from request sense packet) SCSI command that failed (hexadecimal) SCSI Bus phase at time or error Informational value (same as those reported by the self-test...hexadecimal) LBNSTRT Starting logical block number of failed transfer (hexadecimal) XFERSIZ...
Page 375 System Test Error Messages, Continued There are 9 error codes possible for each line: 1 - not all characters transmitted 2 - 1st character not received 3 - timeout 4 - more characters received than expected 5 - parity error 6 - framing error 7 - overrun error 8 - data compare error These errors are translated by...
Page 376 System Test Error Messages, Continued 4 - VAXELN 5 - System 0 00:00:00:00 test run time YY is the speciﬁc error code. Table A–28 list the NI system test error codes and their meanings. Table A–28 NI System Test Error Codes Error Source (X) Error Code (YY) Meaning...
Page 377 System Test Error Messages, Continued Table A–28 (Continued) NI System Test Error Codes Error Source (X) Error Code (YY) Meaning Timeout waiting for receive interrupt Memory error on init BABL Error on init MISS Error on init Parity error on init MAP Error on init Memory error on receive BABL Error on receive...
Page 378 Utility Error Messages Table A–29 describes the errors returned by a SCSI utility. All SCSI SCSI utility errors have the format: text_message information_value. Table A–29 Text Messages for SCSI Utilities Text Message Meaning SCSI_E_badparam Bad parameter entered by the user SCSI_E_err Generic utility error SCSI_E_devtyp...
Page 379 Utility Error Messages, Continued Table A–30 Additional SCSI Information Values for Utilities Information Decimal Meaning Bad utility number received from the user Bad device number received from the user Bad logical unit number received from the user Wrong number of parameters entered by the user Device number entered by the user is the same as the controller...
Page 380: Utility Error Messages
Utility Error Messages, Continued Table A–30 (Continued) Additional SCSI Information Values for Utilities Information Decimal Meaning Illegal ﬂoppy drive Illegal ﬂoppy media LCSPX The LCSPX utilities provide some test patterns that can be used to visually verify the video output and the monitor quality. Enter T/UTIL 2 to access the utilities menu.
Page 381: Menu Item Meanings
Utility Error Messages, Continued Table A–31 Menu Item Meanings Menu Item Action Draws a full white screen Draws a full red screen Draws a full green screen Draws a full blue screen Draws four color bars to the screen Draws eight color bars to the screen Draws eight gray scale bars to the screen Draws a screen of Es Draws a screen of squares with a dot in...
Page 382: Menu Item Meanings
Utility Error Messages, Continued SPXg/gt The SPXg utilities provide some test patterns that can be used to visually verify the video output and the monitor quality. Enter T/UTIL 2 to access the utilities menu. The console device or the alternate console connected to the Model 90 serial port can be used.
Page 383 Utility Error Messages, Continued Table A–32 (Continued) Menu Item Meanings Menu Item Action Draws a screen of squares with a dot in the center of each square. A circle with a diameter equal to the screen length is then drawn on the screen Draws a screen of Hs on the screen All test can be terminated by pressing the space bar on the keyboard.
Page 385: Appendix B Reading The Diagnostic Led Codes
Appendix B Reading the Diagnostic LED Codes Overview In this This appendix describes how to interpret the diagnostic LEDs on Appendix the console control panel. The LED codes covered in this module are: Diagnostic LED Codes LED Error Codes Power-Up/Initialization LED Codes TOY/NVR LED Codes LCSPX LED Codes SPXg/gt LED Codes...
Page 386: Diagnostic Led Codes
Diagnostic LED Codes The system uses the eight LEDs on the control panel to indicate Overview the currently executing test. When power is turned on, all the LEDs come on (LED code is FF(h)), and then display different codes as the devices are tested. The LED codes are divided into two ﬁelds.
Page 387: Power-Up And Initialization Led Codes (1111 Xxxx
Diagnostic LED Codes, Continued Error Code The rest of this chapter contains tables listing the LED codes, Tables descriptions, and corresponding FRU. Table B–1 Power-up and Initialization LED Codes (1111 XXXX) Depiction Code Description 1111 1111 Power has been System module applied but no instruction has been run...
Page 388 Diagnostic LED Codes, Continued Table B–1 (Continued) Power-up and Initialization LED Codes (1111 XXXX) Depiction Code Description 1111 1001 Initializing the System module console data structures 1111 1000 Performing auto System module conﬁguration on the machine 1111 0111 Testing the NVR System module device 1111 0110...
Page 389: Toy And Nvr Led Codes (0001 Xxxx
Diagnostic LED Codes, Continued TOY/NVR LED Table B–2 TOY and NVR LED Codes (0001 XXXX) Codes LED Depiction Code Description 0001 0000 TOY and NVR System module clock test has failed 0001 0001 TOY and NVR System module test has failed LCSPX LED Table B–3 LCSPX LED Codes (0010 XXXX) Codes...
Page 390: Spxg/Gt Led Codes (0010 Xxxx
Diagnostic LED Codes, Continued If the graphics option fails, the system may not display a console error message. In this case you must use the error LEDs on the lights and switches module to isolate the fault. SPXg/gt LED Table B–4 SPXg/gt LED Codes (0010 XXXX) Codes LED Depiction Code...
Page 391: Dz Led Codes (0011 Xxxx
Diagnostic LED Codes, Continued DZ LED Codes Table B–5 DZ LED Codes (0011 XXXX) LED Depiction Code Description 0011 0000 DZ Test has System module been entered 0011 0001 DZ Reset test System module has failed 0011 0010 DZ Modem System module test has failed 0011 0011...
Page 392: Cache Led Codes (0100 Xxxx
Diagnostic LED Codes, Continued CACHE LED Table B–6 Cache LED Codes (0100 XXXX) Codes LED Depiction Code Description 0100 0001 Error in the System module data store read /write 0100 0010 Error in the System module read/write to the tag area 0100 0011 The cache did System module...
Page 393: Memory Fru Led Codes (0101 Xxxx
Diagnostic LED Codes, Continued Memory LED Table B–7 Memory FRU LED Codes (0101 XXXX) Codes LED Depiction Code Description 0101 0000 Memory byte System module or mask test has memory modules failed 0101 0001 Memory error System module or occurred in the memory modules forward pass 0101 0010...
Page 394: System Device Led Codes (1000 Xxxx
Diagnostic LED Codes, Continued System Device Table B–8 System Device LED Codes (1000 XXXX) LED Codes LED Depiction Code Description 1000 0000 ROM Verify System module test has failed 1000 0001 Interrupt System module controller test has failed NI Device LED Table B–9 NI LED Codes (1001 XXXX) Codes LED Depiction...
Page 395: Scsi Device Led Codes (1010 Xxxx)
Diagnostic LED Codes, Continued Table B–9 (Continued) NI LED Codes (1001 XXXX) LED Depiction Code Description 1001 0111 NI Receive System module MISS /BUFFER test has failed 1001 1000 NI Collision System module test has failed 1001 1001 NI Address System module ﬁltering test has failed...
Page 396: Audio Device Led Codes (1011 Xxxx
Diagnostic LED Codes, Continued Table B–10 (Continued) SCSI Device LED Codes (1010 XXXX) LED Depiction Code Description 1010 0100 SCSI Map System module error test has failed 1010 0101 SCSI Minimal Device, System device test has module failed Audio Device Table B–11 Audio Device LED Codes (1011 XXXX) LED Codes LED Depiction...
Page 397: Dsw21 Communication Device Led Codes (1100 Xxxx)
Diagnostic LED Codes, Continued DSW21 Table B–12 DSW21 Communication Device LED Codes (1100 Communications XXXX) Device LED Codes LED Depiction Code Description 1100 0000 Comm option DSW21, System code entered module 1100 0001 Comm option DSW21, System ROM test has module failed 1100 0010...
Page 398: Turbochannel Adapter Led Codes (1100 Xxxx
Diagnostic LED Codes, Continued TURBOchannel Table B–13 lists the TURBOchannel adapter LED codes. Adapter LED Codes Table B–13 TURBOchannel Adapter LED Codes (1100 XXXX) Depiction Code Description 1101 0000 Entry into test TCA module, TCA option 1101.0001 TCA Register test TCA module, TCA option 1101.0010...
Page 399: Appendix C Troubleshooting
Appendix C Troubleshooting Overview In this The tables in this appendix contain information to help you Appendix diagnose problems. The tables list the symptoms, possible causes, and suggest corrective action, as follows: Table C–1, System Problems Table C–2, Monitor Problems Table C–3, Mouse/Tablet Problems Table C–4, Keyboard Problems Table C–5, Drive Problems...
Page 400 Troubleshooting Troubleshooting is the process of isolating and diagnosing Overview problems with the system. When the system does not operate as described in the VAXstation 4000 Model 90 Owner’s Guide (EK- PVAX2-OM), use the information in this section to help diagnose the problem.
Page 401 Troubleshooting, Continued Table C–1 (Continued) System Problems Symptom Possible Cause Corrective Action Wall socket may Try a different wall socket, not be operative. or try an electrical device that you know works in the wall socket. Turn the system off for 10 seconds.
Page 402 Troubleshooting, Continued Table C–1 (Continued) System Problems Symptom Possible Cause Corrective Action Alternate console Turn the power off. Move switch is in the alternate console wrong position. switch to the down (off) position. Use a small pointed object. Do NOT use a pencil to set the switch.
Page 403 Troubleshooting, Continued Table C–1 (Continued) System Problems Symptom Possible Cause Corrective Action Power supply Correctly connect power connector to source to CPU module. system module is not seated correctly. Power-up display Possible system Enter the SHOW ERROR contains an error error.
Page 404: Monitor Problems
Troubleshooting, Continued Table C–1 (Continued) System Problems Symptom Possible Cause Corrective Action Incorrect boot Change the default device was recovery action to boot the speciﬁed. system from the system disk. Expansion Turn the system box off, boxes were not make sure the expansion powered on ﬁrst.
Page 405 Troubleshooting, Continued Table C–2 (Continued) Monitor Problems Symptom Possible Cause Corrective Action Contrast and Adjust the contrast and brightness brightness controls. Refer controls are to the monitor guide for set incorrectly. more information. Alternate console Turn off the system. switch is not set Change the alternate correctly.
Page 406: Mouse/Tablet Problems
Troubleshooting, Continued Mouse/Tablet Problems Table C–3 Mouse/Tablet Problems Symptom Possible Cause Corrective Action System boots Pointing device Turn off the system. but mouse or cable is installed Disconnect then reconnect optional tablet incorrectly or is the cable to rest the pointer does loose.
Page 407: Drive Problems
Troubleshooting, Continued Table C–4 (Continued) Keyboard Problems Symptom Possible Cause Corrective Action Keyboard strokes – Disconnect then reconnect are inconsistent. in the keyboard. Keyboard has Replace the keyboard. failed. Drive problems Table C–5 Drive Problems Symptom Possible Cause Corrective Action Software does No diskette is Insert a diskette with...
Page 408 Troubleshooting, Continued Table C–5 (Continued) Drive Problems Symptom Possible Cause Corrective Action Two SCSI Reset each SCSI ID to a identiﬁers are unique number. set to the same ID number. Loose cables. Verify that all cables are securely connected. Defective drive. Run diagnostics to isolate fault.
Page 409 Troubleshooting, Continued Table C–6 (Continued) Network Problems Symptom Possible Cause Corrective Action Network switch If Ethernet is not being is not set used, move the network correctly. switch to the left, toward standard Ethernet. Terminator is Determine if a ThinWire missing from cable was removed.
Page 410: Audio Problems
Troubleshooting, Continued Audio Problems Table C–7 Audio Problems Symptom Possible Cause Corrective Action No audio tone Speaker is Turn on speaker using the (beep) when the turned off. switch located on the front system is turned of the system box. Audio speaker is Turn off the system.
Page 411 Troubleshooting, Continued Table C–8 (Continued) Expansion Box Problems Symptom Possible Cause Corrective Action Power light is Power cord is not Ensure that the power off. connected. cord is connected at both ends. Wall socket may Try a different wall socket, not be operative.
Page 413: Appendix Dfru Part Numbers
Appendix D FRU Part Numbers Overview In this The tables in this chapter provide the names and part numbers Appendix for the ﬁeld replaceable units (FRUs) for the Model 90 system box. The tables in this chapter are organized as follows: Table D-1, System Box FRUs Table D-2, System Monitors Table D-3, Miscellaneous Hardware...
Page 414: Precautions
Precautions Only qualiﬁed service personnel should remove or install FRUs. Overview Electrostatic discharge (ESD) can damage integrated circuits. Always use a grounded wrist strap (part number 29-11762-00) and grounded work surface when working with the internal parts of the workstation. NOTE It is the customer’s responsibility to back up the software before Digital Services personnel arrive at the...
Page 415: Model 90 System Box Frus
Model 90 System Box FRUs Table D–1 contains the part numbers for the Model 90 FRUs. Table D–1 System Box FRUs Part Number Description Modules 54-21177-01 KA49 System board 54-20377-01 Lights and switches module 54-20377-01 DSW21 Communications module PV21X-DA 54-20430-01 TURBOchannel Adapter DWCTX-BX 54-20764-02 SCSI-FDI Control module (forRX26)
Page 416: System Monitors
Model 90 System Box FRUs, Continued Table D–1 (Continued) System Box FRUs Part Number Description Memory Modules 54-19145-AA (MS44L-AA) 4-MB cost-reduced SIM module 54-19103-AA (MS44-AA) 4-MB SIM module 54-19103-CA (MS44-CA) 16-MB SIM module Internal Storage *RZ23-E RZ23 104-MB Drive with logic module RZ23L-E RZ23L 121-MB Drive (70-28115-01) RZ24-E...
Page 417: Miscellaneous Hardware
Model 90 System Box FRUs, Continued Table D–2 (Continued) System Monitors Part Number Description VRT19- 19" Color (DA,*D3,D4),HA,H4 VRM17- 17" Color HA,H4,(AA,A4) *VR297-DA,D3,D4 19" Color *VR299-DA,D3,D4 19" Color *VR319-CA/C4 19" Monochrome Table D–3 Miscellaneous Hardware Part Number Description BC13M-10 Remote keyboard and mouse kit LK401-AA Keyboard VSXXA-DA...
Page 418: Cables And Terminators
Model 90 System Box FRUs, Continued Table D–3 (Continued) Miscellaneous Hardware Part Number Description 70-28107-01 Top plastic cover 74-40430-01 Bracket for mounting 5 1/4 in half- height drives 74-41127-01 Bracket for mounting RX26 half-height removable media and FDI module 74-41128-01 Bracket for mounting half-height 3 1/2 in drives 74-41128-02...
Page 419 Model 90 System Box FRUs, Continued Table D–4 (Continued) Cables and Terminators Part Number Description 17-02876-01 Internal wire harness power cable 17-02906-01 Cable assembly, high res 10 ft monitor cable (BC29G-09) 17-03345-01 External audio adapter cable 17-00285-00 SCSI Signal cable (from FDI to RX26) 70-28108-01 Internal SCSI Data Cable Assembly 70-26209-01...
Page 420: Turbochannel Option Cables
Model 90 System Box FRUs, Continued Table D–4 (Continued) Cables and Terminators Part Number Description 17-00606-10 System power cable (IEC to 3-prong ac 6-ft cable) 17-00365-19 System power cable for Europe 17-00442-25 System-to-monitor power cable (IEC to IEC 39-inch cable) 17-02446-02 External SCSI cable Table D–5 TURBOchannel Option Cables...
Page 421: Expansion Box Frus
Expansion Box FRUs Table D–6 contains the part numbers for the expansion box. Table D–6 Stand-Alone Tabletop Devices Part Number Description RWZ01-AA Optical disk RRD42-DA RRD42 CD ROM Reader Table D–7 SZ16 Expansion Box FRUs Part Number Description 29-27889-01 RZ56 PCB 29-27890-01 RZ56 HDA RZ57-E...
Page 422 Expansion Box FRUs, Continued Table D–8 SZ16 Expansion Box Miscellaneous Hardware Part Number Description BA46X-AA (70-28107-01) Vertical stand BA46X-AB Double removable media drive bracket H9855-AA Multiple box stand 70-28097-01 SCSI Bracket Assembly 70-28099-01 Front bezel, blank 70-28099-02 Front bezel opening for 5 1/4 in drive 70-28099-03 Front bezel opening for 3 1/2 in drive 70-28096-01...
Page 423: Sz16 Expansion Box Cables And Terminators
Expansion Box FRUs, Continued Table D–9 SZ16 Expansion Box Cables and Terminators Part Number Description 12-30552-01 SCSI Terminator 17-00606-10 Power cable (IEC to 3-prong ac 6-ft cable) 17-02445-01 Internal SCSI ID select cable 17-02446-02 External SCSI cable 17-02876-02 Internal wire harness power cable 17-00365-19 Power Cable for Europe 70-28109-01...
Page 424 Expansion Box FRUs, Continued Table D–11 SZ03 Miscellaneous Hardware Part Number Description 12-30934-01 Screw, sems 6-32 PAN .250 TORX 74-43972-01 Bracket, RX26 drive 90-00001-49 Standoff, male/female for mounting disk drives 90-00049-47 B Screw,sems 6-32 pan 90-07801-00 Washer, helical split SST 90-11187-01 C Screw, sems, drive position Table D–12 SZ03 Cables and Terminators...
Page 425 Index Central Processing Subsystem, 1–7 Chip Locations, 1–4 COMM System Test Error Messages, A–86 COMM Utilities, A–95 Adapter board Conﬁguration inserting TURBOchannel (ﬁg.), 6–58 displaying, 5–8 to 5–10 Adapter Component Descriptions, 6–52 TURBOchannel, 5–11 Alternate consoles Conﬁguration Register, 1–8 during power-up, 2–3 Conﬁguration table Network console, 4–25 device, 2–26...
Page 426 Console commands Driver descriptor (cont’d) SET/SHOW (cont’d) overview, 2–27 SCSI, 4–17 Drive removal, 6–8 TRIGGER, 4–18 DSW21 removal, 6–41 Console devices, 2–5 Console driver interface, 2–31 replacement, 6–41 DSW21 communications device Console mode, 2–5 Console Mode error codes, A–48 to A–86 Input and Output, 2–5 removal, 6–41 utilities error codes, A–76...
Page 427 Error Messages (cont’d) SYS Device, A–21 TOY/NVR, A–8 Error reporting General Exception and Interrupt Handling, console error codes 5–56 FRU, A–6 Graphics Controller, 1–26 Errors Graphics module Correctable ECC, 5–76 removal, 6–27 uncorrectable ECC, 5–73 Graphics Subsystem, 1–7 Ethernet Interface, 1–9 LCSPX, 1–7 Exceptions, 1–17 SPXgt, 1–7...
Page 428 MEM SIM module FRU Values, A–17 Metal ﬁller plate function of, 6–52 MIPS/REX emulator, 5–53 KA49 error messages, A–63 system module, 1–5 Module removal KA49 CPU Module, 1–1 CPU module, 6–39 graphics module, 6–27 light and switches module, 6–23 memory module, 6–25 LCSPX Module, 1–26 Module replacement LCSPX Self-test...
Page 429 RFI gasket position, 6–32 ROM Firmware, 1–8 ROM Overview, 1–25 RRD42 (CDROM) drive Password replacement, 6–14 console, 4–16 RRD42 CDROM drive features, 4–16 removal, 6–14 system Running a Utility, 2–8, 5–43 clearing, 6–47 RX26 (diskette) drive Patchable Control Store removal, 6–16 Error messages, 5–102 replacement, 6–16 Performing I/O, 2–31...
Page 430 System box (cont’d) SGEC, 1–9 speciﬁcations, 3–12 Shared console interface area overview, 2–32 System console commands SHOW see Console commands ERROR, A–4 System cover SHOW CONFIG, 4–7, 5–9 removal, 6–7 SHOW DEVICE, 5–8 replacement, 6–48 SIM module (Single in-line memory System devices module), 6–28 external, 3–11...
Page 431 TURBOchannel option (cont’d) removing the ﬁller plate (ﬁg.), 6–57 shipping contents, 6–53 SHOW CONFIG display for (ﬁg.), 6–62 Test Dispatcher, 2–6 speciﬁcations (tab.), 6–63 Testing TURBOchannel Option, 6–50 TURBOchannel installation, 6–62 inserting, 6–60 Testing the Installation, 6–62 TURBOchannel Option Components, 6–53 Testing the System, 6–48 TURBOchannel Option Removal, 6–54 Test Numbers...
Page 432 VMS Error Logging and Event Log Entry, 5–60 Voltage select, 3–3 VAXsimPLUS, 5–56 error handling, 5–57 event record translation, 5–68 Watch Chip Registers, 1–30 Wrist strap, 6–2 Index–8...

Digital Equipment VAXstation 4000 90 Service Information

Preface

1 System Module

2 Firmware

3 System Conﬁguration

4 Using the Console

5 Diagnostic Testing

6 Frus Removal and Replacement

Appendix A Diagnostic Error Codes

Appendix B Reading the Diagnostic LED Codes

Appendix C Troubleshooting

Appendix Dfru Part Numbers

Quick Links

Need help?

Questions and answers

Related Manuals for Digital Equipment VAXstation 4000 90

Summary of Contents for Digital Equipment VAXstation 4000 90