The expected Status of the mismatch FRU / FW between HPM and DC-SCM

[wulingchang]

Hi all,

• Per https://drive.google.com/file/d/1LJoHoI2L-UYKFeGAMR_BWSy12K665CUP/view, it mentions
  "The DC-SCM specification attempts to support maximum electrical and mechanical interoperability between all DC-SCMs and HPMs, ... Through adherence to such a design specification, a development model called "Plug-and-Code" can be achieved, making possible multi-vendor HPM/DC-SCM interoperability via changes to BMC firmware, DC-SCM CPLD and HPM FPGA firmware."
  " "If the HPM FRU is deemed incompatible or goes undetected, the DC-SCM must halt the boot sequence, to avoid possible electrical stress conditions. This is called “Plug-N-Detect-ElseHalt”"
• That's to say, it may happen mismatch FRU / FW between HPM and DC-SCM and it is required to resolve it via FW operation via DC-SCM
• In addition, per https://www.opencompute.org/documents/ocp-hpm-common-circuit-type-1-design-spec-rev1p0-ver1p00-pdf, it mentions
  "All devices must be powered from VCC_SCM_HPM_FRU or have bus isolation"
  "HPM FRU EEPROM Write Protect is highly recommended for to be HPM FPGA controlled "
  "Potential use case: Early HPM Type and FPGA version discovery, DC-SCM-to-HPM FPGA
  attestation, update, and recovery"

So I would consider the expected status below and hope that there would not be misunderstanding.

[Mismatch of FRU]

• The Health / Status of schema assembly of HPM is Critical / UnavailableOffline (HPM is halted by DC-SCM)
• The Health / Status of schema assembly of DC-SCM is OK / Enabled

[Mismatch of FW version]

• The Health / Status of schema Chassis of HPM is Critical / UnavailableOffline (HPM is halted by DC-SCM)
• The Health / Status of schema Chassis of DC-SCM is OK / Enabled

Thank you
Best Regards
Wuling Chang

[jcleung5549]

@wulingchang - will you be able to attend the Profile workstream meeting tomorrow (6/2 8am PT)?