Google GitGoogle Git
Sign in
gbmc/pldm/318b9dd61681f39e181338bee3873a1a5f71a65e
commit
318b9dd61681f39e181338bee3873a1a5f71a65e
[log]
author
Freddie Jheng <Freddie.Jheng@quantatw.com>
Mon Sep 07 16:23:34 2026 +0800
committer
Patrick Williams <patrick@stwcx.xyz>
Mon Sep 14 18:21:07 2026 +0000
tree
552a998b31456c3ade093ff4ebcd7f31b9dbddf7
parent
993b0e375027b5a13ea93f5d585a803ed0e67628 [diff]
oem-meta: santabarbara: add handler for event logs from Arke MMC

Add support for decoding the event logs emitted by the Arke MMC.

Tested on santabarbara:
Triggered ARKE_OWL_E_TRVDD0P75 voltage regulator faults on the Arke
MMC of Electra module 0 and module 2 from separate consoles.

```
    "909": {
        "additional_data": {
            "FAILURE_DATA": "ARKE_OWL_E_TRVDD0P75 - [00 00]",
            "VOLTAGE_REGULATOR": "/xyz/openbmc_project/inventory/system/board/Santa_Barbara_Electra_module_0/owl_e_trvdd0p75"
        },
        "message": "xyz.openbmc_project.State.Power.VoltageRegulatorFault",
        "redfish": {
            "id": "OpenBMC_StatePower.VoltageRegulatorFault",
            "message": "A fault has been detected on voltage regulator '/xyz/openbmc_project/inventory/system/board/Santa_Barbara_Electra_module_0/owl_e_trvdd0p75'"
        },
        "severity": "xyz.openbmc_project.Logging.Entry.Level.Error",
        "timestamp": "2026-09-08T10:46:04.129000000Z"
    },
    "910": {
        "additional_data": {
            "FAILURE_DATA": "ARKE_OWL_E_TRVDD0P75 - [00 00]",
            "VOLTAGE_REGULATOR": "/xyz/openbmc_project/inventory/system/board/Santa_Barbara_Electra_module_2/owl_e_trvdd0p75"
        },
        "message": "xyz.openbmc_project.State.Power.VoltageRegulatorFault",
        "redfish": {
            "id": "OpenBMC_StatePower.VoltageRegulatorFault",
            "message": "A fault has been detected on voltage regulator '/xyz/openbmc_project/inventory/system/board/Santa_Barbara_Electra_module_2/owl_e_trvdd0p75'"
        },
        "severity": "xyz.openbmc_project.Logging.Entry.Level.Error",
        "timestamp": "2026-09-08T10:46:25.472000000Z"
    }
```

Change-Id: Icccd075aa6215f2e071a62838a70b9aa9c5c3ae7
Signed-off-by: Freddie Jheng <Freddie.Jheng@quantatw.com>
1 file changed
tree: 552a998b31456c3ade093ff4ebcd7f31b9dbddf7
  1. common/
  2. configurations/
  3. docs/
  4. fw-update/
  5. host-bmc/
  6. libpldmresponder/
  7. oem/
  8. platform-mc/
  9. pldmd/
  10. pldmtool/
  11. requester/
  12. softoff/
  13. subprojects/
  14. test/
  15. tools/
  16. utilities/
  17. .clang-format
  18. .clang-tidy
  19. .eslintignore
  20. .gitignore
  21. .linter-ignore
  22. LICENSE
  23. meson.build
  24. meson.options
  25. OWNERS
  26. README.md
README.md

PLDM - Platform Level Data Model

License

Overview

PLDM (Platform Level Data Model) is a key component of the OpenBMC project, providing a standardized data model and message formats for various platform management functionalities. It defines a method to manage, monitor, and control the firmware and hardware of a system.

The OpenBMC PLDM project aims to implement the specifications defined by the Distributed Management Task Force (DMTF), allowing for interoperable management interfaces across different hardware and firmware components.

Features

  • Standardized Messaging: Adheres to the DMTF's PLDM specifications, enabling consistent and interoperable communication between different components.
  • Modularity: Supports multiple PLDM types, including base, FRU,Firmware update, Platform Monitoring and Control, and BIOS Control and Configuration.
  • Extensibility: Easily extendable to support new PLDM types and custom OEM commands.
  • Integration: Seamlessly integrates with other OpenBMC components for comprehensive system management.

Getting Started

Prerequisites

To build and run PLDM, you need the following dependencies:

  • Meson
  • Ninja

Alternatively, source an OpenBMC ARM/x86 SDK.

Building

To build the PLDM project, follow these steps:

meson setup build && meson compile -C build

To run unit tests

The simplest way of running the tests is as described by the meson man page:

meson test -C build

Alternatively, tests can be run in the OpenBMC CI docker container using these steps.

To enable pldm verbosity

pldm daemon accepts a command line argument --verbose or --v or -v to enable the daemon to run in verbose mode. It can be done via adding this option to the environment file that pldm service consumes.

echo 'PLDMD_ARGS="--verbose"' > /etc/default/pldmd
systemctl restart pldmd

To disable pldm verbosity

rm /etc/default/pldmd
systemctl restart pldmd

Documentation

For complete documentation on the functionality and usage of this repository, please refer to the docs folder.