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

grml4d · January 16, 2015, 5:29am

thank you for the file .
i downloaded it .
i have trouble with my internet access from the end of november :
http://imgur.com/a/0reRw
after the electricity truck destroyed my phone line
i changed of provider and gone back to the soviet-french-telecom mid december…
so i had a VDSL running at 4Mb/s download and 80kb/s up last week
http://imgur.com/a/heAMY

as i complained again my line was cut or suspended and now i use a 3G texto thingy to access the web…
i used it to buy a sattelite access with 22 Mo down and 6Mo up for 50 euro while orange is at 40 euro for this …

i report how it turns with the file as soon as possible

plutomaniac · January 16, 2015, 1:54pm

Update:

Yes, I was right guys. For Intel 5-series 5MB ME images (8MB SPI size) there are two SKUs: Desktop (DT) and Mobile (MB). Previously I thought MB meant MegaBytes but that’s a wrong assumption.

Up until now I was giving only the mobile SKU for 5MB ME6 named: PCH_8M_MBUPD_Production
From now on I will add the desktop SKU for 5MB ME6 named: PCH_8MDT_UPD_Production

Now, since OEMs used (& use) to rename the binaries I need to check the $SKU to identify them. It seems to slightly change from binary to binary but I figured it out (maybe @lordkag disagrees? - LINK):

03 00 00 00 77 FC 6E 00 → Desktop
03 00 00 00 77 FC EE 00 → Mobile

03 00 00 00 77 DC 6E 00 → v6.x
03 00 00 00 77 FC 6E 00 → v6.0

Now, based on the binaries I have found and if I am correct, the latest Desktop (DT) ME6 5MB firmware is v6.2.50.1062 from an HP package. The “latest” definitely Desktop firmware (based on the file’s name) is v6.0.40.1215 and it’s the file I have given to grml4d HERE.

So, @grml4d (once your internet is stable, no worries in the meantime) let me know if the one I gave you works. If it does, I’ll give you the (almost latest) v6.2.50.1062 firmware to try which I suspect is for Desktop (DT) models as well.

iceman · January 16, 2015, 2:04pm

hm57 not support intel active management technology, but it also have 5mb me firmware and 1.5m me firmware, hm76 \ hm77 seem to have the situation 1.5mb me firmware and 5mb me firmware co-existence, why would this happen? Depending on whether Intel?

plutomaniac · January 16, 2015, 6:32pm

I updated my previous findings and I am now certain of what ME6 5MB SKU is for Desktop and for Mobile. Once it’s verified, I will add it to the main post.

@ grml4d:

Since you unfortunately (I’ve been there) have slow internet and probably limited data, I have attached for you another file. Please test this one, not the previous one. If everything goes properly, this should update your HM57 machine from ME v6.0.31.1208 to v6.2.50.1062.

PCH_8M_DT_UPD_Production_(6.2.50.1062).rar (1.8 MB)

grml4d · January 16, 2015, 9:47pm

i took the new file because previous failed like the lenovo .

here is the dos 7 console messages obtained with verbose parameter

Intel (R) Firmware Update Utility Version 6.2.0.1022
Copyright (C) 2007-2011, Intel Corporation. All rights reserved.

Trying to connect to MEI driver.
***** Flash Info *
Version : 6.0.31.1208
Last Update Staus : 4
EnabledUpdateInterfaces : 1

Image Info ******
Version : 6.0.40.1215
Communication Mode: MEI
Checking firmware parameters…

Warning: Do not exit the process or power off the machine before the firmware update process ends.
Initiating firmware update process…

Sending the update image to FW…
Image successfully sent to FW.
FW verifying and updating the image on flash…
End Reply : Status: 4

Error 8704: Firmware update operation not initiated due to a SKU mismatch

i ll try the new file right now , i pray for success ; before coming i asked pegatron about the above error and say a word about the forum 's topic .
mainboard is IMPIP-M5 (E66) : http://h10025.www1.hp.com/ewfrf/wc/docum…cname=c02017992

lordkag · January 16, 2015, 9:53pm

@plutomaniac

I think you are right. Just that 03000000 is the length of the field ( 3 * 4 = 0xC ) and the SKU is actually 006EFC77 and so on. Since Intel doesn’t say anywhere what does numbers mean, we can assume that they can be grouped like 6E = DT, EE = MB. Since the flasher complains about the SKU mismatch, there can be no harm in letting users test this.

