Forum - RE: Cannot access Intel ME on hm77 chipset

Win-Raid Forum (Drivers - Firmware - Modding) � Special Topics � Intel Management Engine � Cannot access Intel ME on hm77 laptop chipset

Page 2 of 3 � Page 1 2 3 Page �

Topic settings

Print view

Jump to forum

General & Forum related Topics News / Announcements Forum-related Questions & Suggestions Off Topic Important Drivers (AHCI/RAID, NVMe, USB etc.) General: Storage Drivers (AHCI/RAID, NVMe and USB) Specific: Intel AHCI/RAID Drivers Specific: NVIDIA nForce Chipset Drivers (incl. AHCI/RAID) Specific: NVMe Drivers Other Drivers System Performance RAID Performance AHCI/NVMe Performance Solid State Drives BIOS Modding BIOS Modding Guides and Problems BIOS modules (PCI ROM, EFI and others) BIOS Modding Requests Reports: BIOS Modding Results Offers: Already modded special BIOSes Special Topics Intel Management Engine CPU Microcodes NVMe Support for old Systems Other Tools (not BIOS modding related) Interesting PC Hardware & Software OS related Topics Windows 11 Windows 8-10/Server 2012-2019 Windows 7/Vista/Server 2008 Windows XP/2000/Server 2003 DOS/Windows 3.X/9X/ME - Retro Gaming Other Operating Systems

#16 | RE: Cannot access Intel ME on hm77 chipset datum

Tue Jun 02, 2020 2:18 pm

Lenovo_ThinkPad_Edge_E330_Clean.bin --> Full 12MB (0xC00000) SPI image for "FPT -f" use
Lenovo_ThinkPad_Edge_E330_Clean_ME.bin --> ME Region only (0x7FF000 < 0x800000 = 8MB) for "FPT -me -f" use

The 12MB SPI image consists of 2 Flash Components: 8MB = 0x800000 (FD + ME) and 4MB = 0x400000 (EC + BIOS). You need to split them for SPI Programmer use.

reply

#17 | RE: Cannot access Intel ME on hm77 chipset datum

Tue Jun 02, 2020 2:20 pm (Last edited: Tue Jun 02, 2020 2:22 pm)

I rould really like to try the pin method and flash with FPT (I found a GPIO33 pin in schematic pdf that is for Flash Descriptor unlock; but I will get back to that)

Wouldn't it sufice to change the command sets in fparts.txt for the two chips to coincide, and make the command sets compatible?
If it's not complatible you can't flash the whole .bin to those chips with FPT?

W25Q32BV, 0xEF4016, 0x2000000, 0x1000, 0x20, 64, 0, 0xc7, 80000
MX25L6405D, 0xC22017, 0x4000000, 0x1000, 0x20, 64, 0, 0x60, 80000

>fptw64.exe -i
Intel (R) Flash Programming Tool. Version: 8.1.60.1561
Copyright (c) 2007 - 2014, Intel Corporation. All rights reserved. Platform: Intel(R) HM77 Express Chipset
Reading HSFSTS register... Flash Descriptor: Valid

--- Flash Devices Found ---
MX25L6405D ID:0xC22017 Size: 8192KB (65536Kb)
W25Q32BV ID:0xEF4016 Size: 4096KB (32768Kb)

--- Flash Image Information --
Signature: VALID
Number of Flash Components: 2
Component 1 - 8192KB (65536Kb)
Component 2 - 4096KB (32768Kb)
Regions:
Descriptor - Base: 0x000000, Limit: 0x000FFF
BIOS - Base: 0x800000, Limit: 0xBFFFFF
ME - Base: 0x001000, Limit: 0x7FFFFF
GbE - Not present
PDR - Not present
Master Region Access:
CPU/BIOS - ID: 0x0000, Read: 0x0B, Write: 0x0A
ME - ID: 0x0000, Read: 0x0D, Write: 0x0C
GbE - ID: 0x0118, Read: 0x08, Write: 0x08
Total Accessable SPI Memory: 12288KB,
Total Installed SPI Memory : 12288KB

reply

#18 | RE: Cannot access Intel ME on hm77 chipset datum

Tue Jun 02, 2020 2:25 pm (Last edited: Tue Jun 02, 2020 2:26 pm)

Change W25Q32BV from 0xC7 to 0x60 for FPT use, both are the same:

reply

#19 | RE: Cannot access Intel ME on hm77 chipset datum

Tue Jun 02, 2020 2:28 pm (Last edited: Tue Jun 02, 2020 2:34 pm)

Zitat von plutomaniac im Beitrag #18
Change W25Q32BV from 0xC7 to 0x60 for FPT use, both are the same:

