Here is 11.0.0.1180 Consumer & Corporate Stock Regions.

Intel ME 11.0 Consumer PCH-H Firmware v11.0.0.1180 (EXTR --> RGN)
Intel ME 11.0 Corporate PCH-H Firmware v11.0.0.1180 (EXTR --> RGN)

Thanks to Pacman for the clean regions. These are usable with FWUpdate for anyone interested.

@ GrofLuigi:

Check the .inf file to see the correct driver version. Otherwise, check the TeeDriverW8x64.sys and not HECI.sys driver.

@ GrofLuigi:

That would explain why they also include the older HECI.sys driver nowadays: for older operating systems such as XP/2003. So if you have such an OS then that's the driver that gets installed.

@ Scamperor:

As far as I can see you don't rally need to mod anything for an LGA (not BGA) C236 board to work with Xeon chips. Intel has stated that it is compatible. From what I can see from Gigabyte MW31-SP0 (which is where I assume you found the image.bin file you showcased) the only difference is that C236 uses ME 11 firmware whereas C232 uses SPS 4 firmware (support for SPS 4 is ready and will be available at the next MEA version). So if you have an LGA C236 workstation board you should be able to use Xeon chips just fine. Here are some interesting articles that address that concern:

http://www.anandtech.com/show/9730/intel...e31200-v5-xeons
http://wccftech.com/intel-skylake-xeon-e...sktop-chipsets/

Regarding the non-workstation/server SKUs, they are not supported. It may very possibly be a restriction at ME firmware but I doubt Intel would allow changing that via tools such as FIT. I suppose it's embedded into the firmware and just taking one from a C236 won't change anything. The "Platform" value that you see at MEA is the platform for which the firmware was built for at FIT. It's basically the drop-down menu at the top of the FIT window which is OEM/user adjustable. Also, as far as I know C236 only works with Corporate ME 11 firmware and not Consumer. In that case only H170, B150, Q150 & Q170 SKUs are the only remotely viable solutions either way.

@ Scamperor:

Before you do the things below, can you do me a small favor? You have a Corporate SKU and I have been looking for a Corporate ME UPD image for some unrelated (to this issue) testing. Can you run FWUpdate tool with -save me.bin command and attach the output me.bin file? The actual command would be FWUpdLcl64 -save me.bin . Do you have any other 5MB/Corporate SKUs by any chance?

Now, the fact that you have a B150 SKU is a good first step even though I'm fairly certain it won't work either way. But if you have the capability of restoring a bad flash then why not test it? I know Gigabyte prefers Dual-BIOS implementations and they sometimes leave the Flash Descriptor unlocked which are both good for what you are trying to do. Let's test the latter, that your flash descriptor is unlocked. Run FPT with the command fptw64 -d spi.bin and check the result. If a full 16MB file called spi.bin got dumped then you are good to go. However, if you see Error 26 then your flash descriptor is locked and only by using a hardware programmer will you be able to restore the ME after a bad flash (and that may actually be a bad flash). If your flash descriptor is unlocked, keep that 16MB spi.bin dump of your chip in order to be able to restore it to the exact way it was before via the 2nd BIOS chip (verify it is working/booting properly before any of the above/below tests).

Now that we are certain the system can be restored in case things go wrong, I have created a new F4 "BIOS" for you with the ME region from the C236 Gigabyte workstation. I need to emphasize this: it's completely wrong to take the ME firmware of one machine and blindly transfer it to another without adjusting settings with FIT based on the already existing ME region of your own BIOS provided by the manufacturer. But, in this case, we are taking the most direct rout to see quickly and dirty if this method will even work at all and allow Xeon chips to work with a non-workstation board. The board will probably lose overclocking capabilities and stuff like that with that ME firmware but we can restore back in such case. What I'm trying to say is that a) there will most probably be problems after doing that and b) even if it works and Xeon cpus are accepted, that firmware cannot stay at the system. In the latter case, after being happy that it works, we will have to track down the exact option that enabled Xeon chips on non-workstation SKUs. My belief is that if Intel know what they are doing, they will have locked the usage of Xeon chips on consumer SKUs at the silicon level or non-modifiable settings at the "locked/protected" sections of the ME firmware. Still, let's try it. The modded "BIOS"/SPI image is attached.

Intel ME 11.0 Corporate PCH-LP Firmware v11.0.0.1180
Intel ME 11.0 Consumer PCH-LP Firmware v11.0.0.1173
Intel ME 11.0 Corporate PCH-H Firmware v11.0.0.1180 Re-Upload
Intel ME 11.0 Consumer PCH-H Firmware v11.0.0.1180 Re-Upload
Intel MEI Driver Installer v11.0.0.1169
Intel MEI Driver INF v11.0.0.1166 Re-Upload

Intel ME System Tools v11.0 r8:

Flash Image Tool v11.0.0.1180
Flash Programming Tool(DOS) v11.0.0.1180
Flash Programming Tool(EFI64) v11.0.0.1180
Flash Programming Tool(Windows) v11.0.0.1180
Flash Programming Tool(Windows64) v11.0.0.1180
FWUpdate(DOS) v11.0.0.1180
FWUpdate(EFI64) v11.0.0.1180
FWUpdate(Win) v11.0.0.1180
FWUpdate(Win64) v11.0.0.1180
MEInfo(DOS) v11.0.0.1180
MEInfo(EFI64) v11.0.0.1180
MEInfo(Windows) v11.0.0.1180
MEInfo(Windows64) v11.0.0.1180
MEManuf(DOS) v11.0.0.1180
MEManuf(EFI64) v11.0.0.1180
MEManuf(Windows) v11.0.0.1180
MEManuf(Windows64) v11.0.0.1180
CCT(DOS) v11.0.0.1180
CCT(EFI) v11.0.0.1180
CCT(Windows) v11.0.0.1180
Manifest Extension Utility v11.0.0.1180
Consumer FW Release Notes v11.0.0.1173
Corporate FW Release Notes v11.0.0.1168
SPT Consumer FW Bring Up Guide v1.0 PV
SPT Corporate FW Bring Up Guide v1.1 PV
SKL SPT BIOS Release Notes v95.2

@ all:

Has anyone tried the 11.0.0.1180 FWUpdate tool with an EXTR ME region to see if the bug is fixed already? Of course only people with Skylake systems can test that. Meanwhile, Pacman and I have figured out where the problem is exactly and in case 1180 still doesn't solve it, we are looking for some testers. It has been verified to work at one Skylake system.

@ allee:

Yes, latest for your system is 1.5MB 9.0.31.1487 firmware. By the way, thank you for using MEA.

I just tried flashing an extracted 1180 image while on FW 1178, using FWUpdate 1180, but sadly same error 1 as before.

@ allee:

There is no point in running MEA without a filename afterwards. What is it going to analyze then? I have added a help screen at the next version of MEA: