Contents

The following Help Topics are available:


Copyright and Trademarks

The information used in this document is subject to change without notice and should not be construed as a commitment from Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that appear in this document.

Possession, use, duplication, or dissemination of the software described in this documentation is authorized only pursuant to a valid written license from Digital or the third-party owner of the software copyright.

Copyright © Digital Equipment Corporation 1997. All rights reserved.

The following are trademarks of Digital Equipment Corporation:  AlphaGeneration, AlphaStation, DECchip, DEC, DECstation, DECsystem, DECWORLD, OpenVMS, VAX, VAXstation, Digital, and the DIGITAL logo.

Windows NT is a trademark of Microsoft Corporation.

UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Ltd.


System Overview

Features
The Digital AlphaStation 600A Model 5/500 system offers the following features:

•	Choice of operating system: Windows NT, Digital UNIX, or OpenVMS

•	EV56 CPU with a 128-KB serial-boot ROM

•	I/O subsystem Ethernet/small computer system interface (SCSI) peripheral component interconnect (PCI) module

•	Up to 1 gigabyte (GB) of system memory

•	Three-year warranty

Technical Specifications

For technical specifications, click on one of the specification types.

  Mechanical

  Electrical

  Environmental


Mechanical Specifications

Height:	446.2 mm (17.4 in.)
Width:	241.0 mm (9.4 in.)
Depth:	651.3 mm (25.4 in.)
Operation clearance:	100.0 mm (3.9 in.)
Weight (fewest options):	32+ kg (70+ lbs)


Electrical Specifications

Power supply:	Rated at 400 watts (maximum) output, this power supply supports -12.0, -5.0, +3.43, +5.1, +12.0V  DC output voltages.
	DC Outputs	Maximum     Load	Maximum     Power
	-12.0 V	0.2 amp	2.4 W
	-5.0 V (auxiliary)	0.6 amp	1.0 W
	+3.4 V	36.4 amp	120.0 W
	+5.0 V	52.0 amp	265.0 W
	+12.0 V	11.0 amp	132.0 W
Note:	The maximum power from any combination of +3.3V DC and +5.0V DC does not exceed 335 watts.


Environmental Specifications

Storage temperature range:	-40 [image] C to 66 [image] C  (-40 [image] F to 151 [image] F)
Operating temperature range:	10 [image] C to 40 [image] C (50 [image] F to 104 [image] F)
Maximum rate of change:	11 [image] C (20 [image] F) per hour
Storage humidity range   (noncondensing):	10% to 90% relative humidity;  maximum wet bulb 65 [image] C (149 [image] F)
Operating humidity range (noncondensing):	10% to 90% relative humidity (without removable media) or 20% to 80% relative humidity (with removable media); maximum wet bulb 2 [image] C (36 [image] F)
Maximum altitude:	Nonoperating--4867 meters (16000 feet); Operating--2400 meters (8000 feet)
Acoustic power:	Nonoperating--5.1 B LWAd; Operating--5.2 B LWAd
Acoustic pressure:	Nonoperating--33 dBA LpAm; Operating--34 dBA LpAm
Shipping vibration:	IAW Federal Standard 101, method 5019
Nonoperating shock:	30 G, 25 ms halfsine


System Front View

1.  Indicator lights (power and disk activity)
2.  On/Off button
3.  Internal storage bay (the drive assembly)
4.  Reset button
5.  Halt button
6.  Diskette eject button
7.  Diskette drive
8.  External storage bay


System Rear View

 1.    Mouse connector
 2.    Keyboard connector
 3.    Serial port connectors
 4.    Parallel port connector
 5.    Video port (on option module)
 6.    Network connectors
 7.    AC power connector
 8.    Security loop (for attaching a cable or lock)
 9.    Additional SCSI slots
10.   68-pin SCSI connector
11.   50-pin SCSI connector
12.   Side-panel lock


System Block Diagram


FRU Part Numbers

CAUTION:  Always wear a grounded wrist strap when servicing internal components of the AlphaStation 600A 5/500 system.

Part Numbers	Field-Replaceable Units (FRUs)
12-41768-01	SCSI terminator
17-03970-01 A03	Diskette-drive cable
17-03971-03	OCP cable
17-04009-01 B01	Wide-to-narrow SCSI adapter
17-04403-01 A01	Wide internal SCSI harness
17-04190-01	Microswitch assembly   (fan cable; interconnect cable part of tower; speaker cable)
30-43120-02	Power supply (SMS)
AVA01-AA	MS SoundSystem
30-42635-01	MS WIN audio card
30-44395-01	Oak audio card
54-23302-02	OCP module
54-21246-BA	DRAM SIMM (8MBx36, 60-ns)
54-23170-BA	DRAM SIMM (16MBx36, 60-ns)
54-21277-BA	DRAM SIMM (32MBx36, 60-ns)
54-24123-AA	DRAM SIMM (64MBx36, 60-ns)
54-23499-02	Motherboard (MLB)
54-24799-03	CPU daughter board (EV56, 500 MHz)
70-31351-01	Cooling fan
70-31349-01	Speaker assembly
Additional Options' Part Numbers

Part Numbers	Options	Description
	Storage
PBXRX-AA		3.5-inch 1.44-MB diskette w/industry gray (RX23L);    3.5-inch 1-GB, LP SCSI (16-bit wide) disk (RZ26L);    3.5-inch 2-GB, HH SCSI (16-bit wide) disk (RZ28)
PBXRD-CA		Double-speed, high-performance, 600-MB SCSI    tape (RRD45)
	Video
PBXGA-AA		TGA 8-plane graphics adapter
PBXGA-BA		TGA 24-plane graphics adapter
PBXGA-CA		TGA 24Z-plane graphics adapter
	Keyboard
LK46W-		OpenVMS/Digital UNIX
LK47W-		PC Style


Connector Pinouts

Click on specific pinouts for descriptions.


Keyboard Connector Pinouts

The keyboard connector is a miniature, six-position, circular DIN receptacle.

Pin	Signal
1	KBData
2	N/C
3	Ground
4	+5V DC
5	KBClock
6	N/C


Mouse Connector Pinouts

The mouse connector is a miniature, six-position, circular DIN receptacle.

Pin	Signal
1	MSData
2	N/C
3	Ground
4	+5V DC
5	MSClock
6	N/C


68-Pin High-Density SCSI Port

The 68-pin high-density port (a single-ended P-cable) uses the following connector contact assignments:

Pin	Signal	Description		Pin	Signal	Description
1	Ground			35	DB(12)*	Data-bus line 12
2	Ground			36	DB(13)*	Data-bus line 13
3	Ground			37	DB(14)*	Data-bus line 14
4	Ground			38	DB(15)*	Data-bus line 15
5	Ground			39	DB(P1)*	Data-bus parity
6	Ground			40	DB(0)*	Data-bus line 0
7	Ground			41	DB(1)*	Data-bus line 1
8	Ground			42	DB(2)*	Data-bus line 2
9	Ground			43	DB(3)*	Data-bus line 3
10	Ground			44	DB(4)*	Data-bus line 4
11	Ground			45	DB(5)*	Data-bus line 5
12	Ground			46	DB(6)*	Data-bus line 6
13	Ground			47	DB(7)*	Data-bus line 7
14	Ground			48	DB(P)*	Data-bus parity
15	Ground			49	Ground
16	TERMPWR	Terminate Power		50	Ground
17	TERMPWR	Terminate Power		51	TERMPWR	Terminate Power
18	Reserved			52	TERMPWR	Terminate Power
19	Ground			53	Reserved
20	Ground			54	Ground
21	Ground			55	ATN*	Attention
22	Ground			56	Ground
23	Ground			57	BSY*	Busy
24	Ground			58	ACK*	Acknowledge
25	Ground			59	RST*	Reset
26	Ground			60	MSG*	Message
27	Ground			61	SEL*	Select
28	Ground			62	C/D*	Control/Data
29	Ground			63	REQ*	Request
30	Ground			64	I/O*	Input/Output
31	Ground			65	DB(8)*	Data-bus line 8
32	Ground			66	DB(9)*	Data-bus line 9
33	Ground			67	DB(10)*	Data-bus line 10
34	Ground			68	DB(11)*	Data-bus line 11
Notes:	An asterisk (*) following a signal name indicates an active-low signal.   Reserved lines are open in the bus-terminator assemblies and in SCSI devices on the SCSI bus; they have continuity from one end of the SCSI bus to the other.


Communications Port Pinouts

The AlphaStation 600A Model 5/500 system uses two identical nine-position subminiature-D serial-line male connectors for communications. These serial ports support baud rates of 300, 1200, 2400, 4800, 9600, 19 200, and 38 4000 and use the following connector contact assignments:

Pin	Signal	Description
1	DCD	Data carrier detect
2	RXD	Receive data
3	TXD	Transmit data
4	DTR	Data terminal ready
5	GND	Signal ground
6	DSR	Data set ready
7	RTS	Request to send
8	CTS	Clear to send
9	RI	Ring indicator


Bidirectional Parallel Port Pinouts

A 25-position subminiature-D parallel-port female connector provides an interface to a printer (or other parallel devices) and uses the following connector contact assignments:

Pin	Signal	Description
1	STB-R*	Strobe
2	PRTD0	Printer data bit 0
3	PRTD1	Printer data bit 1
4	PRTD2	Printer data bit 2
5	PRTD3	Printer data bit 3
6	PRTD4	Printer data bit 4
7	PRTD5	Printer data bit 5
8	PRTD6	Printer data bit 6
9	PRTD7	Printer data bit 7
10	ACK*	Acknowledge
11	BUSY	Busy
12	PE	Paper end
13	SLCT	Select
14	AUTOFDXT*	Autofeed
15	ERR*	Error
16	INIT*	Initialize printer
17	SLCTIN*	Select input
18 to 25	GND	Ground
Note:	An asterisk (*) following a signal name indicates an active-low signal.


Jumpers

For information about specific jumpers, click on one of the following system components:

  Motherboard

  CPU Daughter Board


Motherboard Jumpers

The following figure shows the location and default settings for the jumpers located on the motherboard.

The motherboard jumper pins allow you to set specific parameters by changing the pin location on the jumper blocks. To change a jumper setting, remove the jumper from its current location using either your fingers or a pair of small needlenose pliers. Place the jumper over the two pins designated for the desired settings. Press the jumper evenly onto the pins; be careful not to bend the pins.

Jumper	Name	Description	Default Setting
J16	Large Fan	Allows the large fan to be disabled to accommodate the alternative enclosures	This jumper is not installed on AlphaStation 600A Model 5/500 Systems.
J50	Flash ROM VPP Enable	Permits the 12V voltage needed to update the Flash ROMS.	Jumper installed.
J51	SCSI Termination	Allows the internal SCSI terminator to be disabled.	Enabled (as show).
J52	Temperature Shutdown	Allows the temperature sensor to shut down the system in an over temperature condition.	Currently ships enabled (as shown).
J53	Force Shutdown	Allows the operating system  to shut down the system if a fan fails or an over temperature condition occurs.	Enabled (as shown).
J56	Fan Fault	When enabled, the hardware forces the system to shut down if a fan fails. When disabled, the firmware generates a machine check when and enclosure fan fails--it is up to the operating system to shut the system down.	Enabled (as shown).


CPU Daughter Board Jumpers

The CPU daughter board contains two jumpers, J1 and J3. Jumper J3 should not have any jumpers installed on its pins. Jumper J1 should have a jumper installed on its bank 0 pins.

The following lists the bank positions on J1 and a description of each.

Bank	Jumper Setting
0	Standard boot setting (AlphaStation 600A 5/500 systems)
1	Standard boot setting (AlphaStation 600A 5/500 systems)
2	Mini-console setting: Internal use only
3	Mini-console setting: Internal use only
4	Power up with no Bcache: Power up with Bcache disabled allows the system to run despite bad Bcache until a replacement CPU daughter board is available
5	Mini-console setting: Internal use only
6	Mini-console setting: Internal use only
7	Fail-Safe Loader setting: selects fail-safe loader firmware


Error Codes

The AlphaStation 600A Model 5/500 systems report errors and status to the OCP during SROM power-up tests. The following three categories of status and error codes apply:

Execution Status Codes

Nonfatal Error Codes

Fatal Error Codes

Note:  If errors are reported, ensure that the CPU daughter board is properly seated in its connectors.


Execution Status Codes

Execution status codes identify the process that is currently underway. The following is a list of execution status codes along with a description of each.

OCP Code	Description
DF	SROM program beginning to initialize the EV56 CPU
DE	Initialize CPU and system interface
DD	Sizing CPU speed
DC	Sizing S-cache
DB	Initializing and testing  the PCI bus
DA	Sizing B-cache
D9	Sizing memory
D8	Configuring memory
D7	Initializing B-cache
D6	Testing memory
D5	Testing B-cache bits
D4	Testing memory bits
D3	Testing B-cache address
D2	Testing memory address
D1	Testing B-cache cells
D0	Testing memory cells
CF	Initializing memory
CD	Loading Flash ROM code
CC	Re-initializing CPU and system interface
CB	SROM execution completed


Nonfatal Error Codes

Nonfatal error codes identify errors that may not prevent the system from accessing the console, but may prevent the system from successfully booting the operating system. The following is a list of nonfatal error codes along with a description of each and the FRU that is likely causing it.

OCP Code	Description	Likely FRU
EB	CPU speed error detected	CPU daughter board
EA	PCI-to-PCI (PPB) data path error	Motherboard
E9	No real-time clock (TOY)	TOY/NVRAM chip
E6	EISA configuration NVRAM
E5	Main memory data path error
E4	Q-logic SCSI data path error
E3	Main memory address lines error
E2	Super I/O error
E1	Main memory cell test error
E0	Flash ROM checksum error


Fatal Error Codes

Fatal error codes identify errors that prevent the system from accessing the console and booting the operating system. The following is a list of fatal error codes along with a description of each and the FRU that is likely causing it.

OCP Code	Description	Likely FRU
FF	No S-cache bits set in SC_CTL register	CPU daughter board
FD	Floppy load error	Bad or wrong diskette in drive
FA	No usable memory detected	SIMM memory or backplane
F9	System initialization failure	CPU daughter board
F8	PCI data path error	CPU daughter board
F7	CIA/PCEB I/O register initialization failure	CPU daughter board
F6	Bad CIA memory CSR was detected	CPU daughter board
F4	B-cache data path error	CPU daughter board
F3	B-cache address line error	CPU daughter board
F1	Flash ROM data path read error	CPU daughter board


Field Replacable Unit (FRU) Replacement
Field Replaceable Unit (FRU) Replacement

Click on any of the items listed below to access the procedures related to removing and replacing the FRUs.

Opening the Enclosure

Single Inline Memory Modules (SIMMs)

Operator Control Panel (OCP) Module

PCI or EISA Option Modules

CPU Daughter Board

Motherboard

Storage Bay Devices

Power Supply

Speaker

Cooling Fan

Diagram of connectors and components on motherboard

CAUTION:  When servicing the AlphaStation 600A 5/500 system, always remove the AC power cord and follow Digital service procedures.


Opening the Enclosure

To open the AlphaStation 600A 5/500 system enclosure:

1.  Turn off the system and all external peripheral devices.

2.  Unplug the power cord from the wall outlet.

3.  Wait at least 15 seconds, to allow time for the power supply capacitors to fully discharge.

4.  Unlock the left side panel by turning the key counterclockwise to a vertical position.

5.  Insert two fingers into the finger grip on the rear portion of the left side cover.

6.  Slide the left side cover toward the rear of the system unit and remove the cover.

CAUTION:  Always wear a grounded wrist strap when servicing internal components of the AlphaStation 600A 5/500 system.


Left Side Panel


Motherboard Connectors and Components


Removing and Replacing Single Inline Memory Modules (SIMMs)

CAUTION:  Always wear a grounded wrist strap when servicing internal components of the AlphaStation 600A 5/500 system.

Notes

•	Bank 0 must contain a memory option (4 SIMMs - 0, 1, 2, 3).

•	A memory option consists of 4 SIMMs (0, 1, 2, 3).

•	All SIMMs within a bank must be of the same capacity.

To remove and replace a SIMM:

1.	Record the position of the failing SIMM
2.	Turn off the system and disconnect the AC power cord.
3.	Unlock and remove the left side panel.
4.	Locate the failing SIMM on the motherboard.
Memory Layout on Motherboard

WARNING:  Memory and CPU modules have parts that operate at high temperatures. Wait 2 minutes after power is removed before handling these modules.

CAUTION:  Do not use any metalic tools or implements, including pencils, to release SIMM latches. Static discharge can damage the SIMMs.

5.	Remove the failing SIMM by pushing it up gently at a 45 [image] angle and lifting it out of the connector.   Note: SIMMs can only be removed and installed in successive order. For example; to remove SIMM 0 in bank 0, SIMMs 0 and 1 for banks 3, 2, and 1, and SIMM 1 in bank 0 must first be removed.
Removing SIMM from Motherboard

6.	Install the replacement SIMM into the connector at a 45 [image] angle, keeping aware of the orientation of the notch and pushing the SIMM gently down until it seats evenly in the bottom of the connector.
7.	Tilt the SIMM down until the two latches at the ends of the connector lock around the edges of the SIMM.
Installing SIMMs on Motherboard

8.	Replace and secure the left side panel.
9.	Reconnect the AC power cord and turn on the system.


Removing and Replacing a PCI or EISA Option Module

CAUTION:  Always wear a grounded wrist strap when servicing internal components of the AlphaStation 600A 5/500 system.

The AlphaStation 600A Model 5/500 system features three primary PCI slots (slots 11, 12, and 13), four secondary PCI slots (slots 1, 2, 3, and 4), and two EISA slots. You can determine whether an option is peripheral component interconnect (PCI) or extended industry-standard architecture (EISA) by examining the contacts on the module.

To remove an option module:

1.	Turn off the system and disconnect the AC power cord.
2.	Unlock and remove the left side panel.
3.	Disconnect any external cables that are connected to the option module you are removing.
4.	Remove the screw that secures the option module being removed.
5.	Gently pull out on the option module.
To replace an option module:

1.	Insert the replacement option module into the slot and secure it by pressing it firmly into its connector.
2.	Replace and tighten the screw that secures the option module in its slot.
3.	Connect previously removed external cables to the replacement option module.
4.	Replace and secure the left side panel.
5.	Reconnect the AC power cord and turn on the system.
6.	If the module is an EISA-based option and the customer runs the Digital UNIX or OpenVMS operating systems, start the EISA configuration utility using the ecu command from the SRM console prompt. The ecu command allows you to enter such configuration information as interrupt sources and channels, direct memory access (DMA) channels and modes, and so forth.
For information about system-specific options, refer to documentation for both the operating system and the specific option module.


Option Module


Removing and Replacing the CPU Daughter Board

CAUTION:  Always wear a grounded wrist strap when servicing internal components of the AlphaStation 600A 5/500 system.

To remove the CPU daughter board:

1.	Turn off the system and disconnect the AC power cord.
2.	Unlock and remove the left side panel.
3.	Remove the screw that secures the CPU daughter board support bar.
4.	Remove the CPU daughter board support bar.
5.	Gently pull on the CPU daughter board to remove it from the motherboard connector.
To replace the CPU daughter board:

1.	Ensure that the CPU daughter board jumpers on the new CPU daughter board are installed to match the jumpers that were on the old CPU daughter board.
2.	Slide the new CPU daughter board into its slot and secure it by pressing it firmly into its connector.
3.	Reinstall the CPU daughter board support bar.
4	Replace and secure the left side panel.
5.	Reconnect the AC power cord and turn on the system.