So, after I change the command set and hopefully unlock the descriptor with pin method (gpio33 to gnd; as I said will get back to this with some info request; but this is the way the schematic pdf sais it unlocks)

then use FPT -f "full 12mb .bin" and it should work?

reply

#20 | RE: Cannot access Intel ME on hm77 chipset datum

Tue Jun 02, 2020 2:50 pm

If the 12MB file plutomaniac created for you isn't based on your own bios- backup, you could lose som information that was specific for your notebook (possibly serial, network address...) when overwriting the bios region.

reply

#21 | RE: Cannot access Intel ME on hm77 chipset datum

Tue Jun 02, 2020 3:08 pm (Last edited: Tue Jun 02, 2020 3:08 pm)

Zitat von lfb6 im Beitrag #20
If the 12MB file plutomaniac created for you isn't based on your own bios- backup, you could lose som information that was specific for your notebook (possibly serial, network address...) when overwriting the bios region.

I will make a backup first.

Then I could try and transfer those (serial etc) parts into the image plutomaniac gave me with UEFITool I guess
Didn't use this tool untill now so I don't know much about it.
I don't know if there are CRC problems to take care of, and if yes, can it be done with UEFITool (does it do it automaticaly etc)?

reply

#22 | RE: Cannot access Intel ME on hm77 chipset datum

Tue Jun 02, 2020 3:25 pm

Zitat von plutomaniac im Beitrag #10
.....Download the attachment and use Flash Programming Tool via "fptw -me -f Lenovo_ThinkPad_Edge_E330_Clean_ME.bin" followed by "fptw -greset". A hard reboot will occur and afterwards, you should have a working ME firmware. Check with "MEInfo -fwsts" again......

Why don't you flash the ME first as recommended by plutomaniac? Maybe your ME is working properly afterwards.
And I'm sorry, I can't help you with transfer of board sepcific information.

reply

#23 | RE: Cannot access Intel ME on hm77 chipset datum

Tue Jun 02, 2020 3:47 pm

Zitat von corexlim im Beitrag #19
then use FPT -f "full 12mb .bin" and it should work?

Instructions are provided here to re-flash the ME region only. For "FPT -f" usage, dump your own SPI image first, replace the BIOS region at the 12MB image with your own via UEFITool and flash. For programmer usage, take the first 8MB (0x800000) from the provided 12MB SPI image and flash only the 1st 8MB SPI chip (FD + ME).

reply

#24 | RE: Cannot access Intel ME on hm77 chipset datum

Tue Jun 02, 2020 7:56 pm

I will try that first for sure.
I was just seeking to understand other options and what is their purpose etc.

reply

#25 | RE: Cannot access Intel ME on hm77 chipset datum

Thu Jun 04, 2020 4:33 pm

So , I am trying to follow [Guide] Unlock Intel Flash Descriptor Read/Write Access Permissions for SPI Servicing and use pin method to unlock flash descriptor.

The problem is there is HDA_SDO(UT) and also HDA_DOCK_EN#/GPIO33 on this Lenovo e330 motherboard, as you can see on the attached pictures.

From boardview HDA_SDO (from PCH) is linked to ME_UNLOCK that goes to EC chip.

HDA_DOCK_EN#/GPIO33 goes to PCH and at page 3 (in schmatics) PCH Strapping Table there is the explaination for Flash Descriptor unlock.
I don't understand then what is the role of ME_UNLOCK and HDA_SDO then.

What should I do?
I think I would go for GPIO33 to Gnd link and not setting ME_UNLOCK to high (3.3v)
How much time the link to GND (jumper) should be on? Only as I start the laptop from S5 mode or should I live it (jumper, link) all the time?

Any other understanding (way to do it) from what I have posted in here before I start this process (just to be sure) would be appreciated.

Thanks.

reply

#26 | RE: Cannot access Intel ME on hm77 chipset datum

Thu Jun 04, 2020 5:06 pm

As far as I know, at CPT+ PCH (ME >= 7), the FD is unlocked via the HDA_SDO pin. GPIO33 was used on older platforms (ICH and 1st PCH with ME 6). It could be that the PCH Strapping Table info at the schematic was not updated to reflect that by accident. Personally I would go with HDA_SDO which triggers ME_UNLOCK. You need to short the pins only at the beginning, until the BIOS POSTs is a good rule of thumb.

reply

#27 | RE: Cannot access Intel ME on hm77 chipset datum

Thu Jul 02, 2020 2:55 pm (Last edited: Thu Jul 02, 2020 3:00 pm)

Hello,
I finally (after a long hiatus; had some problems and been busy) did the strap (ME_UNLOCK to 3.3v) for unlocking the flash descriptor (for the lenovo e330 with intel hm77 chipset) and it works now. I could read the whole flash region (with fptw64.exe -d full.spi)

But before I continue and write the ME region please explain why

MEInfoWin64.exe -fwsts

displays

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

FW Status Register1: 0x1E040195
FW Status Register2: 0x1652010E

CurrentState: Normal
ManufacturingMode: Enabled
FlashPartition: Valid
OperationalState: Bring Up
InitComplete: Initializing
BUPLoadState: Success
ErrorCode: No Error
ModeOfOperation: Unsecured mode by H/W jumper
ICC: Valid OEM data, ICC programmed
PhaseStatus: UNKNOWN

as if the ME is ok now , and I could enter it with CTRL-P if I wished.
But trying to do that does not work though. (at bootup I interrupt the process and the menu with that options comes up, as I can reset (not shutdown) the laptop and ME_UNLOCK strap survives)

Then, after shutdown the MEInfo is the same (as if ME is in a corrupted state), as I mentioned at the begging of this thread

MEInfoWin64.exe -fwsts
Intel(R) MEInfo Version: 8.1.56.1541
Copyright(C) 2005 - 2014, Intel Corporation. All rights reserved.

FW Status Register1: 0x00304181
FW Status Register2: 0x153B0100

CurrentState: Init
ManufacturingMode: Disabled
FlashPartition: Valid
OperationalState: Bring Up
InitComplete: Initializing
BUPLoadState: Success
ErrorCode: Debug Error
ModeOfOperation: Normal
ICC: No valid OEM data, ICC not programmed
PhaseStatus: UNKNOWN

reply

#28 | RE: Cannot access Intel ME on hm77 chipset datum

Thu Jul 02, 2020 3:22 pm

Zitat von corexlim im Beitrag #27
as if the ME is ok now , and I could enter it with CTRL-P if I wished.

It is not. As you can see, the Mode of Operation is "Unsecured mode by H/W jumper". Basically the ME is in Recovery Mode, for repairs. You can now follow the instructions that were given before.

reply

#29 | RE: Cannot access Intel ME on hm77 chipset datum

Thu Jul 02, 2020 3:41 pm

Zitat von plutomaniac im Beitrag #28
Zitat von corexlim im Beitrag #27
as if the ME is ok now , and I could enter it with CTRL-P if I wished.

It is not. As you can see, the Mode of Operation is "Unsecured mode by H/W jumper". Basically the ME is in Recovery Mode, for repairs. You can now follow the instructions that were given before.

OK I understand. Thanks for clarification.

I will do that, and get back with results

reply

#30 | RE: Cannot access Intel ME on hm77 chipset datum

Thu Jul 02, 2020 4:17 pm (Last edited: Thu Jul 02, 2020 4:29 pm)

I flashed the ME part with fptw64.exe -me -f Lenovo_ThinkPad_Edge_E330_Clean_ME.bin.
I can access Intel ME with CTRL-P finally.

I still don't have any devices in windows device mananger, suitable to install Intel ME SB.

Is it because I forgot
fptw -greset after flashing it?

MEInfoWin64.exe -verbose

Sorry. Disregard this. Intel Management Engine Interface appeared as disabled in System Devices; did not observed it; had to enable it.

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

FW Status Register1: 0x1E000245
FW Status Register2: 0x69000106

CurrentState: Normal
ManufacturingMode: Disabled
FlashPartition: Valid
OperationalState: M0 with UMA
InitComplete: Complete
BUPLoadState: Success
ErrorCode: No Error
ModeOfOperation: Normal
ICC: Valid OEM data, ICC programmed

Windows OS Version : 6.2.9200 ""
OS BIOS Support : UEFI

Table Type 134 ( 0x 86 ) found, size of 16 (0x 10 ) bytes
Table Type 4 ( 0x 04 ) found, size of 42 (0x 2A ) bytes
Table Type 7 ( 0x 07 ) found, size of 19 (0x 13 ) bytes
Table Type 7 ( 0x 07 ) found, size of 19 (0x 13 ) bytes
Table Type 7 ( 0x 07 ) found, size of 19 (0x 13 ) bytes
Table Type 7 ( 0x 07 ) found, size of 19 (0x 13 ) bytes
Table Type 129 ( 0x 81 ) found, size of 8 (0x 08 ) bytes
Table Type 16 ( 0x 10 ) found, size of 23 (0x 17 ) bytes
Table Type 17 ( 0x 11 ) found, size of 34 (0x 22 ) bytes
Table Type 17 ( 0x 11 ) found, size of 34 (0x 22 ) bytes
Table Type 19 ( 0x 13 ) found, size of 31 (0x 1F ) bytes
Table Type 134 ( 0x 86 ) found, size of 13 (0x 0D ) bytes
Table Type 0 ( 0x 00 ) found, size of 24 (0x 18 ) bytes

