| commit | b5a80748172437d5ec2d3e1003e176ce3b41a3f7 | [log] [tgz] |
|---|---|---|
| author | Anupama B R <anupama.b.r1@ibm.com> | Thu Nov 20 01:48:35 2025 -0600 |
| committer | Anupama B R <anupama.b.r1@ibm.com> | Tue Nov 25 08:48:28 2025 +0000 |
| tree | dec7f030d7286e740a4b7fbf11d433c9614a35db | |
| parent | b1698aee8af3840334fcb7dfa48ccba1436e7fa5 [diff] |
Handle file mode for system VPD collection
This commit adds changes to read system VPD from designated file
location in case VPD collection mode is 'file mode' for the system.
In non-field mode, VPD collection mode is determined by reading u-boot
variable "vpdmode".
```
Test:
Good path:
1. Updated u-boot vpdmode to file mode.
2. Copied the system VPD to designated location for file mode.
3. After system reboot, observed that system VPD is collected successfully.
Bad path:
1. Updated u-boot vpdmode to file mode.
2. Skipped copying system VPD to designated file location.
3. After system reboot, observed that vpd-manger logged a critical PEL as system VPD parsing is failed.
Part of info from PEL:
"User Data 1": {
"Section Version": "1",
"Sub-section type": "1",
"Created by": "bmc error logging",
"DESCRIPTION": "Standard runtime exception. Reason: System VPD parsing failed, from path [/var/lib/vpd/file/sys/bus/i2c/drivers/at24/8-0050/eeprom]. Either file doesn't exist or error occurred while parsing the file.",
"FileName": "/usr/src/debug/openpower-fru-vpd/1.0+git/vpd-manager/oem-handler/ibm_handler.cpp",
"FunctionName": "performInitialSetup",
"InteranlRc": "0",
"UserData1": "",
"UserData2": ""
}
```
Change-Id: Iae4eb64fe91e608f9ae61ab7f88ae41d36bc1007
Signed-off-by: Anupama B R <anupama.b.r1@ibm.com>
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:
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 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.
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:
# and are > 255 bytes in length).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.