=============================================================================
         Intel(R) Server Platform ME Firmware Release Notes
=============================================================================

Intel(R) Server Boards and Systems
Intel(R) Corporation
2111 N.E. 25th Avenue, Hillsboro, OR 97124 USA

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

DATE:    May 30,2012
TO:      Intel(R) Server Boards S1200BTLR and S1200BTLRM customers
SUBJECT: Intel(R) SPS ME Firmware "SPS_02.02.00.049" release notes

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

================================================================================
                       SYSTEM FIRMWARE REQUIREMENTS
================================================================================
BIOS Update Utility: 
  UEFI iFlash32 v11.0 Build 11
  
Production boards:
  Product     Fab Version   BMC      FRUSDR    EEPROM
  S1200BTLR    FAB3          N/A      N/A       v1.0       
  S1200BTSR    FAB3          N/A      N/A       V1.0
  S1200BTLRM  FAB1          N/A      N/A       V1.0

================================================================================
                     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.

!!!!! Please make sure AC stays plugged in during the full update !!!!!
!!!!! AC failure during update may cause damage to your system and the system
      may become unrecoverable !!!!!

ME capsule files for S1200BTLR/S1200BTLRM and S1200BTSR are different. 
   Please run below script to update ME in EFI shell:
    For S1200BTLR/S1200BTLRM: updMe_LC_RM.nsh
    For S1200BTSR: updMe_SE.nsh
    

User can update ME image using the following method:

UEFI iFlash32 11.0 Build 11
   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 either of the following methods:
       a) Use the nsh file to do the update:
            fs0:\> updMe_LC_RM.nsh
       b) Run the IFlash32 utility at the prompt.
            fs0:\> IFlash32 [File Name] /u /ni
   6.  Reboot system after the update is completed.
===============================================================================
                     FIRMWARE UPGRADE/DOWNGRADE PROCEDURES
===============================================================================
Upgrade of ME Firmware from this version to later versions will be documented
in the release notes for those versions.

Downgrade of ME Firmware to versions lower than SPS_02.02.00.049 is
unsupported.

Reverting to a lower version of firmware may have unexpected side effects,
including but not limited to user settings reset to defaults, and will always
result in the loss of functionality which was present in the higher version
but was not implemented in the lower version.
We do not guarantee that any downgrade will operate without side-effects.

Always observe caution when downgrading firmware.

===============================================================================
                           KNOWN ISSUES
===============================================================================
- S4 and S3 ACPI states do not work in SUSE* Linux Enterprise Server 10 SP3 x64
  and RHEL* 5.5.
- ME FW may reset itself when mixed set of valid and corrupted IPMI frames is
  sent through SMLink after switch to Recovery image and back to Operational.
- ME fails to boot operational image if per-rail PSU is defined in the power
  readings configuration. Recovery boot loader is running in this case.
- Diagnostic command Get PSU Discovery Data on ME Debug SMBus interface returns
  invalid coefficients. For PMBus version 1.1 coefficients are always 0 0 0.
  For PMBUS version 1.2 coefficients are always 1 0 0.
- BIOS does not handle booting mode information passed in ME Firmware Status
  register. The value set in the register is correct according to NM
  configuration; it is just not respected by the BIOS
- Sometimes ME FW may generate Node Manager Exception Event and Node Manager
  Alert Threshold Exceeded events despite the policy requirements are met.

===============================================================================
                           SPS_02.02.00.049
===============================================================================
- Fixed: ME does not recognize proper CPU ID when host change power state from
         SX to S0.
- Fixed: When ME FW met an exception during platform power state transition,
         the platform could not finalize the transition (host will hang).
- Fixed: ME FW may reset itself during host reset when there is no receiver on
         IPMBus for IPMI messages generated by ME.
- Fixed: ME FW may reset itself during host reset with power cycle.
- Fixed: When ME FW configuration on flash is wrong ME may permanently stay in
         transitioning between Operational and Recovery instead of staying in
         Recovery after few tries.
- Fixed: NM power limiting functionality is not working on Intel(R) Xeon(R)
         processor E5-4600/2600/2400/1600/1400 v2 product families with 17
         watts TDP power.
- Added: This release contains fixes in the ME recovery boot loader section.

===============================================================================
                           SPS_02.02.00.036
===============================================================================
- Fixed: Sometimes the platform is not booting when the Operational image is
         corrupted, ME is not responding.
- Fixed: MEInfo does not show ME features set when ME is in Recovery mode. Also
         Recovery image version is not shown.
