| commit | 36dba30ad1af598bc4b30d0b38f4911a3c8b93f5 | [log] [tgz] |
|---|---|---|
| author | Souvik Roy <souvikroyofficial10@gmail.com> | Thu Jan 23 03:38:04 2025 -0600 |
| committer | Souvik Roy <souvikroyofficial10@gmail.com> | Fri Apr 11 08:48:42 2025 +0000 |
| tree | cbbb59731bf0dbb6ebab86c9a729d987756892b3 | |
| parent | 8dedd1e7fab2260b56d004f52a06003f6cff3404 [diff] |
vpd-tool mfgClean: implement sync BIOS attributes This commit implements --syncBiosAttributes feature in vpd-tool --mfgClean. When --syncBiosAttributes is selected along with --mfgClean, the VPD keywords which are used for backing up BIOS attributes are updated with the BIOS attribute values read from BIOS Config Manager service. Test: ``` - Install BMC image on rainier_2s2u. - Reboot and wait for BMC to reach Ready state. - Using vpd-tool, check the value of all the System VPD keywords used for backing up BIOS attributes both on EEPROM and on D-Bus. - Run vpd-tool --mfgClean --syncBiosAttributes/-s --yes - Check return code - Use pldmtool to check the current values of respective BIOS attributes - Use vpd-tool, check the value of all the System VPD keywords used for backing up BIOS attributes, both on EEPROM and on D-Bus. - The VPD values should correspond with the BIOS attribute values. - For all other keywords for which --mfgClean applies, the value on EEPROM and D-Bus should be the default value from the respective backup_restore JSON file. ``` Change-Id: I57c5df6ac0b3c4c91533d1ef22e69efcd4c87162 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 here.
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.