Digital PDFs

XX-XXXXX-XX

2000

117 pages

Original

0.2MB

Document:	Lost document 26469
Order Number:	XX-XXXXX-XX
Revision:	000
Pages:	117
Original Filename:	http://sup.xenya.si/sup/info/digital/Alpha/digital_semiconductor_firmware/srmcons.pdf

OCR Text

Alpha SRM Console for
Alpha Microprocessor
Evaluation Boards
User’s Guide
Order Number: EC–QK8DE–TE

Revision/Update Information:

This document supersedes the
Alpha SRM Console for Alpha
Microprocessor Evaluation Boards
User’s Guide (EC–QK8DD–TE).

Software Version:

Alpha SRM Console version 4.5 or
higher

Operating Version:

Digital UNIX version 3.2B or higher
and OpenVMS version 6.2 or higher

Digital Equipment Corporation
Maynard, Massachusetts

June 1996
While Digital believes the information included in this publication is correct as of the date of
publication, it is subject to change without notice.
© Digital Equipment Corporation 1996. All rights reserved.
Printed in U.S.A.
AlphaGeneration, AlphaPC, DEC, DECchip, DECnet, DEC EtherWORKS, Digital, Digital
Semiconductor, OpenVMS, ThinWire, VMS, the AlphaGeneration design mark, and the
DIGITAL logo are trademarks of Digital Equipment Corporation.
Digital UNIX Version 3.2B for Alpha is a UNIX 93 branded product.
Digital Semiconductor is a Digital Equipment Corporation business.
IEEE is a registered trademark of The Institute of Electrical and Electronics Engineers, Inc.
NCR is a registered trademark of NCR Corporation.
OSF is a registered trademark of Open Software Foundation, Inc.
QLogic is a registered trademark and ISP is a trademark of QLogic Corporation.
UNIX is a registered trademark in the United States and other countries licensed exclusively
through X/Open Company Limited.
Windows NT is a trademark of Microsoft Corporation.
All other trademarks and registered trademarks are the property of their respective owners.

Contents
Preface ......................................................................................................... vii
Overview ...................................................................................................................vii

Introduction ............................................................................................... 1–1
Overview ................................................................................................................. 1–1
What Is the Alpha SRM Console?........................................................................... 1–2

Installing the Alpha SRM Console ........................................................... 2–1
Overview ................................................................................................................. 2–1
Updating Firmware in a Flash ROM....................................................................... 2–2
Updating the Flash ROM from Windows NT Firmware ........................................ 2–4
Updating the Flash ROM from the Debug Monitor Firmware .............................. 2–6
Updating the Flash ROM from the Alpha SRM Console ....................................... 2–7
Running the Firmware Update Utility .................................................................. 2–10
Switching to the Alpha SRM Console ................................................................. 2–12
Switching to the Alpha SRM Console from Windows NT Firmware ................... 2–13
Switching to the Alpha SRM Console from the Debug Monitor Firmware ......... 2–15
Updating Firmware in a UVPROM....................................................................... 2–16
Replacing the UVPROM ....................................................................................... 2–17

iii

Alpha SRM Console Commands .............................................................. 3–1
Overview ................................................................................................................. 3–1
Alpha SRM Console Conventions and Special Keys............................................... 3–2
Basic Alpha SRM Console Command Descriptions ............................................. 3–4
boot .......................................................................................................................... 3–5
deposit ..................................................................................................................... 3–8
examine ................................................................................................................. 3–12
fwupdate................................................................................................................ 3–15
set .......................................................................................................................... 3–16
show....................................................................................................................... 3–18
Environment Variables for Alpha SRM Console Commands ............................. 3–20
Environment Variable Descriptions ..................................................................... 3–21
ISA Configuration Utility ...................................................................................... 3–24
isacfg...................................................................................................................... 3–25
DEC EtherWORKS 3 Configuration Utility........................................................... 3–30
ewrk3_config ......................................................................................................... 3–31

Alpha SRM Console Diagnostic Commands .......................................... 4–1
Overview ................................................................................................................. 4–1
Alpha SRM Console Diagnostic Firmware Bootstrap Procedure ........................... 4–2
Alpha SRM Console Diagnostic Command Descriptions .................................... 4–5
exer .......................................................................................................................... 4–6
exer_read ............................................................................................................... 4–13
exer_write.............................................................................................................. 4–15
kill_diags ............................................................................................................... 4–17
memexer ................................................................................................................ 4–19
memtest................................................................................................................. 4–21
nettest.................................................................................................................... 4–26
iv

show_status........................................................................................................... 4–29
sys_exer ................................................................................................................. 4–31
test......................................................................................................................... 4–34
Environment Variables for Diagnostic Commands ............................................ 4–37
Environment Variable Descriptions ..................................................................... 4–38

Technical Support and Ordering Information ........................................A–1
Obtaining Technical Support..................................................................................A–1
Ordering Digital Semiconductor Products .............................................................A–2
Ordering Digital Semiconductor Literature ...........................................................A–4
Ordering Third-Party Literature............................................................................A–6

Index

Preface

Overview
This document describes the Alpha SRM Console firmware (also referred
to as the Alpha SRM Console) for the following Alpha microprocessor
evaluation and motherboard systems running the Digital UNIX and
OpenVMS operating systems:
•

AlphaPC 164 Motherboard (AlphaPC 164)

•

Alpha 21164 Evaluation Board (EB164)

•

Alpha 21066A Evaluation Board (EB66+)

•

AlphaPC 64 Evaluation Board (AlphaPC 64)

•

Alpha 21064 and Alpha 21064A PCI Evaluation Board (EB64+)

This document also describes how to install the Alpha SRM Console and
use the Alpha SRM Console commands.

Intended Audience and Prerequisites
This document provides Alpha SRM Console information for users to
bootstrap the Digital UNIX and OpenVMS operating systems and for
system designers to diagnose hardware problems on their Alpha
microprocessor-based designs. For information specific to installing and
booting the OpenVMS and Digital UNIX operating systems, see the
OpenVMS and Digital UNIX installation guides.
vii

Before you use this document, be familiar with your system’s hardware
configuration, and read your evaluation board’s user’s guide or
motherboard’s user’s manual.

Document Organization
This document is organized as follows:
•

Chapter 1 describes the Alpha SRM Console.

•

Chapter 2 describes how to install the Alpha SRM Console.

•

Chapter 3 describes some basic Alpha SRM Console commands,
associated environment variables, and the ISA configuration and
firmware update utilities.

•

Chapter 4 describes how to run the diagnostic firmware to test and
debug various system components.

•

Appendix A lists technical support and ordering information.

Document Conventions and Terms
The following conventions are used in this document:
Convention

Description

<angle_brackets>

A term between two angle brackets indicates
a placeholder in which the user must specify
a value.

>>>

Three angle brackets indicate the Alpha
SRM Console prompt.

boldface type

Boldface type indicates user input or a menu
selection.

{braces, commas}

Braces containing items separated by
commas indicate mutually exclusive items.

{braces | vertical | lines}

Braces containing items separated by vertical
lines indicate that more than one item may
be selected.

(Continued on the next page)
viii

(Continued)
Convention

Description

Ctrl/A

A slash between two key names indicates
that the two keys must be pressed
simultaneously.

EBxxx>

The name of an evaluation board followed by
an angle bracket indicates the debug monitor
command prompt.

Italic type

Italic type emphasizes important information
and indicates complete titles of manuals.

Note:

Notes provide additional information about a
topic.

Monospaced type

Text that the system displays is shown in
monospaced type.

[square_brackets]

Square brackets enclose optional
parameters, qualifiers, and values.

The following terms are used in this document:
This term...

Refers to...

EBSDK and Firmware
Update compact disc

The compact disc labeled Alpha Evaluation Boards
Software Developer’s Kit and Firmware Update.

Evaluation board

An Alpha microprocessor evaluation board.

Motherboard

An Alpha microprocessor motherboard.

System

All of the hardware and software components
associated with an Alpha microprocessor evaluation
board or motherboard.

Related Documentation
Documentation referenced in this document, such as the Alpha
Evaluation Boards Software Developer’s Kit and Firmware Update Read
Me First, can be found on the EBSDK and Firmware Update compact
disc.
See Appendix A for information about ordering related documentation.

Chapter 1
Introduction

Overview
This chapter describes the Alpha SRM Console and its features.

Introduction 1–1

What Is the Alpha SRM Console?
All evaluation board and motherboard systems that run the Digital
UNIX or OpenVMS operating system require the Alpha SRM Console.
This firmware resides in either a flash ROM or a UVPROM on the
evaluation board or motherboard.

Description
The Alpha SRM Console provides the following service functions:
•

Power-up diagnostics and initialization

•

Operator interface

•

Operating system bootstrap and restart

Features
The Alpha SRM Console provides the following features:
•

Event-driven executive, providing:
 Process management
 Memory management
 Symmetric multiprocessor support
 Memory-resident file system
 Interrupt and exception handling and error reporting

•

UNIX-style I/O and file system, providing:
 Generic model for byte-streamed devices or files
 Local or remote console connections through serial ports or
Ethernet

1–2 Introduction

 SCSI, FAT, MOP, and BOOTP protocol (class) drivers
 Device (port) drivers:

•

∗

Ethernet controllers: DS 21040 Ethernet LAN Controller for
PCI, DE205 (ISA)

∗

SCSI disk controllers: NCR810 (PCI), QLogic ISP1020 (PCI)

∗

Storage: NVRAM, flash ROM, physical memory, virtual
memory, GPRs, IPRs

Console shell, providing:
 Shell command parser with command line editing and recall
 boot, set, show, examine, deposit, start, stop, and continue shell
commands
 Online help

•

Diagnostics, exercisers, and test scripts, providing:
 CPU, cache, and memory initialization and configuration
 Device-specific self-test within the driver initialization
 Exercisers for memory, buses, and devices
 Test scripts for the evaluation board and motherboard systems,
subsystems, and individual devices
 Script creation and simple editing

Introduction 1–3

Chapter 2
Installing the Alpha SRM Console

Overview
Use the firmware update utility to install the Alpha SRM Console.
For evaluation boards and motherboards that have a flash ROM, you can
update the SRM firmware from the Windows NT firmware, the Debug
Monitor firmware, or the Alpha SRM Console. For evaluation boards
that have a UVPROM, you need to obtain a new UVPROM containing
the Alpha SRM Console and install it on the evaluation board.
After the Alpha SRM Console has been installed, you must restart the
evaluation board or motherboard to activate the new firmware.
Use the following table to determine the update procedure for your
evaluation board or motherboard:
To update firmware on an...

See this section...

AlphaPC 164
EB164
EB66+
AlphaPC 64

Updating Firmware in a Flash ROM

EB64+

Updating Firmware in a UVPROM

Installing the Alpha SRM Console 2–1

Updating Firmware in a Flash ROM

The firmware update utility is used to add or update the firmware in a
flash ROM on the AlphaPC 164, EB164, EB66+, and AlphaPC 64
evaluation board and motherboard systems. Depending on which
firmware you are using, this utility may be invoked from either a
diskette or a compact disc.
All evaluation board and motherboard systems that have a flash ROM
have the Windows NT firmware and the Debug Monitor firmware
factory installed. You can use either to add the Alpha SRM Console to
the flash ROM. Systems running the Alpha SRM Console version 4.1–1
or higher can also be used to update the flash ROM.
For the AlphaPC 164 motherboard system only, you can use the fail-safe
booter for updating the firmware if the firmware has been corrupted. See
the AlphaPC 164 Motherboard User’s Manual for instructions on how to
run the fail-safe booter.

2–2 Installing the Alpha SRM Console

To update the flash ROM, the update enable/disable jumper must be in
the enable position, which is the default. See the evaluation board’s
user’s guide or the motherboard’s user’s manual for more information
about jumper positions.

If your system is running...

Then see this section...

Windows NT firmware

Updating the Flash ROM from Windows NT
Firmware

