5MB FW Release Notes 10 0 26 1000 (HF) (1)


Чтобы посмотреть этот PDF файл с форматированием и разметкой, скачайте его и откройте на своем компьютере.








Intel Management Engine
Firmware 10 for Broadwell PCH
-
LP

5MB Readme / Release Notes
-

NDA


July

201
4


Revision
10.0.2
6
.
1000

Hot Fix

(
HF
)

Release





Intel Confidential

















2


Intel Confidential





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 SAL
E 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, O
R
INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT.


A "Mission Critical Application" is any application in which failure of the Intel Product could result, directly or indirectl
y, in
personal injury or death. SHOULD YOU PURCHASE

OR USE INTEL'S PRODUCTS FOR ANY SUCH MISSION CRITICAL APPLICATION,
YOU SHALL INDEMNIFY AND HOLD INTEL AND ITS SUBSIDIARIES, SUBCONTRACTORS AND AFFILIATES, AND THE DIRECTORS,
OFFICERS, AND EMPLOYEES OF EACH, HARMLESS AGAINST ALL CLAIMS COSTS, DAMAGES, AND
EXPENSES AND REASONABLE
ATTORNEYS' FEES ARISING OUT OF, DIRECTLY OR INDIRECTLY, ANY CLAIM OF PRODUCT LIABILITY, PERSONAL INJURY, OR
DEATH ARISING IN ANY WAY OUT OF SUCH MISSION CRITICAL APPLICATION, WHETHER OR NOT INTEL OR ITS
SUBCONTRACTOR WAS NEGLIGENT I
N THE DESIGN, MANUFACTURE, OR WARNING OF THE INTEL PRODUCT OR ANY OF ITS
PARTS.


Intel may make changes to specifications and product descriptions at any time, without notice. Designers must not rely on the

absence or characteristics of any features or in
structions marked "reserved" or "undefined". Intel reserves these for future
definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them
. The
information here is subject to change without no
tice. Do not finalize a design with this information.


The products described in this document may contain design defects or errors known as errata which may cause the product to
deviate from published specifications. Current characterized errata are avai
lable on request.


Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing your product

order.


Copies of documents which have an order number and are referenced in this document, or other Intel li
terature, may be obtained
by calling 1
-
800
-
548
-
4725, or go to:
http://www.intel.com/design/literature.htm%20

All products, platforms, dates, and figures specified are preliminary
based on current expectations, and are subject to change
without notice. All dates specified are target dates, are provided for planning purposes only and are subject to change.

This document contains information on products in the design phase of developm
ent. Do not finalize a design with this
information. Revised information will be published when the product is available. Verify with your local sales office that yo
u have
the latest datasheet before finalizing a design.

Intel


Active Management Technology

r
equires activation and a system with a corporate network connection, an Intel AMT
-
enabled chipset, network hardware and software. For notebooks, Intel AMT may be unavailable or limited over a host OS
-
based
VPN, when connecting wirelessly, on battery pow
er, sleeping, hibernating or powered off. Results dependent upon hardware,
setup and configuration. For more information, visit
Intel Active Management Technology
.

Client Initiated Remote Access may not be available in public hot spots or "click to accept" locations. For more information
on
CIRA, visit
Fast Call for Help Overview

No computer system can provide absolute security. Intel Identity Protection Technology requires an Intel Identity Protectio
n
Technology
-
enabled system, including an enabled Intel processor,

enabled c
hipset, firmware, software, and Intel integrated
graphics (in some cases) and participating website/service. Intel assumes no liability for lost or stolen data and/or systems

or
any resulting damages. For more information, visit
http://ipt.intel.com/
.


Consult your system manufacturer and/or software
vendor for more information.

KVM Remote Control (Keyboard, Video, Mouse) is only available with Intel® Core™ i5 vPro™ and Core™ i7 vPro™ processors
with Intel
Active Management technology activated and configured and with integrated graphics active. Discrete graphics are
not supported.

No computer system can provide absolute security.
Intel Platform/Device Protection Technology r
equires an enabled
Intel

proces
sor, enabled chipset, firmware, software and may require a subscription with a capable service provider (may not
be available in all countries).


Intel assumes no liability for lost or stolen data and/or systems or any other damages resulting
thereof.


Con
sult your Service Provider for availability and functionality.


For more information, visit
http://www.intel.com/go/anti
-
theft

.


Consult your system manufacturer and/or software vendor for more informatio
n.


Intel® vPro™ Technology is sophisticated and requires setup and activation. Availability of features and results will depend
upon
the setup and configuration of your hardware, software and IT environment. To learn more visit:
http://www.intel.com/technology/vpro
.

Code

names featured are used internally within Intel to identify products that are in development and not yet publicly announced
for release. Customers, licensees and other third

parties are not authorized by Intel to use code names in advertising, promotion
or marketing of any product or services and any such use of Intel’s internal code names is at the sole risk of the user.

*Other names and brands may be claimed as the property

of others.

Copyright
2013
-
2014
, Intel Corporation. All rights reserved.






Intel Confidential

3

Contents

1

Introduction

................................
................................
................................
......

5

1.1

Scope of Document

................................
................................
.................

5

1.2

Acronyms

................................
................................
..............................

5

2

Release Kit Summary

................................
................................
.........................

7

2.1

Release Kit Details

................................
................................
..................

7

2.2

Kit Overview

................................
................................
..........................

7

2.3

Contents

of Downloaded Kit

................................
................................
.....

8

2.3.1

Intel


SW Components

................................
...............................

8

2.3.2

Image Components

................................
................................
....

8

2.3.3

System Tools

................................
................................
...........

11

2.3.4

Intel


ICCS Tools

................................
................................
.....

13

2.4

Release Version Numbering Information

................................
...................

14

2.5

Firmware Update Information

................................
................................
..

14

2.5.1

Firmware Update Terminology

................................
....................

14

2.5.2

VCN Firmware Upgrade / Downgrade Table

................................
..

15

3

Important Notes

................................
................................
...............................

16

3.1

Hardware Configurations

................................
................................
.........

16

3.2

Important Notes

................................
................................
....................

17

3.3

Best Known Configuration

................................
................................
.......

17

4

Kit Details

................................
................................
................................
........

18

4.1

Build Details

................................
................................
..........................

18

4.2

FITC XML Compare

................................
................................
................

19

5

Intel


ME New Features

................................
................................
.....................

20

5.1

RCR Update

................................
................................
..........................

20

6

Issue Status Definitions

................................
................................
.....................

29

7

Closed Issues

................................
................................
................................
...

30

7.1

Closed


Intel


AMT

................................
................................
...............

30

7.2

Closed


Intel


ME Kernel

................................
................................
.......

34

7.3

Closed


Intel


Device Protection Technology with Boot Guard / Intel


PTT

...

36

7.4

Closed


Software / Tools

................................
................................
.......

37

7.5

Closed


No Plan to Fix

................................
................................
...........

43

7.6

Closed


Not a Firmware or Software Bug

................................
.................

43

7.7

Closed


No Plan to Fix

................................
................................
...........

45

7.8

Closed


External Dependency

................................
................................
.

45

7.9

Closed


Documentation

................................
................................
.........

46

8

Known Issues

................................
................................
................................
...

47

8.1

Open


Int
el


AMT

................................
................................
.................

47

8.2

Open


Intel


ME Kernel

................................
................................
.........

48

8.3

Open


Software / Tools

................................
................................
.........

48






4


Intel Confidential


Revi
sion H
istory


Revision
Number

Description

Revision Date

10.0.0.1012

Alpha

Release

Y Series

November

201
3

10.0.0.1042

Alpha Release

U Series

December 2013

10.0.20.1156

(U and Y Series)

March 2014

10.0.25.1030

Production
Candidate

June 2014

10.0.25.1048

Production Version

June 2014

10.0.26.1000

Hot Fix Release

July 2014






Introduction




Intel Confidential

5

1

Introduction

1.1

Scope of Document

This document provides component level details of the
downloaded kit and the
contents of each folder in the kit.

1.2

Acronyms

Term

Description

BIOS

Basic Input Output System

Boot Guard

Intel


Device Protection Technology with Boot Guard

(formerly
known as Anchor Cove)

BLU
-
RAY PLAYBACK

B
lu
-
r
ay


Playback

CCM

Client Control Mode (See: HPC)

CIM

Common Information Model

CRB

Intel


Customer Reference Board

FITC

Flash Image Tool

FOV



FW

Firmware

GbE


HBC

Host Based Configuration

HECI

Host Embedded Controller Interface.
Same as Intel


ME
I.

Intel


AMT

Intel


Active Management Technology

Intel


AT

Intel


Anti
-
Theft Technology

Intel


CIRA

Intel


Client Initiated Remote Access

Intel


DAL

Intel


Dynamic Application Loader (Intel


DAL)

Intel


ICCS

Intel


Integrated Clock Controller Service

Intel


IPT

Intel


Identity Protection Technology


Introduction



6


Intel Confidential


Term

Description

Intel


MEB
X

Intel


Management Engine BIOS Extension

Intel

ME
I

Intel

Management Engine and the Host system)

