History log of /openbmc/openpower-vpd-parser/const.hpp (Results 26 – 48 of 48)
Revision Date Author Comments
# 647868ed 08-Sep-2020 PriyangaRamasamy <priyanga24@in.ibm.com>

Translate Udev Event path to a generic path

Given Udev event generated path is translated into sys bus path - as the json will
have the sys/bus path.

Test:
-> Translation successful for all frus in

Translate Udev Event path to a generic path

Given Udev event generated path is translated into sys bus path - as the json will
have the sys/bus path.

Test:
-> Translation successful for all frus including frus behind muxes.
-> If the system vpd is triggered by udev event, then the execution stops as
the system vpd will already be parsed via system-vpd.service.

Few Reasons why we translate the path to a generic path:
-> Each i2c bus is memory mapped to a certain address in ASPEED.
In future if there are any architectural changes in the kernel, we need to
make changes to the JSON accordingly.
-> Also in future if the system runs on a different ASPEED, we need to
update the JSON accordingly.
-> This generic /sys/bus path represents the system wiring and doesnot rely on
how the busses are memory mapped.
-> Also for call out based events, generic path is expected than the udev event path.

Sample Udev Event i2c path : "/sys/devices/platform/ahb/ahb:apb/ahb:apb:bus@1e78a000/1e78a480.i2c-bus/i2c-8/8-0050/8-00500/nvmem"
Which gets translated to /sys/bus/ path as : "/sys/bus/i2c/drivers/at24/8-0050/eeprom"

Sample Udev Event spi path : "/sys/devices/platform/ahb/ahb:apb/1e79b000.fsi/fsi-master/fsi0/slave@00:00/00:00:00:0a/fsi-master/fsi1/slave@03:00/01:03:00:04/spi_master/spi6/spi6.0/spi6.00/nvmem"
Which gets translated to /sys/bus/ path as : "/sys/bus/spi/drivers/at25/spi6.0/eeprom"

Sample Udev Event i2c path for frus behind mux : "/sys/devices/platform/ahb/ahb:apb/ahb:apb:bus@1e78a000/1e78a300.i2c-bus/i2c-5/i2c-24/24-0051/24-00510/nvmem"
Which gets translated to generic path as /sys/bus/i2c/drivers/at24/24-0051/eeprom

Tested on simics:

<the inventory json should have generic eeprom paths for all frus>

root@rainier:/tmp# ./ibm-read-vpd-UG -f /sys/devices/platform/ahb/ahb:apb/1e79b000.fsi/fsi-master/fsi0/slave@00:00/00:00:00:04/spi_master/spi12/spi12.0/spi12.00/nvmem
the path after translation : /sys/bus/spi/drivers/at25/spi12.0/eeprom

root@rainier:/tmp# ./ibm-read-vpd-UG -f /sys/devices/platform/ahb/ahb:apb/ahb:apb:bus@1e78a000/1e78a480.i2c-bus/i2c-8/8-0051/8-00510/nvmem
the path after translation : /sys/bus/i2c/drivers/at24/8-0051/eeprom

root@rainier:/tmp# ./ibm-read-vpd-UG -f /sys/bus/i2c/drivers/at24/8-0051/8-00510/nvmem
the path after translation : /sys/bus/i2c/drivers/at24/8-0051/eeprom

Signed-off-by: PriyangaRamasamy <priyanga24@in.ibm.com>
Change-Id: I6d5995a85ef15e63d2d0b6f054fb0bf14a2b756c

show more ...


# f05effdb 07-Apr-2021 Alpana Kumari <alpankum@in.ibm.com>

PASS 2 Planar support for vpd parser

The system has two planar passes - Pass1 & Pass2 Planars.
Pass1 Planar a buffer connects all pcie cards, Whereas
Pass2 Planar has mux connection established for

PASS 2 Planar support for vpd parser

The system has two planar passes - Pass1 & Pass2 Planars.
Pass1 Planar a buffer connects all pcie cards, Whereas
Pass2 Planar has mux connection established for pcie card selection.

ibm-read-vpd picks up the right deviceTree and json
(either 2UPass1/2UPass2/4UPass1/4UPass2)
based on the HW and IM kw of the planar.

