platform-mc: Close CPER file before creating dump

Close the temporary CPER file before creating the
FaultLog dump entry. This ensures phosphor-debug-collector
observes the final CPER file size when it records
the dump entry Size property.

Without this ordering, PLDM-created FaultLog Redfish entries
can report AdditionalDataSizeBytes as zero because the
CPER data may still be buffered in pldmd.

Tested:

'''
Cherry-pick below patch onto phosphor-debug-collector:
https://gerrit.openbmc.org/c/openbmc/phosphor-debug-collector/+/91083
Cherry-pick below patch onto bmcweb:
https://gerrit.openbmc.org/c/openbmc/bmcweb/+/91085

Send a CPER through pldm

root@phoenix-crb-1-9082C309C448:/var/cper# ls -al
drwxr-xr-x    2 root     root             0 Apr 30 08:23 .
drwxr-xr-x    1 root     root             0 Apr 30 05:04 ..
-rw-------    1 root     root           424 Apr 30 08:23 cper-BFgwBK

curl -k -u root:0penBmc -X GET https://{BMC_IP}/redfish/v1/Managers/bmc/LogServices/FaultLog/Entries/3

{
  "@odata.id": "/redfish/v1/Managers/bmc/LogServices/FaultLog/Entries/3",
  "@odata.type": "#LogEntry.v1_11_0.LogEntry",
  "AdditionalDataSizeBytes": 424,
  "AdditionalDataURI": "/redfish/v1/Managers/bmc/LogServices/FaultLog/Entries/3/attachment",
  "Created": "2026-04-17T07:07:24.775620+00:00",
  "EntryType": "Event",
  "Id": "3",
  "Name": "FaultLog Dump Entry"
}

'''

Change-Id: I65cf49b4b8342a1f9365463cc6aebe51315f4c6d
Signed-off-by: Meghana H <Meghana.H@arm.com>
1 file changed
tree: 93370d4efa1f4eafc0d4dac8242f30b49c6753ef
  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.