Board Management Controller User Guide: Intel FPGA Programmable Acceleration Card N3000-N

Download PDF
ID 683186
Date 9/08/2020
Public
Document Table of Contents
Document Table of Contents x
1. Introduction 2. Board Monitoring through PLDM over MCTP SMBus 3. Board Monitoring through I2C SMBus 4. EEPROM Data Format 5. Document Revision History for Board Management Controller User Guide: Intel FPGA Programmable Acceleration Card N3000-N A. Example PLDM Command and Response Messages
1. Introduction x
1.1. About this Document 1.2. Overview 1.3. Root of Trust (RoT) 1.4. Secure Remote System Update 1.5. Power Sequence Management 1.6. Board Monitoring Through Sensors
2. Board Monitoring through PLDM over MCTP SMBus x
2.1. SMBus Interface Speed 2.2. MCTP Packetization Support 2.3. Supported Command Sets 2.4. PLDM Topology and Hierarchy
4. EEPROM Data Format x
4.1. MAC EEPROM 4.2. Field Replaceable Unit Identification (FRUID) EEPROM Access
1. Introduction
2. Board Monitoring through PLDM over MCTP SMBus
3. Board Monitoring through I2C SMBus
4. EEPROM Data Format
5. Document Revision History for Board Management Controller User Guide: Intel FPGA Programmable Acceleration Card N3000-N
A. Example PLDM Command and Response Messages

2.2. MCTP Packetization Support

MCTP Definitions

  • The message body represents the payload of an MCTP message. The message body can span multiple MCTP packets.
  • MCTP packet payload refers to the portion of the message body of an MCTP message that is carried in a single MCTP packet.
  • Transmission Unit refers to the size of the portion of the MCTP packet payload.

Transmission Unit Size

  • The baseline transmission unit (minimum transmission unit) size for MCTP is 64 bytes.
  • All MCTP control messages are required to have a packet payload that is no larger than the baseline transmission unit without negotiation. (The negotiation mechanism for larger transmission units between endpoints is message type-specific and is not addressed in MCTP Base specification)
  • Any MCTP message whose message body size is bigger than 64 bytes shall be split into multiple packets for a single message transmission.
MCTP Packet Fields
Figure 2. Generic Packet/Message Fields
Refer to the table below for more information on message fields.
Message Fields Description
Byte Count Byte counting from byte #4 to the byte right before PEC.
Header Version Set to 0001b for MCTP devices that are conformant to the MCTP Base Specification DSP0237.
SOM, EOM, Pkt Seq #, TO, and Msg Tag Refer to DSP0237 (MCTP SMB us/I2C Transport Binding Spec) and DSP0236 (MCTP Base Spec).
IC Message Integrity Check bit = 0b -> MCTP control and PLDM over MCTP messages do not include an overall Message Integrity check field according to DSP0236 and DSP0241 in respective.
Msg Type 0x00 for MCTP control and 0x01 for PLDM, others are not supported, refer to DSP0239 for more message types.
Rq, D, and Instance ID Refer to the spec DSP0236.
Hdr Ver 0x00 according the spec DSP0240.
PLDM Type 0x00 for PLDM Messaging Control and Discovery, 0x02 for PLDM for Platform Monitoring and Control, only two types here are supported.
PLDM Command Code Refer to the spec DSP0245 for more PLDM types.
PLDM Completion Code* Present only in PLDM response message, refer to the spec DSP0240.
PLDM Message Payload

The fields within PLDM messages are transferred from lower offset (e.g. +0 byte) first. And Unless otherwise specified, byte ordering of multi-byte numeric fields or bit fields is “Big Endian” (that is, the lower byte offset holds the most significant byte, and higher offsets hold lesser significant bytes).

Level Two Title