Fix getscom on DDR4 everst system #97
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The index values of pdbg targets are updated to match the physical device path. So using the index value for getting the scoms shall fail. The fapi position is still connected to the OMI index. So using the fapi position to calculate the instance id in case of DDR4 system. Tested Results: root@p10bmc:/tmp# getscom explorer 08012400 -all explorer k0:n0:s0:p00 0x0000000000000000 explorer k0:n0:s0:p01 0x0000000000000000 explorer k0:n0:s0:p24 0x0000000000000000 explorer k0:n0:s0:p25 0x0000000000000000 explorer k0:n0:s0:p32 0x0000000000000000 explorer k0:n0:s0:p33 0x0000000000000000 explorer k0:n0:s0:p56 0x0000000000000000 explorer k0:n0:s0:p57 0x0000000000000000 /usr/bin/edbg getscom explorer 08012400 -all root@p10bmc:/tmp# getscom explorer 8012810 -all explorer k0:n0:s0:p00 0x8122640700112820 explorer k0:n0:s0:p01 0x8122640700112820 explorer k0:n0:s0:p24 0x8122640700112820 explorer k0:n0:s0:p25 0x8122640700112820 explorer k0:n0:s0:p32 0x8122640700112820 explorer k0:n0:s0:p33 0x8122640700112820 explorer k0:n0:s0:p56 0x8122640700112820 explorer k0:n0:s0:p57 0x8122640700112820 /usr/bin/edbg getscom explorer 8012810 -all
devenrao
reviewed
May 15, 2024
devenrao
approved these changes
May 15, 2024
aravynd
approved these changes
Aug 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The index values of pdbg targets are updated to match the physical device path. So using the index value for getting the scoms shall fail. The fapi position is still connected to the OMI index. So using the fapi position to calculate the instance id in case of DDR4 system.
root@p10bmc:/tmp# getscom explorer 08012400 -all
explorer k0:n0:s0:p00 0x0000000000000000
explorer k0:n0:s0:p01 0x0000000000000000
explorer k0:n0:s0:p24 0x0000000000000000
explorer k0:n0:s0:p25 0x0000000000000000
explorer k0:n0:s0:p32 0x0000000000000000
explorer k0:n0:s0:p33 0x0000000000000000
explorer k0:n0:s0:p56 0x0000000000000000
explorer k0:n0:s0:p57 0x0000000000000000
/usr/bin/edbg getscom explorer 08012400 -all
root@p10bmc:/tmp# getscom explorer 8012810 -all
explorer k0:n0:s0:p00 0x8122640700112820
explorer k0:n0:s0:p01 0x8122640700112820
explorer k0:n0:s0:p24 0x8122640700112820
explorer k0:n0:s0:p25 0x8122640700112820
explorer k0:n0:s0:p32 0x8122640700112820
explorer k0:n0:s0:p33 0x8122640700112820
explorer k0:n0:s0:p56 0x8122640700112820
explorer k0:n0:s0:p57 0x8122640700112820
/usr/bin/edbg getscom explorer 8012810 -all