Forum - RE: ME Analyzer: Intel Engine Firmware Analysis Tool

Win-Raid Forum (Drivers - Firmware - Modding) � Special Topics � Intel Management Engine � ME Analyzer: Intel Engine Firmware Analysis Tool Discussion

Page 15 of 21 � Page 1 ... 10 11 12 13 14 15 16 17 18 19 ... 21 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

#211 | RE: ME Analyzer: Intel Engine Firmware Analysis Tool datum

Sun Dec 11, 2016 1:01 pm

Can I use MEA to update the MEI fw in a BIOS file?

reply

#212 | RE: ME Analyzer: Intel Engine Firmware Analysis Tool datum

Mon Dec 19, 2016 4:38 pm

ME Analyzer v1.7.0 Dev 21 & DB r74

reply

#213 | RE: ME Analyzer: Intel Engine Firmware Analysis Tool datum

Mon Dec 26, 2016 9:17 pm (Last edited: Mon Dec 26, 2016 11:45 pm)

ME Analyzer v1.7.0 Dev 35 RC & DB r75 Dev 3

The next version of MEA is almost ready with big changes all around. So please test and let me know of any issues.

reply

#214 | RE: ME Analyzer: Intel Engine Firmware Analysis Tool datum

Sat Jan 07, 2017 1:32 am

ME Analyzer v1.8.0 & DB r75

v1.8.0

Added Engine firmware size validation and display
Added ME 11.x FIT SKU detection (11.0 - 11.6)
Added $FPT header checksum validation check
Added $FPT Entry Counter validation check
Added Manifest detection from $FPT directly
Added parameter to display $FPT header details
Added early support for TXE 3.x APL firmware
Added ME 11.x Flash Descriptor EC lock detection
Added info to fix FWUpdate-buggy ME 11.x images
Added SPS 3.x $FPT checksum validation check
Added support for ME2-ME6 SPI Flash Descriptor
Added support for ME 6.x ROM-Bypass firmware
Improved detection & analysis of $FPT header
Improved VCN detection of post-SKL ME,TXE firmware
Improved Engine Release detection (PRD/PRE/BYP)
Fixed wrong Engine $FPT selection when multiple exist
Fixed wrong error messages at special TXE 1.x images
Fixed various code issues and errors under rare cases
Removed irrelevant info shown at Partial Update images
Removed option to extract Dell HDR RBU ImagME Regions
Removed option to print whole DB without SHA1 hashes
Removed option to encode all textual output to Unicode
MEA now pauses automatically at unexpected exceptions
Various code optimizations and performance improvements
Updated Engine Firmware Repository Database to r75

r75

Latest ME 11.6 CON LP SKU to 11.6.10.1196
Latest TXE 2.1 1.375MB SKU to 2.1.5.3105
Added ME 11.6.10.1196_CON_H_D0_NOPDM_PRD_RGN
Removed ME 11.6.10.1196_CON_H_D0_NOPDM_PRD_EXTR
Added ME 11.6.10.1196_CON_LP_C0_UKPDM_PRD_EXTR
Added ME 11.6.1.1142_CON_H_D0_UKPDM_PRD_RGN
Removed ME 11.6.1.1142_CON_H_D0_UKPDM_PRD_EXTR
Added ME 11.6.1.1142_CON_LP_C0_PDM_PRD_RGN
Added ME 11.6.0.1121_CON_H_D0_NOPDM_PRD_RGN
Added ME 11.6.0.1121_CON_LP_C0_NOPDM_PRD_RGN
Removed ME 11.6.0.1121_CON_LP_C0_UKPDM_PRD_RGN
Added ME 11.6.0.1121_CON_H_D0_NOPDM_PRE_RGN
Added ME 11.6.0.1121_CON_LP_C0_NOPDM_PRE_RGN
Renamed ME 11.0.18.1002_CON_H_D0_NOPDM_PRD_RGN
Added TXE 2.1.5.3105_1.375MB_PRD_EXTR
Added SPS 04.00.03.137_PRD_REC
Added SPS 04.00.03.137_PRD_OPR

reply

#215 | RE: ME Analyzer: Intel Engine Firmware Analysis Tool datum

Tue Jan 17, 2017 3:45 am

Hi, it seems that ME Analyzer v1.8.0 & DB r75 wrongly detects size of ME FW blob in my case.

File: P67DS_F5.BIN
Family: ME
Version: 7.1.20.1119
Release: Production
Type: Region, Extracted
FD: Unlocked
SKU: 1.5MB
Date: 08/08/2011
Size: 0x17D000
Platform: CPT
Latest: No

But FIT 7.1.60.1191 unpacked ME Region.bin file only 839680B and when I checked with hexaeditor I can see only FFh blank behind 839680+4k descriptor offset. FIT doesn't show ME size anywhere. I'm not sure if it's right as other 7.x ME FW blob, e.g. 7.1.80.1214 has 1335296B. Maybe GB used some stripped version? You can check yourself, BIOS image is
here

reply

#216 | RE: ME Analyzer: Intel Engine Firmware Analysis Tool datum

Tue Jan 17, 2017 7:02 pm

I haven't tested the file but I know MEA is correct. If you load the FITC "ME Region.bin" at MEA you'll see a Warning about possible data loss. FITC v2 to v10 used to cut all the padding from extracted ME images even if that violated region boundaries. Before reinserting the file back to the BIOS/SPI image, FITC would just readd the padding. Stupid but that's how it worked. MEA detects the size intelligently from what the actual firmware reports. At bare Engine regions it can check for extra (useless) padding, less (possible data loss) padding and at full SPI images it can check if there are extra/unknown data after the ME firmware size but before the ME region actually ends as described at the Flash Descriptor.

reply

#217 | RE: ME Analyzer: Intel Engine Firmware Analysis Tool datum

Fri Jan 20, 2017 8:26 pm

Is the total ME size stored inside the blob or you have to calculate it according parsig the ME partition table or so? Yeah, interesting that FIT is cutting the paddings. I see more ME FW blobs that differ slightly in size, seems there's no standard. But it it seems to be safe to cut off unnecessary padding as when inserted to flashROM empty pages are blanked and no used anyway... Thanks for explanation.

reply

#218 | RE: ME Analyzer: Intel Engine Firmware Analysis Tool datum

Fri Jan 20, 2017 11:59 pm

Thank you for your interest in ME Analyzer and for using it.

Zitat von RayeR im Beitrag #217
Is the total ME size stored inside the blob or you have to calculate it according parsig the ME partition table or so?

It has to be calculated manually and after taking in mind all the differences, weirdness, uncharted sections etc which have appeared in all the firmware that MEA supports (10 ME, 3 TXE and 4 SPS major generations). MEA is open source so if you are interested, the full code on how it calculates the sizes can be found at its github page.

Zitat von RayeR im Beitrag #217
Yeah, interesting that FIT is cutting the paddings. I see more ME FW blobs that differ slightly in size, seems there's no standard.

The size of the ME region does not matter as long as data are not lost. MEA checks that but also reports extra padding to lower the required filesize. For example, you can find a 8MB ME region at an SPI image with only the first 1.5MB taken by the ME code and everything being unneeded padding. This is due to various reasons but the most usual is that, by design/default, any extra space of the SPI image is appended to the ME region. So, if a system uses a 16MB chip and the BIOS is 9MB for example, the ME will be padded at the end if its region to fill the rest, meaning approximately 7MB (minus the Flash Descriptor which is 4KB at the start).

Zitat von RayeR im Beitrag #217
But it it seems to be safe to cut off unnecessary padding as when inserted to flashROM empty pages are blanked and no used anyway... Thanks for explanation.

I don't understand this sentence.

reply

#219 | RE: ME Analyzer: Intel Engine Firmware Analysis Tool datum

Mon Jan 23, 2017 3:07 am

ME Analyzer v1.8.1 & DB r76

reply

#220 | RE: ME Analyzer: Intel Engine Firmware Analysis Tool datum

Sun Jan 29, 2017 3:09 am

ME Analyzer v1.8.2 & DB r77

reply

#221 | RE: ME Analyzer: Intel Engine Firmware Analysis Tool datum

Sat Feb 18, 2017 10:01 pm (Last edited: Sat Feb 18, 2017 10:03 pm)

ME Analyzer v1.9.0

reply

#222 | RE: ME Analyzer: Intel Engine Firmware Analysis Tool datum

Sun Mar 05, 2017 3:34 pm

@ all:

This thread is now a discussion topic only and just links to github for everything else.

To download MEA, report bugs, recommend new functionality etc go to the Github's Issues page. Anything not strictly MEA related should be discussed here and not github.

Changelogs won't be posted here anymore. I urge you to Follow the twitter account @platomaniac for news and/or Watch the project over at Github for detailed changelogs and pre-build releases.