Debug Monitor firmware

Updating the Flash ROM from the Debug
Monitor Firmware

Alpha SRM Console

Updating the Flash ROM from the Alpha
SRM Console

Installing the Alpha SRM Console 2–3

Updating the Flash ROM from Windows NT Firmware
This section describes how to access and start the Windows NT firmware
update utility.

Windows NT Firmware Conventions
To select and choose different options in the menus, use the following
keys:
Key

Description

Arrow

The Arrow keys are used to select different options.

Enter

The Enter key is used to choose the highlighted option.

Escape

The Escape key is used to close a menu or cancel an operation.

Accessing the Windows NT Firmware Menus
When you power up your evaluation board or motherboard system, the
firmware displays a blue screen on the monitor, initializes the firmware
drivers, and displays the boot menu. The currently selected option in the
menu is highlighted.
If autoboot is enabled, to interact with the firmware menus, cancel
autoboot by pressing the Escape key before the timeout period expires.

Starting the Firmware Update Utility
The firmware update utility is used to update the firmware in a flash
ROM. If your evaluation board or motherboard has firmware prior to
Windows NT version 4.42, you must use a diskette to invoke the
firmware update utility. If your evaluation board or motherboard has
Windows NT firmware version 4.42 or higher, you can invoke the
firmware update utility from either a diskette or a compact disc.

2–4 Installing the Alpha SRM Console

To invoke the firmware update utility to update the firmware in a flash
ROM, follow this procedure:
1. Insert either a compact disc or a diskette into the appropriate drive:
•

Compact disc — If you are using Windows NT firmware
version 4.42 or higher and you want to run the firmware update
utility from a compact disc, insert the EBSDK and Firmware
Update compact disc into the CD–ROM drive.

•

Diskette — If you are using firmware prior to Windows NT
firmware version 4.42 or if you want to run the firmware update
utility from a diskette, insert the diskette that you have created
into drive A and verify that the CD–ROM drive does not contain
a compact disc.
Note: The firmware update utility is provided only on a
compact disc; a diskette is not provided. See the
Alpha Evaluation Boards Software Developer’s Kit and
Firmware Update Read Me First for information about
how to create a firmware update diskette.

2. Restart your evaluation board or motherboard system.
3. From the Boot menu, choose Supplementary menu....
4. From the Supplementary menu, choose Install new firmware.
Note: The firmware update utility will reinitialize some system
components; it may appear as if your system is restarting.
5. Proceed to the Running the Firmware Update Utility section.

Installing the Alpha SRM Console 2–5

Updating the Flash ROM from the Debug Monitor
Firmware
Use the firmware update utility to update the firmware in a flash ROM.

Using the Debug Monitor Firmware to Install the Alpha SRM Console
The firmware update utility can be invoked by the Debug Monitor
firmware only from a diskette. However, the firmware update utility is
provided only on a compact disc; a diskette is not provided. See the
Alpha Evaluation Boards Software Developer’s Kit and Firmware
Update Read Me First for information about how to create a firmware
update diskette.
Starting the Firmware Update Utility
To start the firmware update utility after you have created your
firmware update diskette, follow this procedure:
1. Insert the firmware update diskette into drive A.
2. At the Debug Monitor firmware prompt, enter the following
command:
EBxxx>fwupdate
Note: • Versions prior to 2.0 of the Debug Monitor firmware do
not recognize the fwupdate command. If your Debug
Monitor firmware does not recognize the fwupdate
command, enter the following command at the Debug
Monitor firmware prompt:
EBxxx>flboot fwupdate.exe 900000
• The firmware update utility will reinitialize some system
components; it may appear as if your system is
restarting.
3. Proceed to the Running the Firmware Update Utility section.

2–6 Installing the Alpha SRM Console

Updating the Flash ROM from the Alpha SRM Console
Use the firmware update utility to update the firmware in a flash Rom.
Only Alpha SRM Console version 4.1–1 or higher can be used to install
the Alpha SRM Console into the flash ROM.

Starting the Firmware Update
The firmware update utility can be invoked by the Alpha SRM Console
from either a compact disc or a diskette. However, this utility is provided
only on a compact disc; a diskette is not provided. For information about
how to create a firmware update diskette, see the Alpha Evaluation
Boards Software Developer’s Kit and Firmware Update Read Me First.
The following procedures describe how to invoke the firmware update
utility from a compact disc and from a diskette.
Starting the Firmware Update Utility from a Compact Disc
To invoke the firmware update utility from a compact disc, follow this
procedure:
1. Insert the EBSDK and Firmware Update compact disc into the
CD–ROM drive.
2. Enter the following command to determine the unit number of the
drive for your CD–ROM device:
>>>show dev
A display appears showing information about the devices on your
system. In the following example, DKA400 is the CD–ROM device:
dka0.0.0.9.0
dka400.4.0.9.0
dva0.0.0.0.1
ewa0.0.0.7.0
pka0.7.0.9.0

DKA0
DKA400
DVA0
EWA0
PKA0

RZ26L 440C
RRD43 1084
08-00-2B-E2-B1-08
SCSI Bus ID 7

Installing the Alpha SRM Console 2–7

The numbers in the middle column are the unit numbers assigned to
each drive on your system, where:
•

The letters DK refer to a SCSI CD–ROM or disk device.

•

The third letter (A, B, C, D, or E) refers to the SCSI bus
designation. Refer to the hardware owner’s guide for more
details.

•

The numbers refer to the drive number.

3. Using the following syntax, enter the boot command to boot from a
compact disc.
boot -fl 0,a0 device-number
For example, to boot the system from CD–ROM drive number 4,
enter:
>>>boot -fl 0,a0 dka400
The following prompt appears for the bootfile path:
BOOTFILE:
4. Use the following table to determine the path that corresponds to the
firmware update utility for your evaluation board or motherboard.

If you have an...

Enter this path...

AlphaPC 164

[update.pc164]fwupdate.exe

EB164

[update.eb164]fwupdate.exe

EB66+

[update.eb66p]fwupdate.exe

AlphaPC 64

[update.pc64]fwupdate.exe

2–8 Installing the Alpha SRM Console

Note: The firmware update utility will reinitialize some system
components; it may appear as if your system is restarting.
5. Proceed to the Running the Firmware Update Utility section.

Starting the Firmware Update Utility from a Diskette
The firmware update utility is provided only on a compact disc; a
diskette is not provided. See the Alpha Evaluation Boards Software
Developer’s Kit and Firmware Update Read Me First for information
about how to create a firmware update diskette.
To start the firmware update utility from a firmware update diskette
that you have created, follow this procedure:
1. Insert the firmware update diskette into drive A.
2. At the Alpha SRM Console prompt, enter the following command:
>>>fwupdate
Note:

• Alpha SRM Console versions prior to version 4.4–1 do not
recognize the fwupdate command. For versions prior to
4.4–1, enter the following commands at the Alpha SRM
Console prompt:
>>>cat fat:fwupdate.exe/dva0 > pmem:900000
>>>stop -drivers
>>>jtopal 900000
• The firmware update utility will reinitialize some system
components; it may appear as if your system is
restarting.

3. Proceed to the Running the Firmware Update Utility section.

Installing the Alpha SRM Console 2–9

Running the Firmware Update Utility

To run the firmware update utility, follow this procedure:
1. From the Firmware Update menu, choose whichever selection
appears:

•

Update SRM Console Firmware

•

Update Firmware

2. When you are prompted to continue the update, choose Yes.
3. If the console selection does not match the firmware you flashed, you
will be prompted to update the console selection. If you are prompted
to update the console selection, choose Yes.
4. Restart the evaluation board or motherboard system.
Note: Depending on the version of firmware that you are
updating from, an error condition may occur. If an error
condition occurs, power cycle the system.
5. Observe the Alpha SRM Console prompt (>>>) on the terminal
attached to the COM1 serial port and on the graphics display unit.
Note: If you do not receive the Alpha SRM Console
prompt (>>>), press the Enter key on the terminal
attached to COM1 or on the console keyboard.

2–10 Installing the Alpha SRM Console

6. To specify the default console device, use the following Alpha SRM
Console commands:
To use the...

Enter these commands...

Terminal attached to the
COM1 serial port

>>>set console serial
>>>init

Graphics display unit

>>>set console graphics
>>>init

See Chapter 3 for more information about Alpha SRM Console
commands and environment variables.

Installing the Alpha SRM Console 2–11

Switching to the Alpha SRM Console

This section describes how to switch to the Alpha SRM Console from
either the Windows NT firmware or the Debug Monitor firmware on the
AlphaPC 64, EB164, EB66+, and EB64+.
Because the AlphaPC 164 supports only one firmware in the flash ROM,
you cannot switch to the Alpha SRM Console from either the
Windows NT firmware or the Debug Monitor firmware. For the AlphaPC
164 only, you must reprogram the flash ROM if you wish to run the
Alpha SRM Console instead of the Windows NT firmware or the Debug
Monitor firmware.

2–12 Installing the Alpha SRM Console

Switching to the Alpha SRM Console from Windows NT
Firmware
To switch to the Alpha SRM Console from the Windows NT firmware,
follow this procedure:
1. From the Boot menu, choose Supplementary menu....
2. From the Supplementary menu, choose Set up the system....
3. From the Setup menu, choose Machine specific setup....
4. From the Machine specific setup menu, choose one of the following
operating systems:
•

Switch to OpenVMS

•

Switch to Digital UNIX
Note: On some evaluation board systems, the Switch to
Digital UNIX option appears as Switch to OSF.

5. Restart your evaluation board or motherboard system.
6. Observe the Alpha SRM Console prompt (>>>) on the terminal
attached to the COM1 serial port and on the graphics display unit.
Note: If you do not see the Alpha SRM Console
prompt (>>>), press the Enter key on the terminal
attached to COM1 or on the console keyboard.

Installing the Alpha SRM Console 2–13

7. To specify the default console device, use the following Alpha SRM
Console commands:
To use the...

Enter these commands...

Terminal attached to the
COM1 serial port

>>>set console serial
>>>init

Graphics display unit

>>>set console graphics
>>>init

See Chapter 3 for more information about Alpha SRM Console
commands and environment variables.

2–14 Installing the Alpha SRM Console

Switching to the Alpha SRM Console from the Debug
Monitor Firmware
To switch to the Alpha SRM Console from the Debug Monitor firmware,
follow this procedure:
1. At the Debug Monitor firmware prompt, enter bootopt OSF or
bootopt VMS to switch to the Alpha SRM Console.
2. Power down the evaluation board or motherboard system.
3. Verify that the BOOT_OPTION jumper is inserted, which allows
booting of the Alpha SRM Console. See the evaluation board’s user’s
guide or motherboard’s user’s manual for more information about
jumper positions.
4. Restart the evaluation board or motherboard system.
5. Observe the Alpha SRM Console prompt (>>>) on the terminal
attached to the COM1 serial port and on the graphics display unit.
Note: If you do not see the Alpha SRM Console
prompt (>>>), press the Enter key on the terminal
attached to COM1 or on the console keyboard.
6. To specify the default console device, use the following Alpha SRM
Console commands:
To use the...

Enter these commands...

Terminal attached to
the COM1 serial port

>>>set console serial
>>>init

Graphics display unit

>>>set console graphics
>>>init

See Chapter 3 for more information about the Alpha SRM Console
commands and environment variables.

Installing the Alpha SRM Console 2–15

Updating Firmware in a UVPROM

Program the UVPROM to update the firmware on an EB64+.
The Alpha SRM Console is provided only on a compact disc;
a UVPROM is not provided. To program your own UVPROM, use
the .rom file or the .sr file on the EBSDK and Firmware Update compact
disc.
See the Alpha Evaluation Boards Software Developer’s Kit and
Firmware Update Read Me First for information about how to locate files
to program your UVPROM.

2–16 Installing the Alpha SRM Console