lordkag · January 16, 2015, 10:02pm

If your board is HM57 based, you need the Mobile ME. This would mean either PCH_8M_MB_UPD_Production_(6.0.30.1203).bin or PCH_8M_MB_UPD_Production_(6.2.60.1066).bin

If 6.2.60.1066 fails, then the third byte of the SKU is also important, so you are stuck at 6.0.30.1203 for now.

plutomaniac · January 16, 2015, 11:41pm

@ grml4d:

Well yes, normally you need the MB firmware as it’s a mobile platform. I don’t know why the latest MB v6.2.60.1066 firmware we have here (from Lenovo) is not working for your mobile system. It should. The finding that there is also a desktop firmware was coincidental but I asked you to try it just in case.

Without a look at your current firmware I cannot make any more progress really. Go to Flash Programming Tool and run fptw -d ME.bin -ME. Does it say Error 26? If yes, we cannot take a peak at your ME region unfortunately.

@ lordkag:

Thanks for looking into it. What do you mean by “third byte of the SKU”? FC or DC? This definitely has to do with whether it’s v6.0 or v6.1/v6.2. I don’t see how that could determine a firmware as coming from a wrong SKU.

Either way, the last MB v6.0 is v6.0.41.1216. I don’t think it will make any difference for grml4d but he can try it. I have attached it below.

PCH_8M_MB_UPD_Production_(6.0.41.1216).rar (2.35 MB)

grml4d · January 17, 2015, 5:42am

i used both dos and windows version of fpt and got same error :

Intel (R) Flash Programming Tool. Version: 6.1.20.1057
Copyright (c) 2007-2010, Intel Corporation. All rights reserved.

Platform: Intel(R) HM57 Express Chipset Revision: B3
Reading HSFSTS register… Flash Descriptor: Valid

— Flash Devices Found —

Error 103: There are no supported SPI flash devices installed. Please check connectivity and orientation of SPI flash device.

with the i parameter i got something else :

Intel (R) Flash Programming Tool. Version: 6.1.20.1057
Copyright (c) 2007-2010, Intel Corporation. All rights reserved.

Platform: Intel(R) HM57 Express Chipset Revision: B3

Error 360: Invalid Block Erase Size value in "me.bin".

i used latest file you gave and renamed it me.bin , with -d parameter i used me.bin name too and an other not pointing to an existing file

fwupdlcl is not able to flash the file…

plutomaniac · January 17, 2015, 1:12pm

As I said earlier 5-series was a total mess, everything became a lot simple after 6-series. HM57 could probably accommodate either a 1.5MB ME (4MB SPI flash) or a 5MB ME (8MB SPI flash).

But we still don’t know whether you have a 1.5MB or 5MB ME firmware image. We can find that by checking your motherboard’s SPI flash size. If it’s 4MB -> 1.5MB SKU otherwise if it’s 8MB -> 5MB SKU. An easy way to determine that is by running FPTw -d x.bin. For example on my 6-series system I can see that:

To continue and not go blind it’s important to know whether you have an 1.5MB or 5MB ME image first. If fpt shows these weird errors (other than error 26), can you run MEManuf to check if everything is ok with the ME?

lordkag · January 17, 2015, 10:24pm

I don’t think the number 6.x should belong in the SKU. Rather than that, 6.x was released for new SKU, kind of like Lenovo writes in the changelog of some ME Firmwares - “added support for Thinkpad Carbon XYZ”.

To find more about grml4d system, he should do “fpt -i” to find the flash chip - the ID can easily be found online, since the chips are well documented. Next he should do “meinfo - verbose” and “memanuf - verbose” to check ME capabilities.

plutomaniac · January 17, 2015, 11:28pm

So if I understand what you are saying properly, your opinion is that 6.1 is for different SKUs than 6.0? Meaning that for example an FC 6E machine can only update to a latter FC 6E firmware? This has never happened at all the previous or following ME firmware versions (4,5,7,8 etc).

Other than that, indeed it doesn’t make sense to have the ME major version version at the $SKU for me as well. For good measure, before posting those results for the different 5MB SKUs, I downloaded all the firmware from Lenovo (6.0.31 up to 6.2.60) and checked the $SKU. All of them were EE (makes sense, mobile) and 11/13 were DC (v6.x) with only the remaining two being FC (v6.0.31 & 6.0.41). So my theory makes perfect sense fact-wise.

