Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / pldm / 44f8804574581ab063cde67fa5bf2da491e4dd88
commit44f8804574581ab063cde67fa5bf2da491e4dd88[log] [tgz]
authorPavithra Barithaya <pavithrabarithaya07@gmail.com>Mon Aug 19 15:36:29 2024 +0530
committerManojKiran Eda <manojkiran.eda@gmail.com>Tue Sep 23 08:56:19 2025 +0000
treeff640fcbbbe1f4516e0831d409371bc4f00b7013
parent3419e180c971ec9d30114d98d0b63c83625ec516 [diff]
oem-ibm: Fix in pointer increment in the PCIe Config Data

The PCIe Config data is a 64 bytes huge data which needs to be
parsed and corresponding DBus values needs to be updated. The
parsing logic had a pointer increment issue that resulted in
some bug w.r.t the values.

The pointer incrementation here is for FRU Record Data -
SPEC - DSP0257_1.0.0 - Table 2 – PLDM FRU Record Data Format.

When we get a SetFruRecordTable command(Table 11) we have a portion
of FRU record data that needs to be parsed and updated and this
FRU Record data can be one or more.

The data here corresponds to the size of the whole
pldm_fru_record_data_format and based on the number of FRU fields
present we need to update the data pointer based on the FRU Field
Length.

Tested: Checked the DBus values are populated.

Change-Id: I35540565557d43acf6a58be540f7d8f6db7483a9
Signed-off-by: Pavithra Barithaya <pavithrabarithaya07@gmail.com>
1 file changed
tree: ff640fcbbbe1f4516e0831d409371bc4f00b7013
  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.