search

open-power / pdbg

PowerPC FSI Debugger
Apache License 2.0
17 stars 39 forks source link

Fix getscom on DDR4 everst system #97

Closed deepakala-k closed 1 month ago

deepakala-k commented 4 months ago

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