Intel


NFC

Intel


PROSet/Wireless Near Field Communications Software

Intel


PDA

Intel


Platform Debug Analyzer (platform debug tool formerly
referred to as MDES or
Intel


ME
Debug)

Intel


PETS

Intel


Platform Enablement Test Suite

Intel


PTT

Intel


Platform Trust Technology

Intel


SVT

Intel Silicon View Technology

KVM

Keyboard/Video/Mouse

ISV

Independent Software Vendor

LAN



LMS

Local Manageability Service

MAC

Media Access Control

MOF

Managed Object Format

MRC

Memory
Reference Code


OS

Operating System

PCH

Platform Control Hub

PKI
-
CH

Public Key Infrastructure with Certificate Hashing


RCFG

Remote configuration

SOL

Serial over LAN

Intel


SB
T

Intel


Small Business Technology

SPI

Serial Peripheral Interface


SUT

System Under Test

SVN

Security Version Number. Used in Firmware Upgrade /
Downgrade capabilities

TDT

-
p, which is
part of the Intel


Anti
-
Theft Technology.

UNS

User Notification Service

VCN

Version Control Number. Used in Firmware Upgrade /
Downgrade capabilities

WMI


Windows*

Management Instrumentation

WSI

Web Services Interoperability Organization


Release Kit Summary




Intel Confidential

7

2

Release Kit Summary

This document covers the following Intel


Management Engine Firmware SKUs for the

Broadwell Mobile

U/Y Series

platform:



Intel


Management Engine Firmware
Broadwell Mobile U/Y Series Platform
.

o

Digital Office Intel


vPro™


Kit release information is outlined below:

2.1


* Firmware

Support

:

Intel


Active Management Technology
,
PAVP,

Intel


ICCS,

Intel


IPT
, Intel


NFC
,
Intel


Platform

Protection
Technology with Boot Guard (Anchor

Cove
)
, Intel


SVT

* Release

:

Broadwell Mobile U/Y Series Platform

HF

Release



10.0.26.1000

*



:

Broadwell Mobile U/Y Series Platform
.

* .zip name

:

ME
10.0
_5M_
10.0.26.1000
.zip

Contents:



Intel

Management Engine
Firmware

for
Broadwell Mobile U/Y Series
Platform



GbE PCH SPI components



Intel Reference System BIOS



Intel


Management Engine BIOS Extension (
Intel


MEBX
) image

2.2

Kit Overview

The kit can be downloaded from VIP (
https://platformsw.intel.com/
)
.

Note:


A username and password are required to access the website and to log in. User must
have an account created for access.


1.

After logging in, click on the link ‘View All Kits’ on the left side of the web page.

2.

Click on the corresponding kit number that is to

be downloaded.

3.

Select and open the appropriate kit component
.


4.

The Supporting Documentation folder under the selected component contains the
following supporting documentation:

1.

5MB FW Release Notes


This document gives an overview of the contents of
the
entire downloaded component. Also provides the details on closed and
open Sightings and bugs with this kit release.


Release Kit Summary



8


Intel Confidential


2.

BIOS Release Notes


This document provides details of BIOS issues resolved
with the kit.

5.

Click on the Installation Files folder under the s
elected component and extract the
.zip kit into a folder (Example: C:
\
)
.


2.3

Contents of Downloaded Kit

Download the kit, as previously specified, into the directory (C:
\
). The details of the
contents and directory structure are listed below:

2.3.1

Intel


SW Components

Installers

Description

ME
_SW
_MSI



Intel


ME
I is the interface between the host and the Intel


Management Engine firmware.



Drivers and applications on the host that wish to interact with
Intel


Management Engine through the host interface use

the
Intel


ME
I host Windows* driver.



Intel


ME
I driver is installed by running:
C:
\
[skuName_x.x.xxxx]
\
Installers
\
ME
_SW
_MSI
\
Setup
ME.exe



To view the installer options, enter the following in a
Command window:
S
ME
.exe
-
?
and the help dialog
should
appear.




Additional information can be found in the
Intel(R)_ME_
10_
SW_Installation_Guide

document

within
this kit.

MEI
-
Only Installer MSI



The
ME
I
-
Only Installer only installs the
Intel


ME
I driver.

2.3.2

Image Components

NVM Images are included in:

o

ME
10.0
_5M_
10.0.26.1000
.zip


This folder contains the component images (BIOS image, Intel

Management Engine
image

and GbE image) that are integrated to form the final flash image. The table
below lists the different images and briefly describes them.


Release Kit Summary




Intel Confidential

9

Image

Descr
iption

BIOS



Contains Intel Reference System BIOS
.



Supported devices:
Broadwell Mobile U/Y Series Platform
.



After flashing a new BIOS, enter BIOS setup and ‘Load
Default Settings’ (Press F3). Then ‘Save and Exit’ (Press
F4) from Setup. This is a required
step when updating to
a new BIOS release.



BIOS image components are located in the following
directory:
C:
\
[skuName_x.x.xxxx]
\
Image
Component
s
\
BIOS
\



For latest release information and known issues on the
BIOS, please refer to the
Intel ME

BIOS Writer’s Guide
.

ME



The Intel

Management Engine firmware contains code
and configuration data for Intel

Management Engine
functions.



This is one of the regions that are integrated into the final
flash image that is built using the Flash Image Tool,

and is
then programmed into the flash.

NOTES:



For more details on building the flash image, please refer
to
5MB

FW Bringup Guide.pdf
, included in the
downloaded kit.



For more details on the firmware and related issues,
please refer to
Important Notes
sec
tion

of this
document.

GbE



The GbE hardware is a component embedded in the
MCP
.
GbE region of the flash contains bits that define the
configuration of the GbE hardware.



The given Gigabit Ethernet or GbE component image
should be integrated with the other
images (
Intel


ME

and
BIOS) using the Flash Image Tool, to create a single
binary flash image.



The GbE image will be programmed into the SPI flash as
part of this integrated image using the Flash Programming
Tool.



The GbE folder contains images for PHY

silicon.
Example:

NAHUM6_LP_CLARKVILLE_ULT_6.bin

(for LPT
-
LP only) and
NAHUM6_WPT_0_2.bin (for WPT only)
. Th
ese

image
s

can
be used with the Intel

Management Engine
.


Release Kit Summary



10


Intel Confidential


Image

Descr
iption

ME_BIOS_Extension



Intel

Management Engine BIOS Extension is used to
provision the syste
m with manageability options.



Intel

Reference System BIOS has Intel

Management
Engine extensions integrated. If using custom BIOS, then
please use the binary files in the following folder: "

C:
\
[skuName_x.x.xxxx]
\
Image Components
\
ME_BIOS_Extension
\
" and

merge with the BIOS.



For latest release information and known issues on the
Intel

Management Engine BIOS Extension, please refer to
the Intel

ME BIOS Writer’s Guide.


Release Kit Summary




Intel Confidential

11

2.3.3

System Tools

System Tools are
included in:

o

ME
10.0
_5M_
10.0.26.1000
.zip


This folder contains system tools that are common to all the firmware components.
Please refer to the
System Tools User Guide.pdf

document for details on tool
usage.

Tool

Description

Flash Image Tool


fitc.exe



Provides both a GUI and a command line tool
.



OS Support





Windows
*

XP SP3,
Windows
*

7 (32
-
bit & 64
-
bit),
Windows
*

8 (64
-
bit), Windows
*

Server 2003,
Windows*

Server 2008
R2
(32
-
bit & 64
-
bit).



Used to assemble the different elements of the SPI flash
Descriptor, Intel Reference System BIOS, Intel

Management Engine firmware, Gigabit Ethernet (GbE) into
a single binary image.

Flash Programming
Tool


fpt.exe and
fptw.exe



Provided as DOS
, EFI

and Windows* command line tools.



OS Support





MS DOS 6.22 and later, DRMK and FreeDOS.



U
EFI

64
-
bit.



The
Windows*

version (fptw.exe) will run in
Windows*

PE,
Windows*

XP SP3,
Windows*

7 (32
-
bit & 64
-
bit),
Windows*

8
R2
(64
-
bit), Server 2003, and 2008 R2 (32
-
bit & 64
-
bit).



Used to write the flash image into the SPI flash device.

FWUpdate


FWUpdLcl Tools



Provided as DOS
, EFI

and Windows* command line tools.



OS Support





MS DOS 6.22 and later, DRMK and FreeDOS.



U
EFI

64
-
bit.



Used to update the Intel

Management Engine's firmware.


Release Kit Summary



12


Intel Confidential


Tool

Description

ME
Info



Provided as DOS
, EFI

and Windows* command line tools.



OS Support





MS
-
DOS 6.22 and later, DRMK and FreeDOS.



U
EFI

64
-
bit.



Windows*

Command line executable for
Windows*

(Intel
MEInfoWin) is supported on
Windows*

PE,
Windows*

XP
SP3,
Windows*

7 (32
-
bit & 64
-
bit),
Windows*

8 (64
-
bit),
Server 2003, and 2008 R2 (32
-
bit &

64
-
bit).



Verifies that Intel

Management Engine (
Intel ME
)
firmware is alive and returns data about

Intel ME
.

ME
Manuf



Provided as DOS
, EFI

and Windows* command line tools.



OS Support




MS
-
DOS 6.
22 and later, DRMK and FreeDOS.



U
EFI

64
-
bit.



Windows*

PE,
Windows*

XP SP3,
Windows*

7 (32
-
bit & 64
-
bit),
Windows*

8 (64
-
bit), Server 2003, and 2008 R2 (32
-
bit
& 64
-
bit).




Used on the manufacturing line to vali
date platform is
configured properly.

UpdParam



Provided as a DOS command line tool.



OS Support




MS
-
DOS 6.22 and later, DRMK and FreeDOS,



UpdateParam tool is used to change certain
Intel


ME

Intel


AMT

and Kernel) after the



Release Kit Summary




Intel Confidential

13

2.3.4

Intel


ICC
S

Tools

Tool

Description

Clock
Commander
Tool (CCT)



ICC Tool
is used
to get
Intel

ICC
S

see
ICC Tools User Guide

for more information.



OS Support




MS
-
DOS 6.22 and later, DRMK and FreeDOS.



UEFI 64
-
bit.



Windows* 7 (32
-
bit & 64
-
bit) and Windows* 8 (64
-
bit).




Release Kit Summary



14


Intel Confidential


2.4

Release Version Numbering Information

Typical release version numbering is as follows,

10
.x.y.z


(for example:
10
.
0
.0.
zzzz
)

where
:


10


refers to
the Intel Management Engine
10
.
x

Firmware SKU for

the

Broadwell Mobile U/Y Series Platform
.

‘x’

represents point releases where new features
or changes to existing features
may be added
.

‘y’

refers to Maintenance and Hot Fix release designations
.


‘z’

refers to firmware release revision
.

2.5

Firmware Up
date

Information

Intel


ME

Firmware Update (either upgrade or downgrade)
is evaluated based on the
SVN value, the VCN value, or the PV values. These values work in unison and can
impose restrictions at the same time.

2.5.1

Firmware Update Terminology

SVN (Security Version Number):
will
be incremented if there is a high or critical
security fix in
Intel ME

Firmware. A downgrade to a lower SVN value will be
prohibited.


VCN (Version Control Number):

will be incremented if there is a security fix, a
significant firmware change or a new fe
ature addition. A downgrade to lower VCN
value will be prohibited.


PV (Production Version):
Intel ME

non
-
PV firmware is not allowed. An update from non
-
PV version to a PV is allowed.


Update rules:



If the
system is at PV (Production Version) quality firmware that has PV bit
-
PV firmware is not allowed. Only Non
-
PV to PV is allowed.

o

Example:
9
.
5
.0.
zzzz

PV cannot
upgrade

to
9
.
7
.0.
zzzz

Beta



Update to firmware that has lower SVN (Security Vers
ion Number) is not
allowed.



Update to firmware that has lower VCN (Version control number) is not
allowed.



Update across major point release is not allowed for example 8.x to 9.x.



Intel
ME
BX
is password protected,
Intel
ME
BX

password must be supplied during the update.



Release Kit Summary




Intel Confidential

15

2.5.2

VCN

Firmware Upgrade / Downgrade

Table


Intel


ME

FW
Version

SVN #

VCN #

PV (1 or 0)

10.0.26.1000

(HF U/Y Series)

1

2

1

10.0.25.1048

(PV U/Y Series
)

1

2

1

10.0.25.1030

(PC U/Y Series)

1

1

1

10.0.20.1156


1

0

0

10.0.0.1042

(Alpha U
-
Series)

1

0

0

10.0.0.1012

(Alpha

Y
-
Series
)

1

0

0


Important Notes



16


Intel Confidential


3

Important Notes

This
HF

Release

firmware supports 5MB
Corporate
SKU platforms.

o

Full Moff Power flows (PP1)


S
upported

o

Full M3 Power flows (PP2)


Supported

o

Intel


AMT Web UI


Supported

o

KVM


Supported

o

SOL / IDER


Supported

o

Deep Sx


Supported

o

BLU
-
RAY
*

PLAYBACK


Supported

o

WLAN


Supported

o

Intel


Insider™ Supported

o

Intel

DAL
-

Supported

o

Intel


NFC


Supported

o

Intel


SB
T



Supported

o

Intel


PTT


Supported

o

Intel


Boot Guard
-

Supported

o

Intel


Identity Protection Technology


Supported

3.1

Hardware Configurations

This release supports the following HW configurations:

-

MCP
:
BDW
(
QS
)




Important Notes




Intel Confidential

17

3.2

Important Notes



Firmware upgrade from a pre
-
PV version to Intel


ME Firmware 10.0.25.1048
PV version is not supported, and should not be attempted by customers.

All customers are asked to rebuild their image with the PV release and reflash
their platforms.

Updating to Intel


ME Firmware 10.0.25.1048 PV from a pre
-
PV

version will
prevent the platform from booting. Recovery from this state requires
reflashing of the Intel


ME firmware.



Issue #
320684

“Unexpected autoshutdown after Connected Standby stress
testing

in rare cases
” is under investigation.



RPMC
w
as remove
d in th
e

10.0.25.1048 PV release.



Intel


Identity Protection Technology (Intel


IPT) POR change: Intel


IPT
support expanded to Intel


Pentium


and Intel


Celeron


processors (in
addition to Intel


Core™ processors).

This change is applicable for all
generations supporting Intel


IPT (i.e. Sandy
Bridge, Ivy Bridge, Haswell and Broadwell processors).



BIOS/SW cannot configure GPIO 74/75

