Intel (Converged Security) Management Engine: Drivers, Firmware and Tools (2-15)

Special Topics Intel Management Engine
641

getyasome,

Original BIOS 2103 for ASUS Z87-Deluxe came with 9.0.30.1482 ME firmware.

How you post pic with 9.1.2.1010…?..you flash before?..(and update to 9.1.10.1005 which is for Intel 9 system).

Something will not work properly…as… Fan speed or Bus Speed (BCLK) with this firmware.
You should flash with 9.0.31.1487, which is latest for your Intel 8 series board.

642

Hey, I found 6 series mobile chipset me drivers7.1.70.1198 seems to be a full version. ：http://downloads.dell.com/FOLDER01232491…4_SETUP_ZPE.exe

643


These drivers have been around for quite some time now actually from lenovo and others

644

@ plutomaniac:

Thank you very much for starting this great thread.
I am glad, that I found an Intel ME expert, who was willing and had the time to do it.

Thanks again!
Fernando

645

Thank you for your kind words Fernando even though I’m not an expert. Still learning the basics. Generally there are things that I want to try (like what lordkag was saying regarding cutting ME update files etc) but unless I have a programmer or Dual BIOS system, I don’t want to risk bricks. That may hold me back but I do like to share my experiments, knowledge and found stuff (in this case tools) which my help others.

646

Intel ME System Tools v10.0.30.1072

http://www.station-drivers.com/index.php…startdown/1019/

647

Updates since 30/10/2014:

* Updated ME System Tools v10.0 Full Package

Flash Image Tool: 10.0.30.1054
Flash Programming Tool(DOS): 10.0.30.1054
Flash Programming Tool(EFI): 10.0.30.1054
Flash Programming Tool(Windows): 10.0.30.1054
Flash Programming Tool(Windows64): 10.0.30.1054
FWUpdate(Local-DOS): 10.0.30.1054
FWUpdate(Local-EFI): 10.0.30.1054
FWUpdate(Local-Win): 10.0.30.1054
FWUpdate(Local-Win64): 10.0.30.1054
MEInfo(DOS): 10.0.30.1054
MEInfo(EFI): 10.0.30.1054
MEInfo(Windows): 10.0.30.1054
MEInfo(Windows64): 10.0.30.1054
MEManuf(DOS): 10.0.30.1060
MEManuf(EFI): 10.0.30.1060
MEManuf(Windows): 10.0.30.1060
MEManuf(Windows64): 10.0.30.1060
CCT(DOS): 10.0.30.1054
CCT(EFI): 10.0.30.1054
CCT(Windows): 10.0.30.1054

* Added ME System Tools v3.x Full Package
Flash Image Tool: 1.7.3.1105
Flash Programming Tool(DOS): 0.9.5
Flash Programming Tool(Windows): 0.9.5
Fixed Address Programming Tool(DOS): 3.0.9
Fixed Address Programming Tool(Windows): 3.0.9
FWUpdate(Local-DOS): 3.2.2.1035
FWUpdate(Local-Win): 3.2.2.1035
MEInfo(DOS): 3.0.0.1105
MEInfo(Windows): 3.0.0.1105
MEManuf(DOS): 3.0.0.1105
MEManuf(Windows): 3.0.0.1105
MENVM(Windows): 3.0.0.1105
iAMT_Tools: 3.0.0.1105
QST_Tools: x.x.x.1105

Added ME System Tools v5.x Full Package
Flash Image Tool: 5.1.0.1167
Flash Programming Tool(DOS): 5.1.0.1167
Flash Programming Tool(Windows): 5.1.0.1167
FWUpdate(Local-DOS): 5.2.50.1042
FWUpdate(Local-Win): 5.2.50.1042
MEInfo(DOS): 5.0.0.1167
MEInfo(Windows): 5.0.0.1167
MEManuf(DOS): 5.0.0.1167
MEManuf(Windows): 5.0.0.1167
AMT_Tools: 5.1.0.1004
QST_Tools: 1.5.5.1018
TPM_Tools: 5.x.0.1167

 Added at ME System Tools v4.x → iAMT Tools
