============================================================================= Intel(r) Server Board SHG2 RELEASE NOTES ============================================================================= INTEL Enterprise Platform & Services Marketing Intel Corporation 2111 N.E. 25th Avenue, Hillsboro, OR 97124 ============================================================================= DATE: June 10, 2003 TO: Intel server board SHG2 customers SUBJECT: BIOS Release Notes Production Build 1.09 (0039): ============================================================================= 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 BIOS RELEASE ============================================================================= Build # : 0039 Build Stamp : SHG20.86B.0039.P09.0305131555 Build Date : May 13, 2003 ============================================================================= BIOS COMPONENTS/CONTENTS ============================================================================= Processor stepping(s) supported: Intel(R) Xeon(TM) processors Microcode update versions: CPUID Stepping Microcode Update ID 0F24h B0 1D 0F27h C1 34 0F29h D1 0F System hardware configurations supported: SHG2 PBA -4xx and -5xx Baseboards ============================================================================= SYSTEM FIRMWARE REQUIREMENTS/REVISIONS ============================================================================= BMC FW : .09 or later ============================================================================= IMPORTANT INSTALLATION NOTES ============================================================================= IMPORTANT NOTES: 1. Note the settings of the SETUP parameters. Enter SETUP by hitting the F2 key during boot up. Write down the settings for each of parameters. At the end of the BIOS update process you should set the parameters to default values by hitting the F9 key, and then re-enter these values you have written down. 2. Place the bootable floppy containing the BIOS into drive a: of the system that you want to upgrade and boot the system while the floppy diskette is in the drive. 3. Update (iFLASH) 3.1 Type 1 or 2 at the BIOS option menu. 3.2 If you type 1, update finishes automatically. 3.3 If you type 2, iFlash starts with interactive mode. Update and reboot the system by following menu of iFLASH. 4. Check to make sure the BIOS version is the new version as the system reboots. 5. Enter Setup by pressing the F2 key during boot up. Once in Setup, press the F9 to set the parameters back to default values. Re-enter the values you wrote down at the beginning of this process. If you do not set the CMOS values back to defaults using the F9 key, the system may function erratically. ============================================================================= KNOWN ISSUES/WORKAROUNDS ============================================================================= - None. ============================================================================= FEATURES ADDED IN THIS RELEASE ============================================================================= BIOS 39: - Microcode update for new Intelr XeonT D1 step processors BIOS 36: - Microcode update for new Intelr XeonT B0 and C1 step processors - Added the mixed processor speed feature. - NOTE: You may encounter a CMOS Checksum error or other problem after reboot. Try shutting down the system and booting up again. CMOS checksum errors require that you enter Setup, check your settings, save your settings, and exit Setup. BIOS 32: - None BIOS 31: - None BIOS 29: - Microcode update for new Intel(r) Xeon(tm) processor C1 stepping. - Added support for 38.4 kbps console redirection BIOS 26: - Changed the name of the blank *.USR, *.LGO/LG1 files in iFlash disk to CLRBIN.USR, CLRLOGO.LGO/LG1. - BIOS production banner change P02. BIOS 23: - Updated the SCSI BIOS for AIC7902 from 40030 -> V4.00. The SCSI BIOS for AIC7899 has not been changed. ============================================================================= ISSUES FIXED SINCE LAST RELEASE ============================================================================= BIOS 39: Fixed the following issues: - Corrected Check Sum Error seen immediately after updating BIOS flash and rebooting system. - Correceted an Adaptec U320 RAID Controller Hang condition on RAID Creation or Deletion. - Corrected video corruption seend during post with LSI 22320-R PCI Adaptor Card BIOS 36: Fixed the following issues: - Novell Netware 6 hangs when "Downing" when legacy USB is Enabled - Onboard NIC BIOS controls add in P100+SA when add in Boot Agent is disabled - HCT unreported I/O failure issue with Windows Server2003 - Included the CIOBX2 Errata workaround - Changed the processor max speed on DMI type4 BIOS 34: Fixed the following issues: - XMS disappears when booting from an IDE hard drive - DPC over modem service partition boot fails - Parity Issue - On-screen display of processor information during POST - KC hang - LPTTEST fails - Need User Binary file for test programs to run properly BIOS 32: Fixed the following issues: - Processor offline errors 8180 with IERR in SEL BIOS 31: Fixed the following issues: - PCI multi-function devices are not properly configured by the BIOS - SSU does not work with console redirection enabled - Flash operations leave the flash component in an unknown state - NMI is unconditoinaly issued on Target Abort and on PERR - PERR not enabled on PCI devices behind P2P bridges - Divide by Zero overflow error on FRU update with C1 stepping procesor installed - User binary update causes failures during next BIOS POST BIOS 29: Fixed the following issues: - Fixed packed file corruption error - Resolved low/erratic memory bandwidth reported by Sandra 2002 on Xeon processors. - PCI cards with multiple devices are correctly configured - Resolved issue with Int 15 function 87 taking 5 milliseconds to complete per operation. - 38.4bps baud rate option included. - Invalid characters (other than A-Z and 0-9) cannot be accepted for Admin & User Password. BIOS 26: Fixed the following issues: - Changed the EPP mode setting to correct an LPT Test failure. - CSB5: disabled the memory write and invalidate function. - SCB5/IDE: PERR and SERR signals enabled as a bus mastering adjustment. - The BIOS MP header changed/corrected to reflect "SHG2". BIOS 24: Fixed the following issues: - Fixed problems connecting to the Service Partition via modem. BIOS 23: Fixed the following issues: - Fix to boot from a USB floppy or CD-ROM ============================================================================= REFERENCE MATERIAL ============================================================================= Intel(R) SHG2 Technical Product Specification (TPS) ============================================================================= BIOS RECOVERY INSTRUCTIONS ============================================================================= Download the BIOS recovery disk from support.intel.com and follow the instructions included with the disk. [END OF BIOS RELEASE NOTES] SHG2 Server Baseboard Management Controller (BMC) Firmware Version 0.22 (Bootblock Version 0.07) Release Notes - May 5th, 2003 Introduction. This document applies to the firmware used in the Intel SHG2 server Baseboard Management Controller (BMC). File SHG2_xx.HEX is used by the FWPIAUPD utility to update the BMC code on a running server. A note about DCS numbers. The DCS numbers used in this document refer to Intel's internal defect tracking database. These numbers are generally not meaningful outside of Intel, they are included in these release notes as part of Intel's tracking and correction process. Updating the Firmware. The firmware is updated by the FWPIAUPD.EXE utility program that is included with this release package. This program can be run interactively (the program prompts the user for information) or with all information supplied on the command line. Using the command line is less prone to error, the command line to use is: FWPIAUPD -ni -u -o -p SHG2_xx.HEX The included batch file UPDATE.BAT performs this update automatically. Regarding Boot Block Updates. The boot block on the BMC is write protected and should never be updated unless these release notes specifically call for a boot block update. Never use the -b or -boot switch on the command line. If the utility is run interactively, always answer NO to the "Update the boot block" question. If you do attempt to update the boot block while the write protection jumper is in place, the boot block will NOT be modified. However, when the utility attempts to verify that the code in the flash matches the code in the SHG2_xx.HEX file, the verify will fail. Please note that this is a "false" warning - the boot block on the BMC is still perfectly fine since it is write protected. The reason the verify fails in this case is that each version of firmware places a time/date stamp of when the firmware was compiled into the boot block area of the SHG2_xx.HEX file. It is this data that changes with each new file and causes the verify to fail. To perform a boot block update, do the following: 1. Power down the server, unplug the AC cord and open the chassis. 2. Install a jumper on the two pins labelled "BMC WP". The labelling is a little confusing, the correct pins are next to the fan connector. 3. Plug in the AC cord, power up and boot to DOS. 4. Enter the command: FWPIAUPD -ni -u -o -p -b SHG2_xx.HEX OR Use the included UPD_BOOT.BAT batch file 5. After the update completes, power down and unplug AC. 6. Move the jumper you installed in step 2. 7. Close the chassis, plug in AC and boot normally. Known Dependencies. BMC 22 requires FRU & SDR package version 5.0.9 or later. Only the SDRs need to be updated, it is not necessary to update any FRUs. It is suggested that the SDRs be updated before the BMC is flashed in. SHG2 BMC firmware release history. BMC version 0.22 (Bootblock version 0.07), May 5th, 2003 Bootblock checksum: F4CDh Opcode checksum: 6748h ID LED was flashing when ID button pressed. Now solid. Added support for 11,000 RPM fans used with 3 Ghz processors. [END OF BMC RELEASE NOTES] ============================================================================= ABOUT THIS FRUSDR RELEASE ============================================================================= This document describes some specifics of the FRU & SDR Utility SHG2 Package Version HG-5.0.9. This utility is used for updating the server management subsystem product level Field Replacement Unit (FRU) and the Sensor Data Repository (SDR). FRU & SDR Package 5.0.9, April 11, 2003 *** This package should only be used with BMC 22 or later! *** ============================================================================= GENERAL INFORMATION ============================================================================= This utility is used to update the non-volatile storage device associated with the 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 Loader 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 ---------------------------------------------------------------------------- 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 SM BIOS (SMB) area can be displayed with the -D SMB parameter with the FRUSDR command. Note: The system must be rebooted in order for the SM BIOS (SMB) changes to take effect. 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 Server Platforms SPSH4 & SRSH4: 1. To display the SSH4 SM BIOS area: C> FRUSDR /P /D SMB 2. To display the SSH4 SDR's: C> FRUSDR /P /D SDR 3. To display the SSH4 BMC FRU: C> FRUSDR /P /D FRU 4. To display the 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 ============================================================================= None. ============================================================================= FEATURES ADDED IN THIS RELEASE ============================================================================= FRU & SDR Package 5.0.9, April 11, 2003 *** This package should only be used with BMC 22 or later! *** Added support for the high speed processor fans used by 3 GHz processors. BMC 22 or later is also required for correct support of these fans. The "Processor Hot" sensors were renamed to "CPU x Therm Ctrl". Added an OEM record for the SC5200 chassis that indicates to Intel ISM software that the system supports an ID LED. Added another record for OEM chassis that indicates the lack of an ID LED. ============================================================================= ISSUES FIXED SINCE LAST RELEASE ============================================================================= None ============================================================================= REFERENCE MATERIAL ============================================================================= Intel(R) Server Board SHG2 Technical Product Specification (TPS) [END OF FRUSDR RELEASE NOTES] ================================================================================ ABOUT THIS HSC RELEASE ================================================================================ Firmware Version: 0.10 Bootblock Version: 0.47 This document applies to the firmware used in the Intel server chassis SC5200 Hot-Swap SCSI Backplane (HSBP). File H2FHxxxx.HEX is used by the FWPIAUPD utility to update the Hot Swap Controller (HSC) code on a running server. ================================================================================ SUPPORTED SYSTEMS ================================================================================ Intel(r) Server Board SHG2 and Intel(r) Server Chassis SC5200 HSRP ================================================================================ SYSTEM BIOS & FIRMWARE DEPENDENCIES ================================================================================ - None ================================================================================ IMPORTANT INSTALLATION NOTES ================================================================================ - Validation: Intel only validates system software releases that are current. System software is defined as BIOS, BMC firmware, and FRU/SDR. Intel does not perform regression testing of current system software with previous versions of system software. Intel recommends upgrading to the latest revisions of system software as necessary. There are no known compatibility issues or dependencies between system software revisions. -------------------------------------------------------------------------------- UPDATING THE FIRMWARE -------------------------------------------------------------------------------- The firmware is updated by the FWPIAUPD.EXE utility program that is included with this release package. This program can be run interactively (the program prompts the user for information) or with all information supplied on the command line. Using the command line is less prone to error, the command line to use is: FWPIAUPD -ni -u -o -[p|s] -nopc H2FHxxxx.HEX The notation -[p|s] means to include either the -p OR the -s, but not both. -p selects the primary HSC for updating, -s selects the secondary HSC for update. In a system with only one HSC installed, that is the primary HSC, so all users will need to use the -p switch. If two HSCs (supporting up to 10 drives) are installed, the FWPIAUPD command will need to be run twice, once with -p and once with -s. The order they are run is not important. (There is no way to tell the utility to do both at once.) The supplied PRIUPDAT.BAT and SECUPDAT.BAT batch files update the primary and secondary HSCs using the command lines described above. -------------------------------------------------------------------------------- BOOT BLOCK UPDATES -------------------------------------------------------------------------------- The boot block on the HSC cannot be updated. Never use the -b or -boot switch on the command line. If the utility is run interactively, always answer NO to the "Update the boot block" question. If you do attempt to update the boot block, it will not be modified, that area of the flash chip is write-protected. However, when the utility attempts to verify that the code in the flash matches the code in the H2FHxxxx.HEX file, the verify will fail. Please note that this is a "false" warning - the boot block on the HSC is still perfectly fine since it is write-protected. The reason the verify fails in this case is that each version of firmware places a time/date stamp of when the firmware was compiled into the boot block area of the H2FHxxxx.HEX file. It is this data that changes with each new file and causes the verify to fail. ================================================================================ KNOWN ISSUES/WORKAROUNDS ================================================================================ - None. ================================================================================ FEATURES ADDED IN THIS RELEASE ================================================================================ HSC 0.09: - Normally the HSC queries the BMC every several seconds to obtain power supply status. Normally, without knowing the number of power supplies the HSC cannot communicate via SAF-TE because many SAF-TE commands use fixed length responses, and one factor in that length is the number of supplies. To support BMC-less operation, the HSC now quits attempting to communicate with the BMC after 5 communication failures in a row, and declares that there are 0 monitorable power supplies. This allows SAF-TE communications to proceed. ================================================================================ ISSUES FIXED SINCE LAST RELEASE ================================================================================ HSC 0.10: - The HSC did not handle SCSI messages that used multiple message bytes properly. This caused Linux install failures with certain RAID cards and Linux versions. HSC 0.10 corrects this. Note that the HSC doesn't support multi-byte messages, but it now rejects them correctly. HSC 0.09: - HSC 0.08 acceptS certain system and device ACPI power state values and not others. HSC 0.09 now accepts all ACPI states defined by IPMI 1.5. HSC 0.08: - Initial release ================================================================================ REFERENCE MATERIAL ================================================================================ Intel(R) Server Board SHG2 Technical Product Specification (TPS) [END OF HSC RELEASE NOTES]