1. FRUSDR_37.zip Driver
2. ReadMe.txt File Contents

ReadMe.txt Driver File Contents (FRUSDR_37.zip)

=============================================================================
Intel(R) Server Board S5000PAL / S5000XAL BMC RELEASE NOTES
=============================================================================

INTEL Enterprise Platform & Services Marketing
Intel Corporation
2111 N.E. 25th Avenue, Hillsboro, OR 97124 USA

=============================================================================
DATE:       August 23, 2006
TO:         Intel(R) Server Board S5000PAL / S5000XAL customers
SUBJECT:    FRUSDR Package FAL v37 Release Notes


=============================================================================
LEGAL INFORMATION
=============================================================================

Information in this document is provided in connection with Intel products 
and for the purpose of supporting Intel developed server boards and systems. 
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) 2005 - 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 and FRU 
area. The utility has the capability to generically handle FRU devices that
may not be associated with the BMC.

Each version of the FRUSDR Load Utility package contains the FRUSDR Load
utility program as well as the latest FRU, SDR, and CFG files available at the
time the FRUSDR Load utility package is released.  

Utility and File Versions:

	FRUSDR Load Utility v 7.0.2
	SDR Files: AL_37.SDR
	FRU Files: ALMBD_05.FRU
	           ALXMBD_3.FRU

=============================================================================
SYSTEM HARDWARE REQUIREMENTS/REVISIONS
=============================================================================

Baseboard:
S5000PAL / S5000XAL 
Beta Fab5 (PBA# -50x), Silver FAB6 (PBA# -60x), Production (PBA -70x, -80x)

BMC Firmware - R52 or Later
System BIOS - R62 or Later
Intel Chassis HSC FW - R1.41 or Later

=============================================================================
IMPORTANT INSTALLATION NOTES
=============================================================================

The FRUSDR Load utility is meant to be used as a DOS application on a server. 
The utility should be placed onto a bootable DOS media and the system rebooted 
just before and right after using the utility. Running the utility in a Window's
DOS box is not supported and will provide incorrect results. 


=============================================================================
INSTALLATION PROCEDURES
=============================================================================


****  Standard Update Procedure: ****

1) Extract Update Package contents to a USB Flash Drive
2) Boot to the ROM-DOS command prompt.
3) Go to directory containing the FRUSDR utility files
4) At the command prompt type "FRUSDR37.BAT"
5) When prompted, enter requested information


The FRUSDR update should complete with no error and exit out to a DOS prompt.

  



**** Custom update procedure: ****

This procedure can be used in place of the Standard update procedure if you have
created a custom .CFG file for a non-Intel chassis. Otherwise, the Standard 
Update Procedure should be followed.

   1. Boot to the ROM-DOS command prompt.

   2. Copy frusdr.exe and any .fru, .sdr, and .cfg files from the latest firmware
      release to a hard drive or USB key.

   3. a. Command line Interface:

             frusdr [File Name] [Options]

      The following command-line options are supported:

      /? or /h              Displays usage information.
      /d {smb,fru,sdr,tbl}  Only displays requested area.
      /cfg filename.cfg     Uses custom CFG file.
      /p                    Pause between blocks of data.

      NOTE:  A '-' may be used instead of a '/'.

      b. Examples:

	i. Display SMBIOS information:

		frusdr /d smb /p

	ii. Display SDR repository:

		frusdr /d sdr /p

	iii. Display FRU data:

		frusdr /d fru /p

	iv. Update FRUs and SDRs using default configuration file (named
	    master.cfg):

		frusdr /cfg master.cfg

      c. Displaying Data Using Direct Addressing
         FRU data can also be displayed using a command of the following form:

	frusdr /d fru [NVS type] [dev ctlr] [lun] [bus] [addr]

	Where:

		NVS type is the non-volatile storage type
		dev ctlr is the device controller (must start with "C")
		lun is the logical unit number (must start with "L" and can only
			be 0, 1, 2, or 3.
		bus is the bus the storage area is associated with
		addr is the slave address 

	Example of a command to display BMC FRU data using direct addressing:

		frusdr /d fru imbdevice C20 L00 FF 20
	 
       d. Displaying FRU Data Using Indirect Addressing
	  To display FRU data using indirect addressing, a command of the following
 	  form must be used:

	  frusdr /d fru [NVS type] [device ID]

	Example of a command using indirect addressing:

		frusdr /d fru imbdevice 00
      

   4. Reboot system after updating of the FRUs or SDRs is completed.

   5. Temporary Files

	If you desire to create temporary files, you must use the undocumented 
	"/tmp" switch on the command line.  When the FRUSDR Loader is executed,
	it creates temporary files  that may be used to aid in recreating a problem.
	The FRUSDR loader does not remove the temporary files; they must be 
	removed by the user.

	Example of a command to create a temporary file:

	frusdr /d sdr /tmp

	The FRUSDR Loader creates a file called sdr.tmp in the current directory.




=============================================================================
KNOWN ISSUES/WORKAROUNDS
=============================================================================


1. Immediately after updating the FRUSDR Package, BMC may not respond for
   approximately 35 seconds. During this period front panel will be locked out and
   status LED will blink amber. During this period user should not reboot the system
   using CTRL+ALT+DEL.

=============================================================================
CHANGES FROM THE PREVIOUS FRUSDR UTILITY PACKAGE RELEASE
=============================================================================

A. CHANGES FROM PREVIOUS SDR VERSION
	No changes

B. CHANGES FROM PREVIOUS FRU VERSION
	No changes

C. CHANGES SINCE PREVIOUS FRUSDR UTILITY VERSION
	FRUSDR Load Utility v 7.0.2


=============================================================================
FEATURES ADDED IN THIS RELEASE
=============================================================================
FAL_37 
 None


[END OF RELEASE NOTES]

=============================================================================
Pedigree of Changes
=============================================================================

FRUSDR R36 (Released)

1. Defect# 127357. The following SDR's are being reported as having issues 
which affect customer's software. (Fixed the entity instance values in CPU2 
VRD Temp and CPU2 Vcc OOR records.)
2. Remove the PVCS header.