Flash Image Tool: 4.1.3.1031
Flash Programming Tool(DOS): 4.2.0.1017
Flash Programming Tool(Windows): 4.2.0.1017
FWUpdate(Local-DOS): 4.2.0.1017
FWUpdate(Local-Win): 4.2.50.1053
MEInfo(DOS): 4.1.0.1023
MEInfo(Windows): 4.2.50.1053
MEManuf(DOS): 4.1.0.1023
MEManuf(Windows): 4.1.0.1023
TPM_Tools: 4.1.0.1023
iAMT_Tools: 4.1.0.1023

* Added at ME System Tools v6.x → QST Tools, AMT Tools, BraidWood Tools, FITC v6.0.0.1115 (additionally supports P57 & PM57 systems), New Documentation
Flash Image Tool: 6.0.0.1184
Flash Programming Tool(DOS): 6.0.0.1184
Flash Programming Tool(Windows): 6.0.0.1184
FWUpdate(Local-DOS): 6.2.0.1022
FWUpdate(Local-Win): 6.2.0.1022
MEInfo(DOS): 6.0.0.1184
MEInfo(Windows): 6.2.0.1022
MEManuf(DOS): 6.0.0.1184
MEManuf(Windows): 6.0.0.1184
MEVerificationUtility(Windows): 1.0.3604
UpdParam(DOS): 6.0.0.1184
QST_Tools: 2.x.x.1184
NANDUtil(DOS): 0.24

 Included alongside is FITC v6.0.0.1115 which also has P57 & PM57 system support.

Thank you Stasio (ex58) for the link!

1 Like
648

Hi plutomaniac.

I currently have an Asrock Z68 Extreme4 Gen3 FW 1.10, which supposedly features ME FW 7.1.10.1065 according to BIOS boot screen. My OS is Win7 Ultimate SP1 x64. I have no ME drivers/package installed, just the chipset (INF) drivers (“Intel(R) 6 Series/C200 Series Management Engine Interface - 1C3A” is shown in my Device Manager).

I’m trying to use MEInfo in your 7.1 package in order to check my ME, without success (errors 1002 “Could not determine ME FW version”, 9458 “Comm error between app and ME module” and 9459 “Internal error, could not determine FW features”). I’ve tried both Windows and DOS (boot to clean DOS) MEInfo tools. The fact that I have no ME driver installed should not be the cause (not in DOS at least).

My final goal is update to UBU-modded BIOS 2.30, which includes ME FW 8.0.2.1410 (according to UEFITool), and then update to latest 1.5MB ME FW for Z68 8.1.52.1496. I hope MEInfo for ME8 works then, but I’m afraid MEInfo for my current ME7 should work as well. Don’t know what else to try before flashing my new BIOS.

649

@ Reducer:

According to ASrock’s website your motherboard seems to come with ME8 support out of the box. The oldest BIOS at their site (v2.10) includes ME v8.0.2.1410. Maybe they removed all older versions for risk of bricking systems due to a ME8 to ME7 downgrade. Are you sure you have a ME7 firmware, have you tried the ME8 tools to see if they work instead? I thought about the HECI driver not being installed properly but as you correctly mentioned that wouldn’t explain the incapability of the DOS version running. Try MEInfo v8 and let me know how it goes.

The latest BIOS for your motherboard is actually a newer one, Beta v2.31A from 25/02/2013 compared to v2.30 from 16/10/2012. It can be found at the BETA Zone. I suggest you mod that one with UBU as it’s newer and provides official Windows 8 support according to the changelog. BIOS v2.31A also includes ME Firmware v8.1.0.1248 by default but as you said you can safely update to v8.1.52.1496 afterwards.

@ All:

* Added at ME System Tools v9.1 → Flash Programming Tool EFI v9.1.10.1000
* Updated at ME System Tools v9.1 → Flash Programming Tool DOS v9.1.2.1000 to v9.1.10.1000

