Management Engine (ME). This includes the definition of event data bytes 10-16 of the
Request
Byte 1 - EvMRev
=04h (IPMI2.0 format)
Byte 2 – Sensor Type
=DCh (OEM)
Byte 3 – Sensor Number
=23 – Server Platform Services Firmware Health
Byte 4 – Event Dir | Event Type
[7] – Event Dir
=0 Assertion Event
[6-0] – Event Type
=75h (OEM)
Byte 5 – Event Data 1
[7,6]=10b – OEM code in byte 2
[5,4]=10b – OEM code in byte 3
[3..0] – Health Event Type
=00h –Firmware Status
Byte 6 – Event Data 2
=0 - Forced GPIO recovery. Recovery Image loaded due to MGPIO<n>
(default recovery pin is MGPIO1) pin asserted.
Repair action: Deassert MGPIO1 and reset the ME
=1 - Image execution failed. Recovery Image loaded because
operational image is corrupted. This may be either caused by Flash
device corruption or failed upgrade procedure.
Repair action: Either the Flash device must be replaced (if error is
persistent) or the upgrade procedure must be started again.
=2 - Flash erase error. Error during Flash erases procedure probably
due to Flash part corruption.
Repair action: The Flash device must be replaced.
=3 – Flash corrupted. Error while checking Flash consistency probably
due to Flash part corruption.
Repair action: The Flash device must be replaced (if error is
persistent).
=4 – Internal error. Error during firmware execution.
Repair action: FW Watchdog Timeout
Operational image shall be upgraded to other version or hardware
board repair is needed (if error is persistent).
=5..255 – Reserved
Byte 7 – Event Data 3
=<Extended error code. Should be used when reporting an error to the
support>