• Aucun résultat trouvé

Configuring and Installing the Bootstrap Loader

Dans le document Host System (Page 87-90)

4. 1 Booting Systems from Disks

4.2 Down-Line Loading

4.2.1.4 Configuring and Installing the Bootstrap Loader

You must configure and install the down-line load bootstrap loader on the target machine. VAX-ll/730- and VAX-ll/750-family processors use the console storage medium (TU58) to store the bootstrap loaders.

MicroVAX processors store the down-line loader in the boot ROM. VAX 8800, 8700, 8550, 8530, and 8500 processors store the loader on a P /05 diskette.

To install the down-line load bootstrap loader on a TU58 console tape, use the VAXELN NEWBOOT command procedure. You should run this procedure from the system manager's account because some operations require the CMKRNL privilege.

The NEWBOOT procedure copies the bootstrap loader's image file to the console medium. This command procedure prompts you for the bootstrap load device (XE=DEUNA), the device containing the console medium on which the loader is to be installed, and the processor type of the target medium, the loader installation is complete.

No configuration is required for a MicroVAX because the down-line loader is contained in boot ROM. However, you may find it useful to set the MicroVAX CPU's configuration dual inline package (DIP) switches to skip disk booting, thus enabling unattended down-line loading of the target machine. See the MicroVAX I Owner's Manual or MicroVAX II Owner's Manual for details.

A P lOS diskette is included in the distribution kit for down-line loading a system image on a VAX 8800, 8700, 8550, 8530, or 8500 processor. For the 8700, 8550, 8530, or 8500, the P lOS diskette contains the following files in the directory [CONSOLE]:

• XEBOOT.EXE - Bootstrap image for DEUNA down-line loading.

• XEABOO.COM - Sample console command procedure for booting the target processor, using the DEUNA.

• ETBOOT.EXE - Bootstrap image for DEBNT down-line loading.

• ETABOO.COM - Sample console command procedure for booting the target processor, using the DEBNT.

• DEFBOO.COM - Sample console command procedure for booting from the DEBNT. This command procedure is invoked when the BOOT command is typed, with no device specified, at the console terminal. The procedure is also invoked directly by trigger booting the system, if the system has a DE UNA, or by the command procedure NMIRESET;COM, if the system has a DEBNT.

• NMIRESET.COM - Sample console command procedure, invoked when a target system is trigger booted, if it has a DEBNT. This command procedure invokes the command procedure DEFBOO.COM.

• RESTAR.COM - Command procedure for restarting the system.

For the 8800, the diskette contains different versions of the these files in the directory [8800]. The file names have 8 appended to them. For example, the 8800 version of XEABOO.COM is XEAB008.COM. The diskette also contains the file [8800]SECB008.COM for booting the secondary CPU on the 8800.

NOTE

To boot an 8800, you must ensure that the right CPU is the primary. The sample command files ETAB008.COM and XEAB008.COM include the SET NEXT_PRIMARY RIGHT command before the INITIALIZE command for this purpose.

To build another copy of the P /05 diskette that contains the files just listed, you can run the command procedure NEWBOOT.COM (normally found in the VAXELN host directory ELN$:). This command procedure prompts you for the bootstrap load device, the device containing the console medium on which the loader is to be installed, and the processor type of the target machine. Answer the questions as follows:

$ SET DEFAULT ELN$

Depending on your target configuration, you may have to edit one or two of the sample command files before using them. If your host system has an RX-50 or RX-33 drive, you can edit the file on your host system using a standard editor. If your host system does not have either of these drives, you can edit the file after you copy it to your P / OS disk device on the target system. See the appropriate console manual for directions on how to edit the file on the target system.

If your system has a DEBNT, you may need to edit the following line in file ETABOO.COM or ETAB008.COM:

DEPOSIT R1 27 !DEBNT is on bi 2, node number 7

The first hexadecimal digit specifies the BI number for the DEBNT and the second hexadecimal digit specifies the node number. If your configuration differs from that, you must edit the line to match your system.

If your system has a DE UNA, you may need to edit the following line in file XEABOO.COM or XEAB008.COM:

DEPOSIT R1 10 IDWBUA is on bi 1, node number 0

The first hexadecimal digit specifies the BI number for the DWBUA (BI-to-UNIBUS converter) and the second hexadecimal digit specifies the DWBUA node number. (The DE UNA itself is specified in the System Builder's Device Driver Menu.) If your configuration differs from that, you must edit the line to match your system.

If your system has a DEUNA, you must also edit the command file DEFBOO.COM or DEFB008.COM. Edit the following lines, changing ETA to XEA:

BOOT ETA I Boot from DEBNT (device type ETA), unit set in I ETABOO.COM

To install the supplied files on your target console system:

1. Exit the console control program.

2. Mount the P lOS diskette in a drive on your target system.

3. Copy the files to the directory BIGVOLUME:[8nnO], where nn is 50 for an 8500 or 8530, 55 for an 8550, 70 for an 8700, and 80 for an 8800, or the directory BIGVOLUME:[CONSOLE]. When you invoke a file, the system first looks on BIGVOLUME:[8nnO]. If the needed file is not there, the system then looks on BIGVOLUME:[CONSOLE].

On an 8800 system, change the name of each file as you copy it, omitting the 8. For example:

$ COPY DZ1:[8800]DEFB008.COM BIGVOLUME:[8800]DEFBOO.COM

Dans le document Host System (Page 87-90)