@SoniX
sorry, in this case the motherboard uses 1 82579LM and 1 82574L,
UBU Automatically uses a CL module and not good, with the GE module is ok
This file is created when you select
"8 - Other Option ROM in FFS"
in the Main Menu.
It contains information about OROM not available for the update.
This image file is deleted the next time you run the UBU.
If this feature is redundant, I’ll remove it in the next version.
Automatic: for 82579 DevID 1502 supported file CL, for 82574 DevID 10D3 supported file GE - this is the right support. Which NIC is not working 82579 or 82574 or both?
No it’s ok, I was testing the new MEA and forgot that I had pressed 8 before apparently. You don’t have to remove it. 
Tuesday check and let you know, before I can not.
I was looking for a way of doing it before flashing the BIOS but, I guess not.
Good morning guys,
ME Analyzer in UBU keeps telling me that my ME firmware is not the latest available, but I downloaded and flashed 9.0.31.1487 which is the latest according to this post:
Intel Management Engine: Drivers, Firmware & System Tools
Here is the output from UBU:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
-------[ ME Analyzer v1.4.13 ]-------
Database r48
Firmware: Intel ME
Version: 9.0.30.1482
Release: Production
Type: Region, Extracted
FD: Unlocked
SKU: 1.5MB
VCN: 3
PV: Yes
Date: 10/10/2013
FITC Ver: 9.0.22.1467
Latest: No
And this is the output from MEinfo tool:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
Intel(R) MEInfo Version: 9.0.22.1467
Copyright(C) 2005 - 2013, Intel Corporation. All rights reserved.
Intel(R) ME code versions:
BIOS Version: 1603
MEBx Version: 0.0.0.0000
Gbe Version: 1.3
VendorID: 8086
PCH Version: 5
FW Version: 9.0.31.1487 H
LMS Version: 11.0.0.1183
MEI Driver Version: 11.0.0.1181
Wireless Hardware Version: Not Available
Wireless Driver Version: Not Available
FW Capabilities: 0x01101940
Intel(R) Capability Licensing Service - PRESENT/ENABLED
Protect Audio Video Path - PRESENT/ENABLED
Intel(R) Dynamic Application Loader - PRESENT/ENABLED
TLS: Disabled
Last ME reset reason: Power up
Local FWUpdate: Enabled
BIOS Config Lock: Enabled
GbE Config Lock: Enabled
Host Read Access to ME: Disabled
Host Write Access to ME: Disabled
SPI Flash ID #1: EF4017
SPI Flash ID VSCC #1: 20252025
SPI Flash BIOS VSCC: 20252025
BIOS boot State: Post Boot
OEM Id: 00000000-0000-0000-0000-000000000000
Capability Licensing Service: Enabled
OEM Tag: 0x00000000
Localized Language: Unknown
Independent Firmware Recovery: Disabled
What am I missing?
The fact that MEA displays info from the inputted file and not what’s flashed in the system’s SPI chip.
The fact that MEA displays info from the inputted file and not what’s flashed in the system’s SPI chip.
Uhm, sorry but I don’t understand… The file I checked with UBU (ME Analyzer) is the bios I’m currently running on this machine… How can it contain an older version of the ME firmware? Shouldn’t my ME firmware version match the one included in that bios file, since I just flashed it?
@ ZioGTS:
Not necessarily. The ME is not part of the BIOS but another region like the BIOS. It’s commonly called “BIOS” but the images provided by most OEMs are actually full SPI (Flash Descriptor, GbE, ME, BIOS etc). The ME region gets replaced only if the CPU/BIOS has read/write access to it during flashing, something which is controlled by the Flash Descriptor, another region of the full SPI image. In a lot of cases where the flash descriptor is locked (no ME read/write access from CPU/BIOS), the ME region of the OEM’s latest SPI image won’t be reflashed at all. So if for example you had the ME updated with FWUpdate and the FD is locked, the former will stay at the same version no matter what BIOS you flash. It depends on the system’s configuration.
To ZioGTS,
The file checked with UBU (ME Analyzer) is one thing.
UBU tool gives this information as is read in the BIOS file.
UBU tool never updates MEI firmware chipset.
The contents of the MEI firmware chipset can be updated (flashed) only with specific MEI tool, not with UBU tool.
The contents of the MEI firmware is what is used in fact in the machine.
I ignore what is the need of a MEI ‘firmware’ bios module…
Thank you guys, now I got it! 
SoniX,
mostly vendors updated their X99 BIOS’s with upcoming Broadwell-E CPU.
When you planning to incorporate BDWe in UBU ?
Thanks.
Once the available microcode for BDW-E (LGA2011v3). I do not know CPUID processor BDW-E.
cpu000406F1_platEF_ver00000019_date#17-03-2016 for BDWe.
cpu000406F1_platEF_ver00000019_date#17-03-2016.zip (24.2 KB)
I’m not sure. But I will add support when there is accurate information.
It’s either 406F0 or 406F1. Both ASRock and Gigabyte’s new BIOS have only added 406F0 & 406F1 compared to the last BIOS releases. So it’s definitely one of these two.
We’ll have to wait and see which the firmware will be updated frequently.
I do not want to risk being uncertain
Yes of course. This page also verifies that. But I don’t know between F0 and F1, we’ll see.
For future reference, it seems that the KBL-H/S cpuid will be 906Ex.
DrvVer v0.20.2
While the added displaying microcode:
- Broadwell-E CPUID 0406F1
- Kabylake CPUID 0906E0
drvver_v0_20_2.rar (46.2 KB)