| commit | 11085f1bd8bc53d7ed142116d18c91ab67c29668 | [log] [tgz] |
|---|---|---|
| author | Rajeev Ranjan <ranjan.rajeev1609@gmail.com> | Fri Aug 29 20:58:29 2025 +0530 |
| committer | Rajeev Ranjan <ranjan.rajeev1609@gmail.com> | Thu Oct 30 14:01:21 2025 +0000 |
| tree | ef111282975155f4ca5fe23ad99bbd6034449e70 | |
| parent | 34f902598235f9e5fb4e35b8c19c5e21c83e6cc9 [diff] |
Expose Software.MultipartUpdate on PLDM update object Expose the xyz.openbmc_project.Software.MultipartUpdate interface [1] alongside xyz.openbmc_project.Software.Update on the PLDM update object (/xyz/openbmc_project/software/pldm). This allows clients (e.g., bmcweb) to discover a single multipart-capable update entity when no targets are specified, while continuing to use StartUpdate for image transfer. PLDM continues to handle multi-component updates internally. [1] https://gerrit.openbmc.org/c/openbmc/phosphor-dbus-interfaces/+/78905 Tests: - FW Update using Multipart URI ``` curl -X POST -k https://{ip}/redfish/v1/UpdateService/update-multipart --form 'UpdateParameters={"Targets":[]};type=application/json' --form "UpdateFile=@vbios.fwpkg;type=application/octet-stream" { "@odata.id": "/redfish/v1/TaskService/Tasks/0", "@odata.type": "#Task.v1_4_3.Task" ... "PercentComplete": 0, "StartTime": "2025-08-05T13:33:23+00:00", "TaskMonitor": "/redfish/v1/TaskService/TaskMonitors/0", "TaskState": "Running", "TaskStatus": "OK" } ``` Signed-off-by: Rajeev Ranjan <ranjan.rajeev1609@gmail.com> Change-Id: I11b21ae1df1862166cce16e4d9804c80cef79ecc Signed-off-by: Rajeev Ranjan <ranjan.rajeev1609@gmail.com>
- common/
- configurations/
- docs/
- fw-update/
- host-bmc/
- libpldmresponder/
- oem/
- platform-mc/
- pldmd/
- pldmtool/
- requester/
- softoff/
- subprojects/
- test/
- tools/
- utilities/
- .clang-format
- .clang-tidy
- .eslintignore
- .gitignore
- .linter-ignore
- LICENSE
- meson.build
- meson.options
- OWNERS
- README.md
PLDM - Platform Level Data Model
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:
MesonNinja
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.