Hello plutomaniac, do you have any private contact, e-mail or something?
You can send a pm here
Ok, maybe I missed a part or a post, but MEAnalyzer displayed I should update to v1.283.3.
Downloaded the package from Github but the MEA.exe is missing.
Made also sure that my AV (Eset) didnât interfere, but nothing in the logs or quarantine.
Itâs not like that, that I need it urgently, the previous version 1.283.2 did itâs job on my âoldâ notebook, but still wondering whether it was forgotten or removed from the package on purpose.
Cheers
Tom
EXE wasnât there, you have to compile it yourself. Try reading the README file
Well, thatâs a bummer, install Python, compile, just to have a slight bump in version number for a minor fix.
Thanks anyway.
Cheers
Tom
A post was merged into an existing topic: Intel (Converged Security) Trusted Execution Engine: Drivers, Firmware and Tools
I wonder- CSE SPS 04.04.04.500 and CSE SPS 06.00.03.505 should be known to MEA according to history, but are still marked?
Whitley was never supported, actually, even in the past. That platform (4.4) was so bad that I refused to spend the time to try to make it work at MEA. An abomination.
For CSSPS 6, only Tatlow should not display the âunsupportedâ message, which it does (in the picture). The âhashâ errors MEA reports are valid/true, Intel had bad hashes in some CSSPS families, which clearly were not used for something there so it didnât matter I suppose.
1 Like
Thank you! But itâs the ânew - not foundâ message I was wondering about:
CSSPS 04.04.04.500_WH_SVR_B_PRD_EXTR is included in DB r333
CSSPS 06.00.03.505_TA_SVR_B_PRD_EXTR is included DB r332
but they still get a ânot in the database - please report inâ
1 Like
Ah, I see. My suspicion is that these files are in a non-standard (for SPS firmware) format. Can you attach them to take a look?
1 Like
Those were HP updates, the two mentioned versions and an older version (04.04.04.053) behave identically.
SPS.zip (5.6 MB)
1 Like
Ah, ok, I forgot. At CSSPS 4.4 (WH) and 6.0 (TA), the database does not include records for OPR and REC, only EXTR. For WH, I never bothered (unsupported). For TA, it was added right before stopping the maintenance of the tool, so the minimum effort was to simply add EXTR (without extracting the OPR/REC from within). Also, if I remember correctly, Intel stopped distributing OPR and REC separately in the System Tools packages, so I left only EXTR at the DB.
Moreover, those firmware images are indeed non-standard. They are actually in IFWI (BPDT) format, which is weird. Maybe custom HP logic is used for updating or something. You can see by â-dfptâ parameter too:
1 Like
Interesting, thank you! But are you still interested to get those SPS versions or are they completely irrelelvant to you?
In both cases itâd be nice to have a different message like:
âUnsupported SPS, please check version with latest MEA.dat. If unknown version you can help this project by sharing it at https://win-raid.com forum. Thank you!â
or - if youâre not interested at all -
âUnsupported SPSâ
But I understand that the amount of reported SPS versions might be too small to justify a code- change.
1 Like
I actually worked on an update to MEA during the previous weekend, after 1 year or something 
, which re-writes the ugly and (most importantly) broken JSON output it had before. As I had promised, I will maintain supported features and JSON was supported but, honestly, completely broken.
So, anyway, I decided to add two lines of code to check only if the hash of the SPS 4.4 and 6.0 firmware exists at the DB, without caring if itâs EXTR, OPR or REC. Small fix that one, but since I worked on the (much more difficult) JSON output topic, why not?
So, in the upcoming MEA version (v1.300.0), you wonât be seeing the ânew fwâ message for SPS 4.4 and 6.0 (unless even their EXTR cannot be found at the DB).
As for your question on what Iâm interested in, indeed I donât maintain MEA anymore with new features, firmware etc. But, even if I donât end up adding something (new) to the DB, I do believe that it is a good idea for people to share what they find (by attaching them at the forum for example) so that the content is there for future reference. Personally, I collect/download some unsupported stuff and simply keep them. The supported firmware are also added to MEA DB of course.
3 Likes
Thanks for the clarifications, looking forward to the next version of MEA 
1 Like
The latest MEA v1.304.4 should not display ânot in dbâ messages for unsupported platforms anymore. That includes CSSPS 6, which has been dropped as supported altogether.
platomav/MEAnalyzer: Intel Engine & Graphics Firmware Analysis Tool (github.com)
Huh, why have you moved 16.0 and 16.1 to unsupported too and removed them from MEA DB? A very strange decision for what?
Good job, thanks to your SPS complaints, Alder Lake support has been removed and we will not be able to see which 16.x CSME firmware are in the database and which are not. Unfortunately, from now on I will have to stay on the old version and maintain my own DB. 