Flash Programming Tool(DOS): 9.1.10.1000
Flash Programming Tool(EFI): 9.1.10.1000
Flash Programming Tool(Windows): 9.1.2.1000
Flash Programming Tool(Windows64): 9.1.2.1000
FWUpdate(Local-DOS): 9.1.2.1000
FWUpdate(Local-EFI): 9.1.2.1000
FWUpdate(Local-Win): 9.1.2.1000
FWUpdate(Local-Win64): 9.1.2.1000
MEInfo(DOS): 9.1.20.1020
MEInfo(EFI): 9.1.20.1020
MEInfo(Windows): 9.1.20.1020
MEInfo(Windows64): 9.1.20.1020

650

Ok plutomaniac, this is just a quick update on my tests. Full details tonight, with reports. Under my Win OS I’ve been completely unsuccessful in using both the 7.1 and 8.1 tools. However, I retried the DOS ones, this time using the Rufus tool to create the boot device and success!. Definitely my MoBo FW 1.10 features ME 7.1.10.1065. One interesting thing I’ve noticed is that “Host Read Access to ME” feature is DISABLED. Maybe this is preventing access of the tools from Windows. I’ve also run MEManuf and created a backup of my ME 7.1 with FWUpdLcl. MEManuf reports 1 error. More tonight.

EDIT: I attach here text files containing the outputs from MEInfo, MEManuf and FWUpdLcl for Win and DOS from both ME 7.1 and 8.1 packages. My ME FW 7.1.10.1065 dump is also included, but I cannot find a reference for integrity checking. I can only confirm that DOS FWUpdLcl 7.1 reported a “Successful” backup creation and that it matches byte size and relative data-FF padding structure of latest known 7.1.60.1193, I mean looks like a good dump.

As I’ve reported this morning, only the DOS versions of the tools were able to query my ME firmware. MEManuf 7.1 is reporting 1 failed test (of 11):

Policy Kernel - SMBus: Read byte - Failed
SMBus Read Byte PEC Failure

MEInfo 7.1 and FWUpdLcl 7.1 didn’t report errors. For the record, FWUpdLcl 7.1 reports that blacklisted FW versions in my ME are two: 7.0.10.1202 and 7.1.10.1062.

Regarding the risks of the 1.x to 2.x transition (SnB to SnB+IvB support) in my MoBo BIOS FW, yes I’m aware of them. Initial lack of proper updating instructions, due to the additional (and unexpected by the end user) ME FW update step from 7 to 8 after BIOS flashing, caused a lot troubles, Asrock having to mail properly flashed BIOS chips. Risky business this BIOS update, yes. I also researched about 2.30 vs latest 2.31a (beta) some months ago. Some users reported overclocking stability issues and ended downgrading to 2.30. Since I will not need the Win 8 compatibility features before I replace my MoBo, I will stick with latest stable version 2.30 instead.

651

Host Read Access to ME is Disabled for me as well since if I’m not mistaken this shows whether the Descriptor is locked which it pretty much always is for security reasons. Only Gigabyte seems to be leaving it unlocked which makes it so much easier to update or modify the ME firmware. No matter how locked the Descriptor is though, you should be able to run MEInfo.

When you say FW 1.10 you mean BIOS v1.10. Yeah, ASRock has removed all older versions prior to v2.10 (which is the first one to support ME8 and thus Ivy Bridge) in order to avoid consumer bricks. In order for the ME upgrade from v7 → v8 to be completed correctly, you need to leave the USB flash drive connected during the whole process. That’s because the ME firmware needs to be updated together with the new BIOS. Otherwise you’ll end up with a brick. Fist, the image will be copied to the BIOS chip, then a restart will occur (at this point do not remove the flash drive!!!), the ME will be updated and then follow the prompts.

Alright, when you are home write here the full report and we’ll proceed from there.

652

hi, I’ve formated my ssd a few hours ago and now i’m installing all the drivers. I came here to check the ME drivers and I step with a problem. In the older guide which made fernando, it said for the z68 chipset, it needs the v8.1.52.1496 ME firmware, so I flashed it a few months ago. Then today I see that originaly z68 chipset use the v7 ME firmware, is this a problem? I have a p8z68-v pro motherboard, with the lastest bios 3603 with w8.1 x64.
Do I need to downgrade to lastest v7 fw? also, which driver should install? v7, v8 or v10?

