Forum - RE: Intel Management Engine: Drivers, Firmware & System Tools

Win-Raid Forum (Drivers - Firmware - Modding) � Special Topics � Intel Management Engine � Intel (Converged Security) Management Engine: Drivers, Firmware and Tools

Page 162 of 380 � Page 1 ... 157 158 159 160 161 162 163 164 165 166 ... 380 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

#2416 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Wed Sep 07, 2016 7:39 pm (Last edited: Wed Sep 07, 2016 7:40 pm)

Zitat von plutomaniac im Beitrag #2420
@Wootever

Ah, great. As I thought, 11.5 is for 100/200-series whereas 11.6 is only for 200-series. I haven't found documentation which proves that yet but from the GbE included with 11.5 SPI images I've found (always the SKL one, whereas KBL for 11.6) and your test, it's fairly obvious.

What method did you use to upgrade, FWUpdate v11.0 or FIT+FPT v11.0? If you used the latter, did you encounter any errors or similar? I remember that 11.0 FIT shows some ICC errors when loading newer branches (11.5 and 11.6). The warnings you see at MEManuf are probably due to the fact that it's not KBL compatible. We certainly need a 11.5 or 11.6 system tools kit to show up at some point.

I used the latest FWUpdate to upgrade my Skylake to 11.5.1 FW ver. works fine.

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

Intel(R) ME code versions:

BIOS Version D3CN32WW
MEBx Version 11.0.0.0005
GbE Region does not exist.
GbE Version Unknown
Vendor ID 8086
PCH Version 21
FW Version 11.5.1.1006 LP
LMS Version 11.5.0.1020
MEI Driver Version 11.6.0.1009
Wireless Hardware Version Not Available
Wireless Driver Version Not Available

FW Capabilities 0x31111240

Intel(R) Capability Licensing Service - PRESENT/ENABLED
Protect Audio Video Path - PRESENT/ENABLED
Intel(R) Dynamic Application Loader - PRESENT/ENABLED
Intel(R) Platform Trust Technology - PRESENT/ENABLED

TLS Disabled
Last ME reset reason Global system reset
Local FWUpdate Enabled
BIOS Config Lock Enabled
GbE Config Lock Enabled
Host Read Access to ME Disabled
Host Write Access to ME Disabled
Host Read Access to EC Disabled
Host Write Access to EC Disabled
SPI Flash ID 1 EF4018
SPI Flash ID 2 Unknown
BIOS boot State Post Boot
OEM ID 00000000-0000-0000-0000-000000000000
Capability Licensing Service Enabled
OEM Tag 0x00000000
Slot 1 Board Manufacturer 0x00000000
Slot 2 System Assembler 0x00000000
Slot 3 Reserved 0x00000000
M3 Autotest Disabled
C-link Status Disabled
Independent Firmware Recovery Disabled
EPID Group ID 0xF85
OEM Public Key Hash FPF 0000000000000000000000000000000000000000000000000000000000000000
OEM Public Key Hash ME 0000000000000000000000000000000000000000000000000000000000000000
ACM SVN FPF 0x0
KM SVN FPF 0x0
BSMM SVN FPF 0x0
GuC Encryption Key FPF 0000000000000000000000000000000000000000000000000000000000000000
GuC Encryption Key ME 0000000000000000000000000000000000000000000000000000000000000000

FPF ME
--- --
Force Boot Guard ACM Disabled Disabled
Protect BIOS Environment Disabled Disabled
CPU Debugging Enabled Enabled
BSP Initialization Enabled Enabled
Measured Boot Disabled Disabled
Verified Boot Disabled Disabled
Key Manifest ID 0x0 0x0
Enforcement Policy 0x0 0x0
PTT Enabled Enabled
PTT Lockout Override Counter 0x0
EK Revoke State Not Revoked
PTT RTC Clear Detection FPF 0x0

reply

#2417 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Wed Sep 07, 2016 8:06 pm

Zitat von plutomaniac im Beitrag #2420
What method did you use to upgrade, FWUpdate v11.0 or FIT+FPT v11.0? If you used the latter, did you encounter any errors or similar?

I used FWUpdate 11.0, might it be helpful to post the results from FIT+FPT as well?

reply

#2418 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Wed Sep 07, 2016 8:22 pm (Last edited: Wed Sep 07, 2016 8:28 pm)

@ Octopuss:

The 6.0 tools don't have FWUpdate and you said you used another tool. That tool is certainly Flash Programming Tool (FPT) which is not a replacement of FWUpdate. FPT replaces the whole ME region and not just the parts that need updating like FWUpdate does. It also doesn't care about platform settings stored at the ME. Before ME8, FWUpdate required only UPD images and not full regions (RGN or EXTR) so if you flashed an UPD image with FPT then the ME is bricked. You said that you flashed 6.2.50.1062 1.5MB firmware with FPT. I checked what ME your system uses and it's actually 5MB Mobile (MB) and not 1.5MB.

So now you have flashed the wrong firmware SKU (1.5MB) and type (UPD with FPT instead of FWUpdate, FPT works with EXTR or RGN only after merging settings with Flash Image Tool - FITC) with no platform settings (FPT doesn't keep those unless the firmware is setup by FITC). I'm surprised the system still boots, that was possible back at 5-series but not 6-series or later. So you are lucky. Now, to restore (I think we can because Gigabyte tends to not lock the Flash Descriptor). From the 6.x tools, run FPT with command fptw -d spi.bin and attach the resulting file.

@ kostar20071 & Wootever:

Thank you very much for your tests and determination to be the first to do such an upgrade. Indeed it seems to work just fine, when we have 11.5 or 11.6 tools we should verify that those don't report any warnings or errors as well.

Can you guys tell me what DEV_ID is shown at Device Manager > Intel(R) Management Engine Interface now (SKL + 11.5 firmware)?

@ Wootever:

Well if you want to test FIT+FPT/Programmer then sure but it probably won't work properly. It would be more interesting to see whether 11.6 works as well (primarily with FWUpdate and if you want FIT+FPT/Programmer - however, the 11.6 we have is only EXTR so it might not be the best case to test). If I'm right and 11.6 is 200-series only then it won't work. But since you can easily recover from bricks, you can try if you have the time and courage. If you try 11.6 with FWUpdate, note that the CON LP we have is EXTR so you might need to replace the ISHC region at the $FPT header with 0x20 FF again like we did back when you helped with the PDM/NOPDM testing.

reply

#2419 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Wed Sep 07, 2016 8:29 pm (Last edited: Wed Sep 07, 2016 8:50 pm)

Zitat von plutomaniac im Beitrag #2424
Can you guys tell me what DEV_ID is shown at Device Manager > Intel(R) Management Engine Interface now (SKL + 11.5 firmware)?

Mobile 6th (100-Series) Generation Intel(R) Processor Intel Core i7-6500U . (I also noticed that all chipset drivers (Intel Chipset) inf s are inside SunrisePoint-LP directory)

Consumer LP
Driver ver: ME 11.5.0.1011
PCI\VEN_8086&DEV_9D3A&SUBSYS_382817AA&REV_21

reply

#2420 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Wed Sep 07, 2016 8:37 pm (Last edited: Wed Sep 07, 2016 8:38 pm)

Very nice, thank you kostar20071. So it seems that Intel's comments at the 11.5 and 11.6 drivers are correct. I assume that they have forgotten to add "KBL/SPT-H" next to A13A and that's why only 9D3A is written. It does show though that these DEV_IDs are for 11.0 Skylake + SunrisePoint (100-series) or 11.5 KabyLake + SunrisePoint (100-series).

reply

#2421 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Wed Sep 07, 2016 8:59 pm (Last edited: Wed Sep 07, 2016 9:13 pm)

Wootever

Show info

Posts:	51
Registered since:	06.03.2015

Alright, tried 11.6 with FWUpdate and got the following error:

1
 
Error 8804: FW update/downgrade is not allowed to the supplied FW image.

FIT shows:

1
 
Integrated Clock Controller Settings not supported by provided ME image.

Both is working fine with version 11.5.

Edit:
FIT + FPTW 11.5.1.1006 Consumer LP

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
 
Intel(R) MEManuf Version: 11.0.0.1205
Copyright(C) 2005 - 2016, Intel Corporation. All rights reserved.
 
FW Status Register1: 0x94000255
FW Status Register2: 0x020B0506
FW Status Register3: 0x00000020
FW Status Register4: 0x00084000
FW Status Register5: 0x00000000
FW Status Register6: 0x00000000
 
  CurrentState:                         Normal
  ManufacturingMode:                    Enabled
  FlashPartition:                       Valid
  OperationalState:                     CM0 with UMA
  InitComplete:                         Complete
  BUPLoadState:                         Success
  ErrorCode:                            No Error
  ModeOfOperation:                      Normal
  SPI Flash Log:                        Not Present
  Phase:                                ROM/Preboot
  ICC:                                  Valid OEM data, ICC programmed
  ME File System Corrupted:             No
  PhaseStatus:                          CALL_NEXT_MODULE
 
  FPF and ME Config Status:             Not committed
 
FW Capabilities value is 0x31111240
Feature enablement is 0x31111240
Platform type is 0x41110321
No Intel vPro Wireless device was found
Feature enablement is 0x31111240
ME initialization state valid
ME operation mode valid
Current operation state valid
ME error state valid
OEM ICC data valid and programmed correctly
MFS is not corrupted
PCH SKU Emulation is correct
 
Request Intel(R) ME BIST status command... done
 
Get Intel(R) ME test data command... done
 
Get Intel(R) ME test data command... done
 
Warning 463: A test returned from FW does not match known test by the tool: App(12) Comp(0) Test(0)
Error 463: A test returned from FW does not match known test by the tool: App(%d) Comp(%d) Test(%d) 
 
Warning 463: A test returned from FW does not match known test by the tool: App(12) Comp(0) Test(1)
Error 463: A test returned from FW does not match known test by the tool: App(%d) Comp(%d) Test(%d) 
 
Warning 463: A test returned from FW does not match known test by the tool: App(12) Comp(0) Test(2)
Error 463: A test returned from FW does not match known test by the tool: App(%d) Comp(%d) Test(%d) 
Total of 11 Intel(R) ME test result retrieved
 

Policy Kernel - Boot Guard : Self Test - Passed
Policy Kernel - Embedded Controller : Power source type - Passed
MCA - MCA Tests : Blob - Passed
MCA - MCA Tests : MCA Manuf - Passed
SMBus - SMBus : Read byte - Passed
VDM - General : VDM engine - Passed
Unknown App(12) - Unknown Comp(0) : Unknown Test(2) - Passed
Unknown App(12) - Unknown Comp(0) : Unknown Test(1) - Passed
Unknown App(12) - Unknown Comp(0) : Unknown Test(0) - Passed
Policy Kernel - ME Configuration : M3 Power Rails Available - Passed
Policy Kernel - ME Configuration : PROC_MISSING - Passed
 
Clear Intel(R) ME test data command... done
 
MEManuf Operation Passed (with warnings)
 

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
 
Intel(R) MEInfo Version: 11.0.15.1003
Copyright(C) 2005 - 2016, Intel Corporation. All rights reserved.
 
FW Status Register1: 0x94000255
FW Status Register2: 0x020B0506
FW Status Register3: 0x00000020
FW Status Register4: 0x00084000
FW Status Register5: 0x00000000
FW Status Register6: 0x00000000
 
  CurrentState:                         Normal
  ManufacturingMode:                    Enabled
  FlashPartition:                       Valid
  OperationalState:                     CM0 with UMA
  InitComplete:                         Complete
  BUPLoadState:                         Success
  ErrorCode:                            No Error
  ModeOfOperation:                      Normal
  SPI Flash Log:                        Not Present
  Phase:                                ROM/Preboot
  ICC:                                  Valid OEM data, ICC programmed
  ME File System Corrupted:             No
  PhaseStatus:                          CALL_NEXT_MODULE
 
  FPF and ME Config Status:             Not committed
FW Capabilities value is 0x31111240
Feature enablement is 0x31111240
Platform type is 0x41110321
No Intel vPro Wireless device was found
Intel(R) ME code versions:
                  
 
  Windows OS Version : 6.2.9200 ""
    Table Type   0 ( 0x 00 ) found, size of  24 (0x 18 ) bytes 
BIOS Version                                 1.0
 
  Windows OS Version : 6.2.9200 ""
    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   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   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   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   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   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   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes 
    Table Type   8 ( 0x 08 ) 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   9 ( 0x 09 ) found, size of  17 (0x 11 ) 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  10 ( 0x 0A ) found, size of   6 (0x 06 ) bytes 
    Table Type  11 ( 0x 0B ) found, size of   5 (0x 05 ) bytes 
    Table Type  12 ( 0x 0C ) found, size of   5 (0x 05 ) bytes 
    Table Type  32 ( 0x 20 ) found, size of  20 (0x 14 ) bytes 
    Table Type  34 ( 0x 22 ) found, size of  11 (0x 0B ) bytes 
    Table Type  26 ( 0x 1A ) found, size of  22 (0x 16 ) bytes 
    Table Type  36 ( 0x 24 ) found, size of  16 (0x 10 ) bytes 
    Table Type  35 ( 0x 23 ) found, size of  11 (0x 0B ) bytes 
    Table Type  28 ( 0x 1C ) found, size of  22 (0x 16 ) bytes 
    Table Type  36 ( 0x 24 ) found, size of  16 (0x 10 ) bytes 
    Table Type  35 ( 0x 23 ) found, size of  11 (0x 0B ) bytes 
    Table Type  27 ( 0x 1B ) found, size of  15 (0x 0F ) bytes 
    Table Type  36 ( 0x 24 ) found, size of  16 (0x 10 ) bytes 
    Table Type  35 ( 0x 23 ) found, size of  11 (0x 0B ) bytes 
    Table Type  27 ( 0x 1B ) found, size of  15 (0x 0F ) bytes 
    Table Type  36 ( 0x 24 ) found, size of  16 (0x 10 ) bytes 
    Table Type  35 ( 0x 23 ) found, size of  11 (0x 0B ) bytes 
    Table Type  29 ( 0x 1D ) found, size of  22 (0x 16 ) bytes 
    Table Type  36 ( 0x 24 ) found, size of  16 (0x 10 ) bytes 
    Table Type  35 ( 0x 23 ) found, size of  11 (0x 0B ) bytes 
    Table Type  26 ( 0x 1A ) found, size of  22 (0x 16 ) bytes 
    Table Type  28 ( 0x 1C ) found, size of  22 (0x 16 ) bytes 
    Table Type  27 ( 0x 1B ) found, size of  15 (0x 0F ) bytes 
    Table Type  29 ( 0x 1D ) found, size of  22 (0x 16 ) bytes 
    Table Type  39 ( 0x 27 ) found, size of  22 (0x 16 ) bytes 
    Table Type  41 ( 0x 29 ) found, size of  11 (0x 0B ) bytes 
    Table Type  41 ( 0x 29 ) found, size of  11 (0x 0B ) bytes 
    Table Type  41 ( 0x 29 ) found, size of  11 (0x 0B ) 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   4 ( 0x 04 ) found, size of  48 (0x 30 ) bytes 
    Table Type  16 ( 0x 10 ) found, size of  23 (0x 17 ) bytes 
    Table Type  17 ( 0x 11 ) found, size of  40 (0x 28 ) bytes 
    Table Type  17 ( 0x 11 ) found, size of  40 (0x 28 ) bytes 
    Table Type  19 ( 0x 13 ) found, size of  31 (0x 1F ) bytes 
    Table Type  20 ( 0x 14 ) found, size of  35 (0x 23 ) bytes 
    Table Type  20 ( 0x 14 ) found, size of  35 (0x 23 ) 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 11.0.0.0005 
MEBx Version                                 11.0.0.0005
GbE Region does not exist.
GbE Version                                  Unknown
Vendor ID                                    8086
PCH Version                                  21
FW Version                                   11.5.1.1006 LP
LMS Version                                  Not Available
MEI Driver Version                           11.5.0.1019
Wireless Hardware Version                    2.1.77
Wireless Driver Version                      19.2.0.1
                                             
FW Capabilities                              0x31111240
                                             
    Intel(R) Capability Licensing Service - PRESENT/ENABLED
    Protect Audio Video Path - PRESENT/ENABLED
    Intel(R) Dynamic Application Loader - PRESENT/ENABLED
    Service Advertisement & Discovery - NOT PRESENT
    Intel(R) NFC Capabilities - NOT PRESENT
    Intel(R) Platform Trust Technology - PRESENT/ENABLED
                                             
TLS                                          Disabled
Last ME reset reason                         Global system reset
Local FWUpdate                               Enabled
BIOS Config Lock                             Enabled
GbE Config Lock                              Enabled
Get flash master region access status...done
Host Read Access to ME                       Enabled
Host Write Access to ME                      Enabled
Get EC region access status...done
Host Read Access to EC                       Enabled
Host Write Access to EC                      Enabled
Protected Range Register Base #0 0x0
Protected Range Register Limit #0 0x0
Protected Range Register Base #1 0x0
Protected Range Register Limit #1 0x0
Protected Range Register Base #2 0x0
Protected Range Register Limit #2 0x0
Protected Range Register Base #3 0x0
Protected Range Register Limit #3 0x0
Protected Range Register Base #4 0x0
Protected Range Register Limit #4 0x0
SPI Flash ID 1                               EF4017
SPI Flash ID 2                               Unknown
BIOS boot State                              Post Boot
OEM ID                                       00000000-0000-0000-0000-000000000000
Capability Licensing Service                 Enabled
OEM Tag                                      0x00000000
Slot 1 Board Manufacturer                    0x00000000
Slot 2 System Assembler                      0x00000000
Slot 3 Reserved                              0x00000000
M3 Autotest                                  Disabled
C-link Status                                Disabled
Independent Firmware Recovery                Disabled
EPID Group ID                                0xF9D
OEM Public Key Hash FPF                      Not set
 
Retrieving Variable "OEM Public Key Hash" 
OEM Public Key Hash ME                       EA6FA86514FA887C9044218EDB4D70BB3BCC7C2D37587EA8F760BAFBE158C587
ACM SVN FPF                                  0x0
KM SVN FPF                                   0x0
BSMM SVN FPF                                 0x0
GuC Encryption Key FPF                       Not set
 
Retrieving Variable "GuC Encryption Key" 
GuC Encryption Key ME                        0000000000000000000000000000000000000000000000000000000000000000
                                             
                                             FPF                      ME
                                             ---                      --
Force Boot Guard ACM                         Not set        
Retrieving Variable "Force Boot Guard ACM Enabled" 
          Disabled
Protect BIOS Environment                     Not set        
Retrieving Variable "Protect BIOS Environment Enabled" 
          Disabled
CPU Debugging                                Not set        
Retrieving Variable "CPU Debugging" 
          Enabled
BSP Initialization                           Not set        
Retrieving Variable "BSP Initialization" 
          Enabled
Measured Boot                                Not set        
Retrieving Variable "Measured Boot Enabled" 
          Disabled
Verified Boot                                Not set        
Retrieving Variable "Verified Boot Enabled" 
          Disabled
Key Manifest ID                              Not set        
Retrieving Variable "Key Manifest ID" 
          0x0
Enforcement Policy                           Not set        
Retrieving Variable "Error Enforcement Policy" 
          0x0
PTT                                          Not set        
Retrieving Variable "Intel(R) PTT Supported" 
          Enabled
EK Revoke State                              Not Revoked
PTT RTC Clear Detection FPF                  Not set
 

reply

#2422 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Wed Sep 07, 2016 9:45 pm (Last edited: Wed Sep 07, 2016 10:09 pm)

Zitat von plutomaniac im Beitrag #2424
From the 6.x tools, run FPT with command fptw -d spi.bin and attach the resulting file.

Unfortunately, that doesn't work. When I do what you suggested this happens:

d:\Programy\Intel ME System Tools v6.x r3\Flash Programming Tool\Windows>fptw -d spi.bin

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

Platform: Intel(R) H55 Express Chipset Revision: B3
Reading HSFSTS register... Flash Descriptor: Invalid

--- Flash Devices Found ---

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

reply

#2423 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Wed Sep 07, 2016 10:20 pm (Last edited: Wed Sep 07, 2016 10:25 pm)

@ Wootever:

Yes, both these things were noticed by Pacman as well who first tried (and failed due to incompatibility) to flash 11.6 CON H firmware. Alright, no need to try anything with 11.6. I will wait for some documentation or a package to be 100% certain but for now your (and kostar20071's) reports are pretty much all we need. As for FIT+FPT, apparently it also worked just fine. However, it's not ideal. It worked becaused the image you took is RGN (clean). I remember that before I found the RGN 11.5.1, the EXTR equivalent would crash FIT 11.0. So the way I see it, the best solution is to use FWUpdate, otherwise FIT + RGN + FPT. If you decide to get a KBL cpu and want the latest microcode I have at that point, let me know then.

@ Octopuss:

No worries, that's because the tool is old and cannot detect your chip. Use the attached fparts.txt by replacing the old one at the FPT folder you plan to use. What we don't want to see is Error 26 (cpu access error) because that would mean a locked Flash Descriptor and thus a programmer would be required.

@ kostar20071:

I haven't looked at the Chipset INF files lately but the 200-series may be under UnionPoint folder because that's their codename.

plutomaniac has attached files to this post

fparts.rar

reply

#2424 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Wed Sep 07, 2016 10:26 pm

Zitat von plutomaniac im Beitrag #2429

@ Octopuss:

No worries, that's because the tool is old and cannot detect your chip. Use the attached fparts.txt by replacing the old one at the FPT folder you plan to use. What we don't want to see is Error 26 (cpu access error) because that would mean a locked Flash Descriptor and thus a programmer would be required.

d:\Programy\Intel ME System Tools v6.x r3\Flash Programming Tool\Windows>fptw -d
spi.bin

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

Platform: Intel(R) H55 Express Chipset Revision: B3
Reading HSFSTS register... Flash Descriptor: Invalid

--- Flash Devices Found ---
W25Q64BV ID:0xEF4017 Size: 8192KB (65536Kb)

Address 0x00000000 is not within any region.

Error 26: The host CPU does not have read access to the target flash area. To en
able read access for this operation you must modify the descriptor settings to g
ive host access to this region.

Is this bad?

reply

#2425 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Wed Sep 07, 2016 10:57 pm (Last edited: Wed Sep 07, 2016 11:01 pm)

We are trying to fix one thing and another issue appears. I think this has to do with Gigabyte being stupid. They used to set the Flash Descriptor BIOS starting location to 0x00 instead of the normal one. We can fix that as well, if that's really the problem and not that the FD is locked. Try commands fptw -d desc.bin -desc and fptw -d me.bin -me and fptw -d me.bin -a 0x1000 -l 0x4F2000, do they work?

reply

#2426 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Thu Sep 08, 2016 8:16 am (Last edited: Thu Sep 08, 2016 8:18 am)

Zitat von plutomaniac im Beitrag #2431
We are trying to fix one thing and another issue appears. I think this has to do with Gigabyte being stupid. They used to set the Flash Descriptor BIOS starting location to 0x00 instead of the normal one. We can fix that as well, if that's really the problem and not that the FD is locked. Try commands fptw -d desc.bin -desc and fptw -d me.bin -me and fptw -d me.bin -a 0x1000 -l 0x4F2000, do they work?

d:\Programy\Intel ME System Tools v6.x r3\Flash Programming Tool\Windows>fptw -d
desc.bin -desc

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

Platform: Intel(R) H55 Express Chipset Revision: B3
Reading HSFSTS register... Flash Descriptor: Invalid

--- Flash Devices Found ---
W25Q64BV ID:0xEF4017 Size: 8192KB (65536Kb)

Address 0x00000000 is not within any region.

Error 26: The host CPU does not have read access to the target flash area. To en
able read access for this operation you must modify the descriptor settings to g
ive host access to this region.

----

d:\Programy\Intel ME System Tools v6.x r3\Flash Programming Tool\Windows>fptw -d
me.bin -me

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

Platform: Intel(R) H55 Express Chipset Revision: B3
Reading HSFSTS register... Flash Descriptor: Invalid

--- Flash Devices Found ---
W25Q64BV ID:0xEF4017 Size: 8192KB (65536Kb)

Address 0x00000000 is not within any region.

Error 26: The host CPU does not have read access to the target flash area. To en
able read access for this operation you must modify the descriptor settings to g
ive host access to this region.

---

d:\Programy\Intel ME System Tools v6.x r3\Flash Programming Tool\Windows>fptw -d
me.bin -a 0x1000 -l 0x4F2000

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

Platform: Intel(R) H55 Express Chipset Revision: B3
Reading HSFSTS register... Flash Descriptor: Invalid

--- Flash Devices Found ---
W25Q64BV ID:0xEF4017 Size: 8192KB (65536Kb)

Address 0x00000000 is not within any region.

Error 26: The host CPU does not have read access to the target flash area. To en
able read access for this operation you must modify the descriptor settings to g
ive host access to this region.

P.S. How do you know all this stuff? In several years, I couldn't find a single person who could even describe what ME really does, and now here's you who almost look like you programmed it all :P

reply

#2427 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Thu Sep 08, 2016 9:40 pm (Last edited: Thu Sep 08, 2016 9:43 pm)

I'm confused, I said earlier that you most probably used FPT to flash the stock 1.5MB firmware so a) FPT had to work and b) your FD to be unlocked for that to be successful. Try FPT from 6.0 package (no need to replace fparts.txt there) and let me know if this works with fptw -d spi.bin command.

I haven't even scratched the surface of the security engine called ME. Trust me, I know nothing of actual importance. As for the rest, lots of research, tests and most importantly help from the great members of this community.

reply

#2428 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Thu Sep 08, 2016 11:35 pm

(about 500 pages worth of this)
PMXUtil: Error during PMX Call: PMxDrv!PCI - Failed Call to OS_SafePCI
PMXUtil: Error during PMX Call: PMxDrv!PCI - Failed Call to OS_SafePCI
PMXUtil: Error during PMX Call: PMxDrv!PCI - Failed Call to OS_SafePCI
PMXUtil: Error during PMX Call: PMxDrv!PCI - Failed Call to OS_SafePCI
PMXUtil: Error during PMX Call: PMxDrv!PCI - Failed Call to OS_SafePCI
PMXUtil: Error during PMX Call: PMxDrv!PCI - Failed Call to OS_SafePCI
PMXUtil: Error during PMX Call: PMxDrv!PCI - Failed Call to OS_SafePCI
PMXUtil: Error during PMX Call: PMxDrv!PCI - Failed Call to OS_SafePCI
PMXUtil: Error during PMX Call: PMxDrv!PCI - Failed Call to OS_SafePCI
PMXUtil: Error during PMX Call: PMxDrv!PCI - Failed Call to OS_SafePCI
PMXUtil: Error during PMX Call: PMxDrv!PCI - Failed Call to OS_SafePCI
PMXUtil: Error during PMX Call: PMxDrv!PCI - Failed Call to OS_SafePCI
Platform: Intel(R) H55 Express Chipset Revision: B3
Reading HSFSTS register... Flash Descriptor: Invalid

--- Flash Devices Found ---
W25Q64BV ID:0xEF4017 Size: 8192KB (65536Kb)

Address 0x00000000 is not within any region.

Error 26: The host CPU does not have read access to the target flash area. To en
able read access for this operation you must modify the descriptor settings to g
ive host access to this region.

reply

#2429 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Fri Sep 09, 2016 12:55 am (Last edited: Fri Sep 09, 2016 12:57 am)

Alright, I don't know exactly what tool was used to flash the firmware that you said worked or what has happened for that matter. I am confused at this point. I can't think of anything else that flashes images, it can only be FWUpdate or FPT. Anyway, let's move on from FPT.

Let's try the obvious. Download the attached BIOS, put it at a FAT32 formatted USB drive and flash it via the BIOS menu, wherever the equivalent option is. After it succeeds, run fptw -greset and check if the ME device driver is there after the system has reset and if MEInfo and MEManuf from v6.x work.

plutomaniac has attached files to this post

h55mud2h.rar

reply

#2430 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Fri Sep 09, 2016 10:32 am (Last edited: Fri Sep 09, 2016 10:40 am)

Ha, that worked. I flashed a newer BIOS, but that isn't important.
Now what should I do to update the damn ME? :D

d:\Programy\Intel ME System Tools v6.x r3\MEInfo\Windows>MEInfoWin.exe

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

PMXUtil: Error during PMX Call: PMxDrv!MAPPHYS - Bad Input Parameters

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

BIOS Version: F12j
MEBx Version: 0.0.0.0
Gbe Version: Unknown
VendorID: 8086
PCH Version: 6
FW Version: 6.0.30.1203
UNS Version: Not Available
LMS Version: Not Available
MEI Driver Version: 6.2.50.1050
Wireless Hardware Version: Not Available
Wireless Driver Version: Not Available

FW Capabilities: 7232

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: Never
FWU Override Qualifier: Always
Local FWUpdate: Disabled
OEM Id: 00000000-0000-0000-0000-000000000000
Capability Licensing Service: Enabled
Capability Licensing Service Status: Permit info not available
Override to RPAT-c SKU: Not Set
FW behavior on Flash Descriptor Override Pin-Strap: Halt

reply

Repair MEI on Samsung NP550P7C-S04PL � � Strange ME Region size mismatch after reconfiguring and rebuilding

Page 162 of 380 � Page 1 ... 157 158 159 160 161 162 163 164 165 166 ... 380 Page �

Please enter a reason for warning.