f. OpenVMS FAQ -&- page 22)b @5z

HP OpenVMS Systems Documentation

 q> $"b,
Content starts here"D

The OpenVMS Frequently Asked Questions (FAQ)


 l n  
PreviousContentsIndex

K

14.3.5.3 What are the VAX VMB boot flag values?



|The flags described in Table 14-3 are passed (via register R5) toDthe OpenVMS VAX primary bootstrap image VMB.EXE. These flags control.the particular behaviour of the bootstrap.

n   # &                                                                             
Table 14-3 VAX Conversational Bootstrap Flags
Bit Mnemonic Description
 0 CONV J Conversational boot. At various points in the system boot procedure,L the bootstrap code solicits parameter and other input from the consoleK terminal. If DIAG is set, then the diagnostic supervisor should enter< its menu mode and prompt user for the devices to test.
 1 DEBUG J Debug. If this flag is set, OpenVMS VAX maps the code for the XDELTAA debugger into the system page tables of the running system.
 2 INIBPT K Initial breakpoint. If RPB$V_DEBUG is set, OpenVMS VAX executes a BPT5 instruction immediately after enabling mapping.
 3 BBLOCK I Secondary boot from the boot block. Secondary bootstrap is a single3 512-byte block, whose LBN is specified in R4.
 4 DIAG G Diagnostic boot. Secondary bootstrap is the Diagnostic Supervisor image; the image & [SYSMAINT]DIAGBOOT.EXE.
 5 BOOBPT K Bootstrap breakpoint. Stops the primary and secondary bootstraps with@ an XDELTA breakpoint instruction prior to the memory test.
 6 HEADER I Image header. Takes the transfer address of the secondary bootstrapI image from that file's image header. If the RPB$V_HEADER bit is notG set, the image is assumed to have no image header, and control is> transfered to the first byte of the secondary boot file.
 7 NOTEST I Memory test inhibit. Sets a bit in the PFN bit map for each page of/ memory present. Does not test the memory.
 8 SOLICT H File name. VMB prompts for the name of a secondary bootstrap file.
 9 HALT K Halt before transfer. Executes a HALT instruction before transferring) control to the secondary bootstrap.
 10 NOPFND J No PFN deletion (not implemented; intended to tell VMB not to read aM file from the boot device that identifies bad or reserved memory pages,H so that VMB does not mark these pages as valid in the PFN bitmap).
 11 MPM G Specifies that multi-port memory is to be used for the total EXECD memory requirement. No local memory is to be used. This is forE tightly-coupled multi-processing. If the RPB$V_DIAG bit is alsoG enabled, then the Diagnostic Supervisor enters its AUTOTEST mode.
 12 USEMPM J Specifies that multi-port memory should be used in addition to local; memory, as though both were one single pool of pages.
 13 MEMTEST I Specifies that a more extensive algorithm be used when testing main5 memory for hardware uncorrectable (RDS) errors.
 14 FINDMEM  Requests the use of MA780 1 multiport memory if the main MS780 S memory is insufficient for booting. This is a remnant of the support for the Q VAX-11/782 series system and its Asymmetric Multiprocessing (ASMP) V environment. Support for the VAX-11/782 and for ASMP was withdrawn withS the V5.0 release; with the advent of Symmetric Multiprocessing (SMP)  support.


EThe exact syntax is console-specific, recent VAX consoles tend to usethe following:

 

"
  >>> BOOT/R5:flags


_

14.3.6 How do I boot an AlphaStation without monitor or keyboard?



GThe AlphaStation series will boot without a keyboard attached. To use aAserial terminal as the console, issue the SRM console command SETBCONSOLE SERIAL followed by the console INIT command. Once this SRMFcommand sequence has been invoked and the CONSOLE environment variableEis set to SERIAL, the Alpha system will use the serial terminal. (SetBthe environment variable to GRAPHICS to select the console display!output via the graphics display.)

EThe DEC 3000 series has a jumper on the motherboard for this purpose.CVarious older Alpha workstations generally will not (automatically)Dbootstrap without a keyboard connected, due to the self-test failure3that arises when the (missing) keyboard test fails.