Removing and Replacing the Motherboard

CAUTION:  Always wear a grounded wrist strap when servicing internal components of the AlphaStation 600A 5/500 system.

To remove the motherboard:

1.	Turn off the system and disconnect the AC power cord.
2.	Unlock and remove the left side panel.
3.	Remove any option modules.
4.	Remove the CPU daughter board.
5.	Remove the SIMMs from the motherboard.
6.	Disconnect all internal connections and all external connections from the motherboard.
7.	Remove the 15 mounting screws.
8	To clear the external connectors on the upper left side of the motherboard, pull the right side of the motherboard toward the front of the unit first.
To install the motherboard:

1.	Remove the socketed NVRAM chip (position E14) and the NVRAM TOY chip(E78)  from the old motherboard and install them on the new motherboard. Note:  The NVRAM TOY chip contains the os_type environment variable. This environment variable may need to be reset.
2.	Ensure that the motherboard jumpers on the new mother board are installed to match the jumpers that were on the old motherboard.
3.	Reinstall the SIMMs on the new motherboard.
4.	Insert the left side of the motherboard first, so that the external connectors on the upper left side of the board can be positioned properly.
5.	Reinstall the 15 mounting screws.
6.	Reconnect all internal connections and all external connections to the motherboard.
7.	Reinstall all option modules.
8.	Reinstall the CPU daughter board.
9.	Replace and secure the left side panel.
10.	Reconnect the AC power cord and turn on the system.


Removing and Replacing a Storage-Bay Device
Removing and Replacing a Storage Bay Device

The AlphaStation 600A 5/500 system enclosure contains two mass-storage bays--one internal and one external. The internal bay (the drive assembly) can hold three 3.5-inch storage devices. The external bay can hold one slimline 3.5-inch diskette drive and two 5.25-inch half-high removable media devices (typically, tape and CD-ROM).

Procedure for replacing a device in the internal storage bay

Procedure for replacing a device in the external storage bay


Removing and Replacing a Device in the Internal Storage Bay

CAUTION:  Always wear a grounded wrist strap when servicing internal components of the AlphaStation 600A 5/500 system.

The AlphaStation 600A 5/500 system supports three 3.5-inch devices in a drive assembly. To add or replace one of these devices, you must remove the entire drive assembly from the system unit, remove the device from the assembly, and install the new device

To remove the drive assembly from the system unit:

1.	Turn off the system and disconnect the AC power cord.
2.	Unlock and remove the left side panel.
3.	Remove the SCSI and power cables from the devices in the drive assembly.  Note the position of the cables so you can reconnect them to the correct devices later.
4.	Loosen the two mounting screws in the keyhole slots just above the power supply.
5.	Slide the drive assembly toward the rear of the system unit and remove it.
To replace a device in the drive assembly:

1.	Remove the screws on the side and slide the device out of the assembly.
2.	Slide the new device into the assembly and replace and tighten the screws.
To replace the drive assembly in the system unit:

1.	Reconnect the SCSI and power cables to the devices in the drive assembly.
2.	Slide the drive assembly into the system unit until it is positioned properly.  Ensure that the two mounting tabs on the drive assembly engage the mounting finger and slot in the system unit.
3.	Tighten the two mounting screws.
4.	Replace and secure the left side panel.
5.	Reconnect the AC power cord and turn on the system.


Removing and Replacing a Device in the External Storage Bay

CAUTION:  Always wear a grounded wrist strap when servicing internal components of the AlphaStation 600A 5/500 system.

The AlphaStation 600A 5/500 system supports three external drive bay devices--a slimline 3.5-inch diskette drive and two 5.25-inch half-high removable media devices (intended for tape and CD-ROM).

To remove a device from the external drive bay:

1.	Turn off the system and disconnect the AC power cord.
2.	Unlock and remove the left side panel.
3.	Carefully remove the plastic filler panel, pushing it out from the inside using a Phillips screwdriver inserted through one of the screw holes in the side of the drive bay.
4.	Remove the mounting screws for the device you are replacing.
5.	Slide the device toward the front of the system unit and remove it.
To replace a device in the external drive bay:

1.	Check the configuration jumpers of the replacement drive and configure it.  For information about addresses, terminations, and so forth, refer to the drive manual.
2.	Transfer the securing bracket (if used) from the device just removed to the device you are installing by aligning the holes and inserting and tightening the screws.
3.	Slide the device into the system unit and secure it with the mounting screws.
4.	Connect the cables, including power, data, and (if applicable) audio.
5.	Replace and secure the left side panel.
6.	Reconnect the AC power cord and turn on the system.


Removing and Replacing the Speaker

CAUTION:  Always wear a grounded wrist strap when servicing internal components of the AlphaStation 600A 5/500 system.

The internal speaker is located behind the front of the system unit, to the right of the operator control panel (OCP).

To replace the internal speaker:

1.	Remove the internal drive assembly.
2.	Disconnect the speaker cable (red and black, twisted-pair wire) from J23 on the motherboard.
3.	Using a small flat-head screwdriver, push the speaker up until the bottom tab clears.
4.	Grasping the bottom of the speaker, keep it lifted and slide it gently downward toward the rear of the system unit, until it frees itself from its mounting.
5.	Remove the faulty speaker by lifting it out of the enclosure.
6.	Grasping the bottom of the replacement speaker, align it into the mounting and (keeping it lifted) slide it upward until the bottom tab clears.  Observe the cable positions during this step.
7.	After the bottom tab clears, gently snap the speaker into place.
8.	Reinstall the internal drive assembly and reconnect all cables.
9.	Replace and secure the left side panel.
10.	Reconnect the AC power cord and turn on the system.


Removing and Replacing the Power Supply

CAUTION:  Always wear a grounded wrist strap when servicing internal components of the AlphaStation 600A 5/500 system.

The power supply for the AlphaStation 600A 5/500 system is rated at 400 W output.  It features five output voltages and automatic input-voltage selection.

To remove the power supply:

1.	Turn off the system and disconnect the AC power cord.
2.	Unlock and remove the left side panel.
3	Remove the enclosure bezel.
4.	On the front of the enclosure, loosen the two captive (nonremovable) screws located on the top of the power-supply shield.
5.	Swing down the power-supply shield and lift it away.
6.	Disconnect the four DC power connectors from the front of the power supply.
7.	Using a short Phillips screwdriver, remove the two screws on the retaining bracket located on the lower front side of the power supply.
8.	Remove the retaining bracket.
9.	Remove the screw from the rear of the power supply.
10.	Pull the power supply forward about 2 inches and, reaching in from the side of the system unit, unplug the AC power cable located behind the power supply.
11.	Remove the power supply.
To replace the power supply:

1.	Slide the replacement power supply part way into the enclosure.
2.	Reach in from the side of the system unit and reconnect the AC power cable to the rear of the replacement power supply.
3.	Slide the replacement power supply all the way into the enclosure.   Note:  To ensure that the power supply is seated properly, slide it in until it rests snugly against the center brace of the enclosure.  (A screw in the upper right corner at the rear of the power supply secures the supply to the center brace.)
4.	Replace the screw at the rear of the power supply.
5.	Replace the power-supply retaining bracket.
6.	Reconnect the four DC power connectors on the front of the power supply.
7.	Replace the power-supply shield and tighten the captive screws.
8.	Replace the enclosure bezel.
9.	Replace and secure the left side panel.
10.	Reconnect the AC power cord and turn on the system.


Enclosure Bezel


Removing and Replacing the Cooling Fan

CAUTION:  Always wear a grounded wrist strap when servicing internal components of the AlphaStation 600A 5/500 system.

If the cooling fan stops operating or when the system overheats due to airflow blockage the system turns off after a one-second delay.

To remove the cooling fan:

1.	Turn off the system and disconnect the AC power cord.
2.	Unlock and remove the left side panel.
3	Remove the cooling-fan mounting screw.
4.	Disconnect the fan wire at J24 on the motherboard, noting the wire routing.
5.	Remove the cooling fan.
Note:	Before replacing the cooling fan, remove the mounting bracket from the removed cooling fan.  You will reuse the bracket in the replacement procedure.
To replace the cooling fan (after securing the replacement fan into the mounting bracket):

1.	Reroute the fan wire along the removal path.
2.	Insert the tabs on the interior edge of the fan into the slots.
3	Replace the cooling-fan mounting screw.
4.	Connect the fan wire at J24 on the motherboard.
5.	Replace and secure the left side panel.
6.	Reconnect the AC power cord and turn on the system.


Removing and Replacing the Operator Control Panel (OCP) Module

CAUTION:  Always wear a grounded wrist strap when servicing internal components of the AlphaStation 600A 5/500 system.

To remove the OCP module:

1.	Turn off the system and disconnect the AC power cord.
2	Remove the enclosure bezel.
3.	Press on the top tabs of the OCP bezel and pull the OCP bezel toward you.
4.	Remove the OCP module from the OCP bezel.
5.	Remove the OCP cable from the OCP module.
To replace the OCP module:

1.	Connect the OCP cable to the replacement OCP module.
2.	Reattach the replacement OCP module to the OCP bezel.
3.	Insert the OCP bezel onto the enclosure.
4.	Replace and secure the enclosure bezel.
5.	Reconnect the AC power cord and turn on the system.


System Configuration and Setup

Click on one of the topics listed below for more information on the AlphaStation 600A 5/500 system configuration and setup:

System Firmware

Switching Between Interfaces

Digital UNIX and OpenVMS SRM Console Commands

Introduction to the AlphaBIOS Console

Using the AlphaBIOS Menus

AlphaBIOS Firmware Menus

System Bus Options

Motherboard

EISA Bus Options

EISA Configuration Utility

PCI Bus Options

Console Port Configurations


System Firmware

The system firmware currently provides support for the following operating systems:

•	Digital UNIX and OpenVMS Alpha are supported under the SRM command line interface, which can be serial or graphical. The SRM firmware is in compliance with the Alpha System Reference Manual (SRM).

•	Windows NT is supported under the AlphaBIOS console.

The console firmware provides the data structures and callbacks available to booted programs defined in the SRM and AlphaBIOS standards.

SRM Command Line Interface

AlphaBIOS Menu Interface


SRM Command Line Interface

Systems running Digital UNIX or OpenVMS access the SRM firmware through a command line interface (CLI). The CLI is a UNIX style shell that provides a set of commands and operators, as well as a scripting facility. The CLI allows you to configure and test the system, examine and alter system state, and boot the operating system.

The SRM console prompt is >>>.

Several system management tasks can be performed only from the SRM console command line interface:

•	All console test and reporting commands are run from the SRM console.

•	Certain environment variables are changed using the SRM set command. For example:

er*0_protocols

ew*0_mode

ew*0_protocols

ocp_text

pk*0_fast

pk*0_host_id

To run the ECU, you must enter the ecu command. This command will boot the AlphaBIOS firmware and the ECU software.


AlphaBIOS Menu Interface

Systems running Windows NT access the AlphaBIOS console firmware through menus that are used to configure and boot the system, run the EISA Configuration Utility (ECU), adapter configuration utility, or set environment variables.

You must run the EISA Configuration Utility (ECU)  whenever you add, remove, or move an EISA option in your AlphaStation 600A 5/500 system. The ECU is run from diskette. Two diskettes are supplied with your system shipment, one for Digital UNIX and OpenVMS and one for Windows NT.


Switching Between Interfaces

For a few procedures it is necessary to switch from one console interface to the other.

•	The test command and other diagnostic commands are run from the SRM interface.

•	The EISA Configuration Utility (ECU)  is run from AlphaBIOS interface, as are some option-specific configuration utilities.

Switching from SRM to AlphaBIOS

Switching from AlphaBIOS to SRM


Switching from SRM to AlphaBIOS

Two SRM console commands are used to temporarily switch to the AlphaBIOS console:

•	The arc command loads the AlphaBIOS firmware and switches to the AlphaBIOS menu interface.

•	The ecu command loads the AlphaBIOS firmware and then boots the ECU diskette.

For systems that boot the Windows NT operating system, return to the AlphaBIOS console by setting the os_type environment variable to NT, then enter the init command:

>>> set os_type NT

>>> init


Switching from AlphaBIOS to SRM

Switch from the AlphaBIOS console to the SRM console as follows:

1.	From the CMOS Setup menu, press F6 to enter Advanced CMOS setup.

2.	From the Advanced CMOS Setup menu, select Windows NT (AlphaBIOS).

3.	Press F10 to save the change.


Digital UNIX and OpenVMS SRM Console Commands

The following SRM console commands are used to verify system configuration on Digital UNIX and OpenVMS systems:

show config -- Displays the buses on the system and the devices found on those buses.

show device -- Displays the devices and controllers in the system.

show memory -- Displays main memory configuration.

set and show -- Set and display environment variable settings.


show config

The show config command displays all devices found on the system bus, PCI bus, and EISA bus. You can use the information in the display to identify target devices for commands such as boot and test, as well as to verify that the system sees all the devices that are installed.

The configuration display includes the following:

•	Firmware:

The version numbers for the firmware code, PALcode, SROM chip, and CPU are displayed.

•	Memory:

The memory size and configuration for each bank of memory is displayed.

•	Hose 0, Bus 0, PCI:

All controllers on Hose 0, Bus 0 of the primary PCI bus. The logical slot numbers are listed in the left column of the display.

-- Slot 7 = PCI to EISA bridge chip

-- Slot 8 = PCI to PCI bridge chip

-- Slots 11-13 correspond to physical PCI card cage slots on the primary PCI bus:

        Slot 11 = PCI11

        Slot 12 = PCI12

        Slot 13 = PCI13

In the case of storage controllers, the devices off the controller are also displayed.

•	Hose 0, Bus 1, EISA:

All controllers on Hose 0, Bus 1 of the EISA bus. The logical slot numbers in the left column of the display correspond to physical EISA card cage slots (1 and 2).

In the case of storage controllers, the devices off the controller are also displayed.

•	Hose 0, Bus 2, PCI:

All controllers on Hose 0, Bus 2 of the secondary PCI bus. The logical slot numbers are listed in the left column of the display.

-- Slot 0 = SCSI controller on the system backplane, along with storage drives on the bus.

-- Slots 1-4 correspond to physical PCI card cage slots on the secondary PCI bus:

       Slot 1 = PCI1

       Slot 2 = PCI2

       Slot 3 = PCI3

       Slot 4 = PCI4

In the case of storage controllers, the devices off the controller are also displayed.

•	Hose 0, Bus 3, PCI:

If PCI options contain a PCI-to-PCI bridge, such as the DECchip 21050-AA in the secondary PCI bus, slot 4, in the show configuration example, the additional bus is represented in the display.

For each option that contains a PCI-to-PCI bridge, the bus number increments by 1, and the logical numbers start anew at 0.

For more information on device names, refer to the show device command. Refer to the motherboard layout for the location of physical slots.

Synopsis:

show config

Example:

>>> show config

                           AlphaStation 600A 5/500

Firmware

SRM Console:    X4.5-4322

ARC Console:    5.12

PALcode:        VMS PALcode V1.18-2, OSF PALcode V1.21-4

Serial Rom:     T1.1

Processor

DECchip (tm) 21164-5    500MHz

Memory

       64 Meg of System Memory

       Bank 0 = 64 Mbytes(16 MB Per Simm) Starting at 0x00000000

       Bank 1 = No Memory Detected

       Bank 2 = No Memory Detected

       Bank 3 = No Memory Detected

Slot   Option               Hose 0, Bus 0, PCI

  7    Intel 82375EB                          Bridge to Bus 1, EISA

  8    DECchip 21050-AA                       Bridge to Bus 2, PCI

  11   DECchip 21040-AA     wb0.0.0.11.0      08-00-2B-E5-CC-B1

Slot   Option              Hose 0, Bus 1, EISA

  1    DE422                era0.0.0.1001.0   08-00-2B-39-4F-4E

Slot   Option              Hose 0, Bus 2, PCI

  0    QLogic ISP1020       pka0.7.0.2000.0   SCSI Bus ID 7

                            dka0.0.0.2000.0   RZ26L

                            dka400.4.0.2000.0 RRD43

  4    DECchip 21050-AA                       Bridge to Bus 3, PCI

Slot   Option              Hose 0, Bus 3, PCI

  0    DECchip 21040-AA     ewa0.0.0.3000.0   08-00-2B-E2-31-68

  2    QLogic ISP1020       pkb0.7.0.3002.0   SCSI Bus ID 7

  3    QLogic ISP1020       pkc0.7.0.3003.0   SCSI Bus ID 7

>>>

Note:  The onboard SCSI controller (Qlogic 1020A) is always device pka.


show device

The show device command displays the devices and controllers in the system. The device name convention is shown below.

Synopsis:

show device [device_name]

Argument:

[device_ name]	The device name or device abbreviation. When abbreviations or wildcards are used, all devices that match the type are displayed.
Example:

>>> show device

                 1                             2                                         3              4

dka400.4.0.6.0       DKA400                RRD43  2893

dva0.0.0.0.1         DVA0

era0.0.0.2.0         ERA0         08-00-2B-BC-93-7A

pka0.7.0.6.0         PKA0            SCSI Bus ID 7

>>>

1  Console device name

2  Node name (alphanumeric, up to 6 characters)

3  Device type

4  Firmware version (if known)


show memory

The show memory command displays information for each bank of memory in the system.

Synopsis:

show memory

Example:

>>> show memory

     48 Meg of System Memory

     Bank 0 = 16 Mbytes(4 MB Per Simm) Starting at 0x00000000

     Bank 1 = 16 Mbytes(4 MB Per Simm) Starting at 0x01000000

     Bank 2 = 16 Mbytes(4 MB Per Simm) Starting at 0x02000000

     Bank 3 = No Memory Detected

>>>


set and show

The environment variables described in the following table are typically set when you are configuring a system.

Synopsis:

set [-default] [-integer] -[string] envar value

Note:  Whenever you use the set command to reset an environment variable, you must initialize the system to put the new setting into effect. You initialize the system by entering the init command or pressing the Reset button.

show envar

Arguments:

envar	The name of the environment variable to be modified.
value	The value that is assigned to the environment variable. This may be an ASCII string.
Options:

-default	Restores variable to its default value.
-integer	Creates variable as an integer.
-string	Creates variable as a string (default).
Examples:

>>> set bootdef_dev eza0

>>> show bootdef_dev

eza0

>>> show auto_action

boot

>>> set boot_osflags 0,1

>>>

