RKL-S Consumer Bring Up Guide
RKL-S Consumer Bring Up Guide
Revision 1.23
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 lTigernse to any patent claim thereafter drafted which
includes subject matter disclosed herein.
INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH Intel® PRODUCTS. NO LTigerNSE, 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,
OFFTigerRS, 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 notTiger. 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 notTiger.
The Rocket Lake Platform and Rocket Lake 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 lTigernse and may only be used or copied in
accordance with the terms of that lTigernse.
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 lTigernses 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.
2 Intel Confidential
Contents
1 Introduction .............................................................................................................. 6
1.1 Related Documentation ........................................................................................ 6
1.2 Prerequisites....................................................................................................... 6
1.3 Acronyms and Definitions ..................................................................................... 7
1.3.1 General................................................................................................... 7
1.3.2 Intel® Converged Security and Management Engine...................................... 8
1.3.3 System States and Power Management ....................................................... 9
1.4 Reference Documents ........................................................................................ 10
1.5 Format and Notation.......................................................................................... 10
1.6 Kit Contents ..................................................................................................... 11
1.7 External Hardware Requirements for Bring Up ....................................................... 15
2 Image Creation: Intel® Flash Image Tool ............................................................... 16
2.1 Start Intel®FIT ................................................................................................. 16
2.2 Step-by-Step Guide to Build SPI Flash Image with Intel® FIT Interface..................... 16
3 Programming SPI Flash Devices and Checking Firmware Status ............................ 131
3.1 Flash Burner/Programmer ................................................................................ 131
3.1.1 In-Circuit SPI Flash Programming for CRB................................................ 131
3.2 Flash Programming Tool (Intel® FPT) ................................................................. 131
3.2.1 Intel® FPT Windows* Version................................................................. 132
3.3 Checking Intel® ME Firmware Status.................................................................. 132
3.4 Common Bring Up Issues and Troubleshooting Table............................................ 134
A Appendix — Flash Configurations........................................................................... 135
B Appendix — Intel® ICCS SKU Support Matrix ......................................................... 136
C Appendix — Boot Guard Configuration ................................................................... 137
D Appendix — Intel® Platform Trust Technology ....................................................... 139
E Appendix — Integrated Sensor Hub (ISH) Public Key Settings............................... 140
Intel Confidential 3
Figures
Tables
1-1 Number Format Notation........................................................................................... 10
1-2 Data Format Notation ............................................................................................... 10
1-3 Kit Contents ............................................................................................................ 11
2-1 - Initial Screen Layout .............................................................................................. 17
2-2 - Build Settings........................................................................................................ 26
2-3 - Flash Layout ......................................................................................................... 28
2-4 - Flash Settings ....................................................................................................... 34
2-5 - Intel® ME Kernel ................................................................................................... 44
2-6 - Intel® AMT ........................................................................................................... 48
2-7 - Platform Protection ................................................................................................ 56
2-8 - Integrated Clock Controller ..................................................................................... 65
2-9 - Networking & Connectivity ...................................................................................... 74
2-10- Internal PCH Buses ................................................................................................ 79
2-11- Power .................................................................................................................. 85
2-12- Integrated Sensor Hub ........................................................................................... 87
2-13- Debug .................................................................................................................. 89
2-14- CPU Straps ........................................................................................................... 95
2-15- Flex I/O Straps...................................................................................................... 98
2-16- GPIO.................................................................................................................. 118
2-17- Download and Execute ......................................................................................... 123
2-18- Intel® Unique Platform ID ..................................................................................... 125
2-19- FW Update Image Build ........................................................................................ 126
2-20- Intel® FIT - Build Image ....................................................................................... 130
3-1 Common Bring Up Issues and Troubleshooting Table .................................................. 134
Intel Confidential 4
Revision History
Document Revision
Description Revision Date
Number Number
1.1 Added Paired Tx1/Tx2 Rx1/Rx2 Orientation to USB3.2 Port Pairing settings August 2020
Added additional USB2 and USB3 ports under Power Delivery PD Controller
Configuration.
1.2 Changed WLAN Microcode value to 0x43F0 September 2020
1.21 Added ME Feature Pins and GPIO Mode Control sections to GPIO tab October 2020
Updated DMI Configuration entries
Removed Duplicate Intel® HD Audio Voltage Select setting
1.22 Added SMx State and Rsa 1K State setting information December 2020
1.23 Removed note for TRC FPF setting February 2021
§§
Intel Confidential 5
Introduction
1 Introduction
This document covers the Intel® Converged Security and Management Engine
Firmware (Intel® ME) 15.0 - Consumer / 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® CSME FW region — Contains firmware for the Intel® Converged
Security and Management Engine.
• [optional] GbE region — Contains firmware for Intel LAN solution.
For more details on SPI Flash layout, see the document Rocket Lake-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.2 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 6
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 Rocket Lake 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 7
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® Converged Security
and Management Engine Firmware.
Intel® Converged Security and Interface between the Converged Security and Management Engine and
Management Engine 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 8
Introduction
CM3 Intel® Converged Security and 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® Converged Security and Management Engine activities are
mostly suspended to save power. The Intel® Converged Security and
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.
Rocket Lake Intel® Converged Security and Management Engine (Intel® CSME) and 549024 / CDI
Embedded Controller Interaction Product Specification Revision 0.5
Intel® Converged Security and Management Engine BIOS Writers Guide TBD / *
®
Intel Converged Security and Management Engine (Intel® CSME) 15 SKU Firmware TBD / CDI
Consumer Compliance Guide for Rocket Lake PCH-H/LP Chipset Family - Rocket Lake
Platform Compliancy and Testing Guide - Revision x.x
Note: * Unless specified otherwise, a document can be ordered by providing its reference number to your
Intel Field Applications Engineer.
Intel Confidential 9
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 10
Introduction
This document
XML file
Intel Confidential 11
Introduction
XML file
Exe file
Ini file
Exe file
Intel Confidential 12
Introduction
Intel Confidential 13
Introduction
Intel Confidential 14
Introduction
§§
Intel Confidential 15
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 16
Image Creation: Intel® Flash Image Tool
1 2 3 4 5 6 7
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
Save This button labeled ‘Save’ on rollover allows saving of xml file
3
Clear Console This button labeled ‘Clear Console’ clears the console area (see page 23)
4
This button labeled ‘Build Settings’ brings up the build settings popup Window
Build Settings
5 see (Table 2-2)
6 Build Image This button labeled ‘Build Image’ on rollover allows build of the image
This button labeled ‘Build Image For FWUpdate’ allows the user to build separate
7 Build Image For FWUpdate
firmware update binaries.
Intel Confidential 17
Image Creation: Intel® Flash Image Tool
8 9 10
9 Drop Down Selector This drop down allows selection of SKU within platform selected
10 Indicator This displays the type of Boot Media Target based on FW being used
Intel Confidential 18
Image Creation: Intel® Flash Image Tool
Intel Confidential 19
Image Creation: Intel® Flash Image Tool
Intel Confidential 20
Image Creation: Intel® Flash Image Tool
Intel Confidential 21
Image Creation: Intel® Flash Image Tool
Intel Confidential 22
Image Creation: Intel® Flash Image Tool
Intel Confidential 23
Image Creation: Intel® Flash Image Tool
CPU Straps which contain a detailed list of parameters (see Table 2-14):
• CPU Straps
22 CPU Straps Tab
Intel Confidential 24
Image Creation: Intel® Flash Image Tool
Intel Confidential 25
Image Creation: Intel® Flash Image Tool
10
11
12
13
14
15
FWUpdate Output Path Double click to the right of FWUpdate.bin and click to get browse button to
specify path and name of file to create for the build - default is
2 FWUpdate.bin in the same folder as Intel® FIT tool
Intel Confidential 26
Image Creation: Intel® Flash Image Tool
7
Yes 32-bit value to use as the IFWI build version number.
Yes This setting enabled Redundancy support for critical layout components.
9 Redundancy Enabled
Yes
Intel® Manifest
12 Extension Utility Path
Yes
Yes
14 Signing Tool
Intel Confidential 27
Image Creation: Intel® Flash Image Tool
Click on Flash Layout in the left tabs menu> Descriptor Region is expanded by default:
Click on Flash Layout in the left tabs menu> BIOS Region is expanded by default:
2
BIOS Region - Length -This displays the length of the BIOS binary.
Note: This value will be automatically populated by Intel® FIT during image
build.
BIOS Binary File RKL-S biosimage.bin
Navigate to path to load bios.rom file. This loads the BIOS binary that will be
merged into the output image generated by the Intel® FIT tool.
Click on Flash Layout in the left tabs menu> Ifiw: Intel® ME and PMC Region is expanded by default:
Intel Confidential 28
Image Creation: Intel® Flash Image Tool
3
Intel® CSME Binary File RKL-S meimage.bin
Navigate to your Source Directory (as specified in Table 2-2) and switch to the
Intel® CSME subdirectory. Choose the appropriate Intel® CSME Firmware binary
image. This loads the Intel® CSME binary that will be merged into the into the
output image generated by the Intel® FIT tool.
Note: You may choose to build the Intel® CSME Region only. To do so, the Number
of Flash Components in Flash Settings> Flash Components must be set to 0.
Note: If loading meimage.bin file, check that the ME region is enabled in tool
before building image.
Major Version - This displays Major revision number of the currently loaded Intel®
CSME binary.
Minor Version - This displays Minor revision number of the currently loaded Intel®
CSME binary.
Hotfix Version - This displays Hot-Fix revision number of the currently loaded
Intel® CSME binary.
Build Version - This displays Build version number of the currently loaded Intel®
CSME binary.
Chipset Initialization Version - This displays the current Chipset Initialization
version contained in the currently loaded Intel® CSME binary.
Intel Confidential 29
Image Creation: Intel® Flash Image Tool
Chipset Initialization Binary - This loads the Chipset Initialization binary that will RKL-S Chipset.bin
be merged into the output image generated by the Intel® FIT. If specified, this will (Optional)
override the version contained in the Intel® CSME binary to align with the values
programmed by BIOS.
Note: When BIOS passes new Chipset Initialization settings to ME, a Global Reset
is initiated (only required on the first boot, subsequent boots will not incur
a global reset). This allows for the new settings to be stored in the ME
Region and programmed into the PCH. This global reset can be avoided by
loading the proper chipset initialization binary in to the ME Region when
building the image that aligns with the values in BIOS. The Chipset
Initialization Binary will be included in BIOS RC package. If BIOS contains
an older version of Chipset Initialization settings ME will be updated at boot
with the older settings regardless of any newer settings being present in
firmware. In order to avoid this problem and the additional Global Reset
customers should ensure that both BIOS and ME are updated with same
Chipset Initialization binary.
ChipsetInit Override Version - This displays the version of the Chipset
Initialization Binary override if specified.
PMC Binary File - This loads the PMC binary that will be merged into the output RKL-S PMC.bin
image generated by the Intel® FIT tool.
Note: Disable for SKUs and platforms with limited image size, without planned
firmware update support only.
Click on Flash Layout in the left tabs menu> EC Region is expanded by default:
4
EC Region - Length
Note: This value will be automatically populated by Intel® FIT during image
build.
EC Binary File RKL-S EC Binary
Navigate to path to load EC bin file. This loads the Embedded Controller binary used
for eSPI that will be merged into the output image generated by the Intel® FIT tool.
EC Region Enable RKL-S Enabled
Values: Enabled/Disabled
This option allows the user to enable or disable the Embedded Controller data
region.
Intel Confidential 30
Image Creation: Intel® Flash Image Tool
Intel Confidential 31
Image Creation: Intel® Flash Image Tool
7
This loads the PCH Configuration binary that will be merged in the output image
generated by the Intel® FIT tool.
Intel Confidential 32
Image Creation: Intel® Flash Image Tool
Note: The GBST sub-partition is used to enabling FuSa safety standards and is
not applicable for client platforms.
GBST Configuration File RKL-S GBST.bin
Navigate to path to load GBST.bin file. This loads the GBST Configuration binary. (Optional)
Version - This displays the version number of the GBST Configuration Sub-
Partition
Length - This displays the length of the GBST Configuration Sub-Partition.
Note: This value will be automatically populated by Intel® FIT during image
build.
Click on Flash Layout in the left tabs menu> PDR Region is expanded by default:
Intel Confidential 33
Image Creation: Intel® Flash Image Tool
Click on Flash Settings in the left tabs menu> Flash Components is expanded by default:
1
Number of Components RKL-S 1
Values: 0, 1, 2 - This setting configures the total number of flash components for
the platform. Note: Choosing a selection of '0' part will cause the Intel® FIT tool to
build an output image containing only the Intel® ME region.
Flash component 1 Size RKL-S 32MB
Values: 512KB, 1MB, 2MB, 4MB, 8MB, 16MB, 32MB, 64MB - This setting
determines the size of Flash component 1 for the platform image.
Flash component 2 Size RKL-S Greyed Out
Values: 512KB, 1MB, 2MB, 4MB, 8MB, 16MB, 32MB, 64MB - This setting
determines the size of Flash component 2 for the platform image. Note: This
setting is only applicable when the Number of Flash Components option is set to '2'.
SPI Global Protected Range - This sets the default value of the Global Protected RKL-S 0x0
Range register in the SPI Flash Controller.
SPI Idle to Deep Power Down Timeout - This sets SPI Idle to Deep Power Down RKL-S 0x5
Timeout Default Specifies the time in microseconds that the Flash Controller waits
after all activity is idle before commanding the flash devices to Deep Power down,
time = 2^N microseconds.
SPI Out of Order operation Enabled - When this setting is enabled priority RKL-S Yes
operations may be issued while waiting for write / erase operations to complete on
the flash device. When this setting is disabled all write / erase type operations in
order.
SPI Resume Hold-off Delay - This specifies the time after the completion of a RKL-S 4us
pri_op before the flash controller sends the resume instruction. If a new pri_op is
eligible to be issued prior to the end of this delay time then the pri_op is issued
and the timer is reinitialized to tRHD. 3-bit field encodes count with range 0-7.
tRHD = count * 2us.
Intel Confidential 34
Image Creation: Intel® Flash Image Tool
SPI Max write / erase Resume to Suspend intervals - This setting specifies RKL-S No Ceiling
the maximum value for the write and erase Resume to Suspend intervals.
SPI Suspend / Resume Enabled - When this setting is enabled writes and erases RKL-S Yes
may be suspended to allow a read to be issued on the flash device. When this
setting is disabled no transaction will be allowed to the busy flash device.
Software Re-Binding Enabled RKL-S No
Values: Yes / No
When enabled this settings will allow for SPI re-binding to a new PCH during
manufacturing and re-manufacturing flows prior to platform EOM.
2
Host CPU / BIOS Write Access Intel Recommended RKL-S 0xFFFF
Values: 0xFfFF, 0x000A, 0x001A, 0x010A, 0x011A - This setting determines
write access control for the BIOS region.
0xFfFF = Debug/Manufacturing
0x000A = Production
0x001A = Production with access to PDR (should ONLY be used if PDR region is
implemented).
0x010A = Production with access to EC
0x011A = Production with access to EC and PDR
Custom = User custom Host / BIOS Write Access values
For further details on Region Access Control see Rocket Lake H SPI Programming
guide further details.
Host CPU / BIOS Write Access Custom - This setting allows free form user RKL-S Hex Input
customized Host CPU / BIOS Write Access regions permissions
Note: This setting is grayed out unless Custom is selected under the Host CPU /
BIOS Write Access Intel Recommended drop down menu.
Intel Confidential 35
Image Creation: Intel® Flash Image Tool
For further details on Region Access Control see Rocket Lake H SPI Programming
guide.
Host CPU / BIOS Read Access Custom - This setting allows free form user RKL-S Hex Input
customized Host CPU / BIOS Read Access regions permissions
Note: This setting is grayed out unless Custom is selected under the Host CPU /
BIOS Read Access Intel Recommended drop down menu.
3
Intel® ME Write Access Intel Recommended RKL-S 0xFFFF
Values: 0xFFFF, 0x0004- This setting determines write access control for the ME
region.
0xFFFF = Debug/Manufacturing
0x0004 = Production
Custom = User custom Intel® ME Write Access values
For further details on Region Access Control see Rocket Lake H SPI Programming
guide further details.
Intel® ME Write Access Custom - This setting allows free form user customized RKL-S Hex Input
Intel® ME Write Access regions permissions
Note: This setting is grayed out unless Custom is selected under the Intel® ME
Write Access Intel Recommended drop down menu.
Intel Confidential 36
Image Creation: Intel® Flash Image Tool
For further details on Region Access Control see Rocket Lake LP SPI Programming
guide further details.
Intel® ME Read Access Custom - This setting allows free form user customized RKL-S Hex Input
Intel® ME Read Access regions permissions
Note: This setting is grayed out unless Custom is selected under the Intel® ME
Read Access Intel Recommended drop down menu.
4
GbE Write Access Intel Recommended RKL-S 0xFFFF
Values: 0xFFFF, 0x0008 - This setting determines write access control for the
Gigabit Ethernet Region.
0xFFFF = Debug/Manufacturing
0x0008 = Production
Custom = User custom GbE Write Access values
For further details on Region Access Control see Rocket Lake LP SPI Programming
guide further details.
GbE Write Access Custom - This setting allows free form user customized GbE RKL-S Hex Input
Write Access regions permissions
Note: This setting is grayed out unless Custom is selected under the GbE Write
Access Intel Recommended drop down menu.
Intel Confidential 37
Image Creation: Intel® Flash Image Tool
For further details on Region Access Control see Rocket Lake LP SPI Programming
guide further details.
GbE Read Access Custom - This setting allows free form user customized GbE RKL-S Hex Input
Read Access regions permissions
Note: This setting is grayed out unless Custom is selected under the GbE Read
Access Intel Recommended drop down menu.
5
EC Write Access Intel Recommended RKL-S 0xFFFF
Values: 0xFFFF, 0x0100 - This setting determines write access control for the
Embedded Controller Region.
0xFFFF = Debug/Manufacturing
0x0100 = Production
Custom = User custom EC Write Access values
For further details on Region Access Control see Rocket Lake LP SPI Programming
guide further details.
EC Write Access Custom - This setting allows free form user customized EC Write RKL-S Hex Input
Access regions permissions
Note: This setting is grayed out unless Custom is selected under the EC Write
Access Intel Recommended drop down menu.
Intel Confidential 38
Image Creation: Intel® Flash Image Tool
For further details on Region Access Control see Rocket Lake LP SPI Programming
guide further details.
EC Read Access Custom - This setting allows free form user customized EC Read RKL-S Hex Input
Access regions permissions
Note: This setting is grayed out unless Custom is selected under the EC Read
Access Intel Recommended drop down menu.
Intel Confidential 39
Image Creation: Intel® Flash Image Tool
Intel Confidential 40
Image Creation: Intel® Flash Image Tool
7
8
9
7
VSCC Entries
W25Q128BV
VSCC Entries RKL-S
8
Name - This setting allow the OEM input a name designation for each flash RKL-S Winbond
component being used. Note: This is a free form entry field it does not affect actual
flash component operation.
Vendor ID - This configures the JEDEC vendor specific byte ID of the SPI flash RKL-S 0xEF
component. See Rocket Lake LP SPI Programming guide for further details.
device ID 0 - This configures the JEDEC device specific byte ID 0 of the SPI flash RKL-S 0x40
component. See Rocket Lake LP SPI Programming guide for further details.
device ID 1 - This configures the JEDEC device specific byte ID 1 of the SPI flash RKL-S 0x19
component. See Rocket Lake LP SPI Programming guide for further details.
+ Add VSCC Entry
9
Click on Flash Settings in the left tabs menu> BIOS Configuration is expanded by default:
Intel Confidential 41
Image Creation: Intel® Flash Image Tool
10
# Parameter Platform
BIOS Configuration
10
BIOS Redundancy Assistance RKL-S Disabled
Values: Enabled, Disabled
In cases of BIOS boot failure, Intel®CSME will configure the platform to boot with
backup BIOS using Top Swap when this setting is enabled.
# Parameter Platform
FPF Configuration
11
Hardware Binding Enabled RKL-S Disabled
Values: Enabled / Disabled Disabled
This setting configures the FPF Hardware binding behavior for the platform image.
If this setting is enabled FPF Hardware binding will occur when platform close
manufacturing flow is executed with Intel® FPT. If this setting is disabled FPF
Hardware binding will not take place when close manufacturing flow is executed.
For Revenue parts this setting will be ignored and FPF Hardware binding will take
place when close manufacturing flow is executed.
Click on Flash Settings in the left tabs menu> RPMC Configuration is expanded by default:
Intel Confidential 42
Image Creation: Intel® Flash Image Tool
12
# Parameter Platform
RPMC Configuration
12
RPMC Supported RKL-S No
Values: Yes / No
Intel Confidential 43
Image Creation: Intel® Flash Image Tool
Click on Intel® ME Kernel in the left tabs menu> Processor is expanded by default:
1
Processor Emulation RKL-S EMULATE Intel®
Values: No Emulation Core (TM)
branded
EMULATE Intel® vPro (TM) capable Processor
Processor
EMULATE Intel® Core (TM) branded Processor
EMULATE Intel® Celeron (R) branded Processor
EMULATE Intel® Pentium (R) branded Processor
EMULATE Intel® Xeon (R) branded Processor
EMULATE Intel® Xeon (R) Manageability capable Processor
This setting determines processor type to be emulated on pre-production silicon.
Set this parameter to the type of processor that the target system will use during
production. This field will emulate that processor class for pre-production silicon. It
is necessary to set this to Emulate Intel® vPro™ Processor in order to enable Intel®
AMT.
Missing Processor Detection Alert RKL-S No
Values: Yes/No
This setting determines if missing processor detection is enabled on Desktop /
Workstation platforms using Corporate Intel® CSME firmware.
Note: This feature will only work if the platform has the appropriate glue logic
present.
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 RKL-S 0 string
to ensure that customers can only update their platform with images from the OEM
of the platform.
Hide Intel® MEBx Firmware Update Control RKL-S No
Values: Yes/No - This setting allows the customer to hide the Firmware Update
option in the Intel® MEBx interface.
Intel Confidential 44
Image Creation: Intel® Flash Image Tool
3
OEM Tag - This is a free form 32bit field that allows the OEM to configure their own RKL-S 0x00000000
unique identifier in the firmware image.
Click on Intel® ME Kernel in the left tabs menu> Firmware Diagnostics is expanded by default:
4
Automatic Built in Self Test RKL-S Disabled
Values: Enabled/Disabled
This setting enables the firmware Automatic Built in Self Test which is executed
during first platform boot after initial image flashing.
Click on Intel® ME Kernel in the left tabs menu> End of Manufacturing Configuration is expanded by default:
Intel Confidential 45
Image Creation: Intel® Flash Image Tool
6
MCTP Stack Configuration RKL-S 0x920030
Defines the Intel® ME’s 8-bits MCTP Endpoint ID’s for each SMBus physical
interface (SMBus, SMLink0, and SMLink1). These values are needed for FW to
communicate with MCTP end points. For each of these 3 bytes, a value of 0x00
means not used, and values 0xFF or 0x01 - 0x07 or 0x20 - 0x2F are not allowed.
MctpdevicePortEc RKL-S 0x02
MctpdevicePortSio RKL-S 0x00
MctpdevicePortIsh RKL-S 0x00
MctpdevicePortBmc RKL-S 0x00
Click on Intel® ME Kernel in the left tabs menu> Intel® ME Boot Configuration is expanded by default:
Intel Confidential 46
Image Creation: Intel® Flash Image Tool
7
Persistent PRTC Backup Power RKL-S Exists
Values: None / Exists
FPF that indicates if the device is designed such that it may lose PRTC power more
than 10 times throughout the normal life-cycle of the product and hence has no
persistent time or AR protection. At EOM this value is burned to the FPF, and can
never be changed
Click on Intel® ME Kernel in the left tabs menu> Intel® ME Measured Boot Configuration is expanded by default:
8
Intel® ME Measured Boot State UP4 Disabled
Values: Disabled / EnabledIntel® UP3 Disabled
When measured boot is enabled firmware will use additional extended registers for
all IUPs and Key Manifests that firmware loads and verifies from flash. When
measured boot is enabled any IUPs or firmware updates will require a global reset.
Reserved
9
Reserved RKL-S No
Values: Yes/No
Intel Confidential 47
Image Creation: Intel® Flash Image Tool
Click on Intel® AMT in the left tabs menu> Intel® AMT is expanded by default:
1
Intel® AMT Supported RKL-S No
Values: Yes/No - This setting allows customers to disable Intel® AMT on the
platform and force the platform into Standard Manageability mode.
Note: If this setting has been set to disabled Intel® AMT cannot be re-enabled
once the descriptor has been locked. This setting applies to Desktop and
Workstation only.
Manageability Hardware Status RKL-S Enabled
Values: Enabled / Disabled - This setting will permanently disable Manageability
hardware through platform FPFs. At End-of-Manufacturing (EOM), enable/disable
policy value is committed to FPF and can never be changed. Permanently disabling
Manageability hardware with this setting requires “Manageability Application
Supported” and “Disabled” and “Intel® ME Network Services Supported” are set to
“No”.
Note: When “Manageability Application Hardware Status” is Enabled but
“Manageability Application Supported” and “Intel® ME Network Services
Supported” are set to “No”, Manageability Hardware will be disabled by the
Intel®CSME through CVAR.
Intel® ME Network Services Supported RKL-S No
Values: Yes/No - This setting allows customers to enable / disable Intel® ME
Network Services on the platform.
Note: This setting and TLS needs to be enabled for proper operation of Intel®
Authenticate (Corporate Only). In addition if this setting is disabled Intel®
AMT will also be disabled.
Intel® Manageability Application Supported RKL-S No
Values: Yes/No - This setting allows customers to force Intel® AMT enabled
platforms to operate in Standard Manageability mode.
Intel Confidential 48
Image Creation: Intel® Flash Image Tool
Note: If this setting is disabled Intel® AMT or Standard Manageability can still be
re-enabled through the Intel® MEBx interface.
# Parameter Platform Settings
®
Intel AMT Idle Timeout RKL-S 0xFFFF
Values: 0xFFFF - This setting configures the idle timeout value before Intel® AMT
enters into an off state.
Intel® AMT Watchdog Automatic Reset Enabled RKL-S No
Values: Yes/No - This setting allows customers to enable the Intel® ME firmware
to trigger an automatic platform reset if either the MEI or Agent Presence are in a
hung state.
Note: This feature only allows one reset at a time when the watchdog expires.
After this feature has triggered a reset, it must be re-armed for reuse via
management console.
Click on Intel® AMT in the left tabs menu> KVM Configuration is expanded by default:
2
Firmware KVM Screen Blanking RKL-S No
Values: Yes/No - This setting enables KVM Screen blanking capabilities in the
firmware image.
Note: If this setting has been set to disabled it cannot be re-enabled once the
descriptor has been locked.
Click on Intel® AMT in the left tabs menu> Provisioning Configuration is expanded by default:
# Parameter Platform
Intel Confidential 49
Image Creation: Intel® Flash Image Tool
Provisioning Configuration
3
Embedded Host Based Configuration RKL-S No
Values: Yes/No - This setting allows customers to enable / disable Embedded
Host Based Configuration. Important - EHBC is primarily intended for use in
embedded systems as it offers less user privacy/security protection than may be
appropriate for business client systems.
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 RKL-S -
Name Suffix used for PKI provisioning in their firmware image.
Note: For normal out-of-box provisioning functionality this setting should be left
empty.
Click on Intel® AMT in the left tabs menu> OEM Customizable Certificate 1 is expanded by default:
4
Certificate Enabled RKL-S No
Values: Yes/No - This setting allows customers to enable PKI provisioning Custom
Certificate 1.
Certificate Friendly Name - This setting allows customers to assign a user RKL-S -
friendly name for PKI provisioning Custom Certificate 1. Maximum of 32 characters.
Certificate Stream - This setting allows customers to input hash stream for PKI RKL-S -
provisioning Custom Certificate 1. If enabled the certificate will be used in addition
to those already pre-loaded in base firmware during provisioning.
Intel Confidential 50
Image Creation: Intel® Flash Image Tool
5
Certificate Enabled RKL-S No
Values: Yes/No - This setting allows customers to enable PKI provisioning Custom
Certificate 2.
Certificate Friendly Name - This setting allows customers to assign a user RKL-S -
friendly name for PKI provisioning Custom Certificate 2. Maximum of 32 characters.
Certificate Stream - This setting allows customers to input hash stream for PKI RKL-S -
provisioning Custom Certificate 2. If enabled the certificate will be used in addition
to those already pre-loaded in base firmware during provisioning.
6
Certificate Enabled RKL-S No
Values: Yes/No - This setting allows customers to enable PKI provisioning Custom
Certificate 3.
Certificate Friendly Name - This setting allows customers to assign a user RKL-S -
friendly name for PKI provisioning Custom Certificate 3. Maximum 32 characters.
Certificate Stream - This setting allows customers to input hash stream for PKI RKL-S -
provisioning Custom Certificate 3. If enabled the certificate will be used in addition
to those already pre-loaded in base firmware during provisioning.
Intel Confidential 51
Image Creation: Intel® Flash Image Tool
7
Certificate Enabled RKL-S No
Values: Yes/No - This setting allows customers to enable PKI provisioning Default
certificate 1.
Certificate Friendly Name - This setting allows customers to assign a user RKL-S -
friendly name for PKI provisioning Default Certificate 1. Maximum 32 characters.
Certificate Stream - This setting allows customers to input hash stream for PKI RKL-S -
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.
Click on Intel® AMT in the left tabs menu> OEM Default Certificate 2 is expanded by default:
8
Certificate Enabled RKL-S No
Values: Yes/No - This setting allows customers to enable PKI provisioning Default
certificate 2.
Certificate Friendly Name - This setting allows customers to assign a user RKL-S -
friendly name for PKI provisioning Default Certificate 2. Maximum 32 characters.
Certificate Stream - This setting allows customers to input hash stream for PKI RKL-S -
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:
Intel Confidential 52
Image Creation: Intel® Flash Image Tool
9
Certificate Enabled RKL-S No
Values: Yes/No - This setting allows customers to enable PKI provisioning Default
certificate 3.
Certificate Friendly Name - This setting allows customers to assign a user RKL-S -
friendly name for PKI provisioning Default Certificate 3. Maximum 32 characters.
Certificate Stream - This setting allows customers to input hash stream for PKI RKL-S -
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.
Click on Intel® AMT in the left tabs menu> OEM Default Certificate 4 is expanded by default:
10
10
Certificate Enabled RKL-S No
Values: Yes/No - This setting allows customers to enable PKI provisioning Default
certificate 4.
Certificate Friendly Name - This setting allows customers to assign a user RKL-S -
friendly name for PKI provisioning Default Certificate 4.
Certificate Stream - This setting allows customers to input hash stream for PKI RKL-S -
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
Intel Confidential 53
Image Creation: Intel® Flash Image Tool
11
Certificate Enabled RKL-S No
Values: Yes/No - This setting allows customers to enable PKI provisioning Default
certificate 5.
Certificate Friendly Name - This setting allows customers to assign a user RKL-S -
friendly name for PKI provisioning Default Certificate 5.
Certificate Stream - This setting allows customers to input hash stream for PKI RKL-S -
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.
Click on Intel® AMT in the left tabs menu> Redirection Configuration is expanded by default:
12
12
Redirection Localized Language - This setting allows customers to configure RKL-S English
which localized language will be used initially by firmware for user consent output
information (Examples: May be displayed before SOL / KVM session starts).
Redirection Privacy / Security Level - This setting allows customers to RKL-S Default
configure the Privacy and Security level for redirection operations.
Default enables all redirection ports (User consent is configurable).
Enhanced - Enables all redirection ports. (User consent is required and cannot be
disabled).
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
13
Intel Confidential 54
Image Creation: Intel® Flash Image Tool
Note: If this is disabled TLS will be permanently disabled in the firmware image.
This setting needs to be enabled along with along with the Intel® ME
Network Services Supported for proper operation of the Intel®
Authenticate (Corporate Only) feature.
Intel Confidential 55
Image Creation: Intel® Flash Image Tool
Click on Platform Protection in the left tabs menu> Content Protection is expanded by default:
1
PAVP Supported RKL-S Yes
Values: Yes/No
This setting determines if the Protected Audio Video Path (PAVP) feature will be
permanently disabled in the FW image.
HDCP Internal Display Port 1 - 5K RKL-S PortA
Values: None, Port A, Port B, Port C, Port D
This setting determines which port is connected for 5K output on the Internal
Display 1.
Note: Both Display Port 1 & 2 need to be configured for proper operation.
HDCP Internal Display Port 2 - 5K RKL-S None
Values: None, Port A, Port B, Port C, Port D
This setting determines which port is connected for 5K output on the Internal
Display 2.
Note: 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:
2
GuC Encryption Key RKL-S 0x00000000
Values: This option is for entering the raw hash 256 bit string or certificate file for
the Graphics uController.
Click on Platform Protection in the left tabs menu> Hash Key Configuration for Bootguard / ISH is expanded by
default:
Intel Confidential 56
Image Creation: Intel® Flash Image Tool
# Parameter Platform
Hash Key Configuration for Bootguard / ISH
3
OEM Public Key Hash RKL-S 0x00000000
Values: This option is for entering the raw hash string or certificate file for Boot
Guard and ISH. This 384-bit field represents the SHA-384 hash of the OEM public
key corresponding to the private key used to sign the BIOS-SM or ISH image.
Please see Appendix F for further details.
OEM Key Manifest Binary RKL-S
Signed manifest file containing hashes of keys used for signing components of
image. This setting is only configurable when OEM signing is enabled (See
PlatformIntegrity / OemPublicKeyHash).
Second OEM Key hash RKL-S 0x00000000
This option is for entering a secondary raw hash string or certificate file for Boot
Guard and ISH used in instances of OEM Key Revocation. This 384-bit field
represents the SHA-384 hash of the OEM public key corresponding to the private
key used to sign the BIOS-SM or ISH image. Please see Appendix F for further
details.
Note: This setting is greyed out and not configurable until the Second OEM Key
Revocation Enable is set to Yes.
OEM Key Revocation Enabled RKL-S No
Values: Yes/No
This setting enables firmware OEM Key Revocation capabilities.
Note: This setting requires that both OEM Public Key Hash and Second OEM Key
Hash are configured.
Skip OEM Key Check RKL-S No
Values: Yes/No
This is meant for debugging purposes only. Enabling this parameter impacts image
creation procedure in FIT tool only.
Click on Platform Protection in the left tabs menu> Descriptor Configuration is expanded by default:
Intel Confidential 57
Image Creation: Intel® Flash Image Tool
# Parameter Platform
Descriptor Configuration
4 These settings are used for FuSa safety standards and are not applicable
for client platforms.
Flash Descriptor Verification Enabled RKL-S No
Values: Yes/No
This setting enables / disables Flash Descriptor Verification.
Descriptor Signing Key RKL-S -
Values: Hex
This is the path to the private key used to sign the Descriptor, while public key hash
of it is included in the OEM hash manifest. This setting is only configurable when
Flash Descriptor Verification is enabled (See PlatformIntegrity/FdvEnabled).
exclude master access in the signature RKL-S No
Values: Yes/No
Include/exclude master access in the signature.
Click on Platform Protection in the left tabs menu> Exclusion Ranges is expanded by default:
Intel Confidential 58
Image Creation: Intel® Flash Image Tool
# Parameter Platform
Exclusion Ranges
5 These settings are used for FuSa safety standards and are not applicable
for client platforms.
Range 1 offset RKL-S 0x800
Range 1 offset covers manifest, cannot be changed
Range 1 size RKL-S 0x400
Range 1 size covers manifest, cannot be changed.
Range 2 offset RKL-S 0x80
Range 2 offset covers manifest, cannot be changed
Range 2 size RKL-S 0x20
Range 2 size covers manifest, cannot be changed.
Range 3 offset RKL-S 0x0
Values: Hex
Range 3 offset covers OEM defined unprotected range start.
Range 3 size RKL-S 0x0
Values: Hex
Range 3 size covers OEM defined unprotected range length
Intel Confidential 59
Image Creation: Intel® Flash Image Tool
6
Key Manifest ID RKL-S 0x0
Values: This option is for entering the hash of another public key, used by the ACM
to verify the Boot Policy Manifest.
Intel Confidential 60
Image Creation: Intel® Flash Image Tool
7
SAMF Engine Manifest Anti-Rollback Enabled RKL-S Yes
Values: Yes/No
This setting enables Anti-Rollback for the Type-C Subsystem SAMF Engine binary.
PPHY Manifest Anti-Rollback Enabled RKL-S Yes
Values: Yes/No
This setting enabled Anti-Rollback for the Type-C Subsystem NPHY binary.
Click on Platform Protection in the left tabs menu> Intel® PTT Configuration is expanded by default:
Intel Confidential 61
Image Creation: Intel® Flash Image Tool
8
Intel® PTT Supported RKL-S Yes
Values: Yes/No - This setting permanently disables Intel® PTT in the firmware
image.
Intel® PTT initial power-up state RKL-S Enabled
Values: Enabled/Disabled - This setting determines if Intel® PTT is enabled on
platform power-up.
Intel® PTT Supported [FPF] RKL-S Yes
Values: Yes/No - This setting will permanently disable Intel® PTT through
platform FPFs.
Caution: Setting this option to Yes will permanently disable Intel® PTT on
the platform hardware.
SMx State RKL-S Enabled
Values: Enabled / Disabled
This setting allow the user to enable / disable SMx which is set of encryption
algorithms promoted by PRC government regulation and defined by TCG TPM 2.0
Specification.
Rsa 1K State RKL-S Disabled
Values: Enabled / Disabled
This setting allows the user to enable / disable RSA 1024 bit encryption Intel highly
recommends that customers leave this set to “Disabled” due to security concerns.
Note: Having RSA 1024 bit encryption disabled impacts Windows* HLK TPM
testing. Several tests have RSA 1024 dependencies. To avoid these failures
this setting should be set to “Enabled” during HLK testing and then set to
“Disabled” for the manufacturing image.
Click on Platform Protection in the left tabs menu> TPM Over SPI Bus Configuration is expanded by default:
9
TPM Clock Frequency RKL-S 14MHz
Values: 14MHz, 25MHz, 48MHz - This setting determines the clock frequency
setting to be used for the TPM over SPI bus.
TPM Over SPI Bus Enabled RKL-S No
Values: Yes/No - This setting determines if TPM over SPI bus is enabled on the
platform.
Click on Platform Protection in the left tabs menu> BIOS Guard Configuration is expanded by default:
Intel Confidential 62
Image Creation: Intel® Flash Image Tool
10
10
BIOS Guard Protection Override Enabled RKL-S No
This setting allows BIOS Guard to bypass SPI flash controller protections (i.e.
Protected Range Registers and Top Swap).
Click on Platform Protection in the left tabs menu> TXT Configuration is expanded by default:
11
11
TXT Supported RKL-S No
This setting determines if enabled for the platform.
Click on Platform Protection in the left tabs menu> Crypto Hardware Support is expanded by default:
12
12
Crypto HW Support RKL-S Yes
Values: Yes/No - This setting can be used to disable Intel® CSME cryptographic
functionality.
Caution: Configuring this setting to “No” will disables all Intel® CSME
cryptographic related features.
Click on Platform Protection in the left tabs menu> Platform Trusted Device Setup Support is expanded by default:
Intel Confidential 63
Image Creation: Intel® Flash Image Tool
13
13
Enable TDS Capabilities RKL-S No
Values: Yes/No - This setting enables Intel® Trusted Device Setup on the
platform.
Click on Platform Protection in the left tabs menu> FuSa Configuration is expanded by default:
14
14 Note: The GBST sub-partition is used to enabling FuSa safety standards and is
not applicable for client platforms.
Intel Confidential 64
Image Creation: Intel® Flash Image Tool
Click on Integrated Clock Controller in the left tabs menu> Integrated Clock Controller Policies are expanded by
default:
1
Boot Profile RKL-S Profile 0
This parameter allows user to select default profile to be used by the final
generated SPI Flash binary image for the target platform at boot time.
The ‘Record #’ refers to profile created under the “Integrated Clock Controller |
Profiles”.
Default boot profile for system is Profile 0.
Double click on value column of this parameter to choose from available options.
Intel Confidential 65
Image Creation: Intel® Flash Image Tool
This parameter specifies the profile index of the fail-safe profile. On boot failure
detection or CMOS clear the Intel® ME Firmware will revert to this profile if
“Integrated Clock Controller |Integrated Clock Controller Policies - Profile
Changeable “ is set to True. If profile Changeable parameter is set to False, User
can not select Failsafe Boot Profile and profile 0 will be selected as a fail safe boot
profile by default.
The ‘Record #’ refers to profile created under the “Integrated Clock Controller |
Profiles”.
Default Failsafe boot profile for system is Profile 0.
Double click on value column of this parameter to choose from available options.
Profile Changeable RKL-S True
This parameter controls if BIOS or 3rd party application can select boot profile or
not. When set to true, it allows user to change boot profile via BIOS or 3rd party
application. When set to false, Runtime change to boot profile is not allowed and
boot profile selected by “Integrated Clock Controller |Integrated Clock
Controller Policies - Boot Profile “ parameter will be used to boot platform.
Double click on value column of this parameter to choose from available options.
Click on Integrated Clock Controller in the left tabs menu> Profiles >Profile> Bclk Clock Configuration is
expanded by default:
2
BCLK Clock Configuration Enabled RKL-S Disabled
Values: Enabled / Disabled
This setting enables / disables BCLK Clock configuration values for Adaptive /
Overclocking profiles
This parameter allows user to select the nominal frequency for the selected clock.
Range is limited based on the Clock Range Definition record and HW SKU.
BCLK Spread Setting RKL-S N/A
This parameter allows user to select the percentage of Spread setting for the
selected clock. Range is limited based on the Clock Range Definition record and HW
SKU.
Intel Confidential 66
Image Creation: Intel® Flash Image Tool
Click on Integrated Clock Controller in the left tabs menu> Profiles are expanded by default:
3
PLL Reference Clock Select RKL-S Gen2
Values: Gen2 / Gen4
This setting determines which PLL reference clock is being used to supply the
100MHz CPU and PCIe root ports and their corresponding PCIe devices.
4
External PEG / DMI Clock Configuration RKL-S Disabled
Values: Enabled / Disabled
This setting determines if the PEG / DMI clock source if from ICC or from an
external discrete oscillator
Click on Integrated Clock Controller in the left tabs menu> Profiles are expanded by default:
6 5
Intel Confidential 67
Image Creation: Intel® Flash Image Tool
5 Note: Intel® ME image has to be loaded to enable other ICC profile settings.
For RKL-S, Intel® FIT provides 5 pre-defined ICC profiles to choose from.
•Standard
•Adaptive
•OverClockingExt
Note: User can select pre-defined profiles via “Integrated Clock Controller |
Profiles - Profile Type “ parameter
User can add up to maximum 16 profiles.To add new profile, please use
“Integrated Clock Controller | Profiles - + Add Profile Button”
Profile Name RKL-S Profile 0
This parameter allows user to customize profile name for easy identification. By
default it uses pre-defined profile name like Profile 0.
Profile Type RKL-S Standard
Available ICC profiles for RKL-S are Standard, Adaptive and OverClockingExt.
This parameter indicates which pre- defined profile selected for each profile#.
Double click on value column of this parameter to choose from available options.
+ Add Profile Button RKL-S
6 This button is used to add new ICC profile. User can add up to maximum 16
profiles. New profile will be added under “Integrated Clock Controller |
Profiles” tab.
Click on Integrated Clock Controller in the left tabs menu> Profiles >Profile> Clock Range Definition Record is
expanded by default:
Intel Confidential 68
Image Creation: Intel® Flash Image Tool
7
BCLK PLL Clock Source Maximum Frequency - This parameter allows user to RKL-S
specify the maximum frequency that can be applied to BCLK clock source when
overclocking the platform. Value is limited by divider/frequency limits determined
by HW SKU, and cannot be less than 100 MHz.
Intel Confidential 69
Image Creation: Intel® Flash Image Tool
9
SRC0[6:15] RKL-S Enabled
Values: Enabled/Disabled
These parameters come under the Power Management section and they control
Enabling /Disabling of specific Output Clocks at boot time.
These settings should match with platform
hardware design.
For RVP, recommend keeping defaults for bring up with Intel® CSME FW.
Intel Confidential 70
Image Creation: Intel® Flash Image Tool
Intel Confidential 71
Image Creation: Intel® Flash Image Tool
10
Intel Confidential 72
Image Creation: Intel® Flash Image Tool
11
11
SSCEN RKL-S Enabled
Values: Enabled / Disabled
Intel Confidential 73
Image Creation: Intel® Flash Image Tool
Click on Networking & Connectivity in the left tabs menu> Discrete vPro NIC is expanded by default:
Intel Confidential 74
Image Creation: Intel® Flash Image Tool
1
Platform vPro 2.5G Wired LAN Enabled RKL-S No
Values: Yes / No
This setting enables / disables Discrete Intel® vPro Network adapter support on the
platform.
Platform vPro 2.5G Wired LAN slave SMBus Address RKL-S 0x49
Values: Hex
This setting configures the SMBus address for the Discrete Intel®vPro Network
adapter.
Click on Networking & Connectivity in the left tabs menu> Docking Station is expanded by default:
2
vPro Dock Enabled RKL-S No
This setting enables Intel® vPro communication over supported NIC in a
ThunderboltTM Dock.
vPro 2.5G Wired LAN on dock slave SMBus Address RKL-S 0x0
This setting configures the NIC SMBus slave address.
Type-C Port1 Re-Timer SMBus Address RKL-S 0x20
This setting configures Intel® SMBus Address.
Type-C Port2 Re-Timer SMBus Address RKL-S 0x21
This setting configures Intel® SMBus Address.
Type-C Port3 Re-Timer SMBus Address RKL-S 0x22
This setting configures Intel® SMBus Address.
Type-C Port4 Re-Timer SMBus Address RKL-S 0x23
This setting configures Intel® SMBus Address.
Click on Networking & Connectivity in the left tabs menu> Wired LAN Configuration is expanded by default:
Intel Confidential 75
Image Creation: Intel® Flash Image Tool
3
LAN Power Well RKL-S SLP_LAN#
Values: Core Well, Sus Well, ME Well, SLP_LAN - This setting allows customers
to configure the power well that will be used by Intel® Integrated LAN.
Note: Recommended setting is SLP_LAN#.
LAN PHY Power Up Time RKL-S 100ms
Values: 50ms, 100ms
Intel® Integrated Wired LAN Enable RKL-S Enabled
Values: Enabled/Disabled - This setting enables or disables the Intel®
Integrated LAN.
GbE PCIe Port Select RKL-S Port 13
Values: None, PORT5, PORT9, PORT12, PORT13 - This setting allows
customers to configure the PCIe Port that will Intel® Integrated LAN will operate
on.
TSN GbE PCIe Port Select RKL-S None
Values: None, TSN PORT6, TSN PORT 7 - This setting allows customers to
configure the PCIe port that TSN will operate on.
Note: The Intel® Integrated LAN and TSN GbE are mutually exclusive.
GbE PHY SMBus Address RKL-S 0x64
This setting configures Intel® Integrated Wired LAN SMBus address to accept
SMBus cycles from the MAC. Note: Recommended setting is 64h.
GbE SMBus Address Enabled RKL-S Yes
Values: Yes/No - This enables the Intel® Integrated Wired LAN MAC SMBus
address. Note: This setting must be enabled if using Intel® Integrated LAN.
GbE MAC SMBus Address RKL-S 0x70
Intel Confidential 76
Image Creation: Intel® Flash Image Tool
4
CLINK Enabled RKL-S No
Values: Yes/No
This setting allows customers to enable / disable the Wireless LAN CLINK signal
through Intel® CSME firmware.
Note: For using Intel® vPro Wireless solutions this should be set to “Yes”.
WLAN Microcode RKL-S 0x43F0
This setting allow OEMs to configure which Intel® Wireless LAN card microcode to
load into the firmware image.
WLAN Power Well RKL-S SLP_WLAN#
Values: Disabled, Sus Well, ME Well, SLP_M#||SPDA, SLP_WLAN#
This setting allows OEMs to configure the power well that will be used by Intel®
Wireless LAN.
Note: This setting should be enabled if the WLAN adapter on the platform is
CNVi.
Click on Networking & Connectivity in the left tabs menu> Time Sensitive Networking Configuration is expanded
by default:
Intel Confidential 77
Image Creation: Intel® Flash Image Tool
5
Time Sensitive Networking RKL-S Disabled
Values: TSN Enable / TSN Disabled
Note: Time Sensitive Networking and Wired LAN are mutually exclusive only one
of these features can enabled on the platform.
Intel Confidential 78
Image Creation: Intel® Flash Image Tool
Click on Internal PCH Buses in the left tabs menu> PCH Timer Configuration is expanded by default:
1
PCH clock output stable to PROCPWRGD high (tPCH45) RKL-S 1ms
Values: 100ms, 50ms, 5ms, 1ms - This setting configures the minimum timing
from XCK_PLL locked to CPUPWRGD high. For further details see Rocket Lake LP
Platform Controller Hub EDS.
PCIe Power Stable Timer (tPCH33) RKL-S Disabled
Values: Enabled/Disabled - This setting configures the enables / disables the t36
timer. When enabled PCH will count 99ms from PWROK assertion before PLTRST# is
de-asserted.
Intel Confidential 79
Image Creation: Intel® Flash Image Tool
2
Intel® SMLink0 MCTP Address Enabled RKL-S No
Value: Yes/No
This setting configures the Intel® SMLink0b MCTP Address.
Note: This setting is only used for testing.
Intel® SMBus ASD Address - This setting configures the Intel® SMBus Alert RKL-S 0x00000000
Sending device Address. For details see Rocket Lake LP SPI Programming guide for
further details.
Intel® SMBus ASD Address Enable RKL-S No
Values: Yes/No - This setting enables / disables the Intel® SMBus Alert Sending
device. For details see Rocket Lake LP SPI Programming guide for further details.
Intel® SMBus Subsystem Vendor & device ID for ASF - This setting RKL-S 0x00000000
configures the Intel® SMBus Subsystem Vendor & device ID for ASF. For details see
Rocket Lake LP SPI Programming guide further details.
Intel® SMBus I2C Address - This setting configures the Intel® SMBus I2C RKL-S 0x00000000
Address. Note: This setting is only used for testing purposes. The recommended
setting is "0000000".
Intel Confidential 80
Image Creation: Intel® Flash Image Tool
3
DMI Lane Reversal RKL-S No
Values: Yes/No - This setting allows the DMI Lane signals to be reversed. For
further details see Rocket Lake LP Platform Controller Hub EDS.
Intel Confidential 81
Image Creation: Intel® Flash Image Tool
Note: The maximum DMI Lane Width is dependent on CPU / PCH combination
being used. Settings higher than the CPU / PCH combination supports are
ignored and the maximum supported width will be used.
Click on Internal PCH Buses in the left tabs menu> eSPI Configuration is expanded by default:
Intel Confidential 82
Image Creation: Intel® Flash Image Tool
Intel Confidential 83
Image Creation: Intel® Flash Image Tool
Intel Confidential 84
Image Creation: Intel® Flash Image Tool
Click on Power in the left tabs menu> Platform Power is expanded by default:
1
SLP_S3# / GPD4 Signal Configuration RKL-S SLP_S3#
Values: SLP_S3#, GPD4 - This setting allows the customer to assign the
SLP_S3# Power Control signal as SLP_S3# or as GDP4. For further details see
Rocket Lake LP Platform Controller Hub EDS.
SLP_S4# / GPD5 Signal Configuration RKL-S SLP_S4#
Values: SLP_S4#, GPD5 - This setting allows the customer to assign the
SLP_S4# Power Control signal as SLP_S4# or as GDP5. For further details see
Rocket Lake LP Platform Controller Hub EDS.
SLP_S5# / GPD10 Signal Configuration RKL-S SLP_S5#
Values: SLP_S5#, GPD10 - This setting allows the customer to assign the
SLP_S5# Power Control signal as SLP_S5# or as GDP10. For further details see
Rocket Lake LP Platform Controller Hub EDS.
SLP_A# / GPD6 Signal Configuration RKL-S SLP_A#
Values: SLP_A#, GPD6 - This setting allows the customer to assign the SLP_A#
Power Control signal as SLP_A# or as GDP6. For further details see Rocket Lake LP
Platform Controller Hub EDS.
SLP_S0# Tunnel RKL-S Disabled
This setting Enables / Disables the tunneling of the SLP_S0# pin over ESPI to the
EC when in ESPI mode.
Integrated 1.8v VRM RKL-S VRM Disabled
Values: VRM Disabled / VRM Enabled
This setting enables the integrated 1.8v Voltage Regulator Module on the PCH for
CML-H
Click on Power in the left tabs menu> Deep Sx is expanded by default:
Intel Confidential 85
Image Creation: Intel® Flash Image Tool
2
Deep Sx Enabled RKL-S Yes
Values: Yes/ No - This setting enables / disables support for Deep Sx operation.
For further details see Rocket Lake LP Platform Controller Hub EDS. Note: Support
for Deep Sx is board design dependent.
Click on Power in the left tabs menu> PCH Thermal Reporting is expanded by default:
3
Thermal Power Reporting Enabled RKL-S Yes
This setting enabled a once-per-second timer interrupt is enabled which triggers
firmware to report power and temperature information as enabled by configuration
registers. Note: When this setting is disabled ensure that the once-per-second
timer interrupt associated with this feature is also disabled.
Intel Confidential 86
Image Creation: Intel® Flash Image Tool
Click on Integrated Sensor Hub in the left tabs menu> Integrated Sensor Hub is expanded by default:
1
Integrated Sensor Hub Supported RKL-S No
Values: Yes/No
This setting allows customers to disable ISH on the platform.
Integrated Sensor Hub Power Up State RKL-S Disabled
Values: Enabled/Disabled
Field is enabled for editing if “Integrated Sensor Hub Supported” field above is set
to “Yes”. This setting allows customers to determine the power up state for ISH.
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.
Input File RKL-S ISH Binary
(Optional)
Version - This displays the version of ISH
Click on Integrated Sensor Hub in the left tabs menu> ISH Data is expanded by default:
Intel Confidential 87
Image Creation: Intel® Flash Image Tool
3
PDT Binary File RKL-S Path for PDT
Binary file
Intel Confidential 88
Image Creation: Intel® Flash Image Tool
Click on Debug in the left tabs menu> Intel® ME Firmware Debugging Overrides is expanded by default:
1
IDLM Binary RKL-S IDLM Binary
This allows an IDLM binary to be merged into output image built by Intel® FIT. (Optional)
Click on Debug in the left tabs menu> Delayed Authentication Mode Configuration is expanded by default:
2
Delayed Authentication Mode Enabled RKL-S No
Values: Yes/No - This setting enable / disables Delayed Authentication Mode on
the platform.
Click on Debug in the left tabs menu> Intel® Trace Hub Technology is expanded by default:
Intel Confidential 89
Image Creation: Intel® Flash Image Tool
3
Intel® Trace Hub Binary - This loads the Intel® Trace Hub binary that will be RKL-S Trace Hub
merged into the output image generated by the Intel® FIT tool. Binary
Intel® Trace Hub Emergency Mode Enabled RKL-S No
Values: Yes/No - This setting enable / disables Intel® Trace Hub in the firmware
base image.
Intel® Trace Hub Filtering RKL-S Trace Hub Filter
This setting allows a user input binary for filtering of output messages for Intel® Binary
Trace Hub (Optional)
PMC Debug Messages Enabled RKL-S Yes
Values: Yes/No - This setting enables/disables the PMC debug messages.
Unlock Token RKL-S Unlock Token
This allows the OEM to input an Unlock Token binary file for closed chassis debug. Binary
(Optional)
Click on Debug in the left tabs menu> Intel® ME Debugging Overrides is expanded by default:
4
Debug Override Pre-Production Silicon - Allows the OEM to control FW features RKL-S 0x00000000
to assist with pre-production platform debugging. This control has no effect if used
on production silicon.
Bit 0: Disable DRAM_INIT_DONE (default timeout 60 seconds)
Bit 1: Disable Host Reset Timer
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.
Intel Confidential 90
Image Creation: Intel® Flash Image Tool
Debug Override Production Silicon - Allows the OEM to control FW features to RKL-S 0x00000000
assist with production platform debugging.
Bit 0: Extend DRAM_INIT_DONE timeout to 30 minutes (default timeout 15
seconds)
Bit 1: Disable Host Reset Timer
Bit 2: Disable CPU_RESET_DONE timeout
Note: Certain options do not work when the descriptor is locked.
Intel® ME Reset Behavior RKL-S Intel® ME
Values: Intel® ME will Halt / Intel® Alternate image boot Alternate image
boot
This setting determines Intel® ME behavior when boot image errors are
encountered. Warning: This setting should be used for debug purposes only.
Note: This may block normal Firmware functional flows.
Enable Intel® ME Reset Capture on CLR_RST# RKL-S No
Values: Yes/No
This setting configures Intel® ME behavior when it resets during CL_RST#1. Note:
The recommended default for this setting is 'No'
Firmware ROM Bypass RKL-S No
Values: Yes/No - This setting enables / disables firmware ROM bypass. Note:
This setting only has affect when the firmware being used has ROM Bypass code
present.
ASF Idle Flash Reclaim Enabled RKL-S Yes
Values: Yes / No
This controls enabling / disable the Intel® AFS Idle flash reclaim capabilities.
5 Note: When any of the DCI BSSB USB3 Port interfaces are enabled the
associated USB3 port selection control will be greyed out under the USB3
Port Configuration settings section under the Flex I/O tab
Intel Confidential 91
Image Creation: Intel® Flash Image Tool
Intel Confidential 92
Image Creation: Intel® Flash Image Tool
6
eSPI / EC Low Frequency Debug Override RKL-S No
When enabled this setting will divide eSPI clock frequency by 8.
Note: This setting should only be used for debugging purposes. Leaving this set
to “Yes” will impact eSPI performance on the platform.
Click on Debug in the left tabs menu> Early USB DBC Type-A Configuration is expanded by default:
7
Enabled early USB2 DbC connection RKL-S No
Values: Yes / No
This setting enabled a delay during Intel® ME firmware bring-up to allow USB2 DbC
connection to be established
USB2 DbC port enable RKL-S No USB2 Ports
This setting determines which USB2 ports are enabled for Early DbC debugging.
Intel Confidential 93
Image Creation: Intel® Flash Image Tool
8
TRC Enabled (FPF) RKL-S No
Values: Yes / No
When enabled the TRC HIP and TRC Countermeasures are enabled. When
manufacture is completed, this value is burned into an FPF.
TRC Enabled RKL-S No
Values: Yes / No
When enabled the TRC HIP and TRC Countermeasures are enabled. The purpose of
this setting is to allow OEMs to enable TRC for testing prior to close of
manufacturing and FPF commit.
Intel Confidential 94
Image Creation: Intel® Flash Image Tool
Click on CPU Straps in the left tabs menu> CPU Straps are expanded by default:
Intel Confidential 95
Image Creation: Intel® Flash Image Tool
Intel Confidential 96
Image Creation: Intel® Flash Image Tool
Intel Confidential 97
Image Creation: Intel® Flash Image Tool
Click on Flex I/O in the left tabs menu> Intel® RST for PCIe Configuration is expanded by default:
1
PCIe Controller 3 Port 1 SRIS Enabled RKL-S No
Values: Yes/ No - This is used to configure SRIS Port 1 for Intel® RST for PCIe
on PCIe Controller 3.
Note: Configuration of this setting is only required if the NVM device will be
connected external SATA Express cable.
PCIe Controller 3 Port 2 SRIS Enabled RKL-S No
Values: Yes/ No - This is used to configure SRIS Port 2 for Intel® RST for PCIe
on PCIe Controller 3.
Note: Configuration of this setting is only required if the NVM device will be
connected external SATA Express cable.
Intel Confidential 98
Image Creation: Intel® Flash Image Tool
Intel Confidential 99
Image Creation: Intel® Flash Image Tool
2
PCIe Controller 1 Lane Reversal Enabled RKL-S No
Values: Yes/ No - This setting allows the PCIe lanes on Controller 1 to be
reversed. Note: Refer to EDS for PCIe supported port
configurations.
PCIe Controller 2 Lane Reversal Enabled RKL-S No
Values: Yes/ No - This setting allows the PCIe lanes on Controller 2 to be
reversed. Note: Refer to EDS for PCIe supported port
configurations.
PCIe Controller 3 Lane Reversal Enabled RKL-S No
Values: Yes/ No - This setting allows the PCIe lanes on Controller 3 to be
reversed. Note: Refer to EDS for PCIe supported port
configurations.
PCIe Controller 4 Lane Reversal Enabled RKL-S No
Values: Yes/ No - This setting allows the PCIe lanes on Controller 4 to be
reversed. Note: Refer to EDS for PCIe supported port
configurations.
PCIe Controller 5 Lane Reversal Enabled RKL-S No
Values: Yes/ No - This setting allows the PCIe lanes on Controller 5 to be
reversed. Note: Refer to EDS for PCIe supported port
configurations.
PCIe Controller 6 Lane Reversal Enabled RKL-S No
Values: Yes/ No - This setting allows the PCIe lanes on Controller 6 to be
reversed. Note: Refer to EDS for PCIe supported port
configurations.
Click on Flex I/O in the left tabs menu> PCIe Port Configuration is expanded by default:
3
PCIe Controller 1 (Port 1-4) RKL-S 4x1
Values: 4x1, (1x2, 2x1), 2x2, 1x4 - This setting controls PCIe Port
configurations for PCIe Controller 1. For further details see Rocket Lake LP
Platform Controller Hub EDS.
PCIe Controller 2 (Port 5-8) RKL-S 1x4
Values: 4x1, (1x2, 2x1), 2x2, 1x4 - This setting controls PCIe Port
configurations for PCIe Controller 2. For further details see Rocket Lake LP
Platform Controller Hub EDS.
PCIe Controller 3 (Port 9-12) RKL-S 1x4
Values: 4x1, (1x2, 2x1), 2x2, 1x4 - This setting controls PCIe Port
configurations for PCIe Controller 3. For further details see Rocket Lake LP
Platform Controller Hub EDS.
PCIe Controller 4 (Port 13-16) RKL-S 4x1
Values: 4x1, (1x2, 2x1), 2x2, 1x4 - This setting controls PCIe Port
configurations for PCIe Controller 4. For further details see Rocket Lake LP
Platform Controller Hub EDS.
PCIe Controller 5 (Port 17-20) RKL-S 1x4
Values: 4x1, (1x2, 2x1), 2x2, 1x4 - This setting controls PCIe Port
configurations for PCIe Controller 5. For further details see Rocket Lake LP
Platform Controller Hub EDS.
PCIe Controller 6 (Port 21-24) RKL-S 1x4
Values: 4x1, (1x2, 2x1), 2x2, 1x4 - This setting controls PCIe Port
configurations for PCIe Controller 6. For further details see Rocket Lake LP
Platform Controller Hub EDS.
Click on Flex I/O in the left tabs menu> SATA / PCIe Combo Port Configuration is expanded by default:
4
SATA / PCIe Combo Port 0 RKL-S PCIe
Values: SATA, PCIe (or GbE), GPIO - This setting configures the PCIe port to
operate as either:
PCIe Port 11 or SATA Port 0
For further details on Flex I/O see Comet Lake H Platform Controller Hub EDS.
Note: This port is shared with GbE Port select if PCIe Port 12 has been selected
for Intel® Integrated LAN this port setting will be grayed out.
SATA / PCIe Combo Port 2 RKL-S GbE
Values: SATA, PCIe, GPIO Polarity PCIe, GPIO Polarity SATA - This setting
configures the PCIe port to operate as either:
PCIe Port 13 or SATA Port 0b
For further details on Flex I/O see Comet Lake H Platform Controller Hub EDS.
Note: This port is shared with GbE Port select if PCIe Port 13 has been selected
for Intel® Integrated LAN this port setting will be grayed out.
SATA / PCIe Combo Port 3 RKL-S SATA
Values: SATA, PCIe, GPIO Polarity PCIe, GPIO Polarity SATA - This setting
configures the PCIe port to operate as either:
PCIe Port 14 or SATA Port 1b
For further details on Flex I/O see Comet Lake H Platform Controller Hub EDS.
SATA / PCIe Combo Port 4 RKL-S SATA
Values: SATA, PCIe, GPIO Polarity PCIe, GPIO Polarity SATA - This setting
configures the PCIe port to operate as either:
PCIe Port 15 or SATA Port 2
For further details on Flex I/O see Comet Lake H Platform Controller Hub EDS.
SATA / PCIe Combo Port 5 RKL-S SATA
Values: SATA, PCIe, GPIO Polarity PCIe, GPIO Polarity SATA - This setting
configures the PCIe port to operate as either:
PCIe Port 16 or SATA Port 3
For further details on Flex I/O see Comet Lake H Platform Controller Hub EDS.
SATA / PCIe Combo Port 6 RKL-S GPIO Polarity PCIe
Values: SATA, PCIe, GPIO Polarity PCIe, GPIO Polarity SATA - This setting
configures the PCIe port to operate as either:
PCIe Port 17 or SATA Port 4
For further details on Flex I/O see Comet Lake H Platform Controller Hub EDS.
SATA / PCIe Combo Port 7 RKL-S PCIe
Values: SATA, PCIe, GPIO Polarity PCIe, GPIO Polarity SATA - This setting
configures the PCIe port to operate as either:
PCIe Port 18 or SATA Port 5
For further details on Flex I/O see Comet Lake H Platform Controller Hub EDS.
SATA / PCIe Combo Port 8 RKL-S PCIe
Values: SATA, PCIe, GPIO Polarity PCIe, GPIO Polarity SATA - This setting
configures the PCIe port to operate as either:
PCIe Port 19 or SATA Port 6
For further details on Flex I/O see Comet Lake H Platform Controller Hub EDS.
5
USB3 / PCIe Combo Port 0 RKL-S USB3
Values: PCIe (or GbE), USB3 - This setting configures the PCIe port to operate
as either:
PCIe Port 1 or USB3 Port 7
For further details on Flex I/O see Rocket Lake H Platform Controller Hub EDS.
Note: If DCI BSSB for this USB3 Combo port it will be Grayed out.
USB3 / PCIe Combo Port 1 RKL-S USB3
Values: PCIe (or GbE), USB3 - This setting configures the PCIe port to operate
as either:
PCIe Port 2 or USB3 Port 8
For further details on Flex I/O see Rocket Lake H Platform Controller Hub EDS.
Note: If DCI BSSB for this USB3 Combo port it will be Grayed out.
USB3 / PCIe Combo Port 2 RKL-S PCIe
Values: PCIe (or GbE), USB3 - This setting configures the PCIe port to operate
as either:
PCIe Port 3 or USB3 Port 9
For further details on Flex I/O see Rocket Lake H Platform Controller Hub EDS.
Note: If DCI BSSB for this USB3 Combo port it will be Grayed out.
USB3 / PCIe Combo Port 3 RKL-S PCIe
Values: PCIe (or GbE), USB3 - This setting configures the PCIe port to operate
as either:
PCIe 4 or USB3 Port 10
For further details on Flex I/O see Rocket Lake H Platform Controller Hub EDS.
Note: If DCI BSSB for this USB3 Combo port it will be Grayed out.
USB3 Port 1 Connector Type Select RKL-S Type C
This setting configures the physical connector type to be used for USB 3.0 / 3.1
Port 1.
USB3 Port 2 Connector Type Select RKL-S Type C
This setting configures the physical connector type to be used for USB 3.0 / 3.1
Port 2.
USB3 Port 3 Connector Type Select RKL-S Type C
This setting configures the physical connector type to be used for USB 3.0 / 3.1
Port 3.
USB3 Port 4 Connector Type Select RKL-S Type C
This setting configures the physical connector type to be used for USB 3.0 / 3.1
Port 4.
USB3 Port 5 Connector Type Select RKL-S Type A / Type C
This setting configures the physical connector type to be used for USB 3.0 / 3.1
Port 4.
USB3 Port 6Connector Type Select RKL-S Type A / Type C
This setting configures the physical connector type to be used for USB 3.0 / 3.1
Port 4.
USB3 Port 7 Connector Type Select RKL-S Type A / Type C
This setting configures the physical connector type to be used for USB 3.0 / 3.1
Port 4.
USB3 Port 8 Connector Type Select RKL-S Type A / Type C
This setting configures the physical connector type to be used for USB 3.0 / 3.1
Port 4.
Note: When a USB 3.2 Gen 2x1 (10 Gb/s) capable port is configured to USB
3.2 Gen 1x1 (5 Gb/s) speed using the soft strap, the port may still send
10 Gb/s compliance patterns if the USB compliance test (TD1.4, and
TD1.7) is run on the port.
USB3 Port 2 Speed Select RKL-S USB 3.2
This setting determines the USB3 Port 2 speed capabilities.
Note: When a USB 3.2 Gen 2x1 (10 Gb/s) capable port is configured to USB
3.2 Gen 1x1 (5 Gb/s) speed using the soft strap, the port may still send
10 Gb/s compliance patterns if the USB compliance test (TD1.4, and
TD1.7) is run on the port.
USB3 Port 3 Speed Select RKL-S USB 3.2
This setting determines the USB3 Port 3 speed capabilities.
Note: When a USB 3.2 Gen 2x1 (10 Gb/s) capable port is configured to USB
3.2 Gen 1x1 (5 Gb/s) speed using the soft strap, the port may still send
10 Gb/s compliance patterns if the USB compliance test (TD1.4, and
TD1.7) is run on the port.
USB3 Port 4 Speed Select RKL-S USB 3.2
This setting determines the USB3 Port 4 speed capabilities.
Note: When a USB 3.2 Gen 2x1 (10 Gb/s) capable port is configured to USB
3.2 Gen 1x1 (5 Gb/s) speed using the soft strap, the port may still send
10 Gb/s compliance patterns if the USB compliance test (TD1.4, and
TD1.7) is run on the port.
USB3 Port 5 Speed Select RKL-S USB 3.1 Gen2
This setting determines the USB3 Port 5 speed capabilities.
Note: When a USB 3.2 Gen 2x1 (10 Gb/s) capable port is configured to USB
3.2 Gen 1x1 (5 Gb/s) speed using the soft strap, the port may still send
10 Gb/s compliance patterns if the USB compliance test (TD1.4, and
TD1.7) is run on the port.
USB3 Port 6 Speed Select RKL-S USB 3.1 Gen2
This setting determines the USB3 Port 6 speed capabilities.
Note: When a USB 3.2 Gen 2x1 (10 Gb/s) capable port is configured to USB
3.2 Gen 1x1 (5 Gb/s) speed using the soft strap, the port may still send
10 Gb/s compliance patterns if the USB compliance test (TD1.4, and
TD1.7) is run on the port.
USB3 Port 7 Speed Select RKL-S USB 3.1 Gen2
This setting determines the USB3 Port 7 speed capabilities.
Note: When a USB 3.2 Gen 2x1 (10 Gb/s) capable port is configured to USB
3.2 Gen 1x1 (5 Gb/s) speed using the soft strap, the port may still send
10 Gb/s compliance patterns if the USB compliance test (TD1.4, and
TD1.7) is run on the port.
Note: When a USB 3.2 Gen 2x1 (10 Gb/s) capable port is configured to USB
3.2 Gen 1x1 (5 Gb/s) speed using the soft strap, the port may still send
10 Gb/s compliance patterns if the USB compliance test (TD1.4, and
TD1.7) is run on the port.
USB3 Port 9 Speed Select RKL-S USB 3.1 Gen2
This setting determines the USB3 Port 9 speed capabilities.
Note: When a USB 3.2 Gen 2x1 (10 Gb/s) capable port is configured to USB
3.2 Gen 1x1 (5 Gb/s) speed using the soft strap, the port may still send
10 Gb/s compliance patterns if the USB compliance test (TD1.4, and
TD1.7) is run on the port.
USB3 Port 10 Speed Select RKL-S USB 3.1 Gen2
This setting determines the USB3 Port 10 speed capabilities.
Note: When a USB 3.2 Gen 2x1 (10 Gb/s) capable port is configured to USB
3.2 Gen 1x1 (5 Gb/s) speed using the soft strap, the port may still send
10 Gb/s compliance patterns if the USB compliance test (TD1.4, and
TD1.7) is run on the port.
USB3.2 Ports 1 and 2 Pairing RKL-S Paired
Values: Not Paired/Paired Tx1/Tx2 Rx1/Rx2, Paired
This setting configures USB3 Ports 1 and 2 to operate in pairing mode.
Note: The Paired Tx1/Tx2 Rx1/Rx2 Orientation setting option changes USB 3.2
Gen2x2 Tx and Rx signal pairs muxing orientation.
USB3.2 Ports 3 and 4 Pairing RKL-S Paired
Values: Not Paired/Paired Tx1/Tx2 Rx1/Rx2, Paired
This setting configures USB3 Ports 3 and 4 to operate in pairing mode.
Note: The Paired Tx1/Tx2 Rx1/Rx2 Orientation setting option changes USB 3.2
Gen2x2 Tx and Rx signal pairs muxing orientation.
USB3.2 Ports 5 and 6 Pairing RKL-S Not Paired
Values: Not Paired/Paired Tx1/Tx2 Rx1/Rx2, Paired
This setting configures USB3 Ports 5 and 6 to operate in pairing mode.
Note: The Paired Tx1/Tx2 Rx1/Rx2 Orientation setting option changes USB 3.2
Gen2x2 Tx and Rx signal pairs muxing orientation.
USB3.2 Ports 7 and 8 Pairing RKL-S Not Paired
Values: Not Paired/Paired Tx1/Tx2 Rx1/Rx2, Paired
This setting configures USB3 Ports 7 and 8 to operate in pairing mode.
Note: The Paired Tx1/Tx2 Rx1/Rx2 Orientation setting option changes USB 3.2
Gen2x2 Tx and Rx signal pairs muxing orientation.
USB3.2 Ports 9 and 10 Pairing RKL-S Not Paired
Values: Not Paired/Paired Tx1/Tx2 Rx1/Rx2, Paired
This setting configures USB3 Ports 9 and 10 to operate in pairing mode.
Note: The Paired Tx1/Tx2 Rx1/Rx2 Orientation setting option changes USB 3.2
Gen2x2 Tx and Rx signal pairs muxing orientation.
Click on Flex I/O in the left tabs menu> USB2 Port Configuration is expanded by default:
6
USB2 Port 1 Connector Type Select RKL-S Type A / Type C
This setting configures the physical connector type to be used for USB2 Port 1.
USB2 Port 2 Connector Type Select RKL-S Type A / Type C
This setting configures the physical connector type to be used for USB2 Port 2.
USB2 Port 3 Connector Type Select RKL-S Type A / Type C
This setting configures the physical connector type to be used for USB2 Port 3.
USB2 Port 4 Connector Type Select RKL-S Type A / Type C
This setting configures the physical connector type to be used for USB2 Port 4.
USB2 Port 5 Connector Type Select RKL-S Type A / Type C
This setting configures the physical connector type to be used for USB2 Port 5.
USB2 Port 6 Connector Type Select RKL-S Type A / Type C
This setting configures the physical connector type to be used for USB2 Port 6.
USB2 Port 7 Connector Type Select RKL-S Type-C
This setting configures the physical connector type to be used for USB2 Port 7.
USB2 Port 8 Connector Type Select RKL-S Type A / Type C
This setting configures the physical connector type to be used for USB2 Port 8.
7
Type-C Default State RKL-S USB SPR in un-
Values: USB SPR in un-subscription or disconnected state default/USB subscription or
SPR in host subscription state by default disconnected state
default
This bit defines how the PMC configures Type -C USB3 / USB2 SPR.
Click on Flex I/O in the left tabs menu> Type-C Subsystem Configuration is expanded by default:
8
SAMF Binary File - This loads the SAMF binary that will be merged into the RKL-S SAMF Binary
output image generated by the Intel® FIT.
SAMF Enabled RKL-S Yes
Values: Yes/No
This setting enables / disables the Type-C Subsystem IO Manageability Engine on
the platform.
SAMF Length - This displays the length of the SAMF binary.
Note: This value will be automatically populated by Intel® FIT during image
build.
SAMF Version - This displays the version of SAMF binary.
PPHY Binary File - This loads the PPHY binary that will be merged into the RKL-S PPHY Binary
output image generated by the Intel® FIT.
PPHY Manifest Enabled RKL-S Yes
Values: Yes/No
This setting enables / disables the PPHY on the platform.
PPHY Length - This displays the length of the PPHY binary.
Note: This value will be automatically populated by Intel® FIT during image
build.
PPHY Version - This displays the version of PHY binary.
Tcss - Partial Update Enabled RKL-S Disabled
Values: Disabled/Enabled
This setting enables partial update for TCSS partitions
Click on Flex I/O in the left tabs menu> Power Delivery PD Controller Configuration is expanded by default:
9
PMC-PD controller USB-C Mode RKL-S PMC / SMBus
Values: PMC/ eSPI, PMC/ SMBus
This bit defines how the PMC interfaces with the Type-C components on the
board.
Notes:
1. This setting is greyed and not configurable for LP based SKUs. for LP SKUs,
PMC interfaces with PD chips/Re-timer via ALERT# pin.
2. if user selection is 0 where PMC interfaces with an eSPI connected agent, all
of the below parameters are N/A and will be grayed out.
Re-timer Power Gating Enabled RKL-S No
Values: Yes / No
This setting indicates whether platform Re-timer power gating is enabled.
Type-C port 1 Enabled RKL-S Yes
Values: Yes / No
This setting indicates whether the associated Type-C port1 is enabled.
Note: This setting is only available for configuration when PMC-PD controller
USB-C Mode Enabled parameter is set to 1.
USB2 Port Number associated for Type-C Port 1 RKL-S USB2 Port 7
Values: USB2 Port 1,USB2 Port 2,USB2 Port 3,USB2 Port 4,USB2 Port
5,USB2 Port 6,USB2 Port 7,USB2 Port 8,USB2 Port 9,USB2 Port 10, USB2
Port 11, USB2 Port 12, USB2 Port 13, USB2 Port 14
This indicates the USB2 port number for the associated Type-C port1.
Notes:
1. This parameter is applicable only when Type-C port 1 Enabled is set to yes.
2. Once user selects USB2 port number associated with Type-C port1,the
respective USB2 port connector selection will be greyed out and auto set to
Type-C under the USB2 Port Configuration section. example: if USB2 Port
number associated for Type-C Port 1 is set to “USB2 Port 2” ,Parameter
under Flex I/O->USB2 Port Configuration->USB2 Port 2 Connector Type
Select will be grayed out and auto set to “Type C”.
3. OEMs are recommended to configure different USB-C connectors with
increasing port numbers (TCP0_*, TCP1_*, TCP2_*, TCP3_*), should be
paired with increasing number of USB2 ports from PCH. (this is needed to
make split xDCI controller work functionally)E.g. (TCP0_* , USB2*_1),
(TCP1_* , USB2*_3), (TCP2_* , USB2*_4), (TCP3_* , USB2*_5)
USB3 Port number associated for Type-C Port 1 RKL-S USB3 Port 1
Values: USB3 Port 1,USB3 Port 2,USB3 Port 3,USB3 Port 4, USB3 Port 5,
USB3 Port 6, USB3 Port 7, USB3 Port 8, USB3 Port 9, USB3 Port 10
This indicates the USB3 port number for the associated Type-C port1.
Notes:
1. This parameter is applicable only when Type-C port 1 Enabled is set to yes.
2. Once user selects USB3 port number associated with Type-C port1,the
respective USB3 port connector selection will be greyed out and auto set to
Type-C under the USB3 Port Configuration section. example: if USB Port
number associated for Type-C Port 1 is set to “USB3 Port 6” ,Parameter
under Flex I/O->USB3 Port Configuration->USB3 Port 6 Connector Type
Select will be grayed out and auto set to “Type C”.
3. OEMs are recommended to configure different USB-C connectors with
increasing port numbers (TCP0_*, TCP1_*, TCP2_*, TCP3_*), should be
paired with increasing number of USB2 ports from PCH. (this is needed to
make split xDCI controller work functionally)E.g. (TCP0_* , USB2*_1),
(TCP1_* , USB2*_3), (TCP2_* , USB2*_4), (TCP3_* , USB2*_5)
Note: OEMs are recommended to set unique SMBus address allocation for
Type-C port and Re-timer associated.
Type-C port 2 Enabled RKL-S No
Values: Yes / No
This setting indicates whether the associated Type-C port is enabled.
Note: This setting is only available for configuration when PMC-PD controller
USB-C Mode Enabled parameter is set to 1.
USB2 Port Number associated for Type-C Port 2 RKL-S USB2 Port 9
Values: USB2 Port 1,USB2 Port 2,USB2 Port 3,USB2 Port 4,USB2 Port
5,USB2 Port 6,USB2 Port 7,USB2 Port 8,USB2 Port 9,USB2 Port 10, USB2
Port 11, USB2 Port 12, USB2 Port 13, USB2 Port 14
This indicates the USB2 port number for the associated Type-C port.
Notes:
1. This parameter is applicable only when Type-C port 2 Enabled is set to yes.
2. Once user selects USB2 port number associated with Type-C port2,the
respective USB2 port connector selection will be greyed out and auto set to
Type-C under the USB2 Port Configuration section. example: if USB2 Port
number associated for Type-C Port 2 is set to “USB2 Port 2” ,Parameter
under Flex I/O->USB2 Port Configuration->USB2 Port 2 Connector Type
Select will be grayed out and auto set to “Type C”.
3. OEMs are recommended to configure different USB-C connectors with
increasing port numbers (TCP0_*, TCP1_*, TCP2_*, TCP3_*), should be
paired with increasing number of USB2 ports from PCH. (this is needed to
make split xDCI controller work functionally)E.g. (TCP0_* , USB2*_1),
(TCP1_* , USB2*_3), (TCP2_* , USB2*_4), (TCP3_* , USB2*_5)
USB3 Port number associated for Type-C Port 2 RKL-S USB3 Port 2
Values: USB3 Port 1,USB3 Port 2,USB3 Port 3,USB3 Port 4, USB3 Port 5,
USB3 Port 6, USB3 Port 7, USB3 Port 8, USB3 Port 9, USB3 Port 10
This indicates the USB3 port number for the associated Type-C port.
Notes:
1. This parameter is applicable only when Type-C port 2Enabled is set to yes.
2. Once user selects USB3 port number associated with Type-C port2,the
respective USB3 port connector selection will be greyed out and auto set to
Type-C under the USB3 Port Configuration section. example: if USB Port
number associated for Type-C Port 2is set to “USB3 Port 6” ,Parameter
under Flex I/O->USB3 Port Configuration->USB3 Port 6 Connector Type
Select will be grayed out and auto set to “Type C”.
3. OEMs are recommended to configure different USB-C connectors with
increasing port numbers (TCP0_*, TCP1_*, TCP2_*, TCP3_*), should be
paired with increasing number of USB2 ports from PCH. (this is needed to
make split xDCI controller work functionally)E.g. (TCP0_* , USB2*_1),
(TCP1_* , USB2*_3), (TCP2_* , USB2*_4), (TCP3_* , USB2*_5)
Type-C Port 2 Re-timer Present RKL-S Yes
Values: Yes / No
This indicates whether a re-timer is present for the associated Type-C port.
Note: OEMs are recommended to set unique SMBus address allocation for
Type-C port and Re-timer associated.
Type-C port 3 Enabled RKL-S Yes
Values: Yes / No
This setting indicates whether the associated Type-C port is enabled.
Note: This setting is only available for configuration when PMC-PD controller
USB-C Mode Enabled parameter is set to 1.
USB2 Port Number associated for Type-C Port 3 RKL-S USB2 Port 9
Values: USB2 Port 1,USB2 Port 2,USB2 Port 3,USB2 Port 4,USB2 Port
5,USB2 Port 6,USB2 Port 7,USB2 Port 8,USB2 Port 9,USB2 Port 10, USB2
Port 11, USB2 Port 12, USB2 Port 13, USB2 Port 14
This indicates the USB2 port number for the associated Type-C port.
Notes:
1. This parameter is applicable only when Type-C port 3 Enabled is set to yes.
2. Once user selects USB2 port number associated with Type-C por3 ,the
respective USB2 port connector selection will be greyed out and auto set to
Type-C under the USB2 Port Configuration section. example: if USB2 Port
number associated for Type-C Port 3 is set to “USB2 Port 2” ,Parameter
under Flex I/O->USB2 Port Configuration->USB2 Port 2 Connector Type
Select will be grayed out and auto set to “Type C”.
3. OEMs are recommended to configure different USB-C connectors with
increasing port numbers (TCP0_*, TCP1_*, TCP2_*, TCP3_*), should be
paired with increasing number of USB2 ports from PCH. (this is needed to
make split xDCI controller work functionally)E.g. (TCP0_* , USB2*_1),
(TCP1_* , USB2*_3), (TCP2_* , USB2*_4), (TCP3_* , USB2*_5)
USB3 Port number associated for Type-C Port 3 RKL-S USB3 Port 3
Values: USB3 Port 1,USB3 Port 2,USB3 Port 3,USB3 Port 4, USB3 Port 5,
USB3 Port 6, USB3 Port 7, USB3 Port 8, USB3 Port 9, USB3 Port 10
This indicates the USB3 port number for the associated Type-C port.
Notes:
1. This parameter is applicable only when Type-C port 3 Enabled is set to yes.
2. Once user selects USB3 port number associated with Type-C port3,the
respective USB3 port connector selection will be greyed out and auto set to
Type-C under the USB3 Port Configuration section. example: if USB Port
number associated for Type-C Port 3 is set to “USB3 Port 6” ,Parameter
under Flex I/O->USB3 Port Configuration->USB3 Port 6 Connector Type
Select will be grayed out and auto set to “Type C”.
3. OEMs are recommended to configure different USB-C connectors with
increasing port numbers (TCP0_*, TCP1_*, TCP2_*, TCP3_*), should be
paired with increasing number of USB2 ports from PCH. (this is needed to
make split xDCI controller work functionally)E.g. (TCP0_* , USB2*_1),
(TCP1_* , USB2*_3), (TCP2_* , USB2*_4), (TCP3_* , USB2*_5)
Type-C Port 3 Re-timer Present RKL-S No
Values: Yes / No
This indicates whether a re-timer is present for the associated Type-C port.
Type-C Port 3 Re-timer Configuration Enabled RKL-S No
Values: Yes / No
Indicates whether the associated re-timer requires configuration. Yes =
configuration done via PMC; No = configuration done via PD Controller.
Note: OEMs are recommended to set unique SMBus address allocation for
Type-C port and Re-timer associated.
Type-C port 4 Enabled RKL-S No
Values: Yes / No
This setting indicates whether the associated Type-C port is enabled.
Note: This setting is only available for configuration when PMC-PD controller
USB-C Mode Enabled parameter is set to 1.
USB2 Port Number associated for Type-C Port 4 RKL-S USB2 Port 7
Values: USB2 Port 1,USB2 Port 2,USB2 Port 3,USB2 Port 4,USB2 Port
5,USB2 Port 6,USB2 Port 7,USB2 Port 8,USB2 Port 9,USB2 Port 10, USB2
Port 11, USB2 Port 12, USB2 Port 13, USB2 Port 14
This indicates the USB2 port number for the associated Type-C port.
Notes:
1. This parameter is applicable only when Type-C port 4 Enabled is set to yes.
2. Once user selects USB2 port number associated with Type-C port4,the
respective USB2 port connector selection will be greyed out and auto set to
Type-C under the USB2 Port Configuration section. example: if USB2 Port
number associated for Type-C Port 4 is set to “USB2 Port 2” ,Parameter
under Flex I/O->USB2 Port Configuration->USB2 Port 2 Connector Type
Select will be grayed out and auto set to “Type C”.
3. OEMs are recommended to configure different USB-C connectors with
increasing port numbers (TCP0_*, TCP1_*, TCP2_*, TCP3_*), should be
paired with increasing number of USB2 ports from PCH. (this is needed to
make split xDCI controller work functionally)E.g. (TCP0_* , USB2*_1),
(TCP1_* , USB2*_3), (TCP2_* , USB2*_4), (TCP3_* , USB2*_5)
USB3 Port number associated for Type-C Port 4 RKL-S USB3 Port 4
Values: USB3 Port 1,USB3 Port 2,USB3 Port 3,USB3 Port 4, USB3 Port 5,
USB3 Port 6, USB3 Port 7, USB3 Port 8, USB3 Port 9, USB3 Port 10
This indicates the USB3 port number for the associated Type-C port.
Notes:
1. This parameter is applicable only when Type-C port 4 Enabled is set to yes.
2. Once user selects USB3 port number associated with Type-C port4,the
respective USB3 port connector selection will be greyed out and auto set to
Type-C under the USB3 Port Configuration section. example: if USB Port
number associated for Type-C Port 4 is set to “USB3 Port 6” ,Parameter
under Flex I/O->USB3 Port Configuration->USB3 Port 6 Connector Type
Select will be grayed out and auto set to “Type C”.
3. OEMs are recommended to configure different USB-C connectors with
increasing port numbers (TCP0_*, TCP1_*, TCP2_*, TCP3_*), should be
paired with increasing number of USB2 ports from PCH. (this is needed to
make split xDCI controller work functionally)E.g. (TCP0_* , USB2*_1),
(TCP1_* , USB2*_3), (TCP2_* , USB2*_4), (TCP3_* , USB2*_5)
Type-C Port 4 Re-timer Present RKL-S Yes
Values: Yes / No
This indicates whether a re-timer is present for the associated Type-C port.
Type-C Port 4 Re-timer Configuration Enabled RKL-S No
Values: Yes / No
Indicates whether the associated re-timer requires configuration. Yes =
configuration done via PMC; No = configuration done via PD Controller.
Type-C Port 4 Re-timer SMBus Address RKL-S 0x0
Value: Hex
This indicates the SMBus address for the associated re-timer.
Note: OEMs are recommended to set unique SMBus address allocation for
Type-C port and Re-timer associated.
Type-C Port 1 USB3 Ownership RKL-S PCH
Values: CPU/PCH
This setting determines if the Type-C Port 1 USB3 is owned by CPU or PCH.
Type-C Port 1 Connector Type Select RKL-S 1 Re-Timer
Values: 1 Re-Timer, 2 Re-Timers
This setting determines the number of Re-Timers being used for TYpe-C Port 1
Type-C Port 2 USB3 Ownership RKL-S PCH
Values: CPU/PCH
This setting determines if the Type-C Port 2 USB3 is owned by CPU or PCH.
Type-C Port 2 Connector Type Select RKL-S 1 Re-Timer
Values: 1 Re-Timer, 2 Re-Timers
This setting determines the number of Re-Timers being used for TYpe-C Port 2
Type-C Port 3 USB3 Ownership RKL-S PCH
Values: CPU/PCH
This setting determines if the Type-C Port 3 USB3 is owned by CPU or PCH.
Type-C Port 3 Connector Type Select RKL-S 1 Re-Timer
Values: 1 Re-Timer, 2 Re-Timers
This setting determines the number of Re-Timers being used for TYpe-C Port 3
Type-C Port 4 USB3 Ownership RKL-S PCH
Values: CPU/PCH
This setting determines if the Type-C Port 4 USB3 is owned by CPU or PCH.
Type-C Port 4 Connector Type Select RKL-S 1 Re-Timer
Values: 1 Re-Timer, 2 Re-Timers
This setting determines the number of Re-Timers being used for TYpe-C Port 4
Click on GPIO in the left tabs menu> GPIO VCCIO Voltage Control is expanded by default:
2
CpuDetection RKL-S None
Values: Available GPIO
This setting is used in conjunction with the Missing Processor Detection Alert
configuration option to assign an available GPIO.
3
Battery Low / GPD0 Signal Configuration RKL-S Enable as Battery
Values: Enable as Battery Low / Enable as GPD0 Low
This setting allows the user to assign the Battery Low / GPD0 signal as Battery
Low or as GDP0.
Note: For further details see Tiger Lake Platform Controller Hub EDS.
Battery Low / GPD0 Signal Configuration RKL-S Enable as
Values: Enable as SLP_DRAM / Enable as GPP_G5 SLP_DRAM
This setting allows the user to assign the GPP_G5 / SLP_DRAM signal as
SLP_DRAM or as GPP_G5.
Note: For further details see Tiger Lake Platform Controller Hub EDS.
Clockout48 Mode Configuration RKL-S GPP_A16
Values: CLKOUT_48 / GPP_A16
This setting determines the native mode of operation for the CLKOUT_48 signal.
Click on Download and Execute in the left tabs menu> DnX Image is expanded by default:
1
Platform ID RKL-S 0
Value: Hex
This configures the Platform ID that DnX uses to verify the image is correct for the
platform. Before FPFs are fused, this field is ignored and DnX will accept any image.
After FPS lock, only images with this Platform ID will be accepted by DnX.
DnX Fuses
2
DnX Enabled RKL-S Yes
Value: Yes / No
This setting enables / disables DnX.
Click on Intel® Unique Platform ID in the left tabs menu> Intel® Unique Platform ID Configuration is expanded by
default:
1
UPID Supported Feature RKL-S No
Values: Yes/No
Unique Platform ID RKL-S 0x0
Values: Hex
This setting allows OEMs to configure their Unique ID into the platform FPFs.
Click on FW Update Image Build in the left tabs menu> ME Image is expanded by default:
Intel® ME, PMC, OEM KM, IOM, MG, TBT, ISH, iUnit, PCHC and GBST
ME Image
1
ME Binary Image RKL-S ME Binary
Values: Binary File
This loads the Embedded Controller binary that will be merged into the FWUpdate
image generated by the Intel® FIT tool.
Click on FW Update Image Build in the left tabs menu> PMC Image is expanded by default:
2
PMC Max Length
PMC Binary Image RKL-S PMC Binary
Values: Binary File
This loads the PMC binary that will be merged into the FWUpdate image generated
by the Intel® FIT tool.
Click on FW Update Image Build in the left tabs menu> OEM KM Image is expanded by default:
3
OEM KM RKL-S Enabled
Values: Enabled/Disabled
This setting Enables / Disables OEM KM in the FWUpdate image.
OEM KM Max Length
OEM Key Manifest Binary File RKL-S OEM KM Binary
Values: Binary File
This loads the OEM Key manifest binary merged into the output image generated
by the Intel® FIT tool.
Click on FW Update Image Build in the left tabs menu> IOM Image is expanded by default:
4
SAMF RKL-S Enabled
Values: Enabled/Disabled
This setting Enables / Disables SAMF in the FWUpdate image.
SAMF Max Length
SAMF Binary File RKL-S SAMF Binary
Values: Binary File
This loads the SAMF binary merged into the output image generated by the Intel®
FIT tool.
Click on FW Update Image Build in the left tabs menu> MG Image is expanded by default:
PHY Image
5
PHY RKL-S Enabled
Values: Enabled/Disabled
This setting Enables / Disables NPHY in the FWUpdate image.
PHY Max Length
PHY Binary File RKL-S NPHY Binary
Values: Binary File
This loads the NPHY binary merged into the output image generated by the Intel®
FIT tool.
Click on FW Update Image Build in the left tabs menu> ISH Image is expanded by default:
6
ISH RKL-S Enabled
Values: Enabled/Disabled
This setting Enables / Disables ISH in the FWUpdate image.
ISH Max Length
ISH Binary File RKL-S ISH Binary
Values: Binary File
This loads the ISH binary merged into the output image generated by the Intel®
FIT tool.
Click on FW Update Image Build in the left tabs menu> IUNIT Image is expanded by default:
8
PCH Configuration Max Length
Values: Binary File RKL-S PCHC Binary
This loads the PCHC binary merged into the output image generated by the Intel®
FIT tool.
Click on FW Update Image Build in the left tabs menu> GBST Image is expanded by default:
9
GBST Configuration Enable RKL-S Disabled
Values: Enabled/Disabled
This setting Enables / Disables GBST in the FWUpdate image.
GBST Configuration Max Length
Values: Binary File RKL-S GBST Binary
This loads the GBST binary merged into the output image generated by the Intel® (Optional)
FIT tool.
Note: The GBST sub-partition is used to enabling FuSa safety standards and is
not applicable for client platforms.
2
Console shows status of build and path where saved
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 devices. 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 devices accordingly.
Note: Intel® FPT will automatically disable the Intel® ME or EFI prior to flashing the
image to the platform.
fptw.exe -i
The system should respond with the number of SPI Flash device 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.
2. Boot the target system and use F2 or Del to enter the BIOS setup menu. Load
default values for BIOS (on Intel® CRBs press F3 to load default values). Save and
reboot (on Intel® CRBs press F4 and select Yes).
3. Boot the target system to DOS and change to the root directory of the bootable
USB key. At the DOS prompt type:
MEInfo.exe -fwsts
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.
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.
§§
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®Rocket Lake PCH-H / LP Clocks and Intel® Converged Security and Management
Engine — Platform Compliancy Guide for ME Hardware.
§§
The following table describes ICC features supported for specific PCH SKU, clock range
(maximum and minimum), spread mode supported by Rocket Lake-H SKUs.
Note: Please refer to Rocket Lake-H Platform Controller Hub (PCH) External Design
Specification (EDS) for details about Rocket Lake-H Chipset Clock architecture
In below tables,
Q570 x
Z570 x
H570 x
B560 x
H510 x
H510D 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
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.
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.
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.
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.
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.