| commit | 844f88f984ded76c3b68fab7356a48accb88fec3 | [log] [tgz] |
|---|---|---|
| author | Anupama B R <anupama.b.r1@ibm.com> | Sun Jan 26 02:47:06 2025 -0600 |
| committer | Jinu Joy Thomas <jinu.joy.thomas@in.ibm.com> | Fri Feb 28 05:33:08 2025 +0000 |
| tree | 9084203c21a8bd0a2a55430d0a281b3fd19c590f | |
| parent | 31c04110b5f85e4788ae5796539be694720fb409 [diff] |
vpd-tool force reset command implementation
This commit implements force reset command option in vpd-tool
application.
The commit implements clearing of Phosphor Inventory Manager’s (PIM)
persisted data, restarts the PIM and VPD manager services. In turn VPD
manager triggers the VPD collection for the FRUs listed in the system
config JSON.
Output:
```
Create mismatch value, by updating keyword value only on DBus.
busctl call xyz.openbmc_project.Inventory.Manager /xyz/openbmc_project/inventory xyz.openbmc_project.Inventory.Manager Notify a{oa{sa{sv}}} 1 "/system/chassis/motherboard" 1 "com.ibm.ipzvpd.VSYS" 1 "BR" ay 2 0x32 0x33
Data On Hardware:
root@rainvpdteam:/tmp# vpd-tool -O /sys/bus/i2c/drivers/at24/8-0050/eeprom -R VSYS -K BR -r -H
{
"/sys/bus/i2c/drivers/at24/8-0050/eeprom": {
"BR": "S0"
}
}
Data on DBus:
root@rainvpdteam:/tmp# vpd-tool -O /system/chassis/motherboard -R VSYS -K BR -r
{
"/system/chassis/motherboard": {
"BR": "23"
}
}
On force reset command:
root@rainvpdteam:/tmp# ./vpd-tool -f
Stopping vpd-manager service.
Restarting xyz.openbmc_project.Inventory.Manager service.
Starting vpd-manager service.
After force reset command, DBus got updated with hardware data:
root@rainvpdteam:/tmp# vpd-tool -O /system/chassis/motherboard -R VSYS -K BR -r
{
"/system/chassis/motherboard": {
"BR": "S0"
}
}
root@rainvpdteam:/tmp# vpd-tool -O /sys/bus/i2c/drivers/at24/8-0050/eeprom -R VSYS -K BR -r -H
{
"/sys/bus/i2c/drivers/at24/8-0050/eeprom": {
"BR": "S0"
}
}
```
Change-Id: Ic236265817d793892902f63835667167365b8cdc
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 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.