Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-vpd-parser / 37c6bef9e3ad2ab80a5fb7ac9f76eedd1cd37ec8
commit37c6bef9e3ad2ab80a5fb7ac9f76eedd1cd37ec8[log] [tgz]
authorSouvik Roy <souvikroyofficial10@gmail.com>Thu Jul 17 00:55:59 2025 -0500
committerSunnySrivastava <sunnsr25@in.ibm.com>Fri Jul 25 04:32:57 2025 +0000
treeaac43f049c4e3f4683fd17c39ef2171ffce293f6
parentd966f27f27359500f1dbd04470764e432facb430 [diff]
Fix exception type loss while parsing VPD

This commit includes changes to prevent loss of exception type while
parsing VPD. In case of Data/ECC exception while parsing IPZ VPD, the
exception type was lost. This commit also handles setting PEL severity
in case of Data/ECC exception. In case of Data/ECC exception while
parsing VPD, predictive PEL must be logged.

Test:
```
- On rainier 2s2u simics system, corrupt VHDR data of base op panel
- On rainier 2s2u simics system, corrupt VHDR ECC of op LCD panel
- Restart vpd-manager
- Check PELs using peltool
- Observe 2 predictive PELs logged with Data Exception and ECC Exception
  respectively
```

Change-Id: I21e5b668aa70cc13916475792e38e5822c00117e
Signed-off-by: Souvik Roy <souvikroyofficial10@gmail.com>
2 files changed
tree: aac43f049c4e3f4683fd17c39ef2171ffce293f6
  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 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.