Intel MEI Driver v11.5.0.1011 INF for manual installation
Intel SOL "Driver" v11.5.0.1003 INF for manual installation
Intel MEI Drivers & Software v11.5.0.1015 for Consumer systems complete package
Intel MEI Drivers & Software v11.5.0.1003 for Corporate systems complete package

Intel ME 11.5 Consumer PCH-LP Firmware v11.5.0.1058



For 100/200-series SKL/KBL-U and SKL/KBL-Y systems which come with ME firmware v11.5.x

Warning: KabyLake-U and KabyLake-Y are not released yet! For research only!

MEA: 11.5.0.1058_CON_LP_XX_UKPDM_PRD_EXTR_FFF127D25BB18FA2FD53564CAF3056EC2F79E5D5_SHA1

@ greg.chalk:

Your binary confirms that you have Consumer LP NOPDM firmware flashed. That exact firmware has been tested by someone else as far as the FW Status Register3 value is concerned. It should be 200 which we have associated with CON NOPDM. As a last test, run Flash Programming Tool with command fptw -greset and after the reset, check MEInfo again. Don't you see 200?

Rewritten Warning 1 for 100-series systems to add more details and better explanation
Rewritten Warning 2 for 100-series systems to change most of the stuff that were written before
Reuploaded Intel ME 11.0 CON/COR PCH-H/LP Firmware with latest version regardless of PDM and a new "Term Help" file



@ greg.chalk:

Thank you for showing me some proof greg.chalk. I'm not saying that the laptop is not working properly. After your report and Pacman's, I just realized that a) we cannot use FW Status Register3 to determine PDM/NOPDM and b) I'm sick of dealing with this PDM nonsense. It seems to work for most people and reflashing will usually resolve FWUpdate getting stuck the first time. Thus, I decided to change the 2nd SKL warning as seen above. Again, thank you for that last report.

@ burner07:

What do you mean "restricted"? Explain in detail what you are trying to do. If you are getting the "Local ME Firmware Update disabled" error then the problem is BIOS related. Make sure you have the latest BIOS flashed, otherwise contact Gigabyte and ask them to fix it.

@ rvail623:

If the FD of the 1st chip is unlocked (Gigabyte leaves both of them unlocked to my knowledge) then of course you can switch to the 2nd chip, boot, switch to 1st and relfash the SPI image or just ME region.

@ Morku:

It's the stupid PDM issue all over again. I don't think the 11.5 driver is related because it's supposed to support 100-series systems. But in your case, I would use the older and definitely stable 11.0 driver just to be on the safe side. At least until the 11.5 branch has matured a bit more. Does your system have an unlocked Flash Descriptor? That's the only way to recover from a bad ME firmware flash unless your board uses ASRock's ME "recovery" feature, which enforces only one version and reverts back whenever a newer one is flashed - probably not since you said you were at 11.0.11 firmware. Based on the fact that you received an error, it may be that the 11.0.15 we have is PDM and you are one of the cases where "cross-flashing" NOPDM and PDM leads to FWUpdate errors and thus ME corruption. For some people, retrying to flash the same firmware (even PDM), after restoring the previous working one, worked the 2nd time without issues. I don't really know what to suggest. It depends on whether you can always restore/reflash the SPI in case of trouble. If you can, I would say to install 11.0 driver and try again 11.0.15 followed by 11.0.12 PDM if the former is (again) unsuccessful.

To check if your FD is locked, just run Flash Programming Tool with command "fptw -d spi.bin". If you see "cpu access error" then you FD is locked, otherwise unlocked.

In your case though, you definitely have the ASRock ME recovery feature. Based on what you described, they changed it. Previously it forced 11.0.0.1180 even if the user updated properly to a newer version. Now it seems to only restore in case the version if older or the fw is corrupted (no driver interface available, version 0.0.0.0).

I changed how I deal with PDM some days ago due to conflicting reports and lack of any info from Intel or new packages. The FW Status Register3 of 11.0.15 was new, another user was seeing the value of PDM firmware (020) even though he had clearly flashed NOPDM (200) etc. I got tired of dealing with PDM, especially since Intel only documents Register1 and 2 with no mention for 3 or higher. If you need the last NOPDM firmware again then check the Engine Firmware Repository thread.

Zitat von Yuno im Beitrag #2328

---

does me fw 11.5 work with skylake? "100/200-series SKL/KBL-S" is listed so..

---