COM-HPC-ALT User's Guide
PICMG COM-HPC R1.0
The COM-HPC management platform shall use an IPMI (Intelligent Platform Management Interface) for communication between the Carrier BMC and
MMC, over the COM-HPC IPMB port. The interface from the BMC to the user is independent from this, and may be realized using Redfish, it may
support IPMI for legacy support. The interface used for IPMI between BMC and MMC shall be IPMB (an I2C bus specifically for IPMI use.
As set of IPMI commands for communication between MMC and BMC have been defined in the PICMG COM-HPC Platform Management Interface
Specification. Most of those commands are not specific to COM-HPC, but defined in the IPMI specification and related specifications. However, also
some COM-HPC specific commands have been developed. Specifically, the following command sets are covered:
- IPM Device Global Commands: Initialization and module discovery
- BMC Watchdog and Device and Messaging Commands: System interface and BMC interaction.
- Chassis Device Commands: Power control and boot options
- Event Commands: IPMI event handling
- PEF and Alerting Commands: Alerting and trigger support
- Sensor Device Commands: Sensor monitoring and housekeeping
- FRU Device Commands: Inventory data
- SDR Device Commands: Sensor information
- SEL Device Commands: System event logging
- LAN Device Commands and HPM.2: Support for Ethernet
- Serial/Modem Device Commands: For UART and SOL support
- AdvancedTCA subset: For Fan Management
- HPM.1: For Firmware update
- HPM.2: For managing BMC-MMC Ethernet communication
- COM-HPC specific Commands: For fast sensors and JTAG support
The inventory data available via IPMI FRU also includes information present in the COM-HPC EEPROM (see Section Error! Bookmark not defined.). The
COM-HPC EEPROM content is defined in the PICMG Embedded EEPROM for COM-HPC document, a companion document to the PICMG COM-HPC
Platform Management Interface Specification. The information available in the COM-HPC EEPROM area will be converted from EeeP format into
IPMI FRU data structures by the MMC. In order to accomplish this, the MMC reads the data from the EEPROM during start of the system, and buffers
the data internally to service incoming IPMI FRU accesses.
The EEPROM area for storing EeeP data may be implemented as a physical EEPROM on the board, on the I2C0 bus. Alternatively, it may be realized
within the MMC. This is illustrated in Figure 10 above. In that figure, it is labeled as an "emulated EEPROM". An I2C slave interface on the MMC is
Page 15
Copyright © 2023 ADLINK Technology, Inc.
Need help?
Do you have a question about the arm AMPERE COM-HPC-ALT and is the answer not in the manual?