=============================================================================
Intel(R) Server Board S3200SH/X38ML BIOS RELEASE NOTES
=============================================================================
Intel Enterprise Platform & Services Marketing
Intel Corporation
2111 N.E. 25th Avenue, Hillsboro, OR 97124 USA
=============================================================================
DATE:     Nov  29, 2010
TO:       Intel(R) Server Board S3200SH/X38ML Customers
SUBJECT:  BIOS Release Notes Ver. R0052
=============================================================================
                           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) 2010 Intel Corporation.

=============================================================================
                              ABOUT THIS RELEASE
=============================================================================


Build Stamp : S3200X38.86B.00.00.0052
Build Date :  Nov  29, 2010

=============================================================================
                           BIOS COMPONENTS/CONTENTS
=============================================================================
Processor supported: 
Quad-Core Intel(R) Xeon(R) Processor 3300 Series
Quad-Core Intel(R) Xeon(R) Processor 3200 Series
Dual-Core Intel(R) Xeon(R) Processor 3100 series
Dual-Core Intel(R) Xeon(R) Processor 3000 Series
Intel Pentium(R) Dual-Core processors
Intel(R) Core(R) 2 Quad Desktop processors
Intel(R) Core(R) 2 Extreme processors
Intel(R) Core(R) 2 Duo Desktop processors
Intel(R) Celeron(R) Processor 400 Sequence

Microcode update versions:
CPUID   Microcode   
06F2h       5Dh
06F6h       D0h
06F7h       6Ah
06FBh	    B6h
06FDh	    A3h
10661h      38h
10676h      60Fh
10677h      70Ah                                                
1067Ah      A0Bh                

Intel (R) Matrix Storage Manager option ROM -v7.5.0.1017 
Serial ATA AHCI BIOS: Release Date 01-05-2007
NIC 82541, 82566, 82575: Intel (R) Boot Agent GE v1.2.60
VGA: VBE BIOS V3.8SL
LSI OpRom, version 10101641
Memory Reference Code 1.00

BIOS image checksum: 0x34D1F58D for the R0052_MT.rom file (Melstone)

=============================================================================
                       SYSTEM FIRMWARE REQUIREMENTS/REVISIONS
=============================================================================

N/A

=============================================================================
                           INSTALLATION NOTES
=============================================================================

IMPORTANT NOTES:
  Before Alpha exit, BIOS flash update would also update the NVRAM section, which
  means all BIOS configurations would be restored to default after BIOS is updated. 
  The purpose is to avoid system unbootable after BIOS update. If the BIOS setup map
  is changed from BIOS to BIOS, this is very likely to happen. After Alpha exit, 
  BIOS setup map would be locked down and the NVRAM section would no longer be updated
  by flash update process.   
   
UPDATE INSTRUCTIONS:
   
A. If you want to update BIOS from R0019 or earlier version to version R0020 or later version R00XX, 
you need to flash BIOS twice as below:

   1. Boot to EFI shell and update capsule file R0020_2M.cap by iFlash32  
   : iFlash32 /u /ni R0020_2M.cap

   2.Then update the capsule file R00XX.cap
   : iFlash32 /u /ni R00XX.cap

B. If you want to update BIOS from R0020 or later version to any version R00XX or
you just need to flash BIOS once as below:

- Boot to EFI shell and update capsule file R00XX.cap by iFlash32

C.it needs iFlash32.efi Ver 2.0 Build 4 or newer version.

=============================================================================
                        BIOS RECOVERY INSTRUCTIONS
=============================================================================
Recovery process can be initiated by setting the recovery jumper (called force recovery)

A BIOS recovery can be accomplished from SATA CD and USB Mass Storage device. 
Please note that recovery from USB floppy is not supported on this platform. 

SATA CD image for recovery is created using El-Torito format image (which is bootable).

The recovery media must contain the image file: FV_MAIN.FV, under the root directory. 
And also the following files: 
1.	IFLASH32.EFI
2.	*.CAP
3.	Startup.nsh

The BIOS starts the recovery process by first loading and booting to the recovery image 
file (FV_MAIN.FV) on the root directory of the recovery media (SATA CD or USB disk). T
his process takes place before any video or console is available. Once the system boots 
to this recovery image file (FV_MAIN.FV), it would boot automatically into EFI Shell and 
invoke the Startup.nsh. and the flash update application (IFLASH32.EFI). 
IFLASH32.EFI requires the supporting BIOS Capsule image file (*.CAP). 
At last, there would have two short beeps indicating the completion of the recovery. 
User should switch the recovery jumper back to normal operation and restart the system 
by doing power cycle.


The following steps illustrate the recovery process:
1.  Power off the system,Insert recovery media.
2.  Switch the recovery jumper,The details of the jumper can be found in the Board EPS. 
3.  Power on the system.
4.  The BIOS POST screen will appear and display the progress, and system would automatically 
    boot to the EFI SHELL.
5.  Startup.NSH file would be automatically invoked. It will initiate the flash update (IFLASH32.EFI) 
    with new capsule file (*.CAP). The message will be displayed if flash update succeeds. 
6.  Once the flash update is completed, two beeps would be heard. User should Power off the system, and revert
    the recovery jumper back to normal operation.
7.  Power on the system. ¡°DON¡¯T INTERRUPT THE POST PROCESS AT THE FIRST BOOT¡±.


=============================================================================
                            KNOWN ISSUES/WORKAROUNDS
=============================================================================

  
=============================================================================
                          VERIFIED PRIOR TO RELEASE
=============================================================================
Passed Basic Acceptance Test
  - Boot to EFI shell
  - Boot to DOS
  - Install, Boot, Reboot, Shutdown on Win2003 SP1.
  - Install, Boot, Reboot on RHEL5 EM64T
  - Flash update with iFlash32
  
=============================================================================
                FEATURES MODIFIED/ADDED/REMOVED IN THIS RELEASE
=============================================================================
1, Processor MicroCode update.

=============================================================================
                         FIXED ISSUES IN THIS RELEASE
=============================================================================


[END OF RELEASE NOTES]
