Then there must be something wrong with how MEInfo from Intel.CSME.System.Tools.v11 r11 works on my system? Please see the screenshot. I first ran MEInfo successfully from "Intel.CSME.System.Tools.v11 r10" followed by MEInfo from "Intel.CSME.System.Tools.v11 r11". The latter keeps giving error 82 each and every time I run it???
In case you missed what I said in the OP I used FWUpdLcl64.exe from the version that the MEInfo give error 82 [Intel.CSME.System.Tools.v11 r11] to update the ME firmware from v11.8.50.3460 to v11.8.50.3470. However, I have to use "Intel.CSME.System.Tools.v11 r10" to read the me info without the error 82?
What could be the problem? Is there any command I could run to diag this error with any tool?
UPDATE:
I ran "FPTW64.exe -d spi.bin" from "Intel.CSME.System.Tools.v11 r11" which ran successfully with the following output:
However I thought I should report this as asked at the bottom of the CMD because the MEAnalyzer tool that I ran on the spi.bin file reported that the firmware is not found at the database [but I got the firmware from the first post of this thread?] :
Run MEInfo from C:\ directory or somewhere with a simpler path name, just in case that’s the issue. On a 200-series laptop with CSME 11.8.50.3460, both MEInfo 3460 and 3470 worked perfectly. I then updated to CSME 11.8.50.3470 and, again, both MEInfo 3460 and 3470 worked as expected.
Your copy of ME Analyzer is older, that’s why you get the message.
By the way, since 3460 and 3470 have the same VCN, you can downgrade to 3460 and do tests there if you like.
I have been running it from c:\ and I have tried different names with and without spaces and from just 2 letters long to the full name of how the file un-rars. BTW talking about un-raring…interestingly enough I just discovered another bug/error. I get an error with 7zip v1805 when I try and extract only the WIN64 and WIN folders of MEInfo by either drag and drop or highlight either folder and choose "Extract"? See screenshots;
I get this error no matter where I store "Intel CSME System Tools v11 r11.rar" on my drive and no matter what I rename it to.
Next step is testing different versions of 7zip and also if there is another source/mirror for "Intel CSME System Tools v11 r11" to test it against the one I got from the 1st post of this thread. There MUST be a link between what 7zip is doing with the very folder/files that I am getting error 82 from where MEInfo is taken from. Maybe, just maybe I am getting close to solving this mystery [hopefully, soon to be mystery no more :]
yes I certainly shall report this to Igor, it’s the second bug that I have had to report, although the first one was actually a Windows 10 bug that got fixed in the April update [the cursor would jump out of the 7zip window when you click and drag with multiple files when either Horizontal and/or Vertical scroll bar was active and at its/their default position]. Thanks for your continual feedback and support :}
I’ve found that its current installed BIOS version is A09, and I can’t upgrade to the most recent, A25. I’m able to run the executable file, the computer restarts but nothing changes. It doesn’t even show a screen updating BIOS, it’s a normal restart.
Looking at the first page of the topic, I’ve tried to run MEInfo, the result is shown below:
----- Intel(R) MEInfo Version: 9.5.35.1850 Copyright(C) 2005 - 2014, Intel Corporation. All rights reserved.
Error 9256: Communication error between application and Intel(R) ME module (FW Update client)
Error 9256: Communication error between application and Intel(R) ME module (FW Update client)
Error 9256: Communication error between application and Intel(R) ME module (FW Update client)
Error 9256: Communication error between application and Intel(R) ME module (FW Update client)
Error 9459: Internal error (Could not determine FW features information) -----
There is no Intel Management driver installed in Device Manager. When I try to install such driver, I got a “this platform is not supported” error message.
To fix that issue we need read/write access to the firmware. At the Flash Descriptor guide you can find all the possible methods to do that. Otherwise, you’ll need to use a hardware programmer.
The goal is to test if you can dump the full SPI chip image via Flash Image Tool (fptw -d spi.bin) after setting the bit. MEInfo is irrelevant. If the steps at the FD guide don’t help, the only option is to use a hardware programmer.
Even setting the bit, fptw shows the following error: Error 26: The host CPU does not have read access to the target flash area. To enable read access for this operation you must modify the descriptor settings to give host access to this region.
Intel MEI Driver v12.0.2021 (Windows 8 & Windows 10) INF for manual installation Intel MEI Driver v12.0.2021 (Windows 7) INF for manual installation Intel MEI v12.0.1130 for Consumer systems Drivers & Software
just tried to install Intel ME driver v1815.12.0.2021 for Windows 7 on a new System with Intel ME 12.0.
The provided .INF has to be modified, adding to section [Intel.NTx86.6.1] %TEE_DeviceDesc%=TEE_DDI, PCI\VEN_8086&DEV_9DE0 ;ME12.0 - CNL/CNP-LP %TEE_DeviceDesc%=TEE_DDI, PCI\VEN_8086&DEV_A360 ;ME12.0 - CNL-H
and to section [Intel.ntamd64.6.1] %TEE_DeviceDesc%=TEE_DDI_x64, PCI\VEN_8086&DEV_9DE0 ;ME12.0 - CNL/CNP-LP %TEE_DeviceDesc%=TEE_DDI_x64, PCI\VEN_8086&DEV_A360 ;ME12.0 - CNL-H
This will make the .INF unsigned but nonetheless the Intel ME 12.0 driver v1815.12.0.2021 will be installed successfully on Windows 7
