Google GitGoogle Git
Sign in
gbmc/pldm/e0ea17efc683421a60aacbf1292a4244913dcf85
commit
e0ea17efc683421a60aacbf1292a4244913dcf85
[log]
author
Luka Strizic <lstrz@google.com>
Thu Jul 09 12:42:23 2026 -0700
committer
Luka Strizic <lstrz@google.com>
Fri Aug 14 09:55:59 2026 -0700
tree
ff6d6890fa9b05805174441dd790854aa1dc09d6
parent
fd3375ba9e8935bdb7b23263d9f53fb292c5e081 [diff]
platform-mc: Suppress expected discovery errors

Downgraded various expected discovery conditions from errors to
warnings to match the legacy pldmd-google behavior and reduce
log spam.
- In terminus.cpp, downgraded unsupported FRU Record ID types
  to warning.
- In platform_manager.cpp, gracefully handle unsupported
  SetEventReceiver command by returning PLDM_SUCCESS and
  logging a warning.
- In mctp_endpoint_discovery.cpp, explicitly handle missing
  UUID interfaces by logging a warning instead of an error.

Tested:
Verified that the previously observed errors for unsupported
FRU types, missing event receiver support, and missing
MCTP UUID interfaces are no longer generated as errors in the
system log on platform31, matching the baseline log output.

Change-Id: I177c3bc10a860fc26fecf360ff0b15cb97aff7ba
Google-Bug-Id: 458166668
Signed-off-by: Luka Strizic <lstrz@google.com>
3 files changed
tree: ff6d6890fa9b05805174441dd790854aa1dc09d6
  1. common/
  2. configurations/
  3. docs/
  4. fw-update/
  5. fw-update-legacy/
  6. host-bmc/
  7. libpldmresponder/
  8. oem/
  9. platform-mc/
  10. pldmd/
  11. pldmtool/
  12. requester/
  13. softoff/
  14. subprojects/
  15. test/
  16. tools/
  17. utilities/
  18. .clang-format
  19. .clang-tidy
  20. .eslintignore
  21. .gitignore
  22. .linter-ignore
  23. LICENSE
  24. meson.build
  25. meson.options
  26. OWNERS
  27. 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.