Digital Equipment Corporation VAXstation 4000 Model 90 Service Information EK-KA490-SV.
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. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license.
Contents Preface 1 2 3 4 System Module Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Central Processor Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interrupts and Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cache Memory .
5 6 System Console Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alternate Consoles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2 4–25 Diagnostic Testing Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Diagnostic Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Power-Up Test . . . .
Installing the TURBOchannel Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TURBOchannel Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–55 6–63 Appendix A Diagnostic Error Codes Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Self-Test Error Messages .
2–6 2–7 2–8 2–9 2–10 2–11 2–12 3–1 3–2 3–3 3–4 5–1 5–2 5–3 5–4 5–5 5–6 5–7 5–8 5–9 5–10 5–11 5–12 5–13 5–14 5–15 5–16 6–1 6–2 6–3 6–4 6–5 6–6 6–7 6–8 6–9 6–10 6–11 6–12 Main Configuration Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device Configuration Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Driver Descriptor Data Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6–13 6–14 6–15 6–16 6–17 6–18 6–19 6–20 6–21 6–22 6–23 6–24 6–25 Installation Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the SPXg 8-plane Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing the SPXgt 24-Plane Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the SPXgt 24-Plane Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4–6 4–7 5–1 5–2 5–3 5–4 5–5 5–6 5–7 5–8 5–9 5–10 5–11 6–1 6–2 6–3 6–4 6–5 6–6 6–7 6–8 6–9 A–1 A–2 A–3 A–4 A–5 A–6 A–7 A–8 A–9 A–10 A–11 A–12 A–13 A–14 A–15 A–16 A–17 Processor Control Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BOOT Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Diagnostic Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A–18 A–19 A–20 A–21 A–22 A–23 A–24 A–25 A–26 A–27 A–28 A–29 A–30 A–31 A–32 A–33 B–1 B–2 B–3 B–4 B–5 B–6 B–7 B–8 B–9 B–10 B–11 B–12 B–13 C–1 C–2 C–3 C–4 C–5 C–6 C–7 C–8 D–1 D–2 AUD Self-Test Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Synch Comm Device Test Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TURBOchannel Adapter Self-Test Error Codes . . . . . . . . . . . . . . . . . . . . . . . . .
D–3 D–4 D–5 D–6 D–7 D–8 D–9 D–10 D–11 D–12 Miscellaneous Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cables and Terminators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TURBOchannel Option Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stand-Alone Tabletop Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SZ16 Expansion Box FRUs . . . . . . .
Preface Overview Purpose and Audience This manual is a support and reference document for Digital 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. Organization This manual is organized as follows: Chapter 1, System Module, provides an overview of the Model 90 features, main memory, network interface, and SCSI controller.
Overview, Continued Organization (continued) Appendix A, Diagnostic Error Codes, contains tables listing 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.
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. PN Part number Ctrl/C This type of key sequence means you hold down the first key while you type the letter of the next key. THIS TYPEFACE Indicates text the system displays. THIS TYPEFACE Indicates user input.
Chapter 1 System Module Introduction In this Chapter This chapter describes the features of the VAXstation 4000 Model 90 system module.
System Overview Overview The KA49 CPU module combines with either the 4-MB or 16-MB (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.
System Overview, Continued CPU Components Table 1–1 lists the major hardware components found on the KA49 CPU module.
System Overview, Continued Chip Locations Figure 1–1 shows the major chip locations on the KA49 CPU module.
Central Processor Unit Overview Figure 1–2 shows how, functionally, the KA49 CPU module is divided into five major areas.
Central Processor Unit, Continued Figure 1–2 KA49 CPU Module Block Diagram G-BITS 256KB CACHE & TAG NVAX NCA CP1 DC7238 XCVR CEAC SQWF TURBO CHANNEL GRPHCS ADAPT NMC SGEC CP2 CONSOLE ROMS NDAL LCSPX DC7238 XCVR DMA RAMS QUART SCSI SPXG & GT EDAL TOY SYNC COM Memory SIMMS 16-128 MEG LEDS CNFG REG SOUND EID ROM LJ-01816-TI0 Continued on next page 1–6
Central Processor Unit, Continued Central Processing Subsystem The NVAX CPU (DC246) chip is the heart of the KA49 CPU module. It executes the VAX base instruction group as defined in the VAX Architecture Reference Manual plus the optional VAX 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.
Central Processor Unit, Continued System Support Subsystem The system support subsystem handles the basic functions required to support the console in a system environment. This subsystem contains the firmware ROMs, the firmware ROM controller, the configuration register, and the station address ROM. Resident firmware ROM is located on four chips, each 128 KB by 8 bits of programmable FLASH EPROM1 , for a total of 512 KB of ROM. The firmware gains control when the CPU halts.
Central Processor Unit, Continued Sound generator Four asynchronous lines Time-of-Year clock Ethernet identification ROM NVAX CP-Bus Bus Adapter To provide buffering and connection to the I/O devices, the KA49 contains a DC243, NDAL to CDAL adapter (NCA). The NCA provides an interface between the NVAX NDAL bus and two CPBuses where the I/O device adapters reside. As a bus adapter, the NCA controls transactions between the higher performance NDAL bus and the lower performance CP-Buses.
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 Generator Sound output uses the DTMF tone generation capability of the 79C30 chip.
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. The NMC controls transactions between the main memory and the NVAX, and between main memory and any of the I/O devices (through the NCA interface).
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. The KA49 implements 16 GPRs, as defined in the VAX Architecture Reference Manual.
Central Processor Unit, Continued Internal Processor Registers The internal processor registers (IPRs) that are implemented by the KA49 CPU chip, and those that are required of the system environment, are logically divided into five 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 Bcache Deallocate IPRs—The write-only block of IPRs by which a Bcache bloc
Interrupts and Exceptions Overview Both interrupts and exceptions divert execution from the normal flow 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 overflow).
Interrupts and Exceptions, Continued Interrupt Priority Levels Table 1–3 lists KA49 interrupt conditions, associated priority 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.
Interrupts and Exceptions, Continued Table 1–3 (Continued) Interrupt Priority Levels Priority Level Interrupt Condition SCB Offset 1A Correctable main memory errors 54 Uncorrectable main memory errors 54 Correctable O-bit memory errors 54 Pending read times out waiting for disown write 54 No acknowledgment on returned read data from NMC 54 NDAL Data parity errors 54 Pcache tag or data parity errors 54 VIC tag or data parity errors 54 Bcache addressing errors 54 Bcache correctable data
Interrupts and Exceptions, Continued Table 1–3 (Continued) Interrupt Priority Levels Priority Level Interrupt Condition SCB Offset 16 IRQ_H[2] asserted Unused Interval timer (IRQ_H[2] takes priority) C0 15 IRQ_H[1] asserted 14 IRQ_H[0] asserted Network interface 13:10 Unused 0F:01 Software interrupt requests 104 84-BC ** These conditions generate a hardware halt procedure with a halt code of 2 (external halt). Exceptions There are six categories of exceptions.
Interrupts and Exceptions, Continued Table 1–4 Exception Categories Types of Exceptions Exception Class Instances Arithmetic traps/faults Integer overflow trap Integer divide-by-zero trap Subscript range trap Floating overflow fault Floating divide-by-zero fault Floating underflow fault Memory management exceptions Access control violation fault Translation not valid fault M=0 fault Operand reference exceptions Reserved addressing mode fault Reserved operand fault or abort Instruction execution ex
Interrupts and Exceptions, Continued Trap Exceptions A trap is an exception that occurs at the end of the instruction that caused the exception. Therefore, the PC saved on the stack is the address of the next instruction that would normally have been executed. Fault Exceptions A fault is an exception that occurs during an instruction and that leaves the registers and memory in a consistent state such that elimination of the fault condition and restarting the instruction will give correct results.
Cache Memory Overview The NVAX memory subsystem follows a hierarchical structure. The VIC, Pcache, Bcache, and finally 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. For I-stream references, the memory hierarchy starts with the VIC, whereas for D-stream references the memory hierarchy starts with the Pcache.
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. Furthermore, this problem is complicated by the writeback nature of the Bcache.
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.
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. The Bcache allocates on reads and writes, and uses a write-back protocol.
Main Memory System Overview The main memory system is implemented in the NVAX memory 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. The NMC serves as an interface between the NDAL and NVAX memory interconnect. The NMI is comprised of the set of signals leading from the NMC to the memory modules, and provides a 64-bit path to the memory modules.
ROM Memory Overview The system board ROM contains processor restart, diagnostic and console code, and the primary bootstrap program. Another small ROM is uniquely programmed for each system with its network address. System Board ROM The system board ROM contains four 128 KB x 8 FLASH ROM chips that collectively hold 512 KB of data. ROM data appears at physical addresses 2004.0000 through 200B.FFFF. The data path to this ROM is 32 bits wide. Certain physical addresses in the ROM have fixed uses.
Graphics Controller Overview The VAXstation 4000 Model 90 workstation supports three 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. Note that only one video option can be physically installed into the workstation at a time. All the graphics options share a single interrupt request signal and interrupt vector.
Graphics Controller, Continued Table 1–6 Diagnostic ROM/Configuration Register Bit Definitions Bit Name Definition <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> Reserved Read as zero. <17> MSB This bit indicates the speed of the oscillator used as timing for the 1280 X 1024 monitor. A zero indicates 66 Hz operation, a one indicates 72 Hz operation.
Network Interface Controller Overview 1–28 The KA49 includes a network interface that is implemented by 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. The SGEC also supports CP-Bus parity protection.
Serial Line Controller Overview The serial line controller handles four asynchronous serial lines. 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. The four serial lines are numbered 0 through 3, and each has a particular primary use, as described in Table 1–7.
Time-of-Year Clock Overview The time-of-year (TOY) clock consists of an MC146818BM CMOS 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. Battery Backup A lithium battery within the watch chip supplies power to the watch chip and its time base oscillator while system power is off.
SCSI Controller Overview The SCSI interface is a single-ended, bi-directional, 8-bit-wide bus 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. An initiator originates an operation by sending a command to a specific target. A target performs an operation that was requested by an initiator.
SCSI Controller, Continued SCSI Bus Signals Table 1–8 describes the SCSI bus signals used by the SCSI 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. These lines may be driven by either an initiator or a target, depending upon the direction of data transfer. RST Signals all devices on the SCSI bus to reset to their initial poweron states.
DSW21 Synchronous Communications Adapter Overview The DSW21 syncrhonous communications adapter is a 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.
DSW21 Synchronous Communications Adapter, Continued Figure 1–5 DSW21 Connections 50-PIN CONN 64-PIN CONN 128K BYTE PROM 256K BYTE SRAM EDAL T X I/O RAW PAL CONTROL LOGIC MC68302 IMP R X INTERRUPT LJ-02225-TI0 1–34
Chapter 2 Firmware Overview Introduction This chapter provides an overview of the VAXstation 4000 Model 90 system firmware. The firmware is located in four EPROMs, which hold a total of 512 KB of data. The system firmware has five distinct areas of operation.
Power-Up Initialization Code Overview The power-up initialization code is executed when power is applied to the VAXstation 4000 Model 90 workstation or any time volatile console data structures are altered. Power-Up Initialization Sequence Table 2–1 describes the power-up initialization sequence. Table 2–1 Power-Up Initialization Sequence Stage What the System Does 1 Tests enough memory to bring up the console for building console and device structures.
Power-Up Initialization Code, Continued Table 2–1 (Continued) Power-Up Initialization Sequence Stage What the System Does 5 Tests the serial lines. If this test fails, the console terminal is not enabled and the only output is the HEX display. 6 If... And... Then... No video option is present —– The system defaults to line three of the serial port.
Power-Up Initialization Code, Continued Table 2–1 (Continued) Power-Up Initialization Sequence Stage What the System Does 7 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.
Console Mode Overview The VAXstation 4000 Model 90 console mode allows operation of a 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: The HALT parameter is set to halt when power is turned on.
Extended Self-Test Overview The extended self-tests are started by entering the TEST 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 configuration table (MCT), device configuration table (DCT), and drive descriptor data structures when running a self-test.
Extended Self-Test, Continued Table 2–2 (Continued) Test Dispatcher Procedure Stage What the Dispatcher Does 6 Reads the flags field in the DCT to determine if the diagnostic uses a shared diagnostic driver. 7 If... Then... The self-test diagnostic uses a shared diagnostic driver The dispatcher gets the directory entry and the pointer to the driver descriptor from the DCT.
Utilities Overview A utility test is started at the console prompt by entering a command using the following format: TEST/UTIL dev_nbr util_nbr op1...opn Running a Utility 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 One to n optional parameters The console mode passes a list of parameters to the test dispatcher.
Utilities, Continued Table 2–3 (Continued) Running a Utility Process Stage Dispatcher Process 6 Reads the flags field in the DCT to determine if the utility uses a shared diagnostic driver. If... Then... The utility uses a shared diagnostic driver The dispatcher gets the directory entry and the pointer to the driver descriptor from the DCT.
System Test Overview The system test tests the device interaction in the system by creating maximum DMA and interrupt activity. The test consists of: Modified 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. Customer - 1 Digital Services - 2 Manufacturing - 3 CAUTION Do not use the manufacturing mode in the field.
System ROM Overview The base VAXstation 4000 Model 90 firmware contains 512 KB of 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 ROM 3 ROM 2 ROM 1 ROM 0 byte 3 byte 2 byte 1 byte 0 2004.0000 byte 7 byte 6 byte 5 byte 4 2004.0004 byte B byte A byte 9 byte 8 2004.0008 LJ-01818-TI0 The system firmware ROMs supply some information on a per byte basis for ease of manufacture and development.
System ROM, Continued Figure 2–2 System ROM Part Format 15.. ..8 7.. ..
System ROM, Continued System ROM Part Format Table 2–4 shows the part formats in the system ROM. 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 firmware. 03h ROM byte number Indicates the position of the byte among the set of ROMs used to implement the firmware. This value is equal to the low 2 bits of the physical address of the first byte in the ROM part.
System ROM, Continued System ROM Set Format Table 2–5 shows the physical addresses in the system ROM. These addresses are fixed. 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. Kernel mode halt instruction executes. A break signal is received from the console device. The HALT button is depressed. The CPU detects a severe corruption of its operating environment. 2004.
System ROM, Continued Table 2–5 (Continued) System ROM Physical Addresses Physical Address Name Description 2004.008A System diagnostic firmware revision number This word contains the system diagnostic firmware revision number. 2004.008C Diagnostic descriptor This longword contains the physical address of the beginning of the system level diagnostic boot block. A value of zero indicates that there is no system level diagnostic present in the Model 90 system firmware ROM. 2004.
Option ROM Overview Each option in the Model 90 system has its own ROM firmware. The ROM memory on the option board may be implemented as discussed in the following sections. Option ROM Part Format The option ROM part format is provided for each byte in the ROM set. This format is compatible with the system ROM format, with the addition of the data path indicator. Figure 2–3 shows the ROM byte data.
Option ROM, Continued Byte Name Description 00h Data path indicator Indicates the size of the ROM data 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. Words in ROM occupy the low two bytes of each longword. 4: Four bytes per longword. Longwords in ROM correspond to longwords in the address space. 02h Version Contains the low 8 bits of the version number for the option firmware.
Option ROM, Continued Byte Name Description 07h ROM part length Indicates the length of each byte 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. Each of the ROM parts on the option board must have the same number of bytes. Option ROM Set Format 8 Reserved Reserved for ROM set data.
Option ROM, Continued Name Description Option revision This number controls changes in both the option hardware and firmware. Option index value An index value of the last DCT entry. A zero in this field indicates a single DCB for the device, a one indicates two device control blocks for this device. An option that occupies the storage option slot can have the values of zero or one. An option that occupies the video option slot can have the values of zero, one, or two.
Configuration Table Overview Information on the VAXstation 4000 Model 90 devices is stored in the system configuration tables during the power-up initialization. The initialization code sizes the system by reading the ROM-based device configuration tables (DCT) and builds a memory resident configuration data structure. Figure 2–5 shows how the data structures are linked together.
Configuration Table, Continued Figure 2–6 Main Configuration Table Minor Version ID Major Version ID Number of Devices Edit Version ID 0 Device ID Pointer to Device Configuration Table 0 Device ID Pointer to Device Configuration Table 0 Number of Devices *8 Device ID Pointer to Device Configuration Table (Number of Devices *8)+4 LJ-00104-TI0 The components of the MCT are as follows: Table 2–6 MCT Components Name Description Major version ID Tracks major changes in the diagnostic interface
Configuration Table, Continued Table 2–6 (Continued) MCT Components Name Description Pointer to device configuration table1 Points to the DCT for the particular device 1 Replicated Device Configuration Table for each device in the system. There is a device configuration table (DCT) entry for each device in the Model 90 system.
Configuration Table, Continued Figure 2–7 Device Configuration Table Minor Version ID Major Version ID 0 Number of Devices Edit Version ID 4 Device Name 8 Pointer to Driver Descriptors 10 Device Status 14 Pointer to Extended Status 18 Size of Extended Status 1C Pointer to Extended Config 20 Pointer to Permanent Memory 24 Size of Permanent Memory 28 System Test Status 2C Pointer to Extended System Test Status 30 Size of Extended System Test Status 34 Flags Flags DPSIZE DIRTYP
Configuration 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 devices Number of directory entries for the device. A directory entry tells the user where to find a particular component of code for the device. Edit version ID Device ID number Device name Device Name is ASCII.
Configuration Table, Continued Table 2–7 (Continued) DCT Components Name Description Size of permanent memory Amount of permanent memory (in pages) that has been allocated. This field is filled in by the diagnostic the first time that it allocates memory. System test status Saved the last time that system test was ran on this device without doing intervening test commands. Pointer to extended system test status Points to any extended information that is saved by the device’s selftest.
Configuration 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. DIRTYP Definition Meaning 1 ROM Width is one byte wide. 2 ROM Width is two bytes wide. 4 ROM Width is four bytes wide. Contains the type of directory entry that the previous elements refer to.
Driver Descriptor Overview Any device that provides a shared port driver or shared class driver must provide a descriptor that supplies the Model 90 base system firmware, system test monitor, and any other piece of software specific information about the drive. The format for a driver descriptor is shown in Figure 2–8.
Driver Descriptor, Continued 2–28 Name Description Length of driver Contains the length of the device driver in bytes. This field 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. Entry point of driver Contains the number of bytes from the beginning of the device driver to the INIT_DRIVER function.
Interfacing to Diagnostic Drivers Overview The network device contains routines to UNJAM the device and to 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.
Interfacing to Diagnostic Drivers, Continued Overview (continued) 2–30 Call the INIT_DRIVER routine with the following parameters: — Pointer to the I/O segment table — Pointer to the driver data area — Pointer to the driver function block or console function block — Pointer to the shared console interface area, or display zero if this is not a console driver — As many as two additional device-specific parameters
Console Driver Interface Overview The Model 90 console code is split into a class/port driver scheme. The class driver contains the main console functions, such as PUTCHAR and GETCHAR. The port drivers contain the device specific code required to support these functions. Figure 2–10 shows the division of the console function.
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.
Console Driver Interface, Continued The SCIA data structure is shown in Figure 2–11.
Console Driver Interface, Continued Console Port Driver The fields of the console port drivers driver descriptor are the 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. Figure 2–12 shows the function block of the port driver.
Chapter 3 System Configuration Overview In this Chapter This chapter describes the system box used with the VAXstation 4000 Model 90 workstation and its components, cabling, and specifications.
System Box The BA46 enclosure is used for desktop and floorstand installations of the VAXstation 4000 Model 90 system. Figure 3–1 shows the Model 90 system box and its components.
System Box, Continued Mass Storage Device Areas The Model 90 system box can hold two half-height, fixed media 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). The bottom drive in the H bracket is mounted upside down. The H bracket releases by a single latch and the other bracket uses two release points.
System Box, Continued AC power for system monitor Power Supply Specifications The power supply specifications are listed in the following tables. Input Specifications Parameter Specifications Line voltage 120 V 240 V Voltage tolerance 88 V to 132 V 176 V to 264 V Frequency 60 Hz 50 Hz Frequency tolerance 47 Hz to 63 Hz 47 Hz to 63 Hz Input current 2.9 A (max.) power supply only 4.0 A (max.) AUX only 1.4 A (max.) power supply only 2.0 A (max.) AUX only Inrush current 45.
System Box, Continued Parameter Minimum Specifications Typical Maximum +12.1 V reg. Short term +11.70 V +12.10 V +12.50 V +12.1 V reg. Long term +11.50 V +12.10 V +12.70 V -12.0 V reg. Long term -11.40 V -12.00 V -12.60 V -9.0 V (isolated) Long term -8.55 V -9.00 V -9.45 V +3.3 V Long term +3.13 V +3.3 V +3.46 V +3.3 V +5.1 V +12.1 V -12.0V -9.0 V 3.20 A 2.8 A 0.18 A 0.26 A 0.12 A 6.39 A 19.52 A 3.82 A 0.69 A 0.17 A +3.3 V +5.1 V +12.1 V -12.0 V -9.0 V 20.0 mV 30.0 mV 50.0 mV 30.
System Box, Continued Parameter Minimum Ripple and noise (except +5.1 V and +3.3 V) Ripple and noise 10 MHz to 50 MHz 10 MHz to 50 MHz +5.1 V +3.3 V Specifications Typical Maximum 1.0% 2.0% 30 mV 20 mV 50 mV 30 mV Physical Dimensions Internal Cabling Weight Height Width Depth 14.9 kg (33 lb) 6.99 cm (2.75 in) 11.18 cm (4.4 in) 38.10 cm (15.0 in) The system box internal cabling is shown in Figure 3–2. Note that there is one SCSI cable and one dc power harness connecting to the drives.
System Box, Continued Figure 3–2 Internal Cabling Power Cable SCSI Cable To RX26 Controller Module (Optional) 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 3 SCSI Devices 17-02875-01 Four 50-pin IDC to 50-pin champ (external) SCSI Device dc power harness 17-02876-01 Four 4-pin Mat-N-Loks to 4-pin mini Continue
System Box, Continued System Box Control Panel The controls and indicators for the system box are located behind the flip-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 On/Off Switch Halt Button Diagnostic Lights Front Door MLO-005090 ON/OFF Switch This switch, located on the upper left side of the front bezel and labeled O I, controls ac power to the H7819AA power supply.
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. These lights display two binary fields, which represent a two-digit hexadecimal diagnostic code. I/O Panel The I/O panel provides connectors to devices external to the system.
System Box, Continued Figure 3–4 Model 90 I/O Panel 7 8 4 9 10 6 11 5 3 2 1 LJ-00639-TI0 Continued on next page 3–10
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. to 3 BNC 10 ft (3.0 m) Remote LK/VSXXX (mouse/keyboard) 17-02640-01 15-pin Dsub. to LK/VSXXX 10 ft (3.0 m) DSW21 communications device option BC19x 50-pin Dsub. to x-pin1 2 ft (.
System Box, Continued System Box Specifications The system box specifications are listed in the following tables. Table 3–3 lists the system box operating conditions and Table 3–4 lists the electrical specifications. NOTE The operating clearance is 8.9 cm (3.5 in) minimum on the sides and back of the system box. The service clearance is 15.2 cm (6 in) minimum on all sides of the box.
Chapter 4 Using the Console Overview In this Chapter This chapter describes the system console commands and how to use alternate consoles. Diagnostic commands used to troubleshoot a system are described in Chapter 5.
System Console Commands Standard Console Commands Standard console commands for the VAXstation 4000 Model 90 are listed by functional groups as follows: Operator assistance commands are HELP or the question mark (?), LOGIN, and REPEAT. SET/SHOW commands are used to set or examine system parameters and configuration. Memory commands include the DEPOSIT and EXAMINE commands. Processor control commands are BOOT, CONTINUE, UNJAM, START, and INITIALIZE commands.
System Console Commands, Continued Operator Assistance Commands (continued) REPEAT The REPEAT command repeats a console command entered on the same line following the REPEAT command. BOOT, INIT, and UNJAM cannot be repeated. The commands being repeated are terminated by pressing Ctrl C . Example: This command repeats the memory test. Entering Ctrl/C terminates the test. >>> REPEAT TEST MEM . . .
System Console Commands, Continued SET and SHOW Commands The SET and SHOW commands are used to set and examine system parameters. Table 4–1 lists the SET/SHOW parameters and their meanings.
System Console Commands, Continued Table 4–1 (Continued) SET/SHOW Parameters SET and SHOW Command Syntax Parameter Meaning SET SHOW SCSI System SCSI ID X X TRIGGER Enable network console X X The following is the syntax for the SET and SHOW commands and parameters: Syntax: >>> SHOW parameter >>> SET parameter value BFLG The BFLG parameter is the default bootflag. It is equivalent to R5:xxxxxxxx in the boot command. BFLG is normally set to 0.
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 first column of the table (VMS/VMB) lists the device names. Example: >>> SET BOOT DKA200 BOOT = DKA200 >>> SHOW BOOT BOOT = DKA200 CONFIG The CONFIG parameter displays the system configuration and device status. The SET command does not apply to this parameter.
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 ------ ------ ---1 NVR OK 2 LCSPX OK Highres - 8 Plane 3 4 5 6 7 8 9 10 11 12 DZ CACHE MEM FPU IT SYS NI SCSI AUD COMM 4MPixel FB - V1.0 OK OK OK 16MB 0A,0B,0C,0D = 4MB, 1E,1F,1G,1H = 0MB OK OK OK OK OK 0-RZ24 6-INITR 1-RZ25 2-RRD42 OK OK Response Meaning KA49-A V0.0-051-V4.
System Console Commands, Continued DEVICE Response Meaning 9 NI OK Ethernet 10 SCSI OK SCSI and drives 11 AUD OK Sound 12 COMM OK DSW21 communications 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. >>> SHOW DEVICE VMS/VMB ------EZA0 DKA0 DKA100 DKA200 ..HostID..
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). NUMBYTES Drive capacity. Capacity is not displayed for empty removable media drives. RM/FX Indicates whether the drive has removable or fixed media.
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. Some tests require loopback connectors for successful completion.
System Console Commands, Continued Setting the Diagnostic Environment To set the diagnostic environment, enter a console command listed in Table 4–3. Note that all settings except DIAGENV 1 require a loopback connector be installed. Table 4–3 SET DIAGENV Command Command Result SET DIAGENV 1 Resets environment to customer mode. SET DIAGENV 2 Sets environment to Digital Services mode. SET DIAGENV 3 Sets environment to manufacturing mode.
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 ESTAT The ESTAT parameter displays status information about the system test at the console prompt. The SET command does not apply.
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 FBOOT The FBOOT (fast boot) parameter determines whether the memory is tested when power is turned on. The test time is reduced when main memory is not tested. When FBOOT = 0 the memory is tested on power-up. When FBOOT = 1 the memory test is skipped on power-up. The setting only affects the power-up test.
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 1 System tries to restart the operating system. If restart fails, then the system tries to reboot. 2 System tries to reboot. 3 System halts and enters console mode.
System Console Commands, Continued 0) 1) 2) 3) 4) 5) 6) 7) Dansk Deutsch Deutsch (Schweiz) English English (British/Irish) Espanol Francais Francais (Canadian) 8) 9) 10) 11) 12) 13) 14) 15) Francais (Suisse Romande) Italiano Nederlands Norsk Portugues Suomi Svenska Vlaams >>> 3 KBD = 3 MEM The MEM parameter displays the memory address range and the unavailable memory address range. The unavailable range is memory that is used by the console, and memory that is marked unavailable by the diagnostics.
System Console Commands, Continued MOP 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 >>> SHOW MOP MOP = 00000001 PSE and PSWD The PSE parameter is the enable console password bit. This enables the console password to restrict access to the console. The PSWD parameter is used to set the console password.
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>>> prompt. SCSI This parameter is the SCSI ID for the system. The system SCSI ID should be set to 6. The system SCSI ID should never be changed.
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: >>> SHOW TRIGGER TRIGGER = 00000000 >>> SET TRIGGER 1 TRIGGER = 00000001 Memory Commands The following table lists console commands that manipulate memory and registers. Command Function DEPOSIT Enters values into memory locations or registers.
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 qualifiers and what each one specifies.
System Console Commands, Continued >>> DEPOSIT/P/N:5 00100000 01234567 P P P P P P 00100000 00100004 00100008 0010000C 00100010 00100014 01234567 01234567 01234567 01234567 01234567 01234567 EXAMINE The EXAMINE command displays specific memory locations from the console. Syntax: EXAMINE/QUALIFIERS ADDRESS Table 4–5 lists the qualifiers and what each one specifies.
System Console Commands, Continued The ADDRESS specifies the address (or first address) to be read. Example: This example reads the Ethernet hardware address. >>> EXAMINE/P/N:5 20090000 P P P P P P Processor Control Commands 20090000 20090004 20090008 2009000C 20090010 20090014 0000FF08 0000FF00 0000FF2B 0000FF1B 0000FF48 0000FFE3 Table 4–6 lists the processor control commands and their functions. Table 4–6 Processor Control Commands Command Function BOOT Bootstraps the operating system.
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: >>> boot/qualifier device, second_device Table 4–7 BOOT Command Syntax Term Meaning /qualifier This optional qualifier sets the value for R5 for the bootloader. It is used to select a boot on the disk, or a conversational boot.
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. These commands together reset the system. UNJAM should be entered first.
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. >>> START 200 TEST The TEST command invokes standard diagnostics, extended diagnostics, and utilities. Output from the diagnostics running from direct console commands is to the current console display device.
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.
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: 1. Log in to a user account (no special privileges are required). 2. Type the commands as shown in bold type in this next example. An explanation of the system response is included after the exclamation mark.
Alternate Consoles, Continued 6 7 8 9 10 FPU IT SYS NI SCSI 11 12 AUD COMM OK OK OK OK OK 0-RZ24 OK OK ! Floating point accelerator ! Interval timer ! Other system functions ! Ethernet ! SCSI and drives 1-RZ25 2-RRD42 6-INITR ! Sound ! 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.
Chapter 5 Diagnostic Testing Overview In this Chapter This chapter describes the diagnostic testing and test commands 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.
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 A.
Diagnostic Functions The system firmware 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. Utilities Provide functions for visual screen test, mass storage devices, and the network listener.
System Power-Up Test Overview The system power-up self-test sequentially tests the devices in the 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 configurations take approximately seven minutes to complete the self-test, Additional time is required for SCSI devices.
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. During initialization, the system is configured by creating the main configuration table (MCT) and the device configuration table (DCT). Figure 5–1 Successful Power-Up KA49-A V1.
System Power-Up Test, Continued Figure 5–2 Unsuccessful Power-Up KA49-A V1.
System Power-Up Test, Continued Error Information The general format for error information is: ?? Fru Dev_nbr Dev_nam Err_nbr Format Meaning ?? Two question marks (??) indicate a fatal error; one question mark (?) indicates a non-fatal error. FRU Identifies the field replaceable unit of the device that failed Dev_nbr The device number of the failing function Dev_nam The device mnemonic of the failing function Err_nbr A decimal number that corresponds to a specific device failure.
Displaying System Configuration Configuration Commands The Model 90 firmware provides two configuration 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 configuration. SHOW DEVICE The SHOW DEVICE command determines the presence of storage devices, such as a hard disk, diskette drives, or other drives.
Displaying System Configuration, 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 first character shown is the bus (A or B); the second character represents the device number (3, 5, 6); the third field (00) is not used. DEVTYPE Device type, RODISK is a read-only disk (CDROM). NUMBYTES Drive capacity. Capacity is not displayed for empty removable media drives.
Displaying System Configuration, Continued Example: >>> SHOW CONFIG KA49-A V0.0-051-V4.0 08-00-2B-F3-31-03 16 MB DEVNBR -----1 2 3 4 5 DEVNAM -----NVR LCSPX DZ CACHE MEM INFO ---OK OK Highres - 8 Plane OK OK OK 4MPixel 16MB 0A,0B,0C,0D = 4MB, 6 7 8 9 10 FPU IT SYS NI SCSI 11 12 AUD COMM OK OK OK OK OK 0-RZ24 OK OK 1-RZ25 2-RRD42 FB - V0.8 1E,1F,1G,1H, = 0MB 6-INITR Response Meaning KA49-A V0.0-051-V4.
Displaying System Configuration, Continued Response Meaning 11 AUD OK Sound 12 COMM OK DSW21 Communications device 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. TURBOchannel Configuration The presence of a configuration object is optional. A given TURBOchannel option may or may not have a configuration function. No error occurs if an option has no configuration object.
Displaying Additional Error Information Overview Use the SHOW ERROR utility to obtain detailed error 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. Example: This is an example of the system response if errors are present.
Setting Up the Diagnostic Environment Procedure Selecting a Diagnostic Environment You must take the following actions before running a self-test: Step Action Comment 1 Put the system in console mode. Shut down the operating system or power up the system if you do not have the console prompt. 2 Attach loopbacks if required. See Table 5–4. 3 Select the diagnostic environment. See Table 5–3.
Setting Up the Diagnostic Environment, Continued Setting the Diagnostic Environment To set the diagnostic environment, enter one of the console commands listed in Table 5–3. Note that all diagnostic environments except DIAGENV 1 require a loopback connector. Table 5–3 SET DIAGENV Command Command Result SET DIAGENV 1 Resets environment to customer mode. SET DIAGENV 2 Sets environment to Digital Services mode. SET DIAGENV 3 Sets environment to manufacturing mode.
Device Tests Device Test IDs and Mnemonics Table 5–4 lists the device tests and corresponding mnemonics, decimal ID, binary ID, and loopback requirements.
Device Tests, Continued Running Self-Tests This section describes the test command interface used to run the self-test on a device. Table 5–4 lists the device IDs and mnemonics. Device Test Syntax Rules Table 5–5 describes the syntax used to run device self-tests. Table 5–5 Device Test Syntax Rules If you want to... Then...
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. T 8:10,6,3:5 Figure 5–3 is an example of what the console displays when successful and unsuccessful self-tests have been run.
Device Tests, Continued Devices can be specified 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 5–18 Example Description T 10:8,6,5:3 Tests devices 10 through 8, then device 6, and then devices 5 through 3.
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 DZ 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. TOY/NVR Self-Test (T 1) This is the non-volatile RAM and time-of-year clock self-test.
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. If not, a test of all the TOY registers is performed. This test writes/reads all possible values a TOY register can hold.
Self-Test Descriptions, Continued DZ Self-Test (T 3) 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. The LK401 test fails if the LK401 is not plugged in and the console is a video device. A keyboard and pointing device must be plugged in, or an error is reported.
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. SCSI DMA RAM, OBIT RAM, BCACHE Tests (T 4) This is the cache system self-test. The following tests are included: DATA Store test Tests the data store in the Model 90 primary cache. A two-pass memory test is performed on the data store.
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 filled with AAh. Memory test (forward) Performs a read/compare/complement/write on the memory in the forward direction. If a page is found to be bad, the appropriate bit in the memory bitmap is cleared.
Self-Test Descriptions, Continued Interval Timer Self-Test (T 7) The following test is included: 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 Self-Test (T 8) The following test is included: System ROM test Checks the system ROMs one byte at a time to ensure that they contain the correct manufacturing check data and the correct checksum.
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 Verifies the correct operation of the SGEC transmitter and receiver during an internal loopback. It also verifies the burst-mode DMA read and write on non-word-aligned data buffers for packets of different lengths and data patterns.
Self-Test Descriptions, Continued SCSI Self-Test (T 10) The SCSI self-test is for the SCSI controller. 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 configuration display after running the test, ensure that all devices have a unique ID number. Verify that power is supplied to all devices and the system module.
Self-Test Descriptions, Continued The following tests are included: Register test Verifies that the 53C94A Controller Chip registers are fully functional. All read/write bits that can be written are written to. It also verifies the bits. Interrupt test Verifies the SCSI bits in the interrupt mask register, interrupt request register, and the interrupt clear register. A SCSI interrupt is forced, with the SCSI bit in the interrupt mask first set and then cleared.
Self-Test Descriptions, Continued Audio Self-Test (T 11) The audio self-test tests the sound chip. 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. Audio test The tones are only heard if the switch on the front of the system for headphone/speaker is switched to speaker.
Self-Test Descriptions, Continued EPROM test Checks the EPROM dual access; EPROM bus arbitration. Host Interrupt test Checks the host interrupt; verifies 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. Reset test Resets the communication options and waits for an interrupt.
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. The FIFO is then emptied and the count is checked against the read values from the FIFO.
System Test Environment Configuration Overview The system test is a strenuous test of the workstation. All devices are exercised simultaneously to find system interaction problems. The system test can be used to find 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. Refer to Selecting a Diagnostic Environment for information on selecting an environment.
System Test Monitor Running the System Test This section describes the test command interface to use to run 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. Table 5–8 Running the System Test Using the Test Command Command Action T 100 Runs system test in the customer environment for two passes. T 101 Runs system test in the Digital Services environment for two passes.
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 specific devices. The system prompts you for a specific device; 1 = yes; 0 = no. >>>T 106 Display from the System Test Figure 5–4 shows the response to a successful system test. Figure 5–4 Successful System Test KA49-A V1.0 CU 00 00:02:00.
System Test Monitor, Continued Response Meaning KA49-A The system module ID. V1.0 The ROM version number. CU 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. Figure 5–5 Unsuccessful System Test KA49-A V1.0 UE 00 00:02:00.
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 Summary Screens You can get summary information about the most recent system test using either of the following two methods: Action Result Press Ctrl C . Stops the system test and displays summary screens for the devices.
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.
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. ?? 001 3 DZ 0220 The following is an example of the DZ system test summary screen.
System Test Monitor, Continued Network Interconnect System Test This section explains the Network Interconnect (NI) System test. Setup Notes 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. Maximum testing of hardware occurs on a live network with MOP enabled. The network system test tests the network port using external loopback packets.
System Test Monitor, Continued SCSI System Test This section describes the SCSI system test. CAUTION Do not use manufacturing mode in the field. 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. Ensure that the power cable is connected to the devices and the system module.
System Test Monitor, Continued The following tests are included: Inquiries test Performs inquiries to find 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.
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.
System Test Monitor, Continued In order for writes to occur, a key pattern must be installed on writeable removable media (floppies and tapes). The key pattern is put on the media by the SCSI utilities. This is described in SCSI Utilities. DSW21 Communication System Test The system test loads and runs 68302 test/scheduler. The following shows a DSW21 communication system test error: ?? 12 COMM 020 001E 0 00:00:15.
Utilities Overview TEST commands run or display available utilities. Utilities can 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. >>> T [EST]/UT[ility] dev_nbr util_nbr opt_p1,...,opt_pn Running a Utility Format Meaning dev_nbr The number of the device on which you want to run the utility.
Utilities, Continued Step Action Comment 1 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>>>. 2 Enter the utility number that you want to run. In Figure 5–7, utility 8 is selected. 3 Press Return at the prompt to exit the utility. 4 Press the space bar to return to the utility menu after the utility has run.
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 SPX_util>>> 8 LJ-02217-TI0 If you run a utility that will destroy the contents of a mass storage device, the following appears: dev_nam OK ? dev_nam is the name of the device whose contents will be lost.
Utilities, Continued The console firmware provides the following utilities: Utility Group Functions LCSPX/SPXg/gt (2) Provides colored screens and geometric patterns. NI Use the SET and SHOW commands for: MOP - NI listener Trigger - Entity-Based Module (EBM) LCSPX Utility SCSI (10) Key utilities, floppy formatter, and disk eraser TCA (13) TURBOchannel configuration display The LCSPX utility provides fourteen screens of color bars and geometric programs.
Utilities, Continued LCSPX Utility Menu The following is an example of the LCSPX utility menu. An explanation of the items is included to the right of the menu. See Figure 5–7.
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. The operation of the NI listener is transparent to the console, and NI listener errors are not reported. Listener failure can only be detected with the use of a network monitor device.
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. The key utility writes a key on block 0 of the floppy media. The key is used by the System test in Digital Services mode.
Utilities, Continued Invoking SCSI Utilities The next table describes how to invoke the SCSI utilities. Table 5–10 Invoking SCSI Utilities SCSI Utility Menu Step Action Result 1 Enter the T/UT SCSI command. Displays the SCSI Utility Menu. 2 Enter the utility number. Selects the utility. 3 Enter the SCSI ID. Selects the drive. 4 Enter the SCSI LUN (always 0). Logical unit number (LUN). 5 Enter OK if requested. Verifies action for formatter and erases the utilities.
Utilities, Continued Command Comment T/UT 10 Enter this command (or T/UT SCSI) 1 - SCSI-flp_key Floppy key utility. 2 - SCSI-tp_key Tape key utility. 3 - SCSI-hd_dis_eras Hard disk erase. 4 - SCSI-flp_fmt Floppy formatter. SCSI_util>>> 3 Enter the utility number. SCSI_id(0-7)>>> 5 Enter the SCSI device ID. SCSI_lun(0-7)>>> 0 Enter the SCSI logical unit number (always 0). DKA500 OK ? ok Confirm the action. ############# Progress banner on ERASE and FORMAT only.
Utilities, Continued SCSI Utility Notes Follow these guidelines about the SCSI utilities: 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 specified device, for example, running the tape key utility on a fixed disk. On the formatter and erase utilities, you must type OK at the DKAxxx OK prompt, or an error appears. An error occurs if an invalid device ID and logical unit number (always 0) are entered.
MIPS/REX Emulator Invoking the Emulator Enter the following command to invoke the MIPS/REX emulator: >>> T/UT TCA The system responds with the following message: **KA49 TURBOCHANNEL REX EMULATOR** >> Available Option Script Functions Enter the following command for a list of available script functions: >>T TC0 LS *emul: t tc0 ls 28 | boot --> code 28 | cnfg --> code 28 | init --> code 28 | t --> code 256 | pst-q 272 | pst-t 288 | pst-m 29264 | code* Continued on next page 5–53
MIPS/REX Emulator, Continued Option Self-Tests Enter the following command for self-test availability: >>T TC0/? flash eprom 68K sram rmap phycsr mac elm cam nirom intlpbk iplsaf pmccsr rmc pktmem >>> Invoking the Option Self-Test The command syntax you use to invoke an individual option self-test is as follows: Syntax: >> T TC0/[Self-Test Name] Example: >>T TC0/FLASH If the test runs successfully, the test returns you to the prompt.
MIPS/REX Emulator, Continued Option Error Message Example The following is an example of an emulator self-test error message. Example: >> t tc0 flash 10 *emul: t tc0 flash 10 ERR-MIPS - ROM OBJECT REPORTED A SEVERE ERROR >> NOTE Consult the option firmware specifications if you receive an error message that is dependent on the device. Exiting the Emulator Press Ctrl D to exit the emulator and access the Model 60 console prompt. Ctrl D is not echoed.
Product Fault Management Overview This section describes how errors are handled by the microcode 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. Interpreting error logs to isolate the FRU is the primary method of diagnosis.
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. These conditions cover all of the cases that eventually are handled by the VMS error handler.
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 flag that signifies that this resource is to be disabled (the cache will be disabled in most, but not all, cases). Update the SYSTAT software register with results of error /fault handling.
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. — Uncorrectable data store ECC errors present in Bcache for marked as OWNED. — Most INT60 errors. — Threshold is exceeded (except for cache errors).
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. VMS Error Logging and Event Log Entry Format The VMS error handler for the kernel can generate six different entry types, as shown in Table 5–11.
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. Refer to VMS Event Record Translation in this chapter for actual examples of the error and event logs described throughout this section.
Product Fault Management, Continued Machine Check Exception Entries Machine check exception entries contain, at a minimum, a machine check stack frame subpacket (Figure 5–10). Figure 5–10 Machine Check Stack Frame Subpacket 24 23 31 08 07 16 15 00 00000018 (hex) byte count (not including this longword, PC or PSL) AST LVL RN xxxxxx xx Mode Machine Check Code CPU ID xxxxxxxx 0. 4. ISTATE1 INT. SYS register 8. SAVEPC register 12. VA register 16. Q register 20.
Product Fault Management, Continued Processor Register Subpacket INT54, INT60, polled, and some machine check entries contain a processor register subpacket (Figure 5–11), which consists of some 40-plus hardware registers. Figure 5–11 Processor Register Subpacket 00 31 00 31 BPCR (IPR D4) 0. PAMODE (IPR E7) MMEPTE (IPR E9) MMESTS 92. MMEADR (IPR E8) 4. VMAR (IPR D0) 96. 8. TBADR (IPR EC) 100. (IPR EA) 12. PCADR (IPR F2) 104. PCSCR (IPR 7C) 16. BCEDIDX (IPR A7) 108.
Product Fault Management, Continued Bugcheck Entries Bugcheck entries generated by the VMS kernel error handler include the first 23 registers from the Processor register subpacket along with the Time-of-Day register (TODR) and other software context state. Uncorrect ECC Memory Error Entries Uncorrectable ECC memory error entries include a memory subpacket (Figure 5–12).
Product Fault Management, Continued Correctable Memory Error Entries Correctable memory error entries have a memory (single-bit error) SBE reduction subpacket (Figure 5–13). This subpacket, unlike all others, is of variable length. It consists solely of software registers from state maintained by the error handler, as well as hardware state transformed into a more usable format.
Product Fault Management, Continued Figure 5–14 Correctable Read Data Entry Subpacket Header 31 24 23 16 15 08 07 00 Logging Reason 0. Page Mapout CNT 4. MEMCON 8. Valid Entry CNT 12. Current Entry 16. MLO-007268 Following the subpacket header are one to 16 fixed-length memory CRD entries (Figure 5–15). The number of memory CRD entries is shown in VALID ENTRY CNT. The entry that caused the report to be generated is in CURRENT ENTRY.
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.
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. The CRD Buffer is also logged immediately if PAGE MAPOUT THRESHOLD EXCEEDED is set in SYSTAT as a result of pages being marked bad.
Product Fault Management, Continued As in this example, the VMS error handler also provides support for the /INCLUDE qualifier, 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 flags and fields are not covered by the service theory. Although these flags are generally not required to diagnose a system to the FRU, this information can be useful for component isolation.
Product Fault Management, Continued If the following two conditions are satisfied, the most likely FRU Interpreting is the CPU module. CPU 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. The example on the next page shows an abbreviated error log with numbers to highlight the key registers.
Product Fault Management, Continued V A X / V M S SYSTEM ERROR REPORT COMPILED 14-JAN-1992 18:55:52 PAGE 1. ******************************* 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 REVISION SYSTAT CPU FW REV# 2. 00000000 00000001 CONSOLE FW REV# 3.
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.
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. No amount of repair will fix them, as generally there is nothing to be fixed.
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 ******************************* ENTRY ERROR SEQUENCE 2. DATE/TIME 4-OCT-1991 09:14:29.86 SYSTEM UPTIME: 0 DAYS 00:01:39 SCS NODE: COUGAR INT54 ERROR KA49-A REVISION SYSTAT CPU FW REV# 2. 00000000 00000601 COMPILED 6-NOV-1991 10:16:49 PAGE 13.
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 & 0B Set = 0(X) Bank = B MEMCON3 8B000003 64 bit mode Base address valid RAM size = 1MB base address = 0B(X) $ SHOW MEMORY System Memory Resources on 21-FEB-1992 05:58:52.
Product Fault Management, Continued In the next example, 5ffb8 (under the page frame number [PFN] column) is identified 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> as 0.
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 flip due to transient alpha particles. Scrubbing reads the corrected data and writes it back to the memory location.
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 errors.
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. The FOOTPRINT longword for this entry contains the message ‘‘Uncorrectable ECC errors due to disown write’’.
Product Fault Management, Continued MEMORY CRD ENTRY 1. FOOTPRINT 0000003D MEMORY ERROR STATUS: _SIMM MEMORY MODULE: 0A _set = 0. Bank = B LOCATION VALID ENTRY CNT 00000001 1. CURRENT ENTRY 00000001 1. MEMORY CRD ENTRY 1. FOOTPRINT 0000003D MEMORY ERROR STATUS: _SIMM MEMORY MODULE: LOCATION 0A _set = 0. ECC SYNDROME = 3D(X) _CORRECTED DATA BIT = 3. STATUS 00000059 PAGE MARKED BAD HARD SINGLE ADDRESS scrubbed GENERATE REPORT CRD CNT 00000002 2. PAGE MAPOUT CNT 00000001 1.
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.
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 & 0B Set = 0(X) Bank = B MEMCON0 80000003 64 bit mode Base address valid RAM size = 1MB base address = 00(X) ANAL/ERR/OUT=TB1 TB1.
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 ARB RETRY CNT = 0. SEL RETRY CNT = 0. BUSY RETRY CNT = 0.
Using MOP Ethernet Functions Console Requester The console requester can receive LOOPED_DATA messages from 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 -EZA0 (08-00-2B-28-18-2C) >>>BOOT EZA0 (BOOT/R5:2 EZA0) 2.. -EZA0 Retrying network bootstrap.
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 ISA-0 State Loopback Name on Adjacent Routing Node 25.
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. ***system 3*** $MCR NCP NCP>SHOW NODE KLATCH Node Volatile Summary as of 27-FEB-1992 21:04:11 Executor node = 25.
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 Surveillance flag Elapsed time Physical address Time of last report Maintenance version Function list Hardware address Device type = ISA-0 = enabled = 00:09:37 = 08-00-2B-28-18-2C = 27-Feb 11:50:34 = V4.0.
User Environmental Test Package Overview When the user environmental test package (UETP) encounters 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.
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 files, and it stores the information from the previous run in one or more OLDUETP.LOG files. If a run of UETP involves multiple passes, there is one UETP.LOG or one OLDUETP.LOG file for each pass. At the beginning of a run, UETP deletes all OLDUETP.LOG files, and renames any UETP.LOG files to OLDUETP.LOG. Then UETP creates a new UETP.
User Environmental Test Package, Continued Possible UETP Errors This section lists some problems you might encounter while running UETP.
FEPROM Firmware Update Overview KA49 firmware is located on four chips, each 128 KB by 8 bits of 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).
FEPROM Firmware Update, Continued A firmware update utility image consists of two parts: the update program and the new firmware, as shown in Figure 5–16. The update program uniformly programs, erases, reprograms, and verifies the entire FEPROM. Figure 5–16 Firmware Update Utility Layout Update Program New Firmware Image MLO-007271 Once the update has completed successfully, normal operation of the system may continue. The operator may then either halt or reset the system and reboot the operating system.
FEPROM Firmware Update, Continued Updating Firmware by Ethernet To update firmware across the Ethernet, the ‘‘client’’ system (the target system to be updated) and the ‘‘server’’ system (the system 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. Use the following procedure to update firmware across the Ethernet: Step Action Comment 1 Enable the server system’s NCP circuit.
FEPROM Firmware Update, Continued Step Action Comment 3 On the client system, enter the command BOOT/100 EZ at the console prompt (>>>). The system then prompts you for the file name. 4 After the FEPROM upgrade program is loaded, press Y at the prompt to start the FEPROM blast. NOTE Do not type the .SYS file extension when entering the Ethernet bootfile name. The MOP load protocol only supports 15-character filenames.
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) 2..
FEPROM Firmware Update, Continued Updating Firmware on Disk This table describes how to update firmware on disk. Step Action 1 Create a top level directory on the disk. CREATE/DIR DKA100:[FIRMWARE] 2 Copy the firmware update savesets to the directory. Use the following command: $ COPY :[FIRMWARE]*.* 3 On the client system, enter this command at the console prompt: b/100 dka100 The system then prompts you for the name of the file.
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.
Updating Firmware On Tape Overview To update firmware on tape, the system must have a TZ30 tape drive. If you need to make a bootable tape, copy the bootable image file to a tape as shown in the following example. Refer to the release notes for the name of the file. NOTE There are different files for booting from tape/disk or Ethernet.
Updating Firmware On Tape, Continued Step Action Comment 3 After the FEPROM upgrade program is loaded, press Y at the prompt to start the FEPROM blast. CAUTION Once you enter the bootfile name, do not interrupt the FEPROM blasting program, as this can damage the CPU module. The program takes several minutes to complete. NOTE On systems with a VCB02 terminal, you will see an abbreviated form.
Updating Firmware On Tape, Continued >>> BOOT MKA500 2.. 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. starting uniform_program...
Updating Firmware On Tape, Continued FEPROM Update Error Messages The next table lists the error messages generated by the FEPROM update program and the actions to take if the errors occur. Message Action update enable jumper is disconnected unable to blast ROMs... Reposition update enable jumper (Preparing the Processor for an FEPROM Update). ROM programming error-expected byte: xx actual byte: xx at address: xxxxxxxx Replace the CPU module.
Updating Firmware On Tape, Continued Patchable Control Store Loading Error Messages The next table lists the error messages that may appear if there is a problem with the PCS. The PCS is loaded as part of the power-up stream (before ROM-based diagnostics are executed). Message Comment CPU is not an NVAX CPU_TYPE as read in NVAX SID is not = 19 (decimal), as is should be for an NVAX processor. Microcode patch/CPU rev mismatch Header in microcode patch does not match MICROCODE_REV as read in NVAX SID.
Chapter 6 FRUs Removal and Replacement Overview Introduction This chapter describes how to remove and replace the field 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 specified, you can install a FRU by reversing the steps in the removal procedure.
Precautions Removing and Installing FRUs Only qualified service personnel should remove or install 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. The customer should also shut down the workstation software. Before performing any maintenance work, Digital Services personnel must confirm that the customer has completed both of these tasks.
System FRU Removal Before Starting Perform these preliminary steps before removing and replacing a FRU. Step Action 1 Verify that the symptom is not caused by improper configuration or a loose cable. 2 Confirm with the customer that data has been backed up. If not, the data could be lost (when a hard disk is at fault). 3 Ensure that the operating system is shut down before turning off the system or halting the CPU.
System FRU Removal, Continued Figure 6–1 shows the location of the system FRUs.
System Preparation Prepare the System Prepare the system for removing or replacing FRUs by following these next steps. 1. Shut down the operating system. 2. 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. The console prompt (>>>) appears. Figure 6–2 Halt Button Audio Selector Switch Alternate Console Switch Handset Jack On/Off Switch Halt Button Diagnostic Lights Front Door MLO-005090 3.
System Preparation, Continued NOTE After adding the new device or module, halt the system when you first turn it on. Use the diagnostic tests described in Chapter 5 to determine if the new device or module is connected correctly. 4. Before adding a new device or module, review the current system configuration. Record the current system configuration information for reference.
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. 5. Turn power to the system off (0). WARNING Turn the monitor power off for at least three minutes before removing the power cord. Remove the power cord before moving the monitor.
Mass Storage Drive Removal Overview This section describes how to remove mass storage devices from 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. NOTE Refer to the System Preparation section before removing or replacing a device or module. Hard Disk Drive Removal This section describes how to remove a hard disk drive from its bracket.
Mass Storage Drive Removal, Continued Hard Disk Drive Replacement Step Action 6 Lift the drive from the bracket. 7 Match the SCSI ID with the error code to verify that the failed drive was removed. 8 Remove the drive mounting plate. 9 Remove the second hard disk drive from the bracket if one is present. Comment Figure 6–3 and Figure 6–4 show the disk drive ID jumper locations. Table 6–1 contains the SCSI jumper settings.
Mass Storage Drive Removal, Continued Step Action Comment 2 Set the SCSI ID jumpers of the top disk drive as specified in Table 6–1. The jumpers are used in the following manner: Install a new drive by reversing the steps in the Hard Disk Drive Removal procedure. Note: When installing a drive into the bracket, you must apply pressure on the drive for it to seat properly.
Mass Storage Drive Removal, Continued Figure 6–4 RZ24 Disk Drive SCSI ID Jumper Location SCSI ID Jumpers Terminator Packs 50-Pin SCSI Signal Connector E2 E1 E3 Connector to HDA Module Power Connector LJ-00622-TI0 Continued on next page 6–11
Mass Storage Drive Removal, Continued Figure 6–5 RZ25 Disk Drive SCSI ID Jumper Location P3 P2 P1 MLO-005323 Continued on next page 6–12
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 P1 P2 P3 0 Out Out Out 1 In 2 Out In Out 3 In Out 4 Out Out In 5 In 6 Out In In 7 In In Comment Out Out In Out In In Usually reserved for SCSI controller The following table lists the standard ID numbers for the SCSI devices.
Mass Storage Drive Removal, Continued RRD42 CDROM Drive Removal RRD42 CDROM Drive Replacement This section describes how to remove an RRD42 CDROM drive. Figure 6–1 shows the RRD42 CDROM drive. Step Action 1 Remove the hard disk drive. 2 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. 3 Lift the drive and drive bracket from the system box.
Mass Storage Drive Removal, Continued Step Action 2 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. To set the SCSI ID jumper in the OFF position, remove the jumper from its seating. To set a jumper in the ON position, leave the jumper in place.
Mass Storage Drive Removal, Continued Installing a New Drive To install a new drive, reverse the steps in RRD42 CDROM Drive Removal. You do not need to push the tabs to insert the bracket. The bracket snaps into place if positioned correctly. RX26 (Diskette) Drive Removal This section describes how to remove the RX26 diskette drive. Figure 6–1 shows the drive location. Step Action 1 You need to release two tabs. The first tab is located at the upper right front of the bracket.
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 1 Locate the type number switches 0, 1, and 2 on the drive, as shown in Figure 6–7. 2 Use a pen or small pointed object to move the switches side to side. The switch should be set to 0. Figure 6–8 shows the SCSI ID switch location for an RX26 drive. 3 The SCSI ID switches should be in the factory-set positions for SCSI ID 5.
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 1 2 3 2 3 MLO-002886 TZK10 QIC Tape Drive Removal This section describes how to remove a TZK10 QIC tape drive. Figure 6–1 shows the drive location. Step Action 1 You need to release two tabs. The first tab is located at the upper right front of the bracket. The second tab is located behind the screw hole at the bottom left center of the bracket.
Mass Storage Drive Removal, Continued TZK10 (Tape) Drive Replacement Before installing the new drive, verify the drive ID setting. Figure 6–9 shows the drive SCSI ID switch locations for the tape drive. Use the following procedure to verify or set the drive SCSI ID jumpers. Step Action 1 Locate the set of SCSI ID jumpers 0, 1, and 2 at the rear of the drive. The jumpers should be to the left side of the drive. The jumpers are removable electrical connectors on the ID settings.
Mass Storage Drive Removal, Continued Installing a New Drive To install a new drive, reverse the steps in the TZK10 QIC Tape Drive Removal procedure. You do not need to push the tabs to insert the bracket. The bracket snaps into place if positioned properly.
Power Supply Removal Removing the Power Supply This section describes how to remove the system 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. There are dangerous voltages inside the power supply, and there are no user-serviceable parts. To remove the power supply, follow the next procedure.
Power Supply Removal, Continued Power Supply Replacement To install a new power supply, reverse the steps in the Power 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. Align the two guides (one on the right front of the supply, and one on the right rear) with the slots on the system box. Push the supply down into place. The power supply snaps into place if positioned properly.
Module Removal Overview The following sections describe how to remove and replace the 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. Light and Switches Module Removal This section describes how to remove the light and switches module from the system.
Module Removal, Continued Light and Switches Module Replacement Memory Module Identification To replace the light and switches module, perform the following steps: Step Action 1 Align the switches with their respective holes in the front bezel. 2 Align the connector on the lower side of the module with the connector on the system module and seat the connector. Three types of memory modules are available: 4 MB (MS44AA), 4 MB reduced cost (MS44L), and 16 MB (MS44-CA).
Module Removal, Continued Figure 6–10 Memory Module Identification AA = 4 Megabyte Memory Board CA -A AA -A 8 8 CA = 16 Megabyte Memory Board LJ-00499-TI0 MS44 Memory Module Removal This section describes how to remove the MS44 memory modules from the system. CAUTION Memory components are easily damaged with static electricity. An antistatic wrist strap should always be worn when installing or removing memory components.
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. Memory module locations are numbered on the right edge of the memory connectors located on the system board. The location of the memory modules is shown in Figure 6–1.
Module Removal, Continued MS44 Memory Module Replacement Graphics Module Removal To install a new MS44 memory module, perform the following steps. NOTE When installing memory modules (sets of four), each set must be installed in the slots identified for a particular set. These designators are to the right of each slot and identified with a 0x (where x=A1x [where x=E,F,G,H] for set 1. Step Action 1 Look for the double grove at end of the SIM module connector.
SPXg 8-Plane Option Overview The SPXg 8-plane option includes the following: 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. Radio frequency interference (RFI) gasket Removing the SPXg 8-plane Option Follow this procedure and refer to Figure 6–11 to remove the SPXg option.
SPXg 8-Plane Option, Continued Figure 6–11 Removing the SPXg 8-Plane Option 2 1 Graphics Boards RFI Gasket 2 1 Switch Package MR-0234-92DG Continued on next page 6–29
SPXg 8-Plane Option, Continued Installing the SPXg 8-plane Option Reassemble the option assembly with the new FRU as follows: Step Action 1 If the new FRU is a SIM module, install it on the frame buffer module. 2 Set switch 2 towards the B marker on the frame buffer module. This setting is at 66 Hz. If switch 2 is set towards the opposite side of the frame buffer module, the setting is at 72 Hz. 3 Align the graphics module and system module intermodule connectors.
SPXg 8-Plane Option, Continued 6 See Figure 6–14. Carefully tilt the assembly into position . The two hooks on the system box subchassis slip through the square holes in the lower curve of the connector bracket. 7 Insert the assembly. With the assembly in position, align the graphics subsystem processor and system module intermodule connectors . Mate the connectors by pressing down on the frame buffer module above the inter-module connectors.
SPXg 8-Plane Option, Continued Figure 6–13 Installation Details Frame Buffer Graphics Subsystem Processor Ridge RFI Gasket Video Connector Video Connector Bracket Hook System Box Subchassis WMO_SPXGGT_009 Continued on next page 6–32
SPXg 8-Plane Option, Continued Figure 6–14 Installing the SPXg 8-plane Option 1 Tail Bracket Frame Buffer Module 2 3 5 4 H-Bracket Graphics Boards RFI Gasket 1 2 Switch Package LJ-02221-TI0 6–33
SPXgt 24-Plane Option Overview The SPXgt 24-plane option includes the following: 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 to the LCSPX.
SPXgt 24-Plane Option, Continued Removing the SPXgt 24-Plane Option The shape and size of the 24-plane frame buffer module prohibits removing the SPXgt as an assembly. See Figure 6–15 and remove the components as follows: Step Action 1 Turn off the system power, move the monitor, and open the system unit cover as described in System Preparation . 2 Remove the plastic clip (not shown) that holds the graphics subsystem processor module to the frame buffer module.
SPXgt 24-Plane Option, Continued Figure 6–15 Removing the SPXgt 24-Plane Option 1 Tail Bracket Frame Buffer Module 2 3 6 4 5 H-Bracket Tail Bracket Frame Buffer Module Graphics Subsystem Processor Module RFI Gasket 1 3 2 6 5 Board Latches 4 MR-0218-92DG Continued on next page 6–36
SPXgt 24-Plane Option, Continued Installing the SPXgt 24-Plane Option Reassemble the option assembly with the new FRU as follows: Step Action 1 Align the graphics module and system module intermodule connectors. Mate the connectors by pressing down on the module. The module latches should snap into place to secure the module. 2 Align and mate the frame buffer with the graphics module. The frame buffer module tail bracket should snap over the ridge on the disk drive H-bracket.
SPXgt 24-Plane Option, Continued Figure 6–16 Installing the SPXgt 24-Plane Option Tail Bracket 1 2 2 H-Bracket Graphics Boards Tail Bracket RFI Gasket 1 2 LJ-02220-TI0 6–38
CPU Module System Module (CPU) Removal This section describes how to remove the system module. 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 1 Disconnect the cables attached to the module at the rear of the system. 2 Remove the optional graphics module (if applicable). Refer to the Graphics Module Removal procedure.
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. System Module (CPU) Replacement 6–40 To install a new system module (CPU), reverse the steps in the System Module (CPU) Removal procedure. Ensure that the five slots in the module are aligned with the five latches on the base of the system box.
DSW21 Removal and Replacement DSW21 Removal DSW21 Replacement To remove the DSW21 from the system box, perform the following steps: Step Action 1 Remove the system box cover. 2 Disconnect the SCSI cable, located directly in front of the DSW21. 3 Disconnect the communications cable or terminator from the back of the system box. 4 Lift and remove the DSW21 (directly behind the SCSI connector), front end first. Replace the DSW21 as described in the following table.
Bezel Removal System Bezel Removal Bezel Replacement Use the next procedure and refer to Figure 6–1 to remove the system bezel. Step Action 1 Remove the cover. 2 Remove the removable media bracket, with drives. See the RRD42 CDROM Drive Removal or RX26 (Diskette) Drive Removal procedures. 3 Remove the lights and switches module. See the Light and Switches Module Removal procedure. 4 Slide the bezel up and out of its guides.
Bezel Removal, Continued Synchronous Communications Adapter Cables Adapter cables for the synchronous communications adapter vary according to the option. Table 6–3 lists the adapter cable variations. 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 BC19W EIA-449/423/V.10 DSW21-AC 1 Line sync comm BC19U EIA-449/422/V.
Bezel Removal, Continued Installing the Synchronous Communications Adapter This section describes how to install the synchronous communications adapter interface in the system unit. NOTE Refer to the system preparation instructions before installing any module in the workstation. To install the communications interface, do the following: Step Action 1 Remove any rear panels or shields (if applicable) from the I/O panel. 2 Mount the adapter internally to the Model 90 using the 64-pin option connector.
Bezel Removal, Continued Environmental Specifications Table 6–4 lists the synchronous communications model environmental specifications.
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 Specifications The synchronous communications adapter is a four-layer circuit board assembly. Table 6–5 shows its specifications. Table 6–5 Physical Specifications 6–46 Height 4.3 cm (1.7 in) Width 12.4 cm (4.9 in) Depth 14 cm (5.5 in) Weight .
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.
Testing the VAXstation 4000 Model 90 System Testing the System This section describes how to test the system after completing the removal or replacement process. Restoring the System Before you can test the system, you must restore the system to its previous operating state. To restore the system, perform the following steps: Testing the System Step Action 1 Replace the system cover.
Testing the VAXstation 4000 Model 90 System, Continued Step Action 2 Display the system device configuration by using the SHOW CONFIG command (see the System Preparation section). Compare the latest configuration display with the configuration display you viewed during system preparation. You should see the new device and the other devices present in the system. Verify that no error messages appear on the monitor screen.
TURBOchannel Option Overview The TURBOchannel option is a high-performance input/output interconnection that provides a data communications path.
Shipping Contents TURBOchannel Adapter Components Figure 6–17 shows the components that ship with the TURBOchannel adapter.
Shipping Contents, Continued Adapter Component Descriptions Table 6–6 describes the TURBOchannel adapter components shown in Figure 6–17.
Shipping Contents, Continued TURBOchannel Option Components Figure 6–18 shows the components that ship with the TURBOchannel option. Figure 6–18 TURBOchannel Option Components 3 1 2 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 package are not necessary. You can discard them.
TURBOchannel Adapter and Option Modules TURBOchannel Adapter and Option Removal 6–54 Table 6–7 provides an overview of how to remove and replace the TURBOchannel adapter and the TURBOchannel option. Table 6–7 TURBOchannel Adapter/Option Removal Step Action 1 Disconnect the TURBOchannel option cable. 2 Remove the two screws that hold the option plate over the outside of the TURBOchannel option.
Installing the TURBOchannel Option Installation Overview Table 6–8 provides an overview of the TURBOchannel option installation procedure. Each step is explained in more detail in the following sections. Table 6–8 TURBOchannel Option Installation Procedure Step Action 1 Touch the TOUCH HERE space on the power supply. 2 Disconnect the SCSI cable. 3 Remove the option plate. 4 Remove the graphics board (if applicable). 5 Insert the TURBOchannel adapter board. 6 Replace the graphics board.
Installing the TURBOchannel Option, Continued TOUCH HERE Space As soon as you remove the cover, and before you remove anything else, touch the space labeled TOUCH HERE (Figure 6–19 ), to avoid damage from static discharge. Figure 6–19 Inside the System Box 2 3 n T M ou c T as h H oq se he ie ue re r a b q e u ru i h re 1 MLO-008167 Disconnect the SCSI Cable Disconnect the SCSI cable from the system unit by pushing the two side clips out, then lifting the cable off.
Installing the TURBOchannel Option, Continued Remove the Option Plate Remove the option plate that covers the TURBOchannel option port opening. Squeeze the tabs together, then pull the plate out, as shown by the arrows in Figure 6–20. n T M ou c T as h H oq se he ie ue re r a b q e u ru i h re Figure 6–20 Removing the Filler Plate MLO-008524 Remove the Graphics Board If there is a a graphics board present, you need to remove it.
Installing the TURBOchannel Option, Continued n T M ou c T as h H oq se he ie ue re r a b q e u ru i h re Figure 6–21 Inserting the TURBOchannel Adapter Board MLO-008168 Replace the Graphics Board Replace the graphics board in your system unit. Refer to the Installing the SPXg 8-plane Option procedure.
Installing the TURBOchannel Option, Continued Attaching the FCC Shield Attach the FCC shield to the front of the TURBOchannel option module, over the metal bracket, as shown in Figure 6–22. Figure 6–22 Attaching the FCC Shield MLO-008519 Reconnect the SCSI Cable Reconnect the SCSI cable to the port slot above the TURBOchannel option port.
Installing the TURBOchannel Option, Continued Install the TURBOchannel Option Install the TURBOchannel option module to the right of the graphics board. Slide the TURBOchannel option module firmly towards the front. Press the rear of the module so that the connector underneath slides into the connector on the TURBOchannel adapter board.
Installing the TURBOchannel Option, Continued Attach the Option Plate Place the metal option plate over the outside of the 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. You now need to test the installation.
Installing the TURBOchannel Option, Continued To test your TURBOchannel option installation, follow the instructions in Testing the VAXstation 4000 Model 90 System. Testing the Installation Callout of Figure 6–25 shows the line in the SHOW CONFIG display that indicates a successful TURBOchannel option installation. Figure 6–25 Testing the TURBOchannel Option Installation >>> SHOW CONFIG KA49-A V0.0-051-V4.
TURBOchannel Specifications Specifications Table 6–9 provides the specifications for the TURBOchannel option. Table 6–9 TURBOchannel Specifications Air flow 150 LFM Connector 96-pin DIN Data path 32-bit multiplexed address/data Nonoperating storage temperature 0 to 50°C (32 to 89.6°F) Operating temperature 10 to 40°C (50 to 104°F) Operating temperature With tape or floppy 15 to 32°C (59 to 90°F) Protocol Synchronous, 12.
Appendix A Diagnostic Error Codes Overview In this Chapter The system firmware 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. The error codes identify the device and the test that failed.
Overview, Continued — TURBOchannel Adapter — LCSPX System Test Error Messages — SCSI — DSW21 Communications Device Utility Error Messages A–2 — SCSI — LCSPX — SPXg/gt
Error Messages Overview The system reports two kinds of self-test errors. 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. Extended test errors These error messages display more detailed information.
Error Messages, Continued Extended Error Messages Message Meaning 10 The device identification (decimal). This value corresponds to the left bank of four LEDs (hexadecimal). This ID also corresponds to the mnemonic in the next field. Use Table 5–4 to correlate the error code to a device. SCSI The mnemonic of the device ID. 50 The error code that displays following the test is in decimal. The extended message error codes have a hexadecimal format.
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. 150 Field replaceable unit (FRU). See Table A–1. 10 Device identification (Value is given in decimal.
Error Messages, Continued FRU Codes The FRU code identifies the field replaceable unit that failed. The FRU codes and their names are listed in the following table. Table A–1 FRU Codes Code FRU 001 System module. The mnemonic identifies the device.
Error Messages, Continued Table A–1 (Continued) FRU Codes Code FRU SCSI Drive Codes 100-199 Code Drive with ID 100 0 110 1 120 2 130 3 140 4 150 5 160 6 170 7 A–7
Self-Test Error Messages TOY/NVR Table A–2 lists the TOY/NVR self-test decimal and hexadecimal error messages and their meanings. Table A–2 TOY/NVR Self-Test Error Messages Decimal Hexadecimal Meaning 4 4 Battery faulty. 8 8 NVR Register test has failed. 12 c Battery down and NVR Register test has failed. 16 10 TOY Register test has failed. 32 20 Valid RAM and Time bit has failed to set. 36 24 VRT bit failure and battery faulty.
Self-Test Error Messages, Continued Table A–2 (Continued) TOY/NVR Self-Test Error Messages DZ Decimal Hexadecimal Meaning 129 81 Update in progress has failed to clear; soft error. 160 A0 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. Table A–3 DZ Self-Test Error Codes Decimal Hexadecimal Meaning 16 10 DZ Reset test has failed. 32 20 DZ Read LPR test has failed.
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 The data expected The extended error code messages in the following formats are returned by polled and interrupt test when a transfer times out.
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 21 READ LPR Baud rate is incorrectly set 22 READ LPR Character width is incorrectly set 23 READ LPR Parity bit is incorrectly set 24 READ LPR Receiver on bit is incorrectly set 31 DZ Modem test - Failed RTS <-> CTS loopback 32 DZ Modem test - Failed DSRS <-> DSR & CD loopback 33 DZ Modem test - Failed LLBK <-> SPDMI loopback 34 DZ Mod
Self-Test Error Messages, Continued Table A–4 (Continued) DZ Suberror codes Suberror (hexadecimal) SCSI DMA Meaning 56 DZ Interrupt test - Character received != Character transmitted 61 DZ LK401 test - transfer has timed out 62 DZ LK401 test - LK401 has failed self-test 71 DZ Mouse test - transfer has timed out 72 DZ Mouse test - Mouse has failed self-test This table lists the SCSI DMA self-test error codes.
Self-Test Error Messages, Continued OBIT Table A–6 lists the OBIT self-test decimal and hexadecimal error codes.
Self-Test Error Messages, Continued CACHE Table A–7 lists the CACHE self-test decimal and hexadecimal error codes.
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 CCTL register contents 001 000b aaaaaaaa bbbbbbbb cccccccc dddddddd Memory Format Meaning aaaaaaaa Address that failed the test bbbbbbbb Expected value o
Self-Test Error Messages, Continued Table A–8 MEM Self-Test Error Codes Decimal Hexadecimal Meaning 64 40h Bank 0 1 or more SIM modules missing. 66 42h Bank 0 SIM modules not all same size. 68 44h Bank 2 1 or more SIM modules missing. 70 40h Bank 2 SIM modules not all same size. 256 100h Failure has occurred in the Byte Mask test. 260 104h Parity error occurred during the Byte Mask test. 514 202h Data compare error occurred during the forward pass.
Self-Test Error Messages, Continued Extended Error Format: xxx 4 MEM yyyy xxx 00a bbbbbbbb cccccccc dddddddd eeeeeeee MEM SIM Module FRU Values Format Meaning xxx The FRU where the failure occurred yyyy The error code in Hexadecimal 00a Extended error information format type bbbbbbbb The contents of the Memory System Error register (MSER) cccccccc The failing address dddddddd The expected data eeeeeeee The data that was read Table A–9 lists the MEM SIM module FRU values.
Self-Test Error Messages, Continued Table A–9 (Continued) MEM SIM Module FRU Values FPU FRU (decimal) SIM Module BANK 046 1H 1 047 0D 0 Table A–10 lists the floating point diagnostic decimal and hexadecimal error codes. Table A–10 FPU Self-Test Error Codes Decimal Hexadecimal Meaning 258 102 MOVF Instruction test has failed. 260 104 Unexpected Exception has occurred during MOVF test. 514 202 MNEGF Instruction test has failed.
Self-Test Error Messages, Continued Table A–10 (Continued) FPU Self-Test Error Codes Decimal Hexadecimal Meaning 1538 602 CVTFD/CVTFG Instruction test has failed. 1540 604 Unexpected Exception has occurred during CVTFD/CVTFG test. 1794 702 CVTFx Instruction test has failed. 1796 704 Unexpected Exception has occurred during CVTFx test. 2050 802 CVTxF Instruction test has failed. 2052 804 Unexpected Exception has occurred during CVTxF test.
Self-Test Error Messages, Continued Table A–10 (Continued) FPU Self-Test Error Codes Decimal Hexadecimal Meaning 3586 E02 TSTF Instruction test has failed. 3588 E04 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. The extended error formats are shown in the following examples.
Self-Test Error Messages, Continued Table A–11 (Continued) FP Exception Vectors Interval Timer Vector Description 018 Reserved operand vector 01c Reserved Addressing mode vector 034 Arithmetic Trap vector Table A–12 lists the interval timer self-test decimal and hexadecimal error codes and their meanings.
Self-Test Error Messages, Continued Extended Error Format: This format displays when there is an invalidate filter RAM error. 001 0010 aaaaaaaa rrrrrrrr eeeeeeee Network Interface Format Meaning 001 The FRU number (system board) 0010 The format number aaaaaaaa The failing invalidate filter address rrrrrrrr The data read Table A–14 lists the decimal and hexadecimal error codes returned by the network interface (NI) self-test.
Self-Test Error Messages, Continued Table A–14 (Continued) NI Self-Test Error Codes Decimal Hexadecimal Meaning 28 1C Network Address ROM: bad test patterns 30 1E SGEC CSR0 R/W error 32 20 SGEC CSR1 R/W error 34 22 SGEC CSR2 R/W error 36 24 SGEC CSR3 R/W error 38 26 SGEC CSR4 R/W error 40 28 SGEC CSR5 R/W error 42 2A SGEC CSR6 R/W error 44 2C SGEC CSR7 R/W error 46 2E SGEC CSR8 R/W error 48 30 SGEC CSR9 R/W error 50 32 SGEC CSR10 R/W error 52 34 SGEC CSR11 R/W error
Self-Test Error Messages, Continued Table A–14 (Continued) NI Self-Test Error Codes Decimal Hexadecimal Meaning 72 48 SGEC Chip self-test: Self-Test loopback error 74 4A SGEC Initialization: Setup frame send failure 76 4C SGEC Interrupts: initialization failed 78 4E SGEC Interrupts: transmit failed 80 50 SGEC Interrupts: receive failed 82 52 SGEC Interrupts: packet comparison failed 84 54 SGEC Interrupts: NI ISR not entered 86 56 SGEC Interrupts: NI ISR entered multiple times 88 5
Self-Test Error Messages, Continued Table A–14 (Continued) NI Self-Test Error Codes Decimal Hexadecimal Meaning 112 70 SGEC Address filtering: initialization failed 114 72 SGEC Address filtering: transmit failed 116 74 SGEC Address filtering: receive failed 118 76 SGEC Address filtering: packet comparison failed 120 78 SGEC Address filtering: broadcast filtering failed 122 7A SGEC Address filtering: promiscuous mode failed 124 7C SGEC Address filtering: null destination accepted 126
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 Meaning aaaaaaaa Base address of the Network Address ROM bbbbbbb First four bytes of the network address cccccccc Next two bytes of t
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 Format Meaning aaaaaaaa Actual value of SGEC CSR5 bbbbbbbb Physical addres
Self-Test Error Messages, Continued NI EXTENDED ERROR FORMAT 11h: Interrupt Error 0001 0011 aaaaaaaa SCSI Format Meaning aaaaaaaa Actual value of SGEC CSR5 Table A–15 lists the decimal and hexadecimal error codes returned by the SCSI self-test. Table A–15 SCSI Self-Test Error Codes Decimal Hexadecimal Meaning 2 2 SCSI Reset Register test has failed. 4 4 SCSI Configuration Register test has failed. 6 6 SCSI FIFO register test has failed. 8 8 SCSI Transfer Count Register test has failed.
Self-Test Error Messages, Continued Table A–15 (Continued) SCSI Self-Test Error Codes Decimal Hexadecimal Meaning 28 1C SCSI Interrupt test Low Ipl, Mask Enabled has failed. 30 1E SCSI Data Transfer Test, Prom Function has failed. 32 20 SCSI Data Transfer Test, DMA Mapping has failed. 34 22 SCSI Data Transfer Test, Non-DMA Inquiry has failed. 36 24 SCSI Data Transfer Test, Not Enough Data Returned. 38 26 SCSI Data Transfer Test, DMA Inquiry has failed.
Self-Test Error Messages, Continued Table A–15 (Continued) SCSI Self-Test Error Codes Decimal Hexadecimal Meaning 66 42 SCSI Map Error Test, Map Error Will Not Set. 68 44 SCSI Map Error Test, Parity Error Will Not Clear. 70 46 SCSI Map Error Test, Prom Function has Failed. 80 50 SCSI Prom Function has failed. 82 52 SCSI Init Driver has failed. The SCSI self-test also returns extended error information when an error occurs. This information is available by entering the SHOW ERROR command.
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.
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.
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 at the time of error mmmmmmmm Request sense key EXTENDED ERROR FORMAT F(h): This error format is used when status phase returns a bad status, or when a bad sense key
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.
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.
Self-Test Error Messages, Continued EXTENDED ERROR FORMAT 12(h): This error format is used when an unsupported message is seen.
Self-Test Error Messages, Continued EXTENDED ERROR FORMAT 13(h): This error format is used by the Map Error test.
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.
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.
Self-Test Error Messages, Continued Table A–16 (Continued) SCSI Information Values Information Decimal Hexadecimal Meaning 12 C Selected bit set in Controller Interrupt register 13 D Select with attention bit clear in Controller Interrupt register 14 E Select with attention bit set in Controller Interrupt register 15 F Reselected bit clear in Controller Interrupt register 16 10 Reselected bit set in Controller Interrupt register 17 11 Function complete bit clear in Controller Interrupt regi
Self-Test Error Messages, Continued Table A–16 (Continued) SCSI Information Values Information Decimal Hexadecimal Meaning 26 1A SCSI Reset bit set in Controller Interrupt register 27 1B Arbitration not won 28 1C Selection timeout 29 1D Invalid sequence in Sequence Step register 30 1E FIFO flags are not clear 31 1F FIFO flags are clear 32 20 Unexpected ISR hit 33 21 SCSI Interrupt request set in system interrupt request register 34 22 SCSI Bit set unexpectedly in Controller status
Self-Test Error Messages, Continued Table A–16 (Continued) SCSI Information Values Information Decimal Hexadecimal Meaning 44 2C Phase did not go to message in phase 45 2D Command phase changed too soon 46 2E Data out phase changed too soon 47 2F Message in phase changed too soon 48 30 Message out phase changed too soon 49 31 Stuck in command phase 50 32 Stuck in message in phase 51 33 Stuck in message out phase 52 34 Stuck in data out phase 53 35 Stuck in data in phase 54 36
Self-Test Error Messages, Continued Table A–16 (Continued) SCSI Information Values Information Decimal Hexadecimal Meaning 61 3D Unexpected message reject from device 62 3E FIFO flag count is wrong 63 3F Message is unsupported 64 40 Bus device reset was sent, but device didn’t drop off bus 65 41 Illegal phase 66 42 Should not be in data in phase 67 43 Problem with a device trying to reconnect 68 44 Unexpected disconnect message received 69 45 Device not seen before is trying to rec
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 Overview Mode (hexadecimal) Meaning 0 Asynchronous mode with programmed I/O 1 Asynchronous mode with DMA 2 Synchronous mode with DMA The audio self-test (AUD) is divided into three major sections. Register tests Audio tests Interrupt tests Registers are tested by writing data then reading back the data, or reading the READ_ONLY registers.
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 2 2 AUD$LIU_LSR_SAE Register test has failed. 4 4 AUD$LIU_LPR_SAE Register test has failed. 6 6 AUD$LIU_LPR_NZE Register test has failed. 8 8 AUD$LIU_LMR1_SAE Register test has failed. 10 A AUD$LIU_LMR2_SAE Register test has failed. 16 10 AUD$MUX_MCR1_SAE Register test has failed.
Self-Test Error Messages, Continued Table A–18 (Continued) AUD Self-Test Error Codes Extended Error Information Decimal Hexadecimal Meaning 48 30 AUD$INTR_RECEIVE_BYTE_ AVAILABLE test has failed. 50 32 AUD$INTR_BAD_DLC_LOOPBACK_ DATA Test has failed. 52 34 AUD$INTR_TIME_OUT test has failed. 56 36 AUD$INTR_INVALID_IR_VALUE test has failed. 58 38 AUD$INTR_NO_INT_GENERATED test has failed. 60 3A AUD$INTR_NOT_ALL_INTS_RCVD test has failed. 62 3C AUD$INTR_INT_NOT_DISABLED TEst has failed.
Self-Test Error Messages, Continued Format Meaning cccccccc The contents of data register (DR) dddddddd TBS EXTENDED ERROR FORMAT 11(h): This error format is used by all audio interrupt tests. aaa 0011 bbbbbbbb cccccccc dddddddd Format Meaning aaa The FRU bbbbbbbb The error number cccccccc The contents of D channel status register 2 (DSR2) dddddddd TBS EXTENDED ERROR FORMAT 12(h): This error format is used by all audio tests.
Self-Test Error Messages, Continued DSW21 Synch Communications Test Error Codes Table A–19 lists the DSW21 Synch communications test error codes.
Self-Test Error Messages, Continued Table A–19 (Continued) Synch Comm Device Test Error Codes Decimal Hexadecimal Meaning 38 26 Invalid test Synch Comm.
Self-Test Error Messages, Continued Table A–19 (Continued) Synch Comm Device Test Error Codes Decimal Hexadecimal Meaning Synch Comm.
Self-Test Error Messages, Continued Table A–19 (Continued) Synch Comm Device Test Error Codes Decimal Hexadecimal Meaning Synch Comm.
Self-Test Error Messages, Continued Table A–19 (Continued) Synch Comm Device Test Error Codes Decimal Hexadecimal Meaning Synch Comm.
Self-Test Error Messages, Continued Table A–19 (Continued) Synch Comm Device Test Error Codes Decimal Hexadecimal Meaning 222 DE Memory free error 224 E0 UTIL Invalid utility number 226 E2 UTIL Invalid cable code DSW21 Comm.
Self-Test Error Messages, Continued Table A–19 (Continued) Synch Comm Device Test Error Codes Decimal Hexadecimal Meaning 250 FA ROM Test 252 FC ROM Checksum error 254 FE Ctrl C entered at console 256 100 Comm option receive error-CRC follow error 258 102 Comm option MC68302 component is not REV B 260 104 Test request sequence error 262 106 IMP Timeout waiting for host to clear RA 264 108 IMP Timeout waiting for host to clear SR Continued on next page A–54
Self-Test Error Messages, Continued Table A–19 (Continued) Synch Comm Device Test Error Codes TURBOchannel Adapter Self-Test Error Codes Decimal Hexadecimal Meaning 266 10A ROM Test error 268 10C FBUG Secure error-reserved operation 270 10E Port PB3 Signal stuck high 272 110 Timer 3 not counting 274 112 Comm option diagnostics did not complete 276 114 Comm option SDMA bus error occurred 278 116 Timeout waiting for IRQ assertion 280 118 Transmit restart of 10 exceeded Table A–20 d
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 Forced ERROR condition not seen 0018 0012 TCA Interrupt at VAX INT_REG not set 0020 0014 Interrupt bit on TCA not set 0022 0016 ISR Was not entered on interrupt 0024 0018 FIFO Data was bad aft
Self-Test Error Messages, Continued Decimal Format The following example shows a TCA decimal error code. >>>T TCA | | ?? 013 13 TCA Hexadecimal Format 0026 The following example shows a TCA hexadecimal error code. >>>SHOW ERROR ?? 013 13 TCA 001A TURBOchannel Adapter System Test Error Codes There is no system test for the TURBOchannel adapter. TURBOchannel Adapter MIPS/REX Emulator Utility Commands The MIPS/REX Emulator utility allows you to execute TURBOchannel option firmware.
Self-Test Error Messages, Continued Example: >> T TC0 ? REX CMDS: T TC0 / | ? T TC0 SCRIPT T TC0 INIT T TC0 CNFG T TC0 LS T TC0 CAT >> The examples are for the single-width DEFZA TURBOchannel FDDI option. ROM Object List ROM objects reside on the TURBOchannel option card. Type the following to display all ROM objects for the TURBOchannel device.
Self-Test Error Messages, Continued ROM Object Symbols The following table defines the ROM object symbols. Symbol Meaning --> Symbolic link * Executable image | Separator between the two parameters pst-q, pst-t, pst-m Scripts (built-in tests to be executed one after the other) Use these tests with the T TC0 CAT [SCRIPTNAM] and T TC0 SCRIPT [SCRIPTNAM] commands. NOTE After entering T TC0 LS, it is not always safe to run tests which do not appear in any script.
Self-Test Error Messages, Continued t t t t t ${#}/rtostim ${#}/botim ${#}/extlpbk ${#}/extmemtst ${#}/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 ${#}. The slot number is always zero (0) for the VAXstation 4000 Model 60. Option Tests Type the following to display all the option tests.
Self-Test Error Messages, Continued The option test results are option dependent. TURBOchannel options can display the tests differently. Some options show only the 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). NOTE Read the specific TURBOchannel Option User’s Guide to properly test the option. Running an Option Test Enter the following to run an option test.
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 t 0/botim t 0/dmatst >> The emulator shows each test within the script as it is executed. Also, error status is checked after each test completes and is saved for the end of the script. NOTE Standard scripts pst-q, pst-t, and pst-m can be run as single tests.
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. MIPS/REX Emulator Errors The emulator’s function is to execute the tests. While an error status code is maintained during testing, the emulator does not diagnose TURBOchannel hardware failures.
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. Corrective Action Check whether a ?TFL error message displayed before this message. Refer to the option user’s guide.
Self-Test Error Messages, Continued Table A–21 Synch Communications Self-Test Sequence Numbers Test Number Decimal Hexadecimal Routine Description 01 01 imp_exc Exception vector initialization 02 02 imp_vec User interrupt vector initialization 03 03 imp_rdb Local register RDB initialization 04 04 imp_pub_ init Up block initialization 05 05 imp_op_ init Option register initialization 06 06 imp_br_init Base register initialization 07 07 imp_cs_ switch Power-up switch initializatio
Self-Test Error Messages, Continued Table A–21 (Continued) Synch Communications Self-Test Sequence Numbers Test Number Decimal Hexadecimal Routine Description 15 0F imp_loc_ init Local scratch RAM SCR initialization 16 10 imp_idb_ init Interrupt data block initialization 17 11 imp_pcb_ init Process control block initialization 18 12 imp_ic_init Interrupt controller initialization 19 13 imp_cable_ code Read cable code 20 14 imp_dma_ test IDMA Transfers test 21 15 imp_rings Initia
Self-Test Error Messages, Continued Table A–21 (Continued) Synch Communications Self-Test Sequence Numbers Test Number Decimal Hexadecimal Routine Description 30 1E imp_ modem_ test Modem signal test 31 1F imp_elb_ test SCC External loop 32 20 imp_isdn_ test ISDN test 33 21 imp_rdb Runtime register RDB initialization 34 22 imp_loc_ init Runtime SCR RAM initialization 35 23 imp_cable_ code Runtime read adapter cable code 36 24 imp_ic_init Runtime interrupt controller initializati
Self-Test Error Messages, Continued Table A–21 (Continued) Synch Communications Self-Test Sequence Numbers Test Number Decimal Hexadecimal Routine Description 43 2B imp_s3_ inte Runtime SCC3 ISR 44 2C imp_t1_ start Runtime timer 1 start 45 2D imp_t2_ start Runtime timer 2 start 46 2E imp_t3_ start Runtime timer 3 start 47 2F imp_dainit Runtime RAM dual access initialization 48 30 imp_xvec Runtime transfer vector initialization The DSW21 Communications Device test displays extended
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 selftests.
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.
Self-Test Error Messages, Continued Format Meaning jj 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.
Self-Test Error Messages, Continued Format Meaning ii Internal loopback mode (0=internal, 1=external) jj 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.
Self-Test Error Messages, Continued Format Meaning gg Current channel under test (1, 2, 3) hh Current electrical interface ii Internal loopback mode (0=internal, 1=external) jj 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 0006: This format is used by the DSW21 communications device loopback tests.
Self-Test Error Messages, Continued Format Meaning ff Current software revision gg Current channel under test (1, 2, 3) hh Current electrical interface ii Internal loopback mode (0=internal, 1=external) jj 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 0007: This format is used by the DSW21 communications device reset test.
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 020 The FRU for the DSW21 communications device 0008 Format type 0008 The currently running null request Extended Error Format 0009: This format is used by the DSW21 communications device when an exception occurs.
Self-Test Error Messages, Continued Extended Error Format 10: This format is used by the DSW21 communications device when it first executes code, and is used to verify that the 68K is executing instructions. 020 000A 00040003 00060005 00080007 00100009 00120011 00140013 00160015 DSW21 Communications Utilities Error Codes Format Meaning 020 The FRU for the DSW21 communications device 000A Format type Table A–22 lists the DSW21 utilities error codes.
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.
Self-Test Error Messages, Continued Failing Logical Block Field The failing logical block field points in an area that can be used 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.
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 FIFO Direct Access 0B/11 FIFO Auto Increment Location 0C/12 FIFO Auto Increment Buffer Load 0D/13 FIFO Auto Increment Buffer Execution 0E/14 Frame Buffe
Self-Test Error Messages, Continued Table A–24 (Continued) Test Number Summary SPXg/gt Self-Test Error Codes 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 Brooktree Analog Compare The SPXG module provides error information that can be utilized to identify faults down to a logical block
Self-Test Error Messages, Continued ?? 0022 SPXG 0080 001 0081 FFFF0000 FF00FF00 22004400 00000000 00000000 00000000 Extended Data 6 Extended Data Extended Data Extended Data Extended Data Extended Data Error Number Failing Test 5 4 3 2 1 Failing Block Failing Logical Block Field The failing logical block field points in an area that can be used as a starting point for diagnosing the fault. This does not mean that it is the actual fault, but that the error was detected at that point.
Self-Test Error Messages, Continued Test Numbers The following table lists all the tests provided in the SPXG selftest ROM. The test number is found in the failing test field of the error code.
Self-Test Error Messages, Continued Table A–26 (Continued) Test Number Summary Test Number Hexadecimal /Decimal LED Codes (Hexadecimal) 0150/0336 ScanProc Stream Write 23 0160/0352 FIFO Transfer 24 0170/0368 ScanProc External Write 24 0180/0384 ScanProc Stream Read 24 0190/0400 LCG DMA 25 01A0/0416 LCG OTF 25 01B0/0432 DMA Stream 25 01C0/0448 OTF Stream 25 01D0/0464 Auto Increment Location Stream 25 01E0/0480 Command FIFO OTF Stream 25 01F0/0496 Command FIFO External Stream
System Test Error Messages SCSI Table A–27 lists the error codes returned by the SCSI system test.
System Test Error Messages, Continued Table A–27 (Continued) SCSI System Test Error Codes SCSI System Test Summary Screen Decimal Hexadecimal Meaning 142 8E Wrong number bytes read when checking for boot block 150 96 Non-DMA inquiry failed in data transfer test 152 98 Synchronous DMA inquiry failed in data transfer test 154 9A Number bytes miscompare in data transfer test 156 9C Data miscompare in data transfer test 160 A0 Device test failed 162 A2 Wrong number bytes read in device t
System Test Error Messages, Continued Format Meaning FRU Field replaceable unit (hexadecimal if FRU gotten from request sense packet) CMD SCSI command that failed (hexadecimal) PHS SCSI Bus phase at time or error INF Informational value (same as those reported by the self-test...hexadecimal) LBNSTRT Starting logical block number of failed transfer (hexadecimal) XFERSIZ Transfer size in blocks of failed transfer (hexadecimal) This information is followed by any available request sense data.
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 the summary screen.
System Test Error Messages, Continued 4 - VAXELN 5 - System 0 00:00:00:00 test run time YY is the specific error code. Table A–28 list the NI system test error codes and their meanings.
System Test Error Messages, Continued Table A–28 (Continued) NI System Test Error Codes Error Source (X) Error Code (YY) Meaning 5 0A Timeout waiting for receive interrupt 5 0C Memory error on init 5 0E BABL Error on init 5 10 MISS Error on init 5 12 Parity error on init 5 14 MAP Error on init 5 16 Memory error on receive 5 18 BABL Error on receive 5 1A MISS Error on receive 5 1C Parity error on receive 5 1E MAP Error on receive 5 20 Memory error on transmit 5 22 BAB
Utility Error Messages SCSI Table A–29 describes the errors returned by a SCSI utility. All SCSI utility errors have the format: text_message information_value.
Utility Error Messages, Continued Table A–30 Additional SCSI Information Values for Utilities Information Decimal Meaning 176 Bad utility number received from the user 177 Bad device number received from the user 178 Bad logical unit number received from the user 179 Wrong number of parameters entered by the user 180 Device number entered by the user is the same as the controller 181 Utility cannot be executed in this mode of operation 182 Not enough data was returned from a SCSI command 183
Utility Error Messages, Continued Table A–30 (Continued) Additional SCSI Information Values for Utilities LCSPX Information Decimal Meaning 197 Illegal floppy drive 198 Illegal floppy media 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.
Utility Error Messages, Continued Table A–31 Menu Item Meanings Menu Item Action 0 Draws a full white screen 1 Draws a full red screen 2 Draws a full green screen 3 Draws a full blue screen 4 Draws four color bars to the screen 5 Draws eight color bars to the screen 6 Draws eight gray scale bars to the screen 7 Draws a screen of Es 8 Draws a screen of squares with a dot in the center of each square.
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.
Utility Error Messages, Continued Table A–32 (Continued) Menu Item Meanings Menu Item Action 8 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 9 Draws a screen of Hs on the screen All test can be terminated by pressing the space bar on the keyboard. If you press either Ctrl Y or Ctrl >box>(C), the test terminates and and the system displays the chevron prompt.
Appendix B Reading the Diagnostic LED Codes Overview In this Appendix This appendix describes how to interpret the diagnostic LEDs on the console control panel.
Diagnostic LED Codes Overview The system uses the eight LEDs on the control panel to indicate 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 fields. The left-most four LEDs represent the device number. The right-most four LEDs represent a substate that the device test is currently in. LED codes E0h - FFh are reserved for the console.
Diagnostic LED Codes, Continued Error Code Tables The rest of this chapter contains tables listing the LED codes, descriptions, and corresponding FRU.
Diagnostic LED Codes, Continued Table B–1 (Continued) Power-up and Initialization LED Codes (1111 XXXX) LED Depiction1 Code Description FRU 1111 1001 F9h Initializing the console data structures System module 1111 1000 F8h Performing auto configuration on the machine System module 1111 0111 F7h Testing the NVR device System module 1111 0110 F6h Testing the DZ device System module, mouse, keyboard 1111 0101 F5h Testing the graphics output device System module, Graphics 1111 0100 F4h
Diagnostic LED Codes, Continued TOY/NVR LED Codes LCSPX LED Codes Table B–2 TOY and NVR LED Codes (0001 XXXX) LED Depiction Code Description FRU 0001 0000 10h TOY and NVR clock test has failed System module 0001 0001 11h TOY and NVR test has failed System module Table B–3 LCSPX LED Codes (0010 XXXX) LED Depiction Code Description FRU 0010 0000 20h LCSPX test has been entered System module, graphics 0010 0001 21h LCSPX video RAM test has failed System module, graphics 0010 0010 22h
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 Codes Table B–4 SPXg/gt LED Codes (0010 XXXX) LED Depiction Code Description FRU 0010 0001 21h JChip and SRAM have failed.
Diagnostic LED Codes, Continued DZ LED Codes Table B–5 DZ LED Codes (0011 XXXX) LED Depiction Code Description FRU 0011 0000 30h DZ Test has been entered System module 0011 0001 31h DZ Reset test has failed System module 0011 0010 32h DZ Modem test has failed System module 0011 0011 33h DZ Polled test has failed System module 0011 0010 34h DZ Interrupt test has failed System module 0011 0101 35h LK401 Test has failed Keyboard, system module 0011 0110 36h Mouse test has failed
Diagnostic LED Codes, Continued CACHE LED Codes Table B–6 Cache LED Codes (0100 XXXX) LED Depiction Code Description FRU 0100 0001 41h Error in the data store read /write System module 0100 0010 42h Error in the read/write to the tag area System module 0100 0011 43h The cache did not contain the correct state of the valid bit System module 0100 0100 44h Error during the cache tag validation System module 0100 0101 45h Unexpected TAG parity error System module 0100 0110 46h Cache d
Diagnostic LED Codes, Continued Memory LED Codes Table B–7 Memory FRU LED Codes (0101 XXXX) LED Depiction Code Description FRU 0101 0000 50h Memory byte mask test has failed System module or memory modules 0101 0001 51h Memory error occurred in the forward pass System module or memory modules 0101 0010 52h Memory error occurred in the reverse pass System module or memory modules 0101 0011 53h Memory error in parity test 1 System module or memory modules 0101 0100 54h Memory error in p
Diagnostic LED Codes, Continued System Device LED Codes NI Device LED Codes Table B–8 System Device LED Codes (1000 XXXX) LED Depiction Code Description FRU 1000 0000 80h ROM Verify test has failed System module 1000 0001 81h Interrupt controller test has failed System module Table B–9 NI LED Codes (1001 XXXX) LED Depiction Code Description FRU 1001 0000 90h NI Test has been entered System module 1001 0001 91h Network address test has failed System module 1001 0010 92h NI Registe
Diagnostic LED Codes, Continued Table B–9 (Continued) NI LED Codes (1001 XXXX) SCSI Device FRU LED Codes LED Depiction Code Description FRU 1001 0111 97h NI Receive MISS /BUFFER test has failed System module 1001 1000 98h NI Collision test has failed System module 1001 1001 99h NI Address filtering test has failed System module 1001 1010 9Ah NI External loopback test has failed Network, loopback, system module 1001 1011 9Bh NI Transmit buffer test has failed System module Table B–1
Diagnostic LED Codes, Continued Table B–10 (Continued) SCSI Device LED Codes (1010 XXXX) Audio Device LED Codes LED Depiction Code Description FRU 1010 0100 A4h SCSI Map error test has failed System module 1010 0101 A5h SCSI Minimal device test has failed Device, System module Table B–11 Audio Device LED Codes (1011 XXXX) LED Depiction Code Description 1011 0000 B0h Audio test has been entered 1011 0001 B1h Audio LIU test has failed 1011 0010 B2h Audio MU1 Register test has failed
Diagnostic LED Codes, Continued DSW21 Communications Device LED Codes Table B–12 DSW21 Communication Device LED Codes (1100 XXXX) LED Depiction Code Description FRU 1100 0000 C0h Comm option code entered DSW21, System module 1100 0001 C1h Comm option ROM test has failed DSW21, System module 1100 0010 C2h Comm option RAM test has failed DSW21, System module 1100 0011 C3h Comm option self-test has failed DSW21, System module 1100 0100 C4h Comm option Dual RAM access test has failed DSW
Diagnostic LED Codes, Continued TURBOchannel Adapter LED Codes Table B–13 lists the TURBOchannel adapter LED codes. Table B–13 TURBOchannel Adapter LED Codes (1100 XXXX) LED Depiction1 Code Description FRU 1101 0000 D0h Entry into test TCA module, TCA option 1101.0001 D1h TCA Register test TCA module, TCA option 1101.0010 D2h TCA Interrupt test TCA module, TCA option 1101.0011 D3h TCA FIFO Test TCA module, TCA option 1101.0100 D4h TCA DMA Trigger test TCA module, TCA option 1101.
Appendix C Troubleshooting Overview In this Appendix The tables in this appendix contain information to help you diagnose problems.
Troubleshooting Overview Troubleshooting is the process of isolating and diagnosing problems with the system. When the system does not operate as described in the VAXstation 4000 Model 90 Owner’s Guide (EKPVAX2-OM), use the information in this section to help diagnose the problem. If the power-up tests complete, you can use the console error messages to identify the failed FRU, or you can run the selftest, system test, and utility tests in Digital Services mode to help isolate the failing FRU.
Troubleshooting, Continued Table C–1 (Continued) System Problems Symptom Possible Cause Corrective Action Wall socket may not be operative. Try a different wall socket, or try an electrical device that you know works in the wall socket. Turn the system off for 10 seconds. Then turn the system on and then off again. Disconnect the video, communication, and printer cables from the power source, then reconnect securely at both ends and turn the power on to the system.
Troubleshooting, Continued Table C–1 (Continued) System Problems Symptom Possible Cause Corrective Action Alternate console switch is in wrong position. Turn the power off. Move the alternate console switch to the down (off) position. Use a small pointed object. Do NOT use a pencil to set the switch. Turn the power back on. Monitor fuse is blown. See the monitor guide for fuse replacement instructions. Wall socket may not be operative.
Troubleshooting, Continued Table C–1 (Continued) System Problems Symptom Power-up display contains an error message. Possible Cause Corrective Action Power supply connector to system module is not seated correctly. Correctly connect power source to CPU module. Possible system error. Enter the SHOW ERROR command. Refer to the error code tables in the VAXstation 4000 Service Information Kit Model 90 Base System to interpret the error code. Interpret the diagnostic LEDs at the front of the system.
Troubleshooting, Continued Table C–1 (Continued) System Problems Symptom Possible Cause Corrective Action Incorrect boot device was specified. Change the default recovery action to boot the system from the system disk. Expansion boxes were not powered on first. Turn the system box off, make sure the expansion boxes are on, and then turn on the system box. Boot device is not properly configured. Enter the SHOW DEVICE command and ensure that all devices are configured correctly.
Troubleshooting, Continued Table C–2 (Continued) Monitor Problems Symptom Possible Cause Corrective Action Contrast and brightness controls are set incorrectly. Adjust the contrast and brightness controls. Refer to the monitor guide for more information. Alternate console switch is not set correctly. Turn off the system. Change the alternate console switch to the down (off) position. Use a small pointed object. Do NOT use a pencil to set the switch. Turn on the system. Turn on the system box last.
Troubleshooting, Continued Mouse/Tablet Problems Table C–3 Mouse/Tablet Problems Symptom Possible Cause Corrective Action System boots but mouse or optional tablet pointer does not appear on the screen, or monitor does not respond to pointing device commands. Pointing device cable is installed incorrectly or is loose. Turn off the system. Disconnect then reconnect the cable to rest the device. Turn on the system. The system is halted; no pointer appears on the screen. Reboot the system.
Troubleshooting, Continued Table C–4 (Continued) Keyboard Problems Symptom Possible Cause Corrective Action Keyboard strokes are inconsistent. – Disconnect then reconnect in the keyboard. Keyboard has failed. Replace the keyboard. Drive problems Table C–5 Drive Problems Symptom Possible Cause Corrective Action Software does not work from the diskette drive, or a diskette read or write error message displays. No diskette is in the diskette drive. Insert a diskette with software.
Troubleshooting, Continued Table C–5 (Continued) Drive Problems Symptom Drive does not work. Possible Cause Corrective Action Two SCSI identifiers are set to the same ID number. Reset each SCSI ID to a unique number. Loose cables. Verify that all cables are securely connected. Defective drive. Run diagnostics to isolate fault. Replace FRU. Two SCSI identifiers are set to the same ID number. Reset each SCSI ID to a unique number. Loose cables. Verify that all cables are securely connected.
Troubleshooting, Continued Table C–6 (Continued) Network Problems Symptom Possible Cause Corrective Action Network switch is not set correctly. If Ethernet is not being used, move the network switch to the left, toward standard Ethernet. Terminator is missing from network. Determine if a ThinWire cable was removed. If so, replace the cable with a terminator. Cable connection is loose. Verify that all connections on the Ethernet segment are secure. Power supply failure. Replace the power supply.
Troubleshooting, Continued Audio Problems Table C–7 Audio Problems Symptom Possible Cause Corrective Action No audio tone (beep) when the system is turned on. Speaker is turned off. Turn on speaker using the switch located on the front of the system box. Audio speaker is not working. Turn off the system. Plug in the headset and turn the system on. If you hear an audio tone from the headset, then there is a problem with the speaker. Replace the lights and switches module. Defective sound chip.
Troubleshooting, Continued Table C–8 (Continued) Expansion Box Problems Symptom Possible Cause Corrective Action Power light is off. Power cord is not connected. Ensure that the power cord is connected at both ends. Wall socket may not be operative. Try a different wall socket, or try an electrical device that you know works in the wall socket. Turn the system off for 10 seconds and then back on. Turn the system off. Drive does not work. Defective power supply. Replace the power supply.
Appendix D FRU Part Numbers Overview In this Appendix The tables in this chapter provide the names and part numbers for the field replaceable units (FRUs) for the Model 90 system box.
Precautions Overview Only qualified service personnel should remove or install FRUs. 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 site. This is important to ensure that data is not lost during the service process.
Model 90 System Box FRUs Table D–1 contains the part numbers for the Model 90 FRUs.
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 RZ24 Disk 209-MB Drive RZ24L-E RZ24L Disk 245-MB drive RZ25-E RZ25 420-MB drive TZK10-AA TZK10 QIC Tape drive RRD42-AA RRD42 CD ROM reader
Model 90 System Box FRUs, Continued Table D–2 (Continued) System Monitors Part Number Description VRT19(DA,*D3,D4),HA,H4 19" Color VRM17HA,H4,(AA,A4) 17" Color *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 3-D Graphics dial box VSXXA-KA Lighted programmable keyboard VSXXX-AB Tablet VSXXX-EA Gray mouse pad VSXXX-GA Three-Button
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 halfheight 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 Bracket for mounting RZ25 only 3 1/2 in drive mounting bracket 74-41472-01 Rear opening filler 74-41473-01 Rear opening RFI shield filler 74-41734-
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 Thickwire and ThinWire Ethernet Kit BC16M-xx ThinWire Ethernet cable xx = 6, 15, 30 refers to length in feet BNE3H-xx Thickwire
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 Part Number Description BZOD-03, 06, 12 D–8 H8578-AA Terminator H4082-AA 10BaseT Terminator
Expansion Box FRUs Table D–6 contains the part numbers for the expansion box.
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 kit 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 Base plastic assembly 70-28106-01 Enclosure assembly 70-28107-01 Top plastic cover 74-409
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 Internal SCSI data cable Assembly 70-28109-01 Internal SCSI data cable Table D–10 SZ03 Sidecar Part Number Description 30-36532-01 Chas
Expansion Box FRUs, Continued Table D–11 SZ03 Miscellaneous Hardware Part Number Description 12-30934-01 Screw, sems 6-32 PAN .
Index A Adapter board inserting TURBOchannel (fig.
Console commands SET/SHOW (cont’d) SCSI, 4–17 TRIGGER, 4–18 Console devices, 2–5 Console driver interface, 2–31 Console mode, 2–5 Console Mode Input and Output, 2–5 Console Port Driver, 2–34 Console Requester, 5–84 Control panel, 3–8 Correctable ECC Errors, 5–76 Correctable Memory Error Entries, 5–65 Correctable Reset Data Buffer, 5–65 CPU Components, 1–3 CPU module removal, 6–39 replacement, 6–40 Driver descriptor (cont’d) overview, 2–27 Drive removal, 6–8 DSW21 removal, 6–41 replacement, 6–41 DSW21 commu
Error Messages (cont’d) SYS Device, A–21 TOY/NVR, A–8 Error reporting console error codes FRU, A–6 Errors Correctable ECC, 5–76 uncorrectable ECC, 5–73 Ethernet Interface, 1–9 Exceptions, 1–17 Extended Error Information, A–46 Extended Error Messages SHOW ERROR, A–4 Extended self-test sequence, 2–6 F Failing Logical Block Field LCSPX, A–78 SPXg/gt, A–81 Fault isolation, C–2 to C–13 FCC shield attaching (fig.
K KA49 system module, 1–5 KA49 CPU Module, 1–1 L LCSPX Module, 1–26 LCSPX Self-test error codes, A–77 LCSPX Self-Test, 5–20 LCSPX utilities, 5–46 Menu, 5–47 LCSPX Utilities, A–92 LED error codes, B–2 Light and switches module removal, 6–23 replacement, 6–24 Log file generated by UETP OLDUETP.
P Password console, 4–16 features, 4–16 system clearing, 6–47 Patchable Control Store Error messages, 5–102 Performing I/O, 2–31 Physical addresses system ROM, 2–14 Plastic standoffs for TURBOchannel adapter board, 6–52 Power LED, 3–8 Power supply overview, 3–3 physical dimensions, 3–6 removal, 6–21 replacement, 6–22 specifications, 3–4 to 3–6 voltage, 3–3 Power-up initialization code scratch RAM, 2–20 Power-up Initialization Code, 2–2 Power-up sequence, 2–2, 5–4 Power-up test, 5–4 Printer port console, 4–2
SGEC, 1–9 Shared console interface area overview, 2–32 SHOW ERROR, A–4 SHOW CONFIG, 4–7, 5–9 SHOW DEVICE, 5–8 SIM module (Single in-line memory module), 6–28 Small Computer Systems Interface SCSI, 1–9 Sound Generator, 1–10 Specifications power supply, 3–4 to 3–6 TURBOchannel, 6–63 TURBOchannel option (tab.
T Test Dispatcher, 2–6 Testing TURBOchannel installation, 6–62 Testing the Installation, 6–62 Testing the System, 6–48 Test Numbers LCSPX, A–78 SPXG/gt, A–82 Three Level Cache Architecture, 1–7 Time-of-Year Clock TOY, 1–10, 1–30 TOY/NVR Error Messages, A–8 TOY Self-Test, 5–19 TRIGGER, 5–48 Troubleshooting, C–2 to C–13 diagnostic testing, 5–1 UETP, 5–90 TURBOchannel adapter component descriptions (tab.), 6–52 diagnostic LED codes, B–14 error codes, A–55 function of, 6–52 inserting (fig.
V VAXsimPLUS, 5–56 VMS error handling, 5–57 event record translation, 5–68 Index–8 VMS Error Logging and Event Log Entry, 5–60 Voltage select, 3–3 W Watch Chip Registers, 1–30 Wrist strap, 6–2
