Specifications

Futurebus+ Bus Support

15.9 Conﬁguring a Futurebus+ Adapter

Manual conﬁguration of adapters is very similar across platforms and buses.

There are some bus-speciﬁc differences, usually in the format of the base

CSR address and in the speciﬁcation of the interrupt vector(s). The SYSMAN

utility is used to manually conﬁgure adapters. In order to manually conﬁgure

a Futurebus+ adapter, the ﬁrst step is to issue the SYSMAN IO SHOW BUS

command. This command uses the ADP list (pictured in the DEC 4000 and DEC

10000/7000 chapter) to display information on all of the I/O options that are

present in the system.

The SYSMAN IO CONNECT command is used to actually conﬁgure an adapter.

For a Futurebus+ adapter, this command should be issued as follows:

SYSMAN> IO CONNECT devname /adapter=x /csr=y /node=w /vec=z

/driver=yourdriver.exe

The devname parameter should be speciﬁed in the standard device naming

format–a 2 letter device code, controller letter, and unit number (such as

XXA0). The ADAPTER parameter should be speciﬁed as the TR number of the

Futurebus+ ADP. This is part of the SYSMAN IO SHOW BUS display. The csr

parameter is the base of Futurebus+ Initial Node Space for the adapter. This is

an A32 Futurebus+ address in Futurebus+ CSR space. The value speciﬁed in

the "csr" parameter is copied directly to the IDB$Q_CSR ﬁeld in the IDB by the

SYS$LOAD_DRIVER program. The /node parameter speciﬁes the Futurebus+

node number of the adapter. The node number is part of the SYSMAN IO SHOW

BUS display. The /node parameter is copied to the CRB$L_NODE ﬁeld in the

CRB by the SYS$LOAD_DRIVER program. The /driver parameter is the ﬁle

name of the driver. The vec parameter speciﬁes the interrupt vector to be used

by this Futurebus+ adapter. If the adapter and driver use multiple interrupt

vectors, they must be explicitly listed as follows:

/vec = (vec1, vec2, vec3, ...)

You must be careful when specifying interrupt vectors not to use one that is

already in use by another driver/adapter. OpenVMS/AXP maintains a data

structure which keeps track of which SCB vectors are in use. This is shown in

Figure 15–6.

15–9