Zitat von blogger im Beitrag #2018

---

What's mean LP on the end of ME version ? I hadn't it before upgrade.

---

@ PhatAgent:

What exact model do you have? I'd like to find it's UEFI update in this Apple link. Apple doesn't lock the flash descriptor so you should have read/write access to the ME region. To verify that, run Flash Programming Tool with the command fptw -dumplock and you should see 00 00 FF FF at both CPU and ME. If yes, attach a dump of the current SPI image to see for a fact what's inside, do this with the command fptw -d spi.bin and attach the resulting spi.bin file compressed here. Also, run MEInfo -verbose and MEManuf -verbose and show me some pictures of the output to see what errors you mean exactly. Apple ME firmware is a relatively uncharted category so that's why I'm asking for more info from you.

@ FormatC:

Yes, it makes sense for the problem to be BIOS related. The ME co-processor requires the BIOS to inform it when the POST has completed by sending an EoP (End of Post) message. If that is not send for some reason, the ME does not fully initialize which in turn does not allow proper communication and causes errors at the tools. If they send you a new BIOS or something then you can share it here with us which might help others in the future. The fpt -greset command doesn't reset BIOS settings but it's more general. It resets the ME basically, some more info about it's actions can be found at the System Tools User Guide provided within the latest ME 11.0 System Tools package as found at the first post of mine.

@ PhatAgent:

At Device Manager > System Devices > Intel(R) Management Engine Interface, what drivers do you have installed (assuming that you have such a device which you should)?

For ME7, it's better to use the x86 tools based on experience. Have you tried the ME8 MEInfo tool to see if it shows something more without crashing? Some errors are normal when you use MEInfo v8. If that fails as well and you do have a valid MEI driver installed, you should boot into DOS and try the DOS versions of MEInfo and MEManuf as these don't rely on any drivers and should work if the problem is for some reason indeed there.

Both 7.0.0.1193 and 7.0.1.1205 ME firmware have the same (Apple) SKU so they should be compatible. If the problem is the Windows versions, maybe the DOS one will work. First though, let's see what the DOS versions of MEInfo and MEManuf v7 report.

@ FM:

It may be the outdated MEBx but I cannot be certain without documentation from Intel. I agree with you, if these systems are used actively for work then it would be best to leave them at 5.2.10 as I doubt Fujitsu is ever going to release something newer for that older platform. For that one system, I suppose you would need a programmer to get the actual SPI image as Futsjitsu provides that compressed in a proprietary way image which doesn't extract properly with that one tool I found. That is of course if you want to experiment only with one system and see where it leads you.

@ PhatAgent:

The MEInfo v7 crash is probably system related as it's fine on my HM65 (ME7) system under Windows 10 x64. Unfortunately ME7 did not have EFI tools so if you can boot from an MBR device with DOS you could try the DOS versions of MEInfo v7 and FWUpdate v7.

Honestly, since your descriptor is unlocked, you can update the ME firmware manually without the need of FWUpdate. I searched the UEFI images provided by Apple and only four of them are ME7 based. These are:

IM121_0047_21B --> 7.0.0.1193
MBA41_0077_B12 --> 7.0.1.1205
MBP81_0047_2AB --> 7.0.0.1193
MM51_0077_B12 --> 7.0.1.1205

The last one, MM51_0077_B12, has the updated firmware and it's settings are almost identical to your own model's, MBP81_0047_2AB. Only two things are different which I adjusted with Flash Image Tool and rebuilt a 7.0.1.1205 version with the settings from MBP81_0047_2AB. The only thing that concerns me a little bit is the fact that the MM51 7.0.1.1205 is Extracted and thus may have some leftovers from MM51. Since the settings are adjusted to be identical to MBP81 you should be ok by just replacing that ME region with the one I created. The reason I mentioned this is because I cannot guarantee that everything will work properly, Apple tends to be weird. Judging from past experience, it should work just fine but you never know. My point is, if you have a way to reflash the spi image in case of a problem then go for it, otherwise you might have to consider the risk, no matter how small it is. I have the ME region ready and I'll provide instructions but only if a) you can't make FWUpdate to work and b) you are aware of the small risk of reflashing the entire ME region from MM51 with the settings adjusted for MBP81.

Personally, I believe that if you can make FWUpdate work then you would have nothing to worry about. Maybe the errors you see are related to the crashing of MEInfo v7, something else is causing issues. You don't have anything running in the background right? Something like a Hardware Info utility or similar? These can interfere.