=============================================================================
Intel(R) Server Platform SR4850HW4,SR6850HW4,SR4850HW4M,SR6850HW4M,SR4850HW4S 
and SR6850HW4S FRUSDR Load Utility RELEASE NOTES
=============================================================================
Intel Enterprise Platform & Services Division - Marketing
Intel Corporation
2800 Center Drive, DuPont, WA 98327 USA
=============================================================================
DATE: 		Oct 31, 2006
TO:		Intel(R) Server Platforms SR4850HW4,SR6850HW4,SR4850HW4M, 
		SR6850HW4M,SR4850HW4S and SR6850HW4S customers
SUBJECT:	FRUSDR Load Utility version 7.0.1 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) 2006 Intel Corporation.

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

The FRUSDR Load Utility is a DOS application program used for updating the server 
management subsystem product level Field Replacement Unit (FRU) 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.


   1. Executes under the DOS Shell.
   2. For Advanced IMM Card use revison 403 and later with FPGA version 47 and EID version 3
   3. Use LCP with firmware version 0.66
	

=============================================================================
                             DEPENDENCIES
=============================================================================	
- Executes under the DOS Shell.
- Use LCP with firmware version 0.66 or later
	
=============================================================================
                           SUPPORTED PLATFORMS
=============================================================================
Intel(R) Server platfoms SR4850HW4, SR6850HW4, SR4850HW4M, SR6850HW4M 
	SR4850HW4S and SR6850HW4S with BMC47 or later.

=============================================================================
                              KNOWN ISSUES
=============================================================================
None

=============================================================================
                           HOW TO USE THIS UTILITY
=============================================================================
The FRUSDR loader is meant to be used as an DOS 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.

    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.


=============================================================================
                        ISSUES FIXED IN RELEASE FRUSDR39
=============================================================================

Updated the SCSI Drive Slot Presence Sensors to reflect the proper 'Sensor 
  Record Sharing' field.


=============================================================================
                              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 v 7.0.1 
           SDR Files: SHW4_039.SDR
           FRU Files: SHW4MBD2.FRU
		      SHW4_IP2.FRU
		      SHW4_IA1.FRU
		      6scsiHS1.FRU
		      4scsihs1.fru
		      SAS6U35.FRU
		      SAS4U35.fru
		      SHW4FPL1.FRU					
		      SHW4MM12.FRU		
		      SHW4MM22.FRU
		      SHW4MM32.FRU
		      SHW4MM42.FRU
              	      SHW4GCM1.FRU

		      				

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

