Intel E5-2470 CM8062007187242 User Manual

Product codes
CM8062007187242
Page of 258
66
Intel® Xeon® Processor E5-1600/E5-2600/E5-4600 Product Families
Datasheet Volume One
2.5.2.9.1
Command Format
The RdPCIConfigLocal() format is as follows:
Write Length: 0x05
Read Length: 0x02 (byte), 0x03 (word), 0x05 (dword)
Command: 0xe1
Description: Returns the data maintained in the PCI configuration space within the 
processor at the requested PCI configuration address. The Read Length dictates the 
desired data return size. This command supports byte, word and dword responses as 
well as a completion code. All command responses are prepended with a completion 
code that includes additional pass/fail status information. Refer to 
details regarding completion codes.
Note:
The 3-byte PCI configuration address and read data field defined in 
 are sent in standard PECI ordering with 
LSB first and MSB last.
2.5.2.9.2
Supported Responses
The typical client response is a passing FCS, a passing Completion Code and valid data. 
Under some conditions, the client’s response will indicate a failure.
The PECI client response can also vary depending on the address and data. It will 
respond with a passing completion code if it successfully submits the request to the 
appropriate location and gets a response. 
Figure 2-47. RdPCIConfigLocal()
0
1
2
3
Byte #
FCS
12
7
9
Completion
Code
LSB         PCI Configuration Address       MSB
10
Write Length
0x05
LSB                    Data (1, 2 or 4 bytes)                                 MSB
5
Cmd Code
0xe1
14
Read Length
{0x02,0x03,0x05}
6
8
Host ID[7:1] & 
Retry[0]
Client Address
13
4
11
FCS
Byte 
Definition
Table 2-13. RdPCIConfigLocal() Response Definition  (Sheet 1 of 2)
Response
Meaning
Bad FCS
Electrical error
Abort FCS
Illegal command formatting (mismatched RL/WL/Command Code)
CC: 0x40
Command passed, data is valid.
CC: 0x80
Response timeout. The processor was not able to generate the required response in a 
timely fashion. Retry is appropriate.
CC: 0x81
Response timeout. The processor is not able to allocate resources for servicing this 
command at this time. Retry is appropriate.