| commit | c97dc12836f314d4c93e76d3ec465524c47dafc5 | [log] [tgz] |
|---|---|---|
| author | rajeeranjan <ranjan.rajeev1609@gmail.com> | Mon Jun 30 12:02:09 2025 +0530 |
| committer | Rajeev Ranjan <ranjan.rajeev1609@gmail.com> | Wed Oct 22 22:55:05 2025 +0530 |
| tree | bed2c8bb376f57ceb8489ba171aab601f3630e88 | |
| parent | 2ca14ceefd207ec6994ec9516553807d7efa6630 [diff] |
fw_update: Create FirmwareInventory entries per component Previously, only a single firmware inventory entry was created per device (with component identifier 0 and image set version). This didn't properly represent devices with multiple firmware components in the Redfish FirmwareInventory collection. Fix is to create individual FirmwareInventory entry for each firmware component, with: - Individual component version strings - Component-specific naming (Device_Name_Component_<ID>) This allows proper representation of multi-component firmware devices in Redfish, where each component appears as a separate updatable firmware resource. Tested: Verified all firmware components appear in FirmwareInventory and each component shows its individual version on B40: ''' curl -k https://root:0penBmc@localhost/redfish/v1/UpdateService/FirmwareInventory { "Members": [ { "@odata.id": "/redfish/v1/UpdateService/FirmwareInventory/PLDM_Device_Firmware_Device_12_Component_65282_1913" }, { "@odata.id": "/redfish/v1/UpdateService/FirmwareInventory/PLDM_Device_Firmware_Device_13_Component_49152_73" }, { "@odata.id": "/redfish/v1/UpdateService/FirmwareInventory/PLDM_Device_Firmware_Device_13_Component_49168_8233" } ], "Members@odata.count": 4 } curl -k https://root:0penBmc@localhost/redfish/v1/UpdateService/FirmwareInventory/PLDM_Device_Firmware_Device_13_Component_49152_73 { "@odata.type": "#SoftwareInventory.v1_1_0.SoftwareInventory", "Id": "PLDM_Device_Firmware_Device_13_Component_49152_73", ... "Version": "98.02.90.00.00" } ''' Change-Id: I5c91de3a886a4335e7357f4498db787624f330d1 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.