BThe usual settings for the console serial terminal (or PC terminal(emulator acting as a serial console are:

 

"
<9600 baud, 8 bits, no parity, one stop bit (9600 baud, 8N1).




GAlphaServer 4100 and derivative series platforms, and AlphaServer GS80,FGS160, and GS320 series system consoles are capable of 57600 baud. SeeDthe COM2_BAUD console environment variable, and ensure that you have$current SRM firmware version loaded.

FThe AlphaStation and AlphaServer series use a PC-compatible DB9 serialconnector for the COM1 and COM2E serial lines (and for the OPA0: console line, if that was configuredq via SRM), please see Section 14.26 for details and pin-out.

EFor information on registering software license product authorization[keys (PAKs), please see Section 5.6.2.

yFor a related behaviour of DECwindows, please see Section 11.10. ForFinformation on the VAXstation alternate console mechanisms, please seeESection 14.3.3.3.T

14.3.7 Downloading and using SRM console Firmware?



DThis section discusses downloading and using Alpha console firmware,sometimes called PALcode.b

14.3.7.1 Where can I get updated console firmware for Alpha systems?



9Firmware updates for HP Alpha systems are available from:



?The latest and greatest firmware---if updated firmware has beenGreleased after the most recent firmware CD was distributed---is locatedat:



BFor information on creating Alpha bootable floppies containing the@firmware, and for related tools, please see the following areas:



GThe SROM firmware loader expects an ODS-2 formatted floppy, see mkboot.CAs for which image to use, the ROM image uses a header and the fileFextension .ROM, and the SROM bootable floppy cannot use the .ROM file.

ETo check the firmware loaded on recent OpenVMS Alpha systems, use thecommand:

 

"
.$ write sys$output f$getsyi("console_version").$ write sys$output f$getsyi("palcode_version")SDA> CLUE CONFIG




}Also see Section 14.3.7.2. For information on HP Integrity EFI firmwareDupgrades and for a sequence useful in generating CD-R or CD-RW mediaqcontaining a firmware disk image, please see Section 14.3.11.b

14.3.7.2 How do I reload SRM firmware on a half-flash Alpha system?



BSome of the AlphaStation series systems are "half-flash"Aboxes, meaning only one set of firmware (SRM or AlphaBIOS) can be@loaded in flash at a time. Getting back to the SRM firmware when;AlphaBIOS (or ARC) is loaded can be a little interesting...

GThat said, this usually involves shuffling some files, and then getting>into the AlphaBIOS firmware update sequence, and then entering."update srm" at the apu-> prompt.

GTo shuffle the files, copy the target SRM firmware file (as200_v7_0.exe@is current) to a blank, initialized, FAT-format floppy under thefilename A:\FWUPDATE.EXE

EFrom the AlphaBIOS Setup screen, select the Upgrade AlphaBIOS option.3Once the firmware update utility gets going, enter:

 

"
     Apu-> update srm0           Answer "y" to the "Are you ready...?"     Apu-> quit




@You've reloaded the flash. Now power-cycle the box to finish theprocess.

OAlso see Section 14.3.7.1._

14.3.7.3 How do I switch between AlphaBIOS/ARC and SRM consoles?



FThe specific steps required vary by system. You must first ensure thatGthe particular Alpha system is supported by OpenVMS (see the SPD), thatGall core I/O components (graphics, disk controllers, etc) in the systemDare supported by OpenVMS (see the SPD), and that you have an OpenVMSGdistribution, that you have the necessary license keys (PAKs), and that+you have the necessary SRM firmware loaded.

FA typical sequence used for switching over from the AlphaBIOS graphics#console to the SRM console follows:

    ?
  1. Press [F2] to get to the AlphaBIOS setup menu..
  2. Pick the "CMOS Setup..." item.I
  3. Press [F6] to get to the "Advanced CMOS Setup" menu.G
  4. Change the "Console Selection" to "OpenVMS Console (SRM)".G
  5. Press [F10], [F10], then [Enter] to save your changes.
  6. Power-cycle the system.


EMost Alpha systems support loading both the AlphaBIOS/ARC console andFthe SRM console at the same time, but systems such as the AlphaStation255 are "half-flash"F systems and do not support the presence of both the AlphaBIOS/ARC and5 SRM console firmware at the same time. If you have aC "half-flash" system, you must load the SRM firmware fromF floppy, from a network download, or from a firmware CD-ROM. FollowingH the normal AlphaBIOS or ARC firmware update sequence to the APU prompt,G and then explictly select the target console. In other words, power upB the system to the AlphaBIOS or ARC console, use the supplementaryC options to select the installation of new firmware (typically fromA CD-ROM), and then rather than using a sequence which updates the current firmware:

 

"
    Apu-> updates
      -or-    Apu-> update ARCm    Apu-> verify     Apu-> quita    Power-cycle the system

i


eEUse the following sequence to specifically update (and load) SRM froma1AlphaBIOS/ARC on a "half-flash" system:<

> 
<
"
    Apu-> update SRM     Apu-> verifyp    Apu-> quitm    Power-cycle the system

P


D@Use the following sequence to specifically update (and load) theBAlphaBIOS/ARC console from SRM on a "half-flash" system:

c 
-
"
     >>> b -fl 0,A0 ddcu$    BOOTFILE: firmware_boot_file.exe    Apu-> update ARCn    Apu-> verifyi    Apu-> quito    Power-cycle the system




tGOnce you have the SRM loaded, you can directly install OpenVMS or Tru64>UNIX on the system. Do not allow Microsoft Windows NT or otherDoperating system(s) to write a "harmless" signature to anyEdisk used by OpenVMS Alpha or OpenVMS VAX, as this will clobber a key"@part of the disk; this will overwrite the OpenVMS bootblock. (OnBOpenVMS Alpha and OpenVMS VAX, you can generally recover from thisFso-called "harmless" action by using the WRITEBOOT.EXE tool. c=

_?Using OpenVMS I64 and the EFI console, the bootblock structuresd"Gare expected to be compatible with those of Microsoft Windows and otherhAIntegrity operating systems; please see the discussion of the SETl/BOOTBLOCK command and the SYS$SETBOOT.EXE imagenp 0in Section 9.7.3, in Section 14.3.9, and in the OpenVMS documentationfor related details.) 

nFIf you have a "full-flash" system and want to select the SRMAconsole from the AlphaBIOS or ARC console environment, select the A"Switch to OpenVMS or Tru64 UNIX console" item from thetF"set up the system" submenu. Then power-cycle the system. IfFyou have a "full-flash" system with the SRM console and want)to select AlphaBIOS/ARC, use the command:u

s 
l
"
   >>> set os_type NT

s


oand power-cycle the system.d

ruFor information on acquiring firmware, see Section 14.3.7.1. For:information on OpenVMS license PAKs (for hobbyist use) seeSection 2.8.1. For information on the Multia, see Section 14.4.1.

oBInformation on enabling and using the failsafe firmware loader forDvarious systems---this tool is available only on some of the variousDAlpha platforms---is available in the hardware documentation for theFsystem. This tool is used/needed when the firmware has been corrupted,and cannot load new firmware.>

EThe full list of AlphaBIOS key sequences---these sequences are needed Gwhen using an LK-series keyboard with AlphaBIOS, as AlphaBIOS expects aiPC-style keyboard:

 

"
         F1   Ctrl/A         F2   Ctrl/B         F3   Ctrl/C         F4   Ctrl/D         F5   Ctrl/E         F6   Ctrl/F         F7   Ctrl/P         F8   Ctrl/R         F9   Ctrl/T        F10   Ctrl/U     Insert   Ctrl/V     Delete   Ctrl/W  Backspace   Ctrl/H     Escape   Ctrl/[     Return   Ctrl/M   LineFeed   Ctrl/J%   (Plus) +   upselect (some systems)s'  (Minus) -   downselect (some systems)c        TAB   down arrow   SHIFT+TAB  up arrow

=
<

14.3.8 Console Management Options



d=Options to collect multiple consoles into a single server are Davailable, with both hardware options and software packages that can+provide advanced features and capabilities.e

i=Some of the available console management options for OpenVMS:f dl  t.p

o

>Computer Associates is the owner of what was once known as theCVAXcluster Console System (VCS) console management package, and hasV@integrated this capability into the CA management product suite.mJ

14.3.9 Why do my EFI Boot Aliases Fail?

>t

FOpenVMS I64 boot aliases contain signature information referencing theBspecific volume, meaning that the entries are specific to the disk<volume and not the disk device. This also means that certain8operations, such as the SET BOOTBLOCK command or the RUNSYS$SETBOOT.EXE operationi  Gthat can rewrite these volume signatures (signature or GUID values) canrd&render existing boot aliases unusable.

rDIf your boot aliases do not function as expected, first try removingEand re-adding them; this will resynchronize the boot aliases with theBvolume contents. If you are using the SET BOOTBLOCK command or theo DRUN SYS$SETBOOT.EXE operation to rewrite the disk bootblock, you canCrequest that the current signatures (if any) be preserved, and thisuFwill typically maintain the validity of your EFI console boot aliases.W

14.3.10 Can OpenVMS access the EFI console Boot Aliases?



For access to the EFIir. console environment from OpenVMS I64, see theVC BOOT_OPTIONS.COM command procedure, and the EFI SET, SHOW and BCFG = mechanisms. Details on these are in the System Manager's andn7 particularly in the System Manager's Utilities manual.w

yFor related information on boot aliases, please see Section 14.3.5.1. P

14.3.11 Downloading and using EFI Console Firmware?



CHP Integrity EFI system firmware can be downloaded in the form of aaDbootable image master, unzipped and then burned onto CD or DVD mediar(please see Section 9.7 for details of recording optical mediaEdirectly on OpenVMS), and the system can then generally be booted offt6the created media to perform the EFI firmware upgrade.

aEThe HP Integrity Server website is accesssable via the following URL,rEand the available services and support information there has links toLCthe available platform-specific firmware images and upgrade-relatede materials:

i u

aETo use the following sequence, you will need a writable or rewritablexDCD drive and software, and a blank CD-R or CD-RW disk. If you use CDEwriter software for another platform, you will want to use the block,sAbinary, ISO or raw mode operations appropriate for the particulart@chosen recording package. The following directions assume use oftOpenVMS and native CD-R capabilities, please see Section 9.7 forassociated details.e

    aD
  1. First, you must acquire the Integrity server firmware from the@ above URL. Select the platform, and navigate to the supportingH information and specifically to the Download Drivers and Software link:
  2. Select Cross operating system (BIOS, Firmware, etc.)H
  3. Locate the appropriate ISO-format firmware file. There are severalE firmware file formats available and there are also various off-linen9 diagnostic images, choose the ISO-format firmware file.iB
  4. Read the directions for the firmware file, then download theG ISO-format firmware (zip-compressed) file. A binary-mode FTP transfern should be used.<
  5. Unzip= F the file into the corresponding .ISO data file. Somewhat confusingly,G the .ISO extension can indicate either a block-oriented raw image of a.F disk, or a disk with the ISO-9660 volume structure. In this case, theG former is intended and this file contains a a block copy or disk images@ of the firmware disk for the platform, and may or may not be anfF ISO-9660 volume structure. The unzip tool is available on the OpenVMSv Freeware and elsewhere; please see Section 13.11 for details and locations..@
  6. Use CDRECORD or other available recording tool (please seet Section 9.7 for related details) to burn a CD-R or CD-RW disk,? specifying the ISO file as the source for the burn operation.3E
  7. Shut the Integrity Server system down to the EFI console level. E
  8. Unload the recorded CD media from the CD-R drive, label it, andF load it into the Integrity console drive. This assuming the disk wasJ not generated directly on an Integrity CD-R/RW-capable drive, of course.I
  9. Using the EFI shell, display the current firmware version using thex command

    > 
    /
    "
    info fwh
    
    
    F

  10. Exit the EFI shell and select the boot options maintenance menu;G create a boot alias for the removable media drive for the CD; for thel newly-created firmware disk.I
  11. Boot it. Follow the directions displayed by the firmware loader andeE related documentation, heeding the release notes that were reviewed earlier.5
  12. Perform a cold restart of the Integrity server.h
a

rBFor information on Alpha SRM console firmware upgrades, please seeHSection 14.3.7.m

14.4 What platforms will OpenVMS operate on?

e

"CFor the list of boxes that are officially and formally supported by<OpenVMS Engineering, please see the OpenVMS Software ProductDescription (SPD).

/

iDSometimes a particular and officially unsupported Alpha box or Alpha?motherboard will sufficiently resemble a supported box that the/9platform can effectively mimic and can bootstrap OpenVMS.mAAlternatively, somebody (usually one or more engineers within theeDOpenVMS Engineering group) will have put together a bootstrap kit --?such as the kit for the Alpha Multia---which permits OpenVMS todbootstrap on the platform.

CContrary to the assumptions of some folks, there are platform-level=Adifferences even within the VAX and within the Alpha platforms--- Ehardware-level differences that can require moderate to extensive newyAcoding within OpenVMS. Within a platform series, and particularlyl?within Alpha platforms (and those few VAX systems) that supporthrE@Dynamic System Recognition (DSR), OpenVMS can usually bootstrap.

-@DSR is a mechanism by which OpenVMS can gather platform-specificFinformation, and DSR is the reason why newer Alpha systems can be moreGeasily and more commonly supported on older OpenVMS Alpha releases. DSRyGis implemented with OpenVMS Alpha code, with SRM console code, and with;platform non-volatile memory.g

nCOpenVMS users with experience on older OpenVMS VAX releases and VAXmAhardware will recall that then-new VAX systems either required andBOpenVMS VAX upgrade, or that earlier releases would mis-identifiedCthen-newer VAX systems---such as the case of the VAX 7000 model 800fBbeing (mis)identified as a VAX 7000 model 600 when bootstrapped onBOpenVMS VAX V5.5-2. (This (mis)identification was the outcome of aAdeliberate engineering effort to permit the VAX 7000 model 800 toaDbootstrap on V5.5-2; the system manager could configure the VAX 7000Fmodel 800 to (mis)identify itself as a model 600, to permit the systemHto bootstrap on V5.5-2.) OpenVMS VAX and VAX platforms lack DSR support.

OpenVMS I64  ipx(please see Section 14.4.5 for Intel Itanium terminology) supports aBplatform-level feature similar to the OpenVMS Alpha DSR mechanism, based on ther@ ACPI interface and the byte-code interpreter implemented withinF OpenVMS, within the EFI console, and particularly within non-volatileF memory located on (byte-code interpreter compliant) PCI I/O hardware.E ACPI tables provide the information that was formerly retrieved fromMH DSR and from the SRM, and the byte-code interpreter can (theoretically)B permit at least limited operations with (compliant) PCI hardware,A whether or not OpenVMS has a driver for the particular hardware. 

CThe byte code interpreter may or may not permit operations with anyGparticular PCI hardware, and may or may not have sufficient performancepCfor local requirements, and PCI hardware may or may not include therEnecessary ROM-based drivers in the PCI hardware non-volatile storage.eC(The intent of this Intel platform-level effort is to move the hosttFsoftware drivers out onto the specific PCI hardware, and to permit theFsame byte code to operate regardless of the particular host platform.)CAt least the initial releases of OpenVMS I64 will not haveEsupport for the byte code interpreter nor for arbitrary PCI or systemDhardware, but will have support for ACPI-based system identificationand system configuration.s 

l


 i l n  
PreviousNextContentsIndex

 

o#s6- rather than using a sequence which updates the current firmware:

 

"