Filter
Top Products
MPCMM0001 Chassis Management Module Software Technical Product Specification 227
FRU Update Configuration File
FRU Update Configuration File 27
27.1 Configuration File Format
This section specifies the format for the configuration file used to assist in determining the
configuration of the product. The configuration for a product consists of information about the
product that can be used to select appropriate Field Replaceable Unit (FRU) information to be
loaded into non-volatile storage areas. The information about the product is obtained by identifying
all the boards, sub-assemblies, and components in the product.
The configuration file directs the load utility via a system of commands, probes, requests, and
prompts. The configuration file tells the load utility how to discover the configuration of a product
via probing and user queries. As the Load Utility processes the configuration file, tag values
(sensor ID and descriptive strings) are accumulated and saved. The entire file is processed prior to
the FRU files being programmed.
In programming the FRU areas, the appropriate areas must be specified after the FRU name is
given. If no FRU areas are specified, then the default procedure is to disregard all FRU areas in the
FRU file and leave what was previously programmed in the non-volatile storage device.
27.2 File Format
The configuration file format is ASCII text and is editable. The file consists of commands, data,
and comment fields. There are two data types, strings and numbers. The numeric data values will
be represented in decimal unless specified otherwise by a leading ‘0x’. Strings are consecutive non
white space characters or a double quoted series of printable characters. These strings and numeric
values are formed into fields that make up commands, requests, and prompts. The commands,
requests, and prompts can be formed into combinations and used to obtain the information
necessary to establish a system’s configuration. A line in the configuration file can be commented
out by placing the comment characters (“//”) at the beginning of the line. The comment characters
are effective until the end-of-line character is reached. An example configuration file is shown at
the end of this document. Comment characters can also be used in the middle of the line to
comment out all data on the line after the comment characters.
The extension for the configuration file will be ‘cfg’, case does not matter. If the file does not have
the ‘cfg’ extension, it shall cause an error in the utility.
27.3 String Constraints
• All lines in the file are allowed to be unlimited in length and are terminated with a linefeed.
• All strings with spaces must be enclosed in double quotes. It is recommended that all strings
be enclosed in double quotes.
• The double quote character is not valid within a string (that is, in any position except the
enclosing double quote marks).
• If a null ASCII string is desired, then two double quotes must be inserted as such, “”.