White Papers

7
 Product Name
 Product Part/Model Number
 Product Version
 Product Serial Number
 Asset Tag
 FRU File ID
 Custom Product Info Fields
MULTIRECORD AREA
MultiRecord Area provides an extension area that can go beyond the standard areas defined in the specification. OEM customers are
free to leverage this area if it meets their requirements, but the structure and use cases of this area are out of scope of this document.
The FRU tool also does not support generating this content.
DEVELOPMENT
The following section provides details on using the Python FRU tool made available to OEM customers along with this white paper to
speed up the process of creating the OEM FRU binary payload.
INI FILE STRUCTURE
The FRU tool requires an INI file as an input in order to generate the binary FRU structure. Sections of this INI file are captured below
with notes explaining how the fields are to be used. It follows the same general structure of the FRU as defined earlier.
COMMON HEADER
[common]
; Version of FRU spec being adhered to – always set to 1
version = 1
; Size of FRU – the OEM FRU space is 1KB in size
size = 1024
; Is Internal Use Area section to be populated
; Tool only parses the [internal] section if this bit is set
internal = 0
; Is Chassis Info Area to be populated
; Tool only parses the [chassis] section if this bit is set
chassis = 0
; Is Board Info Area to be populated
; Tool only parses the [board] section if this bit is set
board = 0
; Is Product Info Area to be populated
; Tool only parses the [product] section if this bit is set
product = 0