[Feature Request] Would you be able to support x399 and 2000 series Threadripper?
ChiefZigZag opened this issue · comments
What would be required to fully support it? Is it even possible? Attached is the results I am currently getting on a Asrock X399m board with a 2950x. It seems that the DrvStr is incorrect, the RTT settings are incorrect, its not showing the ProcODT, and the voltages seem off.. everything else seems to check out.
VSOC (SMU) should be fixed with the upcoming new version.
The rest of the values - I don't really know, it probably depends on some security feature like TPM or something else.
I would be grateful if you attach a debug report.
Tools -> Debug -> click on Debug -> Save or Save As
I can also give you a preview of the new version to double-check if at least the VSOC is showing up correctly.
Okay, if you need my machine for any additional reports or tests i'd gladly help. let me know. I don't know or think you can disable TPM on this threadripper.. i think its built right into the chip.. i'll see if there are any BIOS options for it and give it a try
Debug_Report_26669700.4616882.txt
I have been trying to confirm the VDDP voltage and stumbled across your application, it seems to fluctuate depending on load and the readout of 1.1(809) seems to make sense but whenever I change it in the bios it does not reflect in the application either. Perhaps the new version will work better
Appreciate it.
The dumped table contains just 3 values, which are unknown to me. Others are reported as 0, hense the readings in the app.
120.0 Ω matched 0 from the table, as it is the first option in the resistances tables. There's no way I can distinguish if it is a real value of 0 ("120.0 Ω" selected in BIOS) or it is the default 0 as in "unknown".
The only option would be to detect if ProcODT is available and if not, just display "N/A" for the rest of the values - they are all matched to "index 0" from the translation tables.
I've seen Stilt mentioning a workaround for Threadrippers in his RTC changelog, but I don't have a clue what is it. Maybe I have to do the same in order to get these values right on TR 2nd gen. Sadly, no public source and I don't know what to do in this case, but I will keep digging.
Added support for reading Threadripper CAD & Data bus settings with AGESA fTPM enabled.
You can see the changelog here: https://www.techpowerup.com/download/ryzen-timing-checker/
I know for sure that ProcODT is exposed because the Ryzen Master Utility seems to be able to present that.. The other ones I have been struggling to find anything that can read them. Thank you
FYI, Attached is the Ryzen Timing Checker.. I found your utility far more useful.
Currently that debug output the CAD settings on this systems BIOS are set to 24-20-24-24.. not 120Ω
RTC is only working correctly with first gen Ryzen CPUs and some of the Zen+, then it got hard to support every single AGESA version and different BIOS implementations, so AFAIK he gave up when Zen2 was released.
RTC mostly works with older AGESA versions, while ZT works with newer versions. However, I don't know what is changed between different firmware versions and can't implement checks in the code, so it either works or not.
In order to fix the readings I will have to find what that workaround is. I will try to emulate that on my 3900X with the integrated fTPM device.
Hi Ivan, I cold booted my machine and jumped into Windows to do some memory overclocking and i fired up the application and for some reason the readout was working?? I took the oppritunity to share a screenshot and upload the debug info.. very odd since its the first time I have ever seen this app do anything like this and I didn't update it.
Debug_Report_26679050.9917629.txt
Very very odd.. I am uncertain if I found a BIOS/motherboard bug on this board or a software bug in ZenTimings but the VDDP voltage seems to change according to the SOC voltage.. cannot set the VDDP manually but if I change the SOC the VDDP changes with it.. just a note I thought i'd add unsure if its relevant to you.
Hi Ivan, I cold booted my machine and jumped into Windows to do some memory overclocking and i fired up the application and for some reason the readout was working??
I discovered that if I launch Ryzen Master and then ZenTimings the values show up accordingly.. hmm
I guess RyzenMaster has the ability to read the table when fTPM is enabled, so once the table is available, ZenTimings is able to read it.