FRUSDR R35 (Not Released)

1. # 125853. No SEL entry to indicate loss of redundancy after 10th SBE injection in sparing. (Update the Sensor Initialization byte in the sensors F0h to F5h from 2Dh to 67h.)
2. # 27340. Change required for legal wording in FRUSDR release notes. (Fix release note title.)
3. Remove processor 2 records of Domain 3 and Domain 4 in other chassis.
4. Fix Count of Temperature valus from 08 to 09.



Frusdr R34 (Released)
1. Defect# 127295. Update CPU steppings in FRUSDR



FRUSDR 33 (Not Released)

--- 1. Defect# 127139. The SDR record of some sensors didn't match with ESB2 BMC EPS v1.1.
a. Fixed the power unit status sensor assertion and deassertion event mask to 7300h.
b. Added the deassertion event mask in sensor# 01h, 02h, 04h, 6Fh, E1h to E7h and ECh to EFh.
c. The sensor# 86 has been removed.
d. The upper non-critical has been removed in sensor# C0h and C1h.
e. The assertion and deassertion event mask has been removed in sensor# D0h and D1h.
--- 2. Defect# 127200. Therm Ctrl sensor SDR settings incorrect - causes "nominal" 
reading in ISM to show up unavailable. (Set analog characteristic flags bit 0 
in P1 and P2 thermal control records.)
--- 3. Defect# 127201. Therm Margin SDR's need units to be set to temperature instead 
of unspecified. (Set sensor unit 2 field to degree C in P1 and P2 thermal margin records)
--- 4. Defect# 127211. Other Chassis - PWM3 and PWM4 should be set to 100% as a default. 
(Add PWM3 and PWM4 records for other chassis and setting it to 100%.)
--- 5. Defect# 127226. Sensor Initialization needs to be changed from 0x27 to 0x67 for 
the following sensor numbers. (Fixed sensor initialization from 27h to 67h in 
sensor# 90h, 91h and E0h to E7h )
--- 6. Defect# 127230. Threshold and Range settings for other chassis processor 
fansinks should be increased to enable reading of full range of fan speeds. 
(Fixed LM94 RPM for 100% and threshold values in processor 1 and 2 fan)
--- 7. Defect# 127103. Power supply sub system is shown as redundant when one is absent. 
--- 8. Defect# 127146. Other chassis fan OEM config SDR's not present. 
Causes Other chassis fan tach readings to be incorrect. (The LM94 and SIO records 
were added in other chassis.)
--- 9. Defect# 127151. The lower non-critical threshold value of HSBP temperature 
sensor is the same with the normal minimum value. (Fixed HSBP temperature lower 
critical to 00h and lower non-critical to 05h.)
--- 10. Defect# 127158. A minor typo error in String Byte details for voltage 
sensor names. (Add the "+" in voltage records.)
--- 11. Defect# 127174. Sensor called BB+1.9V  NIC CORE  Sensor 11h changed Typical 
set point from 1.90V to 1.95V. (Remove the 1.9 NIC records.)
--- 12. Defect# 127175. 5000X AC Type 2 record does not read S5000XAL. 
(Add the file which names ALXMBD_2.FRU for S5000XAL.)
--- 13. Defect# 127181. FRUSDR throttling value updates 
--- 14. FRUSDR 32 will detect the North bridge type then update each FRU.



FRUSDR R32 (Released)

1. Remove BB+1.9V NIC CORE record.