Thermal Specifications
Description: Deposits the Request Type and associated 4-byte data in the Mailbox
interface and returns a completion code byte with the details of the execution results.
Refer to Section 6.3.4.2 for completion code definitions.
Figure 6-20. MbxSend()
Byte #
0
1
2
3
Byte
Definition
Write Length
0x07
Read Length
0x01
Cmd Code
0xd1
Client Address
4
5
6
7
8
Request Type
LSB
Data[31:0]
MSB
9
10
11
12
Completion
Code
AW FCS
FCS
FCS
Note that the 4-byte data defined above is sent in standard PECI ordering with LSB first
and MSB last.
Table 6-12. MbxSend() Response Definition
Response
Bad FCS
Meaning
Electrical error
CC: 0x4X
CC: 0x80
Semaphore is granted with a Transaction ID of ‘X’
Error causing a response timeout. Either due to a rare, internal timing condition or a
processor RESET condition or processor S1 state. Retry is appropriate outside of the
RESET or S1 states.
CC: 0x86
Mailbox interface is unavailable or busy
If the MbxSend() response returns a bad Read FCS, the completion code can't be
trusted and the semaphore may or may not be taken. In order to clean out the
interface, an MbxGet() must be issued and the response data should be discarded.
6.3.2.8
MbxGet()
The MbxGet() command is utilized for retrieving response data from the generic
Mailbox interface as well as for unlocking the acquired mailbox. Please refer to
Section 6.3.2.7 for details regarding the MbxSend() command. Many of the
fundamental concepts of Mailbox ownership, release, and management are discussed
in Section 6.3.2.9.
6.3.2.8.1
Write Data
The MbxGet() command is designed to retrieve response data from a previously
deposited request. In order to guarantee alignment between the temporally separated
request (MbxSend) and response (MbxGet) commands, the originally granted
Transaction ID (sent as part of the passing MbxSend() completion code) must be issued
as part of the MbxGet() request.
Datasheet Volume 1 of 2
135
INTEL [ INTEL ]
