Datasheet

Intel
®
Xeon
®
Processor C5500/C3500 Series
February 2010 Datasheet, Volume 1
Order Number: 323103-001 87
Interfaces
2.2.4 Client Responses
2.2.4.1 Abort FCS
The Client responds with an Abort FCS (See the RS - Platform Environment Control
Interface (PECI) Specification) under the following conditions:
• The decoded command is not understood or not supported on this processor (this
includes good command codes with bad Read Length or Write Length bytes).
• Data is not ready.
• Assured Write FCS (AW FCS) failure. Under most circumstances, an Assured Write
failure will appear as a bad FCS. However, when an originator issues a poorly
formatted command with a miscalculated AW FCS, the client will intentionally abort
the FCS in order to guarantee originator notification.
2.2.4.2 Completion Codes
Some PECI commands respond with a completion code byte. These codes are designed
to communicate the pass/fail status of the command and also provide more detailed
information regarding the class of pass or fail. For all commands listed in Section 2.2.2
that support completion codes, each command’s completion codes is listed in its
respective section. What follows are some generalizations regarding completion codes.
An originator that is decoding these commands can apply a simple mask to determine
pass or fail. Bit 7 is always set on a failed command, and is cleared on a passing
command.
Table 40. Domain ID Definition
Domain ID Domain Number
0b01 0
0b10 1
Table 41. Multi-Domain Command Code Reference
Command Name
Domain 0
Code
Domain 1
Code
GetTemp() 0x01 0x02
PCIConfigRd() 0xC1 0xC2
PCIConfigWr() 0xC5 0xC6
MbxSend() 0xD1 0xD2
MbxGet() 0xD5 0xD6
Table 42. Completion Code Pass/Fail Mask
0xxx xxxxb Command passed
1xxx xxxxb Command failed