==============================================================================
Intel(R) Server Board SE7520JR2 FRU/SDR and BMC Configuration RELEASE NOTES
==============================================================================
Intel Enterprise Platform & Services Marketing
Intel Corporation
2111 N.E. 25th Avenue, Hillsboro, OR 97124 USA
=============================================================================
DATE: 		January 03, 2006
TO:		Intel(R) server board SE7520JR2 customers
SUBJECT:	FRU/SDR & BMC Configuration Release Note JR-6.6.B
=============================================================================
                          IMPORTANT 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) 2005-2006 Intel Corporation.

=============================================================================
                              ABOUT THIS RELEASE
=============================================================================
This document describes some specifics of the Intel(R) server board
SE7520JR2 FRUSDR Utility Package Version and BMC Configuration utility.
These utilities is used for updating the server management subsystem product
level Field Replacement Unit (FRU) and the Sensor Data Repository (SDR) and
BMC Configuration.


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

Through the use of a configuration file, added features allow the user to 
control the execution path by probing hardware, requesting user input, and 
setting tags to provide filtering of FRU and SDR data. Multiple FRU and SDR 
files may also be processed at once.

If the user receive an error concerning the FRU headers not matching, when
trying to program a FRU file, this happens when the FRU file on the server
is a non-compatible version with the one you are trying to program.  In
this case you should contact your vendor for support and get a system update
package made to handle this problem.

The FRUSDR utility supports IPMI 0.9, IPMI 1.0 and IPMI 1.5 specifications. 
Be aware that both the FRU and SDR file formats vary between these different
implementations and are not completely backward compatible.  The utility will 
work correctly on a IPMI 0.9, a IPMI 1.0 or a IPMI 1.5 system, but mixed 
IPMI solutions on systems are not supported except for IPMI 1.0 and 1.5 FRU 
devices.

Also the FRUSDR utility is used to update the non-volatile storage device associated
with the mini Baseboard Management Controller, which holds the SAT,SIT,SBT and 
Configuration parameter areas.


=============================================================================
                         INSTALLATION PROCEDURE
=============================================================================
The FRUSDR Loader 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 
prior to and after using. Running the utility in a Window's DOS box is not 
supported and will provide incorrect results. 


- Copy all files to update media (Floppy Disk, USB disk-on-key, etc)
- If the media is not bootable, type "AUTOEXEC" at the command prompt. 
The AUTOEXEC.BAT file will automatically start the FRUSDR update utility


Note: Programming the BMC FRU internal use area clears the SDR repository. 
Therefore, the SDR repository must be reprogrammed after programming the 
BMC. Upon completion of programming the FRU and SDR areas, remove the 
update media and reboot the server. 

Note: After update this package, most of PEF table will be set with defaults.



=============================================================================
		       SYSTEM SOFTWARE REQUIREMENTS/REVISIONS
=============================================================================
- PC87431M mini-Baseboard Managment Controler (mBMC) from National Semiconductor:
  Revision 2.40 or Later. 
- IMM Module needs to be pre-installed 0.29 (or later) before running the package 6.5.1(or later) update. 



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


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


=============================================================================
                        ISSUES ADDRESSED IN THIS RELEASE
=============================================================================
JR-6.6.B 
 1.  Fixed Defect: FRUSDR 6.6.A showing wrong version in BIOS setup in the case of mBMC. (Changing SJR2m_VR.SDR and SJR2BMCS.SDR)
 2.  Fixed the spelling error. "platfrom to platform" "Editon to Edition" (Changing Master.CFG)
 3.  Increased the year of Copyright to 2006.  (Changing Master.CFG)


=============================================================================
                               Pedigree of changes
=============================================================================
JR-6.6.A
1. Fixed blinking green LED issue on SATA SKU. The SDR has been addded with two extra records.
   By this we have seperated out the SCSI terminator records for SATA and SCSI SKU's

JR-6.6.8
1. Fixed Defect: Abnormal SEL occur when updating BIOS to P09.1 and FRUSDR package 667. turned off the thermtrip (Changing SJR2SAT1.TBL)

JR-6.6.7
1. Fixed Defect: Possible issue with hardware damage using Jarrell FRUSDR 6.6.6. (Changing SJR2SIT7.TBL)
2. Fixed Defect: FRUSDR 6.6.5 fan control is not functioning correctly when using mBMC. (Changing SJR2SIT7.TBL)

JR-6.6.6
1. Fixed Defect: reduce some unuseful register setting. (Changing SJR2SIT7.TBL)
2. Fixed Defect: FRUSDR 6.6.5 fan control is not functioning correctly when using mBMC. Sensor Initialization Table must under 40 entries.(Changing SJR2SIT7.TBL)

JR-6.6.4
1. Change the terminator sensors for IMM to only log the error offsets.
2. Change the assert & deassert values from the SATA HSBP Temp sensor for IMM.

JR-6.6.3
1. Fixed Defect: FRUSDR settings for "Other Chassis" does include CPU processor temperature monitoring. 

JR-6.6.2
1. Fixed Defect: FRUSDR settings for "Other Chassis" does include CPU processor temperature monitoring.
2. Fixed Defect: CBC device locator record needs to be updated.
3. Fixed Defect: SEL events generated when viewing log from web console.
4. Fixed issue. PROCHOT doesn't generate by mBMC.

