Enterprise Platform & Services Marketing * Intel Corporation * 2111 N.E. 25th Avenue * Hillsboro, OR 97124 DATE: May 14Intel® SSH4 BIOS Release Notes P14 Build 97: 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 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 © 2001, 2002, 2003, 2004 Intel Corporation.About This Release Build # : 0097 Build Stamp : SSH40.86B.0097.P14.0405141707 Build Date : May 14, 2004 BIOS Components/Contents Processor stepping(s) supported: Intel® Xeon™ processors Microcode update versions: CPUID Code Name Microcode update ID 0F11h C0 0A (MU2F110A) 0F22h A0 05 (MU2F2205) 0F25h B1 1D (MU2F251D) 0F26h C0 0E (MU2F260E) System hardware configurations supported: SSH4 Beta 2 / Silver / Gold board System FW Requirements/Revisions BMC FW : 9 or later revision Important Installation Notes NOTICE1: Systems with any BIOS revision earlier than Build 59, must first update to Build 59 or later using Phoenix Phlash (i. e. BIOS59PH.ZIP). Once the system has been updated to Build 59 or later, it can be updated to later releases using Phoenix Phlash or Intel iFlash. NOTICE2: There is a limitation when BIOS is updated on windows 2003 system using BIOS P08 or before. If you update BIOS to BIOS Build 0086 or later on your Windows 2003 system, must first delete the IBM Active PCI device driver from your system, and then please update BIOS. At the end, reinstall the IBM Active PCI device driver to your system. 1. Updating Boot Block Boot Block update required: No 2. Upgrading BMC Note: BMC must be updated with BMC09 or later before upgrading the BIOS. The new sensor number specification was supported from BIOS 0038 and BMC 09. So, BIOS and BMC FW can't handle some sensors correctly except for the combination of revision number designated by BIOS or FW release notes. In updating function, they do not have any limitations each other about the revision number. 3. Upgrading SDR The FRU SDR must be updated to AC1 or later before updating the BIOS. The new sensor number specification was supported from BIOS 0038. So, SDR also must support it , AC1 or later are supporting it. In updating function, they do not have any limitations each other about the revision number. Please read the release notes for the FRUSDR package prior to performing this update. 4. Creating a Bootable Floppy * You must use a DOS system to create the bootable floppy. * Place an unformatted floppy diskette in the floppy drive and format the floppy using the /S option. Example: "format a: /s" * Alternatively, place a formatted floppy in the floppy drive and use the "sys" command. Example: "sys a:" 5. Making a BIOS Upgrade Floppy * Follow the instructions (above) for creating a bootable floppy to create a bootable floppy diskette. * Insert the bootable floppy into drive a:. * Extract the contents of the BIOS zip file onto the bootable floppy. 6. Upgrading a BIOS * 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. * 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. * Boot the system from the floppy disk drive. Automatically, system BIOS is updated. * This update processing takes 3 to 4 minutes. Never turn off the system during the update processing. The following message appears when the update processing is finished. Flash memory has been successfully programmed PRESS ANY KEY TO RESTART THE SYSTEM If the system does not restart, TURN THE POWER OFF, THEN ON * Remove the floppy and Press the Enter key to reboot the system. * Check to make sure the BIOS version is the new version as the system reboots. * 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. 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. 7. Performing a BIOS Recovery * Unzip the crisis zip file to a temp directory on a system * Insert a blank, formatted floppy in A and run CRISDISK.BAT. Follow the instructions on the screen thoroughly. This makes the diskette. * With the system powered off, insert this diskette. * Place a jumper on BIOS Recovery (Alpha/Beta board: pins 9-10, Silver or later boards: pins 3-4) of the BIOS jumper block (see jumper diagram to locate the jumper block). * Place a jumper on header JP5 to disable the FRB3 timer if you update BIOS from Build 1012, 0012 or 0006. * Power up the system. System will beep intermittently for about 2 minutes. * When it stops beeping, power the system off, remove the jumper, remove the floppy diskette and power the system back up. * Make sure you clear CMOS as well after this is all done. Known Issues/Workarounds 1. You can not update the system that has former version BIOSes using the iFlash utility. Because the Data area mismatch is detected by changing BIOS area in this version. You must first update your systems to 0044 using the Phlash utility. 2. BIOS Build0097 does not support –321 boards which has an AIC7902 A1. 3. Set the FRB3_Disabled Jumper when you update BIOS from Build 1012, 0012 or 0006 by Crisis recovery. 4. This BIOS can use on Power On Refresh system 5. BIOS Build0097 supports both 7899 and 7902 A2 SCSI BIOS as onboard device on same PCID. (7899 BIOS: v2.57S13, 7902 BIOS: 4.10.1) 6. Please select following BIOS setup option according with Hot-Added PCI spec. Setup Item: Advanced>>PCI Configuration>>Hot-Plug PCI Control >>Reserving memory space for PhP Option: [Disabled] = (Default) Memory hole for empty slots are not reserved. [Minimum] = 6MB. Memory hole for each empty slots are reserved to 6MB. [Middle] = 48MB Memory hole for each empty slots are reserved to 48MB. [Maximum] =96MB Memory hole for each empty slots are reserved to 96MB. 7. Please install the filter driver (ibmhpf.sys/imbhpa.sys) for Windows 2000. Note that Windows2000 will detect an Unknown device error in Device manager if these drivers are not installed. Features added in this release * None Change List History - BIOS Build 0097 [P14] It’s based on Build 0096 [RC31]. (1) Applied the latest Production MU for Intel® Xeon™ MP processors B1/C0 stepping. (2) Banner was changed for production phase, [P14]. - BIOS Build 0096 [RC31] It’s based on Build 0095 [RC30]. (1) Modification for solving the tracker #15378. Applied BIOS workaround for CMIC autocompensation issue. [Workaround] -If CMIC Function 2 register 64h is 7Bh or greater, change register 64 to 77h. -If CMIC Function 2 register 64h is 7Ah or less, allow to automatically set register 64h. (2) Modification for solving the tracker #15979. I/O reservation region of PhP function was extended. (2) Modification for solving the tracker #15707. INTERRUPT SOURCE OVERRIDE ENTRY of ACPI table was deleted. - BIOS Build 0095 [RC30] It’s based on Build 0094 [P13]. (1) Modification for solving the tracker #15657. Modified the _CRS method of USB device. (2) Modification for solving the tracker #16186. Applied the latest Production MU(0D) for Intel ® Xeon™ MP processors C0 stepping. - BIOS Build 0094 [P13] It’s based on Build 0093 [P12]. (1) Applied the latest Production MU for Intel ® Xeon™ MP processors B1/C0 stepping. (2) Enabled Fast-Strings(MSR 1A0h.bit0). (3) Updated the BIOS Copyright to 2004. - BIOS Build 0093 [P12] It’s based on Build 0092 [P11]. (1) Modification for solving the tracker #14820. Applied the latest Production MU for Intel® Xeon™ MP processors C0 stepping. - BIOS Build 0092 [P11] It’s based on Build 0091 Beta (1) Banner was changed for production phase, [P11]. - BIOS Build 0091 Beta It’s based on Build 0089 [P10] (1) Modification for solving the tracker #15013. -Note that the detecting option ROM error issue isn't fixed by a new BIOS because the bug is only to display wrong messages (Requested 00Kb) when option rom error is detected. (2) Modification for solving the tracker #15300. -Supported additional request from Intel. BIOS will display POST messages to indicate sparing/mirroring mode when it is enabled by setup. Please refer to DR15300. (3) Applied the latest MU for Intel® Xeon™ MP processors C0/ A0/B1-Step. - BIOS Build 0089 [P10] It’s based on Build 0088 Beta (1) Removed a MU (MU2F2604) for Intel ® Xeon™ MP processors 4M cache. (2) Banner was changed for production phase, [P10]. - BIOS Build 0088 Beta It’s based on Build 0086 Beta (1) Modification for solving the tracker #14509. -Modified a BIOS issue in emulating INT10h Function 13h. (2) Modification for supporting Sparing/Mirroring memory features. Note that BMC FW 00.25 or later revisions are needed to support them. - BIOS Build 0086 Beta It’s based on Build 0083 [P08] (1) Modification for solving the tracker #14744. -Added a _HPP method in ASL. -Modified a _HID method of IBM Active PCI Device so that Filter driver (IBMHPF.SYS) can not be loaded. NOTICE: This modification has a limitation when BIOS is updated on windows 2003 system using BIOS P08 or before. If you update BIOS to BIOS Build 0086 or later on your Windows 2003 system, must first delete the IBM Active PCI device driver from your system, and then please update BIOS. At the end, reinstall the IBM Active PCI device driver to your system. (2) Modification for solving the tracker #14772. -NUMLOCK is forcibly disabled when a keyboard is not attached. (3) Modification for solving the tracker #14799. -Modified a function for detecting mis-matched processors. (4) Modification for solving the tracker #14820. -Applied Micro code M02F26041 (MU2F2604) for Intel® Xeon™ MP processors 4M Cache. (5) Modified Multi Language messages for PnP POST error messages. - BIOS Build 0083 [P08] It’s based on Build 0082 Beta. (1) Modification for solving the tracker #13687. -Applied the latest MU (MU2F250E) for Intel® Xeon™ MP processors B1-Step. (2) Banner was changed for production phase, [P08]. - BIOS Build 0082 Beta It’s based on Build 0081 Beta Modification for solving the tracker #13687. -Applied the latest MU (MU2F250B) for Intel® Xeon™ MP processors B1-Step. - BIOS Build 0081 Beta It’s based on Build 0080 [P07]. (1) Modification for solving the tracker #11923. Applied the BIOS recommendation on GCHE Newsletter No.15. Alert on PLL losing lock is disabled. (2) Modification for solving the tracker #13091. Supported PME# signals from Slot#3 and Slot#4. BIOS checks the FRU on the baseboard. If the Board Part Number bytes is A60891-704 or later, BIOS will handle PME# from Slot 3-4. (3) Modification for solving the tracker #13687. -Applied the latest MU (MU2F2504) for Intel® Xeon™ MP processors B1-Step. -Modified the function for detecting Unsupported CPU Error so that the error is not detected if Gallatin B1-step processors are populated. (4) Modification for solving the tracker #14041. Provided the BIOS proc frequency menu if BIOS detects unlocked processors. Note that this BIOS proc frequency menu is not supported on Production BIOS. (5) Modification for solving the tracker #14087. Changed the Refresh Delay value. ServerWorks recommends that this value is set to RCR-2 (RCR is Bus=0, Device=0, Function=0, Offset=79h). BIOS applied it. (6) Modification for solving the tracker #14089. Enabled the optimal timing between writes and reads. (Bus=0, Device=0, Function=0, Offset=9Bh, bit5: 1b). (7) Modification for solving the tracker #14099. Changed the Processor Family in type4 structure to B5h from B3h. The B3h indicates "Intel(R) Xeon(TM) processor" as Processor Brand. It should be B5h that indicates "Intel(R) Xeon(TM) processor MP". (8) Modification for solving the tracker #14118. Updated the BIOS Copyright to 2003. (9) Modification for supporting Windows 2003. Added the BMC resource information to ASL to pass the HCT11.1a. SSH4 BIOS Release Notes SSH4 Server Baseboard Management Controller (BMC) Firmware Version 0.28 (Bootblock Version 0.07) Release Notes - April 23, 2003 Introduction. This document applies to the firmware used in the Intel SSH4 server Baseboard Management Controller (BMC). File SSH4_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 SSH4_xx.HEX The supplied UPDATE.BAT file performs this command. ************************************************************************ SPECIAL NOTE: If you have a system that was updated to BMC version 0.25, which included updating the boot block, you will have to update your boot block again, following the procedure in the next section. ************************************************************************ 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 SSH4_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 SSH4_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(s) and open the chassis. 2. Install a jumper on the two pins at jumper block 8H, pins 9 & 10. The jumper block is just behind the memory board near the center of the board. 3. Plug in the AC cord, power up and boot to DOS. 4. Enter the command: FWPIAUPD -ni -u -o -p -b SSH4_xx.HEX OR Use the supplied Upd_Boot.bat 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. None known. SSH4 BMC firmware release history. BMC version 0.28 (bootblock version 0.7) April, 2004 Bootblock checksum: F3D5h Opcode checksum: FD98h Include fix for DCS 15733: BMC 27 not correctly clearing configuration error Bit 5. BMC version 0.27 (bootblock version 0.7) November, 2003 Bootblock checksum: F4D5h Opcode checksum: F4C5h Include fix for DCS 15287 SCSI performance lag SEL. BMC version 0.26RC2 (bootblock version 0.7) October 6, 2003 Bootblock checksum: F4D5h Opcode checksum: F4C3h BMC version 0.26RC2 (bootblock version 0.7) October 2, 2003 Bootblock checksum: F4D5h Opcode checksum: F4C3h Includes fixes to memory sparing code. DCS 14792 PCI slot numbering incorrect. BMC version 0.26 (bootblock version 0.7), September 9, 2003 Bootblock checksum: F4D5h Opcode checksum: B65Dh Includes memory sparing and mirroring code. BMC version 0.25 (bootblock version 0.8) August, 2003 Not recommended for use. BMC version 0.24 (Bootblock version 0.7), November 14, 2002 Bootblock checksum: F5D5h Opcode checksum: E0C4h DCS 12631 - The BMC did not always report the correct DIMM population via the DIMM sensors. This has been corrected in BMC 24. END SSH4 BMC Release Note Intel(R) Server Board SSH4 FRU/SDR RELEASE NOTES ============================================================================= Intel Enterprise Platform & Services Marketing Intel Corporation 2111 N.E. 25th Avenue, Hillsboro, OR 97124 USA ============================================================================= DATE: April 14, 2004 TO: Intel(R) server board SSH4 customers SUBJECT: FRU/SDR 5.6.A ============================================================================= 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 ============================================================================= This document describes some specifics of the Intel(R) server board SSH4 FRU & SDR Utility Package Version 5.6.A. This utility is used for updating the server management subsystem product level Field Replacement Unit (FRU) and the Sensor Data Repository (SDR). ============================================================================= 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 Windows 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(R) server platforms SPSH4 & SRSH4: 1. To display the Intel(R) server board SSH4 SM BIOS area: C> FRUSDR /P /D SMB 2. To display the Intel(R) server board SSH4 SDR's: C> FRUSDR /P /D SDR 3. To display the Intel(R) server board SSH4 BMC FRU: C> FRUSDR /P /D FRU 4. 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 ============================================================================= None. ============================================================================= FEATURES ADDED IN THIS RELEASE ============================================================================= Version 5.6.9: - Added support for Intel(r) Xeon(tm) C0 processors. Version 5.6.8: - Added support for the new Memory Sparing function. ============================================================================= ISSUES FIXED SINCE LAST RELEASE ============================================================================= Version 5.6.A: Changed the Fan Speed Control SDR record Temperture 2 from 20h to 1Bh, and Control Value 4 from 66h to 64h per tracker 16131. Version 5.6.9: None. Version 5.6.8: - The Manufacturer's Name (MN) field in the baseboard FRU Board and Product areas are no longer automatically programmed. OEMs can use this field to insert their own name. ============================================================================= REFERENCE MATERIAL ============================================================================= Intel(R) Server Board SSH4 Technical Product Specification (TPS) [END FRUSDR OF RELEASE NOTES]