Windows OS Version : 6.2.9200 ""
OS BIOS Support : UEFI

Table Type 134 ( 0x 86 ) found, size of 16 (0x 10 ) bytes
Table Type 4 ( 0x 04 ) found, size of 42 (0x 2A ) bytes
Table Type 7 ( 0x 07 ) found, size of 19 (0x 13 ) bytes
Table Type 7 ( 0x 07 ) found, size of 19 (0x 13 ) bytes
Table Type 7 ( 0x 07 ) found, size of 19 (0x 13 ) bytes
Table Type 7 ( 0x 07 ) found, size of 19 (0x 13 ) bytes
Table Type 129 ( 0x 81 ) found, size of 8 (0x 08 ) bytes
Table Type 16 ( 0x 10 ) found, size of 23 (0x 17 ) bytes
Table Type 17 ( 0x 11 ) found, size of 34 (0x 22 ) bytes
Table Type 17 ( 0x 11 ) found, size of 34 (0x 22 ) bytes
Table Type 19 ( 0x 13 ) found, size of 31 (0x 1F ) bytes
Table Type 134 ( 0x 86 ) found, size of 13 (0x 0D ) bytes
Table Type 0 ( 0x 00 ) found, size of 24 (0x 18 ) bytes
Table Type 1 ( 0x 01 ) found, size of 27 (0x 1B ) bytes
Table Type 2 ( 0x 02 ) found, size of 15 (0x 0F ) bytes
Table Type 3 ( 0x 03 ) found, size of 22 (0x 16 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 126 ( 0x 7E ) found, size of 9 (0x 09 ) bytes
Table Type 126 ( 0x 7E ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 126 ( 0x 7E ) found, size of 9 (0x 09 ) bytes
Table Type 126 ( 0x 7E ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 126 ( 0x 7E ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 126 ( 0x 7E ) found, size of 9 (0x 09 ) bytes
Table Type 126 ( 0x 7E ) found, size of 9 (0x 09 ) bytes
Table Type 126 ( 0x 7E ) found, size of 9 (0x 09 ) bytes
Table Type 126 ( 0x 7E ) found, size of 9 (0x 09 ) bytes
Table Type 126 ( 0x 7E ) found, size of 9 (0x 09 ) bytes
Table Type 126 ( 0x 7E ) found, size of 9 (0x 09 ) bytes
Table Type 126 ( 0x 7E ) found, size of 9 (0x 09 ) bytes
Table Type 126 ( 0x 7E ) found, size of 9 (0x 09 ) bytes
Table Type 126 ( 0x 7E ) found, size of 9 (0x 09 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 126 ( 0x 7E ) found, size of 17 (0x 11 ) bytes
Table Type 10 ( 0x 0A ) found, size of 6 (0x 06 ) bytes
Table Type 12 ( 0x 0C ) found, size of 5 (0x 05 ) bytes
Table Type 13 ( 0x 0D ) found, size of 22 (0x 16 ) bytes
Table Type 22 ( 0x 16 ) found, size of 26 (0x 1A ) bytes
Table Type 22 ( 0x 16 ) found, size of 26 (0x 1A ) bytes
Table Type 18 ( 0x 12 ) found, size of 23 (0x 17 ) bytes
Table Type 21 ( 0x 15 ) found, size of 7 (0x 07 ) bytes
Table Type 21 ( 0x 15 ) found, size of 7 (0x 07 ) bytes
Table Type 131 ( 0x 83 ) found, size of 22 (0x 16 ) bytes
Table Type 136 ( 0x 88 ) found, size of 6 (0x 06 ) bytes
Table Type 130 ( 0x 82 ) found, size of 20 (0x 14 ) bytes
Table Type 131 ( 0x 83 ) found, size of 64 (0x 40 ) bytes
MEBx Version found is 8.0.0.0065

Error 9458: Communication error between application and Intel(R) ME module (FW Update client)

Error 9459: Internal error (Could not determine FW features information)

reply

Intel ME driver failed to perform handshake with the Firmware (FWSTS0: 0x00304181, FWSTS1: 0x153B0100) � � EliteDesk G2 Mini 35 Watt ME Disable Jumper Location!

Page 2 of 3 � Page 1 2 3 Page �

Please enter a reason for warning.