Intel(R) Server Board S2600WT Product Family
Firmware Update Package for Intel(R) One Boot Flash Update Utility and
Windows* Preboot Execution Environment 
================================================================================
Intel Enterprise Platform & Services Division - Marketing
Intel Corporation
2111 N.E. 25th Avenue, Hillsboro, OR 97124 USA
================================================================================
DATE    : 	Oct 04, 2018
TO      : 	Intel(R) Server Board S2600WT Product Family customers
SUBJECT : Release Notes for System Firmware Update Package 
================================================================================
                              ABOUT THIS RELEASE
================================================================================
BIOS: 01.01.0027	
ME:   03.01.03.050     	
BMC:  01.53.11210 	
FRUSDR:	1.17	
================================================================================
                           Support Platforms and Dependency
================================================================================
Processors supported:
Intel(R) Xeon processor E5-2600 v3 series
Intel(R) Xeon processor E5-2600 v4 series

Microcode update versions:
CPUID     Version      Status
0x306f2   0x0000003d   Production (Haswell EP C0/C1)
0x406f1   0x0b00002e   External   (Broadwell EP B0)

Production boards:
  Product		Fab Version	      
  S2600WT		Fab2 or above  

The following update process must be followed to ensure a trouble free update.
1.	Manageability Engine (ME) firmware
2.	FD
3.	BMC firmware
4.	BIOS
5.      FRUSDR

================================================================================
                             IMPORTANT NOTE!!!                   
================================================================================
- This Update package must be installed using Intel(R) One-boot Flash Update (OFU) V14.0 Build 15
- BIOS downgrade from this release only can be done by using the BIOS recovery mode
- Due to a fix in the BIOS R01.01.0020, older version of update utilities in older FSUP packages (R018 and older) can’t be used for downgrade even though under recovery mode, the customer needs to manually replace the utilities with the newer version utilities.
================================================================================
                  System Firmware Update Package Usage instructions                   
================================================================================
This package can be updated using one of the following methods:
 - Windows* or Linux* operating system using Intel(R) One-boot Flash Update (OFU)
   V14.0 Build 14
 - Windows* Preboot Execution Environment (WinPE)

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(R) 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:
  <OFU install folder name>:\flashupdt -u  <package folder name>\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.
 ================================================================================
			IMPORTANT NOTICE
================================================================================
1. BIOS R01.01.0018 will include a security revision upgraded. 
   BIOS downgrade is not allowed from the OS and can only be performed on uEFI shell using the BIOS recovery jumper method.

2. BIOS R01.01.0009 will enable UEFI Secure Boot and include below limitations:
    - Please read "BIOS UEFI SECURE BOOT IMPACT AND MITIGATION METHOD" section in this BIOS release notes
    - All customer settings saved in BIOS NVRAM will be lost after new BIOS upgrade
    - BIOS downgrade is not allowed if user has enabled BIOS secure boot. All customer setting will be lost also if downgrade to previous BIOS release
    - Backup BIOS region is also required to be updated to prevent recovery failure please use release package to update BIOS
    - There is downgrade hang risk if you don't follow above rules
    - Further BIOS release will not suffer from these side effects as the NVRAM region is formatted as authenticated variable storage
3. System will hang 0xbf after downgrading BIOS (E5-2600V4 code tree) to R0011/R0009(E5-2600V3 code tree) randomly
    - Set SUT to recovery mode to power on, then set it back to normal boot to see whether it is recovered
4. The iFlash32 utility parameter of 'UpdateNvram' is not supported under Normal Mode, however it is only supported under Recovery Mode
5. Design change for <PCIe correctable error threshold> to change default setting from <All> to <10>. Need to press <F9> to see the new default string
6. Suggest to press 'F9' to load default if using the 'IOU Non-posted prefetch control' setup options in the first time
================================================================================
     BIOS UEFI SECURE BOOT IMPACT AND MITIGATION METHOD