Test-
tested on Rainier 2U simics

root@rainier:/tmp# ./ibm-read-vpd -f /tmp/systemVpd
imKeyword- 50001001, HW - 0001
Processing with this JSON - /usr/share/vpd/50001001_v1.json

root@rainier:/tmp# ./ibm-read-vpd -f /tmp/systemVpd
imKeyword- 50001001, HW - 0011
Processing with this JSON - /usr/share/vpd/50001001_v2.json

root@rainier:/tmp# ./ibm-read-vpd -f /tmp/systemVpd
imKeyword- 50001000, HW - 0011
Processing with this JSON - /usr/share/vpd/50001000_v2.json

root@rainier:/tmp# ./ibm-read-vpd -f /tmp/systemVpd
imKeyword- 50001000, HW - 0001
Processing with this JSON - /usr/share/vpd/50001000_v1.json
root@rainier:/tmp#

Signed-off-by: Alpana Kumari <alpankum@in.ibm.com>
Change-Id: I36de12d9697039e61e6ad569e1e119f001e782f6

show more ...


# 414d5aef 04-Mar-2021 Alpana Kumari <alpankum@in.ibm.com>

Support XYZ interface for Location code

Update xyz interface for Location code in ibm-read-parser and vpd-manager
along with com.ibm.path for Location code.

Test Result-
busctl introspect xyz.openb

Support XYZ interface for Location code

Update xyz interface for Location code in ibm-read-parser and vpd-manager
along with com.ibm.path for Location code.

Test Result-
busctl introspect xyz.openbmc_project.Inventory.Manager /xyz/openbmc_project/inventory/system/chassis/motherboard| grep -e "Location" -e "FC" -e "SE"
com.ibm.ipzvpd.Location interface - - -
.LocationCode property s "U78DA.ND1.WZS004K-P0" emits-change writable
.FC property ay 8 65 65 68 65 45 48 48 49 emits-change writable
.SE property ay 7 68 68 83 48 48 52 75 emits-change writable
.SE property ay 7 49 51 57 70 50 66 48 emits-change writable
xyz.openbmc_project.Inventory.Decorator.LocationCode interface - - -
.LocationCode property s "UAADA.ND0.DDS004K-P0" emits-change writable

Below write command should trigger the LC update for motherboard and other dependent FRUs.

busctl call com.ibm.VPD.Manager /com/ibm/VPD/Manager com.ibm.VPD.Manager WriteKeyword ossay "/system/chassis/motherboard" "VCEN" "FC" 2 55 56
busctl call com.ibm.VPD.Manager /com/ibm/VPD/Manager com.ibm.VPD.Manager WriteKeyword ossay "/system/chassis/motherboard" "VCEN" "SE" 2 87 90

busctl introspect xyz.openbmc_project.Inventory.Manager /xyz/openbmc_project/inventory/system/chassis/motherboard| grep -e "Location" -e "FC" -e "SE"
com.ibm.ipzvpd.Location interface - - -
.LocationCode property s "U78DA.ND0.WZS004K-P0" emits-change writable
.FC property ay 8 55 56 68 65 45 48 48 49 emits-change writable
.SE property ay 7 87 90 83 48 48 52 75 emits-change writable
.SE property ay 7 49 51 57 70 50 66 48 emits-change writable
xyz.openbmc_project.Inventory.Decorator.LocationCode interface - - -
.LocationCode property s "U78DA.ND0.WZS004K-P0" emits-change writable

busctl introspect xyz.openbmc_project.Inventory.Manager /xyz/openbmc_project/inventory/system/chassis/motherboard/cpu0| grep -e "Location" -e "FC" -e "SE"
com.ibm.ipzvpd.Location interface - - -
.LocationCode property s "U78DA.ND0.WZS004K-P0-C15" emits-change writable
xyz.openbmc_project.Inventory.Decorator.LocationCode interface - - -
.LocationCode property s "U78DA.ND0.WZS004K-P0-C15" emits-change writable

Change-Id: If8715b8cafcc87d8a46e7083f90f162c5ad4a6b0
Signed-off-by: Alpana Kumari <alpankum@in.ibm.com>

show more ...


# 0746eeeb 22-Mar-2021 Sunny Srivastava <sunnsr25@in.ibm.com>