(Issue #4802515):

Writes to the GPIO_USE_SEL bit 0 of the GPnCONFIGA registers for these two
pins will have no effect

(GPIO74_SML1DATA & GPIO75_SML1CLK).


Please see the BDW PCH Sighting report for more details (CDI
-

http://www.intel.com/cd/edesign/library/asmo
-
na/eng/536956.htm


3.3

Best Known C
onfiguration

For the late
st Client Based
Broadwell
U
/Y

Mobile Platforms

Best Known Configuration
(BKC), please
review
Document ID#
537047

[Broadwell] Platform


Client
-
Based
Platform Best Known Configuration for Broadwell Mobile Platform

-

http://www.intel.com/cd/edesign/library/asmo
-
na/eng/539245.htm




Kit Details



18


Intel Confidential


4

Kit Details

4.1

Build Details

Kit


Changes since
previous
release

(
10.0.
2
5
.1
048

P
V
)?

Reasons
for
changes

Firmware
Version

10.0.26.1000

Yes

See FW
issues
highlighted
below

Intel


ME
BX

Version

10.0.0.0006

No

N/A

CRB BIOS
Version

BDW_LP_ECP_
8
3
_acm2975

Yes

See Intel
BIOS Release
Notes

Intel


MEI
Driver
Version

10.0.
2
5.1042


Certified for Windows* 7/8/8.1

Submission ID:

1665899


Yes

Windows*
certification

SOL Driver
Version

10.0.20.1258

Certified for Windows* 7/8/8.1

Submission ID:
1659520

No

N/A




Kit Details




Intel Confidential

19

4.2

FITC XML Compare





HF

10.0.2
6
.10
00


1


?xml version=
"1.0"

encoding=
"utf
-
8"
�?

=

1

?xml version=
"1.0"

encoding=
"utf
-
8"
�?

2


ftoolRoot version="
5.
9



=

2


ftoolRoot version="
5.
9



Note:



procedure below, please refer to the
Broadwell

PCH
-
LP SPI
Programming Guide
within each kit release
.

Open the Flash image Tool (double
-
click on fitc.exe) and follow the steps
below:

a.

Under Descriptor Region node, right
-
click on VSCC Table, and select ‘Add
Table Entry…’

b.

Enter an Entry name.

c.

Ad
d values for the fields: Vendor ID, Device ID 0, Device ID 1 and VSCC
register value. These fields are with respect to the ‘Entry Name’ entered
above in step b.

Please refer to the 5MB FW Bringup Guide.pdf
included in this kit
for more details.





Intel ME New Features



20


Intel Confidential


5

Intel


ME

New Features


5.1

RCR Update


RCR #

Description / Background

Build

CCG0100011029

Description:



Allow host to read PCH Protected RTC via MEI
message.

Background:

track how long each system has been running
across

an entire lifespan and request read
access to a stable RTC unmodifiable by host
software.

10.0.25.1030

CCG0100011026

Description:



NFC State Control via BIOS.

Background:

Adds support for BIOS to enable/disable NFC if
NFC is ‘Enabled’ in FW image using
FITc/FOV
allowing IT administrators in the field to control
NFC.

10.0.25.1030

CCG0100198241

Description:



Add an option to prevent Intel


IFR SW
installation in the Intel


ME SW installer.

Background:

The Intel


ME 10 SW installer for Intel


ME 10
and ba
ckwards compatible to Intel


ME 9.x and
8.1 platforms uses a MSI Installer instead of the
previous open package and does not allow OxMs
or end customers from deselecting features
during an installation.

10.0.25.1030

CCG0100010800

Description:



Add FW
support to allow disabling Intel


ME FW
watch dog timer (WDT) even when SPI
descriptors are locked.

Background:

Watch Dog Timer is a timer that is used by the
Intel


ME to prevent any possible hang. The
WDT will be triggered if there is no activity from
th
e ARC processor for more than 30 seconds.

10.0.25.1030

CCG0100010579

Description:



Control Intel

ME Unconfigure on RTC Clear.

Background:

10.0.25.1030


Intel ME New Features




Intel Confidential

21

RCR #

Description / Background

Build

The Intel


controlling the Intel


factory defaults) event u
clear event via BIOS.

CCG0100197668

Description:



Pre
-
manufacturing DCI Control.

Background:

DCI enables closed chassis debug using a USB3
port. This RCR allows OEMs to enable DCI on
platforms in Pre
-
manufacturing state through
the PCH soft strap 10, bit 5.


10.0.20.1156

CCG0100196813

Description:



FITC SKU Emulation


No Emulation Support
pre
production.

Background:

The Intel


ME10 Firmware will support both
BDW PCH
-
LP and HSW PCH
-
LP.

The lack of a no emulation option in the SKU
emulation drop down box when loading pre
-
production FW in FITC, is causing the need for 2
firmware images to be produ
ced (one for HSW
and one for BDW) since each force a different
SKU emulation.

10.0.20.1156

CCG0100010944 /
CCG0100010294

Description:



NFC over NCI support on HSW with Intel
ME10.

Background:

NCI protocol support is a Windows* 8.1 logo
requirement and
must be supported by NFC
solution providers.


Intel


ME FW will support the NCI protocol for
communication with the NFC module on HSW
platforms with Intel


ME FW 10 and support of
the old HCI protocol will be deprecated.

10.0.20.1156

CCG0100010916

Descrip
tion:



Adding BUS driver capabilities to Intel


MEI
Driver.

Background:

The Intel

MEI driver acts as a communication


ME FW
clients. T
he OS can load/unload them in any
order, therefore, an OS could unload Intel

MEI
driver before unloading the NFC Driver which
may lead to communication and timing issues


MEI driver.


10.0.20.1156


Intel ME New Features



22


Intel Confidential


RCR #

Description / Background

Build

CCG0100010898

Description:




Background:

Intel


ME 10 firmware is required to support
both Haswell
-
LP and Broadwell
-
LP PCH hardware
with the same firmware build.


ensure proper system operation and this RCR
F
W image.


10.0.20.1156

CCG0100010879

Description:



Intel


Platform Protection Technology Support
on Intel


vPro™ Platforms with Intel


TXT
Disabled

Background:

Intel


Platform Protection Technology is
supported on Corporate SKUs (5MB) in addition
to Consumer SKUs (1.5MB). Since Intel


Platform Protection Technology and Intel


TXT
are incompatible, currently the support of Intel


Platform Protection Technology on an In
tel


vPro™ machine is not explicitly defined

This RCR confirms that Intel


Platform
Protection Technology is supported on a
Corporate SKU (5MB) vPro platform, when
Intel


TXT is disabled.

10.0.20.1156

CCG0100010776

Description:



Intel


PTT Gen2 functiona
lity (excluding SPI
RPMC) to Intel


ME10 on Haswell
-
LP.

Background:

Platforms launching after 1.1.2015, will need to
support Intel


PTT Gen2 command profile
the Windows* 8.1 logo certification. This RCR
asks for Intel ME10 to support SHA2 PCRs +
ECC + EK cert (a.k.a. Intel


PTT Gen2) on
Haswell
-
LP platforms.

10.0.20.1156

CCG010001082
2

Description:



Remove Chip Erase Command Support from
FPT.

Background:

FPT will not support the chip erase (
-
c)
command any longer to accommodate RCR
CCG0100010574.

10.0.20.1156

CCG0100010623

Description:



SPI RPMC (also known as Intel


PTT Gen2)
10.0.20.1156


Intel ME New Features




Intel Confidential

23

RCR #

Description / Background

Build

Default Mode Change.

Background:

SPI Based monotonic counters is a new
approach for enabling anti
-
replay monotonic
counters (RPMC) on the platform. It requires
enabling a SPI part with special support for anti
-
replay monotonic counters.

SPI RPMC can be
enabled/disabled via FITC
(Enabled by default).

CCG0100010579

Description:



BIOS Control on Intel


ME un
-
configure when
RTC is cleared.

Background:

OEMs can design their platform without RTC coin
battery and use the Main Battery to power the

RTC well.

Some applications of Intel


ME store information
on the RTC well. When the RTC well is cleared,
Intel


ME performs the Intel


ME Unconfigure
operation which could cause loss of all data
stored in RTC and thus, reverting some of the
application
to factory default (e.g. Intel


AM Un
-
provision). In order to mitigate the risk in an
RTC less design, this RCR allows BIOS to control
the Intel


ME un
-
configure operation upon RTC
clear.

10.0.20.1156

CCG0100010574

Description:



Flash Device Hardening
-

NIST
-
800
-
147
Manufacturing Tools Support.

Background:

the default value for the Invalid Opcode (0
-
7)
in the descriptor as follows: Instruction 0


0x21
Instru
ction 1

0x42 Instruction 2

0x60
Instruction 3

0xAD Instruction 4

0xB7
Instruction 5

0xB9 Instruction 6

0xC4
Instruction 7
-
0xC7 The blocked Opcodes are
communicated to the PCH SPI Controller by the
OEM, through the flash image (In the descriptor
regio
n)

FPT will read the FLILL and FLILL1 invalid
opcode registers when a chip erase is requested.
If the chip erase opcode is in the black list, the
command is prevent from executing and the
user should use the bl
ock erase command
instead.

10.0.20.1156

CCG0100010496

Description:



Add FWSTS bit to indicate if SPI log is empty or
10.0.20.1156


Intel ME New Features



24


Intel Confidential


RCR #

Description / Background

Build

non
-
empty.

Background:

When Intel


errors/events, MDES SPI Flash logging feature
will store those messag
es in the SPI flash.
Currently there is no mechanism available to
indicate if SPI log is empty or non
-
empty. RCR
adds FWSTS bit to indicate if SPI log is empty or
non
-
empty and defines bit 15 to Extended
Firmware status (FWSTS2). Additionally,
MEINFO to
ol will indicate if SPI log is empty or
not.

CCG0100010465

Description:



Simplify SPI refurbish process for SPI RPMC
(a.k.a Intel

PTT Gen2).

Background:

Intel


PTT Gen2 (SPI Based Monotonic
Counters) requires binding between the PCH and
the SPI and exchange of a root key over the SPI
bus. When the SPI part is replaced, a rebind is
required. In order to make sure the rebind is
done in authorized environment, by

authorized
personal, an external means of authentication is
required. OEM was required to implement
authentication server environment in
manufacturing line or in refurbish lab.

10.0.20.1156

CCG0100010311

Description:



Adding Intel

ME10 Support to Haswe
ll+ LPT
-
LP
MCP products.

Background:

Intel


ME10 Will be able to load on a Haswell
ULT based platform (Haswell + LPT
-
LP MCP).
When running on this HW configuration, Intel


ME10 will not have any new feature. Only
baseline transfer from Intel


ME9.5 is
sup
ported.

10.0.20.1156

CCG0100010234

Description:



Intel


PTT support in TPM2.0 profile.

Background:

Intel


PTT will support the TPM2.0 PC Client
command Profile, ECC
-
DSA algorithm agility and
SHA2
-
PCRs on Intel


ME10 FW, running on
Broadwell HW.

10.0.20.1156

CCG0100010195

Description:



Enable OOB Remote Monitor Screen Blanking
(ORMSB) for an Intel


AMT enabled devices.

Background:

System managers of public unattended systems
10.0.20.1156


Intel ME New

Features




Intel Confidential

25

RCR #

Description / Background

Build

in cases such as cra
shes, maintenance, and
healing sessions to hide display from public view
while system keeps running.

CCG0100010832

Description:



Add an option to program the FQDN and PKI
suffix through FOV interface.

Background:

Calls out for requirement to

add FOV variables
for FQDN and PKI suffix in the factory. The
FQDN and PKI suffix FOVs to be added are to
help end customers provision in ACM mode for
Wireless LAN only Intel


vPro platforms to
prevent additional manual steps.

10.0.20.1156

CCG0100010625

Description:



Allow FQDN & PKI DNS Suffix Programming in
Favor of Admin Control Mode provisioning on
LAN
-
less Platforms.

Background:

Allows Intel® Vpro™ provisioning via Host
Based Configuration in Administrator Control
Mode (ACM) when secure FQDN is
programed
(via FITC, Intel MEBX or USB).

10.0.20.1156

CCG0100010639

Description:



AMT SMI client over Intel MEI2 will be
removal.

Background:

Intel


ME supports special Intel


AMT SMI client
alerts and logging alerting events.

10.0.20.1156

CCG0100010643

Description:



The version of HDCP used by Intel WiDi has
been updated to version 2.2

Background:

Intel


WiDi uses HDCP to strea
m protected
content over the Intel


WiDi link.

10.0.20.1156

CCG0100010501

Description:



Adding Remote Wake Capability into Intel


ME10 and Enable it by Default.

Background:

Remote Wake is one of the features of Intel


Smart Connect technology and can work over
wired LAN (a.k.a. LAN) or wireless LAN (a.k.a.
WLAN).

In the Shark Bay ULT platform, Remote Wake
over LAN was not supported but in Intel


ME10,
Remote Wake will be supported over LAN (on
10.0.20.1156


Intel ME New Features



26


Intel Confidential


RCR #

Description / Background

Build

non Connected Standby p
latforms) as well as

Remote Wake will be enabled by default.

CCG0100010434

Description:



Windows* 8.1 Validation Requirements for
Intel


ME FW 10.

Background:

Adds support for Windows* 8.1.

10.0.20.1156

CCG0100010402

Description:



Support all mobile DeepSx on AC power states
which do not require M3 operation.

Background:

Currently DeepSx is supported for Mobile
platform in DC mode and Desktop platform in
AC mode. Request adds validation
coverage to
support DeepSx for mobile platform in AC mode.

10.0.20.1156

CCG0100010397

Description:



Reboot Request after Intel


AMT Provisioning.

Background:

Intel


ME Power Gating is supported in the 5MB
SKU of Intel


ME10. In order to allow Intel


ME
to enter power gating (PG), the SOL device is
not exposed to the OS, while Intel


AMT is not
provisioned. As a result, SOL device is
unavailable immediately after provisioning, until
the machine reboots

After Intel


AMT provisioning, IMSS will notify
the
user that the machine needs to be rebooted
due to a configuration change that was initiated
by the system administrator. The user will be
given the option to choose reboot now or, defer
the reboot. If the user chooses reboot now, the
IMSS will initiate a

reboot. All strings will be
localized.

10.0.20.1156

CCG0100010327

Description:



Remove Configuration Tools from FW Kit.

Background:

Remove the Configuration Tools folder, and all
its contents, from the Intel


ME 5MB FW kits.
The USBFile.exe tool, which is in a sub
-
folder of
the Configuration Server, is moved to the
UdpParam tool folder.

10.0.20.1156

CCG0100010284

Description:



Restore ~Graceful RCO `Ability during
Windows* Connected Standby state.

Background
:

Intel


AMT will be supported in Windows*
Connected Standby (CS) state in Intel


ME10
10.0.20.1156


Intel ME New Features




Intel Confidential

27

RCR #

Description / Background

Build

(on BDW platform).

Intel


AMT supports Legacy RCO (Remote
Control Operation) and has the ability to make a
remote power operations such as shutdown,
. Intel


AMT supports next
hibernate

Intel


AMT will support the above RCOs while
the system is in CS state.


CCG0100010592

Description:



Remove EOM checkbox and tag in FITC/FIT and
FPT commands for

Background:

A few generations ago

Intel
the

mfg done” bit (“fpt
-
u
-
n globallocked
-
v
0x1”) and flash access permission to Intel
recommended values (“fpt
-
lock") into “fpt
-
closemnf”. Moreover “fpt

dumplock” displa
yed
descriptor region and was replaced with “fpt

i”.
Removing the fpt

lock and fpt

dumplock and
checkbox in FITC will remove redundancy,
confusion about their difference and erroneous
configurations.

10.0.0.104
2

CCG0100010711

Description:



Re
-
enable FITC to choose load series resistance
for LPC Clocks for Intel


ME 10 platforms.

Background:

under ME Region
-
�Integrated Clock Controller
-
�Profile allows customers to
control LPC Clock
series resistance (17 ohm)). In Intel


ME 9.5
for double load was removed leaving single load
as the only option.

10.0.0.1012

CCG0100010225

Description:



Implementation of a UDP interface for Intel


RWT.

Background:

Along with support for sending Keep Alive


RWT
the Intel


appropriate format.


10.0.0.1012


Intel ME New Features



28


Intel Confidential


RCR #

Description / Background

Build



CCG0100010208

Description:



A field in WS
-
Event has been added that wh
en
CILA is triggered, identifies the originating
system and how or why it was generated at
generation time.

Background:

ISV solutions dependent upon the CILA and
CIRA WS
-
Eventing alerts were not scalable
because there were no means to identify the
hostname

of the originating system or how or
why a CILA alert was generated.



10.0.0.1012

CCG0100010128

Description:



Legacy AMTHI commands removed in Intel


ME
10.

Background:

AMTHI commands marked as deprecated have
been removed to reduce FW code.

10.0.0.1012


Issue Status Definitions




Intel Confidential

29

6

Issue Status Definitions

This document provides sightings and bugs report for
Intel


Management Engine
Firmware
10.0

SKU, Software and Tools for
the
Broadwell

U
/Y
-
Series Platform
. Each
report contains a snapshot of sightings and critical internal bugs dating to the Friday
of the week in which it was released. At the time of a milestone release, this report
will be distributed with the
Intel


ME

Kit and will provide information o
n new issues
and the status of old issues (replacing the Release Notes document).

The issues are separated into sub
-
groups to assist in understanding the status of the
issues and what action, if any, needs to be done to address the issue. The names and
def
initions of the sub
-
groups are detailed below.

Closed Issues
: Issues will not be classified as “Closed” until the fix is verified with
the appropriate firmware version or disposition given below. Closed issues are
separated into three different categories:



Closed


Fixed in Firmware Kit:

All issues detailed in this
section have been fixed in the firmware version identified in the
individual sighting details.



Closed


No Plan to Fix
: All issues detailed in this section are
not planned to be fixed in any
revision of the firmware.



Closed


Documentation Change:

All issues detailed in this
section require a change to either a specification and/or a
documentation change. The specific revisions to the appropriate
documentation/specification are identified in t
he issue details.

Open Issues
: New sightings and bugs will be classified as “Open” issues until the fix
is verified with the appropriate firmware version. Ope
n issues are separated into
categories based on suspected component.
All issues
under Open Issues

are still
under investigation. Issues may or may not be root caused.

Note:

Any issues that are still open for production revisions of the components
will be documented in the respective specification update documents.

Sightings listed in this document apply to A
LL
B
roadwell

CRB SKU’s unless
otherwise noted either in this document or in the sightings tracking systems.



Closed Issues



30


Intel Confidential


7

Closed Issues

7.1

Closed



Intel


AMT

Issue #

Description

Affected Component/Impact /
Workaround/Notes

Fixed in Kit#

320702

If KVM session is opened during
Connected Standby and
the
SUT
resumes to S0
, if the

opened User
Consent Sprite Window is closed

in any
way,
a
Black Screen
and CAT ERROR
may occur.



Affected Component


FW.AMT.UserConsent

Impact:

Black screen and CAT ERRO
R
if User Consent is invoked on exit from
Connected Standby if HDMI display is
connected to SUT.

Workaround:

None.

Notes:

10.0.26.1000

320589

SUT fails to display the OptIn code from
the Intel


MEBX when resuming from
Connected Standby or when the display
timeout has expired.

Affected Component


FW.AMT.UserConsent

Impact:

A

reboot
may be

required
prior to displaying the

OptIn code.
Unable to establish KVM session if User
Consent is required w
hen resuming
from CS.

Workaround:

None.

Notes:

10.0.26.1000

320582

S5/M3 + Power Button up resulting in
FW in recovery state.

Affected Component


FW.AMT.UserConsent

Impact:

FW reset causes Boot Guard
to block the OS from loading.

Workaround:

None.

Notes:
Issue trending as localization
component.

10.0.25.1048

100186531

Host driver does not connect within a
few seconds in passive mode after
resuming from Sx, or when
enabling the
wireless driver or during a restart.

Affected Component


WiAMT

Impact:

Redirection stress testing
over WLAN may fail.

Workaround:

None.

Notes:
Fixed in the next Intel


drivers kit release.

Update: WLAN
driver kit release date
trendin
g to
WW30.

N/A

100210516

After waking from Sx, Intel


AMT on
SUT may not be accessible over wireless
while the LAN interface is still accessible


Affected Component


WiAMT

Impact:

May lose connection with
Wireless Intel


AMT during S3 cycle
testing.

Workaround:

None.

Notes:
Fixed in the next Intel


drivers kit release.

N/A


Closed Issues




Intel Confidential

31

Issue #

Description

Affected Component/Impact /
Workaround/Notes

Fixed in Kit#

320204

When KVM is disabled in FITC, screen
blanking doesn't work and displays "The
service cannot comply with the request
due to internal
processing errors".

Affected Component


FW.AMT.RemoteControlOperations

Impact:

Screen blanking does not
work.

Workaround:

Feature can be enable
via WSMAN.

Notes:
This issue has been fixed in this
PC release but has not completed
validation.

10.0.25.1
030

100200514

A SUT with WiAMT enabled and moving
from S0 to S3 and performing HW RF
off and resuming with RF on will cause
the Intel


ME to not respond on
WoWLAN.

Affected Component


WiAMT

Impact:

Loss of Intel


ME connectivity
(host is alive and WiAMT receives an IP
address but Intel


ME
is non
responsive
)
.

Workaround:
Perform G3.

Notes:

Fixed in the next Intel


drivers kit release.


10.0.25.1030

320534

When provisioning Intel


ME with
WLAN/LAN, and run
ning "opentestman"
tests, results show
PowerManagementService,
PowerManagementCapabilities failure.

Affected Component


FW.AMT.WSMAN_GEN

Impact:

DASH compliance Power
Management tests fail.

Workaround:
None

Notes:


10.0.25.1030


Closed Issues



32


Intel Confidential


Issue #

Description

Affected Component/Impact /
Workaround/Notes

Fixed in Kit#

320324

FW doesn't update

the connection
status after transition from IN to OUT
when IPv6 is enabled.

Affected Component


FW.AMT.RemoteConnectivity

Impact:

May not be able to open CIRA
connection by UI via Intel


IMSS/Intel


MEBX/BIOS.

Workaround:
None

Notes:

Reproduction Steps:

1.

Add MPS and UI Policy.

2.

Enable IPv6 via WebUI.

3.

15 (ex : intel.com).

4.

Move SUT to OUT environment.

5.

Open DebugView with filter

6.

FW should send
ConnStatus=0 ConnType=2(out)
ConnTrigger=0

and CIRA connection can be open.

However, FW sends
ConnStatus=0 ConnType=0
(in)

ConnTrigger=0

and CIRA fails to open via Intel


IMSS and the “Get Technical help”
is greyed out.

10.0.25.1030

320166

Intel


address when connected to a different


Affected Component


FW.AMT.NETP

Impact:

Intel


ME may not accept a
environment has changed.

Workaround:
None

Notes:

Intel


ME sends IP request and
DHCP sends offer and ack, but Intel


ME loses address and reverts to the old
address.


10.0.25.1030

100203194

SUT fails to res
ume from S3/S4/S5
-
M3
when Intel


to PP2.

Affected Component


WiAMT

Impact:

System does not resume from
S3/S4/S5 after Intel


AMT is
provisioned.

Workaround:
G3 or power button
override.

Notes:

Fixed in Intel


kit release.


N/A


Closed Issues




Intel Confidential

33

Issue #

Description

Affected Component/Impact /
Workaround/Notes

Fixed in Kit#

319974

IDER device is not hidden on OS restart
flow.

Affected Component


FW.AMT.Remote Control Operations

Impact:

IDER device is not hidden on

Workaround:

Notes:

Reproduction Steps
:

1.

Provision Intel


Power policy to PP2.

2.

run cold boot on DOS, then boot to
Windows

3.

Check in Device Manager under IDE
ATA/ATAPI controllers: IDE
-
R
controller is listed

10.0.25.1030

319827

Sporadically an un
-

power package 2, when
80 seconds from Power Button
Override.

Affected Component


FW.AMT.General

Impact:

Unexpected global reset may
2 when no WLAN adapter is installed.

Workaro
und:

None

Notes:

Reproduction Steps:

1.

Flash image on SUT.

2.

Set SUT to power pkg 2 in Intel


MEBX.

3.

Boot SUT to OS.

4.

Perform power button override
(PBO).

5.

Wait 80 seconds

6.

Boot to OS.

7.


10.0.20.1156

215809

When DNS infrastructure is
implemented with a trailing dot ending
the FQDN. FW rejects the FQDN.

Affected Component


FW.AMT.Provisioning

Impact:

Provisioning with PKI will fail.

Workaround:

N/A

Notes:
Occurs if the DNS infrastructure
is implemented according to RFC 1034
with a
trailing dot ending the FQDN.


10.0.0.1012


Closed Issues



34


Intel Confidential


7.2

Closed


Intel


ME Kernel

Issue #

Description

Affected Component/Impact /
Workaround/Notes

Fixed in Kit#

320629

After Intel


ME BIOS Payload message,
HECI may indicate it is ready to receive
messages before it is able to receive.

Affected Component


FW.Kernel.HECI

Impact:
May cause
HECI message
sent after MBP to be incomplete to
Intel


ME.


Workaround:

None

Notes:
.

10.0.25.1048

320487

Intel


ME exits Intel


ME PG state
immediately.

Affected Component


FW.Kernel.
TCPIP

Impact:
May prevent power saving.

Workaround:

Allow SUT to move to
Power Gating (PG)

after 30 minutes.

Notes:
Occurs after configuring system
with

Connected Standby, booting to OS
and removing LAN cable when system
is idle.

10.0.25.1048

320287

Intel


reason for valid Remote Wake.

Affected Component


FW.Kernel

Impact:
Wake reason can be
overwritten if the server send
wake

Workaround:

None

Notes:

10.0.25.1048

320393

Intel


ME FW enables DCI on a bringup
critical error path.

Affected Component


FW.Bringup

Impact:
USB devices would not
connect with DCI enabled.

Notes:

This
failure will only have impact on
production systems if End Of
OEM.

10.0.25.1030

320390

After closemnf, BIOS shows “ME FW
Downgrade
-

Request MeSpiLock Failed”
error message due to HMRFPO_LOCK
response timeout or POST
time is
delayed.

Affected Component


FW.Kernel.FWUpdate

Impact:

May see an increase in boot
time.

Notes:


10.0.25.1030

320372

Intel


ME fails to go to Moff (M0
-
�Moff,
M3
-
�Moff) if MDES is enabled on SMBus.


Affected Component


FW.Kernel.SmBusDriver

Impact:

With MDES SMBus enabled:
In PP1, a system cannot enter Sx and
hangs. In PP2, the Intel


ME cannot go
to M3
-
�Moff after idle timeout and the
system hangs.

Notes:


10.0.25.1030


Closed Issues




Intel Confidential

35

Issue #

Description

Affected Component/Impact /
Workaround/Notes

Fixed in Kit#

320354

MEManuf displays “Eror 9331: SMBus
hardware is not ready Error
9296:
MeManuf Test Failedmessage on first
boot.

Affected Component


FW.Kernel.SmBusDriver

Impact:

MEManuf may fail on first
power.

Notes:


10.0.25.1030

215642

SUT enters into a S5

Cycle during reboot
when Intel


ME is in an PG state.

Affected Component


FW.Kernel.PowerManagement

Impact:

While the
Intel

ME is in
Power Gating (PG) state and the
system is rebooted from the OS UI or
for 1
-
2
seconds and only then the
system is power on.

Notes:


10.0.20.1156

215411

Intel


ME transition from Moff to M3
then waking from Sx cause a global
reset.

Affected Component


FW.Kernel.PowerManagement

Impact:

May observe unexpected
transitions when resuming from Sx
states.

Notes:
Only happens when ME goes
from Moff to M3.

Reproduction Steps:

1.

Intel


ME.

2.

Start SUT in S0/M0 PP2 DC.

3.

Move SUT to S4 via Windows*
hibernate.

4.

Apply AC power back to the SUT.

5.

Press the Power button to resume
SUT back to Windows*.

6.

SUT should resume back to
Windows* but SUT performs a
to Windows*

10.0.20.1156


Closed Issues



36


Intel Confidential


Issue #

Description

Affected Component/Impact /
Workaround/Notes

Fixed in Kit#

319641

After
flashing a partial Intel


ME
Firmware image. ME is left in recovery
mode.

Affected Component


FW.Kernel.BistMgr

Impact:

Intel


ME may enter recovery
mode after flashing a partial ME
Firmware image.

Notes:

Reproduction Steps:

1.

Ensure M3 autotest is enabled

in
image.

2.

Flash SPI image

3.

Perform a partial FW update.

4.

Intel


ME may enter recovery
mode.


10.0.0.1042

7.3

Closed


Intel


Device Protection Technology
with Boot Guard

/
Intel


PTT

Issue #

Description

Affected Component/Impact /
Workaround/Notes

Fixed in
Kit#

320708

System hang during S3/S4
stress
testing
. System does not resume from
S3/S4 and system may hang with POST
Code 0x00AD or 0x0096.

Affected Component


FW.PTT.Main

Impact:

Intel


PTT may cause a BDW
2+2 SUT from resuming after
strenuous Sx cycle testing.

Workaround:

None.

Notes:


10.0.26.1000

320359

/
320183

from FWSTS2 after flashing profile_0 (or
guard=disabled.

Affected Component


FW.PTT.Main

Impact:

Intel


first boot after flashing causing a long
or delayed boot time.

Workaround:

None.

Notes:


10.0.25.1030



Closed Issues




Intel Confidential

37

7.4

Closed


Software /
Tools

Issue #

Description

Affected
Component/Impact /
Workaround/Notes

Fixed in Kit#

5486763

Intel


ME 10 SW switch "
-
notc" does not
prevent IUM installation during an
upgrade.

Affected Component


Installer

Impact:
Running the Intel


ME SW
update, the
-
NO
TC

switch is ignored
and Intel


Update Manager is installed.

Workaround:

Uninstall Intel


ME SW
and reinstall SW as as fresh install.

Notes:

Replication Steps:

1.

Install Intel


ME 10 SW e.g.
“SetupME.exe
-
s
-
notc

noimss”
and the
Intel


Update Manager
agent is not installed as
expected.

2.

Upgrade to
later version of Intel


ME

10 SW
e.g. “
SetupME.exe
-
s
-
notc

noimss

Intel


Update
Manager

is installed despite the
notc switch.


10.0.25.1030

5485979

Intel


Management Engine Firmware
Recovery Agent displays it is uninstalled
on system where it was never installed.

Affected Component


Installer

Impact:
The uninstallation screen
displays that Intel


IFR was uninstalled
on a system which has Intel


IFR
disabled in firmware and was never
installed.

Workaround:

None.

Notes:

Replication Steps:

1.

Set the ‘ME Region | Configuration
| ME | Independent Firmware
Recovery Enable’ setting to ‘false’.

2.

Boot to OS on fresh system that
does not have Intel


ME FW
installed. If not, uninstall all Intel


ME
-
related software before
proceeding.

3.

Install the Intel


ME 10 SW
software package from a previous
release.

4.

Uninstall the Intel

ME SW.

5.

"Intel(R) Management Engine
Firmware Recovery Agent" is
reported on the

final summary
screen as having been uninstalled
despite Intel


IFR is disabled in FW
and not previously installed.

10.0.25.1030


Closed Issues



38


Intel Confidential


Issue #

Description

Affected
Component/Impact /
Workaround/Notes

Fixed in Kit#

5443890

When installing Intel


ME SW with
Intel



Recovery Agent was

successfully
installed.



Affected Component


Installer

Impact:
displays Intel


ME Firmware Recovery
Agent instead of Intel


Update
Manager.

Workaround:

None.

Notes:




10.0.25.1030

320092

LMS service occasiaonally fails to shut
down.

Affected Component


SW.AMT.Services

Impact:

Sporadically the LMS service
fails to shutdown.

Workaround:

None.

Notes:

Reproduction Steps:

1.

Install older Intel ME 10 SW.

2.

Upgrade to the current release of
Intel


ME 10 SW

3.

Sporadically the upgrade fail
s due
to LMS not stopping.

4.

LMS service does not stop,
blocking placement of the new
LMS and causing the isntall to fail.

10.0.25.1030

319860

"FPT
-
r NfcGpioIrq" FOV is not
consumed upon FPT is commit.

Affected Component


SW.Tools.FlashProgrammingTool

Impact:

Affects GPIO NFC IRQ pin
assignment.

Workaround:

None.

Notes:
Related to #215998 under
Open


Intel


NFC. FPT has been fixed
by updating the table value to enable
FOV.

Reproduction Steps:

1.

On CRB run "FPT
-
u
-
n nfcgpioirq
-
FC IRQ
pin.

2.

Run "FPT
-
r nfcgpioirq" to check
the update of FOV value.

3.

#2 result is "Value: GPIO26 / 00"
instead of expected “Value:
GPIO73 / 01".


10.0.25.1030


Closed Issue
s




Intel Confidential

39

Issue #

Description

Affected
Component/Impact /
Workaround/Notes

Fixed in Kit#

319846

When using an input file to update FOVs
in FPT (the
-
in option), if you use an
input
file that does not contain a blank
line at the end, then FPT will fail to
update the last FOV in the file. If you
add a blank line to the end of the file,
then FPT updates all FOVs correctly.

Affected Component


SW.Tools.FlashProgrammingTool

Impact:

Upda
ting FOVs with an input
file that does not contain a blank line
at the end will not update the last FOV.

Workaround:
Add a blank line at the
end.

Notes:

Reproduction Steps:

1.

Create a file called fovlist.txt that
contains the following line:

2.

OEM_TAG = 0x12
345678

3.

Make sure that there is *not* a
blank line at the end of the file.

4.

Execute "fpt
-
u
-
in fovlist.txt
-
verbose

5.

"OEM_TAG" not being updated and
should display "OEM_TAG" will be
updated with value: "0x12345678"

6.

If a blank line to the end of
fovlist.txt

is added, then OEM_TAG
will be updated correctly.

10.0.25.1030

319336

Once ACPRESENT state is changed,
FWSTS Phase (FWSTS2[28:31])
becomes Policy Phase. With this
condition, FPT /greset fails with an error
"The ME is not in a functional state.
Cannot
execute ME Reboot." even
though the ME is in a functional state.

Affected Component


SW.Tools.FlashProgrammingTool

Impact:

Manufacturing tests may fail
because the Intel


ME FW state was
"Policy module" vs being in a functional
state.

Workaround:

None.

N
otes:


10.0.25.1030


Closed Issues



40


Intel Confidential


Issue #

Description

Affected
Component/Impact /
Workaround/Notes

Fixed in Kit#

5444506

Upgrading from Intel


ME 8.x and Intel


ME 9.x Software to Intel


ME 10
Software does not work properly.

Affected Component


Installer

Impact:

After upgrading from Intel


ME 8.x and Intel


ME 9.x Software to
Intel


ME 10 Software, both versions
of Intel

ME Software (the older
version and the Intel


ME 10 version)
are listed in the Control Panel’s
Installed Programs list, Intel


IMSS
may not work properly, and
subsequently uninstalling the previous
Intel


ME SW ve
rsion may uninstall
some of the Intel


ME 10 Software
components as well.

Workaround:

None

Notes:





10.0.25.1030

5294446

The Intel


ME Software installer reports
that IFR software has been installed,
even when IFR has been disabled in the
Intel


ME firmware image.

Affected Component


SW.AMT.Icon

Impact:
May confuse customers and
lead them to believe that IFR has been
installed.

Workaround:

None

Notes:





10.0.25.1030

320279

The handle count of the system process
increases at every S3/S4 cycle
with the
Intel


ME SW included in the recently
released 10.0.0.1168 PV SW
-
Only and
9.1.0.1120 PV kits.

Affected Component


SW.HECI
Driver

Impact:

Each powercycle S0 to S3/S4
caused the number of the following
handle to be increased:

HKLM
\
SYSTEM
\
ControlSet001
\
Services
\
MEIx64
\

Workaround:
N/A


10.0.25.1030


Closed Issues




Intel Confidential

41

Issue #

Description

Affected
Component/Impact /
Workaround/Notes

Fixed in Kit#

320041

BIST test Fails with Production MCP and
Production image. MEManuf gives
"Error 9411: EPID Group ID out of
range. Please check FW Version is
Compatable."

Affected C
omponent


SW.Tools.MeManuf

Impact:

BIST test fails with production
parts.

Workaround:

None

Notes:

Reproduction Steps:

1.

Setup SUT with production MCP.

2.

Flash production FW on SUT.

3.

Run MEManuf

s0

verbose

4.

B
IST should pass without error but
with “Error 9411:
EPID Group ID out of range.
Please check FW Version is
Compatable.”

10.0.20.1156

319354

Periodically MEInfo displays "Not
Available" for BIOS and Intel


MEBX
versions.

Affected Component


SW.Tools.MEInfo

Impact:

MEInfo may not display the
BIOS and
Intel


MEBX

version.

Workaround:

None.

Notes:

Reproduction Steps:

1.

Run MEInfo.

2.

Displays "Not available" for Intel


MEBX and BIOS.

10.0.20.1156

319311

When executing
-
meinfowin.exe, the

' The function
Windows Error Code: 1 '

Affected Component


SW.Tools.MEInfo

Impact:

Running Windows MEinfo
results in error

Workaround:

None.

Notes:


10.0.20.1156

319193

Meinfo displays the NFC radio FW
version with only 2 bytes instead of the
expected 3 bytes value.

Affected Component


SW.Tools.MEInfo

Impact:

“NFC FW Version” may be
displayed incorrectly.

Workaround:

None.

Notes:


10.0.20.1156


Closed Issues



42


Intel Confidential


Issue #

Description

Affected
Component/Impact /
Workaround/Notes

Fixed in Kit#

215845

RPMC binding (fpt
-
rpmcbind) results in
Error 8199 (communication error).

Affected Component


SW.Tools.FlashProgrammingTool

Impact:

Error appears when
executing: # fpt
-
rpmcbind

Workaround:

None.

Notes:

Reproduction Steps:


10.0.20.1156

215728

Executing ‘MEManufWin64.exe

TEST’
may result in te following errors:

Error 9328: Internal error

Error 9296: MEManuf Test Failed


Affected Component


SW.Tools.MEManuf

Impact:

MEManuf
-
TEST fails to rerun
a full test.

Workaround:

None.

Notes:
No longer able to reproduce
issue with 10.0.20.1156 FW.

Reproduction Steps:

1.

Flash image and clear CMOS.

2.

driver and Intel


MEI driver

3.

Execute MEManufWin64.exe
-
TEST

4.

System should perform full BIST
however it
errors:

Error 9328: Internal error

Error 9296: MEManuf Test Failed

10.0.20.1156


Closed Issues




Intel Confidential

43

7.5

Closed


No Plan to Fix

Issue #

Description

Affected Component/Impact / Workaround/Notes

215804

"Fast Call for Help" button become
available when WiAMT
is enabled and
LAN or WLAN device is disabled in
device manager

Affected Component


SW.AMT.Icon

Impact:
"Fast Call for Help" button become
available when
WiAMT is enabled and LAN or WLAN device is disabled in device
manager

Workaround:

When issue occurs,
click the "Disconnect" button
and then the button status will be correct

Notes:

Reproduction Steps:

1.

Flash bios and provision
Intel


ME

2.

Setup

Intel



ME to connect to Wireless profile via WebUI

3.

Boot to OS and confirm the
Intel



ME has been connected
to wireless accordingly.

4.

Disable wireless or LAN device in OS device manager

5.

Check IMSS "Fast Call for Help" button.
---
� (if status still
normal in step 5, go to next step.)

6.

Set System to enter S3.

7.

Resume from S3.

8.

Check IMSS "Fast C
all for Help" button.
----
� (button will

9.


10.

IMSS will pop
-
up warning message for failing to reach your
support organization.

11.

Click on OK button to close warning message.

12.

Check on "Fast Call for Help" button become available and
show up "Disconnect".

7.6

Closed


Not a Firmware or Software Bug

Issue #

Description

Affected Component/Impact /
Workaround/Notes

320510

After running "fpt
-
closemnf" to fuse
the part followed by G3 and CMOS
clear, “PTT Lockout Override Counter"
does not increment as expected in DOS
and EFI.

Affected Component


FW.PTT.HCI

Impact:

Counter does not increment
when executing "PTT Lockout
Ove
rride Counter" in DOS/EFI
versions of FPT however Windows*
version works as expected.

Workaround:

Perform operation in
Windows* version.

Notes:
Not a bug. DOS/EFI cannot
take ownership of TPM and must test
after booting at least once to
Windows* after fl
ashing FW.



Closed Issues



44


Intel Confidential


Issue #

Description

Affected Component/Impact /
Workaround/Notes

215843

Error 7: Hardware sequencing failed
when flashing image on SUT.

Affected Component


SW.Tools.FlashProgrammingTool

Impact:

Potential Hardware
Sequencing failure when flashing
image.

Workaround:

None

Notes:
Not POR and therefore not a
bug.


Reproduction Steps:

1.

Flash Full_Image to board

2.

Boot to OS

3.

Run "FPT.exe
-
f image.bin"

4.

or

5.

Flash Full_Image to board

6.

Boot to OS

7.

Run "FPT.exe
-
d InitBios.bin
-
bios"

8.

Reboot SUT

9.

Run "FPT.exe
-
f InitBios.bin
-
bios".

10.

Error 7: Hardware sequencing
failed.
(while trying to erase)



Closed Issues




Intel Confidential

45

7.7

Closed


No Plan to Fix

Issue #

Description

Affected Component/Impact /
Workaround/Notes

215998

"FPT
-
r NfcGpioIrq" shows wrong FOV

Affected Component


FW.NFC

Impact:

Affects GPIO NFC IRQ pin
assignment.

Workaround:

Enable NFC before
configuring it.

Notes:

Deferred to Intel


ME 11 platform.

IRQ pin e.g.# FPT
-
u
-
n nfcgpioirq
-
v
01.

Reproduction Steps:

1.

On CRB run "FPT
-
u
-
n
nfcgpioirq

-
for NFC IRQ pin.

2.

Run "FPT
-
r nfcgpioirq" to check
the update of FOV value.

3.

#2 result is "Value: GPIO26 /
00" instead of expected “Value:
GPIO73 / 01".


7.8

Closed


External Dependency

Issue #

Description

Affected Component/Impact /
Workaround/Notes

320538

SUT hangs are postcode “0xEC02”
after resuming from G3 to S5
-
Moff DC
only to S0
-
M0 via power button press.

Affected Component


FW.Kernel.PowerManagement
Embedded Controller

Impact:


Workaround:

Issue can be avoided
by hitting the power button before
10 seconds are up.

Notes:

Doesn’t occur when State
occurs on DC power after G3.
Doesn’t happen when state after G3
is AC/DC or AC.


319776

SUT is unable to ping
or access Intel


AMT while in any Sx state.

Affected Component


External
Dependency


LAN Drivers

Impact:

Ping requests time out and
operator is unable to access remote
Intel

AMT in Sx mode.

Workaround:

Recovery via G3.

Notes:
Trending as a LAN driver
issue.



Closed Issues



46


Intel Confidential


Issue #

Description

Affected Component/Impact /
Workaround/Notes

5316933 /
320362

When CSM is disabled in the BIOS
-

IDER UEFI floppy device is ignored.

Affected Component


External
Dependency
-

BIOS

Impact:

IDER UEFI floppy device
fails, but IDER UEFI CD is working.

Workaround:

None.

Notes:
Not a requirement

319874

When secure boot is enabled in BIOS,
booting to an IDER device while a SOL
session is open causes a black screen.

Affected Component


External
Dependency
-

BIOS

Impact:

Remote operation hangs
recover.

Workaround:

Recovery via RCO
reset.

Notes:



7.9

Closed


Documentation

Issue #

Description

Affected Component/Impact /
Workaround/Notes

Fixed in Kit#

215843

Error 7: Hardware sequencing failed
when flashing image on SUT.

Affected Component


Docu
mentation.SystemToolsUsersGuide

Impact:

Potential Hardware
Sequencing failure when flashing
image.

Workaround:


Notes:

Reproduction Steps:

1.

Flash Full_Image to board

2.

Boot to OS

3.

Run "FPT.exe
-
f image.bin"

4.

or

5.

Flash Full_Image to board

6.

Boot to OS

7.

Run
"FPT.exe
-
d InitBios.bin
-
bios"

8.

Reboot SUT

9.

Run "FPT.exe
-
f InitBios.bin
-
bios".

10.

Error 7: Hardware sequencing
failed. (while trying to erase).

10.0.25.1030



Known Issues




Intel Confidential

47

8

Known Issues

8.1

Open


Intel


AMT

Issue #

Description

Affected Component/Impact /
Workaround/Notes

100210521 /
320610

When attempting to open a KVM
session, it closes immediately and
KVM border frame remains
incorrectly suggersting the KVM
session is still active.

Affected Component


WiAMT

Impact:

May be unable to establish
KVM session over LANless SUT; loss
of redirection sessions.

Workaround:
None

Notes:

KVM session will appear
“active” on remote SUT with KVM
borders.


Not a FW issue. Debugging wireless
driver.


100209192

In a Connected
Standby state, the
host sends DHCP Requests in ~20
second intervals regardless of the
DHCP Lease Time.

Affected Component


WiAMT

Impact:

Connectivity loss and
impacts CS related compliance
testing.

Workaround:

None.

Notes:

Not a FW issue. Debug
ging
wireless driver.

320501

Intel


AMT WEBUI may not be able
to reconnect within the expected
amount of time when running S4
wake by RCO stress testing.

Affected Component


FW.AMT.WebUI

Impact:

Unable to reconnect WEBUI
session without delay.

Workaround:

I
ssue can be avoided
by hitting the power button before 10
seconds are up.

Notes:

100203825

When resuming from S3 with an
closed.

Affected Component


WiAMT

Impact:

May lose IDER session over
wireless.

Workaround:

Reattempt IDER
session.

Notes:

Not a FW issue. Debug
ging
wireless driver.



Known Issues



48


Intel Confidential


8.2

Open


Intel


ME Kernel

Issue #

Description

Affected Component/Impact /
Workaround/Notes

320505

Updating FOV "FeatureShipState" on
Bit29 PTT feature does not take effect
after
global reset.

Affected Component


FW.Kernel.SkuMgr

Impact:

Updating FOVs may not
upda
t
e the Intel


PTT enable bit.

Workaround:

None

Notes:

214984

Intel


ME does not wake to M3 by ping
from Moff after idle timeout if MDES LAN
is enabled.

Affected Component


FW.Kernel

Impact:
Once Intel


ME transits to
OFF status in S3/4/5, Intel

ME can
not be woken up by pinging from
LAN or WLAN.

Workaround:

None

Notes:


8.3

Open


Software /
Tools

Issue #

Description

Affected Component/Impact /
Workaround/Notes

320570

Intel


Management Engine Interface
yellow bang issue when run warm boot or
Sx stress testing.

Affected Component


S
W.HECI
Driver

Impact:


Workaround:

Shutdown and
restart SUT (Intel


MEI driver will no
longer be in yellow bang state and
will function as expected.

Notes:

320673

Intel


IMSS shows "Information
unavailable" for the IPv6 address.

Affected Component


S
W.AMT.Icon

Impact:

IPv6 address doesn’t
appear in Intel


IMSS.

Workaround:

None.

Notes:

319851

Intel


MEI driver does not release LMS
Service from Intel


SBA service for Intel

ME SW Update and an error message
"Windows could not start Intel SBA
service on local computer. Error 1075:
the dependency service does not
exist or
displayed.

Affected Component


Installer

Impact:

Intel


SBA loses
functionality after reinstalling the
Intel


MEI driver.



Known Issues




Intel Confidential

49






Приложенные файлы

  • pdf 23840763
    Размер файла: 634 kB Загрузок: 4

Добавить комментарий