| commit | bab2bedab1ccf3d36fa7f7cb063b06a0a6888eb4 | [log] [tgz] |
|---|---|---|
| author | girik <giridharikrishnan@gmail.com> | Mon May 15 04:00:17 2023 -0500 |
| committer | Jinu Joy Thomas <jinu.joy.thomas@in.ibm.com> | Tue Jul 18 14:19:10 2023 +0000 |
| tree | 080861a07264f611fa84cdae8b8b411f58a9b25d | |
| parent | 91e784d4582e28bf2e522f1ddfa3f89d0dfb4515 [diff] |
vpd-tool: Flow to read keyword from hardware updated
The commit implements change to check if the offset passed by the user
for a given EEPROM path is equal to the offset if defined for that
EEPROM in inventory JSON.
In case of any mismatch, error message is flagged to the user.
As all EEPROMs are not modelled in inventory JSON file, In order to
handle case where an EEPROM path passed by user is not present in JSON,
check has been added to avoid any exception thrown due to extraction of
inventory path from JSON based on the passed EEPROM path.
Test cases:
CASE1: Trying to read from i2c FRU
/tmp/vpd-tool -r -H -O "/sys/bus/i2c/drivers/at24/8-0050/eeprom" -R VINI -K PN --seek 0x30000
Invalid offset, please correct the offset
Recommended Offset is: 0
/tmp/vpd-tool -r -H -O "/sys/bus/i2c/drivers/at24/8-0050/eeprom" -R VINI -K PN
{
"/sys/bus/i2c/drivers/at24/8-0050/eeprom": {
"PN": "00L5521"
}
}
CASE2: Trying to read from proc and EEPROM not defined in JSON:
/tmp/vpd-tool -r -H -O /sys/bus/spi/drivers/at25/spi22.0/eeprom -R VINI -K CC
Invalid offset, please correct the offset
Recommended Offset is: 196608
/tmp/vpd-tool -r -H -O /sys/bus/spi/drivers/at25/spi22.0/eeprom -R VINI -K CC --seek 0x30000
{
"/sys/bus/spi/drivers/at25/spi22.0/eeprom": {
"CC": "5C5F"
}
}
/tmp/vpd-tool -r -H -O /sys/bus/spi/drivers/at25/spi23.0/eeprom -R VINI -K CC --seek 0x30000
{
"/sys/bus/spi/drivers/at25/spi23.0/eeprom": {
"CC": "5C5F"
}
}
/tmp/vpd-tool -r -H -O /sys/bus/spi/drivers/at25/spi23.0/eeprom -R VINI -K CC --seek 0x3000
VHDR record not found
Did you provide a valid offset? By default VPD offset is taken as 0. To input offset, use --seek. Refer vpd-tool help.
/tmp/vpd-tool -r -H -O /sys/bus/spi/drivers/at25/spi23.0/eeprom -R VINI -K CC
VHDR record not found
Did you provide a valid offset? By default VPD offset is taken as 0. To input offset, use --seek. Refer vpd-tool help.
/tmp/vpd-tool -r -H -O /sys/bus/spi/drivers/at25/spi22.0/eeprom -R VINI -K CC --seek 0x3000
Invalid offset, please correct the offset
Recommended Offset is: 196608
Signed-off-by: Giridhari Krishna <giridharikrishnan@gmail.com>
Change-Id: I246ca983fc75490999f18386bf60e949959d49d2
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.