Intel S1200V3RPL Server Board UEFI Firmware 03.03.0003 Download

Posted at April 19, 2024 by PCI-DB Team

Intel S1200V3RPL Server Board UEFI Firmware 03.03.0003 Description

Versions:

- BIOS: 03.03.0003
- ME: 03.00.07.024
- BMC: 01.14.9309
- FRUSDR: 1.08

BIOS Changes in 03.03.0003:

- NOTICE: Capsule update method: If previous BIOS version is R02.02.0004 and earlier version, need use E3-1200 V3 CPU part boot to EFI shell, and use capsule files update BIOS to R03.03.0003 and update ME to 3.0.7.24,then replace with E3-1200 V4 CPU part to power on.
- EPSD100251166: System will auto reset when run Trusted Boot- measured launch(TBOOT) test
- ESS RC V119_03 integration
- [Security] Implemented BIOS lock before PCI bus emulation
- EPSD100249332: [RBP-RM] Virtual Machine can't POST with E3-1200 V4 CPU after you install RemoteFX 3D video adapter
- EPSD100250117: BIOS update script does not check BIOS update failure, cause ME updated to latest version and does not match with on board old BIOS(startup Stript updated)
- EPSD100250117: [RBP] 4k monitor issue with E3-1200 CPU (Win2k12R2)

ME Changes in 03.00.07.024:

- Fixed: Platform does not go to S3/S4 state in recovery mode
- Fixed: Wrong value returned from Get Max Allowed Logical Processors command after S0->(S4,S3)->S0 transition

BMC Changes i 01.14.9309:

- Fixed: The BMC Lan IP cannot ping successful with new S1200RP MB.
- Update openssl from 0.9.8zf to 0.9.8zg to add fix for CVE-2015-1789.
- Fixed: Firefox version 38.0 or higher breaks with system with RMM4 and RMM3.

FRUSDR Changes in release 1.08:

- Fixed: The sensor reading of P1 MTT is always 0 in EWS(Intel Integrated BMC Web Console)

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:
- Boot the system to EFI Shell
- Copy IFlash32.efi, ipmi.efi and BIOS.CAP file to a USB Flash Drive ( Do not use the Rec.CAP file as it will clear the NVRAM)
- It is recommended to copy full package
- Map the respective storage device in the system with the command Shell> map -r
- Change the Shell to mapped device file system. Example: Shell> fs0: (or fs1:)
- Run the IFlash32 utility at the prompt fs0:\> IFlash32 [File Name] /u /ni
- Either reboot the system and Go into BIOS setup <F2>, reset defaults <F9> and save <F10> or After the BIOS update and before rebooting, run: fS0:> Iflash32 -rd
- Reboot the system

Backup BIOS update instructions:
- Boot the system to EFI Shell
- Copy IFlash32.efi, ipmi.efi and BIOS .CAP file to a USB Flash Drive ( Do not use the Rec.CAP file as it will clear NVRAM)
- It is recommended to copy full package
- Map the respective storage device in system with the command Shell> map -r
- Change the Shell to mapped device file system. Example: Shell> fs0: (or fs1:)
- Run the IFlash32 utility on the prompt fs0:\> IFlash32 -u [File Name] UpdateBackupBios -ni
- It will update primary BIOS with processed capsule, and the backup BIOS update will be completed in next normal boot.
- Reboot the system.

IMPORTANT NOTICE:

- Need use recovery capsule file to downgrade/upgrade between R02.00.0x32 and before version BIOS (Including R01.04.0002 and before).
- R02.01.0002 and later version need use command "iflash32 -u RB_R02.0x.xxxxRec.cap UpdateBackupBios -ni" to upgrade from R01.04.0002 and early version. Similarly, R01.04.0002 and early version need use command "iflash32 -u RB_R01.0x.xxxxRec.cap UpdateBackupBios -ni" to downgrade from R02.01.0002 and later version.
- As security requirement, R03.01.0001 reversion and later version doesn't support capsule downgrade to R03.00.0x43 and previous reversion(Including R02.02.0005 and before) in normal mode.
- As security requirement, R03.03.0003 reversion and later version doesn't support capsule downgrade to R03.02.0004 and previous reversion(Including R02.02.0005 and before) in normal mode.
- Added a cold reset to ensure boot completion after Backup BIOS update trigged.

About ME Firmware:

If you wish to apply this ME (Management Engine) Firmware version, you should first make sure that the version number matches your AMT (Active Management Technology) family, as each update is specifically developed for certain system configurations.

While this technology is mostly associated with enterprises, it can also be used by various IT administrators as well as regular users. However, bear in mind that even though other platforms might also be compatible, we do not recommend installing this release on OSes other than the specified ones.

In order to apply this package, it would be best if you carefully read and understand the instructions provided by your computer manufacturer, and perform the update only when you have completely familiarized yourself with the steps.

In addition to that, make sure you perform a system reboot after upgrading the firmware version in order to allow all changes to take effect properly.

About OS Independent BIOS:

Although installing a newer BIOS version might add new features, update various components, or improve the device’s usability, this process is very risky, so the upgrade is recommended to be performed only when it is really needed.

In addition to that, this task should be performed by someone who has the knowledge to successfully complete the installation; regular users may fulfill it at their own risk.

When it comes to applying a new version without taking into account the computer’s operating system, the most commonly used method to flash the BIOS is by creating a bootable USB or CD containing the update file, and running it from DOS.

Still, regardless of the method used or whether the upgrade is performed by a regular or power user, it’s recommended that the new BIOS be applied in a steady power environment such as the one ensured by a UPS unit.

The Basic Input/Output System (BIOS) is a very important software that loads the currently installed OS, and tests all of the system’s hardware components – so make sure you flash it correctly.

Bear in mind that failing to perform a successful installation could seriously damage your device, and the faulty BIOS resulted from the process might even render it unusable.

About Firmware Updates:

Applying a newer firmware version than the one already installed on your unit can bring various enhancements, include workarounds for diverse problems encountered by the device, and improve or add newly developed features.

On the other hand, downgrading the firmware version can recover the device’s functionality in the event of a software update either turning up faulty or causing the unit’s overall performance to drop. However, bear in mind that applying an older firmware isn’t recommended and might not always be possible.

When it comes to the update steps, due to the large variety of devices and numerous ways for installing a new firmware, it is recommended that you carefully read and understand the upgrade steps, and consider applying a different firmware only when you have familiarized yourself with the update method.

As the installation process is most of the times quite risky, this step should be taken by users that have the ability to successfully complete the update; regular users may initiate it at their own risk. Moreover, it’s best that this task be performed in a steady power environment such as the one ensured by a UPS unit.

Therefore, if you consider applying this release, hit the download button, take into account all the aforementioned aspects, and update the device’s firmware. Also make sure you constantly check with our website to ensure that you don’t miss a single new release. 

  It is highly recommended to always use the most recent driver version available.

Try to set a system restore point before installing a device driver. This will help if you installed an incorrect or mismatched driver. Problems can arise when your hardware device is too old or not supported any longer.

Related Intel Drivers