You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This implements support for the i2c and i3c basic controller logic that will be required for the DRAM proxy and related access. These are blocks that provide the SP access as an initiator.
The text was updated successfully, but these errors were encountered:
I have some stream of consciousness notes here, but I figured a summary is warranted at this point.
The system we have been doing investigation on is an AMD Ruby with a DDR5 DIMM at A1 and G1. The capture above is on that GHIJKL DIMM1 bus. The main takeaways are:
We can see the SP5 attempt to talk to all six potential DDR5 channels, with the communication to G1 being successful (HID b000).
All comms are happening at 100KHz
We do not observe any attempt to move from I2C to I3C Basic. i.e., no 7'h7E address broadcasts with CCCs.
We can see communications with the SPD/Hub, PMIC, and RCD.
While in I2C mode, the Hub can page in the SPD contents in the upper 128-bytes it exposes in its own memory map.
All this was running a ?? version of firmware that is definitely out of date. We should do another analysis with the latest bits we have access to.
This implements support for the i2c and i3c basic controller logic that will be required for the DRAM proxy and related access. These are blocks that provide the SP access as an initiator.
The text was updated successfully, but these errors were encountered: