@Pacman

Thank you.
Alas, WBT size has changed. I don't have a suitable BSF.

Can anyone explain what is the purpose of the OROM VBIOS and BSF-script package? I don't see any reference to this in post #1 other than the link to download it.

@kyriacos - see steps #3-9 of the guide, it's used all through the process

@Lost_N_BIOS
In step 1) I have DevID: 1969,e091 8086,2822 and 8086,402.
Assuming that 8086,402 is the correct one, if I extract vbios.dat and open it in a hex editor, I get "BD 00" for Version VBT, "1038" for Version OROM and "5D 11" for Size VBT. Are these all the correct values?

@kyriacos - Yes, that's correct based on what I see in the included docx file - you can update to 1044

@Lost_N_BIOS
And use the included hsw_1044.bsf?

@kyriacos - follow the guide, at some point (Step 9) yes you will be using that BSF

Hi! Am I right: if there is no correct bsf for my version, i can get bsf from version with the same VBT size?

@Sonix, thank you for you're wonderful guide!

I hope one of you guys can help me with something:

I have a mobile Skylake system with OROM version 1028. Since you say ideally the VBT size and VBT version should stay the same, is it best for me to only upgrade to OROM version 1030 (like in youre table doc) or can I also upgrade to the latest Skylake/Kabylake OROM version 1062?

For example I transferred the settings from my old v1028 to v1062. This worked, but when overviewing the transferred settings in BMP I saw that the TP1, TP2 and TP3 wakeup time under 'PSR feature' was not set (0)
After researching, I found this is because in the new OROM these settings have a drop down menu with preset values rather than a text field.
In my old OROM this setting can be set to anything (string) and is set to '50' and the BMP info window says 'TP1 wake up time in multiples of 100 usec'. Meaning this would be 5000 usec, but in the new OROM I can only choose 500 usec, 100 usec or 2,5 msec

Do you guys think this is a typo in the BMP info window and should be 'multiples of 10usec' instead of 100usec?
Would it be safe if I set the values manually to 500usec or is there no benefit for me to upgrade to the 1062 OROM and should I rather play safe and stick to v1030, which has the same VBT size and VBT version?

Does anyone have sky/coffee 1001-1017 BSF/DAT folder? Trying to update the following (have v9.0.1080 GOP already)
EFI GOP Driver SKL-CFL - 9.0.1071
OROM VBIOS CoffeeLake - 1001 << Issue, no BSF/Dat and all similar version/size VBT files have Sky/Kaby text only in them (Latest in package I have is 1062 for example)

I know I can use the 1062 BSF script, but where is files to update Coffee vBIOS/VBT itself?

Unfortunately BSF + DAT OROM VBIOS CoffeLake files - not available.

Thanks @SoniX - is there anything that can be done, how to move forward/update? Is it not possible?

@Lost_N_BIOS
Alas. I tried rebuilding the BSF for CFL, but some parameters are significantly different.

Previously, pure OROM and BSF could be found in the Intel driver package. But recently, Intel has "forgotten" to add these files.

It would be great to find friends or acquaintances on Intel or who have access to the Cloud of Developers to receive new files for experiments. ;))

So far I see one solution.
If $VBT 'Name', Size and Version match, then you can simply clone the WBT from one file to another.
Over time, I will try to write a utility CloneVBT.

Thanks @SoniX - you lost me at WBT, I'll have to look around in there and see if I can figure out what you mean

I agree, it would be great if some Intel person reading this that has such files to play with for testing, would drop anonymously that would be great!
They could even join the site using a fake email and use a guest/anony name hint, hint,

I'm kinda confused. I have a CoffeeLake (Asus Maximus X Code - Z370) system but the UBU tool shows this:

Video OnBoard
[Current version]
EFI GOP Driver SKL-CFL - 9.0.1084
OROM VBIOS SKL-KBL - 1063

So the GOP driver is being detected as CFL, as expected, but why doesn't the OROM VBIOS show CFL? Does this mean that my onboard video uses the SKL-KBL OROM VBIOS and is that something to worry about?