-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MemPowerSpec iddX specification effort reduction #5
Comments
|
These are numbers from the 3rd voltage domain (VDDca/VDDq), which we have 2014-08-25 14:18 GMT+05:30 Sven Goossens notifications@github.com:
|
The DDR4 mapping (comments tells which value to read from the datasheet): <parameter id="idd0" value="58" comment="IDD0" />
<parameter id="idd02" value="4" comment="IPP0" />
<parameter id="idd2n" value="44" comment="IDD2N" />
<parameter id="idd2p0" value="30" comment="IDD2P" />
<parameter id="idd2p1" value="30" comment="IDD2P (copy)" />
<parameter id="idd3n" value="61" comment="IDD3N" />
<parameter id="idd3p0" value="44" comment="IDD3P" />
<parameter id="idd3p1" value="44" comment="IDD3P (copy)" />
<parameter id="idd4r" value="140" comment="IDD4R" />
<parameter id="idd4w" value="156" comment="IDD4W" />
<parameter id="idd5" value="190" comment="IDD5B" />
<parameter id="idd6" value="20" comment="IDD6N" />
<parameter id="idd62" value="0" comment="Should be equal to IPP6N, but this value is not mentioned in the datasheet." />
<parameter id="vdd" value="1.2" comment="VDD" />
<parameter id="vdd2" value="2.5" comment="VPP" /> FYI, this particular set of values corresponds to a DDR4-1866 according to the latest(?) micron datasheet (4gb_ddr4_dram.pdf - Rev. B 10/14 EN), at speed grade -107E. Once I have had time to test with these numbers, I might update the full memspec that ships with drampower. |
The different current measurement conditions will be handeled internally in the new version 5.0 of DRAMPower. |
MemPowerSpec iddX specification
This issue is related to a discussion that took place in an earlier email thread, so I'll copy-paste some relevant bits:
For the non-DDR2/3 memory types, the definition of the currents as defined in the vendor data sheets is not the same as the values we need to plug into the MemPowerSpec. This makes it hard to define new memspecs and to verify that the ones we currently have are correct.
Goal
It should be easy to create the spec (since that is a manual process) and the burden of calculating intermediate values or remapping variable names should sit in the tool / parser. The way it's done now is very error-prone, difficult to check and time consuming.
I would vote for a usage scheme like this:
User: [1) User reads datasheet 2) Inserts required currents as defined in the datasheet into memspec] --> Program: [ 3) uses given currents and memory type to derive model input variables, 4) Model uses variables and performs generic calculations]
This separates the concern of specification and modeling, and provides a cleaner and more intuitive interface for the users. Similarly, duplicating IDD2P0 into IDD2P1 for other memories could be done in this intermediate layer, if the model really requires this.
Datasheet to MemPowerSpec mappings
Feel free to extend this with other memories. It would also be good to have the list of required currents per memory type.
LPDDR2 mapping
This is what I think the mapping from LPDDR2 datasheet currents to MemPowerSpec variables is (written in the xml comments):
DDR2 mapping
The text was updated successfully, but these errors were encountered: