I mean in theory if you use PSPTool and know where to look for, you maaybe can get that to work
But the theory would require a fix inside SMU firmware very likely
Then ported back AMD CBS flags in order to support the PCIe 4.0 switch
And yes, PSP firmware (on the chip) needs to be able to talk with valid commands to SMU
theoretically i could work, if AMD didn't/won't change the encryption method before 1005AGESA
And updating to a new one will invalidate the public key, and update PSP Firmware
Yes TK421, maybe :wheee:
As stamped several revisions of ryzens exist, one UG one UF and one without a stamp
it might be possible that inside PSP firmware this sector is permanently locked on the new stamped batch too
The PSP firmwares are indeed part of AGESA, but thats quite an understatement really.
On these platforms, the PSP starts up first and only then are the rest of the IPs / hardware initialised.
There is exactly zero control over anything prior the PSP and basically until it has completed initialising the rest of the hardware, you are running a non-x86 system that is completely isolated.
What almost certainly happens is, that the PSP checks the fused DeviceID of the chipset, to determine if the present variant is allowed to run PCIe Gen. 4.
Probably the easiest way around this would be physically replacing the existing Promontory / Promontory LP chipsets with the variant, that is white listed for Gen. 4 enablement in the FW (Promontory LP; B550A, B550).
There is some indication that some kind of anti roll-back measures for the PSP FW have been implemented, but I'm not sure how tripping into such measures would manifest itself.
From the prior experience I know that the cross-compability of the different AGESA modules is very limited and with PSP modules it is virtually non-existent. Essentially, until the PSP has been satisfied, you're dealing with a brick.
Even if it would be somehow possible to downgrade to a PSP FW which allows Gen. 4 operation on older board designs, it probably wouldn't be wise to use such old version. Afterall, PSP stands for "Platform Security Processor" at this
point (more than 6 months after the change), there have been tons of bug fixes and other kinds of improvements.
Also personally, I fail to see the point in enabling the Gen. 4 PCIe on Promontory chipset (300 & 400-series) based boards.
Since the chipset itself doesn't support Gen. 4, there is no bandwidth advantage for the chipset connected devices, that rely on the x4 link between the CPU and the chipset and because of that are potentially bandwidth starved at Gen. 3 bandwidth.
Currently the only M.2 Gen. 4 drives have Phison controllers on them (...) and the only GPUs that support Gen. 4 are Navi based Radeons (...). So since Radeons most certainly don't need Gen. 4, the only potential use would be M.2 storage. Given that you are willing to rely a Phison controller with your data.
Personally, I'm not touching them even with a ten foot pole due to the horrible experiences on both, their USB and SATA flash controllers.Wait, are Phison controllers of dubious quality/reliability?
Based on the very brief look I had at the tool, to me it appears the "PSPTool" is only able to manipulate the different components of the PSP stack (insert, extract, delete or replace) not touch the code itself.does psptool even exist, I know tools for intel ME does but unaware of amd stuff being accessible
2080ti is already showing perf loss on P3x8, and samsung is going to release their pcie4 nvme drives soon
most consumers will have 1 gpu and 1 nvme connected to the cpu
Good to know. Thank you.Personally, I'm not touching them even with a ten foot pole due to the horrible experiences on both, their USB and SATA flash controllers.
Granted things might have improved since then, but personally I won't touch anything made by Phison ever again.
Unfortunately it isn't possible, since I'm now using 3rd gen. Threadripper as a workstation and these aren't compatible with Linux.@The Stilt
Hi mate, sorry for my request, but would you be so kind to compile latest flashrom 1.2 with -internal support under pure DOS environment ?
I've downloaded source from the github repository but my attempts to compile from myself have failed hundred times and I'm very tired.
If you could make a 1.2 version of this wonderful tool it would be a great and useful thing.
Thanks anyway for your help and keep up the good work.
Actually, I took interest in the reasons why I couldn't get TRX40 platform to work under Linux, despite all of the know workarounds I tried.Don't worry, thanks anyway.
ifeq ($(CONFIG_RAIDEN), yes) UNSUPPORTED_FEATURES += CONFIG_RAIDEN=yes else override CONFIG_RAIDEN = no endif
Hi Dieter,@The Stilt
Thank you very much for your phantastic work.
I can confirm, that the Flashrom tool is able to flawlessly dump the 32MB sized BIOS Region of my ASRock X570 Pro4 and to successfully flash the updated/modded BACKUP.ROM into the SPI Chip of the board.
Since I was not able to get any UBU tool modded BIOS properly flashed into my ASRock X570 Pro4 mainboard by using the in-box Instant Flash tool, it was your friend aGeoM, who encouraged me to try the Flashrom tool and helped me to find the exact BIOS flashing procedure. Meanwhile I have written a short guide into the start post of >this< Win-RAID Forum thread.
Today I wanted to find out, whether it is possible to do it as well by using FREEDOS instead of MS DOS. After having removed the diskcopy.dll file from my Win10 system drive, I created the bootable FREEDOS image by using the original (unpatched) Rufus version 3.10. To my surprise I succeeded with the creation of the BIOS Region dump.
Question to you: Do you think, that it is possible as well to get a modded BIOS properly flashed by using the same FREEDOS USB Stick?
Thanks in advance for your reply.
Dieter (alias Fernando)
I never said he is my "friend", in terms of knowing him or ever interact with him on any forum, but I truly respect his knowledge as his work and must of all his good will to help the community all over this years asking nothing and offering everything, in that sense, yes... he is my friend and friend of all of us, like many others that I respect silently, but honoring them helping others.[MENTION=348110] ...it was your friend aGeoM...