| commit | 6bd095f965b990cc1fc249505f3effa3410e4688 | [log] [tgz] |
|---|---|---|
| author | Alpana Kumari <alpankum@in.ibm.com> | Wed Feb 23 10:20:20 2022 -0600 |
| committer | Santosh Puranik <santosh.puranik@in.ibm.com> | Wed May 04 09:10:09 2022 +0000 |
| tree | a8a9a0e3ff466ff0e1e6ef7d6a6c77720d15bf71 | |
| parent | a4a2adfa96d2c491b1baf776013a6442bc88c78b [diff] |
PEL support for GPIO failure
This commit logs PEL in case of GPIO line name is not valid or this line
is busy for some other purpose or I2C line itself is bad.
Test:
Tried to access some dummy GPIO line name, which doesn't exist.
root@rain111bmc:/tmp# peltool -l
{
"0x50002D5E": {
"SRC": "BD554007",
"Message": "GPIO line couldn't find or read.",
"PLID": "0x50002D5E",
"CreatorID": "BMC",
"Subsystem": "CEC Hardware - VPD Interface",
"Commit Time": "03/07/2022 18:32:43",
"Sev": "Predictive Error",
"CompID": "0x4000"
},
root@rain111bmc:/tmp# peltool -i "0x50002D5E"
….
"Error Details": {
"Message": "GPIO line couldn't be found or read."
},
"Valid Word Count": "0x09",
"Reference Code": "BD554007",
"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": "2",
"Callouts": [{
"FRU Type": "Normal Hardware FRU",
"Priority": "Mandatory, replace all with this type as a unit",
"Location Code": "U78DA.ND0.WZS0042-P0-C5",
"Part Number": "02WF327",
"CCIN": "6B58",
"Serial Number": "Y131UF18H003"
}, {
"FRU Type": "Normal Hardware FRU",
"Priority": "Lowest priority replacement",
"Location Code": "U78DA.ND0.WZS0042-P0",
"Part Number": "02WG676",
"CCIN": "2E2D",
"Serial Number": "Y131UF07302T"
}]
}
…….
……..
},
"User Data 0": {
"Section Version": "1",
"Sub-section type": "1",
"Created by": "0x2000",
"BMCState": "Ready",
"BootState": "Unspecified",
"ChassisState": "Off",
"FW Version ID": "fw1020.00-41.2-275-g429803741-dirty",
"HostState": "Off",
"System IM": "50001001"
},
"User Data 1": {
"Section Version": "1",
"Sub-section type": "1",
"Created by": "0x2000",
"CALLOUT_IIC_ADDR": "0x0061",
"CALLOUT_IIC_BUS": "8",
"DESCRIPTION": "Couldn't find output line for the GPIO. Skipping this GPIO action. GPIO : SLOT10_PRSNT_EN_RSVD"
},
"User Data 2": {
"Section Version": "1",
"Sub-section type": "1",
"Created by": "0x2000",
"PEL Internal Debug Data": {
"SRC": [
"MRU: /sys-0/node-0/nisqually-0/ebmc-card-connector-0/ingraham-0/BMC-0",
"I2C: bus: 8 address: 97 dest: /sys-0/node-0/nisqually-0/PCA9552-5"
]
}
}
}
Signed-off-by: Alpana Kumari <alpankum@in.ibm.com>
Change-Id: I6f5582ea614e663133bac2e580ee5c0b36c3a038
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.