What Lenovo means by “added support for xxx model” I do not know exactly. It’s not like you can set something “laptop-specific” via FITC (only platform specific) so my guess so far has been that this means “users of this xxx model will from now on be able to download the ME firmware from it’s support page”.

grml4d · January 18, 2015, 12:00pm

according to version number in the lenovo readme, my firmware is a 8M first release .

here are the info i got :

Intel (R) Flash Programming Tool. Version: 6.0.30.1202
Copyright (c) 2007-2009, Intel Corporation. All rights reserved.

Number of LPC Devices supported: 61
LPC Device Id: 3B0B.
Platform: Intel(R) HM57 Express Chipset Revision: B3
Initializing SPI utilities
Reading HSFSTS register… Flash Descriptor: Valid

— Flash Devices Found —

Error 103: There are no supported SPI flash devices installed. Please check connectivity and orientation of SPI flash device.

Intel(R) MEInfo Version: 6.2.0.1022
Copyright(C) 2005 - 2011, Intel Corporation. All rights reserved.

Platform stepping value is 6

FW Status Register: 0x00000245
FW Status Register1: 0x60000000

CurrentState: Normal
ManufacturingMode: Disabled
FlashPartition: Valid
OperationalState: M0 with UMA
InitComplete: Complete
BUPLoadState: Success
ErrorCode: No Error
ModeOfOperation: Normal
Phase: HOSTCOMM Module

SMBIOS table starting address is 000FBAD0
Maximum SMBIOS table size is 219
Searching end-of-table (double null) terminator
Found end-of-table (double null) terminator, size 69

Get ME FWU info command…done

Get ME FWU version command…done

Get ME FWU feature state command…done

Get ME FWU platform type command…done

Get ME FWU feature capability command…done

Get ME FWU OEM Id command…done
FW Capabilities value is 0x1C60
Feature enablement is 0x1C60
Platform type is 0x321

Error 9269: Access to SPI Flash device(s) failed
Intel(R) ME code versions:

BIOS Version: 6.08
MEBx Version: 0.0.0.0
Gbe Version: Unknown
VendorID: 8086
PCH Version: 6
FW Version: 6.0.31.1208
UNS Version: Not Available
LMS Version: Not Available
MEI Driver Version: 6.0.0.1179
Wireless Hardware Version: Not Available
Wireless Driver Version: Not Available

FW Capabilities: 7264

Intel(R) Anti-Theft Technology PC Protection
Intel(R) Capability Licensing Service
Protect Audio Video Path

Cryptography Support: Disabled
Last ME reset reason: Power up
BIOS and GbE Config Lock: Unknown
BIOS boot State: Post Boot
FWU Override Counter: Always
FWU Override Qualifier: Always
Local FWUpdate: Enabled
OEM Id: 00000000-0000-0000-0000-000000000000
FW behavior on Flash Descriptor Override Pin-Strap: Halt

Intel(R) MEManuf Version: 6.0.30.1202
Copyright(C) 2005 - 2009, Intel Corporation. All rights reserved.

Platform stepping value is 6

FW Status Register: 0x00000245
FW Status Register1: 0x60000000

CurrentState: Normal
ManufacturingMode: Disabled
FlashPartition: Valid
OperationalState: M0 with UMA
InitComplete: Complete
BUPLoadState: Success
ErrorCode: No Error
ModeOfOperation: Normal
Phase: HOSTCOMM Module

Get FWU info command…done

Get FWU version command…done

Get FWU feature state command…done

Get ME FWU feature capability command…done

Get ME FWU platform type command…done
Feature enablement is 0x1C60
gFeatureAvailability value is 0x0
vsccommn.bin was created on 00:29:16 07/16/2009 GMT
SPI Flash ID #1 ME VSCC value is 0x2005
SPI Flash ID #1 (ID: 0xEF4016) ME VSCC value checked
SPI Flash ID #1 BIOS VSCC value is 0x2001
SPI Flash ID #1 (ID: 0xEF4016) BIOS VSCC value checked
FPBA value is 0x0

