=============================================================================
Intel(R) S7000FC4UR Server Platform FRUSDR Load Utility RELEASE NOTES
=============================================================================
Intel Enterprise Platform & Services Division - Marketing
Intel Corporation
2800 Center Drive, DuPont, WA 98327 USA
=============================================================================
DATE: 	    Mar 10, 2008
TO:         Intel(R) S7000FC4UR Server Platform customers
SUBJECT:    FRUSDR Release Notes
=============================================================================
                               LEGAL INFORMATION
=============================================================================
Information in this document is provided in connection with Intel products.
No license, express or implied, by estoppel or otherwise, to any intellectual
property rights is granted by this document. Except as provided in Intel's
Terms and Conditions of Sale for such products, Intel assumes no liability
whatsoever, and Intel disclaims any express or implied warranty, relating to
sale and/or use of Intel products including liability or warranties relating
to fitness for a particular purpose, merchantability, or infringement of any
patent, copyright or other intellectual property right. Intel Corporation may
have patents or pending patent applications, trademarks, copyrights, or other
intellectual property rights that relate to the presented subject matter.
The furnishing of documents and other materials and information does not
provide any license, express or implied, by estoppel or otherwise, to any
such patents, trademarks, copyrights, or other intellectual property rights.
Intel products are not intended for use in medical, life saving, or life
sustaining applications. Intel may make changes to specifications and product
descriptions at any time, without notice.

Intel is a registered trademark of Intel Corporation.

*Other names and brands are the property of their respective owners.

Copyright (c) 2008 Intel Corporation.

=============================================================================
                              ABOUT THIS RELEASE
=============================================================================

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

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.


=============================================================================
                             DEPENDENCIES
=============================================================================
- Executes under the EFI Shell.

=============================================================================
                           SUPPORTED PLATFORMS
=============================================================================
Intel(R) S7000FC4UR Server platform.

=============================================================================
SYSTEM SOFTWARE REQUIREMENTS/REVISIONS
=============================================================================
- BMC Firmware version: BMC17 or later.
- BIOS version: R0019 or later.

=============================================================================
                              KNOWN ISSUES
=============================================================================
- An issue with an I2C repeater device on the fab 1 baseboard prevents the
BMC from acquiring data from S1 power supplies using the PSMI
interface.  The FRUSDR loader utility will detect the PSMI interface of the
power supply and load the related sensors, but they will not read properly.
Temperature sensors may show as "reading unavailable," and status sensors
may generate "configuration error" SEL events.  This is expected to be
addressed on fab 2, and rework may be available later for fab 1 boards.
See SSPD Products Tracker 49166 for more details.

- If S0 or Harwich power supplies are used, the PS1 status sensor will
always show "configuration error" because the PSMI interface is not active.
Corresponding SEL events will be generated.

- NOTE FRUSDR loader hangs sometimes while updating the FRU.

=============================================================================
                           HOW TO USE THIS UTILITY
=============================================================================
The FRUSDR loader is meant to be used as an EFI application on a server. The
utility should be placed onto a floppy diskette, USB key fob, or hard drive.
There is no need to actually install the application onto the server. Running
the utility from within an operating system is not supported and may 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 both FRU and SDR files with the master config file using the below command or with autoexec.nsh file

    FRUSDR /CFG master.cfg

