Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / pldm / e7b4f07d071fdfc25df0bcbb17cd50b075eb0265
commite7b4f07d071fdfc25df0bcbb17cd50b075eb0265[log] [tgz]
authorEric Yang <eric.yang.wiwynn@gmail.com>Wed Sep 24 08:20:46 2025 +0000
committerManojKiran Eda <manojkiran.eda@gmail.com>Thu Oct 09 04:59:35 2025 +0000
tree73410bd8083cefe53539678245c1fd5ae7ad054c
parent2965f7da346fa3542a4d81a042cbb5a228cb46d6 [diff]
platform-mc: Clarify SetTID failure logging

Simplify the failure path to a single branch:
when SetTID fails, emit a specific message for devices that do not
support the command; otherwise report a general failure.

Motivation:
Remove unreachable and contradictory checks and make failure messages
clearer without altering behavior.

Change-Id: Ia8a0dfbdbc451fa2f2a173ae8b11d1dedef9fd27
Signed-off-by: Eric Yang <eric.yang.wiwynn@gmail.com>
1 file changed
tree: 73410bd8083cefe53539678245c1fd5ae7ad054c
  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.