Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-vpd-parser / 0a5fce1e84d0d742073c8a5bbd565a91eaa688af
commit0a5fce1e84d0d742073c8a5bbd565a91eaa688af[log] [tgz]
authorSunny Srivastava <sunnsr25@in.ibm.com>Wed Apr 09 11:09:51 2025 +0530
committerJinu Joy Thomas <jinu.joy.thomas@in.ibm.com>Wed Apr 09 08:46:13 2025 +0000
tree896d711bfa70d9314528335e3a73f061f262f9e9
parente2f09be83c032805c1aa924b5d2187ee994f4ebb [diff]
Update PELs while parsing FRU

Severity of PEL needs to be updated as informational in case any
of the FRU collection fails for reason other than EEPROM or data
failure, for which the severity will be handled by the specific parser.

This is done as successful collection of a FRU other than system VPD
is not a mandatory condition to bring BMC to ready state.

In case of failure in the processing of pre action, to figure out what
failed in the flow, informational PEL is added while processing
pre-action tags.

No error in case the file is not found and pre-action was not required
as FRU can be actually absent.

Empty map is also not considered for logging PEL in worker as
respective parser should take care of any error and log PEL at their
end.

Change-Id: I4adf5be3adeb5ca556b1b4283e3036361793b108
Signed-off-by: Sunny Srivastava <sunnsr25@in.ibm.com>
3 files changed
tree: 896d711bfa70d9314528335e3a73f061f262f9e9
  1. configuration/
  2. scripts/
  3. service_files/
  4. test/
  5. vpd-manager/
  6. vpd-tool/
  7. vpdecc/
  8. .clang-format
  9. .gitignore
  10. LICENSE
  11. meson.build
  12. meson.options
  13. OWNERS
  14. 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.