(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:

    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.

=============================================================================
                   FEATURES ADDED/CHANGED IN THIS RELEASE
=============================================================================
FFC_14:
  NONE

FFC_13:
- Remove sensor number 0x7C.
- Sorting the Record ID in the SDR file.

FFC_12:
- Update SDR as per Foxcove SDR Tables - New Format - V15.xls

FFC_11:
- Update SDR as per Foxcove SDR Tables - New Format - V13.xls
- Changed the FRUSDR loader to  1.0.4 Alpha build 4.
- Removed HSC backplane sensor monitoring.

FFC_10A:
- This package is same as FFC_10. Only the FRUSDR loader is updated to Version 1.0.4 Alpha build 3

FFC_10:
- Removed SDR_TAG "ALL" from auto detected sensors.

FFC_09A:
- Mother board FRU size is changed from the previous package. So we need to flash mother
  board FRU first and then run the package to update other areas. To automate this,
  autoexec.nsh file is provided to update the whole package.

FFC_09:
- Update SDR as per Foxcove SDR Tables - New Format - V11.xls
- Update OLTT/CLTT parameters as per Foxcove SDR Tables - New Format - V11.xls.
- Update Sensor Name as per FoxCove BMC EPS v1.01.
- Enhance Chassis info area size in mother board FRU.
- Add 'SHP','FCT1', 'FCT2' Tags for factory, and 'ALL' Tag for end user.

FFC_08:
- Update SDR as per Foxcove SDR Tables - New Format - V6.xls.
- Update OLTT/CLTT parameters as per Foxcove SDR Tables - New Format - V6.xls.

FFC_07A:
- Added BMC_REFRESH after updating the SDRs
- BIOS setup will show the FRUSDR version as 07.

FFC_07:
- Add platform check at beginning of FRU/SDR update.
- Update SDR as per Foxcove SDR Tables - New Format - V4.xls.
- Update OLTT/CLTT parameters as per Foxcove SDR Tables - New Format - V4.xls.
- Removed Diff Sensors in SDR table.

FFC_06A:
- Updated Mother board fru with Board id as S7000FC4UR.
- Changed the file name from FC4_MB1.FRU to FC4_MB2.FRU
- changed master.cfg from FC4_MB1.FRU to FC4_MB2.FRU
- BIOS setup will show the FRUSDR version as 06.

FFC_06:
- Updated SDR as per FSC SDR Foxcove v2.xls.
- Updated real fan speed thresholds as per Fox Cove Configuration Sheet v1.xls.
- Updated Sensor Names for the Fan Tach signals as per Fox Cove Configuration
  Sheet v1.xls.
- Updated the FRUSDR utility from v1.0.3 Alpha 2 to v1.0.3 Alpha 3.

=============================================================================
                        ISSUES FIXED IN THIS RELEASE
=============================================================================
FFC_14:
- Tracker #32499:[WHQL]  SMBIOS HCT Test fails on Fox Cove w/ FRU error

FFC_13:
  NONE

FFC_12:
- Tracker #31997: Foxcove SDR Table Change Rev 14.
- exchange boost control value & sleep control value in fan control domain 1.

FFC_11:
- Tracker #30871: FRUSDR - Mem Aggregate Scan Rate change.
- Tracker #30882: Model 0 Config - Text should be changed.
- Tracker #31083: Up-loaded SDR Table Version  13 to Eroom
- Tracker #31296: Master.cfg reference to SDR file causes Juntura update to fail
- Tracker #31374: BMC - HSC communication causing LCP update to fail and degrade the performance
- Tracker #31026: FoxCove: FRUSDR 1.0.4 Build3: frusdr /d fru imbdevice 00 C0 comd fails on 401 br

FFC_10A:
  NONE

FFC_10:
  NONE

FFC_09A:
  Workaround added to support the change in mother board FRU size.

FFC_09:
- Tracker #29656: The sensor name verification for FFC_06 is failed.
- Tracker #29821: [SMBIOS] The Product Name string in Type 1 and Type 2 are failed.
- Tracker #30468: (X) Power Supply Predictive Failure Event.
- Tracker #30695: UNC/UC thresholds not working for FBDIMM Sensors.
- Tracker #30696: No clamping on Baseboard Sensor.
- Tracker #30697: HSBP sensor thresholds wrong.
- Tracker #30732: Enhance chassis info area size in mother board FRU.

FFC_08:
- Tracker #29655: The Upper non-critical value verification for FFC_06 is
  failed.
- Tracker #30333: Change the HSC sensor offsets for sensor number #2 to #9

FFC_07:
- Tracker #29655: The Upper non-critical value verification for FFC_06 is
  failed.
- Tracker #29703: Add platform check at beginning of FRU/SDR update.
- Tracker #29865: Duplicate entries in the FRUSDR readme.txt .
- Tracker #29869: Title is given wrongly in the files.
- Tracker #30111: "Get sensor reading" for CPU temperature sensors not working.

FFC_06:
- Tracker #29414: CLTT/OLTT parameter defined as GlobalActRatio needs to be
  changed.
- Tracker #29423: Same sensor #s for 'Proc missing' & 'Proc Throttled'
  sensors in the SDR file.
- Tracker #29546: Foxcove sensor 0x86: Offset should be 0x0001 in SDR.
- Tracker #29600: Asset Tag gets overwritten.
- Tracker #29613: Include Revision History , reference Doc & S/W requirment
  into README.txt.
- Tracker #29614: Update SDR files based latest Config sheet and FSC sheet.
- Tracker #29615: Copy right Year in FRUSDR package should be updated to 2007.

FFC_05:
- Updated the FRU Package version info in the SDR file.
- Tracker #49395: 'SAS BP PWRGD' has wrong entity ID
- Tracker #49394: Wrong Entity Instance for 'Mem Fan Pres'
- Added Platform ID checking to auto detect the S7000FC4UR's BMC
- All memory and processor sensors (other than PECI) are now always loaded.
  At run-time, BMC will disable sensors for components that are not installed.
- Updated Thermal Profile Data and Tcontrol SDRs.

=============================================================================
                             REFERENCE MATERIAL
=============================================================================
- Intel Server System S7000FC4UR Baseboard Management Controller EPS v1.1.
- Foxcove SDR Tables - New Format - V15.

=============================================================================
                              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

     FRUSDR Loader Utility Version 1.0.4 Alpha build 4

           SDR Files:   FC4_14.SDR
           FRU Files:   FC4_MB3.FRU
                        FC4_SR1.FRU
                        FC4_IO1.FRU
                        FC4_MMA2.FRU
                        FC4_MMB2.FRU
                        FC4_MMC2.FRU
                        FC4_MMD2.FRU
			Autoexec.nsh

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