KBL-R Consumer FW Bring Up Guide
KBL-R Consumer FW Bring Up Guide
July 2017
Revision 1.7
Intel Confidential
By using this document, in addition to any agreements you have with Intel, you accept the terms set forth below. You may not use
or facilitate the use of this document in connection with any infringement or other legal analysis concerning Intel products described
herein. You agree to grant Intel a non-exclusive, royalty-free license to any patent claim thereafter drafted which includes subject
matter disclosed herein.
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 INTL
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.
A "Mission Critical Application" is any application in which failure of the Intel Product could result, directly or indirectly, 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 IN 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 instructions 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 notice.
The Kabylake Platform and Kabylake PCH products may contain design defects or errors known as errata which may cause the
product to deviate from published specifications. Current characterized errata are available on request.
Intel® AMT should be used by a knowledgeable IT administrator and requires enabled systems, software, activation, and connection
to a corporate network. Intel AMT functionality on mobile systems may be limited in some situations. Your results will depend on
your specific implementation. Learn more by visiting Intel® Active Management Technology.
Intel® Small Business Technology (Intel® SBT) requires an Intel® Small Business Technology enabled system and proper
configuration. Availability of features will depend upon the setup and configuration by your PC manufacturer. Consult your system
manufacturer.
Intel® vPro™ Technology requires setup and activation by a knowledgeable IT administrator. Availability of features and results will
depend upon the setup and configuration of your hardware, software and IT environment. Learn more at: http://www.intel.com/
technology/vpro.
Any software source code reprinted in this document is furnished under a software license and may only be used or copied in
accordance with the terms of that license.
64-bit computing on Intel architecture requires a computer system with a processor, chipset, BIOS, operating system, device drivers
and applications enabled for Intel® 64 architecture. Processors will not operate (including 32-bit operation) without an Intel® 64
architecture-enabled BIOS. Performance will vary depending on your hardware and software configurations. Consult with your
system vendor for more information.
Intel processor numbers are not a measure of performance. Processor numbers differentiate features within each processor family,
not across different processor families. See http://www.intel.com/products/processor_number for details. I2C is a two-wire
communications bus/protocol developed by Philips. SMBus is a subset of the I2C bus/protocol and was developed by Intel.
Implementations of the I2C bus/protocol may require licenses from various entities, including Philips Electronics N.V. and North
American Philips Corporation.
Microsoft*, Windows* and the Windows* logo are trademarks or registered trademarks of Microsoft Corporation in the United States
and/or other countries.
Intel, Celeron, Pentium, Intel Xeon, Intel Core, Intel vPro™, and the Intel logo are trademarks of Intel Corporation in the United
States and/or other countries. *Other names and brands may be claimed as the property of others.
KVM Remote Control (Keyboard, Video, Mouse) is only available with Intel® Core™ i5 vPro™ and Core™ i7 vPro™ processors with
integrated graphics and Intel® Active Management technology activated. Discrete graphics are not supported.
Intel Confidential
Table of Contents
1 Introduction............................................................................................... 6
1.1 Related Documentation ................................................................................. 6
1.2 Intel® ME FW Features .................................................................................. 6
1.3 Prerequisites ................................................................................................ 6
1.4 Acronyms and Definitions .............................................................................. 7
1.4.1 General ............................................................................................. 7
1.4.2 Intel® Management Engine .................................................................. 8
1.4.3 System States and Power Management ................................................. 9
1.5 Reference Documents ................................................................................... 9
1.6 Format and Notation ..................................................................................... 9
1.7 Kit Contents............................................................................................... 11
1.8 External Hardware Requirements for Bring Up ................................................ 15
3 Programming SPI Flash Devices and Checking Firmware Status ............ 124
3.1 Flash Burner/Programmer...........................................................................124
3.1.1 In-Circuit SPI Flash Programming for CRB ...........................................124
3.2 Flash Programming Tool (Intel® FPT) ...........................................................124
3.2.1 Intel® FPT Windows* Version ............................................................125
3.3 Checking Intel® ME Firmware Status ............................................................126
3.4 Common Bring Up Issues and Troubleshooting Table ......................................128
F Appendix — Integrated Sensor Hub (ISH) Public Key Settings ............... 145
Intel Confidential
Figures
Tables
1-1 Number Format Notation ............................................................................. 10
1-2 Data Format Notation.................................................................................. 10
1-3 Kit Contents............................................................................................... 11
2-1 Intel® FIT - Initial Screen Layout .................................................................. 17
2-2 Intel® FIT - Build Settings ........................................................................... 24
2-3 Intel® FIT - Flash Layout ............................................................................. 25
2-4 Intel® FIT - Flash Settings ........................................................................... 31
2-5 Intel® FIT - Intel® ME Kernel ....................................................................... 40
2-6 Intel® FIT - Intel® AMT ............................................................................... 46
2-7 Intel® FIT - Intel® Platform Protection .......................................................... 53
2-8 Intel® FIT - Integrated Clock Controller ......................................................... 58
2-9 Intel® FIT - Intel® Networking & Connectivity................................................ 78
2-10 Intel® FIT - Flex I/O ................................................................................... 83
2-11 Intel® FIT - Internal PCH Buses .................................................................... 96
2-12 Intel® FIT - GPIO ......................................................................................107
2-13 Intel® FIT - Power .....................................................................................110
2-14 Intel® FIT - Integrated Sensor Hub ..............................................................112
2-15 Intel® FIT - Debug.....................................................................................115
2-16 Intel® FIT - CPU Straps ..............................................................................119
2-17 Intel® FIT - Build Image .............................................................................123
3-1 Common Bring Up Issues and Troubleshooting Table ......................................128
B-1 Intel® ICCS SKU Matrix - KBP-LP.................................................................. 132
B-2 Intel® ICCS SKU Matrix - KBP-H.................................................................. 133
B-3 How to configure CLKREQ# parameters via FIT Tool....................................... 136
C-1 Profile Description..................................................................................... 139
C-2 Enforcement Policy Description.................................................................... 139
C-3 Profile Parameters Description..................................................................... 140
D-1 Intel® Platform Trust Technology Configuration table...................................... 141
E-1 Kabylake-LP RVP Board Settings.................................................................. 142
E-2 Kabylake-H RVP Board Settings................................................................... 143
F-1 ISH Public Key Settings.............................................................................. 145
Intel Confidential
Revision Description Date
1.5 Beta Release: See change bars on the left side of the page January 2017
1.6 Removed RPMC references March 2017
Removed M3 Power Rail setting.
1.7 Changed Post Manufacturing NVAR Configuration Enabled default July 2017
Intel Confidential
Introduction
1 Introduction
This document covers the Intel® Management Engine Firmware (Intel® ME) 11.7 -
Consumer Firmware bring up procedure. Intel® ME is tied to essential platform
functionality — this dependency cannot be avoided for engineering reasons.
The bring up procedure primarily involves building a Serial Peripheral Interface (SPI)
Flash image that will contain:
• [required] Descriptor region — Contains sizing information for all other SPI Flash
image regions, SPI settings (including Vendor Specific Configuration - or VSCC -
tables, SPI device parameters), and region access permissions.
• [required] BIOS region — Contains firmware for the processor (or host) and/or
Embedded Controller (EC).
• [required] Intel® ME FW region — Contains firmware for the Intel® Management
Engine.
• [optional] GbE region — Contains firmware for Intel LAN solution.
For more details on SPI Flash layout, see the document Kabylake-H / LP SPI
Programming Guide SPI Programming Guide and Appendix A. Once the SPI Flash
image is built, it will be programmed to the target based platform and the platform will
be booted. This document also covers any tests and checks required to ensure that this
boot process is successful and that Intel® ME Consumer FW is operating as expected.
1.3 Prerequisites
Before this document is read and utilized, it is essential that the reader first review the
Consumer FW Release Notes (included with this Intel® ME Consumer FW kit).
Intel Confidential
Introduction
This document is constructed so that the reader can complete the bring up steps as
given for the Intel Customer Reference Board (CRB). However, in the case that bring up
is being performed on a different Intel® x based platform, this document will highlight
any changes that must be imposed onto the bring up steps accordingly.
This document makes only the following limited assumptions regarding hardware:
• The platform is Kabylake LP/H based
• The platform is equipped with one or more SPI Flash devices with a total capacity
sufficient for storing all relevant firmware images.
EC Embedded Controller
FW Firmware
OOB Out-of-Band
OS Operating System
Intel Confidential
Introduction
End User The person who uses the computer (either Desktop or Mobile). In
corporate, the user usually does not have administrator privileges.
Host or Host CPU The processor that is running the operating system. This is different
than the management processor running the Intel® Management
Engine Firmware.
Intel® Management Engine Interface between the Management Engine and the Host system
Interface (Intel® MEI)
Intel® MEI driver Intel® ME host driver that runs on the host and interfaces between ISV
Agents and the Intel® ME HW.
NVM Non-Volatile Memory: A type of memory that will retain its contents
even if power is removed. In the Intel® AMT current implementation,
this is achieved using a FLASH memory device.
OOB Interface Out Of Band interface: This is WSMAN interface over secure or non-
secure TCP protocol.
OS not Functional The Host OS is considered non-functional in Sx power state and any one
of the following cases when system is in S0 power state:
• OS is hung
• After PCI reset
• OS watch dog expires
• OS is not present
System States Operating System power states such as S0. See detailed definitions in
System States and Power Management section.
Intel Confidential
Introduction
CM0 Intel® Management Engine firmware power state where all hardware
power planes are activated. The host power state is S0.
CM3 Intel® Management Engine power state where the host is in Sx. The
processor DRAM Controller is turned off and DRAM power stays in off/
self refresh mode. There is no UMA usage in CM3 state. Less than 1MB
of SRAM used for code and data. Code is executed off of flash takes
~1mS.
CM0-PG Core Well Powered; Intel® ME Well Powered; (Intel® ME core not
consuming power) DRAM available.
OS Hibernate System state where the OS state is saved on the hard drive.
S0 A system state where power is applied to all HW devices and the system
is running normally.
S1, S2, S3 A system state where the host CPU is halted but power remains
available to the memory system (memory is in self-refresh mode).
S4 A system state where the host CPU and memory are not active.
S5 A system state where all power to the host system is off, however the
power cord (and/or battery in mobile designs) is still connected.
Snooze Mode Intel® Management Engine activities are mostly suspended to save
power. The Intel® Management Engine monitors HW activities and can
restore its activities depending on the HW event.
Standby System state where the OS state is saved in memory and resumed from
the memory when mouse/keyboard is clicked.
Kabylake Intel® Management Engine (Intel® ME) and Embedded Controller Interaction 549024 / CDI
Product Specification Revision 0.5
Note: * Unless specified otherwise, a document can be ordered by providing its reference number to your
Intel Field Applications Engineer.
Intel Confidential
Introduction
Decimal (default) d 14d. Note that any number without an explicit suffix can be
assumed to be decimal.
Binary b 1110b
Hex h 0Eh
Hex 0x 0x0E
Byte B 8 bits
Gigabyte GB 1024 MB
Intel Confidential
Introduction
Kabylake-H Client SPI Programming Guide.pdf How to program SPI device parameters and
descriptor region details. Also contains a
complete SPI Flash softstrap reference.
Kabylake-LP Client SPI Programming Guide.pdf How to program SPI device parameters and
descriptor region details. Also contains a
complete SPI Flash softstrap reference.
[Image Components]
[BIOS]
[Certificates]
[HDCP]
IntelProvisioning_Root_PublicKey.cer
SklDeviceProvCertProd.cer
IntelProvisioning_Root_PublicKey.cer
SklDeviceProvCertPreprod.cer
SklDeviceProvCertProd.cer
[GbE]
[ME]
ME_11.7_Consumer_D0_H_Production.bin
[Installers]
[ME_SW_MSI]
IntelMEFWVer.dll
Intel Confidential
Introduction
SetupME
WixLicenseNote.txt
IntelMEFWVer.dll
MEISetup
[Tools]
[ICC_Tools]
Intel® ME Firmware Integrated Clock Control (ICC) Tools ICC Tools User Guide
User Guide.pdf
[CCT]
cctDll.dll
[EFI]
[System Tools]
Open Watcom Public License.pdf Sybase Open Watcom Public License version 1.0
document.
[DOS]
[EFI64]
[Windows]
Idrvdll.dll
Intel Confidential
Introduction
Pmxdll.dll
[Windows64]
Idrvdll32e.dll
Pmxdll32e.dll
[FWUpdate]
[EFI64]
[DOS]
[Win]
[Win64]
[Win]
[MEInfo]
[DOS]
Idrvdll.dll
Pmxdll.dll
ISHLib.dll
[Windows64]
Idrvdll32e.dll
ISHLib.dll
Pmxdll32e.dll
[MEManuf]
[DOS]
Intel Confidential
Introduction
[EFI64]
[Windows]
Idrvdll.dll
Pmxdll.dll
ISHLib.dll
[Windows64]
Idrvdll32e.dll
ISHLib.dll
Pmxdll32e.dll
(empty)
Intel Confidential
Introduction
§§
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel® Flash Image Tool (Intel® FIT) can be used to generate either a full SPI Flash
binary image with Descriptor, GbE, BIOS, and Intel® ME Regions. Additionally, it can be
used to create a simple image containing only the Intel® ME Region only for use with
custom SPI Flash binary image assembly solutions. Use the steps shown in following
sections.
After this image has been created, it will need to be burned onto the target platform’s
SPI Flash device(s). Section 3, “Programming SPI Flash Devices and Checking
Firmware Status” later in this document provides steps to do this.
Note: The Flash Image Tool may be updated throughout the release cycles. As a general rule,
please ensure you use the tools, images and other content from the same kit and
refrain from using different version tools.
Intel Confidential
Image Creation: Intel® Flash Image Tool
This button labeled ‘New’ on rollover allows opening of a new session with default
1 New
values
2 Open This button labeled ‘Open’ on rollover allows opening of an xml or bin file
3 Save This button labeled ‘Save’ on rollover allows saving of xml file
4 Clear Console This button labeled ‘Clear Console’ clears the console area (see page 23)
This button labeled ‘Build Settings’ brings up the build settings popup Window see
5 Build Settings
(Table 2-2)
6 Build Image This button labeled ‘Build Image’ on rollover allows build of the image
Intel Confidential
Image Creation: Intel® Flash Image Tool
8 Drop Down Selector This drop down allows selection of SKU within platform selected
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
5
$WorkingDir and $DestDir can be left at the default ‘.’
Click on $SourceDir Value field and type in path where the Image
6 Components are located for the Manageability Engine kit
Intel Confidential
Image Creation: Intel® Flash Image Tool
These additional settings are under the Networking & Connectivity tab > Wired LAN Configuration. In the GPIO > LAN /
GPIO Select ensure the value is set correctly for board type.
Image Id - This displays Image ID of the currently loaded Intel® Integrated LAN
binary.
Major Version - This displays Major revision number of the currently loaded
Intel® Integrated LAN binary.
Minor Version - This displays Minor revision number of the currently loaded
Intel® Integrated LAN binary.
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
1
Number of Components KBL-Y 1
Values: 0, 1, 2 - This setting configures the total number of flash components for KBL-U 1
the platform. Note: Choosing a selection of '0' part will cause the Intel® FIT tool to KBL-H 1
build an output image containing only the Intel® ME region.
KBL-S 1
HEDT 1
Flash component 1 Size KBL-Y 8MB
Values: 512KB, 1MB, 2MB, 4MB, 8MB, 16MB, 32MB, 64MB - This setting KBL-U 16MB
determines the size of Flash component 1 for the platform image. KBL-H 16MB
KBL-S 16MB
HEDT 16MB
Flash component 2 Size KBL-Y 8MB
Values: 512KB, 1MB, 2MB, 4MB, 8MB, 16MB, 32MB, 64MB - This setting KBL-U 8MB
determines the size of Flash component 2 for the platform image. Note: This setting KBL-H 8MB
is only applicable when the Number of Flash Components option is set to '2'.
KBL-S 8MB
HEDT 8MB
SPI Voltage Select KBL-Y 3.3 Volts
Values: 1.8 Volts, 3.3 Volts - This strap sets the internal control signal on the pad KBL-U 3.3 Volts
for either 1.8 or 3.3 volts. See Kabylake H / LP SPI Programming Guide for further KBL-H 3.3 Volts
details.
KBL-S 3.3 Volts
HEDT 3.3 Volts
Click on Flash Settings in the left tabs menu> Host CPU/BIOS Master Access is expanded by default:
Intel Confidential
Image Creation: Intel® Flash Image Tool
3
Intel® ME Write Access KBL-Y 0xFFF
Values: 0xFFF, 0x004 - This setting determines write access control for the ME KBL-U 0xFFF
region. KBL-H 0xFFF
0xFFF = Debug/Manufacturing KBL-S 0xFFF
0x004 = Production HEDT 0XFFF
For further details on Region Access Control see Kabylake H / LP SPI Programming
guide further details.
Intel® ME Read Access KBL-Y 0xFFF
Values: 0xFFF, 0x00D - This setting determines read access control for the ME KBL-U 0xFFF
region. KBL-H 0xFFF
0xFFF = Debug/Manufacturing KBL-S 0xFFF
0x00D = Production HEDT 0XFFF
For further details on Region Access Control see Kabylake H / LP SPI Programming
guide further details.
Click on Flash Settings in the left tabs menu> GbE Master Access is expanded by default:
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
4
GbE Write Access KBL-Y 0xFFF
Values: 0xFFF, 0x008 - This setting determines write access control for the Gigabit KBL-U 0xFFF
Ethernet Region. KBL-H 0xFFF
0xFFF = Debug/Manufacturing KBL-S 0xFFF
0x008 = Production HEDT 0XFFF
For further details on Region Access Control see Kabylake H / LP SPI Programming
guide further details.
GbE Read Access KBL-Y 0xFFF
Values: 0xFFF, 0x009 - This setting determines read access control for the Gigabit KBL-U 0xFFF
Ethernet Region. KBL-H 0xFFF
0xFFF = Debug/Manufacturing KBL-S 0xFFF
0x009 = Production HEDT 0XFFF
For further details on Region Access Control see Kabylake H / LP SPI Programming
guide further details.
Click on Flash Settings in the left tabs menu> EC Master Access is expanded by default:
5
# Parameter Platform Settings
EC Write Access KBL-Y 0xFFF
Values: 0xFFF, 0x100 - This setting determines write access control for the KBL-U 0xFFF
Embedded Controller Region. KBL-H 0xFFF
0xFFF = Debug/Manufacturing KBL-S 0xFFF
0x100 = Production HEDT 0XFFF
For further details on Region Access Control see Kabylake H / LP SPI Programming
guide further details.
EC Read Access KBL-Y 0xFFF
Values: 0xFFF, 0x101, 0x103 - This setting determines read access control for the KBL-U 0xFFF
Embedded Controller Region. KBL-H 0xFFF
0xFFF = Debug/Manufacturing KBL-S 0xFFF
0x101 = Production HEDT 0XFFF
0x103 = Production with EC BIOS Read Access
For further details on Region Access Control see Kabylake H / LP SPI Programming
guide further details.
Intel Confidential
Image Creation: Intel® Flash Image Tool
6
Dual I/O Read Enabled KBL-Y No
Values: Yes/No - This setting allows the customer to enable support for Dual I/O KBL-U No
Read capabilities for flash components. See Kabylake H / LP SPI Programming guide KBL-H No
for further details.
KBL-S No
HEDT No
Dual Output Read Enabled KBL-Y Yes
Values: Yes/No - This setting allows the customer to enable support for Dual KBL-U Yes
Output Read capabilities for flash components. See Kabylake H / LP SPI KBL-H Yes
Programming guide for further details.
KBL-S Yes
HEDT Yes
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
8
Name - This setting allow the OEM input a name designation for each flash KBL-Y Winbond
component being used. Note: This is a free form entry field it does not affect actual KBL-U Winbond
flash component operation.
KBL-H Winbond
KBL-S Winbond
HEDT Winbond
Vendor ID - This configures the JEDEC vendor specific byte ID of the SPI flash KBL-Y 0xEF
component. See Kabylake H / LP SPI Programming guide for further details. KBL-U 0xEF
KBL-H 0xEF
KBL-S 0xEF
HEDT 0xEF
Device ID 0 - This configures the JEDEC device specific byte ID 0 of the SPI flash KBL-Y 0x40
component. See Kabylake H / LP SPI Programming guide for further details. KBL-U 0x40
KBL-H 0x40
KBL-S 0x40
HEDT 0x40
Device ID 1 - This configures the JEDEC device specific byte ID 1 of the SPI flash KBL-Y 0x18
component. See Kabylake H / LP SPI Programming guide for further details. KBL-U 0x18
KBL-H 0x18
KBL-S 0x18
HEDT 0x18
Intel Confidential
Image Creation: Intel® Flash Image Tool
9
Click on Flash Settings in the left tabs menu> BIOS Configuration is expanded by default:
11 Values: 64KB, 128KB, 256KB, 512KB, 1MB - This configures the Top Swap Block
size for the platform. For further details see Kabylake H / LP Platform Controller Hub
KBL-H
KBL-S
64KB
64KB
EDS.
HEDT 64KB
Intel Confidential
Image Creation: Intel® Flash Image Tool
1
Processor Emulation KBL-Y No Emulation
Values: No Emulation KBL-U No Emulation
EMULATE Intel® vPro (TM) capable Processor KBL-H EMULATE Intel®
EMULATE Intel® Core (TM) branded Processor vPro (TM) capable
Processor
EMULATE Intel® Celeron (R) branded Processor
EMULATE Intel®
EMULATE Intel® Pentium (R) branded Processor KBL-S
vPro (TM) capable
EMULATE Intel® Xeon (R) branded Processor Processor
EMULATE Intel® Xeon (R) Manageability capable Processor
This setting determines processor type to be emulated on pre-production silicon. HEDT EMULATE Intel®
Set this parameter to the type of processor that the target system will use during Core (TM)
production. This field will emulate that processor class for pre-production silicon. It branded
is necessary to set this to Emulate Intel® vPro™ Processor in order to enable Processor
Intel® AMT.
Missing Processor Detection Alert KBL-Y NA
Values: Yes/No - This setting determines if missing processor detection is KBL-U NA
enabled on Desktop / Workstation platforms. Note: This feature will only work if KBL-H No
the platform has the appropriate glue logic present.
KBL-S No
HEDT No
Click on Intel® ME Kernel in the left tabs menu> Intel® ME Firmware Update is expanded by default:
2
Firmware Update OEM ID - This setting allows configuration of an OEM unique ID KBL-Y 0 string
to ensure that customers can only update their platform with images from the OEM KBL-U 0 string
of the platform.
KBL-H 0 string
KBL-S 0 string
HEDT 0 string
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
3
ODM ID used by Intel® Services - This setting is for entering the ODM ID for KBL-Y 0x00000000
Intel® Services to identify the ODM Board builder. Note: This ID is either KBL-U 0x00000000
generated by or registered with Intel® Services Web servers.
KBL-H 0x00000000
KBL-S 0x00000000
HEDT 0x00000000
System Integrator ID used by Intel® Services - This setting is for entering the KBL-Y 0x00000000
System Integrator ID for Intel® Services to identify the System Integrator. Note: KBL-U 0x00000000
This ID is either generated by or registered with Intel® Services Web servers.
KBL-H 0x00000000
KBL-S 0x00000000
HEDT 0x00000000
Reserved ID used by Intel® Services - This setting is for entering the Reserved KBL-Y 0x00000000
ID for Intel® Services currently not used. KBL-U 0x00000000
KBL-H 0x00000000
KBL-S 0x00000000
HEDT 0x00000000
Click on Intel® ME Kernel in the left tabs menu> Image Identification is expanded by default:
4
OEM Tag - This is a free form 32bit field that allows the OEM to configure their own KBL-Y 0x00000000
unique identifier in the firmware image. KBL-U 0x00000000
KBL-H 0x00000000
KBL-S 0x00000000
HEDT 0x00000000
Intel Confidential
Image Creation: Intel® Flash Image Tool
5
MCTP Stack Configuration KBL-Y 0x920030
Defines the Intel® ME’s 8-bits MCTP Endpoint ID’s for each SMBus physical KBL-U 0x920030
interface (SMBus, SMLink0, and SMLink1). These values are needed for FW to KBL-H 0x920030
communicate with MCTP end points. For each of these 3 bytes, a value of 0x00
KBL-S 0x920030
means not used, and values 0xFF or 0x01 - 0x07 or 0x20 - 0x2F are not allowed.
HEDT 0x920030
MctpEspiEnabled KBL-Y No
Value: Yes/No KBL-U No
KBL-H No
KBL-S No
HEDT No
MctpDevicePortEc KBL-Y 0x0
KBL-U 0x0
KBL-H 0x0
KBL-S 0x0
HEDT 0x0
MctpDevicePortSio KBL-Y 0x00
KBL-U 0x00
KBL-H 0x00
KBL-S 0x00
HEDT 0x00
MctpDevicePortIsh KBL-Y 0x00
KBL-U 0x00
KBL-H 0x00
KBL-S 0x00
HEDT 0x00
MctpDevicePortBmc KBL-Y 0x00
KBL-U 0x00
KBL-H 0x00
KBL-S 0x00
HEDT 0x00
Intel Confidential
Image Creation: Intel® Flash Image Tool
6
Automatic Built in Self Test KBL-Y Disabled
Values: Enabled/Disabled KBL-U Disabled
This setting enables the firmware Automatic Built in Self Test which is executed KBL-H Disabled
during first platform boot after initial image flashing. KBL-S Disabled
HEDT Disabled
Click on Intel® ME Kernel in the left tabs menu> Post Manufacturing Lock is expanded by default:
Intel Confidential
Image Creation: Intel® Flash Image Tool
7
Post Manufacturing NVAR Configuration Enabled KBL-Y Yes
Values: Yes/No KBL-U Yes
This setting determines if modifications to Customer configurable NVARs is to be KBL-H Yes
allowed after close of manufacturing. KBL-S Yes
HEDT Yes
Click on Intel® ME Kernel in the left tabs menu> Reserved is expanded by default:
8
Reserved KBL-Y No
Values: Yes/No KBL-U No
KBL-H No
KBL-S No
HEDT No
Intel Confidential
Image Creation: Intel® Flash Image Tool
1
Intel® AMT Supported KBL-Y No
Values: Yes/No - This setting allows customers to disable Intel® AMT on the KBL-U No
platform and force the platform into Standard Manageability mode. Note: If this KBL-H No
setting has been set to disabled Intel® AMT cannot be re-enabled once the
KBL-S No
descriptor has been locked. This setting applies to Desktop and Workstation only.
HEDT No
Intel® ME Network Services Supported KBL-Y Yes
Values: Yes/No - This setting allows customers to enable / disable Intel® ME KBL-U Yes
Network Services on the platform. Note: This setting and TLS needs to be KBL-H Yes
enabled for proper operation of Intel® Authenticate (Corporate Only). In addition
KBL-S Yes
if this setting is disabled Intel® AMT will also be disabled.
HEDT No
Intel® Manageability Application Supported KBL-Y No
Values: Yes/No - This setting allows customers to force Intel® AMT enabled KBL-U No
platforms to operate in Standard Manageability mode. Note: This setting only KBL-H No
applies to Desktop and Workstation platforms.
KBL-S No
HEDT No
Manageability Application initial power-up state KBL-Y Disabled
Values: Enabled/Disabled KBL-U Disabled
This setting allows customers to determine the power up state for Intel® AMT or KBL-H Disabled
Standard Manageability. Note: If this setting is disabled Intel® AMT or Standard KBL-S Disabled
Manageability can still be re-enabled through the Intel® MEBx interface.
HEDT Disabled
Intel® AMT Idle Timeout KBL-Y 0xFFFF
Values: 0xFFFF - This setting configures the idle timeout value before Intel® KBL-U 0xFFFF
AMT enters into an off state. KBL-H 0xFFFF
KBL-S 0xFFFF
HEDT NA
Intel® AMT Watchdog Automatic Reset Enabled KBL-Y No
Values: Yes/No - This setting allows customers to enable the Intel® ME KBL-U No
firmware to trigger an automatic platform reset if either the MEI or Agent KBL-H No
Presence are in a hung state. Note: This feature only allows one reset at a time
KBL-S No
when the watchdog expires. After this feature has triggered a reset, it must be
re-armed for reuse via management console. HEDT No
Intel Confidential
Image Creation: Intel® Flash Image Tool
2
Firmware KVM Screen Blanking KBL-Y No
Values: Yes/No - This setting enables KVM Screen blanking capabilities in the KBL-U No
firmware image. Note: This feature is dependent on processor level support. KBL-H No
KBL-S No
HEDT No
KVM Redirection Supported KBL-Y Yes
Values: Yes/No - This setting allows OEMs to enable / disable the KVM KBL-U Yes
Redirection capabilities of the firmware. Note: If this setting has been set to KBL-H Yes
disabled it cannot be re-enabled once the descriptor has been locked.
KBL-S Yes
HEDT No
Click on Intel® AMT in the left tabs menu> Provisioning Configuration is expanded by default:
3
Embedded Host Based Configuration KBL-Y No
Values: Yes/No - This setting allows customers to enable / disable Embedded KBL-U No
Host Based Configuration. Important - EHBC is primarily intended for use in KBL-H No
embedded systems as it offers less user privacy/security protection than may be
KBL-S No
appropriate for business client systems.
HEDT NA
Note: The Intel® FIT tool will not adjust the Redirection Privacy/Security value
based on selection here. Please set security level as needed.
PKI Domain Name Suffix - This setting allow OEMs to pre-configure the
Domain Name Suffix used for PKI provisioning in their firmware image. Note:
For normal out-of-box provisioning functionality this setting should be left empty.
Intel Confidential
Image Creation: Intel® Flash Image Tool
4
Certificate Enabled KBL-Y No
Values: Yes/No - This setting allows customers to enable PKI provisioning KBL-U No
Custom Certificate 1. KBL-H No
KBL-S No
HEDT NA
Certificate Friendly Name - This setting allows customers to assign a user
friendly name for PKI provisioning Custom Certificate 1. Maximum of 32
characters.
Certificate Stream - This setting allows customers to input hash stream for PKI
provisioning Custom Certificate 1. If enabled the certificate will be used in
addition to those already pre-loaded in base firmware during provisioning. Note:
If the platform is un-configured the Custom Certificate Hash will be deleted.
Click on Intel® AMT in the left tabs menu> OEM Customizable Certificate 2 is expanded by default:
5
Certificate Enabled KBL-Y No
Values: Yes/No - This setting allows customers to enable PKI provisioning KBL-U No
Custom Certificate 2. KBL-H No
KBL-S No
HEDT NA
Certificate Friendly Name - This setting allows customers to assign a user
friendly name for PKI provisioning Custom Certificate 2. Maximum of 32
characters.
Certificate Stream - This setting allows customers to input hash stream for PKI
provisioning Custom Certificate 2. If enabled the certificate will be used in
addition to those already pre-loaded in base firmware during provisioning. Note:
If the platform is un-configured the Custom Certificate Hash will be deleted.
Intel Confidential
Image Creation: Intel® Flash Image Tool
6
Certificate Enabled KBL-Y No
Values: Yes/No - This setting allows customers to enable PKI provisioning KBL-U No
Custom Certificate 3. KBL-H No
KBL-S No
HEDT NA
Certificate Friendly Name - This setting allows customers to assign a user
friendly name for PKI provisioning Custom Certificate 3. Maximum 32 characters.
Certificate Stream - This setting allows customers to input hash stream for PKI
provisioning Custom Certificate 3. If enabled the certificate will be used in
addition to those already pre-loaded in base firmware during provisioning. Note:
If the platform is un-configured the Custom Certificate Hash will be deleted.
Click on Intel® AMT in the left tabs menu> OEM Default Certificate 1 is expanded by default:
7
Certificate Enabled KBL-Y No
Values: Yes/No - This setting allows customers to enable PKI provisioning KBL-U No
Default certificate 1. KBL-H No
KBL-S No
HEDT NA
Certificate Friendly Name - This setting allows customers to assign a user
friendly name for PKI provisioning Default Certificate 1. Maximum 32 characters.
Certificate Stream - This setting allows customers to input hash stream for PKI
provisioning custom certificate 1. Note: Default Certificates if enabled will be
used in addition to those already pre-loaded in firmware during provisioning.
Unlike Customizable Certificates the Default Certificates are not deleted when
the platform is un-provisioned.
Intel Confidential
Image Creation: Intel® Flash Image Tool
8
Certificate Enabled KBL-Y No
Values: Yes/No - This setting allows customers to enable PKI provisioning KBL-U No
Default certificate 2. KBL-H No
KBL-S No
HEDT NA
Certificate Friendly Name - This setting allows customers to assign a user
friendly name for PKI provisioning Default Certificate 2. Maximum 32 characters.
Certificate Stream - This setting allows customers to input hash stream for PKI
provisioning custom certificate 2. Note: Default Certificates if enabled will be
used in addition to those already pre-loaded in firmware during provisioning.
Unlike Customizable Certificates the Default Certificates are not deleted when
the platform is un-provisioned.
Click on Intel® AMT in the left tabs menu> OEM Default Certificate 3 is expanded by default:
9
Certificate Enabled KBL-Y No
Values: Yes/No - This setting allows customers to enable PKI provisioning KBL-U No
Default certificate 3. KBL-H No
KBL-S No
HEDT NA
Certificate Friendly Name - This setting allows customers to assign a user
friendly name for PKI provisioning Default Certificate 3. Maximum 32 characters.
Certificate Stream - This setting allows customers to input hash stream for PKI
provisioning custom certificate 3. Note: Default Certificates if enabled will be
used in addition to those already pre-loaded in firmware during provisioning.
Unlike Customizable Certificates the Default Certificates are not deleted when
the platform is un-provisioned.
Intel Confidential
Image Creation: Intel® Flash Image Tool
10
Certificate Enabled KBL-Y No
Values: Yes/No - This setting allows customers to enable PKI provisioning KBL-U No
Default certificate 4. KBL-H No
KBL-S No
HEDT NA
Certificate Friendly Name - This setting allows customers to assign a user
friendly name for PKI provisioning Default Certificate 4.
Certificate Stream - This setting allows customers to input hash stream for PKI
provisioning custom certificate 4. Note: Default Certificates if enabled will be
used in addition to those already pre-loaded in firmware during provisioning.
Unlike Customizable Certificates the Default Certificates are not deleted when
the platform is un-provisioned.
Click on Intel® AMT in the left tabs menu> OEM Default Certificate 5 is expanded by default:
11
Certificate Enabled KBL-Y No
Values: Yes/No - This setting allows customers to enable PKI provisioning KBL-U No
Default certificate 5. KBL-H No
KBL-S No
HEDT NA
Certificate Friendly Name - This setting allows customers to assign a user
friendly name for PKI provisioning Default Certificate 5.
Certificate Stream - This setting allows customers to input hash stream for PKI
provisioning custom certificate 5. Note: Default Certificates if enabled will be
used in addition to those already pre-loaded in firmware during provisioning.
Unlike Customizable Certificates the Default Certificates are not deleted when
the platform is un-provisioned.
Intel Confidential
Image Creation: Intel® Flash Image Tool
12
Redirection Localized Language - This setting allows customers to configure KBL-Y English
which localized language will be used initially by firmware for user consent KBL-U English
output information (Examples: May be displayed before SOL / KVM session
KBL-H English
starts).
KBL-S English
HEDT NA
Redirection Privacy / Security Level - This setting allows customers to KBL-Y Default
configure the Privacy and Security level for redirection operations. KBL-U Default
Default enables all redirection ports (User consent is configurable). KBL-H Default
Enhanced - Enables all redirection ports. (User consent is required and cannot KBL-S Default
be disabled).
HEDT NA
Extreme - Disables Redirection and Remote Configuration / Client Control Mode.
Note: The Intel® FIT tool will not adjust the Embedded Host Based
Configuration value based on selection here. Please set EHBC to yes or no as
needed.
Click on Intel® AMT in the left tabs menu> TLS Configuration is expanded by default:
13
# Parameter Platform Settings
Transport Layer Security Supported KBL-Y Yes
Values: Yes/No - This setting allows customers to enable / disable firmware KBL-U Yes
Transport Layer Security support. Note: If this is disabled TLS will be KBL-H Yes
permanently disabled in the firmware image. This setting needs to be enabled
KBL-S Yes
along with along with the Intel® ME Network Services Supported for proper
operation of the Intel® Authenticate (Corporate Only) feature. HEDT NA
Intel Confidential
Image Creation: Intel® Flash Image Tool
1
PAVP Supported KBL-Y Yes
Values: Yes/No KBL-U Yes
This setting determines if the Protected Audio Video Path (PAVP) feature will be KBL-H Yes
permanently disabled in the FW image. KBL-S Yes
HEDT NA
LSPCON Internal Display Port 1 - LSPCON / 4K KBL-Y None
Values: None, Port B, Port C, Port D KBL-U None
This setting determines which port for LSPCON will be connected to the HDCP 2.2 KBL-H None
bridge adapter Display 1. KBL-S None
HEDT NA
HDCP Internal Display Port 1 - 5K KBL-Y None
Values: None, Port A, Port B, Port C, Port D KBL-U None
This setting determines which port is connected for 5K output on the Internal KBL-H None
Display 1. KBL-S None
Note: HEDT NA
Both Display Port 1 & 2 need to be configured for proper operation.
Click on Platform Protection in the left tabs menu> Graphics uController is expanded by default:
Intel Confidential
Image Creation: Intel® Flash Image Tool
2
GuC Encryption Key KBL-Y 0x00000000
Values: This option is for entering the raw hash 256 bit string or certificate file for KBL-U 0x00000000
the Graphics uController. KBL-H 0x00000000
KBL-S 0x00000000
HEDT NA
Click on Platform Protection in the left tabs menu> Hash Key Configuration for Bootguard / ISH is expanded by default:
3
OEM Public Key Hash KBL-Y 0x00000000
Values: This option is for entering the raw hash string or certificate file for Boot KBL-U 0x00000000
Guard and ISH. This 256-bit field represents the SHA-256 hash of the OEM public KBL-H 0x00000000
key corresponding to the private key used to sign the BIOS-SM or ISH image.
KBL-S 0x00000000
Please see Appendix F for further details.
HEDT 0x00000000
Click on Platform Protection in the left tabs menu> Boot Guard Configuration is expanded by default:
4
Key Manifest ID KBL-Y 0x0
Values: This option is for entering the hash of another public key, used by the KBL-U 0x0
ACM to verify the Boot Policy Manifest. KBL-H 0x0
KBL-S 0x0
HEDT 0x0
Intel Confidential
Image Creation: Intel® Flash Image Tool
5
Intel® PTT initial power-up state KBL-Y Enabled
Values: Enabled/Disabled - This setting determines if Intel® PTT is enabled on KBL-U Enabled
platform power-up. KBL-H Enabled
KBL-S Disabled
HEDT Disabled
Intel® PTT Supported KBL-Y Yes
Values: Yes/No - This setting permanently disables Intel® PTT in the firmware KBL-U Yes
image. KBL-H Yes
KBL-S Yes
HEDT Yes
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
6
TPM Clock Frequency KBL-Y 17MHz
Values: 17MHz, 30MHz, 48MHz - This setting determines the clock frequency KBL-U 17MHz
setting to be used for the TPM over SPI bus. KBL-H 17MHz
KBL-S 17MHz
HEDT 17MHz
TPM Over SPI Bus Enabled KBL-Y No
Values: Yes/No - This setting determines if TPM over SPI bus is enabled on the KBL-U No
platform. KBL-H No
KBL-S No
HEDT No
Intel Confidential
Image Creation: Intel® Flash Image Tool
1
Register Lock Policy KBL-Y 0: Default
Values: 0:Default, 1:All Locked, 2: All Unlocked KBL-U 0: Default
This parameter controls Register lock policy. It defines the integrated clock KBL-H 0: Default
registers left accessible to host after EOP. KBL-S 0: Default
0:Default - Locks all but the registers associated to adjust BCLK nominal HEDT 0: Default
clock frequency and spread settings.
1:All Locked - Locks all integrated clock registers and disables all writes
to these registers via Intel® ME Firmware.
2:All Unlocked - Leaves pre-EOP integrated clock registers unlocked.This
option is mainly used for debug purpose.
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
User can add up to maximum 16 profiles.To add new profile, please use
“Integrated Clock Controller | Profiles - + Add Profile Button”
Profile Name KBL-Y Profile 0
KBL-U Profile 0
This parameter allows user to customize profile name for easy KBL-H Profile 0
identification. By default it uses pre-defined profile name like Profile 0. KBL-S Profile 0
HEDT Profile 0
Intel Confidential
Image Creation: Intel® Flash Image Tool
This parameter indicates which pre- defined profile selected for each
profile#.
Intel Confidential
Image Creation: Intel® Flash Image Tool
4
BCLK Clock Frequency - This parameter allows user to select the nominal KBL-Y
frequency for the selected clock. Range is limited based on the Clock Range KBL-U
Definition record and HW SKU.
KBL-H
Standard Setting Profile Type - Option is grayed out.
KBL-S
Adaptive Setting Profile Type - Option is able to be edited.
HEDT
Overclocking Setting Profile Type - Option is able to be edited.
Overclocking Plus Setting Profile Type - Option is able to be edited.
Overclocking Ext. Setting Profile Type - Option is able to be edited.
BCLK Spread Setting - This parameter allows user to select the KBL-Y
percentage of Spread setting for the selected clock. Range is limited based KBL-U
on the Clock Range Definition record and HW SKU.
KBL-H
BCLK Clock Frequency
KBL-S
Standard Setting Profile Type - Option is grayed out.
HEDT
Adaptive Setting Profile Type - Option is able to be edited.
Overclocking Setting Profile Type - Option is able to be edited.
Overclocking Plus Setting Profile Type - Option is able to be edited.
Overclocking Ext. Setting Profile Type - Option is able to be edited.
Click on Integrated Clock Controller in the left tabs menu> Profiles >Profile> Clock Range Definition Record is
expanded by default:
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
BCLK SSC Changes Allowed - This parameter allows user to specify if the KBL-Y
spread mode and percentage is allowed to be modified at runtime or not. if KBL-U
set to “True’: Runtime modification is allowed.
KBL-H
Standard Setting Profile Type - Option is grayed out.
KBL-S
Adaptive Setting Profile Type - Option is able to be edited.
HEDT
Overclocking Setting Profile Type - Option is able to be edited.
Overclocking Plus Setting Profile Type - Option is able to be edited.
Overclocking Ext. Setting Profile Type - Option is able to be edited.
BCLK SSC Halt Allowed - This parameter allows user to select if the KBL-Y
spread generator can be disabled at runtime or not.if set to “True”, the KBL-U
spread generator can be enabled and disabled at runtime.
KBL-H
Standard Setting Profile Type - Option is grayed out.
KBL-S
Adaptive Setting Profile Type - Option is able to be edited.
HEDT
Overclocking Setting Profile Type - Option is able to be edited.
Overclocking Plus Setting Profile Type - Option is able to be edited.
Overclocking Ext. Setting Profile Type - Option is able to be edited.
BCLK SSC Percentage - This parameter Specifies the maximum KBL-Y
percentage of spread adjustment that can be applied to the clock. Value is KBL-U
specified in 1/100th of percent(50=0.5%)
KBL-H
Standard Setting Profile Type - Option is grayed out.
KBL-S
Adaptive Setting Profile Type - Option is able to be edited.
HEDT
Overclocking Setting Profile Type - Option is able to be edited.
Overclocking Plus Setting Profile Type - Option is able to be edited.
Overclocking Ext. Setting Profile Type - Option is able to be edited.
Click on Integrated Clock Controller in the left tabs menu> Profiles >Profile> Clock Output Configuration is
expanded by default:
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
7
Configuring CLKREQ# and assigning GPIO depends on how CLKOUT_SRCx
configuration via FIT is done (Enabled or Disabled) and if CLKREQ is
required or not.
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
1
GbE MAC SMBus Address KBL-Y 0x70
KBL-U 0x70
KBL-H 0x70
KBL-S 0x70
HEDT 0x70
GbE SMBus Address Enabled KBL-Y Yes
Values: Yes/No - This enables the Intel® Integrated Wired LAN MAC KBL-U Yes
SMBus address. Note: This setting must be enabled if using Intel® KBL-H Yes
Integrated LAN.
KBL-S Yes
HEDT Yes
Intel® PHY over PCIe Enabled KBL-Y Yes
Values: Yes/No - This setting allows customers to enable / disable Intel® KBL-U Yes
Integrated LAN operation over the PCIe Port selected by the GbE PCIe Port KBL-H Yes
Select option.
KBL-S Yes
HEDT Yes
GbE PCIe Port Select KBL-Y PORT5
Values: PORT3, PORT4, PORT5, PORT9, PORT10 - This setting allows KBL-U PORT4
customers to configure the PCIe Port that will Intel® Integrated LAN will KBL-H PORT4
operate on.
KBL-S PORT4
HEDT PORT4
GbE PHY SMBus Address KBL-Y 0x64
This setting configures Intel® Integrated Wired LAN SMBus address to KBL-U 0x64
accept SMBus cycles from the MAC. Note: Recommended setting is 64h. KBL-H 0x64
KBL-S 0x64
HEDT 0x64
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
2
CLINK Enabled KBL-Y
Values: Yes/No - This setting allows customers to enable / disable the KBL-U
Wireless LAN CLINK signal through Intel® ME firmware. Note: For using KBL-H
Intel® vPro™ Wireless solutions this should be set to "Yes".
KBL-S
HEDT No
MLK_RSTB Buffer Driven Mode KBL-Y NA
Values: Open-drained/Driven - This soft strap determines the control KBL-U NA
mode for the output buffer MLK_RST # signal. KBL-H Driven
KBL-S Driven
HEDT NA
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
1
Intel® RST for PCIe-C1 Select x2 or x4 KBL-Y NA
Values: x2, x4 - This is used to configure NAND Cycle routers for the KBL-U NA
Intel® RST for PCIe interface as either x2 or x4 lane operation on PCIe KBL-H x2
Controller 1.
KBL-S x2
HEDT x4
Intel® RST for PCIe-C2 Select x2 or x4 KBL-Y x2
Values: x2, x4 - This is used to configure NAND Cycle routers for the KBL-U x2
Intel® RST for PCIe interface as either x2 or x4 lane operation on PCIe KBL-H x2
Controller 2.
KBL-S x2
HEDT x2
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
2
PCIe Controller 1 Lane Reversal Enabled KBL-Y No
Values: Yes/ No - This setting allows the PCIe lanes on Controller 1 to KBL-U No
be reversed. Note: Refer to EDS for PCIe supported port KBL-H No
configurations. KBL-S No
HEDT No
PCIe Controller 2 Lane Reversal Enabled KBL-Y No
Values: Yes/ No - This setting allows the PCIe lanes on Controller 2 to KBL-U No
be reversed. Note: Refer to EDS for PCIe supported port KBL-H No
configurations. KBL-S No
HEDT No
PCIe Controller 3 Lane Reversal Enabled KBL-Y No
Values: Yes/ No - This setting allows the PCIe lanes on Controller 3 to KBL-U Yes
be reversed. Note: Refer to EDS for PCIe supported port KBL-H No
configurations. KBL-S No
HEDT No
PCIe Controller 4 Lane Reversal Enabled KBL-Y NA
Values: Yes/ No - This setting allows the PCIe lanes on Controller 4 to KBL-U NA
be reversed. Note: Refer to EDS for PCIe supported port KBL-H No
configurations. KBL-S No
HEDT No
PCIe Controller 5 Lane Reversal Enabled KBL-Y NA
Values: Yes/ No - This setting allows the PCIe lanes on Controller 5 to KBL-U NA
be reversed. Note: Refer to EDS for PCIe supported port KBL-H No
configurations. KBL-S No
HEDT No
PCIe Controller 6 Lane Reversal Enabled KBL-Y NA
Values: Yes/ No - This setting allows the PCIe lanes on Controller 6 to KBL-U NA
be reversed. Note: Refer to EDS for PCIe supported port KBL-H No
configurations. KBL-S No
HEDT Yes
Click on Flex I/O in the left tabs menu> PCIe Port Configuration is expanded by default:
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
8
XHCI Port 1 Ownership KBL-Y XHCI
Values: XHCI, Non-XHCI - This setting configures USB3 Port 1 to KBL-U XHCI
operate as either XHCI or Non-XHCI. For further details on Flex I/O see KBL-H XHCI
Kabylake H / LP Platform Controller Hub EDS.
KBL-S XHCI
HEDT XHCI
XHCI Port 2 Ownership KBL-Y XHCI
Values: XHCI, Non-XHCI - This setting configures USB3 Port 2 to KBL-U XHCI
operate as either XHCI or Non-XHCI. For further details on Flex I/O see KBL-H XHCI
Kabylake H / LP Platform Controller Hub EDS.
KBL-S XHCI
HEDT Non-XHCI
XHCI Port 3 Ownership KBL-Y XHCI
Values: XHCI, Non-XHCI - This setting configures USB3 Port 3 to KBL-U XHCI
operate as either XHCI or Non-XHCI. For further details on Flex I/O see KBL-H XHCI
Kabylake H / LP Platform Controller Hub EDS.
KBL-S XHCI
HEDT
XHCI Port 4 Ownership KBL-Y XHCI
Values: XHCI, Non-XHCI - - This setting configures USB3 Port 4 to KBL-U XHCI
operate as either XHCI or Non-XHCI. For further details on Flex I/O see KBL-H XHCI
Kabylake H / LP Platform Controller Hub EDS.
KBL-S XHCI
HEDT
XHCI Port 5 Ownership KBL-Y Non-XHCI
Values: XHCI, Non-XHCI - This setting configures USB3 Port 5 to KBL-U XHCI
operate as either XHCI or Non-XHCI. For further details on Flex I/O see KBL-H Non-XHCI
Kabylake H / LP Platform Controller Hub EDS.
KBL-S XHCI
HEDT
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
3
eSPI / EC Boot Enabled KBL-Y Yes
Values: Yes/No KBL-U Yes
KBL-H Yes
KBL-S Yes
HEDT N/A
eSPI / EC Bus Frequency KBL-Y 60MHz
20MHz, 24MHz, 30MHz, 40MHz, 60MHz KBL-U 60MHz
KBL-H 60MHz
KBL-S 60MHz
HEDT N/A
eSPI / EC CRC Check Enabled KBL-Y No
Values: Yes/No KBL-U No
KBL-H No
KBL-S No
HEDT N/A
eSPI / EC Max Outstanding Requests for Master Attached Flash KBL-Y 2
Channel KBL-U 2
Values: 1, 2 KBL-H 2
KBL-S 2
HEDT N/A
eSPI / EC Max Read Request Payload size for Master Attached KBL-Y 64 bytes
Flash Channel KBL-U 64 bytes
Values: 64 bytes, 128 bytes, 256 bytes, 512 bytes, 1024 bytes, KBL-H 64 bytes
2048 bytes, 4096 bytes
KBL-S 64 bytes
HEDT N/A
eSPI / EC Max Read Request Payload size for OOB Channel KBL-Y 64 bytes
Values: 64 bytes, 128 bytes, 256 bytes, 512 bytes, 1024 bytes, KBL-U 64 bytes
2048 bytes, 4096 bytes KBL-H 64 bytes
KBL-S 64 bytes
HEDT N/A
eSPI / EC Max Read Request Payload size for Peripheral Channel KBL-Y 64 bytes
Values: 64 bytes, 128 bytes, 256 bytes, 512 bytes, 1024 bytes, KBL-U 64 bytes
2048 bytes, 4096 bytes KBL-H 64 bytes
KBL-S 64 bytes
HEDT N/A
eSPI / EC Max Virtual Wire Channels KBL-Y 8
Values: 8, 4, 2, 1 KBL-U 8
KBL-H 8
KBL-S 8
HEDT N/A
eSPI / EC Maximum I/O Mode KBL-Y Single, Dual and Quad
Values: Single, Single and Dual, Single and Quad, Single Dual and KBL-U Single, Dual and Quad
Quad KBL-H Single, Dual and Quad
KBL-S Single, Dual and Quad
HEDT N/A
eSPI / EC OOB Channel Enabled KBL-Y Yes
Values: Yes/No KBL-U Yes
KBL-H Yes
KBL-S Yes
HEDT N/A
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
4
APWROK Timing KBL-Y 2 ms
Values: 2ms, 4ms, 8ms, 16ms - This soft strap determines the time KBL-U 2 ms
between the SLP_A# pin de-asserting and the APWROK timer expiration. KBL-H 2 ms
For further details see Kabylake H / LP Platform Controller Hub EDS.
KBL-S 2 ms
HEDT 2 ms
PCH clock output stable to PROCPWRGD high (tPCH45) KBL-Y 100 ms
Values: 100ms, 50ms, 5ms, 1ms - This setting configures the KBL-U 100 ms
minimum timing from XCK_PLL locked to CPUPWRGD high. For further KBL-H 100 ms
details see Kabylake H / LP Platform Controller Hub EDS.
KBL-S 100 ms
HEDT 100 ms
PCIe Power Stable Timer (tPCH33) KBL-Y Disabled
Values: Enabled/Disabled - This setting configures the enables / KBL-U Disabled
disables the t36 timer. When enabled PCH will count 99ms from PWROK KBL-H Disabled
assertion before PLTRST# is de-asserted. Note: The recommended
KBL-S Disabled
setting is "Disabled".
HEDT Disabled
PROCPWRGD and SYS_PWROK high to SUS_STAT# de-assertion KBL-Y 1 ms
(tPCH46) KBL-U 1 ms
Values: 1ms, 2ms, 5ms - This setting configures the minimum timing KBL-H 1 ms
from CPUPWRGD assertion to SUS_STAT#. For further details see
KBL-S 1 ms
Kabylake H / LP Platform Controller Hub EDS.
HEDT 1 ms
Time Stamp Counter Clear on Warm Reset KBL-Y NA
Values: Yes/No - When set to ‘Yes’ causes PCH to clear the Time Stamp KBL-U NA
Counter when a Warm Reset is performed. KBL-H No
KBL-S No
HEDT No
Intel Confidential
Image Creation: Intel® Flash Image Tool
5
Intel® SMBus ASD Address Enable KBL-Y No
Values: Yes/No - This setting enables / disables the Intel® SMBus Alert KBL-U No
Sending Device. For details see Kabylake H / LP SPI Programming guide KBL-H No
for further details.
KBL-S No
HEDT No
Intel® SMBus ASD Address - This setting configures the Intel® SMBus KBL-Y 0x00000000
Alert Sending Device Address. For details see Kabylake H / LP SPI KBL-U 0x00000000
Programming guide for further details.
KBL-H 0x00000000
KBL-S 0x00000000
HEDT 0x00000000
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
1
LAN PHY Power Control GPD11 Signal Configuration KBL-Y LANPHYPC
KBL-U LANPHYPC
KBL-H LANPHYPC
KBL-S LANPHYPC
HEDT LANPHYPC
Click on GPIO in the left tabs menu> WLAN / GPIO Select is expanded by default:
2
SLP_WLAN# / GPD9 Signal Configuration KBL-Y SLP_WLAN#
KBL-U SLP_WLAN#
KBL-H SLP_WLAN#
KBL-S SLP_WLAN#
HEDT GDP9
Click on GPIO in the left tabs menu> Platform Power / GPIO is expanded by default:
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
4
NFC Reset GPIO Select
NFC must be enabled in the Networking and Connectivity section to
configure this setting.
NFC IRQ GPIO Select
NFC must be enabled in the Networking and Connectivity section to
configure this setting.
NFC DFU GPIO Select
NFC must be enabled in the Networking and Connectivity section to
configure this setting.
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
2
Deep Sx Enabled KBL-Y Yes
Values: Yes/ No - This setting enables / disables support for Deep Sx KBL-U Yes
operation. For further details see Kabylake H / LP Platform Controller Hub EDS. KBL-H Yes
Note: Support for Deep Sx is board design dependent.
KBL-S Yes
HEDT Yes
Intel Confidential
Image Creation: Intel® Flash Image Tool
1
Integrated Sensor Hub Supported KBL-Y
Values: Yes/No KBL-U
This setting allows customers to disable ISH on the platform. KBL-H
KBL-S
HEDT
Integrated Sensor Hub Power Up State KBL-Y
Values: Enabled/Disabled KBL-U
Field is enabled for editing if “Integrated Sensor Hub Supported” field KBL-H
above is set to “Yes”. This setting allows customers to determine the KBL-S
power up state for ISH.
HEDT
Integrated Sensor Hub Signing Policy KBL-Y
Values: OEM/Intel, OEM KBL-U
This setting determines ISH signing will be checked against the Intel KBL-H
provisioned hash included in the base image or OEM public key hash KBL-S
provisioned on the platform.
HEDT
Click on Integrated Sensor Hub in the left tabs menu> ISH Image is expanded by default:
2
Length - Total size (in bytes) of the ISH code partition including
reserved space. It is recommended to be at least 256kb.
Intel Confidential
Image Creation: Intel® Flash Image Tool
HEDT
Intel Confidential
Image Creation: Intel® Flash Image Tool
3
PDT Binary File KBL-Y Path for PDT Binary file
KBL-U Path for PDT Binary file
KBL-H Path for PDT Binary file
KBL-S Path for PDT Binary file
HEDT
Intel Confidential
Image Creation: Intel® Flash Image Tool
Debug Override Pre-Production Silicon - Allows the OEM to control FW KBL-Y 0x00000000
features to assist with pre-production platform debugging. This control has no KBL-U 0x00000000
effect if used on production silicon.
KBL-H 0x00000000
Bit 0: Disable DRAM_INIT_DONE (default timeout 60 seconds)
KBL-S 0x00000000
Bit 1: Disable Host Reset Timer
HEDT 0x00000000
Bit 2: Disable CPU_RESET_DONE timeout
Bit 3: Reserved
Bit 4: Disable Intel® ME Power Gating
Bit 5: Reserved
Bit 6: Secure Boot debug hook. Used to shorten wait time before ENF shutdown.
Bit 7: Force real FPFs on preproduction (default is to use flash)
Bit 8: Secure Boot debug hook. Used to reduce S3 or FFS optimization tries.
Bit 9: Reserved
Bit 10: Override power package to always enter M3.
Note: Certain options do not work when the descriptor is locked.
Debug Override Production Silicon - Allows the OEM to control FW features to KBL-Y 0x00000000
assist with production platform debugging. KBL-U 0x00000000
Bit 0: Extend DRAM_INIT_DONE timeout to 30 minutes (default timeout 15 KBL-H 0x00000000
seconds)
KBL-S 0x00000000
Bit 1: Disable Host Reset Timer
HEDT 0x00000000
Bit 2: Disable CPU_RESET_DONE timeout
Note: Certain options do not work when the descriptor is locked.
Enable Intel® ME Reset Capture on CLR_RST# KBL-Y No
Values: Yes/No - This setting configures Intel® ME behavior when it resets KBL-U No
during CL_RST#1. Note: The recommended default for this setting is "No". KBL-H No
KBL-S No
HEDT No
Firmware ROM Bypass KBL-Y No
Values: Yes/No - This setting enables / disables firmware ROM bypass. Note: KBL-U No
This setting only has affect when the firmware being used has ROM Bypass code KBL-H No
present.
KBL-S No
HEDT No
Click on Debug in the left tabs menu> Direct Connection Interface Configuration is expanded by default:
Intel Confidential
Image Creation: Intel® Flash Image Tool
2
Direct Connect Interface (DCI) Enabled KBL-Y No
Values: Yes/No - This setting enables / disables the DCI interface used for KBL-U No
Intel® Trace Hub debugging. KBL-H No
KBL-S No
HEDT No
Click on Debug in the left tabs menu> Intel® Trace Hub Technology is expanded by default:
3
Intel® Trace Hub Emergency Mode Enabled KBL-Y No
Values: Yes/No - This setting enable / disables Intel® Trace Hub in the firmware KBL-U No
base image. KBL-H No
KBL-S No
HEDT No
Intel® Trace Hub Soft Enabled KBL-Y No
Values: Yes/No - This setting configures the Intel® Trace Hub soft enable. KBL-U No
Note: When enabling this setting you also need to enable Intel® Trace Hub Debug KBL-H No
Messages setting for proper operation.
KBL-S No
HEDT No
Intel® Trace Hub Debug Message Enabled KBL-Y No
Values: Yes/No - This setting enables/disables the Intel® Trace Hub debug KBL-U No
messages. Note: When enabling this setting you also need to enable Intel® Trace KBL-H No
Hub Soft Enable setting for proper operation.
KBL-S No
HEDT No
Unlock Token
This allows the OEM to input an Unlock Token binary file for closed chassis debug.
Click on Debug in the left tabs menu> Intel® IDLM is expanded by default:
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
4
Intel® IDLM
This allows an IDLM binary to be merged into output image built by Intel® FIT.
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
1
Disable Hyperthreading KBL-Y No
Values: Yes/No KBL-U No
This setting controls enabling or disabling of Hyper threading. Note: This strap is KBL-H No
intended for debugging purposes only. See BIOS Spec for more details on KBL-S No
enabling / disabling Hyperthreading.
HEDT No
Number of Active Cores KBL-Y All
Values: All, 1, 2, 3, 4 KBL-U All
This setting controls the number of active processor cores. Note: This strap is KBL-H All
intended for debugging purposes only. See BIOS Spec for more details on KBL-S All
enabling or disabling processor cores.
HEDT All
BIST Initialization KBL-Y No
Values: Yes/No KBL-U No
This setting determines if BIST will be run at platform reset after BIOS requested KBL-H No
actions. KBL-S No
Note: This strap is intended for debugging purposes only. HEDT No
Flex Ratio KBL-Y 0x0
This setting controls the maximum processor non-turbo ratio. Note: This strap is KBL-U 0x0
intended for debugging purposes only. See BIOS Spec for more details on KBL-H 0x0
maximum processor non-turbo ratio configuration.
KBL-S 0x0
HEDT 0x0
Processor Boot Max Frequency KBL-Y Yes
Values: Yes/No KBL-U Yes
This setting determines if the processor will operate at maximum frequency at KBL-H Yes
power-on and boot. Note: This strap is intended for debugging purposes only. KBL-S Yes
HEDT Yes
JTAG Power Disable KBL-Y No
Values: Yes - JTAG Power on C10 and Lower/No - No Power on C10 and KBL-U No
Lower KBL-H No
This setting determines if JTAG power will be maintained on C10 or lower power KBL-S No
states. Note: This strap is intended for debugging purposes only.
HEDT No
SA Power Plane Topology KBL-Y 0x2
This setting determines the SA power plane topology. See Processor EDS for KBL-U 0x2
details. Note: This strap should be left at the recommended default setting. KBL-H 0x2
KBL-S 0x2
HEDT 0x2
SA VR Type KBL-Y SVID
Value: SVID/Fixed VR KBL-U SVID
This setting determines the SA core domain VR type. See Processor EDS for KBL-H SVID
details. KBL-S Fixed VR
HEDT Fixed VR
IA Power Plane Topology KBL-Y 0x0
This setting determines the IA power plane topology. See Processor EDS for KBL-U 0x0
details. Note: This strap should be left at the recommended default setting. KBL-H 0x0
KBL-S 0x0
HEDT 0x0
IA Power Plane VR KBL-Y SVID
Value: SVID/Fixed VR KBL-U SVID
This setting determines the IA core domain VR type. See Processor EDS for KBL-H SVID
details. KBL-S SVID
HEDT SVID
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
Intel Confidential
Image Creation: Intel® Flash Image Tool
Green Build button Can also select CTRL+B, or Build> Build Image from the menu bar
along the top of the screen
1
Console shows status of
build and path where saved
2
Intel Confidential
Programming SPI Flash Devices and Checking Firmware Status
Now that the Flash image file has been created, it can be programmed into the SPI
Flash device(s) of the target machine. For platforms that don’t boot, a Flash Chip
Programmer will be required. For platforms that can boot to DOS or Windows*, the
Intel® FPT can be used.
If two total SPI Flash devices were specified during the build process, then
additional image files will be saved, one for each SPI Flash device. These files are
assumed to be named outimage(1).bin and outimage(2).bin.
2. Utilize a Flash burner/programmer to program the image(s). For multiple SPI Flash
devices, the images are numbered sequentially to correspond to the first and
second SPI Flash device accordingly.
Note: Intel® FPT will automatically disable the Intel® ME or EFI prior to flashing the
image to the platform.
Intel Confidential
Programming SPI Flash Devices and Checking Firmware Status
The DOS versions supported by Intel® FPT are: DOS, Free DOS, and DRMK DOS. Use
the following steps to program the SPI Flash devices,
1. Copy all the files in the “(root)\Tools\System Tools\Flash Programming Tool\DOS”
directory to the root directory of a bootable USB key.
2. Navigate to your Output Directory (as specified in Table 2-2) where your
generated SPI Flash image(s) are saved. It is assumed that this image file is named
outimage.bin. Copy this image file to the root directory of the USB key.
3. Boot the target system to DOS and change to the root directory of the bootable
USB key. At the DOS prompt type:
fpt.exe -i
The system should respond with the number of SPI Flash devices available. For
example:
Note: If the SPI Flash device does not currently contain a descriptor it may
report only a single device.
4. Program the SPI Flash image to the Flash device(s) by issuing the following
command at the prompt:
fpt.exe -f outimage.bin
If the programming was successful, then the following message will be shown.
If the programming was NOT successful, then repeat this step to try again. If
programming problems persist, then check the SPI Flash devices and platform
hardware.
5. Execute a platform global reset using Intel® FPT -greset. Next go to Section 3.3 to
check the Intel® ME Firmware status.
Intel Confidential
Programming SPI Flash Devices and Checking Firmware Status
fptw.exe -i
The system should respond with the number of SPI Flash devices available. For
example:
Note: If the SPI Flash device does not currently contain a descriptor it may
report only a single device.
3. Program the SPI Flash image to the Flash device(s) by issuing the following
command at the prompt:
fptw.exe -f outimage.bin
If the programming was successful, then the following message will be shown.
If the programming was NOT successful, then repeat this step to try again. If
programming problems persist, then check the SPI Flash devices and platform
hardware.
4. Use fptw.exe -greset to perform a G3 power cycle. Next go to Section 3.3 to check
the Intel® ME Firmware status.
MEInfo.exe -fwsts
Intel Confidential
Programming SPI Flash Devices and Checking Firmware Status
Note: This section is only intended to show how to use the MEInfo.exe tool for checking
firmware status. For full usage and capabilities of the MEInfo.exe tool, please see the
System Tools User Guide.
Intel Confidential
Programming SPI Flash Devices and Checking Firmware Status
System does not boot to By default, the system will boot to EFI Shell. To boot to DOS,
DOS 1. Enter BIOS menu, then go to the ‘Boot’ screen
2. Change ‘Boot Option #1’ to be your USB key (ensure USB key is
formatted to be DOS bootable)
3. Press ‘F4’ to save settings and reboot
Hear 3 beeps when Possible device is disconnected or device not found, check
platform powers on • platform power and MCP fan power connectors
• DIMM memory modules (if applicable for memory down modules
• USB devices (keyboard, mouse, USB key) may be plugged into
inactive USB port
• missing/incorrect jumpers
• missing or poorly socketed MCP
No display on monitor Ensure Corporate FW SKU supports integrated graphics. Try external
graphics card.
USB device not detected USB device may be plugged into inactive USB port
or does not work
System does not boot Incorrect Flash image – possible reasons:
(Post Code 00) • wrong FW selected during Flash image build process
• wrong Flash size selected
Re-build image with correct settings and re-flash using Flash burner.
§§
Intel Confidential
Appendix — Flash Configurations
A Appendix — Flash
Configurations
This chapter covers only the basic information needed for clock control parameter
programming. For a more detailed treatment of Mainstream - Mobile Family clocks, see
Intel®Kabylake PCH-H / LP Clocks and Intel® Management Engine — Platform
Compliancy Guide for ME Hardware.
Intel Confidential
Appendix — Flash Configurations
Intel Confidential
Appendix — Flash Configurations
§§
Intel Confidential
Appendix — Intel® ICCS SKU Support Matrix
The following table describes ICC features supported for specific PCH SKU, clock range
(maximum and minimum), spread mode supported by Kabylake-H/LP SKUs.
Note: Please refer to Kabylake-H/LP Platform Controller Hub (PCH) External Design
Specification (EDS) for details about Kabylake-H/LP Chipset Clock architecture
In below tables,
Premium Y x
Premium U x
Base U x
Clock Range
[Min-Max]=100 MHz. BCLK [Min-Max] = 98 - 100 MHz.
Supported
SSC
Down SSC: 0 - 0.5% Down SSC: 0 - 0.5%
Supported
Intel Confidential
Appendix — Intel® ICCS SKU Support Matrix
Q270 X
Q250 X
B250 X
H270 X
Z270 X
X290 X
Clock Range [Min-Max] = 100 MHz BCLK [Min-Max] = 98 - 100 MHz Overclocking Range support:
Supported
BCLK Over clocking [Min-Max] =
99.5 -170 MHz *
SSC Down SSC: 0 - 0.5% Down SSC : 0 - 0.5% BCLK Over clocking Down SSC :
Supported 0 - 0.5%
*BCLK Overclocking ranges mentioned here are ranges supported by The Intel® ME
FW, please make sure to choose range based on platform/HW configuration.
Intel Confidential
Appendix — Intel® ICCS SKU Support Matrix
Note: In below table, Mask Control CLKREQ cannot be configured via FIT Tool. It’s configured
to default once by FW during cold boot and bios can set/clear bits anytime.
Intel Confidential
Appendix — Intel® ICCS SKU Support Matrix
Intel Confidential
Appendix — Intel® ICCS SKU Support Matrix
Intel Confidential
Appendix — Intel® ICCS SKU Support Matrix
Intel Confidential
Appendix — Intel® ICCS SKU Support Matrix
Disabled N/A Keep Default Keep it enabled Set to If SRCx output clock
1b. is disabled, please
keep FIT->ICC-
Since SRCx clock is
>Power
unused/disabled.
Management
Config. -> CLKREQ
SRCx Enable =
Enabled
However no need to
configure an
associated GPIO
mapping.
Intel Confidential
Appendix — Boot Guard Configuration
Boot Guard Profile - 0 0 0 00 0 This configuration will invoke Boot Guard during boot with
No_FVME neither Verification nor Measurement. For platforms with all
0
the required Boot Guard components but do not wish to enable
Boot Guard boot block verification protection.
Boot Guard VE 0 1 0 01 1 When Verification is desired but if verification fails the platform
1 will continue to boot with the unverified IBB for a short period,
to allow remediation.
2 Boot Guard VME 0 1 1 01 1 When Verification and Measured are desired and the asset
protection is provided by both TPM protection and a timed
remediation period.
3 Boot Guard VM 0 1 1 00 1 When Verification and Measured are desired and the asset
protection is provided by TPM protection.
Error Enforcement
Enforcement Mode Name Description
Policy (ENF)
2 Reserved
3 Restricted Mode 0 minutes before shutdown – instant shutdown policy.
Intel Confidential
Appendix — Boot Guard Configuration
Force Boot Guard ACM Enabled Force Boot Guard Boot determines if the false - Allow the CPU to jump to the
(F) platform starts the Force Boot Guard Boot legacy reset vector if the Boot Guard
timer. If it successfully starts it indicates Module cannot be successfully loaded.
success. When the Force Boot Guard timer (default)
stops, it starts the Protect Bios Environment
timer, if indicated by the boot policy
true - Force the Boot Guard ACM to
restrictions. Anchor ACM then jumps to the
execute.
Initial Boot Block(IBB) with the Force Boot
Guard Boot time stopped and the Protect BIOS
enable timer running.
Verified Boot Enabled (V) Boot Guard cryptographically verifies the false - Platform does not perform
platform Initial Boot Block (IBB) using the verified boot (default)
boot policy key. On successful verification,
Boot Guard executes Initial Boot Block (IBB)
true - Platform performs verified boot
using the boot policy key. If the verification
fails, Anchor signals or enters Remediation.
Measured Boot Enabled (M) Boot Guard measures the Initial Boot Block false - Platform does not perform
(IBB) into the TPM. Boot Guard perform no measured boot (default)
verification that the IBB is correct or from the
platform manufacturer. The Slylake
true - Platform performs measured
implementation of Boot Guard will support
boot
measurements into TPM or Intel’s Platform
Trust Technology.
Protect Bios Environment Platform manufacturer may want Initial boot false - Take no actions to control the
Enabled (PBE) block to be protected between verification/ environment during execution of the
measurement and execution from attacks on BIOS components (default)
buses and non-CPU components. Boot Guard
accomplishes this by allowing the initial boot
true - Takes actions to control the
block to be verified and executed in LLC in
environment during the execution of
NEM if PBE is enabled.
the BIOS components.
Error Enforcement Policy (ENF) Boot Guard invokes the Enforcement Policy See Section C-2 for details.
when a fatal error is encountered. The action
taken by ENF is determined by the OEM set
persistent policies. Like,
• Allowing platform to continue to boot
• Immediate Shutdown
• Shutdown with Timeout intervals
When the ENF logic is invoked, PTT or TPM
also disconnects.
Intel Confidential
Appendix — Intel® Platform Trust Technology
Note: Intel® Platform Trust Technology does not support the full TPM functionality
requirements and should not be used for Intel® vPro™ based platforms.
Configuration Description
Intel® PTT Supported
Intel® PTT Permanently Disabled No No After the End of Manufacturing command, this setting will
Disabled in HW via FPF permanently set into the FPFs contained in the MCP. If disabled,
the specific MCP can never be enabled for Intel® PTT.
Intel® PTT Permanently Disabled No Yes This setting allows Intel® PTT to be set to disabled without
Disabled in base firmware disabling the MCP FPFs. This is the recommended option to
image permanently disable Intel® PTT on a platform.
Intel® PTT Ship State Disabled Yes Yes Intel® PTT initially shipped in disabled mode, can be enabled by
Disabled in base firmware BIOS command.
image
Intel® PTT Enabled Enabled Yes Yes This is the recommended option to enable Intel® PTT on a
platform.
Intel Confidential
Appendix — Settings for RVP CRBs (B)
Note: The Intel® FIT default settings for Kabylake-LP are based on the RVP3 CRB.
Intel Confidential
Appendix — Settings for RVP CRBs (B)
Polarity Select SATA / PCIe Combo Port 2 Yes 0x1C8 [2] SATA
Polarity Select SATA / PCIe Combo Port 3 Yes 0x1C8 [3] SATA
RVP8 Polarity Select SATA / PCIe Combo Port 4 Yes 0x1C8 [4] PCIe
Polarity Select SATA / PCIe Combo Port 5 Yes 0x1C8 [5] PCIe
Polarity Select SATA / PCIe Combo Port 6 Yes 0x1C8 [6] SATA
Intel Confidential
Appendix — Settings for RVP CRBs (B)
Intel Confidential
Appendix — Integrated Sensor Hub (ISH) Public Key Settings
CLSMNF = Close Manufacturing switch used with Intel® Flash Programming Tool (FPT)
PV = Production Version
For additional information on FPT see System Tools User Guide included with ME kit under system tools
folder.
FPF Automatic FPF MEI command after FPF MEI command before
Firmware MCP
Commit CLSMNF (Yes/No) CLSMNF (Yes/No)
Note: The Intel® FIT allows integration of binary files within Integrated Sensor Hub section under ISH Image
and ISH Data. The Intel® FIT does not generate or create the required files. The table above lists
configuration combinations that can be used. Please see VIP # 105658 - Intel® Integrated Sensor
Solution 3.0 for KBL Program Alpha Corporate Milestone Release Version 3.0.0.1037 update for firmware
information.
Intel Confidential