================================================================================
Intel(R) Server Platform S1200V3RP System Firmware Update Package for 
The embedded EFI Shell
================================================================================
Intel Enterprise Platform & Services Division - Marketing
Intel Corporation
2111 N.E. 25th Avenue, Hillsboro, OR 97124 USA
================================================================================
DATE    : Jun 20, 2013
TO      : Intel(R) Server Board S1200V3RP
SUBJECT : Release Notes for System Firmware Update Package 
================================================================================
                              ABOUT THIS RELEASE
================================================================================
BIOS   : R01.02.0004
ME     : R03.00.04.164
BMC    : 1.05.4775
FRUSDR : 1.04
================================================================================
                           Support Platforms and Dependency
================================================================================
This update package is for Intel(R) Server Board S1200V3RPS
 and

Intel(R) Server Platform S1200V3RP family Processors supported: 
  Intel(R) Xeon(R) Processor E3-1200 V3 series
  
Microcode update versions:
Intel(R) Xeon processor E3-1200V3 series A0 version: 0xffff0013 CPUID = 0x306C1
Intel(R) Xeon processor E3-1200V3 series B0 version: 0xffff0003 CPUID = 0x306C2
Intel(R) Xeon processor E3-1200V3 series C0 version: 0xffff0003 CPUID = 0x306C3

On-Board Component Option ROM Versions:
Integrated Matrox VGA               : VBE BIOS V3.8 SQ
PXE Option ROM                      : Intel(R) Boot Agent XE v1.4.10
iSCSI Option ROM                    : Intel(R) iSCSI Remote Boot version 2.7.137
SATA RAID Option ROM - RSTe         : 3.7
UEFI SATA RAID Option ROM - RSTe    : 3.7
ESRT II FOR SATA                    : A.11.11191606
Legacy Processor Video              : 2164 
UEFI Processor Video driver         : 5.2.1002 

Memory Reference Code Version       : 1.1.0.2
Management Engine Firmware Version  : 3.0.4.164

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

UEFI iFlash32 
   1.  Boot the system to EFI Shell
   2.  Copy IFlash32.efi and BIOS.CAP file to a USB Flash Drive
       ( Do not use the *Rec.CAP file as it will clear the NVRAM and should
         only be used for Recovery - See Recovery Instructions below )
   3.  Map the respective storage device in the 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 at the prompt
	   fs0:\> IFlash32 [File Name] /u /ni
   6. Either reboot the system and
      6a. Go into BIOS setup <F2>, reset defaults <F9> and save <f10> or
      6b. After the BIOS update and before rebooting, run: fS0:> Iflash32 -rd
   7.  Reboot system.

================================================================================
                        BIOS RECOVERY INSTRUCTIONS
================================================================================

The Recovery process can be initiated by setting the recovery jumper. (called 
BIOS Recovery Boot Jumper)
 
A BIOS recovery can be accomplished from the backup BIOS region or USB Mass Storage device. 
Please note that recovery from USB floppy is not supported on this platform. 
 
The recovery media must contain the following files under the root directory:
   1.  DNL.ROM (optional)
   2.  UEFI iFlash32 (including IFlash32.efi and ipmi.efi )
   3.  *Rec.CAP
   4.  Startup.nsh (update accordingly to use proper *Rec.CAP file)
 
BIOS starts the recovery process by first loading and booting to the recovery image from the 
backup BIOS region or file (DNL.ROM) on the root directory of the recovery media (USB disk).

This process takes place before any video or console is available. Once the system boots 
to recovery image, it will boot automatically into EFI Shell to invoke the Startup.nsh 
script and start the flash update application (IFlash32.efi). IFlash32.efi requires the 
supporting BIOS Capsule image file (*Rec.CAP). After the update is complete, there will 
be a message displayed stating that the "BIOS has been updated successfully" indicating 
the recovery process is finished. The User should then switch the recovery jumper back to
normal operation and restart the system by performing a power cycle.
 
The following steps demonstrate this recovery process:
   1.  Power OFF the system.
   2.  Insert recovery media.(Optional if the backup BIOS region works)
   3.  Switch the recovery jumper. Details regarding the jumper ID and location
       can be obtained from the Product Board TPS.
   4.  Power ON the system.
   5.  The BIOS POST screen will appear displaying the progress and system automatically 
       boots to the EFI SHELL.
   6.  Startup.nsh file executes, and initiates the flash update (IFlash32.efi)
       with new capsule file (*Rec.CAP). The regular IFlash message will be displayed at
       the end of the process, once the flash update succeeds.
   7.  Power OFF the system, and revert the recovery jumper position to "normal".
   8.  Power ON the system. 
   9.  Do *NOT* interrupt the BIOS POST during the first boot.

================================================================================
                            KNOWN ISSUES/WORKAROUNDS
================================================================================
- BIOS R01.00.0017 cannot be used to update beta boards from earlier BIOS revisions. 
- If you want to install Linux* SUSE* 11 SP2 or boot to a pre-installed Linux* SUSE* 11 
  SP2 OS, USB 3.0 support will need to be disabled in BIOS setup -> USB Configuration tab.

================================================================================
                                R01.02.0004
================================================================================
- Fixed: Signed driver check test fails due to an unknown device found in Windows 2012 WHQL
         (Windows Hardware Quality Labs) certification.

================================================================================
                                R01.02.0002
================================================================================
- Fixed: Memory DIMM will sometimes starts throttling, even in good thermal conditions.
- Fixed: System can't wake up from S3 via power button/USB device/Lan.
- Fixed: System power consumption cannot be limited by Node Manager.
- Fixed: BIOS version is not be updated accordingly in server management remote console.

