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.
No responsibility is assumed for the use or reliability of software on equipment that is
not supplied by Digital Equipment Corporation or its affiliated companies.
Restricted Rights: Use, duplication, or disclosure by the U. S. Government is subject
to restrictions as set forth in subparagraph(c)(1)(ii)oftheRights in Technical
Data and Computer Software clause at DFARS 252.227–7013.
D–12 SZ03 Cables and Terminators . . ..................................... D–12
Contents–x
Overview
Preface
Purpose and
Audience
Organization
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.
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.
Chapter 2, Firmware, provides information on diagnostic
firmware.
Chapter 3, System Configuration, provides configuration
information on the system box.
Chapter 4, Using the Console, describes system console
commands and using alternate consoles.
Chapter 5, Diagnostic Testing, provides information on
diagnostic testing.
Chapter 6, FRU Removal and Replacement, provides
information on how to remove and replace system field
replaceable units.
Continued on next page
xi
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.
Guide
BA46 Expansion Box Service InformationEK-VBA46-SV
The following documents provide additional information about the
VAXstation 4000 Model 90 workstation:
EK-VAXOG-IN
EK-SCP8P-MG
Continued on next page
xii
Overview,Continued
Conventions
This guide uses the following conventions:
ConventionDescription
WARNINGContains important information that
relates to personal safety.
CAUTIONContains information to prevent damage
to the equipment.
NOTEContains general information.
PNPart number
Ctrl/CThis type of key sequence means you
hold down the first key while you type
the letter of the next key.
THIS TYPEFACEIndicates text the system displays.
THIS TYPEFACEIndicates user input.
Return
Text within a box means you press that
key.
SHOW ERRORCommands that you enter are shown in
all uppercase text.
!
A number in a circle in text corresponds
to that number in an illustration.
xiii
Introduction
Chapter1
SystemModule
In this Chapter
This chapter describes the features of the VAXstation 4000 Model
90 system module. The topics covered include:
System Overview
Central Processor Unit (CPU)
Interrupts and Exceptions
Cache Memory
Main Memory System
ROM Memory
Graphics Controller
Network Interface Controller
Serial Line Controller
Time-of-Year Clock (TOY)
SCSI Controller
DSW21 Synchronous Communications Adapter
1–1
System Overview
Overview
Main Memory
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. A 16-bit programmed I/O port
connection is available to attach synchronous communications
or other options. An optional bus adapter can be connected to
the module using one of the 32-bit CDAL buses. Four serial
lines are supported for a keyboard, pointing device, printer,
and asynchronous communication. Audio input and output is
supported through the sound generator interface. The KA49 CPU
module supports low cost graphics using the LCSPX module or
high performance graphics using the SPXg/gt modules.
The KA49 CPU module can support up to eight memory SIM
modules to provide main memory configurations of 16, 32, 64, 80,
or 128 MB.
Cache Memory
1–2
The module uses multiple levels of cache memory to maximize
performance. The NVAX CPU contains a 2-KB virtual instruction
cache (VIC) and an 8-KB write-through primary cache (Pcache).
The KA49 module contains an on board 256-KB backup write
secondary cache (Bcache).
Continued on next page
System Overview,Continued
CPU
Components
Table 1–1 Major Components
DC246Central processorNVAX
Cache RAMs256-KB Bcache—–
DC243NDAL to CDAL I/O bus interface chipNCA
DC244Main memory controller, with ownership
Figure 1–2 shows how, functionally, the KA49 CPU module is
divided into five major areas.
Central processing subsystem
Graphics subsystem
System support subsystem
I/O Subsystem
Memory control subsystem
Continued on next page
1–5
Central Processor Unit, Continued
Figure 1–2 KA49 CPU Module Block Diagram
G-BITS
256KB
CACHE
& TAG
NVAX
CONSOLE
ROMS
TURBO
CHANNEL
GRPHCS
ADAPT
SPXG
& GT
NCANMC
CP2
CP1
LCSPX
SGEC
CEAC
SQWF
EDAL
NDAL
DMA RAMS
QUART
SCSI
TOY
SYNC COM
LEDS
CNFG REG
SOUND
EID ROM
DC7238
XCVR
Memory
16-128 MEG
DC7238
XCVR
SIMMS
LJ-01816-TI0
1–6
Continued on next page
Central Processor Unit,Continued
Central
Processing
Subsystem
Three Level
Cache
Architecture
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.
The KA49 CPU module uses a three-level cache architecture to
maximize performance. The first level of cache, referred to as
the virtual instruction cache (VIC), is 2 KB in size, and is located
on the CPU chip. This cache handles instructions only (no data
references), and deals only with virtual addresses. In this way
the CPU can obtain instruction information without the need for
virtual to physical address translation, thereby decreasing latency
and improving performance.
The second level of cache, referred to as the primary cache
(Pcache), is 8 KB in size and is located on the CPU chip. This
cache implements a write-through instruction and data cache, and
helps to reduce latency on access to data and instructions that are
not found in the VIC. The Pcache uses physical addresses.
Graphics
Subsystem
The third level of cache, referred to as the backup write cache
(Bcache) is 256 KB. The Bcache is controlled by the Bcache
controller located in the CPU chip. The data and tag store
memory for this cache is located in SRAM chips on the KA49
CPU module. The Bcache uses physical addresses.
The graphics subsystem consists of either the LCSPX for low cost
graphics support or the SPXg/gt modules, which support high
performance graphics. Two connectors are provided on the module
that provide a unique interface to each.
Continued on next page
1–7
Central Processor Unit, Continued
System
Support
Subsystem
ROM Firmware
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 EPROM
1
, for a total of 512 KB of
ROM. The firmware gains control when the CPU halts.
ROM firmware provides the following services:
Board initialization
Power-up self-testing of the KA49 module
Emulation of a subset of the VAX standard console (auto
or manual bootstrap, auto or manual restart, and a simple
command language for examining or altering the state of the
processor)
Booting from supported Ethernet or SCSI devices
Configuration
Register
I/O Subsystem
Multilingual translation of key system messages
The configuration register allows the firmware and the operating
system to read KA49 configuration bits. These bits indicate which
options are present and the size of the physical memory.
The I/O subsystem contains the following:
CP-Bus adapter
SCSI mass storage interface
Ethernet interface
Optional bus adapter interface
Optional synchronous communication interface
1
A FLASH EPROM is a programmable read-only memory that uses electrical (bulk)
erasure rather than ultraviolet erasure.
Continued on next page
1–8
Central Processor Unit,Continued
Sound generator
Four asynchronous lines
Time-of-Year clock
Ethernet identification ROM
NVAX CP-Bus
Bus Adapter
Small
Computer
Systems
Interface
Ethernet
Interface
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. Each of the NCA’s
CP-Bus ports provide a CVAX compatible peripheral bus for direct
memory access (DMA) by peripheral devices.
NCR 53C94 implements the small computer system interface
(SCSI) bus interface. It has a single port, connecting both to
devices within the BA46 system box and allowing for expansion
externally.
The Ethernet interface handles communications between the CPU
module and other nodes on the Ethernet. It is implemented with
the second generation Ethernet controller chip (SGEC) onboard
network interface. Used in connection with the module backpanel,
the SGEC allows the KA49 to connect to either a ThinWire or
standard Ethernet. It supports the Ethernet data link layer and
provides CP-Bus parity protection.
Optional
Bus Adapter
Interface
The optional bus adapter provides a translation between one of
the CP-Buses and the adapter bus. The VAXstation 4000 Model
90 has direct, transparent access to the bus adapter. The slot
appears as a region of memory in the workstation’s I/O space.
The bus adapter option can perform DMA to any location in the
memory space of the VAXstation 4000 Model 90. This DMA can be
done either directly to the physical memory of the workstation or
Continued on next page
1–9
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
Serial Line
Controller
Time-Of-Year
Clock
Sound output uses the DTMF tone generation capability of
the 79C30 chip. Two tone generators may be individually
programmed for frequency and amplitude; their outputs appear
summed using either the loudspeaker integral to the system
unit, or to headphones, or an external loudspeaker if plugged
in to the jack at the front of the machine. The resolution of the
frequency generators is eight bits, giving a frequency range of 8
Hz to approximately 2 kHz.
The VAXstation 4000 Model 90 system board serial line controller
handles four asynchronous serial lines. The controller consists of
the DC7085 QUART and a 64 entry FIFO RAM shared by all four
receive lines.
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 logic and oscillator while the system power is off.
Station
Address ROM
Memory
Control
Subsystem
1–10
A 32-byte ROM on the system board contains a unique network
address for each system. This ROM is installed in a socket so it
can be moved in the event that a system’s CPU board is replaced.
The memory control subsystem provides support for the KA49
memory subsystem. A key feature of the KA49 memory
subsystem is the use of ownership bits to maintain a sense
of ownership over each hexaword (32 bytes) of main memory.
This ownership mechanism serves the dual function of
maintaining coherency between main memory and the NVAX
Continued on next page
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). In addition, the
NMC has a key role in maintaining main memory coherency with
the NVAX Pcache and Bcache through the use of ownership bits.
The NMC interfaces the NVAX and I/O subsystem to up to 128
MB of main memory. Main memory is comprised of one or two
sets of SIM modules. Each set contains either four 4-MB SIM
modules or four 16-MB SIM modules. The NMC controls access to
shared memory locations through the use of the ownership bits,
thereby providing a reliable interlock mechanism for memory that
is shared between the NVAX and the I/O devices.
NVAX
Data/Address
Lines
Processor
State
In order to maximize the bandwidth of the bus connecting the
CPU to the memory and I/O controllers, the NVAX chip set
(NVAX, NMC, NCA) communicates over a "pended" bus called the
NDAL. The main feature of this bus is that devices requesting
read data do not tie up the bus while waiting for the return data.
Rather, a device issues one of the "read" commands on the NDAL
and then relinquishes control of the bus to other devices. This is
so other transactions can be performed while the responder to the
first device prepares to send back the data associated with the
read request. Because of the pended nature of the bus, the NDAL
bus command set includes separate transactions for returning
data from an earlier read cycle.
The processor state consists of that portion of the state of a
process that is stored in processor registers rather than in
memory. The processor state is composed of 16 general purpose
registers (GPRs), the processor status longword (PSL), and the
internal processor registers (IPRs).
Continued on next page
1–11
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 VAXArchitecture Reference Manual. These registers are used for
temporary storage, accumulators, and base and index registers
for addressing. These registers are denoted R0 - R15. The bits
of a register are numbered from the right <0> through <31>.
Table 1–2 describes the registers.
Table 1–2 General Purpose Register Descriptions
Register Register NameMnemonic Description
R15Program CounterPCThe PC contains the address of the next
instruction byte of the program.
R14Stack PointerSPThe SP contains the address of the top of
the processor defined stack.
R13Frame PointerFPThe call convention builds a data structure
on the stack called a stack frame. The FP
contains the address of the base of this data
structure.
R12Argument PointerAPThe call convention uses a data structure
termed an argument. The AP contains the
address of the base of this data structure.
Continued on next page
1–12
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 block may be deallocated
Pcache Tag IPRs—The read-write block of IPRs that allow
direct access to the Pcache tags
Pcache Data Parity IPRs—The read-write block of IPRs that
allow direct access to the Pcache data parity bits
1–13
Interrupts and Exceptions
Overview
Nonmaskable
Interrupts
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 can be divided into two classes: nonmaskable and
maskable. Nonmaskable interrupts cause a halt by way of the
hardware halt procedure. The hardware halt procedure does the
following:
Saves the PC, PSL, MAPEN<0> and a halt code in IPRs
Raises the processor IPL to 1F
Passes control to the resident firmware
The firmware dispatches the interrupt to the appropriate service
routine based on the halt code and hardware event indicators.
Nonmaskable interrupts cannot be blocked by raising the
processor IPL.
Maskable
Interrupts
1–14
Maskable interrupts cause the following:
The PC and PSL are saved.
The processor IPL is raised to the priority level of the
interrupt.
The interrupt is dispatched to the appropriate service routine
through the system control block (SCB).
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.
Bcache uncorrectable data ECC errors on
Bcache read for a write that hits valid/owned
NVAX read timeout or read data error
on Bread for a write after the requested
quadword has arrived
Illegal length write transaction to memory or
I/O
Reserved command detected by memory or I/O
during write transaction
60
60
60
60
Pending write times out waiting for disown
write
Disown write to unowned memory location60
Main memory NXM errors on writes60
NDAL parity errors on writes60
CP-Bus NXM/TIMEOUT on a write60
1CUnused
1BPerformance monitoring interrupt (internally
handled by microcode)
** These conditions generate a hardware halt procedure with a halt code of 2 (external halt).
60
Continued on next page
1–15
Interrupts and Exceptions,Continued
Table 1–3(Continued) Interrupt Priority Levels
Priority LevelInterrupt ConditionSCB Offset
1ACorrectable main memory errors54
Uncorrectable main memory errors54
Correctable O-bit memory errors54
Pending read times out waiting for disown
write
No acknowledgment on returned read data
from NMC
NDAL Data parity errors54
Pcache tag or data parity errors54
VIC tag or data parity errors54
Bcache addressing errors54
Bcache correctable data ECC errors54
Bcache uncorrectable data ECC errors54
Bcache correctable tag ECC errors54
Bcache uncorrectable data ECC errors54
Illegal length transaction to memory or I/O
space
Reserved command to memory or I/O space54
CP-Bus parity errors on I/O read transactions54
CP-Bus ERR_L signal asserted by I/O device
during I/O read transaction
54
54
54
54
CP-Bus NXM/TIMEOUTS errors on I/O reads54
19:18Unused
17IRQ_H[3] assertedUnused
** These conditions generate a hardware halt procedure with a halt code of 2 (external halt).
Continued on next page
1–16
Loading...
+ 402 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.