Replacing the UVPROM
To update the firmware on an evaluation board after you have a
programmed UVPROM, follow this procedure:
1. Turn off the power for the evaluation board system.
2. Locate and, noting the correct orientation of the UVPROM, remove
one of the UVPROMs from the evaluation board.
3. Using the correct orientation, insert the Alpha SRM Console
UVPROM.
4. Select the Alpha SRM Console UVPROM device with the UVPROM
select jumper as described in the evaluation board’s user’s guide.
5. Turn on the power for the evaluation board system.
6. Observe the Alpha SRM Console prompt (>>>) on the terminal
attached to the COM1 serial port and on the graphics display unit.
Note: If you do not receive the Alpha SRM Console
prompt (>>>), press the Enter key on the terminal
attached to COM1 or on the console keyboard.
7. To specify the default console device, use the following Alpha SRM
Console commands:
To use the...

Enter these commands...

Terminal attached to the
COM1 serial port

>>>set console serial
>>>init

Graphics display unit

>>>set console graphics
>>>init

See Chapter 3 for more information about Alpha SRM Console
commands and environment variables.

Installing the Alpha SRM Console 2–17

Chapter 3
Alpha SRM Console Commands

Overview
This chapter describes the Alpha SRM Console commands necessary to
set environment variables, configure the system, bootstrap the operating
system, and update the firmware. This chapter is divided into the
following sections:
•

Alpha SRM Console Conventions and Special Keys

•

Basic Alpha SRM Console Command Descriptions

•

Environment Variables for Alpha SRM Console Commands

•

ISA Configuration Utility

•

DEC EtherWORKS 3 Configuration Utility

Alpha SRM Console Commands 3–1

Alpha SRM Console Conventions and Special Keys
The following table lists the console conventions that apply to all Alpha
SRM Console commands:
Convention

Description

Backslash (\) at the end of a line

Continuation symbol to continue long
commands on the next line.

>>>

Console prompt.

Console prompt for line continuation.

Maximum command length

255 characters.

Multiple contiguous spaces or
tabs

Treated as a single space.

Command abbreviations

Allowed, if not ambiguous.

Command qualifiers or options

Prefix with a space and a dash (–).

Numbers

Hexadecimal, unless otherwise specified.
(Registers, such as R0–R31, are shown in
decimal notation.)

3–2 Alpha SRM Console Commands

The following table lists Alpha SRM Console special keys and their
functions. These special keys provide command recall, line editing, and
basic input/output control flow.

To do this function...

Use one of these keys
or key sequences...

Terminate the command line input.

Enter

Delete one character to the left of the cursor.

Delete

Toggle insert/overstrike mode.
(Overstrike is the default.)

Ctrl/A

Recall previous commands.
(The last 16 commands are stored.)

Ctrl/B
Up arrow
Down arrow

Terminate the foreground process.

Ctrl/C

Move the cursor one position to the left.

Ctrl/D
Left arrow

Move the cursor to the end of the line.

Ctrl/E

Move the cursor one position to the right.

Ctrl/F
Right arrow

Move the cursor to the beginning of the line.

Ctrl/H

Suppress/resume (toggle) console output.

Ctrl/O

Resume the flow (XON) of data to the console.

Ctrl/Q

Retype the current command line.

Ctrl/R

Stop the flow (XOFF) of data to the console.

Ctrl/S

Delete the entire line.

Ctrl/U

Alpha SRM Console Commands 3–3

Basic Alpha SRM Console Command
Descriptions

This section describes the following basic Alpha SRM Console commands
that are necessary to boot the Digital UNIX and OpenVMS operating
systems:

•

boot

•

deposit

•

examine

•

fwupdate

•

set

•

show

The Alpha SRM Console offers additional commands. For a complete list
of Alpha SRM Console commands, enter help at the Alpha SRM Console
prompt (>>>).

3–4 Alpha SRM Console Commands

boot
Initializes the processor, loads a program image from the specified boot
device, and transfers control to the loaded image.

Syntax
boot [-file <filename>] [-flags <longword>[,<longword>]]
[-protocols <enet_protocol>] [-halt] [<boot_device>]

Arguments
<boot_device>
A device path or list of devices from which the firmware will attempt to
boot. Use the set bootdef_dev command to set an environment
variable that specifies a default boot device.

Options
-file <filename>
Specifies the name of a file to load into the system. Use the
set boot_file command to set the environment variable that specifies
a default boot file.
-flags <longword>[,<longword>]
Specifies additional information for the operating system. For systems
with OpenVMS, root number and boot flags are specified here. For
Digital UNIX systems, the following values may be used:
i = Interactive boot
s = Boot to single user
a = Autoboot to multiuser
Use the set boot_osflags command to set an environment variable
that specifies a default boot flag value.
-protocols <enet_protocol>
Specifies the Ethernet protocols that will be used for a network boot.
Values may be mop or bootp.

Alpha SRM Console Commands 3–5

-halt
Forces the bootstrap operation to halt and invoke the console program
after the image is loaded and the page tables and other data structures
are set up.

Description
The boot command initializes the processor, loads a program image from
the specified boot device, and transfers control to that image. If you do
not specify a boot device in the command line, the default boot device is
used. The default boot device is determined by the value of the
bootdef_dev environment variable.
If you specify a list of devices, a bootstrap is attempted from each device
in the order in which the device is listed. Then control passes to the first
successfully booted image. In a list, always enter network devices last,
because network bootstraps terminate only if a fatal error occurs or if an
image is successfully loaded.
The –flags option can pass additional information to the operating
system about the boot that you are requesting. On an OpenVMS system,
the –flags option specifies the system root number and boot flags. If you
do not specify a boot flag qualifier, the default boot flags value specified
by the boot_osflags environment variable is used.
The –protocols option allows selection of either the DECnet MOP or the
TCP/IP BOOTP network protocols. The keywords mop and bootp are
valid arguments for this option. It is possible to set the default protocol
for a port by setting the environment variable ewa0_protocols or
era0_protocols to the appropriate protocol.
Explicitly stating the boot flags or the boot device overrides the current
default value for the current boot request, but does not change the
corresponding environment variable.
See the Environment Variables for Alpha SRM Console Commands
section in this chapter for more information about environment
variables.

3–6 Alpha SRM Console Commands

Examples
The following boot command boots the system from the default boot
device. The console program returns an error message if a default boot
device has not been set.
>>>boot
The following boot command boots the system from Ethernet port ewa0:
>>>boot ewa0
The following boot command boots the system, using the file named
dec2.sys from Ethernet port ewa0:
>>>boot -file dec2.sys ewa0
The following boot command boots the system, using the TCP/IP BOOTP
protocol from Ethernet port ewa0:
>>>boot -protocol bootp ewa0
The following boot command boots the system from the default boot
device, using flag settings 0,1:
>>>boot -flags 0,1
The following boot command loads the bootstrap image from disk dka0,
halts the bootstrap operation, and invokes the console program.
Subsequently, you can enter the continue command to transfer control to
the operating system.
>>>boot -halt dka0

Alpha SRM Console Commands 3–7

deposit
Writes data to the specified address.

Syntax
deposit [-{b,w,l,q,o,h}] [{physical, virtual, gpr, fpr,
ipr}] [-n <count>] [-s <step>] [<device>:]<address>
<data>

Arguments
<device>:
The optional device name (or address space) selects the device to access.
The following platform-independent devices are supported:
•

pmem
Physical memory.

•

vmem
Virtual memory. All access and protection checking occur. If the
access is not allowed to a program running with the current
processor status (PS), the console issues an error message. If
memory mapping is not enabled, virtual addresses are equal to
physical addresses.

<address>
An address that specifies the offset within a device into which data is
deposited. The address may be any legal symbolic address.

3–8 Alpha SRM Console Commands

Valid symbolic addresses are:
Symbolic Address

Description

gpr-name

Represents general-purpose register.

ipr-name

Represents internal processor
register.

Program counter.

The location immediately following
the last location referenced by an
examine or deposit operation.

The location immediately preceding
the last location referenced by an
examine or deposit operation.

The location last referenced by an
examine or deposit operation.

The location addressed by the last
location referenced by an examine or
deposit operation.

<data>
The data to be deposited.

Options
-b
Specifies the data type is byte.
-w
Specifies the data type is word.
-l
Specifies the data type is longword.

Alpha SRM Console Commands 3–9

-q
Specifies the data type is quadword.
-o
Specifies the data type is octaword.
-h
Specifies the data type is hexword.
-physical
References physical address space.
-virtual
References virtual address space.
-gpr
References general-purpose register address space.
-fpr
References floating-point register address space.
-ipr
References internal processor register address space.
-n <count>
Specifies the number of consecutive locations to examine.
-s <step>
Specifies the address increment as a hexadecimal value. This option
allows you to override the increment that is normally derived from the
data size.

Description
The deposit command writes data to the address specified, such as a
memory location, register, device, or file. The defaults for address space,
data size, and address are the last specified values. After initialization,
the default for address space is physical memory; for data size, the
default is a quadword; and for address, the default is zero.

3–10 Alpha SRM Console Commands

An address or device can be specified by concatenating the device name
with the address. For example, use pmem:0 and specify the size of the
address space to be written. If a conflicting device, address, or data size
is specified, the console ignores the command and issues an error
response.

Examples
The following deposit command clears the first 512 bytes of physical
memory:
>>>d -n 1ff pmem:0 0
The following deposit command writes the value 5 into four longwords,
starting at physical memory address 1234:
>>>d -l -n 3 pmem:1234 5
The following deposit command loads GPRs R0 through R8 with –1:
>>>d -n 8 r0 ffffffff
The following deposit command writes the value 8 in the first longword
of the first 17 pages in physical memory:
>>>d -l -n 10 -s 200 pmem:0 8

Alpha SRM Console Commands 3–11

examine
Displays the contents of the specified address.

Syntax
examine [-{b,w,l,q,o,h,d}] [-{physical, virtual, gpr,
fpr, ipr}] [-n <count>] [-s <step>] [<device>:]<address>

Arguments
<device>:
The optional device name (or address space) selects the device to access.
<address>
The address specifies the first location to examine within the current
device. The address can be any legal address specified.

Options
-b
Specifies the data type is byte.
-w
Specifies the data type is word.
-l
Specifies the data type is longword.
-q
Specifies the data type is quadword.
-o
Specifies the data type is octaword.
-h
Specifies the data type is hexword.

3–12 Alpha SRM Console Commands

-d
Specifies the data displayed is the decoded macro instruction. The Alpha
instruction decode (–d) does not recognize machine-specific PALcode
instructions.
-physical
References physical address space.
-virtual
References virtual address space.
-gpr
References general-purpose register address space.
-fpr
References floating-point register address space.
-ipr
References internal processor register address space.
-n <count>
Specifies the number of consecutive locations to examine.
-s <step>
Specifies the address increment as a hexadecimal value. This option
allows you to override the increment that is normally derived from the
data size.

Description
The examine command displays the contents of the specified address,
such as a memory location, register, device, or file. The defaults for
address space, data size, and address are the last specified values. After
initialization, the default for address space is physical memory; for data
size, the default is a quadword; and for address, the default is zero.
An address or device can be specified by concatenating the device name
with the address. For example, use pmem:0 and specify the size of the
address space to be displayed. If a conflicting device, address, or data
size is specified, the console ignores the command and issues an error
response.

Alpha SRM Console Commands 3–13

The display line consists of the device name, the hexadecimal address (or
offset within the device), and the examined data, also in hexadecimal.
The examine command supports the same options as the deposit
command. Additionally, the examine command supports instruction
decoding with the –d option, which disassembles instructions beginning
at the current address.

Examples
The following examine command displays the contents of R0, using a
symbolic address:
>>>e r0
gpr: 0 (R0)

0000000000000002

The following examine command displays the contents of R0, using
address space:
>>>e -g 0
gpr: 0 (R0)

0000000000000002

The following examine command displays the contents of R0, using a
device name:
>>>e gpr:0
gpr: 0 (R0)

0000000000000002

