Error Building image with Intel Flash Image Tool

Hi there,

First post, so apologies if I did anything incorrectly.

I’ve been following this guide on Imgur to enable AMT/ME on Dell Optiplex 7040’s with great success, however, I’ve run into a situtation where I needed to go back and enable some features that I had previously left disabled. I’m able to export the BIN using FPTW just fine, but the FIT is unable to build the image based on that BIN, throwing the errors below. On both systems I’ve enounterd this issue, Intel ME has been upgraded to the latest v11.8.82, so I’m not sure if there’s a mismatch there. I’ve tried different builds of FIT v11, with the newest I’ve been able to find being v11.8.79.3722.

Any ideas would be much appreciated!


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
 
02/10/2021 13:22:16
Using vsccommn.bin with timestamp 19:06:41 03/20/2020 GMT
 
Command Line: C:\Users\kadmin\Downloads\!Intel CSME System Tools v11 r37\fit.exe
 
Log file written to fit.log
 
Loading C:\Users\kadmin\Downloads\!Intel CSME System Tools v11 r37\me.bin
 
Decomposed SKU Value: "Intel (R) H Series Chipset - Intel (R) Q170 - Desktop".
 
Warning: The ME FW image loaded has been pulled from a previously booted system. Some FW settings will not be allowed to be changed.
Warning: Could not set "Redirection Privacy / Security Level" to: 0x0000000000000000000000000000000000000098FFD935F71FDEC9CF01DC5894F5624B37F733B395CB2011594BEAF5CBA8E7D38201, reverting to previous/default value: Default
Writing map file C:\Users\kadmin\Downloads\!Intel CSME System Tools v11 r37\me\me.map
Executing pre-build actions
Warning: Did not update "IshSigningPolicy" because the ME FW is from a previously booted system.
Warning: Did not update "OdmIDIntelServices" because the ME FW is from a previously booted system.
Warning: Did not update "SysIntIdIntelServices" because the ME FW is from a previously booted system.
Warning: Did not update "ReservedIdIntelServices" because the ME FW is from a previously booted system.
Warning: Did not update "NvarPostManUnLckd" because the ME FW is from a previously booted system.
Warning: Did not update "PkiDomainSuffix" because the ME FW is from a previously booted system.
Warning: Did not update "PkiDomainSuffix" because the ME FW is from a previously booted system.
Warning: Did not update "EhbcEnable" because the ME FW is from a previously booted system.
Error 21: [NvarActions] Data Conversion error.
Error converting data type of length: 53
NVAR name: RedirectionPrivSecLevel
value: 1
Error 37: [NvarActions] Could not write NVAR value. RedirectionPrivSecLevel
Error 14: [NvarActions] Failed to write NVAR. RedirectionPrivSecLevel
Error 5: [CsmeBinaryGen] Error executing pre-build actions.
Error 15: Failed to build.
Failed to build!
 

Hi,

Although you haven’t lined to the dump you’re working on and is thus not possible to reproduce/diagnose, try following [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization instead and adjust any AMT settings during Step 6. It is generally a much better idea to work on a non (File System) Initialized CSME firmware.