Set severity for PELs

This commit adds an option to pass severity while logging PEL.
This will help to classify PELs based on their severity.
By default severity of all the PELs logged for system VP

Set severity for PELs

This commit adds an option to pass severity while logging PEL.
This will help to classify PELs based on their severity.
By default severity of all the PELs logged for system VPD failure
is set to be unrecoverable where as other failures are flagged as
predictive errors.

Signed-off-by: Sunny Srivastava <sunnsr25@in.ibm.com>
Change-Id: I9cd10a29252a42f5031b91b9c7ad2e284ed5b861

show more ...


# 6c71c9dc 15-Apr-2021 Sunny Srivastava <sunnsr25@in.ibm.com>

Segregate utility methods

This commit segregates utility methods required commonly by both
openpower-read-vpd and ibm-read-vpd from methods only required by
ibm-read-vpd.
All dependency required by

Segregate utility methods

This commit segregates utility methods required commonly by both
openpower-read-vpd and ibm-read-vpd from methods only required by
ibm-read-vpd.
All dependency required by utility methods specific to ibm-read-vpd
is not applicable to utility methods required by openpower-read-vpd.

Hence to avoid un-necessary dependency inclusion, this change is
introduced.

Signed-off-by: Sunny Srivastava <sunnsr25@in.ibm.com>
Change-Id: I95f2be27dc0c391a45beb1654a99506317aaa52b

show more ...


# 7c9cddf7 19-Mar-2021 Andrew Geissler <geissonator@yahoo.com>

add support for rainier 1s4u

The rainier 1s4u is very similar to the standard rainier 4u. It will
have a different device tree but the only change from the 4u is two
less fans.

Tested:
- Updated IM

add support for rainier 1s4u

The rainier 1s4u is very similar to the standard rainier 4u. It will
have a different device tree but the only change from the 4u is two
less fans.

Tested:
- Updated IM keyword to that of 1s4u and re-ran system-vpd service.
Verified that u-boot fitconfig env variable was correctly set to
conf@aspeed-bmc-ibm-rainier-1s4u.dtb

Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I3507e0239283dc700bd0834b66a46ff0c6deeba7

show more ...


# 9094d4f6 05-Aug-2020 SunnySrivastava1984 <sunnsr25@in.ibm.com>

Restore system VPD if EEPROM data is blank.

This commit implement changes which enables restoring system VPD.
If at the time of VPD parsing for backplane it is found that data
related to system VPD

Restore system VPD if EEPROM data is blank.

This commit implement changes which enables restoring system VPD.
If at the time of VPD parsing for backplane it is found that data
related to system VPD is blank on EEPROM but available on cache,
then the data from Dbus will be used to restore data in EEPROM.

There are another scenarios in restoring the system VPD but this
commit only implement changes to restore system VPD when the data
is available on cache but blank on EEPROM.

This commit also implements creation and logging of PEL in case blank
system VPD is found both on EEPROM and Dbus in the process of
system VPD restore.

Meson Build: OK.
Tested on Simics: OK.

Signed-off-by: Sunny Srivastava <sunnsr25@in.ibm.com>
Change-Id: I32a872b3c3a74b79a9b8173c712b50f72fd7588c

show more ...


# 4641bff5 30-Nov-2020 Santosh Puranik <santosh.puranik@in.ibm.com>

Fix u-boot env var name for Rainier 2U

Change the value of the fitconfig u-boot environment
variable to 'conf@aspeed-bmc-ibm-rainier.dtb'.
This is to match the value used by u-boot to switch to the

Fix u-boot env var name for Rainier 2U

Change the value of the fitconfig u-boot environment
variable to 'conf@aspeed-bmc-ibm-rainier.dtb'.
This is to match the value used by u-boot to switch to the right
device tree for Rainier 2U.

This also adds Everest to the list of supported systems.

Signed-off-by: Santosh Puranik <santosh.puranik@in.ibm.com>
Change-Id: Ie52bffb1e50c0fd7d081038732e3c5676a69de03

show more ...


# a20be8ec 26-Aug-2020 SunnySrivastava1984 <sunnsr25@in.ibm.com>

