Ryzen - Return of the Jedi

[NEOAethyr]

cool thx.

Had to put my Rottweiler down today out of the blue.....was not expecting it, happened that quick so I'm going to step away from pc's for a couple days get my together as this was a crushing blow for me.

She has lived at my side literally glued to me for the past 7 years so.....yah anyway. to be continued.

My condolences dude .
I have my little cat, he's been around for probably 8 years or so.

Just to confirm what aGeoM has stated regarding modded BIOSes... I went ahead and flashed one of my modded ones to my MSI Titanium yesterday (used the original v1.10 BIOS that my board shipped with, which is the only BIOS I've been using since it worked fine, even with my RAM @ 3200).

Thankfully everything went just fine!

Points of interest:
- SubTimings indeed are currently non-Adjustable on that BIOS version, at least with how I went about making them visible (ticking them all as USER for Access), but I have one last idea... doubt it'll work though. They DO show up, and tell you what they're set to, which (probably unsurprisingly) are different than the Tertiary Timings shown in Mem TweakIt.
- CPU VDDP allows for entering values, even has a Help that indicates the Default (says 1.050V), Low and Max, but since I don't know how to verify that I have no idea if the 1.070V I set is has actually applied. (I think that HWiNFO's VIN6 under the motherboard might be the VDDP, but I have no evidence and it's a shaky theory at best. After fresh boot it hovers around only 1.000V, but after waking from Sleep it is sticking at 1.048V. Lots of odd stuff happens post-sleep so it's hard to determine things then just due to that.) If anyone knows of a way to figure out what CPU VDDP is running at, let me know.
- The thing that bummed me out the most was that due to these BIOSes full on GUI (at least MSI's specifically), the menu structure inside AMIBCP is very oddly laid out. Additionally, there is no way in the actual BIOS to navigate to these other 'un-hidden' menus (though, now after I've had sleep it just dawned on me that the "Search" feature may turn them up). There are plenty of additional menus listed as you can see, but only the highlighted menus are directly accessible (MFlash is as well of course, but that's not really a 'menu' seeing as it's an option that reboots the system):


In the old Award BIOS editor (the cmd prompt one), it allowed you to easily select a menu category and then literally cut-and-paste it elsewhere. The newer AMIBCP versions do not provide that ability at all, which is not only kinda sad given it's a full GUI, but also because v5.xx EXE size is 11MB >_> What's all that code for if it can't even provide drag-and-drop? v4.55 was only 500KB and it offers the exact same functionality *shrug* ANYways... the unfortunate nature of this means I'm unable to do the other primary thing I had wanted to accomplish through modding, which was to enable the PState overclocking options that are tucked inside the OTHER "Advanced" menu (the one with the [+] not the one above '[+]Overclocking'). Sadly, with my skillset (no hex editing know-how) I'm unable to shuffle options around like I had hoped. There are empty spaces, but they're all tied together, and I an't edit the "Handle". So when I changed one space, every empty space on that page mirrored it Oh well...

Thinking bout flashing the 1.41beta (that was pulled). I don't now if the BCLK was visible by default since I never flashed their version, but I did mod it to ensure it's visible ^_^ We shall see how daring I feel. They pulled all their Betas due to a "flaw in the microcode", but what exactly that means I haven't a clue...

There's likely gonna be duplicate entries and useless ones.
You can't enable them all.
Some can be left overs from the ref bios, ie useless as well if they don't actually work or really do anything of importance.

Yes, Ryzen 1700.

Just change OPTIMAL values, you can't make it (USER)show in BIOS, leave it at default.
PSTATE Adjustment (1st row of pstates) was the one and only changed.

How are you guys modding your bios'es without messing them up?
I wanna beable to play with my r4be bios.
I've used both apps, the one that hides/unhides entries, and the one that does modules.
Both mess up the data, it's not 100% the same anymore.
Asus won't allow flashing it, however I can use the flashback and it works.
At that point, unhiding doesn't do much, they don't show anyways.
And not that it matters... I just need a way of modding things...
And the module thing works, tried with a raid rom, booted windows for a few secs and my cpu hardlocked, power off and on again and cpu is dead.
One time I noticed when playing around that my vcore wasn't setting and was on auto, at that time I had my pump hooked into the cpu fan header.
It makes me think there was some sort of checksum for the cmos or something.

I'de like to know what the heck I was doing wrong lol, or to find a guide that's 100% step by step correct.
Or something.

My goal is to lay out each of the modules in a folder, uncompressed in binary form.
I can do this with winhex, redo the format with winhex replace cmd and compile with fasm each module one by one into a binary.
From there I can format each file into there strings, terminations, and code, or at least tables of some sort.
And do checksums in fasm np, when I learn how they work...

Then the idea is to build a bios with a tool, one module at a time.
Here's where I'm stuck with ami, so I have yet to actually start...
I can't for the life of me figure out what compression scheme they use.
Otherwise I would compress them one by one and patch the small diffs with fasm.
them combined them and put int he boto strap code and decompress code etc, but it's all a mystery I can't figure crap out of the thing.