================================================================================
       Intel(R) Xeon(R) Processor-Based Server BIOS Development
================================================================================

INTEL Server Systems 
Intel Corporation
2111 N.E. 25th Avenue, Hillsboro, OR 97124 USA

================================================================================

DATE    : July, 2014
TO      : Intel(R) Xeon(R) Processor-Based Server Platform customers
SUBJECT : Manageability Engine Release notes for version SPS_03.00.06.274

================================================================================
                           LEGAL INFORMATION
================================================================================

Information in this document is provided in connection with Intel Products
and for the purpose of supporting Intel developed server boards and systems.
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.

================================================================================
                              ABOUT THIS RELEASE
================================================================================
Build Stamp : ME Firmware             --> 03.00.06.274
              ME Recovery Boot Loader --> 03.00.06.274
Build Date  : July, 2014

================================================================================
                           Supported Platforms
================================================================================
        S2600WT
        S2600KP
        S2600CW

                
================================================================================
                        ME RECOVERY INSTRUCTIONS
================================================================================
The Recovery process can be initiated by setting the recovery jumper (called ME
FRC UPDT Jumper)

The following steps demonstrate this recovery process:
   1.  Power OFF the system.
   2.  Switch the ME FRC UPDT jumper. Details regarding the jumper ID and
       location can be obtained from the Board EPS for that Platform.
   4.  Power ON the system.
   5.  Enter Setup and verify ME status in Server Management, it should be "recovery"
   6.  Boot to EfiShell and update ME if necessary
   7.  AC OFF the system, and revert the ME FRC UPDT jumper position to
       "normal operation".
   8.  Power ON the system.
   9.  Enter setup and verify ME status in Server Management, it should be "OK"

Note 1 : ME will continuously monitor recovery jumper. Whenever ME FRC UPDT is
         asserted ME will immediately switch to recovery mode.  AC Power cycle
         is required after de-asserting ME FRC UPDT jumper for ME to function
         normally.
Note 2 : When MC FRC UPDT jumper is asserted with AC OFF, ME will restore to
         factory default settings.


================================================================================
				ME FW Capsule INSTALLATION NOTES
================================================================================
WARNING:  It is very important to follow these instructions as they are written.
Failure to update using the proper procedure may cause damage to your system.

!!!!! AC failure during update may cause damage to your system and be unrecoverable !!!!!


Please follow the below procedure to update ME using UEFI iFlash32 13.0 Build 5
   1.  Boot the system to EFI Shell
   2.  Download ME release package
   3.  Unzip the ME release package to HD or USB Flash Drive
   3.  Map the respective storage device in system with the command
           Shell> map -r
   4.  Change the Shell to mapped device file system
           Example: Shell> fs0: (or fs1:)
   5.  Run the IFlash32 utility on the prompt.
       Use ME_xx_xx_xx_xxx.cap file when ME operational Image update is required.
       Use MEComplete_xx_xx_xx_xxx.cap file when Only whole ME Image update is required.
           fs0:\> IFlash32 [File Name] /u /ni
   6.  Reboot system after the update is completed.


================================================================================
			KNOWN ISSUES in 03.00.06.274 release (Production RC)
================================================================================
* If host main power delayed relatively to the standby power for 720-770ms ME stop
  responding.
* Sporadically Watchdog reset occurs when ME is working as MCTP Proxy. 
* For Shared Power Supply configuration power isn't kept in the range of 2% during
  power limiting. The power kept in range of 3 - 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.  
* Unable to set Alert Threshold Limit to 0 degrees (minimum from capabilities) for
  Inlet Temperature Trigger Type Policy. 
* 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.   
* [MESDC] Compliance Test 7.8  Set PSU Configuration w/Power Cycle is failed. 
* [MESDC] ME FW Status in S3 State is failed. 
* During Host Warm Reset flow, unexpected Intel? SPS 3.0 E5 Firmware exception may
  be promoted to Platform Global Reset. 
* 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. 
* 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. 
* Sometimes after setting coefficients via “Set Intel® NM Parameter” IPMI command 
  the ME may respond “Node Busy” (0xC0) on all NM commands for one minute. 

================================================================================
			Issues fixed in 03.00.06.274 release (Production RC)
================================================================================
* Sometimes during SMBalert assertion stress test unexpected ME FW reset may be observed.    
* spsFITc and ME FW do not enable configuring MGPIO number greater than 15.
* Sometimes unexpected SmaRT&CLST event is send by ME FW during platform AC cycle.    
* During Global Reset cycle testing ME Exception: LOADER TIMEOUT may be observed.
* Alerts from redundant PSU are not properly masked, so system could be throttled when
  redundant PSU asserts an error signal. Approx. one second throttling could be observed
  when redundant PSU is unplugged. 