=================================================================================
1. Customer Setting Loss Issue and Mitigation Method
    When user upgrades BIOS with secure boot feature, the NVRAM will be automatically
  formatted as authenticated variable physical storage. However, all previous customer
  settings storage in NVRAM will be lost even if user does not enable UEFI secure boot
  feature.
    Users can take the follow recipe to save and restore their settings based on
  the actual NVRAM usage if they wish to upgrade or downgrade between BIOS with or
  without secure boot feature.
    Supposing customer requires to save & restore their specific NVRAM named 'var':
  Steps:
  1. Prepare FAT partition USB key (or HDD).
  2. Boot to EFI shell.
  3. Check the file system mapping (e.g. fs0:) of the USB key with 'map -r' command.
  4. Use 'dmpstore var -s fs0:\var.bin' to save the variable to the physical file.
  5. Perform BIOS update and reboot system.
  6. Boot to EFI shell.
  7. Use 'dmpstore var -l fs0:\var.bin' to restore the variable.
  8. Reboot the system if the customer setting requires reboot to take effect.

Notes:
  1. Immediate reboot after BIOS update is mandatory. Or the restore operation will
     not take effect.
  2. Customers can repeat step 4 and step 7 for several times if they need to save & restore
     multiple NVRAM variables.
  3. Most of BIOS customer settings by SysCfg can also be restored in this way. Customers
     can follow previous step1~8 by substituting 'Setup' for 'var' in the sample.
  4. For BIOS downgrade case, step7 cannot be used to restore authenticate variables
     (e.g. PK, KEK, DB, DBX) to non-authenticated NVRAM storage

2. Recovery Mode Failure
   There is known bug that it cannot POST successfully with authenticated NVRAM storage.
   This will cause platform recovery failure and permanent deny of service (PDOS) if the
   primary BIOS region gets corrupted for some reason. It is required to update backup BIOS
   region when upgrade BIOS capsule with secure boot feature.
Notes:
  For downgrade case, user is not required to update backup BIOS region as new
  BIOS with secure boot feature can handle NVRAM with old storage format:
  it will format it to new authenticated variable storage automatically.
  However, care must be taken when downgrading BIOS in recovery mode: After flashing
  BIOS without secure boot feature, user should restore recovery HW jumper immediately
  before platform reset.If platforms reset occurs before restoring recovery HW jumper,
  the backup BIOS will once again format NVRAM to new storage format, which will cause
  newly flashed BIOS (without secure boot feature) POST failure after user restores
  recovery HW jumper.
================================================================================
		Issues Fixed in BIOS 01.01.0027
================================================================================
Unable to successfully boot after disabling PXE port with ITK
Unable to boot PXE using Intel X710 10 GbE NICs on Legacy Mode
Add Infineon FW update capability support in BIOS and UEFI application
Update the Security Rvision:0909
[Windows Server 2012 R2] ACPI_BIOS_ERROR BSOD
Some items failed when running  command "chipsec_main.py"
Update microcode BDW to 0b00002e
Update microcode HSW to 0000003d
Update RC V4.4
================================================================================
                Issues Fixed in ME 03.01.03.050
================================================================================
Diagnostic interface crash after sending IPMI command SendRawPmBusReq with
imput: 0x2E 0x00 0xD9 0x57 0x01 0x00 0x50 0x00 0x7E 0x00 0x00 0x00 0x20
0x00 0x00.
Adjusted diagnostic command filtering according to FAS.
CUPS sensors don’t get initialized and get updated if socket initialization
information is not received during platform boot phase.
Race condition in FW caused NM to incorrectly assume that RTC synchronization
failed.
===============================================================================
                Issues Fixed in BMC 01.53.11.210
===============================================================================
Defective 1600W PSU is not properly communicating the failure status to BMC - Fully Redundancy has been lost but system is reporting the redundancy as OK.
The Server system will not reboot after CATERR generate.

================================================================================
                Issues Fixed in FRUSDR 1.17
================================================================================    
-Modify master.cfg to set the 2U Riser 3 fab 2's FRU and Temp sensor. 
-Update new FRUSDR utility ( FRUSDR_V14_0_Build9_AllOS ).

=============================================================================
                            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) 2018 Intel Corporation.

A portion of this firmware is open source code, which falls under the
GPL 2.0 license.  

[END OF RELEASE NOTES]
