Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / pldm / refs/heads/master
commit58b6663575555d2a6cbc17e89d408ec5690d470a[log] [tgz]
authorJayashankar Padath <jayashankarpadath@gmail.com>Mon Jan 12 07:17:46 2026 -0600
committerManojKiran Eda <manojkiran.eda@gmail.com>Wed Jan 28 05:31:50 2026 +0000
treee84dc945a5cc58ff3c961b38114ec5bc6a8d0f51
parentacf7579247282c9a2dbee93850f459cc88a5419c [diff]
pldm: PDR and FRU VPD additions in Huygens system

This commit contains below changes related to Huygens system
1. Addition of PDR folder and added the required FRUs for
   switch  board and three other chassis
2. Added new FRU VPD keywords for System, Chassis and Board
   a. System - Added full set of UTIL and VSBP keywords
   b. Chassis - Missing keywords DR, RB, RG and TM are added
   c. Board - Newly added full set of keywords such as VCFG,
      VINI, VMPU, VR10, VW10 and Location Code
3. Updated the FRU master json with core entity id and the
   pldmtool with processor core name

Tested By:
Verified the changes in the Huygens simics setup

Change-Id: I89bb59d04a9372345bb73af3610f29d0a0115eb1
Signed-off-by: Jayashankar Padath <jayashankarpadath@gmail.com>
14 files changed
tree: e84dc945a5cc58ff3c961b38114ec5bc6a8d0f51
  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.