============================================================================== Intel(R) Server Board SE7210TP1-E FRU/SDR and mBMC Configuration RELEASE NOTES ============================================================================== Intel Enterprise Platform & Services Marketing Intel Corporation 2111 N.E. 25th Avenue, Hillsboro, OR 97124 USA ============================================================================= DATE: June 23, 2004 TO: Intel(R) server board SE7210TP1-E customers SUBJECT: FRU/SDR & mBMC Configuration Release Note TP-5.8.D ============================================================================= 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) 2003 Intel Corporation. ============================================================================= ABOUT THIS RELEASE ============================================================================= 1. This document describes some specifics of the Intel(R) server board SE7210TP1-E FRUSDR Utility Package Version and mBMC 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 mBMC Configuration. 2. The mBMC Configuration programs PEF,SIT,SAT,defaul FRU and CFG Utility Package Version. ============================================================================= GENERAL INFORMATION ============================================================================= 1. 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. ============================================================================= INSTALLATION NOTES ============================================================================= The FRUSDR utility is meant to be used as a DOS application on a server. The utility should be placed onto a bootable DOS floppy 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 in a Window's DOS box is not supported and will provide incorrect results. Normal Command Line Use: A:> FRUSDR -CFG MASTER.CFG 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 floppy disk and reboot the server. ---------------------------------------------------------------------------- PARSING THE COMMAND LINE ---------------------------------------------------------------------------- 1. The FRUSDR Loader command line provides the following options: Usage: /? or /h Displays usage information. /d {smb,fru,sdr} 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, and SMB INFORMATION ---------------------------------------------------------------------------- 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. ---------------------------------------------------------------------------- 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. ============================================================================= KNOWN ISSUES/WORKAROUNDS ============================================================================= V 0.50 V 0.40 1. Defect ID 71220, LED action issue 2. Fan control policy of all chassis is changed. And not verify by thermal team. V 0.30 1. Fan control policy and Fan threshold for Kahana chasiss is not already. 2. CPU Vpp threshold is not ready 3. FRUSDR Utility can not update SDR and FRU at the same time. V0.20 Threshold Not Ready: CPU Vccp voltage; Base board temperatur; System Fan1-6; CPU Fan ============================================================================= FEATURES ADDED IN THIS RELEASE ============================================================================= TP-5.8.A 1. Add Caesar chassis option. TP-5.8.8 1. Remove Watchdog Time and Power down/off PEF item according to Defect ID71396. TP-5.8.7 1. Modify PEF Table as Intel FW team request * Analog Sensor Assert * Analog Sensor Assert * Analog Sensor Deassert * Proc 1 IERR Assert * Digital Sensor Deassert * Watchdog Timer Expired * FP NMI Assert * ID Button Assert * Front Panel button clear CMOS * OS Load Post Code * Power Off * Chassis Intrusion(Used by ISM) * Post Code Error(Used by ISM) * Voltage Failure(Used by ISM) * Fan Failure(Used by ISM) * Temperature Failure(Used by ISM) 2. Modify SIT table for chesness chassis. 3. Modify voltage threshold as HW meeting consequence. TP-5.8.6 Remove Built-in SDR 1-9. ADD Chesnee Chassis. V0.50 1. Remove Thermal trip sensor from SDR because mBMC can't detect this sensor. 2. Remove System Event Sensor from SDR because built-in sensor already includes it. 3. Add "Other" option for third-party chassis. 4. Change All Sensor number because in order to match mBMC FW 2.30. 5. ADD 3 entries PEF, Memory Error, BIOS Post Code Error, FRB Failure V0.40 1. Add CPU Vccp voltage threshold value 2. Remove SAT Table from TP_CFG.TXT, Add TBL file 'TP_SAT.TBL' 3. Remove SIT Tabel From TP_CFG.TXT, Add TBL file 'TP_SIT.TBL' 4. Disable mBMC Build in SDR, Add Sensor number 1-5 to SDR and SAT. V 0.30 1.Modify SAT Table to enable Intruder and Chassis ID button can generate event when DC OFF 2. RCRP Chassis Fan threshold Fan1 Fan2 Fan3 Fan4 CPU_Fan BB_Temp Upper critical Threshold value 55h 55h 60h 60h 43h 54h Upper non-critical Threshold value 50h 50h 5ah 5ah 41h 49h Normal Maximum Reading 42h 42h 54h 54h 39h 42h Normal Reading 33h 33h 40h 40h 37h 35h Normal Minimum Reading 28h 28h 30h 30h 30h 30h Lower non-critical Threshold value --- --- --- --- --- 05h Lower critical Threshold value --- --- --- --- --- 00h 2. Pilot Point Chassis Fan threshold Fan1 Fan3 CPU_Fan BB_Temp Upper critical Threshold value 80h 75h 43h 54h Upper non-critical Threshold value 71h 70h 41h 49h Normal Maximum Reading 64h 65h 39h 42h Normal Reading 4Ah 4dh 37h 35h Normal Minimum Reading 33h 35h 30h 30h Lower non-critical Threshold value --- --- --- 05h Lower critical Threshold value --- --- --- 00h 3.Change Proc Temp upper critical threshold equ 85; Non-critical Threshold equ 80 4. On SIT table, Add Ambient temperature Offset(72h), configure with 02h. 5. On mBMC configuration, Disable FP Lock with GPIO 6. On SIT table, Enable Automatic Fan speed Control Mode for RCRP and Pilot Point chassis 7. On PEF, Change LED Action to match TP mBMC EPS 8. On mBMC configureation, Change LED default color priority, blinking is 3, solid is 2 9. On PEF, Add Front Panel button clear CMOS 10. VTT_GMCH (SIO) for Northwood VTT_GMCH (SIO) for Prescott Upper non-recoverable ---------- ---------- Upper critical 1.55 1.31 Upper non-critical 1.54 1.30 Normal Maximum Reading 1.5 1.25 Normal Reading 1.45 1.22 Normal Minimum Reading 1.4 1.20 Lower non-critical 1.36 1.15 Lower critical 1.35 1.14 Lower non-recoverable ---------- ---------- V 0.20 Ready Threshold: Items 1.5V 3.3V VCC 12V V_MCH Proc temp Upper non-recoverable Threshold value ---------- ---------- ---------- ---------- ---------- ---------- Upper critical Threshold value 1.55 3.47 5.25 12.6 1.55 80 Upper non-critical Threshold value 1.54 3.44 5.22 12.54 1.54 75 Normal Maximum Reading 1.53 3.4 5.15 12.4 1.5 55 Normal Reading 1.5 3.3 5 12 1.45 45 Normal Minimum Reading 1.47 3.2 4.85 11.6 1.4 35 Lower non-critical Threshold value 1.46 3.16 4.77 11.46 1.36 5 Lower critical Threshold value 1.45 3.13 4.75 11.4 1.35 0 Lower non-recoverable Threshold value ---------- ---------- ---------- ---------- ---------- ---------- ============================================================================= ISSUES FIXED SINCE LAST RELEASE ============================================================================= TP-5.8.D 1. Modify PEF Table for Chesnee Chassis. 2. Modify MCH_Vtt voltage sensor as below in order to fix Defect 71478. SENSOR NAME Normal Min Lower-NC Lower-C Vtt_GMCH-NWD 54h/1.34V 51h/1.30V 4Eh/1.30V Vtt_GMCH-PSC 45h/1.1V 42h/1.06V 3Fh/1.01V TP-5.8.C 1. Disable the Platforma Alter event in the mBMC. The will save us the limited SEL space. Currently. Program the mBMC internal flash offset 3BH to value 09h. 2. Set mBMC SIT table with Last item. 3. Modify PEF Table and SIT Table for Chesnee Chassis. TP-5.8.B 1. Modify Voltage threshold for all chassis on SDR. Please refer to below. SENSOR NAME Upper-C Upper-NC Normal Max Nominal Read Normal Min Lower-NC Lower-C 1.5V 7Fh/1.65V 7Dh/1.62V 79h/1.575V 73h/1.5V 6Eh/1.425V 6Ah/1.38V 68h/1.36V 3.3V E2h/3.62V DEh/3.55V D9h/3.465V CEh/3.3V C4h/3.135V BFh/3.06V BBh/3.00V 5V CBh/5.49V C7h/5.38V C2h/5.25V B9h/5.0V B0h/4.75V ABh/4.63V A8h/4.54V 12V E1h/13.30V DDh/13.04V D6h/12.6V CBh/12.0V C1h/11.4V B7h/10.79V B3h/10.58V 12V-Kahana E1h/13.30V DDh/13.04V D6h/12.6V CBh/12.0V C1h/11.4V ADh/10.20V A9h/10.00V Vtt_GMCH-NWD 64h/1.60V 62h/1.57V 5Fh/1.523V 5Bh/1.45V 56h/1.3775V 53h/1.33V 51h/1.30V Vtt_GMCH-PSC 56h/1.38V 54h/1.34V 4Fh/1.26V 4Bh/1.2V 47h/1.14V 45h/1.10V 43h/1.07V TP-5.8.A 1. Fixed Defect ID 71433 2. Fixed Defect ID 71434 3. Modify BB +12V LNC threshold equ 10.2V & LC threshold equ 10V for Kahana UP. TP-5.8.9 1. Fixed Defect ID 71408 2. Fixed Defect ID 71409 3. Fixed Defect ID 71411, Modify MCH Voltage threshold as below. Items VTT_GMCH (SIO) for Prescott Upper critical 56h,1.38V Upper non-critical 54h,1.34V Normal Maximum Read 53h,1.32V Normal Reading 4Ch,1.22V Normal Minimum Read 46h,1.12V Lower non-critical 45h,1.10V Lower critical 42h,1.07V 4. Modify Chesnee chassis Fan SDR and PEF table. TP-5.8.8 1. Fixed Defect ID 71385 2. Fixed Defect ID 71390 3. Fixed Defect ID 71369 TP-5.8.7 1. Fix Defect ID71360 TP-5.8.6 1. Fix Defect ID71354 2. Fix Defect ID71368 v 0.50 1. Fix Defect ID 71321 2. Fix Defect ID 71220 3. Fix Defect ID 71316 V 0.40 1. Fix Defect ID 71258,71293,71294,71303,71310 V 0.20 Modify Entity Instance byte for Defect ID 71187 Modify sensor Initialization byte for Defect ID 71188 Modify Event Mask field for Defect ID 71189 Modify Sensor #07,15,16,17,19 for Defect ID 71190 Modify Sensor #1Bh for Defect ID 71191 Modify Sensor #17h of ID String Bytes For Defect Id 71192. V 0.15 1. Modify some Sensor data ============================================================================= REFERENCE MATERIAL ============================================================================= Torrey Pines Mini Baseboard Management Controller EPS Revision 0.5 mini Baseboard Management Controller Core EPS for IPMI based Systems Revision 1.0 [END OF RELEASE NOTES]