Google GitGoogle Git
Sign in
gbmc/pldm/1602b362455e3f87dae4b314c61e8a4df2d8e260
commit
1602b362455e3f87dae4b314c61e8a4df2d8e260
[log]
author
Vishnunithyasoundhar S <vishnunithyasoundhar.s@intel.com>
Wed Apr 08 15:40:45 2026 +0530
committer
ManojKiran Eda <manojkiran.eda@gmail.com>
Wed Apr 15 06:07:51 2026 +0000
tree
3f777552d5b10171a2621528c750b3c57defbb0d
parent
7e18c415c8254142125befd6fe925a8757b12d64 [diff]
platform-mc: fix infinite retry on FRU record table response error

In getFRURecordTable() and getFRURecordTableMetadata(), when the PLDM
response decode succeeds but the completion code is non-zero, rc is 0
(PLDM_SUCCESS) at that point. Returning rc instead of completionCode
caused the caller getFRURecordTables() to treat the error as success
and loop indefinitely, flooding the log with repeated errors like:

  Error : GetFRURecordTable for terminus ID 1, complete code 128.

Fix by returning completionCode when it is non-PLDM_SUCCESS, so the
caller exits the transfer loop correctly.

Change-Id: I35bb9535ac3aeeb12e842ddce48988e1f1a04418
Signed-off-by: Vishnunithyasoundhar S <vishnunithyasoundhar.s@intel.com>
Co-developed-by: Arun P. Mohanan <arun.p.m@intel.com>
1 file changed
tree: 3f777552d5b10171a2621528c750b3c57defbb0d
  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.