| commit | df9e554f24b31d5f9048ba8c1610c3cdb36cdac6 | [log] [tgz] |
|---|---|---|
| author | Sunny Srivastava <sunnsr25@in.ibm.com> | Wed Feb 12 12:33:07 2025 -0600 |
| committer | Jinu Joy Thomas <jinu.joy.thomas@in.ibm.com> | Fri Feb 14 09:38:30 2025 +0000 |
| tree | 3b5c64f76ddafabfaab810f0000a469ea63a0729 | |
| parent | 46b73d9fcf234034801baed2998644b2bc79a67b [diff] |
Update dump inventory and dump object
VPD-Tool currently tries to populate interfaces in case of dump object
and dump inventory without confrming if the object implements that
interface. This can cause Dbus exceptions which can be seen along with
output.
The commit add a pre-check and populates interfaces only which are
applicable. It also adds support for some more interface(s).
Test:
verified both dump object and dump inventory.
Works without giving any exceptions.
root@rain203bmc:~# /tmp/vpd-tool -o -O /system
[
{
"/system": {
"LocationCode": "U9824.42A.13E0C40",
"Model": "9824-42A",
"PrettyName": "System",
"SerialNumber": "13E0C40",
"SubModel": "S0",
"TYPE": "FRU",
"type": "xyz.openbmc_project.Inventory.Item.System"
}
}
]
root@rain203bmc:~#
/tmp/vpd-tool -o -O /system/chassis/motherboard/pcieslot10/pcie_card10
[
{
"/system/chassis/motherboard/pcieslot10/pcie_card10": {
"Address": "80",
"Bus": "29",
"CC": "6B87",
"DR": "NVME JBOF RISER",
"FN": "03FL195",
"LocationCode": "U78DB.ND0.WZS0019-P0-C10",
"PN": "03FL286",
"PrettyName": "PCIe4 x16 or PCIe5 x8 adapter",
"SN": "YA30UF13S01P",
"SlotNumber": "10",
"TYPE": "FRU",
"type": "xyz.openbmc_project.Inventory.Item.FabricAdapter"
}
}
]
Change-Id: I97ecfbec734c14cddff075f2bbf6469f70f6e25e
Signed-off-by: Sunny Srivastava <sunnsr25@in.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.