Thanks for the file! But this is just the Tee Driver, not a complete driver package? And in the inf file it mentions only newer ME firmwares (ME 10 and ME 11)?
Yes it is not a complete driver installation package. If you want to have driver installation packacke with a exe file then on station-drivers.com these files are.
The Tee Driver installs on me 9.x.
@lfb6 Yes, FIT 15 was always behaving in a weird way. You can get it to work by selecting the equivalent platform at the top first. H or LP, depending on the input firmware. In my experience, for H, the RKL one works more often than the old one, but you may need to try both.
Also, it had this bug in which it would not get rid of some IUPs upon de-compilation (SAMF, PCHC, NPHY). These can be removed manually only.
Has a date 2022-11-04, but I don’t see a hint in the forum and it’s not in the database of MEA?
EDIT
Had a closer look and it seems it has been added in DB r309 already and is in the linked repo in #1. This one is marked as new because of a slightly different date (2 days younger) and a different RSA signature.
Yeah, the only difference is those 2 days and the RSA signature of course. Identical otherwise. This was happening often with TGP stuff, including IUPs. My guess is that they released different system tool kits for TGP-based PCH/SoCs and would (stupidly) recompile the same firmware with slightly different dates. Anyway, they are the same.
Warning: CSE FW version: 15.0.49.2573 is not the same as the FIT version: 15.0.35.1951
If pre-locking is not set, closemnf will revert back master access settings to ‘golden master access settings’. To set master access post locking, use -CLOSEMNF command of the Intel(R) Flash Programming Tool (FPT). Error 237: [Ifwi Actions] Failed to load input file. IO Manageability Engine Binary File: Empty file path
Error 20: [Csme Binary Gen] Error executing pre-build actions.
Error 2: Failed to build.
Failed to build!
The de-compiled IomOemConfigDataFile.bin is at 0KB. The CSME v12 instructions include a couple extra steps, but I don’t think they apply for 15. Thanks
Edit: Updated Intel(R) Tigerlake LP Refresh C0 Chipset to Intel(R) Tigerlake LP Refresh C0 Chipset, but still getting the same error/result.
I’m just trying to create a stitched ME firmware, like you and others are doing, and that should be achievable, regardless of my machine, as long as I’ve got the correct CSME FIT (CSME System Tools v15.0 r15 is good), ME firmware, PCHC.bin, and PMC.bin. PHY shouldn’t be needed.
It’s weird that the FIT 15 program changes the chipset to tigerlake LP Refresh C0 from LP B0. When I change it back, I’m getting the error. If I leave it at Refresh C0, I’m getting the error.
I am glad that you asked me to run the MEA program, though, because I’m getting the dreaded “Impossible” FWUpdate Support. This does make sense, because when I updated the Dell Latitute 5320 firmware update, the Dell program updates the Corp ME, looks to update the Consumer ME but doesn’t, and then I get another “off” MEInfo run.
It’s a strange setup, for sure. If I extract the downloaded Dell bios update, there’s a corporate and consumer ME bin, and I guess that makes sense, even though the Dell update program looks first to update both. The weirdess is the MEA vs. the MEInfo. MEA says Corporate LP. MEInfo says LP Consumer.
The “Impossible” makes this a mute point, but I should be able to stitch, regardless, but FIT is choking.