FRAP register value is 0x00000A0B
Flash Master1 (Host/BIOS) value is 0x0A0B0000
Flash Master2 (ME) value is 0x0C0D0000
Flash Master3 (Gbe) value is 0x08080118
RCBA Base Address read as [0xFED1C000] expecting 0xFED1C000
Data read from RCBA offset for SPIBA: 0xFED1F800
Data read from offset [0x00000038]: 0x00000000
Data read from offset [0x00000028]: 0x00017144
Data read from offset [0x3440]: 0xDEADDEED

Request Intel(R) ME kernel test command…done

Request Intel(R) ME kernel test result command…done
ME kernel test run was successful

MEManuf Test Passed

plutomaniac · January 18, 2015, 1:07pm

The ME firmware has a 1.5MB & 5MB SKU for all versions, v6.0.31 is not 5MB exclusive so that’s not it.

The error that you are getting at FPT has to do with fparts.txt file, basically it does not include your SPI chip’s specifications. MEManuf helped me identify what was missing and I made a new FPT package for you to download which should work with your system from now on. Download it (preferably use the DOS version as it’s newer that the Windows one) and run:

FPT -verbose -I
FPT -D BIOS.bin

Your chip is either W25Q32BV or W25Q32FVSSIQ or S25FL032K. All of them are 32Mbit according to spec so 4MB SPI flash size and thus you have a 1.5MB firmware at your machine. FPT will verify.

EDIT: Reuploaded file to add S25FL032K chip as well. Still 32Mbit all three of them.

Flash Programming Tool.rar (241 KB)

plutomaniac · January 19, 2015, 1:33am

NEW! Intel ME6 Firmware 5MB v6.2.50.1062 DT (for Desktop Intel 5-series)

* Updated at ME System Tools v5.x: FW Bringup Guide from v0.49 (ME5.0 , 09/2008) → v0.3 (ME5.1 , 11/2008)

grml4d · January 19, 2015, 2:37am

that is weird both version have same number, mostly because from what i have seen with drivers , bad size leads to non working tool…
beside that your tool worked better but made a new error with both commands

Intel (R) Flash Programming Tool. Version: 6.1.20.1057
Copyright (c) 2007-2010, Intel Corporation. All rights reserved.

Number of LPC Devices supported: 61
LPC Device Id: 3B0B.
Platform: Intel(R) HM57 Express Chipset Revision: B3

Error 363: Invalid Chip Erase Timeout value in “fparts.txt”.

plutomaniac · January 19, 2015, 1:10pm

Try this one, I think it will work now. Reminder on what to run:

FPT -verbose -I
FPT -D BIOS.bin

Also, run MEManuf -verbose and post the results here please.

Flash Programming Tool.rar (240 KB)

iceman · January 19, 2015, 2:48pm

Why is there no instructions 5 Series platform for me firmware? Although very old

plutomaniac · January 20, 2015, 3:51pm

@lordkag

An interesting finding. At Intel BIOS files (.bio) there are always two ME Regions of the same version and SKU. The first is the normal production one and the second is always smaller in size (less FF) and slightly different.

For example, a TXE Intel .bio I tested has two TXE Regions that are different because the second one reports all errors (not only the critical) and has NFC disabled. At another firmware, ME 8.1.20.1336, the differences between the two images seem to be similar to what I saw at TXE.

While extracting the firmware, the second image can be easily identified because a) of the smaller size and b) at the $FPT ("krid") header the actual ME/TXE version is shown exactly like before the $MN2 regions (that’s not the case for the full-sized Production firmware).

It seems to me that the second image a "debug" version of sorts and no it’s not a PreProduction image. I don’t know why it’s included every time though at Intel .bio files. Why do you think they do that? If interested, there’s an attachment.

I would like to retract that statement as it’s wrong. I checked FITC and it’s Wizard. Indeed a ME image can be adjusted to work on many different models with some differences at clocks etc. That’s what the Profiles are for under ICC settings at FITC.

ME_INTEL-BIO_Debug.rar (6.47 MB)

grml4d · January 21, 2015, 1:47pm

i am ready to check but is it useful for a later update of firmware ?
Pegatron has not yet answered …[ i am happy to be a samsung user ;’] ] or helped …
they do the 5 minutes warranty on their products : only the time to buy and leave the shop with the product… if you come back , shop owner acts like it is first time you get in…
some call it the fish memory of 5s… [5s memory : strange idea because fishes are always hiding or not with same predators]