NAME

bp_config − VME backplane networking configuration utility

SYNOPSES

Store configuration to non-volatile memory

bp_config [−bus|−poll] [−f cfgfile] [−D name] [−U name]

Perform syntax check

bp_config −c [−bus|−poll] [−f cfgfile] [−D name] [−U name]

DESCRIPTION

The bp_config utility creates a VME backplane networking system configuration by reading an ASCII configuration file that specifies the VME address range and space for a memory area that is shared by the CPUs in the system; the number of CPUs that use backplane networking; and other VME resources for the backplane networking driver.  The configuration file format is described in vme.CFG(4).

The bp_config utility uses the same configuration file as the vme_config(1M)utility.  VME Services provide default backplane networking parameters if bp_config is not executed.  These defaults specify the anchor size, position, and address modifier type.  bp_config derives the backplane networking configuration from the bpSharedMem memory entity declaration in the configuration file. 

bp_config checks to see that /dev/bp0 exists, creating it if not. 

When bp_config is invoked without command line parameters, it generates a configuration from the default file /etc/vme/vme.CFG and does not change the interrupt type (bus or poll) that was set by its previous execution.  (If no interrupt type has been previously specified, bp_config assumes bus interrupts.)  The configuration information for the current CPU is saved to the system’s non-volatile memory. 

The current CPU is identified by the CPU number stored in non-volatile memory.  This value may be changed by using the -N cpu_number option of the vme_config(1M) command.  For more information on VME configuration and configuration file format, see the HP-UX 10.20 VME Services Guide.

Storing configuration information to non-volatile memory requires that the vme2 and bp device drivers be installed in the kernel.  The vme2 device driver is in the VME_SERV fileset. 

Options

−bus Configure backplane networking to use VME bus interrupts.  One or more VME bus interrupt levels must be assigned to this CPU in the configuration file.  If no interrupts are assigned, backplane networking will poll instead. 

−poll Configure backplane networking to use polling. 

−c Perform a syntax check on the configuration file.  The configuration is not saved to the system’s non-volatile memory. 

−f cfgfile
Use the specified configuration file instead of /etc/vme/vme.CFG. 

−U name Passed to cpp to remove any initial definition of name. 

−D name

−D name=def
Passed to cpp to define name as if by a #define directive.  If no =def is given, name is defined as 1.  The -D option has lower precedence than the -U option.  Thus, if the same name is used in both a -U option and a -D option, the name is undefined regardless of the order of the options. 

Configuration Process

To configure a VME system, follow these steps.  For further information, refer to vme_config(1M) or the HP-UX 10.20 VME Services Guide.

1.  Edit the configuration file /etc/vme/vme.CFG or another file to reflect the desired VME system.  This file must include the bpSharedMem memory entity. 

2.  Execute vme_config(1M) on each HP−UX processor in the VME system, using the same configuration file for every processor. 

3.  Execute bp_config on each HP−UX processor that will use backplane networking, using the same configuration file for every processor. 

4.  Reboot the systems.  The HP−UX kernels will initialize VME backplane networking according to the contents of the non-volatile memory as created in the previous step. 

EXAMPLES

Load non-volatile memory with the configuration specified in /etc/vme/vme.CFG, and do not change the interrupt type, which is assumed to be bus if this is the first execution:

bp_config

Load non-volatile memory with the configuration specified in a different file, and set backplane networking to use VME bus interrupts:

bp_config -bus -f hpux_bp.CFG

Load non-volatile memory with the configuration specified in a different file, and set backplane networking to poll:

bp_config -poll -f my_cfg.CFG

RETURNS

bp_config returns an exit code of 0 if successful.  An exit code of 1 indicates a syntax error in the configuration file.  An exit code of 2 indicates an internal or system error. 

Error messages will be displayed to STDOUT. 

NOTES

bp_config will ask for confirmation before overwriting the values stored in non−volatile memory. 

The stored configuration information does not take effect until the system is rebooted. 

The vme2 and bp device drivers must be in the kernel before bp_config can save configuration information to non-volatile memory.  The vme2 driver is in the fileset VME−SERV.  The bp driver is in the fileset HPUX−BP. 

AUTHOR

bp_config was developed by HP. 

FILES

/etc/vme/vme.CFG The default VME configuration file that bp_config uses. 

SEE ALSO

vme_config(1M), vme.CFG(4), cpp(1).

Hewlett-Packard Company  —  HP-UX Rel. 10.20: August, 1996