Others:
 - Updated RSTe UEFI/Legacy OPROM to 3.7
 
================================================================================
                                R01.01.0006
================================================================================
- First production BIOS release.

================================================================================
			  ME Changes in Release 03.00.04.162
================================================================================   
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. 
Dynamic Core Allocation: SetTotalPowerBudger does not park cores. 
Disable NM IPMI command does not stop limiting power (NM S0only SKU with OEM thermal reading and SUSE*11x64 ) 
ME is not responding after Unconditional Power Down. 
Unexpected ME reset happens after repeated power state changes. 
Several lines are doubled in LPTAB_NM.XML 
NM memory power capping occasionally fails outside 2.5% range. 
Superfluous CPU/MEM power requests on PECI during Sx state. 
The ME Recovery IPMI command many not always work. 
The OS ACPI PState may differ by 2 from what was set by Node Manager. 
Missing reading police is not triggered in the CPU domain. 
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. 
MESDC: SUSRAM - Entry Format is unknown 
No "Firmware Update In Progress" bit set in FW Status register during online update. 

===============================================================================
                               BMC Changes in 01.05.4775
===============================================================================
-Fixed: Change Intel(R)RMM in EWS into RMM Dedicated Mgmt.
-Fixed: The LCD Screen display is not clear while scrolling error events.
-Fixed: LAN leash lost event is shown during DC cycle testing.
-Fixed: Px DIMM Thrm Mrgn and Px DIMM Thrm Trip not decoding DIMM number
        correctly in the Embedded Web Server SEL text log.
-Fixed: Embedded Web Server SEL text log not decoding BIOS update versions
        correctly.
-Fixed: There are assert events for Mem Err Sensor 0x28 - 'DIMM Thrm Mrgn 1'
        sensor and 'SPS FW Health' sensor after updating ME firmware.


===============================================================================
                                BMC Changes in 01.04.4674
===============================================================================
-Fixed: Update SDR to version 1.04.
-Fixed: The BMC version information not displaying as expected in Embedded Web
        Server after entering firmware transfer mode..
-Fixed: The host power status show inconsistently betweeen system information
        page and server power control page in Embedded Web Server when system
        is in S1 or S3.
-Fixed: There are assert and deassert events logged for PCH temp sensor 0x22 -
        low critical and low non-critical during DC cycle stress test.
-Fixed: System status LED is incorrect and there is no assert event logged for
        DIMM thermal trip after DIMM thermal trip is triggered.
-Fixed: Multiple KVM socket error and media redirection errors.
-Fixed: Integrated BMC Web Console Keyboard Macro Cltrl+Alt+F1 not working as expected.

===============================================================================
                                BMC Changes in 01.03.4595
===============================================================================
-Fixed: Update SDR to version 1.03.
-Fixed: RGMII signal integrity test failed on S1200RP.
-Fixed: BMC shared NIC cannot be pinged successfully after BMC shared NIC IP
        address is set in BIOS setup.
-Fixed: The Web Console Event Log page uses IBMC.

===============================================================================
                                BMC Changes in 01.02.4452
===============================================================================
-Fixed: Update SDR to version 1.02.
-Fixed: DIMM margin resolution isn't right when saving DIMM inventory into
        extend SEL.
-Fixed: There are four BIOS recovery boot entries in the SEL for a recovery
        boot,only two are expected.
-Fixed: When recovery jumper is connected to 1-2 pin(normal mode), system
        always boots from recovery mode after programming a new BIOS offline.
-Fixed: BMC shared NIC cannot be pinged successfully after run VLAN id set/get
        stress test from VLAN id 0 to 4094.
-Fixed: Source of DIMM event does not show in the SEL extended data.

===============================================================================
                                BMC Changes in 01.01.4412
===============================================================================
-Fixed: Update SDR to version 1.01.

-Fixed: Change resolution of DIMM temp sensor reading.
-Fixed: SUT is reset even when the timer action is "none" after getting a
        Watchdog timeout.
-Fixed: Sensor reading/state for DIMM Thermal Margin 1 is unavailable.
-Fixed: Fail to generate system debug log in Embedded Web Server.
        - Refreshing the page shows the debug log is available
-Fixed: Embedded Web Server Power Policy numbers cannot be set to 255. Per the
        help information 255 should be valid.
-Fixed: There are unnecessary event logged for sensor Voltage BB +5.0V STBY
        (#0xD3) lower non-critical during AC cycle test.
-Fixed: Message shows as "undefined" with ff in Embedded Web Server SEL page
        when SEL is full.
-Fixed: Intel(R) Hybrid Cloud cannot get session ID when use BMC
        username/password with special characters.

================================================================================
				BMC Changes in Release 00.14.4348
================================================================================
01.00.4348:
- Count of currently enabled users still is changed even failed to enable users without 
 name setting with command "set user access".
- Wrong completion code returned by issuing "Get DIMM information" IPMI OEM command.
- Failed to check the timer Interrupt-Action Interaction when settting pre-interrupt as NMI.
- Lan configuration information and User configuration information change to default value

 after updating BMC FW ver:00.19.4290.
===============================================================================
                          BMC Changes in Release R0014
===============================================================================
- Initial Version

=============================================================================
                           FRUSDR Changes in release 1.04
=============================================================================
 - Fixed the issue of System status LED show green blinking when unplug the front panel

===============================================================================
			  FRUSDR Changes in release 1.03
===============================================================================
- Initial version

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

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

[END OF RELEASE NOTES]
