pldmtool: send the allocated instance ID

exec() declared a local instanceId that shadowed the member of the same
name, so the ID allocated from the instance ID database never reached
createRequestMsg() and every request went out with instance ID 0.

Assign to the member instead.

Tested: successive requests of "pldmtool platform GetPDR -a -m 14 -v".
The instance ID is the low 5 bits of the first header byte.

Before, every request goes out with instance ID 0:

  Tx: 80 02 51 34 00 00 00 00 00 00 00 01 ff ff 00 00
  Tx: 80 02 51 35 00 00 00 00 00 00 00 01 ff ff 00 00
  Tx: 80 02 51 36 00 00 00 00 00 00 00 01 ff ff 00 00
  Tx: 80 02 51 37 00 00 00 00 00 00 00 01 ff ff 00 00

After, the instance ID increments per request:

  Tx: 87 02 51 08 00 00 00 00 00 00 00 01 ff ff 00 00
  Tx: 88 02 51 09 00 00 00 00 00 00 00 01 ff ff 00 00
  Tx: 89 02 51 0a 00 00 00 00 00 00 00 01 ff ff 00 00
  Tx: 8a 02 51 0b 00 00 00 00 00 00 00 01 ff ff 00 00
  Tx: 8b 02 51 0c 00 00 00 00 00 00 00 01 ff ff 00 00
  Tx: 8c 02 51 0d 00 00 00 00 00 00 00 01 ff ff 00 00

Change-Id: I67c2586f1964171e6605170eca2a662e2c2cf427
Signed-off-by: Aditya Kurdunkar <adityakurdunkar2@gmail.com>
1 file changed
tree: 9ef400105fe2500ab7a42e10bf97f3e89db29c6f
  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.