Variable	Attributes	Function
auto_action	NV, W	The action the console should take following an error halt or power failure. Defined values are: BOOT-Attempt bootstrap. HALT-Halt, enter console I/O mode. RESTART-Attempt restart. If restart fails, try boot. No other values are accepted. Other values result in an error message, and the variable remains unchanged.
bootdef_dev	NV	The device or device list from which booting is to be attempted, when no path is specified on the command line. Set at factory to disk with Factory Installed Software; otherwise NULL.
boot_file	NV, W	The default file name used for the primary bootstrap when no file name is specified by the boot command. The default value when the system is shipped is NULL.
boot_osflags	NV, W	Default additional parameters to be passed to system software during booting if none are specified by the boot command. OpenVMS: On the OpenVMS Alpha operating system, these additional parameters are the root number and boot flags. The default value when the system is shipped is NULL. Digital UNIX: The following parameters are used with the Digital UNIX operating system: a     Autoboot. Boots /vmunix from bootdef_dev, goes to multiuser mode. Use this for a system that should come up automatically after a power failure. s     Stop in single-user mode. Boots /vmunix to single-user mode and stops at the # (root) prompt. i     Interactive boot. Requests the name of the image to boot from the specified boot device. Other flags, such as -kdebug (to enable the kernel debugger), may be entered using this option. D     Full dump; implies "s" as well. By default, if Digital UNIX crashes, it completes a partial memory dump. Specifying "D" forces a full dump at system crash. Common settings are a, autoboot; and Da, autoboot and create full dumps if the system crashes.
bus_probe_algorithm	NV	Specifies a bus probe algorithm for the system. OLD-Systems running OpenVMS V6.1 or earlier must set the bus probe algorithm to old-Failure to do so could result in bugcheck errors when booting from an EISA device. NEW-Systems running Digital UNIX V3.0B or later or OpenVMS V6.2 or later should be set to new. This setting improves the bus sizing and configuration for Digital UNIX systems. Not applicable for systems running Windows NT.
com1_baud or com2_baud	NV, W	Sets the baud rate of the COM1 or COM2 port. The default baud rate is 9600. Baud rate values are 300, 600, 1200, 2400, 4800, 9600, and 19200.
com1_flow, com2_flow	NV, W	The com1_flow and com2_flow environment variables indicate the flow control on the serial ports. Defined values are: NONE-No flow control. SOFTWARE-Use XON/XOFF (default value). HARDWARE-Use modem signals CTS/RTS. BOTH-Use SOFTWARE and HARDWARE
com1_modem, com2_modem	NV, W	The com1_modem and com2_modem environment variables are used by the operating system to determine if a modem is present. ON-Modem is present. OFF-Modem is not present (default value).
console	NV	Sets the device on which power-up output is displayed. GRAPHICS-Sets the power-up output to be displayed at a graphics terminal or device connected to the VGA module at the rear of the system. SERIAL-Sets the power-up output to be displayed on the device that is connected to the COM1 port at the rear of the system.
ew*0_mode	NV	Sets the Ethernet controller to the Ethernet device type. "aui"-Sets the default Ethernet device to AUI or thinwire. "twisted"-Sets the default Ethernet device to 10Base-T  (twisted-pair). "auto"-Reads the device connected to the Ethernet port and sets the default to the appropriate Ethernet device type.
er*0_protocols, ew*0_protocols	NV	Determines which network protocols are enabled for booting and other functions. "mop"-Sets the network protocol to MOP: the setting typically used for systems using the OpenVMS operating system. "bootp"-Sets the network protocol to bootp: the setting typically used for systems using the Digital UNIX operating system. "bootp,mop"-When the settings are used in a list, the mop protocol is attempted first, followed by bootp.
os_type	NV	Sets the default operating system. "vms" or "unix"-Sets system to boot the SRM firmware. "nt"-Sets system to boot the AlphaBIOS firmware.
pci_parity	NV	Disable or enable parity checking on the PCI bus. ON-PCI parity enabled. OFF-PCI parity disabled. Some PCI devices do not implement PCI parity checking, and some have a parity-generating scheme in which the parity is sometimes incorrect or is not fully compliant with the PCI specification. In such cases, the device functions properly as long as parity is not checked. The default value is ON-PCI parity enabled. Note:  If you disable PCI parity, no parity checking is implemented for any PCI device, even those devices in full compliance with the PCI specification.
pk*0_fast	NV	Enables Fast SCSI devices on a SCSI controller to perform in standard or fast mode. 0-Sets the default speed for devices on the controller to standard SCSI. If a controller is set to standard SCSI mode, both standard and Fast SCSI devices will perform in standard mode. 1-Sets the default speed for devices on the controller to Fast SCSI mode. Devices on a controller that connect to both standard and Fast SCSI devices will automatically perform at the appropriate rate for the device, either fast or standard mode.
pk*0_host_id	NV	Sets the controller host bus node ID to a value between 0 and 7. 0 to 7-Assigns bus node ID for specified host adapter.
pk*0_soft_term	NV	Enables or disables SCSI terminators. This environment variable applies to systems using the Qlogic ISP1020 SCSI controller. The QLogic ISP1020 SCSI controller implements the 16-bit wide SCSI bus. The QLogic module has two terminators, one for the 8 low bits and one for the high 8 bits. There are five possible values: off-Turns off both low 8 bits and high 8 bits. low-Turns on low 8 bits and turns off high 8 bits. high-Turns on high 8 bits and turns of low 8 bits. on-Turns on both low 8 bits and high 8 bits. diff-Places the bus in differential mode.
tga_sync_green	NV	Sets the location of the SYNC signal generated by the ZLXp-E PCI graphics accelerator (PBXGA). This environment variable must be set correctly so that the graphics monitor will synchronize. The parameter is a bit mask, where the least significant bit (LSB) sets the vertical SYNC for the first graphics card found, the second for the second found, and so on. The command set tga_sync_green 00 sets all graphics cards to synchronize on a separate vertical SYNC line, as required by some monitors. See the monitor documentation for all other information. ff-Synchronizes the graphics monitor on systems that do not use a ZLXp-E PCI graphics accelerator (default setting). 00-Synchronizes the graphics monitor on systems with a ZLXp-E PCI graphics accelerator.
tt_allow_login	NV	Enables or disables login to the SRM console firmware on alternative console ports. 0-Disables login on alternative console ports. 1-Enables login on alternative console ports (default setting). If the console output device is set to "serial", set tt_allow_login 1 allows you to log in on the primary COM1 port, or alternate COM2 port, or the graphics monitor. If the console output device is set to "graphics", set tt_allow_login 1 allows you to log in through either the COM1 or COM2 console port
Key to variable attributes:

NV -- Nonvolatile. The last value saved by system software or set by console commands is preserved across system initializations, cold bootstraps, and long power outages.

W -- Warm nonvolatile. The last value set by system software is preserved across warm bootstraps and restarts.

Note:  Whenever you use the set command to reset an environment variable, you must initialize the system to put the new setting into effect. You initialize the system by entering the init command or pressing the Reset button.


Introduction to the AlphaBIOS Console

This topic describes the AlphaBIOS interface and includes the following topics:

The AlphaBIOS Console

Windows NT System Start-Up

The Firmware Menus

Help in Navigating AlphaBIOS

Primary Operating System and the Auto Start Option


The AlphaBIOS Console

AlphaBIOS is a program used to initialize and set up the I/O system of the computer, which includes the PCI bus and connected devices such as SCSI disk controllers, the video display, the diskette drive, and the keyboard. The AlphaBIOS program instructions are contained within computer chips called flash ROMs (read-only memory) that are located on the motherboard. The chips can be electronically reprogrammed, allowing you to upgrade the AlphaBIOS firmware without removing and installing chips.

AlphaBIOS provides a menu-based interface to the console subsystem that supports the Microsoft Windows NT operating system for hardware based on the Alpha processor. The console subsystem contains special software, called firmware, that interacts directly with the hardware components and facilitates interaction between the system hardware and the operating system.

Windows NT Users

Users of the Windows NT operating system can use the information in this and the following topics along with their system Owners Guide to configure, start, update, and troubleshoot the  AlphaStation 600A 5/500 system.

OpenVMS Alpha and Digital UNIX Users

Users of the OpenVMS Alpha and Digital UNIX operating systems need to use the AlphaBIOS interface only to run the EISA Configuration Utility (ECU) or other option-specific configuration utilities. To switch from the SRM console to the AlphaBIOS console on your system, type either of the following commands at the SRM prompt: arc or ecu. Either of these commands will access the AlphaBIOS Boot menu. For information on running the ECU, refer to running a configuration utility.

ARC vs AlphaBIOS

The AlphaBIOS firmware interface replaces the ARC firmware interface. Throughout these topics you will find notes that indicate where the AlphaBIOS interface differs significantly from the previous ARC interface.

Using a Serial Line

AlphaBIOS can be run from the graphics console or from a serial line. If you use the serial line, refer to the following table for serial line equivalents to graphics line keyboard commands.