PEL creation in case of HW/SW failure.

Creation of PEL in case the parser process fails to parse and/or publish
VPD data.
This commit handles both hardware or software failure and creates PEL
accord

PEL creation in case of HW/SW failure.

Creation of PEL in case the parser process fails to parse and/or publish
VPD data.
This commit handles both hardware or software failure and creates PEL
accordingly.

Tested on Simics.

Test procedure:
Step1 : Copy ibm_read_vpd in /tmp folder on simics
Step2 : Run ibm_read_vpd exe with a vpd file path having invalid VPD/ECC or
invalid JSON path. In this case we have given path to VPD file with
invalid VPD data.
command-> ./ibm_read_vpd --file <vpd_file_path>
Step3 : After the execution is over, look for PEL logged using command
"peltool -a"

PEL logged incase of invalid VPD:
[
{
"Private Header": {
"Section Version": "1",
"Sub-section type": "0",
"Created by": "0x4000",
"Created at": "11/27/2020 04:40:00",
"Committed at": "11/27/2020 04:40:00",
"Creator Subsystem": "BMC",
"CSSVER": "",
"Platform Log Id": "0x50000002",
"Entry Id": "0x50000002",
"BMC Event Log Id": "2"
},
"User Header": {
"Section Version": "1",
"Sub-section type": "0",
"Log Committed by": "0x2000",
"Subsystem": "CEC Hardware: VPD Interface",
"Event Scope": "Entire Platform",
"Event Severity": "Unrecoverable Error",
"Event Type": "Not Applicable",
"Action Flags": [
"Service Action Required",
"Report Externally",
"HMC Call Home"
],
"Host Transmission": "Not Sent"
},
"Primary SRC": {
"Section Version": "1",
"Sub-section type": "1",
"Created by": "0x4000",
"SRC Version": "0x02",
"SRC Format": "0x55",
"Virtual Progress SRC": "False",
"I5/OS Service Event Bit": "False",
"Hypervisor Dump Initiated":"False",
"Power Control Net Fault": "False",
"Backplane CCIN": "2E2D",
"Error Details": {
"Message": "A VPD data exception occurred."
},
"Valid Word Count": "0x09",
"Reference Code": "BD554001",
"Hex Word 2": "00000055",
"Hex Word 3": "2E2D0010",
"Hex Word 4": "00000000",
"Hex Word 5": "00000000",
"Hex Word 6": "00000000",
"Hex Word 7": "00000000",
"Hex Word 8": "00000000",
"Hex Word 9": "00000000",
"Callout Section": {
"Callout Count": "1",
"Callouts": [{
"FRU Type": "Normal Hardware FRU",
"Priority": "Mandatory, replace all with this type as a unit",
"Location Code": "U78DA.ND1.1234567-P0",
"Part Number": "F191014",
"CCIN": "2E2D",
"Serial Number": "YL2E2D010000"
}]
}
},
"Extended User Header": {
"Section Version": "1",
"Sub-section type": "0",
"Created by": "0x2000",
"Reporting Machine Type": "9105-22A",
"Reporting Serial Number": "SIMP10R",
"FW Released Ver": "",
"FW SubSys Version": "fw1020.00-6",
"Common Ref Time": "00/00/0000 00:00:00",
"Symptom Id Len": "20",
"Symptom Id": "BD554001_2E2D0010"
},
"Failing MTMS": {
"Section Version": "1",
"Sub-section type": "0",
"Created by": "0x2000",
"Machine Type Model": "9105-22A",
"Serial Number": "SIMP10R"
},
"User Data 0": {
"Section Version": "1",
"Sub-section type": "1",
"Created by": "0x2000",
"BMC Version ID": "fw1020.00-6-22-gbbd23f832",
"BMCState": "Ready",
"ChassisState": "Off",
"HostState": "Off",
"Process Name": "Unknown"
},
"User Data 1": {
"Section Version": "1",
"Sub-section type": "1",
"Created by": "0x2000",
"CALLOUT_INVENTORY_PATH": "/xyz/openbmc_project/inventory/system/chassis/motherboard",
"DESCRIPTION": "Invalid VPD data"
}
}
]

