================================================================================ Intel(R) Server Board S2600KP Product Family and Intel(R) Compute Module HNS2600KP Product Family Firmware Update Package for Intel(R) Deployment Assistant, Intel(R) One Boot Flash Update Utility, The embedded EFI Shell, Windows* Preboot Execution Environment ================================================================================ Intel Enterprise Platform & Services Division - Marketing Intel Corporation 2111 N.E. 25th Avenue, Hillsboro, OR 97124 USA ================================================================================ DATE : October 22, 2014 TO : Intel(R) Server Board S2600KP Product Family and Intel(R) Compute Module HNS2600KP Product Family customers SUBJECT : Release Notes for System Firmware Update Package ================================================================================ ABOUT THIS RELEASE ================================================================================ BIOS: 01.01.0005 ME: 03.00.07.114 BMC: 01.08.6942 FRUSDR: 1.02 ================================================================================ Support Platforms and Dependency ================================================================================ Processors supported: Intel(R) Xeon processor E5-2600 v3 series Microcode update versions: Intel(R) Xeon processor E5-2600 V3 series C1 stepping: 0x00000023 CPUID = 0x306f2 Production boards: Product Fab Version S2600KP Fab3 (PBA# -350) or above S2600KP F Fab3 (PBA# -350) or above The following update process must be followed to ensure a trouble free update. 1. BMC firmware 2. BIOS 3. Manageability Engine (ME) firmware 4. FRUSDR ================================================================================ System Firmware Update Package Usage instructions ================================================================================ This package can be updated using one of the following methods: - The embedded UEFI shell - Intel(R) Deployment Assistant - Windows* or Linux* operating system using Intel(R) One-boot Flash Update (OFU) V11.0 Build 14 or later) - Windows* Preboot Execution Environment (WinPE) To update from the embedded EFI Shell Update system firmware from Intel server EFI shell by the following steps: - Download Intel server system firmware update package from http://downloadcenter.intel.com/ - Unzip package and copy all files to root folder in USB flash drive - Insert USB flash drive to server USB port - Reboot server, system will start BIOS/BMC/FRUSDR update automatically If the unzipped package is not under the root folder of USB flash drive: - Reboot server to EFI shell manually - Run command "map -r" in EFI shell to find the mount point of the USB flash drive - The USB flash drive may mount to fs0: or fs1: or other. - Run command "fs0:" or other to change folder to USB flash drive, - Change folder to the folder storing the firmware package - Run command "startup.nsh" to start firmware update process Please refer to "EFI_Instructions.pdf" in this firmware package for a quick guide to use the EFI commands To Update from Intel(R) Deployment Assistant (IDA) The Intel(R) Deployment Assistant software is easy to use and is present on the "Intel(R) Server Deployment & Management" DVD shipped with the system. User can download the latest version IDA CD ISO image from http://downloadcenter.intel.com/ To use the IDA CD to update the system firmware: - Boot server with IDA CD - Select "Get System Updates" - Choose one of the three options . From http://www.intel.com/support/ Automatically downloads the latest Firmware Update Package from Intel Requires Internet connection Enter your local IP address and proxy configuration Click "Next" to start the download and update process . From my network Download the latest Firmware Update Package from http://downloadcenter.intel.com/ and copy it to a Windows* shared folder Enter your local IP address, the Windows* file server name, and a Windows user name and password Select the firmware package in pop-up window Click "Next" to start the update process . From USB flash drive or Hard Disk Download the latest Firmware Update Package from http://downloadcenter.intel.com/ and copy it to a USB flash drive, then insert the USB flash drive into the server USB port Click "Browse" Select the firmware package in pop-up window Click "Next" to start the update process Note: 1) The Firmware Update Package is in the ZIP file format. Do not unzip before copying to a Windows* shared folder or USB flash drive. 2) The IDA will always update backup bios with this FSUP package even if the IDA backup bios check box is not selected. To update from Windows* and Linux* or operating systems using the Intel(R) One Boot Flash Update Utility (OFU) Intel(R) One boot Flash Update utility can be downloaded from http://downloadcenter.intel.com/ and it is part of the "BIOS, Firmware Update & Configuration Utilities" for Windows* and Linux*. Please refer to Intel OFU user guide about the details of installation and usage of OFU. Use OFU to update system firmware by the following steps: - Install OFU on Windows* or Linux* system - Download the latest firmware update package from http://downloadcenter.intel.com/ - Unzip package to a folder - Run the following command in Windows* command line/Linux* terminal window: :\flashupdt -u \flashupdt.cfg To update from Windows* Preboot Execution Environment (WinPE) The System Firmware Update Package can be inserted to Windows* PE customized image for creating a bootable Windows* PE CD. User is able to update system firmware from customized WinPE CD by the following steps: - Boot server with customized WinPE CD - Run script "WinPE21_x64_Update.bat" or "WinPE20_x86_Update.bat" (name may be varied depends on your own customization) Note: 1. The Intel(R) OFU utility is case sensitive. Therefore, when you transfer the Firmware Update Package using USB flash drive from a Microsoft Windows* system to a Linux environment, you must first extract under the Linux* environment. Otherwise, you will need to mount the USB flash drive manually with 'vfat' option under Linux to avoid conversion from upper case to lower case and vice versa. 2. To make Intel(R) OFU utility run properly under x86 or x64 OS, you have to read OFU release notes on known issues for OFU installation. 3. In this SFUP package, Intel only provide batch file "WinPE_x86_Update.bat" for WinPE2.0 32 bit solution "WinPE_x64_Update.bat" for WinPE2.1/3.0 64 bit solution as an example. Please refer to white paper "White Paper-Intel Server Utilities Procedure for WinPE.pdf" for details on building your own customized WinPE CD. 4. Windows PE 2.0 - built from Windows Vista SP1 32bit or EM64T 5. Windows PE 2.1 - built from Windows Vista SP1 or Windows Server 2008, EM64T 6. Windows PE 3.1 - built from Windows Server 2008R2, EM64T 7. Microsoft IPMI driver is loaded by default from WinPE CD, if you want to use Intel IPMI driver instead of MS IPMI driver for firmware update, you can un-install Microsoft IPMI driver by: Devicesetup.exe ¨Cv remove *IPI0001 Note: IPI0001 is the device ID for Microsoft IPMI driver. 8. If to update backup BIOS region or NVRAM, you need to customize the OFU update scripts (eg.flashupdt.cfg) and add "UpdateBackupBios" or "UpdateNvram" parameter. ================================================================================ BIOS 01.01.0001 ================================================================================ EPSD100244208 SEL intermittently reports therm trip ================================================================================ ME 03.00.07.114 ================================================================================ - For Shared Power Supply configuration, power isn't kept in the range of 2% during power limiting. The power kept in range of 3C 4%. - SMLink0 utilization is too high after disabling Node Manager with Set ME FW capabilities command. - Sporadically MESDC hangs up during reading trace logs via IPMB/RMCPP/HECI interface. - Few events instead of one are send after Flash Wear-Out Protection occurs. - OSPM and DCMI policies are not created when policies maximum number of policies defined in XML file. - BMC OEM readings discovery is working incorrectly in Sx when BMC responded with completion code different from Successful (0x00). - [MESDC] Compliance test NM_13: After running the test the PROCHOT# is not deasserted which may fail other compliance tests with power limiting. - Certain power delivery systems may provide power data which fluctuates outside of the tolerances of the NM PTU power data filtering algorithm causing the Get Node Manager Power Characterization Range command (0x61) to return 0xFFFE power data. - ME goes to recovery state after graceful shutdown when power and thermal readings are enabled. - In G3 to S5 transition ME sends 2 NM Health Events: power readings in domain 0 and inlet temp readings are missing. - BMC set as power source even if only PSU is available when auto configuration is enabled. - P-States cannot be set while platform is in idle state. - Unexpected CLST event is sent during S0->S5 transition. - PSU Monitoring service error during GetSelftestResults IPMI command. - BackBone exceptions during various power flows (SX/Global Reset) or after SKU burning / NMon alwaysOn/ s0only. - Unexpected ME resets during SMBAlert stress test (backbone exception). - MESDC over IPMI causes FW crash in Recovery if MeMdesAddr is disabled in xml. - ME failed during cold reset after continuously setting and resetting ME recovery jumper - two exceptions occurred. - Get NM Capabilities IPMI command return CompCode 0xC0 (Node Busy) when power telemetry is enabled. - Unable to assign GPIO > 15 to MEMHOT, PROCHOT, SMBALERT. - HMRFPO_ENABLE does not always respond during FW update after EOP. - Missing readings policy causes maximum throttling after S3. - Me does not send SMB Alert mask when setting redundant PSU. - Me switches to recovery image when auto configuration is enabled and no sensors are enabled. - Send Raw PMBUS command PMBUS_Revison does not work on SiEn SKU. - Get Sel Entry IPMI command returns too few bytes in Recovery. - SPS FW switches to Recovery during BMC DC Reboot. - BMC OEM readings discovery does not work correctly in Sx. - Platform shuts down during AC Cycles with 0W policies set on all domains. - Threshold Exceeded event desertion not received when BMC sets new power threshold. - Incorrect NM-PTU SHA-256 hash. - Inband PECI Failure health events are not sent in some cases. - "Get Self-Test Results"IPMI command reports PSU Monitoring error for PSU configured as redundant that is missing. - When user issues ˇ°Set Max Allowed CPU P-state/T-stateˇ± command CPU will operate on Max Turbo frequency instead P1. =============================================================================== BMC 01.05.6802 =============================================================================== -EPSD100244631: Added command tracking to prevent the BIOS mailbox or IPMI commands from sending more than one successful initialization sequence to specific PCIe cards on each boot. ================================================================================ FRUSDR 1.02 ================================================================================ - Update SDR as per Kennedy Pass FSC Config Sheet Rev 1.1.xlsm. ============================================================================= 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) 2014 Intel Corporation. A portion of this firmware is open source code, which falls under the GPL 2.0 license. [END OF RELEASE NOTES]