Intel NetStructure® MPCBL0010 Single Board Computer
October 2006 Technical Product Specification
Order Number: 304120 127
Hardware Management Overview—MPCBL0010 SBC
10.6 Customizable FRU Area
The LinuxCustFru utility is a Linux utility that runs directly on the MPCBL0010 SBC
and is available on the Intel web site. This utility can be used to read data from a file
and write it to the existing Field Replaceable Unit (FRU) information storage area on the
MPCBL0010 SBC, or it can be used to purge any existing customer area in the FRU. The
MPCBL0010 SBC provides 512 bytes of space for users to store custom FRU
information. The FRU file complies with the IPMI Platform Management FRU
Information Storage Definition v1.0.

10.6.1 LinuxCustFru Utility Usage

Running the LinuxCustFru utility with a FRU filename argument causes it to read in
the customer area MRA record from the FRU file and write it to the FRU of the blade. If
there is no valid customer area MRA record in the FRU file, nothing is written to the FRU
(FRU is unchanged):
LinuxCustFru filename.fru
Running the LinuxCustFru utility with the "-p" argument, without a FRU filename,
causes it to purge any existing customer area MRA record in the FRU area of the blade.
If there is no valid customer area MRA record within the FRU on the blade, the FRU is
left unchanged:
LinuxCustFru -p
Running the utility without arguments shows usage information and some examples of
usage:
LinuxCustFru
Usage: ./LinuxCustFru [-p | fileName]
Where:
fileName = FRU file containing customer record (writes to the SBC). Omitting the
filename clears the customer area of the FRU.
-p: purge / write customer area of FRU.
-v: verbose - show read/write data.
Examples:
./LinuxCustFru filename.fru
Reads customer area MRA record from filename.fru, writes it into the FRU of the SBC.
./LinuxCustFru -p
Purges customer area MRA record from the MPCBL0010 SBC FRU, if present.

10.6.2 FRU Customer Area

The FRU customer area consists of one or more OEM MRA records with a Record Type
ID of ‘0xC1’. Platform Management FRU Information Storage Definition v1 provides
more information about the format of the MRA records.
Multiple C1 records are needed to program more than 252 bytes of customer data into
the FRU. The specification limits the size of the OEM records in the MRA to 255 bytes.
Of these 255 bytes, the first three bytes are reserved by the specification for a three-
byte manufacturer’s ID, as described in the FRU Storage Definition.