Signed-off-by: Sunny Srivastava <sunnsr25@in.ibm.com>
Change-Id: Ieb434bb45b4051d8b7b6d4c9022984d5471fc855

show more ...


# 65b83601 01-Sep-2020 Alpana Kumari <alpankum@in.ibm.com>

support multiple device trees in the same BMC image

This commit checks for current system type and if it is changed from last boot,
it loads new/appropriate device tree and reboot the system.

Teste

support multiple device trees in the same BMC image

This commit checks for current system type and if it is changed from last boot,
it loads new/appropriate device tree and reboot the system.

Tested-
=========================================
Test Case 1: first boot when env not defined

triggerred system vpd collection-
DBG: systemType is: 50001000
DBG: newDeviceTree: fw_dt2
U-Boot environment is not set. Updating...
DBG: rebooting...
root@rainier:/tmp# Connection to rain4bmc closed by remote host.
Connection to rain4bmc closed.
========================================
Test case 2-
triggerred system vpd collection-
DBG: systemType is: 50001001
DBG: newDeviceTree: fw_dt1
U-Boot environment is not updated. Updating...
DBG: rebooting...
root@rainier:/tmp# Connection to rain4bmc closed by remote host.
Connection to rain4bmc closed.

alpana07> ssh -k root@rain4bmc
root@rain4bmc's password:
printenv
...
bootside=b
devTree=fw_dt1
root@rainier:~#
=========================================
Test case 3-
triggerred system vpd collection again-
DBG: systemType is: 50001001
DBG: newDeviceTree: fw_dt1
U-Boot environment is Updated.

root@rainier:~# fw_printenv
...
bootside=b
devTree=fw_dt1
=========================================

Change-Id: I28bce8ced4a970e1818b4f4f613bd062647a4d3a
Signed-off-by: Alpana Kumari <alpankum@in.ibm.com>

show more ...


# e12b181b 26-May-2020 SunnySrivastava1984 <sunnsr25@in.ibm.com>

Interface & Factory implementation for VPD Parsers

This commit abstracts the implementation logic of different parser.
A parser factory is implemented to provide instance of required
parser based on

Interface & Factory implementation for VPD Parsers

This commit abstracts the implementation logic of different parser.
A parser factory is implemented to provide instance of required
parser based on the type of vpd file needed to be parsed.

The interface should be derived to implement any further parser logic
related to vpd.

Status: This does not add any new function, so basic testing of
VPD parsing, VPD tool and writes was performed.

Signed-off-by: Sunny Srivastava <sunnsr25@in.ibm.com>
Change-Id: I3ce1a2d6b7e8d8984fd7800132e78ab8a9a21e56

show more ...


# 58e22145 05-May-2020 Alpana Kumari <alpankum@in.ibm.com>

Handling FRU and Module in vpd read code

Misc changes to handle reading of CPU VPD.

Change-Id: Ia8143dec680bbfeecb1e63505650428103192157
Signed-off-by: Alpana Kumari <alpankum@in.ibm.com>


# 945a02d3 06-May-2020 SunnySrivastava1984 <sunnsr25@in.ibm.com>

Code refactoring

Moved all the constants to const.hpp and utility method to
utils.cpp/hpp.
Removed file ibm_vpd_type_check.cpp/hpp and keyword_vpd_types.hpp.

Signed-off-by: SunnySrivastava1984 <sun

Code refactoring

Moved all the constants to const.hpp and utility method to
utils.cpp/hpp.
Removed file ibm_vpd_type_check.cpp/hpp and keyword_vpd_types.hpp.

Signed-off-by: SunnySrivastava1984 <sunnsr25@in.ibm.com>
Change-Id: Ie7b54e6fd03a499fab7c3124e17292c6d525e471

show more ...


# 83a1d5de 30-Apr-2020 PriyangaRamasamy <priyanga24@in.ibm.com>

IBM VPD Parser support for both 2U & 4U system

Based on motherboard IM keyword the type of the system is identified
and the corresponding json is linked at the runtime.

Currently 2U system has supp

IBM VPD Parser support for both 2U & 4U system

Based on motherboard IM keyword the type of the system is identified
and the corresponding json is linked at the runtime.

Currently 2U system has support for single dasd-backplane
whereas 4U system has support for more than one dasd-backplanes.