The following examine command displays the contents of R7 and the
next five registers: >>>examine -n 5 r7
gpr: 38 (R7) 0000000000000000
gpr: 40 (R8) 0000000000000000
gpr: 48 (R9) 0000000000000000
gpr: 50 (R10) 000000007FFBF800
gpr: 58 (R11) 000000007FF781A2
gpr: 60 (R12) 0000000000000000
The following examine command displays the contents of internal
processor register 11:
>>>examine ipr:11
ipr: 11 (KSP) FFFFFFFF8228DFD0

3–14 Alpha SRM Console Commands

fwupdate
Loads and runs the firmware update utility form a diskette.

Syntax
fwupdate

Arguments
None

Options
None

Description
The fwupdate command script is used to load and run the firmware
update utility from a diskette. The file fwupdate.exe is extracted from a
diskette with a FAT file structure. This executable is then loaded to
physical address 900000 and is executed in PALmode.

Examples
The following fwupdate script command loads and runs the firmware
update utility from a diskette:
>>>fwupdate

Alpha SRM Console Commands 3–15

set
Sets or modifies the value of an environment variable.

Syntax
set <envar> <value> [-default] [-integer] [-string]

Arguments
<envar>
The environment variable to be assigned a new value.
<value>
The value that is assigned to the environment variable. It can be either
a numeric value or an ASCII string.

Options
-default
Restores an environment variable to its default value.
-integer
Creates an environment variable as an integer.
-string
Creates an environment variable as a string.

Description
The set command is used to set or modify the value of an environment
variable. Environment variables are used to pass configuration
information between the console and the operating system. See the
Environment Variables for Alpha SRM Console Commands section in
this chapter for more information about environment variables.

3–16 Alpha SRM Console Commands

Examples
The following set command modifies the default boot device to ewa0:
>>>set bootdef_dev ewa0
The following set command attempts to boot the console following an
error, halt, or power up:
>>>set auto_action boot
The following set command modifies the default boot flags to 0,1:
>>>set boot_osflags 0,1
The following set command creates an environment variable called
foobar and gives it a value of 5:
>>>set foobar 5
The following set command sets up the system to start the Windows NT
firmware after the next power cycle:
>>>set os_type nt

Alpha SRM Console Commands 3–17

show
Displays the current value of the specified environment variable or
information about the system.

Syntax
show [{config, device [device_name], iobq, hwrpb, map,
memory, pal, version, <envar>...}]

Arguments
config
Displays the current memory configuration, PCI logical slots, and ISA
logical slots (based on the ISA configuration utility input to the
configuration database).
device [device name]
Displays the devices and controllers in the system. Specifying a device
name returns information on that device only.
iobq
Displays the input/output counter blocks.
hwrpb
Displays the hardware restart parameter block.
map
Displays the system virtual memory map.
memory
Displays the memory module configuration.
pal
Displays the version of Digital UNIX and OpenVMS PALcode.
version
Displays the version of the console.
<envar>
Displays the current value of a specified environment variable.

3–18 Alpha SRM Console Commands

Description
The show command displays information about the system and the
current value of a specified environment variable.
For more information about environment variables, see the Environment
Variables for Alpha SRM Console Commands section in this chapter.

Examples
The following show command lists device information, such as system
designation, drive model, or Ethernet address:
>>>show device
dka0.0.0.6.0
DKA0
RZ26L 441A
dka400.4.0.6.0 DKA400 RRD43 3213
dva0.0.0.0.1
DVA0
ewa0.0.0.12.0 EWA0 08-00-2B-E2-1C-25
pka0.7.0.6.0
PKA0
SCSI Bus ID 7
The following show command lists system random-access memory (RAM)
size:
>>>show memory
48 Meg of System Memory
The following show command lists all environment variables and their
settings:
>>>show *
The following show command lists all environment variables, beginning
with boot:
>>>show boot*

Alpha SRM Console Commands 3–19

Environment Variables for Alpha SRM
Console Commands

This section describes environment variables that are used to define
system operational state and to pass information between the firmware
and the operating system.

Alpha SRM Console Commands 3–20

Environment Variable Descriptions
Environment variables are classified as either Alpha SRM Console
architecture-required or system-defined.

Alpha SRM Console Architecture-Required Environment Variables
The following table shows common Alpha SRM Console
architecture-required environment variables and their descriptions. For
a complete list, enter show * at the Alpha SRM Console prompt.
Variable

Description

auto_action

When used with the set or show command, this variable
modifies or displays the console action that follows an
error, halt, or power up. The action can be halt, boot, or
restart. The default is halt.

boot_file

When used with the set or show command, this variable
modifies or displays the file name to be used when a
bootstrap requires a file name. The default is null.

boot_osflags

When used with the set or show command, this variable
modifies or displays the additional parameters to be
passed to system software. For OpenVMS software,
these parameters are the system root number and boot
flags. The default is 0.

bootdef_dev

When used with the set or show command, this variable
modifies or displays the default device or device list from
which the system will attempt to boot. If the system
software is preloaded, the variable is preset to point to
the device containing the preloaded software. The
default is null.

Alpha SRM Console Commands 3–21

System-Defined Environment Variables
The following table shows common system-defined environment
variables and their descriptions. For a complete list, enter show * at the
Alpha SRM Console prompt.
Variable

Description

console

When used with the set command, this variable
modifies the console output to either the serial port or
the graphics controller.

control_scsi_term

This variable is unused in the evaluation board or
motherboard system.

ewa0_mode

This variable determines whether either the AUI
(ThinWire) or the twisted-pair Ethernet ports will be
enabled. AUI is the default. (Autosensing is not
supported.)

os_type

When used with the set or show command, this variable
modifies or displays the specified firmware that will be
loaded on the next power cycle. The possible values
are:
nt
= Select the Windows NT firmware.
osf = Select the Alpha SRM Console.
vms = Select the Alpha SRM Console.

pci_parity

This variable controls PCI parity checking. The
possible values are:
on
= Parity checking is enabled.
off = Parity checking is disabled; this is the default.
sniff = Parity checking is enabled or disabled
depending on the PCI device.

oem_string

When used with the set or show command, this variable
modifies or displays a text string that identifies the
product name in the Alpha SRM Console banner.

(Continued on the next page)

3–22 Alpha SRM Console Commands

(Continued)
Variable

Description

language n

The language environment variable assigns language n to the
system (where n is the option number of a language listed in the
menu that follows). Use the following procedure to select the
language:
1. At the Alpha SRM Console prompt, enter the following
commands:
>>>set language 0
>>>init
The following menu and prompt are displayed:
n Language

Language

0 none (display menu)
30 Dansk
32 Deutsch
34 Deutsch (Schweiz)
36 English (American)
38 English (British/Irish)
3A Espanol
3C Francais
3E Francais (Canadian)

40 Francais (Suisse Romande)
42 Italiano
44 Nederlands
46 Norsk
48 Portugues
4A Suomi
4C Svenska
4E Vlaams

(1..16):
2. Enter the number that corresponds to the language you
want to use. The following example shows how to assign
the English (American) language to the system:
(1..16):36
3. When you receive a message to reset the system, power
cycle the system.

Alpha SRM Console Commands 3–23

ISA Configuration Utility

This section describes how to configure Industry Standard Architecture
(ISA) options before using a new option module with an evaluation board
or motherboard system.

3–24 Alpha SRM Console Commands

isacfg
Allows you to enter installation information about ISA option modules.

