================================================================================
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    : 	August 8, 2016
TO      : 	Intel(R) Server Board S2600WT Product Family customers
SUBJECT : Release Notes for System Firmware Update Package 
================================================================================
                              ABOUT THIS RELEASE
================================================================================
BIOS:     	01.01.0018
ME:        	03.01.03.032
BMC:     	01.46.9995
FRUSDR:	    	1.13a
================================================================================
                           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   0x00000036   Production (E5-2600 v3 C0/C1)
0x406f1   0x0b000010   External   (E5-2600 v4 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) V13.1 Build 13
- BIOS downgrade from this release only can be done by using the BIOS recovery mode

================================================================================
                  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)
   V13.1 Build 13
 - 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 from D0055(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 from D076 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.
  
================================================================================
				BIOS 01.01.0018
================================================================================
EPSD 100253916 : The default value of BIOS setup option [Snooped Response Wait Time for Posted Prefetch] is not correct during R9 to R16 update 
EPSD 100254004 : Security Fix for Grantley SmmRuntime driver 
EPSD 100253648 : Grantley memory RAS feature ECC error Leaky Bucket decay time window is set to 100 days, which is too long.
EPSD 100253299 : 4x4x4x4 on Slot5 for S2600CW2SR
EPSD 100253233 : CC_SPARE bits not cleared in accordance with E5-2600V3 spec update (CDI # 550584) errata HSE22S - may cause NVMe issues
EPSD 100253548 : Fan PWM Limit default value and operational range are wrong
CCB 391: Implement a BIOS setup option to Limit PWM to a maximum value similar to Purley
EPSD 100252598 : [x] Add more DIMM support -- supported DIMM informaiton can't be shown correctly in SMBIOS Table Memory information
EPSD 100032105 : [E5-2600V4][E5-2600V4 CPU] Error message of memory channel A not match other Channel.
Update ME to 03.01.03.032
EPSD 100032453 [E5-2600V4][E5-2600V4 CPU]The String not right at IOU Non-Posted Prefetch Control in BIOS Setup.
EPSD 100251776 [S2600WT] VR Watchdog reports it has been asserted after Global reset(Update ACM to v3.0.5)
hidden "Platform type input for SPD page selection"
BIOS workaround for EPSD 100031139 [Switch]The DPC function couldn't work on the PCIe switch AIC via Switch AIC
EPSD 100032467 [E5-2600V4][E5-2600V4 CPU] Press Hot key F6 , F12 will not display any screens describe during POST
EPSD 100252973 : NTB performance drop with DMA-enabled
         Notes: Need to disable Relaxed Ordering under IIO configuration setup menu when DMA-enabled in NTB Linux driver.  
Roll back W/A for [E5-2600V4] 2400MHz LRDIMM size missed in power cycling test
EPSD 100251966 : 32GB Hynix LRDIMM size mismatch during cycle test
EPSD 100031669 : Intel SSD AIC SSDPEDMX020T4 Link margin Fail
EPSD 100252478 After saving in setup, PXE boot option is not maintained during reboot
EPSD 100032100 : [E5-2600V4][E5-2600V4 CPU]Hot key F12 without function during POST when boot mode change to UEFI
Sync Grantley RC 3.2.0 code
EPSD 100032112 : SBO function not correct when insert USB device in J3A1 and J8E2
EPSD 100252440 Inversion PCIE card location was detected between Riser slot 1 and slot 2
EPSD 100252718 : Use Angilent Card to inject Poisoned TLP and Surprise Link Down fatal error the function is abnormal.
IpPlan v1.12 update.
IpPlan v1.12 document update.
NO SIGHTING: IpPlan Doc update.
EPSD 100252195 :Clone of: [X] DMI type 41 records is not correct for onboard and IO module NICs.
EPSD 100252209 [X] Syscfg 13.1-15 sets [Snooped Response Wait Time] and [Non-Posted Prefetch] options fail with BIOS R15 + E5-2600V4.
EPSD 100252266 : [E5-2600V4][TGF]Connect Resistor TGF card to Riser slot 2 and set bifurcation to x16, SUT hang at POST screen.
EPSD 100031863 [E5-2600V4][E5-2600V4 CPU]SMBIOS Type 7 L3-Cache associativity should display 20 way not fully.
EPSD 100031758 : [E5-2600V4][E5-2600V4 CPU] Error message not match EPS1.16 at Error manager
Update copyright to 2016
================================================================================
                            ME 03.01.03.023
================================================================================
SPS FW sends P-state change requests to OS when no power limiting policy is configured.
Can't set power policy in S5 after Power Button Override.
SPS generates health event in each AC cycle.
SmaRT&CLST Status of Get SEL Entry have wrong byte order.
Predictive Power Limiting NM Policy does not meet 99.5% below power limit criteria in case of SMBAlert assertions (Fast #PROCHOT).
CPU cannot reach max frequency when stressed by PTU in SMI Optimized mode.
NM PTU option ROM running on HSX systems will exit early, after first characterization, and may cause system instabilit

===============================================================================
                        KNOWN ISSUES/WORKAROUNDS/REQUIREMENTS
===============================================================================
None.
  
===============================================================================
                             BMC 01.46.9995
===============================================================================
-none: Watchdog assert happened on Nodes with bigger number while unplug PSU
on S2600KP/S2600TP
-EPSD100253232: [S2600WT] FRUSDR112 and FRUSDR113 dont detect PSUs on a 3rd party chassis
-EPSD100251931: Email and SNMP alerts are not sent during a drive fault on 1U HSBP.
-EPSD100253499: EWS show in Chinese not align with English
-EPSD100252884: Change FAN to auto-rearm, fan status cannot show correct status on EWS
-none: Remove the 2130W PSU FW Ver24 for update hang issue
-EPSD100252472: Defect title: vulnerabilities found on BMC release 01.41.9579
-EPSD100252826: BMC FW Use of Voltage Fault (D1h) Violates DFT Rule #1619
-EPSD100252984: modify master.cfg to automation will results fail
-EPSD100249322: duplicate response from remote host during SSH SOL/SMASH session
-EPSD100252884: Change FAN to auto-rearm, fan status cannot show correct status on EWS
-none: After load FCT or Default SDR in 24HDD System, HSBP update process cannot start
-EPSD100031139: The DPC function couldn't work on the PCIe switch AIC via Switch AIC
               (Implement OEM Misc command (NetFn:0x30, Cmd:0x67) to detect SSD switch AIC)
-EPSD100248833: SMASH cannot read recent SEL events when SEL has a high volume.
-EPSD100031101: IE11 displaying EWS->Configuration->KVM & Media /SOL & SMASH , Sever 
                Diagnostics->POST Codes with help ON, text exceeds the Box size
-EPSD100252439: PCIe SSD Add-in-Card present slot bitmap don't match current inserted 
                slot number in EFI shell

=============================================================================
        SYSTEM HARDWARE & SOFTWARE REQUIREMENTS/REVISIONS
=============================================================================
- S2600WT baseboard PBA G11481-201 or higher.
- E5-2600 v3 processor C1 stepping or higher.
- BMC FW 01.46 or later.
- BIOS 1.01.009 or later.
- Front Panel, Hot-swap backplane, and Baseboard FRU data must be available
  for chassis auto-detection to succeed.

================================================================================
                             FRUSDR 1.13a
================================================================================    
-Update frusdr.efi and ipmi.efi utility 13.1 build 11.
-Update master.cfg and mster_internal.cfg files with added the wildcard "%".
-Add S2600WTTS1R.fru file for board S2600WTTS1R 10G.
=============================================================================
                            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) 2016 Intel Corporation.

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

[END OF RELEASE NOTES]
