
                  FRUSDR Load Utility - Release Notes
               Copyright (c) 2000-2003 Intel Corporation
                          All Rights Reserved
                            February 02, 2004


The FRUSDR Load Utility is an EFI application program used for updating the 
server management subsystem product level Field Replacement Unit (FRU) and 
Sensor Data Repository (SDR) for Itanium(TM) Systems.

This utility is used to update the non-volatile storage device associated 
with the Baseboard Management Controller (BMC), which holds the SDR & FRU 
area. The utility has the capability to generically handle FRU devices that
may not be associated with the BMC.


RELEASE NOTES FOR FRUSDR LOAD UTILITY PACKAGE VERSION 2.0.14

A. CHANGES SINCE PREVIOUS VERSION

   1. This package includes T2SDR14.SDR 
	- Added C0 record to include the SDR Pkg version information
	- Fixed the threshold Hysteresis values overlap issue
	- Incremented the SDR file version number.
   
   2. FRU files version
	- NONE
      
B. DEPENDENCIES

   1. Executes under the EFI Shell ver 0.99 or greater.
   2. IPMI driver is required.
   3. This FRUSDR revision or later is meant to be used with Beta or 
      newer hardware. However, on Alpha systems due to SDR05 enabling 
      some temp and volt sensors, additional SEL entries will be logged
      due to known Alpha heardware issues. Old 'PERI BD FRU' has been 
      renamed as SCSI BP for beta systems.


C. SUPPORTED PLATFORMS

   1. SR870BH2A with BMC v0.15 or later releases. 

D. HOW TO USE THIS UTILITY

The FRUSDR Loader is meant to be used as an EFI application on an Itanium(TM)
server. The utility should be placed onto a floppy or hard drive and the 
system rebooted prior to and after using. There is no need to actually install 
the application on to a server. Running the utility from within an operating
system is not supported and will provide incorrect results. 

The FRUSDR Loader command line provides the following options:

Usage: 
      /? or /H          Displays detailed usage information
      /D SDR            Displays the Sensor Data Records
      /D FRU [Address]  Displays the FRU located at a given Address
      /CFG [Filename]   Uses the specified custom configuration file
      /p                Pauses the display between blocks of data  

(a) Update the SDR records

   1. Boot to EFI shell.

   2. Copy the entire FRUSDR package files to an LS120 or HD:

   3. Load the IPMI driver as follows

            load ipmi.efi

   4. Execute FRUSDR utility as follows

             FS0:>FRUSDR /CFG <filename>

   5. To update the SDR records, select 1 - Load the SDR records.

(b) Display SDR Information

The SDR area can be displayed by using the /D SDR parameter with the FRUSDR 
Command. To display the SDR records from the non-volatile repository:

         FS0:> FRUSDR /D SDR 

(c) Display FRU Information

The /D FRU command displays the FRU located at a given Address. 
The Addressing mode may be "Indirect" or "Direct".

Indirect: FRUSDR /D FRU [NVS_TYPE | DEV_CNTR | NVS_LUN | DEV_ID]
Direct:   FRUSDR /D FRU [NVS_TYPE | DEV_CNTR | NVS_LUN | DEV_BUS | DEV_ADDR]
 
NVS_TYPE - The type of EEPROM, { AT24C02, DS1624S, or IMBDEVICE (default) }
DEV_CNTR - Controller's Address; defaults to 'C20'. Must be prefixed by 'C'.
NVS_LUN  - The LUN; defaults to 'L00'. Must be prefixed by 'L'.
DEV_ID   - The Device ID; defaults to 00. Used only if NVS_TYPE is IMBDEVICE.
DEV_BUS  - The Device's bus; has no default value.
DEV_ADDR - The Device's address; has no default value.

The DEV_BUS and DEV_ADDR are required only if NVS_TYPE is not IMBDEVICE.
If DEV_CNTR is specified, it must be 3 characters in length, including 
the 'C'. All numbers entered for DEV_CNTR, DEV_ID, DEV_BUS, and DEV_ADDR are
interpreted as hexadecimal values, in the range 0 - FF; LUN must be 0, 1, 2 
or 3. The command line arguments may be specified in any order, and if one of
the arguments is not specified then its default value will be used, if it has
one. However, if DEV_BUS and DEV_ADDR are specified, DEV_BUS is assumed to be 
first. If no arguments are specified for [Address] then the BMC FRU will be 
displayed.

    Examples: FRUSDR /D FRU 
              FRUSDR /D FRU IMBDEVICE 00
              FRUSDR /D FRU IMBDEVICE C20 L00 00
              FRUSDR /D FRU AT24C02   09 AA
              FRUSDR /D FRU AT24C02   C20 09 AA
              FRUSDR /D FRU DS1624S   C20 05 90

See the device's FRU file to determine the NVS_TYPE, DEV_CNTR, NVS_LUN, 
DEV_BUS DEV_ADDR, and DEV_ID required to address the device.

(d) FRU Field Lengths

If a user is going to develop their own Configuration, FRU or SDR files, then 
they need a thorough understanding of FRU areas and lengths. That discussion 
is beyond the scope of this document. Although, only a basic understanding of 
how the FRUSDR application uses FRU files is needed before one modifies 
information in a FRU field via a configuration file prompt.

The governing FRU format and specifications do not specify a 
maximum FRU field length. However, a length constraint does exist due to the 
limited amount of space available in the Non-Volatile Storage device 
containing these items. These maximum lengths are artificial since, if all 
strings were of the maximum length, the FRU file would overflow the FRU area. 
Therefore, the true maximum field length is actually controlled by the space 
available to the FRU file. 

