Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-vpd-parser / c09e210b8ca55901957aee8d507fff9b105938b7
commitc09e210b8ca55901957aee8d507fff9b105938b7[log] [tgz]
authorSunny Srivastava <sunnsr25@in.ibm.com>Wed Apr 23 10:47:06 2025 +0530
committerSunny Srivastava <sunnsr25@in.ibm.com>Wed Apr 23 18:03:18 2025 +0530
treeb5d8ecf7952545358425931fbb0d9782081a60f9
parentc74c8efe7646df9d6eb3797e672e257620670e11 [diff]
Continue execution on any GPIO exception

In case there is any issue with reading of presence GPIO, the code
should check if the required EEPROM file exists.
If found and can be parsed then instead of exiting collection for the
FRU, the code will log an informational PEL for the error and will
continue with the execution.
This is required so that we don't exit collection for an intermediate
error when the collection can be successfully done.

Change-Id: I889668a0e765cc6df7e5df174c7a80c133892d18
Signed-off-by: Sunny Srivastava <sunnsr25@in.ibm.com>
3 files changed
tree: b5d8ecf7952545358425931fbb0d9782081a60f9
  1. configuration/
  2. docs/
  3. scripts/
  4. service_files/
  5. test/
  6. vpd-manager/
  7. vpd-tool/
  8. vpdecc/
  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 here.

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.