Intel C2550 FH8065401488912 データシート
製品コード
FH8065401488912
Intel
®
Atom™ Processor C2000 Product Family for Microserver
September 2014
Datasheet, Vol. 2 of 3
Order Number: 330061-002US
385
Volume 2—SMBus 2.0 Unit 2 - PECI—C2000 Product Family
PECI Over SMBus
17.6.2.1
PECI Proxy Command Format
The SoC has no Manageability Engine (ME). Unlike some Intel Peripheral Controller Hub
(PCH) products, the SoC PECI-over-SMBus controller only operates in PECI mode. The
SMBus Interface PECI Proxy Command Protocol is an encapsulation of PECI
specification commands onto the SMBus by the SMBus master. Two new SoC-specific
PECI commands are also supported.
The PECI proxy command bytes, encapsulated in bytes [N:2] of the protocol, conform
to
and the RS - Platform
Environment Control Interface (PECI) Specification, Revision 3.0. The SoC PECI-over-
SMBus controller provides a transparent pass-through of the PECI command to the
integrated PECI client and does not verify the validity of the command. It is the burden
of the BMC or platform board External Circuitry (EC) to provide valid data in the PECI
Proxy Command fields of the incoming packet.
Because the SMBus is used and not the serial PECI electrical interface, it is unnecessary
to calculate the Frame Check Sequence (FCS). The SoC design does keep the PECI
commands consist with non-SoC Intel products and carry additional bytes that are set
to 0x0. These are called out where appropriate. The PECI Proxy Command Format is
shown in
Table 17-5. PECI Proxy Command Protocol Format
PECI Proxy Command
SMBus Default Data
SMBus to
PECI
Handshake
Control
Data
PECI Command Data as Described for Each
Supported PECI Command in the PECI
Specification
Slave
Address
PECI
Mode
Command
Code
Byte
Count
Byte 1
Byte 2
Byte 3
Byte 4
Byte [N:5]
0x4C
(default)
0x62
0x04...N
Control Byte
(Reserved)
PECI Target
Address
1
0x30 =
CPU
1. Required PECI Header byte.
PECI Write
Length
2
2. Required PECI Header byte. Must be set to the proper value as defined by the particular PECI Command. If an
Assured Write FCS (AW FCS) is needed, the PECI Write Length value must also include the AW FCS byte.
PECI Read
Length
3
3. Required PECI Header byte. Must be set to the proper value as defined by the particular PECI Command.
Remaining
Part of
PECI
Command
4
4. This field does not exist for the PECI Ping() command. This field is used for write data bytes including a
placeholder for an AW FCS byte. Note that the Retry bit shall be set to zero and the command code byte must
be one of the codes supported by the SoC.