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

INTEL Enterprise Products and Services Division
Intel Corporation
2111 N.E. 25th Avenue, Hillsboro, OR 97124 USA

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

DATE    : Apr 10, 2013
TO      : Intel(R) Xeon(R) Processor-Based Server Platform customers
SUBJECT : Manageability Engine Release notes for version SPS_03.00.04.162

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

================================================================================
                              ABOUT THIS RELEASE
================================================================================
Build Stamp : ME Firmware             --> 03.00.04.164
              ME Recovery Boot Loader --> 03.00.04.164
Build Date  : Apr 10, 2013

================================================================================
                           Supported Platforms
================================================================================
	S1200RP LC/SE/RM/RO
                
================================================================================
                        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 Error manager displays 83A0 error code
   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 Error Manager does not display 83A0 error code

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
   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 MEComplete_xx_xx_xx_xxx.cap file when the 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.04.164 release
================================================================================   
When the ME put into Recovery mode using the Recovery jumper and host performs transition from Sx to S0 additional unexpected global platform reset appeared.
Power Statistics after platform shutdown by policy are not valid 
Factory Presets and AIM, OCS and OCP MFS files are not readable using MESDC or Diagnostic Service.
"Enable/Disable Intel(R) Node Manager Policy Control" IPMI command does not stop limiting power (NM S0only SKU with OEM thermal reading and SUSE*11x64 ) 
When ME operating in Recovery mode it may stop responding after Unconditional Power Down.
Unexpected ME reset happens after repeated platform power state changes. 
NM memory power capping occasionally fails outside 2.5% range.
Superfluous CPU/MEM power requests on PECI during Sx state.
The "Force ME Recovery" IPMI command may not always work. 
The OS ACPI P-State may differ by 2 from what was set by Node Manager. 
After creating policy the min. value in statistics gathered per-policy-Id is always 0 W. 
NM does not limit power if cores are disabled from BIOS setup 
The loss of all power readings in domain: 0, 1 or 2 is signaled with only one NM Health Event. 
"Firmware Update In Progress" bit does not set in FW Status register during online update. 

================================================================================
			Issues fixed in 03.00.04.164 release
================================================================================
Sometimes Dynamic Core Allocation temporarily parks cores in unexpected cases. 
Sometimes aggressive power policy in Domain Total is not able to limit power in specified correction time.
MESDC "ME-BIOS communication" flow test fail even when "BIOS ICC Set Clock Enable message" test is unchecked. 
Several lines are doubled in LPTAB_NM.XML 
Some MESDC SUSRam entry displayed as "Entry Format is unknown". 

================================================================================
			Issues fixed in 03.00.04.162 release
================================================================================
System will shutdown when running Windows* reboot
After executing "power button override" flow platform enters Sx state and stops responding. ME configured for operating in S0-only. 
IPMI: Wrong value of "reading/state unavailable" bit for Get Sensor Reading Command - CPU Thermal Status Sensor.
ME FW became unresponsive when it put into Recovery mode and no CPU installed on the platform.
CPU is not being fused properly during first boot after SPI flashing when board and FW are configured for operating in S0-only mode. 
It is not possible to disable Hotham functionality using BIOS HECI message. 
Memory and CPU power statistics are always equal 0W. 
Shutdown action could be interrupted by cold reset when volatile policies are used. 
During limiting the power isn't kept in the range of 2.5%(power limit is changed every 2 sec)
Invalid statistic values with throttling policy in domain 0x00. 
MolleteBend-D: GetSensorReading returns not stable values as data field. 
PeciProxy component hangs after sending CPU PCIConfigRd/Wr command 16 times.
Dynamic Core Allocation stopped working after a few minutes 
If cable is removed from backup PSU, power readings are not zeroed. 
Memory throttling statistics are != 0 when NM does not limit power (just after fw burn).
Wrong throttling statistic calculation in mode 03 and 0x13. 
Impossible to create non aggressive police in memory domain. 
[NM Event] Lack of Operational Capabilities Change (ME Reset and Platform reset). 
No response for HMRFPO_GETSTATUS command after EOP in Operational Mode. 
FW health event data=0xA0040B during DC power cycling test. 
Continuous: After reset from DOS ME goes to M3, HOST goes to Sx. 
Events from Node Manager Operational Capabilities Change Sensor are generated when disabled. 
Settings provided by IPMI command "Set Max Allowed CPU P-state/T-state" are ignored after S0->Sx->S0 transition. 
De-assertion instead of assertion event is generated for Total domain, when power or temperature readings are lost. 
"Host Communication Error" is being sent only when the host OS returns to operating state.
ME FW sends too many health events when "factory presets" partition is corrupted. Only one event should be sent. 
The access for PIA_SDR data flash area is not restored after defined flash wear out protection period. This access is locked permanently. 

================================================================================
			Issues fixed in 03.00.03.082 release
================================================================================
The system may not boot when it gets shutdown by "power button override"
The recovery mode (RCV) jumper does not function correctly. When the platform boots with RCV on and its gets switched off, the Host does to Sx power state. 
BIOS: Console redirection to RS-232 doesn't work 
ME does not send command "ME changed power state" after receiving "Host Reset With Power Cycle" or while restarting from OS. 

================================================================================
			Issues fixed in 03.00.03.078 release
================================================================================
The table below lists the issues detected in the former Alpha 2 Hotfix 1 release that have been fixed in this Beta release of SPS firmware. 
When MFS is corrupted, ME hangs for more than 60s and doesn’t send the appropriate health event 
FW does not wake up in operational mode when recovery image is corrupted. 
ME not operational after cold reset when VSCC table is empty. 
"OEM ME Power State Change" IPMI frame will be sent twice during Host Transition from Sx to S0 with the "Flash Override Security Strap" jumper asserted. 
Some times (randomly, after several dozen continuously performed power cycles), after power button override or host reset with power cycle ME stops responding to IPMI commands. Still responses to diagnostic commands. 
Some times when PSU optimization functionality is enabled power under load may not reach it maximum value after Node Manager stops power capping. 
Unstable power limiting when OEM Power readings are used for delivering platform power consumption information. 
Wrong ME FW Status register value when Security strap override jumper asserted. Operating Mode field is not set to 4 "RECOVER_JMPR - Security Strap Override asserted, ME works in recovery mode".
Depends on PSU SKU sometimes during P-state switching power limiting mechanism stops working. 
Time After Host Reset Policy triggers later than expected. 
Hotham getSignalsBlockState command makes ME FW unresponsive. 
Hotham getCrystalsCheckStatus command reports test status as failed in case host has transited from G3 to any other state. 
The HSC input voltage has a resolution of 1 volt. It should be 0.1 volt. 
Missing Readings Policy triggers earlier than expected. 
"NM enabled" bit in Node Manager Firmware Status (NMFS) in HECI-2 HFS Register is never been set properly due to fact that Node Manager using invalid AUX registers for PTState estimation.

================================================================================
			Issues fixed in 03.00.02.203 release
================================================================================
[OS Install] All OS Installation tests with RSTe mode are blocked
Sensor SSB Temp always in upper critical state
Sensor P1 MTT state display incorrectly in EWS
Failed to read some ME sensors with command "Get sensor reading"
RSTe OPROM cannot enabled with R006 on Fab 103 board.
Clock Run Enable for FLEXn option is not accessible. 
Lack of "DMI Clock Divider"and "DMI Spread Generator Enable" options. 
Some fields in PCH Straps section should set differently for lpt platform. 