@mdog474 - You're welcome. I am making BIOS now, so will be done in a few minutes. Please also see my edit above

* Edit - @mdog474 - For now, here, please test and see if you can boot to BIOS or not with this BIOS. This has fixed FIT + ucode updates only to one volume only, the main DXE, microcodes in PEI volume (x4 volumes) remain untouched.
http://s000.tinyupload.com/index.php?fil...757357268574592

The NVME insert causes it's own issues, no matter what tool/method is used, padding above microcode is added and or padding above files above the nested volume get removed (or those files themselves get removed too)
So, all this may be what's causing the fail for you too. So for now, test without NVME insert. I will sort that out later for you, it may take a few hours to work around and find solution to not having these things happen on insert
On this, was the BIOS you made with NVME insert bootable? If yes, great to know, if it is OK with other CPU, then I will fix the BIOS you made with the above ucode changes and fix FIT later tonight, if the above BIOS I made boots with the E3-V4 for you.

@Lost_N_BIOS Well that didn't work out so well. The bios updated successfully, but now with a E3-V3 CPU it won't get past post code 71.
I've recovered the BIOS (put the BIOS recovery jumper on 2-3, then boot with USB drive with original BIOS named Super.ROM, press control-home until double-beep then recover BIOS).
Now I'm back to the original setup.

@Lost_N_BIOS : Just to make sure I'm doing it right, what command and options do you use to update the BIOS?

I'll be offline for 3-4 hours and I can try another update then.
-------------------

@Lost_N_BIOS After recovering the original BIOS, I flashed your BIOS.

The flash.bat file I used is executing: afudos %1 /P /B /N /K /R /ME

The BIOS flash completed successfully.

I can load and run memtest with the E3-V3 processor, but with the E3-V4 processor, the board won't POST (open applying power the fans run at full speed and nothing is displayed on the screen).

Oh, and in answer to your question, the BIOS that I made with NVMe support was bootable on the E3-V3 processor, and I was able to install and boot from an NVMe drive using a PCIE to M.2 NVMe adapter.

Here, try same mod again, but this time I only changed CPUID 40671 to updated version & Fix FIT
I used MMTool 4.50 and CPU patch tab to change the microcodes, then fix FIT is done via process with two other tools UEFITool NE 57 + UEFITool 25.0 and hex editor
Here is outdated guide, you can get microcode address quickly with UEFITool 57 now, just click on the microcodes indivudually in second microcode volume at end of main DXE volume of the BIOS
Click on stock BIOS microcodes in FIT and it will take you to correct place, so you can them see where to go in broken fit BIOS to get the address to fix FIT
[GUIDE] Update CPU Microcode + Fix FIT Using UEFITool / Hex

The issue may be due to I updated other microcodes (306C1/306C3), not just the one for 40671 CPUID, you didn't say what E3 V3 CPU, so I can't be sure what you are using?

With your mod BIOS, the one with NVME insert and 40671 Rev 22 insert, could you boot to BIOS with E3 V3 CPU, or did you never test? Please test that now, if you have not already.
Then test this BIOS here, with E3 V3 and then if fails, go ahead and try E4 V4 just so we can see outcome
http://s000.tinyupload.com/index.php?fil...582543136086184

Really, the original 2018 microcode that's in there on stock BIOS should be compatible, if microcode was part of the issue, because this CPU was released in 2015.
So, I don't think microcode has anything to do with this issue. I assume this is due to either a block/allow list, or other parts of the BIOS and or SPS ME FW are not compatible with that CPU.
For this, only DeathBringer would be able to look or help, I am not skilled enough in that area to do anything

Since this has recovery jumper and you know it works, please also test a NVME mod BIOS only, without microcode insert, can you boot to BIOS with that, or it's bricking too?

* Edit - Pre-Post - I was just about to post this reply above, and then you made another post. That post is confusing! First you said you could not boot and had to recover with BIOS I sent you, then you just now said you can post to BIOS??!??!
Good to hear that edit for NVME insert did not break this BIOS. That is a ton of bad changes, interesting to see it's still bootable with all that incorrect stuff done in that volume (talking about the added and remove paddings at top and bottom)!

So, with the BIOS I sent you and V3 CPU, what microcode revision do you see loading in the OS, check like this with HWINFO (and, also see if you can see in BIOS main or info/CPU areas, if it shows microcode revision there too, as it may differ from what you see in windows)

I want to know this, because there is 4 other microcode volumes we're both not touching right now, that still have the old/orig microcodes in them, so I want to see if BIOS and or Windows is showing the old or new one being the one that is loaded while you are using the V3
Because, if it's showing the older version, then that means we also need to edit one or all of the other 4 microcode volumes to update them too. But, as mentioned above, I really don't think this is microcode issue, or it would be booting with original BIOS/Microcode, since that has compatible microcode already in it.

@mdog474
Try to disable integrated graphics in BIOS (with supported CPU). And try to boot with your E3-1285L V4

@Lost_N_BIOS @DeathBringer Here's what I've tried:
Installed the latest BIOS from @Lost_N_BIOS , set the graphics to external, and verified that with my E3-1231 v3 processor, that the machine boots using the PCI-E GPU. Swapped to use the E3-1285L V4, and the machine does not POST, does not beep. The fans run full speed and nothing. Bummer. Any follow-up suggestions?

This board seems to be what the X10SLH-N6-ST031 board is based on, I wonder if anything can be learned from looking at the BIOS from this board--the X10SLH-F: https://www.supermicro.com/en/products/motherboard/x10slh-f

@mdog474
Try to transfer ME-region (3.0.7.60) from X10SLH-F to your X10SLH-N6-ST031.

@DeathBringer Here's what I did:
-Opened the X10SLH-F BIOS in UEFITool
-Selected the ME region
-Action->Region->Extract as is
Opened the original X10SLH-N6-ST031 BIOS in UEFITool
-Selected the ME region
-Action->Region->Replace as is (using just extracted region)
-File->Save Image file

One thing I noticed is that is the Intel descriptor region, ME has Read=No and Write=No -- do I need to somehow change this?

Anyway, I put the modified BIOS (attached) on the board, and it works with the E3-1231 v3 processor but still does not work with the E3-1285L V4 processor.
One thing I will try is to take the BIOS modified by @Lost_N_BIOS and copy the ME region to that BIOS.
For what its worth, the ME region in the X10SLH-F BIOS is version 3.0.7.60, which is the same version as in the BIOS for my X10SLL-F board that works with the E3-1285L V4 processor

If I did something wrong transferring the ME-region, please let me know.

SPS3 3.0.7.60 is a security fix, why would that possibly change Broadwell support? 3.0.7.24 supports Broadwell already.

The SPS configuration for X10SLH-F is different in one bit
<IchStrap15 name="PCH Strap 15">
......
<Reserved24 value="0" name="Reserved" default="0"></Reserved24> (1 for X10SLH-N6-ST031)

and an additional flash device.

For X10SLH-F Broadwell uc shows first time with bios 3.0 (SPS 3.0.7.24)

@lfb6 I'm new to BIOS modding. What is the SPS configuration, what sort of info does it capture/config, and if I wanted to try to change this value, what tool would I use? If there is a guide already, would you please point me in the right direction? Searching didn't really help me answer these questions.

@mdog474 There's no need to do anything with SPS right now. The 2 regions you exchanged are both fine concerning Broadwell support, SPS is not the problem here, just as you found out...

@DeathBringer Are you sure that the bios region/ pei- modules like cpuinit/ core/ setup all have Broadwell support?

Zitat von lfb6 im Beitrag #25

---

@DeathBringer Are you sure that the bios region/ pei- modules like cpuinit/ core/ setup all have Broadwell support?

---