Thermal Specifications
Any mailbox request made with an illegal or unlocked Transaction ID will get a failed
completion code response. If the Transaction ID matches an outstanding transaction ID
associated with a locked mailbox, the command will complete successfully and the
response data will be returned to the originator.
Unlike MbxSend(), no Assured Write protocol is necessary for this command because
this is a read-only function.
6.3.2.8.2
Command Format
The MbxGet() format is as follows:
Write Length: 2
Read Length: 5
Command: 0xd5
Multi-Domain Support: Yes (see Table 6-15)
Description: Retrieves response data from mailbox and unlocks / releases that
mailbox resource.
Figure 6-21. MbxGet()
Byte #
0
1
2
3
Byte
Definition
Write Length
0x02
Read Length
0x05
Cmd Code
0xd5
Client Address
4
150
161
Completion
Code
Transaction ID
FCS
7
1850
1961
10
MSB
11
LSB
Response Data[31:0]
FCS
Note that the 4-byte data response defined above is sent in standard PECI ordering
with LSB first and MSB last.
Table 6-13. MbxGet() Response Definition
Response
Meaning
Aborted Write FCS Response data is not ready. Command retry is appropriate.
CC: 0x40
CC: 0x80
Command passed, data is valid
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: 0x81
CC: 0x82
CC: 0x83
CC: 0x84
Thermal configuration data was malformed or exceeded limits.
Thermal status mask is illegal
Invalid counter select
Invalid Machine Check Bank or Index
136
Datasheet Volume 1 of 2
INTEL [ INTEL ]
