Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-vpd-parser / 37ce6e3966d425193d6edfc3ba30352c36619ab5
commit37ce6e3966d425193d6edfc3ba30352c36619ab5[log] [tgz]
authorAlpana Kumari <alpankum@in.ibm.com>Thu Oct 23 06:37:59 2025 -0500
committerSunnySrivastava <sunnsr25@in.ibm.com>Fri Nov 07 13:17:00 2025 +0000
tree4aa571af114fcaa1cf1e0509fe5c9822c6abe37b
parentb5fab80a2955b33d56c07f47bf5c20057b3d1de3 [diff]
Add a flag to logger

This commit adds one config flag in meson, to be used at build time.This
flag is to decide whether the logs will dump in a file or will go to the
console by default.

Test:
Image built with file logging enabled, and so all the logs are part of
log file.

$cat /var/lib/vpd/test.log |grep -i  "sanity"
FileName: /usr/src/debug/openpower-fru-vpd/1.0+git/vpd-manager/src/
logger.cpp, Line: 59 Performing sanity check for file path: /sys/bus/
spi/drivers/at25/spi12.0/eeprom

FileName: /usr/src/debug/openpower-fru-vpd/1.0+git/vpd-manager/src/
logger.cpp, Line: 59 Sanity checker Passed for /sys/bus/spi/drivers/
at25/spi12.0/eeprom

FileName: /usr/src/debug/openpower-fru-vpd/1.0+git/vpd-manager/src/
logger.cpp, Line: 59 Performing sanity check for file path: /sys/bus/
spi/drivers/at25/spi13.0/eeprom

FileName: /usr/src/debug/openpower-fru-vpd/1.0+git/vpd-manager/src/
logger.cpp, Line: 59 Sanity checker Passed for /sys/bus/spi/drivers/
at25/spi13.0/eeprom
~#

Change-Id: I3239683e643a06eeda6b0d23678c16bcf7cdf121
Signed-off-by: Alpana Kumari <alpankum@in.ibm.com>
2 files changed
tree: 4aa571af114fcaa1cf1e0509fe5c9822c6abe37b
  1. configuration/
  2. docs/
  3. service_files/
  4. test/
  5. vpd-manager/
  6. vpd-tool/
  7. vpdecc/
  8. wait-vpd-parser/
  9. .clang-format
  10. .gitignore
  11. LICENSE
  12. meson.build
  13. meson.options
  14. OWNERS
  15. README.md
README.md

Overview

This repository hosts code for OpenPower and IBM IPZ format VPD parsers. Both OpenPower VPD and IPZ VPD formats are structured binaries that consist of records and keywords. A record is a collection of multiple keywords. More information about the format can be found at a broken link.

The repository consists of two distinct applications, which are:

OpenPower VPD Parser

This is a build-time YAML driven application that parses the OpenPower VPD format and uses the YAML configuration (see extra-properties-example.yaml and writefru.yaml) to determine:

  • The supported records and keywords.
  • How VPD data is translated into D-Bus interfaces and properties.

The application instance must be passed in the file path to the VPD (this can, for example, be a sysfs path exposed by the EEPROM device driver) and also the D-Bus object path(s) that EEPROM data needs to be published under.

IBM VPD Parser

This parser is can be built by passing in the --enable-ibm-parser configure option. This parser differs from the OpenPower VPD parser in the following ways:

  • It parses all the records and keywords from the VPD, including large keywords (Keywords that begin with a # and are > 255 bytes in length).
  • It relies on a runtime JSON configuration (see examples/inventory.json) to determine the D-Bus object path(s) that hold interfaces and properties representing the VPD for a given VPD file path.

Making the application runtime JSON driven allows us to support multiple systems (with different FRU configurations) to be supported in a single code image as well as making the application more flexible for future improvements.

TODOs and Future Improvements

  1. The long-term goal is to completely do away with the build time YAML driven configurations and instead reconcile the OpenPower VPD parser and the IBM VPD parser applications into a single runtime JSON driven application.
  2. Add details to the README on how to configure and build the application.
  3. More JSON documentation.
  4. Support for more IBM VPD formats.
  5. VPD Write and tool documentation.