- Fixed: HECI reset is not properly supported when ME is in Recovery Mode.
- Fixed: NM does not support DCMI1.1 commands defined in IPMI-spec.
- Fixed: VHD dynamic fusing is not working as expected.
- Fixed: When ME FW configured for operating in All Sx states and platform
         powered up from G3 to S5 power mode. ME FW will stuck during ME reset
         executed in recovery mode.
- Fixed: Get ME-BIOS Interface Version (HECI command) is not implemented in
         Recovery mode.
- Fixed: After Direct Update (without ME reset) Get FW Version HECI command
         returns version of the former image.
- Fixed: General NM Presets configuration in FITc application does not contain
         all S1200BT options.
- Fixed: There are power flow scenarios where ME recovery jumper does not reset
         ME configuration to factory defaults. The jumper is supposed to cause
         ME to enter recovery boot loader code and reset ME firmware
         configuration to factory defaults. The later sometimes does not occur.
- Fixed: Firmware Heartbeat in HECI-1 Extended FW Status register is not
         incremented as it is described in "ME-BIOS-SPS Firmware Interface
         Specification".
- Fixed: After sending the "ME Reset to defaults" IPMI command ME stops
         responding to IPMI commands for 8 seconds.
- Fixed: When Diagnostics service is enabled and Diagnostics Console is
         disconnected switching to Recovery via IPMI or HECI commands takes
         about 5 seconds.
- Fixed: Diagnostics console Compliance Test 1.2. "BIOS HECI Initialization
         message" gives unspecified state of "HECI Initialization message".
- Fixed: In case when flash erase limit has been reached ME generates ME
         Firmware Health event with the event data 3 equal to 0xD5 instead of
         0x01.
- Fixed: Resuming platform after S3 state fails on Intel(R) Xeon(R) processor
         E5-4600/2600/2400/1600/1400 v2 product families, also Dynamic Fusing
         will fail during Sx -> S0 transition.
- Fixed: If ME reset will be performed after AC cycle, then HMRFPO_LOCK HECI
         message will return invalid Nonce causing Direct Update failure.
- Fixed: If invalid image will be used for Direct Update and global reset will
         be issued for ME reset, then ME will state in Recovery mode and
         repairing broken image using Direct Update will fail (HMRFPO_LOCK HECI
         message will return invalid Nonce).
- Fixed: Active policy with Policy Exception Actions = 1 (Shutdown system) may
         sometimes unexpectedly shutdown platform even when power is properly
         capped.
- Fixed: Power Sensor Address set to 0x10 instead of 0x20 in Alert Immediate NM
         Health Event.
- Fixed: Power Reading polling is not working when Scan Period is set to 250 ms
         for BMC set as a Power Reading source.
- Fixed: Node Manager Exception Events are sent after every Correction Time.
         This behavior can cause SEL overflow.
- Fixed: Unexpected shutdown during aggressive policy operation. Sometimes
         aggressive policy could cause platform shutdown even if power limit
         was reached.
- Fixed: Node Manager Exception Event "Policy Correction Time Exceeded" comes
         after double correction time instead of one correction time.
- Added: Thermal policies support was added in current release.
- Added: This release contains fixes in the ME recovery boot loader section.

===============================================================================
                           SPS_02.02.00.0005
===============================================================================
- Fixed: If ME configured for operating in All Sx states then ME will be reset
         during host transition from Sx to S0 state.
- Fixed: Sometimes during ME reset or switching to Recovery image (e.g during
         long continuous tests of FW update) ME FW could get stuck in
         transitioning state. Intensive transmission on SMLink or SMBus may
         increase failure rate.
- Fixed: Sometimes, when ME is configured for operating in all Sx states and
         while platform is performing transition from G3 to S5 and later from
         S5 to S0, ME could be unexpectedly reset.
- Fixed: MESDC console may generate exception when running SusRAM parser it for
         first time after the ME was programmed to the flash.
- Fixed: Sometimes during power flows (and for some specific PSUs), the PSU
         monitoring service may improperly manage the internal resources,
         impacting the IPMI communication on SMLink0. As a result, ME stops
         responding to IPMI commands on SMLink0.
- Fixed: After Sx transaction ME losses synchronization with the Real-time
         Clock. Due to this issue all policies with defined Suspend Period
         would be disabled within a few minutes after platform start.
- Fixed: Unexpected ME reset could appear during NM communication with some
         specific PSU, as a result of which the CPU throttling statistics could
         be violated.
- Added: This release contains fixes in the ME recovery boot loader section.
- Added: Support for PCH thermal reading over SMLink1 has been added.

[END OF RELEASE NOTES]
