0a725f83 | 22-Oct-2021 |
Manojkiran Eda <manojkiran.eda@gmail.com> |
Fix a bad error traces
There are couple of places where we are trying to print the 8 bit value, and it std::cout cannot display those directly, we need to typecast it to an integer.
Signed-off-by:
Fix a bad error traces
There are couple of places where we are trying to print the 8 bit value, and it std::cout cannot display those directly, we need to typecast it to an integer.
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com> Change-Id: Ibaa212de28e125fd6904c0a7b1f5b5f8c0609d51
show more ...
|
cc5c22d8 | 18-Nov-2021 |
Eddie James <eajames@linux.ibm.com> |
Fix renamed IBM OEM state set header in pldmtool
The pldmtool oem headers weren't updated with the renamed state set header.
Signed-off-by: Eddie James <eajames@linux.ibm.com> Change-Id: I306c58a92
Fix renamed IBM OEM state set header in pldmtool
The pldmtool oem headers weren't updated with the renamed state set header.
Signed-off-by: Eddie James <eajames@linux.ibm.com> Change-Id: I306c58a923997b6049837532192ffad5ce9abe96
show more ...
|
16eff863 | 14-Oct-2021 |
Brad Bishop <bradleyb@fuzziesquirrel.com> |
pldmtool: platform: getpdr: form proper JSON
Separate records with commas and wrap in an array so we get a parseable json document for tools like pldm_visualize_pdrs.py. It doesn't look pretty - fo
pldmtool: platform: getpdr: form proper JSON
Separate records with commas and wrap in an array so we get a parseable json document for tools like pldm_visualize_pdrs.py. It doesn't look pretty - for example:
} ,{
but it isn't clear how to improve the situation without significant refactoring.
Change-Id: I6484e6d2b479adeb942ec802094adab6e12f783f Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
show more ...
|
02d71143 | 14-Oct-2021 |
Brad Bishop <bradleyb@fuzziesquirrel.com> |
pldmtool: platform: check for circular references
Avoid endless loops with:
pldmtool platform getpdr -a
by detecting circular references between records in the event of a buggy/broken PLDM terminu
pldmtool: platform: check for circular references
Avoid endless loops with:
pldmtool platform getpdr -a
by detecting circular references between records in the event of a buggy/broken PLDM terminus implementation.
Change-Id: I2299c4d709fa0b8861956e55ada38da8fffb2d6e Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
show more ...
|
a2b964f2 | 06-Oct-2021 |
Pavithra Barithaya <pavithra.b@ibm.com> |
PLDM: Refactor the code
This commit refactors the code as IBM's OEM state sets where moved to oem/ibm/libpldm/state_set.h and 7f9523cda174e2c6b0b05c7446a9a8799d302c97 commit had broken the compilati
PLDM: Refactor the code
This commit refactors the code as IBM's OEM state sets where moved to oem/ibm/libpldm/state_set.h and 7f9523cda174e2c6b0b05c7446a9a8799d302c97 commit had broken the compilation of pldm master with oem-ibm enabled.
Signed-off-by: Pavithra Barithaya <pavithra.b@ibm.com> Change-Id: I676e105ed549b6d19874e6077d1f5dbe0f9b9675
show more ...
|
5bb9edb9 | 05-Aug-2021 |
George Liu <liuxiwei@inspur.com> |
BIOS: support readonly attributes
Since the P10 system has BMC to manager the BIOS attributes, and the BMC side does not know the attribute values of the BIOS, it should allow the OOB interface(Host
BIOS: support readonly attributes
Since the P10 system has BMC to manager the BIOS attributes, and the BMC side does not know the attribute values of the BIOS, it should allow the OOB interface(Host) to be able to set BIOS readOnly attributes, while still preventing the redfish-doPATCH operation on it.
Tested: if the readOnly attribute of the pvm_system_name is true, so we can use `pldmtool` to update the BIOS attributes.
pldmtool bios SetBIOSAttributeCurrentValue -a pvm_system_name -d XXX { "Response": "SUCCESS" }
Signed-off-by: George Liu <liuxiwei@inspur.com> Change-Id: Iabcb5c2400eb0a5c208cc76180d4b07e02457f44
show more ...
|
e5268cda | 07-Sep-2021 |
Tom Joseph <rushtotom@gmail.com> |
Refactor the verbose tracing in PLDM
1. Add verbose tracing in requester code 2. Change the prefix of verbose tracing to "Tx: " and "Rx: " 3. Remove explicit verbose tracing flag in libpldmresponder
Refactor the verbose tracing in PLDM
1. Add verbose tracing in requester code 2. Change the prefix of verbose tracing to "Tx: " and "Rx: " 3. Remove explicit verbose tracing flag in libpldmresponder 4. Change the prefix of pldmtool verbose tracing to "pldmtool: Tx: " and "pldmtool: Rx: "
Signed-off-by: Tom Joseph <rushtotom@gmail.com> Change-Id: Ie2c6b323e32e0828ed5ecaeb3e61943a98a2f089
show more ...
|
3ddbe439 | 29-Jun-2021 |
Shantappa Teekappanavar <sbteeks@yahoo.com> |
pldmtool: List all PDR records or PDR records based on PDR type
Support listing of all PDR records or all PDR records of the requested PDR type.
Testing: - Ran 'pldmtool platform getPDR -a' and ver
pldmtool: List all PDR records or PDR records based on PDR type
Support listing of all PDR records or all PDR records of the requested PDR type.
Testing: - Ran 'pldmtool platform getPDR -a' and verified that all PDR records were printed - Ran 'pldmtool platform getPDR -t fruRecord' and verified that all the PDR records printed were of PDR type "FRU Record Set PDR"
Signed-off-by: Shantappa Teekappanavar <sbteeks@yahoo.com> Change-Id: I5759c745c6740063752b02e7be7c7788122b6ed4
show more ...
|
5079ac4a | 19-Aug-2021 |
Brad Bishop <bradleyb@fuzziesquirrel.com> |
treewide: remove 'using namespace' from headers
Using namespace at global scope in a header file violates the cpp core guidelines. Quoting the guidelines:
"Doing so takes away an #includer’s abi
treewide: remove 'using namespace' from headers
Using namespace at global scope in a header file violates the cpp core guidelines. Quoting the guidelines:
"Doing so takes away an #includer’s ability to effectively disambiguate and to use alternatives. It also makes #included headers order-dependent as they might have different meaning when included in different orders."
For further reading: https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Rs-using-directive
The guidelines don't call out using using namespace from namespace scope, but it is only marginally less problematic and still unexpected, so this patch removes those as well.
The process used to do the update is roughly:
1 - git grep 'using namespace' **.hpp 2 - For each instance, remove the offending 'using namespace' line 3 - build 4 - add 'using namespace' to cpp files or fully resolve types in hpp files until the project builds again.
Further cleanup is possible - for example cpp files could be scrubbed for unnecessary namespace qualification - this was not done here to make review as simple as possible.
Change-Id: I4931f5e78a1b5b74b4a4774c035a549f4d59b91a Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
show more ...
|
dcdcd3b8 | 15-Jun-2021 |
Sridevi Ramesh <sridevra@in.ibm.com> |
pldmtool: Display GetPDR state set ID possible state names in an array
Note: Also, displays OEM state set and their possible states. Created new oem_ibm_state_set.hpp for OEM IBM PDR's possibl
pldmtool: Display GetPDR state set ID possible state names in an array
Note: Also, displays OEM state set and their possible states. Created new oem_ibm_state_set.hpp for OEM IBM PDR's possible states.
Example:
{ "nextRecordHandle": 115, "responseCount": 27, "recordHandle": 114, "PDRHeaderVersion": 1, "PDRType": "State Sensor PDR", "recordChangeNumber": 0, "dataLength": 17, "PLDMTerminusHandle": 0, "sensorID": 93, "entityType": "[Physical] Unspecified", "entityInstanceNumber": 0, "containerID": 0, "sensorInit": "noInit", "sensorAuxiliaryNamesPDR": false, "compositeSensorCount": 1, "stateSetID[0]": "Identify State(17)", "possibleStatesSize[0]": 1, "possibleStates[0]": [ "Identify State Unasserted(1)", "Identify State Asserted(2)" ] }
{ "nextRecordHandle": 125, "responseCount": 27, "recordHandle": 124, "PDRHeaderVersion": 1, "PDRType": "State Sensor PDR", "recordChangeNumber": 0, "dataLength": 17, "PLDMTerminusHandle": 0, "sensorID": 103, "entityType": "[Physical] System chassis (main enclosure)", "entityInstanceNumber": 1, "containerID": 0, "sensorInit": "noInit", "sensorAuxiliaryNamesPDR": false, "compositeSensorCount": 1, "stateSetID[0]": "Operational Fault Status(10)", "possibleStatesSize[0]": 1, "possibleStates[0]": [ "Normal(1)", "Stressed(2)" ] }
{ "nextRecordHandle": 249, "responseCount": 30, "recordHandle": 248, "PDRHeaderVersion": 1, "PDRType": "State Effecter PDR", "recordChangeNumber": 0, "dataLength": 16, "PLDMTerminusHandle": 1, "effecterID": 116, "entityType": "[Physical] OEM IBM Firmware Update", "entityInstanceNumber": 1, "containerID": 0, "effecterSemanticID": 0, "effecterInit": "noInit", "effecterDescriptionPDR": false, "compositeEffecterCount": 1, "stateSetID[0]": "OEM IBM Boot State(32769)", "possibleStatesSize[0]": 2, "possibleStates[0]": [ "P Side(1)", "T side(2)" ] }
Signed-off-by: Sridevi Ramesh <sridevra@in.ibm.com> Change-Id: Iae44b14dab071683c86fd65c95e984b9287eca80
show more ...
|
8fb11c97 | 08-Jun-2021 |
Sridevi Ramesh <sridevra@in.ibm.com> |
libpldmresponder & pldmtool : Expand support for GetPLDMCommands
Update newly available pldm commands for bios and platform. Resolves : https://github.com/openbmc/pldm/issues/9
Tested on latest BMC
libpldmresponder & pldmtool : Expand support for GetPLDMCommands
Update newly available pldm commands for bios and platform. Resolves : https://github.com/openbmc/pldm/issues/9
Tested on latest BMC environment.
$ pldmtool base GetPLDMCommands -t 3 [ { "PLDM Command Code": 1, "PLDM Command": "GetBIOSTable" }, { "PLDM Command Code": 2, "PLDM Command": "SetBIOSTable" }, { "PLDM Command Code": 7, "PLDM Command": "SetBIOSAttributeCurrentValue" }, { "PLDM Command Code": 8, "PLDM Command": "GetBIOSAttributeCurrentValueByHandle" }, { "PLDM Command Code": 12, "PLDM Command": "GetDateTime" }, { "PLDM Command Code": 13, "PLDM Command": "SetDateTime" } ]
$ pldmtool base GetPLDMCommands -t 2 [ { "PLDM Command Code": 4, "PLDM Command": "SetEventReceiver" }, { "PLDM Command Code": 10, "PLDM Command": "PlatformEventMessage" }, { "PLDM Command Code": 17, "PLDM Command": "GetSensorReading" }, { "PLDM Command Code": 33, "PLDM Command": "GetStateSensorReadings" }, { "PLDM Command Code": 49, "PLDM Command": "SetNumericEffecterValue" }, { "PLDM Command Code": 50, "PLDM Command": "GetNumericEffecterValue" }, { "PLDM Command Code": 57, "PLDM Command": "SetStateEffecterStates" }, { "PLDM Command Code": 81, "PLDM Command": "GetPDR" } ]
Signed-off-by: Sridevi Ramesh <sridevra@in.ibm.com> Change-Id: Id7fbc449d6eb90541e46f98cf0aa2bf5d6f48316
show more ...
|
c50c6cd7 | 08-Jun-2021 |
Sridevi Ramesh <sridevra@in.ibm.com> |
Fix for pldmtool GetFruRecordTable command with oem-ibm disabled.
Tested on BMC environment with oem-ibm enabled & disabled.
Signed-off-by: Sridevi Ramesh <sridevra@in.ibm.com> Change-Id: Ie8b43f7e
Fix for pldmtool GetFruRecordTable command with oem-ibm disabled.
Tested on BMC environment with oem-ibm enabled & disabled.
Signed-off-by: Sridevi Ramesh <sridevra@in.ibm.com> Change-Id: Ie8b43f7ea55a4255b74a46250dc9d15ec5949cad
show more ...
|
0c5d1ec3 | 29-May-2021 |
Manojkiran Eda <manojkiran.eda@gmail.com> |
Improve the pldmtool to display logical entities
- The logic in pldmtool was written in such a way that it would display anything as OEM if it is not in the supported map.
- For example a "core
Improve the pldmtool to display logical entities
- The logic in pldmtool was written in such a way that it would display anything as OEM if it is not in the supported map.
- For example a "core" (entity type - Processor | Logical Bit) which is a logical Processor entity is wrongly displayed as OEM by the pldmtool.With this commit that behavior of pldmtool is fixed.
Tested By: root@rainier:/tmp# ./pldmtool platform getpdr -d 64 { "nextRecordHandle": 65, "responseCount": 20, "recordHandle": 64, "PDRHeaderVersion": 1, "PDRType": "FRU Record Set PDR", "recordChangeNumber": 0, "dataLength": 10, "PLDMTerminusHandle": 2, "FRURecordSetIdentifier": 42496, "entityType": "[Logical] Processor", "entityInstanceNumber": 1, "containerID": 2 }
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com> Change-Id: I52e314cbc80629d05f2b4dbf4fcd7ad40989fb91
show more ...
|
12c8a661 | 13-May-2021 |
Sridevi Ramesh <sridevra@in.ibm.com> |
Document README for pldmtool.
Resolves openbmc/pldm/issues/#20
Signed-off-by: Sridevi Ramesh <sridevra@in.ibm.com> Change-Id: I2f07ff506d24d9caec45e56fd6817b87e59b195e |
afbdb6d1 | 27-May-2021 |
Manojkiran Eda <manojkiran.eda@gmail.com> |
pldmtool : Add new entity types & statesets
- This commit adds all the entity types & state sets mentioned in the spec dsp 0249 into supported map used by the pldmtool, so that it can display th
pldmtool : Add new entity types & statesets
- This commit adds all the entity types & state sets mentioned in the spec dsp 0249 into supported map used by the pldmtool, so that it can display those when queried.
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com> Change-Id: I5b865bb861c2bfee771a65b724b61c9a8fd17762
show more ...
|
79175b44 | 20-May-2021 |
Jayashankar Padath <jayashankar.padath@in.ibm.com> |
pldmtool: Add new entity types in the pdr support list
Added new entity types in the GetPDR command interface to parse the newly added entity types. Added new types for disk backplane, fan, nvme dri
pldmtool: Add new entity types in the pdr support list
Added new entity types in the GetPDR command interface to parse the newly added entity types. Added new types for disk backplane, fan, nvme drive, dimm, tod battery, pcie slot and pcie cable card.
Testing Result for some entity types:
pldmtool platform GetPDR -d 156 { "nextRecordHandle": 157, "responseCount": 27, "recordHandle": 156, "PDRHeaderVersion": 1, "PDRType": "State Sensor PDR", "recordChangeNumber": 0, "dataLength": 17, "PLDMTerminusHandle": 0, "sensorID": 55, "entityType": "Slot", "entityInstanceNumber": 1, "containerID": 3, "sensorInit": "noInit", "sensorAuxiliaryNamesPDR": false, "compositeSensorCount": 1, "stateSetID[0]": "17", "possibleStatesSize[0]": 1, "possibleStates[0]": " 1 2" }
pldmtool platform GetPDR -d 170 { "nextRecordHandle": 171, "responseCount": 27, "recordHandle": 170, "PDRHeaderVersion": 1, "PDRType": "State Sensor PDR", "recordChangeNumber": 0, "dataLength": 17, "PLDMTerminusHandle": 0, "sensorID": 69, "entityType": "Real Time Clock (RTC)", "entityInstanceNumber": 1, "containerID": 3, "sensorInit": "noInit", "sensorAuxiliaryNamesPDR": false, "compositeSensorCount": 1, "stateSetID[0]": "17", "possibleStatesSize[0]": 1, "possibleStates[0]": " 1 2" }
Signed-off-by: Jayashankar Padath <jayashankar.padath@in.ibm.com> Change-Id: Iddf290d68cf20d3c274a41079ac6c4ff1f805310
show more ...
|
bd5e2eaa | 22-Apr-2021 |
George Liu <liuxiwei@inspur.com> |
Fix potential map::at error
There are some potential errors, when using the map::at method, the process may hang due to out of bounds. so the exception should be caught.
Also, use the map::contains
Fix potential map::at error
There are some potential errors, when using the map::at method, the process may hang due to out of bounds. so the exception should be caught.
Also, use the map::contains method of C++20 instead of map::find.
Tested: built pldm successfully and worked.
Signed-off-by: George Liu <liuxiwei@inspur.com> Change-Id: Ia5d7dea906e5c598072c08b27387195ef1201839
show more ...
|
3b1dc01d | 16-Apr-2021 |
Patrick Williams <patrick@stwcx.xyz> |
build: add wrapfiles for dependencies
Add wrapfiles for all dependencies and update meson.build files to ensure dependencies are requested in all cases. This enables out-of-bitbake/out-of-sdk builds
build: add wrapfiles for dependencies
Add wrapfiles for all dependencies and update meson.build files to ensure dependencies are requested in all cases. This enables out-of-bitbake/out-of-sdk builds for this repository and enables it to be used as a meson subproject.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I0f2f7eed98f7f7555cafefc2605e1031a7f0adaf
show more ...
|
6f4479c7 | 16-Apr-2021 |
Patrick Williams <patrick@stwcx.xyz> |
build: rename dependency variable
Per [1], the conventions for dependency variables are to be named '<project or lib>_dep'. This allows consistency when using this project as a meson-subproject els
build: rename dependency variable
Per [1], the conventions for dependency variables are to be named '<project or lib>_dep'. This allows consistency when using this project as a meson-subproject elsewhere.
Switch the name from 'libpldm' to 'libpldm_dep'.
1. https://mesonbuild.com/Subprojects.html#naming-convention-for-dependency-variables
Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I98c8e2148610b45755b45029d1d38206bac5b885
show more ...
|
bcf91acc | 14-Mar-2021 |
Manojkiran Eda <manojkiran.eda@gmail.com> |
Fix a possible null pointer dereference
- This commit would fix a potential null pointer dereference.
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com> Change-Id: Ic323bde2c4bd35c35132e43104
Fix a possible null pointer dereference
- This commit would fix a potential null pointer dereference.
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com> Change-Id: Ic323bde2c4bd35c35132e4310466cd6ae7ec7aeb Signed-off-by: George Liu <liuxiwei@inspur.com>
show more ...
|
a6daacb5 | 22-Mar-2021 |
George Liu <liuxiwei@inspur.com> |
pldmtool: Fix confusing attribute name
- The intent behind this commit is to fix the confused attribute name. when we run `pldmtool bios getBIOSTable -t 1(PLDM_BIOS_ATTR_TABLE)`, we can only get
pldmtool: Fix confusing attribute name
- The intent behind this commit is to fix the confused attribute name. when we run `pldmtool bios getBIOSTable -t 1(PLDM_BIOS_ATTR_TABLE)`, we can only get the default value and index.
- Early naming will make the caller mistakenly think that this is the currect value. In fact, we need to run `pldmtool bios getBIOSTable -t 2(PLDM_BIOS_ATTR_VAL_TABLE)` to get the currect value.
Tested: - pldmtool bios getBIOSTable -t 1 Before: { "AttributeHandle": 19, "AttributeNameHandle": "28(pvm_system_power_off_policy)", "AttributeType": "BIOSEnumeration", "NumberOfPossibleValues": 3, "PossibleValueStringHandle[0]": "12(Power Off)", "PossibleValueStringHandle[1]": "14(Stay On)", "PossibleValueStringHandle[2]": "2(Automatic)", "NumberOfDefaultValues": 1, "DefaultValueStringHandleIndex[0]": 2, "StringHandle": "2(Automatic)" }
After: { "AttributeHandle": 19, "AttributeNameHandle": "28(pvm_system_power_off_policy)", "AttributeType": "BIOSEnumeration", "NumberOfPossibleValues": 3, "PossibleValueStringHandle[0]": "12(Power Off)", "PossibleValueStringHandle[1]": "14(Stay On)", "PossibleValueStringHandle[2]": "2(Automatic)", "NumberOfDefaultValues": 1, "DefaultValueStringHandleIndex[0]": 2, "DefaultValueStringHandle": "2(Automatic)" }
- pldmtool bios getBIOSTable -t 2 { "AttributeHandle": 19, "AttributeType": "BIOSEnumeration", "NumberOfCurrentValues": 1, "CurrentValueStringHandleIndex[0]": "Automatic" }
Signed-off-by: George Liu <liuxiwei@inspur.com> Change-Id: Ib493d80431dad039f264c65cbdcb8bab80ca85f0
show more ...
|
9f8d2b0a | 24-Mar-2021 |
Sampa Misra <sampmisr@in.ibm.com> |
Revert "Fix return value for the pldm_send method"
This reverts commit 4d25f6a6f4a027d51863393e55cb770ededf0358.
Reason for revert: <sendMsg returns the number of bytes transferred in success. that
Revert "Fix return value for the pldm_send method"
This reverts commit 4d25f6a6f4a027d51863393e55cb770ededf0358.
Reason for revert: <sendMsg returns the number of bytes transferred in success. that is being treated as error response as per current code. blocking Host to power on. Reverting for now until we find a better solution>
Change-Id: I606f0245075e38eb99de74219453dc5f781d46b7
show more ...
|
4d25f6a6 | 16-Mar-2021 |
George Liu <liuxiwei@inspur.com> |
Fix return value for the pldm_send method
- If the caller uses invalid mctp_eid to call the pldm_send/sendmsg method, it will return a value greater than 0(non -1).
- At this time, the pldm_send
Fix return value for the pldm_send method
- If the caller uses invalid mctp_eid to call the pldm_send/sendmsg method, it will return a value greater than 0(non -1).
- At this time, the pldm_send method will return to `PLDM_REQUESTER_SUCCESS`, and will cause the pldm daemon to die.
Tested: - use an invalid mctp_eid: Before: pldmtool platform getpdr -d 0 -m 11 -v the pldm daemon to die.
After: pldmtool platform getpdr -d 0 -m 11 -v Request Message: 0b 01 80 02 51 00 00 00 00 00 00 00 00 01 ff ff 00 00 Failed to call pldm_send_recv, rc = 18 pldmSendRecv: Failed to receive RC = 18
Signed-off-by: George Liu <liuxiwei@inspur.com> Change-Id: I12eb5a83e7848a5aaec3e7f38b142a9e64d3dd45
show more ...
|
f31b5049 | 22-Jan-2021 |
Sridevi Ramesh <sridevra@in.ibm.com> |
Implement pldmtool platfrom Getstatesensorreading
./pldmtool platform GetStateSensorReadings -h get the state sensor reading Usage: ./pldmtool platform GetStateSensorReadings [OPTIONS]
Options:
Implement pldmtool platfrom Getstatesensorreading
./pldmtool platform GetStateSensorReadings -h get the state sensor reading Usage: ./pldmtool platform GetStateSensorReadings [OPTIONS]
Options: -h,--help Print this help message and exit -m,--mctp_eid UINT MCTP endpoint ID -v,--verbose -i,--id UINT REQUIRED A handle that is used to identify and access the sensor -r,--rearm UINT REQUIRED Each bit location in this field corresponds to a particular sensor
./pldmtool platform GetStateSensorReadings -i 7 -r 2 -m 9 { "compositeSensorCount": 2, "sensorOpState[0]": "Sensor Enabled", "presentState[0]": "Sensor Warning", "previousState[0]": "Sensor Unknown", "eventState[0]": "Sensor Unknown", "sensorOpState[1]": "Sensor Enabled", "presentState[1]": "Sensor Critical", "previousState[1]": "Sensor Unknown", "eventState[1]": "Sensor Unknown" }
./pldmtool platform GetStateSensorReadings -i 1 -r 0 { "compositeSensorCount": 1, "sensorOpState[0]": "Sensor Enabled", "presentState[0]": "Sensor Unknown", "previousState[0]": "Sensor Unknown", "eventState[0]": "Sensor Warning" }
Change-Id: I963fb1625a7aeba0c35bfe54707a7009c151020c Signed-off-by: Sridevi Ramesh <sridevra@in.ibm.com>
show more ...
|
ae28bc77 | 10-Dec-2020 |
Sridevi Ramesh <sridevra@in.ibm.com> |
Add tracing when the BMC PLDM daemon issues GetPDR to host
After PDR trace enabled
Sending Msg: 80 02 51 18 00 00 00 00 00 00 00 01 ff ff 00 00 Receiving Msg: 00 02 51 00 19 00 00 00 00 00 00 00 05
Add tracing when the BMC PLDM daemon issues GetPDR to host
After PDR trace enabled
Sending Msg: 80 02 51 18 00 00 00 00 00 00 00 01 ff ff 00 00 Receiving Msg: 00 02 51 00 19 00 00 00 00 00 00 00 05 14 00 18 00 00 00 01 14 00 00 0a 00 02 00 40 01 43 00 01 00 01 00 Sending Msg: 80 02 51 19 00 00 00 00 00 00 00 01 ff ff 00 00 Receiving Msg: 00 02 51 00 1a 00 00 00 00 00 00 00 05 14 00 19 00 00 00 01 14 00 00 0a 00 02 00 41 01 43 00 02 00 01 00 Sending Msg: 80 02 51 1a 00 00 00 00 00 00 00 01 ff ff 00 00 Receiving Msg: 00 02 51 00 1b 00 00 00 00 00 00 00 05 14 00 1a 00 00 00 01 14 00 00 0a 00 02 00 c0 20 42 00 01 00 01 00 Sending Msg: 80 02 51 1b 00 00 00 00 00 00 00 01 ff ff 00 00 Receiving Msg: 00 02 51 00 1c 00 00 00 00 00 00 00 05 14 00 1b 00 00 00 01 14 00 00 0a 00 02 00 c2 20 42 00 02 00 01 00
Signed-off-by: Sridevi Ramesh <sridevra@in.ibm.com> Change-Id: I464de3c128054b381dbba6199f2525ed2b327195
show more ...
|