Tested on simics.

Change-Id: Ia3eb48661fe565f6286c079a8f87736bb136210a
Signed-off-by: Priyanga Ramasamy <priyanga24@in.ibm.com>

show more ...


# fb5815a6 24-Apr-2020 SunnySrivastava1984 <sunnsr25@in.ibm.com>

Get inventory list using expanded location code

This commit implements api to get inventory list with respect to
a given location code in expanded format.

In case no inventory is found at the given

Get inventory list using expanded location code

This commit implements api to get inventory list with respect to
a given location code in expanded format.

In case no inventory is found at the given location or location code
is not correct, corresponding error is returned to the caller.

Tested on simics.
This api is under com.ibm.vpd.Manager interface. So vpd-manager app
needs to be running for this api to work.
Sample command for simics:
busctl call com.ibm.VPD.Manager /com/ibm/VPD/Manager com.ibm.VPD.Manager
GetFRUsByUnexpandedLocationCode sq <location_code> <node_number>

Signed-off-by: Sunny Srivastava <sunnsr25@in.ibm.com>
Change-Id: Ifa47d73a64338cbd228b5be1346027c69695612a

show more ...


# bca5aaa5 21-Apr-2020 SunnySrivastava1984 <sunnsr25@in.ibm.com>

Un-expanded to expanded location code conversion

This commit implements an api to get expanded location code
from a given un-expanded location code and node number.

In case invalid argument is pass

Un-expanded to expanded location code conversion

This commit implements an api to get expanded location code
from a given un-expanded location code and node number.

In case invalid argument is passed or the location code is
not found, corresponding error is returned to the caller.

Tested on simics.

To build use following command.
meson -Dibm-parser=enabled -Dvpd-manager=enabled build
ninja -C build

Sample bus call.
busctl call com.ibm.VPD.Manager /com/ibm/VPD/Manager com.ibm.VPD.Manager
GetExpandedLocationCode sq <locationCode> <nodeNumber>.

Signed-off-by: SunnySrivastava1984 <sunnsr25@in.ibm.com>
Change-Id: I52654a1c34d25dc9b861159a2ae1d15379b44677

show more ...


# 4330654e 01-Apr-2020 SunnySrivastava1984 <sunnsr25@in.ibm.com>

Expand and update location code property on BUS

This commit expands and updates the required location code
poperty on BUS in case following condition holds true.

a) if FC or SE or both keyword
unde

Expand and update location code property on BUS

This commit expands and updates the required location code
poperty on BUS in case following condition holds true.

a) if FC or SE or both keyword
under VCEN record has been modified by VPD write
application for Motherboard FRU.

OR

b) if TM or SE or both keyword
under VSYS record has been modified by VPD write
application for Motherboard FRU.

Tested on simics.
-make bus call or use VPD tool application to update
keywords as mentioned above in (a) and (b).
-Introspect that motherboard object on bus.
-Check the value of interface "com.ibm.ipzvpd.Location",
property - "LocationCode"

To build the application
meson -Dibm-parser=enabled -Dvpd-manager=Enabled build
ninja -C build

Signed-off-by: Sunny Srivastava <sunnsr25@in.ibm.com>
Change-Id: Ic964da0f058153bdd43b94679bdfc5596d7f3861

show more ...


# a739259f 09-Mar-2020 SunnySrivastava1984 <sunnsr25@in.ibm.com>

Merge of vpd_manager meson script with repo meson

This commit merges meson script of vpd-manager app
into the meson script for openpower-vpd-parser repo.
vpd-manager needs to be build only if we are

Merge of vpd_manager meson script with repo meson

This commit merges meson script of vpd-manager app
into the meson script for openpower-vpd-parser repo.
vpd-manager needs to be build only if we are building
ibm-read-vpd exe.

To enable build of vpd-manager the flag needs to
be enabled.

Test Command:
meson -Dibm-parser=enabled -Dvpd-manager=enabled builddir
ninja -C builddir

Signed-off-by: Sunny Srivastava <sunnsr25@in.ibm.com>
Change-Id: Ib9c8229e54c37c55654b070adb3df616d105af23

show more ...


