vme_config(1M)
NAME
vme_config − VME configuration utility
SYNOPSES
Store configuration to non-volatile memory
vme_config [−f cfgfile] [−D name] [−U name]
Display address map for address modifier
vme_config −m address_modifier [−f cfgfile] [−D name] [−U name]
Display holes in address map for address modifier
vme_config −h address_modifier [−f cfgfile] [−D name] [−U name]
Display entity information
vme_config −e entity_name [−f cfgfile] [−D name] [−U name]
Perform syntax check
vme_config −c [−f cfgfile] [−D name] [−U name]
Display the CPU/card number
vme_config −N
Set the CPU/card number
vme_config −N cpu_number
DESCRIPTION
The vme_config utility creates a VME system configuration by reading required resources from an ASCII configuration file. The configuration file specifies what address ranges each processor, card, or shared memory space occupies, which interrupt levels each processor handles, and assigns other VME resources. The configuration file format is described in vme.CFG(4).
When vme_config is invoked without command line parameters, it generates a configuration from the default file /etc/vme/vme.CFG. 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. For more information on VME configuration and configuration file format, see the "HP−UX VME Configuration and Driver Development Guide".
vme_config should be run before system shutdown to install cards or other processors.
Storing configuration information to non-volatile memory requires that the vme2 device driver be installed in the kernel. The vme2 device driver is in the VME_SERV fileset.
Options
−m address_modifier
Display the address map of the address space indicated by the specified address modifier.
−h address_modifier
Display the holes in the address map of the address space indicated by the specified address modifier. This option is helpful in determining where a new card or CPU can be placed.
−e entity_name
Display information about the specified entity. entity_name is the name of a processor, card, or memory entity declared in the configuration file. This option is useful in determining where vme_config has placed dynamically locatable memory entities. For more information on dynamically configured memory entities, see vme.CFG(4).
−c Perform a syntax check on the configuration file. The configuration is not saved to the system’s non-volatile memory.
−N Print the CPU/Card number of this processor (in decimal) to STDOUT.
−N cpu_number
Change the CPU/Card number of this processor.
−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 the "HP−UX VME Configuration and Driver Development Guide".
1. Edit the configuration file /etc/vme/vme.CFG or other file to reflect the desired VME system. Information on cards or other processors should be provided by the vendor. Information on HP processors is already in the example configuration files in the directory /etc/vme.
2. Execute vme_config on each HP−UX processor in the VME system, using the same configuration file for every processor. vme_config builds a conflict-free configuration, then saves the configuration to non-volatile memory (NVM).
3. Install appropriate drivers and device files.
4. Shut down the system.
5. Install the other processors and cards. Some cards have hardware switches that must be set according to the configuration. Refer to the card’s documentation for information about any hardware switches.
6. Reboot the system. The HP−UX kernel initializes the VME hardware according to the contents of NVM.
EXAMPLES
Loading non-volatile memory with configuration specified in /etc/vme/vme.CFG.
vme_config
Loading non-volatile memory with configuration specified in a different file.
vme_config -f my_cfg.CFG
Changing the CPU number.
vme_config -N 2
Displaying address space generated from a specific file.
vme_config -f my_cfg.CFG -m A24
RETURNS
vme_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. A complete description of the error messages and possible causes can be found in the "Warning and Error Messages" chapter of the "HP−UX VME Configuration and Driver Development Guide".
NOTE
vme_config will ask for confirmation before overwriting the values stored in non−volatile memory.
A system reboot is required before the stored configuration information takes effect.
The vme2 device driver must be in the kernel before vme_config can save configuration information to non-volatile memory. The vme2 driver is in the fileset VME−SERV.
The HP−UX 9.05 version of vme_config always has the following cpp names defined: HPUX and HPUX_90.
AUTHOR
vme_config was developed by HP.
FILES
/etc/vme/vme.CFG The default VME configuration file that vme_config uses.
/etc/vme/example.CFG
An example CFG file showing various record formats.
/etc/vme/example2.CFG
An example CFG file showing a configuration for two HP processors in the same VME system.
/etc/vme/example3.CFG
An example CFG file showing a configuration for many processors and cards in the same VME system.
/etc/vme/system.log This file contains the current system configuration.
SEE ALSO
Hewlett-Packard Company — HP-UX Release 9.05: May, 1994