FRU Update Configuration File

27.8Update Commands

The configuration file allows the user to update the FRUs by specifying a target source file. And allow more customization of how the update should proceed with more commands. If the load utility fails at any of the updates, it should exit immediately and report the error. The update commands do not support path names; no error will be generated if a pathname exist.

27.8.1FRUNAME

The FRUNAME command specifies the file name of the FRU to update the system with. Alternately, the name of the FRU file can also be “SYSTEM”, and in that case the FRU will be loaded from the system. In either case, the contents of the FRU specified are not modified unless specified with FRUADDRESS, FRUAREA, and FRUFIELD commands.

The SYSTEM FRU name should be used when you don’t want any inputs from a FRU file and want to change a field by typing in the value or reading from an environment variable.

Example:

FRUNAME “MPCHC001.FRU”

FRUADDRESS chassis

FRUAREA “PRODUCT”

FRUFIELD “P#” // Input from MPCHC001.FRU file

FRUFIELD “S#” “@STDIN:ASCII” // Input from user thru standard input

The configuration file allows the user to select the areas and fields to update through using FRUADDRESS, FRUAREA, and FRUFIELD. By default, no FRU areas are programmed, even if a FRUNAME is given. If the user wants the entire FRU file programmed, then they need to specify all the FRU areas and fields to be programmed.

To update more than one FRU in a configuration, you need to identify a second FRU by using the FRUNAME command again. All FRUADDRESS, FRUAREA, and FRUFIELD commands above the command in the file will have no affect on this new FRU entity. You will need to specify a new address and fields to update.

Example:

FRUNAME “MPCHC001.FRU”

FRUADDRESS chassis

FRUAREA “PRODUCT”

FRUFIELD “P#”

FRUNAME SYSTEM

FRUADDRESS cmm

FRUAREA “BOARD”

MPCMM0001 Chassis Management Module Software Technical Product Specification

233

Page 233
Image 233
Intel MPCMM0001 manual Update Commands, Fruname