| commit | d237a65d3b12920963951310a015dddbcce03b40 | [log] [tgz] |
|---|---|---|
| author | Carter Chen <carter.chen.wiwynn@gmail.com> | Tue Dec 09 03:16:02 2025 +0000 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Tue Dec 09 20:59:43 2025 +0000 |
| tree | 8fe2e963d7167068db1b13081deb6f9f66f11321 | |
| parent | b249a645fdcd5d9feb0197d2a2fbe3187c369e31 [diff] |
oem-meta: Fix to_hex_string truncation issue for values > 0xFF Description: Change parameter type from uint8_t to uint32_t and fix the format string to properly handle hexadecimal values larger than 0xFF. Motivation: The current implementation truncates values larger than 0xFF due to uint8_t limitation, causing incorrect display in event messages. Change-Id: I791c7f0771d3a2ae7b637ca22fed959d94bc86df Signed-off-by: Carter Chen <carter.chen.wiwynn@gmail.com>
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.
To build and run PLDM, you need the following dependencies:
MesonNinjaAlternatively, source an OpenBMC ARM/x86 SDK.
To build the PLDM project, follow these steps:
meson setup build && meson compile -C build
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.
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
rm /etc/default/pldmd systemctl restart pldmd
For complete documentation on the functionality and usage of this repository, please refer to the docs folder.