Please report all spam threads, posts and suspicious members. We receive spam notifications and will take immediate action!

If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Do not confuse ME firmware and MEI driver, ME FW is part of the BIOS while MEI driver is installed on Windows and allows software to communicate with ME firmware in BIOS (as some overclocking and fan management software).

2 - Checking ME firmware

2 - Checking ME firmware

A - Update ME FW with MEupdate (FWupdate)

First, even if it is irrelevant since the challenge is to insert the ME FW directly in the BIOS, I add here how to update under Windows with FWUpdLcl for those who have difficulty with the command prompt.

- when finished and according to CodeRush, a complete power off is required to restart ME.

Originally Posted by CodeRush

If you flash BIOS with different ME version then current one, you need to use poweroff command after successful flashing to ensure ME restart. ME is powered with standby power line and doesn't restarts on normal reset, so you must use that command or remove power completely and wait for 30 secs to reset ME state. If they have same versions - normal reset is enough.

Also you can flash the same ME FW version (if you think it's corrupted) with the following command :

MEManuf validates ME functionality (verifies that all its components have been assembled together correctly) on the manufacturing line. The tool accomplishes this by invoking the test program embedded in the ME firmware. The test covers the following features: SMBus Interface, BIOS and BIOS/FW connectivity, C-Link (ME-ICH and ICH-Shilo), EC, iTPM, Wireless connectivity.

With FITC you can check which version of ME firmware is in a BIOS file, so no need to have the motherboard with this BIOS installed :
- download Flash Image Tool above
- run fitc.exe
- just drag and drop BIOS file within FITC
- ME firmware version is easily showed :

Unfortunately, it doesn't works with certain brand (Asus…), BIOS is not recognized so we have to extract ME FW before being able to read version it in FITC…

Originally Posted by Pacman

... to open Asus Cap file in FITC, you can use "fd44cpr" from FTK package.
"fd44cpr filename.rom filename.rom" have to enter filename twice,
then the Cap header is removed and works with FITC.
The Cap header can also easily be removed manually in a Hexeditor, tested with Asrock also.
It has worked with the Z87 BIOSes i've tried.

4 - Setting ME firmware

4 - Setting ME firmware

And now the most laborious part…

I want to emphasize that we are now entering a deep modification of BIOS, before playing with the insertion of ME FW in the BIOS you need to master BIOS flashing and usage of Dual-BIOS to be able to revert back if necessary. (BIOS flashing thread)

ME firmware is not a read only as a ROM or microcode. When comparing many ME files with HxD editor : original ME firmware (generic production/preproduction file provides in MEupdate), ME region extracted from original BIOS file and from BIOS chip with @BIOS or Q-Flash : all files are different ! While ROM and µcode stay unchanged in BIOS, using FWUpdLcl update ME FW parts while keeping previous settings, of course I could be wrong but I suspect that data is written in the ME region during the first boot after BIOS flash.
This means ME firmware can’t be pasted “as it is” in BIOS file, that’s why it must be prepared to match with chipset platform and manufacturer BIOS settings before being included in BIOS.
To match the settings of the new ME FW with the target BIOS, I extract two identical FITC to open and compare the original BIOS with the ME FW build. The principle is the same for different chipset, but for example Z87 has a lot more settings.

A - ME FW settings for Z77 (same for Z68/P68)

So we need to work with 2 FITC opened side by side… a wide screen is useful ! (but for the forum's width I put both FITC one above the other)
- open first FIT and drag and drop within original BIOS
- open a second FIT and drag and drop ME FW to adjust… but in this FITC for building of new ME FW, go under Descriptor Region/Descriptor Map to set Number of flash to 0, it will be necessary to build a file that contains only the ME FW :

- as with original BIOS, in new ME FW we set SKU to the matched platform : Intel 7 Series Chipset and Intel Z77 - Desktop (6 Series and Z68 Desktop for Z68/P68)

- then develop ME region/Configuration to check each of the original BIOS settings and apply them to the new ME FW… but for example there is some impact between different fields : in Power Packages we have to set Power Pkg 2 Supported to "false" to be able to disable M3 Power Rails Availability in ME sub-settings :

… then we can return to ME to set M3 Power Rails to False :

- continue with all settings, Manageability Application can't be open because it's not for Z77 chipset… be care in ME Debug Event Service, double-click on Event Filters and check Group 1 (must be 0x00000001) and Group 76 (0x000000FE) :

- under FCIM/BTM Specific ICC Registers, we have to copy/paste each settings, for example changing 0x00011A33 to 0X00011A34 change settings below :

- generally, the adjustable settings are yellow ... but not always, so take the time to check them all ! Continue with all settings… it is a long job, but much shorter than Z87 !

- and when all is done, check 2 or 3 times that everything is perfect !
- hit the build button (or menu Build/Build image F5), you obtain your prepared ME FW named outimage.bin (size 1524kB), you can rename it with appropriate name for further usage (thereafter for my example I name it ME_8.1.51.1471_Z77.bin)

B - ME FW settings for X79

Same job with few differences…
- when opening many X79's original BIOS, FITC returns error with SKU non recognized (but we will not have this error with the modified BIOS with our prepared ME FW), you have to set it as Intel C600 Series Chipset, I don't see any difference between Intel Patsburg A, B/J, D, T and X79. Example with G1assassin2 F12u SKU error :

Good news with the Z87 chipset : the first settings are almost identical to the ME FW default... Now the bad news: the last settings under Integrated Clock Controller are very likely to be particularly tedious, especially in Hardware Register : it's fast but under ICC Profile 0 and ICC Profile 1 there are more than 500 lines to check !
Be brave, I always check 2 or 3 times !

Most settings to change are yellow but not always, so be meticulous !

D - Prepared ME FW files

You can save some time by using my ME FW prepared, but I still advise you to check because there may be some small differences for some BIOS :

Re: About Intel Management Engine firmware

Nice thread, fred! (Rhyme unintentional.)

Any chance you've also got the manuals for the straps and tables?

I may have to find the time to do a write up on the PCH Straps and MAS; technically MAS\GbE is where changes to ethernet are supposed to be made including firmware update (\GbE Region). On the plus side, I can now confirm that Gigabyte did in fact, completely screw the pooch on the F4 release BIOS. Set ME to Workstation from HED and failed to use correct SKU (chipset identifier.)

It's not a real high end workstation till it's got four sockets, eight video cards, and takes two thirty amp circuits to run. Yes, I build those kind of systems too.

Re: About Intel Management Engine firmware

Excellent initial post!!
These thread will probably be stickied sooner rather than later.
I think that you carried the reserved thread count too 2 far.

Thanks, yes I did in doubt, now deleted, but I know it is possible to insert posts later if necessary.

Originally Posted by RootWyrm

Nice thread, fred! (Rhyme unintentional.)
Any chance you've also got the manuals for the straps and tables?
I may have to find the time to do a write up on the PCH Straps and MAS; technically MAS\GbE is where changes to ethernet are supposed to be made including firmware update (\GbE Region). On the plus side, I can now confirm that Gigabyte did in fact, completely screw the pooch on the F4 release BIOS. Set ME to Workstation from HED and failed to use correct SKU (chipset identifier.)

Nice rhyme . I gave links for all guides i have, i played with copy/paste with PCH Straps for LAN issue in G1.assassin2 F12t... but yet i haven't any other tool working with other region...

Re: About Intel Management Engine firmware

About Z77 vs Z87, Google will help you better than me... I do not have the knowledge necessary to answer you specifically.
I'm sure put a FW ME 9 in Z77 BIOS would result in infinite boot loops, many clock settings and frequencies are different... i'm not mad enough to try it
ME FW 8 & 9 have the same size, Z77's BIOS are 8MB while Z87's BIOS are 16MB.