| commit | d7c7cb5d2369e179361302f281b10af131260d0f | [log] [tgz] |
|---|---|---|
| author | Souvik Roy <souvikroyofficial10@gmail.com> | Wed Jul 30 06:31:02 2025 +0000 |
| committer | Souvik Roy <souvikroyofficial10@gmail.com> | Thu Oct 09 15:26:38 2025 +0000 |
| tree | d17207346f16482cf1171a41674c69d3e67c04e3 | |
| parent | 6bd74ad17db90e84414e959c6f7105fe1495e568 [diff] |
Log vpd write action to file This commit implements changes to log VPD write action to file. VPD WriteKeyword API is exposed on DBus and can be triggered by any application. VPD write also has the potential to corrupt data in some cases. Hence all VPD write actions need to be logged. This commit also implements an utility API to convert WriteVpdParams to string data type. Test: ``` - execute vpd-tool writeKeyword on Op Panel's VINI record, CC keyword - observe vpd-tool writeKeyword is successful and following log entry is added in /var/lib/vpd/vpdWrite.log 2025-09-18 08:17:02.367 [Info] FileName: /usr/src/debug/openpower-fru-vpd /1.0+git/vpd-manager/src/manager.cpp, Line: 277 VPD write successful on path[/xyz/openbmc_project/inventory/system/chassis/motherboard/tpm_wilson ] : Record: VINI Keyword: CC Value: 0x36423630 - execute vpd-tool writeKeyword with invalid Keyword, observe no new log added to /var/lib/vpd/vpdWrite.log ``` Change-Id: I209d761d3504dea6a1b65577fb4f3ee548c8adf6 Signed-off-by: Souvik Roy <souvikroyofficial10@gmail.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.