thanks and sorry about my poor english haha.

653

@all:
As you have probably noticed the first post was rewritten for the most part by combining Fernando’s thread with the System Tools & Legacy Firmware one. More info/details were added as well as older drivers, firmware, tools etc.

Updates in detail:

Added ME System Tools section: v10.0, v9.5, v9.1 (incomplete), v9.0, v8.1, v7.x, v6.x, v5.x, v4.x, v3.x, v2.x
 Added at Drivers: v9.5, v8.1, v7.1, v6.2 (bare .inf & full 1.5M/5M installer packages)
Added at 1.5MB Firmware: v6.0.0.1184, v4.2.30.1040
 Added at 5MB Firmware: v6.2.60.1066, v5.2.50.1039, v4.2.60.1060, v3.2.60.1060, v2.6.50.1056
Added at MEInfo Tool: v5.0.0.1167, v4.2.50.1053, v3.0.0.1105, v2.5.0.1084
 Added at MEManuf Tool: v9.5.14.1724, v5.0.0.1167, v4.1.0.1023, v3.0.0.1105, v2.5.0.1084
Added FWUpdate Tool section: v10.0.30.1054, v9.5.14.1724, v9.1.2.1000, v9.0.22.1467, v8.1.40.1456, v7.1.50.1166, v6.2.0.1022, v5.2.50.1042, v4.2.50.1053, v3.2.2.1035, v2.5.1.1084

 Added at ME System Tools v6.x: Manufacturing with Intel ME Ignition Firmware, New PCH SPI Programming Guide (v1.5 for package & v1.3 for Braidwood Tools)
* Added at ME System Tools v7.x: UpdParam Tool, IUSManuf Tool, Configuration Tools, 5MB FW Bring Up Guide, 5MB MEBX User Guide, AMT 7.0 OEM WebUI Guide, SW Installation Guide

Flash Image Tool: 7.1.10.1065 *
Flash Programming Tool(DOS): 7.1.20.1119
Flash Programming Tool(Windows): 7.1.20.1119
Flash Programming Tool(Windows64): 7.1.20.1119
FWUpdate(Local-DOS): 7.1.50.1166
FWUpdate(Local-Win): 7.1.50.1166
MEInfo(DOS): 7.1.20.1119
MEInfo(Windows): 7.1.52.1180
MEManuf(DOS): 7.1.20.1119
MEManuf(Windows): 7.1.20.1119
CCT(DOS): 7.1.20.1119
CCT(Windows): 7.1.20.1119
UpdParam(DOS): 7.0.4.1197
IUSManufTool(DOS): 7.0.4.1197
IUSManufTool(Windows): 7.0.4.1197
Added at ME System Tools v8.1: IUSManuf Tool, Configuration Tools, 5MB FW Bring Up Guide, 5MB MEBX User Guide, AMT 8.0 OEM WebUI Guide, SW Installation Guide
Flash Image Tool: 8.1.40.1456
Flash Programming Tool(DOS): 8.1.51.1476
Flash Programming Tool(EFI): 8.1.51.1476
Flash Programming Tool(Windows): 8.1.51.1476
Flash Programming Tool(Windows64): 8.1.51.1476
FWUpdate(Local-DOS): 8.1.40.1456
FWUpdate(Local-EFI): 8.1.40.1456
FWUpdate(Local-Win): 8.1.40.1456
FWUpdate(Local-Win64): 8.1.40.1456
MEInfo(DOS): 8.1.56.1541
MEInfo(EFI): 8.1.56.1541
MEInfo(Windows): 8.1.56.1541
MEInfo(Windows64): 8.1.56.1541
MEManuf(DOS): 8.1.51.1476
MEManuf(EFI): 8.1.51.1476
MEManuf(Windows): 8.1.51.1476
MEManuf(Windows64): 8.1.51.1476
UpdParam(DOS): 8.1.40.1456
IUSManufTool(DOS): 8.1.0.1265
IUSManufTool(Windows): 8.1.0.1265
CCT(DOS): 8.1.0.1265
CCT(EFI): 8.1.0.1265
CCT(Windows): 8.1.0.1265
 Added at ME System Tools v9.0: Configuration Tools, SW Installation Guide

If you check at the bottom of the topic, you will see this regarding the ME v8 tools + firmware: * Also some 6-series systems which can be upgraded to ME firmware v8.x. Some 6-series desktop systems were able to be upgraded to ME v8 instead of the stock ME v7 in order to support Ivy Bridge cpu’s. If your’s motherboard is Ivy Bridge compatible or was made with a latter BIOS revision then you are fine.

No, if your motherboard received a Ivy Bridge compatible BIOS which came with ME8 you can safely upgrade to the latest ME v8 firmware version.

The latest v10 drivers supports all 6-series & up systems. I suggest you install the latest v10 and only if you are facing issues should you consider the older versions. The older drivers are provided (as mentioned in the first topic) for compatibility reasons in case of issues with the newer drivers. Examples:

–> At my HM65 laptop (6-series, ME7 Firmware) I use the latest v10 drivers without any issues.
–> At my Z77 desktop (7-series, ME8 Firmware) I use the v8.1.40.1416 drivers due to a sleep issue with anything after that (also mentioned at first topic).

654

Hi all. is anyway to enable AMT on 1.5 mb firmwares ?

655


No, they are not designed for that.

656

Hi again!

As I reported here, I was only able to query my ME 7.1 from DOS. Windows tools were no able to connect to my ME firmware. I had not ME driver installed on my Win 7 OS, just the chipset (INF) drivers. Well, after installing ME driver 10.0.30.1054 (driver only, from Device Manager>Intel(R) 6 Series/C200 Series Management Engine Interface - 1C3A>Update Driver Software…) the Windows ME systems tools now work. So definitely they require ME driver installed in OS in order to query ME firmware.

I was able to redump my ME FW 7.1.10.1065 from Windows and it is a SHA1 match of the DOS dump. No errors from MEInfo either. Sadly I get the same failed test in Windows after running MEManuf:
Policy Kernel - SMBus: Read byte - Failed
SMBus Read Byte PEC Failure

I’ve checked Device Manager and I have:
Intel(R) 6 Series/C200 Series Chipset Family SMBus Controller - 1C22

but this comes from the chipset (INF) drivers, no actual driver installed. Do you have an actual driver for this device in your OS? Anyway, it wouldn’t explain the error also being reported under DOS.

657

Intel (R) 6 Series/C200 Series Chipset Family SMBus Controller - 1C22 in the notebook touchpad driver is covered on the table board is not know.

658

@ Reducer,

The Intel INF is not a driver but a utility. It just tells Device Manager to not show yellow exclamation marks for certain devices by installing a dummy/fake driver. This also applies for the ME device. The dummy ME “driver” doesn’t work with the tools of course which require the ME HECI driver. The latter can be downloaded at the first post.

As I said before, some 6-series systems (ME v7) can be upgraded to ME v8 which adds Ivy Bridge support. Your motherboard is upgradable that way because ASRock made it possible. However, first you need to update your BIOS to the latest version which is the BETA one. I wrote what to do by being careful to not remove the flash drive before the new bios + v8 ME is written to the flash chip.

Regarding the MEManuf error, it could either mean a non-properly functioning ME or a hardware problem of sorts. MEManuf is geared more towards hardware problems but it could detect firmware ones as well. Before updating your BIOS and moving to v8 ME firmware let’s try something - maybe it will “repair” your current v7 ME firmware. Download ME v7.1.60.1193 and the v7 FWUpdate tool. Then follow the instructions on how to update your current ME from 7.1.10.1065 to 7.1.60.1193. After a reboot, run MEInfo to make sure you are running on 7.1.60.1193 and then MEManuf to see if the problem is still there.

659

(Wrong post) Please delete.

660

What’s wrong with you? This is obviously a 5MB firmware.