JR-6.5.2
1. Fixed Defect: Lower critical/non-critical, Normal, Max, Min readings are not correct.
    Set Max reading be 74h=45%.
2. Fixed Defect: FRU/SDR package 6.5.1 does not properly configure the FRU size.
    Corrected the FRU header and write FFh to register 0x38 with and without IMM.

JR-6.5.1
1. Fixed Defect: Heccta driving PWM when DC is off. Add PEF item 0Eh and 0Fh on PEF table.

JR-6.4.4
1. Disabled PEF Filter Number 0Eh and set all parameters to 00h.
2. Fixed Defect. Removed the _SDR_TAG from CPU status sensors (0x90 & 0x91) sensor data records.
3. Fixed Defect. Set mBMC internal flash offset 0x38 to 0xFF.
4. Modified the hysteresis about IMM card FSC in SDR.

JR-6.4.3
1. Fixed DCS#18906.

JR-6.4.2
1. Fix Defect 75881.
2. Fix Defect. Modify mBMC Internal flash 0x07 with 00h; the mBMC doesn't detect Warm Reset event any more.
3. Fix Defect 75875.
3. Fix Defect. Add one PEF item on PEF table.

JR-6.4.1
1. Pre Defect, Modify "BB Vbat" sensor record For IMM module.
2. Fix defect 75581,74498 issue.
3. Modify "IMM Module FRU" of SDR type 11.
4. Disable FRB3 feature.

JR-6.2.1
1. Modify mBMC SIT table.
2. Fixed Defect# 75735.
3. Modify CPU Vccp threshold as below
Sensor#	SENSOR NAME	UC	UNC	LNC	LC
19h	Proc1 Vccp	1.48	1.44	0.84	0.81
1Ah	Proc2 Vccp	1.48	1.44	0.84	0.81
4. Pre Defect ID 75755, remove "LAN Leash Lost" event from mBMC



JR-6.1.2
1. Modify PEF table, Item 26-30, Filter configuration equ 40h.
2. Modify SIT table, Change FSC configure order.

JR-6.1.1
1. Fix defect ID 75622.
2. Fix defect ID 75623.

JR-6.0.A
1. Fix Defect ID 75521
2. Fix Defect ID 75534
3. mBMC SDR over size, remove two sensors, AUX +3.3V and +1.5V NIC core sensor.
4. Fix Defect ID 75553
5. Modify SDR threshold.

JR-6.0.9
1. Fix Defect ID 75435

JR-6.0.8
1. Fix Defect ID 75364.


JR-6.0.1
1. workaround Defect ID 75131



----------------------------------------------------------------------------   
                           PARSING THE COMMAND LINE
----------------------------------------------------------------------------
The FRUSDR Loader command line provides the following options:

Usage: 

      /? 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: Users may alternatively use a '-' instead of the '/'. 

----------------------------------------------------------------------------
DISPLAY FRU, SDR, SMB and National Semiconductor(c) PC87431 Internal Flash Area
----------------------------------------------------------------------------
The SDR area can be displayed by using the -D SDR parameter with the FRUSDR 
command, such as FRUSDR -D SDR.

The -D FRU parameter will display the BMC FRU area by default. To view other 
FRU areas, additional addressing information must be provided:

The -D FRU command may be followed with up to 16 device addresses. These 
device addresses are used to view up to 16 different FRU areas. The arguments 
following the "-D FRU" are in the same order and value as the NVS_TYPE, 
NVS_LUN, DEV_BUS and DEV_ADDRESS which may be found in the FRU file header of 
each FRU file. The LUN address is optional. If the LUN address is used, it 
must start with an 'L'. 

      Usage: FRUSDR /d fru (device) [lun] (bus) (addr1) (addr2) (etc) 

Examples for the Intel(R) server platforms SPSH4 & SRSH4:


1. To display the Intel(R) server board SSH4 SDR's:
   C> FRUSDR /P /D SDR 

2. To display the Intel(R) server board SSH4 BMC FRU:
   C> FRUSDR /P /D FRU 

3. To display the Intel(R) server board SSH4 HSC 1 FRU:
   C> FRUSDR /P /D FRU IMBDEVICE 00 C0 

Note: If your system does not display the above FRU device, then it probably 
does not contain that device.

The -D TBL parameter will display the National Semiconductor(c) PC87431 internal flash area by default.

      Usage: FRUSDR /D TBL <Hex_word_Offset> <Hex_word_Length>
	where 
		Hex_word_Offset : Start offset in the mini BMC Internal flash
		Hex_word_Length : Length of data to display.

Examples for the Intel(R) server platforms SJR2:

1. To display the Intel(R) server board SJR2 TBL's:
   C> FRUSDR /P /D TBL

----------------------------------------------------------------------------
                              TEMPORARY FILES
----------------------------------------------------------------------------
Temporary files are not created by default.  If you desire to have
temporary files created you must use the undocumented "/tmp" switch on the 
command line, then when the FRUSDR Loader is executed, it creates temporary 
files which may be used to aid in recreating a problem, should on arise.  
The FRUSDR Loader does not remove the temporary files, the temporary files 
may be erased by the user after the FRUSDR Loader has completed.
----------------------------------------------------------------------------
                             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 SM BIOS specification documents 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.



[END OF RELEASE NOTES]
