![American Megatrends MegaRAC M300V User Manual Download Page 81](http://html.mh-extra.com/html/american-megatrends/megarac-m300v/megarac-m300v_user-manual_2924748081.webp)
Chapter Nine : BIOS/Firmware Considerations
75
Chapter 9
BIOS/Firmware Considerations
While OPMA attempts to minimize impacts on existing BIOS, any form of the MegaRAC card
cross-platform compatibility requires some degree of system BIOS support. The main reason for
OPMA specific BIOS support is to enable simple plug and play capability. Under normal
circumstances, the BIOS should not halt the boot process or require keystroke input on any sort of
BMC related error; the absence of the MegaRAC M300V card should never stop a server from
booting up. Any reference in the following paragraphs to BIOS printing messages to the boot
screen should be taken to mean that BIOS must write the indicated message to the text-based
BIOS POST screen that is displayed during POST.
MCard Presence Detect
BIOS must be capable of identifying the presence/absence of the MegaRAC M300V card. This is
done by monitoring the MCARD_PRESENCE_L signal using a BIOS-controlled GPIO that is
typically implemented using the system Southbridge chip. If the GPIO is not available directly
from the chipset, the system must use an alternative solution to read this signal from the
MegaRAC M300V card (for example, an SMBus based GPIO expander).
If the MegaRAC M300V card is found to be present, the BIOS then determines which IPMI
interface to use for sending IPMI commands. BIOS and other system software reads the card
detect signal and then determine the MegaRAC M300V card presence.
Card Detect Signal States
Card Detect State
Meaning
Asserted (Low)
The MegaRAC M300V card is installed in the OPMA
connector.
Deasserted (High)
No mCard is installed in the OPMA connector.
MCard IPMI Command Interface Type Detection
The BIOS must be capable of determining which IPMI interface the MegaRAC M300V card
supports. This is done by monitoring the MCARD_INTERFACE_ID0–CARD_INTERFACE_ID2
signals using BIOS-controlled GPIOs that are typically implemented using the system Southbridge
chip. If the GPIOs are not available directly from the chipset, the system must use an alternative
solution to read the signals from the MegaRAC M300V card (for example, an SMBus-based GPIO
expander).
The value read back from the INTERFACE_ID signals indicates the default IPMI
communications interface supported by the management controller. In cases where the MegaRAC
M300V card supports more than one IPMI interface, these additional interfaces are conveyed
through an IPMI OEM command. BIOS or system software can decide at runtime which interface
to use for IPMI communications.
Summary of Contents for MegaRAC M300V
Page 1: ...MegaRAC M300V Card Implementer s Reference and User s Guide MAN M300V 07 9 07 ...
Page 14: ...8 MegaRAC M300V Card Implementer s Reference and User s Guide ...
Page 16: ...10 MegaRAC M300V Card Implementer s Reference and User s Guide ...
Page 58: ...52 MegaRAC M300V Card Implementer s Reference and User s Guide ...
Page 62: ...56 MegaRAC M300V Card Implementer s Reference and User s Guide ...
Page 80: ...74 MegaRAC M300V Card Implementer s Reference and User s Guide ...
Page 87: ...Index 81 ...