# d076da8d 05-Mar-2020 SunnySrivastava1984 <sunnsr25@in.ibm.com>

DBus calls to update VPD cache data for Interfaces

This commit implements required bus call to update vpd cache
once the data has been updated on the hardware.
It updates data for Common interface,E

DBus calls to update VPD cache data for Interfaces

This commit implements required bus call to update vpd cache
once the data has been updated on the hardware.
It updates data for Common interface,Extra interface and COM
interface.

To test on simics use following procedure
- Hexdump the vpd file of EEPROM you want
to update in a .txt file.
- To update data of keyword for any record
make "busctl call" to WriteKeyword.
-After successful execution, agaim hexdump
VPD file of same EEPROM in another .txt
file.
-Difference can be observed in both the
file w.r.t. updated data and ECC.

once complete call has been made, updated
data in cache can be seen using following command
on simics.
- busctl intrsopect <service> <object_path>
- busctl introspect <service> <object_path>
<interface_name>

Signed-off-by: Sunny Srivastava <sunnsr25@in.ibm.com>
Change-Id: I7997a027b631de25e254be9811c1926902fda8ec

show more ...


# b421bfdd 02-Mar-2020 SunnySrivastava1984 <sunnsr25@in.ibm.com>

Process json for Extra and Common Interfaces

This commit contains code to process json to check if the
record and keyword combination updated using write keyword
is a part of extra interfaces and co

Process json for Extra and Common Interfaces

This commit contains code to process json to check if the
record and keyword combination updated using write keyword
is a part of extra interfaces and common interfaces of
VPD inventory json.

Signed-off-by: Sunny Srivastava <sunnsr25@in.ibm.com>
Change-Id: I95333abec6e7a7ad6981621f89e6d6e7edc7ecc9

show more ...


# 6d8314d6 15-May-2020 SunnySrivastava1984 <sunnsr25@in.ibm.com>

Editor implementation update for VPD-Manager app.

This commit updates the implementaion logic of reading VPD file
for vpd keyword update using VPD-Manager app.

In order to improve the efficiency, f

Editor implementation update for VPD-Manager app.

This commit updates the implementaion logic of reading VPD file
for vpd keyword update using VPD-Manager app.

In order to improve the efficiency, full vpd file will be read
in a single call instead of multiple blocks using multiple call.

Signed-off-by: Sunny Srivastava <sunnsr25@in.ibm.com>
Change-Id: Ibf4c6ba1cfb1b098a542be7ade7f0046e444abbe

show more ...


# f6d541e8 04-Feb-2020 SunnySrivastava1984 <sunnsr25@in.ibm.com>

Editor implementation for VPD manager

This commit implements editor class for VPD manager app.
This calss holds responsibility of handling and editing
vpd data related requests on behalf of manager

Editor implementation for VPD manager

This commit implements editor class for VPD manager app.
This calss holds responsibility of handling and editing
vpd data related requests on behalf of manager app and
updating the cache with new data if required.

This commit also changes parser class to implement api
needed to validate vpd header file in case of write call.

Steps to build:
meson <build_directory>
ninja -C <directory_path>

-Tested with sample json and sample vpd file
sample command to test
busctl call com.ibm.VPD.Manager /com/ibm/VPD/Manager
com.ibm.VPD.Manager WriteKeyword sssay
<"inventory_path"> <"Record_Name"> <"Keyword_Name">
<no. of bytes to update> <array_of_bytes>

Signed-off-by: Sunny Srivastava <sunnsr25@in.ibm.com>
Change-Id: I569f03e329b0f62937c6e143a344d8e4ff02db6f

show more ...


# 19be6d3d 03-Mar-2020 SunnySrivastava1984 <sunnsr25@in.ibm.com>

Common file to hold all constant values

This commit introduces a const.hpp file to hold all the
constants related to the openpower vpd repository.
All new and ongoing implementations can make use of

Common file to hold all constant values

This commit introduces a const.hpp file to hold all the
constants related to the openpower vpd repository.
All new and ongoing implementations can make use of this
file to declare or reuse constants.

Signed-off-by: Sunny Srivastava <sunnsr25@in.ibm.com>
Change-Id: Ib93c1c264dc8c69198140d63318e7e132d33fb13

show more ...


12