Syntax
isacfg [-init] [-slot <slot#>] [-dev <device#>]
[-all|-rm|-mk|-mod] [-<field> <value>]...

Arguments
None

Options
-init
Initializes the configuration table to the default settings.
-slot <slot#>
Allows you to enter a unique slot number for each ISA adapter. You may
assign the numbers in any order. The slot number does not relate to a
physical ISA adapter position. Slot 0 is reserved for the motherboard
devices.
-dev <device#>
Optional; defaults to 0 if not entered. On a multifunction or multiport
adapter, this specifies the device on the adapter.
-all
Shows the entire configuration table. Overrides all other commands.
-rm
Deletes an entry from the table.
-mk
Adds an entry to the table.
-mod
Modifies an entry in the table.

Alpha SRM Console Commands 3–25

The following field names and associated values are optional:
-<dmachan{0-3}> <value>
Allows you to specify up to four direct memory access (DMA)
channels for the device. The valid values are 0,1,2,3.
-<dmamode{0-3}> <value>
Allows you to specify the DMA type for –dmachan{0-3}. The
following values specify the DMA modes:
1 = Block
2 = Demand
4 = Single
8 = Cascade
-<enadev> <value>
Allows you to specify whether an entry is enabled or disabled.
Disabled devices are not used in resource allocation calculations.
The following values specify whether an entry is enabled or disabled:
0 = No (disabled)
1 = Yes (enabled)
-<etyp> <value>
Defines an entry type. The following values specify an entry type:
0 = Causes the entry to be deleted
1 = Single option
2 = Embedded multiport device
3 = Multiport option device
-<handle> <string>
Binds a name to the driver (up to 15 characters).
-<iobase>{0-5}> <value>
Specifies up to six I/O base registers (in hexadecimal) for a particular
device entry.
-<irq{0-3}> <value>
Allows you to assign up to four interrupt request (IRQ) channels to
the device (use decimal IRQ levels).

3–26 Alpha SRM Console Commands

-<membase{0-2}> <value>
Specifies up to three read/write ISA memory regions.
-<memlen{0-2}> <value>
Specifies the length of a memory region for one of three read/write
memory regions.
-<rombase> <value>
Specifies an address for the ISA BIOS on an external ROM.
-<romlen> <value>
Specifies the length of the ROM.
-<totdev> <value>
Allows you to record the total number of devices for a particular slot.

Description
ISA devices are not capable of being probed for configuration information
by the Digital UNIX or OpenVMS operating systems. Therefore, you
must enter ISA option information manually by using the ISA
configuration utility (isacfg). You must use this utility before installing a
new ISA option module on an evaluation board or motherboard system
that is running the Digital UNIX or OpenVMS operating systems.

Adding ISA Options
To add a supported ISA option to an evaluation board or motherboard
system running the Digital UNIX or OpenVMS operating system, use
the following procedure:
Step

Action

Result

Perform operating system
configuration tasks, if any. Refer to
your operating system installation
guide and release notes.

The operating system is
prepared for the ISA option.

Shut down the operating system.

The system displays the Alpha
SRM Console prompt (>>>).

(Continued on the next page)
Alpha SRM Console Commands 3–27

(Continued)
Step

Action

Result

Enter isacfg <options> at the
Alpha SRM Console prompt (>>>).

The new ISA option is added to
the Alpha SRM Console
configuration table.

Enter init at the Alpha SRM Console
prompt (>>>).

The Alpha SRM Console is
reinitialized.

Refer to the ISA option documentation
to configure the ISA option.

The ISA option is properly
configured.

Refer to the evaluation board or
motherboard documentation to turn
off the system and install the ISA
option.

The ISA option is properly
installed.

Turn on and boot the system.

The operating system boots
and recognizes the new ISA
option.

Examples
The following example shows how to use the isacfg utility to enter
configuration information for the DE205 Ethernet controller option into
the configuration database. Examples to display, modify, and remove
table entries are included as well. In some cases, there are scripts
available to issue the proper isacfg command. Script commands are
preceded by an add_ prefix.
The following isacfg command uses the built-in script to add the DE205
option:
>>>add_de205
The following isacfg command, which performs the same function as the
add_de205 command in the previous example, adds the DE205 option:
>>>isacfg -slot 1 -dev 0 -mk -handle DE200-LE \
_>-irq0 5 -iobase0 300 -etyp 1 -enadev 1

3–28 Alpha SRM Console Commands

The following isacfg command displays the configuration database:
>>>isacfg -all
The following isacfg command modifies the irq0 entry of an option:
>>>isacfg -mod -slot 1 -irq0 14
The following isacfg command removes an entry:
>>>isacfg -rm -slot 1 -dev 0

Alpha SRM Console Commands 3–29

DEC EtherWORKS 3 Configuration Utility

This section describes how to configure the DE205 ISA network interface
module.

3–30 Alpha SRM Console Commands

ewrk3_config
Programs the DE205 onboard EEPROM.

Syntax
ewrk3_config [-curaddr <io_base>] [-ioaddr <io_base>]
[-bufsize <mode>] [-memaddr <memory_base>][-irq
<irq_line>] [-fbus] [-ena16] [-default] [-show]

Arguments
None

Options
-curaddr <io_base>
Specifies the current hex I/O base address (physical bus address) where
the network interface module is located.
-ioaddr <io_base>
Specifies the hex I/O base address (physical bus address) for the current
network interface module. The default address range is 300 (hex)
through 31F (hex).
-bufsize <mode>
Specifies the memory mode and the amount of actual memory utilized
and owned by the network interface module. The possible settings are
2K, 32K, or 64K. In most cases, Digital recommends that the 2K setting
be used, leaving a maximum amount of high memory for other
application programs.

Alpha SRM Console Commands 3–31

-memaddr <memory_base>
Specifies the base memory address for the network interface module.
Depending upon the memory buffer size and mode selected, the network
interface module can be in any unused high memory area. In 2KB mode,
this includes segments A through F on any 2KB boundary; 32KB mode
allows segments A through F on any 32KB boundary; 64KB mode allows
segments A through F on any 64KB boundary.
-irq <irq_line>
Specifies the IRQ line for the network interface module to interrupt the
CPU. The default for the interrupt line is IRQ5. The possible values for
the IRQ lines are:
5 = IRQ5
10 = IRQ10
11 = IRQ11
15 = IRQ15
-fbus
Enables the fast bus option for bus clock speeds greater than the
standard ISA 8.33 MHz.
-ena16
Enables 16-bit transfer mode, and indicates that 16-bit memory transfers
should be used. The default mode is 16-bit transfer.
-default
Sets the network interface module to the default settings.
-show
Displays the entire contents of the EEPROM of the network interface
module.

3–32 Alpha SRM Console Commands

Description
The DEC EtherWORKS 3 configuration utility programs the DE205
onboard EEPROM and is similar to the isacfg utility. In order to use
multiple network interface modules in a system, the modules must be
inserted one at a time to change, at a minimum, their I/O base address to
avoid address conflicts. The system must then be power cycled for the
new settings to take effect.
Entering the ewrk3_config command without options causes the entire
address space to be searched for DE205 modules and displays the I/O
base addresses of all modules found.

Examples
The following ewrk3_config command displays the I/O base addresses of
all DE205 modules in the system:
>>>ewrk3_config
The following ewrk3_config command sets the DE205 module back to its
default settings. The system must be power cycled for the new settings
to take effect.
>>>ewrk3_config -default
The following ewrk3_config command changes a DE205 module’s I/O
base address from its default setting to address 340h. The system must
be power cycled for the new settings to take effect.
>>>ewrk3_config -curaddr 300 -ioaddr 340

Alpha SRM Console Commands 3–33

Chapter 4
Alpha SRM Console Diagnostic Commands

Overview
This chapter describes how to run the diagnostic firmware to test and
debug various system components. This chapter is divided into the
following sections:
•

Alpha SRM Console Diagnostic Firmware Bootstrap Procedure

•

Alpha SRM Console Diagnostic Command Descriptions

•

Environment Variables for Diagnostic Commands

Alpha SRM Console Diagnostic Commands 4–1

Alpha SRM Console Diagnostic Firmware Bootstrap
Procedure
To run diagnostic commands on your system, you must bootstrap the
Alpha SRM Console diagnostic firmware from the compact disc. While
running the Alpha SRM Console diagnostic firmware, some diagnostic
commands exercise graphic devices that require a terminal attached to
the COM1 serial port to be the default terminal device.

Bootstrapping the Diagnostic Firmware
To boot the Alpha SRM Console diagnostic firmware, follow this
procedure:
1. Insert the EBSDK and Firmware Update compact disc into the
CD–ROM drive.
2. Enter the following command to determine the unit number of the
drive for your CD–ROM device:
>>>show dev

4–2 Alpha SRM Console Diagnostic Commands

A display appears showing information about the devices on your
system. For example:
dka0.0.0.9.0
dka400.4.0.9.0
dva0.0.0.0.1
ewa0.0.0.7.0
pka0.7.0.9.0

DKA0
DKA400
DVA0
EWA0
PKA0

RZ26L 440C
RRD43 1084
08-00-2B-E2-B1-08
SCSI Bus ID 7

The numbers in the middle column are the unit numbers assigned to
each drive on your system, where:
•

The letters DK refer to a SCSI CD–ROM or disk device.

•

The third letter (A, B, C, D, or E) refers to the SCSI bus
designation. Refer to the hardware owner’s guide for more
details.

•

The numbers refer to the drive number.

3. Using the following syntax, enter the boot command to boot from a
compact disc.
boot -flag 0,a0 device-number
For example, to boot the system from CD–ROM drive number 4,
enter:
>>>boot -flag 0,a0 dka400
The following prompt appears for the bootfile path:
BOOTFILE:

Alpha SRM Console Diagnostic Commands 4–3

4. Use the following table to determine the path that corresponds to the
diagnostic firmware for your evaluation board or motherboard:

If you have an...

Enter this path...

AlphaPC 164

[update.pc164]pc164srm.sys

EB164

[update.eb164]eb164dia.sys

EB66+

[update.eb66p]eb66pdia.sys

AlphaPC 64

[update.pc64]pc64dia.sys

EB64+

[update.eb64p]eb64pdia.sys

5. The Alpha SRM Console will restart. Observe the Alpha SRM
Console prompt (>>>) on the default console terminal device.

4–4 Alpha SRM Console Diagnostic Commands

Alpha SRM Console Diagnostic Command
Descriptions

This section describes the following diagnostic commands that test and
debug various system components:
•

exer

•

exer_read

•

exer_write

•

kill_diags

•

memexer

•

memtest

•

nettest

•

show_status

•

sys_exer

•

test

Diagnostic commands that are described as command scripts can be
customized for a particular purpose.
The Alpha SRM Console offers additional commands. For a complete list
of Alpha SRM Console commands, enter help at the Alpha SRM Console
prompt (>>>).

Alpha SRM Console Diagnostic Commands 4–5

exer
Exercises one or more devices by performing read, write, or compare
operations.

Syntax
exer [-sb <start_block> ] [-eb <end_block> ]
[-p <pass_count> ] [-l <blocks> ] [-bs <block_size> ]
[-bc <block_per_io> ] [-d1 <buf1_string> ]
[-d2 <buf2_string> ] [-a <action_string> ]
[-sec <seconds> ] [-m] [-v] [-delay <milliseconds> ]
<device_name>...

Arguments
<device_name>
Specifies the names of the devices or file streams to be exercised.

Options
-sb <start_block>
Specifies the starting block number (hex) within file stream. The default
is 0.
-eb <end_block>
Specifies the ending block number (hex) within file stream. The default
is 0.
-p <pass_count>
Specifies the number of passes to run the exerciser. If the number of
passes is set to 0, the devices will be activated continuously until halted
with a Ctrl/C. The default is 1.

4–6 Alpha SRM Console Diagnostic Commands

-l <blocks>
Specifies the number of blocks (hex) to exercise. The –l option has
precedence over the –eb option. When reading from a device without the
–l and –eb options specified, the read operation continues until an
end-of-file is detected. When writing to a device without the –l and –eb
options specified, the write operation continues for the size of the device.
The default is 1.
-bs <block_size>
Specifies the block size (hex) in bytes. The default is 200 (hex).
-bc <block_per_io>
Specifies the number of blocks (hex) for each read and write operation.
On devices without a predetermined length, such as tape devices, the
packet size specified for the device should be used. The default packet
size is 2048. The maximum block size allowed with variable length block
read operations is 2048 bytes. The default is 1.
-d1 <buf1_string>
Specifies the value of the string argument variable for the eval command
to generate the buffer1 data pattern. The value of buffer1 is initialized
once prior to all read and write operations. The default value of the
string argument variable is all bytes set to 5A (hex).
-d2 <buf2_string>
Specifies the value of the string argument variable for the eval command
to generate the buffer2 data pattern. The value of buffer2 is initialized
once prior to all read and write operations. The default value of the
string argument variable is all bytes set to 5A (hex).

Alpha SRM Console Diagnostic Commands 4–7

-a <action_string>
Specifies an ‘action string’ that determines the sequence of read, write,
and compare operations to various buffers. The default action string is
‘?r’. The possible values for the action string are:
b = Add a constant to buffer1.
c = Compare buffer1 with buffer2.
n = Write without lock from buffer1.
r = Read into buffer1.
s = Sleep for a number of milliseconds specified by the delay
qualifier. If no delay qualifier is present, sleep for 1 millisecond.
Note: Times reported in verbose mode will not be accurate when
this action string is used.
w = Write from buffer1.
z = Zero the contents of buffer1.
B = Add a constant to buffer2.
N = Write without lock from buffer2.
R = Read into buffer2.
W = Write from buffer2.
Z = Zero the contents of buffer2.
- = Seek to file offset prior to last read or write operation.
? = Seek to a random block offset within the specified range of
blocks.
-sec <seconds>
Specifies to terminate the exercise after the number of seconds have
elapsed. By default, the exerciser continues until the specified number
of blocks or passcounts are processed.
-m
Specifies metrics mode. When the exer command has completed, a total
throughput line is displayed.
-v
Specifies verbose mode. All data read is displayed on the default
terminal device. This option is not applicable on write or compare
operations. The default is verbose mode off.

4–8 Alpha SRM Console Diagnostic Commands

-delay <milliseconds>
Specifies the number of milliseconds to delay when “s” appears as a
character in the action string.

Description
The exer command exercises one or more devices by performing read,
write, and compare operations. Two buffers, buffer1 and buffer2, are
used to carry out these operations. A read operation reads from a
specified device into a buffer. A write operation writes from a buffer to a
specified device. A compare operation writes from two specified devices
into two buffers and compares the contents of the buffers. A read or
write operation can use either buffer, while a compare operation uses
both buffers.
Options, postfix string arguments, and qualifiers are used with the exer
command to specify:
•

The address range to test within the test devices.

•

The packet size, also known as the I/O size, which is the number of
bytes read or written in one I/O operation.

•

The number of passes to run the exer command.

•

The number of seconds to run the exer command.

•

The sequence of read, write, and compare operations on the test
devices.

Both buffer1 and buffer2 are initialized to a data pattern before any read
or write operations occur. These buffers are never reinitialized, even
after completing one or more passes. The data patterns that the buffers
are initialized with are either a hex 5A in every byte of each buffer or are
specified by the string arguments to the optional data pattern qualifiers,
–d1, –d2.
The –d1, –d2 qualifiers use a postfix string argument to initialize a
buffer's contents. For each byte in the specified buffer, starting with the
first byte, this postfix string is passed to the eval command, which
returns a byte value that is then written to the specified buffer.

Alpha SRM Console Diagnostic Commands 4–9

Several exer command qualifiers are used to specify the amount of device
data to be processed. The qualifiers –sb, –eb, –l, –bs, and –bc specify,
respectively: starting block, ending block, number of blocks, block size in
bytes, and the number of blocks in a packet, where a packet is the
amount of data transferred in one read or write operation.
Reading, writing, comparing buffers, and other operations can be
specified to occur in various combinations and sequences. These
operations are specified by a string of one-character command codes
known as the ‘action string’. The action string is specified as an
argument to the action string qualifier, –a.
Each command code character in the action string is processed in a
sequence from left to right. Each time that the exer command completes
all of the operations specified by the action string, the exer command will
reduce the remaining amount of device data to be processed by the size
of the last packet processed by the action string. The action string is
repeatedly processed until the specified amount of device data has been
processed.
The lowercase action string characters, bnrwz, are used to specify
operations that involve buffer1. The uppercase action string characters,
BNRWZ, specify operations that involve buffer2. The action string
character, ‘c’, involves both buffer1 and buffer2. The action string
characters, ‘-?’, do not involve either buffer1 or buffer2.
The total number of bytes read or written on each pass of the exerciser is
specified by the length in blocks or the length indicated by the starting
and ending block address option arguments. If neither the ending
address nor the length options are specified, then on each pass, the
number of bytes processed could vary depending on whether or not the
file stream is being written to or just being read.
If the file stream is not being written to by the exer command, then it
will read until an end-of-file is detected. If the exer command will be
writing to the file (as specified in the action string), then the number of
bytes processed per pass is equal to the allocation size of the file. The
allocation size of the file is usually larger than the length of the file for
RAM disk files, but equal to the length for disk devices.

4–10 Alpha SRM Console Diagnostic Commands

All disk device read and write operations will fail if the block size is not
equal to 1 or a multiple of 512. Partial block read and write operations
are not supported so a length that is not a multiple of the block size will
result in no errors, but the last partial block read and write operations of
data will not occur.
Any combination of writing, reading, or comparing the buffer1 and
buffer2 can be executed in the sequence as specified in the action string.
Depending on the option arguments, some of the read, write, or compare
operations may be omitted without affecting the execution of the other
operations.
The exer command will return an error code immediately after a read,
write, or compare error, if the diagnostic environment variable
d_harderr is set to halt. When the diagnostic environment variable is set
to continue or loop when an error is detected, then subsequent
operations specified by the action string qualifier will occur except for
compare operations.
For example, if a read error occurs, a subsequent compare operation will
be omitted because a read failure preceding a compare operation
guarantees that the compare operation will fail. If subsequent block
read and write operations succeed, then compare operations of those
blocks will occur. When the exer command terminates, either because
all passes are complete or because of operator termination, then the
status returned will be that of the last failed write, read, or compare
operation, regardless of subsequent successful read or write operations.

Examples
The following command reads all SCSI-type disks for the entire length of
each disk. It continues to read all disks concurrently until 36000 seconds
(10 hours) have elapsed. Each read operation will occur at a random
block number on each disk.
>>>exer dk*.* -p 0 -sec 36000
The following command writes the hex pattern 5A to every byte of blocks
1, 2, and 3 — using a packet size of 2048. The value of 2048 for the

Alpha SRM Console Diagnostic Commands 4–11

packet size is derived from multiplying the –bc value (block per I/O) of 4
by the default –bs value (block size) of 512.
>>>exer -sb l -eb 3 -bc 4 -a ‘w’ -d1 ‘0x5a’ dka0

4–12 Alpha SRM Console Diagnostic Commands

exer_read
Continuously reads random blocks of data from all online disks and
displays detected errors. This is a command script.

Syntax
exer_read [-sec <seconds>] [<device>...]

Arguments
<device>
Specifies the device name to be exercised. The default is all online disks.

Options
-sec <seconds>
Specifies the number of seconds after which to terminate the exer_read
command script. By default, this command script continues to execute
until all blocks are processed or until the passcount value has been
reached. The passcount value is specified by the d_passes environment
variable. See the Environment Variables for Diagnostic Commands
section in this chapter for more information.

Description
The exer_read command script randomly determines a block number on
any online disk and reads a packet of 2048 bytes. Upon detecting an
error, the exer_read command script displays an error report to the
default console terminal device.

Alpha SRM Console Diagnostic Commands 4–13

This command script continues to repeat random read operations until
one of the following conditions occurs:
•

All blocks on the devices have been read for the number of passes
specified by the d_passes environment variable. See the
Environment Variables for Diagnostic Commands section in this
chapter for more information.

•

The process for this command has been stopped by pressing Ctrl/C or
by entering the kill_diags command.

•

The amount of time specified by the –sec option has elapsed.
Note: This command script will not display messages unless an
error occurs.

Examples
The following exer_read command randomly reads blocks of data from all
online disks and displays detected errors:
>>>exer_read

4–14 Alpha SRM Console Diagnostic Commands

exer_write
Continuously reads and non-destructively writes random blocks of data.
This is a command script.

Syntax
exer_write [-sec <seconds>] [<device>...]

Arguments
<device>
Specifies the device name to be exercised. The default is all online disks.

Options
-sec <seconds>
Specifies the number of seconds after which to terminate the exer_write
command. By default, this command continues to execute until all
blocks are processed or until the passcount value has been attained. The
passcount value is specified by the d_passes environment variable. See
the Environment Variables for Diagnostic Commands section in this
chapter for more information.

Description
The exer_write command script randomly determines a block number on
any online disk and reads a packet of 2048 bytes and then writes the
same data back to the same location. The data from the read operation
is then compared with the data on the disk for discrepancies. Upon
detecting a discrepancy, the exer_write command displays an error
report to the default console terminal device.

Alpha SRM Console Diagnostic Commands 4–15

This command continues to repeat random read, write, and compare
operations until one of the following conditions occurs:
•

•

The process for this command has been stopped by pressing Ctrl/C or
by entering the kill_diags command.

•

The specified time has elapsed.
Note: This command script will not display messages unless an
error occurs.

Examples
The following exer_write command randomly reads, writes, and
compares blocks of data from all disks that are online:
>>>exer_write

4–16 Alpha SRM Console Diagnostic Commands

kill_diags
Stops all executing diagnostic processes. This is a command script.

Syntax
kill_diags

Arguments
None

Options
None

Description
The kill_diags command script stops all executing diagnostic processes.

Alpha SRM Console Diagnostic Commands 4–17

Examples
The following diagnostic commands start two memory exerciser
processes and display the status of all executing diagnostics. A kill_diags
command is then issued, which stops all memory exerciser processes.
The show_status command is then issued a second time to confirm that
the system is idle.
>>>memexer 2 &
>>>show_status
ID

Program

Device

Pass

Hard/Soft

Bytes Written

Bytes Read

------

-------

-----

-------

-------------

----------

00000001

idle

system

00000351

memtest

memory

37748736

00000352

memtest

memory

37748736

>>>kill_diags
>>>show_status
ID

Program

Device

Pass

Hard/Soft

Bytes Written

Bytes Read

------

-------

-----

---------

-------------

----------

00000001

idle

system

>>>

4–18 Alpha SRM Console Diagnostic Commands

memexer
Tests all available memory. This is a command script.

Syntax
memexer [ <number> ]

Arguments
<number>
Specifies the number of memory test processes to invoke. The default
is 1.

Options
None

Description
The memexer command script invokes the requested number of memory
tests running continuously in the background. Memory tests randomly
allocate and test blocks of memory two times the size of the Bcache using
all available memory.
Note: This command script will not display messages unless an
error occurs.

Alpha SRM Console Diagnostic Commands 4–19

Examples
The following memexer command starts two memory tests running in
the background:
>>>memexer 2
>>>show_status
ID

Program

Device

Pass

Hard/Soft

Bytes Written

Bytes Read

------

-------

-----

---------

------------

----------

00000001

idle

system

00000107

memtest

memory

541065216

00000108

memtest

memory

541065216

>>>

4–20 Alpha SRM Console Diagnostic Commands

memtest
Tests the specified section of memory with multiple write, read, and
verify operations.

Syntax
memtest [-sa <start_address> ] [-ea <end_address> ]
[-l <length> ] [-bs <block_size> ] [-i <address_inc> ]
[-d <data_pattern> ] [-p <pass_count> ]
[-rs <random_seed> ] [-rb ] [-f ] [-m ] [-z ]
[-h ] [-mb ] [-t <test_number>] [-ba <block_address>]

Arguments
None

Options
-sa <start_address>
Specifies the starting address for the test. The default is the first
free space in memzone.
-ea <end_address>
Specifies the ending address for the test. The default is the start
address plus the length.
-l <length>
Specifies the length of section to test in bytes. The default is the
block_size, except with the –rb option, which uses the zone size.
The –l option has precedence over the -ea option.
-bs <block_size>
Specifies the block (or packet) size (hex) in bytes. The default is
8192 bytes. This is only used for the random block test. For all
other tests the block size equals the length.

Alpha SRM Console Diagnostic Commands 4–21

-i <address_inc>
Specifies the address increment value in longwords. This value will
be used to increment the address through the memory to be tested.
The default is 1 (longword). This is only implemented for the gray
code test. An address increment of 2 tests every other longword. This
option is useful for multiple CPUs testing the same physical memory.
-d <data_pattern>
Specifies to use this data pattern for testing memory. This is only
used for the march test. The default pattern is all 5’s.
-p <pass_count>
Specifies the number of times to execute the test. If the number of
passes is set to 0, then the section of memory will be tested
continuously until halted with a Ctrl/C. The default is 1.
-rs <random_seed>
Specifies the value of the random seed in order to vary the random
data patterns generated. This option is only used for the random
test. The default is 0.
-rb
Specifies to randomly allocate and test all of the specified memory
address range. Allocations are done of block_size.
-f
Specifies fast mode. If –f is specified, the data compare is omitted.
Only Error Correction Circuitry (ECC) and Error Detection Codes
(EDC) errors are detected.
-m
Specifies to time the memory test. The elapsed time is displayed at
the end of the test. By default the timer is off.
-z
Specifies the test will use the specified memory address without an
allocation. This bypasses all checking but allows testing in addresses
outside of the main memory heap. It also allows unaligned testing.
Warning: This option permits testing and corrupting of any
memory location.

4–22 Alpha SRM Console Diagnostic Commands

-h
Specifies to allocate test memory from the firmware heap.
-mb
Specifies to use memory barriers after each memory access. When
set, an mb (memory barrier) will be done after every memory access.
This guarantees serial access to memory.
-t <test_number>
Specifies the test mask. The default is all tests.
-ba <block_address>
Specifies that data stored at this address will be used to write each
block. This option is used only for the victim block test.

Description
The memtest command contains a gray code memory test, a marching 1’s
and 0’s memory test, a random test, and a victim block test. These four
tests, which are referred to as Memtest t1 through t4, can be run
sequentially or individually to detect different types of memory
problems.

Alpha SRM Console Diagnostic Commands 4–23

The following table describes Memtest t1 through t4.

memtest

Description

Uses a gray code algorithm to test a specified section
of memory. A gray code pattern and inverse gray
code pattern are written, read, and verified for the
specified address range.

Uses a marching 1’s and 0’s algorithm to test a
specified section of memory. A marching pattern of
1’s and 0’s and inverse pattern are written, read, and
verified for the specified address range.

Uses a random algorithm to test a specified section of
memory. Random addresses, within the specified
address range, can be tested with random data of
random length.

Writes blocks of data, victimize the data, then read
and verify blocks of data for the specified address
range.

The default is for all four tests to run sequentially.
Multiple memtest commands can be issued concurrently, and can be
used in conjunction with other commands to test the complete system.
Warning: The memtest command will destroy the data in the
section of memory under test.
The –f (fast mode) option can be specified to reduce the depth of testing
for the memtest command. Using this option will stress the section of
memory under test with a higher throughput, but will not detect address
shorts. Failures can still be detected with the ECC and EDC logic.
Large sections of memory require more time for testing than small
sections of memory. To make the memtest command run faster, a Ctrl/C

4–24 Alpha SRM Console Diagnostic Commands

or a kill command can be detected only while it is outside of all test loops.
For this reason, a Ctrl/C or a kill command may not abort immediately.

Examples
The following memtest command tests a section of memory starting at
0x200000 (–sa) for 0x1000 bytes (–l):
>>>memtest -sa 200000 -l 1000
The following memtest command tests a section of memory from
0x200000 for 0x1000 bytes, but data is not verified (–f):
>>>memtest -sa 200000 -l 1000 -f
The following memtest command has a default block size of 8192 bytes
and is written from 0x300000 for 10 passes (–p):
>>>memtest -sa 300000 -p 10
The following memtest command tests a section of memory from
0x200000 to 0x3fffff. This example also uses the –rb option, which allows
every block within the range randomly allocated and prevents the
reporting of errors if a block within the range cannot be allocated.
>>>memtest -sa 200000 -ea 400000 -rb
The following memtest command has the console heap (–h) tested by
randomly dynamically allocating 0x100 byte blocks (–bs):
>>>memtest -h -rb -bs 100
The following memtest command performs tests across all of memzone
(all memory excluding the HWRPB, the PAL area, the console, and the
console heap). It is run in the foreground until you press Ctrl /C.
>>>memtest -rb -p 0

Alpha SRM Console Diagnostic Commands 4–25

nettest
Tests the network.

Syntax
nettest
[-f <file>] [-mode <port_mode>]
[-p <pass_count>] [-sv <mop_version>] [-to <loop_time>]
[-w <wait_time>] [<port>]

Arguments
<port>
Specifies the Ethernet port on which to run the test.

Options
-f <file>
Specifies the file containing the list of network station addresses to
which to loop messages. The default file name is lp_nodes_ewa0 for port
ewa0. The default file name is lp_nodes_ena0 for port ena0. The files by
default have their own station address.
-mode <port_mode >
Specifies the mode to set the port adapter (TGEC). The default
is ‘ex’ (external loopback). Allowed values are:
df = Default, use environment variable values
ex = External loopback
in = Internal loopback
nm = Normal mode
nf = Normal filter
pr = Promiscuous
mc = Multicast
ip = Internal loopback and promiscuous
fc = Force collisions
nofc = Do not force collisions
nc = Do not change mode

4–26 Alpha SRM Console Diagnostic Commands

-p <pass_count>
Specifies the number of times to run the test. If the number of passes is
set to 0, the network ports will be tested continuously until halted with a
Ctrl/C. The default is 1.
Note: This is the number of passes for the diagnostic. Each
pass will send the number of loop messages as set by the
environment variables ena*_loop_count and
ewa*_loop_count.
-sv <mop_version>
Specifies which MOP version protocol to use. If 3, then MOP V3
(DECnet Phase IV) packet format is used. If 4, then MOP V4 (DECnet
Phase V IEEE 802.3) format is used.
-to <loop_time>
Specifies the time, in seconds, allowed for the loop messages to be
returned. The default is 2 seconds.
-w <wait_time>
Specifies the time, in seconds, to wait between passes of the test. The
default is 0 (no delay). The network device can be very CPU intensive.
This option will allow other processes to run.

Description
The nettest command tests the network. This command contains options
for MOP loopback tests that can test specific ports in internal loopback,
external loopback, or live network loopback mode.
This command can run separately or be included in a script to test the
entire system.

Examples
This command performs an internal loopback test on port ewa0:
>>>nettest ewa0

Alpha SRM Console Diagnostic Commands 4–27

This command performs a normal mode loopback test on port ewa0,
using a list of nodes contained in the file ewa0_lp_nodes:
>>>nettest -f ewa0_lp_nodes -mode nm ewa0

4–28 Alpha SRM Console Diagnostic Commands

show_status
Shows the status of all executing diagnostic processes. This is a
command script.

Syntax
show_status

Arguments
None

Options
None

Description
The show_status command script reports one line of information for each
executing diagnostic process. The information includes error count,
passes completed, and bytes read or written to the device being tested.
The source of each line of information is an I/O block.

Alpha SRM Console Diagnostic Commands 4–29

Examples
The following diagnostic commands start up two memory test processes
and display the status of all executing diagnostic processes:
>>>memexer 2 &
>>>show_status
ID

Program

Device

Pass

Hard/Soft

Bytes Written

Bytes Read

------

-------

-----

-------

-------------

----------

00000001

idle

system

00000351

memtest

memory

37748736

00000351

memtest

memory

37748736

>>>

4–30 Alpha SRM Console Diagnostic Commands

sys_exer
Tests all subsystems and devices in the system concurrently. This is a
command script.

Syntax
sys_exer

[-lb]

Arguments
None

Options
-lb
Specifies external loopback tests to be performed on the parallel port and
COM1 serial port.

Description
The sys_exer command script simultaneously tests all subsystems and
system devices. All subsystems and devices are those that can be listed
with the show config and show device commands, including: memory,
disks, tapes, diskette, serial ports, parallel port, network, and graphic
devices.
All tests will continue to execute concurrently until a kill_diags or an init
command is issued. The set command, used with environment variables,
can establish parameters such as whether to halt, loop, or continue on
error. See the Environment Variables for Diagnostic Commands section
in this chapter for more information.

Alpha SRM Console Diagnostic Commands 4–31

The –lb option allows an external loopback test to be performed on the
parallel port and serial port COM1. The sys_exer command ignores the
passcount environment variable, d_passes.
Note: The sys_exer command attempts to test the entire system,
including graphic devices. Commands that exercise
graphic devices require that the terminal connected to
the COM1 serial port be the default console terminal
device.
To determine your default terminal device and to specify that the
terminal attached to the COM1 serial port be your default device,
use the following Alpha SRM Console commands:
To do this function...

Enter these commands...

Determine the default
terminal device.

>>>show console

Set the terminal attached
to the COM1 serial port to
be the default console
terminal device.

>>>set console serial
>>>init

4–32 Alpha SRM Console Diagnostic Commands

Examples
These commands run the sys_exer script to test all system components
concurrently and display the status of all executing diagnostic processes.
>>>sys_exer &
>>>show_status
ID

Program

Device

Pass

Hard/Soft

Bytes Written

Bytes Read

------

-----

---

---------

------

-----

00000001

idle

system

0000009f

memtest

memory

100663296

000000b4

exer_kid

dub0.0.0.1.0

444416

000000b5

exer_kid

duc0.6.0.2.0

122

1249280

000000b6

exer_kid

dud0.7.0.3.0

122

1249280

000000b7

exer_kid

dka0.0.0.0.0

256000

000000be

nettest

ewa0.0.0.6.0

20888

000000be

nettest

era0.0.0.7.0

17904

>>>

Alpha SRM Console Diagnostic Commands 4–33

test
Sequentially tests the entire system. This is a command script.

Syntax
test [-lb]

Arguments
-lb
Specifies which external loopback tests are performed on the parallel
port and the COM1 serial port.

Options
None

Description
The test command script sequentially tests the entire system, including
memory, disks, tapes, diskettes, serial ports, parallel port, network, and
graphic devices. All tests will execute serially for a minimum of
10 seconds per test. The run time of a test is proportional to the amount
of memory to be tested and the number of disk drives to be tested.
Only one instance of the test command can be executed at a time. The
test command can be executed as either a background or foreground
process.
The set command, used with environment variables, can establish
parameters such as whether to halt, loop, or continue on error. See the
Environment Variables for Diagnostic Commands section in this chapter
for more information.
The –lb option allows an external loopback test to be performed on the
parallel port and on the COM1 serial port. The passcount environment
variable, d_passes, is ignored by the test command.

4–34 Alpha SRM Console Diagnostic Commands

Note: The test command attempts to test the entire system,
including graphic devices. Commands that exercise
graphic devices require the terminal connected to the
COM1 serial port be the default console terminal device.
To determine your default terminal device and to specify that the
terminal attached to the COM1 serial port be your default device,
use the following Alpha SRM Console commands:
To do this function...

Enter these commands...

Determine the default
terminal device.

>>>show console

Set the terminal attached
to the COM1 serial port to
be the default console
terminal device.

>>>set console serial
>>>init

Alpha SRM Console Diagnostic Commands 4–35

Examples
These commands run the test script in the background to sequentially
test all system components and display the status of all executing
diagnostic processes.
>>>test &
>>>show_status
ID

Program

Device

Pass

Hard/Soft

Bytes Written

Bytes Read

------

-----

---

---------

------

-----

00000001

idle

system

0000009f

memtest

memory

100663296

000000b4

exer_kid

dub0.0.0.1.0

444416

000000b5

exer_kid

duc0.6.0.2.0

122

1249280

000000b6

exer_kid

dud0.7.0.3.0

122

1249280

000000b7

exer_kid

dka0.0.0.0.0

256000

000000be

nettest

ewa0.0.0.6.0

20888

000000be

nettest

era0.0.0.7.0

17904

>>>

4–36 Alpha SRM Console Diagnostic Commands

Environment Variables for Diagnostic
Commands

This section describes environment variables that are used to control the
operational state of the diagnostic test and describes how to respond to
error conditions.

Alpha SRM Console Diagnostic Commands 4–37

Environment Variable Descriptions
The following table shows optional Alpha SRM Console diagnostic
environment variables and their descriptions. For a complete list, enter
show * at the Alpha SRM Console prompt.
Variable

Description

d_bell

This variable specifies whether or not to ring the
terminal bell if an error is detected. The possible values
are:
off = Do not ring the bell. The default is off.
on = Ring the bell if an error is detected.

d_cleanup

This variable specifies whether or not cleanup code is
executed at the end of a diagnostic command. The
possible values are:
off = Do not execute cleanup code.
on = Execute cleanup code. The default is on.

d_complete

This variable specifies whether or not to display a
message that the diagnostic command has finished. The
possible values are:
off = Do not display a completion message. The default
is off.
on = Display a completion message.

d_eop

This variable specifies whether or not to display end-ofpass messages. The possible values are:
off = Do not display end-of-pass messages. The default
is off.
on = Display the end-of-pass messages.
(Continued on the next page)

4–38 Alpha SRM Console Diagnostic Commands

(Continued)
Variable

Description

d_harderr

This variable specifies the action taken following hard
error detection. The possible values are:
continue = Attempt to continue functioning until
normal completion.

d_oper

halt

= Stop functioning. The default is halt.

loop

= Continue to function.

This variable specifies whether or not an operator is
present. The possible values are:
off = No operator present. The default is off.
on = An operator is present.

d_passes

When used with the exer_write or exer_read command,
this variable determines the number of passes executed
by the command. When set to 0, the command is
executed indefinitely. The default is 1.

d_report

This variable specifies the depth of information provided
by the diagnostic error reports. The possible values are:
summary = Provide a brief summary of all errors.
full

= Provide a full and complete error report.

off

= Do not provide an error report.

(Continued on next page)

Alpha SRM Console Diagnostic Commands 4–39

(Continued)
Variable

Description

d_softerr

This variable specifies the action taken following hard
error detection. The possible values are:
continue = Attempt to continue functioning until
normal completion.

d_startup

halt

= Stop functioning. The default is halt.

loop

= Continue to function.

This variable specifies whether or not to display the
diagnostic startup message. The possible values are:
off = Do not display the startup message. The default is
off.
on = Display the startup message.

d_trace

This variable specifies whether or not to display test
trace messages. The possible values are:
off = Do not display test trace messages. The default is
off.
on = Display the test trace messages.

4–40 Alpha SRM Console Diagnostic Commands

Appendix A
Technical Support and Ordering
Information

Obtaining Technical Support
If you need technical support or help deciding which literature best
meets your needs, call the Digital Semiconductor Information Line:
United States and Canada
Outside North America

1–800–332–2717
+1–508–628–4760

or visit the Digital Semiconductor World-Wide Web Internet site:
http://www.digital.com/info/semiconductor

Technical Support and Ordering Information A–1

Ordering Digital Semiconductor Products
To order Alpha microprocessors, evaluation boards, and motherboards,
contact your local distributor.
To obtain a Digital Semiconductor Product Catalog , contact the Digital
Semiconductor Information Line. The following table lists some of the
semiconductor products available from Digital:

Product

Order Number

Alpha 21064A–233 Microprocessor

21064–BB

Alpha 21064A–275 Microprocessor

21064–DB

Alpha 21066–166 Microprocessor

21066–AA

Alpha 21066A–100 Microprocessor

21066–CB

Alpha 21066A–233 Microprocessor

21066–AB

Alpha 21164–266 Microprocessor

21164–AA

Alpha 21164–300 Microprocessor

21164–BA

Evaluation Board Kits
Evaluation board kits include a complete design kit, a Windows NT
installation kit, and an accessories kit with an evaluation board.
Product

Order Number

AlphaPC 64 Evaluation Board Kit –275 MHz

21A02–03

Alpha 21066A Evaluation Board Kit –233 MHz

21A03–03

Alpha 21164 Evaluation Board Kit –266 MHz

21A04–01

A–2 Technical Support and Ordering Information

Motherboard Kits
Motherboard kits include the motherboard and the motherboard user’s
manual.
Product

Order Number

21164 Motherboard

21A04–A0

Alpha 21164 Motherboard with 266MHz CPU and
2MB Cache

21A04–A1

AlphaPC 164 Motherboard

21A04–B0

AlphaPC 64 P3 Motherboard without CPU, cache,
and memory

21A02–A3

AlphaPC 64 P3 Motherboard with 2MB cache but
without CPU and memory

21A02–A4

AlphaPC 64 P3 Motherboard with 512KB cache but
without CPU and memory

21A02–A5

Design Kits
Design kits include full documentation and schematics. They do not
include evaluation boards or related hardware.
Product

Order Number

Alpha 21064 Evaluation Board Design Kit

QR–21A01–13

AlphaPC 64 Evaluation Board Design Kit

QR–21A02–13

Alpha 21066A Evaluation Board Design Kit

QR–21A03–13

Alpha 21164 Evaluation Board Design Kit

QR–21A04–11

AlphaPC 164 Evaluation Board Design Kit

QR–21A04–12

Technical Support and Ordering Information A–3

Ordering Digital Semiconductor Literature
The following table lists some of the available Digital Semiconductor
literature. For a complete list, contact the Digital Semiconductor
Information Line or visit Digital Semiconductor’s World-Wide Web
Internet site: http://www.digital.com/info/semiconductor.
Title
Alpha AXP Architecture Reference Manual

Order Number
1

EY–T132E–DP

DECchip 21064 and DECchip 21064A Alpha AXP
Microprocessors Hardware Reference Manual

EC–Q9ZUA–TE

Alpha 21066, 21066A, and 21068 Microprocessors
Hardware Reference Manual

EC–QC4GA–TE

Alpha 21066/21066A Microprocessors Data Sheet

EC–QC4HA–TE

Alpha 21066A Microprocessor Evaluation Board (EB66+)
User’s Guide

EC–QDVCB–TE

Alpha 21066A Microprocessor Evaluation Board (EB66+)
Product Brief

EC–QDVEA–TE

Alpha 21164 Microprocessor Hardware Reference Manual

EC–QAEQB–TE

AlphaPC 64 Evaluation Board Product Brief

EC–QEZMC–TE

AlphaPC 64 Evaluation Board User’s Guide

EC-QGY2C–TE

AlphaPC 164 Motherboard User’s Manual

EC–QPG0A–TE

AlphaPC 164 Microprocessor Evaluation Board Read Me
First

EC–QPFZA–TE

Alpha Evaluation Boards Software Developer’s Kit and
Firmware Update Read Me First

EC–QERSE–TE

Alpha Microprocessors Evaluation Board Debug Monitor
User’s Guide

EC–QHUVD–TE

Alpha Microprocessors Evaluation Board Software Design
Tools User’s Guide

EC–QHUWB–TE

A–4 Technical Support and Ordering Information

Alpha Microprocessors Evaluation Board Windows NT
3.51 Installation Guide

EC–QLUAE–TE

Alpha Microprocessors SROM Mini-Debugger User’s
Guide

EC–QHUXB–TE

Alpha SRM Console for Alpha Microprocessor Evaluation
Boards User’s Guide

EC–QK8DE–TE

PALcode for Alpha Microprocessors System Design Guide

EC–QFGLC–TE

Digital Semiconductor 21164 Alpha Microprocessor
Evaluation Board User’s Guide

EC–QD2UD–TE

DECchip 21064 and DECchip 21064A Alpha AXP PCI
Evaluation Board User’s Guide

EC–N0640–72

Digital Semiconductor 21164 Alpha Microprocessor
Motherboard User’s Manual

EC–QLJLC–TE

To purchase the Alpha AXP Architecture Reference Manual , call
1–800–DIGITAL from the U.S. or Canada, contact your local Digital
office or technical, or call Digital Press at 1-800-366-2665.

Technical Support and Ordering Information A–5

Ordering Third-Party Literature
You can order the following third-party literature directly from the
vendor:

Title

Vendor

PCI Local Bus Specification Revision 2.0
PCI Local Bus Specification Revision 2.1
PCI BIOS Specification Revision 2.1

PCI Special Interest Group
1–800–433–5177 (U.S.)
1–503–797–4207 (International)
1–503–234–6762 (FAX)

A–6 Technical Support and Ordering Information

Index

A
Adding ISA options, 3–25
Alpha SRM architecture-required
environment variables for Alpha
SRM Console commands, 3–21
Alpha SRM Console commands
boot, 3–5
deposit, 3–8
examine, 3–12
fwupdate, 3–15
set, 3–16
show, 3–18
Alpha SRM Console conventions, 3–2
Alpha SRM Console diagnostic
commands
exer, 4–6
exer_read, 4–13
exer_write, 4–15
kill_diags, 4–17
memexer, 4–19
memtest, 4–21
nettest, 4–26
show_status, 4–29
sys_exer, 4–31
test, 4–34
Alpha SRM Console diagnostic
environment variables. See

Environment variables for
diagnostic commands
Alpha SRM Console environment
variables. See Environment
variables for Alpha SRM Console
commands
Alpha SRM Console features, 1–2
Alpha SRM Console keys, 3–3
Alpha SRM system-defined
environment variables for Alpha
SRM Console commands, 3–22
AlphaPC 164
updating firmware from Alpha SRM
Console, 2–7
updating firmware from Debug
Monitor firmware, 2–6
updating firmware from Windows NT
firmware, 2–4
AlphaPC 64
updating firmware from Alpha SRM
Console, 2–7
updating firmware from Debug
Monitor firmware, 2–6
updating firmware from Windows NT
firmware, 2–4
Assigning language, 3–23
auto_action environment variable, 3–21

Index–1

B
boot command, 3–5
boot_file environment variable, 3–21
boot_osflags environment variable, 3–21
bootdef_dev environment variable, 3–21
Booting
changing default device, 3–17
from Ethernet port, 3–7
from the default boot device, 3–7
using –file option, 3–7
using –flags option, 3–7
using –protocol option, 3–7
Bootstrapping diagnostic firmware, 4–2

C
Commands. See Alpha SRM Console
commands; Alpha SRM Console
diagnostic commands
Compare disk operations. See Disks
console environment variable, 3–22
Console firmware. See Firmware
Console heap
testing, 4–25
control_scsi_term environment variable,
3–22
Conventions. See Alpha SRM Console
conventions; Document conventions

D
d_bell diagnostic environment variable,
4–38
d_cleanup diagnostic environment
variable, 4–38
d_complete diagnostic environment
variable, 4–38
d_eop diagnostic environment variable,
4–38
d_harderr diagnostic environment
variable, 4–39
Index–2

d_oper diagnostic environment variable,
4–39
d_passes diagnostic environment
variable, 4–39
d_report diagnostic environment
variable, 4–39
d_softerr diagnostic environment
variable, 4–40
d_startup diagnostic environment
variable, 4–40
d_trace diagnostic environment
variable, 4–40
DE205 option
adding, 3–28
changing base address, 3–33
configuring with default settings,
3–33
displaying the I/O base address, 3–33
ewrk3_config command, 3–31
Debug Monitor firmware
switching to the Alpha SRM Console,
2–15
updating the flash ROM, 2–6
DEC EtherWORKS 3 Configuration
Utility. See DE205 option
deposit command, 3–8
Device information, 3–19
Diagnostic firmware
bootstrapping, 4–2
Diagnostic processes
displaying status, 4–30
Disks
perform read, write, or compare
operations, 4–6
read and non-destructively write
random blocks of data, 4–16
read random blocks of data, 4–14
SCSI testing, 4–11
Document conventions, viii

E
EB164
updating firmware from Alpha SRM
Console, 2–7
updating firmware from Debug
Monitor firmware, 2–6
updating firmware from Windows NT
firmware, 2–4
EB64+
updating firmware, 2–16
EB66+
updating firmware from Alpha SRM
Console, 2–7
updating firmware from Debug
Monitor firmware, 2–6
updating firmware from Windows NT
firmware, 2–4
Environment variables for Alpha SRM
Console commands
auto_action, 3–21
boot_file, 3–21
boot_osflags, 3–21
bootdef_dev, 3–21
console, 3–22
ewa0_mode, 3–22
language, 3–23
oem_string, 3–22
os_type, 3–22
pci_parity setting, 3–22
Environment variables for diagnostic
commands
d_bell, 4–38
d_cleanup, 4–38
d_complete, 4–38
d_eop, 4–38
d_harderr, 4–39
d_oper, 4–39
d_passes, 4–39
d_report, 4–39
d_softerr, 4–40

d_startup, 4–40
d_trace, 4–40
ewrk3_config command, 3–31
ewa0_mode environment variable, 3–22
examine command, 3–12
exer diagnostic command, 4–6
exer_read diagnostic command script,
4–13
exer_write diagnostic command script,
4–15

F
Firmware
description, 1–2
features, 1–2
updating, 2–1, 2–2, 3–15
Firmware update utility
AlphaPC 164, 2–4, 2–6, 2–7
AlphaPC 64, 2–4, 2–6, 2–7
EB164, 2–4, 2–6, 2–7
EB66+, 2–4, 2–6, 2–7
running, 2–10
Flash ROM
updating from the Alpha SRM
Console, 2–7
updating from the Debug Monitor
firmware, 2–6
updating from Windows NT
firmware, 2–4
fwupdate command script, 3–15

G
General-purpose register. See GPR
GPR
displaying contents, 3–14
displaying contents of multiple GPRs,
3–14
loading, 3–11
Index–3

Industry Standard Architecture. See
ISA configuration database; ISA
options
Internal processor register. See IPR
IPR
displaying contents, 3–14
ISA configuration database
displaying, 3–29
modifying a table entry, 3–29
removing a table entry, 3–29
ISA options, 3–24
adding, 3–27
isacfg command, 3–25

nettest diagnostic command, 4–26
Network testing, 4–26, 4–27

Read, write, and compare operations.
See Disks

Keys
Alpha SRM Console, 3–3
kill_diags diagnostic command script,
4–17

L
Language environment variable, 3–23

M
memexer diagnostic command script,
4–19
Memory
clearing a section, 3–11
depositing, 3–11
listing size, 3–19
starting two tests, 4–20
testing a specified section, 4–25
testing all, 4–25
testing for a specified number of
passes, 4–25
testing using random blocks, 4–25
memtest diagnostic command, 4–21
Index–4

O
oem_string environment variable, 3–22
os_type environment variable, 3–22

P
pci_parity environment variable, 3–22

SCSI
testing, 4–11
set command, 3–16
show command, 3–18
show_status diagnostic command script,
4–29
Small Computer System Interface. See
SCSI
Specifying device with address, 3–11,
3–13
Switching to the Alpha SRM Console,
2–12
from Debug Monitor firmware, 2–15
from Windows NT firmware, 2–13
Switching to the Windows NT firmware,
3–17
sys_exer diagnostic command script,
4–31
System-defined environment variables,
3–22

T
test diagnostic command script, 4–34

U
Updating firmware
in a flash ROM, 2–2
in a UVPROM, 2–16
Updating the flash ROM
from the Alpha SRM Console, 2–7
from the Debug Monitor firmware,
2–6

from Windows NT firmware, 2–4
UVPROM
replacing, 2–17
updating firmware, 2–16

W
Windows NT firmware
conventions, 2–4
switching to the Alpha SRM Console,
2–13
updating the flash ROM, 2–4
Write disk operations. See Disks

Index–5