Graphics Line Commands	Serial Line Commands
F1	CTRL +A
F2	CTRL +B
F3	CTRL +C
F4	CTRL +D
F5	CTRL +E
F6	CTRL +F
F7	CTRL +P
F8	CTRL +R
F9	CTRL +T
F10	CTRL +U
Insert	CTRL +V
Delete	CTRL +W
Backspace	CTRL +H
ESC	CTRL +[


Windows NT System Start-Up

For systems using the Windows NT operating system, AlphaBIOS initializes the video and keyboard devices first. Thus, if AlphaBIOS does not start when you turn on your computer, check first to see that the keyboard is plugged in and working and that the video card and monitor are properly connected and working. After the video and keyboard are initialized, AlphaBIOS displays a windowed, graphical-style user interface (UI), where progress is displayed as initialization continues.

Next, a memory test verifies that the memory is fully functioning. While the memory test runs, it shows each megabyte (MB) of memory tested. If you do not want to test memory during initialization, you can disable the test while it is running by pressing the space bar, or use the CMOS Setup menu to disable it.

After memory is tested, AlphaBIOS detects and initializes SCSI disk controllers connected to the computer. As each controller is detected, AlphaBIOS probes its SCSI bus and reports each of the SCSI devices detected.

Finally, after the SCSI initialization is complete, AlphaBIOS leaves the initialization window and displays the Boot menu, shown below. Whenever you turn on or reset the system, the Boot menu is displayed.

The Boot menu lists each of the operating systems that have been set up on your computer. From the boot menu, you can choose which of the operating systems you want to boot, or you can enter the AlphaBIOS Setup menu.


The Firmware Menus

By pressing F2 in the Boot menu, you can access the AlphaBIOS Setup menu, shown below.

From the Setup menu you can access other menus to perform the tasks listed in the following table.

Task	Menu
Enable the Auto Start option	CMOS Setup (Standard)
Set date and time	CMOS Setup (Standard)
Configure the diskette drive and keyboard	CMOS Setup (Standard)
Test memory at system start-up	CMOS Setup (Advanced)
Set PCI parity	CMOS Setup (Advanced)
Set password protection	CMOS Setup (Advanced)
Select a console (AlphaBIOS or SRM)	CMOS Setup (Advanced)
Run a configuration utility	Utilities
Set up the hard disk	Hard Disk Setup
Display the system configuration	Display System Configuration
Upgrade the AlphaBIOS firmware	Upgrade AlphaBIOS
Verify and change operating system selections	Utilities


Help in Navigating AlphaBIOS

Two levels of keyboard help are available for AlphaBIOS. To reach the first level, press F1 once from the CMOS Setup menu. This Help display, shown below, provides explanations of the keystrokes available for the part of the AlphaBIOS interface currently displayed.

The second level of keyboard help, reached by pressing F1 twice from the CMOS Setup menu, shows explanations of the keystrokes available for navigating the interface throughout the AlphaBIOS firmware interface. The following figure shows an example of the second Help display.


Primary Operating System and the Auto Start Option

Alpha systems can have multiple versions of Windows NT installed at the same time. This feature is useful, for example, when testing application compatibility across different versions of Windows NT.

Each time you install a separate version of Windows NT, a new operating system selection is created. Although you can start any of the installed versions of Windows NT, one of the installed versions must be the primary operating system. The version you select as the primary operating system is the one that automatically starts if the Auto Start option is enabled in AlphaBIOS.

The following figure shows an example of a primary operating system selection as it appears in the Boot menu. Notice that the primary operating system is listed first on the boot display.

The primary operating system starts automatically if the Auto Start option is enabled in the CMOS Setup menu, as shown below.

The primary operating system can be selected in the Operating System Selection Setup menu, shown below.

Note:  ARC vs AlphaBIOS

With ARC firmware, the group of values associated with a particular Windows NT installation are called a boot selection, and information is accessed from separate menus using the Manage Boot Selections menu.

With AlphaBIOS, these values are called an operating system selection, and information is accessed through the Operating System Selection Setup menu. Alternative choices for values such as disk and partition numbers are available from drop-down list boxes, and only valid values are displayed. When creating new selections, you can use an existing selection as a template.


Using the AlphaBIOS Menus

This section introduces the AlphaBIOS menu displays and explains how to perform common tasks needed to get up and running.

Topics covered in this section include:

Preparing to Install the Operating System

System Setup Tasks

Displaying Your Configuration

Running a Configuration Utility

Setting Up Password Protection

Upgrading AlphaBIOS

Troubleshooting Suggestions


Preparing to Install the Operating System

Note:  For Systems with Pre-installed Windows NT Software

If you have a system with Windows NT installed at the factory, Windows NT setup will start automatically the first time you turn on your system. If your system does not have Windows NT pre-installed, you must have a CD-ROM drive attached to your system to install Windows NT. Refer to your operating system documentation to install your operating system.

To prepare your system for a first-time installation of Windows NT from CD-ROM, follow these steps:

Note:  Steps 1 and 2 in the following procedure are necessary only when you are first setting up your system. On subsequent installations and upgrades, begin at step 3.

1.	From the AlphaBIOS Setup menu, select the CMOS Setup menu and press Enter. Set the system date and time.

2.	Return to the main AlphaBIOS Setup menu, select Hard Disk Setup, and press Enter.

You can easily set up the first hard disk in your system (disk 0) with the recommended default partition arrangement by performing an express setup.  Note, however, that express setup does not format the large partition with NTFS. You will have the opportunity to do this during the Windows NT installation.

Note:  The hard disk with the lowest SCSI ID number is seen as disk 0 by AlphaBIOS.

Caution:  If you have any needed information on your disk, be sure to back up your disk before using express setup.

To perform an express hard-disk setup, follow these steps:

a.   From the AlphaBIOS Setup menu, select Hard Disk Setup, and press Enter.

b.   Press F7 to enter express setup.

c.   Press F10 to continue with the setup.

Note:  ARC vs AlphaBIOS

With ARC firmware, initial hard-disk partitioning and formatting was accomplished using a utility called ARCINST.EXE, distributed on the Windows NT CD-ROM. This utility was run from a command line. With AlphaBIOS, hard-disk setup is integrated into the menu-based interface, and path name descriptions correspond to those used by the Windows NT Disk Administrator.  For example: ARC Path Name = scsi(0)disk(0)rdisk(0)partition(1); AlphaBIOS Path Name  = Disk 0, Partition 1.

3.	Put the Windows NT CD into the CD-ROM drive.

4.	Start AlphaBIOS Setup, select Install Windows NT, and press Enter.

To complete the installation, refer to your operating system documentation.

Manually Setting Up the Hard Disk

For information on manually managing hard disks, refer to the  Hard Disk Setup Menu.

Caution:   Unlike other parts of AlphaBIOS setup, hard disk setup makes changes to your disk configuration as you enter them. Use care when changing your hard-disk arrangement, because unintended data loss can occur.


System Setup Tasks

The CMOS Setup menu is used for a variety of system settings and is divided into two modes, standard and advanced. The following table lists the tasks that can be performed in the two CMOS Setup modes:

Standard Mode	Advanced Mode
Auto Start	Memory test at start-up
Date and time	PCI parity
Diskette configuration	Password protection
Keyboard configuration	Console selection
To enter standard CMOS setup mode:

1.	From the AlphaBIOS Setup menu, select CMOS Setup, and press Enter.

To enter advanced CMOS setup mode:

1.	From the AlphaBIOS Setup menu, select CMOS Setup, and press Enter.

2.	In the CMOS Setup menu, press F6.

Note:  ARC vs AlphaBIOS

With ARC firmware, a number of settings stored in CMOS and NVRAM are set using several separate ARC firmware selections. With AlphaBIOS, these settings are integrated into the CMOS Setup program.


Displaying Your System Configuration

You can use AlphaBIOS to display your system configuration in an easy-to-read format organized by category: system board, memory, hard disk, PCI options, SCSI devices, and peripherals.

To display your system configuration, follow these steps and refer to the following figure:

1.	From the AlphaBIOS Setup menu, select Display System Configuration, and press Enter.

2.	In the Display System Configuration menu, use the Arrow or Tab keys to select the configuration category you want to see.

Note:  ARC vs AlphaBIOS

The system configuration display in ARC firmware provides general information about system setup. In contrast, the system configuration display in AlphaBIOS displays detailed information categorized by major subsystem. In addition, for many of the elements listed, you can select the element and obtain additional detailed information.

Support for multiple languages, which was recently added to ARC firmware, is not currently a feature of AlphaBIOS.

For detailed information on the Display System Configuration menus, refer to the Display System Configuration Menu .


Running a Configuration Utility

If you change your system configurationfor example, by adding a new EISA adapter, you will have to run an EISA configuration utility. As you modify your system, you might be required to run other types of configuration utilities as well. Configuration utilities (also called maintenance programs) are run directly from the AlphaBIOS Utility menu.

Users of OpenVMS Alpha or Digital UNIX:  Users of the OpenVMS Alpha and Digital UNIX operating systems need to switch from the SRM console to the AlphaBIOS console to run a configuration utility. To switch, type either of the following commands at the SRM console prompt:  arc or ecu. This command will access the AlphaBIOS Boot menu. To access the Setup menu from the Boot menu, press F2.

To run a configuration utility:

1.	From the AlphaBIOS Setup menu, select Utilities.  From the submenu that appears, select Run Maintenance Program, and press Enter.

2.	In the Run Maintenance Program dialog box, type the name of the program to be run in the Program Name field. Then Tab to the Location list box, and select the hard-disk partition, diskette, or CD-ROM drive from which to run the program.

3.	Press Enter to execute the program.

Note:  If you are running a utility from a diskette, you can simply type the utilitys name into the Program Name field, and press Enter. The diskette drive is the default selection in the Location field. Use Alt+Down arrow when a list box is selected, to open the list.


Setting Up Password Protection

Password protection provides two levels of security for your system: setup protection and startup protection. When system setup protection is enabled, a password is required to start AlphaBIOS Setup. When startup password protection is enabled, a password is required before the system initializes.

Caution:  Take care to remember your password.  To clear the password requires replacement of a motherboard component.

Startup password protection provides more comprehensive protection than setup password protection because the system cannot be used at all until the correct password is entered.

To enable password protection:

1.	From the AlphaBIOS Setup menu, select CMOS Setup, and press Enter.

2.	In the CMOS Setup menu, press F6 to enter advanced CMOS setup mode.

3.	In the Advanced CMOS Setup menu, shown below, select AlphaBIOS Password Option.

Use the Arrow Keys to select the type of protection you want. An explanatory dialog box appears. Read the dialog box and press Enter to continue.

4.	Enter your password in the Enter New Password dialog box, then press Enter.

5.	Enter your password in the Confirm New Password dialog box, then press Enter.

6.	Press F10 to save your changes.

Note:  If you want to change your password, simply set up your password again.


Upgrading AlphaBIOS

As new versions of Windows NT are released, it might be necessary to upgrade AlphaBIOS to the latest version. As improvements are made to AlphaBIOS, you may want to upgrade to take advantage of new AlphaBIOS features.

To upgrade from an earlier version of AlphaBIOS, follow these steps:

1.	Insert the diskette or CD-ROM containing the AlphaBIOS upgrade.

2.	If you are not already running AlphaBIOS Setup, access the AlphaBIOS Setup menu by restarting your system and pressing F2 when the Boot menu is displayed.

3.	From the AlphaBIOS Setup menu, select Upgrade AlphaBIOS and press Enter. When you choose this option, the existing AlphaBIOS searches for an executable AlphaBIOS update file, first on CD-ROM, and then on diskette. Once the update file has been found, it executes it, and the AlphaBIOS is upgraded.

4.	After the upgrade is complete, the system either resets automatically or prompts you to reset the system.

Upgrading from the SRM Console

To upgrade using the SRM console, follow these steps:

1.	Insert the diskette or CD-ROM containing the AlphaBIOS upgrade.

2.	At the console prompt (>>>) type the following command:

>>> boot dva0

The system will display this menu:

Display

Exit

List

Update

Verify

UPD>

3.	At the UPD> prompt, type the appropriate update command. To update AlphaBIOS only:

UPD > update arc

To update both SRM and AlphaBIOS:

UPD> update

To update SRM only:

UPD> update srm

4.	When the update is complete, type exit to return to the console prompt.


Troubleshooting Suggestions

The following table describes symptoms of hard disk problems and suggests possible causes and solutions.

Error message	Possible Cause	Corrective Action
Internal error occurred	Incompatible or failed disk cables.	Try another cable that is known to be good.
	Disk controller not configured.	Check your hard-disk controller documentation to see if you need to run a configuration utility to set up your hard-disk.
	Disk controller malfunction.	Test controller functioning using the controllers diagnostic utility. If an error is found, contact your service representative for a replacement.
	Improper SCSI termination.	Check to see that terminating resistor packs are removed from all drives except the controller itself and the last drive connected to it.
No hard drives were found connected to your computer	No hard disk installed.	Install hard disk.
	Cable not connected to either the disk or controller.	Check the cable connections to ensure that cable connectors are fully seated.
	No power to drive.	Check cable connections. If problem persists, try connecting the drive to a different power connector.
	Disk drive malfunction.	Try replacing the drive with a drive known to be good. If problem persists, hard drive is defective. Contact your service representative.
Perform an express disk setup?	Hard disk 0 does not have any partitions defined.	Perform an express disk setup to automatically create default disk partition arrangement on hard disk 0.


AlphaBIOS Firmware Menus

This section presents detailed explanations of the elements found in each of the AlphaBIOS menus. The following topics are covered:

Hard Disk Setup Menu

Operating System Selection Setup Menu

Display System Configuration Menu

Run Maintenance Program Menu

CMOS Setup Menu


Hard Disk Setup Menu

This section details all of the information presented on the AlphaBIOS Hard Disk Setup menu. An example is shown.

1. Disk

The Disk line describes the physical characteristics of the hard disk. This information is presented for informational purposes and is not selectable or editable.

For detailed information on the fields presented on the Disk line, refer to the Hard Disk Configuration Menu,.

2. Partitions

The Partition line(s) describes how space on the drive is allocated to logical drives.

Fields on the partition line include:

Partition number

Within a single drive, partition numbers are assigned in sequential order: 1, 2, 3, and so on. The partitions populate the drive from the innermost cylinders to the outermost cylinders. If you have a large hard disk (over 800 MB) and plan to use the FAT file system, it is a good idea to break the disk into several smaller partitions because the FAT file system uses disk space more efficiently at smaller partition sizes. This is not a concern for the NTFS file system, however, as it uses disk space very efficiently at all partition sizes.

Partition size

The partition size is the raw (unformatted) storage capacity of the partition. Actual storage space will differ based on the file system with which the partition is formatted.

Partition format

The file system (if any) used on a partition. This field will display FAT, NTFS, or unknown (if the partition is unformatted).

3. Disk Setup Options

Insert partition

Use this option to create new partitions. Before creating a new partition, be sure to select an unpartitioned space. Pressing the Insert key while an already-partitioned space is selected causes an informational error to be displayed.

Delete partition

Use this option to delete existing partitions. Before deleting a partition, make sure any data that you wish to save on the partition has been backed up. Deleting a partition deletes all data on the partition being deleted, but leaves the rest of the disk unaffected. Pressing the Delete key while an unpartitioned space is selected causes an informational error to be displayed.

Format partition

By pressing F6, you can use this option to format a partitioned space with the FAT file system.

Express setup

By pressing F7, you can use this option to create the default recommended partition arrangement for Windows NT on your system.

Exit

Press the Escape key to return to the AlphaBIOS Setup menu.


Operating System Selection Setup Menu

This section details the information presented on the AlphaBIOS Operation System Selection Setup Menu. An example is shown.

The process of setting up your operating system selections is somewhat like using an editor. You can make all the changes you want to your operating system selections, and then either save your changes or exit without saving your changes.

1. Boot Name

Each boot name is associated with an operating system selection. Windows NT Setup automatically creates a boot name each time you install the operating system. Because the boot name is only a name, you can modify the boot name at any time without affecting the rest of the operating system selection. Note that the boot name must have at least one character.

2. Primary Operating System

The primary operating system is the OS that appears first on the AlphaBIOS boot menu. It is also the version of the OS that automatically starts if Auto Start is selected. You can make any of the operating system selections the primary operating system.

3. Boot File

The Boot File line describes the disk, partition, path, and name of the file that AlphaBIOS passes control to during the process of starting the operating system. This setting is created along with the operating system selection during Windows NT Setup, and it is usually not modified by the user. However, this setting can be modified if necessary. For example, a developer testing different versions of OSLOADER.EXE can store the different versions in different locations and modify this line to start the operating system with the different versions as needed.

During Operating System Selection Setup, the disk and partition for the location of the boot file can be selected from a list of choices presented in a list box. To open a list of values for the field, press the Alt and Down Arrow keys together. When you select a boot file location and name, AlphaBIOS searches for the specified program on the specified partition. If the search fails, a warning appears, saying that the file does not exist. You are given the choice to continue with the changes anyway or to cancel the operation and fix the problem.

Note that because the boot file must be located in a FAT partition, only FAT partitions are available as the boot partition within the list box.

4. OS Path

The OS Path line describes the disk, partition, and path to the operating system root directory for an operating system selection.

During Operating System Selection Setup, the disk and partition for the location of the boot file can be selected from a list of choices presented in a list box. To open a list of possible values for the field, press the Alt and Down Arrow keys at the same time. When you select or enter an OS path, AlphaBIOS searches for the directory. If the search fails, a warning appears, saying that the directory does not exist. You are given the choice to continue with the changes anyway or to cancel the operation and fix the problem.

5. OS Options

The OS Options line lists the startup parameters passed to the operating system for an operating system selection. One example of a startup parameter is whether to start the operating system in debug mode. By default, Windows NT does not add any entries to this field. This field can be modified.

6. OS Selection Setup Options

You can use the options listed at the bottom of the menu to edit operating system selections. When you edit an OS selection, the fields of the OS Selection are validated when you exit the OS selection setup menu. Depending on the option you choose, one of the following dialog boxes will appear.

New OS Selection.  Pressing the Insert key displays the Insert New Operating System Selection dialog box, with default values for the new OS selection already filled in. You can change these values as necessary.

Delete OS Selection.  Pressing the Delete key tags the currently selected OS selection for deletion. Although the OS selection is removed from the menu, it is not actually deleted until you save your changes.

You can also delete all of your OS selections at once by pressing the Control and Delete keys at the same time while in the Operating System Selection Setup menu.

Note:  If you delete all of your OS selections, a dialog box appears informing you that no OS selections exist and offering three options. You can create a new OS selection, exit without saving changes, or exit and save changes.

Edit OS Selection.  You can edit all of the values of an OS selection by selecting the OS selection to edit and pressing F6. A dialog box appears with current information. You can then edit all of the OS selection fields.

Copy OS Selection.  You can make it easy to create a new OS selection by using an existing OS selection as a template. To do this, select the OS selection you want to make a copy of and press F7 to make a copy of it. A dialog box appears with the values of the OS selection you selected. You can then edit all of the OS selection fields. Note that if you do not make any changes, a duplicate copy of the OS selection you copied is made.

Validate OS Selection.  Pressing F9 in the Operating System Selection Setup menu allows you to validate the fields in the currently selected OS selection. The validation routine checks that the OS loader file and OS directory fields contain valid paths, and that the OSLOADER.EXE file exists in the directory specified. At the end of the validation, a dialog box appears describing the results of the validation. If there is an error in an OS selection, the validation routine displays a dialog box describing the component of the OS selection that is in error. At this point you can choose to edit the OS selection to correct the error, or delete the OS selection altogether.

You can also validate all of the OS selections at once by pressing the Control and F9 keys at the same time. All OS selections are validated in the order they are listed on menu.

Primary Operating System. You can set any of the OS selections to be the primary operating system by selecting the OS selection and pressing F8. When you make an OS selection primary, it is displayed first on the Operating System Selection Setup menu and the text Primary Operating System appears next to the OS selection. In addition, the primary operating system is displayed first on the AlphaBIOS boot menu and is automatically started if Auto Start is enabled.

Exit. Pressing the Escape key returns you to the AlphaBIOS Setup menu.


Display System Configuration Menu

The Display System Configuration Menu allows the following configurations to be displayed:

Systemboard Configuration Menu

Hard Disk Configuration Menu

PCI Configuration Menu

EISA Configuration Menu

SCSI Configuration Menu

Memory Configuration Menu

Integrated Peripherals Menu


Systemboard Configuration Menu

Information about the system board configuration is presented when you select Systemboard Configuration and press Enter. An example is shown.

1. System Type

The System Type field shows the system family to which the system board in your system belongs. Alpha system families are defined by the basic architecture of the system board. Individual system models within the family can have different processors, run at different speeds, have different options, etc.

2. Processor

The Processor field shows the model and revision of processor installed on your system boardfor example, 21064. Revision level information can be useful in troubleshooting problems with technical support personnel.

3. Speed

The Speed field shows the speed at which the processor runs internally.

4. Cache

The Cache field shows the amount, in kilobytes, of static RAM cache memory installed. Cache memory is used to speed system performance by acting as an intermediary between the processor and the systems main memory, which uses slower dynamic RAM.

5. Memory

The Memory field shows the amount, in megabytes, of main memory installed.

6. AlphaBIOS Version

The AlphaBIOS Version field shows the version of AlphaBIOS currently running on your system. The AlphaBIOS Version field has three parts: the major version number, minor version number, and build date. The major version number signifies the overall level of the BIOS; that is, it represents major functionality. The minor version number signifies minor enhancements that have been made since the last major revision. The build date is the date and time the BIOS was compiled.


Hard Disk Configuration Menu

Information about the hard disk configuration is presented when you select Hard Disk Configuration and press Enter. An example is shown.

Fields in the hard disk configuration menu include:

1. Physical disk ID.

The physical disk ID is based on the SCSI ID. The disk with the lowest SCSI ID is disk 0; the disk with the next lowest SCSI ID is disk 1, and so on.

2. Controller.

The controller is the brand and model of SCSI chip used on the SCSI controller.

3. Controller number.

The controller number is based on how many SCSI controllers of a particular type are installed in the system. The first controller of a type is always numbered 0.  For example, if two NCR 810 controllers and one QLogic controller existed in a system, they would be numbered as follows:

First NCR 810 = NCR810 #0, Second NCR 810 = NCR 810 #1, QLogic = QLogic #0

4. SCSI ID number.

The SCSI ID number is a unique number you assign to each SCSI device installed in the system.  This is usually done via jumpers or a thumb wheel attached to the drive housing or by jumpers supplied on the StorageWorks backplane.

5. Size.

This is the raw capacity of the drive. Formatting the drive with different file systemsfor example, FAT and NTFSmay result in different usable sizes because of the differences in how storage is managed under those file systems.

6. Drive manufacturer ID.

This line identifies the type of drive and the manufacturer, as well as the firmware revision of the drive.


PCI Configuration Menu

Information about all the PCI devices in your system is presented when you select PCI Configuration and press Enter. An example is shown.

1. Device Name

This is the name and model of the device as recorded in the devices firmware.

2. Device Type

The device type lists the function of the device in the system.

3. Physical Slot

The physical slot lists the actual PCI slot number to which the device is attached. Refer to your system manual for the physical location of PCI slots on the motherboard.

4. Revision

The revision level of the device signifies the number of times it has been updated by the manufacturer.

PCI Device Detail

You can also get additional detail about any of the PCI devices listed by following this procedure:

To get additional detail about a PCI device:

1. 	Press Enter to allow selection in the device list.

2. 	Select the device about which you want additional detail.

3. 	Press Enter, and the detail is displayed, as shown below.

4. 	Press Escape to return to the table of PCI devices.

1. Bus Number

The bus number is the virtual PCI bus number.

2. Function Number

The function number represents the number assigned to a particular function on a multifunction device. For example, a combination Ethernet/SCSI controller would be listed twice, with the first function listed as function 0 and the other function listed as function 1.

3. Device Number

The device number is the PCI bus device number.

4. Configuration Header Space

The configuration header space displays the PCI configuration space information for the selected device. This information is supplied for system engineers.


EISA Configuration Menu

Information about all the EISA devices in your system is presented when you select EISA Configuration and press Enter. An example is shown.

1. Device Name

This is the name and model of the device as recorded in the devices firmware.

2. Device Type

The device type lists the function of the device in the system.

3. Physical Slot

The physical slot lists the actual EISA slot number to which the device is attached. Refer to your system manual for the physical location of EISA slots on the motherboard.


SCSI Configuration Menu

Information about the configuration of your systems SCSI devices is presented when you select SCSI Configuration and press Enter.  In the following figure, only one controller is installed in the system. If additional controllers were installed, a menu, allowing you to select which controller you wish to display information about, is displayed before detailed information about the controller is displayed.

1. SCSI Controller Information

The SCSI controller information describes the physical characteristics of the selected SCSI controller. Information listed in this field includes:

Controller. The controller is the brand and model of SCSI chip used on the SCSI controller.

Controller number. The controller number is based on how many SCSI controllers of a particular type are installed in the system. The first controller of a type is always numbered 0.

SCSI ID number. The SCSI ID number is a unique number assigned to the SCSI controller. This must be a unique number. The standard controller numbering scheme is for controllers to be SCSI ID 7.

SCSI bus number. The SCSI bus number indicates whether the controller is first or second in the system. The first controller is tied to SCSI bus 0, and the second controller is tied to SCSI bus 1.

2. SCSI ID

The SCSI ID number is a unique number you assign to each SCSI device installed in the system.  This is usually done via jumpers on the device or on the StorageWorks backplane.

3. Device Type

The device type displays whether the device is a hard disk, CD-ROM, scanner, or other type of  device.

4. Size

This is the raw capacity of the drive. Formatting the drive with different file systemsfor example, FAT and NTFSmay result in different usable sizes because of the differences in the way storage is managed under those file systems. This information is left blank if it is not applicable to a device, for example, a scanner.

5. Description

This is the name and model of the device as recorded in the devices firmware.


Memory Configuration Menu

Information about the memory configuration is presented when you select Memory Configuration and press Enter. An example is shown.

This shows the amount of memory, in megabytes, installed in your system.

1.  Memory bank

2.  Installed memory

3.  Memory per SIMM


Integrated Peripherals Menu

The integrated peripherals, such as parallel and serial ports, installed in your system are detailed in this menu.

1. Device type

This is the physical device as it exists on the system board.

2. MS DOS name

This shows whether the device is enabled, and if it is enabled, the addressable MS-DOS name for the device.

3. Port address

The port address is the physical memory location from and to which data travels as it is received into the device, and sent from the device, respectively.

4. Interrupt

This is the interrupt request line (IRQ) used by the device to get the CPUs attention.


Run Maintenance Program Menu

This section details the information presented on the AlphaBIOS Run Maintenance Program Menu.

Location

The location is the location from which the program in the Program Name field will be run if no path is entered along with the program name. To display a list of all available disks and partitions, press the Tab key, then use the Down Arrow key. Once the list is displayed, use the Up Arrow key to cycle through the selections. To highlight a location, press the Tab key and the Arrow key.

Program Name

The program name is the program to be run. It must be an executable program with a .EXE filename extension. However, when entering the program name, it is not necessary to type the extension. Programs written to be run from AlphaBIOS must be written as ARC compatible images.


CMOS Setup Menu

CMOS Setup is used to configure several basic system parameters. There are two modes for CMOS Setup:

Standard CMOS Setup Menu

Advanced CMOS Setup Menu


Standard CMOS Setup Menu

Standard CMOS setup is used to configure basic system parameters. To move through the fields, use the Tab key.

1. Date and Time

When setting the time, use the 24-hour format; for example, 10:00 p.m. is 22:00:00.

2. Floppy Drive

AlphaBIOS supports the following types of diskette drives:

•	5.25 inch, 1.2 MB

•	3.5 inch, 1.44 MB

•	3.5 inch, 2.88 MB

3. Keyboard

The keyboard setting makes it possible to use just about any language keyboard available. To ensure correct character mappings, the language of your keyboard, Windows NT, and the keyboard language selection in CMOS setup should all match.

4. Auto Start and Auto Start Count

The Auto Start setting determines whether the primary operating system is automatically started after the system is reset or power-cycled. The Auto Start Count setting is the amount of time the boot menu is displayed before the default system is automatically started. This delay gives you the opportunity, after resetting or power-cycling the system, to select another operating system to start or to enter AlphaBIOS Setup.

5. Standard CMOS Setup Options

Color. Pressing F3 repeatedly cycles through the available AlphaBIOS color schemes.

Advanced. Pressing F6 displays the Advanced CMOS Setup menu.

Defaults. Pressing F7 restores the default standard CMOS setup values without affecting the advanced CMOS setup values.

Discard Changes. Pressing Escape restores the settings in effect when you started CMOS Setup. This option also discards changes made in advanced CMOS setup.

Save Changes. Pressing F10 saves changes made in both the standard and advanced modes of CMOS Setup.


Advanced CMOS Setup Menu

Advanced CMOS setup is used for system-specific parameters and password protection. . To move through the fields, use the Tab key.

1. PCI Parity Error Checking

Possible settings for PCI parity checking are enabled and disabled by using this setting. Parity checking is a method for ensuring data integrity across the PCI bus. AlphaBIOS supports PCI option cards that generate parity as well as those that do not. Unfortunately, many older, and even some newer, PCI option cards do not fully comply with the PCI specification. One of the results of this non-compliance can be incorrect generation of PCI parity.

To accommodate cards that do not correctly generate PCI parity, Alpha systems with PCI expansion slots leave PCI parity checking disabled by default. If you are certain that all of your PCI option cards correctly implement PCI parity generation, you can turn parity checking on. If PCI parity checking results in unstable system behavior, such as lockups, you can turn PCI parity checking off again.

If you discover that a card in your system does not correctly generate PCI parity, you can check with the card manufacturer about getting an updated version of the card with PCI parity generation correctly implemented.

2. Power-up Memory Test

Possible settings for the power-up memory test are enabled and disabled. When enabled, the memory test writes and then reads patterns of data to main system memory. This testing verifies the integrity of main system memory.

3. Password Setup

Possible settings for password setup are disabled, setup password protection, and startup password protection. For more information on password protection, refer to Setting Up Password Protection.

4. Console Selection

Select the firmware console to be presented the next time the system is reset or started up. Selections are Digital UNIX (SRM), OpenVMS Alpha (SRM), or Windows NT (AlphaBIOS).

5. Advanced CMOS Setup Options

Discard changes.  Pressing Escape restores the settings in effect when you started Advanced CMOS Setup. This does not discard changes made to Standard CMOS Setup.

Save Changes.  Pressing F10 saves changes made in advanced CMOS setup. Note that, when exiting CMOS Setup, you must also save your changes at the Standard CMOS Setup menu for the changes to be stored permanently.


System Bus Options

The system bus interconnects the CPU daughter board and memory modules.

The following topics are provided:

CPU Daughter Board

Memory Modules


CPU Daughter Board

AlphaStation 600A 5/500 systems use a CPU daughter board. The daughter board provides:

•	The DECchip 21164A processor

•	8 megabytes of backup cache

•	4 DSW ASIC provides the memory interface

•	CIA provides the PCI bus interface

•	SROM code (SROM tests are controlled by jumper J1 on the CPU daughter board


Memory Modules

AlphaStation 600A 5/500 systems can support from 16 megabytes to 1024 megabytes of memory. Memory options consist of four single in-line memory modules (SIMMs) and are available in the following variations:

•	16-megabyte (consisting of four 4-megabyte SIMMs)

•	32-megabyte (consisting of four 8-megabyte SIMMs)

•	64-megabyte (consisting of four 16-megabyte SIMMs)

•	128-megabyte (consisting of four 32-megabyte SIMMs)

•	256-megabyte (consisting of four 64-megabyte SIMMs)

The motherboard has 16 SIMM connectors. The SIMM connectors are grouped in four memory banks (0, 1, 2, and 3).

Memory Configuration Rules

Observe the following rules when configuring memory on AlphaStation 600A 5/500 systems:

•	Bank 0 must contain a memory option.

•	A memory option consists four SIMMs (0, 1, 2, and 3). The memory SIMMs have built in error detection and correction (ECC) logic.

•	All SIMMs within a bank must be of the same capacity.

The following is the memory requirements and recommendations for each operating system.

Operating System	Memory Requirements
Digital UNIX and OpenVMS	32 MB minimum; 64 MB recommended
Windows NT	16 MB minimum; 32 MB recommended


Motherboard

The motherboard provides a standard set of I/O functions:

•	A Fast Wide SCSI controller chip (Qlogic 1020A) that supports up to 7 Fast Wide SCSI drives

•	The firmware console subsystem on 1 MB of Flash ROM

•	A floppy drive controller

•	Two serial ports with full modem control and the parallel port

•	The keyboard and mouse interface

•	The speaker interface

•	PCI-to-PCI bridge chip set (PPB)

•	PCI-to-EISA bridge chip set

•	EISA system component chip

•	Time-of-year (TOY) clock

•	Connectors:

-  EISA bus connectors (Slots 1 and 2)

-  PCI bus connectors (Slots 11, 12, and 13-before the bridge)

-  PCI bus connects (Slots 1, 2, 3, and 4-behind the bridge)

-  Memory module connectors (16 SIMM connectors)

-  CPU daughter board connector


EISA Bus Options

The EISA (Extended Industry Standard Architecture) bus is a 32-bit industry standard I/O bus. EISA is a superset of the well-established ISA bus. EISA was designed to accept newer 32-bit components while remaining compatible with older 8-bit and 16-bit cards.

EISA offers performance of up to 33 MB/sec for bus masters and DMA devices. Two EISA modules can reside in the EISA bus portion of the card cage. All slots are bus master slots. EISA slots can be filled in any order.


EISA Configuration Utility

Whenever you add or move EISA options or some ISA options in the system, you will need to run a utility called the EISA Configuration Utility (ECU). Each EISA board has a corresponding configuration (CFG) file, which describes the characteristics and the system resources required for that option. The ECU uses the CFG file to create a conflict-free configuration. The ECU is a menu-based utility that provides online help to guide you through the configuration process. The ECU is run from the AlphaBIOS menu interface.

The ECU is supplied on the two System Configuration Diskettes shipped with the system. Make a backup copy of the system configuration diskette and keep the original in a safe place. Use the backup copy when you are configuring the system. The system configuration diskette must have the volume label "SYSTEMCFG."

Note:  The CFG files supplied with the option you want to install may not work on this system if the option is not supported. Before you install an option, check that the system supports the option.

Note:  The version of the ECU that ships with AlphaStation 600A 5/500 systems accommodates 8 EISA slots. However, AlphaStation 600A 5/500 systems have only two EISA slots, slots 1 and 2.

The following topics are available for starting the ECU and configuring EISA options:

Before You Run the ECU

How to Start the ECU

Configuring EISA Options


Before You Run the ECU

Before running the ECU:

1. Install EISA option(s).

For information about installing a specific option, refer to the documentation for that option.

2. Familiarize yourself with the utility.

You can find more information about the ECU by reading the ECU online help. To read the online help, start the ECU. Online help for the ECU is located under Step 1, "Important EISA Configuration Information."

3. Familiarize yourself with the configuration procedure for the system:

•	If you are configuring an EISA bus that contains only EISA options, refer to Configuring EISA Options.

4. Locate the correct ECU diskette for your operating system. The ECU diskette is shipped in the accessories box with the system. Make a copy of the appropriate diskette, and keep the original in a safe place. Use the backup copy for configuring options. The diskettes are labeled as follows:

•	ECU Diskette DECpc AXP (AK-PYCJ*-CA) for Windows NT

•	ECU Diskette DECpc AXP (AK-Q2CR*-CA) for Digital UNIX and OpenVMS


How to Start the ECU

Complete the following steps to run the ECU:

1. Invoke the console firmware.

•	For systems running Windows NT-Shut down the operating system or power up to the console Boot menu.

•	For systems running OpenVMS or Digital UNIX-Shut down the operating system and press the Halt button or power up with the Halt button set to the "in" position. When the console prompt >>> is displayed, set the Halt button to the "out" position.

2. Start the ECU as follows:

Note:  Make sure the ECU diskette is not write-protected.

•	For systems running Windows NT on AlphaBIOS-Select the following menus:

a. From the AlphaBIOS Setup menu, select Utilities.

b. From submenu, select Run Maintenance Program. Insert the ECU diskette for Windows NT (AK-PYCJ*-CA) into the diskette drive and select Run ECU from floppy.

•	For systems running OpenVMS or Digital UNIX-Start the ECU as follows:

a. Insert the ECU diskette for OpenVMS or Digital UNIX (AK-Q2CR*-CA) into the diskette drive.

b. Enter the ecu command.

The system displays "loading ARC firmware." When the firmware has finished loading, the ECU program is booted.

If the system is running AlphaBIOS, the AlphaBIOS firmware is loaded. Refer to section above for starting the ECU on AlphaBIOS.

3. Complete the ECU procedure according to the guidelines provided in the following sections.

•	If you are configuring an EISA bus that contains only EISA options, refer to Configuring EISA Options.

Note:  If you are configuring only EISA options, do not perform Step 2 of the ECU, "Add or remove boards." (EISA boards are recognized and configured automatically.)

4. After you have saved configuration information and exited from the ECU:

•	For systems running Windows NT-Remove the ECU diskette from the diskette drive and boot the operating system.

•	For systems running OpenVMS or Digital UNIX-Remove the ECU diskette from the diskette drive. Return to the SRM console firmware as follows:

a. From the CMOS Setup menu, press F6 to enter Advanced CMOS setup.

b. From the Advanced CMOS Setup menu, select Windows NT (AlphaBIOS).

c. Press F10 to save the change.

d. When the "Power-cycle the system to implement the change" message is displayed, press the Reset button. (Do not press the On/Off switch.) Once the console firmware is loaded and device drivers are initialized, you can boot the operating system.

5. Verify that the new options are configured correctly.


Configuring EISA Options

EISA boards are recognized and configured automatically. Study the following table for a summary of steps to configure an EISA bus. Review Before You Run the ECU. Then run the ECU as described in How to Start the ECU.

Note:  It is not necessary to run Step 2 of the ECU, "Add or remove boards." (EISA boards are recognized and configured automatically.)

Summary of Procedure for Configuring EISA Bus Options

Step	Explanation
Install EISA option.	Use the instructions provided with the EISA option.
Power up and run ECU	If the ECU locates the required CFG configuration files, it displays the main menu. The CFG file for the option may reside on a configuration diskette packaged with the option or may be included on the system configuration diskette. Note:  It is not necessary to run Step 2 of the ECU, "Add or remove boards." (EISA boards are recognized and configured automatically.)
View or Edit Details (optional)	The "View or Edit Details" ECU option is used to change user-selectable settings or to change the resources allocated for these functions (IRQs, DMA channels, I/O ports, and so on). This step is not required when using the board's default settings.
Save your configuration and restart the system.	The "Save and Exit" ECU option saves your configuration information to the system's nonvolatile memory.
Return to the SRM console (Digital UNIX  and OpenVMS systems only) and restart the system.	Refer to step 4 of How to Start the ECU for operating-system-specific instructions.


PCI Bus Options

PCI (Peripheral Component Interconnect) is an industry-standard expansion I/O bus that is the preferred bus for high-performance I/O options. The AlphaStation 600A 5/500 provides seven slots for 32-bit PCI options.

Install PCI boards according to the instructions supplied with the option. PCI boards require no additional configuration procedures; the system automatically recognizes the boards and assigns the appropriate system resources.

PCI-to-PCI Bridge

AlphaStation 600A 5/500 systems have a PCI-to-PCI bridge (DECchip 21050) on the motherboard.

•	Physical PCI slots 11, 12, and 13 (primary PCI) are located before the bridge.

•	Physical PCI slots 1, 2, 3, and 4 (secondary PCI) are located behind the bridge.

Some PCI options are restricted to the primary PCI bus, slots 11, 12, and 13. Refer to the option documents for restrictions on specific PCI options.


Console Port Configurations

Power-up information is typically displayed on the system's console terminal. The console terminal may be either a graphics monitor or a serial terminal (connected through the COM1 serial port).

There are several SRM console environment variables related with configuring the console ports:

Environment Variable	Description
console	Determines where the system will display power-up output. Set this environment variable according to the console terminal that you are using.
tt_allow_login	Enables or disables login to the SRM console firmware on alternative console ports.
In addition, the tga_sync_green environment variable is used to synchronize monitors using the high-performance turbo graphics adapter card (PBXGA).

A serial terminal can also be configured to run the ECU.

When using a VGA controller, refer to Using a VGA Controller.


set console

The setting of the console environment variable determines where the system will display power-up output. Power-up information is typically displayed on the console terminal. The console terminal can be either a graphics monitor or a serial terminal. Set this environment variable according to the console terminal that you are using.

Whenever you change the value of this environment variable, you must initialize the firmware with the init command.

Synopsis:

set console output_device

Arguments:

graphics	Sets the power-up output to be displayed at a graphics monitor or a device that is connected to the VGA module at the rear of the system (default setting).
serial	Sets the power-up output to be displayed on the device that is connected to the COM1 port at the rear of the system.
Example:

P00>>> set console serial

P00>>> init

.

.

.  !Now switch to the serial terminal.

P00>>> show console

console       serial


set tt_allow_login

The setting of the tt_allow_login environment variable enables or disables login to the SRM console firmware on alternative console ports.

Synopsis:

set tt_allow_login [0,1]

Arguments:

1	Enables login on alternative console ports (default setting). If the console output device is set to "serial", allows you to log in on the primary COM1 port, or alternative COM2 port, or the graphics monitor. If the console output device is set to "graphics", allows you to log in through either the primary graphics monitor or the alternate COM1 or COM2 console ports.
0	Disables login on alternative console ports.
Whenever you change the value of this environment variable, you must initialize the firmware with the init command.

Example:

>>> set console serial

>>> set tt_allow_login 1

>>> init


set tga_sync_green

The tga_sync_green environment variable sets the location of the SYNC signal generated by the ZLXp-E PCI graphics accelerator card.

The correct setting, displayed with the show command, is:

>>> show tga_sync_green

tga_sync_green

If the monitor does not synchronize, set the parameter as follows:

>>> set tga_sync_green 00

Description:

This commands sets all graphics cards to synchronize on a separate vertical SYNC line, as required by some monitors. See the monitor documentation for all other information.


Setting Up a Serial Terminal to Run ECU

You can run the ECU from either a VGA-compatible graphics terminal or from a serial (VT200 or higher, or equivalent). Graphics is the default. To use a serial terminal with the ECU, do the following:

1. Invoke the terminal setup utility as described in the documentation for the serial terminal and change settings as follows:

•	From the General menu, set the terminal mode to VTxxx, 8-bit controls.

•	From the Comm menu, set the character format to 8 bit, no parity, and set receive XOFF to 128 or greater.

•	From the Keyboard menu, set the keyboard so that the tilde (~) key sends the escape (ESC) signal.

2. Enter the following commands at the SRM console prompt to set the console terminal to receive input in serial mode.

>>> set console serial

>>> init

.

.

.   !Now switch to the serial terminal

>>> show console

console     serial


Using a VGA Controller

When the system is configured to use a PCI- or EISA-based VGA controller, consider the following:

•	The console environment variable should be set to graphics.

•	If there are multiple VGA controllers, the system will direct console output to the first controller it finds.


Troubleshooting

This section provides information on troubleshooting strategy and diagnostics for the AlphaStation 600A 5/500 system.

It includes the following main topics:

Troubleshooting the System

Service Tools and Utilities

Information Services

Power-Up Diagnostics and Display

Running System Diagnostics

Error Log Analysis


Troubleshooting the System

Before troubleshooting any system problem, check the site maintenance log for the system's service history. Be sure to ask the system manager the following questions:

1.	Has the system been used before and did it work correctly?

2.	Have changes to hardware or updates to firmware or software been made to the system recently? If so, are the revision numbers compatible for the AlphaStation and the operating system? (Refer to the hardware and operating system release notes).

3.	What is the state of the system -- is the operating system running?

•	If the operating system is down and you are not able to bring it up, use the console environment diagnostic tools, such as the power-up display and ROM-based diagnostics (RBDs).

•	If the operating system is running, use the operating system environment diagnostic tools, such as the DECevent management utility (to translate and interpret error logs), crash dumps, and exercisers (DEC VET).

System problems can be classified into the following five categories. Using these categories, you can quickly determine a starting point for diagnosis and eliminate the unlikely sources of the problem.

Power problems

No access to console mode

Console-reported failures

Boot failures

Operating system-reported problems


Power Problems

Use the following table for diagnosing power problems.

Symptom	Action
System does not power on.	Check the power source and power cord.
	Check that the system s side panel is properly secured. A safety interlock switch shuts off power to the system if the side cover is removed.
	Check the On/Off switch setting on the operator control panel.
	Check that the ambient room temperature is within environmental specifications (10-40ºC, 50-104ºF).
	Check that internal power supply cables are plugged in at both the power supply and system motherboard.
Power supply shuts down after a few seconds (fan failure).	Using a flashlight, look through the to determine if the fan is spinning at power-up. A failure of the fan causes the system to shut down after a few seconds.


No Access to Console Mode

Use the following table to diagnose problems with accessing console mode.

Symptom	Action
Power-up screen is not displayed.	Interpret the error beep codes at power up for a failure detected during self-tests. In addition to beep codes, error codes are displayed on the OCP. Check that keyboard and monitor are properly connected and powered on. If the power-up screen is not displayed, yet the system enters console mode when you press the Return key, check that the console environment variable is set correctly. If you are using a VGA console terminal, the console variable should be set to graphics. If you are using a serial console terminal, the console variable should be set to serial. If a VGA controller is being used, refer to Using a VGA Controller for more information. If console is set to serial, the power-up screen is routed to the COM1 serial communication port and cannot be viewed from the VGA monitor. Try connecting a console terminal to the COM1 serial communication port. If necessary use an MMJ-to-9-pin adapter (H8571-J). Check the baud rate setting for the console terminal and system. The system baud rate setting is 9600. When using the COM1 port, you must set the console environment variable to "serial." For certain situations, power up using the fail-safe loader to load new console firmware from a diskette.


Console-Reported Failures

Use the following table to diagnose problems reported by the console program.

Symptom	Action
Power-up tests do not complete.	Interpret the error beep codes at power-up and check the power-up screen for a failure detected during self-tests. Error codes are also displayed on the OCP.
Console program reports error: • Error beep codes report an error at power-up. • Power-up screen includes error messages. • Error codes are displayed on the OCP.	Use the error beep codes and/or console terminal to determine error. . Error codes are also displayed on the OCP. Examine the console event log (enter the more el command) or the power-up screen to check for embedded error messages recorded during power-up. If power-up screen or console event log indicate problems with mass storage devices, or if storage devices are missing from the show config display, use the mass storage troubleshooting table to determine the problem. If power-up screen or console event log indicate problems with EISA devices, or if EISA devices are missing from the show config display, use the EISA troubleshooting table to determine the problem. If power-up screen or console event log indicate problems with PCI devices, or if PCI devices are missing from the show config display, use the PCI troubleshooting table to determine the problem. Run the ROM-based diagnostic (RBD) tests to verify the problem.


Boot Failures

Use the following table for diagnosing power problems.

Symptom	Action
System cannot find boot device.	Check system configuration for correct device parameters (node ID, device name, and so on).  • For Digital UNIX and OpenVMS, use the show config and show device commands. • For Windows NT, use the Display Hardware Configuration display and the Set Default Environment Variables display. Check the system configuration for the correct environment variable settings.  • For Digital UNIX and OpenVMS, examine the auto_action, bootdef_dev, boot_osflags, and os_type environment variables. Also make sure that the bus_probe_algorithm is set to new. For problems booting over a network, check the ew*0_protocols or er*0_protocols environment variable settings: Systems booting from a Digital UNIX server should be set to bootp; systems booting from an OpenVMS server should be set to mop. • For Windows NT, examine the FWSEARCHPATH, AUTOLOAD, and COUNTDOWN environment variables.
Device does not boot.	For problems booting over a network, check the ew*0_protocols or er*0_protocols environment variable settings: Systems booting from a Digital UNIX server should be set to bootp; systems booting from an OpenVMS server should be set to mop. For systems running Digital UNIX and OpenVMS, make sure that the bus_probe_algorithm environment variable is set to new. Run the device tests to check that the boot device is operating.


Operating System-Reported Failures

Use the following table to diagnose operating system-reported failures.

Symptom	Action
System is hung or has crashed.	Examine the crash dump file.   • Refer to OpenVMS Alpha System Dump Analyzer Utility Manual (AA-PV6UB-TE) for information on how to interpret OpenVMS crash dump files. • Refer to the Guide to Kernel Debugging (AA-PS2TD-TE) for information on using the Digital UNIX Krash Utility.
Errors have been logged and the operating system is up.	Examine the operating system error log files to isolate the problem.   If the problem occurs intermittently, run an operating system exerciser, such as DEC VET, to stress the system. Refer to the DEC Verifier and Exerciser Tool User's Guide (AA-PTTMD-TE) for instructions on running DEC VET.


Service Tools and Utilities

This section contains information on the following service tools and utilities available for acceptance testing, diagnosis, and serviceability and provides recommendations for their use.

Error Handling/Logging Tools

ROM-Based Diagnostics (RBDs)

Loopback Tests

Firmware Console Commands

Operating System Exercisers (DEC VET)

Crash Dumps


Error Handling/Logging Tools

Digital UNIX, OpenVMS, and Microsoft Windows NT operating systems provide recovery from errors, fault handling, and event logging. The DECevent Translation and Reporting Utility provides bit-to-text translation of event logs for interpretation for Digital UNIX and Open VMS error logs.

RECOMMENDED USE: Analysis of error logs is the primary method of diagnosis and fault isolation. If the system is up, or you are able to bring it up, look at this information first.


ROM-Based Diagnostics (RBDs)

Many ROM-based diagnostics and exercisers are embedded in AlphaStation 600A 5/500 systems. ROM-based diagnostics execute automatically at power-up and can be invoked in console mode using console commands.

RECOMMENDED USE: ROM-based diagnostics are the primary means of testing the console environment and diagnosing the CPU, memory, Ethernet, I/O buses, and SCSI and DSSI subsystems. Use ROM-based diagnostics in the acceptance test procedures when you install a system, add a memory module, or replace the following components: CPU daughter board, memory module, motherboard, I/O bus device, or storage device.


Loopback Tests

Internal and external loopback tests are used to isolate a failure by testing segments of a particular control or data path. The loopback tests are a subset of the ROM-based diagnostics.

RECOMMENDED USE: Use loopback tests to isolate problems with the COM2 serial port, the parallel port, and Ethernet controllers.


Firmware Console Commands

Console commands are used to set and examine environment variables and device parameters, as well as to invoke ROM-based diagnostics and exercisers. For example, the show memory, show configuration, and show device commands are used to examine the configuration; the set (bootdef_dev, auto_action, and boot_osflags) commands are used to set environment variables; and the cdp command is used to configure DSSI parameters.

RECOMMENDED USE: Use console commands to set and examine environment variables and device parameters and to run RBDs.


Operating System Exercisers (DEC VET)

The Digital Verifier and Exerciser Tool (DEC VET) is supported by the Digital UNIX, OpenVMS, and Windows NT operating systems. DEC VET performs exerciser-oriented maintenance testing of both hardware and operating system.

RECOMMENDED USE: Use DEC VET as part of acceptance testing to ensure that the CPU, memory, disk, tape, file system, and network are interacting properly. Also use DEC VET to stress test the user's environment and configuration by simulating system operation under heavy loads to diagnose intermittent system failures.


Crash Dumps

For fatal errors, such as fatal bugchecks, Digital UNIX and OpenVMS operating systems save the contents of memory to a crash dump file.

RECOMMENDED USE: Crash dump files can be used to determine why the system crashed. To save a crash dump file for analysis, you need to know the proper system settings. Refer to the OpenVMS Alpha System Dump Analyzer Utility Manual (AA-PV6UB-TE) or the Guide to Kernel Debugging (AA--PS2TD--TE) for Digital UNIX.


Information Services

Several information resources are available, including online information for service personnel and customers, computer-based training, and maintenance documentation database services.

A brief description of some of these resources is contained in the following topics:

Alpha Firmware Updates

ECU Revisions

OpenVMS Patches

Supported Options

Training

Digital Assisted Services


Alpha Firmware Updates

Under certain circumstances, such as a CPU upgrade or replacement of the system backplane, you need to update your system firmware. An Alpha Firmware CD-ROM is shipped on an as released basis with Digital UNIX, OpenVMS, and Windows NT operating systems.

The Alpha firmware files can also be downloaded from the Internet as follows:

http://ftp.digital.com/pub/DEC/Alpha/firmware/

New versions of firmware released between shipments of the Alpha Firmware CD-ROM are available in an interim directory:

ftp://ftp.digital.com/pub/Digital/Alpha/firmware/interim/


ECU Revisions

The EISA Configuration Utility (ECU) is used for configuring EISA options on AlphaStation systems. Systems are shipped with an ECU kit, which includes the ECU license. Customers who already have the ECU and license, but need the latest revision of the ECU, can order a separate kit. Call 1-800-DIGITAL to order.

If the customer plans to migrate from Digital UNIX or OpenVMS to Windows NT, you must re-run the appropriate ECU. Failure to run the operating-specific ECU will result in system failure.


OpenVMS Patches

Software patches for the OpenVMS operating system are available from the World Wide Web as follows:

http://www.service.digital.com/html/patch_service.html

Choose the Contract Access option if you have a valid software contract with Digital or you wish to become a software contract customer. Choose the Public Access options if you do not have a software service contract.


Supported Options

Refer to the AlphaStation 600A 5/500 Supported Options List for a list of options supported under Digital UNIX, OpenVMS, and Windows NT. The options list is available from the Internet as follows:

•	FTP address:

ftp://ftp.digital.com/pub/Digital/Alpha/systems/

•	World Wide Web address:

http://www.service.digital.com/alpha/server/

You can obtain information about hardware configurations for the AlphaStation 600A 5/500 from the Digital Systems and Options Catalog. The catalog is regularly published to assist in ordering and configuring systems and hardware options. Each printing of the catalog presents all of the products that are announced, actively marketed, and available for ordering.

Access printable postscript files of any section of the catalog from the Internet as follows (Be sure to check the Readme file):

ftp://ftp.digital.com/pub/Digital/info/SOC/


Training

The following Computer Based Training (CBT) and lecture lab courses are available from the Digital training center:

•	Alpha Concepts

•	DSSI Concepts: EY-9823E

•	ISA and EISA Bus Concepts: EY-I113E-P0

•	RAID Concepts: EY-N935E

•	SCSI Concepts and Troubleshooting: EY-P841E, EY-N838E


Digital Assisted Services

Digital Assisted Services (DAS) offers products, services, and programs to customers who participate in the maintenance of Digital computer equipment. Components of Digital assisted services include:

•	Spare parts and kits

•	Diagnostics and service information/documentation

•	Tools and test equipment

•	Parts repair services, including Field Change Orders


Power-Up Diagnostics and Display

This section provides information on how to interpret error beep codes and the power-up display on the console screen. In addition, a description of the power-up and firmware power-up diagnostics is provided to aid in troubleshooting.

The following topics are included:

Error Beep Codes

SROM Error Codes

Power-Up Screen

Console Event Log

Mass Storage Problems

Storage Device LEDs

EISA Bus Problems

PCI Bus Problems

Fail-Safe Loader

Power-Up Sequence

Firmware Power-Up Diagnostics


Error Beep Codes

If errors are detected at power-up, audible beep codes are emitted from the system. For example, if the SROM code could not fine any good memory, you would hear a 1-3-3 beep code (one beep, a pause, a burst of three beeps, a pause, and another burst of three beeps).

Be sure to check that the CPU daughter board is properly seated in its connector if errors are reported.

Note:  A single beep is emitted for the system when the SROM code has successfully completed. The console firmware then continues with its power-up tests.

The beep codes are the primary diagnostic tool for troubleshooting problems when console mode cannot be accessed. Use the table below to interpret error beep codes.

Beep Code	Problem	Corrective Action
1-1-2	ROM data path error detected while loading the SRM/AlphaBIOS console code.	1. Use the Fail_Safe Loader to load new SRM/AlphaBIOS console code. 2. If successfully loading new console firmware does not solve the problem, replace the motherboard.
1-1-4	The SROM code is unable to load the console code: Flash ROM header area or checksum error detected.	1. Use the Fail-Safe Loader to load new SRM/AlphaBIOS console code. 2. If successfully loading new console firmware does not solve the problem, replace the motherboard.
1-2-1	TOY NVRAM failure.	Replace the TOY NVRAM chip (E78) on the motherboard.
1-2-4	Backup cache error.	Replace the CPU daughter board. The system can be operated with Bcache disabled until a replacement CPU daughter board is available. Bank 4 of the J1 jumper on the CPU daughter board is used to disable the Bcache.
1-3-3	No usable memory detected.	1. Verify that the memory modules are properly seated and try powering up again. 2. Swap bank 0 memory with known good memory and run SROM memory tests at power-up. 3. If populating bank 0 with known good memory does not solve the problem, replace the CPU daughter board. 4. If replacing the CPU daughter board does not solve the problem, replace the motherboard.
3-1-2	J1 jumper on the CPU daughter board set incorrectly or failure of native SCSI controller (Qlogic 1020A).	1. Check that the J1 jumper on the CPU daughter board is set at bank 0.   2. If the J1 jumper setting is not the problem, replace the motherboard.
3-3-1	Generic system failure. Possible problem sources include the TOY NVRAM chip (Dallas DS1287A) or PCI-to-EISA bridge chipset (Intel 82375EB).	1. Replace the TOY NVRAM chip (E78) on system motherboard.  2. If replacing the TOY NVRAM chip did not solve the problem, replace the motherboard.
3-3-2	J1 jumper on the CPU daughter board set incorrectly or failure of the PCI-to-PCI bridge (DECchip 21050).	1. Check that the J1 jumper on the CPU daughter board is set at 0.  2. If the J1 jumper setting is not the problem, replace the motherboard.
3-3-3	Failure of the native SCSI controller (Qlogic 1020A) on the motherboard.	Replace the motherboard.


Power-Up Screen

During power-up self-tests, the test status and result are displayed on the console terminal.  Information similar to the following should be displayed on the screen.

ff.fe.fd.fc.fb.fa.f9.f8.f7.f6.f5.ef.df.ee.f4.

probing hose 0, PCI

probing PCI-to-PCI bridge, bus 1

bus 1, slot  0 -- pka -- QLogic ISP1020

bus 0, slot 11 -- ewa -- DECchip 21040-AA

probing hose 1, EISA

ECU error, slot 0, found DEC5000, expected nothing

EISA Configuration Error

Run the EISA Configuration Utility

ed.ec.eb.....ea.e9.e8.e7.e6.e5.e4.e3.e2.e1.e0.

X4.6-8189, built on Jul 29 1996 at 03:21:03

Memory Testing and Configuration Status

     32 Meg of System Memory

     Bank 0 = 32 Mbytes(8 MB Per SIMM) Starting at 0x00000000

     Bank 1 = No Memory Detected

     Bank 2 = No Memory Detected

     Bank 3 = No Memory Detected

Testing the System

Change mode to Internal loopback.

Change to Normal Operating Mode.

>>>

If the power-up display stops, use the error beep codes and the following countdown table to isolate the likely field-replaceable unit (FRU).

Countdown Number	Description	Likely FRU
ff	Console initiation  started	Non-specific/Status message
fe	Initialized idle PCB	Non-specific/Status message
fd	Initializing semaphores	Non-specific/Status message
fc,fb,fa	Initializing heap	Non-specific/Status message
f9	Initializing driver structures	Non-specific/Status message
f8	Initializing idle process PID	Non-specific/Status message
f7	Initializing file system	TOY chip (E78)
f6	Initializing timer data structures	Non-specific/Status message
f5	Lowering IPL	Non-specific/Status message
f4	Entering idle loop	TOY chip (E78)
ef	Start memory configuration (heap)	SIMM memory or backplane
df	Configure PCI and EISA bus	PCI or EISA option
ee	Start phase 1 drivers: NVRAM andPCICFG drivers	NVRAM chip (E14) or PCI option
ed	Start phase 2 drivers: IIC and OCP drivers	Non-specific/Status message
ec	Start phase 3 drivers (console selct): tt serial line class, tga graphics, vga graphics, and keyboard drivers	Keyboard, VGA or TGA option, or backplane
eb	Run power-up memory test	SIMM memory
ea	Start phase 4 drivers	Non-specific/Status message
e9	Phase 4 drivers complete	Non-specific/Status message
e8	Initialize environment variables	Non-specific/Status message
e7	Start SCSI class driver	Backplane (on-board Qlogic 1020A)
e6	Start phase 5 drivers: I/O drivers	PCI or EISA option
e5	Restore timers	TOY chip (E78)
Digital UNIX or OpenVMS Systems

Digital UNIX and OpenVMS operating systems are supported by the SRM firmware. The SRM console prompt, >>>, is available using SRM console firmware.

Windows NT Systems

The Windows NT operating system is supported by the AlphaBIOS firmware. Systems using Windows NT power up to the AlphaBIOS boot menu.


Console Event Log

AlphaStation 600A 5/500 systems maintain a console event log consisting of status messages received during power-on self-tests. If problems occur during power-up, standard error messages indicated by asterisks (***) may be embedded in the console event log. To display a console event log, use the more el or cat el command.

Note:  To stop the screen display from scrolling, enter Ctrl/S. To resume scrolling, enter Ctrl/Q. You can also use the command, more el, to display the console event log one screen at a time.

The following example shows a console event log that contains two standard error messages. The first indicates that the mouse is not plugged in or is not working, and the second indicates that SROM tests detected a bad SIMM (bank1, SIMM3).

>>>  cat el

ff.fe.fd.fc.fb.fa.f9.f8.f7.f6.f5.ef.df.ee.f4.

probing hose 0, PCI

probing PCI-to-EISA bridge, bus 1

probing PCI-to-PCI bridge, bus 2

bus 2, slot  0 -- pka -- QLogic ISP1020

bus 0, slot 11 -- ewa -- DECchip 21040-AA

ed.ec.

** mouse error **

*** Bad memory detected by serial rom

*** SROM failing Bank 1, SIMM 3

eb.....ea.e9.e8.e7.e6.e5.e4.e3.e2.e1.e0.

X4.6-10166, built on Aug 30 1996 at 16:18:06

.

.

.

>>>


Mass Storage Problems

Mass storage failures at power-up are usually indicated by read fail messages. Other problems are indicated by storage devices missing from the show config display. The following mass storage troubleshooting table can help you diagnose the likely cause of the problem.

Problem	Symptom	Corrective Action
Drive failure	Fault LED for  drive is on (steady).	Replace drive.
Duplicate SCSI IDs	Drives with duplicate SCSI IDs are missing from the show config display.	Correct SCSI IDs.
SCSI ID set to 7 (reserved for host ID)	Valid drives are missing from the show config display. One drive may appear seven times on the configuration screen display.	Correct SCSI IDs.
Duplicate host IDs on a shared bus	Valid drives are missing from the show config display. One drive may appear seven times on the configuration screen display.	Change host ID through the pk*0_host_id environment variable, (set pk*0_host_id) for systems running Digital UNIX or OpenVMS (SRM console). For systems running Windows NT (AlphaBIOS), choose Hard Disk Configuration in the Display System Configuration Menu.
Missing or loose cables.	Activity LEDs do not come on. Drive missing from the show config display.	Remove device and inspect cable connections.
SCSI storage controller failure	Problems persist after eliminating the problem sources.	Replace the failing EISA or PCI storage adapter module (or motherboard for the native SCSI controller).


Storage Device LEDs

Storage device LEDs indicate the status of the device.

The following figure shows the Activity LED for the floppy drive. This LED is on when the drive is in use.

The following figure shows the Activity LED for the CD-ROM drive. This LED is on when the drive is in use.

For information on other storage devices, refer to the documentation provided by the manufacturer or vendor.


EISA Bus Problems

EISA bus failures at power-up are usually indicated by the following messages displayed during power-up:

EISA Configuration Error. Run the EISA Configuration Utility.

Run the EISA Configuration Utility (ECU) when this message is displayed. Other problems are indicated by EISA devices missing from the show config display.

Use the EISA Troubleshooting Table below to troubleshoot EISA bus problems that continue after you run the ECU.

Step	Action
1	Confirm that the EISA module and any cabling are properly seated.
2	Run the ECU to: • Confirm that the system has been configured with the most recently installed controller. • See what the software setting should be for each EISA controller. • See if the ECU deactivated (<>) any controllers to prevent conflict. • See if any controllers are locked (!), which limits the ECU's ability to change resource assignments.
3	Run ROM-based diagnostics for the type of option: • Storage and network adapter  Run test to exercise the storage devices off the EISA controller option and the network adapter.
4	Check for bad slot by moving the last installed controller to a different slot.
5	Call option manufacturer or support for help.
Additional EISA Troubleshooting Tips

The following tips can aid in isolating EISA bus problems:

•	Peripheral device controllers need to be seated (inserted) carefully, but firmly, into their slots to make all necessary contacts. Improper seating is a common source of problems for EISA modules.

•	Be sure you run the correct version of ECU for the operating system. For Windows NT, use ECU diskette DECpc AXP (AK-PYCJ*-CA); for Digital UNIX and OpenVMS, use ECU diskette DECpc AXP (AK-Q2CR*-CA).

•	The CFG files supplied with the option you want to install may not work on AlphaStation 600A 5/500 systems. Some CFG files call overlay files that are not required on this system or may reference inappropriate system resources, for example, BIOS addresses. Contact the option vender to obtain the proper CFG file.

•	Peripherals cannot share direct memory access (DMA) channels. Assignment of more than one peripheral to the same DMA channel can cause unpredictable results or even loss of function of the EISA module.

•	Not all EISA products work together. EISA is an open standard, and not every EISA product or combination of products can be tested. Violations of specifications may matter in some configurations, but do not in others.

Manufacturers of EISA options often test the most common combinations and may have a list of EISA options that do not function in combination with particular systems. Be sure to check the documentation or contact the option vender for the most up-to-date information.

•	EISA systems will not function unless they are first configured using the ECU.

•	The ECU will not notify you if the configuration program diskette is write-protected when it attempts to write the system configuration file (system.sci) to the diskette.


PCI Bus Problems

PCI bus failures at power-up are usually indicated by the inability of the system to see the device. Use the PCI following troubleshooting table to diagnose the likely cause of the problem.

Note:  Some PCI devices do not implement PCI parity, and some have a parity-generating scheme in which parity is sometimes incorrect or is not compliant with the PCI Specification. In such cases, the device functions properly as long as parity is not checked. The pci_parity environment variable for the SRM console, or the ENABLEPCIPARITY CHECKING for the AlphaBIOS console, allow you to turn off parity checking so that false PCI parity errors do not result in machine check errors.

Note:  When you disable PCI parity, no parity checking is implemented for any PCI device, even those devices that produce correct, compliant parity.

Some PCI options are restricted to the primary PCI bus, slots 11, 12, and 13. Refer to the option documents for restrictions on specific PCI options.

Step	Action
1	Confirm that the PCI module and any cabling are properly seated.
2	Run ROM-based diagnostics for the type of option: • Storage and network adapter -- Run test to exercise the storage devices off the PCI controller option and the network adapter.
3	Check for bad slot by moving the last installed controller to a different slot.
4	Call option manufacturer or support for help.


Fail-Safe Loader

The fail-safe loader (FSL) is a redundant or backup ROM that allows you to power up without running power-up diagnostics and load new SRM/AlphaBIOS and FSL console firmware from the firmware diskette.

Note:  The fail-safe loader should be used only when a failure at power-up prohibits you from getting to the console program. You cannot boot an operating system from the fail-safe loader.

Note:  If a checksum error is detected when the SRM/AlphaBIOS console is loading at power-up (error beep code 1-1-4), you need to activate the fail-safe loader and reinstall the firmware.

The fail-safe loader (FSL) allows you to attempt to recover when one of the following is the cause of a problem getting to the console program under normal power-up:

•	A hardware or power failure, or accidental power down during a firmware upgrade occurred.

•	A configuration error, such as an incorrect environment variable setting or an inappropriate nvram script.

•	A driver error at power-up.

•	A checksum error is detected when the SRM console is loading at power-up (corrupted firmware).

From the FSL program, you can update or load new SRM/AlphaBIOS console firmware and FSL console firmware. The fail-safe loader program is available on diskette.

Activating the Fail-Safe Loader

Note: When installing new console firmware, the flash ROM VPP enable jumper (J50) on the motherboard must be enabled.

To activate the FSL:

1.	Install the jumper at bank 7 of the J1 jumper on the CPU daughter board. The jumper is normally installed in the standard boot setting (bank 0 for AlphaStation 600A 5/500 systems).

2.	Install the console firmware floppy diskette and turn on the system. Two messages are displayed on the operator control panel (OCP) when the FSL program loads the diskette:

OCP Message	Meaning
Floppy Boot	FSL firmware is executing.
Starting CPU	FSL firmware found a valid boot block, loaded the program into memory, and is attempting to transfer control to the loaded program.
3.	Reinstall the console firmware from a firmware diskette.

4.	When you have finished, power down and return the J1 jumper to the standard boot setting (bank 0).


Power-Up Sequence

During the AlphaStation 600A 5/500 power-up sequence, the power supply is stabilized and the system is initialized and tested through the firmware power-on self-tests.

The power-up sequence includes the following:

AC Power-Up Sequence

DC Power-Up Sequence


AC Power-Up Sequence

The following power-up sequence occurs when AC power is applied to the system (systems is plugged in) or when electricity is restored after a power outage:

•	The front end of the power supply begins operation and energizes.

•	The power supply then waits for the DC power to be enabled.

Note:  The side panel must be securely installed. A safety interlock prevents the system from being powered on with the panel removed.


DC Power-Up Sequence

DC power is applied to the system with the DC On/Off button on the operator control panel.

A summary of the DC power-up sequence follows:

1.	When the DC On/Off button is pressed, the power supply checks for a POK_H condition.

2.	12V, 5V, 3.3V, and -12V outputs are energized and stabilized. If the outputs do not come into regulation, the power-up is aborted and the power supply enters the latching-shutdown mode.


Firmware Power-Up Diagnostics

After successful completion of AC and DC power-up sequences, the processor performs its power-up diagnostics. These tests verify system operation, load the system console, and test the core system (CPU, memory, and motherboard), including all boot path devices. These tests are performed as two distinct sets of diagnostics:

•	Serial ROM diagnostics --These tests are loaded from the serial ROM located on the CPU daughter board into the CPU's instruction cache (I-cache). They check the basic functionality of the system and load the console code from the FEPROM on the motherboard into system memory.

Failures during these tests are indicated by audible error beep codes, the console event log, and the OCP error codes.

•	Console firmware-based diagnostics --These tests are executed by the console code. They test the core system, including all boot path devices.

Failures during these tests are reported to the console terminal through the power-up screen or console event log.


Serial ROM Diagnostics

The serial ROM diagnostics are loaded into the CPU's instruction cache from the serial ROM on the CPU daughter board. The diagnostics test the system in the following order:

1.	Test the CPU and backup cache located on the CPU daughter board.

2.	Test the CPU module's system bus interface.

3.	Test the system bus to PCI bus bridge and system bus to EISA bus bridge. If the PCI bridge fail or EISA bridge fails, an audible error beep code (3-3-1) sounds.. The power-up tests continue despite these errors.

4.	Test the PCI-to-PCI bus bridge. If the bridge fails, an error beep code (3-1-2) sounds.

5.	Test the native SCSI controller. If the controller fails, an error beep code (3-1-2) sounds.

6.	Configure the memory in the system and test only the first 16 MB of memory. If the memory test fails, the failing bank is mapped out and memory is reconfigured and re-tested. Testing continues until a good memory is found. If good memory is not found, an error beep code (1-3-3) is generated and power-up tests are terminated.

7.	Check the data path to the FEPROMs on the motherboard.

8.	The console program is loaded into memory from the FEPROM on the motherboard. A checksum test is executed for the console image. If the checksum test fails, an error beep code (1-1-4) is generated and the power-up tests are terminated. If the checksum test passes, control is passed to the console code, and the console firmware-based diagnostics are run.


Console Firmware-Based Diagnostics

Console firmware-based tests are executed once control is passed to the console code in memory. They check the system in the following order:

1.	Perform a complete check of system memory.

Steps 2--5 may be completed in parallel.

2.	Start the I/O drivers for mass storage devices and tapes. At this time a complete functional check of the machine is made. After the I/O drivers are started, the console program continuously polls the bus for devices (approximately every 20 or 30 seconds).

3.	Check that EISA configuration information is present in NVRAM for each EISA module detected and that no information is present for modules that have been removed.

4.	Run exercisers on the drives currently seen by the system.

Note:  This step does not ensure that all disks in the system will be tested or that any device drivers will be completely tested. Spin-up time varies for different drives, so not all disks may be on line at this point in the power-up. To ensure complete testing of disk devices, use the test command.

5.	Enter console mode or boot the operating system. This action is determined by the auto_action environment variable.

If the os_type environment variable is set to NT, the AlphaBIOS console is loaded into memory, and control is passed to the AlphaBIOS console.


Running System Diagnostics

This section provides information on how to run system diagnostics.

The following topics are covered:

Running ROM-Based Diagnostics

Command Summary

Command Reference

Acceptance Testing and Initialization

DEC VET


Running ROM-Based Diagnostics

ROM-based diagnostics (RBDs), which are part of the console firmware that is loaded from the FEPROM on the motherboard, offer many powerful diagnostic utilities, including the ability to examine error logs from the console environment and run system- or device-specific exercisers.

AlphaStation 600A 5/500 RBDs rely on exerciser modules, rather than functional tests, to isolate errors. The exercisers are designed to run concurrently, providing a maximum bus interaction between the console drivers and the target devices.

The multitasking ability of the console firmware allows you to run diagnostics in the background (using the background operator & at the end of the command). You run RBDs by using console commands.

Note:  ROM-based diagnostics, including the test command, are run from the SRM console (firmware used by OpenVMS and Digital UNIX operating systems). If you are running a Windows NT system, you will need to switch consoles. RBDs report errors to the console terminal and/or the console event log.


Command Summary

The following table provides a summary of the diagnostic and related commands.

Command	Function
Acceptance Testing
test	Quickly tests the core system. The test command is the primary diagnostic for acceptance testing and console environment diagnosis. The test command runs one pass of the tests. To run tests concurrently and indefinitely, use the sys_exer command.
Error Reporting
cat el	Displays the console event log.
more el	Displays the console event log one screen at a time.
Extended Testing and Troubleshooting
memexer	Exercises memory by running a specific number of memory tests. The tests are run in the background.
memory	Runs memory exercises each time the command is entered. The tests are run in the background.
net -ic	Initializes the MOP counters for the specified Ethernet port.
net -s	Displays the MOP counters for the specified Ethernet port.
sys_exer	Exercises the core system. Runs tests concurrently.
Loopback Testing
test -lb	Conducts loopback tests for COM2 and the parallel port in addition to quick core system tests.
sys_exer -lb	Conducts loopback tests for COM2 and the parallel port in addition to core system tests.
Diagnostic-Related Commands
kill	Terminates a specified process.
kill_diags	Terminates all currently executing diagnostics.
show_status	Reports the status of currently executing test/exercisers.


Command Reference

This section provides detailed information on the following diagnostic and related commands:

test

sys_exer

cat el and more el

memexer

memory

net -s

net -ic

kill and kill_diags

show_status


test

The test command runs firmware diagnostics for the entire core system. The tests are run concurrently in the background. Fatal errors are reported to the console terminal.

The cat el command should be used in conjunction with the test command to examine test/error information reported to the console event log.

The tests are run once. To run the tests concurrently and indefinitely, use the sys_exer command.

Note:  By default, no write tests are performed on disk and tape drives. Media must be installed to test the floppy drive and tape drives. A loopback connector is required for the COM2 (9-pin loopback connector, 12-27351-01) port.

The test command does not test the DNSES, TGA card, or reflective memory option, as well as third party options.

When using the test command after shutting down an operating system, you must initialize the system to a quiescent state. Enter the following commands at the SRM console:

>>> set auto_action halt

>>> init

 .

 .

 .

>>> test

After testing is completed, set the auto_action environment variable to its previous value (usually, boot) and use the Reset button to reset the system.

To terminate the tests, use the kill command to terminate and individual diagnostic or the kill_diags command to terminate all diagnostics. Use the show_status display to determine the process ID when terminating an individual diagnostic test.

Note:  A serial loopback connector (12-27351-01) must be installed on the COM2 serial port for the kill_diags command to successfully terminate system tests.

The test script tests devices in the following order:

1.	Console loopback tests if lb argument is specified: COM2 serial port and parallel port.

2.	Network external loopback tests for E*A0. This test requires that the Ethernet port be terminated or connected to a live network; otherwise, the test will fail.

3.	Memory tests (one pass).

4.	Read-only tests:  DK* disks, DR* disks, DU* disks, MK* tapes, DV* floppy.

5.	VGA console tests.  These tests are run only if the console environment variable is set to serial." The VGA console test displays rows of the letter "H". or Digital.

Synopsis:

test [lb]

Argument:

[lb]	The loopback option includes console loopback tests for the COM2 serial port and the parallel port during the test sequence.
Note:  If you are running the Windows NT operating system, you need to switch to the SRM console in order to enter the test command.

Note:  To examine test/error information, examine the console event log using the cat el command.

Example 1

The system is tested, and the tests complete successfully.

>>> test

Requires diskette and loopback connectors on COM2 and parallel port

type kill_diags to halt testing

type show_status to display testing progress

type cat el to redisplay recent errors

Testing COM2 port

Setting up network test, this will take about 20 seconds

Testing the network

  48 Meg of System Memory

  Bank 0 = 16 Mbytes(4 MB Per Simm) Starting at 0x00000000

  Bank 1 = 16 Mbytes(4 MB Per Simm) Starting at 0x01000000

  Bank 2 = 16 Mbytes(4 MB Per Simm) Starting at 0x02000000

  Bank 3 = No Memory Detected

Testing the memory

Testing parallel port

Testing the SCSI Disks

Non-destructive Test of the Floppy started dka400.4.0.6.0 has no media present or is disabled via the RUN/STOP switch

file open failed for dka400.4.0.6.0

Testing the VGA(Alphanumeric Mode only)

Printer offline

file open failed for para

>>> show_status

ID -------	Program -------	Device ------	Pass ----	Hard/Soft -----	Bytes Written -------	Bytes Read -------
00000001	idle	system	0	0	0	0
0000002d	exer_kid	tta1	0	0	1	0
0000003d	nettest	era0.0.0.2.1	43	0	1376	1376
00000045	memtest	memory	7	0	424673280	424673280
00000052	exer_kid	dka100.1.0.6	0	0	0	2688512
00000053	exer_kid	dka200.2.0.6	0	0	0	922624
>>> kill_diags

>>>

Example 2

The system is tested, and the system reports a fatal error message. No network server responded to a loopback message. Ethernet connectivity on this system should be checked.

>>> test

Requires diskette and loopback connectors on COM2 and parallel port

type kill_diags to halt testing

type show_status to display testing progress

type cat el to redisplay recent errors

Testing COM2 port

Setting up network test, this will take about 20 seconds

Testing the network

*** Error (era0), Mop loop message timed out from: 08-00-2b-3b-42-fd

*** List index: 7 received count: 0 expected count 2

>>>


sys_exer

The sys_exer command runs firmware diagnostics for the entire core system. The same tests that are run using the test command are run with sys_exer, only these tests are run concurrently and in the background. Nothing is displayed unless an error occurs.

Note:  The diagnostics started by the sys_exer command require extra memory resources. The init command must be used to reconfigure memory before booting and operating the system.

Because the sys_exer tests are run concurrently and indefinitely (until you stop them with the init command), they are useful in flushing out intermittent hardware problems.

Note:  By default, no write tests are performed on disk and tape drives. Media must be installed to test the floppy drive and tape drives.

Certain memory errors that are reported by the OCP may not be reported by the ROM-based diagnostics. Always check the power-up/diagnostic display before running diagnostic commands.

Synopsis:

sys_exer [lb]

Arguments:

[lb]	The loopback option includes console loopback tests for the COM2 serial port and the parallel port during the test sequence.
Examples:

>>> sys_exer

Default zone extended at the expense of memzone.

Use INIT before booting

Exercising the Memory

Exercising the DK* Disks(read only)

Exercising the Floppy(read only)

Testing the VGA (Alphanumeric Mode only)

Exercising the EWA0 Network

Exercising the EWB0 Network

Type "init" in order to boot the operating system

Type "show_status" to display testing progress

Type "cat el" to redisplay recent errors

>>> show_status

ID	Program	Device	Pass	Hard/Soft	Bytes Written	Bytes Read
00000001	idle	system	0	0       0	0	0
0000550b	memtest	memory	193	0       0	7243563008	7243563008
00005514	memtest	memory	192	0       0	7222591488	7222591488
0000551d	exer_kid	dka100.1.0.2	0	0       0	0	2461184
0000551e	exer_kid	dka400.4.0.2	0	0       0	0	2460672
00005533	exer_kid	dva0.0.0.100	0	0       0	0	2311168
00005608	nettest	ewa0.0.0.200	1131	0       1	12160512	12159632
00005746	nettest	ewb0.0.0.13	1127	0       2	12116624	12115280
>>> init

ff.fe.fd.fc.fb.fa.f9.f8.f7.f6.f5.ef.df.ee.f4.

.

.

.

>>>


cat el and more el

The cat el and more el commands display the current contents of the console event log. Status and error messages (if problems occur) are logged to the console event log at power-up, during normal system operation, and while running system tests.

Standard error messages are indicated by asterisks (***).

When cat el is used, the contents of the console event log scroll by. You can use the Ctrl/S combination to stop the screen from scrolling and Ctrl/Q to resume scrolling.

The more el command allows you to view the console event log one screen at a time.

Synopsis:

cat el

or

more el

Example

The following example shows an abbreviated console event log that contains a standard error message indicating that the keyboard is not plugged in or is not working.

>>> cat el

*** keyboard not plugged in...

ff.fe.fd.fc.fb.fa.f9.f8.f7.f6.f5.

ef.df.ee.f4.ed.ec.eb.ea.e9.e8.e7.e6.port pka0.7.0.6.0 initialized,

scripts are at 4f7faa0

resetting the SCSI bus on pka0.7.0.6.0

port pkb0.7.0.12.0 initialized, scripts are at 4f82be0

resetting the SCSI bus on pkb0.7.0.12.0

e5.e4.e3.e2.e1.e0.

V1.1-1, built on Nov  4 1994 at 16:44:07

device dka400.4.0.6.0 (RRD43) found on pka0.4.0.6.0

>>>


memexer

The memexer command tests memory by running a specified number of memory exercisers. The exercisers are run in the background and nothing is displayed unless an error occurs. Each exerciser tests all available memory in twice the backup cache size blocks for each pass.

To terminate the memory tests, use the kill command to terminate an individual diagnostic or the kill_diags command to terminate all diagnostics. Use the show_status display to determine the process ID when terminating an individual diagnostic test.

Synopsis:

memexer [number]

Arguments:

[number]	Number of memory exercisers to start. The default is 1.
	The number of exercisers, as well as the length of time for testing, depends on the context of the testing. Generally, running three to five exercisers for 15 minutes to 1 hour is sufficient for troubleshooting most memory problems.
Examples:

Example with no errors.

>>> memexer 4

>>> show_status

ID	Program	Device	Pass	Hard/Soft	Bytes Written	Bytes Read
00000001	idle	system	0	0    0	0	0
000000c7	memtest	memory	3	0    0	635651584	62565154
000000cc	memtest	memory	2	0    0	635651584	62565154
000000d0	memtest	memory	2	0    0	635651584	62565154
000000d1	memtest	memory	3	0    0	635651584	62565154
>>> kill_diags

>>>

The following is an example with a memory compare error indicating bad SIMMs. In most cases, the failing bank and SIMM position are specified in the error message. If the failing SIMM information is not provided, use the memory command to isolate a failing SIMM.

>>> memexer 3

*** Hard Error - Error #41 - Memory compare error

Diagnostic Name      ID        Device  Pass  Test  Hard/Soft 11-JUN-1996

memtest        00000193          brd0   114     1     1    0    12:00:01

Expected value:          25c07

Received value:          35c07

Failing addr:            a11848

*** End of Error ***

>>> kill_diags

>>>


memory

The memory command tests memory by running a memory exerciser each time the command is entered. The exercisers are run in the background and nothing is displayed unless an error occurs.

The number of exercisers, as well as the length of time for testing, depends on the context of the testing. Generally, running three to five exercisers for 15 minutes to 1 hour is sufficient for troubleshooting most memory problems.

To terminate the memory tests, use the kill command to terminate an individual diagnostic or the kill_diags command to terminate all diagnostics. Use the show_status display to determine the process ID when terminating an individual diagnostic test.

Synopsis:

memory

Example with no errors

>>> memory

>>> memory

>>> memory

>>> show_status

ID --------	Program -------	Device -----------	Pass ----	Hard/Soft -----	Bytes Written -------	BytesRead -------
00000001	idle	system	0	0    0	0	0
0000006b	memtest	memory	1	0    0	53477376	53477376
00000071	memtest	memory	1	0    0	31457280	31457280
00000077	memtest	memory	1	0    0	24117248	24117248
>>> kill diags

>>>

Example with a memory compare error indicating bad SIMMs

>>> memory

>>> memory

>>> memory

*** Hard Error - Error #41 - Memory compare error

Diagnostic Name      ID       Device  Pass  Test  Hard/Soft  11-JUN-1996

memtest        00000193         brd0   114     1     1    0    12:00:01

Expected value:         25c07

Received value:         35c07

Failing addr:          a11848

*** End of Error ***

>>> kill diags

>>>

To find the failing bank, compare the failing address (a11848 in this example) with the show memory display or memory portion of the show config command display:

1.	Banks with no memory present are eliminated as possible failing banks.

2.	If the failing address is greater than the bank starting address, but less than the starting address for the next bank, then the failing SIMM is within this bank. Bank 0 in the example using failing address a11848 and the following memory display.

>>> show memory

Memory

32 Meg of System Memory

Bank 0 = 16 Mbytes (4MB per SIMM) Starting at 0x00000000

Bank 1 = 16 Mbytes (4MB per SIMM) Starting at 0x01000000

Bank 2 = No Memory Detected

Bank 3 = No Memory Detected

>>>

To determine the failing SIMM, match the least significant nibble of the failing address and the bit range in which the bad data is received to the failing SIMM using the table below.

Failing Address Least Significant Nibble	Data Miscompare in Bit Range	Falling SIMM
0 or 8	bits 15:0	0
0 or 8	bits 31:16	1
4 or C	bits 15:0	2
4 or C	bits 31:16	3
In the example the least significant nibble is the failing address is 8 (a11848). The expected data value was 25c07, the received value was 35c07.

The data miscompare occurred in bits 16-19 or within bits 31:16, therefore the failing SIMM would be SIMM 1.


net -s

The net -s command displays the MOP counters for the specified Ethernet port.

Synopsis:

net -s ewa0

Example

>>> net -s ewa0

Status counts:

ti: 72 tps: 0 tu: 47 tjt: 0 unf: 0 ri: 70 ru: 0

rps: 0 rwt: 0 at: 0 fd: 0 lnf: 0 se: 0 tbf: 0

tto: 1 lkf: 1 ato: 1 nc: 71 oc: 0

MOP BLOCK:

 Network list size: 0

MOP COUNTERS:

Time since zeroed (Secs): 42

TX:

 Bytes: 0 Frames: 0

 Deferred: 1 One collision: 0 Multi collisions: 0

TX Failures:

 Excessive collisions: 0 Carrier check: 0 Short circuit: 71

 Open circuit: 0 Long frame: 0 Remote defer: 0

 Collision detect: 71

RX:

 Bytes: 49972 Frames: 70

 Multicast bytes: 0 Multicast frames: 0

RX Failures:

 Block check: 0 Framing error: 0 Long frame: 0

 Unknown destination: 0 Data overrun: 0 No system buffer: 0

 No user buffers: 0

>>>


net -ic

The net -ic command initializes the MOP counters for the specified Ethernet port.

Synopsis:

net -ic ewa0

Example

>>> net -ic ewa0

>>> net -s ewa0

Status counts:

ti: 72 tps: 0 tu: 47 tjt: 0 unf: 0 ri: 70 ru: 0

rps: 0 rwt: 0 at: 0 fd: 0 lnf: 0 se: 0 tbf: 0

tto: 1 lkf: 1 ato: 1 nc: 71 oc: 0

MOP BLOCK:

 Network list size: 0

MOP COUNTERS:

Time since zeroed (Secs): 3

TX:

 Bytes: 0 Frames: 0

 Deferred: 0 One collision: 0 Multi collisions: 0

TX Failures:

 Excessive collisions: 0 Carrier check: 0 Short circuit: 0

 Open circuit: 0 Long frame: 0 Remote defer: 0

 Collision detect: 0

RX:

 Bytes: 0 Frames: 0

 Multicast bytes: 0 Multicast frames: 0

RX Failures:

 Block check: 0 Framing error: 0 Long frame: 0

 Unknown destination: 0 Data overrun: 0 No system buffer: 0

 No user buffers: 0

>>>


kill and kill_diags

The kill and kill_diags commands terminate diagnostics that are currently executing.

Note:  A serial loopback connector (12-27351-01) must be installed on the COM2 serial port for the kill_diags command to successfully terminate system tests.

The kill command terminates a specified process.

The kill_diags command terminates all diagnostics.

Synopsis:

kill_diags

kill [PID . . . ]

Argument:

[PID. . .]	The process ID of the diagnostic to terminate. Use the show_status command to determine the process ID.


show_status

The show_status command reports one line of information per executing diagnostic. The information includes ID, diagnostic program, device under test, error counts, passes completed, bytes written, and bytes read.

Many of the diagnostics run in the background and provide information only if an error occurs. Use the show_status command to display the progress of diagnostics.

The following command string is useful for periodically displaying diagnostic status information for diagnostics running in the background:

>>> while true;show_status;sleep n;done

Where n is the number of seconds between show_status displays.

Example

>>>show_status

ID  1 -------	Program  2 -------	Device  3 ------	Pass  4 ----	Hard/Soft  5 -----	Bytes Written  6 -------	Bytes Read  7 -------
00000001	idle	system	0	0    0	0	0
0000006f	memtest	memory	1	0    0	35651584	35651584
00000070	memtest	memory	1	0    0	35651584	35651584
00000077	memtest	memory	1	0    0	37748736	37748736
0000007e	exer_kid	dka0.0.0.1.0	0	0    0	0	69120
0000007f	exer_kid	dka600.6.0.1	0	0    0	0	66560
00000093	exer_kid	dva0.0.0.0.1	0	0    0	0	0
000000d5	nettest	era0.0.0.2.1	13	0    0	308672	308672
1.	Process ID

2.	Program module name

3.	Device under test

4.	Diagnostic pass count

5.	Error count (hard and soft):  Soft errors are not usually fatal; hard errors halt the system or prevent completion of the diagnostics.

6.	Bytes successfully written by diagnostic.

7.	Bytes successfully read by diagnostic.


Acceptance Testing and Initialization

Perform the acceptance testing procedure listed below after installing a system or whenever adding or replacing the following:

CPU daughter board

Memory modules

Motherboard

Storage devices

EISA or PCI options

1.	Run the RBD acceptance tests using the test or sys_exer command.

2.	If you have added, moved, or removed an EISA option, run the EISA Configuration Utility (ECU).

3.	Bring up the operating system.

4.	Run DEC VET to test that the operating system is correctly installed.


DEC VET

Digital's DEC Verifier and Exerciser Tool (DEC VET) software is a multipurpose system maintenance tool that performs exerciser-oriented maintenance testing.  DEC VET runs on OpenVMS, Digital UNIX, and Windows NT operating systems. DEC VET consists of a manager and exercisers.  The DEC VET manager controls the exercisers.  The exercisers test system hardware and the operating system.

DEC VET supports various exerciser configurations, ranging from a single device exerciser to full system loading, that is, simultaneous exercising of multiple devices.

Refer to the DEC Verifier and Exerciser Tool Users Guide (AA-PTTMD-TE) for instructions on running DEC VET.


Error Log Analysis

This section provides information on how to interpert error logs reported by the operating system.

The following topics are covered:

Fault Detection and Reporting

Machine Check/Interrupts

Error Logging and Event Log Entry Format

Event Record Translation


Fault Detection and Reporting

The following table provides a summary of the fault detection and correction components of AlphaStation 600A 5/500 systems.

Generally, PALcode handles exceptions as follows:

•	The PALcode determines the cause of the exception.

•	If possible, it corrects the problem and passes control to the operating system for reporting before returning the system to normal operation.

•	If error/event logging is required, control is passed through the system control block (SCB) to the appropriate exception handler.

Component	Fault Detection/Correction Capability
KN22A Processor Module
DECchip 21064 and 21064A microprocessors	Contains error detection and correction (EDC) logic for data cycles. There are check bits associated with all data entering and exiting the 21064(A) microprocessor. A single-bit error on any of the four longwords being read can be corrected (per cycle). A double-bit error on any of the four longwords being read can be detected (per cycle).
Backup cache (B-cache)	EDC check bits on the data store; and parity on the tag address store and tag control store.
Memory Subsystem
Memory SIMMs	EDC logic protects data by detecting and correcting data cycle errors. A single-bit on any of the four longwords can be corrected (per cycle). A double-bit error on any of the four longwords being read can be detected (per cycle).
System Motherboard
SCSI controller EISA-to-PCI bridge chip PCI-to-PCI bridge chip	SCSI data parity is generated. PCI data parity is generated. PCI data parity is generated.


Machine Check/Interrupts

The exceptions that result from hardware system errors are called machine check/interrupts. They occur when a system error is detected during the processing of a data request. There are four types of machine check/interrupts related to system events:

Processor Machine Check (SCB 670)

System Machine Check (SCB 660)

Processor-Corrected Machine Check (SCB 630)

System-Corrected Machine Check (SCB 620)

Note:  The system control block (SCB) vector through which PALcode transfers controls to the operating system is shown in parentheses.

During the error handling process, errors are first handled by the appropriate PALcode error routine and then by the associated operating system error handler.


Processor Machine Check (SCB: 670)

Processor machine check errors are fatal system errors that will result in a system crash. The error handling code for these errors are common across all platforms using the DECchip 21064 and DECchip 21064A microprocessors.

•	DECchip 21064 or DECchip 21064A microprocessor detected one or more of the following uncorrectable data errors:

--Uncorrectable B-cache data error

--Uncorrectable memory data error

•	A B-cache tag or tag control parity error occurred

•	Hard error was asserted in response to:

--Double-bit Istream ECC error

--Double-bit Dstream ECC error

--System transaction terminated with CACK_HERR

--I-cache parity errors

--D-cache parity errors


System Machine Check (SCB:660)

A system machine check is a system detected error, external to the DECchip microprocessor and possibly not related to the activities of the CPU. These errors are specific to AlphaStation 600A 5/500 systems.

Fatal errors:

•	System overtemperature failure

•	System complete power supply failure

The power supply number is called out in the register: power supply 1 is the bottom supply; power supply 2 is the top supply.

•	System fan failure

•	I/O read/write retry timeout

•	DMA data parity error

•	I/O data parity error

•	Slave abort PCI transaction

•	DEVSEL not asserted

•	Uncorrectable read error

•	Invalid page table lookup (scatter gather)

•	Memory cycle error

•	B-cache tag address parity error

•	B-cache tag control parity error

•	Non-existent memory error

•	ESC NMI:IOCHK


Processor-Corrected Machine Check (SCB: 630)

Processor-corrected machine checks are caused by B-cache errors that are detected and corrected by the DECchip 21064 or 21064A microprocessor. These are nonfatal errors and result in an error log entry. The error handling code for these errors are common across all platforms using the DECchip 21064 and 21064A microprocessors.

•	Single-bit Istream ECC error

•	Single-bit Dstream ECC error

•	System transaction terminated with CACK_SERR


System-Corrected Machine Check (SCB: 620)

System-corrected machine check errors are AlphaStation 600A 5/500-specific correctable errors. These errors result in the generation of the correctable machine check logout frame:

•	Correctable read errors

•	Single power supply failure when operating with redundant power supplies

•	System overtemperature warning


Error Logging and Event Log Entry Format

The Digital UNIX and OpenVMS error handlers can generate several entry types. All error entries, with the exception of correctable memory errors, are logged immediately. Entries can be of variable length based on the number of registers within the entry.

Each entry consists of an operating system header, several device frames, and an end frame. Most entries have a PAL-generated logout frame, and may contain frames for CPU, memory, and I/O.


Event Record Translation

Systems running Digital UNIX and OpenVMS operating systems use the DECevent management utility to translate events into ASCII reports derived from system event entries (bit-to-text translations).

The DECevent utility has the following features relating to the translation of events:

•	Translating event log entries into readable reports

•	Selecting input and output sources

•	Filtering input events

•	Selecting alternate reports

•	Translating events as they occur

•	Maintaining and customizing the user environment with the interactive shell commands

Note:  Microsoft Windows NT does not currently provide bit-to-text translation of system errors.

The following topics summerize the command used to translate the error log information for OpenVMS and Digital UNIX operating systems using DECevent:

OpenVMS Alpha Translation Using DECevent

Digital UNIX Translation Using DECevent


OpenVMS Alpha Translation Using DECevent

The kernel error log entries are translated from binary to ASCII using the DIAGNOSE command. To invoke the error log utility, enter the DCL command DIAGNOSE.

Format:

DIAGNOSE/TRANSLATE [qualifier] [,...] [infile[,...]]

Example:

$ DIAGNOSE/TRANSLATE/SINCE=14-jun-1995

For more information on generating error log reports using DECevent, refer to the DECevent Translation and Reporting Utility for OpenVMS Alpha, User and Reference Guide, AA-Q73KC-TE.

System faults can be isolated by examining translated system error logs or using the DECevent Analysis and Notification Utility. Refer to the DECevent Analysis and Notification Utility for OpenVMS Alpha, User and Reference Guide, AA-Q73LC-TE, for more information.


Digital UNIX Translation Using DECevent

The kernel error log entries are translated from binary to ASCII using the dia command. To invoke the DECevent utility, enter the dia command.

Format:

dia [-a -f infile[...]]

Example:

% dia -t s:14-jun-1995:10:00

For more information on generating error log reports using DECevent, refer to the DECevent Translation and Reporting Utility for Digital UNIX, User and Reference Guide, AA-QAA3-TE.

System faults can be isolated by examining translated system error logs or using the DECevent Analysis and Notification Utility. Refer to the DECevent Analysis and Notification Utility for Digital UNIX, User and Reference Guide, AA-QAA4A-TE, for more information.


Glossary

 - A -

AlphaBIOS

ASIC

 - B -

B-cache

boot block

BIU

bus

 - C -

cache memory

CAS

central processing unit (CPU)

checksum

CIA

control and status register (CSR)

control, input/output, and addressing (CIA)

CPU

CSR

 - D -

DAC

data switch (DSW)

DCSR

diagnostic read-only memory (DROM)

direct memory access (DMA)

dirty parity

DMA

DROM

 - E -

ECC

ECL

EDSR

EISA

 - F -

flashROM

 - G -

GB

GRU

 - H -

hard error (HERR)

 - I -

IDE

interrupt

interrupt masking

I/O

IOA

IRQ

ISA

 - J -

jumper

 - K -

Kb

KB

 - L -

LED

 - M -

mask

maskable interrupt

Mb

MB

MHz

MMB

 - N -

NMI

nonmaskable interrupt (NMI)

nonvolatile random-access memory (NVRAM)

ns

NVRAM

 - O -

OCP

 - P -

page table entry (PTE)

parity error (PERR)

PCEB

PEAR

peripheral component interconnect (PCI)

PERR

PTE

 - Q -

 - R -

RASType hotspot text in this box

RISC

read-only memory (ROM)

 - S -

SAC

scatter/gather

SCSI

SEAR

SERR

SIMM

small computer system interface (SCSI)

soft error (SERR)

SRM

SROM

system reference manual (SRM)

 - T -

TLB

 - U -

 - V -

victim

 - W -

 - X -

 - Y -

 - Z -


CPU
central processing unit (CPU)

The main unit of a computer that contains the circuits controlling interpretation and execution of instructions; the central processing unit holds the main storage, arithmetic unit, and special registers.


DMA
direct memory access (DMA)

A method of addressing memory, a device, or a location by its actual value; in other words, the actual value is not translated or processed prior to use.


DROM
diagnostic read-only memory (DROM)

In the AlphaStation 600A 5/500 system, the portion of code used for power-on self-tests (POSTs).  The DROM code executes after serial ROM (SROM) code loads it successfully.  Following successful completion of POSTs, the DROM code loads and starts the appropriate flashROM (either AlphaBIOS or SRM console firmware).  Alternatively, if a flashROM error occurs, the DROM code attempts to load from the diskette drive.


DSW
data switch (DSW)

An ASIC component of the AlphaStation 600A 5/500 system; the four DSW ASICs provide the data path between the EV5, memory, and the CIA ASIC (for PCI data).


EISA

Abbreviation for extended industry-standard architecture.


flashROM

In the AlphaStation 600A 5/500 system, the read-only memory that contains console firmware; four 256-KB flashROMs yield a total size of 1 MB.  Certain conditions permit writing to the flashROMs, allowing field updates to the firmware.


GB

A suffix to a numerical value that indicates size in gigabytes (for example, 1 GB); a gigabyte equals 1,073,741,824 bytes.


IRQ

A high-priority signal representing an interrupt request that informs another task of some significant event.


ISA

Abbreviation for industry-standard architecture.


I/O

A reference to input and output functions.


Kb

A suffix to a numerical value that indicates size in kilobits (for example, 512 Kb); a kilobit equals 1024 bits.


KB

A suffix to a numerical value that indicates size in kilobytes (for example, 640 KB); a kilobyte equals 1024 bytes.


LED

Abbreviation for light-emitting diode.


Mb

A suffix to a numerical value that indicates size in megabits (for example, 10 Mb); a megabit equals 1,048,576 bits.


MB

A suffix to a numerical value that indicates size in megabytes (for example, 550 MB); a megabyte equals 1,048,576 bytes.


MHz

A suffix to a numerical value that indicates frequency in megahertz.


ns

A suffix to a numerical value that indicates speed in nanoseconds (for example, 22 ns).


NVRAM
nonvolatile random-access memory (NVRAM)

Random-access memory that retains its contents, even while the system is turned off.  In the AlphaStation 600A 5/500 system, the NVRAM stores setup information for the console firmware--either AlphaBIOS or system reference manual (SRM).


PCI
peripheral component interconnect (PCI)

The connection permitting communication between units (distinct from the CPU and physical memory) that can provide the system with input or accept output from it.


RISC

An abbreviation for reduced instruction set computing.


ROM
read-only memory (ROM)

Memory that cannot be altered in normal use of the system--usually a small memory that contains often-used instructions such as microprograms or system software (for example, firmware).


SCSI
small computer system interface (SCSI)

In the AlphaStation 600A 5/500 system, an I/O bus that provides the interface between the system and peripheral devices.


SIMM

Abbreviation for single inline memory module.


SRM
system reference manual (SRM)

In the AlphaStation 600A 5/500 system, the console firmware that supports the Digital UNIX and OpenVMS operating systems.


SROM
serial read-only memory (SROM)

In the AlphaStation 600A 5/500 system, the portion of read-only memory that contains the code to perform power-up initialization and configuration of the central processing unit (CPU) and the input/output (I/O) system.


PCEB

Abbreviation for PCI-to-EISA bridge.


victim

A block of cache-memory data replaced by new data.


ASIC

Abbreviation for application-specific integrated circuit.  The AlphaStation 600A 5/500 system uses six ASICs:

•	Four data switch (DSW) ASICs

•	One control, input/output, and addressing (CIA) ASIC

•	One miscellaneous ASIC called the GRU ASIC


B-cache

In the AlphaStation 600A 5/500 system, a direct-mapped, write-back, ECC-protected plug-in secondary cache partitioned across three required SIMMs.


CIA

Abbreviation for control, input/output, and addressing--an ASIC component of the AlphaStation 600A 5/500 system.  The CIA ASIC accepts the address and command from the EV56 and drives the memory array with the address, row-address selects (RASs), and column-address selects (CASs).  It also provides an interface to the PCI bus.


GRU

In the AlphaStation 600A 5/500 system, a miscellaneous ASIC on the IOD bus that handles both the PCI-interrupt logic and the memory/cache presence-detection logic and generates the data bus used to access the flashROMs.


interrupt

A break in the usual flow of a system or program to perform an external task.


jumper

A short length of wire used either to compete a circuit temporarily or to bypass a circuit.


OCP

Abbreviation for operator control panel.


IOA

Abbreviation for I/O address.


ECC

Abbreviation for error-correction code.


cache memory

A small, high-speed memory placed between slower main memory and the processor.  A cache increases effective memory-transfer rates and processor speed.  It contains copies of data recently used by the processor and fetches several bytes of data from memory in anticipation that the processor will access the next sequential series of bytes.


CAS

An abbreviation for the column-address select signal.


RAS

An abbreviation for the row-address select signal.


page table entry (PTE)

An entry in the process-page table that describes the location and status of a process page.  In a global page table, a PTE describes the location and status of a page of a global section.  In the system page table, a PTE describes the status and location of a page of the operating system.


TLB

An abbreviation for translation lookaside buffer.


SERR
soft error (SERR)

A recoverable error.  A SERR is a wire-OR'd signal that can be driven by several devices at any one time.  SERR reports address parity errors and data parity errors on special cycles; it is sent to the CPU as a nonmaskable interrupt (NMI).


HERR
hard error (HERR)

A nonrecoverable error.


PERR
parity error (PERR)

With even parity, the number of 1's in a set of binary data should be even; with odd parity, the number of 1's should be odd.  Exceptions to either parity type indicate a parity error and generate a PERR signal.  PERR reports data parity errors for all transactions except special-cycle commands; targets use PERR to signal data parity errors to the master device.  (Only one device at a time can drive PERR.)


bus

A flat, flexible cable consisting of many transmission lines (or wires) that interconnect system components to provide communication paths for addresses, data, and control information.


BIU

Abbreviation for bus interface unit.


dirty parity

Parity that contains errors, but is allowed (for example, to troubleshoot data-transmission problems).


DAC

Abbreviation for dual address cycle.


SAC

Abbreviation for single address cycle.


MMB

Abbreviation for memory motherboard, a deprecated term for system board.


ECL

Abbreviation for emitter-coupled logic.


CSR
control and status register (CSR)

A register that resides in the processor's I/O space and contains control and status data pertaining to a device or controller.


S/G
scatter/gather

Pertaining to the ability to transfer data in one I/O operation either from discontiguous pages in memory to contiguous blocks on disk or from contiguous blocks on disk to discontiguous pages in memory.


checksum

A sum of digits or bits used to verify the validity of a number or an operation.


PEAR

Abbreviation for PCI Error Address register.


EDSR

Abbreviation for Error and Diagnostic Status register.


DCSR

Abbreviation for Diagnostic control and status register.


SEAR

Abbreviation for sysBus Error Address register.


NMI
nonmaskable interrupt (NMI)

Nonmaskable interrupts (NMIs) are interrupts that cannot be ignored.  In the AlphaStation 600A 5/500 system, NMIs originate on the PCI/EISA bridge chip (for example, address parity errors on the PCI bus and parity errors on expansion modules plugged into the ISA bus).


mask

To disable or enable functions by writing specific bit patterns to a register.


interrupt masking

The method of defining whether a specified interrupt is ignored.


IDE

Abbreviation for internal drive electronics.


boot block

A block in a file of a system disk that contains a program for loading the operating system into memory.


AlphaBIOS

In the AlphaStation 600A 5/500 system, the console firmware that supports the Windows NT operating system.