As a rule, the length defined in the header of the FRU file and the sizes 
defined in each FRU area of the FRU file must not be altered. These were 
originally chosen so that the FRU file would fit into the FRU area. Often 
each FRU area does contain a certain amount of padding, which will allow an 
increase in the length of some strings. To be on the safe side, if FRU 
strings are modified, they should be kept at the same length as the current 
string in that FRU area. For fields such as the Asset Tag, for which data may 
not exist to fill the field, the length should be kept to as few characters 
as needed, not to exceed 31 characters.

(e) Documentation

Additional information on the FRUSDR Loader may be found in the Product 
Manual, the FRUSDR Loader EPS (External Product Specification), and in 
the FRUSDR Configuration file developers guide.

E. Errata Items and Firmware Dependency

 1. The PROBE PROCESSOR command currently does not work, and will be fixed
    in a future release of this utility.

F. PVCS TAG VERSION

      Project         Tag

   1. CMDS\FRUSDR     FRUSDR_2.0BUILD3
   2. LIB\LIBEFITG    FRUSDR_2.0BUILD3
   3. LIB\LIBBMC      FRUSDR_2.0BUILD3
   4. INCLUDE\EFITG   FRUSDR_2.0BUILD3
   5. INCLUDE\BMC     FRUSDR_2.0BUILD3

G. PACKAGE VERSIONS

Each version of the FRUSDR Loader Utility package contains the FRUSDR Loader
utility program as well as the latest FRU, SDR, and CFG files available at the
time the FRUSDR Package is released.  The package version number is a three 
digit number, (x.y.z), where the first digit (x) specifies the major version 
of the utility, the second digit (y) specifies the minor version of the
utility, and the third digit(z) specifies the version of the package. Below 
is a table indicating which versions of the FRU, SDR, CFG and 
FRUSDR Loader binary files are included in each version of the packages.

Package  
Versions - Utility and File versions

   2.0.14 - FRUSDR Loader Utility v 2.0 Build 3
           CFG Files: Master.cfg
           SDR Files: T2SDR14.SDR
           FRU Files: T2MAIN04.FRU
                      T2SCSIBP05.FRU
                      T2PCIRSR04.FRU

   2.0.13 - FRUSDR Loader Utility v 2.0 Build 3
           CFG Files: Master.cfg
           SDR Files: T2SDR13.SDR
           FRU Files: T2MAIN04.FRU
                      T2SCSIBP05.FRU
                      T2PCIRSR04.FRU

   2.0.12 - FRUSDR Loader Utility v 2.0 Build 3
           CFG Files: Master.cfg
           SDR Files: T2SDR12.SDR
           FRU Files: T2MAIN04.FRU
                      T2SCSIBP05.FRU
                      T2PCIRSR04.FRU

   2.0.11 - NONE

   2.0.10 - FRUSDR Loader Utility v 2.0 Build 3
           CFG Files: Master.cfg
           SDR Files: T2SDR10.SDR
           FRU Files: T2MAIN04.FRU
                      T2SCSIBP05.FRU
                      T2PCIRSR04.FRU

   2.0.09 - FRUSDR Loader Utility v 2.0 Build 3
           CFG Files: Master.cfg
           SDR Files: T2SDR09.SDR
           FRU Files: T2MAIN04.FRU
                      T2SCSIBP05.FRU
                      T2PCIRSR04.FRU

   2.0.08 - FRUSDR Loader Utility v 2.0 Build 3
           CFG Files: Master.cfg
           SDR Files: T2SDR08.SDR
           FRU Files: T2MAIN04.FRU
                      T2SCSIBP05.FRU
                      T2PCIRSR04.FRU

   2.0.07 - FRUSDR Loader Utility v 2.0 Build 3
           CFG Files: Master.cfg
           SDR Files: T2SDR07.SDR
           FRU Files: T2MAIN04.FRU
                      T2SCSIBP04.FRU
                      T2PCIRSR04.FRU

   2.0.06 - FRUSDR Loader Utility v 2.0 Build 3
           CFG Files: Master.cfg
           SDR Files: T2SDR06.SDR
           FRU Files: T2MAIN04.FRU
                      T2SCSIBP04.FRU
                      T2PCIRSR04.FRU

   2.0.05 - FRUSDR Loader Utility v 2.0 Build 3
           CFG Files: Master.cfg
           SDR Files: T2SDR05.SDR
           FRU Files: T2MAIN04.FRU
                      T2SCSIBP04.FRU
                      T2PCIRSR04.FRU

   2.0.04 - FRUSDR Loader Utility v 2.0 Build 3
           CFG Files: Master.cfg
           SDR Files: T2SDR05.SDR
           FRU Files: T2MAIN03.FRU
                      T2SCSIBP03.FRU
                      T2PCIRSR03.FRU

   2.0.03 - FRUSDR Loader Utility v 2.0 Build 3
           CFG Files: Master.cfg
           SDR Files: T2SDR04.SDR
           FRU Files: T2MAIN02.FRU
                      T2SCSIBD02.FRU
                      T2PCIRSR02.FRU

   2.0.02 - FRUSDR Loader Utility v 2.0 Build 3
           CFG Files: Master.cfg
           SDR Files: T2SDR03.SDR
           FRU Files: T2MAIN01.FRU
                      T2PERI01.FRU
                      T2PCIRSR01.FRU


   2.0.01 - FRUSDR Loader Utility v 2.0 Build 3
           CFG Files: Master.cfg
           SDR Files: T2SDR02.SDR
           FRU Files: T2MAIN00.FRU
                      T2PERI00.FRU
                      T2PCIRSR00.FRU

H. TOOLS USED IN BUILD

   1. Intel IA64 SDK Tools v2.0
   2. EFI v1.01.12.33
   3. EFI-AT v1.00 (with support for blkx devices)
   4. MS C/C++ Compiler for IA-64 v6.00.8168

*  Third-party brands and names are the property of their respective owners. 


